text:
Visual Studio workspace indexing and explore codebase command are not working for me.

please complete the following information:

OS version: Windows 10
Editor: Visual Studio 2022
Editor version:
Programming language: C#
TabNine extension version: 1.142.1
Engine version (could be located within Tabnine Hub): 4.200.0-62

**Issue Details: I open my Unity project. I right click on an empty area within my project folder and open C# project. My project opens in Visual Studio. I open Tabnine chat. It shows ready and logged in. Unfortunately, workspace indexing never starts. It simply never begins. No errors. I have a Readme.md file in the project, but I have no idea if it is in the right location or if it includes what is needed by Tabnine, as attempting to explore the codebase returns an error telling me that it requires a package manager file or a readme to work.
In the end, because I can't find any information telling me how to correctly prepare a package manager file or readme file for Tabnine use, the responses to my chat requests are very poor. I have ended up having more success with Microsoft Copilot and will most likely end up canceling my Tabnine subscription because of this.**
gz#36071(related to Zendesk ticket #36071)

Try closing the IDE, deleting the VDB folder ( https://support.tabnine.com/hc/en-us/articles/24781988831767-VDB-logs)
and try again.

Thank you. That reset things for me so I could create that .tabnine_root file I didn't know I was missing. Cheers!

Great!

repo: codota/TabNine


text:
🛑 server is down

In 1e0a1c7, server ($API_ENDPOINT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: server is back up in a5e73d7.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Encryption mechanism

The original proof of concept uses the built-in password-based encryption provided by iTunes. An open question is whether this should be supported long-term. Some concerns:

Relies on password strength. This could be an issue, especially if users choose to store their backup in the public IPFS network
There are some manifest/metadata files that don't seem to be encrypted. How sensitive is this data?

Possible ideas:

Custom encryption mechanism that requires a more strict key-management integration and encrypts manifests
Use the built-in encryption, but enforce a password strength
Leave it up to the user

More info on the metadata:
https://www.theiphonewiki.com/wiki/ITunes_Backup
There is definitely sensitive data.

repo: codynhat/ipfs-ios-backup


text:
ucx-py causing issues

Hi @dsroberts
I am having trouble setting up an ESMValTool environment here: https://github.com/ACCESS-NRI/MED-condaenv/pull/66
Error message is:
error    libmamba Could not solve for environment specs
    The following packages are incompatible
    �~T~\�~T~@ python_abi 3.11 4_cp311 is installable and it requires
    �~T~B  �~T~T�~T~@ python 3.11.* *_cpython, which can be installed;
    �~T~T�~T~@ ucx-py is not installable because it requires
       �~T~T�~T~@ python >=3.10,<3.11.0a0 , which conflicts with any installable versions previously reported.
critical libmamba Could not solve for environment specs

I get ucx-py from the coecms conda channel....
Is there something we could do to help with that?
R

Hi @rbeucher
We could probably do that. At this stage ucx-py is only provided by rapidsai for Python 3.9 and 3.10, though I think that's a reflection of the fact that most users will build ucx-py from source. It looks like we're a bit behind in ucx-py releases anyway, I may as well do another one for ucx-py/0.36.00, and build it against ucx/1.15.0 now that that version is available on Gadi & conda-forge. I'll try a Python 3.11 version for you guys, though I'm not sure what to do if it doesn't work...

Thanks @dsroberts !

It would be good to know the process so we can do it next time @dsroberts

Yep, sure. I'm at SCAsia so won't be able to look at this until later in the week. You don't have to follow our approach here either, you could build from source or add the rapidsai conda channel.

OK, new ucx-py packages are now uploaded. I've done ucx-py 0.36.00 for UCX 1.14.0 and 1.15.0 for Python 3.10 and 3.11. A quick test with a new environment seems to confirm that it'll pick the right variant of ucx-py depending on which version of UCX you ask for. As I said before though, this is somewhat outside the bounds of what rapidsai supports. As for doing this yourself, we maintain a fork of ucx-py here https://github.com/coecms/ucx-py that has a few customisations to the build setup. The main branch on the upstream is kept up to date with releases, and we have a couple of branches off of that (main.cms.ucx1.14.0 and main.cms.ucx1.15.0) that we build from. If you want a variant outside of what we provide, you'll need to upload it to the accessnri conda channel.

authors: dsroberts rbeucher

repo: coecms/cms-conda-singularity


text:
🛑 Gstar is down

In 932cdb7, Gstar (https://gstar.gq) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Gstar is back up in 3654bfe after 3 hours, 41 minutes.

repo: coffeefargo/sitestatus


text:
Update to latest CoffeeNet parent version 0.32.0

New CoffeeNet parent version 0.32.0 was released! Please check https://github.com/coffeenet/coffeenet-starter/blob/master/CHANGELOG.md for more information

Pull Request Test Coverage Report for Build 290

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.827%

Totals

Change from base Build 288:
0.0%

Covered Lines:
220

Relevant Lines:
237

💛  - Coveralls

source: gharchive/pull-request

authors: coffeenetrelease coveralls

repo: coffeenet/coffeenet-frontpage


text:
[Feature Request] Parse data in response headers

CoinAPI provides data on request limits, exchanges used in aggregation of OHLCV data, and possibly more that I'm not aware of in the response headers. As far as I can see, the response header is currently neither parsed nor stored. I think it would be good to capture that information, either by parsing it for the relevant request or by just giving the CoinAPIv1 class an attribute response_header and leaving it to the user to parse it. I have only looked at the Python SDK, but I imagine the other languages are similar.
Do you think this makes sense generally and one of the implementations above specifically? If so, I'm happy to make a PR for the Python SDK.

This suggestion is valid as we are tracking it, however can't provide a timeline for that at this moment.

CT

CT

?

@iuvbio Will you be making PR for this?

I hope to get some time to take a look in the next weeks, this has been completely off my radar for a while.

authors: Svisstack iuvbio qqqq-collab

repo: coinapi/coinapi-sdk

license: mit

license_source: bigquery


text:
[xmr] Error(s) refreshing network stats: One or more errors occurred.

Description
been running xmr pool for almost 3 days  but recently I could see some error message from pool log
Steps to Reproduce
1 - Setup XMR main chain
2 - Connect Clients on MiningCore.
3 - Wait for blocks
Expected behavior
no error showing in pool log
Actual behavior
[What actually happens]
not sure whats happening here,
Reproduces how often
this error will show up every 2 - 3  hour
[What percentage of the time does it reproduce?]
Version
v 3.0
Additional Information
##error log:
[2018-10-07 18:17:26.0362] [W] [xmr] Error(s) refreshing network stats: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) (Code -500)
[2018-10-07 18:17:26.0362] [E] [xmr] System.NullReferenceException: Object reference not set to an instance of an object.
at MiningCore.Blockchain.Monero.MoneroJobManager.UpdateNetworkStatsAsync() in /userA/miningcore/src/MiningCore/Blockchain/Monero/MoneroJobManager.cs:line 186 System.NullReferenceException: Object reference not set to an instance of an object.
at MiningCore.Blockchain.Monero.MoneroJobManager.UpdateNetworkStatsAsync() in /userA/miningcore/src/MiningCore/Blockchain/Monero/MoneroJobManager.cs:line 186    at MiningCore.Blockchain.Monero.MoneroJobManager.UpdateNetworkStatsAsync() in /userA/miningcore/src/MiningCore/Blockchain/Monero/MoneroJobManager.cs:line 186
###xmr config
{
"id": "xmr",
"enabled": true,
"coin": {
"type": "XMR"
},
"hasLegacyDaemon": false,
"enableInternalStratum": false,
"externalStratums": [
{
"url": "tcp://192.168.1.3:6000",
"topic": "Monero"
}
],
"address": "45P3tNGKfBTR2Kt7wtz9zHZrpt6Yg3RaDPpeF88TJYU14Q5sYBTHWucKPsCTpShRosgp7wyjzXHqZTRgaCuCPR6kHDgiQVz",
"rewardRecipients": [
{
"address": "45P3tNGKfBTR2Kt7wtz9zHZrpt6Yg3RaDPpeF88TJYU14Q5sYBTHWucKPsCTpShRosgp7wyjzXHqZTRgaCuCPR6kHDgiQVz",
"percentage": 0.75
}
],
"blockRefreshInterval": 500,
"jobRebroadcastTimeout": 10,
"clientConnectionTimeout": 600,
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 50,
"checkThreshold": 50
},
"ports": {
"3092": {
"listenAddress": "0.0.0.0",
"difficulty": 1,
"name": "ASIC Mining",
"varDiff": {
"minDiff": 1,
"targetTime": 15,
"retargetTime": 90,
"variancePercent": 30
}
}
},
"daemons": [
{
"host": "10.100.1.6",
"port": 18081,
"user": "user",
"password": "password"
},
{
"host": "10.100.1.6",
"port": 18082,
"user": "walletuser",
"password": "password",
"category": "wallet"
}
],
"paymentProcessing": {
"enabled": true,
"minimumPayment": 0.1,
"payoutScheme": "PPLNS",
"payoutSchemeConfig": {
"factor": 2
},
"minersPayTxFees": true
}
},

im actually using Latest miningcore  2018 from master . sorry for the typo

miningcore 2018?

yes the one that i clone from master (https://github.com/coinfoundry/miningcore)  few days  ago

authors: fathusband oliverw

repo: coinfoundry/miningcore


text:
Improve the external profiles information.

Description:
To show the external profiles of an entity (institutions, authors, etc.) Guatquyca is parsing a list of IDs and building the URL to make a clickable link for the user:

"Páginas Externas" is displayed using what comes in "external_urls" and "Perfil Externos" is displayed using what comes in "external_ids"
Example of the response:

URL
Request:
Improve the Data or the API Response to remove this job from Guatquyca.
Sample URL to build:
Replace {ID}
researchgate: https://www.researchgate.net/profile/{ID}
orcid: https://orcid.org/{ID}
scholar: https://scholar.google.com/citations?user={ID}
scopus: https://www.scopus.com/authid/detail.uri?authorId={ID}
openalex: https://openalex.org/{ID}
ror: https://ror.org/{ID}
wikidata: https://www.wikidata.org/wiki/{ID}
isni: https://isni.org/isni/{ID}
fundref: https://search.crossref.org/search/funders?from_ui=yes&id={ID}
ucas: https://www.ucas.com/explore/search/providers?query={ID}
linkedin: https://www.linkedin.com/in/{ID}
ukprn: https://www.ukrlp.co.uk/ukrlp/ukrlp_provider.page_pls_provDetails?x=&pv_status=VERIFIED&pv_vis_code=L&pn_p_id={ID}

Revisar este Issue también: https://github.com/colav/HunabKu_plugins/issues/54

revisar para el próximo relese de datos

Ya se controla esto en works, se hará una implementación similar en affiliations y person teniendo en cuenta la sugerencia de @luismvargasg de una posible unificación en "external_profiles"

¿Cual sería la url cuando el source es mag?

mag no tiene url, es solo un número

Y no se entrega a frontend. Ese mag no se pinta en la página.

Hay que tener en cuenta que las URL para Scholar se tienen que construir de diferente forma según sea la entidad: perfil usuario, producto y citas. Revisar la forma en la que se está entregando.

Google scholar para producto es
https://scholar.google.com/scholar?hl=en&as_sdt=0%2C5&q=info%3ASCHOLAR_ID%3Ascholar.google.com&btnG=
donde el SCHOLAR_ID se cambia por el id del producto que está en esternal ids ej:
 external_ids: [
    {
      provenance: 'openalex',
      source: 'openalex',
      id: 'https://openalex.org/W2162822169'
    },
    {
      provenance: 'openalex',
      source: 'doi',
      id: 'https://doi.org/10.15517/aie.v7i3.9281'
    },
    { provenance: 'openalex', source: 'mag', id: Long('2162822169') },
    { provenance: 'scholar', source: 'scholar', id: 'Z5j2ZL_T53oJ' },
    {
      provenance: 'scienti',
      source: 'scienti',
      id: { COD_RH: '0000088994', COD_PRODUCTO: '13' }
    }
  ]

url para ese producto
https://scholar.google.com/scholar?hl=en&as_sdt=0%2C5&q=info%3AZ5j2ZL_T53oJ%3Ascholar.google.com&btnG=

authors: joselomanuelo luismvargasg omazapa

repo: colav/impactu


text:
COPY error

https://github.com/colin-nolan/docker-ffmpeg-rpi/blob/ca66edfe8e8e673797554008e9e31f27be030d57/Dockerfile#L67
Docker gives an error about this line. I believe COPY source globs were removed at some version.
It appears that it worked well when I changed it to
COPY --from=ffmpeg-builder /usr/local/src/ffmpeg/ffmpeg.deb /tmp/ffmpeg.deb

Apologies for not seeing your issue earlier - I did not realise that I wasn't subscribed to notifications.
Happily, I did an update on the 24th December (few weeks after you raised this) that removed the glob (perhaps I hit this too!). Therefore this should be fixed. Please let me know if there's still any issues though.

authors: colin-nolan mkazlauskas

repo: colin-nolan/docker-ffmpeg-rpi


text:
Regular expression with postive lookahead and lookbehind is considered invalid

This Token Regex ...

(?<=\")__\w+[-]*[\.\w+-]*__(?=\")

... results in this error ...

##[error]Invalid regular expression: /(?<=\")__\w+[-]*[\.\w+-]*__(?=\")/: Invalid group

.. while according to the .NET Regex Tester (http://regexstorm.net/tester) it's valid.
What I'm trying to do is only match tokens like this (within quotes):

apiUrl:"__CustomerPortal.ClientAPI.Url__"

and exclude tokens (generated by an Angular build) like this:

(o=Object.setPrototypeOf||{__proto__:[]}instanceof Array&&function(e,t){e.__proto__=t}

EDIT - I also tried this:
"__(\w+[-]*[\.\w+-]*)__"
but that resulted in the quotes being removed after the tokenization.
EDIT #2:
 (?<=\")__(\w+[-]*[\.\w+-]*)__(?=\")
results in
 ##[error]Invalid regular expression: /(?<=\")__(\w+[-]*[\.\w+-]*)__(?=\")/: Invalid group
too.

@frankvaneykelen I'd suggest you simply change the __ to some other symbol like %% so that you don't get conflicts with Angular __.

Since the __ is in all of our hundreds of builds and releases one does not simply change it. We now have to use a hardcoded regex ( __(CustomerPortal\.ClientAPI\.Url|gwa_Account)__) in our Angular releases, which is bad, but since it only needs to replace two tokes for most of these release it's not a big problem.

authors: colindembovsky frankvaneykelen

repo: colindembovsky/cols-agent-tasks


text:
Include original class in schema for z.instanceof()

It'd be great if the original class (e.g. Uint8Array for z.instanceof(Uint8Array)) could be included in the schema to allow for more flexibility.

Hi, can I work on this

What do you mean by "include the original class"? Could you provide some pseudo code that shows how you would like to use this?

@JacobWeisenburger sorry for the late response but i meant that the original class (in this example Uint8Array) should be somewhere included in the object of the schema (so if you log z.instanceof(Uint8Array) to console you can actually know that it should be the specified class).
This would allow other libraries to further analyze the schemas. No longer sure whether this is even needed.
As I personally don't have a use case for this any longer I'm closing this as completed, but feel free to re-open it if this should become a feature.

repo: colinhacks/zod


text:
Parse complicated Mail links for subject and other info

Sort of an involved fix. Will need to create the unsubscribe email body based on the parsed unsubscribe email link. Note that the blacklist.json file filters out any of these complex emails because we currently can't parse them [see https://github.com/colinking/n1-unsubscribe/commit/3a528a1681ccbb6ef6b62f2dd147b70adb3098da]

Closing since update system had to be depreceated


text:
#clear_locks! doesn't handle exceptions

I've recently switched to TokuMX engine (drop-in replacement for MongoDB). It has document-level locking which means sometimes there's timeouts waiting for locks to be granted. This is OK if a failure is handled.
However, in the ClearLocks plugin, there's no protection for failure in the ensure block of clear_locks!. At least in the delayed_job_mongoid backend for DJ, clear_locks! does an update_all that can fail when a lock isn't granted (raises a Moped::Errors::OperationFailure currently). This operation should be retried, as suggested by the error message text: "Lock not granted. Try restarting the transaction.".
Unfortunately, this causes the DJ worker to exit in a ball of fire, which leads to a Very Bad Day™

The error that kills the worker looks something like this:
/var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/operation/read.rb:50:in `block in execute': The operation: #<Moped::Protocol::Command (Moped::Errors::OperationFailure)
  @length=90
  @request_id=947
  @response_to=0
  @op_code=2004
  @flags=[]
  @full_collection_name="app_delayed_job_production.$cmd"
  @skip=0
  @limit=-1
  @selector={:getlasterror=>1, :w=>1}
  @fields=nil>
failed with error 16759: "Lock not granted. Try restarting the transaction."

See https://github.com/mongodb/mongo/blob/master/docs/errors.md
for details about this error.
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:594:in `[]'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:594:in `block (2 levels) in flush'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:593:in `map'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:593:in `block in flush'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:617:in `block in logging'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/activesupport-4.2.0/lib/active_support/notifications.rb:164:in `block in instrument'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/activesupport-4.2.0/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/activesupport-4.2.0/lib/active_support/notifications.rb:164:in `instrument'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/instrumentable.rb:31:in `instrument'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:616:in `logging'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:587:in `flush'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:358:in `pipeline'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/operation/write.rb:47:in `execute'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:665:in `write'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:502:in `update'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/query.rb:427:in `block in update'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/cluster.rb:249:in `block in with_primary'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:204:in `block in ensure_primary'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/executable.rb:25:in `execute'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/node.rb:203:in `ensure_primary'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/cluster.rb:248:in `with_primary'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/query.rb:426:in `update'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/mongoid-4.0.0/lib/mongoid/query_cache.rb:117:in `update_with_clear_cache'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/moped-2.0.2/lib/moped/query.rb:449:in `update_all'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/mongoid-4.0.0/lib/mongoid/query_cache.rb:117:in `update_all_with_clear_cache'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/mongoid-4.0.0/lib/mongoid/contextual/mongo.rb:472:in `update_documents'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/mongoid-4.0.0/lib/mongoid/contextual/mongo.rb:433:in `update_all'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/mongoid-4.0.0/lib/mongoid/contextual.rb:20:in `update_all'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job_mongoid-2.1.0/lib/delayed/backend/mongoid.rb:58:in `clear_locks!'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:9:in `ensure in block (2 levels) in <class:ClearLocks>'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:9:in `block (2 levels) in <class:ClearLocks>'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block in add'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:146:in `start'
  from tasks/jobs.rake:16:in `block (2 levels) in <top (required)>'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/task.rb:236:in `call'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/task.rb:236:in `block in execute'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/task.rb:231:in `each'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/task.rb:231:in `execute'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/task.rb:175:in `block in invoke_with_call_chain'
  from /usr/share/ruby/2.1/monitor.rb:211:in `mon_synchronize'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/task.rb:168:in `invoke_with_call_chain'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/task.rb:161:in `invoke'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/application.rb:149:in `invoke_task'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/application.rb:106:in `block (2 levels) in top_level'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/application.rb:106:in `each'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/application.rb:106:in `block in top_level'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/application.rb:115:in `run_with_threads'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/rake-10.1.1/lib/rake/application.rb:100:in `top_level'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/padrino-core-0.12.4/lib/padrino-core/cli/base.rb:23:in `rake'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
  from /var/www/my-app/shared/bundle/ruby/2.1/gems/padrino-core-0.12.4/bin/padrino:9:in `<top (required)>'
  from /var/www/my-app/shared/bundle/ruby/2.1/bin/padrino:23:in `load'
  from /var/www/my-app/shared/bundle/ruby/2.1/bin/padrino:23:in `<main>'

I've also opened an issue in Moped's repo to see if we can get a more granular exception.

Closing stale


text:
Only heared one side's voice

When I call to second side ,I heared his voice but he does'nt hear my voice.I tried many times but all time the same issue happened.We used  asterisk freePBX as sip accaunt and websocket server.
User: 200
password : 200
Realm:10.10.3.30:5160
WSServer: wss://10.10.3.30:8089/ws
What's the problem ?

https://github.com/collecttix/ctxSip/issues/39
Making the suggested change solved this problem.

https://github.com/collecttix/ctxSip/issues/39
Making the suggested change solved this problem.

yeah thanks a lot. It fixed this issue

Hi,
Also, I am facing the same issue, I tried a lot of times but can't work.
Can you please help me out to fix this issue.?

@awadheshkumarconsta  was facing same issue , try to connect with VPN !

authors: 0samaHaider MrArabboy awadheshkumarconsta comoretti

repo: collecttix/ctxSip


text:
CIM Mapping Native Image broken

It look like the latest upgrade of Quarkus (we think) broken the native image.
The following error occurs:
2022-05-02 10:54:00,235 WARN  [org.lfe.com.cor.jax.exc.GenericExceptionHandler] (executor-thread-0) Unknown exception occurred.: java.lang.ClassCastException: javax.xml.bind.annotation.XmlSeeAlso$$ProxyImpl cannot be cast to com.sun.xml.bind.v2.model.annotation.Locatable
	at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:260)

It seems like to many classes are stripped.

@dlabordus is this still an issue?

repo: com-pas/compas-cim-mapping


text:
backport: Add p2p security fix to v0.34 and v0.37 #9517

Original issue:  tendermint/tendermint#9517
This is a ToDo issue for backporting and testing the security fix from tendermint/tendermint#9500.
v0.34

[x]  Backport v0.34.x and add a CHANGELOG_PENDING.md tendermint/tendermint#9516
[x] Run a large-scale testnet (a single test) on v0.34.x with this fix and check that things work as expected.
[x] Cut v0.34.22.

v0.37.1

[x] Backport to v0.37.x and add a CHANGELOG_PENDING.md #87
[x] Keep the v0.37.x backport branch open until we've cut v0.37.0, then merge it.
[x] Run another large-scale testnet on v0.37.x to check that things work before cutting v0.37.1.

Closed as #473 has been launched (and the fix was merged into 0.37.0 - we decided to forego the 0.37.1 route).

repo: cometbft/cometbft


text:
perf(state): Cache the block hash

Closes #2923
Caches the block hash to ensure we only compute it once in consensus execution.

PR checklist

[x] Tests written/updated - not sure what test I should write, any suggestions?
[x] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments
[x] Title follows the Conventional Commits spec

I don't know why the mutex is needed


text:
perf(p2p)!: Remove PeerSendBytesTotal metric

Component of #2840. As we discussed in the issue, we want to deprecate the peer send bytes total metric because:

This is a costly metric (see pprof)
This increases the cardinality of labels in Prometheus, which can slow things down in Prometheus significantly.
Its not really useful at this level of abstraction. We don't have reported usecases of this being used yet. If we want to do it in the future, we should more likely architect it as updating a live go variable, and then sending to our metrics instance on a polling ticker (ala PeerSendQueue metric). The right levels that are interesting for outbound traffic could be the consensus gossip routines or blocksync.

To see its costly, 21% of all CPU time for live osmosis nodes in the latest Osmosis patch release is in peer.Send. over half of that time is in these metrics:

Please advise for how we should go about deprecating / removing this metric? Feel free to close this PR / say you want to handle it separately.

PR checklist

[X] Tests written/updated - N/A
[x] Changelog entry added in .changelog (we use unclog to manage our changelog)
[x] Updated relevant documentation (docs/ or spec/) and code comments - I didn't find any relevant docs
[x] Title follows the Conventional Commits spec

Concerning the fact that this is going to be removed and not available in the future, it would be interesting to ensure this is not used in our QA or Infra tests, I briefly looked at the logic there and couldn't find references to this particular metric, but @hvanz or @sergio-mena might have more insights.
If we find out that some logic critically depends on this metric, probably a better approach would be to make it a configurable option if possible (e.g. disable it through a config value).

ah thanks, didn't think to search the docs with underscores! (Explains why I didn't find it earlier haha)

Thoughts on merging, and then reverting if we discover some metric consumer used this?

That's a bad dev UX 😅

If we find out that some logic critically depends on this metric, probably a better approach would be to make it a configurable option if possible (e.g. disable it through a config value).

please no more config options. IMO we have too many config options

If we find out that some logic critically depends on this metric

Even if some external software depends on this metric, it shouldn't prevent us from removing it. CometBFT's mission and what it should do best in the world is fast and reliable consensus. And if some metric is significantly slowing CometBFT down, we should eliminate it!

Ive tested removing it, and the prometheus time here went down ~70%! TBH that still justifies us removing the other metric or doing that more "asynchronously", e.g. via the updateStatsRoutine

@mergify backport v1.x

authors: ValarDragon andynog melekes


text:
[Bug] Incompatibility with LambaControls

Seems to be a Crash on Launch with LambaControls and this mod both installed. The easiest solution is to uninstall this mod, but I like it so... You Know.
crash-2021-01-18_20.20.39-server.txt

Duplicate of #4 , I plan to fix this soon, don't have access to a computer for a couple weeks so it might take a bit.

Duplicate of #4 , I plan to fix this soon, don't have access to a computer for a couple weeks so it might take a bit.

authors: ZaneDragonBorn cominixo


text:
When starting Corolla 2017, engine may stutter + comma2 reboots immediately

Describe the bug
After updating to 0.8.3, my Corolla 2017 SE engine starts to stutter when starting the car + comma2 reboots. The comma2 will eventually turn back on while I'm driving and openpilot is functional.
How to reproduce or log data
Not always reproducible, but seems like this issues occurs after being away from car for a couple hours, e.g when I go to my car in the morning this issue will happen.
Expected behavior
When car starts, engine should not stutter and comma2 should not reboot
Device/Version information (please complete the following information):

Device: comma2
Dongle ID: da8078584fafb6c1
Route: da8078584fafb6c1|2021-04-07--19-14-54
Timestamp: At the very beginning of the drive (around 7:10pm which is before the timestamp of the video start)
Version: stock 0.8.3
Car make/model: Toyota Corolla 2017

Additional context

Toyota Pedal is attached
first observed this on 0.8.3
After my drive was over I immediately tried testing this again (turning car off and on) but this time issue did not occur: da8078584fafb6c1|2021-04-07--19-22-44

Did you try without the pedal? And without the C2 at all? This sounds more like a car issue to me.

Thanks that makes sense, I unplugged the C2 + pedal and still experience this.
My question is what would cause the C2 to reboot when the car eventually starts up though?

Thanks that makes sense, I unplugged the C2 + pedal and still experience this.
My question is what would cause the C2 to reboot when the car eventually starts up though?

Voltage drop. C2 does not have a battery.

I'll go get my car checked and close this if that resolves the issue.

Since it happens without the C2 as well I'm going to close the issue. Feel free to open a new issue if your C2 is still misbehaving after your mechanical problems are solved.

repo: commaai/openpilot


text:
Honda: Mini cars missing and speed too slow errors

Describe the bug
After either #31763 or #31799 , and the March 12th master-ci build, my dashboard no longer works as expected. The lead car (mini car) no longer shows along with the adjacent cars, which show on my trim. It used to show up to 2 in each adjacent lane, even when using alpha longitudinal control.
Also when setting ACC under 25mph, or when the current speed falls under 25mph, a message shows on screen "Cannot set cruise: speed too low". Openpilot never disengages, but these issues never occurred before today.
Provide a route where the issue occurs
5130484aa8069bad/00000010--c76b9d991a/2
openpilot version
0.9.7 / master-ci / 224ee9f / Mar 12
Additional info
No response

Can you revert this and try again? https://github.com/commaai/openpilot/pull/31799
Can you also get a stock route where you cycle from closest to max distance on the dash and mark the beginning and end of that section?

Issue seemed to be when testing the distance button, accidentally set it to standard cruise mode, but the UI did not update. This made something think the car was in standard cruise mode, while openpilot was sending ACC commands.
If using Stock ACC, the UI icon updates back and forth when switching and car makes a long beep.
If using openpilot ACC, the UI icon doesn't update, nor does it make a beep. Only symptom is mini cars no longer show and shows "slow speed" error when under 25 mph.
op long, with car in "standard" cruise mode: 5130484aa8069bad/00000012--f2f58aca39/0
Stock long, starting in "standard" cruise mode, then switching to ACC. Also played with lead distance button: 5130484aa8069bad/00000013--e85305cd64/1
op long starting in ACC mode, then switching back and forth between "standard" and ACC modes with lead: 5130484aa8069bad/00000014--26d854a52d/1

Ah, so you're saying some ECU besides the camera is in non-adaptive cruise mode, and therefore is not caused by the distance button PR recently merged?

I checked the first two routes in your last message, and no other signal outside of ACC_HUD matched exactly. My guess is the ECU that accepts the acceleration command messages (PCM) also manages an internal state of whether it should be doing standard cruise control or not, and just doesn't publish this state back out over CAN (both camera and PCM must look at the buttons to sync their states).
This supports this theory, you can see the PCM is reporting "ACC" is active, but the camera is not sending anything. This hints the PCM keeps its own adaptive cruise state as well as does non-adaptive cruise internally:

Going to block enabling in this non-adaptive state like we do when we're using stock long.

authors: MarcoTheDingo sshane


text:
lower thumbnail resolution & frequency and remove from camerad

Now that we don't upload qcams by default on cell, we can't use the I-frames to show thumbnails before qcams upload, which we still want.

generate thumbnails in encoderd or loggerd (so loop of camerad isn't variable depending on if it's making a thumbnail or not)
reduce resolution and frequency. 1/8th and 2 per segment? currently it's 1/4th and 12 per segment

Moved to https://github.com/commaai/openpilot/issues/24570


text:
Update hyundai elantra hb values.py

Added hyundai elantra hybrid 2021 fwd camera, eps firmware versions.

What's the dongle id?


text:
common PlatformFlags base class + test for < 32 bits

>32 bit flags would not be supported because in cereal, flags is 32 bits. good check to have, especially because Hyundai exists
also allows for a helper on the flags, ex: for checking exact flag matches: https://github.com/commaai/openpilot/pull/31645

I realized the tests already catch this, we don't this test inside the flag class


text:
Update sbt-github-actions to 0.14.1

Updates com.codecommit:sbt-github-actions from 0.13.0 to 0.14.1.
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.codecommit", artifactId = "sbt-github-actions" } ]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor

Superseded by #365.

repo: commercetools/sphere-scala-libs


text:
Pre-Bump Scripts do not have access to packages installed before using commitizen-tools/commitizen-action

Background
I have a closed-sample project where I make use of commitizen-action to handle versioning and changelog generation. I make use of .cz.toml's pre_bump_hooks configuration to add shell scripts which should be executed before version bump commit. The idea was to run a couple of cleanups based on the version information.
However, this fails as some external required packages are not made available to the scripts although they were installed in previous steps before commitizen-tools/commitizen-action is used.
Example
release.yml
 tag-and-bump:
    if: ${{ github.ref == 'refs/heads/main' && !startsWith(github.event.head_commit.message, 'bump:') }}
    needs: install-and-test
    runs-on: ubuntu-latest
    name: "Bump version and create changelog with commitizen"
    steps:
      - name: Check out
        uses: actions/checkout@v3
        with:
          fetch-depth: 0
          token: "${{ secrets.GITHUB_TOKEN }}"
      - name: Setup Node
        uses: actions/setup-node@v3
        with:
            node-version: 16
      - name: Install packages
        run: yarn install --immutable
      - id: cz
        name: Bump package
        uses: commitizen-tools/commitizen-action@master
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
      - name: Print Version
        run: echo "Bumped to version ${{ steps.cz.outputs.version }}"

.cz.toml
pre_bump_hooks = [
  "scripts/pre-bump-script.sh"
]

scripts/pre-bump-scripts.sh
node -v

The script above fails with a command node not found

Interesting, I'm not sure how to solve this issue. The thing is that the action runs on its own docker image.

Interesting, I'm not sure how to solve this issue. The thing is that the action runs on its own docker image.

That would explain it.
So far, a fix I have found is to install the required packages within the same script however, the workflow takes wayy too long when I do this.

Is it a possibility for you to re-write it in python or with coreutils? That's why I'm not a big fan pre_bump_hooks from commitizen.

Is it a possibility for you to re-write it in python or with coreutils? That's why I'm not a big fan pre_bump_hooks from commitizen.

Unfortunately, the scripts aren't portable to python due to tight dependence on the packages.
Is there an alternative to using pre_bump_hooks you can recommend?

What is your script doing? I'd consider if the step can be done outside commitizen. Which variables do you use from: https://commitizen-tools.github.io/commitizen/bump/#pre_bump_hooks

Which variables do you use from: https://commitizen-tools.github.io/commitizen/bump/#pre_bump_hooks

I only make use of CZ_PRE_NEW_VERSION.

I'd consider if the step can be done outside commitizen.

Thanks for this, I can already see possible ways I can handle much of this outside commitizen. The only downside is I'd have a chore: cleanup after bump commit after each version bump. But I should be able to live with that 😅

You can have a step which installs commitizen with pip install commitizen, then run something like:
cz bump --git-output-to-stderr --dry-run | grep 'tag to create:' | grep -Eo '[0-9].+' > CZ_NEXT_VERSION
cat CZ_NEXT_VERSION

Or directly into a github action variable:
- name: Next version
   id: getnextversion
   run: |
      export NEXT_VERSION=$(cz bump --git-output-to-stderr --dry-run | grep 'tag to create:' | grep -Eo '[0-9].+')
      echo "VERSION=$NEXT_VERSION" >> $GITHUB_OUTPUT
- name: Your NODEJS script
  env:
    CZ_PRE_NEW_VERSION: ${{ steps.getversion.outputs.VERSION }}

# HERE the commitizen action

I believe any change done in git will be picked up by commitizen and commit them in the bump commit. If that's not the case, try doing git add <files you changed>, at that point cz bump will definitely pick them up for the cz bump commit generated.

You can have a step which installs commitizen with pip install commitizen, then run something like....

Thanks @woile I'm going to give this a try and let you know how it goes

I'm closing this since my issue has been addressed already by @woile.
Thanks for the help

authors: elcharitas woile

repo: commitizen-tools/commitizen-action


text:
The EKS recipe auth is slow, add alternative approach to docs

Hi! I just tried granted and it looks awesome except one thing: the recommended way slows down my kubectl / k9s operations.
I followed the recipe here: https://docs.commonfate.io/granted/recipes/eks
This caused me to almost give up on granted but I realised that I could export my credentials via -ex. I think the docs should mention this approach also. This has the added benefit of not having to modify your ~/.kube/config file which is kind of a PITA if you're working with lots of clusters.
Congratulations - I'm very impressed with what you've created and will be following the project 👏

Could you expand on how you used the --ex approach ?

@greg-swift-yohana I use this bash function:
switch_account () {
	source assume $1 -ex --duration 12h
	kubectl config use-context $1
}

This sets credentials for the current terminal session.

authors: greg-swift-yohana mkotsalainen

repo: common-fate/granted


text:
"Finishing uploading" not finished after an hour

On @maskaravivek 's wikidataTest branch.
Two images were uploaded correctly (and the Wikidata properly set) but the third does not seem to finish. It is still running right now, so if there is any way I can give you more debug information please ask me :-)
All images uploaded via Nearby->Gallery

Actually the image has been uploaded but not categorized and not linked from Wikidata:
https://commons.wikimedia.org/wiki/File:調布市Green_Hall_3.jpg
https://www.wikidata.org/wiki/Q11631740

Media wiki uploaded file

Reproduced again today (one year later!) on the GSoC 2019 branch, not sure if it is the same bug but it is the same symptom:

logcat5.txt

The upload service has been refactored, the issue was the notifications not being updated properly, I verified that this does not happen on the master. Closing this issue, feel free to re-open if someone is able to reproduce this again

repo: commons-app/apps-android-commons


text:
Notifications for thanks and usages

When I get a thank, or when a picture of mine gets used somewhere, a counter is increased in "Achievements". That's hard to see, and most people don't go check more than once a month, I guess.
We should show these two events MUCH more prominently, and I think that a notification is the most natural way to do that.
The notification should not be shown if the image usage results from an edit by me, though (typically from Wikidata). Maybe our server could check that.
As a rule of thumb, as a heavy user, since 2005 I have received 13 thanks and my pictures have been used 229 times, maybe 30% by myself. With https://github.com/commons-app/apps-android-commons/issues/780 the number of thanks could increase a lot, though.

I would suggest that for WikiMedia [sic]
Commons to be more interesting to a general user
who has access to the internet, he/she would
probably want to contribute more if he or she were
to get something back in return. For example, on
Facebook, people get likes or reactions in the form
of comments which makes them feel good about
contributing, on Quora, you get upvotes and views
which makes you want to write more. If Wikimedia
Commons were to be built on a platform where
people could rate contributions of their friends
and colleagues, it would probably draw more
interest, especially from the millennials. -Man, age
18-21, United Arab Emirates

To be fair, in the new v3.0 UI the counter will likely be shown in Home, loaded whenever the user opens the app. :) However, I still think a notification would be great!

Agreed, this would be a great motivator. Has anything been incorporated into the app since 2018?
Chris.

notification is currently sent for thanks.
notification for usages not implemented yet.

authors: chrisdebian misaochan nicolas-raoul


text:
Update crash reporting framework

I notice that the app is using the ACRA crash reporter.  In the commercial app experience I've had, we moved away from ACRA to Crashlytics several years ago.  Google bought Crashlytics back in January and are now suggesting that people use it in preference to Firebase crash reporting.  Crashlytics is free.
Out of the box, in addition to crash reporting, Crashlytics offers

Key performance metric tracking (I setup "login", "took a photo",  "share from gallery")
Release adoption graphs (how many people are using which versions)
Live count of active users
Session length in the app

Crash reports are collected in the web interface so everyone with an account (say, all the folk with commit access here) would be able to look at them.  Want to try it out / evaluate it?
The code to switch is on a branch in my fork if you're curious.

The link to Crashlytics brings up Fabric - was that intended?
If the link is correct, is Fabric/Crashlytics open source? I understand that it is free, but AFAIK according to our policies we cannot use non-open source dependencies?

Crashlytics started out a standalone crash reporting service that was bought by Twitter and integrated into the wider Fabric SDK in 2013.  Last year it was bought by Google with the plan for Crashlytics to replace their existing Firebase crash reporting system.
So, no it's not open source but it is free and part of the overall portfolio of other Google tools.  Do we plan on using Google SDKs for push notifications (https://firebase.google.com/products/cloud-messaging/)?  This would likely fall into a similar category as that.
I wasn't aware of the open-source only rule.  I'm happy to close this issue in that case.

(HockeyApp would be an alternative whose SDKs are open source on Github)

The HockeyApp server is not open source either.
We have no requirement that server-based code is 100% open source, but in accordance with https://wikimediafoundation.org/wiki/Privacy_policy we must be very careful about what we let third-party companies know about our users.

What are the "main" Wikipedia apps doing for crash reporting? If they built their own thing, maybe one can piggyback on them...

@nicolas-raoul Wasn't there an issue with the use of Google Maps SDKs for lat/long calculations when I was implementing the map of nearby places? https://github.com/commons-app/apps-android-commons/issues/73#issuecomment-239756301 Perhaps we might need to discuss this and agree on a policy for which external libraries and SDKs we can and cannot use (and document it on the wiki, as @janpio suggests).
Also, what are the requirements for F-Droid inclusion? Is it just apps relying on Google Play Services that cannot be included?
@psh Yeah, I was wondering about that, too. We have been finding it difficult to implement push notifications for that reason.

That comment was about using a proprietary Android component directly on the phone. Google Play Services can be considered a library, as it provides methods for all sorts of random things. A GNU-GPL program can not call a proprietary library.
Calling a proprietary server via HTTP calls, on the other hand, is less of a problem, if privacy is respected.
If we choose to call a proprietary service, though, we will get a negative badge on F-Droid saying "promotes non-free network services". (free being used with the meaning of free software)

I started a wiki paragraph about this topic here: https://github.com/commons-app/apps-android-commons/wiki/Code-style#external-libraries

Thanks for the clarification @nicolas-raoul ! I would be on board with using Crashlytics in that case. :)

That means telling Microsoft the IP address of our users.
I am not sure how WMF will see that :-/
On Tue, Sep 5, 2017 at 7:04 PM, Josephine Lim notifications@github.com
wrote:

Thanks for the clarification @nicolas-raoul
https://github.com/nicolas-raoul ! I would be on board with using
Crashlytics in that case. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/858#issuecomment-327131170,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBisC6UDXT8K7QRfg50wmx6PgT6qtks5sfRykgaJpZM4PE3wW
.

If it contravenes the privacy policy, perhaps not a good idea then.

That's a grey area.
For some reason giving our users' IP addresses to Mapbox did not sound
problematic to them.
Better ask WMF case-by-case I think, with a clear explanation of the
benefits.
On Tue, Sep 5, 2017 at 8:25 PM, Josephine Lim notifications@github.com
wrote:

If it contravenes the privacy policy, perhaps not a good idea then.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/858#issuecomment-327147683,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBkdZl264dWGG5GZVC9HT6dW_J8ySks5sfS-agaJpZM4PE3wW
.

Haha, I also still had a tab open where I researched this a few minutes ago:
https://github.com/wikimedia/apps-android-wikipedia/search?utf8=✓&q=hockeyapp&type=

I guess we can use it then.
On Tue, Sep 5, 2017 at 10:47 PM, Jan Piotrowski notifications@github.com
wrote:

Haha, I also still had a tab open where I researched this a few minutes
ago:
https://github.com/wikimedia/apps-android-wikipedia/search?
utf8=%E2%9C%93&q=hockeyapp&type=
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/858#issuecomment-327180314,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBqRmHxDcMmt5CFL3qsXapf_AjgMYks5sfVD0gaJpZM4PE3wW
.

Yes, the Wikipedia app uses Hockey app for Crash reporting and @sharvaniharan from the Wikipedia Android team confirmed the same during the hackathon. It would be great if our app also starts using Hockeyapp. Its open source so unlike Fabric or Firebase it should be safe to use this.
Apart from automatic crash reporting, Hockeyapp has a few other features as well, which we check and use if needed. https://github.com/bitstadium/HockeySDK-Android
Also, Hockeyapp is different from Acra as:

it sends the crash reports automatically, rather than the user having to send an email
the crash reports are automatically grouped on a dashboard so it is easy to track and resolve issues.

As the device metadata, crash reports are automatically grouped, its easier to find patterns and understand the issue easily.
For eg.

@misaochan @ashishkumar468 It would be nice to have your opinions on this. :)

Note that HockeyApp won't be available much longer and has be replaced by Visual Studio App Center: https://hockeyapp.net/

Thanks for pointing it out @janpio! I didn't know about App Center.
Looks like App center SDK is also open source. https://github.com/microsoft/appcenter-sdk-android
@dbrant @sharvaniharan Do you have any opinions on what platform we should use for crash reporting?

I think adding the hockey app sdk will be of great help.
As @maskaravivek  mentioned

Also, Hockeyapp is different from Acra as:

it sends the crash reports automatically, rather than the user having to send an email
the crash reports are automatically grouped on a dashboard so it is easy to track and resolve issues.
Right now it is really painful to browse and fix the crashes from the google groups. Also, as the crashes are grouped together, it will also help us prioritise them based on the frequency.

Hmm, I guess it depends on whether the new App Center is allowed under policy. @dbrant @sharvaniharan What does the Wikipedia app plan to do when Hockey is deprecated? Will you be switching to App Center?

Yes, presumably HockeyApp is being folded into AppCenter. I don't think it's going away, so we'll keep using it.  It's been useful to us for being able to add extra metadata to the crashes, such as the user's language selection.  If the new AppCenter experience proves to be inadequate in some way, then we'll happily go back to using the generic Play Store crash reporting, which is perfectly fine, too.

Yay, thanks for the feedback @dbrant ! Let's proceed with integrating HockeyApp/AppCenter in that case. :)
Re: Play Store crash reporting, it is a problem for us to rely on that as only myself and @nicolas-raoul have access to the WMF Play Store account at the moment. Adding more people would require Legal's consent (and we did not get it the last time we asked). However, if we use HockeyApp, we can just migrate all the core devs over since the NDA that they signed should suffice for that (I don't think Hockey gives us any additional information that ACRA isn't already, it just organizes it better).

I just realized that there might be a benefit of ACRA - it lets the user comment on what they are doing during the crash, and we can follow up with them because we have their email address from the email that they sent us. @ashishkumar468 how important do you think this would be for your bug-solving? Maybe we should keep Acra AND implement Hockey (as a replacement for the generic Play Store crash reporting)?

I am okay with having both :-), The user's comment is definitely valuable.

authors: ashishkumar468 dbrant janpio maskaravivek misaochan nicolas-raoul psh


text:
Fix NPE in nearby fragmnet

Description
Fixes #1329 number 6, NPE exception when you click one of nearby markers and make information bottom sheet visible, then go to settings and change theme, app will crash when you re-start nearby activity. Editing first entry accordingly.
Added nullcheck, solves the error and all things else goes well.
Tests performed
Manual tests API 19

I am merging my own PR, since release is urgent.


text:
Add labels against ID & email address in the email sent to designated CLA Manager who is identified from Contributor Console

When a contributor identifies initial CLA Manager from Contributor Console then an email is sent that designated CLA Manager.
There are two possible emails sent based on whether the designated CLA Manager has an LF Login account or not.
If designated CLA Manager doesn't have LF Login account that following email is sent:
Subject: EasyCLA: Invitation to create LF Login and complete process of becoming CLA Manager
Body:
Hello Manish jio six,
This is a notification email from EasyCLA regarding the project(s): A-LF Networking Fund-Manish-Child001, A-LF Networking Fund-Manish-Child002, A-LF Networking Fund-Manish-Child003, A-LF Networking Fund-Manish-Child004.
We received a request from manishyahoo09 (manishvdy@yahoo.com) to contribute to any of the above projects on behalf of your organization.
Before the user contribution can be accepted, your organization must sign a Corporate CLA(CCLA). The requester has stated that you would be the initial CLA Manager for this CCLA, to coordinate the signing of the CCLA and then manage the list of employees who are authorized to contribute.
Please complete the following steps:
Please click on Accept Invite to create your LF Login. This is used to access the EasyCLA CLA Manager console.
After login, you will be redirected to the portal https://lfx.staging.platform.linuxfoundation.org where you can either sign the CLA for any of the project(s): A-LF Networking Fund-Manish-Child001,A-LF Networking Fund-Manish-Child002,A-LF Networking Fund-Manish-Child003,A-LF Networking Fund-Manish-Child004, or send it to an authorized signatory for your company.
After signing the CLA, you will need to add this contributor to the approved list in the CLA Manager console.
After adding the contributor, please notify them so that they can complete the contribution process.
If you need help or have questions about EasyCLA, you can read the documentation or reach out to us for support.
EasyCLA Support Team
If designated CLA Manager has an LF Login account that following email is sent:
Subject: EasyCLA: Invitation to Sign the Pinterest Corporate CLA and add to approved list amolsontakke3576
Body:
Hello Amol,
This is a notification email from EasyCLA regarding the project(s): NewOrgChange002.
We received a request from amols@proximabiz.com (amolsontakke3576) to contribute to the above projects on behalf of your organization.
Before the user contribution can be accepted, your organization must sign a Corporate CLA (CCLA). The requester has stated that you would be the initial CLA Manager for this CCLA, to coordinate the signing of the CCLA and then manage the list of employees who are authorized to contribute.
Please complete the following steps:
After login, you will be redirected to the portal https://lfx.dev.platform.linuxfoundation.org where you can either sign the CLA for any of the project(s): NewOrgChange002, or send it to an authorized signatory for your company.
After signing the CLA, you will need to add this contributor to the approved list in the CLA Manager console.
After adding the contributor, please notify them so that they can complete the contribution process.
If you need help or have questions about EasyCLA, you can read the documentation or reach out to us for support.
EasyCLA Support Team

The above emails need following changes.

Email says "Please click on Accept Invite to create your LF Login" but there is no link to accept invite. Can we make Accept Invite clickable so that user can click on it. Similarly "After login" doesn't tell the user where exactly they have to login
The comma separated list of projects doesn't have spaces between each project name
There are some sentence where there is no space after period and the next sentence starts
Instead of giving a generic link like https://lfx.dev.platform.linuxfoundation.org could we change it to project specific link so that the user doesn't have to search for that project
The sentence which says "We received a request from ..." doesn't mention tell exactly whether value is GitHub Username & GitHub Email Address. So, need to add label before the value.
We received a request from GitHub Username: manishyahoo09 (Email Address: manishvdy@yahoo.com)
We received a request from Email Address: amols@proximabiz.com (GitHub Username: amolsontakke3576).
Note: If email address is certainly GitHub Email Address then instead of saying Email Address say GitHub Email Address.

This is deployed to DEV, Staging & PROD.

If User has  LF Login :
Subject: EasyCLA: Invitation to Sign the Reliance Jio Infocomm Limited Corporate CLA and add to approved list manishyahoo09
Hello Manish Vaidya,
This is a notification email from EasyCLA regarding the project(s): A-LF Networking Fund-Manish-Child001, A-LF Networking Fund-Manish-Child002, A-LF Networking Fund-Manish-Child003, A-LF Networking Fund-Manish-Child004.
We received a request from manishvdy@yahoo.com (manishyahoo09) to contribute to the above projects on behalf of your organization.
Before the user contribution can be accepted, your organization must sign a Corporate CLA (CCLA).The requester has stated that you would be the initial CLA Manager for this CCLA, to coordinate the signing of the CCLA and then manage the list of employees who are authorized to contribute.
Please complete the following steps:
After login, you will be redirected to the portal https://lfx.staging.platform.linuxfoundation.org where you can either sign the CLA for any of the project(s): A-LF Networking Fund-Manish-Child001,A-LF Networking Fund-Manish-Child002,A-LF Networking Fund-Manish-Child003,A-LF Networking Fund-Manish-Child004, or send it to an authorized signatory for your company.
After signing the CLA, you will need to add this contributor to the approved list in the CLA Manager console.
After adding the contributor, please notify them so that they can complete the contribution process.
If you need help or have questions about EasyCLA, you can read the documentation or reach out to us for support.
EasyCLA Support Team

If User doesn't have LF Login and coming from Github
Subject: EasyCLA: Invitation to create LF Login and complete process of becoming CLA Manager
Hello Manish Paytm Five,
This is a notification email from EasyCLA regarding the project(s): A-Feb-10 Multi Level Projects-CHLD004.
We received a request from GitHub Username: manishyahoo09 (GitHub Email Address: manishvdy@yahoo.com) to contribute to any of the above projects on behalf of your organization .
Before the user contribution can be accepted, your organization must sign a Corporate CLA(CCLA). The requester has stated that you would be the initial CLA Manager for this CCLA, to coordinate the signing of the CCLA and then manage the list of employees who are authorized to contribute.
Please complete the following steps:
Please click on Accept Invite to create your LF Login.This is used to access the EasyCLA CLA Manager console.
After login, you will be redirected to the portal https://lfx.staging.platform.linuxfoundation.org where you can either sign the CLA for any of the project(s): A-Feb-10 Multi Level Projects-CHLD004, or send it to an authorized signatory for your company.
After signing the CLA, you will need to add this contributor to the approved list in the CLA Manager console.
After adding the contributor, please notify them so that they can complete the contribution process.
If you need help or have questions about EasyCLA, you can read the documentation or reach out to us for support.
EasyCLA Support Team

repo: communitybridge/easycla


text:
EasyCLA dashboard not working after admin disables bot on github - [CDF/Tekton]

Summary
EasyCLA dashboard not working after admin disables bot on github. EasyCLA manager level user can see and list repositories, but can no longer administer the repositories if a developer who has admin rights on github disables the bot.
Screenshots

@danlopez00 the Project Manager will need to navigate to the EasyCLA Project Console and re-authorize/re-connect the GitHub Bot under the project.  Once this is complete, project managers will be able to administer the repositories.

@danlopez00 Instructions are here: https://lf-docs-linux-foundation.gitbook.io/easycla/getting-started/project-managers/add-github-repositories-to-cla-monitoring-or-remove-them-from-cla-monitoring

Closing this issue during the product backlog review meeting.  @danlopez00 ping the EasyCLA team if you need further assistance.


text:
After deploying, there's no app

When I try to access https://agminsta.herokuapp.com/, it says "There's nothing here, yet"
So when I try to use instafeed.js, it can't find https://agminsta.herokuapp.com/token.js.
What should I do?

Got the same issue!

Same issue here https://robin-insta-test.herokuapp.com/

Same issue here.

Probably related to app being suspended by Heroku https://github.com/companionstudio/instagram-token-agent/issues/13

Probably related to app being suspended by Heroku #13

I understand but is someone working on the app being approved by Heroku? Because now nobody can use this app (and the Instagram feed).

As of July 9, Heroku support said they were waiting to hear back from the app developer.

Same issue here... worked for the initial View and then went blank

Same issue!

Same here

same issue, any updates?

Same!

@SILENTVOICE976 @j-bn @qsad @nicholasroubal and anyone else this is affecting:
There's a different service available called instant-tokens.com. There are some examples on how to implement on this thread:
https://github.com/stevenschobert/instafeed.js/issues/654
Hope this helps!

Hey everyone - I'm going to close this so we can continue discussion over in #13 (it's the same issue).

authors: RobinOTYS SILENTVOICE976 TimothyGilman angelogiomateo benjamin-hull garethmorgans hhermsen j-bn nicholasroubal qsad sandervanh wearegoose

repo: companionstudio/instagram-token-agent


text:
Add cluster volume type constant

Cluster volumes were added to docker SwarmKit in 23.0 of docker engine. In short, cluster volumes enable use of container storage interface (CSI) volumes through docker's plugin system. This PR simply adds the cluster volume type constant.

LGTM, need to be rebased as compose-spec schema was updated

@glours, for sure! Just opened it!

authors: aaraney ndeloof

repo: compose-spec/compose-go


text:
Add beta banner

Checklist

[x] Resolves #99
[x] The code of conduct is respected
[x] Added project
[x] Added label "Review needed"
[x] Assigned a reviewer

Reviewer

[ ] I've checked out the code and tested it myself.

Changes

Added a Banner component and put it on the top of every page

ich würde den Banner in diesem Apricot Farben machen, dann sticht es mehr raus und nach unten an den Bildschirm packen. Ich glaub, da schaut man eher hin.

authors: Narigo Wiesusenurmitj

repo: compose-us-research/noqueue


text:
Otp View Typing Response Slow

The library exhibits a delay in character rendering during rapid typing, occasionally resulting in skipped characters. This behavior impacts user experience, particularly during fast-paced input sessions.

Compose dependencies updated with version 1.0.9. Seems like it fixed the issue for me. Can you check and let me know if it fixed?

This issue has been inactive for a while, so I’m going to close it. If the problem persists or there’s more to discuss, feel free to reopen the issue or create a new one.

authors: ilyasipek praveenathuru tarikyasar

repo: composeuisuite/ohteepee


text:
Update circe-literal, circe-parser to 0.14.2

Updates

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

from 0.14.1 to 0.14.2.
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 = [{
  pullRequest = { frequency = "@monthly" },
  dependency = { groupId = "io.circe" }
}]

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

Superseded by #272.


text:
Retravailler le format de données des salarié⋅es / membres / associé⋅es

Infos à avoir :

salariat :

dates du contrat (début + optionnellement date de fin)
identifiant de personne

membre / associé⋅e :

pareil

Concernant les comptes, pour le moment, je décide que, attaché à la personne, on attribue différents comptes 4 (tous optionnels et créés à la volée) : compte courant d'associé, compte de personnel (salarié.e), compte fournisseur, compte client
Et pour les personnes, rajouter le type ("physique" ou "morale"). Pour tout le monde un champ adresse optionnel et pour les personnes morales, un champ SIRET optionnel


text:
Minor fix to label transform function in finetuning notebook

Fixes https://github.com/computational-cell-analytics/micro-sam/issues/676

This should work as expected now. I'll go ahead and merge this once the tests pass. Thanks!

repo: computational-cell-analytics/micro-sam


text:
[bug] VS compiler autodetection doesn't work

Environment Details (include every applicable attribute)

Operating System+version: Win10
Compiler+version: VS2019
Conan version: 1.26
Python version: 3.8

Steps to reproduce (Include if Applicable)
Write a simple build.py
from conan.packager import ConanMultiPackager

if __name__ == "__main__":
    builder = ConanMultiPackager(visual_runtimes=["MD", "MDd"])
    builder.add_common_builds(shared_option_name=False, pure_c=False)
    builder.run()

Run it.
It tries to use not installed VS versions 14 and 15. When I have 16 installed.
Logs (Executed commands with output) (Include/Attach if Applicable)
conans.errors.ConanException: VS non-existing installation: Visual Studio 14

Hello @Ri0n !
CPT doesn't check compiler/build system, it runs a matrix with all possible combinations by default. This is well explained here: https://github.com/conan-io/conan-package-tools#generating-the-build-configurations-automatically
If you have only a version installed, you should set the environment variable CONAN_VISUAL_VERSIONS=16 as described on the README file.
Regards

Thanks.
Is there any configuration file for such things to not mix with system env?
I tried to limit VS versions via conan settings files. but package tools ignore them. That's weird.

repo: conan-io/conan-package-tools


text:
Typing after each message sent

Hi,
First, thank you for this great job, I were able to build almost perfect chatbot with your library 👍
I just have one issue (in addition to missing pictures in quick-replies):
My chatbot is typing almost after every message is sent (just a few seconds and then typing becomes off). I don't know why. I tried to add a page.typing_off(recipient_id) after every page.send(...) but it does nothing. My bot is still typing after each message...
Do you have any solution?
Thanks
EDIT : Moreover, I do not understand how it could be possible to see typing on with my chatbot regarding the fact that I actually never called page.typing_on() in all my code. Is there an "auto typing on" implemented with your library? I can't find it...

I have the same issue even the fact I'm not using this library ... I wonder if the problem is not coming from elsewhere... It seems to only appear after a postback button (in my case)

Could it be linked to this error I get every time I push a postback button ?
('Webhook received unsupported Entry:', {u'id': u'769783789855499', u'time': 1513414644813, u'standby': [{u'timestamp': 1513414644813, u'postback': {u'title': u'Red\xe9marrer'}, u'sender': {u'id': u'1693939997299999'}, u'recipient': {u'id': u'769783789899999'}}]})

authors: timdid yafeunteun

repo: conbus/fbmq


text:
185493638 document flipper

In workspace and class work > starred tabs, adds arrow buttons to the open document to open the prvevious or next document in the list.

@tealefristoe Made the your review changes and refactored the document view to its own component to memoize the starred documents. Also made some minor logic changes in anticipation to next part of this feature (the 2 document flipper).


text:
9.0.2 Accordion Block Body content missing

Affected Version of Concrete CMS
9.x
Description
Content in the Body text editor in the add or edit forms is not saved.  Accordion only displays title and no text.
How to reproduce
Add block to page
Possible Solution
No response
Additional Context
No response

I don't know why, it didn't work when I tried it on two sites, then it started working.  Maybe something with the browser. sorry


text:
File Manager Service Doesn't Obey Form Folder Settings

Use the Dashboard File Manager to create a new Folder (say ‘Fold’).
Add Form block (not ‘legacy’)
Select ‘New Form’ (not ‘Express’)
Add question with Answer Type of Image/File, and Input Format of ‘File Manager Selector’.
In the form Options, specify that files should be uploaded to ‘Fold’ (and not ‘File Manager’).
Save and publish.
Use the form to open the File Manager service. Note that the File Manager opens in the root folder, rather than Fold (which would probably be more useful).
Without changing folder to ‘Fold’, upload a file.
Expected behaviour: the file should be placed in ‘Fold’, as specified in the Form Options.
Observed behaviour: the file is stored in whatever folder was open at the time, ignoring the Form Options. If the Form Options don’t apply to files uploaded through the File Manager, the UI should not expose those settings.
It is desirable to be able to use the File Manager service to constrain non-admin users to a single folder so they can’t scatter files elsewhere, and to simplify things for them.

The folder settings only apply to files uploaded using the HTML input. Using the file selector in this way from a front-end form wasn't something we really anticipated. Certainly reasonable but a pretty lower priority use case.

authors: aembler gondwanasoft


text:
[9.0.0RC4] Forced Trailing Slash During Install (Install Loop)

On fresh install at https://site.com/index.php/install I choose a language, and I'm taken to the pre install checks.  I continue to install and again I'm at the url https://site.com/index.php/install being asked to choose a language.  Simply adding a trailing slash to the url, https://site.com/index.php/install/ , will initiate install.  Otherwise it's a mad loop.
This is something I've been seeing since many many versions ago, at least 8.5.4ish if it hasn't been before that.  I've mentioned it here or there with little feedback, leading me to believe this may be server related.  I typically turn trailing slashes on, but they are disabled on my server by default during install.  Not a server guru so I'll provide any info as needed rather than crazily pasting away.  Hoping someone may be able to reproduce this or could help find what the issue is...

Anybody else seeing this?

authors: aembler ccmEnlil


text:
Stored XSS prevention in  form elements [fixes H1 247529,247520]

Hi Guys,
This is more general fix, which should prevents  elements against Stored XSS attempts.
For now this change resolves:
https://hackerone.com/reports/247529
https://hackerone.com/reports/247520
but should fixes any other XSS issues in  elements as well.
Regards,
bl4de

Won't this break backward compatibility? There are a ton of places that already run htmlspecialchars on content before they send it into the textarea.

That's a good question actually, so I've made some simple test to check it (although I am sure that calling htmlspecialchars() or htmlentities() on value previously parsed by those functions has no effect).
So here's my test script:
<?php
ini_set('display_errors', 0);

// from concrete/src/Utility/Service/Text.php
function specialchars($v)
{
    return htmlspecialchars($v, ENT_QUOTES, APP_CHARSET, false);
}

// from concrete/bootstrap/helpers.php
/**
 * Security helper.
 *
 * @param string $input
 *
 * @return string mixed
 */
function h($val)
{
    return specialchars($val);
}

// ---------------------------------------------------------------------------

$value = '"></textarea>';

// ---------------------------------------------------------------------------

?>

    <form action="">
        <textarea>
            <?= $value; ?>
        </textarea>
        <textarea>
            <?= h($value); ?>
        </textarea>
        <textarea>
            <?= h(h($value)); ?>
        </textarea>
        <textarea>
            <?= h(h(h($value))); ?>
        </textarea>
    </form>

And here's the result:

    <form action="">
        <textarea>
            "></textarea>        </textarea>
        <textarea>
            "></textarea><script>alert("XSS")</script>        </textarea>
        <textarea>
            "></textarea><script>alert("XSS")</script>        </textarea>
        <textarea>
            "></textarea><script>alert("XSS")</script>        </textarea>
    </form>

First textarea is just plain $value, so XSS payload executes.
Other payloads are sanitized as expected, only once.
Hope this helps you to provide valid solution.
Regards,
bl4de

Hi @aembler,
Please take a look at my comment here:
https://hackerone.com/reports/247529#activity-1860201
Regards,
bl4de

This was resolved.

authors: KorvinSzanto aembler bl4de


text:
Py312 migration

Checklist

[X] Used a personal 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)
[ ] 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

The re-rendering is hit again by https://github.com/conda-forge/conda-forge-pinning-feedstock/issues/4190. Some files need to updated to replace the PyPy implementation with CPython before this PR can be merged.

repo: conda-forge/basemap-feedstock


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

[ ] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

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

authors: conda-forge-linter ngam

repo: conda-forge/botorch-feedstock


text:
PR: Add 1.5.1 version

Checklist

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

Is there something wrong with https://github.com/conda-forge/cached-property-feedstock/pull/7  ? I'm inclined to merge that one given that it's been automatically updated.

@mvdbeek nope, I just missed that PR and made this one also :-\ , I can close this one

Thanks, I just merged the other one!

authors: goanpeca mvdbeek

repo: conda-forge/cached-property-feedstock


text:
Make noarch

Checklist

[x] Used a personal 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.

This PR makes this package noarch, by replacing the windows only dependency with one that works on all platforms.
Ref: https://github.com/conda-forge/pywin32-on-windows-feedstock

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

@nehaljwani Quick ping, if you have a sec.

authors: BastianZim conda-forge-linter

repo: conda-forge/certbot-feedstock


text:
Rebuild for RDKit 2023.03.1

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.

@conda-forge-admin, please rerender

repo: conda-forge/chemicalite-feedstock


text:
Update meta.yaml

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)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

repo: conda-forge/datastock-feedstock


text:
correct license

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)
[ ] Ensured the license file is being packaged.

The license for this package was specified as BSD-3, but it is and has always been MIT licensed.

@fpottbaecker, thank you for noticing this.  I have no idea where this mistake crept in.

I think I now understand.  The license is both MIT and PSF-2.0 in a single file, which confused grayskull into somehow thinking the BSD was the least bad match.

authors: fpottbaecker xylar

repo: conda-forge/exceptiongroup-feedstock


text:
Updated geemap feedstock to v0.7.6

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 giswqs

repo: conda-forge/geemap-feedstock


text:
rerender with conda smithy 3.3.0

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.

@conda-forge/gettext

authors: conda-forge-linter notestaff

repo: conda-forge/gettext-feedstock


text:
Rebuild glib-split for 2.64.6

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] 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)
[ ] 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.

This is basically applying the same split that's now on master, right?

Yes!

authors: conda-forge-linter xhochy

repo: conda-forge/glib-feedstock


text:
Align conda-forge.yml with ignition repo

Checklist

[x] 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)
[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.

@conda-forge-admin, please rerender

The linux_aarch64 emulate build is taking too much, I switched to cross-compile even there.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin please restart ci

Probably makes sense to set
https://github.com/traversaro/gz-math-feedstock/blob/ec605ba6dae0d67ffea45e7e220fefa6d92ff40f/conda-forge.yml#L2
to linux-64 instead.

Probably makes sense to set https://github.com/traversaro/gz-math-feedstock/blob/ec605ba6dae0d67ffea45e7e220fefa6d92ff40f/conda-forge.yml#L2
to linux-64 instead.

I can't find the log, but unfortunatly this resul in an error. I wanted to get a first build with aarch64 in so to unblock the sdormat13 build, then we can investigate the issue in a dedicate PR.

Probably makes sense to set https://github.com/traversaro/gz-math-feedstock/blob/ec605ba6dae0d67ffea45e7e220fefa6d92ff40f/conda-forge.yml#L2
to linux-64 instead.

I can't find the log, but unfortunatly this result in an error. I wanted to get a first build with aarch64 in so to unblock the sdormat13 build, then we can investigate the issue in a dedicate PR.

See https://github.com/conda-forge/gz-math-feedstock/pull/4 .

repo: conda-forge/gz-math-feedstock


text:
windows Ipopt executables crash , while NEOS or OSX or Linux  versions always succeed

Forgive me if this not totally the right place to post my concern.
But I understand you are blacksmiths for Ipopt, therefore I guess you might help.
I have posted this topic for the first time on Coin-Or .
You can find the details there, as well as two test .nl files that I also zipped here.
In summary.
I have used windows versions of Ipopt (from Pyomo) with reasonably few difficulties (few crashes, few numerical problems).
However, I have now big troubles with a family of 50 problems of various sizes.
For more than 80% of the models, Ipopt crashes with an access violation.
The same models are always running perfectly well on Neos, Notebooks Azure and OSX .
My impression is that a memory leak is involved.
I tested that issue on several versions of Ipopt (3.7, 3.10, 3.11, 3.12, w32, w64, Coin, conda-forge) .
The rate of failure may change but remains always very high.
I read a little bit here about difficulties to create windows executable versions.
This convince me that I should probably not try to do it by myself.
Thanks for your help,
Michel
test.nl.zip
test2.nl.zip

New test on window. I downloaded IPOPT (v3.9.1) from http://apmonitor.com/wiki/index.php/Main/DownloadIpopt .
It is interresting that this command line works succesfully, unlike other windows versions tested so far:
"ipopt 3.9.1" test2
Unfortunately, the command line to get the sol file crashes like the other windows version:
"ipopt 3.9.1" -s test2
Maybe this gives a little more information ?
Michel

repo: conda-forge/ipopt-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.0.0) 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/iris-feedstock


text:
0.4.1

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.

@conda-forge-admin, please rerender

authors: conda-forge-linter zzhengnan

repo: conda-forge/iscan-feedstock


text:
Build ITK from Source

This PR addresses https://github.com/conda-forge/itk-feedstock/issues/2. Instead of building packages from the pypi wheels, transition to building from source (with python bindings). This allows important optional modules (such as itkv3 compatability and itk review) to be included in build.
I'm unsure if this will be built correctly, as I am unfamiliar with the conda-build toolchain package to set environment variables. Also, we may run into build time issues on MacOS, as the swig wrapping takes a long time (even when building locally), we may have to circle ci for macos to alleviate this problem
@msarahan, sorry for the tag, but I haven't received replies from the current maintainers in my last issue  https://github.com/conda-forge/itk-feedstock/issues/2. Wondering if you could give this recipe a quick review or if you could point me to the appropriate person on the conda-forge core team?

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.

Use other conda-forge pacakges instead of using the vendored copy. For eg: HDF5, jpeg, GDCM

Also, if there are third party libraries being built that are not in conda-forge, I suggest adding separate packages for them.

got it! updating now

Closing. This functionality is available in the libitk repo

authors: conda-forge-linter isuruf rlizzo

repo: conda-forge/itk-feedstock


text:
Fix system libcxxabi leaking in

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.

cc @jschueller, @mingwandroid, no warnings now.

Great work @isuruf. Thank you!

My rebuild is in progress now. Fingers Crossed.

authors: conda-forge-linter isuruf mingwandroid

repo: conda-forge/libcxx-feedstock


text:
release 0.4.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 (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:
Windows package

Checklist

[x] Used a personal 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)
[ ] 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

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@egallicc, this builds Windows packages of the plugin. We need it for the deployment on GPUGRID.


text:
Upgrade to 0.1.7.post4

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.

Bumps version to 0.1.7.post4 which adds support for numpy 2.

Thank you very much, it looks good to me, just a small question due to my own lack of CMAKE expertise.

@adament What is your CMake-related question? While I did not author the original patches, maybe I can help.

I am very sorry, I am not familiar with github reviews so I forgot to submit my question.

authors: adament sebp

repo: conda-forge/qdldl-python-feedstock


text:
REL sklearn-compat 0.1.2

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] 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.

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.

authors: conda-forge-admin glemaitre

repo: conda-forge/sklearn-compat-feedstock


text:
Add automated deps update with grayskull

Checklist

[x] 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)
[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.

I do not know if this works if the source tarball is not from pypi.

What about using inspection: update-source or inspection: update-all?

Alright, I'll leave it like this and eventually we can disable it in the future

Alright, I'll leave it like this and eventually we can disable it in the future, if you agree

Ok for me.

authors: flferretti traversaro

repo: conda-forge/warp-lang-feedstock


text:
version 0.14.2

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.

@conda-forge-admin please rerender

repo: conda-forge/wgpu-native-feedstock


text:
yamllint 1.23.0, pip check

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] 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.

Notes

alternative to #22 (thanks @wbadart!)
adds pip check
cleans up some syntax, hopefully more findable by the autotick bot
removes rest of attempt to lint itself... perhaps another day

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: bollwyvl conda-forge-linter

repo: conda-forge/yamllint-feedstock


text:
Fix issue: Return 404 instead of 2xx codes for methods handling non-existent tasks#38

Pull Request type

[x] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] WHOSUSING.md
[ ] Other (please describe):

NOTE: Please remember to run ./gradlew spotlessApply to fix any format violations.
Changes in this PR
Describe the new behavior from this PR, and why it's needed

Issue #
Alternatives considered
Describe alternative implementation you have considered

Note that changing /poll and /poll/batch can break clients (since the expected codes were 200 with content if I get homework, and 204 without content if there was none).
If you also want those methods to give 404, this change should be labeled as BREAKING CHANGE.

@JCHacking, are you suggesting that we undo the code changes for /poll and /poll/batch to maintain the current behavior?

@JCHacking, are you suggesting that we undo the code changes for /poll and /poll/batch to maintain the current behavior?

No, I think it is more correct that if it fails to get a task it returns 404.
But if you make this change you may have to change the client package as well and the SDKs in other languages.

I don't think that for poll it is more correct to return 404. This could be correct if task definition is not known because in that case it would actually reflect a possible error condition. 204 means operation has no errors but returns no content which is much more correct and it would not break anything.

I don't think that for poll it is more correct to return 404. This could be correct if task definition is not known because in that case it would actually reflect a possible error condition. 204 means operation has no errors but returns no content which is much more correct and it would not break anything.

You right

I will rever the code to make the poll APIs return 204.

authors: JCHacking dcore94 vgopari

repo: conductor-oss/conductor


text:
any interest in getting this working with the new Benthos project ?

Benthos was taken over Redpanda
It's not all bad news as the code is still there.
https://github.com/redpanda-data/benthos
import is now: github.com/redpanda-data/benthos/v4

https://github.com/united-manufacturing-hub/benthos-umh has also changed over

@gedw99 Sorry for the late reply, it somehow got lost among many other notifications.:) For now, the Conduit team itself doesn't plan to invest any time in this connector.


text:
Unclear that Commit with enumerable of offsets will commit at N-1

Commit with ConsumeResult commits at Offset + 1
Commit with IEnumerable offsets commits at offset.
        /// <remarks>
        ///     A consumer at position N has consumed
        ///     messages with offsets up to N-1 and will
        ///     next receive the message with offset N.
        ///     Hence, this method commits an offset of
        ///     <paramref name="result" />.Offset + 1.
        /// </remarks>
        void Commit(ConsumeResult<TKey, TValue> result);

https://github.com/confluentinc/confluent-kafka-dotnet/blob/d65c05a5a1e6e2a0df4745cdf1c50ebc7a1aeae9/src/Confluent.Kafka/IConsumer.cs#L356

that's correct. void Commit(ConsumeResult<TKey, TValue> result); is a convenience method that 'helps' you by defaulting to the behavior you probably need. the IEnumerable overload works explicitly as defined. the docs would be better if they explicitly called out the difference.

authors: anthonyz-orange mhowlett

repo: confluentinc/confluent-kafka-dotnet


text:
When creating broker datadir directories, you cannot specify multiple datadirs

If I override the datadir to be /dir01,/dir02,/dir03, the parameter logs.dir is correct in server.properties - but it also tries to create the directories with a mkdir command which fails because it takes it as "mkdir /dir01,/dir02,/dir03" instead of 3 separate mkdir commands "mkdir /dir01; mkdir /dir02; mkdir /dir03"

Agreed, the code expects an array

repo: confluentinc/cp-ansible