What will be the impact?

I want to know who can track us while performing this testing!
The imsi capture is not detected because we does not send the packets to the other side just receive them!
Can you please tell me which attacks will be tracked! Can we use vpn or tor to protect our self?
How to be untraced!

its your operator's responsibility
On Fri, Dec 28, 2018 at 9:05 AM Kate Saikishore<EMAIL_ADDRESS>wrote:

I want to know who can track us while performing this testing!
The imsi capture is not detected because we does not send the packets to
the other side just receive them!
Can you please tell me which attacks will be tracked! Can we use vpn or
tor to protect our self?
How to be untraced!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SigPloiter/SigPloit/issues/158, or mute the thread
https://github.com/notifications/unsubscribe-auth/AXXuvwxADrukeV0gSMkAaLhaNuFiLA4cks5u9cLOgaJpZM4ZjiMa
.


kie-issues#296: Fix CVE-2022-3517 in kogito-apps and kie-tools

Closes https://github.com/kiegroup/kie-issues/issues/296
Fixes CVE-2022-3517 vulnerability on minimatch:3.0.4.
This is part of an ensemble, please merge with:
https://github.com/kiegroup/kie-tools/pull/1687
https://github.com/kiegroup/kogito-apps/pull/1746

Closed in favor of https://github.com/kiegroup/kie-tools/pull/1710


feat: more nav bar work

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3451

PR #3456

PR #3457   👈

This comment was auto-generated by Graphite.

@wraeth-eth queued this pull request to merge with Graphite.

Graphite rebased this pull request as part of a merge.

@wraeth-eth merged this pull request with Graphite.


can't import ComfyUI_Jags_Audiotools module for custom nodes: 'reduce_cython'

Here's the related log, I install ComfyUI_Jags_Audiotools](https://github.com/jags111/ComfyUI_Jags_Audiotools and restart it,  but Import failure.

i will check this and update


[native] Add substitute Windows headers

Adds substutite Windows + DirectX headers for use when building DXVK natively for Linux

If there is anything here to review at all really, it's the winbase.h I made which just has the substitute Windows defines.
There is also native_sdl2.h but that's not very interesting really.

For any header license concerns please see native/directx/readme.txt.
The relevant part (copied exactly from their COPYING file):
DirectX and DDK headers are under GNU LGPLv2.1+ (see the file
COPYING.LGPLv2.1) and copyrighted by various people. Using these
headers doesn't make LGPLv2.1 apply to your code, because these
headers files contain only data structure definitions, short
macros, and short inline functions. Here is the relevant part
from LGPLv2.1 section 5 paragraph 4:

    If such an object file uses only numerical parameters, data
    structure layouts and accessors, and small macros and small
    inline functions (ten lines or less in length), then the use
    of the object file is unrestricted, regardless of whether it
    is legally a derivative work.


Add FAQ and Some Link in Report pages

PR Checklist
Please check all that apply to this PR using "x":

[ x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x ] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ x] Feature
[ ] Breaking changes (bugfix or feature that introduces breaking changes)
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

What is the new behavior?

Great idea @ykris45. I made a few minor changes.


Missing cmake documentation

I'm trying to build a project that use some library like glm, QT, Vulkan etc.
Of course, I'm trying to use glTF-SDK too.
I'm struggling a lot because there is no documentation on how to use CMake with glTF-SDK
To be more specific CMake through the use of the FetchContent command can act as a package manager.
So I'm trying to use it in that way avoiding to use NuGet or vckpg
Can someone add an example on how to use this library from CMake in a proper way?

I'm not familiar with FetchContent usage and I don't know anyone who has tried it with this repo, but this seems like a cmake question and not something specific to this repo. If you bring the repo as a cmake dependency (e.g. via add_subdirectory), you should be able to include the GLTFSDK target. Would that work for you?

I'm not familiar with FetchContent usage and I don't know anyone who has tried it with this repo, but this seems like a cmake question and not something specific to this repo. If you bring the repo as a cmake dependency (e.g. via add_subdirectory), you should be able to include the GLTFSDK target. Would that work for you?

This worked for me:
# If you are not interested in using UNIT TESTS or SAMPLES, assign the variables to OFF
set(ENABLE_UNIT_TESTS OFF)
set(ENABLE_SAMPLES OFF)

# Declare the repo
include(FetchContent)
FetchContent_Declare(
  glTF-SDK
  GIT_REPOSITORY https://github.com/microsoft/glTF-SDK.git
  GIT_TAG        382dea2c80737f9f3ae2b93e97263a593c2ea832 # r<IP_ADDRESS>
)

# Populate the library
FetchContent_MakeAvailable(glTF-SDK)

# Link to your target
target_link_libraries(MyTarget GLTFSDK)


ESLint lightbulb not showing up in certain circumstances

VSCode Version: 10.12-alpha
OS Version: Mac

Regarding test item #5654
I'm not getting a lightbulb on one of my custom rules.
Also while this is less important, in my opinion it's not very intuitive for me to have to put my cursor at the beginning of an error.  Could you enable it whenever the cursor is over any part of an error (Maybe that's not possible)?
Problems:
1
With this setting,
"no-use-before-define": [
    "error"
]

I get an error, as expected, on trying to increment brad before I've defined it as a variable.  However, I get no lightbulb when the cursor is positioned at brad like I would get with some other error.
brad ++;
var brad = 1;

2
With no trailing commas rule, I also can't get a light bulb.

This issue was moved to Microsoft/vscode-eslint#75


yeast 8.7.1

Main improvements in this PR:

Fix:

Failing GitHub Action workflows (PR #350)
Correct 'enxyme' in r_1024 reaction name (PR #355)
Make .standard-GEM.md hidden (PR #357)

Features:

UniProt annotations for all genes (PR #349)

I hereby confirm that I have:

[x] Selected main as a target branch (top left drop-down menu)

All issues have been reviewed in their respective PR.


Error creating machine: Error in driver during machine creation [ boot2docker under xhyve ]

occurs on macOS Mojave 10.14.2
Homebrew used to install: dinghy, docker, docker-compose, docker-machine, docker-machine-nfs, docker-machine-driver-xhyve

codekitchen/dinghy/dinghy 4.6.5
docker 18.09.0
docker-compose 1.23.2
docker-machine 0.16.0
docker-machine-driver-xhyve 0.3.3_1

Meanwhile, recommend to use an older version for boot2docker by specifying --boot2docker-url
dinghy create --provider=xhyve --cpus=2 --memory=8192 --disk=80000 --boot2docker-url=https://github.com/boot2docker/boot2docker/releases/download/v17.12.1-ce/boot2docker.iso

:white_check_mark:: dinghy create --provider=xhyve --cpus=${cpus:-3} --memory=${memory:-4096} --disk=${disk:-40000} --boot2docker-url=https://github.com/boot2docker/boot2docker/releases/download/v18.06.1-ce/boot2docker.iso
:rocket:: eval $(dinghy env)

@codekitchen

Yes i can reproduce that. But i thing this is a problem with ne driver and boot2docker

This does look like a problem with boot2docker or the xhyve driver. Do you get the same error if you do a docker-machine create -d xhyve directly?
On your workaround, was there a particular reason that you chose the v18.06.1-ce boot2docker version? I'm curious why that would fix it.
If this does happen when running docker-machine create directly also, I'd recommend reporting it to the docker-machine-driver-xhyve project. I'll see if I can repro as well.

I did  docker-machine create -d "xhyve" theMachine directly.

Workaround came as v18.06.1-ce boot2docker was the last version that I remembered I had tried  before and worked.

Have you succeeded to repro?

I am able to successfully repro, and I found this existing issue in the docker-machine-driver-xhyve project for the issue: https://github.com/machine-drivers/docker-machine-driver-xhyve/issues/211
It sounds like it has already been fixed upstream and the fix will be in the next boot2docker release, so your workaround is the best option for now.

Yes it will work with
dinghy create --memory=8000 --cpus=4 --disk=100000 --provider=xhyve --boot2docker_url="https://github.com/boot2docker/boot2docker/releases/download/v18.09.1-rc1/boot2docker.iso"


Fixes issue with non-encrypted database connection

Was improperly evaluating config value of false as true, so always thought database connections were to use SSL. Fixed by changing environmentConfiguration loader.
Verified no other boolean values handled incorrectly.
Also found bug in epoch query (needs a version factory to handle global_slot_since_genesis vs. _since_hard_fork).
Minor cleanup - don't import * from database providers, be explicit.
Don't pass some config value as param when most are read straight from config - simplified interface to db factory.
Refactored databaseFactory.ts to simplify some redundancy.
Added guard on staking-ledgers route to return 400 if no key provided when querying. (It was just returning empty results which can be confusing.)

Tested locally, will define more interfaces later....forcing merge.


fix initial value cron value in applications

Describe your changes:

I worked on fixinf initial value cron value in applications while installing and editing them.

Issue :
https://github.com/open-metadata/OpenMetadata/assets/66266464/9dbf21f9-d130-4665-b520-d2e57ae7e1fb
Resolved :
https://github.com/open-metadata/OpenMetadata/assets/66266464/4d381db9-a859-47cd-aad0-94e98ac14a26
https://github.com/open-metadata/OpenMetadata/assets/66266464/6bff08e4-5a18-4439-a351-13d640c5c5a1
https://github.com/open-metadata/OpenMetadata/assets/66266464/eb15a961-d3e2-4a1a-878c-2197abda785b

Type of change:

[x] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@Ashish8689 , can you check why we don't have the week option as the selected one?


DoAfter Refactor

About the PR
Requires https://github.com/space-wizards/RobustToolbox/pull/3662
Fixes https://github.com/space-wizards/space-station-14/issues/3088
Fixes https://github.com/space-wizards/space-station-14/issues/6132
Huge refactor to the DoAfter system so it's now in shared and can work with prediction.
Cleanup was done on most classes that had a doafter to remove references to Owner and obsolete references.
Plus a Tool Refactor was done.

[X] Move client and server into shared
[x] Merge ClientDoAfter into DoAfter
[x] Network/Prediction
[x] Unify Events
[x] Consolidate CancellationTokens
[x] Obsolete DoAfter methods, move them to DoAfterSystem
[x] Refactor DoAfterEventArgs
[x] Dynamic cancel events (repeated clicks do nothing vs 2nd click cancels)
[x] Remove references to old events

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

This makes it possible to mine multiple rocks at the same time with a single pickaxe. Is that an intended change?
Current behavior is that you can mine one rock at a time per hand/pickaxe, so 2 rocks at once if you dual wield.

This makes it possible to mine multiple rocks at the same time with a single pickaxe. Is that an intended change?
Current behavior is that you can mine one rock at a time per hand/pickaxe, so 2 rocks at once if you dual wield.

that was added in a separate pr

This makes it possible to mine multiple rocks at the same time with a single pickaxe. Is that an intended change?
Current behavior is that you can mine one rock at a time per hand/pickaxe, so 2 rocks at once if you dual wield.

that was added in a separate pr, i believe?

I don't think so. I tested on both master and this PR branch.
Master: One rock at a time per pickaxe.
PR: Multiple rocks at the same time with a single pickaxe.


doc: Add a note on scalers which support float target value

Signed-off-by: Jorge Turrado<EMAIL_ADDRESS>After merging the PR to support mili unit in core, there are some scalers that support float as target value (because the scaler logic already supported float64 and it made sense).
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)

Related https://github.com/kedacore/keda/issues/3135

As an end-user, how much do I care about this? If I do, might need some more background on what this means maybe? Scaler typically does the heavy lifting on this and in some scalers this does not make sense - For example, I won't be scaling for 30.5 messages.
Maybe it's better to update the scalers where this is useful?

you are right, on it

They do support it, but does it make sense? :D Anyway it's up to them but for SB it's less relevant

Yes, the scalers inclued in this PR support float because it's relevant.
I mean, you can get a rate from 0 to 1 using Azure Monitor, or database scalers, etc.
The only case where could not be relevant is RabbitMQ using queues, but there is a remark explaining that this only applies in case of message rate

@zroubalik , does this match with your expectations too?


Remove deprecated methods.

Removed ShopBuyableException.
Cleaned up canPurchase implementations in the process (no longer throw/catch exceptions there).
Use config API for WeightShippingModifier. Removed static setter.
Fixed tests to no longer use deprecated methods.

@markguinn What do you think? We should be fine to remove the parts that were marked as deprecated for 2.0, right?

Yeah I think that's great. I also love to see those docblocks getting healthier. Thanks!


Allow zero-padding components of UrlTemplateImageryProvider.

Some Image services provide imagery with components that require padding x,y,z values with zeros. For example:
/my/example/server/{z}/{y}/{y}_{x}.PNG
with values of x y and z of 1, 2, 3 comes out as:
/my/example/server/3/2/2_1.PNG
But the images are actually at the path:
/my/example/server/3/0002/0002_0001.PNG
This addition allow a user to optionally supply the padding for each component.

Thanks for the contribution, @dwhipps!  Looks like a nice improvement.  Can you please update CHANGES.md so users know about it?
@kring do you have time to review this?

Thanks @dwhipps, looks great!  I think in the future we might want to be able to put the padding in the url, for example {x:4}, but this is more complicated and needs more thought, and there's a clear path to get from this PR to something like that without breaking compatibility, so I'm happy to merge this as it is.

Hey. Thanks for updating CHANGES for me. I've been ill for a few days. @kring, I considered adding the padding directly to the URL, but thought that the simplicity of both implementation and usage of this additional parameter outweighed the beauty of that solution. Thanks all!


Opening a port

Nice script. Worked flawlessly for me.
Can you advise how I would open up a port for torrent access please?
thanks

Setting up transmission I need to select an open port to allow traffic through. So I would like to open a specific port on the server for this purpose.
Daniel

When you connect to the openvpn server set up by this script, then you're behind NAT and you have to use iptables to forward the port on the server machine. If then the server is also behind NAT, port forward that also on the router.
Another approach is configuring the openvpn server with a TAP interface ( aka bridge setup ) so the connected client gets a IP on the server's private network and so just port forward on the router next. ( I'm talking about router because I'm assuming that the openvpn server is behind NAT, so on a home LAN otherwise with a public IP it's not necessary ).

@Angristan actually it happens on many softwares that you have to open ports just to improve speed, as it's optional by default and not necessary like you said.

The servers on a public network.  I'm having trouble with the tables. I tried this example where <IP_ADDRESS> is the public network, but the 6688 still showed as closed at the client. Maybe the example is wrong or do I need to apply something. I've used UFW, but not done much with iptables. Any help appreciated.
iptables -A PREROUTING -t nat -i ens3 -p tcp --dport 6688 -j DNAT --to <IP_ADDRESS>:6688
iptables -A FORWARD -p tcp -d <IP_ADDRESS> --dport 6688 -j ACCEPT

I can't test it, but here's what I've found:
try first answer + its comments from https://serverfault.com/questions/834566/port-forwarding-with-openvpn.
Or the first answer from https://unix.stackexchange.com/questions/55791/port-forward-to-vpn-client.
After changing, flush iptables and list the rules to make sure they're active.
BTW, it seems to me that in the rules you just pasted the first one has --to <IP_ADDRESS>:6688 instead the openvpn client ip --to 10.8.0.x:6688. Maybe that's why it doesn't work.

@cezar97 thanks :) correct rules were as you said (x.x.x.x is public and <IP_ADDRESS> is the client VPN address)
iptables -A PREROUTING -t nat -i ens3 -p tcp --dport 6688 -j DNAT --to <IP_ADDRESS>:6688
iptables -A FORWARD -p tcp -d x.x.x.x --dport 6688 -j ACCEPT

It would be really cool if this was added as an option on the menu

Just a quick question. How do I make these rules persistent. I see you have the rules in /etc/iptables/iptable.rules. I tried iptables-save, but that didn't work. thanks

To make it persistent once everything works do iptables-save > /etc/iptables/iptables.rules.

It would be really cool if this was added as an option on the menu.

I'll consider this when I'm going to have more free time. At the moment we had a lot of requests of tweaks like this one.

hello could you add to your script the ban of ping following the example of these rules iptables -A INPUT -p icmp --icmp-type echo-request -j DROP
iptables -A INPUT -i eth0 -p icmp --icmp-type echo-request -j DROP


Add resources for Mainz, Germany, Europe

Thanks @moschlar 👍
I merged just the first part in 44ea21e3


Install TagBot as a GitHub Action

You're receiving this pull request because the now-deprecated Julia TagBot GitHub App is installed for this repository. This pull request installs TagBot as a GitHub Action.
If this PR does not belong in this repository for any reason, feel free to close it.
See this Discourse thread for more details and to ask questions.
Please do not comment on this pull request, because it is unlikely that I (@christopher-dG) will see it.

Codecov Report

Merging #27 into master will increase coverage by 0.78%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #27      +/-   ##
=======================================
+ Coverage   74.21%   75%   +0.78%
=======================================
  Files          16    16
  Lines         698   720      +22
=======================================
+ Hits          518   540      +22
  Misses        180   180

Impacted Files
Coverage Δ

src/multi_indices.jl
100% <0%> (ø)
:arrow_up:

src/scalar_product.jl
97.91% <0%> (+0.04%)
:arrow_up:

src/quadrature_rules.jl
98.91% <0%> (+0.11%)
:arrow_up:

src/stieltjes.jl
98.68% <0%> (+0.15%)
:arrow_up:

src/evaluate.jl
61.53% <0%> (+2.07%)
:arrow_up:

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 4a23ed9...2ce7aef. Read the comment docs.


Updated conditions to retrieve primary keys in bulk_create() docs.

… primary key
I rewrote the documentation as part of the feedback given in #17507

@simkimsia Thanks :+1: Welcome aboard :boat:


error assigning object to object[key]

Sure that's a bug or something related to restricted keywords
const myList = {}
const id="anyId"

myList[id] = {
          itemsQty: 0,
          subTotal: 0,
          xsubTotal: 0,
          total: 0,
        }

and displaying that right after the assignment:

                         itemsQty: 1
                         subTotal: NaN
                         total: NaN
                         xsubTotal: 0

Any reason those NaN ?
Thanks!
================================
UPDATE:
Just wondering, if I set:
{
          itemsQty: 0,
          xSubTotal: 0,
          subTotal: 0,
          x: 0,
          xTotal: 0,
          total: 0,
          xxSubtotal: 0,
        }

the log:
itemsQty: 1
subTotal: 0
total: 0
x: 0
xSubTotal: NaN
xTotal: NaN
xxSubtotal: 0

================================
UPDATE #2
Assigning right the same value to a var like:
const x = { ... } works fine
but myList[anyValue] = { ...} still produces the same error
version: Nuxt 2.15.8
nodejs: ver 14.x and 16.x

@danielroe
Daniel:
Weird issue cause even one line is after another it seems the console is displaying a value that gets much later.
Disregard the issue so far.
I will continue my research and re-open it in case of being able to replicate it.
Thanks for your super fast response.
Regards.


Added autointerceptor

Why
Running ev.auto() will automatically intercept all fetch() requests to endpoints at the same host and encrypt them.
How
Describe how you've approached the problem

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Delete command and retweeting your own tweets

In birdknife the /delete command either deletes your tweet or tries to removes the retweet if it's from another user.
Now that you can retweet your own tweets, what do we do with a retweet of your own tweet?
Introduce something like /unretweet?

Current behavior: Retweets of your own retweet just get unretweeted and not deleted.
I think that's expected behavior.


Current retry messages logic is conflicting with usage of prefetch_count setting

By its nature, RabbitMQ's prefetch_count setting limits the number of messages sent to a worker at a given time. To release consumed message and receive a new one, a worker should acknowledge consumed message first.
This conflicts with the implementation of "retry" logic. Because messages scheduled for a retry are delayed from being redelivered using JS's setTimeout(), workers acknowledge them only after the timeout.
Thus, when a worker is waiting on more retry messages than prefetch_count setting, a worker will receive no new messages.
Example: prefetch count 3, 5 messages scheduled for a retry, 32 new messages are not processed.

Known approaches to this problem.

Completly change mechanism of delaying message redelivery for "retry messages". It's possible to utilize dead letter exchange expiration property simulate desired functionality. Unfortunately, this means using dead letter concept against its original design.

Update on approach 2.
RabbitMQ documentation does not specify if it's possible to update prefetch count property on live channels.
After series of manual experiments, I discovered that even though it's possible to do that, this change won't affect existing consumers listening on this channel. See the picture below: the consumer has prefetch count 2, even though its channel has prefetch count 5.

I also experimented to see if this is actually true and not just UI issue. And it is true. Even after updating channel's prefetch count to 5, consumer still is grouping requests by 2:

This means that updating prefetch count on consumer would mean we would need to cancel it and start it again. This would be a really bad idea, as it introduces new potential points of failure to the code and increases its complexity drastically.

The original article I linked for the dead letter exchange approach now has an update:
https://felipeelias.github.io/rabbitmq/2016/02/22/rabbitmq-exponential-backoff.html

Update: As pointed out in the comments by Bryan, you should consider whether the TTL times you’ll need are not very long, since per-message TTL have some caveats. The messages get expired only when they hit the head of the queue. For example, if you have a message with 1h TTL on the head of the queue, messages after that will expire only after the one in the head is.

More info: https://jack-vanlightly.com/blog/2017/3/24/rabbitmq-delayed-retry-approaches-that-work

Retries in Redis: saving messages flowchart.

Retries in Redis screenshot:


Delete package-lock.json

This PR contains a:

[ ] bugfix
[ ] new feature
[ ] code refactor
[ ] test update
[ ] typo fix
[x] metadata update

Motivation / Use-Case

This cannot be published along with the package to NPM, so its existence causes version inconsistencies between its authors/CI and its consumers.
Breaking Changes

None.
Additional Info

@evilebottnawi only for authors, which prevents them from experiencing what the consumers will experience. If you need hard versions, don't use ranges, but then no automatic security updates.

@stevenvachon use dep bots for updating, lock file is good practice, so no need to remove this file

Closing as package-lock.json is needed and large libraries include theirs (see: babel, yarn, webpack)


Add vox models for Min

Update vox models for Min

The last change "Update vox models for Min" is with the right way to name the files


"File name too long" error for file locks

Describe the bug
Getting the following error when calling load_dataset("gar1t/test"):
OSError: [Errno 36] File name too long: '<user>/.cache/huggingface/datasets/_home_garrett_.cache_huggingface_datasets_csv_test-7c856aea083a7043_0.0.0_9144e0a4e8435090117cea53e6c7537173ef2304525df4a077c435d8ee7828ff.incomplete.lock'

Steps to reproduce the bug
Where the user cache dir (e.g. ~/.cache) is on a file system that limits filenames to 255 chars (e.g. ext4):
from datasets import load_dataset
load_dataset("gar1t/test")

Expected results
Expect the function to return without an error.
Actual results
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<python_venv>/lib/python3.9/site-packages/datasets/load.py", line 1112, in load_dataset
    builder_instance.download_and_prepare(
  File "<python_venv>/lib/python3.9/site-packages/datasets/builder.py", line 644, in download_and_prepare
    self._save_info()
  File "<python_venv>/lib/python3.9/site-packages/datasets/builder.py", line 765, in _save_info
    with FileLock(lock_path):
  File "<python_venv>/lib/python3.9/site-packages/datasets/utils/filelock.py", line 323, in __enter__
    self.acquire()
  File "<python_venv>/lib/python3.9/site-packages/datasets/utils/filelock.py", line 272, in acquire
    self._acquire()
  File "<python_venv>/lib/python3.9/site-packages/datasets/utils/filelock.py", line 403, in _acquire
    fd = os.open(self._lock_file, open_mode)
OSError: [Errno 36] File name too long: '<user>/.cache/huggingface/datasets/_home_garrett_.cache_huggingface_datasets_csv_test-7c856aea083a7043_0.0.0_9144e0a4e8435090117cea53e6c7537173ef2304525df4a077c435d8ee7828ff.incomplete.lock'

Environment info

datasets version: 1.12.1
Platform: Linux-5.11.0-27-generic-x86_64-with-glibc2.31
Python version: 3.9.7
PyArrow version: 5.0.0

Hi, the filename here is less than 255
>>> len("_home_garrett_.cache_huggingface_datasets_csv_test-7c856aea083a7043_0.0.0_9144e0a4e8435090117cea53e6c7537173ef2304525df4a077c435d8ee7828ff.incomplete.lock")
154

so not sure why it's considered too long for your filesystem.
(also note that the lock files we use always have smaller filenames than 255)
https://github.com/huggingface/datasets/blob/5d1a9f1e3c6c495dc0610b459e39d2eb8893f152/src/datasets/utils/filelock.py#L135-L135

Yes, you're right! I need to get you more info here. Either there's something going with the name itself that the file system doesn't like (an encoding that blows up the name length??) or perhaps there's something with the path that's causing the entire string to  be used as a name. I haven't seen this on any system before and the Internet's not forthcoming with any info.

Hello @mariosasko
Has this fix shown up in the 2.10.1 version of huggingface datasets?

It looks like the issue is back with #6445 since the MAX_FILENAME_LENGTH is explicitly set to be 255 there
https://github.com/huggingface/datasets/blob/dd9044cdaabc1f9abce02c1b71bdb48fd3525d4e/src/datasets/utils/_filelock.py#L28

Ah good catch, I opened https://github.com/huggingface/datasets/pull/6482 with a quick fix


ci: close stale issues

:tada: This PR is included in version 3.1.1 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Add CpuFuture::forget() function.

CpuFuture::forget() consumes the future but does not cancel the computation.
Closes #293

Looks great to me, thanks!

Thanks!


Box2D setTransform angle not persisting

Issue details
When the angle of a Box2D Body is set using setTransform the angle does not persist when the call is not made. If the setTransform is not called the angle will snap back to 0, if setTransform is called every frame with the target angle set the body's rotation remains correct.
Click here for a short video demonstrating the bug (the texture won't rotate, only the box drawn by a Box2D debug render should). The snippet below is used to move the body to the target location on click.
Reproduction steps/code
targetPosition is a Vector2 and bodyPosition is equal to body.getPosition() .

// https://stackoverflow.com/a/23482465/3833743
Vector2 direction = targetPosition
    .sub(bodyPosition)
    .nor();

body.setTransform(bodyPosition, direction.angleRad());
body.setLinearVelocity(direction.scl(target.speed));

The desired state is that the body points to and move towards and the target position. The above snippet is run until the body arrives at the target location as which point the body remains at the location angle snaps to 0.
Version of LibGDX and/or relevant dependencies
libGDX: 1.9.10
Please select the affected platforms

[ ] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[ ] HTML/GWT
[ ] Windows
[x] Linux (Pop!_OS 20.04)
[ ] MacOS

Given the fact libgdx simply passes the transform to the underlying box2d native code, I'm not sure there's actually a bug here - it appears to just be how box2d works.

@MobiDevelop are there any plans to fix this bug and if not are there any other ways to set the rotation of a body?

(Applying Ockham's Razor I'd assume that the problem is in your code)
Can you add a minimal testcase that reproduces your issue?
Also, what exactly does your video show?
The body seems to rotate properly doesn't it?

@intrigus No, it does not rotate correctly. See how the body snaps at the end of travel. If setTransform is not called every frame the rotation defaults to 0.

for people facing this issue, setTransform should only be used to "teleport" bodies (rarely used).
In order to manually control position and/or rotation, you should use setLinearVelocity and/or setAngularVelocity instead.


ghost using SQLite despite env variables using Mysql

Probably linked to #176
Steps:

have docker
launch a ghost container using the demo setup:

services:

  ghost:
    image: ghost:1-alpine
    restart: always
    ports:
      - 8080:2368
    environment:
      # see https://docs.ghost.org/docs/config#section-running-ghost-with-config-env-variables
      database__client: mysql
      database__connection__host: db
      database__connection__user: root
      database__connection__password: example
      database__connection__database: ghost

  db:
    image: mysql:5.7
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: example```

note that ghost is still using SQLite instead of MySQL on run

Have you tried with Ghost 2?  Did the configuration parameters change between 1 and 2?

I can't reproduce
when starting the containers ghost will error and restart while mysql initializes
[2019-08-23 22:01:50] ERROR

NAME: RollbackError
CODE: ECONNREFUSED
MESSAGE: connect ECONNREFUSED <IP_ADDRESS>:3306

level:normal

OuterError: The server has encountered an error.
RollbackError: connect ECONNREFUSED <IP_ADDRESS>:3306
    at RollbackError.KnexMigrateError (/var/lib/ghost/versions/1.26.0/node_modules/knex-migrator/lib/errors.js:7:26)
    at new RollbackError (/var/lib/ghost/versions/1.26.0/node_modules/knex-migrator/lib/errors.js:32:26)
    at /var/lib/ghost/versions/1.26.0/node_modules/knex-migrator/lib/index.js:212:23
    at tryCatcher (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/promise.js:689:18)
    at Async._drainQueue (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:810:20)
    at tryOnImmediate (timers.js:768:5)
    at processImmediate [as _immediateCallback] (timers.js:745:5)

Error: connect ECONNREFUSED <IP_ADDRESS>:3306
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
    --------------------
    at Protocol._enqueue (/var/lib/ghost/versions/1.26.0/node_modules/mysql/lib/protocol/Protocol.js:145:48)
    at Protocol.handshake (/var/lib/ghost/versions/1.26.0/node_modules/mysql/lib/protocol/Protocol.js:52:23)
    at Connection.connect (/var/lib/ghost/versions/1.26.0/node_modules/mysql/lib/Connection.js:130:18)
    at /var/lib/ghost/versions/1.26.0/node_modules/knex/lib/dialects/mysql/index.js:109:18
    at Promise._execute (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/debuggability.js:303:9)
    at Promise._resolveFromExecutor (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/promise.js:483:18)
    at new Promise (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/promise.js:79:10)
    at Client_MySQL.acquireRawConnection (/var/lib/ghost/versions/1.26.0/node_modules/knex/lib/dialects/mysql/index.js:104:12)
    at create (/var/lib/ghost/versions/1.26.0/node_modules/knex/lib/client.js:283:23)
    at tryPromise (/var/lib/ghost/versions/1.26.0/node_modules/tarn/lib/Pool.js:366:22)
    at tryPromise (/var/lib/ghost/versions/1.26.0/node_modules/tarn/lib/utils.js:57:20)
    at Promise (/var/lib/ghost/versions/1.26.0/node_modules/tarn/lib/Pool.js:366:5)
    at Promise._execute (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/debuggability.js:303:9)
    at Promise._resolveFromExecutor (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/promise.js:483:18)
    at new Promise (/var/lib/ghost/versions/1.26.0/node_modules/bluebird/js/release/promise.js:79:10)
    at callbackOrPromise (/var/lib/ghost/versions/1.26.0/node_modules/tarn/lib/Pool.js:357:10)

Eventually ghost will establish a connection
[2019-08-23 22:02:26] INFO Creating table: posts
[2019-08-23 22:02:30] INFO Creating table: users
[2019-08-23 22:02:32] INFO Creating table: posts_authors
[2019-08-23 22:02:38] INFO Creating table: roles
[2019-08-23 22:02:40] INFO Creating table: roles_users
[2019-08-23 22:02:42] INFO Creating table: permissions
[2019-08-23 22:02:44] INFO Creating table: permissions_users
[2019-08-23 22:02:46] INFO Creating table: permissions_roles
[2019-08-23 22:02:48] INFO Creating table: permissions_apps
[2019-08-23 22:02:50] INFO Creating table: settings
[2019-08-23 22:02:52] INFO Creating table: tags
[2019-08-23 22:02:58] INFO Creating table: posts_tags
[2019-08-23 22:03:03] INFO Creating table: apps
[2019-08-23 22:03:07] INFO Creating table: app_settings
[2019-08-23 22:03:11] INFO Creating table: app_fields
[2019-08-23 22:03:15] INFO Creating table: clients
[2019-08-23 22:03:17] INFO Creating table: client_trusted_domains
[2019-08-23 22:03:21] INFO Creating table: accesstokens
[2019-08-23 22:03:30] INFO Creating table: refreshtokens
[2019-08-23 22:03:36] INFO Creating table: subscribers
[2019-08-23 22:03:38] INFO Creating table: invites
[2019-08-23 22:03:40] INFO Creating table: brute
[2019-08-23 22:03:40] INFO Creating table: webhooks
[2019-08-23 22:03:42] INFO Model: Tag
[2019-08-23 22:03:42] INFO Model: Client
[2019-08-23 22:03:42] INFO Model: Role
[2019-08-23 22:03:42] INFO Model: Permission
[2019-08-23 22:03:42] INFO Model: User
[2019-08-23 22:03:43] INFO Model: Post
[2019-08-23 22:03:45] INFO Relation: Role to Permission
[2019-08-23 22:03:46] INFO Relation: Post to Tag
[2019-08-23 22:03:46] INFO Relation: User to Role
[2019-08-23 22:03:46] INFO Finished database migration!
[2019-08-23 22:03:50] WARN Theme's file locales/en.json not found.
[2019-08-23 22:03:50] INFO Ghost is running in production...
[2019-08-23 22:03:50] INFO Your blog is now available on http://localh
[2019-08-23 22:03:50] INFO Ctrl+C to shut down
[2019-08-23 22:03:50] INFO Ghost boot 3.521s

Verifying the data is in the mysql container
$ docker exec -it ghost_db_1 mysql -pexample

mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 34
Server version: 5.7.26 MySQL Community Server (GPL)

Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> USE ghost;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show tables;
+------------------------+
| Tables_in_ghost        |
+------------------------+
| accesstokens           |
| app_fields             |
| app_settings           |
| apps                   |
| brute                  |
| client_trusted_domains |
| clients                |
| invites                |
| migrations             |
| migrations_lock        |
| permissions            |
| permissions_apps       |
| permissions_roles      |
| permissions_users      |
| posts                  |
| posts_authors          |
| posts_tags             |
| refreshtokens          |
| roles                  |
| roles_users            |
| settings               |
| subscribers            |
| tags                   |
| users                  |
| webhooks               |
+------------------------+
25 rows in set (0.00 sec)

weird. I've tried with 1 and 2, both still use SQlite...
I'll look into it tomorrow

Closing since this appears to be resolved and/or environmental.
For further help, I'd suggest trying the Docker Community Forums, the Docker Community Slack, or Stack Overflow.

Same issue here, though oddly enough the database is created and the tables are populated appropriately. Head scratch Not sure why this appears to be working...


Cilium native hostport: an empty hostIP or a <IP_ADDRESS> hostIP behaves differently than CNI portmap

Is there an existing issue for this?

[X] I have searched the existing issues

Version
equal or higher than v1.14.13 and lower than v1.15.0
What happened?
This is a follow up of https://github.com/cilium/cilium/issues/12116 (Cilium native hostport only listens on a internal IP, unlike CNI portmap ).
Lately we came across a few issues when using Cilium native hostport in conjunction with passthrough load balancer. The traffic path is follow:
pass through LB -> k8s_nodes:hostport -> pods with hostport

When the LB packets hit the kubernetes node, it tends to come with the LB IP as the destination. The LB IP may or may not be attached to the node's interface. What we are observing is that Cilium hostport failed to forward such traffic into the corresponding pods. This didn't work even when we gave an empty hostIP or a <IP_ADDRESS> hostIP and it seems Cilium only serves hostport on known IPs.
This can be worked around by explicitly setting the LB IP as a hostIP along with the hostPort, but the question here is why a <IP_ADDRESS> hostIP is not taking effect despite Cilium listed that as a serving IP? e.g.:
# cilium service list | grep -i "hostport"
15   <IP_ADDRESS>:60000    HostPort       1 => <IP_ADDRESS>:60000 (active)
16   <IP_ADDRESS>:60000        HostPort       1 => <IP_ADDRESS>:60000 (active)

Notably this behaves differently than the containernetworking portmap CNI: https://www.cni.dev/plugins/current/meta/portmap/, where an empty hostIP or <IP_ADDRESS> hostIP results in an iptables rule that forwards any packet matching the hostport regardless of the destination IP. Something like:
-p tcp --dport 8043 -j DNAT --to-destination <IP_ADDRESS>:443

cc @zuzzas @jingyuanliang
How can we reproduce the issue?
My repro is with GCP where I can set up a passthrough load balancer (https://cloud.google.com/load-balancing/docs/passthrough-network-load-balancer) on a GKE DPv2 cluster (https://cloud.google.com/kubernetes-engine/docs/concepts/dataplane-v2). This however isn't really cloud-specific.
Cilium Version
1.14.13
Kernel Version
6.1.100+
Kubernetes Version
v1.31.0
Regression
No response
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Cilium Users Document

[X] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Tested and verified that the issue also exists in Cilium 1.16.1 without GKE modifications (Google-internal: sponge 30eabc67-71bb-4250-8885-9b52837459c2)

Same here. Tested and verified that the issue also exists in Cilium 1.16.3
I have multiple IPv6 addresses and I want to listen [::]:80, but cilium only reply on internal-ips and external-ips


Pinecone in docs is outdated

Pinecone default environment was recently changed from us-west1-gcp to us-east1-gcp (see here), so new users following the docs here will hit an error when initializing.
Submitted #898

issue solved


Update JoyStick Page UI

Note: This issue is reserved for SLoP Contributors.
Color Values
#FFFFFF
#DC143C
#DC143C: 35% Opacity
#DC143C: 52% Opacity

Can I work on this? I am done with my last task.

Wait for #10 and #11 to get merged.

@ritvij14  Okay, you can take this up.


Fix CI tests

Copies CI test setup from ApproximateGPs

Looks like the Window's runner doesn't have enough memory. I wonder whether the ubuntu failures are also caused by out-of-memory problems?

The last commit is showing up on the branch but not on this pr somehow?

The last commit is showing up on the branch but not on this pr somehow?

Maybe you need to rebase onto master? My git knowledge is bad. Either way, I wouldn't worry about it.


Retrieving Ghost Location also retrieves ID

The API to retrieve a Ghost's location also returns the Ghost's ID, which was used in the request.
This should be changed to simply return a location without the ID. The associated tests should be modified, and the wiki should also be updated.
The resultant response body should be in this form:
{
    "latitude" : 123.321,
    "longitude" : 321.123
}

Resolved in above-referenced merge.


Nopolygon

Getting rid of Polygon dependency

Created functions to compute area and barycenter of polygons
Updated conda recipe
Updated pip formula

Extra

Accelerated Poly_isClockwise

Issues resolved
Fixes #23

Codecov Report

Merging #169 into devel will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##            devel    #169      +/-   ##
=========================================
+ Coverage   45.17%   45.2%   +0.03%
=========================================
  Files          70      70
  Lines       20612   20624      +12
=========================================
+ Hits         9311    9323      +12
  Misses      11301   11301

Impacted Files
Coverage Δ

tofu/geom/_comp.py
60.04% <100%> (-0.35%)
:arrow_down:

tofu/tests/tests01_geom/tests03_core.py
89.87% <0%> (+0.23%)
:arrow_up:

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 f386f84...615b3a6. Read the comment docs.


memorySize is limited to 512MB

wskdeploy limits memory size to 512mb. To me, it is unclear why that is. I'd propose raising those limits, OpenWhisk (at least on IBM) supports up to 2048MB limits

Hmm, ok, according to the documentation, the memory limit is still 512MB https://github.com/apache/incubator-openwhisk/blob/master/docs/reference.md

hmm, @rabbah shed some light on the issue: "openwhisk operators can configure these limits at deployment time". Makes me wonder if more than 512MB should be allowed here. Right now the setting is just ignored. The warning is only shown when deploying with -v (verbose) and then there's so much output that it's very hard to notice...
Could we instead show a warning and still use the setting? What would this mean if the setting is actually invalid for the provider?

I haven’t looked at the implementation here but any hard coding of limits in the wskdeploy client is a bug in my opinion and should be read from the api host which provides them.
There is an issue I opened related to the runtime kinds for example which bit me sometime ago.

According to my recollection, wskdeploy itself imposes no limits on memory (or other size); thanks for referencing the docs/other issue.

Why is this closed?

Just because the PR was merged, bu the underlying issue (hard coding client-side vs reading from api host) still remains, I guess. Updated the title accordingly

the API (such as https://openwhisk.ng.bluemix.net/) returns the memory size limit as "limits.max_action_memory", this can be used accordingly I'd say


protonvpn-gui: 4.7.3 -> 4.7.4; proton-vpn-api-core: 0.36.4 -> 0.36.6; proton-vpn-network-manager: 0.9.4 -> 0.9.7

Updated the packages to the latest version and checked that everything is working as expected.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 356720

x86_64-linux

:white_check_mark: 10 packages built:

protonvpn-gui
protonvpn-gui.dist
python311Packages.proton-vpn-api-core
python311Packages.proton-vpn-api-core.dist
python311Packages.proton-vpn-network-manager
python311Packages.proton-vpn-network-manager.dist
python312Packages.proton-vpn-api-core
python312Packages.proton-vpn-api-core.dist
python312Packages.proton-vpn-network-manager
python312Packages.proton-vpn-network-manager.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 356720

x86_64-linux

:white_check_mark: 10 packages built:

protonvpn-gui
protonvpn-gui.dist
python311Packages.proton-vpn-api-core
python311Packages.proton-vpn-api-core.dist
python311Packages.proton-vpn-network-manager
python311Packages.proton-vpn-network-manager.dist
python312Packages.proton-vpn-api-core
python312Packages.proton-vpn-api-core.dist
python312Packages.proton-vpn-network-manager
python312Packages.proton-vpn-network-manager.dist

aarch64-linux

:white_check_mark: 10 packages built:

protonvpn-gui
protonvpn-gui.dist
python311Packages.proton-vpn-api-core
python311Packages.proton-vpn-api-core.dist
python311Packages.proton-vpn-network-manager
python311Packages.proton-vpn-network-manager.dist
python312Packages.proton-vpn-api-core
python312Packages.proton-vpn-api-core.dist
python312Packages.proton-vpn-network-manager
python312Packages.proton-vpn-network-manager.dist

x86_64-darwin

:fast_forward: 4 packages marked as broken and skipped:

python311Packages.proton-vpn-network-manager
python311Packages.proton-vpn-network-manager.dist
python312Packages.proton-vpn-network-manager
python312Packages.proton-vpn-network-manager.dist

:x: 4 packages failed to build:

python311Packages.proton-vpn-api-core
python311Packages.proton-vpn-api-core.dist
python312Packages.proton-vpn-api-core
python312Packages.proton-vpn-api-core.dist

aarch64-darwin

:fast_forward: 4 packages marked as broken and skipped:

python311Packages.proton-vpn-network-manager
python311Packages.proton-vpn-network-manager.dist
python312Packages.proton-vpn-network-manager
python312Packages.proton-vpn-network-manager.dist

:x: 4 packages failed to build:

python311Packages.proton-vpn-api-core
python311Packages.proton-vpn-api-core.dist
python312Packages.proton-vpn-api-core
python312Packages.proton-vpn-api-core.dist


c-api

do you want to participate in our c-api?
ngn and i designed an api, that could be implemented by any k backend.
then extension libraries can be shared unmodified across any k implementation (written in c at least).
As your k is still young, you could implement the api directly and use the syntax internally (our K type being a struct is no problem).
Otherwise you could write glue code (as ngn and i have to do).

definitely. i have seen your conversation with ngn on the k tree about the api, i will take a closer look. the point of this project is for my own learning, so the fact i'm not sure what's involved for me here is a good reason to participate


add azure ai data document loader

This PR adds an "Azure AI data" document loader, which allows Azure AI users to load their registered data assets as a document object in langchain.

updated to add lazy loading support, let me know if it looks good to you @samuel100!


Reuse variable as dict key

This commit removes a minor redundancy in the code by reusing a variable as dictionary key.

Thank you!


drivers: gpio: gecko: GPIO driver ignores pull-up/pull-down settings

Fixes #4395.
Coverity-ID: 178059
Signed-off-by: Leandro Pereira<EMAIL_ADDRESS>

@chrta, I'm unfamiliar with the Gecko platform; since you wrote the driver, could you please take a look at this patch?

This looks good, thanks for fixing this bug.


LeaderBoard data generation

How is the evaluation data for the leaderboard obtained? Could you please provide some detailed explanations?

Checkout this section of the leaderboard blog!


Extend the tracing capabilities to set a span's status

Currently, all collected spans provides a status attribute which is set to Status.OK.
This status attribute will be used by certain tracing backend systems for e.g. visualization or grouping of collected spans.
In this ticket, the ability should be implemented to assign a custom status to a span.
Using OpenCensus, a span's status is set as following:
span.setStatus(Status.NOT_FOUND.withDescription("Cache miss"))

It should be able to set the status using a constant value or dynamically via the data context.

I would suggest that we start with only error / success status, to keep it simple for now.
This is sufficient to visualize the errornous spans in the tracing backends, details liek the http status or error messages can already be added as attributes to spans.
I would suggest the following configuration approach:
my_rule:
  tracing:
    error-status: my_data_key

When the instrumented method finishes, the given data key is read and "interpreted" as error status. This means, if the value is neith null nor false, the span is marked with the OpenCensus UNKOWN status code, which seems to be the general purpose one.
Why null or false? I have the following two use-cases in mind:
first_rule:
  tracing:
    error-status: _thrown
second_rule:
  tracing:
    error-status: is_error

The first rule most-likely is the 99% case: make the span as an error, if any exception was thrown.
The second rule is for special stuff, such as http: here we can derive the is_error booelan for example from the http_status code and therefore mark the span accordingly.


Add convenience functions for diatomic molecules

Related to NQCD/DiatomicBasics#1.
Add center of distance, mass, center of mass, velocity and variants correcting for periodic boundary conditions into NQCBase somewhere. (Probably best as a sub package to avoid blocking common function names such as distance)

Included here instead: https://github.com/NQCD/NQCDynamics.jl/issues/317


Update or reformat the Blue Waters guide

This repository's issues are reserved for feature requests, and bug reports, and questions.
I'm submitting a ...

[ ] bug report
[x] feature request
[ ] question

Expected Behavior
As our group expands to a variety of super computers, the guide for Blue Waters could have general information about applying to super computers reflecting the drafts in our drive. It could answer questions like:

How do you figure out the amount of compute time you'll need?
What are the steps to identify the type of machine you want to work with?
Are there any existing resources we can/want to link to about adapting code for a super computer?

Actual Behavior
This doesn't yet exist.
Steps to Reproduce the Problem

Check out the Blue Waters guide

How can this issue be closed?
This issue can be closed with a PR that either creates a new guide about generally applying for compute time on a super computer, or adds information to the existing Blue Waters guide.

Closing because of #215


Indexing web apps. Closes #11

Added a listener for any history state changes. onCommited is still needed as this onHistoryStateUpdated does not detect first loads of the page (if website is not a web app).

@urbancvek I think onHistoryStateUpdated is not suitable here.
When testing, I run into a few problems:

It leads to multiple indexing of the same url
On youtube and facebook, every reload/switch to another page is indexed twice and sometimes even the wrong page is indexed. On youtube i actually switched to other videos in the same tab but it still only took the original one and duplicated the entries.
Screenshot:

Back then, when I implemented the web-apps support, the only real option to use was onUpdated https://github.com/WorldBrain/Research-Engine/blob/master/src/js/get_tab.js.
This way all reloads in the same tab won't be indexed (which is actually good to remove duplicates) and I could catch every event of change of URLs properly.
I tried it with onHistoryStateUpdated back then as well, but it didnt work.
I suggest trying it out with the way it is done in the old extension.

I've used onUpdated. Checking for status: "complete" is not needed because the code that analyses the page already waits for page to load. The only problem I found is on web apps that are doing some weird redirects. It would be very hard to detect duplicates there as the urls are different and even the status is set to complete even though it's clearly not because it then redirects the page.  Youtube does this for example: when clicking on a channel first url is something like /channel/3291987312 and then it redirects to a user friendly version of it in the likes of /channel/shakiraVEVO. We might be able to use some function that debounces for 100-200ms as the redirects happen at the same time.

Is this ready to be merged into master?

Not much to say on this, the problem would be in the algorithm to check if a page is always the same.
About the debouncer, even 10 seconds. Do we care about saving a page the user decided to spend less than 10 seconds on?

Yep we could definitely use something like this and it's a fairly simple fix. I also agree with filtering out the websites user spent so little time on. This may even have some benefits beside solving this issue of indexing web apps (not polluting the history with this data).
I can implement it if we decide it's a good solution.

I can implement it if we decide it's a good solution.
+1

@urbancvek If you add the last commit with waiting 10 seconds, then we are good to go with that PR! :)

@urbancvek How's things going with this PR? If everything's working functionality-wise, it would be great to revisit it one last time and get it merged in. Obviously things have gotten a bit messy with the merges and the rebasing happening on master, so let me know (on slack or wherever) if you have some time and we can work through cleaning up the branch together :)

I've created a new PR here #32.

This PR was sorted out in (merged) PR #32. Closing now


Unknown version '0.7.0-beta.6' - Mac.

running any dfx command inside any example directory throws this error:
Warning: The version of DFX used (0.7.0-beta.6) is different than the version being run (0.6.26).
This might happen because your dfx.json specifies an older version, or DFX_VERSION is set in your environment.
We are forwarding the command line to the old version. To disable this warning, set the DFX_WARNING=-version_check environment variable.

Error when trying to forward to project dfx:
Unknown version '0.7.0-beta.6'.
Installed executable: 0.6.26

Is there a command line to downgrade to a different version of the SDK?

I'm getting the same issue on ubuntu. I think '0.7.0' might only be released internally, '0.6.26' seems to be the latest available version at the moment.

Experiencing the same on Mac. How do we downgrade to the supported '0.6.26' version. Than

Resolved by dfxvm


User/ole

:white_check_mark: Build TheIdServer 4.7.1-user-ole1-0050 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/bc6bf2b13e by @aguacongas)

:white_check_mark: Build TheIdServer 4.7.1-user-ole1-0051 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/e582a75f95 by @)

:white_check_mark: Build TheIdServer 4.7.1-user-ole1-0052 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/86dfb5e79f by @)


microsoft.graph.sharedChanged not returned in certain condition.

Steps To Reproduce

Get The latest delta token for the user with Prefer: hierarchicalsharing and Prefer: deltashowsharingchanges
Create a folder with no sharing on the folder or any of its parent
Add a user with direct access to the the folder
Fetch the latest changes for the user using delta changes with Prefer: hierarchicalsharing and Prefer: deltashowsharingchanges. The drive item returned has @microsoft.graph.sharedChanged set to true
Remove the direct access for the user from the folder
Fetch the latest changes for the user using delta changes

The drive item returned in the step 6 @microsoft.graph.sharedChanged is not returned.
Expected behavior
The drive item returned in the step 6, should have  @microsoft.graph.sharedChanged set to true

@chackman @JeremyKelley Would you need any info from my side? Also is there any recommended alternatives? or any additional flags to be sent for getting this info?

Is there a plan to fix this? The whole sharing headers thing is useless due to this bug, and this bug is almost a year old now.
@chackman @JeremyKelley
I have run into the same bug when using these Prefer headers:
deltashowsharingchanges, deltashowremovedasdeleted, deltatraversepermissiongaps

Hi @JeremyKelley following our talk, This could help us out as well!
Any plan of handling this issue?
Thanks!

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


bigDiffy comparison between natively partitioned BigQuery tables

Currently, bigDiffy does not seem to support comparing natively partitioned BigQuery tables. I ran bigDiffy with $<partition>-decorated BQ tables on the rhs and lhs. The $partition argument was not retained in the arguments to the Dataflow job.
The job did not read any input records (according to the job graph) and failed after 15 minutes with NullPointerException messages (not 100% sure if the null pointers are related to the native partitioning).
FYI @catherinejelder

@catherinejelder my instinct is to set this up to work automatically for inputs with a $partition decorator without specifying any additional arguments.
the updates should be incorporated here. I believe this method is not currently tested. is that accurate? or am I missing it somewhere? just want to adhere to existing approach if there is a test for this method currently.

@idreeskhan can you link the merged PR and close this issue? I don't have permissions to link the PR


Missing universes in SMT encoding

In #3644, Guido thankfully pointed me to the old discussion #2069 about missing universe instantiations in the SMT encoding.  Apparently, the most obvious way to encounter that issue was eliminated in #2205 by removing the axiom f x << f.
However, the underlying unsoundness due to missing universe instantiations is still present.  We can easily define a "predicate" is_univ_zero u#a which is true if and only if a is zero.  The SMT encoding of this predicate is clearly inconsistent if we omit the universe instantiation:
module MissingUniv
open FStar.Functions
open FStar.Cardinality.Universes

// is_univ_zero u#a  <==>  a == 0
let is_univ_zero = exists (f: Type u#a -> Type u#0). is_inj f

let is_univ_zero_zero () : Lemma (is_univ_zero u#0) =
  assert is_inj fun (t: Type u#0) -> t

let not_is_univ_zero_succ () : Lemma (~(is_univ_zero u#(a+1))) =
  introduce forall (f: Type u#(a+1) -> Type u#0). ~(is_inj f) with
  no_inj_universes u#0 u#(a+1) f

let _ : squash False =
  is_univ_zero_zero (); not_is_univ_zero_succ u#0 ()

A minimized version that might (or might not) be easier to digest:
module MissingUniv

let contradiction : squash False =
  assert Functions.is_inj (id #Type0);
  Classical.forall_intro (Cardinality.Universes.no_inj_universes u#0 u#(a+1))


Implement Handler::tick()

The Handler::tick() method is called at the beginning of each event
loop tick.
Fixes #219

Thanks! Merged

Nice!


Create service template with Ansible Tower after first creating a new job template

Create a new job_template in Ansible Tower
Run a refresh to generate the subsequent ConfigurationScript
https://www.pivotaltracker.com/story/show/137306185

@miq-bot add_label 'providers/ansible_tower', enhancement
@miq-bot assign @bzwei

-cc @gmcculloug, @bdunne

cc - @jntullo

@syncrou we also want to save config_info in service_template's options column. The main purpose is to save hosts, but it may be beneficial to save all info.

@miq-bot add_label wip

@miq-bot remove_label wip

@syncrou your last commit is not needed with the work done in #13822, instead you can call create_from_options - depending on which PR gets merged first 😃

@bzwei, @mkanoor, @bdunne, @gmcculloug - I believe I have applied all the requested changes.

@syncrou 👍 Thanks!

@bdunne @mkanoor Please take another look.


Add tests for #422 and #430

No text

Thanks for the test cases @Zache.

Can I ask you to write it.skip so I can merge safely without breaking continuous integration please?

Thanks @Zache.


Add k8s compatibility warnings to logs

enhance issue : https://github.com/kubernetes-sigs/descheduler/issues/1062
i have already test on my local kubernetes platform

Can we add a unit test for this? To make sure that we stay within the skew

also fix another log issue as below

@a7i  could you review and give me a /lgtm if possible?
i just back, and so sorry for my mom sick and i leave for one week ago.

can we move all the logic into its own function? when I look at the Run function code, I don't really need to go through all 20+ lines of code. But rather just see a call to "ensure k8s version compatibility"
Can we add a test for the new function?

Sorry to hear about that, hope all is well now!
What are your thoughts on the question above? i.e.

can we move all the logic into its own function? when I look at the Run function code, I don't really need to go through all 20+ lines of code. But rather just see a call to "ensure k8s version compatibility"

Can we add a test for the new function?

@a7i  i already separate a function, and i do test on local latop for real test done, see the picture as below(the first picture is k8s version 1.25, the second picture is k8s version1.22).  sorry for i don't see any testcase to cover the log in descheduler, maybe when the pr merge, could  you help to add test function for that?

/retest

/retest

/retest

/lgtm
Thank you, I will create a follow-up PR with the test


Services Library

ServiceManager can manage one or more services. One serviceManager can have another serviceManager instance as parent.
Service can be added to ServiceManager by ServiceManager#manage(service)
Services can have events that can be managed by ServiceManager trees
Services can be inherited and be used for different purposes (such as http calls)

Marking as done


Alternative data model

While I was investigating https://codesandbox.io/s/github/tannerlinsley/react-charts/tree/next/examples/stress-test?file=/src/index.js
I think one of the issues in regards to performance and memory usage, is current data model. While it is somehow easy to use (that is discussable tho), I personally prefer purely-array based solutions, with shared X-axis, in a majority of cases. This way there are no objects involved.
Current data model:
   const data = React.useMemo(
     () => [
       {
         label: 'Series 1',
         data: [
           { primary: 1, secondary: 10 },
           { primary: 2, secondary: 10 },
           { primary: 3, secondary: 10 },
         ],
       },
       {
         label: 'Series 2',
         data: [
           { primary: 1, secondary: 20 },
           { primary: 2, secondary: 20 },
           { primary: 3, secondary: 20 },
         ],
       },
       {
         label: 'Series 3',
         data: [
           { primary: 1, secondary: 30 },
           { primary: 2, secondary: 30 },
           { primary: 3, secondary: 30 },
         ],
       },
     ],
     []
   )

Alternative:
   const data = React.useMemo(
     () => [
       {
         label: 'Group A',
         common_primary: [1, 2, 3],
         series: [
         {
            label: 'Series 1',
            data: [10, 10, 10],  // secondary
         },
         {
            label: 'Series 2',
            data: [10, 10, 10],  // secondary
         },
         {
            label: 'Series 3',
            data: [10, 10, 10],  // secondary
         },
         ],
       },
     ],
     []
   )

The common_primary is just an example, but occurs often in practice.
For non-repeating primary, each series will have own primary array.
Also, it would be great if data could be other iterable or possibly also a typed array, instead of just array.
Unfortunately I don't know much about React, to try and experiment with this, and see the performance / memory benefits, but it is likely there are some. The iteration over two arrays for individual points, shouldn't be a problem, the cache usage at any given time should be the same, if not lower, and flat representation like proposed here, actually allows more JS VM optimizations.

Due to a massive overhaul and rewrite of React Charts to TypeScript and a massively upgraded public API, this issue is being bulk closed for triage. The latest version can be tested via the react-charts@beta tag. Documentation is in the process of being upgraded, but thankfully, everything is fully typed now, so you can explore the API that way for now.
If, after testing or playing with the v3 beta, you believe your issue is still not addressed or relevant, feel free to open a new issue.


Authentication not working in NWJS (node-webkit)

Version info
Angular: 6.0.3
Firebase: 5.0.4
AngularFire: 5.0.0-rc.11
Other (e.g. Ionic/Cordova, Node, browser, operating system): NWJS v0.30+
How to reproduce these conditions
As the setup is not trivial I created a small repository demonstrating the problem. It uses docker and docker-compose.
The repository is at https://github.com/xcash/angularfire2-auth-issue
Steps to set up and reproduce
The Firebase Authentication is not working inside NWJS (static content, not using internal webserver).
Firebase Realtime DB, Firestore is working perfectly. Authentication doesn't work for OAuth providers.
The redirect does nothing and the popup opens a blank page.
When using NWJS option --mixed-context to prevent it from running on a different worker thread the redirect still doesn't work but the popup shows up a login screen. But it won't work returning a "Something has gone wrong" error message upon login.
Same code served from localhost and viewed from a normal chrome works without an issue.
To run the repro clone the repository at https://github.com/xcash/angularfire2-auth-issue
Then follow these instructions:

Run with docker-compose up

Installa nwjs

create a symlink in NW's directory pointing to the dist/angularfire-auth-issue directory.
ln -s /path/to/repo/dist/angularfire-auth-issue/ package.nw

Modify src/environments/environment.ts with firebase authentication credentials

Launch nw ./nw

The login page appears. Select Google for a Google popup login.
Maybe you'll need to whitelist on Firebase console the chrome-extension://id
If everything is configure well, when you try to login the page popup will be blank with no error on console.
If you launch NW with --mixed-context you will be able to see the login popup but login is still impossible. You'll get a "something has gone wrong" error.
Debug output
No logs are printed on console.
Expected behavior
Normal authentication flow
Actual behavior
Broken authentication.
Foot notes
Sorry for the long issue but it is not a simple setup. But i think Angular is perfect for desktop apps and having Firebase with a full authentication backend in it would be awesome.

Hi @xcash! This is unlikely an issue with AngularFire and more likely an issue with the core auth SDK. Do you mind raising an issue with the official repo? I don't work on the Auth SDK so I can't provide much help here. https://github.com/firebase/firebase-js-sdk/

Hi @davideast, thanks for the reply. :) Ok as I return from holidays i'll open that referring here.


Add option for intel devices?

MACE seems to have added support for the "xpu" device (at least for training) via the intel_extension_for_pytorch package.
I imagine this could be useful for anyone using the new Intel PVCs via Dawn, and elsewhere.
We can certainly add xpu as a valid device type straightforwardly. I think everything else can be handled by the individual MLIP calculators, so that may be all that's required?

yap shall be added, also the config file got merged we shall check it.


mkl-dnn version vs tensorflow version

I want to git clone and build mkl-dnn (dnnl) and tensorflow from source.
Is there any guideline which mkl-dnn version works best with which version of tensorflow?
E.g. with Tensorflow branch v2.0 which branch of mkl-dnn to use for best performance?
with Tensorflow branch 1.15 which branch of mkl-dn to use for best performance?
Is there any guidelines?

@ratan,
In general we recommend using the latest stable version of DNNL for the best performance. Note, that major library versions 0.x and 1.x are note API compatible and moving from v0.x to v1.x requires code changes. As of today the latest stable versions are v0.21.4 and v1.2.1.
Tensorflow v1.15 builds with v0.20.6 by default and you may try upgrade the library version to v0.21.4.
Tensorflow v2.2 builds with v0.21.3, which is one patch short of the latest version. It has an option to build with v1.2, but support for v1.x did not reach production maturity yet.
Hope this helps,
Vadim

Thanks @vpirogov for the detailed reply.
I have few more questions, it will be great if you if you may answer them:

Tensorflow v1.15 builds with v0.20.6 by default.
I checked out TF 1.15 branch, see following details in third_party/mkl_dnn/mkldnn.BUILD
template_rule(
name = "mkldnn_version_h",
src = "include/mkldnn_version.h.in",
out = "include/mkldnn_version.h",
substitutions = {
"@MKLDNN_VERSION_MAJOR@": "0",
"@MKLDNN_VERSION_MINOR@": "20",
"@MKLDNN_VERSION_PATCH@": "3",
"@MKLDNN_VERSION_HASH@": "N/A",
},
)
Which indicates version 0.20.3

In the file bazel-out/host/bin/external/mkl_dnn/include/mkldnn_version.h
/* Major version of MKL-DNN */
#define MKLDNN_VERSION_MAJOR 0
/* Minor version of MKL-DNN */
#define MKLDNN_VERSION_MINOR 20
/* Patch version of MKL-DNN */
#define MKLDNN_VERSION_PATCH 3
Are they correct place to find out which version of mkl-dnn was used to build Tensorflow?

So latest Tensorflow builds (v2.2) uses the 0.x version of mkl-dnn and not 1.x version. If someone wants to build Tensorflow v2.2 with 1.x version of mkl-dnn (which has API changes) what optional flags is required to build Tensorflow ? I hope user doesn't require to do some code changes in Tensorflow to build it with 1.x version of mkl-dnn.

Latest stable version of Tensorflow uses 0.x version of mkl-dnn. Will this be default behaviour? Or there is any plan to integrate Tensorflow with 1.x version of mkl-dnn in future?

The v0.20.3 looks incorrect, as actual package TF downloads is v0.20.6. TF uses it's own bazel-based build system to build it's dependencies, including DNNL. As part of build process it generates mkldnn_version.h file and puts version information there. Actual version of the library that TF builds is included into bazel configuration here.
Transition of Tensorflow to DNNL v1.x should happen in one of future releases. I'm not directly involved into Tensorflow development though and do not have full picture of the plans.
@nhasabni, @bhavani-subramanian could you please help with question related to TF transition to DNNL v1.x?

@ratan The latest version of TF uses DNNL v1.2 by default (PR) i.e. when compiling using --config=mkl, DNNL v1.2 will be downloaded. To use v0.x, you need to build with --config=mkl_open_source_only.
Hope this helps!

Thanks @bhavani-subramanian @vpirogov It was really helpful.


ENH: document QC checkpoint after denoising

Draft exclusion criteria based on several visualizations generated after data denoising and FC extraction.
PS The reports I'm referring to do not exist yet, so I'm not sure if we want to merge the PR yet or let it in WIP until we implement the code to generate it.
Related to #384

@celprov - what's the status of this? This is not held up by MRIQC metrics, right?

No, not held up by the IQMs, this is the QA criteria corresponding to the visualization I was implementing last week. As we discussed a few meetings ago, I have to reframe it more clearly as QC criteria, not exclusion criteria.

I've checked the rendering.

I'll check how it renders and give you the green tick asap :)


Add user guide to Rust docs

Description
Python now has a decent user guide: https://delta-io.github.io/delta-rs/python/usage.html
We should write the equivalent of that for Rust on our crate homepage: https://docs.rs/deltalake/latest/deltalake/
Use Case
Related Issue(s)

We should make sure we have good docs for the operations module in particular: https://github.com/delta-io/delta-rs/blob/main/rust/src/operations/mod.rs

I am currently working on writing an example / docs and tuning the api a bit for the create command.
Of course other commands need to follow 🙂

chatted some with @wjones127 this morning and volunteered to help out here :)

Is this issue still available to work on?

@tbar4 for sure!!


TTS is not working with new version 1.0.0

Since update to version 1.0.0 on hassio 0.88.1 alex_tts seams to be not working ... with last version before 1.0.0 all was fine ... any hint or advice?

Please provide logs.

This part?

2019-02-23 10:04:16 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection.1863610416] Received {'type': 'call_service', 'domain': 'media_player', 'service': 'alexa_tts', 'service_data': {'entity_id': 'media_player.wohnzimmer', 'message': 'Test'}, 'id': 21}
2019-02-23 10:04:16 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=media_player, service=alexa_tts, service_data=entity_id=media_player.wohnzimmer, message=Test>
2019-02-23 10:04:16 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection.1863610416] Sending {'id': 21, 'type': 'result', 'success': True, 'result': None}

The logs are not showing what the component is directly doing. We should be seeing info from custom_components.alexa_media or alexapy if fully enabled.

Better?
custom_components.alexa_media
2019-02-23 10:02:16 DEBUG (SyncWorker_9) [custom_components.alexa_media] Setting up Alexa devices
2019-02-23 10:02:21 DEBUG (SyncWorker_10) [custom_components.alexa_media] Updating devices for<EMAIL_ADDRESS>2019-02-23 10:02:26 DEBUG (SyncWorker_10) [custom_components.alexa_media] Found 13 devices, 1 bluetooth, last_called: {'serialNumber': 'G000JN0573520BBD', 'timestamp':<PHONE_NUMBER>412}
2019-02-23 10:02:27 INFO (MainThread) [homeassistant.loader] Loaded alexa_media.media_player from custom_components.alexa_media.media_player
a lot of this for each device:
2019-02-23 10:02:49 DEBUG (SyncWorker_5) [custom_components.alexa_media.media_player] Disabling polling and scheduling last update in 300 seconds for Küche
2019-02-23 10:02:49 DEBUG (SyncWorker_12) [custom_components.alexa_media.media_player] Refreshing Atelier
alexapy
2019-02-23 10:02:14 INFO (MainThread) [homeassistant.setup] Setting up alexa_media
2019-02-23 10:02:14 DEBUG (SyncWorker_9) [alexapy.alexalogin] Trying cookie from file<EMAIL_ADDRESS>2019-02-23 10:02:14 DEBUG (SyncWorker_9) [alexapy.alexalogin] cookie loaded: <RequestsCookieJar[<Cookie at-acbde=Atza|IwEBIOMi4nCQYOzQqV7RWTzcmI9My8lRC8ZWZLlzOYWmTtSGLYt2AlG0rJcY26jp9RmPzPkwnb3KZshYjklZUQwkbbZs1-Asr2fc0Y2d2zCZ_0VFbmHBeYmKV3e6lGLpxphjxnTStTi6oG_sJBUbxPVm4Oyw-oBGAwocl-_RsNE9XXc3jlnNrbfd1yh459pvWjkaW-qp8r2hvRUeTNp3CxU9OQredq3jQSdO2K7UNtGnG9iNbQpnUrIO0lnvJdOvAFsiGbFIOIfzYRq0nMqT7wVZAHQNxuGEOvDkrANzy1AwVAANcTj8MkrVTkRD6U_gTULHXF26QWpMC6gf9Q61Hj3HMBaDtk-cU97sI7CoqxweX_zvdE1U2B2uJeBdoOEu6VV1udHnXu3QSnK0LYT_0uOv2HYg for .amazon.de/>, <Cookie csrf=1180531641 for .amazon.de/>, <Cookie sess-at-acbde="yAV+GEUfYxpkuMJtbEeOrIPOoLBYCb1lCVn2uwpoQ1Y=" for .amazon.de/>, <Cookie session-id=262-9034112-9399223 for .amazon.de/>, <Cookie session-id-time=2181628376l for .amazon.de/>, <Cookie session-token="y9tmfPQUZGq3Sn75BPQA3CMM26JFOH/IkBqC5qtCv+X83MYlNesgMgfAzXTsa7z5nJ/OEVbC887wPLq9yPydeWT/OX817svfmGpcTNnKY7WBAp/qZxMLg4/kcNTGJF9iSoXFYj5qhWMm5BjuiOHqPOE7PXQ9hgsoTs8lFKxl5ygVCSA3Jl8FirK74jIt5aHlK5TSpZNSP6KsjyuT47ecCyOg3MUywidvLEuztXbUhbg=" for .amazon.de/>, <Cookie sst-acbde=Sst1|PQFAHCTDFwUmvXU1skX9VmeXC1WqC5jawNN4WymhdngZTsAaU2WdTq0NiOQrnNACJhrZqnKx52xE-VYAOSR_XInIAsqPQCQfUU2wh6pvhE58hxwiaHJUVWtk-G1KCuQg7ABX4K51x3ZcyUkuV3oXeYU3QOdb4Uw-xS_KmqDz089RO_wQxmtZThh8hkmW4zQDu6dGs1JrtsVmkd6KRSx8Bkyac-SxDpM4k6d0LVfFTHIA8t9iypZp1Jpp9BCOqIZKqeY0BE0q8LmHksi_Wu8iiNfE1ZOrPdNxWQvJ4zG3Zga7MS0FiZC4DPLye_BbaTlSowAD-LYbw4b84IE1XBzoiuFZUQ for .amazon.de/>, <Cookie ubid-acbde=257-4528379-5286029 for .amazon.de/>, <Cookie x-acbde="Wl9j8erFkuXxunNh3RDOz@mVlNUQGGzn" for .amazon.de/>]>
2019-02-23 10:02:16 DEBUG (SyncWorker_9) [alexapy.alexalogin] Log in successful with cookies
2019-02-23 10:02:16 DEBUG (SyncWorker_9) [custom_components.alexa_media] Setting up Alexa devices

Please show the logs for when you actually try the TTS service. Also, please use the code quotes ``` and also scrub out some data.  I will edit your post to remove the cookie info and show you what I mean for the quote.

Problem is solved ... the components "media_player.xxxx" was renamed after new version of alexa media player with a new prefix on the end "_2" e.g. media_player_kitchen changed to media_player.kitchen_2

Glad you were solved. I saw you also deleted the log data which was a good idea.


Add Preview the documentation using a container section

So I add a link to localhost:4000 which is obviously a 404. To ignore said link in htmltest I have to add the 'data-proofer-ignore' attribute (https://github.com/wjdp/htmltest). I tried a few combinations of https://docs.asciidoctor.org/asciidoc/latest/macros/link-macro-attribute-parsing/ but to no avail, the attribute is never there in the html (I assume because markdown does not support custom attributes on links). I'll just push a non clickable link


Updated for upstream community operator Strimzi 0.12.2

This PR is about updating the Strimzi operator to 0.12.2 in the upstream-community-operators.
/CC @scholzj

Thanks submitting your Operator. Please check below list first.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?

Your submission should not

[ ] Modify more than one operator
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?

Your submission should not

[x] Modify more than one operator
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

/ok-to-test

@ppatierno - KafkaConnectS2I custom resource definition can only be used in environment which supports OpenShift build, image and apps APIs. Are you sure you want this in upstream?

@J0zi yes I am sure, it's the same for all the other previous releases.

@J0zi any news on that? The counter part of this PR was already merged. It would be great having our update on the operatorhub.io website.

@ppatierno, on #529 was just scorecard issue so I merged it because it fixes bugs. There is an issue with CSV. Let`s have a look what my community colleagues will say.

@J0zi what's the issue here? The files are the same as the other PR, it's just a different PR as requested.

@ppatierno the reason is that files are working for Openshift, but not for Kubernetes. See Travis.

@J0zi I took a look at the Travis log but to be honest it's not really clear to me what's going wrong there.
At some point the trace says ...
failed to reach Succeeded clusterserviceversion status for "strimzi-cluster-operator.v0.12.2"

but then
phase:Installing reason:InstallWaiting] map[lastTransitionTime:2019-07-25T08:52:12Z lastUpdateTime:2019-07-25T08:52:12Z message:install strategy completed with no errors phase:Succeeded reason:InstallSucceeded]] lastTransitionTime:2019-07-25T08:52:12Z lastUpdateTime:2019-07-25T08:52:12Z phase:Succeeded reason:InstallSucceeded certsRotateAt:<nil> message:install strategy completed with no errors]Logs for container strimzi-cluster-operator in pod strimzi-cluster-operator:

which says that all is fine.
Anyway our Strimzi cluster operator starts without any error at the end of the log.


Delete auto-merger.md

Learn Build status updates of commit 5b1afc5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

csidevdocs-public/demo/v-caxian/auto-merger.md
:white_check_mark:Succeeded
n/a (file deleted or renamed)

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


Improve error report

This PR is try to use panic/recover mechanism to do error report, instead of actively checking if stack's  top value is an error object.

@saveriomiroddi Sorry, I actually want you to review this. I'll keep polishing the panic raising part, but I think you can see what I intend to do already.

@saveriomiroddi This is pretty much finished, can you help me review it?

Hello! I've just finished reviewing now. I don't have experience with Go patterns, but this looks ok as error throwing/catching pattern.

@saveriomiroddi Yes that's what I try to do, thanks!


wish: set default User-Agent

Setting a default user agent string is something that Strava's own REST client in Go does:
https://github.com/strava/go.strava/blob/f5c7cee1038b80d25e3d262208d295c10ca2ac4b/service.go#L116
I'm thinking it might be 'node-strava-v3  '+version.
We can automatically introspect the package version from package.json just by calling require on package.json and reading the version property:
 var version = require('../package').version;

The primary place seeing this in their logs would be the Strava service itself. If there was a problem with how this library was accessing the Strava servers, having a consistent user agent string across requests would help Strava recognize that the common issue had to with a particular version of this library.

This is resolved in #55, which will be merged.


Half-sized resolution with HDMI

Using my Laptop and my Desktop, proper sizing via HDMI doesn't work. I have confirmed via wlr-randr, that the monitor supports the resolution i want it to use, and even applies it, but hyprland reports a wrong size.
-> wlr-randr
...
 1920x1080 px, 60.000000 Hz (preferred, current)
...
-> wlr-randr --output HDMI-A-1 --mode 1920x1080@60Hz
(nothing changes, because resolution is applied)

-> hyprctl monitors
Monitor HDMI-A-1 (ID 0):
<EMAIL_ADDRESS>at 0x0
	active workspace: 1 (1)
	reserved: 0 37 0 0

Setting the monitor resolution via the following line in the config file also didn't work
monitor=HDMI-A-1,1920x1080@60,0x0,2
I am pretty sure this is a bug either with hyprland as this occurs with different monitors on different systems, with the common factor being the HDMI connection.

well you have your scale set to 2, so the effective resolution is reported correctly.

OHH
facepalm
i thought this would be the workspace the output would usually take
somehow misread the Advanced Configuration page


[Docs] In 'Iteration' section should be reference to $parent

Stuck with impossibility of access to parent variables in Edge, like this:
@each(fabric in fabrics)

{{ fabric.name }}

	@each(product in products)
		@if(product.parent == fabric.id)
		{{ product.name }}
		@endif
	@endeach
@endeach

Later on forum I got explanation that I should use $parent.fabric.id.
I came from Laravel world, where all variable accesible in all @foreach while it open.
I more like Edge way with '$parent', it's more clear, but nowhere in documentation I can't find it. Can you add reference to '$parent' on 'Conditionals' page? Something called 'nested loops' maybe.

So this issue is more related to the concept missing in the docs, or you also facing the issue getting it worked?

Everything works great in code!
Only thing to do is add some explanation to Edge docs, so the laravel-comers like me could quickly get into.

Sure, even if not coming from Laravel it should be in docs 😉


Correctly set .fileTypeSymlink on windows

When calculating file attributes for an item, we did not previously correctly detect symlinks on Windows. This updates the implementation to correctly detect symlinks and set the file type when populating the attributes dictionary.

@swift-ci please test


Support FP16 for user buffer

/te-ci pytorch

LGTM. Have you tested that userbuffers works as expected with FP16 in your use-case?

@timmoon10 A China customer, Baidu, verified the fp16+user buffer by hard-coding the dtype to fp16.


Minor edits to "improved systemd integration"

Is your feature request related to a problem? Please describe.
Monitoring poller instance health via systemd units. The provided solution can be improved further.
Describe the solution you'd like

The description of the improved systemd integration should be linked into the README (https://github.com/NetApp/harvest/tree/main/service/contrib)
Poller service Unit file should be modified

improve description
change path to default
add user/group to avoid unix poller /proc issue and improve security
add "WantedBy" to correctly stop when harvest.target is stopped
Suggestion:

[Unit]
Description="Netapp Harvest Poller instance %I"
PartOf=harvest.target

[Service]
User=harvest
Group=harvest
Type=simple
Restart=on-failure
WorkingDirectory=/opt/harvest
ExecStart=/opt/harvest/bin/harvest --config /opt/harvest/harvest.yml start -f %i

[Install]
WantedBy=harvest.target

-harvest generate systemd output should be modified to allow piping directly to unit file

harvest.target unit file should use Requires instead of Wants. That way the target will fail if any poller fails to start.
harvest.target unit file should reference unix poller as last unit to avoid instance discovery error messages. (skip instance [ontap], process: process not found)
Suggestion

[Unit]
Description="NetApp Harvest Meta Service"
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
[Install]
WantedBy=multi-user.target' | sudo tee /etc/systemd/system/harvest.target

Describe alternatives you've considered
None
Additional context
None

Verified on release/22.02.0 727e0b5 :

documentation was updated
description was improved
default path printed to console is standard service location
harvest user and group are included in service file
service file includes WantedBy clause. Pollers are stopped when harvest.target is stopped
unix poller is added last in the service list


[VL] Daily Update Velox Version (2024_03_12)

Velox Upstream New Commits:
af49aa528 by Krishna Pai, Add better messaging for bad dates in DateTimeFormatter (8923)
17f0ed844 by joey.ljy, Add skewness Spark agg function (7513)
c5d3b938e by joey.ljy, Fix the bug in positional delete file traversal (9023)
d43663c30 by lingbin, Use uintptr_t instead of uint64_t to represent address (8778)
3efac60dc by Ankita Victor, Fix test method names in sparksql/tests/StringTest.cpp (9028)
c3dc8a0f6 by Richard Barnes, Remove "using namespace" dep in velox/common/memory/tests/SharedArbitratorTest.cpp + 5 (9017)
d87d6e0cd by Yang Zhang, Fix unhex Spark function with inputs of odd length (8993)

/Benchmark Velox

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_4923_time.csv
log/native_master_03_11_2024_5d923bf29_time.csv
difference
percentage

q1
35.71
36.18
0.474
101.33%

q2
24.29
24.37
0.074
100.31%

q3
37.00
36.99
-0.005
99.99%

q4
39.01
37.92
-1.088
97.21%

q5
67.56
69.79
2.237
103.31%

q6
7.11
7.17
0.061
100.86%

q7
82.93
81.73
-1.202
98.55%

q8
86.09
86.64
0.552
100.64%

q9
123.52
123.40
-0.126
99.90%

q10
44.02
44.98
0.959
102.18%

q11
21.66
20.66
-0.993
95.41%

q12
29.61
24.91
-4.702
84.12%

q13
48.95
46.43
-2.514
94.86%

q14
17.32
19.75
2.426
114.00%

q15
32.21
31.88
-0.330
98.98%

q16
13.99
12.73
-1.261
90.99%

q17
101.23
101.43
0.198
100.20%

q18
141.58
143.66
2.082
101.47%

q19
13.56
13.67
0.109
100.80%

q20
27.32
30.65
3.329
112.19%

q21
232.25
231.81
-0.440
99.81%

q22
13.78
13.84
0.059
100.43%

total
1240.69
1240.59
-0.101
99.99%


Term::read_line_initial_text() inconsistent with Term::read_line() regarding terminating newline

Term::read_line() allows the delimiting newline to be printed to the terminal, even though it is omitted from the returned String. This is the same as the documented behaviour of BufRead::read_line(), which Term::read_line() ends up calling.
The implementation of Term::read_line_initial_text() is not consistent with this. In this case, the newline is not printed to the terminal.
use console::Term;

fn main() {

    let term = Term::stderr();

    println!("Enter ten lines. The final five will have initial text");
    for _ in 1..6 {
        term.read_line().unwrap();
    }

    for _ in 6..11 {
        term.read_line_initial_text("Inital text ").unwrap();
    }
}

After I run the above and enter the numbers 1 to 10, my terminal looks like this:
Enter ten lines. The final five will have initial text
1
2
3
4
5
Inital text 6Inital text 7Inital text 8Inital text 9Inital text 10$

This has contributed to a bug I reported in dialoger. I think it might be cleanest to fix it here. I've raised a PR showing a possible fix.


Add ADABOUND Algorithm?

It is known that adaptive stochastic optimizers like Adam, Adagrad, RMSprop can indeed fail to converge. Moreover the test error of the trained models can be larger when compared to the models trained by SGD even though if they attain lower training error than with SGD - in other words they can overfit. See http://papers.nips.cc/paper/7003-the-marginal-value-of-adaptive-gradient-methods-in-machine-learning.pdf .
Recently, ADABOUND was proposed (https://openreview.net/pdf?id=Bkg3g2R9FX) to overcome the above mentioned problems of the adaptive optimizers. The algorithm combines the best of both worlds : (a) Makes fast progress initially like the adaptive methods, and (b) attains similar or better test accuracy to that of SGD.
Would this algorithm be welcome in JAX? If so, I would be interested to implement it.

Looks interesting!
We want to be careful about what we add into JAX core; part of what lets us move quickly is that we have a fairly small API surface to support.
I'd suggest implementing this out of tree for now, given the optimizer is quite new and we don't yet know whether it will become popular or not. Of course, if it does become popular, we should certainly add it!
That said, one of the joys of JAX is that optimizers are only a few lines of code. You can probably just branch the ADAM implementation and adapt it without too much trouble:
https://github.com/google/jax/blob/d161e1badb6259f033d8f097f6ded55b6701d023/jax/experimental/optimizers.py#L328
What do you think?

Just making sure that I understood correctly, by "implementing out of tree" were you suggesting to add this as a separate sort of experimental branch or create a JAX implementation and keep it outside of the repo?

Yes, precisely. I'd start by implementing the new optimizer in your own code base. I'd estimate it will only be 10-15 lines of code. Should Adabound turn out to be important to many people, we can add it to Jax itself. (For future readers: feel free to +1 this issue if that's you!)
We want to be careful about what we add, since it's much easier to add things than to remove them later.

In case you guys decide to add the Adabound algorithm to Jax, I have an implementation of it in my github : https://github.com/touqir14/Adabound-Jax . Actually, I am generally interested in writing optimization algorithms. Let me know if you guys would like to see any optimization algorithm implemented in Jax . @hawkinsp


KYC Fill-in Readiness Checklist

Include the checklist for meta-release Fall24, including documentation, ATPs and alignment with commonalities (0.4.0).
Same as KYC Match, Fill-in (v0.1.0/v0.1.1 base) will be included in meta-release Fall24. Corresponding PR for Readiness Checklist and Release Candidate PR will be created.

This issue seems to be fixed with the merged #118, just that it was closed automatically (due to syntax "Fixes issue #..." instead of "Fixes #...").

Closed as this issue has been fixed by PR #118.