Only returning 10?

Ive got this install but its only returning the last 10 redirects? There are 301 redirects in there and it even says that in the response but only returns 10?

301 seperate page redirects, not 301 type redirects

Just realised I can us ethe graphql pagination querystrings on it


#2045: Functional Groups: The functional group is not added to one of the H3C

Fixed wrong false check on template insertion.
Resolves #2045

typeof neiId === 'number won't protect from NaN.
I know that in this particular case it's highly unlikely, but I'd better stick to more stable solution.


Added i18n to Kibbeh

If anybody see anything weird, please tell me or commit to this pull request. I've tested it out locally and both generating translation keys and syncing translation.json files works fine.

@goldyydev


Crash with NEI

http://pastebin.com/mDDxuKBZ
Mariculture : 1.2.4e
NEI : <IP_ADDRESS>

For it to crash there. Something would have had to break NEI's item list. Or Something would have had to break my Crucible. This crash is not worth fixing. It would crash in other places anyways.

I get this crash too. But I don't think it's an issue with NEI or other mods, since everything is fine when I just delete Mariculture. And I already deleted EVERY mod in the folder once.
About the crash: Whenever I try to look up a recipe or the use of an block/item, it shows "Shutting down internal server..." and then this crash-report gets generated: http://pastebin.com/F8pinykn
Forge: <IP_ADDRESS>8
CCC: <IP_ADDRESS> NEI: <IP_ADDRESS>
Mariculture: <IP_ADDRESS>a
I tried Forge <IP_ADDRESS>0, with the same result.


inpage.js:1 Uncaught TypeError: Cannot assign to read only property 'ethereum' of object '#'

With stable version 2.0.0 of Web3Modal now released, we are officially dropping support for version 1.x
Due to this this issue/pr was marked for closing. It is highly recommended to upgrade as 2.x will be receiving further updates that will enable functionality for some of our newer sdks like auth and push as well as support for WalletConnect v2 (See this post about WalletConnect v1 being deprecated https://medium.com/walletconnect/walletconnect-v1-0-sunset-notice-and-migration-schedule-8af9d3720d2e)
If you need to continue using Web3Modal 1.x and require this feature/fix implemented, we suggest adding it via forking V1 branch.


typo in variable name of error message when port number conflict

Exception ignored in: <bound method _ServiceBackend.__del__ of <jubakit.base._ServiceBackend object at 0x7f4ff8e4b6d8>>
Traceback (most recent call last):
  File "/home/jubatus/Development/jubakit/jubakit/base.py", line 576, in __del__
    self._unassign_port(self.port, proc.pid)
  File "/home/jubatus/Development/jubakit/jubakit/base.py", line 659, in _unassign_port
    raise RuntimeError('port {0} is used by PID {1}, not PID {2}'.format(port, m[port], pcid))
NameError: name 'pcid' is not defined

659       raise RuntimeError('port {0} is used by PID {1}, not PID {2}'.format(port, m[port], pcid))

pcid should be pid.

Fixed via #50


When downloading frameworks from cache lots of error messages are logged

Question
When downloading cached frameworks, the console shows a lot of error messages.
Steps which explain the enhancement or reproduce the bug

Uploaded carthage dependency to AWS S3 bucket with:

$ carthage bootstrap --platform ios && rome upload --cache-prefix Swift_4_2_1

Tried to download the cached framework(s) from the AWS S3 cache.

Current behavior
When running
$ rome download --cache-prefix Swift_4_2_1 -v

.. the download works.
But there are lots of console messages, which I don't understand.
Are these indicators that something went wrong?
16:23:00 2019-04-04 - Unzipped CocoaLumberjack.7B8E1169-9CDC-3E4D-A202-46874C63FFED.bcsymbolmap from: 7B8E1169-9CDC-3E4D-A202-46874C63FFED.bcsymbolmap-3.5.2.zip
16:23:00 2019-04-04 - Error: could not find CocoaLumberjack.74186576-341F-3AFC-BB25-9FC4CAE91946.bcsymbolmap in local cache at : /Library/Caches/Rome/Swift_4_2_1/CocoaLumberjack/iOS/74186576-341F-3AFC-BB25-9FC4CAE91946.bcsymbolmap-3.5.2.zip
16:23:00 2019-04-04 - Error: could not find CocoaLumberjack.4F74522A-AF89-3DD8-A36C-10967E24AD77.bcsymbolmap in local cache at : /Library/Caches/Rome/Swift_4_2_1/CocoaLumberjack/iOS/4F74522A-AF89-3DD8-A36C-10967E24AD77.bcsymbolmap-3.5.2.zip
16:23:00 2019-04-04 - Started downloading CocoaLumberjack.74186576-341F-3AFC-BB25-9FC4CAE91946.bcsymbolmap from: Swift_4_2_1/CocoaLumberjack/iOS/74186576-341F-3AFC-BB25-9FC4CAE91946.bcsymbolmap-3.5.2.zip
16:23:00 2019-04-04 - Error: could not download CocoaLumberjack.74186576-341F-3AFC-BB25-9FC4CAE91946.bcsymbolmap : ServiceError (ServiceError' {_serviceAbbrev = Abbrev "S3", _serviceStatus = Status {statusCode = 404, statusMessage = "Not Found"}, _serviceHeaders = [("x-amz-request-id","XXX"),("x-amz-id-2","XXX"),("Content-Type","application/xml"),("Transfer-Encoding","chunked"),("Date","Thu, 04 Apr 2019 08:22:59 GMT"),("Server","AmazonS3")], _serviceCode = ErrorCode "NoSuchKey", _serviceMessage = Just (ErrorMessage "The specified key does not exist."), _serviceRequestId = Just (RequestId "12FBC8A6A52E04F7")})

Suggested behavior
Why would the enhancement be useful to most users
[Explain why the enhancement would be useful to most users, list some use cases]

Rome version:
blender/tap/rome: stable <IP_ADDRESS>
OS and version:
macOS Mojave 10.14.4 (18E226)

Errors are cache misses. You're totally fine.
bcsymbolmap  ids are for all platform but of course if you either don't upload them or you don't build for all platfroms you won't have them. Hence the "error".
I should really rename this to Warning :)

@blender renaming this to warning would be helpful, or even info might be sufficient.
Or even hide these messages behind a --verbose command.


Implement feature to export geometry only

Currently when I use this tool to convert a .obj (geometry only export from Rhino3D) it introduces default materials and shaders. I'm assuming it does this so that the model will show up in a simple glTF viewer. I'm using glTF as a model format and then applying materials and shader (in three.js) programatically.
Could we/should we have an option to export a .gltf with only geometry/nodes/meshes (discarding shaders and materials)?

Could be a reasonable option here as it is probably straightforward.  It could also be a nice contribution to gltf-pipeline so that all exporters/converters could benefit.

Yeah this shouldn't be too hard to do, even if it means processing the whole glTF and then just deleting the unneeded sections. For the gltf-pipeline we will need to make sure not to oct-encode or quantize if a flag like this is set.

You likely already know that materials etc are "required" in the glTF spec, I wonder then if the option needs a warning that the generated glTF will not be standards compliant? Maybe, maybe not.

@webprofusion-chrisc the material could be stripped down to the minimal required, https://github.com/KhronosGroup/glTF/tree/master/specification#appendix-a.  Would that work for your use case?

@pjcozzi hmm, that sounds a lot like what already happens when converting a geometry only .obj? A minimal material is a good start but I'm guessing we would save about 5Kb on .gltf with no defined materials/shaders.
As an aside, as I mentioned earlier I'm using three.js GLTFLoader. The inspiration for discarding the materials is that overriding those materials currently doesn't work for me, because there's an issue somewhere with supplying your own texture, I haven't figured that out yet.

I can't speak to the three.js implementation, but the spec allows material.technique to be undefined meaning that the technique and shaders do not need to be included.  Sorry, I was not suggesting adding the entire default technique; I mean that it is implicit when not defined.

Partially fixed by #49
With --bypassPipeline no techniques or shaders are generated. A material is still generated and this is required by the gltf 1.0 spec, but that will change in 2.0.


BeforeClass being called for each Parameter

Currently, @BeforeClass methods get invoked once for the test class and then again every time a new Class Parameter combination gets tested the first time.
The code below will result in a sequence of messages like:
test: beforeClass
test: beforeClass
test: (param1 SMALL, param2 ENABLED) -> SquareBurst constructor
test: (size: SMALL, param2 ENABLED) -> before
test: (param1 SMALL, param2 ENABLED) -> test1
test: (param1 SMALL, param2 ENABLED) -> SquareBurst constructor
test: (size: SMALL, param2 ENABLED) -> before
test: (param1 SMALL, param2 ENABLED) -> test2
test: (param1 SMALL, param2 ENABLED) -> SquareBurst constructor
test: (size: SMALL, param2 ENABLED) -> before
test: (param1 SMALL, param2 ENABLED, methodParameter: SMALL) -> someShortTest
test: (param1 SMALL, param2 ENABLED) -> SquareBurst constructor
test: (size: SMALL, param2 ENABLED) -> before
test: (param1 SMALL, param2 ENABLED, methodParameter: MEDIUM) -> someShortTest
test: beforeClass
test: (param1 MEDIUM, param2 ENABLED) -> SquareBurst constructor
test: (size: MEDIUM, param2 ENABLED) -> before
test: (param1 MEDIUM, param2 ENABLED) -> test1
test: (param1 MEDIUM, param2 ENABLED) -> SquareBurst constructor
test: (size: MEDIUM, param2 ENABLED) -> before
test: (param1 MEDIUM, param2 ENABLED) -> test2
test: (param1 MEDIUM, param2 ENABLED) -> SquareBurst constructor
test: (size: MEDIUM, param2 ENABLED) -> before
test: (param1 MEDIUM, param2 ENABLED, methodParameter: SMALL) -> someShortTest
test: (param1 MEDIUM, param2 ENABLED) -> SquareBurst constructor
test: (size: MEDIUM, param2 ENABLED) -> before
test: (param1 MEDIUM, param2 ENABLED, methodParameter: MEDIUM) -> someShortTest
test: beforeClass
test: (param1 LARGE, param2 ENABLED) -> SquareBurst constructor
test: (size: LARGE, param2 ENABLED) -> before
test: (param1 LARGE, param2 ENABLED) -> test1
test: (param1 LARGE, param2 ENABLED) -> SquareBurst constructor
test: (size: LARGE, param2 ENABLED) -> before
test: (param1 LARGE, param2 ENABLED) -> test2
test: (param1 LARGE, param2 ENABLED) -> SquareBurst constructor
test: (size: LARGE, param2 ENABLED) -> before
test: (param1 LARGE, param2 ENABLED, methodParameter: SMALL) -> someShortTest
test: (param1 LARGE, param2 ENABLED) -> SquareBurst constructor
test: (size: LARGE, param2 ENABLED) -> before
test: (param1 LARGE, param2 ENABLED, methodParameter: MEDIUM) -> someShortTest
test: beforeClass
test: (param1 SMALL, param2 DISABLED) -> SquareBurst constructor
test: (size: SMALL, param2 DISABLED) -> before
test: (param1 SMALL, param2 DISABLED) -> test1
test: (param1 SMALL, param2 DISABLED) -> SquareBurst constructor
test: (size: SMALL, param2 DISABLED) -> before
test: (param1 SMALL, param2 DISABLED) -> test2
test: (param1 SMALL, param2 DISABLED) -> SquareBurst constructor
test: (size: SMALL, param2 DISABLED) -> before
test: (param1 SMALL, param2 DISABLED, methodParameter: SMALL) -> someShortTest
test: (param1 SMALL, param2 DISABLED) -> SquareBurst constructor
test: (size: SMALL, param2 DISABLED) -> before
test: (param1 SMALL, param2 DISABLED, methodParameter: MEDIUM) -> someShortTest
test: beforeClass
test: (param1 MEDIUM, param2 DISABLED) -> SquareBurst constructor
test: (size: MEDIUM, param2 DISABLED) -> before
test: (param1 MEDIUM, param2 DISABLED) -> test1
test: (param1 MEDIUM, param2 DISABLED) -> SquareBurst constructor
test: (size: MEDIUM, param2 DISABLED) -> before
test: (param1 MEDIUM, param2 DISABLED) -> test2
test: (param1 MEDIUM, param2 DISABLED) -> SquareBurst constructor
test: (size: MEDIUM, param2 DISABLED) -> before
test: (param1 MEDIUM, param2 DISABLED, methodParameter: SMALL) -> someShortTest
test: (param1 MEDIUM, param2 DISABLED) -> SquareBurst constructor
test: (size: MEDIUM, param2 DISABLED) -> before
test: (param1 MEDIUM, param2 DISABLED, methodParameter: MEDIUM) -> someShortTest
test: beforeClass
test: (param1 LARGE, param2 DISABLED) -> SquareBurst constructor
test: (size: LARGE, param2 DISABLED) -> before
test: (param1 LARGE, param2 DISABLED) -> test1
test: (param1 LARGE, param2 DISABLED) -> SquareBurst constructor
test: (size: LARGE, param2 DISABLED) -> before
test: (param1 LARGE, param2 DISABLED) -> test2
test: (param1 LARGE, param2 DISABLED) -> SquareBurst constructor
test: (size: LARGE, param2 DISABLED) -> before
test: (param1 LARGE, param2 DISABLED, methodParameter: SMALL) -> someShortTest
test: (param1 LARGE, param2 DISABLED) -> SquareBurst constructor
test: (size: LARGE, param2 DISABLED) -> before
test: (param1 LARGE, param2 DISABLED, methodParameter: MEDIUM) -> someShortTest

As can be seen, the @BeforeClass annotated method gets invoked multiple times.
My test methods need some resources that are read only and thus can be shared. However, it takes multiple seconds to create these, so I'd like to initialize them once for the entire test class.
I propose, BeforeClass should be called once for every test class, not for every new combination of Class Parameters. This is how JUnit's Parameterized Class does it as well.
Also, it would be great to have a new annotation that can be used to invoke a method every time a new Class Parameter combination is created, just like @BeforeClass does now, but give it access to the newly created Class Parameter combination, so that it can be used to do a one time setup and teardown for each Class Parameter combination.
Example Code:
@RunWith(BurstJUnit4.class)
public class SquareBurst {

	public enum Parameter1 { SMALL, MEDIUM, LARGE }
	public enum Parameter2 { ENABLED, DISABLED }
	public enum MethodParameter { SMALL, MEDIUM }

	@Before
	public void before() {
		System.out.println(String.format("test: (size: %s, param2 %s) -> before", size, parameter2));
	}

	@BeforeClass
	public static void beforeClass() {
		System.out.println("test: beforeClass");
	}

	private Parameter1 size;
	private Parameter2 parameter2;

	public SquareBurst(Parameter2 parameter2, Parameter1 size) {
		System.out.println(String.format("test: (param1 %s, param2 %s) -> SquareBurst constructor", size, parameter2));
		this.size = size;
		this.parameter2 = parameter2;
	}

	@Test
	public void someShortTest(MethodParameter methodParameter) {
		System.out.println(String.format("test: (param1 %s, param2 %s, methodParameter: %s) -> someShortTest",
		                                 size, parameter2, methodParameter));
	}

	@Test
	public void test1() {
		System.out.println(String.format("test: (param1 %s, param2 %s) -> test1", size, parameter2));
	}

	@Test
	public void test2() {
		System.out.println(String.format("test: (param1 %s, param2 %s) -> test2", size, parameter2));
	}

}

I propose, BeforeClass should be called once for every test class, not for every new combination of Class Parameters. This is how JUnit's Parameterized Class does it as well.

Yes. This is a clear bug.

Thanks for the detailed bug report.
A separate annotation like @BeforeVariation seems like a good idea; I'll try adding that later after the fix is in.

Awesome, thanks for the fast fix. Looking forward to the @BeforeVariation annotation.


Correct a typo in profileservice.rst.

What issue does this PR address?
Fix a typo in profileservice.rst.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[x] Unit Tests for the changes have been added (for bug fixes / features)

Other information:

Thanks


bs-alert onDismiss and onDismissed actions not working

Output from ember bootstrap:info (available since 1.0.0-alpha.9):
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version 5.2.8 located: carapp -> ember-select-2 -> ember-cli-babel
Npm packages:
ember-bootstrap: ^1.2.2 -> 1.2.2
ember-cli: ~3.1.4 -> 3.1.4
bootstrap: ^4.1.1 -> 4.1.1
bootstrap-sass: n/a
ember-cli-sass: ^7.1.7 -> 7.1.7
ember-cli-less: n/a
Bower packages:
bootstrap: n/a
bootstrap-sass: n/a
ember-bootstrap configuration:
bootstrapVersion: 4
importBootstrapFont: false
importBootstrapCSS: false

I cannot seem to hook into onDismiss or onDismissed. Either the documentation is unclear and I'm using this wrong, or there is a bug.
{{#bs-alert type="danger" class="mt-4" visible=errVisible onDismiss="onDismissed2"}}
	Error - {{signInError}}
{{/bs-alert}}

Uncaught TypeError: this.get(...) is not a function
    at Class.dismiss (bs-alert.js:119)
    at Class.send (action_support.js:128)
    at Class.superWrapper [as send] (ember-utils.js:428)
    at ember-glimmer.js:5943
    at exports.flaggedInstrument (ember-metal.js:4582)
    at ember-glimmer.js:5942
    at Backburner._run (backburner.js:758)
    at Backburner._join (backburner.js:736)
    at Backburner.join (backburner.js:477)
    at Function.run.join (ember-metal.js:456)
dismiss @ bs-alert.js:119
send @ action_support.js:128
superWrapper @ ember-utils.js:428
(anonymous) @ ember-glimmer.js:5943
exports.flaggedInstrument @ ember-metal.js:4582
(anonymous) @ ember-glimmer.js:5942
_run @ backburner.js:758
_join @ backburner.js:736
join @ backburner.js:477
run.join @ ember-metal.js:456
handler @ ember-glimmer.js:5921
(anonymous) @ event_dispatcher.js:234
dispatch @ jquery.js:5183
elemData.handle @ jquery.js:4991

You cannot pass a string as an action. This addon requires so called closure actions, i.e. regular functions. Use something like onDismiss=(action "myaction")!
This is a good read regarding this topic, in case you need some more background: http://miguelcamba.com/blog/2016/01/24/ember-closure-actions-in-depth/

Thank you for clarifying.
The addon could use some input checking to prevent seemingly unrelated errors, but in the end I was using it wrong, and the closure works! :+1:


Add missing properties to stagnation _ShockClass

Thanks @ashwinvis! Merging :)

That was quick!
Sent from ProtonMail mobile
-------- Original Message --------
On 8 May 2018 2:35 pm, Juan Luis Cano Rodríguez wrote:

Merged #24.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Vagrant up doesn't bring the machine up as it probably should

$ vagrant up

doesn't result in the machine being brought up as expected.
This has already been mentioned in https://github.com/zendframework/modules.zendframework.com/pull/187#issuecomment-51773218, but as pointed out there, this is a deal breaker for people willing to contribute.
Can someone please have a look?
Here's the console output of my attempt:
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'debian-wheezy72-x64-vbox43'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: moduleszendframeworkcom_default_1416328545092_76185
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 => 6161 (adapter 1)
    default: 80 => 8082 (adapter 1)
    default: 3306 => 3308 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: <IP_ADDRESS>:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout.  See http://links.puppetlabs.com/env-settings-deprecations
==> default:    (at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning')
==> default: Finished updating puppet to latest version: Puppet v3.7.3
==> default: Created empty file /.puphpet-stuff/update-puppet
==> default: Running provisioner: shell...
    default: Running: /var/folders/fb/q922_rc10fjf303z816ybdmc0000gn/T/vagrant-shell20141118-53922-q4pjpt.sh
==> default: stdin: is not a tty
==> default: Installing git
==> default: dpkg-preconfigure: unable to re-open stdin: No such file or directory
==> default: Finished installing git
==> default: Copied Puppetfile
==> default: Installing base packages for librarian
==> default: dpkg-preconfigure: unable to re-open stdin: No such file or directory
==> default: Finished installing base packages for librarian
==> default: Installing librarian-puppet
==> default: Finished installing librarian-puppet
==> default: Running initial librarian-puppet
==> default: Finished running initial librarian-puppet
==> default: Replacing puppetlabs-git module with custom
==> default: Cloning into '/etc/puppet/modules/git'...
==> default: Finished replacing puppetlabs-git module with custom
==> default: Running provisioner: puppet...
==> default: Running Puppet with manifest.pp...
==> default: stdin: is not a tty
==> default: Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
==> default:    (at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning')
==> default: Info: Loading facts
==> default: Info: Loading facts
==> default: Info: Loading facts
==> default: Info: Loading facts
==> default: Info: Loading facts
==> default: Info: Loading facts
==> default: Info: Loading facts
==> default: Info: Loading facts
==> default: Info: Loading facts
==> default: Error: PHP: cannot set both source and template on node packer-virtualbox.vagrantup.com
==> default: Error: PHP: cannot set both source and template on node packer-virtualbox.vagrantup.com
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

@localheinz ping! :) I use this configuration, does it work for you?


Add function to set LCD brightness

The project has been switched to use M5Unified library which makes this PR obsolete. Closing.


SqlNormalizedCacheFactory make sqldriver public to support Sqlcipher data encryption.

@yuvaraj119: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/


MongoDB Connector

This feature requests serves as a central place to discuss development and progress for the MongoDB connector. Please contribute in the comments below. I will update the top comment as consensus forms.

Here's an outline of some things we need to consider:

align with existing Mongo-based GraphQL APIs (vulcanJs)
active/passive (does schema migration even make sense?)
mutations (can we support the powerful nested mutations? relations?)
queries (What are the query limitations?)
subscriptions

Top level fields
For each type with an id field, the following fields are generated:

Types without an id field are called embedded types and are stored as nested documents.

The id field is represented as _id in the mongo document per normal mongo convention. Prisma does not support having both _id and id fields.

The type User is used as an example throughout this document

Query

user returns a single user
users returns a list of users
usersConnection returns a relay style Connection of users

In addition to the generated query fields, the following field is present:

node returns a single node by id

field name generation
The user field name is generated by taking the type name and lowercasing the first letter
The users and usersConnection field names are generated by taking the type name and lowercasing the first letter and then using the evo-inflector library
Mutation

createUser create a single user
updateUser update a single user
deleteUser delete a single user
upsertUser update a single user if exists, otherwise create
updateUsers update multiple users
deleteUsers delete multiple users

Note: The API has no explicit mutations for managing relations. Instead relations are managed through nested mutations #1280

MongoDB has no concept of foreign key constraints and cascading deletes. Prisma ensures that relations stays valid and that cascading deletes are enforced.

Examples:
A -> B

Deleting B will fail if the relation is required and there is no cascading delete
Deleting B will succeed if the relation is required and there is cascading delete
Deleting B will succeed if the relation is not required and there is no cascading delete. In this case the relation field will be set to null
Deleting B will (obviously) succeed if the relation is not required and there is cascading delete

Note: MongoDB has no concept of transactions that span more than one document. As mutations that involve relations or mutate many nodes, involve multiple documents, it is possible that the mutation will be only partially applied if the server is stopped before the mutation completes.

Details
type Query {
  user(where: UserWhereUniqueInput): User

  users(
    where: UserWhereInput
    orderBy: UserOrderByInput
    skip: Int
    before: String
    after: String
    first: Int
    last: Int
  ): [User!]!

  usersConnection(
    where: UserWhereInput
    orderBy: UserOrderByInput
    skip: Int
    before: String
    after: String
    first: Int
    last: Int
  ): UserConnection!
}

type Mutation {
  createUser(data: UserCreateInput!): User!
  updateUser(data: UserUpdateInput!, where: UserWhereUniqueInput!): User
  deleteUser(where: UserWhereUniqueInput!): User
  upsertUser(where: UserWhereUniqueInput!, create: UserCreateInput!, update: UserUpdateInput!): User

  updateUsers(data: UserUpdateInput!, where: UserWhereInput!): BatchPayload
  deleteUsers(where: UserWhereInput!): BatchPayload
}

Nested Mutations
Mongo supports arbitrarily nested documents but has no understanding of relations between documents.
Prisma supports two ways to model related data:

relations
embedded types.

relations is a great fit for relational databases and Prisma implements embedded types for SQL databases by automatically managing all the tables and foreign keys required.
In the same way, embedded types is a great fit for mongos document model. Prisma implements relations by performing multiple inserts/updates or queries under the hood.
When is a type embedded?
In Prisma a type is considered to be embedded when it has no id field. Types without an id field can only ever exist when referenced from an "owning" type. The mongo connector takes advantage of this fact by using mongos native capability to nest documents. This can result in improved performance compared to SQL.

Note: MongoDB has a storage limit of 16mb per document. This limits the aggregate size of a single node with embedded types. The SQL connector does not have this limit.

handling of relations

todo: specify how mutations and queries are handled for embedded types

scalar lists

todo: specify how scalar lists are implemented. They should be embedded. Document how each operation maps to mongos primitives. Document storage limit

There needs the be a common api or interface so one can switch to different connectors.

That's a great point @juicycleff
We plan to support database specific APIs as well a a Core API. Most of the database specific APIs will have significant overlap with the core API making it easy to switch between connectors. For Mongo and SQL specifically we will be able to have almost 100% overlap :-)

If you need some inspiration for a GraphQL type system of a document database, have a look at cruddl. This is a TypeScript library that servers a GraphQL API similar the one of prisma, but it uses ArangoDB as database (might also be interesting for #1645) is built to embrace the possibilities of document databasees like embedding. We invented four kinds of object types to support different use cases of embedding and relating objects - like when id should be auto-generated and whether omitted fields in update mutations should remove them or leave them unchanged.

Have a look at graphql-compose it's a toolkit for construction of complex GraphQL schemas. Provides bunch of plugins for type generation. Allows to build your own plugins/helper-functions for type construction and modification and graphql-compose-mongoose a Mongoose model converter to GraphQL types with resolvers. They also have type generator plugins for elasticsearch and aws

@sorenbs in my opinion, we should consider a model without embedded type to remove the complexity of mongodb connector. As far as I know:

Current generated Prisma api does not support embedded type
We just implement connector to support current Prisma API

@duytai i agree.
The term embedded type is used here only to describe a certain way to lay out your data. Prismas SQL connector has no understanding of that term and neither will the Mongo connector. The final api will be almost identical apart from less powerful filters.

any updates on this?

Is someone working on this at the moment?

Yes, we are 🙂
We plan to start a preview for the MongoDB connector later this month. Please reach out to me in Slack (@nilan) if you're interested in participating.

An update for this note:

Note: MongoDB has no concept of transactions that span more than one document. As mutations that involve relations or mutate many nodes, involve multiple documents, it is possible that the mutation will be only partially applied if the server is stopped before the mutation completes.

Transactions will be supported in 4.0

todo: specify how mutations and queries are handled for embedded types

In Mongodb joins/relations are not recommended for cases where the related documents don't change often, better said, we have a lot more of queries than mutations, for example, suppose that our User has a books fields which can be a one-to-many relation or just an embedded field with the books instead, A Book will probably never change so we don't need a one-to-many relation here.
I believe embedded types can be handled in the same way Prisma handles relations, but every embedded document should contain an id (and the operations for update/remove/insert will be using different mongodb operators). In most cases embedded documents will contain an id, or something that will allow them to be identified inside the array (like the index), if the embedded document is just an object and not an array, all operations will be for that document.

@sorenbs Have you considered including any mongoose-specific abstractions like virtuals and references/reference population (i.e. using references as an alternative to embedded documents)? I've really liked utilizing mongoose's populate operator to keep document sizes to a predictable limit, avoid arrays growing without bound, and normalize the data as much as possible. Virtuals/getters and setters are more of a nice-to-have but have still proven to be handy in certain situations, acting like Redux selectors.
I know the purpose of the mongodb connector isn't to be a mongoosejs connector, however I anticipate a large number of developers having likely interacted with mongoosejs as much if not more than the mongodb API directly, so having some familiar features might make the adoption process easier.
Also, do you plan to support GeoJSON object types for geospatial queries? They've been indispensable in a few projects and I'd really hope for them to be supported.

+1 for GeoJSON. My primary use case for mongo is to enable efficient geospatial queries. These complex queries can be done with mongo directly, but the ability to resolve GeoJSON data through Prisma would be very handy.

hi @marktani. Do you have this MongoDB connector in a specific branch, what's the name of the branch. I would like to take a look to the code. Thanks

...just to clarify my earlier comment re GeoJSON, the key to allowing location queries is a location field on the document. It'd be great if the Prisma SDL included a type such as GeoPoint (as it does other types, like DateTime). Then a mongo geolocation query could be done independent of Prisma, or even awesomer, through Prisma with its paging support.

@alexandrakl,@sorenbs  - I would love to contribute to this project. I hope that it's not too late. Currently, I'm studying data science at Berkeley.  And I have been a fan of this project. Full Disclosure - I only just got started with Scala. I would love for this to be a learning experience.

@ArvinGanesan - it is never too late to contribute :-)
I think the MongoDB connector would be too big of a mouthful for you to tackle if you are new to Scala. As a first step I would recommend that you clone the repo and get to a point where you can run the tests locally.
Issues tagged good-first-issue https://github.com/graphcool/prisma/issues?q=is%3Aopen+is%3Aissue+label%3Agood-first-issue might be a good place to start. Alternatively you could find a reported issue that you find interesting and create a test case that demonstrates the issue. This will help us prioritise and fix that issue and it helps you get an understanding for the code base.
Please keep in mind that the code base is moving fast and we might not be able to merge your PR.
@debianw We will begin implementing the MongoDB connector in a few weeks and will link the branch from this issue so you can follow along. Our initial plan was to begin the implementation last month, but we had to rearrange some work tasks.
@heysailor - thanks for your input on GeoJSON. This is definitely on our radar!

@sorenbs - I ran in to some sbt build error. I did create an issue for that - sbt build error #2349
Any help is appreciated!

I  this being developed in a public branch somewhere?
I'm curious how it's progressing since the initial delivery timeframe was back in April.
We have a new project rapidly approaching its prototype phase and we are asking ourselves  if we can count on this being public by then.

@jay-jlm We are planning to release a public roadmap soon. Although our planning is not final yet, you should expect a beta release of the MongoDB connector in August.

@sorenbs I read in prisma blog that version 1.11 (next one) will include the beta support for mongodb. Does this roadmap still the same?

@bazaglia that is inaccurate - sorry about the confusion. August is the current plan :-)

Transactions will be supported in 4.0

MongoDB 4.0 was released on June 28.
https://www.mongodb.com/transactions

https://www.prisma.io/ lists MongoDB as a selling feature but this thread seems to contradict that...am I missing something? is there another branch I can checkout?

@nolandg The mongodb connector is probably the closest connector coming out soon, it will be released in August

happy 10th of August 😎 🏖

The work for the Mongo connector is underway and there is a related discussion about embedded types. So if someone has strong opinions around embedded types you can chime in here: https://github.com/prisma/prisma/issues/2836

Happy 24th of August, evryone!
Say what you want about the Prisma team, but you can't deny they know how to keep the graphql community on their toes!  😆😆

Are there any updated timelines as we're about to start the first week of September?

We are actively working on it. You can follow this PR https://github.com/prisma/prisma/pull/2883

How can I test the new functionalities???

Once we have a public preview available we'll report back here.

We now have a very early prototype available for testing. We decided to implement the new feature of embedded types first to get feedback on that early on. You can head over here to check out how to try out the early preview.

The website says it working on mongodb but you comments says beta, prototype, in-progress, I highly suggesst better removed that "check" on mongodb because it's totally misleading.
Admit it, you just want a marketing bait!!!!!
Grow up prisma and separate yourself from those poor documented and poor company that just want attention based on non-existing products. I've been to that, I've been to the company that just sells "photoshoped" products, products that exists only on photoshop, but no really running product.
Grow up and fixed yourself!!!

Thanks for sharing your point of view, @iamrommel! 🙂You are expressing what probably many are thinking. I can feel your frustration! I am sorry to hear that you feel misled, and I offer a different perspective.
It is not our intention to use marketing terms or click bait titles to draw in more attention. In fact, we are positively overwhelmed about the attention and the passionate feedback for the MongoDB connector, and many other connectors! It makes me smile everytime there's a new feature request for a new DB connector, or someone offering their help in pushing a particular connector forward.
Driven by our excitement and the community feedback, we are working hard on building more connectors and are really excited about its potential. We have validated the MongoDB connector in thorough internal tests and many discussions and demos with customers. Hence, we are convinced that the MongoDB connector will provide a lot of value, and we want to share our excitement and conviction with the community on our homepage!
However, we don't always find the right ways and words to express this excitement, what we think about a feature, or what state it's currently in. And we have been working much longer on the MongoDB connector than anticipated. These are aspects where we can improve a lot, and I really appreciate your participation by reminding us of this.
One particular step of improvement that I can think of is to add a "beta" label whereever the MongoDB connector is mentioned on our homepage. I will bring this up to the team.
I hope you will try out the preview soon, and I'm curious to hear what you think about it. You can always find me in Slack (@nilan), if you have any questions or want to share anything else. Thanks 🙌

Great answer. I think everyone needs to realize that making money off of open source involves walking some tricky and thin lines and it will be impossible to do it all perfectly and keep everyone happy. This must be even more difficult when you're spending someone else's $4.5M and they need to see returns.  I accept commercial open source being a bit trigger happy in the marketing department as a necessity of getting this great software. Cheers to Prisma, you're making me money.

@nolandg i know everyone needs a move to make some money. But i guess everyone needs be careful too.
My point on my post is being true on prisma for telling user/customer about thier product status. The mongodb CRUD from the website has been check maybe 2 or 3months (or even more) but there is no valid resources for it, i've been checking on it for them several times but none was provided.
The information is misleading that is what want to emphasize.
I now remember Aesop's fable about the boy and the wolf. The boy always telling lies about the attack of the wolf, and in the end when real wolf attacks, no one listen. So of prisma continues to feed us wrong/misleading/click bait thing, no one would listen even the real feature was realease and then lowering the confidence to the company too.
I'm not throwing stones at prisma, i'm just giving harsh feedbacks. And that's what REAL friends do, giving harsh comments and not sweet compliments. :)

That's an interesting criteria for friendship 🤔
Regardless, this is a professional setting, not a friendship, and real professionals conduct themselves accordingly. Your tone here is counterproductive and overshadows any valid points your argument might have. Shouting "grow up" at the devs is a bit ironic, no?

@iamrommel We understand your point, Prisma still doesn't has the mongodb connector, I even remember having a preview of the Beta of the new Prisma that was going to replace Graphcool and asking why Mongo was there, they had plans to have the connector released very soon, it didn't happen but that doesn't means we need to be rude about it, it's open source and it's free, they surely have more priorities and we can always be nice about this stuff, I agree with your point, but not with "harsh comments and not sweet compliments".

Maybe i'm on the wrong neighborhood, because "constructive feedback" are so 1900s, and  harsh comments are future (or maybe i'm living in the future.)
If anyone is offended, I sincerely apologize!

@iamrommel  ouch, it must be indeed very self-reassuring to think that one's ideas come from the future.
Sadly, I'm afraid you just happen to lack basic understanding of how basic economics work.
Companies must able to market future technologies because you need to build visibility for your product before it reaches the market so that demand has scaled to a sustainable level by the time does.
Let me offer a different perspective than yours about "growing up": being a "grown-up" (developer) is all about relying on yourself to evaluate which and when to adopt and up-and-coming technology,  and not about expecting Prisma's mkt department to do this job for you.

@jay-jlm,
Companies must able to market future technologies (that they have already committed resources to develop) because you need to build visibility for your product before it reaches the market so that demand has scaled to a sustainable level by the time does.
These are the things that I hate these days, as i have said, i've been to companies like these, just selling ideas from "photoshopped" products. It's very hard for the customer to accept that they wanted the product now and it's not yet available. You tell your customer that your prodcut are ready but when they want it now, they tell you back it under massive developement. They marketting specifically tells you that it's ready to roll and when you are going to use it, they'll drop you a bomb that it's not ready.
Remember my point about is about truth about the status. Mongodb CRUD feature is there for a couple of months but haven't seen any actual implememtation. If only that is stated clearly (coming soon, beta) then i'm pacified. And that is how to tell your customers about the future ideas (telling the thruth that it is beta or coming soon)

Even though there have been a lot of messages since my last post, I don't think I can add anything of value to the conversation at this point which I haven't said already. I think everyone had the chance to share their input 🙂
This thread is not right the place to continue this discussion. I would encourage everyone to start a new discussion in the feedback section of our Forum if there is further need to talk: https://www.prisma.io/forum/c/feedback. I appreciate any and all input there.
If you are interested in the MongoDB preview, head over to https://github.com/prisma/Mongo-Connector-Preview.
And again, you can always find me in Slack (@nilan) to talk about anything.
Thank you.

We just merged Join-Relations (relations between models in different collections) into the Mongo Connector preview. If you want to try it out, I’ve updated the preview page. As always: feedback is very welcome. https://github.com/prisma/Mongo-Connector-Preview/blob/master/README.md (ed

This is a proposal for the directives to  be introduced for the Mongo connector.
We are already using connector specific directives in the Postgres Passive connector. https://www.prisma.io/docs/data-model-and-migrations/introspection-mapping-to-existing-db-soi1/#overview

Postgres Directive
Active
Passive

@pgTable(name: "X")
opt
opt
can be provided to rename tables

@pgColumn(column: "X")
opt
opt
can be provided to rename columns

@pgRelation(column: "X")
opt
req
has to be provided to identify fields with relation ids

@pgRelationTable(table: "X")
-
req
identifies a relation table

Mongo Directive

@mongoCollection(name: "X")
opt
opt
can be provided to rename collections

@mongoField(field:"X")
opt
opt
can be provided to rename fields

@mongoRelation
req
req
explicitly determine the side that stores inline relation ids

@mongoRelation(field:"X")
opt
opt
can be provided to rename inline relations and embedded types

Active Connector
Bi-Directional Join Relation
type Parent{
    name: String
    child: Child @mongoRelation    # required! this side has inline ids, autogenerated field names
}

type Child{
    name: String
    parent: Parent
}

Uni-Directional Join Relation
type Parent{
    name: String
    child: Child     # optional. no directive necessary since there is only one relationField
}

type Child{
    name: String
 }

Embedded Type Relation
type Parent{
    name: String
    child: Child     # optional. embedded under fieldname
}

type Child @embedded {
    name: String
}

Embedded Type To Other Non-Embedded Type Relation
type Parent{
    name: String
    child: Child     # optional. stored under fieldname
}

type Friend{
    name: String
}

type Child @embedded {
    name: String
    friend: Friend  # optional. stored under fieldname
}

Passive Connector
Bi-Directional Join Relation
type Parent{
    name: String
    child: Child @mongoRelation    # required! field which stores ids
}

type Child{
    name: String
    parent: Parent
}

Uni-Directional Join Relation
type Parent{
    name: String
    child: Child    # optional. field which stores ids
}

type Child{
    name: String
 }

Embedded Type Relation
type Parent{
    name: String
    child: Child      # optional. field that stores inline ids
}

type Child @embedded {
    name: String
}

Embedded Type To Other Non-Embedded Type Relation
type Parent{
    name: String
    child: Child     # optional. field that stores inline ids
}

type Friend{
    name: String
}

type Child @embedded {
    name: String
    friend: Friend   # optional. field that stores inline ids
}

Questions:

always use name instead of field/column/name?
discern between mongo/pg?
relation tables in mongo

While I appreciate the passion displayed by the community in the comments here, this thread is a place to discuss design decisions for the upcoming MongoDB connector. I have deleted a number of comments that were off-topic. If you are interested in these other topics, feel free to reach out to me in slack or open a conversation in the forum.

Take a look at mongodb references. Equivalent to foreign keys in pgsql.
It was also previously mentioned that multi-document transactions is supported by mongo 4.0.

As we are getting closer to the first beta release of the Mongo connector, we are looking for early adopters to take it for a spin.
If you are planning to build an application using Prisma and MongoDB, now is a good time to get involved to make sure the MongoDB connector covers all your needs.
If you are interested, please ping @do4gr here or in the Prisma slack 🙏

@do4gr , I'm interested in testing it out... any docs I can follow?

The documentation how to set up Prisma to use Mongo and how to use the new features can be found here: https://github.com/prisma/Mongo-Connector-Preview

Also interested in testing out the MongoDB connector.

To those trying out this new connector, it would be great to leave links if your work is open source.
Hoping to try this myself soon.

@do4gr I'd like to test the MongoDB connector and hope to use it in production on a project I'm currently building.

The current documentation how to use it can be found here: https://github.com/prisma/Mongo-Connector-Preview
We'll release full documentation in the next days.

https://www.prisma.io/blog/mongodb-preview-ow4wahkekaep/ 🎉

I was waiting a long time for this, and I must say prisma is doing a great job, I was wondering if there is support for multi-document ACID transactions that were introduced in mongodb v4. I can see that the current documentation is using mongodb v3.6 not v4+. Thanks!

Hey @vibhanshu909,
we haven't done extensive testing on the compatibility with Mongo 4.0. The core is structured in a way that we should be able to test this with 4.0 fairly easily. The challenge is in properly testing this for correctness and performance afterwards. This is why we are still holding off on this. But I would expect us to enable this at some point.

Wow amazing, wish have support mongo 4.0 soon 👍

You can track the progress on multi-document ACID transactions in #3785

Nothing about GeoJson? this future is mandatory for many MongoDB projects.


enhancement in the buttons of Navbar.

@RIKI-05
i would like to work on this issue under hactoberfest.

@amananand917 do the necessary changes

I would like to contribute


Please include region and subregion names in dungeons.json

hi,
please, can you include fields

region_name
subregion_name

in dungeons.json file?
Thank you.

Hey, this should be satisfied by 8e9b70afd329910dcaefdc90cbfa141dc7baaf40, right?

It does! Thank you very much!


This version of Android Studio cannot open this project, please retry with Android Studio 4.0 or newer.

Expected behavior
After cloning project should successfully run on all versions of Android Studio.
Actual behavior
It's showing an error message"This version of Android Studio cannot open this project, please retry with Android Studio 4.0 or newer."
Steps to reproduce
1.Clone this repository to Android studio version which before "4.0.0".
2.Let the gradle build finish.
3.You will see the error message.
Environment
K-9 Mail version:

We typically don't use alpha or beta versions of the Android Gradle Plugin (AGP). So if you stay with the latest stable Android Studio version you should always be able to build K-9 Mail. However, we won't limit ourselves to even older AGP versions, so older Android Studio versions can be used. That means right now you'll have to use Android Studio 4.0 or newer.
May I ask why using Android Studio 4.0 doesn't seem to be an option for you?

Yes we should use stable version but it should also other versions too .Because I have also tried other that projects run successfully on this version and that's completely fine if we shouldn't consider this as an issue.


test: disable e2e tests pending investigation

test: disable e2e tests pending investigation

bors try

bors try

bors try

bors try

bors merge

bors merge

bors merge

bors merge


Scrolling Behavior for better UX (User Experience) in Product page

When clicking on any nav icon, it navigates to the section.
However this navigation is not smooth, and feels rough for user.
Having a smooth navigation would be better experience for customer journey.
https://github.com/user-attachments/assets/982bd8ed-f3fb-466b-93ae-65972fe3c09b
added better version for it.
https://github.com/user-attachments/assets/bcc30ed4-ca14-454d-9ade-060ae0416696

I would really like to work on it! Please assign it to me.
Also assign relevant labels (GSSOC ext) , good first issue

Proceed!

I almost done with that, along with that found one more issue related to product nav link may I also fix that and report in PR

https://github.com/user-attachments/assets/4e10f76a-8ab6-442c-b035-3128126eeaba


docs: fix references to config.plugins

Hi, folke: I was following your new updates, and then I noticed that this link is broken. In the URL: both tree and blob can work, I picked the one used in the next line!
(Thank you for creating this great plugin and sharing your dotfiles btw! It helps me a lot during my config debugging!)

I've updated the docs to point to LazyVim instead of my personal dots.


Upgrade to mypy 0.711

A continuation of the mypy upgrade from #12139

This is my first shot at doing an upgrade like this, it looks like there were some other small errors, mainly related to test_runner, which I updated as part of 2f88d29 before upgrading to 0.711

I updated this by splitting it into a bunch of preliminary commits with explanations.  Looking forward to feedback regarding the "whys" and "hows".

Merged as the series ending with ba7a0934e382add096702914c6ef66afcda6388f, after doing cleaner / more correct fixes for a number of the individual commits.


Change missing ref loaders error to warning

v7.0.20 introduced a change to the reference lookups that made them error if no ref loaders were configured on the xslt filter element.  This makes sense as without any ref loaders the lookup(s) can never return anything.  However this is causing processing to error where previously it would have been processed with unsuccessful lookups.
Plan is to change it to WARNING for v7.0 and then change back to ERROR for v7.1.
Error msg is this in AbstractLookup
No reference loaders are configured so the lookup cannot be performed.

Changed back to warning

Fixed in > 7.0.20


Detect filetypes for *.v files

closes #12274
Edit: Uff, what did I do to get this cov report? 🙈
Also feel free to point out or change formatting or naming preferences. I haven't found a consistent style in the codebase that I could model myself after. Since ci takes a bit, I'll hold off on making further changes on my end.
Edit 2: Okay codecov was re-subbed I see.🍀

for ln in getline(1, numberOfLines)

Could .v files be million lines long? Wouldn't that take too much memory?
Perhaps that should be changed to  for ln in getline(1, min(200, numberOfLines)) to be on the safe side?

yes, I think that should also work. Thanks!

Please note that .v is also an extension used for Coq files. The most commonly-used Coq-related Vim plugin https://github.com/whonore/Coqtail unconditionally detects *.v as the filetype coq.
If need be, words like Require, Import, Definition, Inductive, and (* *) comments could be used for disambiguation.

Thanks for the hint @benknoble.
As far as I can see, the most distinct patter next to comment style are dot character code line endings .. Since it looked to me that there are a few more keywords in Coq that would match the dot ending is probably on the safer side. What do you think about using this for disambiguation?

Thanks for the hint @benknoble. As far as I can see, the most distinct patter next to comment style are dot character code line endings .. Since it looked to me that there are a few more keywords in Coq that would match the dot ending is probably on the safer side. What do you think about using this for disambiguation?

Seems reasonable. Most Coq commands can be thought of as "sentences" ending with ., as you said.

This one might be ready. When a moment frees up you can take a look @brammool 🙂:+1:

Thanks for making this PR.  A few remarks.
The use of "non_comment_line_num" doesn't look very useful.  Dropping it
makes it simpler, and I don't see much of a disadvantage.
I suppose this condition is to detect the start of a comment:
if ln[0] ==? "/"

This doesn't allow for any white space before the slash.  To allow for
that this should work better:
if ln[0] =~ '^\s*/'

If 'filetype' was already set then the ":setf" commands won't do
anything.  Still we go through the lines to do the detection, which is a
waste of time.  To avoid it put this at the top of FTv():
if did_filetype()
   return
endif

The test is minimal, but it's a good start.
--
A law to reduce crime states: "It is mandatory for a motorist with criminal
intentions to stop at the city limits and telephone the chief of police as he
is entering the town.
[real standing law in Washington, United States of America]
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Thanks a lot @brammool. I applied your suggestions.


Cache reset by specified db operations

Your Question
How can I reset my cache from the memory example by specified operations like create, update and delete?

The document you expected this should be explained

Expected answer

Hey @dennis-dko,
This is a big and complex topic, but I will try to keep it as simple as possible.
My personal opinion is that in this case I'd go with designing my application in a way that handles intervals of inconsistent data, caching the items for shorter amounts of time etc.
Now let's look at the problem you are facing from technical perspective.
Problem's complexity explained...
If you really want to go to this rabbit hole, and want to invalidate the cache items for a specific entity it could easily become the mission impossible. Two main points..

Parsing the SQL query that is prepared to be sent to the DB, and deciding what to invalidate?

This requires some kind of SQL tokenizer, Parser, and logic that decides what is affected.

What if you have a custom SQL function defined, of which you don't have the source code?

This makes it almost impossible to accommodate for.

Middle ground solution (What I'd do)
I'd write a cache invalidator that registers for the following gorm hooks (reference on how to properly register for those check this plugin's source code https://github.com/go-gorm/caches/blob/master/caches.go#L37 In here i am registering the c.Query function that wraps around (decorates) the default /gorm's/ gorm:query hook)

gorm:after_create
gorm:after_update
gorm:after_delete
In those hooks I'd just invalidate all the caches generated beforehand.

As a last point do you want me to proceed with implementing such a functionality for this plugin? And if so how urgent is it for your project /so I can prioritize it accordingly/?
Otherwise feel free to contribute, ask for further assistance on this topic /or any other issues related to this project/.

Hello thank you for your answer,
Please implement it, but what is the difference between this cache plugin and the PrepareStmt configuration flag from official GORM?

Hi @dennis-dko , no problem, will do so!
The preparestmt flag will cache the queries locally. If the application runs in multiple pods/servers it will not share the cache between instances.

Hi @dennis-dko , no problem, will do so!
The preparestmt flag will cache the queries locally. If the application runs in multiple pods/servers it will not share the cache between instances.

Ah ok, if you have implemented it, please inform me and the cache will be cleared automatically if I use GORM Create, update or delete functions, right? Like FirstOrCreate, Updates()...

Hey @dennis-dko , please have a look at this
https://github.com/go-gorm/caches/pull/11
Examples of the implementation are added in the readme file.
What it does:
Implements cache invalidation upon dispatching Create, Update, or Delete statements.
What it doesn't do:
It does not handle Queries dispatched through gorm.DB.Raw(), it only covers ones done through

gorm.DB.Create()
gorm.DB.Delete()
gorm.DB.Update()
and gorm.DB.Save()
Note that go-gorm/caches/v4 is not yet publish, I will be waiting for your confirmation before I publish it.

Hello,
I found an other error with the identifier for the cache with pointer query args.
My Example of query args to build the identifier:

you can see the string is a pointer variable and the problem is that the pointer value will be changed on same request again like this:

and in the next request with the same query args (values), the string pointer variable value  shows like this:

Before I can try out the invalidate function, this needs to be fixed.

Fixed, and version 4 released


Replace Pants with Rye for package building and publishing

What are the relevant tickets?
N/A
Description (What does it do?)

Configure Rye for managing sub-packages
Restructure directory structures to maintain current package namespaces
Update workflow file to use Rye for dependencies and tests

How can this be tested?

Install Rye following instructions from https://rye.astral.sh/
Use the Rye command to install the dependencies and sub-packages with rye sync
Verify that tests pass using rye test
Build a sub-package using rye build -p <package_name>
Install that package in an empty virtualenv and ensure that the package and all dependencies are installed

Additional Context

I pushed a branch/commit with the fixes I mentioned plus a few other things to https://github.com/mitodl/ol-django/commit/098a8ac14e0fe41fe7d5ef1625aaf010ab3ecee7

1. `rye build` should build all the packages as mentioned in [rye docs](https://rye.astral.sh/guide/commands/publish/) but it gives me

You need to run rye build --all

2. `5` tests are erroring out for me locally, I didn't work on the fix yet but they are related to `cybersource-rest-client-python` package
3. When I run tests for a single package it doesn't find the actual tests from the `tests`dir instead it looks for the tests in the `src` hence finds no test

I wasn't able to reproduce these issues on my end, not sure if Tobias is seeing them too?

4. The `README.md` files in older packages and the newly generated package by rye have different locations:

I think this is ok, because it should be at the root of the package anyway.

I haven't seen the test failures, but it's possible that it's due to the DJANGO_SETTINGS_MODULE being used? I configured it in pyproject.toml to use the testapp.settings.test module https://github.com/mitodl/ol-django/pull/158/files#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711R69
As to the per-package test discovery I did see that. The discovery gets scoped to the package location under src, so that becomes a question of how we want the tests to work. By default running rye test will run all tests that it finds in the whole repository. If we want the tests to be scoped to the sub-package then we would need to relocate the corresponding tests inside the directory path of the sub-package. If that's what we want, then we should maybe do that as a follow-on task from this work.

@arslanashraf7 looking at your test failures I see that the Python version you're executing with is 3.8.13, and the tests in GH Actions are using 3.8.19. Can you check the value of any .python-version file you have locally and try updating it to see if that addresses your test failures?


code review for server side

I am gonna implement server side. so I need to review files under /Server/...

@taxookim What does it means?

that means I need to study the code for server.

taxoo's vacation : 25,26,27,28,29


Styles: Modals spacing update

The modal padding should be updated to match the design specifications.

@alizedebray, closing as the modal will be deprecated and replaced with the dialog element.


Hard to see the time

The relic has so many different colors on it that the time is hard to see regardless of text color - a toggle/color picker for a background color would be awesome - placing the timer above the relic icon with a background would be good too.

Fixed in 0aa2923934675ba9d011dd5eba80a4365e0a7290


Feature/update dependencies

Task/Issue URL:
Tech Design URL:
CC:
Description:
Updating AGP / Gradle / lib dependencies
Steps to test this PR:

Ensure it builds and runs locally for you

Internal references:
Software Engineering Expectations
Technical Design Template

It's build success locally,  I'm wondering why All checks have failed.
Building time has increased like about 20-30 seconds in average respect to the old gradle dependencies.

It's build success locally, I'm wondering why All checks have failed.

Yeah, there is a known ongoing issue with our Bitrise builds at the moment.


Add bad hostname preflight check

Hostname must be a valid DNS name, which is checked as https://github.com/kubernetes/apimachinery/blob/master/pkg/util/validation/validation.go#L115
The situation I have encountered is that my hostname contained underscore which is disallowed and apiserver refused to start.

ci check this


postinstall fails with iojs-1.4.1

I encountered the same error than kevinSuttle here: https://github.com/sass/node-sass/issues/693#issuecomment-76340269
iojs-1.4.1 installed via nvm.
➜  tmp  npm i node-sass
|
><EMAIL_ADDRESS>install /Users/hugues/proj/tmp/node_modules/node-sass
> node scripts/install.js

Can not download file from https://raw.githubusercontent.com/sass/node-sass-binaries/v2.0.1/darwin-x64-iojs-1.4/binding.node

><EMAIL_ADDRESS>postinstall /Users/hugues/proj/tmp/node_modules/node-sass
> node scripts/build.js

module.js:322
    throw err;
          ^
Error: Cannot find module '/Users/hugues/proj/tmp/node_modules/node-sass/node_modules/pangyp/bin/node-gyp'
    at Function.Module._resolveFilename (module.js:320:15)
    at Function.Module._load (module.js:262:25)
    at Function.Module.runMain (module.js:485:10)
    at startup (node.js:112:16)
    at node.js:863:3
Build failed

On my Macos machine there is no homebrew installation of nodejs or iojs; it is important because homebrew does not install the proper patched npm for iojs and one ends-up having to use pangyp as an alternative to node-gyp when that happens.
The stack trace shows that pangyp, a devDependency, was not installed.
So I moved pangyp to a runtime dependency and got past that problem: https://github.com/sass/node-sass/pull/714#issuecomment-76371437
However the sass binary produced remained incompatible.
I have reverted the use of pangyp (https://github.com/hmalphettes/node-sass/commit/5a113952bf517ebb96f50204431b8f2d8844500d) and put back node-gyp and everything is working like a charm.

Thanks for your contribution. I am in the middle of changing this build related stuff in another PR.
There are two issues with this PR:
1 - You are assuming that end user will already have node-gyp globally installed, which might not be the case. This is exactly what we were assuming before I added pangyp as dependency (as io.js appeared at the same time).
2 -

..put back node-gyp and everything is working like a charm.

Yes it seems like it (I am actually surprised, last time I tried building io.js binary, node-gyp just said "no!"). Even though things are looking pretty promising, we should not make any assumption unless this is merged: https://github.com/TooTallNate/node-gyp/pull/564. Till then, pangyp is the build tool of choice.

@am11 thanks for your attention.
I had not realised that node-gyp could ever be not installed when running npm install. I'll research that.
Yes I can't wait for https://github.com/TooTallNate/node-gyp/pull/564 and the upstream https://github.com/iojs/io.js/pull/493 to be resolved.
Should we close this PR then?

Should we close this PR then?

Yes. For now, sticking with pangyp would be make sense until those issues in up streams are sorted out.
We had actually achieved a quite stable build process before io.js days. The aim is to re-achieve that stability. We are also trying to avoid manual building step on end terminals as much as possible (in favour of pre-build binaries).

FYI: https://github.com/sass/node-sass/pull/717.


[SPARK-26682][SQL] Use taskAttemptID instead of attemptNumber for Had…

What changes were proposed in this pull request?
Updates the attempt ID used by FileFormatWriter. Tasks in stage attempts use the same task attempt number and could conflict. Using Spark's task attempt ID guarantees that Hadoop TaskAttemptID instances are unique.
This is a backport of d5a97c1 to the 2.3 branch.
How was this patch tested?
Existing tests. Also validated that we no longer detect this failure case in our logs after deployment.

@rdblue , hi, May I have a question that how to reproduce the attemptnumber conflict?


t

Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:

oops was trying to pull into my own


C API: allow guest to set 'context' variables

Is your feature request related to a problem?
MIP SDK running in Edge in certain cases should not rely on SDK auto-captured device ID. For example, recent developments suggest that Edge may need to apply custom device ID on certain OS other than Windows.
Describe the solution you'd like.
One way to solve this is to allow MIP SDK to override the ID themselves, assuming that MIP SDK somehow knows the device ID./ But currently there's no way to set context fields via C API. This Feature ask is to allow C API guest to specify 'context' / 'semantic context' vars, given that C API guest knows the device ID from somewhere.
Describe alternatives you've considered.
Allow Edge to populate Device ID at LogManager level via SetContext. Assume that C API guest, e.g. MIP SDK - anchors to that same SDK instance, same LogManager level. And subsequently reuses that same Device ID previously populated by Edge. That way there's no need to expose the API.
Additional context.
API already exists for C++, but since C API is very lean - provides only "essential" features, currently there's no way to populate LogManager-level context variables, or get/set semantic context values (that are usually stamped on Part A/B) via C API.
This issue is somewhat related to #290 , as common solution may be possible for both.
See comments in #290

Closing since there was no ask / no renewed interest in this feature.


Braces following a variable declaration with no initializer clause are accessors

Fixes rdar://134877843, a regression introduced recently as part of the fix to https://github.com/swiftlang/swift/issues/76089.

@swift-ci please test


⚠ Bofrost.es has degraded performance

In 52db97d, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1433 ms

Resolved: Bofrost.es performance has improved in 6395ee6 after 9 minutes.


How to download shared files/folders?

How to download shared files/folders?

A work-around I've used is to add the shared folder to your own drive first.

Then you should be able to get a shareable link. Download with:
skicka download https://drive.google.com/open?id=<RestOfYourLinkHere>
I've last ran this in February 2018, so I'm not sure if this is still supported but I would give it a try.

cool hack. Thank you.

Google removed "Add to My Drive" last year, so this no longer works. Now skicka seems to have no way at all to interface with "Shared with me" folders.


build(client-devtools): reclaim @alpha for traditional use

devtools are not a part of framework and may use @alpha for its traditional meaning. This also resolves issues with @alpha referencing @beta APIs, which is not supported for the /legacy pattern. (api export lint policy once enabled will flag that.)

I don't understand how we know whether a package has legacy APIs or not. Is the intention that all alpha APIs get re-tagged as legacy?

I don't understand how we know whether a package has legacy APIs or not. Is the intention that all alpha APIs get re-tagged as legacy?

That is the eventual goal. I think we now have to tooling to make it happen. This was flagged by linting policy and upon review I don't see any legacy style use here. I think these packages were tagged apart from the Loop use effort and then the packages were caught up in the trimming revisions incorrectly. Authors of each package will have to know their use. These could be the only  non-/legacy @alpha uses.

I don't understand how we know whether a package has legacy APIs or not. Is the intention that all alpha APIs get re-tagged as legacy?

That is the eventual goal. I think we now have to tooling to make it happen. This was flagged by linting policy and upon review I don't see any legacy style use here. I think these packages were tagged apart from the Loop use effort and then the packages were caught up in the trimming revisions incorrectly. Authors of each package will have to know their use. These could be the only non-/legacy @alpha uses.

These APIs are not used by Loop, and were not available (publicly) prior to 2.0, so they are safe to update like this.


An unnecessary space is inserted in ${...} by the auto formatter

This is what I get after Ctrl+K+D in VS:
throw Error(`${JSON.stringify(this.value) } cannot be found in ${JSON.stringify(y) }`);

As you see, a space was inserted after JSON.stringify(...). The bug doesn't appear if a plain variable is used: ${x}.

Does this accept PR?

Sure! PR will definitely be appreciated

thanks @SaschaNaz !


Documentation for Upgrading from 1 -> 2

Somrthing missing from the documentation in regards to upgrading from pl1 -> pl2
Your universal JSON files may not work, if that's the case, do this:
in:  source/data/
If your files are named: "_data.jason" and "_listitems.json" , remove the underscore so that they are named "data.jason" and "listitems.json"
Also:

Close #383. This has been added to the "Upgrading" documentation. Thanks @gjhead.


Month 1: Objective 2

Setting Up an AKS Cluster:
Go through the process of creating an AKS cluster in Azure.
Learn about AKS cluster configurations and best practices for initial setup.

Draft of Deployment Steps:

Create a new resource group for the entire year-long project.
Create a Service Principal for the GitHub actions that will be used.
Create a GitHub action to deploy a Bicep configuration for an AKS cluster.


elfutils: fix compiling with llvm

Description of changes
Fixes build errors related to https://github.com/RossComputerGuy/nixpkgs-llvm-ws/runs/27893850441

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

How can you build a package with llvm? IOW: How can I test this?

pkgsLLVM.elfutils

isClang is used for the CFLAGS because it is only an error which occurs in clang. However, the demangler is more of an LLVM specific stdenv issue, theoretically if you were to use the clang but no LLVM stdenv, you would only run into the clang error.


Set the default font type for manim

When I use the Text() function, I write the text in Chinese, but it see that Manim does not support Chinese,I think manim should set the default font is MSYH

Manim supports custom font though:
https://github.com/3b1b/manim/blob/4729e44e057fcc4f02b4d6bdb64c010af4a540b3/manimlib/mobject/svg/text_mobject.py#L82

ok,thanks


Use tabs for curriculum guide page

Just like bus-stop-times page We should add tabs using Components/Tabs.js to curriculum-guide page. So We'll see one semester courses at a time.

hey, can i work on it

hey, can i work on it

Sure ! I hope You do it well !

That's very kind of You ! @kaleemullah786

That's very kind of You! @kaleemullah786

@amirihusayn thanks agian! can you suggest some good projects to contribute, leading to job opportunities

There are a lot of open source projects; But if I had enough time I would contribute on drawio .

Great!

There are a lot of open source projects; But if I had enough time I would contribute on drawio.

@amirihusayn any other suggestions

I'm not sure. See what area You like, then search and find a repository that matches your favorites, abilities and time.

Right


Review expiring cloud certificates and determine next steps

Describe the issue
We acquired a set of certificates last year prior to having our current landing zones/tenancies, etc.  We received notices that these will be expiring in early April.  We have not used these certificates thus far, but we may still have a need these going forward.  We should review our anticipated work related to SSL Termination and make a decision whether to renew some/all of these.
Which Sprint Goal is this issue related to?

Note: 'Milestone' is a ZenHub term that we use synonymously with 'Sprint'.

The 'Milestone' description (created in ZenHub) should clearly list Sprint Goals. This section should indicate which 'goal' this issue is related to.
Additional context
Definition of done
Decision whether we need to renew certs.  If yes, ticket(s) related to renewals. If not, no-op.

Decision not to use (due to capacity).  Make ticket to create new ones later if needed.


#187 run_pca method

resolves #187
Adds methods and tests.

I will branch off here to build pca plotting methods.


Adjust image to container

It would be interesting if the plugin allow to edit an image with a different proportion of the container.
For example, I want the user to upload an square picture, but him uploads a rectangular one. The current implementation doesn't allow to fit the image on the container, cropping the image. Without that limitation, the user would move and zoom the image until it fits the container, and then save it. What do you think?

@javiermarinros @phunksta I've added a minZoom option in 34f79e3850141741b4ad3950e6eeb5834571284e which works as follows:

minZoom decides the minimal zoom level of the image. If set to 'fill', the image has to fill the preview area, i.e. both width and height must not go smaller than the preview area. If set to 'fit', the image can shrink further to fit the preview area, i.e. at least one of its edges must not go smaller than the preview area.

The default value is 'fill', consistent with previous default setting. Feel free to try it out (it's in the current master) and let me know how it works for you. Thanks!

It works pretty well, the last thing needed would be to allow the user to drag the image around the container, in order to allow him center the image.
Thank you!

@javiermarinros Thanks for testing! Did you have to set freeMove to true to move the image around after zooming out? You should be able to achieve what you described above in the screenshot by only setting minZoom to fit. It doesn't allow you to drag the image off the preview area, but you should be able to drag it up and down, if the image is wider than the preview area.

That's true! I didn't tried without freeMove, but it's better if the image cannot go off the preview area. Thank you!

Hey @scottcheng,
Sorry for the delay, I'm back on the project using cropit today.
After some initial 'duh' moments (I'm quite noob with github) I found the new source in the master and tried it out.
Brilliant! what more do I need to say? It works very nicely indeed thank you!
What's more you can now brag that yours is pretty much the only crop plugin that allows you to do this gracefully!
The only possible improvement I could think of is having buttons on the cropit form that allow this mode to be toggled. Is that just a case of changing the options object, or would the form need re-initialising?
Thanks again!

@phunksta Thanks for trying it out!
Regarding toggling the mode, I don't think changing the options object is the best approach. Neither is re-initializing. Ideally there should be an API for it, e.g. $el.cropit('minZoom', 'fit'). Do you have a real world use case for this?

No I think for our purposes what you've added is perfect. I just wasn't clear on how the options work, and you've answered that.
Thanks again!
-------- Original message --------
From: Scott Cheng<EMAIL_ADDRESS>Date: 17/02/2015  5:59 PM  (GMT+00:00)
To: scottcheng/cropit<EMAIL_ADDRESS>Cc: phunksta<EMAIL_ADDRESS>Subject: Re: [cropit] Adjust image to container (#20)
@phunksta Thanks for trying it out!
Regarding toggling the mode, I don't think changing the options object is the best approach. Neither is re-initializing. Ideally there should be an API for it, e.g. $el.cropit('minZoom', 'fit'). Do you have a real world use case for this?
—
Reply to this email directly or view it on GitHub.

@scottcheng when we set minZoom: to 'fit', the image while zoomed out moves freely. The user is not always very genius, so sometimes they move image to one side of the canvas (example#1), how can we force it centered while its smaller than the canvas (example#2)?
example#1 : http://i.imgur.com/UooWarh.jpg
example#2 : http://i.imgur.com/IiRD9HS.jpg

If user crop an image 1 time and then want to crop the the croped image again.it does not show the image.How I can fix it?

@DevotionGeo I fixed with css :
.cropit-preview-image{             float: left;     }

.cropit-preview-image{ float: left; }
Exactly what i was looking for ! Thanks

Is there any way to 'cut' those 'transparent' sides of generated image, if the container is bigger than the image?

how to add flip/flop button along rotation button? any idea, please let me know?


ELK stack for Pachyderm cluster

What is the ask?
Create documentation for how to configure an ELK stack for centralized logging of the pachyderm cluster.
What is the goal / desired outcome?
Complete instructions on how to configure centralized logging of the pachyderm cluster so that information isn't lost due to log rotation.
So that I can accomplish my goal ...
If there is a way to accomplish this today via workaround, what does that require?

Environment?:

Kubernetes version (use kubectl version):
Pachyderm CLI version (use pachctl version):
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s):
OS (e.g. from /etc/os-release):
Others:

What happened?:
What you expected to happen?:
How to reproduce it (as minimally and precisely as possible)?:
Anything else we need to know?:
Environment?:

Kubernetes version (use kubectl version):
Pachyderm CLI version (use pachctl version):
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s):
OS (e.g. from /etc/os-release):
Others:

A starting point is to look at the make logging task
It worked at some point, but I'm not sure its still working.
On Fri, Sep 14, 2018 at 7:41 AM, Nick Harvey<EMAIL_ADDRESS>wrote:

What is the ask?
Create documentation for how to configure an ELK stack for centralized
logging of the pachyderm cluster.
What is the goal / desired outcome?
Complete instructions on how to configure centralized logging of the
pachyderm cluster so that information isn't lost due to log rotation.
So that I can accomplish my goal ...
If there is a way to accomplish this today via workaround, what does that
require?
Environment?:

Kubernetes version (use kubectl version):
Pachyderm CLI version (use pachctl version):
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g.
minikube vs dockerized k8s):
OS (e.g. from /etc/os-release):
Others:

What happened?:
What you expected to happen?:
How to reproduce it (as minimally and precisely as possible)?:
Anything else we need to know?:
Environment?:

Kubernetes version (use kubectl version):
Pachyderm CLI version (use pachctl version):
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g.
minikube vs dockerized k8s):
OS (e.g. from /etc/os-release):
Others:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pachyderm/pachyderm/issues/3152, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkfwTW0Zm0qZ_2bCdfuwvM0Qy2oLl4Hks5ua8AdgaJpZM4WpZkZ
.


Cleanup procfs read/write handlers

Signed-off-by: Adam Rutkowski<EMAIL_ADDRESS>

Can one of the admins verify this patch?


 Update design discussion is here: #733
Update for dynamic items is TBD and tracked by a separate issue: #889

LGTM but seems to have a lot of commits that are already in?


Feature/profast fin model

Add a ProFAST financial model to HOPP custom financial

This PR adds a basic ProFAST model to the HOPP custom financial model so all technologies can be modeled with ProFAST inside HOPP instead of using the PySAM financial models. While an effort has been made to align parameter names with the names in PySAM, I was not able to find corresponding parameters for all the profast parameters in PySAM.Singleowner.
Related issue

Impacted areas of the software

README.md
hopp/simulation/hybrid_simulation.py
hopp/simulation/technologies/dispatch/hybrid_dispatch_builder_solver.py
hopp/simulation/technologies/financial/custom_financial_model.py
tests/hopp/test_custom_financial.py
tests/hopp/utils.py
Additional supporting information

Test results, if applicable

All tests passing.

I'm working on fixing the failed tests

The custom financial model in hopp already had methods for NPV and cash flow calculations. I would like to override those with the calculations from profast, but right now I only set up profast to provide LCOE (both nominal and real). I would like to hear others' thoughts on if we should move all calculations in custom financial to profast. This also raises the question of if we should just make a third financial model for profast so we leave custom alone. That would be a larger lift. Switching custom financial to fully profast would be fairly simple except that many tests would fail.

Thanks @kbrunik! Is this ready to be merged in @jaredthomas68 or are you planning any further modifications? Could you please make issues for any upcoming changes that need to happen that are not part of this PR?

Thanks @kbrunik! Is this ready to be merged in @jaredthomas68 or are you planning any further modifications? Could you please make issues for any upcoming changes that need to happen that are not part of this PR?

I have created or referenced existing issues for all outstanding conversations. I'm going ahead with merging this PR now.


Tutorials aren't sorted despite being documented as having that capability

The doc for tutorials implies that when you use a JSON file, JSDoc should respect the ordering of that file for the tutorials.

You can use a JSON file to provide a title for each tutorial and indicates how the tutorials should be sorted and grouped in the documentation.

However, the default theme/template does not respect that, nor do the tutorial items appear to have an order property.
How can I have the order respected in my theme/template?

I haven't investigated this, but it's possible that it's an easy fix.

Can someone please investigate? If I need it sooner than later, I'll be looking into it and sending a PR.

News on that ?

+1
This would be a very useful feature and the documentation is confusing in this respect. Is there any progress on this? Cheers.

+1
Shaka Player's forked jsdoc sorts tutorials based on the order they appear in the json config file in the tutorial folder, but there appears to be no way to do this in a standard template or plugin without modifying jsdoc.
PR #1198 does this with an explicit order field in the json config file.  This is a little bit of a pain to update for many tutorials, but it's better than nothing.  Ideally, templates could sort either by index in the json or by explicit ordering field.
Any objection to another PR for this?  #1198 was originally posted more than 1.5 years ago, so I'm not feeling too hopeful at the moment.  Can anyone from the jsdoc team comment on this idea?

I just tested naming the tutorial files like "01-chapter-one.md", "02-chapter-two.md", and this ordering seems to stick. Then I just use the JSON file to give the tutorials proper names..

Is anyone still interested in a config option to sort tutorials by their JSON order?

PR #1502

Has this been solved? Or should I be using @torarvid's idea:

I just tested naming the tutorial files like "01-chapter-one.md", "02-chapter-two.md", and this ordering seems to stick. Then I just use the JSON file to give the tutorials proper names..


Great initiative!

Awesome to see some efforts for standardisation.
Looking forward to follow inputs for QC measures (Quality management).

Considered number of regions covered (by the artic protocol)
Genome coverage

I think it would be relevant to tag genomes with the protocol that was used to generate them. E.g. artic network wetlab protocol+ bioinformatics pipeline. As some genomes might have protocol specific issues that need to be taken into account when comparing sequences.
A raw data catalogue for the different protocols would also be super helpful for people setting up and testing bioinformatics pipelines.

These are all great ideas.
We deliberately left QC for the initial, because we wanted to get feedback from the community on what sort of thresholds, quality measures and process controls were actually being used, and what might be the most feasible.  We'd definitely welcome any edits to that section, but should be adding more shortly.
Also plan to expand on bioinformatic tools and workflows considerably, and (again) would welcome contribs.
Consensus sequences in GISAID and NCBI usually have a few protocol notes attached in the metadata, but it might be worthwhile to recommend a more detailed summary of the end to end process, including wetlab/bioinformatics.
Plan to add an index, and links to reference and gather together some example data from different sequencing platforms and protocols for groups that are trying to validate their bioinformatic workflows.


Support risc-v

RISC-V is a good start to get Ethereum nodes running in free hardware, which is a necessary step for a local-first decentralized economy. Lightclients are another necessary step, so these two worlds together are very powerful.
Please support the risc-v architecture in this project.

Next we have to update rustls, which is problematic because surf keeps it pinned to an old version and it is unmaintained:
https://github.com/http-rs/surf/issues/352#issuecomment-1709404352

Next we have to update rustls, which is problematic because surf keeps it pinned to an old version and it is unmaintained: http-rs/surf#352 (comment)

Yeah I guess we should remove it as a dependency and switch to something else in that case

Next we have to update rustls, which is problematic because surf keeps it pinned to an old version and it is unmaintained: http-rs/surf#352 (comment)

https://github.com/ethereum/trin/issues/1446
I moved a PR to move us to reqwest instead of surf, hopefull this helps with the mission

Nice! Thank you @KolbyML. It works.
Next is ethers-providers:
https://github.com/gakonst/ethers-rs/issues/2786

Nice! Thank you @KolbyML. It works.
Next is ethers-providers: gakonst/ethers-rs#2786

We want to remove etheres-rs in Trin and replace it with alloy

That sounds perfect.

@come-maiz This PR https://github.com/ethereum/trin/pull/1456 removes our dependency on ethers-rs, are you able to compile on risc-v yet, or are there still some dependency issues?

thanks @KolbyML!
Compilation almost finishes now. It's getting stuck in librocksdb-sys, I'll see what I can do on my machine to get it to compile.

thanks @KolbyML!
Compilation almost finishes now. It's getting stuck in librocksdb-sys, I'll see what I can do on my machine to get it to compile.

@come-maiz try installing clang and tell me if it works sudo apt install clang

It was installed.


Support install files in lib64

Hello,
Under fedora, lib files are installed in lib64 directory.
This behavior should be managed be the CMakeLists.txt file.
Best regards,
YC

Thanks for the commit, I will test this ASAP.

The build is ready.
The Copr repo: https://copr.fedorainfracloud.org/coprs/ycollet/linuxmao/
The spec file can be found here: https://github.com/ycollet/fedora-spec

Good :+1:
Just for some commentary and clarification about the work done, let me have a few remarks.

not all of ADLplug is Boost licensed. I know I must change the license file at the root to make this point clear. ADLplug is made partially of libraries governed under several GPL-compatible licenses.
On Linux MAO, I have written a list of these licenses. If the package can allow a specification of multiple licenses, it would be better that way. BSL leaves it to be believed that ADLplug is a liberally-licensed program in entirety, but it's not.

I hope to make beta 2 happen in a very short term. I have fixed the project dependencies so curl headers will not be required anymore.

I notice the package summary is wrong as it describes the lmms software.

You can have the OPNplug build in a nearly identical way, it's a name change and a flag to cmake.


[ 12.1.a ] As a user, I want to be able to access the information that the application stores about me , so i know they follow the GDPR.

Acceptance criteria:

[x] add link in top navigation bar, between the link to public timeline and logout. The link should be written as "about me" and should only appear if the user is authenticated.
[x] Make sure the page lists: name, email, links to other users that the logged in user follows and all the logged in users cheeps
[x] In the about me section make it possible to see all information about the user. This could be things like the name, email, links to other users, that the user is following.
[ ] optional Make it possible to download the information that is displayed on the page
[x] #210

References:

lecture_notes

Closed since pull reqeust https://github.com/ITU-BDSA2024-GROUP14/Chirp/issues/210 merged all the remaining functionality into main


Job Listing Card

As seen on the job page section in figma, we need to have cards that can display all relevant job info for a specific Job Posting (Job Lead)
Send a screenshot in your PR and use dummy JSON data to feed into your card since our backend CRUD is not ready yet!

JSON dummy data should be in following format:
{
"id": ObjectId("fe0b3acec32e1fb86cdbe9cd"),
"title": "Lorem",
"pay_per_hour": 72,
"employer_name": "Shopper's Drug Mart",
"email"<EMAIL_ADDRESS>"description": "Lorem",
"type": "Permanent",
"expiry_date": ISODate("2016-04-08T15:06:21.595Z"),
"creation_date": ISODate("2016-04-08T15:06:21.595Z"),
"owner_id": ObjectId("8e83ffe1f1c3638c3fc6653c"),
"creator_id": ObjectId("e18debaeab4ebb39ceea0f3a"),
"timeline":{
    "notes": [
          {
          "text": "Lorem",
          "category": "Lorem"
          },
          {
          "text": "Lorem2",
          "category": "Lorem2"
          }
     ]
}
,
"employer_id": ObjectId("cabca54558fe16d6cca2af67")
}

Source: https://github.com/uoftblueprint/tces/wiki/Database-Schema#job
This would require some joins, if u are wondering why it doesn't look exactly the job collection.


Fix toGamut() types

Allow a ColorSpace id to be specifed for the second param.

As a more lightweight alternative to PRs that you then merge, you can just commit directly and @-mention people in the commit message.


Processed data for SIIMS dataset

Can the Processed data be shared for SIIMS dataset in google drive? I can't access the baidu link here from US. Thank you in advance!

Hi, I've just uploaded the SIMS feature file to Google Drive. Thank you for your interest in our work!

Thank you for your prompt reply. Can I know the kind of features that have been used in the SIMS dataset that has been shared?

Also, can you share how did you extract 33 features from librosa, or is there any related code for that?


Investigate in situ data issues/quality and other sources

Analysis of OpenAQ in situ data for cities provided + other data sources

After our call with the mentors we discussed:

We need to continue investigation into additional data sources - purple air or world aq are options
Storing more metrics such as max, min, avg etc for a given city to indicate range
Maintaining the source of where data is coming from
Developing some screening for very obvious values we would want to exclude like -1000 etc.

aqicn is free but only provides AQI level (and not the same AQI we use currently)
purpleair will cost money and their API isn't the best

Test Analysis
No test needed on this, spoke with @amehta-scottlogic


fix!: export typescript-eslint instead of `@typescript-eslint/eslint-…

…plugin`
It's actually where:

complete shareable configurations are available
configuration helper is available

There's an issue with not allowed reexporting:
ConfigError: Config "neostandard/ts": Key "plugins": Cannot redefine plugin "@typescript-eslint".
    at rethrowConfigError

I put it as a draft until I figure a workaround.

Yeah, this is why I exported the plugin, since that's what's referenced in the neostandard config and that's what needs to be reused, hmm

@jerome-benoit I believe the reason why I used https://github.com/neostandard/neostandard/blob/05f976994852b71e90619b87d21854f95bc8a17f/lib/ts.js#L3-L4
and not:
const { parser, plugin } = require('typescript-eslint')

is that @typescript-eslint/eslint-plugin returns a richly typed plugin, whereas typescript-eslint simply types it as a generic TSESLint.FlatConfig.Plugin, hmm

@jerome-benoit What do you think about this solution?

is that @typescript-eslint/eslint-plugin returns a richly typed plugin, whereas typescript-eslint simply types it as a generic TSESLint.FlatConfig.Plugin, hmm

The issue mentioned is also present in the 0.10 release: https://github.com/jerome-benoit/poolifier/actions/runs/9749052301/job/26905401063. As long as typescript-eslint shareable configurations are used, eslint is erroing because of the plugin name key redefinition: module.exports usage seems to trigger it.
The issue with the  '@typescript-eslint/eslint-plugin' reexport is that it's not really relevant for the shareable configurations: the .configs property does not expose complete reusable configurations.

@jerome-benoit What do you think about this solution?

The dependencies cleanup looks better, but I need to test that branch against poolifier repo to ensure it fix the error, not sure I will be able tonight.
I think a test for reexport use should be planned, at least for typescript-eslint one that seems trigger a code path in eslint checking for plugin name change.

I think a test for reexport use should be planned, at least for typescript-eslint one that seems to trigger a code path in eslint checking for plugin name change.

Added ✔ And I did it in a .mjs file to ensure the mixture of CJS and ESM did not mess with anything

Looks good. Since I can't approve a PR I've opened ... :-)


Change to the new artifactory domain

We created a new domain name for our repository manager (Artifactory) to replace the old Nexus proxy URL (app.camunda.com/nexus). The proxy URL will be removed in the future.
Related to INFRA-3114

LGTM! I'll get this merged!