"az keyvault create \     --resource-group learn-33b14343-8e20-4365-a4c2-afac1f90aaaa \     --location centralus \     --name " ERROR

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az keyvault create
Errors:
400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token
Traceback (most recent call last):
python3.6/site-packages/knack/cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 608, in execute
    raise ex
cli/core/commands/__init__.py, ln 666, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli/core/commands/__init__.py, ln 659, in _run_job
    six.reraise(*sys.exc_info())
...
python3.6/site-packages/msrestazure/azure_active_directory.py, ln 486, in get_msi_token
    result.raise_for_status()
python3.6/site-packages/requests/models.py, ln 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az keyvault create --resource-group {} --location {} --name {}

Expected Behavior
Environment Summary
Linux-4.15.0-1071-azure-x86_64-with-debian-stretch-sid
Python 3.6.5

azure-cli 2.1.0

Additional Context

Getting same -- reported to https://github.com/Azure/azure-cli/issues/9345

We'll investigate it

Thanks @justSteve for the super useful information.
Hi @jaipaldom , as @justSteve just said that you would get this error when your vault name was too long, I'm not sure whether this is the exact same scenario as yours, but it worth a try! Thanks.

Hi @jaipaldom are you still being blocked by this issue? You may try the above workaround.


Extends context as an object

This PR change context and condition types to support objects.

:tada: This PR is included in version 4.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


4.6: Using BOM import results in generating invalid pom

Using feature preview for BOM import results in invalid pom being generated.
dependencies {
    // import a BOM
    implementation 'org.springframework.boot:spring-boot-dependencies:1.5.8.RELEASE'

    // define dependencies without versions
    implementation 'com.google.code.gson:gson'
    implementation 'dom4j:dom4j'
}

Expected Behavior
Expected would be either:
  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-dependencies</artifactId>
        <version>1.5.8.RELEASE</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>

  <dependencies>
    <dependency>
      <groupId>com.google.code.gson</groupId>
      <artifactId>gson</artifactId>
    </dependency>
    <dependency>
      <groupId>dom4j</groupId>
      <artifactId>dom4j</artifactId>
    </dependency>
  </dependencies>

or:
  <dependencies>
    <dependency>
      <groupId>com.google.code.gson</groupId>
      <artifactId>gson</artifactId>
        <version>2.8.2</version>
    </dependency>
    <dependency>
      <groupId>dom4j</groupId>
      <artifactId>dom4j</artifactId>
        <version>1.6.1</version>
    </dependency>
  </dependencies>

Current Behavior
  <dependencies>
    <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-dependencies</artifactId>
      <version>1.5.8.RELEASE</version>
      <scope>runtime</scope>
    </dependency>
    <dependency>
      <groupId>com.google.code.gson</groupId>
      <artifactId>gson</artifactId>
      <scope>runtime</scope>
    </dependency>
    <dependency>
      <groupId>dom4j</groupId>
      <artifactId>dom4j</artifactId>
      <scope>runtime</scope>
    </dependency>
  </dependencies>

Context
Generated pom then can't be consumed as dependency of maven project. Given following warning:
[WARNING] Invalid POM for com.gradle.test:dep-pom:jar:1.0-SNAPSHOT, transitive dependencies (if any) will not be available, enable debug logging for more details: Some problems were encountered while processing the POMs:

Steps to Reproduce (for bugs)
Use snippet from User Guide documentation.
Your Environment
Gradle 4.6

Publication has been addressed for the maven-publish plugin, but not the maven plugin.

However, decided not to address the maven plugin since it is to be deprecated.

@ljacomet Hi, I just gave it a quick try with the latest nightly and I have the same problem. Could you please explain how I am supposed to import a bom in Gradle 5.0 in order to have the right pom published?


Feat: Drizzle-ORM support for Generated columns

This PR will close #261, will close #579 and will close #1464.
The API for generated columns will look like this:
const users = sqliteTable(
  'users',
  {
    id: int('id').primaryKey(),
    firstName: text('first_name', { length: 255 }),
    lastName: text('last_name', { length: 255 }),
    email: text('email').notNull(),
    fullName: text('full_name').generatedAlwaysAs(sql`concat_ws(first_name, ' ', last_name)`, { mode: 'stored' }),
    upperName: text('upper_name').generatedAlwaysAs(
      sql` case when first_name is null then null else upper(first_name) end `,
      { mode: 'virtual' }
    ).$type<string | null>(), // There is no way for drizzle to detect nullability in these cases. This is how the user can work around it
  },
);

In Postgres there is also a new method on integer bigint and smallint columns called .generatedAsIdentity()
You can pass a configuration object that will be different depending on your dialect:
// MySql & SQLite:
interface config {
  mode?: 'virtual' | 'stored';  // virtual is default
}

// Pg only for .generatedAsIdentity() method
interface config {
  type?: 'always' | 'byDefault';  // always is the default
}

For this table, the inferred types will be as follows:
type User = typeof users.$inferSelect;
    // ^?  {
    //   id: number;
    //   firstName: string | null;
    //   lastName: string | null;
    //   email: string;
    //   fullName: string;
    //   upperName: string | null;
    // },

type NewUser = typeof users.$inferInsert;
    // ^?  {
    //   email: string;
    //   id?: number | undefined;
    //   firstName?: string | null | undefined;
    //   lastName?: string | null | undefined;
    // },

Please note that drizzle kit support for this is still pending.

This will also close #1239

Any updates on this? Thank you!

This looks awesome! What's holding up merging this PR? Generated columns are currently very difficult, because of the custom type bug in drizzle-kit https://github.com/drizzle-team/drizzle-kit-mirror/issues/167.

Is there anything the community can do to help this move forward? It's currently kind of cumbersome to create a custom type every time we need a generated column and this feature would make schema declarations much cleaner imho.

Echoing the comments above on how we can help move this PR forward -- I think this PR adds some fairly necessary functionality!

It is time to ditch the PostgreSQL specific way of doing auto incremented columns with SERIAL.

Changing an a bit API to this and adding it to drizzle-kit and releasing. Finally 💪
Thanks @Angelelz a lot! I'll take from here and finish everything we think should be changed
export const seq = pgSeq('seq_name', { min, by, ... })

// pg
.generatedAlwaysAs((): SQL => sql`${user.firstName}`, { mode?: 'stored' })
.generatedAlwaysAs(sql``, { mode?: 'stored' })

.generatedAlwaysAsIdentity(seq)
.generatedAlwaysAsIdentity({ name?, min, by, ... })

.generatedByDefaultAsIdentity(seq)

// mysql
.generatedAlwaysAs(sql``, { mode?: 'stored' | 'virtual' })
.generatedAlwaysAs((): SQL => sql`${user.firstName}`, { mode?: 'stored' | 'virtual' })

// sqlite
.generatedAlwaysAs(sql``, { mode?: 'stored' | 'virtual' })
.generatedAlwaysAs((): SQL => sql`${user.firstName}`, { mode?: 'stored' | 'virtual' })

Finally found a proper strategy and queries so that generated columns and identity columns can work with push, introspect, and generate. Adding all of that to drizzle-kit, and I guess we are going live.

Any ETA on when this will get merged? Our team would greatly benefit from this feature. Thank you!

Thank you all for your hard work. Is this feature ready to be merged?

Maybe, in the meantime, leave an example in the docs with the necessary SQL code to make this happen?

For Postgres users here is a patch-package to fix this with drizzle-kit
diff --git a/node_modules/drizzle-kit/bin.cjs b/node_modules/drizzle-kit/bin.cjs
index 9b92321..d347342 100755
--- a/node_modules/drizzle-kit/bin.cjs
+++ b/node_modules/drizzle-kit/bin.cjs
@@ -15496,6 +15496,7 @@ var init_sqlgenerator = __esm({
       "interval minute to second"
     ]);
     isPgNativeType = (it) => {
+      return true
       if (pgNativeTypes.has(it))
         return true;
       const toCheck = it.replace(/ /g, "");

I've only tested this type, test other custom types as I have no clue if this will break them
import { customType } from "drizzle-orm/pg-core";
export const identity = (name: string) =>
  customType<{
    data: string;
    notNull: true;
    default: true;
  }>({
    dataType() {
      return "BIGINT GENERATED ALWAYS AS IDENTITY";
    },
  })(name);

Heya, thanks a lot for amazing work!
Are there any plans to finish this up soon? Thanks!

LGTM 🇺🇸🚀

Adding a +1 for this - would love to use generated columns for post comment counts and such! It would get widespread use throughout the app I'm building. 🙏 😁

+1 for this!

+1 for this, would be great for generated columns in fulltext search for types like arrays with tags for example!

Back in March it sounded like this PR was set to be merged, and then progress stalled. I can't find the discussion now, but I remember reading in Discord that the Drizzle team was going to make some major changes to schema definition implying that it would require a different approach for generated columns. (Maybe this? https://github.com/drizzle-team/drizzle-orm/discussions/2316) So I wouldn't expect this PR to get merged soon.
Personally, after waiting several months for generated columns I couldn't wait any longer.  I ended up ripping Drizzle out of everything, and just using the Postgres.js driver directly. Which also solved a lot of other issues (e.g. lack of query aggregations, a bug in migration generation for custom types, etc.). It turns out that writing my own TS type definitions was easier than I expected.
Not trying to bash Drizzle. It's excellent. It's just missing some features that I need right now.

Back in March it sounded like this PR was set to be merged, and then progress stalled. I can't find the discussion now, but I remember reading in Discord that the Drizzle team was going to make some major changes to schema definition implying that it would require a different approach for generated columns. (Maybe this? #2316) So I wouldn't expect this PR to get merged soon.
Personally, after waiting several months for generated columns I couldn't wait any longer.  I ended up ripping Drizzle out of everything, and just using the Postgres.js driver directly. Which also solved a lot of other issues (e.g. lack of query aggregations, a bug in migration generation for custom types, etc.). It turns out that writing my own TS type definitions was easier than I expected.
Not trying to bash Drizzle. It's excellent. It's just missing some features that I need right now.

sending this to beta release today, I'm finishing release notes, will update here

Release notes with all the detailed info: https://github.com/drizzle-team/drizzle-orm/releases/tag/v0.32.0-beta
GitHub discussions: https://github.com/drizzle-team/drizzle-orm/discussions/2564


Added example to README

Summary

Type of change

[ ] Bug fix (added a non-breaking change which fixes an issue)
[ ] New feature (added a non-breaking change which adds functionality)
[ ] Updated documentation (updated the readme, templates, or other repo files)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

[ ] Ran tests with composer test
[ ] Added or updated test cases to test new features

Looks good.
I might recommend adjusting the width to be a bit wider (eg. 550 or so) since it seems one of the letters is cut off.

Sure, I've made the recommended change. Width is now set to 550. Thanks!


Roll engine 91ff524e6329..a61fae08247c (6 commits)

https://github.com/flutter/engine/compare/91ff524e6329...a61fae08247c
git log 91ff524e6329..a61fae08247c --date=short --no-merges --format='%%ad %%ae %%s'
2018-08-01<EMAIL_ADDRESS>Dart SDK roll for 8/1/2018 (#5918)
2018-08-01<EMAIL_ADDRESS>Roll src/third_party/skia fd98c2c87164..afea9c32acd9 (1 commits) (#5916)
2018-08-01<EMAIL_ADDRESS>Roll src/third_party/skia f4bf7fc35d83..fd98c2c87164 (1 commits) (#5915)
2018-07-31<EMAIL_ADDRESS>Roll src/third_party/skia 6cfa29738295..f4bf7fc35d83 (2 commits) (#5914)
2018-07-31<EMAIL_ADDRESS>Initial support for more finely-grained a11y features on Window (#5901)
2018-07-31<EMAIL_ADDRESS>Roll src/third_party/skia 1935aa3d27cd..6cfa29738295 (7 commits) (#5912)
The AutoRoll server is located here: http://localhost:8000
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

@rmistry : New roll has been created by http://localhost:8000

Trybots failed. These were the failed builds: https://flutter-dashboard.appspot.com/build.html


GPU and cuda support

Hello,
Is there currently a way to use GPU instead of CPU ?
I started training GNN using the following example GIT project: https://github.com/BNN-UPC/GNN-NIDS
using the function model.train_and_validate()  and receive following output:

closing this issue. IGNNITION uses tensorflow in the background. My device was not properly set up for tensorflow, working now

As @AaronDeRybelHowest pointed out, in order to use the GPU, it is needed to set up CUDA for Tensorflow.
Closing this issue.


Use github as an issue tracker

A lot of open-source projects rely on Github issues for their issue tracker. Since researchers work a lot with open source repositories, I think it's extremely valuable to have a support for retrieving issues from Github issues and using it with SZZUnleashed.
Could this feature be added?

See the fork at https://github.com/fuhrmanator/SZZUnleashed/tree/master/fetch_github_bugs (it's not perfect, but it's a start). It's not been tested a lot with various repos (care must be taken in matching what is a bug, it's noisier on GitHub than on Jira).


Uncaught SyntaxError: Unexpected token }

Adding a .tern-project file to project's root folder (no issues yet)
Fill with content:

{
  "libs": [
      "browser",
      "ecma6"
  ],
}

Atom Version: 1.0.0
System: Mac OS X 10.9.5
Thrown From: atom-ternjs package, v0.6.4
Stack Trace
Uncaught SyntaxError: Unexpected token }
At file:///Applications/Atom.app/Contents/Resources/app.asar/static/index.html#%7B%22locationsToOpen%22%3A%5B%7B%7D%5D%2C%22bootstrapScript%22%3A%22%2FApplications%2FAtom.app%2FContents%2FResources%2Fapp.asar%2Fsrc%2Fwindow-bootstrap.js%22%2C%22resourcePath%22%3A%22%2FApplications%2FAtom.app%2FContents%2FResources%2Fapp.asar%22%2C%22devMode%22%3Afalse%2C%22safeMode%22%3Afalse%2C%22appVersion%22%3A%221.0.0%22%2C%22shellLoadTime%22%3A438%2C%22initialPaths%22%3A%5B%22%2FApplications%2FAMPPS%2Fwww%2Fbabel%22%5D%7D:6

SyntaxError: Unexpected token }
  at Object.parse (native)
  at Config.module.exports.Config.getContent (/Users/Peter/.atom/packages/atom-ternjs/lib/atom-ternjs-config.coffee:26:20)
  at Config.module.exports.Config.gatherData (/Users/Peter/.atom/packages/atom-ternjs/lib/atom-ternjs-config.coffee:61:20)
  at Manager.module.exports.Manager.setActiveServerAndClient (/Users/Peter/.atom/packages/atom-ternjs/lib/atom-ternjs-manager.coffee:110:15)
  at /Users/Peter/.atom/packages/atom-ternjs/lib/atom-ternjs-manager.coffee:180:10
  at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:82:11)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/pane-container.js:343:34
  at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:82:11)
  at Pane.module.exports.Pane.setActiveItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:234:22)
  at Pane.module.exports.Pane.activateItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:298:21)
  at Pane.module.exports.Pane.activateItemAtIndex (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:292:19)
  at Pane.module.exports.Pane.activateNextItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:253:21)
  at Pane.module.exports.Pane.removeItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:370:16)
  at Pane.module.exports.Pane.destroyItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:442:16)
  at HTMLDivElement.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/tabs/lib/tab-bar-view.js:236:22)
  at space-pen-ul.jQuery.event.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4435:9)
  at space-pen-ul.elemData.handle (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4121:28)

Commands
     -8:52.1.0 core:backspace (atom-text-editor.editor.is-focused)
  2x -8:51.1.0 core:move-down (atom-text-editor.editor.is-focused)
     -8:50.8.0 core:select-up (atom-text-editor.editor.is-focused)
     -8:50.5.0 core:backspace (atom-text-editor.editor.is-focused)
     -8:50.2.0 core:save (atom-text-editor.editor.is-focused)
     -8:49.6.0 core:backspace (atom-text-editor.editor.is-focused)
  5x -8:49.4.0 core:save (atom-text-editor.editor.is-focused)
  2x -8:44.5.0 core:backspace (atom-text-editor.editor.is-focused)
  4x -8:43.9.0 core:save (atom-text-editor.editor.is-focused)
     -8:36.1.0 editor:newline (atom-text-editor.editor.is-focused)
  2x -8:35.9.0 core:save (atom-text-editor.editor.is-focused)
  8x -6:21.4.0 core:close (atom-pane.pane.active)
  4x -5:57.8.0 core:save (atom-text-editor.editor.is-focused)
     -5:51.8.0 grammar-selector:show (atom-text-editor.editor)
  4x -5:45.3.0 core:save (atom-text-editor.editor.is-focused)
  3x -5:43 deprecation-cop:view (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-monokai.theme-atom-dark-ui)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "monokai"
    ],
    "disabledPackages": [
      "linter-jshint",
      "whitespace",
      "secure-copy",
      "scp",
      "remote-sync",
      "jshint",
      "auto-detect-indentation",
      "color-picker",
      "git-control",
      "git-history",
      "git-log",
      "highlight-selected",
      "indentation-indicator",
      "keybinding-cheatsheet",
      "language-docker",
      "language-lua",
      "language-openscad",
      "linter-csslint",
      "linter-js-yaml",
      "linter-luacheck",
      "merge-conflicts",
      "motepair",
      "pretty-json",
      "webbox-color",
      "pigments",
      "linter-js-standard",
      "linter-eslint",
      "Tern"
    ],
    "excludeVcsIgnoredPaths": false
  },
  "atom-ternjs": {}
}

Installed Packages
# User
atom-ternjs, v0.6.4
linter, v1.0.6
monokai, v0.14.0

# Dev
No dev packages

I now see that I get better errors when I restart the Tern server (Packages -> Atom Ternjs > Restart server) or reload Atom (View > Reload).
I think it was my mistake, caused by the ,.
The following .tern-project does seem to work:
{   "libs": ["browser","ecma6"] }


RuntimeError: Event loop is closed

Since updating to HA 0.92.1 my instance stopped working which this error:
2019-04-28 21:18:25 ERROR (SyncWorker_1) [concurrent.futures] exception calling callback for <Future at 0x7f4cadf18080 state=finished raised RuntimeError>
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/alexa_media/__init__.py", line 550, in setup_alexa
    update_devices()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/util/__init__.py", line 224, in wrapper
    result = method(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/util/__init__.py", line 224, in wrapper
    result = method(*args, **kwargs)
  File "/config/custom_components/alexa_media/__init__.py", line 340, in update_devices
    config)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/discovery.py", line 130, in load_platform
    hass_config))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 246, in add_job
    self.loop.call_soon_threadsafe(self.async_add_job, target, *args)
  File "uvloop/loop.pyx", line 1261, in uvloop.loop.Loop.call_soon_threadsafe
  File "uvloop/loop.pyx", line 604, in uvloop.loop.Loop._call_soon
  File "uvloop/loop.pyx", line 608, in uvloop.loop.Loop._call_soon_handle
  File "uvloop/loop.pyx", line 637, in uvloop.loop.Loop._check_closed
RuntimeError: Event loop is closed

Does a reboot change anything?

Unfortunately not, that was the second thing I tried after a restart of HA did not help.

@keatontaylor can you take a look at this please? I think I broke something with when I split your async function into helper functions.

Potentially more info from #162


[FEAT] Trigger getList function in custom data provider manually

Is your feature request related to a problem? Please describe.
Is it possible to trigger getList function in custom data provider via useDataGrid hook manually? Currently, I had to call the setFilters function with unique key for each trigger needs. My problem is we have a toggle button in actions and we'd like to refresh datagrid's data(state) after toggle state is changed in a record.
My solution is: Send a same filter props and one unique key to bypass React.memo. There is an useEffect hook which listens every custom mutate so we are able to catch the toggle changes.
useEffect(() => {
    if (customMutateData?.data) {
      setFilters([...filters, { field: Date.now().toString(), operator: 'eq', value: '' }]);
    }
  }, [customMutateData]);

Describe alternatives you've considered
As I reviewed source codes, getList is called in useTable hook after component is initialized.
https://github.com/refinedev/refine/blob/9c4f73e5112f74b77f0ed415f5296ee32fc969dd/packages/core/src/hooks/useTable/index.ts#L511-L530
Additional context
No response
Describe the thing to improve
We'd like to trigger useList, useUpdate and other hooks in DataGrid Component via useDataGrid hook, manually whenever we  want without a trick.

Hey @azmicirit ,
Thank you for getting in touch with us. Does the refetch function work for your use case? You can find more information here: https://refine.dev/docs/faq/#how-can-i-refetch-data"

@omeraplak Sorry, It was my fault. I see now, there is a nested export in useDataGrid hook.


[FLINK-2533] [core] Gap based random sample optimization.

For random sampler with fraction, like BernoulliSampler and PoissonSampler, Gap based random sampler could exploit O(np) sample implementation instead of previous O(n) sample implementation, it should perform better while sample fraction is very small.When deal with large fraction, it's better to use previous sample implementation. So we add a threshold to control the sampling method according to the fraction.(threshold_Bernoulli = 0.33, threshold_Poisson = 0.4)

Thanks for contributing on this, @gallenvara , the micro benchmark result is quite impressive, and the patch looks good, i left some comments, most of them are about file format.

@gallenvara, thanks for the PR.
Looks good to me.

I will merge this PR tomorrow.


ewallet docker container can't start

Subject of the issue
When starting a fresh instance of the ewallet, using docker-compose, the ewallet container keeps restarting.
Your environment
OSX Mojave
~ ■ docker -v
Docker version 18.09.0, build 4d60db4

~ ■ docker-compose -v
docker-compose version 1.23.2, build 1110ad01

Steps to reproduce
All information here : https://gist.github.com/kartsims/3514ed2cdab4abd9b28c46ae9c41ae22
After discussion with @unnawut it appears that since the customizable settings are stored in the DB, the ewallet app makes a query in the DB, which fails, and triggers a restart on the container.
In this context, the seed command can never be executed.
On a sidenote, the docker command proposed to seed could be updated to leverage docker-compose's environment and links as such :
docker-compose run ewallet bash -c "env MIX_ENV=prod mix do local.hex --force, local.rebar --force, ecto.create, ecto.migrate, seed --sample"

Note that it is using run so we can seed the ewallet before starting the container using docker-compose up

Nice! Thanks @sirn
May I suggest to add explicit container names too ? Using default container names (that get suffixed with a number and prefixed with the directory's name) isn't very elegant, and completely useless in a dev environment.
Also, this prevents me from releasing the JS lib for the ewallet API that I am working on (not that the whole world is waiting for it... 😆).

Just a side note that kartsim's docker-compose run ... command worked well for me.
A slight addition so that the runned container doesn't experience the restart loop the same way as the main container by disabling the entrypoint:
$ docker-compose run --entrypoint="" ewallet bash -c "env MIX_ENV=prod mix do local.hex --force, local.rebar --force, ecto.create, ecto.migrate, seed --sample"


Always pull latest cert-manager version

Make sure we're always pulling the latest cert-manager by getting the latest release tag from GitHub and passing it to kubectl apply -f.
This may look shady to some users so i'm open to just mentioning "hey go here and check the latest version number and add it to the URL by hand".
Up to you to decide.

ping @snobu, we'd love to merge this!

I don't really know how the {% include code-block-start.md %} thing works so can only assume it will :)
Also the CI trigger should ignore Markdown files, it's wasted compute. I can send a PR but just checking with you first if it's not intentional.

I can send a PR but just checking with you first if it's not intentional.

That would be great, thanks!


Permalinks Feature - Abel

Stage 1:
Added base permalink functionality.

The application loads the state from local and then compares it with the URL and, if there is a partial match, it uses the data from the local and loads the rest from the DCS API.
App listens for the context state change and changes the permalink accordingly if necessary (if the user interacts with the ApplicationStepper component the URL will change accordingly).
A feature has been added to allow TSVs to be searchable via URL queries.

To do:

Enable the app to navigate back and load previous state from History.state.
Improve performance, and perception of performance (partial rendering of the layout until all data is loaded).

Would like to schedule a meeting to discuss the DCS-API and how that avoids conflicts with the GiteaReactToolkit that is already implemented.
We can also discuss how we might start abstracting the DCS-API hooks so that we can use them in other apps.
Again, Great job!


CLOUD-58877 fix JID response NPE

@schfeca75

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2602/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2603/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/94/


textinput: No deactive when leaving tiv1

Already reported ? *

[X] I have searched the existing open and closed issues.

Regression?
Yes
System Info and Version
 System/Version info
Hyprland, built from branch main at commit 118be4dea048df88fd21b84580fe62950c868c8f dirty (textinput: fix tiv3 leave (7761)).
Date: Fri Sep 13 00:41:24 2024
Tag: v0.43.0-19-g118be4de, commits: 5215

flags: (if any)

Description
Same as issue #7757
How to reproduce

Open vscode with code --ozone-platform=wayland --enable-wayland-ime, and open an xwayland client
After activating fcitx5 in vscode, switch to xwayland client to use fcitx5

Crash reports, logs, images, videos
https://github.com/user-attachments/assets/7fb9332f-cff5-41fc-b84c-8b901b489526

@sungyoonc Same as issue #7753, but occurs on tiv1.

@sungyoonc Same as issue #7757, but occurs on tiv1.

Will check it out when I have time

@sungyoonc Same as issue #7757, but occurs on tiv1.

Will check it out when I have time

Thanks

Try this.
patch.txt

Try this. ~patch.txt~
edit: new patch patch.txt

No fix, still the same problem.

Even with the new patch? In my side it's fixed with the repro step that is provided.

Even with the new patch? In my side it's fixed with the repro step that is provided.

I forgot to patch it, it fixed this problem. Except that the position of imepopup is sometimes incorrect, no other problems were found.

Even with the new patch? In my side it's fixed with the repro step that is provided.

I forgot to patch it, it fixed this problem. Except that the position of imepopup is sometimes incorrect, no other problems were found.

Yeah had that issue too, but dunno how to fix that. Anyways making a MR then.

Even with the new patch? In my side it's fixed with the repro step that is provided.

I forgot to patch it, it fixed this problem. Except that the position of imepopup is sometimes incorrect, no other problems were found.

Yeah had that issue too, but dunno how to fix that. Anyways making a MR then.

The imepopup position problem seems to only exist in the wayland client. When the wayland client is opened or the window is switched, the imepopup position is not recalculated. I will open a new issue and see if you have any good ideas.


TabError: inconsistent use of tabs and spaces in indentation

Describe the bug
using docker-compose up ends in label-studio_app_1 exited with code 1
To Reproduce
Steps to reproduce the behavior:

Run 'git clone https://github.com/heartexlabs/label-studio.git'
Run 'docker-compose up'
See error

Expected behavior
Normal running Container
Screenshots
app_1    | [2021-05-18 12:10:01,133] [root::_read_py::52] [WARNING] Can't read version file: version_.py
app_1    | [2021-05-18 12:10:01,133] [root::_read_py::53] [WARNING] No module named 'version_'
app_1    | [2021-05-18 12:10:01,371] [asyncio::__init__::59] [DEBUG] Using selector: EpollSelector
app_1    | Traceback (most recent call last):
app_1    |   File "label_studio/manage.py", line 22, in <module>
app_1    |     execute_from_command_line(sys.argv)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
app_1    |     utility.execute()
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/management/__init__.py", line 395, in execute
app_1    |     self.fetch_command(subcommand).run_from_argv(self.argv)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/management/base.py", line 330, in run_from_argv
app_1    |     self.execute(*args, **cmd_options)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/management/base.py", line 371, in execute
app_1    |     output = self.handle(*args, **options)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/management/base.py", line 85, in wrapped
app_1    |     res = handle_func(*args, **kwargs)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/management/commands/migrate.py", line 75, in handle
app_1    |     self.check(databases=[database])
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/management/base.py", line 392, in check
app_1    |     all_issues = checks.run_checks(
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/checks/registry.py", line 70, in run_checks
app_1    |     new_errors = check(app_configs=app_configs, databases=databases)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/checks/urls.py", line 13, in check_url_config
app_1    |     return check_resolver(resolver)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/core/checks/urls.py", line 23, in check_resolver
app_1    |     return check_method()
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/urls/resolvers.py", line 408, in check
app_1    |     for pattern in self.url_patterns:
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/utils/functional.py", line 48, in __get__
app_1    |     res = instance.__dict__[self.name] = self.func(instance)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/urls/resolvers.py", line 589, in url_patterns
app_1    |     patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/utils/functional.py", line 48, in __get__
app_1    |     res = instance.__dict__[self.name] = self.func(instance)
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/urls/resolvers.py", line 582, in urlconf_module
app_1    |     return import_module(self.urlconf_name)
app_1    |   File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
app_1    |     return _bootstrap._gcd_import(name[level:], package, level)
app_1    |   File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
app_1    |   File "<frozen importlib._bootstrap>", line 991, in _find_and_load
app_1    |   File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
app_1    |   File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
app_1    |   File "<frozen importlib._bootstrap_external>", line 783, in exec_module
app_1    |   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
app_1    |   File "/label-studio/label_studio/core/urls.py", line 58, in <module>
app_1    |     re_path(r'^', include('data_manager.urls')),
app_1    |   File "/usr/local/lib/python3.8/dist-packages/django/urls/conf.py", line 34, in include
app_1    |     urlconf_module = import_module(urlconf_module)
app_1    |   File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
app_1    |     return _bootstrap._gcd_import(name[level:], package, level)
app_1    |   File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
app_1    |   File "<frozen importlib._bootstrap>", line 991, in _find_and_load
app_1    |   File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
app_1    |   File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
app_1    |   File "<frozen importlib._bootstrap_external>", line 783, in exec_module
app_1    |   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
app_1    |   File "/label-studio/label_studio/data_manager/urls.py", line 6, in <module>
app_1    |     from data_manager import api, views
app_1    |   File "/label-studio/label_studio/data_manager/api.py", line 212
app_1    |     return DataManagerTaskSerializer
app_1    |                                    ^
app_1    | TabError: inconsistent use of tabs and spaces in indentation
label-studio_app_1 exited with code 1

Environment (please complete the following information):

OS: Ubuntu 20.04

Additional context
Yesterday I started to inspect label-studio but run in similar error to #942.
Today I pulled again actual master and tried to rebuild. Then I got the TabError above. I tried to reformat code in api.py file but when I rebuild the container with docker-compose build --no-cache my code changes get not adopted. Do I have to change something on dockerfiles to use my local codebase?

@Schulzjo Could you take the latest commit from the master branch?

still the same error.
I did:
git pull
docker-compose build --no-cache
docker-compose up
But I am still confused about the docker behavior. My container seems not to use actual codebase.
For test reasons I added adummie_classabove the get_serializer_class in api.py which produce the error. And the error is still in line 212, but should be now in 214, or do I misunderstand something?
I am a docker newbie and can not identify why the container do not get the actual code changes.
Anny suggestions?
Thx

deleting container and image made it.
Sorry for confusion


Update UI from design QA feedback

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #1961 #1962 #1963
Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

Noticed codecov is not reporting coverage for some test classes. Will fix this separately - no test data is reported however the lines are covered.

K no worries fine to override for merge

On Jan 20, 2023, at 17:52, Elly Kitoto @.***> wrote:

Noticed codecov is not reporting coverage for some test classes. Will fix this separately - no test data is reported however the lines are covered.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

Noticed some changes breaking the app on the Pin Login screen, the keyboard remains hidden sometimes or disappears while entering the pin. Should be fixed before merging, Tagging with DNM for now.

Issue resolved. Ready for review & merge.

@ellykits this page looks very different. We are missing the log. The wording also seems off. Trying to find the mocks.

Can we update the Login page such that if the user enters the username and hits enter the cursor moves to the password, then if both the username and password are filled then we can shift the focus to the login button.

This design was updated as requested by the Design team. The Logo and App names were removed on purpose to fulfill the requirements @HenryRae can comment on this.

@dubdabasoduba Here is the link to Figma

This design was updated as requested by the Design team. The Logo and App names were removed on purpose to fulfill the requirements @HenryRae can comment on this.

Interesting. This looks very weird in terms of consistency. I might be wrong but I think all the login and pre-login pages should have the same look and feel.

Can we update the Login page such that if the user enters the username and hits enter the cursor moves to the password, then if both the username and password are filled then we can shift the focus to the login button.
Pin on the "Set Pin" Should be in caps

These comments have been addressed @dubdabasoduba Re-run the app to test.

@dubdabasoduba the logo was removed on set PIN to reduce clutter on any sort of destruction, this also allows us to have more room for design to fully show when keyboard is open on smaller screens.
cc: @rowo any thoughts?


make WINDOW_MIN_HEIGHT use existing values

Per @dcposch feedback in previous review:
https://github.com/feross/webtorrent-desktop/pull/827/files/aedbc3c32f51813b137e34b5a555a2869c4ccc8f

They straight up broke the Squash and Merge button. I can't believe it.
Tried a few times in a row with Squash and Merge

Tried once with Create a Merge Commit
Worked.
CC @feross

Dang! You can really tell that Merge without squashing is their preferred method given that they literally didn't test Squash and Merge before shipping! I bet this'll be fixed shortly


Skip /dev setup in container when it is bind mounted in

We need to set the device array to nil to skip /dev setup in runc/libcontainer.
See https://github.com/opencontainers/runc/commit/c9d58506297ed6c86c9d8a91d861e4de3772e699
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

Is there some issue you can link to?

@cpuguy83
Not sure if there is an issue created for this, but this is a long outstanding problem with sharing /dev into a container.  I believe it used to work, but got broken with runc merge.
We need this for running libvirt/qemu within containers and other use case like the one stated below.
Here is the email that spurred us to look into this.
"One of the unsolved problems I have had with the image-scanner daemon image (now the openscap-daemon image) is that it needs to access devices in /dev.  So I have been mounting /dev in, but that seems
to mess up /dev/pts|pty|ptmx where once I run the image, I can no longer spawn virtual ttys, like either xterm of ssh instances on the host.
Do you guys know how to work around this?  I've seen some references to bind mounting /dev/ptmx from the host to the image but that hasn't worked for me either.
"

I think it makes sense. But now I think maybe it's better to error-out such cases? Silently ignoring invalid configuration doesn't look like good thing.

@LK4D4 With this and the runc patch we merged, one can safely bind mount host /dev inside a container.

@mrunalp I understand, but seems like it's invalid configuration to have both bind-mounted /dev/ and devices, devices will be just discarded.

@LK4D4 This is similar to --privileged and how it override --cap-drop :)
For e.g.
[root@localhost code]# docker run --privileged --rm -it alpine grep Cap /proc/self/status
CapInh: 0000003fffffffff
CapPrm: 0000003fffffffff
CapEff: 0000003fffffffff
CapBnd: 0000003fffffffff
[root@localhost code]# docker run --privileged --cap-drop SYS_ADMIN --rm -it alpine grep Cap /proc/self/status
CapInh: 0000003fffffffff
CapPrm: 0000003fffffffff
CapEff: 0000003fffffffff
CapBnd: 0000003fffffffff

I'd like to know exactly what problem we're trying to solve here.

One of the unsolved problems I have had with the image-scanner daemon image (now the openscap-daemon image) is that it needs to access devices in /dev. So I have been mounting /dev in, but that seems

This sounds like they should be using docker run --device
Why bind all of /dev?

@mrunalp Yea, I think that's bug too :)

@phemmer I'd imagine in cases where they do want all devices, even new ones, to show up in the container.

@cpuguy83 given that extra devices only show up in /dev when using --privileged, how about mounting /dev using devpts when the container is privileged?

is there a way to have an integration test for this.

ping @mrunalp

@jfrazelle Not sure about we should do in a test for this. All this is doing is not setting up devices when /dev is mounted in so it doesn't mess things up on the host.

ok sounds fine
On Thu, Oct 8, 2015 at 2:30 PM, Mrunal Patel<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle Not sure about we should do in
a test for this. All this is doing is not setting up devices when /dev is
mounted in so it doesn't mess things up on the host.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16639#issuecomment-146691135.

Are we doing this?

I certainly hope so...

ping @crosbymichael @LK4D4 can we give this a :+1: or :-1: ?

LGTM

LGTM


Implement "Extended Master Secret" extension (RFC7626)

Description
This change implements RFC7627 "Extended Master Secret" extension with
optional enforcement by default
Reference issue
Fixes #86

Codecov Report

Merging #93 into master will decrease coverage by 0.04%.
The diff coverage is 73.72%.

@@            Coverage Diff             @@
##           master      #93      +/-   ##
==========================================
- Coverage   70.93%   70.89%   -0.05%
==========================================
  Files          51       52       +1
  Lines        2928     3030     +102
==========================================
+ Hits         2077     2148      +71
- Misses        609      627      +18
- Partials      242      255      +13

Impacted Files
Coverage Δ

cipher_suite.go
97.1% <ø> (ø)
:arrow_up:

...r_suite_tls_ecdhe_ecdsa_with_aes_128_gcm_sha256.go
77.77% <100%> (-3.48%)
:arrow_down:

...pher_suite_tls_ecdhe_ecdsa_with_aes_256_cbc_sha.go
80.95% <100%> (-3.26%)
:arrow_down:

extension.go
66.66% <100%> (+1.66%)
:arrow_up:

cipher_suite_tls_psk_with_aes_128_ccm8.go
77.77% <100%> (+2.77%)
:arrow_up:

prf.go
62.18% <100%> (+0.97%)
:arrow_up:

state.go
67.5% <100%> (+0.83%)
:arrow_up:

conn.go
78.57% <100%> (+1.04%)
:arrow_up:

server_handlers.go
82.53% <56.52%> (-1.21%)
:arrow_down:

extension_use_master_secret.go
62.5% <62.5%> (ø)

... and 7 more

Continue to review full report at Codecov.

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

@RyanGordon So not using errors.go isn't a huge deal, but is just nice to see the full range of errors and give us a little type safety.
In the future we may export these, and would be great if we can just upcase them all when we get  to that point. I think that could be a huge advantage over OpenSSL, actually let people really understand what happened and why.

Sorry I realize a lot of issues I have with code... is actually mine -_-
If we can bring down the stored state to the absolute minimum (less bugs and random things changing the world) this is an approve from me!
I will go back and send PRs your way to make things better.

@RyanGordon this LGTM!
I am approving, feel free to merge w/e you are happy with it and all the tests pass :) after it lands I am going to do do a cleanup pass (I will submit it!). When reading the code during the review I saw a lot of things that I did that make me unhappy :(


[Feature]: Decouple the benchmark script from the components of vLLM

🚀 The feature, motivation and pitch
Currently, the benchmark script of vLLM supports multiple backends, and the overall functionality is also relatively rich.
And it relies on backend_request_func and get_tokenizer. The backend_request_func is  independent and is a separate file but if we want to use get_tokenizer, we need to clone the repository or install Python package.
https://github.com/vllm-project/vllm/blob/845a3f26f9706acafe8fa45ae452846d8cc3b97f/benchmarks/benchmark_serving.py#L37-L42
https://github.com/vllm-project/vllm/blob/845a3f26f9706acafe8fa45ae452846d8cc3b97f/vllm/transformers_utils/tokenizer.py#L57
When we typically use the vLLM script to benchmark other backends, we do not want to rely on vLLM components. We don't want to clone the repository or install a Python package.
May I submit a PR to extract the function get_tokenizer into backend_request_func? Do you think this is okay or do you have any other suggestions? Thanks.
@ywang96 @simon-mo
Alternatives
No response
Additional context
No response

Hey @zhyncs! First of all thanks for the feedback on benchmark_serving.py and I'm glad you liked its functionality.
Yes I think it totally make sense to decouple serving benchmark out of vLLM since it doesn't really have any dependencies on the library itself other than reusuing get_tokenizer. Like you said, the only thing you need to do should be just copying codes for get_tokenizer into backend_request_func so we won't need to install vLLM itself at all.
Happy to review your PR!


Support for GPG Signature Verification

Given that Git and GitHub now support GPG signature verification, it would be a positive addition for the option to sign your commits show up in the commit window, instead of needing to go to the terminal to sign and commit each time.

Another trouble is Git Brackets error when trying co commit:
Error: error: cannot run gpg: No such file or directory
error: could not run gpg.
fatal: failed to write commit object

It happens when u add to git config following rules:
[commit]
    gpgsign = true
[gpg]
    program = gpg2

I have alias for gpg, but it does not help
$ which gpg
/usr/local/bin/gpg
$ readlink /usr/local/bin/gpg
/usr/local/bin/gpg2


Extension not working in the Qlik Saas

In the Qlik Saas environment, the extension is not working.
When you open the sheet where the extension is allocated, first appears an error that says "Unable to refresh. Please try again." after that, a new error appears saying this: Invalid parameters -> Error code: 8. The extension is blocked and there is no option to select any metric or dimension.

We tried with this fork https://github.com/frangar888/qs-dynamic-table  and didn’t work either but we realised that maybe it’s a problem with the Content Security Policy
Looking the .js this extension uses, we realized that there are some calls to http://code.jquery.com/  instead of using the native jquery from Qlik SaaS.
After adding a policy for allowing script from code.jquery.com , we tested and it works like a charm


UTF-8-SIG encoding

If the target file has UTF-8-SIG encoding then the script won't process it.

I've fixed the issue by removing everything before the first '@' before calling bibtexparser. This removes the BOM which caused the problem.


feat: port Algebra.Category.Group.Colimits

Still lots to do, help most welcome!

bors merge


Ignore exception cause when it's not another exception

Custom error classes might define #cause as a string or similar, which would in turn result in an internal Rollbar error.

@pedro do you have this error using third party libraries? the problem is with some custom exceptions of your own?
I remember we had a problem with another library that defined its own #cause method, but upgrading the library resolved the problem.
Can you give us those details?
Thanks

Hey! For sure, it is actually a private library, so we'll probably end up changing the method name.
But seeing that Ruby didn't give us any warning when we defined that method, and that debugging this in Rollbar took quite some time, I figured it might be worth being extra cautious here. Searching in Github this method doesn't seem all uncommon (wish there was a way to skip duplicates heh).


timeEvent uses wall clock time, which can be adjusted backwards and result in weird $duration values

When capturing short event durations at scale, it's common to see negative $duration values because the device adjusted its wall time backwards while the event was being timed. It may be better to measure durations with System.nanoTime().

hi @dougkeen , sorry for the late response. I'm afraid System.nanoTime() will have the same problem if the user adjusts the wall clock time. I'm closing this one now, please feel free to reopen if needed.


Fixes for Kotlin 1.6.0-M1

Fixing a couple of issues identified with a test build using Kotlin 1.6.0-M1

😂 I didn't realised that this was already merged

@BraisGabin thanks for your feedback, I've raised #4143 to address it.


v1.3.0 Catchable fatal error: Argument 3 passed to ZF\ContentValidation\ContentValidationListenerFactory::__invoke() must be of the type array

Getting this error after updating to v1.3.0: Catchable fatal error: Argument 3 passed to ZF\ContentValidation\ContentValidationListenerFactory::__invoke() must be of the type array, string given in /<my_path>/vendor/zfcampus/zf-content-validation/src/ContentValidationListenerFactory.php on line 21
not sure what is causing it or if I'm missing anything else after the update, any help would be great...

Hey,
I'm having the same issue than @asaxena187. After some debugging, essentially dumping, I noticed that the value passed for $options is not what the factory would expect.
The current code use this signature:
public function __invoke(ContainerInterface $container, $requestedName, array $options = null)
When i remove the array typing for $options, then check contents with var_dump($options);, here is what i get:
/path/to/ContentValidationListenerFactory.php:23:string 'ZF\ContentValidation\ContentValidationListener' (length=46)

Yet even more strange, the current code does not seem to use these $options:
https://github.com/zfcampus/zf-content-validation/blob/master/src/ContentValidationListenerFactory.php#L21-32
Hope that would help someone understand what's going on.

@asaxena187, @e7d, If you are looking for temporary solution, this PR fix this issues : #71

Is there any final solution? Merge for this? zf-content-validation is required by zf-apigility-admin an causes errors @1.3.0

v1.3.1 is still unusable due to this error.

Simply, ContentValidationListenerFactory is incompatible with Service Manager v2 in part of createFromFactory method (is_callable check & putting $requestedName to options in old way) & tested only with v3.

Should be fixed with #76

The v1.3.1 fix does not correct this, we need #76 merged please!
Ping @Ocramius @akrabat

Closed with 1.3.2 release.


factor out IS_SLASH, perdir fix

in per-dir, the filename will be internally redirected, so / is OK too.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1918651 13f79535-47bb-0310-9956-ffa450edef68 (cherry picked from commit f2db4112861b10192de7a1a42321b42cb8a2ba55)

Backported in 4326d6b9041a3bcb9b529f9163d0761c2d760700

@covener : This one can be closed as it was merged.

Do you not all have power to close these yourselves?

Unfortunately there was no close button for me. No idea why.


Auth header not being sent if tokenAttributeName is changed & Rails is expecting 'token', not 'user_token'

I ran into a couple of issues using ember-simple-auth and ember-simple-auth-devise (both 0.7.2) with Rails 4.2 and ember-rails.
With the default configuration, ember-simple-auth-devise expects a user_token and user_email from the server in order to set up a session, and then sends both in the Authorization header on subsequent requests e.g. "Token user_token=\"p-bbux4Br1ULzvzjTGGv\"<EMAIL_ADDRESS>The authenticate_with_http_token method within Rails, however, uses "token=" as a key to find the token from the Authorization header. This means that the token that it finds ends up parsed like: user_token="p-bbux4Br1ULzvzjTGGv instead of just p-bbux4Br1ULzvzjTGGv, causing the authentication filter to fail, at least as it is written in the ember-simple-auth-devise README. (issue 1)
To attempt to fix the problem, I set the tokenAttributeName setting within ember-simple-auth-devise to token. Since this setting also changes what ember-simple-auth expects back from the server, the authorize function within ember-simple-auth-devise gets token, instead of the user_token (which the server returns, at least as it is written in the README). Thus, the Authorization header on the outgoing API request is not set, causing the token authentication to fail. (issue 2)
Double whammy.
I was able to finally solve the issue by changing user_token to token in the response from the create action in my session controller.
The Rails function should probably be configurable to properly parse the Authorization header, but I also wonder if in the mean time we should set the default tokenNameAttribute to be token instead of user_token since that's what Rails is expecting, and devise is a Ruby plugin?

You're right, the token should always be sent as token. Pull request would be cool.

fixed in #394

How can I get latest changes from master for my Rails app?
Now I attach library via Rails Assets
# Gemfile
source 'https://rails-assets.org'
gem 'rails-assets-ember-simple-auth'

This hasn't been released yet - next version will probably ship later this week. Using master directly doesn't work really - you'll have to build your own, see the README for reference.

kudos @matthooks. Changing both the server json response and the tokenAttributeName to 'token' worked like a charm.

I installed the last version of ember simple auth devise but it seems like the request does not include the token in the header.  My configuration is:
  ENV['simple-auth-devise'] = {
       tokenAttributeName: 'token',
       identificationAttributeName: 'email',
	serverTokenEndpoint: ENV.host + '/users/sign_in',
	authorizer: 'devise'
  };

  ENV['simple-auth'] = {
	// crossOriginWhitelist: ['*'],
	authorizer: 'simple-auth-authorizer:devise'
  };
```

when I uncomment crossOriginWhitelist: ['*'] the ember app sends OPTIONS request instead of GET. any idea how I would what's wrong?

I'm in the same boat---using the -token authorizer. I can't seem to get the Authorization header to work, even whitelisting ['*'].

I had a situation to attach the token with the header manually . (to upload images via ember-uploader to carrier-wave in rails api).
I done it this way
// in controller
export default Ember.Controller.extend({
  session: Ember.inject.service('session'),
  var authenticated = controller.get('session.data.authenticated');
   ajaxSettings: function() {
         var settings = this._super.apply(this, arguments);
         settings.headers = {
           'Authorization':'Token token="'+ authenticated.token +'", email="'+ authenticated.email+'"'
           };
         return settings;
       }

Is it okay to get the token with controller.get('session.data.authenticated) ?
i am afraid this is a reliable method or not.
If there is any better method. please share me.
Thanks

You should always use the session service's authorize method to generate authorization data.

@marcoow ,
Thanks for a quick reply.
I had set it in my devise authenticator as you said
import DeviseAuthorizer from 'ember-simple-auth/authorizers/devise';
export default DeviseAuthorizer.extend({
  actions: {
    authorize: function(){
      this.get('session').authorize('authorizer:devise', (headerName, headerValue) => {
        XHR.setRequestHeader(headerName, headerValue);
        // jqXHR.setRequestHeader(headerName, headerValue); I tried jqXHR too
      });
    }
  }
});

but it's not sending token with header , my ember-uploader request is redirected like this in console
XMLHttpRequest cannot load http://localhost:3000/siteimages/28. The request was redirected to 'http://localhost:3000/users/sign_in', which is disallowed for cross-origin requests that require preflight.```

 my previous method worked well  .but this one not .Is it any problem with the devise authenticator implementation?

Thanks

Any word on this? I'm encountering the same issue. I've whitelisted both '*' and the auth0 domain, and I'm still getting a 401 because the Authorization header isn't being added to the request. Any help is much appreciated.

In order to have a request authorized you can either use the DataAdapterMixin if it is an Ember Data request or use the session service's authorize method directly if it is e.g. a plain jQuery request:
this.get('session').authorize('authorizer:devise', (headerName, headerValue) => {
  const headers = {};
  headers[headerName] = headerValue;
  Ember.$.ajax({
    url: '…',
    headers
  });
});

Auto-authorization of all requests was removed in ESA 1.0.

That worked. Thanks for your help, @marcoow.

HI,
I am having the same problem with sending the header. I understood from doing gizillion searches, that I need to include the header in the authorizers. But @marcoow 's comment seems to indicate that the header needs to be attached to the actual request? Can somebody please clarify?
To clarify: I have a service to get the information of the current user from the back-end and add it to the session. I am having a lot of problems with what sounds a very simple task.

@bmatmentel I applied to his change to my application adapter:
import DS from 'ember-data';
import DataAdapterMixin from 'ember-simple-auth/mixins/data-adapter-mixin';

export default DS.JSONAPIAdapter.extend(DataAdapterMixin, {
  namespace: 'api',
  host: 'http://myapi.herokuapp.com',
  authorizer: 'simple-auth-authorizer:jwt',
  headers: {
    'Content-type': 'application/json'
  }
});

authorizer added the Authorization header and headers hash added the Content-Type header for me.

Thanks @benbabics!
But what worked for me at the end, I found it here: https://github.com/simplabs/ember-simple-auth/issues/798, in a comment by @gte451f,
I was to able to include the code in the authorizer. What happens is that the signature from  authorize changed from  authorize: function (jqXHR, requestOptions) to  authorize(sessionData, block).

@bmatmentel: when reading stuff about authorization on stackoverflow or on blogs make sure the content is for ESA 1.0 - the 1.0 release changed authorization quire significantly.

@marcoow Thanks for the comment, But I am new to this. Can you point to more info on ESA 1.0? Also, how do you make sure contents in blogs refer to it when it is not explicitly specified?

All info on this repo as well as on the ESA website relates to the latest version of course. If you're upgrading from a previous version you can follow this guide on our blog: http://log.simplabs.com/post/131698328145/updating-to-ember-simple-auth-10.
If blogs don't specify the version of ESA they refer to you have no way of knowing really - just be aware that quite some things changed with ESA 1.0


Publish caddy-cache

After a long time I finally think caddy-cache is ready to be published. It does not have every feature I want but I think it handles the basic thinks it needs to support:

it handles Vary header
it handles correct usage of cache headers with the help of https://github.com/pquerna/cachecontrol
it handles locking and concurrency (if two request gets the server at the same time, there will be only one fetch to upstream and both original requests will get the response at the same time without having to wait until the upstream request ends)

What do you think?
1. What does this change do, exactly?
Adds a middleware for http caching
2. Please link to the relevant issues.
https://github.com/mholt/caddy/issues/10
3. Which documentation changes (if any) need to be made because of this PR?
It needs a new section for the new cache directive
4. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I am willing to help maintain this change if there are issues with it later

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@nicolasazrak thanks for the PR and the great looking plugin.
Does the cache directive need to be the first plugin?  Perhaps if it does you could provide a little explanation, and if not perhaps move it further down the list close to realip and git.

@tobya I think I am a little confused about how root works. I expected root to be one of the last ones, so other plugins like gzip had the chance to intercept the content root writes and do something, but I moved cache before after git and it seems to be working.

Waiting for @elcore to approve and then will merge. :+1: Thank you, Nicolas! You can publish your plugin immediately after the next release of Caddy. If it needs to be re-ordered in this list, you can do so most efficiently before that release. :wink:

@mholt thanks I'll be waiting for the next release !

@nicolasazrak The new version is out, you may now publish this plugin!

@mholt it's done ! 🎉

@nicolasazrak If you'd ever be interested in helping to build the v2 equivalent of a caching middleware, we have a repo for it now: https://github.com/caddyserver/cache-handler - just FYI, you're not obligated or anything :)


android video autoplay even if paused={true}

I followed PR #625 but video continues to autoplay when rendered. I manually added "mActiveStatePauseStatus = paused;" to my ReactVideoView.java file.  Here is what I have (RN - 0.44; react-native-video - 2.0.0) -
rate={0} //paused
paused={true}
volume={1}
muted={false}
playInBackground={false} // Audio continues to play when app entering background.
playWhenInactive={false}
ignoreSilentSwitch={"obey"}
resizeMode="cover"
onError={e => console.log(e)}
onLoad={load => console.log(load)}
repeat={false}

Hey maybe this helps I have it like this:
style={styles.backgroundVideo}                 ref={this.videoReference.bind(this)}                 onLoad={this.videoOnLoad.bind(this)}                 onError={this.videoError.bind(this)}                 resizeMode="cover" paused={this.state.paused}                 rate={1} volume={this.state.videoVolume} muted={false} repeat={false} key="video2"
and I'm pausing the video like this
AppState.addEventListener('change', this._handleAppStateChange);
_handleAppStateChange = (nextAppState) =>     {         this.playVideoFromStart();         this.pauseVideo();         this.setState({appState: nextAppState});     }
where pause video just setState({paused:true})
note: also I had to add the fix from the PR #625

Can you share more of this code ^? I am unable by any means to get android to stop playing.  I'm more asking, what is this.playVideoFromStart() and this.pauseVideo() methods?

@deehuey sure!
`
constructor()
{
super();
this.player;
this.state = {
paused: true,
videoError: false,
appState: AppState.currentState,
videoVolume: 1.0
};
}
componentDidMount()
{
AppState.addEventListener('change', this._handleAppStateChange);
}
_handleAppStateChange = (nextAppState) =>
{
if(!this.state.videoError)
{
this.playVideoFromStart();
this.pauseVideo();
}
this.setState({appState: nextAppState});
}
playVideoFromStart()
{
if(this.player != null) this.player.seek(0);
}
pauseVideo()
{
this.setState({paused: true});
}
renderVideoSlide()
{
return <TouchableOpacity style={styles.videoView}
onPress={this.onPlayOrPauseVideo.bind(this, this.state.paused)}>
          {!this.state.videoError && <Video source={require('../../assets/videos/home_video.mp4')}
            style={styles.backgroundVideo}
            ref={this.videoReference.bind(this)}
            onLoad={this.videoOnLoad.bind(this)}
            onError={this.videoError.bind(this)}
            resizeMode="cover" paused={this.state.paused}
            rate={1} volume={this.state.videoVolume} muted={false} repeat={false} key="video2" />}

          {this.state.paused && !this.state.videoError &&
              <Image style={styles.videoIcon}
                     source={require('../../assets/icons/btn-play/btn-play.png')}/>}
        </TouchableOpacity>;
}

`

the PR #625

Bit of a hack, but if you pass the endWithThumbnail={true} prop then the repeat bug does not occur on iOS

I'm also facing this problem, PR #625 is not working either.
What I'm trying to accomplish is to start/stop the video depending it's being shown by the scrollview or not. I'm passing a prop "isViewable" to the component and nothing happen. My idea is to give the autoplay to start fetching the video when the component is loaded but pause it until is on screen.
Is there any other way to do it? Will this work as intended?
Thanks!

I cleaned up the pause code for both MediaPlayer & ExoPlayer and am pretty sure this is resolved. Reopen if not.


[DataFactory]SDK code change for some new features

Support HDFS for delete activity and deleteFilesAfterCompletion feature in copy activity: https://github.com/Azure/azure-rest-api-specs/pull/10394

Added support for managed Virtual Network and managed private endpoint CRUD APIs: https://github.com/Azure/azure-rest-api-specs/pull/10191

Added Support for Query EC List API: https://github.com/Azure/azure-rest-api-specs/pull/10316

Added more options on XML and CosmosDbSqlApi copy source: https://github.com/Azure/azure-rest-api-specs/pull/10271

Fix bug: Added AzureFileStorageWriteSettings: https://github.com/Azure/azure-rest-api-specs/pull/10381

@allenjzhang  Could you please help review it?


added namespaceIDPrefix option

option to fix error #292

Coverage increased (+0.02%) to 78.906% when pulling d30f2ea7acd665f31a5f5c2208964ab60831e1b4 on mikemellor11:master into<PHONE_NUMBER>dfcf2cd9ed2bba500cb8ee31c00b9c on jkphl:master.


Add functionality to allow gochan-migrate to migrate deprecated gochan installs

Closing this issue since gochan-migrate's development is suspended.


backport changes made to cluster reboot playbook

LGTM

We need the check_compute_services.yml also

thanks @twaldrop 👍

retest


[WIP] Support None type

#328

Seems there is problem representing None in initializers of nodes.
TensorProto can only handle tensor type(of course), though there is a candidate type to use like None:

STRING type
UNDEFINED type

Though either of the type may cause some confusion or unexpected errors....

Seems difficult for now so doing this later


Add specification on top-nav

This PR covers issue #18
Moved specification on top-nav following a recommendation on the TUF documentation analysis
Please review @chalin @lukpueh

This is ready for another review @chalin

The text reads like a general TUF project overview, and only vaguely prepares the reader for the specification.
I suggest to remove it and just leave the index. Or add a small paragraph about what the user will find in the spec. Maybe you can take inspiration from this talk. More specifically, about how the spec defines a detailed client updater workflow and otherwise TUF repo primitives (roles, metadata, delegations), which can be used as building blocks.

@lukpueh Okay. I'll try. Thanks

@lukpueh I have edited the section and added in the video you shared for reference. Let me know what you think.


Deprecated methods on iOS 9

Some methods and classes are deprecated on iOS 9: MPMoviePlayerViewController, NSURLConnection and some encryption methods.

This has already been taken care of in c0df2c86ed0bbd9cd187b633f8f4246c78958e1d and b35f73ba55485ffe012cecaea2afa35d07b573ca. I hope to release version 2.4.0 in a few weeks.


Fix mssql-plugin occur ClassCastException when call the method of return generate key

Fix mssql-plugin occur ClassCastException when call the method of return generate key

[ ] Add a unit test to verify that the fix works.
[x] Explain briefly why the bug exists and how to fix it.

fix https://github.com/apache/skywalking/issues/6080,
Previously, I wrapped the return value of the prepareStatement method of SWPreparedStatement type, but in the method com.microsoft.sqlserver.jdbc.SQLServerConnection#prepareStatement(java.lang.String, int, com.microsoft.sqlserver.jdbc.SQLServerStatementColumnEncryptionSetting) , Type conversion, a java.lang.ClassCastException: org.apache.skywalking.apm.plugin.jdbc.trace.SWPreparedStatement cannot be cast to com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement, fix method: using the interceptor to replace wrapper.

You need to explain what you are doing and why you are doing in the PR, please fix this.
From my understanding, your chance is using the interceptor to replace wrapper, if so, why these interceptors are not in the jdbc-common, instead, you created msql-common?

You need to explain what you are doing and why you are doing in the PR, please fix this.
From my understanding, your chance is using the interceptor to replace wrapper, if so, why these interceptors are not in the jdbc-common, instead, you created msql-common?

You need to explain what you are doing and why you are doing in the PR, please fix this.
From my understanding, your chance is using the interceptor to replace wrapper, if so, why these interceptors are not in the jdbc-common, instead, you created msql-common?

    public PreparedStatement prepareStatement(String sql,
            int flag,
            SQLServerStatementColumnEncryptionSetting stmtColEncSetting) throws SQLServerException {
        loggerExternal.entering(getClassNameLogging(), "prepareStatement", new Object[] {sql, new Integer(flag), stmtColEncSetting});
        checkClosed();
        SQLServerPreparedStatement ps = (SQLServerPreparedStatement) prepareStatement(sql, ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY,
                stmtColEncSetting);
        ps.bRequestedGeneratedKeys = (flag == Statement.RETURN_GENERATED_KEYS);
        loggerExternal.exiting(getClassNameLogging(), "prepareStatement", ps);
        return ps;
    }

For example, in this method com.microsoft.sqlserver.jdbc.SQLServerConnection#prepareStatement(java.lang.String, int, com.microsoft.sqlserver.jdbc.SQLServerStatementColumnEncryptionSetting), the return value of the prepareStatement method is forcibly converted. Because mssql-jtds and mssql-jdbc have certain similarities, a new mssql-commons module has been added.

You need to explain what you are doing and why you are doing in the PR, please fix this.
From my understanding, your chance is using the interceptor to replace wrapper, if so, why these interceptors are not in the jdbc-common, instead, you created msql-common?

    public PreparedStatement prepareStatement(String sql,
            int flag,
            SQLServerStatementColumnEncryptionSetting stmtColEncSetting) throws SQLServerException {
        loggerExternal.entering(getClassNameLogging(), "prepareStatement", new Object[] {sql, new Integer(flag), stmtColEncSetting});
        checkClosed();
        SQLServerPreparedStatement ps = (SQLServerPreparedStatement) prepareStatement(sql, ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY,
                stmtColEncSetting);
        ps.bRequestedGeneratedKeys = (flag == Statement.RETURN_GENERATED_KEYS);
        loggerExternal.exiting(getClassNameLogging(), "prepareStatement", ps);
        return ps;
    }

For example, in this method com.microsoft.sqlserver.jdbc.SQLServerConnection#prepareStatement(java.lang.String, int, com.microsoft.sqlserver.jdbc.SQLServerStatementColumnEncryptionSetting), the return value of the prepareStatement method is forcibly converted. Because mssql-jtds and mssql-jdbc have certain similarities, a new mssql-commons module has been added.

You forget to update the changelog. Please fix.

You forget to update the changelog. Please fix.


Understand how to build a new executable within CLAM

Understand better the structure of CLAM and how to build in our new program without interfering with other modules and functionality.

Met with Najib in 2024-10-19.
We should build SHELL as a module within crates/abd-clam/src
The results binary will go in crates/results


.NET 5 NSwagExe MSBuild Property

We're working on preparing our codebase for .NET 5 release in November. Is there a planned naming convention for NSwagExe MSBuild properties following .NET 5 removing "Core"/"Framework"? Maybe NSwagExe_Net5?

Didnt think about this yet, but NSwagExe_Net5 make sense.

Now that that the release candidate is out, is there any news on support for .NET 5?

Can't you reference and use the current version of NSwag.AspNetCore?

I'm using NSwag.MSBuild to generate a client for my API and it's giving me
System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

when i try and build.

Can't you reference and use the current version of NSwag.AspNetCore?

OpenAPI generation works just fine in .NET 5 build, VS 2019 preview using NSwagExe_Core31. Using just-released VS preview and nightly build of dotnet SDK, RC2 preview.

Is that different from RC1? What command are you using to make that work?

I would expect that NSwag.AspNetCore still works as it “hosted” by a .net 5 process, however NSwag.MSBuild might fail because it’s a .net core 3.1 process loading .net 5 dlls/projects

It's different from RC1 in the sense that it's a RC2 nightly build. I would not expect any of those differences to be relevant to NSwag behavior.
<Target Name="GenerateSwaggerDoc" AfterTargets="Build" Condition=" '$(RuntimeIdentifier)' != 'linux-arm64' ">
  <Copy SourceFiles="@(Reference)" DestinationFolder="$(OutDir)References" />
  <Exec Command="$(NSwagExe_Core31) run nswag.json /variables:Configuration=$(Configuration)" />
</Target>

Yeah -- that is an interesting point. Depending on the assemblies being loaded and their target arch you could run into something funny.

I would expect that NSwag.AspNetCore still works as it is “hosted” by a .net 5 process

Of course only if they didnt break an api which nswag relies on (eg api explorer). Maybe there is also more metadata we can/should support. But for that we’d need to check the changes

not sure when we can expect the new NSwagExe_Net5, any update?

Any idea when the .NET 5 support will be given? Can we support it?... Would like to create a PR for that issue

@RicoSuter Please have a look at the PR. This is imho important as many projects using NSwag want to make the change to .NET 5. Thank you in advance.

Updating to the newest version of Visual Studio breaks existing projects that use $(NSwagExe_Core31):
.csproj
  <Target Name="NSwag" BeforeTargets="PrepareForBuild" Condition="'$(GenerateCode)'=='True' And '$(Configuration)'!='Release' ">
    <Exec Command="$(NSwagExe_Core31) run nswag.json /variables:Configuration=$(Configuration)" />
  </Target>

build output
error MSB3073: The command " run nswag.json /variables:Configuration=Debug" exited with code 9009

Why is that? Because its built by net 50 or because you just installed net 50?

It seems the newest version of Visual Studio (16.8.0) defaults to using the .NET 5.0 SDK even if you are using a netcoreapp3.1 project.

@phil-harmoniq VS default behavior is to use the latest SDK available on the system & VS 16.8 to the best of my knowledge cannot be installed without .NET 5 so makes sense. You can override the SDK used by VS — don’t recall off hand how, but should be easily googled.

NSwag v13.9.0 released with .NET 5.0 support - please test and report any problems.

Seems to working fine, managed to build in VS 16.8.1, console using dotnet build -f net5.0 and also in docker image mcr.microsoft.com/dotnet/sdk:5.0
Pasting this for reference, the dll name was giving me a hard time NSwagExe_Net50 vs NSwagExe_Net5 mentioned above.
<Target Name="NSwag" AfterTargets="Build">
    <Copy SourceFiles="@(Reference)" DestinationFolder="$(OutDir)References" />
    <Exec Command="$(NSwagExe_Net50) run nswag.json /variables:Configuration=$(Configuration) /runtime:Net50" />
    <RemoveDir Directories="$(OutDir)References" />
  </Target>

Thanks guys for a quick upgrade.

Same problem as @phil-harmoniq  here:
VS 2019 16.8.3
TargetFramework: netcoreapp3.1

It seems $(NSwagExe_Core31) is empty.
I've tried the global.json workaround (in the project's root dir) but that did not work for me.

Command line works:

Any ideas @RicoSuter ?

Same problem as @phil-harmoniq  here:
VS 2019 16.8.3
TargetFramework: netcoreapp3.1

It seems $(NSwagExe_Core31) is empty.
I've tried the global.json workaround (in the project's root dir) but that did not work for me.

Command line works:

Any ideas @RicoSuter ?

@Kobus-Smit Did you install the NSwag.MSBuild nuget package?

@Kobus-Smit Did you install the NSwag.MSBuild nuget package?

Yes I did.
On Mon, 4 Jan 2021, 10:47 pm Jérémy VIGNELLES<EMAIL_ADDRESS>wrote:

@Kobus-Smit https://github.com/Kobus-Smit Did you install the
NSwag.MSBuild nuget package?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RicoSuter/NSwag/issues/3026#issuecomment-753930505,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACV566CSUMN4HVKN5HYQT63SYGTFNANCNFSM4QMPN3VA
.

Yes I did.
On Mon, 4 Jan 2021, 10:47 pm Jérémy VIGNELLES<EMAIL_ADDRESS>wrote:

@Kobus-Smit https://github.com/Kobus-Smit Did you install the
NSwag.MSBuild nuget package?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RicoSuter/NSwag/issues/3026#issuecomment-753930505,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACV566CSUMN4HVKN5HYQT63SYGTFNANCNFSM4QMPN3VA
.

Then please open a new issue with your whole csproj. This issue is about .net 5

Then please open a new issue with your whole csproj. This issue is about .net 5

Is it not related to Phil's:
Updating to the newest version of Visual Studio breaks existing projects
that use $(NSwagExe_Core31) even if you never changed your target framework
It seems the newest version of Visual Studio (16.8.0) includes .NET 5.0 SDK
and defaults to it even if you are using a netcoreapp3.1 project. I did not
install .NET 5 manually. However, I noticed if I try to build the project
using using the CLI (dotnet build) it seems to work fine.
On Mon, 4 Jan 2021, 11:00 pm Jérémy VIGNELLES<EMAIL_ADDRESS>wrote:

Then please open a new issue with your whole csproj. This issue is about
.net 5
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RicoSuter/NSwag/issues/3026#issuecomment-753935700,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACV566A2EKTKOKYG7OO7JX3SYGUUZANCNFSM4QMPN3VA
.

Is it not related to Phil's:
Updating to the newest version of Visual Studio breaks existing projects
that use $(NSwagExe_Core31) even if you never changed your target framework
It seems the newest version of Visual Studio (16.8.0) includes .NET 5.0 SDK
and defaults to it even if you are using a netcoreapp3.1 project. I did not
install .NET 5 manually. However, I noticed if I try to build the project
using using the CLI (dotnet build) it seems to work fine.
On Mon, 4 Jan 2021, 11:00 pm Jérémy VIGNELLES<EMAIL_ADDRESS>wrote:

Then please open a new issue with your whole csproj. This issue is about
.net 5
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RicoSuter/NSwag/issues/3026#issuecomment-753935700,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACV566A2EKTKOKYG7OO7JX3SYGUUZANCNFSM4QMPN3VA
.

Did you try $(NSwagExe_Net50) with your .net core 3.1 proj?

My issue was resolved in https://github.com/RicoSuter/NSwag/issues/3240. Somehow had an outdated NSwag.MSBuild PackageReference.

Ok, thanks for the heads up. @thenadz can we close the issue?

@RicoSuter Yep -- looks good to me! Thanks!


Using ADIOS2 with MPI and system-provided libraries

Hi, I'm trying to use ADIOS2 with MPI using the vendor-provided MPI library cray-mpich.
While MPI.jl works fine, throwing ADIOS2 into the mix results in LoadErrors:
rkube@nid005838:~/source/julia_perlmutter> srun -n 1 ~/software/julia-1.8.0/bin/julia --project=. src/test_mpi_adios.jl
ERROR: LoadError: InitError: MPI library has changed, please re-run `Pkg.build("MPI")`.

Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:35
 [2] compilecache(pkg::Base.PkgId, path::String, internal_stderr::IO, internal_stdout::IO, keep_loaded_modules::Bool)
   @ Base ./loading.jl:1705
 [3] compilecache
   @ ./loading.jl:1649 [inlined]
 [4] _require(pkg::Base.PkgId)
   @ Base ./loading.jl:1337
 [5] _require_prelocked(uuidkey::Base.PkgId)
   @ Base ./loading.jl:1200
 [6] macro expansion
   @ ./loading.jl:1180 [inlined]
 [7] macro expansion
   @ ./lock.jl:223 [inlined]
 [8] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:1144
in expression starting at /global/u2/r/rkube/source/julia_perlmutter/src/test_mpi_adios.jl:6
srun: error: nid005838: task 0: Exited with exit code 1
srun: launch/slurm: _step_signal: Terminating StepId=3062902.4
rkube@nid005838:~/source/julia_perlmutter> cat src/test_mpi_adios.jl
using MPI
MPI.Init()

using Random

using ADIOS2

comm = MPI.COMM_WORLD
rkube@nid005838:~/source/julia_perlmutter>

This is the Project.toml:
[deps]
ADIOS2 = "e0ce9d3b-0dbd-416f-8264-ccca772f60ec"
MPI = "da04e1cc-30fd-572f-bb4f-1f8673147195"

To install MPI.jl with the system-provided libraries I followed the instructions provided here: https://juliaparallel.org/MPI.jl/stable/configuration/#Using-a-system-provided-MPI
Is there an easy way to make this setup work?

@rkube The problem is that ADIOS2.jl calls into the actual ADIOS2 library libadios2.so, which is written in C++, and which is directly linked against MPI. This library is precompiled and downloaded by the Julia package manager, and is not compatible with any system-provided MPI.
The solution that I prefer is to use MPItrampoline. This is an MPI wrapper around any MPI implementation that provides a system-independent ABI. It's designed to handle exactly this case.
To use MPItrampoline, you would:

Build MPIwrapper with cray-mpich. (That is straightforward if you are familiar with invoking cmake.)
Configure MPI.jl to use MPItrampoline (MPIPreferences.use_jll_binary("MPItrampoline_jll"))
Restart Julia, re-instantiate packages (as described in the MPI.jl) documentation when changing MPIPreferences)
Set the environment variable MPITRAMPOLINE_LIB to point to the MPIWrapper *.so library (which you built and maybe installed above)

Under the hood, this still uses cray-mpich.
I've been using this approach for a while, and am now asking others to do so as well because I think this is the simplest way to address this problem. Please let me know if something doesn't work, or if there's another problem.
The "standard" way of addressing this would be to build the ADIOS2 C++ library yourself, against cray-mpich, and then make ADIOS2.jl use that library.

Thanks for the detailed instructions, this approach works fine.
The cluster I'm deploying on has MPI disabled on the login nodes. From time to time I use ADIOS2 on the login nodes for data processing purposes without MPI.
When I load ADIOS2 precompiled with MPI on the compute nodes it works fine.
When I load ADIOS2 on the login nodes, precompilation fails:
julia> using ADIOS2
[ Info: Precompiling ADIOS2 [e0ce9d3b-0dbd-416f-8264-ccca772f60ec]
ERROR: LoadError: InitError: could not load library "/global/homes/r/rkube/.julia/artifacts/a3334801c3f22e264487a1b1c2afef643e4188df/lib/libadios2_c_mpi.so"
/global/common/software/spackecp/cori/e4s-22.02/software/cray-cnl7-haswell//intel-<IP_ADDRESS>/adios2-2.7.1-eensbbtvrnepy4ch6q3onnf5kztugyyz/lib64/libadios2_core_mpi.so.2: undefined symbol: _ZN6adios24core6Engine5DoPutERNS0_8VariableIaEERNS0_4SpanIaEEmRKa
Stacktrace:

Do you know if there is a way to have two versions installed, one mpi-enabled and one mpi-disabled?

Glad to hear!

I am trying to build ADIOS2.jl to use my own adios2 library. What commnad should I use? I am very new to Julia. Thanks.

@jychoi-hpc Using your own ADIOS2 library is a difficult task. The problem is that you need to ensure binary compatibility between the library you built and the glue code that ADIOS2.jl is using. I do not have ready-made instructions for this. Julia can automate many complex steps when using its own ADIOS2 library. You would have to change the part of ADIOS2.jl that loads the external ADIOS2 library. Since Unix library linking does not check types, any error you make would at best lead to segfaults.
If possible, I would recommend using the ADIOS library that comes with Julia. Why are you using your own library?

I see. I understand the complexity and difficulty.
Basically, I am trying to use on Perlmutter, Cori (NERSC), or Summit (ORNL). On those machines, I found using their system library or something I compiled specificifally on that machine worked better than using pre-built binary. It looks like HDF5's Julia package supports using system binary: https://juliaio.github.io/HDF5.jl/stable/#Using-custom-or-system-provided-HDF5-binaries
Another reason would be as follows. I found the pre-built binary is not sufficient. ADIOS has so many features and options to turn on/off. I want to use my specific Adios build with Julia. Since I am new to Julia, I might miss something. Please correct me or give any information.

I myself have a C/Fortran/C++ background. When coming to Julia, I wanted to have the freedom to link against any package that I built myself, as this is common in these languages, especially on HPC systems. However, I found that not doing so has many advantages, and I have not found it necessary to install package on my own (with the exception of MPI, which is a different story).
It is currently, unfortunately, not easy to use ADIOS2.jl with a custom adios2 library. Managing finding and loading such a package is handled by the Julia package ADIOS2_jll.jl, which is used by ADIOS2.jl. ADIOS2_jll.jl is generated automatically when the adios2 library is built by BinaryBuilder.
I assume the best way to support loading your own library is to remove the dependency on ADIOS2_jll.jl, and use libdl.jl to load the adios2 library yourself. The Julia documentation describes how to do that. If you have a concrete problem with the default adios2 library then I'd be happy to look into that, either correcting that problem in ADIOS2_jll.jl or adding a mechanism to load a self-built library. Otherwise my strong suggestion is to use ADIOS2.jl as is, even though that practice is different from how packages in C/Fortran/C++ would be managed.

@eschnett thanks for the pointers. Question, as I don't know much about Julia's packaging, can both approaches coexist in your current implementation? Meaning using the environment variable such as JULIA_ADIOS2_PATH pointing at a ADIOS2 native installation and then pkg> build
, similar to HDF5. If so, this would be done at the ADIOS2_jll level or the ADIOS2.jl level?  Thanks for the effort of making this available.

ADIOS2.jl contains only the line using ADIOS2_jll. I assume this line could in principle be inside an if statement that checks an environment variable, and does something else (load an external library via libdl and set up a few things) otherwise. Of course, this would break precompiling. I guess the respective logic could be moved into an __init__ function.
Ultimately, ADIOS2_jll.jl sets a global constant libadios2_c that is used by the ccalls in ADIOS2.jl.
I don't recall how to move this logic to build time, but I'm sure this can be done as well.
Is there a particular problem you're trying to address? Is the Julia-provided adios2 library insufficient or configured wrong?

Thanks @eschnett , it's mostly what @jychoi-hpc mentioned. ADIOS2 is really a framework with multiple compile-time options. Linking to a spack-installed version module or more experimental/development features on HPC clusters with their own vendor MPI, would be the end goal. Nothing wrong with the current ADIOS2.jl, actually what you did is the sane choice.

If using a vendor MPI is the issue, then I recommend MPItrampoline as remedy. It's straightforward to configure Julia's MPI.jl to use it.

@eschnett, maybe it would be easy enough to implement something inspired by our workaround using Overrides.toml:

We created a file Overrides.toml in the artifacts folder of the julia depot used and it contained this (the first is the hash of the ADIOS2 artifact):
6b9210b346f45445a1acf311f166f5ed0655a0b0 = "path-to-our-adios2-module-installation"
See: https://pkgdocs.julialang.org/v1/artifacts/#Overriding-artifact-locations-1
In addition, we had to move in our module the content of lib64 to lib to match the directory structure of ADIOS2_jll.

@jychoi-hpc : if none of the other solutions works for you, the here described should work. It worked for us on Piz Daint with Cray-MPICH


Typo. should tenantID ?

This PR for visibility, I found this typo when looking through the code for some issues I have been seeing.
Not sure what the impact is.

Thanks for opening the PR 😄 this should be fine as it's simply a variable name in a function type signature, however it's definitely something to fix-up!
/ok-to-test
/override dco
/approve

/release-note-none

/lgtm


Is heron only support centos and Ubuntu?

Other linux platform is not be supported?

@yunfanfighting - Hi, currently Heron supports darwin, centos and ubuntu.

@mycFelix , Why? Major component is written in java. It should can run in any platform. Which component can't be compiled in other platform.

@yunfanfighting - The Heron code organization guide is following http://twitter.github.io/heron/docs/contributors/codebase/ . The Contributing New Environments guide is following http://twitter.github.io/heron/docs/developers/compiling/docker/

@yunfanfighting - Here is Compiling Heron Guide telling us how to compile Heron and which OS Heron supports currently. If you want to know something about the code organization, you could click Heron code organization . And There is Contributing New Environments telling us how to compile Heron with other OS.

@yunfanfighting - Heron has C++ and Java code. Due to C++, the code has to be explicitly ported to another platform before you can run on it.

Can I run all of heron components in docker? So I can run the heron in other linux platform.

@yunfan123 - yes, you can. We already support it. Check the documentation at
https://github.com/twitter/heron/tree/master/docker

I can't access http://maven.twttr.com.
Is this a internal maven service? Or this service is not so stable?
I can access twitter.com normally.


feat: Adding checksum verification to install script

Enables checksum verification by default, which is useful for verifying integrity of the download.

For context, @ohmer , I'm the lead maintainer of Terragrunt, and would appreciate it if Terragrunt installs did this by default when users used asdf/mise. It's a nice extra check that is inconvenient to do manually.

Did some tests with asdf. LGTM!


Remove Function CR refs

The Function CRD and Repo content tyoe has been removed from Porch. This cleans up any remaining refs.

/restest

/approve looks good to me apart from the weird test behavior.

We can ignore the reviewdog job result so far. It is fixed in https://github.com/nephio-project/docs/pull/176 what requires the merger of https://github.com/nephio-project/docs/pull/179

/lgtm

/retest

/retest

/approve
/lgtm


use this library in regular ReactJS app?

Can I use this library in regular React app (not react-native) ? to connect it with Meteor backend.

I dont think so... For that use - surprise - Meteor ;-)

I think you can modify this project and replace the part related to react-native with react. Actually, I had done this without CollectionFS feature since I need to separate backend and frontend in my project, and it worked fine. (https://github.com/pomelyu/react-native-meteor)


How to connect mpu9250 to stm32f767zi

Hey, guys!
I am new to PX4. Here is the situation. I have flashed the px4nucleoF767ZI-v1 to stm32f767zi Nucleo board. And I am able to run mpu9250 application in Nutshell. But I don't know which pins on the Nucleo board I should connect to using SPI connection. Could you guys give me some suggestions, please?

This question should rather be posted here: http://discuss.px4.io/.
I have not tried this myself, but I know where in the code to look to find what pins are configured.
The board initialization files can be found here:  Firmware/src/drivers/boards/px4nucleoF767ZI-v1/

Looking at board_config.h, the MPU250 CS line is connected to PF2 (pin define GPIO_SPI_CS_MPU9250)
The SPI is initialized in spi.c - the MPU9250 is on bus SPI1.

To find out which pins are configured for MISO, MOSI and CLK on SPI1, you need to look at the NuttX config files. These can be found here:  Firmware/platforms/nuttx/nuttx-configs/px4nucleoF767ZI-v1:

In px4nucleoF767ZI-v1/include/board.h, you will find the definitions for GPIO_SPI1_MISO (PA6), GPIO_SPI1_MOSI (PD7) and GPIO_SPI1_SCK (PG11).

I hope that helps you.

Thank you for your response! I connected the MPU9250 as the way you said. And then I get the following:
nsh> mpu9250 test
mpu9250 test
ERROR [mpu9250] bus 0 not started
nsh> mpu9250 -s test
mpu9250 -s test
ERROR [mpu9250] bus 3 not started
Do you know how to start bus 0 or 3?

Have you started the mpu9250 driver already? You need to run mpu9250 start before you can run mpu9250 test.

Thank you for your response, ksschwabe! I just run mpu9250 start and then the mpu9250 test.
I get the following:
nsh> mpu9250 start
mpu9250 start
WARN  [mpu9250] probe failed! 0
WARN  [mpu9250] no device on bus 3
nsh> mpu9250 test
mpu9250 test
ERROR [mpu9250] bus 0 not started
nsh> mpu9250 -s start
mpu9250 -s start
WARN  [mpu9250] probe failed! 0
WARN  [mpu9250] no device on bus 3
nsh> mpu9250 -s test
mpu9250 -s test
ERROR [mpu9250] bus 3 not started
Do you know why probe failed?

Thank you, ksschwabe! I will look into those issues.

Hey, @ksschwabe.
I have checked the connection over and over. So the connection is correct. But I still can't start the mpu9250.
I used a logic analyzer to check the spi connection and I get the following diagram.

I have no idea what is wrong. Could you give me some suggestion, please?

It looks like the MPU9250 is not responding (the MISO line is not responding). Are you sure that the MPU9250 is powered corectly?

Hey, @ksschwabe
I am sure the MPU9250 is powered correctly. Because the datasheet of MPU9250 showed that for SPI and I2C have the same setting for powering it up. And I have used I2C to write and read the MPU9250.
I can get all the data from the MPU9250. I used the same setting to power up the MPU9250.
Do you have any other suggestions?  I am thinking about connecting the MPU9250 with the NUCLEO board using I2C. Could you tell me how to do it?

I think it is easiest to try and use the I2C_EXPANSION bus (as defined in board_config.h). This is I2C4. I2C is configured with I2C4_SCL on PF14 and I2C4_SDA on PF15.
When starting the MPU9250 driver, I think you can still just use MPU9250 start, otherwise you will need to pass it the 'X' option to start on the external I2C bus, MPU9250 -X start.

Do you have pull-ups on the I2C lines? (Probably not if you are connecting it directly to the Nucleo board. Or maybe your MPU9250 dev board has the pull-ups.)
You could try using I2C2 (SCL -> pin PF1 and SDA -> pin PF0) or I2C1 (SCL -> pin PF1 and SDA -> pin PF0).

Hey @ksschwabe
I have tried to use the I2C1 and I2C2. And the Nucleo board still gives me nothing.
I am using the Sparkfun MPU9250 breakout board. The board has the pull-up resistors in their SCL and SDA line.
I am afraid the code is not working. Could you give me some suggestions, please?

Unfortunately I don't have a Nucleo STM32F767ZI board, so I can't test this myself. You will have to dig through the code and try and see where it is failing.
You can try and post your problem on http://discuss.px4.io/. Hopefully someone there will be able to help you.

I will try it. Thank you @ksschwabe!

Were you ever able to resolve this? I am having a similar issue.