Vue comments are broken

The submission from a month ago still seems to be correct
Expected behaviour (filetype=vue)
<style>
/* display: flex; */
</style>

Actual behaviour:
<style>
<!-- display: flex;  -->
</style>

Please provide proper steps.

Please provide proper steps.

It was working fine before, after I did an update this problem occurs

Working just fine for me. Make sure you are on 0.9 stable.

Working just fine for me.  I am on nvim 0.9 and everything is working fine for me.

I also using 0.9
NVIM v0.9.0-dev
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3

It seems you are a nightly user. Would you mind updating to the latest nightly?

It seems you are a nightly user. Would you mind updating to the latest nightly?

OK,i will try,thank you so much😊

Now it works!
<style>
/* display: flex; */
</style>

but use scss work bad
<style lang="scss" scoped>
<!-- display: flex;  -->
</style>

Do you have scss parser installed?

Do you have scss parser installed?

i install nvim-ts-context-commentstring and it worked fine,thanks!🎉🎉🎉


When upgrading to 3.0.3 from 2.18.1, invalid signature is returned from coinbase

Are there any upgrade steps? I can reproduce this locally by switching the versions.

Hi @jdgriffith, can you please post the code which is throwing this error?

I also noticed you very recently created code for mutually excluding status and product_id. It's very helpful to be able to use both together so curious the thought there.
For some reason, this works:

With v3.0.3 order.getOrders cannot be used anymore with status and product_id. These properties are mutually exclusive. I suggest to fetch by status and to filter the response by product_id in your code (using Array.filter).

Ok I will do that. I'm not sure that explains the invalid signature though?

Verified locally I'm still receiving invalid signature when not using the product_id.
I think* this is happening anytime I pass status to the function.
    const { data: orders } = await this.client.rest.order.getOrders({
      limit,
      status: [OrderStatus.ACTIVE, OrderStatus.PENDING, OrderStatus.OPEN]
    })

vs
    const { data: orders } = await this.client.rest.order.getOrders({
      limit
    })

The last code example fetches data without a hitch.

I was testing it actually. Can you test what happens when just using status: ['all']?

This also fails for me.
    const { data: orders } = await this.client.rest.order.getOrders({
      limit,
      status: ['all']
    })

currentUrl: 'https://api.pro.coinbase.com/orders?status=all&limit=10'

data: { message: 'invalid signature' }

Something is incorrect when generating the signature for these calls (and including a status array).

{
  url: '/orders?status=all',
  method: 'get',
  headers: {
    common: { Accept: 'application/json, text/plain, */*' },
    delete: {},
    get: {},
    head: {},
    post: { 'Content-Type': 'application/x-www-form-urlencoded' },
    put: { 'Content-Type': 'application/x-www-form-urlencoded' },
    patch: { 'Content-Type': 'application/x-www-form-urlencoded' }
  },
  params: { limit: 10 },
  baseURL: 'https://api.pro.coinbase.com',
  transformRequest: [ [Function: transformRequest] ],
  transformResponse: [ [Function: transformResponse] ],
  timeout: 50000,
  adapter: [Function: httpAdapter],
  xsrfCookieName: 'XSRF-TOKEN',
  xsrfHeaderName: 'X-XSRF-TOKEN',
  maxContentLength: -1,
  maxBodyLength: -1,
  validateStatus: [Function: validateStatus]
}

Your config.params does not include status from the query string for stringifying when doing the signing operation. I think this is where it is falling apart.

Hmm, I was guessing that status is not needed in the params object as it's part of the url /orders?status=all.

Yeah - looks like this might work if you changed this code from manually adding status to the query string:
    if ((query as OrderListByStatus)?.status) {
      status = '?' + (query as OrderListByStatus).status!.map(s => `status=${s}`).join('&');
      delete (query as OrderListByStatus).status;
    }
    const response = await this.apiClient.get<Order[]>(`${resource}${status}`, {
      params: query,
    });

Might want to use something like:
https://nodejs.org/api/querystring.html#querystring_querystring_stringify_obj_sep_eq_options

and add a paramsSerializer to the getOrders request?
https://stackoverflow.com/questions/49944387/how-to-correctly-use-axios-params-with-arrays
Up to you but seems like there are some straightforward ways to get around the serializing of array data for axios.

Thanks for your immense research. Can you try to create a PR for that? I can also help by adding the required tests for it.

Created a PR: https://github.com/bennycode/coinbase-pro-node/pull/478

Also, on the mutually exclusive topic, I know all too well about tripping up other people with that. Just in the last month I created some mutually exclusive env vars, complete with a fatal error when both were injected and it completely tripped up our dev-ops guys 😂 .
Definitely not against mutually exclusive control flow in programming - I'm just not understanding why you chose it here.

I chose it because I wanted to reduce the complexity as I couldn't grasp why it's failing when setting both props. So I thought it's good to have a defined state where one or the other is set.
Thanks to your support, it's now possible to set both params at the same time. Fix just got released with v3.0.4.

oh that's awesome! Thank you sir!


Unhide air gap and alphabetize flags

What this PR does / why we need it:

I realized the air gap flags are still hidden, so I unhide those. I also alphabetized the CLI flags in the help menus so they're easier to read. The CIDR and proxy flags are from functions, so those didn't get alphabetized. Ultimately I'd like them to be alphabetized, but I didn't bother to rework those functions.
Which issue(s) this PR fixes:

Does this PR require a test?

NONE
Does this PR require a release note?

Unhides the `--airgap-bundle` flag for the `install`, `join`, and `restore` commands.

Does this PR require documentation?

NONE

For example:


TextInput in Android doesn't respect the selection attribute and places the caret at the beginning

Description
Create a TextInput component with value and selection attributes, then programmatically focus it after a delay. You'll find the caret at the beginning instead of at the specified selection.
This is only reproducible under the New Arch.
Steps to reproduce

Clone reproducer or use the code below.

// App.tsx

import { TextInput } from 'react-native';
import { useEffect, useRef} from 'react';

export default function App() {
  const input = useRef(null);
  useEffect(() => { setTimeout(() => input.current?.focus(), 1000); }, []);
  return <TextInput ref={input} value='1.00' selection={{start: 4, end: 4}} />;
}

Build the app with New Arch enabled and run it on Android.

Wait a second.

Expected result: The caret is at the end.
Actual result: The caret is at the beginning.
React Native Version
0.75.4
Affected Platforms
Runtime - Android
Output of npx react-native info
System:
  OS: Linux 5.15 Linux Mint 21.3 (Virginia)
  CPU: (6) x64 AMD Ryzen 5 3500X 6-Core Processor
  Memory: 37.72 GB / 39.16 GB
  Shell:
    version: 5.1.16
    path: /bin/bash
Binaries:
  Node:
    version: 20.15.1
    path: ~/.nvm/versions/node/v20.15.1/bin/node
  Yarn:
    version: 3.6.4
    path: ~/.nvm/versions/node/v20.15.1/bin/yarn
  npm:
    version: 10.7.0
    path: ~/.nvm/versions/node/v20.15.1/bin/npm
  Watchman:
    version: 20231008.002904.0
    path: /usr/local/bin/watchman
SDKs:
  Android SDK:
    API Levels:
      - "31"
      - "33"
      - "34"
    Build Tools:
      - 33.0.1
      - 34.0.0
    System Images:
      - android-34 | Intel x86_64 Atom
      - android-34 | Google APIs Intel x86_64 Atom
    Android NDK: Not Found
IDEs:
  Android Studio: Not Found
Languages:
  Java:
    version: 17.0.12
    path: /usr/bin/javac
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Stacktrace or Logs
N/A

Reproducer
https://github.com/QichenZhu/reproducer-react-native-textinput.git
Screenshots and Videos
https://github.com/user-attachments/assets/b0e2f80d-f76d-4c32-b410-3c460aed404b

@QichenZhu Is this happening only on Android? Did you get a chance to check on iOS?

@shubhamguptadream11 No, it works fine on iOS.
https://github.com/user-attachments/assets/0802560c-ca6f-4057-b5d1-d96ec012c59d

In my testing, the selection changed after this line.
https://github.com/facebook/react-native/blob/699f73a6b0734fe716b01d263e9579bca38c4652/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/views/textinput/ReactEditText.java#L1060
A possible fix is to save and restore the selection before and after it.
int prevSelectionStart = getSelectionStart();
int prevSelectionEnd = getSelectionEnd();
super.setTextIsSelectable(true);
setSelection(prevSelectionStart, prevSelectionEnd);

I can create a PR if you're interested.

Yeah sure go ahead!


WebSharper project no longer builds due to Paket changes to project file

This happens with command line paket or with Paket for Visual Studio. There were two updates to Paket for Visual Studio recently. I'm not sure which one started this problem.
I have a WebSharper project, and if I understand correctly the WebSharper compiler is run by the following step at the end of the project file:
<Import Project="..\packages\WebSharper\build\$(__paket__WebSharper_targets).targets" Condition="Exists('..\packages\WebSharper\build\$(__paket__WebSharper_targets).targets')" Label="Paket" />

The __paket__WebSharper_targets property is set earlier in the file:
  <Choose>
    <When Condition="$(TargetFrameworkIdentifier) == '.NETFramework' And $(TargetFrameworkVersion) == 'v4.6.1'">
      <PropertyGroup>
        <__paket__WebSharper_targets>WebSharper</__paket__WebSharper_targets>
      </PropertyGroup>
    </When>
  </Choose>

This <Choose> code has now moved. It used to be quite near the end of the project file, not far from the <Import> statement that uses it, and now it is much earlier and now appears before this line:
<Import Project="$(FSharpTargetsPath)" />

I am not very familiar with how MSBuild works, so I'm only guessing that this line is significant.
The result is that the F# project compiles, but the WebSharper compiler is not started.

I just pushed another Paket.VisualStudio update that brings the addin in
sync with paket.exe
On Apr 11, 2016 6:56 PM, "Bananas-Are-Yellow"<EMAIL_ADDRESS>wrote:

This happens with command line paket or with Paket for Visual Studio.
There were two updates to Paket for Visual Studio recently. I'm not sure
which one started this problem.
I have a WebSharper project, and if I understand correctly the WebSharper
compiler is run by the following step at the end of the project file:

The __paket__WebSharper_targets property is set earlier in the file:

        <__paket__WebSharper_targets>WebSharper

This  code has now moved. It used to be quite near the end of the
project file, not far from the  statement that uses it, and now
it is much earlier and now appears before this line:

I am not very familiar with how MSBuild works, so I'm only guessing that
this line is significant.
The result is that the F# project compiles, but the WebSharper compiler is
not started.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1595

My Visual Studio (Tools / Extensions and Updates command) is not showing a new version yet, but I just got the latest paket.exe (v2.58.14), and updated from the command line, and I can confirm that it now builds correctly.
Thanks.

The new version of Paket for Visual Studio is now showing. I guess it takes 15 minutes or so for it to appear.


An error occurs when executing "Deploy to Web App..." command from Command Palette

OS: All
Azure Resources extension: 20230215.1
App Service Extension Version: 0.24.7
Repro Steps:

Open the nodejs-docs-hello-world project in VS Code.
F1 -> Azure App Service: Deploy to Web App.... -> Select the above project -> Select a web app to deploy.
Check whether succeeds to deploy the project to web app.

Expect:
Succeed to deploy the project to web app.
Actual:
An error occurs when executing "Deploy to Web App..." command from Command Palette.

More Info:
This issue does not reproduce when deploying the project from context menu.

I'm unable to reproduce this, but this seems like a critical issue that needs fixing.
Can you try reproducing this again? Are there any other details you can provide to help me reproduce this?

@alexweininger This issue reproduces on the yesterday's latest main branch Resource Groups extension build 20230215.1.
Verified this issue on the latest main branch Resource Groups extension build 20230215.10, it is no longer reproduce. Close it.

@alexweininger This issue reproduces on the yesterday's latest main branch Resource Groups extension build 20230215.1.
Verified this issue on the latest main branch Resource Groups extension build 20230215.10, it is no longer reproduce. Close it.

Thank you!


Where to get prior information of Starting cell for Margaret?

I observed that Margaret uses Palantir_pseudotime information and requires user to have prior knowledge of starting cell. Is there an inbuilt function to identify which cells could be used as starting cells or we have to run some other tools to find that out? I think choosing any cell arbitrarily as starting point will be wrong!!

The starting cell needs to be specified as an input for Margaret. It is possible to identify the starting cells usually using some exploratory analysis like clustering (and then projecting expressions of known marker genes in start cells on the 2d-embedding visualization) or from prior biological knowledge about the dataset you are working with. Choosing an arbitrary starting cell will likely result in incorrect pseudotime and trajectory analysis


msg: parameter #1  is not type UnicodeString.

Just installed this package, get my telegram-cli running by
/bin/telegram-cli --json -W -d -P 4458

And when i run this example:
https://github.com/luckydonald/pytg/blob/master/examples/command_send_message.py
I got this:
(i changed only my username)
Traceback (most recent call last):
  File "command_send_message.py", line 19, in <module>
    main()
  File "command_send_message.py", line 14, in main
    res = sender.msg("@timhok", "Hello!")
  File "/usr/local/lib/python2.7/dist-packages/pytg/sender.py", line 630, in command_alias
    return self.execute_function(command_name, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/pytg/sender.py", line 274, in execute_function
    command_name, new_args = self._validate_input(function_name, arguments)
  File "/usr/local/lib/python2.7/dist-packages/pytg/sender.py", line 414, in _validate_input
    function_name=function_name, number=i, type=func_type.__class__.__name__, param=str(func_type), error=str(err)))
ValueError: Error in function msg: parameter #1 <text> is not type UnicodeString. (Not a string.)

I also tried unicode strings with no success:
pytg.exceptions.FailException: Error 38: u'can not parse arg #1' (command u"[disable_preview] msg timhok 'Hello'\n")

I realize that maybe pytg sends msg command without "@" symbol in name, and last version of telegram-cli (version 1.4.1, tgl version 2.1.0) does not support that:
timhok@srv04:~# echo msg timhok hi | nc <IP_ADDRESS> 4458
ANSWER 70
{"result": "FAIL", "error_code": 38, "error": "can not parse arg #1"}

^C
timhok@srv04:~# echo msg @timhok hi | nc <IP_ADDRESS> 4458
ANSWER 22
{"result": "SUCCESS"}

^C

FYI: pytg usually starts the CLI with this arguments. Does that json output differ?

Hey, I have the exact same problem, tried the arguments, which doesn't help. Anything else?

You have to decode the text before sending as it expects unicode text:
res = sender.msg("@nick", "hi".decode("utf-8"))
will make it

What is your python version? 2.7?

Yes in that example I used the 2.7

You can probably also use u"hi"  insead of "hi".decode(...)

using u"msg' or "msg".decode("utf-8") fixed the error for me,
but now I get # TODO remove me NoResponse: [disable_preview] msg @contact 'msg :)'

Sorry, you didn't write with version of python on what OS you are running.

If using Python 2, be sure you are using Unicode strings (unicode), not the normal (binary) str.
Or just use Python 3.

I'm Using Ubuntu 16.04 LTS And Python 2.7

I'm getting the same error with python 3.5.2 on Linux-4.4.0-75-generic-x86_64-with-Ubuntu-16.04-xenial,
Traceback (most recent call last):
  File "cli.py", line 5, in <module>
    res = sender.send_msg('@bitwisepi', u"Testing, does this thing work?")
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 630, in command_alias
    return self.execute_function(command_name, *args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 354, in execute_function
    raise e
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 351, in execute_function
    return result_parser(message)
  File "/usr/local/lib/python3.5/dist-packages/pytg/result_parser.py", line 55, in success_fail
    raise FailException(json.error_code, json.error)
pytg.exceptions.FailException: Error 38: 'can not parse arg #1' (command "[disable_preview] msg @bitwisepi 'Testing, does this thing work?'\n")

Tried passing both arguments as unicode strings, still throws an error.

Which cli version (The commit hash?) are you using?

Should be 6547c0b21b977b327b3c5e8142963f4bc246187a, the most recent one
I actually fixed this error by adding quotes before and after the peer value in my msg() function, but it still returns the same error as described in #81, with the "can't find user telegramd to switch to" value


Update PySB's Docker setup

Use jupyter/scipy-notebook base image (ipython/scipyserver is deprecated)
Update BioNetGen to 2.2.6-stable
Use non-privileged user within container

:+1: but I'm going to rebase this against master to keep the history cleaner.

By the way, the github "fixes/closes/resolves #xxx" trick to close an issue from a commit message or PR does also work to close PRs. Handy.


Revert "Revert "Renamed google_benchmark submodule to benchmark""

Reverts grpc/grpc#8950.  Re-do of #8851.  Won't merge until after fixit.

Test this please

Looks like this breaks Jenkins

@dgquintas, you're the original author of this change.  Can you fix the jenkins problems?  Thanks!

yes, on it.

The original PR had some issues. I've created a brand new PR, https://github.com/grpc/grpc/pull/8986 This one can be closed.


Polish BuildScanConfigurationPlugin

by refining formating, imports
and removing unecessary parameters, receivers, parenthesis
and properly closing streams
and preferring Kotlin lambda over Runnable
and simpliflying boolean expressions
and removing unecessary explicit casts

Feedback build https://builds.gradle.org/viewQueued.html?itemId=11278971


Agent unable to access vector results

Describe the bug
The LLM is to unable to access the results from the vector search, there seems to be a mismatch between the JSON schema and the format method for vector search results in the agent method/endpoint. The inconsistency is on the text and metadata.text properties.
The result passed to the llm is filled with only "N/A"s. As a result, the final response does not include the relevant context.
To Reproduce
Steps to reproduce the behavior:

Perform an operation with an agent, via the dashboard or the sdk
Observe that the response lacks the context that should be present.

Expected behavior
The format method should correctly access and format the text field from the vector search results.
Code snippets
JSON Schema:
class Config:
    json_schema_extra = {
        "fragment_id": "c68dc72e-fc23-5452-8f49-d7bd46088a96",
        "extraction_id": "3f3d47f3-8baf-58eb-8bc2-0171fb1c6e09",
        "document_id": "3e157b3a-8469-51db-90d9-52e7d896b49b",
        "user_id": "2acb499e-8428-543b-bd85-0d9098718220",
        "group_ids": [],
        "score": 0.23943702876567796,
        "text": "Example text from the document",
        "metadata": {
            "title": "example_document.pdf",
            "associatedQuery": "What is the capital of France?",
        },
    }

Format Method:
def format_search_results_for_llm(
    results: list[VectorSearchResult],
) -> str:
    formatted_results = ""
    for i, result in enumerate(results):
        text = result.metadata.get("text", "N/A")
        formatted_results += f"{i+1}. {text}\n"
    return formatted_results

Proposed solution
Perhaps there could a more effective way of giving the results to the llm (including metadata/filename/order/etc...), at minimum it should include the text itself so this could be a quick fix:
def format_search_results_for_llm(
    results: list[VectorSearchResult],
) -> str:
    formatted_results = ""
    for i, result in enumerate(results):
        text = result.text  # Access text directly from result
        formatted_results += f"{i+1}. {text}\n"
    return formatted_results

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Great catch, pushing an update today.


ClusterLoader - Increasing apiserver cpu limit to 2.5

ref https://github.com/kubernetes/kubernetes/issues/75509

/assign @wojtek-t

Can we first check with PR author that the increase is expected? If so, I'm fine with bumping, if not, we should understand it.

/hold
There is a PR that should fix the issue - https://github.com/kubernetes/kubernetes/pull/75570

/close
kubernetes/kubernetes#75570 fixed the issue


[BUG] How many epoch should we finetune with lora?

How many epoch should we finetune with lora?

Fit with the size of your dataset.

Suppose I have a multi-speakers dataset, which contains 6 hours in total. What is your suggestion in term of this situation?


Fix install command in README

The command would install the binary in usr/local/bin in the current working directory, not in /usr/local/bin.
In order to install to /usr/local/bin you need sudo, so I added that as well

Thank you for your contribution!


Add ledger updates to replay events

The bulk of this PR is changing the on-disk part of the LedgerDB to be parameterized over blk, just like the LgrDB. This brings the two closer together, and so this would be a good basis for unifying the two, although that isn't done in this PR yet. We do simplify the QSM tests for the legder DB (the whole LUT business is gone, see commit message), something that was long overdue. But the main goal of this PR was to be able to add LedgerUpdates to the TraceReplayEvent; this is particularly useful when using the DB analyser replaying all blocks, as we can then also see some information about how the ledger is evolving when it does that (since no chain selection happens during this replay, the normal AddedToCurrentChain trace message does not occur).

bors merge


Fix race condition in ADS

So basically these two tests are doing this 3 second sleep for a full push to be triggered. This is bad from a testing standpoint (because we never want to sleep if possible) and leads to flakes - this test has been super flaky. Additionally, this is not really testing what we want - Envoy has no such 3 second sleep.
When removing this sleep, the test fails pretty often. What is happening here is a race between connection being added and a full push being triggered.
Normally we expect:

We send RDS request
RDS request completes
We add the connection
We send a full push to 1 connections

But because of a race we get:

We send RDS request
RDS request completes
We add the connection
We send a full push to 0 connections

This can be fixed by adding the connection before we try to respond to xDS requests. The added connection is not used anywhere in that code, so doing it first or last is not important.
This makes the problem much rarer, but there is still another race. When we send a response, we set the nonce for the response. However, we return from the send() function BEFORE we set the nonce asynchronously. This introduces a race where the next request comes in before we finish setting the nonce, and it is rejected. To fix this, we simply return from send only after we have set the nonce.
Fixes: https://github.com/istio/istio/issues/14504
Fixes: https://github.com/istio/istio/issues/11022
Fixes: https://github.com/istio/istio/issues/15822

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio
af50a54a402145374d361d1edb9e96c68bb987d2
link
/test gencheck_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio
af50a54a402145374d361d1edb9e96c68bb987d2
link
/test gencheck_istio

lint_istio
af50a54a402145374d361d1edb9e96c68bb987d2
link
/test lint_istio

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

This can be fixed by adding the connection before we try to respond to xDS requests. The added connection is not used anywhere in that code, so doing it first or last is not important.

@howardjohn This matters i think, if we add connection once a proxy connects, there may be full push triggered before the initial xDS requests. I am concerned whether this will introduce other races other than the redundant pushes.

@hzxuzhonghu I am pretty sure there will never be a full push before the request. First of all, even today we only guarantee the first request (CDS) completes, not all of them. But also, if you look at the select in this function, the XDS request will block the full push, so behavior should remain the same I think.

Could we add connection before the first rds pushes?


Feature Request - Parsing Tenable Nessus

Hello,
Would it be possible to add the feature that would allow aquatone to take a .nessus file and pull out URLs

I could do that if you provide me one file as an example.

I could do that if you provide me one file as an example.

Here's a sample nessus xml file https://github.com/DefectDojo/sample-scan-files/tree/master/nessus
I tried importing it to latest version of nessus and it worked.
I also found this post on parsing nessus xml files that might be helpful https://avleonov.com/2020/03/09/parsing-nessus-v2-xml-reports-with-python/
Another screenshot tool eyewitness currently has this implemented as well as nmap parsing here
https://github.com/FortyNorthSecurity/EyeWitness/blob/b4866e66bc960c318f17ec00876fff052cbb9d76/Python/modules/helpers.py#L80


Make sure we return the gossip data with the correct order.

Fixes #1603

Closed in favour of #1605


multiple w215's only last is used

I have 3 w215's setup as accessories and only the last one seems to work.  The other three register, and show up in home kit, but turning any of them on always turns the last switch on.  Same with turning it off.
Is it a config problem or is it a limitation?  I'd appreciate any help you can offer. Here is my config:
config.json
{
"bridge":
{
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"accessories": [
{
"accessory": "w215",
"name": "Dlink1",
"host": "<IP_ADDRESS>",
"username": "admin",
"password": "edited"
},
{
"accessory": "w215",
"name": "Dlink2",
"host": "<IP_ADDRESS>",
"username": "admin",
"password": "edited"
},
{
"accessory": "w215",
"name": "Dlink3",
"host": "<IP_ADDRESS>",
"username": "admin",
"password": "edited"
}
]
}

I tried making the password invalid on the first entry, and home bridge loaded without error.  I then tried making the password invalid on the last accessory entry, and it broke.  It looks like only the last accessory entry credentials and IP are being used.

Hi, I think that this is not related to the code as such. You probably select wrong IP address from your config.json file as you mentioned in your last post. The code is supposed to communicate with only one socket. If you want multiple sessions you should modify the code.
Regards Pavel

You can see from the config I posted that each switch is on a different IP with a different password.  I have verified the IPs from my router, they are setup to be static.  How can I modify the config file to allow for more than one switch?

Hi,
as I said this code is intended to communicate with one target only. There is no config file so I can't tell what is wrong with your code. You can share your code on github and send me the link so I can take a look.
Since it is not related to my code I close the issue.
Pavel

I solved the issue by running multiple copies of homebridge, one for each switch.


[WIP] BoxedUint: even GCD support

Tests are currently failing due to the handling of zero as one of the values.
I'm thinking the return value of CtOption is largely a vestige of when even numbers weren't supported, and we can change it to be infallible now, similar to num-bigint.
I'm uncertain why we aren't seeing similar failures in the Uint::gcd proptests as I expect it to have a similar issue.

agreed on removing ctoption 👍

Opened #619 to make Uint::gcd infallible, then when that's merged I'll do a similar treatment here


Add travis

Would it make sense to create a matrix of these 2 configurations, so that they appear as separate "jobs" in Travis?

Yes, but maybe after we merge ets-tracker?

merge this to get going
merge ets tracker
adapt travis yml to use N matrices

Hmm, I already merged ets-tracker. Is this an incorrect order?

@studzien I'm off to bed. Feel free to rebase this, add the matrix thingie, and merge :)


Update the ExAC project URL for the population genotype page

Hi @ens-hsr,
Is something wrong with the PR I did ?

Sorry, no nothing wrong with the commit. I had to remove the postreleasefix/87 branch, and since your pull request was against that branch, I think GitHub closed it automatically. I have reopened it by created the branch again.

No problem @ens-hsr !


ROX-25048: S3 compatible integration forms

Description

This adds a new type of backup integration type meant for non-AWS S3 compatible storage providers (e.g. MinIO, Cloudflare R2, Backblaze B2, ...). See https://github.com/stackrox/stackrox/pull/11877 and https://github.com/stackrox/stackrox/pull/11878 for the corresponding backend changes.
I have attempted to follow the patterns from the existing S3 and GCS back integrations types. Changelog and documentation will be done outside of this PR. I'm also planning a follow up to create a UI e2e test for these changes.
Config changes that are different from AWS S3 plugin:

container IAM role is only supported for AWS S3 for now.
S3 compatible plugin may configure a URL style setting.

User-facing documentation
(must be 2 items and both must be checked)

[ ] CHANGELOG is updated
[x] CHANGELOG update is not needed
[ ] Documentation PR is created and linked above
[x] Documentation is not needed

Testing

[x] inspected CI results

Automated testing
(must be at least 1 item and all items must be checked)

[ ] added unit tests
[ ] added e2e tests
[ ] added regression tests
[ ] added compatibility tests
[ ] modified existing tests
[x] contributed no automated tests

How I validated my change

see screenshots

/retest


Linux permissions issues

We need to ensure that the user has execute permissions for go-spacemesh process. This needs to be part of the installer.
We need to make sure that the smapp process has permissions to create the POST folder. The POST folder should be in the app data folder. Currently, post fails on linux as it tries to create a dir at root.

Likely not reproducible with the latest path changes.


release: v1.3.1

Description
Change log for v1.3.1
Task Item
#minor

Screenshots

Coverage remained the same at 54.897% when pulling 8138c4529089dba1db7eb4dff34e31d306e4a0f0 on zhixzhan/v1.3.1 into 70c0d7b85a9c895c9cc688e6c959f7da1b59f84c on main.

Coverage remained the same at 54.897% when pulling 8138c4529089dba1db7eb4dff34e31d306e4a0f0 on zhixzhan/v1.3.1 into 70c0d7b85a9c895c9cc688e6c959f7da1b59f84c on main.


keyNotInSchema for nested boolean field

Here's an excerpt from my schema:
 safety: {type: Object, optional: true},
 "safety.carOff": {type: Boolean, optional: true, srf: {type: TextInput}},
 "safety.safePlace": {type: Boolean, optional: true, srf: {type: TextInput}},
 "safety.medicalAttention": {type: Boolean, optional: true, srf: {type: TextInput}},
 "safety.call911": {type: Boolean, optional: true, srf: {type: TextInput}},
 "safety.waitForPolice": {type: Boolean, optional: true, srf: {type: TextInput}},

Any reason trying to set safety.carOff would give me keyNotInSchema errors?
Full error:
updated {"error":400,"reason":"INVALID","details":"[{\"name\":\"safety.carOff\",\"type\":\"keyNotInSchema\",\"value\":true}]","message":"INVALID [400]","errorType":"Meteor.Error"} null

@JulianKingman, no, what is your exact modifier that is producing this error?

collection.update(doc._id, { $set: {safety.carOff: true}}, (err, res) => {
  console.log("updated", err, res);
});

OK, I found the problem. I added the safety property in a second schema definition. I'm not sure why that caused the problem, maybe because of a faulty import somewhere, or maybe something else. In any case, it's fixed. Thanks for your help :)


Use multistage build to copy into distroless image.

The idea is that now that the runtime image doesn't contain an OS distribution, including package manager, we always want to use a multi-stage build to get a folder set up with what we need in one image that uses alpine or debian, and then copy into the runtime image using COPY --from=.
Fixes #8

It's too bad nowadays we all assume caffeine can replace the productivity of real sleep / dreams ;)

hehe


Update faqs.md

Caught the out of use CloudKnox and changed to Permissions Management.

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

#sign-off

@Writethedocs-MS: I'm sorry - only the author of this article, @kenwith, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Hi @Writethedocs-MS
Can you make future content updates in the private repo? That way, you can sign off on PRs, and your PRs can benefit from validation.
I'll merge this PR now.
Thank you!

Hello -
Yes, I usually function that way. Friday was an exception.
Thanks!
Kat
From: Courtney Wales @.>
Sent: Monday, June 6, 2022 8:14 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Kat Campise (Aquent LLC) @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update faqs.md (PR #93911)
Hi @Writethedocs-MShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWritethedocs-MS&data=05|01|v-campisekat%40microsoft.com|2d3df2cb38104e4c7a8208da47cf1f83|72f988bf86f141af91ab2d7cd011db47|1|0|637901252161486287|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=JqEsqwSrKSyP9I%2FbEyP8rqvYK6AYfGvI6PUQaT3eA5M%3D&reserved=0
Can you make future content updates in the private repo? That way, you can sign off on PRs, and your PRs can benefit from validation.
I'll merge this PR now.
Thank you!

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F93911%23issuecomment-1147560176&data=05|01|v-campisekat%40microsoft.com|2d3df2cb38104e4c7a8208da47cf1f83|72f988bf86f141af91ab2d7cd011db47|1|0|637901252161486287|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=ORnv5e4Byezcw%2F2Plv9TgL3Dd57N8ECH%2FVZqGYYvlxY%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZBHG324YAJTLHGCSXZITO3VNYIR3ANCNFSM5X2MRPYQ&data=05|01|v-campisekat%40microsoft.com|2d3df2cb38104e4c7a8208da47cf1f83|72f988bf86f141af91ab2d7cd011db47|1|0|637901252161486287|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2FRXOHXulzMf4yCrB6StC17TS77F4mUjW0HbWU%2FRKZfY%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>


Crafting is crashing the game

I dont know if this is a Reborn Storage Problem or a refined storage problem, as it states both mod names in the log.
Tried to craft something using the Reborn Storage crafter multiblock and it crashes the game.
What you expected to happen: It to craft something.
Steps to reproduce:

Try to autocraft using the Reborn Storage Crafter

Minecraft: 1.12
Forge: 1.12-<IP_ADDRESS>2
Refined Storage: Does it on both 1.5.16 and 1.5.17

Does this issue occur on a server? [yes/no] IDK
https://pastebin.com/NMxZj6g3

This is not an Refined Storage issue (and I don't think this is a RebornStorage issue either).


How to install Step 2?

Well, Step 2: Install Stable-TS ... Run this command. ...
Where should I run this command?
In PowerShell? It does not work ... (The term 'pip' is not recognized ...)
In Python?  It does not work ... (invalid syntax)
In Resolve Console? It does not work ... (invalid syntax)

Well, the installer does not work.
I made complet new Windows 10 reainstal ...

Hey, I just updated the setup process which simplifies it down to one command and no download. Hopefully, it also fixes your problem.


Although it is managed through URL, don't you find it disgusting that there are so many packages with the same name as pkg_go_dev? Does it not infringe on the rights of the original author?

What is the URL of the page with the issue?
pkg_go_dev
What is your user agent?
..
Screenshot
Although it is managed through URL, don't you find it disgusting that there are so many packages with the same name as pkg_go_dev? Does it not infringe on the rights of the original author?
this  is  my     package search  function feature  made by  self

Related Issues

x/pkgsite: Search result title is wrong #53260 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)


Clean repo of unnecessary files

There are some leftover files from the old standalone Interact that are no longer necessary for the notebook extension.

Removed unutilized files


refactored code to improve readability

Changed demote keyword to removeUser to improve readability. Corresponding issue #848

Code charges are good.
Does not affect functionality.
:+1:

:+1:
Code works


Trolley.download() uncaught value error

dicomtrolley version: 3.0.1
Python version: 3.8

Description
Ran into this when downloading a specific corrupt DICOM dataset. The dataset has inproperly configured encapsulation of compressed pixeldata. pydicom dataset.save_as() on this dataset will raise the following:
ValueError: (7FE0,0010) Pixel Data has an undefined length indicating that it's compressed, but the data isn't encapsulated as required. See pydicom.encaps.encapsulate() for more information

Pydicom raising the exception is understandable; it cannot properly write this data. The problem is that ValueError is not typically caught at higher levels, and thus typically crashes the whole program.

Solution would be to catch this and transform it to a TrolleyError so that the error is easier to catch


Documentation update: Container DNS issues on Linux (With systemd-resolve)

The documentation for Auto-DNS mentions that for linux you can manually add <IP_ADDRESS> to your /etc/resolv.conf
I had difficulties with that setup, but was able to find another way of making it work.
1)
Do not manually edit /etc/resolv.conf (the file says "DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN").
Add those lines to this file: /etc/resolvconf/resolv.conf/head
And then run:
resolvconf --enable-updates
resolvconf -u

I still had dns troubles with this, but I was able to find out how to get docker to use both the bind server, and your dhcp given dns servers:
Add this to your /etc/docker/daemon.json (replace the <IP_ADDRESS> with the 127* address that your resolv.conf file has:
{
    "dns" : ["<IP_ADDRESS>"]
}

Then, in the /etc/resolvconf/resolv.conf/head add:
nameserver <IP_ADDRESS>

These two things combined let me use my networks dns via systemd-resolved, and the bind container's dns.
Note: This is specifically for linux, where the system is running its own resolve server (i.e.: systemd-resolv)
Thanks for the work on this great tool.

Good job!!! I will update the documentation. Can you also let me know what Linux/Distribution you're using.

This is from Ubuntu 17.10, but any distribution that uses systemd-resolved should have this same affect. (Ubuntu started in 16.10)

@science695 I just checked. I am using a Debian system, but the files you have mentioned are not available on my system. In the first the directory does not even exist.
$ ls -l /etc/resolvconf/
total 4
drwxr-xr-x 2 root root 4096 Mar 27 13:11 update-libc.d/

$  ls -l /etc/docker/
total 4
-rw------- 1 root root 244 Jan  8 16:02 key.json

What about adding the following line at the very top to /etc/dhcp/dhclient.conf
prepend domain-name-servers <IP_ADDRESS>;

and restart network manager afterwards via
$ sudo service network-manager restart

http://devilbox.readthedocs.io/en/latest/configuration-global/auto-dns.html#linux
Please re-open in case this does not work

That would appear to be proper instructions if your particular flavor of linux is not using systemd-resolve.
I would recommend including both sets of instructions labeled as With vs Without Systemd-resolve.

OK, looks like I somehow misunderstood that and took it for systemd in general instead of systemd-resolve.  Thanks for clarifying.

If I shutdown system-resolved and made those updates, it seems to be working properly.
however, I had to manually shutdown system-resolved. just

systemctl restart NetworkManager

didn't do it. Its possible that a restart would make it work properly


Which prometheus "internal" metrics are required for conformance?

Currently, conformance tests require the 'up' metric be present.  However, there are other internal metrics, such as scrape_duration_seconds, scrape_samples_post_metric_relabeling, scrape_samples_scraped, and scrape_series_added that a prometheus server would also produce that are designed to make debugging prometheus endpoints easier.
I asked this question at the wg today, and we weren't sure which would be required by conformance.  There is a separate question of which are useful, but we should probably start with ones that are required.
@RichiH agreed to raise this with question with prometheus folks.

PR #3116 addresses all these metrics.

Is this an issue to be better filed at https://github.com/prometheus/compliance/ for visibility?

We decided to add all of the metrics instead of just limiting to "up", so we should be all set either way.


Modify the output content in readme.

Run the YAML.stringify() in readme and get the different result.

Thank you, good catch!


Constantly loading in the viewer

Hi Markus,
I discovered a bug.
One of the files in the ZIP is constantly loading in the viewer, while the octree.bin is less than 100MB after a few minutes it exceeds the GB in the viewer.
https://gofile.io/d/dPgwYN
Is this a viewer or converter bug?

Hi Markus,
Have you try it ?

Hi Markus and Polak,
I have the same problem. I have a las file without a color only with intensity. I use pdal (filters.python) to scale the intensity to color. With the PotreeConverter 1.7 this work fine but with the PotreeConverter 2.0 the loader in the viewer is constantly loading it,.
If i just convert the las file without touching it with pdal, it works fine. Is it possible that pdal is adding some attributes to the las file that Potree 2.0 does not support
?

Thanks for the report. For some reason, some nodes have numPoints > 0 but byteOffset and byteSize = 0. I'll take a closer look at that bug tomorrow.

Possible to fix the bug ?

Yeah, but still looking at it. Using the latest version of the converter and potree (compression branches), Potree doesn't load the octree constantly, but the "bad" file still results in some strange precision issues.

Hi Markus,
Fixed !
We are going to do some more testing!
Thank you for your responsiveness.

Great!

Hi Markus !
We discovered with this new converter, a random problem, depending on the clouds or the PC viewer.
However :
Chrome latest version
graphics card driver also.
The nodes are well downloaded, we can see the network activity, but no point cloud appears.
I don't know how to reproduce the problem for you.

https://gofile.io/d/zQxj0N
An example, perhaps in file you can find solution, check on differente pc to reproduce error

@Polak74 This is going to be partly questions and partly troubleshooting - my apologies if it's not that helpful.
Could you clarify if you mean you don't see a rendering of the point clouds or if entries are also missing in Potree's scene menu? Can you confirm that this behavior does not occur with an earlier version pairing of the converter & viewer (e.g. 2.0.1 & 1.7.1 respectively)? When you say it depends on the point cloud or viewer PC, does that mean that

your clouds always work on one machine but not others,
your conversions either work or don't work and the effect is the same across every machine, or
sometimes a converted cloud will work or not work, at random, regardless of the machine?

If you can still see the point cloud name in the scene menu, ensure that it is checked (enabled), double click on it to see if the viewer zooms to a new location, and change the active attribute so you can see if the point cloud shows up when coloring the points differently, like with elevation or intensity gradients instead of RGBA. Check if you have high quality splats or Eye Dome Lighting enabled in the appearance menu; if so, disable EDL and switch to standard quality. Many mobile systems like phones, tablets, and Chromebooks will not render the points at all when these features are used because of an oversight in their WebGL extension compatibility. By the way, since we recently learned that Chrome doesn't like to render EDL/HQ when hardware acceleration is disabled, please make sure you have this turned on and running a modern-ish GPU - or just use Firefox since it doesn't suffer from this problem. Lastly, it would be really weird for this to be the case, but make sure the point cloud material opacity isn't set to something really low like 0 or 0.1.

Hi,
The right answer is sometimes a converted cloud will work or not work, at random, regardless of the machine.
The point cloud is right in scene menu and if i double click zoom in is correct but nothing in render, but network work good.
In same scene 1.7.2, i can have 2 point cloud, one with 2.0.0 and 2.0.2, but the file convert with 2.0.2 sometime not render....
but it can work on other machines.

Could you please upload a small sample to something like Google Drive or Dropbox and share the link here? I'd need a known problematic file, and when I went to the previous link, the website said there was no download.
Perhaps looking for console errors or debugging the JavaScript is necessary here.
By the way, does this also happen in Firefox?

https://gofile.io/d/zQxj0N

Same on FireFox

@FrenchTrott I can confirm that I'm seeing what you described. The point cloud isn't being rendered as expected. The ranges are indeed being called and downloaded when the view changes or when the point budget changes. Changing the attributes and disabling EDL has no effect.
I've stepped through the JavaScript, and it doesn't look like the 0 byte issue is at play here. I couldn't find a direct cause here when I was poking it yesterday. I'm going to give it another go tonight. The metadata has a few different values between the good and bad point clouds, but I'm not sure that's to blame. Do you remember what CLI arguments you passed to the converter to get these different conversions?

@minuit-dev thanks to reply
of memory none, no particular parameter.
Is Markus reading this issue since it is closed !?

Is Markus reading this issue since it is closed !?

I'm glancing at all new posts (getting mails), just don't always have time to respond right away. I'll try to find time to look at this issue today.

The right answer is sometimes a converted cloud will work or not work, at random, regardless of the machine.

At random sounds bad. Any way to reliably reproduce the error?

random sounds
I have been looking for 5 days but not found.
Maybe the problem comes from viewer 1.7.2

on the other hand, always on the same computers!
Thanks Markus !

@Polak74 https://gofile.io/d/zQxj0
@FrenchTrott https://gofile.io/d/zQxj0N

First doesn't work, second does. Is second link just the fixed version of the first one or are they supposed to be two different ones?
In any case, the point cloud by @FrenchTrott works fine for me in PotreeDesktop, including the release at: https://github.com/potree/PotreeDesktop/releases/tag/1.7.2. No errors and everything seems to render as it should.

on the other hand, always on the same computers!

So on one PC it always works, and on another it never works? Are there any errors in the dev console (F12 or Ctrl+shift+i)?

That's a bit tough to debug, then. Can you provide some more infos like:

What's the last version that works? Does PotreeConverter 1.7 + Potree 1.7 work? PotreeConverter 1.6 with Potree 1.6?
OS?
What GPU?
Do the demos at https://github.com/potree/potree/#examples work?

I hate to be the bearer of bad news, but I can absolutely confirm what @FrenchTrott is experiencing. Originally, I thought the bugged point cloud might not work at all because I was only viewing it on my laptop, but I'm at work right now scratching my head because the point cloud is rendered on my workstation. Mostly.
At first, it only renders as black points.

Clicking on the point cloud name under the Scene menu immediately selects intensity and its material can now be seen.

Changing the display attribute to RGBA gives it the (presumably) correct color.

Meanwhile, on my laptop, clicking on the point cloud name & changing the display attribute does nothing. Double clicking makes the movement speed change, so it thinks its zooming to something, but nothing is rendered. It's like the frustum is getting messed up and everything is being culled.

Activating measurements, e.g. point or volume boxes, seems to do nothing at first (no change to the render), but upon zooming out, this they appear out of nowhere.

This has further piqued my interest. I'll continue investigating this, but for now I can't say why it renders on one machine and not the other. My laptop uses an Intel iGPU with a hybrid NVidia MX150 GPU, while the workstation has 3 monitors and 2 dedicated GPUs, and each monitor is 4K. When I shrunk the window size to less than 1080p, nothing changed. It still loads on my desktop, but not on my laptop. Anyway, this was just to give you guys an update. We still need to figure out how to reproduce this across machines and then find what is causing this mess.

@midnight-dev
If it's useful I'd be happy to serve that cloud publicly so it's easier for multiple people to try on different hardware.

@smcavoy12 Much appreciated, Scott. I may have found something though. Not sure how much longer this will be relevant, but it's still curious why different machines handle this more gracefully than others. By the way, I forgot to mention in my earlier comment that even when the point clouds and measurements to appear, the bounding boxes are still properly rendered when that debug option is enabled. This may be irrelevant, but it's worth noting.
So on a whim, I compared the metadata JSON files and noticed the bugged version has a gps-time attribute while the working point cloud does not. Removing this allows my laptop to render black points like my desktop. I can't seem to get at the proper RGBA color that my workstation renders. It's still very dark if not black. The shaders for other materials like elevation and intensity work as expected, just not RGBA.
For documentation sake, this is the JSON of the gps-time attribute that's bugging out Potree 1.7.2, 1.7.1, and 1.7.0 on my laptop:
{
	"name": "gps-time",
	"description": "",
	"size": 8,
	"numElements": 1,
	"elementSize": 8,
	"type": "double",
	"min": [0],
	"max": [0]
}

Update:
You know how in programming, a single character can cause a lot of headache and frustration?
"max": [1]

ಠ_ಠ
Apparently, the renderer will flip out if the gps-time has a min and max that are equal. But only on some computers, I guess. It's better to not have the gps-time attribute at all if the min and max aren't different. It might be a race condition where some machines, like my office workstation, are faster than others at loading the data. It skips over whatever is causing trouble on my laptop.
@Polak74 & @FrenchTrott Can you guys confirm whether or not the point cloud renders on faster machines? And also, to fix the render issue, open the metadata.json file and change the "max" property of the gps-time to be [1] instead of [0]. Hope this helps.
@m-schuetz If PDAL is adding this 0, 0 gps-time to point clouds, maybe core Potree should just skip adding the gps-time to the known attributes or fail gracefully when a 0, 0 min/max are discovered.

Hi all,
Hi @midnight-dev, and thanks.
I confirm that GPS is the cause.
My problematic file had this.
		"name": "gps-time",
		"description": "",
		"size": 8,
		"numElements": 1,
		"elementSize": 8,
		"type": "double",
		"min": [0],
		"max": [0]

And if i modify this to
		"name": "gps-time",
		"description": "",
		"size": 8,
		"numElements": 1,
		"elementSize": 8,
		"type": "double",
		"min": [0],
		"max": [1]

File is render ...
but i find it hard to understand why some computers can render and others can't.
curious to understand.

@FrenchTrott I don't know why either. I can only speculate that some computers finish extracting the gps-time a little sooner than others, and based on when the shaders get compiled, sometimes the points are rendered and other times they are not.
That's why I was asking you if you notice slower computers having this problem. Two workstations at my office rendered the bugged point cloud as expected, but my laptop (much slower) would always fail. This is just a hunch. It deserves more attention at a later date, but for now we have a fix that should work. If you're able, checkout potree/potree#909 to see if this works for you too. Let me know if there are still problems.


Update construction_api.go

Update struct field tags for TxMetadata

Thanks @qiwu7 !
These changes have been superseded by this PR https://github.com/Zondax/rosetta-filecoin-lib/pull/19 where we upgrade to the latest testnet.


Investigate gnomAD version in population tab provided by external API

For some reason the gnomAD version is showing up not as "v.2.1.1" (the actual version) but as "20210610". This is true on both the test and production site and was observed for multiple variants
Example variant: CA41020385

4

We get this from my.variant.info... which is showing this as the version. Christine to contact them about the version.

Contacted myvariant.info help email on 04/21/22.


⚠ ClamAV has degraded performance

In 5b116cb, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 454 ms

Resolved: ClamAV performance has improved in 733c8aa.


Update version: trzsz.tssh version 0.1.15

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

@wingetbot waivers Add Validation-Executable-Error


controllers: support custom queries

In order to resolve https://github.com/confio/poe-contracts/issues/36, it looks like we need the tgrade-valset contract to use TgradeQuery as the custom query type for Deps and DepsMut (currently it's Empty).
In order to do that, Admin needs to support custom query types that are not Empty in Deps/DepsMut.

Ah, yes, now that I made Deps/DepsMut generic over the custom query type, we need to make controllers generic over that as well, not just Response.
I agree. Can you also update other controllers? (Possibly as a follow up)

Note that main is breaking, so after merge, you should make a new branch off of v0.11.1, back port this fix (and for the other controllers) and release a v0.11.2.
I don't think v0.12.0 is coming out so fast, so let's just patch the last stable version

I agree. Can you also update other controllers? (Possibly as a follow up)

Happy to do that, should be easy enough.

OK with me. Only thing is that v0.12 will include type safe bounds, and it will require code migration.
Migration should be easy, though. And, there's already a MIGRATING entry for this.

As @ethanfrey says, you can either cherry pick this into a 0.11 branch (branched off from the latest 0.11 version tag) and release a new 0.11, or release 0.12 early. I for one would do the 2nd, even when it'll require some code migration on the client repo.

Speaking of.. let me tag the v0.12.0-alpha2 release I prepared.
And then I will make one more PR I would like in a final v0.12.0. I will try to finish tonight, be able to review/merge tomorrow

Great. I can help with releasing 0.12 final if needed.

I realized we might also need to update multitest with custom queries and I'm taking a shot at that, but it's not trivial.

This is the relevant PR: https://github.com/CosmWasm/cw-plus/pull/653
I would like that in before a v0.12.0 is tagged

Okay, I tried to cover all of the /packages, multi-test included. Hopefully I didn't miss anything. Can you please take another look?

As @ethanfrey says, you can either cherry pick this into a 0.11 branch (branched off from the latest 0.11 version tag) and release a new 0.11, or release 0.12 early. I for one would go for the 2nd, even when it'll require some code migration on the client repo(s).

I'd rather cut the new release than backport things. I guess for the migration there's nothing to do on my side if there's already a MIGRATING.md entry? Just that this is breaking for users?


[WIP] Testing userfaultfd

CI gfxreconstruct build queued with queue ID 149115.

CI gfxreconstruct build # 3855 passed.

CI gfxreconstruct build queued with queue ID 151695.

CI gfxreconstruct build # 3872 running.

CI gfxreconstruct build # 3872 passed.

CI gfxreconstruct-extended build queued with queue ID 151718.

CI gfxreconstruct-extended build # 332 running.

CI gfxreconstruct-extended build # 332 passed.


table borders

ffpdfjs_bug_tablelines.pdf
Configuration:

Web browser and its version: Firefox Quantum 65.0 (64 bits)
Operating system and its version: macOS Mojave 10.14.3
PDF.js version:
Is a browser extension:

Steps to reproduce the problem:

open attached pdf in firefox (drag and drop in new tab)
the rendering of the borders in the table changes with the level of zoom

What is the expected behavior? (add screenshot)
expected behavior (from preview/or google chrome)

What went wrong? (add screenshot)

This pdf was modified for anonymisation reasons.
But you can find this in the metadata of the original file :
File Permissions                : rw-r--r--
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.6
Linearized                      : No
Encryption                      : Standard V4.4 (128-bit)
User Access                     : (none)
Creator                         : Excel
Producer                        : Mac OS X 10.12.6 Quartz PDFContext
XMP Toolkit                     : Adobe XMP Core 5.4-c006 80.159825, 2016/09/16-03:31:08
Format                          : application/pdf
Creator Tool                    : Excel```

I can reproduce this issue both with my browser.
Name 	    Firefox
Version 	62.0.3
Build ID<PHONE_NUMBER>1701
User Agent 	Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0
OS 	        Linux 4.14.98

var pdfjsVersion = '2.0.625';
var pdfjsBuild = 'e8b50883';

and with master at https://github.com/mozilla/pdf.js/commit/ece6a31a442d8d2489817579dfc57ed371135d3a (on the same browser obviously).

This looks like another case where PR #6606 might help.

@Snuffleupagus well, it may be linked, but this issue looks different than #6606 because lines get wider as you zoom out on the page. Ratios are not preserved when zooming in and out.


How to set up the application

How to set up the application

Done!
https://github.com/lgallard/qBittorrent-Client/wiki


Lift captured project.toString to conf. time.

This change is required to fix gradle doc sample project configuration
cache compatibility.
Fixes: #21802
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[x] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] Provide unit tests (under <subproject>/src/test) to verify logic
[x] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass sanity check: ./gradlew sanityCheck
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@Jeffset, please add your full name and github handle to the list of contributors in the release notes as described here.

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

Judging by the logs of two failed builds, seems like restarting them would help. Probably a flaky timeout issue?

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

OK, I've already triggered a build for you.


change css label on md-input

Hi,
Hello,
I would, in case of error on my form, change the label of my input as well as the text color and border-color below, much like with dividerColor, but without focus, I'd like that persistent.
So I made this code there for the label:
md-input:not(.ng-invalid) label {         background-color: red !important;         color:red !important;     }
However, when I run the project, my css is modified in this way:
md-input[_ngcontent-fcu-13]:not(.ng-invalid)   label[_ngcontent-fcu-13] {         background-color: red !important;         color:red !important;     }
And therefore, it does not work.
Do you have an idea ?
(Translated by google translation)

Your css is being encapsulated by Angular. See https://angular.io/docs/ts/latest/guide/component-styles.html
Also see #348


Also save component if directly opened (eg. without a project)

Save Component on Save, but Save as popup is displayed nonetheless.

@Liioooo Can we easily check if the main project has been touched?

@yEinFallsLos Yes we can. The project has an property saveDirty. The only downside of this would be that you wouldn't be able to save empty projects form the editor anymore. But this is compromise we can make in my opinion.

Yeah I don't think that's much of a concern.


[Event Modification] Codeunit 5520 Get Unplanned Demand - OnBeforeOpenPlanningWindow

Hi, would it be possible to modify the event OnBeforeOpenPlanningWindowin codeunit Codeunit 5520 Get Unplanned Demand  to insert a ProdOrderComp parameter, like this :

    trigger OnRun()
    begin
        if IncludeMetDemandForSpecificSalesOrderNo <> '' then
            SetFilterToSpecificSalesOrder();

        DeleteAll();
        SalesLine.SetFilter("Document Type", '%1|%2', SalesLine."Document Type"::Order, SalesLine."Document Type"::"Return Order");
        ProdOrderComp.SetFilter(
            Status, '%1|%2|%3', ProdOrderComp.Status::Planned, ProdOrderComp.Status::"Firm Planned", ProdOrderComp.Status::Released);
        ServLine.SetRange("Document Type", ServLine."Document Type"::Order);
        AsmLine.SetRange("Document Type", AsmLine."Document Type"::Order);
        JobPlanningLine.SetRange(Status, JobPlanningLine.Status::Order);

        RecordCounter := SalesLine.Count + ProdOrderComp.Count + ServLine.Count + JobPlanningLine.Count;
        OnBeforeOpenPlanningWindow(ProdOrderComp, RecordCounter);
        OpenWindow(ProgressMsg, RecordCounter);

    [IntegrationEvent(false, false)]
    local procedure OnBeforeOpenPlanningWindow(var ProdOrderComp: Record "Prod. Order Component"; var RecordCounter: Integer)
    begin
    end;

Thanks

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Release 0.55

Problem
Features for 0.55 are not yet deployed
Solution
Manual release process:

[x] Create a release/0.55 branch off of main. Ensure github test actions run. Merge Against release/0.55 branch
[x]  Bump Snapshot to 0.56.0-SNAPSHOT branch off of main. Merge against Main
[x] Tag as v0.55.0-rc2

[x] git tag
[x]  Confirm new docker image version is deployed
[x] Deploy Version
[x] Finished Testing (Manual, Newman, Dapp, Acceptance)

[x] Review and update dependencies

[x] @hashgraph/hedera-local
[x] @hashgraph/sdk

[x] Previewnet Testing

[x] Deploy tagged version
[x] Manual testing
[x] Run newman tests
[x] Run Dapp Example Bootstrap and manual tests
[x] Run acceptance tests
[x] Run performance tests

[x] Testnet Testing

[x] Deploy tagged version
[x] Manual testing
[x] Run newman tests
[x] Run Dapp Example Bootstrap and manual tests
[x] Run acceptance tests
[x] Run performance tests

[x] Let Bake

[x] git tag
[x] Confirm new docker image version is deployed
[x] Write up release notes and changelist

[x] Mainnet Testing

[x] Deploy tagged version
[x] Manual testing

Alternatives
No response

Complete


Update README.md

Drop reference to AGPL v3.0 and replace with PostgreSQL license
Ticket(s) Closed

Closes #

What
Why
How
Tests

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

Thank you! We just need you to sign the CLA and this will be good to go


[rapidjson] Fix cmake config

Describe the pull request

What does your PR fix?
Importing rapidjson from cmake didn't work
Don't remove pc files
Fix string replaces in cmake config file
Remove docs

Thanks! Will merge as soon as build is green.


Merge request: #78 'Signing' class cannot create old CURL addresses

The current commit is related to the ticket #78 - 'Signing' class cannot create old CURL addresses. The class Signing.class is modified to allow the use of any kind of ICarl instance and prevent a live lock problem.

@schierlm  I've upgraded the code, you can review it know.

Looks good, thanks.

Closing the PR as its stale for a long time, if we need it i will reopen it :+1:

@kwek20 can you tell if there were any objections not to merge this during the last 1.5 years? Ignoring a pull request for that long time and then closing it as stale is something new for me.
#78 is still open and I'm using a locally patched (old) version of iota.lib.java for that use case.

@schierlm Aha! I figured everyone would be using the new addresses by now.
Ill get to it then!

@kwek20 Yes, regular users are all using KERL addresses. But just come to Discord and look into the #reclaim channel, and you will notice how often some HODLer finds their old IOTA inaccessible and being unable to recreate their old addresses from their seed due to the change to Kerl algorithm. :)

@schierlm This has been solved with https://github.com/iotaledger/iota-java/pull/187

@Kwek20 So you can close #78 too :)


Parsing

Right now we're hardwiring in JSON. We'll want to change that and add proper content negotiation.

Support for multipart data

Werkzeug has great support for handling this, so we'll rely on that.

That would be great. Seems to get the job done quite well!

De-scoping this to just parsing for now.

Doesn't validate if field is None?


[#3761] Support okhttp 3.3.1

#3761

Codecov Report

Merging #3821 into master will decrease coverage by 0.09%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #3821     +/-   ##
=========================================
- Coverage   40.86%   40.76%   -0.1%
=========================================
  Files        2174     2177      +3
  Lines       70772    70930    +158
  Branches     9743     9780     +37
=========================================
- Hits        28919    28917      -2
- Misses      39094    39252    +158
- Partials     2759     2761      +2

Impacted Files
Coverage Δ

...ercorp/pinpoint/plugin/okhttp/OkHttpConstants.java
0% <ø> (ø)
:arrow_up:

...ceptor/HttpEngineSendRequestMethodInterceptor.java
0% <ø> (ø)
:arrow_up:

...eptor/HttpEngineReadResponseMethodInterceptor.java
0% <ø> (ø)
:arrow_up:

...ceptor/HttpEngineSendRequestMethodInterceptor.java
0% <0%> (ø)

...ercorp/pinpoint/plugin/okhttp/v2/OkHttpPlugin.java
0% <0%> (ø)
:arrow_up:

...nterceptor/HttpEngineConnectMethodInterceptor.java
0% <0%> (ø)

...ercorp/pinpoint/plugin/okhttp/v3/OkHttpPlugin.java
0% <0%> (ø)
:arrow_up:

...eptor/HttpEngineReadResponseMethodInterceptor.java
0% <0%> (ø)

...ofiler/sender/StandbySpanStreamDataSendWorker.java
80.59% <0%> (-2.99%)
:arrow_down:

...corp/pinpoint/rpc/stream/StreamChannelManager.java
70.68% <0%> (-1.73%)
:arrow_down:

... and 5 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 dcfb665...f3afd9e. Read the comment docs.


404 at /en/latest/use/port_redirection

URL: https://docs.docker.com/en/latest/use/port_redirection

I have no idea what you were trying to reach. Can you let me know the URL where you followed this link from? The string port_redirection does not exist anywhere in our source.


fix: properly filter by os version

Currently in stage-beta, if you add os filters, the system fetch will break because it's not properly adding the versions to the request string. This PR properly creates the fetch request.
It will only work in stage-beta at this point. It is currently not fetching correctly because the backend needs a change. if you filter by centos version 7.9 and rhel version 8.8, it will try to fetch centos versions 7.9 and 8.8 and rhel versions 7.9 and 8.8.

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Files
Coverage Δ

src/SmartComponents/SystemTable/helpers.js
20.40% <0.00%> (ø)

:loudspeaker: Thoughts on this report? Let us know!.


Send warnings

This appears to initially work, but is not compressively tested. Because warnings are not written to TTC it only will work on first load, but that it an issue with idris2 not idris2-lsp.
Edit: This only works if there are errors in the file, because Idris 2 reloads from TTC if there are no warnings.

I'll merge this now, even if warnings emission is broken in the compiler. This way at least we would get warnings on the first load.

I don't think it even works on first load because a reload from TTC occurs. I think think it only works if there is an error in the file. I'm still trying to think of the best way to solve this issue. I have been struggling to think of the best way to expose warnings to the LSP. The 4 ideas I currently have are below:

List Warning with warnings from the main file and not from the dependencies
List Warning with warnings from the main file and from the dependencies
SortedMap String (List Warning) with a map from file to the list of warnings
Have LSP pass a report diagnostic function to the API (filename : String) -> List Warning -> List Error -> Core () to the API. The API will call this function on every TTC load or error.

Another complication I can think of is warnings outside of the current project.
What do you think is best?

I think the best approach is to have the compiler call handler functions on errors, warnings and logs, like approach 4. The regular compiler behaviour of printing to stdout should be the default handler, but could be overwritten by toolings to get more fancy interfaces or for LSP to provide a different encoding. However, I'm still not completely set on the signature, probably some discussion is needed before, and the Idris meeting could be perfect for such discussions and refactorings.
In this particular case, probably both errors and warnings should be stored in TTC files. Compilation should be deterministic, so if nothing changes also errors must not change.


Display Metadata/Feature list in the frontend

Hi,
How do you display the metadata for each product in the front end? I want to display a list of features for each subscription product. And lastly, can Stripes 'Feature list' be used with this template?
Thanks

Hey there! You should be able to grab this information from Stripe (the template here doesn't have this added, but it should be possible with user code). Hope this helps!

Hi,
How do you display the metadata for each product in the front end? I want to display a list of features for each subscription product. And lastly, can Stripes 'Feature list' be used with this template?
Thanks

I'm actually trying to do the same. Were you able to figure out how to do it?

No, sorry I was not able to figure it out.

Hi there, if someone stumbles upon this issue looking to add Stripe product features to this starter, here are the steps I took:

Create features column for products table, you can do it either in Supabase ui or Postgres schema file;
Update product fixtures with: "features": [ { "name": "Unlimited customers" }, ...your features ];
Update supabase admin utility to add product features to supabase product table features column
Seed your fixtures into stripe and voila - you get a fancy features list


How to run React JS build in React-Native Webview?

I created complete offline ReactJS web application and I want to run it from android application from Web View using React-Native.
I followed the following procedure to do so:

I created a compiled ReactJS web application got the build using the following command:

npm run build

Then I created react-native project and placed the build folder with following architecture

I updated App.js with the following content:

import React, {Component} from 'react';
import {Platform, StyleSheet, Text, View, WebView} from 'react-native';
import {roscon} from "./build/index.html";

type Props = {};
export default class App extends Component<Props> {
  render() {
    return (
      <View style={{height: 300, width: 300,overflow:'hidden' }}>
          <WebView
            source={{uri: roscon}}
            scalesPageToFit={true}
            domStorageEnabled={true}
            javaScriptEnabled={true}
            startInLoadingState={true}
          />
      </View>
    );
  }
}

After running this code I expected it to run my ReactJS Web application, instead I got white screen.
Can you please tell what can be the causing issues and how i can make my ReactJS Web App run on react-native?
Note: I was able to run generated build folder using npm command:
serve -s build

But I still can't figure out how to port it to react-native project as WebView

Have you found a solution?

Hi. @damian165-cpu, you can open a web server in React Native by https://github.com/bachlongkocanh/saaf-rn-web-server.


Split vscode NPM node module into @types/vscode and vscode-test

Per the recent incidents (https://github.com/Microsoft/vscode/issues/69656), I think it's a good opportunity for us to split vscode node modules into 2 pieces:

@types/vscode
vscode-test

Explanation
vscode node module contains 3 scripts:

compile: no longer used
install: used to fetch vscode.d.ts according to engine.vscode in package.json
test: used for extension test (also lib/testRunner)

Problems

install asks update server for finding matching vscode.d.ts version (actual dts files fetched from GitHub). When update service is down, all extension deps install (CI or local development) could fail.
yarn install and npm install can't be completed offline, even if they have caching: https://github.com/Microsoft/vscode-extension-vscode/issues/93
test depends on a lot of node modules (13MB). Everyone has to download them even if they just want to use the API.
test needs some improvements. For example, for running extension tests against multiple workspaces, I had to pull out the test scripts and modify them manually Vetur. Also https://github.com/Microsoft/vscode-extension-vscode/issues/124, people want functionalities exposed from test so they can build upon them.

Benefits of splitting vscode into @types/vscode and vscode-test

No awkward postinstall scripts after each npm install for extension
Users don't have to pull in the 11MB dependencies of test. They pull a few kb of vscode.d.ts from @types/vscode, and it's fully cached by npm/yarn.
vscode.d.ts are hosted on NPM which is pretty reliable. d.ts live in a @types package as they should be.
test now lives in its own repo. It's easier to make improvements, release new versions, expose functionalities (for example, import { downloadVSCodeExecutable } from vscode-test).

Challenges
We can't put all versions of vscode.d.ts into @types/vscode and let TS infer which one, from engines.vscode.
However I think we can publish vscode.d.ts the same version as we do for VS Code, since all our 1.x API are backwards compatible. Most users also auto-update to latest version, so extension authors could use "@types/vscode": "^1.31.0" and safely get minor updates.
/cc @Microsoft/vscode for thoughts.

:+1: I like the proposal, I would suggest the small twist of shipping the .d.ts file directly within the vscode npm module instead of using @types/vscode. But that means we have to remember to always publish a new vscode npm module when we create a stable release. That should be fine, given we do it strictly after a VS Code release.
I would also vote for rewriting the script which downloads a vscode release to use https directly and the native installed tar instead of 13MB of gulp-* dependencies.

rewriting the script which downloads a vscode release to use https directly

Agreed, something like this already works for macOS/Linux, which is what I'm using on Travis. vscode-test should also contain minimal or zero dependencies, so we'd be exempted from issues like event-stream.
let downloadPlatform

switch (process.platform) {
  case 'darwin':
    downloadPlatform = 'darwin'
    break
  case 'win32':
    downloadPlatform = 'win32-archive'
    break
  default:
    downloadPlatform = 'linux-x64'
}

const url = `https://update.code.visualstudio.com/latest/${downloadPlatform}/stable`

const https = require('https')
const fs = require('fs')
const cp = require('child_process')

https.get(url, res => {
  const zipUrl = res.headers.location

  if (zipUrl.endsWith('.zip')) {
    const outStream = fs.createWriteStream('vscode.zip')
    https.get(zipUrl, res => {
      res.pipe(outStream)
    })
    outStream.on('close', () => {
      if (process.platform === 'win32') {
        // need some windows powershell script or a zip library that supports windows
      } else {
        cp.execSync('unzip vscode.zip')
      }
    })
  } else {
    const outStream = fs.createWriteStream('vscode.tgz')
    https.get(zipUrl, res => {
      res.pipe(outStream)
    })
    outStream.on('close', () => {
      cp.execSync('tar -xzf vscode.tgz')
    })
  }
})


Create pandoc transtype for XXX=>dita

Related: https://github.com/jason-fox/fox.jason.passthrough/issues/1

Using the dita output format does not produce files with .dita or .xml extension. Instead it is the source files extension even though the contents of the converted file are in fact DITA. I'm forced to rename the extension.

This is a limitation of the dita plugin - the xslt there is converting the treated files with the same file names as the input. There is no extension point I could use, so I'd have to create a new transtype for pandoc-dita post-processing.

Fixed https://github.com/jason-fox/fox.jason.passthrough/commit/af977a35d
An additional transtype is not necessary.


floating point exception (core dumped) when process images with different size

If I resize all the images to the same size before transforming, there will be no error.
By the way, all the images with height = 70 and width in (200, 400) , no very small size.

Can you give me more details? Do you use my tool in PyTorch?

I double checked my scripts and found that there is one file which is not an image.
I remove that file then the code worked without error.
Sorry to bother you and thank you very much!

That's all right. Hopefully the tool can help you.


Update org mgt version to the latest 1.3.67

Changes in this PR

$subject to get the changes from https://github.com/wso2-extensions/identity-organization-management/pull/242

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6244217246

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6244217246
Status: success


GOSA21 - Add splash screen

Add native splash screen to App using the package (flutter_native_splash).

assign me

assign me

@singhtaran1005 you can work on this

@singhtaran1005 thank you for the contribution. you have recieved 5 points for the contribution. We have merged your pr successfully.


updates?

about to install and test. curious if you're considering any updates to accommodate more bpmn options?  planning to test with spiffworkflow = lmk if you have ideas :)

This was a project for my final thesis, and is unfortunately not under active development anymore. Lately I've been experimenting with fully LLM-based approaches to generating BPMN diagrams, which would even allow for iterative editing of the diagram based on the user's prompts. Stay tuned 😄

very interested in this work = hit me up sometime =<EMAIL_ADDRESS>there are a lot of people interested in using this in the legal field to make laws easier to understand


Update license year, remove dist dir, remove bower.json

Why did you remove bower.json? Isn't that used for bower?

Oops... Reverted and rebased...


Error: You must supply options.input to rollup

Just followed the readme, got
$ npx @pika/web
npx: installed 75 in 9.201s
- @pika/web installing...
Error: You must supply options.input to rollup
    at Promise.all.then (C:\Users\dfcre\AppData\Roaming\npm-cache\_npx\6000\node_modules\@pika\web\node_modules\rollup\dist\rollup.js:16590:23)
    at processTicksAndRejections (internal/process/next_tick.js:81:5)
    at process.runNextTicks [as _tickCallback] (internal/process/next_tick.js:51:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:865:11)
    at findNodeScript.then.existing (C:\Program Files\nodejs\node_modules\npm\node_modules\libnpx\index.js:268:14)

In a way I imagined pika to be a package installer, alternative to npm, that puts any npm package compiled to ES module into /web_modules folder.
Just curious - what's the reasoning for making pika a local package installer npx @pika/web instead of global cli tool pika?

Facing the same issue.
npx @pika/web
npx: installed 75 in 4.076s
⠋ @pika/web installing... Error: You must supply options.input to rollup
    at /Users/singh.kunal/.npm/_npx/15059/lib/node_modules/@pika/web/node_modules/rollup/dist/rollup.js:16610:23
    at async install (/Users/singh.kunal/.npm/_npx/15059/lib/node_modules/@pika/web/dist-node/index.js:253:25)
    at async cli (/Users/singh.kunal/.npm/_npx/15059/lib/node_modules/@pika/web/dist-node/index.js:285:18)
⠏ @pika/web installing... @types/node, @types/express-serve-static-core, append-query, body-parser, bunyan,

Can either of you share a list of "dependencies" that you're trying to install? My guess is that none of your dependencies expose a "module" entrypoint, so the tool tries to install nothing and then gets confused and fails.

@FredKSchott that's true, indeed. I was trying to install https://github.com/substack/tape/blob/master/package.json

Fixed in https://github.com/pikapkg/web/commit/5c5b8253d26f93cd2b2cd3218c39dc66874214f0

Just curious - I had an impression that pika compiles cjs to esm on install - what’s the difference with installing esm via npm?


Can not get webp images work

Hi
I followed step by step this: https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_WebPimages_support.md but i can´t get them to work.

Hi! I would check the app service logs and see if startup.sh is failing to execute.

Yes, I think it does. And for almost all our App services.

same problem

The document seems to be slightly outdated because of which it is not working. I will test the new steps and update it soon.

@gokaycagri, @emmigereb
WebPI support has been enabled by default within the image. You can restart your App Service to pull the latest changes.
Note: Please ignore the previous documentation (as it is no longer required), and also remove any custom startup script for the same (if you have added any).

Closing this issue. Thanks!!


Make podManagementPolicy configurable for Stardog statefulset

When starting Stardog Cluster on existing volumes it's possible to encounter the following error:
Cannot start kernel since there are no other nodes in the cluster to sync up

This happens because the latest tx id is stored in ZK and the Stardog cluster node with a matching tx id needs to start first. With k8s this can be problematic because the default nature of statefulsets starts them in an ordered fashion so if the first node doesn't match the tx id then the deployment hangs and no other pods are deployed.
The setting podMangementPolicy: Parallel can be set on the Stardog statefulset to start all of the Stardog pods at the same time, which allows the pod with the matching tx id to start and the other nodes to sync.
We should make this a configurable option.

Fixed: https://github.com/stardog-union/helm-charts/pull/40

Fixed: https://github.com/stardog-union/helm-charts/pull/40


REally Slow

This is taking hours.  Is that normal or what are the dependencies?
I'm on a high end MacBook Pro.

It has to access api keys from openai and anthropic. Maybe your network is slow. Mine coded a full app in an hour and my wifi stays at a constant 2.5gb download.

This is the first time I have done this.
I followed the directions and I only have the open AI one.
How do I get the other 2?  And how do I add them?

Under the API Folder is shows:
import Anthropic from "@anthropic-ai/sdk";
import dotenv from "dotenv";
dotenv.config();
const anthropic = new Anthropic();
============
import fs from "fs";
import OpenAI from "openai";
import dotenv from "dotenv";
dotenv.config();
let openai;
So how do I add them?

@chadwickallison probably you have to edit the file called .env inside the folder cofounder/api/.env

OPENAI_API_KEY = "REPLACE_WITH_OPENAI_KEY"
ANTHROPIC_API_KEY = "REPLACE_WITH_ANTHROPIC_KEY"
COFOUNDER_API_KEY = "REPLACE_WITH_COFOUNDER.OPENINTERFACE.AI_KEY"

And you can ask to google or chatgpt how to obtain these keys from the different providers.


2 | program capacit       | 1 Error: Non-numeric character in statement label at (1)

i'm getting this for all the lines of my code
(base) macs-MacBook-Pro:nodefortran mac$ node index.js
/var/folders/6g/mrdn4qhd7q5344ld8xcxzy5h0000gn/T/tmp-979jbS4OjXw5X7z.f:2:1:
2 | program capacit
  | 1

Error: Non-numeric character in statement label at (1)
/var/folders/6g/mrdn4qhd7q5344ld8xcxzy5h0000gn/T/tmp-979jbS4OjXw5X7z.f:3:1:
3 | implicit double precision(a-h,o-z,l,m)
  | 1

Error: Non-numeric character in statement label at (1)
/var/folders/6g/mrdn4qhd7q5344ld8xcxzy5h0000gn/T/tmp-979jbS4OjXw5X7z.f:4:1:
4 | pi=2*asin(1.)
  | 1

Error: Non-numeric character in statement label at (1)
/var/folders/6g/mrdn4qhd7q5344ld8xcxzy5h0000gn/T/tmp-979jbS4OjXw5X7z.f:5:2:

I speculate there is an issue with the fortran code itself, rather than with the bridge.


Alias: Season 6

Add some aliases to make the options a bit quicker to get to.
Here is a screenshot of what the new help print out looks like:

Note: I wasn't quite sure what to do when it came to oneline and oneline-browser, so I just sort of improvised haha. Definitely open to ideas around that.

No problemo. I actually just realized the Does it have lots of command line options? section of the readme is out of date now. I can update that if you'd like.
Lemme know!

Appreciate it, but I added some other options too so I updated it myself.


CanvasGraphics.drawRoundRect use wrong context for mask

CanvasGraphics.drawRoundRect use the static var context, when CanvasGraphics.renderMask use renderSession.context, so when mask have DrawRoundRect is is rendered on wrong context, as a result mask is incorrect, may be empty at all, if no other command is there.

Thanks! :smile:


Microchip ADC driver fix

ADC readings with current microchip ADC driver aren't accurate.
ADC configuration register need to be programmed with appropriate values for high & low clock time values.

@jvasanth1 do help review this

@cfriedt can you help with this PR approval.


Release v3.2.1

Release Type
patch
For all releases Create prepare-release/x.y.z Branch

[ ] Ensure that you have up to date copy of main: git checkout main; git pull or a targeted release branch e.g. release/2.7.x: git checkout release/2.7.x; git pull
[ ] Create the prepare-release branch for the version (e.g. prepare-release/2.7.1): git branch -m prepare-release/2.7.1
[ ] Review carefully CHANGELOG.md. Manually reorder entries for relevance, common topic, adjust description, etc. - make it clear and easy to follow for users. Optionally headline notable changes (emojis are allowed). Double-check that dates are correct, that link anchors point to the correct header, and that you've included a link to the GitHub compare link at the end. If there were any RC releases before this version, fold their changes into the final release entry.
[ ] Resolve all licensing issues that FOSSA has detected. Go to Issues tab in FOSSA's KIC project and resolve every issue, inspecting if it's a false positive or not. ignored.go script should be useful to look for issues that have been already resolved and reappeared due to version changes.
[ ] Update ignored.json following instructions in README.
[ ] Retrieve the latest license report from FOSSA and save it to LICENSES (go to Reports tab in FOSSA's KIC project, select 'plain text' format, tick 'direct dependencies' and download it).
[ ] Ensure base manifest versions use the new version (config/image/enterprise/kustomization.yaml and config/image/oss/kustomization.yaml) and update manifest files: make manifests
[ ] Push the branch up to the remote: git push --set-upstream origin prepare-release/x.y.z

For all releases Create a Release Pull Request

[ ] Check the latest E2E nightly test run to confirm that E2E tests are succeeding. If you are backporting features into a non-main branch, run a targeted E2E job against that branch or use ci/run-e2e label on the PR preparing the release.
[ ] Open a PR from your branch to main. Set a backport release/X.Y.Z label.
[ ] If this is a patch release, ensure that the release branch (e.g. release/2.9.x) compared against the latest patch for this minor release (e.g. v2.9.0) includes the expected changes that the release should include (e.g. by checking https://github.com/kong/kubernetes-ingress-controller/compare/v2.9.0..release/2.9.x).
[ ] Once the PR is merged (the prepare-release/x.y.z branch will get automatically removed), approve and merge the automatic backport PR and initiate a release job on the main branch for major or minor release, for patch use the release branch. Your tag must use vX.Y.Z format. Set latest to true if this is be the latest release. That should be the case if a new major.minor release is done or a patch release is done on the latest minor version.
[ ] CI will validate the requested version, build and push an image, and run tests against the image before finally creating a tag and publishing a release. If tests fail, CI will push the image but not the tag or release. Investigate the failure, correct it as needed, and start a new release job.
[ ] The release workflow (.github/workflows/release.yaml) will update the latest branch - if the released version was set to be latest - to the just released tag.

For major/minor releases Create release/<MAJOR>.<MINOR>.x Branch

[ ] Create the release/<MAJOR>.<MINOR>.x branch at the place where you want to branch of off main. It should be done after the release workflow has run successfully.

For major/minor releases only Update Release documents

[ ] Trigger release_docs workflow. Note that you will need to update the new version's navigation manifest (e.g. for 2.7 to use the new files (CRDs and CLI arguments references) after.
[ ] Ensure a draft PR is created in docs.konghq.com repository.
[ ] If you are adding a new CRD, add a new description file under app/_includes/md/kic/crd-ref/. This is a brief description injected into the CRD reference page.
[ ] Update articles in the new version as needed.
[ ] Update reference/version-compatibility.md to include the new versions (make sure you capture any new Kubernetes/Istio versions that have been tested)
[ ] Copy app/_data/docs_nav_kic_OLDVERSION.yml to app/_data/docs_nav_kic_NEWVERSION.yml and update the release field to NEWVERSION. Add entries for any new articles.
[ ] Make sure that app/_data/docs_nav_kic_NEWVERSION.yml links to the latest generated custom-resources-X.X.X.md.
[ ] Add a section to app/_data/kong_versions.yml for your version and move the latest field to version that's being released.
[ ] Add entries in support policy documents: app/_src/kubernetes-ingress-controller/support-policy.md and app/_includes/md/kic/support.md.
[ ] Mark the PR ready for review.
[ ] Inform and ping the @Kong/team-k8s via slack of impending release with a link to the release PR.
[ ] Ensure that KGO works with the released version of KIC. Update and release it if needed.

For major/minor releases only Bump charts' dependencies

[ ] Synchronize config/crd/bases with [kong/kong charts CRDs][https://github.com/Kong/charts/blob/6c1421bf2f4/charts/kong/crds/custom-resource-definitions.yaml]
[ ] Update RBAC policy rules (kong.kubernetesRBACRules template) in [kong/kong's charts/kong/templates][https://github.com/Kong/charts/blob/0b1f635f180220f86d17f5b1b4dd60fc0dc35aae/charts/kong/templates/_helpers.tpl#L1292].
[ ] Bump the KIC version in the kong/kong Helm chart.
[ ] Release new version of the kong/kong Helm chart.
[ ] After kong/kong is released, bump the dependency on kong/kong chart in the kong/ingress Helm chart and release a new version of the chart.

Conformance tests report
Trigger for released version CI workflow Generate Kubernetes Gateway API conformance tests report, verify artifact and submit it to https://github.com/kubernetes-sigs/gateway-api/tree/main/conformance/reports. Update the KIC version in the README's Gateway API conformance badge.
Post release testing
Appoint volunteer(s) to perform end-to-end testing of newly released features by following official documentation. Testing should cover following all the newly added or modified guides/tutorials, etc.
Release Troubleshooting
The Release Troubleshooting guide covers strategies for dealing with a release that has failed.

Candidates to be included: (feel free to edit this message)

#6252
#6237

This release needs to contain the fix for Consumer Groups + HTTPRoutes too (no PR yet). I believe @rainest was looking in to it

Backporting PRs:

https://github.com/Kong/kubernetes-ingress-controller/pull/6259
https://github.com/Kong/kubernetes-ingress-controller/pull/6260


There are so new code that is not generic make that better

Segmentation
Threshold
Move towards fully generic image operations

All image operations are now generic. There were a problem that I had to take specialization away from some of them otherwise the problem failed.