Consolidate Bot section

The #organization/bot-list-admin URL is now deprecated in favor of the new #organization/bots/{tab_name} URL by default tab_name will all-bots.

As mentioned in the issue,  PERSONAL > BOTS  is renamed as Your bots. Clicking on this renamed tab will redirect you to ORG SETTINGS > BOTS with the Your bots tab pre-selected.

If the user has one or more active outgoing webhooks, the botserverrc text has been added to the Your bots section. ( This was not mentioned in the issue description ).

Originally, my plan was to create two separate commits: one for splitting the bot section and another for consolidating information in the "Manage bot" tab. However, due to Puppeteer tests, I had to combine these changes into a single commit.

fixes #31156

Light
Dark

api and zuliprc
bot type

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@zulipbot add "buddy review"

@adnan-td  can you review this one?

@adnan-td are you up for reviewing this one ?

Removed conflicts ready for review

Some things I noticed:
In "all bots" tab, when we add a bot, I feel like tab should switch to "your bots". What do you think @sujalshah-bit?
For non-admins, "your bots" should be opened by default as suggested by @alya.
Suggestions for "Manage bot" tab of the bot profile:

Styling for api key and Tooltip for copy api key button

I feel like there should be some design changes to make it feel different from text.

Spacing issue below avatar

Thanks @adnan-td for the review

In "all bots" tab, when we add a bot, I feel like tab should switch to "your bots". What do you think @sujalshah-bit?

yeah it make sense to switch to your bot section.

For non-admins, "your bots" should be opened

alya said that :

From the organization settings, "All bots" should open by default (perhaps just for admins?).

What I believe is when a user, particularly a non-admin, navigates to the bots section through the organization settings, it is most likely that they want to view all the bots available to them. This is because they can already access their personal( your bots)  bots section through the link provided in their personal settings.

I feel like there should be some design changes to make it feel different from text.

I agree to you in this point because it looks not so good in manage bot section although this what style we currently have for the fields (api key and others ) in personal bot settings.  may be should start a design discussion?

Spacing issue below avatar

I don't think it is related to this PR
@alya can you look all the points here to clarify things further ?

In "all bots" tab, when we add a bot, I feel like tab should switch to "your bots". What do you think @sujalshah-bit?

Mm, possibly! Let's put that in a separate commit in case we change our minds.

@sayamsamal is making changes to the copy button for #28700.
@sayamsamal could you please review the copy button-related changes on this PR? You know best how we should manage that part of the work.

What I believe is when a user, particularly a non-admin, navigates to the bots section through the organization settings, it is most likely that they want to view all the bots available to them. This is because they can already access their personal( your bots) bots section through the link provided in their personal settings.

That sounds reasonable to me.

Testing the PR, we should make sure to show the appropriate message when no bots match the filter (active/deactivated and/or search terms).
Before the PR:

After:

I agree to you in this point because it looks not so good in manage bot section although this what style we currently have for the fields (api key and others ) in personal bot settings. may be should start a design discussion?

Yeah, it would be great if you could start design discussion. We sometimes use the pattern of showing info you can't edit in a disabled text field:

In personal settings, the API key is shown like this (which I don't especially like):

If someone has a bot, they should have buttons for managing it even if organization settings have been changed so that they can no longer add one.

Overall, I think this direction feels good!

Regarding your last https://github.com/zulip/zulip/pull/31164#issuecomment-2337211626 I don't understand which button are you referring to ? can you please elaborate on this one ?

The "Edit" and "Deactivate" buttons for the user's bot are missing. The user doesn't have permission to create new bots, but they should still be able to modify the ones they have.

Do you agree with this direction? should I remove the API key changes and stick with the feedback you provided in https://github.com/zulip/zulip/pull/31164#issuecomment-2337199791?

The uneditable fields approach looks reasonable to me!

You can add the "maintainer review" label and ping @sahil839 for review whenever all the feedback above has been addressed.

@zulipbot add "maintainer review"

@zulipbot remove "buddy review"

One thing about changes to show the message when list is empty. For bots, we always have either "Active" or "Deactivated" option selected, so how we decide whether we show the message which mentions that there are no bots matching the filter, as we always have at least one of them selected.

Hmm, can we have a custom message that depends on which option is selected? And only show the generic not matching bots message when there is a filter query as well?

Yes, that sounds good.


285 MB of perf profile data was packaged as part of 3.8.0

It looks like tslint 3.8.0 was uploaded with 285 MB of perf profiling data with it. It's causing exceedingly long "npm install" times for everyone.

Oh no! This is completely my fault - very sorry that those performance
profiles got included. I'll fix it when I can get back to a computer next
On Sun, Apr 24, 2016, 7:40 PM David Federman<EMAIL_ADDRESS>wrote:

It looks like tslint 3.8.0 was uploaded with 285 MB of perf profiling data
with it. It's causing exceedingly long "npm install" times for everyone.
[image: image]
https://cloud.githubusercontent.com/assets/6445614/14771280/3d3477a8-0a3b-11e6-820a-244e505f426b.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/palantir/tslint/issues/1160

Thanks!

Oops, didn't mean to close. I'll let you do that when you upload a new version :)

This should be all fixed up in now-published version 3.8.1, thanks again for noticing @dfederm!


Some updates to the Pycache, changed Linux guide.

Fixed up the linux guide. I can't say for other distributions of Linux, but it at least works on Fedora now.

Good work!


[Code cleanup] Refactor HomeScreenViewModel

Replace disposeOnClear with LiveData for add feature requests
Expose handler to fragment for UI interactions
Add tests for FeatureRepository

@gino-m  PTAL

Please avoid force-pushing if possible, since it erases your edit history and it makes incremental reviews impossible ;)

@gino-m Resolved the comments and added tests for the new behavior

@gino-m PTAL. I've updated the PR with the requested changes

@gino-m Ping.

@gino-m Ping.

Sorry didn't know if it was ready! Note for next time you can also re-request review to get my attention:


Using with npm enterprise

I am currently working with our companies own private npm enterprise registry. I have code very similar to this repo but the changes-stream library is returning a 404 for the couch db. However I am getting the registry data in the response body. Here is the output
body {"db_name":"registry","doc_count":10,"doc_del_count":0,"update_seq":95,"purge_seq":0,"compact_running":false,"disk_size":1347688,"data_size":129773,"instance_start_time":"1510780609538097","disk_format_version":6,"committed_update_seq":95}
error null
events.js:182
      throw er; // Unhandled 'error' event
      ^

Error: Received a 404 from couch
    at ChangesStream._onResponse (/Users/griffin/sandbox/registry-follower-tutorial/node_modules/changes-stream/index.js:155:15)
    at Object.onceWrapper (events.js:314:30)
    at emitOne (events.js:120:20)
    at ClientRequest.emit (events.js:210:7)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:549:21)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23)
    at TLSSocket.socketOnData (_http_client.js:438:20)
    at emitOne (events.js:115:13)
    at TLSSocket.emit (events.js:210:7)
    at addChunk (_stream_readable.js:263:12)

This approach with changes-stream should work with enterprise registries since it is still using couch DB right? Currently our registry is running in a Docker container on a VM.
Any suggestions would be much appreciated! Thanks

oh this is a very interesting question @gciluffo ! sorry for the delay, i'll talk to my colleagues and see if i can figure out what's up. i would suspect it should work but i can also imagine a few spots that might make it tricky. i'll let you know what i figure out!
cc @bcoe @arobson

I got it working. But I had to write the service in the VM where the npm couch db lives. And then used forever/npm to run it.


feat(ROS-38): use managed vectordb

don't want to restart every time
WIP haven't validated all flows, need better UX on initializing

looks great good job buddy


'002422.XSHE'，卖出报错。开始时间：20220829； 结束时间20220901

Describe the bug
9月1日早盘获取开盘价后进行回测运算。'002422.XSHE', 卖出报错。
2022-09-01 00:00:00 持仓：
[('603955.XSHG',  6400.,  6400., 18.28000122)
('002422.XSHE',  5200.,  5200., 22.4       )
('002615.XSHE', 14400., 14400.,  8.12      )
('600775.XSHG', 11900., 11900.,  9.81000066)]
按比例卖出股票 failed: 499, Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/backtest/common/helper.py", line 83, in decorated_function
result = await f(request, *args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/backtest/web/interfaces.py", line 239, in sell_percent
result = await request.ctx.broker.sell(security, price, sellable, order_time)
File "/usr/local/lib/python3.8/dist-packages/backtest/trade/broker.py", line 1087, in sell
return await self._sell(*args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/backtest/trade/broker.py", line 1096, in _sell
await self._before_trade(bid_time)
File "/usr/local/lib/python3.8/dist-packages/backtest/trade/broker.py", line 803, in _before_trade
await self._fillup_positions(bid_time)
File "/usr/local/lib/python3.8/dist-packages/backtest/trade/broker.py", line 837, in _fillup_positions
dr_info = await feed.get_dr_factor(secs, frames)
File "/usr/local/lib/python3.8/dist-packages/backtest/feed/zillionarefeed.py", line 114, in get_dr_factor
async for sec, bars in Stock.batch_get_day_level_bars_in_range(
File "/usr/local/lib/python3.8/dist-packages/omicron/models/stock.py", line 291, in batch_get_day_level_bars_in_range
cached = await cls._batch_get_cached_bars_n(frame_type, 1, end, codes)
File "/usr/local/lib/python3.8/dist-packages/omicron/models/stock.py", line 822, in _batch_get_cached_bars_n
barss = numpy_append_fields(barss, "code", codes, [("code", "O")])
File "/usr/local/lib/python3.8/dist-packages/omicron/extensions/np.py", line 299, in numpy_append_fields
result[names[i]] = data[i]
ValueError: could not broadcast input array from shape (4,) into shape (0,)

错误因omicron导致。升级后解决了这个问题。


Rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/pdfrw-feedstock#3.


Implement highlighted today element in calendar

Background or text color can be overriden via scss labels, default is #c00 for the text.
Fixes #202

Thanks for the PR - unfortunately, per https://github.com/dalelotts/angular-bootstrap-datetimepicker/blob/master/contributing.md, I am closing without review because tests are failing and there are no tests for the new functionality.
Please write tests for this PR and re-submit. You might also consider ways of representing "today" on the hour and minute views.

Sorry about that, the new test file got dropped up when I rebased to develop apparently. There's a new PR that includes the tests. I don't see any travis results or anything on this commit so it's hard to know what failed, but both gulp, gulp test and gulp tdd are all succeeding for me locally on the new PR


Overlord for review

@gguntupalli Looks mostly good. Resubmit with changes based on comments.

Looking good.  Please look at the comments, refactor and resubmit.


ci: Add Staging Process (Step 1) for Phased Rollout

Instructions

PR target branch should be against development
PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

Adds a staging process for phased rollout, using a staging branch as an intermediary before releasing to master/main.

Testing Plan

[ ] Was this tested locally? If not, explain why.
N/A - this is a CI/CD change

Reference Issue (For mParticle employees only.  Ignore if you are an outside contributor)

Closes https://go.mparticle.com/work/SQDSDKS-5706

:tada: This PR is included in version 2.24.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(dispatch): added example simulation runs with visuaulizations using SBGN PD maps

Adds seven additional example simulation runs (two presently disabled due to issues with simulation tools)

Model languages: CellML, SBML
Simulation algorithms: CVODE, LSODA, other
Seven simulation tools

Also

Updated to BioSimulators-utils 0.1.103
Added documentation for SBGN PD -> Vega converter

:tada: This PR is included in version 3.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Error: (401) Unauthorized

Hi,
i'm currently facing an issue due an outdated dependencie (agent-base) :
HTTPError: Response code 401 (Unauthorized)
    at Request.<anonymous> (/home/adrien/Documents/dropshapp/node_modules/got/dist/source/as-promise/index.js:117:42)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  code: undefined,
  timings: {
    start:<PHONE_NUMBER>470,
    socket:<PHONE_NUMBER>474,
    lookup:<PHONE_NUMBER>737,
    connect:<PHONE_NUMBER>745,
    secureConnect:<PHONE_NUMBER>764,
    upload:<PHONE_NUMBER>765,
    response:<PHONE_NUMBER>120,
    end:<PHONE_NUMBER>133,
    error: undefined,
    abort: undefined,
    phases: {
      wait: 4,
      dns: 263,
      tcp: 8,
      tls: 19,
      request: 1,
      firstByte: 355,
      download: 13,
      total: 663
    }
  }
}

According to agent-base, the error has been fixed in version >= 5, could you please update your dependencies ?
(node:6408) [DEP0139] DeprecationWarning: Calling process.umask() with no arguments is prone to race conditions and is a potential security vulnerability.
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └──<EMAIL_ADDRESS>

Please update to latest version v2.0.2. All issues are fixed.


Exponent app reinstalls every time iOS Simulator opens

XDE 2.9.0 - Mac OSX 10.12 - iOS Simulator 10.0
Actual

iOS Simulator is closed
Click on "Device" toolbar item in XDE
Choose "Open on iOS Simulator
Notice following error message in XDE Logs:

12:18:27 PM Opening iOS simulator
12:18:27 PM Opening exp://localhost:19000 in iOS simulator
12:18:41 PM Error running `xcrun simctl openurl booted exp://localhost:19000`:
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=60):
The operation couldn’t be completed. Operation timed out Operation timed out
12:18:41 PM Error running app. Uninstalling exponent and trying again.
12:18:41 PM Uninstalling Exponent from iOS simulator.
12:18:41 PM Downloading latest version of Exponent
12:18:42 PM Installing Exponent on iOS simulator
12:18:46 PM Opening exp://localhost:19000 in iOS simulator

Expected
Exponent app should not be uninstalled and reinstalled every time.

I think this is a bug with the simulator. See: http://stackoverflow.com/questions/24233589/xcode6-cant-run-any-app-in-simulator-domain-nsposixerrordomain-code-3
Looks like people have had success with rebooting or clearing the simulator

Sorry again for not searching better for a solution.  I just switched my hardware device in the simulator and then switched it back.  Not sure what it jostled, but everything is working again.

No worries, thanks for letting us know! I'll add a note to add some suggestions when this error happens

I am facing this too. But, happens when I remotely debug.

@shettyrahul8june - can you provide exact repro steps? what platform? simulator/emulator or device?

@brentvatne Sure.
Steps to reproduce:

Start Expo XDE
Go to your respective project
Once the project is opened, Click on Devices -> Open on iOS Simulator.
Simulator (iPhone 6 - iOS 10.3) fires up.
Javascript builds successfully and the project starts successfully but below is the error that I get:

@shettyrahul8june - did you read the original answer by @jesseruder? This can happen when the iOS simulator is in a bad state, the solution is to Reset Content and Settings

I read. And I did reset and start everything again. But, I still see the error.

@shettyrahul8june - this isn't really anything to do with Expo, it's an iOS simulator error :( you might have better luck googling what the source of that error is and making sure all of your apple developer tools are up to date

@brentvatne Yea. I realised.

I've got the same error

@martinezguillaume I had the issue too, but as @brentvatne kept saying this isn't an Expo problem but instead is an issue with the ios simulator.
I eventually quit expo, re-opened, selected my project to open it, once open restarted the project, then opened the ios simulator. I still see the error now and then but my project opens successfully in the simulator.

I have this issue as well.

I have this issue as well.
Currently updating mac os sierra and then will update xcode. Hope it solves the problem.

@shettyrahul8june did you figure out what is going on? I am getting the same error 🗡

@jonieldasilva I can still see the error but fortunately, it doesn't mess up with the project. I see only when I start the simulator. After that, I can continue developing without any errors. So for now, I just ignore that error.

I have this issue too. Reset content of the ios simulator does work but every time we need to perform this. Any permanent solution?


export VERSION from @sveltejs/kit

implements #9937
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

I could not test if the CI action actually works, but I would assume it does so

@dominikg you're more familiar with the release process. Do you think this will actually work?

Is it really needed to parse this at publish and generate an extra module?  Can't we just read it from package.json and export?
vite: https://github.com/vitejs/vite/blob/main/packages/vite/src/node/constants.ts#L5

Can't we just read it from package.json and export?

Not in the browser

Can't we just read it from package.json and export?

Not in the browser

do we need it in the browser though? We are already embedding an application version iirc, so we could embed a kit version too with the same mechanism.
If it's possible to prevent this extra moving part i'd prefer it, even if it was a bit more cumbersome to get the verison in browsers (whats the usecase for that)

I mean we can't not allow it in the browser — it would be deeply weird if we couldn't do this sort of thing:

Welcome to SvelteKit version {VERSION}

We could get it into the browser the same way we populate $app/paths and $env/[type]/public — by including it in the


Highlight NPCs when in range

If an npc walks into range, highlight them to show they are attackable.

0e642470516461643f5ebdd91907e5bb2d7d55a9


"NODE_ENV=production node_modules/.bin/webpack -p" produce no bundle.js file

I am working through your amazing article building every js file step by step and finally i have reached this line: "NODE_ENV=production node_modules/.bin/webpack -p".
I have added npm script like this:
"scripts": {
"build": "NODE_ENV=production node_modules/.bin/webpack -p"
}
and get returned an error. And smart guys whispered me that as soon as i am on windows i should prepend script with "set" so i changed it to:
"build": "set NODE_ENV=production node_modules/.bin/webpack -p"
Now i got no errors but no bundle.js file is produced. Simply nothing.
Please help me to figure this out.

I'm having the same issue on windows 10.
I did solve the problem by running set
NODE_ENV=production
and then, as a separate command
node_modules/.bin/babel-node --presets 'react,es2015' src/server.js

try doing something like
"start": "set NODE_ENV=production&&webpack -p"

include &&

Same issue from the git and the website tutorial, blank page when everything is said and done. Seems to be a bundle issue but don't know how to go about it. Please help, this is a great tutorial!

Hei :) Not sure what you did here on other systems but I had to replace the "build" property with "postinstall", as the "build" command just wouldn't run.
Note that I am deplying on Heroku, so it may not apply to you guys.

@EduardJS did you run npm build or npm run build (the latter is the correct one, I know it's always confusing... 😝 )

Just added support for multi-os env variables using cross-env module.

@lmammino I am deploying onto Heroku, using nodejs buildpack. Therefore the running command is "npm start".
And since heroku has a "postinstall" utility for package.json I figured I would just use that instead.
Not sure if there's anything to do, as I didn't bother searching for a fix anyway.
Don't think there's anything to do about that anyway!


completion

bash zsh

asking permission to @i-kiwamu at https://gist.github.com/i-kiwamu/b21a9dc57ba7d2d7c40d

work in progress: https://github.com/roswell/roswell/tree/completion

:+1:

imported the zsh completion script from https://gist.github.com/i-kiwamu/b21a9dc57ba7d2d7c40d at 9842343d53e98a7f99f019e49b4cf56ee2686da6

remaining task:

[ ] current installation/uninstallation script does not manage subdirectory etc/.
[ ] zsh completion quality might not be as good as in bash completion.

I'd like to move files. how about
etc/zsh/functions/_ros -> scripts/completion/ros-completion.zsh
etc/bash-completion.d/ros -> scripts/completion/ros-completion.bash

They are the directories zsh/bash (resp.) search for completion scripts by default, at least on linux systems. Wouldn't it be the same for OSX? They wouldn't affect Windows users, either.
I am not familiar with autotools, so Id like someone to write the rules for copying them in Makefile.am.

I think there are no relationship between where it placed in repository and where it installed on system.
Just I prefer how it placed like git project.
https://github.com/git/git/tree/master/contrib/completion

I am not familiar with autotools, so Id like someone to write the rules for copying them in Makefile.am.

Sure. I will.

done.

thanks


Error importing a filename with a unicode character stopped import of rest of library

What version of Music Assistant has the issue?
2022.6.6
The problem
I have a music library mounted from my NAS via SMB to /media/music. I have "filesystem provider" enabled for this path in the music assistant integration configuration. The integration successfully imported 38 albums from the library, but then encountered a FileNotFoundError on one of the files, which stopped the entire import. When I fixed the problem with the filename, the rest of the import proceeded okay. I expect you want the filesystem provider to be more resilient than this.
How to reproduce
Place a file named "test∕file.flac" (note the unicode division slash character) in a smb mountpoint that is scanned by the filesystem provider. Wait for it to do a scan and you should see the crash error in the HA core log. This might also be reproducible simply by placing a file with this name, or possibly any unicode character, in a regular local directory read by the filesystem provider.
Relevant log output
Logger: music_assistant
Source: /usr/local/lib/python3.9/site-packages/music_assistant/mass.py:244
First occurred: 26 June 2022, 15:55:56 (7 occurrences)
Last logged: 09:20:53

Job [Library sync for provider Filesystem] failed with error [Errno 2] No such file or directory: '/media/music/ALBUM/The?Song.flac'.
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/music_assistant/music_providers/filesystem.py", line 158, in sync_library
    stat = await asyncio.get_running_loop().run_in_executor(
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
FileNotFoundError: [Errno 2] No such file or directory: '/media/music/ALBUM/The?Song.flac'

(I have replaced the original path with ALBUM/The?Song.flac above. The important part is the "?").
Additional information
The problem with the file was that it included a unicode character in its filename that confused either SMB or hass-music-assistant's filesystem provider. On the filesystem the "?" in the filename is actually the unicode division slash U+2215 "∕ ".  When the filesystem provider tries to read the file, it seems to have replaced that unicode character with a "?", causing a FileNotFoundError. This error seems not to be handled, and seems to have crashed the entire import. This seems consistent with python code that calls .encode("ascii", "replace") on the filename, which would replace unicode with the ascii "?", and subsequently not find the file.
I got around this by finding the offending file and removing the unicode character. This allowed the rest of the library to import. I did not test if the same error is reproducible with a local file containing this unicode character, but I suppose it probably is and would therefore be a bug you would like to fix (even if that just means logging a warning and skipping the problem file).
What version of Home Assistant Core are your running
2022.6.0
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
ODROID

Thanks for your issue. We had a similar issue a while ago with an ' in the name. As we couldn't reproduce, I guess the user had an Unicode in the name as well.

This error is induced by Python builtin libraries, not Music Assistant, completely crashing.
I am going to catch the exception and log it so the scan does not halt completely but I do like to note that probably SMB is to blame here as the only time it happens is on smb mounted locations.
I can not reproduce the issue on my setup and tried several unicode characters in the filename.
Anyways, I'll fix the bug in MA to not choke on the FileNotFoundError so you can at least spot what's going on but the real fix is probably somewhere else.

I agree, not chocking is the only thing needed on MA side to close the issue👍

should be fixed in 2022.6.7, if not please reopen, thanks!


PCR-698 Validation/popup chngs in all applications

PCR-698 Validation/popup chngs in all applications

PCR 698, 703


Missing references to identifiers staticcrt and native in vcpkg/triplets/**

Hi,
I'm the maintainer for vcpkgx.com and recently I've found that both the native and staticcrt identifiers are never referenced in the triplets folder.
I'll be fair by acknowledging that native is at least kind of documented in the predefined identifier expression in the supports section of the manifest documentation
But staticcrt is nowhere to be found.
Is your feature request related to a problem? Please describe.
It's a problem for external tools makers because the triplets folder is the only reliable source for what kind of identifiers can be expected in the supports field of a manifest. This force community tool maintainers to keep hardcoded "patch"  to allow complete evaluation of a supports field in a manifest like in this exemple
Proposed solution
If possible can stubs of empty cmake files  be created under the triplets/** containing the missing identifiers. But even now I'm not convinced that this is the best solution. (Consider this an open discussion.)
Describe alternatives you've considered
That an index could be maintained/generated somewhere in the repo?
But this solution doesn't sound right, because it's not something that should exist in the vcpkg repo, all this data should be derivable from the repo existing data (used for normal vcpkg operation).
Additional context
Nope, everything is at the beginning of the issue.

Hmm... @BillyONeal can you please take a look?
Thanks.

I'm not sure I understand what you mean by a triplet 'containing' the missing identifiers. The triplets don't contain the other identifiers either; they are synthesized from things vcpkg detects from the build environment most of the time, over here: https://github.com/microsoft/vcpkg-tool/blob/1b7edfa7196228006613d96657492e78d3e22043/src/vcpkg/platform-expression.cpp#L43
staticcrt should be on for x64-windows-static, for example (it builds with /MT and /MTd)

To be more precise is that I'm parsing the name of all the cmake files under triplets/** because it's the closest thing to having a full list of identifiers used in the supports  field  and that can be programmatically scraped (for many reasons I would like to avoid parsing a C++ file to get the identifiers).
Just to help me understand how these identifiers can change in the future, lets say I add under triplets/community a file for the RISC-V architecture for linux aka riscv-linux.cmake and in a package I add "supports": "riscv" would I need in the same PR to modify https://github.com/microsoft/vcpkg-tool/blob/1b7edfa7196228006613d96657492e78d3e22043/src/vcpkg/platform-expression.cpp#L43
to add the identifier riscv or would it be ok to just be treated as an invalid identifier https://github.com/microsoft/vcpkg-tool/blob/1b7edfa7196228006613d96657492e78d3e22043/src/vcpkg/platform-expression.cpp#L18?
Also it seams I've taken a shortcut in how I evaluate the supports field by using python eval (why I need all the Identifiers)  (relevant links: status parser, evalEBNF)
So if I rephrase everything, I would like to know where I could get a complete list of all identifiers that can be used in the supports field that can be easily scraped for third party tooling (which the triplets folder is currently the best source from my understanding)

To be more precise is that I'm parsing the name of all the cmake files under triplets/** because it's the closest thing to having a full list of identifiers used in the supports field and that can be programmatically scraped (for many reasons I would like to avoid parsing a C++ file to get the identifiers).

OK, so you're assuming that you can take all the triplet names, separate by -s, and the resulting names will be all the identifiers? That's not generally going to be true and for things like staticcrt and native, cannot be true. You can't have a native "triplet" because whether it's native or not is a property of the "powers combined" of the host system and the triplet. You might be able to theoretically have a staticcrt one but I'm not sure what that even means generally.
In general, the set of identifiers is open ended and is going to increase over time. Moreover, we are likely to extend it to allow users to pass in whatever they want there.
arm32 also doesn't have an associated triplet name.

Also it seams I've taken a shortcut in how I evaluate the supports field by using python eval

That is likely to break soon as we added support for CSS media query syntax for consistency with the ISO SBOM standards (ISO/IEC 5926:2021). https://github.com/microsoft/vcpkg-tool/pull/267

So if I rephrase everything, I would like to know where I could get a complete list of all identifiers that can be used in the supports field that can be easily scraped for third party tooling (which the triplets folder is currently the best source from my understanding)

A complete list is not possible, because the set is arbitrarily extendable by users. However, the authority of the complete list of ones the tool will cough up on its own is currently platform-expression.cpp. We can certainly make a separate doc or something for you?

Also, can you back up a bit and describe why you want to evaluate these anyway? Perhaps we could just give you a command that dumps out a report with the information you need

@Balnian ,Thanks for posting this issue. Please reopen this issue if it still be a problem for you.


ActivityId validation is broken

QName validation is not correct
Steps to reproduce:
Add Service.Task_2 as ActivityID
Problem:
Field validation displays an error
Steps to reproduce:
Add U:serTask2 as ActivityID
Problem:
The following error appears in the console
Error: Failed to execute 'querySelectorAll' on 'Element': '.djs-resizer-U:serTask2' is not a valid selector.     at Error (native)
Expected behavior:
Both IDs are valide ActivityIDs aka QNames

Links to Camunda support project: https://app.camunda.com/jira/browse/SUPPORT-2128

Fixed with https://github.com/bpmn-io/bpmn-js-properties-panel/issues/143


Added The Device Modeling Language (DML)

Add The Device Modeling Language (DML) to the Linguist project.
Add the .dml as an extension for the DML language

Description
The Device Modeling Language (DML) is an open source domain-specific language for writing fast functional or transaction-level device models for virtual platforms. DML provides high-level abstractions suitable for functional device models, including constructs like register banks, registers, bit fields, event posting, interfaces between models, and logging. DML code is compiled by the DML Compiler (DMLC), producing C code with API calls tailored for a particular simulator.
Currently, the compiler supports building models for the Intel® Simics® simulator, but other back-ends may be added in the future.
DMLC is maintained by Intel.

[x] I am adding a new language.

[ ] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?type=code&q=NOT+is%3Afork+path%3A*.dml+"dml+1.4"
For some reason I see 0 repositories. While it's unclear to me if there are 200 unique public repositories. Intel has a lot of code internally written in DML but they are unfortunately in private repositories. The same is the case with customer's using Intel Simics to write their device models using DML.

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

sample-device.dml
sample-interface.dml

Sample license(s): Same as for Linguist project (MIT)

[x] I have included a syntax highlighting grammar: https://github.com/intel/device-modeling-language
[x] I have added a color

Hex value: #0068B5
Rationale: Intel logo and Simics logo are blue.

[x] I have updated the heuristics to distinguish my language from others using the same extension.

This search is quite precise. I assume 1.4 is the version. What about earlier versions? A quick search shows there are some files with dml 1.0, dml 1.2, dml 1.4. Are these the same language?

Yes, they are the same language. However, the syntax is quite different between 1.2 and 1.4, and the grammar file only covers 1.4. Do you have any suggestion regarding how this can be handled?

If we remove your qualifier, we get a lot more files and things look a bit more promising, however a lot of the files returned don't appear to be the same language as you're proposing with this PR as we can see if we exclude the dml 1 string. As a result, these will all be misidentified as this language if this PR is merged as Linguist doesn't know of any other languages with the .dml extension.

There are far more of those other languages than this language if dml 1.? always has to be in the file, so at least one of those other languages needs to be identified and added at the same time in this PR. Your (relaxed?) heuristic will then be used to differentiate the two.

Would you say that if we include 1.0, 1.2 and 1.4 and add also add another language with a .dml extension, there is a chance that support for the DML (as in device modeling language) to be added to Github Linguist? Or is it not popular enough anyway?

Would you say that if we include 1.0, 1.2 and 1.4 and add also add another language with a .dml extension, there is a chance that support for the DML (as in device modeling language) to be added to Github Linguist? Or is it not popular enough anyway?

Even if you add a single entry for all .dml files that contain dml 1, you're still a long way off. When adding support for a language, all languages, filenames and extensions being added in the PR need to meet requirements.

We (Altera) have plans to public release repos with Simics code in the near future and would greatly benefit from having DML support in linguist. The repos we plan would be FPGA designs with their associated Simics model, in addition to specific training examples on using Simics and modeling.
I am aware of at least 4 major engineering companies that use both GitHub and Simics, where this linguist support would benefit them too.
Please consider this a very strong endorsement of this PR.


Pylance autocomplete doesn't work, while pyright does.

 Environment data

Language Server version: 2021.10.3
OS and version: linux x64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: undefined
python.analysis.typeCheckingMode: basic

 Expected behaviour
Expecting pylancer to have at least the same autocompletion as pyright, because its build on top of it.

 Actual behaviour

 Logs

Python Language Server Log
[Info  - 12:58:06 PM] Pylance language server 2021.10.3 (pyright 2cf9c059) starting
[Info  - 12:58:06 PM] Server root directory: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist
[Info  - 12:58:06 PM] No configuration file found.
[Info  - 12:58:06 PM] No pyproject.toml file found.
[Info  - 12:58:06 PM] Setting pythonPath for service "April": "/home/dh/anaconda3/envs/aprilv2/bin/python"
[Warn  - 12:58:06 PM] stubPath /home/dh/Programming/Python/April/typings is not a valid directory.
[Info  - 12:58:06 PM] Assuming Python version 3.7
[Info  - 12:58:06 PM] Assuming Python platform Linux
Search paths for /home/dh/Programming/Python/April
  /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib
  /home/dh/Programming/Python/April
  /home/dh/Programming/Python/April/typings
  /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stubs/...
  /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs
  /home/dh/anaconda3/envs/aprilv2/lib/python3.7
  /home/dh/anaconda3/envs/aprilv2/lib/python3.7/lib-dynload
  /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages
[Warn  - 12:58:07 PM] Exception received when installing file system watcher: TypeError [ERR_FEATURE_UNAVAILABLE_ON_PLATFORM]: The feature watch recursively is unavailable on the current platform, which is being used to run Node.js
[Warn  - 12:58:07 PM] Exception received when installing file system watcher: TypeError [ERR_FEATURE_UNAVAILABLE_ON_PLATFORM]: The feature watch recursively is unavailable on the current platform, which is being used to run Node.js
[Warn  - 12:58:07 PM] Exception received when installing file system watcher: TypeError [ERR_FEATURE_UNAVAILABLE_ON_PLATFORM]: The feature watch recursively is unavailable on the current platform, which is being used to run Node.js
[Info  - 12:58:07 PM] Searching for source files
[Info  - 12:58:07 PM] Found 15 source files
[Info  - 12:58:07 PM] Background analysis(1) root directory: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist
[Info  - 12:58:07 PM] Background analysis(1) started
Background analysis message: setConfigOptions
Background analysis message: setImportResolver
Background analysis message: ensurePartialStubPackages
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: setFileOpened
Background analysis message: getSemanticTokens full
[BG(1)] getSemanticTokens full at /home/dh/Programming/Python/April/point.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/point.py (46ms)
[BG(1)]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (86ms)
[BG(1)]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/builtins.pyi (36ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/point.py (3ms)
[BG(1)]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/typing.pyi [fs read 1ms] (31ms)
[BG(1)]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/typing.pyi (13ms)
[BG(1)]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 1ms] (9ms)
[BG(1)]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
[BG(1)]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (1ms)
[BG(1)]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/typing_extensions.pyi (2ms)
[BG(1)]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (1ms)
[BG(1)]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/abc.pyi (0ms)
[BG(1)]   parsing: [virtual] /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/cv2/__init__.pyi [fs read 2ms] (124ms)
[BG(1)]   binding: [virtual] /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/cv2/__init__.pyi (49ms)
[BG(1)]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/__init__.pyi [fs read 0ms] (3ms)
[BG(1)]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/__init__.pyi (1ms)
[BG(1)]   parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/__init__.pyi [fs read 0ms] (89ms)
[BG(1)]   binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/__init__.pyi (23ms)
[BG(1)]   parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/apriltag.py [fs read 0ms] (26ms)
[BG(1)]   binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/apriltag.py (12ms)
[BG(1)]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/collections/__init__.pyi [fs read 0ms] (15ms)
[BG(1)]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/collections/__init__.pyi ...

[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/posixpath.pyi [fs read 0ms] (4ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/posixpath.pyi (1ms)
[BG(1)]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/os/path.pyi (14ms)
[BG(1)]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/genericpath.pyi [fs read 0ms] (1ms)
[BG(1)]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/genericpath.pyi (0ms)
[BG(1)]   parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/ctypeslib.pyi [fs read 0ms] (0ms)
[BG(1)]   binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/ctypeslib.pyi (0ms)
[BG(1)] getSemanticTokens full at /home/dh/Programming/Python/April/point.py (953ms)
Background analysis message: getSemanticTokens range
[BG(1)] getSemanticTokens range 0:0 - 43:66 at /home/dh/Programming/Python/April/point.py (6ms)
Background analysis message: analyze
[BG(1)] analyzing: /home/dh/Programming/Python/April/point.py ...
[BG(1)]   checking: /home/dh/Programming/Python/April/point.py (13ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/point.py (13ms)
Background analysis message: resumeAnalysis
[BG(1)] analyzing: /home/dh/Programming/Python/April/april.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/april.py [fs read 0ms] (2ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/april.py (1ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/april.py ...
[BG(1)]     parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/core/fromnumeric.pyi [fs read 0ms] (4ms)
[BG(1)]     binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/core/fromnumeric.pyi (2ms)
[BG(1)]     parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/lib/type_check.pyi [fs read 1ms] (1ms)
[BG(1)]     binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/lib/type_check.pyi (0ms)
[BG(1)]     parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/lib/function_base.pyi [fs read 0ms] (1ms)
[BG(1)]     binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/lib/function_base.pyi (2ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/april.py (168ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/april.py (172ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/calibrate.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/calibrate.py [fs read 0ms] (1ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/calibrate.py (1ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/calibrate.py ...
[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/json/__init__.pyi [fs read 0ms] (1ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/json/__init__.pyi (1ms)
[FG] parsing: /home/dh/Programming/Python/April/point.py (59ms)
[FG] parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 4ms] (92ms)
[FG] binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/builtins.pyi (33ms)
[FG] binding: /home/dh/Programming/Python/April/point.py (2ms)
[FG] parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/typing.pyi [fs read 2ms] (24ms)
[FG] binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/typing.pyi (12ms)
[FG] parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (9ms)
[FG] binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (2ms)
[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/io.pyi [fs read 0ms] (4ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/io.pyi (4ms)
[BG(1)]     parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/lib/index_tricks.pyi [fs read 1ms] (4ms)
[BG(1)]     binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/lib/index_tricks.pyi (4ms)
[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/json/encoder.pyi [fs read 1ms] (1ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/json/encoder.pyi (0ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/calibrate.py (83ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/calibrate.py (86ms)
Background analysis message: resumeAnalysis
[BG(1)] analyzing: /home/dh/Programming/Python/April/calibration.py ...
[BG(1)]   checking: /home/dh/Programming/Python/April/calibration.py ...
[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/types.pyi [fs read 0ms] (6ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/types.pyi (3ms)
[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/json/decoder.pyi [fs read 0ms] (1ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/json/decoder.pyi (0ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/calibration.py (26ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/calibration.py (26ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/capture.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/capture.py [fs read 0ms] (1ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/capture.py (1ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/capture.py (6ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/capture.py (8ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/game.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/game.py [fs read 0ms] (7ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/game.py (3ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/game.py ...
[BG(1)]     parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/typing/_scalars.py [fs read 0ms] (1ms)
[BG(1)]     binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/typing/_scalars.py (0ms)
[BG(1)]     parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/typing/_ufunc.pyi [fs read 0ms] (5ms)
[BG(1)]     binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/typing/_ufunc.pyi (2ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/game.py (155ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/game.py (165ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/main.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/main.py [fs read 0ms] (6ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/main.py (1ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/main.py ...
[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/image.pyi [fs read 0ms] (3ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/image.pyi (3ms)
[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/patches.pyi [fs read 0ms] (0ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/patches.pyi (1ms)
[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/animation.pyi [fs read 0ms] (2ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/animation.pyi (2ms)
[BG(1)]     parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/axes/__init__.pyi [fs read 0ms] (0ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/axes/__init__.pyi ...
[BG(1)]       parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/axes/_subplots.pyi [fs read 0ms] (1ms)
[BG(1)]       binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/axes/_subplots.pyi (0ms)
[BG(1)]       parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/axes/_axes.pyi [fs read 0ms] (14ms)
[BG(1)]       binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/axes/_axes.pyi (11ms)
[BG(1)]     binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/axes/__init__.pyi (27ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/main.py (67ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/main.py (74ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: resumeAnalysis
[BG(1)] analyzing: /home/dh/Programming/Python/April/math.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/math.py [fs read 0ms] (1ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/math.py (0ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/math.py ...
[BG(1)]     parsing: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/linalg/__init__.pyi [fs read 0ms] (1ms)
[BG(1)]     binding: /home/dh/anaconda3/envs/aprilv2/lib/python3.7/site-packages/numpy/linalg/__init__.pyi (0ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/math.py (25ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/math.py (26ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/movement.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/movement.py [fs read 1ms] (1ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/movement.py (1ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/movement.py (9ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/movement.py (11ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/nativ.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/nativ.py [fs read 0ms] (1ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/nativ.py (1ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/nativ.py (42ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/nativ.py (44ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/opencv.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/opencv.py [fs read 0ms] (2ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/opencv.py (1ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/opencv.py (123ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/opencv.py (126ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: resumeAnalysis
[BG(1)] analyzing: /home/dh/Programming/Python/April/perspectivetransform.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/perspectivetransform.py [fs read 0ms] (1ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/perspectivetransform.py (1ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/perspectivetransform.py (25ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/perspectivetransform.py (30ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/play.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/play.py [fs read 0ms] (2ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/play.py (1ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/play.py (87ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/play.py (90ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/test.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/test.py [fs read 0ms] (2ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/test.py (2ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/test.py (30ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/test.py (35ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/thresh.py ...
[BG(1)]   parsing: /home/dh/Programming/Python/April/thresh.py [fs read 0ms] (0ms)
[BG(1)]   binding: /home/dh/Programming/Python/April/thresh.py (2ms)
[BG(1)]   checking: /home/dh/Programming/Python/April/thresh.py (67ms)
[BG(1)] analyzing: /home/dh/Programming/Python/April/thresh.py (70ms)
Background analysis message: resumeAnalysis
[FG] parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/figure.pyi [fs read 0ms] (4ms)
[FG] binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/figure.pyi (1ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] completion at /home/dh/Programming/Python/April/point.py:11:7 ...
[FG]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (2ms)
[FG]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/typing_extensions.pyi (2ms)
[FG]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (0ms)
[FG]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/typeshed-fallback/stdlib/abc.pyi (1ms)
[FG]   parsing: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/artist.pyi [fs read 0ms] (0ms)
[FG]   binding: /home/dh/.vscode/extensions/ms-python.vscode-pylance-2021.10.3/dist/bundled/stubs/matplotlib/artist.pyi (0ms)
[FG] completion at /home/dh/Programming/Python/April/point.py:11:7 [found 40 items] (33ms)
[FG] parsing: /tmp/pyright-11605-6Hpjtj2W2VzO/builtins-11605-52JKoDGmvMqJ-.py [fs read 1ms] (93ms)
[FG] binding: /tmp/pyright-11605-6Hpjtj2W2VzO/builtins-11605-52JKoDGmvMqJ-.py (43ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] completion at /home/dh/Programming/Python/April/point.py:11:7 [found 40 items] (2ms)

 Code Snippet / Additional information

from matplotlib import pyplot as plt
from matplotlib.figure import Figure
Figure.

This is because our stub for matplotlib doesn't have any of these members yet: https://github.com/microsoft/python-type-stubs/blob/main/matplotlib/figure.pyi#L6
Pyright doesn't ship the stubs, so with useLibraryCodeForTypes enabled, it will go try and analyze the code.

I also needed to remove/rename the stub. But it works, thanks for the quick response.


Please change css & js links in examples files

[kitchen-sink-ios]  & [kitchen-sink-material] 。

Please, see the README file:

Framework7' JS and CSS files in Kitchen Sink are temporary linked to build/ to make development process easier on this stage. So to make it work you need to build Framework7 (see Build section) or to re-link JS and CSS files to dist/ folder.

I got it，thanks 。


applet deactivated after waking from sleep mode

Hello . My PC is connected to an external monitor.
When QRedShift is activated and I put the PC to sleep, the applet deactivates after waking up.
Each time, I have to deactivate and then activate the applet to get the program working again.
What's the solution to this problem?

I have the same.
I'm trying with systemd service, but it's not working so far.

Hi. I noticed that the problem is linked to the connection of the PC to the external monitor via HDMI. To check this. Disconnect the HDMI cable then reconnect it and you will see that RedShift turns off automatically! Unfortunately, I haven't found a solution to this problem. Can you tell me what shell command you call with the Systemd Service?

/usr/bin/dbus-send --session --dest=org.Cinnamon.LookingGlass --type=method_call /org/Cinnamon/LookingGlass org.Cinnamon.LookingGlass.ReloadExtension string:'qredshift@quintao' string:'APPLET'

/usr/bin/dbus-send --session --dest=org.Cinnamon.LookingGlass --type=method_call /org/Cinnamon/LookingGlass org.Cinnamon.LookingGlass.ReloadExtension string:'qredshift@quintao' string:'APPLET'

If you keep the night mode enabled it will do the tricky, the screen will flash but the color will be setted again..
The problem is when changing TTYs the gamma ramps is reseted.

Can you try the new version and check if it works?
Copy and paste that on terminal to update:
curl https://github.com/raphaelquintao/QRedshiftCinnamon/raw/master/install.sh -sSfL | bash

Hello,
Not only is the previous issue not resolved, but the situation has worsened: the applet no longer works at all :-).
I am currently using Linux Mint LMDE 6 .
Thank you for your assistance.

Dont works? What happens? do you see any erros?

The applet is properly installed. However, when I click on the "Activate filter mode" button, nothing happens, and the application does not generate any errors.


pythonPackages.pypandoc: fix tests for pandoc >= 2.11.2

Motivation for this change
A change in the Markdown output of pandoc breaks the unicode input test
of pypandoc.
See also https://github.com/bebraw/pypandoc/pull/204.

Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamCOfBorg build python3Packages.pypandoc

Result of nixpkgs-review pr 104625 1

3 packages built:

python27Packages.pypandoc
python37Packages.pypandoc
python38Packages.pypandoc


MemoryTracker: fixed build with clang 9.0.0 not properly supporting thread_local

This fixes #1488.
XCode 9.0 added support for C++11 thread_local:
https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Chapters/Introduction.html
The 443088ce3134b1c61e9bc746ed9306bdf0f4c067 replaced __thread with C++11 thread_local, which
broke the compilation for this platform with an error on link time.
I can't reproduce this with a minimal example yet.

Great!


right click speed is highly limited when using v1.5.0 (MC 1.20.2)

I noticed that when I use this mod and I want to place blocks I can only do this around once per second. Don't really know why and if it may have to do with another mod but right now this seems to be an issue on my end.

Are you able to reproduce this issue with only this mod and Fabric API installed? I can't seem to reproduce it myself.

Yes, even with only these mods installed exactly like this I still have the issue.

I made a quick video showcasing the issue. I think its related to how long you click since the more CPS I have the less likely it will place a block.

If you check your latest.log (../.minecraft/logs/latest.log), does it say anything there? When I start an autoclicker at ~20 cps I can still place blocks.

latest.log
Thats what it says. Also if I set my auto clicker to exactly these settings the right clicking will not place blocks at all. (left click still will break them)

So it does seem to have to do with how long you click down for a block to be placed.

Your log doesn't contain any errors, so that can be ruled out as a possible source of the problem. What happens if you click manually? Because Minecraft may not register all clicks if they're too fast.

Nope its caused by the mod. Made another video comparing this.

Do you have the same issue when you use v1.4.0 for 1.20.2? In v1.5.0 I fixed an issue with the right click CPS counter, which may have resulted in this bug.

Yeah not an issue on the previous version

Can you try this? Made a small adjustment to the mixin.
tiptapshow-1.6.0-BETA-TEST+1.20.2.zip

Seems to still be happening on my end and didn't improve.

What Fabric Loader version are you using? I'm using 0.15.3 to test.

Same version

I'm not sure what the issue could be, but could you also upload your debug.log? Also can you try not displaying the CPS and see if that changes anything, so I can be more sure of where the issue lies.

I don't really know how to get a debug log, can't find it. For the other troubleshooting I tried that and did not solve the issue either, even disabling the overlay completely doesnt resolve it.

Should be located under ./minecraft/logs/debug.log, but it might be behind a setting.

I don't have a debug.log so idk where to find it, def not in that folder

If anyone else experiences this, please comment below.

Yes, and I have the same problem. When I have this mod, the click speed is highly limited. Without it, there would be no problem.

I can't seem to reproduce it myself.

You can use experience bottles to easily reproduce the bug. How it should be:
https://github.com/Spyxar/TipTapShow/assets/75726196/1de690e0-5735-422b-ad06-f06104cf465f
https://github.com/Spyxar/TipTapShow/assets/75726196/9164c63e-8460-4185-83e7-25b4da46a88b
How it is:
https://github.com/Spyxar/TipTapShow/assets/75726196/a6e7a396-e8d2-42fa-83d0-cb90e5d6f0e7

tiptapshow-1.5.1+1.20.4.zip Could one of you try and see if this version works again?

tiptapshow-1.5.1+1.20.4.zip Could one of you try and see if this version works again?

Yes. this issue appears resolved for me with that version of the mod!

Can confirm, the issue has been fully fixed
https://github.com/Spyxar/TipTapShow/assets/75726196/1fb924b9-7b8e-4fae-9c60-86cac644d532


Adds banner flag

Description
Adds a banner flag to override what's displayed on the main login page.
Motivation and Context
This is to implement the suggestion in #193
How Has This Been Tested?
Built docker image after applying patch in #190. Run in Kubernetes to load page and see that both -banner='-' and -banner='My sweet banner' worked.
Checklist:

[X] My change requires a change to the documentation or CHANGELOG.
[X] I have updated the documentation/CHANGELOG accordingly.
[X] I have created a feature (non-master) branch for my PR.

Do we know when a release with this is coming? This would be really handy!

@JoelSpeed are you able to help with this?

LGTM, will be cutting a release next week hopefully

That is great! Thank you!

Thanks @JoelSpeed !


Icpick like Storing/Restoring

How about support for IcePick style storing/restoring of parcelable classes?
https://github.com/frankiesardo/icepick
Because of the extra wrapping step, IcePick is currently incompatible with parceler (if I'm not mistaken)

Is there any interest in a fork of Icepick with Parceler support?  Im considering releasing it on Maven central: https://github.com/johncarl81/icepick/tree/parceler_support

Is there any interest in a fork of Icepick with Parceler support?
Would be great

+1

Yes
On Thu, Feb 26, 2015, 8:48 AM Pedro Paulo de Amorim <
<EMAIL_ADDRESS>wrote:

+1
—
Reply to this email directly or view it on GitHub
https://github.com/johncarl81/parceler/issues/36#issuecomment-76180318.

+1

+1

+1

I decided to roll my own Ickpick. It is written from scratch and works perfectly with Parceler, please take a look [here] (https://github.com/tom91136/Akatsuki).
One of the more unique feature of my library is that it supports a pluggable compile-time code generation system. The parceler support is done with ONLY the following lines:
@TransformationTemplate(
		save = @StatementTemplate("{{bundle}}.putParcelable({{keyName}}, org.parceler.Parcels.wrap({{fieldName}}))"),
		restore = @StatementTemplate(type = Type.ASSIGNMENT,
				                     value = "org.parceler.Parcels.unwrap({{bundle}}.getParcelable({{keyName}}))",
				                     variable = "{{fieldName}}"),
		filters = {@TypeFilter(type = @TypeConstraint(type = Parcel.class))}
		)

Awesome work @tom91136!


NewEvnClient doesn't work with manual setting environment variables

    os.Setenv("LEANCLOUD_APP_ID", "*************")
  os.Setenv("LEANCLOUD_APP_KEY", "*************")
  os.Setenv("LEANCLOUD_APP_MASTER_KEY", "*************")
  os.Setenv("LEANCLOUD_API_SERVER", "*************")
  client := leancloud.NewEnvClient()

Not sure how to initialize the sdk; even with manually setting the required environment variables, it still throws:
"please set API's serverURL for China region or legacy app"

This issue is a bit complicated.
The LeanEngine part of Go SDK initializes a client in the package's init() function for LeanEngine related operations, such as remote calls to cloud functions, but this part of the client initialization is done by reading environment variables. So if you set environment variables in main(), it must be after init() is executed, and that's why the error is reported.

I had a quick look at the code and agree that init() is called to load the environment variables.
So there is no easy fix for this?
Wonder how others have been using the go-sdk.

by setting environment variables via direnv or similar tools, or using IDEs like Jetbrains and editors like vscode support setting environment variables in debug targets
for example I'm using vscode with this configuration:
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch Package",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}/main.go",
            "envFile": "${workspaceFolder}/.env"
        }
    ]
}


[Bug] TextCaseConverter

I am using the converter on a custom control to a Text property that has BindingMode.TwoWay
[mono-rt] [ERROR] FATAL UNHANDLED EXCEPTION: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NotImplementedException: The method or operation is not implemented.
[mono-rt]   at Xamarin.CommunityToolkit.Converters.TextCaseConverter.ConvertBack (System.Object value, System.Type targetType, System.Object parameter, System.Globalization.CultureInfo culture) [0x00000] in <5265966be8d2407fb7a4c3b38c6441d7>:0

That is correct, this would call the ConvertBack method which is not implemented because there is no way of knowing how to convert back. If you change the casing, the original information is lost.


Vimeo giving up after 10 fragment retries

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2020.09.20
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

youtube-dl https://vimeo.com/331404905 -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'https://vimeo.com/331404905', u'-v']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2020.09.20
[debug] Python version 2.7.13 (CPython) - Linux-5.3.9-x86_64-with-debian-9.13
[debug] exe versions: ffmpeg 3.2.15-0, ffprobe 3.2.15-0
[debug] Proxy map: {}
[vimeo] 331404905: Downloading webpage
[vimeo] 331404905: Extracting information
[vimeo] 331404905: Downloading JSON metadata
[vimeo] 331404905: Downloading JSON metadata
WARNING: Unable to download JSON metadata: HTTP Error 403: Forbidden
[vimeo] 331404905: Downloading akfire_interconnect_quic m3u8 information
[vimeo] 331404905: Downloading akfire_interconnect_quic m3u8 information
[vimeo] 331404905: Downloading fastly_skyfire m3u8 information
[vimeo] 331404905: Downloading fastly_skyfire m3u8 information
[vimeo] 331404905: Downloading akfire_interconnect_quic MPD information
[vimeo] 331404905: Downloading akfire_interconnect_quic MPD information
[vimeo] 331404905: Downloading fastly_skyfire MPD information
[vimeo] 331404905: Downloading fastly_skyfire MPD information
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on u'https://skyfire.vimeocdn.com/1603445696-0x5083e346ed674ffa4244d27c8177d8c0c56c35e0/331404905/sep/video/1303099786,1303099787,1303099790,1303099779,1303099783/master.mpd?base64_init=1'
[dashsegments] Total fragments: 44
[download] Destination: 10 000 valandų iki tobulo margučio-331404905.fdash-fastly_skyfire_sep-video-1303099779.mp4
[download] 100% of 81.74MiB in 00:09
[debug] Invoking downloader on u'https://skyfire.vimeocdn.com/1603445696-0x5083e346ed674ffa4244d27c8177d8c0c56c35e0/331404905/sep/video/1303099786,1303099787,1303099790,1303099779,1303099783/master.mpd?base64_init=1'
[dashsegments] Total fragments: 44
[download] Destination: 10 000 valandų iki tobulo margučio-331404905.fdash-fastly_skyfire_sep-audio-1303099786.m4a
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 1 of 10)...
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 2 of 10)...
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 3 of 10)...
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 4 of 10)...
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 5 of 10)...
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 6 of 10)...
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 7 of 10)...
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 8 of 10)...
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 9 of 10)...
[download] Got server HTTP error: HTTP Error 404: Not Found. Retrying fragment 1 (attempt 10 of 10)...
ERROR: giving up after 10 fragment retries
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/dash.py", line 48, in real_download
    success, frag_content = self._download_fragment(ctx, fragment_url, info_dict)
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/fragment.py", line 102, in _download_fragment
    'http_headers': headers or info_dict.get('http_headers'),
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 366, in download
    return self.real_download(filename, info_dict)
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 348, in real_download
    establish_connection()
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 114, in establish_connection
    raise err
HTTPError: HTTP Error 404: Not Found

Description

Each time I try to download a video from Vimeo I get this error. It downloads the video file but stuck with the audio file (m4a).

I can confirm that this issue is affecting me as well when downloading audio fragments.

Yep, youtube-dl doesn't work with audio fragments of Vimeo.

This commande helped me to baypass the issue youtube-dl -f 'http-1080p/http-720p' URL

This commande helped me to baypass the issue youtube-dl -f 'http-1080p/http-720p' URL

Does this format contain audio as well?

This commande helped me to baypass the issue youtube-dl -f 'http-1080p/http-720p' URL

Does this format contain audio as well?

Yes! it downloads one file with both video and audio

just tried this link > https://vimeo.com/331404905
downloads ok for me.

youtube-dl https://vimeo.com/331404905
[vimeo] 331404905: Downloading webpage
[vimeo] 331404905: Extracting information
[vimeo] 331404905: Downloading JSON metadata
[vimeo] 331404905: Downloading JSON metadata
WARNING: Unable to download JSON metadata: HTTP Error 403: Forbidden
[vimeo] 331404905: Downloading akfire_interconnect_quic m3u8 information
[vimeo] 331404905: Downloading akfire_interconnect_quic m3u8 information
[vimeo] 331404905: Downloading fastly_skyfire m3u8 information
[vimeo] 331404905: Downloading fastly_skyfire m3u8 information
[vimeo] 331404905: Downloading akfire_interconnect_quic MPD information
[vimeo] 331404905: Downloading akfire_interconnect_quic MPD information
[vimeo] 331404905: Downloading fastly_skyfire MPD information
[vimeo] 331404905: Downloading fastly_skyfire MPD information
[dashsegments] Total fragments: 44
[download] Destination: 10 000 valandų iki tobulo margučio-331404905.fdash-fastly_skyfire_sep-video-1303099779.mp4
[download] 100% of 81.74MiB in 12:21
[dashsegments] Total fragments: 44
[download] Destination: 10 000 valandų iki tobulo margučio-331404905.fdash-fastly_skyfire_sep-audio-1303099786.m4a
[download] 100% of 4.32MiB in 00:34
[ffmpeg] Merging formats into "10 000 valandų iki tobulo margučio-331404905.mp4"
Deleting original file 10 000 valandų iki tobulo margučio-331404905.fdash-fastly_skyfire_sep-video-1303099779.mp4 (pass -k to keep)
Deleting original file 10 000 valandų iki tobulo margučio-331404905.fdash-fastly_skyfire_sep-audio-1303099786.m4a (pass -k to keep)


Add PR template prototype

Description
The idea of this PR is to create a pull request template as a prototype in order to set a kind of "agreement" for new PRs.
It is very handy and it is automatically integrated into GitHub.
Take a look and tell me what do you think.

I though about this myself too. However, I came to the conclusion that this is to much of a process for this early stage. I don't want people to stuck in to many processes right now. But I'm open for a discussion on this.
As alternative we could think of a small contributions guide where we could give some best practices on submitting a pull request.

I though about this myself too. However, I came to the conclusion that this is to much of a process for this early stage. I don't want people to stuck in to many processes right now. But I'm open for a discussion on this.
As alternative we could think of a small contributions guide where we could give some best practices on submitting a pull request.

Well, the point of this PR is to unify and simplify the PRs.
You can take a look at those PRs (I took a random one of each contributor) :
https://github.com/jenshaase/phel-lang/pull/36 -> @JesusValera
https://github.com/jenshaase/phel-lang/pull/23 -> @paullaffitte
https://github.com/jenshaase/phel-lang/pull/18 -> @Chemaclass
https://github.com/jenshaase/phel-lang/pull/11 -> @dominikb
By one side, I think it makes simple the process,
by the other, I agree with you maybe it makes more complicated the process of creating new PRs.
About your suggestion, what do you mean with "small contribution guide"?
You can close this PR, and create an issue with that. :smile:

I agree with @jenshaase. But I like the proposal idea from @JesusValera too.
What about making it simpler? I would propose a minimalistic template like:
# Description

Replace this text by a short description of your feature/bugfix.
This will help people understand your PR and can be used as a start for the docu.

# Changes

- Modified X class/method to do Y because Z

What do you think?

Hi,
I would go for an even simple and more open template. This will also work for documentation changes.
# Description

Replace this text by a short description of your feature/bugfix.

# Changes

- List individual changes in more detail

What do you think?

Hi,  I would go for an even simple and more open template. This will also work for documentation changes.
# Description

Replace this text by a short description of your feature/bugfix.

# Changes

- List individual changes in more detail

What do you think?

Yes! I like this even more.

I like even more now! :smile:
Done.

Thanks. Merged it!


Unable to find input class InetInput

Hi guys. I am using activeadmin on my models and I came across with a error caused by formtastic that is used behind activeadmin.
Formtastic::UnknownInputError at /admin/users/1/edit
Unable to find input class InetInput

When using a devise model, desive adds two columns as inet(network address type), but there isn't a InetInput class declared on formtastic, so input_helper.rb can not resolve the lookup for the correct class to instantiate.

I think that the inet fields should be treated as string by default. They're used by default for trackable Devise models on PostgreSQL and it's a bit annoying to have to redefine the whole form for the resource because of these inet fields. If the form is not redefined, an exception will be raised.

@justinfrench what do you thing about a DefaultInput or FallbackInput, which is used for all unknown inputs?

@timoschilling @mitio We already fallback to StringInput in many cases. I think the problem here is that we don't have a fallback to StringInput when we're mapping database column types to inputs. I've created a new issue #1146 for this, would love help patching :)


FIX Updated for Xcode 10 and Swift 4.2

Can we merge this please?

It would be great if we can merge this :)

Merge please, thanks.

@gilesvangruisen hello?

@gilesvangruisen Thanks for merging, now we need a new release please 😉

@gilesvangruisen Thanks, but the new version is not available on cocoapods. I guess because linting fails. I've created a PR to fix the podspec: #168
NOTE: You'll have to move the tag v0.5.0 to the new commit or make a new release...


EQ-413 Transaction ID

What is the context of this PR?
Adding Transaction ID to the Metadata store, and submitted response downstream and also updating logging events
How to review

Check out this branch
Run the application
Check that the transaction ID is being written to the log files at info level
Complete a survey and check that the transaction id is displayed on the thank you page

[ ] Do all commits have sensible commit messages?
[ ] Is all new code unit tested?
[ ] Are there integration tests if needed?
[ ] Is there sufficient logging?
[ ] Is there documentation or is the code self-describing?

Who worked on the PR
@warrenbailey and @bennpearson

Just waiting for design input

Changes Unknown when pulling d8153c04a97de45661bc32d9988813e6b2e50d6e on eq-413-transaction-tracking into ** on master**.

Changes Unknown when pulling 1e538cb383c55610c14bd0ee0ee645aba5f5ed08 on eq-413-transaction-tracking into ** on master**.

Changes Unknown when pulling 5e32982cddc42074149d12324f7131130cfa8bfa on eq-413-transaction-tracking into ** on master**.

Changes Unknown when pulling 028c1f67a815acad652b5afa5d46846912dbe3c3 on eq-413-transaction-tracking into ** on master**.

Changes Unknown when pulling 028c1f67a815acad652b5afa5d46846912dbe3c3 on eq-413-transaction-tracking into ** on master**.

All done, just needs front end work on the thank you page.

Benn has done the front end changes so this is ready for review now. Removing WIP label.

Changes Unknown when pulling fed42fedc034b882b6737050c9506e2cdb80823f on eq-413-transaction-tracking into ** on master**.

Not ready now, we're going to add the transaction ID to the errors pages too

Changes Unknown when pulling 7e38bbf139c5938ca759d4d2316d4437ee6d758b on eq-413-transaction-tracking into ** on master**.

Changes Unknown when pulling 7e38bbf139c5938ca759d4d2316d4437ee6d758b on eq-413-transaction-tracking into ** on master**.

Ready for review again

All LGTM :+1:


Added tox support in ci

flake8, nose and coverage now orchestrated by tox instead of travis.

look great, thanks @ruivieira !


structure for challenge

[ ] Top-level README “Table of Contents” is updated
[ ] Feature tasks for this challenge are completed
[ ] Unit tests written and passing

[ ] “Happy Path” - Expected outcome
[ ] Expected failure
[ ] Edge Case (if applicable/obvious)

[ ] README for this challenge is complete

[ ] Summary, Description, Approach & Efficiency, Solution
[ ] Link to code
[ ] Picture of whiteboard

doint this so i can go back and resub

doint this so i can go back and resub


Translation completed in french

Hi,
Yesterday in France, me and @gendy54 managed to gather the energy of the community and reviewed the whole translation of MapRoulette.
We are glad to say that we managed to do it! We also reviewed already translated chains and corrected a lot of them too.
We did review and double-check our work together and managed to translate almost all of the chains.
We also populated the glossary https://www.transifex.com/osmlab/maproulette3/glossary/fr/ which is extra-useful when you'd like to do the job seriously.
We still have some questions remaining, see the comment section of these chains https://www.transifex.com/osmlab/maproulette3/translate/#fr/en-us-json/170937372?q=issue%3Aopen
I don't have the status of translators' reviewer so I wonder how to validate all the translation that has been done. If there is a need, I agree to become a translation's validator for french.
Thanks
PS: as part of a small team of french contributors, we will begin to use a lot your great tool in the upcoming months, so expect some feedback from us!

Thank you so much for this contribution!

You're welcome. We are now waiting for the team's help to get it approved/integrated as stated in my first message.

A deployment is going out this Tuesday (Dec 14) and will include translation updates (https://github.com/osmlab/maproulette3/commit/7fc64e125ccb09b5393897f65525852959dc6c15#diff-c4e2a9d0bd1f8543073aa55692f5225d5249dd3beeb87eab8a5b335de327a1b8R2).
As for review/approval, @mvexel may be the right person to go through your remaining questions (https://www.transifex.com/osmlab/maproulette3/translate/#fr/en-us-json/170937372?q=issue%3Aopen).

Thanks for this deployment. @gendy54 @PanierAvide and I will double check it.
@mvexel could you please provide some useful context directly in the Transifex interface?
(for the story, I really discovered advanced features of transifex in the process. We pushed the limit: populated the glossary, check the automatic errors... I believe we made some great job here)

Thanks @mvexel for your replies. We are adding new suggestions, please check Transifex tomorrow


How to give input text default font-family style to QuillEditor

I want to add a font-family by default to the input text.. how can we do that in quillEditor?

@shivika24 custom fonts and default font-family has been added.
You may check the example project to know how to setup them.

I'm gonna close this issue for now . Please feel free to reopen if there were any problems.


Use {arch}/{os}/remote/installState.sh and {arch}/{os}/remote/setupNode.sh to install state on remote machine

https://github.com/Shippable/pm/issues/10232

this is done, closing


Montpellier DjangoCong 2012

Lightning talks and main talks are on separate YouTube playlists but are from the same conference.
Lightning Talks: https://www.youtube.com/playlist?list=PL66702ED0B508F4AB
Talks: https://www.youtube.com/playlist?list=PLADB4C31B364E4B22
Site: http://rencontres.django-fr.org/2012/

I wonder if the dir shouldn't be djangocong-2012/, i.e. without the "Montpellier" in it (same for category.json title)
With https://github.com/pyvideo/data/issues/266 coming, these 2 would be under the same "DjangoCong" section in http://pyvideo.org/events.html
Thoughts?

The reason I put Montpellier in the title is because the event from #266 occurred in the same country, same year, but a different city and different dates. I wasn't sure how to handle that, but I'm happy to do whatever more seasoned contributors think is best here.
As a side note, it looks like there are other years of DjangoCong, but I couldn't find videos of any of the other years in my cursory search. It does seem to be in a different city every year, but 2012 is the only year listed on the site that has two separate conferences.

Oh, right! Then I don't know what's the best. PyData has different cities too.


"Reset" button needed

First of all, thank you for this awesome package!
This is a feature request.
In case when I`m setting pin code first time and miss clicked then I can not enter the same code one more time.
It is not a problem if I trying to change old pin code.
But if setting of pin code is mandatory on first run, I should unload app to make a new try.
It is not clear for many users.
So, I need to write much code to make it work my way. I guess, not only mine.
Thank you!

Set confirmation to true.
If the code is the same the first and second time, didConfirmed will be called.
I think this will solve this use case.

I do use confirmation: true and correctString: '' in my case.
But what if I going to set pin code 1234 but entered 1235 and did not noticed it?

Are you saying you want to go back to the first input?

Yes!

ElevatedButton(
  onPressed: () {
    // Define it to control the confirmation state with its own events.
    final inputController = InputController();
    screenLock(
      context: context,
      correctString: '',
      confirmation: true,
      inputController: inputController,
      didConfirmed: (matchedText) {
        // ignore: avoid_print
        print(matchedText);
      },
      footer: TextButton(
        onPressed: () {
          // Release the confirmation state and return to the initial input state.
          inputController.unsetConfirmed();
        },
        child: const Text('Return enter mode.'),
      ),
    );
  },
  child: const Text('Confirm mode'),
)

Oh, thank you! Now I see, I can use that controllers method with custom button. It will be less code than I have. But still, I have to use StatefullWidget to create and dispose controller. So I cant just call screenLock() and being not coupled tight with that.
I can live with that.
Are you going to add this feature yourself some day or do prefer PR or won`t it at all?

We have no plans to add it, as we currently have that means.
However, PRs would be welcome.

Will see what i can do :)
Thank you once again!


Maven interpolation

Is this a request for help?: yes

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST
What happened:
During a Maven build is normal to interpolate resources files with Maven property, as far as I have got the plugin takes files directly from the src folder.
The simple scenario is to interpolate values.yaml with a a given version of an image.
Is there a way to directly interpolate the resources (helm charts) without passing via the target folder?
What you expected to happen:
The plugin could interpolate Maven properties.
How to reproduce it (as minimally and precisely as possible):
Just add a Maven property to values.yaml and run the plugin.

Can you filter your files with maven-resource-plugin to /target/helm-filtered and set -Dhelm.chartDirectory=target/helm-filtered ?

Can you filter your files with maven-resource-plugin to /target/helm-filtered and set -Dhelm.chartDirectory=target/helm-filtered ?

agree - dedicated plugin should be used, instead of complicate code in this project


Bring Gradle client plugin to same level as maven plugin 0.1.18

The commits mostly match the equivalent maven plugin commits (with same titles), plus a few fixup commits in between.
I have not included the latest maven plugin commits (Util:Android), as I cannot comprehend what they do (both Maven and Android are opaque to me).

I also have updates to the client-samples project.
Using this PR state of the client plugin works with all four client samples.
I will submit a separate PR for that project, so you have something to test this PR with.

I've added a quick review. I've tested HelloFX with the plugin, looks good to me.
About missing commits (Util/Android), it is not a maven/android thing, so these should be straightforward to apply.

@jskov Thank you for your efforts to bring the Gradle plugin on par with the Maven plugin.

@abhinayagarwal no problem. Thanks for taking the time to guide me :)


run-dev bootstrap error

Hi Gildas
This looks like a great project combining some of the leading techniques!
I'm keen to get it up and running to have a closer look but I've run into a strange error.
(I'm running on Ubuntu 15.10)
I ran the make install and make run-dev and then get the following error which seems to indicate that it cannot find bootstrap?. Rather than start "fiddling" too much, I thought you may be able to give me some immediate pointers:
sudo make run-dev
node ./bin/development.js
<EMAIL_ADDRESS>without ES6 number constructor is up to date
70% 1/1 build modulesHash: 41810d1994e4ed5ed42c
Version: webpack 1.12.9
Time: 10248ms
Asset     Size  Chunks       Chunk Names
a3de2170e4e9df77161ea5d3f31b2668.ttf   142 kB
f775f9cca88e21d45bebe185b27c0e5b.svg   366 kB
client.bundle.js  24.8 MB       0       main
chunk    {0} client.bundle.js (main) 21.1 MB [rendered]
ERROR in ./app/main_client.js
Module not found: Error: Cannot resolve module 'bootstrap' in /home/joel/Dev/my-nutrition/app
@ ./app/main_client.js 44:0-20
ERROR in ./~/css-loader!./~/sass-loader!./app/client/styles/main.scss
Module build failed:
@import '~bootstrap/scss/bootstrap';
^
File to import not found or unreadable: ~bootstrap/scss/bootstrap
Parent style sheet: stdin
in /home/joel/Dev/my-nutrition/app/client/styles/main.scss (line 2, column 1)
@ ./app/client/styles/main.scss 4:14-127 13:2-17:4 14:20-133
Hash: c30a7a4c921e58c2e33e
Version: webpack 1.12.9
Time: 2964ms
Asset     Size  Chunks             Chunk Names
server.bundle.js  1.17 MB       0  [emitted]  main
server.bundle.js.map  1.36 MB       0  [emitted]  main
chunk    {0} server.bundle.js, server.bundle.js.map (main) 1.1 MB [rendered]
[[[[[ ~/Dev/my-nutrition/meteor_core ]]]]]
=> Started proxy.
=> Started MongoDB.
=> Started your app.
=> App running at: http://localhost:3000/
I20160105-08:53:38.597(2)? ### Mailman is activated ###

Previously I "sudo" ran the make instructions, so I re-installed again without sudo.
This time I received the error below when I ran make run-dev HOWEVER the application was up and running...(issue closed).
ERROR in multi main
Module not found: Error: Cannot resolve 'file' or 'directory' ./lib/core-js-no-number in /home/joel/Dev/my-nutrition/webpack
@ multi main


Polish deploy command

Some cleanup + polish tasks for the deploy command before we document and promote it more:

[ ] Support auto-fill for SSH key
[ ] Support auto-fill for cluster name (derived from RG name)
[ ] Support auto-fill for SP creds
[ ] Cleanup UX for the output (there’s a few places where the wrong output formatter is used and looks sloppy)

@seanknox Can I send this this week? I've implemented all 4 of these things in a branch. Or would you prefer I hold off for a different release?

Let's do it. 👍

Drat. I forgot I had to hack around the validation code because it's... oddly tied to the deserialization process. I need to refactor a bit more before this can be submitted. I'll do it tonight and get a PR out, tired of rebasing it :).

No worries or rush—let's push to next release officially, merge in at your leisure.


fix setfacl check

Duplicate of #28

Closing as duplicate of #28, which was finally merged. Thanks anyway!


No e-mail is sent to affected user when removing a user as a package's owner

If you don't already, create two user accounts on NuGet.  I'll call them A and B.
Create a package, log in as A, and upload the package.
Edit the package owners to include account B.
Log out and log in as B.
Remove A from the list of package owners.
Watch A's email inbox.

Result:  There's no notice to user A that he is no longer an owner on the package.
Expected:  We should, as a matter of symmetry, have e-mail notification that a user was removed a package's list of owners.  Folks learn through e-mail that they've been added, after all.

When removing user A, should there be a link in the email to confirm they can be removed? At the moment there is no choice for the owner being removed, so my initial thought is no. I imagine this is just a courtesy email?

It's indeed just a courtesy email at the moment.


[BUG][Opensearch] Identical docker image discrepancy

Describe the bug
I created a docker image identical to opensearchproject/opensearch:2.11.0, except that when I try to run the pods, they won't start and keep backing off due to the container failing, unlike opensearchproject/opensearch:2.11.0, which runs fine.
To Reproduce
Steps to reproduce the behavior:

build dockerfile that is simply FROM opensearchproject/opensearch:2.11.0
upload it to dockerhub and run it through changing image.repository
It crashes every node

Expected behavior
Identical behavior between images
Chart Name
Opensearch
Host/Environment (please complete the following information):

Helm Version: v3.10.1
Kubernetes Version: 1.27.3-gke.100

Additional context
I don't want to think that this is an issue with this repo, but I can't think of any other explanation.

Hi @dgisser could you share these two items with us to help debugging the issues?

Your new dockerfile
Your error logs

Thanks.

For sure. The dockerfile is literally just the line FROM opensearchproject/opensearch:2.11.0
I unfortunately don't have any logs since the container that was loading the docker image failed on startup and didn't generate any.

The architecture of your image is linux/arm64, and I don't believe OpenSearch supports anything other than amd64.


[flutter_tools] split cache into API and implementation

In order to make the null safe migration easier, reduce the dependencies of cache.dart (which is commonly imported) by moving all of the artifact set definitions into another library.
#71511

@jmagman WDUT about landing this and fixing the real errors on post-submit? Otherwise I'll probably need to wait a few more days

@jmagman WDUT about landing this and fixing the real errors on post-submit? Otherwise I'll probably need to wait a few more days

SGTM, it's probably all fine on cl/366144401.

Marked the google testing as good.