text:
option to preserve html comments

Hi,
we are using nginx serversideincludes infront of our application. nginx SSIs are expressed as html comments (https://nginx.org/en/docs/http/ngx_http_ssi_module.html) (<!--# include file="footer.html" -->)
Unfortunately jte strips all html comments without providing an option keep them which removes all nginx SSI expressions as well.
Could you please provide an option to keep html comments as they are.
My current workaround is:
$unsafe{"<!--"}# include virtual="${virtual}" -->

Hey @Fender123!
thanks for reporting this. When we decided to omit comments in HTML mode we couldn't think of a reason one would want them in the output. Didn't think about serverside includes. Let me know if this change would work for you: https://github.com/casid/jte/commit/9ae8c37be5b6ae385b050a71c970043fec1a131f

It's probably a good idea for another policy? You probably want to strip comments except for SSI includes?

@kelunik you can still use jte-style comments if you want to omit them: <%-- This will never be rendered. --%>.

yes fixes the problem!

Awesome, thanks for the feedback @Fender123. I'll put together a bugfix release this week and close this issue once it is out.

I tried to publish 1.5.1 to maven central today, but ran into timeouts. Never had that happening before. I'm wondering JFrog's announcment to sunset jcenter is driving lots of people to upload their stuff to maven central right now, causing bandwidth problems.
I'll keep you posted.

@Fender123 this morning publishing to maven central worked again. 1.5.1 is live containing this fix 👍

authors: Fender123 casid kelunik

repo: casid/jte


text:
cask told me to post this

> brew cask install mongo-management-studio

Error: wrong number of arguments (1 for 0) while loading '/usr/local/Library/Taps/caskroom/homebrew-cask/Casks/mongo-management-studio.rb'
Please report this bug:
https://github.com/caskroom/homebrew-cask/issues

:5:in `name'
:5:in `'
:in `'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/source/path_base.rb:65:in `eval'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/source/path_base.rb:65:in `rescue in load'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/source/path_base.rb:62:in `load'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/source/tapped.rb:28:in `load'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask.rb:124:in `load'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli/install.rb:19:in `block in install_casks'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli/install.rb:17:in `each'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli/install.rb:17:in `install_casks'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli/install.rb:6:in `run'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli.rb:81:in `run_command'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli.rb:121:in `process'
/usr/local/bin/brew-cask.rb:42:in `'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/Library/brew.rb:58:in `require?'
/usr/local/Library/brew.rb:146:in `'

Old versions of the brew cask command can fail with recent packages. Upgrading homebrew-cask should fix the problem:
brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup

beautiful, thanks

source: gharchive/issue

authors: hackerhasid ndr-qef

repo: caskroom/homebrew-cask

license_type: permissive

license_source: github-api


text:
Mimic homebrew submission templates

They have an interesting approach. Here’s what I was met with when submitting a PR:
### All Submissions:

- [ ] Have you followed the guidelines in our [Contributing](https://github.com/Homebrew/homebrew/blob/master/.github/CONTRIBUTING.md) document?
- [ ] Have you checked to ensure there aren't other open [Pull Requests](https://github.com/Homebrew/homebrew/pulls) for the same update/change?

_You can erase any parts of this template not applicable to your Pull Request._

### New Formulae Submissions:

- [ ] Does your submission pass
`brew audit --strict --online <formula>` (where `<formula>` is the name of the formula you're submitting)?
- [ ] Have you built your formula locally prior to submission with `brew install <formula>`?

### Changes to Homebrew's Core:

- [ ] Have you added an explanation of what your changes do and why you'd like us to include them?
- [ ] Have you written new tests for your core changes, as applicable? [Here's an example](https://github.com/Homebrew/homebrew/pull/49031) if you'd like one.
- [ ] Have you successfully ran `brew tests` with your changes locally?

And for an Issue:
# Please follow the general troubleshooting steps first:

- [ ] Ran `brew update` and retried your prior step?
- [ ] Ran `brew doctor`, fixed as many issues as possible and retried your prior step?
- [ ] If you're seeing permission errors tried running `sudo chown -R $(whoami) $(brew --prefix)`?

_You can erase any parts of this template not applicable to your Issue._

### Bug reports:

Please replace this line with a brief summary of your issue **AND** if reporting a build issue include the link from:

`brew gist-logs <formula>`
(where `<formula>` is the name of the formula that failed to build).

### Feature/Formula Requests:

**Please note by far the quickest way to get a new feature or formula into Homebrew is to file a [Pull Request](https://github.com/Homebrew/homebrew/blob/master/.github/CONTRIBUTING.md).**

We will consider your request but it may be closed if it's something we're not actively planning to work on.

Having boxes you specifically need to tick seems like a great way to ensure people have actually read what’s in them (which doesn’t always happen with us).
Also, take a look at their Contributing document. A quick steps-based document that links to others depending on what you need to know more about seems like a great solution.
Pinging @caskroom/maintainers. @adidalal might be particularly interested.

Am interested, but will likely be pending for a bit as I am not around to implement currently

Updated with the issue template as well.

Not a huge fan of their CONTRIBUTING - I like our current layout, honestly. The most common thing (updating a Cask) is easily visible, and (luckily) cask-repair automates away most of the pain after that. Adding a cask is alrady a step-by-step doc, and links to core/hacking are also there.
If anything, the issue templates could be merged into as appropriate/revamped, and our FAQ expanded (ie "where's brew cask upgrade" is getting a bit repetitive)

Fair point on the CONTRIBUTING, though for adding a cask I’d like to see clear guidelines to run brew cask audit and brew cask style --fix before submitting. That should be part of the PR template, though. In that regard, I believe they’ve done the right thing: not only making each step clear, making you tick the boxes of what you’ve done, thus making it less likely to skim.

Still aware of this but it's on the back burner priority-wise. If there's a huge uptick in errant issue requests I'll try to do it ASAP, but I'd like to roll it into a slightly more comprehensive issue template revamp incorporating https://github.com/blog/2111-issue-and-pull-request-templates instead of our current hack-ish workaround.

Sure, take your time.

First draft/suggestion for new PRs:
# Instructions:

- Delete every part of this placeholder text irrelevant to your submission, including these instructions.
- `{{cask_file}}` is used a placeholder to the actual cask you’re submitting/editing (if applicable)
- If there’s a checkbox you can’t complete for any reason, that’s OK. Just explain in detail why you weren’t able to do it.

### Changes to a cask
#### Editing an existing cask

- [ ] `brew cask audit {{cask_file}}` is error-free.
- [ ] `brew cask style --fix {{cask_file}}` left no offenses.

#### Adding a new cask

- [ ] Checked there aren’t open [pull requests](https://github.com/caskroom/homebrew-cask/pulls) for the same change.
- [ ] Checked there aren’t closed [issues](https://github.com/caskroom/homebrew-cask/issues) where that cask was already refused.
- [ ] When naming my cask, followed the [token reference](https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/token_reference.md).
- [ ] `brew cask audit {{cask_file}}` is error-free.
- [ ] `brew cask style --fix {{cask_file}}` left no offenses.
- [ ] `brew cask install {{cask_file}}` worked successfully.
- [ ] `brew cask zap {{cask_file}}` worked successfully.

### Changes to the core

- [ ] Followed [hacking.md](https://github.com/caskroom/homebrew-cask/blob/master/doc/development/hacking.md).

This is now complete.

authors: adidalal vitorgalvao


text:
Bug report: [microsoft-lync-plugin has been officially discontinued upstream]

Remember to follow the pre bug report guide beforehand. Failure to do so might get your issue closed.
Description of issue
microsoft-lync-plugin has been officially discontinued upstream
MacBook-Pro:~ christophechirat$ brew install Caskroom/cask/microsoft-lync-plugin
==> brew cask install Caskroom/cask/microsoft-lync-plugin
==> Caveats
microsoft-lync-plugin has been officially discontinued upstream.
It may stop working correctly (or at all) in recent versions of macOS.
==> Downloading https://lync12.lyncweb.microsoft.com/lwa/Plugins/LWAPluginInstaller.pkg
curl: (6) Could not resolve host: lync12.lyncweb.microsoft.com
Error: Download failed on Cask 'microsoft-lync-plugin' with message: Download failed: https://lync12.lyncweb.microsoft.com/lwa/Plugins/LWAPluginInstaller.pkg
The incomplete download is cached at /Users/christophechirat/Library/Caches/Homebrew/Cask/microsoft-lync-plugin--latest.pkg.incomplete

Home page doesn’t even exist anymore. I’ll just remove the cask altogether.

authors: ChristopheChirat vitorgalvao


text:
Cask (sqlworkbenchj) Not Updating to Latest Version

Description of issue
sqlworkbenchj is not updating to latest version (123):  https://github.com/caskroom/homebrew-cask/blob/master/Casks/sqlworkbenchj.rb
Output of your command with --verbose --debug
brew update --verbose && brew upgrade --verbose                                    19:27:29
Checking if we need to fetch /usr/local/Homebrew...
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask...
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/chainsawbaby/homebrew-formula...
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-completions...
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core...
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-services...
Updating /usr/local/Homebrew...
Reset branch 'stable'
Current branch stable is up to date.

Already up-to-date.

brew cask info sqlworkbenchj
sqlworkbenchj: 123
https://www.sql-workbench.net/
/usr/local/Caskroom/sqlworkbenchj/122 (64B)
From: https://github.com/caskroom/homebrew-cask/blob/master/Casks/sqlworkbenchj.rb
==> Name
SQL Workbench/J
==> Artifacts
SQLWorkbenchJ.app (App)
==> Caveats
sqlworkbenchj requires Java. You can install the latest version with

  brew cask install java

brew cask list --versions | grep sqlworkbenchj
sqlworkbenchj 122

Output of brew cask doctor
==> Homebrew-Cask Version
Homebrew-Cask 1.3.6
caskroom/homebrew-cask (git revision 43c5e; last commit 2017-10-27)
==> Homebrew-Cask Install Location
<NONE>
==> Homebrew-Cask Staging Location
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3776 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib
/Library/Ruby/Site/2.3.0
/Library/Ruby/Site/2.3.0/x86_64-darwin17
/Library/Ruby/Site/2.3.0/universal-darwin17
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby/2.3.0
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby/2.3.0/x86_64-darwin17
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby/2.3.0/universal-darwin17
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/x86_64-darwin17
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17
==> Environment Variables
LANG="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
PATH="/usr/local/sbin:/usr/local/Cellar/python/2.7.12_2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Applications/Postgres.app/Contents/Versions/9.6/bin:/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/cmd:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/bin/zsh"

Cask doesn't auto-update, run brew cask reinstall sqlworkbenchj


text:
Outdated cask: android-studio

android-studio
latest version: 3.1
I deleted the file and retried three times, and it still told me the checksum does not match.
$ brew cask reinstall android-studio --force
==> Satisfying dependencies
==> Downloading https://dl.google.com/dl/android/studio/install/3.1.0.16/android
######################################################################## 100.0%
==> Verifying checksum for Cask android-studio
==> Note: running "brew update" may fix sha256 checksum errors
Error: Checksum for Cask 'android-studio' does not match.

Expected: 0049960274b2c5670b1d448b5b9646b63079ca6d0576c5a611ae6c89b3d03d29
Actual:   920f1505fd6b8c23d8c56c1ebc72bbea2c99c3c1badc9747372a1fc9d7add04c
File:     /Users/daniel/Library/Caches/Homebrew/Cask/android-studio--3.1.0.16,173.4670197.dmg

To retry an incomplete download, remove the file above.

sha256 should be https://developer.android.com/studio/index.html per android website. I have sent a git commit for the change.

thanks, is this fixed now?

The pull request is currently on the page. Once the item is merged it will be back to normal function.

authors: PureWhiteWu TheeNawMan


text:
add GoPro-App cask

unsure about the name, options/reasons:

name
reason

gopro
this installs GoPro.app (as well as GoPro Studio.app); download is GoPro-MacInstaller...

gopro-app
some gopro pages call it "GoPro App | Desktop"

gopro-app-desktop
some gopro pages call it "GoPro App for Desktop"

gopro is the way to go.

@vitorgalvao renamed

Thank you for the contribution. It was merged directly as 16696212b603df21be7875507dbfbeaea18ae97c to keep commit history cleaner. Your contribution is still credited to you.

source: gharchive/pull-request

authors: adidalal jconley vitorgalvao


text:
updated jabref (3.4)

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

So...I'm a little embarrassed that I didn't catch this before submitting a pull request, but after actually installing the new version, I realized that there was an issue with their 3.4 build on OS X. After all of two seconds of browsing jabref's issues page, I found someone had already reported both the issue and a temporary fix in jabref issue #1481.
Anyway, I can confirm @kojiyokota's report that running the app using java -jar path/to/JabRef.app/Contents/java/app/JabRef-3.4.jar works fine. However, I'll leave it to your discretion, @vitorgalvao, whether this will suffice in the interim, or if it would be better to just roll back this pull-request.

@joeygravlin Should be fine. Seems like they’ll look into a fix soon.

authors: joeygravlin vitorgalvao


text:
add Camunda Modeler v1.2.0

Instructions

Look for and complete the section relevant to your submission. Delete the others, including these Instructions.
{{cask_file}} represents the cask file you’re submitting/editing (if applicable).
If there’s a checkbox you can’t complete for any reason, that’s OK. Just explain in detail why you weren’t able to do so.

Adding a new cask

[x] Checked there aren’t open pull requests for the same cask.
[x] Checked there aren’t closed issues where that cask was already refused.
[x] When naming the cask, followed the token reference.
[x] Commit message includes cask’s name.
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.

provide new cask, see #22817
fix 'name'
add checksum

I am sorry for the inconvenience ... I had to re-fix the checksum due to some remote/local mix up ... can you accept it like this, or should I squash and create a new PR?

Looks fine. Thank you.

thanks.

authors: jangalinski vitorgalvao


text:
Remove Yate.

Download link is protected with JavaScript.

Why was this removed? The last cask script worked fine and I was able to update to 3.15 right now using cask-repair.

Can confirm it just worked for me.

authors: decrement reitermarkus vitorgalvao


text:
Update anypass to 1.0.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as dbaac0fd9916028ece7832f8b183436021c703e1 to keep commit history cleaner. Your contribution is still credited to you.

authors: giannitm vitorgalvao


text:
🛑 Baked Bean is down

In 9de8b7d, Baked Bean (https://baked-bean.co.uk) was down:

HTTP code: 403
Response time: 225 ms

Resolved: Baked Bean is back up in e90dd04.

license: MIT


text:
Bump package.json signer version

Resolves package.json version
Summary
Change to increment Casper Signer version from 1.4.26 to 1.4.27 in package.json and package-lock.json
TODO

[x] N/A.

Checklist

[x] Code is properly formatted - Yes
[x] Tests included/updated or not needed - Not needed
[x] Documentation has been updated or is not required - Not required

Build artifact for QA: Please refer commit details.

@devendran-m What about the version field in the manifest.json?

@devendran-m What about the version field in the manifest.json file?

Hi @mrkara , thanks for highlighting this. I have pushed another commit to this PR, to bump the version in manifest.json

@devendran-m I verified that the new Signer build is correct.
I would like to propose that you should add a Release Checklist in the wiki section and put there all steps related to versioning so we don't have to spend time on again figuring out the process of bumping a package version on release.

authors: devendran-m mrkara piotrwitek

repo: casper-ecosystem/signer


text:
release-1.4.6 trie-compact tool

We need to move the code in https://github.com/casper-network/casper-node/pull/2948 to a subcommand of the db-utils tool.
The review comments should be addressed as part of this work, ideally as a separate commit to simplify the review.  Any further deviations/improvements other than changes strictly required to support the move should be kept to standalone commits too, for the same reason.

Closed in https://github.com/casper-network/casper-db-utils/pull/11

authors: georgepisaltu piotr-dziubecki

repo: casper-network/casper-db-utils


text:
Use match statements to avoid runtime errors

Refactor to use match statements to avoid errors appearing only at runtime instead of being caught by the compiler.
In both cases I found invalid tags should be caught when parsing from u8, so the error branches would never be reached anyway.

bors r+

bors r+

repo: casper-network/casper-node


text:
What changes have you made to the PX4 source code?

   Hello,Thank you very much for your previous help.But I still have some questions.  I would like to ask how do you use the code of Pixhawk to control the Fully-actuated UAV?What changes have you made to the PX4 source code?Is it mainly about modifying the control allocation matrix?This control principle is not described in detail in your paper, so I hope to get your help.

how do you use the code of Pixhawk to control the Fully-actuated UAV?

The control is very similar to the normal UAV using PX4, except that the attitude behavior is defined by the OMNI_ATT_MODE parameter. For example, in mode 2, the roll and pitch controllers will move the UAV on the horizontal plane very similar to the normal behavior except that there is no tilting anymore. I encourage you to try it out in the simulator to learn the behavior.

What changes have you made to the PX4 source code? Is it mainly about modifying the control allocation matrix? This control principle is not described in detail in your paper, so I hope to get your help.

Control allocation needs to fit the structure of the drone and there are many papers describing different allocation methods. We modified PX4's control allocation to work with 3-D thrust and generate the allocation matrix for our drone, but it was not a novel contribution and thus was not the focus of the ICRA paper. You can use any method for control allocation.
That said, the main changes to the source code related to the paper are in the position controller module. You can git diff our code with the last commit before my commits to see what changes we have made.

how do you use the code of Pixhawk to control the Fully-actuated UAV?

The control is very similar to the normal UAV using PX4, except that the attitude behavior is defined by the OMNI_ATT_MODE parameter. For example, in mode 2, the roll and pitch controllers will move the UAV on the horizontal plane very similar to the normal behavior except that there is no tilting anymore. I encourage you to try it out in the simulator to learn the behavior.

What changes have you made to the PX4 source code? Is it mainly about modifying the control allocation matrix? This control principle is not described in detail in your paper, so I hope to get your help.

Control allocation needs to fit the structure of the drone and there are many papers describing different allocation methods. We modified PX4's control allocation to work with 3-D thrust and generate the allocation matrix for our drone, but it was not a novel contribution and thus was not the focus of the ICRA paper. You can use any method for control allocation.
That said, the main changes to the source code related to the paper are in the position controller module. You can git diff our code with the last commit before my commits to see what changes we have made.

Thank you very much for your help. I will continue to learn your scheme.

Thank you very much for your help. I will continue to learn your scheme.


text:
EPA CEMS Intake Catalog

Description
Create a full featured Intake Catalog for distributing the EPA CEMS hourly emissions data stored as Parquet files. This follows some exploration in #1155, and feeds into #1179. I'm importing some overly broad design thoughts from #1495.
Billing
This work should be billed under our Sloan Foundation "Data Distribution" sub-project.
Goals

Allow users to easily work with this relatively large data set (~1 billion rows, 50GB uncompressed).
Make it fast and easy to query subsets of the dataset remotely, without having to download the whole thing.
Provide human and machine readable metadata in association with the data itself, so that users can understand what they're working with.
Ensure that parquet file names are human & machine readable, and compatible with many different filesystems and parquet access methods.
Ensure that our EPA CEMS ETL outputs data that's appropriate for distribution as a data catalog.

Methods

Partition the data by common filter columns (years, states) to make queries fast. This can be done in one file (using row groups) or many files (each of which is its own row group).
Allow efficient local filesystem caching of the remote data, so that users don't have to download it all at once, and so nobody has to pay unnecessary data egress fees. This means breaking it up into smaller individual files, like one per (state, year).
Enable parallel/distributed processing of the parquet outputs, avoiding concurrent writes to the same files from different workers.
Programmatically export metadata from our Pydantic models directly into the PyArrow schema, and also into the Intake catalog YAML file.

Problems

intake_parquet doesn't seem to be able to efficiently query a collection of separate parquet files using filters. It seems to still search through all of them when using wildcards like {{ env(INTAKE_PATH) }}/epacems/epacems*.parquet
intake_parquet can't take a directory (filled with parquet files) as its urlpath even though pandas and dask are happy to read from a directory. E.g. {{ env(INTAKE_PATH) }}/epacems/ does not work.
The simplecache file based caching that's available in some Intake plugins and that uses fsspec to access many different remote filesystems has not been implemented for intake_parquet.
The overhead associated with parallel / distributed processing of individual (state, year) partitions is too high for this arrangement to be efficient.
It's unclear how to specify min/max allowable years or the set of allowable state abbreviations for filtering, or how to enforce those limitations and provide useful feedback to the user if they are violated.
Pandas nullable string columns show up as object when read via intake-parquet

Tasks (to be turned into issues)
Minimum Viable Catalog
Publish a basic EPA CEMS data catalog that makes use of basic Intake functionality.

[x] Switch to producing a single EPA CEMS Parquet file as output, with (year, state) row groups (See #1563).
[ ] Ensure that all column types are preserved by Intake as they would be by read_parquet()
[ ] Determine the right format for table and column metadata in the YAML catalog file (names, types, descriptions).
[ ] Automate export of the catalog metadata from our Pydantic metadata models.
[ ] Constrain or at least indicate what years and states can be used to filter the data efficiently.
[ ] Create a dedicated repository for our high-level data catalog.
[ ] Set up CI in the data catalog repository to test whether the catalog is valid and working.
[ ] Package and publish that catalog for installation via conda.

Ideal Catalog
Improve the usability of the EPA CEMS data catalog by enabling file caching and fast filtering on collections of Parquet files. This may or may not be strictly necessary for EPA CEMS depending on how fast everyone's network connections are, and how much we end up paying in data egress fees. E.g. or cloud-based access where you have a 1-10Gbit network connection, downloading 5GB of data will only take seconds, and if it's in the same zone as our storage, there will be no fees.
In addition to allowing efficient file caching, distributing the data in many smaller files will make it easier to split up the work of processing the data across many workers (they can all write their own state-year files) without needing to then combine those smaller files into a single large file at the end.

[ ] Implement fsspec / simplecache based file caching for the intake_parquet plugin (See also #1496)
[ ] Implement fast filtering for collections of parquet files (either wildcard or directory based) within the intake_parquet plugin.
[ ] Switch to producing a directory of epacems-YYYY-SS.parquet files when file caching and fast filtering are working.

Out of Scope

Parallelizing / Distributing the processing of the EPA CEMS data (that'll happen in the Dagster refactor).
Any additional EPA CEMS data wrangling, e.g. the things discussed in #1049

Whoops yes I forgot to add the intake requirements. I had them installed in my local environment.
The dtypes you've got listed there seem to be the correct ones. But you have no year or state columns.  I'm still confused as to why those aren't showing up, given that the data is definitely stored in the files.
I really don't understand how the source specific metadata works. My suspicion is that the allowable year/state values can be put in there, and the column/table descriptions, but I don't see any documentation on how to do it appropriately.

Hey @martindurant thanks so much for your comment on #1496! I got simplecache working and created a basic installable catalog, and have been experimenting with different setups for our open US energy data catalog over in the pudl-catalog repo. I've collected a bunch of outstanding issues in the issue above, which point at the individual pudl-catalog issues and was wondering if we might be able to get some advice from you on how best to set things up. I'm not sure which of these things is just me not understanding how to configure the catalog correctly and which are deeper constraints.
Do you happen to have a list of publicly visible intake catalogs that use Parquet data sources? I've tried searching GitHub but haven't been very successful. The CarbonPlan Data repo is the best I've seen, but they have a very simple configuration.
Once the EPA CEMS Hourly Emissions data source is finished, we also want to look at writing an intake-sqlite driver (#1156) to manage the distribution of versioned SQLite databases, which will download and cache the database file locally, and then use the intake-sql driver to access it. Does that seem like a reasonable approach?  Thanks for any pointers you can offer!

repo: catalyst-cooperative/pudl

license: mit

license_source: bigquery


text:
count() ignores $where clause

I tried to use count as follows for a reason:
public function count_main($table,$join=NULL,$column=NULL,$where=NULL){

		$count = $db->medoo->count($table,$join,$column,$where);
	}

If the $join and $column are NULL, the count() ignores the $where clause.
But this works:
public function count_main($table,$join=NULL,$column=NULL,$where=NULL){

		$count = $db->medoo->count($table,$where);
	}

This happens because you assign $where = $join if $column is NULL and later $where = $join when $count_fn is SET.
Any way to get around this to use the count() in the format specified ? I always want to pass $join, $column and $where even when they are NULL.

Fixed

authors: amitbansod catfan

repo: catfan/Medoo


text:
Secondary eclipse branch merging

Here I created the merging of branch 'merging-eclipse' which used 'Starry' as a model.

Hi @Pat-Wachiraphan can you send me a notebook with an example fit? I'm struggling to get the initial priors quite right to test it out

I also don't see where limb darkening is used in the code

I have an issue fitting for the stellar amplitude - the logP goes to inf or nan

when run cm.add_model_to_rainbow() function, it seems like the parameters that pass to eclipse_model are not correct. Probably the extract_from_posteriors function doesn't account for Fitted with shape = 2 case. It make the ecs parameter has only 1 instance instead of 2.
The error
KeyError                                  Traceback (most recent call last)
Cell In[3], line 1
----> 1 cm.add_model_to_rainbow()

File ~/Work/chromatic_fitting/chromatic_fitting/models/combined.py:535, in CombinedModel.add_model_to_rainbow(self)
    533 if isinstance(mod, TransitModel) or isinstance(mod, EclipseModel):
    534     if i_transit == 0:
--> 535         transit_model = mod.get_model()
    536     else:
    537         # I'm not sure that this works if the combination option is multiply or divide
    538         transit_model = combination_options[self.how_to_combine[i - 1]](
    539             transit_model, mod.get_model()
    540         )

File ~/Work/chromatic_fitting/chromatic_fitting/models/lightcurve.py:1181, in LightcurveModel.get_model(self, params_dict, as_dict, as_array, store)
   1179             params = params_dict[f"w{i}"]
   1180     print (params, i)
-> 1181     model_i = self.model(params, i)
   1182     model[f"w{i}"] = model_i
   1184 if store:

File ~/Work/chromatic_fitting/chromatic_fitting/models/eclipse.py:347, in EclipseModel.eclipse_model(self, eclipse_params, i, time)
    332 self.check_and_fill_missing_parameters(eclipse_params, i)
    334 star = starry.Primary(
    335     starry.Map(
    336         ydeg=0,
   (...)
    344     prot=eclipse_params[f"{name}stellar_prot"],
    345 )
--> 347 omega = theano.tensor.arctan2(eclipse_params[f"{name}ecs[1]"], eclipse_params[f"{name}ecs[0]"])
    348 eccentricity = pm.math.sqrt(eclipse_params[f"{name}ecs[0]"]**2+eclipse_params[f"{name}ecs[1]"]**2)
    350 planet = starry.kepler.Secondary(
    351     starry.Map(
    352         ydeg=0,
   (...)
    368     mass_unit=u.M_jup,
    369 )

KeyError: 'eclipse_ecs[1]'

The parameters passed through eclipse_model
{'eclipse_stellar_radius': 0.265, 'eclipse_stellar_mass': 0.257, 'eclipse_stellar_amplitude': 1.0, 'eclipse_stellar_prot': 1.0, 'eclipse_period': 5.3587657, 'eclipse_t0': 2458412.70851, 'eclipse_planet_log_amplitude': -4.1435571387, 'eclipse_inclination': 89.68, 'eclipse_planet_mass': 0.00903, 'eclipse_planet_radius': 0.1164, 'eclipse_ecs': 0.0123583112, 'eclipse_limbdark1': 0.4, 'eclipse_limbdark2': 0.2}

@Pat-Wachiraphan is this ready for a review to be merged?

@Pat-Wachiraphan is this ready for a review to be merged?

Sorry for the delay but yes! I think it should be ready!

I've encounter problem with plot_priors and plot_posteriors. I'm not sure how to fix this but yet.
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Cell In[16], line 1
----> 1 visit1.plot_priors()

File ~/Work/chromatic_fitting/chromatic_fitting/models/lightcurve.py:871, in LightcurveModel.plot_priors(self, n, quantity, plot_all)
    869             else:
    870                 i_dict = {**i_dict, **{k: v[i][w]}}
--> 871         model_for_this_sample.append(self.model(i_dict))
    872     model_for_this_sample = np.array(model_for_this_sample)
    874 # add posterior model and draw from posterior distribution to the Rainbow quantities:

TypeError: CombinedModel.combined_model() takes 1 positional argument but 2 were given

authors: Pat-Wachiraphan catrionamurray


text:
Model deadline

Is the model deadline still 14th April, despite the delay in the challenge starting and the starter repo being available? Thanks!

hi @finlayiainmaclean, thank you very much! No extensions to the deadline are planned.
We unfortunately do not have flexibility to adjust the timeline because the challenge is linked to the MLDD workshop at ICLR where we plan to announce the winners. Many thanks for your understanding and best of luck! 🥇

authors: causalbench finlayiainmaclean

repo: causalbench/causalbench-starter


text:
Fail image_optim hook if gem not installed

Per discussion in #100.

Merged in b16ce1a8512986491b05cd093ee6c16bf8145cf5. Thanks!

authors: jawshooah sds

repo: causes/overcommit


text:
🛑 Artfos ERP is down

In a750ac7, Artfos ERP (https://intranet.artfos.com.ar/equipo/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Artfos ERP is back up in 65980dd.

repo: cavalicenti/upptime


text:
Feature/server sessions

Добавил sessions/join и sessions/create. Протокол общения как в apiary.
Техническое описание:

Контроллер sessions_controller с двумя запросами
Переименнованный participation_storage (в SessionsStorage), который хранит мапу сессий и invite кодов. Также есть всякие методы для обращения к сессиям.
Класс GameSession, в котором хранятся user_id игроков, соответствие player_id и т.п.
Класс GameSessionInfo -- сжатая информация GameSession для передачи клиенту (из документации api)

Менее относящееся к функциональности:

В своих методах сделал ошибки валидации через exceptions вместо std::optional, просто такое чувство, что это какой-то питонизм или джавизм
Создал пока тупой AuthenticationManager. В будущем будет JWT/JWK.
Какие-то микроутилиты. Например, макрос для drogon, чтобы сразу отдавать пустой запрос с нужным status code.
затронутые и новые файлы начал пихать по папочкам, потому что папка model начала расширяться...
наверняка что-то ещё...

В apiary не указано, что требуется URI параметр user_id

При попытке повторно присоединиться к комнате с тем же user_id ответ сервера -- 400 без каких-либо комментариев.

Если к уже заполненной сессии подключается человек, сервер отвечает просто 400 без комментариев, почему Request is Bad

Запрос на получение обновления всё ещё называется get_update а не get_state, как в apiary

Если я правильно понял, то у тебя нет возможность по player_id и session_id получать user_id. Но это требуется, если мы собираемся узнавать, кто победил (т. к. логика возвращает player_id)

Запрос на получение обновления всё ещё называется get_update а не get_state, как в apiary

Это не входит в этот реквест, это есть у Пети

В apiary не указано, что требуется URI параметр user_id

@MarkTheHopeful Казалось бы и в create, и в join это всё-таки есть?

authors: MarkTheHopeful petrtsv waleko

repo: cavoke-project/cavoke


text:
My First PR commit

PR comments

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: cjxd-bot-test
If they are not already assigned, you can assign the PR to them by writing /assign @cjxd-bot-test in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

:star: PR built and available in a preview environment cb-kubecd-bdd-nh-1587589737-pr-1 here


text:
My First PR commit

PR comments

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: cjxd-bot-test
If they are not already assigned, you can assign the PR to them by writing /assign @cjxd-bot-test in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

:star: PR built and available in a preview environment cb-kubecd-bdd-nh-1588473714-pr-1 here


text:
My First PR commit

PR comments

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: cjxd-bot-test
If they are not already assigned, you can assign the PR to them by writing /assign @cjxd-bot-test in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

:star: PR built and available in a preview environment cb-kubecd-bdd-sbhg-1583456327-pr-1 here


text:
My First PR commit

PR comments

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: cjxd-bot-test
If they are not already assigned, you can assign the PR to them by writing /assign @cjxd-bot-test in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

:star: PR built and available in a preview environment cb-kubecd-bdd-sbhg-1585888795-pr-1 here


text:
features for v1.0.0

Inherit the original author's intention and continue to improve：
Must have

[x] Support for custom Image component (ImageProgress, FastImage etc)
[ ] Support for lo-res thumbnail -> hi-res transition
[ ] Set up CI to run tests and release
[ ] Andorid hardware back button support
[ ] Gesture to close by swiping down/up
[x] No dependency on navigation lib
[x] No dependency on Modal
[ ] Improved peformance with native animation driver
[ ]  Feature parity between Android and iOS

Really nice to have

[ ] Support for aspect-ratio change from thumbnail -> hi-res
[ ] Pinch to zoom
[x] Double-tap to zoom
[ ] Support for gallery mode
[ ] Configurable Touchable component
[ ] Configurable transition properties
[ ] Configurable status bar transitioning
[ ] Configurable/custom header/footer

Nice to have

[ ] Pure JavaScript implementation
[ ] Integration library with react-navigation (et al)
[ ] Integration library with redux
[ ] Support Image->Video transition
[ ] Some form of lifecycle support (will/did open/close)

On the fence

[ ] Orientaion change support
[ ] Programmatic way of opening/closing lightbox

Not doing

[ ] Generic shared element transition

That's quite the undertaking. Would love to see this complete :D

Welcome！

save image feature?

f you happen to need the ability to use this warehouse, you can stay and build it together, welcome!

FYI on Android 10+ there's no need to provide a navigator, it works anyway

FYI on Android 10+ there's no need to provide a navigator, it works anyway

thx~

Please Support for gallery mode

Please Support for gallery mode

we can custom our gallery like in demo, but it's so good, if we can use a props, like mode: 'gallery', auto support it !

Seems like orientation change should be high on the list. I wanted so bad to use this lib but the first thing i checked was a device rotation, and it wasn't pleasant. Seems like you could get most of the way there by changing out the old way:

// from this

const { width, height } = Dimensions.get('window')

// to this

const { width, height } = useWIndowDimensions()

The latter is reactive instead computed once on load.

Please note that there is still an open issue with useWindowDimensions. See https://github.com/facebook/react-native/issues/29290

authors: cbbfcd dariuscosden demedos dongdyang hellotreedigital jforaker

repo: cbbfcd/react-native-lightbox


text:
Support dynamic screen orientation changes

Allow IOS to render the lightbox in landscape orientation
Use useWindowDimensions() as recommended by react team so that dimensions update correctly when orientation changes.
update dist, as it appears some previous commits did not include the updated build

Thank you! Can you help resolve the conflicts?

It actually looks that this fix may not be necessary as another a similar one was merged ~7 months ago
Any idea if a new release with this fix will be made soon?

ok~ thx again!


text:
feat: Debug for Value and Key to be optional

error[E0277]: `User` doesn't implement `Debug`
  --> examples/borsh.rs:12:22
   |
12 | impl redb::Value for User {
   |                      ^^^^ `User` cannot be formatted using `{:?}`
   |
   = help: the trait `Debug` is not implemented for `User`
   = note: add `#[derive(Debug)]` to `User` or manually `impl Debug for User`
note: required by a bound in `Value`
  --> /home/dz/github.com/cberner/redb/src/types.rs:74:18
   |
74 | pub trait Value: Debug {
   |                  ^^^^^ required by this bound in `Value`
help: consider annotating `User` with `#[derive(Debug)]`
   |
8  | #[derive(Debug)]
   |

error[E0277]: `Id` doesn't implement `Debug`
  --> examples/borsh.rs:50:22
   |
50 | impl redb::Value for Id {
   |                      ^^ `Id` cannot be formatted using `{:?}`
   |
   = help: the trait `Debug` is not implemented for `Id`
   = note: add `#[derive(Debug)]` to `Id` or manually `impl Debug for Id`
note: required by a bound in `Value`
  --> /home/dz/github.com/cberner/redb/src/types.rs:74:18
   |

I would like to avoid Debug in our production code, only in test, so Debug for sure does not slows performance.
Debug is optional feature.

If you're worried about performance, you should be able to use cfg in your Debug implementation to make it a no-op in production. Is there a reason that doesn't work?

I guess yes, this is workaround. So it will not allow to read behavior out of struct definition.

Also, workaround does not guarantees redb does not creates some temporal structures which are compiled away without being created just for Debug.

Debug is poor man json serde kind of, it should be optional feat of redb, like redb could have optional support of some serde kinds of for example.

I decided not to add support in redb for serde. You can find the reasoning in past issues, such as this one: https://github.com/cberner/redb/pull/805

authors: cberner dzmitry-lahoda

repo: cberner/redb


text:
on

TestNG Version

Note: only the latest version is supported

Expected behavior
Actual behavior
Is the issue reproductible on runner?

[ ] Shell
[ ] Maven
[ ] Gradle
[ ] Ant
[ ] Eclipse
[ ] IntelliJ
[ ] NetBeans

Test case sample

Please, share the test case (as small as possible) which shows the issue

Empty bug. Closing this off

authors: dmitriy-zhydchenko krmahadevan

repo: cbeust/testng


text:
"mySalt" is not defined. (createLoginDataJs#3)

Release v0.1.3
Script attempted a restart but got this error:
[2020-05-18T05:00:01.119661300] Could not restart router! Reason:
org.mozilla.javascript.EcmaError: ReferenceError: "mySalt" is not defined. (createLoginDataJs#3)
        at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:4236)
        at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:4214)
        at org.mozilla.javascript.ScriptRuntime.notFoundError(ScriptRuntime.java:4304)
        at org.mozilla.javascript.ScriptRuntime.name(ScriptRuntime.java:1924)
        at org.mozilla.javascript.gen.createLoginDataJs_12._c_createLoginData_0(createLoginDataJs:3)
        at org.mozilla.javascript.gen.createLoginDataJs_12.call(createLoginDataJs)
        at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:412)
        at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3545)
        at org.mozilla.javascript.gen.createLoginDataJs_12.call(createLoginDataJs)
        at MainKt$restartRouterInternal$4.invokeSuspend(Main.kt:290)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:825)

Full log attached. Thank you.
log.txt

Strange, seems like your router either performs encryption differently or not at all. Can you check what this page says for you? For reference, here's what it looks like for me:

See here:

authors: cbruegg theotherp

repo: cbruegg/packetloss-watchdog


text:
🛑 MRSpec Portal is down

In 9981b79, MRSpec Portal (https://mrspec.ccm.sickkids.ca) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MRSpec Portal is back up in e70f1d8 after 12 minutes.

repo: ccmbioinfo/status


text:
Create eve_market.md

Added a documentation for the market endpoint (explaining history). Hope this suits the doc standards.

You may wonna add your name in CONTRIBUTORS too. Give credits to yourself.

Added info from https://developers.eveonline.com/blog/article/new-crest-resource-for-bulk-market-orders, but still unsure about the parameter handling.

Will try and respond tonight. Last week at the office and a lot to do so sorry for the delayed responses.

For the parameters I think it would be best just to have Paramaters section under the Route section (still H4) that has a l list of possible parameters for the route.
Does anyone see a better way to handle params?

How can we get more insight on the parameters? Which ones are available, what values do they expect, what changes when I use different verbs?

You typically get this data by making an OPTIONS request, although it's not always complete in my experience.  Good overview of this here: https://www.youtube.com/watch?v=QMQOjUjrZIo

The OPTIONS request explains what content is delivered from the server, but does not give insight on the request parameters one can use. So the request parameters are still unclear.

Thanks! I've merged your pull request.

authors: JimiC Regner bahrmichael deadlybulb polarina


text:
Cannot read property 'createModel' of null

hi getting this error while using the package , i might be using it wrong, can you help me with
    storageType: 'file',
    modelPath: './gemma-2b-it-gpu-int4.bin',
  });

That filepath needs to point to a location on your device.
For android, see here
For iOS, you need to find a way to push the file to local application storage, or perhaps an icloud location, if you are familiar with how that works, or potentially using the iOS platform APIs for accessing files.
The easiest way, on both platforms, is simply to bundle the model as an asset.

That filepath needs to point to a location on your device.
For android, see here
For iOS, you need to find a way to push the file to local application storage, or perhaps an icloud location, if you are familiar with how that works, or potentially using the iOS platform APIs for accessing files.
The easiest way, on both platforms, is simply to bundle the model as an asset.

Thank you I will try that, okay I have two more questions

What is the type asset ?
The .bin model, is the right one , right ?

Yes and yes.
On Wed, Jun 26, 2024 at 7:58 AM Kumar Deepanshu @.***>
wrote:

That filepath needs to point to a location on your device.
For android, see here
https://ai.google.dev/edge/mediapipe/solutions/genai/llm_inference/android#push_model_to_the_device
For iOS, you need to find a way to push the file to local application
storage, or perhaps an icloud location, if you are familiar with how that
works, or potentially using the iOS platform APIs for accessing files.
The easiest way, on both platforms, is simply to bundle the model as an
asset.
Thank you I will try that, okay I have two more questions

What is the type asset ?
The .bin model, is the right one , right ?

—
Reply to this email directly, view it on GitHub
https://github.com/cdiddy77/react-native-llm-mediapipe/issues/7#issuecomment-2191510203,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDG2KJY7E57JBCI5VGRNRLZJKUGDAVCNFSM6AAAAABJ4XDTX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJRGUYTAMRQGM
.
You are receiving this because you commented.Message ID:
@.***>

getting this error
createModel [Error: internal: Failed to initialize session: %sCan not open OpenCL library on this device - undefined symbol: clSetPerfHintQCOM]
i have tried it on physical pixel 7 and emulator pixel 8 pro.

Ever figure this out - also having a difficult time figuring out how to bundle the model as an asset or access via a file path to the model on the device.
To bundle, have downloaded a model and included in an assets folder, tried putting it in android/app/src/main/assets, tried putting it in a models/converted folder as well as in the same folder as the file calling the function.
With storageType of file - have put the model on my device and tried accessing with /data/local/tmp/llm/gemma-2b-it-cpu-int4.bin as well as moving it to other locations trying different variations of the file path.
Most interested in getting it working as a bundled asset though.  Any help/pointes appreciated.  Thanks.

Hey guys, I just pushed a new PR attempting to fix the problem of OpenCL library and also commenting about where to put the model files to make it work. I hope this fixes your problems and clear up your doubts 😄

That filepath needs to point to a location on your device.
For android, see here
For iOS, you need to find a way to push the file to local application storage, or perhaps an icloud location, if you are familiar with how that works, or potentially using the iOS platform APIs for accessing files.
The easiest way, on both platforms, is simply to bundle the model as an asset.

I'm setting up my llmInference like this:
const llmInference = useLlmInference({
   storageType: 'file',
   modelPath: '/data/user/0/com.offlinellmpoc/files/gemma-2b-it-cpu-int4.bin',
 });

But my app is getting crashed. I'm not able to get what the issue is

That filepath needs to point to a location on your device.
For android, see here
For iOS, you need to find a way to push the file to local application storage, or perhaps an icloud location, if you are familiar with how that works, or potentially using the iOS platform APIs for accessing files.
The easiest way, on both platforms, is simply to bundle the model as an asset.

I am relatively new to react native and mobile app development. How does one bundle the model as an asset?
According to google docs:

Note: During development, you can use adb to push the model to your test device for a simpler workflow. For deployment, host the model on a server and download it at runtime. The model is too large to be bundled in an APK.

I agree that bundling it as an asset is the best but I do not know how to do it?

@luey-punch I was able to do that by creating a folder named 'assets' inside android/app/src/main and moving the model inside it although it worked, my android was lagging a lot.
 const {generateResponse} = useLlmInference({    storageType: 'asset',     modelName: 'gemma.bin',   });


text:
Installation problem

I tryed to install this plugin on prestashop 1.7.8.10 version, but I get installation error.

What kind of error?

LUCA NAPPINI ha condiviso il seguente file con te:
scrnli_9_4_2024_14-33-51.png
Visualizza file https://share.mail.libero.it/ajax/share/03eea240096e0242376a46d96e0246aca2a7f8bd7e2a4d06/2/m8/fRE1RRlM6Ly9kcml2ZW1haWwtZGVmYXVsdC1hY2NvdW50LzQ5MDM2OD0yMzk5NjMwNTM/aZHJpdmVtYWlsLnJlY2lwaWVudA~cmVwbHkrQUNJWVkyTTJaVkhPUlJSWEJQWVJXUFdFRURZN1RFVkJOSEhJS0Y3NU40QHJlcGx5LmdpdGh1Yi5jb20.ZHJpdmVtYWlsLmZvbGRlcmlk~NDkwMzY4Izk5NjMwNTM
Il collegamento scadrà il 16 aprile 2024

Utilizza il link sopra per scaricare i file. Si aprirà una nuova pagina dalla quale potrai scegliere quali file scaricare.
To download all desired files click on the link above. You will be taken to a new page that allows you to pick the files you want to download.

see image attached....

Il 09/04/2024 11:57 CEST Carmine Di Gruttola @.***> ha scritto:
What kind of error?
—
Reply to this email directly, view it on GitHub https://github.com/cdigruttola/barcodegenerator/issues/1#issuecomment-2044613271, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACIYY2MT4RCRZOPZD3KVHTTY4O3PTAVCNFSM6AAAAABF6E4HQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBUGYYTGMRXGE.
You are receiving this because you authored the thread.Message ID: @.***>

Hi,
you have to create the zip to upload the module. The zip downloaded via https://github.com/cdigruttola/barcodegenerator/archive/refs/heads/master.zip is not valid.
the zip anche folder inside must have named barcodegenerator.zip e the folder must be barcodegenerator

I file che @.*** ha condiviso con te sono scaduti

scrnli_9_4_2024_14-33-51.png

authors: cdigruttola pollat

repo: cdigruttola/barcodegenerator


text:
chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2782

Questions ?
Please refer to the Backport tool documentation


text:
fix(docs): incorrect API reference link in HPA overview

Summary
This PR fixes an incorrect link in the HPA overview doc page.

💔 All backports failed

Status
Branch
Result

❌
k8s-23/main
Backport failed because of merge conflicts

❌
k8s-24/main
Backport failed because of merge conflicts

Manual backport
To create the backport manually run:
backport --pr 1343

Questions ?
Please refer to the Backport tool documentation


text:
Allow overriding GOPROXY

GOPROXY=https://goproxy.cn,https://goproxy.io,direct
This line in Dockerfile is forcing us to use goproxy.cn, and it sometimes returns 504 Gateway Timeout and breaks our build. Can we make this configurable or overridable from an env var? Thanks.
go: [gopkg.in/fsnotify.v1@v1.4.7:](http://gopkg.in/fsnotify.v1@v1.4.7) reading [https://goproxy.cn/gopkg.in/fsnotify.v1/@v/v1.4.7.mod:](https://goproxy.cn/gopkg.in/fsnotify.v1/@v/v1.4.7.mod) 504 Gateway Timeout
The command '/bin/sh -c go mod download -x' returned a non-zero code: 1```

@broom9 According to GOPROXY doc, it will fallback to the next proxy if go  command encountered an error. However, the behavior between comma split(,) and pipe split(|) list is different. I think we should change from comma split to pipe split, because it looks more robust. Again, I don't against to let user to override GOPROXY env. But since cdk-ecr-deployment already pre-built golang binary, I don't understand why we still need to built from scratch?

The go command may be configured to contact proxies or source control servers using the GOPROXY environment variable, which accepts a list of proxy URLs. The list may include the keywords direct or off (see Environment variables for details). List elements may be separated by commas (,) or pipes (|), which determine error fallback behavior. When a URL is followed by a comma, the go command falls back to later sources only after a 404 (Not Found) or 410 (Gone) response. When a URL is followed by a pipe, the go command falls back to later sources after any error, including non-HTTP errors such as timeouts.

Thanks. I agree pipe looks more robust.
The code logic is to rebuild the image from scratch if on CI (when the CI env var is set to 1). So this issue happened in our CI pipelines.

@wchaws Hi, can your change with the GOPROXY separator be also added to v1?

authors: broom9 marcin-kwasnicki wchaws

repo: cdklabs/cdk-ecr-deployment


text:
feat: specs generation for ConstructProps

currently generates deCDK specs for ConstructProps (defined as Properties in the spec) for all constructs of the aws_lambda module
script runs during build process on post-compilation step, and outputs the specs to a file.

@mluk-aws For my understanding, could you explain the purpose of the specs file and how it's different to the JSON Schema and jsii assembly?
I'm guessing it will be used to generate docs, but even if that's indeed the case would like to understand a little bit more how it will be used.

@mluk-aws For my understanding, could you explain the purpose of the specs file and how it's different to the JSON Schema and jsii assembly?
I'm guessing it will be used to generate docs, but even if that's indeed the case would like to understand a little bit more how it will be used.

@mrgrain It will be consumed here: https://github.com/cdklabs/cdk-ops/pull/2216.

authors: mluk-aws mrgrain otaviomacedo

repo: cdklabs/decdk


text:
ci: finish release please fix

Many commits and test fixes later, I finally managed to fix the release please bot to use the workspace and publish it to npm.

I also made release-please a bit more resilient so it installs/builds/tests, just as npm-publish.yaml does, before publishing. Since --filter uses that package.json, it actually doesn't run the roots "prepare" script, it uses the package.json prepare script, which doesn't exist. What I noticed in my testing was, that it will still publish, even if ./dist doesn't exist. So it would publish without the types. The additions will safeguard that, since there is no prepare, but just something to note.
(I thought about including a prepare script for that package, but husky is a root dependency and not one for that workspace, so rather than duplicate the dependency and bloat it a bit, I chose to just run all the typical ci suites... Technically, this would be after a persons PR got merged, therefore, already running the test suites, therefore running the test twice. Once before a person's merged, and once after the bots version change gets merged)

Lastly, it should be noted that post 0.2, the README for the ./packages/bootstrap-vue-3 is slimmed down a lot. This will affect the README on npm once a 0.2.x is released. Should we duplicate it to make it look nice for npm, make it different, or just leave it the way it is?

Lastly, it should be noted that post 0.2, the README for the ./packages/bootstrap-vue-3 is slimmed down a lot. This will affect the README on npm once a 0.2.x is released. Should we duplicate it to make it look nice for npm, make it different, or just leave it the way it is?

Yes would be great

Lastly, it should be noted that post 0.2, the README for the ./packages/bootstrap-vue-3 is slimmed down a lot. This will affect the README on npm once a 0.2.x is released. Should we duplicate it to make it look nice for npm, make it different, or just leave it the way it is?

Yes would be great

Which one? 😆

I think it's fine the way it is. People can always click on github repo.

authors: VividLemon aceofwings mariusa


text:
Terminal names not displayed when shown as tabs after reloading

OS/Web Information

Web Browser: Chrome (90.0.4430.212 (Official Build) (x86_64)
Local OS: macOS 11.3.1
Remote OS: macOS 11.3.1
Remote Architecture: macOS 11.3.1
code-server --version: 3.10.2 387b12ef4ca404ffd39d84834e1f0776e9e3c005

Steps to Reproduce

Launch Chrome and open code-server URL
Open Terminal panel
Open few New Terminal
In terminal dropdown list, select Show tabs
Reload code-server URL

Expected
Terminal names should be displayed after realoding
Actual
Terminal names aren't displayed after realoding
Logs

[2021-05-24T11:20:29.702Z] info  code-server 3.10.2 387b12ef4ca404ffd39d84834e1f0776e9e3c005
[2021-05-24T11:20:29.703Z] info  Using user-data-dir ~/.local/share/code-server
[2021-05-24T11:20:29.715Z] info  Using config file ~/.config/code-server/config.yaml
[2021-05-24T11:20:29.715Z] info  HTTP server listening on http://127.0.0.1:8080
[2021-05-24T11:20:29.716Z] info    - Authentication is enabled
[2021-05-24T11:20:29.716Z] info      - Using password from ~/.config/code-server/config.yaml
[2021-05-24T11:20:29.716Z] info    - Not serving HTTPS
[2021-05-24T11:20:33.135Z] debug forking vs code...
[2021-05-24T11:20:33.483Z] debug setting up vs code...
[2021-05-24T11:20:33.486Z] debug vscode got message from code-server {"type":"init"}
[2021-05-24T11:20:34.397Z] debug vscode got message from code-server {"type":"socket"}
[2021-05-24T11:20:34.399Z] debug protocol Initiating handshake... {"token":"0413b0a7-be02-4648-9bf9-8035b28666db"}
[2021-05-24T11:20:34.414Z] debug protocol Handshake completed {"token":"0413b0a7-be02-4648-9bf9-8035b28666db"}
[2021-05-24T11:20:34.414Z] debug management Connecting... {"token":"0413b0a7-be02-4648-9bf9-8035b28666db"}
[2021-05-24T11:20:34.415Z] debug vscode 1 active management connection(s)
[2021-05-24T11:20:34.637Z] debug Making request {"uri":"https://api.github.com/repos/cdr/code-server/releases/latest"}
[2021-05-24T11:20:34.653Z] debug vscode got message from code-server {"type":"socket"}
[2021-05-24T11:20:34.653Z] debug protocol Initiating handshake... {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:20:34.701Z] debug got latest version {"latest":"3.10.2"}
[2021-05-24T11:20:34.701Z] debug comparing versions {"current":"3.10.2","latest":"3.10.2"}
[2021-05-24T11:20:34.792Z] debug protocol Handshake completed {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:20:34.792Z] debug exthost Connecting... {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:20:34.793Z] debug exthost Getting NLS configuration... {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:20:34.793Z] debug vscode 1 active exthost connection(s)
[2021-05-24T11:20:34.793Z] debug exthost Spawning extension host... {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:20:34.800Z] debug exthost Waiting for handshake... {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:20:35.392Z] debug exthost Handshake completed {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:20:35.392Z] debug exthost Sending socket {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}

# Reload

[2021-05-24T11:21:02.555Z] debug management Disposing... {"token":"0413b0a7-be02-4648-9bf9-8035b28666db"}
[2021-05-24T11:21:02.556Z] debug management Closed {"token":"0413b0a7-be02-4648-9bf9-8035b28666db"}
[2021-05-24T11:21:02.596Z] debug setting up vs code...
[2021-05-24T11:21:02.598Z] debug vscode got message from code-server {"type":"init"}
[2021-05-24T11:21:02.622Z] debug exthost Got disconnected message {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:21:02.622Z] debug exthost Disconnected {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:21:03.584Z] debug exthost Exited {"code":0,"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:21:03.584Z] debug exthost Disposing... {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:21:03.585Z] debug exthost Closed {"token":"b3ea6fde-b86c-44e6-8590-76fd23a7979e"}
[2021-05-24T11:21:03.614Z] debug vscode got message from code-server {"type":"socket"}
[2021-05-24T11:21:03.615Z] debug protocol Initiating handshake... {"token":"48c13a01-cc18-47ad-bc89-633dbf653fba"}
[2021-05-24T11:21:03.632Z] debug protocol Handshake completed {"token":"48c13a01-cc18-47ad-bc89-633dbf653fba"}
[2021-05-24T11:21:03.633Z] debug management Connecting... {"token":"48c13a01-cc18-47ad-bc89-633dbf653fba"}
[2021-05-24T11:21:03.633Z] debug vscode 1 active management connection(s)
[2021-05-24T11:21:04.010Z] debug got latest version {"latest":"3.10.2"}
[2021-05-24T11:21:04.011Z] debug comparing versions {"current":"3.10.2","latest":"3.10.2"}
[2021-05-24T11:21:04.023Z] debug vscode got message from code-server {"type":"socket"}
[2021-05-24T11:21:04.024Z] debug protocol Initiating handshake... {"token":"6d9a13b8-08b7-4b4c-8114-9bbd2304d2af"}
[2021-05-24T11:21:04.315Z] debug protocol Handshake completed {"token":"6d9a13b8-08b7-4b4c-8114-9bbd2304d2af"}
[2021-05-24T11:21:04.315Z] debug exthost Connecting... {"token":"6d9a13b8-08b7-4b4c-8114-9bbd2304d2af"}
[2021-05-24T11:21:04.316Z] debug exthost Getting NLS configuration... {"token":"6d9a13b8-08b7-4b4c-8114-9bbd2304d2af"}
[2021-05-24T11:21:04.316Z] debug vscode 1 active exthost connection(s)
[2021-05-24T11:21:04.316Z] debug exthost Spawning extension host... {"token":"6d9a13b8-08b7-4b4c-8114-9bbd2304d2af"}
[2021-05-24T11:21:04.323Z] debug exthost Waiting for handshake... {"token":"6d9a13b8-08b7-4b4c-8114-9bbd2304d2af"}
[2021-05-24T11:21:04.957Z] debug exthost Handshake completed {"token":"6d9a13b8-08b7-4b4c-8114-9bbd2304d2af"}
[2021-05-24T11:21:04.958Z] debug exthost Sending socket {"token":"6d9a13b8-08b7-4b4c-8114-9bbd2304d2af"}
[IPC Library: Pty Host]  INFO Persistent process "3": Replaying 4869 chars and 4 size events
[IPC Library: Pty Host]  INFO Persistent process "1": Replaying 4809 chars and 4 size events
[IPC Library: Pty Host]  INFO Persistent process "2": Replaying 4809 chars and 4 size events

Screenshot

Notes

This issue can be reproduced in VS Code: No

I think this might be a duplicate of https://github.com/cdr/code-server/issues/3340 although that one doesn't specifically mention tabs so I'll close this one and edit the other. Thank you for reporting!

authors: code-asher sestegra

repo: cdr/code-server


text:
Be able to adjust amount of minutes threshold to lower values than 15 minutes

As a Canadian citizen, could I build a personal build that will work with the official built ones, if I manually install my version ?
If so, is there a way for me to adjust the 15 minutes exposure threshold to 5 minutes ?

Thanks for the question @fredvb you won't be able to do a local build as the app requires entitlements which are only given to Public Health authorities.
As far as adjusting the threshold that's not currently possible.

A 5 minutes timer configuration may become more important with a more virulent strain of the virus and more stringent lockdown measures in red zones.

A 5 minutes timer configuration may become more important with a more virulent strain of the virus and more stringent lockdown measures in red zones.

authors: LeCanardQuoi fredvb timarney

repo: cds-snc/covid-alert-app


text:
Fastlane config for limited access

missing keystore.properties file

Currently need:
STOPCOVID_UPLOAD_STORE_FILE=

Fixed in #599 and #603

authors: dsamojlenko timarney

repo: cds-snc/covid-shield-mobile


text:
Go-live date change 📅

This PR:

changes the date range to August 1st - September 20th (ie 4 weeks from July 4th, and then 8 weeks of Wednesdays and Thursdays)
Updates our date format to display longer months and days

Thu, Sep 6, 2018 -> Thursday, September 6, 2018
jeu. 6 sept. 2018 -> jeudi 6 septembre 2018

updates page copy where we refer to dates
updates our "Go Back" links to say "Go back"
updates our hardcoded tests

before
after

LGTM but I have one small thing - I poked around when I was making changes and I couldn't find a way to remove the comma , after the DAYOFWEEK. Can we remove that easily? Do not worry about it if not, it's not critical or even high importance. Just a nice to have.

@zakkain, yeah, it's possible but let's wait until @timarney's PR is in too before we standardize our date formats.

repo: cds-snc/ircc-rescheduler


text:
Fix the servicePort in the Ingress so that it matches the pdns Service

Fixes https://github.com/cdwv/powerdns-helm/issues/3

Thank you @rosskusler !

authors: andrzejwp rosskusler

repo: cdwv/powerdns-helm


text:
已经添加到-keep的类依旧 NoClassDefFoundError

机器系统:4.4
我想在启动页面用multidex加载其他dex ,但是在application中就报错了

你先检查下生成的 maindexlist.txt是否有你的类。
如果multidex不在application中加载，在multidex加载前的任何其他dex中的类都不能用。
你可能是keep的类中还有其他依赖的类未keep

我开启了
-split .
会不会有什么影响呢

-split . 是个比较危险的选项，你无法实时保证没有遗漏。这个需要你自行调试了，插件只能保证maindexlist中类存在，但不保证依赖链和mutildex加载时机问题。
你的问题可能是连 android.support.multidex.** 都没keep，或者依赖链出问题了，不是只有keep一个类就够了

repo: ceabie/DexKnifePlugin


text:
🛑 tanecni-divadlo.cz is down

In 52e750d, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 6591f48.

repo: cebreus/upptime


text:
🛑 tanecni-divadlo.cz is down

In 70ce7bc, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in b86791c.


text:
🛑 tanecni-divadlo.cz is down

In 3ac1b93, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 6e4b26e.


text:
🛑 Bali 2017 is down

In d004751, Bali 2017 ($SITE_BALI) was down:

HTTP code: 502
Response time: 22864 ms

Resolved: Bali 2017 is back up in f311b17 after 3 minutes.


text:
🛑 tanecni-divadlo.cz is down

In eec1397, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in b89f100.


text:
🛑 CDN is down

In e99878d, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 502
Response time: 657 ms

Resolved: CDN is back up in b21f787.

repo: ceccun/status


text:
Use nanoids as Eids for schema-based hierarchy generation

Issue #, if available: #86
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Correct.

Approved, but I imagine you'll have to fix the CI break before merging.

authors: khieta shaobo-he-aws

repo: cedar-policy/cedar-spec


text:
api::ValidationResult implements error but diagnostics::ValidationResult doesn't

Describe the improvement you'd like to request
api::ValidationResult is a wrapper for diagnostics::ValidationResult that implements Diagnostic and Error. However, this makes things awkward internally since diagnostics::ValidationResult doesn't have an error implementation.
I propose we move the implementation of error and diagnostic to the inner diagnostics::ValidationResult.
Describe alternatives you've considered
No response
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this internal improvement
[ ] ⚠ This feature might incur a breaking change

Make sense. IIRC, there were some issue with the wrapper types for the public API that made this the convenient way to do things. You can add it to the internal with a bit of duplicate code. Feel free to refactor if you see a nicer way to do it.

authors: john-h-kastner-aws oflatt

repo: cedar-policy/cedar


text:
Fixed tables getting metatables twice

Also added a demo of wrapping native JS classes
@ceifa Sorry for the bug, though hopefully this now resolves the original that had a memory leak and my one :)

Do this solves the problem of #25?
I was trying to do a different thing on my own in #27

Yep, solves #25
Hopefully the test shows how to accomplish with the current code what you were doing in #27

@timstableford Tested it here and now I could understand the idea. But maybe it should be cool to work out of the box, without needing to wrap the object.
I made it in #27, but I'm not sure if it's okay, can you take a look?

authors: ceifa timstableford

repo: ceifa/wasmoon


text:
Backport relevant changes to the v0.34.x-celestia branch

tendermint v0.34.20 will be released soon, and since the current plan is to downgrade along with the cosmos-sdk, then we will have to backport all of the changes we've introduced since we've upgraded to v0.35 to v0.34

we still need to do a more in depth comparison with the changes between v0.34.x-celestia and v0.35.x-celestia, but at first glance the commits that were made on v0.35 that we will want in v0.34

Fix links for readme ADR 7232099b81c79f493afa036db7b4250fef52daca
Only check for celestia dependabot PRs c860375d6d2e5dff7f8e2cddf16094af7f5a9cd2
Fix image file extension de7ef42c905be9f8bb698a2efa63eef8eff64ba2
Update career links 8cad09dbebf7e82cb2e7ed3b902348e9c6d29e90
Prove txs that span more than two shares 2f46519dd9ecd1f0693c02c2adbdd002097fe245
Refactor min dah 615ca799edd785766b0f99fbb12e7ff69637fdb7
Double check that the mempool functionality is working as expected b2478c24e69464cc0c7b75b66caa860305826c18
ADR 008 4f1c343bdee596fd3a6de7abf01c3bb3629de12a

closed with #802

repo: celestiaorg/celestia-core


text:
header: Implement ExtendedHeaderService

Implement an ExtendedHeaderService in package header:

[x] type ExtendedHeader
[x] Constructor function for ExtendedHeaderService
[x] Start
[x] Stop
[x] #172
[x] ExtendedHeaderVerification -- triggers a Sampling process for the given header (light node only)
[x] #164
[x] #150
[x] #202

Closing, as all components of HeaderService have been completed (and we will add more in the next testnet iteration) 🚀

repo: celestiaorg/celestia-node


text:
service/share, ipld: adds ability to retrieve shares by namespace ID

This PR implements the ability to retrieve shares by namespace ID via two helper methods in the ipld package as well as a broader RetrieveShares function in service/share package.
One thing to note:
PutData in ipld/write.go prepends the namespaceID twice, so in several tests, it's necessary to check the returnedShare[8:] against the expectedShare.
TODO:

[x] full test for RetrieveShares
[x] clean up code / address TODOs
[x] lint / make sure good test coverage
[x] check on mod to make sure no accidents occurred

The tests if failing due to #173. To resolve this here we can either:

Rerun until success
Merge #171 first, which fixes the problem inside.

@renaynay, WDYT?

@renaynay, rebase on master and tests will go green

1.16 tests running for too long, ***, seems like TestSubscriber still hangs

@renaynay, add pls context.WithTimeout(time.Second * 10) to TestSubscriber. This way we ensure that tests won't run longer than 10*seconds if it hangs.

Rerun helped and we can merge this, though in master, rarely hanging still might be the case.

Conflicting with default branch @renaynay

authors: Wondertan adlerjohn renaynay


text:
fix: removing quic transports until GSO bug is fixed

Related: https://github.com/libp2p/go-libp2p/issues/2591

https://github.com/celestiaorg/celestia-node/pull/2837


text:
changed user UserAgent name

Description
This pull request introduces modifications to the user agent/network name.
Issues
fixes: #2932

@ATREAY, This works and solves the issue. Let's also fix #2908 in this PR. You can get it from nodebuilder/node.GetBuildInfo

Certainly, @Wondertan.
Since I'm new to the repo, could you please clarify whether the system should return the semantic version or the system version?

@ATREAY, semantic. System version should stay private

Hey @Wondertan, I included the network version. Could you confirm if this meets the requirements mentioned in the issue?

Hey @Wondertan, I have formatted the user agent name. Could you please check and confirm if it is correct when you have a moment?

Hey @Wondertan, Since params.Net contains comprehensive information about the network name and its alias, I believe this should suffice.

@ATREAY, No. It must be in the following format celestia-node/Arabica-10/v0.12/abc2das, currently it will produce Arabica-10-node/v0.12/abc2das. Again, celestia-node should stay constant.
Also, I made a typo initially, and it should be 7 first chars of commit instead of 8.
Please write a unit test that ensures we follow the requested UserAgent form

Hey @Wondertan
I want to inform you that I lack familiarity with unit testing techniques and creating unit tests, as I have not worked on them previously. If feasible, could you please assign this task to someone with experience in unit testing? This would help prevent unnecessary errors that may arise if I were to undertake this task.
I apologize for any inconvenience this may cause.

@ATREAY i can help with getting some unit tests in place so we can get this merged

@ATREAY i created some tests and refactored code here a7c7b16
have a look, if you like and agree i can push the changes to this branch and we can see about getting this merged

I think it's good. What do you think, @Wondertan? Is it okay?

@Wondertan check this with some expanded tests, if you like we can replace this PR with it and get over the line: https://github.com/ATREAY/celestia-node/pull/1

@ramin, lets use your tested version! We can open your PR directly to node

replaced by https://github.com/celestiaorg/celestia-node/pull/3379

authors: ATREAY Wondertan ramin


text:
chore!: adjust stopped status actions for the update image and others

Closes #561
Note: This PR removes the UpgradeImage functions, instead, the user has to stop their instance, configure whatever they want and start it again.

Summary by CodeRabbit
Release Notes

New Features

Introduced flexibility in state management, allowing operations like setting images, adding ports, and adjusting resources even when instances are in a 'Stopped' state.
Enhanced error handling with clearer feedback for state restrictions when adding hosts to a proxy.

Bug Fixes

Improved state checks for various methods, ensuring proper functionality across different instance states.

Documentation

Updated comments and documentation to reflect changes in state conditions for various functionalities.

A breaking change should break tests. If not then that is a clear gap in our testing, so we should be adding a test for the new use case.

There is no  dedicated E2E test for the upgrade image that's why it does not brake any. There is one use case in the app e2e test which we have to update the sequence. i.e. Stop the instance first, upgrade the image, then Start the instance again.

repo: celestiaorg/knuu


text:
Migrate remaining unit tests to foundry

Follow-on from:

https://github.com/celo-org/celo-monorepo/issues/10319

### Tasks
- [ ] https://github.com/celo-org/celo-monorepo/issues/10802
- [ ] https://github.com/celo-org/celo-monorepo/issues/10801

Currently working on FeeHandlerSeller tests here:

https://github.com/celo-org/celo-monorepo/pull/11155

Marked this PR as ready for review:

https://github.com/celo-org/celo-monorepo/pull/11155

Working on UniswapFeeHandlerSeller tests here:

https://github.com/celo-org/celo-monorepo/pull/11171

Marked this PR as ready for review:

https://github.com/celo-org/celo-monorepo/pull/11171

Done ✅ Took less time than expected 👍

@arthurgousset can you please update "Elapsed + remaining (hours)" and "Time elapsed (hours)"?

authors: arthurgousset lvpeschke

repo: celo-org/celo-monorepo


text:
Isolated integration tests

Don't mind me, just trying to get the integration tests working according to https://github.com/celsworth/lxp-bridge/pull/147#issuecomment-1437420017
With the isolated approach, they're currently taking ~45 seconds to run locally, factoring out the cargo build part.

❤
Haven't forgotten about the other PRs, just starting a new job so focused elsewhere at the moment :) Will take a look when I can. This looks awesome though, getting these running in CI was a good next step before expanding them to cover more cases, nice job :)

No worries; I'm just fiddling as I have time :sweat_smile:

It's green \o/

authors: celsworth lupine

repo: celsworth/lxp-bridge


text:
Made a copy of the 01 file and modified to print the name afterit rea…

…ds in an input

You were supposed to hardcode your name in the script.

authors: cengique d-sales

license: Unlicense


text:
No such file or directory: 'data/bio-forget-corpus.jsonl

I extracted all the contents of the data files from the Google Drive mirrors. bio_remove_dataset.jsonl was extracted from the "Bio Forget Corpora" form link. Should bio_remove_dataset.jsonl be namedbio-forget-corpus.jsonl?

yes it should

Thanks for raising the issue we're currently working on a fix and it should be posted soon.

Great to hear it! Another thing is that both files seem like different formats.

authors: Kyle1668 nathanneuro steven-basart

repo: centerforaisafety/wmdp


text:
Client logos added to the landing page (#21)

Let's continue #21 here

Hidden on mobile for now in 2552fc511d0c784f8bfd2527635ec0220b130ff3 and released


text:
remove inline sourcemap from dist Javascript

Hi,
I'd like to request that the inline sourceMap present in the packaged javascript is removed from the Javascript file and externalised.

It breaks my own bundling and minification as there's a sourceMap blob in the middle of other scripts.
I have to hack the build script to ensure it always last to be concatenated.
Even though I have my own sourceMap, this is the one that Chrome references and I can't see my own source references.
it's 160% of the size of the source itself, and is only really useful in this format for agGrid development itself.

Cheers
angularGrid is excellent by the way!

makes sense. will stick this onto my list. thanks.

since moving to typescript, i've reviewed this. the maps are not included when i do releases now.

authors: ceolter robshep

repo: ceolter/angular-grid


text:
purge-cluster.yml - colocated scenario fails because of no lvm_volumes var definition

purge-cluster.yml breaks again due in osd_scenario: collocated because lvm_volumes var is undefined, but it should not have to be defined in this scenario.
TASK [remove osd logical volumes] *******************************************************************************************************************************************
fatal: [192.168.121.64]: FAILED! => {"failed": true, "msg": "'lvm_volumes' is undefined"}
fatal: [192.168.121.112]: FAILED! => {"failed": true, "msg": "'lvm_volumes' is undefined"}
fatal: [192.168.121.158]: FAILED! => {"failed": true, "msg": "'lvm_volumes' is undefined"}

Surprisingly the when clause does not protect ansible from evaluating the variable lvm_volumes.  Is this another ansible bug?  Seems like it should evaluate the when clause first, then the with_items clause.
But in the meantime, we need to define lvm_volumes to the empty list in this case.  I worked around by setting lvm_volumes: []  but this is ugly.

@bengland2 what version of ansible and ceph-ansible are you using? I agree that it does kind of sound like an ansible bug. I just ran a test using ansible 2.3.1 and ceph-ansible@master and did not reproduce this issue though.
Here's the purge cluster test that passed: https://2.jenkins.ceph.com/view/ceph-ansible/job/ceph-ansible-scenario/16/console

I'm running ansible-2.3.2.0-1.fc26.noarch.   I noticed your Jenkins job Ceph VMs ran on Xenial not Centos,   and my laptop, where ansible runs, is Fedora 26 not Xenial.  But I'm using vagrant just like you are.  I have no idea why my test failed and yours passed.  Here's the simplest reproducer - no roles, no includes, just one var, no dependencies at all on other files.
---
- name: trivial play illustrating bug
  hosts: localhost
  vars:
          osd_scenario: collocated
  tasks:
          - name: task illustrating bug
            when: osd_scenario != "lvm"
            with_items: "{{ lvm_volumes }}"
            shell: "echo hi there"

and its output:
[bengland@bene-laptop ceph-ansible]$ pushd /tmp
/tmp ~/vagrant/ceph-ansible ~/vagrant/libvirt
[bengland@bene-laptop tmp]$ ansible-playbook -u root -i ../libvirt/host.inv t.yml
 [WARNING]: Host file not found: ../libvirt/host.inv

 [WARNING]: provided hosts list is empty, only localhost is available

PLAY [trivial play illustrating bug] ****************************************************************************************************************************************

TASK [Gathering Facts] ******************************************************************************************************************************************************
ok: [localhost]

TASK [task illustrating bug] ************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"failed": true, "msg": "'lvm_volumes' is undefined"}
        to retry, use: --limit @/tmp/t.retry

PLAY RECAP ******************************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=1

I was using ansible-2.3.2.0-1.fc26.noarch.  I looked at  your ci job log and it does not show the problem, but I can't tell if lvm_volumes was somehow defined in there.  I reproduce the problem using this simple playbook:
---
- name: trivial play illustrating bug
  hosts: localhost
  vars:
          osd_scenario: collocated
  tasks:
          - name: task illustrating bug
            when: osd_scenario != "lvm"
            with_items: "{{ lvm_volumes | default([]) }}"
            shell: "echo hi there"

and get this result:
[bengland@bene-laptop ceph-ansible]$ ansible-playbook -u root -i ../libvirt/host.inv t.yml

PLAY [trivial play illustrating bug] ****************************************************************************************************************************************

TASK [Gathering Facts] ******************************************************************************************************************************************************
ok: [localhost]

TASK [task illustrating bug] ************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"failed": true, "msg": "'lvm_volumes' is undefined"}

PLAY RECAP ******************************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=1

But if I replace when clause with this:
            with_items: "{{ lvm_volumes | default([]) }}"

Then it works fine.  I read in ansible issue 17484 that this is not a bug.  So I think this is the correct fix.

Sure that works for me, instead of inserting Jinja2 default filter
everywhere we can do it one time up front.
Could we add this to roles/ceph-defaults/tasks/facts.yml and put
roles:

ceph-defaults

in the OSD play within purge-cluster.yml and any other playbook that deals
with OSDs, that way we don't have to add this kind of defaulting logic for
OSD vars to every playbook.   I've tried this in the past and it worked,
never got it upstream though.  I think this was Seb's comment on a PR that
I wrote.
On Wed, Sep 13, 2017 at 5:18 PM, Andrew Schoen notifications@github.com
wrote:

I think it might be best to do something like this at the top of the
playbook, like we used to do for devices.

set_fact:
lvm_volumes: []
when: lvm_volumes is not defined

I'm still a bit unsure why I can't reproduce though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ceph/ceph-ansible/issues/1887#issuecomment-329299982,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABozcxwv-TYhKpl_1bKSxcmDRjLZGyIAks5siEa_gaJpZM4PWK0k
.

@bengland2 actually, that's exactly why the ceph-defaults role was created. That's a much better solution than defaulting these values manually in the playbook, and it'll be updated automatically for us as new config options are added.

@andrewschoen unfortunately that wasn't good enough - I then hit a failure because osd_scenario var was undefined!  This is not fixable in ceph-defaults - have to pull in user-specified value of this variable.  This seemed to work well, found in examples for include_vars clause in ansible docs.  Does it make sense to you?
diff --git a/infrastructure-playbooks/purge-cluster.yml b/infrastructure-playbooks/purge-cluster.yml
index df82a358..f386c4d8 100644
--- a/infrastructure-playbooks/purge-cluster.yml
+++ b/infrastructure-playbooks/purge-cluster.yml
@@ -194,6 +194,12 @@

   tasks:

+  - name: pull in user-specified OSD vars
+    include_vars: "{{ item }}"
+    with_first_found:
+      - ../group_vars/osds.yml
+      - ../group_vars/osds
+
   - name: get osd numbers
     shell: "if [ -d /var/lib/ceph/osd ] ; then ls /var/lib/ceph/osd | sed 's/.*-//' ; fi"
     register: osd_ids

But I wasn't satisfied, this is a per-playbook change, wanted a way to fix it for everyone.  So I tried this:
diff --git a/roles/ceph-defaults/tasks/main.yml b/roles/ceph-defaults/tasks/main.yml
index 25887efa..3a94a425 100644
--- a/roles/ceph-defaults/tasks/main.yml
+++ b/roles/ceph-defaults/tasks/main.yml
@@ -1,3 +1,10 @@
 ---
+
+- name: pull in user-specified OSD vars
+  include_vars: "{{ item }}"
+  with_first_found:
+      - ../group_vars/osds.yml
+      - ../group_vars/osds
+
 - include: facts.yml
 - include: check_socket.yml

And that seemed to work as well.  So any playbook that includes ceph-defaults role will get this, right?    Will try to come up with PR but if I don't quickly enough, at least you know how I would try to fix it.

@bengland2 we really don't want to be including group_vars/ like that. Ansible should pull that in automatically if you have group_vars/ relative to your inventory or the playbook being run.
I'm assuming you had osd_scenario defined in your config somewhere, where was it located? Where did you include the ceph-defaults role? I wouldn't think that including a role would override config defined in group_vars/.

@andrewschoen , yes this is very counter-intuitive that you have to do this.  My osd_scenario var was defined in ceph-ansible/group_vars/osds.yml.  But it didn't get pulled in!   I think the reason is that I don't include the ceph-osds role ever in purge-cluster.yml - doing so would trigger OSD creation which we don't want.  I just want OSD-related vars, nothing else.   I do pull in ceph-defaults as described above because that role takes no action, it just defines facts.  I don't have to do this with ceph-ansible/group_vars/all.yml, that seems to get pulled in automatically just fine.  So if we didn't have a separate osds.yml, then this would not be necessary.  Is this analysis correct?  Thx for helping me understand this better.
I retested and found that using relative pathname ../group_vars/osds.yml was insufficient, this doesn't work for site.yml because it's not in same directory as purge-cluster.yml.  So I changed to:
+
+- name: pull in user-specified OSD vars
+  include_vars: "{{ item }}"
+  with_first_found:
+      - group_vars/osds.yml
+      - group_vars/osds
+

And do this:
cd ceph-ansible/infrastructure-playbooks
ln -s ../group_vars .

it works.  We could do a similar thing for infrastructure_playbooks/untested_by_ci/   and these softlinks could be pre-populated in git repo, yes?

@bengland2 you can also just copy purge-cluster.yml to the root of ceph-ansible and it should use the group_vars/ in the root of ceph-ansible then if that's where you like to keep them. You are right that if there is no hosts: osds anywhere in the playbook then config defined in group_vars/osds.yml will not be used.
Typically I like to keep a group_vars/ directory relative to my inventory file so I know my config will always be used. This is how we manage all of our CI testing scenarios.
We don't want to use include_vars at all in these playbooks because doing so can override config options set elsewhere as include_vars in a playbook has very high variable precedence.

@andrewschoen, I had osd_scenario properly defined in ceph-ansible/group_vars/osds.yml  .    there was a hosts: osds or equivalent in that play within the OSD play in the purge-cluster.yml playbook, but gather_facts: no was used, which apparently inhibited reading group_vars/osds.yml .  When I removed include_vars statement above and also dropped gather_facts (which defaults to true) in the OSD play, it worked! so I think this is the best solution now, do you agree?
To see this, use this example playbook:
---
- name: see if osd_scenario is defined

 roles:
 - ceph-defaults
 hosts:
   - osds

 gather_facts: false

 become: true

 tasks:

 - name: use osd_scenario
   shell: "echo {{ osd_scenario }}"

This will fail but if you remove the gather_facts statement, it will work.

@bengland2 actually, using ceph-defaults here won't work because the osd configuration does not exist in ceph-defaults, it's only in ceph-osd.
Could you try this PR and see if it fixes things for you? https://github.com/ceph/ceph-ansible/pull/1916

@andrewschoen I think this fixes it for purge-cluster.yml.  if we could do this kind of fix in ceph-defaults role so that all playbooks could inherit it but maybe later.

fixed by https://github.com/ceph/ceph-ansible/pull/1916

repo: ceph/ceph-ansible


text:
ceph-ansible-mimic broken

See details http://tracker.ceph.com/issues/24926

@vasukulkarni  ^ ?

@guits trying https://github.com/ceph/ceph/pull/23122

@yuriw you are still using ansible 2.3 :
2018-07-19T02:18:02.357 INFO:teuthology.orchestra.run.ovh055:Running: 'cd ~/ceph-ansible ; virtualenv --system-site-packages venv ; source venv/bin/activate ; pip install --upgrade pip ; pip install setuptools>=11.3 notario>=0.0.13 ansible==2.3.2 ; ANSIBLE_STDOUT_CALLBACK=debug ansible-playbook -vv -i inven.yml site.yml'

@yuriw I still see 3 failing job. I'm not sure the reason since at the moment I can't download the logs

authors: guits yuriw


text:
tests: provide ways to change the install method

This provides ways that allow you to change the install method when running the testing scenarios. For example, if you wanted to test the ansible2.2-journal_collocation scenario against latest master build from shaman you'd do the following:
CEPH_DEV=true CEPH_STABLE=false CEPH_DEV_BRANCH=master tox -rve ansible2.2-journal_collocation

jenkins test ansible2.2-xenial_cluster

jenkins test this please

jenkins test this please

jenkins test ansible2.2-dmcrypt_journal

jenkins test ansible2.2-update_dmcrypt

jenkins test ansible2.2-update_dmcrypt

jenkins test ansible2.2-purge_dmcrypt

jenkins test ansible2.2-purge_dmcrypt


text:
rgw: add multi-instances support when deploying multisite

This commit adds the multi-instances when deploying rgw multisite
Signed-off-by: Guillaume Abrioux gabrioux@redhat.com

jenkins test centos-container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

@alimaredia FYI

jenkins test centos-non_container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

jenkins test centos-container-rgw_multisite

jenkins test centos-non_container-rgw_multisite

authors: dsavineau guits


text:
shrink_osd: add missing default value

This commit adds a missing | default(False) needed to avoid error like
following :
fatal: [ceph01]: FAILED! =>
  msg: |-
    The conditional check 'ceph_osd_data_json[item.2]['encrypted'] | bool' failed. The error was: error while evaluating conditional (ceph_osd_data_json[item.2]['encrypted'] | bool): 'dict object' has no attribute 'encrypted'

Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1862416
Signed-off-by: Guillaume Abrioux gabrioux@redhat.com

jenkins test centos-non_container-shrink_osd-single

jenkins test centos-non_container-shrink_osd-multiple

jenkins test centos-non_container-shrink_osds-multiple

jenkins test centos-non_container-shrink_osd_multiple

jenkins test centos-non_container-shrink_osd_single

jenkins test centos-container-shrink_osd_multiple

jenkins test centos-container-shrink_osd_single

closing in favor of #5599


text:
ci: wait before starting ceph-osd

This is another attempt to fix #423.
Signed-off-by: Sven Anderson sven@redhat.com

Checklist

[ ] Added tests for features and functional changes
[ ] Public functions and types are documented
[ ] Standard formatting is applied to Go code

It's worth a try. Did you remove --foreground because you don't think it does anything?

Yeah, I didn't think it makes a difference from the beginning, because it is described as preventing the process to start in the background, which this variant of the command doesn't do anyways. But I wanted to try to be sure.

repo: ceph/go-ceph