Instructions for running the script

Hello,
I am trying to run the script on my own data. Since the script was written with python2 I made a conda environment, cloned this repository and placed the allPeptides.txt input file in the working directory.
When I run "python run.py -d", it makes the output folder and says
detecting substitutions. That step might take some time...
but the command just ends a few seconds later and nothing is produced without any errors.
I tried running python detect.py, but got:
Traceback (most recent call last):
File "/nfs/users2/enovoa/imilenkovic/substitutions_MS/substitutions/detect.py", line 377, in
for record in SeqIO.parse(open(path_to_fasta,'rU'),'fasta'):
IOError: [Errno 2] No such file or directory: '/Users/ernestmordret/Library/Mobile Documents/com~apple~CloudDocs/Documents/MS_files/sequences/Escherichia_coli_str_k_12_substr_mg1655.ASM584v2.cdna.all.fa'
so I guess this is not what should be done either.
Is there something I am missing? Thanks in advance.

Looks like you should modify some paths… they’re still pointing towards my computer at the moment!

Le 8 avr. 2021 à 12:47, imilenkovic @.***> a écrit :
Hello,
I am trying to run the script on my own data. Since the script was written with python2 I made a conda environment, cloned this repository and placed the allPeptides.txt input file in the working directory.
When I run "python run.py -d", it makes the output folder and says
detecting substitutions. That step might take some time...
but the command just ends a few seconds later and nothing is produced without any errors.
I tried running python detect.py, but got:
Traceback (most recent call last):
File "/nfs/users2/enovoa/imilenkovic/substitutions_MS/substitutions/detect.py", line 377, in
for record in SeqIO.parse(open(path_to_fasta,'rU'),'fasta'):
IOError: [Errno 2] No such file or directory: '/Users/ernestmordret/Library/Mobile Documents/comappleCloudDocs/Documents/MS_files/sequences/Escherichia_coli_str_k_12_substr_mg1655.ASM584v2.cdna.all.fa'
so I guess this is not what should be done either.
Is there something I am missing? Thanks in advance.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/ernestmordret/substitutions/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACUL3WMWWA7NOE6DQ7WE7ELTHWCVRANCNFSM42ST7Z6A.

I see that :D but I couldn't find any paths in the scripts; eg. in detect.py it goes:
for record in SeqIO.parse(open(path_to_fasta,'rU'),'fasta'):     record.seq = record.seq.upper()
but it's not specifying your paths so I didn't know where that came from.
Am I running the script correctly by trying "python run.py -d"? And is everything I need in the working directory the allPeptides.txt file or do I also need this cdna fasta that detect.py is saying is missing?
Thanks a lot!

I know, it’s a terrible script. It was not meant to be used as a package, and it’s not maintained anymore, as I’m out of academia. So handle it with caution!

Le 8 avr. 2021 à 12:52, imilenkovic @.***> a écrit :
I see that :D but I couldn't find any paths in the scripts; eg. in detect.py it goes:
for record in SeqIO.parse(open(path_to_fasta,'rU'),'fasta'): record.seq = record.seq.upper()
but it's not specifying your paths so I didn't know where that came from.
Am I running the script correctly by trying "python run.py -d"? And is everything I need in the working directory the allPeptides.txt file or do I also need this cdna fasta that detect.py is saying is missing?
Thanks a lot!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/ernestmordret/substitutions/issues/1#issuecomment-815662632, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACUL3WIYW2AAGHZUGLO724TTHWDINANCNFSM42ST7Z6A.

Hello again,
Thanks for letting me know. Is there anyone else I can contact regarding this algorithm? I managed to make it work, but the detect.py script only produced a very small subs.csv file (19 lines).
Thanks in advance.


Several broken links in the tutorial

Here is one https://docs.nativescript.org/ui/layouts in Lesson #2, step 4/20. A link in below text in it is broken.
Learning NativeScript layouts can be tricky, especially if you come from a web development background. Reading the documentation is a good place to start.
Here is another in the same page: https://docs.nativescript.org/angular/ui/layout-containers

I am coming across many broken links and out of date information in many of the tutorials and docs, which is becoming increasingly frustrating. Most recent example, looking for the docs for the VSCode NativeScript extension for debugging since the instructional "Details" are out of date on the extension itself (the VSCode debug is now called "Run" and the instructions for setup are no longer applicable) but the "View the Docs" link (https://docs.nativescript.org/core-concepts/visual-studio-code-extension) gives a 404 error. This is probably the 8th broken link I've encountered in an hour of trying to get started with a new project.

I am coming across many broken links and out of date information in many of the tutorials and docs, which is becoming increasingly frustrating. Most recent example, looking for the docs for the VSCode NativeScript extension for debugging since the instructional "Details" are out of date on the extension itself (the VSCode debug is now called "Run" and the instructions for setup are no longer applicable) but the "View the Docs" link (https://docs.nativescript.org/core-concepts/visual-studio-code-extension) gives a 404 error. This is probably the 8th broken link I've encountered in an hour of trying to get started with a new project.

I can confirm using NS+ JavaScript.

I can confirm using NS+ JavaScript.

This would be some changes:
https://docs.nativescript.org/ui/layouts -> https://docs.nativescript.org/ui/layouts/layouts
https://docs.nativescript.org/core-concepts/visual-studio-code-extension -> https://docs.nativescript.org/tooling/visual-studio-code-extension
https://docs.nativescript.org/ui/ui-views -> https://docs.nativescript.org/ui/overview
https://docs.nativescript.org/angular/code-samples/ui/text-field -> https://docs.nativescript.org/ui/components/text-field
https://docs.nativescript.org/angular/code-samples/ui/button -> https://docs.nativescript.org/ui/components/button
....
Inside the docs there are also broken links, so it seems it is an issue in the docs and not in the playground.

This would be some changes:
https://docs.nativescript.org/ui/layouts -> https://docs.nativescript.org/ui/layouts/layouts
https://docs.nativescript.org/core-concepts/visual-studio-code-extension -> https://docs.nativescript.org/tooling/visual-studio-code-extension
https://docs.nativescript.org/ui/ui-views -> https://docs.nativescript.org/ui/overview
https://docs.nativescript.org/angular/code-samples/ui/text-field -> https://docs.nativescript.org/ui/components/text-field
https://docs.nativescript.org/angular/code-samples/ui/button -> https://docs.nativescript.org/ui/components/button
....
Inside the docs there are also broken links, so it seems it is an issue in the docs and not in the playground.


[Docker] Add script to build llvm from source

This allows us to use the latest llvm and make sure it builds with the same configuration as the rest of tvm
Change-Id: I004ec89700498167c632d25f4fdf667922ba4943

@tvm-bot rerun

@neildhickey what is the benefit of building from source if we are using the released version anyway?

@mehrdadh Newer versions of gcc and clang introduce an option to outline atomic calls which means it will look for these atomic functions calls in glibc. The atomic calls are of the form __aarch64_ldadd4_acq_rel and others.
With the version of gcc and glibc we use to build tvm, these functions aren't available, and the build fails when trying to build against prebuilt libraries which use these options.
The released llvm packages for llvm-15 are built with these options enabled, so a workaround is to build llvm from source using the same version of the compiler we use to build tvm, those alleviating the of the undefined function references.


Color generation example fails

Should this example from this ipynb work for me?
import cufflinks as cf
gen=cf.colors.colorgen()
outputColors=[gen.next() for _ in range(len(df))]
cf.colors.color_table(outputColors)

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-106-8cab56c26750> in <module>()
      1 import cufflinks as cf
      2 gen=cf.colors.colorgen()
----> 3 outputColors=[gen.next() for _ in range(len(df))]
      4 cf.colors.color_table(outputColors)

<ipython-input-106-8cab56c26750> in <listcomp>(.0)
      1 import cufflinks as cf
      2 gen=cf.colors.colorgen()
----> 3 outputColors=[gen.next() for _ in range(len(df))]
      4 cf.colors.color_table(outputColors)

AttributeError: 'generator' object has no attribute 'next'

Hello Hendy
Excuse for my poor English, I'm not totally understand your question.
But what is your variable "df" in your code, I think it's empty so
"outputColors=[gen.next() for _ in range(len(df))]" has error.
Have a nice day
ST, H
2017-12-24 12:10 GMT+08:00 John Hendy<EMAIL_ADDRESS>
Should this example from this ipynb
https://github.com/santosjorge/cufflinks/blob/master/Cufflinks Tutorial - Colors.ipynb
work for me?
import cufflinks as cf
gen=cf.colors.colorgen()
outputColors=[gen.next() for _ in range(len(df))]
cf.colors.color_table(outputColors)

AttributeError                            Traceback (most recent call last)
 in ()
1 import cufflinks as cf
2 gen=cf.colors.colorgen()
----> 3 outputColors=[gen.next() for _ in range(len(df))]
4 cf.colors.color_table(outputColors)
 in (.0)
1 import cufflinks as cf
2 gen=cf.colors.colorgen()
----> 3 outputColors=[gen.next() for _ in range(len(df))]
4 cf.colors.color_table(outputColors)
AttributeError: 'generator' object has no attribute 'next'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/santosjorge/cufflinks/issues/80, or mute the thread
https://github.com/notifications/unsubscribe-auth/AcSlSaWNsjEj0KUVyxsYEYaqjJqseBy1ks5tDc6ugaJpZM4RL1EI
.

Sorry about making it dependent on something else... please try this:
import cufflinks as cf
gen=cf.colors.colorgen()
outputColors=[gen.next() for _ in range(5)]

Hmm. Actually, silly me. Looks to be a python2 vs. python3 issue. That said, might be best to see if your code could be made version agnostic.
See this SO question. The python3 equivalent is:
outputColors=[next(gen) for _ in range(5)]

Hello Hendy
It can work and my environment is Python3 with Jupyter notebook.
[image: 內置圖片 1]
Have a nice day
ST, H
2017-12-26 9:04 GMT+08:00 John Hendy<EMAIL_ADDRESS>
Closed #80 https://github.com/santosjorge/cufflinks/issues/80.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/santosjorge/cufflinks/issues/80#event-1401199012, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AcSlScCk_HANF8lhLdO14SPHmwS10XvKks5tEEYxgaJpZM4RL1EI
.

This works for you on python3?
import cufflinks as cf
gen=cf.colors.colorgen()
outputColors=[gen.next() for _ in range(5)]

More details:
$ python --version
Python 3.6.3

# after running the above:
>>> type(gen)
<class 'generator'>

>>> dir(gen)
['__class__', '__del__', '__delattr__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__gt__', '__hash__', '__init__', '__init_subclass__', '__iter__', '__le__', '__lt__', '__name__', '__ne__', '__new__', '__next__', '__qualname__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', 'close', 'gi_code', 'gi_frame', 'gi_running', 'gi_yieldfrom', 'send', 'throw']

Hello Hendy
Sorry and forgive my fool mistake
[image: 內置圖片 1]
Have a nice day
ST, H
2017-12-26 10:09 GMT+08:00 John Hendy<EMAIL_ADDRESS>
This works for you on python3?
import cufflinks as cf
gen=cf.colors.colorgen()
outputColors=[gen.next() for _ in range(5)]
More details:
$ python --version
Python 3.6.3
after running the above:

type(gen)
<class 'generator'>

dir(gen)
['class', 'del', 'delattr', 'dir', 'doc', 'eq', 'format', 'ge', 'getattribute', 'gt', 'hash', 'init', 'init_subclass', 'iter', 'le', 'lt', 'name', 'ne', 'new', 'next', 'qualname', 'reduce', 'reduce_ex', 'repr', 'setattr', 'sizeof', 'str', 'subclasshook', 'close', 'gi_code', 'gi_frame', 'gi_running', 'gi_yieldfrom', 'send', 'throw']

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/santosjorge/cufflinks/issues/80#issuecomment-353904422,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcSlScZBNOnEdEM5rebYZBbL18yPLULkks5tEFVggaJpZM4RL1EI
.


Need help with Depth orders  using websockets

Dear All, I would appreciate if anybody can help me with how to get the depth order book for all symbols instead of calling DepthCachemanager for each symbol separately. I want to pull all the depth order book for all symbols at once. I have tried multiplex socket, but it is not working as I expected. Thank you in advance...!!

Im currently working on the same problem this is my try:
import time
import settings
from binance.client import Client
from binance.depthcache import DepthCacheManager
client = Client(settings.pubkey, settings.privkey)

symbols=['BTCUSDT', 'ETHUSDT', 'NEOUSDT', 'LTCUSDT', 'ETHBTC', 'LTCBTC', 'NEOBTC', 'LTCETH', 'NEOETH']

def process_depth(depth_cache):
    if depth_cache is not None:
        print("symbol {}".format(depth_cache.symbol) + " - BIDS: " + ''.join(str(e) for e in depth_cache.get_bids()[:1]) + " - ASKS: " + ''.join(str(e) for e in depth_cache.get_asks()[:1]))
    else:
        print("error")

for symbol in symbols:
    dcm = DepthCacheManager(client, symbol, callback=process_depth, refresh_interval=10)

depth_cache = dcm.get_depth_cache()

Hope it helps you... i still have the problem that it does not output it every 10 seconds....
Currently i dont know how i can solve that....


Any request over 10.5k returns a null body to the lambda

We have observed that any time a request is sent through Kong to our lambda with a body size larger than 10753 bytes, the request body field given to our lambda comes up as null, regardless of whether or not skip_large_bodies was specified as true.
I am not sure why the number is 10.5k, nor why it is so reproducible, but it's close to the default nginx_http_client_body_buffer_size of 8k, so I figure they're related. Further, since the skip_large_bodies flag makes no difference in whether or not we actually receive the body back when we process the data in our lambda, it leads me to believe that this line of code in the AWS lambda plugin returns null every time when a request gets to be too big. This makes sense because if it returns null, skip_large_bodies is completely ignored and results in nothing being different. It also results in a null body.
Again, the 10.5k thing is baffling, but I see no way of fixing this by changing any particular kong setting (other than perhaps nginx_http_client_body_buffer_size, but I am concerned about performance and hope I don't end up having to change it  much).
Please help?
To give more background or to be perfectly clear: our set-up is a hybrid-mode enterprise deployment with the control plane nodes deployed to their own ECS cluster and data plane nodes also being run in a containerized environment elsewhere. There is an AWS lambda that is processing requests coming in for a particular route. If the request size is too big, the request body given in the json object to the lambda is null, every time, regardless of skip_large_bodies.

Wanted to add some more information. By increasing the size of nginx_http_client_body_buffer_size, my dev was able to get a body size of ~1MB through, so the setting does have bearing on what's happening. Further, he still confirms that the skip_large_bodies setting seems to have no effect, confirming my suspicions that the plugin is not able to retrieve larger streamed bodies from disk.

More information. All of this comment is in regard to the bug found on line 9 in this file: https://github.com/Kong/kong-plugin-aws-lambda/blob/master/kong/plugins/aws-lambda/request-util.lua#L9
The problem, as I understand it, is that before calling ngx.req.get_body_file() in that file, the function ngx.req.read_body() should be called first, but it isn't. Source: https://openresty-reference.readthedocs.io/en/latest/Lua_Nginx_API/?q=get_body_file&check_keywords=yes&area=default#ngxreqget_body_file
In order to get around this bug in the plugin, we were able to set the not-recommended setting of lua_need_request_body by setting KONG_NGINX_HTTP_LUA_NEED_REQUEST_BODY on the dataplane deployment. This got us to a better place of being able to observe the error message in the logs printed on line 12 of that file.
However, we believe that #44 is not yet fixed, and we have commented on that ticket showing that the line that originally caused the breakage in #44 hasn't been fixed yet. We were also able to prove experimentally that:

Kong WAS picking up our lambda config, since we specified the non-default value of true for forward_request_body and this was honored
However, Kong lambda plugin was NOT honoring the skip_large_bodies configuration item.

I think, in order to fix this issue, the following needs to be done:

A call to ngx.req.read_body() needs to be added before the ngx.req.get_body_file() call
skip_large_bodies needs to be honored by fixing the logic in aws-serializer.lua (here: https://github.com/Kong/kong-plugin-aws-lambda/blob/master/kong/plugins/aws-lambda/aws-serializer.lua#L57) so that skip_large_bodies is honored.

If that aws-serialize.lua line is not the bug, then i'm telling you, the bug is somewhere. That configuration item is simply not being honored, no matter what we do, even though other configuration items like forward_request_body are being honored.
Please fix, thank you.

We desperately need this fixed please. Thank you.

I created a pull request (#48). I have tested and verified that that pull request fixes our issue. I hope that it is accepted; please message me if you have any problems with it.

fixed by #48


Receive waypoints from MissionPlanner and Control it using Mavros offboard

I wish to have a pixhawk connected to 2 things

a companion computer running mavros through Uart
and MissionPlanner using Telemetry

Has anyone had experience doing this?

Closing because of no activity. Feel free to comment and re-open, if there are things left to discuss.


Migration from adv api v2 to v3 auth. issue

Hi Amazon team,
I'm having troubles migrating our advertising api layer from v2 to v3. Basically, using the same credentials (clientId, refreshTokens and profileId), the new endpoint responses back with 401 auth error. I followed the documentation but I can't find any issues, shall I set something on the account before using the new versione?
Here's the working V2 snippet:
headers={     "Amazon-Advertising-API-ClientId": clientId,     "Amazon-Advertising-API-Scope": profileId,     "Authorization": accessToken,     "Content-Type": "application/json" } data={     "stateFilter": "enabled",     #"metrics": metrics,     "metrics": ",".join([ "impressions","clicks","cost","campaignId","adGroupId" ]),     "reportDate": "20221001" } response = re.post("https://advertising-api-eu.amazon.com/v2/sp/productAds/report", headers=headers, json=data) r = response.json()
And the not working V3 snippet:
`
headers = {
'Amazon-Advertising-API-ClientId': clientId,
'Amazon-Advertising-API-Scope': profileId,
'Authorization': accessToken,
'Content-Type': 'application/vnd.createasyncreportrequest.v3+json'
}
data = {
"name":"SP campaigns report 10/1-10/10",
"startDate":"2022-10-01",
"endDate":"2022-10-10",
"configuration":{
"adProduct":"SPONSORED_PRODUCTS",
"groupBy":["campaign","adGroup"],
"columns":["impressions","clicks","cost","campaignId","adGroupId","date"],
"reportTypeId":"spCampaigns",
"timeUnit":"DAILY",
"format":"GZIP_JSON"
}
}
response = requests.post('https://advertising-api.amazon.com/reporting/reports', headers=headers, data=data)
r = response.json()
`

Hi @FedericoSala , your issue may relate to the regional subdomain used in each request:

https://advertising-api-eu.amazon.com (for the working v2)
https://advertising-api.amazon.com (for the unauthorized v3)

A profile ID represents an advertiser in a single marketplace. A profile for a marketplace outside the region covered by a given host does not provide authorization for operations on the host. If the advertiser account is in EU, that profile will not be authorized on the North American host.
See Profiles in the advanced tools center for more information, and let us know if this helps!

Hi @jerirose ,
what I understood from your documentation is there's just a single unified endpoint https://advertising-api.amazon.com, I haven't find anything about regions so far.
I literally used Amazon's docs test request with our working credentials:
curl --location --request POST 'https://advertising-api.amazon.com/reporting/reports' \ --header 'Content-Type: application/vnd.createasyncreportrequest.v3+json' \ --header 'Amazon-Advertising-API-ClientId: amzn1.application-oa2-client.xxxxxxxx' \ --header 'Amazon-Advertising-API-Scope: xxxxxxxx' \ --header 'Authorization: Bearer Atza|xxxxxxxxx' \ --data-raw '{         "name":"SP targeting report 7/5-7/10",         "startDate":"2022-07-05",         "endDate":"2022-07-10",         "configuration":{             "adProduct":"SPONSORED_PRODUCTS",             "groupBy":["targeting"],             "columns":["adGroupId","campaignId", "targeting","keywordId","matchType","impressions", "clicks", "cost", "purchases1d", "purchases7d", "purchases14d", "purchases30d","startDate","endDate"],             "filters": [                 {                     "field": "keywordType",                     "values": [                     "TARGETING_EXPRESSION",                     "TARGETING_EXPRESSION_PREDEFINED"                     ]                 }             ],             "reportTypeId":"spTargeting",             "timeUnit":"SUMMARY",             "format":"GZIP_JSON"         }     }'

Yes, @FedericoSala , since your working v2 request is directed to https://advertising-api-eu.amazon.com, your v3 request using the same credentials will also need to use that same root URL.
In the example in your initial post, you could try changing this line:
response = requests.post('https://advertising-api.amazon.com/reporting/reports', headers=headers, data=data)

To this, adding -eu in the URL:
response = requests.post('https://advertising-api-eu.amazon.com/reporting/reports', headers=headers, data=data)

I'll also pass this on to the author of the "Getting started" document to consider adding a note on regions to accompany that sample request.

I've updated the V3 reporting tutorial to include a note about regional URLs. Closing the issue for now.


Update control-gallery.md

Updated text around perferformance

Updated some text, Milos said the previous wasn't formal enough.


Remove TypeEntity and associated endpoints

Related PRs:
https://github.com/DFE-Digital/get-into-teaching-app/pull/675
https://github.com/DFE-Digital/get-teacher-training-adviser-service/pull/461
The TypeEntity has been replaced with two new entities; PickListItem and LookupItem.
Remove all references to TypeEntity and associated endpoints.
The validation against PickListItem/LookupItem could be DRYed up, but I'll address this in a follow up PR (there's already a ticket raised for it).

@jebw it's mergeable now, the apps have both been updated in prod. I've removed the warning from the PR description.


[Improve][Manager] Add check param for manager-client

Description
add check param for manager-client
InLong Component
InLong Manager
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Fixed by https://github.com/apache/incubator-inlong/pull/3177


Switching From Native To Lemon

Tried to switch Native Events with LemonUi and got errors. So have resorted to default for now. Any assistance switching please.

LemonUI is currently only available for Mono projects (C#, VB.net and F#), not for Lua.
There is a Lua version in the works, you can check the progress LemonUIbyLemon/LemonUI_Lua. There is nothing yet implemented but you might want to follow the repo to learn when it's finally release :)


Unable to pass auth headers for WebSockets in vscode.web

Create a custom jupyter server behind a custom authentication
The URL auth works by passing the auth headers, however the WebSockets do not authenticate appropriately.
Solution: Need the ability to pass protocols in the WebSocket ctor.

Hi @DonJayamanne, what are some steps to verify this issue?

Marking as verified, as a separate (internal) extension has been able to verify this works as expected.


Fix too eager GDScriptFunctionState stack cleanup

The philosophy of my recent improvements to yield() involved cleaning up the stack stored in a GDScriptFunctionState as early as possible.
It seems than one case was too eager: when a function that yielded did complete. Cleaning the stack of the stored state at that very point wasn’t right because it could make the GDScriptFunctionState be freed too soon; namely, when the disconnection logic for one-shot signals still needed to be run on that object.
GDScriptFunctionState's destructor will do the cleanup anyway when it's ready to do so.
I've tested that this change doesn't revert the intent of the original change, so it should be fine.

This code is generously donated by IMVU.

Thanks!

Cherry-picked for 3.2.2.


Add default date to post_date in create form

Add default date to post_date in create form to avoid "Attribute post_date is required" exception when submitting a new page.

Thank you for your PR! :confetti_ball:
I'd use the "now()" helper method, rather than using "Carbon\Carbon::now()". If you can make that change, I'll merge this PR :+1:


Remove MunifTanjim/exrc.nvim

Repo URL:
https://github.com/MunifTanjim/exrc.nvim
Repo is archived since 5th January 23
Checklist:

[x] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
[x] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] The title of the pull request is Add/Update/Remove `username/repo`  (notice the backticks around `username/repo`) when adding a new plugin.
[x] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else.
[x] The description doesn't contain emojis.
[x] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
[x] Acronyms should be fully capitalized, for example LSP, TS, YAML, etc.

Thanks for the PR!


harvester load balancer, IPAM, defaults to DCHP and overrides user's selection

Setup

Rancher version: v2.6.4-rc9
Browser type & version: any

Describe the bug

There is a default value for IPAM, DCHP, which is overriding the value the user selects.
To Reproduce

using harvester node driver, deploy a cluster with cloud provider enabled
deploy a workload with an LB

note that the default is set to DCHP
select Pool as the IPAM

view the workload after creation

Result
LB deployed using DCHP instead of Pool
Expected Result
User selected option should be what is used for the deployment
Additional context
also tested the following:

removing the ipam option when editing as yaml

still results in DCHP deployment

does not occur when cloning an existing workload (default for IPAM is blank, and selecting either pool or dchp works as expected)

after more debugging, I've found the following:

on a fresh create, no matter what the user selects, the resulting yaml/deployment sets spec.containers.ports._ipam = dchp -> default value overrides everything is the bug here. Even if you edit as yaml, that gets overridden with the default value of dhcp

is there a different values.yaml for clone vs. fresh deployment?

on a clone, there is no default value. Here it is revealed that, the UI is not setting the value at all for the deployment. So maybe that IPAM element isn’t connected to the backend variables? But again, no matter what the user sets, the UI value is set to null once the deployment is created. And in the backend, if there isn’t something set in values.yaml it is being set automatically to DHCP.  However, though the manually set yaml value is not read into the UI view, for cloned workloads I see that the yaml value is respected when creating the service (this is not the case when doing a fresh deployment)

@jtravee this may have to a release note for 2.6.4 for Harvester

@jtravee this may have to a release note for 2.6.4 for Harvester

@gaktive, would you or @slickwarren be able to give a short note/summary from that that you'd like captured for the RN?

_ipam is used for creating a service with an ipam annotation.
There is a workaround for the first bullet: After changing ipam, input listening port or container port.

@n313893254 Is the PR https://github.com/rancher/dashboard/pull/5444 targeted for 2.6.4, if so does it affect the release notes?

@richard-cox  Yes, PR target for 2.6.4.
I think it would affect the release notes because I fix the user selection issue. But for the second bullet on a clone, I am not sure about that.

@n313893254 Thanks! The PRs merged now, I'll leave the release note part to your side to determine

_ipam is used for creating a service with an ipam annotation.
There is a workaround for the first bullet: After changing ipam, input listening port or container port.

I'll add this to the release note, thanks!

tested on v2.6-head (85d6925) and no longer see this problem, however I did file a separate issue related to IPAM https://github.com/harvester/harvester/issues/2077


Project config migrate "Calling unknown method: craft\console\Request::getToken()"

Description
Installing the plugin locally, then using project config to sync to live production fails:
./craft project-config/sync Installing plugin "nocache" ... error: Calling unknown method: craft\console\Request::getToken() Aborting config sync

Just need to change line 88 of Service.php to:
return $generalConfig->enableTemplateCaching && !$request->getIsLivePreview() && !$request->getIsConsoleRequest() && !$request->getToken();

Thanks @Coysh!


Multiple changes to Recording/Media operations

Changes done:

Updated swagger
Adding PlayOptions to the play operations.
Adding Unit Testing (in progress)

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Communication.CallingServer


Research on external data sources

Quote from project description:
The following are examples of public data sources only and should not constrain the thinking and creativity of the team:

Google-maps API
Google Search API
Domain registration service
facebook/instagram
ChatGPT
…

These could yield data like:

Customer Reviews and extracted information (sentiment, type of business, do they have staff, tables to be served, …)
Name, Address, type of the business (competition in the area, demographic, …)
Do they already have a web-presence or a web-shop
…

The data providers should target the European market (i.e. GB, Spain, Germany, Italy, France).

@luccalb This looks good! We could add another metric where if the company is worth contacting, but won't generate enough revenue to warrant a call from a salesperson (90% of companies according to Marc if I recall), we can keep track of that so they could use this information to instead redirect them to an automated/self-directed signup process.

I don't know how much of that job would be part of the AI team, but we could combine your ideas.
Create a model, maybe first decision trees or clustering because we get so much categorical data at the beginning (and no revenue). After we get revenue data of the leads we can "upgrade" by using regression (linear / logistic).  And based on the results of the models we suggest process decisions.

Recently I have heart about new "chatGPT Browse with Bing" from openAI, which now can make searches on Internet to provide answers unlike chatGPT 3.5. One can basically ask GPT a question about an individual and GPT searches other sources like linkedIn and provides an answer. Please follow the link for more info.


Outdated docs and tutorials about importing Client/DBClient

Some docs and tutorials use the following code to import the client,
from mspasspy.db.client import Client as DBClient

from mspasspy.db.client import Client

but now it fails due to the recent renaming in 80fff8868e8f26614eaf1a10da3f9a6429e7f9cb.
Need to update the docs and tutorials to use
from mspasspy.db.client import DBClient

Thanks for catching it. We will revise all the documents when the API is finalized.


Add missing Github labels

area/transit/egress
area/transit/ipv6
Signed-off-by: Antonin Bas<EMAIL_ADDRESS>

Codecov Report

Merging #2847 (732d61c) into main (e880406) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2847      +/-   ##
==========================================
+ Coverage   40.90%   40.91%   +0.01%
==========================================
  Files         158      158
  Lines       19539    19539
==========================================
+ Hits         7992     7995       +3
+ Misses      10798    10791       -7
- Partials      749      753       +4

Flag
Coverage Δ

unit-tests
40.91% <ø> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/agent/openflow/pipeline.go
22.10% <0.00%> (-0.08%)
:arrow_down:

pkg/controller/traceflow/controller.go
67.27% <0.00%> (ø)

...gent/controller/noderoute/node_route_controller.go
45.22% <0.00%> (+1.12%)
:arrow_up:


feat(torrent): getTrackers()

This PR introduces a new BitTorrent-specific function for getting direct access to the WebSocket tracker connections. I needed to access these WebSockets in order to evaluate their readyStates to potentially present a troubleshooting UI if no successful connection is made.
This PR also implements retry logic if the WebSocket tracker connection is closed.
This may be a naive implementation, but it seemed like the simplest way to meet the need. Let me know what you think!

Here's a demonstration of this change in use: https://github.com/jeremyckahn/chitchatter/pull/128/files#diff-c24677bbb96aaa14277b339703c0f0e774c9275d800f180bc059ebb894011832

This makes sense and is a nice implementation. The only thing I think we might consider changing before merging is the retry logic. Have you found that retries are successful sometimes with trackers that are down or not cooperating? I have noticed that public trackers that are up sometimes disconnect (maybe due to info hashes they haven't seen? still investigating) but I haven't seen them start working after a page refresh/reconnect.
In any case, I think we should have a simple max retry counter for each tracker (maybe 3 or so attempts?) so an app isn't constantly trying to connect to a tracker in the background every few seconds. This way we don't pollute the error console and flood trackers with connection attempts.

Have you found that retries are successful sometimes with trackers that are down or not cooperating?

I've observed successful reconnections in contrived development scenarios (by stopping and restarting a local tracker manually), but not in practice because I don't know how to recreate such a situation in a "natural" way. Given that it works locally and doesn't seem to introduce any problems, I'm inclined to move ahead with it. I think it's worth keeping an eye on and potentially reassessing in the future.

In any case, I think we should have a simple max retry counter for each tracker (maybe 3 or so attempts?) so an app isn't constantly trying to connect to a tracker in the background every few seconds.

I think that's a great idea and can update this PR to include it. I'd just propose one tweak: Instead of a limited amount of reties, what do you think about an exponential backoff strategy or something similar? That way there's at least the potential of eventually reconnecting to unavailable trackers automatically.

I had some time this morning, so I just pushed an exponential backoff implementation in https://github.com/jeremyckahn/trystero/commit/8a07485e2f0ee0c499789f89c522d4ff4ed8dd67. If you'd prefer to switch to a limited number of retries, I can make that change. Let me know what you think @dmotz!

Thanks @jeremyckahn! Now available on npm in 0.13.0.

Awesome! Thanks for merging and releasing, @dmotz.


use CASE WHEN IN MOOR

How to effeciently implement multiple case when in moor to mimic this sql
SELECT trackid,name
CASE
             WHEN milliseconds<60000    THEN
                 'short'
              When milliseconds>60000 And milliseconds<300000 THEN 'medium'
              ELSE   'long'
              END category
FROM tracks;

Thanks in advance

We don't (yet) support CASE from the Dart query builder. Of course, you can use CASE expressions in custom queries or moor files.
In your case, you're only using the CASE expression in a result column, so you might as well implement this in Dart:
final result = select(tracks).map((track) {
  String category;
  if (track < 60000) {
    category = 'short';
  } else if (track < 300000) {
    category = 'medium';
  } else {
    category = 'long';
  }

  // ...
}).getAll();

Must have missed this issue - caseMatch has been available for some time.


feat: Make initial user configurable in helm chart

SUMMARY
This PR updates the helm chart to allow easy configuration of the initial user via helm properties. At the moment, to not use the default admin/admin user, you have to download and modify the chart or to set a the complete init script. With these changes, username/password and the other user details can be set via normal helm properties.
The default behavior does not change.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[x] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #12862 (c66288d) into master (9a7fba8) will decrease coverage by 3.64%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12862      +/-   ##
==========================================
- Coverage   67.04%   63.40%   -3.65%
==========================================
  Files        1022      489     -533
  Lines       50186    30193   -19993
  Branches     5204        0    -5204
==========================================
- Hits        33647    19143   -14504
+ Misses      16404    11050    -5354
+ Partials      135        0     -135

Flag
Coverage Δ

cypress
?

javascript
?

python
63.40% <ø> (-0.69%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/hive.py
73.84% <0.00%> (-17.31%)
:arrow_down:

superset/databases/commands/create.py
83.67% <0.00%> (-8.17%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/connectors/sqla/models.py
84.31% <0.00%> (-6.28%)
:arrow_down:

superset/db_engine_specs/sqlite.py
90.62% <0.00%> (-6.25%)
:arrow_down:

superset/databases/commands/test_connection.py
84.78% <0.00%> (-4.35%)
:arrow_down:

superset/utils/celery.py
86.20% <0.00%> (-3.45%)
:arrow_down:

superset/models/core.py
85.59% <0.00%> (-3.27%)
:arrow_down:

... and 543 more

Continue to review full report at Codecov.

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


Fully support displaying all supporter PodVolume types

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>Noticed that this was missing while working on https://github.com/lensapp/lens/pull/4121. So I thought I would implement it, based the types on the GO types from kubectl's repo.

Just found errors while opening pod details:


List of Apis to implement

A list of APIs to be implemented in the library, so we can call from them.
From this post: http://guides.lib.berkeley.edu/information-studies/apis

[x] arXiv
[x] BioMed Central API
[ ] Chronicling America API
[ ] Elsevier Scopus APIs
[ ] Europe PubMed Central
[ ] HathiTrust Extracted Features Dataset
[x] IEEE Xplore Search Gateway
[ ] JSTOR Data for Research
[ ] Microsoft Academic Search API
[ ] National Library of Medicine (NLM) APIs
[x] Nature OpenSearch API
[ ] NCBI E-utilities API
[ ] ORCID API
[ ] PLOS Article-Level Metrics API
[ ] PLOS Search API
[ ] PubMed Central OAI-PMH service
[ ] rOpenSci
[x] Springer API Portal
[ ] UN Comtrade Web Services
[ ] Web of Sciences Web Services
[ ] Worldbank APIs
[ ] Worldcat Identities

From here: http://api.plos.org/

[ ] PLOS API

arXiv Default, runs fine
BioMed Central API  This is covered with Springer
Chronicling America API Irrelevant
Elsevier Scopus APIs Can only search for specific fields each time
Europe PubMed Central Irrelevant
HathiTrust Extracted Features Dataset Not Arcas- Good for data
IEEE Xplore Search Gateway runs fine
JSTOR Data for Research Not Arcas- Good for data
Microsof Academic Search API Not Arcas- Good for data
National Library of Medicine (NLM) APIs Irrelevant
Nature OpenSearch API  runs fine
NCBI E-utilities API Can only search for specific fields each time
ORCID API Not Arcas- Good for data
PLOS Search API Implemented, not happy yet
PubMed Central OAI-PMH service  Irrelevant
rOpenSci Irrelevant
Springer API Portal Implemented, not happy yet
UN Comtrade Web Services Irrelevant
Web of Sciences Web Services Not Arcas- Good for data
Worldbank APIs Irrelevant
Worldcat Identities Implemented, not happy yet

[ ] virxa

[ ] SHERPA http://www.sherpa.ac.uk/

[ ] PubRouter https://pubrouter.jisc.ac.uk/

[ ] CORE https://core.ac.uk/

[ ] Europe PubMedCentral (biomedical literature)
[ ] Jisc's PubRouter service https://pubrouter.jisc.ac.uk/
[ ] ORCID
[ ] Grants data (Gateway)
[ ] UK Data discovery service / other data portals


🐝 Allow unbalanced HTML in markdown card.

No issue.
The simpledom interpreter that the Mobiledoc DOM renderer uses does not allow for unbalanced or incorrect HTML such as that which is entered by a user.
This PR adds a step where the HTML is sanitised and balanced before being passed to simpledom.

PR will need to stay open for the moment - it or something similar will be needed to prevent the server-side exploding if there's any invalid HTML added in a markdown or embed card - cc @kevinansfield

@kirrg001 I've rebased this on top of the markdown-it PR and updated/added comments. It will need merging after the markdown-it PR is merged so that the editor can be used when writing raw HTML without it throwing errors.
It seems like overkill to add an entire browser emulation library just to fix unbalanced HTML but I'm not sure what other solutions are available because direct HTML rendering has been deprecated in mobiledoc and we're unlikely to find an alternative solution that will be as thorough at cleaning up invalid HTML.

I did a little memory test, couldn't find any big problem (with > 65k words).
Memory grows to ~500/600mb after saving a lot, but falls down to 100mb after a while.


Question regarding debugging Authenticated vs. Unauthenticated GDAX requests

TLDR: Can anyone give me a slight bit of direction where it seems my issue is stemming from (the gdax-tt source, my local system setup or the gdax WS API) as I get failed trades when following the tutorial guide and without entering gdax authentication keys but then I get websocket connection closed errors when I do provide my keys manually?
Hi, I'm trying to get my feet wet by testing out the t005_alertTrader.ts tutorial.  I'm trying to figure out if I'm running into a gdax-tt source, a local system setup or a gdax WS API issue, as I'm unable to complete a basic test trade with valid api keys.  I have tried 2 different api keys I created on gdax, both with full permissions.  I have added ENVs via dotenv but I'm unsuccessful completing a basic test trade whether I add my ENVs to the tutorial script or not.  I am able to at least connect and get responses from the GDAX WS API when I leave the tutorial script untouched as mentioned in the tutorial's advice of:
"You can set auth: null to just use the defaults, which since you have your GDAX API keys set in the environment, will automatically use those and receive authenticated messages (nice if you want to confim when your trades are filled)."
However, whenever the script sees a market opportunity and attempts to make a trade, it fails, presumably because my ENVs are not actually getting passed like the tutorial says.  I get output similar to this:
MacBook-Pro:gdax-tt goheelsgo$ ts-node tutorials/t005_alertTrader.ts
2017-09-26T13:25:53.072Z - info: Creating new Websocket connection to wss://ws-feed.gdax.com
2017-09-26T13:25:53.090Z - debug: Reconnecting to wss://ws-feed.gdax.com  in 0 seconds...
2017-09-26T13:25:53.090Z - debug: Closing existing socket prior to reconnecting to wss://ws-feed.gdax.com
2017-09-26T13:25:53.331Z - debug: Connection to wss://ws-feed.gdax.com  has been established.
2017-09-26T13:25:53.331Z - debug: Sending {"type":"subscribe","product_ids":["BTC-USD"],"channels":["ticker","heartbeat"]} message to WS server
Price:   3954.500 | Bid:   3954.490 | Ask:   3954.500 | sequence: undefined
Price:   3954.500 | Bid:   3954.490 | Ask:   3954.500 | sequence: 21336971
.
.
.
2017-09-26T13:26:17.957Z - error: Placing order failed type=order, time=null, productId=BTC-USD, orderType=market, side=buy, size=0.005, reason=A GDAX API request failed. Bad Request
(node:6783) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): Error: A GDAX API request failed. Bad Request
(node:6783) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Price:   3954.010 | Bid:   3954.000 | Ask:   3954.010 | sequence: 21336983

Now, when i set my ENVs in the tutorial script:
const options: GDAXFeedConfig = {
    logger: logger,
    auth: {
        key: process.env.GDAX_KEY,
        secret: process.env.GDAX_SECRET,
        passphrase: process.env.GDAX_PASSPHRASE
    }, // use public feed
    channels: ['ticker'],
    wsUrl: GDAX_WS_FEED,
    apiUrl: GDAX_API_URL
};

It appears to pass them in the config options, yet I get a websocket connection closed by external party 1006 error over and over again, presumably due to a timeout?
MacBook-Pro:gdax-tt goheelsgo$ ts-node tutorials/t005_alertTrader.ts
2017-09-26T13:17:53.197Z - info: Creating new Websocket connection to wss://ws-feed.gdax.com (authenticated)
2017-09-26T13:17:53.217Z - debug: Reconnecting to wss://ws-feed.gdax.com (authenticated) in 0 seconds...
2017-09-26T13:17:53.217Z - debug: Closing existing socket prior to reconnecting to wss://ws-feed.gdax.com
2017-09-26T13:17:53.446Z - debug: Connection to wss://ws-feed.gdax.com (authenticated) has been established.
2017-09-26T13:17:53.447Z - debug: Sending {"type":"subscribe","product_ids":["BTC-USD"],"channels":["ticker","heartbeat"],"signature":"<REDACTED>","key":"<REDACTED>","timestamp":"1506431873.447","passphrase":"<REDACTED>"} message to WS server
2017-09-26T13:18:53.219Z - info: The websocket feed to wss://ws-feed.gdax.com (authenticated) has been closed by an external party. We will reconnect in 5 seconds code=1006, reason=
2017-09-26T13:18:53.220Z - debug: Reconnecting to wss://ws-feed.gdax.com (authenticated) in 5 seconds...
2017-09-26T13:18:58.364Z - debug: Connection to wss://ws-feed.gdax.com (authenticated) has been established.
2017-09-26T13:18:58.365Z - debug: Resubscribing to BTC-USD...
2017-09-26T13:18:58.365Z - debug: Sending {"type":"subscribe","product_ids":["BTC-USD"],"channels":["ticker","heartbeat"],"signature":"<REDACTED>","key":"<REDACTED>","timestamp":"1506431938.365","passphrase":"<REDACTED>"} message to WS server
2017-09-26T13:18:58.366Z - debug: Sending {"type":"subscribe","product_ids":["BTC-USD"],"channels":["ticker","heartbeat"],"signature":"<REDACTED>","key":"<REDACTED>","timestamp":"1506431938.366","passphrase":"<REDACTED>"} message to WS server
2017-09-26T13:18:58.367Z - debug: Reconnection to BTC-USD successful
2017-09-26T13:19:57.911Z - info: The websocket feed to wss://ws-feed.gdax.com (authenticated) has been closed by an external party. We will reconnect in 5 seconds code=1006, reason=

The trade I'm attempting to make is around $15-20 and I've got $50 in my GDAX in USD, so I'd think I wouldn't have any issue with minimums.  I'm a bit at a loss currently as Node is not my forte--can anyone give me a bit of direction where it seems my issue is stemming from?
MacBook-Pro:gdax-tt goheelsgo$ ts-node -v
ts-node v3.3.0
node v8.4.0
typescript v2.5.2

I've checked tutorial 5 again, and the trade is placed.
BTW, Are you using v0.1.16? There were a few auth issues that have been ironed out in the latest version.

Regarding the disconnects, GDAX did have some instability a few days ago and you might have been testing during that period. If you run with the latest GTT version now, do you still have the same issues?

Awesome, thanks for double-checking.   The latter isn't as well tested (but I am working on it this week)

I'm simply trying to run tutorials/t005_alertTrader.ts as is, out of the box, i.e.:
GTT.Factories.GDAX.getSubscribedFeeds(options, [product]).then((feed: GDAXFeed) => {
     // --------------------------------------------
     // I GET HERE WITH/WITHOUT ADDING ENVS
     // --------------------------------------------

    GTT.Core.createTickerTrigger(feed, product)
        .setAction((ticker: TickerMessage) => {
            const currentPrice = ticker.price;
            GTT.Core.createPriceTrigger(feed, product, currentPrice.minus(spread))
                .setAction((event: TickerMessage) => {
                    pushMessage('Price Trigger', `${base} price has fallen and is now ${event.price} ${quote} on ${product} on GDAX`);
                    // --------------------------------------------
                    // I ONLY GET HERE WITHOUT SUPPLYING ENVS BUT TRADES FAIL
                    // AS ENVS DON'T APPEAR TO BE PASSED DESPITE WHAT GUIDE SAYS
                    // --------------------------------------------
                    submitTrade('buy', '0.01');
                });

            GTT.Core.createPriceTrigger(feed, product, currentPrice.plus(spread))
                .setAction((event: TickerMessage) => {
                    pushMessage('Price Trigger', `${base} price has risen and is now ${event.price} ${quote} on ${product} on GDAX`);
                    // --------------------------------------------
                    // I ONLY GET HERE WITHOUT SUPPLYING ENVS BUT TRADES FAIL
                    // AS ENVS DON'T APPEAR TO BE PASSED DESPITE WHAT GUIDE SAYS
                    // --------------------------------------------
                    submitTrade('sell', '0.01');
                });
        });

    GTT.Core.createTickerTrigger(feed, product, false)
        .setAction((ticker: TickerMessage) => {
            console.red(GTT.utils.printTicker(ticker, 3));
        });
});

The non-responses/timeouts occur when I hit  the calls to GTT.Core.createTickerTrigger(feed, product).  When I do not provide api authentication credentials and run the tutorial as is, any attempted trade fails.  However, whenever I add my ENVs to the GDAXFeedConfig object, the calls to GTT.Core.createTickerTrigger(feed, product) never seem to call back, which is what I assume leads to the timeout/closed connection.
I'm going to try to wipe my npm installation and start from scratch to see if that is the ticket.  Then will attempt to dig deeper into what's occurring with createTickerTrigger() for additional debugging and will report back here.

Well, I have good and bad news.  Good news: running t005_alertTrader.ts out of the box is working now when I provide my authentication ENVs.  Bad news: I have no idea why it decided to start working now as I did not change a single thing on my end from what had been failing to run previously.  I simply re-ran my existing local copy of the t005_alertTrader.ts script again for the upteenth time and it finally began to run with ticker info and attempted trades.  Perhaps it was related to the GDAX instability mentioned by @CjS77? Perhaps it was a wifi/router/local system issue on my end?  No clue. ¯_(ツ)_/¯
Whatever it was, I'm closing this issue now but will certainly add additional details as available.  Thanks for the assistance!


[BACKPORT]Fix compilation with USE_LAPACK=0 USE_BLAS=mkl (#19570)

Description
backport #19570 as a part of effort #19911

@Zha0q1 can you review ?

I think we do not need to backport this pr since ilp64 blas/lapack is only enabled on master. The original pr should be for the ilp64 code


feat: add RecordValidator

Codecov Report

Merging #20 (002ac76) into main (da208cf) will increase coverage by 1.21%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
+ Coverage   58.75%   59.96%   +1.21%
==========================================
  Files          30       31       +1
  Lines         628      652      +24
  Branches      140      147       +7
==========================================
+ Hits          369      391      +22
- Misses        245      247       +2
  Partials       14       14

Impacted Files
Coverage Δ

src/validators/RecordValidator.ts
90.47% <90.47%> (ø)

src/lib/Shapes.ts
24.39% <100.00%> (+3.87%)
:arrow_up:

src/validators/imports.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

@all-contributors please add @Khasms  for code


FEATURE: Added clips timeline and clip upload support.

I added the ability to fetch instagram reels (clips) with the graphql API and jsdom to get a needed header called fb_dtsg. The first two commits have been voided and are made up into the third.
How to get the clips timeline:
const feed = client.feed.clipsFeed();
const items = await feed.items();
const isMoreAvailable = feed.isMoreAvailable();

How to upload clips:
await client.publish.video({
  coverImage,
  video,
  isClipVideo: true,
});

what's preventing this from being merged?


Update harness-terraform-provider.md

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[x ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/DOC-3203

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Removed suppression of data element default value.

Coverage decreased (-0.01%) to 95.542% when pulling 12c7047d06918116c0c9c6b4aa75b6a19649de33 on default-suppression into b848c1cad9bc1368cc46f9864d97134a391506ef on master.


Feature Request: strokeLineCap prop

strokeLinecap is a prop already in react-native-svg. It basically gives you the option to make the stroke endpoint rounded if you want. Is this feature possible? Thanks.

This is supported (you can check the code here) but the documentation is not up to date.

Create a PR to update the doc https://github.com/73R3WY/react-native-svg-animations/pull/44

#44


chore: test switch to the axios fork/branch

switched to the repo/fork
used the adapter to get a response
logging response

Result

no error message in the console/webpack whatsoever.

Doing somethign similiar in replit with a minimal setup:
<EMAIL_ADDRESS>Result
webview devtools throw:
SyntaxError: The requested module '/node_modules/form-data/lib/browser.js?v=fce17dee' does not provide an export named 'default' (at FormData.js?v=fce17dee:1:8)

lots of activity here: https://github.com/axios/axios/pull/5146
so I think that's really the way to go, what do you think?

hey guys,
thank you for testing the adapter! 😁 i caught your tag on the PR. i'm happy to help support here if you run into errors. i'm happy to hear the browser/webpack side is running smoothly, but could you elaborate on:
switched to the repo/fork
used the adapter to get a response
logging response
Result
image
no error message in the console/webpack whatsoever.

Doing somethign similiar in replit with a minimal setup:
<EMAIL_ADDRESS>
Result
webview devtools throw:

SyntaxError: The requested module '/node_modules/form-data/lib/browser.js?v=fce17dee' does not provide an export named 'default' (at FormData.js?v=fce17dee:1:8)

what Node version is this running in / where is that occurring? that could be helpful in diagnosing this one. if this arises from an Electron context, Electron supports a maximum of Node 16, so that could be a hint for me toward solving any issues.

I think that's really the way to go, what do you think?

@bumi on the long run yes. This will be the much better approach. But if we wanted to release MV3 at the end of this year - for practical reasons - I would go for the "currently working" solution.

@escapedcat understood on the data property -- i have solved a number of issues around that in the latest betas. let me see if i can pull this down today and hunt down what's going on.

Hey @sgammon , sorry for dragging you into here :D

to be fair i went looking for trouble

to be fair i went looking for trouble

@sgammon welcome to ze internet! :D (and thanks for your work!)


How to delete tasks?

Can I delete all taks from a challenge?

Currently the only way would be to delete and re-create the challenge, or to delete them one by one. Is What is your use case?

Use case: Starting over after I discover that tasks are bad. Or maybe they are all done or so. Re-creating the challenge means I have to add metadata for the challenge again and that the new challenge has a new ID. If I have published the link to the challenge, I can't use it any more.

Fair enough. Would that make sense as DELETE /api/v2/challenge/:id/tasks ?


Remove metatools dependency

{metatools} is currently an "Imports:" dependency of admiralvaccine. Not all companies choose to use {metatools}, so we actively try to avoid making this a dependency in the open source admiral packages.
It is only being used to combine suppqual domains (combine_supp()), which could equally just be a step companies take prior to using your package/templates, as this would be then more consistent with all other admiral packages.
FYI @ahasoplakus

See latest discussions at https://github.com/pharmaverse/pharmaversesdtm/issues/112 which might impact the action taken here

Thanks @rossfarrugia @statasaurus ! Based on the discussion at https://github.com/pharmaverse/pharmaversesdtm/issues/112, I think we agree on keeping the same approach as {admiralonco} i.e. adding {metatools} to Suggests instead of Imports and also fixing the {supp_xx_vaccine} data sets in {pharmaversesdtm} that would resolve the issue in {metatools} as @statasaurus  mentioned above. For the change in {pharmaversesdtm} as @manciniedoardo mentioned "it might be good to wait to make this change and coordinate releases so that we don’t have any periods where test data is unavailable"


[labs/testing] Make WTR plugin work with on-the-fly ts compilation

Should this be an RFC?

[X] This is not a substantial change

Which package is this a feature request for?
Other/unknown (please mention in description)
Description
Currently the labs/testing WTR plugin and fixture functions only work when all test files are pre-compiled to JS before running the test.
Many projects (such as shoelace) use the esbuild plugin for web test runner for on-the-fly compilation of ts files. This is useful for not having to remember to run ts compilation before running tests, or for quickly iterating on tests and running it in watch mode.
Currently, the plugin does not work with the ssr testing plugin as dynamic imports expect .js file extensions and the esbuild plugin only works on browser requests, not dynamic imports done on the dev server.
Alternatives and Workarounds
Tests for packages in Lit do not use the esbuild plugin, and instead pre-compile all TS files to JS before running tests. Coordination of this is handled with wireit so that running the test command automatically runs the build command if needed.
To support on-the-fly compilation, the lit ssr testing plugin's server code would need to detect and apply the same esbuild plugin settings for server-side dynamic imports (in addition to browser requests).

I don't think that our testing package should have direct integration with esbuild or really any particular build system. Maybe we can add a config option for an import function, the default implementation of which just calls import(). Hopefully someone using esbuild can provide an implementation that calls esbuild first.

An extension point around import might help. Do you imagine that we'd still need to write the compiled file to disk, so that a module can be materialised? Pseudocode:
async function myCustomImport(path) {
  const compiled = await compileWithEsBuild(path)
  await writeToDisk(path, compiled)
  return import(path)
}

node does not yet have good support for creating in-memory es modules via its vm module https://nodejs.org/api/vm.html#class-vmmodule
I suppose in the ideal would be that the file can be imported from the WTR server itself via http. That way all the same esbuild/rollup plugins are applied. But unfortunately importing from http(s) urls is not generally available in node either: https://nodejs.org/api/esm.html#https-and-http-imports

The nice thing about an import hook is that whatever facilities are available in the Node environment are available to use in the hook, even as things change.
I don't actually know the best way to integrate a WTR build setup with a otherwise plain Node import/fs operation (this is one of many reasons I personally prefer to to builds as their own non-integrated step with an npm script). WTR obviously has a way to get the bytes for a particular file internally, maybe that can be called to get bytes to write to disk.

yeah of course.
i guess it feels like something is amiss if the testing package is implemented as a WTR plugin, but it does not integrate with how many people use WTR. i was hoping this would be a quick win to add to our DS. i'll revisit again in future when node is better equipped for this.

I have created a PR as a base for this issue: #4730
It would be possible to extend the PR to allow an easy configuration for supporting .ts files.


After update synctrazor does not start in W10, before was working ok for years....

Error   ooops!  something went badly wrong
Version: <IP_ADDRESS>; Variant: Installed; Arch: X86
Path: C:\Program Files (x86)\SyncTrayzor\SyncTrayzor.exe
System.IO.FileNotFoundException: CefSettings.BrowserSubprocessPath not found.
File name: 'C:\Program Files (x86)\SyncTrayzor\CefSharp.BrowserSubprocess.exe'
at CefSharp.Cef.Initialize(CefSettingsBase cefSettings, Boolean performDependencyCheck, IApp cefApp)
at CefSharp.Cef.Initialize(CefSettingsBase cefSettings)
at SyncTrayzor.Pages.ViewerViewModel.OnInitialActivate()
at Stylet.Screen.<Stylet.IScreenState.Activate>b__35_0(ScreenState oldState, ScreenState newState)
at Stylet.Screen.SetState(ScreenState newState, Action2 changedHandler)    at Stylet.Screen.Stylet.IScreenState.Activate()    at Stylet.ScreenExtensions.<>c__DisplayClass4_0.<ActivateWith>b__0(Object o, ActivationEventArgs e)    at System.EventHandler1.Invoke(Object sender, TEventArgs e)
at Stylet.Screen.<>c__DisplayClass35_0.<Stylet.IScreenState.Activate>b__1()
at Stylet.Execute.OnUIThread(Action action)
at Stylet.Screen.<Stylet.IScreenState.Activate>b__35_0(ScreenState oldState, ScreenState newState)
at Stylet.Screen.SetState(ScreenState newState, Action2 changedHandler)    at Stylet.Screen.Stylet.IScreenState.Activate()    at Stylet.ScreenExtensions.TryActivate(Object screen)    at Stylet.WindowManager.WindowConductor..ctor(Window window, Object viewModel)    at Stylet.WindowManager.CreateWindow(Object viewModel, Boolean isDialog, IViewAware ownerViewModel)    at Stylet.WindowManager.ShowWindow(Object viewModel)    at Stylet.BootstrapperBase.DisplayRootView(Object rootViewModel)    at Stylet.Bootstrapper1.Launch()
at SyncTrayzor.Bootstrapper.Launch()
at Stylet.BootstrapperBase.Start(String[] args)
at Stylet.BootstrapperBase.b__9_0(Object o, StartupEventArgs e)
at System.Windows.Application.OnStartup(StartupEventArgs e)
at System.Windows.Application.<.ctor>b__1_0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

IT WAS SOLVED   adding folowing command line flag:
-allow-newer-config
in advanced settings


Doesn't handle incompatible value property

Everytime i'm facing some HTML using property such as 'initial', 'normal', ect.
It is isn't handled properly by this library
Warning: Failed prop type: Invalid prop `textDecorationColor` supplied to `Text`: initial
Warning: Failed prop type: Invalid prop `display` of value `inline` supplied to `Text`, expected one of ["none","flex"]
Warning: Failed prop type: Invalid prop `letterSpacing` of type `string` supplied to `Text`, expected `number`.
Bad object: {
  "letterSpacing": "normal"
}
Warning: Failed prop type: Invalid prop `textDecorationStyle` of value `initial` supplied to `Text`, expected one of ["solid","double","dotted","dashed"].
Failed prop type: Invalid prop `textAlign` of value `start` supplied to `Text`, expected one of ["auto","left","right","center","justify"].

I can't possibly ignore all these styling.
Using react-native-render-html: 3.9.3,

I think we should set up some kind of object that holds every conversion that needs to be done when a style property is available both in the browser and react native but with different accepted values.
The current logic where '18px' is converted into 18 just doesn't cut it. We need to remove specific code and handle all of this into a single helper.
This should be one of the last major steps towards being able to render any HTML string without crashing.

I also have this crash

any follow up on this?

For me its an invalid propety in 'letterSpacing'

any one fixed this bug successful . I have faced it with props display 'inline': should be one of (flex, none)

I have this issue too :
Warning: Failed prop type: Invalid prop `letterSpacing` of type `string` supplied to `ForwardRef(Text)`, expected `number`.

I have this issue too
Invalid property caused a crash
Warning: Failed prop type: Invalid prop textAlignof valuestartsupplied toForwardRef, expected one of ["auto","left","right","center","justify"].

I have this issue too!
Please follow on this

I have this issue too!
Please follow up on this
v4.1.1

Had the same issue with this library and spend almost 2 days trying to prevent the app from crashing. At the end i've fixed this issue in a different way. I have used the inbuilt WebView component for html rendering. Two issues i faced with WebView component are:

Dynamic height for the view based on the html content.
to make the clickable links to open in an external browser.

I've fixed both the above issues in the following way.
const script =

; const style =

;
<WebView                  ref="webview"                  originWhitelist={['*']}                  source={{html: this.state.htmlcontent + style + script}}                  style={{ height: this.state.contentHeight}}                  scrollEnabled={false}                  onNavigationStateChange={this.onNavigationChange.bind(this)}>                </WebView>
onNavigationChange(event) {    if(event.navigationType && event.navigationType === 'click') {      this.refs.webview.stopLoading();      Linking.openURL(event.url);    }    else if (event.title) {      const htmlHeight = Number(event.title) //convert to number      this.setState({contentHeight:htmlHeight});    }  }
Hope this helps...

What would be the simplest way of completely ignoring the style attribute entirely?

ds8k !! was wondering the same. Ignoring styles fixed this issue. I ignored this by using this prop allowedStyles={[]}

ds8k !! was wondering the same. Ignoring styles fixed this issue. I ignored this by using this prop allowedStyles={[]}

This solution worked well.

Thanks @saadzaman !! Good to go

ignoredStyles={['font-family', 'display','text-align',]}
allowedStyles={["none","flex"]}

I have implemented a bunch of fixes, see #382, which should also fix what you've all encountered here. If you happen to still have an issue after release 4.2.2, please open an new ticket. Closing now, expecting release very soon.

This issue will be fixed in version 4.2.2.
A pre-release is already available if you want this fix now, see #385.


New version: NamedTupleTools v0.8.0

Registering package: NamedTupleTools
Repository: https://github.com/JeffreySarnoff/NamedTupleTools.jl
Created by: @JeffreySarnoff
Version: v0.8.0
Commit: 2b5f6037d8e1a094e1e398b8dceea9028bf4540d
Reviewed by: @JeffreySarnoff
Reference: https://github.com/JeffreySarnoff/NamedTupleTools.jl/commit/2b5f6037d8e1a094e1e398b8dceea9028bf4540d#commitcomment-33638659
Release notes:

dict(nt::NamedTuple)::Dict
faster NT <--> Dict
removed deprecation

GitHub did not fire any webhook apparently? TagBot tag

TagBot tag
Apparently GitHub is back to life

TagBot tag plssss GitHub

TagBot tag


Attempt to read from field 'int android.view.View.mViewFlags' on a null object reference

The sample app is crashing after a backwards scene transition. It seems like this is happening on Android 5.x and above. It looks like an bug in View#dispatchDraw when calling removeFromParent under very specific conditions. I haven't found the exact cause, but there's a workaround in the 84 branch.

should be fixed by #89


feat(layout): add Ticket layout with grid css system

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Jest 25 with node env fails on node 10.14.1

💥 Regression Report
This is more to make people aware of what I found than an issue that should be fixed. After updating to jest 25.1.0 I saw some of my test suites failing with errors like ReferenceError: describe is not defined and ReferenceError: beforeAll is not defined. Turns out the issue only occurs when using "testEnvironment": "node" with node 10.14.1 (and jest 25). Upgrading to node 10.14.2 fixes the issue (or not specifying a testEnvironment), so perhaps a node bug. Either way I wanted to post this here in case anyone comes across the same issue.
Last working version
Worked up to version: 24.*
Stopped working in version: 25.1.0
To Reproduce
Steps to reproduce the behavior:
I created a minimal repro here: https://github.com/AndrewLeedham/repros/tree/1f7e042e241e2f439bd69d1073bafffa5200beb5/packages/jest-25-node

I wouldn't clone the repo because it is a monorepo and things get messy with deps. Just download it as a zip I guess.
Either use nvm to switch to 10.4.1 or run the docker:build script.
Depending on the above either run the test script or docker:test script.

Expected behavior
No errors with global jest functions in test suites.
Link to repl or repo (highly encouraged)
https://github.com/AndrewLeedham/repros/tree/1f7e042e241e2f439bd69d1073bafffa5200beb5/packages/jest-25-node
Run npx envinfo --preset jest
Paste the results here:
System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 10.14.1 - ~/.nvm/versions/node/v10.14.1/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.14.1/bin/npm

For anyone having this issue, just upgrade to 10.14.2 and it should fix!

For anyone having this issue, just upgrade to node version to 10.14.2 and it should fix!

THANK YOU! I would never have thought to check node version while debugging my issue, but this was it.

For anyone having this issue, just upgrade to node version to 10.14.2 and it should fix!

@manwithsteelnerves THANK YOU! I would never have thought to check node version while debugging my issue, but this was it.

@AndrewLeedham, you saved me from head ache brother. Thank you.


Storage pointer alignment in nalgebra

See the discussion in #480 for details.
We need to see when and how we want pointers of matrices (including empty matrices) to be aligned.

Just want to add that we really should investigate the claim that storage needs to be aligned thoroughly. On modern microprocessors, whether or not data is aligned may be largely irrelevant for performance reasons. Many SIMD instructions are identical for aligned/unaligned storage on modern hardware. There may be a slight issue with unaligned storage cross cache boundaries, however, but we should in any case try to measure any such effects.
On the other hand, dealing with alignment adds complexity. For an example of this complexity, just look at Eigen (C++ library): due to alignment considerations it is undefined behavior to store aligned types in standard library data structures (e.g. std::vector<Matrix4d>), or in structs (e.g. struct MyStruct { Matrix4d m; }).


Refactor map*ToProps functions to improve performance

In the code snippet,
function mapStateToProps(store) {
  return {
    val: store.getState().val
  };
}

module.exports = connect(mapStateToProps)(React.createClass({
  render: function() {
    return (<p>{this.props.val}</p>);
  }
}));

mapStateToProps will run on every store update; render will only run when the .val which is assigned to props changes.
We can use this knowledge to make smarter decisions about how we write our mapStateToProps method: for example, any code that derives or iterates on the results of store data should go into a method on the component, not in mapStateToProps, because there is no need to compute a generated value unless the original value has changed.
Making these updates across the app should resolve the lag we experience when dragging objects on the stage.

I can't find the specific PR but I believe this has been taken care of. A quick grep through the codebase doesn't reveal any toJS calls being made within mapStateToProps.


React 17+ support

Bonjour @Almouro, do you have any plans to support React 17 and 18? Merci

Bom dia @hnqlv!
So far, the plugin is reporting FPS exclusively from the native side, so it supports RN apps with React 17 or React 18
Or do you mean support for web apps?

@Almouro yea sorry, talking specifically about react-native-startup-trace package:
"peerDependencies": {
  "react": "^16.8.1"
}

Oh right, should probably move that one into it's own repo 😅
It should be compatible with both React 17 and React 18 for sure, I'll update the peer dependencies

@Almouro great! I wanted to make sure before forcing the peer deps! 😆 Appreciate the fast response, cheers!


try - catch in runPutEffect drops thrown errors

https://github.com/yelouafi/redux-saga/blob/master/src/internal/proc.js#L437 does a dispatch within a try - catch and drops any thrown errors, which means thrown errors within any rendered component, or connected redux containers, rendered as a result of the dispatch simply get lost.
The dispatch that made me notice this issue triggered a connected redux container component to render where I attempted to do return: {foo: bar.baz} by mistake inside a redux mapStateToProps, where bar was undefined. Normally I'd just get a Cannot read property 'baz' of null letting me fix my error immediately, but because of the try - catch all I see in Chrome's devtools is:
uncaught at root
 at root
 Invariant Violation: Attempted to update component `Example` that has already been unmounted (or failed to mount).

I'll attempt a reduced testcase if this issue report isn't enough.

Note: I haven't investigated this very thoroughly yet, so I just realised redux saga rethrows the error further up and my issue is elsewhere...

We'll do smth about this, we just need to figure out what
see https://github.com/yelouafi/redux-saga/issues/632

Thanks, I'm subscribing to that issue now.


CSA0501 is reported for partial methods

Partial methods cannot specify visibility, so CSA0501 should not be reported for them.

Thanks for reporting this issue. Since it is not a feature I use, I didn't think about it.
Anyways, I just fixed it and publish the fix on NuGet (version 0.1.3)


Merge 1.5.8

TravisCI failure
==> brew tests --online
Failures:
  1) brew search falls back to a GitHub tap search when no formula is found
     Failure/Error:
       expect { brew "search", "caskroom/cask/firefox" }
         .to output(/firefox/).to_stdout
         .and output(/Searching/).to_stderr
         .and be_a_success
          expected block to output /firefox/ to stdout, but output nothing
       ...and:
          expected #<Proc:0x00000003f47830@/home/travis/build/Linuxbrew/brew/Library/Homebrew/test/cmd/search_spec.rb:29> to be a success

I'm hoping that this failure is transient. Rebuilding.

The above TravisCI error was transient. Merging.


[Bug]: Tag a new release fixing python 3.11 support

What Operating System(s) are you seeing this problem on?
Linux (x86-64)
dlib version
19.24
Python version
3.11
Compiler
GCC 12
Expected Behavior
python 3.11 is landing on several arches and current version does not build with it. I think a new release including the fixes in master would be interesting then
Thanks
Current Behavior
Fails to build with python 3.11
https://github.com/davisking/dlib/issues/2734
https://github.com/davisking/dlib/issues/2659
Steps to Reproduce
Try to build it with python 3.11 and hit known bugs of latest release
Anything else?
No response

This is annoying me on Gentoo atm

Same problem

What is the issue here exactly?  I just now did pip install dlib on Ubuntu using Python 3.11.2 and dlib installed and appears to work as normal.

Then maybe a newer release being offered in pip over github releases :thinking:

Oh, you all using the v19.24 tag in github?

Many distributions, not only on Gentoo:
https://repology.org/project/dlib/versions

Yeah in pip there is a dlib 19.24.1 that is basically what's in git master right now.  We are still working on some stuff, and will tag an official 19.25 in a month maybe.

Who packages git branches besides Arch folks, terrible practice! Looking forward to an easy update sooner than later

I'm not sure what exactly you are asking for. You just want me to make a git tag for you like 19.24.2?

This is annoying me on Gentoo atm

But you're using Gentoo, compiling packages should be your bread and butter.

I'm not sure what exactly you are asking for. You just want me to make a git tag for you like 19.24.2?

Synchronize the releases with the fixed version from pip... it seems 19.24.1 has the needed fixes per the comments here, but the last tag and release in github is from Nov 2022 and is not compatible with python 3.11
Thanks

No problem, just tagged v19.24.2.

It works fine, thanks a lot!


OHRI-2317: Mother’s name to display on the “Child visits” table and Infant banner

Requirements

[ ] This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes the ticket number in the format OHRI-123 My PR title.
[ ] My work includes tests or is validated by existing tests.

Summary

This is a follow-up  to ensure we exclude the patient from their own children list
Screenshots

Related Issue

Other

You may need to check why that e2e test is failing as well

the tests are e2e passing @ODORA0


[Snyk] Upgrade net.portswigger.burp.extensions:montoya-api from 2023.10 to 2023.12.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade net.portswigger.burp.extensions:montoya-api from 2023.10 to 2023.12.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 5 versions ahead of your current version.
The recommended version was released a month ago, on 2023-12-08.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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


The "Debugging in Visual Studio Code" section should be updated to reflect all supported chips

Added this as a task in #105


docs: Update custom authentication code snippets

What's new?

Open GH discussion: https://github.com/rainbow-me/rainbowkit/discussions/884

There seems to be a typo and missing pieces in the docs regarding custom authentication, see: https://github.com/rainbow-me/rainbowkit/issues/680
So I decided to make two working boilerplates following the examples in that GitHub issue, you can find them here:

Frontend: https://github.com/smakosh/SIWE-Next.js
Backend: https://github.com/smakosh/SIWE-Express.js
Demo: https://twitter.com/smakosh/status/1594872447173623810

https://giphy.com/gifs/please-bored-anon-Ass7N88ITsb3a

Thanks for this contribution @smakosh. We'll get these doc improvements in after a few tweaks for simplicity/clarity


First human pass on FR translations

This is a first human pass on the translation done initially with Deepl (I think). What was done:

Fixing obvious errors.
Applying first semantics check.
Standardizing infinitive and imperative forms.
Harmonization of terms and verbs.
Applying WordPress French glossary for global consistency.
Enforcing French typography rules - at least those that are used with WordPress translations.

There's many thing to do to have a great translation but THIS is a first step in the right direction 🙂

Thank you for your contribution to this project!


API performance issues  (packages endpoints)

Let's focus on the Package-related endpoints for now as those are the ones used to collect vulnerability data in DejaCode.
Those tests were run on a clean install of VCIO with only the nginx.NginxImporter data set.
Package.objects.all().count()  # 88
Vulnerability.objects.count()  # 39

It's a very small amount of data but somehow looking at a single Package triggers over a thousand queries.

Package list /api/packages/ (on only 88 packages) -> 6,124 queries: 5706 similar queries.  Duplicated 73 times.
Package details /api/packages/63 -> 1,329 queries: 1230 similar queries.  Duplicated 16 times.
Bulk search /api/packages/bulk_search (providing the 88 purl): 39,925 queries.

This is quite problematic in the context of batch data collection using the VCIO API.
The PackageSerializer and related QuerySets require optimization.
Once done, make sure to implement unit test using the assertNumQueries to make sure that future code change do not add uncontrolled queries back.
Related issues:

https://github.com/aboutcode-org/vulnerablecode/issues/1492
https://github.com/aboutcode-org/dejacode/issues/94#issuecomment-2298445423
https://github.com/aboutcode-org/vulnerablecode/issues/1549

For bulk lookup, we track this here:

[ ] #1561

First batch of improvements went in with this PR:

https://github.com/aboutcode-org/vulnerablecode/pull/1547

More to come

The performance is now acceptable. We need to9 make sure we save a baseline of performances.

FYI, the key code to get this fixed is the new API design in #1572

@tdruez @TG1999 is this completed and closable? If yes, please do!

@TG1999 I've run some data collection using the previous and the new implementation (api v1).
Fetching for 133485 Packages, using bulk_search, with 100 PURL entries per request, so about 1,334 HTTP requests total

Previous: Completed in 39.5 minutes
New: Completed in 21.0 minutes

Seems like we double the performance on the package endpoint.


Crashes when adding shortcut

Finbar crashes as soon as I press any key when trying to add a keyboard shortcut to activate.
I've attached crash reports. I've rebooted computer and same issue. Currently stuck with no keyboard shortcut to activate Finbar which reduces it usefulness quite a lot.
Archive.zip

Thank you so much for reporting — I was able to reproduce the issue. Expect a fix later today!

Nice thank you!

Fixed in v1.13.1 released today!
Sorry for the delay and for your initial negative experience with my app. I’m certain it’d change for the better 🙏


Feedback 'From: Katarina Batina Fonts aren't loading in m...'

Message from katarina batina sent on 2016-12-21 16:37:17 UTC###

From: Katarina Batina
Fonts aren't loading in mg views in eigen

Link to HockeyApp

https://rink.hockeyapp.net/manage/apps/37020/feedback/686728

Fixed with https://github.com/artsy/microgravity/pull/102


Google storage configuration with GCS

We are trying to follow your excellent self hosting documentaiton for GCP but it seems to be missing some key components. Namely GCS - there is no way to configure google storage as a binary storage for files.
Searching through the sourcecode for implements BinaryStorage yields only 2 responses - one for file storage and one for S3. There is no documentation anywhere about GCS for binary storage.
The only way to use it seems to be via GCS' s3 compatibility interface which we've remarked on before. As it stands though it cannot be fully used as s3 code doesn't allow signed urls that are coming from s3 itself - a feature that we are using in prod right now. Hence we had to fork medplum for it https://github.com/medplum/medplum/pull/5445 .
So are there any plans on fully supporting GCP soon or should we just continue using our fork?

Additionally there seems to be a discrepancy between the gcp self hosting docs and what I could read from the terraform manifests namely the absence of cloud armor and the GCS configuration. Am I missing something obvious there?


firefox does not show text in svg from ggplot2

In firefox, this notebook: http://sharing.beakernotebook.com/gist/anonymous/a119ba0126f280b2d041
none of the text shows in the plots.
must be a font problem...

right now i am thinking this is http://stackoverflow.com/questions/13673441/svg-use-element-and-hover-style

the problem comes from this css in bootstrap:
svg:not(:root) {
    overflow:hidden
}

if i remove that it fixes my test case.

uh maybe not. back to square one.  even with no css i can't get the text to show up on ffox in the full app.

I put my test case in this fiddle: http://jsfiddle.net/e1zgzacj/
on chrome i get a black triangle.  on ffox i get nothing.  and indeed if you go into the css and delete the rule quoted above (lines 88-90) then the triangle shows up on ffox too.

another possible approach would be to avoid the  elements by rendering text natively.
apparently there is another svg device driver that does this: http://stackoverflow.com/questions/17555331/how-to-preserve-text-when-saving-ggplot2-as-svg

If plotmath is impossible in RSvgDevice then plan C would be to rewrite the SVG from the standard driver and do the <use> expansions manually.

Here's the branch with RSvgDevice support https://github.com/twosigma/beaker-notebook/tree/spot/alt-svg-driver

https://github.com/twosigma/beaker-notebook/pull/1120


Allow STANDARD-XML searches

Currently 'rets.session.search' has an option for 'response_format' 'STANDARD-XML' but as far as I can tell it's not implemented. Add a simple implementation using 'xmltodict'.

It gets added to the parameters dictionary, which in turns gets turned into parameters for the search request:
https://github.com/refindlyllc/rets/blob/master/rets/session.py#L323

@mcrowson Thank you. I guess my question is regarding 'search_cursor.generator(response=response)'. In 'rets.parsers.search.generator' it parses only RETS xml. Would a general xml implementation be possible ? Just basically return 'xmltodict(response.text)'. This came up because "CREA" mls has a 'STANDARD-XML' option that is not fully RETS compliant. Here is an example:
OrderedDict([(u'RETS',
OrderedDict([(u'@ReplyCode', u'0'),
(u'@ReplyText', u'Operation successful'),
(u'COUNT', OrderedDict([(u'@Records', u'2')])),
(u'RETS-RESPONSE',
OrderedDict([(u'@xmlns',
u'urn:CREA.Search.Property'),
(u'Pagination',
OrderedDict([(u'TotalRecords', u'2'),
(u'Limit', u'100'),
(u'Offset', u'1'),
(u'TotalPages', u'1'),
(u'RecordsReturned',
u'2')])),
(u'PropertyDetails',
[OrderedDict([(u'@ID', u'20270723'),
(u'@LastUpdated',
u'Sun, 27 Jan 2019 20:42:05 GMT'),

I initially tried using xmltodict on the listings responses (we use it elsewhere in the library) but not knowing a consistent response format from the various RETS servers kept giving us inconsistent results. Which is why we end up using Python's native XML library to get the rows: https://github.com/refindlyllc/rets/blob/master/rets/parsers/search.py#L18
I'd love to see it work though if you want to try a new approach.

@mcrowson here is an option to pass a custom parser:
https://github.com/refindlyllc/rets/compare/master...cmdevpy:search-parser?expand=1
Is this okay ? If so I'll open a pr.

That looks awesome, PR welcome

OK, pushed 0.4.8 which includes this. I made a few stylistic changes but the core of it should still work. Give a shout if something is amiss.
Thanks for the contribution!

Looks great. Thank you !
On Thu, May 2, 2019 at 12:49 PM MCrowson<EMAIL_ADDRESS>wrote:

OK, pushed 0.4.8 which includes this. I made a few stylistic changes but
the core of it should still work. Give a shout if something is amiss.
Thanks for the contribution!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/refindlyllc/rets/issues/200#issuecomment-488788160,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL63Z5ZKHMXKF3JQHI7EO33PTMZUTANCNFSM4HJXTGPA
.


feat: add docker-compose support

Close #6

facing same problem with https://github.com/microsoft/DockerTools/issues/209, and exclude .dcproj from package references solves problem

facing same problem with https://github.com/microsoft/DockerTools/issues/209, and exclude .dcproj from package references solves problem


🪲[Bug]: Error in autocomment in Pull_Request_template.tmd

Describe the bug
As we create a pull request, we get an error stating auto comment failed as in the ss below.
To Reproduce
Steps to reproduce the behavior:
create a pull request and see notifications in github
Expected behavior
We should get a comment saying thank you instead of the error.
Screenshots

Additional context
I have corrected this error. Kindly assign me this issue as a contributor under GSSOC'24.

@vansh-sardana still error persists

let me check once sir

It did work on my branch. see this pull request https://github.com/vansh-sardana/ScrapQuest/pull/1#issuecomment-2182181706. Will work on it to see where else may be the issue.


Localization doesn't work (v0.14.3)

Localization doesn't work in v0.14.3 (by property and by direct use of moment)
In v0.14.2 it works

I can confirm this

I'm going to fix it at the weekend.
localization prop works, by the way.

localization prop works, by the way.
Unfortunately no.. At least for DateInput. But works in the previous version (0.14.2)

The bug was introduced here b70a11ece45b1d3a35c38394d458e99d39bdd07c. Even though we set locale on app level moment.locale('ru'), moment is imported on module level and I guess this moment instance uses default locale. To avoid this, we need import locale on app level. Like this:
import moment from 'moment';
import 'moment/locale/ru';

It sets locale globally. So fore example, you have global ru locale and if you need to change it programmatically you can use localization prop.
I update readme to explain this.

localization prop works for me with v0.14.3. @twens could you test if the above explained solution works globally and with localization property?

in v0.14.4  localization prop works correctly.
what about global locale setting
import moment from 'moment';
import 'moment/locale/ru';

it works only when I set any localization  prop. even empty string localization=""

It's something odd. It works for me perfectly.

Strange. But anyway now it works and I close the issue


There is no client for the RateCard REST API

While this project includes a client for the Usage REST API, it does not include a client for the complimentary RateCard REST API. This makes it impossible to use the usage client for cost analysis without manually implementing your own RateCard client.
Can we provide a client for the RateCard REST API?

@Matt-Westphal Can you please assign this appropriately on the billing team

It has already been over 9 months.
When is RATE AIP client planned for implementation?

@markcowl any updates on this? Is there an alternative that API that we should be using?

@markcowl @Matt-Westphal Is there any progress here? We are looking for the same functionality to use internally.

@Matt-Westphal ping.

This has been an old thread. From what I can gather, that API is EOL. I do see new APIs under Consumption. You can try out the SDK here.

This has been an old thread. From what I can gather, that API is EOL. I do see new APIs under Consumption. You can try out the SDK here.


Uncaught Exception: Attempting to call a function in a renderer window that has been closed or released. Function provid

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.0.1
Time: Tue Mar 29 2016 15:01:57 GMT 0300 (FLE Daylight Time)
Error:
Attempting to call a function in a renderer window that has been closed or released. Function provid
Error: Attempting to call a function in a renderer window that has been closed or released. Function provided here: Object.<anonymous> (C:\Users\Joel\AppData\Local\GPMDP_3\app-3.0.1\resources\app\build\inject\GPMInject\interface\mouseButtonNavigation.js:8:8.
    at BrowserWindow.callIntoRenderer (C:\Users\Joel\AppData\Local\GPMDP_3\app-3.0.1\resources\atom.asar\browser\lib\rpc-server.js:201:19)
    at emitTwo (events.js:92:20)
    at BrowserWindow.emit (events.js:172:7)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #470


reddit/web: check if subreddit is available

Request on the support server to check whether
a given subreddit does not exist, and to fail if so.
Thanks to @mrbentarikau for poking at Reddit's API and finding a better endpoint to use, that way this is the only PR required for this functionality.

Addressed the feedback, thanks!

As it stands currently, this is still all wonky and based on maybes etc., also reddit does not like bots calling endpoints without proper authorization (i.e. bearer token).
Converting to draft for now, until I come around and doing it properly with token authorization.

Closing, I don't have the time nor energy to further work on this. If anyone else is interested, then please submit a patch!


Flake fixes

Fixes the flakes found using:
flake8 --ignore=E,W,F999  .

We'll need to decided what to do about this one:
./util.py:7:1: F401 '.core.util.Aliases' imported but unused

I've fixed all the flakes in bokeh except this one:
./plotting/bokeh/chart.py:628:42: F821 undefined name 'style_element'

I still have to fix the flakes in the mpl and plotly backends. I might recommend a squash merge of the PR now so that Philipp can get on with a few bokeh fixes

@philippjfr Ready to review/merge. Probably ASAP so you can make those final fixes...

Okay, thanks for these tedious fixes. Merging.