[CI] New version of urllib3 seems to be causing GCS tests to fail

Describe the bug, including details regarding any error messages, version, and platform.
The GCS tests all started failing (e.g. this example).
From a diff with the most recent passing version it seems the only thing that changed is the urllib3 version:
Old: urllib3-1.26.15-py2.py3-none-any.whl
New: urllib3-2.0.1-py3-none-any.whl
This seems unlikely to be related to gcs3 but...the error is below and seems to be related to urllib3 so maybe this isn't so far fetched.
2023-05-03T17:56:54.4311843Z Traceback (most recent call last):
2023-05-03T17:56:54.4312710Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\_compat.py", line 48, in <module>
2023-05-03T17:56:54.4314727Z     from requests.packages.urllib3.contrib import appengine as gaecontrib
2023-05-03T17:56:54.4319747Z ImportError: cannot import name 'appengine' from 'requests.packages.urllib3.contrib' (C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\urllib3\contrib\__init__.py)
2023-05-03T17:56:54.4323850Z
2023-05-03T17:56:54.4325424Z During handling of the above exception, another exception occurred:
2023-05-03T17:56:54.4339984Z
2023-05-03T17:56:54.4341483Z Traceback (most recent call last):
2023-05-03T17:56:54.4342016Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\runpy.py", line 183, in _run_module_as_main
2023-05-03T17:56:54.4342462Z     mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
2023-05-03T17:56:54.4342905Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\runpy.py", line 142, in _get_module_details
2023-05-03T17:56:54.4343532Z     return _get_module_details(pkg_main_name, error)
2023-05-03T17:56:54.4343965Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\runpy.py", line 109, in _get_module_details
2023-05-03T17:56:54.4344341Z     __import__(pkg_name)
2023-05-03T17:56:54.4344771Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\testbench\__init__.py", line 15, in <module>
2023-05-03T17:56:54.4345166Z     from . import (
2023-05-03T17:56:54.4345597Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\testbench\common.py", line 31, in <module>
2023-05-03T17:56:54.4346056Z     from requests_toolbelt import MultipartDecoder
2023-05-03T17:56:54.4346538Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\__init__.py", line 12, in <module>
2023-05-03T17:56:54.4347029Z     from .adapters import SSLAdapter, SourceAddressAdapter
2023-05-03T17:56:54.4347881Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\adapters\__init__.py", line 12, in <module>
2023-05-03T17:56:54.4348350Z     from .ssl import SSLAdapter
2023-05-03T17:56:54.4348821Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\adapters\ssl.py", line 16, in <module>
2023-05-03T17:56:54.4349270Z     from .._compat import poolmanager
2023-05-03T17:56:54.4349768Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\_compat.py", line 50, in <module>
2023-05-03T17:56:54.4350245Z     from urllib3.contrib import appengine as gaecontrib
2023-05-03T17:56:54.4350808Z ImportError: cannot import name 'appengine' from 'urllib3.contrib' (C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\urllib3\contrib\__init__.py)
2023-05-03T17:56:54.4351658Z Traceback (most recent call last):
2023-05-03T17:56:54.4352696Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\_compat.py", line 48, in <module>
2023-05-03T17:56:54.4353228Z     from requests.packages.urllib3.contrib import appengine as gaecontrib
2023-05-03T17:56:54.4353887Z ImportError: cannot import name 'appengine' from 'requests.packages.urllib3.contrib' (C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\urllib3\contrib\__init__.py)
2023-05-03T17:56:54.4354307Z
2023-05-03T17:56:54.4354502Z During handling of the above exception, another exception occurred:
2023-05-03T17:56:54.4354733Z
2023-05-03T17:56:54.4354860Z Traceback (most recent call last):
2023-05-03T17:56:54.4355275Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\runpy.py", line 183, in _run_module_as_main
2023-05-03T17:56:54.4355883Z     mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
2023-05-03T17:56:54.4356925Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\runpy.py", line 142, in _get_module_details
2023-05-03T17:56:54.4357517Z     return _get_module_details(pkg_main_name, error)
2023-05-03T17:56:54.4358523Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\runpy.py", line 109, in _get_module_details
2023-05-03T17:56:54.4358903Z     __import__(pkg_name)
2023-05-03T17:56:54.4359334Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\testbench\__init__.py", line 15, in <module>
2023-05-03T17:56:54.4360008Z     from . import (
2023-05-03T17:56:54.4360550Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\testbench\common.py", line 31, in <module>
2023-05-03T17:56:54.4361020Z     from requests_toolbelt import MultipartDecoder
2023-05-03T17:56:54.4361701Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\__init__.py", line 12, in <module>
2023-05-03T17:56:54.4362222Z     from .adapters import SSLAdapter, SourceAddressAdapter
2023-05-03T17:56:54.4362746Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\adapters\__init__.py", line 12, in <module>
2023-05-03T17:56:54.4363185Z     from .ssl import SSLAdapter
2023-05-03T17:56:54.4363646Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\adapters\ssl.py", line 16, in <module>
2023-05-03T17:56:54.4364105Z     from .._compat import poolmanager
2023-05-03T17:56:54.4364568Z   File "C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\requests_toolbelt\_compat.py", line 50, in <module>
2023-05-03T17:56:54.4365046Z     from urllib3.contrib import appengine as gaecontrib
2023-05-03T17:56:54.4365610Z ImportError: cannot import name 'appengine' from 'urllib3.contrib' (C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\urllib3\contrib\__init__.py)

Component(s)
Continuous Integration

Ah, storage-testbench already upgraded requests-toolbelt (https://github.com/googleapis/storage-testbench/pull/492) so we just need a new release of storage-testbench.

I've added a PR that pin urllib3<2.  However, once gcs-testbench releases a new version we can remove this pinning.  CC @coryan

@coryan thanks for the quick response.  The new version appears to be working fine.


Picker.Item unable to select on whitespace

Basically there is a wide Picker and each of the item can be clickable only directly on the item itself, means that if we are clicking on the label, it can be selected but if we click on the whitespace besides the label, it wont be selected.
I've tested the same app in most of the devices but apparently this issues only happened on huawei MHA-L29.

In that case, can you try with React Native Picker on same device? Also share screen

@isaaclem Did you try?

I have the same issue


fix several bugs in array type handling in dotnet module

Several bugs were present in the parsing and generation of a string to represent an array type, notably when the "lo_bound" value is set.

The "read_blob_signed" was buggy for values outside the [-2**6, 2**6-1], the sign edition did not use the right bitmask, and the type used was unsigned.

The display when lo_bound != 0 was buggy:

size=5, lobound=0 => should be 5, this was ok
size=5, lobound=1 => should be 1...5, this was buggy and displayed 1...6. The "range format" is inclusive.

0 should still be displayed if size is 0. Only when size is unset should it be left out. So an array declared as [5,0,3] should be displayed the same way, and not as [5,,3].

Yes, I crafted some files for testing in boreal, one of which test array sizes: types2.dll
lo bound values on arrays cannot be used in C# files afaik, but they can easily be tested with MSIL files. The aforementioned file was generated from this source code: types2.cil
This makes it easy to compare the syntax used in the MSIL file with the type strings generated in the yara module.

I fixed an unnecessary change, should be ok now


SpikeHD.Dorion version 4.0.1

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

Log:
2024-01-10 10:12:24.897 [CORE] Started applying motw using IAttachmentExecute to C:\Users\VALIDA~1\AppData\Local\Temp\WinGet\SpikeHD.Dorion.4.0.1\48d0fccc6093f916f077bae51c1e042acce0411187633c0586d87468de4858b1
2024-01-10 10:12:37.776 [CORE] Finished applying motw using IAttachmentExecute. Result: -2147467259 IAttachmentExecute::Save() result: -2147467259
2024-01-10 10:12:37.780 [FAIL] Installer failed security check. Url: https://github.com/SpikeHD/Dorion/releases/download/v4.0.1/Dorion_4.0.1_x64_en-US.msi Result: 0x80004005
2024-01-10 10:12:37.780 [CLI ] Terminating context: 0x8a15002d at D:\a\_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\DownloadFlow.cpp:1e6

I am unfamiliar with how the checks happen and how they work. Why did the security check fail?

The package didn't pass a Defender or similar security scan. This might be a false positive so we can rescan. (unfortunately I'm not a moderator so I don't know if the command will work for my part) @headquarter8302

/AzurePipelines run

yeah

The package didn't pass a Defender or similar security scan. This might be a false positive so we can rescan. (unfortunately I'm not a moderator so I don't know if the command will work for my part) @headquarter8302

I noticed that. While installing the package locally, defender blocked it from running. Do all MSIX packages need to be passed by defender?

Yes, every package receives at least one Defender scan, as well as other security scans.
https://learn.microsoft.com/en-us/windows/package-manager/package/repository#validation-process

Hey all!
I've submitted the portable version of Dorion (contains the same contents of the MSI, just all in one place) to Microsoft's Defender team. I assume that is basically the only thing one can do to get this PR any further?

Hi @SpikeHD,
False positives usually pass about a day later, so I'll scan this again tomorrow.

/AzurePipelines run


Empty cells parameter for spreadsheet read method

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
I am trying to read data from my google spreadsheet by using:
service = build('sheets', 'v4', credentials=creds)
sheet = service.spreadsheets()
result = sheet.values().get(spreadsheetId=spreadsheet_id,range='sheet', majorDimension='COLUMNS').execute()

which returns the data but ignores empty cells as written in the doc[1]. The problem is that it destroys the structure of my table because fields with the same index in the list dont belong together.
Describe the solution you'd like
It would be nice to include the empty cells as empty strings like in the plain HTTP API response.
Maybe as a parameter for the values().get method.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Thanks for reading and considering my idea!
[1] https://googleapis.github.io/google-api-python-client/docs/dyn/sheets_v4.spreadsheets.values.html#get

Hi @hahahannes,
This Python client is a wrapper around the REST API itself. https://developers.google.com/sheets/api/reference/rest/v4/spreadsheets.values/get
It sounds like this is a feature request for the API. Please file a feature request here.
Thanks!

Hi @busunkim96, thanks a lot for your fast answer! I am just a bit confused because the API itself already returns empty strings for empty cells. So I thought, they have to be removed in the wrapper but I guess, I missunderstand something there.

Ah, it looks like I was reading too quickly.
The HTTP response returns empty strings, but the library skips those cells?

Exactly, if I understood correctly.
It is also written in the client doc https://googleapis.github.io/google-api-python-client/docs/dyn/sheets_v4.spreadsheets.values.html#get that empty cells are omitted.

Hi, just wanted to quickly ask, if this is considered as a valid feature request. If so, I would be glad to help out, but couldnt find the spreadsheet section in the code so far.

I just ran into this as well - same thing seems to be happening on the row level. For example if I import a range of "A:E" and columns B and C are sometimes empty then the resulting arrays are length 3 or 4, with no way to tell which column they came from.

@hahahannes @laurikoobas   Is this issue still occurring?

@vchudnov-g I'm seeing this issue as well

I just ran into this as well - same thing seems to be happening on the row level. For example if I import a range of "A:E" and columns B and C are sometimes empty then the resulting arrays are length 3 or 4, with no way to tell which column they came from.

It still an issue with google sheet api v4


Investigate and define the work required for SPIFFE-based client identity management

Summary
This request is to establish a design and create the necessary work items (in this repo and other repos) that are needed to enhance Parsec with a SPIFFE-based identity subsystem.
Details
Investigation required, but necessary work items likely to include:

Creating a new authenticator module in the service that can verify SPIFFE IDs. The expectation is that we will use the JWT SVID in the auth header of the request, with a new integer auth type, and that verification would be performed by calling the workload API ValidateJWTSVID operation to check the JWT and return the SPIFFE identity string (which is then used as the keystore namespace in the familiar way).
Creating a branch in the client library/libraries to populate the auth field with a JWT SVID when the service requires this auth type.
Creating an appropriate integration test system.
Documentation updates.

Dependencies
At the moment, the SPIFFE spec does not allow clients to call ValidateJWTSVID without themselves being a registered SPIFFE workload. The expectation is that Parsec would not be a workload. However, the SPIFFE specification group have agreed that this restriction can be lifted. See https://github.com/spiffe/spiffe/issues/132
Once the spec is changed, SPIRE (as the reference implementation) will also need to honour that change so that Parsec can call the function on a SPIRE-based system. There isn't a GH issue for that yet.
There will be a need to call SPIFFE workload API operations from Rust. We need to investigate whether this can be done by consuming https://github.com/heavypackets/rust-spiffe and adding the necessary JWT operations (since it currently only supports X509).
Definition of Done
This issue can be considered done once we have created a credible set of well-understood issues in this repo and in the other repos for an end-to-end SPIFFE multi-tenant solution. We should by this point be in a position for any contributor(s) to start implementing those pieces without requiring further investigation.

We might need to collaborate with Sabree on this one to use his spiffe crate or to get approval to fork it and upstream.

As part of this investigation, we also need to work with the SPIFFE and SPIRE project representatives to decide on what a proof-of-concept or demo milestone should look like. When expanding this issue into separate engineering items, we should include the work needed to build a demo or showcase of some kind. One example might be to extend the command-line client so that we can demonstrate the creation of keys and show that different workloads cannot "see" each others' keys.

Work needed to complete this task entirely:

add in the rust-spiffe crate support for JWT-SVID (estimate: 2 weeks). More precisely:
a. the ability to fetch its JWT-SVID
b. the ability to validate a JWT-SVID remotely (faster, for PoC/demos)
c. the ability to validate a JWT-SVID locally (for security, will take longer)
add a new AuthType in Parsec Interface (Done): parallaxsecond/parsec-interface-rs#84
add a new authenticator in Parsec to validate a JWT-SVID (estimate: 1 week): parallaxsecond/parsec#268
add a new variant to the Rust client's AuthenticationData for JwtSvid and a constructor that uses rust-spiffe to automatically fetch the JWT-SVID it will use to authenticate (estimate: 1 week): parallaxsecond/parsec-client-rust#55
add a test to the multitenancy testing infrastructure for SPIFFE authentication on the CI (estimate: 1 week): parallaxsecond/parsec#269

In terms of doing a demo, the following could be done locally and recorded (can be done before any PR is up):

two workloads as different Unix users get registered to the SPIRE server based on their UID
on two different terminals, the two workloads create a key on the Mbed Crypto provider, selecting the JwtSvid authentication method. That assumes that 1.a, 2 and 4 are done.
Parsec validates the JwtSvid and creates the key. That assumes that 1.b and 3 are done.
the clients list their keys: they can only see the one they created
the clients try to destroy the other's client key: it does not work
the clients list their keys: same output
the clients destroy their own key
the clients list their keys: empty result


Backwards constness propagation

Since #202 we have special terms needed for calling black boxes unbox(bb(args...), type, sizes) where sizes is for example a single term describing the size of a vector.
Now in the function
julia> typecheck_hs_from_string("
       module L
       f(x) :: BlackBox() = zeros(x,x)
       function g(x::Integer)
        m = unbox(f(x), Matrix{<:Real}, (x,x))
        (xx,_)=size(m)
        xx
       end
       end")
======================== Errors =====================

======================== End Errors =====================

---------------------------------------------------------------------------
Type:
{
  -  Int[s_7 ©]
      @ ∑∅
  --------------------------
   -> Int[s_7 ©]

}
---------------------------------------------------------------------------
Constraints:
   - top:

   - others:
[]
()

we would infer that g : Int[n] -> Int[n], thus refining the input type. This is necessary because this function can only be called if the input x is const, only in this case can we know what the output of the black box is going to be.
On the other hand, we have a problem with const in ops. They had a "proper" solving order (which did not work because of something), so we relaxed the ordered solving in #108, and ?. This means that it now probably could happen that we can have the case where a constraint a + b = Int[n] is ignored by op-solving, while the RHS comes from a BB call, and requires that the LHS actually does resolve to something const.

We have changed how non-constification works (#207).

We could think about what the best approach is to forcing this to fail.


[Bug]: Unable to apply for library permissions without 2 library permissions

ODC version
odc424
OB version

What happened?

What did you expect to happen?

How can we reproduce it (as minimally and precisely as possible)?

Using a low privilege account to execute query statements
Click to apply

Anything else we need to know?
No response
Cloud
No response

pass


Cannot Set Password (the terminal does not acknowledge keyboard input) C100 (asus flip)

Please paste the output of the following command here: sudo edit-chroot -all
NA- can't run sude edit-chroot -all

#### Please describe your issue:
cannot set password (terminal refuses keyboard input for any 'password' prompts)

#### If known, describe the steps to reproduce the issue:

Couldn't set it during install (but could hit enter and leave it blank).
Gave it no response enough times for it to leave it unset
Can't set it now using passwd [user] (still refuses keyboard input- and hitting return to leave it blank returns "Authentication token manipulation error"

please close; resolved by entering the chroot as root and using passwd from there.

No problem, glad you figured it out and thanx for coming back and closing the issue.

Just to clarify and keyword this better for other users who are as new to this as I am:
My issue was that during install I did not see anything happening when I was attempting to enter a password.  I did not realize this was the default behavior of password prompts in the terminal.  I left the password blank (un-set) by repeatedly pressing enter with nothing entered into the password prompt. A message appeared reminding me that I could reset the password afterward using passwd [user], but was not able to do so.
I resolved this issue by a) understanding that the password prompt was still recording my keystrokes even though it was not showing me anything, and b) logging into the chroot as root with sudo enter-chroot -u root and then running passwd [user] from there.
Essentially, this issue duplicates issue #705


$tip stopped working out of the sudden

Did anything update on discord's end? Running $tip now always fails, code hasn't changed...

UPDATE: on mobile phone it works? pc it does not? Discord acting ODD for everyone

Describe your issue please.


BUG: Fix template finding

Figured out the problem.  It was just that setup.py wasn't copying the templates when installing.  You were probably doing python setup.py develop, which wouldn't have had this issue.
Solution as per: http://flask.pocoo.org/docs/0.10/patterns/distribute/
It doesn't need the commit you put in the Try to fix branch.

Ahh that was it, thanks for the PR!


Add info on how the bus stores & repeat the events

Waiting for some comments to be fixed. I am preparing a new release that will no longer use filesystem on both bus or subscribers, but with those PR's I will updated this docs If merged already.


Fix click issue with links within inner carousel items

When implementing jCarousel with this plugin for swipe capability, I ran into an issue where clicks were being unexpectedly disabled on inner elements.
The function dragEnd() adds the click.disable event, which I think was intended to inhibit pass-through clicks on swipe for some touch devices (iOS 8 for one).  This has the unintended side effect of inhibiting the first click of certain elements, based on device and/or browser.   I ran into the following scenarios:

Some Android and iOS 9 devices complete the swipe successfully, though if you attempt to click a link wrapping the item which initiated the touch event, the first click/touch is blocked by the handler.
Chrome 48 in desktop mode completes the swipe, though the click.disable bubbles up to the  element, and effectively blocks any further attempts to activate anchor tags on the entire document, requiring a reload or manual navigation.
Firefox 43 in desktop mode lets the swipe occur if it starts in between element.  If this occurs, no links within the activated carousel will work until reload or manual navigation.

I resolved this by forcing removal of the click.disable event through a short timer.  There is a new example "responsive-item-links" which demonstrates this.  I tested this this across several Android and iOS devices, Chrome 48, and Firefox 43.

Thanks for you help. But click.disable prevent click on desktop browsers because desktop browser fire click on dragend and it go to the link. I will fix this bug a little differently. Need just check event.target on dragStart and dragEnd, because when cursor leave slider area, event.target contains body element.

Sure, glad to help.  I want to make sure you caught my one point about click.disable, and it inhibiting a valid click.
Assume you have 4 items with 2 items shown at a time.  You swipe placing your finger on item 1 to advance the carousel forward to show slides 3 and 4.  If you navigate back to item 1 using previous/next buttons or carousel indicators, the click.disable event will still be bound and inhibit the first valid click.
Without some form of automated removal for the event, it will continue to block valid clicks.

The fact is that if the cursor on dragEnd is located beyond slider area then event.target will contain  element instead element with wich fired dragStart event. Therefore sufficient to verify event.target  on dragStart with event.target on dragEnd.


wsrun doesn't read the workspaces propery in package.json

yarn expects the list of workspaces to be under a workspaces property inside packages.json. Right now wsrun just looks at workspace or uses its own defaults. The 's' is the difference.
Other than that wsrun looks exactly the kind of light weight tool I was looking for. (--exclude-missing probably should be a default, but still give warnings.)

Oops. Fixed!

thanks for the quick fix and update up on npm.


feat(react-settings-form): update sizeinput

add inherit property for sizeinput in react-settings-form
Before submitting a pull request, please make sure the following is done...

[x] Ensure the pull request title and commit message follow the Commit Specific in English.
[x] Fork the repo and create your branch from main.
[x] If you've added code that should be tested, add tests!
[x] If you've changed APIs, update the documentation.
[x] Ensure the test suite passes (npm test).
[x] Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.

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


ttnn.signbit operation failed with low PCC [Grayskull and Wormhole]

Describe the bug
ttnn.signbit operation breaks with "low PCC value" error in some test cases.
To Reproduce
Steps to reproduce the behavior:

Checkout barsic/ttnn-param-fix-skipped branch. To be merged into main soon.
Run unit test test_signbit.py by using this command:
pytest tests/ttnn/python_api_testing/non_working_unit_tests/grayskull/test_signbit.py

Expected behavior
There is a test case presented in the unit test tests/ttnn/python_api_testing/non_working_unit_tests/grayskull/test_signbit.py and it is expected to fail with Equal check failed error.
Getting Additional info for the operation under test and its behavior
To get additional information and results for different combinations of input shapes, types, layouts and memory configs for which this operation was tested you can also run locally sweeps for ttnn.std and check the results. To do this you should:

Follow the Getting Started page to setup the repo, environment variables and python-env
Activate source build/python_env/bin/activate
Run sweeps by using python tests/tt_eager/python_api_testing/sweep_tests/run_pytorch_test.py -i tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_broken/grayskull/ttnn_eltwise_signbit_test.yaml -o ./result-sweeps
After the run is completed all test sweeps results should be available inside specified output directory (in this case ./result-sweeps). There you will find signbit_sweep.csv which holds all executed sweeps, among which you can also find the ones that failed and were recreated by the unit test, which you can get by searching unique data_seed field.

@jliangTT This is already discussed and blocked as we are not able to store the -0.0

@jliangTT This is already discussed and blocked as we are not able to store the -0.0

As mentioned above we are not able to store -0.0 so signbit is fixed for positive 0 in PR link

Please close this once the tests have been updated.

Hi @ttmtrajkovic , @tt-aho , @banekg , @rtawfik01
We have a bug issue related to signbit and we have a few questions here :

Negative Zero Issue #1939 :

We are not able to store -0.0 . So signbit was fixed for positive 0.0 in this PR. And the later we had a discussion under issue #8944.  We would like to get your inputs on how we can test for -0.0 case ( #8944-comment )

Testing Branch : virdhtachani/signbit_test (#13947)
Test file : tests/tt_eager/python_api_testing/sweep_tests/pytests/tt_dnn/test_signbit_op.py
Unit Test command : pytest tests/tt_eager/python_api_testing/sweep_tests/pytests/tt_dnn/test_signbit_op.py::TestSignbit::test_run_signbit_op - Input passed as -0.0 gets passed into kernel as 0.0 value.

Incorrect result Issue #7749 :

I ran the test file mentioned in this issue and made some modification to see what the problem here is. Here, I found that the signbit op fails for bfloat8_b data type of range (-1.0 , 0.0 ) due to precision error ,
Example, values like -0.00363 produced by torch gets into the kernel as 0.0 input value. But the signbit result for

-0.00363 is True and for
0.0 is False.

I've printed all the values causing assertion error in the below test file :

Testing Branch : virdhtachani/signbit_test (#13947)
Test file : tests/ttnn/python_api_testing/non_working_unit_tests/grayskull/test_eltwise_signbit_print_error.py

Would like your inputs on this to proceed further
Thanks

Issue Assigned to LLK Team
https://github.com/tenstorrent/tt-metal/issues/13953


New contributors

Hello, do you accept new contributors? , I see that your discord link is down.

Yup, since we are an open-source community, we are pleased to accept any help we can get from talented devs like you!
also really sorry for the inconvenience thanks to your help we found out the problem and have updated the discord link :D
https://discord.gg/9VgwJetEvG
join us and help make fernosa even better!


Yarn packager excludes non-semver imports such as github references

Describe the bug
The yarn packager assumes the format <name>@<semver> , where everything before the last @ is the name, and after is the version.
This causes a problem for other formats such as this which is not valid semver:
"dependencies": {
   "@metacask/kyc-token-client": "github:mcask/kyc-token-client#0.3.2"
}

The semver comparison here returns false and so the package is excluded.
Even if the semver check is bypassed for invalid semver, the returned name still looks like this:
@metacask/kyc-token-client@git+ssh://git.
This is because the last @ in this case is part of the github ssh URL and doesn't denote the boundary between package name / version.
@metacask/kyc-token-client<EMAIL_ADDRESS>
This means the package does not pass the depWhitelist comparison here and so is still filtered out ( it compares @metacask/kyc-token-client to @metacask/kyc-token-client@git+ssh://git)
To Reproduce
Clone the minimal repo here: https://github.com/flipscholtz/serverless-esbuild-github-deps-test

Run yarn install
Note that<EMAIL_ADDRESS>imports a metacask lib using a github reference:

 "@metacask/kyc-token-client": <EMAIL_ADDRESS>

Run yarn sls package
Unzip the function .serverless/test.zip
Note that the packages node_modules has no @metacask/kyc-token-client dependency.

Expected behavior
The github-referenced dependency should be included in the packaged sls node_modules.
Screenshots or Logs
N/A
Versions (please complete the following information):

OS: MacOS Ventura 13.0
Serverless Framework Version: 3.33.0
Plugin Version: 1.46.0

Additional context
Proposed solution:

If the package reference can't be parsed to valid semver, the packager shouldn't do the semver comparison and just include the package by default.
The package name returned by the packager should be tolerant of multiple @ signs, such as in the case of github URL's, so it still returns the base name of the package accurately.
Maybe a regex like this to get the name: ^(@[^@]+|[^@]+)

I'll make a PR for this soon once I've sufficiently tested.


TASK: Implement Connection::QueueSubscribe

Fixes: #38

Coverage decreased (-2.3%) to 78.613% when pulling faf6f2dd02c570749a356c0635e0c0ce9f276a06 on dfeyer:queuesupport into 068082e48cbae26c4a7d896693cd9fb3667188cc on repejota:develop.

Coverage decreased (-2.3%) to 78.613% when pulling afce35b45541cc08cce80c1a87fe7730978e2647 on dfeyer:queuesupport into 068082e48cbae26c4a7d896693cd9fb3667188cc on repejota:develop.

Coverage increased (+0.6%) to 81.503% when pulling e6ddcb19ba3e33f36c3432539a2e284a81b00067 on dfeyer:queuesupport into 068082e48cbae26c4a7d896693cd9fb3667188cc on repejota:develop.

Thanks!
I will release a new version soon. 👍


[BUG] v1.8.0 breaks HomeKit / Homebridge integration for possible edge cases

Describe the bug
Latest update breaks connection between HomeKit and Homebridge.
Deleting Homebridge in HomeKit and trying to add the Bridge to HomeKit leads to Error message: "accessory is out of compliance"
Deleting Dingz-plugin from HomeKit resolves the issue
To Reproduce
Steps to reproduce the behavior:
Install latest Dingz-plugin in Homebridge
Plugin environment (please complete the following information):

dingz/myStrom Device Firmware Version [1.2.7]
Homebridge Server: [Homebridge Docker]
Plugin Version [v1.8.0]
Node.js Version [v14.15.0]
Homebridge Version [v1.2.3]

        {
            "name": "dingz",
            "motionPoller": true,
            "autoDiscover": false,
            "callbackHostname": "<IP_ADDRESS>",
            "devices": [
                {
                    "type": "dingz",
                    "name": "dingz Küche",
                    "address": "<IP_ADDRESS>"
                }
            ],
            "platform": "Dingz"
        },

Additional context
Remember https://github.com/johannrichard/homebridge-dingz/issues/5 ? :D

Aw shucks. I'll have a look at it. Just to confirm:

You removed HomeBridge completely from your HomeKit and when you try to re-add the bridge, it fails?

If yes: is there a specific reason why you removed it in the first place (i.e. another error that made you remove it)?
And what iOS version did you test with?
And as a workaround: you can downgrade to v1.7.1 by installing via the terminal in HomeBridge:
npm install<EMAIL_ADDRESS>(I suspect the reachability attribute I introduce w/ v1.8.1 might trigger that error. I haven't seen that on my side yet but will do more tests)

Oh and yes, of course: #5. Have to check the code I reused when updating didn't miss that (They're still working on a fix in HomeBridge/Hap-JS. AFAIK it hasn't made it into a release yet). 🤪

I completely removed HomeBridge from HomeKit because all HB-Accessories showed up as "no response". Tried to resolve the problem this way before I tried removing the Dingz-Plugin.
iOS is 14.2, rolling back to 1.7.1 works.

    {
        "name": "dingz",
        "motionPoller": true,
        "autoDiscover": false,
        "callbackHostname": "<IP_ADDRESS>",
        "devices": [
            {
                "type": "dingz",
                "name": "dingz Küche",
                "address": "<IP_ADDRESS>"
            }
        ],
        "platform": "Dingz"
    },

May I ask you to post the output from /api/v1/device as well? As I've said elsewhere (e.g. #114 #87) , the API for v1.2.x firmware changed quite a bit and some information that was beforehand returned (but empty) might now be not returned at all for non-existing serial numbers ...

There you go:
{"246F28A65F30":{"type":"dingz","battery":false,"reachable":true,"meshroot":true,"fw_version":"1.2.7","hw_version":"1.1.2","fw_version_puck":"1.1.21","bl_version_puck":"1.0.0","hw_version_puck":"1.1.1","hw_id_puck":1,"puck_sn":"","puck_production_date":{"year":20,"month":1,"day":2},"puck_hw_model":"","front_hw_model":"dz1f-4b","front_production_date":"20/4/26","front_sn":"F20042600212","dip_config":3,"has_pir":false,"hash":"e6e52dab"}}

Updated to 1.8 and only discovered this issue afterwards.
Luckily it seems this issue doesn't happen in all circumstances, my Homekit/Homebridge connections still works.
myStrom Button Firmware Version [2.74]
myStrom PIR Firmware Version [3.8.2]
Homebridge Server: [Raspberry Pi 4]
Plugin Version [1.8.0]
Node.js Version [14.15.1]
Homebridge Version [1.1.6]
Maybe this helps.

I couldn't find any cases of empty serial numbers and the remaining info seems complete, so this is a bit weird.
In the meantime I've worked on a v2.0.0-nightly of the plug-in. If you install the nightly w/ homebridge-dingz@nightly you should be upgraded to this version.
The functionality remains largely the same but the code is less cluttered and better structured so should generally run better. There might be bugs though but you can always downgrade to v1.7.1 (although I think the newest nightlies are much more robust).
I've had it running over longer periods of time now on my production dingz. So far I could not observe any problems with its operation.
The biggest change I reverted w.r.t. v1.8.0 is the reachability. If the nightly works now, that might somehow have been the cause.
I'd be grateful if you could run it and let me know if it (still) works.

I've been testing v2.0.0-nightly since Monday an this version seems to have fixed the bug described.
I've run into other error messages in the log, but will open another bug for this.

Strangely my setup broke again. I havn't changed anything except always updating to the last version of your plugin. Not sure when and why it broke but I've rolled back version by version (deleting plugin incl. configuration, restarting HB, starting from scratch), but every version since 1.7.1 now seems to be broken with my setup. Even with your plugin uninstalled (but leaving the config in the config-file) my setup breaks.
Not sure how to give you more precise info to debug. Staying on 1.7.1 for now but willing to help debug :)

Just found out why I didn't notice that my setup breaks: When I update your plugin, everything works as long as I don't restart HB. As soon as I restart HB and the updated plugin loads it breaks. Likely since v.1.7.1

Do you have any errors in the log (early on)? I've sometimes seen cases where ports remained blocked in auto-discovery when HB was restarted, but only on my development machine and not on my "production" system (where I install the nightlies as well after first testing on my dev).

Just the already reported errors (dead, alive). Auto discovery is off

Was wondering: do you still have the mixed IPv4/IPv6 setup you had when we worked on the initial bugs? From some (other) problems I had with homebridge crashing because of network issues, I fear it might benedeiende stack related.
I made one change in the callback server, binding the plug-in to <IP_ADDRESS>, in v2.0.0. I've removed that in the latest nightly, if you want test that one, we might confirm/exclude this as a probable cause.

Yes I'm still running dualstack IPv4/v6. Will test with v6 off tomorrow.
Still breaking with latest nightly (2.0.7-nightly.3)

Yes I'm still running dualstack IPv4/v6. Will test with v6 off tomorrow.

Don't bother. If it wasn't the IPv6 stack related to the callback server then it's something else.

Just an update on my investigations: On my side, I've lately seen some weird HomeKit behaviour (endless "Updating", especially when away) which I first attributed to my Apple TV/Hub running iOS beta and/or another HomeKit device being the culprit (since rebooting either one made the issues go away).
I will do some more tests and report  back ASAP.

@simonnelli With a bit more time to reflect on your bug report and a fresh look, I have a few questions related to the breaking (sorry to ask them, but we never discussed these):

when you upgraded to v2.0.0, did you remove the accessories (dingz) from the cache before restarting HB or did you just install/uninstall the config? This is a bit tricky, upgrading/downgrading the plugin does not clear the accessories cache and this can lead to problems (The accessories cache can be found in HB Config UI X Settings. It should be sufficient to remove the dingz from the cache and then restart HB again, however, it will remove them from HomeKit.)

if you run v2.0.0 and issue the following command in Terminal.app on a Mac, do you see your HB listed?

> dns-sd -B _hap._tcp
21:16:59.341  Add        3   4 local.               _hap._tcp.           Serenity XXXX

Just tried following:
Uninstall dingz-plugin, removing configuration
clearing dingz from HB-cache
restarted HB
installed 2.0.0, configured one dingz manually, no auto-discovery
dingz is displayed in Config UI X but HB connection immediately breaks.
Here the output from dns-sd -B _hap._tcp. I assume the duplicated entries are because of IPv4/v6
9:46:30.893  Add        3   4 local.               _hap._tcp.           Philips hue - 2C8000
9:46:30.893  Add        3   8 local.               _hap._tcp.           Philips hue - 2C8000
9:46:30.893  Add        3   4 local.               _hap._tcp.           Switch 01d3f8
9:46:30.893  Add        3   8 local.               _hap._tcp.           Switch 01d3f8
9:46:30.893  Add        3   4 local.               _hap._tcp.           Smart AC Control WR1741951488
9:46:30.893  Add        3   8 local.               _hap._tcp.           Smart AC Control WR1741951488
9:46:30.893  Add        3   4 local.               _hap._tcp.           DINGZ A65F30
9:46:30.893  Add        3   8 local.               _hap._tcp.           DINGZ A65F30
9:46:30.893  Add        3   4 local.               _hap._tcp.           Homebridge AC78
9:46:30.893  Add        2   8 local.               _hap._tcp.           Homebridge AC78

This really sounds like our famous #5 again, only it's much harder to catch. The only difference in the device config I saw was the empty puck_hw_model. But the code handling this didn't change between the v1.7.1 and v2.0.0.
I'm almost tempted to propose a dingz swap: I send you my test dingz and you send me your prototype. Would make my programming harder and (hopefully) solve your problem (and if not, it would be something else ...). Let me know if this is something you'd consider.

I've gone through a bit more looking around if other plugin developers had similar issues. Although I also run my HB setup on<EMAIL_ADDRESS>like you, I saw quite some reports of people who had issues running their setup under this version, and reverted back to<EMAIL_ADDRESS>So what I suggest to further debug:

what happens if you run homebridge-dingz@latest on<EMAIL_ADDRESS>(you can downgrade the homebridge in the docker image as you would with a plugin: npm i<EMAIL_ADDRESS>and then restart homebridge (but not the docker container, obviously); if this works: fine, if not, help with the following as well
I sent you some instructions over at Twitter for full debug output you can send me by mail


volare cannot find gf180

volare ls-remote --pdk gf180mcu
gives
Pre-built gf180mcu PDK versions
and then no further output.
One guess I have is that the request to GitHub to retrieve the list only gets the first few entries?
I have installed volare 0.4.3 from pip:
Requirement already satisfied: volare in ./.local/lib/python3.10/site-packages (0.4.3)
Perhaps that version is too old? In that case, please update the pip package.

It seems the problem is only affecting the ls-remote command, I heard that the other commands can successfully download the gf180mcu PDK

Volare 0.4.3 is too old. The latest version on PIP is 0.6.2 (https://pypi.org/project/volare/) so I'm not 100% sure what you're talking about.

Ok, I upgraded to 0.6.2, but I still don't see any gf180mcu PDK versions.

probably an API pagination issue- ill take a look on Sunday

@donn Any update?

I can see the same issue. If you are using openlane a workaround is to run "PDK=gf180mcuA make pdk" in the openlane root directory, which will use volare to fetch the pre-build gf180mcu PDK required by openlane.

probably an API pagination issue- ill take a look on Sunday

@donn spot on, see https://github.com/orgs/community/discussions/21901 and https://github.com/community/community/discussions/8226
doing something like https://github.com/efabless/volare/commit/3c5077a9a8cc6b2f1d22609f5227a15ae0ba83ff to fetch more result per page can workaround the issue https://github.com/efabless/volare/commit/3c5077a9a8cc6b2f1d22609f5227a15ae0ba83ff, but a proper fix would be to find a way to sort fetch all the pages and have volare sort them.


Templated messages

It would be awesome if the slack callback supported templates for the message content like the email callback does, so users could build their own message however they want.

+1
Thanks for this amazing plug-in. Templating would indeed be awesome.

+1

👍

:+1:

+1

I'll take this.

PR out -> https://github.com/graylog-labs/graylog-plugin-slack/pull/50


The contents of the 'caption' tag are garbled In the Korean translation document

Some characters are garbled in the 'Mapper XML Files' section of Korean translation documents. This happens in the 'caption' tag under the 'table' tag. However the "sqlmap-xml.xml" documentation file does not seem to have a problem.
The url is:

http://www.mybatis.org/mybatis-3/ko/sqlmap-xml.html

Yes, we are aware. See
https://groups.google.com/d/msg/mybatis-user/q51Pz_8lOuQ/w8_9KgvjCAAJ
The Doxia issue has already been fixed.
Although maven-site-plugin has not been updated yet, we may be able to resolve the issue on our site when we release 3.5.2.

The Doxia issue has already been fixed.
Although maven-site-plugin has not been updated yet, we may be able to resolve the issue on our site when we release 3.5.2.

Thank you for your reply.
Is it better to keep this issue open until it is resolved? Or should I close?

Let's keep it open.
I'll close after publishing the 3.5.2 docs.

It should be resolved. Please let me know if there is any problem.

It should be resolved. Please let me know if there is any problem.

Thank you. it is resolved. Have a nice day. :)


Allowing regex patterns to specify flags (e.g. case insensitive, global, etc)

Summary
Using flags in string regexs would be VERY useful in situations where you'd like to reuse a community regex that's slightly tweaked. Passing a string as a regex generally means that you loose the ability to specify Javascript Regex Modfiers that allow you  to ignore case and repeat globally.  This is particularly useful bc many regexs in the wild are written with them. And bc they don't translate to a string - they cannot be supported or need to be rewritten.
I'm proposing an easy way to allow regex strings to have the flags that we get in Javascript Regex Patterns. Is there interest in this from the community or from you @epoberezkin?
Deeper Motivation / Example
I have a case where I'd like to require that the uri has the schema ("https://" in my case). To do this seems simple enough - just include the regex.  Of course the regex for uri is pretty complex. Note that it leverages the 'ignorecase' (i.e. 'i') flag - so you'd need to go through the whole regex to try and make it case sensitive. Error prone, onerous and awesome to maintain.
What I would like to do is just take the 'uri' regex that you've already written and just add the required 'https://' bit to the front of it... keeping the flags intact since I'd obviously like this pattern to be case insensitive.
I wrote a package about a year ago that deals with this problem. It's called 'string-to-regexp' and allows you to write the regex in exactly the same form (though you do need to escape '' characters).
In principal all you need to do is to replace occurances of new RegExp(str) with strToRegExp(str) -- assuming that you define strToRegExp with a require statement : var strToRegExp = require('string-to-regexp');
It looks to me like we'd only need to put this in 3 places to get the desired effect.
https://github.com/epoberezkin/ajv/blob/master/lib/ajv.js#L307
https://github.com/epoberezkin/ajv/blob/master/lib/compile/formats.js#L127
https://github.com/epoberezkin/ajv/blob/master/lib/compile/index.js#L200
The caveats related to the module are very reasonable. However allowing flags does extend beyond the strings that new RegExp takes - just as the Javascript regex format is slightly different - therefore there is a minute opportunity that this won't work as expected for some strings. BUT that opportunity is very small and we could solve this by allowing an option to turn it on or off in ajv.
Is there any interest in this?

I think the better approach than modifying the behaviour of the standard keyword pattern is to define the custom keyword, e.g. regexp, that would accept the JavaScript regular expression with flags as a string and convert it to RegExp instance:
var rx = str.match(/^\/(.*)\/([gimy]*)$/);
if (rx) var regexp = new RegExp(rx[1], rx[2]);

We also have such function in protojs library.
You may even let it accept an object { pattern: '', flags: '' } so you neither have to worry about escaping '/' characters nor about parsing the string.
I don't really like the option that would change the meaning of the standard JSON-schema keyword. I think using custom keyword is better for such situation.

Closing it, please let me know if the proposed solution works for you

Evgeny - I think your proposed solution is just fine - Thank you!

On Jan 21, 2016, at 3:37 AM, Evgeny Poberezkin<EMAIL_ADDRESS>wrote:
I think the better approach than modifying the behaviour of the standard keyword pattern is to define the custom keyword https://github.com/epoberezkin/ajv#defining-custom-keywords, e.g. regexp, that would accept the JavaScript regular expression with flags as a string and convert it to RegExp instance:
var rx = str.match(/^/(.)/([gimy])$/);
if (rx) var regexp = new RegExp(rx[1], rx[2]);
We also have such function in protojs http://milojs.github.io/proto/proto_string.js.html#toRegExp library.
You may even let it accept an object { pattern: '', flags: '' } so you neither have to worry about escaping '/' characters nor about parsing the string.
I don't really like the option that would change the meaning of the standard JSON-schema keyword. I think using custom keyword is better for such situation.
—
Reply to this email directly or view it on GitHub https://github.com/epoberezkin/ajv/issues/101#issuecomment-173516325.

See https://github.com/epoberezkin/ajv-keywords#regexp

Sorry to reopen an old issue, but does this not suggest that pattern should allow for flags? https://github.com/json-schema/json-schema/issues/188

Example repo https://github.com/rofrol/ajv-regexp-errormessage-example

Example repo https://github.com/rofrol/ajv-regexp-errormessage-example

One the other hand I also observed that AJV chokes with "^{{[\u000A.]*}}$" which is the correct alternative encoding for \n.


Prisma fluent API not decrypt data

Describe the Bug
I have trouble in using prisma-field-encryption middleware when using prisma fluent API. Not decrypted data are returned when I request data through prisma fluent API. To avoid N+1 problem, I want to use fluent API which can use prisma data loader.
To Reproduce
Add prisma-field-encryption middleware. Make schema which has parent-children relation model and @encrypted field in children model. (see my code below)
Expected Behavior
I expect data which are requested through prisma fluent API to be decrypted.
Environment:
OS: ubuntu 22.04.1
Node 20.2.0
Prisma version 5.2.0
prisma-field-encryption 1.5.0
TypeScript version 5.2.2
Express 4.18.2
Additional Context
This is my github repository
Prisma schema
// schema.prisma
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = "postgresql://postgres:postgres@db:5432/adgame?schema=public"
}

model User {
  id    Int     @id @default(autoincrement())
  email String
  name  String? /// @encrypted
  posts Post[]
}

model Post {
  id        Int     @id @default(autoincrement())
  title     String
  content   String? /// @encrypted
  published Boolean @default(false)
  author    User    @relation(fields: [authorId], references: [id])
  authorId  Int
}

Express Server
// server.ts

import express from "express";
import { PrismaClient } from "@prisma/client";
import { fieldEncryptionExtension } from "prisma-field-encryption";

const globalClient = new PrismaClient();

const client = globalClient.$extends(
  fieldEncryptionExtension({
    encryptionKey: "k1.aesgcm256.DbQoar8ZLuUsOHZNyrnjlskInHDYlzF3q6y1KGM7DUM=",
  })
);

const app = express();

const server = app.listen(3000, function () {
  console.log("start server");
});

// data are decrypted when using normal query
app.get("/userposts1", async (req, res, next) => {
  const user = await client.user.findFirst();
  const authorId = user?.id || 1;
  const posts = await client.post.findMany({
    where: {
      authorId: authorId,
    },
  });
  console.log(posts);
  res.send(posts);
});

// data are not decrypted when using fluent API
app.get("/userposts2", async (req, res, next) => {
  const posts = await client.user.findFirst().posts();
  console.log(posts);
  res.send(posts);
});

Thanks for the reproduction repo, I'll have a look.
In the mean time, what do the debug logs say when you hit the fluent endpoint?
DEBUG="prisma-field-encryption:*" node your-server.js

Thank you for your reply.
This is my debug logs when I hit fluent endpoint.
// debug logs prisma-field-encryption-error-sample-server-1  | 2023-08-30T17:24:19.777Z prisma-field-encryption:encryption Clear-text input: { prisma-field-encryption-error-sample-server-1  |   args: { select: { posts: true } }, prisma-field-encryption-error-sample-server-1  |   model: 'User', prisma-field-encryption-error-sample-server-1  |   action: 'findFirst', prisma-field-encryption-error-sample-server-1  |   dataPath: [], prisma-field-encryption-error-sample-server-1  |   runInTransaction: false prisma-field-encryption-error-sample-server-1  | } prisma-field-encryption-error-sample-server-1  | 2023-08-30T17:24:19.779Z prisma-field-encryption:encryption Encrypted input: { prisma-field-encryption-error-sample-server-1  |   args: { select: { posts: true } }, prisma-field-encryption-error-sample-server-1  |   model: 'User', prisma-field-encryption-error-sample-server-1  |   action: 'findFirst', prisma-field-encryption-error-sample-server-1  |   dataPath: [], prisma-field-encryption-error-sample-server-1  |   runInTransaction: false prisma-field-encryption-error-sample-server-1  | } prisma-field-encryption-error-sample-server-1  | 2023-08-30T17:24:19.785Z prisma-field-encryption:decryption Raw result from database: [ prisma-field-encryption-error-sample-server-1  |   { prisma-field-encryption-error-sample-server-1  |     id: 5, prisma-field-encryption-error-sample-server-1  |     title: 'Post1', prisma-field-encryption-error-sample-server-1  |     content: 'v1.aesgcm256.2fc1baee.BYsfYrU7k6ppBv0t.n_MIe9lb-jpIveEs3jfRVH2LJGxU4pvvvqECrFg=', prisma-field-encryption-error-sample-server-1  |     published: false, prisma-field-encryption-error-sample-server-1  |     authorId: 5 prisma-field-encryption-error-sample-server-1  |   }, prisma-field-encryption-error-sample-server-1  |   { prisma-field-encryption-error-sample-server-1  |     id: 6, prisma-field-encryption-error-sample-server-1  |     title: 'Post2', prisma-field-encryption-error-sample-server-1  |     content: 'v1.aesgcm256.2fc1baee.srH0TPxsXRm2DDz2.2U9FRykgqty9jiIlGQTLFlnA_EWRysmhUW41oSs=', prisma-field-encryption-error-sample-server-1  |     published: false, prisma-field-encryption-error-sample-server-1  |     authorId: 5 prisma-field-encryption-error-sample-server-1  |   } prisma-field-encryption-error-sample-server-1  | ] prisma-field-encryption-error-sample-server-1  | 2023-08-30T17:24:19.787Z prisma-field-encryption:decryption Decrypted result: [ prisma-field-encryption-error-sample-server-1  |   { prisma-field-encryption-error-sample-server-1  |     id: 5, prisma-field-encryption-error-sample-server-1  |     title: 'Post1', prisma-field-encryption-error-sample-server-1  |     content: 'v1.aesgcm256.2fc1baee.BYsfYrU7k6ppBv0t.n_MIe9lb-jpIveEs3jfRVH2LJGxU4pvvvqECrFg=', prisma-field-encryption-error-sample-server-1  |     published: false, prisma-field-encryption-error-sample-server-1  |     authorId: 5 prisma-field-encryption-error-sample-server-1  |   }, prisma-field-encryption-error-sample-server-1  |   { prisma-field-encryption-error-sample-server-1  |     id: 6, prisma-field-encryption-error-sample-server-1  |     title: 'Post2', prisma-field-encryption-error-sample-server-1  |     content: 'v1.aesgcm256.2fc1baee.srH0TPxsXRm2DDz2.2U9FRykgqty9jiIlGQTLFlnA_EWRysmhUW41oSs=', prisma-field-encryption-error-sample-server-1  |     published: false, prisma-field-encryption-error-sample-server-1  |     authorId: 5 prisma-field-encryption-error-sample-server-1  |   } prisma-field-encryption-error-sample-server-1  | ]

Thank you for your reply.
This is my debug logs when I hit fluent endpoint.
debug logs
prisma-field-encryption-error-sample-server-1  | 2023-08-30T17:24:19.777Z prisma-field-encryption:encryption Clear-text input: {
prisma-field-encryption-error-sample-server-1  |   args: { select: { posts: true } },
prisma-field-encryption-error-sample-server-1  |   model: 'User',
prisma-field-encryption-error-sample-server-1  |   action: 'findFirst',
prisma-field-encryption-error-sample-server-1  |   dataPath: [],
prisma-field-encryption-error-sample-server-1  |   runInTransaction: false
prisma-field-encryption-error-sample-server-1  | }
prisma-field-encryption-error-sample-server-1  | 2023-08-30T17:24:19.779Z prisma-field-encryption:encryption Encrypted input: {
prisma-field-encryption-error-sample-server-1  |   args: { select: { posts: true } },
prisma-field-encryption-error-sample-server-1  |   model: 'User',
prisma-field-encryption-error-sample-server-1  |   action: 'findFirst',
prisma-field-encryption-error-sample-server-1  |   dataPath: [],
prisma-field-encryption-error-sample-server-1  |   runInTransaction: false
prisma-field-encryption-error-sample-server-1  | }
prisma-field-encryption-error-sample-server-1  | 2023-08-30T17:24:19.785Z prisma-field-encryption:decryption Raw result from database: [
prisma-field-encryption-error-sample-server-1  |   {
prisma-field-encryption-error-sample-server-1  |     id: 5,
prisma-field-encryption-error-sample-server-1  |     title: 'Post1',
prisma-field-encryption-error-sample-server-1  |     content: 'v1.aesgcm256.2fc1baee.BYsfYrU7k6ppBv0t.n_MIe9lb-jpIveEs3jfRVH2LJGxU4pvvvqECrFg=',
prisma-field-encryption-error-sample-server-1  |     published: false,
prisma-field-encryption-error-sample-server-1  |     authorId: 5
prisma-field-encryption-error-sample-server-1  |   },
prisma-field-encryption-error-sample-server-1  |   {
prisma-field-encryption-error-sample-server-1  |     id: 6,
prisma-field-encryption-error-sample-server-1  |     title: 'Post2',
prisma-field-encryption-error-sample-server-1  |     content: 'v1.aesgcm256.2fc1baee.srH0TPxsXRm2DDz2.2U9FRykgqty9jiIlGQTLFlnA_EWRysmhUW41oSs=',
prisma-field-encryption-error-sample-server-1  |     published: false,
prisma-field-encryption-error-sample-server-1  |     authorId: 5
prisma-field-encryption-error-sample-server-1  |   }
prisma-field-encryption-error-sample-server-1  | ]
prisma-field-encryption-error-sample-server-1  | 2023-08-30T17:24:19.787Z prisma-field-encryption:decryption Decrypted result: [
prisma-field-encryption-error-sample-server-1  |   {
prisma-field-encryption-error-sample-server-1  |     id: 5,
prisma-field-encryption-error-sample-server-1  |     title: 'Post1',
prisma-field-encryption-error-sample-server-1  |     content: 'v1.aesgcm256.2fc1baee.BYsfYrU7k6ppBv0t.n_MIe9lb-jpIveEs3jfRVH2LJGxU4pvvvqECrFg=',
prisma-field-encryption-error-sample-server-1  |     published: false,
prisma-field-encryption-error-sample-server-1  |     authorId: 5
prisma-field-encryption-error-sample-server-1  |   },
prisma-field-encryption-error-sample-server-1  |   {
prisma-field-encryption-error-sample-server-1  |     id: 6,
prisma-field-encryption-error-sample-server-1  |     title: 'Post2',
prisma-field-encryption-error-sample-server-1  |     content: 'v1.aesgcm256.2fc1baee.srH0TPxsXRm2DDz2.2U9FRykgqty9jiIlGQTLFlnA_EWRysmhUW41oSs=',
prisma-field-encryption-error-sample-server-1  |     published: false,
prisma-field-encryption-error-sample-server-1  |     authorId: 5
prisma-field-encryption-error-sample-server-1  |   }
prisma-field-encryption-error-sample-server-1  | ]

Thanks, I think I have an idea of what is going on.
The query coming into the extension asks for users, with included posts:
{
  args: { select: { posts: true } },
  model: 'User',
  action: 'findFirst',
  dataPath: [],
  runInTransaction: false
}

However, the data coming back from the database (or rather from the client engine doing its thing) is a list of Posts:
[
  {
    id: 5,
    title: 'Post1',
    content: 'v1.aesgcm256.2fc1baee.BYsfYrU7k6ppBv0t.n_MIe9lb-jpIveEs3jfRVH2LJGxU4pvvvqECrFg=',
    published: false,
    authorId: 5
  },
  {
    id: 6,
    title: 'Post2',
    content: 'v1.aesgcm256.2fc1baee.srH0TPxsXRm2DDz2.2U9FRykgqty9jiIlGQTLFlnA_EWRysmhUW41oSs=',
    published: false,
    authorId: 5
  }
]

This throws the decryption engine off which was expecting a User model, with some connections to a list of Posts, not the posts themselves.
Since Prisma does this downstream and doesn't give us any info of this change (neither from the input arguments nor from the returned data), I don't see how we can handle this and differenciate it from a regular (non-Fluent) call.

FYI, I have opened a discussion about this behaviour on the Prisma repo: https://github.com/prisma/prisma/discussions/20901

Thank you very much. I don't have any idea about solving this problem because there is no information on the Internet.
OK. I 'll follow the discussion.


auro-input: documentation is incorrect for "required" attribute error messages

General Support Request
The docs at https://auro.alaskaair.com/components/auro/input#required are incorrect when describing how to add a custom error string on a required field.
What the docs say: "The error message for the valueMissing validityState can be changed to a custom string using the customValidityValueMissing."
However, customValidityValueMissing is incorrect. The actual attribute to use in code is setCustomValidityValueMissing. Seen here in the source code: https://github.com/AlaskaAirlines/auro-input/blob/3e30aa9e302bca440910b6fe9c7d326821b419e5/src/base-input.js#L31C38-L31C38
Possible Solution
Change customValidityValueMissing to setCustomValidityValueMissing in the documentation and include a code example of this being used.
Additional context
No response
Exit criteria
Documentation is corrected.

@Patrick-Daly-AA  I have verified and validated this issue!


Change player likes function name as per Tylergaw's suggestion

Good idea Tyler. Function changed everything should be good to go now.

Hi!
First of all, great plugin!
I´d like to know if there is some way to have for a shots list for a player the shots size bigger. Something like when you display only a shot using the id. There are parameters or how I should modify this?
I like the plugin because you don´t need to use PHP and all the problems this have with server directives, fopen, cURL...
Great work! ;)


[Feature request] drag & drop reordering of rows

Hi,
I see drag reordering of BackGrid columns has been implemented.  We need to be able to drag-reorder rows up & down. Is that in the cards?

Hi is this feature supported  in backgrid?

:+1: I'd like to see this too.


Add ddt as a setup.py optional dependency

Summary
As a side effect of #2563, currently the qiskit.test module fails to import if ddt is not installed. This PR adds ddt as an optional dependency to setup.py in a similar spirit to other optional dependencies (visualization, full-featured-simulators), aiming for the minimal-effort approach for reintroducing the ability of installing "everything terra needs in a single pip instruction".
Details and comments

Alternative option, PR #2897

I'm fine either way - mostly aiming to have all dependencies readily installable :+1:

Closed in favor of https://github.com/Qiskit/qiskit-terra/pull/2895


nexus: Fix BRAM mapping.

@gatecat I think this should fix #3416 with just techmap. Could you test and review it?


Error when using @vitejs/plugin-react-swc

I get the following error when attempting to start up the editor:

My vite.config:
import { defineConfig } from "vite";
import react from "@vitejs/plugin-react-swc";
import { r3f } from "@react-three/editor/vite";

// https://vitejs.dev/config/
export default defineConfig((env) => ({
  plugins: [env.command === "build" ? react() : r3f()],
}));

I am on Windows.
I am using Vite v4.0.0.

I confirmed that vite v4 does work. The problem is using @vitejs/plugin-react-swc insead of @vitejs/plugin-react.

So the earlier error was vite 4 + swc and works with vite 4 + babel.. did u try with vite 3 as well?

I did not, I can try this configuration later.

https://github.com/vitejs/vite/issues/9986 could be related to this

resolve: {
   preserveSymlinks: true,
},

work for me

Open Command Palette: Command + Shift + P.
Search TypeScript: Restart TS server.
Press Enter.

I confirmed that vite v4 does work. The problem is using @vitejs/plugin-react-swc insead of @vitejs/plugin-react.

Thanks!! I had the following error "[vite] Internal server error: Bindings not found." Changing @vitejs/plugin-react-swc to @vitejs/plugin-react solved it.


feat(project): auto-generate project short code on creation (DSP-1614)

resolves DSP-1614

I've tried it out and all works fine, but see my comments below.
While creating new project this is what I've got:
{
    "id": "1fd1cd4c-ea1b-4d2d-9837-62b519e47545",
    "shortCode": "55ca",
    "shortName": "my proj",
    "longName": "my projects name",
    "description": "description of my project",
    "createdAt": "2021-05-27 16:06:40 +0200 CEST",
    "createdBy": "00000000-0000-0000-0000-000000000000",
    "changedAt": "0001-01-01 00:00:00 +0000 UTC",
    "changedBy": "00000000-0000-0000-0000-000000000000",
    "deletedAt": "0001-01-01 00:00:00 +0000 UTC",
    "deletedBy": "00000000-0000-0000-0000-000000000000"
}

I'm not sure of the best practices in Go, but looking at empty/0 values, should these be initialised like that instead of null equivalent?

In Go, variables default to their null value depending on their type. I don't think it's best practice to set them to nil. What I could do is have a different struct in the presenter for when a project is created but you will still get these "empty" fields when you get the project.

I've tried it out and all works fine, but see my comments below.
While creating new project this is what I've got:
{
    "id": "1fd1cd4c-ea1b-4d2d-9837-62b519e47545",
    "shortCode": "55ca",
    "shortName": "my proj",
    "longName": "my projects name",
    "description": "description of my project",
    "createdAt": "2021-05-27 16:06:40 +0200 CEST",
    "createdBy": "00000000-0000-0000-0000-000000000000",
    "changedAt": "0001-01-01 00:00:00 +0000 UTC",
    "changedBy": "00000000-0000-0000-0000-000000000000",
    "deletedAt": "0001-01-01 00:00:00 +0000 UTC",
    "deletedBy": "00000000-0000-0000-0000-000000000000"
}

I'm not sure of the best practices in Go, but looking at empty/0 values, should these be initialised like that instead of null equivalent?

In Go, variables default to their null value depending on their type. I don't think it's best practice to set them to nil. What I could do is have a different struct in the presenter for when a project is created but you will still get these "empty" fields when you get the project.

I don'r mind to see this, but from the FE point of view would be easier to have something null/undefined, otherwise you need to add another condition to check.

I don'r mind to see this, but from the FE point of view would be easier to have something null/undefined, otherwise you need to add another condition to check.

I know what you mean. I think we'll just have to try it out and see what needs to be changed. At least for timestamps, you can check if it's zero which basically means null.

I don'r mind to see this, but from the FE point of view would be easier to have something null/undefined, otherwise you need to add another condition to check.

I know what you mean. I think we'll just have to try it out and see what needs to be changed. At least for timestamps, you can check if it's zero which basically means null.

Are these props required? Do we need to have them required?

I don'r mind to see this, but from the FE point of view would be easier to have something null/undefined, otherwise you need to add another condition to check.

I know what you mean. I think we'll just have to try it out and see what needs to be changed. At least for timestamps, you can check if it's zero which basically means null.

Are these props required? Do we need to have them required?

What do you mean by required? The UUID, short code, timestamps and the props that hold the user UUIDS are all autogenerated. The rest are required in the JSON request body.

I don'r mind to see this, but from the FE point of view would be easier to have something null/undefined, otherwise you need to add another condition to check.

I know what you mean. I think we'll just have to try it out and see what needs to be changed. At least for timestamps, you can check if it's zero which basically means null.

Are these props required? Do we need to have them required?

What do you mean by required? The UUID, short code, timestamps and the props that hold the user UUIDS are all autogenerated. The rest are required in the JSON request body.

Ok, so there is no way to generate these only with non-zero values? Which means, during creation of project only createdAt and createdBy would be generated. Because no property in JSON means no value in db, it's optional.

I don'r mind to see this, but from the FE point of view would be easier to have something null/undefined, otherwise you need to add another condition to check.

I know what you mean. I think we'll just have to try it out and see what needs to be changed. At least for timestamps, you can check if it's zero which basically means null.

Are these props required? Do we need to have them required?

What do you mean by required? The UUID, short code, timestamps and the props that hold the user UUIDS are all autogenerated. The rest are required in the JSON request body.

Ok, so is there no way to generate these only with non-zero values? Which means, during creation of the project only createdAt and createdBy would be generated. Because no property in JSON means no value in db, if it's optional.

Correct. However, the createdBy property shouldn't actually be a zero-value but we don't have the permissions set up yet. Once they are, the UUID of the user performing the operation will be there. Same for updatedBy and deletedBy.

I don'r mind to see this, but from the FE point of view would be easier to have something null/undefined, otherwise you need to add another condition to check.

I know what you mean. I think we'll just have to try it out and see what needs to be changed. At least for timestamps, you can check if it's zero which basically means null.

Are these props required? Do we need to have them required?

What do you mean by required? The UUID, short code, timestamps and the props that hold the user UUIDS are all autogenerated. The rest are required in the JSON request body.

Ok, so is there no way to generate these only with non-zero values? Which means, during creation of the project only createdAt and createdBy would be generated. Because no property in JSON means no value in db, if it's optional.

Correct. However, the createdBy property shouldn't actually be a zero-value but we don't have the permissions set up yet. Once they are, the UUID of the user performing the operation will be there. Same for updatedBy and deletedBy.

Correct, I'm aware of this. But I'm talking about something different.
I'm asking if it's possible to auto-generate properties ONLY during corresponding events. So, createdAt and createdBy only at creation, and no more. updatedBy and updatedAt only at update event and same goes for deletion. So after creation of the project only two autogenerated properties exist: createdAt and createdBy and others are added later if the events will occur.

Ok, so is there no way to generate these only with non-zero values? Which means, during creation of the project only createdAt and createdBy would be generated. Because no property in JSON means no value in db, if it's optional.

Correct. However, the createdBy property shouldn't actually be a zero-value but we don't have the permissions set up yet. Once they are, the UUID of the user performing the operation will be there. Same for updatedBy and deletedBy.

Correct, I'm aware of this. But I'm talking about something different.
I'm asking if it's possible to auto-generate properties ONLY during corresponding events. So, createdAt and createdBy only at creation, and no more. updatedBy and updatedAt only at update event and same goes for deletion. So after creation of the project only two autogenerated properties exist: createdAt and createdBy and others are added later if the events will occur.

The API can return whatever we like. Here the choice was made to return the complete struct of the project. Maybe the API could filter out the "null" values and only return those properties containing something meaningful?

Ok, so is there no way to generate these only with non-zero values? Which means, during creation of the project only createdAt and createdBy would be generated. Because no property in JSON means no value in db, if it's optional.

Correct. However, the createdBy property shouldn't actually be a zero-value but we don't have the permissions set up yet. Once they are, the UUID of the user performing the operation will be there. Same for updatedBy and deletedBy.

Correct, I'm aware of this. But I'm talking about something different.
I'm asking if it's possible to auto-generate properties ONLY during corresponding events. So, createdAt and createdBy only at creation, and no more. updatedBy and updatedAt only at update event and same goes for deletion. So after creation of the project only two autogenerated properties exist: createdAt and createdBy and others are added later if the events will occur.

The API can return whatever we like. Here the choice was made to return the complete struct of the project. Maybe the API could filter out the "null" values and only return those properties containing something meaningful?

Either this or what I said, I'm just not sure wha's best practice here and there is many examples why this might be not. For me it's fine to keep null properties in the response, but this must be just null, which doesn't require any special conditions to check.

Ok, so is there no way to generate these only with non-zero values? Which means, during creation of the project only createdAt and createdBy would be generated. Because no property in JSON means no value in db, if it's optional.

Correct. However, the createdBy property shouldn't actually be a zero-value but we don't have the permissions set up yet. Once they are, the UUID of the user performing the operation will be there. Same for updatedBy and deletedBy.

Correct, I'm aware of this. But I'm talking about something different.
I'm asking if it's possible to auto-generate properties ONLY during corresponding events. So, createdAt and createdBy only at creation, and no more. updatedBy and updatedAt only at update event and same goes for deletion. So after creation of the project only two autogenerated properties exist: createdAt and createdBy and others are added later if the events will occur.

The API can return whatever we like. Here the choice was made to return the complete struct of the project. Maybe the API could filter out the "null" values and only return those properties containing something meaningful?

Either this or what I said, I'm just not sure wha's best practice here and there is many examples why this might be not. For me it's fine to keep null properties in the response, but this must be just null, which doesn't require any special conditions to check on the FE.

Yes, I see what you mean: https://stackoverflow.com/questions/15686995/should-null-values-be-included-in-json-responses-from-a-rest-api
There was a discussion about this recently on API-Craft. The general consensus was there is potentially a semantic difference between the omission of a value, versus an inclusion of a null value.

If there is no semantic value to be gained for your specific use case, then I would say look at your target consumers of the API, and think about whether omitting the value will cause them problems.

Ok, so is there no way to generate these only with non-zero values? Which means, during creation of the project only createdAt and createdBy would be generated. Because no property in JSON means no value in db, if it's optional.

Correct. However, the createdBy property shouldn't actually be a zero-value but we don't have the permissions set up yet. Once they are, the UUID of the user performing the operation will be there. Same for updatedBy and deletedBy.

Correct, I'm aware of this. But I'm talking about something different.
I'm asking if it's possible to auto-generate properties ONLY during corresponding events. So, createdAt and createdBy only at creation, and no more. updatedBy and updatedAt only at update event and same goes for deletion. So after creation of the project only two autogenerated properties exist: createdAt and createdBy and others are added later if the events will occur.

The API can return whatever we like. Here the choice was made to return the complete struct of the project. Maybe the API could filter out the "null" values and only return those properties containing something meaningful?

Either this or what I said, I'm just not sure wha's best practice here and there is many examples why this might be not. For me it's fine to keep null properties in the response, but this must be just null, which doesn't require any special conditions to check on the FE.

Yes, I see what you mean: https://stackoverflow.com/questions/15686995/should-null-values-be-included-in-json-responses-from-a-rest-api
There was a discussion about this recently on API-Craft. The general consensus was there is potentially a semantic difference between the omission of a value, versus an inclusion of a null value.

If there is no semantic value to be gained for your specific use case, then I would say look at your target consumers of the API, and think about whether omitting the value will cause them problems.

Currently, the admin API does not return optional properties as null values. Also, I don't think that omitting properties with null values will hurt the frontend at the moment. What I don't know, if this will maybe be a problem when we need to edit stuff. In the case of the system properties this doesn't matter, but what if for example the description property was optional? If it is omitted, will it be a problem for the FE to know that it should be there when a project would be edited?

Ok, so is there no way to generate these only with non-zero values? Which means, during creation of the project only createdAt and createdBy would be generated. Because no property in JSON means no value in db, if it's optional.

Correct. However, the createdBy property shouldn't actually be a zero-value but we don't have the permissions set up yet. Once they are, the UUID of the user performing the operation will be there. Same for updatedBy and deletedBy.

Correct, I'm aware of this. But I'm talking about something different.
I'm asking if it's possible to auto-generate properties ONLY during corresponding events. So, createdAt and createdBy only at creation, and no more. updatedBy and updatedAt only at update event and same goes for deletion. So after creation of the project only two autogenerated properties exist: createdAt and createdBy and others are added later if the events will occur.

The API can return whatever we like. Here the choice was made to return the complete struct of the project. Maybe the API could filter out the "null" values and only return those properties containing something meaningful?

Either this or what I said, I'm just not sure wha's best practice here and there is many examples why this might be not. For me it's fine to keep null properties in the response, but this must be just null, which doesn't require any special conditions to check on the FE.

Yes, I see what you mean: https://stackoverflow.com/questions/15686995/should-null-values-be-included-in-json-responses-from-a-rest-api
There was a discussion about this recently on API-Craft. The general consensus was there is potentially a semantic difference between the omission of a value, versus an inclusion of a null value.

If there is no semantic value to be gained for your specific use case, then I would say look at your target consumers of the API, and think about whether omitting the value will cause them problems.

Currently, the admin API does not return optional properties as null values. Also, I don't think that omitting properties with null values will hurt the frontend at the moment. What I don't know, if this will maybe be a problem when we need to edit stuff. In the case of the system properties this doesn't matter, but what if for example the description property was optional? If it is omitted, will it be a problem for the FE to know that it should be there when a project would be edited?

I think omitting properties with null values will lead to lots of confusion down the line. Just because the value is null doesn't mean it's not there. As a developer, I'd prefer being able to see all the properties available for me to use, regardless of the value it may hold.

I'm not for omitting anything, null properties are fine, but this must be null not 00000000-0000-0000-0000-000000000000 and other things which need to be interpreted on the FE. But if it isn't possible I suggested autogenerating properties only on corresponding events = no null properties.

@mpro7 @subotic Alright so, I tried out the pointer technique as mentioned here https://stackoverflow.com/a/31048860
Now the JSON response bodies look like this:
Project A created:

Project A deleted without ever being modified:

Project B previously created and just modified (idk why this timestamp is much more precise than the others):

@mdelez this seems for me more reasonable. I don't know all the possible use cases, but having this will be very easy FE to check if project exists, was modified or just created.

Cool 😄 now the question is: should this be added in this PR or a separate one?

@mdelez IMO this one is good. It's about auto-generation too ;)

@mpro7 @subotic you can check out the changes in e07759b

@mdelez Please, everything in this PR. Sorry to be so picky.  These are some fundamental design decisions that need to be taken now. Subsequent PRs will be then simpler to implement.

@mdelez Please, everything in this PR. Sorry to be so picky.  These are some fundamental design decisions that need to be taken now. Subsequent PRs will be then simpler to implement.

No worries :) This is also my first time implementing an API so I would prefer you guys to be picky so that I don't have to go back and redo everything.

closing without merging as this PR has gotten quite convoluted and would be better if broken into separate tasks


destroy session when sign out button is clicked

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

approved


fix-sandbox-value-type

The datatype for this seems to be integer type. I tested with bool and it cost me 1 API document credit

@karlloic is this MR really solving issue for you?
I checked Python SDK code and seems like both Integer and Boolean types are supported.
For example if you try to create common document (create_document.py) with document.sandbox = 1 or document.sandbox.True both are working nice.
On the other side, when I tried to create Template Document as Sandbox, neither = 1 or = True helped.
I am thinking this might be problem with Eversign API, not with the SDK.
What are your thoughts on this?
Thanks,
Milan

Hi Milan,
Yes I agree. This makes sense. Over the weekend I noticed the same thing. It is currently NOT possible to create a document from template as Sandbox. At first I thought it was a bool/int issue just because my account dashboard didn't get updated right away but I can now confirm that neither 1 nor True work. The SDK seems fine but the API might not be capturing that value.
Thanks,
Karl

Hi @karlloic,
Yes, that makes sense, thanks for quick feedback.
I will close this MR because SDK works properly, and I will open ticket for Eversign API so that someone look into this issue.
If this is causing you issues in testing you can contact our support at Eversign with account details.
Kind regards,
Milan

Hi @karlloic,
After revisiting this issue once more, it was Python SDK issue.
Client was not supporting sandbox parameter at all.
This is fixed now, and new release is created here
https://github.com/eversign/eversign-python-sdk/releases/tag/1.2.1
Please, use new release and you will not have problems any more :)
Cheers, and thanks for reporting this in the first place!

@milanlatinovic Great! Thanks for the fix. When will this release be published to pypi?

@karlloic sorry for a delay, I lost this thread out of my sight since it was closed. :)
I made a new release today https://pypi.org/project/eversign/1.2.2/
If any other issues, please reopen the ticket so it will be more visible.
You can also followup on twitter, #eversign tag as well for news about new releases and features.
Happy holidays and stay safe.

Thank you @milanlatinovic
Happy Holidays!


New Fable website!

For now, you can see the result at: http://tpetricek.github.io/Fable.
All documentation related stuff is in the docs folder. There is:

docs.fsx together with liquid.fs and helpers.fs generates the documentation
templates contains DotLiquid templates for the page look
source is the source for the documentation. This can contain static files (just copied to the output directory), Markdown files (formatted and passed to the content.html template) and HTML files (that can specify formatting using DotLiquid header - see index.html for example).
source/content contains some JS for tooltips and CSS styles
source/docs contains the original Fable docs (Markdown) with some tweaks

In paket.dependencies, I added a separate group for the docs, because this might need different version of FSharp.Compiler.Service.dll than the one Fable compiler needs. For this reason, docs.fsx is a separate build script. It is invoked from main build.fsx by spawning a new copy of FAKE. There are two targets:

PublishDocs processes all documentation and pushes it to gh-pages
GenerateDocs processes all documentation but does not push it
BrowseDocs starts a server on localhost and opens the docs. It supports neat live reloading :). This does not recompile all samples, because that can take quite long.

They are stand-alone, but I suppose you can add "PublishDocs" ==> "Publish" to release docs on every release!
In the samples and in the documentation, the file always starts with a Markdown list that specifies some meta data about the item. For samples, this is CSS for the embedded JS app, title & tagline for the page (passed to DotLiquid via "model" object) etc. For documentation, this is again the title & tagline that appear in the purple box.
I only did this for a couple of the samples (Mario, Hokusai, Ozmo, Pacman for the browser and Express and Server from the nodejs samples), but it would be really nice to add more "ordinary" things like the TodoMvc or event the Electron demo. But I guess others can contribute now too :-)

Oh, also, the URL for the video needs to change once Mark uploads the video to FSharp.TV Vimeo or Youtube.

As @ReedCopsey pointed out we say people need F# 4.4 :) that's a tough requirement. I suppose Fable requires just F# 4.0?

 Will change that.

This is wonderful Tomas, thanks a lot! It looks really, really, really nice. I couldn't have come to something even close to this. I just merged your PR (btw, you have also rights if you need to push directly) and I'll go deeper through your recommendations later. You're right about F# 4.4. That was mainly for development as one of the first contributors had problems if FSharp.Core 4.4 wasn't installed. But I guess for users it should be enough with F# 4.0 :+1:

Xoxo. Just wonderful!

Could you add a link to the website in the description at the top of http://github.com/fsprojects/Fable please?

done


tests depend on certain terminals

On a new machine (ubuntu 14.04) tests fail when running rspec due to missing terminals. I installed gnuplot from source, and ran rspec https://gist.github.com/mess110/8921a931342a25999f78
On Travis, we are not getting the same behavior. Maybe because we are installing gnuplot from http://cz.archive.ubuntu.com/ubuntu vivid main universe
The tests should pass. Any ideas?

I think tests are failed because absence of qt terminal. There was the same issue when I tried to run tests on Mac OS. It may be solved by building Gnuplot with --with-qt option.
I will remove requirement for this terminal from tests. This terminal isn't actually used in tests and now (when examples mostly are in notebooks) there is no need in it.
Thank you, it really should be fixed.


Implement ACIR generation from SSA

Problem
This pass will generate the acir ir from the SSA IR, once all optimizations have been completed.
Similar to Monomorphized AST to SSA IR, this should be broken down into granular tasks.
Proposed solution
Implement this as a new module in the ssa_refactor folder
Alternatives considered
No response
Additional context
No response
Submission Checklist

[X] Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.

This has been split into several different issues


Bump version to 1.0.0

Signed-off-by: Victor Vieux<EMAIL_ADDRESS>

ping @docker/swarm-maintainers

LGTM :tada: :balloon:

sweet

LGTM :cool:

Super !!!!!

:birthday:

Awesome! :tada: :tanabata_tree:

LGTM

Awesome!
Thanks,
Dong

On Oct 13, 2015, at 6:14 PM, Andrea Luzzardi<EMAIL_ADDRESS>wrote:
Merged #1292 https://github.com/docker/swarm/pull/1292.
—
Reply to this email directly or view it on GitHub https://github.com/docker/swarm/pull/1292#event-434705144.

Wait — where is the party?

On Oct 13, 2015, at 6:24 PM, Dongluo Chen<EMAIL_ADDRESS>wrote:
Awesome!
Thanks,
Dong

On Oct 13, 2015, at 6:14 PM, Andrea Luzzardi<EMAIL_ADDRESS>wrote:
Merged #1292 https://github.com/docker/swarm/pull/1292.
—
Reply to this email directly or view it on GitHub https://github.com/docker/swarm/pull/1292#event-434705144.

—
Reply to this email directly or view it on GitHub https://github.com/docker/swarm/pull/1292#issuecomment-147898856.

Realized to late that I forgot to LGTM on this. Poor me.

Thanks


Pass a multiprocessing.Pool object to forward modeling functions

The new version of fatiando.gravmag.tesseroid (#175) uses the multiprocessing.Pool to execute the forward modeling in parallel. However, each call to the forward modeling functions creates a new Pool. This can cause significant overhead when functions are called many times.
An option would be pass in a Pool object created before so that it can be reused. Currently, the functions take a njobs argument that, if > 1, tells how many processes to include in the Pool. This argument could optionally receive an open Pool object to use.

Can't pass the pool as njobs because then there is no way of knowing how many processes are in the pool. I need this number to split the computation point arrays between processes.


Still having issues

Okay, so, it still doesn't work. BetterDiscord has always been broken for me (even bandaged). To get it working I had archive and run it through WinRAR, so it could be my computer.
Here's what I've done.
1.) Uninstalled it through control panel.
2.) Deleted everything in "AppData/local/SquirrelTemp/discord-3.0.1-full.NUPKG"
3.) Deleted it in "AppData/roaming/discord."
4.) Deleted this all in my Recycle Bin. Although, would it still infect it? Should I use a software like SpyBot
5.) After reinstalling, I selected "SquirrelTemp" in "AppData/local" because I couldn't select the .NUPKG file itself.
Should I try and export the .NUPKG file to a folder?
PS. My other thread was closed, sorry if I'm making too many. I've spent hours trying to fix this stuff, and I don't know what to do.

Try these steps:

Fully close Discord.
Delete this directory %appdata%\discord\0.0.301
Delete this directory %localappdata%\Discord\app-0.0.301\resources\app
Open Discord
Redownload and run the latest BBD installer

Okay, one last thing that might affect it, whenever I reinstall I get the error "Can't extract Installer" and have to run it through the .NUPKG file. I don't know if that does anything, but maybe.

Can you send me a screenshot of that error? That doesn't sound like an error of the BBD installer. If you are having issues with Discord installation I recommend you go to them and not us.

No no, it's not you, I'm saying it might have an effect on it because instead of a normal download I use the exe in /lib/net45. When using the downloader it says "Not found!" What I'm asking is should I install it to one of the files in /lib/net45 or any other of the files in the NUPKG? As well as that, since there's the option to, what file should I pick to install BBD to?

BBD should automatically detect the correct folder. If it doesn't go to the support servers for direct support.

Could you give me an invite to the server? Or tell me where I could find it?
But out of curiosity and wanting to try it, would you happen to know what the correct folder would be?
Thank you for the help.
Many thanks,
Bailey

Invite on BetterDiscord.net
Folder should be %localappdata%\Discord\app-0.0.301

Oh, the file isn't even there.

I selected that file, but the "install" button is grey'd out. I don't get why it won't work.

Then you need to find your Discord installation. Check where your shortcut points to

C:\Users\levib\Desktop\Discorf\lib\net45\Discord.exe
Points to here.

Screenshot the contents of the net45 folder

There's a few, but alright.
Page 1:

Page 2:

Page 3:

Ah okay I see the issue. There's no version folder like 0.0.301 or app-0.0.301 and the installer looks for that

You can try renaming the net45 folder to that and then updating your shortcuts to install. But I'm not home and can't change the installer for a couple days

Can I have a screenshot of what, "%localappdata%\Discord\app-0.0.301," and, "%localappdata%\Discord," would look like? I want to see if I can replicate the folder. And when you say updating it, you don't mean uninstall and reinstall? Because if I do that it will just reset everything back to normal.

I'm on mobile so no I can't provide that. But by updating the shortcut I mean just updating where it points.

Ah okay. If this doesn't work, I'm also contacting discord support to help me with the installation. And to add on to the other reply, I don't mind waiting if I have to, man. I appreciate any and all effort, because I'm sure its not something I can rush.
Any ways, thank you for your help again, enjoy your stay away from home.
Many thanks,
Bailey

It worked! Thank you for all the help man!

You may want to consider reinstalling Discord. Your installation is very irregular

Glad it worked, but hopefully you won't have the same issue with future updates

No reinstalling it doesn't help at all haha. It has this problem no matter what, I think it might just be my PC.

Will do, thanks <3


Is there a bounty page where we can request features with our wallets?

I'd love a Giphy plugin for Trumbowyg and I'd be happy to throw some $$ at someone to put it together for me.
Is there a bounty page you're using to that I can go create a request on?

I will have some time soon, so email me and make me a donation :)
https://alex-d.github.io/Trumbowyg/#donate

@Alex-D Name your price for the giphy.

Hard to say without specs: what did you expect about a Giphy plugin ?

Hum, I think 200$ is fair since there is some layout to do and Ajax API call.

You got it!

Thank you! I will work on it next week :)

Great can't wait!
When you search, will the list of optional GIFs scroll? I'm happy with a fixed list of the top 10.
Also, if you can choose in the configuration the rating of the set, that'd be great. Giphy can be NSFW so they added a rating options - https://developers.giphy.com/docs/api/endpoint#search

Hey, I've finished the plugin itself, I just need to create the icon, then I will merge it :)
Documentation & demo are also ready \o/
Stay tuned!

Yep:
https://github.com/Alex-D/Trumbowyg/blob/4b7a8964f760278a4d95b9e199389a59ccf8c5c8/plugins/giphy/trumbowyg.giphy.js#L74-77
Depends on IE versions and issues :/

Ie11.
Focus css removal
Pressing enter doesn't line break
On Tue, Aug 27, 2019, 10:44 AM Alexandre Demode<EMAIL_ADDRESS>wrote:

Yep:
https://github.com/Alex-D/Trumbowyg/blob/4b7a8964f760278a4d95b9e199389a59ccf8c5c8/plugins/giphy/trumbowyg.giphy.js#L74-77
Depends on IE versions and issues :/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Alex-D/Trumbowyg/issues/836?email_source=notifications&email_token=AAAXKVZNZXCD4ZNRSCMVULDQGVRYPA5CNFSM4FR62WJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5IRXVY#issuecomment-525409239,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAXKVYAM77VQZ2WNWO3MRDQGVRYPANCNFSM4FR62WJA
.

Giphy plugin available in 2.19.0
Give it a try: https://alex-d.github.io/Trumbowyg/demos/#plugins-giphy
For IE11 issues, I need more details. I've email you, but maybe you prefer continue here. It's just that IE11 are not related to Giphy so that's out of scope for this issue. Maybe you can open a GitHub issue for each bug you want I fix :)

@thatleeguy you're welcome ;)