"pipx install" fails if PIP_USER env var is set

I have PIP_USER=1 environment variable set, which basically makes every pip command behave like --user was passed.
This messes up pipx:
$ pipx install cowsay
Could not find package cowsay. Is the name correct?

Using pip's isolated mode switch (e.g pipx install --pip-args=--isolated cowsay) works.

Thanks for reporting!
What do you think a good fix would be here? For pipx to test if PIP_USER is set to 1 and exit with an error message?

I think using pip's --isolated switch by default would be best. It might break some existing installs for people who rely on their semi-global pip settings. Maybe it should be added as a config-file option?
Just checking PIP_USER doesn't seem fool-proof: you can add any parameter to pip with environment variables, and 3 different config files, and a lot of them can break things in subtle ways

I also hit this issue when installing and using pipx for the first time (but it wasn't obvious that this was the case)
I have the following in my  .config/pip/pip.conf
[install]
user = true

Which meant that installing gives the following not very informative error:
$ pipx install cowsay
Internal error with venv metadata inspection.

Unable to install cowsay.
Check the name or spec for errors, and verify that it can be installed with pip.

With the --verbose flag:
 pipx install cowsay --verbose
pipx > (package_name_from_spec:216): Determined package name: cowsay
pipx > (package_name_from_spec:217): Package name determined in 0.0s
pipx > (run_subprocess:112): running /usr/bin/python3 -m venv --without-pip /home/markhyde/.local/pipx/venvs/cowsay
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python -c import sysconfig; print(sysconfig.get_path('purelib'))
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/shared/bin/python -c import sysconfig; print(sysconfig.get_path('purelib'))
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python --version
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python -m pip install cowsay
Looking in indexes: https://pypi.org/simple, https://pypi.raxent.com/simple/, https://artifacts.rackspace.net/artifactory/api/pypi/pypi/simple
Collecting cowsay
  Using cached https://files.pythonhosted.org/packages/d4/68/af23fbf90493044fc2ea83cd62923b9952c2d38eeeab83e0c016706bfbc8/cowsay-2.0.3-py2.py3-none-any.whl
Installing collected packages: cowsay
Successfully installed cowsay-2.0.3
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python -c <contents of venv_metadata_inspector.py> cowsay /home/markhyde/.local/pipx/venvs/cowsay/bin
pipx > (get_venv_metadata_for_package:266): Internal error with venv metadata inspection.
pipx > (get_venv_metadata_for_package:267): venv_metadata_inspector.py Traceback:
Traceback (most recent call last):
  File "<string>", line 162, in <module>
  File "<string>", line 123, in main
  File "<string>", line 40, in get_apps
  File "/home/markhyde/.local/pipx/shared/lib/python3.8/site-packages/pkg_resources/__init__.py", line 481, in get_distribution
    dist = get_provider(dist)
  File "/home/markhyde/.local/pipx/shared/lib/python3.8/site-packages/pkg_resources/__init__.py", line 357, in get_provider
    return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
  File "/home/markhyde/.local/pipx/shared/lib/python3.8/site-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/home/markhyde/.local/pipx/shared/lib/python3.8/site-packages/pkg_resources/__init__.py", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'cowsay' distribution was not found and is required by the application

pipx > (rmdir:18): removing directory /home/markhyde/.local/pipx/venvs/cowsay
Unable to install cowsay.
Check the name or spec for errors, and verify that it can be installed with pip.

I couldn't find any reference to the error until I found this issue, so I've added my outputs so that hopefully others would also find the workaround given by @indivisible
$ pipx install cowsay --pip-args=--isolated --verbose
pipx > (package_name_from_spec:216): Determined package name: cowsay
pipx > (package_name_from_spec:217): Package name determined in 0.0s
pipx > (run_subprocess:112): running /usr/bin/python3 -m venv --without-pip /home/markhyde/.local/pipx/venvs/cowsay
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python -c import sysconfig; print(sysconfig.get_path('purelib'))
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/shared/bin/python -c import sysconfig; print(sysconfig.get_path('purelib'))
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python --version
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python -m pip install --isolated cowsay
Collecting cowsay
  Using cached https://files.pythonhosted.org/packages/d4/68/af23fbf90493044fc2ea83cd62923b9952c2d38eeeab83e0c016706bfbc8/cowsay-2.0.3-py2.py3-none-any.whl
Installing collected packages: cowsay
Successfully installed cowsay-2.0.3
WARNING: You are using pip version 19.3.1; however, version 20.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python -c <contents of venv_metadata_inspector.py> cowsay /home/markhyde/.local/pipx/venvs/cowsay/bin
pipx > (_symlink_package_apps:108): ⚠  Note: cowsay was already on your PATH at /usr/bin/cowsay
pipx > (needs_upgrade:51): Time since last upgrade of shared libs, in seconds: 4901.842814683914. Upgrade will be run by pipx if greater than 2592000.0.
  installed package cowsay 2.0.3, Python 3.8.3
  These apps are now globally available
    - cowsay
done! ✨ 🌟 ✨

An alternative to --pip-args=--isolated appears to be to set PIP_USER=0 prior to the command:
$ PIP_USER=0 pipx install cowsay --verbose
pipx > (package_name_from_spec:216): Determined package name: cowsay
pipx > (package_name_from_spec:217): Package name determined in 0.0s
pipx > (run_subprocess:112): running /usr/bin/python3 -m venv --without-pip /home/markhyde/.local/pipx/venvs/cowsay
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python -c import sysconfig; print(sysconfig.get_path('purelib'))
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/shared/bin/python -c import sysconfig; print(sysconfig.get_path('purelib'))
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python --version
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python -m pip install cowsay
Looking in indexes: https://pypi.org/simple, https://pypi.raxent.com/simple/, https://artifacts.rackspace.net/artifactory/api/pypi/pypi/simple
Collecting cowsay
  Using cached https://files.pythonhosted.org/packages/d4/68/af23fbf90493044fc2ea83cd62923b9952c2d38eeeab83e0c016706bfbc8/cowsay-2.0.3-py2.py3-none-any.whl
Installing collected packages: cowsay
Successfully installed cowsay-2.0.3
pipx > (run_subprocess:112): running /home/markhyde/.local/pipx/venvs/cowsay/bin/python -c <contents of venv_metadata_inspector.py> cowsay /home/markhyde/.local/pipx/venvs/cowsay/bin
pipx > (_symlink_package_apps:108): ⚠  Note: cowsay was already on your PATH at /usr/bin/cowsay
pipx > (needs_upgrade:51): Time since last upgrade of shared libs, in seconds: 5008.219198703766. Upgrade will be run by pipx if greater than 2592000.0.
  installed package cowsay 2.0.3, Python 3.8.3
  These apps are now globally available
    - cowsay
done! ✨ 🌟 ✨

So a reasonable workaround for me is to set alias pipx='PIP_USER=0 pipx in my .bashrc

Thanks for the helpful investigation @mark-hyde , and the extra ping on this issue.
I think we need to address this.  Using --isolated might be a blunt instrument, because it ignores all of the user's pip config.  There are some options that might be useful to get from the user's config, for example proxy.
Since I don't see a specific pip command-line option that only nullifies --user, the easiest course for pipx might be to inject PIP_USER=0 into the env of the pip install command.


Database aliases are added to the INSERT statement.

Explain your user case and expected results
Database aliases are added to the INSERT statement.

https://github.com/go-gorm/gorm/issues/5357#issuecomment-1133547877


docs: document configuring multiple release branches

Towards #244

@OrenMe don't suppose you'd be willing to try these docs out, and see if it work for your patch based workflow?

@bcoe This looks good, but it also requires to have some prior knowledge of the branch prefix.
What if I have 1.2.0 released and I now add a few features and fixes to the main branch so my next version is 1.3.0.
If AI now need to release a patch I need to have the default-branch be set to 1.2.x
And if I have monthly releases so next month I'll need to patch it to be 1.3.x
Maybe add it with a branch name regex so it can be done dynamically?
If I open patch/1.3.x then it resolves against the latest 1.3.x tag available for the change list resolving.
I also tested this and it acts funny with the main branch PR that release-please opens.
It looks like you need to first close the open PR against the default-branch if it is already opened(which most likely it is)

I also tested this and it acts funny with the main branch PR that release-please opens.

@OrenMe what behavior happened?

@bcoe it reused the same PR that was already opened for the main branch and iirc it was kind of messed up in commit order as it didn't take it cleanly from the new patch branch.
I think it can be better if new target branch PRs be separate and not reuse a single PR across targets.

@OrenMe I think this is an issue @chingor13 brought up with me already, which happens if the alternate branch and the current branch share the same version range.
The plan to solve the problem is to move to a new branch naming format, which includes the name of the target branch.

Thanks @bcoe, sounds like that will do the trick.
Is there a tracking issue on this I can subscribe to?


add zabbix item for inter ssl check

add zabbix item for inter ssl check
add avg trigger for inter ssl check
add cron job for inter ssl check

@drewandersonnz has +1 on #3996


Use BaseSamplerV1 with explicit version

This change is motivated by the following warning under the Qiskit 1.2 rc:

DeprecationWarning: The class qiskit.primitives.base.base_sampler.BaseSampler is deprecated as of qiskit 1.2. It will be removed no earlier than 3 months after the release date. The BaseSampler class is a type alias for the BaseSamplerV1 interface that has been deprecated in favor of explicitly versioned interface classes. It is recommended to migrate all implementations to use BaseSamplerV2. However, for implementations incompatible with BaseSamplerV2, BaseSampler can be replaced with the explicitly versioned BaseSamplerV1 class.

Related to #551 and #506.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
2410

Relevant Lines:
2410

💛  - Coveralls


is there a way to define different cs for different projects of the same filetype?

In some projects I use psr2 and in some wpcs (WordPress). Filetype for both is .php.
phpcs provides both psr2 and wpcs, what are my options for syntastic to differentiate between these two?
I've seen this issue #1180

Set b:syntastic_php_phpcs_args from autocmds on BufRead matching your projects.  Not exactly painless, but that's the Vim way of doing it. shrug

What do you mean by "not exactly painless" ?

Do you enjoy writing autocmds?  Personally, I don't.


[YUNIKORN-2651]Update the unchecked error for make lint warnings

What is this PR for?
There are many different errors  or warnings for make lint.
This PR tries to solve the unchecked error which relates to 5 files,  goconst error and unused error in yunikorn-k8shim repo.

There are 11 errcheck looks like below:
pkg/admission/conf/am_conf.go:121:39: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandler is not checked (errcheck)
configMaps.Informer().AddEventHandler(&configMapUpdateHandler{conf: acc})
^
pkg/admission/namespace_cache.go:61:40: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandler is not checked (errcheck)
namespaces.Informer().AddEventHandler(&namespaceUpdateHandler{cache: nsc})
^
pkg/admission/priority_class_cache.go:44:45: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandler is not checked (errcheck)
priorityClasses.Informer().AddEventHandler(&priorityClassUpdateHandler{cache: pcc})
^
test/e2e/framework/helpers/k8s/k8s_utils.go:719:46: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandler is not checked (errcheck)
configMapInformer.Informer().AddEventHandler(eventHandler)
^
pkg/client/apifactory.go:177:35: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandlerWithResyncPeriod is not checked (errcheck)
AddEventHandlerWithResyncPeriod(handler, resyncPeriod)
^
pkg/client/apifactory.go:180:35: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandlerWithResyncPeriod is not checked (errcheck)
AddEventHandlerWithResyncPeriod(handler, resyncPeriod)
^
pkg/client/apifactory.go:183:35: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandlerWithResyncPeriod is not checked (errcheck)
AddEventHandlerWithResyncPeriod(handler, resyncPeriod)
^
pkg/client/apifactory.go:186:35: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandlerWithResyncPeriod is not checked (errcheck)
AddEventHandlerWithResyncPeriod(handler, resyncPeriod)
^
pkg/client/apifactory.go:189:35: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandlerWithResyncPeriod is not checked (errcheck)
AddEventHandlerWithResyncPeriod(handler, resyncPeriod)
^
pkg/client/apifactory.go:192:35: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandlerWithResyncPeriod is not checked (errcheck)
AddEventHandlerWithResyncPeriod(handler, resyncPeriod)
^
pkg/client/apifactory.go:195:35: Error return value of (k8s.io/client-go/tools/cache.SharedInformer).AddEventHandlerWithResyncPeriod is not checked (errcheck)
AddEventHandlerWithResyncPeriod(handler, resyncPeriod)
^

There are 4 goconst errors as below:
pkg/common/si_helper_test.go:71:13: string pod-resource-test-00001 has 3 occurrences, make it a constant (goconst)
podName := "pod-resource-test-00001"
^
pkg/common/si_helper_test.go:72:15: string important has 3 occurrences, make it a constant (goconst)
namespace := "important"
^
pkg/cache/application_test.go:562:13: string task02 has 3 occurrences, make it a constant (goconst)
taskID2 := "task02"
^
pkg/shim/scheduler_test.go:42:16: string `
partitions:

name: default
queues:

name: root
submitacl: "*"
queues:

name: a
resources:
guaranteed:
memory: 100000000
vcore: 10
max:
memory: 150000000
vcore: 20
has 3 occurrences, make it a constant (goconst) configData :=
^

There is 1 unused error as below :
pkg/shim/scheduler_mock_test.go:165:26: func (*MockScheduler).removeApplication is unused (unused)
func (fc *MockScheduler) removeApplication(appId string) error {
^

Actions:

log out the errors for these 11 unchecked errors in 5 files.
When the error exists for RegisterHandler and NewNamespaceCache, this error should be viewed as fatal, pass the error message back to main(), and we should propagate it to stop k8shime. At same time, update the unit test for NewNamespaceCache func.
add min-occurrences = 5 in .golangci.yml file to increase the threshold
delete the function func (fc *MockScheduler) removeApplication(appId string) error{}

What type of PR is it?

[x] - Bug Fix
[ ] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2651
How should this be tested?
It should pass all CI test.
make test passed locally.
Screenshots (if appropriate)

Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

@SophieTech88 Could you please propagate the error by AddSchedulingEventHandlers?
https://github.com/apache/yunikorn-k8shim/blob/58adfe941d2d8dae5544af8b49e435f304678807/pkg/cache/context.go#L114
By that change We can handle the error in the main function

@SophieTech88 Could you please propagate the error by AddSchedulingEventHandlers?
https://github.com/apache/yunikorn-k8shim/blob/58adfe941d2d8dae5544af8b49e435f304678807/pkg/cache/context.go#L114
By that change We can handle the error in the main function
Many thanks for your suggestion. It is a good catch. The function AddSchedulingEventHandlers is also affected by AddEventHandler, so when AddEventHandler returns error, the function AddSchedulingEventHandlers should pass the error back, too.

But I see AddSchedulingEventHandlers is not called in main(). It works during the process for func InitializeState(). And when I trace back, the error propagate track looks like AddEventHandler() ->> func (ctx *Context) AddSchedulingEventHandlers() error {} ->> func (ctx *Context) InitializeState() error {} ->> func (ss *KubernetesShim) initSchedulerState() error {} ->> func (ss *KubernetesShim) Run() error{}
I just update the code to fix the return error in func AddSchedulingEventHandlers. Welcome to any suggestions.


wlr_seat: fix destroy with multiple handles

Need to use for_each_safe because wl_resource_destroy's callback will
remove the handle from the list itself

Thanks!


Remove extraneous GitLab callout

It looks like that text doesn't belong to the GitHub documentation, and we still have separate sections for GitHub and GitLab. 🤔

@0x2b3bfa0 failing tests?

Yes, not sure why: it works on my codespace. 😈

I had to SSH into the CircleCI environment and run prettier there, because running it from GitHub Codespaces said that everything was clean. 🤔

@casperdcl, it's ready for review again.


Plotting a voronoi map over a street map with folium?

  Nice!  I do have a question though: is it possible to have this map drawn in folium, say, with a street map drawn on it?  Then I'd be able (I hope) to replace the data point labels with folium popups or tooltips.  And show the map in its geographic location.
I already have a nice folium map which shows the region and its data points.  So what I want to with it is put a Voronoi map over it (clearly then the colors would have to semi-transparent).  Is this possible?
Thanks!

I have no idea about folium, but since geovoronoi gives you shapely polygons you can do whatever you want with it, including exporting them to GeoJSON (see interoperation) and hence using it with any other GIS software / package.

Thank you very much, internaut - I will check this out in more detail.
In fact, it seems that the command "voronoi_regions_from_coords" gives a dictionary whose values are shapely polygons; so these can be added to a map directly, rather than using the "plot_voronoi_polys_with_points_in_area" function.  The dictionary keys relate to the places in the original geopandas file by the "region_pts" output.
All I have to do now is to work out how to add shapely files to a folium map ... which will require some fiddling.  Thank you again!

Hey @amca01 did you ever manage to get it working? Any pointers, examples or tutorials?


Upstreaming it?

Have you considered making this part of ESPHome itself and create a pull request like the Optolink Team does in https://github.com/esphome/esphome/pull/4453 ?

From my experience, it creates a lot of extra effort to merge a component into esphome (or HomeAssistant) main branch and then maintain it there. Therefore I don't have plans to do this at the moment.

Would be nice to at least get feedback and then decide if it's worth the time right now.

https://esphome.io/components/sml.html is offered upstream, does this differ significantly?

SML and D0 are 2 different communication protocols, but both use OBIS codes.

ah ok, so not synonym and still needed to become mainlined.


Simple copy task fails

I have absolute paths here, a single file and a target directory:
        copy.one(file, destinationDirectory, opts, function(err, file) {
            cb(err, file)
        })

file = /home/michael-heuberger/binarykitchen/code/videomail.io/var/local/tmp/clients/videomail.io/11e6-0555-3e17b940-b805-ef6a2fea069a/videomail_preview.webm
destinationDirectory = /home/michael-heuberger/binarykitchen/code/videomail.io/var/local/uploads/videomail.io/videomail/11e6/05/55/11e6-0555-3e17b940-b805-ef6a2fea069a
but it gets ugly, the video gets copied into
/var/local/uploads/videomail.io/videomail/11e6/05/55/11e6-0555-3e17b940-b805-ef6a2fea069a/var/local/tmp/clients/videomail.io/11e6-0555-3e17b940-b805-ef6a2fea069a/videomail_preview.webm
which is not what i want. probably the cwd is messing here. how can the cwd be ignored, and just copy from an absolute file to an absolute destination directory?

The same happened to me. It seems quite counter-intuitive for a copy function to work this way, especially without mentioning that behavior in the readme.
It looks like you may get around this by using "cwd" in the options object, but since there's no documentation about the available options, I'll just switch to one of the countless alternative modules offering the same functionality.

Exactly!

On the other hand, we cannot blame the maintainers. It is a major sem-version change, so this is justified. Just the documentation could be better ...

sorry for the late reply. I had a funeral this week. this seems like a bug, I'll take a look

changed the title for clarity

Hmm, I've been trying to reproduce this locally but it seems to just work for me - with absolute paths, relative, with and without cwd.
were there any other options set or something else that might give me a hint about where the bug is happening? Or was it just src/dest paths?

The same happened to me. It seems quite counter-intuitive for a copy function to work this way, especially without mentioning that behavior in the readme.

I'm still trying to figure out which part is counter-intuitive. What behavior shouldn't be happening? Sorry if I'm being dense, I really want to fix this.

I'm able to reproduce this when process.cwd is outside of the path being copied:
var copy = require('copy');
var opts = {};

var src = '/Users/doowb/work/jonschlinkert/copy/test/fixtures/a.txt';
var dest = '/Users/doowb/work/jonschlinkert/copy/actual';
console.log(`Copying "${src}" => "${dest}"`);
copy.one(src, dest, opts, function(err) {
  if (err) throw err;
  console.log('done!');
});

When I run this from /Users/doowb/work/jonschlinkert/copy or /Users/doowb/work/jonschlinkert and it works fine.
When I run this from /Users/doowb/work/assemble/assemble-handlebars-helpers (arbitrary path for testing the issue) it writes the file to /Users/doowb/work/jonschlinkert/jonschlinkert/copy/test/fixtures/a.txt.
This is happening because when the src file is loaded using a vinyl object, the .relative property is calculated from the current process.cwd (in this case .relative ends up being ../../jonschlinkert/copy/test/fixtures/a.txt. Then the final destination is calculated using resolve from the destDir to the .relative property resulting in a destination relative to the actual destination.
Using var opts = { flatten: true }; works fine because the basename of the file is used instead of .relative.
I tried out some different methods of trying to figure out the relative path from the specified destination instead of the process.cwd but I haven't managed to get the correct results.

Awesome, thanks @doowb. that helps a lot


Still exceedingly white.

The ui is still super white.

Also true for GitHub.

I think a dark theme option is now there. Is this issue outdated?


Add support for MICROS parquet timestamp encoding

Fixes https://github.com/prestosql/presto/issues/5483

Thanks. Looks good. THe only concern I have is the verbosity of the test. Maybe we have some helpers which could make it more concise ?

@losipiuk imo the test body is not that long, so i guess you're referring to createPageSource method.
this indeed can be simplified using io.prestosql.plugin.hive.benchmark.FileFormat#createFileFormatReader, but this would require https://github.com/prestosql/presto/pull/5283.

Looks good to me. Do you think it would make sense to add an issue for a Spark product test environment to validate problems like that?

The test file was created using pyarrow, per instructions in the issue.

had to add some more testing code, ptal

Thanks. Looks good. THe only concern I have is the verbosity of the test. Maybe we have some helpers which could make it more concise ?

@losipiuk imo the test body is not that long, so i guess you're referring to createPageSource method.
this indeed can be simplified using io.prestosql.plugin.hive.benchmark.FileFormat#createFileFormatReader, but this would require #5283.

I was thinking about testTimestampBackedByInt64. But there is not much generic stuff :/

@electrum @martint
FYI while TimestampMicrosColumnReader was added for Iceberg and i assume it is still used for Iceberg,
i did not add Iceberg-related release notes, because I do not know what is the impact of my change on Iceberg users
(except that, obviously, all existing tests pass)
@electrum @Parth-Brahmbhatt can you please fill this void?
(you were both changing that class with Iceberg in mind)


Fill footer with real authentic data

use our email, GitHub, and LinkedIn info in the footer

CommitID: dae706a solved this issue!


Enabled cohere with header only authentication

Enabled cohere with header only authentication
What this PR does:
Enabled cohere with header only authentication
Checklist

[x] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[x] CLA Signed: DataStax CLA

@maheshrajamani Should this be merged now?


Minor refactor

Coverage remained the same at 100.0% when pulling e305df53811dba048467c53d0a724495a8ce78d0 on @satya164/tweaks into 102e55bd28905f98e82012294229bbb9036d9912 on master.

Coverage remained the same at 100.0% when pulling 081f1c896b2eb3e343888701708b1fb3974cf690 on @satya164/tweaks into 102e55bd28905f98e82012294229bbb9036d9912 on master.

Also, we need to update the API docs to remove onInit from there

Coverage remained the same at 100.0% when pulling 589b7ae6f9dd6b3e4f50b282c30c3b7280018384 on @satya164/tweaks into 102e55bd28905f98e82012294229bbb9036d9912 on master.

@zamotany it's basically the same as when the provider mounts, so seems unnecessary


Replying to Tweet - possible with existing agent?

If supplied with a tweet event payload, is there a way to reply to that tweet?

Not at the moment. It would be a nice addition to the TwitterPublishAgent, the update method from the twitter gem accepts optional arguments. client.update("I'm tweeting with @gem!", in_reply_to_status_id:<PHONE_NUMBER>60019968) would create a reply to that tweet id.

I'll look into updating that agent. I'm teaching a class this week, so it may be a while before I get to it, but I'm happy to contribute that change.
I've been meaning to update the agent chooser (via Select2) I originally contributed to, also. Hey, @knu, is #1802 still a WIP for you, or can I take that on?


Horizontal scrollbar displayed twice in create token screen on mobile browser of guardian

Problem description
Duplicate horizontal scrollbar displayed in create token screen on mobile browser of guardian
Step to reproduce
Steps to reproduce the behavior:
1.Login as SD and navigate to tokens
2. Create one or two tokens
3. Scroll all the way down
4.Horizontal scroll bar is displayed twice at the end of the screen
Expected behavior
Single horizontal scrollbar should be displayed in create token screen
Screenshots

Issue is resolved.


extract-mode example fails to build

Do you want to request a feature, report a bug or ask a question?
Report a bug.
What is the current behavior?
Building the examples failed with an error, Cannot find module 'extract-text-webpack-plugin', in the extract-mode example.
What is the expected behavior?
Building the examples with npm run build:examples should run successfully.
If the current behavior is a bug, please provide the steps to reproduce, at least part of webpack config with loader configuration and piece of your code.
$ node node_modules/webpack/bin/webpack.js --config examples/extract-mode/webpack.config.js
module.js:472
    throw err;
    ^

Error: Cannot find module 'extract-text-webpack-plugin'
    at Function.Module._resolveFilename (module.js:470:15)
    at Function.Module._load (module.js:418:25)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/kyank/code/svg-sprite-loader/examples/extract-mode/webpack.config.js:4:27)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)

Please tell us about your environment:

Node.js version: 7.9.0
webpack version: 3.8.1
svg-sprite-loader version: 3.4.1 (89c0bdd8218ae0a6963eab1c146bf4903afb1ca7)
OS type & version: macOS 10.13 (High Sierra)

Suggestions to fix:
Add extract-text-webpack-plugin as a devDependency?

@sentience try to run
yarn run bootstrap
yarn run env webpack-3

Aha! Did I miss the docs for this, or do they still need to be written? I'd be happy to draft an addition to examples/README.md and submit a PR if that would help.

Actually it's in Setup section of contributing guidelines, but maybe it should be referenced from readme :)

I've added postinstall script which runs yarn run env webpack-3 each time when you install deps. Hope it helps.

I'm now seeing this in a project that depends on svg-sprite-loader master:
❯ yarn
yarn install v1.2.1
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
[1/3] ⠂ fsevents
[2/3] ⠂ node-sass
[3/3] ⠂ svg-sprite-loader: info Visit https://yarnpkg.com/en/docs/cli/run for docum
[-/3] ⠂ waiting...
error /Users/kyank/code/cultureamp-style-guide/node_modules/svg-sprite-loader: Command failed.
Exit code: 1
Command: yarn env webpack-3
Arguments:
Directory: /Users/kyank/code/cultureamp-style-guide/node_modules/svg-sprite-loader
Output:
yarn run v1.2.1
$ node scripts/select-env webpack-3
module.js:529
    throw err;
    ^

Error: Cannot find module 'shelljs'
    at Function.Module._resolveFilename (module.js:527:15)
    at Function.Module._load (module.js:476:23)
    at Module.require (module.js:568:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/kyank/code/cultureamp-style-guide/node_modules/svg-sprite-loader/scripts/select-env.js:3:15)
    at Module._compile (module.js:624:30)
    at Object.Module._extensions..js (module.js:635:10)
    at Module.load (module.js:545:32)
    at tryModuleLoad (module.js:508:12)

How you include sprite-loader in this project? You should use npm link or yarn link

I simply included it as a GitHub dependency in package.json:
  "svg-sprite-loader": "kisenka/svg-sprite-loader#master",

shelljs specified in devDependencies

That explains it, then, right? The new postinstall script is running when the package is installed as a dependency of my project—when the devDependencies are not available.

npm install --ignore-scripts?

I don't think it's reasonable for all projects that use svg-sprite-loader as a dependency to have to specify --ignore-scripts when they npm install.
Because npm postinstall scripts are run both when you npm install the package itself, as well as when you npm install a project that depends on the package, you simply can't rely on devDependencies being present.
From the official docs of NPM scripts, under “best practices":

Don't use install. Use a .gyp file for compilation, and prepublish for anything else. You should almost never have to explicitly set a preinstall or install script. If you are doing this, please consider if there is another option. The only valid use of install or preinstall scripts is for compilation which must be done on the target architecture.

Hmm, could you suggest better solution? I want to always run env script after dependencies changed.

How about if your postinstall script checked for the presence of a devDependency (such as shelljs), and exited silently if it was not present? That way, when the package is installed with devDependencies, the script will run, and when the package is not installed with devDependencies (i.e. as a dependency of a project), then the script would exit harmlessly.

Too complicated :) I'm better remove postinstall script!

Too complicated :) I'm better remove postinstall script!


link behind PAH's logo should be directed to the application's home page

PAH's logo should be directed to the application's home page not to PAH's website.
Redirection to the PAH's can be next to Code For Poznań link at the bottom of the website.

Closed with #100


feat: install crc on windows

This PR add installation of CRC on windows.

Note: This PR bundle crc installer with crc-extension, so installation could be offline.

Demo:
https://user-images.githubusercontent.com/929743/224037074-1357910b-50fb-48f9-91ed-4b83ba70ae0f.mp4

created dist in 1.5s
  • electron-builder  version=23.6.0 os=10.0.19045
  • loaded configuration  file=C:\Users\gbraad\Projects\podman-desktop\.electron-builder.config.cjs
  • description is missed in the package.json  appPackageFile=C:\Users\gbraad\Projects\podman-desktop\package.json
  • author is missed in the package.json  appPackageFile=C:\Users\gbraad\Projects\podman-desktop\package.json
  • skipped dependencies rebuild  reason=npmRebuild is set to false
  • packaging       platform=win32 arch=x64 electron=23.1.3 appOutDir=dist\win-unpacked
  ⨯ remove C:\Users\gbraad\Projects\podman-desktop\dist\win-unpacked\chrome_100_percent.pak: Access is denied.
github.com/develar/go-fs-util.EnsureEmptyDir
        /Volumes/data/go/pkg/mod/github.com/develar/go-fs-util@v0.0.0-20190620175131-69a2d4542206/fs.go:98
github.com/develar/app-builder/pkg/electron.UnpackElectron.func1.1
        /Volumes/data/Documents/app-builder/pkg/electron/electronUnpack.go:38
github.com/develar/app-builder/pkg/util.MapAsyncConcurrency.func2
        /Volumes/data/Documents/app-builder/pkg/util/async.go:68
runtime.goexit
        /usr/local/Cellar/go/1.17/libexec/src/runtime/asm_amd64.s:1581
  ⨯ C:\Users\gbraad\Projects\podman-desktop\node_modules\app-builder-bin\win\x64\app-builder.exe process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1  failedTask=build stackTrace=Error: C:\Users\gbraad\Projects\podman-desktop\node_modules\app-builder-bin\win\x64\app-builder.exe process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1
    at ChildProcess.<anonymous> (C:\Users\gbraad\Projects\podman-desktop\node_modules\builder-util\src\util.ts:250:14)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.cp.emit (C:\Users\gbraad\Projects\podman-desktop\node_modules\cross-spawn\lib\enoent.js:34:29)
    at maybeClose (node:internal/child_process:1091:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

node:internal/process/esm_loader:97
    internalBinding('errors').triggerUncaughtException(
                              ^
1
(Use `node --trace-uncaught ...` to show where the exception was thrown)

Node.js v18.15.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

@evidolob
Let's assume the extension gets enabled from a download. On initialization, it would download the CRC installer, right?
Is it somehow possible to show that as part of the UI, instead of the command line?
This is an improvement... as I am wondering what can be done to make this smoother. Plus, not considering that the extension might get packaged WITH the installer and possible OpenShift bundle.


Manually provide 814.ffmpeg.js's path

Is your feature request related to a problem? Please describe.
I cannot load the module in a Chrome extension scaffolded by Plasmo
The reason is that when FFmpeg loads up, it looks for 814.ffmpeg.js in the same directory as ffmpeg.js, whereas Plasmo, which uses Parcel under the hood, renames the file to include a hash, e.g. 814.ffmpeg.d7h8ng.js
Describe the solution you'd like
Allow manually providing a path to 814.ffmpeg.js
Describe alternatives you've considered
The only alternative is to create an extension without using Plasmo

Hello @avi12
I have met the same issue.
Did you solve this problem ?

@codegod2222 Your best bet is likely to ditch Plasmo for that particular project


Build: Misc fixes to unblock 'fluid-build --all'

Fixes a few nonconformant NPM scripts and a missing package dependency that was preventing 'fluid-build --all' from succeeding:

Removed the '-b' parameter from 'tsc -b'.

The '-b' argument confused Fluid-Build when attempting to find the 'tsc' task.
'composite: true' already specified in the tsconfig.json.

Removed 'npm run clean' from "build" scripts.

Cleaning the build output during build breaks the incremental build heuristics.

'version-tools' used 'ts-node' instead of building './test' directory

Fluid-Build detected that .eslintrc referenced a *.tsconfig file that wasn't built.
Converted 'version-tools' to conform to the './src/test' pattern used by other projects.

Adding missing "copyfiles" dependency

After these changes, I could successfully build with:
git clean -xfd
npm i
fb --all --install
fb --all

Will review more later, but are these warnings that fluid-build spits out or actual build failures? I thought I excluded build-tools from the fluid-build script policies because some shouldn't apply, and people keep complaining about seeing warnings.

The more I think about it, the more I want fluid-build to know nothing of build-tools. I added it to make it easier to test the release group logic, but with the azure release group there's another place to test stuff outside client. Increasingly I want to be able to go "off the beaten path" with build-tools (for example, using pnpm workspaces until our full-repo infra upgrade is done) and fluid-build makes that difficult.

Are these warnings that fluid-build spits out or actual build failures?

Unfortunately, these are failures that are impacting our external contributors (here).
(Except for removing the unnecessary eslint suppressions...  that was just low hanging fruit.)

@tylerbutler - Have a look at my latest iteration which preserves your desired workflow.  If you're still unconvinced, let's talk.

Can you make the same change in the version-tools package?

Sorry I missed that.  Fixed and verified that '/bin/dev' works there as well.


modified Install subcommand

Added progression bar,
Added time wait status check for all kubearmor-app pods,
Added execution time counter,
Added cursor animation,
Added emojis.

@daemon1024 , @Ankurk99 , if someone is using kubearmor-client APIs (such as kubearmor ginkgo framework) then this animation should not be used .. right?


feat: Added name_only, names_only functions

fix: Fixed handling of keyword/default argument edge-case parsing for the multiple function definition syntaxes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

47 of 50 (94.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.5%) to 84.176%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parsing/expr_types.jl
0
1
0.0%

src/parsing/macrocall.jl
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/parsing/funcs.jl
1
81.94%

Totals

Change from base Build<PHONE_NUMBER>:
0.5%

Covered Lines:
633

Relevant Lines:
752

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

47 of 50 (94.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.5%) to 84.176%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parsing/expr_types.jl
0
1
0.0%

src/parsing/macrocall.jl
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/parsing/funcs.jl
1
81.94%

Totals

Change from base Build<PHONE_NUMBER>:
0.5%

Covered Lines:
633

Relevant Lines:
752

💛  - Coveralls


Broken text rendering

Lagrange sometimes fails at rendering text (missing characters and lines out of place; see images) in the main text display, side interfaces, and context menus.
This is somehow dependent on text scaling: text rendering frequently breaks down or fixes itself when zoom-level is changed.
Things I have tried that don't fix it:

changing the font
enabling "monospace body"
changing line width
disabling "wrap plain text"

This happens on Lagrange 1.5.2, installed on Windows 7 from lagrange_v1.5.2_windows-x64_setup.exe.

This is a bug in the text renderer’s font glyph cache. I have seen it occasionally myself, but perhaps because I tend to restart the app frequently, It’s happening rarely for me.
This does need fixing. I’ll see if it can be reproduced more easily by reducing the cache size.

So far I've been unable to reproduce this issue. Are there any usage patterns that you can identify where the issue would start occurring?

Starting Lagrange again (after a while of inactivity and changing the colour scheme to light), there were no rendering issues at all, until I changed the zoom/scaling by a few scroll-units. After that, some further rescaling sometimes returned rendering to correctness, and sometimes back to chaos.
tl;dr Issue is triggered for me by changing page scale

Thanks, that should help with debugging this!

v1.6 makes a number of changes in text rendering so this issue may already be fixed. However, I haven't found a way to reliably reproduce the problem.

I am assuming the issue has been fixed in v1.6 after the introduction of HarfBuzz and other text rendering changes.


Add :reason step to ManageConsent journey

Penultimate step before the Health Questions page which is more complex and should be PRed on its own.

:shipit:


nixos/plasma5: default runUsingSystemd to on

Description of changes
Upstream switched as of 5.25. We should too.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg eval
hello?

The ofborg-internal-error is a label for the ofborg operators. If it gets attached just restart ofborg evaluation. Otherwise please ignore it.

How about just dropping it? It's the officially supported way to launch KDE session now.

I was thinking about it, but the old way is still available upstream, so maybe we should keep it for a bit.

Fair enough. Been running this for ages too, so let's get it going!

Thank you for leaving this option in. I run KDE with i3 as window manager, and this seems to no longer be supported when this option is turned on.
The specifics of this features is that you can export KDEWM=${pkgs.i3}/bin/i3 in a script for /share/xsessions/my-session.desktop. This gives the beautiful combination of having KDE as desktop manager, but i3 as window manager.

The correct way to do that now would be to just mask out the kwin service and add a new one to start i3.

Additionally, just like the focus going forward is Plasma Wayland and Plasma X11 getting less and less attention, having systemd launch the session will in all likelihood be the better experience.

Thanks, I could look into doing that at some point.
Perhaps it would be nice to have some NixOS options to properly start a plasma5+i3 session, that would also mask the kwin service.
On Wayland, plama5+I3 (or sway) is not a thing AFAIK. I wonder what path that is going to go down in the future. For now I'll stay on X11.

Perhaps it would be nice to have some NixOS options to properly start a plasma5+i3 session, that would also mask the kwin service.
Sure, entirely doable although the issue is finding somebody wanting to work on it. If you feel like giving it go, ping me in the PR - I'll happily review it.


Latest iOS device resolutions are missing

The issue
The ViewImageConfig struct should include static functions for all the latest devices.
I checked main, and they're not there either. (Note that struct is defined in a file named View.swift for some reason.)
Environment

swift-snapshot-testing version [e.g. 1.9.0]
Xcode [e.g. 13.3] (but it doesn't matter)

Workaround
I added the following extension in my project, but I only need portrait, not landscape, so I didn't test for those safe area values. I would probably have created a PR, but there are already so many. I figured maybe this would help someone else looking for these.
extension ViewImageConfig {

    public static let iPhone13 = ViewImageConfig.iPhone13(.portrait)

    public static func iPhone13(_ orientation: Orientation) -> ViewImageConfig {
        let safeArea: UIEdgeInsets
        let size: CGSize
        switch orientation {
        case .landscape:
            // warning: unverified (unused) values
            safeArea = .init(top: 0, left: 44, bottom: 24, right: 44)
            size = .init(width: 844, height: 390)
        case .portrait:
            safeArea = .init(top: 47, left: 0, bottom: 34, right: 0)
            size = .init(width: 390, height: 844)
        }
        return .init(safeArea: safeArea, size: size, traits: .iPhoneX(orientation))
    }

    public static let iPhone13Mini = ViewImageConfig.iPhone13Mini(.portrait)

    public static func iPhone13Mini(_ orientation: Orientation) -> ViewImageConfig {
        let safeArea: UIEdgeInsets
        let size: CGSize
        switch orientation {
        case .landscape:
            // warning: unverified (unused) values
            safeArea = .init(top: 0, left: 44, bottom: 24, right: 44)
            size = .init(width: 812, height: 375)
        case .portrait:
            safeArea = .init(top: 50, left: 0, bottom: 34, right: 0)
            size = .init(width: 375, height: 812)
        }
        return .init(safeArea: safeArea, size: size, traits: .iPhoneX(orientation))
    }

    /// This is the same as the `iPhone13`
    public static let iPhone13Pro = ViewImageConfig.iPhone13(.portrait)

    public static let iPhone13ProMax = ViewImageConfig.iPhone13ProMax(.portrait)

    public static func iPhone13ProMax(_ orientation: Orientation) -> ViewImageConfig {
        let safeArea: UIEdgeInsets
        let size: CGSize
        switch orientation {
        case .landscape:
            // warning: unverified (unused) values
            safeArea = .init(top: 0, left: 44, bottom: 24, right: 44)
            size = .init(width: 926, height: 428)
        case .portrait:
            safeArea = .init(top: 47, left: 0, bottom: 34, right: 0)
            size = .init(width: 428, height: 926)
        }
        return .init(safeArea: safeArea, size: size, traits: .iPhoneX(orientation))
    }

    public static let iPhoneSe3rdGen = ViewImageConfig.iPhoneSe3rdGen(.portrait)

    public static func iPhoneSe3rdGen(_ orientation: Orientation = .portrait) -> ViewImageConfig {
        let safeArea: UIEdgeInsets
        let size: CGSize
        switch orientation {
        case .landscape:
            safeArea = .zero
            size = .init(width: 667, height: 375)
        case .portrait:
            safeArea = .init(top: 20, left: 0, bottom: 0, right: 0)
            size = .init(width: 375, height: 667)
        }
        return .init(safeArea: safeArea, size: size, traits: .iPhoneSe(orientation))
    }

}

I just realized most of the functions in my extension are using the same values for the traits property, and I have no idea how accurate those are to the new devices. I would love it if someone more knowledgeable could chime-in with how to "find" those per device.


Clean up when component is unmounted

Clean up, removing the script when the component is unmounted.
Fixes no op when component is unmounted before being loaded.

LGTM :+1:


fix sequence parallel(Ulysses) grad scale for zero0

use dp_world_size for grad reduction, instead of seq_dp_world_size.
Currently, for zero0, only sparse tensors use the correct world_size.
tiny model with sp=4 grad norm test:

grad_norm
step1
step2
step3
step4
step5
step100

zero1
15.825
16.646
15.853
16.159
17.333
15.555

zero0
3.956
4.161
3.963
4.040
4.333
3.889

zero0(this patch)
15.825
16.646
15.853
16.159
17.333
15.554

Hi, @samadejacobs  I have removed the modifications you mentioned in that line. Could you please help review the other parts again? Thanks!


README clarifications

Thanks so much for making this shim!  It looks very promising and the demo works great.
Am I reading the installation instructions correctly?  This is how I read it: the minimum installation to get things working is to complete one option from step 1, one option from step 2 and all three under step 3.
Step 1. Choose one of the "Install" instructions:

npm
jspm
bower

Step 2. Choose one of the "Include" options:

global
SystemJS/JSPM
ES2015/TypeScript/webpack

Step 3. Follow the instructions under each of these three headings:

Make sure to implement a dragenter-listener!
If you're targeting iOS Safari 10.x and higher (optional)
webpack/scss

Yes, this is correct. It's not really well structured, proposals for making it more clear are highly welcome!


Running make watchjs watches src folder

Running make watchjs will rebuild Rickshaw.js whenever src changes.

Coverage remained the same at 48.983% when pulling 011638d9046d30bcac3ae52f3ddb166b37e805b2 on roberttod:make-watchjs into eb1bf7c9c0cfcd38134a9a92a486fe176d1b191c on shutterstock:master.

Be sure to npm install first to get nodemon!

thanks @roberttod !


Changed CSS code back to english on size-your-images.spanish.md and fixed localTitle

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks!


Move formatEnabledInEnv to a better place

problem
There's not a good, intuitive way of figuring out if the underlying logger/shell supports colours.
sbt 1.0.0-RC2 changed formatEnabled to formatEnabledInEnv. I don't know what triggered this change, but I don't think it was a good idea... In any case, now that it's already done, we should add ways to maintain source compatibility for all plugins.
My idea would be to add a this one-liner:
@deprecated("Use formatEnabledInEnv instead", "1.0.0")
val formatEnabled: Boolean = formatEnabledInEnv

## expectation
There's an API called `Logger` or `LoggerUtils` or something alike that allows me to easily check this. Or even a global key would suffice.
ConsoleAppender.formatEnabled does compile.
notes
IMO, ConsoleAppender is not the right place to have all this information. So we should consider locating this crucial info in a more direct and visible place, which makes more sense than ConsoleAppender, which is not intuitive for those totally unaware of how the underlying log mechanism works (which is most of the people).
sbt version:1.0.0-RC2

In my opinion, we don't need to support source-compatibility between pre-release versions of sbt.
For source compatibility with sbt 0.13.x, which I think is a very worthy cause, we do have that deprecation in place (the "since" field is wrong and there's a typo in the message though.. cc @Duhemm):
  @deprecated("Use ConsoleAppenders.formatEnabledInEnv", "0.13.x")
  val formatEnabled = ConsoleAppender.formatEnabledInEnv

(https://github.com/sbt/util/blob/v1.0.0-M28/internal/util-logging/src/main/scala/sbt/internal/util/ConsoleAppender.scala#L25-L26)

Let me change the main goal of this ticket towards providing a sane API for plugin authors to know if they can use colors or not in their output. I agree than source-compatibility between pre-release versions of sbt is not that of a big deal.

I agree we should consider making this public API. Currently it's in sbt.internal.util.ConsoleAppender.formatEnabledInEnv.

What used to be called "Logger" in 0.13 now splits into two separate categories of classes that many are already familiar from log4j etc: Logger that is responsible for generating log events, and Appender that consumes those events.
From the point of view of the plugin (or tasks) it's not knowable whether all of the terminal supports formatting or not because the idea behind sbt server is that the events could be transmitted to another program via JSON.


Create 2023-09-22-OpenSearch-Personas-Creating-Figma-Templates-to-Rep…

…resent-Person-Framework
This blog gives community members the tools to create personas an jobs to be done. It explains how to access and use these tools.
Description
New Blog regarding the access and use of Figma Templates to create personas and jobs to be done
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

@nateynateynate @krisfreedain - This blog is ready to publish today.


Enh: Allow downloading by album/sets

It would be nice if you could download by album (set).

Same as #20


Implement periodic vesting for NOVA and Tickets

Follow the vesting rules described in the whitepaper for both NOVA and Tickets.

Hey team! Please add your planning poker estimate with Zenhub @aang114 @sinkingsugar

Duplicate of #117


The phone number unable to get  in some kind of android mobile. Why?

The phone number not getting in all the mobiles. why? But it shows carrier name, country code etc but not phone number.
Please tell me why this plugin not getting mobile number from all kind of android mobile. How to overcome this issue..
My coding is:
"
var dataCarrier;
  function successCallback(result) {
      alert(result);//give me [object][object]
      alert(result['carrierName']+" carrierName");//give me 'Verizon'
      alert(result['countryCode']+" countryCode");//give me 'Verizon'
      alert(result['mcc']+" mcc");//give me 'Verizon'
      alert(result['mnc']+" mnc");//give me 'Verizon'
      alert(result['callState']+" mcc");//give me 'Verizon'
      alert(result['phoneNumber']+" mob num")
      dataCarrier = result['phoneNumber'];
      alert(dataCarrier )
  }

  function errorCallback(error) {
      alert(error);
  }

  window.plugins.sim.getSimInfo(successCallback, errorCallback);

"
Its working fine in some android mobile...
Please tell me How to solve this issue..

See #5

Thanks for your replay.
Please tell me how to get sim serial number using sim plugin in ionic framework.

https://github.com/pbakondy/cordova-plugin-sim/releases/tag/v1.1.0


add read / write (char) interface to MediaStream

add read / write of single character for convenience
some progress in implementing AMF0 endcode /decode

Good  point. I'll fix it  today
2016년 4월 5일 (화) 오전 6:41, Dujeong Lee<EMAIL_ADDRESS>작성:

Merged #11 https://github.com/MediaPipe/MediaPipe/pull/11.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/MediaPipe/MediaPipe/pull/11#event-614306169


Default arguments in an object destructure aren't checked for string literal unions

This is a flow bug that caused an incident
Flow version: Latest
Expected/Actual behavior
type MyEnum = 'Top' | 'Latest';

function test({
  // this should error but doesn't
  example = 'wrong',
}: {|
  example?: MyEnum,
|}) {}

Link to Try-Flow or Github repo:
try flow
typescript (correct behaviour)

Duplicate of #8972


[Demangle to metadata] Support simple extension contexts.

Support demangling for types nested within some simple extension contexts.
Still does not support nested types within constrained extensions that
involve same-type constraints among generic parameters, nor
deeply-nested types in extensions. However, it fixes
rdar://problem/40071688.

@swift-ci please test and merge


node expiration can be empty string or even strange string

LGTM.

@AdoHe Could you give a detailed example of this?

Closing due to low activity. Reopen if you have a follow-up. Thanks! @AdoHe


[OpenAI] TypeSpec autogen OpenAI

Using the TypeSpec to generate OpenAI for the first time.
APIview: https://apiview.dev/Assemblies/Review/b4abaab395e24c46a43817bf561f7bbc

/azp run prepare-pipelines

These changes will be as a baseline in https://github.com/Azure/azure-sdk-for-java/tree/feature/open-ai


First Contribution by Khadija

Name:  Khadija
Project:  bqplot
Governance model:  https://github.com/bqplot/governance/blob/master/governance.md
Bqplot is an open-source project, and as such, it has a community-driven governance model. The project is hosted on GitHub, and anyone can contribute to the project by submitting pull requests, reporting issues, or participating in discussions on the project's issue tracker. The core team of Bqplot is responsible for maintaining the project, reviewing contributions, and making decisions about the direction of the project. The core team consists of experienced contributors who have demonstrated their expertise and commitment to the project over time. The project has a well-defined code of conduct, which outlines the expected behavior of contributors and users of the project. The code of conduct is enforced by the core team, who are responsible for resolving any disputes or issues that arise.
Therefore the foundations of Project governance are:

Openness & Transparency
Active Contribution
Institutional Neutrality
The Project leadership consists of a Steering Council.

The main project roles in the Bqplot project are:

Core Contributors
Contributors
Maintainers
Users
Additionally, the Bqplot project has a Steering Committee made up of core contributors.

The Bqplot project follows a consensus-based decision-making process, where decisions are made through discussion and collaboration among the project's contributors and maintainers. The goal of this process is to ensure that decisions are made in a transparent and inclusive manner, with input from all stakeholders.
Specifically, the decision-making process in the Bqplot project involves the following steps:

Discussion.
Consensus.
Voting.
Implementation.
It's worth noting that the decision-making process may vary depending on the nature and scope of the issue at hand.

The governance model for the Bqplot project is easy to find. The project's governance model is documented in a file named "GOVERNANCE.md", which can be found on the project's GitHub page. The file provides a detailed overview of the project's governance structure, including the roles and responsibilities of project contributors, decision-making processes, and conflict resolution mechanisms. The file is well-organized and easy to navigate, making it easy to find the information you need about the project's governance model.

@arliss-NF

It is better to give your full name as we may have one than one Khadija here

@Khadija411 - good work.  This task seems to have been an easy one, but I hope you learned a bit about governance models.  Often the model is found in a file with the name you gave, but it can be buried deep in a GitHub repo.  It should be as easy to find the governance model for all open-source projects ... often it is not.


Restore DOM effect to both usages of effect row for EventListener

This seems to be causing problems: https://github.com/slamdata/purescript-halogen/pull/440#issuecomment-293538712
@nwolverson, @natefaubion - technically this is a breaking change, but since the current thing is breaking more stuff, do you think a patch release would be acceptable instead?

Actually, maybe not 🙈... will find out for sure once I've fixed some other errors.

Ok yeah, just the change in this PR is required. There was something else going on that made it look like the other change was needed.

I don't particularly care about either the particular signature here or the semver usage, I just had a drive-by comment previously but for reference, semver.org suggests a restoring-compatability change does not require a major bump.


Follow-up improvements to RAFT training reference

This issue is to keep track of the progress on some minor improvements related to the RAFT training reference, as a follow up to https://github.com/pytorch/vision/issues/4644

[x] support --weights param to support the prototype API, once pre-trained weights are available
[x] support --model instead of the --small flag
[x] support --epochs param instead of --num-steps, for consistency with the rest of the training references.
[ ] save the scheduler and the optimizer, not just the model.
[ ] try to keep function names as close as possible to existing references. For example validate() -> evaluate()
[ ] Support --device (?? - not sure how useful it would be)
[ ] Better support of weight serialization (move on CPU, avoid having the DDP model weights etc)

cc @datumbox

I beleieve all the remaining points have been addressed by @YosuaMichael in https://github.com/pytorch/vision/pull/5590. Thanks Yosua!


Validation fixed

The current validation allows to evaluate expressions without specifying values for all the variables. This pull requests fixes it.

Current coverage is 100% (diff: 100%)

Merging #49 into master will not change coverage

@@           master   #49   diff @@
===================================
  Files           6     6
  Lines         396   392     -4
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
- Hits          396   392     -4
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 1b2c95e...7d3c3b5


rshim-user-space: 2.0.32 -> 2.1.5

Notable changes include:

more robust timeouts
better BlueField 3 support
better detect install finish in bfb-install with BMC present
loose less log log messages with CLEAR_ON_READ

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Tested on Bluefield 2


MINOR: [Java] Bump com.puppycrawl.tools:checkstyle from 8.19 to 8.29 in /java/maven V2

Rationale for this change
This PR was created in place of https://github.com/apache/arrow/pull/39202 to integrate the puppycrawl.tools.checkstyle upgrade.
What changes are included in this PR?
Style changes in Java classes and core changes to the style format itself.
Some unsupported attributes have been removed. And some attributes have
been reorganized upon the provided guidelines in the documentation.
Are these changes tested?
N/A
Tested by existing checkstyle guideline.
Are there any user-facing changes?
No

@github-actions crossbow submit java

@github-actions crossbow submit java

Not sure if there is such a line though:
https://github.com/ursacomputing/crossbow/actions/runs/7578473688/job/20641129446#step:7:35880

@github-actions crossbow submit java

@github-actions crossbow submit java

@lidavidm the file noted in the error seems to be generated https://github.com/ursacomputing/crossbow/actions/runs/7622553317/job/20760815369#step:7:35295
Should we omit such generated resources from checkstyles?

Yes

@github-actions crossbow submit java

@lidavidm seems like the CIs are passing.


add an implicit for parameters to add them to Template objects

I'm going to merge this one, I'll make a separate commit that adds in all the other implicits that we are still missing.


CMake Error at ClangFormat-stamp with itk-5.1_beta

I am trying to bump our ITK package version to 5.1 beta, and it installs fine, but again I get an error (build.log) when trying to test it.
This update is mainly so as to ensure compatibility with a newer ANTs version which I can actually build (apparently the build system needed a few new tweaks). Don't worry, my complaints will get less frequent after I manage to get some version of ANTs building :)

@TheChymera Your local test data cache is missing a file NoPreambleDicomTest.dcm, available from here.
ITKTestingData might need an update for Beta1. Is that correct @thewtex?

Your local test data cache is missing a file NoPreambleDicomTest.dcm, available from here.
ITKTestingData might need an update for Beta1. Is that correct @thewtex?

Yes -- this patch will add the missing files for the next release.

I get an error (build.log) when trying to test it.

cd /var/tmp/portage/sci-libs/itk-5.1_beta/work/itk-5.1_beta_build/ClangFormat-prefix/src && /usr/bin/cmake -P /var/tmp/portage/sci-libs/itk-5.1_beta/work/itk-5.1_beta_build/ClangFormat-prefix/src/ClangFormat-stamp/ClangFormat-download-Gentoo.cmake && /usr/bin/cmake -E touch /var/tmp/portage/sci-libs/itk-5.1_beta/work/itk-5.1_beta_build/ClangFormat-prefix/src/ClangFormat-stamp/ClangFormat-download
1349 CMake Error at ClangFormat-stamp/ClangFormat-download-Gentoo.cmake:49 (message):
1350   Command failed: 1
1351
1352    '/usr/bin/cmake' '-Dmake=' '-Dconfig=' '-P' '/var/tmp/portage/sci-libs/itk-5.1_beta/work/itk-5.1_beta_build/ClangFormat-prefix/src/ClangFormat-stamp/ClangFormat-download-Gentoo-impl.cmake'
1353
1354   See also
1355
1356     /var/tmp/portage/sci-libs/itk-5.1_beta/work/itk-5.1_beta_build/ClangFormat-prefix/src/ClangFormat-stamp/ClangFormat-download-*.log

@TheChymera This could be avoided by setting -DITK_FORBID_DOWNLOADS:BOOL=ON, but it is set to OFF in line 22. Is it possible to flip the value?

All data issues should be resolved in ITK 5.1 RC 2. @TheChymera thanks for the report. If similar issues occur, re-opening or new issues are appreciated.


Log in to the juju cli before shelling out

This fixes the issue where running juju cli commands fail
because the juju cli has logged out,
and gets an interactive login prompt instead.
The juju cli is used in some functions,
for checking and retrieving the tempest log file.

/canonical/self-hosted-runners/run-workflows 40116e3cda4e77fd659fe60b9e975b2eaeb9dcd6


Fix tflint issue with default_nodepool_vm_type value (IAC-421)

Terraform Version Details
Terraform v1.0.0
Terraform Variable File Details
variables.tf
────────────────────────────────────────────────────────────────────────────────────────────
variable "default_nodepool_vm_type" {
default = "Standard_D8s_v4
}
Steps to Reproduce
Run tflint, a Terraform source file linting tool from the command line in the root level folder of the cloned viya4-iac-azure repository.
Sample output:
❯ tflint
1 issue(s) found:
Error: "Standard_D8s_v4" is an invalid value as vm_size (azurerm_kubernetes_cluster_default_node_pool_invalid_vm_size)
on main.tf line 145:
145:   aks_cluster_node_vm_size                 = var.default_nodepool_vm_type
Callers:
main.tf:145,46-74
modules/azure_aks/main.tf:50,29-57
Reference: https://github.com/terraform-linters/tflint-ruleset-azurerm/blob/v0.14.0/docs/rules/azurerm_kubernetes_cluster_default_node_pool_invalid_vm_size.md
Expected Behavior
No output from tflint would indicate no errors found and is the expected behavior.
Actual Behavior
❯ tflint
1 issue(s) found:
Error: "Standard_D8s_v4" is an invalid value as vm_size (azurerm_kubernetes_cluster_default_node_pool_invalid_vm_size)
on main.tf line 145:
145:   aks_cluster_node_vm_size                 = var.default_nodepool_vm_type
Callers:
main.tf:145,46-74
modules/azure_aks/main.tf:50,29-57
Reference: https://github.com/terraform-linters/tflint-ruleset-azurerm/blob/v0.14.0/docs/rules/azurerm_kubernetes_cluster_default_node_pool_invalid_vm_size.md
Additional Context
No response
References
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This is not an error, but a lack of the lint tool knowing about the newer versions of the VM types. If there is an error its on TFLint and should be opened there.

This is not an error, but a lack of the lint tool knowing about the newer versions of the VM types. If there is an error its on TFLint and should be opened there.

Thanks Thomas, I'll look into doing that then.

Looked into this further, it appears that the enum list that TFLint uses to validate the available vm_sizes is no longer being updated by the compute API team -> https://github.com/Azure/azure-rest-api-specs/issues/10033#issuecomment-657701452
I'll look into whether or not this particular warning can be ignored for now since it is a false indication that something is wrong given the situation.

Strange as I see Standard_D8s_v4 in the valid list on the main and v0.14.0 branch

Strange as I see Standard_D8s_v4 in the valid list on the main and v0.14.0 branch

This is the v0.14.0 ruleset I referenced, it doesn't seem to have the Standard_D8s_v4 entry in that list https://github.com/terraform-linters/tflint-ruleset-azurerm/blob/v0.14.0/docs/rules/azurerm_kubernetes_cluster_default_node_pool_invalid_vm_size.md
Can you link me to the list that you are seeing it in?

Was this issue not address with this PR #223 ?

Nope you should have linked the issue with the PR. That way when the PR is closed, if it covers all aspects of an issue, then the associated issue is also closed. Just a learning moment ;)

OK, thanks @thpang, I think I've got it linked now.


Dev build 2015-04-06 Hangs VS 2013 Desktop Express

I have a mixed solution with three C# projects and one IronPython project in it. When I try to open this solution with the 6th April build of PTVS installed, VS 2013 Desktop Express freezes with the notification "VS Express 2013 Desktop Express is busy ... waiting for an internal operation to complete ...". Solution Explorer shows that the Solution is "(loading...)" but there is little to no CPU activity. It looks like something is deadlocked.
The previous Dev Build 2015-03-26 seemed to work fine except for the occasional freeze that required a restart  which all previous builds of PTVS seem to have suffered from when an IronPython project is loaded in VS but with the IronPython source not necessarily being loaded in the editor.

This problem might have been related to the combination of editor windows open in the solution. I renamed the solution folder which makes the solution load with no editor windows opened and now I can no longer reproduce the hang.


instance.options.contentSelector.height is not a function

When I enable the prefill option, I get this error:
instance.options.contentSelector.height is not a function

Any idea what's causing this? I'm using the latest version of infinite-scroll.

Sorry to hear you're having trouble with Infinite Scroll.
Infinite Scroll v3 is out!. It's an all new re-write, so take a look at how to upgrade from v2.
I recommend upgrading to v3. Please open a new issue if you run into trouble with Infinite Scroll v3. 🌈🐻


Bug: Firestore AggregationQuery stuck when running locally in Docker

Firestore AggregationQuery getting stuck
We are getting Client.Timeout error when running AggregationQuery to count the number of documents in a query inside a Docker container.
How to reproduce
Use the code provided below with the following folder structure:
.
├── credentials.json
├── Dockerfile
├── main.py
└── requirements.txt

credentails.json is used to authenticate to Google Cloud and have access to Firestore. For this example, we assume that Firestore is set up for the project and can be access by this service account key.
Dockerfile, main.py and requirements.txt are provided below.

docker build -t bug .
docker run -d -p 8888:8080 --name bug bug:latest

Running the following curl command output the expected result:

$ curl http://localhost:8888
Count: 0.0

At this point the code works well, the issue appears when we restart the docker container, and we send multiple concurrent request to the endpoint using the hey HTTP load generator to simulate real traffic on our application:
docker restart bug
hey -c 10 -n 100 -m GET http://localhost:8888/

From that point we are not getting any response back from application, and we receive Get "http://localhost:8888/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
This error setup has been reproduced on Linux and Mac.
The error only seems to appear when we restart the container. It is also fix when we restart the container again. It is going in a loop of stuck, unstuck, stuck, unstuck.... We didn't manage to reproduce this bug by running this code outside of Docker.
Is there any undocumented caching or network protocol used by that tool that we should know of and that required some Docker config?
What we tested

Running the same code without the data = aggregate_query.count().get() line solve the timeout issue. We are no longer getting the data we need since we are not running it. By doing so, we isolated the issue to that line.
Adding the timeout parameter to the aggregate_query.count().get(timeout=2) does not do anything for us. This parameter doesn't seem to be working at all.
We tested this code on different network to exclude firewall rules that could block network calls.

Source code

main.py

"""BUGGED module."""

from datetime import datetime, timedelta
from typing import Tuple

import flask
import functions_framework
from flask import Response
from google.cloud.firestore_v1 import Query
from google.cloud.firestore_v1.aggregation import AggregationQuery
from google.cloud.firestore_v1.base_query import FieldFilter
from google.cloud.firestore_v1.client import Client as FirestoreClient

FIRESTORE_CLIENT = FirestoreClient()

def count_data_in_query_bugged(query: Query) -> int:
    """Count data in query."""
    print("Start counting data in query")
    # Transform to aggregation query to count
    aggregate_query: AggregationQuery = AggregationQuery(query)
    data = aggregate_query.count().get()
    count = data[0][0].value
    print("end counting data in query")
    return count

@functions_framework.http
def entry_point(request: flask.Request) -> Tuple[Response | str, int]:
    print("Request received")
    start = datetime.now() - timedelta(days=1)
    end = datetime.now()

    query = (
        FIRESTORE_CLIENT.collection("statistics")
        .where(filter=FieldFilter("status", "==", "acceptable"))
        .where(filter=FieldFilter("timestamp", ">=", start))
        .where(filter=FieldFilter("timestamp", "<", end))
    )

    count = count_data_in_query_bugged(query)
    print(count)
    return f"Count: {count}", 200

Dockerfile

FROM python:3.11

WORKDIR /app

COPY . .

# Install requirements
RUN pip install -r requirements.txt

ENV FUNCTION_TARGET="entry_point"
ENV GOOGLE_APPLICATION_CREDENTIALS="/app/credentials.json"

# Run cloud function locally
CMD functions-framework --target=$FUNCTION_TARGET --debug

requirements.txt

blinker==1.7.0
cachetools==5.3.3
certifi==2024.2.2
charset-normalizer==3.3.2
click==8.1.7
cloudevents==1.10.1
deprecation==2.1.0
Flask==3.0.2
functions-framework==3.5.0
google-api-core==2.18.0
google-auth==2.29.0
google-cloud-core==2.4.1
google-cloud-firestore==2.15.0
googleapis-common-protos==1.63.0
grpcio==1.62.1
grpcio-status==1.62.1
gunicorn==21.2.0
idna==3.6
itsdangerous==2.1.2
Jinja2==3.1.3
MarkupSafe==2.1.5
packaging==24.0
proto-plus==1.23.0
protobuf==4.25.3
pyasn1==0.5.1
pyasn1-modules==0.3.0
requests==2.31.0
rsa==4.9
urllib3==2.2.1
watchdog==4.0.0
Werkzeug==3.0.1

Do you need to close the client or gracefully shutdown? What about a try-catch or increasing the client timeout secs?

Do you need to close the client or gracefully shutdown? What about a try-catch or increasing the client timeout secs?

I've tried to instantiate a new Firestore client at every function call to check if the globally available client was the issue. It didn't change the results of the experiment, we are still getting stuck
I've also recreated that experiment in Go using the function-framework-go library and I am not getting any errors/timeout so far. I can only affirm that the docker restart process to break the python code doesn't seem to work on the Go code. Switching to another programming language to overcome a critical issue of the package isn't a solution for us


Can the animation empty down to the current level?

Great tool!
We are using it to show how full and how empty certain containers are. When observing something filling up, the current "filling animation" (from 0 to the current value) is a great visual indicator.
However, when observing a container emptying, the filling animation looks a little off.
Can an option be added which animates the fill line from 100% down to the current level, showing it emptying instead of filling?
Thanks!

Will the effect look similar to the demo page when it goes down from 100% to x%?

Yeah, I reckon so. Just the other way round.

Was this ever resolved? We desire the same thing.


Home Assistant: Client  disconnected due to protocol error.

Hi,
i have issues to connect the weatherstation to my Home Assistant by MQTT. Testing with the BresserWaetherSensorWaiting gives me perfect values. But when i try a MQTT connection, the Serial Monitor shows me a endless try to MQTT connect and in Home Assistant i get a "Client  disconnected due to protocol error." message. Anyone else got it Working with Home Assistant?
BR

Hi,
I have no experience with Home Assistant. Is there any other debug output available?
Does HA provide an MQTT broker?
Did you cross-check the MQTT port, MQTT login/password and the type of connection (secure vs. non-secure)?
Best regards
Matthias

Hi Matthias,
Thanks for the response.
unfortunately not. When i uncomment the DEBUG_MQTT line, i get a compile error:
`
BresserWeatherSensorMQTT:602:21: error: 'genWeatherdata' was not declared in this scope
602 |         decode_ok = genWeatherdata(0 /* slot /, 0x01234567 / ID /, 1 / type /, 0 / channel */);
  |                     ^~~~~~~~~~~~~~

exit status 1
'genWeatherdata' was not declared in this scope
`
In HA you can setup a Mosquitto Broker. I checked the MQTT settings, and they seem to be correct. In the Broker log i see the esp trying to connect but stopping with the "disconnected due to protocol error".
I tried everything with an online MQTT broker and it works like a charm, so it has something to do with the HA provided broker.
Maybe an incompatible MQTT library or issues with the MQTT topics.
I was hoping that someone ran into the same issue and knows a solution.

O.k., thanks for your feedback. I will check why genWeatherdata() cannot be found.

Fixed DEBUG_MQTT feature:
https://github.com/matthias-bs/BresserWeatherSensorReceiver/commit/a696ff70f6c984b9f4201ea70f607e8d3a91afbc

I have burned a whole evening trying to figure this out. I have a HA myself with the same broker. Same endless........... In the terminal.
A pointer in the right direction to solve this would be nice.

Hi Lschans,
in my case the #define USE_SECUREWIFI was the problem. Use #define USE_WIFI and it will work. And there is a change in the format of the json string from Release 0.4 to 0.5
HA can only work with the 0.4 Release json string format. The change was also only for the data string, extra ist working in 0.5. I wanted to inform @matthias-bs about it as soon as i have time to compare the code and give him the exact change which causes the issue for HA.
@matthias-bs thank you for this amazing project. You should add a "buy me a coffee" button to your git :)

@ga3ns3blu3mchen Thanks for the kind feedback! I'd be happy to make some changes to it (or to add a specific example sketch) compatible to HA.
Good idea to add a "buy me a coffee" button, I will think about this! ;-)

@ga3ns3blu3mchen Sadly this didn't work for me. I tried all different configuration options and it just keeps loading with a bunch of ....... and then nothing.
If I have some time this weekend I will give this a try https://esphome.io/custom/custom_component.html
Mainly because to my opinion ESPHome is the better integration when you have Home Assistant. If I can hack something together I will either push this as a fork to this project, or contact @matthias-bs  and ask if he want's to host the code in his repo. I am not that much of a 'maintaining a repo' guy. And this is most of his code anyway.
Let me know how you people would think about this as an ESPHome integration?

Are using an ESP32 or an ESP8266? With ESP32 and setting "Core Debug Level: Verbose" in the IDE, you might get some helpful information from the WiFi protocol stack.
Due to some network problems today, I noticed a few things:

according to some sources, it is recommended to add a delay(10); between WiFi.begin() and polling WiFi.status()
the dots are printed at several places in the code (not really helpful for localization of a problem...)
in some cases, the program does never recover from a networking problem, but a reset would help

To address the third item, add a retry counter and performed a timed restart, e.g.:
    WiFi.begin(ssid, pass);
    delay(10);
    int cnt = 0;
    while (WiFi.status() != WL_CONNECTED)
    {
        Serial.print(".");
        delay(1000);
        if (++cnt == 10)
            ESP.deepSleep(SLEEP_INTERVAL * 1000);
    }
    Serial.println(F("connected!"));

I don't have any experience with ESPHome, but I'm open to make some modifications if I can help or to add another example (or a real integration).

So far nothing of the tips and tricks helped, my network connection is fine. Either using secure or normal WiFi.
Using secure wifi it fetches the time and this all works fine. It's somehow related to the MQTT (mosquitto server) Home Assistant ships with. I confirmed the server works with other MQTT connectors.
I didn't have much time for coding last week because of some crazyness at the job. I wil keep testing and see if I can find out what exactly is keeping it from connecting to home assistant.
I'll keep you guys updated.

Any update on this?


Make tools script callable

How to categorize this PR?

/area usability
/kind enhancement
What this PR does / why we need it:
In the provider extensions we are currently in process of enabling security linting (gosec).
We want to reuse the scripts provided by gardener/gardener.
However we're using the gardener module files where by design scripts are only readable.
That's why we always use bash in order to execute scripts from the gardener module as in this example.
If we now want to add the following target:
.PHONY: sast
sast: $(GOSEC)
	@bash $(GARDENER_HACK_DIR)/sast.sh

We try to execute install-gosec.sh script in tools.mk but receive Permission denied since install-gosec.sh is only readable.
This issue would resolve if we add the bash keyword.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Make gardener tool script install-gosec executable from gardener as module

How is this PR related to #10642? They are not identical, but both are about making it possible other repositories to re-use gosec from g/g.

/cc @ScheererJ

https://github.com/gardener/gardener/pull/10642 only allows the installation of gosec, but ignores the other executables, e.g. promtool. Not sure if the other tools need to be consumed elsewhere, i.e. from extensions.
With regards to the actual gosec call, I copied the sast.sh script while @hebelsan seem to just execute it. As the report is generated relative to the script's directory moving the script to the correct location seems to be the better option from my point of view.

Sorry, haven't seen the existing PR of @ScheererJ.
We also only need gosec tool but I thought it would be a good idea to change it consistently.
Closing this PR in the light of https://github.com/gardener/gardener/pull/10642.
/close


Not possible to install at CentOS 7 machines

It seems not possible to install PDNS Manager 2.0.1 at CentOS 7 machines.
All requirements are met (PHP 7.1.26, mysqlnd, APCU), the files are owned by the webserver user, config is writable.
However, wenn /setup is called and all data is inserted into the fields and sent to /api/v1/setup, nothing happens. The database won't be set up, no files are written. The screen switches to the login screen and you can login with any data, no matter what you write into the user/password fields. You see an empty dashboard where you can't do anything.
There are no error messages anywhere. Not in the browser console, not in the PHP log, not in any log files. The Webserver access log shows a regular 200 response.
I have no clue what is going on...
It looks like the slim database connection is broken and everything fails silently.

Im having the same issue

Add one to the number of people having this issue.

Fresh install on AWS using Amazon Linux 2 and I have the same issue. So this is not just CentOS 7, but possibly anything based on RedHat Enterprise 7.

fwiw, one more facing the same limitation.

Exact same issue for me, with PHP 7.3 on CentOS 7.

Anyone fixed this issue ?
same issue for me
centos 7, php7.2

The code called for setup is in backend/controllers/Setup.php you can enter debug messages here and check where it fails. I have no experience in cent os therefore it is difficult to check that and it would take me much time. If you have clues please ask again.

Can someone of you check if the change suggested by @medea61 in loewexy/pdns-manager-website#9 solves the problem for you. I just tested it on my Ubuntu setups and it works fine there.

Looks like the setup works fine after https://github.com/loewexy/pdns-manager-website/pull/9. Will do some more testing and will let you know

https://github.com/loewexy/pdns-manager-website/pull/9 worked for me too with php 7.4


Display the actual EB IdPs metadata in the generated XML

This, again very large, PR will ensure the IdPs metadata endpoint renders the correct data.
Worklog (WIP)

[x] Implement the SP entity id filtering
[x] Ensure error reporting is implemented as requested in: 168258776
[x] Add shibmd:Scope elements if applicable
[x] Make the logo an optional field of the entities
[x] Increase test coverage and verify correct metadata generation

Fixes
https://www.pivotaltracker.com/story/show/168258709
Created new issues:
https://www.pivotaltracker.com/story/show/169199290
https://www.pivotaltracker.com/story/show/169199410

Great work!


readyForStable: evaluate / adapt criteria

Ctriteria for issue to add to stable should be eva,luated.
Code might be incorrect
see: https://t.me/ioBroker_development/28445
Criteria should be: (to be discussed)

latest is older than 15 days and stable is more than 30 days older than latest ?? Users ??
latest is older than 15 days and latest users are more than 10% of all users
latest is older than 30 days and latest users are more than 5% of all users
latest is older than 60 days

solved with https://github.com/ioBroker/ioBroker.repositories/commit/1e3dc962317cce22d7af744cd9052ab57d639544

criteria should be reavaluated.
percent limit is too high, eventually drop limit after 30 days totally.
To be discussed with Apollon77

new percent limits:
5% or 30days (after 20day even 0% will be OK)


Add tutorial for error mitigation with Qiskit Runtime Estimator

Fixes #1168
Marked draft because I am waiting for the code cells to finish running (they submit jobs to hardware) so I can include their output.
TODO:

[x] Skip CI because notebook submits jobs
[ ] Format and lint

Phenomenal work Kevin!
my comments:

I think we might need to come up with a different title for this tutorial, atm it's too similar to the PEA utility notebook title
could you add a list of requirements to the top of this notebook (check out some of the other tutorial PRs to see how others have done it)
in the intro when you select the efficientSU2 can you mention that this approach is generalisable to many types of circuits, I believe that was an important point from the original notebook.
I like how clearly you set the goal of the tutorial in the intro, could you also add that first you will be showing a small example and then scaling it up in the second half
Also in the intro, can you mention which of the EM techniques you will be comparing in the rest of the notebook
more of a question - is there a reason we shouldn't just show the full 50q example from the start? The code example at the end looks very similar, maybe we could just use that from the get go?
in general the explanation of the "scale up" section looks a bit sparse - are there any additional insights you could add there? atm it feels like that section was just lumped in at the end without much thought
nice code comments!

Overall I think this is a great simplified version of the notebook, but i think we should definitely follow up with more of a deep dive into the different error mitigation techniques in additional documentation

@kevinsung does this recent comment about breaking changes to the Estimator result data for ZNE affect your tutorial?

@kevinsung does this recent comment about breaking changes to the Estimator result data for ZNE affect your tutorial?

I don't think so. I only access the ZNE results using the evs attribute which should be consistent with the non-ZNE results too.

@javabster I've addressed your comments. I also added a "Conclusion" section and made a few other minor edits. Please take another look.

more of a question - is there a reason we shouldn't just show the full 50q example from the start? The code example at the end looks very similar, maybe we could just use that from the get go?

The main reason is simply ease of visualization. If you try to draw a 50-qubit circuit it's very slow and the output is too large to view comfortably. Also, in general it's preferable to build and test a workflow on small circuits first (I mention this now in the notebook).

Looking great! Some last final small things:

I really liked the bullet points at the end where you summarised the insights from the results 👏
it looks like you used numpy and mpl for the analyse results section, so those packages should be added to the requirements list
for the mirror section, that's the same as the "compute-uncompute" technique right? If both terms are used by end users I think it would be good to mention that the mirror stuff is "otherwise known as compute-uncompute..."
can you update the patterns subheadings to be in line with what the other tutorials are doing (e.g. analyse results should be post-process results)

it looks like you used numpy and mpl for the analyse results section, so those packages should be added to the requirements list

I don't think we should list Numpy and Matplotlib as explicit requirements because that would be redundant and noisy. Numpy is already a dependency of Qiskit (and just about every other Python library that works with numbers). And we already explicitly say Qiskit needs to be installed "with visualization support" which implies Matplotlib. Thoughts?

I see your point about mpl but when you install qiskit does it also install numpy for you? I thought you had to install that separately

I see your point about mpl but when you install qiskit does it also install numpy for you? I thought you had to install that separately

Yes, installing Qiskit installs Numpy too.

for the mirror section, that's the same as the "compute-uncompute" technique right? If both terms are used by end users I think it would be good to mention that the mirror stuff is "otherwise known as compute-uncompute..."
can you update the patterns subheadings to be in line with what the other tutorials are doing (e.g. analyse results should be post-process results)

Done

Is it possible to get the error bars on the expectation values?

Can the operators be constructed using the sparse list method?

Looks very nice!

Is it possible to get the error bars on the expectation values?

Can the operators be constructed using the sparse list method?

Looks very nice!

Done!


Bugfix where clicking on SVG element causes error

Added a check that node.className is actually a string, which is not the case for SVG nodes.

thanks, will create a new release later on

sorry for the delay, npm and bower should have the new version

Cool, thanks for making a nice component :-)


get_active_channels: Handle TRUE response from device

When calling get_active_channels, on the Logic Pro 8, there is a chance
that TRUE will be returned instead of the expected digital_channels.
without this check, the assert will crash out.
This occurs when changing the trigger of the channel after performing a
capture.
Signed-off-by: Malcolm Prinn<EMAIL_ADDRESS>

Thanks! I just pushed 0.3.1 to pypi with this fix.