Unknown: Unhandled Journal event

Sure you guys know this.....but....
Since Update 5 I've been getting the following Making a witchspace jump (system to system).
SHOW ME

```JSON
02/07/3307 19:55:48 Unknown: Unhandled Journal event, Report to EDDiscovery team.
{"timestamp":"2021-07-02T19:55:48Z","event":"ShipLocker","Items":[{"Name":"californium","OwnerID":0,"Count":2},{"Name":"gmeds","Name_Localised":"G-Meds","OwnerID":0,"Count":2},{"Name":"healthmonitor","Name_Localised":"Health Monitor","OwnerID":0,"Count":4},{"Name":"insight","OwnerID":0,"Count":4},{"Name":"insightdatabank","Name_Localised":"Insight Data Bank","OwnerID":0,"Count":3},{"Name":"personalcomputer","Name_Localised":"Personal Computer","OwnerID":0,"Count":4},{"Name":"trueformfossil","Name_Localised":"True Form Fossil","OwnerID":0,"Count":1},{"Name":"compactlibrary","Name_Localised":"Compact Library","OwnerID":0,"Count":8},{"Name":"infinity","OwnerID":0,"Count":9},{"Name":"insightentertainmentsuite","Name_Localised":"Insight Entertainment Suite","OwnerID":0,"Count":5},{"Name":"nutritionalconcentrate","Name_Localised":"Nutritional Concentrate","OwnerID":0,"Count":2},{"Name":"personaldocuments","Name_Localised":"Personal Documents","OwnerID":0,"Count":1},{"Name":"universaltranslator","Name_Localised":"Universal Translator","OwnerID":0,"Count":3},{"Name":"degradedpowerregulator","Name_Localised":"Degraded Power Regulator","OwnerID":0,"Count":3}],"Components":[{"Name":"graphene","OwnerID":0,"Count":4},{"Name":"circuitboard","Name_Localised":"Circuit Board","OwnerID":0,"Count":2},{"Name":"circuitswitch","Name_Localised":"Circuit Switch","OwnerID":0,"Count":16},{"Name":"electricalfuse","Name_Localised":"Electrical Fuse","OwnerID":0,"Count":3},{"Name":"electricalwiring","Name_Localised":"Electrical Wiring","OwnerID":0,"Count":2},{"Name":"encryptedmemorychip","Name_Localised":"Encrypted Memory Chip","OwnerID":0,"Count":14},{"Name":"epoxyadhesive","Name_Localised":"Epoxy Adhesive","OwnerID":0,"Count":6},{"Name":"memorychip","Name_Localised":"Memory Chip","OwnerID":0,"Count":14},{"Name":"metalcoil","Name_Localised":"Metal Coil","OwnerID":0,"Count":7},{"Name":"microhydraulics","Name_Localised":"Micro Hydraulics","OwnerID":0,"Count":2},{"Name":"microsupercapacitor","Name_Localised":"Micro Supercapacitor","OwnerID":0,"Count":1},{"Name":"microthrusters","Name_Localised":"Micro Thrusters","OwnerID":0,"Count":1},{"Name":"microtransformer","Name_Localised":"Micro Transformer","OwnerID":0,"Count":3},{"Name":"opticalfibre","Name_Localised":"Optical Fibre","OwnerID":0,"Count":5},{"Name":"opticallens","Name_Localised":"Optical Lens","OwnerID":0,"Count":3},{"Name":"titaniumplating","Name_Localised":"Titanium Plating","OwnerID":0,"Count":1},{"Name":"tungstencarbide","Name_Localised":"Tungsten Carbide","OwnerID":0,"Count":1},{"Name":"electromagnet","OwnerID":0,"Count":2},{"Name":"microelectrode","OwnerID":0,"Count":6},{"Name":"ionbattery","Name_Localised":"Ion Battery","OwnerID":0,"Count":6}],"Consumables":[{"Name":"healthpack","Name_Localised":"Medkit","OwnerID":0,"Count":97},{"Name":"energycell","Name_Localised":"Energy Cell","OwnerID":0,"Count":95},{"Name":"amm_grenade_emp","Name_Localised":"Shield Disruptor","OwnerID":0,"Count":98},{"Name":"amm_grenade_frag","Name_Localised":"Frag Grenade","OwnerID":0,"Count":92},{"Name":"amm_grenade_shield","Name_Localised":"Shield Projector","OwnerID":0,"Count":98}],"Data":[{"Name":"atmosphericdata","Name_Localised":"Atmospheric Data","OwnerID":0,"Count":1},{"Name":"chemicalinventory","Name_Localised":"Chemical Inventory","OwnerID":0,"Count":1},{"Name":"maintenancelogs","Name_Localised":"Maintenance Logs","OwnerID":0,"Count":1},{"Name":"radioactivitydata","Name_Localised":"Radioactivity Data","OwnerID":0,"Count":1},{"Name":"residentialdirectory","Name_Localised":"Residential Directory","OwnerID":0,"Count":1},{"Name":"topographicalsurveys","Name_Localised":"Topographical Surveys","OwnerID":0,"Count":2}]}

</p>
</details>

Version 1.3.0

We know. It won't affect EDDLite normal operation. A new version will be along in the next week or so to display those events.
thanks

Hate leaving issues on things you know. It did say to let you know! :p


(minor) test name "test_4_body" -> test_helicity_angles

The test validates computation of the helicity angles in tree different topologies for 3b decay, L2pKpi.
The name in the code is confusing. I've renamed the pull request, #32 , but a bit too late

Done


Images in embedded notes do not render in Preview

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[x] Views.  Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[ ] Publish.  External Site Publish
[ ] Markdown.  Markdown features, such as syntax support and features

Describe the bug
images render in their own notes but do not render when embedded using ![[blah.blah]], in preview
To Reproduce
Steps to reproduce the behavior:

make a note
add an image
embed this note into another note
preview the second note

Screenshots

Desktop (please complete the following information)

OS: win
Versions (all that apply to bug):

Dendron Extension: 89
VS Code version: 1.66

Thanks for filing the issue @SR-- - can you let me know a little bit more about your repro?

Does this repro 100% for you right now for all images in a note reference?
Do the images in the original note render fine in preview? I.e., if you're just looking at the preview for blah.blah.md.
Is your blah.blah.md note particularly large, or are the image assets very large?

@jonathanyeung

100% for all images
The images render fine in the source note.
The images are largish because Dendron does not support JPEG paste and PNGs can be big. But nothing extraordinary and they do render find in the source notes.

Is there any asset that's safe to share so that I can try repro'ing on my side?

Issue appears to repro only on Windows - also affects Hover preiew.

Thanks for confirming this @jonathanyeung
Look forward to this getting fixed as it is a noticeable nuisance in the workflow because we use embedding a lot, it is such a great feature.

To add, I just noticed that if I open a note that is embedded into another note first and render it in the Preview, the Preview works OK for the host note that embeds that note too. Not sure if this helps with debugging.

@SR-- - if you upgrade to the latest build,(v91 or higher), do embeds / note-refs consistently work now, or are they still unreliable?
I believe hover is still broken on Windows.

No, does not work in 91

@jonathanyeung just confirming that this is still not working in v98.

Still not working in 106 but what I see now is that if I add a slash before the path the image loads correctly:
![test](/assets/images/test.gif) works in the source note and in the note in which it is referenced.
![test](assets/images/test.gif) only works in the source note.
Paste Image and VSCode dragging generate the note without the leading slash. Is this slash expected? What does it do to publishing? Should this be fixed an/or explained in the docs? Should I be adding these slashes to all images?
Thanks.

doesn't work on Linux too (even with the last version).


pywin32

Im using linux debian to install it cus i wanna be safe however every single tool requires pywin32 anyone got a fix

it's difficult to make pywin32 work with linux, you can use wine to run the win32 Api in Linux but i don't have any documentation for that. Try to run the repo on a Windows virtual machine


Maps are marshalled to Go representation instead of YAML when using parameter file

What happened:
An instance was marshalled with:
map[foo:bar baz:bam]
when installed using:
kubectl kudo install operator/ -P params-file.yaml
when the params file contains:
ENV:
  foo: "bar"
  bam: "baz"

What you expected to happen:
Instance map and array values are marshalled correctly as YAML.
How to reproduce it (as minimally and precisely as possible):
Install an operator with a map type using the -P flag
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version):
Kudo version (use kubectl kudo version): 1.11.1
Operator:
operatorVersion:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

This is a pretty serious bug that will actually be pretty hard to fix, and is further complicated by client-gen not allowing us to change Parameters from map[string]string to map[string]interface{}.

Awesome, this may now be fixable (whereas it wasn't before): https://github.com/kubernetes-sigs/kubebuilder/issues/528

Nevermind:
F0413 15:12:43.033417   44308 deepcopy.go:750] DeepCopy of "interface{}" is unsupported. Instead, use named interfaces with DeepCopy<named-interface> as one of the methods.

(╯°□°)╯︵ ┻━┻

@gerred I cannot reproduce this with kudo CLI built from master:
$ kind create cluster
$ export KUBECONFIG="$(kind get kubeconfig-path --name="kind")"
$ vi params-file.yaml # copy-paste your example
$ make cli-fast
$ PATH=`pwd`/bin:$PATH kubectl kudo init
$ PATH=`pwd`/bin:$PATH kubectl kudo install operators/repository/first-operator/operator/ -P params-file.yaml
operator.kudo.dev/v1beta1/first-operator created
operatorversion.kudo.dev/v1beta1/first-operator-0.2.0 created
instance.kudo.dev/v1beta1/first-operator-instance created
instance.kudo.dev/v1beta1/first-operator-instance ready
$ PATH=`pwd`/bin:$PATH kubectl get instance first-operator-instance -o yaml | grep -A 2 ENV
    ENV: |
      bam: baz
      foo: bar
$

We've seen something similar a while ago but it was fixed since: https://github.com/kudobuilder/kudo/issues/1437#issuecomment-603816117
Please do reopen if you manage to reproduce this.

Ah, it's indeed present in v0.11.1:
$ PATH=`pwd`/bin:$PATH kubectl delete instance first-operator-instance
instance.kudo.dev "first-operator-instance" deleted
$ git checkout v0.11.1
$ make cli-fast
$ PATH=`pwd`/bin:$PATH kubectl kudo install operators/repository/first-operator/operator/ -P params-file.yaml
operatorversion.kudo.dev/v1beta1/first-operator-0.2.0 already installed
instance.kudo.dev/v1beta1/first-operator-instance created
porridge@beczulka:~/Desktop/work/mesosphere/code/kudo$ PATH=`pwd`/bin:$PATH kubectl get instance first-operator-instance -o yaml | grep -A 2 ENV
    ENV: map[bam:baz foo:bar]
  planExecution: {}
$

I had thought that fix was already in v0.11.1 but it's only present in v0.12.0-rc1: https://github.com/kudobuilder/kudo/commit/9515d8654c1fae548f426e8e53466d2f7f7cf67b

ahh got it. thank you!


Zod compatibility

📝 Issue Description
The documentation states:

To use Zod in Astro, import the z utility from "astro:content". This is a re-export of the Zod library, and it supports all of the features of Zod. See Zod’s README for complete documentation on how Zod works and what features are available.

Zod's README gives the following as an example:
z.string().date({ message: "Invalid date string!" });

However, in Astro, z.string().date() is not valid - it has to be z.date(). Furthermore, it is not possible to use message. It looks like I can use invalid_type_error instead, e.g.:
date_tested: z.date({ invalid_type_error: "Invalid date format. Must be YYYY-MM-DD"}).optional(),

but when I try to build a site that might have date_tested defined as, say
date_tested: 1/8/2024

I get the error date_tested: Expected type "date", received "string" instead of my custom error.
📋 On which page(s) it occurs
https://docs.astro.build/en/guides/content-collections/
🤔 Expected Behavior
The documentation needs to make clear that Zod's README is not authoritative and make it clear, for example, that z.string().date() is not supported and to use z.date() instead. I do realise that the existing documentation gives an example of z.date() (which is how I figured it out) but it needs to be clearer because of the "supports all of the features of Zod" statement.
Furthermore, the issue about the custom error message needs to be cleared up in the documentation if it isn't supported.
👀 Current Behavior
See issue description.
🖥 Browser
Edge (Chromium version)
📄 Additional Information
No response

z.string().date() was added in Zod 3.23, which is not released yet.

z.string().date() was added in Zod 3.23, which is not released yet.

Thank you.
Will it support the message attribute that the Zod documentation references?

z.string().date() was added in Zod 3.23, which is not released yet.

OK - thank you.
In the absence of having Zod 3.23, is there a solution to getting a custom error message returned? I don't think users contributing to the data in my repo will find it easy to understand date_tested: Expected type "date", received "string" which is why I wanted to explain that the string needs to be in the specific format YYYY-MM-DD.

Unfortunately, I don't think it's possible to change that error message because it informs that the value found is of the wrong type.
I believe YYYY-MM-DD is the YAML date format, not a string. It's not that a "string" is in the wrong format, but rather that a date format is expected.
So, I will close this issue as I don't think there is anything actionable for docs here, and maybe you can use your contributing guide to provide/highlight the YAML date spec to your contributors to help them with the date format?


[YUNIKORN-1280] Shim side changes for YUNIKORN-1275

What is this PR for?
Shim side changes to support arbitrary resources in namespace annotation.
What type of PR is it?

[ ] - Improvement

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1280
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Can we split the tests for annotations into 3 tests:

test annotations based on the new setup (new function)
mixed new and deprecated (new function)
deprecated annotation (existing test)

Makes checks and regressions easier to track down.

Taken care


Support for L530 lightbulb

I was wondering if or when support for the RGB Lightbulb L530 will be added.
Thanks in advance and best regards

I've just found a pull request from a while ago that added it. Didn't see it until now but the library should now have support for setting the colour of the L530 bulbs.


Page "Configure the AMQP Sender Adapter" removes text "SAP Cloud Integration"

Issue description

When browsing the documentation on the page https://help.sap.com/docs/cloud-integration/sap-cloud-integration/configure-amqp-sender-adapter I noticed there was some text that didn't make sense (see screenshot)
The source markdown makes more sense: https://github.com/SAP-docs/btp-integration-suite/blob/main/docs/ci/Development/configure-the-amqp-sender-adapter-99ce674.md
It appears that something in the build process is replacing the text "SAP Cloud Integration" from the Note.

Feedback Type (Optional)
clarity
Page Title on SAP Help Portal (prefilled)
Configure the AMQP Sender Adapter
Page URL on SAP Help Portal (prefilled)
https://help.sap.com/docs/cloud-integration/sap-cloud-integration/configure-amqp-sender-adapter

Hi @davidcalloway, thank you for your feedback! We’ll look into it and come back to you if we have any questions.

Hi @davidcalloway, you are right. Ths is a problem with some metadata not applied correctly. I have corrected the issue and the change will be seen after our next documentation patch (very likely happening within the next 2 days).
Many thanks for your contribution!
The Text now reads in the following way:
Queues, topics, and messages can only be monitored by using tools provided by the message broker provider. Those monitors are not integrated into SAP Cloud Integration. Using SAP Cloud Integration, you can only monitor the integration flows using the AMQP adapter and the messages that are sent to or consumed from the message broker.

Many thanks for your contribution!


Machines aren't being dropped after broken

Issue description:
Well, the title says it. I try breaking any machine like metallargic infuser in my modpack, and it doesn't drop. The Configurator works but i want it work using my pickaxe.
Steps to reproduce:

idk

Version (make sure you are on the latest version before reporting):
Forge: <IP_ADDRESS>08
Mekanism: <IP_ADDRESS>9
Other relevant version:
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
[gist/pastebin/etc link here]

More info needed. Reproduce with just Mekanism & Forge

It turned out it was some kind of weird conflict with Extreme Energy Mod


Can't build on Windows due to

The following errors appead when I am trying to build ALL_BUILD in a solution, generated by cmake-gui:
Severity	Code	Description	Project	File	Line	Suppression State
Error	LNK1104	cannot open file 'tbb_debug.lib'	openvdb_shared	D:\dev\openvdb\.build\openvdb\LINK	1
Error	LNK1104	cannot open file '..\Debug\openvdb.lib'	vdb_print	D:\dev\openvdb\.build\openvdb\cmd\LINK	1

What can be done?

Hi @dims12, need some more information here. How have you set up your dependencies and exactly what CMake commands are you running.

@dims12 I'm closing this due to no activity - please re-open if this remains a problem


Compatibility with symfony/event-dispatcher ^4.3

Since 4.3, symfony/event-dispatcher changed the signature of the EventDispatcherInterface::dispatch() and removed the Event class. These deprecated changes were removed in 5.0. See the changelog.
Is there a plan to upgrade this package? I am the maintainer of sebdesign/laravel-state-machine which is based on this package and I would love to support the newer versions of Symfony and Laravel.

Hi,
Can you advise what would you update?
Thanks!

Hello,
It seems this has been fixed when support for Symfony 5 was added:
https://github.com/winzou/state-machine/commit/2448d9ab850387bc37c7e3540c8141b27029978c#diff-ce5bba7f8290e8a53edaa5f70682554ef452b143f2819b6682e1d4514fe026e8R94
Thanks!


How can I compile comeonin?

** (UndefinedFunctionError) function Comeonin.Bcrypt.hashpwsalt/1 is undefined (module Comeonin.Bcrypt is not available)
I tried to use the solution here: https://github.com/riverrun/comeonin/issues/102

Sorry, I forgot to add comeonin in applications (mix.exs)


distutils is removed in Python 3.12

distutils is deprecated with removal planned for Python 3.12. See the What’s New entry for more information.
Our only current use of Python distutils is at:
https://github.com/nodejs/node-gyp/blob/33391db3a0008eff8408890da6ab232f2f90fcab/gyp/pylib/gyp/input.py#L19
https://github.com/nodejs/node-gyp/blob/33391db3a0008eff8408890da6ab232f2f90fcab/gyp/pylib/gyp/input.py#L1186
As discussed in https://stackoverflow.com/questions/11887762, we should replace distutils.version.StrictVersion with packaging.version.parse.

@rzhao271 or @dhruvmanila -- Any interest in fixing this one?

I'm interested, though it'll have to be on my own time.

#2888 Needs help to pass test…

This is becoming more urgent now that Python 3.12 is a release candidate.

https://www.python.org/download/pre-releases
#2862 demonstrates the problem
#2888 is not yet a solution

this is breaking for me

Py3.12 is still pre-release.  Please try to copy the pylib/gyp/input.py changes from nodejs#201 and let us know if that unblocks you.

The upstream fix still hasn't been merged https://github.com/nodejs/gyp-next/pull/197

This is also broken for me. Simply create an electron forge app and then attempt to use like:
require('deasync').sleep(1000);
console.log('Hello world');

I'm greeted with:
File node_modules\node-gyp\gyp\pylib\gyp\input.py", line 19, in <module>
  from distutils.version import StrictVersion
  ModuleNotFoundError: No module named 'distutils'
  Error: `gyp` failed with exit code: 1

An unhandled rejection has occurred inside Forge:
Error: node-gyp failed to rebuild '... \resources\app\node_modules\deasync'

@rzhao271 @dhruvmanila This is still broken on Windows see these attempts to fix https://github.com/nodejs/node-gyp/issues/2869#issuecomment-1693409123

Python 3.12 released on Oct 2nd and got it by default with other tooling and nothing is working now because distutils is removed

@jurijsk It's sad, as we knew Python was removing it and have done nothing about it!

Any progress? node-gyp cannot work on Python 3.12 now.

Same issue here (Windows, python 3.12.0)

Doesn't work on Mac either

The upstream fix still hasn't been merged nodejs/gyp-next#197

@rzhao271 upstream was merged since that

🤖 Release is at https://github.com/nodejs/gyp-next/releases/tag/v0.15.1 🌻

I will work on this today.

If some of you are frustrated then please do python3 -m pip install packaging and report back here if that fixes things.
Other activities blocked vendoring effort today but I will dig in with my first coffee tomorrow.

@cclauss This fixed the issue! Thank you.

Thx.  I will make it so that step is not needed but your effort really helps.

I'm seeing errors in our build process that distutils is missing in Python 3.11.6, I can't find reference to these changes being backported in the changelog for this Python version, but maybe it's possible?

Partial Log
D:\a\pulsar\pulsar\ppm\node_modules\git-utils>if not defined npm_config_node_gyp (node "D:\a\pulsar\pulsar\ppm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "D:\a\pulsar\pulsar\ppm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
undefined
Traceback (most recent call last):
  File "D:\a\pulsar\pulsar\ppm\node_modules\npm\node_modules\node-gyp\gyp\gyp_main.py", line 42, in <module>
    import gyp  # noqa: E402
    ^^^^^^^^^^
  File "D:\a\pulsar\pulsar\ppm\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 9, in <module>
    import gyp.input
  File "D:\a\pulsar\pulsar\ppm\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 19, in <module>
    from distutils.version import StrictVersion
ModuleNotFoundError: No module named 'distutils'
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (D:\a\pulsar\pulsar\ppm\node_modules\npm\node_modules\node-gyp\lib\configure.js:305:16)
gyp ERR! stack at ChildProcess.emit (node:events:365:28)
gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
gyp ERR! System Windows_NT 10.0.20348
gyp ERR! command "D:\\a\\pulsar\\pulsar\\ppm\\bin\\node.exe" "D:\\a\\pulsar\\pulsar\\ppm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd D:\a\pulsar\pulsar\ppm\node_modules\git-utils
gyp ERR! node -v v16.0.0
gyp ERR! node-gyp -v v9.4.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\npm\cache\_logs\2023-10-18T18_54_57_896Z-debug.log
Done in 208.45s.
Command completed after 1 attempt(s).

Or here's the full run where this occurs:

Using Python 3.11.6 - Where it fails
Using Python 3.11.5 - Where it succeeds

The Py3.11 runs that you linked to all pass, not fail.
distutils was removed in Py3.12 but 3.11 should be fine.  If you can reproduce on Py3.11, please open a SEPARATE issue and include a FULL log.
The "Partial" Log is a mistake because the lines just above the "Partial" part would have documented exactly which Python version was running.  My bet is that it was Py3.12

@cclauss I understand that it reports it passed, but the logs do include a failure. Apologies. I'll open a separate issue.

I'm seeing errors in our build process that distutils is missing in Python 3.11.6, I can't find reference to these changes being backported in the changelog for this Python version, but maybe it's possible?
Partial Log
Or here's the full run where this occurs:

Using Python 3.11.6 - Where it fails
Using Python 3.11.5 - Where it succeeds

EDIT: I may have spoken too soon. Pinning Python to 3.11.5 still results in No module named 'distutils'. Here's the run. So not sure if this is the same issue or not, apologies if not and this is just noise. Just seems interesting the error matches exactly.
But I'll try the command suggested above to install packaging or the Python Changelog suggests installing setuptools to reintroduce distutils.

for me, fwiw:
pip install packaging - did not work
pip install setuptools - worked

Update: Today gyp-next v0.16.0 was released.

https://github.com/nodejs/gyp-next/releases

This includes some key Windows and Python 3.12 fixes.
Once that is brought into this repo we should see nice improvements in all the issues discussed above.
Who has the expertise to resync with the current gyp-next.

EDIT: This advice was for node-gyp < v10 but is not required for later versions.

If some of you are frustrated then please do python3 -m pip install packaging and report back here if that fixes things.
Other activities blocked vendoring effort today but I will dig in with my first coffee tomorrow.

Wasn't working for me in the case of installing @signalapp/better-sqlite3, but doing pip install setuptools solved it for me.
https://github.com/WiseLibs/better-sqlite3/issues/1093

I am using python3.12 for venv and I have a same problem with execute pandas_datareader.

Please look at your error log and ensure it contains the line gyp info using<EMAIL_ADDRESS>

pip install setuptools

Tengo dos semanas buscando el bug porque no podia correr tensorflow/tfjs muchas gracias!

https://stackoverflow.com/a/76691103/13086128

EDIT: This issue was closed via nodejs/gyp-next#214 which is available in node-gyp v10+.

nodejs/gyp-next#214 -->
#2923


S3 asset storage does not release http connections

Describe the bug
When downloading files archived to S3, the S3 asset storage does not release http connections. After downloading several files, the following error appears in the Opencast log:
"Caused by: com.amazonaws.SdkClientException: Unable to execute HTTP request:
 Timeout waiting for connection from pool"

The same code works fine in 5.x using an older version of the AWS Java sdk but, in 11.x, if the S3 object is not closed, it does not release the http connection.
To Reproduce
Steps to reproduce the behavior:

Set maximum number of connections to a very low number in /etc/org.opencastproject.assetmanager.aws.s3.AwsS3AssetStore.cfg: org.opencastproject.assetmanager.aws.s3.max.connections=N
Use the /assets REST endpoint to download N+1 files that were archived to S3 e.g. /assets/assets/{mediaPackageID}/{mediaPackageElementID}/{version}/{filename}
The N+1 download will hang and then time out, and you will see the above error in the log.

To debug, you can enable AWS metrics and log them:

Add -Dcom.amazonaws.sdk.enableDefaultMetrics as extra java opts.
Add logging:

log4j2.logger.awssdk.name = com.amazonaws
log4j2.logger.awssdk.level = DEBUG (It's recommended to leave it at WARN later)

And look at the Opencast log, you will see something like:
(AWSRequestMetricsFullSupport:204) - ServiceName=[Amazon S3], StatusCode=[200], ServiceEndpoint=[https://<ARCHIVE_BUCKET>.s3.amazonaws.com], RequestType=[GetObjectRequest], AWSRequestID=[DAXTCH4KKE9X3TDA], HttpClientPoolPendingCount=0, RetryCapacityConsumed=0, HttpClientPoolAvailableCount=0, RequestCount=1, HttpClientPoolLeasedCount=0, ResponseProcessingTime=[4.206], ClientExecuteTime=[322.684], HttpClientSendRequestTime=[5.119], HttpRequestTime=[222.462], ApiCallLatency=[248.446], RequestSigningTime=[3.972], CredentialsRequestTime=[55.228, 0.028], HttpClientReceiveResponseTime=[107.072],
where HttpClientPoolLeasedCount only increases and never goes down.
Environment Information

Opencast 11

How to tell if your aws bits aren't getting enough testing...
Are you seeing this with the default config? Or only if you set a limit manually?

Hi Greg,
Both. The default config is 50. We have a process where we "republish" old courses as new courses so downloading files from S3 is a common occurrence for us. We noticed that we could "repub" a few lectures and then no more. Decreasing the setting was only a way to debug the issue. This worked fine with our 5.x code base so I believe it was a change in the sdk. The aws documentation is clear in that you need to close the S3 object to release resources, but it's possible that it behaved differently in previous versions.

@rute-santos is this fixed?

Yes, the fix has already been merged.


Avatar in public User list

hello october community,
so i installed october cms with the user plugin.
i followed watch an learn and managed to extend the userplugin
(https://www.youtube.com/watch?v=AomK1eYAq78)
i even managed to do a frontend image upload for the avatar when a user registers
and the user can change it once the user has been activated.
so now i have a few users and i want to have a page where i can list them.
so i am doing this in the code section of the actual page:
use October\Rain\Auth\Models\User;

function onInit() {
    $this['activatedUsers'] = User::whereIsActivated(true)->get();
}

this gives me all the activated users. works like a charm. but how do i get the avatar?
in my template i can do this now:
{% for user in activatedUsers %}
    {{ user.name }} {{ user.surname}}
{% endfor %}

all of this workes like a charm, but when i try to get the avatar with:
{{ user.avatar }}
it returnes null. the images are ale in the system_files table where they are supposed to be.
but i can't reach them? can anybody help?

@ninobang I think you are using the wrong class at the top. Instead of October\Rain\Auth\Models\User, you would likely want to use RainLab\User\Models\User.

@bennothommo
thanks man, it works like a charm! i knew i was missing something really basic! :)


Basic Docker Instructions

Any chance we can get some basic docker instructions for running this locally?
The docker seems to just run nginx - it's completely unclear how to use/specify the config files with the docker. Running the docker just results in a blank output.
I was able to figure out how to get the server to run and specify config.yml and client-versions.yml flags, but dashboard, I cannot figure out.

So I think the only way to make this work is to build from the source Dockerfile with a modified config/config.prod.jsonc because otherwise simply overwriting /usr/share/nginx/html/config/config.json with a mount does not seem to be enough


The changelog page keeps opening every day, even when there are no updates, and even when I disabled the setting to open the changelog

It's opening the update log when I launch Chrome even though the last update was over a month ago.
It does this almost every day. Extremely annoying.

+1


Improve UX/discoverability of push notifications

taken from #989:

I don't think users dig the settings to enable notifications. I think we should ask them when installing the PWA or after signing up for the first time or smth like that.
push notifications don't (always) use symbols or good deep links to be actionable... There are probably more features we aren't using.

clicking the push notification could lead to a web version of the full notification to read it. That's probably better then directly redirecting to the disposition view if the users didn't read the whole notification or could not, because it was too long

Chrome hat anscheinend den installieren button im menü weggemacht :/
also habs eben nochmal getestet, im gegensatz zu firefox gibts halt beim ersten visit diesen nicen banner der zum installieren promted
aber wenn man das nicht macht muss man auf "zum startbildschirm hinzufügen" tippen, und danach kommt ne choice zwischen installieren und shortcut adden.


Update gcp-bom to 26.49.0

Update gcp libraries-bom to 26.49.0

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

there is a couple of other dependencies need to be in sync:

google_api_services_bigquery : "com.google.apis:google-api-services-bigquery:v2-rev20240919-2.0.0"
google_api_services_storage : "com.google.apis:google-api-services-storage:v1-rev20240924-2.0.0"
google_cloud_datastore_v1_proto_client : "com.google.cloud.datastore:datastore-v1-proto-client:2.23.0"

See #32864
The one that caused problem was netty. We can hold on that for now

Will close this pull request and wait on https://github.com/apache/beam/pull/32864


plugins: add log streaming

This adds log streaming. The stream is transmitted via a base64 string because bytes didn't compile using our gRPC infrastructure.
This PR also exposes base64 encoding and decoding functions for C++ users of the API. For Python, this comes with the batteries included.

@bkueng it would be awesome if you could give this a quick check/review. I'm basically just saving the data stream but not doing any reordering or retrying.

Is the timeout to basically restart logging if we haven't received data in a bit?

Yes exactly. It's not strictly required.

Yes exactly. It's not strictly required.

We'll see if I have to add it once I'm testing it.

Forgot to update proto submodule, duh.

I'm basically just saving the data stream but not doing any reordering or retrying.

Just keep in mind that without considering the sequence number, a message drop will likely lead to a corrupt ulog stream. Which is very likely going to happen if going through a serial link.

Aha, so what do you do on drop? Remove what's currently in the buffer to be written and start fresh?

Yes, that's what first_message_offset is used for. If data is dropped, it tells you when there is a valid message start again.

Ok thanks. I'll try to add that.

Coming with https://github.com/mavlink/MAVSDK/pull/2290.


silent and logLevel option

nps version: v5.3.1
node version: v7.10.0
npm version: v4.6.1

Scripts file (or at least the relevant bits):
in package-scripts.js
options: {
 silent: true,
},

or
options: {
  logLevel: 'warn',
},

The command executed:
# with npm
npm start `anything`

# with yarn
yarn start `anything`

# or globally installed `nps`
nps `anything`

The output:
no differences, the output is still the same just like there's no option is configured.
Problem description:
I need to tame the verbosity of the output a little bit, because I think nps is too 'noisy' with default settings.
But is it me or am I doing the options wrong?

Is your options property at the same depth as scripts? What I mean:
module.exports = {
  scripts: {
    ...
  },
  options: {
    silent: true
  }
}

@Miklet yes, I set scripts and options at the same level
pretty much like this https://github.com/kentcdodds/nps/blob/master/package-scripts.js#L66

@kentcdodds Alright, I did some investigation and probably found a reason. In nps.js we do merge of options from package-scripts.js and cmd options. Command line options take precedence and since values for logLevel and silence are not provided they receive their default values which is false for silent and 'info' for logLevel.

@Miklet so it means any options I set in package-scripts.js will always be ignored?

I think yes :( But I also want to wait for @kentcdodds comment. Btw. you can still pass -s or --silent option to make nps less noicy until it will be fixed.

Yep, that sounds like the problem. The food would be to remove the CLI defaults I think. Happy to accept a pull request 😀

sure, but I need times to figure out how nps works first 😁

Take your time :) It's as urgent as you need it to be :)

Had a look into this and there don't seem to be too many complex changes necessary to fix it, theoretically anyway. Still accepting a PR for this?

Sure 👍

Made a PR above that would finally fix this issue. :)


Connecting through a proxy

Thanks for this very interesting plugin.
I faced a problem to connect to my SharePoint because my network is through a proxy.
Should it be possible to use the tool behind a proxy ?
Tried this but got a Cookie problem:
ctx_auth = AuthenticationContext(url)
ctx_auth.acquire_token_for_user(username, password)
request = ClientRequest(ctx_auth)
options = RequestOptions("{0}/_api/web/".format(url))
options.set_header('Accept', 'application/json')
options.set_header('Content-Type', 'application/json')
options.set_header('proxies',  {'http':'http://XX.XX.XX.XX:8080',
'https':'https://toto:titi@XX.XX.XX.XX:8080'})
data = request.execute_query_direct(options)

Could you provide the error that you're seeing? What precisely do you mean by "Cookie problem."

This is the traceback problem :
<client.office365.runtime.utilities.request_options.RequestOptions object at 0x0000000003D0E3C8>
TypeError                                 Traceback (most recent call last)
 in ()
16 options.set_header('proxies', {'http':'http://XX.XX.XX.XX:8080',
17    'https':'https://toto:titi@XX.XX.XX.XX:8080'})
---> 18 data = request.execute_query_direct(options)
C:\Anaconda2\envs\dcfta\lib\site-packages\client\office365\runtime\client_request.py in execute_query_direct(self, request_options)
77         """Execute client request"""
78         print request_options
---> 79         self.context.authenticate_request(request_options)
80         if request_options.method == HttpMethod.Post:
81             from client.office365.sharepoint.client_context import ClientContext
C:\Anaconda2\envs\dcfta\lib\site-packages\client\office365\runtime\auth\authentication_context.pyc in authenticate_request(self, request_options)
18     def authenticate_request(self, request_options):
19         """Authenticate request"""
---> 20         request_options.set_header('Cookie', self.provider.get_authentication_cookie())
21
22     def get_auth_url(self, redirect_url):
C:\Anaconda2\envs\dcfta\lib\site-packages\client\office365\runtime\auth\saml_token_provider.pyc in get_authentication_cookie(self)
63
64         logger.debug_secrets("self.FedAuth: %s\nself.rtFa: %s", self.FedAuth, self.rtFa)
---> 65         return 'FedAuth=' + self.FedAuth + '; rtFa=' + self.rtFa
66
67     def get_last_error(self):
TypeError: cannot concatenate 'str' and 'NoneType' objects

Are you working with the code from the python3-connect-rest-sample? That code doesn't include any references to the Office365 rest client, but the error message above is from the Office 365 rest client.
Let us know exactly what you're trying to accomplish, ideally including steps to reproduce the issue, and we'll try to help resolve the problem. Generally speaking, you should be able to work with the rest client through a proxy, but we'll need more information to help diagnose the issue. Thanks!


Consider having Money being a part of the People library

There's a set of concepts that describe the world of human beings:

Country, City, MailingAddress
Language
PersonName, GivenName, FamilyName
Gender (with oneof switching between enum Type with values MALE and FEMAIL and Any)
Organization, Person
Contact having PersonName
etc.

The types Currency and Money look like a part of a bigger thing which includes the types above.
Also a user of the framework may want to use own implementation for the monetary types. We'd better make these types an optional component because they are not used by the framework code.
All the money-related types seem to be isolated under the money.proto, and should allow extracting into a separate library.

This is a part of #74.


Right Click Menu: Right Click from Element to Element Discovery

Currently the right click context menu opens up based on the selected element. This ticket is to:

Explore passing in an element to the callback handler to generate the menu items vs generating them based on the selected element
Explore alternatives to the fullscreen clickable background element approach to dismiss the context menu. The new approach should be geared towards allowing for right clicking between elements, but not cause any regressions from the previous approach.

Task 1 should be pretty straight forward to implement, however, task 2 could be a rabbit hole. Mainly setting this up as a 3 point Discovery ticket in case there's no fruitful approaches for task 2 (which is very much a possible outcome).
Please try to time box this. It's okay if nothing gets discovered. This is just a possible UX enhancement, so it's not worth spending a week on if initial discovery seems like there's no possible paths

Verified in QA


Pgr 2845 - Multiple device sync should be handled accordingly for Android

Customer to test with app that supports multiple devices. Major changes here are

DeviceServiceV2
DeviceSyncManagerV2
sync requests are put into a queue and uses the payment device's seID to differentiate what device the sync request is for

So I'd like to understand why we need "v2" versions of these services, what's preventing from extending the support into the existing services?

First of all it works in a bit another way. Using new service you don't need to send class name via Intent, override init method (if I'm not mistaken Garmin had some issues with such behaviour) and so on.
Another reason is to allow OEM continue using old implementaion without any changes in their code.
So extending current service will lead to mess into it, since we need to add a lot of if/else checks into it to separate new and old behaviour.

So that's fair @skynet67 , but I'd like you to consider how this could be implemented as different patterns behind the existing services and their public methods.  Is there a way to mask this complexity behind the existing interfaces.
I don't like the idea of versioned services likes this, which will cause a tremendous amount of confusion for those integrating to the SDK.

@skynet67 Why the switch to tracking back seId?  This won't be a very good solution going forward as we'll be moving into areas where device's won't have seId's.   What issue was using deviceId causing?

@ssteveli what field is it better to use, is it ok to use deviceIdentifier?

Yes, that would be much better.

@dwt71 I'll add more javadoc after finishing PLAT-4330 and PGR-1265


chore: Fix issue templates

Some issue templates failed schema validation, making it impossible to create new issues using templates.

Hei @lusu007
Thanks for your effort. There was already a pr open to fix that problem. I just merged it and should work now.


Getting Unwated Redirect on Openning The website

Link to reproduction
No response
Environment Info
Payload: 3.0.0-beta.78
Next.js: ^15.0.0-rc.0
Node.js: v20.9.0

Describe the Bug
Getting unwanted redirect on opening the payload website template

Reproduction Steps
Run website template using create-payload-app
Adapters and Plugins
No response

Hey, it's not clear from your screenshot what you're referring to here. Can you elaborate please?

This is not due to HMR @paulpopus , I have created a production build and running it locally. I am also getting the same on my vercel deployment. Internal redirects can trick the crawlers and impact the SEO performance.

Ok I just tested this and I'm not able to replicate with blank or the website template.
Note that you should be running next canary 104 (or higher but 104 is the one we pin to) and the latest beta of Payload with React 19.
See our template's package.json here https://github.com/payloadcms/payload/blob/beta/templates/website/package.json

@paulpopus, I was able to reproduce it on chrome. When I fire up incognito window, the first request has the redirect

I am able to reproduce it on Next Canary 104, I have cloned the latest template and tried it out on the local machine. Sharing the curls for both the cases.
 If this is the reason, then is there any way to fix it?

Can you try a different browser perhaps? I just wonder if its something specific to your setup here. Either some configuration in chrome, some extensions. Can you test it with a browser that you don't regularly use and with default settings?
Technically guest window in Chrome should be enough but just in case

It's happening in the guest window as well. Specific to Chrome as of now. I am not getting the issue on Firefox or Safari. I was concerned as I got one warning on the search console about the redirect. We can close this issue for the time being. I will reopen and tag you if I get the error on GSC again. Thanks a lot for the quick help. Payload has been a boon for me. Keep up the good work :)


Convert filter tests to use doc tests

Most built-in filter tests are invoked as normal functions: builtin.rs#L614-L817. It is good that the functions are tested at all, but it too bad that this kind of test cannot not serve as documentation. Some filters are doc-tested using rinja code blocks builtin.rs#L53-L72, so the user gets a proper usage example in the documentation. Also, many filters contain some logic in the generator, which has to be tested, too.
It would be nice if some, if not all, filters could be tested with doc tests:

[ ] fmt
[ ] format
[x] linebreaksbr
[ ] paragraphbreaks
[ ] lower
[ ] lowercase
[ ] upper
[ ] uppercase
[ ] trim
[ ] truncate
[ ] indent
[ ] join
[ ] capitalize
[ ] wordcount
[ ] title
[x] pluralize
[ ] safe
[ ] escape
[ ] e
[x] filesizeformat
[ ] json
[ ] abs
[ ] into_f64
[ ] into_isize
[ ] urlencode
[ ] urlencode_strict

I'd be interested in helping out with this one!
Please let me know if you are looking for new contributors and if so, if you would like me to just go through your checklist here top to bottom. My understanding is that you would like doctests added to these filters. Are we adding new tests, or just copying the regular tests to doctests? Thank you!

New contributors and contributions are very welcome! From what I can see, in case the filter isn't tested, then you need to create one. If one already exist, I think copying it might be enough.

Thank you very much, @Wollaston, great work!


Remove old config file (set_config)

This PR aims to remove old config file, which is not used in the AxonDeepSeg codebase. For context, refer to #447 (Comment)
Fixes #447

This PR is ready for review.


Disable formatting conversion

The markdown->irc is quite buggy, and formats things it shouldn't (anything math, or anything with underscores breaks down).
I suggest just disabling it and sending it as-is, which is better than incorrectly formatted strings.

Yea that's probably a good idea until someone finds the time to implement a proper AST for discord parsing.
I've added this as a config option in 39d25cd9477cf34d25f3c0a8783677425d97fa60


publish<EMAIL_ADDRESS>

Requested by: @antonpirker
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] github
[ ] registry

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

#retract


Visual Block expansion to $ visually not consistent with Vim

I apologize if this has already been reported or is otherwise a consequence of misconfiguration on my end. It seems to be an interface-issue.
When in standard Vim it is possible to expand a Visual Block (C-v) til the end of all selected lines by doing "$" when on any line (even the shortest line). All lines will then be selected until their respective end.
In Oni2 (current EA build) it will instead select a rectangular block that runs only as far as the length of the current line. The behviour when actually perfoming a change is however correct (same as vim). So apparently the visual representation of the selection does not match what is actually selected in the buffer at that time.

Thanks for the issue, @ijzerbroot ! I don't think this has been logged before - nice catch.

he behviour when actually perfoming a change is however correct (same as vim). So apparently the visual representation of the selection does not match what is actually selected in the buffer at that time.

This is a good observation. It looks like the underlying selection model is correct, but that we are not rendering it properly here: https://github.com/onivim/oni2/blob/174af59f0c94303c2e6aec4a5b5e6292af16182f/src/Feature/Editor/Selection.re#L89 We need to pick up this case and make sure we're handling it there.


Change use of fetch() to use of axios() in frontend

Axios is a more robust library with better error handling. It works well with the error messages being displayed

Check that we are using axios everywhere

Update where fetch is found


[ZEPPELIN-1884] Prevent NullPointerException when JDBC query.

What is this PR for?
Sometimes users don't want to set the properties which they don't want to care about and common.max_count of JDBC interpreter is one of that property.
If it does not set the common.max_count, NullPointerException will occur.
What type of PR is it?
Bug Fix
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1884
How should this be tested?

Set properties like as following image and run select query.

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

LGTM.
shouldn't basePropretiesMap.containsKey(COMMON_KEY) be checked in other places then?

@felixcheung Thank you for review!
Currently only COMMON_KEY uses for max line count in JDBC interpreter but as like you mentioned it seems more make sense to move the code to open() method.
Let me fix then.

@felixcheung I updated code, please review. Thanks in advance.

LGTM


Use await in initSate() for sample

Hi,
In the sample code, you are using await in the initState() function, which is not recommended. It would be better to split this into a new function and call it from initState().

Thanks for your issue


Please invite me to the community

Name
Jyoti prakash Rout
Discord Username (if applicable)
Jyoti#0398
Additional Context
I'm an Web Dev Enthusiasts & a junior pursuing my Bachelors in Computer Science & Engineering. I'm interested in Web Devlopment, Android Devlopment, IOS Devlpoment, Machine Learning & Devops & I enjoy learning new things & stuff as well as I'm a Frontend Devloper with experience building Dynamic & Static Web pages. I am always interested in learning the answers to how, why and what relating to Technologies around me.
I would like to grow my programming skills by doing lot's of  Open Source Contribution. Looking forward to learn, collaborate and grow as a community.

Welcome to the community @Jyoti-prakash-rout ! ✨ 🎉 Happy to have you 😄  You can also join our Discord Server 🤓


Fixes to run on Danny's laptop

changed call to NP.pad to use ints in pad arg

Too outdated and all changes incorporated.


Add SSL profile ID to EnrollControlCardReq

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 88.485%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
292

Relevant Lines:
330

💛  - Coveralls


Max Width and Max Height to chat widget

Update chat widget style for improved responsiveness and visibility
Set maximum width and height for the chat widget to enhance responsiveness and ensure proper visibility on various devices and screen sizes. This improves user experience and ensures the widget remains accessible.
issue: #176

Thank you, amazing PR. Do you have any other changes to make?

thank you @n4ze3m, for now I'm looking and testing your amazing work. If I have any other changes to make I'll will send you a PR :)


Unable to convert generator returning 1D arrays into a 2D array using fromiter/vstack

Feature Request

[X ] I have tried using the latest released version of Numba (most recent is
visible in the release notes
(https://numba.readthedocs.io/en/stable/release-notes-overview.html).
[X ] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

I am failing to convert a generator function that returns 1D arrays into a 2D array using numba's fromiter or vstack implementation.
Here is a generator function returning 1D-arrays.
import numpy as np
import numba as nb

@nb.njit
def gen():
    """Generator function returning 1D-arrays."""
    for i in range(3):
        yield np.arange(i, i+3)

The use_gen_fromiter() function raises a TypingError.
@nb.njit
def use_gen_fromiter():
    # return np.fromiter([row for row in gen()], dtype=np.dtype((np.int64, 3)))
    return np.fromiter(gen(), dtype=np.dtype((np.int64, 3)))

print(use_gen_fromiter.py_func())
# [[0 1 2]
#  [1 2 3]
#  [2 3 4]]
print(use_gen_fromiter())
# TypingError: Use of unsupported NumPy function 'numpy.fromiter' or unsupported use of the function.

I also tried using np.vstack() to stack the arrays obtained from the generator into a 2D array.
However, this also raises a TypingError.
@nb.njit
def use_gen_vstack():
    return np.vstack(list(gen()))

print(use_gen_vstack.py_func())
# [[0 1 2]
#  [1 2 3]
#  [2 3 4]]
print(use_gen_vstack())
# TypingError: No implementation of function Function(<function vstack at 0x7faa6fe66d40>) found for signature:
# vstack(list(array(int64, 1d, C))<iv=None>)

A possible workaround could be converting the generator into a list and fill an array.
@nb.njit
def use_gen_arraylist():
    arraylist = list(gen())
    n = len(arraylist)
    k = arraylist[0].shape[0]
    res = np.empty((n, k), dtype=arraylist[0].dtype)
    for i in range(n):
        res[i] = arraylist[i]
    return res

print(use_gen_arraylist())
# [[0 1 2]
#  [1 2 3]
#  [2 3 4]]

Can the additional step of converting the generator into a list be avoided?
Python: 3.12.0
Numpy: 1.26.4
Numba: 0.59.1
<!--

Thanks for the nice report - I think this needs labelling as a feature request to support these functions.
I also tried not using the list in the vstack version:
import numpy as np
import numba as nb

@nb.njit
def gen():
    """Generator function returning 1D-arrays."""
    for i in range(3):
        yield np.arange(i, i+3)

@nb.njit
def use_gen_vstack():
    return np.vstack(gen())

print(use_gen_vstack())

and the error message says:
TypeError: arrays to stack must be passed as a "sequence" type such as list or tuple.

which is a bit odd, given that the list created from the generator isn't accepted, as in your original report.

The error message for "np.vstack(gen())"
TypeError: arrays to stack must be passed as a "sequence" type such as list or tuple.
seems to be OK as per Python's definition of a Sequence.

The part of the message I thought was a problem was the implication that a list must be passed - your second example in the issue report appears to be passing a list but that still doesn't work.

I have seen the function being used in https://github.com/numba/numba/issues/4271
This lead me to the conclusion it might be supported.

I think if any of the snippets in that issue did run at some point, they might have fallen back to object mode - I can't get any of the code in that issue to run at present. A variation on those snippets I can get to run is:
from numba import jit
import numpy as np

@jit(forceobj=True)
def func(x):
    return x[0]

@jit(forceobj=True)
def error():
    topo = [chr(ord('a') + i) for i in range(5)]
    types = [(var_name, "int") for var_name in topo]
    sampled = np.zeros(10, dtype=types)
    return np.fromiter([func(x) for x in sampled], dtype=int)

print(error())

but you don't really want to be running in object mode, since its only effect is really to remove a tiny bit of interpreter loop overhead within your function.

@gmarkall should I open a separate issue to support advanced data types in the numpy.dtype implementation?

I think that seems like a good thing to do, to keep the discussions simpler to follow in issues - many thanks!

What you observe above is expected. The types.containers.ListType is a Numba type used for Numba's type system. The object you get returned when creating a typed list is a numba.typed.List:
from numba import njit, typed

@njit
def give_a_list():
    return typed.List([1, 2, 3])

print(isinstance(give_a_list(), typed.List))

prints
$ python listtype.py
True

This feature does not seem to be supported. Is that correct?

I think that is correct. The docs are not very clear about what it might accept though: https://numba.readthedocs.io/en/stable/reference/numpysupported.html#other-functions

I removed the question label so the stale bot won't close this.


When using BurnerWallet, Transactor is unable to properly parse errors

How to reproduce:

Deploy the default contracts and UI
Use the app with a BurnerWallet (which is the case by default, make sure you are not using Metamask).
Submit an empty new purpose, which will revert with "purpose can not be empty".
Instead of seeing a nice error, the error is caught but it's unable to properly parse it and can't access all the data.

You might, instead, get something like this:
Error: cannot estimate gas; transaction may fail or may require manual gas limit (error={"reason":"processing response error","code":"SERVER_ERROR","body":"{\"jsonrpc\":\"2.0\",\"id\":60,\"error\":{\"code\":-32603,\"message\":\"VM Exception while processing transaction: revert \\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000@\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0018Purpose can not be empty\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\\u0000\"}}","error":{"code":-32603},"requestBody":"{\"method\":\"eth_estimateGas\",\"params\":[{\"gasPrice\":\"0x1dcd65000\",\"from\":\"0x8760db2223686b352d4993deb77a47982c502992\",\"to\":\"0x5fbdb2315678afecb367f032d93f642f64180aa3\",\"data\":\"0xeb68757f00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000\"}],\"id\":60,\"jsonrpc\":\"2.0\"}","requestMethod":"POST","url":"http://localhost:8545"}, tx={"data":"0xeb68757f00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000","to":{},"from":"0x8760Db2223686B352D4993DEb77A47982C502992","gasPrice":{},"nonce":{},"gasLimit":{},"chainId":{}}, code=UNPREDICTABLE_GAS_LIMIT, version=abstract-signer/5.3.0)
    at Logger.makeError (1.chunk.js:87437)
    at Logger.throwError (1.chunk.js:87447)
    at 1.chunk.js:78554
    at async Promise.all (:3000/index 5)

hey I think this was fixed in this commit: https://github.com/austintgriffith/scaffold-eth/commit/0cf8280e628645535c1a339011eede29cae401dc#diff-b28b1ed9821f38c64524ea13e19264bb0772f8376afffd5d8a1f8277621833eb

Hey @azf20 not so much. That change makes the notification output read a bit better by not showing the whole error output, but it doesn't show the actual revert message as it should and it does with Metamask.
See the screenshots below:
With BurnerWallet we get this un-parsed error string, also the notification doesn't specify the revert reason. 😞 😞 😞 😞

With Metamask we get this nice object and the rever reason 😃

Ah yes right you are. That is a shame. The burner account doesn't actually use BurnerWallet, it is just a vanilla ethers.js wallet, but it seems like it's a bit of a challenge between Ethers and the blockchain client per this issue.
And it seems like Metamask also isn't immune given the client dependency, as when I deploy on Rinkeby / Kovan I don't get the nice error on Metamask either.
Rinkeby

Kovan

Added a fix here:
Tested with Metamask and with default ethers signer.
https://github.com/austintgriffith/scaffold-eth/pull/237


consider changing EventListenable.collect to return Nothing

SharedFlow.collect function specifies Nothing as its return type. This is helpful for preventing errors, since the linter can mark any code after collect as unreachable.
Consider changing the EventListenable.collect extension function to match.
See also this issue: https://github.com/Kotlin/kotlinx.coroutines/issues/2789

Thanks for the heads up! Will do.


Remove dead files

Summary

These are left-overs from CI that we no longer use.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

@osrf-jenkins run tests please!


[BUG] [Maven] License analysis is failing for Eclipse che pom.xml

Here is the API response:
[https://gist.github.com/arajkumar/c59acddb10ba71b7d4b153c879b2b9a5#file-res-json-L1460
]
Following error is seen in the response:
"license_analysis": {
"reason": "Some unexpected exception happened!",
"status": "Failure",
"outlier_packages": [],
"unknown_licenses":
{ "really_unknown": [], "component_conflict": [] }
,
"conflict_packages": [],
"f8a_stack_licenses": [],
"current_stack_license": {}
},

https://github.com/fabric8-analytics/fabric8-analytics-license-analysis/pull/196
https://github.com/fabric8-analytics/fabric8-analytics-license-analysis/pull/197


Does using enginePool cause memory leaks？

I need to run v8runtime 100~1000 per second, use enginepool to initialize the instance, and load the lodash library in each v8runtime. When running at full speed, the console has a lot of warnings.
I have 2 questions:

Will continuous operation cause memory leaks?
How to release these objects in time?

Please read https://github.com/caoccao/Javet/blob/main/docs/tutorial/memory_management.rst very carefully and apply try-with-resource.
In your code, you need to wrap lodashGet. Usually, people from J2V8 need some time to get used to the Javet coding style.
try (V8Value lodashGet = ...) {
    if (lodashGet.isUndefined()) {
        // ...
    }
}


Does not work on python 3.7

Hello there, I'm trying to use elevenlabs on my raspberry python, using python 3.7 cuz that's the only version where numpy works out of the box for raspberry
But unfortunately, it throws a typing error:
Traceback (most recent call last):
  File "main.py", line 13, in <module>
    import lib.elevenlabs as elevenlabs
  File "/home/pi/Projects/bmo/lib/elevenlabs.py", line 7, in <module>
    from elevenlabs import generate, Voice, VoiceSettings
  File "/home/pi/.local/lib/python3.7/site-packages/elevenlabs/__init__.py", line 2, in <module>
    from .simple import *  # noqa F403
  File "/home/pi/.local/lib/python3.7/site-packages/elevenlabs/simple.py", line 101, in <module>
    ) -> Union[bytes, Iterator[bytes]]:
TypeError: 'ABCMeta' object is not subscriptable

I think should be easily fixable, let me try to send a PR

oh, nvm, I see that on the latest version it's already fixed, cheers :)


Install problem of GA4GH API demo

hello：
I   try to install the API demo following the command: "pip install --pre ga4gh". But I got Error：
subprocess.CalledProcessError: Command '['wget', 'https://pypi.python.org/packages/source/s/setuptools/setuptools-0.7.zip', '--quiet', '--output-document', '/srv/ga4gh/ga4gh-server-env/build/ga4gh/setuptools-0.7.zip']' returned non-zero exit status 8

Command python setup.py egg_info failed with error code 1 in /srv/ga4gh/ga4gh-server-env/build/ga4gh
Storing complete log in /root/.pip/pip.log
WHO can tell me WHY？
Thanks a lot!

Can you give us a little more detail on your system please @hltdym? What's the OS and the version of Python?
Exit status 8 from wget seems to indicate a server error, so this might just be a transient pypi problem.

The version of Python is Python 2.7.3.
I think it is because of  the wget path "https://pypi.python.org/packages/source/s/setuptools/setuptools-0.7.zip" is not found.
When I run:
wget https://pypi.python.org/packages/source/s/setuptools/setuptools-0.7.zip
--2015-07-17 16:26:33--  https://pypi.python.org/packages/source/s/setuptools/setuptools-0.7.zip
Resolving pypi.python.org (pypi.python.org)... <IP_ADDRESS>
Connecting to pypi.python.org (pypi.python.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response...
404 Not Found
2015-07-17 16:26:34 ERROR 404: Not Found.
But I do not known how to deal with it ?

OK, this looks like a bug in our setup script. Basically, we're looking for setuptools and version 0.7 is the earliest version we can use. However, it seems that version 0.7 has disappeared. If you install setuptools manually, you should be able to continue and run the demo.
Try running pip install setuptools. If this doesn't work, there are instructions on https://pypi.python.org/pypi/setuptools to help bootstrap this.
Sorry for the hassle, and thanks for the bug report!

Should be fixed after #517


Vcpkg spawns processes with IDLE_PRIORITY_CLASS, causing slow builds with low CPU usage on Windows

Describe the bug
Build related processes like Ninja spawned by vcpkg seem to have a very low priority, causing the build to use very few CPU cores despite setting the VCPKG_MAX_CONCURRENCY to a high value.
Environment

OS: Windows
Compiler: revision

To Reproduce
Steps to reproduce the behavior:

./vcpkg install xxx
Bring up Task Manager
Right click on Ninja.exe, go to details
Right click and look at the priority
It is Low

Expected behavior
At least give it a normal priority!
Additional context
The issue is caused by this in windows_create_process which vcpkg uses to spawn subprocesses on Windows. For some reason, the priority is set to IDLE_PRIORITY_CLASS, which according to the doc, 'run only when the system is idle'. This is probably affecting the performance of vcpkg for years as it was introduced in the very beginning of the commit history.
By setting the value to NORMAL_PRIORITY_CLASS, I was able to fix this issue. Please change this or make this configurable. I would be happy to make a pr if this is indeed a bug.

Can you give a specific example?

Can you give a specific example?
Yes,  vcpkg install llvm in the first step.

causing the build to use very few CPU cores

Hmm are you on a system with more than 64 cores?

No. The number of processes is correct (I have 24 cores and there are roughly 24 cl.exe processes in task manager). It's just the number of utilized CPUs that is clearly incorrect; these 24 processes seem to only make 8 cores go 100% on task manager. And once I manually set the ninja.exe's priority to Normal in Task Manager. All cores were working. I tested this on my work PC today. The problem manfested as it did on my home PC.

vcpkg tool windows issue?
https://github.com/microsoft/vcpkg-tool/blob/074906ace8f7c59a7afee07255d58dd9edcd9b91/src/vcpkg/base/system.process.cpp#L836

vcpkg tool windows issue? https://github.com/microsoft/vcpkg-tool/blob/074906ace8f7c59a7afee07255d58dd9edcd9b91/src/vcpkg/base/system.process.cpp#L836

Exactly.


CWE-1080 Source Code File with Excessive Number of Lines of Code

Usage Name
Excessively large file
Reference
https://cwe.mitre.org/data/definitions/1080
Roles

the Operation
the SourceCode

Detection Patterns

8.2.115 ASCQM Limit Size of Operations Code

After initializing with
/static/driver/main.py --init
Run
/static/driver/main.py --report --metric 'LOC' --excess=<interval>
Where <interval> in ["low", "range", "high"]
To report files in that interval. As recommended in the reference above, the current high value is set at LOC=1000,
while those files with LOC < 100 are classified as low. Everything in between is in range.


bad targets input results in "invalid memory address or nil pointer dereference"

~/g/s/g/r/r/inspect-es ❯❯❯ vegeta -version                                                                                ⏎
???

i most likely was using cf6baac643f6b6e60cb2428d25202240ec548c8b though, just after 5.9.0
i'm running vegeta called from a script as vegeta attack -duration 180s -rate 200 , feeding it targets on stdin.
i introduced a bug in the script that caused it to feed "targets" like so:
X-Org-Id: 2

X-Org-Id: 2

this caused:
2016/01/14 18:33:01 bad method: X-Org-Id:
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x10 pc=0x63c43f]

goroutine 1 [running]:
github.com/streadway/quantile.(*Estimator).Get(0x0, 0x3fe0000000000000, 0x0)
	/home/dieter/go/src/github.com/streadway/quantile/quantile.go:141 +0x1f
github.com/tsenart/vegeta/lib.(*Metrics).Close(0xc8200a6200)
	/home/dieter/go/src/github.com/tsenart/vegeta/lib/metrics.go:137 +0x30b
main.report(0x7d1968, 0x4, 0x7d1808, 0x5, 0x7d1810, 0x6, 0x0, 0x0)
	/home/dieter/go/src/github.com/tsenart/vegeta/report.go:99 +0x9bd
main.reportCmd.func1(0xc82000a2b0, 0x0, 0x0, 0x0, 0x0)
	/home/dieter/go/src/github.com/tsenart/vegeta/report.go:21 +0xb6
main.main()
	/home/dieter/go/src/github.com/tsenart/vegeta/main.go:73 +0x909

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
	/usr/lib/go/src/runtime/asm_amd64.s:1696 +0x1

goroutine 5 [syscall]:
os/signal.loop()
	/usr/lib/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
	/usr/lib/go/src/os/signal/signal_unix.go:28 +0x37

goroutine 6 [select, locked to thread]:
runtime.gopark(0x86e978, 0xc820030728, 0x7d1520, 0x6, 0x434f18, 0x2)
	/usr/lib/go/src/runtime/proc.go:185 +0x163
runtime.selectgoImpl(0xc820030728, 0x0, 0x18)
	/usr/lib/go/src/runtime/select.go:392 +0xa64
runtime.selectgo(0xc820030728)
	/usr/lib/go/src/runtime/select.go:212 +0x12
runtime.ensureSigM.func1()
	/usr/lib/go/src/runtime/signal1_unix.go:227 +0x353
runtime.goexit()
	/usr/lib/go/src/runtime/asm_amd64.s:1696 +0x1

upgraded to latest git master. cannot reproduce anymore. saw some recent commits from last november that probably fixed this case.


Automatic style checker

Is there a tool that allows checking of this style automatically? If not, would it be interesting for you?

yep. i'd like a jscs-angular based on my guide. just havent had time

similar thread #207

dupe of #194


Update the release cheat-sheet

Changes
Starting storing release images in ghcr.io.
/kind documentation
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] pre-commit Passed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Container images in the release are stored in ghcr.io,

/test check-pr-has-kind-label

/test pull-tekton-pipeline-go-coverage-df

/lgtm


cleanup: Remove edgex-volume and correct service dependencies

The purpose of this PR is to remove the ~100MB dependency of edgex-volume from the docker-compose files, and make modifications to the service dependencies to reflect the service dependency graph.  Several changes have been made to minimize spurious differences across mongo/redis, no-security/security, and amd64/arm64 versions of the compose files.  It is expected that these changes will also make it easier to remove the logging service in a future PR.
cc: @lenny-intel, @tingyuz, @andresrinivasan, @cloudxxx8
Signed-off-by: Bryon Nevis<EMAIL_ADDRESS>

I tested it locally- except have to restart the virtual-device service once from portainer, everything else seems to be working .

Waiting for https://github.com/edgexfoundry/blackbox-testing/issues/438 to be resolved before moving this out of draft phase, otherwise putting this PR through will break blackbox testing.

https://github.com/edgexfoundry/blackbox-testing/issues/438 resolved

LGTM
But when I ran docker-compose-nexus-redis.yml locally, I got:

Failed to load schedules and events Could not dial Redis: ERR invalid password in support-scheduler log
Couldn't register to metadata service: 500 - Could not dial Redis: ERR invalid password in device-virtual log after restarting the device-virtual service (the first time was error: checking required dependencied services failed)

They are not the issues caused by these PR, so I thought we can merge this first.
@FelixTing to see the device-virtual error

@jinlinGuan, I agree with @cloudxxx8.  I did spin this up again and was not able to reproduce the issue.  For anyone doing validation testing, ensure that you are running the latest container versions (docker-compose pull) and prune docker volumes (docker volume prune) from the previous runs.


Support for Kubernetes 1.28.x

Currently, the Helm Chart configuration/configuration/Chart.yaml limits Kubernetes max version to 1.27.x
I've deployed YAKE to a cluster with 1.28.6 without any issue.
Would it be possible to bump this limit to support v1.28.x?

I've deployed YAKE to a cluster with 1.28.6 without any issue.
That's great to hear!

We'll update our CI to include 1.28 and add support with the next release.

We've added support for 1.28 with 1.89.0-2.

Thank you very much, but I don't see 0b5e2e0 being included in https://github.com/YAKEcloud/yake/commits/v1.89.0-2/

Yep, you're correct. I backported it to the 1.89 branch. https://github.com/YAKEcloud/yake/releases/tag/v1.89.0-3


Typo in Text to HighLevel Picture...

maybe there is a typo in the description to the high-level picture: "Contoso may also have regular (direct) Azure subscriptions, which are billed directly to Contoso." -> i think you mean: "Contoso .... billed directly to Microsoft" ?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c8558255-da49-b81f-e488-bcdf40b8e154
Version Independent ID: 9f58faac-dc04-067c-2780-44a551f027f7
Content: Azure Active Directory Domain Services for Azure Cloud Solution Providers
Content Source: articles/active-directory-domain-services/active-directory-ds-csp.md
Service: active-directory-ds
GitHub Login: @mahesh-unnikrishnan
Microsoft Alias: maheshu

@Naboo2604 Thanks for your feedback! We will investigate and update as appropriate.

@Naboo2604 Please note that if organization has Azure Subscription then based on usage the organization (in this case Contoso) is billed directly by Microsoft.

@Naboo2604 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


added link (adds enhancement #596)

Checklist

[x] Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
[x] If this PR comes from a fork, please Allow edits from maintainers
[x] Set a speaking title. Format: {task_name} (closes #{issue_number}). For example: Use logger (closes # 41)
[ ] Link your Pull Request to an issue (if applicable)
[x] Create Work In Progress [WIP] pull requests only if you need clarification or an explicit review before you can continue your work item.
[x] Make sure that your PR is not introducing unnecessary reformatting (e.g., introduced by on-save hooks in your IDE)
[x] Make sure that your PR does not contain changes in strings.xml (see issue #332)
[x] Make sure that your PR does not contain compiled sources (already set by the default .gitignore) and / or binary files

Description

Hi @Fabus1184 ,
thank's for your contribution! :) But unfortunately we can't include this enhancement, this files are provided to us and we aren't allowed to change them. Nevertheless I'll forward this enhancement to the appropriate persons.
Cheers,
Luka

Ok, well can we add a button to open this pdf at the end of the activity heading when viewing the file in the app ?

It's a bit of a stretch to call adding a link "changing" the documents.

It's a bit of a stretch to call adding a link "changing" the documents.

I already created a pull request for a floating button to print the document when you view it


⚠ Secret Website 1 has degraded performance

In 3037dd8, Secret Website 1 ($SECRET_WEBSITE_1) experienced degraded performance:

HTTP code: 200
Response time: 6642 ms

Resolved: Secret Website 1 performance has improved in c6487ee.


[Feature] Expose force deletion as an API

Is your feature request related to a problem? Please describe.
The force delete feature is great; it allows many of our consumers to get their applications unstuck when Terraform fails under a variety of error conditions. But some of our consumers do not use the KubeVela CLI at all; instead, they have built higher-level abstractions (microservices and even UIs) that interact directly with the Kubernetes API to manage applications. We have hit situations in which these services need to issue a force delete.
For example, we have some Java code that uses the fabric8 client to create/delete applications. In some cases the Terraform apply for the application fails (for example, an AWS resource name conflict) and the Java code needs to clean the application up. But using fabric8 to call the Kubernetes API to delete the application doesn't work; the application becomes stuck in deleting.
Describe the solution you'd like
We'd like the ability to call an API to force delete the application.
The API should be provided through Kubernetes so that our consumers do not have to configure additional endpoints and authentication--knowing the Kubernetes endpoint and credentials should be sufficient. In the most ideal implementation, our Java code that uses fabric8 could use fabric8 to issue the force delete as well.
Describe alternatives you've considered

We could port the force deletion logic from the vela CLI to a new Java library that our consumers can use. This is not desirable because there must be an on-going maintenance effort to port any future force-delete-related changes from the vela CLI. Also, some consumers may use languages other than Java and additional porting effort will be needed.
We could exec the vela CLI as a sub-process to perform the force deletion. But the CLI seems better for humans to use than code to use it. Also, getting the Kubernetes cluster endpoint and credentials from the Java process to the sub-process would be error-prone. Furthermore, it would be difficult to build this approach as a library that can be used by many teams because it wouldn't just be a JAR but also a change to how the teams build their containers to include the vela CLI. Overall, this wouldn't be a very elegant approach.

This feature is taken into consideration but it might need some time. Sorry for the late response.
We are discussing making an force deletion API in velaux apiserver / prism. But for the prism library, there is repo dependency issue so it might be a bit hard to deal with it.


add debugging instructions

/cc @Araq
I was trying to debug https://github.com/nim-lang/nimsuggest/issues/93 but ran into a number of issues;
it turns out debugging nimsuggest is tricky, we should add instructions in doc/nimsuggest.rst

compiling nimsuggest in debug mode:
one gotcha is that -o:/tmp/nimsuggest_dbg won't work, see https://github.com/nim-lang/nimsuggest/issues/91#issuecomment-435548683
this works:

$nimc_D/bin/nim c -o:bin/nimsuggest_dbg --noNimblePath -p:compiler --debugger:native nimsuggest/nimsuggest.nim

at least with that we get proper stacktraces (eg https://github.com/nim-lang/nimsuggest/issues/93#issuecomment-435546865 instead of just SIGSEGV: Illegal storage access)

using gdb currently doesn't work for OSX on latest OS (mojave), see https://stackoverflow.com/questions/52529838/gdb-8-2-cant-recognized-executable-file-on-macos-mojave-10-14
I got BFD "unknown load command 0x32" which led me there; it has nothing to do with Nim but affects all programs
if you're not affected by this issue, you may try your luck with:

gdb --args $nimc_D/bin/nimsuggest_dbg3 --stdin --debug bugs/nimsuggest/t01.nim

although the caveat below (stdin) may apply

using lldb doesn't work with --stdin

this will block forever:
lldb -- $nimc_D/bin/nimsuggest_dbg3 --stdin bugs/nimsuggest/t01.nim
usage: sug|con|def|use|dus|chk|mod|highlight|outline|known file.nim[;dirtyfile.nim]:line:col
type 'quit' to quit
type 'debug' to toggle debug mode on/off
type 'terse' to toggle terse mode on/off
> sug bugs/nimsuggest/t01.nim:5:3

here's what worked for me:

$nimc_D/bin/nimsuggest_dbg3 --stdin bugs/nimsuggest/t01.nim

in another terminal, get pid:
pgrep nimsuggest_dbg3
48944
lldb -p 48944
c # press this to continue

now you can type commands in 1st terminal and it'll break in 2nd terminal if an error happens:
> sug bugs/nimsuggest/t01.nim:5:3

with the bug in https://github.com/nim-lang/nimsuggest/issues/93 I'm finally getting a proper lldb debug session, see example output here: https://github.com/nim-lang/nimsuggest/issues/93#issuecomment-435551093

For future reference, one can use the Microsoft provided C++ Debug extension to debug nimsuggest:
Below is a snippet showing me launching nimsuggest against the vscode extension, feel free to adjust it to your needs. Either in .vscode/launch.json or workspace settings under "launch" (depends upon whethe you're using a workspace) and ensure the following configuration is present:
"configurations": [
  {
    "name": "(gdb) nimsuggest",
    "type": "cppdbg",
    "request": "launch",
    "program": "${workspaceFolder}/bin/nimsuggest",
    "args": ["--stdin", "--find", "--debug", "--backend:js", "~/Development/nim/vscode-nim/src/nimvscode.nim"],
    "stopAtEntry": false,
    "cwd": "${workspaceFolder}",
    "environment": [],
    "externalConsole": false,
    "MIMode": "gdb",
    "miDebuggerPath": "nim-gdb",
    "setupCommands": [
      {
        "description": "Enable pretty-printing for gdb",
        "text": "-enable-pretty-printing",
        "ignoreFailures": true
      }
    ]
  }
]

A few notes:

I'm using choosenim so nim-gdb is broken
workaround: create a dir tools and symlink under ~/.nimble
symlink tools/nim-gdb.py to ~/.nimble/tools/nim-gdb.py
I compiled nimsuggest with: ./koch nimsuggest --debuginfo --linedir:on -u:release -u:danger -d:debug --debugger:native, but the temp one is a better idea

Breakpoints work and most variable value formatting works. There are cases where nim-gdb.py formatters don't seem to handle things well, in my case after a while ConfigRef breaks (no longer displays children). I'm new to gdb, lldb, and co so I haven't had really dug in, but for the curious you can see full details of what's being sent back and forth by adding the following to the configuration above (it should be a sibling to name, type, request, program, ...):
{
  "name": "(gdb) nimsuggest",
  "...": "... all the previous config ...",

  "logging": {
    "engineLogging": true,
    "trace": true,
    "traceResponse": true
  }
}


[New API] : School & College Api

🎯 Title and Issue Number

Closes #337
[New API] : School & College Api
🗒 Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x]  I have gone through rules of when PR will get merged.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have followed proper file structure.
[x] I have gone through CONTRIBUTING GUIDELINES.md.

Output

Thank you for contributing!❤
Don't forget to show some love by ⭐ the repository!

Hey @sivaprasath2004, Thank you for creating PR! We will review it super soon. 😇❣
As we continue to evolve and innovate, we encourage you to share your ideas, feedback, and code to help us push the boundaries of what's possible in the world of APIs🚀.
We hope you have followed CONTRIBUTING GUIDELINES.
Thank you for being an essential part of our community. Together, we'll keep building amazing things!
Don’t forget to ⭐ our repository!
Happy Coding!✨
Will See you soon❣

@dishamodi0910 ,please merge this..

@dishamodi0910 please merge this...

@dishamodi0910 please assign me..

@dishamodi0910 kindly merge the pr

@sivaprasath2004 We're thrilled to inform you that your pull request has been successfully merged into the APIverse🚀🎁
Your hard work, dedication, and expertise have made a significant impact on our project, and we couldn't be more grateful for your contributions.😇
Your code will now be a part of our growing ecosystem, helping developers worldwide to create exceptional APIs.❣🔥
Happy Coding! ✨
Will See you soon❣


docs: submit a argo workflow executor plugin

Please do not open a pull request until you have checked ALL of these:

[x] Create the PR as draft .
[x] Run make pre-commit -B to fix codegen and lint problems.
[x] Sign-off your commits (otherwise the DCO check will fail).

[x] "Fixes #" is in both the PR title (for release notes) and this description (to automatically link and close the issue).
[x] Add unit or e2e tests. Say how you tested your changes. If you changed the UI, attach screenshots.
[x] Github checks are green.
[x] Once required tests have passed, mark your PR "Ready for review".

If changes were requested, and you've made them, dismiss the review to get it reviewed again.

Any progress on this PR? I believe the build failures have nothing about the changes.


Help with defining the RBAC needed for Publishing to be succesful

Describe the bug
We need to define the minimal RBAC needed in Azure to complete a publishing action for bots for all configurations.  Such as: QnA Maker, LUIS , ComosDB, etc.  This way we can document out the minimum requirements in Azure and include this guidance in the Admin Handoff pattern.

@Dewain27 I reviewed all the methods called through azurePublish.  Below I listed the type of activity (heading 1), the client SDK class we use (heading 2) and the methods we call.  For each method, I listed my best guess at the permissions required.  There are not specific permissions required for any of the Azure SDK methods in the Azure docs, so I mapped them against the descriptions of Owner, Contributor, and Reader.
We can probably document the following generalized expectations:

For running the provisioning UI, the user will need to be in the tenant and have reader role on the subscription.  Any user that is specifically denied reader role on a specific resource won't be able to see it.
For provisioning, the user will need contributor role for the subscription.  If the resource group is already created, then they need contributor role on the group if they don't have it on the subscription.
For deploying, the user will need contributor role on the specific resources that are updated.  The include the web app, bot channel, and key vault.  The user may also need contributor access on the web app for uploading the zip contents.

Azure Publish UI
SubscriptionClient
subscriptions.list => Reader (Subscription)
ResourceManagementClient
resourceGroups.list => Reader (Subscription)
resources.listByResourceGroup => Reader (Subscription)
providers.get  => Reader (Subscription)
AzureBotService
bots.getCheckNameAvailability => Reader (general)
WebSiteManagementClient
checkNameAvailability => Account
CognitiveServicesManagementClient
checkSkuAvailability => Reader (Subscription)
Provision Resource Group
ResourceManagementClient
resourceGroups.checkExistence => Reader (Subscription)
resourceGroups.get  => Reader (Subscription | specific group)
resourceGroups.createOrUpdate => Contributor (Subscription)
Provision LUIS
CognitiveServicesManagementClient
accounts.create => Contributor (Subscription)
accounts.listKeys => Reader (Subscription | specific CS account)
Provision QnA
CognitiveServicesManagementClient
accounts.create => Contributor (Subscription)
accounts.listKeys => Reader (Subscription | specific CS account)
WebSiteManagementClient
appServicePlans.createOrUpdate => Contributor (Subscription)
webApps.createOrUpdate => Contributor (Subscription)
SearchManagementClient
services.createOrUpdate => Contributor (Subscription)
adminKeys.get => Reader (Subscription)
Provision Cosmos DB
CosmosDBManagementClient
databaseAccounts.createOrUpdate  => Contributor (Subscription)
sqlResources.createUpdateSqlDatabase => Contributor (Subscription)
sqlResources.createUpdateSqlContainer => Contributor (Subscription)
databaseAccounts.listKeys => Reader (Subscription | specific db)
Provision Blob Storage
StorageManagementClient
storageAccounts.create  => Contributor (Subscription)
storageAccounts.listKeys => Reader (Subscription | specific storage)
Provision App Insights
ApplicationInsightsManagementClient
components.createOrUpdate  => Contributor (Subscription)
components.get => Reader (Subscription | specific app insights)
Provision Azure Web App
WebSiteManagementClient
appServicePlans.createOrUpdate  => Contributor (Subscription)
webApps.createOrUpdate => Contributor (Subscription | specific web app)
Provision Azure Functions
WebSiteManagementClient
appServicePlans.createOrUpdate  => Contributor (Subscription)
Provision Bot Service
AzureBotService
bots.create  => Contributor (Subscription)
Provision Connect App Insights to Bot Service
AzureBotService
bots.get => Reader (Subscription | specific bot)
bots.update => Contributor (specific bot)
Deploy
AzureBotService
bots.get => Reader (Subscription | specific bot)
bots.update => Contributor (specific bot)
WebSiteManagementClient
webApps.update => Contributor (specific web app)
webApps.get => Reader (Subscription | specific web app)
webApps.updateApplicationSettings => Contributor (specific web app)
KeyVaultManagementClient
vaults.update => Contributor (specific key vault resource)
secrets.get => Reader (specific key vault resource)


Number.isIntege is not working in IE 10

I found the code in pixijs
InteractionData.prototype.copyEvent = function copyEvent(event) {         // isPrimary should only change on touchstart/pointerdown, so we don't want to overwrite         // it with "false" on later events when our shim for it on touch events might not be         // accurate         if (event.isPrimary) {           this.isPrimary = true;         }         this.button = event.button;         // event.buttons is not available in all browsers (ie. Safari), but it does have a non-standard         // event.which property instead, which conveys the same information.         this.buttons = Number.isInteger(event.buttons) ? event.buttons : event.which;         this.width = event.width;         this.height = event.height;         this.tiltX = event.tiltX;         this.tiltY = event.tiltY;         this.pointerType = event.pointerType;         this.pressure = event.pressure;         this.rotationAngle = event.rotationAngle;         this.twist = event.twist || 0;         this.tangentialPressure = event.tangentialPressure || 0;       };
I suggest to add below code to fix the PIXIJS 4.7.1 not working in IE 10
Number.isInteger = Number.isInteger || function(value) {
  return typeof value === 'number' &&
    isFinite(value) &&
    Math.floor(value) === value;
};

This is already fixed on the latest dev branch. Sorry about the inconvenience, my mistake for this being there :/

Closing because this is fixed in dev, but good workaround for people bumping into 4.7.1 issue to include that polyfill.


Netty is hanging inside AWS Lambda

Which version of the client library are you using?
The latest 13.0.0 and the v8 for the resources
Which version of Java are you using?
Java 11
Which operating system (Linux, Windows, ...) and version?
AWS Linux Distro and MacOSx as local
Actions taken
Using the provided examples, I have tried to run them locally first and then run them inside an AWS Lambda.
Expected result
Is that both local and AWS will provide the same results.
Actual result
Locally the code is executed correctly. On AWS, the code freezes on googleAdsServiceClient.search(request) due to some netty malfunction.
The pom dependencies are:
<dependencies>
        <dependency>
            <groupId>com.google.api-ads</groupId>
            <artifactId>google-ads</artifactId>
            <version>13.0.0</version>
        </dependency>
        <dependency>
            <groupId>com.amazonaws</groupId>
            <artifactId>aws-lambda-java-core</artifactId>
            <version>1.2.1</version>
        </dependency>
        <dependency>
            <groupId>com.amazonaws</groupId>
            <artifactId>aws-lambda-java-events</artifactId>
            <version>3.9.0</version>
        </dependency>
        <dependency>
            <groupId>software.amazon.awssdk</groupId>
            <artifactId>secretsmanager</artifactId>
            <version>2.16.89</version>
        </dependency>
        <dependency>
            <artifactId>apache-client</artifactId>
            <groupId>software.amazon.awssdk</groupId>
            <version>2.16.89</version>
        </dependency>
</dependencies>

AWS Stacktrace:
remote stacktrace.txt
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See troubleshooting for how to diagnose problems better.
Anything else we should know about your project / environment
AWS Lambda, with 512 RAM

I tried to replicate this on AWS but was unable to. My guess would be that you have a dependency conflict, but with the limited set of dependnecies posted above I can't see where that would come from.
Could you put together a minimum failing example that I could debug?

Actually, thinking about it, this is possibly being caused by the OAuth credentials being invalid. Could you check that valid credentials that are being loaded on AWS?

@nwbirnie This the minimum required set of dependencies so that we can have an AWS Java runtime with Lambda using the Google Ads API.
The actual problem was that the the SSL connection could not handshake in order to be able to start sending messages.
Actually there is a dependency excluded from the shaded JAR during the SAM packaging process. When the following dependency was added,
<dependency>
    <groupId>io.perfmark</groupId>
    <artifactId>perfmark-api</artifactId>
    <version>0.24.0</version>
</dependency>

then the SSL connection was successful and the Lambda was getting Google Ads data.

Nice, thanks for posting the solution and glad to hear you got it fixed.


feat(batch): enable parallel table scan

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
We will not maintain the order of select from an MV with ORDER BY clause now. https://github.com/singularity-data/risingwave/pull/3668#issuecomment-1175217821
Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

SQL commands, functions, and operators

Release note
Select from an MV with ORDER BY clause may return unordered results.
Refer to a related PR or issue link (optional)
close https://github.com/singularity-data/risingwave/issues/3583
close https://github.com/singularity-data/risingwave/issues/3237

@xxchan Could you please explain the release note part ? It sounds like a limitation. Does this mean that this PR resolves the issue (order by statements return unordered results)? Thanks.

@xxchan Could you please explain the release note part ? It sounds like a limitation. Does this mean that this PR resolves the issue (order by statements return unordered results)? Thanks.

The problem is described here https://singularity-data.slack.com/archives/C036F5Z3EMD/p1657075038333919


Can't develop TensorBoard under macOS

I read DEVELOPMENT.md
After npm run prepare finished, gulp come up with error:

[23:42:32] Using gulpfile ~/Desktop/Going/tensorflow-master/tensorflow/tensorboard/gulpfile.js
(node:20770) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[23:42:32] Starting 'watch'...
[23:42:32] Finished 'watch' after 129 ms
[23:42:32] Starting 'first-compile'...
[23:42:41] Finished 'first-compile' after 9.16 s
[23:42:41] Starting 'server'...
[23:42:41] Finished 'server' after 17 ms
[23:42:41] Starting 'default'...
[23:42:41] Finished 'default' after 18 μs
[23:42:41] Webserver started at http://<IP_ADDRESS>:8000
2016-12-15 23:42 gulp[20770] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:160
throw er; // Unhandled 'error' event
^
Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:1022:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1282:11)

macOS 10.12.1
➜  tensorboard gulp -v
[23:44:58] CLI version 3.9.1
[23:44:58] Local version 3.9.1
➜  tensorboard node -v
v7.2.1
➜  tensorboard npm -v
3.10.10
➜  tensorboard bower -v
1.8.0

Due to the great efforts of @jart, you no longer need gulp, bower, or any of their co-conspirators to develop or run TensorBoard! Perhaps try again using our new repository at https://github.com/tensorflow/tensorboard/blob/master/README.md?