SECURITY.py file is not opening

[ WARN:0] global C:\Users\runneradmin\AppData\Local\Temp\pip-req-build-_xlv4eex\opencv\modules\videoio\src\cap_msmf.cpp (1022) CvCapture_MSMF::grabFrame videoio(MSMF): can't grab frame. Error: -2147483638
OpenCV(4.5.3) C:\Users\runneradmin\AppData\Local\Temp\pip-req-build-_xlv4eex\opencv\modules\imgproc\src\color.cpp:182: error: (-215:Assertion failed) !_src.empty() in function 'cv::cvtColor'
[ WARN:1] global C:\Users\runneradmin\AppData\Local\Temp\pip-req-build-_xlv4eex\opencv\modules\videoio\src\cap_msmf.cpp (376) anonymous-namespace'::SourceReaderCB::OnReadSample videoio(MSMF): OnReadSample() is called with error status: -2147023170 [ WARN:1] global C:\Users\runneradmin\AppData\Local\Temp\pip-req-build-_xlv4eex\opencv\modules\videoio\src\cap_msmf.cpp (388) anonymous-namespace'::SourceReaderCB::OnReadSample videoio(MSMF): async ReadSample() call is failed with error status: -1072873851
[ WARN:1] global C:\Users\runneradmin\AppData\Local\Temp\pip-req-build-_xlv4eex\opencv\modules\videoio\src\cap_msmf.cpp (438) `anonymous-namespace'::SourceReaderCB::~SourceReaderCB terminating async callback
Please help to solve the problem.

Looks like it is just a warning. Does the file is not even opening, or is getting failed at some step?
Could you please tell me what python version you're using and have you installed these libraries?
pip install opencv-contrib-python
pip install opencv

When i install and setup in October 2021 its properly working capture face do all task perfectly but when i open security.py on march 2022 it is not opening face cam not opening its show some error in opencv.

You'll see a userData folder created when you had registered, please try to delete this folder and try again, because it contains facial data and other settings.

after deleting user data file i still got error
[ WARN:0] global C:\Users\runneradmin\AppData\Local\Temp\pip-req-build-_xlv4eex\opencv\modules\videoio\src\cap_msmf.cpp (1022) CvCapture_MSMF::grabFrame videoio(MSMF): can't grab frame. Error: -2147483638 Exception in Tkinter callback Traceback (most recent call last):   File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\tkinter\__init__.py", line 1705, in __call__     return self.func(*args)   File "C:\Users\ibran raeen\Desktop\PersonalAssistantChatbot-main\SECURITY.py", line 134, in Add_Face     startCapturing()   File "C:\Users\ibran raeen\Desktop\PersonalAssistantChatbot-main\SECURITY.py", line 93, in startCapturing     if face_extractor(frame) is not None:   File "C:\Users\ibran raeen\Desktop\PersonalAssistantChatbot-main\SECURITY.py", line 77, in face_extractor     gray = cv2.cvtColor(img, cv2.COLOR_BGR2GRAY)
cv2.error: OpenCV(4.5.3) C:\Users\runneradmin\AppData\Local\Temp\pip-req-build-_xlv4eex\opencv\modules\imgproc\src\color.cpp:182: error: (-215:Assertion failed) !_src.empty() in function 'cv::cvtColor'
my Python version is 3.7.8
windows 11

According to this, you're getting errors while adding your face, right?
Is something wrong with the camera or some settings which are blocking CV2 to capture the frame. The frame value which is passed in the face_extractor(frame) function is None, which is causing the error.

So what is the solution?

ibran can we talk a little i have wrote u mail and send u request on insta too.....


Use '/' in sw-precache's stripPrefix

R: @addyosmani @gauntface
Closes #835

:+1:

Closed via https://github.com/google/web-starter-kit/commit/768be943cf420cb2b050fd31e66f2f708d443519


Update AngularJS code section setting cookie

Fixes #9509
Change the documentation to make it more clear that a cookie must be set server side to take advantage of the AngularJS convention to address CSRF. This change adds code showing how to set the cookie via IAntiforgery.

@ahsteele Thank you for the PR! Are you interested in updating this section of the doc to Angular (v2+)? We're slowly updating AngularJS (v1) samples as we find time. Unfortunately, other priorities have trumped that work.
/cc: @Rick-Anderson

I will take a look at what’s in the document and see about getting it updated. No promises things are pretty crazy here too. :)
Happy I was able to help here!


Inline BuildStrategy CRDs with ClusterBuildStrategy

Related to #228
The namespaced BuildStrategy was defining a VERSION column
that the ClusterBuildStrategy didn´t have. Also, this VERSION
column didn´t display anything.
This commit removes the kubebuilder annotation from the
buildstrategy_types.go and regenerate the proper CRD for this resource.
This is how the strategies CRDs looked before:
$ k -n test-build get bs
NAME            VERSION
buildpacks-v3
$ k -n test-build get cbs
NAME                     AGE
buildah                  6m11s
buildpacks-v3            6m24s
buildpacks-v3-heroku     6m26s
kaniko                   6m8s
source-to-image          6m6s
source-to-image-redhat   6m3s

this is how they look with this PR:
$ k -n test-build get bs
NAME            AGE
buildpacks-v3   2m9s
$ k -n test-build get cbs
NAME                     AGE
buildah                  2m14s
buildpacks-v3            2m19s
buildpacks-v3-heroku     2m22s
kaniko                   2m11s
source-to-image          2m9s
source-to-image-redhat   2m6s

@zhangtbj in #228 you mentioned about having both version and age. I´m not sure why we would need version at this point in time. My rational is that this resources are most of the time only applied once, therefore a version becomes not that relevant. I would like first to inline both strategy CRDs with the same columns.

/ok-to-test

New travis will fail because the ruby buildpacks test fail.
We cannot confirm if community support it very well, let us remove it first:
https://github.com/redhat-developer/build/issues/256

Rerun the test and travis passed. Age is fine for us now.
/lgtm

/approve

The version is the Generation of the build strategy, so that we can know what is version we are using, or tell end user maybe different builder version uses different version(Generation) of the build strategy.
I think it is fine in this PR to just use age.
In future, we can think about what we can add in the kubectl get of build strategy.


Workspace - From category GL code page, tapping back button directs to Hhm not here page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.33-1
Reproducible in staging?: Y
Reproducible in production?: N
Issue reported by: Applause Internal Team
Action Performed:

Go to https://staging.new.expensify.com/home
Tap fab -- new workspace
Tap categories
Tap on a category
Tap GL code
Tap app back button

Expected Result:
From GL code page, tapping back button must not direct to hhm not here page.
Actual Result:
From category GL code page, tapping back button directs to hhm not here page.
Workaround:
Unknown
Platforms:

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/74987dc5-3886-410c-9daf-34f700d3500c

View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
From category GL code page, tapping back button directs to hhm not here page.
What is the root cause of that problem?
We have backTo = WORKSPACE_CATEGORY_GL_CODE and will navigate when handle press button back here and we will navigate to WORKSPACE_CATEGORY_GL_CODE => page not found
https://github.com/Expensify/App/blob/57e1313096e1bbc969592bb33c55fe9b4eedf6d6/src/pages/workspace/categories/CategorySettingsPage.tsx#L61-L65
What changes do you think we should make in order to solve the problem?

Add isControlPolicy(policy) to this condition(https://github.com/Expensify/App/blob/57e1313096e1bbc969592bb33c55fe9b4eedf6d6/src/pages/workspace/categories/CategorySettingsPage.tsx#L122-L125)
        if (backTo && isControlPolicy(policy)) {
            Navigation.goBack(ROUTES.SETTINGS_CATEGORIES_ROOT.getRoute(policyID, backTo));
            return;
        }

https://github.com/Expensify/App/blob/57e1313096e1bbc969592bb33c55fe9b4eedf6d6/src/pages/workspace/categories/CategorySettingsPage.tsx#L61-L65
What alternative solutions did you explore? (Optional)

updated proposal

Proposal
Please re-state the problem that we are trying to solve in this issue.

From GL code page, tapping back button must not direct to hmm not here page.

What is the root cause of that problem?

When policy is not controlPolicy we  redirect app to workspaceUpgrade page
https://github.com/Expensify/App/blob/57e1313096e1bbc969592bb33c55fe9b4eedf6d6/src/pages/workspace/categories/CategorySettingsPage.tsx#L195-L201
here we are passing wrong fallback route
https://github.com/Expensify/App/blob/57e1313096e1bbc969592bb33c55fe9b4eedf6d6/src/pages/workspace/categories/CategorySettingsPage.tsx#L200

What changes do you think we should make in order to solve the problem?

change fallback route

ROUTES.WORKSPACE_CATEGORY_SETTINGS.getRoute(policyID, policyCategory.name),

https://github.com/Expensify/App/blob/57e1313096e1bbc969592bb33c55fe9b4eedf6d6/src/pages/workspace/categories/CategorySettingsPage.tsx#L200

so app will navigate to category page when clicking back button from upgrade page.

What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
<!---
ATTN: Contributor+

You are the first line of defense in making sure every proposal has a clear and easily understood problem with a "root cause". Do not approve any proposals that lack a satisfying explanation to the first two prompts. It is CRITICALLY important that we understand the root cause at a minimum even if the solution doesn't directly address it. When we avoid this step, we can end up solving the wrong problems entirely or just writing hacks and workarounds.

Instructions for how to review a proposal:

I think this will be fixed in this PR: https://github.com/Expensify/App/pull/49076

Nice, thanks for confirming, @rayane-djouah!
(I was just about to ask in the Slack thread but you were faster! 🚀 )

This is fixed on staging

No payments due since this was a regression. Closing.


improvement(ram): improve ram size

STR:

so when we do cargo run --release, it takes around 1.24gb in ram

we should improve that
telegram desktop takes up around 200mb, and discord around 150mb

Keep in mind it varies on many conditions (as well as platforms it is running on), as Ive seen telegram get as high as 2GB and discord as high as 1GB, all of which may vary on what is being cached/stored in memory, connections, how many chats are loaded, etc).
However the ram usage (on warp side at least) is mostly a number of connections being opened (see https://github.com/Satellite-im/Warp/issues/67, and https://github.com/Satellite-im/Warp/issues/68 on a small solution) and usually the usage stops over time but the memory remains allocated to reuse for other connections as well as memory for spawned task. Avg memory usage I see when using the command line over 24hrs is around 500mb while bootstrapping the public network with the lowest being about 130mb and highest being about 4gb (could get higher but unlikely in most cases since this case was due to some stuff i was testing out). Without bootstrapping or disabling discovery and connecting directly, its usually a lot less (usually about 30MB) but bound to increase as connections increase, though I do have solutions to handle this more effectively (though i might make pr in uplink in the near future to enable a separate flag to disable some of the discovery options done in exchange for direct connections as an experiment although this is more suited for mobile environments but may also be helpful for those with network restrictions with PCs too).
For uplink, some key points to pay attention to might be (will be updated over time):

Checking how memory usage is impacted while loading/unloading extensions (since this is calling native libraries, loading/unloading without a proper cleanup might cause memory leaks)
How the state (within uplink) handles or retains data
Determine if memory within dioxus remains allocated on heap after the data is removed/dropped
Memory when switching between different parts of the app

I would not rely on a mock environment completely for uplink to determine memory usage checks but could still help detects if there is any slight increase overtime without any decrease.

closing to be improved in the future


aries_cloudagent.revocation.error.RevocationError: tails_server_base_url not configured

Using ACA-Py 0.7.4 version for creating Revocation Registry, Failed
While Creating Credential Definition, set "support_revocation": true, and received the following error:
aries_cloudagent.revocation.error.RevocationError: tails_server_base_url not configured Traceback (most recent call last):   File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 164, in ready_middleware     return await handler(request)   File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 201, in debug_middleware     return await handler(request)   File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp_apispec/middlewares.py", line 45, in validation_middleware     return await handler(request)   File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 362, in setup_context     return await task   File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/messaging/credential_definitions/routes.py", line 167, in credential_definitions_send_credential_definition     raise web.HTTPBadRequest(reason="tails_server_base_url not configured") aiohttp.web_exceptions.HTTPBadRequest: tails_server_base_url not configured
Using indy-tails-server: Indy Tail Server
Credentials Issued were "abandoned" in 0.7.4 by the holder. I fail to understand that despite the above mentioned error, the Cred_Def  was published on the ledger (Indy), but Credentials aren't issuing.
Provided these params for agents as well --tails_server_base_url & --auto-create-revocation-transactions

From the error, it looks like the --tails_server_base_url was not configured -- or at least not properly.  You should take a look at what it was set to.
The creation of the CredDef takes places before the revocation registry -- it is not a single transaction, hence why the CredDef was created, even though the setup of the RevReg failed.

From the error, it looks like the --tails_server_base_url was not configured -- or at least not properly. You should take a look at what it was set to.
The creation of the CredDef takes places before the revocation registry -- it is not a single transaction, hence why the CredDef was created, even though the setup of the RevReg failed.

Provided --tails_server_base_url http://<public-ip>:6543
Tried with ngrok server url as well, and still got same error.
Does "support_revocation": true param automates the process of Revocation Registry creation or do we need to manually create the Revocation Registry using POST /revocation/create-registry API ?

The revocation registry is created automatically when support_revocation is true.
Not the command line parameter is --tails-server-base-url with dashes, not underscores.

The revocation registry is created automatically when support_revocation is true.
Note the command line parameter is --tails-server-base-url with dashes, not underscores.

Yes, I tried with hyphens, but got the same exception. Did anyone try revocation with the latest aca-py version, i.e 0.7.4?
For running the Tail server, I've followed the guide:  https://github.com/bcgov/indy-tails-server
Using ./manage start for running Tail sever containers, running on ngrok and local host.

Revocation Registry was created and committed to the ledger as well. However, after revoking the credential, credential State in Issuer Wallet is credential_revoked, but in Holder's Wallet for same Cred is credential_acked.
used following JSON body for POST /revocation/revoke API
{
  "comment": "string",
  "connection_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "cred_ex_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "notify": true,
  "notify_version": "v1_0",
  "publish": true,
  "thread_id": "string"
}

I think it should change for the Holder as well, kindly suggest if I am missing something here ?


Inconsistence in node-red's new flow admin API

What are the steps to reproduce?
When one has a flow and uses the UI to export and import the flow, the system automagically parses the ids and changes them so they don't duplicate.
The same behavior should occur to the admin API.
What happens?
If we try to get the flow by id and try to import it again the node-red complains that children node ids already exists.
What do you expect to happen?
The expected behavior is that the API does the same as the UI because this is very useful for flow automation and it should be compatible with user interface.
Please tell us about your environment:

[x] Node-RED version: all
[x] Node.js version: all
[x] npm version: all
[x] Platform/OS: all
[x] Browser: all

At least if you consider that this may break someone that already made use of this bug, expose another API or an optional parameter for us to have this behavior the same as the editor's UI.

When one has a flow and uses the UI to export and import the flow, the system automagically parses the ids and changes them so they don't duplicate.
The same behavior should occur to the admin API.
However, if we try to get the flow by id and try to import it again the node-red complains that children node ids already exists.
The expected behavior is that the API does the same as the UI because this is very useful for flow automation and it should be compatible with user interface.
At least if you consider that this may break someone that already made use of this bug, expose another API or an optional parameter for us to have this behavior the same as the editor's UI.
Node-RED Version: all
Node.js version: all
npm version: all
Platform/OS: all
Browser: all

In 1.2, the import behaviour has been changed in the editor to not change the IDs by default. So intact, they are now more consistent then they were.
If you import a flow a second time, it now asks you if you want to import a copy or, in the case of config nodes and subflows, whether you want to replace the existing instance.
The /flow API is entirely separate.
I agree it needs an overhaul to be more useful in some scenarios. We have a item on the backlog to improve the overall /flow API design.
But that is a feature request and not a bug.


Django-river don't display field "parents"

I'm Adding Proceeding Meta，don't display field "parents"
How to do?

I am sorry. I just read the update
https://github.com/javrasya/django-river#082


Config changes to reflect the default branch from master to main. Please merge to complete the default branch renaming job.

Auto branch renaming content.

Docs Build status updates of commit 843e84a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

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


Code cleanup

Major changes

Made decoders public
Added stream decoders for Beatmap and Storyboard classes to normalize use of streams

May want to make this an asynchronous function in the future?

Added extra functions to HitObject class
Minor cleanup and extra line removals

Still incomplete and want some opinions on the current changes

I think a removal of both the OsuParsers.Parser class would remove unnecessary code since the decoders will be exposed now.

Feel free to remove OsuParsers.Parser class. But make sure to add Decode(string filePath) method for each decoder.

Actually, I don't think we need to do anything with this variable at all. I'll push some changes, see if you agree with them.

Going to merge this PR in its current state. If you have something else to add create another pr/issue. Thanks!


On readme.md #Goals: 1: Assess is misspelled

It appears that on Goals; Goal 1, assess is misspelled.

thank you. We have updated this.


Add support for multiple emulators when deep linking

Closes #46

📦 Published PR as canary version: 2.0.3-canary.60.667.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>

:rocket: PR was released in v2.1.0 :rocket:


Revert "Revert "Add GCP support""

Reverts openshift/certman-operator#99
This will undo the revert, and get the GCP changes merged again. There was a problem with OLM on hive-stage that might have given us a false alarm initially.

/lgtm
/approve


Make API easier to call

Currently, importing functions require multiple line of import statement at the front of the script like
from pyfixest.estimation import feols
from pyfixest.summarize import etable
from pyfixest.utils import get_data
from pyfixest.visualize import coefplot

It increases a bit the difficulties of using this package. When I need to import one more function, I need to go back to the front and modify the import statement, and then go back to my working cell.
My suggestion is that on top of current API, we can make most common used functions easier to call, with less level of chaining (Pandas style)
import pyfixest as pf

data = pf.get_data()
fit = pf.feols("Y ~ X", data)
pf.etable(fit)
pf.coefplot(fit)

We just add one more user-friendly interface, which will not affect the original way of importing functions, so existing scripts still work. If you think this is fine, I can also take on this.

I'd love that and would 100% accept such a PR! I also regularly feel like I have to type too much... 😀

I'd love that and would 100% accept such a PR! I also regularly feel like I have to type too much... 😀

Hi Alex, when I sort out the code, I feel like it is time to organize each files under sub-modules, as this project becomes more comprehensive. So as a first attempt, I made a major restructing, but which may require existing scripts to be modified a bit to accomodate the new import structure. I don't know whether it makes sense to you.
Since so many files have been changed (for each file the changes are import statement rather than functions), I think it is necessary to discuss with you before PR to see whether it is fine to change. You may refer to my forked repo. In the forked repo, I have updated all README and Jupyter Notebook accordingly. All cells have been runned.
Basically, for frequently used functions, now it can be used like the way in pandas:
import pyfixest as pf

data = pf.get_data()
fit1 = pf.feols("Y ~ X1 | f1 + f2", data=data).summary()

poisson_data = pf.get_data(model = "Fepois")
fit2 = pf.fepois("Y ~ X1 + X2 | f1 + f2", data = poisson_data).summary()

pf.etable([fit1, fit2])

For functions less used, it is now imported as
from pyfixest.report import *
from pyfixest.estimation import *  # e.g., CCV, demean
from pyfixest.errors import *  # All errors/exceptions
from pyfixest.utils import *

or called as
import pyfixest as pf

pf.estimation.demean()
pf.errors.FixedEffectInteractionError

I didn't change did modules for now.
I would like to propose three possibilities:

Introduce some more codes to accomodate scripts written under old version pyfixest.
Do not restructure files into sub-modules, but just simply edit the pyfixest/__init__.py to provide API for most frequently used functions.
Ignore the compatability issues, but just prompt users to update their scripts to accomodate new APIs.

I am open to either way. See what you think : )
Best regards,
Dave

If a lot of work, we might just bite the bullet and communicate the changes very offensively, i.e. by bumping the version from 0.17 to 0.2 or even 1.0?

This looks very good and I'd be glad to accept the new file structure - it is clearly much cleaner than before! How much work would it be to achieve backwards compatibility (plus maybe a prompt for users to move to the new structure)?

The workload is manageable. I think it can be done within two hours. For example, called
from pyfixest.summarize import table

etable()

This will raise a warning
'pyfixest.summarize.etable' is deprecated and
will be removed in a future version. Please use
'pyfixest.etable' or 'pyfixest.report.etable' instead.
You refer to https://s3alfisc.github.io/pyfixest/quickstart.html
for examples.

And then after a proper transition period, we can formally remove this compatibility design.

Hi Alex,
Please see this version in my forked repo. I added backward compatibility for all functions you used in 0.16.2 documentation. So now the existing example code can run normally, with a FutureWarning.
quickstart-v0.16.2
from pyfixest.summarize import summary  # import in previous way
summary(fit)

One strange thing is that, although I didn't edit any of did module codes, currently it fails Python 3.10 test. It looks like some problem in calling rpy2's did2s.

The code can pass Python 3.9/3.11/3.12 tests. Do you have any clue about what may happen?

Hi Dave, this  looks great, thank you! Sorry for only getting to take a look at it now, I only came home a few minutes ago.
I think the github actions failure is nothing to worry about - occasionally, the workflows simply die for now good reason. I would expect your next run to not fail on 3.10 =)
Would you open a PR? Then I'd start the formal review, merge, and publish a new version at the end of the weekend.
Btw, I used the new etable args keep and exact_match for the first time at work today, and I had a great user experience 😄

Thanks Alex! I have added a PR in #332.
It's great to hear those two args help : ) I also use them frequently in my papers now.


Bug: Unable to backspace inline images on Android

Lexical version: https://playground.lexical.dev/
This seems related to https://github.com/facebook/lexical/issues/1965
Steps To Reproduce

Add an inline image to the document on Android
Press backspace
The keyboard disappears

Video
https://github.com/facebook/lexical/assets/3639540/d8ba07bd-5671-48b5-9f39-3f565b4c38d0
Other info
In my application, I cannot backspace emojis on Android after implementing them in Lexical. I decided to see if maybe it was an issue in Lexical.
https://github.com/facebook/lexical/assets/3639540/f78ca3c5-2c5d-46af-843c-5cb1d03e4a32
My code is here: https://gitlab.com/soapbox-pub/soapbox/-/blob/main/src/features/compose/editor/nodes/emoji-node.tsx

Adding user-select: none to my EmojiNode fixed it! https://github.com/facebook/lexical/pull/4040
How incredibly delicate. I still don't get why Android backspace is so problematic.
I'm convinced now this is exactly the same problem as https://github.com/facebook/lexical/issues/1965. But #4040 is a workaround rather than a fix.

I have the same experience. The keyboard closes when hitting backspace in my decorator node which uses user-select:none.
It also closes in the playground on inline images and equation nodes.
I'm using the GBoard on a Samsung Device.
Interestingly, if I switch to the stock Samsung Keyboard the nodes get deleted without closing the Keyboard.
Maybe this helps narrowing the issue.
Happy Holidays for all :-)

Has anyone fixed this issue?

Hey! I have the same problem when I try to delete an Image or an InlineImage in the playground example https://playground.lexical.dev/
I have this problem only if I use it on Android device, on iOS device it is working!

Running into the same issue with a custom DecoratorNode, also only on mobile with GBoard. The backspace event does not seem to be triggered when pressing backspace when using the GBoard keybaord on Android. On desktop, everything works as expected.
Has anyone found a workaround for this? Or knows what options should be set/overridden when implementing DecoratorNode to let it behave consistently?


Files are decrypted even if sops configuration is not provided

Describe the bug: (a clear and concise description of what the bug is)
To Reproduce
Steps to reproduce the behavior:

Install otomi from chart: helm install otomi chart/otomi -f ../values-mojtaba-02-EE-production.yaml
The otomi apply command produces the following error:

2021-08-09T14:03:50.976Z otomi:evaluateSecrets:log Info: The 'secrets.*.yaml files' are not decrypted, because /home/app/stack/env/.sops.yaml file is not present                                                                                │
│ 2021-08-09T14:03:50.977Z otomi:evaluateSecrets:warn Unable to find the '/home/app/stack/env/.secrets' file (while not in CI).                                                                                │
│ 2021-08-09T14:03:50.982Z otomi:checkKubeContext:info Discovered service account token                                                                                │
│ 2021-08-09T14:03:50.982Z otomi:decrypt:info Starting decryption                                                                                │
│ 2021-08-09T14:03:50.996Z otomi:decrypt:info Checking prerequisites for the (de,en)crypt action                                                                                │
│ 2021-08-09T14:03:50.997Z otomi:evaluateSecrets:log Info: The 'secrets.*.yaml files' are not decrypted, because /home/app/stack/env/.sops.yaml file is not present                                                                                │
│ 2021-08-09T14:03:50.997Z otomi:evaluateSecrets:warn Unable to find the '/home/app/stack/env/.secrets' file (while not in CI).                                                                                │
│     at file:///home/app/stack/dist/common/crypt.js:47:48                                                                                │
│     at ChildProcess.<anonymous> (file:///home/app/stack/node_modules/zx/index.mjs:48:22)                                                                                │
│     at ChildProcess.emit (node:events:394:28)                                                                                │
│     at maybeClose (node:internal/child_process:1067:16)                                                                                │
│     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)                                                                                │
│ 2021-08-09T14:03:51.464Z otomi:decrypt:warn Error: [helm-secrets] File is not encrypted: ./env/charts/secrets.gitea.yaml                                                                                │
│ Error: plugin "secrets" exited with error                                                                                │
│     at file:///home/app/stack/dist/common/crypt.js:47:48

Expected behavior: (a clear and concise description of what you expected to happen)
Skip decryption if .sops.yaml file is not present
Screenshots: (if applicable, add screenshots to help explain your problem)
Cluster(s):

Cloud: [e.g. aws]
Cluster: [e.g. demo]

Versions: (seen in console's /settings)

Core Version [e.g. 0.12.34]
Console Version: [e.g. aws]
API version: [e.g. 0.4.56]

Desktop: (if relevant)

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

Smartphone: (if relevant)

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context: (add any other context about the problem here)

fixed in master


Trim whitespace in channel names

…reated

Checklist

[x] I've read and followed the Contribution Guidelines
[ ] step.yml and README.md is updated with the changes (if needed)

Version

Requires a MAJOR/MINOR/PATCH version update
Context
The channel name would contain whitespaces when space is added in the input field which was then used in creating new messages
Resolves: #75
Changes
While creating the new message the white spaces in the channel if any are removed by using the strings package trimspaces method
Investigation details

Decisions

Thank you @DiptoChakrabarty for the contribution 💪 Welcome to Bitrise contributors 🚀


crossplatform pathseperator

improve crossplatform capabilities of filename handling in iozeug

We can merge this for now, but this is deprecated code anyway. There already is a new class that should be used when dealing with file names and paths (FilePath), which handles this correctly. With the upcoming refactoring of libzeug (after gloperate refactoring), this old code is going to be removed.


W1d2 course updates

change kernelspec to climate match, include slide code for all days, self referencing colab/kaggle links, update install cells.

Merging updates from Jenna W1D2 to main.


(cygwin) --no-admin option

Would it be possible to add the --no-admin switch for installing cygwin without admin privileges?

Chocolatey requires admin access in general however - it needs write access to its C:\ProgramData\Chocolatey\lib. It would require non admin install.
Also, currently every future update would revert this behavior as chocolatey ATM doesn't remember parameters.

But adding:

-B --no-admin                     Do not check for and enforce running as
                                   Administrator

is a one line of code anyway. I can do that any time but you need to have non admin chocolatey installation.

I have a non admin chocolately installation that seems to work, somehow I have write access to C:\ProgramData.

Could you test it up, I didn't push it yet.
You will have to download it from repository and cpack it then install it from the dir. I don't have admin install and wont push it without single test.

The parameters don't seem to get passed in for me. Any of them, not just the /NoAdmin one.
Is this the correct way to pass package parameters?

choco install -v -y -f Cygwin.<IP_ADDRESS>61207.nupkg --source %cd% --params='"/NoAdmin"'

I use this one:
choco install -y  cygwin --source . --params='"/NoAdmin"

You have extra "

@furlongm @majkinetor "'/NoAdmin'"

Both seem to work with my helper func:
master~>     Get-PackageParameters "/NoAdmin" ; Get-PackageParameters "'/NoAdmin'"

Name                           Value
----                           -----
NoAdmin                        True
NoAdmin                        True


[FEA] Enhance profiler tool to output metrics specific to operators that fallback to CPU

I would like a new section of the profiler tool output to include metrics related to operators that did not run on GPU.  Here is a draft of output for a new fallback_metrics output:

App ID
Stage ID
Exec Name
Stage Duration

We added this in qualification tool, closing as not a priority for profiling tool.


laravel-echo-server: command not found

Sorry guys I'm new to Node, I just installed this library, now when I try to run the "laravel-echo-server init" command it gives this error:

laravel-echo-server: command not found

And when I try node laravel-echo-server init
it says:

module.js:478
throw err;
^
Error: Cannot find module '/home/188510.cloudwaysapps.com/xhzhajzzxb/public_html/laravel-echo-server'
at Function.Module._resolveFilename (module.js:476:15)
at Function.Module._load (module.js:424:25)
at Module.runMain (module.js:611:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:160:9)
at bootstrap_node.js:507:3

got the same issue

any solution for this issue
please help me here


Thumbsup first post should also subscribe to issue

Say you really are looking forward to a certain feature and an issue has already been filed.
Now GitHub registers interest by counting thumbs-ups (sort:reactions-+1) so you go and thumb up the first comment on that issue.
Months later you realize someone posted a workaround on that thread but you were never made aware of this as you forgot to subscribe to the thread (or like me you assumed that +1 automatically subscribed oneself).
Example URL: https://github.com/isaacs/github/issues/66#issue-16434919

I think only adding a +1 to the first post of the issue should auto-sub as it is colloquially at least how interest is registered.
Note: I couldn't find a related issue in this repo, however the thread of https://github.com/isaacs/github/issues/283 shows I am not the only one that assumed "+1 of 1st comment = subscribe".
Thanks for your life saving work.

(or like me you assumed that +1 automatically subscribed oneself).

That's the wrong assumption, none of the social networks I know work that way.
It kinda makes sense (+1 shows interest) but also I don't want to know every single update to the issue until years later it's solved.
The Subscribe button is right there; If you want updates, it should be explicit.

Maybe don't fully subscribe, but be notified only whenever issue is thereafter closed?

I think it's still unwanted/unexpected behavior. #3005 would be useful to make on-closed subscription faster.


[main] Update actions

This is a manual copy of the update-actions changes from PR #93 which was stuck/blocked due to Github Actions build problems.  Those problems were fixed in PR #100 but don't seem to updated when re-running PR #93.

Cron -knative-prow-robot
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced by: knative-sandbox/knobots/actions/update-actions

/lgtm
Looks identical to #93


XCM: add a dispatchable call to transfer to relaychain

This is not needed as it's achievable in front end easily with orml-xtokens dispatchable calls.


GET Groups : list response does not include users [userInfo]

Hello,
When I run the following code I get the DocuSign groups as expected. However I don't get the users in the group. In the API reference there is users [userInfo] part of the group object. Can I get the list of groups including the list of users or is this a limitation of the PowerShell implementation? I could use GroupUsers:list as well but then I would have to iterate for each group id from Groups:list which is not ideal.
$response = $(Invoke-RestMethod
-Uri "${apiUri}/v2.1/accounts/${accountId}/groups/"     -Method 'GET'
-Headers @{
'Authorization' = "Bearer $accessToken";
'Content-Type'  = "application/json";
} ).groups
Thank you.

Hello @georgi-butev , Thank you for reporting this issue. I did a few test with the API and I have the same behavior you described. I'm not sure if this is a problem with the documentation or if it is a problem with the API response. We have created bug number EC-3947 so the engineering team can take a look at this.
I recommend you contact your account team so they can add your account to the bug. They should also be able to update you on the status of this bug

Thank you @EdwinMoralesDS
I think if we can get the API updated with the following similar to signing_groups that would be useful:
`

include_users
string
When set to true, the response includes the signing group members.

`

The product team building the API for this endpoint is not willing to commit to make this update at this time. Closing, as it's not related directly to the code examples in here.


OptimizeJSPlugin, Uglify tests, issues 356 (devServer & output), 425 (root path)

⚡ added optimize-js-plugin

🔬 convert uglifyjsplugintest to use fuse-box-test-runner still needs converting from createEnv https://github.com/fuse-box/fuse-box/issues/391

https://github.com/fuse-box/fuse-box/issues/356

🤾 devServer outputting consistent sticky progress wheel
🔗 make the devServer output a clickable link
🌀 create spinner to be used by devserver (based on cli-spinner)

https://github.com/fuse-box/fuse-box/issues/425

👣 fix root path being settable by client, updated for babel plugin and style plugin and fusebox
🗼 allow babel plugin to take in a flat babel config if other options are not set and handle requiring from correct root path

👕⚒ linting autofixes for eof, trailing semi, empty spaces

I will merge it later, once you fix everything.


python3Packages.cherrypy: fix tests after upgrade to pytest5

Motivation for this change
Fix cherrypy python3 build after pytest5 upgrade broke the tests: b3ddab852a5229331553e07be6055fb015966b42
See https://github.com/cherrypy/cherrypy/pull/1791 for reference.
@GrahamcOfBorg build python3Packages.cherrypy
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @FRidh

@GrahamcOfBorg build python3Packages.cherrypy

Looks good!


Fixes #109 and add iterator to VersionInfo

This PR is based on #109 by Karol Werner and contains:

Add Karl to the CONTRIBUTORS file and added him as primary author.
Use version fixture in test function test_version_info_should_be_iterable.
I've deviated from Karl's test function a bit and avoided the "private" _astuple() function and created the tuple manually.
This PR does not contains a conflict. :wink:

I think, Karol's idea is useful as it allows to create a list with just tuple(version) or list(version) without using the (kind of) "private" member function _astuple().
If the maintainers of this project find it useful, I suggest to close #109 as well (as it is related and contains a conflict).

Thanks @tomschr and @ppkt for this work

Wow, that was quick! :laughing: Thanks! :+1:


Conditional Logic on configuration fields?

Description
Working in the modeler, is there fields that Kogito process will support for expression based configuration?
Such as a Task Name being generated at runtime, priority values, actors, groups, subjects, etc.  Are there fields that support expressions such as ${...} #{...} etc?
If no, what is the pattern for handling runtime based configurations?  Gateway logic uses embedded/copied java values coded into the codeGen.  would this type of functionality planned for other fields?
Some common examples:

You have  process for handling Complaints.  based on the type of complaint, you may change the Task title to add contextual info
Priority of a task may be different based on business logic
timer may be different based on business logic
Default Actor assignment may be different
Actor available may be different based on business logic
Groups for a UT may be different based on business logic.

Implementation ideas
No response

short answer no. @elguardian what do you think, sohuld we add expression support for these fields?

Expressions have their own set of issues.  it is very interesting to have the codegen abilities where you are injecting the java code.  It would be EXTRA interesting if down the line you could add Groovy or kotlin support so the scripts could be more concise.  It sort of feels like fields need a marker to say "use these java code snippet" to calculate the value

will look into it.


Missing "parse_dates" parameter in .read_sql

Not much needs to be explained here, seems as though the DbApi hook's get_pandas_df is dropping the ability to pass a list of columns (or date parser functions) to the ever useful Pandas'  read_sql.
https://github.com/airbnb/airflow/blob/60e22ed50d485eb0bcc556b7826299c6b813efc3/airflow/hooks/dbapi_hook.py#L52
Seems like the workaround would be to introduce an additional, Pandas-specific "params" argument to this method.

@timseries I think that would be a good enhancement. Would you like to make a PR for it? Adding a pandas_params dict should do the trick.

No problem!

@timseries any update?


Improve build cache strategy

Ripped off from Quarkus
Here's how it will work:

We create a cache entry on push only. Pull requests only restore it.
We create a new cache entry every day, prefixed with something like
2024-10-25.
When restoring the cache, we try the entry for the day first
(2024-10-25) and default to the one for the month (2024-10-*).
Critically, this means we will build each day's cache based on the
previous day's cache.
Atlas infra uses its own, separate cache entries.

Opening as draft, because this is based on #9163, which must be merged first.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

Merging so we can see the effects in practice -- let's revert if someone disagrees.

@marko-bekhta This might make sense on Search/Reactive too? Up to you, but I see that:

Search almost uses up its cache limit, probably because using the POM hash in the cache key is very, very strict (add a space somewhere and you'll store another 1GB)
Search doesn't cache the Maven install downloaded by Maven wrapper
Reactive makes no use of the GitHub Actions cache at all.

If you apply something like what we have here, make sure that you apply #9166 too.

Also cc @gsmet -- thanks for the example!


Add kernel_params as K8s annotation in addition to hypervisor, kernel, and image.

At https://github.com/kata-containers/runtime/blob/master/virtcontainers/pkg/annotations/annotations.go there is no annotation to customize the kernel boot parameters.  For an Intel(r) QuickAssist card there are multiple versions out there each with their own kernel modules. It would be convenient to build one kata rootfs with all the QAT modules but use a kubernetes yaml file to specify which kernel modules to load on boot that is dependent on which QAT card is used. This could be done with a kermel_params value where the modules to load are specified.

@eadamsintel thanks for reporting this. I noticed this gap too but did not yet check what it needs to have implemented (I was thinking I could help getting this done)

Thanks! That sounds like an offer @mythi! Feel free to assign the issue to yourself :smile:
The place to start looking at this is HypervisorConfig.assetPath(). However, I think this could be slightly more involved than the other assets. The reason being we need to decide how to handle user-specific kernel params set in the config file with kernel_params= when a KernelParams annotation is found.
If you look, there are unit tests to ensure the correct behaviour for kernel_params= currently (user params always take priority (get appended to the kernel cli) over any params the runtime currently specifies. That is the least surprising approach for users so we should continue with that if at all possible. Whatever is decided though, we will need:

new unit tests for the new KernelParams annotation
These will need to explicitly test kernel_params= behaviour too.

documentation explaining the priority ordering of kernel params.

Feel free to assign the issue to yourself

Looks like I cannot do this myself. Anyway, I started working on this.

user params always take priority (get appended to the kernel cli)

I think this how parameters from the annotation should be handled too. Just append them to what is already configured.
My biggest open right now is Asset that seems to assume annotations contain paths only. and KernelParams easily becomes a "special case" among other assets. I'm thinking of abusing .path for storing a raw string...

@mythi yeah, github will only allow it to be assigned if you are a member of the project....
@jodh-intel - is this related to the on-going discussion on adding the ability to modify any config file param via an annotation? If so, I'll /cc @mcastelino here then - and maybe we can assign this to him in the meantime..

Yep, I think so - assigned.

Is the conversation available somewhere? I wonder what is included in any config file param. Just the hypervisor specific?

@mythi - see: https://github.com/kata-containers/runtime/pull/1695.


ProactiveDetection properties should be camel-cased

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[x] Other, please clarify:

The data contract for Proactive Detection properties has always been camel-cased, however the swagger doc uses pascal-casing. The swagger doc was created using the incorrect casing since neither the doc nor the data contract (code) have modified the property names since creation. The data contract cannot be changed as this will break all customers using Proactive Detection. This PR updates the schema in the swagger doc to use camel-casing.

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Microsoft.Insights

@microsoft-github-policy-service agree company="Microsoft"


add utf-8 support.

Tested on my windows 10 zh_CN

So I'm hesitant to accept this since it breaks python3 compatibility, and python 3 handles unicode fine by default.
┬─[william@fillory:~/Dropbox/Projects/jupyter_toc]─[07:59:12 AM]
╰─>$ ./generate_toc.py ~/Dropbox/classwork/2016b/appm3010/lab1/APPM\ 3010\ -\ One\ Dimensional\ Dynamical\ Systems.ipynb
Traceback (most recent call last):
  File "./generate_toc.py", line 41, in <module>
    sys.exit(main())
  File "./generate_toc.py", line 20, in main
    for cell in json.loads(notebook_file.read())['cells']
  File "./generate_toc.py", line 18, in <genexpr>
    for i, s in enumerate(item.encode('utf-8') for sublist in
TypeError: a bytes-like object is required, not 'str'

Maybe make a new file strictly just for python 2?

Sorry for ignoring the compatibility for Python 3 as I've been using Python 2.7 and never give a try on Python 3. I think only support Python 3 is ok.


add terraform section to bind MySQL

@yucwan : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Black screen after startup

A user reported via email (in Ukrainian) that "When the application is opened, a black window appears immediately. After some time, it starts working again."

I guess it will be difficult to debug without knowing the exact Android version and whether the black screen appears always and for how long, but let's create this issue anyway, maybe there are other users experiencing the same behavior.

Thank you. I think, it is this user


Melange does not detect libraries in other places than {/usr,}/lib{64,}

I am working on a hairy package (samba), which provides lots of tools and libraries. Since we want to keep container images as small as possible, those tools and libraries need to be broken into small packages.
Samba makes use of rpaths to make its elf binaries look for libraries in various places under /usr/lib/samba. None of which seems to be captured by the dependency scanner.
E.g. smbclient:
$ patchelf --print-needed smbclient
libreplace-private-samba.so
libsecrets3-private-samba.so
libcli-smb-common-private-samba.so
libmsrpc3-private-samba.so
libcmdline-private-samba.so
libndr-standard.so.0
libsmbconf.so.0
liblibsmb-private-samba.so
libdcerpc-samba-private-samba.so
libsamba-security-private-samba.so
libsamba-credentials-private-samba.so
libsamba-util.so.0
libsamba-errors.so.1
libsamba-hostconfig-private-samba.so
libsamba-debug-private-samba.so
libsamba3-util-private-samba.so
libgenrand-private-samba.so
libpopt.so.0
libtalloc.so.2
libarchive.so.13
libc.so.6

$ sudo melange build ...
2024/10/14 18:02:39 INFO generating package samba-client-smbclient-4.21.0-r0
2024/10/14 18:02:39 INFO scanning for shared object dependencies...
2024/10/14 18:02:39 INFO interpreter for smbclient => /lib64/ld-linux-x86-64.so.2
2024/10/14 18:02:39 INFO   found lib libndr-standard.so.0 for usr/bin/smbclient
2024/10/14 18:02:39 INFO   found lib libsmbconf.so.0 for usr/bin/smbclient
2024/10/14 18:02:39 INFO   found lib libsamba-util.so.0 for usr/bin/smbclient
2024/10/14 18:02:39 INFO   found lib libsamba-errors.so.1 for usr/bin/smbclient
2024/10/14 18:02:39 INFO   found lib libpopt.so.0 for usr/bin/smbclient
2024/10/14 18:02:39 INFO   found lib libtalloc.so.2 for usr/bin/smbclient
2024/10/14 18:02:39 INFO   found lib libarchive.so.13 for usr/bin/smbclient
2024/10/14 18:02:39 INFO   found lib libc.so.6 for usr/bin/smbclient
2024/10/14 18:02:39 INFO scanning for commands...
2024/10/14 18:02:39 INFO   found command usr/bin/smbclient
2024/10/14 18:02:39 INFO scanning for pkg-config data...
2024/10/14 18:02:39 INFO scanning for python modules...
2024/10/14 18:02:39 INFO scanning for ruby gems...
2024/10/14 18:02:39 INFO scanning for shbang deps...
2024/10/14 18:02:39 INFO   runtime:
2024/10/14 18:02:39 INFO     so:ld-linux-x86-64.so.2
2024/10/14 18:02:39 INFO     so:libarchive.so.13
2024/10/14 18:02:39 INFO     so:libc.so.6
2024/10/14 18:02:39 INFO     so:libndr-standard.so.0
2024/10/14 18:02:39 INFO     so:libpopt.so.0
2024/10/14 18:02:39 INFO     so:libsamba-errors.so.1
2024/10/14 18:02:39 INFO     so:libsamba-util.so.0
2024/10/14 18:02:39 INFO     so:libsmbconf.so.0
2024/10/14 18:02:39 INFO     so:libtalloc.so.2
2024/10/14 18:02:39 INFO   provides:
2024/10/14 18:02:39 INFO     cmd:smbclient=4.21.0-r0
2024/10/14 18:02:39 INFO   installed-size: 211243
2024/10/14 18:02:39 INFO   data.tar.gz digest:<PHONE_NUMBER>6b9a3a5af23caa068d7e7a36f7f1631a861542c38a2db5183a430c
2024/10/14 18:02:39 INFO wrote packages/x86_64/samba-client-smbclient-4.21.0-r0.apk

All (missed) lib*-private-samba.so files are located in /usr/lib/samba. There should be a way to scan those and somehow provide them as:
scanning for shbang deps...
  runtime:
    so:samba/lib*-private-samba.so.X

https://github.com/chainguard-dev/melange/blob/4ee7f9ca6fa6975025c2a5511cbd0e919c691fd4/pkg/sca/sca.go#L175


Identifier 'angular' must be imported from a module

1.0.0-beta.1 gives a type error when used with TypeScript:
ERROR in [...]/node_modules/angular-ui-router/commonjs/ng1/services.d.ts
(2,27): error TS2686: Identifier 'angular' must be imported from a module

Repro here: https://github.com/jonrimmer/typescript-bug
npm install
tsc bug.ts

node_modules/angular-ui-router/commonjs/ng1/services.d.ts(2,27): error TS2686: Identifier 'angular' must be imported from a module

So, I was thinking this might be a TypeScript issue, so have raised it there as well: https://github.com/Microsoft/TypeScript/issues/10638#issuecomment-243788466

I believe it's not just ui-router's error, because i'm getting that one on each my file where i using interfaces from angular.

According to mhegazy:

this is an issue in angular-ui-router declaration file. The compiler tries to ensure that a UMD module is used consistently, either as a module or as a global.

File: node_modules\angular-ui-router\commonjs\ng1\services.d.ts

should be:

import * as angular from "angular";
import IInjectorService = angular.auto.IInjectorService;

thanks @jonrimmer

This was fixed in beta.3 via 71bfaa0599f897f47418300d144de523f6232021


RFE: offline mode

It would be really great if this could be setup to work in offline mode with the cache, so that even without an internet connection I can access all my files.
I'd be happy if doing a full sync was a command that I had to run periodically.

FYI Grive stopped working a few days ago.

There is another project to access Google Drive that should work offline.


Pending operations being performed in incorrect order

I have an interface IDocument and an implementing type InvoiceDocument. I want to create a new version of an InvoiceDocument, but soft-deleting the old one and adding a new one:
// Load the existing version
var doc= await session.LoadAsync<InvoiceDocument>(myGuid);

// Soft-delete the existing version
session.Delete<InvoiceDocument>(myGuid);

// Change the ID of the document, so it can be added as a new version
doc.Id = Guid.NewGuid();

session.Store(doc);

I've configured a unique index to ensure there is only ever one version of each document with mt_deleted = false (that is, only ever one 'active' version) - so the order of operations is important; I need to soft-delete the existing version before adding the new one.
But Marten is trying to perform them out of order, so I get an exception. If I examine session.PendingChanges._operations just prior to the call to SaveChanges(), I see 2 values in the list:

Upsert the InvoiceDocument
Delete an IDocument

If I change the first line to:
var doc= await session.LoadAsync<IDocument>(myGuid);
... then it works, with both operations being added in the correct order in a single _operations list value. I guess there is some kind of issue with inheritance here?

What version of Marten are you on? I thought we'd finally managed to get the operations to run in exactly the order you cause them on IDocumentSession. And were you using an auto dirty checked session by chance?

I'm on the latest on Nuget, 2.3.2, and I'm using LightweightSession()

Would you mind making a PR with a failing test for this? It's perfectly possible that it's related to the type hierarchy here.

Sure, will do

I opened PR #900 with a failing test for this.
This is a bit of an odd one... the bug only seems to manifest when:

there are multiple implementations of BaseAccountingDocument
there are multiple levels of inheritance
BaseAccountingDocument contains multiple properties with non-builtin types


Use a linear Color type instead of DVec3 for color calculations

Color calculations for ray tracing must be done in linear color space, and so far I have just been using DVec3 for that. But, I think it would be nice to specify that the type is a color, so that we have more of the business logic encoded in the type system, avoiding future potential errors.
Using Palette::Rgb with T: f64 might be nice. It would play well with later conversion to Srgb for saving the image off. Or, maybe a simple NewType pattern would suffice.

Actually, I think we want to use a NewType pattern. Using Palette would lose optimizations that glam implements for DVec3 operations.

I am convinced we will want to use a new type pattern around the DVec3.
This will introduce boilerplate - we will need pass-through functions and trait implementations to avoid constantly needing to get the color as a DVec3 to perform operations. But, I think it's worth it to make the interfaces more clear and to enforce type expectations (such as ensuring we are actually providing a Color where we expect and not the various other vectors we are using during calculations)

https://rust-unofficial.github.io/patterns/patterns/behavioural/newtype.html


Remove empty cookie, header fields from page rules - cache by custom key

The following block is a valid Cache by custom field Page Rule:
{
    "status": "active",
    "priority": 12,
    "actions": [
        {
            "id": "cache_key_fields",
            "value": {
                "query_string": {
                    "include": "*",
                    "exclude": []
                },
                "header": {
                    "include": [],
                    "exclude": [],
                    "check_presence": []
                },
                "host": {
                    "resolved": false
                },
                "cookie": {
                    "include": [],
                    "check_presence": []
                },
                "user": {
                    "device_type": false,
                    "geo": false,
                    "lang": false
                }
            }
        }
    ],
    "targets": [
        {
            "target": "url",
            "constraint": {
                "operator": "matches",
                "value": "www.foo.bar/*"
            }
        }
    ]
}

cf-terraforming correctly generates
resource "cloudflare_page_rule" "{resource_id}" {
	zone_id = "{zone_id}"
	target = "www.foo.bar/*"
	actions {
    cache_key_fields {
      host {
        resolved = false
      }
      query_string {
        ignore = false
      }
      user {
        device_type = false
        geo         = false
        lang        = false
      }
    }
  }
}

and when I terraform apply, the provider will try to send the following request:
{
    "targets": [
        {
            "target": "url",
            "constraint": {
                "operator": "matches",
                "value": "tamasjozsa.net/*"
            }
        }
    ],
    "actions": [
        {
            "id": "cache_key_fields",
            "value": {
                "cookie": {},
                "header": {},
                "host": {
                    "resolved": false
                },
                "query_string": {
                    "include": "*"
                },
                "user": {
                    "device_type": false,
                    "geo": false,
                    "lang": false
                }
            }
        }
    ],
    "priority": 1,
    "status": "active",
    "modified_on": "0001-01-01T00:00:00Z",
    "created_on": "0001-01-01T00:00:00Z"
}

because of the cookie and header empty fields, Page Rules will respond
resource_cloudflare_page_rule_test.go:749: Step 1/1 error: Error running apply: exit status 1
Error: failed to create page rule: Page Rule validation failed: See messages for details. (1004)
.settings[0].value: cookie expects a non empty array.

This PR removes empty cookie and header fields.
Closes #2062

acceptance tests are all passing here
TF_ACC=1 go test ./internal/sdkv2provider -v -run "^TestAccCloudflarePageRule_" -count 1 -parallel 1 -timeout 120m -parallel 1
=== RUN   TestAccCloudflarePageRule_Import
=== PAUSE TestAccCloudflarePageRule_Import
=== RUN   TestAccCloudflarePageRule_ImportWithBrowserCacheTTL30
--- PASS: TestAccCloudflarePageRule_ImportWithBrowserCacheTTL30 (13.32s)
=== RUN   TestAccCloudflarePageRule_ImportWithoutBrowserCacheTTL
--- PASS: TestAccCloudflarePageRule_ImportWithoutBrowserCacheTTL (11.92s)
=== RUN   TestAccCloudflarePageRule_Basic
--- PASS: TestAccCloudflarePageRule_Basic (9.15s)
=== RUN   TestAccCloudflarePageRule_FullySpecified
--- PASS: TestAccCloudflarePageRule_FullySpecified (8.94s)
=== RUN   TestAccCloudflarePageRule_ForwardingOnly
--- PASS: TestAccCloudflarePageRule_ForwardingOnly (8.86s)
=== RUN   TestAccCloudflarePageRule_ForwardingAndOthers
--- PASS: TestAccCloudflarePageRule_ForwardingAndOthers (3.68s)
=== RUN   TestAccCloudflarePageRule_DisableZaraz
--- PASS: TestAccCloudflarePageRule_DisableZaraz (9.86s)
=== RUN   TestAccCloudflarePageRule_Updated
--- PASS: TestAccCloudflarePageRule_Updated (17.58s)
=== RUN   TestAccCloudflarePageRule_CreateAfterManualDestroy
--- PASS: TestAccCloudflarePageRule_CreateAfterManualDestroy (17.42s)
=== RUN   TestAccCloudflarePageRule_UpdatingZoneForcesNewResource
--- PASS: TestAccCloudflarePageRule_UpdatingZoneForcesNewResource (17.14s)
=== RUN   TestAccCloudflarePageRule_CreatesBrowserCacheTTLIntegerValues
--- PASS: TestAccCloudflarePageRule_CreatesBrowserCacheTTLIntegerValues (9.74s)
=== RUN   TestAccCloudflarePageRule_CreatesBrowserCacheTTLThatRespectsExistingHeaders
--- PASS: TestAccCloudflarePageRule_CreatesBrowserCacheTTLThatRespectsExistingHeaders (11.65s)
=== RUN   TestAccCloudflarePageRule_UpdatesBrowserCacheTTLToSameValue
--- PASS: TestAccCloudflarePageRule_UpdatesBrowserCacheTTLToSameValue (91.65s)
=== RUN   TestAccCloudflarePageRule_UpdatesBrowserCacheTTLThatRespectsExistingHeaders
--- PASS: TestAccCloudflarePageRule_UpdatesBrowserCacheTTLThatRespectsExistingHeaders (15.87s)
=== RUN   TestAccCloudflarePageRule_DeletesBrowserCacheTTLThatRespectsExistingHeaders
--- PASS: TestAccCloudflarePageRule_DeletesBrowserCacheTTLThatRespectsExistingHeaders (33.81s)
=== RUN   TestAccCloudflarePageRule_EmptyCookie
--- PASS: TestAccCloudflarePageRule_EmptyCookie (9.29s)
=== CONT  TestAccCloudflarePageRule_Import
--- PASS: TestAccCloudflarePageRule_Import (12.10s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/sdkv2provider	302.289s

@tamas-jozsa looks like the regex above didn't run all the page rule tests. we do have a couple of failures for diffs after apply - https://github.com/cloudflare/terraform-provider-cloudflare/actions/runs/4069172006/jobs/7008675532#step:6:595

@jacobbednarz apologies for that, I pushed this PR to fix them: https://github.com/cloudflare/terraform-provider-cloudflare/pull/2213
looks like there was some bad test data there

no sweat; this was my bad missing the test cases when running the acceptance tests.
thanks for the PR!


Remove the internal / external folders for the services

Also:

removed GoogleCaptcha service which was blank
fixed a syntax omission in confirm.company test

IDVA31-1276

CI: No security warnings found


previewer: overlapping collapse in zip preview tree

Problem:

[ ] generate div id as "full-path" in the tree

Closed by: https://github.com/inveniosoftware/invenio/pull/2755


[REQ] No translation for help

Is your feature request related to a problem? Please describe.
see title
Describe the solution you'd like
Add translation
Describe alternatives you've considered
Additional context

What part? Hilfe is translated?

But all the text below is English.

Yes, got it

Assiging to you to update de language file. Latest beta introduces localized strings for this (see en language file)

Added in https://github.com/jeroenterheerdt/HAsmartirrigation/releases/tag/v2023.9.0-beta8. Please update de language file. Also tagging French language owner @diyanei and Italian language owner @valerix85 so they can eventually update their respective languages as well.

Because of #222 I reopened

I changed my UI to German and see this:

So looks good to me, not sure what is going on on your end though.

Very Weird. I have three installations.

A virtual machine on Proxmox. Productive system
A virtual machine on Proxmox, for testing purposes
A supervised Installation on my PC, for testing purposes

On each machine I installed v2023.9.0-beta10. I don't see this change. It's still in English when I switch to German. When I switch to the new languages Italian, French and Spanish on all machines All I see is English.
I will close #222 because it's seems to be the same reason.

In /frontend/localize.ts I found following:

The explanation is:
Cannot find module 'intl-messageformat' or its corresponding type declarations.ts(2307)

In /frontend/localize.ts I found following:

The explanation is:
Cannot find module 'intl-messageformat' or its corresponding type declarations.ts(2307)

In /frontend/localize.ts I found following:

The explanation is:
Cannot find module 'intl-messageformat' or its corresponding type declarations.ts(2307)

That is normal if you just opened the file or are you in de dev container when this happens?

Yeah, so no dev container. I still think this is a browser / cache issue. Have you tried another browser? Clearing your browsers cache?

Firefox, Vivaldi and Companion App. All caches deleted an restarted. Don't know what else.

When I push something to the repository I'm getting following since days:

Integration smart_irrigation - /github/workspace/custom_components/smart_irrigation:
Error: R] [SERVICES] Service reset_bucket has no name and is not in the translations file
Error: R] [SERVICES] Service set_bucket has no name and is not in the translations file
Error: R] [SERVICES] Service set_bucket has a field value with no name and is not in the translations file
Error: R] [SERVICES] Service calculate_hourly_adjusted_run_time has no name and is not in the translations file
Error: R] [SERVICES] Service calculate_daily_adjusted_run_time has no name and is not in the translations file
Error: R] [SERVICES] Service enable_force_mode has no name and is not in the translations file
Error: R] [SERVICES] Service disable_force_mode has no name and is not in the translations file
Warning: G] [CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.

Error: Process completed with exit code 1.

Firefox, Vivaldi and Companion App. All caches deleted an restarted. Don't know what else. Also I don't see the new languages, it's all English for them.

neither do I.

When I push something to the repository I'm getting following since days:
Integration smart_irrigation - /github/workspace/custom_components/smart_irrigation:
Error: R] [SERVICES] Service reset_bucket has no name and is not in the translations file
Error: R] [SERVICES] Service set_bucket has no name and is not in the translations file
Error: R] [SERVICES] Service set_bucket has a field value with no name and is not in the translations file
Error: R] [SERVICES] Service calculate_hourly_adjusted_run_time has no name and is not in the translations file
Error: R] [SERVICES] Service calculate_daily_adjusted_run_time has no name and is not in the translations file
Error: R] [SERVICES] Service enable_force_mode has no name and is not in the translations file
Error: R] [SERVICES] Service disable_force_mode has no name and is not in the translations file
Warning: G] [CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.

Error: Process completed with exit code 1.

see #238

not sure what this even is. I have never seen this before. Is this the result of a git command? What is your workflow? What tools do you use? What commands do you run?

Thanks god!
Nonetheless for the record

Commit & Push
workfow? vscode,vscode-json, github, GitHub Pull Requests and Issues and some minor others like ssh, sftp, docker.
Tools see above
hardly at all cli git
aha, understand
Happy to ignore.

Thank you!
This morning I saw everything translated! 😋

Weird but glad it worked!


get rid of empty url parameter section in some redirects

This gets rid of the additional empty ? after some redirects, also some style changes.

@Emilgardis this is what I had in mind, what do you think?

This makes sense and is what I did but in a function, one note about the use of hashmap but 👍🏼


All games unavailable

I have NHL TV subscription but all feed is unavailable.
[URL=https://imageban.ru][IMG]https://i1.imageban.ru/out/2022/10/17/43b9975a8b39600e41e78cddce808871.png[/IMG][/URL]

Unfortunately, they have changed their API and it will require non-trivial code to get it working again. This is already being tracked at https://github.com/kompot/nhl-tv-geeky-streams/issues/59.


SMA EM: Negate power sign for usage pv

Fixes #4399
Ref #4398

Is compilation required in order to test the modified template? if no, what is the default path of the templates?
Thank you for the fast turnaround!

Will be available in next nightly build.


rule34 video downloading broken

Bug description
Attempting to download any mp4 file from rule34.xxx produces an error.
Steps to reproduce

attempt to download any mp4 file from rule34.xxx
Wait
See error

Expected behavior
mp4 file should download.
Context
[Error] Host 'api-cdn-mp4.rule34.xxx' not found for the image: https://api-cdn-mp4.rule34.xxx/images/7330/b7cadfef3e419d78ce0b3b2ccdcce199.mp4: 99 (Network unreachable)
Other filetypes download successfully. Other sources appear unaffected. Grabber appears to be able to access the tags of affected files as usual. The affected files can be accessed normally through the web browser.
System information

Grabber version: 7.12.2 (x86)

Problem appears to have self-corrected.


Views

In this milestone, I implemented the following:

[ ] Implemented the design from the sneak peek wireframes.
[ ] Use methods that you have created in the Blog App - processing data in models.

Hello @mikethreels 👋🏼,
Thank you for reviewing and approving this PR. You are amazing 💯


[WFCORE-3842] Use an actually existing input file for insert-versions…

… in core-galleon-pack
https://issues.jboss.org/browse/WFCORE-3842
My initial fix I screwed up the core-galleon-pack.

Verified, it fixes the issue.


Windows: Calculate PID file after root

Signed-off-by: John Howard<EMAIL_ADDRESS>Astonished this hasn't been noticed before (even by me....). Does later binding of the default PID file - currently the Windows daemon always writes the PID file to c:\programdata\docker.pid (rather than c:\programdata\docker\docker.pid where the default root is), unless an explicit pidfile option is set, even if the root is set to elsewhere such as running dockerd -g c:\control.

Indeed, to follow the root. CI is the short answer.  We can't run DIND on Windows. Two daemons run in parallel on the host. I can't comment on Linux scenarios though.

@vdemeester


The percentage in the change footer is always false by a factor of 100

In the example image, AMD is at 118.21 down from 125.27.
The absolute change is displayed correctly (7.06), but the relative change is actually 5.6% but is displayed as 0.05%
This is always the case for the change footer no matter of the symbol

Confirming I see the same.

Same here

Thank you all for the responses. A fix for this will go out in v1.1.16
Is the plugin currently working for you? Some people are seeing unable to retrieve symbol data errors.

Submitted v1.1.16 today


Error on dataset.pull: TypeError: Api.send_request() got an unexpected keyword argument 'params'

dataset.pull does not work because it is sending a params keyword argument to Api.send_request() that does not exist. Checked the source code and it indeed does not look like that keyword argument is present.
Screenshots

Desktop (please complete the following information):

OS: Ubuntu 22.04
Browser Chrome
Version 22.04

@bendominguez0111 thanks for bringing this up, fixed in latest release (v1.1.0), thanks!


Updated validations.py python script

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #1

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Thank you! I've already accepted the CLA, so it might works now


Attributes of schema extensions can not be dumped

See test case. It was not possible to dump attributes of schema extensions. scim_response_serializer used self.get_attribute_urn to get the URN of EnterpriseUser (which results in attribute_urn to be urn:ietf:params:scim:schemas:core:2.0:user:urn:ietf:params:scim:schemas:extension:enterprise:2.0:user, probably also a bug), which does not get dumped.
This changes the code so that schema extensions are always returned. If no attributes from the extensions are requested, it still always returns a dict with schemas (which is expected).

This is fixed with the help of a serializer that hides attributes coming from Resource:
https://github.com/yaal-coop/scim2-models/blob/34bf363232a75f0bc00d535c33c9dc9686531517/scim2_models/rfc7643/resource.py#L94-L107
Thank you!


[trivial] - fix typo in transfer.md

Fix errant ']' in formatting

@lberk Please sign your PR
git commit -a --amend -s
git push --force

LGTM

bot, add author to whitelist

@rh-atomic-bot retry

bot, retest this please

@rh-atomic-bot retry

@rh-atomic-bot r+

@rh-atomic-bot retry

This is ridiculous I am force merging.  I have no idea what is going on in CI.
@lberk Thanks for the fix.


New App: Tidbyt Clocks

Lists the clocks available on the Tidbyt!!!
Honestly the list was less than I thought it may be...
But this should make @AmillionAirs happy.
Edit: forgot the gif
Edit2: updated gif with correct preview

recheck
this seems to be failing due to the indegostations app. However when I pixlet check locally it gives the thumbs up.

recheck

Updated image with a clock, so it would now be included in the count....


Uplift Field Component for OCS

Issue Description
Uplift Field component.
Issue Type

[ ] New Feature
[x] Enhancement
[ ] Bug
[ ] Other

Field Tech Design
Summary:
The first phase of the uplift will be to maintain existing functionality.
Field can be broken into the following pieces:

Label Group: displays the Label & when applicable, the required asterisk. [See Notes/Questions # 2.A]
Control Group: displays the control and placeholder text
Error Text
Helper Text

Below list the needed themeable variables for each piece.
Responsiveness:

Label, error and helper text will always wrap if the available width is exceeded.
Work needs to be done to determine the feasibility on determining label group width, control width and relational widths. [See Notes/Questions # 1]

Accessibility
None to consider in the first phase of the uplift.
Needed React Props:

labelPosition prop: [string ('above', 'beside')] weather the label should be above or to the left of the control. [See Notes/Questions # 3]

Expected Future Props:

errorIcon prop: [Icon] the error icon to display when a required field was fails validation.[See Notes/Questions # 2.B]
errorIconMessage prop: [node] the information to be displayed in the error icon tooltip when the error icon is present. [Will need additional design input.]
isOptional prop: [bool] appends '(Optional)' to the end of the label. [See Notes/Questions # 2.C]

Themeable Styles
Field Themeable Styles:

Padding Bottom
Border color
Border style
Border image source / linear gradient / border image slice [See Notes/Questions # 4]

- Focused

Border
Box shadow

-Error & Required

Border color

- Error & Required & Focused

Border
Box shadow

Label Group Themeable Styles:

Padding bottom
Line height
Label font size
Label font weight
Label font color
Required asterisk color
Error icon color

Placeholder Themeable Styles:

Font size
Font weight
Font color

Error Text Themeable Styles:

Font size
Font weight
Font color
Padding top

Helper Text Themeable Styles:

Font size
Font weight
Font color
Padding top

Notes / Questions

Spike needed on determining Label Group Width, Control Width and Relational Width. This directly ties with # 2.

The label Group's width must be large enough to display label, required asterisk and error icon at all times.
A. Assuming asterisk dimensions flex on font-size, can you calculate the expected asterisk/icons width to apply to the entire div's width?
B. Need to also consider space for when the error icon is displayed.
C. Need to also consider space for when the appended text '(optional)' is display.

Current designs indicate label should be positioned above or to the left.
A. Should label placement be bidi?

The use of Border image only appears to be supported by >= IE 11.0 (https://www.w3schools.com/cssref/css3_pr_border-image.asp)

Needs More Design Input

What are the width considerations regarding error and helper text?

For question # 3, Lets Just offer above label positioning. Left position can be a later enhancement.

We also may need to spike on the field selection animation that some themes are requesting.

I can assist with that spike. I'm actually responsible for textarea this iteration.

Been looking in more depth & to keep Phase 1 scoped to only uplift current functionality, no additional props will be needed at this time. Implementation regarding the error icon can wait.
Additionally, the themeable aspects of field can be narrows to the label-group, help text and error text. The placeholder and focus styling should be implemented by the control passed into the field as a child.

Updating inError prop to isInvalid.

+1

+1 on tech design. There is an issue I logged related to field but I would not include it within the scope of this tech design as it is a non-passive change, though I did want to raise visibility that the issue exists and if we have non-passive changes we need to make as a part of this tech design, we already have 1 queued up.

The behavior/inclusion of the isInvalid prop will make likely make nonpassive according to @mjhenkes's comment here.

Do we want to call this new package terra-field or terra-form-field?

I would go with terra-form-field for specificity

My vote is for the shortened terra-field.  If this component will be the first to be broken out into a package it will set the standard. I think terra-form-textarea, terra-form-select, and terra-form-checkbox are overly verbose.
I saw that there was a warroom topic over the naming convention, was there a consensus on how they should be named?
These examples feel descriptive to me
terra-select
terra-textarea
terra-field

For the labelPosition prop, is this just the difference between inline and block labels?

@StephenEsser We agreed to append form to the labels of these components to continue to group them together with forms. We agree that terra-form-field would be cumbersome to type however we expect people to alias the components:
import field from 'terra-form-field';

This has been released in terra-form-field 1.0.0

Orion JIRA created


Create JSON-schema for EO profile validation

It'd be good to have a JSON-Schema file that can be used to validate the Earth Observation profile, so people can check that they're compliant.
cc @jeffnaus & @matthewhanson

I could definitely support here as I am familiar to both EO extension and JSON schema. Not sure how familiar @matthewhanson is with JSON schema?

Haven't dealt much with JSON schema, I'd take a crack at it because I did want to figure it out but won't have time until week after next. So if you get some spare time and want to do it have at it @m-mohr

I'll put it on my list, but not sure either about time. We should first concentrate on getting the EO extension renamed and the other fields for the datasets added etc. (see https://github.com/justinwp/stac-spec/blob/feat/dataset/extensions/stac-eo-spec.md)

Yup, definitely lower priority on this one - let's focus on the 'must-haves' first. Plus all those things shifting might lead to tweaks to EO profile.

New PR: #266

Got merged, thanks @jeffnaus for the initial work and PR!


Malformed Dates

I was looking at Issue #147 when I noticed a couple of the data dumps to the S3 bucket stored the date field incorrectly.
  {
    "date": "2018--0-4-",
    "salaryBucketId": 2,
    "ethnicityId": 30,
    "percent": 0
  },
  {
    "date": "2018--0-1-",
    "salaryBucketId": 0,
    "ethnicityId": 4,
    "percent": 0.010260457774269928
  }

It looks like these malformed dates correspond to the 2018-01-02T13:53:51.000Z.csv and 2018-04-04T12:42:38.000Z.csv entries in the bucket which appear to be named with fully qualified ISO instead of the 20180102 format used to name the other CSVs in the bucket.
I believe that when the parser tried to extract the dates it did so assuming the non-qualified format resulting in this:
let date = "2018-01-02T13:53:51.000Z.csv".replace('.csv', '')
date = `${date.slice(0, 4)}-${date.slice(4, 6)}-${date.slice(6, 8)}`
=> "2018--0-1-"

Instead of the expected:
let date = "20180102.csv".replace('.csv', '')
date = `${date.slice(0, 4)}-${date.slice(4, 6)}-${date.slice(6, 8)}`
=> "2018-01-02"

I think a regex group matcher could prevent this from happening again
let date = f.replace('.csv', '')
let re = /(?<year>\d{4})-*(?<month>\d{2})-*(?<day>\d{2})/
let {groups: {day, month, year}} = re.exec(date)
date = `${day}-${month}-${year}`

But some type of "migration" might need to be run on the summaries.json file stored in the S3 bucket to fix the broken entries and prevent the bad data from being displayed in the application.

Awesome find!  Will have a chance to fix this weekend.


Problem with generating _id in before.insert hook

I want to change the _id of a document in a before.insert hook.
The document with the changed id is correctly inserted into the collection, but the return value of the insert call still is the original id. Even when using the callback to insert on the server there is no way to get the generated id. This way the caller is unable to find out the id of the newly inserted document.
Example:
Stuff.before.insert(function (userId, doc) {
  console.log("original id:", doc._id);
  doc._id = "12345";
  console.log("inserted id:", doc._id);
});

var id = Stuff.insert(doc, function(err, result) {
  if (err) return console.log("insert error:", err);
  console.log("callback id:", result);
});
console.log("returned id:", id);

The output then is:
original id: B57zZpKtMn67fnN9r
inserted id: 12345
returned id: B57zZpKtMn67fnN9r
callback id: B57zZpKtMn67fnN9r

Interesting... I'm on the fence but leaning towards implementing something that checks the doc._id for changes and then passing that back. I'll think more on it but i think the behavior you're asking for makes sense.

Thanks for the response!
To give a little more background:
I was trying to keep the collection in sync with an SQL table. The idea was to insert the documents into the SQL table in the before.insert hook and set the ID to the one generated on the SQL side. That actually worked great, until I found out that it's impossible to find out the new ID.

I have the same problem.
How to solve?
Please example.


Getting wrong types with prisma client extensions

Bug description
The findFirst interface doesnt report incorrect types on 4.16.1. On 4.15 I didn't have this issue.
How to reproduce
const x = await prisma.user.findFirst({ stripeCustomerId: customerId });

This code is definitely incorrect, it needs a where clause. But it doesn't report it as an error.
If I get rid of the extension code, it correctly reports a type error.
Expected behavior
Type error is shown
Prisma information
const client = (url: string | undefined) =>
  new PrismaClient(url ? { datasources: { db: { url } } } : undefined).$extends({
    model: {
      $allModels: {
        async exists<T>(this: T, where: Prisma.Args<T, 'findFirst'>['where']): Promise<boolean> {
          const context = Prisma.getExtensionContext(this);
          const result = await (context as any).count({ where });
          return result > 0;
        }
      }
    }
  });

Getting rid of the extension works
Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: 18.12.1

Prisma Version
4.16.1

Hey @jakeleventhal, I believe this has been fixed already in an additional candidate to an upcoming patch. I opened a PR that included a fix for this, would you mind installing trying version 4.17.0-integration-client-extensions-fluent-api.1 ?

I did a reproduction using the user information and 4.17.0-integration-client-extensions-fluent-api.1 fixed it.

I can verify, this is fixed with 4.17.0-integration-client-extensions-fluent-api.1
looking forward to next release. thanks for the speedy fix

:shipit: Note: This fix is now available as 4.16.2


How to add gene names on the SE plot from ROSE?

Hi @crazyhottommy,
Can you please guide, how can I add gene names to the Inflection plot from ROSE for super enhancers?
I'll appreciate your help.
Thanks

you will need to first assign a SuperEnhancer to its putative target gene either by nearest TSS or some other more complicated method (using chromatin looping information) and you then plot the inflection plot yourself using R.