BLE stack can get stuck in connected state despite connection failure

I'm periodically connecting to a Zephyr sensor (nrf52840) using a central device (esp32-c3). The central is rather unstable due to WiFi/BT coexistence, so it drops the connection unexpectedly a lot. I noticed that the Zephyr device does not recover nicely from this, if it had an active connection when the error occurs.
It gets detected on a low level, but the information does not get propagated it seems. It logs the following:
[00:41:33.821,014] <wrn> bt_hci_core: opcode 0x2013 status 0x02

I.e. it tries to update the connection (op=0x2013) but gets the error "NO CONNECTION" (0x02). But no one picks this up. In particular, I checked the file subsys/bluetooth/host/conn.c which calls send_conn_le_param_update(conn, param) inside its deferred work handler, but it never checks the return value so it obviously does not do anything with the information.

The send_conn_le_param_update() will only be called if the connection is not in the disconnected state, so most likely there is a missing state transition somewhere. Can you share some logs that shows what happens before the failed connection parameter update?

Sorry, not really - first of all this is pretty hard to reproduce but basically there was no other indications that something went wrong. Everything looked fine until that opcode warning. Maybe I'd have more info if I had higher log levels set, but as I said it's not easy to reproduce.

@tautologyclub could you please add a couple of details:

When you say that Zephyr doesn't handle this correctly, what do you mean? Is the BLE stack stuck after?
Can you please provide a sniffer trace, just like here
This seems like the opposite situation to #48813, with the L2CAP procedure here being initiated by the local device instead of the remote peer, but in that case it was only an annoyance to see the message printed

@carlescufi

Yeah it's stuck in a perpetually connected state (i.e. the disconnected callbacks never trigger etc but the other side has disconnected)
I wish I could and I will if we manage to reproduce it consistently.
Yeah this is more than an annoyance - luckily we got a hardware watchdog that gets us out of this but it's def not good

But yeah it seems like a pretty easy fix to me - just don't ignore the retval of send_conn_le_param_update() in the work handler? Yall feel like enlightening me as to why this is not a good solution?

I think those are two separate issues. The return value of send_conn_le_param_update shouldn't hang the connection in any case.
Could you try the linked branch and report back if it fixes the issue?
I'll still try to reproduce it on my end to see if we're not just masking a deeper issue, but that could take some time as I have other bug I have to address first.

@jori-nordic What I mean is that knowledge of this hanged connection state is propagated through that retval, so we could use it to escape the state, if we checked the retval. Are you saying that "this is a solution but not the correct solution" or are you saying that this is not a solution at all?

I'm saying this is (maybe) a solution, but likely not the correct (or long-term) solution.
Problem is that we're in a work handler so we can't really propagate the error. The only thing we can do as you say is check it and execute some procedure (like explicitly disconnect the connection).
But that ideally shouldn't be necessary and the device should know it's disconnected when the supervision timeout fires in the controller.

Maybe related to #44998

I haven't seen this for a while, closing. @tautologyclub feel free to re-open the ticket if it happens again.

Hello, I have the exact same scenario as @tautologyclub. I am using the nRF52840 as a peripheral and the ESP32-C3 as a central, and they are connected over BLE. The ESP32_C3 board is also using WiFi. I am noticing that the bt_conn_cb .disconnected callback does not always trigger on the nRF52840 when the ESP32-C3 is turned off (to save power). I do not get any warnings or errors from the BLE stack. Does anyone with a little bit more knowledge on this topic have any clue on why bt_conn_cb .disconnected is called sometimes, but not always?

@Tjoms99 You really don't get any errors or warnings from the stack? Could you check that CONFIG_LOG=y.
Could you add CONFIG_BT_CONN_LOG_LEVEL_DBG=y to generate some logs?
Also having CONFIG_BT_MAX_CONN=1 will help, as if the connection object is not freed, the next connection attempt from the ESP should fail with some errors that can help us debug more.
Something else that could help us is getting sniffer log. You can use The nordic sniffer for gathering a trace, provided you have no encryption. If you're using encryption there is another config to dump the keys for decrypting the trace: CONFIG_BT_LOG_SNIFFER_INFO=y.
Some other questions:

are you running a standard sample, or is this a custom app? If custom app, can you reproduce it using a peripheral sample?
are you using the Zephyr LL or the Softdevice Controller?

@jori-nordic Sorry for the confusion, the nRF52840 is the central (client) and the ESP32-C3 is the peripheral (server), got it mixed up. Regardless, the application did not produce any logs even though I had CONFIG_BT_CONN_LOG_LEVEL_DBG=y and I could not reproduce the same behavior using a peripheral sample, but I managed to pinpoint the problem.
This is a custom application with the purpose of relaying information sent over BLE to a RS485 bus and it is mostly interrupt driven. Long story short: the nRF52 has subscribed to ESP32's characteristics and is notified of any changes (interrupt-driven), and then calls rs485_write(message) inside a notify function. The rs485_write(message) function has a polling mechanism (bad) to check if the RS485 bus can be written to:
    // Wait for the RS485 bus to become available.
    while (uart_get_is_busy())
    {
        LOG_DBG("UART busy");
        k_msleep(30);
    }
    rs485_tx_enable();
    uart_write(message);
    rs485_tx_disable();

Once in a blue moon, when a BLE notification arrives, the RS485 bus is busy, and the ESP32 is turned off during nRF52's  k_msleep(30), the bt_conn_cb.disconnected is never called on the nRF52. Removing the polling feature solved the problem.
PS: I am using the Zephyr LL.

Both the GATT notify callback and the disconnected callback are called from the Bluetooth RX thread. So if you do blocking operations in the notify callback that will block the disconnected callback from firing as well. For how long are you blocking in the notify callback? Do you get the disconnected callback once you return from the notify callback?

@hermabe That makes sense. The notify callback   can block for 100's of milliseconds in the worst case scenario, and it can not block at all (which is usually the case).
The disconnected callback is not called if the notify callback is polling, even after it returns. I am not sure if this is the case all the time; Polling for 30ms vs 300ms might be different. My solution to this might be to offload the work in the notify callback and schedule it in a work queue instead.
I am not able to give specifics until late next week (due to vacation).

Removing the stale label until we get an update from @Tjoms99

@Tjoms99 tried and failed to reproduce your issue in https://github.com/jori-nordic/zephyr/blob/disconnect-cb/tests/bsim/bluetooth/host/misc/disconnect/dut/src/main.c#L235
Do you have anything else going on in that app? other cooperative threads, other users of the system workqueue, etc..

@jori-nordic There was something else going on, have fixed the issue. In short, the MCU the BLE code was running on also communicates with another MCU over UART. When the BLE notify callback was triggered, the BLE MCU would ask the other MCU if it is present before sending data to it. If the MCU never sent an answer, the notify callback would never return (stuck in a while loop), meaning that the BLE disconnect callback would never have a chance to run.

Good to know, I'll close this again then :+1:


Trace when editing an incident

Describe the bug
Getting an error message to console when editing an existing incident in UI
To Reproduce
Steps to reproduce the behavior:

Set up Dispatch with minimal set of plugins (basic auth + dispatch-* ones), master branch (latest)
Create a document, service etc, then finally an incident
Edit that incident, for example its description, click the save icon
Get the error (the changes are saved and applied, though, so it's ok)

Expected behavior
Changes are applied, no errors occur
Additional context
edit_incident.log
I have only one user registered - I log in as it.
Also I have two Individuals - one is that user (created automatically, it seems; has the same name as its email), and the one I create manually. The two have different email addresses, if that matters. I try specifying the 'manual' user for the incident, fill in the fields, except for the last threee (terms, tags, duplicates), nothing special.
Oh! And found a related thing, maybe, while writing this. I put the one created manually as the reporter and commander, and have my log-in user put as reporter and commander instead. Can't change to the other user, getting the same trace.

Looks like we didn't pass a var to the dispatch core contact plugin. #608 should resolve this once it gets reviewed and merged. Thanks for reporting!

Thanks! Yes, now it works properly


issue-17089: Add -clean option for -print_certs pkcs7

Fixes #17089
CLA: trivial

Unfortunately this is outside of what would be acceptable with CLA: trivial. Can you please submit a regular CLA?
https://www.openssl.org/policies/cla.html

Hi!
Okay, I just sent the CLA. Should I remove the CLA: trivial from the commit message?
In addition, I would like to discuss some of the approaches we can follow to accomplish this small change.
What of the following options do you consider to fit better?

An additional flag -clean (like the commit in this PR) that outputs a "clean" version?
An additional flag too -print_certs_clean which the same result before?
In my opinion, the first option could be useful for the future use in another flags.

This is my first contribution in an open-source project, i really appreciate any advice.

Yes, please remove the CLA: trivial (you can do that with git commit --amend).
As for the option name - I'd consider using -quiet - we have this option with other commands.


fix(behavior_path_planner): change the condition of skip_smooth_goal_connection

Signed-off-by: jack.song<EMAIL_ADDRESS>Description
The intention of the "skipSmoothGoalConnection" is that the connection target point is not used in the "PullOver" scenario.
The current judgment condition will make the “pullover” scenario tenable as long as it is registered (whether the pullover scenario is running or not). Because the variable "is_waiting_approval" will be true after all models are registered. Therefore, when the pullover scenario is registered, other scenarios cannot have the "modifypathforsmoothgoalconnection" function.

After changing conditions：

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@shulanbushangshu
thank you very much for your PR. I'll check it.

It needs to skip goal connection also when pull over module is waiting_approval.
This problem is due to the is_waiting_approval state is wrong, so I fixed it in https://github.com/autowarefoundation/autoware.universe/pull/1326.


🐛 pkg/apis/test/cel: fix closure reference

Summary
As findCEL can continue recursing the path three,
The referenced pointers in the returned validator can point to the wrong nodes.

/lgtm
/approve


Unexpected behaviour for ibmqx5

Output for a repetition code run gives significantly different behaviour than expected.
Expected Behavior
Repetition codes were run on ibmqx5 with an encoded bit value of 0. The output should be 0 on all qubits. Given noise levels and previous results, it can be expected that 1 will instead be output for each qubit for 10-20% of the samples. This is seen for codes of size d=3 to d=7 using the implementation here.
Current Behavior
For a d=8 code, it is found that some qubits output 1 for 50-80% of the samples. A comparison of recent runs showing the expected behaviour for d=7, and the unexpected behaviour for d=8, can be found here.
Possible Solution
If this is noise, a solution is obviously outside the scope of the SDK. However, it could be that something strange is going on in the process of taking the QASM and turning it into a pulse sequence. I'd suggest looking further down the stack for a possible bug.
Steps to Reproduce (for bugs)
This issue relates to jobs created by this file. A stripped down version focussed on the job with the issue can be found here. Results for runs with and without the issue are compared here.
Context

Your Environment

Python 3.6.0
IBMQuantumExperience      1.9.0
qiskit                    0.4.14

I think we close this as its not in the sdk. But i let Hanhee and you debug to determine if it is the pulse generating code.


Bug: allOf breaks mock generator

openapi: '3.0.0'
info:
  version: 1.0.0
  title: Swagger Petstore
  license:
    name: MIT
servers:
  - url: http://petstore.swagger.io/v1
paths:
  /pets:
    post:
      summary: Create a pet
      operationId: createPets
      responses:
        '200':
          description: Created Pet
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Pet'
components:
  schemas:
    Id:
      type: number
    Pet:
      type: object
      properties:
        someField:
          description: unexpected error
          allOf: # PAY ATTENTION TO THIS LINE
            - $ref: '#/components/schemas/Id'

produces invalid mock creator:
// With allOf:
// ERROR: Parsing error: ',' expected
export const getCreatePetsMock = () => ({someField: faker.helpers.randomize([{faker.datatype.number()}, undefined])})

//Without allOf:
export const getCreatePetsMock = () => ({someField: faker.helpers.randomize([faker.datatype.number(), undefined])})

@yekver I ran into a similar issue, but I could not reproduce this bug with the OpenAPI spec you provided.
However, I was able to reproduce this bug with this spec:
openapi: 3.0.3
info:
  version: 1.0.0
  title: AllOf
paths:
  /workingendpoint:
    get:
      summary: An endpoint that uses a working demo of allOf
      operationId: workingEndpoint
      tags:
        - working
      responses:
        '200':
          description: Get working schema
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Working'
  /brokenendpoint:
    get:
      summary: An endpoint that uses a broken demo of allOf
      operationId: brokenEndpoint
      tags:
        - broken
      responses:
        '200':
          description: Get broken schema
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Broken'
components:
  schemas:
    CommonProperties:
      type: object
      description: The first set of common properties.
      properties:
        commonPropsField1:
          type: string
          description: 'Common property field #1'
        commonPropsField2:
          type: string
          description: 'Common property field #2'
    Working:
      allOf:
        - $ref: '#/components/schemas/CommonProperties'
        - type: object
          description: A working example of using allOf.
          properties:
            workingField:
              type: string
              description: 'Working field'
    Broken:
      allOf:
        - $ref: '#/components/schemas/CommonProperties'
        - type: object
          description: A broken example of using allOf.

The complete demonstration of the bug can be found here: https://github.com/cowofevil/orval-bug-362

fixed thanks for the examples @cowofevil & @yekver. Will be in the next release

Released with 6.9.0


Render private documentation members, other fixes

Summary
Render private members of documentation (#82) and misc fixes (#88).
Details and comments

@derivation sorry you should have write access now.


Venv identifier

Codecov Report

Merging #13844 into main will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main   #13844      +/-   ##
==========================================
+ Coverage   59.93%   59.96%   +0.03%
==========================================
  Files         684      686       +2
  Lines       37962    38014      +52
  Branches     5466     5474       +8
==========================================
+ Hits        22753    22796      +43
+ Misses      14048    14040       -8
- Partials     1161     1178      +17

Impacted Files
Coverage Δ

...pythonEnvironments/common/environmentIdentifier.ts
86.66% <100.00%> (-3.81%)
:arrow_down:

.../pythonEnvironments/common/externalDependencies.ts
73.33% <100.00%> (+23.33%)
:arrow_up:

...onments/discovery/locators/services/venvLocator.ts
100.00% <100.00%> (ø)

src/client/datascience/crossProcessLock.ts
79.41% <0.00%> (-11.77%)
:arrow_down:

src/client/common/utils/platform.ts
56.00% <0.00%> (-8.00%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

src/client/logging/levels.ts
61.11% <0.00%> (ø)

src/client/logging/logger.ts
62.74% <0.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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

I am not sure why there are two hygiene, and why one of them was cancelled. I am not able to get rid of it.


implement Listener::commitSnapshot to apply data in snapshot.

implement Listener::commitSnapshot to apply data in snapshot.

Logic LGTM. BTW, has this PR verified in your environment? I'll be appreciated if you add a case in NebulaListenerTest.cpp.

I have verified this PR in my testing environment, will add to case in NebulaListenerTest.cpp

Logic LGTM. BTW, has this PR verified in your environment? I'll be appreciated if you add a case in NebulaListenerTest.cpp.

I have verified this PR in my testing environment, will add to case in NebulaListenerTest.cpp

👍 , for ES?

PS: we are doing some improvement on ES. See vesoft-inc/nebula-common#530 and #460. Mainly to support build full text index on specified field.

PS: we are doing some improvement on ES. See vesoft-inc/nebula-common#530 and #460. Mainly to support build full text index on specified field.

Yes


Overview: Refactor Azure

Refactor the "Azure" overview page to use a dropdown in conjunction with tab navigation. This also removes progress bars for most cards (i.e., except 1st), and updates titles.
Mock: https://marvelapp.com/4b95ibf/screen/66066595

verified, 54ec1fef4d374c1453fdf1a996d591660260ff7c


ci: push envoy-build when ci/build_container changes

@lyft/network-team
I have worked building and pushing lyft/envoy-build into our CI process. There are two changes here to the build process that need explanation:

I created a build_image run for two reasons. First, it made logical sense to split it from the release build, as building the envoy-build image does not require anything from the bazel build. Second, it made the bazel.release build take longer than the max amount of time allowed by travis.
I had to change the language specification from cpp to minimal because building the image took more disk space than allowed on a travis run. Per a slack conversation with travis folks I discovered that using language: minimal gives us about 10GB more of disk space on the run. Changing to minimal from cpp precludes our run from canonical cpp tools, but given our move to bazel, none of those are needed for our builds to succeed.

A lyft/envoy-build image is built and pushed if the commit contains changes to the ci/build_container directory.

cc @PiotrSikora ^^^


Display a message if no results are found in the asset library

This closes https://github.com/godotengine/godot-proposals/issues/184.
Preview

Thanks!


Added git push origin master to git aliases as gpom

Hello. Thank you for your awesome tool before hand! It has been really a great aid in my productivity.
I also noticed that I'm always typing gpo master so I figured I would like to have a command like gpom which would translate immediately to git push origin master.
Also I changed the gall from git add . to git add -A.
Now, I'm not quite sure about this change. I'm relateively new to git but every time I try to do a git add . I always get a warning:
warning: You ran 'git add' with neither '-A (--all)' or '--ignore-removal',
whose behavior will change in Git 2.0 with respect to paths you removed.

I'm using git version 1.9.1 and I'm note quite sure about the difference between those two commands, so feel free to ignore that change if that's just something relating to git versions.
Anyway, thank you for your awesome work and keep rocking!

Thanks!


[User] I encountered a problem ..

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[x] I am running the latest code. Development is very rapid so there are no tagged versions as of now.
[x] I carefully followed the README.md.
[x] I searched using keywords relevant to my issue to make sure that I am creating a new issue that is not already open (or closed).
[x] I reviewed the Discussions, and have a new bug or useful enhancement to share.

Expected Behavior
Trying to run the model converter tool using
{'dim': 4096, 'multiple_of': 256, 'n_heads': 32, 'n_layers': 32, 'norm_eps': 1e-05, 'vocab_size': -1}
Namespace(dir_model='../llama.cpp/models/llama-2-7b/', ftype=1, vocab_only=0)
n_parts = 1

Processing part 0

Processing variable: tok_embeddings.weight with shape: torch.Size([32000, 4096]) and type: torch.bfloat16
Traceback (most recent call last):
  File "/Users/vivekv/software/llama-go/./convert-pth-to-ggml.py", line 181, in <module>
    main()
  File "/Users/vivekv/software/llama-go/./convert-pth-to-ggml.py", line 174, in main
    process_and_write_variables(fout, model, ftype)
  File "/Users/vivekv/software/llama-go/./convert-pth-to-ggml.py", line 109, in process_and_write_variables
    data = datao.numpy().squeeze()
           ^^^^^^^^^^^^^
TypeError: Got unsupported ScalarType BFloat16

Physical (or virtual) hardware you are using, e.g. for Linux:
running on an M1 Mac Pro

$ python3 --version

Python 3.11.4

$ make --version

GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i386-apple-darwin11.3.0

$ g++ --version

Apple clang version 14.0.3 (clang-14<IP_ADDRESS>.1)
Target: arm64-apple-darwin22.4.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

The same error, how can it be resolved?

On a Macbook Pro M2, getting the same issue. Any resolution?


QSMR images

consumes messages from a queue (jobs)
loops over jobs and start qsmr

LGTM, A bit annoying having to have (basically) copies of the Dockerfiles, with very minor differences, but it actually might be more manageable than trying to do something clever, in then long run.

I agree, it would have been nice if docker supported some kind of import statement. Another option I considered was multiple Docker files with "from" statements on local built dependency images, but perhaps more error prone considering the risk of pulling in old dependencies


html.prettyPrint does not do any indenting or line-breaking (Node 6.1.0)

System specs:

Node: 6.1.0
OSX: 10.11.5

I haven't had any luck with this:
var html = require('html');
var txt = '
AwesomeComis awesome
';
html.prettyPrint(txt, {indent_size: 2});
// result
'
AwesomeComis awesome
'

So I tried the command-line example in the README but got the same, unformatted text.

+1 for the command-line example in the README not working as expected.

I had the same problem and I went crazy to understand what I was doing wrong...
It works, it's just a wrong example in the readme file.
Try with this input to see it works:
var txt = '

Coffee

Tea

Milk

';

To format example from read.me we need to clear unformated array
line:
https://github.com/max-mapper/commonjs-html-prettyprinter/blob/master/lib/html.js#L54
var html = require('html');
var txt = '
AwesomeComis awesome
';
html.prettyPrint(txt, {unformatted: []});

this will force formatting for all html tags.


No error handling in Management service update method

Package Name: @azure/arm-apimanagement
Package Version: 5.1.1

Describe the bug
Update method does not support callback and promise is not handling error.
https://github.com/Azure/azure-sdk-for-js/blob/d4d55f73f985635bb6fcdb5a2e03a3ad289927bb/sdk/apimanagement/arm-apimanagement/src/operations/apiManagementService.ts#L82
To Reproduce
Steps to reproduce the behavior:

call the apiManagementService.update method

Expected behavior
It should support callback or should handle error by .catch() method
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@chandrakantaS I am not sure I understand your question completely, but I tried this way. it did catch the error.
    client.apiManagementService.update(resourceGroupName, serviceName, parameters).catch(E => {
        console.log("update error");
        console.log(E);
    });

Would you mind show me your code of how you call this function so that I can see what's wrong?

@qiaozha as most of modules support callback too me and my team hear expecting this update call to support the callback to. So, we were trying to call this same function like below:
client.apiManagementService.update(resourceGroupName, serviceName, parameters, (err, result) => { console.log(err); console.log(result) })
now in this case I will not get any response if any error occurs.
Hope I am clear now. Thanks

Close this issue now. If not resolved, reopen it.


📄 Zero Clause BSD

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 51.075%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
140

Relevant Lines:
288

💛  - Coveralls


Display an extra '1' on result.json file when getting the collection names for one mongo database with multiple collections

Repro Steps:

Choose one mongo account -> Create a database with 2 collections at least.
Make sure the created database shows as 'Connected' -> Configure the mongo.shell.path on User Settings.
Create a mongo scrapbook -> Execute the command 'db.getCollectionNames()' -> Check the result.json file.

Expect:
Only display the collection names without the extra '1' on the result.json file.
Actual:
Display the collection names with an extra '1' on the result.json file.

More info:
This issue doesn’t reproduce for databases with only one collection.

I'm unable to repro this.

I see this sometimes but not always.

Related to #838

Likely fixed by https://github.com/microsoft/vscode-cosmosdb/pull/1162. Not worth more investigation unless more users report this issue


Made date property public

Made the date property public with a private setter. I forgot the modifier apaprently so it was internal. This should fix that.

:+1:


Welcome views should use primary + secondary button styles

Today we have 2-3+ primary buttons used in our Explorer. Extensions can also contribute many more. As a general UI principle I think we should only feature one primary action with the rest being styled as secondary.
Before

After

We recently adopted this behavior in notifications where we ensure the first action renders as a primary button. There's no special API other than the order of the array afaik.
cc @misolori

@joaomoreno not sure if you are still the respective welcome-view owner, feel free to re-assign

Two options:

Make the first always be the primary
Enhance the current button markdown syntax to support primary/secondary

@jrieken I lean towards the first. Thoughts?

Aren't these buttons contributed from multiple extensions? How do we agree on the one and only primary button? @joaomoreno what does define the order today?

I believe @bpasero did this for notifications by simply ensuring the first defined action was rendered as primary. I don't think there was any fancy API beyond that.

I'm unsure that simply giving the primary style to the first one is a good approach. Here's what my Explorer welcome looks like, annotated by where the contributions come from:

I believe the core contributions always get top priority, followed by extensions in some order.
If I disable either the Git extension (built-in) or Remote Repositories (from Marketplace), then re-enable them (in either order) they return to positions 2 and 3. These are both published by Microsoft, so I wonder if this causes Remote Repositories to get promoted relative to other Marketplace extensions (see below)
Interestingly, the text at position 4 only appears when built-in Git is enabled, but it appears after the (not built-in) Remote Repositories.
For my other three contributing extensions, disabling and re-enabling any one of them moves them to the end. A window reload reinstates the sequence shown above.
Users of the Serenji extension (a FileSystemProvider) are unlikely to want to use the first button ("Open Folder"). There's currently no way I know of to hide it, and giving it primary-button prominence will make the situation worse.

I believe @bpasero did this for notifications by simply ensuring the first defined action was rendered as primary.

The difference is that notification come from a single source (extension) and these buttons come from multiple


[BUG] resize of a disk in harvester_virtualmachine via terraform is returing success but does nothing

Describe the bug
Creation of a new VM with harvester_virtualmachine and then changing the size of a disk via terraform does not work as expected. Changing size via terraform apply succeeds but does nothing.
To Reproduce
Create a VM via terraform harvester_virtualmachine with two disks.
Then increase the size of the second disk.
Expected behavior
The size of the second disk should be increased.
In case this is not possible a failure should be reported.
Environment

Harvester ISO version: 1.0.3
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): bare metal

@futuretea Do you have new updates of this issue? thanks.

I will try to handle disk resize in vm controller.

Verified fixed on v1.1.2-rc1. Close this issue.
Result
Verified can pass the following test cases
Case 1: Resizing a volume via Volumes page doesn't break the VM.
We can resize volume correctly from virtual machine edit page
Case 2: Can't resize volumes on a running VM.
When we resize the volume size in a running VM on edit yaml, it will indicate error like
please stop the VM before resizing volumes.

Case 3: Can't resize volumes to a smaller size.
When we resize a volume to smaller size on edit yaml, it will indicate error like
PVC requests storage can't be less than previous value.

Case 4: We can resize volumes through VM annotation.
We can successfully resize volume to larger size after vm stopped in edit yaml

Case 5: terraform update volume size
We can use terraform to update the volume size of stopped (Halted) VM.

Test Information

Test Environment: 1 node Harvester on local kvm machine
Harvester version: v1.1.2-rc1

Verify Steps
https://github.com/harvester/tests/issues/626#issue-1459257471
Additional Context

terraform resource.tf
https://github.com/harvester/terraform-provider-harvester/blob/master/examples/resources/harvester_image/resource.tf
https://github.com/harvester/terraform-provider-harvester/blob/master/examples/resources/harvester_virtualmachine/resource.tf


Would you like to transfer ownership ?

I'd like to take it over, then I'll organize the move to jazzband

@jacobh are you able to work this out? What happened to the gizmag organisation? It seems it's now New Atlas...

Hi, I no longer have admin access to this repository. @tysonclugg would you be able to help moving this repo to jazzband?

Thanks very much for the offer to help out!
I've just created the @gizmag/django-fsm-log team with admin rights, and invited @ticosax and @jacobh to join it.  I'd appreciate if the @gizmag/gizmag-development team can retain admin rights to make improvements as @gizmag might need from time to time.
I'm +1 on adopting the code of conduct and other requirements of projects in the @jazzband organization, but -0.5 with this project moving to @jazzband given that you now have admin rights anyway.  Moving the project would be little more than a name change, and somewhat unnecessary.  However, I'll leave that decision to @jacobh and @ticosax.
I'm closing this issue as you now have admin rights.
FYI @browniebroke: Gizmag (the organization) still exists, the online publication was renamed (to New Atlas).

Cool! Thanks for the update and making things move. Let me know if I can help with anything @ticosax

Thank you for your trust @tysonclugg, I'll do my best to keep this project up to date.
One more thing regarding publishing releases to Pypi, do you want to do it or you'd prefer hand it out to us as well ?
If you decide to invite us, my identifier is nicolas_delaby

I've added you as a "maintainer" on PyPI @ticosax :) Thanks for taking this over! I'm quite proud of this project, but haven't had use or interest in it over the last couple of years :)


save a  segment of  that model is  predicted

"Hi! @juanmc2005
I want to save the segments that the model predicts as containing speech. The model detects segments in real-time where someone is talking, and I specifically want to save those audio segments where the model indicates 'yes' for a spoken label. Please save these detected sounds in WAV format."

@juanmc2005
can you help me for this issue?

Hi @m15kh,
The SpeakerDiarization pipeline does provide the waveform aligned to the current diarization output (see here).
The StreamingInference class provides you a way to execute some code when a new pair of "output-audio" is available.
You can achieve this with the attach_hooks() method (see here) by passing a function to execute whenever a new tuple[Annotation, SlidingWindowFeature] is available. Then it would be a matter of cropping the audio according to the speech in the annotation.


AL0157 with ControlAddIn type variable BC21

1. Describe the bug
From version 21.0.40246.0 we´re getting an AL0157 error when declaring a variable of type ControlAddIn, that code has compiled well for the last two years until now.
2. To Reproduce
Create a variable of type ControlAddIn inside a codeunit.
3. Expected behavior
Compile without errors.
4. Actual behavior
AL0157 compiler error.
5. Versions:

AL Language: v10.0.608152
Visual Studio Code: 1.67.2
Business Central: Platform 21.0.40964.0 + Application 21.0.41052.0

Would you be able to explain why this is a problem? We previously allowed this, yes, but unfortunately declaring a variable of type ControlAddIn would lead to issues. Specifically, when the codeunit was being run the runtime would instantly throw an error. If you are able to please provide a sample codeunit which does not break upon usage, we would be able to further investigate,

Thanks for answering so fast. Is this restriction new in BC21? I guess so because in BC20 was working, If I understand it right, in BC21 has never worked in runtime but the compiler was allowing it until version 21.0.40246.0.

The compiler restriction is new in BC21, but the runtime issue has been around before the compiler disallowed this (which is the reason we decided to disallow it).

Thank you.

We have Codeunits that

have global variables of ControlAddIn type,
copy them from Pages' ControlAddIns passed to an initialisation function in the Codeunit, and
do stuff with them afterwards in that Codeunit.

Thus I guess that

ControlAddIn is a reference type
whatever we were doing with it is OK, maybe because we reassign the global reference to point at a valid ControlAddIn instantiated by the Page, rather than the one instantiated (or not?) by the Codeunit

So I would think then that

our existing code will work again in the next version?
to avoid doing this, in case it again becomes an error later, we will have to pass the ControlAddIns to all functions in such Codeunits that need them, instead of 'storing' them as a global in the Codeunit... which seems a best practice anyway.

Do I understand correctly? Thanks!


Suggestion: GitHub links

I think it would be nice if companies that are on GitHub could also have a link to their organization page. Maybe with an Octocat emoji to keep it short? :octocat:

This is actually a good idea! And it supports open source! ✅

This is actually a good idea! And it supports open source! ✅


feat(pkgs/dmd): 2.103.1, 2.104.2 and 2.105.2 (take #2)

This is continuation of #19 by @dukc.

@dukc I've rebased your branch on top of the latest main and I've dropped the pkgs/dmd/2.10{3,4,5}.nix files, as they're redundant with pkgs/dmd/supported-source-versions.json.
You can build these packages like this:
nix-build -A packages.x86_64-linux.dmd-2_103_1
nix-build -A packages.x86_64-linux.dmd-2_104_2
nix-build -A packages.x86_64-linux.dmd-2_105_2

One small improvement idea though, for future: maybe the package names work better without the patch version, meaning packages.x86_64-linux.dmd-2_103 as opposed to packages.x86_64-linux.dmd-2_103_1. We're not going to support different patch versions anyway, only the newest one, right?

Thanks for raising this question! I plan to do the following:

Finish the rewriting of the fetcher scripts. The most important parts are:

Automatically query the git tags for each package, to avoid the need for user to specify them. It should be possible to run the script completely unattended (e.g. dub run -- --min-version=1.05.0 --component=ldc, which should download every single git tag after v1.05.0). We can then add a cron job which will check for updates every day and if so automatically open a PR with the hashes for the new version. That way we can ensure that we support the latest releases as soon as they're tagged.
Use the semver dub package (already started that in scripts/update.d) to compare version in order to pick the latest one for a given minor version. Add a new field latestVersions in version-catalog along the lines of:{
  "latestVersions": {
    "latest": "2.107.0",
    "2.107": "2.107.0",
    "2.106": "2.106.1",
    "2.105": "2.105.3",
    "2.104": "2.104.2",
    ...
   }
}

which will allow us to expose aliases, so a user can just do:nix run d#dmd
# or
nix run d#dmd-2_105


[azure-mgmt-containerinstance] Error 'ImageRegistryCredential' object is not iterable

Package Name: azure-mgmt-containerinstance
Package Version:  1.5.0
Operating System: Ubuntu
Python Version: 3.7

Describe the bug
Returning a TypeError ("object is not iterable") error on creation of an Azure Container Instance of an image hosted on a Azure Container Registry:
Traceback (most recent call last):
  File "app.py", line 60, in <module>
    client.container_groups.create_or_update(resource_group_name, name, cgroup)
  File "/home/someuser/anaconda3/envs/some-env/lib/python3.7/site-packages/azure/mgmt/containerinstance/operations/container_groups_operations.py", line 337, in create_or_update
    **operation_config
  File "/home/someuser/anaconda3/envs/some-env/lib/python3.7/site-packages/azure/mgmt/containerinstance/operations/container_groups_operations.py", line 280, in _create_or_update_initial
    body_content = self._serialize.body(container_group, 'ContainerGroup')
  File "/home/someuser/anaconda3/envs/some-env/lib/python3.7/site-packages/msrest/serialization.py", line 583, in body
    errors = _recursive_validate(data_type, data_type, data)
  File "/home/someuser/anaconda3/envs/some-env/lib/python3.7/site-packages/msrest/serialization.py", line 133, in _recursive_validate
    return data.validate()
  File "/home/someuser/anaconda3/envs/some-env/lib/python3.7/site-packages/msrest/serialization.py", line 227, in validate
    validation_result += _recursive_validate(attr_name, attr_type, value)
  File "/home/someuser/anaconda3/envs/some-env/lib/python3.7/site-packages/msrest/serialization.py", line 125, in _recursive_validate
    for content in data:
TypeError: 'ImageRegistryCredential' object is not iterable

To Reproduce
Steps to reproduce the behavior:

Run a container from an image hosted on the Azure Container Registry.

Can use the following code:
from azure.common.client_factory import get_client_from_auth_file
from azure.mgmt.containerinstance import ContainerInstanceManagementClient
from azure.mgmt.containerinstance.models.image_registry_credential import ImageRegistryCredential
from azure.mgmt.containerinstance.models import (
    ContainerGroup, Container, ContainerPort, Port, IpAddress,
    ResourceRequirements, ResourceRequests, ContainerGroupNetworkProtocol, OperatingSystemTypes
)

# Create the client
client = get_client_from_auth_file(ContainerInstanceManagementClient)

# Parameters
resource_group_name = '...'
location = 'westeurope'
memory, cpu = 1, 1
name = 'myimage'
image = 'myregistry.azurecr.io/samples/myimage:v1'
command = 'some command'
image_registry_credentials = ImageRegistryCredential(
    server='myregistry.azurecr.io',
    username='...',
    password='...'
)
# port = 3000
# environment_variables=

# Set memory and cpu
container_resource_requests = ResourceRequests(memory_in_gb=memory, cpu=cpu)
container_resource_requirements = ResourceRequirements(requests=container_resource_requests)

# Define the container
container = Container(
    name=name,
    image=image,
    resources=container_resource_requirements,
    command=command
    # ports=[ContainerPort(port=port)],
    # environment_variables=environment_variables
)

# Define the container group
cgroup = ContainerGroup(
    location=location,
    containers=[
        container
    ],
    restart_policy='Never',
    # Defaults os_type and ip_address for container group:
    os_type=OperatingSystemTypes.linux,
    # ip_address=IpAddress(
    #     type='public',
    #     ports=[Port(protocol=ContainerGroupNetworkProtocol.tcp, port=port)]
    # ),
    image_registry_credentials=image_registry_credentials
)

# Create the container group
client.container_groups.create_or_update(resource_group_name, name, cgroup)

Expected behavior
I expected the Azure container instance was created.

@davidemiceli thanks for reporting this, looping in the right team to take a look at this //cc: @nickzhums

@RodgeFu can you take a look at this please, thanks!

@changlong-liu to have a look. thanks.

Hi @davidemiceli , the parameter image_registry_credentials of ContainerGroup(...) should be assigned as a list. In this case, would you please help to try below instead?
...
image_registry_credentials=[image_registry_credentials, ]
)

Thanks.

Got a thumb-up from davidemiceli :),  so assume the issue is fixed and close this one to clean up our issues. Feel free to reopen if needed. thanks.


Add helloworld -redis flag for caching with redis

This branch adds a new flag to the helloworld app that will cache responses in redis if the flag is specified. This will be useful for demo'ing non-http protocols. Without the flag set, the app should behave as it does now. The relevant code changes are in 34ddc42.

Discarding this change.


texteur not foud  and crash in game mission

hello M.r Coreynguyen
plase help me  view video  after port model  crash in game mission
texteur not found
https://www.mediafire.com/file/7wbd42ayts5d6b8/plase_read_and_view_video_.rar/file
Plase add fix  for new update MXS

I would like to explain how to edit correctly with this MXS program and show the tools. The program works well, but I need to understand the mechanisms of operation. I continue this SDDE mode in which I have been for many years since 2016. I hope, thanks to your generous ban, that we will contribute to the realization of my life's dream🙏🏻🙏🏻. I am ready to support you, I appreciate what you do.
I would like to know how to work with the character. For example, I want to correctly replace one head with another, because during experiments I get a crash if I choose to play a crash mission. The source of the error is sdhdship.exe with sneakyevil menu script .. I hope it will be modified and fixed with a sleeping dogs mod team to modify and coordinate together in repair and activation sdhdship.exe with sneakyevil menu script with MXS tools
https://www.mediafire.com/file/cta7f2crb3d41bm/bandicam+2024-10-15+20-33-05-333.jpg/file

Hello Mr Coreynguyen
Plase help me send me tutoriel with you tools
Try the program, change a triad db head with another traid thug head in obj fusion and attach format, then put the texture. Please teach me the correct method so that I can finish the mod.
I am getting errors when placing a task
How to maintain the right weight? There are good things in the program like construction, Build, resource manager,.... Please send a simplified explanation so that I can learn this program properly, respecting your time


Strip i386 arch from tvOS compiler-rt lib (if present)

This is to avoid the following issue when generating toolchains for
macOS
ld: building for tvOS, but linking in object file built for tvOS
Simulator, file '/tmp/strip.mgCPcB' for architecture i386
fatal error:
/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip:
internal link edit command failed

This reverts commit 8470faf3092350bd3365946b014ed3de78f5e353, #37929
Addresses rdar://80098850

@swift-ci please smoke test

@swift-ci please build toolchain

From my understanding, this will not work with Xcode 13 beta. We currently have Xcode 13 beta on macOS toolchain bot and Xcode 12.3 on all other bots.

If you don't mind, can you verify this change on both Xcode 12.3 and Xcode 13 beta 1?

Linux Toolchain (Ubuntu 16.04)
Download Toolchain
Git Sha - 245db5371df89f7e4521353fdf8fbac7aa65e281
Install command
tar zxf  swift-PR-38262-619-ubuntu16.04.tar.gz
More info

@swift-ci please smoke test

@swift-ci please build toolchain

Doing a clean build locally with Xcode 13.0 beta 1 indeed exposed an issue around the copy of the libraries when the source library does not have the i386 slice to begin with.
I am still running the preset locally to ensure the change is sane, I will lean on CI to ensure the change still works with Xcode 12.3

Linux Toolchain (Ubuntu 16.04)
Download Toolchain
Git Sha - 376b6f20ebcef66b8dba5cfcdc8773495db203c6
Install command
tar zxf  swift-PR-38262-620-ubuntu16.04.tar.gz
More info

macOS Toolchain
Download Toolchain
Git Sha - 376b6f20ebcef66b8dba5cfcdc8773495db203c6
Install command
tar -zxf  swift-PR-38262-1041-osx.tar.gz --directory ~/

@edymtt Can you also cherry-pick this on to 5.5 branch?


Yaml worker can't read properties of undefined

TypeError: Cannot read properties of undefined (reading 'indexOf')
    at resolveRefs (http://localhost:5173/node_modules/.vite/deps/monaco-yaml_yaml__worker__js.js?v=8e002f8b:29936:27)
    at YAMLSchemaService.resolveSchemaContent (http://localhost:5173/node_modules/.vite/deps/monaco-yaml_yaml__worker__js.js?v=8e002f8b:29962:11)
    at http://localhost:5173/node_modules/.vite/deps/monaco-yaml_yaml__worker__js.js?v=8e002f8b:26721:32
    at async YamlCompletion.doComplete (http://localhost:5173/node_modules/.vite/deps/monaco-yaml_yaml__worker__js.js?v=8e002f8b:31640:23)

I'm not sure where this has come from. I've followed your vite example.

Please provide and example repository and exact steps to reproduce.

Hello, do you have a demo that combines monaco-editor with monaco-yaml? It's a relatively simple demo. I'm a beginner

@Lichenhao01 That’s not related to this issue. Anyway, see https://github.com/remcohaszing/monaco-yaml#examples

I’m closing this because there’s no reproduction.


how to use redux-saga with async callback function

I want to use redux-saga yield call effect with async function that get the result of this function is call back. ( in this case fingerprintjs but it's general case)
This is the async function I want to exactue :
new Fingerprint2().get(function(result, components) { console.log(result); console.log(components); })
The issue that I want to execute this function via saga , but it's always stuck on yield call.
I try many ways :
 import Fingerprint2 from 'fingerprintjs2';    const func = new Fingerprint2().get;    const res = yield call(func);
Also try like this:
import Fingerprint2 from 'fingerprintjs2'; const func = new Fingerprint2().get; const a = yield call(func, (fingerprint, result) => ({   fingerprint,   result }));
And like this:
import Fingerprint2 from 'fingerprintjs2'; let res = yield call(new Fingerprint2().get(), (fingerprint, result) => ({   fingerprint,   result }));
Any one know about idea or some way to acheive my goal ?
Thanks!

One solution for this is that wrapping this function with Promise, and then yield this promise in saga. Another way may be using cps effects, but I'm not sure about it.

@shinima  I try with cps but it's looks the same.
Can you give me example or something I can use ? no one use thing like that with saga never?
tnx!

Hey @OriAmir
I have a question. Is new Fingerprint2().get() synchronous? What does the get return?

This should work too
const { result, components } = yield call(() => new Fingerprint2().get((result, components) => ({ result, components })))

if its callback based it should be possible to do this
const { result, components } = yield cps((err, cb) => new Fingerprint2().get((result, components) => cb({ result, components })))

Sorry, I've made a mistake, it should actually be this:
const { result, components } = yield cps((cb) => new Fingerprint2().get((result, components) => cb(null, { result, components })))

Seem that the issue is resolved. Closing it.

Sorry, I've made a mistake, it should actually be this:
const { result, components } = yield cps(cb => new Fingerprint2().get((result, components) => cb(null, { result, components })))

Why not to use just call instead of misusing cps:
const { result, components } = yield call(new Promise((resolve) => new Fingerprint2().get((result, components) => resolve({ result, components }))))

Sorry, I've made a mistake, it should actually be this:
const { result, components } = yield cps(cb => new Fingerprint2().get((result, components) => cb(null, { result, components })))

Why not to use just call instead of misusing cps:
const { result, components } = yield call(new Promise((resolve) => new Fingerprint2().get((result, components) => resolve({ result, components }))))


exceljs might be vulnerable for regular expression denial of service

Runnig nsp check I get the following warning -
Regular Expression Denial of Service
minimatch
<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>https://nodesecurity.io/advisories/118
Not sure how big of an issue it is, but It might be best to upgrade the archiver package to the latest one (which in turn will upgrade glob and minimatch).

Oddly, I noticed this a few days ago too (must have watched the same video).
I'll push the recommended fix into the next release

Fixed in 0.2.13


LOOP-4178 Fixes for Xcode 14 and iOS 16

https://tidepool.atlassian.net/browse/LOOP-4178

Looks like the description field of HKQuantitySample has changed to include a uuid, which is different between different instances.


Meetup Suggestion: North Houston Bitcoin Club

Name of Meetup:  North Houston Bitcoin Club
Location Of Meetup:
6-7pm:
2101 Lake Robbins Dr
The Woodlands, TX 77380
7p-9p:
21 Waterway Ave
The Woodlands, TX 77380

At least one of the following:

Meetup Page (or similar):  https://www.meetup.com/north-houston-bitcoin-meetup/events/288603961/

Name of Organiser(s) & Twitter Handle: Nate @beeforbacon1

Ready to be made into a pull request.


List of objects in json configuration issue

I'm creating a json file that I wish to add in configuration through configuration.AddJsonFile() with the following structure:
{
  "JsonLocalizerOptions": {
    "SupportedLanguages": [
      {
        "Identifier": "ro-MD",
        "Name": "Romana"
      }
    ]
  }
}

then I have a POCO class for it:
public class JsonLocalizerOptions
{
    #region Private backing fields (Default Values)
    private List<Language> supportedLanguages = new List<Language>()
    {
        new Language
        {
            Identifier = "en",
            Name = "English"
        },

        new Language
        {
            Identifier = "ro",
            Name = "Română"
        },

        new Language
        {
            Identifier ="ru",
            Name ="Русский"
        }
    };
    #endregion

    public JsonLocalizerOptions() { }

    #region Public Properties
    public List<Language> SupportedLanguages
    {
        get => supportedLanguages;
        set => supportedLanguages = value;
    }
    #endregion
}

The problem is that when I call services.Configure<JsonLocalizerOptions>(Configuration.GetSection(nameof(JsonLocalizerOptions))) the value object from the setter of the property SupportedLanguages contains the default list of the languages plus that one object from the json file. I think this is bizarre, I thought that when I call Configure I should receive the data from the json file, not my current data appending that one from json or the same data from the private field even though the setter is accessed.

Is this really how it should work?

Dupe of https://github.com/aspnet/Configuration/issues/694


fix url to index page

fixed broken url to the index page for statistical software workshops at IQSS

Thanks!


Topic connection time

We need to improve the way we ensure topics are connected...
Currently this code is making everything depending on that very slow :
https://github.com/asmodehn/pyros/blob/master/pyros/rosinterface/topic.py#L266
But if we try to do it faster,  topic communication is not established when returning from __init__(), and things start breaking, when running podium with connection cache...
When running podium without connection cache however, topic interfacing seems fine.
So it is likely a race condition between the connection cache message frequency, and the time to establish a topic connection.
But when running tests there doesn't seem to be any difference if this sleep time is slow or fast, with or without cache.
More investigation needed...

This has now been improved after splitting pubs and subs. We check for at least a connection before returning from init()

done and 0.3.0 has been released.


Scoping issues using nested selectors with same names.

Assuming the following object:
category.nodes = [
  {
    product: "1",
    type: "product"
  },
  {
    product: "2",
    type: "product"
  },
  {
    category: "categoryName",
    type: "category"
  }
]

And the following template:

    {{#category.nodes}}
      {{#product}}

{{product}}

      {{/product}}
      {{#category}}

{{category}}

      {{/category}}
   {{/category.nodes}}

One would assume that one

 would be made for the category, however 3 are made.
It appears to be referencing the parent category instead of the nested section category
here is a jsfiddle demonstrating the issue, and here is one demonstrating appropriate behavior by adjusting the parent name (category --> parent).
Related question on StackOverflow

This behavior matches the specification.

Apologies, I must have missed that bit =(
Thank you for the response!


Local pull request success status testing

Docs Build status updates of commit 534de81:
:clock10: Pending: waiting for processors (15 builds ahead of you)
:warning: Docs Build is busy, currently there are 15 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 534de81:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

E2E_DocsBranch_Dynamic/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Can't use sourcery because the binary is not found

Issue description or question
Can't use sourcery because it fails to find the binary during configuration

This may well be an issue with my work network though my other plugins do not have this issue.  Is it possible to download the plugin and install it manually?
Sourcery Version
All versions
Code editor or IDE name and version
Pycharm v?
2019.3
OS name and version
Windows 10

After reading the plugin XML and finding the exe is in fact installed, the issue is that by policy i can't execute binaries in roaming.  Is there a way to configure the installation location to a place i can use?

Oh interesting. I'll look into making that more configurable. It's stored in sourceryExecutable in a sourcery.xml file in PyCharm but I'm not sure where this lives on Windows.
Did you also have an issue with Sourcery taking up lots of disk space? Would also be great to solve that one if you have more details.

On windows, the xml file lives here: C:\Users\rossh.PyCharm2019.3\config\options
I went so far as to edit the path listed there but when restarting the IDE, it seems like it redownloads the plugin and rewrites the xml.  Then I tried write protecting the xml, but it errors because it can't write it's settings.
Re: the large disk space usage, that is on my home pc.  I was shocked to see it taking 10s of gigs.  When I get home I'll see what kind of information I can dig up.

We've decided to switch to bundling the binary with the plugin. This will mean that it runs from within wherever Pycharm is installed, which should fix the AppData/Roaming problem.
It's submitted to IntelliJ - will let you know when it's approved and you can test the new version.

OK the new version of the plugin (0.3.0) is now available. It would be great if you could try it out to see if it resolves your issue.
To install it go to File > Settings > Plugins and update Sourcery via the Update tab.

Wow!  Thanks so much - that works perfectly.  I'm happy to donate my time to an issue or two to any open parts of your project as a thank you.
I'll monitor my disk usage and let you know about the space issue.  If I see it again I'll open an issue.

No problem!  What we need most of all right now is feedback so please do keep opening issues with problems/improvements we could make.


QA-15174 Preview now honors the j:view property

JIRA

https://jira.jahia.org/browse/QA-15174
Description

Tests
The following are included in this PR

[ ] Unit Tests (Most changes should have unit tests)
[ ] Integration Tests

Checklist

I have considered the following implications of my change:

[ ] Security (in particular for changes to authentication, authorization, data fetching, ...)
[ ] Performance
[ ] Migration
[ ] Code maintainability

Documentation

[ ] Inline documentation
[ ] Internal Documentation (wiki)
[ ] User-facing Documentation

while this works, I think part of the implementation notes is that we wanted to make this change on the graphql layer so that we avoid querying stuff that's already available in the graphql. Specifically this additional note on the story:

We should update the GraphQL endpoint renderedContent so that it uses the view set on the node by default instead of using the default view.
If a specific view is passed in the GraphQL call, of course this view should be used.
=> in terms of priority when calling renderedContent:
1 - use the view passed in the graphql call, if there is one
2 - use the view set on the node, if there is one
3 - use the default view

We also might want to rewrite the PR that's already merged in master

After discussion from daily, because we want to limit the backport dependencies and create delays for 8.1, we are going with the UI approach at least for jcontent 2x, as oppose to using the fix available in graphql (although we are still backporting this part in graphql 2x for 8.1 still).


Cloud changelog - April 21

Reviewers: Please help with descriptions for the major features as well as any breaking changes / special notes.

@adamjclarkson, since shared channels is not GA yet, should we leave it unannounced for now?

@adamjclarkson, since shared channels is not GA yet, should we leave it unannounced for now?

Normally features in beta or experimental are included in the changelog with a "beta" or "experimental" tag. Is Shared Channels in beta?

@adamjclarkson @aaronrothschild Kind reminder for PR review.

Normally features in beta or experimental are included in the changelog with a "beta" or "experimental" label. Is Shared Channels in beta?

It's currently alpha.

Normally features in beta or experimental are included in the changelog with a "beta" or "experimental" label. Is Shared Channels in beta?

It's currently alpha.

@wiersgallak Can you help confirm if Shared Channels is alpha or experimental? Do we mention the feature in the changelog?

@amyblais We consider Alpha as Experimental. Listing it as Experimental is correct.


Update high-availability-guide-suse-pacemaker.md

It seems reboot will use PowerOff

@wtmpx : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @wtmpx. That is correct.


update Nuget packages versions to latest

this PR relates to Issue #4611 to refresh NuGet packages to current versions
I bow to ErikEJ's push and Roji's +1 !
summary/caveats

I have updated EF.* from 8.0.0 to 8.0.1 (probably small beer)
Benchmark.Net from 0.13.2(26/8/22) to v0.13.12 which broke 1 file in CompiledModels that I fixed per
https://benchmarkdotnet.org/articles/configs/jobs.html
"Usually, you shouldn't specify such characteristics like LaunchCount, WarmupCount, IterationCount, or IterationTime because BenchmarkDotNet has a smart algorithm to choose these values automatically based on received measurements."
Microsoft.AspNetCore.Identity.EntityFrameworkCore and Microsoft.AspNetCore.Identity.UI from 7.0.0 to 8.0.1
Microsoft.Azure.Services.AppAuthentication to 1.6.2
Microsoft.Extensions.Hosting and Microsoft.Extensions.Logging.Console from 7.0.0 to 8.0.0
Microsoft.NET.Test.Sdk from 17.3.1 to 17.8.0
Moq from 4.18.2 to 4.20.70
NetTopologySuite.IO.GeoJSON from 2.0.4 to 4.0.0
Newtonsoft.Json from 13.0.2 to 13.0.3 (I'm surprised not to see System.Text.Json enforced!)
Swashbuckle.AspNetCore from 6.4.0 to 6.5.0
xunit from 2.4.2 to 2.6.6, xunit.runner.visualstudio from 2.4.5 to 2.5.6
I noticed that (after PMC update) that Microsoft.EntityFrameworkCore.Design 8.0.1 now has PrivateAssets
there are now launchsettings.Json files that sneaked in (not sure if you want/dislike but not rejected by .ignore)

so hopefully EF Team will concur that these change are apposite and will shipit
BTW I am still working on an extra PR for Issue #4612 but should arrive soon

apologies I temporarily "lost" reverting the "What's new in X.*" so this attempts to keep the timewarp clean #9no rewriting history here!)
doubly embarassing after I had a tilt at Roji earlier [please forgive!] https://github.com/roji/EfUpdatePerf/commit/e3278670134ff0482538a2d3a19e3c5131045a76


Fix for issue #8: Clearing RS.Event_MouseTerrainHit is not qualified …

…by event type [Unity 5.6.1xf1]
This change moves the qualifier against mouse events to a single if around the whole block then checks for control and shift within the block.

There will need to be testing to ensure that the change in qualification does not induce an unnecessary burden, by qualifying on all mouse events,

What are the existing testing and qualification methodologies?
Can you elaborate on what 'unnecessary burden' you are concerned about?

Tested change on 5.6.2f1:

Ran Unit Tests - PASS
Select Road2, hold SHIFT and insert nodes between various nodes - PASS
Delete inserted nodes - PASS
Select Road2, hold CTRL and add nodes - PASS
Delete added nodes - PASS

No regressions were detected during testing
Unable to determine the steps needed to reproduce the issue described in issue #8 where nodes could not be placed.


CLI: Print events during invoke if --events option is present

I think we should output events, including any DebugEvents the system has generated to stdout, or somewhere, when the invoke command is used.
This behavior was previously described here: https://github.com/stellar/soroban-cli/issues/39#issuecomment-1238517053

I opened this issue when I thought we weren't outputting events, but we are already outputting the events, and so this issue isn't required.


New command: Remove content type from site

Remove content type from site
command: spo contenttype remove -u|--webUrl <webUrl> --contentTypeId <contentTypeId> --confirm

webUrl: URL of the site from which to remove content type
contentTypeId: ID of the content type to remove from site
confirm: Don't prompt for confirming removing the content type from site

You want to take it? 😄

Yes, with pleasure. 😊

Excellent! All yours!

@phawrylak are you still working on this?

Hi @waldekmastykarz  , May I pickup this?

Of course! All yours!

Thanks @waldekmastykarz

@waldekmastykarz it looks like this is a duplicate of #904 which has since been resolved.

You're right @DaveCalGH


built new static page

Here is a new static page for specification.
built with lazyfox template (open source, html5, bootstrap3).
Feel free to edit the page. its just a first try.
I used rakuris txt-documentation.

Then for the libraries (bootstrap, jquery, css, fonts), i'd advise to use a cdn for those and then don't include these minified files so we host only the custom css/js :)

I disagree, please keep the minified files in this here repository where the license allows it. This is a requirement to comply with GDPR/CCPA/LGPD. Thanks.


[Spark-14230][STREAMING] Config the start time (jitter) for streaming…

What changes were proposed in this pull request?
Currently, RecurringTimer will normalize the start time. For instance, if batch duration is 1 min, all the job will start exactly at 1 min boundary.
This actually adds some burden to the streaming source. Assuming the source is Kafka, and there is a list of streaming jobs with 1 min batch duration, then at first few seconds of each min, high network traffic will be observed in Kafka. This makes Kafka capacity planning tricky.
It will be great to have an option in the streaming context to set the job start time. In this way, user can add a jitter for the start time for each, and make Kafka fetch_request much smooth across the duration window.
How was this patch tested?
Unit test: A test case added.
Integration test.
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
… jobs

Can one of the admins verify this patch?

Is it better to handle this by back-pressure or something like flow control mechanism? I'm just wondering if this jitter will break the internal semantics of Spark Streaming.

I thought the back pressure/flow control handles how many message to fetch, not when to start to generate the job. IMHO, adding the jitter in the start time is more deterministic than adding the jitter in the flow control.

Can one of the admins verify this patch?

Hi @liyintang, thanks for this PR. I apologize for not providing feedback on this earlier. This is indeed a practical problem in production, but I am not sure how adding the jitter would be affect downstream stuff - rate calculation, flow control, etc. Spark Streaming was not designed keep such things in mind. In the new Structured Streaming, this would not be a problem, as the batch interval (called trigger interval there) is optional, and if it is not specified, it will start next batch when previous batch finishes. That means that multiple jobs wont synchronize. I suggest you try out Structured Streaming.


Update shading rules for databricks runtime assembly

Shade more dependencies.

Looks good. I am trying to write code to run test cases against the fat jar.


Fix/execute with retry wrapper exec

Description
Removes executeWithRetry as we no longer need to retry operations due to network stability fixes. We now will only retry operations which are critical to the standup of the sdk. The included node endpoints which are eligible for retry at this time are:

/handshake

Status codes we will retry on:

408
502
503
504

Introduces a new package fetch-retry which now handles retry logic for single requests. As we no longer need to group requests and retry as single network operation.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Tested with local testing to force endpoint failure to observe retry.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

After doing some testing in browser environments it looks like the umd bundle target is non compatible with our build pipeline. Going to make a task in the current sprint to upgrade fetch-retry to a modern cross target bundling implementation. Once complete this pr can be merged.

Closing for #497


B-554 – azure cluster test with adlsgen2

B-554 – azure cluster test with adlsgen2

please fix the commit message: missing B from the beginning


Share event inside event's page

[note to self]

isn't this already part of #4878 ?

@jesseallhands
They are quite similar, #4878 is to create this button on the /events page, the list that shows the events, this is to create the share button inside the event page.
With this ticket when a person receives the event, and it is public, he can share it to other people, so it's possible to propagate it :D


Consider putting more emphasis on readable git history; use squash strategy when merging single-unit PRs.

This is simply a suggestion from a user and contributor to this (excellent) Go project about a way I think it can be made better.
I was recently updating to the latest version and looking over the history to see what changed. On master branch, I saw commit d593fc4cb952c55216fd0f9a28d195b34a5020cf, a revert commit, which did not describe the motivation for reverting a change (which is a bad practice, because it makes it really hard to understand why something was reverted for all other people). Upon further investigation, I saw that commit was actually a part of PR #147, so nothing was actually reverted on master, it was just an internal detail of that PR.
In general, the git history of master branch has a low signal to noise ratio because of many commits with unhelpful subjects and commit message bodies. E.g.:

It seems that most PRs here are made of commits that are just addressing internal PR feedback, rather than broken up into clean, logical and well documented separate commits to make the overall diff easier to understand. Yet they're merged via the "merge commit" strategy, which preserves individual PR commits with their original commit messages, resulting in the problem described above.
I suggest merging such PRs via the "squash merge" strategy, with a descriptive commit message that actually describes what changed on master and why. GitHub makes it easy ever since they've added this feature:

For examples of what it can look like to have more readable git history, see:

https://github.com/golang/go/commits/master
https://github.com/golang/net/commits/master
https://github.com/google/go-cmp/commits/master
https://github.com/google/go-github/commits/master
https://github.com/shurcooL/Go-Package-Store/commits/master

Thanks for consideration!

For reference, I was using GPS to see the updates, which exacerbates the situation. Compare:

To something much more readable, like:

Thanks for creating this @shurcooL -- I appreciate your attention to detail (especially since this more relates to how someone less involved in Vecty development might see / perceive Vecty).
Deciding the right strategy here is hard because sometimes changes / PRs do need to actually make two distinct changes from the perspective of the master branch. For example, if adding a new public function requires modifying an existing one. For these situations, what I will do from now on is write this detail into the squash merge commit message. I don't want to require contributors necessarily to create two distinct PRs in this case, since I wish to place more emphasis on code quality rather than git history.
But, to hopefully improve this issue as a whole, I've enabled GitHub's restrictions on merge/rebase commits, so that only squash merge is possible for me now:

We'll see if that helps improve our commit logicality overall. If it doesn't, we can try a different strategy :)
Closing for now.

Great, thanks a lot! I'm sure this will help significantly. Just make sure to review and edit the commit message title and body when merging PRs, so they contain only the information relevant to the final overall diff. You get a chance to easily modify them during the process of merging (this is one of the biggest benefits of this feature).

Deciding the right strategy here is hard because sometimes changes / PRs do need to actually make two distinct changes from the perspective of the master branch.

In those cases, which as you mention are more rare, you could use rebase merge strategy, but it requires each commit to have a clean commit message. It won't give you a chance to edit them when merging.

Will do! Good points all around :)


Extending styles

What is the proper way to extend styles in this library?

You can apply your custom style and className to each component.


Open Source : 6.29 Explain everything related to Svelte

Description 📜
Open Source : 6.28 Explain everything related to Svelte
NOTE 👇
Please put your doc 6.Popular_Projects with the name 6.29_Svelte.md

Domain
Open Source
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Hey @Aryamanz29 I want to work with this issue. Kindly assign it to me.

/assign

/assign

/assign documentation

@ShivaniAgarwal2001 Assigned, Happy learning 🎉🎉


New scam I just found

The game pretends to be "the new best adventure game", but it was advertised through a token-grabbed discord account. The website is a collection of stolen assets from the upcoming game "Silt" and it downloads a file called "SpiralCircus.rar"; I didn't dare downloading it. I had a fun time forcing the hacker to speak french to me.
spiralcircus.org
bit.ly/spiralcircus

Added in #200 ;) ty!


Expected behavior for NaN annotations

Thanks for the great package! What is the expected behavior of DataGenerator for annotations set to NaN in the annotations h5 file? I use my own labeling GUI and set to NaN all features that are not present within a frame. However, the DataGenerator spits out very large negative numbers (-999999) rather than nan for the annotations set to nan in the annotation h5 file. Is this correct, and will the keras generator spit out all-zero target maps for these features?
Thank you,
Rick

Hi Rick, Yes, this is expected behavior (see https://github.com/jgraving/DeepPoseKit/blob/master/deepposekit/io/BaseGenerator.py#L125). This was a quick workaround to allow the TrainingGenerator to work with NaN annotations. Because keypoint coordinates are defined by the height and width of the image, setting NaN annotations to a large negative number ensures that the confidence maps will be set to all zeros, even if the images are augmented such that the coordinate space is shifted.

Perfect, thanks!

I recently observed that if a feature is set to NaN (such that it's position is set to [-999999, -999999]), but it is connected to a feature not set to NaN, the skeleton connecting these features actually 'reaches out' to [-999999, -999999]. My repo is a few commits behind; are you aware of this issue and has it been fixed?
Thanks!
Rick

I'm closing this because the bug in the graph drawing was address in issue #52


Document recommended memory requirements

For 2.0 make a short-term update to the documentation to say that memory usage may be an issue, pending improvement in a future release.
Include reference to "excessive dedup memory usage with output-stats" CGATOxford/UMI-tools/issues/409, and suggest that users set dedup_stats: FALSE to turn off output statistics creation (see #186).
Spawned from #179

When running RiboViz - either Python or Nextflow - with the vignette data it runs fine for me under:

VMWare VM with 8GB RAM (running on my laptop)
University of Edinburgh EDDIE compute cluster:

Interactive node (accessed via qlogin) with 8GB RAM requested.
Back-end node (accessed via qsub) with 16GB RAM requested. On job completion, qacct shows: maxvmem 13.726G.
If my qsub job requests 8GB RAM they quickly fail with qacct showing, for example, failed 46  : execd enforced h_vmem limit, exit_status  137, maxvmem 8.115G

@FlicAnderson, @ewallace, @john-s-f, @amandamok  @XUEXUEXUE0 please could you provide some idea as to how much GB memory (to the nearest GB will be fine) the platforms run RiboViz on have - both for vignette data and for any full size datasets.

My machine has run riboviz (Python & Nextflow) successfully for vignette & multiple full-size yeast datasets & has 16GB RAM to play with.

8GB RAM is enough for running the riboviz vignette with python method but is not enough for nextflow method. So I suggest 16GB RAM.

Thanks @FlicAnderson  and @XUEXUEXUE0!

@john-s-f and @amandamok this is the ticket for the "survey" of Riboviz memory usage. Thanks!

I've been running the nextflow version on our lab server which has the following:
2x Intel Xeon Processor E5-2660 v4 amounting to 28 cores and 56 threads
264Gb of ram
Ubuntu 18.04.4 LTS

Following @XUEXUEXUE0 's advice, I've run vignette and full-size yeast data on Eddie with 16GB requested. I haven't tested this any further.

Please add further updates to #179.


Obey caching headers for update requests

Today we got a few Error: Wrong value for chrome_ref in offscreencanvas.md in the channel because the Google's status JSON updated but the old file was used from the cache.
This could be circumvented when the caching used in the build would be aware of HTTP caching headers in the web responses.

Thoughts @marco-c @TimAbraldes ?

This could be circumvented when the caching used in the build would be aware of HTTP caching headers in the web responses.

Seems reasonable. We'll store some metadata (e.g. expiration time) with each file and make the files expire based on what the cache headers tell us

I'd leave that yak unshaven as its cold outside. This looks promising: https://www.npmjs.com/package/eu but the search for cache-header-aware request libraries is littered with elderly or half-shaved yaks.

I'm trying eu, but I've got a hard time with closing the link to database. Seems like it should be open and closed on every request. This lib is prepared for servers...

Please review the #376

Fixed by #376.


types: add typespecs

Closes #23
Adds type specifications to all public functions in all modules (except for the callbacks in api.ex).
As much as possible, I tried to name specific types in each module rather than using primitive types everywhere.
I was going to provide a more detailed typespec for Config.t(), but since we don't control that spec here in our code, I chose to leave it as the more generic map().  The Java client does roughly the same thing, typing it as a JsonObject.
In general, I explicitly listed the various options taken by a module, but for structs, I used the more generic keyword() | map() to avoid having to duplicate the fields in the struct, which are already listed out in the t() type.
I modified the User custom property to be an empty map by default rather than having to include an extra nil in the typespec.  Also, I marked the identifier property as required even though we handle the case where it's not provided. From the discussion in Slack, using nil there is discouraged but not disallowed; I figure we can at least provide a Dialyzer warning about it even if we handle it OK.
Refreshingly, adding the typespecs didn't expose any type errors in our code!  I was pleasantly surprised by that.

Refreshingly, adding the typespecs didn't expose any type errors in our code! I was pleasantly surprised by that.

😅


feat: Add a backend for replicated sharing for rings, as well as code of casting between different rings and fields.

IDK how to easiest fix this now since the first 2 commits were already in the other PR?
probably just cherry-picking the other ones onto main?

I just rebased everything, worked out nicely


Rename SoEW shots

Descriptive names, even if official, are arguably more confusing than the more common A, B, C shot designations. Possibly rename them?

On the contrary, I think we're used to the ReimuA, B, C nomenclature even if she's the only character


version bump

getting this error
Error resolving kemal-session (*, 0.6.0)
I think the version needs updating here

Thank you 👍


Centos 7 Fresh  puppet 4.10 uninitialized constant

I have followed the guideline when installing but no matter what i do i get  uninitialized constant Aws::Route53, Aws::EC2 etc
Puppet Gem list:
/opt/puppetlabs/puppet/bin/gem list
*** LOCAL GEMS ***
aws-partitions (1.21.0)
aws-sdk-core (3.5.0)
aws-sigv4 (1.0.2)
bigdecimal (1.2.4)
deep_merge (1.0.1)
facter (3.6.7)
fast_gettext (1.1.0)
gettext (3.2.2)
gettext-setup (0.20)
hiera (3.3.2)
hocon (1.2.5)
io-console (0.4.3)
jmespath (1.3.1)
json (1.8.1)
locale (2.1.2)
minitest (4.7.5)
net-ssh (4.1.0)
psych (2.0.5)
puppet (4.10.8)
rake (10.1.0)
rdoc (4.1.0)
retries (0.0.5)
semantic_puppet (0.1.2)
stomp (1.3.3)
test-unit (<IP_ADDRESS>)
text (1.3.1)

I was able to fix this by downgrading from aws-sdk-core 3.5 to aws-sdk-core 2.4.4 it would be great if you add the version requirements to the README


WIP: Feat: support k-quants q2_k

Still in working. (Some common constants and helper functions for K-Quants are in qkk mod)

Ref: #76 #75

I'm not sure if other ways to find the nearest integer would work the same as llamma.cpp 's version, so I just copy those snippets and keep tests with some random floats generated in cpp code.

I'm not sure if other ways to find the nearest integer would work the same as llamma.cpp 's version, so I just copy those snippets and keep tests with some random floats generated in cpp code.

Don't worry, an end-to-end test using Q2_K can finally help us determine whether it works or not. We can find a model like this one:
https://huggingface.co/jartine/TinyLlama-1.1B-Chat-v1.0-GGUF/blob/d3f63b09fb8b2a1fda466efd1705c103ba3cb5aa/TinyLlama-1.1B-Chat-v1.0.Q2_K.gguf

The q2k dequantization has a diff error which llama.cpp also has. I just ignore it for now. Will try a model later.

thank you for your contribution!
it appears that there are some merge conflicts that need to be resolved before merging.

I think it may be necessary to do a rebase. Currently, this commit has mixed many commits and files by others.

I think it may be necessary to do a rebase. Currently, this commit has mixed many commits and files by others.

Alr done with rebase now. I incorrectly changed the code base before.

cool, LGTM :+1:

Hi, @AuruTus ，I carefully examined your data generation method, and the diff error is caused by the data generation.

Hi, @AuruTus ，I carefully examined your data generation method, and the diff error is caused by the data generation.

Please ignore me, I made a mistake


Added Random Joke Generator Project

Hey @ayushsarode,
I have completed the project. The project is Random Joke Generator using JokeAPI.
Technology Stack:

HTML
CSS
JavaScript

Kindly review the code and if there are any changes please let me know.
Thank you.

Thank you for your valuable contribution!
Make sure you leave a star ⭐ on the repo


Add diskused metric representing most full data_file_dir

Adds DiskUsed to the StorageMetrics metric family. This metric shows the busiest data directory listed in data_file_directories as a percentage ranging from 0 to 100.

Unable to release palantir-cassandra-2.2.18 since the branch protections rules include administrators. Please modify the rule.


Add Manual Tests for schedule and meetings

Coverage remained the same at 88.976% when pulling 87c23d85422595464c1531b795b85373219977c3 on AyushChatto:addManualTestsToDevGuide into 1cab4d22902527b65fca43fe97c9d6c7ce9f2542 on CS2103-AY1819S1-W13-1:master.


Mismatch during loading and saving of model

Hello I have a mismatch of saving and loading the model...
System.ArgumentException
HResult=0x80070057
Nachricht = Mismatched state_dict sizes: expected 54, but found 80 entries.
Quelle = TorchSharp
Stapelüberwachung:
bei TorchSharp.torch.nn.Module.load(BinaryReader reader, Boolean strict, IList1 skip)    bei TorchSharp.torch.nn.Module.load(String location, Boolean strict, IList1 skip)
bei QT.Torch.Model.Attention.TimeEncoder.TrainStock() in D:\Projects\QT\Torch\Model\Attention\TimeEncoder.cs: Zeile166
the class looks like this...
public class TimeEncoder : nn.Module
{
int dim_model;
// TorchSharp.Modules.TransformerEncoder transformer;
Linear input;
Linear output;
PositionalEncoding positional_encoder;
TransformerEncoderLayer el01;
TransformerEncoderLayer el02;
TransformerEncoderLayer el03;
TransformerEncoderLayer el04;
Tensor sqrtmodeldim;
public TimeEncoder(int features, int dim_model, int nhead,long forward, double dropout_p) : base(nameof(TimeEncoder))
{
//INFO
this.dim_model = dim_model;
//Layers
this.positional_encoder = new PositionalEncoding(dim_model: dim_model, dropout_p: dropout_p, max_len: 2000);
this.input = nn.Linear(features, dim_model);
nn.ModuleList();
        var l = new List<TransformerEncoderLayer>();

        el01 = nn.TransformerEncoderLayer(dim_model, nhead, forward, dropout_p);
        el02 = nn.TransformerEncoderLayer(dim_model, nhead, forward, dropout_p);
        el03 = nn.TransformerEncoderLayer(dim_model, nhead, forward, dropout_p);
        el04 = nn.TransformerEncoderLayer(dim_model, nhead, forward, dropout_p);

        this.output = nn.Linear(dim_model, features);
        this.sqrtmodeldim= ((Tensor)Math.Sqrt((float)this.dim_model)).to(device: "Cuda");
        this.RegisterComponents();
    }

As noted by Niklas in another issue, "ModuleList and ModuleDict are primarily used to trigger automatic registration of the modules that are held by them, i.e. during module construction."
I have a suspicion that because List is used here, the RegisterComponents is unable to see the nested layers and properly register them. Therefore I suggest you try with a ModuleList instead of List and see if that might fix the problem.

You should always wait until after the call to RegisterComponents to move anything to CUDA.

@Sprinzl -- is this still a problem for you? If so, please confirm that you are building all the layers on CPU, registering components, and then moving them to CUDA.

@NiklasGustafsson No Problem - Solved - as you said. On Top of it i had some issues with the discope sope. Also solved. Your API is really nice.


Add a Codacy badge to README.md

Coverage remained the same at 100.0% when pulling 5e7f027f46e3cdcaf97fee86ad6bb1b2d6d9e60a on codacy-badger:codacy-badge into 02db049fc266826a9dac51bd260887fbd0306d61 on triat:master.


Working Perfectly! But where to find the key?

I have 3 entries in my Google Authenticator on my phone, Where can I find the key (564HJKHJKHKKKHGJKHJKYUFHFGHJ65E) to enter into this repo?

Hi @notflip
Glad it is working well for you 😊
I have tried to find out myself but I'm also not able to get the key from Google Authenticator. I had to unlink my 2fa and then set it up again to get the key. Sorry, it's not ideal but I couldn't find another way to do it. If you find a way, please let me know and I'll add it to the README.

Do you know what the official term or name for that key is? It's hard to google since a 'key' could in this case also mean the key that gotp returns

@notflip
I believe the term is secret key where what is generated by the Google Authenticator and Gotp is called a verification code

@wesmartin I'm not sure about this but can a Secret key live in two places? Or is it an "or" situations? Where I can have it in here, but not in my Google Authenticator at the same time?

@notflip you can have it in multiple places. I have my keys stored in Gotp and Google Authenticator as a backup or if I don't have my computer with me.

https://github.com/dim13/otpauth.git
this looks like the thing we need, trying it out today. You can export your keys in the Google Auth app, and then scan the QR code, the package above will transform the QR code to the string we need (I hope)

@wesmartin I got it working using the above.

@notflip thanks for letting me know. I did some testing as well and found that any QR code scanner will show what the secret key is. There will be some other text in what is returned by the QR code by the secret will be there 😊


Multiple Integrations Merge into One after Error

Version of the custom_component

Both frigate instances are 0.10.0-beta6-amd64, home assistant is 2012.12.0, and integration v2.2.0.
I have not checked if the issue is present in 0.9.4
Configuration
Both frigate instances have essentially identical configs except one uses a USB TPU and the other PCI, both have different cameras, and a unique client_id and topic_prefix though share the same mqtt server and user.
Both are on the same swarm overlay network as mqtt and homeassistant, but with different hostnames: frigate, and frigatemm.
Config

record:
  enabled: True
  retain_days: 0
  events:
    max_seconds: 1800
    pre_capture: 10
    post_capture: 10
    retain:
      default: 300
birdseye:
  enabled: true
  mode: motion
snapshots:
  enabled: True
rtmp:
  enabled: false
mqtt:
  host: mqtt
  topic_prefix: frigatemm (or frigate)
  client_id: frigatemm (or frigate)
  port: 1883
  user: redacted
  password: redacted
detect:
  fps: 5
  enabled: True
  max_disappeared: 55
database:
  path: /media/frigate.db
cameras:
...

Describe the bug
Home assistant threw two connection errors, both twice, all at the same time, each referencing one of the frigate instances as un-connectable.
Home assistant then shows both Frigate integrations as having the same list of devices and entities, the missing entities are no longer listed (even if referenced by groups/automation) and the new duplicate entities all have a _2 appended.
So far it's happened twice, both after a day or two of uptime, and has always ended up showing only the devices of the second frigate instance configured, frigatemm.
Removing and re-adding either integration does not restore the correct devices/entities.
Restarting the home assistant server sometimes fixes the devices listed, but sometimes even after removing the integration and restarting home assistant re-adding the integrations still only find the devices of the frigatemm instance, even if only re-adding the frigate hostname instance.
Both frigate instances are accessible from their webui, and the only commonality between their logs is warnings about recording disk may be too slow, many more so on frigate which is overloaded than the couple of warnings on frigatemm.
Debug log

Home Assistant logs:

homeassistant    | 2021-12-18 18:16:01 DEBUG (MainThread) [custom_components.frigate] Finished fetching frigate data in 0.018 seconds (success: True)
homeassistant    | 2021-12-18 18:16:01 DEBUG (MainThread) [custom_components.frigate] Finished fetching frigate data in 0.020 seconds (success: True)
homeassistant    | 2021-12-18 18:16:16 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://frigate:5000/api/stats:
homeassistant    | 2021-12-18 18:16:16 ERROR (MainThread) [custom_components.frigate] Error fetching frigate data:
homeassistant    | 2021-12-18 18:16:16 DEBUG (MainThread) [custom_components.frigate] Finished fetching frigate data in 10.002 seconds (success: False)
homeassistant    | 2021-12-18 18:16:16 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://frigatemm:5000/api/stats:
homeassistant    | 2021-12-18 18:16:16 ERROR (MainThread) [custom_components.frigate] Error fetching frigate data:
homeassistant    | 2021-12-18 18:16:16 DEBUG (MainThread) [custom_components.frigate] Finished fetching frigate data in 10.004 seconds (success: False)
homeassistant    | 2021-12-18 18:16:21 INFO (MainThread) [custom_components.frigate] Fetching frigate data recovered
homeassistant    | 2021-12-18 18:16:21 DEBUG (MainThread) [custom_components.frigate] Finished fetching frigate data in 0.022 seconds (success: True)
homeassistant    | 2021-12-18 18:16:21 INFO (MainThread) [custom_components.frigate] Fetching frigate data recovered
homeassistant    | 2021-12-18 18:16:21 DEBUG (MainThread) [custom_components.frigate] Finished fetching frigate data in 0.034 seconds (success: True)
homeassistant    | 2021-12-18 18:16:26 DEBUG (MainThread) [custom_components.frigate] Finished fetching frigate data in 0.021 seconds (success: True)
homeassistant    | 2021-12-18 18:16:26 DEBUG (MainThread) [custom_components.frigate] Finished fetching frigate data in 0.024 seconds (success: True)

Maybe a hass bug? Hasn't happened in awhile on 2021.12.7.

Maybe a hass bug? Hasn't happened in awhile on 2021.12.7.

@Firerouge -- this is an odd one, have not seen that before. Does seem likely this is more a HA issue than an integration one, although it could be either.  Have you still not seen this recently?

@Firerouge -- Does seem likely this is more a HA issue than an integration one, although it could be either.  Have you still not seen this recently?

I'm using the latest stable tagged release from dockerhub. 2021.12.9 as of writing. Frigate instances are both on separate computers in a docker swarm, using an encrypted overlay network for interconnecting/dns.
It doesn't seem to happen very often anymore, hasn't happened spontaneously while running like had happened initially. I still always check it after a restart, as even in this latest version, occasionally after restarting it'll have happened.
It's never once been the second configured URL/integration becoming the first, when it happens, both integrations continue to show their correct URLs, but when clicked to inspect the first will list the devices and entities of the second.
A restart will usually fix it, though I was once unlucky and took 3 restarts before it was correct.

Closed, figure out the underlying cause and it's neither Frigate or Home Assistant
I want to note that when using multiple instances of frigate with docker-compose that it's critical that their service names be different.
It's not sufficient to set only container_name and/or hostname of the service to something unique, as the docker DNS will continue to resolve both container_name and the service name as valid URLs, so if either instance has the same name in any of those fields, it's a coinflip which answers the response.


how to set time pattern support microsecond

MySQL/MariaDB time, timestamp support microseconds(10^-6 sec)
I tried to set time pattern to HH:mm:ss.SSSSSS, but it didn't work well
what should I set ?

You should use .ffffff for miliseconds (see timestamp format).

it seems not work for TIME(6) datatype

Yes, you are right. I tested it on db2 and it doesn't work for time fields only for timestamp. The SSS (or SSSSSS) returns only milliseconds.
Can it be jdbc driver related?

Yes, this is JDBC driver specific. Can't fix this from DBeaver side.


Can't control wheel for vertical speed or flight level control with mouse.

same problem with vr or not, impossible to toggle off the yoke too

Seems the Yoke issue is also happening with the Default MSFS TBM not just in this mod.

Seeing the same issues here.  Has anyone confirmed whether the VS wheel works with the stock TBM930?  Hate to remove this mod but I want that VS wheel working!

To answer my own question, deleting the mod and using the stock aircraft solved the VS wheel issue and the inability to hide the yoke.

Fixed in v0.6.2


Warning: componentWillReceiveProps has been renamed

When I implemented the Control, LocalForm, Errors in my react application. I'm getting the following warning in console:
Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
Please update the following components: Control, Form
Can you tell me how to resolve this warning?  Please update.

That warning is coming from React due to usage of componentWillReceiveProps in this library - React are planning to rename this method in v17. This library will need to be updated and re-released with a fix for this warning to work with React 17 - but until that is released, you can ignore this. More info here: https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html

Thanks, @rikkit for the information.


feat: add math/base/special/round10f

Progresses #649
Description

adds math/base/special/round10f, which would be the single-precision equivalent for math/base/special/round10.

This pull request:

Progresses: https://github.com/stdlib-js/stdlib/issues/649

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines

@stdlib-js/reviewers

@vivekmaurya001 Thanks for working on this, but we would first need to implement math/base/special/powf, in order to move ahead with this.