Waterline's sails-mongo adapter fails to convert query input to ObjectId when applying certain operators

Node version: v8.17.0
Sails version (sails): 1.2.3
ORM hook version (sails-hook-orm): 2.1.1
DB adapter & version<EMAIL_ADDRESS>No additional top-level dependencies present. Confirmed with merely sails, sails-hook-orm and sails-mongo.

There appears to be an issue where the sails-mongo Waterline adapter fails to transform input query filter values to Mongo ObjectId instances where appropriate, instead leaving such values as simple strings.
This occurs in cases where the target field appears to be an appropriate candidate (a primary key) for normalisation to ObjectId and only affects the following operators:

<
<=
>
>=

For instance, the following Waterline query:
Post.find({
  id: {
    '>': '5e9a49923a48025cccdaee43',
  },
});

Will ultimately issue this to MongoDB:
{
  _id: {
    '$gt': '5e9a49923a48025cccdaee43'
  }
}

Rather than the expected query of:
{
  _id: {
    '$gt': ObjectId('5e9a49923a48025cccdaee43')
  }
}

This results in an inability to perform a number of useful queries against PK fields (such as paging on document IDs) and feels inconsistent with the behaviour of the other Waterline query operators supported by sails-mongo, as well as other adapters.
I've built a mostly minimal test case at Rua-Yuki/waterline-mongo-objectid-comparison-funk, which also contains more information about this issue.
A quick fix exists in the fpm-git/sails-mongo fork.

(The following is mostly snipped from Rua-Yuki/waterline-mongo-objectid-comparison-funk, for posterity's sake)
Regarding one use case which this issue prevents, we are left unable to page based on document IDs or use said IDs as tie-breakers when paging on fields that may not be unique.
Given the following model:
/**
 * @file Post.js
 */

module.exports = {
  attributes: {
    content: {
      type: 'string',
      required: true,
      maxLength: 280,
      minLength: 1,
    },
  },
};

And a dataset like so:

_id
content
createdAt
updatedAt

ObjectId("5e9a49923a48025cccdaee43")
Hello World!
1587169682656
1587169682656

ObjectId("5e9a49923a48025cccdaee44")
Testing 123.
1587169682656
1587169682656

ObjectId("5e9a49923a48025cccdaee45")
Testing 456.
1587169682656
1587169682656

ObjectId("5e9a49923a48025cccdaee46")
Testing 789.
1587169682656
1587169682656

The following query will not return results as expected:
// Try and find the next item after our input.
Post.find({
  id: {
    '>': '5e9a49923a48025cccdaee43',
  },
}).sort('id ASC').limit(1).then((res) => {
  // Logs "Found []"
  sails.log.debug('Found', res);
});

The expected result of this query is to return the item directly after our input ID, if any:
[{
  id: '5e9a49923a48025cccdaee44',
  createdAt:<PHONE_NUMBER>656,
  updatedAt:<PHONE_NUMBER>656,
  content: 'Testing 123.'
}]

We instead receive only an empty array, regardless of whether a match exists or not:
[]


Added primary key to table KYLO_ALERT_CHANGE as a pre-requisite for MS-SQL support

Please accept this pull request as part of a long term plan to implement MS-SQL support in Kylo:
This change adds composite primary key (alert_id, state, change_time) to table KYLO_ALERT_CHANGE. This will be necessary for MS-SQL support, as SQL server requires a primary key (e.g. while migrating schema SQL Server Migration Assistant).
The change should not cause any issues with the existing code base: a combination of alert_id, state, change_time should always be unique.  change_time is never null, as it is filled in constructor JpaAlertChangeEvent#JpaAlertChangeEvent(com.thinkbiganalytics.alerts.api.Alert.State, java.security.Principal, java.lang.String, java.io.Serializable)

For future reference, it was decided that the primary key should be a unique id rather than a composite of existing fields. I think that change is being done separately.


ci(release): prevent fail release when setting version

😢

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Neos CMS 5.* version

Hi,
Any known blockes not mentioned in the issue list in order to release a version for Neos CMS 5.*? :-)

Hi @sorenmalling, I just finished a PR from @daniellienert and released a first alpha for 4.0.0 (https://packagist.org/packages/moc/varnish#4.0.0-alpha1) with Neos 5.* compatibility.
A stable release will follow shortly after we tested this in more Neos installations.


updating to add the SwellCorr project

https://github.com/mlbelobraydi/t21-hack-SwellCorr
SwellCorr is a Software Underground Transform 2021 hackathon project. Thank you for adding us.

Oops, I wasn't the first to do this. Sorry for the repeat request. Decline as necessary.


Issue with seeding

How am I meant to seed the first cassandra/priam node in my cluster? My first node fails to start, apparently because it's unable to find a list of seed(s).
What appears to be happening is that the NFSeedProvider is making REST calls to get a list of seed nodes and it is failing. Thus preventing Cassandra from completing the startup (because the Priam agent loops until that REST call succeeds).
Am I missing a step here where I might be required to bootstrap a node manually, without Priam, one that can be the seed node?

Hi Apurva,
Overall, Priam's algorithm should recognize and select the first node as the "seed".  The algorithm is base within InstanceIdentity.getSeeds().  Unfortunately, this is not a common task so I will need for you to do the following to better understand your situation.
Within InstanceIdentify, what is the size of the "locMap".  It should your initial node.  To best way to find this is to use "jdb" to enable interactive debugging on the node.  If you are not familiar with this, I can provide detail instructions.
Regards

@tulumvinh i am facing same issue while spinning up multi-region cassandra, can please you share instructions to use jdb

@yashk please sync with Apurva as I believe he as a cluster bootstrapped.
As for jdb:

Update Tomcat's setenv.sh, normally under /apps/tomcat/bin.  Set JVM argument "suspend" to "y".
Restart Tomcat.  Tomcat will wait until jdb is attached.
jdb -attach port (the port can be derived from the Tomcat log).

Closing as original issue was with apurvasingh which he resolved.


Buildpack over slug size

Hey there, really looking forward to using this build, but when I try to add to heroku I get an error saying its over the allowed slugsize. Have you had this issues, and any recommendations on how I can get this to work?
Thanks!!

@robertdoneill consider pinging heroku and asking to have your limit increased

Same problem here. Not a very useful buildpack — better to use heroku-buildback-apt to install libreoffice I'd imagine.

@fatuhoku FWIW I asked heroku support to up my slug size and they did so within the same day. you might be able to also

Good tip thanks @sgringwe

@robertdoneill  I have a similar problem and I wonder if there is an option to install without a user interface like a regular server:
Apt-get install libreoffice -no-install-recommends


Added collision handler for Huayno OK algorithm

Integrated the collision detection algorithm from the various SHARED_COLLISION Huayno integrators into the OK integrator.
Note: This collision checker does not detect collisions between two massless particles.

I made a new file which hosts the collision detection function and with which both evolve_shared_collisions.c and evolve_ok.c call. The algorithm neglects collisions between two massless particles to save computing time at the detriment that perhaps this isn't an assumption that some users would want. If that is a bother I can rewrite the code to include it.
I hope the changes are fine. I tested collisions using either integrators and I don't see a change in performance.

This PR needs at least a test to show that this collision detection actually works before it can be merged.


jobs being repeatedly called

not 100% the source of this issue, but if you can shed any light it's much appreciated. i'm still just trying to make sure everything is wired up properly so i set up a really simple job. for some reason the job seems to keep getting called over and over again.. here's a snippet of the log when i made a second request. i made a call from my webserver console and called UpdateSongJob.perform_later(args)

[ActiveJob] [UpdateSongJob] [6b99eb86-3981-4bdf-bfd4-21702fca7c4f] Performing UpdateSongJob from ActiveElasticJob(test_queue) with arguments: "568979ced2b38b05d00003d6", "<IP_ADDRESS>", "80"
[ActiveJob] [UpdateSongJob] [6b99eb86-3981-4bdf-bfd4-21702fca7c4f] Performed UpdateSongJob from ActiveElasticJob(test_queue) in 0.48ms
Started POST "/" for <IP_ADDRESS> at 2016-02-18 11:14:27 +0000
[ActiveJob] [UpdateSongJob] [97ea6055-8940-4d18-a02a-f0911d83509f] Performing UpdateSongJob from ActiveElasticJob(test_queue) with arguments: "5670b6fe7e8482b048000166", "<IP_ADDRESS>", "80"
[ActiveJob] [UpdateSongJob] [97ea6055-8940-4d18-a02a-f0911d83509f] Performed UpdateSongJob from ActiveElasticJob((test_queue) in 0.51ms
Started POST "/" for <IP_ADDRESS> at 2016-02-18 11:14:27 +0000
[ActiveJob] [UpdateSongJob] [c2bde572-73d2-4369-be53-263cd86179c5] Performing UpdateSongJob from ActiveElasticJob(test_queue) with arguments: "5670b6fe7e8482b048000166", "<IP_ADDRESS>", "80"
[ActiveJob] [UpdateSongJob] [c2bde572-73d2-4369-be53-263cd86179c5] Performed UpdateSongJob from ActiveElasticJob(test_queue) in 0.38ms
Started POST "/" for <IP_ADDRESS> at 2016-02-18 11:14:27 +0000
[ActiveJob] [UpdateSongJob] [c41a9f00-4437-4889-a1a7-681777b4dd0f] Performing UpdateSongJob from ActiveElasticJob(test_queue) with arguments: "5670b6fe7e8482b048000166", "<IP_ADDRESS>", "80"
[ActiveJob] [UpdateSongJob] [c41a9f00-4437-4889-a1a7-681777b4dd0f] Performed UpdateSongJob from ActiveElasticJob(test_queue) in 0.54ms
Started POST "/" for <IP_ADDRESS> at 2016-02-18 11:14:27 +0000
[ActiveJob] [UpdateSongJob] [73b93aa3-1903-49ef-9da8-171ed1cce732] Performing UpdateSongJob from ActiveElasticJob(test_queue) with arguments: "5670b6fe7e8482b048000166", "<IP_ADDRESS>", "80"
[ActiveJob] [UpdateSongJob] [73b93aa3-1903-49ef-9da8-171ed1cce732] Performed UpdateSongJob from ActiveElasticJob(test_queue) in 0.46ms
Started POST "/" for <IP_ADDRESS> at 2016-02-18 11:14:28 +0000
[ActiveJob] [UpdateSongJob] [6b99eb86-3981-4bdf-bfd4-21702fca7c4f] Performing UpdateSongJob from ActiveElasticJob(test_queue) with arguments: "568979ced2b38b05d00003d6", "<IP_ADDRESS>", "80"
[ActiveJob] [UpdateSongJob] [6b99eb86-3981-4bdf-bfd4-21702fca7c4f] Performed UpdateSongJob from ActiveElasticJob(test_queue) in 0.45ms

This behavior can have several different causes:

the job has not been completed or not reported to the queue as such. Check your logs if the responses return a 200 response code. It should look like this:

/var/app/support/logs/access.log
-------------------------------------

<IP_ADDRESS> - - [18/Feb/2016:14:08:17 +0000] "POST / HTTP/1.1" 200 5 "-" "aws-sqsd/2.0"
<IP_ADDRESS> - - [18/Feb/2016:14:08:24 +0000] "POST / HTTP/1.1" 200 5 "-" "aws-sqsd/2.0"

the Visibility timeout setting is too optimistic. The queue will wait for so long for a response that the job has been successfully processed. If there is no response within this time window (for example the job takes longer), than the queue makes the job available again. You can find this setting here: select your woker environment -> Configuration -> Worker configuration.

I can tell you more if you paste the log snippet from the /var/app/support/logs/access.log part.
Hope that helps,
tawan

ah, i see. yeah looks like i'm getting a 500 error, and i set a pretty high visibility timeout so it keeps retrying. a little confused on how to move forward still, though.
<IP_ADDRESS> - - [18/Feb/2016:10:38:35 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:36 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:37 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:38 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:39 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:40 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:41 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:42 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:43 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:44 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:45 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:46 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:47 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:48 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:49 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"
<IP_ADDRESS> - - [18/Feb/2016:10:38:50 +0000] "POST / HTTP/1.1" 500 193 "-" "aws-sqsd/2.0" "-"

Yea, there is an error while the job is performed. Your issue brought my attention to how the gem handles errors and until now it did it wrong. It just responds with 500 but then leaves no traces in the logs.
I fixed that and released a new version (1.4.2).
You should update to the new version with
bundle update active_elastic_job

commit the updated Gemfile.lock file and deploy again.
With the new version you should have more infos in the logs on what actually isn't working.
You should then check the section below
-------------------------------------
/var/app/support/logs/production.log
-------------------------------------

:+1:  Thanks for posting your problems, your feedback helps to make this gem more stable.

perfect, thankyou! super glad to have discovered this gem

@claudeomusic - How did you get it to stop running?


feat(frontend): add info banner in conversion modal for ck tokens

Motivation
There will be an info banner at the bottom of the ck- conversion forms.
Desktop

Mobile

Discussed with Artem and he is ok with multiple lines


AutoML Unable to infer column types of the file when column# exceeds 10000

System Information (please complete the following information):

Model Builder Version: 16.0.1907.1703
Visual Studio Version: Visual Studio 2017 15.9.14

Describe the bug
csv file get an error when I try to load it "Unable to infer column types of the file provided"
You can get csv file from https://github.com/LetterFirst/DataSet
To Reproduce

Click "Custom Scenario" and "Select a file"

Screenshots

Thank you for help me!

Please investigate root cause.

Dataset has 10,164 columns.
Currently, the AutoML code has an arbitrary limit of the max number of columns set to 10k.
I thought we had a PR out to change this limit to 200k and add automatic column grouping above 20k, though I can't seem to locate it.

Thank you very much! Have a nice day

Is there a way to find out which cause the infer error from AutoML? (can't find any from source code though). Maybe we can add an infer Error type for that?

I am also getting this error from a CSV file exported with this function
using (var stream = File.Create("c:\\temp\\aidata.csv"))
               mlContext.Data.SaveAsText(trainData, stream);

There are 12 columns and some of them are vector types. The data model is valid as the prediction works.

In my CSV file there are 12 columns and some of them are vector types. The data model is valid as the prediction works.

Can you check if vector value is being put into a pair of double quote, like "[val1, val2, val3]", because CSV uses comma as separator, and without double quote, comma in vector-type value will cause a parser error.

Root cause:
AutoML has a limit of inferring up to 10000 columns, in this case, unselect 200 columns and ModelBuilder will (just) work.
Such problem also exists in ML.Net CLI since it also uses AutoML to do column inference.
Problems.
the user experience is awful when having 9999 columns in model builder, UI is slow and ModelBuilder window will flash when I select label. (though it's not crash thanks to @beccamc 's work)
Proposal

remove the restriction of 10000 in AutoML/ through an error in ModelBuilder when user's column exceeds 10000
Update/improving ModelBuilder Data page to make it work well with dataset with bunch of columns.

This issue is no longer exists. Feel free to close it.

In my CSV file there are 12 columns and some of them are vector types. The data model is valid as the prediction works.

Can you check if vector value is being put into a pair of double quote, like "[val1, val2, val3]", because CSV uses comma as separator, and without double quote, comma in vector-type value will cause a parser error.

sorry for the delay, I missed your questions.
The data is tab delimited with this header
#@ TextLoader{
#@   header+
#@   sep=tab
#@   col=Col1:R4:0
#@   col=Col2:R4:1
#@   col=Col3:R4:2-101
#@   col=Col4:R4:102-201
#@   col=Col5:R4:202-301
#@   col=Col6:R4:302-401
#@   col=Col7:R4:402-501
#@   col=Col8:R4:502-601
#@ }

This is the way ML.Net saves it as CSV/text, and it's very strange that ML itself then cannot process it.

This issue not repro on main branch: https://privategallery.blob.core.windows.net/gallery/refs/heads/main/atom.xml

Windows 10 Enterprise, Version 20H2
ML.Net Model Builder (Preview): <IP_ADDRESS>2903
Microsoft Visual Studio Enterprise 2019: 16.9.4
.Net: 5.0.202

Steps:

Download the data set from: https://github.com/LetterFirst/DataSet
Select Text classification and Local (CPU);
Navigate to Data page, select File and click "Browser..." to load the dataset;
About 15 minutes, the data input is complete.


Can unrelate unrelated a given instance?

Confused about unrelate :(
In the docs I can use relate to connect two instances like this:
const actor = await Person.query().findById(100);
const movie = await Movie.query().findById(200);
await actor.$relatedQuery('movies').relate(movie);

I had expected to be able to unrelate the same way:
const actor = await Person.query().findById(100);
const movie = await Movie.query().findById(200);
await actor.$relatedQuery('movies').unrelate(movie);

That doesn't seem to be possible. Am I missing something?

unrelate() doesn't take arguments. If you run this, you'll get an error: Don't pass arguments to unrelate(). You should use it like this: unrelate().where('foo', 'bar').andWhere(...)
So in your case, you should be able to do:
await actor.$relatedQuery('movies').unrelate(). findById(200);

Or:
await actor.$relatedQuery('movies').unrelate().where({ id: 200 });


feat: nydus support encrypted images

Extend native nydus v6 to support handling encrypted containers images:

An encrypted nydus image is composed of encrypted bootstrap and chunk-level encrypted data blobs. The bootstrap is encrypted by the Ocicrypt and the data blobs are encrypted by aes-128-xts with randomly generated key and iv at chunk-level.
The chunk encryption key and iv are stored in the blob info reusing some items of the structure to save reserved space.
For every data blob, all the chunk data, conpression context. table and compression context table header are encrypted.
Encrypted chunk data will be decrypted first, and then be decompressed while bing fetched by the storage backend.

Related issue

/retest

/retest

The bootstrap is encrypted by the Ocicrypt and the data blobs are encrypted by aes-128-xts with randomly generated key and iv at chunk-level.

What is iv? And I thought we agreed on using convergent encryption for shared chunk data encryption. Any reason why it got dropped?

The bootstrap is encrypted by the Ocicrypt and the data blobs are encrypted by aes-128-xts with randomly generated key and iv at chunk-level.

The IV is used to ensure that the same plaintext block encrypted with the same data encryption key produces a different ciphertext block each time.

The bootstrap is encrypted by the Ocicrypt and the data blobs are encrypted by aes-128-xts with randomly generated key and iv at chunk-level.

What is iv? And I thought we agreed on using convergent encryption for shared chunk data encryption. Any reason why it got dropped?

The IV is used to ensure that the same plaintext block encrypted with the same data encryption key produces a different ciphertext block each time.  It's usually suggested to be provided when using AES in xts mode.
About Convergent encryption you mean CipherContext with convergent_encryption set true? It's not really dropped, the related codes are moved to utils/crypt.rs to make them capable of being more commonly and easily used by storage or rafs subsystems.

@taoohong The implementation looks good. Could you add some integration tests (in the smoke/tests/ directory) so that it is actually tested?

Thanks!

@taoohong The implementation looks good. Could you add some integration tests (in the smoke/tests/ directory) so that it is actually tested?

I'd like to. THX for your review 👍


Implement low-latency togglers for decoder

A user must be able to specify:
parameters:
  decoder_low_latency: True

to enable them.

Jetson-specific switches (disable-dpb, enable-max-performance)
dGPU-specific switches (low-latency-mode)

Docs: https://docs.nvidia.com/metropolis/deepstream/dev-guide/text/DS_plugin_gst-nvvideo4linux2.html
Port to 0.4, 0.5

Play till the badge to see the time skew (~3 sec).

Left: ffplay
Right: ffmpeg adapter + display sink (~ +3 sec)
Screencast from 09-03-2024 05:32:35 PM.webm

Play till the badge to see the time skew (~3 sec).

Those 3 seconds because of SYNC_INPUT=True in Always-On-sink (default value).
Tested on samples/telemetry
Without low-latency decoding:

With low-latency decoding:

Time spent on decoding reduced from 33ms to 1.5ms.
Tested with RTSP stream from local mediamtx server
Without low-latency decoding:

With low-latency decoding:

Delay reduced from 120ms to 80ms.

Cool!


Selecting multiple colors

Great library, thank you 😃
Idea for future feature - it would be nice if we could choose multiple colors in a single dialog.

Glad you're enjoying it!
What's the use case where choosing multiple colors at once would be useful?

In my particular case I need to get few colors from user and send it to server (three favorites colors). I've done this by creating three dialogs, and it's not very bad. Bigger problem is general case I thought about.
General case is filtering content - most of online shop has this option: "show products only in those colors".

Ah, those are indeed valid use cases. That would be a good thing to add to Spectrum.
Do you want to take a stab at it? Otherwise, I can add it to my backlog of things to do.

To be honest with you - I haven't got any experience with building libraries but I would like to take part in Spectrum. I'll try do my best but until end of June I haven't got any free time. Is it ok to start then?

Depending on how much free time I have, I may end up doing this myself to expedite things. I'd love your input on the API design for this though!


🎨 Use relative request instead of absolute

There is no need to hardcode the hostname in the frontend app, one can use relative requests.
Fix #28

Thanks @cristianpb!  See @mkaliberda comments and remove compiled .js files (we'll do that on our side) and we will merge.

Done.
Thanks for the review

Thank you, Cristian @cristianpb !


Custom Payload, Facebook, Include persona_id

According to the relatively new FB Beta Functionality, custom persona_id's can be incorporated into messages, taking the following form (Source: HERE):
curl -X POST -H "Content-Type: application/json" -d '{
  "recipient":{
      "id":"<USER_PSID>"
   },
  "message":{
      "text":"hello world!",
   },
  "persona_id": "<PERSONA_ID>"
 }' "https://graph.facebook.com/me/messages?access_token=<PAGE_ACCESS_TOKEN>"

Now the issue, as far as I can see it, is that in terms of trying to use this new (and potentially highly attractive feature) in the dialogflow-fullfillment-nodejs library, is that when a custom payload is provided (such as outlined HERE)
then it might take the following form:
let message = {"text":"hello world!"}
let payload = new Payload(agent.FACEBOOK, message)
agent.add(payload)

And this prohibits injecting the "persona_id" at the correct nesting level in the overall json packet as specified by the FB documentation.
Any suggestions?

Hi did you manage to find a resolution?


Slow performance of multi_agent_simulation due to high asyncio run calls

Setup Python 3.10 (64bit) on windows 11
While running the simulation after 2620 iteration, simulation code is halted. After investigating with a profiler, main issue seems to be multiple usage of asyncio run calls.

After wrapping the whole execution with a single asyncio run, issue is resolved.

Could you open a PR specific to this issue with your solution?

Some execution times from mac pro m1 before changes 33.1 sec and after changes 22 sec.


Fix broken circle build

More hacks thanks to CircleCI's outdated docker install.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-circle-build3" git@github.com:chungers/infrakit.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354467920
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


arrpc fails to start

Running into an odd issue, installed Arch on my laptop and while aarpc has been working fine on my desktop it fails to start on the laptop, even when using the same package from the AUR. I have installed arrpc (tried arrpc-git too, same result), enabled and started the service using systemctl --user enable --now arrpc.service and got an error message in Vencord that ARRPC could not be detected. Running systemctl --user status arrpc.service return the following:
systemctl --user status arrpc.service
× arrpc.service - arRPC Discord RPC daemon
     Loaded: loaded (/usr/lib/systemd/user/arrpc.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2024-04-22 17:36:27 UTC; 1min 35s ago
   Duration: 81ms
    Process: 52163 ExecStart=/usr/bin/arrpc (code=exited, status=1/FAILURE)
   Main PID: 52163 (code=exited, status=1/FAILURE)
        CPU: 80ms

Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Scheduled restart job, restart counter is at 5.
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Start request repeated too quickly.
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Failed with result 'exit-code'.
Apr 22 17:36:27 arch systemd[5221]: Failed to start arRPC Discord RPC daemon.

And here's the full journalctl log of it failing to start:
Apr 22 17:36:26 arch systemd[5221]: Started arRPC Discord RPC daemon.
Apr 22 17:36:26 arch arrpc[51829]: Pkg: Error reading from file.
Apr 22 17:36:26 arch systemd[5221]: arrpc.service: Main process exited, code=exited, status=1/FAILURE
Apr 22 17:36:26 arch systemd[5221]: arrpc.service: Failed with result 'exit-code'.
Apr 22 17:36:26 arch systemd[5221]: arrpc.service: Scheduled restart job, restart counter is at 1.
Apr 22 17:36:26 arch systemd[5221]: Started arRPC Discord RPC daemon.
Apr 22 17:36:26 arch arrpc[52141]: Pkg: Error reading from file.
Apr 22 17:36:26 arch systemd[5221]: arrpc.service: Main process exited, code=exited, status=1/FAILURE
Apr 22 17:36:26 arch systemd[5221]: arrpc.service: Failed with result 'exit-code'.
Apr 22 17:36:26 arch systemd[5221]: arrpc.service: Scheduled restart job, restart counter is at 2.
Apr 22 17:36:26 arch systemd[5221]: Started arRPC Discord RPC daemon.
Apr 22 17:36:26 arch arrpc[52149]: Pkg: Error reading from file.
Apr 22 17:36:26 arch systemd[5221]: arrpc.service: Main process exited, code=exited, status=1/FAILURE
Apr 22 17:36:26 arch systemd[5221]: arrpc.service: Failed with result 'exit-code'.
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Scheduled restart job, restart counter is at 3.
Apr 22 17:36:27 arch systemd[5221]: Started arRPC Discord RPC daemon.
Apr 22 17:36:27 arch arrpc[52156]: Pkg: Error reading from file.
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Main process exited, code=exited, status=1/FAILURE
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Failed with result 'exit-code'.
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Scheduled restart job, restart counter is at 4.
Apr 22 17:36:27 arch systemd[5221]: Started arRPC Discord RPC daemon.
Apr 22 17:36:27 arch arrpc[52163]: Pkg: Error reading from file.
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Main process exited, code=exited, status=1/FAILURE
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Failed with result 'exit-code'.
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Scheduled restart job, restart counter is at 5.
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Start request repeated too quickly.
Apr 22 17:36:27 arch systemd[5221]: arrpc.service: Failed with result 'exit-code'.
Apr 22 17:36:27 arch systemd[5221]: Failed to start arRPC Discord RPC daemon.

I'm not sure what's causing this, especially since it works out of the box on my PC.

The AUR package is unofficial and makes large changes which are unsupported.

I'm sorry to bump this issue, but what changes could you possibly be referring to?  All I see is an additional systemd unit file.  That is excluding the git package, which even then only seems to define a couple of build flags and a minor patch that shouldn't (though I won't risk saying it certainly wouldn't) change anything behaviorally.

The AUR release that was broken had an extra patch file which, I assume, was causing problems. It has since been removed in the fixed versions and the PKGBUILD will now just build the package without any modification.

The AUR release that was broken had an extra patch file which, I assume, was causing problems. It has since been removed in the fixed versions and the PKGBUILD will now just build the package without any modification.

Yes, that seems to be the case for arrpc-git, though I can't see that patch file in the main package.  Granted, it used to build the project much like the git package is currently still specced to do so minus the patch the latter still employs.  The git package is probably still broken.
Even then, I don't see that many a change going through the changelog for the AUR package.  That just confused me a bit, that's all.


Directory Push

I don't see where this is currently possible, so if it is I apologize, but are there any plans to add the ability to push an entire directory?

It's currently not supported. The original author did not add it. You can upload a single file in a new folder, and it will create the folder correctly in NetSuite. But there's no batch upload at this time.

Hi silverl,
I used vscodeExtensionRestlet.js and added to NS account. I always get error as please update latest version   of vscodeExtensionRestlet.js when i try to push file to NS account.

@email2poornileesa that's a separate issue, so I have created a separate GitHub Issue for it: #25

Directory Push (and possibly excluding .ts files) would be awesome feature for TypeScript developers. Right now I have to switch editor focus in order to push the correct file to NetSuite via shortcut.
Another useful feature would be an option to save the file before pushing it.
I will look into it this weekend and possibly create PR if I figure it out.

Here is the PR

Now live with v1.2.3!


FanGraphs Teams pages

FanGraphs Teams pages:

Summary
Stats
Schedule
Player Usage
Depth Chart

Note: The default team for the FanGraphs Teams pages is the Los Angeles Angels of Anaheim.

Covered Summary, Stats, Schedule, Player Usage, and Depth Chart with Pull Request #30


Support the SparkFun ProMini 5V

This PR adds a new feature to arduino-hal, sparkfun-promini-5v, and a new board to ravedude, promini-5v. It is a copy, in nearly all respects, of the Arduino Nano implementation. I have used this datasheet as reference.
In the ravedude board config SparkFunProMini5V I  have implemented guess_port with a VID/PID pair I derived experimentally from my Pro Mini*, but I'm not sure if that is the correct approach.
Related issue: #425
*It is listed in http://www.linux-usb.org/usb.ids as "FT232 Serial (UART) IC" by FTDI.

An alternative to my implementation of the sparkfun-promini-5v feature in arduino-hal is to have it simply imply the arduino-nano feature (and I prefer this for the sake of maintenance). My belief is that the Pro Mini 5V is functionally an Arduino Nano sans an onboard FT232R.

No worries, and sorry I didn't see your reply until now. I'll commit that change when I get home.


error installation

[%key:common::config_flow::error::unknown%]
set the user,pass and serial this error appears

I have the same error.
The log says:
Traceback (most recent call last):
  File "/config/custom_components/atonstorage/config_flow.py", line 70, in async_step_user
    await self.async_set_unique_id(slugify(controller.serial_number))
                                           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/atonstorage/controller.py", line 214, in serial_number
    return self.data["serialNumber"]
           ~~~~~~~~~^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

Same error for me.

I solved by going to aton website and login. If you have never changed credentials, it will ask for new password (to change default one), then it worked.

I solved by going to aton website and login. If you have never changed credentials, it will ask for new password (to change default one), then it worked.

Confirmed, it also worked for me. Thank you very much


Update steps in surface-hub-manage-config.md

Closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/9549.

Learn Build status updates of commit dbe30e3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/rooms/surface-hub-manage-config.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@dstrome
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


bundle exec srb init crashes in Ruby 3.0.0

Input
.ruby-version
3.0.0

Gemfile
source 'https://rubygems.org'

gem 'sorbet

test.rb
class A
end

Observed output
Run bundle install and then
$ bundle exec srb init

Hey there!

This script will get this project ready to use with Sorbet by creating a
sorbet/ folder for your project. It will contain:

- a config file
- a bunch of 'RBI files'

RBI stands for 'Ruby Interface'; these files define classes, methods, and
constants that exist, but which Sorbet doesn't always know about.

Heads up:

To set up your project, this script will take two potentially destructive
actions:

1.  It will require every file in your project. Specifically, every script in
    your project will be run, unless that script checks if __FILE__ == $PROGRAM_NAME
    before running any code, or has the magic comment # typed: ignore in it.

2.  It will add a comment to the top of every file (like # typed: false or
    # typed: true, depending on how many errors were found in that file.)

Would you like to continue? [Y/n]
Generating: sorbet/config
Reusing existing config file: sorbet/config
Generating: sorbet/rbi/sorbet-typed/
Generating: sorbet/rbi/gems/
LoadError: cannot load such file -- sorbet
LoadError: cannot load such file -- sorbet-static
/home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6111/lib/gem-generator-tracepoint/tracepoint_serializer.rb:35:in `initialize': wrong number of arguments (given 1, expected 0; required keywords: files, delegate_classes) (ArgumentError)
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6111/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6111/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6111/lib/gem-generator-tracepoint.rb:43:in `main'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6111/bin/srb-rbi:232:in `block in make_step'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6111/bin/srb-rbi:118:in `init'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6111/bin/srb-rbi:196:in `main'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6111/bin/srb-rbi:237:in `<main>'

Expected behavior
It shouldn't crash :)

It works as expected in 2.7.2
I really expected this issue to exist and I looked for duplicates but couldn't find any. Sorry if this is known!

I faced that issue when trying to reproduce a similar error I get on my actual ruby project
/home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast/node_pattern/compiler/node_pattern_subcompiler.rb:16:in `initialize': wrong number of arguments (given 2, expected 1) (ArgumentError)
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast/node_pattern/compiler.rb:47:in `compile_as_node_pattern'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast/node_pattern.rb:65:in `initialize'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast/node_pattern.rb:37:in `def_node_matcher'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast/node.rb:275:in `<class:Node>'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast/node.rb:21:in `<module:AST>'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast/node.rb:4:in `<module:RuboCop>'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast/node.rb:3:in `<top (required)>'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast.rb:26:in `require_relative'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop/ast.rb:26:in `<top (required)>'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop-ast.rb:3:in `require_relative'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-ast-1.3.0/lib/rubocop-ast.rb:3:in `<top (required)>'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-1.7.0/lib/rubocop.rb:14:in `require'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rubocop-1.7.0/lib/rubocop.rb:14:in `<top (required)>'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem_loader.rb:1206:in `require'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem_loader.rb:1206:in `require_gem'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem_loader.rb:1235:in `block in require_all_gems'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem_loader.rb:1233:in `each'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem_loader.rb:1233:in `require_all_gems'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/require_everything.rb:39:in `load_bundler'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/require_everything.rb:19:in `require_everything'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem-generator-tracepoint.rb:39:in `block in main'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem-generator-tracepoint/tracer.rb:70:in `trace'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/lib/gem-generator-tracepoint.rb:38:in `main'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/bin/srb-rbi:232:in `block in make_step'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/bin/srb-rbi:118:in `init'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/bin/srb-rbi:196:in `main'
        from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6188/bin/srb-rbi:237:in `<main>'

This is because of the kwargs change I believe, because if you run it on 2.7 with deprecation warnings enabled it will warn you about the same lines.

The current code that has the deprecation warning looks like this:
def new(*)
  result = super
  Sorbet::Private::GemGeneratorTracepoint::Tracer.on_module_created(result)
  result
end

As far as I can tell, the new(*) is fully equivalent to new(*args).
The problem is that we're trying to do method delegation in a way that Ruby 3 doesn't like.
The best fix I can come up with is to use ruby2_keywords:
# Add ruby2_keywords (will need a method defined on Ruby versions
# before 2.7 that stubs ruby2_keywords so it'll work). See the
# "compatible delegation" section in this blog post:
# https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/
ruby2_keywords def new(*args)
  result = super
  Sorbet::Private::GemGeneratorTracepoint::Tracer.on_module_created(result)
  result
end

Eventually this can be updated to new(...) once we support only Ruby 2.7+.

I've opened a PR to fix this, but unfortunately it still won't work on Ruby 3 since there's another issue with sorted_set raising an error when trying to run it 😒
It does make it further into the hidden definitions generation process, though!

Heh that's a step forward! Do you have a general "support ruby 3.0" issue I can follow or should I report new issues at each problem I hit?

I'll open a generic 'support ruby 3.0' ticket :)

I've opened #3851

Hi @jez :wave:
Are the changes supposed to be included in https://github.com/sorbet/sorbet/releases/tag/0.5.6249.20210126165344-49e284886 ?
It didn't solve the problem for me, running the same steps as the original issue
Generating: sorbet/config
Generating: sorbet/rbi/sorbet-typed/
Generating: sorbet/rbi/gems/
LoadError: cannot load such file -- sorbet
LoadError: cannot load such file -- sorbet-static
/home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/lib/gem-generator-tracepoint/tracepoint_serializer.rb:35:in `initialize': wrong number of arguments (given 1, expected 0; required keywords: files, delegate_classes) (ArgumentError)
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/lib/gem-generator-tracepoint.rb:43:in `main'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/bin/srb-rbi:232:in `block in make_step'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/bin/srb-rbi:118:in `init'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/bin/srb-rbi:196:in `main'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/bin/srb-rbi:237:in `<main>'

Hi @jez :wave:
Are the changes supposed to be included in https://github.com/sorbet/sorbet/releases/tag/0.5.6249.20210126165344-49e284886 ?
It didn't solve the problem for me, running the same steps as the original issue
Generating: sorbet/config
Generating: sorbet/rbi/sorbet-typed/
Generating: sorbet/rbi/gems/
LoadError: cannot load such file -- sorbet
LoadError: cannot load such file -- sorbet-static
/home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/lib/gem-generator-tracepoint/tracepoint_serializer.rb:35:in `initialize': wrong number of arguments (given 1, expected 0; required keywords: files, delegate_classes) (ArgumentError)
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/lib/gem-generator-tracepoint/tracer.rb:40:in `new'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/lib/gem-generator-tracepoint.rb:43:in `main'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/bin/srb-rbi:232:in `block in make_step'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/bin/srb-rbi:118:in `init'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/bin/srb-rbi:196:in `main'
	from /home/dee-see/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/sorbet-0.5.6249/bin/srb-rbi:237:in `<main>'

Odd, that works for me when I run bundle exec srb rbi hidden-definitions (well, it works until I hit an issue with sorted_set, but that's a separate thing), but I seem to run into a different error when running srb init:
Connors-MacBook-Pro-2:vglist connorshea$ CI=true bundle exec srb init

👋 Hey there!

This script will get this project ready to use with Sorbet by creating a
sorbet/ folder for your project. It will contain:

- a config file
- a bunch of 'RBI files'

RBI stands for 'Ruby Interface'; these files define classes, methods, and
constants that exist, but which Sorbet doesn't always know about.

⚠  Heads up:

To set up your project, this script will take two potentially destructive
actions:

1.  It will require every file in your project. Specifically, every script in
    your project will be run, unless that script checks if __FILE__ == $PROGRAM_NAME
    before running any code, or has the magic comment # typed: ignore in it.

2.  It will add a comment to the top of every file (like # typed: false or
    # typed: true, depending on how many errors were found in that file.)

❔ Would you like to continue? [Y/n] y
Generating: sorbet/config
Reusing existing config file: sorbet/config
Generating: sorbet/rbi/sorbet-typed/
Generating: sorbet/rbi/gems/
/Users/connorshea/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/binding_of_caller-1.0.0/lib/binding_of_caller/mri.rb:21: [BUG] Segmentation fault at 0xfffffffffffffff0
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin19]

-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports
   for more details.
Don't forget to include the above Crash Report log file in bug reports.

This script will get this project ready to use with Sorbet by creating a
sorbet/ folder for your project. It will contain:

- a config file
- a bunch of 'RBI files'

RBI stands for 'Ruby Interface'; these files define classes, methods, and
constants that exist, but which Sorbet doesn't always know about.

⚠  Heads up:

To set up your project, this script will take two potentially destructive
actions:

1.  It will require every file in your project. Specifically, every script in
    your project will be run, unless that script checks if __FILE__ == $PROGRAM_NAME
    before running any code, or has the magic comment # typed: ignore in it.

2.  It will add a comment to the top of every file (like # typed: false or
    # typed: true, depending on how many errors were found in that file.)

❔ Would you like to continue? [Y/n] y
Generating: sorbet/config
Reusing existing config file: sorbet/config
Generating: sorbet/rbi/sorbet-typed/
Generating: sorbet/rbi/gems/
/Users/connorshea/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/binding_of_caller-1.0.0/lib/binding_of_caller/mri.rb:21: [BUG] Segmentation fault at 0xfffffffffffffff0
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin19]

-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports
   for more details.
Don't forget to include the above Crash Report log file in bug reports.

 Ruby 3.0.0, Sorbet 0.5.6292. Is there a workaround or do I switch to Tapioca?

Same issue here, Ruby 3.0.1p64. Literally just started a new ruby project with one ruby file and bundle exec srb init fails with same error message @dee-see described.

Getting the same problem as @dee-see , on 0.5.9318, also ruby 3.0.1p64.

Getting same problem with ruby 3.1

I'm facing the same issue using sorbet 0.5.9553 and ruby 3.0.1p64 I was able to fix it locally by changing TracepointSerializer.new(*trace_results).serialize(output_dir) to TracepointSerializer.new(**trace_results).serialize(output_dir) on lib/gem-generator-tracepoint.rb not sure if thats the a actual fix or it just works for me.
I'm running bundle exec srb rbi gems


Added ps_mem for Python

It is a utility to display the memory consumed by program(s) in an order.

Hi! Sorry, but cannot be merged, because the last commit was more than two years ago.

:+1:
When I checked, the last commit was 3 months ago on ps_mem.py .
And also it is completely compatible with modern machines.


Release 1.12.8 patch

Please provide a description of this PR:

@myidpt: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Record key readability

Currently, the extracted raw data has the UUIDs for the key.userId and key.sourceId fields. I realize how this makes sense (automatic processing within the platform later on, e.g. for plotting), and I don't necessarily want to change that. However, it leaves the data somewhat "unreadable" in my opinion, for data processing and analysis.
Is there currently a way to programmatically map from these UUIDs to a human readable string?
E.g. in the MP you can specify a human-readable-identifier for subjects, and a source name for sources. I suppose the direct way would be to make a handwritten csv that maps these fields, and whenever I am processing the data, e.g. in matlab, to first read that and process by that.
Alternatively,

is there already a way to get a mapping csv or similar during the restructuring? Or separately, get it from the MP?
could there be an option to replace the UUIDs with their readable names during restructuring? Is there even a connection between the restructuring and the MP?

There is currently no connection between MP and the restructuring script. Using the user ID is the canonical way to map users and ensure their uniqueness and presentness. In Git, a common way around showing long hashes is to display only the first 7 characters of a hash, with the possibility of collisions. For display purposes it is usually fine.
Otherwise, perhaps a contribution to https://github.com/RADAR-base/pyRADAR-processing would be helpful, to automatically preprocess files and change the usernames according to the exported data of a managementportal instance. Or an extension to that project to include some common Matlab functionality as well?


Importing into single existing table?

Hi! I have used this feature of importing flat files in order to create new tables however I was wondering if there is a way to import flat files into an existing (empty) table to populate the table? Is there a way to accomplish this?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d89ecc7f-4705-dabe-9f70-2070d4aa19c9
Version Independent ID: 9c991bd5-535c-03b5-d810-c1b2ca7e7cb4
Content: Import Flat File to SQL - SQL Server
Content Source: docs/relational-databases/import-export/import-flat-file-wizard.md
Product: sql
Technology: data-movement
GitHub Login: @yualan
Microsoft Alias: alayu

Hi Dan, not at this time, but it is definitely a feature request we can consider in the future.


Pin rainbow and nokogiri gems to known good versions

I have pulled this branch locally, running bundle update now...

Thanks Mike. Forgot to test with ruby 2.0. Fixed the above comments, as well as google-cloud-trace, and retested rake bundleupdate on ruby 2.0 and ruby 2.3.3.

Same, works for me locally.

Thanks guys.


Redirect Analysis

Hi,
we have a vast amount of http redirects and want to analyse which of the configured redirects is still being used.
We are using httpd and have a custom log format contains:

http host of the request
http uri of the request
http referer of the request
http location of the response

Is it possible to analyse that with GoAccess?
Thanks,
Robert

It sounds like goaccess should be able to parse your log without issues. It would be great if you can post a few sample lines from your access log to come up with a possible log-format.

Any updates on this?

Hi Gerardo,
currently I cannot provide logs as we are still planning.
Your answers enabled me to use GoAccess for the reporting.
Thanks!


Incorrect JSON format during Pytorch Execution Trace generation

Bug Description
I am running a distributed Linear model (20 parameters) across 2 GPU Nodes, each node having 2 NVIDIA H100 NVL GPUs. The Model uses DDP parallelization strategy.  I am generating the Pytorch ET (in json format) trace using the ExecutionTraceObserver() as mentioned in the instructions.  I observe that the trace has many syntactical errors. Also, many nodes have incomplete data (images attached)
I tried this with the latest Pytorch version (2.5.0) as well but encountered the same problem.
Steps to Reproduce
Code used for distributed training: https://github.com/pytorch/examples/tree/main/distributed/ddp-tutorial-series
Command to run across both nodes:
torchrun  --nproc_per_node=2 --nnodes=2 --node_rank=0 --rdzv_id=456 --rdzv-backend=c10d --rdzv_endpoint=<ip:port> <code>.py <no. of epochs> <epochs after which result will be saved>
I am capturing the ET trace for one epoch.
Information for one GPU Node (Both nodes have the same configuration):
Pytorch: 2.1.2 , 2.5.1 (tried both)
OS: Linux
Kernel version: 5.15.0-124-generic
Ubuntu Version: Ubuntu 22.04.5
No. of CPUs : 64
CPU Architecture:  x86_64
CPU op-mode(s): 32-bit, 64-bit
CPU Address sizes:  52 bits physical, 57 bits virtual
CPU Byte Order: Little Endian
Memory: 503Gi
No. of GPUs: 2
GPU Memory (each GPU): 95830MiB
I would be obliged if someone could help in this regard.
Screenshots

Hey, try collecting smaller traces from pytorch's execution trace observer. Try collecting one iteration and you get valid json.
This is a pretty annoying quirk of the execution trace observer serializer

I did try this for a single epoch though.


[CAMEL-19698] [CAMEL-19699] camel-yaml-dsl: schema: Restrict language…

…s/dataformats to be mutually exclusive

Added oneOf property on @YamlProperty annotation. This is to hold an oneOf grouping name to show those are mutually exclusive on deserializer annotation
Let schema generator use the oneOf to express mutually exclusiveness using schema composition
Redeclare the properties inherited through schema composition. This is required when additionalProperties is set to false

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

https://issues.apache.org/jira/browse/CAMEL-19698
https://issues.apache.org/jira/browse/CAMEL-19699

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

Tested with vscode-yaml plugin, got expected validation errors


Fix/improving converter

Small improvements on the converter.
Points addressed:

[x] Improved compatibility with Mechanical ds.dat output file.
[x] Improved coverage
[x] Small general improvements.

Close #808

I'll be fixing the docs build in in a #861. Hold of working on this or fixing the docs.

@akaszynski  in my case the building was failing because of format issues (forgot to backscape).

I'm still investigating the issues about the "-1".

Thank you Alex.
Apologies for the style errors, I should be more careful with those.


Add subtitle support to Table

Current Table component only supports a title. Add support for subtitle:

This should include a Storybook entry.

I would like to work on it 👍

@ayshiff thanks! I have Assigned you.


mention OctoAPI

I've just released my library - OctoAPI - an JSON API abstraction layer to use in iOS projects written in Swift and I am using a built-in Gloss data parser in it.
Can you add a mention about it to your list of Libraries using Gloss? :)

of course!

but could you make the PR against develop instead of master ? develop is the landing page so it'll show immediately and it'll make it's way into master next release

Sure, I was wondering where to put it :)

Changed.


gui: hint at rescan when importing wallet

This is to resolve #866.
I've added the message to the first step where the user enters the descriptor:

Changed to draft as I will also do #791 as part of this PR.

Changed to draft as I will also do #791 as part of this PR.

That issue has now been closed.

ACK 09cf4f4c1f9da5ec8593ea022b1ec58f2dbd05f3 based on the screenshot in the OP. Haven't tested nor reviewed the code.


fix: @invertase Fix missing uuid import for 0.9 RC

This PR addresses the missing uuid dependency issue reported in 0.9 RC. It ensures that uuid is properly installed in the required packages. The changes include adding uuid to the necessary package.json files and updating related imports.
Changes:
Added uuid to missing dependencies.
Updated relevant code to ensure uuid is correctly imported and used.

Sorry, can you point me to where we use uuid in these respective packages? I'm not seeing it.

Hi.
grep -rl "uuid" --exclude-dir={node_modules,dist,lib}
I installed to the nearest package.json in order to make sure it is not missing as it happened in more than 1 situation.
The full script is here, if you want to give it a look:
const fs = require('fs');
const path = require('path');
const { execSync } = require('child_process');
let uuidReferences;
try {
uuidReferences = execSync('grep -rl "uuid" --exclude-dir={node_modules,dist,lib} .', {
encoding: 'utf-8',
})
.trim()
.split('\n')
.filter((file) => file);
} catch (error) {
console.error('No references to "uuid" found.');
process.exit(0);
}
const missingDepsByDir = new Map();
uuidReferences.forEach((filePath) => {
const packageDir = findNearestPackageJsonDir(filePath);
const packageJsonPath = path.join(packageDir, 'package.json');
if (!isUuidInDependencies(packageJsonPath)) {
if (!missingDepsByDir.has(packageDir)) {
missingDepsByDir.set(packageDir, new Set());
}
missingDepsByDir.get(packageDir).add('uuid');
}
});
missingDepsByDir.forEach((deps, dir) => {
console.log(Installing in ${dir}: ${Array.from(deps).join(', ')});
try {
const relativeDir = path.relative(process.cwd(), dir);
execSync(
pnpm add ${Array.from(deps).join(' ')} --filter ${relativeDir || '.'},
{
stdio: 'inherit',
}
);
} catch (error) {
console.error(Failed to install dependencies in ${dir}:, error.message);
}
});
console.log('All missing uuid dependencies installed.');
function findNearestPackageJsonDir(filePath) {
let dir = path.dirname(filePath);
while (dir !== path.parse(dir).root) {
if (fs.existsSync(path.join(dir, 'package.json'))) {
return dir;
}
dir = path.dirname(dir);
}
throw new Error(No package.json found for ${filePath});
}
function isUuidInDependencies(packageJsonPath) {
const packageJson = JSON.parse(fs.readFileSync(packageJsonPath, 'utf-8'));
return (
(packageJson.dependencies && packageJson.dependencies['uuid']) ||
(packageJson.devDependencies && packageJson.devDependencies['uuid'])
);
}

This is addressing https://github.com/firebase/genkit/issues/1184

These testapps and samples do not use uuid therefore do not need the import. I think there's a different root cause of https://github.com/firebase/genkit/issues/1184 and this is not a fix for it.

These testapps and samples do not use uuid therefore do not need the import. I believe the root cause of #1184 is from something else, and this is not a fix for it.

You still had the issue with this update? I did not. My bad.

These testapps and samples do not use uuid therefore do not need the import. I believe the root cause of #1184 is from something else, and this is not a fix for it.

You still had the issue with this update? I did not. My bad.

Nope, was just reviewing the PR :) Glad that it's not an issue anymore (in that case, feel free to close the PR!).


kube?

I saw you starred kube recently. I would really love to hear your thoughts on it.

Haven't fully evaluated live, but I am really interested in hyperbova. However, haven't yet gotten it working. As soon as I do, expect a hypernova starter

Haven't fully evaluated live, but I am really interested in hyperbova. However, haven't yet gotten it working. As soon as I do, expect a hypernova starter

Apologies for horrible spelling mistakes.....at the clubbbbb :fire:

no worries have fun. hypernova looks pretty cool. tackling some of the same
problems. does it also handle hmr?
On Sat, Jun 11, 2016, 9:47 PM Jared Palmer<EMAIL_ADDRESS>wrote:

Apologies for horrible spelling mistakes.....at the clubbbbb 🔥
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jaredpalmer/react-production-starter/issues/83#issuecomment-225410004,
or mute the thread
https://github.com/notifications/unsubscribe/AA-UtnChjActQSnlGcbeb9FAPGLf4lMbks5qK49OgaJpZM4IzrYp
.


Is there a way to overwrite how a field is deserialized?

I have a field in Django models that is an integer, but the value that is returned from an API is a JSON, and I need to grab the value out of it. See example below:
# models.py

class MyModel(models.Model):
    my_field = models.IntegerField(default=0)

# schemas.py
class MySchema(ModelSchema):
    class Config:
        model = MyModel

# API response:
resp = {
    "my_field": {"value": 42}
}

# error happens here
data = MySchema.parse_obj(resp)

Is there a way to overwrite individual field's handling for deserialisation?

Never mind, I figured it.
I was able to do this:
# schemas.py
class MySchema(ModelSchema):
    class Config:
        model = MyModel

    @validator('my_field', pre=True, check_fields=False, allow_reuse=True)
    def validate_my_field(cls, value, values, config, field):
        return value.get('value')

The key was having the pre=True inside the decorator, which runs before default validators kick in.


BigInt support for u256/i256 numbers

What problem does your feature solve?
Operations involving large integers are pretty frequent in cryptography, it might be good to add u256 support for parsing large numbers into BigInt.
What would you like to see?
Possibly a BigInt::from_u256() method, or a BigInt::parse.

@jayz22 originally added host functions to construct a BigInt from a big endian array. We didn't have a use for it at the time, but it seems like this is a good use case. Here's how I think this could all fit together

re-add those host functions
add a macro to the SDK like bigint!("...digits...") that converts the digits to the appropriate array at compile time and then calls the host function

One way the host functions could be designed would be to go from Bytes to BigInt. Then we can use linear memory to construct the Bytes where possible, making everything relatively efficient when hard-coded constants are available but also still usable when values are dynamic.
Does the developer-facing interface bigint! sound reasonable to you @heytdep?

I realized I missed a detail. We would also need to expose a BigInt::from_bytes function (or equivalent using traits) that can be used in the dynamic case, and that can be used behind the scenes by bigint!.

a macro for that seems just what's needed, so to make sure I understand clearly:

the bigint! macro converts the number into an array
the host will know that the array corresponds to a number and will construct a BigInt from that?

Also, say the let big_num = bigint!("0x0999e3730d9a8120caea0a065b8ce05577ba27f61ca315f06e212b647a9c93e8") would have the BigInt type or the type of a slice/vector?

That's basically right, except the macro would explicitly tell the host that it's a BigInt. The intention is that let big_num = bigint!("0x0999e3730d9a8120caea0a065b8ce05577ba27f61ca315f06e212b647a9c93e8") would have type BigInt. Trying to get a bit more specific, the bigint! macro would work something like the following

convert the digits to a [u8]
use Bytes::from_array on the [u8] to construct a Bytes
use BigInt::from_bytes on the Bytes to construct a BigInt

if that makes sense?

I'll work on adding them back to the host (maybe sdk too), should be straightforward.

Also, say the let big_num = bigint!("0x0999e3730d9a8120caea0a065b8ce05577ba27f61ca315f06e212b647a9c93e8") would have the BigInt type or the type of a slice/vector?

We have a bytes! macro that accepts a byte array and creates a Bytes, but it might be convenient to have a hex version of this as I think you're hinting at. I created https://github.com/stellar/rs-soroban-sdk/issues/499 for that separate issue.

Implemented in https://github.com/stellar/rs-soroban-sdk/pull/501.
Example usage:
let env = Env::default();

let big = bigint!(&env, 0xfded3f55dec47250a52a8c0bb7038e72fa6ffaae33562f77cd2b629ef7fd424d);
assert_eq!(big.bits(), 256);

let big = bigint!(&env, -5);
assert_eq!(big.to_i64(), -5i64);


Error processing bit 55 - mci_ipm_encode

Execution Parameters:
mci_ipm_encode T112 -o T112_T --in-format 1014 --out-format 1014 --in-encoding cp500 --out-encoding latin_1 --debug
Error:
...
DEBUG:cardutil.iso8583:processing bit 49
DEBUG:cardutil.iso8583:986
DEBUG:cardutil.iso8583:processing bit 55
DEBUG:cardutil.iso8583:b'\x82\x02\x19\....' (removed the rest)
DEBUG:cardutil.mciipm:bytes_to_write=b'\x00\x00\x00\x00'
DEBUG:cardutil.mciipm:len->4<858
DEBUG:cardutil.mciipm:write b'\x00\x00\x00\x00'
Traceback (most recent call last):
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\Scripts\mci_ipm_encode.exe\__main__.py", line 7, in <module>
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\cardutil\cli\mci_ipm_encode.py", line 9, in cli_entry
    cli_run(**vars(cli_parser().parse_args()))
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\cardutil\cli\mci_ipm_encode.py", line 26, in cli_run
    mci_ipm_encode(in_file, out_file=out_file, **kwargs)
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\cardutil\cli\mci_ipm_encode.py", line 61, in mci_ipm_encode
    writer.write_many(reader)
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\cardutil\mciipm.py", line 587, in write_many
    self.write(record)
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\cardutil\mciipm.py", line 576, in write
    record = iso8583.dumps(obj, encoding=self.encoding, iso_config=self.iso_config)
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\cardutil\iso8583.py", line 108, in dumps
    output = _dict_to_iso8583(obj, iso_config, encoding, hex_bitmap)
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\cardutil\iso8583.py", line 248, in _dict_to_iso8583
    output_data += _field_to_iso8583(
  File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\cardutil\iso8583.py", line 275, in _field_to_iso8583
    output += format(field_value[:field_length], '<' + str(field_length))
TypeError: unsupported format string passed to bytes.__format__

What can be adjusted?
Thanks!

I'll need enough information to recreate the issue. If possible provide desensitised data that causes the issue. If parsing DE55 is the issue, then I would need the full DE55 element.

I'll need enough information to recreate the issue. If possible provide desensitised data that causes the issue. If parsing DE55 is the issue, then I would need the full DE55 element.

I sent you the DE55 example in your email.

I have added some additional debugging statements to the master branch. If you could rerun after installing from source and send me the debug messages, I'll be able to see what is causing the issue and work out next steps.
pip install git+https://github.com/adelosa/cardutil

Thanks for reporting the issue and providing the debug information. I have now been able to recreate the issue.
The issue is that the function that converts the data to the required ISO format did not expect to process a bytes based field. Generally all fields in the dict are not bytes... except DE55, the ICC field which is a binary field.
I will be pushing an update so that it leaves the byte field as is rather than formatting it.
If you find fields missing in the output, it's probably because of the use of both PDS and DE fields in the conversion. See warning in https://adelosa.github.io/cardutil/cli.html#mci-csv-to-ipm.
The encode function you are using first goes from iso to python dict which will contain both DE and PDS fields and then send the result to dict to iso which will be impacted by this constraint.
You can strip PDS fields being output via a custom configuration (remove the field processors = PDS)
Will push a new commit shortly to master branch - you can test it to ensure it resolves your issue and let me know.
I will then push out a new minor release of the tool.

The CLI does not have a custom bit config option. I have updated the CLI to strip any PDS field processors to ensure you don't hit any issues with the encode. Let me know how you go.

Hello, I will only be able to test it on Tuesday.  As soon as I have the results I will let you know.  thank you very much!

Hello, I updated cardutil here to the latest version and using the same T112 file, it still gives the error, is it something I still need to change?
mci_ipm_encode T112_T -o T112_T_ASC --in-format 1014 --out-format 1014 --in-encoding cp500 --out-encoding latin_1 --debug
File "C:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\cardutil\iso8583.py", line 275, in _field_to_iso8583
     output += format(field_value[:field_length], '<' + str(field_length))
TypeError: unsupported format string passed to bytes.__format__

Did you install from source? I have not updated the release yet.
Use 'pip install git+https://github.com/adelosa/cardutil'

Yes, I did it using that same command.

Hi, now everything works, thank you very much for your help.

The goal was to use: --in-format 1014 --out-format 1014 --in-encoding cp500 --out-encoding latin_1 this worked perfectly now.
I tested --in-format 1014 --out-format vbs --in-encoding cp500 --out-encoding latin_1 and it returns an error but in other places, if you want to look, you can see it in the same test file that I sent .

Happy to have a look at that. If you can send me debug details that would be great (here or later).
I'll push a release for this fix and raise a new issue for format conversion.

Thanks for the test file. Was able to recreate the second issue and fixed it. Seems I had the input and output formats mixed up on the CLI command - so input was output and vice versa. Fixed and rerun - working now. Will push out a release shortly.

Release 0.6.4 has fixes for both the issues identified.


Add registration functions to support custom names for workflows/activities

Coverage remained the same at 98.5% when pulling 98e52add44dc900698ed186d8e173b3b9adce8be on extName into a22b56d66fac1c8f2b41bba02cf63bd91c19fc98 on master.

Coverage remained the same at 98.5% when pulling 136defc7781911691814934fea6d37c437538eee on extName into a22b56d66fac1c8f2b41bba02cf63bd91c19fc98 on master.

Coverage remained the same at 98.5% when pulling 136defc7781911691814934fea6d37c437538eee on extName into a22b56d66fac1c8f2b41bba02cf63bd91c19fc98 on master.

Coverage remained the same at 98.5% when pulling eff455570b4a07d8a28e67cd24281b8533367a76 on extName into a22b56d66fac1c8f2b41bba02cf63bd91c19fc98 on master.

Coverage remained the same at 98.5% when pulling 6f0f18b256e2ee4eaa3677465c2b1a71441c980e on extName into a22b56d66fac1c8f2b41bba02cf63bd91c19fc98 on master.

Coverage remained the same at 98.5% when pulling b3d6f72c601bb1060a1a05943ce61621a0c54f58 on extName into a22b56d66fac1c8f2b41bba02cf63bd91c19fc98 on master.

Coverage remained the same at 98.5% when pulling 15cfc97d8437c1805d0a812cc8d14ecce57fa98a on extName into a22b56d66fac1c8f2b41bba02cf63bd91c19fc98 on master.

Coverage decreased (-6.4%) to 92.086% when pulling 7578cab7addcf5ae3c804133f1e0730acc634fea on extName into a22b56d66fac1c8f2b41bba02cf63bd91c19fc98 on master.

Coverage remained the same at 98.5% when pulling 7578cab7addcf5ae3c804133f1e0730acc634fea on extName into a22b56d66fac1c8f2b41bba02cf63bd91c19fc98 on master.


Migrate from npm to yarn package manager

Is there an existing issue that is already proposing this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe it
Normally using of Yarn. But this package use only NPM.
Describe the solution you'd like
It would be good, to switch the pacakge manager from npm to yarn. So that's everything is same.
Yarn can be used add and remove pacakges.
NPM only for publishing this package.
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
No difference of all NodeJS projects.

Steps:

[ ] Remove package-lock.json
[ ] Set Yarn version to berry

[ ] yarn set version berry

[ ] Switch nodeLinker

[ ] yarn.yml (nodeLinker: node_modules)

[ ] Install all dependencies

[ ] yarn install

[ ] Update package.json to allow Yarn

[ ] Minimum version of yarn >= 3.6.0

[ ] Update README.md
[ ] Update GitHub Workflow 'Publish Package to NPM registry'

[ ] npm ci :arrow_right: yarn install --immutable


The from parameter is invalid

Hi, I tried to send whatsapp message using this script:
https://github.com/Vonage/vonage-curl-code-snippets/blob/692ef9cf6aecb6ef6fe8bd07ffc0f0ab7aa1527f/messages/whatsapp/send-text.sh
But I met following error:
{"title":"Invalid sender","detail":"The from parameter is invalid.","instance":"b39ef3a0-bf2f-4850-b2f1-6dd407b73c8c","type":"https://developer.nexmo.com/api-errors/messages#1120"}
Please help me!!!
I see no issue on my end.

WhatsApp messages can only be sent by businesses that have been approved by WhatsApp.
Please read more here: https://developer.vonage.com/en/messages/concepts/whatsapp?source=messages


JsonSerializeOptions race condition

It looks like we may have a race condition between a KubeOps client performing cluster operations with their client and our KubernetesClient.cs implementation with the static constructor that configures the JSON serializer to recognize [EnumMember] attributes, etc.
This problem is that we assumed that our code would be the only place where Kubernetes clients were being created, but this is not the case for operators, where KubeOps actually creates its client first.

There isn't really a totally transparent way to handle this, but I think we can come close:

[ ] Add a public static KubernetesClient.Initialize() method that initializes the JSON serializer and protects against multiple calls.  Have the static KubernetesClient() constructor call that.

[ ] Modify NeonService to scan the appdomain for the Neon.Kube assembly and when found have it reflect the new KubernetesClient.Initialize() method and call it.

This change will make all services derived from NeonService work automatically and for other situations, the application can call KubernetesClient.Initialize() manually.

FIXED


can we relate type field to some other fields in faker?

This one is complicated we should put it on Q3 roadmap

Cool, i said the same to the user.

Solution  is to take from :
type Cat{
  image:String!
}

image will generate random image so we should consider generating from Cat.image instead of image


Arrange the social media icons in footer to center.

About issue
The social media icons in the footer are not centered align
Solution
I will align the icons to the center.
Please assign this issue to me under GSSOC 23.

Sure @vikasjain2003 ..go ahead..pls submit your PR by today itself so that we can merge it without conflicts!

Sure Monalika, I will do it by today itself.
Thanks & Regards
On Fri 26 May, 2023, 12:40 Monalika Patnaik, @.***>
wrote:

Assigned #329 https://github.com/MonalikaPatnaik/UMatter/issues/329 to
@vikasjain2003 https://github.com/vikasjain2003.
—
Reply to this email directly, view it on GitHub
https://github.com/MonalikaPatnaik/UMatter/issues/329#event-9347242724,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUZRYPCFMGJVIZYFNLFGLB3XIBJP7ANCNFSM6AAAAAAYNLENGQ
.
You are receiving this because you were assigned.Message ID:
@.***>

Hey..what's the status?

@MonalikaPatnaik I want to contribute in this could you please assign this issue to me

Hey @vikasjain2003 let me know do u want to work on this issue?

Hey @MonalikaPatnaik/UMatter
@.***> please
assign this issue to someone else as I am having facing some problems
regarding the solution of this issue.
On Sat 27 May, 2023, 16:11 Monalika Patnaik, @.***>
wrote:

Hey @vikasjain2003 https://github.com/vikasjain2003 let me know do u
want to work on this issue?
—
Reply to this email directly, view it on GitHub
https://github.com/MonalikaPatnaik/UMatter/issues/329#issuecomment-1565340340,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUZRYPHLJ7MHTLSTX6FOCEDXIHK5LANCNFSM6AAAAAAYNLENGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@nehabulakhe would u like to work on this?


Timegraph: Tooltips as overlay boxes

When clicking in an element in the timegraph's chart, and overlay box is
displayed with the tooltip of the selected element.
Signed-off-by: Soukaina Moussaoui<EMAIL_ADDRESS>

Can we have a floating tooltip? The current one blocks view of the timegraph chart.

Thanks. Feature implemented by #283.


Support for seach by URL

I'd like to add TLDR to my browser as a search engine which would require an endpoint to navigate to. I could do something like https://tldr.inbrowser.app/pages/common/%s, but that wouldn't work for everything.

https://tldr.inbrowser.app/search/activate-site-search

Oh cool, thank you! It'd be nice if that was publicized in some way, maybe

Is there a suggest URL?

https://github.com/InBrowserApp/tldr.inbrowser.app/blob/main/public/opensearch.xml
https://tldr.inbrowser.app/search?query={searchTerms}


Feature request: Hide/Destroy all popovers

Hey,
is there a possibility to hide all popovers?
I want to hide them when starting to scroll ...
Greetings

Use:
$(".popover").webuiPopover('hide');

I need something like each webuiPopover('destroy') but the popover is attached to different handles so i would have to target each dom element...
A global function would be nice to remove all popovers.

I've added this feature.


Move Error Reporting prepend.php to logging component

I just tested the prepend.php file in the cloud-errorreporting component, and was able to get it to work without gRPC installed. Also, looking at the files, it doesn't actually seem to use the ErrorReportingClient anywhere. It would make more sense to move prepend.php and ErrorReporting\Bootstrap.php to the Logging component. This will users to install just the Logging component, and get logging and exception handling, rather than requiring both gRPC AND the Error Reporting client, for seemingly no reason.
Additionally, these files require the Logging component, but logging is not required in the Error Reporting's composer.json.
This can be done in a BC-compatible way, if that's desirable. Because it already "depends" on the logging component, we can just mark the existing two files as deprecated and have them extend/include the files at the new location.

Currently, yes it doesn't use ErrorReportingClient. However, it may start to use the ErrorReportingClient in the future, also conceptually, it's about error reporting.

If it uses the logging client, it should be in the logging component!

I actually disagree. I prefer the conceptual way of the current file location.
Also moving the location will introduce complexity in our build pipeline and I don't like it.

What complexity is added?

You have to change the path of the prepend file based on the version

Also what will you do when we decide to use ErrorReportingClient for reporting? Will you move it back again? Please keep the current location.

Should we attempt to abstract these files so they can easily be used for either error reporting or logging? Maybe they belong somewhere in core?

These files are solely for reporting the errors. They should be in error-reporting library

Ah, so at some point we will no longer use the LoggingClient as it is used in these files today?

@dwsupplee There's no concrete plan yet.
If the usability issue around needing grpc extension is a problem, consider making ext-grpc as just a suggestion.

What is the point of an error reporting library for this if the logging library works?
Currently this is broken. It depends on Logging, but no dependency exists and so it breaks. If anything, this should be in google/cloud-logging, and when we have an implementation for error reporting, we would add that one here.

I find this incredibly confusing. And I've worked with these libraries a lot. What does the error reporting API do? The logging API seems to handle it just fine, so what is the distinction, and why should our users install a separate package when it's handled by the logging library?

My opinion on this.

prepend.php and Bootstrap.php are solely for reporting errors
The composer package google/cloud-error-reporting is the package for reporting errors
The fact that now those files are only using Logging Client lib is just an implementation detail

My natural choice is have them in google/cloud-error-reporting. If it's broken, let's just add dep on google/cloud-logging.

My problem is these packages relate to the specific APIs and the services provided by the APIs. So having an Error Reporting feature in the Error Reporting Services package that doesn't call the Error Reporting API is an issue. We've already seen the fallout for this issue, including:

The composer requirement is missing for the "prepend" file. We can add it, but then we are requiring the logging package for general error reporting functionality, which is also wrong. The correct way to resolve this dependency issue is to move the prepend file into the logging library.
The grpc requirement for the error reporting library is required if the user is just using the prepend file. So they have to install a C extension which is never used because prepend.php is in the wrong package.

I don't completely disagree, but I still prefer having them in error-reporting.
Consider how many people will just use the prepend file and will be happy. Then the problem 1 is negligible. Also can we just make gRPC a suggestion for error-reporting? It will solve the problem 2 above.

Please don't forget the risk of changing those file locations. We need to be super careful because we put prepend.php as auto_prepend_file config. Missing file cause your app to completely stop.

Decision in #675 was we're not doing this.


Multiple Static File Routes

Is there anyway to configure multiple static file routes and also rename /static/ to something else?
I can't seem to find any existing documentation regarding this and would appreciate any feedback.

See the Custom Server and Routing section (2.0 beta):
https://github.com/zeit/next.js#custom-server-and-routing
You can in fact set up express and use its static middleware if you'd like: https://github.com/zeit/next.js/tree/master/examples/custom-server-express

@rauchg @arunoda So to do static, and nested routes like RRv2/3 have, is the idea to use express code like here?
And by static routes, I mean a long config of routes like -
<Route>
  <IndexRoute component="Homepage" />
  <Route path="about" />
  <Route path="posts" >
    <IndexRoute component = "Feed" />
    <Route path = "(:postId)" component="Post" />
  </Route>
  <Route path="members" />
</Route>

In my app, there are over 50 routes and having a long if/else doesn't feel right, so wanted to check?

@okuryu That's one way and you can also simply drop the file directly into the pages directory.
You can learn about our routing system here: https://learnnextjs.com/basics/create-dynamic-pages


Use map().join instead forEach and slice

This is a small change and has no breaks in the execution of the process.
The main motivation is to eliminate the additional step (.slice) and increase performance by generating an array of strings and merging with the separator ';' between them instead of concatenating strings.
This change also reduces the packet size by 43 bytes

Thanks for the idea! However, in modern browsers, string concatenation is faster and more idiomatic than setting up an array for this cause. I don’t think a performance tradeoff is worth the size benefit.

I totally agree with you, string concatenation is much faster, but we have an additional step that leaves everything on the same level, which is .slice.
Here is a reference to two situations https://jsben.ch/GSoK0.
Run the test three times, if any, it is a close call

Thanks for your efforts, I appreciate it! I've just set up my own tests on three platforms:

jsPerf
jsben.ch
Perflink

As you can see, I'm trying to avoid as much bias as possible. While the benchmarks show varying results, I trust jsPerf the most, being an established platform since a long time.
As for string slicing, it can be highly optimized when used as a return value (no new string allocation is required, just offsetting a pointer to a memory address).


ChatterBot in Lambda AWS

Has anyone managed to run Chatterbot on the AWS lambda?
I'm trying but I'm seeing an error.
Can someone help me?
Thanks

I don't have any addition suggestions on how to do this. Since this ticket is a few weeks old I'm going to close it off.


Navigator is lagging after update to RN  0.42.3

I was on 0.33 version and after update i find my transition animation being slow, even with dev off, do you know how to fix it? That problem is seen only if you try to push or pop navigator, with replace it works as usual

Navigator is deprecated. This seems like a question that is best asked on Stack Overflow. I'll go ahead and close it as Navigator is no longer present in core.


Ensure records flushed before final event

This should make #11 a bit easier to implement as the events more closely align with the stream spec.
Notably:

The 'finish' event is emitted after the stream.end() method has been called, and all data has been flushed to the underlying system.

https://nodejs.org/docs/latest/api/stream.html#stream_writable_final_callback
https://nodejs.org/docs/latest/api/stream.html#stream_event_finish

It also forces the functionality of nodejs-8 event handling onto the stream to ensure consistent event handling across all versions supported.

I just have a quick read, it seems fine to me but I didn't test it yet.


Documentation Restructure

Fixes #111
Preview: https://github.com/pavithraes/csp/wiki
Note:

The structure has diverged a fair bit from the initial proposal
The Getting Started tutorials will cover a lot of csp.baselib usage details, hence it's not a huge focus in the concepts section (→ Already tracking in a separate issue)
The "How-to" guides only have the migrated content from old docs right now, we'll be updating all the pages to follow a "how-to" format (→ Opened a new issue)
The docs authoring workflow will change a little with the new GitHub sidebar, we'll add relevant docs to make this easier

This PR has an initial structure. It'll need some updates, but those will be easier to do after merging.

Sounds good, you can add me

@robambalu, yes, using the preview link at https://github.com/pavithraes/csp/wiki would be the best way to see the current new structure.

@robambalu Yes, I'm keeping https://github.com/pavithraes/csp/wiki up-to-date with this PR at all times. Some pages (like the home page) haven't had any updates for a week, which is why you see that message. But, for example, the Write Output Adapters page shows the recent edits from 2 days ago. :)

Please update the logo files with these versions which were slightly updated by our media dept

@pavithraes can we remove this section all together if you havent already: https://github.com/Point72/csp/wiki/9.-Caching
We dont plan to maintain that ( in its current form )

@robambalu - I've made all the requested updates, this is ready for a final look :)


[debuginfo][windows, PDB] windows debug info drops line location of inlined trap from array's subscript

Description
An array subscript getter out-of-bounds trap has an invalid line location in the LLVM debug information, leading to a wrong line location in the crash. This is for PDB for windows.
Reproduction
import FoundationXML
import Foundation

public struct AppInstaller: Equatable {

    public init(with root: XMLElement) throws {
        let element = root.elements(forName: "MainPackage")[0]
    }

}

build with
> swiftc -c test.swift -S -emit-ir  -g -debug-info-format=codeview -o test.ir -O

you can see that the llvm.trap instruction has a debug location with line entry 0, which isn't preserved in PDB.
Expected behavior
The original location should be preserved without a zero line.
Environment
swift --version
Swift version 6.0-dev (LLVM 73a346c9caf32cc, Swift e2ad12ba5c3bc2a)
Target: x86_64-unknown-windows-msvc
Additional information
No response

Can you post the -g -emit-sil and the -emit-ir ouptut for the function?

Can I even build this on a non-windows machine?


fix _Box2D AttributeError

add !pip install box2d-py
to overcome:
AttributeError: module '_Box2D' has no attribute 'RAND_LIMIT_swigconstant'
Section:
Step 3: Understand what is Gym and how it works? 🤖

Thanks for the update, since we want to keep consistency we merge the PR that update requirements-txt instead. But they found the same solution 🤗


Remove spaces around em dashes

See https://styleguides.azurewebsites.net/Styleguide/Read?id=2700&topicid=28766.

Internal previews
Toggle expand/collapse

📄 File
🔗 Preview link

docs/core/extensions/caching.md
Caching in .NET

docs/core/extensions/custom-logging-provider.md
Implement a custom logging provider in .NET

docs/core/extensions/localization.md
Localization in .NET

docs/core/extensions/windows-service.md
Create Windows Service using BackgroundService

docs/core/porting/versioning-sdk-msbuild-vs.md
.NET SDK, MSBuild, and Visual Studio versioning

docs/core/rid-catalog.md
docs/core/rid-catalog

docs/core/tools/sdk-errors/netsdk1206.md
NETSDK1206: Found version-specific or distribution-specific runtime identifier(s)

docs/devops/dotnet-secure-github-action.md
Create a security scan GitHub workflow

docs/devops/github-actions-overview.md
GitHub Actions and .NET

docs/orleans/deployment/multi-cluster-support/silo-configuration.md
docs/orleans/deployment/multi-cluster-support/silo-configuration

docs/orleans/grains/event-sourcing/immediate-vs-delayed-confirmation.md
Immediate and delayed confirmations

docs/orleans/grains/external-tasks-and-grains.md
External tasks and grains

docs/orleans/implementation/cluster-management.md
Cluster management in Orleans

docs/orleans/resources/orleans-architecture-principles-and-approach.md
docs/orleans/resources/orleans-architecture-principles-and-approach

docs/orleans/resources/orleans-thinking-big-and-small.md
Big and small thinking

docs/orleans/resources/student-projects.md
Student projects

docs/orleans/streaming/stream-providers.md
Orleans stream providers

docs/standard/events/observer-design-pattern-best-practices.md
Observer Design Pattern Best Practices

Thanks @tdykstra