something with mobile that's bound to give someone seizures

https://github.com/violetfrost/violetfrost.github.io/assets/132141735/6eebb9e1-488a-4390-aa04-972c7a21ea16

What android version / what browser / any other pertinent information? This is because it's falling back to the default depth buffer (ie. non lograithmic) so I'm guessing it's an issue of what versions of WebGL your device supports.

Google Chrome on a Samsung Galaxy A12

What OS version, though? Settings -> About Phone -> Android Version

Android 12. Apple's iPhone (you use one) has its own iOS, and they don't license the OS to third parties. Samsung mostly runs on android. as do most other non-apple companies.

So far this is looking to be a bug specific to android 12+ on samsung phones and maybe pixel with WebGL - system level and I can't fix it if that is the case.
Just in case, though, one more question: What version of chrome do you use? Chrome settings -> about chrome

Chrome 120.0.6099.115
appears to be fixed btw

https://github.com/violetfrost/violetfrost.github.io/assets/132141735/24d1e613-ecf9-4a0a-99bc-0970dd616fe3
looks okay on mine now.


Problems using DDP

I met tough problems when running this line in trainer.py/_dist_train
model = MMDistributedDataParallel(model.cuda())
It worked after modifying like this:
model = MMDistributedDataParallel(model.cuda(), device_ids=[local_rank], find_unused_parameters=True)
This is because the model must be set the specific gpu when running parallel, or it will be put on all gpus, and the batch_size will change, then error will occur when calculating backproject.
why other people didn't meet this problem?

you can use CUDA_VISIBLE_DEVICES to control which gpu will be used

you can use CUDA_VISIBLE_DEVICES to control which gpu will be used

but I want to use all GPUS, one GPU for every process, maybe device_ids=[local_rank] is the only solution?


Broken with Babel 7

First off, thanks for this awesome tool. This was a lifesaver for me when I needed exactly this functionality a couple months ago.
Unfortunately, I just updated my project to Babel 7 and found that the loader was no longer working correctly.
In development mode, things seem to be working fine. If, on the other hand, I build my project, the #if statements are seen as regular comments.
I have to admit it's kind of strange that an upgrade to Babel 7 would cause this but I've checked it several times. Happy to help you reproduce it too.
FWIW, I'm on the latest version of Webpack (4.17.1) and everything was working great until I updated Babel.

Btw, this is my rule for JS files:
{
  test: /\.js$/, // Transform all .js files required somewhere with Babel
  exclude: /node_modules/,
  use: ['babel-loader', 'webpack-conditional-loader'],
},

As recommended. Conditional loader will be called first which makes this more confusing to me.

Never mind. Doesn't seem to be the real cause of the problem I'm experiencing.


Creative Labs Audio

Package Requested

[x] I would like someone else to build the manifest.
[x] I would like help so I can submit the manifest.
[ ] I have performed a search and couldn't find this package.
[ ] I think there is a new version available and I have provided the URL.

Manifest:
From what I can see we will be unable to add creative.com software to the manifest as they are using a TOS captcha before you can download any thing.
The actual files are not restricted and can be download if you have a the direct link.
Thoughts?

IE.  https://support.creative.com/downloads/download.aspx?nDownloadId=100337

I was able to get the download link directly:
https://files.creative.com/manualdn/Drivers/100337/e7DhBdRr2t/USBCMDMasterInstaller_<IP_ADDRESS>.exe
however i cannot tell if they generating those links or not, from what I can tell so far they are not

I have not had a chance to fully read the TOS for the download.  So not sure if adding it to a repository would be allowed.

[Policy] Package Request
[Policy] Blocking Issue - Dynamic URLs for download


Unable to specify a collins configuration when using collins.NewClientFromYaml

There are times when I wish to specify which config file I'd like to use.
Rather than having collins.NewClientFromYaml() always search for a config file, I'd like to pass it a filepath that it will parse.

Is there some situation you've encountered where setting COLLINS_CLIENT_CONFIG isn't sufficient? If there seems to be a good use case then adding this feature sounds like a good idea to me. And if so I'd rather we did it without making any breaking API changes, so by adding a new function that accepted a path rather than changing the signature of NewClientFromYaml.

Hey @schallert, yes. The situation would be when you need to connect to more than one Collins instance.
The equivalent feature is provided in Collins::Authenticator.setup_client.
I can understand not wanting to change the signature for NewClientFromYaml.
It sounds like a new function is needed. Something along the lines of NewClientFromPath or NewClientFromFile.

Yup, definitely sounds like a sane addition. How about something like this: https://github.com/tumblr/go-collins/compare/master...defect:newclient_from_path ? Then you could just pass a single-element array to NewClientFromFiles().
NB: I haven't actually tested the code above :) If it seems sane I'll write up a couple of unit tests for it and make a proper PR.

yeah, that seems remarkably reasonable to me


Unintuitive error message when trying to mount an unaccessible/missing file into an existing container location

The title speaks for itself, the docker deamon shows a cryptic error message (see below) when one tries to mount a file that is missing or not accessible on the host in an existing location on the container side.
I have created a small repository containing all the instructions to reproduce the error message: github.com/klingtnet/unintuitive-docker-error-message
Instructions and error:
$ git clone https://github.com/klingtnet/unintuitive-docker-error-message.git && cd unintuitive-docker-error-message && ./trigger-error.sh
docker: Error response from daemon: oci runtime error: rootfs_linux.go:53: mounting "/var/lib/docker/devicemapper/mnt/293288098b315e070975512b52113dc6cbe49d5de455f1cb6f113729520fe2e9/rootfs/usr/bin/foo" to rootfs "/var/lib/docker/devicemapper/mnt/293288098b315e070975512b52113dc6cbe49d5de455f1cb6f113729520fe2e9/rootfs" caused "not a directory".

Here is a link to rootfs_linux.go.

The error message should look like this: Could not mount /foo/bar.sh because file/directory is missing.

Hey I'm a new Contributor, can I work on this?

Oh, missed this issue (thanks for the reproduction repository @klingtnet, that's really great!)
@karsinkk well, you can; the error message was already improved "a bit" in docker 1.13 and up through https://github.com/docker/docker/pull/24754, which, at least explains what's happening (see daemon/start.go#L188);
However, the new output looks like;
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"/Users/sebastiaan/projects/docker-triage/repro-30100/unintuitive-docker-error-message/missing.sh\\\" to rootfs \\\"/var/lib/docker/overlay2/12320edb229f3a1d22859479ad70b6cc82ac4419968cda8ca4194c3070acdf3e/merged\\\" at \\\"/var/lib/docker/overlay2/12320edb229f3a1d22859479ad70b6cc82ac4419968cda8ca4194c3070acdf3e/merged/usr/bin/foo\\\" caused \\\"not a directory\\\"\""
: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.

Some things I notice;

The error is still really verbose; details about the source file and line number (process_linux.go:359) could be useful as a "debug" level log-line, but most likely not to the user
The same applies to the full path to the container's rootfs /var/lib/docker/overlay2/12320edb229f3a1d22859479ad70b6cc82ac4419968cda8ca4194c3070acdf3e/merged/. Useful as a "debug" level log-entry, but not so much to the user
The colon (:) appears on a new line, probably because the  previous error has a trailing \n. We can probably remove the colon and space

Haven't looked into what's returned "where" and what options we have to improve it (without doing string-matching, and find/replace, which would probably be brittle), but if you want to work on this, that'd be welcome 👍


Added flake8 Lint action

python-version: ["3.9", "3.10", "3.11", "3.12"]

made a pull request here, wanted to make it on my fork


wrong  mock.calls structure

filter method runs callback function with three arguments so result of filterTestFn.mock.calls is not correct.

Summary

Test plan

I updated files which you are mentioned.


Selectize and SelectizeMultiple options are capped to 250 options

Is there a way to expand the number of options in selectize and selectmultiple?
I checked the number of items in my queryset and the result is 521
I also checked html rendering of selectize and the options are capped to value="250"
I was wondering if there is a way to show all 521 still? Thank you

closing this. I just din an override of your widget and used the custom one instead
class CustomSelectize(Selectize):
    max_prefetch_choices = #some number
	# customize due to cap of original

class CustomSelectizeMultiple(SelectizeMultiple):
    max_prefetch_choices = #some number
	# customize due to cap of original


[issue 507 & 699] Add support for DM subscriptions for Watchers and Reporter

adding watching and reporter notification feature for jira
ticket here
fixes #507
fixes #699

Hello @sibasankarnayak,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Codecov Report

Merging #840 (6e0a576) into master (f986c15) will decrease coverage by 0.34%.
The diff coverage is 32.36%.

@@            Coverage Diff             @@
##           master     #840      +/-   ##
==========================================
- Coverage   31.46%   31.11%   -0.35%
==========================================
  Files          49       49
  Lines        5982     6174     +192
==========================================
+ Hits         1882     1921      +39
- Misses       3911     4058     +147
- Partials      189      195       +6

Impacted Files
Coverage Δ

server/client.go
8.64% <0.00%> (-0.30%)
:arrow_down:

server/command.go
16.89% <0.00%> (-0.31%)
:arrow_down:

server/plugin.go
10.43% <0.00%> (-0.64%)
:arrow_down:

server/user_cloud.go
0.00% <0.00%> (ø)

server/user_server.go
8.16% <0.00%> (-0.44%)
:arrow_down:

server/webhook_worker.go
0.00% <0.00%> (ø)

server/webhook.go
22.05% <13.72%> (-8.80%)
:arrow_down:

server/settings.go
69.56% <70.00%> (-10.44%)
:arrow_down:

server/webhook_parser.go
83.38% <79.41%> (-1.84%)
:arrow_down:

server/user.go
30.55% <100.00%> (+4.96%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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

@mickmister can you check currently notification will be triggered for watching feature.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

It seems, that the MR is nearly complete. @sibasankarnayak could you please agree with @mickmister on the pending changes? This change would really help me. Thx

Closing in favor of https://github.com/mattermost/mattermost-plugin-jira/pull/872


Clean up demo server code, primarily by importing all used packets.

This is the follow-up to #1. I like how it looks, but it may be very subjective.
Any style guidelines discussion should be archived as an issue on PistonDevelopers/hematite_server.

 Yay.


Decimal == AnythingElse causes assertion failure

Running the following method causes an assertion failure at runtime.
shared void run() {
    if (decimalNumber(3) == 2) {
        process.writeLine("3 == 2");
    } else {
        process.writeLine("3 != 2");
    }
}

The stack trace begins
Exception in thread "main" ceylon.language.AssertionError "Assertion failed
        violated is DecimalImpl that
                expression has type ceylon.language::Integer which is not a subtype of ceylon.decimal::DecimalImpl"
        at ceylon.decimal.DecimalImpl.equals(DecimalImpl.ceylon:123)
        at decimal.run_.run(mwe.ceylon:5)

(The code above is obviously dubious, as an Integer constant and the result of a method returning Decimal are of disjoint types, and in fact the compiler warns about this; where I ran into this, my code was comparing two objects' corresponding fields of declared type Number<out Anything>.)

Yeah, that assertion is totally wrong - https://github.com/eclipse/ceylon-sdk/blob/dd5ed08180f880742703342e6da6fdf79af82998/source/ceylon/decimal/DecimalImpl.ceylon#L132

Thanks @jvasileff 👍


Fix build with disabled ES2015 module system

With a disabled ES2015 module system the build fails as an enum value
is incorrectly guarded and used.

LGTM (informal)


Support versions

Support cluster version from user input based on stream (AWS)/channel-group (ROSA).
Destroy clusters if create fail.

/verified

/verified


Better default material

Motivation and Context
The DEFAULT_MATERIAL was initialized with full white ambient and diffuse light, causing objects to appear flat shaded. These values have been modified for a subjectively better appearance.
How Has This Been Tested
Original:

New:

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Sort of tangent to the PR, but in line with what was stated above : Since a PhongMaterialData has pointers to textures, and only a default destructor, is this not a possible source of memory leaking?

These textures live in the textures_ map as shared pointers. The pointers stored in the material structure are pointing here (assigned in getPhongShadedMaterialData), so no issue with memory leaks. We also don't allow textures to be freed during runtime, so none of these pointers should get stale.

A comment unrelated to the content of the changes: the use of naked new makes loud alarm bells ring in my head whenever I see it outside the innards of class construction/destruction logic that is neatly paired up. 😅I assume this is safe because the ShaderManager takes responsibility to free the memory eventually?

That is a valid concern. In this case we don't remove any materials once added and as a member of esp::assets::ResourceManager the shaderManager_ outlives a Simulator so there is no potential for missed deletion within the current assumptions.
@mosra I see the reference counting and freeing functionality in Magnum::ResourceManager. For these gfx::MaterialData pointers, free handles deletion, right?

Sorry, missed the comments above.

I assume this is safe because the ShaderManager takes responsibility to free the memory eventually?

For these gfx::MaterialData pointers, free handles deletion, right?

Yes to both. This API originates in early C++11 times and it was only updated to take r-value references and smart pointers quite recently (it was waiting for a lighter-weight unique pointer implementation), and most of existing code, docs and examples still uses the discouraged "naked new" way. The PR doesn't touch the relevant part anymore, but what could be done to hide the raw new is for example
shaderManager_.set<gfx::MaterialData>(DEFAULT_MATERIAL_KEY,
                                      gfx::PhongMaterialData{});

shaderManager_.set<gfx::MaterialData>(DEFAULT_MATERIAL_KEY,
                                      Cr::Containers::pointer<gfx::PhongMaterialData>());

or, using the standard unique pointers
#include <Corrade/Containers/PointerStl.h>

shaderManager_.set<gfx::MaterialData>(DEFAULT_MATERIAL_KEY,
                                      std::make_unique<gfx::PhongMaterialData>());


[CON-1291] Merge release/1.3.1 into master

Changes

Merge changes from release/1.3.1 into master

No worries, I temporary disabled the branch protected to be able to remove it from remote (that's the only way I know of deleting protected branches!).


can't initialize iptables table `nat': Table does not exist

❯ Starting Virtual DSM for Docker v7.01...
❯ For support visit https://github.com/vdsm/virtual-dsm
❯ Install: Downloading installer...
❯ Install: Downloading DSM_VirtualDSM_69057.pat...
/DSM_VirtualDSM_69057.pat                               100%[=============================================================================================================================>] 346.98M  2.60MB/s    in 2m 50s
❯ Install: Extracting downloaded image...
❯ Install: Preparing system partition...
❯ Install: Extracting system partition...
❯ Install: Installing system partition...
❯ Creating a 16G preallocated disk image in raw format...
iptables v1.8.10 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
 The iptables kernel module is not loaded when you start DSM. The fix is easy: https://docs.fedoraproject.org/en-US/fedora/latest/system-administrators-guide/kernel-module-driver-configuration/Working_with_Kernel_Modules/#sec-Persistent_Module_Loading
The name of the module is ip_tables.


Preview does not load through reverse proxy

I'm running nginx proxy manager and passing the web admin interface (using SSL/CF tunnel).  The Preview image is not loading - I think the webui page is trying to use the RTSP feed, rather than the MJPEG feed.  From the client, nothing loads on the web side, and in the console it looks like the div "row preview" - "col-lg-9 mb-3" - "small" is calling "playrtsp"
Maybe the default preview pane should be pulling the MJPEG feed instead (/x/mjpeg.cgi)?  Or maybe it could be selectable on the Preview pane?

can you share the full log from the browser developer console?

same issue as #296 preview is initiated via websocket on port 8089. you need to pass this port/websocket via your proxy too.

Thanks for the help on this!  Now I just need to figure out how to do that through NPM, since my nginx skills are bleh.

fixed. please test and confirm.


Return response()->file() stored in Aws s3

Discussed in https://github.com/laravel/framework/discussions/43906

Originally posted by davymaish August 29, 2022
Thank you for the great framework.
I have been having a problem while returning file response from a controller.
Im getting this error;
The file "https://web.s3.eu-west-2.amazonaws.com/...." does not exist
If I open the url in its own tab, the image is dislpayed. As per my code, its a must i return the file as a response()->file() without downloading or streaming.
My partial code is as below
$url = Storage::disk('s3)->temporaryUrl(                 $file->file_path.$file->name, now()->addMinutes(5)             );             return response()->file($url);
I would appreciate your response and assistance. Thank you.

Please don't move discussions back to issues.

Just help, don't discriminate my issue


show variable/function/method signatures in runtime completion

like LSP, show signatures

basic support in commit 224f4f5

add test case in commit c58101c


Galsim as requirement has generated time-out in testing

In a PR, the installation of Galsim has resulted in a time out. Perhaps we do not need to include galsim in the requirements as it is very specific to few functions using the list pipeline?

Yes, we can remove galsim from the requirement.


Possible to use gorm Preload with dbresolver?

Describe the feature
Is is possible to use gorm preload to preload data from multiple db sources?
Currently It seems that the db connection will use the first source, so the table from the second source can not be reached when preloading.

Motivation
Support gorm preload when it comes to multiple db sources

Related Issues

Just found the solution:
db.Clauses(dbresolver.Use("FooDB"), dbresolver.Read)..Preload("model1", func(db *gorm.DB) *gorm.DB {
			return db.Clauses(dbresolver.Use("BarDB"), dbresolver.Read)
		}).


Underline access keys don't work

When I enable the option "Underline access keys when available" in settings, it doesn't work. I'm on Windows 10 22H2.

NS has its own settings:
https://nilesoft.org/docs/configuration/themes
// prefix value [auto, 0 = dont display,  1 = display, 2 = ignore]
prefix = 1
there is also an option to link the two settings: when you change the settings in the windows panel, they can be reflected in NS directly

Thank you! But how can I link the two settings? Sorry but I'm not good at programming. I'm not an English native speaker either. I can't find it on your web.

it is nowhere - a new logic has yet to be created. when I'm ready I'll write.
or
come to NS Discord Channel: https://discord.com/channels/1106387012707168318/

add this line to shell.nss:
theme.item.prefix=if(str.equals(reg.get('HKEY_CURRENT_USER\Control Panel\Accessibility\Keyboard Preference', 'On'), 1), 1,'')

reload NS (or restart the explorer)
the next time you change the Windows setting, you only need to reload the NS
there are other ways to achieve the result

to make a command in the context menu to reload the settings
to set the setting independently when opening the context menu, but there will be a visible result from the next opening of the menu (cannot be done globally - this can be done only for a certain situation: only on the desktop, or only on the taskbar, or only in e-explorer ...)


Flanneld and etcd open too many connections

I'm not sure Kubernetes github is the right place for posting my issue, but I found it during kubernetes usage.
Environment
I have a vm with ubuntu 14.04.1 with kubernetes (with only one master-minion node) installed to it using the following script which installs kubernetes 1.0.3, etcd 2.0.12 and flanneld 0.4.0:
# build binaries
cd cluster/ubuntu
K8S_VERSION=1.0.3 ./build.sh
cd ../..

# deploy kubernetes cluster
cd cluster
KUBERNETES_PROVIDER=ubuntu ./kube-up.sh
cd ..

# deploy ui
kubectl create -f cluster/addons/kube-ui/ --namespace=kube-system

# deploy heapster
kubectl delete -f cluster/addons/cluster-monitoring/influxdb/ --namespace=kube-system
kubectl create -f cluster/addons/cluster-monitoring/influxdb/ --namespace=kube-system

Problem
And I've run into trouble that the etcd process repeatedly crashes once in 16-17 minutes with the following messages in the logs:
2015/08/12 07:17:49 etcdserver: failed to purge wal file open infra0.etcd/member/wal: too many open files
2015/08/12 07:17:49 etcd: no data-dir provided, using default data-dir ./infra0.etcd
2015/08/12 07:17:49 etcd: already initialized as member before, starting as etcd member...
2015/08/12 07:17:49 etcd: listening for peers on http://<IP_ADDRESS>:2380
2015/08/12 07:17:49 etcd: listening for client requests on http://localhost:2379
2015/08/12 07:17:49 etcd: listening for client requests on http://localhost:4001
2015/08/12 07:17:49 etcdserver: datadir is valid for the 2.0.1 format
2015/08/12 07:17:49 etcdserver: recovered store from snapshot at index 90009
2015/08/12 07:17:49 etcdserver: name = infra0
2015/08/12 07:17:49 etcdserver: data dir = infra0.etcd
2015/08/12 07:17:49 etcdserver: member dir = infra0.etcd/member
2015/08/12 07:17:49 etcdserver: heartbeat = 100ms
2015/08/12 07:17:49 etcdserver: election = 1000ms
2015/08/12 07:17:49 etcdserver: snapshot count = 10000
2015/08/12 07:17:49 etcdserver: advertise client URLs = http://localhost:2379,http://localhost:4001
2015/08/12 07:17:49 etcdserver: loaded cluster information from store: infra0=http://<IP_ADDRESS>:2380
2015/08/12 07:17:49 etcdserver: restart member 14158305b132d735 in cluster 6d92d8ce627b6add at commit index 95240
2015/08/12 07:17:49 raft: 14158305b132d735 became follower at term 48
2015/08/12 07:17:49 raft: newRaft 14158305b132d735 [peers: [14158305b132d735], term: 48, commit: 95240, applied: 90009, lastindex: 95240, lastterm: 48]
2015/08/12 07:17:51 raft: 14158305b132d735 is starting a new election at term 48
2015/08/12 07:17:51 raft: 14158305b132d735 became candidate at term 49
2015/08/12 07:17:51 raft: 14158305b132d735 received vote from 14158305b132d735 at term 49
2015/08/12 07:17:51 raft: 14158305b132d735 became leader at term 49
2015/08/12 07:17:51 raft.node: 14158305b132d735 elected leader 14158305b132d735 at term 49
2015/08/12 07:17:51 etcdserver: published {Name:infra0 ClientURLs:[http://localhost:2379 http://localhost:4001]} to cluster 6d92d8ce627b6add

Investigation
I've investigated that according to lsof output processes of etcd and flanneld continously open more and more connections and then crach when hitting 32k limit. Lsof output moments before crashes groupped by processes shows the following:
sudo lsof | grep -E "kube|etcd|heapster|docker|flannel" | perl -lane '$x{"$F[0]:$F[1]"}++; END { print "$x{$_}\t$_" for sort {$x{$a}<=>$x{$b}} keys %x}'; sudo lsof | wc -l
...
105	kube-cont:6222
144	kube-prox:6223
450	kubelet:6216
672	kube-apis:6221
5982	etcd:6207
6762	flanneld:6218
8601	docker:32701
31465 <- total descriptors

After etcd and all the dependent services restart it looks like this:
sudo lsof | grep -E "kube|etcd|heapster|docker|flannel" | perl -lane '$x{"$F[0]:$F[1]"}++; END { print "$x{$_}\t$_" for sort {$x{$a}<=>$x{$b}} keys %x}'; sudo lsof | wc -l
...
90	kube-cont:20231
90	kube-prox:20232
105	heapster:17526
354	flanneld:20227
420	kubelet:20225
510	etcd:20216
648	kube-apis:20229
8715	docker:32701
19579 <- total descriptors

Most of these descriptors use ports 4001 and 2379:
sudo lsof | grep -E "4001|2379" -c
12837

I've shared the complete lsof output: https://gist.github.com/AlexeyKupershtokh/3daf5fae4cedf5e0f18f
Flanneld reports in the logs only this, once a second:
E0812 08:09:48.298232 01713 main.go:171] Failed to create SubnetManager: 100: Key not found (/coreos.com) [6882]
E0812 08:09:49.300837 01713 main.go:171] Failed to create SubnetManager: 100: Key not found (/coreos.com) [6882]
E0812 08:09:50.302249 01713 main.go:171] Failed to create SubnetManager: 100: Key not found (/coreos.com) [6882]

I would like to normalize descriptors usage somehow, preferrably without raising the limit up from 32k.
Should I do any additional debugging either provide more logs?

Solution
I've finally found another related issue https://github.com/GoogleCloudPlatform/kubernetes/issues/8176 which is resolved by installing dns addons.
Not sure if this would help alone but I have also installed sudo apt-get install bridge-utils and run sudo /opt/kubernetes/cluster/ubuntu/reconfDocker.sh.
Now descriptors number stabilized on about 10k and grow slowly. I'll monitor it further.


Wrong widthPerSecond in AssetTrackSampleLoader used to calculate samplesPerPixel

I kept noticing that for short audio 3 seconds or less, the width seemed very off but as the sample became larger it was fine. I finally noticed that the "generateTrackOutput()" in the constructor of AssetTrackSampleLoader() uses the widthPerSecond stored in the AssetTrackSampleLoader class to calculate the samplesPerPixel. But the widthPerSecond is still the default value of 10, so it never changes. It should be the calculated actualWidthPerSecond. So added a parameter to AssetTrackSampleLoader so that it can take the widthPerSecond. Currently, the width is set on the loader only after generateTrackOutput() is called, so it makes no difference.
Update the init/constructor for AssetTrackSampleLoader as follows...
public init(track: AVAssetTrack, actualWidthPerSecond: CGFloat) {
    self.widthPerSecond = actualWidthPerSecond
    self.track = track
    generateTrackOutput()
}

Then pass in the value when creating it in the loadSamples function...
        let loaders = asset.tracks(withMediaType: .audio).map { (track) -> AssetTrackSampleLoader in
            let loader = AssetTrackSampleLoader(track: track, actualWidthPerSecond: widthPerSecond)
            //loader.widthPerSecond = widthPerSecond
            return loader
        }

Also, I'm not sure why but dividing by 5000 instead of 20000 in "updatePoints()" would allow the waveform to show more clearly for me. I'm not sure where 20000 comes from but maybe this should be selectable too.  I tried scaling the height of the waveform instead but that didn't seem to help.
        func updatePoints(with audioSamples: [VIAudioSample]) {
            var points: [Float] = []
            if let audioSample = audioSamples.first {
                points = audioSample.samples.map({ (sample) -> Float in
                    return Float(sample / 5000.0)
                })
            }
            strongSelf.viewModel.points = points
        }

Lastly, I don't ever want to truncate samples. I want to see the whole waveform.  So I changed the following by commenting the if check block and always setting the actualWidthPerSecond based on the duration. I think this was just here due to the above issue where the minWidthPerSecond was not getting set right.
        // if fill the timeline view don't have enough time, per point respresent less time
        /*
        if CGFloat(duration) * strongSelf.minWidthPerSecond < strongSelf.minWidth {
            strongSelf.actualWidthPerSecond = strongSelf.minWidth / CGFloat(duration)
        } else {
            strongSelf.actualWidthPerSecond = strongSelf.minWidthPerSecond
        }
         */

        strongSelf.actualWidthPerSecond = strongSelf.minWidth / CGFloat(duration)

thank you


Array splicing error ???

Is this a bug or I am missing something?
The result of a[1, 3] = [6, 7, 8] seems wrong.

Ruby reports the same:
a = [1, 2, 3, 4, 5]
a[1, 3] = [6, 7, 8]
a # => [1, 6, 7, 8, 5]

But Crystal gives me [1, 3, 3, 4, 5]. Please check the output panel.

Weird indeed... icr returns correct [1, 6, 7, 8, 5] but crystal play shows [1, 3, 3, 4, 5].
Line#6 seems off since it should return [6, 7, 8].

Yup, doing pp a[1, 3] = [6, 7, 8] shows a[1] = 3 # => 3 in output console, so it might be more a crystal play bug.

This issue is not reproducible with 0.27.2. Should we close it?

Yes, seems to be fixed in the playground (was reported a long time ago^^).


Convert destruction

Fixes #29917
Fixes #25946
Fixes #30996
Well, the PR comes after 1 year.
This PR add a refactor that allow us convert between access expression and destruction.
The behavior follow below rules:

Not work with javascript
Edits on current file only
Work on variable like declaration but not Enum member.
Trigger if selected node is the left part of access expression:  [|a|].b // apply at a, [|a.b|].c // apply at a.b
Work with property access and constant element access: a["xxx"] // ok, a[foo] // not work
Not work if type of selection narrowed into another type unless the referenced type is not changed with the original type
Ignore if references has some method call (missing this) [|a|].b()
Ignore if reference in assignment target
Ignore if the argumentExpression of element access is not a valid identifier, eg: a["w-t-f"]
Ignore if reference is before declaration in the code (hoisting).
Ignore if reference is inside a function but not in body.
Generate new name if not conflict with others
If all access is numeric index access  and they all less than 15, Call it Dense
Generate index_i as array destruction binding for Dense array destruction
Generate i: index_i as object destruction binding for array destruction
Numeric index signature will convert into object like destruction

Todo:

[x] Basic find references and apply changes
[x] Smart selection
[x] Unique name resolve
[x] Method call detection
[x] Reference assignment detection
[x] Object literal like destruction
[x] array like destruction
[x] ~Convert back into property access~
[x] Copy comments
[x] Tests

Known Issues

[x] First Reference should at top level
[x] Element access not work
[x] Element name collapse
[x] Element access with invalid identifier

@typescript-bot pack this.

@typescript-bot pack this.

Emmmmmmmm... Up

I have to propose another way to trigger the refactor:
If we have
interface I { foo: string; bar: number }

And we have code:
declare const a: I
console.log(a.foo, a.bar, a.foo, a.bar)

when we select one of the right of property access:
declare const a: I
console.log(a./*a*/foo/*b*/, a.bar, a.foo, a.bar)

The refactor will only be apply at foo:
declare const a: I
const { foo } = a
console.log(foo a.bar, foo, a.bar)

And if we select one of the left of property access:
declare const a: I
console.log(/*a*/a/*b*/.foo, a.bar, a.foo, a.bar)

The refactor will only be apply at all the access of a:
declare const a: I
const { foo, bar } = a
console.log(foo bar, foo, bar)

And we could provide a new action: replace with the destruction, That could handle https://github.com/microsoft/TypeScript/issues/24827 too:
declare const { foo, bar }: I
console.log(foo bar, foo, bar)

@lukaszpolowczyk Maybe you will interested at it.

@gabritto You might be interested in this too.

Please fell free to pm me. I have a week free.

I have already updated the pr with the behavior here.
So @typescript-bot pack this.

UpPpPpP

 interface I { a: string, b: number }
 function foo (item: I) {
    call(item./*a*/a/*b*/, item.b)
 }

I'm stuck on common parent node lookup....... Seems it's very expansive if we lookup on every references.

 interface I { a: string, b: number }
 function foo (item: I) {
    call(item./*a*/a/*b*/, item.b)
 }

I'm stuck on common parent node lookup....... Seems it's very expansive if we lookup on every references.

I guess we can simplify the code by anders's control flow changes.

@Kingwl do you still have time to work on this? Otherwise let's close it.

Without narrowing, it's nearly done, right?

Without narrowing, it's nearly done, right?

In my memory, yes. I'll try to pick this up today or tomorrow(UTC+8)😜

Shit. I guess I cannot pick this up...

Bad news..
 interface I { a: string, b: number }
 function foo (item: I) {
    call(item./*a*/a/*b*/, item.b)
 }

I'm stuck on common parent node lookup....... Seems it's very expansive if we lookup on every references.

Hey @sandersn ! Would you mind give some suggestions about this?
The blocker is I have no idea to find a position to insert the destruction declaration.

You'll have to remind me: how does the current code fail to find the right position? Is it that find-all-refs for a returns a: string, incorrectly setting the position to insert the destructuring to be the first line of your example?
Maybe if you find-all-refs on item you can use "the first line after item is declared".

@sandersn Well, It's not a good case. Below is a better one:
 interface I { a: string, b: number }
 interface II { i: I }
 function foo (item: II) {
    call(item.i./*a*/a/*b*/, item.i.b)
 }

It's suppose to be convert as:
 interface I { a: string, b: number }
 interface II { i: I }
 function foo (item: II) {
    const { a, b } = item.i
    call(a, b)
 }

But how could I find the position to insert the destruction?
valueDeclaration of item.i is a propertySignature.
Is that means I should find the left most symbol (in this case: item)?

Well, it's a good start anyway. That's the symbol that's actually in scope at the point where the refactoring is invoked.


Difference between griffin_lim and griffin_lim_tensorflow

why angles in _griffin_lim(S) equals np.exp(1j * np.angle(_stft(y))), but in _griffin_lim_tensorflow(S) equals est / tf.cast(tf.maximum(1e-8, tf.abs(est)), tf.complex64)? Are they same?
https://github.com/keithito/tacotron/blob/08989cc3553b3a916a31f565e4f20e34bf19172f/util/audio.py#L89
https://github.com/keithito/tacotron/blob/08989cc3553b3a916a31f565e4f20e34bf19172f/util/audio.py#L73

Yes, they should both give the same result, but perhaps it would be better to rewrite one of them so they use the same formula.


Weird maths stuff

So in the tutorial I've been following, when we got to implementing arithmetic precedence I was given this sum to try and interpret: 14 + 2 * 3 - 6 / 2.
Following the rules of precedence, this gets interpreted as (14 + (2 * 3)) - (6 / 2), which turns out to be 17.
After adding the proper ked operators, this sum had to be changed slightly to make up for the fact that both awayFrom and into work RTL instead of LTR (2 awayFrom 7 == 7 - 2)
This made the above sum become 14 plus 2 into 6 awayFrom 2 times 3.
However, due to precedence ordering, this was interpreted as (14 plus (2 into 6)) awayFrom (2 times 3), which instead gives the answer as -11.
My question is simple; do I give ked different handling for maths to make the ked version match the "normal" version, or do I leave it as is?

The answer I'm gonna go with is having a different precedence for each operator.
Instead of having these two levels:

md
as

Ked will use four levels:

d
m
s
a

which should fix the issue? Regardless, I'm working on operators now so I should have this fixed soon.


Usernames are case sensitive

is it possible to disable case sensitivity of usernames ?
e.g when i login with<EMAIL_ADDRESS>, i cant login
when i login with<EMAIL_ADDRESS>i can login.
this affects both with the first login ( web interface of synology ) as accessing a SMB share.

User names are converted to lower case in the queries, so there should be no distinction between upper and lower case...
What version of DSM are you using?
Which version of the wrapper is running? (there should be a message at startup).
Do you see any information in the log entries? If not, you can temporarily set the LDAP_DEBUG environment variable to true and try again - now there should be some entries in the log.

Hey :) I found a way to reproduce the issue. The fix is available in the dev tag and will be released with the next version.


Bump follow-redirects from 1.12.1 to 1.14.7

Bumps follow-redirects from 1.12.1 to 1.14.7.

Release notes
Commits

updated-dependencies:

dependency-name: follow-redirects
dependency-type: indirect
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

dependabot/npm_and_yarn/follow-redirects-1.14.7

dependabot/npm_and_yarn/follow-redirects-1.14.7


feat: add and refactor existing code for hazard report generator

Worked for me except for the custom polygon drawing function. Has that not been implemented yet?  Also the liquefaction sus map in the report is showing the wrong polys on the map.

this pr not needed


Setting default Values doesn't work as expected

The documented way of setting a default value doesn't work:
@Value(String) methodValue: string = 'GET';

this.methodValue is always 'GET' regardless of what gets passed in through data-controller-method-value
Our current workaround is:
@Value({ type: String, default: 'GET' }) methodValue!: string;

This library used to work with Stimulus 3.0.* versions.
From Stimulus 3.1.0 the framework itself provides basic support for TypeScript, which ruins the compatibility with this library.
Anyway, I'll check what I can do here and update the library if it won't require a big change.


Rare issue in rare Gdip_All.ahk :)

For old_gdip_stuff/mmikeww/Gdip_All.ahk in line 1614 variable must be VarRef
VarSetStrCapacity(&wOutput, -1)

fixed.  Thanks!


Small fixes

Codecov Report

Merging #91 (7680f0d) into master (fb50e80) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master      #91   +/-   ##
=======================================
  Coverage   97.49%   97.49%
=======================================
  Files          27       27
  Lines        1438     1438
=======================================
  Hits         1402     1402
  Misses         36       36

Impacted Files
Coverage Δ

source/argparse/internal/arguments.d
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


inplaceupgrade: delete idle MCD pods

The MCD pods currently gets created when a node is marked for update, but doesn't get removed until the whole pool finishes updating.
To conserve resources, this adds logic to remove any idle upgrade pods.
The longer term goal is to use daemonsets instead, see: https://github.com/openshift/hypershift/pull/1757, but as a proof-of-concept, spinning this out separately from https://github.com/openshift/hypershift/pull/1757#issuecomment-1294001810
I am happy to close this in favour of doing daemonsets, since this intermediary step seems of limited value, and the daemonset does dynamic scheduling as well

/approve

/lgtm
/test e2e-aws

Thanks for the review! I can do the followups via https://github.com/openshift/hypershift/pull/1757


Track skipping due to upstream Spotify API issues.

Describe the problem
When connecting to Balena raspberryPi device the tracks skip continuously.
To Reproduce
Open Spotify and attempt to connect to Balena Airplay device.
Tracks just begin skipping, some tracks play but the majority do not.
Expected behavior
Track selected plays on Balena device
Screenshots
 spotify  [2024-09-04T11:50:44Z ERROR librespot_core::channel] channel error: 2 0
 spotify  [2024-09-04T11:50:44Z ERROR librespot_playback::player] Unable to load encrypted file: ChannelError
 spotify  [2024-09-04T11:50:44Z WARN  librespot_playback::player] Skipping to next track, unable to load track <SpotifyId { id:<PHONE_NUMBER>4873040899923648362564505491, audio_type: Track }>: ()
 spotify  [2024-09-04T11:50:44Z INFO  librespot_playback::player] Loading <ApÃ©ro Spritz> with Spotify URI <spotify:track:4K9CUUcvjacTnHdnAnzGRP>

Additional Errors:
 spotify  [2024-09-04T11:54:01Z ERROR librespot_playback::player] Unable to load encrypted file: ChannelError
 spotify  [2024-09-04T11:54:01Z WARN  librespot_playback::player] Skipping to next track, unable to load track <SpotifyId { id:<PHONE_NUMBER>12721626386930062394132188552, audio_type: Track }>: ()

Device information

Board (hardware info): Raspberry Pi 3
Device type (as seen in balenaCloud): Raspberry Pi 3
balenaOS version: balenaOS 5.1.20+rev1

Additional context
Seems a Spotify API change is the cause and recommendation is to build librespot from dev branch which does not have the issue.
https://github.com/librespot-org/librespot/issues/1322

I can see in
/plugins/spotify/Dockerfile.template
we are using image
FROM andrewn/librespot:0.4.2-pulseaudio
@andrewn is it possible for you to rereate docker image of librespot from dev branch ?

Because I am a masochist who doesn't know when to quite whilst he's ahead and I already possess a docker hub account I thought I'd try building the image myself and ran into a few issues:
Modified build-pulseaudio.sh
# not sure if this should align with the dev branch build but it was unique so 🤷
# version = "0.5.0-dev" is dev branch version in cargo.toml
LIBRESPOT_VERSION="0.4.2-dev"
DOCKER_NAMESPACE="brettmillerit"

exec:
bash build-pulseaudio.sh
=> WARN: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 4)                                                      0.1s
 => ERROR [internal] load metadata for docker.io/balenalib/rpi-alpine:edge                                                          0.9s
 => CANCELED [internal] load metadata for docker.io/balenalib/rpi-alpine:3.14-run

ERROR: failed to solve: balenalib/rpi-alpine:edge: failed to resolve source metadata for docker.io/balenalib/rpi-alpine:edge: error getting credentials - err: exit status 255, out: ``

I then tried rebuilding using :3.14 and received a cargo error (I don't remember why I thought changing from edge would work:
> [librespot-builder 6/6] RUN cargo build   --release   --features alsa-backend,pulseaudio-backend   --verbose:
0.997 error: failed to parse manifest at `/app/librespot-src/Cargo.toml`
0.998
0.998 Caused by:
0.999   feature `edition2021` is required
0.999
0.999   this Cargo does not support nightly features, but if you
0.999   switch to nightly channel you can add
0.999   `cargo-features = ["edition2021"]` to enable this feature
------
Dockerfile.pulseaudio.template:20
--------------------
  19 |
  20 | >>> RUN cargo build \
  21 | >>>   --release \
  22 | >>>   --features alsa-backend,pulseaudio-backend \
  23 | >>>   --verbose
  24 |
--------------------
ERROR: failed to solve: process "/bin/sh -c cargo build   --release   --features alsa-backend,pulseaudio-backend   --verbose" did not complete successfully: exit code: 101

I moved back to edge and I think I have it building....or it's stuck building and going to throw an error eventually 🤷

Went back to check the original issue and seems Spotify have reverted their API version changes
https://github.com/librespot-org/librespot/issues/1322#issuecomment-2334271629
However, when Spotify decide to make those changes Balena will need to utilise the new 0.5.0 and the container images will need to be rebuilt and updated.
Guess I learned a tonne about the project 🤣

Hi @brettmillerb, sorry for the delay. I can try and do a new build of the repo in the next couple of days.
I guess 0.5.0 is backwards compatible with the old API too?

Hi @andrewn

I guess 0.5.0 is backwards compatible with the old API too?
Spotify rolled back the changes and I am still using the dev branch build I generated.

I am way past the realms of my existing knowledge as it is. I have noticed with the dev branch build that there are random disconnects when selecting my raspi from Spotify.
May be worth hanging fire for an official release of 0.5.0 before rebuilding the docker images since Spotify rolled back the changes their end 🤷♂

Hi there, currently, i am again getting a lot of:
librespot_core::session] Connection reset by peer (os error 104)
librespot_connect::spirc] subscription terminated

As suggested in docs, there is no actual solution, only to upgrade.
balena-sound-spotify-connect-os-error-104
There is already new librespot release v0.5.0 avalible.
i forked balenasound and updated tag for docker image
https://github.com/mivittek/balena-sound/blob/master/plugins/spotify/Dockerfile.template
and also andrewn librespot, where i bumed tag versions to 0.5.0
https://github.com/mivittek/librespot-docker
Bui i am unable to build docker image with github actions, there is some weird cargo build error.
https://github.com/mivittek/librespot-docker/actions/runs/11425163023/job/31786487840

It took a bit of fiddling around, but I have a version that seems to build v0.5.0 here: andrewn/librespot-docker#3
The GitHub actions have never worked, so I'm building them manually on my laptop.
The only thing is that I don't use balena-sound anymore so once they're up, someone's going to need to run them on a Pi to make sure they work.
I'll post here once they're on dockerhub.

Cool, i have pi4 and pi3 at my disposal, so i can try to build it on device :)

It took a bit of fiddling around, but I have a version that seems to build v0.5.0 here: andrewn/librespot-docker#3
The GitHub actions have never worked, so I'm building them manually on my laptop.
The only thing is that I don't use balena-sound anymore so once they're up, someone's going to need to run them on a Pi to make sure they work.
I'll post here once they're on dockerhub.

I can give it a go on a pi2

I left my laptop cross-compiling all the binaries and went out for the day.
I meant it would be great to check the compiled binaries work with balena-sound once they’re uploaded to docker.

@mivittek @wheredidthecostgo The new v0.5.0 images are now published to docker hub as andrewn/librespot.
Please test them out and let me know how they work for you

Well, i managed to build it and pull form docker repo, thanks for that. But there is error while running build. Some manifest missing ?
[airplay]           Step 1/10 : FROM mikebrady/shairport-sync:4.1.1 as shairport
[spotify]           Step 1/4 : FROM andrewn/librespot:0.5.0-pulseaudio
[spotify]           manifest for andrewn/librespot:0.5.0-pulseaudio not found: manifest unknown: manifest unknown
---- deleted some of build data

[Error]             Some services failed to build:
[Error]               Service: spotify
[Error]                 Error: manifest for andrewn/librespot:0.5.0-pulseaudio not found: manifest unknown: manifest unknown
[Info]              Built on df9c640
[Error]             Not deploying release.

i tried to debug it, but for main packge - without platform there is no manifest
docker manifest inspect andrewn/librespot:0.5.0-pulseaudio
no such manifest: docker.io/andrewn/librespot:0.5.0-pulseaudio

When i edit it manually as you cen see it in commit, it works as a charm.
/mivittek/balena-sound/commit/1847d9f974714fd421f168e48bace59701ccfd92

@mivittek Thanks for reporting that!
I forgot to enable the "create manifest" line in the script. 🤦
If you try again it should work.

@mivittek @wheredidthecostgo The new v0.5.0 images are now published to docker hub as andrewn/librespot.
Please test them out and let me know how they work for you

I've built and deployed!   I'll test and see if it corrects the (os error 104)

I redeployed image and since commit/f954c98 I am running 4+ hours and no error yet, so I got high hopes :)

@andrewn  It has worked perfect for me all day!  Thank you!!!

Its still working like a charm, should we create PR with update + bumped release version ?

It worked fine for a while, now I'm getting status code 502 errors.  See below.  I'm guessing it is some type of bad gateway error, but not sure why it would be happening.
But os 104 errors are gone, so I'm not sure what to do.

Hi there !
Error 502 happens after starting playing after some time without playback. It happens for me as well, but it does not
Log:
Supervisor starting
 spotify  [2024-11-02T17:13:30Z ERROR librespot_connect::spirc] ContextError: Error { kind: Unknown, error: StatusCode(502) }

This issue is documented in librespot , without any real solution :(
Comments in this tread are saying that session handling has bee n imporved and ther eis new librespot version, 0.6.0
reference:
https://github.com/librespot-org/librespot/discussions/609

Thanks!

Hi there !
Error 502 happens after starting playing after some time without playback. It happens for me as well, but it does not
Log:
Supervisor starting
 spotify  [2024-11-02T17:13:30Z ERROR librespot_connect::spirc] ContextError: Error { kind: Unknown, error: StatusCode(502) }

This issue is documented in librespot , without any real solution :(
Comments in this tread are saying that session handling has been  improved and there is new librespot version, 0.6.0
reference:
https://github.com/librespot-org/librespot/discussions/609


📚 Fix shields

Codecov Report

Merging #2 (949ceef) into master (87e3d7e) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master      #2   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files           1       1
  Lines          18      18
======================================
  Misses         18      18

Continue to review full report at Codecov.

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


ES256 and ES384 throwing length error. ES512 works.

I didn't notice another issue on this so I thought I'd mention it. Could be that I've mucked something up, could be coming from a lib you're using, or could be coming from you guys. Not sure so I thought I'd start here.
I'm currently working on a prototype for work using node-jsonwebtoken and everything works fine if I generate a token using ES512 everything is fine, but if I try to use ES256 or ES384 I get a variation of this error: (this is from ES256)
.../node_modules/ecdsa-sig-formatter/src/ecdsa-sig-formatter.js:60
 throw new Error('"r" specified length of "' + rLength + '", max of "' + maxEncodedParamLength + '" is acceptable');
                ^

Error: "r" specified length of "65", max of "33" is acceptable
    at Object.derToJose (.../node_modules/ecdsa-sig-formatter/src/ecdsa-sig-formatter.js:60:9)
    at Object.sign (.../node_modules/jwa/index.js:75:29)
    at Object.jwsSign [as sign] (.../node_modules/jws/lib/sign-stream.js:23:24)
    at Object.module.exports [as sign] (.../node_modules/jsonwebtoken/sign.js:144:16)
    at .../createToken.js:24:17
    at Object.<anonymous> (.../createToken.js:48:3)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)

I've not got anything too important in the script as it's pretty generic so I can add it if someone wishes to take a look at my code that leads to this.
Thanks for the hard work!

Well someone from work pointed out that I was using a 512 key. So that makes sense. I'll close this issue for you. Thanks again!


Use BAM as input

Hi, could BAM file be used as input for ViReMa? If so, how does the command prompt look like?

Thanks of the clarification, Jason.
Would you mind telling me how the command should be constructed? What are the inputs actually?
docker exec -it  python ./ViReMa.py ./FHV_Genome_padded ./FHV_10k.txt FHV_recombinations.SAM --Seed 20 --MicroInDel_Length 5 -BED --Output_Dir FHV_Test


Revert "Cleanup annotation used to synchronize the deployer with the actuator"

Reverts samsung-cnct/cluster-api-provider-ssh#67 There are two problems: 1) updateStatusAndAnnotations() will not add an annotation if Exists() fails, and Exists() will always fail if there is no annotation. 2) updateStatusAndAnnotations() attempts to make two updates using the same Machine object so that the second attempt will always fail.

I agree that reverting is the best course for this - to unblock us.  We can later add the functional changes - once they have been tested.

I agree. Two patches are needed to fix this and even then there is a subtle bug. We should un-revert this eventually as the code readability is better with the changes.


Updated issue template to guide users to try running RViz with C locale

Updated issue template to guide users to try running RViz with C locale. This could prevent (or pinpoint faster) issues like #1665.

I also don't know which part brought this in this time. I remember not having problems with this in a few years. But yesterday I was again staring at an empty rviz for a while until I tried the LANG=C workaround and it helped. Up-to-date Ubuntu 18.04/Melodic on x86/64 CPU, AMD Renoir GPU and with cs_CZ locale.

If your workspace is all from code a grep for std::stof or std::stod might tell

Let's move the discussion back to #1665 .

Merged into melodic-devel: b2386556b2f10de493f53ccb6db82e14c9707220


update interface notebook

Added a use case with parallelise on batches.
Simplified text.

Got it. We have this functionality in GitHub (very limited yet). This "View file" button shows the Jupyter NB with some limitations.


TEP 0097: Implement beforeSteps for TaskRun debug.breakpoints spec

Feature request
Allow users to mention named steps they would like to debug in beforeSteps in the debug.breakpoints spec in TaskRuns. The breakpoint will be before the step starts to help users inspect a step env before it starts executing.
Part of TEP 0097
Use case
Debug a step before it executes.

/assign


Table never creates

Trying to import test data into PostgreSQL 9.1
pgfutter --user postgres --port 30000 --schema public csv friends.csv
74 B / 74 B [====================] 100.00% 0
3 rows imported into public.friends
No table is created though.  Looking in pg_log I see this...
ERROR:  schema "public" already exists
STATEMENT:  CREATE SCHEMA public
I have tried creating a new schema as well but still no joy.  This is on a CentOS 6.7 box.  Here is the version info if it helps.
PostgreSQL 9.1.23 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-17), 64-bit

No table is created though. Looking in pg_log I see this...

It does try to create the schema but shouldn't be the cause for failing.
I must say I never tested it with PostgreSQL 9.1...
You are able to import it into the import schema?

No, not into import schema either.  No matter if I use import or public, it
always says the schema already exists, even if it doesn't.  Do you have
plans to add support for it?  It really looks like the answer to my prayers
but I can't change the version of my postgres server.  Thanks so much for
the quick response!
Ken
On Tue, Sep 27, 2016 at 2:14 AM, Lukas Martinelli<EMAIL_ADDRESS>wrote:

No table is created though. Looking in pg_log I see this...
It does try to create the schema but shouldn't be the cause for failing.
I must say I never tested it with PostgreSQL 9.1...
You are able to import it into the import schema?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lukasmartinelli/pgfutter/issues/29#issuecomment-249784796,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVbSNafoU5BrWde7PtVs-XY0bDxQH42sks5quMJJgaJpZM4KHUxG
.

No, not into import schema either.  No matter if I use import or public, it
always says the schema already exists, even if it doesn't.

After PostgreSQL 9.3 there is support to only create schema if it does not exist yet.
But I don't think the schema creation is the problem here.

Do you have
plans to add support for it?  It really looks like the answer to my prayers
but I can't change the version of my postgres server.  Thanks so much for
the quick response!

Can't promise. Perhaps I find a moment to make a quick test with it later and figure out what's wrong.

Ok, I understand completely.  If I can provide any logs or test anything it
for you, please let me know.
I'm going to look at a different alternatives for the moment, but I am more
than happy to test out any new code and document findings.
Regardless of your ability to add support for 9.1, your tool looks amazing
and I appreciate you working to create such an awesome tool!
On Sep 27, 2016 2:51 AM, "Lukas Martinelli"<EMAIL_ADDRESS>wrote:

No, not into import schema either. No matter if I use import or public, it
always says the schema already exists, even if it doesn't.
After PostgreSQL 9.3 there is support to only create schema if it does not
exist yet.
But I don't think the schema creation is the problem here.
Do you have
plans to add support for it? It really looks like the answer to my prayers
but I can't change the version of my postgres server. Thanks so much for
the quick response!
Can't promise. Perhaps I find a moment to make a quick test with it later
and figure out what's wrong.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lukasmartinelli/pgfutter/issues/29#issuecomment-249791873,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVbSNZvJ2mEGV8uGhtFA2A8Y4_eE5wNUks5quMr8gaJpZM4KHUxG
.

Also having this problem on windows 10. I'm connecting through VPN to my work server.
F:\>pgfutter_windows_amd64.exe --host <IP_ADDRESS> --port 5432 --username xxxxx --pass xxxx  --dbname gesermapa --schema PSR csv PSR2006_teste2.csv --d ";"
I get:
pq: relation "PSR.psr2006_teste2" does not exist
Version:
PostgreSQL 9.3.9 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit
By the way, thank you for this tool.


Stepper - stepper content is overlapping

After creating a new app and pasting the code from docs, the content is not full width. Most likely the issue is the w-100 class instead of w-full.

personnaly I changed if to w-screen like this :
`

      Duis aute irure dolor in reprehenderit in voluptate velit esse
      cillum dolore eu fugiat nulla pariatur.

`


Bundle uninstall and snapshot

Supports bundle install and auto-reinstall for snapshot POSTs.
Doesn't do anything for auto-upgrade but if you POST a new snapshot ZIP then redeploy, the newer version gets used.  Also cleanly uninstalls catalog items.

Failure due to deadlock described and fixed in #671 .  Tests pass locally.

@ahgittin have made a start to this but not got all the way through it yet; looks great; I like the tests testClassAccessAfterUninstall and friends

I have finally got round to doing a test on this, sorry to have taken so long.
I will attach a couple of zip files here for test purposes, each being a separate -SNAPSHOT revision of a simple blueprint. The second builds upon the first, getting a bit more complicated.
My first test zip file causes an error when I try to upload it; what you see on the command line is
br catalog add file://$(pwd)/test672a.zip
json: cannot unmarshal string into Go value of type models.CatalogEntitySummary

and in the Karaf log you get
2017-05-26 15:46:42,844 WARN  121 o.a.b.u.c.j.ErrorAndToStringUnknownTypeSerializer [qtp941342355-186] Standard serialization not possible for class org.apache.brooklyn.rest.resources.CatalogResource$BundleInstallationRestResult (org.apache.brooklyn.rest.resources.CatalogResource$BundleInstallationRestResult@3f7a9dbf)
... lots of repetition deleted...
com.fasterxml.jackson.databind.JsonMappingException: Infinite recursion (StackOverflowError) (through reference chain: org.apache.brooklyn.core.relations.ByObjectBasicRelationSupport["source"]->org.apache.brooklyn.core.typereg.BasicManagedBundle["relations"]->org.apache.brooklyn.core.relations.ByObjectBasicRelationSupport["source"]->org.apache.brooklyn.core.typereg.BasicManagedBundle["relations"]->org.apache.brookly
        at com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:694)
        at com.fasterxml.jackson.databind.ser.BeanSerializer.serialize(BeanSerializer.java:157)
        at com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:672)
        at com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:678)
        at com.fasterxml.jackson.databind.ser.BeanSerializer.serialize(BeanSerializer.java:157)
        at com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:672)
        ... many lines deleted...

I tested the same file against master and it loads ok there, so I think there is something in the PR to cause this.
I will see if I can make a bit of time next week to look at this again and investigate what's going on.

Test files attached (both cause the problem described above.
test672a.zip
test672b.zip

Test files attached (both cause the problem described above.
test672a.zip
test672b.zip

This should address everything, including backwards compatibility so the existing CLI works (though it doesn't show the detail).  New PR coming for the CLI to be able to show the detail.
All changes minor and obvious in light of the PR except for https://github.com/apache/brooklyn-server/pull/672/commits/33d9fd63aae2f7da3b2467bba3e47df8269d5acd#diff-3da051230841536d82a7bcceabdb280aR113 which has a detailed comment in the code (above the method).  @geomacy LMK if you think that is too bad or worth it as a temporary fix until we have a new /bundles endpoint.

@ahgittin changes look good.  I'm comfortable with the variant return type on createFromArchive, especially given the @Beta annotation on it.  I shall pull this and try to get my test going and hopefully merge.

Tests all look good, I added test672a.zip to catalog
[geoff:] master(+0/-889)* ± br catalog add test672a.zip
myTestEnt:0.12.0.SNAPSHOT
myOtherTest:0.12.0.SNAPSHOT
testent1:0.12.0.SNAPSHOT

then deployed a testEnt1 from it, then added the revised snapshot version of the blueprint by adding  test672b.zip:
[geoff:] master(+0/-889)* ± br catalog add test672b.zip
myTestEnt:0.12.0.SNAPSHOT
myOtherTest:0.12.0.SNAPSHOT
myOtherTest2:0.12.0.SNAPSHOT
furtherTest:0.12.0.SNAPSHOT
testent1:0.12.0.SNAPSHOT
testent2:0.12.0.SNAPSHOT

and again deployed a testEnt1; on this second deployment the updated definition from the second zip was used and the entity created with two children.
LGTM, will merge.

Thanks @geomacy.  Merged https://github.com/apache/brooklyn-client/pull/53 following @Graeme-Miller 's review there but as I'm a go newbie (g00b ?) appreciate any comments you have there.

Thanks @geomacy for the super-quick follow-up fix in #719.

I've been catching up on some of the merged PRs and noticed the following. When doing br catalog add . with the following catalog.bom in the folder:
brooklyn.catalog:
  bundle: org.apache.brooklyn.test
  version: "0.1.0-SNAPSHOT"
  itemType: entity
  item:
    type: org.apache.brooklyn.core.test.entity.TestEntity

I get the error:
Server error (400): invalid version "0.1.0-SNAPSHOT": non-numeric "0-SNAPSHOT": NumberFormatException: For input string: "0-SNAPSHOT"

In catalog.bom we are using maven style versioning and the OSGi style of versioning differs from it, mostly by enforcing a .delimiter for the extra tags. It's not restricted to SNAPSHOT versions (which is not a special version in OSGi). It applies to any tagged version.
The code must take this into account and:

Convert maven style versions to osgi style versions when initializing the bundle metadata. There's OsgiUtils.toOsgiVersion(String) to do the mapping which uses the same code as maven does to do the conversion.
Keep the duality hidden to the internals. The version from catalog.bom should be the one we see the catalog item created with, etc.
For the case where there's no catalog.bom and we rely on the MANIFEST.MF - try to get the maven version and use that for the user-visible parts. For example Implementation-Version header  or pom.properties. Fallback to the Version header when no alternative source is available.
The conversion is one way - we can't recover the maven version from an OSGi version. This means we can't directly map from a bundle version to a catalog version without additional metadata.

Very good point Svet.  I got my test above working with snapshot versions exactly by supplying the OSGI version in the bom, without really thinking about whether that was the right thing to do or not:
brooklyn.catalog:
  bundle: io.cloudsoft.cli44
  version: 0.12.0.SNAPSHOT

but indeed it's not right that someone should have to do that.
+1 to your bullets above.

P.S. I can have a look at implementing those changes, unless anyone else is particularly keen to do so?

@neykov @geomacy I've been working in this area for a different reason - if people use v1 as a version a few minor things break.
wdyt about using OSGi versions everywhere, treating anything else including maven versions, as legacy/deprecated?  i'm hoping in future all catalog item versions inherit from the bundle version, IE we stop versioning items separately, but that needs to be discussed.  (if you installed a non-bundle BOM and bundle would be created.)
for convenience if uploading a bundle with a maven (non-osgi) version, we should convert it (one-way) to an osgi version, and also log a warning.  if we do that i guess there is a question should we use the converted-to-osgi version string for items that inherit (items that define their own version will use what they define but if that differs from bundle maybe we will warn?)

@ahgittin re. the version numbers;  suggest we take this to the mailing list to disuss, but my feeling is that people are used to using Maven versions and it's convenient to regard those as "the" version for a module ( = bundle). Could be annoying/error-prone to have to maintain both a version in a pom.xml and another (separate, but almost the same) version in a catalog.bom.

I'm not sold on the idea, but that could be because I spend too much time in Java land.
OSGi style versioning feels niche - not widely known/used. It's more restrictive. We'll still need to special case SNAPSHOT even though it's not a thing in OSGi. semver which is much wider used, even outside of the Java community, better matches our current (maven) versioning style.
I like the vision of having bundle-first design, but feel it's hidden from the user so we are free not not leak the details to the UI.
In any case this deserves a mailing list discussion.

Thanks @geomacy @neykov -- good points.  Will research and take to ML.

Results of ML discussion summarised in https://github.com/apache/brooklyn-docs/pull/198 , with PR to follow on this project implementing that (which will be referenced there)


Update version in NPM

Problem:
Would it be possible to update the NPM repository with the current version here?  I'm using https://github.com/SortableJS/Vue.Draggable and am having the same issue mentioned in #1644 and resolved with e979370.  It would be great to be able to update the dependency in Vue.Draggable.
JSBin/JSFiddle demonstrating the problem:
N/A

Released in 1.10.2


How to get stats in Model retraining using training_data_stats in LimeTabularExplainer?

After creating first model and explainer (1st), and generating data stats using QuartileDiscretizer,
For Retraining
In next model and explainer (2nd), we use training_data_stats in LimeTabularExplainer,
how to create data stats from the 3rd explainer for future retraining?
data stats will have means, stds, maxs, mins, feature_values and feature_frequencies

whether all to be updated or only feature_frequencies?
How to update?

Thanks

Didn't we have this conversation in #461? :)
I don't  know if I have anything new to add there...


Can I still specify the database name in @Database after 4.1?

DBFlow Version:
v4.2.4
Bug or Feature Request:
Can I still specify the database name in @Database after 4.1?
Description:
Can I still specify the database name in @Database after 4.1? I like this way, especially in multiple database modules.
And how do I modify the database name before 4.1?

yes you can. but its much more preferred using it on creation with the DatabaseConfig so you can have dynamic naming.

pre 4.1 its probably not supported if I remember it was added in 4.1.

Thank you very much


Installation problem

Hi, I'm following these installation directions, however, libRCTMaterialKit.a is not available to me when I try to add it to Linked Frameworks and Libraries. It's probably something really simple, hoping you can point me in the right direction.
Cheers

forgive me: user error. had the project open in another xcode workspace which caused the issue. once i closed the other project, i was able to link libRCTMaterialKit.a


Implement it into API Fortress repo

As part of the action to welcome Sauce's new acquisition, and step by step incorporating it to OSPO, add Check-My-Repo into their GitHub

Just made a call with Simone, by tomorrow it should be implemented :)


[test_quality_of_service] Failures

colcon test --packages-select test_quality_of_service
86% tests passed, 3 tests failed out of 22

Label Time Summary:
copyright     =   1.68 sec*proc (1 test)
cppcheck      =   0.39 sec*proc (1 test)
cpplint       =   0.62 sec*proc (1 test)
gtest         = 109.42 sec*proc (16 tests)
lint_cmake    =   0.38 sec*proc (1 test)
linter        =   4.23 sec*proc (6 tests)
uncrustify    =   0.43 sec*proc (1 test)
xmllint       =   0.72 sec*proc (1 test)

Total Test time (real) = 113.66 sec

The following tests FAILED:
	 13 - test_deadline__rmw_zenoh_cpp (Failed)
	 15 - test_liveliness__rmw_zenoh_cpp (Failed)
	 16 - test_best_available__rmw_zenoh_cpp (Failed)

Tests fail as these event types are not yet supported in rmw_zenoh
13 - test_deadline__rmw_zenoh_cpp
[INFO] [1713435048.611577533] [subscriber]: created subscriber subscriber test_deadline
unknown file: Failure
C++ exception with description "Failed to initialize event: provided event_type 7 is not supported by rmw_zenoh_cpp, at /home/yadunund/ros2_rolling/src/rmw_zenoh/rmw_zenoh_cpp/src/rmw_event.cpp:52" thrown in the test body.

15 - test_liveliness__rmw_zenoh_cpp
[INFO] [1713435203.641990760] [subscriber]: created subscriber subscriber test_automatic_liveliness_changed
unknown file: Failure
C++ exception with description "Failed to initialize event: provided event_type 0 is not supported by rmw_zenoh_cpp, at /home/yadunund/ros2_rolling/src/rmw_zenoh/rmw_zenoh_cpp/src/rmw_event.cpp:105" thrown in the test body.

16 - test_best_available__rmw_zenoh_cpp
Failures are related to deadline and liveliness_lease_duration
[INFO] [1713435303.382419270] [subscriber]: created subscriber subscriber /test_best_available_subscription
/home/yadunund/ros2_rolling/src/ros2/system_tests/test_quality_of_service/test/test_best_available.cpp:87: Failure
Expected equality of these values:
  actual_qos.deadline()
    Which is: 16-byte object <78-AB B4-AC 1B-7F 00-00 00-00 00-00 00-00 00-00>
  publisher_qos_profile.deadline()
    Which is: 16-byte object <78-AB B4-AC 1B-7F 00-00 80-84 1E-00 00-00 00-00>

/home/yadunund/ros2_rolling/src/ros2/system_tests/test_quality_of_service/test/test_best_available.cpp:89: Failure
Expected equality of these values:
  actual_qos.liveliness_lease_duration()
    Which is: 16-byte object <78-AB B4-AC 1B-7F 00-00 00-00 00-00 00-00 00-00>
  publisher_qos_profile.liveliness_lease_duration()
    Which is: 16-byte object <78-AB B4-AC 1B-7F 00-00 C0-C6 2D-00 00-00 00-00>

[  FAILED  ] QosRclcppTestFixture__rmw_zenoh_cpp.test_best_available_policies_subscription (1533 ms)
[ RUN      ] QosRclcppTestFixture__rmw_zenoh_cpp.test_best_available_policies_publisher
[INFO] [1713435303.901693591] [rmw_zenoh_cpp]: Successfully connected to a Zenoh router with id 6678b139223765f71bf21f1c8967c71.
[INFO] [1713435304.903443449] [publisher]: created publisher publisher /test_best_available_publisher

[INFO] [1713435304.904354009] [subscriber]: created subscriber subscriber /test_best_available_publisher
/home/yadunund/ros2_rolling/src/ros2/system_tests/test_quality_of_service/test/test_best_available.cpp:147: Failure
Expected equality of these values:
  actual_qos.deadline()
    Which is: 16-byte object <78-AB B4-AC 1B-7F 00-00 00-00 00-00 00-00 00-00>
  subscription_qos_profile.deadline()
    Which is: 16-byte object <78-AB B4-AC 1B-7F 00-00 80-84 1E-00 00-00 00-00>

/home/yadunund/ros2_rolling/src/ros2/system_tests/test_quality_of_service/test/test_best_available.cpp:148: Failure
Expected equality of these values:
  actual_qos.liveliness()
    Which is: 4-byte object <01-00 00-00>
  subscription_qos_profile.liveliness()
    Which is: 4-byte object <03-00 00-00>

/home/yadunund/ros2_rolling/src/ros2/system_tests/test_quality_of_service/test/test_best_available.cpp:149: Failure
Expected equality of these values:
  actual_qos.liveliness_lease_duration()
    Which is: 16-byte object <78-AB B4-AC 1B-7F 00-00 00-00 00-00 00-00 00-00>
  subscription_qos_profile.liveliness_lease_duration()
    Which is: 16-byte object <78-AB B4-AC 1B-7F 00-00 C0-C6 2D-00 00-00 00-00>

@Yadunund A friendly ping to handle this issue.
At the waffle meeting, we decided to assign it to you, but I don't have permission to do so.

This is still a problem on the latest as of today.

Tests skipped for now https://github.com/ros2/system_tests/pull/551


mprocs 0.7.0-rc1 throws Error: invalid type: map, expected a Value::Tagged enum when stop uses send-keys on Windows

Here is the sample config to reproduce the issue:
procs:
  dev:
    shell: 'npm run dev'
    stop:
      send-keys:
        - <C-c>

The issue is specific to the Windows operating system. I tried to narrow down the particular commit that triggered the problem, however, the Windows build already had issues right after the release of v0.6.4. I suspect that the update of serde/serde_yaml  may have caused the problem, but I am not entirely certain.

Thanks for reporting! Indeed looks like serde or serde_yaml changed deserialization a bit. Fixed in
f324470


Cannot redeclare Ybazli\Faker\string()

when using this faker in tests if i have more than one function in a classTest this error thrown

Here is my TestClass
<?php

namespace Modules\Easyshop\Tests;

use Laravel\Passport\Passport;
use Modules\Easyshop\Models\Buyer;
use Modules\Easyshop\Models\Good;
use Tests\TestCase;

class BuyerGoodTest extends TestCase
{
    /**
     * A basic unit test example.
     *
     * @return void
    */
    public function testIndex()
    {

        Passport::actingAs(
            factory(Buyer::class)->make(),
            [], //scopes
            'api_buyer'
        );

        $response = $this->json('GET', '/api/easyshop/v1/buyer/good', ['seller_id' => 5]);
        $response->assertStatus(200);

        $response->assertJson([
            'is_successful' => true,
        ]);

        $response->assertJsonStructure(
            [

                'is_successful',
                'data' => [
                    '*' => [
                        "id",
                        "seller_id",
                        "good_cat_id",
                        "title",
                        "content",
                        "featured_image",
                        "type",
                        "main_price",
                        "real_price",
                        "discount",
                        "is_special",
                        "is_exist",
                        "created_at",
                        "updated_at",
                        "deleted_at",
                        "is_liked",
                    ],
                ],

            ]
        );
    }

    public function testShow()
    {

        Passport::actingAs(
            factory(Buyer::class)->create(),
            [], //scopes
            'api_buyer'
        );

        $good = Good::first();

        $response = $this->json('GET', '/api/easyshop/v1/buyer/good/show', ['good_id' => $good->id]);
        $response->assertStatus(200);

        $response->assertJson([
            'is_successful' => true,
        ]);

        $response->assertJsonStructure(
            [

                'is_successful',
                'data' => [

                    "id",
                    "title",
                    "content",
                    "featured_image",
                    "type",
                    "main_price",
                    "real_price",
                    "discount",
                    "good_cat_id",
                    "seller_id",
                    "is_liked",
                    "seller" => [
                        "id",
                        "shop_name",
                    ],

                ],

            ]
        );
    }
}

I have the same issue right now. Looks like you've merged the menkaff's PR but you haven't released it so when I do composer require ybazli/faker I get the old ( broken ) code.

Hi @xperator are you using dev master version?

@menkaff Um... I just follow the instruction written on the main page. ( I run composer require ybazli/faker )
Am I supposed to do something else to get the latest code?

Check composer.json that using dev-master , like this
"ybazli/faker": "dev-master

Please check composer.json to be like this
"ybazli/faker": "dev-master"

@menkaff Thanks a lot! It's working now.


Get trigger char when using multiple triggers

I am doing something like this:
$(".editor-textarea").mentionsInput({trigger: "#@", source: global_base_url + 'home/get_user_friends'});
I want to be able to distinguish when the users # or @ so I can lookup the correct database table of terms and return them as such. The only data currently being sent is term
Anyone got a solution for this?

I managed to solve this issue by keeping the trigger character next to the value in the hidden input. So instead of username it would appear @username.
I changed the following line (160):
this.searchTerm = match[1];


fixed references to 'webpack.configure.js' in readme

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Move violation message below billable field

Details
Moves the error message below the field on billable.
To do this I:

added a wrapper view around the violation messages
added style override props to to allow for alignment of the text

Fixed Issues
$ https://github.com/Expensify/App/issues/36481
Tests
Pre-requisite: as an employee of a workspace, create an expense with Billable option toggled on.

As the admin of the workspace on OD, set "Re-bill expenses to clients" to Disabled.
As the employee on ND, go to the details page of the created expense.
The message "Billable no longer valid" should be displayed below the billable field.

[ ] Verify that no errors appear in the JS console

Offline tests
N/A
QA Steps
Pre-requisite: as an employee of a workspace, create an expense with Billable option toggled on.

As the admin of the workspace on OldDot, set "Re-bill expenses to clients" to Disabled
As the employee on NewDot, go to the details page of the created expense.
The message "Billable no longer valid" should be displayed below the billable field.

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or
production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using
the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer.
Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using
the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels
should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "
index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working
as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (
i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code
blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component
like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged
out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos
Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari
Having HTTPS issues with the website on iOS, but didn't want to hold up the PR for them. I checked in desktop safari and it was fine.

MacOS: Chrome / Safari

MacOS: Desktop

@trevor-coleman I am confused by your comment

Because of the difference between web and native, just moving the messages below wasn't working, so I ended up leaving the violation messages where they are adding override props to the container and text styles that let me put them where they needed to be.

I am seeing that this PR just moved the message below View

Sorry in the original issue we talked about moving the ViolationMessages component below the containing view in the code.

Should be good to go now.

Just want to flag that tomorrow is my last day on the project, and I won't be available for further updates after that.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/amyevans in version: 1.4.43-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.43-20 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@aimane-chnaif Was an issue created when you reviewed this to pay for this issue? Making sure so we can close the original one

@aimane-chnaif Ok, I will create an issue for the payment then


No docs/example on parameter option

The -p options is not intuitive, we need to documents that key-value pairs are added to a params map and should be accessed through it.

Done in #55


[BUG] Precision errors in distances tests

Describe the bug
main now failing with distance tests
https://github.com/aeon-toolkit/aeon/actions/runs/6380932188/job/17316532763#step:6:910
proably easily solved with assert almost equal
Steps/Code to reproduce the bug
No response
Expected results
pass tests
Actual results

FAILED aeon/distances/tests/test_distances.py::test_distances[dist12] - AssertionError: assert 7.221098545890512 == 7.221098545890511
 +  where 7.221098545890511 = compute_distance(array([[ 0.81217268, -0.30587821, -0.26408588, -0.53648431,  0.43270381]]), array([[-0.20837892, -0.02813341, -1.06809805,  0.8201354 , -0.[896](https://github.com/aeon-toolkit/aeon/actions/runs/6380932188/job/17316532763#step:6:897)71779,\n        -0.42087368,  0.25144071, -0.62264404, -0.52[897](https://github.com/aeon-toolkit/aeon/actions/runs/6380932188/job/17316532763#step:6:898)611, -0.45450381]]), metric='shape_dtw')
FAILED aeon/distances/tests/test_pairwise.py::test_new_single_to_multiple_distances[dist12] - AssertionError: assert False
 +  where False = <function array_equal at 0x1099b2440>(array([[5.37288218, 2.74676541, 2.50430024]]), array([[5.37288218, 2.74676541, 2.50430024]]))
 +    where <function array_equal at 0x1099b2440> = np.array_equal
 +    and   array([[5.37288218, 2.74676541, 2.50430024]]) = compute_pairwise_distance(array([[ 0.81217268, -0.30587821, -0.26408588, -0.53648431,  0.43270381]]), array([[[-0.20837892, -0.02813341, -1.06809805,  0.8201354 ,\n         -0.89671779]],\n\n       [[-0.42087368,  0.2514407...2897611,\n         -0.45450381]],\n\n       [[ 0.27572702,  1.14610401,  0.0207697 , -0.55896272,\n          0.26952916]]]), metric='shape_dtw')
FAILED aeon/distances/tests/test_pairwise.py::test_pairwise_distance[dist12] - AssertionError: assert False

Versions
No response

@chrisholder
extra line left in here (test_distances), seem to be doing the same thing, once with == once with almost equals? Also notice from aeon.distances import distance still uses metric rather than distance

def _validate_distance_result(x, y, name, distance, expected_result=10):
    if expected_result is None:
        return

    dist_result = distance(x, y)

    assert isinstance(dist_result, float)
    assert_almost_equal(dist_result, expected_result)
    assert dist_result == compute_distance(x, y, metric=name)
    assert_almost_equal(dist_result, compute_distance(x, y, metric=distance))

    dist_result_to_self = distance(x, x)
    assert isinstance(dist_result_to_self, float)


feature - page menu detail

Github Issue URL/Tags (required)
What's this PR do? Please give a technical summary (required)

[x] create page menu detail, comment
[x] edit detail UI

Any references (stackoverflow …) (optional)

:+1: There are no linter violations.


Invalid GeoJSON when using NULL as ID

Update: never mind, party on. I wasn't paying attention, this issue's origin is mapbox/geojsonhint, filed it there. Excuse me, close please.
This is not according to specification. The only thing that is stated in the spec. about the identifier is the following:

If a feature has a commonly used identifier, that identifier should be included as a member of the feature object with the name "id".

http://geojson.org/geojson-spec.html#feature-objects
Since nothing else is mentioned about the type of ID, it should adhere to the JSON spec where the property of an object can be any of the following: String, Number, null, true, false, Array or Object

Yep, resolved over at the geojsonhint repo. Non-number-string-undefined ids are valid in GeoJSON 1.0 but soon will be invalid in draft-geojson, and so we validate for the future.


Fix main README

Problem
The Repository Structure section contains an error where the 3.processing_features section does not have purpose and the description was added in that area instead.
Solution
In a small PR, move the description to the correct section and add a purpose.

Issue has been resolved.


Get NoMethodError when there is an example that expect an api to raise 500 error

The example that will cause the problem:
it do
  expect{ subject }.to raise_error(RuntimeError, 'Invalid Buffer')
end

Backtraces
         9: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/mustache-1.1.1/lib/mustache/context.rb:112:in `each'
         8: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/mustache-1.1.1/lib/mustache/context.rb:116:in `block in fetch'
         7: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/mustache-1.1.1/lib/mustache/context.rb:148:in `find'
         6: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/mustache-1.1.1/lib/mustache/context.rb:148:in `call'
         5: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/rspec_api_documentation-6.1.0/lib/rspec_api_documentation/views/api_blueprint_example.
rb:22:in `requests'
         4: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/rspec_api_documentation-6.1.0/lib/rspec_api_documentation/views/markup_example.rb:50:i
n `requests'
         3: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/rspec_api_documentation-6.1.0/lib/rspec_api_documentation/views/markup_example.rb:16:i
n `method_missing'
         2: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/rspec_api_documentation-6.1.0/lib/rspec_api_documentation/example.rb:58:in `requests'
         1: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/rspec_api_documentation-6.1.0/lib/rspec_api_documentation/example.rb:65:in `filter_hea
ders'
/home/khiav/.rvm/gems/ruby-2.5.5/gems/rspec_api_documentation-6.1.0/lib/rspec_api_documentation/example.rb:71:in `remap_headers': undefined m
ethod `each' for nil:NilClass (NoMethodError)

+1

seems like we just need buy-in to write a PR to fix it (and how it should fix it)

@bf4 In general I'm of the opinion that your API endpoints shouldn't knowingly raise, and you should have a catch all for situations you didn't predict, but maybe there's a reason to do this?

In our case I had an acceptance test that asserted the action wasn't routed
    example "PATCH update" do
      expect {
        do_request
      }.to raise_error(ActionController::RoutingError, /No route matches/)
    end

which I think is reasonable, though I should probably just tag it as document: false in that case, I suppose. Maybe that's the fix? rescue the error and asked if you mean to mark document: false?

@bf4 does your app not rescue this error and provide a response to the client?


Update 03_Requirements.md

Update Blocking section to reflect new vendor path. The previous example was not working.

Thank you, I didn’t know about that syntax. Do you happen to know where it is explained in the documentation?
I have updated the commit.

docs here: https://docs.silverstripe.org/en/4/developer_guides/templates/requirements/#direct-resource-urls


Enumerator should be able to access only open Form

Closes sec#2
What has been done to verify that this works as intended?
Integration tests + Manual testing
Why is this the best possible solution? Were any other approaches considered?
Discussed the solution over Slack
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
None
Does this change require updates to the API documentation? If so, please update docs/api.md as part of this PR.
No
Before submitting this PR, please make sure you have:

[x] run make test-full and confirmed all checks still pass OR confirm CircleCI build passes
[x] verified that any code from external sources are properly credited in comments or that everything is internally sourced

Very helpful explanation, that sounds reasonable to me. I can see how there are tradeoffs here. It's a tricky problem!

Just to make sure I'm understanding, Data Collectors will still be able to access closing forms over the API, right? So they'll see a closing form in the form list, but then Frontend will restrict them from actually navigating to the form page? If that's the case, I'm thinking of filing a separate Frontend issue about that. Frontend could hide closing forms from Data Collectors in the forms table.

I'm thinking of filing a separate Frontend issue about that. Frontend could hide closing forms from Data Collectors in the forms table.

I am not sure what's the ideal here. We allow "App Users" and "Public links" to submit against "Closing Forms", by that logic "Data Collector" should also be able to submit. But if they can't see the form in the form list then how are they gonna submit, by saving Enketo URL somewhere offline?


Fix bug during the search by upgrading to Meilisearch v0.28.1 (at least)

I open this issue to ensure we don't forget it, I already discussed it with @mdubus.
Since a pretty annoying bug during the search is present in v0.28.0, I recommend upgrading Meilisearch to v0.28.1 or later.

We've now upgraded to Meilisearch v1.0 =)


Downloading URL Don't working,get a 502 Error

Speech Model's url don't work.

+1

Please try again. It should work now

Thanks


🙈 move the docs to the cop chart 🙈

What is this PR About?
moving the team docs into the cop chart
How do we test this?
just the docs ;)
cc: @redhat-cop/day-in-the-life

As we didn't change anything in the templates, it's okay to merge even though the lint job's failed :)
/lgtm
/approve


Adding social media icons in the footer

please assign this issue to me I would like to work on it for hactoberfest


Question: how to draw the red trajectories

You have done a great job. I have a question, how do you draw the red trajectories shown on the websites, any tool recommendations?

Hi! We use Blender to draw the curves. :)


feat: enable support for Terraform 1.0

Updating this module to work with Terraform versions up to, but not including, 1.1.
Tested this using both 0.15.3 and 1.0.2 deployments, both worked as expected.

thank you @andrew-wiggins !