Bug: No subscription existing for

Whenever a publication throws an error, instead of reporting the actual error, this package reports
No subscription existing for <name>

Is it intentional?
For instance,
I use auth checks in my pubs and when I try the app without a login I receive the above mentioned warning.

Please share a code example.

I experience the same thing.
take for example
Meteor.publish('group.memberProfiles', function(groupId){
    const user = Meteor.users.findOne(this.userId);

    if(!user) throw Meteor.error('user not logged in');
    // If group Id is invalid, metoer console shows error since it can't find a group with invalid ID

    const group = Groups.findOne({ _id: groupId });

    const memberIds = group.members.map(member => member._id);
    // Error cannot read property members of undefined

    return UserProfiles.find({ userId: { $in: memberIds } });
  });

If group Id is invalid, metoer console shows error since it can't find a group with invalid ID.
Error cannot read property members of undefined
However the Yellow box in the device simply says no subscription existing. It probably does not have to pipe the message to the device UI, however it should describe the error a bit more accurately.

I have that same problem
my code meteor api server:
export const PhoneNumbers = new Mongo.Collection('phoneNumbers')

Meteor.methods({
    addPhoneNumber(data) {
        PhoneNumbers.insert({
            name: data.name,
            number: data.number
        }, err => {
            if (err) {
                return err
            } else {
                return null
            }
        })
    }
})

Meteor.publish('getAllNumbers', () => {
    return PhoneNumbers.find({})
})

App.js RN:
import {
  StyleSheet,
  Text,
  View,
  TextInput,
  FlatList,
  TouchableHighlight
} from 'react-native';
import Meteor, { createContainer } from 'react-native-meteor'

class App extends React.Component {
  constructor() {
    super()
    this.state = {
      name: 'Sarawut Kodkeaw',
      number: '06465466'
    }
  }

  componentWillMount() {
    Meteor.connect('ws://localhost:3000/websocket')
  }

  addPhoneNumber = () => {
    const data = {
      number: this.state.number,
      name: this.state.name
    }

    Meteor.call('addPhoneNumber', data, err => {
      if (err) {
        console.log(err)
      } else {
        this.setState({
          number: '',
          name: ''
        })
      }
    })
  }

  render() {
    return (
      <View style={styles.container}>
        <TextInput
          style={styles.input}
          placeholder='Enter a name'
          onChangeText={name => this.setState({ name })}
          value={this.state.name} />
        <TextInput
          style={styles.input}
          keyboardType='numeric'
          placeholder='Enter a phone number'
          onChangeText={number => this.setState({ number })}
          value={this.state.number} />

        <TouchableHighlight
          onPress={this.addPhoneNumber}
          underlayColor="gray"
          style={styles.button} >
          <Text style={styles.text}>Save</Text>
        </TouchableHighlight>

        <FlatList
          data={this.props.phoneNumbers}
          keyExtractor={(item, index) => item._id}
          renderItem={({ item }) => (
            <View>
              <Text>{item.name} || {item.number}</Text>
            </View>
          )} />
      </View>
    );
  }
}

export default createContainer(() => {
  Meteor.subscribe('getAllNumbers')
  return {
    phoneNumbers: Meteor.collection('phoneNumbers').find({})
  }
}, App)

log ERROR:
15:31:19: Connected to DDP server.
15:31:21: No subscription existing for, getAllNumbers
- node_modules/react-native-meteor/src/Meteor.js:173:23 in <unknown>
- ... 8 more stack frames from framework internals

Can somebody help us please???

Don’t use arrow functions for publications and methods. The server sets
some properties on ‘this’ like the callers userId which it cannot do with
arrow functions.
On Tue, 28 Nov 2017 at 4:51 AM, sarawut kodkeaw<EMAIL_ADDRESS>wrote:

I have that same problem
my code meteor api server:
export const PhoneNumbers = new Mongo.Collection('phoneNumbers')
Meteor.methods({
addPhoneNumber(data) {
PhoneNumbers.insert({
name: data.name,
number: data.number
}, err => {
if (err) {
return err
} else {
return null
}
})
}
})
Meteor.publish('getAllNumbers', () => {
return PhoneNumbers.find({})
})
App.js RN:
import {
StyleSheet,
Text,
View,
TextInput,
FlatList,
TouchableHighlight
} from 'react-native';
import Meteor, { createContainer } from 'react-native-meteor'
class App extends React.Component {
constructor() {
super()
this.state = {
name: 'Sarawut Kodkeaw',
number: '06465466'
}
}
componentWillMount() {
Meteor.connect('ws://localhost:3000/websocket')
}
addPhoneNumber = () => {
const data = {
number: this.state.number,
name: this.state.name
}
Meteor.call('addPhoneNumber', data, err => {
  if (err) {
    console.log(err)
  } else {
    this.setState({
      number: '',
      name: ''
    })
  }
})

}
render() {
return (

<TextInput
style={styles.input}
placeholder='Enter a name'
onChangeText={name => this.setState({ name })}
value={this.state.name} />
<TextInput
style={styles.input}
keyboardType='numeric'
placeholder='Enter a phone number'
onChangeText={number => this.setState({ number })}
value={this.state.number} />
    <TouchableHighlight
      onPress={this.addPhoneNumber}
      underlayColor="gray"
      style={styles.button} >
      <Text style={styles.text}>Save</Text>
    </TouchableHighlight>

    <FlatList
      data={this.props.phoneNumbers}
      keyExtractor={(item, index) => item._id}
      renderItem={({ item }) => (
        <View>
          <Text>{item.name} || {item.number}</Text>
        </View>
      )} />
  </View>
);

}
}
export default createContainer(() => {
Meteor.subscribe('getAllNumbers')
return {
phoneNumbers: Meteor.collection('phoneNumbers').find({})
}
}, App)
log ERROR:
15:31:19: Connected to DDP server.
15:31:21: No subscription existing for, getAllNumbers

node_modules/react-native-meteor/src/Meteor.js:173:23 in
... 8 more stack frames from framework internals

Can somebody help us please???
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/inProgress-team/react-native-meteor/issues/262#issuecomment-347454548,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQaDGKrV7_UpkVqBo-fz69FleAEOCVGXks5s68mqgaJpZM4Okyby
.

i changed from arrow functions to anonymous function but still get the same error
19:34:02: No subscription existing for, getAllNumbers
- node_modules/react-native-meteor/src/Meteor.js:173:23 in <unknown>
- ... 8 more stack frames from framework internals
19:34:14: Object {
19:34:14:   "error": 404,
19:34:14:   "errorType": "Meteor.Error",
19:34:14:   "isClientSafe": true,
19:34:14:   "message": "Method 'addPhoneNumber' not found [404]",
19:34:14:   "reason": "Method 'addPhoneNumber' not found",
19:34:14: }

App.js RN:
export default createContainer(function () { //---------->changed
  Meteor.subscribe('getAllNumbers')
  return {
    phoneNumbers: Meteor.collection('phoneNumbers').find({})
  }
}, App)

Meteor api server:
Meteor.methods({
    addPhoneNumber(data) {
        PhoneNumbers.insert({
            name: data.name,
            number: data.number
        }, function (err) { //---------->changed
            if (err) {
                return err
            } else {
                return null
            }
        })
    }
})

Meteor.publish('getAllNumbers', function () { //---------->changed
    return PhoneNumbers.find({})
})

Is that correct?

Oh. Also how you declare the method is also incorrect
it should be
Meteor.methods({
   'addPhoneNumber': function(data) {
      // do whatever
   }
})

Your publication looks like the correct format, but where is it located?For publications to work they must be within
Meteor.startup(() => {
   Meteor.publish('name', function(params) {
      return cursor;
   }
})

you need to make certain changes in the code

import the phonenumber.js in the main.js file inside the server folder

Meteor.startup(() => {
  import '../imports/api/PhoneNumbers.js';
});

createContainer  is deprecated , instead of this use withTracker, then the code in app.js in the react-native-app becomes

export default withTracker(params => {
  return {
    phoneNumbers: Meteor.collection('phoneNumbers').find({}),
  };
})(App);

Put the Meteor.connect('ws://<IP_ADDRESS>:3000/websocket'); before the class declaration (optional)

I'm getting this an it's driving me a little crazy trying to figure out where I'm going wrong. @lc3t35 did you solve your problem?

yes, the problem came from the name of the collection instead of const handleVehicules = Meteor.subscribe("vehicules", agentId); it should be const handleVehicules = Meteor.subscribe("Vehicules", agentId);!

@lc3t35 Hmmm... pretty sure all of mine are lower. I've stripped it right back and I'm still getting this error when moving from offline to online... I'll do some more debugging. Thanks!

@remotealex what are you using to manage offline ?

@lc3t35  redux-offline. I'm starting to think its actually how im testing it. Going to try something new now!

I havent seen this issue in my last few tests so fingers crossed I've fixed it!
For clarity, I'm now checking Meteor.status().connected and Meteor.user() before attempting to subscribe.


Required properties/config options must be validated at start-up

Batch node information such as BatchImagePublisher is driven by configuration. When these settings are missing, the application boots up but fails to submit Jobs to Azure Batch. When this occurs, the root cause of the issue (missing config) is hard to debug - Batch returns a Bad request, and details on the root cause are in the response's body content which is lost and not logged.
AC:

The application must not boot up if the required configuration entries are missing and don't have reasonable defaults.
Must provide a helpful exception to identify the missing configuration.
Should consider refactoring configuration using the IOptions pattern.

Could potentially be moved to "NEXT" milestone


EFS mount error in China region

Environment:

AWS ParallelCluster: aws-parallelcluster-2.7.0
Bug description and how to reproduce:
PCluster will fail when config EFS mounting in China region(BJS & ZHY). We found EFS endpoint resolving error in EFS mounting step through log. It is hard-coded as "xxx.amazonaws.com" in efs_mount.rb recipe.

Additional context:
sudo sed -i "s/amazonaws.com/amazonaws.com.cn/g" /etc/chef/cookbooks/aws-parallelcluster/recipes/efs_mount.rb
Although we can point to a pre_install.sh including above code, we really hope this bug can be fixed to be adaptive to China region without region-sensitive.
Similar code is here FYR:
s3_domain = "https://s3.#{node['cfncluster']['cfn_region']}.amazonaws.com"
s3_domain = "#{s3_domain}.cn" if node['cfncluster']['cfn_region'].start_with?("cn-")

Hi @Iwillsky thanks for pointing this out. It's definitely a bug.

Hi @Iwillsky,
EFS support for China is targeted for next release.

Thanks. It will be convenient to China customers. We ❤ aws.

Hi @lukeseawalker ,
We also found similar hard-coded url in fsx_mount.rb. It would be better if resolved together in the next release.

Hi @Iwillsky,
it has been taken care by this PR https://github.com/aws/aws-parallelcluster-cookbook/pull/640
Thanks

AWS ParallelCluster 2.8.0 with EFS support in China has been released https://github.com/aws/aws-parallelcluster/releases/tag/v2.8.0


BlockChain Public Address API Release Tracker for MetaRelease Spring 25

Problem description
Manage BlockChain Public Address API Release Tracker for MetaRelease Spring25
Parent Issue: #61
Expected action
Generate API Release tracker for BlockChain Public Address API within MetaRelease Spring 25
Additional context
Information to be compiled here: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14564746/BlockchainPublicAddress+API+Release+Tracking

04/DIC: First action completed. API Release Tracker generated:
https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/45973602/blockchain-public-address+v0.2.0


Write tests for requests endpoints

Wrote tests for the requests endpoints

Pull Request Test Coverage Report for Build 73

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+15.6%) to 84.158%

Totals

Change from base Build 71:
15.6%

Covered Lines:
425

Relevant Lines:
505

💛  - Coveralls

Pull Request Test Coverage Report for Build 73

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+15.6%) to 84.158%

Totals

Change from base Build 71:
15.6%

Covered Lines:
425

Relevant Lines:
505

💛  - Coveralls

Pull Request Test Coverage Report for Build 73

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+15.6%) to 84.158%

Totals

Change from base Build 71:
15.6%

Covered Lines:
425

Relevant Lines:
505

💛  - Coveralls


Container lambda function gets DD_LAMBDA_HANDLER unset

Expected Behavior
The following code;
    const func = new Function(this, 'function', {
      runtime: Runtime.FROM_IMAGE,
      handler: Handler.FROM_IMAGE,
      architecture: Architecture.ARM_64,
      environment: {
        DD_LAMBDA_HANDLER: 'dist/index.handler',
      },
      memorySize: 1024,
      timeout: Duration.seconds(30),
      code: Code.fromEcrImage(repository, {
        tagOrDigest: imageInfo.sha,
        entrypoint: ['aws-lambda-ric'],
        cmd: ['node_modules/datadog-lambda-js/dist/handler.handler'],
        workingDirectory: '/opt/applicationpath',
      }),
    });

    const datadog = new Datadog(this, 'dd', {
      site: DDLambdaConfig.DATADOG_SITE,
      apiKeySecret: Secret.fromSecretCompleteArn(
        this,
        'apiKeySecret',
        lambdaExtensionApiKeyArn,
      ),
      extensionLayerVersion: DDLambdaConfig.DATADOG_EXTENSION_VERSION,
      nodeLayerVersion: DDLambdaConfig.DATADOG_NODE_LAYER_VERSION,
      pythonLayerVersion: DDLambdaConfig.DATADOG_PYTHON_LAYER_VERSION,
      env: this.environmentName,
      service: this.serviceName,
      version: this.platformVersion,
      addLayers: false,
    });

    datadog.addLambdaFunctions([func]);

should work (or break).
Actual Behavior
The DD_LAMBDA_HANDLER environment variable is forcibly overridden with the value of
the function defaultChild.handler, which for a container lambda function is undefined (and has to be ´undefined`).
Synth and deploy works, but the DD_LAMBDA_HANDLER env variable has disappeared, so function cant run.
https://github.com/DataDog/datadog-cdk-constructs/blob/0e1d841f7a4537b61ac7205ae7936fc9ccce5bac/src/redirect.ts#L48
From reading the code I could figure out that I should disable the redirect. But it was quite hard to find out.
There is documentation for how to use CDK and how to install the extension in a container but not how to combine the two.
I would expect that doing what I did should cause error on synth, or the redirect would be disabled by default if function is configure with image (func.runtime.runtimeEquals(Runtime.FROM_IMAGE).
Good thing you keep this open source, so one can figure out what's happening :D
Steps to Reproduce the Problem

write the code
run the code
be confused

Specifications

construct version v2-1.16.1

Found another thing related to image based lambdas. You prepend the "LAMBDA_TASK_ROOT" to the "handler" when including it. We have a common image where we are bundling code for many lambdas, so we don't set the env var in the image, and it is reserved, so it can be set in the configuration. Found a workaround for this as well, by setting the "DD_LAMBDA_HANDLER" to a full path /full/path/to/the/file.handler. Not sure if it falls under the same image lambda pitfalls umbrella.


Inspectdb run against Postgres fails to inspect tables imported with foreign data wrapper

On Postgres, the inspectdb command fails to list the tables imported with the foreign data wrapper.
This is due to the fact that pg_catalog.pg_class.relkind is set to 'f' while the function get_table_list
filter the relations only with 'r' and 'v'.
on line 50 the dictionary used to parse the result must also convert the 'f' (for foreign table) into 't' as done with 'r'

Thanks for the contribution. A Trac ticket and a test are required. c2b969e124f65d375aac969f253279085b6f7078 may provide some inspiration.

I created the ticket
https://code.djangoproject.com/ticket/29719#ticket
Regarding the unit test.
In order to write the test a database with the foreign datawrapper must be setup.
Is there a way i can set this up via django inside the test?
Thank u!

I don't know anything about foreign data wrappers.

Postgres' Foreign data wrapper allows to import into your schema tables of another database (this database can be another Postgres instance on a remote server as well as a different RDMBS - I encountered the bug with a double datawrapper importing from MsSQL and Oracle - )

The simplest solution would be to use file_fdw which will allow you to provide a simple CSV file that you can hook up as a foreign table within the scope of a single test, tearing it down afterwards.

@pope1ni Thank you for the prompt.
I tried this way and I could create a test for this .
The problem is that the foreign table isn't created when sql is run inside the test.
I tried the same sql in navicat and it works fine.
In the code below you can see that I created a 'iris_dummy' table and that one does get created, but the foreign table isn't. In fact the test fails miserably.
I also granted the highest privileges possible to the user linked to the django_unit_test and django_unit_test_other_db , but with no luck.
Any idea on how make it create the foreign table?
Thanks!
`@skipUnless(connection.vendor == 'postgresql', 'PostgreSQL foreign data wrapper test')
def test_foreign_data_wrapper(self):
cwd = os.getcwd()
    #CreateExtension("file_fdw")
    with connections["default"].cursor() as c:
        c.execute("CREATE EXTENSION file_fdw")
        c.execute("CREATE SERVER pglog FOREIGN DATA WRAPPER file_fdw")
        create_foreign_table = """CREATE FOREIGN TABLE iris (
            petal_length real,
            petal_width real,
            sepal_length real,
            sepal_width real,
            class int
            ) SERVER pglog
            OPTIONS (filename '%s/inspectdb/iris.csv' ,format 'csv') """ % (cwd, )

        print(create_foreign_table)

        res = c.execute(create_foreign_table)

        create__table = """CREATE  TABLE iris_dummy (
            petal_length real,
            petal_width real,
            sepal_length real,
            sepal_width real,
            class int
            ) """
        c.execute(create__table)

    print(connection.settings_dict['NAME'])
    try:
        out = StringIO()
        call_command('inspectdb', stdout=out)
        output = out.getvalue()
        print(output)
        self.assertIn("Iris", output)
    finally:
        with connection.cursor() as c:
            c.execute("DROP FOREIGN TABLE iris");
            pass`

Could you also attach the iris.csv file you were using to this pull request?

Here's the file (I had to rename it as .txt 'coz .csv isn't supporteD)
iris.txt


Move isProbablyUtf8 from kotlin internal to package named internal.

As part of review comments from https://github.com/square/okhttp/pull/6340/files, cleaning up unrelated changes.

Presumptive approval based on your suggestion on other PR.  cc @swankjesse

LGTM! 👍🏻👍🏻


Not able to use JDK15 build on centos6

Hi there,
I am not sure if this is the right place to report this but I tried to use the latest AdoptJDK 15 release on centos6 and it failed with:
/jdk/bin/java: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /jdk/bin/../lib/libjli.so)
Is this expected ?

Duplicate of https://github.com/AdoptOpenJDK/openjdk-build/issues/2097.


kavita: 0.8.0 -> 0.8.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kavita is: A fast, feature rich, cross platform reading server
meta.homepage for kavita is: https://kavitareader.com
meta.changelog for kavita is: https://github.com/kareadita/kavita/releases/tag/v0.8.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.1 in filename of file in /nix/store/ywb8asn9f1c59apmps4iwy57mbypgx8g-kavita-0.8.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

kavita

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ywb8asn9f1c59apmps4iwy57mbypgx8g-kavita-0.8.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kavita https://github.com/r-ryantm/nixpkgs/archive/bfb6097470e4826ef4d11c92dd539df0b874979b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/bfb6097470e4826ef4d11c92dd539df0b874979b#kavita

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ywb8asn9f1c59apmps4iwy57mbypgx8g-kavita-0.8.1
ls -la /nix/store/ywb8asn9f1c59apmps4iwy57mbypgx8g-kavita-0.8.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

kavita

Maintainer pings
cc @Misterio77 @nevivurn for testing.

Upstream messed up a bit, they bumped the version to <IP_ADDRESS> (Kareadita/Kavita@38dd4a97db1ff55bce8490235bf6365c4075956c), tagged 0.8.1, and then corrected the version in the immediately following commit (Kareadita/Kavita@3c9565468ad5494aef11dace62ba4b18b0c7d7f3).
They ran their release workflow (here) with the corrected version, so we should package the corrected version too. Otherwise it prints warnings every ~hour.


[FLINK-23455][e2e] Remove the usage of the yaml file in SQLJobSubmission

What is the purpose of the change
Remove the usage of the yaml file in the SQLJobSubmission.

Meet unstable test in FLINK-23239 and FLINK-22735 because of HiveTableSinkITCase.
@flinkbot run azure


Update gimli

These are the changes to go with https://github.com/gimli-rs/gimli/pull/382.
Let me know if there are any changes you disagree with, or if you have any ideas for further improvements.

I will have to update for latest nightly. Will merge later today.

Thanks!


cmd/operator: rename kubelet-object flag to kubelet-service

As @mgoodness in #354 kubelet-service describes much better what the flag is supposed to represent than kubelet-object, therefore the renaming here.
@mgoodness @fabxc @mxinden

test this please

test this please

👍


csproj cleanup

remove properties that already default to the project name
make indents consistent

You can test this PR using the following package version. 11.0.999-cibuild0038764-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0038779-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]


.env variables don't work with --template=typescript

Unless there is something I'm missing this looks like a bug. I'm trying to add REACT_APP_GRAPHQL=apiurl to .env and use it within the react app but process.env.REACT_APP_GRAPHQL is undefined and process.env returns an empty object.
"react-scripts": "3.4.1",

do'h VS code likes to automatically import modules and it tried to import "process" when i added the environment variable which overwrote the process.env variables LOL not really an issue just VS code trying to auto-insert things and be smart.


On increasing the size of description box its going outside of the page.This issue exist for all description fields.

Framework Version: 0.1.2

Framework Version:0.1.4
Fixed


Try to lift version constraint on scipy

Fix for Python 3.12 pipeline run in https://github.com/conda-forge/libertem-feedstock/pull/6

The reported errors are:

Encountered problems while solving:

package sparseconverter-0.3.3-pyhd8ed1ab_0 requires scipy <1.11, but none of the providers can be installed

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[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)

@conda-forge-admin please rerender

@matbryan52 do you remember why we had the version constraint in the first place? It seems that the tests do run successfully with scipy 1.12. Was there a specific incompatibility with scipy 1.11 on conda? Do we need scipy != 1.11 or something like that?

@matbryan52 do you remember why we had the version constraint in the first place? It seems that the tests do run successfully with scipy 1.12. Was there a specific incompatibility with scipy 1.11 on conda? Do we need scipy != 1.11 or something like that?

Unfortunately the CI run has been deleted for the commit which made me pin this : https://github.com/conda-forge/staged-recipes/pull/19861/commits/370ff3045601d5bb6e857f65110e8702549f9fb8
But a bit of investigating shows that the SciPy available on the day we merged the feedstock (1.11.0) was yanked one day later )https://pypi.org/project/scipy/1.11.0/). So I think we can convert the pin to scipy != 1.11.0 safely.


Trouble getting the plugin working

Hello,
I am having some trouble getting the plugin working. I have installed ansible and ansible-lint in a virtual environment. I followed the README instructions to create a small shell script, and that seems to be working:

I have a minimal .ansible-lint file like this:
---
# created by 'IntelliJ Ansible Lint Plugin'
#
# check this website for detailed configuration options:
#    https://ansible-lint.readthedocs.io/configuring/#ansible-lint-configuration

profile: production
use_default_rules: true

When I run my executable run_ansible-lint.sh file, I do get output which shows me ansible-lint is installed and working correctly with my .ansible-lint config file:

However, when I edit a test playbook, I don't see any issues or suggestions pop up:

I am on Mac OS 13.6.7, PyCharm 2024.1.5, and Ansible Lint plugin 1.7.1.
Does anyone have suggestions for what to try next? I am new to Ansible in general, so there could be other configuration requirements I haven't found in the docs yet.

I just tried updating PyCharm to 2<IP_ADDRESS> and the Ansible Lint plugin to 1.8.0. Now, on startup I'm seeing this pop up:

Unfortunately, I don't know how to submit this report since typing in the highlighted box doesn't seem to work:

That said, here are the lines that I can see:
ExternalToolPass:

com.intellij.diagnostic.PluginException: annotator: de.achimonline.ansible_lint.annotator.AnsibleLintAnnotator@49aa5138 (class de.achimonline.ansible_lint.annotator.AnsibleLintAnnotator) [Plugin: de.achimonline.ansible_lint]
	at com.intellij.diagnostic.PluginProblemReporterImpl.createPluginExceptionByClass(PluginProblemReporterImpl.java:23)
	at com.intellij.diagnostic.PluginException.createByClass(PluginException.java:90)
	at com.intellij.codeInsight.daemon.impl.ExternalToolPass.processError(ExternalToolPass.java:253)
	at com.intellij.codeInsight.daemon.impl.ExternalToolPass.doAnnotate(ExternalToolPass.java:213)
	at com.intellij.codeInsight.daemon.impl.ExternalToolPass.doAnnotate(ExternalToolPass.java:200)
	at com.intellij.codeInsight.daemon.impl.ExternalToolPass$1.lambda$run$0(ExternalToolPass.java:163)
	at com.intellij.codeInsight.daemon.impl.ExternalToolPass.runChangeAware(ExternalToolPass.java:268)
	at com.intellij.codeInsight.daemon.impl.ExternalToolPass$1.lambda$run$2(ExternalToolPass.java:163)
	at com.intellij.openapi.progress.util.BackgroundTaskUtil.lambda$runUnderDisposeAwareIndicator$15(BackgroundTaskUtil.java:371)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:217)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$13(CoreProgressManager.java:660)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:735)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:691)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:659)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:79)
	at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:202)
	at com.intellij.openapi.progress.util.BackgroundTaskUtil.runUnderDisposeAwareIndicator(BackgroundTaskUtil.java:366)
	at com.intellij.codeInsight.daemon.impl.ExternalToolPass$1.run(ExternalToolPass.java:161)
	at com.intellij.util.ui.update.MergingUpdateQueue.execute(MergingUpdateQueue.java:366)
	at com.intellij.util.ui.update.MergingUpdateQueue.execute(MergingUpdateQueue.java:356)
	at com.intellij.util.ui.update.MergingUpdateQueue.doFlush(MergingUpdateQueue.java:313)
	at com.intellij.util.ui.update.MergingUpdateQueue.flush(MergingUpdateQueue.java:295)
	at com.intellij.util.ui.update.MergingUpdateQueue.run(MergingUpdateQueue.java:262)
	at com.intellij.util.Alarm$Request.lambda$runSafely$0(Alarm.java:371)
	at com.intellij.util.concurrency.ChildContext$runAsCoroutine$1.invoke(propagation.kt:92)
	at com.intellij.util.concurrency.ChildContext$runAsCoroutine$1.invoke(propagation.kt:92)
	at com.intellij.util.concurrency.ChildContext.runAsCoroutine(propagation.kt:97)
	at com.intellij.util.concurrency.ChildContext.runAsCoroutine(propagation.kt:92)
	at com.intellij.util.Alarm$Request.lambda$runSafely$1(Alarm.java:369)
	at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:255)
	at com.intellij.util.Alarm$Request.runSafely(Alarm.java:368)
	at com.intellij.util.Alarm$Request.run(Alarm.java:356)
	at com.intellij.util.concurrency.Propagation.contextAwareCallable$lambda$2(propagation.kt:383)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at com.intellij.util.concurrency.SchedulingWrapper$MyScheduledFutureTask.run(SchedulingWrapper.java:272)
	at com.intellij.util.concurrency.BoundedTaskExecutor.doRun(BoundedTaskExecutor.java:249)
	at com.intellij.util.concurrency.BoundedTaskExecutor.access$200(BoundedTaskExecutor.java:30)
	at com.intellij.util.concurrency.BoundedTaskExecutor$1.executeFirstTaskAndHelpQueue(BoundedTaskExecutor.java:227)
	at com.intellij.util.ConcurrencyUtil.runUnderThreadName(ConcurrencyUtil.java:218)
	at com.intellij.util.concurrency.BoundedTaskExecutor$1.run(BoundedTaskExecutor.java:212)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:735)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:732)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:400)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:732)
	at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.NullPointerException: getParent(...) must not be null
	at de.achimonline.ansible_lint.annotator.AnsibleLintAnnotator.doAnnotate(AnsibleLintAnnotator.kt:66)
	at de.achimonline.ansible_lint.annotator.AnsibleLintAnnotator.doAnnotate(AnsibleLintAnnotator.kt:40)
	at com.intellij.codeInsight.daemon.impl.ExternalToolPass.lambda$doAnnotate$1(ExternalToolPass.java:208)
	at com.intellij.codeInsight.daemon.impl.AnnotationSessionImpl.computeWithSession(AnnotationSessionImpl.java:87)
	at com.intellij.codeInsight.daemon.impl.AnnotationSessionImpl.computeWithSession(AnnotationSessionImpl.java:79)
	at com.intellij.codeInsight.daemon.impl.ExternalToolPass.doAnnotate(ExternalToolPass.java:206)
	... 43 more

Did you install the OrchidE plugin as well? (see https://github.com/4ch1m/intellij-ansible-lint/issues/16#issuecomment-2004372483)
There are known conflicts.

Did you install the OrchidE plugin as well? (see #16 (comment)) There are known conflicts.

No, I have never used that plugin before. I did briefly download this other Ansible plugin, however, I have since uninstalled it. I've also disabled all other non-default plugins temporarily:

After taking a closer look at the stacktrace above...
I believe your setup is correct. And I believe you've found a bug. :smile:
I already prepared a fix.
The updated plugin (v1.8.1) should be available in the marketplace soon.
Please let me know if this solves your issues. Thanks.

I think that did the trick! Thanks for the prompt support, I really appreciate it.

Now that it is working, I've noticed a curious thing that I'd be interested to know if it is expected behavior or not. It seems like the plugin doesn't show some errors until others are fixed.
For example, on this file I see:

However, if I run ansible-lint in the command line I see:

If I fix the first error, then the plugin shows me the second one:

This is totally usable, but I'm curious if it is normal or not.

This is totally usable, but I'm curious if it is normal or not.

Totally normal; and totally correct.
Your errors are referring to the same task/line.
If you hover your mousepointer over the annotation, then you'll see both errors displayed.
Thanks for reporting back.

Great! That is good to know. I won't worry about it then, though FYI I'm not seeing the mouse-over behavior just in case that detail matters to you.

Oh interesting! I'll have to play with it a bit more then.
How do you have python and ansible-lint installed? I think I would like to try replicating that next.
I've been using python installed via Homebrew. I just tried downloading python directly from python.org.
Then I ran this in zsh:
which python3
/Library/Frameworks/Python.framework/Versions/3.12/bin/python3

python3 -m pip install ansible-dev-tools

After that, running ansible-lint works directly in my terminal without using or activating a virtual environment. However, if I try to switch away from using the run script in the plugin, it seems that it can't find ansible-lint:

I'm not sure that this would have any impact on how the errors get displayed, but maybe if I can replicate your environment more closely I can track down what is different between our machines.


Supervise an already running actor.

Right now the supervision container itself instantiates the actor.
An already running actor ought to be possible to supervise once it's already instantiated.
... possibly requiring the saving of the initialization parameters.

If you try to supervise an actor after it's been started, how do you prevent races involving the actor dying before the supervisor starts?
Sure you can potentially detect that, but why add the extra complexity? What's the use case?
Supervision is a place where you have to be very, very, very, very, very careful about what you do, because it's extremely easy to create racy code, and extremely hard to know if your implementation is robust. This is why I have been reluctant to add features to supervision in general.
In general I would suggest shoring up the existing supervision implementation and making sure it's rock solid before adding additional features, and if you do want to add additional features, you might want to first:

look for precedent in Erlang and/or Akka
make sure there's a clear, well-defined use case
do a complete flow diagram of all of the potential temporal interactions between actors, and make sure they aren't racy

#3 is the hardest. These are the kinds of problems that are best modeled in terms of temporal logic, with model checking.
In the absence of that, your best bet is to keep things simple.

I don't think this should be implemented until someone can properly defend "ought to be possible". Use-case first would be a good idea :)

I've been looking for precedent in Erlang and Akka. That in and of itself has been interesting and will probably lead to bringing over some ideas, like one_for_one, one_for_all, rest_for_one behaviors. I expect to work on bullet-proofing supervision before spending time on anything experimental like this.
The use cases are not that significant or urgent if at all. The @tarcieri caution regarding race conditions is closely felt, but the @benlangfeld comment seems like a challenge... I ... can't... resist... :)

Supervising after-the-fact just seems backwards to me. I'd say don't do it unless there's a good use case.

No use case justifies this for the foreseeable future.


LV_COLOR_DEPTH problem

I updated lvgl yesterday to master and now i have a problem with LV_COLOR_DEPTH in 32 Bit mode. Before I was using 24 Bit color depth. I attach 2 pictures for you to see the difference between 16 and 32 bit color. it seems like it is drawn much too big in 32 bit mode.
Any ideas what i could try?

@harteware07 Looks like you're using STM32F746G-DISCO from the picture. I ran into the same problem. The display driver and framebuffer array also need to be adjusted to accommodate other color depths.

I agree with @embeddedt . It seems your display driver needs to be reconfigured. If you are using the example from lv_projects repo than check this function
As you noticed LV_COLOR_DEPTH 24 was replaced by 32. Maybe you driver uses this define and waits for 24?

i changed LV_COLOR_DEPTH_24 to LV_COLOR_DEPTH_32 in order to be able to compile, other than that i didnt change anything.
Could you please give me a hint on what else to change?

@harteware07  There was no activity here for 1 month (plus you appear to have succeeded in getting it working on the discovery board based on your comment in #615) so this issue has been closed. If you continue to have problems please reopen the issue.


Rename ManagedIdentityCredential to ImdsManagedIdentityCredential

Current name: ManagedIdentityCredential
Proposed name: ImdsManagedIdentityCredential
This follows the name from the .Net SDK:
https://github.com/Azure/azure-sdk-for-net/blob/c5738f34a5ded5bf4b49e380a8eec179e12a1c6b/sdk/identity/Azure.Identity/src/ImdsManagedIdentitySource.cs#L15

This is done.


how to train with tensorflow gpu?

how to train with tensorflow gpu : such as CUDA version, CUDNN version, memory share of GPU NVIDIA,...

I suggest you to go for the official tutorial.
This is a very important part for deep learning.


Uppercase letters in keywords

I don't know if this is a common case, but someone might write:
IF FOO:
    BAR()

Checking for this should be easy. If the syntax becomes valid after lowercasing the entire program, there's probably a keyword somewhere that was meant to be lowercase.

Moved to #110.


Add pipeline mode API

This wraps the pipeline mode API, introduced in PostgreSQL 14: https://www.postgresql.org/docs/current/libpq-pipeline-mode.html
I'm not sure how the version requirement should be handled.
(For the moment we're using this experimentally here: https://github.com/PostgREST/postgrest/pull/2707.)

Did similar here but looked at PR's before send my one :)
Your version is clearer than mine and it has better tests. @robx what do you think regarding my approach with cabal compile flag to tweak which version of libpq is linked? Could you add it to your PR or should I do it?

@phadej Hi! Can you help us get this merged?

I'm unsure. The versioning question is hard. There are options:

Always use pkg-config. (Windows users will suffer AFAIU, I don't know if pkg-config can be made work with usual ways postgresql is installed on windows). I'm fine with this myself (I'd only need to figure out pkg-config problem on CI). That would allow me to remove build-type: Custom which I'd be very happy to do.
Assume that postgresql version is always recent enough if pkg-config method is not used.

And there are variants:

Add a (manual) flag whether to include pipeline mode or not. (The library API should be the same, functions will just fail if there are no support).
Always require recent enough libpq (people may use older libpq releases if they cannot upgrade - which is fine, as they won't get much by upgrading).

Opinions?

I may be wrong, but I think that unless the functions that aren't supported by the old libpq actually get used, things will work fine. If that's correct then there seems to be no need for the flags. Instead stating this clearly in the docs shall be enough.

I may be wrong, but I think that unless the functions that aren't supported by the old libpq actually get used,

foo :: Maybe Int -> IO Int
foo (Just x) = return x
foo Nothing  = bar

foreign import ccall "does_not_exist" bar :: IO Int

Even if I do
Prelude Lukko> foo (Just 1)

GHC.Linker.Loader.dynLoadObjs: Loading temp shared object failed
During interactive linking, GHCi couldn't find the following symbol:
  /tmp/ghc57176_0/libghc_37.so: undefined symbol: does_not_exist

things fail. So when linker decides to load symbols is not very predicatable.

Thanks for the clarification!
How about using the flag but have it default to requiring the latest libpq? Thus the library will effectively apply the following strategy:

Always require recent enough libpq

Which seems like an essential requirement for this library and the whole downstream ecosystem to evolve.
However it will also leave the alternative option available for hackers willing to use the older version.

@nikita-volkov that's my option

Add a (manual) flag whether to include pipeline mode or not. (The library API should be the same, functions will just fail if there are no support).

isn't it?

If it implies that the default is to enable the new functions, then it is.

Posted version with cabal flag to support older libpq versions.

Closing this one in favour of #52 (but feel free to reopen if that seems like a better idea)

Released in https://hackage.haskell.org/package/postgresql-libpq-<IP_ADDRESS>


Issues w/ known bug workarounds

We are accepting issues and we want your feedback.

Description
When attempting to open FPS-SimulatedPlayerCoordinator it will not open. The open option is grey. So I cannot rebake the navmesh.
Expected behaviour

I expected the ability to open the FPS-SimulatedPlayerCoordinator in the Hierarchy.
Current behaviour

Hierarchy only contains an Untitled Scene. Dragging and Dropping, Double-Clicking, or Right-Click > Open does nothing for FPS-SimulatedPlayerCoordinator. It does not move to the Hierarchy.
Also Right-clicking Source_Shaders and selecting Reimport does appear to process but nothing happens. No icons change, and warnings go away. It doesn't appear to be having any effect.
Possible solution

Unknown
Steps to reproduce

I am not sure how you can reproduce this other than follow the steps in the getting started guide.
This actually worked a couple days ago, but I wanted to start over so I deleted and recloning the repositories again so maybe something happened in the last couple of days?

Environment

Setup the Unity FPS Starter

`C:\Users\SeeingBlue>spatial diagnose
Running basic diagnostics suite
Network Access Checks
Google Storage APIs Reachable: PASSED
Spatial Website Reachable: PASSED
Spatial Auth Server Reachable: PASSED
Spatial Maven Reachable: PASSED
Spatial API Reachable: PASSED
Spatial Secure Customer Proxy Reachable: PASSED
Can Bind to Local Port: PASSED
Spatial Proxy Reachable: PASSED
Spatial Website TLS and GRPCTLS Ports Reachable: PASSED
Spatial Auth TLS and GRPCTLS Ports Reachable: PASSED
Spatial Maven TLS and GRPCTLS Ports Reachable: PASSED
Spatial API TLS and GRPCTLS Ports Reachable: PASSED
Spatial Deployments Reachable: PASSED
Spatial Logs Reachable: PASSED
Spatial Monitoring Proxy Reachable: PASSED
Spatial Locator Reachable: PASSED
Maven Central Repo Reachable: PASSED
Sonatype OSS Repo Reachable: PASSED
All checks successful`

OS: 'Windows 10  (10.0.0) 64bit' Language: 'en' Physical Memory: 16229 MB
I updated both SpatialOS and Unity today. I was having the same issue with the previous versions too.
Previous Unity Version: 2018.2.14
Current Unity Version: 2018.2.16
I attached the editor.log too
Editor.log

Hey @SeeingBlue, thanks for reporting this. To clarify my understanding of the issue, you're trying to execute these steps in order to rebake the navmesh, but you can't open the FPS-SimulatedPlayerCoordinator.unity, so its contents (ObjectPooling, GameSettings, SimulatedPlayerCoordinatorWorker & FPS-Start_Large) aren't visible in the Hierarchy window?
I can't reproduce this issue, and but my impression is that this was caused by missing a setup when deleting and recloning the repositories.
The cleanest way to fix this would be to delete everything and run the setup guide again.
If the problem persists, please try the following:

Please uninstall 2018.2.16 and reinstall 2018.2.14, as this is the only Unity version currently supported by the GDK.
Please confirm that when you run git status in your gdk-for-unity repo it reports HEAD detached at 0.1.2, which is the git tag of our latest release.

I hope this helps.


Add Mahesh's info in AboutUs page

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (1c277fe) compared to base (f897bba).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #60   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


License

Is this released under any kind of license? I'd like to use a very modified version of it for my blog, but I don't want to violate any terms.

It wasn't, but I've just added a license file, so it's now under the MIT license. Feel free to use it as you please.
And, thanks for checking!


Night CI 2024-03-06: Failed

action url: https://github.com/spidernet-io/egressgateway/actions/runs/8177990984

• [FAILED] [52.612 seconds]
Reliability [Reliability]
/home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:30
  Test the drift of the EIP [BeforeEach]
  /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:43
    Test EIP drift after the eip-node shut down [R00005]
    /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:113

  Timeline >>
  > Enter [BeforeEach] Test the drift of the EIP - /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:43 @ 03/06/24 20:07:51.143
  succeeded to create the gateway: egw-2895091e-d20e-4fc8-85fc-06bbe6329ad0
  v4DefaultEip: <IP_ADDRESS>, v6DefaultEip: fc00:f853:ccd:e793::605
  succeeded to create DaemonSet: ds-reliability-f5543739-f7dd-4265-8e47-665dcc36e89e
  Automatically polling progress:
    Reliability Test the drift of the EIP Test EIP drift after the eip-node shut down (Spec Runtime: 20.001s)
      /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:113
      In [BeforeEach] (Node Runtime: 20.001s)
        /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:43

      Spec Goroutine
      goroutine 27 [sleep]
        time.Sleep(0x1dcd6500)
          /opt/hostedtoolcache/go/1.20.5/x64/src/runtime/time.go:195
        github.com/spidernet-io/egressgateway/test/e2e/common.CreateEgressPolicyNew({_, _}, {_, _}, {0x1, 0x1, {{0xc0004b0fac, 0x4}, 0x0, 0x0, ...}, ...}, ...)
          /home/runner/work/egressgateway/egressgateway/test/e2e/common/egp.go:75
      > github.com/spidernet-io/egressgateway/test/e2e/reliability_test.glob..func3.1.1()
          /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:74
            |
            | // policy
            > policy, err = common.CreateEgressPolicyNew(ctx, cli, egressConfig, egw.Name, daemonSet.Labels, "")
            | Expect(err).NotTo(HaveOccurred())
            | GinkgoWriter.Printf("succeeded to create policy: %s\n", policy.Name)
        github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0, 0x0})
          /home/runner/work/egressgateway/egressgateway/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
          /home/runner/work/egressgateway/egressgateway/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:889
        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
          /home/runner/work/egressgateway/egressgateway/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:876
  [FAILED] Unexpected error:
      <*errors.errorString | 0xc00048d800>:
      create EgressPolicy time out
      {
          s: "create EgressPolicy time out",
      }
  occurred
  In [BeforeEach] at: /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:75 @ 03/06/24 20:08:13.438
  < Exit [BeforeEach] Test the drift of the EIP - /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:43 @ 03/06/24 20:08:13.438 (22.296s)
  > Enter [AfterEach] Test the drift of the EIP - /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:85 @ 03/06/24 20:08:13.439
  delete daemonSet
  delete policy
  delete gateway
  Automatically polling progress:
    Reliability Test the drift of the EIP Test EIP drift after the eip-node shut down (Spec Runtime: 42.297s)
      /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:113
      In [AfterEach] (Node Runtime: 20.001s)
        /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:85

      Spec Goroutine
      goroutine 133 [sleep]
        time.Sleep(0x1dcd6500)
          /opt/hostedtoolcache/go/1.20.5/x64/src/runtime/time.go:195
        github.com/spidernet-io/egressgateway/test/e2e/common.DeleteEgressGateway({0x2984390, 0xc0000501b8}, {0x298bf60, 0xc0004c1b00}, 0xc00035fc00, 0x0?)
          /home/runner/work/egressgateway/egressgateway/test/e2e/common/egw.go:282
      > github.com/spidernet-io/egressgateway/test/e2e/reliability_test.glob..func3.1.2()
          /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:95
            |
            | GinkgoWriter.Println("delete gateway")
            > err = common.DeleteEgressGateway(ctx, cli, egw, time.Minute/2)
            | Expect(err).NotTo(HaveOccurred())
            |
        github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0, 0xc000412900})
          /home/runner/work/egressgateway/egressgateway/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
          /home/runner/work/egressgateway/egressgateway/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:889
        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
          /home/runner/work/egressgateway/egressgateway/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:876
  [FAILED] Unexpected error:
      <*errors.errorString | 0xc000608840>:
      error timeout
      {s: "error timeout"}
  occurred
  In [AfterEach] at: /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:96 @ 03/06/24 20:08:43.754
  < Exit [AfterEach] Test the drift of the EIP - /home/runner/work/egressgateway/egressgateway/test/e2e/reliability/reliability_test.go:85 @ 03/06/24 20:08:43.754 (30.316s)
  << Timeline


rotate video

Can I rotate 30/45/69/90 degrees to a video on top of other video?
thanks

Hello,
I'm sorry to say my took doesn't have rotational options.
You could use FFMPEG to do 90 and 180 degree rotation of the sources before sending them into vedit.
I'm not aware of any ways to do rotations that aren't 90 degree increments (I'm sure there are some, but I don't know them).


Agr 490 : Integrate Wordpress Posts with AGR portal

Still work in progress but it's worth pulling in the following new features.

The "News & Events" page
Individual post pages

Hi @LucyHut this is quite some hard work! Really appreciate it.
I noticed an issue that I suspect might have to do with how routing is setup here. Here is what I tried:

click on News & Events menu to go to the news lists
reload the page and assert that multiple news entries appear
click on a post title to go to a post page
click on the News & Events menu to go to the news lists again
observe that the news list now contains only one entry

Issues with routing:

the  for path "posts" should probably be . The posts index page is about a list of items, its data needs and display needs are different from regular post page which focuses on a single item.  allows you to specify a component.
The the component prop in  is designed for specifying a shared wrapper like component used for displaying post/ and post/:postId . Instead of the Wordpress component, the component that goes in there would have a render function like:

render() {
  return (
    <div>
    {/* some shared display, such as a header */}
    {this.props.children}
    {/* some shared display, such as a footer */}
    </div>
  );
}

Here is an example similar to what you want to do in the React-router tutorial https://github.com/ReactTraining/react-router/blob/v2.8.1/docs/Introduction.md#with-react-router
Please let me know if you have questions

@sibyl229 , thank so much for the feedback --- I also noticed the issue and suspected the routing. I will review the link and give it another try 👍

@sibyl229, after few research it looks like  abstraction is no longer supported starting react-router 4.0 - so I'm exploring different options .

Hi @LucyHut the version we are currently at AGR using is 2.8.1 https://github.com/alliance-genome/agr/blob/development/webapp/package.json#L26

react router 4.0 is very different and not backward compatible. So it will probably have a more widespread impact on the codebase. If we need to upgrade, it's probably good to discuss among the group first, and/or try it in another branch.

@sibyl229, I  went with  the news and posts having the  "posts" route and the pages have the initial wordpress route. It seems to be working fine now.


Review Chapter 12 and determine implications for OCIO vs Ministry responsibilities in our Managed Cloud Service

Describe the issue
There is uncertainty about who is responsible for what in accessing cloud services (procurement, privacy and security compliance, policies, standards, guidelines ..).  If we are actively promoting a shared responsibility model, we wish to make sure there are no contradictions elsewhere.
Which Sprint Priority is this issue related to?
Priority 1
Additional context

New Chapter 12 is yet to be approved by Treasury Board (TB).
estimated as fairly high level (Gen)
Feeds into Service Blueprint

Definition of done

Complete an analysis, develop summary document outlining responsibilities.
look for tech code of practice, digital principles
Peer review (both Ch12 team and Cloud Pathfinder Team).
Stu and PO to review, Gen to approve.

Draft being put forward for branch review by EOD Wednesday (Feb 10).

First draft sent to Jenny R. for review EOD Feb 10.

Final draft sent to @cstua Feb 22nd.


Project system ran into an unexpected problem warning

Issue Description
Everytime i open my vscode, this notification pops up
** Project system ran into an unexpected problem, please report it to the product team **  do not understand the message but i have placed log details in the log section.
Steps to Reproduce
Expected Behavior
Actual Behavior
Logs
C# log

=====================
10/25/2023 1:29:46 PM
LimitedFunctionality
System.AggregateException: Project system data flow 'Workspace update handler 19481099' closed because of an exception: The JSON-RPC connection with the remote party was lost before the request could complete.. (The JSON-RPC connection with the remote party was lost before the request could complete.)
---> (Inner Exception #0) StreamJsonRpc.RemoteInvocationException: The JSON-RPC connection with the remote party was lost before the request could complete.
   at StreamJsonRpc.JsonRpc.InvokeCoreAsync[TResult](RequestId id, String targetName, IReadOnlyList`1 arguments, IReadOnlyList`1 positionalArgumentDeclaredTypes, IReadOnlyDictionary`2 namedArgumentDeclaredTypes, CancellationToken cancellationToken, Boolean isParameterObject)
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Handlers.DynamicItemHandler.<>c__DisplayClass6_0.<g__ProcessAdditions|4>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Handlers.DynamicItemHandler.HandleProjectChangeAsync(IWorkspaceProject context, IComparable version, IProjectChangeDescription projectChange, ContextState state, ITelemetryOperation telemetryOperation, IManagedProjectDiagnosticOutputService logger)
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Handlers.DynamicItemHandler.HandleAsync(IWorkspaceProject context, IComparable version, IImmutableDictionary`2 projectChanges, ContextState state, ITelemetryOperation telemetryOperation, IManagedProjectDiagnosticOutputService logger)
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Workspace.<>c__DisplayClass43_1.<g__ProcessSourceItemsHandlersAsync|6>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Workspace.<>c__DisplayClass43_0.<g__ApplyProjectEvaluationAsync|2>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Workspace.<>c__DisplayClass46_1`1.<g__ApplyInBatchAsync|1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.VisualStudio.Threading.ReentrantSemaphore.StackSemaphore.<>c__DisplayClass3_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.VisualStudio.Threading.ReentrantSemaphore.StackSemaphore.ExecuteAsync(Func`1 operation, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.ProjectSystem.OnceInitializedOnceDisposedUnderLockAsync.ExecuteUnderLockCoreAsync(Func`2 action, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Workspace.OnEvaluationUpdateAsync(IProjectVersionedValue`1 evaluationUpdate)
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Workspace.<>c__DisplayClass42_0.<g__ApplyUpdateWithinLockAsync|1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Workspace.<>c__DisplayClass42_0.<g__ApplyUpdateWithinLockAsync|1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.VisualStudio.ProjectSystem.VSCode.LanguageServices.Workspace.<>c__DisplayClass42_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.VisualStudio.Threading.ReentrantSemaphore.StackSemaphore.<>c__DisplayClass3_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.VisualStudio.Threading.ReentrantSemaphore.StackSemaphore.ExecuteAsync(Func`1 operation, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.ProjectSystem.OnceInitializedOnceDisposedUnderLockAsync.ExecuteUnderLockCoreAsync(Func`2 action, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.ProjectSystem.DataReceivingBlockSlim`1.ProcessInputQueueAsync(InputDataBuffer inputQueue)
<--- (Inner Exception #0)
===================
C# LSP Trace Logs
Post the output from Output-->C# LSP Trace Logs here.  Requires `dotnet.server.trace` to be set to `Trace`
Environment information
VSCode version: 1.83.1
C# Extension: 2.7.25
Using OmniSharp: false
Dotnet Information
.NET SDK:
 Version:   7.0.306
 Commit:    f500069cb7
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.19044
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\7.0.306\
Host:
Version:      7.0.9
Architecture: x64
Commit:       8e9a17b221
.NET SDKs installed:
7.0.306 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 7.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 7.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 7.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
None
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download

Visual Studio Code Extensions

Extension
Author
Version
Folder Name

csdevkit
ms-dotnettools
0.5.150
ms-dotnettools.csdevkit-0.5.150-win32-x64

csharp
ms-dotnettools
2.7.25
ms-dotnettools.csharp-2.7.25-win32-x64

open-in-browser
techer
2.0.0
techer.open-in-browser-2.0.0

vscodeintellicode-csharp
ms-dotnettools
0.1.26
ms-dotnettools.vscodeintellicode-csharp-0.1.26-win32-x64

@tmeschter is devkit calling out to C# here - or is this an error talking to a different service?

Looks like devkit is losing the connection to the C# extension.
@Anurella would you mind changing the dotnet.server.trace configuration to Trace and posting the logs from the C# output window as well when you hit this issue?

Looks like devkit is losing the connection to the C# extension.
@Anurella would you mind changing the dotnet.server.trace configuration to Trace and posting the logs from the C# output window as well when you hit this issue?

@dibarbet may I ask what the steps are to make the change?
I would also look out for it once the change has been made.

@Anurella modify the value in vscode settings, then reload the window (cntrl+shift+p, type 'reload window')

Then share the contents of the C# output window.  Thanks!

@dibarbet please see below content, tried to take the earlier bits as the output was a lot to paste on here

 C# output after changing server config
Using dotnet configured on PATH
Dotnet path: C:\Program Files\dotnet\dotnet.exe
Activating C# + C# Dev Kit + C# IntelliCode...
Starting server at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.LanguageServer.dll
Server arguments c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.LanguageServer.dll --logLevel Trace --starredCompletionComponentPath c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.vscodeintellicode-csharp-0.1.26-win32-x64\components\starred-suggestions\node_modules\@vsintellicode\starred-suggestions-csharp --sharedDependencies<EMAIL_ADDRESS>--extension<EMAIL_ADDRESS>--sessionId fb3d43af-953b-4c58-9145-08ff7df16c3f1698397575556 --telemetryLevel all --extensionLogDirectory c:\Users\ndukwua\AppData\Roaming\Code\logs\20231027T092304\window1\exthost\ms-dotnettools.csharp
waiting for named pipe information from server...
[stdout] trce: Program[0]
      .NET Runtime Version: .NET 7.0.9
[stdout] dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.AnalyzerUtilities.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.CSharp.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.CSharp.Features.dll added to workspace.
[stdout] dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.CSharp.Workspaces.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.Elfie.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.ExternalAccess.RazorCompiler.dll added to workspace.
[stdout] dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.Features.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.Razor.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.Remote.Workspaces.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.Scripting.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.Workspaces.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.Workspaces.MSBuild.BuildHost.dll added to workspace.
dbug: LanguageServerWorkspaceFactory[0]
      Solution-level analyzer at c:\Users\ndukwua\.vscode\extensions\ms-dotnettools.csharp-2.8.23-win32-x64\.roslyn\Microsoft.CodeAnalysis.Workspaces.MSBuild.dll added to workspace.
[stdout] {"pipeName":"\\\\.\\pipe\\8dbe97f6-09e2-4e3b-9754-d2c6c7c518b5"}
received named pipe information from server
attempting to connect client to server...
client has connected to server
[Info  - 10:06:18 AM] [Program] Language server initialized
[LanguageServerHost] [09:06:18.771][Start]initialize
[LanguageServerHost] [09:06:18.776][Start]Initialize
[LanguageServerHost] [09:06:18.831][End]Initialize
[LanguageServerHost] [09:06:18.854][End]initialize
[LanguageServerHost] [09:06:18.869][Start]initialized
[LanguageServerHost] [09:06:18.928][End]initialized
[LanguageServerHost] [09:06:18.930][Start]serviceBroker/connect
[BrokeredServiceTraceListener] ServiceBroker Information: 1 :
[BrokeredServiceTraceListener] SameProcess proffered brokered service(s): Microsoft.VisualStudio.RemoteBrokeredServiceManifest (0.2).
[BrokeredServiceTraceListener] ServiceBroker Information: 1 :
[BrokeredServiceTraceListener] SameProcess proffered brokered service(s): Microsoft.VisualStudio.GlobalBrokeredServiceContainer.MissingServiceDiagnostics (1.0).
[BrokeredServiceTraceListener] ServiceBroker Information: 1 :
[BrokeredServiceTraceListener] SameProcess proffered brokered service(s): Microsoft.ServiceHub.Framework.AuthorizationService.
[LanguageServerHost] [09:06:18.946][Start]workspace/diagnostic
[LanguageServerHost] PublicWorkspacePullDiagnosticsHandler(category: , source: ) started getting diagnostics
[LanguageServerHost] previousResults.Length=0
[LanguageServerHost] Processing 0 documents
[BrokeredServiceTraceListener] ServiceBroker Information: 1 :
[BrokeredServiceTraceListener] SameProcess proffered brokered service(s): Microsoft.VisualStudio.LanguageServices.WorkspaceProjectFactoryService, Microsoft.CodeAnalysis.LanguageServer.ManagedHotReloadLanguageService (0.1), Microsoft.VisualStudio.Server.IBrokeredServiceBridgeManifest (0.1).
[Microsoft.CodeAnalysis.LanguageServer.BrokeredServices.BrokeredServiceBridgeProvider] Setting up brokered service bridge
[LanguageServerHost] [09:06:18.969][End]serviceBroker/connect
[BrokeredServiceTraceListener] ServiceBroker Information: 0 :
[BrokeredServiceTraceListener] Added local RPC method "handshake" -> Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.HandshakeAsync(ServiceBrokerClientMetadata, CancellationToken) (Microsoft.ServiceHub.Framework.IpcRelayServiceBroker)
[BrokeredServiceTraceListener] ServiceBroker Information: 0 :
[BrokeredServiceTraceListener] Added local RPC method "requestServiceChannel" -> Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.RequestServiceChannelAsync(ServiceMoniker, ServiceActivationOptions, CancellationToken) (Microsoft.ServiceHub.Framework.IpcRelayServiceBroker)
[BrokeredServiceTraceListener] ServiceBroker Information: 0 :
[BrokeredServiceTraceListener] Added local RPC method "cancelServiceRequest" -> Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.CancelServiceRequestAsync(Guid) (Microsoft.ServiceHub.Framework.IpcRelayServiceBroker)
[BrokeredServiceTraceListener] ServiceBroker Information: 0 :
[BrokeredServiceTraceListener] Added local RPC method "dispose" -> Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.Dispose() (Microsoft.ServiceHub.Framework.IpcRelayServiceBroker)
[BrokeredServiceTraceListener] ServiceBroker Information: 0 :
[BrokeredServiceTraceListener] Added local RPC method "handshake" -> Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.HandshakeAsync(ServiceBrokerClientMetadata, CancellationToken) (Microsoft.ServiceHub.Framework.IpcRelayServiceBroker)
[BrokeredServiceTraceListener] ServiceBroker Information: 0 :
[BrokeredServiceTraceListener] Added local RPC method "requestServiceChannel" -> Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.RequestServiceChannelAsync(ServiceMoniker, ServiceActivationOptions, CancellationToken) (Microsoft.ServiceHub.Framework.IpcRelayServiceBroker)
[BrokeredServiceTraceListener] ServiceBroker Information: 0 :
[BrokeredServiceTraceListener] Added local RPC method "cancelServiceRequest" -> Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.CancelServiceRequestAsync(Guid) (Microsoft.ServiceHub.Framework.IpcRelayServiceBroker)
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Listening for events from Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.AvailabilityChanged to raise notification.
[BrokeredServiceTraceListener] ServiceBroker Information: 3 :
[BrokeredServiceTraceListener] Listening started.
[BrokeredServiceTraceListener] ServiceBroker Information: 7 :
[BrokeredServiceTraceListener] {"id":2,"method":"handshake"}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 7 :
[BrokeredServiceTraceListener] Received: {"jsonrpc":"2.0","id":2,"method":"handshake","params":[{"supportedConnections":"IpcPipe","localServiceHost":{"operatingSystem":0,"processArchitecture":1,"runtime":2,"runtimeVersion":"7.0.9"}}]}
[BrokeredServiceTraceListener] ServiceBroker Information: 6 :
[BrokeredServiceTraceListener] Received request "2" for method "handshake".
[BrokeredServiceTraceListener] ServiceBroker Information: 0 :
[BrokeredServiceTraceListener] Added local RPC method "availabilityChanged" -> _proxy_Microsoft.ServiceHub.Framework.IRemoteServiceBroker_a17399c5-ebf1-4e55-940c-68acd0601360.OnAvailabilityChanged(BrokeredServicesChangedEventArgs) (_proxy_Microsoft.ServiceHub.Framework.IRemoteServiceBroker_a17399c5-ebf1-4e55-940c-68acd0601360)
[BrokeredServiceTraceListener] ServiceBroker Information: 3 :
[BrokeredServiceTraceListener] Listening started.
[BrokeredServiceTraceListener] ServiceBroker Information: 1 :
[BrokeredServiceTraceListener] IRemoteServiceBroker proffered from remote source: OtherProcessOnSameMachine.
[BrokeredServiceTraceListener] ServiceBroker Information: 1 :
[BrokeredServiceTraceListener] OtherProcessOnSameMachine proffered brokered service(s): vs-intellicode-base-models (0.1), Microsoft.VisualStudio.ProjectSystem.ProjectInitializationStatusService (0.1), Microsoft.CodeAnalysis.LanguageClient.SolutionSnapshotProvider (0.1), Microsoft.VisualStudio.Debugger.ManagedHotReloadService (0.1).
[BrokeredServiceTraceListener] ServiceBroker Information: 9 :
[BrokeredServiceTraceListener] Invoking Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.HandshakeAsync(ServiceBrokerClientMetadata, CancellationToken)
[BrokeredServiceTraceListener] ServiceBroker Start: 0 :
[BrokeredServiceTraceListener] handshake
[BrokeredServiceTraceListener] ServiceBroker Stop: 0 :
[BrokeredServiceTraceListener] handshake
[BrokeredServiceTraceListener] ServiceBroker Information: 8 :
[BrokeredServiceTraceListener] {"id":2}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 8 :
[BrokeredServiceTraceListener] Sent: {"jsonrpc":"2.0","id":2,"result":null}
[BrokeredServiceTraceListener] ServiceBroker Information: 7 :
[BrokeredServiceTraceListener] {"id":3,"method":"requestServiceChannel"}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 7 :
[BrokeredServiceTraceListener] Received: {"jsonrpc":"2.0","id":3,"method":"requestServiceChannel","params":[{"name":"Microsoft.VisualStudio.Server.IBrokeredServiceBridgeManifest","version":"0.1"},{"clientCulture":"en-US","clientUICulture":"en-US"}]}
[BrokeredServiceTraceListener] ServiceBroker Information: 6 :
[BrokeredServiceTraceListener] Received request "3" for method "requestServiceChannel".
[BrokeredServiceTraceListener] ServiceBroker Information: 9 :
[BrokeredServiceTraceListener] Invoking Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.RequestServiceChannelAsync(ServiceMoniker, ServiceActivationOptions, CancellationToken)
[BrokeredServiceTraceListener] ServiceBroker Start: 0 :
[BrokeredServiceTraceListener] requestServiceChannel
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=3a43fc7c-85ef-4d77-a823-12f802e05f50
[BrokeredServiceTraceListener] ServiceBroker Start: 0 :
[BrokeredServiceTraceListener] Requesting pipe to "Microsoft.VisualStudio.Server.IBrokeredServiceBridgeManifest (0.1)"
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for "Microsoft.VisualStudio.Server.IBrokeredServiceBridgeManifest (0.1)" will be fulfilled by SameProcess
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=263969ab-2d10-4f35-bd60-f05287ffa08a
[BrokeredServiceTraceListener] ServiceBroker Start: 0 :
[BrokeredServiceTraceListener] Requesting proxy to "Microsoft.ServiceHub.Framework.AuthorizationService"
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for "Microsoft.ServiceHub.Framework.AuthorizationService" will be fulfilled by SameProcess
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for proxy to "Microsoft.ServiceHub.Framework.AuthorizationService" is Fulfilled by SameProcess: NoExplanation.
[BrokeredServiceTraceListener] ServiceBroker Stop: 0 :
[BrokeredServiceTraceListener] Requesting proxy to "Microsoft.ServiceHub.Framework.AuthorizationService"
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=3a43fc7c-85ef-4d77-a823-12f802e05f50
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for pipe to "Microsoft.VisualStudio.Server.IBrokeredServiceBridgeManifest (0.1)" is Fulfilled by SameProcess: NoExplanation.
[BrokeredServiceTraceListener] ServiceBroker Stop: 0 :
[BrokeredServiceTraceListener] Requesting pipe to "Microsoft.VisualStudio.Server.IBrokeredServiceBridgeManifest (0.1)"
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=a0371d5f-8ef4-416a-b9ac-5016a4dcb818
[BrokeredServiceTraceListener] ServiceBroker Stop: 0 :
[BrokeredServiceTraceListener] requestServiceChannel
[BrokeredServiceTraceListener] ServiceBroker Information: 8 :
[BrokeredServiceTraceListener] {"id":3}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 8 :
[BrokeredServiceTraceListener] Sent: {"jsonrpc":"2.0","id":3,"result":{"requestId":"21d56138-2215-4801-99e3-bae3f4212dca","pipeName":"3b459d28f931450ba5a061faafd709b8"}}
[Microsoft.CodeAnalysis.LanguageServer.BrokeredServices.Services.BrokeredServiceBridgeManifest.BrokeredServiceBridgeManifest] Proffered services: Microsoft.VisualStudio.LanguageServices.WorkspaceProjectFactoryService,Microsoft.CodeAnalysis.LanguageServer.ManagedHotReloadLanguageService (0.1)
[BrokeredServiceTraceListener] ServiceBroker Information: 7 :
[BrokeredServiceTraceListener] {"id":4,"method":"requestServiceChannel"}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 7 :
[BrokeredServiceTraceListener] Received: {"jsonrpc":"2.0","id":4,"method":"requestServiceChannel","params":[{"name":"Microsoft.VisualStudio.LanguageServices.WorkspaceProjectFactoryService"},{"clientCredentials":{},"clientCulture":"en-US","clientUICulture":"en-US"}],"traceparent":"00-e3ce4b1c9101294b805f725b912ef1b8-ea78dfdf68b67c46-00"}
[BrokeredServiceTraceListener] ServiceBroker Information: 6 :
[BrokeredServiceTraceListener] Received request "4" for method "requestServiceChannel".
[BrokeredServiceTraceListener] ServiceBroker Information: 9 :
[BrokeredServiceTraceListener] Invoking Microsoft.ServiceHub.Framework.IpcRelayServiceBroker.RequestServiceChannelAsync(ServiceMoniker, ServiceActivationOptions, CancellationToken)
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=91cc2542-bbb4-4ccc-8f4d-aa02c8d83508
[BrokeredServiceTraceListener] ServiceBroker Start: 0 :
[BrokeredServiceTraceListener] requestServiceChannel
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=69f1c1d1-28ec-4ad6-bfa4-9ab560dd41b8
[BrokeredServiceTraceListener] ServiceBroker Start: 0 :
[BrokeredServiceTraceListener] Requesting pipe to "Microsoft.VisualStudio.LanguageServices.WorkspaceProjectFactoryService"
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for "Microsoft.VisualStudio.LanguageServices.WorkspaceProjectFactoryService" will be fulfilled by SameProcess
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=b30fef93-32df-48be-9785-dc72d0b3394e
[BrokeredServiceTraceListener] ServiceBroker Start: 0 :
[BrokeredServiceTraceListener] Requesting proxy to "Microsoft.ServiceHub.Framework.AuthorizationService"
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for "Microsoft.ServiceHub.Framework.AuthorizationService" will be fulfilled by SameProcess
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for proxy to "Microsoft.ServiceHub.Framework.AuthorizationService" is Fulfilled by SameProcess: NoExplanation.
[BrokeredServiceTraceListener] ServiceBroker Stop: 0 :
[BrokeredServiceTraceListener] Requesting proxy to "Microsoft.ServiceHub.Framework.AuthorizationService"
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=69f1c1d1-28ec-4ad6-bfa4-9ab560dd41b8
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=c9d6a1dd-8167-47b1-a1cf-37aac1c227eb
[BrokeredServiceTraceListener] ServiceBroker Start: 0 :
[BrokeredServiceTraceListener] Requesting proxy to "Microsoft.VisualStudio.ProjectSystem.ProjectInitializationStatusService (0.1)"
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for "Microsoft.VisualStudio.ProjectSystem.ProjectInitializationStatusService (0.1)" will be fulfilled by OtherProcessOnSameMachine
[BrokeredServiceTraceListener] ServiceBroker Information: 8 :
[BrokeredServiceTraceListener] {"id":2,"method":"handshake"}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 8 :
[BrokeredServiceTraceListener] Sent: {"jsonrpc":"2.0","id":2,"method":"handshake","params":[{"supportedConnections":"Multiplexing, IpcPipe","localServiceHost":{"operatingSystem":0,"processArchitecture":1,"runtime":2,"runtimeVersion":"7.0.9"}}],"traceparent":"00-dda1d6c96781b147a1cf37aac1c227eb-483dd7f6a81d854d-01"}
[BrokeredServiceTraceListener] ServiceBroker Information: 7 :
[BrokeredServiceTraceListener] {"id":2}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 7 :
[BrokeredServiceTraceListener] Received: {"jsonrpc":"2.0","id":2,"result":null}
[BrokeredServiceTraceListener] ServiceBroker Information: 11 :
[BrokeredServiceTraceListener] Received result for request "2".
[BrokeredServiceTraceListener] ServiceBroker Information: 8 :
[BrokeredServiceTraceListener] {"id":3,"method":"requestServiceChannel"}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 8 :
[BrokeredServiceTraceListener] Sent: {"jsonrpc":"2.0","id":3,"method":"requestServiceChannel","params":[{"name":"Microsoft.VisualStudio.ProjectSystem.ProjectInitializationStatusService","version":"0.1"},{"clientCredentials":{},"clientCulture":"en-US","clientUICulture":"en-US"}],"traceparent":"00-dda1d6c96781b147a1cf37aac1c227eb-ff1462615b9ac644-01"}
[BrokeredServiceTraceListener] ServiceBroker Information: 7 :
[BrokeredServiceTraceListener] {"id":3}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 7 :
[BrokeredServiceTraceListener] Received: {"jsonrpc":"2.0","id":3,"result":{"requestId":"a3db05eb-3639-43fd-a059-2a33bbca11de","multiplexingChannelId":3}}
[BrokeredServiceTraceListener] ServiceBroker Information: 11 :
[BrokeredServiceTraceListener] Received result for request "3".
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for proxy to "Microsoft.VisualStudio.ProjectSystem.ProjectInitializationStatusService (0.1)" is Fulfilled by OtherProcessOnSameMachine: NoExplanation.
[BrokeredServiceTraceListener] ServiceBroker Stop: 0 :
[BrokeredServiceTraceListener] Requesting proxy to "Microsoft.VisualStudio.ProjectSystem.ProjectInitializationStatusService (0.1)"
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=69f1c1d1-28ec-4ad6-bfa4-9ab560dd41b8
[BrokeredServiceTraceListener] ServiceBroker Information: 2 :
[BrokeredServiceTraceListener] Request for pipe to "Microsoft.VisualStudio.LanguageServices.WorkspaceProjectFactoryService" is Fulfilled by SameProcess: NoExplanation.
[BrokeredServiceTraceListener] ServiceBroker Stop: 0 :
[BrokeredServiceTraceListener] Requesting pipe to "Microsoft.VisualStudio.LanguageServices.WorkspaceProjectFactoryService"
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=91cc2542-bbb4-4ccc-8f4d-aa02c8d83508
[BrokeredServiceTraceListener] ServiceBroker Stop: 0 :
[BrokeredServiceTraceListener] requestServiceChannel
[BrokeredServiceTraceListener] ServiceBroker Transfer: 0 :
[BrokeredServiceTraceListener] Transfer, relatedActivityId=1c4bcee3-0191-4b29-805f-725b912ef1b8
[BrokeredServiceTraceListener] ServiceBroker Information: 8 :
[BrokeredServiceTraceListener] {"id":4}
[BrokeredServiceTraceListener] ServiceBroker Verbose: 8 :
[BrokeredServiceTraceListener] Sent: {"jsonrpc":"2.0","id":4,"result":{"requestId":"9209e3a0-9b45-4e11-9676-e3544527286b","pipeName":"15cfa9f99b25421d962a13fdc485f76c"}}

Thanks - based on those logs it doesn't appear as though anything is explicitly going wrong in the C# extension, it looks like it is still running.
A couple more things to confirm

After you hit this error - is there still a process for the C# server?  You can check by looking for a process with 'Microsoft.CodeAnalysis.LanguageServer.dll' in the command line.  For example in powershell:Get-WmiObject Win32_Process -Filter "name = 'dotnet.exe'" | Select-Object Name,ProcessId,CommandLine | Select-String 'Microsoft.CodeAnalysis.LanguageServer'

Will output something like this if it exists:

Can you zip up and attach the contents of the extension logs folder?  You can find it here:

Hello @dibarbet please find zipped folder. I hope it helps
logsa.zip

@Anurella apologies for the delay, taking a look at the extension logs now, a bunch of logs appear to be missing.  I'm not seeing any of the output window logging which is super important.  Best way to get these

Open VSCode, run the steps to reproduce the issue
From that same VSCode instance, open that extensions log folder, and include everything inside it.  If you'd rather not post it on a public github issue, feel free to send to my microsoft email (dabarbet@microsoft.com).

Thanks!

Thank you @dibarbet. I have sent the email

Thank you @dibarbet. I have sent the email

Got it- thanks!  Will take a look this week.

Aha - this log has the correct details - thanks!
The error:
[Error - 8:36:53 AM] [LanguageServerHost] System.InvalidOperationException: didOpen received for virtualcsharp-razor:///c:/Users/ndukwua/Work/Websites/KCOM.Shop.Web/src/KCOM.Shop.Web/Views/Partials/BlockList/Components/SliderSection.cshtml__virtual.cs which is already open. - line 106
   at Roslyn.Utilities.Contract.Fail(String message, Int32 lineNumber) in /_/src/Workspaces/SharedUtilitiesAndExtensions/Compiler/Core/Utilities/Contract.cs:line 154
   at Microsoft.CodeAnalysis.LanguageServer.LspWorkspaceManager.StartTrackingAsync(Uri uri, SourceText documentText, String languageId, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Protocol/Workspaces/LspWorkspaceManager.cs:line 106
   at Microsoft.CodeAnalysis.LanguageServer.Handler.DocumentChanges.DidOpenHandler.HandleNotificationAsync(DidOpenTextDocumentParams request, RequestContext context, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Protocol/Handler/DocumentChanges/DidOpenHandler.cs:line 42
   at Microsoft.CommonLanguageServerProtocol.Framework.QueueItem`3.StartRequestAsync(TRequestContext context, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Microsoft.CommonLanguageServerProtocol.Framework/QueueItem.cs:line 136
   at Microsoft.CommonLanguageServerProtocol.Framework.QueueItem`3.StartRequestAsync(TRequestContext context, CancellationToken cancellationToken)
   at Microsoft.CommonLanguageServerProtocol.Framework.RequestExecutionQueue`1.ProcessQueueAsync() in /_/src/Features/LanguageServer/Microsoft.CommonLanguageServerProtocol.Framework/RequestExecutionQueue.cs:line 239

This is potentially the same as https://github.com/dotnet/vscode-csharp/issues/6644, which will hopefully be fixed in this weeks release.  However its hard to tell without the solution file.
@ryzngard would you mind taking a look here since this looks like an issue on the Razor side?  I am seeing two entries for the same file in the Razor log:
Trying to create DocumentContext for textDocument/didClose for (no project context) for file:///c%3A/Users/ndukwua/Work/Websites/KCOM.Shop.Web/src/KCOM.Shop.Web/Views/Partials/BlockList/Components/SliderSection.cshtml
...
Trying to create DocumentContext for textDocument/didClose for (no project context) for file:///c%3A/Users/ndukwua/Work/Websites/KCOM.Shop.Web/src/KCOM.Shop.Web/Views/Partials/BlockList/Components/SliderSection.cshtml

Agree this looks the same. @Anurella can you confirm if there is a possible difference in casing somewhere in your csproj files and on disk naming?

@ryzngard there is no difference in the naming, only one file exists.
Or can you help clarify what you would need me to check specifically. Thank you

@Anurella is there a solution you can share? Either or on GitHub or private e-mailing me ? That would be the easiest way for me to verify

@Anurella , if you have a solution that repros this issue, can you share it with us so that we can diagnose the particular cause of the issue?

To be honest I am not sure I have. I sent the log files to @ryzngard when I encountered it.
Not worked on the file in a minute so I have not had to encounter the issue. But I think it might be a case of the razor formatter and prettier being active at the same time.

Let me double check my email, I have a few logs sent to me and for some reason thought this issue I didn't get them.

I apologize @Anurella but I can't seem to find the e-mail. Do you mind resending? I checked spam just in case as well but no luck.

I am sorry it was @dibarbet I sent it to initially, but I have sent it to you now. Do let me know if you get it.

@Anurella I don't see the initial error in the logs you sent, but I do see a lot of exceptions around SemanticTokensRange being incorrect on request. This looks like it might be similar to https://github.com/dotnet/razor/issues/9598 (and others that we haven't correlated yet, but I'm sure we have). Can you confirm you're seeing those exceptions normally?
The original exception I was looking for, Project system data flow 'Workspace update handler... was not contained in the logs

Closing as not enough info, if you're still hitting issues on the latest extensions, please re-open with the information requested above.

Thank you and noted @dibarbet


feat: PRT-add-block-error-parsing-capability

Description
this feature allows the consumer to dynamically identify block errors and update it's relay state machine accordingly, be it a block that is too early or too advanced. this feature is especially effective if there's a missing parsing capability, since it allows the system to identify archive is needed

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] read the contribution guide
[ ] included the correct type prefix in the PR title, you can find examples of the prefixes below:

[ ] confirmed ! in the type prefix if API or client breaking change
[ ] targeted the main branch
[ ] provided a link to the relevant issue or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] included the necessary unit and integration tests
[ ] updated the relevant documentation or specification, including comments for documenting Go code
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

errors contain arbitrary data that is additional to the block making the parsing more difficult than planned


update to node 18. Closes #413

It's not as simple as updating .nvmrc, please see details in https://github.com/verida/verida-js/issues/402

While all the thing in #402 are probably correct we've been running things under node 18 for a while (not node 20). Also for a library it seems to make sense to move to the lowest possible version so we don't lockout other projects that are on node 18.
We have to do something and this seems extremely safe.

While all the thing in #402 are probably correct we've been running things under node 18 for a while (not node 20). Also for a library it seems to make sense to move to the lowest possible version so we don't lockout other projects that are on node 18.
We have to do something and this seems extremely safe.

I disagree.
This PR only updates .nvmrc which is only used for dev, tests and build. The engine requirements is what's important and what constrain other projects.
The engine is currently defined with node >=14 but our tests are run with whatever is defined in .nvmrc so if it is node 18, there is no guarantee these libraries will work on node 14 to 17, so, no, it is not extremely safe!
It is reasonable to think no projects should run on node lower than 18 (actually even 20), so if we "have to do something", it is about upgrading the engine requirement. It's a breaking change and the purpose of #402, which highlight a broader consideration, with changes across package.json, tsconfig.json and .nvmrc. That's my point, it's not as simple as only updating .nvmrc.

The engine is currently defined with node >=14 but our tests are run with whatever is defined in .nvmrc so if it is node 18, there is no guarantee our libraries will work on node 14 to 17. So, no, it is not extremely safe!

Yes this is a good point. But it's still better than now where the tests run in node 14 (which - again - is about to be out of maintenance)
I agree we should do all the things in #402 (although I think I'd still argue for node 18 instead of node 20).
I don't have time to do all of them now though, and by doing this change at least we'd test under the same node version we run things on!

(I was going to update the version in package.json too but clearly we don't want to do that since we still want to allow people to use earlier versions if they choose)

I agree we should do all the things in https://github.com/verida/verida-js/issues/402 (although I think I'd still argue for node 18 instead of node 20).

#402 suggests node 20 in .nvmrc only if we run the tests on multiple node version, otherwise .nvmrc should be aligned with the engine requirement.

(I was going to update the version in package.json too but clearly we don't want to do that since we still want to allow people to use earlier versions if they choose)

#402 suggests the engine requirement to be node >= 16, to take into account that 14 is obsolete but 16 is still maintained and we want to support projects still using it.

by doing this change at least we'd test under the same node version we run things on!

"... we run things on" but we are not the only one running things on. At this stage it's fair to say we are the main consumer of the SDK and we know who use it and can inform them there's a lack of test converage on earlier supposedly supported node version. But I personally don't want this to be a precedent, so by principle I will stay against this PR as it is. I'll leave @tahpot with the decision to merge it.

This now fixes the docs and updates lerna too


Write JWT middleware

Tell the middleware how to retrieve/store the token. Set the token as 'Authorization' header for every request. Trigger "auth_expired" or some such event on failure. We'll have to determine how we want to handle refreshes down the road. Probably the same as oAuth... maybe can just use oauth middleware for everything?
Make sure to document in the readme the events that are dispatched and when they're dispatched.

Closing. Moved to LK