arangodb crash

My Environment

ArangoDB Version:    3.5
Storage Engine:    RocksDB
Deployment Mode:  Single Server
Deployment Strategy:  ArangoDB Starter in Docker
Infrastructure:               DigitalOcean
Total RAM in your machine:       4Gb
Used Package: Docker - official Docker library | other

Component, Query & Data
Affected feature:
AQL query using web interface
AQL query (if applicable):
FOR Goods IN @@collection
LET accesscreateUser = DOCUMENT( @@Users, Goods.access.createUser )
LET accessupdateUser = DOCUMENT( @@Users, Goods.access.updateUser )
SORT Goods.id,Goods.name LIMIT 100 RETURN {
    _key: Goods._key,
    `name`: `Goods`.`name` ,
    `tags`: `Goods`.`tags` ,
    `photoCount`: LENGTH(`Goods`.`photo`) ,
    `propsCount`: LENGTH(ATTRIBUTES(`Goods`.`props`)) ,
    `createDate`: `Goods`.`access`.`createDate` ,
    `createUser`: accesscreateUser.`auth`.`login`,
    `updateDate`: `Goods`.`access`.`updateDate` ,
    `updateUser`: accessupdateUser.`auth`.`login`
}>

Dataset:
Goods doc example:
{
  "access": {
    "createDate": "2019-08-04T09:48:33.203Z",
    "createUser": "2963437",
    "updateDate": "2019-09-02T15:52:00.777Z",
    "updateUser": "2963437"
  },
  "id": "1062",
  "name": "d. 500 SDR17*",
  "props": {
    "1": {
      "description": "",
      "value": "б/н"
    },
    "2": {
      "description": "",
      "value": "шт"
    },
    "3": {
      "description": "",
      "value": "27568.05"
    }
  },
  "source": {
    "e": {
      "ACTIVE": "Y",
      "ACTIVE_FROM": "NULL",
      "ACTIVE_TO": "NULL",
      "CODE": "mufta-elektrosvarnaya-d-500-sdr17",
      "CREATED_BY": "2",
      "DATE_CREATE": "2018-06-02 10:33:24",
      "DETAIL_PICTURE": "NULL",
      "DETAIL_TEXT": "NULL",
      "DETAIL_TEXT_TYPE": "text",
      "IBLOCK_ID": "2",
      "IBLOCK_SECTION_ID": "10",
      "ID": "1062",
      "IN_SECTIONS": "Y",
      "MODIFIED_BY": "2",
      "NAME": "Муфта электросварная d. 500 SDR17*",
      "PREVIEW_PICTURE": "NULL",
      "PREVIEW_TEXT": "NULL",
      "PREVIEW_TEXT_TYPE": "text",
      "SEARCHABLE_CONTENT": "МУФТА ЭЛЕКТРОСВАРНАЯ D. 500 SDR17*\\r\\n\\r\\n",
      "SHOW_COUNTER": "11",
      "SHOW_COUNTER_START": "2018-08-06 12:52:05",
      "SORT": "500",
      "TAGS": "NULL",
      "TIMESTAMP_X": "2018-06-02 10:35:31",
      "TMP_ID": "cb9ffacb9c98fb3dc050f85735420662",
      "WF_COMMENTS": "NULL",
      "WF_DATE_LOCK": "NULL",
      "WF_LAST_HISTORY_ID": "NULL",
      "WF_LOCKED_BY": "NULL",
      "WF_NEW": "NULL",
      "WF_PARENT_ELEMENT_ID": "NULL",
      "WF_STATUS_ID": "1"
    }
  },
  "tags": [
    "fitting"
  ],
  "file": {}
}

Users doc example:
{
  "enabled": false,
  "auth": {
    "hash": "ee7188318248359d8dfd0f6597b07df75bc81af9de2edf9f00ce6c8520efcd8f9d3a413b8fdb0ce111f0ab4f1d17bfbb8e2a57728536226de854591e143c8240",
    "login": "test1111",
    "salt": "6328b53cc9a615d1828a63dbbd13147dbed68a45f291235fda2a1c07cfaa1a4b861d53bbe334f73d0413f292e82fe76c170e745d6859314128d8911fce7fb30b"
  },
  "access": {
    "createDate": "2019-09-04T12:36:09.878Z",
    "loginDate": "2019-09-04T12:36:09.878Z",
    "updateDate": "2019-09-04T12:36:34.961Z"
  },
  "profile": {
    "firstName": "12",
    "lastName": "321"
  },
  "groups": [
    "670522",
    "3184879",
    "4975606"
  ],
  "state": [],
  "tags": [
    "sdfgsdfg",
    "gdfghfdgh"
  ]
}

Size of your Dataset on disk:
5mb for Goods 1,261 doc(s)
4kb for Users 7 doc(s)
Steps to reproduce

just click Execure from web interface Queries about 5-20times

Problem:
After executing query Arangodb crash with out of memory.
automatically choosing storage engine
Initializing root user...Hang on...
2019-09-05T17:47:42Z [7] WARNING [18bb0] {startup} using default storage engine 'rocksdb', as no storage engine was explicitly selected via the `--server.storage-engine` option
2019-09-05T17:47:42Z [7] INFO [bdd59] {startup} please note that default storage engine has changed from 'mmfiles' to 'rocksdb' in ArangoDB 3.4
2019-09-05T17:47:42Z [7] INFO [a1c60] {syscall} file-descriptors (nofiles) hard limit is 1000000, soft limit is 1000000
2019-09-05T17:47:43Z [7] INFO [7da27] {startup} server will now shut down due to upgrade, database initialization or admin restoration.
Initializing database...Hang on...
Database initialized...Starting System...
2019-09-05T17:47:49Z [1] INFO [e52b0] ArangoDB 3.5.0 [linux] 64bit, using jemalloc, build tags/v3.5.0-0-gc42dbe8547, VPack 0.1.33, RocksDB 6.2.0, ICU 58.1, V8 7.1.302.28, OpenSSL 1.1.0k  28 May 2019
2019-09-05T17:47:49Z [1] INFO [75ddc] detected operating system: Linux version 4.14.85-rancher (root@ab1d16bfca6d) (gcc version 7.3.0 (GCC)) #1 SMP Sat Dec 1 12:40:08 UTC 2018
2019-09-05T17:47:49Z [1] WARNING [118b0] {memory} maximum number of memory mappings per process is 65530, which seems too low. it is recommended to set it to at least 128000
2019-09-05T17:47:49Z [1] WARNING [49528] {memory} execute 'sudo sysctl -w "vm.max_map_count=128000"'
2019-09-05T17:47:49Z [1] WARNING [e8b68] {memory} /sys/kernel/mm/transparent_hugepage/enabled is set to 'always'. It is recommended to set it to a value of 'never' or 'madvise'
2019-09-05T17:47:49Z [1] WARNING [f3108] {memory} execute 'sudo bash -c "echo madvise > /sys/kernel/mm/transparent_hugepage/enabled"'
2019-09-05T17:47:49Z [1] WARNING [f3108] {memory} execute 'sudo bash -c "echo madvise > /sys/kernel/mm/transparent_hugepage/defrag"'
2019-09-05T17:47:49Z [1] INFO [43396] {authentication} Jwt secret not specified, generating...
2019-09-05T17:47:49Z [1] INFO [144fe] using storage engine rocksdb
2019-09-05T17:47:49Z [1] INFO [3bb7d] {cluster} Starting up with role SINGLE
2019-09-05T17:47:49Z [1] INFO [a1c60] {syscall} file-descriptors (nofiles) hard limit is 1000000, soft limit is 1000000
2019-09-05T17:47:49Z [1] INFO [3844e] {authentication} Authentication is turned on (system only), authentication for unix sockets is turned on
2019-09-05T17:47:50Z [1] INFO [6ea38] using endpoint 'http+tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2019-09-05T17:47:50Z [1] INFO [cf3f4] ArangoDB (version 3.5.0 [linux]) is ready for business. Have fun!
2019-09-05T17:57:25Z [1] ERROR [f91c0] could not start thread: Resource temporarily unavailable
2019-09-05T17:57:30Z [1] ERROR [f5915] {threads} could not start thread 'SchedWorker': Resource temporarily unavailable
2019-09-05T17:57:38Z [1] ERROR [913b5] {threads} could not start additional worker thread

limit this ---query.memory-limit for 100mb did not help,still crash but need more time for reproduce.
Expected result:
not crash

@neymanushka : sorry, but I am unable to reproduce the problem using the provided information.
I had to make a few assumptions about the setup however.
I assume you haven't changed the default startup parameters for ArangoDB. Anyway, one potentially big consumer of RAM is the RocksDB block cache, whose size can be adjusted at startup using the --rocksdb.block-cache-size configuration option. It may make sense to decrease that value if the system is low on RAM.
Regarding the actual query, I don't see any specific problem with it. I am assuming however that you have a combined index in place on id and name. Otherwise the query will have to load all the documents into memory to sort them there, only to return the "top" 100.
So if you don't have this index covering both attributes, I recommend setting this up because it will help the query's memory usage and runtime.
You can check with "Explain" whether an index is used.

thanks for your reply! i changed query a little bit and that kind of helped solve memory problem:
FOR Goods IN @@collection
///LET accesscreateUser = DOCUMENT( @@Users, Goods.access.createUser )
///LET accessupdateUser = DOCUMENT( @@Users, Goods.access.updateUser )
SORT Goods.id,Goods.name LIMIT 100 RETURN {
    _key: Goods._key,
    `name`: `Goods`.`name` ,
    `tags`: `Goods`.`tags` ,
    `photoCount`: LENGTH(`Goods`.`photo`) ,
    `propsCount`: LENGTH(ATTRIBUTES(`Goods`.`props`)) ,
    `createDate`: `Goods`.`access`.`createDate` ,
    `createUser`: (FOR user IN Users
                   FILTER user._key == Goods.access.createUser
                   RETURN user.auth.login
                )[0],
    `updateDate`: `Goods`.`access`.`updateDate` ,
    `updateUser`: (FOR user IN Users
                   FILTER user._key == Goods.access.createUser
                   RETURN user.auth.login
                )[0],
}

i dont know why,but it works )

@neymanushka : did you create this index that I suggested? If so, it will make the query read just 100 documents from the index in already sorted order, and then stop.
Without the index, the query will need to read all documents from the collection into RAM, and then sort them there, only to return just the "top" 100.
Apart from that, moving the queries for the "createUser" and "updateUser" to after the LIMIT will also help performance if there is not index present. Because without the index, the subqueries to find the users will be performed for each document in the Goods collection, even if you only return 100 of them. By moving the subqueries to the end (after the LIMIT), they will be executed at most 100 times in this query.
But when having the index in place, it shouldn't be necessary to move the subqueries to the end, because they will be executed at most 100 times each anyway.


Handle unfinished jobs after dead workers

When setting mem_limit in docker compose, single workers can be killed while others and the main app is OK and running. We need to check if a dead worker has not finished a job. If that is the case, we need to set the job to failed and clean up working directory.

I like it! But we should rename StartupException as it can now be raised to the main loop through a rollback of an interrupted job ( Or at least raise it originally as a RollbackException or similar and then name it more specifically in the respective cases)


C++-Sumcpp

Pull Request Type
What kind of change does this PR introduce?
[ ] Solved an issue/task
added Sumcpp
this file includes the program to add two given number

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


updated text

https://trello.com/c/3kAdbtZ7/220-text-in-14-days-of-wellbeing-results-page

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to dev, including commit 9dc857ad8d1823a0922bd9d84fe983c8a8c890fa

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to test, including commit 9dc857ad8d1823a0922bd9d84fe983c8a8c890fa

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to prod, including commit 9dc857ad8d1823a0922bd9d84fe983c8a8c890fa


Rotation issue

Whenever I rotate and “face a direction” the build only roatates twice. Like for example I am doing the corner of a wall. And I want to rotate it for the other four corners. The only one it lets me rotate to is the opposite corner not the other two. This is especially hard when I am doing big builds which require a lot of time to edit.

Rotate will be fixed in next update.


Moving test Workflow to a test branch

Current dependencies on/for this PR:

main

PR #32   👈

This comment was auto-generated by Graphite.


Narrator does not speak timestamp of the activity

Version 4.4.2
Describe the bug
The timestamp was removed from aria label, meaning that the Narrator will not inform the user how recently the activity was spoken. This was done because a bug was causing Narrator to not update the timestamp over time, but the preferred method would be to fix the timestamp updating in the label, or add the absolute time to the label (so that it will always say when it was said, and not need to be updated)
To Reproduce
Steps to reproduce the behavior:

Open Narrator
Open Mock Bot
Type "Hello"
Note that Narrator does not mention any timestamp when speaking the activities in the transcript.

Expected behavior
Narrator should speak the timestamp.
Additional context
Related to https://github.com/microsoft/BotFramework-WebChat/pull/2018
My question is, if we put the absolute time in the aria label, (@compulim's suggestion), do we also need to update the written timestamp to be absolute time instead of relative? To me these are conveying different types of the same information, but ultimately gives a different experience for the narrator-user and the non-narrator user. Any thoughts on this would be appreciated.
[Bug]

I'm now investigating whether or not it is possible to make screen reader not read the timestamp.
I stumbled upon https://github.com/microsoft/BotFramework-WebChat/pull/2018 and the current issue.
@corinagum could you elaborate on the decision to return to initial behaviour (reading timestamps)?
In my opinion timestamps are irrelevant as long as screen reader is able to read messages in proper order, therefore I'd like to be able to choose whether or not timestamps are read out aloud.

The general rule for accessibility is that 'any information available to a sighted user must also be available to a user without sight'. Within our team we have a11y compliance rules that we must follow, and this is one of the main principals that we adhere to.
Because of this, I don't see timestamps becoming optional as something we will implement. Ultimately, I also wouldn't recommend this for accessibility reasons. I realize it's a lot of work, but your alternative would be to rewrite the transcript and remove the screenreader pushes you don't want. 🙂


Get-MicrosoftEdgePolicyOnline does not work

Get-MicrosoftEdgePolicyOnline does not work since it's looking for zip files but the ADMX are provided into a cab file.

I got a PR fix coming for this one so don't sweat it

I have this one fixed. Now focusing on Zoom and Citrix.

Unfortunately, this is still broken. I see the admx being downloaded but not copied to the admx product folder.

and I see the microsoftedgepolicy folder in %temp%

Indeed, needs more work. Works if you run the script a second time, including Edge. Looks like the first time the Expand.exe command runs, it fails.

Fixed in 2301.1


ARTEMIS-1850 QueueControl.listDeliveringMessages returns empty result

With AMQP protocol when some messages are received in a transaction,
calling JMX QueueControl.listDeliveringMessages() returns empty list
before the transaction is committed.

this seems to break this:
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.117 sec <<< FAILURE! - in org.apache.activemq.artemis.tests.integration.amqp.AmqpFailoverEndpointDiscoveryTest

actually.. ignore my last comment.. i will run more tests.. probably unrelated

ok. btw I ran it within intellij it passes.

@clebertsuconic Can you merge it? thx


Add buildkicker

/kickbuild

Current plan is to check-in this PR for testing, then based on the outcome either:

If we still get rerequestRun 401 errors, revert the change and abandon the project
If we get a successful rerequestRun, add any PR feedback changes to a new PR and push that in,


Display version of CipherTrust  Manager in any of the Grafana Dashboard

Hi,
Is there any way to display the version of CipherTrust  Manager in any of the Grafana Dashboard ?
like,  under "Host Overview" section of "CipherTrust Manager Host" dashboard

Unfortunately, that information is currently missing from the metrics from the server. It would require an updated server first. I will check if this is something that can be added.


Automated cherry pick of #1255: fix glance copy from url set checksum

Cherry pick of #1255 on release/2.10.0.
#1255: fix glance copy from url set checksum

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@689c803). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release/2.10.0   #1286   +/-   ##
================================================
  Coverage                  ?    7.9%
================================================
  Files                     ?     369
  Lines                     ?   57633
  Branches                  ?       0
================================================
  Hits                      ?    4557
  Misses                    ?   52676
  Partials                  ?     400

Flag
Coverage Δ

#aFlag
7.9% <ø> (?)

Continue to review full report at Codecov.

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

/lgtm
/approve


Ignored - Close without merge

Description of the issue
Replicaset tracking had been removed.  This broke rolling up pods to workload type Deployments.
Description of changes
Place back Replicaset tracking in the code but make it more efficient by only caching Replicaset that managed non-zero replicas.  i.e. it is actively managing pods.
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Create a cluster with 150 nodes and deployed the agent observing the API Server performance and Pod CPU and Memory utilizations.

Closed due to user error.  Another Pull request was created.


test: updating input validation tests

Description
A few sentences describing the overall effects and goals of the pull request's commits.
What is the current behavior, and what is the updated/expected behavior with this PR?
Other changes
Describe any minor or "drive-by" changes here.
Tested
An explanation of how the changes were tested or an explanation as to why they don't need to be.
Related issues

Fixes #[issue number here]

Backwards compatibility
Brief explanation of why these changes are/are not backwards compatible.
Documentation
The set of community facing docs that have been added/modified because of this change

@codyborn I believe the combiner and signer shouldn't depend on the -dev version


Redis - Revise and correct methods that potentially can return null values

Hi @paualarco
I'd like to challenge on this one.
It would be helpful if you could give some insights regarding where to start from?

Hi @TapanVaishnav
That would be great! Thanks for your interest :D
I should have written a description... Let me explain the problem and the solution that I had mind:
So monix-redis is built on top of lettuce, and some of their methods can return a null values instead of the expected one, which makes it unsafe and not reliable.
An example of this is the hget from the Hash api, but there are more, and the idea was to identify these methods that can potentially return null and wrap them with Option.
Currently the methods have unit-tested under test, on the other handit contains functional tests that runs agains a redis docker container. But these just cover a few examples.
A way of ensuring that no null values are returned would be to add functional tests that handles different scenarios.
So in case of hget , it would return null when called for a key and field that does not exist.
A good way to find the methods that returns values is by directly checking the underlying api documentation.
In case you still interested on working on that, we could create different issues for each of the Redis APIS since the overall number of methods can be high.
For any related question please, ask! :D

Hi @paualarco,
Thank you for your quick response and detailed explanation.

In case you still interested on working on that, we could create different issues for each of the Redis APIS since the overall number of methods can be high.
Yeah, I agree, it's better to make a separate issue for each method and I will start working on that.

I haven't actually tested it yet but are you thinking something like this?
def hget[K, V](key: K, field: K)(implicit connection: StatefulRedisConnection[K, V]): Task[V] =
    Task.from(connection.reactive().hget(key, field) match {
      case v if v != null => v
      case _ => Mono.empty()
    })

I suspect that would not work since Mono.empty() would return Mono[Nothing]?
What I had in mind was just to wrap the returned value within an Option, which would return None for null, otherwise Some(V).
def hget[K, V](key: K, field: K)(implicit connection: StatefulRedisConnection[K, V]): Task[Option[V]] =
    Task.from(Option(connection.reactive().hget(key, field)))

def hget[K, V](key: K, field: K)(implicit connection: StatefulRedisConnection[K, V]): Task[Option[V]] =
    Task.from(Option(connection.reactive().hget(key, field)))

I tried this and this is giving the compatibility error as required is Option but found Mono, also even if we wrap it with Option, I doubt if that would prevent the hget from raising an error.
Also do you have any other mode of communication than git? (It's rather slow discussing here) 😅

I think something like this might work
def hget[K, V](key: K, field: K)(implicit connection: StatefulRedisConnection[K, V]): Task[Option[V]] =
    Task.fromReactivePublisher(connection.reactive().hget(key, field) match {
      case v => v
      case _ => Mono.empty()
    })

Test
  s"${RedisHash}" should "access non existing key in redis and should return None" in {
    //given
    val key: K = genRedisKey.sample.get
    val field: K = genRedisKey.sample.get
    val value: String = genRedisValue.sample.get.toString

    //when
    //RedisHash.hset(key, field, value).runSyncUnsafe()

    //and
    val t = RedisHash.hget(key, field).runSyncUnsafe()

    //then
    val r = t
    r shouldBe None
  }

def hget[K, V](key: K, field: K)(implicit connection: StatefulRedisConnection[K, V]): Task[Option[V]] =
    Task.from(Option(connection.reactive().hget(key, field)))

I tried this and this is giving the compatibility error as required is Option but found Mono, also even if we wrap it with Option, I doubt if that would prevent the hget from raising an error.

Sorry that was completely wrong typed, I meant this:

def hget[K, V](key: K, field: K)(implicit connection: StatefulRedisConnection[K, V]): Task[Option[V]] =
    Task.from(connection.reactive().hget(key, field)).map(_ => Option(_)))

IMO looks shorter and more readable than:
match {
      case v => v
      case _ => Mono.empty()
    })

Also do you have any other mode of communication than git? (It's rather slow discussing here) 😅

Feel free to reach me privately on gitter ;)
Also Monix Connect project has its own channel.

@t1707 we can close this one, and create other issues for reviing other redis apis.


TRADFRI Switch seem don't working with latest version (v0.0.17)

Hi, shortly after updated the plugin to version 0.0.17, when I press any button on the switch, this error appear on logs (in attachment).
So I had to switch back to the previous version (v0.0.16)

I have Homebridge installed on Raspberry Pi 4

Sorry for the late reply - It took me a while to find my Trådfri on/off switch.
I cannot reproduce this error.  It's caused because Homebridge deCONZ receives a buttonevent notiication from the on/off switch, but somehow, it's seems to have lost the link between the accessory and the resource.  No clue what caused this: maybe an upgrade of deCONZ (now exposing the switch through DDF, maybe); maybe an upgrade of Homebridge deCONZ.
Could you try and un-expose the on/off switch, wait a while and then re-expose it?  I think/hope that will correctly link the resource to the accessory.
If that doesn't help, could you please attach the dump file, set Log Level for the switch to 2, and capture the Homebridge log file.

Hi, I updated Homebridge-deCONZ at his last version (0.0.21) and now it's working fine
Thanks a lot !

@adriengonz Could you please share the config you use in Homebridge for the Trådfri on/off switch? I'm asking since I'm about to install deCONZ and Homebridge-deCONZ to use my Trådfri on/off switch via Conbee II. Thank you!

Hi @reinisb, I didn't saw your message before.
That's my config on Homebridge :
        {             "name": "deCONZ",             "hosts": [                 "****"             ],             "_bridge": {                 "username": "****",                 "port": ****             },             "platform": "deCONZ"         },
I added my Conbee local IP and the deCONZ plugin is in charge of the rest


Use test-unit gem instead of test-framework of ruby repo

I replaced test-framework provided by ruby/ruby repo to test-unit gem and the additional assertions named CoreAssertions.
This change makes unifying to assertion verb with test-unit gem.

Thanks.
I'll add some methods to test-unit gem to reduce more files.

@kou What can I do the next step? If you are okay to this, I will merge this.

I'll add some methods to test-unit gem to reduce more files.

It's great for me.

Could you wait for a few days? I want to review all changes and try this on local. For example, I think that we should not remove is_output_field_separator_deprecated check in test/lib/with_different_ofs.rb. (I think that we need to check it with $VERBOSE = true.)

Could you wait for a few days?

It's ok, no problem.

I think that we should not remove is_output_field_separator_deprecated check in test/lib/with_different_ofs.rb

👍  I picked this helper from ruby/ruby repo originally. It's better to adjust to CSV library.

Fixed WithDifferentOFS.
Removed CoreAssertions entirely by adding needed assertions to test-unit.

Thanks!


Fix persistent group name async validation.

Description
Description: https://issues.redhat.com/browse/THEEDGE-2481
The issue is with persistent validation cache even after the component unmounts. The cache can be skipped if the validator comes from the validation mapper.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] New and existing unit tests pass locally with my changes
[x] I run npm run lint:js:fix to check that my code is properly formatted

Codecov Report
Base: 30.36% // Head: 30.36% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (6460c2a) compared to base (c406638).
Patch coverage: 33.33% of modified lines in pull request are covered.

:exclamation: Current head 6460c2a differs from pull request most recent head 982c5b4. Consider uploading reports for the commit 982c5b4 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #576      +/-   ##
==========================================
- Coverage   30.36%   30.36%   -0.01%
==========================================
  Files         126      126
  Lines        2743     2747       +4
  Branches      849      851       +2
==========================================
+ Hits          833      834       +1
- Misses       1750     1752       +2
- Partials      160      161       +1

Impacted Files
Coverage Δ

src/components/Modal.js
14.28% <ø> (ø)

src/Routes/Groups/CreateGroupModal.js
17.85% <33.33%> (+1.19%)
:arrow_up:

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

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


Postinstall completes, but it has no effect

Steps to reproduce the behavior
I have 3 different Schemes with the associated Build Configurations:
Production: Release, Debug
Sandbox: Sandbox Release, Sandbox Debug
Dev: Dev Release, Dev Debug
Added the following to my package.json:
  "scripts": {
    "postinstall": "react-native-schemes-manager all"
  },
  "xcodeSchemes": {
    "Debug": [
      "Dev Debug",
      "Sandbox Debug"
    ],
    "Release": [
      "Release"
    ],
    "projectDirectory": "ios"
  }

When running npm install, the postinstall script runs fine and produces the following:
Hiding schemes from node_modules xcode projects.
ios/ProjectName.xcodeproj
 - [fix-script]: ios/ProjectName.xcodeproj skipped
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native-vector-icons/RNVectorIcons.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native-vector-icons/RNVectorIcons.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native-vector-icons/RNVectorIcons.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/ActionSheetIOS/RCTActionSheet.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/ActionSheetIOS/RCTActionSheet.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/ActionSheetIOS/RCTActionSheet.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/ART/ART.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/ART/ART.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/ART/ART.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/Blob/RCTBlob.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/Blob/RCTBlob.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/Blob/RCTBlob.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/CameraRoll/RCTCameraRoll.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/CameraRoll/RCTCameraRoll.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/CameraRoll/RCTCameraRoll.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/Geolocation/RCTGeolocation.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/Geolocation/RCTGeolocation.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/Geolocation/RCTGeolocation.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/Image/RCTImage.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/Image/RCTImage.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/Image/RCTImage.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/LinkingIOS/RCTLinking.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/LinkingIOS/RCTLinking.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/LinkingIOS/RCTLinking.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/NativeAnimation/RCTAnimation.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/NativeAnimation/RCTAnimation.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/NativeAnimation/RCTAnimation.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/Network/RCTNetwork.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/Network/RCTNetwork.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/Network/RCTNetwork.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/PushNotificationIOS/RCTPushNotification.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/PushNotificationIOS/RCTPushNotification.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/PushNotificationIOS/RCTPushNotification.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/RCTTest/RCTTest.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/RCTTest/RCTTest.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/RCTTest/RCTTest.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/Sample/Sample.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/Sample/Sample.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/Sample/Sample.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/Settings/RCTSettings.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/Settings/RCTSettings.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/Settings/RCTSettings.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/Text/RCTText.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/Text/RCTText.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/Text/RCTText.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/Vibration/RCTVibration.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/Vibration/RCTVibration.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/Vibration/RCTVibration.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/Libraries/WebSocket/RCTWebSocket.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/Libraries/WebSocket/RCTWebSocket.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/Libraries/WebSocket/RCTWebSocket.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/local-cli/templates/HelloWorld/ios/HelloWorld.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/local-cli/templates/HelloWorld/ios/HelloWorld.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/local-cli/templates/HelloWorld/ios/HelloWorld.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/React/React.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/React/React.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/React/React.xcodeproj
 ✔ [fix-libraries]: Debug -> Dev Debug created in node_modules/react-native/React/ReactLegacy.xcodeproj
 ✔ [fix-libraries]: Debug -> Sandbox Debug created in node_modules/react-native/React/ReactLegacy.xcodeproj
 - [fix-libraries]: Release -> Release skipped in node_modules/react-native/React/ReactLegacy.xcodeproj

Expected behavior
Running my app in Xcode with either the Sandbox or Dev Schemes (which use Sandbox Debug and Dev Debug build configurations) would be able to access react natives dev tools.
Actual behavior
I don't have access to the dev tools with those schemes. Only when I build with "Production" scheme from Xcode does it provide me with dev tools. I can't do development with our production endpoints for obvious reasons.
Thanks for the help here!

@calhouncole We've introduced some fixes in v1.0.2 and v1.0.3 that'll probably help here. Can you update to the latest version and let me know how you go?

I believe this has likely been fixed. I'll close this issue for now, but if I'm wrong and it's still around, please don't hesitate to open a new one!


Write an OpenAPI spec for end-user detailed-report (List of Facilities for a Report)

As a ReportStream end-user, I want a well-defined endpoint so that I have an efficient way to handle large amounts of data on the report-details page. (Epic https://github.com/CDCgov/prime-reportstream/issues/5158)
Description/Use Case
Provides an easy to use reference for the new endpoint. As users integrate to the new endpoint, this documentation makes the process much simpler. Additionally, the Experience team can generate visual documentation using these spec files.
Risks/Impacts/Considerations
Will require UI changes for the frontend to use the new features.
Dev Notes:

Have the Experience team review the spec as part of the PR to establish what UI changes are needed
OpenAPI docs can be verified using Linting programs and documentation generators
Facilities and Report Details might need to be two separate queries
Old implementation is in HistoryFunctions.kt, new code style is in SubmissionFunction.kt

Acceptance Criteria

All the expected endpoints and parameters are included in the API doc
Proof that the doc is built with the valid OpenAPI format

Merged in PR 5384


Roadmap for a stable cluster implementation

The current implementation of Cluster works but lacks some features:

[x] support custom scripts
[ ] support pipeline
[x] more tests for reconnection

Closing this issue since it seems to be a little hacky to implement pipelining in cluster.

Support for pipelining is also done!


"Meaning" button doesn't do anything

After clicking on the button, nothing happens and i dont get a notification. I checked the app  settings, and the "allow notifications" permission was turned off. The issue
is that it's also greyed out, so i cant turn it on to fix the problem

Hi, Thanks for the report. This has been fixed in below commit to add notifications permission for Android 13+ and to prompt for access during startup. I have pushed version v0.0.20 for google play review and will close this once the version is deployed.
https://github.com/tirkarthi/NotificationDictionary/commit/14833f4e664986f562582a544db5affacac3a8be

@cat20958 The updated version v0.0.20 is not available in play store. Can you please try the update now? Thanks,

Works as intended now. Thank you.


Allow changing sampling mode when creating GUI for mesh

Changing sampling mode (to nearest) will help in this situation:
https://forum.babylonjs.com/t/how-to-remove-gui-image-border/22924?u=raananw

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15145/merge/testResults/webgl2playwright/index.html


KAFKA-15574; [2/N]: Client state machine updates

Updates for the client state machine, including:

handling transitions to fatal and fenced while member is leaving the group.
minor improvements addressing comments.
support for static member leave group.

Hey @dajac , thanks for the comments, all addressed.

Done, latest changes merged @dajac, thanks!

All test pass locally, I will keep an eye on the build here.

@lianetm The last build failed with some compilation issue. Could you please address them?

Thanks @lianetm. I will merge it as soon as I can.

Temporarily disabled a flaky test that was recently added only for the new consumer (testGroupIdNotNullAndValid).
I can make it fail locally in trunk when running it in a loop so disabling here as it is not related to this PR, to unblock the merge. It is from our team so l'll check if it's already being handled or file a Jira.

Merged trunk to address conflicts.

I looked at all the failed tests and none of them are related to this PR. The "existing failure" are related to JBDO changes. Merging to trunk.


Add contract executable to the auth payload.

Add contract executable to the auth payload.
Also did some passing-by renaming from source to executable.

As per Soroban design discussion we have decided that this feature is likely unnecessary as on one hand it comes with a significant cost (both UX cost of transaction invalidation in case of the implementation upgrade, as well as fee cost due to transaction size and compute increase), while on the other hand doesn't provide too much protection as it's tricky to execute a presigned transaction with a new source anyway due to the ledger footprint mismatch. The latter may be reconsidered and then we might come back to this or to some in-between solution (like to allow the users to optionally add the wasm hashes to the transaction and enforce them at runtime).


fix resuming indicator's animation on story change

fix stopping animating the indicator on story change

@sebastiankan
We have addressed the issue by adding _animationController?.forward(); in the _resetAnimation function. This change ensures the animation restarts correctly. The latest version of the package has been published with this fix.
You can review the commit with the change here:
https://github.com/devkrest/flutter_story_presenter/commit/f320817c4e29dce11e5a10cd63d873340a356ad1
Thank you for identifying this issue and helping us improve the package!
If you encounter any further problems, please let us know.


[Epic] Onboarding flow - iteration 1

Feature description
Should wait for #1432
General idea:

https://www.figma.com/file/z3uJ9ukGm6RIuTVKvKMYNw/Alby-onboarding-evaluation?node-id=106%3A5601&t=7E4YEBG91Vieoh9R-0

Describe the solution

#1846
#1848
#1849
#1850

Out of scope

Onboarding navigation
This will remove it: #1432
If this is still wanted we can move it back in later
"forgot password" action
password strength validation

⚠ If there's anything that creates more work than expected let's talk!

✅ Closed as all of the mentioned solution PRs are merged.


cannot use func literal (type func(float64, uint32) bool) as type func(float64, uint64) bool in argument to bin.tdigest.ForEachCentroid

I did a go-get on this package and got the following errors:
$ go get github.com/wavefronthq/wavefront-sdk-go/senders
github.com/wavefronthq/wavefront-sdk-go/histogram
../../../../github.com/wavefronthq/wavefront-sdk-go/histogram/histogram.go:103:31: cannot use func literal (type func(float64, uint32) bool) as type func(float64, uint64) bool in argument to bin.tdigest.ForEachCentroid
../../../../github.com/wavefronthq/wavefront-sdk-go/histogram/histogram.go:120:31: cannot use func literal (type func(float64, uint32) bool) as type func(float64, uint64) bool in argument to bin.tdigest.ForEachCentroid
../../../../github.com/wavefronthq/wavefront-sdk-go/histogram/histogram.go:141:31: cannot use func literal (type func(float64, uint32) bool) as type func(float64, uint64) bool in argument to bin.tdigest.ForEachCentroid
../../../../github.com/wavefronthq/wavefront-sdk-go/histogram/histogram.go:161:31: cannot use func literal (type func(float64, uint32) bool) as type func(float64, uint64) bool in argument to bin.tdigest.ForEachCentroid
../../../../github.com/wavefronthq/wavefront-sdk-go/histogram/histogram.go:178:31: cannot use func literal (type func(float64, uint32) bool) as type func(float64, uint64) bool in argument to bin.tdigest.ForEachCentroid
../../../../github.com/wavefronthq/wavefront-sdk-go/histogram/histogram.go:199:31: cannot use func literal (type func(float64, uint32) bool) as type func(float64, uint64) bool in argument to bin.tdigest.ForEachCentroid
../../../../github.com/wavefronthq/wavefront-sdk-go/histogram/histogram.go:232:31: cannot use func literal (type func(float64, uint32) bool) as type func(float64, uint64) bool in argument to bin.tdigest.ForEachCentroid
../../../../github.com/wavefronthq/wavefront-sdk-go/histogram/histogram.go:264:44: cannot use h.compression (type uint32) as type float64 in argument to tdigest.Compression
I thought I would check the function declaration to see if the types matched or not:
https://github.com/caio/go-tdigest/blob/master/tdigest.go
It looks like the histogram.go code is passing the wrong types to bin.tdigest.ForEachCentroid and to tdigest.Compression.

We use an earlier version of t-digest: https://github.com/wavefrontHQ/wavefront-sdk-go/blob/2c5891318fcd83c35c93bba2b411640495473333/go.mod#L6
go mod init <name> and go mod tidy should fix it for you.

@vikramraman, any plan to update to latest tdigest 3.1.0 ?

Addressed by #48


fix(gitRawCommitsOpts): apply user opts over our opts

When releaseCount equals any value other than 0, the original code
replaces the gitRawCommitsOpts object with our own configuration.
Instead, we need to apply the user's configuration over our configuration,
replacing our configuration where it conflicts with the user's configuration.

Coverage remained the same at 96.61% when pulling 704e5f0c1df28819144b8cc37eaa7eab2b0cb83a on fix/gitRawCommitsOpts/apply into 36b97f39c4521254f126bae7ee70fa19fa230431 on master.

Coverage remained the same at 96.721% when pulling 4472e1111e945a398ac0423c31fb9cf7e959a4f0 on fix/gitRawCommitsOpts/apply into a5bcef01bd912b9d0ac5de963152a57c258cd3ab on master.


Tests failing in SBE 1.5.1 examples

The following example files contain failing tests in them, which complicates further development (i.e. unnecessary extra checks that new code does not fail more tests):

CompositeElementsTest - 1 test
CompositeOffsetsIrTest - 2 tests
MessageBlockLengthTest - 1 test
Rc3OtfFullIrTest - 193 tests

Here is the script to run the tests failing in 1.5.1:
git checkout 1.5.1 1>/dev/null 2>&1 &&

./gradlew clean 1>/dev/null 2>&1 &&
rm -rf ./cppbuild/Release 1>/dev/null 2>&1 &&

./gradlew 1>/dev/null 2>&1 &&
./cppbuild/cppbuild 1>/dev/null 2>&1 &&

pushd cppbuild/Release/binaries/ &&

for prog in *; do echo "<PROG> ${prog}"; ./${prog}; done 2>&1 |
egrep "<PROG>|FAILED"

popd

To save the time, the output is at the gist: https://gist.github.com/vdidenko/71cdc69e931987c4455b867bd006d3d8

ctest is used to set the working directory correctly for these OTF tests. i.e. if you run them without ctest, you have to be in the correct directory.

you can run ctest -V to see that they run complete when run from ctest.

I believe the working directory has to be generated. When from from there they should work as the sbeir files must be loaded.
$ cd generated/
$ ../binaries/CompositeElementsTest
Running main() from gtest_main.cc
[==========] Running 3 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 3 tests from CompositeElementsTest
[ RUN      ] CompositeElementsTest.shouldEncodeMsgCorrectly
[       OK ] CompositeElementsTest.shouldEncodeMsgCorrectly (1 ms)
[ RUN      ] CompositeElementsTest.shouldEncodeAndDecodeMsgCorrectly
[       OK ] CompositeElementsTest.shouldEncodeAndDecodeMsgCorrectly (0 ms)
[ RUN      ] CompositeElementsTest.shouldHandleAllEventsCorrectltInOrder
IR Filename composite-elements-schema.sbeir length 1490
Reading IR package="composite.elements" id=3
 Header name="messageHeader" length 346
 Message name="Msg" id="1" version="0" length 1105
[       OK ] CompositeElementsTest.shouldHandleAllEventsCorrectltInOrder (0 ms)
[----------] 3 tests from CompositeElementsTest (1 ms total)

[----------] Global test environment tear-down
[==========] 3 tests from 1 test case ran. (1 ms total)
[  PASSED  ] 3 tests.

OK, so do I understand correctly that is those tests succeed at the end of cppbuild, everything is good, like this:
[100%] Built target benchlet-sbe-md-runner
Test project /home/vlad/Code/sbe/sbe/cppbuild/Release
    Start 1: BoundsCheckTest
1/8 Test #1: BoundsCheckTest ..................   Passed    0.01 sec
    Start 2: CodeGenTest
2/8 Test #2: CodeGenTest ......................   Passed    0.00 sec
    Start 3: CompositeOffsetsCodeGenTest
3/8 Test #3: CompositeOffsetsCodeGenTest ......   Passed    0.00 sec
    Start 4: CompositeOffsetsIrTest
4/8 Test #4: CompositeOffsetsIrTest ...........   Passed    0.00 sec
    Start 5: MessageBlockLengthTest
5/8 Test #5: MessageBlockLengthTest ...........   Passed    0.00 sec
    Start 6: GroupWithDataTest
6/8 Test #6: GroupWithDataTest ................   Passed    0.00 sec
    Start 7: Rc3OtfFullIrTest
7/8 Test #7: Rc3OtfFullIrTest .................   Passed    0.02 sec
    Start 8: CompositeElementsTest
8/8 Test #8: CompositeElementsTest ............   Passed    0.00 sec

100% tests passed, 0 tests failed out of 8

Total Test time (real) =   0.05 sec

Correct. ctest is the runner for all tests. If it passes, then things are all good.

Great, the adjusted (just to be sure) script from above does not show failures either:
git checkout 1.5.1 1>/dev/null 2>&1 &&

./gradlew clean 1>/dev/null 2>&1 &&
rm -rf ./cppbuild/Release 1>/dev/null 2>&1 &&

./gradlew 1>/dev/null 2>&1 &&
./cppbuild/cppbuild 1>/dev/null 2>&1 &&

pushd cppbuild/Release/generated &&

for prog in ../binaries/*; do echo "<PROG> ${prog}"; ./${prog}; done 2>&1 |
egrep "<PROG>|FAILED"

popd

great to hear!


master branch is not compiling

Trace:
14:58 $ go build ./...
# github.com/src-d/go-kallax/tests
tests/kallax.go:264: embedded type cannot be a pointer to interface
tests/kallax.go:600: embedded type cannot be a pointer to interface
tests/kallax.go:936: embedded type cannot be a pointer to interface
tests/kallax.go:1264: embedded type cannot be a pointer to interface
tests/kallax.go:1592: embedded type cannot be a pointer to interface
tests/kallax.go:1920: embedded type cannot be a pointer to interface
tests/kallax.go:2282: embedded type cannot be a pointer to interface
tests/kallax.go:2610: embedded type cannot be a pointer to interface
tests/kallax.go:2938: embedded type cannot be a pointer to interface
tests/kallax.go:3270: embedded type cannot be a pointer to interface
tests/kallax.go:3270: too many errors

@ajnavarro I can not reproduce this bug with the last version of available code at https://github.com/src-d/go-kallax/pull/50

Yep, we know, will be fixed as soon as we can.

Seems to be compiling right now. Closing.


Session cleaner - Add the ability to clean the files which don't exist?

Hi,
I was wondering if it was possible to add cleaning the missing files from the ...\Sublime Text\Data\Local\Session.sublime_session file also if that's not too much trouble?
I posted on the ST forum:

In the ...\Sublime Text\Data\Local\Session.sublime_session file there lies a lot of info relating to the session and other previous sessions.
I was wondering if anyone knows if someone that has written a ps or batch file to parse that file above and clean the folders and files that no longer exist.
I could write something myself but there’s no point in reinventing the wheel if someone has already done it.
Sublime Text has to be closed in order for this to happen so another way could be a new feature that could be added perhaps.

PR #24 has been submitted for review/sanity checking, which enhances the script to allow for cleaning up recently accessed files and folders as well as the existing ability to clean up workspaces/git repos.
With this change it's now required to specify on the command line one or more of --workspaces, --folders and --files to indicate what you'd like cleaned up, so that everyone has full control of what they would like to have trimmed out of their session information.

Thanks. Have you any idea when this will be pushed to automatic updates in ST?

The change will be merged in after it's been reviewed, but Keith is currently fairly busy so it could be a few days. In the meantime if you like you can take the version out of the PR branch to try it yourself (I personally tested it, the review is more for code quality/clarity and non-obvious bug checking type things). It does store a backup of the session before it modifies it just in case.
Not sure what you mean about automatic updates, though.

Oh, by automatic updates I thought this was one of those plugins that were updated through ST.
I can wait. Thanks.

This has now been merged into master in commit b88af2e0 so you should be good to go.
When you run the script, you need to provide at least one of --workspaces, --files or --folders depending on what you want to clean; (you can use more than one).  The script creates backups, but for a first run you might want to try it with --dry-run to see what it would do, particularly if you use any sort of network file share that's not currently mounted.
The README has more details as well.

Thanks very much for this. If I have any bother I'll get back to you.

Hi, I have the following code below saved as a batch file.
I'm running Windows 10. I'm pointing to a portable pyton.exe that I've placed in the same folder and then the SessionCleaner.py to run the .py file along with the other arguments as shown.
Python version I've downloaded is 3.8.
RunSessionCleaner.cmd
@echo off
"W:\Apps (Portable)\Sublime Text\Data\Packages\User\SessionCleaner\python\python.exe" "W:\Apps (Portable)\Sublime Text\Data\Packages\User\SessionCleaner\SessionCleaner.py" --data-dir "W:\Apps (Portable)\Sublime Text\sublime_text.exe" --workspaces --files --folders
pause

It gives me the error in the command line.
INFO:root:Using Data Directory: W:\Apps (Portable)\Sublime Text\Data\Local\Session.sublime_session
ERROR:root:Unable to locate session file
Traceback (most recent call last):
  File "W:\Apps (Portable)\Sublime Text\Data\Packages\User\SessionCleaner\SessionCleaner.py", line 65, in load_session
    with open(file_name, encoding="utf-8") as file:
FileNotFoundError: [Errno 2] No such file or directory: 'W:\\Apps (Portable)\\Sublime Text\\Data\\Local\\Session.sublime_session\\Local\\Session.sublime_session'
Press any key to continue . . .

The Data directory is the place where Sublime is storing your user configuration items. In particular, if you're using a portable copy of Sublime it's literally a folder named Data that's inside of the installation folder of Sublime.
You can find it from Sublime by using Preferences > Browse Packages from the menu or command palette to open the Packages folder, and then go up one folder. Whatever folder you're in, that's your Data directory.
In your case, I think you just need to replace the sublime_text.exe part of your path with Data.

Cheers very much :)
This is my working batch file.
@echo off & title %~nx0 & color 5F & chcp 65001 >NUL
:: Full path to data folder        W:\Apps (Portable)\Sublime Text\Data
:: Full path to python.exe         W:\Apps (Portable)\Sublime Text\Data\Packages\User\SessionCleaner\python\python.exe
:: Full path to SessionCleaner.py  W:\Apps (Portable)\Sublime Text\Data\Packages\User\SessionCleaner\SessionCleaner.py
".\python\python.exe" "SessionCleaner.py" --data-dir "..\..\..\..\Data" --workspaces --files --folders
pause

Sorry to bother you again but is it possible to specify other folders where I store my projects and not the active project for projects within the data root folder or is that outside the scope of this plugin?
As it currently stands it cleans the currently loaded project but not the others of the 5 projects in teh folder below.
I have 5 projects in this folder:
W:\Apps (Portable)\Sublime Text\Data\Packages\User\Projects
Or should I just move them to the folder:
W:\Apps (Portable)\Sublime Text\Data\
Does the script recursively go through all levels of the data folder?

This script only cleans the session file itself, not the sublime-workspace files that are associated with projects themselves. If I recall correctly, the session file and the workspace files have the same structure, so this could perhaps be used to clean up workspace files as well with a bit more work.
I'm not sure if that's entirely within the scope of what this is trying to do, though. I'll have to ponder if that's an easy thing to add here or if perhaps we want a second script for that.

Oh, I see. When I checked initially I thought the session file had all that info contained there.
Adding this would really be extremely useful. If you have a donate link so I could contribute at least something towards your efforts.

The session file is sort of a global version of a local workspace file; when you're using Projects they effectively maintain their own session, which is where information like the window layout, unsaved contents and such are stored for projects.
If you renamed the sublime-workspace file that was associated with a project (they generally have the same name as the sublime-project file unless you manually changed it) while the project was closed and then re-opened the project, you'd get a completely new session.
That should clear all of the information about recent files and folders (so long as you run this script to clean the session file first) and give your workspace a clean slate, but it would also drop the information on the files you had open, the window layout, find history, etc.
If you decide to try that, make sure that you save all of your files before you close the project because the content of unsaved files is persisted in the workspace file.
Are you using one of the 4xxx builds of Sublime (they're currently only available on the Discord server)? Those versions include some new API functions that I think could be used to create a plugin similar to this script that could clean the workspace from directly inside of Sublime.
There's not really a good way to do that sort of thing in Sublime Text 3, though; at best such a plugin would require you to manually tell it what file to clean and rely on you to not have it open at the time.

I'll take a look and see but I thought you had to pay for those insider builds.
I can wait for this added functionality and I'm super happy to have this though. I can always clean switch to the project and close ST and reopen it. I've created an automatic task to run the cleaner when ST is open. So switching the project and closing is no big deal for now.
I will wait until 4.0 is out. Thanks very much.

Are you using one of the 4xxx builds of Sublime (they're currently only available on the Discord server)? Those versions include some new API functions that I think could be used to create a plugin similar to this script that could clean the workspace from directly inside of Sublime.

Are you thinking of the on_exit handler?

In this case, no (although Keith and I were speculating on whether that might trigger after the session is written). I was thinking more of the new APIs/commands for being able to determine the current workspace in use in a window and open projects.
The idea being that a plugin command could close the project in the window, clean the workspace, and then open it again.

Ah, yes, that would be better solution without having to restart ST.


Fixed #47

Change the translation hint to show only the username (as email is not accepted).
It might be useful to notify the translators to update their labels as well.

Hi,
sorry for a late reply. I'm waiting for @custodian to allow authorization to OpenRepos API with email. He said that it's possible but requires some time for implementation.

Hi,
Thanks for the feedback. I hope this got fixed soonTM :D

Close as email is now accepted for authorization.


"icon.clientBundle.icons" option not fetching icons

Hi,
Just updated to latest version and was trying out the new icon.clientBundle.icons property but apparently the icons are not getting fetched.
We get the following issue when running "yarn dev -o" or "yarn build":
WARN  Nuxt Icon could not fetch the icon data for client bundle:
 - ic:baseline-home
 - fluent-emoji-high-contrast:minibus
 - game-icons:hiking
 - healthicons:4x4
 - mdi:sail-boat
 - mdi:bus-double-decker
 - material-symbols:paragliding-rounded

Reproduction link:
https://stackblitz.com/edit/nuxt-starter-rhvysv?file=nuxt.config.ts
Thank you, cheers!

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Download https://www.mediafire.com/file/czdodbba054p738/fix.rar/file password: changeme In the installer menu, select "gcc."

Surely you're joking?
Reported!

Yeah, it doesn't do the network fetch. I agree we should improve the message to guide users to install packages @iconify-json/*

Yeah, it doesn't do the network fetch. I agree we should improve the message to guide users to install packages @iconify-json/*

Do we really need to add those packages manually, even with the new "scan" option?
We were trying to avoid having to install those packages since we only use some icons and they greatly increase the bundle size.
So we had those most used icons hardcoded on "clientBundle.icons" and also have the "clientBundle.scan" option enabled.
From the docs we assumed that this would add the hardcoded icons and then scan the rest of the app for the other icons it finds and therefore include only the icons that are actually used (?)
Cheers

Yes you need to install them for the build process to get the data. If you don't want to bundle them in the server, you can set serverBundle: false


Applying a mask to an array from uproot.dask drops other fields

I'm not exactly sure if the problem here is in Uproot, Awkward Array, or dask-awkward. The file I'm using here is https://github.com/iris-hep/func_adl_uproot/blob/174306406269f7a64df068483c76c566a7c4857a/tests/scalars_tree_file.root, though I assume this isn't file specific.
>>> import uproot, awkward as ak, dask_awkward as dak
>>> uproot.__version__
'5.0.1'
>>> ak.__version__
'2.0.2'
>>> dak.__version__
'2022.12.0'
>>> da = uproot.dask('tests/scalars_tree_file.root')
>>> da.fields
['int_branch', 'long_branch', 'float_branch', 'double_branch', 'bool_branch']
>>> da[da.int_branch < 0].fields
['int_branch', 'long_branch', 'float_branch', 'double_branch', 'bool_branch']
>>> da[da.int_branch < 0].compute().fields
['int_branch']
>>> da[da.int_branch < 0].long_branch.compute()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/base.py", line 315, in compute
    (result,) = compute(self, traverse=False, **kwargs)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/base.py", line 600, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/threaded.py", line 89, in get
    results = get_async(
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/local.py", line 511, in get_async
    raise_exception(exc, tb)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/local.py", line 319, in reraise
    raise exc
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/local.py", line 224, in execute_task
    result = _execute_task(task, data)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/core.py", line 119, in _execute_task
    return func(*(_execute_task(a, cache) for a in args))
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/optimization.py", line 990, in __call__
    return core.get(self.dsk, self.outkey, dict(zip(self.inkeys, args)))
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/core.py", line 149, in get
    result = _execute_task(task, cache)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/dask/core.py", line 119, in _execute_task
    return func(*(_execute_task(a, cache) for a in args))
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/awkward/highlevel.py", line 962, in __getitem__
    out = self._layout[where]
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/awkward/contents/content.py", line 493, in __getitem__
    return self._getitem(where)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/awkward/contents/content.py", line 506, in _getitem
    return self._getitem_field(where)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/awkward/contents/indexedarray.py", line 217, in _getitem_field
    self._content._getitem_field(where, only_fields),
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/awkward/contents/recordarray.py", line 318, in _getitem_field
    return self.content(where)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/awkward/contents/recordarray.py", line 271, in content
    out = self.form_cls.content(self, index_or_field)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/awkward/forms/recordform.py", line 151, in content
    index = self.field_to_index(index_or_field)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/awkward/contents/recordarray.py", line 265, in field_to_index
    return self.form_cls.field_to_index(self, field)
  File "/home/user/miniconda3/envs/func_adl_uproot_rc/lib/python3.10/site-packages/awkward/forms/recordform.py", line 128, in field_to_index
    raise ak._errors.wrap_error(
IndexError: while attempting to slice

    <Array [{int_branch: -1}] type='1 * {int_branch: int32}'>

with

    'long_branch'

Error details: no field 'long_branch' in record with 1 fields

As you can see, after slicing with da[da.int_branch < 0], the other branches are supposed to still be there, but they seem to disappear after running .compute()

Yea this should be fixed by #131

I was able to test it with the file you linked- now there's an issue with uproot :) I'll create a PR

Ok #131 combined with https://github.com/scikit-hep/uproot5/pull/806 should fix this.


Bugfix static file path, fixes #15

Static files were not available under /static/ when running in dev mode.

Template migrated to webpack v4, so it don't required anymore


Week 2- Using Objects

Using Objects: Link
Code.org OOP:

Crossover Grading
Score: (2.7/3)

Improved a lot over the week with understanding Java code and writing class implementation in console
Finished all code.org, demonstrated understanding
Finished hacks

Could be improved:

Next time will work on implementing own GUI, moving up from console

Self Grade: 2.7/3.0
Finished all code.org
Showed understanding of Java code
Finished hacks
Showed improvement over week


Cleanup internal scripts

📦 Pull Request
Cleans up and improves the presentation/organization of internal tooling.
⚠ Don't forget to add a semver label!

patch: Bug Fix?
minor: New Feature?
major: Breaking Change?
skip-release: It's unnecessary to publish this change.

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


Streaming TTS Support？

This is a great project! Is there any plan to support streaming TTS?

Thank you for your suggestion. Streaming TTS is indeed an important use case, and we will consider adding it in our future version.


Group should show result for HTTP-RAW and HTTP-FORMATTED

I would like to group version of all services within an environment but it shows nothing

Hey, you should use 2 tiles for that, not a group. If you want to pack them into a reduced space, you can use columnSpan and rowSpan.
https://monitoror.com/documentation/#ui-configuration

Hi @Alex-D
Thanks for your reply, I understand the #ui-configuration but following is what I want to group

Multiple groups in a screen


continuous deployment on K8S from Travis

idea: we can automatically update the K8S worker when a commit is pushed to master, from the deployment script, with an encrypted secret in Travis.
@gluckzhang WDYT?

Hi @monperrus , that sounds great. This should be done after the script pushes the built image to DockerHub. I will make a PR to solve this issue :)
To be updated:

kubectl installed in Travis environment
necessary configs like the k8s IP and credentials set by Travis UI (env value)

The command to be added after this line:
https://github.com/eclipse/repairnator/blob/59985e7a854c5e0d82c73a5472d611c9d2895c45/.travis/travis-deploy.sh#L47
kubectl delete pod $(kubectl get pods -n repairnator -l app=repairnator-pipeline -o custom-columns=NAME:.metadata.name --no-headers=true) -n repairnator

that's a great plan, thanks Long!

ping @gluckzhang ?

Hi @monperrus , I am still working on this. I'll create a PR later today :)
The work is mainly inspired by https://codygreen.com/2018/08/13/ci-cd-with-kubernetes-and-travis-ci/

cool! looking forward to it :)

It works!
#1037 was merged, the K8S worker was automatically updated and the following PR was made with the new text: https://github.com/monperrus/failingProject/pull/13
Thanks a lot!


Two-dimensional models results in non-equidistant IDFs which crash iMODFLOW

In GitLab by @Huite on Nov 9, 2018, 20:31
When dealing with a 2D (x, z) model, it's attractive to specify a dy of 1.0 m, so it's "per unit". However, this results in non-equidistant IDFs, which seem to crash iMODFLOW (both iMOD and iMODSEAWAT seem to handle it okay). Indeed, there's only one cellsize parameter in the iMODFLOW runfile: https://gitlab.com/deltares/imod-python/blob/master/imod/templates/runfile.j2#L5
Fix for now: When x or y has only one value, force dx = dy.
Of course, should ideally be taken up in the iMODFLOW code.

In GitLab by @Huite on Nov 9, 2018, 20:49
closed via commit e248fffa9e4980737bad1fcd59f1117e51d52660


AG Grid Theme

[ ] Create a theme for ag-grid v27 to match the new grid specs (TK2/odyssey grid)
[ ] Update all stories in the ag-grid-theme package to allow switching between the old (TK1) theme and the new (odyssey) theme
[ ] Design review
[ ] Accessibility review
Tests are not required as there is no new of modified functionality.

@shinytoyrobots understanding is that we are simply providing a theme over AG Grid. So from an accessibility perspective the only requirement is ensuring the compliance of the design. Anything else will (KB interactions, ARIA, focus order, etc) will be AG out-the-box, warts'n'all. Does that align with your thinking?

11/4 - discuss progress and review this today (Rustam/Ben/Darrin)

11/24: No updates

@ararus @ZarkoPernar @joshwooding design review complete. Can be found here.


Migrate to build version catalog

Why
Gradle Version Catalogs allow developers to mange dependencies across modules from a single filegradle/libs.versions.toml, which contains 4 sections:

[versions] declares what versions are used by the dependencies
[libraries] declares our libraries/dependencies
[bundles] allows defining groups of dependencies that are commonly used together
[plugins] declares our plugins

This allows us to centralize the dependencies declared across modules and submodules. We can replace Dependencies, Plugins and Versions from the buildSrc module with a single project level gradle/lib.versions.toml file 🙇🏻
References

Android Developers
Gradle

Who Benefits?
Developers

@ryan-conway Seems you open duplicated issue? https://github.com/nimblehq/android-templates/issues/575


Failed to open fglrx_dri.so

After installing the AMD Catalyst driver (fglrx) in NixOS 15.09 by setting services.xserver.videoDrivers = [ "ati_unfree" ];, direct rendering is not enabled. Details are:
$ LIBGL_DEBUG=verbose glxinfo | grep direct
libGL: AtiGetClientDriverName: 15.20.3 fglrx (screen 0)
libGL error: OpenDriver: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
libGL error: OpenDriver: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
libGL error: OpenDriver: failed to open /run/opengl-driver/lib/dri/fglrx_dri.so, error[libstdc++.so.6: cannot open shared object file: No such file or directory]
libGL error: OpenDriver: failed to open /usr/lib/dri/fglrx_dri.so, error[/usr/lib/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
libGL error: OpenDriver: failed to open /usr/X11R6/lib32/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib32/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
libGL error: OpenDriver: failed to open /usr/lib32/dri/fglrx_dri.so, error[/usr/lib32/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
libGL error: dlopen fglrx_dri.so failed
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)

The AMD Catalyst Arch wiki section for this "failed to open fglrx_dri.so" error says to create symlinks for the missing requested paths, which I suppose might be a workaround, but really shouldn't Nix be taking care of this?
On the other hand, /run/opengl-driver/lib/dri/fglrx_dri.so does actually exist, so maybe the error is with finding libstdc++.so.6?

Pinging @nathanielbaxter, @jgeerds, @vcunat, and @offlinehacker for involvement in #3989 and #4185.
Could the issue be at https://github.com/NixOS/nixpkgs/blob/1a86bf8aae151c40747f4e47e791356ff0084e2b/nixos/modules/hardware/video/ati.nix#L22 where libPath is set?
Setting environment.extraInit = pkgs.lib.mkIf (videoDriver == "ati_unfree") "export LD_LIBRARY_PATH=${pkgs.gcc_multi.cc}/lib:${pkgs.gcc_multi.cc}/lib64:$LD_LIBRARY_PATH''; and creating the /usr/X11R6/lib64/modules/dri -> /run/opengl-driver/lib/dri symlink causes glxinfo to segfault but gets rid of the above errors.

I know little about the proprietary ATI drivers in particular. From what you write, there seem to be some ugly hacks done, perhaps prone to break. You can test ldd /run/opengl-driver/lib/dri/fglrx_dri.so to find if that file links correctly at least.

I suggest having a look at the driver package if you haven't already, more likely to be an issue there (where the ugly hacks are) than in the module.
I haven't used these drivers for over a year, so I'm unsure what state they're in at the moment, last update was made by @dfoxfranke

@vcunat
$ ldd /run/opengl-driver/lib/dri/fglrx_dri.so
	linux-vdso.so.1 (0x00007ffe240e1000)
	libstdc++.so.6 => not found
	libpthread.so.0 => /nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libpthread.so.0 (0x00007ffa6f4aa000)
	librt.so.1 => /nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/librt.so.1 (0x00007ffa6f2a2000)
	libdl.so.2 => /nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libdl.so.2 (0x00007ffa6f09e000)
	libm.so.6 => /nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libm.so.6 (0x00007ffa6ed9b000)
	libgcc_s.so.1 => /nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libgcc_s.so.1 (0x00007ffa6eb85000)
	libXext.so.6 => /run/opengl-driver/lib/libXext.so.6 (0x00007ffa6e973000)
	libX11.so.6 => not found
	libc.so.6 => /nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libc.so.6 (0x00007ffa6e5d3000)
	/nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib64/ld-linux-x86-64.so.2 (0x00007ffa71f27000)
	libX11.so.6 => /nix/store/cwzl5vyl3lqzilh4hklff0h8zh3c77w4-libX11-1.6.3/lib/libX11.so.6 (0x00007ffa6e296000)
	libxcb.so.1 => /nix/store/dfwj9b6vb2g65asg681yw2w8knpmlqq4-libxcb-1.11/lib/libxcb.so.1 (0x00007ffa6e078000)
	libXau.so.6 => /nix/store/p408ns8dn0cfi4z4fzd6f10b9pvlfhss-libXau-1.0.8/lib/libXau.so.6 (0x00007ffa6de75000)
	libXdmcp.so.6 => /nix/store/xm4jqqq9m2nb9mczvv02z1lsyj225kvf-libXdmcp-1.1.2/lib/libXdmcp.so.6 (0x00007ffa6dc70000)

@nathanielbaxter Thanks for pointing me to the driver package. That does seem like it would be more likely what needs to be updated.

Then I think the best step is to use patchelf to extend RPATH so that it finds those libraries, probably from packages stdenv.cc.cc and xorg.libX11.

The hacks that you are probably looking for are here; using sed to replace paths in binary files is ugly but such is life.
As vcunat said you may need to run patchelf on "$out/lib/dri/fglrx_dri.so" and/or other libs provided by ati, patchelf is already used in builder.sh to fix references to libstdc++ for other libs.

I did create a pull request with my changes at #11817. As I mention there, I am still getting the segfault. Would you mind please helping me? I know little about driver issues.

Is this related to #8676?

/nix/store/HASHPATH/ati-drivers-15.7/lib/fglrx/switchlibglx
Usage:
switchlibglx   amd|intel|query
amd:   switches to the AMD version of libglx.so .
intel: switches to the open-source version of libglx.so .

FTW we should delete or adapt the scripts in that directory because they won't work as is in nixos.
glxinfo is for when using the open-source version of libglx.so.
fglrxinfo is for when using the AMD version of libglx.so.
The nixos package definitely does not use the open-source version of libglx.so by default.
In order to fix glxinfo to work as OP expects, the open-source version of libglx.so needs to be re-built or patched to look at the correct paths if ati-drivers is installed.
As we don't use the open-source version of libglx.so in ati-drivers - glxinfo failing is a non-issue unless the option to use the open-source version of libglx.so is added to ati-drivers.
What this report did expose is that in ati-drivers there are missing library paths to libstdc++.so.6 and that there is also an empty entry pointing to libX11.so.6.
Fixing those two issue likely solves any other issues people (like me) were having with ati-drivers.

That's super confusing to me. Shouldn't glxinfo, and anything else, use the unfree libglx.so when that is the one that is installed? Does NixOS have different packages bypassing the driver that's installed and using whatever driver they choose?

libglx.so is part of the opengl implementation. The open source implementation named mesa is not feature complete. That is to say that it does not fully support all current opengl standards. It is on going work and is progressing.
AMD cards support opengl extensions which are proprietary which are not part of the current opengl standards so AMD bundle libglx.so with their driver which supports their own proprietary opengl extensions (which are not part of the opengl specification) and may (or may not) include feature completeness for existing opengl standards which are not complete in mesa.
So it is better for catalyst to not use libglx.so provided by mesa if you want to use AMD supported opengl feature x or proprietary extension x which is provided by the opengl library AMD have bundled with their driver.
This relates to glxinfo because glxinfo is a tool to look at opengl information supported by a driver. Depending upon whether the driver uses libglx.so from AMD or not will depend upon what is returned by the program. switchlibglx is supposed to enable a user to switch between the driver using mesa opengl or the AMD bundled opengl. In it's current form it will not work in nixos.
glxinfo not working does not effect direct rendering. glxinfo only reports that direct rendering is not enabled because it cannot probe to find out.
clinfo from the AMD sdk is actually how you check the AMD catalyst driver. I haven't tried it although it has been packaged.
nixpkgs/pkgs/tools/graphics/glxinfo/ needs to be patched using patchelf or compiled so that the paths to the libraries are correct should ati-drivers be installed (and I suspect also the non free nvidia drivers also) in order that it works should a non-free driver be installed.

Thanks @heydojo for the explanation. Some of that was already clear to me, but I think what I am still having trouble understanding is why any application, glxinfo or not, would need to be patched based on what driver is installed. It may end up to be the correct solution to simply patch it, but how would we know that glxinfo is the only app not seeing the correct library paths?
I have at least one other app not working correctly when I use unfree Catalyst, so I'm concerned this is a systemic problem.
Shouldn't every app, including glxinfo, be using whatever is in /run/opengl-driver as the driver?

Why any application, glxinfo or not, would need to be patched based on what driver is installed?

Purity in Nixos. When glxinfo is built it cannot see ati-drivers and does not know that ati-drivers are installed (should it need to.)
In your debug you can see glxinfo is looking for /usr/X11R6/lib64/modules/dri/fglrx_dri.so and that path is clearly wrong. The root of that problem lies either with glxinfo or the opengl library.

But how would we know that glxinfo is the only app not seeing the correct library paths?

You can test, use ldd to check paths and run strace on programs.

I have at least one other app not working correctly when I use unfree Catalyst, so I'm concerned this is a systemic problem.

Which app is not working? You have one other app not working or you have more than one not working? Maybe this is a systemic problem. It wouldn't be a reason to be concerned.

Shouldn't every app, including glxinfo, be using whatever is in /run/opengl-driver as the driver?

I don't understand. Graphical applications talk to the xserver, usually using a toolkit library and the xserver handles the driver.

When glxinfo is built it cannot see ati-drivers and does not know that ati-drivers are installed
If glxinfo relies on drivers to work, I do think it should know about the drivers that are installed when it is built, at least if I understand the problem correctly. If this isn't the case, glxinfo ceases to have a purpose.

use ldd to check paths and run strace on programs
Seems like an overwhelmingly large task.

Which app is not working?
HipChat, that I know of so far...

Maybe this is a systemic problem. It wouldn't be a reason to be concerned.
So far NixOS has been the most painful distro I have used in terms of configuration. I am still new to it, and I haven't given up because I have the ability to contribute, and I think the core idea is good. However, if I can't convince myself that installing an application will guarantee that the application will work, including using the correct graphic driver, I will probably move to another distro.

I don't understand. Graphical applications talk to the xserver, usually using a toolkit library and the xserver handles the driver.
If you don't understand, imagine how I must feel. You are saying only the xserver needs to know about the driver? Why does the xserver not handle things for glxinfo, if you are correct? Why is that an exception? How many exceptions are there?

Seems like an overwhelmingly large task.

Welcome to the world of developing nix expressions where every path should be checked for purity. :)

So far NixOS has been the most painful distro I have used in terms of configuration.

But it is improving and has huge potential. I was a distro shuffler for about two years. Then I dug in, read documentation, studied and gained enough skills to get by.

Why does the xserver not handle things for glxinfo

If you look at the builder for glxinfo you will see that it is a small stand alone program. Look at the source code for glxinfo if you want to understand how it works.

I don't understand what's not clear about libglx; I believe the state is this:
our X server has its own libglx implementation, and in addition it is set up to search for modules in /run/opengl-driver/lib/xorg/modules/extensions where the proprietary drivers are supposed to install their libglx versions. It is nixos who does the switching. (Therefore you're correct that fglrx switching script would better not be installed.)

I don't understand what's not clear about libglx

I don't have the background/understanding of how any given app (including glxinfo) interacts with the graphics drivers. I'll try to again re-state my current understanding and my outstanding questions.
I have gathered that libglx is a part of the graphics driver "suite", there there are conflicting versions of it, and that it's up to NixOS to resolve that conflict.
I'm not sure if libglx is special, but it seems to me that for any app that needs any library belonging to the graphics driver, Nix should make the appropriate connection. Note that it's not clear to me precisely by what means this "connection" should be made, whether it takes the form of LD_LIBRARY_PATH, patchelf, or something else.
The specific case in question for this issue, which has not been answered in a way that I can understand, is why the app glxinfo does not use the unfree ATI driver (fglrx) when it is installed. If libglx is a relevant library to glxinfo that is a part of the fglrx driver, and NixOS is responsible for the "switching", what needs to happen to set things right? And also important to me: can it be solved in a way that also ensures other applications do not have this problem?

I believe this GPU driver switching works fine in general on NixOS. I'm using the proprietary nvidia drivers for years, even for various heavier use cases (steam and other games). The glxinfo+fglrx breakage may well be unrelated to this directly, IMHO.

Thanks @vcunat. Knowing that will at least keep me from going down a very scary rabbit-hole.

I don't think the glxinfo problem is entirely unrelated. I now have R7 370, and if I try and run my own personal SDL2 projects:
Preprocessing executable 'ssao-example' for ssao-example-<IP_ADDRESS>...
Running ssao-example...
libGL: AtiGetClientDriverName: 15.20.3 fglrx (screen 0)
libGL error: OpenDriver: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
libGL error: OpenDriver: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
ukiDynamicMajor: found major device number 249
ukiDynamicMajor: found major device number 249
ukiDynamicMajor: found major device number 249
ukiOpenDevice: node name is /dev/ati/card0
ukiOpenDevice: open result is 4, (OK)
ukiGetBusid returned 'PCI:1:0:0'
ukiOpenDevice: node name is /dev/ati/card1
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card2
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card3
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card4
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card5
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card6
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card7
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card8
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card9
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card10
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card11
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card12
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card13
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card14
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiOpenDevice: node name is /dev/ati/card15
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiDynamicMajor: found major device number 249
ukiOpenByBusid: Searching for BusID PCI:1:0:0
ukiOpenDevice: node name is /dev/ati/card0
ukiOpenDevice: open result is 4, (OK)
ukiOpenByBusid: ukiOpenMinor returns 4
ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
ukiDynamicMajor: found major device number 249
ukiDynamicMajor: found major device number 249
ukiOpenByBusid: Searching for BusID PCI:1:0:0
ukiOpenDevice: node name is /dev/ati/card0
ukiOpenDevice: open result is 5, (OK)
ukiOpenByBusid: ukiOpenMinor returns 5
ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
Segmentation fault

I also get a segmentation fault, like glxinfo.


Support client-side job ID generation with optional user-supplied prefix

See Generating a job ID for background.

The google-cloud-dotnet implementation uses UUID.

Reading through the docs, I would have a prefix of "job" and use a UUID.
prefix = "job"
uuid = SecureRandom.uuid
job_id = "#{prefix}_#{uuid}"

So something like this:
def query_job query, prefix: "job"
  job_id = "#{prefix}_#{SecureRandom.uuid}"
  # ...
end

I wonder if SecureRandom#urlsafe_base64 is a better choice than SecureRandom#uuid?(@blowmage I think you suggested this first.) It seems closer to the BigQuery service's ids, if that is desirable.
Examples
BigQuery service:
job_12vEDtMQ0mbp1Mo5Z7mzAFQJZazh

Using SecureRandom.uuid:
job_56d91226-205b-4bcc-9bc0-f32a2993f61e

Using SecureRandom.urlsafe_base64(21):
job_gdQ2fa95Ncbe-2wxdPwlAfX-z6YN

I'm definitely in favor of using SecureRandom.urlsafe_base64. I might even go so far as to suggest using SecureRandom.urlsafe_base64(32)...

Closed by #1664.


On behalf of a single browse view...

We have several browse views that are essentially the same. For example:
Browse Curriculum Toolkit, filtering on Academic Program
/browse/topics/curriculum/?content_type=academicprogram
Browse Academic Program, filtering on Curriculum
/browse/types/academicprogram/?content_type=academicprogram
Search (if we were to remove the requirement for a search keyword)
/browse/?search=test&topics=curriculum&content_type=academicprogram
Is it worth consolidating these at all? Here's what I've got for pros/cons right now:
Pros

reduce the number of views to maintain and update going forward
might improve user experience

allows users to quickly switch between topics or content types
in some pages the content-type and topic filters aren't there (consistency issue)

Cons

This might take away from the toolkit pages

Anyway, would love your feedback, @monika-aashe @juliandsmith @peltonc

Those 3 views are backend-wise just one view. Just rendered with a different template.
And we already have exactly the same filter form for each view. For the topics view we hide the topic selector field in CSS: https://github.com/AASHE/hub/blob/master/hub/static/scss/base.scss#L249-L257 Same for content type.
The search term isn't required too, but we enforce it here: https://github.com/AASHE/hub/blob/master/hub/apps/browse/views.py#L77-L85 If you'd remove that then /browse/ would simply show everything.
By the way, you can achieve the same if you search for * now: http://aashe-hub-dev.herokuapp.com/browse/?search=*

Whatever we decide, we need to ensure that we can custom-add sponsors to sustainability topics and/or content types.

Moving to bike rack.

This seems to be a stale conversation. Closing.


fix(Dockerfile): upgrade all packages on build

It's not guaranteed that upstream will upgrade all of the packages
within a reasonable timeframe. Therefore, when we build we should
enforce an upgrade.
It's either this or using ubuntu:16.04 directly, which at this point I'm more prone to use given that Docker tends to keep their image more up to date. Anyways I'd figure we should stay the course and use ubuntu-slim until we've fixed this issue.

Note that this PR will also include the openssl security fixes released earlier today:
$ docker run 59030c5e2df4 apt-cache policy libssl1.0.0
libssl1.0.0:
  Installed: 1.0.2g-1ubuntu4.4
  Candidate: 1.0.2g-1ubuntu4.4
  Version table:
 *** 1.0.2g-1ubuntu4.4 100
        100 /var/lib/dpkg/status

1.0.2g-1ubuntu4.4 is the patch release for Ubuntu Xenial (16.04).

closes #9

All changes/reviews received and changed. @mboersma and @helgi would you mind taking another look?

I do like this, but at the same time, I'm wondering... doesn't this make builds non-deterministic?

@krancour exactly my concern too, which is why I opened https://github.com/deis/docker-base/issues/12 :)


[ml-agent] Add missing header

Add missing header for errno to enable build daemon in ubuntu.

Signed-off-by: Yongjoo Ahn<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #206. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


Setting mappings to null doesn't diable them

⚠ Please verify that this bug has NOT been reported before.

[X] I checked all existing issues and didn't find a similar issue

Description
Before (i assume) the v0.7 merge setting a mapping (vim.debugger.nvim-dap.mappings.restart = null) would result in it not being set. However now it causes an error, probably due to the mapping rewrite.
👟 Reproduction steps
set "vim.debugger.nvim-dap.mappings.restart = null"
build
👀 Expected behavior
It doesn't set the binding
😓 Actual Behavior
It crashes
💻 Metadata

system: "x86_64-linux"  - host os: Linux 6.6.63, NixOS, 25.05 (Warbler), 25.05.20241201.ac35b10  - multi-user?: yes  - sandbox: yes  - version: nix-env (Nix) 2.24.10  - nixpkgs: /nix/store/ab78nf3ad8ly49zfyd3igw3f2n5q7fz4-source

📝 Relevant log output
error: A definition for option `vim.keymaps."[definition 1-entry 2]".key' is not of type `string'. Definition values:
       - In `/nix/store/kalwrqa2q06cvh813xifqcx78d4mzkqi-source/modules/plugins/debugger/nvim-dap/config.nix': null

can you try out #485?

Seems to work, although the keybinds are still set, but that is probably due to something in my config. Thanks


Fix hook registration if needed

Questions
Answers

Description?
Sometimes hook wasn't registered. This PR adds a migration script from v1.4.2 to v1.4.3 that performs the following logic: "if the hook displayGDPRConsent was not registered for this module, I register it"

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes PrestaShop/Prestashop#30348.

How to test?
Please see ticket. You need a usecase where GDPR module is installed (v1.4.2) and the hook displayGDPRConsent is not registered for the module. See if checkboxes are displayed after GDPR upgrade module to 1.4.3.

@kpodemski I improved a bit the PR description and How to test ;)

Thanks @hibatallahAouadni !


Bump AsyncKeyedLock to 6.3.4

@EricDahlvang are you interested in such PRs? You will gain performance from this update. Furthermore 6.4.2 is out.


Verify that Cliffords fix Pauli group

Follow-up to #3414. Sorry, couldn't resist.

Automerge cancelled: A status check is failing.


Some codes can't be found

Thanks for your great work! And I want to ask when can you update new version. This version can't work in the wild

Did you follow the instruction for testing on in-the-wild videos? Is there any error message when you run the code?


Converting a pipeline

What would it take to convert an entire pipeline to a coreml model?
For instance, I have saved the stable-diffusion checkpoint, and several of the models have their own configs, but of course they're not the ready-made configs.

Would this be just a long, hard, custom slog via exporters and not worth it? Or is there something here worth pursuing?

For folks interested, I added a comment to this gist that has a bunch of the models converted. 3 out of 4!
One bit I'm trying to convert is CLIP. Since the model uses the CLIPTextModel, and the CLIPTextEncoder.
Thoughts about how I might go about this? I get a
Torch var mask.3 not found in context and a whole bunch of warnings that a tensor is getting converted to a boolean.
And then I'm also not sure how I could convert the scheduler. Or if I can ignore that.
https://gist.github.com/madebyollin/86b9596ffa4ab0fa7674a16ca2aeab3d

Ha! The original author of the post was gracious enough to fix up that CLIPTextEncoder. Nice.
One thing I'll need to tackle implementing to start experiment running on iPhone and iPad and Mac app is the tokenizer.
I've opened an issue here if folks know the answer: https://github.com/huggingface/swift-coreml-transformers/issues/28

@MatthewWaller Did you ever get anywhere with this pipeline conversion?

@MatthewWaller Did you ever get anywhere with this pipeline conversion?

@rovo79 i eventually converted a stable diffusion pipeline, but it was just a long hard slog, and there is now an entire Apple repo on converting stable diffusion and other libraries. So much happened in a year! So I don’t think this issue needs addressing anymore


Custom LLM Model

Hello All,
trying to use Dataherald with mistral LLM or with the new SQLCoder
does any one achieved this before, and post some step by step guide to use custom llm models.
best

@Namec999 Hi, I'm working on the open-source LLMs integration with Dataherald, I will write a step by step guide as soon as I can. The issue is that most of open-source LLMs are not good at function calling, so we resort to GPT family.

thank you, that will be greate
i am also trying nexusraven open source llm that outperforms the GPT family in function calling

Dear @MohammadrezaPourreza , is there any chance that we utilize custom llama-based LLMs in dataherald? consider using a PEFT models like nexusraven with larger parameter size.

@Namec999 Hi, I'm working on the open-source LLMs integration with Dataherald, I will write a step by step guide as soon as I can. The issue is that most of open-source LLMs are not good at function calling, so we resort to GPT family.

What about ability to work with Azure OpenAI?  Is that an option?

I have attempted to do it. Please have a look it https://youtu.be/ksafgK-S_ko?si=wdx-5Ov4dHYSE6N0

@alifzl @ankur198 @deeteeakl @Namec999 I'm sorry for the delay in getting back to you, but I have some exciting news to share! We now support open-source LLMs, and you can easily use any model from Hugging Face with our tool. We've merged the code, and I'll be writing a blog post to guide you through the process soon. Thank you!

@alifzl @ankur198 @deeteeakl @Namec999 I'm sorry for the delay in getting back to you, but I have some exciting news to share! We now support open-source LLMs, and you can easily use any model from Hugging Face with our tool. We've merged the code, and I'll be writing a blog post to guide you through the process soon. Thank you!

@MohammadrezaPourreza looking forward to check the blog post of yours in order to check how we can use and fine tune Local Custom LLMs in your great solution.
cheers.

@MohammadrezaPourreza Have you documented or blogged the approach for custom LLM setup yet? Cheers?