Rocky 8.8: Credential error for task 'Disable the Next UI'

Hi,
While following the CIQ Blog post Ascender VM Basic Install Guide (Utilizes K3s), Ascender successfully installed but did present the error shown below.

Host: Rocky 8.8
Ledger not installed
Git commit: 9afd519

[root@ascender ascender-install]# ./setup.sh
Using Inventory File: ./inventory
...
...
TASK [ascender_cleanup : Wait until Ascender API is Up] *********************************************************************
ok: [localhost]

TASK [ascender_cleanup : Disable the Next UI] *******************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to get token: HTTP Error 401: Unauthorized", "response": "{\"detail\":\"Authentication credentials were not provided. To establish a login session, visit /api/login/.\"}"}

PLAY RECAP ******************************************************************************************************************
ascender_host              : ok=11   changed=1    unreachable=0    failed=0    skipped=5    rescued=0    ignored=0
localhost                  : ok=25   changed=6    unreachable=0    failed=1    skipped=5    rescued=0    ignored=0

ERROR OCCURRED DURING SETUP

Thats an odd error.  What did you supply for
ASCENDER_ADMIN_USER
ASCENDER_ADMIN_PASSWORD
in your default.config.yaml?

Our credentials resembled:
ASCENDER_ADMIN_USER: admin
ASCENDER_ADMIN_PASSWORD: "UPPERlower+["

If it helps, all Ascender-related pods are running, the web interface is being served, and I can successfully log into the web interface.

Adam:
I ran the installer with the target machine and installing machine being one and the same. While didn't recreate your issue, I am attaching my inventory and config (I matched your password) to see if you set up anything differently from me.config.zip

@michaelford85,
Thank your for your help on this. Some differences on our end I should have mentioned earlier are:
k8s_lb_protocol: https
tls_crt_path: "/etc/letsencrypt/live/ascender.our.domain/fullchain.pem"
tls_key_path: "/etc/letsencrypt/live/ascender.our.domain/privkey.pem"
use_etc_hosts: false

ASCENDER_HOSTNAME: ascender.our.domain

I don't believe its the special characters in the password causing it, at least not directly.  I have ran the install 10 times with that password, and it failed twice but not the other 8 times.  I am thinking we are running into a race condition where something on the backend is not fully up, even though the api itself is returning fine when we check the ping (which doesn't require auth).  I am running a few more tests to see if I can pin it down.

Even if it does fail, I can immediately rerun the cleanup playbook and it passes this time, so definitely not an issue with the password.

ok, after many many hours of testing and debugging.  It does appear to be a race condition where the API service comes up before the uWSGI, nginx, or daphne services.  This would cause the ping to return because it doesn't require authentication, but anything else would fail.
While debugging this, also found that if things were running really slow, even the database wasn't properly populated with the default items.
To combat both of these, we changed the API check to pull the id of the default organization instead.  This way, the API authentication has to be working, and the database has to be populated.


[Rule]: variable within documentation

It would be nice to have info that documentation contains robot variables. Sometimes, the idea is to escape the variable to document the variable name rather than its value.

It could be community rules - nothing enforced but available to be enabled.


make it compile on recent versions, remove deps on Core/Base etc.

Hi Philippe,
I updated the code to make it work on more recent versions (Caml -> Stdlib for instance) but while I was at it, I removed the dependencies on Base/Core which were not used that much and that was pulling too much dependencies for me...
Cheers,

Ha ha, I had forgotten this code completely. Thanks for the contribution, which looks fine to me. Should I release this on opam-repository?

Yes, that would be very nice. Thanks !


Feat: Add neo-tree.nvim

added support for neo-tree

Thanks!
I also see you kept it consistent to the nvim-tree colors, thank you for the attention to detail.


[FLINK-8101][flink-connectors] Elasticsearch 5.3+ (TransportClient) and 6.x (RestHighLevelClient) support

What is the purpose of the change
The purpose of this PR is to add Elasticsearch 6.X support on top of the RestHighLevelClient. Indeed TransportClient is now deprecated and will be removed in 8.X. Also the hosted version of Elasticsearch often forbid the use of TransportClient.
Brief change log

First a set of changes are borrowed from #4675:

Add createRequestIndex method in ElasticsearchApiCallBridge
Add flink-connector-elasticsearch5.3 project
Add BulkProcessorIndexer in connector-elasticsearch5.3 to convert ActionRequest to DocWriteRequest

Then on top of these changes and of being able to create a RestHighLevelClient instead of TransportClient:

Add createClient method in ElasticsearchApiCallBridge. As TransportClient and RestClient have only the AutoCloseable interface in common, this is what the method returns.
Make ElasticsearchSinkBase agnostic to whether it is using a TransportClient or RestClient by adding a createBulkProcessorBuilder method on ElasticsearchApiCallBridge that the ElasticsearchSinkBase calls. Implement this method on all bridges.
Add flink-connector-elasticsearch6 project leveraging Rest Client while all the other ones still use TransportClient.

Verifying this change
This change added tests and can be verified as follows:

Elasticsearch test base has also been reworked a little bit to leverage it for testing the Rest client base implementation.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): if you use the elasticsearch6 project, this adds dependencies on elasticsearch 6
The public API, i.e., is any changed class annotated with @Public(Evolving):  no
The serializers:  no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? docs & javadocs

@tzulitai did you have a chance to look at this? If you have any question please let me know?

@cjolif sorry, I didn't have the chance, yet.
But I agree that we should try getting this in for 1.5 (I saw your reply on the 1.5 release discussion thread in the mailing lists). I'll try to get back to this as soon as possible.

We were in the process of testing the Flink integration with the ES High Level Rest client in order to perform upgrades to ES6 and stumbled on some issues related to the bulk rejection retry handling. In short, swapping in the HLR backend will not perform retries correctly and it is not actually safe to simply call add on the RequestIndexer that is sent into the ActionRequestFailureHander from the Flink-side sink due to some synchronization issues.
I have created a bug report that has been accepted on the Elasticsearch side https://github.com/elastic/elasticsearch/issues/28885 to automatically perform retries.
One additional note however is that in the case where the retries have been used up from the BackoffPolicy, using the RetryRejectionFailureHandler appears to cause a deadlock, so this may be something to fix on the ElasticsearchSink side. But it may be necessary to independently confirm that in case that is an issue particular to my testing. (TL;DR: The RetryRejectionFailureHandler is not safe to use with HLR and I am not certain it's safe to use with the TransportClient based one either in the case that it actually triggers).

good news the issue reported by @jdewald is now fixed in Elasticsearch master. Not sure which version of Elasticsearch will contain the fix though.

@tzulitai sure. done.


Ground item value seperation

Would be cool to have a "," separate bills,mills,k's and normal gps so for example
1B,1M,200K,400

Should follow the same pattern stacks of items in game use.
1 - 99,999
100k-9999k
10m-9999m

I think this was fixed by #788

I think this is invalid. Dropped stacks can't be over 65535.

I figured the numbers > 65535 were in reference to the monetary value, not the number of items on the ground

Oh. In that case yes it was fixed in #788


Vertical Alignemt for Grid

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
A Grid with an item that contains a Typography and another item that contains a button (both on the same row). The typography and text of the button are not vertically aligned.

Expected behavior 🤔
I expect that the Typography and the text of the button to be vertically aligned.
Steps to reproduce 🕹
This is the link for the sandbox: Test Vertical Alignment
Context 🔦
We are trying to align the text with three buttons not just 1. The same happens using a Toolbar.

  Output from `npx @mui/envinfo` goes here.

The behavior is consistent with CSS grid. To align baselines in your example use alignItems: 'baseline' instead of 'center'.


Warning when export onnx model

Env

onnx verson
1.15
torch version
2.1.2
tensorrt version
8.6.1

Your problem

An warning occurred when the model is converted to an onnx model. Is this a serious problem?

Just warnings.
Do not matter.


Mark the ServiceFabric package as non-shipping

We don't plan to ship the SF package with 1.0 so I've marked it as non-packable like we did for k8. We'll revisit post-1.0.
Downside: We won't ship any more previews of this package in the meantime.
Alternatives:

Continue to ship previews and only disable this for the final 1.0 release.
Categorize packages such that the ones we do want for 1.0 get a final release and the others stay on previews (how?).

Thoughts?

Closing for now, there are other plans here.


Allow older versions of graphql module.

The version of graphql in package.json peerDependencies is the latest version; however, we should allow older, compatible versions as well.

We now allow versions >=0.10.0


Invalid or Missing CSRF token

Whenever I try to login to todoist desktop it opens a page in my browser (here firefox). The page just displays a dialog box with the error "Invalid or Missing CSRF token"

hi @TejasAvinashShetty, thanks for letting me know.
Are you trying to log in with login/pass or through google?

Yes.
Sorry, I  think a similar issue has been posted earlier.
https://github.com/KryDos/todoist-linux/issues/15#issue-345564267
I really should have searched better for similar issues before opening a new issue.

Don't worry. I'm closing this one and I hope that https://github.com/KryDos/todoist-linux/issues/15 will be fixed soon

Great
Regards,
Tejas Shetty
B Tech.Pharma
Department of Pharmaceutical Science and Technology
Institute of Chemical Technology, Matunga,
Maharashtra, India.
Contact No.: +91<PHONE_NUMBER>,9004350057,8450978380,022 25582905
Email ID<EMAIL_ADDRESS>Sent with Shift
https://tryshift.com/?utm_source=SentWithShift&utm_campaign=Sent with Shift Signature&utm_medium=Email Signature&utm_content=General Email Group
On Sun, Feb 10, 2019 at 1:39 AM Ruslan Bekenev<EMAIL_ADDRESS>wrote:

Don't worry. I'm closing this one and I hope that #15
https://github.com/KryDos/todoist-linux/issues/15 will be fixed soon
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KryDos/todoist-linux/issues/30#issuecomment-462075287,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AaLKXo9Jzi0svDXDDhIuNkgk1fFq081vks5vLyregaJpZM4aya6B
.


Add DataMC link in readme.md

Hi,
I would to update the readme

Thanks @YKlausz for adding the DataMC PaaS to the aweseome-docker list!!


chore(release): v1.0.0

Cut major release v1.0.0 🚀

[x] Ensure the e2e nightly tests on v1.x are passing for at least a couple of days before cutting the release.
[x] Update docs/tutorials/forum-application/9.run-app.md to mention v1.0.0
[x] Update version.go
[x] Update summary.md in .changelog
[x] Update CHANGELOG.md
[x] Bump github.com/cometbft/cometbft/api from 1.0.0-rc2 to 1.0.0 in go.mod

[x] ensure cometbft/api is tagged first (#4666)
[x] add changelog entry

[x] Publish protos to Buf registry

References:

https://github.com/cometbft/cometbft/blob/main/RELEASES.md#major-release

All tasks completed and released https://github.com/cometbft/cometbft/releases/tag/v1.0.0


Invalid LLVM bytecode emitted for calls to void functions

Testcase: compile/expression/call/call-void-ok.protosnirk
Code to reproduce:
fn main()
    main()

LLVM gives an error because we attempt to generate this code:
%call_main-ok = call void @main()

Closed in #85.


Forward RTMP Payload to ffmpeg

Hi,
You did a wonderful job. i tried to use your rtmp server to forward flv raw data into ffmpeg pipe0. in practice i tried to forward every single bytes as you did in httpFlv into ffmpeg pipe0 but i get error "pipe:0: Invalid data found when processing input". could you give me a guide how i can forward rtmp packets which taken from rtmp server into ffmpeg?
thanks

Could you show me the full ffmpeg command?  so that I can have a clear view about it

Could you show me the full ffmpeg command?  so that I can have a clear view about it


Eyes are too far apart on Samsung S7 at 1920x1080 scaled resolution

Description:
Taking the example from the repo (0.10.6), the eyes are too far apart if the device resolution is set to a scaled 1920 x 1080. I effectively see 2 cubes and 2 reticles.
If I set the device resolution to native 2560 x 1440, it works as expected.
Additional Information:

webvr-polyfill version: (0.10.6)
Browser name/version/release channel: Chrome 67.0.3396.87
Operating System: Android 8.0.0 SM-G930F Build/R16NW

Potentially related to: https://github.com/immersive-web/webvr-polyfill/issues/312

Samsung devices that have dynamic resolution fail when not at their max resolution/utilizing full performance. There are some potential workarounds, but this is due to hardcoding the resolutions per device -> https://github.com/immersive-web/cardboard-vr-display/issues/7


horizontal scroll bar

Please let me know how to add horizontal scroll bar rather than increasing width of the control. Vertical scroll bar is populated by default when I have more items, needed same horizontal scroll bar for wider items. Thank you.

In css, div.record-picker horizontal scroll bar is deliberately hidden
overflow-x: hidden
Until any solution provided, you can override/change css to overflow-x: auto; as a way around.


client side hydrates error when I use 'useAsync'

client side hydrates error，so I can't emit any click event after the streamEnd。
here is the error:
createErrorWithCleanStackTrace.js:9 Uncaught Error<EMAIL_ADDRESS>You stumbled upon a bug in react-streaming's source code. Reach out at https://github.com/brillout/react-streaming/issues/new or https://discord.com/invite/H23tjRxFvx and include this error stack (the error stack is usually enough to fix the problem). A maintainer will fix the bug (usually under 24 hours). Do not hesitate to reach out as it makes react-streaming more robust.
    at Object.<anonymous> (debug.js:10:1)
    at ./node_modules/react-streaming/dist/cjs/utils/debug.js (debug.js:98:1)
    at __webpack_require__ (bootstrap:19:1)
    at ./node_modules/react-streaming/dist/cjs/server/utils.js (utils.js:19:14)
    at __webpack_require__ (bootstrap:19:1)
    at ./node_modules/react-streaming/dist/cjs/server/useStream.js (useStream.js:28:17)
    at __webpack_require__ (bootstrap:19:1)
    at ./node_modules/react-streaming/dist/cjs/server/useAsync.js (useAsync.js:5:21)
    at __webpack_require__ (bootstrap:19:1)
    at ./node_modules/react-streaming/dist/cjs/server/hooks.js (hooks.js:4:18)
    at __webpack_require__ (bootstrap:19:1)
    at ./src/Page.jsx (module.js:22:1)
    at __webpack_require__ (bootstrap:19:1)
    at ./src/react18client/index.js (index.js:1:1)
    at __webpack_require__ (bootstrap:19:1)
    at bootstrap:83:1
    at bootstrap:83:1

here is my code:
1.server side:
        const { pipe, abort, streamEnd, injectToStream } = await renderToStream(

            <Page />

,
          { disable: false }
        );

        pipe(res);
        injectToStream('');

2.client side:
import { hydrateRoot } from "react-dom/client.js";
import Page from "../Page.jsx";

const root = document.getElementById("root");

hydrateRoot(root, <Page />);

Page.jsx

import React, { useState, Suspense } from "react";
import { useAsync } from "react-streaming";

export default function Page() {
  return (
    <>

Welcome

      This page is:

          <Suspense fallback={
Loading...
}>
            <LazyComponent />
          </Suspense>

Rendered to HTML.

          Interactive. <Counter />

    </>
  );
}
function Counter() {
  const [count, setCount] = useState(0);
  return (
    <button
      type="button"
      onClick={() => {
        console.log("count!");
        setCount((count) => count + 1);
      }}
    >
      Counter {count}
    </button>
  );
}

function LazyComponent() {
  // hydrate error here
  const val = useAsync(
    "hello-component-key",
    () =>
      new Promise((resolve) => {
        setTimeout(() => resolve("Hello, I was lazy."), 1000);
      })
  );
  return
{val}
;
}

if I remove the "useAsync" and "Suspense"，hydrate success，I can click the Button and Emit the click event that I've bind，everything is find。
Could you please take a look at this issues? :)

The stack trace is broken. Can you publish a reproduction?

The stack trace is broken. Can you publish a reproduction?
The console is showing this error all the time

createErrorWithCleanStackTrace.js:9 Uncaught Error<EMAIL_ADDRESS>You stumbled upon a bug in react-streaming's source code. Reach out at https://github.com/brillout/react-streaming/issues/new or https://discord.com/invite/H23tjRxFvx and include this error stack (the error stack is usually enough to fix the problem). A maintainer will fix the bug (usually under 24 hours). Do not hesitate to reach out as it makes react-streaming more robust.
    at Object.<anonymous> (debug.js:10:1)
    at ./node_modules/react-streaming/dist/cjs/utils/debug.js (debug.js:98:1)
    at __webpack_require__ (bootstrap:19:1)
    at ./node_modules/react-streaming/dist/cjs/server/utils.js (utils.js:19:14)
    at __webpack_require__ (bootstrap:19:1)
    at ./node_modules/react-streaming/dist/cjs/server/useStream.js (useStream.js:28:17)
    at __webpack_require__ (bootstrap:19:1)
    at ./node_modules/react-streaming/dist/cjs/server/useAsync.js (useAsync.js:5:21)
    at __webpack_require__ (bootstrap:19:1)
    at ./node_modules/react-streaming/dist/cjs/server/hooks.js (hooks.js:4:18)
    at __webpack_require__ (bootstrap:19:1)
    at ./src/Page.jsx (module.js:22:1)
    at __webpack_require__ (bootstrap:19:1)
    at ./src/react18client/index.js (index.js:1:1)
    at __webpack_require__ (bootstrap:19:1)
    at bootstrap:83:1
    at bootstrap:83:1

here is the code:
https://github.com/NikaidouSkin42/react-streaming-demo1

I get another error:
gitpod /workspace/react-streaming-demo1 (main) $ npm run build

><EMAIL_ADDRESS>build
> npm-run-all build:*

><EMAIL_ADDRESS>build:server
> webpack --config webpack.server.config.js

node:internal/crypto/hash:71
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/workspace/react-streaming-demo1/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/workspace/react-streaming-demo1/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/workspace/react-streaming-demo1/node_modules/webpack/lib/NormalModule.js:471:10)
    at /workspace/react-streaming-demo1/node_modules/webpack/lib/NormalModule.js:503:5
    at /workspace/react-streaming-demo1/node_modules/webpack/lib/NormalModule.js:358:12
    at /workspace/react-streaming-demo1/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/workspace/react-streaming-demo1/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at iterateNormalLoaders (/workspace/react-streaming-demo1/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
    at /workspace/react-streaming-demo1/node_modules/loader-runner/lib/LoaderRunner.js:236:3
    at context.callback (/workspace/react-streaming-demo1/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at /workspace/react-streaming-demo1/node_modules/babel-loader/lib/index.js:44:71 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.16.0
ERROR: "build:server" exited with 1.

Which seems unrelated to react-streaming.
I'm running the code on https://gitpod.io#https://github.com/NikaidouSkin42/react-streaming-demo1.

Node.js 12 (and 14) are now deprecated. Can you try yourself on GitPod? And report back if you find a non-deprecated Node.js version that works.

Node.js 12 (and 14) are now deprecated. Can you try yourself on GitPod? And report back if you find a non-deprecated Node.js version that works.
I install a NVM and switch Node.js to v12，it works。
https://nikaidouski-reactstream-msvmgv4ibkq.ws-us98.gitpod.io

react-streaming doesn't support Node.js 12. So I won't debug a reproduction running on Node.js 12.

react-streaming doesn't support Node.js 12. So I won't debug a reproduction running on Node.js 12.

 it still works on Node.js 16 :
# for macOS, Linux or Windows Git Bash
export NODE_OPTIONS=--openssl-legacy-provider

# for Windows CMD (Command Prompt)
set NODE_OPTIONS=--openssl-legacy-provider

# for Windows PowerShell
$env:NODE_OPTIONS="--openssl-legacy-provider"

I could reproduce. Seems like a webpack misconfiguration. Stay tuned.

Update to 0.3.12 and follow the instructions of the new error.
Btw. in case you think you can convince your employer: https://github.com/sponsors/brillout.


Update categories

Currently these are the categories we have:

I find that some of the categories are unnecessary and somewhat overlap with each other.
I suggest we go for:

🙏    Help needed

Are you having trouble using ADS? Ask the community for help.

💡     Ideas of new features

Share ideas for new features.

#⃣     Bug reports, suggestions for code refactoring

If you encounter a bug, or if you would like to discuss technicalities, please post here.

Updated. Also added:
🙌Show and tell
Show off something you've made or published with ADS


clean up unmatched right single quotes at the end

There are certain situations where unmatched right quotes weren't being caught, so we're doing a final pass after everything else to curl them.

👍  from nelson. "wow what a cool dude"

the reviews are in: ‘it curls the unmatched single quotes’ - roger ebert
⭐⭐⭐⭐⭐ - New York Times
👍 - mike schneider

👍  Thanks for updating the test


📝 README 초안

Please check if the PR fulfills these requirements

[x] Name of Project
[x] Introducing Purpose and Tech Stack
[x] Introducing Contributor

Review Complete.


Data binding with library

Hey developers,  How can I use data  binding  in  my application because  I am  new to  data  binding  concept ?
I have  an  application  module  and  one  android  lib. Module  which  has  all the  entites  those  are used in app module l..
So how  can I  use  data binding  in  my  app  with  lib. Module..
Which also include  dynamic inflation of view  based on parameter in some of the  entities in library module

sorry, i see it late.  you mean want to use  'android-databinding ' with local build ?

if you only want to use this in local build.  you must download the all refer librarys .
this is the extra  three libs:
compile 'com.heaven7.core.adapter:adapter:1.0'
compile 'com.heaven7.anno:android-anno:1.0'
compile 'com.heaven7.core.util:util-v1:1.0.1'
you can just import them as a jar.


TypeError: Cannot read property 'kind' of undefined in 'Object.isIdentifier' during 'getCodeFixes'

This issue comes from crash dumps in telemetry. We've tried to de-duplicate issues on a best-effort basis, comparing the sequence of methods called and the command requested while ignoring line numbers.
TypeScript Version Prefix: 2.7.1
VSCode Version 1.19.3
command requested: getCodeFixes
hitting sessions: 1248
proportion of all sessions: 0.004658924191687852
stack
TypeError: Cannot read property 'kind' of undefined
    at Object.isIdentifier (tsserver.js:9638:20)
    at getCodeActionForParameters (tsserver.js:79045:21)
    at getFix (tsserver.js:79003:27)
    at Object.getCodeActions (tsserver.js:78950:27)
    at unknown (tsserver.js:77059:33)
    at Object.forEach (tsserver.js:1430:30)
    at Object.getFixes (tsserver.js:77058:16)
    at unknown (tsserver.js:83206:35)
    at Object.flatMap (tsserver.js:1697:25)
    at Object.getCodeFixesAtPosition (tsserver.js:83204:23)
    at IOSession.Session.getCodeFixes (tsserver.js:90228:64)
    at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (tsserver.js:89132:61)
    at unknown (tsserver.js:90393:88)
    at IOSession.Session.executeWithRequestId (tsserver.js:90384:28)
    at IOSession.Session.executeCommand (tsserver.js:90393:33)
    at IOSession.Session.onMessage (tsserver.js:90413:35)
    at Interface.<anonymous> (tsserver.js:91614:27)
    at emitOne (events.js:96:13)
    at Interface.emit (events.js:191:7)
    at Interface._onLine (readline.js:241:10)
    at Interface._normalWrite (readline.js:384:12)
    at Socket.ondata (readline.js:101:10)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
    at Socket.Readable.push (_stream_readable.js:136:10)
    at Pipe.onread (net.js:560:20)

This issue reproduced in the following context:
TypeScript Version Prefix: 2.7.2
VSCode Version 1.20.1
command requested: getCodeFixes
hitting sessions: 164
proportion of all sessions: 0.038175046554934824
stack
TypeError: Cannot read property 'kind' of undefined
    at Object.isIdentifier (tsserver.js:9640:20)
    at getCodeActionForParameters (tsserver.js:79205:21)
    at getFix (tsserver.js:79163:27)
    at Object.getCodeActions (tsserver.js:79110:27)
    at unknown (tsserver.js:77219:33)
    at Object.forEach (tsserver.js:1431:30)
    at Object.getFixes (tsserver.js:77218:16)
    at unknown (tsserver.js:83366:35)
    at Object.flatMap (tsserver.js:1698:25)
    at Object.getCodeFixesAtPosition (tsserver.js:83364:23)
    at IOSession.Session.getCodeFixes (tsserver.js:90388:64)
    at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (tsserver.js:89292:61)
    at unknown (tsserver.js:90553:88)
    at IOSession.Session.executeWithRequestId (tsserver.js:90544:28)
    at IOSession.Session.executeCommand (tsserver.js:90553:33)
    at IOSession.Session.onMessage (tsserver.js:90573:35)
    at Interface.<anonymous> (tsserver.js:91774:27)
    at emitOne (events.js:96:13)
    at Interface.emit (events.js:191:7)
    at Interface._onLine (readline.js:241:10)
    at Interface._normalWrite (readline.js:384:12)
    at Socket.ondata (readline.js:101:10)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
    at Socket.Readable.push (_stream_readable.js:136:10)
    at Pipe.onread (net.js:560:20)


Try ngx-virtual-scroller 3

Version 3 came out recently!
https://github.com/rintoj/ngx-virtual-scroller/blob/master/CHANGELOG.md#v300
Also, Angular 8 is coming soon 😁

I tried that in image-viewer actually - worked fine (it's not a big change, but someone complained about breaking changes in minor versions 👍 ).
Didn't try too hard but I didn't get the cool scroll thing working - I think you have to append or something, not replace... Worth investigation! 👍

What's the "cool scroll thing"? 🙃

If items array is prepended with additional items, keep scroll on currently visible items, if possible.

Ideally this would let us update the array (by filtering new terms), while keeping the current items scrolled-to on screen! 😄

I'll glance at it, but most likely I'll keep behavior in the app as is. Perhaps include a "scroll to top" behavior whenever a search occurs. Unsure what the current behavior is like 😅


Add Prettier

Add this to the repo! https://prettier.io/

I can work on this!

A couple questions:

Would you like prettier to be applied to the whole project (with the pre-set rules)? Or would you like a prettierrc file to specify what rules you'd like applied?
If you'd like a prettierrc file, would you only want it applied to certain flies?
A bit different, but would you like to include continuous integration?

standard rules, don't run it on the project as I wouldn't wanna cause a bunch of merge conflicts
don't really care for prettierrc, kind of just wanna role with the defaults
CI is a great idea and could be included in a separate PR :)


Downgrade the vulkan abort logic to a warning

This addresses issues where some drivers are reporting they don't meet the vulkan hardware level 1 support requirements even though they render as expected when the check is removed.

That would atleast let people run it but I'm concerned that this would not be a nice user experience for normal users.
The big question is, why we're getting reports that devices that do support the renderer and supposedly have hardware level 1 support, are not being reported as such. Might be an issue at their end off course.
Also you mentioned in chat the Quest 1 fails to run , it would be good to know what it fails on because it used to work with our Vulkan renderer (unless my memory fails me and I already had a Quest 2 when we got it up and running).

Also you mentioned in chat the Quest 1 fails to run , it would be good to know what it fails on because it used to work with our Vulkan renderer (unless my memory fails me and I already had a Quest 2 when we got it up and running).

@BastiaanOlij Could be that you tested on the Quest 2. Quest 2 works fine with the Vulkan mobile renderer, but Quest 1 fails even if you load a build prior to my additions of the vulkan checks.
Do you still have a Quest 1 you can check against?

I have a Quest 1 sitting in the cupboard, I'd probably need to charge it and somehow get the new firmware on it. Ever since I had my Quest 2 I've not had a use for it and that was pre account changes.
With Meta retiring the Quest 1 in a few months (a decision I don't agree with, but that is a topic for another time and place), it may not be worth spending too much time on?

So I spoke internally about this and while our driver supports the ASTC texture format, it is not a hardware path. So we cannot claim level 1, but everything appears to work as expected with this check disabled.
Maybe using vkGetPhysicalDeviceFeatures is a better check, we report "true" for ASTC.

With this change, what do users see when they attempt to run a Vulkan game but don't have hardware level 1 support?

@clayjohn with this update, they don't see anything but we log the fact the requirements check failed, which we can use for troubleshooting.

Maybe we should add a check for FEATURE_VULKAN_HARDWARE_VERSION then. That way we can at least have the nice message for devices that don't support hardware accelerated Vulkan 1.0 (this is a heard requirement for us a software implementation of Vulkan 1.0 is not suitable). I am mostly concerned about devices that don't support Vulkan at all. We have already had multiple bug reports from users complaining about a black screen when running on Android when using devices that do not have any Vulkan support at all

@rbessems does what @clayjohn suggest work for the chipset you guys are using?

Thanks!

@BastiaanOlij on our platform FEATURE_VULKAN_HARDWARE_VERSION reports: 4198400 (which I think resolves to vulkan 1.1)

We really need to check version or we will get an onslaught of "black screen" bug reports on android with each release. We have two already today https://github.com/godotengine/godot/issues/72910, https://github.com/godotengine/godot/issues/72888

@clayjohn agreed, but seeing the time window and that we're still figuring this out, I take an existing problem of Godot starting on phones that don't support it, over Godot not starting on high end devices that it runs fine on.
But fully agree we need to get this right ASAP.


fix: minecraft_play_time_ticks_total

This should fix #79
Signed-off-by: Kevin Belisle<EMAIL_ADDRESS>

@KevBelisle can you resolve the conflict and change the description in the README.md too please?
Then I can merge the PR and create a new release. Thanks!

Done!
The description in the README.md should already be ok.

Thanks @KevBelisle! Its merged!


Protect local data in Tchap

Enable the protection of the local data by considering the existing PR in matrix android sdk: https://github.com/matrix-org/matrix-android-sdk/pull/305

@giomfo : after the merge of Riot, please enable Data encryption by settings in Matrix.java member CONFIG_ENABLE_LOCAL_FILE_ENCRYPTION to true.

done

@af-anssi, @jp-modernisation-gouv-fr  : FYI we disabled local file encryption until #383 is fixed


Rename negamax function to alpha_beta

Due to changing the original algorithm from negamax to alpha-beta pruning the function name has been modified to "alpha_beta"

Negamax and alpha-beta pruning are not two opposing algorithms. More precisely, the current implementation utilizes negamax with alpha-beta pruning. Therefore, I am wondering if changing the name might actually decrease the program's readability.

@ndsl7109256 Yes I can understand your considerations.
Perhaps I can left a comment in the negamax function in the program to explain that is not origin negamax algorithm?

I don't have opinions on whether to add comments.
If you believe that comments would be helpful for the code, feel free to do so.


fix: input can't be updated in real time #146

fix input binding value can't be updated #146
remove extra space in class names

Fixing a bug requires adding a unit test


PromiseLike.then returns PromiseLike<Promise<T>> instead of PromiseLike<T>

TypeScript Version:  nightly (2.6.0-dev.20170817)
Code
declare const p: PromiseLike<string>;
const x: PromiseLike<number> = p.then(() => Promise.resolve(1));

Expected behavior:
No error.
Actual behavior:
src/a.ts(2,7): error TS2322: Type 'PromiseLike<Promise<number>>' is not assignable to type 'PromiseLike<number>'.
  Type 'Promise<number>' is not assignable to type 'number'.

Discovered in DefinitelyTyped/types/xadesjs.

Old issue, but this was fixed back in #40002.


[Help Wanted] [PLT-5954] Add reactions to post entities

If you're interested please comment here and come join our "Contributors" community channel on our daily build server, where you can discuss questions with community members and the Mattermost core team. For technical advice or questions, please  join our "Developers" community channel.
New contributors please see our Developer's Guide, specifically for machine setup and for developer workflow.

Notes: Jira ticket

Closing, this was a test issue


Site: refactor Form Elements (Pledge)

Description
This PR is a side work while working on the new Resources page which will have some new input elements (checkboxes, selects).
Because this PR is touching all inputs on the PLEDGE site, I separated this PR from the other one.

improve types for InputField and TextAreaField (=> see review comment here)
improve input fiel error mapping types (=> see review comment here)
simplify errors translation mappings for Form components

Related Ticket
Preparation for https://github.com/KlimaDAO/klimadao/issues/534
Checklist

[x] Building the site with npm run build-site works without errors
[x] Building the app with npm run build-app works without errors
[x] I formatted JS and TS files with running npm run format-all

@Atmosfearful @0xAeterno
I refactored the Form components to simplify the error transaltions rendering and mapping for Pledge and resources.
Please check again 🙏


Allow importing from multiple dumps in case of oracle

Per #161, the Oracle connector is now able to import a database from multiple dump files.
The server and connector is not ready to handle multiple files however, so we'd need to introduce this possibility.
This won't be a small feat, however, because:

The server only allows uploading one file
The server only allows selecting one file
The server only sends a single URL to the connector to download
The connector only anticipates a single URL
The connector freaks out and fails if there are multiple files in an archive
This only needs to be implemented for Oracle, but not others.

We may be looking at a bigger refactor.

Yes, I thought so, that's why I did not go into this part and rather "left it to you" :) And taking into consideration the fact that very seldom we get exports made into multiple dump files (so the feature will be very rarely needed, it seems now), this really looks like too much hassle for almost nothing. However, it would be really nice and professional to have this feature though. As you think, Dani.

I just received a dump in 3 files from a customer. Could be that this won't be such a rare use case after all, especially as the customers' database will grow bigger and bigger.

Migrated to https://github.com/djavorszky/liferay-support-ee/issues


Switch from configmap for leader election to lease

Since we already don't support older k8s versions it probably makes more sense to use the new dedicated resource type.

Looks like controller-runtime sets this as the default in version v0.12.0:
https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.12.0
I'm pretty sure we could override this on the version we currently use. But this could be one reason to consider updating this dependency.


[FEATURE]

Is your feature request related to a problem? Please describe.
yes . Sharepoint Modernization tool.
https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-scanner
Describe the solution you'd like
We are facing issues after running the setup . It immediately stop saying "The application has stopped working"
We are running it in our Office 365 enviroment using global admin credentials
Describe alternatives you've considered
We would like to run the tool using any of the authendication methods.
Additional context
Add any other context or screenshots about the feature request here.

Hi @sush315 ,
Can you provide more details on the what error you're getting? It seems as if you're providing invalid input to the scan and therefore it fails...

Hi,
We are following the instructions provided in the below link.
https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-scanner
We are just downloading the setup and then running it
using the option of Authenticate via credentials, We are providing global admin credentials for that.
Please confirm if we are missing out some steps as this is a new tool and we are using first time. Attaching the screen shot of the error.

@sush315 : I don't see any screenshot? If you open a command prompt and launch the scanner.exe from there you still get the UI, but once an error happens it should stay visible in the command prompt window. Without error information there's not much I can do

hi,
We tried the command prompt option . Please find screen shot attached.
Error File.docx
Error File.docx

I assume you're scanning SharePoint Online...the scanner does not work for SharePoint On-premises.
Second thing: the scanner requires the .Net 4.6.1 framework or higher to be installed. Can you cross check what versions are installed on your computer?
What input are you providing in the wizard? Please check https://aka.ms/sharepoint/modernization/scanner to learn more about how to use the scanner

We have the correct .Net installed and we are using Authenticate via credentials, We are providing global admin credentials.
Is there a way we can have a screen sharing session so that you can take a look at the issue we are facing.

Please make screenshots of each page of the wizard and send those...I'm currently OOF but will try to see what I can do

Please find all the screen shots. Please provide resolution as the earliest as we are looking forward to migration and need the reports on priority

When you enter the tenant name you only need to specify the name, you can leave out https://. So in your case tenant name needs to be entered as bd1-admin

Yes that is what we are doing.
On Mon, Aug 3, 2020, 6:19 PM Bert Jansen<EMAIL_ADDRESS>wrote:

When you enter the tenant name you only need to specify the name, you can
leave out https://. So in your case tenant name needs to be entered as
bd1-admin
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pnp/sp-dev-modernization/issues/504#issuecomment-668004131,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVGEWWY7BWRZWM5RY2SDUTR62W5HANCNFSM4PCUVAYA
.

No, your screenshot shows you've entered the https:// in front of the tenant name, that's not needed

We have tested that we are only entering bd1-admin in the middle box. The https:// is pre fixed in first box and greyed out cannot be removed or changed.

Please test with scanning a single site and see if that helps...

we tried with single URL . still same issue.

Can you confirm the used account can access the site collection being scanned? The account should be site collection admin.
Plan B is trying with app-only (which is anyhow the recommended approach for scanning a complete tenant). Please configure Azure AD app-only and use that.

Yes the account has full access.
We need the steps to configure that. Can you please setup a remote session
with us as it's getting delayed now.
On Fri, Aug 7, 2020, 1:16 AM Bert Jansen<EMAIL_ADDRESS>wrote:

Can you confirm the used account can access the site collection being
scanned? The account should be site collection admin.
Plan B is trying with app-only (which is anyhow the recommended approach
for scanning a complete tenant). Please configure Azure AD app-only and use
that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pnp/sp-dev-modernization/issues/504#issuecomment-670157231,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVGEWWTJOHU5T4OV2OOOD3R7MCCZANCNFSM4PCUVAYA
.

see https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-scanner#step-2-preparing-for-a-scan

Do we need Azure admin console to run it.
Please provide us how to install it .
On Fri, Aug 7, 2020, 12:51 PM Bert Jansen<EMAIL_ADDRESS>wrote:

see
https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-scanner#step-2-preparing-for-a-scan
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pnp/sp-dev-modernization/issues/504#issuecomment-670370984,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVGEWVF46P2EXPYPGN2Z43R7OTPJANCNFSM4PCUVAYA
.

The steps to properly configure Azure AD app-only require admin access to Azure AD. Please work with your admins to configure that. If you are tenant admin yourself you can follow the instructions in the documentation I shared earlier on: https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-scanner#step-2-preparing-for-a-scan

We are unable to execute the below command
Initialize-PnPPowerShellAuthentication -ApplicationName ModernizationScannerApp -Tenant contoso.onmicrosoft.com -Scopes "SPO.Sites.FullControl.All","MSGraph.Group.Read.All"  -OutPath c:\temp -CertificatePassword (ConvertTo-SecureString -String "password" -AsPlainText -Force)
Please let us know which console should we use to run this commaand. We are using sharepointonline managment shell.
We have used
Connect-pnpservices
connect-sposervices
Still it fails with error Initialize-PnPPowerShellAuthentication is not a recognized command.

Hi ,
We are not getting any response on this issue as already informed its an urgent issue as we are looking as big migration.
Just wanted to inform you that we have maanged to resolve the previous issue but now while running the below command we are getting error exactly after entering the "Tenant " parameter.

Seems there are too many things getting mixed up...please contact me at<EMAIL_ADDRESS>for a Teams session to help you get the scanner running. Please ensure you've tenant admin credentials available before the call. I'll close this issue as we're following this up via email.


refactor(pose_initializer): rework parameters

Description
Implement the ROS Node configuration layout described in https://github.com/orgs/autowarefoundation/discussions/3371 for the pose_initializer package.

Create the schema

Tests performed
Package build and launch locally.
colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release --packages-up-to pose_initializer
Effects on system behavior
More reliable and faster parameter configuration file creation.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

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

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

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

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

[x] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

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

@PhoebeWu21 Thanks for making the PR!
Unfortunately, we want to avoid managing ndt_enabled and others in pose_initializer.param.yaml.
For example, this launch file rewrites ndt_enabled based on the runtime arguments.
Therefore, I would like you to revert the changes to pose_initializer.param.yaml and pose_initializer.launch.xml and make the PR just add a schema.json file. :pray:
(Also, I am not familiar with the syntax of json.scheme, but I think the default in json.scheme needs to be removed if my request is to be reflected.)

@KYabuuchi Got it. But if remove ndt_enabled and others from the pose_initializer.param.yaml file, they should also be remove from the schema file to pass the build-and-test check.

@PhoebeWu21  Hmm, I'm not familier in JSON schema validation, but  is the only way to pass the build-and-test to remove parameters not included in param.yaml from the json.schema?
In my understanding, the purpose of json.schema is to define the parameters that nodes require, so I thought that json.schema should include ndt_enabled and others as much as possible.
If we have no choice except to remove them, I would like you to proceed in that manner.

@PhoebeWu21 Thanks for making the PR! Unfortunately, we want to avoid managing ndt_enabled and others in pose_initializer.param.yaml. For example, this launch file rewrites ndt_enabled based on the runtime arguments.
Therefore, I would like you to revert the changes to pose_initializer.param.yaml and pose_initializer.launch.xml and make the PR just add a schema.json file. 🙏
(Also, I am not familiar with the syntax of json.scheme, but I think the default in json.scheme needs to be removed if my request is to be reflected.)

@KYabuuchi Got it. But if remove ndt_enabled and others from the pose_initializer.param.yaml file, they should also be removed from the schema file to pass the build-and-test check.

@PhoebeWu21 Hmm, I'm not familier in JSON schema validation, but is the only way to pass the build-and-test to remove parameters not included in param.yaml from the json.schema? In my understanding, the purpose of json.schema is to define the parameters that nodes require, so I thought that json.schema should include ndt_enabled and others as much as possible.
If we have no choice except to remove them, I would like you to proceed in that manner.

Hi @kaspermeck-arm @ambroise-arm, I am not sure if there is other methods to deal with this situation. Please give me some advice, thank you.

Unfortunately, we want to avoid managing ndt_enabled and others in pose_initializer.param.yaml.

@KYabuuchi  The goal of the change is not to manage the parameters in pose_initializer.param.yaml. The goal is to move the default values of the parameters from the launch file of the package to the config file of the package.
Looking at another launch file from the same tier4_localization_launch package you linked to, I see https://github.com/autowarefoundation/autoware.universe/blob/main/launch/tier4_localization_launch/launch/pose_twist_fusion_filter/pose_twist_fusion_filter.launch.xml#L41 simply references the default values from the config file.
So @PhoebeWu21 it may just be about adding a <arg name="config_file" value="$(find-pkg-share pose_initializer)/config/pose_initializer.param.yaml"/> line to https://github.com/autowarefoundation/autoware.universe/blob/main/launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml#L14 (or something like that)

@ambroise-arm  Thank you for clarifying the goal.  :smile:
I believe the issue is that the launch file dynamically change the ndt_enabled based on the runtime argument 'pose_source'.
For example, ros2 launch autoware_launch autoware_launch.xml pose_source:=ndt will result in ndt_enabled=true, ros2 launch ... pose_source:=eagleye will result in ndt_enabled=false.
Are you suggesting placing distinct config files for each condition in pose_initializer/config/*.param.yaml?

Are you suggesting placing distinct config files for each condition in pose_initializer/config/*.param.yaml?

Now that you mention it, it sounds like an excellent idea! It would provide a tidier code in pose_twist_estimator.launch.xml, and it would simplify the interface between the two launch files with only the path to the config file to be used. And it matches the design described in https://autowarefoundation.github.io/autoware-documentation/main/contributing/coding-guidelines/ros-nodes/parameters/#parameter-file under "Launch parameter file". Yes, that's probably the best way to go.
However, I was suggesting a more modest change: keeping the <arg name="..."/> interface as it currently exists for all the parameters, but still adding the missing parameters to the config file as part of this PR. It shouldn't affect any packages that include the launch file from this package but satisfy the new schema linting. What I suggested above with config_file didn't make much sense on its own.

I see. The approach I suggested, involving multiple file placements, is a big changes.
I think it would be better to keep it a modest change that leaves <arg name="..." /> as ambroise-arm says.
As for me, I believe the current commit, in which all parameters independent on runtime arguments are included in param.yaml and passes the json-schema-check, is approvable.
@PhoebeWu21 Are you ok with the current style?
If OK, the code owner will review and approve.

@KYabuuchi Ok. Thank you.

@PhoebeWu21  Oh? I apologize. I was approvable in the last state.

As for me, I believe the current commit, in which all parameters independent of runtime arguments are included in param.yaml and passes the json-schema-check, is approvable.

What I mean here is to include only parameters independent of runtime arguments in param.yaml, excluding dependent parameters (such as ndt_enabled) from both param.yaml and json.schema.

@KYabuuchi Ahh got it. Sorry for the misunderstanding.

So if you agree with me, you did not have to commit https://github.com/autowarefoundation/autoware.universe/commit/095de6b02a9de6ded9d5612cacb3e797637c729c.

I disagree. The point of https://github.com/orgs/autowarefoundation/discussions/3371 that this PR implements is to have a 1 to 1 match between the parameters used in the C++ node and the schema/parameter files. I don't see the issue with having this commit in the PR. And having the PR without it doesn't fulfill the goal of the configuration dojo.
cc @kaspermeck-arm

@PhoebeWu21 @KYabuuchi @ambroise-arm
Autoware allows parameters to be split into multiple parameter files and launch files. Therefore, there is no guarantee that the parameter file and schema file will match exactly. (To be more precise, schema matches the temporary merged parameter file that the ROS launch system gives to the node.)
It has been pointed out that due to file splitting, schema and parameter file validation cannot be done one-on-one.

https://github.com/autowarefoundation/autoware-documentation/pull/367#issuecomment-1567811139

Apply parameters to my_node by two parameter files (e.g. common part and others)

Therefore, possible solutions are as follows (some are temporary solutions)

Define only the schema file and do not validate the parameter file
Split the schema file into expected division units of parameter file
Create a dummy parameter file that is not actually used but for verification (because it is unclear which parameter in the launch file or the parameter file will be used)
Create a mechanism to validate the final parameter file given to the node by the ROS launch system

do you intend to put both <param from="$(var config_file)"> and <param name="ndt_enabled"> in the launch file?

@KYabuuchi Yes, in the pose_initializer.launch.xml launch file. But it is already like this, so it is more about keeping it this way.

And since <param name="ndt_enabled"> takes priority (I'm not sure), we can pass the parameters corresponding to the runtime arguments as before?

@KYabuuchi Exactly. I also assume it takes priority.

Create a dummy parameter file that is not actually used but for validation (because it is unclear which parameter in the launch file or the parameter file will be used)

@isamu-takagi I don't think the issue your are linking to is a problem here. What will happen is that we will have a schema file in this package that has all its fields as "required", and a config file that list all the fields. So it should be validated correctly. The launch file of this package then uses this config file as a default, while also requiring some of its arguments to be passed directly. So in practice the ndt_enabled, gnss_enabled, ekf_enabled, yabloc_enabled and stop_check_enabled arguments will always be overridden. At least until changes as described in https://github.com/autowarefoundation/autoware.universe/pull/5773#issuecomment-1841059273 are done.

For this package, I think the approach mentioned by ambroise-arm is fine.
However, as isamu-takagi  says, some packages have split multiple parameter files, so it will be an issue that will have to be tackled eventually.

So in practice the ndt_enabled, gnss_enabled, ekf_enabled, yabloc_enabled and stop_check_enabled arguments will always be overridden.

@KYabuuchi @ambroise-arm
Is this behavior guaranteed by the launch_ros specification?

i am not sure😞

@KYabuuchi
I found a description that the last parameter has priority. So be careful about the order of parameters in the launch file. Also, note that namespace also affects priority.
https://github.com/ros2/launch_ros/blob/humble/launch_ros/launch_ros/actions/node.py#L175-L182

@isamu-takagi Thank you for finding the description.  Very useful information!

I realized that the override rules are complex, and the current approach might actually introduce more bugs.
(I have created tests to verify the parameter override rules, so please take a look. https://github.com/KYabuuchi/ros2_launch_learn/tree/feat/minimum_case?tab=readme-ov-file#the-result)
I also posted this issue in the github-actions thread.  I don't think we should merge PRs with parameter overrides at this time.

@PhoebeWu21 Sorry to keep you waiting for so long.
As a method to pass parameters from the launch file, the chosen approach is to use substitution within YAML.
reference , example
If it's not too inconvenient, would you mind revising this PR to incorporate that method? If it is troublesome, I am willing to work on it and create a new PR.
Thank you

@KYabuuchi Sure, I can deal with the modifying. But I am a bit confused about the revising of the pose_initializer.launch.xml file. Should I revise it to the format like pose_twist_estimator.launch.xml?

@PhoebeWu21  Thanks for your cooperation. What I want you to do is the following:

Remove all <param name=... /> from pose_initializer.launch.xml.
Replace <param from="$(var config_file)" allow_substs="true"/> in pose_initializer.launch.xml. ref
Add ndt_enabled: $(var ndt_enabled) etc. in pose_initializer.param.yaml. ref
Add ndt_enabled etc. to pose_initializer.schema.json.
Create a PR to change param.yaml in autoware_launch, too. ref

You do not need to refer to pose_twist_estimator.launch.xml to make this change.


Sample drill is not dropping in survival mode. minecraft1.20.1 and fabric0.16.4 and createoreexcavation-fabric-1.20-1.5.2

Sample drill is not dropping in survival mode.
Create wrench doesn't work to Sample drill. And diamond pickaxe can break sample drill, but drill is not drop.
Is this the correct behavior?

Thank you very much.
This problem solved.
I am very grateful for your quick response.


Echo Is Not Defined: socket not working, Echo not connecting

Your environment:
Ubuntu 19.04
Description:
socket.io is not loading, console error reported of Echo is not defined
Steps To Reproduce:

Clone repo.
Follow all instructions as listed here: https://github.com/iluminar/goodwork/wiki/Installation#setup-usual-way-if-youre-not-using-docker
Login

@dougblackjr which laravel-echo-server.json file are you using to run echo-server? If you're running dev version then start echo server with laravel-echo-server.dev.json file, like below
laravel-echo-server start --dir=laravel-echo-server.dev.json

@Hasnayeen Using the production one. Here is my current config (with some variables changed):
{
  "authHost": "https://url-of-site",
  "authEndpoint": "/broadcasting/auth",
  "clients": [
    {
      "appId": "bec9d450fbf2af78",
      "key": "adeb2fe782d9d3dcd955ac5a88aff184"
    }
  ],
  "database": "redis",
  "databaseConfig": {
    "redis": {},
    "sqlite": {
      "databasePath": "/database/laravel-echo-server.sqlite"
    }
  },
  "devMode": false,
  "host": null,
  "port": "6001",
  "protocol": "https",
  "socketio": {},
  "secureOptions": 67108864,
  "sslCertPath": "/etc/nginx/ssl/------.crt",
  "sslKeyPath": "/etc/nginx/ssl/------.key",
  "sslCertChainPath": "",
  "sslPassphrase": "",
  "subscribers": {
    "http": true,
    "redis": true
  },
  "apiOriginAllow": {
    "allowCors": false,
    "allowOrigin": "",
    "allowMethods": "",
    "allowHeaders": ""
  }
}

My only question is whether the app ID and key need to be changed, those both came over what was in the repo.

ID and key doesn't need to be changed, after starting echo server do you see any error? what's the last few output lines?

No error, just says that server is started.
L A R A V E L  E C H O  S E R V E R

version 1.6.0

Starting server...

✔  Running at localhost on port 6001
✔  Listening for http events...
✔  Listening for redis events...

Server ready!

any error on console? also check the network tab for socket.js call, whats the response of that?

socket.js call times out without any response.

Error in console is Echo is not defined.

check the url for socket.js call?

Correct, that file is not in the repo. Did I miss a step in the installation process?

maybe reinstall laravel-echo-server , socket.io is a dependency of laravel-echo-server and will be available from echo server not from repo public directory

I just went ahead and moved to pusher for now. Thank you!

sorry could not help you further, but hopefully you figured it out


RFE: constructor from primitive model

Is your feature request related to a problem? Please describe.
Constructing a request/response object is more arduous than it needs to be, and can't be done from ORM models.
Describe the solution you'd like
class Item(BaseModel):
    name: str
    quantity: int
    price: float

ItemRequest, ItemResponse = JsonApiModel('item', Item)

item = Item(name="my item", quantity=4, price=1.2)
item_req = ItemRequest(item)

This would also make it super easy to construct request/response objects from ORM models.
It wouldn't necessarily have to be the constructor, it could be a different class method e.g. item_req = ItemRequest.from_primitive(item)
Describe alternatives you've considered
Right now, I mangle by hand.
Additional context
Add any other context or screenshots about the feature request here.

Hi @jonathanunderwood thanks for the submission.
I can certainly attempt to implement something like what you suggested, and have been thinking about it as well. Just not sure yet how much magic makes sense to add here. For example, a somewhat logical next step for a feature like this is to add some handling or discovery of relationships, includes, and links. Most JSON api implementations try to do this in some way or another.
For now, this library is focused manly on structural typing and validation of JSON api documents, but I could see it providing more data transformation functionality.
If you're interested, this is the sort of approach I've been taking on this:
from pydantic import BaseModel
from pydantic_jsonapi import JsonApiModel
from my_data_model import Item

class ItemAttributes(BaseModel):
    name: str
    quantity: int
    price: float

    class Config:
        orm_mode = True

ItemRequest, ItemResponse = JsonApiModel('item', Item)

def marshal_item(item: Item) -> dict:
    return {
        'id': item.id,
        'type': 'item',
        'attributes': ItemAttributes.from_orm(item).dict()
        'relationships': {
            'sold_at': {
                'data': {'type': 'store', 'id': item.store.id}
            }
        }
    }

# some http endpoint
@app.get('/item')
def get_item():
    item = db.query(Item).one()
    return ItemResponse(data=marshal_item(item)).json()

There's some amount of duplication with this approach, but it's very flexible in how you want to use json api and there's no magic. Any structure you produce with a function like marshal_item here ends up getting validated against the JSON api spec

Yes, that's essenetially the approach I have been taking. In your example, presumably your ItemAttributes would also have an id field, which is Optional ?

@jonathanunderwood id is a bit tricky since it's not considered an attribute in JSONAPI.

Incidentally, the approach you outline is for marshalling from an ORM model directly. Which is a partial solution. But I find myself often wanting to create a JSONAPI response/request from the corresponding attributes pydantic object.

@jonathanunderwood please take a look at #11 I've added a new method resource_object, which comes pretty close to your request here.
With that change, my above example could be changed to look something like this:
ItemRequest, ItemResponse = JsonApiModel('item', ItemAttributes)

# some http endpoint
@app.get('/item')
def get_item():
    item = db.query(Item).one()
    return ItemResponse(
        data=ItemResponse.resource_object(
            id=item.id,
            attributes=item
        )
    ).json()

or for lists:
@app.get('/items')
def get_items():
    items = db.query(Item).all()
    return ItemResponse(
        data=[
            ItemResponse.resource_object(
                id=item.id,
                attributes=item
            ) for item in items
        ]
    ).json()

released #11 in 0.9.0

This looks very handy, thanks for adding it. I'll give it a try next week. Thanks again.

We've been using this locally for a few days, and it works very well! Many thanks for adding it.


affected/package:

What version of Go are you using (go version)?

go version go1.19.3 darwin/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
GO111MODULE=""
GOARCH="amd64"
GOBIN="/Users/houruizhe/go/bin"
GOCACHE="/Users/houruizhe/Library/Caches/go-build"
GOENV="/Users/houruizhe/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/houruizhe/go/pkg/mod"
GONOPROXY="*.byted.org,*.everphoto.cn,git.smartisan.com"
GONOSUMDB="*.byted.org,*.everphoto.cn,git.smartisan.com"
GOOS="darwin"
GOPATH="/Users/houruizhe/go"
GOPRIVATE="*.byted.org,*.everphoto.cn,git.smartisan.com"
GOPROXY="https://go-mod-proxy.byted.org|https://goproxy.cn|https://proxy.golang.org|direct"
GOROOT="/usr/local/Cellar/go/1.19.3/libexec"
GOSUMDB="sum.golang.google.cn"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.19.3/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.19.3"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/t3/3ck0t1213rnc8sdjm5sv6hn00000gp/T/go-build2127940362=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

What did you expect to see?
The last sort does not change the sequence.
What did you see instead?
It reverse the slice.

Get. I read the document and see this. I guess when both Less(i, j) and Less(j, i) are true, the elements at index i and j are not considered equal.


Graceful handling of Create PR when there are changes but no commits

Issue Type: Feature Request
Testing https://github.com/Microsoft/vscode/issues/64262.

create a new branch
change a file but don't commit
Run Create PR from the command palette
-> Warning

Creating pull requests for 'kieferrm/show-busy-indicator' failed: Validation Failed: No commits between remote-hackathon and kieferrm/show-busy-indicator

Just as with committing without staged changes we should ask people whether the current changes should be included in the PR. Similarly, we should push for the user if there are local commits.
Extension version: 0.337.0
VS Code version: Code - Insiders 1.30.0-insider (fa87e67ebfd6b8014ba697ddbc6c2d6c0e2cb970, 2018-12-04T09:26:33.257Z)
OS version: Darwin x64 18.0.0

Closing as a duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/2100, this should already be fixed


Package request: linux-cachyos

Project description
Kernel based on different schedulers and some other performance improvements
Metadata

homepage URL: https://github.com/CachyOS/linux-cachyos
source URL: https://github.com/CachyOS/linux-cachyos
license: gnu
platforms: unix, linux

Add a :+1: reaction to issues you find important.

Duplicate


[Fix] support XLM in integration tests

What
Support xlm in integration tests
Why
It's a good practice to support it, and it was needed to test e2e on futurenet
Known limitations
[TODO or N/A]
Checklist
PR Structure

[x] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR title and description are clear enough for anyone to review it.
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[x] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr470.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr470.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr470.previews.kube001.services.stellar-ops.com

I'll hold off on this PR while we focus on the 3.0 release. I'll mark it as DRAFT for now.

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr470.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr470.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr470.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr470.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr470.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr470.previews.kube001.services.stellar-ops.com


[Task] Animation sprite created for player

Description
Task: Create sprite animation for weapon attack on the player
Feature: Combat Items #105
The goal of this task is to create a sprite animation for the weapon attacks. This would place more visual aesthetics within the game and allow for deeper interaction between the character and the individual playing the game. Two sprite animations will be created within this sprint both of which will be using either a PVC pipe or a level 3 dual-wielded dagger.  A player sprite must be given beforehand in order to complete this task and therefore will become part of this ticket's dependency. Animations should be sketched out before drawing and should adhere to aspects of previous designs created. Upon completion, the animation is to be exported as multiple .png files ready to be implemented into the game by the player class. Details on the player can be added after the weapon animation has been completed.
Example
Below are some inspirations and directions on potential animation options:

Milestones
List of steps that need to be completed for this task.

[x] Static player drawing to be given to Weapon's team ready for animation (Sept. 5)
[x] Sketches completed  (Sept. 7)
[x] Graphical representation drawn & passed back to player team (Sept. 10)

Dependencies
This ticket heavily relies upon the player team to complete their player image in order for the weapons to be visually integrated and for an animation to be completed.

[x] #104

Documentation

Weapon Animation

Member

Caleb Ang (PurrplePandaa) (Caleb Ang)
Nisha Vashist (NishaVashist0) (Nisha Vashist)
Noland Luo (NolandLuo) (Noland Luo)

Hey @NolandLuo @ew-b, I've done some work on the player attack animation. Was wondering what you guys thought of this.

Hi! @PurrplePandaa looks good, especially for level 2 weapons, but I think it'll be easiest to make essentially masks instead of animating the sprite each time, especially with the continuing iteration of what the character looks like and how it moves. I do think the sprite you have made is too buff for what our team has envisioned for the player character. Cool to see it moving though!

Thanks for the input, I'll go ahead and update it accordingly. I do agree that the animation movement of the hand would look nicer this way but probably more implementable to have it as an overlay. Stay tuned!

looks very cool, I like this weapon. Also, since we're setting up a plumber who hates his job, being too strong might not be a good fit. But a little muscle is ok (have added some muscle to the sprite after user testing)

Alright guys, I've created another sprite animation for the player. This time, I've overlayed it ontop of the player so that we no longer have to depend as tightly on each other. The only downside would be that the arms kinda don't swing? But I wreckon for the purposes of this sprint it doesn't look awefully bad. Lmk if you have any concerns, Ta!

Hi! Looks really good, good work!  Here they are! Feel free to let us know if have any major changes you want to make to these 😄

Weapon Description
Animation

Level 3 Dagger

Level 2 Dagger

That looks pretty good. Arm swing we can talk about in the next sprint. (In addition, the latest Player Sprite has been uploaded)


Add "spinel_platform_config.h" to define spinel files platform related settings

spinel.h, spinel.c are intended to be platform independent and can
be used in different software modules (e.g., in wpantund).  This
commit adds a new header file "spinel_platform_config.h" which defines
the platform related configuration settings used by spinel.
In particular we define SPINEL_PLATFORM_IS_OPENTHREAD which
indicates whether the spinel files are being complied/built as part of
OpenThread NCP build. Setting SPINEL_PLATFORM_IS_OPENTHREAD as 1 (or
non-zero) ensures that the correct include files are used, e.g., the
warped header files such as "utils/wrap_string.h" instead of
<string.h>, or the  <openthread-config.h> will be included.

I don't know if I'm a fan of this spinel_platform_config.h... I think it might be over-engineering the problem. The traditional autotools way of dealing with this is to have this at the top of spinel.c:
#if HAVE_CONFIG_H
#include "config.h"
#endif

No openthread-config.h (that would be HAVE_OPENTHREAD_CONFIG_H), just config.h.

Talked with @darconeous  offline, decided to change the logic to follow a model like HAVE_CONFIG to hanlde the special case of wraped header file (for stdbool and stdint). I will close this PR.


Use CUDA 11.1

In order to work well with emit; we need CUDA 11.1 or greater

As of #133 we're using 11.6 and this should now work without issue.


build.gradle: Update to JLink plugin 3.0.1

This adds support for building with JDK 21 (when combined with https://github.com/sparrowwallet/drongo/pull/19 and https://github.com/sparrowwallet/drongo/pull/21)
I've confirmed this on macOS/aarch64 using Gradle 8.5 and Java (Temurin) 21.0.1 -- both installed with SDKMAN. Both gradle run and gradle jpackage seem to work correctly.

Thanks


Keys created with ES <IP_ADDRESS> do not have "sign" usage bit enabled

As reported by "pkcs15-tool --list-keys" on Linux, the keys created by ES do not have the "sign" usage flag set.  For example:
# pkcs15-tool --list-keys
Using reader with a card: Yubico Yubikey 4 OTP+U2F+CCID 00 00
Private RSA Key [PIV AUTH key]
        Object Flags   : [0x1], private
        Usage          : [0x22], decrypt, unwrap

However, keys created with the YubiKey PIV Manager do:
$ pkcs15-tool --list-keys
Using reader with a card: Yubico Yubikey 4 OTP+U2F+CCID 00 00
Private RSA Key [PIV AUTH key]
        Object Flags   : [0x1], private
        Usage          : [0x26], decrypt, sign, unwrap

Most importantly, the "sign" flag is needed for PKINIT to work on Linux as discovered here: https://pagure.io/SSSD/sssd/issue/3616

We can't reproduce this misbehavior with ES <IP_ADDRESS> and Linux and enroll on behalf of other users
pkinit is working  and the sign bit is set.
Using reader with a card: Yubico Yubikey 4 OTP+CCID 00 00
Private RSA Key [PIV AUTH key]
Object Flags   : [0x1], private
Usage          : [0x26], decrypt, sign, unwrap
Access Flags   : [0x1D], sensitive, alwaysSensitive, neverExtract, local
Public RSA Key [PIV AUTH pubkey]
Object Flags   : [0x0]
Usage          : [0xD1], encrypt, wrap, verify, verifyRecover

ES's responsibility is only to get a certificate from the Active Directory Certificate Services (ADCS) and put it on the Yubikey - it does not set properties on the certificate itself. The certificate content is controlled using templates on the ADCS server, so make sure it contains the correct setup.


Add support for parquet_prefetch_rowgroups flag in TpchBenchmark

Resolves https://github.com/facebookincubator/velox/issues/8693

@jkhaliqi do you have any other changes for this PR?

@jkhaliqi do you have any other changes for this PR?

@majetideepak No other changes for this PR

@jkhaliqi can you rebase with main? That should fix the Linux Build test.
You also have to run make format-fix to fix the Code Format failure.

@jkhaliqi can you rebase with main? That should fix the Linux Build test. You also have to run make format-fix to fix the Code Format failure.

@majetideepak  Rebased with main and also ran make format-fix


Handle rotate API key for non existing user

What does this PR do?
Handle rotate API key for non existing user

What's changed? Why were these changes made?
Before sending request to rotate key we verify that the user actually exists, similarly to what happens for rotating API keys for hosts.
How should the reviewer approach this PR, especially if manual tests are required?
No, there is an integration test
Are there relevant screenshots you can add to the PR description?
User input:

Output:

What ticket does this PR close?
Resolves #979
Checklists
Change log

[ ] The CHANGELOG has been updated, or
[ ] This PR does not include user-facing changes and doesn't require a CHANGELOG update

Test coverage

[x] This PR includes new unit and integration tests to go with the code changes, or
[ ] The changes in this PR do not require tests

Documentation

[ ] Docs (e.g. READMEs) were updated in this PR, and/or there is a follow-on issue to update docs, or
[ ] This PR does not require updating any documentation

Great work @egvili !
Can you please also add a changelog entry? This is a customer-facing change. Something like this should be good:
The Conjur CLI now raises a proper error when trying to rotate a non-existing user's API key

Great work @egvili ! I left some small comments.
Can you please also add a changelog entry? This is a customer-facing change. Something like this should be good:
The Conjur CLI now raises a proper error when trying to rotate a non-existing user's API key

btw @egvili i see that the CHANGELOG file is not in the format that we use. If i would be doing this effort, i would also align it and add a Jenkins stage that verifies the pattern (as we do in other projects) but as this is your first PR feel free to just be as good as the current state without fixing it.

Great work @egvili ! I left some small comments.
Can you please also add a changelog entry? This is a customer-facing change. Something like this should be good:
The Conjur CLI now raises a proper error when trying to rotate a non-existing user's API key

btw @egvili i see that the CHANGELOG file is not in the format that we use. If i would be doing this effort, i would also align it and add a Jenkins stage that verifies the pattern (as we do in other projects) but as this is your first PR feel free to just be as good as the current state without fixing it.

@orenbm Can you elaborate? This repo has inside the Jenkins file a step of verifying the CHANGELOG with the same script as in Conjur OSS (Here: under ./bin/parse_changelog.sh, Conjur: ./ci/parse_changelog.sh). Plus, I didn't find any actual format difference between cli's CHANGELOG and Conjur's. Do you have examples? Do you mean the english time usage? Present simple in Conjur ?

Great work @egvili ! I left some small comments.
Can you please also add a changelog entry? This is a customer-facing change. Something like this should be good:
The Conjur CLI now raises a proper error when trying to rotate a non-existing user's API key

btw @egvili i see that the CHANGELOG file is not in the format that we use. If i would be doing this effort, i would also align it and add a Jenkins stage that verifies the pattern (as we do in other projects) but as this is your first PR feel free to just be as good as the current state without fixing it.

@orenbm Can you elaborate? This repo has inside the Jenkins file a step of verifying the CHANGELOG with the same script as in Conjur OSS (Here: under ./bin/parse_changelog.sh, Conjur: ./ci/parse_changelog.sh). Plus, I didn't find any actual format difference between cli's CHANGELOG and Conjur's. Do you have examples? Do you mean the english time usage? Present simple in Conjur ?

oh sorry, my local code wasn't updated. I pulled the changes and the changelog is fixed.
please add the GH issue link to the changelog entry then.
thanks!

Drive-by note: whoever ends up merging this, please use the squash and merge button since the git history isn't clean.

@egvili  - I'm not sure where I should review.
Which is the user-facing text?

@shulifink , the user facing text is: User ‘’ not found
This message is prompted when user provides a  that does not exist to the command:
conjur user rotate_api_key --user <username>
From the email correspondence you seem to approve that. If you have any reservation please let me know.


metadata version missmatch in uv 0.5.5

Dear all,
I got this error when building and uploading my wheel with 0.5.5 to pypi.org.:
Upload failed with status code 400 Bad Request. Server says: 400 license-file introduced in metadata version 2.4, not 2.1. See https://packaging.python.org/specifications/core-metadata for more information.

But it does work for me with 0.5.4.
Accoridng to the release notes, with 0.5.5 uv started to use license-file, however I did not see a mention of moving the metadata version...
Any ideas?
Thanks in advance,
Franz

This is probably #9442: It's correct that you can only use license-file with metadata of at least version 2.4, but we were missing that field in the upload payload previously so pypi's validation didn't work. What build backend are you using?

I got the same error with uv build used in building my project.
Here is the repo: https://github.com/FHU-yezi/sshared
The failed publish GitHub Action flow: https://github.com/FHU-yezi/sshared/actions/runs/12078435589/job/33682841905
It is a pure Python package and I got this error after updated to the latest uv version.

This is a bug in setuptools: https://github.com/pypa/setuptools/issues/4759
uv unfortunately can't do anything about this.

Ok thanks. Any ideas how to have dynamic versioning without setuptools?
konsti @.***> schrieb am Fr., 29. Nov. 2024, 11:42:

This is a bug in setuptools: pypa/setuptools#4759
https://github.com/pypa/setuptools/issues/4759
uv unfortunately can't do anything about this.
—
Reply to this email directly, view it on GitHub
https://github.com/astral-sh/uv/issues/9513#issuecomment-2507543694, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXSBILVY5IYIXHUHCKUNST2DBAH5AVCNFSM6AAAAABSVWJU6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBXGU2DGNRZGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

@franzhaas versioningit works with setuptools and also hatchling.

I did not try to upload, but when building with hatchling, I ended up using metadata 2.3... for both uv 0.5.4 and 0.5.5...
this might be related to this one.:
https://github.com/pypa/hatch/issues/1819

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

fixed my issue. as @kbrgl suggested

If you still want to use setuptools as build backend, a simple workaround is to explicitly provide an empty value for licence-files in your pyrpoject.toml:
[tool.setuptools]
license-files = []

Okay, here's what I don't understand...
Maybe this is a setuptools bug, but there's something funky going on with uv.
I removed all mentions of license from my pyproject.toml and rm -rf build dist; uv build; uv publish gave me the same error. I then did python -m build . ; python -m twine upload dist/* and everything works just fine. What gives?
Does uv build backend do any caching of metadata somewhere?

Okay, here's what I don't understand...
Maybe this is a setuptools bug, but there's something funky going on with uv.
I removed all mentions of license from my pyproject.toml and rm -rf build dist; uv build; uv publish gave me the same error. I then did rm -rf build dist; python -m build . ; python -m twine upload dist/* and everything works just fine. What gives?
Does uv build do any caching of metadata somewhere?

Use hatchling instead of setuptools should solve this problem, you can find guide about this in uv documentation.

Thanks, I understand that :-) Just based on the sequence of commands I ran, it appears there's also some issue in uv (maybe just a caching issue?) in addition to the one in setuptools

@hauntsaninja:
PEP 639 adds two new fields to the wheel metadata License-Expression and License-File. These fields are added in the new metadata version 2.4.
When uploading a wheel, the uploader reads the METADATA file from the wheel and transforms it to formdata. PyPI has recently started validating the two new metadata fields from PEP 639 in the formdata, thought PyPI does not validate the METADATA. Twine hasn't implemented that PEP yet (https://github.com/pypa/twine/pull/1180), so it does not set the new license fields in the formdata, and PyPI does not catch the invalid metadata (declaring metadata version 2.1 while using version 2.4 fields).

When uploading a wheel, the uploader reads the METADATA file from the wheel and transforms it to formdata. PyPI has recently started validating the two new metadata fields from PEP 639 in the formdata, thought PyPI does not validate the METADATA. Twine hasn't implemented that PEP yet (pypa/twine#1180), so it does not set the new license fields in the formdata, and PyPI does not catch the invalid metadata (declaring metadata version 2.1 while using version 2.4 fields).

The twine PR was just merged. It also added a carveout for setuptools to exclude License-File from the metadata if the version is <2.4 as to not break all projects which use setuptools. Maybe this is something which could be added to uv as well? https://github.com/pypa/twine/blob/main/twine/package.py#L225-L234
The setuptools behavior has been in place for so long at this point that it's probably not worth changing until PEP 639 is fully implemented. I've PRs open for that but those depend on some other work which need to happen first and will likely still need some time.

If you still want to use setuptools as build backend, a simple workaround is to explicitly provide an empty value for licence-files in your pyproject.toml:
[tool.setuptools]
license-files = []

Yes, this is a workaround. However, I'd advise against it. It will not only remove the License-File metadata but also the license files from the distribution. You can include them manually via MANIFEST.in but they will still be excluded from the wheel (unless placed inside the project package itself).
The ideal case would really be a workaround added to uv just like in twine.


random white pixels in superres image

Hi,
I have successfully trained a model and the output images look good, with one exception.  For some reason I get a lot of stray white pixels in dark areas of the image. I have attached an example.  Some images only have a few of these stray pixels, while others (like this one) have many.  Any idea what might be causing this?
Thanks!

Hi, how did you get your HR image? I met this problem when I use imresize function from python version opencv. You can check the value in these pixels, are they NAN?

Thanks for your response.  I fixed the issue...it was due to negative values in the output from the network. I replaced them with zero before converting back to RGB and it fixed the problem.
Thanks!


Test Conversion Operators

We need to test all of the conversion operators. What are the cases for them?

The builtin integral types and the BigInteger conversion don't have any extra-special cases.
The conversions from Int128, UInt128, decimal, float, and double all have special cases. What are they?

Pull Request https://github.com/jacob-bauer/PerfectDecimal/pull/49 solves this


feat: add snippets

Closes #59

Another thing is you need to preserve the documentation in the completion item in the snippet

Should I add a new parameter to the Snippet.get/2 function or use the second one as docs?
Or we don't want to Snippet.get/2 to change?

I'll try and play with this soon, currently wrapping up some work on the editor extensions.

made a couple changes, otherwise great!


Android: Cannot use measure function inside of Marker

I want to be able to tell where on the screen a marker is placed so that I can perform an animation at that position(creating a new image on top of the marker because animating marker size won't work on Android).
To solve this I tried to use the measure function on the child of the marker
componentDidMount() {
    setTimeout(this.measureStuff.bind(this));
}
measureStuff() {
    this.refs.markerview.measure((ox, oy, width, height) => {
        console.log("ox", ox, oy, width, height);
    });
}
...
<MapView.Marker>
    <View ref="markerview" collapsable={false} onLayout={() => {}}>
        <Image/>
    </View>
</MapView.Marker>

But everything logged in measureStuff() returns undefined. I tried this outside of the MapView and it worked, using this same technique.
So for some reason I cannot get the info of a View inside of the MapView(works on iOS). Does anyone have a clue how to solve this? The measure function is problematic on Android which is why I had to use tricks like collapsable={false} to make it work outside of the MapView.

Are sure there is measure exists in this.refs.markerview?
Btw, markers on Android are bitmaps and the they can't be animated.

@alexHlebnikov The reason I want to use measure is to get the position on screen of a marker so that I can create a new image there which animates on create/remove of the marker, because it cannot be done with Android markers due to them being bitmaps.
How do you mean? I assume all View's have access to the measure function?

You could be right about measure in markers, I honestly have no experience wtih it. But I thought on Android it could not work because of markers bitmap nature.

@alexHlebnikov comment is right. IMHO WONTFIX
Maybe change Marker view? Let me know if it's still actual.

it would be very useful to measure views inside marker within the map (get marker position relative to the screen) - with this data we can create/use markers/callouts outside the map and place them with absolute position over the map, this will bring a lot of cool stuff like animations and so on.

@carleryd , have you found a solution? Please, share, if yes =)

@vitto-moz Have you found any solution for this? Currently, I'm using .measure() on View inside Marker, and I'm getting good values for width and height, but for x/y positions on screen, I'm getting some random large values, like 38095240, 36363636 etc

Yes! now we have it! Thanks a lot for creators and maintainers - guys you are awesome! :)
For those who are interested, please check the updated doc for <MapView /> there is new method  called pointForCoordinate that cover the requirement I've mentioned above!


ssh: split the web SSH connection into two steps

In order to start a new SSH connection through web terminal, the user needs to send the credentials, device's UID, device's username and device's password, to /ws/ssh route as a POST request to receive a session's token. This token remains valid for 30 seconds.
With the token, the user sends it as a query parameter to the same route, but through the GET method. Beyond the token, this route requires the number of columns and of rows from the web terminal. If any of those parameters are empty or invalid, the connection will fail, reporting the problem to the user.
Subsequently, if the token is still alive and the data is valid, the SSH connection should behave like usual, connecting to the agent on the device indicated.

The most important thing about this improvement is that now the auth credentials will not be sent by a GET request that were logged by NGINX, now the credentials will be sent by a POST request which could be encrypted when using HTTPS


onLoadMore currentPage != currentPage

When working with EndlessScrollListener, at the initial onLoadMore, I expect currentPage == 1, however I'm observing currentPage == 20. It seems to contain a value equal to itemCount or lastPosition. Perhaps, I'm doing something wrong; any ideas?

@es0329, currentPage is a calculation of the following method:
/**
 * Provides the current endless page if the page size limit is set, if not set the returned
 * value is always 1.
 *
 * @return the current endless page
 */
public int getEndlessCurrentPage() {
	return Math.max(1, mEndlessPageSize > 0 ? getMainItemCount() / mEndlessPageSize : 0);
}


New FAR fork

Replaced the restricted assets with different ones so there are no licensing issues. Would like to get this on CKAN so everyone can use one version and not many different recompiles.
If I was providing backports, how would that work with CKAN? Would I need to create multiple releases one for each KSP version?
Edit: build fails because ModularFlightIntegrator is not found for KSP 1.5 but a version from KSP 1.4.5 works.

I'm a bit wary of replacing the existing entry; if Ferram does come back, he might receive problem reports from people having difficulties with CKAN version sequencing and have to skip other people's version numbers with his releases. He's already not the biggest fan of CKAN, so it would be nice to avoid antagonizing him in that way.
What would you say about creating a new entry called FerramAerospaceResearchContinued (or Redux or any of the other suffixes people use for continued mods)? That way we could keep it separate from the original.

Yeah, no problem. Besides changing the .netkan file name, what else would need to be changed?

Just the file name and the identifier property.

There are two key factors with backports:

Select a versioning scheme that "makes room" for the backports properly; for example, you might designate a 1.4.X series of your mod as KSP 1.4-compatible, and a 1.5.X series as KSP 1.5-compatible.
Upload one release at a time, and allow 3-5 hours in between uploads to give the CKAN bot time to index each one. The bot only checks the most recently uploaded release each time it runs.

Looks OK now, thanks for the submission. Merging...

Maybe the name should also be changed so that users can see it's a different version.

Oops, good point. Added "Continued", should be in the repo momentarily.