text:
Ignore punctuation when calculating link density

When calculating link density, punctuation characters should not count as words.
This could be if a paragraph consists of a single link followed by punctuation such as a full stop.
The punctation could also consist of multiple characters such as an ellipsis.
In that case it should still be regarding as a having a high density of links.

Thanks for this PR! And great catch. However I have a few questions:
How will this affect foreign languages? The method you are using inspects if the word is alphanumeric chars only via isalnum. u'字'.isalnum() evaluates to True, which is good but we should have unit tests.
Can you add unit tests for an example with foreign languages and also add an example where ignoring punctuation generates a correct summary (while including punctuation yields a bad summary?)
Thanks a lot again for this, great catch!

@codelucas
This should work for all languages in the same way.
As per documentation (https://docs.python.org/3/library/stdtypes.html#str.isalnum) the lookup is done by checking the character's Unicode class. Any kind of digit or letter, defined as such in Unicode, would therefore be regarded as alpha-numeric by isalnum().
The code performing the lookup can also be inspected here: https://github.com/python/cpython/blob/1fe0fd9feb6a4472a9a1b186502eb9c0b2366326/Objects/unicodectype.c#L291.
I will try to dig out the example that caused me to create this patch and add unit tests soon.

Thanks for this!

authors: codelucas krzd

repo: codelucas/newspaper


text:
Vim mode's defineEx()'s documentation says prefix is optional, but it's really not

Here is the defineEx function:
  defineEx: function(name, prefix, func){
    if (name.indexOf(prefix) !== 0) {
      throw new Error('(Vim.defineEx) "'+prefix+'" is not a prefix of "'+name+'", command not registered');
    }
    exCommands[name]=func;
    exCommandDispatcher.commandMap_[prefix]={name:name, shortName:prefix, type:'api'};
  },

Nothing in there makes prefix optional.
I guess you want something like
if (arguments.length == 2) { func = prefix; prefix = name }
at the top.

Oops. I've made the prefix optional, but you still need to pass in undefined.

Thank you for your quick attention to this issue.  I think your solution is suboptimal, at least with respect to the documentation of defineEx():

defineEx(name: string, ?prefix: string, fn: function(cm: CodeMirror, ?params: object))
Defines an Ex command, and maps it to :name. If a prefix is provided, it, and any prefixed substring of the name beginning with the prefix can be used to invoke the command.

Everywhere else in the documentation, an optional parameter could just be omitted, not set to undefined.  I think the check of arguments.length that I mentioned earlier would be a better solution.  That said, there certainly may be other constraints of which I am not aware, so certainly please do as you see fit.
I also note that functions in the CM documentation with optional arguments in the middle of the arglist are rare; the few I could find are all in the Vim API.
Thanks again for your time!

Everywhere else in the documentation, an optional parameter could just be omitted, not set to undefined. I think the check of arguments.length that I mentioned earlier would be a better solution. That said, there certainly may be other constraints of which I am not aware, so certainly please do as you see fit.

That's not entirely true. If there is more than 1 optional parameter, and you want to set the second optional parameter, the first can't be omitted. You either need to pass in a value or undefined. I very much dislike method overloading in general, and fake overloading by omitting parameters in Javascript kind of just makes me cringe.
That said, the Vim API is a bit poorly designed to that respect. Unfortunately, the methods were added over time and all have existing usages. I only recently managed to document them. I will look into making the API cleaner in the next major release, but for now I can't tweak the order of arguments.
I can, however, revert my last commit and instead update the documentation to say that the prefix is required, if you prefer.

That's not entirely true. If there is more than 1 optional parameter, and you want to set the second optional parameter, the first can't be omitted.

That's a good point, and not one I'd considered.  Sorry about that.

I only recently managed to document them.

Thank you for doing that, by the way!

I can, however, revert my last commit and instead update the documentation to say that the prefix is required, if you prefer.

Thank you for the offer.  You're the maintainer, you should do as you think best.  But if you're asking me, and apparently you are :) , I'd say keep your last commit and update the documentation to say you can pass any falsy value (or whatever's actually appropriate; I know in documentation you have to consider all the angles, which might not be apparent to me (like in your point above :)) for the prefix to default it to being the same as the command name.

That sounds fine too. Updated in fbd336f.

Awesome.  Thanks!

source: gharchive/issue

authors: mightyguava theclapp

repo: codemirror/CodeMirror

license: MIT

license_type: permissive

license_source: github-api


text:
Feature request: Coq support

It'd be nice to have Coq support in CodeMirror, as it will benefit downstream projects like BoostNote [1].
[1] https://github.com/BoostIO/Boostnote/issues/1906

We're not adding more modes to the main distribution—the way to go would be to implement it yourself and distribute it separately. See the Elixir mode for an example.

authors: ksqsf marijnh


text:
Hi

hi, can u give me the 3D model index of the 3DMM

Are you asking for the indices I gathered from the surrey face model which map to my 13 additional landmarks? You can find them here: https://github.com/codeniko/eos/blob/81-points/share/sfm_indices

authors: codeniko zhoushiwei


text:
Question about cuda version

Greetings! I wanna ask a question that pytorch1.10.1 can only support cuda 10.2 and 11.3 on the offcial website , will there be an error for it ?

Hi, @nemo0526 ,
We didn't encounter version incompatibility problem. The basic environments such as pytorch and cuda we use are based on nvidia's pytorch image. The pytorch version inside is not a release version, but a github commit version (https://github.com/pytorch/pytorch/commit/3fd9dcf). You can see the specific base environment at the this link: https://docs.nvidia.com/deeplearning/frameworks/pytorch-release-notes/rel_21-09.html#rel_21-09
Kind regards

Thanks for your comment!! However, I got an error when establishing the container you offer . It says " The NVIDIA Driver was not detected.  GPU functionality will not be available.",but my driver on nvidia-smi is well to be detected , have you met this kind of problem?

,but my driver on nvidia-smi is well to be detected , have you met this kind of problem?

Hi, we haven't met this problem. Are you using WSL in windows? You can use the following code to verify whether CUDA is available.
import torch
print(torch.version.cuda)
print(torch.cuda.is_available())

I'm so sorry that the code you give can detect the cuda , the problem isn't solved .

It should be OK that driver version >= 470.57.02. I didn't make it clear in my last reply. You should run this code in the docker container, and if no errors are reported, I think it should be possible to run our program in this container.
But, we haven't tested our container and program on WSL2. The reason for this WARNING may be that NVIDIA's container mistakenly thinks that there is no NVIDIA driver in WSL2 when it starts to check, but the driver and CUDA is actually available.


text:
Enable 404 due to page missing due to scrivito err

やりたい事
404 のエラーページが表示されてなかったので、表示が行えるようにパス指定した。(関連 #1268 #1269)

早速の対応ありがとうございます！マージしますね 🛠💨✨

source: gharchive/pull-request

authors: nanophate yasulab

license: mit

license_source: bigquery


text:
Communication to zoom attendees

This issue will have communication that has been sent to those attending via zoom.

Confirmation and software installation
Dear {first_name},
We're contacting you because you registered for the event {event_title}.
If you are getting this message, you have had preliminary acceptance to the CodeRefinery workshop.  In order to finalize, you need to confirm that you can attend.  Please do this immediately via this link below, the deadline is Wednesday at midnight (24:00) CEST. Check the confirmation box and save (also give info on your operating system and academic discipline, this will only be used for assembling the breakout rooms). If you don't, you may be moved to a "Livestream only" registration to make room for others:
{link}
If you know you can not attend, please withdraw your registration, or change it to type="Livestream" using the same link and you will keep getting emails and can watch what you would like.
The workshop begins in one week.  It is very important that, before then, you

Take care of software installation (https://coderefinery.github.io/installation/)
Check the rest of the requirements here: https://coderefinery.github.io/2021-05-10-workshop/requirements/
Come to one of the pre-workshop installation times if you have any difficulties with software installation (5 may and 6 may at 13:00 CET): https://coderefinery.github.io/2021-05-10-workshop/#schedule

If you have any questions, please contact us.  You will hear more from us soon (especially exercise leaders, for the exercise leader training).
You can view your registration details on this page:
{link}
Best regards
Richard Darst

CodeRefinery: Reconfirm registration, Zoom link for installation session
Dear {first_name},
We're contacting you because you registered for the event {event_title}.  We need you to be aware of:
Confirming registration, if you haven't done so yet
Software installation and the Zoom link for the installation help session

Confirmation. If you have not confirmed your attendance yet, please do so now via this link:
{link}
You must go to that link, make sure to check the confirmation box, then select operating system and academic discipline, then save. If you don't confirm, then we can't plan breakout rooms properly, which affects everyone.  You will likely be moved to livestream-only participation.  If you want to withdraw or switch to livestream-only, you can do that via the same link.
Installation help time.  We should re-emphasize how important it is to come with software installed and ready.  The first week uses mainly git, and the second week uses git+the Python environment.  Please follow the installation instructions (https://coderefinery.github.io/installation/).  If you need help, you can ask friends/colleagues, or come to our installation session, as seen in the schedule (https://coderefinery.github.io/2021-05-10-workshop/#schedule). You really need to do this and the verification, with a large course there isn't much time to solve problems and catch up.  The Zoom information for the installation session is:
https://-----
ID/password: --- / ---
You can view your registration details on this page:
{link}
Best regards
Richard Darst

Coderefinery: waitlist confirmation and software installation
Dear {first_name},
We're contacting you because you registered for the event {event_title}. We would like you to be aware of:
Confirming attendance if you would like a spot on the waitlist.
Software installation

Confirming attendance.  If you would like a spot in the zoom if we have space, please do these steps: Open the link below, click "Modify", and you will find a "confirm attendance" checkbox.  Please set that, as well as operating system/academic discipline.  If we have space, we will accept you.
Software installation.  We should re-emphasize how important it is to come with software installed and ready. The first week uses mainly git, and the second week uses git+the Python environment. Please follow the installation instructions (https://coderefinery.github.io/installation/). If you need help, you can ask friends/colleagues. You really need to do this and the verification, with a large course there isn't much time to solve problems and catch up.
If you have any questions, please let us know.
You can view your registration details on this page:
{link}
Best regards
Richard Darst

Coderefinery: how to confirm registartion
Dear {first_name},
We're contacting you because you registered for the event Online CodeRefinery workshop May 10-12, 18-20.
I'm sorry for the repeated emails, but I wasn't very clear in my previous message about how to confirm.  "Your registration has been completed" is not enough.  Go to the link:
{link}
and click "Modify", then the "I confirm I will attend" checkbox and other fields should appear.  Remember to save by clicking "Modify" at the bottom.
You can view your registration details on this page:
{link}
Best regards
Richard Darst


text:
Make lesson citable

[ ] Create citation.cff
[ ] Ask contributors for ok
[ ] Get DOI
[ ] add action to validate citation.cff?

Working on it in citation branch, current citation looks like:
@software{CodeRefinery_and_Bast_CodeRefinery_Documentation_lesson_2023,
author = {{CodeRefinery} and Bast, Radovan and Wikfeldt, Kjartan Thor and Rantaharju, Jarno and Darst, Richard and Wittke, Samantha and van der Burg, Sven and Razick, Sabry and Rasel, Annajiat Alim and Negru, Stefan and Lindi, Bjørn and van Vliet, Marijn and Orozco, Luisa},
license = {CC-BY-4.0},
month = aug,
title = {{CodeRefinery Documentation lesson}},
url = {https://github.com/coderefinery/documentation},
version = {1.0.0},
year = {2023}
}
Authors are currently ordered as they are ordered in github Contributors, only few contributors are not added as authors as they only did a typo fix or other small thing (they will still be asked if they think it is fair).

CodeRefinert should maybe be removed from authors?

Version: Should the version start with 1.0.0 now?

date-released: Together with version, should this be date of the current release, ie the date when the cff is added to main?

Pdf test: (using defaults with make latexpdf of Sphinx): codedocumentation.pdf
Notes:

cannot read svg files

Looks ok otherwise, what do you think?

repo: coderefinery/documentation


text:
Linkoeping 11 2017

Some rearrangements and improvements.

Thanks!

authors: Sabryr bast

repo: coderefinery/git-intro


text:
CLI works fine but I can't call read_cas_pdf in code

I am trying to use your library. Followed all steps as listed on your pypi page. But it always shows the error
module casparser has no attribute.
data = casparser.read_cas_pdf('/home/path.pdf', 'pwd') AttributeError: module 'casparser' has no attribute 'read_cas_pdf'
Code:
import casparser data = casparser.read_cas_pdf('/home/path.pdf', 'pwd')
Great work regardless thank you.

Sorry I figured it out, code works great. Keep up the good work!

Thanks! just curious, was it due to any issue with the code? (or is there any need to update the documentation to avoid such errors)

No it wasn't due to your code at all. I used your function read_cas_pdf from a file that was named casparser(stupid move, naming the file same as the library name). So it was giving me the error casparser has no attribute read_cas_pdf.

repo: codereverser/casparser


text:
Today button

What would be the easiest way to achieve "Today" button on/or outside of the component:
https://github.com/chmln/flatpickr/issues/202#issuecomment-235801957
Thank you!

Nevermind, I checked the source code and figured that defaultDate option is not part of options prop, but is a separate prop. Not sure why though.
Not working:
<Flatpickr
        options={{
          defaultDate: value,
          enable: dates
        }}
      />

Working:
<Flatpickr
        defaultDate={value}
        options={{
          enable: dates
        }}
      />

Hm, defaultValue is a prop instead of part of the object because it's assigned to the DOM element. And all of the hooks are props so we can do a little checking on them (because they need to be arrays when dynamically updating them to flatpickr).
I don't believe defaultDate is a prop that we're paying any attention to in this library, so that's weird, but I'm glad you got it working.

I really like the look of this picker, but not having a today/"right now" button feels like a dealbreaker, i'll have to add buttons next to the text fields instead.
It's so ridiculously hard to find libraries that don't depend on jQuery today.

authors: MrBrax jacobmischka vfonic

repo: coderhaoxin/react-flatpickr


text:
Tweaks to Custom Languages section of the README

The README does not explain the contribution language extension point clearly, and references features that do not exist.
I updated it to match what is in the code, which should be extended when those features are added.

Thanks!

Thanks!

authors: lostintangent qix

repo: codespaces-contrib/codeswing


text:
Add invert-option support for GradientBox

REDMINE-17731

Coverage remained the same at 99.208% when pulling 6e1457220152af68083ec0cb17ee864970f61746 on DanielKuhn:Invert-option-support-for-gradient-box into 1c504c623850460ab92e4cc8e28cd182ba6f4bc6 on codevise:master.

authors: DanielKuhn coveralls

repo: codevise/pageflow


text:
Comments flagged as spoilers are visible

For some reason I can see comments flagged as spoilers on this discourse page even though I haven't replied to them, and haven't completed the kata. The issue persisted after reopening and reloading the page.

I checked the comments under a few other katas I haven't completed, but everything worked correctly there.
Edit: as was suggested on gitter, accessing the editor could be the reason for this. I really doubt that I did, but that's probably the only explanation other than something being broken, so it should be checked as well.

According to the data, you viewed solutions at 2019-01-28 10:24:43 UTC and that's why spoiler is not hidden from you.

authors: FArekkusu kazk


text:
Unexpected column widths in diffs

The columns of diff tables have unexpected widths in some cases at least on kata revision pages, not sure about translations.

(https://www.codewars.com/kata/5b609ebc8f47bd595e000627/revisions)
It looks like it happens when the first row of a table with "table-layout: fixed" doesn't have widths set.

Thanks. Yeah, this seems to happen whenever Expand is the first row.
Controlling the behavior of table cells was much tricker than I thought.

I'm not sure how it's done in the modern web, but I think it could be colgroup with cols and widths for col:nth() (or max-width if the table-layout doesn't have to be fixed).

I had to use table-layout: fixed to prevent the row from overflowing.
The change I made for #2547 should work well except for this edge case I forgot to consider...
I'll take a look after some sleep.

The <td> elements containing the code belong to the w-full class which has a width: 100%!important property - disabling it seems to fix the problem. Idk what's causing the issue, but looking into this one might be a good start.

You disabled w-full from everywhere by unchecking the property. That resolved this issue by removing the width from the table, but that causes the row to overflow again.
Removing w-full class from td doesn't fix it.

I think I found a fix. I'll deploy it soon.

Deployed

authors: FArekkusu error256 kazk


text:
CW-310: No honor for referrals

Describe the bug
I seem to be getting no honor from my referrals.
The people in question confirmed their emails and have finished some Katas.
My username is MIC132
I don't miss those points too much, but it's quite clearly a bug unless I'm missing something major.
To Reproduce
Go to my profile and check honor
https://www.codewars.com/users/MIC132
Expected behavior
I should receive 3 honor per referral up to 5 and then 1 per (according to what's on the site)
Thus I should have 9 referral honor.
Screenshots

Browser
If applicable, please provide your browser information.

OS: Windows
Browser: Vivaldi
Version: 5.6.2867.62

This issue has been escalated to the Codewars engineering team, we hope to have a fix for this issue soon.

Hi @MIC132, this issue has now been resolved, and I'm happy to inform you that your referral points have been updated on your Codewars account. Thank you for flagging this issue for us.


text:
Write a C# program to find digital root of a number

Description
Write a C# program to find digital root of a number
Digital root of a number is the recursive sum of its digits until we get a single digit number.
Input  : 1234
Output : 1

How to contribute

Save the solution in program/FindDigitalRootOfANumber.cs file
Add FindDigitalRootOfANumber.cs file in find-digital-root-of-a-number folder

!assign

Hey @LukasMikolaj,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)

repo: codinasion/program


text:
Write a C program to convert string to uppercase

Description
Write a C program to convert string to uppercase
Input  : "Hello World"
Output : "HELLO WORLD"

How to contribute

Save the solution in program/ConvertStringToUppercase.c file
Add ConvertStringToUppercase.c file in convert-string-to-uppercase folder

I don't need to make a new PR right? I accidentally made the PR before using !assign.

I don't need to make a new PR right? I accidentally made the PR before using !assign.

No, you don't
But please make sure that you comment !assign on the issue before you raise the PR, to prevent any conflict 👍🏻


text:
Added a todo-list maker to 00_Utilities coded in rust

this helpful program generates a markdown formatted todo list, here's a snippet of its output:
...
rust

01_Acey_Ducey✅
02_Amazing✅
03_Animal⬜
04_Awari⬜
05_Bagels⬜
06_Banner⬜
07_Basketball⬜
08_Batnum⬜
09_Battle⬜
10_Blackjack✅
11_Bombardment⬜
12_Bombs_Away⬜
13_Bounce⬜
...

attached, is the todo list as of the time of posting this message
todo.md
e

fun facts:

only 4 of the games have been ported to pascel, making it easily the least popular language in this repository, half as popular as the next least ... vbnet
all but one of the games have been ported to javascript, making it easily the most popular language in this repository

repo: coding-horror/basic-computer-games

license: Unlicense


text:
Establishing connection to TabNine Cloud...

please complete the following information:

OS version: Mac Big Sur 11.2.3
Editor: Atom
Editor version: 1.55.0
Programming language: vue
TabNine extension version: 3.0.2
Engine version (could be located within Tabnine Hub): 3.3.96-29

Issue Details:
I have signed up to TabNine Cloud, enabled it, and all I get in the editor suggestions is "Establishing connection to TabNine Cloud..."
I checked if it was my router blocking the connection, but it's not.
Do you know what is causing it not to connect?
:octocat:

Hi
Are you working from behind a proxy?

I think we will need some logs. Can you please contact our support at: support@tabnine.com

Even though I didn't get any response/feedback from support@tabnine.com, the issue resolved itself since the new updates to TabNine :octocat:

authors: ckhatton shaiahr

repo: codota/TabNine


text:
Add failure table reset for each test

Closes #9.

Tested on macOS 13.4 and it works.

Tests pass and fail correctly on Windows 10.

repo: codylico/reedkiln


text:
iOS compatibility issue

Current Cofacts's use of Object.fromEntries breaks iOS 11.1 / Safari 11

It even doesn't work on iOS 12 / Google Chrome:

Previous analysis of mobile browser versions:
https://g0v.hackmd.io/@mrorz/rksKX45D8#LIFF-compatibility
Compatibility:
https://caniuse.com/#feat=mdn-javascript_builtins_object_fromentries
We should target the following versions:

Android: Chrome mobile 52.0.2743.98 to cover 99% of sessions
iOS: iOS version 10.3 to cover 99% of sessions

Related xpress polyfill: https://github.com/zloirock/core-js/blob/v3.6.5/packages/core-js/modules/es.object.from-entries.js

repo: cofacts/rumors-site


text:
Adding support for docker provider.

Hi,
Are there plans to add docker provider support or is this available already and I have missed it? I tested and got the following configuration working so that the container could be accessed from my local host with the alias on the default port:
config.vm.network "forwarded_port", guest: 8080, host: 80
config.vm.network "private_network", ip: "127.0.0.1"
config.hostsupdater.aliases = ["blah"]
The current version of docker updates the container IP on commands like reload and up so static IP is does not work. I was thinking that having the plugin update the host file with the new docker IP. The work around above which limits me to having only one alias to the default web port. Is there interest in adding this functionality?
Vang

@mtbvang this is merged and added as of version 1.1.0

authors: cgsmith mtbvang

repo: cogitatio/vagrant-hostsupdater


text:
Tests on Travis fail

I'm not sure why. Until Nov 10 it was ok, but now it doesn't pass the tests on Travis, even though the all tests  are pass in local.
FATAL ERROR: MarkCompactCollector: semi-space copy, fallback in old gen Allocation failed - JavaScript heap out of memory

It seems that  mongodb-runner heap out of memory. I've changed the memory size of Node, but it didn't work 😢

efe328e37aa0f6fe609d06f0c8a31c17c571f179: --max_old_space_size=4096
48129e93fc9a38fb0c77831c216acd8c71b05fb2: --max_old_space_size=2560
f5e7f079490a6c1e06f8179c95c6bcf88cbf5fd0: --max_old_space_size=2048
cf0daebce48836479ad8af75f94146c735bb7dab: --max_semi_space_size=16 --max_old_space_size=1024 --max_executable_size=512
f5e7f079490a6c1e06f8179c95c6bcf88cbf5fd0: --max_semi_space_size=2 --max_old_space_size=256 --max_executable_size=192

Let's go with CircleCI. Moving has been done. 2f7e7dbbb946d67a9b1ddb91dca7b1c00629f643

repo: cognitom/momy


text:
fix unit tests again

too many const pointer updates to u16map - fix compiler highlighted issues

I rebuilt the adt unit tests with sources from your branch. Build and tests are working 100%

authors: cogu sander-visser

repo: cogu/adt


text:
client_name parameter to allow applications to identify themselves

As requested by @egrefen

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

I'll let @mkozakov have a look rather than merge myself.

authors: CLAassistant egrefen sanderland

repo: cohere-ai/cohere-python


text:
Snapshot: fix conversations with tools

Thank you for contributing to the Cohere Toolkit!

[ ] PR title: "area: description"

Where "area" is whichever of interface, frontend, model, tools, backend, etc. is being modified. Use "docs: ..." for purely docs changes, "infra: ..." for CI changes.
Example: "deployment: add Azure model option"

[ ] PR message: Delete this entire checklist and replace with

Description: a description of the change
Issue: the issue # it fixes, if applicable
Dependencies: any dependencies required for this change

[ ] Add tests and docs: Please include testing and documentation for your changes

[ ] Lint and test: Run make lint and make run-tests

AI Description

This pull request makes changes to three Python files: conversation.py, tool.py, and snapshot.py.
Summary

The messages and files fields in the Conversation class are now optional and can be of type List[Message] or Optional[List[Message]].
The Conversation class now includes a new field called text_messages, which is also optional and can be a list of messages.
The ToolCall and ToolCallDelta classes in tool.py have been updated to include a Config class with the attribute from_attributes set to True.
The create_conversation_dict function in snapshot.py has been modified to accept a ConversationModel object instead of a Conversation object as its parameter.

Details
conversation.py

The messages and files fields in the Conversation class are now optional and can be of type List[Message] or Optional[List[Message]].
A new field, text_messages, has been added to the Conversation class, which is also optional and can be a list of messages.

tool.py

The ToolCall and ToolCallDelta classes now include a Config class with the attribute from_attributes set to True.

snapshot.py

The create_conversation_dict function now accepts a ConversationModel object instead of a Conversation object as its parameter.

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

Project coverage is 86.11%. Comparing base (9125660) to head (6bed32b).
Report is 5 commits behind head on main.

Files
Patch %
Lines

src/backend/services/snapshot.py
75.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #350      +/-   ##
==========================================
- Coverage   86.46%   86.11%   -0.36%
==========================================
  Files         178      178
  Lines        6873     6934      +61
==========================================
+ Hits         5943     5971      +28
- Misses        930      963      +33

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

authors: codecov-commenter lusmoura

repo: cohere-ai/cohere-toolkit


text:
Repo Transfer Request: colcon-clean

Request Description
I've authored a colcon extension named colcon-clean to introduce a new clean verb to the colcon CLI:

An extension for colcon-core to clean package workspaces. Enables cleaning of various colcon paths, such as build or install folders, for either the entire workspace or for selected packages with advanced path globing options. In conjunction with colcon-package-selection, this extension can help maintain hygienic build environments while leveraging persistent workspaces for caching by allowing users to finely remove stale artifacts, preserving what can be cached during software development. For example, when pulling various changes into a local workspace to review pull requests, this extension can be used to wipe only the build and install paths for affected packages, ensuring subsequent builds are not cross contaminated from previous jobs.

The repo, demo, and talk for this extension can be viewed here:

https://github.com/ruffsl/colcon-clean
https://gist.github.com/ruffsl/b2b567995810c69866221f659d52e71e
https://vimeo.com/649647161/5b0c278e6c

Could this extension be transferred to the colcon org and be slated for release?
Additional Notes
This relates to some long standing tickets, including:

https://github.com/colcon/colcon-core/issues/37
https://github.com/ms-iot/vscode-ros/issues/554
https://github.com/colcon/colcon-core/issues/213

The extension's release was previously blocked in debian, but has since be resolved:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002306

This extension is already being used in the wild:

https://github.com/ros-planning/navigation2/pull/2399
https://discourse.ros.org/t/experiences-with-ros-2-on-our-robots-and-what-we-learned-on-the-way/26637

From what I can tell, we will only be able to build a debian for Jammy, which is the only supported Ubuntu version where python3-scantree is released: https://packages.ubuntu.com/search?keywords=python3-scantree&searchon=names&suite=all&section=all

Indeed. While I manage to upstream some python dependencies into the recent release of debian, we'd have to packing and host those in the ros apt repo if we'd want to backport these extensions to prior distros. That said, I'm unsure of the colcon version differences between distros, or if there would be any API breaks.

I don't want to sound rude or anything. But are there any plans here for what happens next?
It's hard for me to understand why, after several years of development, colcon still can't have a "clean" command. A feature that at least any other buildtool that I've heard of has. Hopefully, the problem cannot be any dependencies on some python library?

I started reviewing the extension last week. I'm on vacation for the next week, but I can take a look after that.
You are 100% able to install the extension from pip right now.

Thanks for the update.
I know that I can install the extension via pip. Maybe it's just me, but mixing apt-installed packages with pip extensions sounds dangerous to me. Also, I would argue that clean should be a basic feature of colcon and come pre-installed (or at least with colcon-common-extensions). Even if typing some rm command doesn't seem that complicated, clean offers a certain extra comfort.

Maybe it's just me

I think that this is part of the equation worth focusing on. Colcon itself, by design is not meant to be a kitchen sink system which builds in everything anyone could possibly want, instead it's built ground up as an extensible system.
To me, colcon is not meant to be "universal" like a black hole absorbing everything in its gravitional pull but universal like interlocking brick toys, allowing its users to build exactly the thing they need for a given situation.
Right now there's no set criteria for what gets included in colcon-common-extensions and I expect it will always be at the discretion of the maintainers of that package, but what you consider essential intersected with what everyone else considers essential would eventually encompass every available colcon extension. If colcon-common-extensions doesn't cover the cases you want, it's entirely possible for you to create your own similar metapackge that includes your preferred colcon extensions. I recognize that right now this is stymied by colcon-clean not yet being published in the colcon apt repositories but this is something that we'll hopefully resolve soon.

@cottsay , any remaining topics to review before releasing this extension?

[x] Fix declared target dependencies
[x] Port CI to colcon/ci

[x] Fix extension for windows

[x] Max out code coverage

Should I now transfer ownership to the colcon github org?

This one is good to go. If it won't let you do it, grant me 'owner' on the original repo and I'll transfer it.

@ruffsl, if you're ready, I'd like to transfer this extension into the colcon org now.

@ruffsl, if you're ready, I'd like to transfer this extension into the colcon org now.

Done! If you could add me back to the repo, that'd also cool.

Is this closed now or not?

The package still needs to be tagged and released.

This package has been released: https://github.com/colcon/colcon-clean/issues/31#issuecomment-1347186325

authors: Niknu cottsay kledom nuclearsandwich ruffsl

repo: colcon/colcon-core


text:
Update setup.cfg patch to account for churn and whitespace

The setup.cfg.patch appears to have been created against a version of setup.cfg that used tabs. There has also been a small amount of churn in setup.cfg since the patch was created.
The patch can currently be applied by ignoring whitespace and allowing fuzz, but it is easy enough to update the patch to get a clean application.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #115   +/-   ##
=======================================
  Coverage   78.17%   78.17%
=======================================
  Files          50       50
  Lines        2831     2831
  Branches      478      478
=======================================
  Hits         2213     2213
  Misses        593      593
  Partials       25       25

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 5c91ead...7d99beb. Read the comment docs.

When creating the Debian package with ros_release_python the current patch file works as is. Have you tried to use the modified file from this PR together with creating a Debian package?

@cottsay Friendly ping.

My lack of knowledge in Debian packaging shows here. At some point, setup.cfg is getting re-formatted and dropping the comments. I was hoping to re-use the patch, but it doesn't appear that is the right thing to do if it expects debian-specific reformatting to occur prior to application.
Good call pushing back here :)

authors: codecov-io cottsay dirk-thomas


text:
Add mistral models.

Add ability to use mistral models. @coleam00

Wonderful - thank you @ArulGandhi!

So happy to contribute! Just a young dev who found this and actually worked on something with some1 for once. You're my inspiration bro! 😁😁😁

@ArulGandhi That means a lot - thank you! Nice work!!


text:
Twilio Voice to Text Implementation?

Hey guys. Really appreciate the project. I'm really new to Whisper and Python but have a fair amount of coding background in other languages. Wondering if you could provide any strategy ideas or an outline on the best way to approach the below.
I've got an existing websocket server implementation that accepts a websocket connection from Twilio
The websocket media messages look like this:
{
 "event": "media",
 "sequenceNumber": "4",
 "media": {
   "track": "inbound",
   "chunk": "2",
   "timestamp": "5",
   "payload": "no+JhoaJjpzSHxAKBgYJDhtEopGKh4aIjZm7JhILBwYIDRg1qZSLh4aIjJevLBUMBwYHDBUsr5eMiIaHi5SpNRgNCAYHCxImu5mNiIaHipGiRBsOCQYGChAf0pyOiYaGiY+e/x4PCQYGCQ4cUp+QioaGiY6bxCIRCgcGCA0ZO6aSi4eGiI2YtSkUCwcGCAwXL6yVjIeGh4yVrC8XDAgGBwsUKbWYjYiGh4uSpjsZDQgGBwoRIsSbjomGhoqQn1IcDgkGBgkPHv+ej4mGhomOnNIfEAoGBgkOG0SikYqHhoiNmbsmEgsHBggNGDWplIuHhoiMl68sFQwHBgcMFSyvl4yIhoeLlKk1GA0IBgcLEia7mY2IhoeKkaJEGw4JBgYKEB/SnI6JhoaJj57/Hg8JBgYJDhxSn5CKhoaJjpvEIhEKBwYIDRk7ppKLh4aIjZi1KRQLBwYIDBcvrJWMh4aHjJWsLxcMCAYHCxQptZiNiIaHi5KmOxkNCAYHChEixJuOiYaGipCfUhwOCQYGCQ8e/56PiYaGiY6c0h8QCgYGCQ4bRKKRioeGiI2ZuyYSCwcGCA0YNamUi4eGiIyXrywVDAcGBwwVLK+XjIiGh4uUqTUYDQgGBwsSJruZjYiGh4qRokQbDgkGBgoQH9KcjomGhomPnv8eDwkGBgkOHFKfkIqGhomOm8QiEQoHBggNGTumkouHhoiNmLUpFAsHBggMFy+slYyHhoeMlawvFwwIBgcLFCm1mI2IhoeLkqY7GQ0IBgcKESLEm46JhoaKkJ9SHA4JBgYJDx7/no+JhoaJjpzSHxAKBgYJDhtEopGKh4aIjZm7JhILBwYIDRg1qZSLh4aIjJevLBUMBwYHDBUsr5eMiIaHi5SpNRgNCAYHCxImu5mNiIaHipGiRBsOCQYGChAf0pyOiYaGiY+e/x4PCQYGCQ4cUp+QioaGiY6bxCIRCgcGCA0ZO6aSi4eGiI2YtSkUCwcGCAwXL6yVjIeGh4yVrC8XDAgGBwsUKbWYjYiGh4uSpjsZDQgGBwoRIsSbjomGhoqQn1IcDgkGBgkPHv+ej4mGhomOnNIfEAoGBgkOG0SikYqHhoiNmbsmEgsHBggNGDWplIuHhoiMl68sFQwHBgcMFSyvl4yIhoeLlKk1GA0IBgcLEia7mY2IhoeKkaJEGw4JBgYKEB/SnI6JhoaJj57/Hg8JBgYJDhxSn5CKhoaJjpvEIhEKBwYIDRk7ppKLh4aIjZi1KRQLBwYIDBcvrJWMh4aHjJWsLxcMCAYHCxQptZiNiIaHi5KmOxkNCAYHChEixJuOiYaGipCfUhwOCQYGCQ8e/56PiYaGiY6c0h8QCgYGCQ4bRKKRioeGiA=="
 },
"streamSid": "MZ18ad3ab5a668481ce02b83e7395059f0"
}

source: https://www.twilio.com/docs/voice/twiml/stream#websocket-messages-from-twilio
Here is my existing websocket proof of concept that accepts an incoming stream fine and I can transcribe using whisper_cpp after the stream has completed. I'm looking to get realtime transcription working though if possible.

@app.websocket("/stream")
async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    audio_bytes_buffer = bytearray()
    try:
        while True:
            message = await websocket.receive_text()
            packet = json.loads(message)
            if packet["event"] == "start":
                print("Streaming is starting")
            elif packet["event"] == "stop":
                print("\nStreaming has stopped")
                # global accumulated_audio, accumulated_frames
                # accumulated_audio = bytearray()  # Reset accumulated_audio
                # accumulated_frames = []  # Reset accumulated_frames
                break
            elif packet["event"] == "media":
                audio = bytes.fromhex(packet["media"]["payload"])
                audio = audioop.ulaw2lin(audio, 2)
                audio = audioop.ratecv(audio, 2, 1, 8000, 16000, None)[0]
                audio_bytes_buffer.extend(audio)

                # Append the processed audio to the audio buffer for asynchronous processing
                audio_buffer.append(audio)

        # length of audio_bytes_buffer in seconds
        length_in_seconds = len(audio_bytes_buffer) / BYTES_IN_1_MS / 1000
        logger.info(f"audio_bytes_buffer seconds: {length_in_seconds}")

        # Schedule background task for transcription
        asyncio.create_task(execute_transcription(model, audio_bytes_buffer))

        # SAVE COMPLETE AUDIO FILE
        filename = f"99_complete_audio.wav"
        length_in_seconds = len(audio_bytes_buffer) / BYTES_IN_1_MS / 1000
        print(f"Saving {filename} seconds: {length_in_seconds}")
        asyncio.create_task(execute_save_segment(audio_bytes_buffer, filename))

    except Exception as e:
        print(f"WebSocket closed unexpectedly: {e}")

What I'm wondering is what would be the best way to send the live streaming audio data to the server? Would it make sense to create a new websocket server to listen for incoming Twilio stream data and then send that to the TwilioClient somehow. Thinking of modifying the record method to handle incoming audio data instead of recording from the mic. Any feedback would be greatly appreciated.
cheers!

FWIW - I got this working here:
https://github.com/collabora/WhisperLive/pull/42

FWIW - I got this working here: #42

I dont see your twilio file, can you share?

authors: justinlevi privacyrepo

repo: collabora/WhisperLive


text:
add pnpm support

Will there be an option for using pnpm as package manager for volto projects in future?
--> https://github.com/plone/volto/blob/0fcacc2a937002079d3e1bbf7be7eccf4e453468/packages/volto/CHANGELOG.md?plain=1#L50C1-L50C80

Yes, it will be preferred in Volto 18, and is recommended now for installation for contributing to Volto. https://6.docs.plone.org/volto/contributing/developing-core.html?highlight=pnpm

alright, so I look forward to Volto 18 becoming a release version. :+1:

repo: collective/cookiecutter-plone-starter


text:
Core Types for Python/Scikit/Pandas

@ancasarb Can you help describe the changes here?
Transformers
Instead of input_features and output_features transformers' mlinit method now takes the FeatureExtractor object that was used to select the scalars or vectors that we need to transform.
The FeatureExtractor now has an input_shapes element that now get serialized to an mleap bundle.
Feature Extractor

Instead of input features, we now have to specify input_scalars or input_vectors
It now generates an input_shapes element that gets used by the serialize to bundle method of the Transformers

Closing this, as it was included in a separate PR.

repo: combust/mleap


text:
Unitialised string offset error

Hi - on running, I get the following error text:
ErrorException

  Uninitialized string offset: 0

  at app/Commands/EcowittExportCommand.php:172
    168▕     protected function getData($stack, $key)
    169▕     {
    170▕         return collect(data_get($stack, $key))
    171▕             ->mapWithKeys(function ($value) {
  ➜ 172▕                 return [$value[0] => $value[1] ?: null];
    173▕             });
    174▕     }
    175▕
    176▕     /**

  1   app/Commands/EcowittExportCommand.php:172
      Illuminate\Foundation\Bootstrap\HandleExceptions::handleError("Uninitialized string offset: 0", "/home/pi/ecowitt2weewx/app/Commands/EcowittExportCommand.php", [""])

      +1 vendor frames
  3   app/Commands/EcowittExportCommand.php:173
      Illuminate\Support\Collection::mapWithKeys(Object(Closure))

Grateful for your help to resolve.  I'll be the first to admit, I'm a bit out of my depth with PHP

Thanks - that's sorted it perfectly !  One final question - I've got some additional temperature/pressure sensors in my EcoWitt set-up.  Where/how do I need to tweak the code to pull these in?

Hej @Tallboy22,
have a look at https://github.com/comes/ecowitt2weewx/blob/bda227a1a6ec7675af2ffa003164a136405f4fab/app/Commands/EcowittExportCommand.php#L92 the variable $ecowitt contains all your data.
In line https://github.com/comes/ecowitt2weewx/blob/bda227a1a6ec7675af2ffa003164a136405f4fab/app/Commands/EcowittExportCommand.php#L157 I build the export array. Nice and dirty.
You can extend this array with your own data. Feel free to make a PR for your changes so others can participate too.
greetings, J

Thanks - really appreciated

Hej, no I never found some official documentation. Everything is based on my own reverse engineering.
To dump the Ecowitt variable, you can use dump() or dd()
dd($ecowitt); is your friend.

close issue; no response


text:
Renaming issue

If a comic has a series name with a ' - ' in it,  for example 'my comic - series 2' it will strip the - out upon rename

This doesn't sound like a renaming issue it sounds more like a fileparser issue.
When renaming ComicTagger only uses information in the metadata it does not care what the filename is. In other words it only uses the information in the form when you open it. For example in this comic the filename is 鋼の錬金術師 #001,.cbz
when renaming however it will end up as Hagane no Renkinjutsushi #001.cbz as 鋼の錬金術師 is not anywhere on the form.

I'm sorry, upon further testing you are right. It keeps the ' - ' i was confusing it with ripping out the ':'. Is there a way to replace the ': ' in series names with ' - ' in filenames for rename?

It should happen automatically on Windows and you can enable it on macOS and Linux with the Strict renaming option in the rename settings.

No, the app strips it rather than converting it prior to rename, look at what the result will be on the right.

So, it turns out I only do the replacement on the template text not the actual values, I'm working on a fix

Release 1.4.8 has this fixed

authors: WHiZSTA lordwelch

repo: comictagger/comictagger


text:
C3 no internet connection after boot with 3rd party SIM card

Describe the bug
Every time I start the C3, I have no internet (bars). The APN is set ("net"). I use a 3rd party SIM card (Orange Romania).
It was working fine with another SIM card with another carrier (also from Romania). It happened roughly after I changed SIM cards.
The only way I can make it work is going to APN and saving it again, without editing it. I need do this every time I plug my C3.
Provide a route where the issue occurs
b387d7bf0f78af1b|2023-08-31--15-36-35
openpilot version
0.9.4
Additional info
Started happening on sunnypilot (twilsonco fork) and switched to official release3 for this bug report.
I preserved 3 consecutive routes:
b387d7bf0f78af1b|2023-08-31--15-36-35
b387d7bf0f78af1b|2023-08-31--15-41-19
b387d7bf0f78af1b|2023-08-31--15-55-49

Duplicate of #29205

Just to clarify for when #29205 is getting fixed. In my case the APN doesn’t dissapear from the menu. When I go to APN, the APN is already there.
Pressing Save in the APN menu, without editing it, restores the internet connectivity.

@adeebshihadeh how hard you think #29205 is to fix? do you think it could be a “good first issue”? I could try to fix it, if yes. thanks!

Yes it’s likely an easy fix.

https://github.com/commaai/openpilot/pull/30517

authors: adeebshihadeh andiradulescu

repo: commaai/openpilot


text:
RAV4: use stock long for certain newer radars

For certain newer RAV4 vehicles, the radar outputs in a format different from most other Toyota, so use stock longitudinal until full radar parsing support is added. We also need to knock out the radar as it sends the ACC messages
RAV4 fw in PR is from dongle: 825c2be1679633af|2022-04-06--20-24-59

[x] Safety to block ACC messages that don't contain the cancel signal - https://github.com/commaai/openpilot/pull/23969
[ ] Test models route

Here are a few more 2022 RAV4s with the new fws. I don't recall if they're gas or hybrid models, but I suppose it doesn't matter too much since they're on stock long.
https://github.com/alancyau/openpilot/commit/bedeb1bcd4c176f5b9cd57c107fb7c50a9fae05c
https://github.com/alancyau/openpilot/commit/0c5407475ff5643e471258a2e1c8f100f3db65c6
https://github.com/alancyau/openpilot/commit/926b2b7249524b747506942720ba8ea6239b043a

@alancyau definitely need to know if they're hybrids or not so we use the correct gas signal. If you have dongle IDs per each fw version, that'd be a great help

Would this include 2020 RAV4 Hybrid XLR too ? I have one, so if you need anything tested just let me know. I tried testing the branch earlier today but I had an error saying vehicle ID couldn't be found or something like that. Just let me know. Thanks Shane!

Your car should already be supported @aolin480, is it not?

Ah okay. Yeah that's what I was wondering. If this is for the newer RAV4 then it's all good, just didn't know if it unlocks something with RAV4's in general. Thanks for clarifying!

Yes this is the PR to add support, the website will be updated soon

authors: alancyau aolin480 sshane


text:
Tesla: explicitly copy signals to forward

split from https://github.com/commaai/openpilot/pull/28020

new tesla label!


text:
typo

typo

cheers

authors: espes rocfig

repo: commaai/research


text:
📦 NEW : Blockchain ---> Job-Boards

Hi, I wanted to add a new job hunting website in the /Blockchain ---> Job-Boards folder. Can I create a PR ?
Thanks :)

Just do it already man. The PR will be reviewed regardless.

Hey @ishvinder-singh as @cosmicqbit you can go ahead with the PR. We make sure to review every PR

repo: commclassroom/roadmaps


text:
Existing file check algorithm uses SHA1 encryption

ShareActivity uses getSHA1 method of Utils class to generate SHA1 of file from input stream. Given the vulnerabilities exposed with SHA1(not sure how critical it is in our use case) we should consider moving to SHA2 for our file matching algorithms. Both the server and client will have to incorporate these changes if we go forward with it.

Yes, and we will have to wait for MediaWiki to migrate: https://phabricator.wikimedia.org/T158986 (and when MediaWiki migrates to another hash, we would like to be not left behind).

@maskaravivek @whym Hi, both.
It sounds like this has probably been overtaken by events; can we confirm whether SHA2 is now being used, so we can potentially close this?
Thanks,
Chris.

authors: chrisdebian maskaravivek whym

repo: commons-app/apps-android-commons


text:
Benchmarks with other parsers

We should make sure we are not leaving some performance on the table compared to other solutions!

These first naive tests are just counting divs and gumbocy is (purposely) ignoring a lot of the html, so the results are to be taken with a grain of salt. Still, lxml is 2x faster (but not HTML5-compilant), and all the other Python alternatives range from 7x to 20x slower.
benchmark_gumbocy: 0.555 seconds
benchmark_gumbo_bs3: 8.960 seconds
benchmark_lxml_raw: 0.254 seconds
benchmark_html5lib_bs4: 9.977 seconds
benchmark_htmlparser_bs4: 3.534 seconds

repo: commonsearch/gumbocy


text:
COMP: Remove UTF-8 BOM from source files

https://github.com/commontk/CTK/issues/1213
https://discourse.slicer.org/t/failed-to-build-slicer-cause-the-ctk-build-exited-with-code-1/37872
@lassoan

For now, the easiest is to keep using ASCII in all CTK source files. If there is a good reason to change this in the future then it should be changed for all source files.

To enforce this, is there a check we could add to https://github.com/commontk/CTK/blob/master/.pre-commit-config.yaml ?

For now, the easiest is to keep using ASCII in all CTK source files. If there is a good reason to change this in the future then it should be changed for all source files.

To enforce this, is there a check we could add to https://github.com/commontk/CTK/blob/master/.pre-commit-config.yaml ?

I am not familiar with the pre-commit check infrastructure. But if possible we could run a script that checks the first 3 characters of a file, i.e. something like this:
# Read the first three bytes of the file
BOM=$(head -c 3 "$FILE" | xxd -p -c 3)

# Check if the BOM matches the UTF-8 BOM (EFBBBF)
if [ "$BOM" = "efbbbf" ]; then
  echo "The file '$FILE' contains a UTF-8 BOM."
else
  echo "The file '$FILE' does not contain a UTF-8 BOM."
fi

Any non-ASCII character (code > 127) might cause trouble, such as accented characters. Also, we should only check source code files.
I've got Copilot generate this code, does this look good?
# Get the list of staged source files
source_files=$(git diff --cached --name-only -- '*.cpp' '*.h' '*.in' '*.cmake' 'CMakeLists.txt' '*.py')

# Check for non-ASCII characters in the staged source files
non_ascii_files=$(echo "$source_files" | xargs grep -P -n "[^\x00-\x7F]")

if [ -n "$non_ascii_files" ]; then
  echo "Error: The following source files contain non-ASCII characters:"
  echo "$non_ascii_files"
  exit 1
fi

authors: Punzo jcfr lassoan

repo: commontk/CTK


text:
POC Assessment Config

POC Assessment Config

Created new PR. This one became hell to rebase.


text:
Convert logging.init_app to use dictConfig

https://dluhcdigital.atlassian.net/browse/FPASF-104
Change description
This allows each app to adjust the log configuration if needed. It moves us from an imperative log configuration flow to a declarative one - we just say what we want in a readable dict, and then logging sets it up as specified. It should be easier to debug logging issues and understand exactly what loggers we're setting up.
This will initially be used by the data-store to grab the default logging config and inject it into our new celery worker, as celery's logger needs to be set up separately (ie not via the flask app).

[x] Unit tests and other appropriate tests added or updated
[x] README and other documentation has been updated / added (if needed)
[x] Commit messages are meaningful and follow good commit message guidelines (e.g. "FS-XXXX: Add margin to nav items preventing overlapping of logo")

Sorry @NarenderRajuB - had left half a test in and a misleading commit message - just fixed that up.

Does this break the existing client interface? If so should we make a major version bump to indicate?

No, it doesn't / shouldn't.

authors: gidsg samuelhwilliams


text:
how to attach the tool with from compas_robots.viewer.scene.robotmodelobject import RobotModelObject? robot_object.attach_tool_model(tool_model) robot_object.draw_attached_meshes() robot_object.draw_visual(),Not effective

tool_model=...
robot_object: RobotModelObject = viewer.scene.add(model, show_lines=False, configuration=configuration)
Attach the tool
robot_object.attach_tool_model(tool_model)
robot_object.draw_attached_meshes()
robot_object.draw_visual()
Not effective？

Hello, I'm not sure I understand your issue.
Are you asking why there is the code pattern of using the Scene class?

There is no example illustrating how to use robot_object.attach_tool() and display it on the Viewer.screen below, nor how to change the joint and have the end follow the changes. The example below only displays the robot, but not the tool attached to the robotic arm. Could the official provide a corresponding example that displays the robotic arm and end claw on the Viewer, without necessarily using ROS or Rhino for display.
Can you provide an example related to attach_tool and demonstrate how to display and update joint changes in the Viewer, ensuring that the tool at the end follows the changes, without utilizing ROS or other CAD environments。Thankyou very much。
programe:Only Robot is displayed below。
from compas_robots.viewer.scene.robotmodelobject import RobotModelObject
from compas_viewer.components import Slider
from compas_viewer import Viewer
from compas.datastructures import Mesh
from compas.geometry import Frame
from compas_robots import RobotModel
from compas_robots.model.tool import ToolModel
from compas_robots.resources import LocalPackageMeshLoader
import compas_fab
viewer = Viewer()
viewer.renderer.rendermode="lighted"
urdf_filename ='./ur5.urdf'
model = RobotModel.from_urdf_file(urdf_filename)
model.load_geometry(LocalPackageMeshLoader(compas_fab.get("universal_robot"), "ur_description"), precision=5)
configuration = model.zero_configuration()
robot_object: RobotModelObject = viewer.scene.add(model, show_lines=False, configuration=configuration) # type: ignore
viewer.ui.sidedock.show = True
##############attach_tool_model##################
mesh = Mesh.from_stl("./vacuum_gripper.stl")
frame_t = Frame([0, 0, 0.07], [1, 0, 0], [0, 1, 0])
tool_model = ToolModel(mesh, frame_t, connected_to="wrist_3_link")
robot_object.attach_tool_model(tool_model)###TODO not work!!!!
viewer.renderer.update()
##############attach_tool_model##################
def make_rotate_function(index):
def rotate(slider: Slider, value: int):
config = robot_object.configuration
config.joint_values[index] = value / 360 * 2 * 3.14159
robot_object.update_joints(config)
return rotate
for i, joint in enumerate(robot_object.configuration.joint_names):
rotate_function = make_rotate_function(i)
viewer.ui.sidedock.add(Slider(title=joint, starting_val=0, min_val=-180, max_val=180, step=1, action=rotate_function))
robot_object.update_joints(robot_object.configuration)
viewer.show()


text:
[verification-helper] timestamps.*.json の内容の拡張

https://github.com/online-judge-tools/verification-helper/issues/77

verify の --output の出力が timestamps.*.json の超絶進化版みたいなもの。
competitive-verifier のコンセプトのひとつなのでもちろん解決済み。


text:
bugfix: Fix "unknown argumet: '-static'" when compiling on Darwin

The code
option(BUILD_SHARED_LIBS "Build shared libraries by default"
  $<PLATFORM_ID:Windows,Darwin>)

doesn't set the option BUILD_SHARED_LIBS to YES on Darwin. I found that it
always return 0.  I tried to use $<IN_LIST> generator but it also returned
0.
Fixes #2

I think that this has been improved upstream, please re-open if the latest CMake still causes issues.

authors: compnerd wanderley

repo: compnerd/swift-build-examples


text:
Use full decompositions in decomposition map

Currently we have a recursive decompose loop to decompose characters until they are no longer decomposable. This requires multiple lookups in the decomposable bitmap and the loop adds to the cost. Instead, we can statically generate fully decomposed sequence for each character and in the run time logic we won't require a recursive loop. This can potentially speed up NFD/NFC normalizations of several languages which involve composed forms (e.g. Devanagari and Japanese).

I tried this idea last week, but did not gain any performance improvements. Full decompositions might get long-ish, maybe it is better to return them as arrays and not as [Char]?..

I removed the recursive decompose altogether to experiment and it does not seem to help at all.

authors: Bodigrim harendra-kumar

repo: composewell/unicode-transforms


text:
Update circe-core, circe-literal, ... to 0.14.3

Updates

io.circe:circe-core
io.circe:circe-literal
io.circe:circe-parser

from 0.13.0 to 0.14.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "io.circe" }
}]

labels: library-update, early-semver-major, semver-spec-minor, commit-count:1

Superseded by #124.

repo: compstak/circe-debezium


text:
cursor next and next_batch usage

Could you please advise on the correct use of next and next_batch with regards to aggregates with batchSize set?
If I set batchSize to 1 and call either of these functions:
defp get_batch(cursor, items \\ []) do
  case :mc_cursor.next_batch(cursor) do
    :error ->
      :mc_cursor.close(cursor)
      List.flatten(items)
    new_items ->
      get_batch(cursor, new_items ++ items)
  end
end

defp get_items(cursor, items \\ []) do
  case :mc_cursor.next(cursor) do
    {item} ->
      get_items(cursor, [item|items])
    _ ->
      :mc_cursor.close(cursor)
      List.flatten(items)
  end
end

I only get one document back, even if the result would return a lot more with a higher batchSize.

For clarification, I'm using mc_cursor.next_batch on an aggregate cursor.  It seems to work for one batch request, then fail for subsequent ones

Hi, sorry for a delay.
Aggregation cursors don't have complete implementation for now. I hoped the fix I made will cover your usage, but seems that it is not that useful.
cursor and mc_worker need to be changed in order to cursor's next batch trigger request to mc_worker.
I will try to fix it but I am not promising as I am pressed for time right now.
Regards

Okay, thanks for being honest.  This is a bit of a headache for us, but not immediately so.  If this is on your short-term road map, anyway, we will keep an eye out for the update.

Hey @comtihon,
I'm attempting to work on this myself, but was wondering if you'd made any progress?  If so, might be good to set up a branch so we can tackle this together?

Hi @Lazarus404
sorry, I an busy on another project right now.
But I will be very happy if you will create pr, if you have something.
Regards, Val

repo: comtihon/mongodb-erlang


text:
At the end report absolute peak memory (may be with % if really like it)

ATM I see
❯ duct -- ./test_script.py --duration 3 --memory-size=1000
duct is executing ./test_script.py --duration 3 --memory-size=1000...
Log files will be written to .duct/logs/2024.06.06T23.20.47-1211148_
this is of test of STDERR
this is of test of STDOUT
Test completed. Consumed 1000 MB for 3 seconds with CPU load factor 10000.

Exit Code: 0
Command: ./test_script.py --duration 3 --memory-size=1000
Log files location: .duct/logs/2024.06.06T23.20.47-1211148_
Wall Clock Time: 3.3275320529937744
Memory Peak Usage: 0.0%
CPU Peak Usage: 104.0%
duct -- ./test_script.py --duration 3 --memory-size=1000  4.18s user 2.58s system 197% cpu 3.428 total

which is odd -- not sure what 0.0% it is reporting given that 1GB was requested.

I'm happy to switch to absolute amount rather than %, I only used % because thats what smon does https://github.com/brainlife/abcd-spec/blob/master/hooks/smon#L151

Fixed by https://github.com/con/duct/pull/54

duct ./test_script.py --duration 3 --memory-size=1000
duct is executing ./test_script.py --duration 3 --memory-size=1000...
Log files will be written to .duct/logs/2024.06.07T11.21.48-553879_
this is of test of STDERR
this is of test of STDOUT
Test completed. Consumed 1000 MB for 3 seconds with CPU load factor 10000.

Exit Code: 0
Command: ./test_script.py --duration 3 --memory-size=1000
Log files location: .duct/logs/2024.06.07T11.21.48-553879_
Wall Clock Time: 3.376 sec
Memory Peak Usage: 3.1%
CPU Peak Usage: 193.0%

authors: asmacdo yarikoptic

repo: con/duct


text:
Add join criteria to left join query

http://www.concrete5.org/index.php?cID=799144

:+1:  Definitely need that join to be more explicit in order for that to work.

Yes, we need this and condition, otherwise it won't work as expected when $inGroup is false

authors: joe-meyer matt9mg mlocati


text:
Add type concrete5-update in composer.json

This continues the discussion from #2087 now that web/ is gone.
At the moment composer create-project concrete5/concrete5 has the disadvantage of losing the possibility to update concrete5 via Composer and composer require concrete5/concrete5 needs the vendor/ directory to be in the web root to serve the static concrete5 files.
Using the already existing Composer installer type concrete5-update is still not the cleanest solution in my mind, but it has proven to work, we have multiple concrete5 installations running with a custom Composer repository which uses concrete5-update.
One cleaner solution would be to create a Git subtree split of the core to a new repository concrete5-core but that would mean some additional maintenance (ref. Monorepo) and would require a new Composer installer type concrete5-core.
Maybe there are other better solutions?
This is mainly to start the discussion again how to install concrete5 as a dependency with Composer (https://github.com/composer/installers/pull/225 and https://github.com/concrete5/concrete5/issues/3311).

Can you describe what exactly this installer does? What does a project using this installer look like from a file structure perspective?

It installs concrete5 to the directory updates/concrete5/ (ref. Concrete5Installer) instead of vendor/concrete5/concrete5.
Here's what a project using it would look like (see this example concrete5-cms repository, similar to the one from @olsgreen):

application

bootstrap

app.php (Bootstrap files copied from concrete5 repository)
start.php
autoload.php (loading Composer autoloader)

config

update.php (Overriding update.core config)

updates

concrete5 (concrete5 installed via Composer installer)

vendor (Composer directory)
composer.json (requiring concrete5/concrete5)
index.php (Loading the concrete5 dispatcher)

Additionally it allows you to install concrete5 to a web root directory with the following in your composer.json (ref. Custom Install Paths):
{
    "require": {
        "concrete5/concrete5": "^8.0"
    },
    "extra": {
        "installer-paths": {
            "web/updates/{$name}/": ["concrete5/concrete5"]
        }
    }
}

Again, having concrete5 installed in the updates/ folder is not the perfect solution. But unless a subtree split of the concrete5 core (which could be installed to concrete/) exists it's the only solution I can see.

I still don't understand the need for the installer type or the need for the update folder?
There is no difference running concrete from the /vendor directory like in my solution or running it from the /updates directory. I'm a bit loss as to what you're trying to achieve here?
The main benefit can see is being able to leave the vendor directory under the webroot and have concrete5 above?

Two reasons:

There used to be some hardcoded URLs for static files that required concrete5 to be either in concrete/ or updates/*/ - could be that this is not the case anymore with 8.0 if your proof-of-concept is working without problems from vendor/concrete5/concrete5/.

Yes, to be able to leave the vendor/ directory outside the web root. My main motivation for this is security: As it is best practice to have the vendor/ directory outside the web root some library authors might rely on it and include some potentially dangerous code in their library. Not a problem if their code is not accessible but can become a problem if vendor/ is suddenly publicly accessible.

@fabian Point's taken. I still think the core-installer type is a messy answer to the problem.
We know the core is heading towards not requiring itself to be above webroot. So in my opinion, it's going to be better to implement the composer functionality with this in mind.
I saw your point regarding proxying the vendor/concrete5/concrete5 directory, so I've reworked my example to install in the default locations (above webroot) and then automatically add /vendor directory protection via .htaccess for apache. I think this solves vendor directory security for 90% of users but also keeps things clean as there is no need for the core-installer types. Take a look and let me know what you think?

Having the core heading towards running outside of webroot is good news! Is there some kind of commitment from core developers for this?
I don't like the .htaccess being automatically created by the composer.json, but I do like the idea of protecting the vendor dir from being access and only allowing access to vendor/concrete5/concrete5 - admittedly a nice solution!
I agree, using  "type": "concrete5-update" is probably the messiest solution to the problem, so I will close this PR.

authors: KorvinSzanto fabian olsgreen


text:
[ci skip] adding user @primozgodec

Hi! This is the friendly automated conda-forge-webservice.
I've added user @primozgodec as instructed in #8.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #8

@conda-forge/core, can you merge this? The Maintainer of this repo is quite unresponsive. #7 is open for long and I want to work on it.

@conda-forge/core, can you merge this? The Maintainer of this repo is quite unresponsive. #7 is open for long and I want to work on it.

Do you mind sending a PR adding yourself + the changes that you want to make? That will make it easier for core members to merge it without waiting for the maintainers response.

authors: PrimozGodec conda-forge-admin ocefpaf


text:
1.0.0

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter horta

repo: conda-forge/almosthere-feedstock


text:
@conda-forge-admin please add bot automerge

@conda-forge-admin please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/asks-feedstock#8.

authors: CJ-Wright conda-forge-linter

repo: conda-forge/asks-feedstock


text:
Patch ffmpeg 6.0.0 and 6.0.1 for stricter pinning

It seems like the SO name changed
https://github.com/conda-forge/ffmpeg-feedstock/pull/216
Checklist

[ ] Used a static YAML file for the patch if possible (instructions).
[ ] Only wrote code directly into generate_patch_json.py if absolutely necessary.
[ ] Ran pre-commit run -a and ensured all files pass the linting checks.
[ ] Ran python show_diff.py and posted the output as part of the PR.
[ ] Modifications won't affect packages built in the future.

<!-- Put any other comments or information here --!>

i'm not so sure this isneeded anymore, it may have been an error in my grep.

don't


text:
Fix compiling with sanitizers

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

cc @bluescarni

@isuruf Thanks a lot!

authors: bluescarni conda-forge-linter isuruf

repo: conda-forge/ctng-compilers-feedstock


text:
Update for CUDA 12.6.3

xref: https://github.com/conda-forge/cuda-feedstock/issues/54

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:

linter: passed
azure: passed

Thus the PR was passing and merged! Have a great day!

authors: adibbley conda-forge-admin


text:
Update for CUDA12.5.1

xref: https://github.com/conda-forge/cuda-feedstock/issues/36

@conda-forge-admin, please rerender

repo: conda-forge/cuda-nvcc-feedstock


text:
Update meta.yaml

v0.1.1

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: WRKampi conda-forge-linter

repo: conda-forge/extensisq-feedstock


text:
prepare to rename feedstock fenics-basix

this should have been the name, but I didn't know about the metadata when it was merged
I'll merge this and rename the repo once feedstock-outputs has been updated

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

authors: conda-forge-linter minrk

repo: conda-forge/fenics-basix-meta-feedstock


text:
Adding maintainer: @michael-gracie

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged) 0 --> 1
[x] Reset the build number to 0 (if the version changed) NA
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

cc: @michael-gracie

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

authors: conda-forge-linter sugatoray

repo: conda-forge/gslides-feedstock


text:
Fixed inability to build models

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This PR adds the ability for the KIM API conda-forge package to build KIM models from source. This involves adding several compilers and build tools as run requirements and passing their paths to CMake to configure the KIM API. I also added a test for building a model.

But to get it to work on osx_64, instead of using
    - {{ compiler('cxx') }}
    - {{ compiler('c') }}
    - {{ compiler('fortran') }}

which I guess finds the default compilers on the system, is it possible to use some other settings such that it installs other compilers (e.g. gcc suits) and use it?
I completely have no idea of how conda-forge works. So the above guess might make no sense.

I think we’ll need to figure out how this is all meant to be used at run time. I would hope conda has a coherent rational for its environment variable settings across architectures…. It’ll probably require some further digging and comparison of how existing packages are dealing with this issue…RyanOn Dec 6, 2023, at 9:20 AM, Mingjian Wen @.***> wrote:
To get it to work on osx_64, instead of using
- {{ compiler('cxx') }}
- {{ compiler('c') }}
- {{ compiler('fortran') }}
which I guess finds the default compilers on the system, is it possible to use some other settings such that it installs other compilers (e.g. gcc suits) and use it?
I completely have no idea of how conda-forge works. So the above guess might make no sense.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because your review was requested.Message ID: @.***>

I think we’ll need to figure out how this is all meant to be used at run time. I would hope conda has a coherent rational for its environment variable settings across architectures…. It’ll probably require some further digging and comparison of how existing packages are dealing with this issue…

I think all we need to do is figure out how to get CMake to build the KIM API with KIM_API_CMAKE_C_COMPILER set to $ENV{CC}, and analogously for the other compilers. The difficulty is that, if I try the following configuration option:
-DKIM_API_CMAKE_C_COMPILER="\$ENV{CC}", then CMake thinks it is a relative path (because the variable type for the cache variable KIM_API_CMAKE_C_COMPILER is FILEPATH). So I add a leading forward slash, -DKIM_API_CMAKE_C_COMPILER="/\$ENV{CC}", to get CMake to accept it as an absolute path. This works on Linux, because $ENV{CC}=/home/ilia/miniconda3/envs/kim-env-pr/bin/x86_64-conda-linux-gnu-cc or whatever, so an additional leading forward slash doesn't break anything.
On OSX (I'm getting this from the CI logs, since I don't have a Mac, but it seems pretty straightforward), $ENV{CC}=x86_64-apple-darwin13.4.0-clang, so the leading slash makes it look for /x86_64-apple-darwin13.4.0-clang, which is not a valid path. I assume the conda-forge compiler package adds the wherever x86_64-apple-darwin13.4.0-clang is to $PATH, so if we can just get CMake to set  KIM_API_CMAKE_C_COMPILER=$ENV{CC} instead of KIM_API_CMAKE_C_COMPILER=/$ENV{CC} as it stands now, everything would work.

I've taken a look at the CI log, and seems we can have a solution for it.
On linux_64_, the CC and FC environmental variables are indeed a full path (image below).

But on osx_64_, while FC is full path, CC is not (image below). I guess this is the reason why @ilia-nikiforov-umn see the error.

But, as you might have noticed in the images, CC is essentially the same as CC_FOR_BUILD. Similarily, FC is the same as FC_FOR_BUILD. The nice thing is that CC_FOR_BUILD and FC_FOR_BUILD are full path.
So, I believe we can modify build.sh to use **_FOR_BUILD.

I don't think that will work for platforms that are cross-compiled, like
osx_arm64. See the build log here:
https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/837612/logs/24
CC_FOR_BUILD and CC are different compilers here.
On Wed, Dec 6, 2023 at 5:25 PM Mingjian Wen @.***>
wrote:

I've taken a look at the CI log, and seems we can have a solution for it.
On linux_64_, the CC and FC environmental variables are indeed a full path
(image below).
Screenshot.2023-12-06.at.5.12.14.PM.png (view on web)
https://github.com/conda-forge/kim-api-feedstock/assets/10203513/4f26a0aa-2150-41b6-a2cc-5d2968f30c13
But on osx_64_, while FC is full path, CC is not (image below). I guess
this is the reason why @ilia-nikiforov-umn
https://github.com/ilia-nikiforov-umn see the error.
Screenshot.2023-12-06.at.5.15.00.PM.png (view on web)
https://github.com/conda-forge/kim-api-feedstock/assets/10203513/cda20913-763f-46bf-845d-1a82adfbb6d2
But, as you might have noticed in the images, CC is essentially the same
as CC_FOR_BUILD. Similarily, FC is the same as FC_FOR_BUILD. The nice thing
is that CC_FOR_BUILD and FC_FOR_BUILD are full path.
So, I believe we can modify build.sh to use **_FOR_BUILD.
—
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/kim-api-feedstock/pull/18#issuecomment-1843849272,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS2TGGGUAS2TNS5CYH63YBTYID5GJAVCNFSM6AAAAABAIVUVU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBTHA2DSMRXGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Cmake has some tools to find things (files, executables, … I think). So maybe we could use one of those with the value if the environment variable to turn it into a path?Ryan Sent from my iPhoneSEhttps://z.umn.edu/relliottOpenPGP: https://z.umn.edu/relliott_asc (576D4997C4D51D92)On Dec 6, 2023, at 3:02 PM, ilia-nikiforov-umn @.***> wrote:
I think we’ll need to figure out how this is all meant to be used at run time. I would hope conda has a coherent rational for its environment variable settings across architectures…. It’ll probably require some further digging and comparison of how existing packages are dealing with this issue…
I think all we need to do is figure out how to get CMake to build the KIM API with KIM_API_CMAKE_C_COMPILER set to $ENV{CC}, and analogously for the other compilers. The difficulty is that, if I try the following configuration option:
-DKIM_API_CMAKE_C_COMPILER="$ENV{CC}", then CMake thinks it is a relative path (because the variable type for the cache variable KIM_API_CMAKE_C_COMPILER is FILEPATH). So I add a leading forward slash, -DKIM_API_CMAKE_C_COMPILER="/$ENV{CC}", to get CMake to accept it as an absolute path. This works on Linux, because $ENV{CC}=/home/ilia/miniconda3/envs/kim-env-pr/bin/x86_64-conda-linux-gnu-cc or whatever, so an additional leading forward slash doesn't break anything.
On OSX (I'm getting this from the CI logs, since I don't have a Mac, but it seems pretty straightforward), $ENV{CC}=x86_64-apple-darwin13.4.0-clang, so the leading slash makes it look for /x86_64-apple-darwin13.4.0-clang, which is not a valid path. I assume the conda-forge compiler package adds the wherever x86_64-apple-darwin13.4.0-clang is to $PATH, so if we can just get CMake to set  KIM_API_CMAKE_C_COMPILER=$ENV{CC} instead of KIM_API_CMAKE_C_COMPILER=/$ENV{CC} as it stands now, everything would work.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because your review was requested.Message ID: @.***>

Have you tried to replace CC like:
export CC=$BUILD_PREFIX/bin/$CC

I agree that it is not a nice solution but if it works, then we could suggest to the conda-forge team to just update it accordingly. Currently I am not aware of any reason why the Apple compilers are defined without the build prefix.

It appears that specifying file type for the compiler paths on the command line (i.e. -D<var>:<type>=<value> instead of -D<var>=<value>) prevents CMake from messing with CACHE entries of type FILEPATH, allowing me to set the paths to just $ENV{CC} etc. like I wanted.
I am not sure if this is intended -- the documentation is unclear: https://cmake.org/cmake/help/latest/manual/cmake.1.html#generate-a-project-buildsystem:

If the :<type> portion is given it must be one of the types specified by the set() command documentation for its CACHE signature. If the :<type> portion is omitted the entry will be created with no type if it does not exist with a type already. If a command in the project sets the type to PATH or FILEPATH then the <value> will be converted to an absolute path.

To me, this is ambiguous whether the last sentence is meant to apply always, or only when :<type> is omitted, but the functionality appears to be the latter. Maybe I'll ask on the CMake forum if this is intended.
Regardless, I think this is ready to merge, I don't think this will break anything that was already working, and it's passing checks including building the model on all platforms except osx_arm64, which does not run the checks (does anyone know why?)
Maybe someone with an Apple Silicon Mac wants to test it locally?

I think the osx_arm64 build doesn't run checks because it's being cross-compiled, so whatever cloud resource is building it can't actually run it.
@jan-janssen I think this is ready to merge.

authors: ellio167 ilia-nikiforov-umn jan-janssen mjwen

repo: conda-forge/kim-api-feedstock


text:
Enable linux cos7 build

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: acesnik conda-forge-linter

repo: conda-forge/metamorpheus-feedstock


text:
release 0.7.12

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter wolfv

repo: conda-forge/micromamba-feedstock


text:
[ci skip] adding user @jtilly

Hi! This is the friendly automated conda-forge-webservice.
I've added user @jtilly as instructed in #11.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #11

Thanks!

authors: conda-forge-linter jtilly

repo: conda-forge/minimalkv-feedstock


text:
MNT: Re-render the feedstock

Hi! This is the friendly conda-forge-admin automated user.
I've re-rendered this feedstock with the latest version of conda-smithy (0.10.3) and noticed some changes.
If the changes look good, then please go ahead and merge this PR.
If you have any questions about the changes though, please feel free to ping the 'conda-forge/core' team (using the @ notation in a comment).
Remember, for any changes to the recipe you would normally need to increment the version or the build number of the package.
Since this is an infrastructural change, we don't actually need/want a new version to be uploaded to anaconda.org/conda-forge, so the version and build/number are left unchanged and the CI has been skipped.
Thanks!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-admin conda-forge-linter

repo: conda-forge/mpir-feedstock


text:
FIX: Update proj.4 package name

Incrementing build number to refresh package dependencies.
Install was still trying to find "proj.4".

ocgis has no direct dependency on proj4, right? that is odd. I will investigate this soon. (This feedstock is quite old and might be good to rerender too.)

You are correct. I quickly learned that this is probably an old build issue. "Rerendering" i assumes means to rebuild. I have a test failure related to a numpy change that needs to be pulled into a new version anyway. Thanks for checking in. :smile:

"Rerendering" i assumes means to rebuild.

Nope. Means that we need to "update" the feedstock with conda-smithy. Let me do that here and check a few other things. Hold on...

authors: bekozi ocefpaf

repo: conda-forge/ocgis-feedstock


text:
Update to 0.4.8, add entry points, add tests, update urls and maintainers

see also https://github.com/conda-forge/pyct-core-feedstock/pull/3

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

license_file entry is missing, but is required.

Unlike for pyct-core, no PR was opened automatically here - I opened this one manually.
@jbednar I saw on the recent nbsmoke PR that @jsignell added some auto merge setting or other for auto created PRs (see https://github.com/conda-forge/nbsmoke-feedstock/pull/5#issuecomment-691061844). That's new (to me), but sounds like something you might want to consider here (and in general for recipes you maintain, assuming dependencies don't change/dependency updates have become automatic).

@conda-forge-admin please rerender

authors: ceball conda-forge-linter ocefpaf

repo: conda-forge/pyct-feedstock


text:
MNT: Re-render the feedstock [ci skip]

Hi! This is the friendly conda-forge-admin automated user.
I've re-rendered this feedstock with the latest version of conda-smithy (2.1.1) and noticed some changes.
If the changes look good, then please go ahead and merge this PR.
If you have any questions about the changes though, please feel free to ping the 'conda-forge/core' team (using the @ notation in a comment).
Remember, for any changes to the recipe you would normally need to increment the version or the build number of the package.
Since this is an infrastructural change, we don't actually need/want a new version to be uploaded to anaconda.org/conda-forge, so the version and build/number are left unchanged and the CI has been skipped.
Thanks!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

repo: conda-forge/pygithub-feedstock


text:
@conda-forge-admin, please add user @srmnitc

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
@conda-forge-admin, please add user @srmnitc
Installed packages
conda

Environment info
conda

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @srmnitc in conda-forge/pyiron-data-feedstock#26.

authors: conda-forge-linter jan-janssen

repo: conda-forge/pyiron-data-feedstock


text:
update to v1.0.42

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

repo: conda-forge/pynmeagps-feedstock


text:
How to get QtWebEngineWidgets on PySide6?

Comment:
I'm getting an ImportError with the code:
from PySide6 import QtWebEngineWidgets
with PySide6 from conda-forge (I tested with 6.4.0 as well as 6.4.1).
Note: It seems to be available in PySide6, version 6.4.1 from pypi.

Humm... how about an approach where the additional modules are built in a separate package?
I believe this is what's done in https://anaconda.org/conda-forge/pyqtwebengine...

The fundamental problems is that the underlying c library doesn't exist for pyside6. We weren't able to compile it.

authors: fabioz hmaarrfk


text:
MNT: Add noarch: python

Hi! This is the friendly automated conda-forge-webservice.
I've made the recipe noarch: python as instructed in #18.
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.
noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

repo: conda-forge/pytask-feedstock


text:
fix: Remove lower bound on zlib host requirement

Resolves #42

zlib is a package controlled through https://github.com/conda-forge/conda-forge-pinning-feedstock/ and so should not have versions manually controlled through lower bounds to enable conda-forge migrations to take place.

c.f. https://conda-forge.org/docs/maintainer/pinning_deps/

Bump build number.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
N/A Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@chrisburr this is ready for review now. Thanks for the original heads up on this.

I'm going to merge this in so that PR #46 can get in so that feedstock for v8.311 will get fixed, but if there's post merge review I'm very happy to make additional revisions.


text:
R3.5

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: cbrueffer conda-forge-linter


text:
fix libblas and openmp deps

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.
@conda-forge-admin please rerender

Update libblas dep according to: https://conda-forge.org/docs/maintainer/knowledge_base.html#blas
Update openmp dep according to: https://conda-forge.org/docs/maintainer/knowledge_base.html#openmp

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter khusmann

repo: conda-forge/r-npflow-feedstock


text:
R3.5

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

repo: conda-forge/r-wesanderson-feedstock


text:
Fix sage-env

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter isuruf

repo: conda-forge/sagelib-feedstock


text:
Updated to version 0.3.0. Switched to Apache 2.0.

Updated to version 0.3.0. Switched to Apache 2.0. Updated minimal versions of geoarray and py-tools-ds. Updated repo URL.

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: host: python>=3.6 must contain a space between the name and the pin, i.e. python >=3.6
requirements: run: python>=3.6 must contain a space between the name and the pin, i.e. python >=3.6
noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter danschef

repo: conda-forge/specclassify-feedstock


text:
⬆ Update TIAToolbox Version to 1.3.2

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

repo: conda-forge/tiatoolbox-feedstock