text:
Added usage information

import and register example for react
fully functional example for react and typescript

Currently it's very difficult to get things working if you're a newcomer. This change is trying to improve that.
As I'm using react + typescript I could only add examples for this environment. Hopefully more examples will follow.

It is already documented here how to integrate the annotation plugin within chart.js.
This information is for the zoom, annotation, deferred and datalabels plugin in the same place as it is within chart.js itself.
Also I don't think that different frameworks should all be documented. Since they all fall under the category of bundlers. Only when there is a tool that does it totally different should it be added in my oppinion

@stockiNail as I described in my first comment do we want this, I have the feeling that current way of documentation is better. Since if we start going this route you could argue you need at least 3 react samples (1 functional component, 1 class and 1 with create element). While all the frameworks are basically the same with importing and that is well documented on the integration page.

as I described in my first comment do we want this, I have the feeling that current way of documentation is better. Since if we start going this route you could argue you need at least 3 react samples (1 functional component, 1 class and 1 with create element). While all the frameworks are basically the same with importing and that is well documented on the integration page.

I have applied the review anyway!
But I agree with you. The risk is to have samples for every JS frameworks.

Closing this since the neccesarry information can be found in the integration page.
Way of importing for frameworks is at the moment to my knowledge all the same and falls under the bundler category.
If there is a framework that works in a different way we can add it.
But replicating the bunder import for all the used frameworks is something I don't see as usefull and only makes the docs too full so people will skip even more through it.

It is already documented here how to integrate the annotation plugin within chart.js.

This might indeed be already enough. Perhaps I'm viewing the website in a wrong way, but I feel this information is quite hidden (the tiny link on the bottom right). I would expect that information to be within the getting started section.
What would you think about merging "getting started", "integration" and "usage" into one bigger "getting started" page.

authors: DarkTrick LeeLenaleee stockiNail

repo: chartjs/chartjs-plugin-annotation


text:
Bug: oracle database cannot see the view

Chat2DB Version
Pro 1.1.5
Describe the bug

现在可以看到了

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Incomplete conf.yml description

A description of the problem
There is no info about:

default values of props
required props

# conf.yml:
# ...
cheatpaths:
  - name: community                   # a name for the cheatpath
    path: ~/documents/cheat/community # the path's location on the filesystem
    tags: [ community ]               # these tags will be applied to all sheets on the path
    readonly: true                    # if true, `cheat` will not create new cheatsheets here

  - name: personal
    path: ~/documents/cheat/personal  # this is a separate directory and repository than above
    tags: [ personal ]
    readonly: false                   # new sheets may be written here
# ...

I assume that:

required props are: name, path
readonly default is false

Am I right?

Thanks for reporting this, @EmilySeville7cfg. There was in fact important information missing here.
I've improved the configuration documentation in the 4.3.2 release:
https://github.com/cheat/cheat/releases/tag/4.3.2
I'm thus going to close this as resolved.

repo: cheat/cheat

license: MIT


text:
[CHEC-826] WYSIWYG Component

WYSIWYG component for the UI Library. Note, the package seems to be having an issue with Prosemirror as documented here.  I have added a workaround for the time being.
We didn't have a style for the dark mode so I used my best judgement @blazepollard. Let me know if you'd like this adjusted.
Light Mode:

Dark Mode:

I played around with this a bit locally, and I found some issues.
I fixed the placeholders, and the value binding (so it emits change events).
There are a few other issues that I've spotted:

The auto-resize needs to kick in much earlier, as you end up typing under the button bar.
The fade effect under the label that the textareas have isn't working, so when you scroll you can't read the label
There's no blockquote style

TODO list:
[] Blockquote styles
[] Label underlay
[] Make the size configurable
[x] Fix the button bar overlap (remove position: absolute)
[] Placeholders

Ok. Squashed and rebased the whole thing and LGTM.

Nice spotting. I'll raise an issue for those things as a bug, but I don't think any of them block us going ahead with the add-product screen. Thanks!

source: gharchive/pull-request

authors: ScopeyNZ kvisca

repo: chec/ui-library


text:
Switching between list shortcuts doesn't update the displayed list contents

Describe the bug
When switching from one list shortcut to another, the title in the main view changes to reflect the new list, but the displayed posts remain the same.
Tested on phanpy.social (27a999f)
To Reproduce
Steps to reproduce the behavior:

Go to Shortcut Settings and choose either Floating button or Tab/Menu bar. Add at least two lists with different contents.
Go to the home timeline. Use the shortcut button or the tab bar to select the first list. The correct contents will be shown.
Use the shortcut button or tab bar to select the second list.
The title changes to reflect the second list, but the displayed posts remain the same.

Expected behavior
The posts from the second list should be shown.
One workaround is to switch to home view, then back to the second list.
Desktop:

OS: Windows 11
Browser: Firefox
Version: 113.0

Looks like this was fixed in a recent update. Thank you!

repo: cheeaun/phanpy


text:
Non apt based systems attempting to install apt-transport-https

Commit 818ae9f added install of apt-transport-https with no guard.  This cookbooks default recipe is included by many other cookbooks and this breaks the chef run when pulling in version 2.9.1 of this cookbook.

Hello!
I added a guard to the package resource in v2.9.2
However, I'm not entirely sure this is a bug....  The apt cookbook shouldn't be applied to non-apt based systems. Is the cookbook that depends on this a community cookbook? or internal. I'd like to fix this upstream.
-s

This is my 'wrapper' cookbook pulling in dependencies.  I only run Centos at the moment so am not calling this myself.  I've just checked through my Berksfile.lock to see where else the apt dependency is but going through those I can't see where the inclusion of the apt::default recipe is being called.  Will update further if I track it down

The entire default  recipe has a guard around on master right now.  That change will be shipping in 3.0. We've also added testing to ensure that RHEL 7 doesn't get any changes when the default recipe is applied.

authors: someara tas50 trilitheus

repo: chef-cookbooks/apt

license_source: bigquery


text:
Fix to allow creation of a RAID on HVM instances

This fixes the issue described here:
https://github.com/opscode-cookbooks/aws/issues/80
There's already a similar pull request, but this one allows the user to specify which method they'd like to use.

This still does not work. The aws cookbook is severly broken.

Whatever happened to this PR? Anything I can do to help it along? HVM is the 'new and shiny.'

At this point in time I'm going to close this PR out. ebs_raid had a time and place and for a set of people it worked great. Unfortunately the implementation of the resource is fairly limited in the platforms it supports and more importantly the instances it supports. Even if we fixed all the implementation issues with the provider it still doesn't belong in this cookbook as it's not a core AWS resources.
For those needing higher IOPS I'd highly recommend just doing this with SSD EBS volumes. You'll avoid a lot of work and you won't impact the reliability of your systems

authors: aub howdoicomputer ponyfleisch tas50

repo: chef-cookbooks/aws


text:
actually wire up the resources + providers

nothing was happening with the files
Signed-off-by: Lamont Granquist lamont@scriptkiddie.org

addresses half of #122

good enough for now


text:
Use the latest cpanm

This is 4 years newer. It has a TON of bug fixes and hopefully it works
with the new perl in Fedora 27.
Signed-off-by: Tim Smith tsmith@chef.io

Still broken on Fedora 27, but we should still be using this so I'm going to merge away

repo: chef-cookbooks/perl


text:
Silence deprecation warnings about ChefSpec.define_matcher

[DEPRECATION] `ChefSpec::Runner.define_runner_method' is deprecated. It is being used in the remote_install resource matcher. Please use `ChefSpec.define_matcher' instead. (called from spec/recipes/bash_spec.rb:4:in `block (2 levels) in <top (required)>')

:+1:

authors: curiositycasualty schisamo


text:
Move vsphere vm find to use container view

Use the container view api in vsphere to retrieve only the info we need
about the VMs so we can search more quickly.
This introduces a breaking change in that the folder is no longer
default. You need to use --short-path to get the folder name.

👍 Looks good, i like the UX change, it seems very reasonable.

authors: jjasghar swalberg

repo: chef-partners/knife-vsphere


text:
Adding IAM Actions doc

Signed-off-by: Mary Jinglewski mjinglewski@chef.io
:nut_and_bolt: Description: What code changed, and why?
To meet a documentation need for support and customers, we're adding a chart of IAM Actions, their end points, and their associated UI page to the Chef Automate docs site.
Related Resources
https://github.com/chef/release-engineering/issues/1064
:+1: Definition of Done
PR should be done when the details of this current chart are filled out as much as possible. @mjingle still needs to do a second run-through.
:athletic_shoe: How to Build and Test the Change
To view the docs change, pull in this PR and follow the instructions for make serve.
:white_check_mark: Checklist

[x] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[x] Docs added/updated?
[x] All commits have been signed-off for the Developer Certification of Origin.

see rel-eng #1064

authors: kagarmoe mjingle

repo: chef/automate


text:
automate-chef-io: remove stale CLI doc data files

The proper fix would be #3403, but it seems some data files aren't rebuilt.
Figuring out why that is would be interesting, but this fixes the issue
at hand.
Re-running env CHEF_DEV_ENVIRONMENT=false make docs in components/automate-cli (in the studio) won't rebuild those files.

Wrong thing. Right thing: #3403.


text:
[openstack]  missuse of  OS key_name attribute to search for r usessh key under .chef/keys or ~/.ssh

boostrap_option => {
  :key_name => '<openstack_key_id>',
}

You should not expect that user has the key stored under .chef/keys or ~/.ssh under the same name as key_name in openstack. We should use ssh-agent or provide an option to specify ssh_key_path.
See the example as kitchen-openstack does: https://github.com/test-kitchen/kitchen-openstack

:+1:

authors: bdangit epcim

repo: chef/chef-provisioning-fog


text:
Fix empty SSH username in ssh_gateway parameter

Signed-off-by: Baurzhan Konurbayev baurzhan_konurbayev@epam.com

Dear Chef guys,
When I am setting ssh_gateway for machine resource using chef-provisioning-fog
[:machine_options][:ssh_gateway] = 'USER@HOST'
Afterwards chef-provisioning's method 'gateway' receives ssh_gateway without USER right here:
gw_user, gw_host = options[:ssh_gateway].split('@')
Could you, please, consider this PR?
Thank you in advance!

I'll release this soon too. Sorry for the delay.

authors: baurzhan-konurbayev jjasghar


text:
Upgrade Postgres 9.2 to 9.6

I looks like the old machinery made for going from 9.1 to 9.2 still works just fine! 🎉
Pending:

[x] automatic upgrade tests (qa-chef-server-cluster)
[x] check tunables one-by-one to see if any other ones are gone, clarify release notes
[x] figure out an edge case or bug with the sentinel file creation
[x] cleanup 9.2 stuff

I thought there was a problem when, for whatever reason, the upgrade process would fail; I think I saw a situation where we'd still get the sentinel file. However, I've tried reproducing this and couldn't (recorded a video to convince myself).

want to give this another round of qa-chef-server-cluster tests, then I'll remove the [hold]. Reviews would be great, though 😀

🏓 @chef/chef-server-maintainers

@marcparadise I've checked off all the things from my list now ✔
Well, a missing bit is checking the deleted old data dir in upgrade tests. But if I find the right place for that test, it'll be in qa-chef-server-cluster anyways. So, could you throw some 👀 at those changes, please? I've intentionally not messed with the history yet, I'll squash and drop before merge.

This looks good to me with the assumption that the omnibus/omnibus-software changes on your branches are merged upstream and we go back to following the master branch.

@ryancragun yeah I'll take care of cross-testing those things before merging both tomorrow 😃

Re: [hold]: This is probably ok, but needs one final verification with the packages from here.

authors: ryancragun srenatus

repo: chef/chef-server


text:
action :remount in mount resource is not idempotent.

Description
For action :remount, mount resource  is not idempotent by default.
Note:
This is the way it should work:
If remount then it should check if mounted or not.
If not then it need to remount else do nothing but a log message.
Chef Version
Chef Infra Client: 17.10.3
Platform Version
Alma Linux 8
Replication Case
Example
my code:
mount tmp do
    fstype 'tmpfs'
    device tmp
    options 'nosuid,nodev,noexec'
    action :remount
    not_if 'mount | grep /tmp | grep nosuid,nodev,noexec'
 end

Cookbook Result on 1st run:
mount[/tmp] action remount
unmount /tmp
mount /tmp

Cookbook Result on 2nd run:
mount[/tmp] action remount
unmount /tmp
mount /tmp

Note:  Currently to male it idempotent I am adding not_if guard.
Client Output
mount[/tmp] action remount
unmount /tmp
mount /tmp

Stacktrace

The recipe used here is incorrect.
The mount resource has a property named supports which sets {remount: false} by default. Ref  doc mount Resource , and by definition of this resource if this flag is not set for action remount , it does the unmounting and then mounting of the endpoint.
Here’s action remount https://github.com/chef/chef/blob/main/lib/chef/provider/mount.rb#L62, if it does not find property supports to be set to true, it will perform the recipe by first unmounting and then mounting the endpoint(which is what is seen example mentioned above). So recipe rather needs to set this property for the mount resource to be able to do a remount Once the property is set, the resource will continue with the remount_fs call here and perform the mount -o remount... command which is not happening due to the missing property.
So in conclusion, it is not an issue in the mount resource but the recipe is incorrect. The expected recipe for action remount to perform remounting of an existing endpoint is to set the property supports remount: true in the recipe.

repo: chef/chef


text:
Chef cannot install chocolatey packages with capital letters from Artifactory

Description
It looks like chef does a downcase on chocolatey package names, which means packages like "GoogleChrome" cannot be installed via chef depending on your nuget/chocolatey repo.
Chef Version
12.19.36
Platform Version
windows2012r2
windows2016
Replication Case
Note: We are using JFrog's Artifactory product as a chocolatey repo source which is case sensitive, so this issue is specific to that product. The official chocolatey repository works fine. I can provide private access to this for testing if required.

Have an artifactory chocolatey (nuget) repository
Upload the GoogleChrome choco package to artifactory
chocolatey_package 'GoogleChrome' in a recipe
Run chef-client.

Client Output
       ---- Begin output of C:\ProgramData\chocolatey/bin/choco.exe install -y --version 60.0.3112.78 googlechrome ----
       STDOUT: Chocolatey v0.10.7
       Installing the following packages:
       googlechrome
       By installing you accept licenses for the packages.
       googlechrome not installed. The package was not found with the source(s) listed.
        If you specified a particular version and are receiving this message, it is possible that the package name exists but the version does not.
        Version: "60.0.3112.78"
        Source(s): "https://our-artifactory.jfrog.io/us/api/nuget/chocolatey"

       Chocolatey installed 0/1 packages. 1 packages failed.
        See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Stacktrace
N/A

@poblahblahblah Please share private repo access to test, however I am working on to setup my own Artifactory repo.

@poblahblahblah According to https://github.com/chocolatey/choco/wiki/CreatePackages#naming-your-package and https://github.com/chocolatey/choco/wiki/CreatePackagesQuickStart#common-mistakes there shouldn't be mixed case in names by chocolatey naming convention.

@dheerajd-msys understood, although unfortunately this is not enforced even for officially maintained packages:
https://github.com/chocolatey/chocolatey-coreteampackages/blob/master/automatic/googlechrome/googlechrome.nuspec#L5
https://github.com/chocolatey/chocolatey-coreteampackages/blob/master/automatic/cygwin/cygwin.nuspec#L5
https://github.com/chocolatey/chocolatey-coreteampackages/blob/master/automatic/winpcap/winpcap.nuspec#L5
https://github.com/chocolatey/chocolatey-coreteampackages/blob/master/automatic/sourcetree/sourcetree.nuspec#L5
And so on

@dheerajd-msys I can give you access, although I would prefer to not share the credentials via github - do you use keybase or twitter?

I setup my own Artifactory Nuget Repo and pushed package

I setup my own Artifactory Nuget Repo and pushed nuget push C:\Users\Administrator\Downloads\googlechrome.57.0.2987.98.nupkg -Source Artifactory

@poblahblahblah I tried using chocolatey_package with my Artifactory setup and issue hasn't reproduced.
I was getting some checksum issue so added an option in recipe to ignore.
My recipe content
chocolatey_package 'GoogleChrome' do
	source  "http://localhost:8081/artifactory/api/nuget/nuget"
	options "--ignore-checksums"
end

Chef Output
PS C:\Users\Administrator> chef-apply C:\chocolatey_recipe.rb
Recipe: (chef-apply cookbook)::(chef-apply recipe)
  * chocolatey_package[GoogleChrome] action install
    - install version 57.0.2987.98 of package GoogleChrome
PS C:\Users\Administrator>

Chef Version
12.19.36
Platform Version
Windows 2012 R2

Hey @dheerajd-msys, I am still able to reproduce this locally, although it looks like I can only get it to fail when:

We specify a package with a capital letter and a package version
We pass any package as an array
We pass packages as an array and versions as an array

Please note that the gist of the successes show that it's able to install the versions that I am requesting.
Failure scenarios (code and failure):
fails: https://gist.github.com/poblahblahblah/bbeefbd6b2154dc8217aff7c9f63ee33
fails: https://gist.github.com/poblahblahblah/156118ad33aea0a9e2acf2fa8f577dd7
fails: https://gist.github.com/poblahblahblah/11428f360e1c69536d8eb374dd3f2e27
fails: https://gist.github.com/poblahblahblah/e0eb70f761644c274f212b2121e33bae
fails: https://gist.github.com/poblahblahblah/43e292a012f9f9fbaec4b019508a9b70
Success scenarios (code and success messages):
succeeds: https://gist.github.com/poblahblahblah/b6ac9e0b87a91d3f6e87014caa7b6278
succeeds: https://gist.github.com/poblahblahblah/492499ec6b8a90f0bf6a92751cad9e31
Chef Version
12.19.36
Platform Version
Windows 2016

@poblahblahblah I have tested with all your scenarios and it seems when you loop through the code it works as expected.
fails: https://gist.github.com/poblahblahblah/bbeefbd6b2154dc8217aff7c9f63ee33 worked in my case(added comment in gist).
fails: https://gist.github.com/poblahblahblah/e0eb70f761644c274f212b2121e33bae worked in my case (Please check candidate version)
For other failed scenarios I got issue reproduced.  It seems passing option as an Array is creating issue. We might work onto it to get it fixed.

Issues fixed in PR https://github.com/chef/chef/pull/6360
fails: https://gist.github.com/poblahblahblah/11428f360e1c69536d8eb374dd3f2e27 is not resolvable for now since choco doesn't list the candidate versions for dependent packages like notepadplusplus which depends on notepadplusplus.install from Artifactory Repo.
PS C:\Users\Administrator\chef> choco list -r notepadplusplus telegraf -source http://localhost:8081/artifactory/api/nug
et/nuget
aqnotepadplusplus|6.8.8
Metrics.NET.Telegraf|1.0.0
Telegraf|2.0.1

authors: dheerajd-msys poblahblahblah


text:
Not consistent behavior of methods default_action in Chef::Resource::LWRPBase class and action in Chef::Resource class.

This PR fixes different behavior in cases then we set action during resource call and then actions sets from default_action method.
If we call resource and set action directly:
foo_resource 'bar' do
  action :add
end

variable @action will be always an array, no matter if we gave an array or a symbol to the method action.
If we call resource without action:
foo_resource 'bar'

and in its declaration contains:
default_action :add

variable @action will be an array if we gave an array to the method default_action or a symbol if we gave a symbol.
I fixed this difference so that the variable @action always has been an array.

Ah, yes. I've also faced with this when I tried to hack over the resource collection.
So, I think the fix is OK. The action should be an Array type regardless of it is defined explicitly or not.
Chefs, please, check it out.

@lamont-granquist review please.

Did this change between Chef 11 and Chef 12 or something?  Just unclear on what issues are driving the change.
Other than that, it looks okay to me.  The action setter in Chef::Resource coerces actions to arrays already (and we should really clean up our use of @action = :whatever to be action(:whatever) consistently throughout all the Chef resources to not bypass that.
I do have some very vague concerns that this might be a breaking change for someone.  If anyone is inspecting resource.action then this will obviously change that API (although the difference between picking up the default_action and declaring an explicit action is already ambiguous, so I can accept the argument that this is an undocumented edge case that we're fixing and if we do break someone that its acceptable breakage in a minor version).

I renamed this pr on a more understandable name.
In the current situation it is difficult inspecting resource.action, because you don't know type of variable.
I have use case:
checks = run_context.resource_collection.select { |r| r.is_a?(Chef::Resource::NrpeCheck) && r.action == [:add] }.map(&:command_name)

and it behavior is unpredictable, now. Of course i can bypass it, but this would be dirty hack.

@lamont-granquist, what do you say about this?

@chef/client-engineers @chef/client-core needs review

While it's possible to be a breaking change, it seems anyone that's relying on it returning a symbol is already broken when an action is set and an array is returned. :+1:

:+1:

:+1:

Guys, when you plan to merge this PR?

I believe @thommay is planning a merge pass soon in preparation for a 12.4.0 RC.

Ok, thanks! ✨👍

Thanks for your contribution, @Kasen!

authors: Kasen btm lamont-granquist legal90 thommay tyler-ball


text:
added scaffolding-chef plan

After some heated discussion, we've determined that the best location for the Effortless pattern, and the scaffolding should belong in chef/chef.
scaffolding-chef is the framework and implementation of all of the best practices that people who use the Effortless pattern to run Chef Infra. We have developed this in collaboration with the community, and will continue to do so.
This is primarily for two reasons:

scaffolding-chef is open source and developed in collaboration with the community. That means the Effortless pattern is also open source. Anyone can build any content they want on top of this pattern, and it's up to them to decide whether that content is open source or not. If someone wants to open source their content, they can contribute to the public Chef Supermarket.

scaffolding-chef depends on packages in the chef origin, which is gated by the expeditor builds that come from this repository, from the /habitat/ directory in the root of this project. It only makes sense that any package that deps on packages from the chef origin should also belong in this project.

Using core-plans as a model, I've put the scaffolding in the root of the project.
Additionally, this adds a brand new plan.ps1 and scaffolding.ps1 to enable others to create windows based scaffolding-chef packages.
During this process we discovered that Windows plan-build.ps1 does not honor scaffolding dependencies in quite the same way as the Linux plan-build.sh scaffolding dependency code. I'll be opening an issue about it soon. Until then, there is a workaround available by simply including this in your consuming package:
$pkg_deps=@(
  "stuartpreston/chef-client-detox"
  "core/cacerts"
)
$pkg_build_deps=@("core/chef-dk", "core/git")

One final note, this windows package is currently dependent on some offshoot, custom built versions of chef-client for Windows. These need to be fixed upstream before switching the origins over to chef/chef-client. Work is ongoing to get this done -- and this PR is not tightly coupled to that work. Consumers of the scaffolding can continue to work with the offshoot builds with no future disruption in how they build their cookbooks.
Testing
Create a consuming plan.ps1 that looks like the following
$pkg_name="effortless"
$pkg_origin="example"
$pkg_version="0.1.0"
$pkg_deps=@(
  "stuartpreston/chef-client-detox"
  "core/cacerts"
)
$pkg_scaffolding="echohack/scaffolding-chef"
$scaffold_policy_name="windows"
$scaffold_policyfile_path="$PLAN_CONTEXT"

You will also need a policyfile in the same directory as the plan.ps1.
name "windows"

default_source :supermarket
default_source :chef_repo, './cookbooks' do |s|
  s.preferred_for 'windows'
end

run_list ['hardening::default']

You will also need some cookbooks. You can grab these over at: https://github.com/echohack/core-plans/pull/2/files
I have been building the Windows scaffolding on my origin, so by pointing to my origin, you'll get the latest scaffolding. You can always build it yourself and point at your own origin too.

This is the right move for the scaffolding and for core plans. I'm excited about this change.

The build failures are completely unrelated to this change. Can someone override?
1) chef-client when the chef repo has a cookbook with a no-op recipe should complete with success when using --profile-ruby and output a profile file
     Failure/Error: cmd.error!
     Mixlib::ShellOut::ShellCommandFailed:
       Expected process to exit with [0], but received '1'
       ---- Begin output of bundle exec chef-client --minimal-ohai -c "C:/Users/appveyor/AppData/Local/Temp/1/chef_repo20190613-4284-g2zmse/config/client.rb" -o 'x::default' -z --profile-ruby ----
       STDOUT: [2019-06-13T19:04:05+00:00] FATAL: RuntimeError: You must have the ruby-prof gem installed in order to use --profile-ruby
       STDERR:
       ---- End output of bundle exec chef-client --minimal-ohai -c "C:/Users/appveyor/AppData/Local/Temp/1/chef_repo20190613-4284-g2zmse/config/client.rb" -o 'x::default' -z --profile-ruby ----
       Ran bundle exec chef-client --minimal-ohai -c "C:/Users/appveyor/AppData/Local/Temp/1/chef_repo20190613-4284-g2zmse/config/client.rb" -o 'x::default' -z --profile-ruby returned 1
     # ./vendor/bundle/ruby/2.5.0/gems/mixlib-shellout-3.0.4-universal-mingw32/lib/mixlib/shellout.rb:297:in `invalid!'
     # ./vendor/bundle/ruby/2.5.0/gems/mixlib-shellout-3.0.4-universal-mingw32/lib/mixlib/shellout.rb:284:in `error!'
     # ./lib/chef/mixin/shell_out.rb:132:in `shell_out_compacted!'
     # ./lib/chef/mixin/shell_out.rb:66:in `shell_out!'
     # ./spec/integration/client/client_spec.rb:358:in `block (3 levels) in <top (required)>'

2) knife data bag from file When the Chef server has an empty data bag when the chef repo has some data bag items uploads a file in chef's internal format

@echohack do we really have to stick this in the root of the directory here. Can this just go in the hab dir we already have?

So one of the reasons that I think this needs to be in its own directory instead of in the habitat directory is to separate the habitat build of Chef Infra from the recommended approach for running it with the Effortless Config model. I also think this needs a .bldr.toml so that both the scaffolding and the client can get built properly with expeditor.

@tas50 The habitat directory in the root is for building the chef/chef-client plan. It's maybe best to move both to a habitat-packages directory, and rename habitat to chef-client.
What do you think about that?

Build is still drunk and will need to be overriden to merge.

Build is still dead.
Travis Build:Rubocop is dying on... not ruby handlebars syntax.
AppVeyor build is dying on Chef Server knife data bag upload, which I'm 100% positive a Habitat plan has nothing to do with. ^_^

authors: TheLunaticScripter echohack tas50


text:
Changed library from (full) Core to just Review

Updated according to https://developer.android.com/guide/playcore#java-kotlin-in-app-review
Seems to work fine for me. Please verify.

Thanks @fredriksthlm !

authors: chemerisuk fredriksthlm

repo: chemerisuk/cordova-plugin-app-review


text:
Allow to hide / show all the panels.

Add a way to hide completely the panels like it is done for the examples

@lpatiny
what do you mean the leftright panel??? do you mean hide the right panel totally if you hide all the panels from the general settings.

Have something like:

To hide all the panels (that are on the right) and keep only the spectra.

@lpatiny
you can now do this by double click on the resizer area

authors: hamed-musallam lpatiny

repo: cheminfo/nmr-displayer


text:
🛑 Homepage is down

In 54b904a, Homepage (https://larrychen.tech) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Homepage is back up in 4e79936.

repo: chendachao/uptime


text:
index not refresh after update from plugin UI

need refresh option

Hi @ZardoZAntony , I could add this feature in next version, but we need to know if we referesh we could not keep the documents in same order when don't query with sort conditions

@chengpohi thx for prompt reply. Before, I think we need to add "POST/_bulk?refresh" for apply changes to index.  I think we shouldn't keep the sort order after the refresh.

Yes, thx! All work fine now!

authors: ZardoZAntony chengpohi

repo: chengpohi/edql


text:
🛑 tt is down

In f032d40, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 2746 ms

Resolved: tt is back up in b54109b.

repo: chenhaonanniubi/upptime


text:
🛑 tt is down

In 4ea09ef, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 8113 ms

Resolved: tt is back up in 1f22b3c.


text:
🛑 tt is down

In 28e9910, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 3902 ms

Resolved: tt is back up in 26bd58c after 10 minutes.


text:
🛑 tt is down

In 7edd831, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 504
Response time: 10238 ms

Resolved: tt is back up in 4ec1ae4 after 24 minutes.


text:
🛑 tt is down

In e5e3f80, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 3704 ms

Resolved: tt is back up in 7e0fdbb after 22 minutes.


text:
🛑 tt is down

In 37065cb, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 3306 ms

Resolved: tt is back up in db3f15c after 10 minutes.


text:
🛑 tt is down

In 9378592, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 2717 ms

Resolved: tt is back up in 18a5357 after 27 minutes.


text:
🛑 Blog is down

In 5959637, Blog (https://blog.chenishr.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Blog is back up in 86f006c.

repo: chenishr/upptime


text:
[Snyk] Upgrade core-js from 3.26.0 to 3.26.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade core-js from 3.26.0 to 3.26.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2022-11-13.

Release notes

Package name: core-js

3.26.1 - 2022-11-13
Disabled forced replacing of Array.fromAsync since it's on Stage 3
Avoiding a check of the target in the internal function-uncurry-this helper where it's not required - minor optimization and preventing problems in some broken environments, a workaround of #1141
V8 will not ship Array.prototype.{ group, groupToMap } in V8 ~ Chromium 108, proposal-array-grouping/44

3.26.0 - 2022-10-23
Array.fromAsync proposal:

Moved to Stage 3, September TC39 meeting
Avoid observable side effects of %Array.prototype.values% usage in array-like branch, proposal-array-from-async/30

Added well-formed unicode strings stage 2 proposal:

String.prototype.isWellFormed
String.prototype.toWellFormed

Recent updates of the iterator helpers proposal:

Added a counter parameter to helpers, proposal-iterator-helpers/211
Don't await non-objects returned from functions passed to AsyncIterator helpers, proposal-iterator-helpers/239
{ Iterator, AsyncIterator }.prototype.flatMap supports returning both - iterables and iterators, proposal-iterator-helpers/233
Early exit on broken .next in missed cases of { Iterator, AsyncIterator }.from, proposal-iterator-helpers/232

Added self polyfill as a part of The Minimum Common Web Platform API, specification, #1118
Added inverse option to core-js-compat, #1119
Added format option to core-js-builder, #1120
Added NodeJS 19.0 compat data
Added Deno 1.26 and 1.27 compat data
Added Opera Android 72 compat data mapping
Updated Electron 22 compat data mapping

    from core-js GitHub release notes

Commit messages

Package name: core-js

e47e6ed update `package-lock.json`
727fe23 3.26.1
ebf6ee9 update the changelog
a9e9609 move browser test runners to `tests/unit-browser/`
c9ed000 update subdependencies
7478c1f fix missed `cd` in `test262`
e503cc2 because of a npm bug, temporarily revert usage `npm --prefix` instead of `cd`
5de3bef try loglevel verbose for debuging
9e9cacb it seems a npm bug, try to use `--legacy-peer-deps`
a28fdab revert prefix path normalization
e5c2b2f try to normalize prefix path
95e55f3 `npm i` strangely fails on windows, try to use another args order
a0a0719 avoid extra `cd` in `zxi`
f6385a3 sometimes `zx` executes scripts with top-level `await` in incorrect order, try to use `await import()` in affected cases
c869e2a missed `sh` in markdown
a82d507 update `eslint-plugin-regexp`
5e5e468 update dependencies
b9006e7 revert previous commit
832521d add zxi to bin again
43e759b temporarily hardcode the current location
9f762c4 oops
c9d6e53 don't use absolute script path
407aa18 normalize file path
46b5515 drop `zxi` bin because of a strange `zx` issue on windows

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Superseded by #117

repo: cheqd/faucet-ui


text:
🛑 Chequeo Colectivo is down

In b1338df, Chequeo Colectivo (https://chequeado.com/colectivo) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chequeo Colectivo is back up in c116a19.

repo: chequeado/status


text:
🛑 Desgrabador gratuito is down

In 7dc68b2, Desgrabador gratuito (https://chequeabot.chequeado.com/desgrabador/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Desgrabador gratuito is back up in 08ae41d.


text:
🛑 Chequeo Colectivo is down

In 997de9d, Chequeo Colectivo (https://chequeado.com/colectivo) was down:

HTTP code: 502
Response time: 9044 ms

Resolved: Chequeo Colectivo is back up in 65b04dc.


text:
Segmentation fault (core dumped)

Hi, thank you for your work. When I train with your code, I met 'Segmentation fault (core dumped)' error, can you help check the code, thank you!

Could you post the training log?

Could you post the training log?

just begin...
2020-06-12 11:21:37,967 hawp INFO: Saving config into: outputs/hawp/config.yml
2020-06-12 11:21:55,088 hawp.trainer INFO: No checkpoint found. Initializing model from scratch
Segmentation fault (core dumped)

Any more information?

i fork your project, just change 'png' to 'jpg', no more other changes.

What are your hardware devices and the CUDA version?

Could you run the data loader without model forward?

Could you run the data loader without model forward?

My cuda is 8.0 before, now i change to cuda10.2, now i can run normally. Thank you very much!

repo: cherubicXN/hawp


text:
feat: added kubesec

Closes #22

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

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

repo: chgl/kube-powertools


text:
harden fd_handle_pipe

Prior to this commit, fd_handle_pipe did not handle any possible read errors. Also, it was prone to a DOS attack vector where a user can endlessly spam the readiness pipe. turnstiled would hang if this happens, and eventually run out of memory.
This commit limits the maximum amount of characters the readiness pipe is allowed to read in to PATH_MAX (seems like a reasonable max, but may need adjustment). It also adds some error logging for the case where the max is exceeded, as well as for if read returns an error at any point. If the max is exceeded, the ready service is still called as usual, and the value read from the pipe up to that point will be passed. This could lead to issues on the ready service side, but it will allow the user to still log in at least (assuming the ready service isn't critical). Perhaps more should be done to communicate this truncation to the user side, but as of now at least this will prevent the DOS.

Amended to use ssize_t, not size_t

hm i think the way this is handled is a bit clunky, i don't think we really need the exceededmax variable or the other checking at all
i'd just check like:
if ((c == '\0') || (lgn->srvstr.size() >= PATH_MAX)) {
    /* done receiving */
    done = true;
    break;
}

Hey thank you for reviewing
That is fair, I was thinking the logging of the possible failures here could be valuable but I agree it does add some clunk and room for possibly other issues.
I can amend to make the change.
Also, do you think PATH_MAX is a fine max to use here or should a max be defined in turnstiled.hh?

please follow the established style, like in the snippet i provided, also size() is correct over length() here

Ah missed the parens, mb. Didn't know about size vs length, am new to c++, thank you.
Will amend soon 👍

they are the same but the convention is that length is for text strings while size is for element vectors, and in this case it's the latter

Sweet, I amended the change.
Regarding logging, the existing logs from the readiness service should be good enough anyways. If it gets truncated and that is an issue, then there should be an error that the readiness service reports. For the runit backend for example, it says "invalid readiness service: ...", which is good. The dinit backend looks like it has a similar check against "$2", so that should be fine as well.
Regarding testing, I did do a manual test of this with the runit backend and fed in a bunch of data to the ready pipe. I can share more details if you'd like to reproduce, or if you think it's OK to merge then that's cool too, whatever you think.

repo: chimera-linux/turnstile


text:
更新TRR中鉴权验证使用中间件的方式

新增鉴权注解中间件 Auth 验证
具体修改如下

更改了 application/http/middleware/Auth.php 文件下 handle 方法
public function handle($request, \Closure $next)
{
     if (!empty(request()->routeInfo()['option']['middleware']) &&
          in_array('Auth', request()->routeInfo()['option']['middleware'])) {
           Token::verificationToken('uuid');
     }
     return $next($request);
}

在 application/lib/token/Token.php 文件下新增 verificationToken 方法
public static function verificationToken($key)
{
     return self::getCurrentTokenVar($key);
}

鉴权中间件使用方式

TRR 类 中间件注册

例如：application/api/controller/v1/Book.php

      ```php
     /**
      * Class Book
      * @doc('图书类')
      * @group('v1/book')
      * @middleware('Auth')
      * @package app\api\controller\v1
      */
     class Book{}
      ```

TRR 类方法 中间件注册

例如：application/api/controller/v1/Book.php 中 create

```php
    /**
     * @doc('创建图书')
     * @route('','get')
     * @validate('CreateGroup.edit')
     * @middleware('Auth')
     * @param('name','图书名称','require|graph|length:1,50')
     * @param('img','图书img','require|graph|length:1,16')
     * @return \think\response\Json
     * @success('')
     * @error('')
     */
    public function create()
    {
        return json([
            'class' => 'application/api/controller/v1/Book.php',
            'action' => 'create'
        ], 200);
    }
```

至此访问此接口就需要在 hearder 头中传入 Authorization 类型为 Bearer 的 access_token 参数实现权限验证

新增鉴权注解中间件 Auth 验证
具体修改如下

更改了 application/http/middleware/Auth.php 文件下 handle 方法

use app\lib\token\Token;
// 省略代码
public function handle($request, \Closure $next)
{
    Token::verification();
    return $next($request);
}

鉴权中间件使用方式

TRR 类 中间件注册

例如：application/api/controller/v1/Book.php

      ```php
     /**
      * Class Book
      * @doc('图书类')
      * @group('v1/book')
      * @middleware('Auth')
      * @package app\api\controller\v1
      */
     class Book{}
      ```

TRR 类方法 中间件注册

例如：application/api/controller/v1/Book.php 中 create

```php
    /**
     * @doc('创建图书')
     * @route('','get')
     * @validate('CreateGroup.edit')
     * @middleware('Auth')
     * @param('name','图书名称','require|graph|length:1,50')
     * @param('img','图书img','require|graph|length:1,16')
     * @return \think\response\Json
     * @success('')
     * @error('')
     */
    public function create()
    {
        return json([
            'class' => 'application/api/controller/v1/Book.php',
            'action' => 'create'
        ], 200);
    }
```

至此访问此接口就需要在 hearder 头中传入 Authorization 类型为 Bearer 的 access_token 参数实现权限验证

repo: china-wangyu/TRR


text:
Resizing of target_specs widget shrinks QLineEdit fields

When the height of the top level widget is reduced to a certain point, the height of the target_specs window is reduced and the QLineEdit widgets are compressed, even when the scroll bar appears.
The encompassing QScrollArea() has setWidgetResizable(True) as suggested in  https://www.qtcentre.org/threads/14938-Dynamic-updates-of-a-QWidget-in-a-QScrollArea so this seems not to be a problem.
Modifying minimumSizeHint() as suggested in https://stackoverflow.com/questions/46361675/pyqt-enforcing-sizehint-dimensions-on-two-widget-app-with-layout-manager#46393700 also didn't work.
This has probably to do with the freq_specs and amplitude_specs subwidgets where fields are added and removed dynamically to a QGridLayout depending on the filter type.
See https://stackoverflow.com/questions/21253755/qscrollarea-with-dynamically-changing-contents
Possible solutions in freq_specs.py that have some effect on the behaviour:

self.adjustSize()
qlineedit_widget.setFixedHeight(qlineedit_widget.sizeHint().height()) # not so much
self.layGSpecs.setSizeConstraint(QtWidgets.QLayout.SetMinAndMaxSize)

The last one has the most effect, the size of the subwidget now stays fixed when the size of the top level window is reduced. However, now the parent widget (target_specs.py) is reduced in size, making a part of the input fields invisible. Maybe this can be combined with monitoring resize events.
setSizePolicy(QSizePolicy.Minimum) sets the minimum size to the size hint and could be set on target_specs to prevent the widget from shrinking. Tried this on freq_specs and target_specs without effect

Fixed in v0.9.6 - the culprit was one missing `QSizePolicy() setting ...

repo: chipmuenk/pyfda


text:
Vendor libtock-rs

We vendor it for a few reasons:

It simplifies our build, so that we no longer have to specify the LIBTOCK environment variables
We can make more easily make changes to accommodate our user-mod testing
We can integrate async support more seamlessly.

I also took this opportunity to rename pldm-app to example-app.
I ran cargo clippy --fix and did some other clippy fixes. (This also reordered some of the tests in other files.)

Thanks! Don't worry about all of the libtock-rs code for now, just because most of it we aren't going to need, and we don't want to change it too much (in case we want to cherry pick code from the upstram later).

repo: chipsalliance/caliptra-mcu-sw


text:
Fix broken gateway ID generation

When testing locally, I noticed that the auto-generation of gateway IDs in the user interface is broken in the development environment. This seems to be due to the fact that Node's Buffer API is not natively available in the browser.
This fix does the conversion from UInt8Array to hex string natively, as per this StackOverflow post.

Thanks @breezykermo, I've fixed this in the above commit. As there are more references to the Buffer class, I have included the buffer package as dependency. Strangely I thought this was working, as I have done testing with the random DevEUI and keys + device queue, but I can confirm this no longer works without the fix. Might have been some local cache where the Buffer class was present. Thanks for raising this issue :+1:

Not a problem, thanks for the great work with chirpstack in general!

authors: breezykermo brocaar

repo: chirpstack/chirpstack


text:
Support WebSocket endpoints

I would like to be able to open WebSocket connections similar to the current HTTP endpoints.
I thought at first I could use a library like https://github.com/websockets/ws inside the endpoint but that's not possible.

also would like to support Server-Sent Events

repo: chiselstrike/chiselstrike


text:
🛑 VirMach US is down

In 768f819, VirMach US (virmach-1.chitang.eu.org) was down:

HTTP code: 0
Response time: 0 ms

到期了，VirMach 狗都不续


text:
Re-List Cards

Would it be possible to have an option to re-list cards and do nothing else.
Sometimes when I have a full transfer list it would be useful to keep listing cards every hour without even searching. I would think that it would cause less captchas and errors.
Great job on this very useful script.

Yeah i had the same question

I just set it up to do a search or two for something tremendously unlikely to hit and then pause for an hour

I just set it up to do a search or two for something tremendously unlikely to hit and then pause for an hour

Im gonne try this 2 not a bad idea

authors: Gafanha captain-cronch dreery1990

license: ISC


text:
Extract server into its own repository to be release and maintained independent from the client

Describe your question
Extract server into its own repository to be release and maintained independently from the client. Currently, both are in the same repo where both are aligned in versioning. Most developers are likely only interested in the MQTT client.
Which project is your question related to?

Client
ManagedClient
MQTTnet.Server standalone
Server
Generic

This seems to be more or less a duplicate of https://github.com/chkr1011/MQTTnet/issues/1026.

This seems to be more or less a duplicate of https://github.com/chkr1011/MQTTnet/issues/1026.

authors: SeppPenner ramonsmits


text:
RFM - FreePlane

I Want To Become The Maintainer

[x] I have followed the Package Triage Process and I do want to become maintainer of the package;
[x] There is no existing open maintainer request for this package;

Checklist

[x] Issue title starts with 'RFM - '

Existing Package Details

Package URL: https://chocolatey.org/packages/FreePlane
Package source URL: https://github.com/dtgm/chocolatey-packages/tree/master/automatic/freeplane
Date the maintainer was contacted (in YYYY-MM-DD): 2020-04-09
How the maintainer was contacted: https://github.com/dtgm/chocolatey-packages/issues/496

I have just added @tunisiano187 as a maintainer of this package.

@gep13 , can you assign it to me?
That's usefull to follow what is still in progress.
Thank you

@tunisiano187 Gary could not have added you until you added a comment to the issue.
This is a limitation of GitHub. (Just so you know).

Thank you, didn't knew it.

@tunisiano187 I don't think most people know that. I found that first out myself last weekend (while working on some upcoming enhancements to the request validator).

Maybe you should add it in the Readme as a requisite to became maintainer ?

I am planning to make some changes to the docs, to add a section of what is expected when a new maintainer is picking up a request.
I have not yet gathered the full thoughts of how this is detailed yet, though.

This package as his first version approved a new one has been sent, so i think you can close the issue.
Thank you


text:
Add openMM checkpointing to VanillaMDSimulator

We should be able to stop and start simulations to use short queue-times rather than having to schedule enough time to

This may not be easy with dask, but worth seeing if it is doable.

repo: choderalab/asapdiscovery


text:
Version management using versioneer

From the example in the cookie cutter (https://github.com/choderalab/cookiecutter-compchem)
This should make version management easy.

Going to cut a release after this and then set up a conda package for omnia so that protons becomes installable. I think this is long overdue.

Codecov Report

Merging #120 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #120      +/-   ##
==========================================
+ Coverage   62.59%   62.64%   +0.05%
==========================================
  Files          37       38       +1
  Lines        5063     5070       +7
==========================================
+ Hits         3169     3176       +7
  Misses       1894     1894

Impacted Files
Coverage Δ

protons/_version.py
100% <100%> (ø)

protons/__init__.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

authors: bas-rustenburg codecov-io

repo: choderalab/protons


text:
Version 2.0 issues to be tackled

This is a place to keep track of what needs to be done before we're ready to submit.
Small things

[x] Fix any inline refs and comments within the text.
[ ] Make sure we reference any open-source software that was used in the class.
[x] Come up with an easy-to-remember name for this model of teaching. What about something like cluster-based bootcamps?

[x] let's call these container-based bootcamps

[x] Insert a table that gives an idea for how cost per student breaks down by size of the class / time.
[x] Confirm / edit the short section at the end to succinctly list new developments that
are needed.
[ ] Add some more citations where we make factual statements.

[x] added clark-proc-scipy-2014 to Challenges of a traditional bootcamp approach

[x] We should include a link to our repositories as well as to the Docker setup images
etc in the main text
[x] Section 2.2: title little misleading b/c you are actually comparing the cloud approach to bootcamp approach. However, traditional teaching implies something else I think. (has this already been addressed?)
[x] address XXX WHY IS JETSTREAM MORE ATTRACTIVE? HOW IS IT DIFF FROM TRADITIONAL HPC
[ ] review Aaron's changes to section on Cost and payment opportunities

Medium things

[x] Brain-storm the title for something a little bit more specific.

[x] updated paper with this proposed based on brainstorm: "Portable learning environments using container- and cloud-based technology for hands-on computational instruction"
[x] title too long in paper heading, so split into title/subtitle \title{Portable learning environments for hands-on computational instruction}\subtitle{Using container- and cloud-based technology to teach data science}

[x] Finalize title

[x] In Section 4.2.1: Include a figure w/ screenshots

[x] Methods section needs to be more "hands on" and step-by-step for people to get things working, in addition to describing the hardware / software that we used. (I already addressed this along with @aculich but somebody should confirm / suggest changes)

[x] Add a section about a user retrospective, or incorporate some of the quotes from the questionnaire.

@aculich or @arokem do you wanna take a pass? Maybe @fatmai could incorporate some kind of user retrospective?

[ ] Brain-storm the title for something a little bit more specific.

Potential titles
"Container- and cloud-based learning environment for hands-on computational instruction"
"Using Docker and the Jetstream cloud for hands-on instruction of computational skills"
"Portable learning environments for ad-hoc computational workshops based on Docker and the Jetstream cloud"

(I'm thumbs-upping after I append above)
I like #1 above - we could also incorporate whatever "short name" we come up with to describe these kinds of things?

I also like title 1, though would like to also bring in the word "portable" from 3 since it captures the "mobility of compute" we talk about in Research IT... so how about some variation on 1 like this: "Portable learning environments using container- and cloud-based technology for hands-on computational instruction"

Regarding the term "cluster-based bootcamps", since we technically didn't use a cluster, I've been expunging that word from earlier editions of the paper, replacing it with "cloud platform"... to the cyberinfrastructure community, the word cluster is going to imply an HPC cluster, but Jetstream has a very different architecture since it is cloud/VM based.

@choldgraf  "Section 2.2: title ... has this already been addressed?" Yes, when I saw Fatma's comment I updated the section, so hopefully it addressed what she was pointing to... I thought I had checked it off on the checklist of #13, but maybe that didn't get saved?

sorry folks I can only work on it after 7:45pm.
On Sun, Mar 12, 2017 at 3:42 PM Aaron Culich notifications@github.com
wrote:

@choldgraf https://github.com/choldgraf "Section 2.2: title ... has
this already been addressed?" Yes, when I saw Fatma's comment I updated the
section, so hopefully it addressed what she was pointing to... I thought I
had checked it off on the checklist of #13
https://github.com/choldgraf/paper-pearc_2017/issues/13, but maybe that
didn't get saved?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/choldgraf/paper-pearc_2017/issues/19#issuecomment-285983280,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFOrNFtO8wmTziezJiW5VVB2BoO3VWbnks5rlHTIgaJpZM4MaqAK
.

For a title, why not just "Portable learning environments using container- and cloud-based technology"
For the text, I took a quick look tonight and will make another quick look early tomorrow AM. We can do a short iteration on it then and then send it off!

PR #24 includes one and the only user comment that I was able to use in terms of cloud-computing usage. Feel free to change framing. Looks good otherwise.

Hey all - I just pushed a new version that includes all the incorporated changes from you all, and also adds an image showing a sample jupyter notebook that the students see after going to an IP address (I just chose a random IP address and opened a notebook locally for the screenshot).
See a PDF of the generated result here:
https://www.dropbox.com/s/l4dkwzlogyrqsab/paper.pdf?dl=0
@arokem @aculich @fatmai where do we stand now? Anything else to do before submitting? If not, should we submit?!?!?

Looks great.
🚢  it!

@aculich @fatmai see top-level comment in this thread to give "ship it" directive :)

:ship: it!!

OK! It is shipped!!!!

I had help reviewing the final draft...

authors: aculich arokem choldgraf fatmai

license: mit


text:
Homebridge plugin

Hello!
This is not an issue, just a question...
Do you know about any kind of plugin like this to use with homebridge, to be compatible with HomeKit?
Or any other way to make it compatible to HomeKit?
Thank u in advance!

I do not know of any.
I have created dedicated API that can be integrated in any environment with python:
https://github.com/chomupashchuk/ariston-remotethermo-api
I see that someone downloaded API but i have no idea how it was used.

I do not know of any.
I have created dedicated API that can be integrated in any environment with python:
https://github.com/chomupashchuk/ariston-remotethermo-api
I see that someone downloaded API but i have no idea how it was used.

authors: chomupashchuk ojoaosemtil


text:
envify not wiring in process env vars correctly

🐛 bug report
Expected Behavior

setting NODE_ENV=development npm start should yield choo components with process.env.NODE_ENV popluated

Current Behavior

NODE_ENV is not reflected on the page when referenced
here's a single commit on top of the default create-choo-app deployment, using bankai 9.7.0: https://github.com/cdaringe/choo-envify-/commit/7bf61d79204a726c7f51b353d9653264dc5f7f94

^you will notice that development flickers, then disappears.
Possible Solution

maybe SSR is getting the env, but the bundled app is dropping the env? that could explain the flickering.

Code Sample

see repo above

Your Environment

Software
Version(s)

Package
create-choo-app/bankai

Runtime
node latest

Package Manager
npm

Operating System
osx, latest

Oh, this is because we use envify via tinyify, which is only enabled in bankai build. we should add it in an else here: https://github.com/choojs/bankai/blob/f0cb935f4d03eb42f2eb797f6de37ed070207c81/lib/graph-script.js#L100

i queued it up:
  if (shouldMinify) {
    b.plugin(tinyify)
    b.on('split.pipeline', function (pipeline) {
      tinyify.applyToPipeline(pipeline, b._options)
    })
  } else {
    b.plugin(envify) // i required it in, above
  }

and npm linked it into create choo app.  the issue still occurs.  I confirmed that the envify code block is being hit as well.  any other ideas?

envify is a transform, not a plugin:
b.transform(envify, { global: true })

Altho I can't get that to work just yet either :sweat_smile:

Should be fixed by #436 in :package: 9.8.0!

:tada:

authors: cdaringe goto-bus-stop

repo: choojs/bankai


text:
rm choo-log

Removes choo-log from the install step. Depends on https://github.com/choojs/choo-devtools/pull/14, and related to https://github.com/choojs/discuss/issues/2. Thanks!
Sibling PR – https://github.com/choojs/create-choo-app/pull/28

📦 v1.7.0

repo: choojs/create-choo-electron


text:
Does CUH-ZCT1x has any support?

So I've bought this controller and I can't get it work over usb
ds4drv --hidraw
just infinitely scans for devices
lsusb
Bus 001 Device 026: ID 054c:05c4 Sony Corp. DualShock 4 [CUH-ZCT1x]
udev rules
KERNEL=="uinput", MODE="0666" KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="05c4", MODE="0666" KERNEL=="hidraw*", SUBSYSTEM=="hidraw", KERNELS=="0005:054C:05C4.*", MODE="0666" KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="09cc", MODE="0666" KERNEL=="hidraw*", SUBSYSTEM=="hidraw", KERNELS=="0005:054C:09CC.*", MODE="0666"

Same thing for me, had to use another controller

Isn't there any other software to make this unsupported version work?

authors: AbdulRhmanHS karimrir1 steveunixson


text:
error while saving youtube stream

[stream.hls][warning] Failed to reload playlist: Unable to open URL: http://manifest.googlevideo.com/api/manifest/hls_playlist/id/HC5sCm6Mg40.1/itag/96/source/yt_live_broadcast/ratebypass/yes/live/1/cmbypass/yes/gir/yes/dg_shard/SEM1c0NtNk1nNDAuMQ.96/hls_chunk_host/r20---sn-5hn7snee.googlevideo.com/pmbypass/yes/gcr/fr/maudio/1/playlist_type/DVR/mm/32/ms/lv/mv/m/pl/44/dover/2/upn/Y2c4lPwmdG4/sver/3/fexp/900720,907263,912334,916657,932627,932631,934954,938813,9406990,9408347,9408919,947243,948124,948703,951703,952612,957201,961404,961406/mt/1428789246/ip/2a00:1ca8:37::8f1:68c/ipbits/0/expire/1428810892/sparams/ip,ipbits,expire,id,itag,source,ratebypass,live,cmbypass,gir,dg_shard,hls_chunk_host,pmbypass,gcr,maudio,playlist_type,mm,ms,mv,pl/signature/1F6E484B7800BA4072FDD4DB5090FB2787E9DA45.391805A0C3FCA2997BE4B275D36AE06C8805A16B/key/dg_yt0/file/index.m3u8 (403 Client Error: Forbidden)
bash: syntax error near unexpected token `('
[cli][error] Error when reading from stream: Read timeout
bash: [cli][error]: command not found
[cli][info] Stream ended
This happened a few hours into the stream; is there any way to avoid this? I increased the timeout length to 40 but the download still got broken.

Youtube playlist URLs seem to expire after a few hours, not sure if we can do anything about it unfortunately.

Thanks for the answer. I ran a script to timeout livestreamer every 2 hours but I was getting a [500 Server
Error: Internal Server Error] occasionally, but it seems that livestreamer continued to run until the 2 hour mark. Do you think any segments are missing?
[stream.hls][warning] Failed to reload playlist: Unable to open URL: h ttp://manifest.googlevideo.com/api/manifest/hls_playlist/id/iGTIK_8ydoI.1/itag/151/source/yt_live_broa dcast/ratebypass/yes/live/1/cmbypass/yes/gir/yes/dg_shard/aUdUSUtfOHlkb0kuMQ.151/hls_chunk_host/r8---s n-5uaeznzs.googlevideo.com/pmbypass/yes/playlist_type/LIVE/maudio/1/gcr/id/mm/32/ms/lv/mv/m/nh/IgpwcjA yLmF0bDAxKgkxMjcuMC4wLjE/pl/22/dover/2/sver/3/upn/eEEtQeoWksA/fexp/900720,907263,916732,924637,932627, 934954,9405985,9407115,9407407,9407669,9408093,9408347,9408618,9408705,9408787,9408940,947233,947243,9 48124,948703,951703,952612,952613,952615,952626,957201,961401,961404,961406/mt/1429162202/ip/63.142.25 0.163/ipbits/0/expire/1429183860/sparams/ip,ipbits,expire,id,itag,source,ratebypass,live,cmbypass,gir, dg_shard,hls_chunk_host,pmbypass,playlist_type,maudio,gcr,mm,ms,mv,nh,pl/signature/634DBA425279627B221 BC6936966EA5ADCF03BE5.8EA4833DADEB1C78C3019C7BA686DF7C661AF684/key/dg_yt0/file/index.m3u8 (500 Server Error: Internal Server Error)

repo: chrippa/livestreamer


text:
i could not import the library

Error:Could not find property 'plugin' on com.android.build.gradle.LibraryExtension_Decorated@5e34222f.

Manifest merger failed : Attribute application@appComponentFactory value=(android.support.v4.app.CoreComponentFactory) from [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91
is also present at [androidx.core:core:1.0.1] AndroidManifest.xml:22:18-86 value=(androidx.core.app.CoreComponentFactory).
Suggestion: add 'tools:replace="android:appComponentFactory"' to  element at AndroidManifest.xml:33:5-314:19 to override.

repo: chrisbanes/PhotoView


text:
handling Inf and NaN subsitutions inside of @avx

Depending on the application, one often needs to define what 0.0/0.0 means, be replacing NaN or Inf in a vector by the appropriate value. For example, my code does:
@. scratch = replace_inf_nan(a / b)
@avx @. x += c * d * scratch

where replace_inf_nan(x::T) where T = ifelse((isnan(x) || isinf(x)), zero(T), x)
I would love to be able to do this at once inside of the @avx expression, avoiding the intermediate computation in the scratch vector. As I understand it, this is not currently supported? I suppose it would require special support, similar to exp.

using SIMDPirates # will eventually be `using VectorizationBase` instead
replace_inf_nan(x::T) where T = vifelse(isnan(x) | isinf(x), zero(T), x)

Also, do you know isfinite?
replace_inf_nan(x::T) where T = vifelse(isfinite(x), x, zero(T))

There are plans to integrate LoopVectorization more with the compiler, but a secondary problem is that, until then, it won't be able to introspect inside your function. It thus assumes the function is relatively costly, like exp.
So that's fine if that's true. Otherwise, for now, you'll probably get better performance by writing simple definitions like vifelse(isfinite(x), x, zero(T)) directly in the loop, to let it more accurately model the costs.

Wonderful, this works like a charm: code is now 20% faster!

authors: chriselrod guyvdbroeck


text:
[ Aesthetics ] Mach border thickness

Now we have 4 pixels ( in red ) for :

the distance between the node's header and the first slider
the distance between the sliders
the distance between the node and the controller's gutter
the controller's gutter thickness

But only 3 pixels ( in blue ) for :

the nodes's side border thickness
the node's bottom border thickness

It would look better and more symmetric, if this was all 4 pixels.

The thicker border will also make the Prompt nodes stand out more, if we give them another color.

mockup:

original:

done, I think, on dev

Looks good !

repo: chrisgoringe/cg-controller


text:
Feature Request: Revisit Periodic Notes Support?

Feature Requested
I recently started using this workflow (and Obsidian) and I'm trying to find a way to navigate to daily/weekly/etc notes using Alfred.
Would we be willing to entertain period notes feature support again?  I see you've already covered this in a previous request: https://github.com/chrisgrieser/shimmering-obsidian/issues/45
I actually discovered https://github.com/hauselin/obsidian-alfred before this repo, and have forked and already fixed a few bugs on my own.  Having to do lots of refactoring and clean up.
Reasons to revisit:

Appears hauselin/obsidian-alfred is stale/dead? and hasn't responded to my pings.
Discovered several bugs in addition to stale issues that's currently blocking a working solution for Obsidian users
I'm happy to own and PR the feature since I've already implemented daily & weekly
- I would prefer to use your code patterns than do refactoring on a fork
I would like to add a pattern for having common javascript functions, and unit tests for them in CI.  Why?  I end up duplicating a lot of functions, so would like to consider using another file as a Library - Jumping into JXA for the first time so happy to use a better mechanism if one exists.

I have several design questions before I would begin the feature, and happy to write up thoughts to get alignment.
Thanks!
Relevant Screenshot
No response
Checklist

[X] The feature would be useful to more users than just me.
[X] I have checked the feature overview and the feature doesn't already exist.
[X] Feature Requests regarding daily notes will not be implemented, since there are other Alfred workflows that do focus on daily notes already.
[X] If it is an entirely new feature: The requested feature makes more sense to be implemented in Alfred than in a plugin. Please also explain why.

Hi, yeah, the main reason for deprecating anything daily- or weekly note related was that they are quite high maintenance (tons of different formats, a lot of date-related edge cases, etc.), while at the same time, I don't use daily notes at all.
If you are willing to PR and maintain the feature, I don't mind adding support for them again. 🙂

I would like to add a pattern for having common javascript functions, and unit tests for them in CI. Why? I end up duplicating a lot of functions, so would like to consider using another file as a Library - Jumping into JXA for the first time so happy to use a better mechanism if one exists.

To be honest, using JXA wasn't the best solution in hindsight. I started creating the workflow when I started out to learn programming, just used JXA because it was JavaScript that I could use without installing anything on my Mac. Due to the fact that a lot of code was written when I was just starting to learn to code, there are probably quite a few places with rather badly written code from that time 😅
One of the big issues is that JXA does not supportimport, kinda restricting you to one file. It is mostly due to Alfred connecting different pipes, that the workflow nevertheless is modularized into different files – however, there is virtually no sharing of common functionality between the files, and therefore a good amount of redundant code. I was actually considering migrating the code base to typescript at some point, but I wasn't aware of those script libraries you linked. If they indeed allow for proper shared functionality, that'd be awesome.

If you are willing to PR and maintain the feature, I don't mind adding support for them again. 🙂

Sweet!  Is this thread a good place to review with you my approach, proposed feature, and shortkeys?
Also do you have a good release version I can check out for the previous daily note feature?

I was actually considering migrating the code base to typescript at some point in the future, but I wasn't aware of those script libraries you linked. If they indeed allow for proper shared functionality, that'd be awesome.

I'll do a quick POC and make sure it's what we want, but from the docs it appears like a good way to share functionality across the code base.

Sweet! Is this thread a good place to review with you my approach, proposed feature, and shortkeys?

Nah, issues are more "user-facing" so to speak. Think a (draft) PR might make most sense, I think.

Also do you have a good release version I can check out for the previous daily note feature?

Don't think it's gonna help much. Those daily note features were from a time when the workflow was structured very differently, so it'd be hard to move just part of them to the present. Also, they were pretty bare bones "create file with today's date and append to it" anyway.

authors: chrisgrieser weklund

repo: chrisgrieser/shimmering-obsidian


text:
Add config values

In order to do NAT traversal for a connection with a specified node, some or all of the following will be required:
"Libp2pStreamMounting": true

"RelayClient": {
     "Enabled": true
}

"Transports": {
     "Network": {
          "Relay": true
     }
}

It may be desirable to also be a RelayService - more research required to determine optimal Embassy setup
Config details here: https://github.com/ipfs/go-ipfs/blob/88d88158c61dc657b2c9d83107ec02d0d6040cef/docs/config.md

Added in b9f72495b24e1af36fa42afad46d39bb26d3a3cf

repo: chrisguida/ipfs-wrapper


text:
Where buy bata bta?

Version

Description

I don't understand your question. I close down the issue.

authors: bzmhmmhi chrisleekr

repo: chrisleekr/binance-trading-bot


text:
Background reload does not update actor background xy limit until restart.

Describe the bug
Updating a Backgrounds Dimensions will not update actor xy limits until an editor restart.
To Reproduce
Steps to reproduce the behavior:

Place an actor on a small background
Change the backgrounds size to larger in any dimension(s) and save
Try to move the actor into the new empty space.
Actors limited to the old xy dimensions.

Expected behavior
Auto or manual asset reload updates the background xy limits for actors in a scene.
Screenshots
If applicable, add screenshots to help explain your problem.

Platform (please complete the following information):

OS: [Windows 10]
App version [1.2.1 / latest dev branch]

Additional context
Collisions are cleared, so at least some areas get the new dimensions.
Another issue related to missing images causing a crash could complicate how this is fixed.

This appears to be fixed in GBStudio 2.0 Beta2! Woo!
(another bug similar to this now exists for changing a scenes background from the editor drop down. #559 )

repo: chrismaltby/gb-studio


text:
Improvement: dtb file

Improvement suggestion:
Backup and Restore the DTB file on use.
Specially useful for those people that swap the DTB file because of screen version.

I don't understand the request.

You can backup the DTB manually by connecting the SD card on your pc and copying the DTB files to your PC

Thanks, I know that. I'm using the internal eMMC, so it's not that linear.
The suggestion was to include the boot DTB file into the backup/restore scripts.

Not something i will incorporate at this time since the issue only affects a small portion of 353 devices with v1 screens.  I have a v1 353v that is on 24/7 for development and testing and v1 353m i use daily and they don’t exhibit this issue.

authors: christianhaitian gabrielmop lauren7ino

repo: christianhaitian/arkos


text:
make package

add init, setup.py and some documentation

also get set up with CI

still missing CI and documentation


text:
Fix build when using libfmt (fmtlib) as system dependency on at least Ubuntu

The recent PR #187 removed git submodules and greatly improved flexibility wrt. build dependencies, however libfmt on Ubuntu (20.10 at least) is broken due to how it is addressed in the cmake files.

/ping @avemilia :+)

Right now I have no space on disk left to install the VM to see what the error is and test, so anyone, feel free to pick up. It would be helpful if you at least posted the error message, maybe somebody can just look at it and say what is wrong.
Anyway, the relevant code is https://github.com/christianparpart/contour/blob/755b7959c801f6373b3065211b684e35798afbbd/CMakeLists.txt#L65-L71
so in my understanding it can only break in two cases: fmt in Ubuntu doesn't provide fmt::fmt-header-only target (which I took from official docs and confirmed in /usr/lib/cmake/fmt/fmt-targets.cmake on my system) or fmt is simply not installed.

Good morning. I will post it here and will also try to look at it by the end of next week, maybe on-stream again into it. :)

hmm... I settled on not using system deps on those 4 libraries. embedding is way to easy. we can re-open at any time again if time permits :)

authors: avemilia christianparpart

repo: christianparpart/contour


text:
Breaks on /^$/gmi (Specifically the next time the regex is changed.)

Sought out this extension to get some visual feedback when editing regexes, as I often use them in my day to day work.  However, when starting from the "empty line" regex above (/^$/gmi) and extending it, the extension host will terminate.
Versions:

Visual Studio Code 1.5.2
Ubuntu 16.04

Reproduction steps:
Two open editor panes.  Left is set to javascript, right is set to plain text.  Extension is enabled and cursor is in regex body.
plain text pane:
# Email Test Cases #

Pulled from https://blogs.msdn.microsoft.com/testing123/2009/02/06/email-address-test-cases/

TODO: Remove invalid test cases that should in fact be valid, such as the one assuming TLD validation.

## Valid Email Addresses ##

email@domain.com
firstname.lastname@domain.com
email@subdomain.domain.com
firstname+lastname@domain.com
email@123.123.123.123
email@[123.123.123.123]
"email"@domain.com
1234567890@domain.com
email@domain-one.com
_______@domain.com
email@domain.name
email@domain.co.jp
firstname-lastname@domain.com

## Invalid Email Addresses ##

plainaddress
#@%^%#$@#$@#.com
@domain.com
Joe Smith <email@domain.com>
email.domain.com
email@domain@domain.com
.email@domain.com
email.@domain.com
email..email@domain.com
あいうえお@domain.com
email@domain.com (Joe Smith)
email@domain
email@-domain.com
email@domain.web
email@111.222.333.44444
email@domain..com

javascript pane:
var emailPattern = /^$/gmi;

To trigger an extension failure, place the cursor between ^ and $ in the javascript pane and enter a character such as e.
Expected result:
Right pane has 0 entries highlighted until finished changing /^$/gmi to something like /^email.*$/gmi, at which point entries matching that regex should become highlighted.
Actual result:
[Error] Extension host terminated unexpectedly.  Please reload the window to recover. [Reload Window]
[Error] Error from the extension host: channel closed [Close]

@SMEmp Thanks for the detailed steps to reproduce!

authors: SMEmp chrmarti

repo: chrmarti/vscode-regex


text:
[New Feature][Ease of Use] Auto-Ingestion Batching

Auto-Ingestion Batching
Chroma users tend to throw a bunch of data at Chroma at once to get their collections set up. On many developer-class machines, and remote notebook environments like Colab, this immediately leads to high memory consumption and hard swapping, making Chroma appear much slower on ingestion than it actually is in the (platonic) world of ideal forms.
Additionally, the user does not know if Chroma has crashed, their system has hung, or how ingestion is going in general.
API Design
# New argument on add
collection.add(..., batch_size=128)

# Display a progress bar
[---------60%           ]

# Impl 1.
# Wrap add classic in a loop with tqdm strapped on it
def add(self, batch_size=128, **kwargs):
    for ...
        self._add(**kwargs)

[Complexity] Subtask

[Low] Ship it with a reasonable default
[Low] Investigate the tradeoffs to make sure we ship a reasonable default
[High] Paralellize and pipeline this with EF (and Chunker). Whole thing is parallelizable. Knowing the batch size in advance helps considerably.

Misc

Is there something here we could do with returning query results also ?

I think the main problem with auto-batching during ingest is that since Chroma doesn't support transactions, there needs to be a good way to report partial failures.
How does this interface feel?
records: (Iterator[ID], Iterator[Document], Iterator[Embedding])

# .batch_add() requires IDs to be specified
for ingested_ids in collection.batch_add(records):
  user_db.documents.update(ingested_ids, ingested=True)

This also lends itself to being wrapped with tqdm/rich.track.

could we call upsert instead so that the client doesn't need to know about any of it's db internals?

could we call upsert instead so that the client doesn't need to know about any of its db internals? Maybe we want to change upsert to return some indication of what was changed and what wasn't?

by that do you mean something like this?
result = collection.upsert(ids=ids, documents=documents)

user_db.documents.update(result["successful_ids"], ingested=True)
user_db.documents.update(result["failed_ids"], ingested=True)

?
I don't like this as much for a few reasons:

there's no way for a user to know the state of the operation (is it 50% done yet?)

could be fixed by adding a parameter to print a progress bar, but there's not an elegant way to inform of progress programmatically

similar to above, users can't update external state during the operation

In other words, imagine a scenario where the operation on Chroma succeeds but their application database goes down sometime during the operation and so the user_db.documents.update() call after upsert() fails. With the original API proposed, they would have been able to save their progress to their database until it became unavailable and resume from that point. With this alternative, they would have to redo the entire operation.

changes the existing semantics of upsert(): users currently expect that it raises errors

No I mean underneath batch_add we call upsert ourselves. This will be idempotent for any existing IDs, so a restart won't cause duplicates.

oh, so something like
records: (Iterator[ID], Iterator[Document], Iterator[Embedding])

# .batch_upsert() requires IDs to be specified
for ingested_ids in collection.batch_upsert(records):
  user_db.documents.update(ingested_ids, ingested=True) # optional, can use to avoid repeating work

?
that makes sense to me

something like that yeah

I started implementing the proposed API above, but after playing around with it I think it adds some cognitive overhead for not much benefit (when should I call batch_upsert() instead of upsert()? can I batch things myself for more control?).
As a client-only feature I'm not really convinced that this approach is better over improving the existing batch utilities. Both approaches end up with roughly the same number of LoC from the user's perspective, but packaging it as a utility for now makes it easier to understand imo.

I don't think I agree. To use the batching utils a user has to, in addition to the regular code:
    from chromadb.utils.batch_utils import create_batches

...

    for (ids, embeddings) in create_batches(client, (ids, embeddings), print_progress_description="Adding documents..."):
        collection.add(ids=ids, embeddings=embeddings)
    ```

which is much more confusing. My ideal API for this feature is that it's completely transparent to the user, i.e. they never have to think of the difference between `add` and adding as a batch. We decide for them when we should batch and display a progress bar (e.g. if we are over some specific number of elements being added) of the batch progress behind the scenes.

So they would never call `batch_upsert` or `batch_add`. They would just call `add` or `upsert` and we do the right thing for them behind the scenes, without any additional imports or reasoning necessary. If a user wanted to control batching, we could provide an additional argument on `add` which might control the batch size.

Because Chroma doesn't support transactions, automatically batching would raise the same issues I noted here: https://github.com/chroma-core/chroma/issues/2282#issuecomment-2263927583. How do we report a partially succeeded state?
It could work if we ignored collection.add() (since it's not idempotent) and changed the interface of collection.upsert() to be def upsert(...) -> Iterator[List[ID]], but I'm not entirely convinced that's the best option since the return signature is so different from the rest of the methods (and perhaps the user's expectations).
collection.delete() also needs to be batched. Would we also change the return signature there?

In the case of a partially failed batch, the simplest thing to do would be assume the user would run the same operation again; in the case of .add, IDs that were alread added will fail silently, in case of upsert they would be updated but the result for the user is the same, then any IDs which did not succeed in the same batch will be added.

In the case of a partially failed batch, the simplest thing to do would be assume the user would run the same operation again; in the case of .add, IDs that were alread added will fail silently, in case of upsert they would be updated but the result for the user is the same, then any IDs which did not succeed in the same batch will be added.
I don't think this requires changing the return signature.

I guess maybe the answer is that if users want to get intermediate results/track progress they can manually batch themselves.

We then display a progress bar if we go into batching for them.

I'm wary of always doing this by default as it's probably not desired if you're running a production app, maybe we only display a progress bar if it's an interactive terminal?

What do you think about doing both automatic batching and providing a batch utility for users who want more control?

The thing we're trying to help / solve for users is that one of the first things they want to do is load a bunch of data into Chroma, and making that experience better (as per the issue description).
I think the feature where users track progress themselves using e.g. an iterator is not as important right now as making it more efficient to upload a bunch of data by not causing hard swapping if / when we can avoid it, and showing users a progress bar.
Could we condition the progress bar on something like log level? Then production users can turn it off if they don't want it.

Providing a batching utility might be nice for users who do want more control themselves, but my aim with this feature is for the default experience to be much better.

The thing we're trying to help / solve for users is that one of the first things they want to do is load a bunch of data into Chroma, and making that experience better (as per the issue description).

👍

Could we condition the progress bar on something like log level? Then production users can turn it off if they don't want it.

Yeah, I think going on whether the terminal is interactive or you're in a notebook is probably a good check; unless you see a scenario where that doesn't work. I'm still wary of taking over their terminal by default--I can't think of another package that does this--but I agree with the mission of making the ingest experience better.

How do you mean 'take over the terminal' ? How is this different to regular log output except that if written to a file it looks weird?

How do you mean 'take over the terminal' ?

e.x. if you print something else during the operation the output isn't great:
https://github.com/user-attachments/assets/38580a69-1725-474e-ac45-b4499ac3f9bb
(This is with tqdm, which is actually a much better experience than what I'm used to from Node.js where printing to the console during a spinner like ora tends to break everything.)

rich handles this better:
https://github.com/user-attachments/assets/ff43644b-05ec-4171-b944-89bb6e7b26b0

rich looks OK to me

@HammadB had some similar concerns about printing progress by default and transparently batching since the resulting guarantees may be different.
How does this API feel? (This is basically what I had proposed before; my concern before was that having a separately-exported batch util was simpler but I've been convinced that's not true.)
for ingested_set in collection.batch_upsert(ids=ids, embeddings=embeddings, print_progress=True):
  user_db.update(ids=ingested_set, ingested=True)

Easy to copy & embed, no extra imports, makes the progress printing behavior explicit, and allows users to update external state during the operation if they wish.

Discussed offline;

will implement this as batch_upsert/ batch_add for now, punting on what to do with auto-batching for add.
we can hoist this to be the default way to add data to chroma when you add for the first time in our getting started docs.
we can make print_progress=True part of the copy/paste code examples in the docs for beginners to get it by 'default'
we'll look into what a sensible default here is; remembering that the point of this feature is to avoid developers having a bad first experience where they ingest a bunch of data and chroma appears to be much slower than we really are

authors: atroyn codetheweb

repo: chroma-core/chroma


text:
[ENH] Add Embedding Function - Universal Sentence Encoder

Description of changes
Summarize the changes made by this PR.

New functionality

Added USE Embedding Function

Test plan
How are these changes tested?

[x] Tests pass locally with pytest for python

@atroyn  I have created a PR for the same: https://github.com/chroma-core/docs/pull/219

@atroyn @beggers Kindly review the changes requested.

@csbasil happy to land this once requested changes are made to the docs: https://github.com/chroma-core/docs/pull/219

@atroyn I have made requested docs changes. Kindly have a look

Our underlying impl has changed and so this PR is not landable as is.
That being said - we'd still like to add this functionality and that is now tracked in this issue.

authors: atroyn csbasil jeffchuber


text:
'DOM.scrollIntoViewIfNeeded' wasn't found

What versions are you running?
$ go list -m github.com/chromedp/chromedp
github.com/chromedp/chromedp v0.7.4
$ google-chrome --version
Chromium 75.0.3770.142
$ go version
go version go1.16.6 windows/amd64

What did you do? Include clear steps.
Hello everyone, I have a problem with chromedp
I try to access to a web page thanks test and I got the error : 'DOM.scrollIntoViewIfNeeded' wasn't found (-32601)
My code :
// Emulate a mobile
err := chromedp.Emulate(device.IPhoneX).Do(c)
if err != nil {
   return err
}

// Go to register endpoint
err = chromedp.Navigate(REGISTER_ENDPOINT).Do(c)
if err != nil {
   return err
}

// Wait the cookie modal
chromedp.WaitVisible(COOKIE_BTN_SELECTOR).Do(c)
if err != nil {
   return err
}

// Accept cookies
err = chromedp.Click(COOKIE_BTN_SELECTOR).Do(c)
if err != nil {
   return err
}

I have update the dependencies and after that, my code return me this error, it worked before that.
The error appear when I run the "accept cookies" phase
What did you expect to see?
No error, like before
What did you see instead?
An error 'DOM.scrollIntoViewIfNeeded' wasn't found
Thanks for your help
Have a good day

I have try to use scrollIntoViewIfNeeded func in a page with my version of Chromium and that work
A example to show it work :

Please upgrade your chromium. DOM.scrollIntoViewIfNeeded is a CDP command. It is needed in chromedp v0.7.4. Sorry that when I used it, I did not check which version of chromium started to support it, and failed to mention it in the release notes.

Just read https://github.com/chromedp/chromedp/issues/877#issuecomment-881875183. IIRC, chromedp.Flag("enable-automation", false) should work in a  recent version of chromium. Please have a try and let me know the result. Thank you!

Hello @ZekeLu
I have installed the version 91.0.* version of chromium
The enable-automation didn't work :

Google use the window.navigator.webdriver value to identify when the browser is controlled
Here the documentation of this :
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/webdriver
That work in the 75.0.* version
Do you know why ?
Have a good day and thanks you for your quick reply

@FournyP I have searched the commit history of chromium, and I have a bad news. window.navigator.webdriver is set to true if any of the following switches is contained in the command line since 79.0.3922.0:

enable-automation
headless
remote-debugging-pipe
remote-debugging-port (or remote-debugging-port=0 since 86.0.4199.0)

And DOM.scrollIntoViewIfNeeded is added in 82.0.4056.0. So there is not an easy way to workaround the issue.
Here are the references:

Additional switches to set EnableAutomationControlled: https://github.com/chromium/chromium/commit/a6e3413f883eec39b987612737aa8250957a80e3
Leave navigator.webdriver undefined when attaching remote debugger: https://github.com/chromium/chromium/commit/c0a619c06981df4f8d6b7c7bf4c9014613ecb668
DevTools protocol: introduce DOM.scrollIntoViewIfNeeded: https://github.com/chromium/chromium/commit/9a0d32249c8289b22e6f80813dbf1478e1fb09bf

So after 86.0.4199.0, we have to set the following flags to make window.navigator.webdriver be false:
// Set enable-automation to false alone is not enough to make
// `window.navigator.webdriver` be false since 79.0.3922.0.
// Headless mode should be disabled too, which is not acceptable
// for automation in my opinion.
opts := append(chromedp.DefaultExecAllocatorOptions[:],
	chromedp.Flag("enable-automation", false),
	chromedp.Flag("headless", false),
	// any port other than "0" will work since 86.0.4199.0
	chromedp.Flag("remote-debugging-port", "9222"),
)

A better workaround is suggested by @pmurley in https://github.com/chromedp/chromedp/issues/557#issuecomment-575727046.

@ZekeLu
No problem, thank you for your reply
Have a good day

when I sign in to my google account at https://accounts.google.com
I use flags
opts := append(chromedp.DefaultExecAllocatorOptions[:],
chromedp.Flag("headless", false),
chromedp.Flag("enable-automation", false),
chromedp.Flag("remote-debugging-port", "9222"),
)
then you can log in, without being warned that the browser is not secure.
Currently, I want to put it on the server to run, but I can't use flag
chromedp.Flag("headless", true)
how do i get it running on the server without chrome?
help me @ZekeLu

authors: FournyP ZekeLu dactoankmapydev

repo: chromedp/chromedp


text:
Any thoughts about error handling

Hey @chronark
Since there have been two tinybird ingest outages within the last month. (Feb 10 and March 9)
Any thoughts how you are currently handling failed tinybird requests?
Was thinking to add error handling and retries to my implementation along the lines of this here:
https://www.tinybird.co/docs/guides/ingest-from-the-events-api.html#error-handling-and-retries
How are you doing it at unkey?

It retries once already, but only on 429 errors. We can improve that, but I don't see a good solution for buffering long outages within this lib.
We're going to buffer and batch all messages in a cloudflare queue soon (similar to what we do for axiom logs already)

Nice! Would love to learn more about this when you release it for unkey

authors: chronark mfts

repo: chronark/zod-bird


text:
Document architectural options for interoperability infrastructure middleware

Can we use HAPI server as first iteration on facade server?
Do we try to modify existing app server?

Added architecture folder https://drive.google.com/drive/folders/1ZSmfKgVKkpk-v7WUiEAu7FjE2ufQ5vuf?usp=sharing

authors: kbertodatti swmuir

repo: chronic-care/mcc-project


text:
🛑 chronwire is down

In d443611, chronwire (https://chronwire.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: chronwire is back up in 0014796.

repo: chronwire/chronwire-upptime


text:
PowerShell cmdlets error on initial Database Migration creation

The following PowerShell cmdlet, executed in the Package Manager Console of Visual Studio 2017 Enterprise (15.2.26430.14) with the Default Project: dropdown listbox set to Scheduler.API causes an error:
Add-Migration -Name Initial -Project Scheduler.API

Startup project 'Scheduler.Model' targets framework '.NETStandard'. This framework is not intended for execution and may fail to resolve runtime dependencies. If so, select a different startup project and try again.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.EntityFrameworkCore.Design, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'Microsoft.EntityFrameworkCore.Design, Culture=neutral, PublicKeyToken=null'
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.Assembly.Load(AssemblyName assemblyRef)
at Microsoft.EntityFrameworkCore.Tools.ReflectionOperationExecutor..ctor(String assembly, String startupAssembly, String projectDir, String contentRootPath, String dataDirectory, String rootNamespace, String environment)
I have updated all NuGet packages in all 3 projects to the latest editions (July 1, 2017).

@fmorriso  simply try to cd to path of the Scheduler.API project and run the following commands:

Add-Migration Initial
Update-Database

authors: chsakell fmorriso

repo: chsakell/dotnetcore-entityframework-api


text:
[🚀] Change issue template to what I would use

🚀 Feature Request
Generally, the issue templates are quite general now.
Think about and implement issue templates I would use in projects

Superseded by #10


text:
One line weather ouputs 2 lines

So I request for one line weather, it works but it also needs another empty line. I was using in a python program and assumed it was my issue but I tried it in in Insomnia and it outputs and extra empty line. Is it my issue or why does it do that?
I was able to remove the extra line using .strip()  I'm just curious.
https://wttr.in/London?format=3&T

Closed because I can just use .strip()

you can use the %-notation format:
curl wttr.in/Nice?format=%C+%t


text:
Added documentation

Added documentation that mentions you can install through bower.

Thanks for adding this!

authors: chuckcarpenter hitautodestruct

repo: chuckcarpenter/REM-unit-polyfill


text:
BUG - Component does not refresh when added outside of a form and moved in

Add the QR component to a blank screen
Add a form component
Drag the QR component into the form
Message is still shown - Form components need to be wrapped in a form

A refresh of the screen does work.

This should be fixed in the new release!

authors: chungchunwang melohagan

repo: chungchunwang/Budibase-QR-Code-Scanner