Import of Purchase order line items fails due to Destination issue

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
When trying to import Purchase Order Line Items, I get a validation error of:  Cannot assign "'11'": "PurchaseOrderLineItem.destination" must be a "StockLocation" instance.
I assumed that the correct data for the "Destination" field should be the "Location ID" from an export of StockLocations.  That appears to be the data value that is stored in the destination_id field order_purchaseorderlineitem table in the database.  I've tried it as just a number, as a number inside quotes, and also as the text of the Location Name.
I've also tried to leave it blank but that fails with the error:  Cannot assign "'null'": "PurchaseOrderLineItem.destination" must be a "StockLocation" instance.  However, I have one entry in the destination_id field that has a NULL value.
When I export the existing Purchase order line items, the output shows the text name of the location.  I've tried to import a line with that exact copy of the text (both with and without quotes) and that doesn't work either.
It appears to me that there's some sort of error with the validator.  Or maybe I just don't know what the correct data should be.

Steps to Reproduce

Create CSV file with data for Purchase order line items
Set value of the "destination" field to the location_id of the stock locations
Attempt to import
Receive validation error

Expected behaviour
I would expect the data to import without errors.
Deployment Method

[ ] Docker
[X] Bare metal

Version Information
Version Information:
InvenTree-Version: 0.12.8
Django Version: 3.2.19
Commit Hash: a7487ff8
Commit Date: None
Commit Branch: stable
Database: mysql
Debug-Mode: False
Deployed using Docker: False
Platform: Linux-5.15.0-84-generic-x86_64-with-glibc2.35
Installer: PKG
Target: ubuntu:20.04
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}]
Please verify if you can reproduce this bug on the demo site.

[ ] I can reproduce this bug on the demo site.

Relevant log output
No response

@bhotrock thanks for reporting

@SchrodingersGat  Thanks for the quick fix!  I can confirm that the import is now successful.
Have a great day!


Feature: add group by

Description & motivation

Hi there,
I would like to group the data in profiler. I am not so sure if this feature is useful for everyone. But this is something I would like to have for my own usage. Feel free to discard the PR if you think it not so useful.
Cheers,
Tran
Checklist

[x] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered):

[x] Postgres
[x] BigQuery
[ ] Snowflake
[ ] Redshift
[ ] SQL Server
[ ] Databricks

[x] I have written tests for new macros (either as dbt schema tests in integration_tests/models, dbt data tests in integration_tests/tests or integration tests in the CI workflow)
[x] I have updated the README.md (if applicable)

@xtutran This had completely went by my radar, sorry for that. I'll merge this as is but I'll make minor change to the group_by  argument so that it's a list of column names. I'll open a separate PR for that.
Thanks for your contribution :)


Escaping issue breaks JSON.

This driver is globally replacing all " with ' :
https://github.com/neo4j-contrib/neo4j-jdbc/blob/2.3/src/main/java/org/neo4j/jdbc/rest/RestQueryExecutor.java#L190
I assume this is because the query is embedded in the JSON post body.  However, I would argue that it should be replacing " with " or at a minimum not interfering with previously escaped double quotes.  If I try to create a node property with a value that is a JSON string, then the jdbc driver is incorrectly changing it into improperly formatted JSON (even if I've escaped " the double quotes).
CREATE (n:Label { json : '{"key":"value"}' }) --X--> CREATE (n:Label { json : '{'key':'value'}'})

It should probably not do that, but just fail if it not escaped.
CREATE (n:Label { json : {1} })
-> parameter statement.setParam(1, "{\"key\":\"value\"}")
In general single quotes for your strings in cypher.


geos: 3.6.1 -> 3.6.2

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2/bin/geos-config --version and found version 3.6.2
found 3.6.2 with grep in /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2
found 3.6.2 in filename of file in /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2

@GrahamcOfBorg build of geos

Failure on aarch64-linux (full log)
Partial log (click to expand)
error: attribute 'of' in selection path 'of' not found

Failure on x86_64-linux (full log)
Partial log (click to expand)
error: attribute ‘of’ in selection path ‘of’ not found

Failure on x86_64-darwin (full log)
Partial log (click to expand)
error: attribute 'of' in selection path 'of' not found

@GrahamcOfBorg build geos

Failure on aarch64-linux (full log)
Partial log (click to expand)
error: attribute 'of' in selection path 'of' not found

Failure on x86_64-darwin (full log)
Partial log (click to expand)
error: attribute 'of' in selection path 'of' not found

Success on x86_64-darwin (full log)
Partial log (click to expand)
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/private/tmp/nix-build-geos-3.6.2.drv-0/geos-3.6.2'
make[2]: Leaving directory '/private/tmp/nix-build-geos-3.6.2.drv-0/geos-3.6.2'
make[1]: Leaving directory '/private/tmp/nix-build-geos-3.6.2.drv-0/geos-3.6.2'
post-installation fixup
strip is /nix/store/4sdh09gmvl15cy0zb6i7mbvxh5syz206-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/pl6pyc6v9d36qckhabj3ykna00gvdgh0-geos-3.6.2/lib  /nix/store/pl6pyc6v9d36qckhabj3ykna00gvdgh0-geos-3.6.2/bin
patching script interpreter paths in /nix/store/pl6pyc6v9d36qckhabj3ykna00gvdgh0-geos-3.6.2
/nix/store/pl6pyc6v9d36qckhabj3ykna00gvdgh0-geos-3.6.2/bin/geos-config: interpreter directive changed from "/bin/sh" to "/nix/store/pkjmwq7sqrvjg7cjiph6hq0khsmfl6p8-bash-4.4-p12/bin/sh"

Success on aarch64-linux (full log)
Partial log (click to expand)
make[1]: Leaving directory '/build/geos-3.6.2'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/f1m1njmd358i9cyj7qdzh76alx5k8gvf-geos-3.6.2
shrinking /nix/store/f1m1njmd358i9cyj7qdzh76alx5k8gvf-geos-3.6.2/lib/libgeos_c.so.1.10.2
shrinking /nix/store/f1m1njmd358i9cyj7qdzh76alx5k8gvf-geos-3.6.2/lib/libgeos-3.6.2.so
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/f1m1njmd358i9cyj7qdzh76alx5k8gvf-geos-3.6.2/lib  /nix/store/f1m1njmd358i9cyj7qdzh76alx5k8gvf-geos-3.6.2/bin
patching script interpreter paths in /nix/store/f1m1njmd358i9cyj7qdzh76alx5k8gvf-geos-3.6.2
/nix/store/f1m1njmd358i9cyj7qdzh76alx5k8gvf-geos-3.6.2/bin/geos-config: interpreter directive changed from "/bin/sh" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/sh"
checking for references to /build in /nix/store/f1m1njmd358i9cyj7qdzh76alx5k8gvf-geos-3.6.2...

Failure on x86_64-linux (full log)
Partial log (click to expand)
error: attribute ‘of’ in selection path ‘of’ not found

Success on x86_64-linux (full log)
Partial log (click to expand)
make[1]: Leaving directory '/tmp/nix-build-geos-3.6.2.drv-0/geos-3.6.2'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2
shrinking /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2/lib/libgeos-3.6.2.so
shrinking /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2/lib/libgeos_c.so.1.10.2
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2/lib  /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2/bin
patching script interpreter paths in /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2
/nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2/bin/geos-config: interpreter directive changed from "/bin/sh" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/sh"
checking for references to /tmp/nix-build-geos-3.6.2.drv-0 in /nix/store/1z3ldj647vpcdj0n4wdjnb3fl2ard1w2-geos-3.6.2...

3.6.2 is in master now


cant get setMaxOverzoomLevel to work

I cant get this to work. I have a layer which datasource stops at zoom 7. Even if i set setMaxOverzoomLevel(1) (or even 0). Then at zoom (let s say) 14 it will always find the parent tile from 7.
I would expect to render empty tile at zoom 14

@farfromrefug 'Overzoom' only applies to tiles already loaded and cached. Thus is if overzoom=1 and current zoom=6 and the relevant tile is not available, SDK checks if it has zoom=5 tile cached. If it has, then this tile is displayed instead while the zoom=6 tile is being fetched.

@farfromrefug Documentation is somewhat ambiguous here, so I can see how it caused the confusion.  As the use case is quite specific, the option is to create a custom data source that returns empty tiles starting from some threshold zoom level.

@mtehver great idea! i am on it!

@mtehver i might need a bit of help from you on this. I started to implement this by returning std::make_shared<TileData>(std::shared_ptr<BinaryData>()); for empty tiles. Then in RasterLayer it falls into that if
My issue is that going there seems to still draw what's in the cache. How can i prevent that?
I have a feeling it is because the parent tile is found in the preloadingCache. Can i invalidate the tile from preloadingCache when i fail into my overzoomLevel ?


SO_PASSCRED and SO_PEERCRED options

Note that those only work on stream (TCP) sockets (unfortuantely not on datagram=UDP sockets)

ping!

Sorry. Was away. Right now, I don't have access to a Windows machine. However, if you apply these changes to options.c, will it still compile on Windows?

2016-10-21 21:59 GMT+02:00 Diego Nehab<EMAIL_ADDRESS>
Sorry. Was away. Right now, I don't have access to a Windows machine.
However, if you apply these changes to options.c, will it still compile on
Windows?

I don't know. I don't have access to a Windows machine too.

It will not.

A bit of research suggests that on Windows these flags are only available in WSL (Windows Subsystem for Linux), which would explain the failure to compile in standard Windows environments.
We could potentially provide support driven by conditional compilation (e.g. #ifdef SO_PASSCRED). Behavior should, of course, degrade gracefully wherever they are not supported.  If this is desired, a PR to that effect would be welcome.
We're reviewing open items in preparation for a release.  If action is needed here, please add a comment.  Otherwise, this issue will be closed on or after 24-Feb-2019.
Thanks!

Closing, as I don't use this anymore.


Update submodules

Hey! I'm just your friendly neighbourhood bot, updating your submodules.

Closing this PR because I'm assuming it's a test pull request.


Fixing context equality check in viewer for gold candidates

Fix for https://github.com/HazyResearch/snorkel/issues/1082 (cc: @bhancock8).
I'd like to add a unit test that at least validates that the viewer can be created, though I was a little unclear on what the strategy with tests is.  The spouses and crowdsourcing dbs that get used in the pytorch and tensorflow tests seem like they could probably be parts of test fixtures that don't necessarily have anything to do with PyTorch or TF functionality right?  It seemed to me like making test data a more generic resource could help with testing many things, including the viewer.  I'll gladly attempt that in another PR if there are no objections that it would be a worthwhile abstraction.

Yep! No objections. The data should be independent from PyTorch or TF. We'd welcome that other PR.


Stripe Checkout as a Snipcart alternative

I'm abandoning this for now as Shopify is just a better "next step" for more robust eCom.


AnimationPlayer changes its frame milliseconds before looping

This is on Godot_v2.0.3_stable_win64.exe

Add a Normal Node Sprite
Set the texture to your spritesheet
Set the vFrames and hFrames respectively
Keyframe an animation using the AnimationPlayer with steps set to 0, and then set it to continuous.
Set the len(s) to: 0.8
Now on the first keyframe, set the  Frame 0.
Now on the last animation keyframe set the Frame to 19 (or your total amount of frames -1)

Now here is where the bug is:
Look at where the timeline is at, it's barely at the end, and it's showing the Frame 19. Which is correct: (This is the last frame it should be on before looping)

Now, move the timeline cursor over just a bit (you might need to click on the image to zoom in) and look what happens:

It goes to the last frame right at the last millisecond before looping. Which causing distortion (barely noticeable) when animating. You can change the steps value to 0.0001 to fix this, but the distortion still happens.

Dupe of #959... Nice to see someone else thinking it's screwy, though... Hope it gets fixed some day, if it hasn't been already.

Ha, well if this doesn't get fixed I'm kind of stumped at continuing to use the engine :P I'm porting my game over from HTML 5 and we have hundreds of sprite sheets like this, the distortion is barely noticeable but it's there :(. I think I isolated the problem more though, it's basically right before the last frame (as you stated, on continuous mode) it sets it to frame 0 when it shouldn't. [The last couple milliseconds] -- I don't know C++ at all, but I think if someone is well versed it will be no problem.
Do you know if this happens on the linux builds though? For example, #4667 doesn't seem to happen on linux builds, but sporadically out of no where on windows.. Might be the same for this :palm_tree:

I only run Linux, so yes.
It's not only a problem with the last frame. It's because of how the engine is behaving as a whole. It is blending from end to beginning when you enable looping, and it's NOT right.  There needs to be a way to turn that off. I had fixed it completely and submitted a pull request, but closed it out because the current behavior is, for some reason, actually intended and desired behavior. It is outside of my skillset to implement a proper fix that retains the current, unexpected, and broken behavior while giving us the option to play animations how they should be played.
And yeah, as you allude, it is definitely discouraging and has at least contributed partly to why I am not as active here as I once was.

duplicate https://github.com/godotengine/godot/issues/959
I guess, thanks @adolson up to the bosses now. See my post there, I tried, we'll wait and see :)

there is a problem with the interpolation which @punto- found. It needs to be corrected and leads to this kind of mistakes... question is if any project would break as a result

question is if any project would break as a result

Thanks for your response! Maybe an option to disable this so current projects are not affected?
It could be added as a checkbox to the Track Tools button:


Propose initial API design based on latest feasibility study

Description:
$subject, a follow-up task of https://github.com/wso2-ballerina/module-mongodb/issues/66
Suggested Labels:
Other

Proposed API can be seen here https://docs.google.com/document/d/1mtwrhS_NnkI-spjQZyXefXTShZaaw5NqDvatWhsToQI/edit
Dev mail thread : https://groups.google.com/forum/?hl=en#!topic/ballerina-dev/z_amsHLV4Bk


Copy the entire manifest list when tagging latest

skopeo only copies over the amd64 image manifest unless explicitly specified by adding the --all option.

/approve

/test

Not sure how to approve the Konflux CI, but maybe it doesn't matter much.

Maybe /ok-to-test ?


Add files via upload

Fractal Native Punks - Activated at block height 21,000

No inscriptions.json file @cbone1234


First attempt, adding _id label to limited_support_enabled metric

This is incorrect, compiler is complainig

@aliceh You can use the logic already present in the proxy controller to set uuid
https://github.com/openshift/osd-metrics-exporter/blob/main/controllers/proxy/proxy_controller.go#L52

/label tide/merge-method-squash

I think the last remaining thing is the unit tests, which are failing because they expect the CLUSTER_ID environment variable to be set. This can be done by using t.SetEnv https://pkg.go.dev/testing#T.Setenv in the corresponding failing tests: https://github.com/openshift/osd-metrics-exporter/blob/d834f20ed0a2314a0bda8b8591dc2b20df1f6251/controllers/limited_support/limited_support_controller_test.go#L27

Codecov Report

Merging #89 (2c56685) into main (d834f20) will increase coverage by 0.00%.
The diff coverage is 84.61%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #89   +/-   ##
=======================================
  Coverage   49.88%   49.88%
=======================================
  Files          10       10
  Lines         439      443    +4
=======================================
+ Hits          219      221    +2
- Misses        210      211    +1
- Partials       10       11    +1

Impacted Files
Coverage Δ

...lers/limited_support/limited_support_controller.go
44.11% <60.00%> (-1.05%)
:arrow_down:

pkg/metrics/aggregator.go
95.16% <100.00%> (+0.03%)
:arrow_up:

/lgtm

/lgtm

/approve
Nice work!


NSE - SE cleanup

There are a number of ways to clean up NSE, I attempted to do this without changing the original dplyr style as much as possible.
There are a couple cases where I had to use the .dots input explicitely, which changes how the function calls look pretty drastically, but I don't think it's bad.
This PR gets my local check to 0-0-0!

Coverage remained the same at 95.482% when pulling 97e0da99735501ec8ad18486770d5058809f3e59 on dblodgett-usgs:nse-cleanup into a19d5a4c5da962b2d6fc1832461d56d86c353109 on USGS-R:master.

As a heads up, the NSE in dplyr is going to change for 0.6.0 - https://github.com/tidyverse/dplyr/releases/tag/v0.6.0-rc.

I doubt that we'll merge this PR. I did this as an excuse to spend some time in the code and get some more tests written. Sounds like people around the USGS-R world prefer to just create "fake" global definitions for variables in the package to get around the notes and move on. All these little tweaks really only accomplish the same thing.

No worries!


Live preview does not correctly find relations when using blocks inside the lexical rte.

Link to reproduction
No response
Describe the Bug
The following line in the rich text traverser detects relations based on the relationTo and value fields inside any given iterated object in a rich text tree:
https://github.com/payloadcms/payload/blob/c038acb3a4da6cda85d034aeb8b042d172ee868f/packages/live-preview/src/traverseRichText.ts#L59
However, when using the blocks feature in the lexical rte, relationships are not defined by those fields, and instead simply hold an id string reference field.
Because of this, the rich text traverser is never able to resolve relation fields inside blocks.
To Reproduce

Enable lexical editor field on some collection.
Use the Blocks feature
Create a block with a type: 'relation' field, with a relationTo some other collection.
Populate the field in the admin UI
Implement the live preview feature, set depth > 0
Check the data returned from the callback function
The relation field in the respective block will always just havr a <fieldname>: <id> entry, regardless of the depth parameter.

Payload Version
2.11.2
Adapters and Plugins
<EMAIL_ADDRESS>

Hey
Any news on the solution for this problem ?

I've found a workaround for this. Just set relationTo to an array, even if you only need to reference a single collection, like relationTo: ['images'] instead of relationTo: 'images'.
In this way the resulting field values will have the form of { relationTo: <collection-slug>, value: <resolved-document> }, which is resolved correctly by traverseRichText.

I'm still able to reproduce this on v3 with 3.4.0.
Here is a test case showing the issue:
https://github.com/andershermansen/payload/commit/70dcb5b6ff03849bff77652aa4d84f76d517d951
Getting string when expecting the object:


Linux installation error “nixbld”

Upon a fresh installation on Linux. I am being thrown error logs saying something on the lines of:
(unfortunately I didn’t manage to capture the entire error log)
Partial error code:
warning: the group 'nixbld' specified in 'build-users-group' does not exist / warning: the group 'nixbld' specified in 'build-users-group' does not exist reading the Nix store...
I was told to add additional codes in the terminal to solve this issue/ error only after the display of the error codes but I would like to get official directions from iohk and the Daedalus team as I want to install Daedalus from scratch the proper way.

@sudomonzter please provide more info about your system. Which Linux are you using? What version? etc...
Please be mindful of the supported Linux versions:  https://iohk.zendesk.com/hc/en-us/articles/360010496553-Daedalus-System-Requirements
@dmitrii-gaico please assist @sudomonzter here. Thanks!

@sudomonzter any news?

Closing the ticket as additional feedback required for further investigations. @sudomonzter please open a new ticket if you still facing the issues so we can resume the research.


Request Followed Cams download for chaturbate.com

Checklist

[X] I'm reporting a site feature request
[X] I've verified that I'm running yt-dlp version 2022.04.08 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Germany
Example URLs
https://chaturbate.com/followed-cams/
Description
Hello, I'm requesting a download feature for downloading followed cams from chaturbate.com.
Verbose log
[debug] Command-line config: ['-vU', 'https://chaturbate.com/followed-cams/']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, err UTF-8, pref UTF-8
[debug] yt-dlp version 2022.04.08 [7884ade65]
[debug] Python version 3.7.13 (CPython 64bit) - Linux-5.4.188+-x86_64-with-Ubuntu-18.04-bionic
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg 3.4.8, ffprobe 3.4.8
[debug] Optional libraries: brotli, certifi, Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
Latest version: 2022.04.08, Current version: 2022.04.08
yt-dlp is up to date (2022.04.08)
[debug] [Chaturbate] Extracting URL: https://chaturbate.com/followed-cams/
[Chaturbate] followed-cams: Downloading webpage
ERROR: [Chaturbate] followed-cams: Unable to download webpage: HTTP Error 403: Forbidden (caused by <HTTPError 403: 'Forbidden'>); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "/usr/local/lib/python3.7/dist-packages/yt_dlp/extractor/common.py", line 641, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/lib/python3.7/dist-packages/yt_dlp/extractor/chaturbate.py", line 43, in _real_extract
    headers=self.geo_verification_headers())
  File "/usr/local/lib/python3.7/dist-packages/yt_dlp/extractor/common.py", line 935, in _download_webpage
    expected_status=expected_status)
  File "/usr/local/lib/python3.7/dist-packages/yt_dlp/extractor/common.py", line 800, in _download_webpage_handle
    urlh = self._request_webpage(url_or_request, video_id, note, errnote, fatal, data=data, headers=headers, query=query, expected_status=expected_status)
  File "/usr/local/lib/python3.7/dist-packages/yt_dlp/extractor/common.py", line 785, in _request_webpage
    raise ExtractorError(errmsg, cause=err)

  File "/usr/local/lib/python3.7/dist-packages/yt_dlp/extractor/common.py", line 767, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/lib/python3.7/dist-packages/yt_dlp/YoutubeDL.py", line 3601, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python3.7/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/usr/lib/python3.7/urllib/request.py", line 641, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python3.7/urllib/request.py", line 563, in error
    result = self._call_chain(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 755, in http_error_302
    return self.parent.open(new, timeout=req.timeout)
  File "/usr/lib/python3.7/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/usr/lib/python3.7/urllib/request.py", line 641, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python3.7/urllib/request.py", line 569, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 649, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 403: Forbidden

I too would like to see this feature added


Bump version for release 0.61.0

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


fix bazel caching for windows

Fixes # (issue)
Changes
Please provide a brief description of the changes here.
For significant contributions please make sure you have completed the following items:

[ ] CHANGELOG.md updated for non-trivial changes
[ ] Unit tests have been added
[ ] Changes in public API reviewed

Codecov Report

Merging #60 (c0e7b2c) into main (ae6d810) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #60   +/-   ##
=======================================
  Coverage   95.44%   95.44%
=======================================
  Files         157      157
  Lines        6633     6633
=======================================
  Hits         6330     6330
  Misses        303      303


[WIP] Add NumPy compatibility module

I talked with @okuta regarding this, and we thought it is better to drop support for some older NumPy versions, because installation/upgrade of NumPy became easier as they now provides wheels.

I'm glad to hear that the draft PR leads to the discussion to drop old NumPy.

Regarding NumPy compatibility, we decided to ask users if they have any special reasons to use older NumPy (1.9/1.10) and drop the support starting in v7 if there's no problem.


Fix FileAlreadyExistsException in LORE dump process

Summary
This PR resolves the FileAlreadyExistsException that occurs when using spark.rapids.sql.lore.idsToDump to dump particular partitions.
Changes Made

Added a check to verify if the LORE dump path exists and is not empty before proceeding with the dump.
If the path exists and contains files, an IllegalArgumentException is thrown to prevent overwriting existing data.

build

build

build

build

build

build

build


How to force Tensorflow app to use Android framework's NNAPI?

Describe the problem
I am using x86 (intel platform) android device to check if tensorflow apk is calling Android's NNAPI. It seems its not calling the APIs.
How can i force tensorflow apk to forcefully use Android framework's NNAPI?
Android studio project location: /tensorflow/contrib/lite/java/demo/app/
Android version: 8.1

I have a PR for this, see https://github.com/tensorflow/tensorflow/pull/16065

This seems to be resolved with another PR see:
https://github.com/tensorflow/tensorflow/blob/049dfd5e070cfa84c82eea71c6c746a70cba4a3f/tensorflow/contrib/lite/java/src/main/java/org/tensorflow/lite/Interpreter.java#L207
Please close if this is done to your satisfaction. Thanks!

I'll close this for now. Let us know if this still doesn't work for you.

This is solved... Please close this


Using environments

While trying to make a multi-threaded(or just async calls) scripting system, I've got into this program design, which all of these scripts to be run are unsafe(aka from the user):

1: One SETUP script, to define common variables/functions/tables which should be readonly from other scripts;
2: Few one-time executed scripts running in the mian thread. This needs to have the SETUP environment so it can access the main variables/tables;
3: Few looping scripts that needs also to have access to the SETUP envorionment. They are running concurrently and can be enabled or disabled on demand.

The framework to have it all working is already built up, with custom stopping/relaunching settings/looping and such. The only thing I cant get it to work is to feed the looping(3) scripts with the SETUP informaiton.
But, since Main Thread has an sol::state and each looping scripts have each one their own state (the docs and here i've been told that for concurrent the proper way is to go with multiple states), I would need to feed the looping ones with the run-time changes of the SETUP.
The current running setup I have is:

For 1: Run the script directly on the state;

lua.script(script->m_Script);

For 2: Run the script on a brand new environment, but on the main thread state each time a new script is run:

script->thisEnvironment = sol::environment(lua, sol::create, lua.globals());
lua.script(script->m_Script, script->thisEnvironment);

-For 3: Run the script on a brand new environment, on the early created state, each time a script loops:
script->thisEnvironment = sol::environment(script->thisState, sol::create, lua.globals());
script->thisState.script(script->m_Script, script->thisEnvironment);

This last one is where I'm having trouble. Is there a way to use the environment fallback on the globals of another state? If yes, how? If no, how can I accomplish the same thing I'm wanting?
I've tryied to use the same state for all three, but since it is async sometimes it bugs out. I need it to be also reliable.
Thanks again

You can't use the globals of another state as the fallback for an environment table. Lua does not have any way of transferring state or objects or values between States. You must explicitly serialize between them. You must either directly serialize and synchronize states, or you must have one and only one state.

What kind of serialization/synchronization between those states you would recommend me to take a look?
I've seen that there is not standard way to do it, but perhaps you may have stumbled upon on a similar use scenario...
With only one state It would be possible with some kind of thread lock to prevent double access to the same state, i think...
Also, another problem just appeared: when trying to defiine each new state, I have a "Setup" function which receives an sol::state as argument and then sets up the argument with new usertypes/tables/functions. The main state works just fine, but when I make a new state using that function, those custom usertypes seem to not be accessed.
I've tryied this:
void Setup(sol::state * arg_stateToSetUP) {
	arg_stateToSetUP->open_libraries(sol::lib::base, sol::lib::math, sol::lib::string, sol::lib::table, sol::lib::bit32, sol::lib::os);
	arg_stateToSetUP->set_function("Wait", &Sleep);
	arg_stateToSetUP->set_function("Time", [&]() { return time(NULL); });
}
Setup(&thisState);

And this:
void Setup(lua_State * arg_stateToSetUP) {
	sol::state_view tempSt(arg_stateToSetUP);
	tempSt.open_libraries(sol::lib::base, sol::lib::math, sol::lib::string, sol::lib::table, sol::lib::bit32, sol::lib::os);
	tempSt.set_function("Wait", &Sleep);
	tempSt.set_function("Time", [&]() { return time(NULL); });
}
Setup(&thisState.lua_state());

But no success... Is there something wrong? It works on defining the main state, but not on the child others... Cant understand why.

If by "child states" you mean sol::thread alikes, that does not work. Lua Threads only have different stack space, and all point to the main thread, and ultimately share that top-level environment.
You can only be calling open_libraries on the Main Thread of any given lua_State*.

Child states I meant a sol::state, which would fit on the number 3 on the main topic. Thats why "child". It is just a bare sol::state, that I call the Setup function when a wrapper that contains external infromation is being constructed.
	thisState = sol::state();
	p->cScripts->Setup(&thisState);

Or
	thisState = sol::state();
	p->cScripts->Setup(thisState.lua_state());

So basically it is on the main thread of that state, but still it doesnt set up.

I've already got some xml implementation as well some json... Worked with protobuf on this project also. But I was thinking on something lua to lua, because there is no way to hardcode every possible variable an user puts in the setup that he would want to use on those looping scripts.
For now I'll stick to this setup, but later on will consider using only one state to hold all the user info.
Thanks for your help, and if anything else pops up i'll jump back here
Oh, and keep up the good work on this lib, it was really few hours of a learning curve to get from zero knowledge of c++ lua to making a complete script with custom usertypes/overloads work (of course without this crazy framework i've trying to accomplish). So yeah, it is really straightforward :P

Not related to sol2, but an even loop like cqueues, luasys and others can be used to flip your threading model on its head (one lua state and a C library that polls underneath your lua code). Cqueues is quite good and very complete. It uses coroutine so you don't have to write ugly callbacks like node.js. Windows libraries to do the same are hard to come by though.


ion-col column delimiters are not working with badge

Hi friends,
I get the error on the link given in the link below. why is that?
https://resmim.net/f/iZUpza.jpg
<ion-list>       <ion-item *ngFor="let _orderDetail of orderDetailArray">         <ion-row>           <ion-col col-sm-7>             {{ _orderDetail.product.name }}  Adet :{{ _orderDetail.quantity }}             <ion-col *ngIf="_orderDetail.properties.length>0">               <ion-badge *ngFor="let _property of _orderDetail.properties"                          color="secondary"> {{ _property.name }}</ion-badge>             </ion-col>             <ion-badge *ngIf="_orderDetail.type" color="primary">{{ _orderDetail.type.name }}</ion-badge>           </ion-col>           <ion-col col-sm-3>             <button ion-button icon-only round outline color="danger"                     (click)="_orderDetail.quantity>1 ? _orderDetail.quantity=_orderDetail.quantity-1 : _orderDetail.quantity">               <ion-icon name="md-remove-circle"></ion-icon>             </button>             <button ion-button icon-only round outline color="info"                     (click)="_orderDetail.quantity=_orderDetail.quantity+1">               <ion-icon name="md-add-circle"></ion-icon>             </button>           </ion-col>           <ion-col col-sm-2 text-right style="font-size: 20px; font-weight: bolder;">             ₺{{ _orderDetail.product.salePrice * _orderDetail.quantity }}           </ion-col>         </ion-row>       </ion-item>     </ion-list>

Hello! Thank you for opening an issue with us!
The Ionic Framework issues list is designated for the reporting of bugs with the Ionic Framework or for requesting new features. As this seems like more of a support question I am going to close this issue.
I urge that you ask this question on our forum or on our slack channel.
If you believe this is due to an error in our standard CSS or some other part of the Ionic Framework, please open an issue with the template fully filled out and with a sample application shared via GitHub that can be used to duplicate the issue you are having.
Thanks for using Ionic!


chore: improve landing page metadata (centered, proper logo + one-sentence description)

favicon would be nice too (:


License field on npm showing "none" due to inappropriate LICENSE file name

On https://www.npmjs.com/package/case, license field is showing as "none", I think NPM cannot parse LICENSE-MIT file. Other variations such as LICENCE, LICENSE.md are accepted.
I suggest renaming LICENSE-MIT to one of these variations if possible.

Sounds reasonable. Care to contribute a PR? If not, i'll get to it at some point.

Yes sure, I'll do a PR within this week.
Thanks.
On Wed, 11 Jul 2018, 23:00 Nathan Bubna<EMAIL_ADDRESS>wrote:

Sounds reasonable. Care to contribute a PR? If not, i'll get to it at some
point.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nbubna/Case/issues/27#issuecomment-404292237, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABJlZmtGM8Zi4G5kVX-o9Y3c4dVwSlEsks5uFll1gaJpZM4VLOey
.

Thanks!


Rename secrets to environment variables (use conceal flag)

WE currently have secrets and environment variables (can be set at server start). Instead I would suggest to rename secrets to environment variables and add an option to conceal environment variables which would be same to the current secrets.
This would allow us to have one way of managing those variables in ui, cli, pipeline parsing ...

Would solve #362 as well

But secrets are not really env variables, they are used quite differently

They can be used by from_secret, are redacted from logs and what else?

they are env vars ... but with spesific propertys like sanitazed in logs before leaving the agent

It would be a super hard and breaking job renaming it, but would only require one thing to maintain. But I am open for other suggestions.
Would you just "copy" the UI / base logic from secrets?

Env vars has one use case and secrets have other, only case where they use case overlaps is if they are specifically bound together in step definition. If we are talking about UI than yes they should have separate tab in settings and way more simple UI - just name and value that should be visible and editable not like secrets that you can just override with new value.

Could this be used to get environment variables at repository level for several pipelines instead that to pipeline level?

Seems not to be wanted


[WIP] Pulse simulator tutorial using Duffing oscillator models

Update Feb 4:
I'm now happy with the current status of the tutorial, and am looking for comments!
Summary
A tutorial demonstrating the PulseSimulator use-case of the user defining their own model, then running pulse simulations on it.
This is a work in progress; comments welcome!
Details and comments
Steps in the tutorial:

A 2 qubit model using a Duffing oscillator model is defined
A calibration routine is run to calibrate a pi pulse on each qubit (ripped from Dave's original example notebook)
Using the calibrated pi pulse, state-dependent CR oscillations are demonstrated (it is shown using the bloch sphere that trajectory of the target qubit changes depending on the state of the driven qubit)

This might be a great fit for the textbook. What do you think, @DanPuzzuoli and @nonhermitian? It seems to work well with the theme of pedagogically presenting something and using qiskit to do it.

I leave it up to you guys to decide. What are the standards for the textbook vs a tutorial; would anything need to be done to adapt it? @zachschoenfeld33 has been thinking about pulse sim textbook stuff as well.

Looks great! This is very useful notebook for hands-on events and lectures.
I have some comments

model description

is there any reason not to use capital J for the coupling constant? it may look like imaginary number, especially for electronic engineers. also there is inconsistency of terms in the model description and the code, eg frequency nu vs oscillator_freqs. they should be unified.
it is better to write full two qubit Hamiltonian after Cell4 because the control channel doesn't appear in the model, but we will use it in the same notebook. also it is better to write relationship of their notations in the model (D, U, M) and pulse channel representations (pulse.DriveChannel, pulse.ControlChannel, pulse.MeasureChannel). I know measurement channel is not actually simulated.
as a simulator tutorial, it may be better to briefly explain how the simulator calculate the dynamics.

pulse part

why you don't show pulse sequence? (ie sched[0].draw()?)

below is not related to the notebook but just from curiosity.

why dt is stored in PulseSystemModel class? it is more natural to be in the qobj configuration.
what is the reason of CR Rabi rate dependency on control qubit state? I guess there is strong IX interaction induced by higher levels and it is interesting to run echo sequence to remove this (this also shows the validity of physical model).

Should provide some kind of definition or introduction to what a duffing osc model is in the first paragraph
2 . This is also a good place to motivate the usage of the model. There is a sentence there listing "duffing model, example 1, example 2". As far as I understand, the model allows you to do the following two examples. You have to specify some kind of model for qubit behavior to start doing any simulations of pulse-level qubit behavior, right? This relationship should be explained right away. What is the relationship between example 1 and 2? Can a reader skip to example 2 if they want, or is example 2 built on example 1?

Duffing system model

Think about swapping how you present the info: if you start with the physics, then the reader has the topic motivation and knows what they are working towards. Then, when you explain that it fits into the simulator as a PulseSystemModel with the convenient duffing_system_model function, they understand why they want that. This also leads you right into the next code block, where duffing_system_model is used.
You could consider waiting to mention and explain PulseSystemModel altogether after the code block. They don't really need to know about it until they have just made one, as extra context.
# time comment over dt should be a little more specific ("timestep" or "sample duration" or "timescale")

Cross-resonance ControlChannel indices

first sentence: the object (I'd wonder, what object?) should be replaced with two_qubit_model
E.g. ... is providing an example of what is stated in the first sentence; should it follow that sentence rather than beginning a new paragraph?

Example 1

Would you mind replacing pulse_lib.X with the parametric pulses? This isn't that important, but I think it could be nice.
I like your qubit_populations_from_memory function! I've been thinking for a while about looking into the results object and adding some utility functions like this to terra

Example 2

## Drive qubit 1 to observe CR oscillations on qubit 0 this is part of example 2, right? It should be a subheader of Ex 2, not the same level (###)

Thanks for the comments!
@nkanazawa1989

model description

is there any reason not to use capital J for the coupling constant? it may look like imaginary number, especially for electronic engineers. also there is inconsistency of terms in the model description and the code, eg frequency nu vs oscillator_freqs. they should be unified.

There is no reason for using j over J 😄 . In the string representation being used behind the scenes it is necessary to use lower case letters for coefficients, and I just carried that over when writing this. If it is standard physics notation I can change it to J (I gather that it is).
For the nu/oscillator_freqs, I think I want to keep it as is. In the simulator code the argument name is already set to oscillator_freqs.

it is better to write full two qubit Hamiltonian after Cell4 because the control channel doesn't appear in the model, but we will use it in the same notebook. also it is better to write relationship of their notations in the model (D, U, M) and pulse channel representations (pulse.DriveChannel, pulse.ControlChannel, pulse.MeasureChannel). I know measurement channel is not actually simulated.

I think I may actually move the Hamiltonian description all the way up to the beginning of the notebook, as per @lcapelluto's comments. I like the idea of motivating the physics in a somewhat self-contained way at the beginning before getting into the code.
I agree that the channel naming/usage could be made more clear, especially in relation to the control channels. I'll try to do this in the next round of changes.

as a simulator tutorial, it may be better to briefly explain how the simulator calculate the dynamics.

I'll try to think of where it is natural to do this.

pulse part

why you don't show pulse sequence? (ie sched[0].draw()?)

👍 I'll add a cell drawing one of the schedules.

below is not related to the notebook but just from curiosity.

why dt is stored in PulseSystemModel class? it is more natural to be in the qobj configuration.

I agree to some extent; though I think in this particular context it is natural. If PulseSystemModel is meant to be the 'simulation/model version' of a real pulse backend, then it does make sense for dt to be stored here, as this is a property of the system as a whole (which includes the control electronics, which do have a fixed sample rate).

what is the reason of CR Rabi rate dependency on control qubit state? I guess there is strong IX interaction induced by higher levels and it is interesting to run echo sequence to remove this (this also shows the validity of physical model).

To be honest I haven't put the time into understanding the physics of the CR driving, so I can't answer that 🤣 . I agree that further exploration of this would be cool in subsequent tutorials (or a more expanded version of this one).
@lcapelluto

Intro comments and ####Duffing system model comment 1

I agree with these three comments; I'll move some pieces (like the Hamiltonian) to the intro, and expand the motivation/description of what's going to happen in the rest of the notebook.

You could consider waiting to mention and explain PulseSystemModel altogether after the code block. They don't really need to know about it until they have just made one, as extra context.

Makes sense.

Could the # time comment over dt be a little more specific? ("timestep" or "sample duration" or "timescale"?)

Is the lone word "time" not enough of an explanation 😆 ?? Will change to "sample duration" or something along these lines.

Cross-resonance ControlChannel indices

first sentence: the object (I'd wonder, what object?) should be replaced with two_qubit_model

👍

E.g. ... is providing an example of what is stated in the first sentence; should it follow that sentence rather than beginning a new paragraph?

👍

Example 1

Would you mind replacing pulse_lib.X with the parametric pulses? This isn't that important, but I think it could be nice.

I'll try this but I'm not sure what will happen. The code in the pulse simulator that interprets pulse schedules is unaware of parametric pulses, so it won't work unless they can be naively interchanged with non-parametric pulses.

I like your qubit_populations_from_memory function! I've been thinking for a while about looking into the results object and adding some utility functions like this to terra

It wasn't originally in a function, but this code (along with most of the notebook) was written by @dcmckayibm  :P.

Example 2

## Drive qubit 1 to observe CR oscillations on qubit 0 this is part of example 2, right? It should be a subheader of Ex 2, not the same level (###)

👍

About parametric pulses: yes they will be assembled to sample pulses since the backend doesn't support it... but it's also fine to leave it as is!

offset from max amp?

@lcapelluto @nkanazawa1989
Thanks again for your comments, I've just updated the tutorial and I think the pedagogy has improved. I've tried to address your comments; the biggest change by far is that I've expanded the intro to explain everything in the notebook at a "physics" level, with a brief description of how this will be performed in the code (as a consequence there is less description throughout the notebook).
@lcapelluto - I switched to parametric pulses, and somehow the issue you pointed out with the pi amplitude not aligning visually with the peak was fixed 😄 / 😢 ???

I think it looks good! In terms of the textbook, I had done something very similar to you @DanPuzzuoli. The Rabi expt part is good for the textbook, but we were thinking of waiting until noise models are added so that we can fully replicate the current textbook chapter (including T1, T2, etc).

Love the changes! This tutorial is seriously awesome. Well written, very valuable new resource. :D
Thank you so much @DanPuzzuoli !!
Some last comments and questions:

I know personally that it is a pain to do this for everything, but it's probably worth it to at least link duffing_system_model to the API reference docs. I've been using markdown style [<backtick>text<backtick>](link). Can't find it in the API reference myself :(
Do people need to know about zvode for these docs?
I didn't realize until Ali mentioned in the meeting that the cutoff dimension is the dimension of the qubit state space. (I guess I thought it could be something more abstract, just the number of terms in some expansion to include, some arbitrary accuracy related value, like p in VQE? Idk) This seems obvious now -- I'm not sure if I was being dense or if it would help to clarify.
When you run the power rabi on qubit 1, you don't have to specify the qubit freq. Was this the case for qubit 0, too? Is the situation special for qubit 1?
"The model generating function duffing_system_model, automatically sets up" I think remove the comma in the middle or add one after 'function'

Yes great work @DanPuzzuoli! Few extra comments on the Duffing oscillator tutorial:
Introduction
Section 1. Duffing oscillator model

remove mentions of zvode/Scipy, don't think the user needs to know how things are solved; I like the mention of the frame. Perhaps add a reference to rotating frame/rotating wave approximation? (Agree w/ Lauren’s point 2)
for Duffing model, I'd add the full Hamiltonian, ie H= and then discuss both terms. I'd also add a sum over all qubits at the front so the full system can be specified.

Section 2. pi pulse calibration

mention Bloch sphere in describing pi pulse
say "larger drive amplitude" rather than "larger amplitude"
I'd note IQ plane and level 1 data when saying "the measurement data is fit"

General:

Maybe call meas_sched->meas_acq_sched since you’re doing both?
Note on what drift means (control terms zero)
The measure and acquire commands are the same for individual qubits and the CR. Perhaps define this pulse at the top as a constant for the entire notebook.

Hi Dan, fashionably late I'm also going over your tutorials - they are great and teach me a lot. If any, I'll send you some further thoughts separately.

Latest changes:

Added table of contents, version table, and copyright
Relabelled section numbers
Simplified Rabi experiment section using Ignis functions as suggested by @dcmckayibm
Renamed the tutorial to match numbered naming conventions

I'd like to wrap this up. Are there any other key/necessary changes, or is this good to go? @ajavadia @nonhermitian @dcmckayibm


Moonbeam dashboard: Missing new registered XC20

Handled in https://github.com/web3go-xyz/moonbeam-data-kit/issues/38


Examples are wrong.

Example 3 is redundant with Example 1.  All examples are invalid in that the -Identity must be the FQDN, and the examples don't show an FQDN, such as "casarray.contoso.org".

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

ID: 4bb3c2ae-13eb-e223-4d3e-a5fb5e35a037
Version Independent ID: 6b4a983d-0183-3409-2f02-2636cce76bc9
Content: Remove-ClientAccessArray (exchange)
Content Source: exchange/exchange-ps/exchange/client-access-servers/Remove-ClientAccessArray.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@curspice, I did some testing on a 2010 SP3 RU20 server. What I found is: the Name value does work as an identifier for Get/Set/Remove-ClientAccessArray, but only if the value doesn't contain spaces. If the name contains spaces, you get an error saying the name is not a valid value for the identity. I tested these other identifier values, and they all worked: ExchangeLegacyDN, FQDN, DistinguishedName, and GUID, so I modified all *-ClientAccessArray topics accordingly.
I also agree that the examples in Remove-ClientAccessArray were redundant, so now there's only one, and it uses the FQDN value as you suggested.
Thanks for the feedback.


Expanded property description

From reading quickly someone may think that setting this to X results in X flowfiles, but in fact it results in X+1. Added explicitly that setting to 0 means no copies.
Not tested.

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
No
[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
No issue, just a description enhancement
[ x] Has your PR been rebased against the latest commit within the target branch (typically main)?
Yes, based of main
[ x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.
Yes

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?
No

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Hey @dennisjaheruddin - is there is a JIRA for this change?


Fix build and test issues on PowerShell v4

Fixed building on PSv4
Fixed tests on PSv4
Added PSv4 to build and test matrix

Visual Studio 2015 OS image in appveyor uses Windows Server 2012 R2.

Resolves #545

This change is

Previously, kapilmb (Kapil Borle) wrote…
> #### Fix build and test issues on PowerShell v4
>
> * Fixed building on PSv4
>
> * Fixed tests on PSv4
>
> * Added PSv4 to build and test matrix
>
>   - Visual Studio 2015 OS image in appveyor uses Windows Server 2012 R2.
>
>
>
> Resolves #545
>
>
>
>
>
>

Comments from Reviewable

Reviewed 20 of 20 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@raghushantha Thanks!


Test making the in-discussion strictInstanceOfTypeParameters flag to always be true

Experimentally always enables https://github.com/microsoft/TypeScript/pull/49863

@typescript-bot pack this
@typescript-bot test this
@typescript-bot test top100
@typescript-bot user test this
@typescript-bot user test tsserver
@typescript-bot test tsserver top100
@typescript-bot run dt
@typescript-bot perf test this

@typescript-bot run dt

I think it already ran DT?
https://github.com/microsoft/TypeScript/pull/53300#issuecomment-1472771069

With the new DT diff, "failed" means something timed out and it couldn't make a diff

The real PR already does this.


fixup passing params to I18n.translate

I18n.translate uses a double splat operator to accept extra parameters
https://github.com/ruby-i18n/i18n/blob/3d0f144038eebe3ff6bc7699de00736abd5ef634/lib/i18n.rb#L196
the double splat operator does not work when the keys are strings
e.g.
def printit(**stuff)
   puts stuff.to_a.join(", ")
end

printit(a: 1, b: 2)
#=> a, 1, b, 2

printit("a" => 1, "b" => 2)
#=> wrong number of arguments (given 1, expected 0)

activity.parameters returns a hash with string keys
so activity.text currently raises a wrong number of arguments error if the activity has any parameters present
to resolve this, change the keys to symbols

@pathouse I’m going to close this PR in favor of https://github.com/public-activity/public_activity/commit/3debdedd5867dcca2b930ff2c2946331dc89caa6 which has been merged and released in https://github.com/public-activity/public_activity/tree/v2.0.0.
Furthermore, I don’t think that your proposed solution is what we’d want to happen. We do want activity.parameters to be splatted for I18n#translate. Its method signature looks as follows:
def translate(key = nil, throw: false, raise: false, locale: nil, **options)

That **options will splat activity.parameters which we wouldn’t want to “bleed” into the other parameters as that would overwrite them with user generated data if we were to symbolize the keys.
Feel free to re-open this PR if the new v2.0.0 is not solving your issue.


IO caused endpoint pods crash with PANIC - fs/fs_napi.cpp line 636

Environment info

NooBaa Version: master-20210517-nsfs
Platform: OCP 4.6.16

Actual behavior

S3 IO caused endpoints crash with PANIC - fs/fs_napi.cpp line 636. The pods didn't recover itself.

Expected behavior

S3 IO shouldn't cause any PANIC into endpoint pods.

Steps to reproduce

Created 3 accounts and 3 buckets - bucket-1, bucket-2.
bucket-1 = /nsfs/parent
bucket-2 = /nsfs/parent/dir2
bucket-3 = /nsfs/parent/dir3

Started IO on all 3 buckets using warp tool. It worked fine for 3 hours

Found IO failing and endpoint crashed.

PANIC: FS::FileWrap::dtor: file not closed _path=/nsfs/parent/40UbANZ0/12170.)kvvRTgTbfzdlEAY.rnd _fd=60  function ~FileWrap file ../src/native/fs/fs_napi.cpp line 636
[root@ocp-akshat-1-inf ~]# oc get pod -n noobaa
NAME                                               READY   STATUS                 RESTARTS   AGE
noobaa-core-0                                      1/1     Running                0          2d2h
noobaa-db-0                                        1/1     Running                0          2d2h
noobaa-default-backing-store-noobaa-pod-8f3b3033   0/1     Terminating            0          44h
noobaa-endpoint-75cf4844f6-858s5                   0/1     CreateContainerError   0          17h
noobaa-endpoint-75cf4844f6-rd6dd                   0/1     CreateContainerError   0          17h
noobaa-operator-fc5dbbb74-czm9l                    1/1     Running                0          2d4h

More information - Screenshots / Logs / Other output
oc describe pod o/p:
Events:
  Type     Reason                  Age                  From                     Message
  ----     ------                  ----                 ----                     -------
  Normal   Scheduled               16h                  default-scheduler        Successfully assigned noobaa/noobaa-endpoint-75cf4844f6-858s5 to worker2.ocp-akshat-1.cp.fyre.ibm.com
  Normal   SuccessfulAttachVolume  16h                  attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-950b978c-d1c8-40fb-bc76-6d5f0e385d00"
  Normal   AddedInterface          16h                  multus                   Add eth0 [<IP_ADDRESS>/22]
  Normal   Created                 16h                  kubelet                  Created container endpoint
  Normal   Started                 16h                  kubelet                  Started container endpoint
  Warning  Failed                  14m                  kubelet                  Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving ctr name k8s_endpoint_noobaa-endpoint-75cf4844f6-858s5_noobaa_96a4c576-dea6-4a3d-bf0d-a0e04c222e2d_1 for id 149cb68bdb7a921acfe862f2de49df3e3d7ece5016ddbf1b7fc4aad42f20db62: name is reserved
  Warning  Failed                  13m                  kubelet                  Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving ctr name k8s_endpoint_noobaa-endpoint-75cf4844f6-858s5_noobaa_96a4c576-dea6-4a3d-bf0d-a0e04c222e2d_1 for id 90e2dc7c83635bf77efd191da85647bc370722b23221493b28261fe54edbdec8: name is reserved
  Warning  Failed                  13m                  kubelet                  Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving ctr name k8s_endpoint_noobaa-endpoint-75cf4844f6-858s5_noobaa_96a4c576-dea6-4a3d-bf0d-a0e04c222e2d_1 for id b6ca2a47853aec6c24c3189b06b3394553ad6167cedd2517dc305af7a0f7704e: name is reserved
  Warning  Failed                  11m (x2 over 14m)    kubelet                  Error: context deadline exceeded
  Warning  Failed                  11m                  kubelet                  Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving ctr name k8s_endpoint_noobaa-endpoint-75cf4844f6-858s5_noobaa_96a4c576-dea6-4a3d-bf0d-a0e04c222e2d_1 for id f6fe249d90a6b3869efc9a05255443fa8555b61c82fdb575d38c142a008556f9: name is reserved
  Warning  Failed                  10m                  kubelet                  Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving ctr name k8s_endpoint_noobaa-endpoint-75cf4844f6-858s5_noobaa_96a4c576-dea6-4a3d-bf0d-a0e04c222e2d_1 for id 851dec4290d400b07210ec89192ae5a3a5944fbcc6ba8dbb413d336a804835e1: name is reserved
  Warning  Failed                  10m                  kubelet                  Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving ctr name k8s_endpoint_noobaa-endpoint-75cf4844f6-858s5_noobaa_96a4c576-dea6-4a3d-bf0d-a0e04c222e2d_1 for id 04dbc5b32fca71e4ab8e7f1acb0a723c049a4bd26a1c8d639c0e22fb4e031fbd: name is reserved
  Warning  Failed                  10m                  kubelet                  Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving ctr name k8s_endpoint_noobaa-endpoint-75cf4844f6-858s5_noobaa_96a4c576-dea6-4a3d-bf0d-a0e04c222e2d_1 for id 37682bbd17f9d32e7e7a83e0a31ea9c62809f1721e5d5f49eef9692fa3e5d4c6: name is reserved
  Warning  Failed                  10m                  kubelet                  Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving ctr name k8s_endpoint_noobaa-endpoint-75cf4844f6-858s5_noobaa_96a4c576-dea6-4a3d-bf0d-a0e04c222e2d_1 for id b7b804e583830971c4ffc84baf12282b5a9294387fc12b1c96f16f1482262cf1: name is reserved
  Warning  Failed                  9m34s (x3 over 10m)  kubelet                  (combined from similar events): Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving ctr name k8s_endpoint_noobaa-endpoint-75cf4844f6-858s5_noobaa_96a4c576-dea6-4a3d-bf0d-a0e04c222e2d_1 for id aa1678edacd631cb32c28de0ae08d2c214ca8a5e3d8f939ddb239c06d3622bcd: name is reserved
  Normal   Pulled                  49s (x45 over 16h)   kubelet                  Container image "noobaa/noobaa-core:master-20210517-nsfs" already present on machine

Endpoint logs:

May-20 8:19:29.944 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/GWSpn5Kf/15709.gXDwjTLU3ESLQYD9.rnd', start: 0, end: Infinity }
May-20 8:19:29.946 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/cWaCm3os/10977.saEz7SN97DuIP(Hj.rnd', start: 0, end: Infinity }
May-20 8:19:29.947 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/dir3/1UExk9Wr/16891.vJ3t5ObdkSplwu)d.rnd', start: 0, end: Infinity }
May-20 8:19:29.947 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/40UbANZ0/17582.0v3a6EzWjfa61GIz.rnd', start: 0, end: Infinity }
May-20 8:19:29.947 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/AaqxCrtW/9558.O6nnXvJj2pSu2cEF.rnd', start: 0, end: Infinity }
May-20 8:19:29.948 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/5Ubo6tPF/16848.8TU4ypThrL68ipX1.rnd', start: 0, end: Infinity }
May-20 8:19:29.948 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/40UbANZ0/12170.)kvvRTgTbfzdlEAY.rnd', start: 0, end: Infinity }
May-20 8:19:29.948 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/(pSD6yAw/14150.6)M(kABek6dGW1z3.rnd', start: 0, end: Infinity }
May-20 8:19:29.948 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/jJrtTrxU/6788.DP7PzTnn2AYcSgU3.rnd', start: 0, end: Infinity }
May-20 8:19:29.948 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/dir3/xsDKdVcg/14803.hV0SPIc1XgSJPRBo.rnd', start: 0, end: Infinity }
May-20 8:19:29.948 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/cWaCm3os/17288.GRZa)KQdcbbiPWZI.rnd', start: 0, end: Infinity }
May-20 8:19:29.948 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/dir3/Cpt2pD0V/17421.Ksh6e8RM(lQEE9zn.rnd', start: 0, end: Infinity }
May-20 8:19:29.948 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/bzTjC)PM/16817.SzOPNeXARQ8DpN35.rnd', start: 0, end: Infinity }
May-20 8:19:29.948 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/dir3/Q5pDc(jq/9954.5RNU5CQCty6Ty)fp.rnd', start: 0, end: Infinity }
May-20 8:19:29.949 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/GWSpn5Kf/16037.C3VHKcqzayzwaWYS.rnd', start: 0, end: Infinity }
May-20 8:19:29.949 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/dir3/ittPiDnZ/15200.UjHTbm94mpZndxN1.rnd', start: 0, end: Infinity }
May-20 8:19:29.949 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/cWaCm3os/10977.saEz7SN97DuIP(Hj.rnd', start: 0, end: Infinity }
May-20 8:19:29.951 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/dir3/g7OCfjlX/9327.j(7(PnvRXeqnvdhq.rnd', start: 0, end: Infinity }
May-20 8:19:29.966 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/(pSD6yAw/16737.xSBJcaXsatoLLT4z.rnd', start: 0, end: Infinity }
May-20 8:19:29.967 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/HXnAtEDC/14784.8uU7KWHgmqisiTul.rnd', start: 0, end: Infinity }
May-20 8:19:29.967 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/GWSpn5Kf/15709.gXDwjTLU3ESLQYD9.rnd', start: 0, end: Infinity }
May-20 8:19:29.967 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/dir3/1UExk9Wr/17073.tPWjlbQ)DRbwwnXF.rnd', start: 0, end: Infinity }
May-20 8:19:30.011 [Endpoint/8]   [LOG] CONSOLE:: NamespaceFS: read_object_stream { file_path: '/nsfs/parent/dir3/IY5uF(yW/12269.SK8CIMURlP2HZLJa.rnd', start: 0, end: Infinity }
PANIC: FS::FileWrap::dtor: file not closed _path=/nsfs/parent/40UbANZ0/12170.)kvvRTgTbfzdlEAY.rnd _fd=60  function ~FileWrap file ../src/native/fs/fs_napi.cpp line 636
/noobaa_init_files/noobaa_init.sh: line 74:     8 Aborted                 $*

######################################################################
Thu May 20 08:19:30 UTC 2021 NooBaa: Process exited RIP (RC=134)
######################################################################

noobaa_diagnostics_1621500574.tar.gz

Looks like a duplicate of https://github.com/noobaa/noobaa-core/issues/6566

@akmithal can we dup into 6566 ?

Closing as dup of 6566


Null checks on fields

Whenever we retrieve a value from the json field, we use .toString() which could throw NullPointerException. That field may be allowed to have null but since we have .toString() we would end up with NPE. This PR aims at avoiding such NPE. Its a better alternative to null check.
More info on this approach is here
Note : This PR contains the changes made in #6  too.

@aarahmanqa can you resolve the merge conflicts for this pull request after that i'll test the code and merge accordingly.

@shivam1608 , sorry for delay. I have resolved conflicts. Kindly review it.

@aarahmanqa  np for delays , currently i don't have my pc with me, i'm using my mobile. i'll soon check the commits when i reach home.

@shivam1608 , could you please review the PR and get it merged?


[196] Make language switcher mobile friendly

Fixes https://github.com/ensdomains/ensdomains-v2/issues/196 and https://github.com/ensdomains/ensdomains-v2/issues/314
Fix applies to both mobile and desktop when the screen can't fit the full list by making it scrollable if the list takes over 60vh

Works the same as it does currently if the list can fit (no scrolling needed)

Thanks for this!


[WIP] Accommodate upstream V8 6.7 API changes

[ ] Decide if Isolate#idle_notification should be removed
[ ] Debug why MiniRacerTest#test_isolate_can_be_notified_of_idle_time fails and if the test itself makes sense
[ ] Wait for a stable libv8 6.7 release

@wk8 what is your call here, I am merging this in for now and correcting test / removing interface

@wk8  what is your call here?

OK I fixed the idle_notification stuff, but am still getting segfaults... @ignisf  any chance you can do a v8 release with symbols?

sure

https://github.com/cowboyd/libv8/releases/download/v6.7.288.46.1beta0/debug-libv8-6.7.288.46.1beta0-x86_64-linux.gem
It seems it has some debugging checks enabled which cause the test suite to fail with SIGABRT, which actually might be helpful. :)
Just uninstall the nondebug version, download the debug binary, install it with gem install ./debug-*, and recompile mini_racer

I commented out the tests that were failing due to debug checks and ran while (true); rake test; done.
The test_undef_mem failed periodically. Here's a backtrace: https://gist.githubusercontent.com/ignisf/6fb047e9582aa9b3f257502d71ddd619/raw/80c772634461550cde3690c9e8c96950ae7b9008/gistfile1.txt


fix: remove useDataGrid columns dependency

The useDataGrid hook required the columns property. Since this situation gives us some difficulties, we will remove the column dependency.

This PR is mentioned in and planned to resolve the issue https://github.com/pankod/refine/issues/2062


Tflite metal gpu ios model reload

My target is ios device ,Target backend is metal gpu , Durining our test ,I found that 'memory leak'  occured when switch different models  about 100 times ,so  how to release last neural models ?like below:
interpreter=nullptr
DeleteGpuDelegate(delegate)
is it right ?

@zuoshaobo It looks, This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there and provide greater support. If you think it is a bug. Please let us know. Thanks!

Closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Some improvements

Hello,
First for all, the Appear.in is a good software. 👍
I think there are some things that can improve! And this pull request were little changes, like:

Check if the first parameter on addRoomToIframe is a valid iframe element. Refs #2
When calling the addRoomToElementById and not exists, improve the error message.
Validate if is a reserved name on normalize function.
Refactor the tests for use chai.
Create tests for RoomUtil.

Feel free to accept it or not. :)

Hmm, the CI failed.
I believe is a problem with the .travis.yml configuration.

Hello @dagingaa, my home is veery far from Norway! :laughing: Is in Brazil!

One of our team members is from Brazil! We don't mind shipping stuff far ;)

Do you know why the CI failed? On my machine, the tests works fine.


Removal of window borders

The window border functionality has had issues ever since macOS Ventura launched, and these issues persist in macOS Sonoma.
Some of these issues include, but are not limited to: incorrect z-ordering, incompatibility with window animations, incompatibility with topmost windows, weird lag upon window focus, inability to properly match corner radius of attached window, mission-control jankiness.
I will be removing this feature in an upcoming version of yabai.
Most of these issues are fairly trivial to solve iff the Apple WindowManager process is prevented from loading, as mentioned in various issues by @felixkratz, but I am not interested in going that route.
It should not be particularly hard for a fork to reintroduce window borders in a patch if they wish to do so.

Just to let you know @koekeishiya , I don't even know why I had expose as a shortcut in skhdrc as I have no use for it. When I did enter expose, I saw that borders was still there. Mentioning just in case you missed it!
yabai -m window --toggle expose

will miss this feature 😢

Expose has its own borders ))

Are there any alternatives to use? It's more difficult to distinguish the highlighted window without any window border color.

Window borders was an amazing feature that is really worth keeping. Very sad to see it go. Hope you'll change your mind.

Does anyone know of an alternative to highlight the currently active window now that borders have been removed?

Sad to see it go. For me this is a regression in the feature set for a tiling window manger. inb4 "make your own fork"

Sad to see it go. For me this is a regression in the feature set for a tiling window manger. inb4 "make your own fork"

The same has happen to i3, the original developer did not want to implement gaps and a fork was created just to add gaps. Just last year gaps have been merged into the original i3wm. Maybe down the line if someone figures a way to make it work without any problem it can be merged back into Yabai. Being a free project, I'm just glad Yabai exist!

Focusing on performance is indeed great. But I’ll have a hard time adjusting to this. I could consider using a fork that re-enables Borders, but I'm not technically proficient enough. Is there anyone else who has an alternative solution? Is there another app that highlights the active window in any way (it mustn’t be borders) without dimming the others?

In case someone is interested, you can add the borders back by using hammerspoon. Unfortunately it's not perfect yet, as theres a delay as well as no support for rounded borders, but knowing which window is active is more important in my opnion. Here's the snippet for anyone interested. Feel free to change and comment, i'm interested in improvments.

In case someone is interested, you can add the borders back by using hammerspoon. Unfortunately it's not perfect yet, as theres a delay as well as no support for rounded borders, but knowing which window is active is more important in my opinion. Here's the snippet for anyone interested. Feel free to change and comment, i'm interested in improvements.
-- fix the window border issue, as the option was deleted from yabai
local windowfilter = require 'hs.window.filter'
local defaultFilter = windowfilter.default
local indicatorWIN = nil

local function drawBorder()
  -- Delete the old border if it exists
  if indicatorWIN then
    indicatorWIN:delete()
  end

  local win = hs.window.focusedWindow()
  local screen = win:screen()
  local max = screen:fullFrame()
  local f = win:frame()
  indicatorWIN = hs.canvas.new { x = max.x, y = max.y, h = max.h, w = max.w }:appendElements({
    type = "rectangle",
    action = "stroke",
    strokeWidth = 1.0,
    -- strokeColor = { red = 1.0 },
    strokeColor = { red = 250/255, green = 189/255, blue = 47/255 },
    frame = { x = f.x, y = f.y, h = f.h, w = f.w }
  }):show()
end

defaultFilter:subscribe(windowfilter.windowFocused, function()
  drawBorder()
end)

defaultFilter:subscribe(windowfilter.windowMoved, function()
  drawBorder()
end)

Hammerspoon is far from perfect for that case. Better to you Felix's fork, as described by robrecord https://github.com/koekeishiya/yabai/issues/1889#issuecomment-1761253731

Is it possible to leave the option for users to use window borders, allowing us to choose whether we want the performance loss or not?

It is not a matter of "performance loss". The functionality has literally been broken since the launch of macOS Ventura. See the 19 related issues for more details.

I have been using borders on Ventura without issues. I don't use any animation nor expose or any macOS WM stuff (mainstage) though so it might not work with those I wouldn't know. I sincerely appreciate the hours put in to this project and I'm well aware of https://mikemcquaid.com/open-source-maintainers-owe-you-nothing/. That said removing a quite essential feature without much warning or switch to re enable "unsupported" feature seems like an odd choice. I respect that this is your project and ultimately you are in charge - I think this seems so out of the blue.
Especially for those of us that have not been aware, or choose to ignore the minor issues with the borders.

I'm very grateful for your work @koekeishiya on yabai, as it really makes working on my Mac a great experience.
Having said that, I really really have a hard time now that I don't know which of my windows has focus. Frankly, yabai has now lost a lot of its value for me...
I do understanding though the rationale for removing it, and I also don't think it makes sense to keep a broken feature, as it only creates more hassle the more time passes.
But we're still left with the core problem: how can I easily identify the active window now?
Does anyone have a suggestion on what can be done, within the confines of the current version, on how to do this?

I completely agree with @aragalie. Yabai has helped me immensely over the years. Borders is the feature that made me use Yabai and not Amethyst.
The only possible solution not mentioned here is window opacity. You can increase the transparency of inactive windows with this feature. I do not find this solution usable though.

I completely agree with @aragalie. Yabai has helped me immensely over the years. Borders is the feature that made me use Yabai and not Amethyst.
The only possible solution not mentioned here is window opacity. You can increase the transparency of inactive windows with this feature. I do not find this solution usable though.

I fully agree. Unfortunately using transparency is not an option for silicon macs when one's using ios apps hence disabling sip is not possible.

I mean I get it, I liked borders too when they worked, but I am the one dealing with all the support requests. As I said, all you have to do is look through the 19 issues connected to this one to get an idea of how exhausting that is.

I think you are severly underestimating the number of people who go "fuck this" when something does not work, rather than reporting the issue. I know because I am usually one of them.
I don't have issues with ungrateful people or whatever; I make decisions that I personally think are the correct way to go, and this happens to be one of them. If someone disagrees with decisisons that I make they are free to make a fork or buid their own software.

@koekeishiya I completely understand you, as you offer your precious free time to develop and maintain this amazing tool. It's become irreplaceable in many people's daily workflow, including my own. Meaning: Thanks for your hard work!
In that sense, I do think this still leaves the core problem: How to identify an active window?
I can not, and probably would not if i had a choice, deactivate SIP, so any transparency configurations do not work, besides other things.
As the borders are now gone, it has become impossible for me to identify an active window. Yabai is still valuable as a window manager, however if it is impossible to identify the current window, it becomes useless to fulfill this function. This a hard problem, that needs to be addressed, regardless of borders or not.
Side Note
Without deactivating SIP, certain things like switching, moving and refocusing apps to different desktop besides others are not possible, therefor i've been scripting my way around this with hammerspoon and lua. I've been able to do all things that i've been missing, including borders. However this is not ideal, only showcases that it is possible. Reason I am saying this is: It is possible, even with SIP, to do everything. (excluding transparency, i've tried with overlays with it's not ideal) Maybe there is a way for yabai as well.

Just spitballing here, but would it be possible/feasible to pull the border highlighting functionality into its own standalone tool? My understanding is that this used to be the case (limelight?) so presumably there was a technical reason it needed to be pulled into yabai proper, but it does seem to me that conceptually at least, this is a completely orthogonal feature to the core of what yabai does, so if there is any way this could be done then maybe that would be the way forward that addresses the stability concerns while also giving folks the option of having the highlights if they really want it?

@DetachedHeadState I think this is more that possible to extract the features. Limelight is probably not feasible to pick up development on again however).
If you look at https://github.com/FelixKratz/SketchyBar for instance it uses the same hooks into Skylight and CoreGraphics and it is probably the result of yabai removing the top bar ages ago (Spacebar was the first to port the top bar functionallity out of yabai iirc).
However both SketchyBar and yabai uses non public apis which are inherently hard to debug and requires a bit more finessing than just your run of the mill application.

I had some free time yesterday and hacked together a new standalone border system: https://github.com/FelixKratz/JankyBorders
It does not use the accessibility API at all and should thus be faster.

I had some free time yesterday and hacked together a new standalone border system: https://github.com/FelixKratz/JankyBorders
It does not use the accessibility API at all and should thus be faster.
Feel free to contribute.

Thanks! Will try soon.

Outstanding. Lightning fast borders, like it should be. Thank You.

Thanks, @FelixKratz, really appreciate your efforts, you are a lifesaver :)

@FelixKratz you are the goat bruh.

I am on macos 12 so I should not be affected by the border issues but I upgraded yabai to v6.0.1 (my mistake, I didn't know the borders would be removed)
Is there any way for me to return to v5.0.9? homebrew has only the latest version and installing from source again only has the option --HEAD to install latest code.

@FelixKratz Thanks for the additional tool, works great! 🙌🙌🙌

I am on macos 12 so I should not be affected by the border issues but I upgraded yabai to v6.0.1 (my mistake, I didn't know the borders would be removed) Is there any way for me to return to v5.0.9? homebrew has only the latest version and installing from source again only has the option --HEAD to install latest code.

I forked the Homebrew formula and rolled it back to the v5.0.9 commit. You can install that version like:
brew install SichangHe/yabai5/yabai

Upgrade to yabai v6.0.7 and use https://github.com/FelixKratz/JankyBorders instead.

coool will try
On Fri, 26 Jan 2024 at 5:17 PM, Åsmund Vikane @.***>
wrote:

Upgrade to yabai v6.0.7 and use https://github.com/FelixKratz/JankyBorders
instead.
—
Reply to this email directly, view it on GitHub
https://github.com/koekeishiya/yabai/issues/1889#issuecomment-1911722673,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIHB3TY2FSTS7K2N65AWST3YQNYDDAVCNFSM6AAAAAA5ZQB3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJRG4ZDENRXGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Missing includes for in6_addr / AF_INET*, fixes compilation on OpenBSD

Coverage remained the same at 91.532% when pulling 9f0b09e830dd9e5a09d0c9cb47d66b5204c46071 on fcambus:master into 65e785e1ca8df3068047c842fc34bd43a99fa8e5 on rockdaboot:master.

Thanks !


Fixing Kind 2.0 XML Stuff

I merged in the XML parse stuff, but threw away the classpath and other configuration specific things.


Fix for building and passing tests for 32-bit archs

Hi,
I suppose NCLS is compatible to run with 32-bit archs right?
The tests actually seem to fail with those archs due to very large values as well as type mismatch at a couple of points.
This is my attempt to fix it.
I tried testing it in a 32-bit environment and it works.

@endrebak this is a bug in Debian with NCLS failing in 32-bit arches. Could you please review this?

Thanks! I will do so after work today :)

I will need to look more closely. This might break macOS. Let me test.

I am not an expert on C types, but long means different things on different architectures, I think. So it is best to use int64_t, not long.
The test is for 64-bit architectures (actually, I do not test NCLS directly, only indirectly through the extensive tests in pyranges).
Why does the build fail on 32-bit architectures?
Wouldn't it be better to just skip the tests on 32-bit architectures?
I need more context. I think by using long instead of int64_t you are going to break NCLS for windows.

I am not an expert on C types, but long means different things on different architectures, I think. So it is best to use int64_t, not long.

I'm not sure here - if the dtype of output_arr is np.long, why should the datatype of output be int64_t?
This lead to a build failure leading to inconsistent types here.

The test is for 64-bit architectures (actually, I do not test NCLS directly, only indirectly through the extensive tests in pyranges).

OK,

Why does the build fail on 32-bit architectures?

Because of two things:

The values assigned in the numpy arrays in the test suite are extremely large and unsuited for 32-bit archs. The log for the same can be seen here

The assignment of output_arr to output is incompatible due to the former being a long  dtype. This is a bigger problem since this means that the function is broken for 32-bit archs.

Wouldn't it be better to just skip the tests on 32-bit architectures?

That can be an option but it might be better to actually fix the problem instead.

I need more context. I think by using long instead of int64_t you are going to break NCLS for windows.

I admit, I don't use windows. Maybe modifying .travis.yml can give us the results?
Again, since you're the author of the package you are much more aware of how this works - please let me know what you'd think should be the best solution?

I will try to make the types consistent. I will also look into how to check whether we are testing in a 32-bit arch. Then I can run the appropriate tests for 32 and 64-bit arches.

Does 0.0.55 work? I've added a check in the tests to see whether we are on a 32 or 64-bit architecture: https://github.com/biocore-ntnu/ncls/blob/master/tests/test_ncls.py

Just tested it.  I've modified the PR accordingly.
diff --git a/tests/test_ncls.py b/tests/test_ncls.py
index 0637b5a..cc4a4c3 100644
--- a/tests/test_ncls.py
+++ b/tests/test_ncls.py
@@ -46,7 +46,7 @@ if struct.calcsize("P") * 8 == 64:
         assert list(subs) == [0, 1] == list(covers)

 else:
-
+
     starts = np.array([5, 2_147_483_645], dtype=np.int64)

     ends = np.array([6, 2_147_483_646], dtype=np.int64)
@@ -71,9 +71,9 @@ else:

     def test_all_containments_both():

-        starts = np.array([5, 10], dtype=int)
-        ends = np.array([6, 50], dtype=int)
-        ids = np.array([0, 1], dtype=int)
+        starts = np.array([5, 10], dtype=np.int64)
+        ends = np.array([6, 50], dtype=np.int64)
+        ids = np.array([0, 1], dtype=np.int64)

         ncls = NCLS(starts, ends, ids)
         subs, covers = ncls.all_containments_both(starts, ends, ids)

Also, could you please tag NCLS with a 0.055 github release? It'd enable me to update the same package in Debian accordingly.

I am confused though. Shouldn't it be np.int32 if you want to use it on a 32-bit architecture?

Can you try with int32 instead of int64 and confirm that it still works?

I've uploaded 0.0.56 where I corrected the test. It uses 32-bits consistently. I had made some sloppy mistakes, sorry.

I've again pushed what works in the PR, please consider merging and tagging this with the new (github)release
This is the output with the patch applied:
=============================================================================================== test session starts ================================================================================================
platform linux -- Python 3.8.6, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
rootdir: /ncls/python-ncls
collected 2 items

tests/test_ncls.py ..                                                                                [100%]

============================================================================================= 2 passed in 0.20 seconds =============================================================================================
	rm -fr -- /tmp/dh-xdg-rundir-nRu9sb2c

@endrebak thanks a lot for your fixes and work. Could you please tag a git release to 0.0.56 so I can upload this new version which would fix NCLS in Debian?

Alrighty, it's done. Super thanks!

I am so happy we were able to find a solution :)


Drop Node 8 support

Because it's EOL.
It's probably a good idea to wait for ESLint 7, since that will drop Node 8.
https://github.com/eslint/eslint/releases/tag/v7.0.0-alpha.0
https://github.com/eslint/eslint/pull/12700
We can also drop support for older ESLint versions then, since we're doing a major release anyways.

No, because EOL status is utterly irrelevant, and dropping support for EOL nodes makes it harder for those users to upgrade.
This package still supports eslint 3, and will do so for as close to forever as i can manage (i maintain 200+ packages that support down to node 0.4), and thus it will support all node versions eslint 3+ works on.


wtf implementation?

flask-bootstrap have pre-made wtf.html within the package. can I request the same with your package?

Hi, thanks for the suggestion, I did not use flask-bootstrap before, so I did not know what they do with that, I suppose it is about pre-defined macros for forms/fields rendering?
For field rendering, what I am using now is simply pass in class attributes, e.g:
{% macro render_form_field(field) %}
{% if field.type == 'BooleanField' %}

{% for error in field.errors %}
{{ error }}
{% endfor %}
{{ field.label.text|safe }}
{{ field(**kwargs) }}

{% else %}
{% set required = kwargs.pop('required', field.flags.required) %}
{# default to 100% width #}
{% set class_ = kwargs.pop('class_', 'pure-input-1') %}
{{ field.label }}
{% for error in field.errors %}
{{ error }}
{% endfor %}
{{ field(class_=class_, required=required, **kwargs) }}
{% endif %}
{% endmacro %}

Do we need anything fancier beyond that?

It doesn't catch flask_wtf File validators.
example, I need to filter the file to be allowed in the FileField.


Created RR Dec 21 Summary post

RR Dec 21 initial draft.

Updated image

Added Jan 2 summary post and image

Added post for 1-4-24 and related image


[AMORO-2401] Support reading encrypted iceberg data files

Why are the changes needed?

Close #2401.
Brief change log

As described in #2401

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? no

@liaoyt Thanks a lot for your contribution!
You may need to sign NetEase's CLA before you start to contribute to Amoro, you can conveniently complete the signing via the link: https://cla-assistant.io/NetEase/amoro

@liaoyt Thanks a lot for your contribution!
You may need to sign NetEase's CLA before you start to contribute to Amoro, you can conveniently complete the signing via the link: https://cla-assistant.io/NetEase/amoro

thanks for reminding, already signed

@liaoyt Thanks for your contribution，I want to know if you are currently using the encryption feature.

@liaoyt Thanks for your contribution，I want to know if you are currently using the encryption feature.

yes, although iceberg has only PlaintextEncryptionManager currently, we implement a custom encryption manager

@liaoyt Thanks for your contribution，I want to know if you are currently using the encryption feature.

yes, although iceberg has only PlaintextEncryptionManager currently, we implement a custom encryption manager

I am very interested in this area. How does your EncryptionManager work? Currently, the implementation of BaseTable does not provide a custom method. Did you wrap your own Table object?

@liaoyt Thanks for your contribution，I want to know if you are currently using the encryption feature.

yes, although iceberg has only PlaintextEncryptionManager currently, we implement a custom encryption manager

I am very interested in this area. How does your EncryptionManager work? Currently, the implementation of BaseTable does not provide a custom method. Did you wrap your own Table object?

There is not custom method provided currently, we just overwrite the TableOperations.encryption() method to provider our custom EncryptionManager.
Also, we patch some of the PR in this project: https://github.com/apache/iceberg/projects/5

As for the behavior of reading data file of iceberg table, iceberg already implement it. This PR attempt to keep this behavior the same as iceberg do.

@liaoyt Thanks for your contribution，I want to know if you are currently using the encryption feature.

yes, although iceberg has only PlaintextEncryptionManager currently, we implement a custom encryption manager

I am very interested in this area. How does your EncryptionManager work? Currently, the implementation of BaseTable does not provide a custom method. Did you wrap your own Table object?

There is not custom method provided currently, we just overwrite the TableOperations.encryption() method to provider our custom EncryptionManager. Also, we patch some of the PR in this project: https://github.com/apache/iceberg/projects/5

I got you, BTW, GenericDeleteFilter also need EncryptionManager

@liaoyt Thanks for your contribution，I want to know if you are currently using the encryption feature.

yes, although iceberg has only PlaintextEncryptionManager currently, we implement a custom encryption manager

I am very interested in this area. How does your EncryptionManager work? Currently, the implementation of BaseTable does not provide a custom method. Did you wrap your own Table object?

There is not custom method provided currently, we just overwrite the TableOperations.encryption() method to provider our custom EncryptionManager. Also, we patch some of the PR in this project: https://github.com/apache/iceberg/projects/5

I got you, BTW, GenericDeleteFilter also need EncryptionManager

thanks for reminding, i'll have a look and fix it later, maybe tomorrow.

Can you add some unit tests to verify if it's working?

Can you add some unit tests to verify if it's working?

sure，i can try add some unit test

Thanks for your contributions


As well as more, and more representative Android.


fix Prevent concurrent accessing to dependencies

Proposed changes
Issue Number: close #xxx

If a pipeline task is cancelled by another thread during executing extract_dependencies, dependencies will be accessed by different read/write threads which will lead to serious result.

run buildall


146 -> v1-release Dropdown value container modalIsOpen issue

:tada: This PR is included in version 1.0.0-v1-release.21 :tada:
The release is available on:

npm package (@v1-release dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

: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:


git alias evaluates at the time of loading profile

Code of Conduct

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

What happened?
aliae config
alias:
  - name: db
    value: "!basename $(git symbolic-ref refs/remotes/origin/HEAD)"
    type: git

after reloading profile git config looks like this
[alias]
db = "!basename "

or like this if reloaded in context of git repository
[alias]
db = !basename refs/remotes/origin/master

expected to see this
[alias]
db = !basename $(git symbolic-ref refs/remotes/origin/HEAD)

What OS are you seeing the problem on?
Windows, Linux
Which shell are you using?
bash, powershell

@harrhp this is a tricky one. That statement, when evaluated by the shell will always execute in the evaluation. This can be intentional or not, so how do we distinct between that?


Structuring frontend and merging latest routing implementation

god forgive me for my choices i regret wanting to use high abstractions layering

by the way i removed most properties that would make it look compelx in products just to make it less painful to work on


Would it be possible to add a controller?

Hi, thank you for this package, it's amazing and works out of the box.
Would it be possible in the future to add a controller that will allow for starting/stopping/resetting the animation?

It's now supported in the latest version. See usage at https://pub.dev/packages/svg_drawing_animation#custom-animation.