Plugins installed with wrong ownership

I've just upgraded from 0.9.9 to 0.10.2 of this plugin, and it looks like https://github.com/elastic/puppet-elasticsearch/issues/107 has returned.  Plugins are installed/owned by root, which means they can't be read by the elasticsearch user when starting ES.  I was able to get around this by running the following manually:
chown -R elasticsearch.elasticsearch /usr/share/elasticsearch/plugins/

Hi. I have some plugin tests and none of them have shown issues loading them in elasticsearch.
They are with the elasticsearch user but they should be readable by the elasticsearch user. Can you check the mode set on the directory and files ?

/usr/share/elasticsearch/plugins is owned by elasticsearch as expected, but /usr/share/elasticsearch/plugins/marvel is owned by root after the plugin installs.  Note, I am still on v1.7 of ES.  Here is the relevant part of my class:
    $instance_name = 'vagrant'
    elasticsearch::plugin { 'elasticsearch/marvel/latest':
        instances  => $instance_name,
    }

To reproduce all I need to do is manually remove the plugin (/usr/share/elasticsearch/bin/plugin -r marvel) and then run vagrant provision to trigger a Puppet run.

Did a quick check and everything has -rw-r--r-- as rights. so everything is readable for everyone.

Just checked, and while the root plugin dir has the expected permissions, the individual plugin dirs do not:
drwxr-xr-x 4 elasticsearch elasticsearch 4.0K Jan 26 13:08 /usr/share/elasticsearch/plugins
drwxr-x--- 3 root          root          4.0K Jan 28 10:30 /usr/share/elasticsearch/plugins/marvel

Hi,
I'll do some more digging into it this week.

Same problem here after upgrading ES versions. Perms seemed fine prior to upgrading ES and all I did was tell it a new verison of the plugin + es.
[root@cxpxelk02mas001 ~]# ls -al /usr/share/elasticsearch/plugins/
total 16
drwx------. 4 root          root          4096 Apr  8 09:41 .
drwxr-xr-x. 8 elasticsearch elasticsearch 4096 Apr  8 09:41 ..
drwx------. 2 root          root          4096 Apr  8 09:41 license
drwx------. 2 root          root          4096 Apr  8 09:41 marvel-agent

Same with puppetmodule for elasticsearch v10.3 and Elasticsearch 2.3
Plugin Folder Owner is root not elasticsearch.
Result is:```
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/elasticsearch_plugin: Could not autoload puppet/provider/elasticsearch_plugin/plugin: undefined method `[]' for Facter:Module at /etc/puppetlabs/code/environments/ciso_master/external_modules/elasticsearch/manifests/plugin.pp:134:7 at /etc/puppetlabs/code/environments/ciso_master/services/cselastic/manifests/init.pp:44 on node cselasticdbbsba01.db.server.lan
Warning: Not using cache on failed catalog

Same problem here with the kopf plugin. (using offline installation)
worked around this issue by adding the next block of code to our profile, but it would be ideal if the module would take care of this:
  if ($ensure=='present') {     file { $path_plugins:       ensure  => directory,       owner   => $es_user,       group   => $es_group,       recurse => true,     }   }
ES 2.3.3
Kopf 2.1.2
Puppet module: 0.13.1

Frustrating to see a new release of the module where this is still a problem. Have had to work around this with hacky exec calls and file resources to get EC2 discovery and ElasticHQ installed and enabled with the correct permissions 😞

I'm curious as to what issue people are experiencing with this?
I have the same issue that the plugins are being installed with root:root ownership but the permissions are in such a way that they are readable and executable by elasticsearch user, so there are no errors on puppet runs and plugins are running without issue.
I'm using module 0.11.0 and ES 2.3.3 and there are no issues loading the plugins (kopf, head, marvel, etc)

I also can't reproduce the behavior cited here; the plugin permissions and mode I'm seeing are also root:root but with read privileges for all, so plugins seem to work correctly in my testing scenario.
However, given the issues raised here, it's evident we can't assume ownership and mode will be correct; my best guess here is that some customized setups have different umask settings of some sort and are thus restricting the elasticsearch user from reading plugin files.
Bearing in mind the (valid) concerns in #568 regarding permissions granted to the elasticsearch user, it seems the most robust and secure option here is to recursively manage the plugin directory to ensure files and directories are readable for all users (i.e. a+r or something like that). Ensuring plugin source files are owned as the elasticsearch user/bin/plugin is executed as the elasticsearch user stopped happening as of df3047fc when the native provider was swapped in.

this is how the elasticsearch dir looks like after a fresh installation (looks okay):

sudo ls -al /usr/share/elasticsearch/
total 40
drwxr-xr-x.   9 elasticsearch elasticsearch  4096 Aug 17 08:25 .
drwxr-xr-x. 106 root          root           4096 Aug 17 08:25 ..
drwxr-xr-x.   2 root          root            102 Aug 17 08:25 bin
drwxr-xr-x.   2 elasticsearch elasticsearch  4096 Aug 17 08:25 lib
-rw-r--r--.   1 root          root          11358 Jan 27  2016 LICENSE.txt
drwxr-xr-x.   5 root          root             60 Aug 17 08:25 modules
-rw-r--r--.   1 root          root            150 May 12 15:24 NOTICE.txt
drwxr-xr-x.   2 elasticsearch elasticsearch     6 Aug 17 08:25 plugins
-rw-r--r--.   1 root          root           8700 May 12 15:24 README.textile
drwxr-xr-x.   2 elasticsearch elasticsearch     6 Aug 17 08:25 scripts
drwxr-xr-x.   2 root          root              6 Aug 17 08:25 shield
drwxr-xr-x.   2 elasticsearch elasticsearch     6 Aug 17 08:25 templates_import

This is how the plugins dir looks like after plugin installation:

sudo ls -al /usr/share/elasticsearch/plugins/
total 8
drwxr-xr-x. 3 elasticsearch elasticsearch   17 Aug 17 08:29 .
drwxr-xr-x. 9 elasticsearch elasticsearch 4096 Aug 17 08:25 ..
drwxr-x---. 8 root          root          4096 Aug 17 08:29 kopf

As you can see, on my RHEL 7 system (umask = 0027), it is not readable for everyone :(
Also someone decided somewhere between ES 1.7.2 and 2.3.3 that it would be an excellent idea for elasticsearch to FAIL when it can't load one of it's plugins :(

[2016-08-17 08:29:21,877][INFO ][node                     ] [mynode] version[2.3.3], pid[26287], build[218bdf1/2016-05-17T15:40:04Z]
[2016-08-17 08:29:21,877][INFO ][node                     ] [mynode] initializing ...
[2016-08-17 08:29:23,225][ERROR][bootstrap                ] Exception
java.lang.IllegalStateException: Could not load plugin descriptor for existing plugin [kopf]. Was the plugin built before 2.0?

Aug 17 08:29:23 mynode systemd[1]: elasticsearch-myinstance.service: main process exited, code=exited, status=1/FAILURE
Aug 17 08:29:23 mynode systemd[1]: Unit elasticsearch-myinstance.service entered failed state.
Aug 17 08:29:23 mynode systemd[1]: elasticsearch-myinstance.service failed.

If you need more system specific information, let me know.

@RogierSchuring so you are configuring this umask change as it isn't default. I have a EL7 system as well and the default permissions are 0022 umask which is fine. So I'm guessing you are specifying this umask somewhere in your code which is what is causing this problem as that isn't the default?

@cdenneen Its the default setting of the company stack, so unfortunately, i am not allowed to change it.
Seeing that i'm not the only one with the problem, I don't think my company is the only company with the umask set that way ;)

CentOS 6.8 does this in /etc/profiles:
# By default, we want umask to get set. This sets it for login shell
# Current threshold for system reserved uid/gids is 200
# You could check uidgid reservation validity in
# /usr/share/doc/setup-*/uidgid file
if [ $UID -gt 199 ] && [ "`id -gn`" = "`id -un`" ]; then
    umask 002
else
    umask 022
fi

We pre-create the elasticsearch user with a GID > 200, which explains why we're getting wrong permissions in our setup.

Without casting blame here, this is definitely something that arises out of end-user changes to the system, and the module functions entirely correctly out-of-the box by default. This is only an issue when folks make some change that skews the umask that plugins are installed with.
The super conservative response here would be "if you're changing the umask, it's your responsibility to ensure the fallout doesn't break anything", but practically, the module does some shifty things to figure out what the plugin directory name is, so it's far easier to control this directly in the module where we can reliably determine the plugin directory's name.
The changeset in #685 makes that happen by ensuring the relevant plugin dir is (basically) chmod -R o+Xr. The change should be in the next release.

Thanks @tylerjl.  To be clear, we're not explicitly changing the umask, it's a side effect of specifying our own UID/GID for the elasticsearch user, which I imagine is a common practice especially for large deployments with managed user accounts.  This fix looks like it will do the job, thanks so much!

@tylerjl to be fair the fact that puppet runs as root is what makes the plugins install as root. If ES is meant to run as non-root user then the module should change the ownership of the installed plugins or runas es user. You could login as es user on a server and install the plugins and the ownership would be correct so this is actually more of a side effect of the puppet run.
I know with puppet Exec you can specify a different user, is the same possible when using a puppet Type like this?

The question of whether the running service should have the same effective user ID as the plugin files is an open one. While we could run the elasticsearch service as the elasticsearch user and ensure that chown -R elasticsearch:elasticsearch /usr/share/elasticsearch, the concern raised is #568 still valid. That is, if someone gets control of the Elasticsearch daemon, the goal should be to limit the possible damage done to the system with as few paths writable to the daemon as possible - this is pretty unavoidable for the Elasticsearch data directory, but there's really no reason the running daemon needs ownership and thus write permissions for the plugin directory - it just needs to read plugin source files.
I'm aware that this definitely isn't the case for many of the paths that ship with Elasticsearch packages out-of-the box, but we can certainly move the in the right direction regardless. 👍
P.S. FWIW I still don't know what the best practice is for setting an effective user ID for shell commands within custom types/providers - my guess is that the "correct" approach would be to recursively manage directory owner/group similar to the way it's managing the mode now, but I'd love to learn if that's not the case 🎱

Thanks @tylerjl

I just updated to 0.13.2, and this still broken for me.  It looks like permissions are set correctly on the individual plugin dirs, but not on the /usr/share/elasticsearch/plugins dir itself:
01:36 PM [vagrant@vagrant /] ls -lh /usr/share/elasticsearch
total 60K
drwxr-xr-x 2 root          root          4.0K Aug 29 13:25 bin
drwxr-x--- 3 elasticsearch elasticsearch 4.0K Aug 29 13:25 data
drwxr-xr-x 2 elasticsearch elasticsearch 4.0K Aug 29 13:25 lib
-rw-r--r-- 1 root          root           12K Jun 30 04:22 LICENSE.txt
drwxr-xr-x 5 root          root          4.0K Aug 29 13:25 modules
-rw-r--r-- 1 root          root           150 Jun 30 04:22 NOTICE.txt
drwxr-x--- 3 root          root          4.0K Aug 29 13:25 plugins
-rw-r--r-- 1 root          root          8.5K Jun 30 04:22 README.textile
drwxr-xr-x 2 elasticsearch elasticsearch 4.0K Aug 29 13:25 scripts
drwxr-xr-x 2 root          root          4.0K Aug 29 13:25 shield
drwxr-xr-x 2 elasticsearch elasticsearch 4.0K Aug 29 13:25 templates_import

Starting ES in this state gives the following error:
Unable to access 'path.plugins' (/usr/share/elasticsearch/plugins)
If I manually fix the permissions, it works:
01:36 PM [vagrant@vagrant /] chmod o+Xr /usr/share/elasticsearch/plugins/
01:36 PM [vagrant@vagrant /] ls -lh /usr/share/elasticsearch
total 60K
drwxr-xr-x 2 root          root          4.0K Aug 29 13:25 bin
drwxr-x--- 3 elasticsearch elasticsearch 4.0K Aug 29 13:25 data
drwxr-xr-x 2 elasticsearch elasticsearch 4.0K Aug 29 13:25 lib
-rw-r--r-- 1 root          root           12K Jun 30 04:22 LICENSE.txt
drwxr-xr-x 5 root          root          4.0K Aug 29 13:25 modules
-rw-r--r-- 1 root          root           150 Jun 30 04:22 NOTICE.txt
drwxr-xr-x 3 root          root          4.0K Aug 29 13:25 plugins
-rw-r--r-- 1 root          root          8.5K Jun 30 04:22 README.textile
drwxr-xr-x 2 elasticsearch elasticsearch 4.0K Aug 29 13:25 scripts
drwxr-xr-x 2 root          root          4.0K Aug 29 13:25 shield
drwxr-xr-x 2 elasticsearch elasticsearch 4.0K Aug 29 13:25 templates_import

@tylerjl Can the module update permissions on the plugins dir itself as well?

Dang - sorry about that. The dangers of fixing issues without reproducing a viable test case in CI. 🎲
Given that all the subdirectories of plugin/ are being managed now, the only thing that needs to be changed is adding a mode => 'o+Xr' at https://github.com/elastic/puppet-elasticsearch/blob/0.13.2/manifests/config.pp#L140 (with an added parameter to check the mode at https://github.com/elastic/puppet-elasticsearch/blob/0.13.2/spec/classes/000_elasticsearch_init_spec.rb#L279).
Should be an easy fix, I'll open a new ticket to track it and get it into another minor bugfix release.


feat(search-table): delete PSearchTable component

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[x] Not that difficult

Type of Change

[x] New feature
[ ] Bug fixes
[ ] Feature improvement

[ ] These changes require a usage change

[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[ ] Updated Storybook documents for component
[ ] Wrote test codes for composable, utils and etc.
[x] Tested with console(if usages are changed)

Description

delete PSearchTable component

:tada: This PR is included in version 2.0.0-beta.55 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Release ports during delete operation

Daemon is long running process and with usermode networking we expose
some of the ports to host and same happen when user uses podman bundle
and expose port for a container. Now those ports are remain exposed until
daemon process is stopped and started again. This PR try to use unexpose
api from the usermode networking and release all the ports which is exposed
by the process once user execute delete.
➜  macos-amd64 git:(dev) crc start
➜  macos-amd64 git:(dev) sudo netstat -p tcp -van | grep '^Proto\|LISTEN'
Password:
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)     rhiwat shiwat    pid   epid  state    options
tcp46      0      0  *.9090                 *.*                    LISTEN<PHONE_NUMBER>72  67452      0 0x0100 0x00000006
tcp46      0      0  *.2222                 *.*                    LISTEN<PHONE_NUMBER>72  67452      0 0x0100 0x00000006
[..]
➜  macos-amd64 git:(dev) podman run --log-level=debug -d -p 8081:80 docker.io/httpd:2.4
2849e69f4798613aa1aec8b8ce5d8481fd636ddfb3be6df125e184ae64c29a5c
➜  macos-amd64 git:(dev) sudo netstat -p tcp -van | grep '^Proto\|LISTEN'
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)     rhiwat shiwat    pid   epid  state    options
tcp46      0      0  *.8081                 *.*                    LISTEN<PHONE_NUMBER>72  67452      0 0x0100 0x00000006
tcp46      0      0  *.9090                 *.*                    LISTEN<PHONE_NUMBER>72  67452      0 0x0100 0x00000006
tcp46      0      0  *.2222                 *.*                    LISTEN<PHONE_NUMBER>72  67452      0 0x0100 0x00000006
[...]
➜  macos-amd64 git:(dev) ./crc delete
➜  macos-amd64 git:(dev) sudo netstat -p tcp -van | grep '^Proto\|LISTEN'
<no_port_bind_to_crc_daemon_process>

Looks like something which should be done on stop as well?

@cfergeau yes, I do need to check the behavior of podman-machine in this regard and can create a separate PR.


adjust for 0.28.0 Mesos build

I was working on this last night also. If we combine this with my work, this should work. Closing an opening a new PR.


error fetching answer please try again

click also error

I am having this same issue when trying to use this from another computer on the same network

are you accessing this from the computer you installed it on or another computer on your network?

I'm having the same issue -- using an ec2 machine and accessing it from my computer. It's a CORS error. Thanks!


Adding packages inconsistently doesn't load the actors

Commands:
cl = j.servers.threebot.local_start_default(web=True)
cl.actors.package_manager.package_add(git_url="https://github.com/threebotapps/interface.git")
cl.actors.package_manager.package_add(git_url="https://github.com/threebotapps/contacts.git")

When running the commands above the UI start and I can access it but the actors don't always start, I then have to restart the 3bot, clear bcdb and sometimes use 'js_init generate'. To make to work.
Looking at the logs with 'tmux at' doesn't show any errors whatsoever.

It could be related to the order the packages are loaded and the rules NGINX uses.
If I switch contacts and interface around it seems to be working little bit more consistent.

you need to do cl.reload afterwards.

@MathiasDeWeerdt please close if this fixes your issue

This fix will enable fix that when called from gedis http https://github.com/threefoldtech/jumpscaleX_threebot/issues/232.

Verified
If it is wanted in the same kosmos session , reload should be used.


Error on running docker exec -it catalog-mongo /bin/bash

@mehmetozkaya
I am able to successfully install container for mongo DB and but executing command for mongo DB throws below error.
C:\Users\ashishjain4>docker ps
CONTAINER ID   IMAGE     COMMAND                  CREATED          STATUS          PORTS                      NAMES
039ab1536008   mongo     "mongod --bind_ip_all"   39 seconds ago   Up 36 seconds   <IP_ADDRESS>:27017->27017/tcp   catalog-mongo
C:\Users\ashishjain4>docker exec -it catalog-mongo /bin/bash
container bce995a3638f836b3ddf864e0bf002c658f5c3901264a444f8b89b0fd6e80f16 encountered an error during hcsshim::System::CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2)
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail: onecore\vm\compute\management\orchestration\vmhostedcontainer\processmanagement.cpp(173)\vmcomputeagent.exe!00007FF6F18F9D2B: (caller: 00007FF6F18AE13A) Exception(9) tid(3f4) 80070002 The system cannot find the file specified.
CallContext:[\Bridge_ProcessMessage\VmHostedContainer_ExecuteProcess]
Provider: 00000000-0000-0000-0000-000000000000] extra info: {"CommandLine":"/bin/bash","WorkingDirectory":"/","Environment":{"MONGO_DOWNLOAD_SHA256":"d811282527bbdc3266244209ad0971c0d375dbb209bb8eb4ae66ba576b19e9f6","MONGO_DOWNLOAD_URL":"https://fastdl.mongodb.org/windows/mongodb-windows-x86_64-4.4.3-signed.msi","MONGO_VERSION":"4.4.3"},"EmulateConsole":true,"CreateStdInPipe":true,"CreateStdOutPipe":true,"ConsoleSize":[0,0]}

Actually it was worked for me but not sure that why its happened. When I checked the official image;
https://hub.docker.com/_/mongo
I saw that below part, so could you try with only bash instead of bin/bash
Container shell access and viewing MongoDB logs
The docker exec command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your mongo container:
$ docker exec -it some-mongo bash

Actually it was worked for me but not sure that why its happened. When I checked the official image;
https://hub.docker.com/_/mongo
I saw that below part, so could you try with only bash instead of bin/bash
Container shell access and viewing MongoDB logs
The docker exec command allows you to run commands inside a Docker container.  Please find screenshot below.
I am stuck here now.

@mehmetozkaya

Still having same issue. Please find screenshot below.
I am stuck here now.

@mehmetozkaya

I also don't know why it is giving this error but if you can try with fresh test with delete and re-create mongo image and try. If nothing change then it could be network problem that you can't insert your docker image from your computer.

I also don't know why it is giving this error but if you can try with fresh test with delete and re-create mongo image and try. If nothing change then it could be network problem that you can't insert your docker image from your computer.

Thanks for the response. I tried all . may be its with mongo DB something . I will try this out with Sql instead of mongo and creating Catalog DB over there.
thanks for your support
@mehmetozkaya

Thanks for the response. I tried all . may be its with mongo DB something . I will try this out with Sql instead of mongo and creating Catalog DB over there.
thanks for your support
@mehmetozkaya

I ran into the same issue. We need to use mongosh instead of mongo
Found solution  found the solution here
https://stackoverflow.com/questions/73582703/mongo-command-not-found-on-mongodb-6-0-docker-container


Update README for custom analyzer.

Add related sample code in get started section.
Add explanation in get started steps.

@gyllstromk Feel free to leave any comments if there needs any modification.

thanks a lot and sorry for the delay!


Suspend session for an Livepeer.com active stream and block new sessions

This new feature will allow a .com user to stop an ongoing stream. This should end any in progress session and prevent new sessions from being started with the same stream key. It will also allow a Livepeer admin to stop ANY active stream, and add it into the admin interface.
Requirements:

New boolean parameter on the parent stream object suspend. The default is false, and it should be hidden by default in the stream object response.

When suspend is set to true, end any in progress session and prevent new sessions from being started with the same stream key.

The suspend parameter does not need to exist on "child" stream objects (sessions).

In the Livepeer.com dashboard, on the stream page we will add a checkbox Recording with the label Suspend and block.

By default this will be unchecked.
When a user checks the box, display a pop-up saying "Are you sure you want to suspend and block this stream? Any active stream sessions will immediately end. New sessions will be prevented from starting until unchecked." The user will need to click the "Confirm" button before the new setting takes effect.
When a user unchecks the box, display a pop-up saying "Are you sure you want to allow new stream sessions again?" The user will need to click the "Confirm" button before the new setting takes effect.

For Livepeer.com admins we will also need to display the Terminate and block checkbox on ALL stream pages.

I moved this back to in review because it doesn't work on livepeer.monster yet.


Fixing bug 1145616 and 1145613 in samples used by accessibility test team.

Fixes issues #349 and #350.
Description
The AddProduct window of DataBindingDemo sample has two fields that should be required, Date and Start price, but it was not marked as required. I added a * character to indicate this in the text, and included this information on the AutomationProperties.Name property of both Controls.
Also, I added a TextBlock to show an error whenever a user press the AddProduct button with invalid Date or StartPrice values. If one of them is empty, this text tells the user to fill in both, and if there is an error with the input, it also tells the user. This label is a LivingRegion so it also seen by the narrator.
Customer Impact
When using the sample app, the user would not know both Date and StartPrice are required, and when the AddProduct button was pressed with invalid inputs for those field, it would not show an error message.
Regression
No. This sample is used for Accessibility testing and never fully supported Narrator.
Testing
The sample project was tested using narrator to assert the informations are being said.

Thanks, Felipe!


TECH-187: Create test configuration for "/{GovStackInstance}/{memberClass}/{memberCode}/{applicationCode}/listMethods" endpoint

Created mocks and Cucumber tests for "/{GovStackInstance}/{memberClass}/{memberCode}/{applicationCode}/listMethods" endpoint
Description
Create test configuration for /{GovStackInstance}/{memberClass}/{memberCode}/{applicationCode}/listMethods endpoint from  https://github.com/GovStackWorkingGroup/bb-information-mediator/blob/main/api/govstack_im_service_metadata_api-0.3-swagger.json.  This should include all the steps that are pointed out in the parent ticket.
TICKET: https://govstack-global.atlassian.net/browse/TECH-187

LGTM !

@aleksander-reitsakas i changed those regexes. Let me know please if identifiers should allow other signs like _ or -
If you could provide an example it would be great.
Also the spec doesn't provide response in case those values are invalid.Should it be 400? As in getOpenAPI endpoint?


CommentNode#equals() results in an infinite loop

Hey @mattbdean, I'm using DiffUtils when displaying comments in my app for animating changes. I'm seeing a problem where calling equals() on the same CommentNode is resulting in an infinite loop.
~I'm not sure if I understand this correctly, but CommentNode#equals() calls equals on both its~
~parent node and its children node, which ends in an endless loop.~
Update: something else is triggering an infinite loop. Matt, does this sound familiar to you?

My first thought would be that this line is causing it like you suggested. How'd you rule that out?

Because I replaced parent.equals(that.parent) with parent.comment.getFullName().equals(that.parent.comment.getFullName()) and the error was still there.

Can you post the relevant code?

@mattbdean are you referring to my DiffUtils implementation? or the modified CommentNode#equals()?

Both

@Saketme did you ever figure out the issue?

Whoops, I totally forgot about this issue. I could not figure out what exactly was triggering the loop, because I eventually ended up changing my implementation which depended on this :(


Issues with migrating to multi envs from a previous custom multi env setup

Note: I initially sent this to the amplify team email and was told to post here. If anyone has any feedback on this it would be greatly appreciated 🙌🏻.
Issue:
Our team has been trying to migrate our amplify-cli to the latest version and we’re reaching out for advice on how to proceed as we’ve run into some issues. Our setup is a little unique which makes it a bit more challenging than using the migration tool or following the manual migration guide.
Our project is React and prior to trying to migrate we were using version 0.1.42 of the CLI. Since multiple environments weren’t supported until version 1.0 we created two configs, appended .staging or .production to the files, and copied those files to the amplify defined locations based on the environment we were trying to target.
Unfortunately this setup is fragile and somewhere along the way our #current-cloud-backend for our staging and production targets fell out of step with what is actually there. With version 0.1.42 we can’t pull or restore the environment to get the #current-cloud-backend. In our specific case we’ve pushed storage and the S3 buckets are live, but amplify status shows that it wants to Create the resource.
Since this didn’t work we’ve tried upgrading to the latest version of the cli, 3.9.0, and following the migration guide to use multiple environments. I’m familiar with how the new cli now uses the env name to name and create resources. However we already have the names and resources defined so I’ve tried skipping the conditions around the env variable and using amplify env checkout to add the configs per environment.
After migrating we are able to use amplify status and get a response. But we’re still unable to restore the #current-cloud-backend with amplify env pull or using the restore flag. The error we receive is that the key for the resource doesn’t exist when it tried to do the pull. They key it’s looking for is #current-cloud-backend.zip.
So right now we’re a bit stuck on adding new Amplify features or modifying existing configs until we can finish this migration and sync with the #current-cloud-backend.
What we’re looking for is advice on how to proceed with this migration without affecting our production environment. The staging environment can be reprovisioned and if we need to migrate to new user pools we can do that to. Using amplify push in this scenario seems risky and we want to make sure we get this right.

@wmcbain Did you get an error log - stating if the migration failed or succeeded?

@wmcbain Also, it'll be super helpful to know your current directory structure after the migration and what's the error you're getting when trying to push again or creating a new environment.

@kaustavghosh06
I did not use amplify migrate as we have two environments that already exist within the project. I've migrated our staging configuration using the manual migration guide. However I've avoided adding the conditions to the templates that change resource names based on the env variable.
I've made some progress but I'm still catching errors trying to amplify push.
$ amplify push

Current Environment: staging

| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Auth     | Staging       | Update    | awscloudformation |
| Storage  | Staging       | No Change | awscloudformation |
? Are you sure you want to continue? Yes
⠹ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          app-redacted-123 AWS::CloudFormation::Stack Wed Sep 25 2019 15:52:48 GMT-0400 (Eastern Daylight Time) User Initiated
UPDATE_IN_PROGRESS          UnauthRole           AWS::IAM::Role             Wed Sep 25 2019 15:52:51 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS          AuthRole             AWS::IAM::Role             Wed Sep 25 2019 15:52:51 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS          storageStaging       AWS::CloudFormation::Stack Wed Sep 25 2019 15:52:51 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS          authStaging          AWS::CloudFormation::Stack Wed Sep 25 2019 15:52:51 GMT-0400 (Eastern Daylight Time)
UPDATE_FAILED               storageStaging       AWS::CloudFormation::Stack Wed Sep 25 2019 15:52:51 GMT-0400 (Eastern Daylight Time) Parameters: [env] do not exist in the template
UPDATE_COMPLETE             authStaging          AWS::CloudFormation::Stack Wed Sep 25 2019 15:52:51 GMT-0400 (Eastern Daylight Time)
UPDATE_FAILED               UnauthRole           AWS::IAM::Role             Wed Sep 25 2019 15:52:51 GMT-0400 (Eastern Daylight Time) Resource update cancelled
UPDATE_FAILED               AuthRole             AWS::IAM::Role             Wed Sep 25 2019 15:52:51 GMT-0400 (Eastern Daylight Time) Resource update cancelled
UPDATE_ROLLBACK_IN_PROGRESS app-redacted-123 AWS::CloudFormation::Stack Wed Sep 25 2019 15:52:52 GMT-0400 (Eastern Daylight Time) The following resource(s) failed to update: [AuthRole, storageStaging, UnauthRole].
⠴ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS authStaging        AWS::CloudFormation::Stack Wed Sep 25 2019 15:53:03 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS AuthRole           AWS::IAM::Role             Wed Sep 25 2019 15:53:03 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS UnauthRole         AWS::IAM::Role             Wed Sep 25 2019 15:53:03 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE    storageStaging     AWS::CloudFormation::Stack Wed Sep 25 2019 15:53:03 GMT-0400 (Eastern Daylight Time)
⠹ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE authStaging AWS::CloudFormation::Stack Wed Sep 25 2019 15:53:03 GMT-0400 (Eastern Daylight Time)
⠹ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              UnauthRole           AWS::IAM::Role             Wed Sep 25 2019 15:53:20 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              AuthRole             AWS::IAM::Role             Wed Sep 25 2019 15:53:20 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS app-redacted-123 AWS::CloudFormation::Stack Wed Sep 25 2019 15:53:21 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS                           storageStaging   AWS::CloudFormation::Stack Wed Sep 25 2019 15:53:22 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS                           authStaging     AWS::CloudFormation::Stack Wed Sep 25 2019 15:53:22 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              storageStaging   AWS::CloudFormation::Stack Wed Sep 25 2019 15:53:22 GMT-0400 (Eastern Daylight Time)
UPDATE_COMPLETE                              authStaging     AWS::CloudFormation::Stack Wed Sep 25 2019 15:53:22 GMT-0400 (Eastern Daylight Time)
UPDATE_ROLLBACK_COMPLETE                     app-redacted-123 AWS::CloudFormation::Stack Wed Sep 25 2019 15:53:22 GMT-0400 (Eastern Daylight Time)
⠸ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
⠦ Updating resources in the cloud. This may take a few minutes...

Following resources failed

Resource Name: app-redacted-123-authRole (AWS::IAM::Role)
Event Type: update
Reason: Resource update cancelled
URL: https://console.aws.amazon.com/cloudformation/home?region=us-east-2#/stacks/arn%3Aaws%3Acloudformation%3Aus-east-2%3A686711563431%3Astack%2Fapp-redacted-123%2F5f4720e0-baa4-11e8-b387-020cf0d94894/events

Resource Name: app-redacted-123-unauthRole (AWS::IAM::Role)
Event Type: update
Reason: Resource update cancelled
URL: https://console.aws.amazon.com/cloudformation/home?region=us-east-2#/stacks/arn%3Aaws%3Acloudformation%3Aus-east-2%3A686711563431%3Astack%2Fapp-redacted-123%2F5f4720e0-baa4-11e8-b387-020cf0d94894/events

@wmcbain "UPDATE_FAILED               storageStaging       AWS::CloudFormation::Stack Wed Sep 25 2019 15:52:51 GMT-0400 (Eastern Daylight Time) Parameters: [env] do not exist in the template
^This is the main issue. If you add the "env" as a parameter in your Cloudformation templates, you should be good - since the CLI auto-injects the env parameter as input for each of the Cloudformation templates at deploy time. So if the Cloudformation tempaltes don't have "env" as an input parameter, you would see Cloudformation failures like the one above. The auto-migration would've injected this in your templates.

@kaustavghosh06 Sorry for going silent on this issue but I was still blocked by this and needed tome onto other work.
I'm still seeing this failure and the error isn't making a lot of sense. I'm including the env parameter in the template:
  "Parameters": {
    "bucketName": {
      "Type": "String"
    },
    "authPolicyName": {
      "Type": "String"
    },
    "unauthPolicyName": {
      "Type": "String"
    },
    "authRoleName": {
      "Type": "String"
    },
    "unauthRoleName": {
      "Type": "String"
    },
    "unauthPermissions": {
      "Type": "String"
    },
    "authPermissions": {
      "Type": "String"
    },
    "env": {
      "Type": "String"
    }
  },

However when I run amplify push I still get the following error:
UPDATE_FAILED               storageuserStorage   AWS::CloudFormation::Stack Wed Oct 02 2019 12:04:10 GMT-0400 (Eastern Daylight Time) Parameters: [env] do not exist in the template
UPDATE_FAILED               UnauthRole           AWS::IAM::Role             Wed Oct 02 2019 12:04:10 GMT-0400 (Eastern Daylight Time) Resource update cancelled
UPDATE_FAILED               AuthRole             AWS::IAM::Role             Wed Oct 02 2019 12:04:10 GMT-0400 (Eastern Daylight Time) Resource update cancelled


Investigate testing

We haven't investigated that at all yet

https://github.com/ctrlplusb/prisma2-pg-jest by @crtlplusb
Sent with GitHawk

What can we learn from https://github.com/prisma/prisma-test-utils?
Sent with GitHawk

Hm, narrowing the scope of this issue to be about just an example would make it a subset of #229 and #228 I think.


Save Conflict Compare Tab Not Working

Make unsaved changes to a file.
Open the file in another editor (e.g. Notepad) and make and save come changes.
Return to VSCode and save the file.  VSCode will warn you of newer changes to file.
Click compare.

See GIF below.  I have also tried this with --disable-extensions.

Please see if you can find any logged output that could help us find the source of the issue:

run code --verbose from the command line and attach the output
in Code select Help | Toggle Developer Tools and select the Console
attach any output you see in the Console you can find

Thanks!

Sorry, I tried this again with extensions disabled and it appears to work fine when extensions are disabled.  I assume it must be an extension somewhere.  Not sure what happened the other day.  Feel free to close the issue and I'll see if I can track down the extension and recreate it with the author.
Here are the logs anyway:

--verbose:

[main 2020-07-13T20:41:19.375Z] Sending some foreground love to the running instance: 22372
[main 2020-07-13T20:41:19.378Z] Sending env to running instance...
[main 2020-07-13T20:41:19.491Z] Sent env to running instance. Terminating...
[main 2020-07-13T20:41:19.491Z] Lifecycle#kill()

Console:

abstractExtensionService.ts:415 [ms-vscode.powershell]: Command `workbench.action.debug.start` appears multiple times in the `commands` section.
abstractExtensionService.ts:415 [ms-vscode.powershell]: Command `workbench.action.closePanel` appears multiple times in the `commands` section.
abstractExtensionService.ts:415 [ms-vscode.powershell]: Command `workbench.action.positionPanelLeft` appears multiple times in the `commands` section.
abstractExtensionService.ts:415 [ms-vscode.powershell]: Command `workbench.action.positionPanelBottom` appears multiple times in the `commands` section.
7abstractExtensionService.ts:415 [MehediDracula.php-namespace-resolver]: Menu item references the same command as default and alt-command
TMScopeRegistry.ts:45 Overwriting grammar scope name to file mapping for scope source.graphql.
Old grammar file: file:///c%3A/Users/Abdullah/.vscode/extensions/apollographql.vscode-apollo-1.16.5/syntaxes/graphql.json.
New grammar file: file:///c%3A/Users/Abdullah/.vscode/extensions/kumar-harsh.graphql-for-vscode-1.15.3/syntaxes/graphql.json
register @ TMScopeRegistry.ts:45
TMScopeRegistry.ts:45 Overwriting grammar scope name to file mapping for scope inline.graphql.
Old grammar file: file:///c%3A/Users/Abdullah/.vscode/extensions/apollographql.vscode-apollo-1.16.5/syntaxes/graphql.js.json.
New grammar file: file:///c%3A/Users/Abdullah/.vscode/extensions/kumar-harsh.graphql-for-vscode-1.15.3/syntaxes/graphql.js.json
register @ TMScopeRegistry.ts:45
console.ts:137 [Extension Host] Starting express server on port: 58821 (at LocalWebServer.start (c:\Users\Abdullah\.vscode\extensions\vsciot-vscode.vscode-arduino-0.3.1\out\src\arduino\localWebServer.js:32:17))
console.ts:137 [Extension Host] using default c:\Users\Abdullah\.vscode\extensions\vsciot-vscode.vscode-arduino-0.3.1\out\node_modules\usb-detection\build\Release\detection.node (at Object.loadLibrary [as load] (c:\Users\Abdullah\.vscode\extensions\vsciot-vscode.vscode-arduino-0.3.1\out\node_modules\node-usb-native\lib\native_loader.js:15:13))
console.ts:137 [Extension Host] using default<EMAIL_ADDRESS>(at Object.loadLibrary [as load] (c:\Users\Abdullah\.vscode\extensions\vsciot-vscode.vscode-arduino-0.3.1\out\node_modules\node-usb-native\lib\native_loader.js:15:13))
console.ts:137 [Extension Host] Error: Document version already has changed	at c:\Users\Abdullah\.vscode\extensions\naumovs.color-highlight-2.3.0\dist\extension.js:2903:17	at processTicksAndRejections (internal/process/task_queues.js:85:5) (at c:\Users\Abdullah\.vscode\extensions\naumovs.color-highlight-2.3.0\dist\extension.js:2938:24)
log.ts:197   ERR [text file model] handleSaveError(7) - exit - resulted in a save error: Error: Unable to write file 'c:\Users\Abdullah\test.txt' (Error: File Modified Since) file:///c:/Users/Abdullah/test.txt
notificationsAlerts.ts:40 Failed to save 'test.txt': The content of the file is newer.  Consider marking event handler as 'passive' to make the page more responsive. See

Console with extensions disabled:

log.ts:197   ERR [text file model] handleSaveError(2) - exit - resulted in a save error: Error: Unable to write file 'c:\Users\Abdullah\test.txt' (Error: File Modified Since) file:///c:/Users/Abdullah/test.txt
notificationsAlerts.ts:40 Failed to save 'test.txt': The content of the file is newer. Please compare your version with the file contents or overwrite the content of the file with your changes.
event.ts:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
event.ts:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952


Bug fixes for running locally

A few small changes and the return of a missing function to allow develop to run bug free again.

Are you actually getting energy spectra? Can you show a histogram of what you are getting?
I am getting a bunch of NaNs
You can get rid of the commented lines - the git history will still have it if we need to go back (seems unlikely)

[test.py.txt](https://github.com/Helium6CRES/he6-cres-spec-sims/files/12457001/test.py.txt)

I am not seeing that error. I tried running a much higher statistics run and am now seeing rarely a integration nonconvergence warning:
IntegrationWarning: The algorithm does not converge.  Roundoff error is detected   in the extrapolation table.  It is assumed that the requested tolerance   cannot be achieved, and that the returned result (if full_output = 1) is   the best which can be obtained.   T_a = 4 / velocity(energy) * integrate.quad(sec_theta, 0, zmax)[0]
However, this warning does not appear to break anything like yours.
Here is a histogram of energies. Looks like we may be calling cobs incorrectly.

@buzinsky You can go ahead and test. The spectra are being pulled correctly, the shape we see is different because we always test the same number of betas at each field.

Done with my comments, hopefully you got them. Once those two (.png & gitignore) are resolved, you are good to merge


Remember to update btstack

We need this fix https://github.com/bluekitchen/btstack/commit/24d14ae36e95f1a6b777d41469836b4230ab79cc

merged into develop


Build Failed - unable to download minecraftforge:forgeSrc

After downloading the pre-built version 0.22.0 on Windows and following the "Launching Minecraft with our Mod" instructions, I receive the following build failed error after running ".\launchClient.bat":
============================================
FAILURE: Build failed with an exception.

Where:
Build file 'C:\Users\User\Documents\Project Malmo\Malmo-0.22.0-Windows-64bit\Minecraft\build.gradle' line: 57

What went wrong:
A problem occurred configuring root project 'Minecraft'.

Could not resolve all dependencies for configuration ':forgeGradleMc'.
Could not find net.minecraftforge:forgeSrc:1.8-<IP_ADDRESS>3.
Searched in the following locations:
http://files.minecraftforge.net/maven/net/minecraftforge/forgeSrc/1.8-<IP_ADDRESS>3/forgeSrc-1.8-<IP_ADDRESS>3.po
m
http://files.minecraftforge.net/maven/net/minecraftforge/forgeSrc/1.8-<IP_ADDRESS>3/forgeSrc-1.8-<IP_ADDRESS>3.ja
r
https://repo1.maven.org/maven2/net/minecraftforge/forgeSrc/1.8-<IP_ADDRESS>3/forgeSrc-1.8-<IP_ADDRESS>3.pom
https://repo1.maven.org/maven2/net/minecraftforge/forgeSrc/1.8-<IP_ADDRESS>3/forgeSrc-1.8-<IP_ADDRESS>3.jar
https://libraries.minecraft.net/net/minecraftforge/forgeSrc/1.8-<IP_ADDRESS>3/forgeSrc-1.8-<IP_ADDRESS>3.pom
https://libraries.minecraft.net/net/minecraftforge/forgeSrc/1.8-<IP_ADDRESS>3/forgeSrc-1.8-<IP_ADDRESS>3.jar
file:/C:/Users/User/.gradle/caches/minecraft/deobfedDeps/net/minecraftforge/forgeSrc/1.8-<IP_ADDRESS>3/forgeSrc
-1.8-<IP_ADDRESS>3.pom
file:/C:/Users/User/.gradle/caches/minecraft/deobfedDeps/net/minecraftforge/forgeSrc/1.8-<IP_ADDRESS>3/forgeSrc
-1.8-<IP_ADDRESS>3.jar
file:/C:/Users/User/.gradle/caches/minecraft/net/minecraftforge/forge/1.8-<IP_ADDRESS>3/snapshot/20141130/forge
Src-1.8-<IP_ADDRESS>3.jar
file:/C:/Users/User/.gradle/caches/minecraft/net/minecraftforge/forge/1.8-<IP_ADDRESS>3/snapshot/20141130/forge
Src.jar
Required by:
com.microsoft.MalmoMod:Minecraft:0.22.0
=============================================================

The build is successful when I run the command for version 0.21.0. Any suggestions? Thank you in advance.

*Solved
It was a firewall access issue.

Well thank you for this post tho!  I had the same issue. You helped me out there haha.
Running with sudo bypassed firewall 😄

Well I have the same issue, and disabling firewall did not help.
In fact, if you look at the links the script is trying to access, they all give 404's back, as if the files it is trying to download don't exist on the specified urls.

This seems to be a problem with Forge - hopefully they will get it fixed soon, but in the meantime we'll look into workarounds. I don't think it's to do with Malmo 0.22 vs 0.21 - gradle caches its dependencies, so if forgeSrc has been downloaded successfully in the past, it should continue to work unless the cache is cleared. New installations of Malmo will experience this problem - we're reproduced it here and on our continuous build server.

Thanks for the confirmation. Let's hope they fix it soon.

I encountered the same problem, hoping it get fixed soon.

Well, it looks like I owe Forge an apology... the problem seems to have been caused by some code I added into build.gradle myself, though quite why it's causing the problem remains a bit of a mystery...
We will release new binaries that contain this fix in due course, but in the meantime, the fix can be applied manually fairly easily as follows:

Find build.gradle inside the Minecraft folder.
Either replace it with the latest version from master - https://github.com/Microsoft/malmo/blob/master/Minecraft/build.gradle - or edit it manually to remove the afterEvaluate section (around line 48).

Alternatively, manually creating a file called runMC.sh (or runMC.bat on Windows) inside the Minecraft folder also seems to "fix" things.
Hopefully this should get everyone back up and running - do let me know if not!

FWIW, I think the issue is as follows:
If you look at the list in the error message, (under where it says Searched in the following locations), you can see that, after failing to download the files, it looks in the gradle cache for them.
These files get put in the cache by the setupDecompWorkspace gradle task - so the broken links are a red herring: with everything working "normally", the files are generated, not downloaded.
Unfortunately, the afterEvaluate code I added apparently forces gradle to resolve the forgeGradleMc dependencies before these files have been generated, leading to the error.
If these files are already cached, of course, this is fine. And once runMC.sh exists, the code never runs again, so even trashing the gradle cache won't reproduce the error if runMC.sh exists. All of which nicely masks the real issue...

Can confirm that the latest build.gradle from master solves the issue.

@DaveyBiggers Removing the afterEvaluate section in build.gradle solved the problem. Thanks

Fixed by removing the afterEvaluate section.

The pre-built release of 0.22 for windows still has this bug. Copying the latest build.gradle over the one in the downloaded release fixes the issue, but the release needs to be updated.

I've re-uploaded the 0.22 windows binaries with this fix - haven't done the same for the other builds, but ideally people should be using 0.30 by now.

Hi all, the problem is here again
Could not resolve all dependencies for configuration ':forgeGradleMc'.
> Could not find forgeSrc.jar (net.minecraftforge:forgeSrc:1.11.2-<IP_ADDRESS>8).
  Searched in the following locations:
      https://files.minecraftforge.net/maven/net/minecraftforge/forgeSrc/1.11.2-<IP_ADDRESS>8/forgeSrc-1.11.2-<IP_ADDRESS>8.jar

The searched jar has an invalid url, it returns 404

Bump


[Feature][scaleph-application-flink] support flink kubernetes operator ingress

Already searched before asking?

[X] I had searched in the feature and found no similar feature requirement.

Usage Scenario
now scaleph only support flink themself service expose and not support flink kubernetes operator ingress
Description
support flink kubernetes operator ingress
Are you willing to submit a PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

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

support ingress

[ ] update nginx-ingress-controller install docs
[ ] add metallb install docs


Error connecting to Harmony Hub

I just installed ha-bridge 3.5.1 on Ubuntu 16.04, and configured my Harmony Hub with the correct IP address (checked the IP address twice in the Harmony Android App to make sure it's the right one) and saved and re-initialized ha-bridge.
But it won't show any Harmony actvities or devices. All I get from the log is this error message:
01-21-2017 21:41:08.668	ERROR	Cannot get harmony client (Wohnzimmer) setup, Exiting with message: null	com.bwssystems.harmony.HarmonyHome
I also tried rebooting my Ubuntu machine as well as the Harmony Hub (plug/unplug cable). I can ping the Hub from the Ubuntu machine and it shows up on my router network page.
Any advice?
Thanks!

I had the same issue. Luckily, the Echo supports harmony devices natively.

Sadly this is not the case here in Germany - the Echo discovers the Harmony hub but due to a non existent Harmony skill it cannot be used.

@DaRealDan There was an exception that was written to the logfile, (it does not show up in the log tab) that we need to see. Please post the exception.
Thanks

Here is the exception:
`2017-01-22 19:33:53.663:INFO:oejs.Server:Thread-40: Started @136258ms
2017-01-22 19:33:53,667 [main] ERROR com.bwssystems.harmony.HarmonyHome - Cannot                      get harmony client (Wohnzimmer) setup, Exiting with message: null
java.lang.NullPointerException: null
at org.jivesoftware.smack.sasl.SASLMechanism.authenticate(SASLMechanism.                     java:170)
at org.jivesoftware.smack.sasl.SASLMechanism.authenticate(SASLMechanism.                     java:148)
at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentica                     tion.java:333)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.login(XMPPTCPConnection.                     java:244)
at net.whistlingfish.harmony.HarmonyClient.connect(HarmonyClient.java:11                     6)
at com.bwssystems.harmony.HarmonyServer.execute(HarmonyServer.java:78)
at com.bwssystems.harmony.HarmonyServer.setup(HarmonyServer.java:50)
at com.bwssystems.harmony.HarmonyHome.(HarmonyHome.java:45)
at com.bwssystems.HABridge.HABridge.main(HABridge.java:70)
Exception in thread "main" java.lang.NullPointerException
at com.bwssystems.HABridge.dao.DeviceRepository._loadRepository(DeviceRe                     pository.java:63)
at com.bwssystems.HABridge.dao.DeviceRepository.(DeviceRepository.                     java:49)
at com.bwssystems.HABridge.devicemanagmeent.DeviceResource.(Device                     Resource.java:50)
at com.bwssystems.HABridge.HABridge.main(HABridge.java:80)
`

A question, did you build the ha-bridge yourself or did you use the downloaded jar?

I used the jar provided for version 3.5.1 (wget https://github.com/bwssytems/ha-bridge/releases/download/v3.5.1/ha-bridge-3.5.1.jar)

You have your IP of your hub typed in properly in the bridge control tab? Also, take a look at your habridge.conf file to make sure it saved properly.

Yep, I'm certain I entered the IP correctly (re-checked with Harmony android app Menu->Info->Version->Hub-IP-Address). It's also saved properly. Here is my current habridge.conf:
{"upnpconfigaddress":"<IP_ADDRESS>","serverport":8080,"upnpresponseport":50000,"upnpdevicedb":"data/devices.db","harmonyaddress":{"devices":[{"name":"Wohnzimmer","ip":"<IP_ADDRESS>"}]},"buttonsleep":100,"upnpstrict":true,"traceupnp":false,"veraconfigured":false,"harmonyconfigured":true,"nestconfigured":false,"farenheit":false,"configfile":"data/habridge.config","numberoflogmessages":512,"hueconfigured":false,"halconfigured":false,"whitelist":{"WATuoP2eAz81HwpayUrG3WFnhOcItTpTgkoN403J":{"lastUseDate":"2017-01-22T19:52:35","createDate":"2017-01-22T19:52:35","name":"auto insert user"}},"settingsChanged":true,"myechourl":"alexa.amazon.de/spa/index.html#cards","webaddress":"<IP_ADDRESS>","mqttconfigured":false}

So, lets try the beta for fun, look at #371

Let's get you upgraded to the new release instead of the beta:
https://github.com/bwssytems/ha-bridge/releases/download/v4.0.0/ha-bridge-4.0.0.jar

Updated today, didn't help. Figured, there had to be something wrong with my network - so I unplugged the cable from the fritzbox that was connecting my linux server and plugged it back in a network switch. My network was setup like this: Internet -> Router #1 (this is where the Harmony hub is connected) -> Networkswitch -> Fritzbox 7240 -> Linux Server
Re-initialized the ha-bridge, and connecting to the Harmony Hub did work!
So now all I had to do was figure out what the hell is going on with the fritzbox... Until I figured it out:
For future references, disable "Transmit status information over UPnP" within your fritzbox (mine was a 7240, fritzos 6.06). You can disable it here: "Home Network" -> "Home Network Overview" -> "Network Settings" -> Untick "Transmit status information over UPnP" -> Apply to ave settings. I also unticked the option above UPnP, "Allow access for applications", saved and rebooted. After that the ha-bridge<-> Harmony Hub connection is still working with my linux server plugged into the fritzbox.
Thanks for your help and patience and keep up the good work!

Damn networks! always the hard one to figure out. Glad you got it resolved.


Sample项目貌似无法运行

Describe the bug
根据readme, cd packages/app && npm run app. 发现无法运行，装了依赖包也没法运行
To Reproduce
Steps to reproduce the behavior:

cd packages
yarn
npm run app

Expected behavior
能够正常运行Sample
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

npm run init  初始化一下lerna工程配置 不用单独cd到app目录安装依赖

Describe the bug
根据readme, cd packages/app && npm run app. 发现无法运行，装了依赖包也没法运行
To Reproduce
Steps to reproduce the behavior:

cd packages
yarn
npm run app

Expected behavior
能够正常运行Sample
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

npm run init 初始化一下lerna工程配置 不用单独cd到app目录安装依赖


aop: 13.5 bring up +  mics + als + generalize afk/epic

aop_audio: stream hpai device (high power audio input) microphone samples from aop to admac. output seems to be 32-bit LE floats in groups of 3 (3 mic array)
aop_als: monitor/report red, green, blue, clear, lux, gain etc information from ambient light sensor (ALS)
Tested j293ap 13.5
Also includes afk/epic/rbep generalizations which hopefully don't break DCP

nvm this broke dcp. fixing it

@jannau  I generalized AFK/EPIC code to both DCP and AOP. I feel like I should send these in a separate series but it obviously depends on the above. I think marcan's on holiday. From my tests (dcp/dcp_iboot; I can't test dptx/dcpext) it doesn't break DCP but I'd like to get your ack

Hi, could someone familiar with Asahi Linux and Apple audio help to move this PR or more generally the microphone support forward?


Problems running shim exampe skeleton

I first tried to build the project:
root@ecsHyNL:~/dierbei/rust-extensions# cargo build --example skeleton

Tried to run the program after that, but it failed.
root@ecsHyNL:~/dierbei/rust-extensions# ctr run --rm --runtime ./target/debug/examples/skeleton docker.io/library/hello-world:latest hello
ctr: failed to start shim: start failed: : exec: "/": permission denied: unknown

Containerd version:
root@ecsHyNL:~/dierbei/rust-extensions# containerd -v
containerd github.com/containerd/containerd v1.7.2 0cae528dd6cb557f7201036e9f43420650207b58

OS:
root@ecsHyNL:~/dierbei/rust-extensions# uname -a
Linux ecsHyNL 5.15.0-79-generic #86-Ubuntu SMP Mon Jul 10 16:07:21 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

All operations are performed under the root user.

runtime is assigned by pre-defined config from containerd config file, not support by specific binary file


Saving different settings screens open in different tabs can overwrite with old values

Issue Summary
If you open two settings screens in different tabs, make changes in the first and save, make changes in the second and save, then the second save will have overwritten your changes from the first save with the old values.
Related forum discussion: https://forum.ghost.org/t/editing-code-injection-and-navigation-at-the-same-time-does-not-work/32984/7
Steps to Reproduce

Open "Code injection" settings screen in one tab
Open "Navigation" settings screen in another tab
Enter some text into the code injection fields and save
Make a change on the navigation screen and save
Refresh the code injection screen

After doing this you'll find that the changes you made on the code injection screen have been "undone".
Ghost Version
5.16.0
Node.js Version
16.15.0
How did you install Ghost?
Local
Database type
MySQL 8
Browser & OS version
No response
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

This can potentially be fixed by only saving changed attributes of the Setting model via its serialializer.
There's some example code at the end of the discussion here https://discuss.emberjs.com/t/dirt-tracking-with-ember-data-only-save-dirty-properties/4191/36?u=lookingsideways

Hi, would be willing to work on this issue but do i have to have a framwork knowledge or plain JS would suffice

This is a bug in Ember.js, Kevin has already posted some directions for how to fix it. If you're able to understand the directions and implement the fix then you have enough knowledge :)

Hey Peeps, are you assigning or should i just work on it and open a PR.
happy hacktoberfest to you :)

We are not assigning PRs very welcome though :)

Hi @kevinansfield
I recently switched from wordpress to ghost for my personal blog. I love how simple the application is to use. Thanks for building such a great application.
I also wanted to contribute to this application, so started looking at the code. I have never done any coding using ember but I can make some sense of the code.
I tried the potential solution mentioned here https://github.com/TryGhost/Ghost/issues/15470#issuecomment-1257742840.
serializeAttribute(snapshot, json, key, attributes) {
      if (snapshot.record.get('isNew') || snapshot.changedAttributes()[key]) {
            super.serializeAttribute(snapshot, json, key, attributes);
        }
}

The above code works great and will send only the changed attributes to the API. But it will fail to identify attributes such as navigation: attr('navigation-settings') which has a custom transform.
The above sample code does not recognize changes made to nagivation. I only tested it for this attribute but there might be other attributes too for which it will not work.
Also, API will not like the request if user simply clicks on save without making any changes. Then in this case we will end up sending an empty setting array to the server.
https://github.com/TryGhost/Ghost/blob/main/ghost/api-framework/lib/validators/input/all.js#L130-L136
 if (!['posts', 'tags'].includes(apiConfig.docName)) {
   if (_.isEmpty(frame.data) || _.isEmpty(frame.data[apiConfig.docName]) || _.isEmpty(frame.data[apiConfig.docName][0])) {
     return Promise.reject(new BadRequestError({
       message: tpl(messages.noRootKeyProvided, {
         docName: apiConfig.docName
       })
     }));
   }
 }

I think we need some more discussion on how to proceed.

I was trying to look at this one but I can't get the admin UI to load. The splash screen just shows up and nothing else.

Hey @JohnGrisham - if you need a hand getting a dev environment setup, please use the contributor section of the forum so that the conversation here needs can focus on how to solve the bug 🙂


Move core pre/postinstall logic to Nudge.app and fix calendar issue

All core zsh scripts have been moved to the Nudge.app and are signed
The shebangs have been removed from them
The core postinstall scripts in the packages are moved back to bash

These scripts call the zsh scripts within the Nudge.app, disregarding the global and user zsh environments

Due to these changes, the preinstall script has been retired and placed at the top of the postinstall logic
The "suite" postinstall script has been retired since it is identical code to the other postinstall scripts. These are now called instead

also this fixes https://github.com/macadmins/nudge/issues/557

Adding a note from our Slack discussion about checking to make sure the app is installed, in case someone installs the LaunchAgent or Logger first.


fixed readme file

Codecov Report

Merging #30 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #30   +/-   ##
=========================================
  Coverage     49.19%   49.19%
  Complexity      454      454
=========================================
  Files            85       85
  Lines          2183     2183
  Branches        128      128
=========================================
  Hits           1074     1074
  Misses         1046     1046
  Partials         63       63

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 849759d...3f8da90. Read the comment docs.


Added QRCode GB

@amraboelela can you please correct the merge conflicts and submit to develop. We are trying a submission for QA process, see https://github.com/GuideBlocks-org/iOS-GuideBlocks/wiki

@djinoz pls check now.


readme: spelling & grammar updates

Edited Base Module readme for clarity. No content changes, only changes to grammar, spelling, and formatting.

Updated! Thanks for the feedback


Improve symmetry in client/server address/port text

Attempt to improve symmetry of

(client|server).(address|port)
(client|server).socket.(address|port)

based on @Oberon00's https://github.com/open-telemetry/semantic-conventions/issues/206#issue-1819655650.
I haven't (intentionally) changed any definitions, so I don't think change log is needed, but not a problem to add.

@open-telemetry/specs-semconv-maintainers can this be merged? I'd like to continue iterating on @Oberon00's concerns from #206


feat: allow changing name pattern during watch mode

Closes #658

I tested locally and I can't type the pattern once I select the option. I can only press enter.
The PATTERN label isn't visible due to contrast, at least in my terminal (that I think has a proper font and color theme)

About the wording, Jest uses "Press t to filter by a test name regex pattern.". Maybe we could also expand it to "Change test name pattern"? The testNamePattern casing looks a bit off in the middle of the other options.

I tested locally and I can't type the pattern once I select the option. I can only press enter. The PATTERN label isn't visible due to contrast, at least in my terminal (that I think has a proper font and color theme)

Oh, I did too much refactoring 👀

Changed the color to magenta

Looks good now! And I can type. But if I press backspace it writes "backspace" and if I tried to use uppercase it doesn't let me. I was trying to write "JSON" to filter that one.

Looks good now! And I can type. But if I press backspace it writes "backspace" and if I tried to use uppercase it doesn't let me. I was trying to write "JSON" to filter that one.

Should be fixed 😃
First time using this API!

Works great!
One thing about DX, maybe we shouldn't show the skipped tests when using this option, because if there are a lot of them you don't see the ones that were filtered (for example with JSON in the core tests)

I agree, but this is more about testNamePattern implementation


Code does not compile

As of today, latest code does not compile.
Appears to be referencing missing fields in Song from flute_music_player library (0.0.6)
error: The getter 'Columns' isn't defined for the class 'Song'. (undefined_getter at [musicplayer] lib/database/database_client.dart:38)
error: The setter 'count' isn't defined for the class 'Song'. (undefined_setter at [musicplayer] lib/database/database_client.dart:53)
error: The getter 'timestamp' isn't defined for the class 'Song'. (undefined_getter at [musicplayer] lib/database/database_client.dart:55)
error: The getter 'isFav' isn't defined for the class 'Song'. (undefined_getter at [musicplayer] lib/database/database_client.dart:58)

#1


LogAspect is only applied to core components

Discovered during #956
The LogAspect that is within the core module is only weaved into the core components. An easy solution would be to include the same LogAspect in all other modules.

Experimenting with this issue a bit more: I initially tried to move the aspect into its module, and then declare that module as an aspect library for the plugin during the weaving process. Turns out that is not possible, as it will create a circular dependency. The solution would be to include the aspect class in all modules for now.

What is it depending on that creates the circular dependency?

Why is the waeving not working in submodules?

So, weaving does not work in submodules because the LogAspect is only placed within the core module. The plugin takes an aspect and applies it to that module only. That class is not shared across all other submodules. The correct way to share an aspect across more than one module is to declare it as an aspectLibrary for the plugin itself, assuming it lives elsewhere and it is also a dependency to the project.
This is what I did that ran into a circular dependency:

Created a separate module, moved the LogAspect over and declared/overrode the aspectj plugin in that module to skip weaving. Had to do this because aspectj plugin is shared by all modules by default. It's in the parent pom and part of the normal plugins section.
Added the new module dependency to the parent CAS pom.
added the aspectLibrary to the configuration of the aspectj plugin in the parent pom, and let it point to the module.
Ran compile. Circular dependency. I think it's because the aspect module itself is part of the same project and compiling one against another creates issues like that.

Is LogAspect generic enough that we could publish as its own module (even as a sub-module of Inspektr) to eliminate the circular dependency?

Sure. It makes sense for it to be a standalone jasig library.

I can experiment with Inspektr's submodule to see if that can be made to work. If so, I'll fork it over to Jasig and cut a release before modifying CAS

I have been successful in generalizing inspektr to include a log aspect for org.jasig calls. I will need to cut a quick release, which should happen by Monday, before further working on this issue


Fixes duplicates on tag pages (#354)

See issue #354. A tag page like cake was also using recipes tagged as pancake because it contained the word cake. Since some pancake recipes were also tagged as cake, they appeared twice.
Solution was to specify that grep look for a line that is the name of a tag, instead of seeing if the line contains the name of a tag.

I updated this PR to use awk instead of grep | sed now. After removing the -F.

@sylGauthier Thought I'd include you in on this since you work on blogit.


FB player harness

Simple test tool that feeds JSON to FB video player.

@mbebenita, can you review and merge @mwobensmith's FB test harness? He also has some questions for you about measuring Shumway performance from JS.


isort range formatting deletes lines

          I'm having an issue with lines being removed due to `isort`, probably related.

Test file:
import numpy as np

from A import B
import C

Output if I use conform.format() (works as expected):
import C
import numpy as np
from A import B

Output if I use conform.format({range = {start={1, 0}, ["end"]={4,8}}}) (whole file as range):
import C

I tracked it down to apply_format, in particular indices_in_range here is evaluating to false, so it does the deletion but not the insertion, shown in the lack of a second text edit for the call with a range. If I bypass that line (just saying if true for this test), it works exactly as expected.
trace for no range (conform.format()):
15:06:37[DEBUG] Running formatters on ~/test.py: { "isort" }
15:06:37[INFO] Run isort on ~/test.py
15:06:37[TRACE] Input lines: { "import numpy as np", "", "from A import B", "import C" }
15:06:37[DEBUG] Run command: { "isort", "--stdout", "--filename", "~/test.py", "-" }
15:06:38[DEBUG] isort exited with code 0
15:06:38[TRACE] Output lines: { "import C", "import numpy as np", "from A import B" }
15:06:38[TRACE] Applying formatting to ~/test.py
15:06:38[TRACE] Comparing lines { "import numpy as np", "", "from A import B", "import C" } and { "import C", "import numpy as np", "from A import B" }
15:06:38[TRACE] Diff indices { { 1, 3, 0, 0 }, { 4, 0, 2, 2 } }
15:06:38[TRACE] Applying text edits: { {
    newText = "",
    range = {
      ["end"] = {
        character = 0,
        line = 3
      },
      start = {
        character = 0,
        line = 0
      }
    }
  }, {
    newText = "import numpy as np\nfrom A import B",
    range = {
      ["end"] = {
        character = 0,
        line = 4
      },
      start = {
        character = 0,
        line = 4
      }
    }
  } }
15:06:38[TRACE] Done formatting ~/test.py

trace with a range (conform.format({range = {start={1, 0}, ["end"]={4,8}}})):
15:06:33[DEBUG] Running formatters on ~/test.py: { "isort" }
15:06:33[INFO] Run isort on ~/test.py
15:06:33[TRACE] Input lines: { "import numpy as np", "", "from A import B", "import C" }
15:06:33[DEBUG] Run command: { "isort", "--stdout", "--filename", "~/test.py", "-" }
15:06:33[DEBUG] isort exited with code 0
15:06:33[TRACE] Output lines: { "import C", "import numpy as np", "from A import B" }
15:06:33[TRACE] Applying formatting to ~/test.py
15:06:33[TRACE] Comparing lines { "import numpy as np", "", "from A import B", "import C" } and { "import C", "import numpy as np", "from A import B" }
15:06:33[TRACE] Diff indices { { 1, 3, 0, 0 }, { 4, 0, 2, 2 } }
15:06:33[TRACE] Applying text edits: { {
    newText = "",
    range = {
      ["end"] = {
        character = 0,
        line = 3
      },
      start = {
        character = 0,
        line = 0
      }
    }
  } }
15:06:33[TRACE] Done formatting ~/test.py

Originally posted by @milisims in https://github.com/stevearc/conform.nvim/issues/98#issuecomment-1751803047

This is likely not related to the other issue, so I've moved it to a new issue.
I added some docs under advanced topics that explain the range formatting a little more. As a general rule, the "aftermarket" range formatting that conform offers when a formatter doesn't support it natively is a "best effort" operation and will never be perfect. In this particular case I was able to find a small change that improves the formatting results, but just as a warning this sort of thing can still happen in the future.


cmd: remove SkipArgReorder

Fixes #940
Before:
➜  buildah git:(from-issue) ✗ sudo buildah from scratch --name builder
too many arguments specified

After:
➜  buildah git:(from-issue) ✗ sudo ./buildah from scratch --name builder
builder
➜  buildah git:(from-issue) ✗ sudo buildah containers
CONTAINER ID  BUILDER  IMAGE ID     IMAGE NAME                       CONTAINER NAME
e173e4ed21d3     *                  scratch                          builder

Signed-off-by: Zhou Hao<EMAIL_ADDRESS>

@q384566678, thanks a lot for the PR. Although it fixes the issue, I have some doubts if that's the way to go.
As mentioned in #940, the image is required to be the last argument to buildah-from, which is not the case with the changes in this PR anymore. I am also skeptical towards the reordering of arguments as it can introduce very subtle bugs and some CLI invocations can turn into something quite ambiguous.

Thanks for the PR @q384566678 , but sorry, I concur with @vrothberg .  We don't want to remove the reorder flag for a number of reasons that he stated.  For the buildah from command the last argument should be the image name.  We need to "just" change the error returned in this instance, but I quote the just as I'm not sure it will be a quick and easy fix.

I agree.  We want to be consistent and have the reorder flag in all the tools


[TF 2.0] Provide a tool to convert checkpoints for optimizers, from TF 1.x to TF 2.0.

Checkpoints will break with RNNs and shared embedding columns, which is unfortunate but acceptable. For optimizers, though, checkpoint breaking is a bit more extensive.
Ideally this feature request would result in a function or tool that could take the old checkpoint and some information about the old + new optimizers, and replace the old checkpoint with the new. This should involve some variable renaming, and some new variables added in. (Hyperparameters are now variables, so we will need to add those in to the checkpoints, and set with reasonable values-- either the defaults, or with user-specified values.)
Priority:
P0 - optimizers
P1 - RNNs
P1 - shared embeddings

I'm looking into this, seems reasonably straightforward.

I am also happy to help, @dynamicwebpaige please lemme know if this issue is still open

This Issue Looks Interesting. Anyone working on this issue? Would love to work on this.😄

I have been busier than I imagined, so I've just done some research and haven't started working on it. If the people above that are interested want to start outlining what such a tool would look like I'm happy to collaborate on a solution. Alternatively, I won't be offended if someone just does the whole thing. I'll continue to post as I make progress.

This issue is still up for grabs, and we'd appreciate the help! Supporting information for building the conversion mapping can be found in the two referenced issues (#26350, #26349).

@dynamicwebpaige am i in a right direction.
we are supposed to build a function model.load_weight(convert('old_checkpoint_path'))
that convert function should change the checkpoint data format into the format supported by tf.keras.optimizer.Adam. as tf.train.AdamOptimizer is deprecated in tf2.0.

cp_callback = tf.keras.callbacks.ModelCheckpoint(checkpoint_path,verbose=1)

model = create_model(tf.train.AdamOptimizer,0.01) // model trained using tf.train.AdamOptimizer

model.fit(train_images, train_labels,  epochs = 10,
          validation_data = (test_images,test_labels),
          callbacks = [cp_callback]) // model checkpoint saved

loss, acc = model.evaluate(test_images, test_labels)
print("Trained model, accuracy: {:5.2f}%".format(100*acc))

model = create_model(tf.keras.optimizers.Adam,0.01)

model.load_weights(checkpoint_path) // will cause problem as the format used to save weights by tf.keras.optimizer and tf.train.AdamOptimizer are different

loss, acc = model.evaluate(test_images, test_labels)
print("Untrained model, accuracy: {:5.2f}%".format(100*acc))```

for the P0 item, A checkpoint converter tool for converting optimizers is included with the 2.0.0-beta0 release.
This checkpoint converter tool is mainly for Canned Estimators, including DNN
Linear and DNNLinearCombined estimators. The allowed optimizers to be converted
include Adam, Adagrad, Ftrl, RMSProp, and SGD.
Note that, this converter is not suitable for the case where 'dnn_optimizer'
and 'linear_optimizer' in DNNLinearCombined model are the same.
If your current canned estimators and checkpoints are from TF 1.x, after you
migrate the canned estimator to v2 with tf.keras.optimizers.*, the converted
checkpoint allow you to restore and retrain the model in TF 2.0.

I think this was resolved already with the detailed guide on migrating checkpoints from TF1.x to 2.x.
Here is the link to the guide.
I am closing this issue as this was already resolved. Please feel free to reopen if I am mistaken. Thanks!


Support optionalDependencies in [GithubPackageJson]; also test [npm]

Closes #6044

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against 449e3c505a05457ea4716c95346b76304d10bb85

Yea, it could be. The existing examples are representative but I don’t think comprehensive.
It would be great if the example system were more closely aligned to the way routes are designed so we could unambiguously communicate the interface a route provides rather than generating representative examples.

Yea, it could be. The existing examples are representative but I don’t think comprehensive.
It would be great if the example system were more closely aligned to the way routes are designed so we could unambiguously communicate the interface a route provides rather than generating representative examples.

Oh I hope this PR wasn't held up waiting for me to respond to this :smile:
Agreed on all counts though. I believe the npm dependency version does have a comprehensive set of examples but definitely not needed here


Remove console

This PR closes #9
I've added debug, chalk and node-emoji to the project. Also I've updated current console.log statement to use debug instead.
All debug statements are grouped under cmc:* namespace, execute the module using DEBUG=cmc:* to enable all of them.
@MicheleBertoli feel free to improve the output and the emojis used :),  Here you can find a partial list of supported emojis 👊

@MicheleBertoli seems that logs inside the ast traverse loop greatly slow the process, can you confirm that happens also to you?

Nevermind, now the process is fast as usual. Probably I had some process stuck on the shell.

Awesome, @cef62!
I ❤ emojis :)
Just one small comment and it's good to go.


pull request for e2e test at 01/14/2017 22:26:13

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update Links “tiktok-103”

Automatically generated by Netlify CMS

👷 Deploy Preview for distracted-hoover-7b89cc processing.
🔨 Explore the source changes: cf69fec4f39e11d55bf242d788a97dfdaaa24fee
🔍 Inspect the deploy log: https://app.netlify.com/sites/distracted-hoover-7b89cc/deploys/610d792f1608d10008c95d38


Deploy Cockroach DB in Minikube

Description
For now, go with a single instance.
Discussion
No response
Motivation
No response
Details
No response

@kami619 - before I start on this, it would be great to have #139 merged as it touches similar areas in the taskfile, and I want to avoid conflicts. Thanks!

@ahus1 on it, I think I should be able to wrap #139 in the next hour.


Draft record in Datastore being overwritten instead of updated

Currently, when you run the app:

The draft announcement is generated successfully.
Errors out when you click the 'Send announcement' button.

Slackbot error message:
:siren: There was an error executing function Create a draft announcement as part of workflow Create an announcement. This workflow belongs to app announcement-bot-app (local). Error details:
Message: parameter_validation_failed Team: Natasha Test 1 Trace ID for developers: Tr0548G4QGCR

CLI error message:
> natasha.thomas of Natasha Test 1
Connected, awaiting events
2023-04-19 11:17:36 [info] [Wf053VPD5G91] (Trace=Tr0548G4QGCR) Execution started for workflow 'Create an announcement'
2023-04-19 11:17:36 [info] [Wf053VPD5G91] (Trace=Tr0548G4QGCR) Executing workflow step 1 of 4
2023-04-19 11:17:36 [info] [Fn010N] (Trace=Tr0548G4QGCR) Function execution started for Slack function 'Open a form'
2023-04-19 11:17:57 [info] [Fn010N] (Trace=Tr0548G4QGCR) Function execution completed for function 'Open a form'
2023-04-19 11:17:58 [info] [Wf053VPD5G91] (Trace=Tr0548G4QGCR) Execution completed for workflow step 'Open a form'
2023-04-19 11:17:59 [info] [Wf053VPD5G91] (Trace=Tr0548G4QGCR) Executing workflow step 2 of 4
2023-04-19 11:17:59 [info] [Fn054KHXN0V6] (Trace=Tr0548G4QGCR) Function execution started for app function 'Create a draft announcement'
Error completing function {
ok: false,
error: "parameter_validation_failed",
error_messages: [ "Missing value for parameter `message`" ]
}
2023-04-19 11:18:17 [error] [Fn054KHXN0V6] (Trace=Tr0548G4QGCR) Function execution failed for function 'Create a draft announcement'
        parameter_validation_failed
2023-04-19 11:18:18 [error] [Wf053VPD5G91] (Trace=Tr0548G4QGCR) Execution failed for workflow step 'Create a draft announcement'
2023-04-19 11:18:18 [error] [Fn053YBR9G76] (Trace=Tr053VT41DAN) Function execution failed for function 'Create an announcement'
        parameter_validation_failed
2023-04-19 11:18:18 [error] [Wf053VPD5G91] (Trace=Tr0548G4QGCR) Execution failed for workflow 'Create an announcement'
        parameter_validation_failed

In the 'Create a draft announcement' function, the file 'handler.ts' creates a new datastore record with the draft.
It then updates the draft record with the successful sent drafts timestamp. This is done using the 'apps.datastore.put' method, but the behaviour of 'apps.datastore.put' was changed on April 6, 2023 to fully replace an item if it exists. So the record that was created previously with the id, created_by, message, channels, channel, icon, username and status fields is replaced by a record the same id and a message_ts field alone. This explains the missing message parameter error.
To partially update an item, the 'apps.datastore.update' method must be used . This is mentioned here: https://api.slack.com/automation/datastores#put

Thanks for the detailed issue report @natnats92 and accompanying PR.

Confirmed I can reproduce the behavior reported here on a local run.

Will take a look at the PR next.

I believe that all PRs related to this issue have been merged. If the issue persists, feel free to reopen! 🙇🏼♀


Add minimal bucket DB read snapshot guard interface

@geirst please review Only exposes enough functionality to be used for Get operations for now.

Enable free-lists for underlying replica ArrayStore.
Legacy MapBucketDatabase read guard is not thread safe, as it will never be used for non-blocking reads.
Use snapshot read guard for Get operations

@toregge FYI


Enable GILProtected access via PyVisit

Closes #3615
This simply adds a new method which uses the existence of a PyVisit object as proof that the GIL is held instead of a Python object. This allows GILProtected to be used in instances where contained Python objects need to participate in garbage collection. Usage in this situation should be valid since no Python calls are made and this does not provide any additional mechanism for accessing a Python object.

I am 100% willing to change the name of the method. I just wanted the MR to go with the issue ASAP so both can be closed quickly (assuming there is little to no need to discuss the feature).

I'm feeling split about this feature. I understand why in practice this seems ok at the moment, but can we really rely on the fact that the GC will never traverse the graph in parallel?
Can you give some use cases of what you need this for? With the advent of nogil, we sort of need to be killing GILProtected so perhaps we can work out alternative patterns...

can we really rely on the fact that the GC will never traverse the graph in parallel?

If we can't, then PyO3 already has a major issue around marking types as unsendable. That being said, I think we can based on the fact that making the garbage collector parallel would be a major happening in Python and would probably break a fair number of existing extensions.

Can you give some use cases of what you need this for?

Any time you have any Python object behind a GILProtected, you would need this in order to enroll in GC correctly. My specific use case is I am implementing something similar to a MPMC channel and I want to leverage the fact that the GIL is present in order to not have to pull in another mutex or deal with atomics. The vastly oversimplified version looks something like this:
struct Inner {
    items: VecDeque<PyObject>,
}

#[pyclass]
struct Sender {
    inner: Arc<GILProtected<RefCell<Inner>>>,
}

#[pymethods]
impl Sender {
    fn send(&self, py: Python<'_>, obj: PyObject) {
        self.inner.get(py).borrow_mut().items.push_back(obj);
    }

    fn __traverse__(&self, visit: PyVisit<'_>) -> Result<(), PyTraverseError> {
        // unable to traverse objects in the queue
    }

    fn __clear__(&mut self, py: Python<'_>) {
        self.inner.get(py).borrow_mut().items.clear();
    }
}

With the advent of nogil, we sort of need to be killing GILProtected so perhaps we can work out alternative patterns...

I'll need to read up on the nogil but I'm not opposed to alternative patterns. I mostly want these changes so I can remove instances of self.inner.get(Python::assume_gil_acquired()) from my code.

Fair points! Good thought about unsendable too, I vaguely recall hearing that the GC runs in a dedicated thread on nogil so we might indeed have a problem there, but that's a different discussion.
I think for practicality's sake I'm happy to move forward here with the name traverse, and when we start dealing with nogil (hopefully on my target for early in the new year) we can figure out the replacements. I suspect that GILProtected<RefCell<T>> will be best served by something like RwLock<T>.

Please also fix the reference to the original method name in the changelog entry. Thanks!

Please also fix the reference to the original method name in the changelog entry. Thanks!

Good catch. Done!


♻Use name instead of email

Feature Request
We recently got the username from the backend, use it instead of the email.

Hey @AntoLC , I would love to help solve this issue.
Could you help me understand which part of the backend the information comes from and in which file this user needs to be received and displayed?

Let 's have the name and the email on two lines. Because emails are a good way to know from which org the user is.
First Name
<EMAIL_ADDRESS>

Hi, @virgile-dev! Could you help me with the questions I asked in my last comment?


Support for recent Ubuntu and Debian versions, stdlib 9.x and Puppet 8

Pull Request (PR) description
This PR implements support for Debian > 9 and Ubuntu > 18, puppetlabs/stdlib 9.x and Puppet 8.
This Pull Request (PR) fixes the following issues
Fixes #24

can you run bundle exec rake strings:generate:reference? the CI might be passing then :)

I've closed this PR for now. Will add a new one with Debian 12 support soonish hopefully.


Add version of functions that take pointers

For the sake of performance, it should be added version of functions that take the structures as pointers. The functions that take the structures as values will still exist, and the functions that take the structures as pointers will have a p prefix.
As example:
cvector2 pvector2_add(const cvector2 *a, const cvector2 *b)
{
	cvector2 result;
	result.x = a->x + b->x;
	result.y = a->y + b->y;
	return result;
}

inline cvector2 vector2_add(const cvector2 a, const cvector2 b)
{
	return pvector2_add(&a, &b);
}

The changes were made and this is the new design of the functions that take pointers:
void pvector2_multiply(cvector2 *a, cvector2 *b, cvector2 *result);
float pvector3_dot(cvector3 *a, cvector3 *b);

Results that are structures are outputted in the last argument *result, while results that are float are returned by the function.


Add Bertish

Codecov Report

Merging #72 (5baff4c) into main (1c76fbe) will decrease coverage by 1.08%.
The diff coverage is 36.84%.

:exclamation: Current head 5baff4c differs from pull request most recent head c7876cd. Consider uploading reports for the commit c7876cd to get more accurate results

@@            Coverage Diff             @@
##             main      #72      +/-   ##
==========================================
- Coverage   92.09%   91.01%   -1.09%
==========================================
  Files          48       48
  Lines        2088     2125      +37
==========================================
+ Hits         1923     1934      +11
- Misses        165      191      +26

Impacted Files
Coverage Δ

src/hearth/modules/transformer.py
73.33% <35.13%> (-26.67%)
:arrow_down:

src/hearth/modules/__init__.py
100.00% <100.00%> (ø)

src/hearth/vision/utils.py
93.75% <0.00%> (-6.25%)
:arrow_down:

src/hearth/callbacks/monitors.py
94.59% <0.00%> (-2.71%)
:arrow_down:

src/hearth/callbacks/learning_rate.py
97.67% <0.00%> (-1.17%)
:arrow_down:

src/hearth/vision/ops.py
100.00% <0.00%> (+6.66%)
:arrow_up:

Continue to review full report at Codecov.

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


.NET 7+ only for windows platform ? (skiasharp rendering)

Dear team,
Reading this:
https://github.com/FastReports/FastReport/issues/554
https://github.com/FastReports/FastReport/issues/445
I understand that FastReport Opensource will hopefully receive (linux, osx) skiasharp rendering sometimes in the future (commercial product already has)
But reading this:
https://github.com/FastReports/FastReport/issues/563
https://github.com/FastReports/FastReport/issues/484
I understand that from .NET7+  FastReport Opensource will only support windows platform cause it will never receive skiasharp rendering.
Please write CLEAR this new issue/policy on readme page, because in our case FastReport Opensource will became a big "demo" repo for the commercial product. For some, it can be a blocking issue in adoption of fastreport not being able to support linux/linux containters other than using the commercial product.
Thank for your works.

Indeed, this question is also bothering me;
I used the OpenSource version, but I had quite a few problems exporting PDF;
Switch to FastReport .NET Trail version，There were also some issues running inside Docker;
This seems to be because System.Drawing no longer supports the Linux platform

Hello!
FastReport.Opensource does not support development for macOS. System.Drawing.Common, starting with version 7.0, will completely stop supporting non-Windows systems, so the examples of libgdiplus given above will soon not work at all.
Only the commercial version of FastReport.Core.Skia has support.
See here:
https://www.fast-report.com/en/blog/show/fastreport-core-skia/
Also expect the demo Nuget packages FastReport.Core.Skia and FastReport.Web.Skia to be released for testing with the demo FastReport .Net packages.
Best regards,
Bogdan

Maybe we can migrate System,Drawing.Common to Aspose.Drawing.Common


Replace codemirror with monaco editor

https://microsoft.github.io/monaco-editor/
This would replace all instances of the codemirror editor with the monaco editor.

closing in favor of: https://github.com/influxdata/influxdb/issues/14483


JSON Query to graphql/query: HTTP error code 401.

I am getting the error on the Ubuntu server. But it is working on the local machine.
JSON Query to graphql/query: HTTP error code 401.

Having the same problem, it seems to be triggered by the login function, works fine on public accounts.

@GarethFreeman But I am trying to download a public video. I think it is related to the server or smth

Closing these as duplicate of #2011 – no need to track the 401 problem in several different issue threads.


Merge collector's store into sourceStore

If the sources are not inlined, the source store provided to the remap
function will not contain the sources. Therefore the sources returned by
the collector's store are merged into the provided sourceStore for the
report wirter to be used during report generation.

Hi, I'm leaning towards solution in https://github.com/marcules/karma-remap-istanbul/pull/27 as this is consistent with what remap-istanbul does. Let me know if this works for you.

I think this is already resolved by https://github.com/marcules/karma-remap-istanbul/pull/27, which was released as 0.2.2. If it's not fixed please let me know!


Update 0.15.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Requires: https://github.com/conda-forge/staged-recipes/pull/16101

@conda-forge-admin, please restart ci

@conda-forge-admin, please restart ci


7.7.2b Create new PIN - error

1. User Story
As a user I want to see an error message when my confirmation PIN does not match the new PIN I set in the previous step
so that I can be sure that I know my new PIN and did not make a mistake.
2. Acceptance Criteria

If PINs don't match, show error, and let user try again.
The new PIN needs to encrypto the recovery phrase (to be stored on device).

3. Related Issues

[ ] Create all related issue for this issue, label them, assign them, and move them to the right projects.
[ ] tbd
[ ] tbd

4. Wire Frame
None
5. Design
Add:

Screenshot
Figma link to specific element

@Chegemartinx pls add design


update twitter icon to x [Fixes #1321]

Fixing the issue [fixes https://github.com/cert-manager/website/issues/1321]
hacktober
Changed the svg of twitter icon to x

@inteon can you add hacktoberfest-accepted label to this PR

@sarthak-kumar-shailendra I added the label, although I don't think it is strictly required for hacktoberfest.

Thanks a lot! Actually, it was showing not accepted in hacktoberfest for this PR.


BTL-15 Rematch UI and Custom Menu

Consolidated Custom Menu and removed redundant code.
removed old actions from the custom menu manual setup
added functionality to clear old assigned buttons when you close the custom menu
added main menu button to the settings instead of quit game, added quit game button to the Game Selection Menu

@EVERYPLANET Dynamic menus are functional and existing menus seem to be working normally. Have indented the cases so it should be readable now. Ready to merge with QA when you're happy with the latest work


Adds Coevolve aggregator to the Jumps benchmark suite

This PR adds the new Coevolve aggregator (added in PR SciML/JumpProcesses.jl#276) to the Jumps benchmark suite.

Does this method make sense in these benchmarks? Since it's all constant rates, it's just going to have overhead compared to the other techniques? Is this just to measure that overhead?

The benchmark is to measure the overhead. When passed constant rates, Coevolve should obtain a performance very close to NRM since the algorithm reduces to the latter.

The benchmarking machine had a hard drive failure. Remind me to make this rerun after the hardware is fixed up


Add BIBTEX entries to insert_worm.py for Evidence from data sources

Our data sources are listed in docs/data_sources.rst.  These data sources should be included as bibtex & evidence in insert_worm.py

Ok, I assumed I could just add bibtex entries like pmid. Looking into it further, this feature doesn't seem to be implemented.
Skipped test 1
Skipped test 2
Also, the docstrings for Evidence assume we have a bibtex module available. There's nothing on PyPI with this name, though something like bibtexparser may be used in the future.

For now, I will save the bibtex entries in a text file on that sources branch, so we don't have to go looking for them later on.

Since this issue was originally raised we are using bibtexparser. BibTeX for the entries below needs to be added and incorporated into insert_worm.py. I've added a beginner label to this since there's not much left on it.
[3] Emmons, S., Cook, S., Jarrell, T., Wang, Y., Yakolev, M., Nguyen, K., Hall, D. Whole-animal C. elegans connectomes.  C. Elegans Meeting 2015 http://abstracts.genetics-gsa.org/cgi-bin/celegans15s/wsrch15.pl?author=emmons&sort=ptimes&sbutton=Detail&absno=155110844&sid=668862
[4] Bentley B., Branicky R., Barnes C. L., Chew Y. L., Yemini E., Bullmore E. T., Vertes P. E., Schafer W. R. (2016) The Multilayer Connectome of Caenorhabditis elegans. PLoS Comput Biol 12(12): e1005283. http://doi.org/10.1371/journal.pcbi.1005283