Add ExceedBurden and CategorySpacer

Purpose

create ExceedBurden component that is used twice
create a .categorySpacer class for the AND component
modify indicator styling to work with background higlighting
add BE stubs for Burden booleans
remove Indicators header
add copy to intl

QA

note that the ExceedBurden Spacers are all hardcoded to YES for now as we wait for BE

Let's add a 1 px space between indicators to allow for a white line. Let's also bold the font.

Feedback

Make the Yes / No bold
See bugs in Side Panel Testing doc

@emma-nechamkin,
Some QA feedback led to boolean strangeness. Was able to spin up Jupyter (which is my new favorite tool) to investigate:

Any thoughts? Wondering if I'm doing something wrong (likely). Thanks!

@vim-usds these booleans are for "low income, low ed, and exceeds 90th percentile" -- we don't pipe the threshold booleans to you separately, I don't think.
I think for the new side panel, we might need to pass this through!
field_names.ENERGY_BURDEN_LOW_INCOME_LOW_HIGHER_ED_FIELD: "EBLI",


Persisted queries in relay format should be written in deterministic order

Product
Strawberry Shake
Is your feature request related to a problem?
When writing persisted queries in relay format, the queries are written in non-deterministic order. This leads to changes in the git repository even if the queries remain identical. To fix this, the queries should be written in a deterministic order to file.
The solution you'd like
I already have a proposal for a simple fix: https://github.com/DanielZuerrer/graphql-platform/commit/6c2fd69485553dc8af5e353887e070429b201bb4. I'd be happy to create a pull request if you think the change is sensible.

Sounds like a sensible change to me.
Personally, I'd probably just put the file in a .gitignore and generate the persisted operations during CI. That way you're certain they are up-to-date. Having them checked in doesn't really provide a benefit as they are generated on every build anyways and changes to the operations are already surfaced in code review through the .graphql files.

I agree that it would probably be the best to not have the persisted queries in version control at all. With our CI setup where solutions are built in docker and pipelines are not setup to extract files from docker images it would require some changing of the pipelines themselves. So I think there is still some value to have the queries be in deterministic order, even if it's probably not the best practice.


👍 Add private API (getbalancehistory)

Thanks for the PR!
It seems alright so I will merge this~

@allcontributors please add @shidetake for code

Released in 1.4.0


[coap] Add helper functions to encode coap block options

This small feature addition is two helper functions to encode the Block1 and Block2 uint options described in RFC7959. This should help the effort in #4213 and #4247.

@sjlongland - given that you've been driving a bunch of CoAP enhancements, can you review/comment on this PR?

Nothing really jumped out at me, it looks good.  There are a few small improvements that can be made, but even as-is, it looks great. :-)


Receive error on long-lived connections to SB

Hello.
I've stumbled into the following receive() error:
{
  "descriptor":{
    "buffer":[0,0,0,0,0,0,0,29],
    "offset":0
  },
  "condition":{
    "contents":"amqp:illegal-state"
  },
  "description":"operation: R:ATTACH, state: OpenReceived"
}

This happens on connections to SB's queues that are up for days (weeks, sometimes) and handle large amount of messages. Unfortunately, I still haven't found a way to reproduce the issue, no matter how many thousands of messages I send. Even more unfortunately, this only happens in a remote environment that makes it quite hard to debug.
I am using v1.0.3 and a custom policy that throttles links according to the state of the system. Any idea of what might be causing this?
Cheers.

@noodlefrenzy my best guess is that it looks like the link is somehow trying to reattach while already attached?
@jacoscaz it would be very helpful if you could run a copy of your client with the environment variable DEBUG=amqp* set, so we could see what kind of framing is occurring during the problem

@mbroadst unfortunately, I cannot. Sorry about that, I'd be more than happy to but that specific environment doesn't allow for that.

@jacoscaz @mbroadst That's possible - I ran into a similar error yesterday when testing some code for V2. I've reached out to my contact inside ServiceBus to see if they might have any insight into when they throw that error so we can match up against what we do.
@jacoscaz are there gaps of time (> 10 minutes) when you are not sending messages? If so, ServiceBus kicks the link and we re-attach the next time a message is sent, which could potentially lead to some sort of overflow of an internal counter or number of handles on their end. Pure speculation at this point.

@noodlefrenzy yes, absolutely. I'd say there could be even hours of no messages being sent - mostly at night.
@noodlefrenzy @mbroadst thanks for your support. I guess I'll refactor things so as to tear down the client completely and set it back up when this thing happens. Does this sound reasonable?

@jacoscaz yeah I think you're going to have to do that with 1.0.x unfortunately. @noodlefrenzy is currently working on improvements to handle this scenario more seamlessly in 2.0

I was going to suggest that exact thing, but felt bad about it :)
I'll let you know if I hear anything back from the ServiceBus team. I'll try and build a burn-in test for 2.0 to make sure this doesn't happen with it - can I get any more information about when it happens? How many days, typically? How many messages total? Gaps between messages?

@noodlefrenzy my best guess would be anywhere between 2 to 5 days from starting the system @ 100 - 2k messages per day per link, received in bursts of 10 - 100 through 1 - 5 active links. It's a wild guess, though. I'll try to come up with more precise numbers.
No worries - sometimes the old 'just reboot it' trick still comes handy... :).

Quick follow-up @noodlefrenzy @mbroadst:
We've just seen the same error making an appearance after two weeks without glitches. This time, though, it's taken a complete reboot of the VM to get things back to normal. Killing and re-starting the node process anew gave 0 results.

How the... what the... huh? My code doesn't keep any external state - I have no clue what it's doing that would require a reboot. All I can think of is that it's leaking connections on error and causing the VM to run out of sockets. Maybe you can do a netstat right after reboot and one after a couple of days and see if there are a bunch of extra listeners lying around?

@noodlefrenzy maybe we should look into: https://nodejs.org/api/net.html#net_socket_destroy, for error cases

@mbroadst Good idea. We should definitely make sure that makes it into v2.

@noodlefrenzy: I'm sorry I have come across in the wrong way - I absolutely did not mean to imply that your code was responsible for that. My intent is to gather as much context as possible and share it.
A check with netstat is definitely a good idea and I would gladly do that right now if only I had found a way to reproduce this baffling issue. What you suggest makes sense, although (if I understand correctly) it also implies that something is preventing further connections from being established. I will get back at you as soon as I manage to discover more. Many thanks for your awesome work and very kind support - I'm hopeful we'll be able to start working with the next version of amqp10 in the coming weeks.

@jacoscaz Hahaha, dude, never worry about insulting me - I've been in this industry a long time and have a thick skin. Plus, I've worked at Amazon so can handle just about anything ;-)
I realized you were just trying to give me more context - I was just genuinely baffled by how it might be happening. All I could think of was that we're trapping resources somehow that live beyond process restart, and sockets seemed like the most likely culprit. My thought with the time-delayed netstats was that you wouldn't need to wait for it to replicate, since I'm guessing it's a slow leak and it'll be visible with any time-lapsed snapshots on the same machine.

:)
I will give that a try over the next few days and report back with my
findings. Once again, thanks a lot.
On Tuesday, August 18, 2015, Michael Lanzetta<EMAIL_ADDRESS>wrote:

@jacoscaz https://github.com/jacoscaz Hahaha, dude, never worry about
insulting me - I've been in this industry a long time and have a thick
skin. Plus, I've worked at Amazon so can handle just about anything ;-)
I realized you were just trying to give me more context - I was just
genuinely baffled by how it might be happening. All I could think of was
that we're trapping resources somehow that live beyond process restart, and
sockets seemed like the most likely culprit. My thought with the
time-delayed netstats was that you wouldn't need to wait for it to
replicate, since I'm guessing it's a slow leak and it'll be visible with
any time-lapsed snapshots on the same machine.
—
Reply to this email directly or view it on GitHub
https://github.com/noodlefrenzy/node-amqp10/issues/146#issuecomment-132350867
.

--
--
Jacopo Scazzosi
Developer
http://www.jacoscaz.com

Hello @noodlefrenzy, hello @mbroadst. Here's another follow-up on this issue.
Over the last two weeks we had the same thing happen two times. I've been able to check the machine's state (memory, sockets, fds, ...) every 2 - 3 days or so but never found anything out of the ordinary.
However, we did notice that rebooting the machine from within the machine itself (via SSH) doesn't always solve the problem. A reboot from the Azure's console is often necessary to get the AMQP connections to work.
Any news from your contacts in the Azure team?

@noodlefrenzy this sounds like the handles aren't being reused, I can't recall if that made it in your last set of changes. Did it?

@mbroadst yes, the handles-not-being-reused issue should be fixed in master. The issue he's seeing is that it's failing to reconnect even after restarting the node process, which doesn't make sense since we don't keep any state.
@jacoscaz - please email me your service-bus namespace and queue-name(s) to<EMAIL_ADDRESS>I'll forward them on to my contacts on that team and see if they can look at the logs on their end.

Hey @jacoscaz, two things:

Did you ever hear back from the Service Bus folks? I forwarded your message with your details on to them, and then kind of lost track and didn't hear anything back myself.

v2 of the library is now out (has been for a little bit) and has a TON of bug fixes. It requires some minor rewrites as we've changed to a promise-based API, but if you're willing to do the work it should be much more stable, and might in fact solve this problem. I can't be sure, since honestly it seems like something on the Azure side, but it's worth considering if you have the time. I've updated the examples/ directory with examples for using the new API, so it should be easy to port.

Let me know what I can do to help, I'm terribly sorry this has dragged on.

Hello @noodlefrenzy.

Nope, I've never heard from them.

Yes, I realized a while ago that it had been published on NPM. Unfortunately, I'm still to be scheduled the necessary time to make the switch.

I really appreciate your support and I'm sorry I haven't been able to come back at you sooner. I will update you as soon as I get the chance to work on this.

Let me know if/what I can do to help when you decide to do the switch - I've updated the examples in the /examples/ directory, but I'm willing to help however you need it. I'm just sorry you ran into such troubles with it - I really hope you won't see those problems when you switch, v2 has a lot of bug fixes, and I think the API is cleaner.

Hello @noodlefrenzy and @mbroadst.
Unfortunately we're yet to switch to V2. However, I believe I have some useful feedback (which might also relate to #152).
As partly mentioned in my above comment dated Aug 18th, we've been dealing with this extremely frustrating issue by manually rebooting any VM that stops receiving messages. As we usually don't get any error whatsoever, we've set-up email alerts based on the amount of transferred data within the hour so that we can intervene when the situation requires it. Far from ideal, yes, but this is the only thing that works, or at least used to work.
This morning, though, one of our VMs stopped receiving messages and we haven't been able to do anything about it so far. We tried rebooting, we tried leaving it off for a while. As usual, no code changes, no errors, nothing. The system looks ok, sockets look ok, FDs look ok, CPU and memory consumption look ok. Even worse, this happened on a relatively "new" VM. It never happened on VMs that have been running (minus the reboots) for much longer.
Setting up the same exact environment (exactly the same code, exactly the same configuration, exactly the same everything) onto another machine, however, worked perfectly.
Regardless of us stumbling into V1's issue of handles not being reused (as per your comment dated Sep 2nd), this looks more and more like something on the SB / Azure side.

What the heck?! Is this still using the same credentials you emailed me to my work address previously? If so, I'll try and get the SB team to start looking at it ASAP and see if they can find the logs on their side.

Two more questions for you:

Would you be willing to run in "debug mode" (export DEBUG=amqp*)? If not in production, would you be willing to do so against a different queue and on a dedicated VM maybe so you don't interfere with prod? (the latter might not get us the result we need, but is better than nothing). We'd be looking to see if you were getting a disconnect/reconnect loop that might be causing you to overflow counters.

Would you be willing to take a "point release" upgrade (e.g. 1.0.3 to 1.0.4) if we were to try and selectively pull some of our V2 bug-fixes "back in time"?

Thanks!
Mike

P.S. I just heard back from Xin, and it looks like there was a networking issue in the data center with your queue last night which resulted in a temporary outage. That's likely what caused the issues you saw with your new VM.

Hello @noodlefrenzy.
Thank you for getting back at me so quickly. Ok, I understand about the networking issue. Will tell the team. Yes, the credentials are still the same.

Would you be willing to run in "debug mode" (export DEBUG=amqp*)?

I can try. It'd help if I had a word or a string to look for in the logs. Is there a specific pattern I can work with?

Would you be willing to take a "point release" upgrade (e.g. 1.0.3 to 1.0.4) if we were to try and selectively pull some of our V2 bug-fixes "back in time"?

I'd be more than willing to but I am afraid I do not have the time to do so on my schedule. However, it looks like I'll be able to work on V2 in a week or so. Fingers crossed.
Cheers.

Woohoo, a switch to V2 would be fantastic :) I think that'd almost certainly help clear up a number of issues. I'll take a look at the code for 1.0.3 (it's been a while) and get you something to grep for in debug mode.

@jacoscaz I think if you look for the string "Transitioning from" that should give us useful information without disclosing anything from your end - we're just trying to get a handle on how often we're seeing state transitions and why.
Looking for "Processing frame" would give us much more information, but some of it would undoubtedly be sensitive. You could limit it to those containing "DetachFrame" without giving away any details, and that would give us a better insight into whether ServiceBus is severing your connections and why.

@jacoscaz any further information on this? I'd like to close the issue if it's no longer a problem.


No such file or directory: './scripts/lib/update-git-upstream'

Hi,
I've been running the latest git version of zulip for years now but suddenly I see the following error message when running /home/zulip/deployments/current/scripts/upgrade-zulip-from-git main
Traceback (most recent call last):
  File "/home/zulip/deployments/current/scripts/lib/upgrade-zulip-from-git", line 136, in <module>
    subprocess.check_call(["./scripts/lib/update-git-upstream"], preexec_fn=su_to_zulip)
  File "/usr/lib/python3.10/subprocess.py", line 364, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/usr/lib/python3.10/subprocess.py", line 345, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.10/subprocess.py", line 969, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.10/subprocess.py", line 1845, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: './scripts/lib/update-git-upstream'

Zulip upgrade failed (exit code 1)!

The upgrade process is designed to be idempotent, so you can retry after resolving whatever issue caused the failure (there should be a traceback above). A log of this installation is available in /var/log/zulip/upgrade.log

what's going on here?

@andreas-bulling thanks for the report! This is probably a bug in upgrade-zulip-from-git itself, which runs code from the version you're upgrading to. @alexmv can you investigate?

What git commit are you upgrading from?
su - zulip -c 'git -C ~/deployments/current rev-parse HEAD'

@andreas-bulling any chance you have time to answer this? We'd like to track down this bug.

Lacking further information, I suspect this was from the brief window after 96e42b8e811f28855ddae8721361f7ffccbaa19b but before 63e31a6de47aced1234143770ad596fe600d3fbe.
Applying 63e31a6de47aced1234143770ad596fe600d3fbe to ~zulip/deployments/current before running ~zulip/deployments/current/upgrade-zulip-from-git should allow one to bootstrap out of that bad commit range.


chore: Run unit test with separate data. DO NOT MERGE

Description

[!TIP]
Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).
Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

Summary by CodeRabbit
Release Notes

New Features

Introduced comprehensive Cypress tests for validating various date formats in table widgets.
Added a utility for generating formatted date strings for tomorrow's date.
New constants for handling different date input formats.

Bug Fixes

Enhanced date validation logic in data transformation functions.

Tests

Added unit tests for data transformation functions, covering valid and invalid date cases.

Chores

Created mock data structures for testing table widget functionalities.

removing as no longer needed


Add website output

I made a quick example view of what we could get: https://paulzierep.github.io/datatable-rendering/
We can add it as an iframe to the hub.
Pages for each community could be created here...

Great work @paulzierep 😄
Some initial ideas / comments:

Could / should the metadata currently in the drop down menu be included as additional (optional columns)?
I can't locate the tool cherri on bio.tools (see image below). Is this an error?

We can customize the data table as much as we want, so I think the first point should be easy todo, actually any community could customize as they want by manipulation the template for this, but I am not good at all with JS / Frontend stuff, so maybe we find someone still who can help with this, or I will check next week with our dev people ...
The other point is probably again the issue with an link in the wrapper but people forgot to actually add the entry in bio.tools. I just added it.

This is how ToolFinder renders a data table using R
https://github.com/AustralianBioCommons/australianbiocommons.github.io/blob/master/rmarkdowns/2_tools.Rmd#L114-L160

I think I cannot do much this week to improve the table, but feel free to modify to improve the rendering and style.
https://github.com/bebatut/galaxy_tool_extractor/pull/22

See also https://github.com/galaxyproject/galaxy_tool_extractor/issues/25

Hi @paulzierep - is a dedicated website for the tables still of interest? I have some ideas 😄

@supernord sure, currently the table is rendered purely via the JS library datatables, but I do not have the JS knowledge to further improve it, also it runs without a backend, purely using the JS library.
If you (or anybody) can use the csv as input and produce a nice view output, I am happy to replace the current view, with an improved version.
We also need a landing page view for the GitHub pages. Maybe just a simple HTML, that provides the complete table as well as as a list of the sub-tables. But also here I am happy for any contribution !

Thanks @paulzierep - would you be happy to use the ELIXIR Toolkit Theme for the landing page? https://elixir-belgium.github.io/elixir-toolkit-theme/
I can generate a PR to set this up.


Fix Websockets not working

This will cause python-socketio to be downgraded to version 5.5.0. As otherwise the frontend will somehow not receive any messeges via websockets. Should fix #160

Works for me, thanks!


Update the gradle build tasks to generate play store builds

Configure the gradle builds to sign and build the release version of the Godot Android Editor
Note: dependent on https://github.com/godotengine/godot-build-scripts/pull/78
3.x version

@akien-mga Updated this PR following our conversation.
Here also, the build generates a android_editor-release-unsigned.apk binary when the signing credentials are not provided.

Thanks!

Cherry-picked for 4.0.4.


Template for feature requests

Nice to have a template for feature requests

Yes, we should have. I also suggest that you join our Discord channel for quick requests.


Special vue tags do not autocomplete

So we need something like this?
{
    "scope": "text.html - source, punctuation.definition.tag.begin",

    "completions":
    [
        { "trigger": "slots", "contents": "<slot>$0</slot>" },
        { "trigger": "component", "contents": "<component :is='$1'>$0</component>" },
        { "trigger": "transition", "contents": "<transition>$0</transition>" },
        { "trigger": "transition-group", "contents": "<transition-group>$0</transition-group>" },
        { "trigger": "keep-alive", "contents": "<keep-alive>$0</keep-alive>" }

    ]
}

It's annoying that the Vue special tags can't be tab completely like any other HTML tag.  I can make a pr if this would be welcome, or perhaps there is a better way?

Ping?

Hi @yyyc514
Thank you for taking the time to point this out and look into possible solutions. I apologize for the delay.
I personally think this would be useful. I just don't want to interfere with emmet or other packages. Moreover this is just a syntax highlight package, and I believe there are other packages in place for snippets.
@yyx990803 do you have any thoughts of including snippets in the extension?

Emmet looks nice (installed).  It doesn't work out of the box with Vue files though, so I'm not sure this would be a conflict.  Someone using just the syntax would get the snippets for free... and someone who decided to specifically turn on Emmet for .vue files would know they were manually killing snippets (the docs mention this) in favor of Emmet.  At least that's what it seems like from reading the docs: ("How to expand abbreviations with Tab in other syntaxes")
https://github.com/sergeche/emmet-sublime/blob/master/README.md

And of course Emmet's default keybinding (Ctrl-E) isn't going to conflict with the snippets at all.


Power management signals

There were discussions on https://github.com/pgaskin/NickelMenu/issues/124 about using the signals from N3PowerWorkflowManager to notify scripts/programs when resuming from sleep etc. It's probably best to continue the discussion over here.
For reference, the available signals are:
aboutToSleep()
resumingFromSleep()
resumedFromSleep()
aboutToPowerOff()
aboutToReboot()

Pinging @marnovdm @NiLuJe

Yes this seems like a better place, thanks for opening this! I (unintentionally) hijacked the original issue post a bit anyway :smile:
Not sure if I can contribute anything here, as I'm not really familiar with C++, and I'll be on holiday for the next couple of weeks so it'll be a while before I get back to this issue.


qwen1.8B GPU memory usage is too high

https://www.modelscope.cn/models/qwen/Qwen-1_8B-Chat/summary
使用如上模型在显卡A770上运行，得到如下数据：
32in32 out peak GPU mem:3.1G
2048in512 out peak GPU mem:7.4G
4096in1024 out peak GPU mem:11.6G
8192in2048 out peak GPU mem: OOM
这个和官网INT4 的memory占用差距很大，是否能优化。
env： Linux 22.05 kernel5.19
OneAPI 2024.0
bigdl 2.5.0b20231218
ipex :2.1.10+xpu
复现方式：
转换Qwen模型到Low bit int4
使用benchmark脚本运行不同的输入测试性能。
部分测试代码：
with torch.inference_mode():
torch.xpu.synchronize()
prompt = QWEN_PROMPT_FORMAT.format(prompt=prompt)
input_ids = tokenizer.encode(prompt, return_tensors="pt").to('xpu')
torch.xpu.synchronize()
# ipex model needs a warmup, then inference time can be accurate
output = model.generate(input_ids,
max_new_tokens=args.n_predict)
for i in range(5):
        st = time.time()
        torch.xpu.synchronize()
        input_ids = tokenizer.encode(prompt, return_tensors="pt").to('xpu')
        output = model.generate(input_ids, do_sample=False, max_new_tokens=args.n_predict)
        output_str = tokenizer.decode(output[0], skip_special_tokens=True)
        torch.xpu.synchronize()
        end = time.time()
        print(f"cost {end - st:.4f}s")
        print(output_str)

Hi, https://www.modelscope.cn/models/qwen/Qwen-1_8B-Chat/summary in this page seems the memory is for 1 token in and 2048/8192 token out, and in the script they provide, seems they are using flash_attention, not sure if this is the reason why their memory usage is smaller.
We are currently doing memory optimization on QWen and will update you when we have progress.

For longer sequence input (1k/2k/4k,...), bigdl-llm uses larger memory than the official model. We will look into this.

thanks for the update.

Hi, sorry for the late reply. One difference is that for the official int4 model, it is using w4a16, but previously when you run with ipex-llm, we are using w4a32, so you need to add model = model.half() after loading the model before putting it on xpu.
We have optimized our memory usage and compared with RTX4090, the memory usage is reasonable/compatible now. Please have a check with the latest ipex-llm :)


Change OLM deployment to add ServiceAccount with nonroot

What this PR does:
When creating the bundle, a new serviceAccount called cass-operator-cassandra-default-sa is created with nonroot access. If cass-operator detects the Datacenter is deployed in a OLM installation, this same ServiceAccount is set for the StatefulSets.
Output in CSV:
        - rules:
            - apiGroups:
                - security.openshift.io
              resourceNames:
                - nonroot
              resources:
                - securitycontextconstraints
              verbs:
                - use
          serviceAccountName: cass-operator-cassandra-default-sa

@mgoerens
Which issue(s) this PR fixes:
Fixes #541
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[x] CHANGELOG.md updated (not required for documentation PRs)
[x] CLA Signed:  DataStax CLA

Related: https://github.com/k8ssandra/management-api-for-apache-cassandra/pull/310

Closed in favor of #547

When I ran docker pull, I received error.
 % docker pull datastax/cass-config-builder:1.0-ubi7
1.0-ubi7: Pulling from datastax/cass-config-builder
no matching manifest for linux/arm64/v8 in the manifest list entries


Skip modules with bad image sizes

When encountering a module with a bad image size, log a warning and continue instead of returning an error for the whole module list.

Merging, thanks!


Handle creation prompt default to Y

When using quartz use <non-existent-handle> the CLI immediately figures there is no such handle and displays a prompt asking whether you would like to create one. In most of the CLI tools I use, the Y option is the default(Y/n), so I think it would be a good ideia implement this, since most of the time you actually want to create the handle anyways.

What do you mean by "by default" exactly? If you'd provide an example application would be great too!

What do you mean by "by default" exactly? If you'd provide an example application would be great too!

So here is one example from Vtex CLI:

Notice that if I just hit Enter, it will create the workspace, that's what I mean by "default"


AlignedObjectValues: support computed property names

Fixes #1404

Coverage increased (+0.0%) to 99.02% when pulling 71fa3a60611f691cfae6327ad77521247433937a on hzoo:i-1404 into 527771d4bb5f10783e199a84c3beebeba7ad01d0 on jscs-dev:master.

Lgtm. Nice work!


Illegal Access

Throws "illegal access" when toString is called on the error created in lib/transporters.js#78. The error is not thrown if line #80 is removed.

http://www.karadzhov.com/2014/06/nodejs-and-illegal-access-error.html
https://code.google.com/p/v8/issues/detail?id=2397

node -v 0.10.26
npm -v 1.4.3
(will upgrade node/npm as soon as I'm stable.)

+1

+1

+1

FYI: this is being addressed in #21

Fixed by #21


Unable to add new keypad user

I am having trouble getting the add a new keypad user process to work. Everything else seems to work well (great job btw!), for example, I can delete a user that I have previously created using the Nuki app. But If I run a HA script to add a new user I get a failed commandResult (monitored using MQTT Explorer). I am running the Mosquito broker add-on in HA. Below are my script yaml's:
alias: "Nuki: Add New User Code"
sequence:
  - service: mqtt.publish
    data:
      topic: nuki/keypad/command/name
      payload: fred
      qos: "2"
  - service: mqtt.publish
    data:
      topic: nuki/keypad/command/code
      payload: "123456"
      qos: "2"
  - service: mqtt.publish
    data:
      topic: nuki/keypad/command/enabled
      payload: "1"
      qos: "2"
  - service: mqtt.publish
    data:
      topic: nuki/keypad/command/action
      payload: add
      qos: "2"
mode: single

alias: "Nuki: Delete User Code "
sequence:
  - service: mqtt.publish
    data:
      topic: nuki/keypad/command/id
      payload: "4"
      qos: "0"
  - service: mqtt.publish
    data:
      topic: nuki/keypad/command/action
      payload: delete
      qos: "0"
mode: single

Any help or pointers to aid debugging will be greatly appreciated.
Also, I did not see any way to set time limited access on the keypad codes. Is this possible using nuki_hub and, if not, are there plans to introduce such functionality?

I don't see anything obvious that's wrong with the script. I tried manually setting nodes the same way and it works for me. Does it work when you set it manually using MQTT explorer?
I've not added the time limited access functionality because the API is a bit tedious ... it requires six fields to be set:
https://developer.nuki.io/page/nuki-smart-lock-api-2/2#heading--add-keypad-code
But if there's a need I could add it.

Yeah, I started off using MQTT Explorer but that didnt work either. Interestingly I see data appearing on the command node continuously, multiple times per second as below. Is that to be expected?

My use case depends on being able to set the time limited access functionality, so I definitely have a need (although that's kinda moot if I can't set up new users in the first place)

No that's not supposed to happen. I'll check the code later. It's supposed to ignore the UnknownCommand string to prevent a neverending loop of receiving and sending UnknownCommand. For now maybe disconnect the ESP, and write a valid command in there, then re-connect the ESP.

Ahh Ok, well at least we are on to something. Your disconnect suggestion didn't work I'm afraid.

Which node exactly do you get constant traffic on? The "action" node? Whenever you write something to the action node, two things happen:

The action node itself will be reset to "--"
The commandResult node gets updated.

Is the UnknownCommand from you testing something? You should only ever write "add", "delete or "update" to the action node, anything else will result in an UnknownCommand. If that happens unintentionally, someone (HA ?) is writing something to the action node. It's just not very obvious, because it gets reset to "--" immediately by the ESP.
The attached firmware outputs what it receives on the action node over the serial line.
nuki_hub.zip

Hopefully this video makes it obvious which nodes. If it's coming from HA it's not something I've (intentionally ) done. Is there a way to tell where it's coming from (apologies I am very new to MQTT)?
https://user-images.githubusercontent.com/30226844/207974947-dafee959-75d6-4fe2-94d2-fee4679550dd.mp4

From what I can see I think all nodes are updated. The most plausible explanation is indeed that something is writing to the action node, because that resets all the other nodes (showing as an update in MQTT explorer).
You can:

Have a look at the history of the nodes, especially the action node
write something into the commandResult node (e. g. "###"). If it's immediantely reset to UnknownCommand, you know the ESP is updating the node.

To really tell which client is updating the node I guess you have to check your MQTT broker, so there's general answer. It depends on whatever broker you are using.

Have a look at the history of the nodes, especially the action node

The history of these nodes just shows the same thing repeated again and again (as per this screen shot):

write something into the commandResult node (e. g. "###"). If it's immediantely reset to UnknownCommand, you know the ESP is updating the node.

It is immediately reset to UnknownCommand when I write to commandResult.
And I am using Mosquito, when I set the logs to debug this is what I see receiving and transmitting:

Can you try 6.3 ? I've added a check there to ignore "--" in the action node.

I've uploaded 6.3, the continuous updating of the keypad nodes has stopped, however, if I run my script to add a new keypad user, I can see those values being published but there is no response on the commandResult node (and no new user appears in the nuki app)

Just to make sure, you did enter the PIN on the ESP?

Hmmm, I'm not sure what you mean. I have previously entered the PIN in the credentials page (and I've now just done it again on your prompt, in case you meant after updating the firmware). In any case, there's still no response on thecommandResult node after I run my add user script.

 Keypad commands didn't work at all with 6.3 and 6.4, it's fixed now in 6.5. I reviewed the code, I have no explanation why nodes would be constantly updated ... it doesn't happen for me. I wonder if this somehow has to do with the broker being used.

I do get a commandResult this time, but I am afraid its "failed"

ok ... does it always return failed? Failed usually means something went wrong with the bluetooth communicaiton.

Yes, it fails every time I try (I've just checked 10 times or so just in case)

ok, there are a few reasons why it could fail:

bluetooth communication failed. Unlikely if everything else works.
PIN missing or wrong ... but you checked that already
Parameters wrong. You have to give a name and a 6 digit code. No zeroes allowed in the code, for obvious reasons :)

Other than that I'm out of ideas

bluetooth communication failed. Unlikely if everything else works.

Yeah, and I've just double checked that by deleting a user

PIN missing or wrong ... but you checked that already

Well, I've re-entered it, but I saw no way of actually checking it (if I deliberately add in a wrong pin I get no notification of that)

Parameters wrong. You have to give a name and a 6 digit code. No zeroes allowed in the code, for obvious reasons :)

Yes, indeed.
One point of clarification, I don't get a "failed" commandResult now, I get nothing at all when I try to add a new user.

Please flash the attached firmware and check the serial logs. If successful it should look like this:
# KP action received: add
## KP has keypad: 1
## KP keypad enabled: 1
## KP has keypad: ADD
## KP name: the name
## KP code: 111222
Add keypad code: 1

One thing I noticed: It seems the lock rejects certain simple codes. I tried "123456" for testing, and I consistently get "failed" as a result. Trying the same in the NUKI smartphone app, it says "entry codes must not start with 12" ... so whatever code you're trying to add, better check first in the smartphone add if it's a valid code.
nuki_hub-dbg-1.zip

I just noticed I put 123456 as an example in the readme ... I've updated it to something that works.

I changed the code to one that didn't start "12..." and it now works. I cant believe it was that that had me foxed all along. Thanks for your help and persistence with this, it works great now.
Now, if you ever get round to adding in the time limited access ...

Wild guess: is it a keypad 2.0?

Nope, this was related to using the example PIN I provider (123456). The Locks firmware doesn't allow PINs starting with "12" to prevent people from using 123456 as a PIN. I didn't know that at the time of writing of the README, but I've since corrected it, and the issue could be resolved.


Completed inorder traversal assigned to me for hakincodes

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Description
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[ ] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

Completed #415 issue assigned to me
Divyang Bagla

As a part of hakin codes they were telling not to update readme so should i update or ?

@bagladivyang03 Ok than leave it. I was not aware of that.

Yeah ok

It is working na See
Enter the data for root node
3
Enter the postion l / r where u want to insert the element
l
2
Do u want to enter more data ?
y
Enter the postion l / r where u want to insert the element
l
Enter the postion l / r where u want to insert the element
l
1
Do u want to enter more data ?
y
Enter the postion l / r where u want to insert the element
r
4
Do u want to enter more data ?
y
Enter the postion l / r where u want to insert the element
r
Enter the postion l / r where u want to insert the element
r
5
Do u want to enter more data ?
n
1 2 3 4 5
1 2 3 4 5
using recursive and non recursive the ans is correct na ?
Then whats the prob ??

Could u pls tell what is the change i have to do ?

Could u pls tell what is the change i have to do ?

Hey @bagladivyang03 the code is working fine for me.
\cc: @plazzy99

Yeh sure i will do that :)

Hi there is some conflict between C++/readme @iamrajiv could u pls help in previous pr i was also getting the same type of conflicting issue.

@bagladivyang03 Your branch is 119 commits behind TesseractCoding:master. Please make it even. Also, add inorder.cpp file inside the C-Plus-Plus directory. I would also suggest whenever you do changes make a separate branch for that, do not commit to master branch.

Okay i will do that inorder.cpp in c++ directory but how to make it even @iamrajiv

@bagladivyang03 move inorder.cpp to C-Plus-Plus/graphs and for syncing issues go through this https://www.atlassian.com/git/tutorials/syncing

Can anyone pls help as i try to create a new pr it is always coming with previous commits as @siddharth25pandey u mentioned to create new pr Could u pls help

Can anyone pls help as i try to create a new pr it is always coming with previous commits as @siddharth25pandey u mentioned to create new pr Could u pls help

@bagladivyang03 You can create separate PR by Committing the required files only i.e one by one .

Can anyone pls help as i try to create a new pr it is always coming with previous commits as @siddharth25pandey u mentioned to create new pr Could u pls help

Commit all the changes if current branch.
Move to master branch
Create n new branch and make the changes, commit it and push it and then create a PR with this.

Always remember to navigate to your master branch while creating a new branch, otherwise all previous commit of previous branch will get to the new one.
Feel free to ask if you need any further clarification.

@Kajol-Kumari  could u pls merge these as my repo is showing x commits ahead , y commits behind so if u merge ig these issue will solved and also the new PR issue which I m facing


Mention some file dependencies of dune files explicitly

Explicitly mention a few implicit file dependencies in dune files.
Also contains some changes to how bash scripts are called from Dune (via explicit Bash call), this simplifies usage in nix wrapping and seems to do no harm to default flow.
Explain how you tested your changes:

Mina compiles

Checklist:

[x] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[x] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? None

!ci-build-me


Define account status implementation

As a user I want to know the status of each connected account: if it is running, the progress, and if there are any errors.
Define how the account status will be implemented.

status (running/paused/error)
persistence (historical data)
retrieve (real-time data)
a model that will be displayed

Acceptance criteria
1 - Description of the implementation of account status
2 - Create new issues to implement this

As a user, when you first scan, overall progress should be seen
Once initial scan is done and we only want to index/fetch new stuff, the user should see progress about the additional fetch only.
When fetch is done, it should say the amount fetching.
Change fetch table to:
overall_indexed, overall_fetched, overall_total, current_indexed, current_fetched, current_total


temp force export to default host

Temporary fix to unblock the dev env. This appears to need the db details to be provided in master.host, and when it sees an empty string '' it throws the <IP_ADDRESS>:5432 connection refused error. I suspect if we force export function connection to be the same as the default for now, we won't get this issue.
Dev env still doesn't connect, and when I pull the code down it doesn't connect for me in local docker setup. Something doesn't seem right with the replica connection stuff yet, not sure how it works on your env @ppratikcr7.


Fail to run static pod without master running

Environmental Info:
K3s Version:

1.28.6
Node(s) CPU architecture, OS, and Version:

4 core arm64
Cluster Configuration:

1 master + 1 worker
Describe the bug:

I have a static pod running in each node, both nodes went into failure for a power lost.  For some reason, the master node was not able to recovery, but worker node boot back as normal. However, k3s service stuck at
time="2024-04-28T02:53:14Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33176-><IP_ADDRESS>:6444: read: connection reset by peer"

hence my static pod was not able to come back.
I am wondering if this is an expected behaviour. Could it will be nice to have containerd and kubelet up and run, then static pod start. Let the kubelet try to connecting  back when master is available later on?
Steps To Reproduce:

Installed K3s on two node, one run as master, another run as agent.
Deploy static pod yaml in /var/lib/rancher/k3s/server/manifests
Static pod up and run in both nodes
Power off both nodes
Power on work node, but let master off
k3s service fails to start, so the static pod
Expected behavior:

k3s service on work node  start containerd, kubelet, and static pod,  keep trying to reach master until master node is online.
Actual behavior:

k3s  service on work node failed to start
Additional context / logs:

time="2024-04-28T02:52:00Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33126-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:52:06Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33130-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:52:12Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33136-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:52:18Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33140-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:52:25Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33144-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:52:31Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33148-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:52:37Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33152-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:52:43Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33156-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:52:49Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33160-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:52:55Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33164-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:53:01Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33168-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:53:08Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33172-><IP_ADDRESS>:6444: read: connection reset by peer"
time="2024-04-28T02:53:14Z" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": read tcp <IP_ADDRESS>:33176-><IP_ADDRESS>:6444: read: connection reset by peer"

I see we have allow this for etcdagent node, can it be extended to normal agent node?

This is a duplicate of https://github.com/k3s-io/k3s/issues/1686
K3s agents do not start the container runtime or kubelet until a server is reachable to provide up-to-date certificates and configuration. Because the kubelet isn't started yet, there is no issue with Kubernetes conformance - conformance places no requirements on how a distribution operates prior to startup of Kubernetes itself, or what startup dependencies a distribution enforces.
Although there have been discussions on this topic in the past, we are not planning to relax this requirement at this time


add missing inline declarations

This is so that memcury can be used in multiple cpp files without breaking.

thanks for merging! 👍🏻


Ignore applinks for current domain

Task/Issue URL: https://app.asana.com/0/414730916066338/1200868385373197/f
Description
This PR adds logic to ignore app links for the current domain if the user taps "no" on the app link dialog.
Steps to test this PR
Install a companion app (Amazon, LinkedIn, Github, Guardian, Wikipedia...)
The below steps assume the Amazon app was installed.
Navigating via SERP

Type "amazon" in the search bar
Tap on the Amazon link in the search results
Verify that the app link dialog is shown
Tap "No" on the dialog
Verify that the app link dialog is not shown again while navigating around the amazon.com domain
Type "google maps" in the search bar
Tap on the Google Maps link in the search results
Verify that the app link dialog is shown

Navigating via search bar

Type "amazon.com" in the search bar
Verify that the app link dialog is not shown while navigating around the amazon.com domain

Thanks for the review @marcosholgado! I've made the requested changes ✅


(fix) update insecure packages

Snyk reported 18 issues and 54 vulnerable paths for this repo.
This PR upgrades some of the packages, based on snyk recommendations. It does not wrap up the work that needs to be done because the repo still has 15 issues and 42 vulnerable paths. It merely is a first iteration.
I tested using npm run test and all tests pass.

It would be better to open this as a PR to https://github.com/wayfair/dociql since we'd lose these changes in our fork if we pull from the upstream master.

Thanks Eric! I created a PR to the wayfair/dociql repo: https://github.com/wayfair/dociql/pull/5


lsp, Flycheck checker and Autocomplete don't work if file is passed as an argument to Emacs

What did you expect to happen?
I have enabled lsp for python and C/C++ and it works flawlessly if I manually open associated files in emacs but whenever I open it using emacs "filename" or emacs -nw "filename" from terminal lsp and flycheck should work.
What actually happened?
When filename is given as argument in terminal Flycheck, lsp and autocomplete do not work and I have to enable them manually!
Steps to reproduce:

Open a terminal and type emacs "filename" or emacs -nw "filename".
Flycheck, lsp and autocomplete are disabled, need to enble them manually.

System information:

((system
  (type . gnu/linux)
  (config . "x86_64-pc-linux-gnu")
  (shell . "/usr/bin/fish")
  (uname . "Linux 5.8.5-arch1-1 #1 SMP PREEMPT Thu, 27 Aug 2020 18:53:02 +0000 x86_64")
  (path "~/.config/xmobar/scripts/" ".bin/" ".cargo/bin/" ".emacs.d/bin/" "/usr/local/sbin" "/usr/local/bin" "/usr/bin" "/usr/bin/site_perl" "/usr/bin/vendor_perl" "/usr/bin/core_perl" "/usr/lib/emacs/27.1/x86_64-pc-linux-gnu"))
 (emacs
  (dir . "~/.emacs.d/")
  (version . "27.1")
  (build . "Aug 28, 2020")
  (buildopts . "--prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib --localstatedir=/var --with-x-toolkit=gtk3 --with-xft --with-wide-int --with-modules --with-cairo --with-harfbuzz 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt' CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now")
  (features . "XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB NOTIFY INOTIFY ACL GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD JSON PDUMPER LCMS2 GMP")
  (traits batch envvar-file))
 (doom
  (dir . "~/.doom.d/")
  (version . "2.0.9")
  (build . "grafted, HEAD -> develop, origin/develop, origin/HEAD ae3a2fa 2020-09-02 14:23:11 -0400")
  (elc-files . 0)
  (modules :completion company ivy :ui doom doom-dashboard doom-quit hl-todo modeline neotree ophints (popup +defaults) vc-gutter vi-tilde-fringe workspaces :editor (evil +everywhere) file-templates fold snippets :emacs dired electric ibuffer undo vc :term vterm :checkers syntax :tools (eval +overlay) lookup lsp magit :lang (cc +lsp) emacs-lisp json (javascript +lsp) (lua +lsp) markdown org (python +lsp) (rust +lsp) sh :config (default +bindings +smartparens))
  (packages "n/a")
  (unpin "n/a")
  (elpa "n/a")))

I can confirm this behavior too. It affects at least python, bash, and docker files too.

If I add in my config.el(add-hook! python-mode LSP), then python works as it should even if I invoke
emacs filename . I guess the generic solution is to add the relevant line for each mode when LSP is enabled in init.el. @hlissner

As of b461f76 this issue should be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

As of b461f76 this issue should be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

Thank you very much, my issue is resolved now and its working as expected! :)


Implement nicer code editor

When working on hooks / reports / pages, it would be lovely to have something a little higher quality to work in than the standard textarea control.

I found a couple of embedded code editors that we could work with yesterday:

CodeJar
AceJs

CodeJar is more minimal and looks better, but AceJs has a lot more features. I haven't tested any of these out yet so I don't know how any of the specifics work.

I tried both of these out, couldn't get Ace to work at all & Codejar did better but still had some issues - like the auto-closing pairs made your cursor disappear. Also looked in to using Monaco, which is the editor component from VS Code, but it is really not mobile-friendly at all.
More research needed!

CodeMirror is another possibility.


Cant find https module.

Hi. Im trying to use Syncano library and it uses the https module but the tabris app can't find the https module.

https is a code node module but is not implemented in tabris-js-node.  It would need to be implemented there.
Alternatively, you could package the module separately and load it, for example, using a tarball.

you could package the module separately and load it

That would not work, as this module depends on other node modules such as http that aren't yet available in Tabris.js.
For HTTP, your options in Tabris.js are currently either using XmlHttpRequest or the npm module whatwg-fetch.
Alternatively, you could try to find a Cordova module for Syncano and use this.

The builtin node modules http and https are not supported by Tabris.js. Even a partial implementation would be a considerable amont of work.


node_modules/.bin/tsc conflict with TypeScript in my package.json

I ran into https://github.com/huan/sidecar/issues/18 today and found that the @tsd/typescript has a { bin: { tsc: 'typescript/bin/tsc' }} and it overwrites the TypeScript version from my package.json:
https://github.com/SamVerschueren/tsd-typescript/blob/10f4da67ee72ce4005141bc2bef1830d3ae14512/package.json#L14-L16
I'd like to suggest that we should remove the bin entry in the package.json so that it will not overwrite the system version.

This is a case if you use NPM or PNPM, but not Yarn btw.

Yes, this behaviour can be different via implementations because module A and B both want to put a binary with the same name, and the NPM can not know which one should be preferred.

The way I see it, we should remove the tsc (and other binaries) from our tsc fork (@tsd/typescript).

I removed the bin from @tsd/typescript but didn't re-release any patches yet. I'm open to feedback if I should manually release a patch for every major TS version from the past, or if it's ok if this is only the case for newer versions?

I'm looking forward to the change for future versions, don't care about the past versions.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-24-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1686

Questions ?
Please refer to the Backport tool documentation


Enhancement: Extend spo navigation node add with support for audience targeting

Options to add:

Option
Description

--audienceIds [audienceIds]
Comma separated list of group IDs that will be used for audience targeting. The limit is 10 ids per navigation node.

API request:
Update the body of the already existing request to include:
{
    "AudienceIds": ["4a7a1426-4d90-421a-8050-265d8eca2495"]
}

Validation:

Max amount of audience IDs is 10
All IDs are GUIDs

I would love to work on this

All yours!


cursor navigation

change highlight of the current row + scrolling when needed with the up/down cursor keys. pressing the space key should toggle the selection state of the row

start in https://github.com/datavisyn/lineupjs/tree/sgratzl/cursor. However, somehow the arrow keys event are just triggered on the document or input nodes and not on regular nodes.

wontfix


Use the random_name function on the project_name argument of the project create command

Current behavior
The project_name argument of the ockam project create command is calling hex::encode() to generate the random name in the default_value_t attribute.
Desired behavior
The project_name argument of the ockam project create command should be calling the random_name() function.
Implementation details
Don't forget to import the random_name() function with use ockam_api::cli_state::random_name;.
This is the argument that must be changed, where default_value_t = random_name():
https://github.com/build-trust/ockam/blob/140a8bd71183754d70ec1e4bc1a5c962062fa0a9/implementations/rust/ockam/ockam_command/src/project/create.rs#L30-L31

Some tips for newcomers:

Create a new branch for the issue you are working on (don't push directly to your fork's develop branch)
Run cargo fmt. You can configure the editor to run it automatically everytime a file is saved
Run cargo clippy to make sure the code compiles + follows rust standards/best practices
You don't need to keep your branch updated with develop until there is a merge conflict. If you still want to update it, use git rebase develop instead of gir merge develop

We love helping new contributors! ❤
If you have questions or need help as you explore, please join us on Discord. If you're looking for other issues to contribute to, please checkout our good first issues.

Please assign it to me. I can do it.

I tried to run cargo clippy , but getting error as failed to select version for tauri-utils. In the repository we have tauri-macros v2.0.0-alpha.8 but its is saying tauri-macros = "v2.0.0-alpha.7" satisfies. What should i do?

Can you try installing these dependencies? https://tauri.app/v1/guides/getting-started/prerequisites#setting-up-linux
sudo apt update
sudo apt install libwebkit2gtk-4.0-dev \
    build-essential \
    curl \
    wget \
    file \
    libssl-dev \
    libgtk-3-dev \
    libayatana-appindicator3-dev \
    librsvg2-dev

I'm trying to confirm with another contributor if this is the root cause of this problem.
Once you have that, please try:
cargo build -p ockam_command
cargo clippy -p ockam_command


How to choose large kernel convolution internal kernel sizes for any external kernel size

In your paper you describe two cases:
kernel = 21, dw_kernel = 5, dwd_kernel = 7, dwd_dilation=3
kernel = 13, dw_kernel = 5, dwd_kernel = 5, dwd_dilation=3
and propose equations:
dw_kernel = 2 * dwd_dilation - 1
dwd_kernel = kernel / dwd_dilation
Could you please clarify how to choose these parameters for other kernel sizes?
E.g. what if we have kernel size = 22. Should we choose even dw_kernel, dwd_kernel and dilation?
It seems that from all possible 2 <= dwd_dilation <= kernel // 2 we should choose such value that minimizes (dw_kernel^2 + dwd_kernel^2). I'm wondering if there is an analytical solution?

We choose d according to the amount of calculation and parameters.
You can write formulas for the quantities of parameters and calculations, and then take the derivative with respect to d for a fixed K. In this way, you can choose a d such that the amount of computation and parameters is minimal.


v6: Promise based submit validation errors not processed (solved)

Promise based validation not works in v6.0.0-alpha.5.
Here the submit handler which I used. Tested in reduxForm({}) or passed in the container component.
onSubmit: () => {
        return new Promise((resolve, reject) => {
               reject({
                      _error: 'Some error',
                       job_title: 'Not valid!'
               });
        })
 },

The START_SUBMIT and STOP_SUBMIT action is fired on submit but without the errors. So no errors will show up.
The sync validate method works, when I just return the error object.
edit: I tried now to catch the promise directly and fire the SubmissionError exception. Then it works.
return new Promise((resolve, reject) => {
            .... reject(error)
        }).catch(errors => {
            throw new SubmissionError(errors);
        });

So there are two steps:
You MUST return a promise and you MUST throw the SubmissionError exception with the errors (in the catch block) to return some errors. The second step is little bit unnecessary because I only reject promise with errors when there was an input error. When there was an API error I reject it without errors?
edit:
Okey solved I found the way. I just call reject(new SubmissionError({...})). I first try to throw directly the SubmissionError. Don't know that that this works. So problem solved :) 👍

So, is there a problem? Maybe a problem in the docs? It sounds like you found your way to where you want to be.


No migrations volume in docker-compose.server.yml

Hi @chrisleekr, quick question...
I see migrations volume added into docker-compose.yml file and docker-entrypoint.sh but nothing added into docker-compose.server.yml
Could this be a problem where migrations don't get executed for who using on production with the server.yml definition?
I am asking just because I still having to run the FLUSHALL command every time I upgrade the bot.

Your log does not include migration part.
Please get the log of the migration parts.
__________.__                                    __________        __
\______   \__| ____ _____    ____   ____  ____   \______   \ _____/  |_
 |    |  _/  |/    \__  \  /    \_/ ___\/ __ \   |    |  _//  _ \   __
 |    |   \  |   |  \/ __ \|   |  \  \__\  ___/   |    |   (  <_> )  |
 |______  /__|___|  (____  /___|  /\___  >___  >  |______  /\____/|__|
        \/        \/     \/     \/     \/    \/          \/

><EMAIL_ADDRESS>migrate:up /srv
> migrate up --store=/srv/mongo-state-storage.js

It's migration up command after you restart.

Here's another attempt on the logs... let me know if it's complete now...
fabio.zip
Very strange, now that I am running v0.85 I don't get the error after a restart...
Will keep an eye on it and report back with more logs if get the problem again.

@chopeta
Your log still does not include the migration part.
Let me give you another way to check.
$ docker exec -it binance-bot /bin/ash
/srv # npm run migrate:up

Then it should run migration.
If you see the result like below, it means migration is completed.
><EMAIL_ADDRESS>migrate:up /srv
> migrate up --store=/srv/mongo-state-storage.js

WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
{"name":"binance-api","version":"0.0.85","hostname":"21981342578d","pid":92,"level":30,"NODE_ENV":"production","msg":"API logger loaded","time":"2021-11-09T10:34:55.610Z","v":0}
  migration : complete

@chrisleekr I am new to this bot.
Can you document the migration guide?

@binhnq94
This is an old issue, which I am about to close.
You do not need to run migration by yourself. It will automatically run the migration whenever it starts it.
Hence, you don't need any documents for migration.


Closing tag suggested too aggressively in HTML

Have the following html content
<header>
	<
</header>

Let the cursor be on the second line, as soon as you type < suggest widget shows and /header is the first suggestion.
I would not expect /header to be offered here since that tag is already closed.
fyi @keford

I see your point.

it's just a proposal. It's up to the user to decide whether it makes sense to pick that proposal.
closing an element that is closed later makes more sense when doing it for common elements like  and

+1 for sorting it lower if we find out that the element is already closed later in the file. We currently don't look after the current completion position.


E2E: Improve tests, lint, and add more drivers

This PR introduces lint to cypress code, adds drivers to try and abstract the usage of cypress as much as possible.
Nothing very interesting, mainly to try out the driver pattern for the e2e tests.

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

Comparison is base (b784bf2) 57.18% compared to head (eb04570) 57.18%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #855   +/-   ##
=======================================
  Coverage   57.18%   57.18%
=======================================
  Files         104      104
  Lines        2929     2929
  Branches      674      674
=======================================
  Hits         1675     1675
  Misses       1254     1254

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


Resolve a few recently introduced warnings

Bug/issue #, if applicable:
Summary
This resolves a few recently introduced warnings.
It also removes the need for @testable import in the testing utilities target.
Dependencies
None
Testing
Nothing in particular. This isn't used-facing.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests
[x] Ran the ./bin/test script and it succeeded
[ ] Updated documentation if necessary

@swift-ci please test


SW onupdatefound not triggered

Library Affected:
<EMAIL_ADDRESS>Browser & Platform:
*Chrome Version 69.0.3497.100 (Official Build) (64-bit)
Issue or Feature Request Description:
When testing my app in localhost then the onupdatefound is triggered and I can display a message telling about "new content available please close application". But when I testing with a domain using https then onupdatefound is not triggered but I can see where service worker change its state from activated to waiting to activate

But when I testing with a domain using https then onupdatefound is not triggered but I can see where service worker change its state from activated to waiting to activate

Can you show the code you're using?

I'm going to close this as I don't believe it's actionable at this point.
If you could provide more details, like a live deployment URL, we can revisit.


Oracle VM in Windows 10 Home Assistant + Frigate NVR (Full Access) plug-in + MQTT + HASC frigate add-on + M.2 Accelerator with Dual Edge TPU + Dual Edge TPU Adapter - PCIe x1 Low Profile

I bought M.2 Accelerator with Dual Edge TPU https://lh3.googleusercontent.com/esMOG-SboxCzrO18VYzqEz1DsPublV3p4tK1SVhFguiq0U_31bB9j2bW9ng7l99ljjMd9hHGuR9AEXuA6ksNyn4dkLiB3pUYXWUGZIKtMJg6ICYd6mW6=w2000-rw and Dual Edge TPU Adapter - PCIe x1 Low Profile https://thumb.tildacdn.com/tild6433-3330-4536-b835-643832613436/-/resize/360x/-/format/webp/TPU_Adapter_PCIe.jpg and installed drivers for Windows!
frigate.yml:
detectors:   cpu1:     type: cpu     num_threads: 2   cpu2:     type: cpu     num_threads: 2   coral1:     type: edgetpu     device: pci:1   coral2:     type: edgetpu     device: pci:2
PCIe x1 Low Profile (COR.PCI20102.2) card is presented to the windows system as PCI and not as USB and therefore I cannot use it in VM because it does not allow PCI Passthrough!
1.)	I turned on the VT-x feature in the bios.
2.)	Recognized hardware from Windows I can see that windows recognizes coral and VT-x function.
3.)	Could not turn on "Enable Nested VT-x/AMD-V" in VM! So I searched the forums for possible solutions and found the "nested-hw-virt on" command, which I ran in the CMD (administrator) in the directory where the Oracle VM is installed
4.)	After restarting the computer, I checked the " Enable Nested VT-x/AMD-V " setting in the VM and it was turned on
5.)	Even before starting vm, it can be seen that the function is on/supported
6.)	I have to explain to you that I know nothing about Linux.
7.)	So I don't know how to show the PCIe gateway configurations!
8.)	In Home Assitent terminal i ran "intel_iommu=on"
9.)	I try to run "lspci -vv" with an error
HOW TO ENABLE EDGETPU PCI-e Passthrough in VM?

First off this repo is for the home assistant integration, https://github.com/blakeblackshear/frigate is for the actual frigate repo.
Also I don't believe you can have CPU detectors and coral detectors running at the same time. Are you actually seeing errors or what happens when you try to run with just PCIe coral running as detector?

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [2022-06-02 23:59:49] frigate.app                    INFO    : Starting Frigate (0.10.1-83481af) [2022-06-02 23:59:49] frigate.app                    INFO    : Creating directory: /tmp/cache Starting migrations [2022-06-02 23:59:49] peewee_migrate                 INFO    : Starting migrations There is nothing to migrate [2022-06-02 23:59:49] peewee_migrate                 INFO    : There is nothing to migrate [2022-06-02 23:59:49] detector.coral1                INFO    : Starting detection process: 213 [2022-06-02 23:59:49] frigate.edgetpu                INFO    : Attempting to load TPU as pci:1 [2022-06-02 23:59:49] frigate.app                    INFO    : Output process started: 216 [2022-06-02 23:59:49] frigate.edgetpu                ERROR   : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. Process detector:coral1: Traceback (most recent call last):   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate     delegate = Delegate(library, options)   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in __init__     raise ValueError(capture.message) ValueError During handling of the above exception, another exception occurred: Traceback (most recent call last):   File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap     self.run()   File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run     self._target(*self._args, **self._kwargs)   File "/opt/frigate/frigate/edgetpu.py", line 136, in run_detector     object_detector = LocalObjectDetector(   File "/opt/frigate/frigate/edgetpu.py", line 44, in __init__     edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate     raise ValueError('Failed to load delegate from {}\n{}'.format( ValueError: Failed to load delegate from libedgetpu.so.1.0 [2022-06-02 23:59:49] ws4py                          INFO    : Using epoll [2022-06-02 23:59:49] detector.coral2                INFO    : Starting detection process: 215 [2022-06-02 23:59:49] frigate.edgetpu                INFO    : Attempting to load TPU as pci:2 [2022-06-02 23:59:49] frigate.app                    INFO    : Camera processor started for jedilnica: 223 [2022-06-02 23:59:49] frigate.app                    INFO    : Capture process started for jedilnica: 229 Process detector:coral2: [2022-06-02 23:59:49] frigate.edgetpu                ERROR   : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. Traceback (most recent call last):   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate     delegate = Delegate(library, options)   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in __init__     raise ValueError(capture.message) ValueError During handling of the above exception, another exception occurred: Traceback (most recent call last):   File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap     self.run()   File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run     self._target(*self._args, **self._kwargs)   File "/opt/frigate/frigate/edgetpu.py", line 136, in run_detector     object_detector = LocalObjectDetector(   File "/opt/frigate/frigate/edgetpu.py", line 44, in __init__     edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate     raise ValueError('Failed to load delegate from {}\n{}'.format( ValueError: Failed to load delegate from libedgetpu.so.1.0 [2022-06-02 23:59:49] ws4py                          INFO    : Using epoll [2022-06-03 00:00:09] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting frigate... [2022-06-03 00:00:09] frigate.app                    INFO    : Stopping... [2022-06-03 00:00:09] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting frigate... [2022-06-03 00:00:09] frigate.app                    INFO    : Stopping...

First off this repo is for the home assistant integration, https://github.com/blakeblackshear/frigate is for the actual frigate repo.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [2022-06-02 23:59:49] frigate.app                    INFO    : Starting Frigate (0.10.1-83481af) [2022-06-02 23:59:49] frigate.app                    INFO    : Creating directory: /tmp/cache Starting migrations [2022-06-02 23:59:49] peewee_migrate                 INFO    : Starting migrations There is nothing to migrate [2022-06-02 23:59:49] peewee_migrate                 INFO    : There is nothing to migrate [2022-06-02 23:59:49] detector.coral1                INFO    : Starting detection process: 213 [2022-06-02 23:59:49] frigate.edgetpu                INFO    : Attempting to load TPU as pci:1 [2022-06-02 23:59:49] frigate.app                    INFO    : Output process started: 216 [2022-06-02 23:59:49] frigate.edgetpu                ERROR   : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. Process detector:coral1: Traceback (most recent call last):   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate     delegate = Delegate(library, options)   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in __init__     raise ValueError(capture.message) ValueError During handling of the above exception, another exception occurred: Traceback (most recent call last):   File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap     self.run()   File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run     self._target(*self._args, **self._kwargs)   File "/opt/frigate/frigate/edgetpu.py", line 136, in run_detector     object_detector = LocalObjectDetector(   File "/opt/frigate/frigate/edgetpu.py", line 44, in __init__     edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate     raise ValueError('Failed to load delegate from {}\n{}'.format( ValueError: Failed to load delegate from libedgetpu.so.1.0 [2022-06-02 23:59:49] ws4py                          INFO    : Using epoll [2022-06-02 23:59:49] detector.coral2                INFO    : Starting detection process: 215 [2022-06-02 23:59:49] frigate.edgetpu                INFO    : Attempting to load TPU as pci:2 [2022-06-02 23:59:49] frigate.app                    INFO    : Camera processor started for jedilnica: 223 [2022-06-02 23:59:49] frigate.app                    INFO    : Capture process started for jedilnica: 229 Process detector:coral2: [2022-06-02 23:59:49] frigate.edgetpu                ERROR   : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. Traceback (most recent call last):   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate     delegate = Delegate(library, options)   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in __init__     raise ValueError(capture.message) ValueError During handling of the above exception, another exception occurred: Traceback (most recent call last):   File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap     self.run()   File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run     self._target(*self._args, **self._kwargs)   File "/opt/frigate/frigate/edgetpu.py", line 136, in run_detector     object_detector = LocalObjectDetector(   File "/opt/frigate/frigate/edgetpu.py", line 44, in __init__     edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)   File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate     raise ValueError('Failed to load delegate from {}\n{}'.format( ValueError: Failed to load delegate from libedgetpu.so.1.0 [2022-06-02 23:59:49] ws4py                          INFO    : Using epoll [2022-06-03 00:00:09] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting frigate... [2022-06-03 00:00:09] frigate.app                    INFO    : Stopping... [2022-06-03 00:00:09] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting frigate... [2022-06-03 00:00:09] frigate.app                    INFO    : Stopping...

This is not a Home Assistant issue. Please open a bug in the correct repo (https://github.com/blakeblackshear/frigate) to maximize the odds someone knows how to help you.


[Do not merge - only in case of emergency] rollback the integration live content-store to just the mongo version

As I'm away until August 14th, and the rollout of dual-running on mongo & postgres for the integration live content-store had to be split across several PRs (#1213 , #1215 and #1216), this is a single draft PR to use in case of emergency, which will revert those 3 in one go

closing un-merged - we're extremely unlikely to revert this now, it's well settled-in


example path

Description
I am installing jax and running a simple example for the first time.  I am on and have installed the nightly JAX via pip3. (This error occurs if I also install stable jax via pip3.) I am running an up-to-date Ubuntu 22.04.4 LTS using cuda12.
python3 ./examples/mnist_classifier_fromscratch.py

Traceback (most recent call last):
  File "~/jax/./examples/mnist_classifier_fromscratch.py", line 28, in <module>
    from examples import datasets
ModuleNotFoundError: No module named 'examples'

Modifying the example appears to resolve the issue:
import os
import sys
sys.path.append(os.path.dirname(os.path.dirname(os.path.abspath(__file__))))
from examples import datasets

The jax git repo I am working with is a fresh clone from this morning:
commit ff3db9b3a1bd19154769c2f72cf88593a52d8eb5 (HEAD -> main, origin/main, origin/HEAD)
Date:   Tue May 28 07:59:31 2024 -0700

System info (python version, jaxlib version, accelerator, etc.)
jax:    0.4.29.dev20240528+ff3db9b3a
jaxlib: 0.4.29.dev20240528
numpy:  1.26.4
python: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
jax.devices (1 total, 1 local): [cuda(id=0)]
process_count: 1
platform: uname_result(system='Linux', node='c', release='6.5.0-35-generic', version='#35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May  7 09:00:52 UTC 2', machine='x86_64')
$ nvidia-smi
Tue May 28 09:08:46 2024
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.161.08             Driver Version: 535.161.08   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce RTX 4070        On  | 00000000:03:00.0  On |                  N/A |
|  0%   38C    P2              16W / 200W |    470MiB / 12282MiB |      2%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      1903      G   /usr/lib/xorg/Xorg                          106MiB |
|    0   N/A  N/A      2062      G   /usr/bin/gnome-shell                         62MiB |
|    0   N/A  N/A      6587      G   ...irefox/4259/usr/lib/firefox/firefox      132MiB |
|    0   N/A  N/A      8811      C   python3                                     154MiB |
+---------------------------------------------------------------------------------------+

This has to do with the relative position of the two files.
As they are right now datasets.py and mnist_classifier_fromscratch.py are under the same folder. I might be missing something here but if you move the mnist_classifier_fromscratch.py outside of the examples folder, it works as intended.
If you want to keep the two files in the same folder then in mnist_classifier_fromscratch.py change;
from examples import datasets

to
from datasets

Something is telling me that I am missing something here since all examples that use the datasets.py are importing it with the first way and the author was able to run them just fine as they are.


DG Dirichlet Boundary conditions for interior faces

Hello, I am trying to apply Dirichlet boundary conditions on an internal surface in a DG implementation. While I can apply such conditions to the boundary of the system, nothing I do seems to apply it to the internal face. For reference, this is how I am trying to implement this, where bdr_array_V0 and bdr_array_V1 are the marker arrays for the external boundaries:
   BilinearForm *a = new BilinearForm(fespace);

   a->AddDomainIntegrator(new DiffusionIntegrator(one));
   b->AddDomainIntegrator(new DomainLFIntegrator(zero));

   a->AddInteriorFaceIntegrator(new DGDiffusionIntegrator(one, sigma, kappa));
   a->AddBdrFaceIntegrator(new DGDiffusionIntegrator(one, sigma, kappa), bdr_array_V1);
   a->AddBdrFaceIntegrator(new DGDiffusionIntegrator(one, sigma, kappa), bdr_array_V0);

   b->AddBdrFaceIntegrator(new DGDirichletLFIntegrator(one, sigma, kappa),bdr_array_V1);
   b->AddBdrFaceIntegrator(new DGDirichletLFIntegrator(zero, sigma, kappa),bdr_array_V0);

   b->AddInteriorFaceIntegrator(new DGDirichletLFIntegrator(one, sigma, kappa));

   a->Assemble();
   a->Finalize();
   b->Assemble();

The problematic line is when I add the DGDirichletLFIntegrator to b and assemble it. I get the following error at runtime:
LinearFormIntegrator::AssembleRHSElementVect(...)
It seems that this functionality is somehow not implemeted? Or perhaps I am using the DG integrators incorrectly, which is possible due to me being new to this. I tried to bypass this issue using the AddInternalBoundaryFaceIntegrator method implemented in #3777, but stumbled upon the same problem. All in all, is there an issue with how I implemented the conditions in the code snippet above, and if not, is there a way to implement Dirichlet boundary conditions in interior faces under DG? Thank you!

Hi @Heinrich-BR, the DGDirichletLFIntegrator is not implemented for internal faces (that use info from the 2 sides), it's only implemented for boundary faces (that use only 1 side). The function that aborts is this:
void LinearFormIntegrator::AssembleRHSElementVect(
   const FiniteElement &el1, const FiniteElement &el2,
   FaceElementTransformations &Tr, Vector &elvect)
{
   mfem_error("LinearFormIntegrator::AssembleRHSElementVect(...)");
}

I'm not sure what you want to achieve, and whether doing it weakly is the best approach, but if you want to use the DG integrator, you'll have to implement the above.


Add operating system name to Mac OS X package

For PowerShell Core distribution packages, every other package has the operating system name in the file name, except for the Apple Mac OS X one, with a .pkg file extension.
I'd suggesting adding the operating system into the package's file name, to make it clear which OS it's intended for.

Cheers,
Trevor Sullivan
Docker Captain
Microsoft MVP: Cloud & Data Center Management
https://trevorsullivan.net
https://twitter.com/pcgeek86

This has to be done by someone with access to the builds correct?  I see that the appveyor builds publish most of the installation artifacts.  I looked over the code, and nothing in there packages it up as far as I can see.


Inactive organization with the 28 days trial organization

Hi,
I'm trying to use the "28 days trial organization" but the current subscription has the status inactive.
Also, I cannot create a project with this organization because I have the error : "500 Internal Server Error
We're sorry, but something went wrong on our end. Our team has been notified and we're working to fix it as soon as possible."
Can you help me please ?
Thank you

Hey! Did you contact our support? The issue queue is more for speciifc code related issues rather than operations.


Need duplicate conditional formatting when duplicate row

Sorry,
Is the duplicate conditional formatting available?
If i am duplicate the row, the conditional formatting is not duplicated.
There may be other features I could use that I am not aware of.
Thank's,

This library doesn't support to copy row with conditional format style currently, you can set a new range of conditional format rules which include copied destination row.

@xuri , thank's for your answer.
Can you explain to me which method can i use to read existing conditional format?

Sorry for my late reply, 18 months later. I've just merged pull request #1315, which resolves issue #827. Now we can get conditional formatting settings by the GetConditionalFormats function. Please upgrade to the master branch code, and this feature will be released in the next version.


Use fallible allocation APIs

For the implementation of Write for Vec<u8>, use Vec::try_reserve
to try and allocate memory before copying a slice into the Vec. If a
TryReserveError is returned, bubble that up to the caller instead of
letting alloc do a process abort.
If an allocation fails, return Error::OutOfMemory.
This commit removes derive(Copy) from the error type in this crate
because the inner TryReserveError in the OutOfMemory variant is not
Copy.

Sorry to merge this change without pinging you @x-hgg-x. I wasn't sure you had accepted the invite yet. If you'd like to do a post-merge code review, I'm open to feedback on this PR.


[BUG] Broken link to GraphQL tutorial

Describe the bug
It's a documentation bug, not a software bug :wink:
Unfortunately the link for GraphQL tutorial is broken: https://fastapi.tiangolo.com/tutorial/graphql/
References:

https://fastapi.tiangolo.com/release-notes/#061
PR #48

Best regards.

Thanks! This was fixed by @sattosan in #1052

Links mentioned working perfectly.
Closing issue.


Error running topswitch_update.sh

Changing top app of station vb-hb-test-1 to hb_test_b

Running custom management command: '~/.config/dockapp/topswitch.sh hb_test_b' on station 'vb-hb-test-1'...

Running command: 'exit 0' on station 'vb-hb-test-1' via 'SSH'...
Running command: 'test -x ~/.config/dockapp/topswitch.sh && exit 0 || exit 1' on station 'vb-hb-test-1' via 'SSH'...

Running command: '~/.config/dockapp/topswitch.sh hb_test_b' on station 'vb-hb-test-1' via 'SSH'...

Stopping dockapp_hb_test_a_1 ...

Stopping dockapp_hb_test_a_1 ... done

Not including one-off containers created by `docker-compose run`.
To include them, use `docker-compose rm --all`.
This will be the default behavior in the next version of Compose.

Removing dockapp_hb_test_a_1 ...

Removing dockapp_hb_test_a_1 ... done

Going to remove dockapp_hb_test_a_1

Creating dockapp_hb_test_b_1

mkdir: cannot create directory './~/': Read-only file system

./~/lastapp.cfg: No such file or directory

ERROR: could not get 'vb-hb-test-1:/tmp/lastapp.cfg'!

topswitch_update.sh returned 0. Stopping station vb-hb-test-1 cancelled.

The last line of the dump is wrong but you can disregard it. It should read:
topswitch_update.sh returned XX. Changing top app of station vb-hb-test-1 cancelled.

The same problem occurs when calling default_update.sh
4. Call default_update.sh

Running custom management command: '~/.config/dockapp/default.sh ' on station 'vb-hb-test-3'...

Running command: 'test -x ~/.config/dockapp/default.sh && exit 0 || exit 1' on station 'vb-hb-test-3' via 'SSH'...

Running command: 'exit 0' on station 'vb-hb-test-3' via 'SSH'...

Running command: '~/.config/dockapp/default.sh' on station 'vb-hb-test-3' via 'SSH'...

Starting Background Service: 'omd_agent'...

Creating dockapp_omd_agent_1

Front GUI Application: 'hb_test_c'...

Creating dockapp_hb_test_c_1

mkdir: cannot create directory './~/': Read-only file system

./~/lastapp.cfg: No such file or directory

ERROR: could not get 'vb-hb-test-3:/tmp/lastapp.cfg'!

default_update.sh returned 0. Starting station vb-hb-test-3 cancelled.

my bad (untested minor change made /DOCKAPP/STATIONS/ read-only for the case of execution via make check)!
should be fixed now..?

should be fixed now..?

now is not a valid git revision. Please always reference the commit that fixes the issue.

Please always reference the commit that fixes the issue.

I do now, this issue is really old.

now is not a valid git revision.

Was fixed in (or slightly prior to) https://github.com/hilbert/hilbert-docker-images/releases/tag/v0.1.0


Add filepath mode none to Destination

Hello,
I do not see spec.filepath.mode in the Destination template, would it be possible to have that added so it can be configured for the destinations?
From the Kratix docs on Destinations
spec:
  # Optional, defaults to `nestedByMetadata`
  # The mode to use when writing to the State Store, valid options are:
  #   - nestedByMetadata: Writes to the State Store in a nested structure
  #   - none: Writes to the State Store in a flat structure
  filepath:
    mode: nestedByMetadata | none

hey @tdiaque
thanks for raising it to our attention; we have now released a new version of the chart that includes the filepath!


Additional styles

Though these might be useful too.
Like the idea of auto width as a standard - but will leave that decision to you.

Some great additions, thank you 😄. Auto width as default sounds good to me.


Notify when new message is received

Is your feature request related to a problem? Please describe.
I want to know if a new message is received without needing to refresh my page.
Describe the solution you'd like
Something should do something in the background.
Describe alternatives you've considered
Hitting F5, or clicking 'Check Messages'
Additional context
N/A

Closing due to archiving repository


Upgrade nokogiri & devise gems

Upgraded the gems due to security vulnerabilities:
devise: http://blog.plataformatec.com.br/2016/01/improve-remember-me-cookie-expiration-in-devise/
nokogiri: https://groups.google.com/forum/#!topic/ruby-security-ann/Dy7YiKb_pMM

Looks fine, merge when green...

:+1: if tests pass :)


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

@bryant1410,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@bryant1410, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

Thanks for the update!


Event Pagination

This PR implements pagination for the events tab. The page defaults to show upcoming events for the next month, with buttons for selecting previous or next months. You can also search all events, as long as your search is > 2 characters and searches are also limited through debouncing.
Major Changes
Database and Model Changes

Added the EventPaginationParams model, which includes pagination parameters for specifying a start and end date, ascending/descending, order by, and filter
Added two more events as demo data for testing this feature

API Changes
Exposes the following API to the Angular Frontend via FastAPI:

GET api/events/paginate: returns a paginated list of events based on the specified pagination parameters

Service Changes

Added the list() function to the backend EventService to query and paginate events based on the parameters passed in from the API call

Frontend

Added corresponding frontend model and service function
Updated EventPageComponent to include the buttons for navigating between the previous and next months of events
Updated search bar on this page to include debouncing and send search requests through API calls rather than filtering on the frontend
Remove eventFilterPipe now that filtering is done on the backend

Picture:

Testing
Backend: Added a new PyTest to test the list() function. Confirm 100% passing by running pytest
Frontend:

Run honcho start and python3 -m backend.script.reset_demo
Navigate to the Events tab and see that the default dates are set to Today - One Month from Today. There should be four events listed in ascending order
Select Previous Month, and date range at the top should change to last month. There should be two events listed in descending order
Search for 'ca.' Nothing should happen. Now search for 'cads'. Four events should appear. Clearing the search bar should reset data to the correct date paginated view.

Future Considerations

Put pagination stuff into a widget for reusability, if that is possible. Wasn't sure how to to neatly and properly do that here since there were interactions with routes and other things.
Note: I am no longer using the eventResolver; I was not sure if I should delete it or change my code to incorporate it back in

@atoneyd / @jadekeegan / @KrisJordan, with #276 open, I will close this PR. Great work getting this started !!


Add PSTypeName Support for Import-Csv and ConvertFrom-Csv

closes #5134

Adds PSTypeName preservation on Import-Csv and ConvertFrom-Csv

A note for reviewers: the logic for adding the type name was moved to after the object's properties are populated to prevent Cannot add a member with the name "<PorpertyName>" because a member with that name already exists errors during object serialization.

@SteveL-MSFT CI Travis don't report status - can PG investigate the issue?

@iSazonov seems to be an ongoing issue with Travis-CI.  Looking at the actual results, it passed on both macOS and Linux, so we are good.

@SteveL-MSFT It seems I haven't permission to manually merge.

@SteveL-MSFT It seems the problem with CI Travis coming from #5249

@markekraus can you rebase and pick up #5249?

Rebased.

@SteveL-MSFT *shrugs. Rebased and the Travis CI tests passed, but they still are not updating the PR to reflect that.

Merging with macOS still not finished.  Talked to other maintainers and we think the risk is low.


Edits for creating UFO test files and AMV updates in x0045.

Update CRTM coefs path in "analyzer" (04/2022)
Major updates in  setuprad.f90 and crtm_interface.f90

Updated from GEOS5.29 in order to write out various diagnostics.  (04/2022)
Write out tropopause pressure  (05/09/2022)
Write out obs error in physical space for CrIS, IASI, and AIRS. varinv0 = varinv for other radiance data (Wei Gu). (05/17/2022)
Write out the original surface(1)%ice_temperature (ice_temperature_0). (05/19/2022)
The surface(1)%ice_temperature may be altered by CRTM and creates discrepancy between UFO and GSI hofx values.
Write out original Water_Fraction,  Land_Fraction, Ice_Fraction, and Snow_Fraction. (06/14/2022)
Write out "Forecast_adjusted_clear" for validation. (06/14/2022)
Updated setupw.f90 in which atmospheric pressure levels are saved along with other variable. (06/19/2022)

Added "half_goesr_err" in gsimod.F90, and qcmod.f90 which was updated in x0045,  which is not necessary for producing UFO testing files (03/2022).

GPS data can be converted to IODA files after these updates are added in GSI.  However, stationary data in "conv_pwnc4" and "TCP" data in "conv_tcp" cannot be converted.  Reasons are unknown at moment.

I don't understand why any of these changes are non-zero diff to what we presently have in 5.29.4 - I suggest working on these changes to make sure they are zero-diff to the what was used to x0046a; I can only approve when this is the case. Also, I don't understand why you are changing the knob I put in setupw - half_goes_err - that was put in to avoid messing up w/ whatever NCEP had done. It needs to be in.

These updates were merged into a new branch bugfix/rtodling/jjin_netcdf4_ufo and eventually into the develop branch by @rtodling . Therefore this PR is closed.


photos but not obs licensing on 'Yes, license my photos so scientists can use my data!'

http://www.inaturalist.org/observations/new?flickr_photo_id=6483815001&project_id=871&taxon_id=54541&welcome=true
'Yes, license my photos so scientists can use my data!' should license obs/sounds/photos not just photos, maybe reword:
Yes, license my content so scientists can use my data!'

I suspect this old issue can be closed, but not sure. Found it when I searched for my own issue about licenses!

now says  'Yes, license my photos, sounds & observations so scientists can use my data!' so closing this because it covers sounds