Omit unnecessary "ipmanage --auto-remap" after conversion

Is your feature request related to a problem? Please describe.
After the conversion, an ip remapping is performed. This consumes some cpu time and (maybe) also reconfigures webserver configuraton files (I am not perfectly sure about the later):
root       3521 19.0 0.1<PHONE_NUMBER>16 ?      Ss  18:00  3:53 /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/bin/ipmanage --auto-remap -with-public-reload
Describe the solution you'd like
The remapping should normally not be necessary unless the IP address of the server changes. Hence it could be disabled before conversion or omitted after conversion:
# plesk bin ipmanage --auto-remap-ip-addresses false
unless there is a technical reason for it that I don't know about.
Describe alternatives you've considered
Let it run and accept the wait and cpu load.
Additional context
n/a

It seems that we currently do not have a way to turn off IP re-mapping throughout the entire conversion process. We will need to enable it at the end and it will be initiated on reboot after completing the stage.
However, we could consider disabling re-mapping on the first reboot, which could be beneficial. This would prevent re-mapping from being performed twice (on the first boot in AlmaLinux 8 and after completing the stage).

I have rechecked and found that the plesk-ip-remapping.service was disabled during the conversion process, so IP remapping was avoided already.
However, it's important to re-enable the service to ensure that Plesk functions properly. The ipmanage will be started after the conversion is completed. Unfortunately, I don't see a solution to fix this issue at the moment.
Based on my knowledge, ipmanage should not reconfigure anything if the IP addresses have not been changed on reboot. To verify this, it checks the IPAddresses table in the Plesk database.


Conversions

As discussed on the November 22nd teleconference I've tried these changes with the same command line above on an Intel discrete GPU (Arc A770).  Note, this is with recent internal drivers on Linux.  I don't see a benefit with it either.  It actually runs a little slower, but it's close enough the differences are probably noise:
Original code:
~/git/OpenCL-CTS/build$ time ./test_conformance/conversions/test_conversions_orig float_float

test_conversions_orig   float_float
<snip>
Compute Device info:
        Device Name: Intel(R) Graphics [0x56a0]
        Vendor: Intel(R) Corporation
        Device Version: OpenCL 3.0 NEO
        CL C Version: OpenCL C 1.2
        Driver Version: 22.47.024779
        Processing with 512 devices
<snip>
Thread pool exited in a orderly fashion.

real    1m19.247s
user    2m31.115s
sys     0m16.591s

With these changes:
$ time ./test_conformance/conversions/test_conversions_new float_float

test_conversions_new    float_float
<snip>
Thread pool exited in a orderly fashion.

real    1m26.677s
user    1m27.871s
sys     0m19.657s

As above, the "user" benefits are due to the use of one thread vs. two, but the "real" wallclock time is more or less unchanged.

Here are our test results running on a linux machine (w/ dedicated GPU):
Original Conversions
time ./opencl-cts/build/test_conformance/conversions/test_conversions float_float

test_conversions	float_float
Test binary built Nov 27 2022 13:18:21
sizeof( void*) = 8
ARCH:	x86_64
system name = Linux
node name   = openclubuntu
release     = 5.15.0-50-generic
version     = #56~20.04.1-Ubuntu SMP Tue Sep 27 15:51:29 UTC 2022
machine     = x86_64

Random seed:<PHONE_NUMBER>
 Initializing random seed to 0.
Requesting Default device based on command line for platform index 0 and device index 0
Compute Device Name = NVIDIA GeForce GTX 1060 6GB, Compute Device Vendor = NVIDIA Corporation, Compute Device Version = OpenCL 3.0 CUDA, CL C Version = OpenCL C 1.2
Device latest conformance version passed: v2021-02-01-00
Supports single precision denormals: YES
sizeof( void*) = 8  (host)
sizeof( void*) = 8  (device)

Compute Device info:
	Device Name: NVIDIA GeForce GTX 1060 6GB
	Vendor: NVIDIA Corporation
	Device Version: OpenCL 3.0 CUDA
	CL C Version: OpenCL C 1.2
	Driver Version: 510.85.02
	Processing with 10 devices
	Device Frequency: 1784 MHz
	Subnormal values supported for floats? YES
	Testing with FTZ mode ON for floats? NO
	Testing with default RTZ mode for floats? NO
	Has Double? YES
	Test Double? YES
	Has Long? YES
	Testing vector sizes: 	1	1	2	3	4	8	16

conversions...
conversions passed
Thread pool exited in a orderly fashion.

real	9m58.748s
user	12m8.886s
sys	9m54.461s

With these changes
time ./opencl-cts/build/test_conformance/conversions/test_conversions float_float

test_conversions	float_float
Test binary built Nov 27 2022 13:36:27
sizeof( void*) = 8
ARCH:	x86_64
system name = Linux
node name   = openclubuntu
release     = 5.15.0-50-generic
version     = #56~20.04.1-Ubuntu SMP Tue Sep 27 15:51:29 UTC 2022
machine     = x86_64
===========================================================
Random seed:<PHONE_NUMBER>
 Initializing random seed to 0.
Requesting Default device based on command line for platform index 0 and device index 0
Compute Device Name = NVIDIA GeForce GTX 1060 6GB, Compute Device Vendor = NVIDIA Corporation, Compute Device Version = OpenCL 3.0 CUDA, CL C Version = OpenCL C 1.2
Device latest conformance version passed: v2021-02-01-00
Supports single precision denormals: YES
sizeof( void*) = 8  (host)
sizeof( void*) = 8  (device)

Compute Device info:
	Device Name: NVIDIA GeForce GTX 1060 6GB
	Vendor: NVIDIA Corporation
	Device Version: OpenCL 3.0 CUDA
	CL C Version: OpenCL C 1.2
	Driver Version: 510.85.02
	Processing with 10 devices
	Device Frequency: 1784 MHz
	Subnormal values supported for floats? YES
	Testing with FTZ mode ON for floats? NO
	Testing with default RTZ mode for floats? NO
	Has Double? YES
	Test Double? YES
	Has Long? YES
	Testing vector sizes: 	1	1	2	3	4	8	16

conversions...
conversions passed
Thread pool exited in a orderly fashion.

real	0m53.307s
user	3m7.690s
sys	0m41.790s

We have also run on a Windows machine with similar results. Using CLtracer we noted a relatively large chunk of blocking time due to clWaitForEvents in the original conversions code. This blocking call time can be seen in the images below for both original and modified code versions. Running with CLtracer (slows execution down a bit) we found the original code to take 13m and the modified code to take 3m54s.
Windows test machine info:
test_conversions.exe    float_float
sizeof( void*) = 8
ARCH:   Windows
===========================================================
Random seed:<PHONE_NUMBER>
 Initializing random seed to 0.
Requesting Default device based on command line for platform index 0 and device index 0
Compute Device Name = NVIDIA GeForce GTX 1060 6GB, Compute Device Vendor = NVIDIA Corporation, Compute Device Version = OpenCL 3.0 CUDA, CL C Version = OpenCL C 1.2
Device latest conformance version passed: v2021-02-01-00
Supports single precision denormals: YES
sizeof( void*) = 8  (host)
sizeof( void*) = 8  (device)

Compute Device info:
        Device Name: NVIDIA GeForce GTX 1060 6GB
        Vendor: NVIDIA Corporation
        Device Version: OpenCL 3.0 CUDA
        CL C Version: OpenCL C 1.2
        Driver Version: 516.40
        Processing with 10 devices
        Device Frequency: 1708 MHz
        Subnormal values supported for floats? YES
        Testing with FTZ mode ON for floats? NO
        Testing with default RTZ mode for floats? NO
        Has Double? YES
        Test Double? YES
        Has Long? YES
        Testing vector sizes:   1       1       2       3       4       8       16

Original code CLtrace

With these changes CLtrace

OK that's encouraging.  I have access to the same GPU and I can verify a benefit with it (on Windows).  It may just be that our devices don't benefit from this optimization...

My comments still need to be addressed, especially the first one, because we currently have a cl_event leak with these changes:
Possible leak of type cl_event!
    Number of Allocations: 49152
    Number of Retains:     131072
    Number of Releases:    163840

There is also a conflict that needs to be resolved before merging.  Thanks!

PTAL

Merging as discussed in the January 24th teleconference.


Whitelist organization doesn't work

URL to the linked Repo/Org:
https://github.com/scalableminds/webknossos/pull/4200
Steps to reproduce the problem:

One of our team members (member of scalableminds org) created a PR
scalableminds is whitelisted for that repo

What is the expected result?
There should be no CLA request since he is a member of the whitelisted org.
What happens instead?
There is a CLA request.
Other info
We have been using CLA assistant for several months now. We started seeing this issue today on all PRs.

Chiming in a second instance of this: also started seeing it on every PR today after having used it fine for a couple months.

Hi @normanrz @andschwa,   I just checked and I'm sorry It seems like a bug :/.
Anyways,  I have rolled back to the previous version, So CLA Assistant should be working fine :).
You can do Recheck PR now, then the comment and status will be changed.

Thanks for investigating and rolling back. Appreciated!


Fix for https://github.com/keras-team/keras/issues/20425

The issue was caused by the fact that the iterator was not fully consumed and on_epoch_end was not called.
Added an exception to catch this situation in the future.
Added a unit test to test model.fit() with all the combinations of data adapters.

Codecov Report
Attention: Patch coverage is 62.50000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 72.16%. Comparing base (272bb90) to head (35ba7db).
Report is 1 commits behind head on master.

Files with missing lines
Patch %
Lines

...s/src/trainers/data_adapters/py_dataset_adapter.py
57.14%
2 Missing and 1 partial :warning:

:exclamation:  There is a different number of reports uploaded between BASE (272bb90) and HEAD (35ba7db). Click for more details.
HEAD has 4 uploads less than BASE

Flag
BASE (272bb90)
HEAD (35ba7db)

keras
4
2

keras-numpy
1
0

keras-jax
1
0

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #20453      +/-   ##
==========================================
- Coverage   82.01%   72.16%   -9.85%
==========================================
  Files         514      514
  Lines       47239    47243       +4
  Branches     7413     7414       +1
==========================================
- Hits        38741    34092    -4649
- Misses       6704    11487    +4783
+ Partials     1794     1664     -130

Flag
Coverage Δ

keras
72.06% <62.50%> (-9.81%)
:arrow_down:

keras-jax
?

keras-numpy
?

keras-tensorflow
65.91% <62.50%> (+0.01%)
:arrow_up:

keras-torch
64.86% <62.50%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


modifies node_status_re to match load value if it's an integer format

What does this PR do?
This PR matches nodes if the load does not have any decimals. Sample nodetool output below.
Datacenter: dc1
===================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address         Load       Tokens       Owns (effective)  Host ID                               Rack
UN  <IP_ADDRESS>   3 GiB      256          100.0%            12345678-ab123-cd34-ef56-987654321ab  rk1

Motivation
Currently, the check is not submitting the metric since regex was only matching load values with decimal
Versioning

[x] Bumped the version check in manifest.json
[x] Updated CHANGELOG.md. Please use Unreleased as the date in the title
for the new section.

Duplicate of https://github.com/DataDog/integrations-core/pull/803


unix: fix error check when closing process pipe fd

uv__close() does not set errno, it returns the error.  It also never
returns EINTR, it always maps it to EINPROGRESS.
R=@saghul

LGTM


I want to make good header and some logical things like backend and use some coloring scheme using Tailwindcss

Please assign it to me I want to make some changes to it .
good first issue

Hey @ankitsunil530  we currently want contributions on the frontend design. So you can work only on the frontend part.

thanks for assign it me.


Test for cases where client tries to override a non-container in a deep hierarchy

As discussed.

I wasn't quite sure how I would make predictable container suffixes, but this appears to work.

Thanks a lot, @edwardsph , great review. And for others who may jump in here, @edwardsph and I went through it all in a shared-screen video call.


Fix issues due to old numpy versions in dist_test and gcs_test

Previously numpy was installed with apt-get, leading to a version too
old to be compatible with the recently-added autograd dependency of
tensorflow. This change set fixes that.

Test failures are all unrelated.

Jenkins, test this please.


ConnectEx tcp: The semaphore timeout period has expired - does CLI work over proxy?

I'm using the Windows EXE from https://force-cli.heroku.com.
I login to either dev or live, copy the link to Chrome (because it doesn't seem to work in firefox) - page on chrome tells me auth worked ok then after 30 seconds or so the cmd line updates with an error:
ERROR: Get https://login.salesforce.com/id/[...id removed...]/[...id removed...]
: dial tcp <IP_ADDRESS>:443: ConnectEx tcp: The semaphore timeout period has expired.

We have an internet proxy here - is there any way of telling CLI about this proxy or is this a different issue?
Thanks.

Hi Guys,
Any update on this issue. I am still having issues with login on windows.
Thanks
Sravan

Hey Everyone,
This is a very important issue and I hope it will be addressed soon.  Many of us DEVs that work for larger companies with well-established security models are dealing with a proxy and there is currently no intuitive (or any) way to deal with this.  Like the comments above state, the issue is not with getting my browser to display the "you may close this tab" screen, but rather that the command line hangs afterwards and eventually times out.
I have tried using set HTTP_PROXY=etc... in the command prompt.  I have also tried going to the Windows Control Panel and creating environment variables.  I've tried different variations, user:password@proxy.com:80 , etc.  No matter what I try I get the same results.
If this tool is not compatible with a proxy then it needs to state that clearly.  If it is compatible, then it should also state that clearly with the correct steps to make it work.
This tool is a vital part of my workflow and I need to know once and for all if I can use it, or if I have to find something else.  Please reply and advise.

@jarwady, have you tried testing master?  Proxy support was added in #254.

Outstanding @cwarden !  Sorry that I did not know that.
I will read your comments from #254 and post again once I get it working or if I have more questions.
Thank you.

@cwarden I have added the variables as instructed in #254 but unfortunately it has not changed my situation.  Here are the exact values of the two system variables I've added in the control panel.  There are two conventions in use: one is that "proxy.com" is replaced with my actual proxy; and two is that I'm using "http://" for both variable values as instructed in some research I found (however I also tried "https://" and it made no difference).
Variable Name: HTTP_PROXY
Variable Value: http://proxy.com:80
Variable Name: HTTPS_PROXY
Variable Value: http://proxy.com:80
Please let me know if there is anything else I need to do or add/change.  Thanks.

@jarwady, did you build from source?  The last release doesn't have the changes in #254.
I just tested on Windows, and it seems to be working correctly.

@cwarden : Thanks for the great visuals!  I did not build it, but rather downloaded force.exe from the heroku site.  To build it, I assume I need to have Google Go installed, and then run the appropriate command?

I will publish a new release and then you will be able to download a new
binary.
On Wed, Feb 17, 2016 at 11:51 AM, jarwady<EMAIL_ADDRESS>wrote:

@cwarden https://github.com/cwarden : Thanks for the great visuals! I
did not build it, but rather downloaded force.exe from the heroku site. To
build it, I assume I need to have Google Go installed, and then run the
appropriate command?
—
Reply to this email directly or view it on GitHub
https://github.com/heroku/force/issues/51#issuecomment-185374369.

--
Thanks,
Dave

@dcarroll : Thanks!!


Connection to Workstream context??

Adding a pre-chat question creates/adds a context variable to the workstream. Why is this behavior not documented?
Can you please add details on how to use this? default pre-chat customer lookup doesnt work at all when instructions are followed.
Thank you.

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

ID: 781c5ed5-4a1c-24dd-a9d5-55ccf1287c9f
Version Independent ID: d61256b4-832c-7b03-1a73-db7d93a1155f
Content: Configure a pre-conversation survey
Content Source: ce/omnichannel/administrator/configure-pre-chat-survey.md
Service: dynamics-365-customerservice
GitHub Login: @lalexms
Microsoft Alias: laalexan

@anbhar,
The following content is added in the Configure a pre-conversation survey article now.

When you add a question to the pre-conversation survey, a corresponding context variable is created and is displayed in the Advanced settings > Context variables section.

We have improved the content around context variables in collaboration with product managers and are addressing the gaps iteratively. Please let me know if you are still facing issues.
Best regards,
Neeraja

Hello @anbhar
As we haven't heard back from you, I'll be going ahead and closing this issue. Please feel free to reach out in case the issue persists.


[Microsoft.StorageMover] [v2024-07-01] Extract JobRunStatus Enum to Its Own Definition to be Reused by JobDefinitionProperties + JobRunProperties

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.
[x] Other, please clarify:

Update new version (not yet released) - extracting an enum definition used by 2 models to its own definition.

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.

/azp run


Create Generic DamageOnInteract/Attacked Comps/Systems

About the PR

Lightbulb and anomaly contact damage is pretty hardcoded. Changed to use generic systems.
Only like six gloves actually had light bulb protection, changed it so that all gloves get protection as well as hardsuits/EVA suits. Fingerless gloves do not get protection.
Why / Balance

GloveHeatResistanceComponent needed to be removed, it was only used for checking if light bulbs hurt you. AnomalyContact damage was just something that came to mind that probably also didn't need to exist.
With the two new generic systems I can add in things like touching the hot grill with your bare hands hurting you without feeling gross about hardcoding it.
Technical details

Removed GloveHeatResistanceComponent.cs, it was only responsible for determining if light bulbs hurt you.
Removed damage from PowerLightComponent.cs now that damage is declared in its DamageOnInteract component.
Removed PowerLightSystem.cs logic relating to hot bulbs cancelling interactions, it's handled in DamageOnInteract system now.
Removed ContactDamage and ContactDamage related interactions from Anomalies, they are handled by DamageOnInteract and DamageOnAttacked system now. A side-effect of this change is that GORILLA gloves provide no protection because they are technically held in the hand and not equipped to the glove slot.
Created the DamageOnAttacked and DamageOnInteract component and system. Interactions can be cancelled if the user does not have sufficient protection, attacks don't need to be canceled.
Both systems support localized popup messages and changing the sound played when the user takes damage. Damage is determined by using DamageSpecifiers. Protection uses positive DamageSpecifier values. Damage - Protection = Resulting Damage.
TryGetInventoryEntity<T> in InventorySystem.Slots.cs was updated to provide the Entity<T> rather than just the EntityUid. This isn't a breaking change, but it does conveniently give me a way to access the DamageProtection components that I'm checking for.

Media

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

https://github.com/user-attachments/assets/8d7ec147-90ba-4497-b5d3-7b06d02a778b
Breaking changes

Removed GloveHeatResistanceComponent.cs, please use the DamageOnInteract and DamageOnInteractProtection components for determining damage.
Removed damage from PowerLightComponent.cs, please use the DamageOnInteract component.
Removed ContactDamage and ContactDamage related interactions from Anomalies, please use the DamageOnInteract and DamageOnAttacked components for determining damage.

Changelog

:cl:

add: Hardsuits and EVA suits now count as protection for unscrewing lightbulbs.
add: More gloves were given the ability to unscrew light bulbs.

ah, right, forgot
it technically will deal damage now without power, I'll uh, deal with that

also forgot to give protection to entities like borgs which was the whole reason I made this PR, zzz I'm too tired and hungry to remember all the details right

checking if something is both powered and toggled on is kinda hard, in a generic system
my idea was using Delta's ComponentToggler to toggle whether or not the entity has the DamageOnInteractComponent, but it also means that whenever the lights flicker on or off, every single light on the station would have their component removed/added every single time
something tells me that's not really a good idea.......

the big prank would obsolete this :trollface:
- type: TriggerOnActivate
- type: Triggers
  groups:
    Activate:
      selectors:
      - !type:PoweredSelector
      - !type:UserSelector
      handlers:
      - type:DamageOnTrigger
        damage:
          types:
            Burn: 5

the big prank would obsolete this :trollface:
- type: TriggerOnActivate
- type: Triggers
  groups:
    Activate:
      selectors:
      - !type:PoweredSelector
      - !type:UserSelector
      handlers:
      - type:DamageOnTrigger
        damage:
          types:
            Burn: 5

how about the protection against that?

selector that filters user that doesnt have gloves on :trollface:

selector that filters user that doesnt have gloves on :trollface:

hardsuits, eva suits, some random costumes that have gloves for some reason... guh

if the maintainers want this to be an easier to review PR I can split up the DamageOnInteraction and Lightbulb stuff into its own PR


Restore original options editor on core init

Having issues with a workaround put into medium editor core.js.  I, unexpectedly, can't re-use my options object because editor is unexpectedly set (and left) as null.  Current workaround:
var options = { ... }
var editor = { my Medium editor }
Object.defineProperty(options, 'editor', {
  get: function() { return editor; },
  set: function(value) { } //Ignore for write only, non-strict
});

Thanks 🙏


remove_other_approval_rules flag does not actually remove all other approval rules

Describe the bug
Steps to recreate:

Configure your own approval rule in a gitlab project manually (without using gitlab form)
Configure project approval settings via gitlab form and set remove_other_approval_rules: true and add new approval rule

Expected:
Pre existing approval rules to be removed
Actual:
Old approval exists and any new rules combined are both added to merge request settings
GitLabForm version
3.3.2
GitLab version
15.6.3-ee

Hello @M-Murad-Ahmed
I have directly used the GitLabForm version 3.4.0rc3. With this it works without any problems.
Example:
config_version: 3

projects_and_groups:
  "infrastructure/*":
    merge_requests_approvals:
      merge_requests_author_approval: false
      reset_approvals_on_push: true
    merge_requests_approval_rules:
      qa:
        name: "Quality Assurance Team"
        approvals_required: 1
        users:
          - user1
          - user2
      enforce: true

I hope my answer is helpful for you.
Best regards
Felix

+1 to that.
I recommend using v3.4.0rc4, released a moment ago, which contains all known issues with the new syntax fixed.
Or you may wait a day or two for a final release of v3.4.0, which will most probably contain the same code as RC4, unless someone reports a problem using it.

v3.4.0 with the new syntax has been released as a new stable release. Using it should fix your issue, @M-Murad-Ahmed. Please let us know if it did not.


Couldn't findandroid.support.v4.app.ActivityCompat in React Native 0.59.1

Version
Tell us which versions you are using ( you can see the versions in your package.json ):
react-native-audio :  4.2.2
react-native : 0.59.1
react :  16.4.1
using react-native-sound ? Yes/No  No
Expected behaviour :
What were you trying to do and what did you expect to happen ?
Migrated from 0.57 to 0.59.1 While trying to run the android (react-native run-android) I am getting the below error
Path/node_modules/react-native-audio/android/src/main/jav
a/com/rnim/rn/audio/AudioRecorderManager.java:30: error: cannot find symbol
import android.support.v4.app.ActivityCompat;
^
symbol:   class ActivityCompat
location: package android.support.v4.app
Path/node_modules/react-native-audio/android/src/main/java/com/rnim/rn/audio/AudioRecorderManager.java:31: error: package android.support.v4.content does not exist
import android.support.v4.content.ContextCompat;
^
Path/node_modules/react-native-audio/android/src/main/java/com/rnim/rn/audio/AudioRecorderManager.java:105: error: cannot find symbol
int permissionCheck = ContextCompat.checkSelfPermission(getCurrentActivity(),
^
symbol:   variable ContextCompat
Actual behaviour
Not able to run the app
Steps to reproduce
gradle.properties
android.useDeprecatedNdk=true
android.enableAapt2=false
android.useAndroidX = true
android.enableJetifier=true
package.json
"@haskkor/react-native-pincode": "^1.7.4",
"aws-amplify": "^1.1.9",
"aws-appsync": "^1.3.4",
"aws-appsync-react": "^1.1.4",
"babel-polyfill": "^6.26.0",
"buffer": "^5.2.1",
"circular-json": "^0.5.7",
"eslint": "^5.2.0",
"eslint-config-airbnb": "^17.0.0",
"eslint-config-prettier": "^2.9.0",
"eslint-plugin-import": "^2.13.0",
"eslint-plugin-jsx-a11y": "^6.1.1",
"eslint-plugin-prettier": "^2.6.2",
"eslint-plugin-react": "^7.10.0",
"graphql-tag": "^2.7.3",
"jest-expo": "~27.0.0",
"lottie-ios": "3.0.3",
"lottie-react-native": "3.1.0",
"moment": "^2.22.2",
"native-base": "^2.8.1",
"prettier": "^1.13.7",
"prop-types": "^15.6.2",
"react": "16.4.1",
"react-apollo": "^2.1.11",
"react-native": "^0.59.1",
"react-native-animatable": "^1.3.0",
"react-native-audio": "4.2.2",
"react-native-autolink": "^1.4.0",
"react-native-background-upload": "^5.0.0",
"react-native-blur": "^3.2.2",
"react-native-brightcove-player": "^1.3.1",
"react-native-calendars": "^1.21.0",
"react-native-dialog": "^5.1.0",
"react-native-document-picker": "^2.1.0",
"react-native-elements": "^1.0.0-beta5",
"react-native-exit-app": "^1.0.0",
"react-native-fetch": "^2.0.0",
"react-native-firebase": "^4.3.8",
"react-native-flip-card": "^3.5.2",
"react-native-fs": "^2.11.17",
"react-native-google-analytics-bridge": "6.0.1",
"react-native-highlight-words": "^1.0.1",
"react-native-htmlview": "^0.13.0",
"react-native-icon-badge": "^1.1.3",
"react-native-image-crop-picker": "^0.21.3",
"react-native-image-gallery": "^2.1.5",
"react-native-image-picker": "^0.27.1",
"react-native-interactable": "^0.1.10",
"react-native-is-device-rooted": "^1.0.3",
"react-native-loading-spinner-overlay": "^0.5.2",
"react-native-mime-types": "^2.2.1",
"react-native-modal": "^6.5.0",
"react-native-modal-datetime-picker": "^6.0.0",
"react-native-permissions": "^1.1.1",
"react-native-popup-dialog": "^0.15.1",
"react-native-progress": "^3.5.0",
"react-native-progress-bar-animated": "^1.0.6",
"react-native-search-filter": "^0.1.4",
"react-native-searchable-list": "^1.1.3",
"react-native-snap-carousel": "^3.7.2",
"react-native-text-input-enhance": "^1.0.11",
"react-native-touch-id": "^4.3.0",
"react-native-uuid": "^1.4.9",
"react-native-vector-icons": "^4.6.0",
"react-native-video": "4.4.2",
"react-native-video-controls": "^2.2.3",
"react-native-wheel-picker-android": "^2.0.5",
"react-native-wkwebview-reborn": "^2.0.0",
"react-navigation": "^2.18.2",
"react-redux": "^5.0.7",
"redux": "^4.0.1",
"redux-logger": "^3.0.6",
"redux-persist": "^5.10.0",
"redux-thunk": "^2.3.0",
"rn-fetch-blob": "0.10.13"
},
"devDependencies": {
"@babel/plugin-external-helpers": "^7.2.0",
"@babel/runtime": "^7.5.4",
"babel-jest": "23.2.0",
"babel-preset-react-native": "^5",
"jest": "23.3.0",
"metro-react-native-babel-preset": "^0.55.0",
"react-test-renderer": "16.4.1",
"schedule": "0.4.0"
},
In build.gradle file
ext {
buildToolsVersion = "28.0.3"
minSdkVersion = 19
compileSdkVersion = 28
targetSdkVersion = 28
supportLibVersion = "28.0.0"
}
repositories {
    jcenter()
    google()
    mavenCentral()
}
dependencies {
    classpath 'com.android.tools.build:gradle:3.3.1'
    classpath 'com.google.gms:google-services:4.2.0'
	classpath 'com.dynatrace.tools:android:+'

}

When run the app every time for Android getting the issue.

Need to Have androidX

@kiran-mantana  hi ，do you solve this issue ,wo have same problem,😢😢😢

I think it works
npm install --save-dev jetifier
npx jetify

Maybe PR #330 fixes that

npx jetify

not works!

In Android Studio, try Refactor > Migrate to AndroidX. If there is Java code referencing the old support libraries, it'll show which namespaces need to be updated -- click "Do Refactor."  Then npx jetify, clean and rebuild.


Warpwire in RTE with multiple editors on same page

Reported by Brenda Knox
Warpwire embeds being pushed into other editor frames. Current workaround is to pull embed from WW & put in RTE source
https://warpwire.duke.edu/w/8fUFAA/

following up with OIT/WW


RP adapter: convert floor currency to USD

This PR duplicates #1117 but a few ideas moved to initial PR. Closing.


The fan speed will keep going up and down

When using  custom fan curve, the speed of the fan keeps going up and down except when turned off. After clicking armoury crate plan again, the fan returns to normal. I know this question has been asked before, but I didn't get an answer from it. I have uninstalled ARMOURY CRATE and am not using atrofac.

I've  got the same problem on G14 2021. Like some services battle constantly overriting each other's settings.
But seems devs lost interest to this project and we'll not get an answer. That's so sad ;(


CI tests timing out

CI really needs some attention. I had three PRs yesterday and they all failed on one test or another due to timeouts. Tests need to be broken up or streamlined. It shouldn't take 4 hours for tests to run and then timeout.
I'm flagging the 1.5 GB imagenet model and related tests. I think these should be moved to nightly.
https://github.com/apache/incubator-mxnet/blob/master/cpp-package/tests/ci_test.sh#L69-L70
GPU: CUDA10.1+cuDNN7 - 3 hour timeout
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-16500/15/pipeline/46
dist-kvstore tests GPU - 3 hour timeout
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-16512/1/pipeline
Python2: CPU 4 hour timeout
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-16514/1/pipeline/260

Also this one had 3 timeouts:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-16496/3/pipeline/45

https://github.com/apache/incubator-mxnet/issues/16524
Timeout too.

Another on unix-gpu, kvstore http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-16512/4/pipeline/

Unix-gpu kvstore is fixed now, next is looking into other timeouts

Timeout on GPU: CMake TVM_OP OFF
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-16598/2/pipeline/54


Looking for integration datasets with  celltype category intersection

I tried to train a scRNA-seq data set with celltype category intersection between multiple data sets. I would like to ask if there are some data sets with a small amount of data that are recommended?

Apologies for the late response, this repository is now moved to: https://github.com/mctp/single-cell-Databases
I recommend using the Tabula Sapiens dataset instead: https://tabula-sapiens-portal.ds.czbiohub.org/. This dataset covers around 18 different tissues, so you won't need to search through multiple datasets.
To handle data more efficiently, you can downsample your Seurat object using this function in Seurat:
seurat_downsampled_obj <- subset(original_seurat_obj, downsample = 200)
This will downsample your Seurat object based on the active identifier, which can be set to cell type in your case. Use the downsampled object to run your model.


[Bug]: ProtocolError: NS_BINDING_ABORTED on navigation in Firefox

Minimal, reproducible example
import puppeteer from "puppeteer";

const browser = await puppeteer.launch({
	browser: "firefox"
});

const page = await browser.newPage();

await page.goto("https://x.com/"); // Crash!

Background
I've been trying to access x.com with puppeteer through the Firefox browser. For some reason, the Firefox version of puppeteer cannot get past some step of the navigation process unique to x.com and crashes.
Expectation
I expected the redirects to be followed properly and the page to load accordingly.
Reality
This error occurs on page.goto:
file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89
    #error = new ProtocolError();
             ^

ProtocolError: Protocol error (browsingContext.navigate): unknown error Error: NS_BINDING_ABORTED #checkLoadingState@chrome://remote/content/shared/Navigate.sys.mjs:286:28
onStateChange@chrome://remote/content/shared/Navigate.sys.mjs:345:28
 at https://x.com/
    at <instance_members_initializer> (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89:14)
    at new Callback (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:93:16)
    at CallbackRegistry.create (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:19:26)
    at BidiConnection.send (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/bidi/Connection.js:51:32)
    at Session.send (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/bidi/core/Session.js:134:42)
    at Session.<anonymous> (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/util/decorators.js:94:27)
    at BrowsingContext.navigate (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/bidi/core/BrowsingContext.js:303:33)
    at BrowsingContext.<anonymous> (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/util/decorators.js:94:27)
    at BidiFrame.goto (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/bidi/Frame.js:322:22)
    at BidiFrame.<anonymous> (file:///.../Puppeteer%20Firefox%20Testing/node_modules/.pnpm/puppeteer-core@23.0.2/node_modules/puppeteer-core/lib/esm/puppeteer/util/decorators.js:94:27)

Node.js v20.16.0

Puppeteer configuration file (if used)
No response
Puppeteer version
23.0.2
Node version
20.16.0
Package manager
pnpm
Package manager version
9.7.0
Operating system
Linux

@whimboo could you please take a look?

Thanks for the report. We will investigate via https://bugzilla.mozilla.org/show_bug.cgi?id=1908515.

What's the update here

For an up-to-date information about the state of the bug please check the bug as listed on https://github.com/puppeteer/puppeteer/issues/12929#issuecomment-2283775505.

@OrKoN I was initially confused when testing with Puppeteer and Chrome trying to understand why we didn't get any error, but that's only the case when using CDP. When using Chrome + protocol WebDriver BiDi, Chrome has the exact same issue when navigating to x.com, mozilla.com etc...

ProtocolError: Protocol error (browsingContext.navigate): unknown error navigation canceled, as new navigation is requested by scriptInitiated Error
at new UnknownErrorException (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/chromium-bidi/lib/cjs/protocol/ErrorResponse.js:122:39)
at /Users/juliandescottes/Development/git/puppeteer-examples/node_modules/chromium-bidi/lib/cjs/bidiMapper/modules/context/BrowsingContextImpl.js:348:52
at /Users/juliandescottes/Development/git/puppeteer-examples/node_modules/mitt/dist/mitt.js:1:255
at Array.map ()
at Object.emit (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/mitt/dist/mitt.js:1:239)
at CDPClientAdapter.emit (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/chromium-bidi/lib/cjs/utils/EventEmitter.js:55:23)
at #forwardMessage (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/bidi/BidiOverCdp.js:124:14)
at /Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/third_party/mitt/mitt.js:64:7
at Array.map ()
at Object.emit (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/third_party/mitt/mitt.js:63:39) at https://x.com/
at <instance_members_initializer> (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:94:14)
at new Callback (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:98:16)
at CallbackRegistry.create (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:23:26)
at BidiConnection.send (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/bidi/Connection.js:54:32)
at Session.send (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/bidi/core/Session.js:137:42)
at Session. (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/util/decorators.js:104:27)
at BrowsingContext.navigate (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/bidi/core/BrowsingContext.js:309:33)
at BrowsingContext. (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/util/decorators.js:104:27)
at BidiFrame.goto (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/bidi/Frame.js:339:22)
at BidiFrame. (/Users/juliandescottes/Development/git/puppeteer-examples/node_modules/puppeteer-core/lib/cjs/puppeteer/util/decorators.js:104:27)

That's true, thanks for testing! I think we should add a test for this scenario.

@OrKoN I'm about to land https://bugzilla.mozilla.org/show_bug.cgi?id=1914407 , after which we should get the following error message for the navigation issues mentioned in this report:

Navigation was aborted by another navigation

That will be available in Firefox 134. I imagine we should update https://github.com/puppeteer/puppeteer/blob/2747e7f2439484da5a74e1bb547a327f04599ebc/packages/puppeteer-core/src/bidi/Frame.ts#L332 based on this?

yes, or with a dedicated message if we can agree on what to do with aborted navigations in the spec.


Batch download of Favourites

While one can download an entire playlist right now (although I haven't tried a playlist longer than 50 items...), I'm hoping to use youtube-dl to archive my ~800 favourites.
Channel-style (notice that it's specifying the given content to look at with an anchor, and their client-side JS code displays the right thing):
http://www.youtube.com/user/orospakr#g/f
So, if you give youtube-dl that URL, it will actually download the first 50 of your favourites, as well as the first 50 of your uploads, and so on.  It appears to be falling back to a naiive scrape of YouTube IDs out of that page, or something.  Normally in the browser further content is unhidden using the "Show more" button (bad UI, but there it is).
My Videos-style:
http://youtube.com/my_favorites
It's also paginated, and depends on your session (obviously).
Neither of those is particularly ideal.
Maybe there's nothing for it but to use the YouTube Data API?

Are there any new updates or is there still no chance to fetch the favourites of a user?
Regards

There is a chance, that's why this bug is still open. However, someone needs to implement this, and since it's not a high-priority issue for me personally, and I don't have a lot of time, it may take a while for me to do it.
On a closer look, this doesn't seem overly complicated. We need to send requests to http://www.youtube.com/profile_ajax?action_ajax=1&user=orospakr&new=1&box_method=load_playlist_page&box_name=user_playlist_navigator with the following form data (decoded here, with successive page_num values, here 2):
messages:[{"type":"box_method","request":{"name":"user_playlist_navigator","x_position":1,"y_position":-2,"palette":"default","method":"load_playlist_page","params":{"playlist_name":"favorites","encrypted_playlist_id":"favorites","query":"","encrypted_shmoovie_id":"favorites","page_num":2,"view":"grid","playlist_sort":"date","playlist_sort_direction":"desc"}}}]```

I'll see what I can do this weekend, but I'm not making any promises.

So, today, I made a discovery.  Unlike the "Channels" view, if you get to your favourites by clicking on your name in the top right corner and clicking on "Favorites" in the pop down, you'll get an URL that looks like this, which actually displays your favourites as a playlist:
http://www.youtube.com/playlist?list=FLXFUoBbw37pkeDg3NkxOaCw

youtube-dl consumes this just fine and recognizes it as a Playlist, and seems to detect and fetch all of the pages of it.  I have it downloading my entire favourites now.  :D

That is interesting.
I tried exactly the same and I get no results at all.
[/media/personal/YouTube Favourites]$ youtube-dl "http://www.youtube.com/playlist?list=FLVnIUe_Lp4nVYG4eeBRt8Jg&feature=mh_lolz"
[youtube] Setting language
[youtube] PL FLVnIUe: Downloading page #1
[/media/personal/YouTube Favourites]$

Try removing the feature= parameter? (I can't try it again right now)
Also, always make sure that your youtube-dl tree is up to date.  Moving targets and all. ;)


Set up a GCP Project

I think in https://www.kubeflow.org/docs/gke/deploy/project-setup/, step 4 should mention to enable
Cloud Build API.

Can I add that?

@j-wezel I installed Kubeflow 1.0.0 rc4 on GCP without enabling the Cloud Build API. Could you give us more information about why we need to enable it. For example, is it a new requirement for Kubeflow 1.0.1, or did you get an error when running a particular Kubeflow application?

Well you will need it later on when Fairing builds containers with models to be served. Fair enough, it's not required per se, so that should go into the description.

Thank you for the additional information @j-wezel
@imskr Yes, please do create a PR to add the requirement for enabling the API, with a note that it's required if you plan to use Fairing in your Kubeflow cluster.
/assign @imskr


Random number can't go into EmptyLatentImage: width

Number to Int node

I appreciate your help but I'm getting this error when i add the final int to the width field.
Prompt outputs failed validation
Number to Int:

Return type mismatch between linked nodes: number, INT != NUMBER

Looks like you already have a int. Hars to know what you are doing without seeing.

The new random node you made works amazing.


refractoring code snippets

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[ ] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.

But why this PR is closed without merging ? Any issues

The changes you suggested were not deemed necessary.


Add support for LTS Teachers as a type

The member type,  LTS Teacher is not supported.
Describe the solution you'd like
Add support!
Also Open Water

Fixed in 1.3.2


Add bitbox02

Motivation for this change
Preparatory work for supporting BitBox02 in electrum whenever electrum 4.0 comes out.
Removes python2 support from block-io, streamlit, and zeronet, hopefully we're not caring about losing python2 support these days?
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] 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.

@ofborg build python3Packages.block-io python3Packages.py-multihash zeronet streamlit

@nyanloutre I'm quite new to contributing to nixpkgs, is there a proper procedure for dropping python2 support from streamlit, zeronet, and block-io?  I don't think anything changed for us with py-multihash
Thanks!

@reardencode Can you please rebase the PR, there are conflicts. While you are at it, please check whether some of the packages cannot be updated to even more recent versions. Finally, please prefix your commit messages with python3Packages.  so it reads python3Packages.base58 instead of base58. Thanks!


infra: add Segment snippet + page impression to all pages

Using Segment for page tracking enables consistent user IDs with the CockroachDB Cloud console, and allows us to configure where events are sent without redeploying this site. Add the standard Segment snippet, which fires a page impression on-load by default.

This change is

Just an FYI that I have the Segment source disabled server-side for now.  I'll enable it next week, but if anyone reviewing this needs it turned on sooner just let me know!

LGTM! Do you have merge access to docs?

I do!  Thanks for the review!


Support tools and tool_choice parameter in OpenAI compatible service

Also aliased as functions and function_call in deprecated parameters.
https://platform.openai.com/docs/api-reference/chat/create#chat-create-tools
After #1756 is merged (thanks @Tostino!), it should be straightforward to add this as a core parameter to OpenAI compatible service. This will help unlock client libraries using similar interface. Do note that the underlying model need to support function calling (e.g. OpenHermes) and prompt engineering might be needed.
Also see @dongxiaolong's example here: https://github.com/vllm-project/vllm/pull/1756#issuecomment-1827064922

I am confused, is this supported by vllm or not?

vllm openai 接口应该如何使用 tools 和 tool_choice 参数？

Can someone help to confirm if tools/tools_choice is supported? this is not clear from the thread . I am using mistral 8 * 7B instruct model which supports function calling

Can someone help to confirm if tools/tools_choice is supported?

Not yet, tools support is coming with https://github.com/vllm-project/vllm/pull/3237

I really appreciate all the work being done in all attempts so far (#2488, #3237, #4656)! I've been waiting now already months for this...
I'd like to make a suggestion for a two-step approach to add this feature into vLLM. It's a relatively big change and I think it would make things much easier if we would go step-by-step.
Step 1 – support tool_choice set to required or none
In this first step vLLM would support requests where the tool_choice is set to required or none (c.f. https://platform.openai.com/docs/api-reference/chat/create#chat-create-tool_choice). This means that the LLM is either required to generate a tool call or required to not generate a tool call.
Why would this make things easier?
Supporting tool_choice none is trivial – this is what we already do.
Supporting tool_choice required is relatively easy. This is almost equivalent to the current guided_json option. We would need to parse the tool parameter and translate it into something Outlines understands.
We would not need to build any kind of embedded tool prompting or output buffering and parsing into vLLM. This would make the work in #4656 much simpler.
Disadvantages
Not supporting the auto tool_choice means the use-case of agents choosing their next action is not supported.
Step 2 – support tool_choice auto
Once we support the other two use-cases, adding the auto case, should be easier and if not, we would not be blocking all other use-cases one can cover without auto.
@simon-mo I'd really appreciate any feedback on this idea.

@br3no Yes. Thank you for your suggestion and pushing this through.


Add new gateways directory (resolves #31)

Signed-off-by: Simon Stone<EMAIL_ADDRESS>

/azp run


Awesome Admin Dashboard

I cannot express how much I like this admin interface.  I ported it out to my existing Laravel 8 application and love it.  However, trying to find an elegant way of keeping the history of what was selected and maintaining the selected sidebar menu display after a page refresh.  Any suggestions?

Never mind, using Laravel's @if(Request::is('item/*')) for each section and setting isActive/open true with an @else setting it to false. I then took the same approach to set the individual menu item font colors to show that it was selected.


[HOLD] Pusher events possibly arrive out of order. Jumping comments when coming back online as they are created.

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

Coming from https://github.com/Expensify/App/pull/8650
Action Performed:

Add several comments (20) to a report while offline
Go online

Expected Result:

Pusher events sent for all comments in the order that comments are created
No visual jumping of comments

Actual Result:

Some Pusher events never arrive (observed on dev)
Pusher event delivery seems disconnected from report comment creation leading to a perception of jumping comments

Note: This is not solved by the sequential queue as comments may be created in order, but it seems like one of the two things is possible:

Comment events are not showing up at all via Pusher (evident because optimistic action IDs are not replaced)
Pusher events arrive out of order (which causes the jumping effect)

https://user-images.githubusercontent.com/32969087/163501249-a3b68d2c-17fc-4459-8fc0-cf16aa4f81bc.mp4
Workaround:
No.
Platform:

Web (possibly others)

Version Number:
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @marcaaron
Slack conversation:
View all open jobs on GitHub

Ah so testing this on staging and it seems like this won't happen at all after implementing the sequential queue. I think this effect is only observable on dev.

cc @MonilBhavsar if you want to double check that it only happens on dev. Not sure we need to look into it further, but feel free to reopen if you disagree.


Add package info

Currently the version comes from setup.py as version="0.1.3" rather than version=version so, for example, ":Release: |version|" displays as 0: http://minorminer.readthedocs.io/en/latest/

Version comes from conf.py version = u'0.0'
Needs to be stored in one place, as in other projects


inverse transform issue

Hi, Haoyi. Great research work!!
I have a little question about inverse transform. When 'inverse' = True, the data loader will return untransformed data_y. Could you help me understand why we still need to call inverse_transform(outputs) ?
Thanks.

Because the input of model is transformed and we hope the data scale between model's output and input do not differ too much, so we call inverse_transform on model's output.

Because the input of model is transformed and we hope the data scale between model's output and input do not differ too much, so we call inverse_transform on model's output.

Thanks for the reply. When inverse = True, decoder input (X_token) is not transformed. Will decoder outputs be in the same untransformed space as decoder input?

Because the input of model is transformed and we hope the data scale between model's output and input do not differ too much, so we call inverse_transform on model's output.

Thanks for the reply. When inverse = True, decoder input (X_token) is not transformed. Will decoder outputs be in the same untransformed space as decoder input?

Thanks for your remind, this is our negligence, we will fix this problem in the next update.


Font weight inconsistancy

For colors you have a number like:

bg-red-100
bg-red-200

For font-weight you use names for all of them. For new users like me, it may not be very easy to learn all these names. I have always used numbers for them.

Solution 1 (probably not popular)
Start over and rename it to like font-100 etc. That would probably break a lot of sites, not keeping current names around.
Solution 2
Add aliases for numbers.
font-100
font-200
font-300
font-400
font-500
font-600
font-700
font-800
font-900

It will duplicate the amount of css for this but you are already doing that quite a lot and you already have a solution removing unneeded code.

Unlikely that we change this since it would be a breaking change, and I don't love classes like font-600 because it doesn't communicate the fact that it's referring to the weight, unlike font-bold for example.
You can customize all this for your own projects though if you like:
// tailwind.config.js
module.exports = {
  theme: {
    fontWeight: {
      '100': '100',
      '200': '200',
      '300': '300',
      '400': '400',
      '500': '500',
      '600': '600',
      '700': '700',
      '800': '800',
      '900': '900',
    }
  }
}

You are right. font-600 could be line-height or anything. More solid would be font-weight-600.
Because the font weight is increasing, just as with the colors I still think a number is a better approach. Imagine if browsers/fonts will add a new weight like 450, then you need to come up with yet another name for it. I guess that was why you got rid of names for the colors?
Anyway, we can still extend it to whatever we want, which means things like this will not block us in any way. 👍
You can close this if you have made up your mind about it.

@jenstornell Is better if you add them to your  tailwind.config.js file like Adam suggested, that way you get them for all of your utilities, for example class="fw-300 md:fw-500  hover:fw-900"

If you want to go all-in I'd create a new font weight plugin that reads from the same fontWeight keys in the config, and disable the built-in one:
// tailwind.config.js
module.exports = {
  theme: {
    fontWeight: {
      "100": "100",
      "200": "200",
      "300": "300",
      "400": "400",
      "500": "500",
      "600": "600",
      "700": "700",
      "800": "800",
      "900": "900",
    },
  },
  corePlugins: {
    fontWeight: false,
  },
  plugins: [
    function ({ addUtilities, e, theme, variants }) {
      const utilities = Object.fromEntries(
        Object.entries(theme("fontWeight")).map(([key, value]) => {
          return [`.${e(`fw-${key}`)}`, { fontWeight: value }]
        })
      )

      addUtilities(utilities, variants("fontWeight"))
    },
  ],
}

@dazuaz As a new Tailwind user, I did not see the limitations of my approach, with the lack of variations.
@adamwathan Your plugin above was a great starting point for me. For compability I still want to keep the current Tailwind names, but still provide my new names.
Plugin
Here is what I did and it works just as expected.
const plugin = require('tailwindcss/plugin');

module.exports = {
  theme: {},
  variants: {},
  plugins: [
    plugin(function ({ addUtilities, e, theme, variants }) {
      const utilities = {};

      for (i = 100; i <= 900; i += 100) {
        utilities[`.fw-${i}`] = {
          fontWeight: i
        };
      }

      addUtilities(utilities, variants("fontWeight"));
    })
  ]
}

It adds the new font weights below on top of Tailwinds current classes.
.fw-100
.fw-200
.fw-300
.fw-400
.fw-500
.fw-600
.fw-700
.fw-800
.fw-900

Be aware, the plugin loops out the number in a linear way. To add support for like .fw-356, a more manual approach is needed to build the array.


fix: transpiler should rebuild when noir is changed

Please read contributing guidelines and remove this line.

Benchmark results
Metrics with a significant change:

note_trial_decrypting_time_in_ms (8): 16.4 (-85%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit f31c181f and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,412
179,524
716,068

l1_rollup_calldata_gas
221,680
866,932
3,447,892

l1_rollup_execution_gas
314,167
984,672
3,667,549

l2_block_processing_time_in_ms
1,155
4,364 (+1%)
17,312 (+1%)

note_successful_decrypting_time_in_ms
304 (+2%)
1,002 (+4%)
3,772 (+5%)

note_trial_decrypting_time_in_ms
:warning: 16.4 (-85%)
36.5 (-59%)
145 (-1%)

l2_block_building_time_in_ms
18,207
72,099
289,667

l2_block_rollup_simulation_time_in_ms
13,058
51,666
208,233

l2_block_public_tx_process_time_in_ms
5,120
20,288 (+1%)
81,183 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,735
26,509 (+1%)

note_history_successful_decrypting_time_in_ms
2,571 (+10%)
4,656 (-2%)

note_history_trial_decrypting_time_in_ms
91.9 (-2%)
233 (+6%)

node_database_size_in_bytes
17,297,488
33,050,704

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
309 (-1%)
44,481
26,193

private-kernel-ordering
194
44,513
14,929

base-rollup
1,404
128,970
881

root-rollup
83.0 (+1%)
4,088
677

private-kernel-inner
411
71,640
26,193

public-kernel-private-input
242
32,615
26,193

public-kernel-non-first-iteration
242
32,657
26,193

merge-rollup
7.66 (+1%)
2,608
881

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
2 leaves
8 leaves
16 leaves
32 leaves
128 leaves
64 leaves
512 leaves
1024 leaves
2048 leaves
8192 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.2 (+1%)
10.6 (-4%)
12.6
17.0 (-1%)
22.8
63.8
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.9
17.5
23.0
31.6
47.0
143
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.595 (+1%)
0.591 (-4%)
0.537
0.525 (-1%)
0.478
0.440
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
N/A
N/A
N/A
74.8 (+1%)
47.6
240 (+1%)
461
900 (+1%)
3,556 (+1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
N/A
N/A
N/A
159
96.0
543
1,055
2,079
8,223

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.463
0.488
0.437
0.432
0.428
0.427

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
N/A
N/A
N/A
103
56.9 (+1%)
348 (-2%)
689
1,368 (+1%)
5,435 (+1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
N/A
N/A
N/A
197
104
691
1,363
2,707
10,771

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.491
0.496
0.474 (-2%)
0.474
0.473
0.473 (+1%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
56.6 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
94.1
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
0.577
N/A
N/A
N/A
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,575
37,975

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
586 (+7%)
1,373

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.609 (+28%)
630


Fixed bundling failure due to missing prettyprint module.

Just added a reference to the prettyprint module in the interleaved entry point file.

We don't actually need prettyprint in the bundle, only in the REPL. I've committed 575a8a3c9bd61b7e19f557bb7459611054b7c94a to fix it.
Thanks!


missing security feature: ocsp for checking website certs

Description
add ocsp feature behind a flag
Who's implementing?

[ ] I'm willing to implement this feature myself

The problem
I undestand the scope of this project and the no-phone-home privacy that it achieves.
I also read the point about why safe browsing features are removed.
What I ask here is: is the security impact of not querying ocsp justified by the "privacy/transaparency" obtained?
I think that ocsp is different from safe browsing: ocsp is not an arbitrary trusted whitelist controlled by one entity; at least in theory, is a standardized specification with multi-party partecipant. It is still centralized over a small set of entity (and I think that the built-in implementation in chromium heavily query over google servers). But it's still a feature part of the open-web, and it's a protocol that describes a vendor-agnostic way to enanche a security aspect of a web-browser.
What about still build-in this feature in the browser and permit to enable it with a flag?
What are your positions about ocsp features?
Possible solutions
.
Alternatives
No response
Additional context
No response

Duplicate of #2719


WIP: Using Jinja for Configuration Templates

@Mierdin Please review our lessons.

@ShrutiVPawaskar Per https://antidoteproject.readthedocs.io/en/latest/contributing/curriculum.html#step-4-get-it-reviewed, please include a changelog update - that's why CI is failing.
In addition, as a heads up, there are a lot of commits here with the same name. I would prefer that you squash them into a handful of meaningful commits - in its current state I would likely squash instead of merge, and I'd rather you get the credit.


JavaScript block comment with arrow in HTML script - Expression expected / Unterminated regular expression literal.

Bug Report
🔎 Search Terms

javascript, html, error, comment, regex, arrow
🕗 Version & Regression Information
Occurs in Version 1.74.3
All extensions have been disabled for the workspace.
💻 Code
<script>
/* --> */
</script>

🙁 Actual behavior
Console shows 2 problems:

Expression expected.
Unterminated regular expression literal.

Full errors:
[{
"resource": "test.html",
"owner": "generated_diagnostic_collection_name#1",
"severity": 8,
"message": "Expression expected.",
"source": "javascript",
"startLineNumber": 2,
"startColumn": 8,
"endLineNumber": 2,
"endColumn": 9
}]
[{
"resource": "test.html",
"owner": "generated_diagnostic_collection_name#1",
"severity": 8,
"message": "Unterminated regular expression literal.",
"source": "javascript",
"startLineNumber": 2,
"startColumn": 10,
"endLineNumber": 2,
"endColumn": 10
}]

It even shows more errors for every pair of -- within the comment block.
e.g.
<script>
/* --> ----------------------------- */
</script>

Results in a total of 16 errors logged (15 x expression expected, 1 x Unterminated regular expression literal.)
🙂 Expected behavior
Ignore whatever is in comments.

Will re-create issue in vscode repo ...


Fix masquerading in NFT backend

This should fix the persistent test flakes observed in the following e2e tests (when run against the nft backend):

should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]
should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance]
should have session affinity work for NodePort service [LinuxOnly] [Conformance]

Changes include:

Preventing the masquerading of local traffic directly within the host
Configuring the correct CLUSTER_CIDR values so that the rest of the values are masqueraded.

/assign @mcluseau

/lgtm

/approve


Section B.3.1.5, FCS_TLSS_EXT.1.3 (and others)

FCS_TLSS_EXT.1.3 (and others) includes “of size 2048 bits” and “ffdhe2048” selections. These selections are of different level of details that potentially overlap (i.e., ffdhe2048 is of size 2048 bits). Is the intent behind “of size 2048 bits” is to specify MODP (RFC 3526) groups? If so, why not do so directly?

The wording could be tightened up to differentiate ffdhe and other DHE key agreement.
The generic sizes are meant to be generic and not necessarily refer to RFC 3526 groups. Per FCS_CKM.2, a TOE can theoretically (even if unlikely) use FIPS 186-Type FFC Parameter-size Sets.

TLSWG agrees there's some overlap and it's a little ambiguous, but clear enough with the app note explanation. This issue is on hold due to possible deprecation of ffdhe for TLS, https://mailarchive.ietf.org/arch/msg/tls/iZGV0kKHfbV5MrO-owB8mFwfffw/.

This issue was resolved in NDcPPv3.0e.


Issue when generating OData Client with the OData Generator

Issue Description

Errors occurred when generating OData Client with the OData Generator.
It seems I found the workaround, but I would like to know root cause of this issue.
Workaround :
When I removed too much Annotation parts, it works well.
Important information:

Your code : https://github.com/micol92/cloudsdkissue

Expected outcome :  successful creation of OData client

Actual outcome : errors occurred like below.

$> mvn clean install
....
[ERROR] Failed to execute goal com.sap.cloud.sdk.datamodel:odata-v4-generator-maven-plugin:4.27.0:generate (generate-consumption) on project testmysdkapp02-application: Execution generate-consumption of goal com.sap.cloud.sdk.datamodel:odata-v4-generator-maven-plugin:4.27.0:generate failed: trying to create the same field twice: ???????? -> [Help 1]

Steps attempted to resolve the issue
When I removed too much Annotation parts in EDMX file, it works well.

In case of issues with any of our VDMs:

What happens when a request is performed directly via an HTTP client tool such as Postman?
In case that succeeds please provide details on the request such as URL, query parameters, header parameters, prerequisite requests (e.g. CSRF token), etc.

Potentially missing information (open questions you might have)

Impact / Priority

Affected development phase: e.g. Getting Started, Development, Release, Production
Impact: e.g. No Impact, Inconvenience, Impaired, Blocked
Timeline: e.g. Go-Live is in 12 weeks.
Error Message
Please paste your stracktrace here within the backticks (replacing this comment)

Project Details

SDK Version:

Link to GitHub repo:
Project type, for example:

[ ] CAP Project
[ ] SDK Maven Archetype
[ ] None of the above:

Platform:

[ ] Cloud Foundry
[ ] Deploy with Confidence (Cloud Foundry)
[ ] None of the above:

Checklist

[ ] Checked out the documentation and Stack Overflow
[ ] Description provided with all relevant information
[ ] Exception and stack trace provided
[ ] Attached debug logs
[ ] Attached dependency tree
[ ] Provided Cloud SDK version & link to relevant source code

Hi @micol92,
thanks for reaching out to us.
The issue you are experiencing is (most probably) caused by two fields in the same EDMX type that do have the same SAP__common.Label annotation value.
This is because, by default, the OData generator uses the value of the SAP__common.Label (if it exists) to generate the field name.
(Background: Our experience has shown that those labels are often times more speaking and, therefore, semantically more meaningful.)
Luckily, you can easily change that behavior by specifying the <nameSource>NAME</nameSource property in the Maven Plugin configuration like so:
<plugin>
    <groupId>com.sap.cloud.sdk.datamodel</groupId>
    <artifactId>odata-v4-generator-maven-plugin</artifactId>
    <version>4.27.0</version>
    <executions>
        <execution>
            <id>generate-consumption</id>
            <phase>generate-sources</phase>
            <goals>
                <goal>generate</goal>
            </goals>
            <configuration>
                <inputDirectory>${project.basedir}/src/main/resources/edmx</inputDirectory>
                <outputDirectory>${project.build.directory}/vdm</outputDirectory>
                <deleteOutputDirectory>true</deleteOutputDirectory>
                <packageName>com.mycompany.vdm</packageName>
                <defaultBasePath>sap/opu/odata/sap/</defaultBasePath>
                <compileScope>COMPILE</compileScope>
                <serviceMethodsPerEntitySet>true</serviceMethodsPerEntitySet>
                <nameSource>NAME</nameSource> <!-- add this line -->
            </configuration>
        </execution>
    </executions>
</plugin>

With above configuration, I can generate the clients for your service specifications.
Best regards,
Johannes

Thank you so much.
I’ve confirmed that it works well. 😊
For your reference,
My customer is performing ERP project, and also they are leveraging BTP as side-by-side extension for ERP.
For the application development in BTP, they’re using Java language with SAP Cloud SDK.
As I know,  when external application requests C/U/D transaction of ERP, it sends CSRF token(exact name: x-csrf-token) to ERP.
I’m wondering how CSRF token is handled with Cloud SDK for Java.
Unfortunately,  I couldn’t find useful information in  SAP Cloud SDK site (sap.github.io).
If available, please share the example source or ideas.
Please let me know If I have to register this inquiry to issue list.
Thanks and Best Regards
Jungwoo
보낸 사람: Johannes Schneider @.>
날짜: 금요일, 2023년 11월 24일 오후 4:47
받는 사람: SAP/cloud-sdk-java @.>
참조: Han, Jungwoo @.>, Mention @.>
주제: Re: [SAP/cloud-sdk-java] Issue when generating OData Client with the OData Generator (Issue #156)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Hi @micol92https://github.com/micol92,
thanks for reaching out to us.
The issue you are experiencing is (most probably) caused by two fields in the same EDMX type that do have the same SAP__common.Label annotation value.
This is because, by default, the OData generator uses the value of the SAP__common.Label (if it exists) to generate the field name.
(Background: Our experience has shown that those labels are often times more speaking and, therefore, semantically more meaningful.)
Luckily, you can easily change that behavior by specifying the NAME</nameSource property in the Maven Plugin configuration like so:

<groupId>com.sap.cloud.sdk.datamodel</groupId>

<artifactId>odata-v4-generator-maven-plugin</artifactId>

<version>4.27.0</version>

<executions>

    <execution>

        <id>generate-consumption</id>

        <phase>generate-sources</phase>

        <goals>

            <goal>generate</goal>

        </goals>

        <configuration>

            <inputDirectory>${project.basedir}/src/main/resources/edmx</inputDirectory>

            <outputDirectory>${project.build.directory}/vdm</outputDirectory>

            <deleteOutputDirectory>true</deleteOutputDirectory>

            <packageName>com.mycompany.vdm</packageName>

            <defaultBasePath>sap/opu/odata/sap/</defaultBasePath>

            <compileScope>COMPILE</compileScope>

            <serviceMethodsPerEntitySet>true</serviceMethodsPerEntitySet>

            <nameSource>NAME</nameSource> <!-- add this line -->

        </configuration>

    </execution>

</executions>

With above configuration, I can generate the clients for your service specifications.
Best regards,
Johannes
—
Reply to this email directly, view it on GitHubhttps://github.com/SAP/cloud-sdk-java/issues/156#issuecomment-1825265968, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJNJCWT6NSMO7AY76EW74KLYGBGIBAVCNFSM6AAAAAA7X2VKBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRVGI3DKOJWHA.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @micol92,
the SAP Cloud SDK handled the retrieval of CSRF tokens for OData requests automatically under the hood.
Unfortunately, I can not point you to any documentation - it seems this is actually lacking at the moment.
As we are in the process of reworking our connectivity related documentation anyways, I'll make sure we have that topic covered as well.
Best regards,
Johannes

thank you for your reply. I've successfully created  sales order record in S/4HANA using standard cloud sdk. As you mentioned, I've confirmed that I don't need to take care CSRF token logic.
The final question is, does that automatic CSRF logic apply equally to the  OData clients generated with OData Generator ?
Best Regards
Jungwoo

Hi @micol92 ,
Yes that is correct, the automatic CSRF logic also applies to OData clients generated with the OData generator.
Regards,
Kavitha

Thanks to your support, we solved issues. thanks again.
I am not sure if I should ask this question. I ask for your indulgence.
I have to use ".withServicePath(service path)" like manual guide because EDMX file doesn't contain correct namespace for S/4HANA OData V4 path.
Cloud SDK Manual : https://sap.github.io/cloud-sdk/docs/java/features/odata/vdm-generator
When I need to use function ".withServicePath(service path)”, I would like to store service path in my source or elsewhere, because service path sometimes may change.
Can you please guide me on the right way to do this?
BR, Jungwoo.

thank you team.
Solutions suggested seems very helpful. My customer is currently storing service path into database.  Maybe they will decide which way is more useful.
BR, Jungwoo.

Hi @micol92,
glad to head that everything seems to be working fine.
I'll close the issue for now.
Please don't hesitate to open a new ticket in case of further questions and/or problems.
Best regards,
Johannes


V<IP_ADDRESS>

@cadexproject Looks like you pointed this PR at the upstream Dash repo accidentally.

Wrong repo. Closing.


Fix page unload bug and integrate do not track settings with new tracker

Fixes a bug retrying identify calls on page unload
Respects browser do not track settings in new tracker

Tested manually

@AndrewJakubowicz no additional testing needed, would be great if this could go out today!


fix: Correctly resolve classes with FindClass(..)

JNIEnv's FindClass(..) function takes the classes in the standard
foo/bar/Baz class specification (unless they're special, like arrays).
Specifying them with Lfoo/bar/Baz; results in a
ClassNotFoundException being raised -- which is especially unhelpful
when intending to re-throw an exception.
Fixes: #1120

@NickGerleman wrote in another PR that yoga has been without a full-time maintainer.
@NickGerleman, would you be able to have a look at this PR as well?
It is bringing down the hostapp with a ClassNotFound exception when yoga wants to tell us what is really wrong instead of rethrowing it.

Oh, nice - fixing it in the facebook/react-native repo automatically pushed the fix here.
I guess this PR can be closed!


HEX COLOR GENERATOR

#757
Added Hex Color Generator
Close #757
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md

I have successfully completed #757 issue,Can you pls merge it. @pranjay-poddar


IDA 9.0 porting

Since IDA decided to *** as always the entire plugins community by removing pretty much all functions in ida_enum and ida_struct, we need to port every plugins to new IDA9.X API.
is this planned for this plugin ? i'm working on a patch myself but not so serious code, only relevant part for my usage.

We are working on a new version for Ida 8.4. I am not familiar with the changes made to the API in version 9. I guess we will have to look into that.

Since IDA decided to *** as always the entire plugins community by removing pretty much all functions in ida_enum and ida_struct, we need to port every plugins to new IDA9.X API.
is this planned for this plugin ? i'm working on a patch myself but not so serious code, only relevant part for my usage.

I think you've finished patching? Are you willing to release your patch version? Patching seems to take a long time.


Configuration option to Send chat message on Enter

Is your feature request related to a problem? Please describe.
When i am chatting with short messages, I'm am used to use [Enter] to send the message, however with twinny i'm forced to return to the mouse to send my message or use the for me unnatural key combo of [Ctrl]+[Enter]
Describe the solution you'd like
I would like the chat to send my message when i press enter, and except [schift]+[Enter] to be used for a newline,
Could this be a configuration option? Or am i missing an already existing way to change this?
Describe alternatives you've considered
Writing this i wonder if there is an option to change this behavior.
Additional context
I am aware that [Ctrl]+[Enter] send the message, it works but is different from what i am used to.

This is something I've been meaning to implement. Thanks for the suggestion.


Support ellipsoid geometry

There's an ellipsoid geometry type on Ignition math now:
https://github.com/ignitionrobotics/ign-math/blob/ign-math6/include/ignition/math/Ellipsoid.hh
Also on SDFormat:
https://github.com/osrf/sdformat/blob/master/include/sdf/Ellipsoid.hh
It would be nice to add support for that in Ignition Physics, together with the other currently supported geometry types, like sphere, cylinder, etc.

similar to #196, regarding support for capsule geometry

similar to #196, regarding support for capsule geometry


Fix nodes getting desynced after a while

All our alphanet nodes besides the Coo node became desynced. They're all stuck at different LSMIs.
2020-10-29T10:22:07Z	INFO	Tangle	Valid milestone detected! Index: 1071, MilestoneID: 40123946bc16c7df104d14e587d97fca20f84d9eae24308a95992e40e4c5da0a
2020-10-29T10:22:07Z	INFO	Tangle	Run solidity check for Milestone (1071)...
2020-10-29T10:22:07Z	WARN	Tangle	Stopped solidifier due to missing msg -> Requested missing msgs (0/1), collect: 0s
2020-10-29T10:22:07Z	INFO	Tangle	Milestone couldn't be solidified! 1071

This was fixed via #705


Add doc on API stability

Here is a doc which does two things:

it clarifies what external users can depend on
it clarifies "experimental" vs "beta" vs "stable"

cc @BramGruneir @mjibson @bobvawter @jordanlewis for checking this is aligned with our actual practices so far and aspirations for the future.
cc @rmloveland for further editing and integration in the docs.
cc @bdarnell to sign off on the stability commitments.
cc @rolandcrosby @awoods187 to acknowledge the compatibility and visibility commitments.

This change is

I broke this PR... I have to re-create it. will do

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c0d5022a0ca3e018d87f3869a660f5eb5ab5e0be/


not validating on submit

EDIT: ok, it seems like once I put the actions code into the controller for my route it worked fine.
I'm new to ember, so forgive me for a noob question, but isn't ember 2.0 onwards depreciating the use of controller? So would it be better to do this right in the route? and if so, how would I implement it?
Hi guys, really like this addon, but I'm running into some trouble validating on submit.
I'm trying to get the:
               {{#if showAlert}}

                        Please fix all the errors below before continuing.

                {{/if}}

and also any alert messages for a input field to show up, when there is nothing entered or there is a missing field on submit.
but for some reason I there just doesn't seem to be a response when I click submit, I was trying this with all fields left empty so it will tell me to fill out all required info, but nothing! here is how i call submit action in template.
   {{action 'submit' model}}

code in the route:
  `actions: {
	submit: function(model) {
      model.validate().then(({
        model,
        validations
      }) => {
        if (validations.get('isValid')) {
          this.setProperties({
            showAlert: false,
          });
        } else {
          this.set('showAlert', true);
        }
        this.set('didValidate', true);
      }, (errors) => {

      });
	},
},`

and here is my model,
import DS from 'ember-data';
import Ember from 'ember';
import {
  validator, buildValidations
} from 'ember-cp-validations';

const { computed } = Ember;
const { attr } = DS;

const Validations = buildValidations({
  fullName: {
    validators: [
      validator('presence', true)
    ]},
  email: {
    validators: [
      validator('presence', true),
      validator('format', { type: 'email' })
    ]
  },
  tel: {
    validators: [
      validator('presence', true),
      validator('format', { type: 'tel' })
    ]
  },
  emailConfirmation: {
    validators: [
      validator('confirmation', {
        on: 'email',
        message: 'Email addresses do not match',
        debounce: 500}),
    ]
  },
  city: validator('presence', true),
  state: validator('presence', true),
  zipCode: validator('presence', true),
});

export default DS.Model.extend(Validations, {
  fullName: DS.attr('string'),
  email: DS.attr('string'),
  tel: DS.attr('string'),
  comment: DS.attr('string'),
  city: DS.attr('string'),
  state: DS.attr('string'),
  zipCode: DS.attr('number'),
});

I'm at lose as to what I'm not doing right. Any help will be appreciated.

Did you figure it out? If so, can you post the solution in case others find this?

@blimmer well in my Edit at the top I ended up just creating a controller for my route and put the action code in there and everything worked fine. also worked fine when using it in a component. But from what I gather about ember going forward they plan to remove controllers from blueprint, so was asking if there are plans to move the implementation into the route directly instead of using the controller. I new to ember, so I'm not very well versed in quite a lot of the thing to understand how to change the code so it works directly inside the route.
btw, it seems it's the model.validate part of the code that doesn't seem to hook when in the route, if there is a way to fix that, then it should work fine directly in route.

To get around using a Controller, I would consider making your form logic into a Component. I usually follow the pattern of having my route render just one component so I'm not introducing Controllers and will be ready if routable components ever happen.
You might also look at ember-route-actions.


Creating duplicate pointing relation between token and structure throws IllegalArgumentException

Describe the bug
May be a corner case? When you create a pointing relation between a token and a structure and annotate it with namespace:name:value (e #structure12 -> #sTok9 ns:n:a), then try to create a new pointing relation between the same nodes, annotating it with a new value within the same namespace:name combination (e #structure12 -> #sTok9 ns:n:x),

the console freezes (doesn't display a new prompt), and
an IllegalArgumentException is thrown.

To reproduce the bug
Steps to reproduce the behavior:

Open a document in the example corpus
Do e #structure12 -> #sTok9 ns:n:a
Do e #structure12 -> #sTok9 ns:n:x

Expected behavior

The console doesn't freeze
The pointing relation is created with the new annotation (unless Salt forbids having more than one pointing relation between model elements
No error message is popped up, or the error message contains helpful hints (e.g., "You cannot create more than one pointing relation between the same model elements")

Screenshots

Desktop (please complete the following information):

Operating System: Ubuntu 18.04
Hexatomic Version: #150
Java Version: OpenJDK 8

Tested without namespace, doesn't make a difference of course.


Dashboard completly Translateable

The Dashboard is completly Translatable now.
Please fix some of the missing Chines Strings =)

Thanks.


Numbers are ignored in the search

In a store with Advanced Search, the products are always given the same ranking score regardless of the number after the product name.
For example:
The following products exist:
Main article 1
Main article 2
Main article 3
You now search for main article 2.
Result:
All three products receive the same ranking score and the number after the product name is ignored.
Expected result:
Main article 2 receives the highest ranking score, as this article was explicitly searched for.

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39706
[created from NEXT-39706, comment 514229]


The clock disappears when music is playing

When listening to music, in this case Spotify, ClockBar gets replaced by the music icon

If i kill Spotify the clock reappears

I'm on a 13" M2 MacBook Pro

Since i'm almost always playing some music when working the clock is never shown


Add a script to auto-download SPANet Checkpoint

The default context adapter is SPANet, and by default it looks for this checkpoint. However, it expects a certain repository structure, plus this checkpoint has to be downloaded.
We should add a convenience script that auto-configures the repository structure and downloads this checkpoint.

I resolved the AcquireFood issue by doing a couple of things:

Manually add food_spanet_all_rgb_wall_ckpt_best.pth to the expected directory
Map the weights to cpu as follows: ckpt = torch.load(ckpt_file, map_location=torch.device('cpu')). Since I'm fairly sure I used something like pip install cv2 or equivalent, CUDA is not enabled by default. I'm guessing this was done on lovelace, so we should probably add explicit instructions to set that up on other production machines.
Install Pillow version 9.5.0: pip install Pillow==9.5.0. In later versions, you will get AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS', so we should probably add this to requirements.txt


[typo] Fix minor typos in spec file

Fix minor typos in spec file

Signed-off-by: Yongjoo Ahn<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #625. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.


prepare release 0.9.3

Warnings

:warning:
The library files were changed, but the tests remained unmodified.
Consider updating or adding to the tests to match the library changes.

  Generated by :no_entry_sign: Danger Swift against c820533ad2bebed142e046e76fcaebce808d3a5a


Support GPIO on Raspberry Pi 5

It appears that GPIO has changed with the Raspberry Pi 5.  It would be great if you could update this module to support the RPI 5.

As a workaround, you can edit the pin to gpio number table (both the v1 and v2) to change the GPIO numbers. In most cases, the correct thing to do is to add 512.
But this module needs to be rewritten or hacked to rest on top of libgpiod for great justice.

See issue 122.


Sorting by indirect attributes doesn't work

Describe the bug
Sort order is lost in DISP for indirect attributes
Details of the bug
p = GET process
    FROM file:///home/pcoccoli/github/kestrel-lang/test-data/doctored-1k.json
    WHERE name in ('conhost.exe', 'services.exe', 'taskhost.exe')
DISP p ATTR binary_ref.name SORT BY binary_ref.name DESC
sp = SORT p BY binary_ref.name DESC
DISP sp ATTR binary_ref.name

The two DISP outputs do not match - the first is sorted correctly; the second is not.
To Reproduce
Run the statements above
Expected behavior
The two DISP outputs should be the same - sorted descending.
Screenshots
binary_ref.name
   taskhost.exe
   services.exe
    conhost.exe

binary_ref.name
   services.exe
    conhost.exe
   taskhost.exe

[SUMMARY] block executed in 1 seconds
VARIABLE    TYPE  #(ENTITIES)  #(RECORDS)  directory*  file*  process*  user-account*
       p process            9           9           8     16        23              8
      sp process            9           9           0      0         0              0
*Number of related records cached.

There are at least 2 places where we have an issue:

firepit's lookup function (used by kestrel in Session.get_variable() via variable.get_entities().  This probably has to be fixed in firepit itself.
DISP itself, more specifically the _build_query() private function it uses loses the sort order.


Fade out image

On the example:

To make it more "Android" like, is there any way to make this fade out into the colour of the header rather than instantly change to the base color?

Hi @Ehesp, this is possible. I need to take a look at the animation opacity animation.

If it's any help, we do it here:
https://github.com/react-native-material-design/react-native-material-design/blob/master/lib/IconToggle.js
So could update the "opacityValue" on scroll percentage, and just ensure the background colour behind the image is the same as the toolbar?

Sorry for the delay, been a busy month so far! I dug into the issue and found that removeClippedSubviews is working, but I forgot to add overflow: hidden in my ListView example. I've update the example now.
Here's the test I used. The number of views stays constants at around 55 while scrolling down.

Going to close this for now, feel free to re-open again if anything else comes up.

Oops, closed the wrong issue. Reopening.

@Ehesp I just realized the the demo is probably out of date. Here's the current version:
https://github.com/jaysoo/react-native-parallax-scroll-view/blob/master/demo.android.20160117.gif
The opacity is interpolated based on the scroll position.
Let me know if you think the values need to be tweaked, or requires customizable.
https://github.com/jaysoo/react-native-parallax-scroll-view/blob/master/src/index.js#L251-L254

Closing this issue. Feel free to reopen if anything else comes up.


Allow empty first line after code block with ruff format

I've seen some discussion on here about allowing/not allowing an empty first line after a new code block with ruff format. This was updated to be allowed by black 24+. It also seems that black's removing of the empty new line was only a feature in black 23; previous versions of black did not enforce this.
Is there any willingness to allow these empty newlines in ruff? Or perhaps an optional flag to allow them? I agree with others' opinions that ruff should not format existing code with no new line, but should allow empty new lines.
Thoughts?

See https://github.com/astral-sh/ruff/issues/9745

Appreciate the link


Status module

"Status" module (name from readme), feel free to rename it or what have you.
The god mode might not be complete, I have only tested mob damage (zombies, skeletons, creeps), TNT, lava and fire.

Sorry, should have put the spawn module in a separate branch.

git checkout status
git reset --hard af8bb46c
git cherry-pick d4948ab
git cherry-pick 282392e
git cherry-pick fb90ebf
git cherry-pick 87cc769

or
git rebase -i HEAD~8

and remove the unneeded commits

I'm not sure how 'clean' this is. The getTarget method could be moved into a util, but it felt repetitive to have to figure out the target in all 3 commands with the same code.

I've added the necessary parameter providers to ForgeModule so you can now do this:
@Command(aliases = "bring", desc = "Brings a player to you")
@Require("plume.teleport.bring")
public void bring(@Sender EntityPlayerMP player, Set<EntityPlayerMP> targets) {
    for (EntityPlayerMP target : targets) {
        TeleportHelper.teleport(target, player);
        target.addChatMessage(Messages.info(tr("teleport.teleportedBy", player.getGameProfile().getName())));
    }
    player.addChatMessage(Messages.info(tr("teleport.success")));
}

https://github.com/SKCraft/Plume/blob/master/src/main/java/com/skcraft/plume/module/Teleports.java#L25

Oh nice, I wondered if there was something like @Switch.