Experiment with speech/text interleaving

Apply ASR (e.g., Whisper) to an existing speech dataset to establish word-level timings, and add said timings as an additional column for the dataset. With this new column, add an option to data/datasets.py to generate samples with interleaved text and speech (e.g., instead of "Transcribe <|audio|>", the input for the utterance "Rice is often served in round bowls" would be of the form "<|audio|> is often <|audio|> in round <|audio|>").

@juberti This is very interesting, I have been trying to establish word-level timings using openai/whisper-small model to generate samples with interleaved text and speech.
So, I am trying to get word-level timing first using whisper-small model, and after add one more column for that. Successfully working to get word-level timing dataset.
But curious what algorithm works to get the interleaved text. I am thinking that I would like to calc some attention weights of each word in the sentence, and get random words with high attention scores and change those into <|audio|> special tokens.
What do you think ?

The goal here would just be to allow the model to see interleaved text during stage 1 training, which should help it learn text-audio invariance. So once we have the new column you mention, during training we could run for multiple epochs, and for each sample, randomly choose for each word in that sample whether to use the text or audio representation.

Yeah, make sense, so we can randomly select world to tokenize with special token.


Create RFC around open source and working in the open.

There are several internal documents around open source and working in the open. They should be combined/consolidated and included into the RFC repo (either as RFCs or discussion topics depending on their purpose). The documents should be then be deprecated and point to the RFC repo.
This is related to #14 as working in the open is one of the plays.

https://docs.google.com/document/d/1TgyhNVxiLnB44YQaw9sGxPg5OfdYQ5HZEOK-Y2_x7GA/edit#heading=h.adft07cswi7w
https://docs.google.com/document/d/1Q1d1zAYxWCADfDXkrNWTGRKsYQQS6IBux68LuXejFhs/edit
https://docs.google.com/document/d/1a2Namrvb9qXNvC6CCap59_PMDIoE_q5V3LeoQvn-qV0/edit#heading=h.9nprw4fvy92t
https://docs.google.com/document/d/1q1jyzs0A-6v49ghMPAMS4ax8tb-9Uu1Xz-J7TGJ5ONU/edit#

Marking this as complete as I think it's done.


Feat/advisory CVE 2024 6387

A security note on the openssh desaster.

We should publish this tomorrow -- or maybe discard, if we think it's not worthwhile.

We need to decide whether or not we publish this. @fkr ? @ bitkeks? @scoopex ?
This would be an extra service (given the scope of exploits), not an acknowledgement that we are responsible to create such security notes.
If we push it out, we should do it today (or maybe tomorrow), otherwise, it's probably better to not publish it.

I think, this should not be an advisory. If we want to raise awareness to the issue, it should be a blogpost.
Why not an advisory: Because with the advisories, we should focus on the core stuff that relates to our deliverables. If we start issueing advisories for other stuff, we will have no clear "where to start and where to stop". Aside from that I think, it is also a matter of focus. We should focus on our core deliverables - there is enough heavy lifting to be done there.

Ok, we won't do this.


WSSRV004 in Development

This function checks the pagefile min and max sizes

rewriting with CIM instead of WMI.

Reset is complete.  It is dependent on the new WMI branch in Development.


DeiT (small) on ADNI Dataset | s4744343

This pull request introduces the foundational codebase for classifying Alzheimer's disease using the ADNI dataset and the Data-efficient Image Transformer (DeiT) model. The accuracy on test data of this model has been developed to be over 80%.
Key Files

train.py: The training script that includes model setup, data loading, and training loop. Implements gradient accumulation, learning rate scheduling, early stopping, and automatic mixed precision for efficient training.
predict.py: Script for making predictions on individual MRI scans, outputting a classification (NC or AD) with confidence scores. This file also supports batch predictions over test data for bulk inference.
modules.py: Contains the DeiT model implementation along with essential helper classes, including multi-layer perceptron (MLP), global filter layers, and the forward pass structure. This modular setup supports easy customisation and potential integration of additional transformer layers.
dataset.py: Defines the ADNIDataset class responsible for loading and preprocessing the ADNI dataset, along with data transformations specific to training and testing. Ensures MRI data is correctly structured for input into the DeiT model.
images/: Folder containing sample images of the MRI scans, processed input data, and visualisations of model performance, such as confusion matrices and loss curves.
README.md: Comprehensive documentation detailing the project objectives, dataset structure, preprocessing methods, model architecture choices, experimental comparisons with other transformer models, and a step-by-step guide for running the code. Includes insights into the efficacy of different transformers in achieving robust Alzheimer's classification.

Model Architecture:

DeiT Small model setup using pretrained weights from ImageNet.
Configured for binary classification to distinguish between Normal Control (NC) and Alzheimer's Disease (AD) MRI scans.

@gayanku

This is an initial inspection, no action is required at this point
Uses a pretrained imageNet model for ADNI classification.

Observational Feedback
File Organizing: Well-organized files.
Pull Request :
Correctly generated to Topic Recognition Branch .
The Description talks about the File Structure Clearly , Add about achieved Results .
Problem Solving:
The algorithm solves the problem appropriately   .
Accuracy in testing dataset:0.8142
Model and functions:
It correctly uses PyTorch to construct the functions.
Code design: Good.
Code comment and docstring:
Sufficient Code Commenting .
Missing function docstrings
Difficulty: Hard.
Additional Comments:
Meaningful commits.
Good ReadMe design. However, It would be better if a conclusion and future improvements  appeared in the report.

Alzheimer's Classification with ViT, using DeiT small
This pull request introduces the foundational codebase and report for classifying Alzheimer's disease using the ADNI dataset and the Data-efficient Image Transformer (DeiT) model, with a target accuracy of above 80% on the test set in Project 5 for COMP3710 A3:
Classify Alzheimer’s disease (normal and AD) of the ADNI brain data using one of the latest
vision transformers such as the GFNet set having a minimum accuracy of 0.8 on the test set.
[Hard Difficulty]

Key Achieved Results

Test Accuracy: Achieved 81.42% accuracy on the test set, surpassing the target for effective differentiation between Normal Control (NC) and Alzheimer's Disease (AD) cases.
Performance Metrics: Confusion matrices and loss curves are included to illustrate the model’s performance, showing clear differentiation between NC and AD cases.
Expanded Analysis and Evaluation: Added in-depth sections on analysis, evaluation, model limitations, and potential extensions for comprehensive insights into the model’s performance and areas for improvement.

Key Files

train.py: The training script, including model setup, data loading, and the training loop. Implements gradient accumulation, learning rate scheduling, early stopping, and automatic mixed precision.
predict.py: A script for predicting classifications (NC or AD) with confidence scores for individual or batch MRI scans.
modules.py: Contains the DeiT model implementation and helper classes, supporting customisation and integration of additional layers.
dataset.py: Defines the ADNIDataset class for loading and preprocessing the ADNI dataset, ensuring compatibility with the DeiT model.
images/: Contains sample MRI images and performance visualisations, such as confusion matrices and loss curves.
README.md: Comprehensive documentation, including project objectives, dataset structure, preprocessing, model architecture, and a step-by-step guide for running the code. Expanded to include analysis of the model's performance and possible improvements.

Additional Improvements Based on Feedback

Detailed Analysis and Evaluation Sections: Added sections on in-depth analysis, evaluation of results, limitations, and suggested improvements/extensions for the model.
Enhanced Code Comments and Docstrings: Updated all Python files with detailed comments and docstrings for clarity and documentation of functions and classes.

Model Architecture

DeiT Small: Configured with pretrained weights from ImageNet for binary classification between NC and AD MRI scans. The modular design supports experimentation with larger DeiT models for potential accuracy gains.

Hi, the above commit replaces an earlier R&D plot with the correct early stopping plot used in the report. This ensures alignment with the discussed results and conclusions

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation.
Spacing and comments.
No Header blocks. -1
Recognition Problem
Good solution to problem.
Driver Script present.
File structure present.
Good Usage & Demo & Visualisation & Data usage.
Module present.
Commenting missing. Missing doc string.-1
No Data leakage found.
Difficulty : Hard. ViT (Hard Difficulty)
Commit Log
Good Meaningful commit messages.
Good Progressive commits.
Documentation
Readme :Good.
Model/technical explanation :Good.
Description and Comments :Good.
Markdown used and PDF submitted. PDF checked.
Pull Request
Successful Pull Request (Working Algorithm Delivered on Time in Correct Branch). On time submission.
No Feedback required.
Request Description is good.
TOTAL-2

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

Feedback marks possible +2 if the requested changes are made (see above).

Hi @gayanku,
Thank you for the feedback. I was a bit confused and had assumed that the 2 marks associated with implementing feedback would be given based on @aniketgupta17 's comments, which is why I implemented those changes. Discussions on Ed suggested that lost marks could be recovered through this, alongside the additional 2 marks.
Additionally, I have now updated the branch for the PR correctly. Sorry for the earlier oversight.
Thanks,
Masham


поправил дроп

Pull request template
Checklist

[x] I have read the CONTRIBUTING guide
[x] branch rebased on develop
[x] styleguide check npm run validate
[x] good naming
[x] keep simple
[x] video or screenshot attached
[x] testing instruction attached
[x] check your PR once again

Description

Video or screenshot
###was

###become

What and how to test

Какие здесь правки?


Push with PAT

I copied the wrong wrong PAT from my account settings into the repo settings. This branch is not necessary


team merkle race

@maxtaco lmk when this is ok to merge (wasn't sure if you wanted to investigate the merkle freshness issue)


ROS recipes for velodyne

Th velodyne recipe can't download the source file. It is not in that archive
ERROR: velodyne-msgs-1.3.0-r0 do_fetch: Fetcher failure for URL: 'https://github.com/ros-drivers/velodyne/archive/velodyne-1.3.0.tar.gz;downloadfilename=velodyne-1.3.0.tar.gz'. Unable to fetch URL from any source

Hello,
This happen to me too:
ERROR: velodyne-driver-1.3.0-r0 do_fetch: Fetcher failure for URL: 'https://github.com/ros-drivers/velodyne/archive/velodyne-1.3.0.tar.gz;downloadfilename=velodyne-1.3.0.tar.gz'. Unable to fetch URL from any source.
ERROR: velodyne-driver-1.3.0-r0 do_fetch: Function failed: base_do_fetch

See https://github.com/ros/meta-ros/pull/625 which should fix this.

@monicuti < Can this issue be closed?

Hello, yes, that fix the issue.
Thanks!
From: Herb Kuta<EMAIL_ADDRESS>Sent: viernes, 7 de febrero de 2020 17:17
To: ros/meta-ros<EMAIL_ADDRESS>Cc: Monica Ruiz Macias<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ros/meta-ros] ROS recipes for velodyne (#628)
@monicutihttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_monicuti&d=DwMCaQ&c=CIoxZ4z5BqFvKvSGFOTo726QZIiNTc_M9CmngT-Pla4&r=hDuTobJAlzyUNy827vtQWA&m=8oadidf-5SWptot70qr53Ej6rAfTP3qdtS6PW7FIHGc&s=nKR6wnDSi7CdtuWtjDET2tKjZxw25kBsIEPMsfYX2m0&e= < Can this issue be closed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ros_meta-2Dros_issues_628-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAG43GW2TMOREMVGBYMDKGU3RBWCPRA5CNFSM4HLR2IZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELDSUFA-23issuecomment-2D583477780&d=DwMCaQ&c=CIoxZ4z5BqFvKvSGFOTo726QZIiNTc_M9CmngT-Pla4&r=hDuTobJAlzyUNy827vtQWA&m=8oadidf-5SWptot70qr53Ej6rAfTP3qdtS6PW7FIHGc&s=B4Ud2CUZg-RUoXrKnzuMWlnvXr8BxYZXP-yKIYHfFcg&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AG43GW2WQZLSKDXMIXTTB4LRBWCPRANCNFSM4HLR2IZA&d=DwMCaQ&c=CIoxZ4z5BqFvKvSGFOTo726QZIiNTc_M9CmngT-Pla4&r=hDuTobJAlzyUNy827vtQWA&m=8oadidf-5SWptot70qr53Ej6rAfTP3qdtS6PW7FIHGc&s=LjCKUr4binoQs5DP3WyrxiI0CIciGxoCV6Hq8PgOQBg&e=.
P Please consider the environment before printing this e-mail.


openrtm_aist: 1.1.0-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository openrtm_aist to 1.1.0-0:

upstream repository: http://svn.openrtm.org/OpenRTM-aist/tags/RELEASE_1_1_0/OpenRTM-aist/
release repository: https://github.com/tork-a/openrtm_aist-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.5.21
previous version for package: null

holding builds waiting for indigo rebuild to finish

Since a new release is a leave package and it will relatively fast I think we should allow Kinetic releases to move on since its impact on the Indigo rebuild is minimal.


make separate contexts for outgoing extensions

hooked up a HT701 to test it, had it going to the usual default-outgoing context, autodialling an extension in the device to get the menu on pickup. I was able to get a dialtone in default-outgoing by flashing rapidly. This would let me connect to any extension in default-outgoing, including the admin menu.
I don't know if the SPA2s have this problem, they use a dialplan. The HT701 autodial is probably just sending DTMF or something cheesy.
Fix:

keep demo/test extensions in default-outgoing, just treat them as slightly dangerous if used for public phones
give our known extensions the specific contexts instead of default-outgoing, dunno if we want/need to keep the interim context or what - just give them fewer choices, or one choice

I've found it's fairly hard (potentially impossible) to bypass the dialplans in the devices that support them (the D-link vonage boxes, PAP2T, etc.). I specifically set a delay before auto-dialing an extension so that I could dial whatever I want (for diagnostics/power users in the field) but if I wanted to clamp it down, I'd drop the pause and AFAIK put the clamps on the options a user could touch. The dial-plan can be so sparse that it won't even accept any DTMF/Key-Presses (until the call is connected of course)....so seems secure.

yeah, I don't know what these HT701s are doing, the dialplan didn't support S0<:999>, instead there's a separate field, which I was able to bypass as described. The other vulnerability would be someone editing the dialplan, or accessing the SIP password and using it for their own device.
I don't expect any of this will be likely in real life. The bigger risk is users getting confused by an HT701 style unexpected bypass, having its own context would help.

Would this even work for our various ATAs? Probably does if they accept a dialplan of just S0 or something. But then we couldn't change the destination without changing the SIP ID, which means the SIP IDs wouldn't be by location anymore, they'd change.


Apple Mach-O Linker (ld) Error Group [Compile error]

Hello, I'm trying to compile my project into an iPad Air 2 and I got this error:

My iPad uses iOS 11.3 and on xCode also I selected 11.3 on Deployment Target
Already deleted the DerivedData folder from Developer/xCode, also deleted the Build from myProject/iOS/Build

seems to be issue with FirebaseMessaging SDK itself.
Does it happen for enumerator or iphone?

I dont know what do you mean by enumerator, but I was trying to compile to iPhone and iPad. Didint fixed the issue so I gave up trying to make it work without cocoapod and started the tutorial again with cocoapod. Compiled with success but none notification is showed on iOS, just on android. I'm trying to find what I did wrong now... Thanks for try help me

cool


"Cetățeni" is listed in the drop-down menu

Description:
"Cetățeni" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Cetățeni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Cetățeni, Argeș (Cetățeni)".


Assert in vmod_clean

Child (23192) died signal=6 (core dumped)
Child (23192) Panic message:
Assert error in vmod_clean(), vmod_cookie.c line 233:
Condition((cookie)->magic == 0x3BB41543) not true.
thread = (cache-worker)
version = varnish-4.0.3 revision b8c4a34
ident = Linux,2.6.32-504.el6.x86_64,x86_64,-smalloc,-smalloc,-hcritbit,epoll
Backtrace:
0x431c15: /usr/sbin/varnishd() [0x431c15]
0x7ff9ccaed3ef: /usr/lib64/varnish/vmods/libvmod_cookie.so(vmod_clean+0xaf) [0x7ff9ccaed3ef]
0x7ff9ccaedf3a: /usr/lib64/varnish/vmods/libvmod_cookie.so(vmod_parse+0x4a) [0x7ff9ccaedf3a]
0x7ff9cccf2f22: ./vcl.RMFhp7Mo.so(VGC_function_vcl_recv+0x1f2) [0x7ff9cccf2f22]
0x43e172: /usr/sbin/varnishd() [0x43e172]
0x43f565: /usr/sbin/varnishd(VCL_recv_method+0x45) [0x43f565]
0x4372ca: /usr/sbin/varnishd(CNT_Request+0x5ca) [0x4372ca]
0x42c17b: /usr/sbin/varnishd(HTTP1_Session+0x56b) [0x42c17b]
0x43ab18: /usr/sbin/varnishd() [0x43ab18]
0x434695: /usr/sbin/varnishd(Pool_Work_Thread+0x365) [0x434695]
req = 0x7ff9c609b020 {
sp = 0x7ff9c441afe0, vxid =<PHONE_NUMBER>,  step = R_STP_RECV,
req_body = R_BODY_NONE,
restarts = 0, esi_level = 0,
sp = 0x7ff9c441afe0 {
fd = 14, vxid = 65537,
client = <IP_ADDRESS> 39481,
step = S_STP_WORKING,
},
worker = 0x7ff9c3249c10 {
ws = 0x7ff9c3249e30 {
id = "wrk",
{s,f,r,e} = {0x7ff9c3249400,0x7ff9c3249400,(nil),+2048},
},
VCL::method = RECV,
VCL::return = abandon,
},
ws = 0x7ff9c609b1b8 {
id = "req",
{s,f,r,e} = {0x7ff9c609d010,+1008,(nil),+57360},
},
http[req] = {
ws = 0x7ff9c609b1b8[req]
"GET",
"/WebResource.axd?d=6JkJ7du29aJvrAL3cPzeAMkmqoZHOmy1tIh6FujyhuCFn9uRT5zgjxupebDechfQuz8Uryr-BxplOgKek3jFXM_FssJH9zkWNhEXwGaz_uw1&t=635588654815688065",
"HTTP/1.1",
"Host: statistikkportalen.XXX.no",
"Connection: keep-alive",
"Cache-Control: max-age=0",
"Accept: /",
"If-Modified-Since: Fri, 06 Feb 2015 23:24:41 GMT",
"User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.81 Safari/537.36",
"Referer: https://statistikkportalen.XXX.no/Pages/default.aspx",
"Accept-Encoding: gzip, deflate, sdch",
"Accept-Language: en-US,en;q=0.8,nb;q=0.6",
"Cookie: __utma=96641627.1805302195.1410765487.1417038264.1417693820.5; WT_FPC=id=<IP_ADDRESS>-89042160.30424790:lv=1422907049355:ss=1422905138414; _ga=GA1.2.1805302195.1410765487; WSS_FullScreenMode=false",
"X-Forwarded-Proto: https",
"X-SSL-cipher: DHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=DH       Au=RSA  Enc=AESGCM(128) Mac=AEAD",
"X-Forwarded-For: <IP_ADDRESS>, <IP_ADDRESS>",
},
vcl = {
srcname = {
"input",
"Builtin",
"/opt/etc/varnish/backends.vcl",
"/opt/etc/varnish/statistikkportalen/vcl_recv.vcl",
"/opt/etc/varnish/statistikkportalen/vcl_backend_response.vcl",
},
},
},
VCL related to cookie handling (if it matters):
Parse cookies
if (req.http.Cookie) {
cookie.parse(req.http.Cookie);
if (cookie.get("STATISTIKKCOOKIE")) {
set req.http.X-Tracker = cookie.get("STATISTIKKCOOKIE");
}
}
if (! req.http.X-Tracker) {
if (req.http.X-Forwarded-For) {
set req.http.X-Tracker = req.http.X-Forwarded-For;
} else {
set req.http.X-Tracker = client.ip;
}
}
Set site backend, hash key is cookie value, this should ensure sticky session
set req.backend_hint = statistikkportalen.backend(req.http.X-Tracker);

Hi. Please try latest master (3a2a9ae).

With my so far limited testing, I have not been able to reproduce after the proposed fix.

Thanks for the feedback. I'm closing this issue now, please open a new one if the problem reappears.


Getting validation error while running examples\spdx2_document_from_scratch.py

unable to follow the validation error in examples\spdx2_document_from_scratch.py
tried document.files = [file1, file2] , still no solution

This has been fixed in #687 already, please pull the newest version :)
Nevertheless, to ensure that the examples will continue to work in the future, I opened a PR to add it as a test.


[Improvement] Improve the current SQL of JDBCBackend

What would you like to be improved?
In the current implementation of xxxMetaMapper and xxxMetaService, we seldom use JOIN and transactions, for example:

The list catalog operation will issue two SQL queries, the first one is to get a metalake id, then using this id to get the catalog list.
Instead of issuing two queries, we can use JOIN to join catalog and metalake table to get catalog list by one query, this will save the IO time and avoid inconsistent problem.
Also for updateCatalog

We have several steps:

get metalake id.
get catalog PO.
update the catalog object.
update the catalog in RDBMS.

These 4 steps are not in the transaction, which will potentially meet the inconsistent problem, and we highly leverage the lock to avoid the concurrent problem. A better solution is to put these 4 steps into a transaction.
How should we improve?
So basically, we can improve the current SQL to:

reduce the queries and increase the performance.
Put multiple step actions into one transaction to leverage DB's transaction to keep consistent.

CC @xloya @yuqi1129 , please take a look when you have time.

It's a big work to change everything, we can separate it into small tasks to iterate one by one. Currently, there's no functionality issue here since we have locks to guarantee the concurrency.

I think there is no problem with using JOIN to reduce the number of queries.
As for whether to put all operations in the same transaction, I may have some doubts, because this may cause a database transaction to be too large and cause deadlock and other problems.
I think we can consider whether it is enough to ensure transactionality with upper-level locks (later, while supporting horizontal expansion of the server, ensuring transactionality), or whether a large database transaction is really needed.

I have no clear answer for now. I think we can do some tests to see if transaction is OK or not. But for join I think we can do some changes somehow. For example, like delete operation, we can use join to do it and check the return value, you can check my code #4019 , I use join to handle some cases. @xloya


Files in config are not copied to installer

Files that I place in the config tree (before starting build.sh) do not end up on the image for the installer.
I think that is because here: https://github.com/FooDeas/raspberrypi-ua-netinst/blob/master/build.sh#L626 you cd into the build_dir and then this:
https://github.com/FooDeas/raspberrypi-ua-netinst/blob/master/build.sh#L671-L673 won't find anything to copy anymore.
What do you think?

 Thanks!


:fire: Remove explicit tokens

Type of Change

[ ] Bugfix
[ ] Enhancement / new feature
[x] Refactoring
[ ] Documentation

Description

remove explicit tokens
usage of one of the docker build secrets properties is recommended

Checklist

[x] Add relevant labels (for example type of change or patch/minor/major)
[x] Make sure not to introduce some mistakes
[x] Update documentation
[x] Review the Contributing Guideline and sign CLA
[x] Reference relevant issue(s) and close them after merging

@timdittler Yeah sure, but I would add this information directly to the release. I would write something like that:
Breaking Changes:
If you are using one of these variables ..., you need to adapt your workflow and move these variables to the parameter.

Is this okay? 🤔

I'm missing a piece of advice on how to migrate from explicit tokens to docker build secrets. Would be great if not every team would have to figure this out by themselves.

here is an example: https://github.com/Staffbase/play-store-connect-service/pull/92/files


Fix double divider on profile page

Introduced by https://github.com/go-gitea/gitea/pull/11437
The divider line is now in Vue component and follows general guideline of having divider below element
Closes https://github.com/go-gitea/gitea/pull/11508

https://github.com/go-gitea/gitea/pull/11508 handles this?


iterator for InstagramGetUserFollowersRequest & InstagramGetUserFollowingRequest & clean code

f3f4fd1 add iterator for InstagramGetUserFollowersRequest & InstagramGetUserFollowingRequest
Added iterator for GetUserRequests same as iterator in ArrayList. Because the request returns only up to two hundred users at a time, it is necessary to manually iterate through followers/followings every time and this leads to a violation of the DRY principle.
d171d7b and to the add-on I cleaned some code :)
Hope y'all reviewers will approve it

This actually seems like the "right way" of using the API 😅
I will test this at some point in the near future

Addressed in rewrite or no longer relevant.


Fingerprint not updated

Had issues with the previous fingerprint and had to update (/src/FirebaseHttpClient.h) it to : CF:6C:F8:33:A3:FB:42:4A:49:0A:E7:72:24:53:1A:11:A2:C1:34:0D.
To generate the latest fingerprint use : https://www.grc.com/fingerprints.htm (Enter your database url).

Still the Serial monitor shows the same error:
if (Firebase.failed())
{
Serial.print("pushing /logs failed:");
Serial.println(Firebase.error());
return;
It Shows "pushing /logs failed"

why do you think that the fingerprint causes the problem?
Anyways, it is possible that the fingerprint has changed since my comment. Yo can get the new one at https://www.grc.com/fingerprints.htm (Enter your database url).


data normalization - possible bug

I noticed that the data normalization is
transforms.Normalize((0.5, 0.5, 0.5),(0.5, 0.5, 0.5))

(for example in twoafc_dataset.py).
The imagenet normalization coefficients are
mean=[0.485, 0.456, 0.406],
std=[0.229, 0.224, 0.225]
This raises the questions:

possibly you confused mean with variance? (the Normalize function accepts std as the second argument, not variance)
any reason behind the design choice not to use the imagenet normalization?

This "normalize" converts images from [0,1] to [-1,+1]. We do the actual imagenet normalization here: https://github.com/richzhang/PerceptualSimilarity/blob/master/models/networks_basic.py#L112

Hi
I don't understand where did you get the normalization values.
Currently your using mean = [ -.030,-.088,-.188] and std = [.458,.448,.450] which doesn't correspond to ImageNet statistics.
self.register_buffer('shift', torch.Tensor([-.030,-.088,-.188])[None,:,None,None])
self.register_buffer('scale', torch.Tensor([.458,.448,.450])[None,:,None,None])

Thanks for the question. The imagenet statistics assume images are normalized between [0,1]. This code uses images from [-1,+1], so the appropriate transformation is done (notice that the std is just doubled)

Thank you for the fast answer =)


Filter Tags-EPA report 508 Issue

Required Fix

Page/ Screen
Description Of Issue
Test(s)
508 Standard(s)
WCAG 2.0 Standard(s)

Custom Data   Downloads
The filter   elements include controls to both modify a filter or remove it.  The button(s) to modify a filter should   include tagging to indicate that this is the purpose of the button.           See Figure 3
6A
1194.21(d),   1194.31(a), 1194.31(b)
2.4.4, 4.1.2

Context
Refer to EASEY July 2021 Test Report

Figure 3: Buttons to refine filters should describe the purpose of the button

Passes testing, all available filters now have the word Modify before it


Provide a tensorflow maven package for AWS Lambda or lighter builds in general

The current build size of tensorflow 1.14.0 makes it impossible to use the library on AWS Lambda without further steps to reduce the depedency size.
It would be great to have for example a tensorflow dependency for AWS Lambda specifically.
What would also work, would be a separate module for tensorflow without all native libraries and a module per native implementation. This way the overhead of the darwin and windows native code is gone and reduces the dependency significantly (~200MB).

This request is not valid with latest versions , so closing this issue.


pip install

Bug Report
Current Behavior
pip install libs differs from source even tho it has same version (1.6.3)
Environment

Python Version: 3.8.2
Hcloud-Python Version: 1.6.3 (installed from pip)

Additional context/Screenshots
https://i.imgur.com/FFHLVKZ.png
Image of servers/client.py from pip install hcloud
Notice that its missing the networks which will cause a TypeError
TypeError: create() got an unexpected keyword argument 'networks'

The version which contains the networks flag is not yet released, you can see this within the changelog: https://github.com/hetznercloud/hcloud-python/blob/master/CHANGELOG.rst


ui: remove QtQml and related dependencies

This PR refactors the TermsPage to use standard Qt Widgets instead of QtQml components.
This change removes QtQml and its related modules (QtQuick, QuickWidgets, Qml, QtQmlModels, ...), which are quite large. The primary goals are to reduce project dependencies, improve build performance, and simplify the dependency graph. additionally, since QtQml components are more resource-intensive, this change will also save some UI resources.
The UI appearance remains consistent with previous designs, with the only difference being that the scrollbar is hidden, leading to slight changes in padding.
Also the UI may eventually move to another framework, but since that could take a while, I think it's still worth removing QtQml now.
After:

Before:

How’s the scrolling on device? I think this is why we did it originally.

It behaves consistently with other UI components using ScrollView, which do not display scrollbars by default on the device.

It’s possible that the TermsPage was one of the earliest widgets implemented, and the ScrollView component at that time had many bugs.

FYI @deanlee, we plan on removing terms + training from device and just putting them on a webpage. So no need to rewrite these.

got it


Differentiate Between Breaking, Placing, Eating

Being able to differentiate between whether I'm trying to eat a carrot or place a carrot would be very nice.  Adding a use case within the quotations that would allow for this would likely be the easiest way in my mind. For example, "minecraft:carrot minecraft:farmland farming:5" would make it so ONLY placing the carrot on a tiled tile is disabled and not eating or general right clicking with the carrot.

I agree that would be a good feature, but I don't know how I'd go about implementing that. The way you suggested would be really complicated, so I'll try to come up with a better way to approach it. Until then, I don't know whether I want to spend a lot of time on this feature. Anyone is welcome to submit a pull request however!


[SPARK-34031][SQL] Union operator missing rowCount when CBO enabled

What changes were proposed in this pull request?

Improve Statistics.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test.

Test build #133746 has started for PR 31068 at commit c0dbbe4.

Test build #133746 has started for PR 31068 at commit c0dbbe4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38334/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38334/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38334/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38334/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38334/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38334/

Test build #133746 has finished for PR 31068 at commit c0dbbe4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #133746 has finished for PR 31068 at commit c0dbbe4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Seems needing to update query plan files.

Seems needing to update query plan files.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133746/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133746/

Looks fine except for the @viirya comment.

Looks fine except for the @viirya comment.

Test build #133770 has started for PR 31068 at commit 3c5af90.

Test build #133770 has started for PR 31068 at commit 3c5af90.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38358/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38358/

@wangyum, sorry but can you push an empty commit to retrigger the GA build? I would like to keep the result of the test failure because it looks like a flaky test.

@wangyum, sorry but can you push an empty commit to retrigger the GA build? I would like to keep the result of the test failure because it looks like a flaky test.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38358/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38358/

The flaky tests are known and being fixed at https://github.com/apache/spark/pull/31076. Let me just merge this in

The flaky tests are known and being fixed at https://github.com/apache/spark/pull/31076. Let me just merge this in

The flaky tests are known and being fixed at https://github.com/apache/spark/pull/31076. Let me just merge this in

The flaky tests are known and being fixed at https://github.com/apache/spark/pull/31076. Let me just merge this in

Merged to master.

Merged to master.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38358/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38358/

Test build #133770 has finished for PR 31068 at commit 3c5af90.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #133770 has finished for PR 31068 at commit 3c5af90.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133770/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133770/


feat(clerk-js): Improve password error feedback

Description

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

@desiprisg can you please add a description and a couple of screenshots if needed?

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Listing Swapzone.io on "Swappers" section

Hello team!
I'm Maria, a marketing manager at Swapzone - an instant crypto exchange aggregator. We help users to compare exchange rates, analyze and swap cryptocurrency in just one interface.
XMR is one the most popular asset on our platform and we also have a separate page of your coin so new users can learn about your project: https://swapzone.io/currencies/monero
I'd love to know whether it's possible for you to add our project in your "Swappers" section (https://www.getmonero.org/community/merchants/). It would be a huge deal for us.
Let me know your opinion about it!
Best regards, Maria

Hello @erciccione! I've seen you added a label to my request 3 days ago. Do you have any updates regarding the Swapzone placement on the "Swappers" section?

Hi again @erciccione! Did you get a chance to check Swapzone? We look forward for the decision.

Hi @MariaSwapzone I don't investigate swappers/merchants for inclusion on getmonero. If somebody else is interested in doing that, they will review this issue.

Thank you for the reply @erciccione! If you're not the right person to discuss it, could you please let me know who's the appropriate person to reach out directly?

@MariaSwapzone you might have more luck asking on the Matrix/IRC room: #monero-site

@erciccione could you please share a link?

Hi @erciccione! Could you please share a link where I could ask about this integration?

Since you are insisting so much to get your business listed, i would expect you to at least take a couple of minutes to actually visit the website and find the info you are looking for: https://www.getmonero.org/community/hangouts/

Hi! We took that listing opportunity very serious and, off course, I explored  the website very carefully. It seems that the link  (the Matrix/IRC room: #monero-site) is unavailable. I tried to click on the link several times, but nothing happened. This is why I asked for your assistance.

Open a IRC client, join #monero-site or open a matrix client and look for Monero website.

Thank you so much for your help! I'll try to do that.

Swapzone is more likely aggregator instead of an exchange or swapper. Creating another section for it would be better.


Dementors

Hey Nathan!
I have configured magic for harry potter, But i was wondering how I would make a dementor?
Any Ideas?

Hm I thought I had one in the configs but I guess not.
You could make a magic mob wither that casts spells... I'll add one when I get a chance.

OK thanks, Magic mob is one of your plugins?

How do I make it so it can cast spells?

Check on the warlock in the default configs

There is now a basic dementor mob in the potter configs.


Add indented fences

In rare cases, Markdown contains a code block with a leading space in it.
  ```
aaa
  aaa
aaa
  ```

This is a proper code block, as defined by the following URL:
https://spec.commonmark.org/0.29/#example-101
If you merge this pull request, you can create ctags to the code block even if it contains indentation.

thanks


Success rate in summary to reflect features pass/fails

Hi there,
I'm liking this plugin, however one gripe I have is in the top summary section is the way the stats are presented.  For example, if I run one Spec file that has 10 features in it, and 9 pass and 1 fails, that is a 90% pass rate.  This is reflected correctly in the Specifications portion on bottom.  However in the top Summary section, total is 1, 0 passed, 1 failed, 0% success rate and the pie chart shows 0%.
Is there a reason you chose this all or nothing approach for the summary?  I think it would be much more beneficial if it was summarized by features, so that it would show total is 10, 9 passed, 1 failed, 90% success rate.  I ran one file that was 90% successful but the summary shows 0% successful and that seems misleading.

I just wanted to drop by to say I am still interested in this enhancement :)

Hey @jacattau, do you have an idea on how this could be shown in the UI, without adding too much clutter?
Proposal 1: Adding another column Feature success rate to the summary table. This shouldn't be too difficult, but then it is unclear what the pie chart on the right refers to. Adding a second chart wouldn't really fit well here.

Proposal 2: Have two separate summary tables, and two pie charts. One for the specs, and another one for the features. The chart is not shown in the image below, but just imagine a second one below. Dummy example:

What do you think?

I believe option 2 is closest to what I am picturing.  I believe the pie chart is showing the rate of the summary where I would rather have it show the rate of the specifications.
So using an example here.  If I have 5 features each with 10 tests inside of them and I run all the tests and 1 test fails that means 49/50 (98%) passed.  At the feature level that would say 4/5 passed (80%).  What I would like to see is the 98% represented.

Yeah I agree that the 98% success rate is more representative and relevant than the 80% success rate. Just to clarify: I think you have mixed up specifications and features in your description. A single specification is a class which contains many features.
I am starting to wonder if those pie charts are really necessary, but I don't want to get rid of the visual representation entirely. Maybe a very simple stacked bar chart which can show both specification and feature success rate could be a compromise.

You are right, I definitely had those mixed up.   Our client requirement is to show fixture success rate on the report dashboard. Thank you in advance.

Hi @ShubhenduPandey, I would still prefer if those statistics would be added in spock-reports directly, see the issue which is linked above your comment. I don't want to deviate too much from spock-reports, as this might increase the chance of breaking changes in the future which are harder to maintain.
In the meantime, if it is urgent for you, I would also accept pull requests to add this to geb-spock-reports until it is available in spock-reports.

Geb-spock-report doesn't work for me. Getting error below error
[(Could not resolve all dependencies for configuration ':testCompile'.

Could not find com.aoe:geb-spock-reports:0.2.6.
Searched in the following locations:
https://repo1.maven.org/maven2/com/aoe/geb-spock-reports/0.2.6/geb-spock-reports-0.2.6.pom
https://repo1.maven.org/maven2/com/aoe/geb-spock-reports/0.2.6/geb-spock-reports-0.2.6.jar
)]
I am currently using spock report.

@ShubhenduPandey geb-spock-reports is published on jcenter, you need to add it as a repository in your build.gradle:
repositories {
    jcenter()
}

Thanks @tilmanginzel Can you please merge pull requests to add this to geb-spock-reports.

Currently there are no pull request available to merge. Maybe there was a misunderstanding. I will accept a pull request if someone is willing to work on this, but I don't have the time to do it myself.

I misunderstood it. Just wanted to know how you have calculated the total feature count in the first place? I didn't see a method that calculated total features in Utils.stats and Utils.aggregateStats methods.

I didn't see a method that calculated total features in Utils.stats and Utils.aggregateStats methods.

Correct, that is why I proposed to add these statistics to spock-reports: https://github.com/renatoathaydes/spock-reports/issues/193


Fix 'File accessed outside allowed roots' CI error

partial fix for #1770
Fixes "java.lang.AssertionError: File accessed outside allowed roots:" errors.
See https://youtrack.jetbrains.com/issue/IDEA-129297
Update DefaultAppEngineProjectServiceTest to use the CloudToolsRule, and added the root fix to AppEngineCodeInsightTestCase (eventually this test could be updated to use the CloudToolsRule, but currently its deeply tied into the platforms test hierarchy so I left it as is).

Also, somehow, this seems to consistently fix the CI overall.


esp_http_client redirect issue

I want to say that i have tested this url (or evn mp3 file, which hardcoded works) with esp_http_client example and it seems to work (redirect as far as i could see), but for some reason its crashing with my code:
I (25487) web_radio: https://maestro.emfcdn.com/stream_for/sa008/tunein  // <-- value retrieved from audio/x-mpegurl (m3u playlist) and set as url for new http request (called from outside of this request)

W (25495) web_radio: Success: add track to queue - 2
W (25500) web_radio: HTTP_EVENT_ON_FINISH stack: 4572

I (25506) web_radio: HTTP_EVENT_ON_FINISH
I (25511) web_radio: HTTP chunk encoding Status = 200, content_length = 51
I (25519) web_radio: HTTP_EVENT_DISCONNECTED

E (25536) web_radio: 148: http_client_get URL: https://maestro.emfcdn.com/stream_for/sa008/tunein, 51  // <-- number of bytes in string to check if there is any non-printable char

E (25546) HTTP_CLIENT: Error parse url https://maestro.emfcdn.com/stream_for/sa008/tunein // <-- its redirecting uri

E (25555) HTTP_CLIENT: Error set default configurations
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x400ef8cb  PS      : 0x00060330  A0      : 0x801328c3  A1      : 0x3ffde830
A2      : 0x00000000  A3      : 0x3ffdabb0  A4      : 0x00000000  A5      : 0x00000001
A6      : 0x00000001  A7      : 0x00000004  A8      : 0x800ef4f8  A9      : 0x3ffde810
A10     : 0x00000000  A11     : 0x3ffb6ea0  A12     : 0x3f40eed0  A13     : 0x0000001f
A14     : 0x00000001  A15     : 0x00000005  SAR     : 0x0000001d  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000040  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0xffffffff

Backtrace: 0x400ef8cb:0x3ffde830 0x401328c0:0x3ffde850 0x40132967:0x3ffde8d0

Backtrace ends in here:
https://github.com/espressif/esp-idf/blob/master/components/esp_http_client/esp_http_client.c#L943
https://github.com/espressif/esp-idf/blob/master/components/esp_http_client/esp_http_client.c#L487
I have to add that works when i hardcode this url (or any other that is causing crash) in my code. Here is part of my code that is making initialization:
esp_err_t _http_event_handler(esp_http_client_event_t *evt)
{
....
        case HTTP_EVENT_ON_FINISH:
        {
            if(content_type == AUDIO_MPEG)
            {

            }else if(content_type == MPEG_URL)
            {
                web_radio_t *radio_config;
                radio_config = calloc(1, sizeof(web_radio_t));
                memcpy(radio_config, evt->user_data, sizeof(web_radio_t));
                // radio_config->url = calloc(strlen(tmp_url)+1, sizeof(char));
                strcpy(radio_config->url, tmp_url);
                web_radio_add_to_queue(radio_config);
            }
....
}

void http_perform_as_stream_reader(void *_config)
{
    web_radio_t *web_config = _config;
    char *buffer = malloc(MAX_HTTP_RECV_BUFFER);
    if (buffer == NULL) {
        ESP_LOGE(TAG, "Cannot malloc http receive buffer");
        return;
    }

    esp_http_client_config_t config = {
        .url = web_config->url, // <-- char* variable
        .event_handler = _http_event_handler,
        .user_data = web_config,
    };
.....
}

Im almost sure its my fault, just i dont know where. Only time it works is when i hardcode this line:
`radio_config->url = "https://some_url";'
Could you help me please @projectgus

@tuanpmt can you take a look, please?

I overcame this error when I increased the stack size of my task.

@WayneKeenan
How to Increase stack size


pythonPackages.pwntools: add bash completions

Motivation for this change
Install shellcraft completions. Note that they don't work with nix-shell -p since no completions does (#26031), but I have run and tested them using mkShell.
Things done

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

[ ] NixOS
[ ] macOS
[X] 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"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121907 at d1d671c0 run on x86_64-linux 1

2 packages built successfully:

pwntools (python38Packages.pwntools)
python39Packages.pwntools

4 suggestions:

warning: unused-argument
Unused argument: makeWrapper.
Near pkgs/development/python-modules/pwntools/default.nix:7:3:
  |
7 | , makeWrapper
  |   ^

warning: unused-argument
Unused argument: isPy3k.
Near pkgs/development/python-modules/pwntools/default.nix:5:3:
  |
5 | , isPy3k
  |   ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/pwntools/default.nix:79:0:
   |
79 |     description = "CTF framework and exploit development library";
   | ^

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/development/python-modules/pwntools/default.nix:23:3:
   |
23 | , fetchpatch
   |   ^

LGTM, and builds fine.
But I am not too sure how to test this.
@kristoff3r Could you provide the expression with mkShell you used please?

LGTM, and builds fine.
But I am not too sure how to test this.
@kristoff3r Could you provide the expression with mkShell you used please?

{ pkgs ? import <nixpkgs> {}}:

pkgs.mkShell {
  nativeBuildInputs = with pkgs; [
    python3Packages.pwntools
  ];
}

Then run it with nix-shell -I nixpkgs=<path-to-checked-out-pr>. I don't know if there's a way to get the PR via url, that would be handy.

Now the diff looks very neat. Thanks for bearing with me and sorry for the nitpicks!

No worries, thanks for reviewing and merging!


bug: v3 CLI Error: Span processor did not completed within timeout period

Provide environment information
System:
OS: macOS 14.5
CPU: (8) arm64 Apple M2
Memory: 169.73 MB / 24.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.11.0 - /usr/local/bin/node
npm: 10.5.2 - ~/myproject/node_modules/.bin/npm
Describe the bug
The v3 project creator said the project was initialized successfully, and then threw error asking me to open issue on github.
`●     3. Head over to our v3 docs (https://trigger.dev/docs/v3) to learn more.
│
●     4. Need help? Join our Discord community (https://trigger.dev/discord) or email us at<EMAIL_ADDRESS>│
└  Project initialized successfully. Happy coding!
✘ [ERROR] An unknown error has occurred. Please open an issue on github with the below:
✘ [ERROR] [
Error: Span processor did not completed within timeout period of 500 ms
    at Timeout._onTimeout

(/Users/kamil/.npm/_npx/615bebf0b780b73f/node_modules/@opentelemetry/sdk-trace-base/build/src/BasicTracerProvider.js:109:29)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7)
]
`
Reproduction repo
n/a
To reproduce
Run the CLI again?
Additional information
I already had the V2 Project set up in my codebase, it's possible that this somehow interfered with the v3.

Hey @ky-zo, thanks for creating an issue. This is due to a timeout that's a bit too aggressive. Luckily, we fixed this a few days ago in c11a77f50b9207b5fa83053ec7b7b0beb45f5498 but new packages are yet to be released. We're in the process of running some tests on the latest changes and should release a new CLI within the next day or two.

cool, thanks!

Ok I think this was fixed in 3.0.0-beta.37


Topic/sort devices

Devices can now be sorted according to name
and online status through dataTable ordering.

This PR has conflicts that must be resolved
Conflicting files:
api/deviceadm/service_test.go
api/sessionmngr/service_test.go
api/store/mocks/store.go


Pull requests failing with circleci

Hi there are some pull requests failing in circleci. The error says
lein trampoline midje
WARNING: cat already refers to: #'clojure.core/cat in namespace: net.cgrand.parsley.fold, being replaced by: #'net.cgrand.parsley.fold/cat
WARNING: update already refers to: #'clojure.core/update in namespace: utilize.map, being replaced by: #'utilize.map/update
WARNING: update already refers to: #'clojure.core/update in namespace: clojure.math.combinatorics, being replaced by: #'clojure.math.combinatorics/update
lein trampoline midje died unexpectedly
And also
Your build has exceeded the memory limit of 4G on 1 container. The results of this build are likely invalid. We have taken a snapshot of the memory usage at the time, which you can find in a build artifact named memory-usage.txt. The RSS column in this file shows the amount of memory used by each process, measured in kilobytes.
Does anyone knows about this? If there is anyway I could help please tell me.
Thanks!

You can ignore the error from CircleCI


LM Studio Integration via OpenAI API V1 using base URL

Using opensource local LLM's available in LM Studio.
Using URL from LM Studio in OpenDevin for OpenAI-like integration:
OPENAI_API_BASE_URL = "http://localhost:1234/v1" # LM Studio local API endpoint
This solution proposed on crewAI may help: https://github.com/joaomdmoura/crewAI/issues/154#issuecomment-1919150315

See this issue for the solution: https://github.com/OpenDevin/OpenDevin/issues/111


Create LICENSE

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master      #3   +/-   ##
======================================
  Coverage    58.5%   58.5%
======================================
  Files          23      23
  Lines         388     388
======================================
  Hits          227     227
  Misses        161     161

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b5f6696...4da61c2. Read the comment docs.


az connectedk8s install appears to be looping and reinstalling

Windows 11
PowerShell 7.2.4
When prompted to install the connectedk8s extension, the install appears to be looping.  Please see the below screen print where the customer is prompted to continually reinstall the extension.

CCing @mikefrobbins who originally reported this issue

route to CXP team

@dbradish-microsoft Thanks for reaching out to us and sharing this feedback.
As an isolation step, Could you please have the customer open the CMD prompt (not PS prompt) and then run the below command to install the extension separately ?

az extension add --name connectedk8s

Once the installation is done, then try running the below command and check if that works. Awaiting your reply.

az connectedk8s enable-features -n clusterName -g resourceGroupName --features cluster-connect custom-locations

@mikefrobbins, this latest  is for you.

@dbradish-microsoft @mikefrobbins Thanks for getting back. We will now proceed with closure of this github issue. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help.


SAK- 30342 Joda 2.9.2

https://jira.sakaiproject.org/browse/SAK-30342

cheers!

no worries dave!
On Tue, Feb 16, 2016 at 6:12 PM, David Horwitz<EMAIL_ADDRESS>wrote:

cheers!
—
Reply to this email directly or view it on GitHub
https://github.com/sakaiproject/sakai/pull/1732#issuecomment-184555402.


Add fast-path for exporting png/jpeg textures without going through Skia bitmap

There's no reason to re-encode the image to png when it's already a png. Should also make it faster.

Just tested it. The exported PNG file now has the same SHA1 hash in CS2 and CSGO (CS2 file is vtex_c, CSGO file is plain png). So it seems to restore the original file, as intended.

Hey @xPaw - I noticed one issue with VTEX_FORMAT_BGRA8888 files. They are originally also PNG files but still seem to get decoded and not restored to their original. Do you think it would be possible to restore the original file for VTEX_FORMAT_BGRA8888 as well?

That's not png.

Is this an error on Valve's part then? Because the original is definitely a .png file, at least Valve stores it as PNG.
One example is the ./panorama/images/econ/stickers/antwerp2022/astr_graffiti_large_png.vtex_c of the CS2 pak01:
VTEX File: https://media.chescos.me/uploads/znUOcc2VNZUxSxhF7oplOOOXwjRO1LQfibvxapjYl3OS2DjI2hDl0PLu4RxNNz6Y.vtex_c
CDN PNG file: https://steamcdn-a.akamaihd.net/apps/730/icons/econ/stickers/boston2018/nor_graffiti_large.d662f7dbecd1c0c20e0c5cb11bf595ef5c8d39c5.png
When opening the vtex_c in VRF, it shows up as VTEX_FORMAT_BGRA8888.

There's no error and there's no need for them to compile it as png if they don't need it.


Unable to publish server-hosted Blazor app from Visual Studio Preview

This may be related to https://github.com/aspnet/AspNetCore/issues/10878 but appears to have different symptoms.
The issue is described at https://stackoverflow.com/questions/56543379/how-can-i-deploy-a-blazor-server-hosted-application-from-visual-studio-2019 but in summary, when attempting to publish a server-hosted Blazor app from with Visual Studio, it appears that the deployment process assumes that the Client dll lives in $client-build-directory/$runtimeEnvironment rather than just $client-build-directory.  I.e. I get errors saying

CSC(0,0): Error CS0006: Metadata file 'D:\work\Applications\Web\MyApp.Client\bin\Release\netstandard2.0\win-x86\MyApp.Client.dll'
could not be found

Note that the dll has been built to D:\work\Applications\Web\MyApp.Client\bin\Release\netstandard2.0\MyApp.Client.dll

I have just spotted that the reported error in the Error List is the same as for #10878.  Not sure if that means it's really the same problem or it's just that any build error will eventually cause a "projects.assets.json" report.

Further details in the SO link above, but it appear my main problem was trying to set the deployment to "self-contained" to workaround the lack of .netcore 3.0 on the server.  It appears that .netcore3 can be manually added from the Azure portal (websockets also needs to be enabled) but this is not done automatically by the deployment mechanism.

Thanks for contacting us, @NeilMacMullen.
Looks like you've got your problem solved already. We're closing this issue as there is no follow-up actions are pending here.

@mkArtakMSFT   The implicit follow-up action in my last comment was for the deployment mechanism to be modified to add .netcore 3 automatically or, at the very least, for a warning to be generated making it obvious that this needs to be done.   (Maybe this has already been done/worked around in one of the referenced issues?)


CREATE INDEX on table with data

Looks like there is a bug preventing a creation of an index on tablse already populated with data.
CREATE TABLE t1( x INTEGER, y VARCHAR(8) );
INSERT INTO t1 VALUES(1,'a');
CREATE INDEX tmp ON t1(x);

will give TypeError: rightfns is not a function while if there is no insert it does not rase an error

Fixed.

Strange. When I am testing with node I get no error, but when I run same code in the browser I get:

I remember you said some other bug was also present in browser but not node - do you remember?

I just tested https://github.com/agershun/alasql/issues/506 and I also get an error in the browser.
I am wondering - have you pushed the last changes?

Yes. Please let me know if the problem still occur.

Ough ! I think I had the wrong version on my computer. Its totally working now :+1:


KiCad Driver Project SCH file does not include HV507 to connector wires

I am working on adding current limiting resistors as we discussed and I'm just looking at the Driver schematic. There don't seem to be connecting wires between the HV507 output lines and the connectors. Was that an oversight in the SCH file that was committed or did you route each of those manually on the PCB design?

Looks like I just connected them in the PCB design since the layout would dictate the best connection scheme.

NP. With the placement of the HV507s relative to the connectors, I think I might "punt" and place the resistors on the segment board. I'm working on that now.


fix trackbar wrapper

Fix #832
I gave up wrapping userdata

This fix is much much worse now. Opencv stores the pointer passed down if it's not null. So now, it's storing a stack pointer that is definitely going to be pointing to another variable later in the program. There is going to need to be an IntPtr overload as the only way to do this safely.


Why you dont write same document like this article for springboot?

[Enter feedback here]

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

ID: 99d7a4e1-48e0-df79-ee56-79d5df3b7bc7
Version Independent ID: 7266a603-9e98-9864-6b26-bdaa8d5b78b8
Content: Move a protected web API to production - Microsoft identity platform
Content Source: articles/active-directory/develop/scenario-protected-web-api-production.md
Service: active-directory
Sub-service: develop
GitHub Login: @jmprieur
Microsoft Alias: jmprieur

@navyasric

Thank @jmprieur for replying!
I have implenment angular to get token from azure AD, angular call springboot api with this token. I want to verify this token in springboot and get user infor. But I can't see any samle repository or document.
Please help me point out where I can look up it?
Note: English is not my mother tongue.

@longMOR @jmprieur We have plans to add samples and surface them in the documentation for these scenarios using Spring Boot. Meanwhile, please take a look at this sample if it solves your need: https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/spring/azure-spring-boot-samples/azure-spring-boot-sample-active-directory-resource-server-by-filter

@longMOR - Please see the response from @navyasric
Flagging @mmacy to open a work item in ADO and add to our backlog - Something for us to consider adding in future or to work on with the PMs. For now looks like there's a reference to use.
#please-close

@CelesteDG @longMOR @jmprieur Added to internal Azure DevOps for triage/scheduling:
Microsoft-internal tracking information:

ID
Title
Iteration Path

1349220
[ISSUE][71079] Why you dont write same document like this article for springboot?
Technical Content\Backlog

@mmacy also notifying @navyasric


ur_modern_driver sometimes keeps executing one trajectory list behind

Hi,
My research group at university has been using ur_modern_driver for awhile, and sometimes we noticed a strange bug where ur_modern_driver never finishes executing a trajectory (it just stopped halfway). Whenever this happened, after we cancel the goal, if we input a new trajectory list, it will be executing 1 trajectory list behind.
here is the log we have when it happened. Note: sec 24 in follow_joint_trajectory/result and sec 26 in /follow_joint_trajectory/goal is the last published msg/response we got before cancelling the goal.
Afterward, the follow_joint_trajectory/result always says error code: 0 and error_string: Goal canceled by client. The published joint state reflects the actual robot joint position.
Restarting the ur_modern_driver will temporarily fix this problem, until it resurfaces for unknown reason.
Any helps would be appreciated,
Felix
rostopic echo /follow_joint_trajectory/goal
---
header:
  seq: 25
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 751332044
  frame_id: ''
goal_id:
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 751256942
  id: /simple_ur5_driver_node-25-1488322862.751
goal:
  trajectory:
    header:
      seq: 0
      stamp:
        secs: 0
        nsecs:         0
      frame_id: ''
    joint_names: ['shoulder_pan_joint', 'shoulder_lift_joint', 'elbow_joint', 'wrist_1_joint', 'wrist_2_joint', 'wrist_3_joint']
    points:
      -
        positions: [0.30003762358163316, -1.3300827834477285, -1.7997786308312367, -0.2700036285261235, 1.4998983234390535, 1.6002492253792502]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs:         0
      -
        positions: [0.2740209366499169, -1.3557743539621965, -1.8373377133488311, -0.1987249852305596, 1.5041957780008162, 1.6021728750855273]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 169328642
      -
        positions: [0.22599013000674842, -1.4032049456812143, -1.906677557996698, -0.06713364376182626, 1.5121295402686858, 1.6057242283894235]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 338657284
      -
        positions: [0.16502795234426537, -1.463405312093814, -1.994685822357452, 0.09988613579464298, 1.5221993154548281, 1.6102317152751378]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 507985927
      -
        positions: [0.10250264192120583, -1.525149277645198, -2.084950708881302, 0.2711884738012781, 1.5325272900047175, 1.6148547787476653]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 677314569
      -
        positions: [0.04839420020894276, -1.5785815555262035, -2.16306455298848, 0.4194308816916354, 1.5414649602882757, 1.6188555067527373]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 846643212
      -
        positions: [0.008437197098348496, -1.6180392376537152, -2.2207486224830117, 0.5289021982875916, 1.548065086036134, 1.6218098905103289]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs:  15971854
      -
        positions: [-0.016663997163435074, -1.6428267559133058, -2.2569860507552177, 0.5976726407645384, 1.5522113188777373, 1.6236658495375338]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 185300497
      -
        positions: [-0.02990418754327696, -1.6559014908194636, -2.2761002986350625, 0.6339471598732576, 1.5543983427941874, 1.624644816936499]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 354629139
      -
        positions: [-0.03563311607301624, -1.6615588280384743, -2.284370886659995, 0.649642865256838, 1.5553446512195743, 1.6250684085995128]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 523957782
      -
        positions: [-0.03759172411737154, -1.663492960421042, -2.2871984381215107, 0.6550089183794296, 1.5556681754675699, 1.6252132262620818]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 693286424
      -
        positions: [-0.03808890923632328, -1.6639839324873862, -2.2879162011848186, 0.6563710703259337, 1.5557503008535996, 1.6252499876687339]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 862615067
      -
        positions: [-0.03817235289265084, -1.6640663333936256, -2.2880366649157233, 0.6565996832400323, 1.555764084135171, 1.6252561574153048]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs:  31943709
      -
        positions: [-0.0381790390830617, -1.6640729360303435, -2.2880463174582637, 0.656618001582508, 1.555765188564784, 1.6252566517860236]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs: 201272352
      -
        positions: [-0.03817930138745474, -1.664073195056861, -2.288046696134933, 0.6566187202251744, 1.5557652318924073, 1.6252566711805672]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs: 370600994
      -
        positions: [-0.03817930649111488, -1.6640732000967435, -2.2880467035028498, 0.6566187342078146, 1.5557652327354337, 1.625256671557927]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs: 539929637
      -
        positions: [-0.038179306530678137, -1.6640732001358123, -2.2880467035599654, 0.6566187343162071, 1.5557652327419687, 1.6252566715608523]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs: 709258279
  path_tolerance: []
  goal_tolerance: []
  goal_time_tolerance:
    secs: 0
    nsecs:         0
---
header:
  seq: 26
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 775063037
  frame_id: ''
goal_id:
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 775028944
  id: /simple_ur5_driver_node-26-1488322865.775
goal:
  trajectory:
    header:
      seq: 0
      stamp:
        secs: 0
        nsecs:         0
      frame_id: ''
    joint_names: ['shoulder_pan_joint', 'shoulder_lift_joint', 'elbow_joint', 'wrist_1_joint', 'wrist_2_joint', 'wrist_3_joint']
    points:
      -
        positions: [-0.038390898830618525, -1.6642658158903219, -2.288329537497892, 0.6571696412718988, 1.5557814352918464, 1.6252728742097837]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs:         0
      -
        positions: [-0.03718284135872967, -1.6806558343009068, -2.290063694912922, 0.6379053192919489, 1.5433001111963, 1.6241308836145596]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 179052190
      -
        positions: [-0.03495258141062718, -1.7109143298281408, -2.2932652162945155, 0.6023404171751184, 1.5202576667122145, 1.622022593284915]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 358104380
      -
        positions: [-0.03212186686111248, -1.7493193433819378, -2.2973286857403847, 0.5572003491037567, 1.4910114871747215, 1.6193466863280583]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 537156570
      -
        positions: [-0.029218569887251244, -1.7887091008730116, -2.3014963467105067, 0.5109028433895395, 1.4610154055978055, 1.6166021663723078]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 716208760
      -
        positions: [-0.026706101352179025, -1.8227963910095177, -2.3051029763961894, 0.47083769421377464, 1.4350572580793206, 1.6142271010259854]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 0
          nsecs: 895260950
      -
        positions: [-0.024850739972433384, -1.847968543725707, -2.3077663337025394, 0.4412511225147483, 1.4158881645272086, 1.6124732066163934]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs:  74313140
      -
        positions: [-0.02368519243900343, -1.8637818191499798, -2.309439468420631, 0.42266468644741123, 1.403846041654728, 1.6113714011539573]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 253365330
      -
        positions: [-0.023070398135655763, -1.87212288750564, -2.310322001019185, 0.41286085203826645, 1.397494152667046, 1.6107902290419032]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 432417520
      -
        positions: [-0.022804381369784178, -1.8757320036210698, -2.310703866085867, 0.4086188083035403, 1.3947457391627605, 1.610538760339572]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 611469710
      -
        positions: [-0.022713435466922095, -1.876965889472499, -2.3108344182454164, 0.4071685369412408, 1.3938061106142867, 1.610452788133647]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 790521900
      -
        positions: [-0.022690349199272493, -1.8772791066501695, -2.310867558408994, 0.40680039113388783, 1.3935675895212125, 1.6104309644198351]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 1
          nsecs: 969574090
      -
        positions: [-0.022686474580925705, -1.8773316745681001, -2.31087312039449, 0.40673860442496146, 1.3935275580090882, 1.610427301698636]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs: 148626280
      -
        positions: [-0.02268616411471202, -1.8773358867410113, -2.310873566066405, 0.4067336535668744, 1.3935243503558732, 1.6104270082113603]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs: 327678470
      -
        positions: [-0.022686151934883637, -1.8773360519877946, -2.310873583550457, 0.40673345934090327, 1.3935242245171702, 1.6104269966976288]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs: 506730660
      -
        positions: [-0.02268615169790055, -1.8773360552030036, -2.3108735838906442, 0.4067334555618459, 1.3935242220687247, 1.610426996473606]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs: 685782851
      -
        positions: [-0.022686151696063472, -1.8773360552279277, -2.3108735838932812, 0.4067334555325509, 1.3935242220497446, 1.6104269964718694]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        effort: []
        time_from_start:
          secs: 2
          nsecs: 864835041
  path_tolerance: []
  goal_tolerance: []
  goal_time_tolerance:
    secs: 0
    nsecs:         0
---

rostopic echo /follow_joint_trajectory/goal
---
header:
  seq: 23
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 255526896
  frame_id: ''
status:
  goal_id:
    stamp:
      secs:<PHONE_NUMBER>
      nsecs: 763487100
    id: /simple_ur5_driver_node-24-1488322860.763
  status: 3
  text: ''
result:
  error_code: 0
  error_string: ''
---
header:
  seq: 24
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 548539396
  frame_id: ''
status:
  goal_id:
    stamp:
      secs:<PHONE_NUMBER>
      nsecs: 751256942
    id: /simple_ur5_driver_node-25-1488322862.751
  status: 3
  text: ''
result:
  error_code: 0
  error_string: ''
---
header:
  seq: 25
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 192089845
  frame_id: ''
status:
  goal_id:
    stamp:
      secs:<PHONE_NUMBER>
      nsecs: 775028944
    id: /simple_ur5_driver_node-26-1488322865.775
  status: 2
  text: ''
result:
  error_code: -100
  error_string: Goal cancelled by client
---
header:
  seq: 26
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 243607138
  frame_id: ''
status:
  goal_id:
    stamp:
      secs:<PHONE_NUMBER>
      nsecs: 296827077
    id: /simple_ur5_driver_node-27-1488323099.297
  status: 3
  text: ''
result:
  error_code: 0
  error_string: Goal cancelled by client
---
---
header:
  seq: 27
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 676625450
  frame_id: ''
status:
  goal_id:
    stamp:
      secs:<PHONE_NUMBER>
      nsecs: 282537937
    id: /simple_ur5_driver_node-28-1488323109.283
  status: 3
  text: ''
result:
  error_code: 0
  error_string: Goal cancelled by client
---

The last /joint_states when the robot never finishes/execute the trajectory we sent.
header:
  seq: 93739
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 735777683
  frame_id: ''
name: ['shoulder_pan_joint', 'shoulder_lift_joint', 'elbow_joint', 'wrist_1_joint', 'wrist_2_joint', 'wrist_3_joint']
position: [-0.038390898830618525, -1.66428467107084, -2.28834839267841, 0.6571372359277533, 1.5557814352918464, 1.6252728742097837]
velocity: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
effort: [-0.2981608185299103, 1.7777558578512693, 1.4616605539962517, 0.9348502409565058, 0.19215518819008112, 0.4468370646007442]
---

This may be related to my PR #101 which addresses some race conditions present in the trajectory action goal/cancel callbacks. Maybe you can check if you can still reproduce the problem with #101?
I also noticed that the error string is never reset, so subsequent action calls after a failure will always return the old error string.

This may be related to my PR #101 which addresses some race conditions present in the trajectory action goal/cancel callbacks. Maybe you can check if you can still reproduce the problem with #101?

Interesting. I do noticed that this problems seems to happen more often with more stop trajectory in the middle of execution, although it usually happened randomly. That might be in fact related to the issue you addressed on your PR.
I will try #101 and get back to you. It might take few days to ascertain whether it fixes this problem or not, given the randomity behavior of this bug.

I'm seeing this behavior on 9ca88362427e32f8d1a125199f6b8e387e81a711. I'll try #101 as well and report back.

I haven't seen the retained trajectory bug on #101, but the server appears to be deadlocking after running for a period of time.
Output from the follow_joint_trajectory/status channel:
---
header:
  seq: 2614
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 250381600
  frame_id: ''
status_list:
  -
    goal_id:
      stamp:
        secs:<PHONE_NUMBER>
        nsecs: 823723015
      id: /capture_experiment-96-1500952750.823723015
    status: 2
    text: ''
  -
    goal_id:
      stamp:
        secs:<PHONE_NUMBER>
        nsecs:  77816914
      id: /capture_experiment-97-1500952781.77816914
    status: 7
    text: ''

Output from node:
[ INFO] [1500952750.868821747]: on_goal
[DEBUG] [1500952750.869189614]: Accepting goal, id: /capture_experiment-96-1500952750.823723015, stamp:<PHONE_NUMBER>.82
[DEBUG] [1500952763.989070505]: The action server has received a new cancel request
[DEBUG] [1500952763.989228775]: Transisitoning to a cancel requested state on goal id: /capture_experiment-96-1500952750.823723015, stamp:<PHONE_NUMBER>.82
[ INFO] [1500952763.989467065]: on_cancel
[DEBUG] [1500952763.989660130]: Setting status to canceled on goal, id: /capture_experiment-96-1500952750.823723015, stamp:<PHONE_NUMBER>.82
[DEBUG] [1500952763.989778564]: Publishing result for goal with id: /capture_experiment-96-1500952750.823723015 and stamp:<PHONE_NUMBER>.82
[DEBUG] [1500952781.141009364]: The action server has received a new goal request
[ INFO] [1500952781.141109694]: on_goal
[DEBUG] [1500952812.011810600]: The action server has received a new cancel request
[DEBUG] [1500952812.011858699]: Transisitoning to a cancel requested state on goal id: /capture_experiment-96-1500952750.823723015, stamp:<PHONE_NUMBER>.82
[DEBUG] [1500952812.011892001]: Transisitoning to a cancel requested state on goal id: /capture_experiment-97-1500952781.77816914, stamp:<PHONE_NUMBER>.08

Action 96 did not execute anything (maybe the deadlock starts here?), so the client timed out and sent a cancel request. Notice that the debug statements say it's trying to cancel the 96 goal twice. After this point, the node is completely locked, and sending additional goals or cancels has no effect and produces no debug statements.
This behavior has been observed multiple times over the past hour or so.

I am also observing the retained trajectory bug issue.  Ours seems to be triggered infrequently by a trajectory cancellation.  Has #101 demonstrated an appropriate fix?

I can't guarantee correctness, but we were having the same problem, and #101 has fixed it, or at least made it much more infrequent. I can also confirm we also experience very occasional deadlock with that pull request, but that is a MUCH more preferable mode of failure.
This is a dangerous bug! I'm surprised that pull request has been sitting for a year. Our UR5 would freak out every once in a while when we cancelled and then gave a new trajectory.

I am also facing the same issue.  If I lower the velocity slider bar in the UR teach pendant and run the trajectory, the robot goes into an abrupt protective stop. After which, I enable the robot from the pendant and cancel the goals and send a new trajectory.  This time the robot goes into various jerky random motions before going to desired pose. This must be due to the retained trajectory. Has anyone found a proper fix to the problem? I will check #101.

I'm closing this as we've officially deprecated this package.
Refer to the announcement on ROS Discourse.

ur_robot_driver makes use of ros_control's JointTrajectoryController, which should not exhibit this behaviour.


fix: test case expects different error message

yarn test was failing with:
Expected pattern: /Must be a full url with/
Received message: "...
    npm WARN invalid config registry=\"npm_config_registry\" set in environment
    npm WARN invalid config Must be full url with \"http://\"
    npm ERR! code ETARGET
    npm ERR! notarget No matching version found for<EMAIL_ADDRESS>    npm ERR! notarget In most cases you or one of your dependencies are requesting
    npm ERR! notarget a package version that doesn't exist.·

@fernandonogueira thanks for this! I guess you were using node 18 before we got a chance to :)
In any case this is now fixed here


Fix setting webhook activity using isActive field in the App manifest

I want to merge this change because it uses the isActive field from App manifest to set the initial webhook activity state.
Resolves https://github.com/saleor/apps/issues/435

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

@przlada Why is it useful to support apps installing inactive webhooks? Why do we need isActive in manifest at all?

@przlada Why is it useful to support apps installing inactive webhooks? Why do we need isActive in manifest at all?

@patrys In many cases, apps require additional configuration after they are installed. Without that configuration, the app might receive webhook events that it cannot handle correctly. To address this with @lkostrowski we came up with an idea to install those apps with webhooks disabled by default and leave them for the app to enable when the configuration is provided by the user (to make that possible, we enabled webhookUpdate mutation for apps)

@patrys we want apps to control webhooks enabled/disabled. Many apps initially will have inactive webhooks. We can either:

Have them statically declared in manifest as isActive: false and app will make it active in runtime
Dont register it at all - app will create webhook in runtime with webhookCreate

IMO option 1 is slightly better, because its more explicit what webhooks app will register (but app can still hide some webhooks. Also, this field was already added so removing it is an API change


Add dockerfile and compose for production

feat(deploy) Add dockerfile and compose for production.
Add Dockerfile for production (#1431)
Add docker-compose.yml for production
Update documentation for deployment
Fixes #1435
Fixes #1431

Thanks @FedeG.
Have you tested both dockerfile and the docker-compose file configuration to work well?

I tested it, seems to be ok including live reload for dev environment.

Actually FYI I tested the dev docker updates, haven't yet tested the production one.

@FedeG can you outline the differences from the dev docker setup? is it just the NODE_ENV defaulting to production in the dockerfile?

Differences:

In Dockerfile:

Simplify some commands
Add --production to npm install
NODE_ENV defaulting to production
Remove expose for debug port (remove EXPOSE 5858:5858)

In docker-compose.yml:

Change ports (remove 3000, 5858 and 35729 and add 8443)
NODE_ENV defaulting to production
Remove code volumes (change ./:/opt/mean.js to /opt/mean.js)
Remove expose db port (remove 27017 in mongo container)

Update documentation for deployment in production

Sounds good.
Thanks @FedeG.


Added PF_LDAP_USERNAME, PF_LDAP_PASSWORD in docker-compose.yaml examples

Added default variables back for ease of use.

What's the reason for the switch from PING_IDENTITY_DEVOPS_TAG to edge?

Was using edge in testing. I changed this back to the ${PING_IDENTITY_DEVOPS_TAG} variable. Nice catch!


a/v desync - decoder dependent

Transcoding nVidia shadowplay videos causes desync depending on which decoder is used.
(bad) Synth log: https://pastebin.com/FV6k0RJZ
(better) avcuvidnative log: https://pastebin.com/kYJehCUL
(better) avcuvidcuda log: https://pastebin.com/Qtv5zV4R
(perfect(slower)) ffmpegintel log: https://pastebin.com/80uLe2W5
(perfect(slow))ffmpegdxva2 log: https://pastebin.com/WHLeWq95

Thanks for trying different decoders and for uploading the results to pastebin, this gives me all needed info.
What is unusual:
Frame rate mode           : Variable
Frame rate                : 59.338 FPS
Minimum frame rate        : 1.360 FPS
Maximum frame rate        : 63.694 FPS
Original frame rate       : 60.000 FPS

and then the properties staxrip reads from the scripts:
source frame count : 17816
source frame rate  : 59.338162
source duration    : 00:05:00.2450000
target frame count : 17816
target frame rate  : 59.338162
target duration    : 00:05:00.2450000

synth output:
Frame rate mode           : Constant
Frame rate                : 59.338 FPS

ffmpeg output:
Frame rate mode           : Constant
Frame rate                : 60.000 FPS

I believe that the ffmpeg decoder converts vfr to cfr. I also believe that some avisynth and vapoursynth source filters can make this conversion too, you would have to read the docs of the source filters and edit the avs code yourself.
Generally it's possible to re-encode with VFR, staxrip got some VFR improvements a few weeks ago but only for MKV, it can extract and mux a time code file for MKV. If somebody makes a request MP4 could probably also be improved. Unfortunately I don't have much experience with VFR.
Other things you could try is to check if shadowplay has a setting to record with CFR and if you are familiar with handbrake or are interested in it you can check how handbrake deals with it, I think typically handbrake is good in handling many type of issues automatically.
Hope this helps

in the next build you can use the context menu:
https://postimg.org/image/v2a9wcqcr/
https://github.com/VFR-maniac/L-SMASH-Works/blob/master/AviSynth/README#L48
Can I close the issue?

Yes, thank you. 👍


Failure during kernel rebuild

On nixos-17.09 after setting

musnix.enable = true;
musnix.kernel.realtime = true;

sudo  -E nixos-rebuild boot

...
GOT: *
QUESTION: CRC-CCITT functions, NAME: CRC_CCITT, ALTS: M/y/?, ANSWER:
GOT:
QUESTION: CRC16 functions, NAME: CRC16, ALTS: M/y/?, ANSWER:
GOT:
GOT: CRC calculation for the T10 Data Integrity Field (CRC_T10DIF) [Y/?] y
QUESTION: CRC ITU-T V.41 functions, NAME: CRC_ITU_T, ALTS: M/y/?, ANSWER:
GOT:
GOT: CRC32/CRC32c functions (CRC32) [Y/?] y
QUESTION:   CRC32 perform self test on init, NAME: CRC32_SELFTEST, ALTS: N/y/?, ANSWER: n
GOT:
GOT:   CRC32 implementation
GOT:   > 1. Slice by 8 bytes (CRC32_SLICEBY8)
GOT:     2. Slice by 4 bytes (CRC32_SLICEBY4)
GOT:     3. Sarwate's Algorithm (one byte at a time) (CRC32_SARWATE)
GOT:     4. Classic Algorithm (one bit at a time) (CRC32_BIT)
CHOICE: 1-4?, ANSWER:
QUESTION: CRC7 functions, NAME: CRC7, ALTS: M/y/?, ANSWER:
GOT:
QUESTION: CRC32c (Castagnoli, et al) Cyclic Redundancy-Check, NAME: LIBCRC32C, ALTS: M/y/?, ANSWER:
GOT:
QUESTION: CRC8 function, NAME: CRC8, ALTS: M/y/?, ANSWER:
GOT:
QUESTION: PRNG perform self test on init, NAME: RANDOM32_SELFTEST, ALTS: N/y/?, ANSWER:
GOT:
GOT: XZ decompression support (XZ_DEC) [Y/?] y
QUESTION: XZ decompressor tester, NAME: XZ_DEC_TEST, ALTS: N/m/y/?, ANSWER: n
GOT:
QUESTION: glob self-test on init, NAME: GLOB_SELFTEST, ALTS: N/y/?, ANSWER: n
GOT:
QUESTION: CORDIC algorithm, NAME: CORDIC, ALTS: M/y/?, ANSWER:
GOT:
QUESTION: JEDEC DDR data, NAME: DDR, ALTS: N/y/?, ANSWER:
GOT:
GOT: IRQ polling library (IRQ_POLL) [Y/?] y
QUESTION: Select compiled-in fonts, NAME: FONTS, ALTS: N/y/?, ANSWER:
GOT:
GOT: #
GOT: # configuration written to .config
GOT: #
GOT: make[1]: Leaving directory '/tmp/nix-build-linux-config-4.9.35-rt25.drv-0/build'
GOT: make: Leaving directory '/tmp/nix-build-linux-config-4.9.35-rt25.drv-0/linux-4.9.35'
error: unused option: RT_GROUP_SCHED
builder for ‘/nix/store/kdjqqv28kdvjxya5ffmsrc2cz5yq7n7a-linux-config-4.9.35-rt25.drv’ failed with exit code 255

Curious.  I'll see if I can reproduce locally...
nixos-version?

% nixos-version
17.09.git.0e423ee (Hummingbird)
it was forked from channels/nixos-17.09 at commit 1987983 and cotains some innoncent stuff not related to kernel at all.

Okay, I can reproduce here on 17.09.2281.b4a0c011e81 (Hummingbird) (aka latest 17.09).
I'll investigate a fix.

Fix: https://github.com/musnix/musnix/pull/58
Let me know if this works for you.

Sort of works. At least kernel compiled successfully. But later compilation process stopped on nvidia module saying it doesn't support PREEMPT_RT. Looks like I have to stop now, because I can't sacrifice the ability to run cuda. Thanks for your help.


[Feature] Implement PR Title Checker workflow

Description
The project would benefit from a PR title checker that ensures conformity to conventional commit prefixes to help maintainer keep the track of PRs
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

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

Assign me @Rakesh9100

No need, please work on other issues @praptisharma28


Partial or maybe full fix of #537

this pull request fixes the initstate when widget.mode.isSelect = true
Fixes issue: #537

@bosskmk any chances of this being included in 5.1 or a hotfix 5.0.5?

It will be added in version 5.0.5.
I've been busy with other things lately and haven't been paying attention to this project.
I will update soon.
thank you

Any date for the release of this fix?

Updated to PlutoGrid 5.0.5.
Thanks for the code contribution.


Error at login

Hi, i installed a new version 1.0.3 an now, i cannot login.

I also did a token refresh but did not fix.

I have a Fairpjone with LineageOS20-20230619-NIGHTLY-FP3 installed (no google services). I used Aurora Store to install Waterfly.

Downloaded it from the other source and works now :D


Replace EditorService AJV Property with Specification API Call

This will require getBaseValidator to be part of the public API.

Resolved in build 100.


Operable area error

Hi

Use:

pixel streaming 2.2.6
react 17.0.2
node 16.13.2

I can't select the text and can only operate the push flow screen.

import React from "react";

// libs
import PixelStreaming from "pixel-streaming";
import Title from "./Title";

export default function Player(props) {
    const refPixelStreaming = React.useRef(null);

    return (
        <PixelStreaming
            ref={refPixelStreaming}
            onLoad={(payload) => {
                // console.warn('loaded', payload);
            }}
            onConnect={() => {
                // console.warn('connected');
            }}
            onRestart={() => {
                // console.warn('onRestart');
            }}
            onError={(payload) => {
                // console.error('error', payload);
            }}
            onClose={(payload) => {
                // console.error('closed', payload);
            }}
            onCommand={(payload) => {
                // console.warn('command', payload);
            }}
            onCallback={(payload) => {
                // console.warn('callback', payload);
            }}
            onProgress={(payload) => {
                // console.warn('progress', payload);
            }}
            autoConnect={true}
            quality={1}
            isDev={false}
            host="http://<IP_ADDRESS>"
            port={80}
        >
            {(payload) =>

{props.children}
                <Title/>

            }
        </PixelStreaming>
    );
}

import React from "react";

import "./Title.css"

export default function Title(props) {

    return (

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum consequat scelerisque elit sit amet
            consequat. Aliquam erat volutpat. Aliquam venenatis gravida nisl sit amet facilisis. Nullam cursus fermentum velit sed
            laoreet.

    );
}

Component Title is the React component where I can't select the text.

@aaronmack
In order for the elements to be clickable, write the parent user-select: all

@aaronmack In order for the elements to be clickable, write the parent user-select: all CSS user-select Property

I can't do anything with the UI, including scroll, drag, click, select, etc. It seems that I can only operate on unreal stream scenes with full screen.
I also tried to add user-select:all, but it doesn't seem to work, this is my project, hope you can get any help, really appreciate it
test-app.zip

@aaronmack
My apologies. Wrong. You need to use pointer-events: all

Problem solved, Thank you very much. Heartfelt.

Great!