Adding additional options to the types plugin

Add the ability to provide a template for the text of the node and also default attributes for the a_attr property.  The idea here is to provide a way of keeping HTML related to a node in javascript as opposed to providing it in the JSON.  Building out HTML on the server isn't necessarily ideal.  Let me know if there's another approach or if I missed something.
Below is an example.
$("#container").jstree({
'plugins': ["wholerow", "types"],
'types': {
'organization': {
'template': '{{orgId}} {{success_width}}% ({{success_total}}){{warning_width}}% ({{warning_total}}){{danger_width}}% ({{danger_total}}) Total: {{item_total}}',
'a_attr': {"style": "width: 99%; display: inline-flex; flex-direction: row;"}
},
'text_with_total': {
'template': '{{text}} {{total}}'
}
},
'core': {
'data': [{
"type": "organization",
"template_data": {
orgId: 'A',
'success_width': 50,
'success_total': 100,
'warning_width': 30,
'warning_total': 60,
'danger_width': 20,
'danger_total': 40,
'item_total': 200
},
"children": [{
"type": "organization",
"template_data": {
orgId: 'B',
'success_width': 80,
'success_total': 80,
'warning_width': 0,
'warning_total': 0,
'danger_width': 20,
'danger_total': 20,
'item_total': 100
},
"children": [{
"text": "Summary",
"children": [{
"text": "D",
"children": [{
type: "text_with_total",
template_data: {
text: 'A',
total: 3
}
}
]
},
]
}]
}]
}]
}
});

Sorry, I can not merge this, as templating is out of the scope of the types plugin, maybe you should package this as a separate plugin? I will however see if I can expand the types plugin to provide default values, but not only to a_attr.
Thank you.

Vakata,
I'll be happy to try and separate the templating into a separate plugin.  I will get back with you on that.


Create "URL link generator" component

From reqs:

URL link generator for: www.DOMAIN.com/send/0zk123...456 or www.DOMAIN.com/send/something.crypto, which would prefill the “to” field.

Let's create a small component that takes an input value and generates a send link for the user.

Where do you guys think this component will go @wildmolasses @mds1? Would it be a separate page or a button under the form?

Wdyt of doing it like we have on Umbra, where you fill out the form and then can either use that form info to send (here, shield) or use it to creat a payment link? Though if we don't actually support all the fields and it's only "to" hat we support, maybe a separate page is better?

Actually, I think we should just do it on the same page with a secondary style button, like Umbra. We can address any UX confusion with a tooltip or something that indicates only the address is used for payment links. But adding a second page feels like it'd be more work for minimal benefit


Make Style/HashSyntax a bit faster

The RuboCop::ProcessedSource#valid_syntax? check is rather slow, so let's first do a fast check against a simple regex. The regex will probably not match all correct inputs, in which case we fall back to calling RuboCop::ProcessedSource#valid_syntax?.
The regex was built by running RuboCop against the Rails 4.2.4 source code with a puts sym_name after the regex.
I have not written a performance test as such, but instead run it against a repository of ~2500 files:
$ time rubocop -f o --only HashSyntax

Before:
rubocop -f o --only HashSyntax  22.83s user 0.30s system 99% cpu 23.147 total

After:
rubocop -f o --only HashSyntax  19.94s user 0.23s system 99% cpu 20.198 total

Interesting change. Decent improvement in speed.
I have also been working on some performance/memory enhancements to RuboCop. I really need to put in some small pull requests.

I'm fine with the suggested change, but it has to be clarified a bit in the code and the changelog and this PR has to be rebased.

:+1:


refactored using URL object

Yes you are right, the params values can be dynamic
But as per my knowledge the params are not part of the function. If you want me to receive params as an argument in the getURL function, it can definitely be dynamic


buffer rbenv-help output for printing

This PR:

Buffers the help output so that it is printed all at once, rather than a "scrolled" output
L103 requires a trailing space after a newline, otherwise bash strips newlines when strings are "psuedo-returned" from a function

Prior (unbuffered)

Buffered

Hey Mislav 👋, sorry I should have made a case for it first.
If the default help output seems like it's lagging to print for the end user, it lowers the user's confidence in the cli tool's quality. I'd also consider it be an UX issue to have the end user try read text immediately after each block is quickly printed (The GIFs don't capture it well enough unfortunately) for what is less than a paragraph of total text.
I should also note that rbenv+pyenv is the only cli tool I have installed which has this effect, so it's jarring every time I run into it (enough for me to make this PR). So I'd argue it's "bad" because it's not the normal behaviour of what users have come to expect from cli tools when they print their help output (perhaps even anti-pattern?).

Hey @mislav any update to my previous post? I'll understand if you think this is unimportant, unnecessary etc., I'd just like some closure on this Pr (I'm doing a cleanup of my PRs, and this is over a year old 😮)

Also "scrolled" output wasn't the right term, sorry for the confusion there.

Personally, I'm 👎 on this.
While I can appreciate there is a visual difference between progressive rendering and buffered, I disagree with both of these assertions:

it lowers the user's confidence in the cli tool's quality.

UX issue to have the end user try read text immediately

If we agree that it takes, let's say 2 seconds to completely render the output; and current behavior is to progressively write lines throughout the duration of that 2 seconds, isn't it a performance degradation to hold all that output in a buffer before it is printed? I'd be more wary of tools that have an initial lag (as would be indicated with a buffer-induced delayed print) because that would typically indicate non-trivial boot-up time. Printing ASAP indicates no such boot-up penalty.
As for reading text immediately, there isn't any rendering of the output that would make the printed text reflow as new output is written. (ie, the jarring reflow of text in an HTML page as image assets are loaded and force reflows). With this output, once the text is printed, it's stationary. So I'd argue that it's a performance and UX improvement to be able to start reading the output as soon as possible. (of course, without any actual UX studies we're just stating our personal opinions; but this is mine 😸 )
More importantly, for *nix tools, buffering is (usually) an anti-pattern because it consumes memory. Being able to pipeline the output from one command to a chain of many others without concern (generally) for the size of the text is a benefit of unbuffered streaming. Granted, the size of the output we're talking about here for rbenv is beyond negligible; and users are unlikely to be piping help output to many other tools. (Other than perhaps less/more/grep) But we'd be behaving counter to other unix tools for little to no reason (IMO).

I should also note that rbenv+pyenv is the only cli tool I have installed which has this effect, so it's jarring every time I run into it

With this I agree (and add nodenv to the list of affected tools), and it's due to how the help text is generated. Rather than having the help output exist within the tool as static content, it is generated dynamically by parsing the comments at the beginning of its own scripts, and by searching within the tool to find the available commands. In a sense, rbenv is "self-documenting". I would be inclined to PRs that improve the real performance of the help command instead of buffer tricks for perceived performance.

Thanks for your thoughts @jasonkarns. I agree, it would be better to put effort in speeding up how the documentation is generated (if possible, there's a lot of string manipulation going on). Typically (from what I've seen) in cli tools the help output isn't generated and simply printed, so imo there is already performance overhead of generating every time rbenv is run—but that's the design choice with has benefit of the help pages being self-documenting and modular. Personally I'd generate it once and and have it baked in—a small cost to save end user's CPU cycles + IO.
I think the question here is whether it ought to be printed early or not? Say an error occurs in one of the summary files, it would print partly to stdout then fail, so it wouldn't be an atomic operation.


Network name is not unique across the cluster

The current Docker UI has the user refer to networks by name.  In order for that to work correctly, the name needs to be unique across the cluster.  Currently, libnetwork doesn't enforce this.
A quick example to show this is a problem: create two Docker containers on different hosts
On the first host
docker run --publish-service serviceA.net1.overlay ...

On the second host
docker run --publish-service serviceB.net1.overlay ...

The desired effect is for these services to be on the same network.  However, if the commands are executed simultaneously, or in rapid succession, each Docker Engine will think it should create net1 with a new UUID.  So there will be two net1 networks with one endpoint each, rather than what was desired.
Some ideas for fixing:
If, as @mrjana has said, we want network names and IDs to have different lifetimes, then libnetwork should store the names in the consistent data store (with the name itself as part of the key, e.g. /docker/libnetwork/netname/net1).  The name would be a "pointer" object that points to the UUID.  In the above example, both Docker Engines would attempt to create the name net1, but only one would succeed.  The unsuccessful one would then read back the name key to find out which network it currently points to and then attach the container to that network.
Another possibility would be to simply use the name as the unique ID for the network.  Simpler to implement, but it ties the lifetime together.
/cc @lxpollitt @tomdee @squaremo

The name would be a "pointer" object that points to the UUID.

That would work for preventing races to create the network name; but, is it possible to atomically rename a network in this scheme? (I don't know the capabilities of libkv and its underlying stores well enough to know)

@squaremo One approach might be to map rename to a create followed by a delete. Prior to the delete both old and new name would map to the same UUID.  (And you can build on that with things like generation numbers etc if you want to get more advanced and know which name to delete should you crash mid-way through the rename operation.)

I think it's important to square away the UI before deciding how to implement renames.  In particular, can a network have more than one name at any given time?
If yes, then I think renames are trivial in this model, as @lxpollitt suggested.
If each network can have only one name at a time, then the we can use a back "pointer" on the network object to ensure atomic renames.

@mrjana  @mavenugo @aboch I think this issue is important for a first stable multi-host release of libnetwork. Could it get triaged and assigned to a milestone?

Is this still a problem, given that we store the network name and id in a central kv store ?

I think this is still a problem.  Networks are keyed by ID in the data store, so the race condition described in the issue still exists.

@bpradipt @spikecurtis It is not a problem anymore because before docker 1.9 release we have made names to be non-unique references/aliases to network which is uniquely identified using it's id only. In fact the network api allows you to create as many networks as you like with the same name. If you need unique names the user has to make sure of it external to docker either manually or using an external orchestrator.
Now the api has a CheckDuplicate flag which will try to check for already existing networks with the same name in a best effort manner. But it is exactly that, best effort.
With this knowledge I am going to close this issue since it's not a problem anymore. Feel free to continue the discussion here.

I know that Docker advocates strongly for the developer UX being of primary importance.  Can you help me understand how this fits with that philosophy?  I'm not saying it doesn't, but it would be very helpful to those of us outside the tent to better understand the thinking behind this.


Jukebox preventing allay duplication

This mod makes it so the allays wont duplicate when playing music and giving them an amethyst shard.

for 1.21 btw

Chiming in to add that I'm also having this problem using Fabric for 1.21.1.


Add support for Neware cyclers

We should extend our handling of echem data to include neware, probably via https://github.com/FTHuld/neware_reader

Looks like https://github.com/Solid-Energy-Systems/NewareNDA/ might be more suitable as it supports the new ndax format.

(and again, this will be done via navani)


Investigate how Framer extracts type info

Framer does some pretty nifty stuff to keep types sync'd up with docs. It would be great if tsdx could leverage this.
Code of Interest: https://github.com/framer/api-docs/tree/master/api
Site: https://www.framer.com/api (it uses Framer's monobase SSG)

not sure i see it. was the investigation done? nothing there?


Edge has very slow(odd) loading speed compare to chrome

Many times it will legged, and takes nearly 10 second to load a website. But when I minimize it and suddenly open it, it works as usual. Also, I cannot use control+c to copy, can only use right click, or it will legged like above.
using a Windows11 operating system, intel i5-1300k, RTX3060Ti, 32gb memory.

btw, chrome don't have those problems, so I'm pretty sure it's a software problem.

What version of Edge is installed?
What channel of Edge is installed?
How much RAM does Task Manager report Edge is using?

Version 117.0.2045.55 (Official build) (64-bit) look like stable version
stable
it use approx 1gb memory

I just find out this problem is caused by Microsoft Remote Desktop.
Can be solved by restart.


If migration file is too big supabase start fails, same file works with supabase db reset

Bug report
Describe the bug
Here's a video walking through the issue: https://share.descript.com/view/FeJdbUO7Rtp
Here's the written description:
We have been using supabase for >1 year, and we've been wanting to update our workflow to use the CLI. To get started I ran supabase db remote commit to get the current state of our DB. This produces a file about 12K lines long.
With this file, I ran supabase start, which runs and reports success. However when I connect to the database, the migration has not been applied. It was very odd, because if I ran the file directly in psql with \i supabase/migrations/..._remote_commit.sql, it worked just fine. After fiddling with it for a while, I ended up running supabase db reset and after I connect to the database the migration had been applied. I can consistently reproduce this:

supabase stop && supabase start, no migration run
Then supabase db reset, the migration had been run!

This seem nearly good enough, but after this whenever I would run supabase db diff ..., it would diff the whole database (and output file was very similar to supabase db remote commit). I believe this is because supabase diff tries to apply the migrations the same way that supabase start does, which is reporting success but silently failing. In which case the shadow DB is empty so the diff is huge.
I decided to try to break apart the large file into several smaller ones, as I saw another issue where the cli couldn't handle large files. This worked! I broke the 12K file into 4 files of about 3K lines each. Each file has ~1050 sql statements. With these 4 files, I could run supabase start and supabase diff and it all works as expected!
I can share the files in question with someone from the supabase team
To Reproduce
I tried to reproduce by creating arbitrarily large migration files with lots of ALTER statements but I was unable to reproduce.
Unfortunately, I can't share the remote_commit file publicly, however I can share it with someone from the supabase team.
Expected behavior
The migration generated by supabase db remote commit should be applied to the DB with supabase start and supabase db diff
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: macOS
Version of CLI: 1.6.0

Additional context
Add any other context about the problem here.

Thanks for the detailed bug report! I suspect the issue faced by supabase start is due to max size limit for docker exec arg. We faced similar issues in the past with seed.sql https://github.com/supabase/cli/pull/295.
Since db reset applies migrations via pgx, it doesn't face the same issue. I will work on a fix for supabase start soon.


python-memcached FLAG_TEXT == pylibmc FLAG_BOOL

In https://github.com/linsomniac/python-memcached/commit/e1f72daabc011b83a8debb86e9e2b7ff6307a41c, python-memcached has assigned 1 << 4 to _FLAG_TEXT, which is used for representing unicode objects.
However, pylibmc uses the same value for FLAG_BOOL. This results in the following oddity:
Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34)
Type "copyright", "credits" or "license" for more information.

IPython 5.5.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import pylibmc

In [2]: import memcache

In [3]: servers = ['localhost:11211']

In [4]: mc = memcache.Client(servers)

In [5]: plc = pylibmc.Client(servers)

In [6]: mc.set('asdf', u'asdf')
Out[6]: True

In [7]: plc.get('asdf')
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-7-9372f452b2ee> in <module>()
----> 1 plc.get('asdf')

ValueError: invalid literal for long() with base 10: 'asdf'

In [8]: plc.set('asdf', True)
Out[8]: True

In [9]: mc.get('asdf')
Out[9]: u'1'

In [10]: plc.set('asdf', False)
Out[10]: True

In [11]: mc.get('asdf')
Out[11]: u'0'

Sigh. How typical. We've used this flag literally for years.

I think the best approach here is to implement the python-memcached text stuff, and remove the bool flag. We could have a special case for "is it length 1 and either exactly 0 or 1" to provide backwards compatibility. Ugly, but I don't see an easy way forward.

Also... The way pylibmc stores bools is as a one-byte value, and certainly not ASCII encoded. This must mean that the actual value in memcached is 0x00 or 0x01, but python-memcached converts it to u'0' and u'1'?

From past experiences, adding new bitflags downstream should be done from the other side, e.g. 1 << 15 or something (not sure how wide the flag field is). I recall ancient RHEL builds having a similar issue for the open(2) syscall when a very old RHEL kernel was used against a newer Ubuntu userland.

Also... The way pylibmc stores bools is as a one-byte value, and certainly not ASCII encoded. This must mean that the actual value in memcached is 0x00 or 0x01, but python-memcached converts it to u'0' and u'1'?

Yes

Then the workaround would not be too bad -- unlikely that somebody would store just 0x00 or 0x01 as a unicode text.

Actually it turns out that pylibmc stores it as ascii 0 and 1, sorry.

I guess that’s not too unexpected, it’s the same for other types of numbers.

On 9 Nov 2018, at 12:59, Chow Loong Jin<EMAIL_ADDRESS>wrote:
Actually it turns out that pylibmc stores it as ascii 0 and 1, sorry.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/lericson/pylibmc/issues/242#issuecomment-437339490, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC3NdemcYfyiltiKg8hYmaMAQuD2auXks5utW45gaJpZM4YWcWa.

https://github.com/lericson/pylibmc/blob/master/src/_pylibmcmodule.c#L1255

This been fixed.


OpenUTAU won't launch on NixOS

Acknowledgement

[X] I have read Getting-Started and FAQ

🐛 Describe the bug
OpenUTAU won't launch on NixOS. I suspect that this has to do with missing and incorrect RPATH of dynamic libraries:
$ ldd OpenUtau
	linux-vdso.so.1 (0x00007f89f94b3000)
	libpthread.so.0 => /nix/store/46m4xx889wlhsdj72j38fnlyyvvvvbyb-glibc-2.37-8/lib/libpthread.so.0 (0x00007f89f9484000)
	libdl.so.2 => /nix/store/46m4xx889wlhsdj72j38fnlyyvvvvbyb-glibc-2.37-8/lib/libdl.so.2 (0x00007f89f947f000)
	libstdc++.so.6 => not found
	libm.so.6 => /nix/store/46m4xx889wlhsdj72j38fnlyyvvvvbyb-glibc-2.37-8/lib/libm.so.6 (0x00007f89f939f000)
	libgcc_s.so.1 => /nix/store/jd99cyc0251p0i5y69w8mqjcai8mcq7h-xgcc-12.2.0-libgcc/lib/libgcc_s.so.1 (0x00007f89f937e000)
	libc.so.6 => /nix/store/46m4xx889wlhsdj72j38fnlyyvvvvbyb-glibc-2.37-8/lib/libc.so.6 (0x00007f89f9196000)
	/lib64/ld-linux-x86-64.so.2 => /nix/store/46m4xx889wlhsdj72j38fnlyyvvvvbyb-glibc-2.37-8/lib64/ld-linux-x86-64.so.2 (0x00007f89f94b5000)

All the related executable files have to be either ELF-patched, or a package file has to be added to nixpkg (a rather convenient solution) in order to make them work. Unfortunately, I am just a newbie to NixOS, so it is beyond my ability to create a build or a shell/develop file.
Explains how to reproduce the bug

cd  to where OpenUtau was extracted
Execute OpenUtau using ./OpenUtau
Here's the output:

$ ./OpenUtau
bash: ./OpenUtau: cannot execute: required file not found

OS & Version
Linux lenovo-s540 6.1.38 #1-NixOS SMP PREEMPT_DYNAMIC Wed Jul  5 17:27:38 UTC 2023 x86_64 GNU/Linux
Logs
Logs are non-existent in my case, as the app fails to start in the first place.

OpenUtau has been added to Nixpkgs successfully in NixOS/nixpkgs#236003 . If there are any unsupported distros out there, or anyone out there using NixOS, they may use Nixpkgs.
@stakira , can you also address this issue regarding the license? Resamplers haven't been included in the package, it seems.

@stakira perhaps you might have missed my previous ping, but could you confirm the license of the worldline sampler?

Closing this issue, as the above comment is unrelated to the topic.


⚠ Jenkins Plugins Artifactory has degraded performance

In bcb0376, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1498 ms

Resolved: Jenkins Plugins Artifactory performance has improved in fcb1586 after 12 minutes.


Error Install with Flask-JWT-Login

Hello,
i tried to install but i got:
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [6 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "C:\Users\ user .... \AppData\Local\Temp\pip-install-dagqibp8\flask-jwt-login_372ce447414e4e20ac0341d4898d6c5e\setup.py", line 12, in
long_description=open('README.md').read(),
FileNotFoundError: [Errno 2] No such file or directory: 'README.md'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

Hey XFG9
To fix this error just create a file named 'README.md' inside Termsteel Folder

ThxVon meinem/meiner Galaxy gesendet
-------- Ursprüngliche Nachricht --------Von: Afi @.> Datum: 08.09.22  14:32  (GMT+01:00) An: afi-dev/Termsteel @.> Cc: XFG9 @.>, Author @.> Betreff: Re: [afi-dev/Termsteel] Error Install with Flask-JWT-Login (Issue #6)
Hey XFG9
To fix this error just create a file named 'README.md' inside Termsteel Folder
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


more simple example

can you provide a very simple example.
I think a clean raspberry project with just sending a message and subscribe to a topic would be great.
I would help with this but.. I don't get it to work because there are so many variables and structs.. I don't really see whats going on there and I can't get it to work in an other project.
Thank you

Hello dkeipp,
yes your are right, it is a little complex and maybe confusing. I'll make a smal test projekt to test.mosquitto.org.
but you must make sure that the dns clienent geht's your dns Server ip, for this take a look to commontypsandfunctions
BR
Stefam

Thank you for the hint :-)
now I can send messages...
So maybe I can make a small example during the weekend..
for those who are trying to get this to work, here is the comment from GET_DNS_IP:
(don't forget to restart Runtime after that change)
`
for linux
change
sudo nano /etc/CODESYSControl.cfg
or from runtime version <IP_ADDRESS>
sudo nano /etc/CODESYSControl_User.cfg
[SysProcess]
Command.0=shutdown
to
[SysProcess]
Command.0=shutdown
Command.1=cat
for windows, needs powershell
"C:\ProgramData\CODESYS\CODESYSControlWinV3???\CODESYSControl.cfg"
[SysProcess]
BasePriority=Realtime
Command=AllowAll
`

Hi dkeipp,
i am happy to heat that you can send Messages now.
And if you make this example i more happy....
i think it would be the best if you make it as an seperate projekt, not in the library. do you think to?
let me know if subscribe is working too.
BR Stefan

Hello folks,
the IP resolve functionality of your library seems very special to me. I added an example, which helps you to get the IP-Address resolved directly in IEC Code.
I think it makes sense to add that function to your project :)
https://github.com/KevinRohn/cds-common-examples

Hello Kevin,
Looks gootd, i will have a try…
BR

Hi Kevin,
i implemnted it, just try it...
resolved a error in IP_CONTROL to.
BR Stefan

Hey Stefan,
I will check it later. Is there any chance to contact you via Mail?
You can contact me by visiting my private website: rohn(dot)io

Hello to all,
done an out of the box test projekt for the Raspberry, please test it...
BR Stefan

Everything fine?
I am going to close this issue.
BR Stefan

So here I am again,
now with new and tested Example Projects. Please have a look and tell your opinion.
BR Stefan

Ok,
I think now it is fine.
BR Stefan


user_identity needs to be optional var input on azurerm_key_vault_access_policy

Currently the user_identity is an input but it is not used as a var if found in the resource block below. As a result, the user provided user_identity ID does not have a policy applied to it. Instead, the keyvault policy is applied to the azurerm_user_assigned_identity. Which...this block also needs to have a "count" condition if var.user_identity exists.
fix this...by adding count "if" logic var.user_identity exists
resource "azurerm_user_assigned_identity" "user_identity" {
  name                = format("%s-ident", local.instance_prefix)
  resource_group_name = data.azurerm_resource_group.bigiprg.name
  location            = data.azurerm_resource_group.bigiprg.location
  tags = merge(local.tags, {
    Name = format("%s-ident", local.instance_prefix)
    }
  )
}

fix this...by allowing object_id to be the var.user_identity if provided or the azurerm created resourece
resource "azurerm_key_vault_access_policy" "example" {
  count        = var.az_keyvault_authentication ? 1 : 0
  key_vault_id = data.azurerm_key_vault.keyvault[count.index].id
  tenant_id    = data.azurerm_client_config.current.tenant_id
  object_id    = azurerm_user_assigned_identity.user_identity.principal_id

Hi @JeffGiroux , there is condition check based on user_identity : https://github.com/F5Networks/terraform-azure-bigip-module/blob/main/main.tf#L498-L500

Is there a timeframe for next release and fix for this?

@RavinderReddyF5 the latest release broke the template: https://github.com/F5Networks/terraform-azure-bigip-module/commit/89e050f0810e1e337631aa6c4683daf11a2dba58#r95818004

please reopen new issue if any issue seen


[INLONG-8272][SDK] Fix DataProxy's HTTP SDK verification response code error

Fixes #8272

@xuesongxs please use English to add the commit msg. thanks.


Provide a callback whenever retry is triggered

Confirm this is a feature request for the Python library and not the underlying OpenAI API.

[X] This is a feature request for the Python library

Describe the feature or improvement you're requesting
Is it possible to provide a callback whenever a retry is triggered internally, so that we can know when and how the requests failed?
Additional context
We want to give our users some insights if some OpenAI requests fail with rate limit error

Thanks for the suggestion – I don't think we have a great way to do this right now, but it seems like a reasonable idea. I don't expect to get to it soon, but will keep the issue open.

Can we just pass in a callback like this
def error_callback(exception: Exception):
    # custom logic

completion = await openai_client.chat.completions.create(
    model=model, ..., error_callback=error_callback
)

And here do
except Exception as err:
    error_callback(err)

I doubt that's how we'd design it. You could use httpx event_hooks: https://www.python-httpx.org/advanced/event-hooks/

I doubt that's how we'd design it. You could use httpx event_hooks: https://www.python-httpx.org/advanced/event-hooks/

Ah I didn't know we can use custom httpx Client. This works for us, thanks!

Great! It'd be appreciated if you could share the (rough) code snippet you and up using, so others can benefit

Great! It'd be appreciated if you could share the (rough) code snippet you and up using, so others can benefit

Sure, this block works for me
from openai import OpenAI, timeout
from openai._base_client import SyncHttpxClientWrapper

def _print_response_status_code(response):
    print("Response status code", response.status_code)

http_client = SyncHttpxClientWrapper(
  base_url="https://api.openai.com/v1",
  timeout=timeout,
  follow_redirects=True,
  event_hooks={"response": [_print_response_status_code]},
)
client = OpenAI(http_client=http_client)

response = client.chat.completions.create(
  model="gpt-3.5-turbo",
  messages=[
    {"role": "system", "content": "You are a helpful assistant."},
    {"role": "user", "content": "Who won the world series in 2020?"},
    {"role": "assistant", "content": "The Los Angeles Dodgers won the World Series in 2020."},
    {"role": "user", "content": "Where was it played?"}
  ]
)

It's still a bit annoying to hack to import SyncHttpxClientWrapper, and manually set all the defaults(like base_url, timeout, etc) for its constructor tho. If it's possible to expose SyncHttpxClientWrapper with all default arguments, it would make life much easier

@rattrayalex : +1 on this request... Would you be open to a contribution to pass along event_hooks from the OpenAI client initialization to the constructor for the client?
We're really to avoid having to redefine the http_client and leverage what OpenAI provides out of the box.

It's still a bit annoying to hack to import SyncHttpxClientWrapper, and manually set all the defaults(like base_url, timeout, follow_redirects, etc) for its constructor tho. If it's possible to expose SyncHttpxClientWrapper with all default arguments, it would make life much easier

That's a good point – it'd be nice for us to expose the default args at least, if not a class which has those defaults. I don't think you should really need to import SyncHttpxClientWrapper instead of just httpx.Client though.

Would you be open to a contribution to pass along event_hooks from the OpenAI client initialization to the constructor for the client?

I don't think we'd want it to be event_hooks but something closer to on_request=. We have to gavel on the design there internally first, so I don't think a contribution at this time would be a wise investment. Thank you though!
cc @RobertCraigie on the above – we should get this slated.

Yes you definitely should not have to use SyncHttpxClientWrapper, thats an internal only thing that we use for reference counting.
It might be a good idea to provide something like this though, which would use our default options, thoughts?
import openai

client = openai.OpenAI(
  http_client=openai.DefaultHttpxClient(...),
)

@rattrayalex @RobertCraigie DefaultHttpxClient looks good to me! Can you help expose that for us? Really appreciate it!

I really like the idea of having a DefaultHttpxClient that users can use without needing to redo setting the default properties, with other configurable options that are currently available on httpx's client.
I'm having a bit of a hard time connecting the dots to go from on_request handlers to something akin to event_hooks especially because what I'm trying to get at is understanding not just when a request occurred, but when a 4xx response / retry occurred. So, that necessitates skipping maybe the first request and then catching the other ones.
I'm probably just missing some connection which is likely obvious to the maintainers here, so that's totally fine, just saying out loud that it'd be nice to get some docs on the usage here when this gets worked on.
Appreciate the quick feedback, iterations on design and openness to implementation here a bunch, OpenAI team!

You're correct it isn't trivial, which is why we will need to take our time designing it – and on_request and similar niceities may not land right away.
However, DefaultHttpxClient is more straightforward and should be able to happen sooner.
We plan to do both!

Great to hear that there's potential for both of those approaches to be supported natively. Thanks for adding this to the roadmap and proactively engaging here!

@rattrayalex @RobertCraigie Thanks! Is there any ETA for the straightforward DefaultHttpxClient? This is blocking us on an important project, so I really appreciate if it can be fixed asap.

OOC how is this blocking you? That class would just be changing the defaults and you can change the defaults yourself as well, e.g. this will be functionally exactly the same as the solution we provide
import openai
import httpx

openai = openai.OpenAI(
  http_client=httpx.Client(
    timeout=openai.DEFAULT_TIMEOUT,
    follow_redirects=True,
    limits=httpx.Limits(max_connections=100, max_keepalive_connections=20), # also currently the httpx default
  )
)

@RobertCraigie Yeah this is not a blocker. We can move forward with this, but please keep us posted if the formal solution is out. Thanks!

Was just digging through the client code and see there's a new DefaultAsyncHttpxClient (introduced in https://github.com/openai/openai-python/pull/1302), which would allow us to do exactly what we need.
I think this issue can be safely closed. Thanks a bunch!

Thank you!


Rm local session frame size checks

This pull requests removes maximum messages size restrictions of the zeromq transports. This is done in accordance to the discussion in #25 .
Removes frame size checks from the zeromq transports and the PlainTranscoder. Adds a unit test to ensure large messages are now routable.
Updates the docstrings of the SendFrame trait in concert with the changes.

Released to crates.io as 0.8.0-rc.3


Can't run unit 3.1 test

When I try to run npm test in unit 3.1, it fails with Error: cannot resolve path (or pattern) '—recursive'. Using --recursive also fails (see below). npm is installing mocha 2.3.3, but I get a similar error if I tweak package.json to the install mocha 2.2.5.
thad@localhost:~/archives/web-videos/reactjs-src/Section 3/Video 3.1
615 $ npm install
...

thad@localhost:~/archives/web-videos/reactjs-src/Section 3/Video 3.1
616 $ npm run build

><EMAIL_ADDRESS>build /Users/thad/archives/web-videos/reactjs-src/Section 3/Video 3.1
> browserify src/main.js -t babelify --outfile public/bundle.js && node-sass --output-style compressed styles/main.scss public/main.css

Rendering Complete, saving .css file...
Wrote CSS to /Users/thad/archives/web-videos/reactjs-src/Section 3/Video 3.1/public/main.css

thad@localhost:~/archives/web-videos/reactjs-src/Section 3/Video 3.1
617 $ npm run test

><EMAIL_ADDRESS>test /Users/thad/archives/web-videos/reactjs-src/Section 3/Video 3.1
> ./node_modules/mocha/bin/mocha --compilers js:babel/register --reporter dot -—recursive

  error: unknown option `--'

(A single dash also shows a stack trace.)
The npm-debug.log is
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/Users/thad/.npm-packages/bin/npm', 'run', 'test' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'pretest', 'test', 'posttest' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for pretest, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /Users/thad/.npm-packages/lib/node_modules/npm/bin/node-gyp-bin:/Users/thad/archives/web-videos/reactjs-src/Section 3/Video 3.1/node_modules/.bin:/opt/local/bin:/opt/local/sbin:/Users/thad/.npm-packages/bin:/Users/thad/bin:/Library/Frameworks/Python.framework/Versions/3.4/bin:/opt/groovy/bin:/opt/gradle/bin:/opt/asf/maven/bin:/opt/asf/ant/bin:/Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/bin:/Users/optix/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/git/bin:/Library/Frameworks/Firebird.framework/Resources/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/thad/archives/web-videos/reactjs-src/Section 3/Video 3.1
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c',
11 silly lifecycle   './node_modules/mocha/bin/mocha --compilers js:babel/register --reporter dot -—recursive' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec test script
14 verbose stack Error<EMAIL_ADDRESS>test: `./node_modules/mocha/bin/mocha --compilers js:babel/register --reporter dot -—recursive`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/Users/thad/.npm-packages/lib/node_modules/npm/lib/utils/lifecycle.js:233:16)
14 verbose stack     at EventEmitter.emit (events.js:110:17)
14 verbose stack     at ChildProcess.<anonymous> (/Users/thad/.npm-packages/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at ChildProcess.emit (events.js:110:17)
14 verbose stack     at maybeClose (child_process.js:1015:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /Users/thad/archives/web-videos/reactjs-src/Section 3/Video 3.1
17 error Darwin 14.5.0
18 error argv "node" "/Users/thad/.npm-packages/bin/npm" "run" "test"
19 error node v0.12.7
20 error npm  v3.3.5
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>test: `./node_modules/mocha/bin/mocha --compilers js:babel/register --reporter dot -—recursive`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>test script './node_modules/mocha/bin/mocha --compilers js:babel/register --reporter dot -—recursive'.
23 error This is most likely a problem with the mastering-react package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     ./node_modules/mocha/bin/mocha --compilers js:babel/register --reporter dot -—recursive
23 error You can get their info via:
23 error     npm owner ls mastering-react
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Argh! In changing the single dash to double-dash, Atom on the Mac was inserting a em-dash.
Now the only issue is the time assertion, which may be a newer setting in moment (2.10.6 installed vs 2.10.3).
      -  "Mar 9, 1:14pm"
      +  "Mar 9, 6:14pm"

Oh thats unfortunate.
I believe the time difference is a timezone issue - Surely a brittle test that could have been done better.

Aha! I took a look at the original file. It's not a hyphen (0x2D) but E28094 before the word recursive (offset 0xE4). I get that from from the Packt source download or from a copy-paste of package.json from here. Adding a second hyphen makes it look like an em-dash.
Yes, I realized what the timezone issue is. orderedAt: moment("2015-03-09T17:14:00.000Z").utcOffset(1) is one way to "fix" it.
Thanks for the video lesson. It's well done. I'm completely new to ReactJS, and I'm finding the lessons interesting.

Good to hear! let me know if there are other issues - I'll do my best to help :)


[WIP] Don't copy data during literal validation and object creation

These changes are needed for the JS binding as it requires support for object creation using literals when using the dynamic interface.
This adds a separate validation step when creating objects from literals and no longer copies data into standalone objects when creating/updating objects. We have talked about this for quite some time and this should hopefully address a number of outstanding issues.
As a side effect we should be able to support using literals when using object subscripting but this is not yet tested.
Things that still need to be fixed:

when updating objects we allow missing values during validation, but don't check that all values are present in the case a new object is created
clean up/refactor old code path for initialization of standalone objects
more testing

IMO it'd be preferable to keep using an enum rather than a bool, even though you've eliminated most of the members. RLMCreationOptionsUpdateOrCreate is much more descriptive at a call site than true.

I agree having RLMCreationOptions is better than a bool. My main issue with this was that the options we had were confusing and were set and mutated in odd ways - removing them made cleaning up the code a lot easier. I'm happy to add this back but we will only support two options RLMCreationOptionsUpdateOrCreate and RLMCreationOptionsPromoteStandalone.

I personally don't like referring to literals, since all we care about those objects is that they're KVC-compliant

Not quite true. We also support array literals.

Literals doesn't seem like the appropriate term. At the point we're dealing with the objects its irrelevant whether they were literals or created in some other fashion.

Since Jenkins doesn't seem to have run on this, I'm also concerned that this might break our recent improvements with object re-use.

All the tests pass. I'm not sure what the goal of the object re-use pr was but we should be moving away from creating standalone objects internally, except in the case where we are actually initializing standalone objects. This pr accomplishes that in all cases where we are creating persisted objects.
Feel free to suggest alternate terminology. I can't think of anything better offhand.
My main goal here is unblock the JS work. The current functionality in this pr does this and also fixes a few other bugs with the current code. Don't think I am going to spend much more time on this so it would be helpful to figure out what else needs to be done to get this merged.

"Literal" is dumb and wrong but in lieu of a similarly concise term I'd prefer to keep using it over "KVC compliant object or array with values in the correct order".

Please add a CHANGELOG entry for the update issue you've fixed.

anything else?

Other than the remaining rebase error, you get my :+1:

Seems good :+1:


[Query] Hiding rows with 'undefined' values

is there a way i can define columns that if the value there is undefined the row would be hidden?

i also have a similar query. use multiple options for hide field.  My use case is to hide rows with 0 and "undefined" cell values.

Yes I can confirm. Same issue. I can't hide values, which are the number 0.
My workaround: Add 1 to each value (at DB query) and hide values below "threshold + 1".

not everywhere you can do +0.1
Empty values are not overridden by "Null Value"

SOLUTION IS HIDDEN :)
Yes THERE ARE "NEWS" -> [PavelvKalinin] gave the solution but you did not spend enough time reading
In query just add a dummy value like in example bellow: +0.001
Whatever number that does not influence the numbers significantly
Then null become +0.001 so use Hide series /Hide if value is below: 1 for example
sort_desc(
sum by (uri,status,outcome)(
(
rate (
http_server_requests_seconds_count {app=~"web-gateway", outcome="SUCCESS", uri!="/health" }
[10m]
)*60+0.001
)
)
)


[build-preset] Add swift-driver to CI builder presets

Build and test the new integrated swift driver against the just-built toolchain.
The new, integrated swift-driver is seeing a lot of development that goes hand-in-hand with the frontend so it would be extremely helpful to ensure we do not accidentally break swift-driver with frontend changes.

@swift-ci please test

Looks reasonable to me.

@swift-ci build toolchain

Couple of questions:

Is this going to add swift-driver to the package toolchains?
Not strictly related to this patch, but doesn't swiftpm already depend on swift-driver?  Why does it not need to be explicitly built for swiftpm?

Build failed
Swift Test Linux Platform
Git Sha - 9406d4613865801b6394b552c94d79417bc90d29

Couple of questions:

Is this going to add swift-driver to the package toolchains?
Not strictly related to this patch, but doesn't swiftpm already depend on swift-driver?  Why does it not need to be explicitly built for swiftpm?

Yes, my understanding is that it is going to add swift-driver to the package toolchains, but it will not make it a default. It will simply be an additional available executable called swift-driver.
SwiftPM does have swift-driver as a dependency and when we build SwiftPM, it will pull (in a git sense) and build swift-driver on its own, regardless of whether the toolchain has it or not. This change does so explicitly as a part of the toolchain and also adds testing of the swift-driver against the just-build toolchain, which the SwiftPM build does not do for swift-driver. Separately from this change, we can then change the SwiftPM build to use the toolchain's local swift-driver instead of fetching it again, on its own, it already has an environment variable that allows it to do so.


 Why is it so and where do I get "cd: no such file or directory:"
—
Reply to this email directly or view it on GitHub.￼

@pottiep what does that mean?

That appears to be some sort of spam?

Whoo the user got deleted altogether : ghost. But still waiting for answer.

@shahankit, python uses /bin/sh as a shell for subprocess.Popen, you should match for output from /bin/sh:
➜  /bin/sh -c "cd somewhere"
/bin/sh: 1: cd: can't cd to somewhere

thanks @nvbn, that solved the issue.
This is my script for cd to mkdir
"""
Automatically creates a new directory when no such file
directory is shown by cd

Example:
> cd newTemp
cd: no such file or directory: newTemp
def match(command, settings):
return ("cd: can't cd to " in command.stderr)
def get_new_command(command, settings):
return 'mkdir '+command.stderr.rsplit(' ', 1)[1]
"""

Don't you want to cd into the created directory afterwards?
I would also use mkdir -p to create any missing directories if you try to do something like this cd foo/bar/baz.

@nwinkler thanks nice suggestion. I'll do that.

FYI, the stderr is the same when a user tries to enter in a file :
$ cd /foo/bar.txt
sh: 1: cd: can't cd to /foo/bar.txt

Or in a denied directory :
$ cd /root/
sh: 1: cd: can't cd to /root/

So be careful in your match() function to avoid these cases.

@ncrocfer Then what should be used in matcher to avoid files and permission issues?


Fixes #131

Add a pre-delete lifecycle listener that verifies a subscription has been closed at least 6 weeks
before it can be deleted.

Your fix looks ok to me for subscriptions. Do you plan to handle the FLW deletion case (also described in #131) with a separate PR?

No, I had forgotten about the other half of the issue. :)  I'll add that in
and then ask for review again.
On Tue, May 19, 2015 at 1:23 PM, Lauren Lavoie<EMAIL_ADDRESS>wrote:

Your fix looks ok to me for subscriptions. Do you plan to handle the FLW
deletion case (also described in #131
https://github.com/motech-implementations/mim/issues/131) with a
separate PR?
—
Reply to this email directly or view it on GitHub
https://github.com/motech-implementations/mim/pull/263#issuecomment-103658615
.

@llavoie @frankhuster @koshalt Come 'n get it!

Onit

lgtm


Add config for branch limits

I imagine that some folks will want to only enable todo on their master branch. Or, on any branch that is not their master branch. Or on a specific branch. Who knows? Basically, there should be a config to customize which branches todo runs on.
This could use globs, an array of strings, defaultBranchOnly true or false. The possibilities are endless!

Given the change in how PRs work, This is less relevant so I'm going to close.


+refs/pull//merge: not update after rebase and force push

We have a problem with force-push.
The essence can be understood from the correspondence with github support.

Greetings!
Github have a bug when we doing rebase and force push. With 90% of cases the special branch +refs/pull/<ID>/merge: are not updated or update after some long time.
The live example of that situation we have prepared at https://github.com/abak-press/apress-demands/pull/256
Right now it is reproduced in our CI and locally.
Latest commit in a PR have ref de9ed321028b3338ec19689274ee596234c08d24
But doing this locally right now (and about during 30 minutes):
$ git init
Initialized empty Git repository in /home/merkushin/code/tmp/demands-remove/.git/

$ git fetch --no-tags origin +refs/pull/256/merge:

$ git checkout -qf FETCH_HEAD

$ git log -2
commit 16aaa6d3f72a64ceb45d6dc96bf467cdc85bbf0a (HEAD)
Merge: d8993a90 81018f75
Date: Tue May 22 11:38:28 2018 +0000

Merge 81018f751a953fc3458c1c67327a7c0f63a94d86 into d8993a90412871b3c3ce3d3568c99b15ddbb8721

commit 81018f751a953fc3458c1c67327a7c0f63a94d86
Date: Tue May 22 14:42:43 2018 +0500

chore: Check head commit in drone

This bug is very very very get frustrating us.
We are currently is forced to use this crutch :(
if ! git merge-base --is-ancestor ${DRONE_COMMIT} HEAD; then
  echo "The commit ${DRONE_COMMIT} has not been found in HEAD."
  echo "Try to restart a build or open a new pull-request."
  exit 1
fi

Hey Michail!
We currently wouldn't recommend using the merge ref directly as it can sometimes be out of date.
As an alternative, our API can be used to trigger the update and retrieve the merge ref:
https://developer.github.com/v3/git/#checking-mergeability-of-pull-requests
Hope this helps and please let me know if you need anything else!
Cheers
Stacey

This may help: https://discourse.drone.io/t/planned-change-to-git-clone-logic/1165

closing this in favor of the discourse discussion, since this is a plugin issue and not a drone core issue.


two questions

Hello!
thank you for this.
is there any chance getting a gui without needing to install python like koboldcpp in the future for its portability?
also, can we use this with other models like wizardlm too?
kind regards

Maybe in the future. Unfortunately, GUI is using python right now, but the CLI version works without any dependencies at least for now.
wizardlm is a different model than vicuna. minigpt4 weights was trained with vicuna, so it will not work wizardlm. If someone has trained minigpt4 with wizardlm and has provided those weights, then I can add those.

thank you for repley, can u please update and show us how to use cli version in the description? is it like stable diffusion cpp to use with cmd? what are the commands in cmd?
kind regards


tablesorter.com is down

http://tablesorter.com/__jquery.tablesorter.min.js
Doesn't work any more, so the generated results aren't sortable.  Speaking of, I was quite surprised when I first found out that the sorting actually required an external domain because I had no internet at the time.

Already fixed in f67264cee755fb421421cb69b3d4f409a1d27a3e

I'm working on a fix, I think I'll just remove external JS and rewrite the sorting feature using vanilla JS and then release a new version.


[csolution/cbuildgen] Improve the toolchain registration

Today the user of the tools is required to register a toolchain by creating a copy of a toolchain version specific cmake file located in the $CMSIS_COMPILER_ROOT (default ../etc).
AC6.<version>.cmake
GCC.<version>.cmake
IAR.<version.cmake
Inside the cmake two variables can be edited:
TOOLCHAIN_ROOT -> pointing to the bin directory of the toolchain
TOOLCHAIN_VERSION -> specifying the major,minor and patch version of the toolchain
Instead of specifying the TOOLCHAIN_ROOT an environment variable e.g. GCC_TOOLCHAIN_<version> can be specified.
This system requires to maintain one cmake file per registered toolchain.
Assuming that many toolchain versions are widely compatible the proposal is to use a single cmake file for multiple toolchain versions. The version in the cmake filename no longer specifies a fixed version but the minimum toolchain version that is 'sufficiently' compatible. Once a breaking change is introduced by a toolchain version an additional cmake version will get added to the 'etc' directory and any toolchain version greater or equal to this version will use the newly added cmake file.
If no environment variable is set for a toolchain, then the heuristic search of CMake will be used to try and find a suitable toolchain in the system.
Note:
One anticipated use case is for toolchain versions being managed as vcpkg artifacts. As part of the activation the corresponding environment variable will be exported by vcpkg. This way csolution does not rely on the order in the PATH and does not need to inquire the version from the toolchain.

I like that approach as it is simple and easier to understand.
Would it be possible to write the *.cmake files in a way that they issue a warning if an unknown option is passed.

Sounds good to me in the way it improves running proposal limiting toolchains description updates.

CMSIS-Toolbox 1.5.0


How to add custom route ?

Not able to call custom route

I have registered auth route like shown in image but i am not able to view or call this route
it is giving 404 not found

please tell me how to do this ?

Hi @awais786327,
We are trying to shift questions to Stack Overflow to make questions and answers easier for others to discover. In the future, could you please post questions there with the tag node-fhir-server-core or javascript-fhir and we can answer them on Stack Overflow.
The reason you are getting a 404 is that FHIRServer.initialize(config) calls several functions, including setting up a catch all error handler. Any routes added after initialize will not ever be reached because of the way express adds routes.
What you can do, is not call initialize but call the functions it calls internally yourself, something like this:
const { Server } = require('@asymmetrik/node-fhir-server-core');

let server = new Server(config);

// Write your own custom middleware here for validating roles or using passport
server.app.use(function (req, res, next) {

});

// This is everything initialize calls except configurePassport
server.configureMiddleware()
	.configureSession()
	.configureHelmet()
	.setPublicDirectory()
	.setProfileRoutes()
	.setErrorRoutes();

server.listen(3000);

You can read more on that here: https://github.com/Asymmetrik/node-fhir-server-core/wiki/Access-Control#how-to-customize.


Issue: Access token - email based TOTP login

OAuth flow is broken with the new emai based TOTP login (TOTP is One Time Passcode, used to login without a password:
Email-based TOTP overview | Smartsheet Learning Center ).
When I'm using this login method, I'm not getting the Access token from Smartsheet API.
For now we can still use the login with email/password but they are planning to remove this feature, this year.
Does anybody found a workaround for this? Or does anybody have insights if Smartsheet API team is plannig to fix it?

Great question! I will ask around and see if I find anything. Hope others do the same!

Thank you, @timothodge. I look forward to your findings.
I have also opened a case with Smartsheet and have been awaiting a response for a few days.
Additionally, I have reached out to the Smartsheet community for assistance: Smartsheet Community Discussion.


Chore: bump openfermion version

Description
Newer verison of openfermion fixes warnings in its code
Please verify that you have completed the following steps

[ ] I have self-reviewed my code.
[ ] I have included test cases validating introduced feature/fix.
[ ] I have updated documentation.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (b531b3c) 95.90% compared to head (4a1f128) 95.90%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #52   +/-   ##
=======================================
  Coverage   95.90%   95.90%
=======================================
  Files           8        8
  Lines         342      342
=======================================
  Hits          328      328
  Misses         14       14

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@AthenaCaesura Id like to pair on that PR on monday if thats OK. I cant run tests locally as one of the dependencies do not provide wheels for ARM M1


[Proposal]: Add commit message docs in Readme for commitlint

Proposal
Instructions on writing good commit messages should be included in the documentation for husky commit msg to work.
Reference - https://www.freecodecamp.org/news/writing-good-commit-messages-a-practical-guide/

@avinashupadhya99
Seems like a good proposal 👍🏽
I read the article you linked which seems good, but, there is another committing convention which is more widely used, which is this one - Click Here


[🐞 Bug Fix] Fix Locale Selector Switching Back to Default Locale

Description
This PR fixes #1661.
The locale selector in the footer would always use the default site for url generation even if you were currently on a non-default site.
Types of Changes

[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

Remove explicit use of defaultSite in url generation.

How to Test-Drive This PR

See issue for steps to repro

Checklists

General

[ ] Changes are covered by test cases
[x] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

is this PR duplicate to #1662 ?

is this PR duplicate to #1662 ?

@alexvuong  Looks like it.. must have missed that. But since there isn't a change log addition in Sandra's PR it might jsut be easier to go with this so we don't have to wait for that change.

looks good.... i had already submitted the PR #1662 last Monday when i opened the issue, added change log today if that's what was blocking the merge?

looks good.... i had already submitted the PR #1662 last Monday when i opened the issue, added change log today if that's what was blocking the merge?

Nope.. I just didn't see your PR, by the time I did I had done my own and had it in the channel for review. Thanks for the submission


Fixed #30412 -- Fixed crash when adding check constraints with OR'ed condition on Oracle and SQLite.

Ticket: #30412

@cansarigol Test and release notes are required.

thanks @charettes.

buildbot, test on oracle.


Fix: handle NULL input in lead/lag window function

Which issue does this PR close?
Closes #12717
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?

Thanks @HuSen8891 I have some feeling that we should fix the out_data_type earlier so it will serve both LAG/LEAD

Thanks! handle NULL input in lag window function

Thanks @HuSen8891 and @comphead 🙌

Thank you @HuSen8891 and @comphead  and @jcsherin  for the review