Do not set default_mimetype in finalize() - Slim 4.x

Closes #2284
[Unrelated] Removed an unused namespace reference.
Note: If merged a separate PR should be created to document this requirement.

Coverage decreased (-0.008%) to 94.94% when pulling 7d9f2264b23e786fa40428a08c8257f8a6150fe1 on RyanNerd:do-not-set-default_mimetype-in-finalize into 13065707e9fc5a45b6b8a69b2994f60921c6fcfb on slimphp:4.x.


Ollama Function Calling

Resolves #50
More in-depth testing incoming

We should also add docs about this

Did some manual testing with different models also added a few more tests to tests/function_calling.rs.
An example run with finance tool + nous hermes 2:
> What are the current risk factors to $APPL?
[2024-05-20T00:01:32Z INFO  ollama_rs::generation::functions] Function call: To provide you with an analysis of the current risk factors for Apple Inc. (AAPL), I will use the "Stock Scraper" tool from the provided functions. This tool allows me to scrape stock information from Google Finance, including potential risk factors. Please bear with me as I gather this data.

    <tool_call>
    {"arguments": {"exchange": "NASDAQ", "ticker": "AAPL"}, "name": "Stock Scraper"}
    </tool_call>

[2024-05-20T00:01:33Z INFO  ollama_rs::generation::functions] Parsing done
<tool_response>
{"Market cap":"2.91T USD","Avg Volume":"63.51M","Dividend yield":"0.53%","CEO":"Tim Cook","Primary exchange":"NASDAQ","Founded":"Apr 1, 1976","Year range":"$164.08 - $199.62","Previous close":"$189.84","Website":"apple.com","P/E ratio":"29.53","Headquarters":"Cupertino, CaliforniaUnited States","Employees":"161,000","Day range":"$189.18 - $190.81"}
</tool_response>

I tried to stick to the original design of ollama-rs as much as possible, and keep the recursive-looping agentic functionality excluded from this repo. Both send_function_call and send_function_call_with_history handle function calling, with the latter storing a history of tool calls.
Function calling is crucial for agentic frameworks such as ReAct (Reason + Action), but it would introduce unnecessary overhead to ollama-rs. I would probably implement it in langchain-rust or a crewAI-like Rust doppelganger. One can use responses from function calls to "Reason" over the observations done through "tools" implemented within the library.

@pepperoni21 my bad, added cargo fmt -all + cargo clippy to build. Should be ok now

Looks very good! I'll run the tests when I'm home 👍

@pepperoni21 any estimates on when we can merge this?


doc: fix missed package name

Fix midded package name of SpanCustomizingHandlerInterceptor in the README.md

thanks!


Add a basic man page

This is very much a work in progress.  Here are the issues I'm aware of:

The output is going to the build dir.  I think it fits best in doc
The "About" string describes the cascade language, not the casc compiler.  I think it's just read out of the Cargo.toml.  This is a problem for casc --help as well.
There is no custom information in the man page at this point.  A longer description would probably be helpful

@l0kod as we discussed offline last week, it would be nice to release a 0.0.2 prior to LSS this week so we have all the recent work in a release.  I would consider this a "nice to have" for that, but I also want to get it into good shape before including it, and I'm not sure whether that fits into this week.  Any thoughts on any of the above?

Rebased and addressing item @2 above.  Items 1 and 3 are still outstanding.
In terms of item 1, I'm struggling to determine rust best practices in terms of man page output location.  I've done some googling around crates.io and manpages, with no success.  I found this discussion which seems highly inconclusive about what users generating man pages should actually do with them: https://github.com/rust-cli/man/issues/33.  I think my initial take is that maybe the build dir is sensible for now.  It seems like the most reasonable default.  If we can determine what best practices exist, and how to best integrate with crates.io, distro packagers etc, then we can move it if needed.


[Rust] target any directory (not just root)

Allow target to be ignored when the Cargo dir is not the root of the repo
Reasons for making this change:
The current version only works if the rust folder is the root of a repository

The current version only works if the rust folder is the root of a repository

@j-campbell should we just update that then to drop the first / and make it work for nested projects?
cc @schnoddelbotz @waynenilsen @deepak @cnd who have contributed to the template before for their thoughts

It would probably be best to try to be consistent with whatever cargo new is doing. I do think this makes sense for workspaces as well. The only reason that cargo new wouldn't just use target/ is because of the footgun of some directory like **/src/**/target/ getting ignored accidentally. This is entirely possible. Perhaps add a negation rule as well to include these sources. This could end up being a PR to cargo as well I would think.

I'm agreed with the change.

@j-campbell does the feedback from @waynenilsen make sense here?

Not allowing the target folder to be tracked by default would solve this problem? As @waynenilson said there are a few situations where cargo not being the root folder comes up.

I'm not sure where we ended up with this - can we close this out unless we've come to a consensus about what changes we should make?

Closing this out as we don't seem to have reached a consensus here.
@j-campbell feel free to open a fresh PR if this is something you still care about.


initial commit

@yilunzhang @dreamfly281

@dreamfly281 I tested pub/sub from js client and wallet and everything works properly


Update blog contains incubator-shenyu changed to shenyu(#1039)

@damonxue How do I find community developer wechat groups?

pls add my wechat: Fibonacci_stack


Dissociate is disable.

What to do and why when dissociate is disabled.
I add created a vnet for webabb integration with a gateway (now classic) and now I want to deleted because I want to use the regional vnet integration instead. But gives me errors because of the ip associated that I can't dissociate. Can you point out what is missing in this cases?
I also request a support ticket for this.

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

ID: 19d6d70c-eed7-8fdc-e04b-995cabf0a902
Version Independent ID: a33391e9-3023-8212-6246-d64071efc2b5
Content: Create, change, or delete an Azure public IP address
Content Source: articles/virtual-network/virtual-network-public-ip-address.md
Service: virtual-network
GitHub Login: @KumudD
Microsoft Alias: kumud

@ftereso I understand that you want to delete the Public IP off of your VPN Gateway. Unfortunately a Public IP is required on a VPN Gateway. You will need to delete the VPN Gateway first, then delete the Public IP.

In order to to delete the vnet you should first delete the gateway. This will remove the association to the ip.
My following steps were then delete the subnet, vnet and public ip

@ftereso do you still need assistance with this?

@ftereso We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Is this repository maintained by elastic at all?

Has elastic abandoned this repository?

You can't expect anyone to make an effort to contribute if they can't even expect anything to be upstreamed.

We're working towards adding proper async support to the elasticsearch package rather than packaging them seperately.
See: https://github.com/elastic/elasticsearch-py/pull/1203

Thanks for directing me to that @sethmlarson !  That's a recent PR too!  Very excited to see that.


Azure Connected Machine Agent failed to upgrade - MainEngineThread is returning 1603

We have one Windows 2012 Server that currently running with Azure Connected Machine Agent v1.37. It has failed upgrading to v1.40 or v1.42. The msi log only showing few lines with 1603 error. Does anyone has any experience and what should I do to fix it?

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

ID: 7fa48880-0b59-48c1-8f28-ae479e7be559
Version Independent ID: 8f513f59-0396-8d02-ee44-ef28a6ae67e3
Content: Managing the Azure Connected Machine agent - Azure Arc
Content Source: articles/azure-arc/servers/manage-agent.md
Service: azure-arc
Sub-service: azure-arc-servers
GitHub Login: @johnmarco
Microsoft Alias: johnmarc

@silverong
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

@silverong It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

Hi, I am following this link https://learn.microsoft.com/en-us/azure/azure-arc/servers/manage-agent?tabs=windows. Basically just download the agent MSI and run it. I have double click to run the MSI but it disappear in fee secs without error. Hence I use msiexec command to run it and generating verbose log, it only contains 1603.

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

@silveron, Based on the timestamps in the log screenshot, the installer exits right after getting launched. You could try the following to see if it helps:

Install from an elevated cmd prompt manually using the steps here - To upgrade from the command line. Review the logs getting created in C:\Support\Logs folder or any other location as specified in the cmdline. Also review the Application, System, setup logs in EventViewer around this time to see if that contains error causing it to fail.
Also, please review the following doc for arc agent logs and common scenarios - Troubleshoot Azure Connected Machine agent connection issues

In case they don't help, I would advice reaching out to Microsoft Q&A for help or filing a Azure support ticket.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation, therefore closing this issue. Thank you for your co-operation.


Godot failed to compile on an ARM Chromebook (Internal Error that said to report it)

Godot version
3.x branch
System information
Chrome OS,
MediaTek MT8183C 8 Core ARM Cortex-A73 CPU,
4GB Memory,
Model is Acer Chromebook Spin 311 CP311-3H-K3WL,
Issue description
Godot failed to compile on an ARM Chromebook, and the log said to report it. See below for details, thanks in advance!
Steps to reproduce
In my terminal:
git clone https://github.com/godotengine/godot.git
cd godot
git checkout 3.x
scons -j4 platform=x11 target=release_debug use_lto=yes

Minimal reproduction project
Error log:
scons: Reading SConscript files ...
Enabling ALSA
Enabling PulseAudio
Enabling udev support
Checking for C header file mntent.h... (cached) yes
scons: done reading SConscript files.
scons: Building targets ...
[Initial build] Compiling ==> editor/editor_fonts.cpp
[Initial build] Compiling ==> editor/editor_node.cpp
[Initial build] Compiling ==> editor/editor_run.cpp
[Initial build] Compiling ==> editor/editor_run_native.cpp
[Initial build] Compiling ==> editor/editor_run_script.cpp
[Initial build] Compiling ==> editor/editor_scale.cpp
[Initial build] Compiling ==> editor/editor_sectioned_inspector.cpp
[Initial build] make_translations_header(["editor/translations.gen.h"], ["editor/translations/af.po", "editor/translations/ar.po", "editor/translations/az.po", "editor/translations/bg.po", "editor/translations/bn.po", "editor/translations/br.po", "editor/translations/ca.po", "editor/translations/cs.po", "editor/translations/da.po", "editor/translations/de.po", "editor/translations/el.po", "editor/translations/eo.po", "editor/translations/es.po", "editor/translations/es_AR.po", "editor/translations/et.po", "editor/translations/eu.po", "editor/translations/fa.po", "editor/translations/fi.po", "editor/translations/fil.po", "editor/translations/fr.po", "editor/translations/ga.po", "editor/translations/gl.po", "editor/translations/he.po", "editor/translations/hi.po", "editor/translations/hr.po", "editor/translations/hu.po", "editor/translations/id.po", "editor/translations/is.po", "editor/translations/it.po", "editor/translations/ja.po", "editor/translations/ka.po", "editor/translations/km.po", "editor/translations/ko.po", "editor/translations/lt.po", "editor/translations/lv.po", "editor/translations/mi.po", "editor/translations/mk.po", "editor/translations/ml.po", "editor/translations/mr.po", "editor/translations/ms.po", "editor/translations/nb.po", "editor/translations/nl.po", "editor/translations/or.po", "editor/translations/pl.po", "editor/translations/pr.po", "editor/translations/pt.po", "editor/translations/pt_BR.po", "editor/translations/ro.po", "editor/translations/ru.po", "editor/translations/si.po", "editor/translations/sk.po", "editor/translations/sl.po", "editor/translations/sq.po", "editor/translations/sr_Cyrl.po", "editor/translations/sr_Latn.po", "editor/translations/sv.po", "editor/translations/ta.po", "editor/translations/te.po", "editor/translations/th.po", "editor/translations/tr.po", "editor/translations/tt.po", "editor/translations/tzm.po", "editor/translations/uk.po", "editor/translations/ur_PK.po", "editor/translations/vi.po", "editor/translations/zh_CN.po", "editor/translations/zh_HK.po", "editor/translations/zh_TW.po"])
[Initial build] Compiling ==> editor/editor_spin_slider.cpp
[Initial build] Compiling ==> editor/editor_settings.cpp
[Initial build] Compiling ==> editor/editor_sub_scene.cpp
{standard input}: Assembler messages:
{standard input}:233324: Warning: end of file not at end of a line; newline inserted
{standard input}:233325: Warning: unterminated string; newline inserted
{standard input}:233326: Internal error in stringer at ../../gas/read.c:5366.
Please report this bug.
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
scons: *** [editor/editor_fonts.x11.opt.tools.64.o] Error 1
scons: building terminated because of errors.

I then tried compiling with flag "-j2" which compiled fine but then at the very bottom, linking failed.
Here is the error in question:
[Initial build] Compiling ==> core/bind/core_bind.cpp
[Initial build] progress_finish(["progress_finish"], [])
[Initial build] Linking Static Library ==> core/libcore.x11.opt.tools.64.a
[Initial build] Ranlib Library         ==> core/libcore.x11.opt.tools.64.a
[Initial build] Linking Program        ==> bin/godot.x11.opt.tools.64
thirdparty/minimp3/minimp3_ex.h:87:3: note: type 'mp3d_sample_t' should match type 'mp3d_sample_t'
 } mp3dec_ex_t;
   ^
modules/minimp3/audio_stream_mp3.h:42:2: warning: 'get_class' violates the C++ One Definition Rule  [-Wodr]
  GDCLASS(AudioStreamPlaybackMP3, AudioStreamPlaybackResampled);
  ^
modules/minimp3/audio_stream_mp3.h:42:2: note: 'get_class' was previously declared here
  GDCLASS(AudioStreamPlaybackMP3, AudioStreamPlaybackResampled);
  ^
g++: fatal error: Killed signal terminated program lto1
compilation terminated.
lto-wrapper: fatal error: g++ returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
scons: *** [bin/godot.x11.opt.tools.64] Error 1
scons: building terminated because of errors.

Here is the full error log:
scons: Reading SConscript files ...
Enabling ALSA
Enabling PulseAudio
Enabling udev support
Checking for C header file mntent.h... (cached) yes
scons: done reading SConscript files.
scons: Building targets ...

It probably fails because you don't have enough RAM to build with LTO. You should not pass use_lto=yes on this hardware.

Try using LLVM with LTO (use_llvm=yes flag), 4 GB should be enough for it. GCC LTO uses about 11 GB for master and 7 GB for 3.2.

Thank you for the response! Forgot to mention I tried increasing the swap memory by 4GB so it theoretically had 8GB total, but guess that didn't work. Will let you know how it goes.

Ok, I tried running only scons -j8 platform=x11 target=release_debug
which gave an error where somewhere in its compilation, it generated what looks like a RISC command that wasn't memory aligned (I assume), not sure if that's a problem with my computer:
...
[ 26%] Compiling ==> modules/gdscript/language_server/gdscript_text_document.cpp
{standard input}: Assembler messages:
{standard input}:31812: Warning: end of file not at end of a line; newline inserted
{standard input}:32999: Error: immediate value must be a multiple of 8 at operand 3 -- `ldp x29,x30,[sp],4'
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
scons: *** [modules/gdscript/gdscript_function.x11.opt.tools.64.o] Error 1
scons: building terminated because of errors.

Does it work if you pass module_libvpx_enabled=no on the SCons command line?

Not sure, I'll try it now.

@Calinou Looks like it didn't, ran scons -j8 platform=x11 target=release_debug module_webm_enabled=no:
[ 26%] Compiling ==> modules/gdscript/language_server/gdscript_text_document.cpp
{standard input}: Assembler messages:
{standard input}:31812: Warning: end of file not at end of a line; newline inserted
{standard input}:32999: Error: immediate value must be a multiple of 8 at operand 3 -- `ldp x29,x30,[sp],4'
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
scons: *** [modules/gdscript/gdscript_function.x11.opt.tools.64.o] Error 1
scons: building terminated because of errors.

BTW, since nobody mentioned it, the "please report" message is from the compiler, not Godot, so technically it asks you to report the bug to GCC. Not sure if it is actually a compiler bug or not. I don't think many people are building X11 on ARM, so it might be something in the buildsystem.

I did try using LLVM without LTO, ie: scons -j8 platform=x11 target=release_debug use_lto=yes

This command builds with LTO and GCC, not with LLVM. You should use scons -j8 platform=x11 target=release_debug use_llvm=yes instead.

Oh whoops! Slipped my eyes when I was copying commands over. It finally worked without LTO and LLVM, thanks!


Cursor option to pre-process results

Hi,
Is there a way to say to pass a function to the #find method to "pre-process" returned documents?
I'd need to convert the result documents to my own Javascript object instead of having them as a standard Object created fron JSON.
Thank you.

Not at the moment. You can always create your own wrapper around find(). Or use mongoose :) mongoskin is meant to be more lightweight and so this feature might be overkill.


Support optional "teardown" script to run before kexec

A new zfsbootmenu_teardown dracut option has been added to module-init.sh that, when set to a path that refers to an executable, will install the named executable as /libexec/zfsbootmenu-teardown in the initramfs. In kexec_kernel, if /libexec/zfsbootmenu-teardown is found to exist and be executable, the script will be run immediately before the final kexec call to jump into the new kernel.
On my 2015 "VoidBook Air", the system keyboard, trackpad and bluetooth controller are connected to the XHCI USB hub. These devices are fully functional in ZBM, but when I boot the final kernel,  I can see the hub but not the peripherals. With the following teardown hook:
#!/bin/sh

SYS_XHCI=/sys/bus/pci/drivers/xhci_hcd

for DEVPATH in ${SYS_XHCI}/????:??:??.?; do
	[ -L "${DEVPATH}" ] || continue
	DEVICE="${DEVPATH#${SYS_XHCI}/}"
	echo "Tearing down USB controller ${DEVICE}..."
	echo "${DEVICE}" > ${SYS_XHCI}/unbind
done

I can unbind the XHCI device from the driver, which allows the final kernel to properly initialize the device and my peripherals to function.
I suspect there are a few use cases like this where a teardown script will be useful to ease the kexec transition. The script is not intended to interact with any ZFS pools or filesystems, so is executed at the last possible moment (specifically, after the pool is exported.)

The XHCI teardown script has been added to contrib/.

On 2020-12-07 at 20:15 (UTC -0500), Zach Dykstra wrote:

@zdykstra requested changes on this pull request.
Very clean/user-expandable solution here. It might be nice to document
this mechanism in zfsbootmenu.7 under a new section, and to update
the Makefile to copy these to /usr/share/examples/zfsbootmenu/contrib.

I incorporated your requests. Not seeing a need for another level in the
hierarchy, I left out the contrib subdirectory in the examples tree.
If you object, I will put it in the subdirectory.


Error when importing Pouchdb

Hello,
I'm trying to use Pouchdb with this boilerplate, however, whenever I add import PouchDB from 'pouchdb'; anywhere, I immediately get the following error:
WARNING in ./~/levelup/lib/util.js [0] Module not found: Error: Cannot resolve module 'leveldown/package' in /home/samir/Sites/school/node_modules/levelup/lib [0]  @ ./~/levelup/lib/util.js 36:23-51 [0]  [0] WARNING in ./~/bindings/bindings.js [0] Critical dependencies: [0] 76:22-40 the request of a dependency is an expression [0] 76:43-53 the request of a dependency is an expression [0]  @ ./~/bindings/bindings.js 76:22-40 76:43-53 [0]  [0] WARNING in ./~/bindings/README.md [0] Module parse failed: /home/samir/Sites/school/node_modules/bindings/README.md Unexpected token (2:3) [0] You may need an appropriate loader to handle this file type. [0] SyntaxError: Unexpected token (2:3) [0]     at Parser.pp.raise (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:923:13) [0]     at Parser.pp.unexpected (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:1490:8) [0]     at Parser.pp.parseExprAtom (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:333:12) [0]     at Parser.pp.parseExprSubscripts (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:228:19) [0]     at Parser.pp.parseMaybeUnary (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:207:17) [0]     at Parser.pp.parseExprOp (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:174:41) [0]     at Parser.pp.parseExprOp (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:176:19) [0]     at Parser.pp.parseExprOps (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:156:15) [0]     at Parser.pp.parseMaybeConditional (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:136:19) [0]     at Parser.pp.parseMaybeAssign (/home/samir/Sites/school/node_modules/webpack/node_modules/acorn/dist/acorn.js:112:19) [0]  @ ./~/bindings ^\.\/.*$
And the app devtools shows the following: validate.js?c7dd:17Uncaught Error: define cannot be used indirect
After a long search I stumbled on the following https://github.com/pouchdb/pouchdb/issues/3647 but unfortunately the suggested solution does not work for me.
How do I fix this?
I'm pretty much useless when it comes to Webpack, hence the question.
Thank you, and good evening

You need to edit webpack.config.base.js:
...
  resolve: {
    extensions: ['', '.js', '.jsx', '.json'],  // <- Add `.json`, see levelup/lib/util.js#L36
...
  externals: [
    'leveldown'  // <- Add here
  ]
...

The levelup/lib/util.js is required leveldown/package instead of leveldown/package.json, so you need add .json extension. The leveldown package is a native module, it must avoid built, so you need add it to externals.

Hello again,
Tried your approach, I'm still encoutering the same error: validate.js?c7dd:17Uncaught Error: define cannot be used indirect
The terminal however shows a clean bundle this time.
My webpack.config.base.js
import path from 'path';

export default {
  module: {
    loaders: [{
      test: /\.jsx?$/,
      loaders: ['babel-loader'],
      exclude: /node_modules/
    }, {
      test: /\.json$/,
      loader: 'json-loader'
    }],
    noParse: /lie\.js$|\/leveldown\//
  },
  output: {
    path: path.join(__dirname, 'dist'),
    filename: 'bundle.js',
    libraryTarget: 'commonjs2'
  },
  resolve: {
    extensions: ['', '.js', '.jsx', '.json'],
    packageMains: ['webpack', 'browser', 'web', 'browserify', ['jam', 'main'], 'main']
  },
  plugins: [

  ],
  externals: [
    // put your node 3rd party libraries which can't be built with webpack here
    // (mysql, mongodb, and so on..)
    'leveldown'
  ]
};

Thank you for sharing this!

Now I got this error
api.js?dffc:9 Error: ReferenceError: leveldown is not defined: unable to import leveldown
    at requireLeveldown (eval at <anonymous> (http://localhost:8080/app.js:1872:2), <anonymous>:4994:12)
    at PouchDB.LevelDownPouch (eval at <anonymous> (http://localhost:8080/app.js:1872:2), <anonymous>:5006:17)
    at eval (eval at <anonymous> (http://localhost:8080/app.js:1872:2), <anonymous>:2728:36)
    at new PouchDB (eval at <anonymous> (http://localhost:8080/app.js:1872:2), <anonymous>:2659:17)
    at eval (eval at <anonymous> (http://localhost:8080/app.js:2136:2), <anonymous>:13:15)
    at Object.<anonymous> (http://localhost:8080/app.js:2136:2)
    at __webpack_require__ (http://localhost:8080/app.js:518:30)
    at fn (http://localhost:8080/app.js:49:20)
    at eval (eval at <anonymous> (http://localhost:8080/app.js:2142:2), <anonymous>:7:12)
    at Object.<anonymous> (http://localhost:8080/app.js:2142:2)

@rdpascua The answer from @Unforgiven-wanda might help you.
After wasting a lot of time with leveldown and problems with multiple windows we ended up switching to pouchdb-browser, which runs entirely inside the browser window, not main.js.

might as well try pouchdb-browser


CUDA Dispatcher refactor

This PR moves classes around in the CUDA target to better mirror the structure of the CPU target and core of Numba (see #7739)
Fixes #7739.

gpuci run tests

gpuci run tests

gpuci run tests

Buildfarm ID: numba_smoketest_cuda_yaml_115.

Buildfarm ID: numba_smoketest_cuda_yaml_115.

Passed.


Solution of 1DCA does not work for CARules > 127

Solution: Int8 should be replaced by uint8

Solved in #38


Library not found for libPods-TwilioVideo-VideoQuickStart.a

I successfully updated twilio pod and installed it:
pod repo update twilio
pod install
but when I try to build from within XCode, I get the following missing library:
Library not found for -lPods-TwilioVideo-VideoQuickStart
Linker command failed with exit code 1 (use -v to see invocation)
Thanks, Jose

Hi @jannunzi,
Are you still running into this issue? It sounds like you tried to build from the Xcode project rather than the workspace after running pod install.
Best,
Chris

Hi @jannunzi,
Hopefully you were able to get up and running via Cocoapods. Please re-open if you are still having any issues with your dev setup.
Cheers,
Chris

Hi @jannunzi
I am facing the same issues, it builds fine and runs fine locally but when I try to archive it I get the same error, installed via pod file
this is my pod file

source 'https://github.com/CocoaPods/Specs'
abstract_target 'TwilioVideo' do
pod 'TwilioVideo', '~> 3.2'
target 'projectname' do
platform :ios, '11.0'
project 'projectname.xcproject'
end
end

ld: library not found for -lPods-TwilioVideo-projectname
clang: error: linker command failed with exit code 1 (use -v to see invocation)
I used the .xcworkspace file to open build & archive via xcode. Let me know if you need additional details.


Missing Macro

Hey,
Amazing module. Ray of Enfeeblement has the following error: "No macro found"

noted, thanks fro the catch


Question: why not use x = restX + maxX*sin(sqrt(k/m)+sqrt(k/m)

why not caculate position using x = restX + maxX*sin(sqrt(k/m)+sqrt(k/m)? It only relate to t,you may not use a fixed frame time.

Didn't have time to look at this. Why is this closed? (Also, we used some logic to make sure we loop the correct amount of times even with a fixed frame time)


[PE-D][Tester E] entering ssort does not show entire list after list is filtered, unless slist is called

Perhaps it would be a good implementation to simple show the list (auto call slist right after) after sorting the food store list instead of having the user type slist again? After all, as a user, I would want to see the entire list after sorting.
Steps to replicate this:

sfind n/
ssort

Labels: type.FunctionalityBug severity.Low
original: ketamethane/ped#5

Thank you for the suggestion. We will definitely consider this for future versions after 1.4. However for now, this will be the intended functionality for FoodWhere.


example 'quest'

some sort of NPC lead errand resulting in XP

climb skill example covers this -- ie: joining the newbie academy


[WIP] Prevent cycle in the QueueManager

Description
This is basically based on https://github.com/apache/openwhisk/pull/5251
I just added a small change to improve the performance.
Without performance optimization.

With performance optimization.

Related issue and scope

[x] I opened an issue to propose and discuss this change (#5250)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[x] Scheduler
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[x] Bug fix (generally a non-breaking change which closes an issue).
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[x] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report

Merging #5332 (2e2e640) into master (236ca5e) will decrease coverage by 76.97%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #5332       +/-   ##
==========================================
- Coverage   81.51%   4.54%   -76.98%
==========================================
  Files         240     240
  Lines       14264   14310       +46
  Branches      598     591        -7
==========================================
- Hits        11627     650    -10977
- Misses       2637   13660    +11023

Impacted Files
Coverage Δ

...in/scala/org/apache/openwhisk/common/Logging.scala
41.66% <0.00%> (-45.12%)
:arrow_down:

.../openwhisk/core/scheduler/queue/QueueManager.scala
0.00% <0.00%> (-83.28%)
:arrow_down:

.../main/scala/org/apache/openwhisk/core/WarmUp.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ain/scala/org/apache/openwhisk/spi/SpiLoader.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/scala/org/apache/openwhisk/utils/JsHelpers.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...scala/org/apache/openwhisk/common/Prometheus.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...scala/org/apache/openwhisk/common/time/Clock.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...scala/org/apache/openwhisk/core/FeatureFlags.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ala/org/apache/openwhisk/common/ConfigMXBean.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...la/org/apache/openwhisk/http/BasicRasService.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 206 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

LGTM

I found a regression in this change.
Please do not merge this.

What is the regression?

1. Disable the scheduler
[2022-10-11T09:31:48.791Z] [WARN] [#tid_BOjlyL4vneiwdeJc422InK80fwojMF0e] [FPCSchedulerServer] Scheduler is disabled

2. Shutting down the queue manager
[2022-10-11T09:31:48.802Z] [INFO] [#tid_sid_unknown] [QueueManager] Gracefully shutdown the queue manager

3. Shutting down the queue
[2022-10-11T09:31:48.805Z] [INFO] [#tid_sid_unknown] [MemoryQueue] [guest:guest/noop0@0.0.1:Running] Gracefully shutdown the memory queue.

4. Queue endpoints are removed
[2022-10-11T09:31:48.805Z] [INFO] [#tid_sid_unknown] [WatcherService] unwatch endpoint: UnwatchEndpoint(bmt-1480/queue/guest/guest/noop0/leader,false,data-management-service,true)
[2022-10-11T09:31:48.805Z] [INFO] [#tid_sid_unknown] [WatcherService] unwatch endpoint: UnwatchEndpoint(bmt-1480/throttling/guest,false,data-management-service,true)
[2022-10-11T09:31:48.805Z] [INFO] [#tid_sid_unknown] [WatcherService] unwatch endpoint: UnwatchEndpoint(bmt-1480/throttling/guest/guest/noop0,false,data-management-service,true)
[2022-10-11T09:31:48.805Z] [INFO] [#tid_sid_unknown] [QueueManager] Remove init revision map cause queue is removed, key: bmt-1480/queue/guest/guest/noop0/leader

5. A queue is in the removing state
It's waiting for buffered activations to be handled.
[2022-10-11T09:31:48.808Z] [INFO] [#tid_sid_unknown] [MemoryQueue] [guest:guest/noop0@0.0.1:Removing] Queue is going to stop but there are still 0 activations and 17 request buffered.
[2022-10-11T09:31:48.811Z] [INFO] [#tid_sid_unknown] [MemoryQueue] [guest:guest/noop0@0.0.1:Removing] This queue is shutdown by `/disable` api, do nothing here.

5. New activation comes and it recovers the queue
In the meantime, new activation comes and it tries to recover a queue.
[2022-10-11T09:31:48.807Z] [INFO] [#tid_3168d300edca4fda4e2927be9dd35bf8] [QueueManager] Got activation message b6cec1514fa545828ec1514fa5558251 for<EMAIL_ADDRESS>from kafka.
[2022-10-11T09:31:48.807Z] [INFO] [#tid_3168d300edca4fda4e2927be9dd35bf8] [QueueManager] [b6cec1514fa545828ec1514fa5558251] the key bmt-1480/queue/guest/guest/noop0/leader is not in the initRevisionMap. revision: 15-5aa72ce8d0070b26994803ac8c22de81
[2022-10-11T09:31:48.807Z] [INFO] [#tid_85ddc3a977a53a14f6a709d503534b92] [QueueManager] Recover a queue for<EMAIL_ADDRESS>
6. All incoming activations trigger the recovery procedure
[2022-10-11T09:31:48.822Z] [INFO] [#tid_c4bc33dcb78ef6f5794af9e424d0c7c8] [QueueManager] Got activation message 77d486061de24c869486061de28c8606 for<EMAIL_ADDRESS>from remote queue manager.
[2022-10-11T09:31:48.822Z] [INFO] [#tid_c4bc33dcb78ef6f5794af9e424d0c7c8] [QueueManager] Recover a queue for<EMAIL_ADDRESS>[2022-10-11T09:31:48.823Z] [INFO] [#tid_3168d300edca4fda4e2927be9dd35bf8] [QueueManager] Got activation message b6cec1514fa545828ec1514fa5558251 for<EMAIL_ADDRESS>from remote queue manager.
[2022-10-11T09:31:48.823Z] [INFO] [#tid_3168d300edca4fda4e2927be9dd35bf8] [QueueManager] Recover a queue for<EMAIL_ADDRESS>[2022-10-11T09:31:48.823Z] [INFO] [#tid_3ab104600fa6cc0628d56b4e2c56c52d] [QueueManager] Got activation message 4864ed562a78408fa4ed562a78308f75 for<EMAIL_ADDRESS>from remote queue manager.
[2022-10-11T09:31:48.823Z] [INFO] [#tid_3ab104600fa6cc0628d56b4e2c56c52d] [QueueManager] Recover a queue for<EMAIL_ADDRESS>[2022-10-11T09:31:48.823Z] [INFO] [#tid_b4f3a44cfe6aac7fd242d03b4aa791c2] [QueueManager] Got activation message 0db275dac7b84458b275dac7b8b45842 for<EMAIL_ADDRESS>from remote queue manager.
[2022-10-11T09:31:48.823Z] [INFO] [#tid_b4f3a44cfe6aac7fd242d03b4aa791c2] [QueueManager] Recover a queue for<EMAIL_ADDRESS>[2022-10-11T09:31:48.824Z] [INFO] [#tid_c85be9165297bc619860e1a26cc04649] [QueueManager] Got activation message 3ca322823217472fa322823217072f15 for<EMAIL_ADDRESS>from remote queue manager.
[2022-10-11T09:31:48.824Z] [INFO] [#tid_c85be9165297bc619860e1a26cc04649] [QueueManager] Recover a queue for<EMAIL_ADDRESS>[2022-10-11T09:31:48.824Z] [INFO] [#tid_91cb27040fff0411ca0b4bb985973e74] [QueueManager] Got activation message b0e69df6995b4962a69df6995ba96246 for<EMAIL_ADDRESS>from remote queue manager.
[2022-10-11T09:31:48.824Z] [INFO] [#tid_91cb27040fff0411ca0b4bb985973e74] [QueueManager] Recover a queue for<EMAIL_ADDRESS>[2022-10-11T09:31:48.824Z] [INFO] [#tid_a9fa02e03083ae8a1328a37047e5c6be] [QueueManager] Got activation message 6d5c80bb62eb4a7f9c80bb62eb8a7f92 for<EMAIL_ADDRESS>from remote queue manager.
[2022-10-11T09:31:48.824Z] [INFO] [#tid_a9fa02e03083ae8a1328a37047e5c6be] [QueueManager] Recover a queue for<EMAIL_ADDRESS>
7. The queue is recreated
It is also added to the init revision map and other recovery attempts are ignored.
[2022-10-11T09:31:48.884Z] [WARN] [#tid_3ab104600fa6cc0628d56b4e2c56c52d] [QueueManager] recreate queue for<EMAIL_ADDRESS>[2022-10-11T09:31:48.884Z] [INFO] [#tid_sid_unknown] [QueueManager] Update init revision map, key: bmt-1480/queue/guest/guest/noop0/leader, rev: 15-5aa72ce8d0070b26994803ac8c22de81
[2022-10-11T09:31:48.885Z] [INFO] [#tid_sid_unknown] [MemoryQueue] [guest:guest/noop0@0.0.1:Uninitialized] a new queue is created, retentionTimeout: 60000, kind: nodejs:10.
[2022-10-11T09:31:48.885Z] [INFO] [#tid_a9fa02e03083ae8a1328a37047e5c6be] [QueueManager] Queue for action<EMAIL_ADDRESS>is already recovered, skip

8. Shutdown the queue again
This newly created queue even received an activation but it receives GracefulShutdown again.
And the queue endpoint is also removed.
[2022-10-11T09:31:48.885Z] [INFO] [#tid_3ab104600fa6cc0628d56b4e2c56c52d] [MemoryQueue] [guest:guest/noop0@0.0.1:Running] got a new activation message 4864ed562a78408fa4ed562a78308f75
[2022-10-11T09:31:48.885Z] [INFO] [#tid_sid_unknown] [MemoryQueue] [guest:guest/noop0@0.0.1:Running] Gracefully shutdown the memory queue.
[2022-10-11T09:31:48.885Z] [INFO] [#tid_sid_unknown] [WatcherService] unwatch endpoint: UnwatchEndpoint(bmt-1480/queue/guest/guest/noop0/leader,false,data-management-service,true)

This is because the scheduler is in the shuttingdown state.
  private def recreateQueue(action: FullyQualifiedEntityName,
                            msg: ActivationMessage,
                            actionMetaData: WhiskActionMetaData): Unit = {
    logging.warn(this, s"recreate queue for ${msg.action}")(msg.transid)
    val queue = createAndStartQueue(msg.user.namespace.name.asString, action, msg.revision, actionMetaData)
    queue ! msg
    msg.transid.mark(this, LoggingMarkers.SCHEDULER_QUEUE_RECOVER)
    if (isShuttingDown) {
      queue ! GracefulShutdown.  // here
    }
  }

9. While the queue is going to stop another queue is created again
And it also shut down the queue again.
[2022-10-11T09:31:48.886Z] [WARN] [#tid_738382b188d8c89f5f517a02c4bdd2c6] [QueueManager] recreate queue for<EMAIL_ADDRESS>[2022-10-11T09:31:48.888Z] [INFO] [#tid_sid_unknown] [MemoryQueue] [guest:guest/noop0@0.0.1:Running] Gracefully shutdown the memory queue.
[2022-10-11T09:31:48.888Z] [INFO] [#tid_sid_unknown] [QueueManager] Remove init revision map cause queue is removed, key: bmt-1480/queue/guest/guest/noop0/leader

10. Shutdown the feed
This problem was repeatedly happening until the feed is also shut down and no more activation was coming.
[2022-10-11T09:31:49.306Z] [INFO] [#tid_sid_unknown] [KafkaConsumerConnector] wakeup consumer for 'creationAck0'
[2022-10-11T09:31:49.306Z] [INFO] [#tid_sid_unknown] [KafkaConsumerConnector] WakeupException happened when do commit action for topic creationAck0
[2022-10-11T09:31:49.307Z] [INFO] [#tid_sid_unknown] [KafkaConsumerConnector] closing consumer for 'creationAck0'

11. Stop the scheduler when there are still activations in the queue
Since no more activation was coming, all created queues (for the same action) were in the removing state and no queue reference was in the QueuePool. Since the current deployment script only checks if there is a queue in the scheduler, it just redeployed the scheduler while there are still activations in the queues.

When the scheduler was stopped, there were around 10 different queues for the same actions and 33 activations were in them.
[2022-10-11T09:31:51.309Z]initialized: true, avgDuration:Some(1.9665047142459378), stateName:Removing, incoming:0, current:2, existing:29, in-progress:88, stale:2, existingInNs:70, in-progressInNs:88
[2022-10-11T09:31:51.649Z]initialized: false, avgDuration:Some(1.9665046118449014), stateName:Removing, incoming:0, current:2, existing:0, in-progress:2, stale:2, existingInNs:72, in-progressInNs:88
[2022-10-11T09:31:51.548Z]initialized: true, avgDuration:Some(1.9664630890896282), stateName:Removing, incoming:0, current:3, existing:0, in-progress:3, stale:3, existingInNs:71, in-progressInNs:88
[2022-10-11T09:31:51.649Z]initialized: true, avgDuration:Some(1.966497872446949), stateName:Removing, incoming:0, current:18, existing:0, in-progress:18, stale:18, existingInNs:72, in-progressInNs:88
[2022-10-11T09:31:51.548Z]initialized: true, avgDuration:Some(1.9665114532673995), stateName:Removing, incoming:0, current:2, existing:0, in-progress:2, stale:2, existingInNs:71, in-progressInNs:88
[2022-10-11T09:31:51.548Z]initialized: true, avgDuration:Some(1.9664458988566114), stateName:Removing, incoming:0, current:2, existing:0, in-progress:2, stale:2, existingInNs:71, in-progressInNs:88
[2022-10-11T09:31:51.548Z]initialized: true, avgDuration:Some(1.9664526436773975), stateName:Removing, incoming:0, current:1, existing:0, in-progress:1, stale:1, existingInNs:71, in-progressInNs:88
[2022-10-11T09:31:51.548Z]initialized: false, avgDuration:Some(1.9664874298803876), stateName:Removing, incoming:0, current:2, existing:0, in-progress:2, stale:2, existingInNs:71, in-progressInNs:88
[2022-10-11T09:31:51.548Z]initialized: true, avgDuration:Some(1.9665462308159125), stateName:Removing, incoming:0, current:1, existing:0, in-progress:1, stale:1, existingInNs:71, in-progressInNs:88
[2022-10-11T09:31:51.548Z]initialized: true, avgDuration:Some(-48.25), stateName:Removing, incoming:0, current:0, existing:47, in-progress:0, stale:0, existingInNs:71, in-progressInNs:88

So to summarize the issue, the problem is that it's possible with this change for a scheduler to be stopped with activations still stuck in them even after being disabled? Are you sure that's introduced just with this change?

So to summarize the issue, the problem is that it's possible with this change for a scheduler to be stopped with activations still stuck in them even after being disabled? Are you sure that's introduced just with this change?

Previously the queue was only created by controllers. When a scheduler was shut down or a queue was removed for some reason controllers were in charge of creating them again.
So once the scheduler is disabled, no queue was recreated and no above regression happened.

I feel it's better to merge this PR and work based on it as the cycle anyway has to be addressed.
Since the regression only happens when the scheduler is disabled, I think it would be ok to merge this for now.


Add checking for invalid operand in perfix operation.

Fixes ch07/7.9/S7.9_A5.7_T1.js.

Good to me

LGTM


Let's try 3.8 python build

Issue #, if available: #340
Description of changes: trying 3.8 build, to see if it works
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

And it worked. Merging


Clean Stop / Abort Command in HFSS

Would anyone employ the code to execute Clean Stop or Abort command? Appreciate your help.

that would be though but I'll investigate.

I wonder how it would work.
Currently if someone gives oDesign.Analyze() then that function only goes to the next script command when its completed. So when will user be able to do an Abort? This change might require development to step in and essentially allow a argument like oDesign.Analyze(dont_wait_for_simulation_to_finish=True)
@maxcapodi78

this cannot implemented at this time since AEDT API doesn't support it

closing this issue as not supported by the API.


[#109035334] Implement acceptance and smoke tests

#109035334 Implement acceptance tests on the CF deployment
What
The objective is to implement a set of acceptance tests to ensure that the deployment was successful and that the platform functions as expected. Given that we have started with a vanilla install, we should be able to use the existing CF acceptance tests and we will build on these as we add functionality.
Context
The PR should be reviewed in this context:

I want to add the required configuration to run the basic acceptance tests.
I want to add a job that runs the smoke tests after deployment and is triggered
automatically after any successful deployment.
I want to add a job that runs the acceptance tests after deployment, altough
not triggered automaticaly.

How to test it?
Apply the pipelines from this branch and deploy CF as described in the README.md.
Remember set the variable BRANCH:
export BRANCH=$(git rev-parse --abbrev-ref HEAD)

Run the jobs smoke-tests and acceptance-tests.
acceptance-tests might have some tests failing due timeouts, but it is not
in the scope of this story fix that.
Who?
Anyone but @keymon or @combor

This works, both smoke and acceptance tests. Additional tests will be enabled as issues making them fail are being fixed...


Update utils.py

I needed to embark the code instead of the library because of the complexity of the parameters( model_path being checked when i just wanted to update the cuda parameters).
Here is a proposal for factorizing the model config overload, removing the model path check.

Thanks for your contribution.

Can you give some examples of when this was necessary?

The main issue i had was that when i was overloading the config with use_cuda parameters, the model path was prepended with the root path which i didn't want, so i just had to rewrite utils.py. Here i'm just proposing this and a refactor.

Sorry for reply late.
I rewrote the utils.py. You can try it whether solving your problem.
Honestly, I am still confused whether your changes are universal.


Add widget support for pages.

Add support to display Widgets in any filament page below the header and above footer.
Also update MakeWidgetCommand to allow create  a widget specifically for a Resources (like page command)
artisan make:filament-widget CustomerOverview --resource=CustomerResource
This is a solution to create widgets only for a resource page and dont display it on dashboard.
Maybe we need an option in the widget to define which ones will be automatically loaded in dashboard.

Thanks!


Different Bubble when calling derivativeservice/v2/manifest/:urn

Hi,
Sometimes the downloaded zips do not have all files in them, only the xref/designDescription.json file is in the zip, not the 0 folder with the scene.
I believe it is happening because of different results returned from the /derivativeservice/v2/manifest/:urn api. For example, I call /derivativeservice/v2/manifest/dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ and get:
{ guid: 'dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ',
  owner: 'dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ=',
  type: 'design',
  hasThumbnail: 'false',
  startedAt: 'Mon Dec 19 00:11:05 UTC 2016',
  urn: 'dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ',
  region: 'US',
  status: 'success',
  progress: 'complete',
  success: '100%',
  children:
   [ { guid: 'aa85aad6-c480-4a35-9cbf-4cf5994a25ba',
       name: 'd2uddpvm9os908ie0k34k7qfr.ipt',
       success: '100%',
       hasThumbnail: 'false',
       role: 'viewable',
       version: '2.0',
       urn: 'dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ',
       status: 'success',
       assetCount: 29,
       type: 'folder',
       progress: 'complete',
       children:
        [ { guid: '3b81724e-5543-4ff8-aeb7-9d74588f38a9',
            type: 'resource',
            role: 'Autodesk.CloudPlatform.DesignDescription',
            urn: 'urn:adsk.viewing:fs.file:dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ/output/xref/designDescription.json',
            mime: 'application/json' } ] } ] }

This shows all translations have completed with result success. My application then proceeds to download the files listed in the manifest on the basis that all nodes in the manifest show successful translation. However, calling /derivativeservice/v2/manifest/dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ again 10 seconds later returns a different result with more information. I get:
{ guid: 'dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ',
  owner: 'dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ=',
  type: 'design',
  hasThumbnail: 'true',
  startedAt: 'Mon Dec 19 00:11:05 UTC 2016',
  urn: 'dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ',
  region: 'US',
  status: 'success',
  progress: 'complete',
  success: '100%',
  children:
   [ { guid: 'aa85aad6-c480-4a35-9cbf-4cf5994a25ba',
       name: 'd2uddpvm9os908ie0k34k7qfr.ipt',
       success: '100%',
       hasThumbnail: 'true',
       role: 'viewable',
       version: '2.0',
       urn: 'dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ',
       status: 'success',
       assetCount: 29,
       type: 'folder',
       progress: 'complete',
       children:
        [ { guid: '3b81724e-5543-4ff8-aeb7-9d74588f38a9',
            type: 'resource',
            role: 'Autodesk.CloudPlatform.DesignDescription',
            urn: 'urn:adsk.viewing:fs.file:dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ/output/xref/designDescription.json',
            mime: 'application/json' },
          { guid: '8615e0f8-2ff4-4f94-9baa-cb2541744b02',
            type: 'folder',
            name: 'Scenes',
            status: 'success',
            progress: 'complete',
            success: '100%',
            hasThumbnail: 'true',
            children:
             [ { guid: '9d76bf67-0622-4df7-a960-20ba448ab5e6',
                 type: 'geometry',
                 role: '3d',
                 name: 'Scene',
                 status: 'success',
                 progress: 'complete',
                 size: 201544,
                 success: '100%',
                 hasThumbnail: 'true',
                 children:
                  [ { guid: 'bb1388e5-3961-4b5b-980a-0d4f13c31d11',
                      type: 'resource',
                      urn: 'urn:adsk.viewing:fs.file:dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ/output/1/d2uddpvm9os908ie0k34k7qfr.svf',
                      role: 'graphics',
                      mime: 'application/autodesk-svf',
                      size: 119274 } ] },
               { guid: '31bd9eff-10b0-4763-9e78-f8bc2bdb6b12',
                 type: 'resource',
                 urn: 'urn:adsk.viewing:fs.file:dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c3RlbW4vZDJ1ZGRwdm05b3M5MDhpZTBrMzRrN3Fmci5pcHQ/output/1/properties.db',
                 role: 'Autodesk.CloudPlatform.PropertyDatabase',
                 mime: 'application/autodesk-db',
                 status: 'success',
                 size: 24576 } ] } ] } ] }

This response contains the information required to download the scene. Can you advise a way of getting a consistent response from the /derivativeservice/v2/manifest/:urn api so that my application does not download incomplete zips?

Any word @cyrillef?

Hi, I'll take a look right now - sorry for delay

Did you find a solution @cyrillef?

@sabrehagen - is it still an issue, I update the sample a minute ago, and do not have this issue. If you got a sample to share that would be great to track the issue you got.


looking for ideas on where to start..

hey guys!!
I had a crazy idea, that may turn out to be a bit too much...
I was thinking of doing a clock, where the hands turn like they would on a real one.....
but here's the kicker,...they follow the direction of the mouse..
So...go around to the right, and  the hands follow that direction, go left, and they go that way..
Sound crazy?
anyway, any ideas where to start?

seems like it would be easier to get one hand to rotate, instead of trying both...
another idea, would be to use a similar code to the "man with a spinning head" example, but it wouldn't have to move left and right.


Authenticating socket with cookie

Hi
I am currently using the authentication scheme for HTTP requests and websocket communication.
I am storing a cookie in the browser using Guardian which works fine.
When it comes to sockets, I see that I must pass in the JWT explicitly, which is a problem due to the cookie being HTTP only.
How do I get around this?

@madshargreave is this question directed at Phoenix Channel socket authentication?
If so, there are a couple of options for this:

Create a normal HTTP API endpoint on the server that a client can use to fetch a token based on the value in the cookie.
Render a token into the DOM and query it with JS.

Because Phoenix Channels were designed to not be coupled to browsers, cookie-based authentication is not supported.


Create page for common errors

I had previously listed common errors in the Troubleshooting guide, but when I went to look for it I could never remember where it was. This PR moves that information to it's own page, in the support section.

Assigning to on-call.

Did we get rid of the CI job that would show a preview of the built docs?

Did we get rid of the CI job that would show a preview of the built docs?

Yes, it was using a 3P service that we cancelled the contract with.


crowdin-cli: 3.7.9 -> 3.7.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/crowdin/crowdin-cli/releases.
meta.description for crowdin-cli is: "A command-line client for the Crowdin API"
meta.homepage for crowdin-cli is: "https://github.com/crowdin/crowdin-cli/"
meta.changelog for crowdin-cli is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.7.10 with grep in /nix/store/i5xrzacb90j8j749j7swnlhwgw894vzv-crowdin-cli-3.7.10
found 3.7.10 in filename of file in /nix/store/i5xrzacb90j8j749j7swnlhwgw894vzv-crowdin-cli-3.7.10

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
crowdin-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/i5xrzacb90j8j749j7swnlhwgw894vzv-crowdin-cli-3.7.10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A crowdin-cli https://github.com/r-ryantm/nixpkgs/archive/d9a9b87d1d11cabddd6bdb59412e1ef4e6bd832b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/i5xrzacb90j8j749j7swnlhwgw894vzv-crowdin-cli-3.7.10
ls -la /nix/store/i5xrzacb90j8j749j7swnlhwgw894vzv-crowdin-cli-3.7.10/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

crowdin-cli

Maintainer pings
cc @DamienCassou for testing.

Result of nixpkgs-review pr 186386 run on x86_64-linux 1

1 package built:

crowdin-cli


Possibility to compare type text as case insensitive?

Hi All,
Is it possible to compare the text columns as case insensitive somehow in NBi?
As per the documentation I have found that the text is case sensitive by default.
It is possible to use  tag to transform the expected result set, but I was unable to find any setting for the second side (tested result set) so this is a no go option.
For example if I compare two cubes and the key column is text, is it possible to ignore case sensitivity on both sides?
I do not want to edit the input MDX queries and use the upper/lower case there (by creating the calculated MEMBERs) because in some cases this complicates the automated test creation using nbitt files and dimensions as variables files.
Could you give me the guide (if it is possible) please?
In case it is not possible could it be implemented (I mean just something like "tolerance" option to turn off/on the case sensitivity in the text)?
Cheers.

Ignore-case is supported in some places:

When comparing two members
When checking the structure (model)
When using a predicate (for text columns) in filters or none/all rows.

But is not supported when comparing the equivalence of two result-sets (Neither in the key comparison or the value comparison).
For the values, it sounds easy to implement a new TextTolerance (currently supporting fuzzy string equality) named "ignore-case" and use it in the TextComparer. For the keys, it's more complex. You'd need to add a new attribute on the equal-to and then change the classes DataRowKeysComparer. Sounds a bit harder to do.
I'll consider to add this but will surely not be a priority. Feel free to propose a PR.

Changed a little bit my mind about priority around columns that are "values"  … To specify that two textual values should be compared ignoring the case, the following tolerance should be set:
<equalTo>
    <column index="1" role="value" type="text" tolerance="Ignore-case"/>
    ...
</equalTo>

this feature is available in build https://ci.appveyor.com/project/Seddryck/nbi/builds/19805551 or nuget 1.19-beta0090

Huuum, in your text you say that it's not possible to alter a result-set from the system-under-test. In fact it's possible within a result-set to define an alteration more info … the documentation is not covering it but these alterations also supports column's transformation.
I'll open a new issue to support some ignore-case features for keys … but I'm not convinced by this one.

Cool, thanks!

I created a bug at #420
Not really part of this new feature but linked to this new version (refactoring).

Hey @Seddryck ,
In the documentation I can see that the transform in the assert part should not be used at all.
http://www.nbi.io/docs/scalar-transform/
Is there any new possibility to do this in kind of "correct" way?
I mean, is there any other way to compare key values case insensitive?
Cheers.

Not sure where you read that it shouldn't be used, it's probably an old syntax that shouldn't be used but transform is still part of the alterations supported by the framework.
Specifically for being case-insensitive on keys, I'd upper or lower-case in a transform, no issue with this.

Hmm, then maybe I just don't understand the documentation.
Specfically this part in between the two examples (I thought the second example is the second option that should be avoided):
From your documentation:
The second option is deprecated and should be avoided as much as possible. It can safely be replaced by the previous notation. The idea of this notation was to specify the transformation in the column’s definition of an equal-to assertion.
Anyway, if you say it's ok to be used then I am OK with it.
Thanks for the quick response.


Fix 128-bit int regression on big-endian with Python <3.13

Fixes #4290.
As described in the issue, a change from Ok(<$rust_type>::from_le_bytes(buffer)) to Ok(<$rust_type>::from_ne_bytes(buffer)) was unconditional, but was only appropriate when the preceding Python-3.13-only block was compiled. This PR makes that change conditional on Python version, too.
I tested this as a patch on all Fedora releases and EPEL9 and confirmed the tests now pass on all Fedora primary architectures, for both Python 3.13 and previous interpreter versions.

Thank you for contributing to PyO3!
By submitting these contributions you agree for them to be dual-licensed under PyO3's MIT OR Apache-2.0 license.
Please consider adding the following to your pull request:

an entry for this PR in newsfragments - see [https://pyo3.rs/main/contributing.html#documenting-changes]

or start the PR title with docs: if this is a docs-only change to skip the check

docs to all new functions and / or detail in the guide
tests for all new or changed functions

PyO3's CI pipeline will check your pull request, thus make sure you have checked the Contributing.md guidelines. To run most of its tests
locally, you can run nox. See nox --list-sessions
for a list of supported actions.

This might be a slightly simpler version of the fix (also confirmed to work) which keeps the number of cfg-gated blocks to 2 instead of adding a third one:
diff --git a/src/conversions/std/num.rs b/src/conversions/std/num.rs
index effe7c7..1304e73 100644
--- a/src/conversions/std/num.rs
+++ b/src/conversions/std/num.rs
@@ -238,15 +238,18 @@ mod fast_128bit_int_conversion {
                         unsafe { ffi::PyNumber_Index(ob.as_ptr()).assume_owned_or_err(ob.py())? };
                     let mut buffer = [0u8; std::mem::size_of::<$rust_type>()];
                     #[cfg(not(Py_3_13))]
-                    crate::err::error_on_minusone(ob.py(), unsafe {
-                        ffi::_PyLong_AsByteArray(
-                            num.as_ptr() as *mut ffi::PyLongObject,
-                            buffer.as_mut_ptr(),
-                            buffer.len(),
-                            1,
-                            $is_signed.into(),
-                        )
-                    })?;
+                    {
+                        crate::err::error_on_minusone(ob.py(), unsafe {
+                            ffi::_PyLong_AsByteArray(
+                                num.as_ptr() as *mut ffi::PyLongObject,
+                                buffer.as_mut_ptr(),
+                                buffer.len(),
+                                1,
+                                $is_signed.into(),
+                            )
+                        })?;
+                        Ok(<$rust_type>::from_le_bytes(buffer))
+                    }
                     #[cfg(Py_3_13)]
                     {
                         let mut flags = ffi::Py_ASNATIVEBYTES_NATIVE_ENDIAN;
@@ -272,8 +275,8 @@ mod fast_128bit_int_conversion {
                                 "Python int larger than 128 bits",
                             ));
                         }
+                        Ok(<$rust_type>::from_ne_bytes(buffer))
                     }
-                    Ok(<$rust_type>::from_ne_bytes(buffer))
                 }

                 #[cfg(feature = "experimental-inspect")]

This might be a slightly simpler version of the fix (also confirmed to work) which keeps the number of cfg-gated blocks to 2 instead of adding a third one:

I think this is a clear improvement over the original, which was:
diff --git a/src/conversions/std/num.rs b/src/conversions/std/num.rs
index effe7c7c..6841e9dc 100644
--- a/src/conversions/std/num.rs
+++ b/src/conversions/std/num.rs
@@ -272,8 +272,10 @@ mod fast_128bit_int_conversion {
                                 "Python int larger than 128 bits",
                             ));
                         }
+                        Ok(<$rust_type>::from_ne_bytes(buffer))
                     }
-                    Ok(<$rust_type>::from_ne_bytes(buffer))
+                    #[cfg(not(Py_3_13))]
+                    Ok(<$rust_type>::from_le_bytes(buffer))
                 }

                 #[cfg(feature = "experimental-inspect")]

Your version not only reduces the number of conditionals, but keeps related code close together.
I will amend and force-push.

No problem. Thank you for the quick fix!


WIndows 10 Install Error

The 1 extension(s) below, in workspace recommendations have issues: undefined.dark (not found in marketplace)

I tried installing this on windows 10 and got the above code. Unable to enable through extensions view

Thanks for the feedback! This appears to have been a problem with the naming of the package in it's configuration file. I've fixed the issue. Try pulling the repository again and let me know if it works.

This appears to have resolved the issue, thanks!


Update Resource.php

We can't send a zip file, cause zip file is not a media.

Media should work fine for the zip files - I'm not sure what this patch is trying to do?


[Bug] [Alert] Users cannot select alarm groups when triggering / scheduling workflows

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

After creating an ordinary user and alert groups with admin, I log out and re-login with the new user. Then when triggering / scheduling the workflows, there are no alert groups to select from.

I haven't found the error logs yet. Will follow up with error logs later.

What you expected to happen

Users should be able to choose alert groups when triggering / scheduling workflows.

How to reproduce

Already described in the What happened section.

Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Seems we have the same situation with Environment:

Hi @EricGao888 I can select the exists alert group in branch 3.0.0-prepare

Hi @EricGao888 I can select the exists alert group in branch 3.0.0-prepare

Looks like a bug on dev. If there's no such thing on 3.0.0-prepare, we may change the milestone to 3.1.0 or something else. WDYT @zhongjiajie @SbloodyS

Oh, I find out it exists in workflow definition page instead of runing workflow dialog

@songjianet @Amy0104 @devosend I find out backend return the right entry, could you please take a look the frontend code?

I re-test it, and find there are two error places

workflow definition -> Edit task -> select environment name

workflow definition -> mark workflow online -> trigger -> select environment name

I re-test it, and find there are two error places

workflow definition -> Edit task -> select environment name

workflow definition -> mark workflow online -> trigger -> select environment name

Have you selected a work group for the environment?

I re-test it, and find there are two error places

workflow definition -> Edit task -> select environment name

workflow definition -> mark workflow online -> trigger -> select environment name

Have you selected a worker group for the environment? If not, the worker group of the environment list from the back end should be set to default not empty.  @zhongjiajie pls cc.

Yesh, you are right I forget to connect the environment to workgroup, when I connect them then it work correctly, thanks for your clarification 👍

cc @EricGao888

I re-test it, and find there are two error places

workflow definition -> Edit task -> select environment name

workflow definition -> mark workflow online -> trigger -> select environment name

Have you selected a worker group for the environment? If not, the worker group of the environment list from the back end should be set to default not empty.  @zhongjiajie pls cc.

@Amy0104 @zhongjiajie Thanks for the clarification. Environments works for me after associating it with worker group. My bad and I think I need to reread the docs : ). BTW, I still have the issue with alarm groups, do I miss anything here?

@Amy0104 @zhongjiajie Thanks for the clarification. Environments works for me after associating it with worker group. My bad and I think I need to reread the docs : ). BTW, I still have the issue with alarm groups, do I miss anything here?

alarm groups work in my laptop, can you run mvn clean and then restart the server? @EricGao888

@Amy0104 @zhongjiajie Thanks for the clarification. Environments works for me after associating it with worker group. My bad and I think I need to reread the docs : ). BTW, I still have the issue with alarm groups, do I miss anything here?

alarm groups work in my laptop, can you run mvn clean and then restart the server? @EricGao888

@zhongjiajie Sure, I'm going to double check this. BTW, are u testing the dev branch for alarm group or 3.0.0-prepare?

I only test in branch 3.0.0-prepare

I only test in branch 3.0.0-prepare

@zhongjiajie It does exist on dev branch.

I only test in branch 3.0.0-prepare

@zhongjiajie It does exist on dev branch.

Just pulled the latest code of dev branch and retested it, the alarm group issue still exists. cc @zhongjiajie @SbloodyS @Amy0104

I only test in branch 3.0.0-prepare

@zhongjiajie It does exist on dev branch.

Just pulled the latest code of dev branch and retested it, the alarm group issue still exists. cc @zhongjiajie @SbloodyS @Amy0104

I tested it on branch dev. It is working for me if I set a worker group to the environment. Could you provide the response of the environment list request when creating a task. @EricGao888

I only test in branch 3.0.0-prepare

@zhongjiajie It does exist on dev branch.

Just pulled the latest code of dev branch and retested it, the alarm group issue still exists. cc @zhongjiajie @SbloodyS @Amy0104

I tested it on branch dev. It is working for me if I set a worker group to the environment. Could you provide the response of the environment list request when creating a task. @EricGao888

I mean Alarm Group. Environments works on dev branch for me, as I've mentioned above: https://github.com/apache/dolphinscheduler/issues/11249#issuecomment-1203526359

{     "code": 0,     "msg": "success",     "data": {         "processDefinition": {             "id": 1,             "code":<PHONE_NUMBER>792,             "name": "sda",             "version": 1,             "releaseState": "ONLINE",             "projectCode":<PHONE_NUMBER>480,             "description": "",             "globalParams": "[]",             "globalParamList": [],             "globalParamMap": {},             "createTime": "2022-08-03 07:03:54",             "updateTime": "2022-08-03 07:03:54",             "flag": "YES",             "userId": 2,             "userName": null,             "projectName": null,             "locations": "[{\"taskCode\":6410217114432,\"x\":158,\"y\":73}]",             "scheduleReleaseState": null,             "timeout": 0,             "tenantId": -1,             "tenantCode": null,             "modifyBy": null,             "warningGroupId": 0,             "executionType": "PARALLEL"         },         "processTaskRelationList": [             {                 "id": 1,                 "name": "",                 "processDefinitionVersion": 1,                 "projectCode":<PHONE_NUMBER>480,                 "processDefinitionCode":<PHONE_NUMBER>792,                 "preTaskCode": 0,                 "preTaskVersion": 0,                 "postTaskCode":<PHONE_NUMBER>432,                 "postTaskVersion": 1,                 "conditionType": "NONE",                 "conditionParams": {},                 "createTime": "2022-08-03 07:03:54",                 "updateTime": "2022-08-03 07:03:54",                 "operator": 2,                 "operateTime": "2022-08-03 07:03:54"             }         ],         "taskDefinitionList": [             {                 "id": 1,                 "code":<PHONE_NUMBER>432,                 "name": "ts",                 "version": 1,                 "description": "",                 "projectCode":<PHONE_NUMBER>480,                 "userId": 2,                 "taskType": "SHELL",                 "taskParams": {                     "localParams": [],                     "rawScript": "echo hello",                     "resourceList": []                 },                 "taskParamList": [],                 "taskParamMap": null,                 "flag": "YES",                 "taskPriority": "MEDIUM",                 "userName": null,                 "projectName": null,                 "workerGroup": "default",                 "environmentCode": -1,                 "failRetryTimes": 0,                 "failRetryInterval": 1,                 "timeoutFlag": "CLOSE",                 "timeoutNotifyStrategy": null,                 "timeout": 0,                 "delayTime": 0,                 "resourceIds": "",                 "createTime": "2022-08-03 07:03:54",                 "updateTime": "2022-08-03 07:03:54",                 "modifyBy": null,                 "taskGroupId": 0,                 "taskGroupPriority": 0,                 "cpuQuota": -1,                 "memoryMax": -1,                 "operator": 2,                 "operateTime": "2022-08-03 07:03:54",                 "dependence": ""             }         ]     },     "failed": false,     "success": true }

I only test in branch 3.0.0-prepare

@zhongjiajie It does exist on dev branch.

Just pulled the latest code of dev branch and retested it, the alarm group issue still exists. cc @zhongjiajie @SbloodyS @Amy0104

I tested it on branch dev. It is working for me if I set a worker group to the environment. Could you provide the response of the environment list request when creating a task. @EricGao888

I mean Alarm Group. Environments works on dev branch for me, as I've mentioned above: #11249 (comment)

I got u, but the alarm group works for me on dev branch.

I only test in branch 3.0.0-prepare

@zhongjiajie It does exist on dev branch.

Just pulled the latest code of dev branch and retested it, the alarm group issue still exists. cc @zhongjiajie @SbloodyS @Amy0104

I tested it on branch dev. It is working for me if I set a worker group to the environment. Could you provide the response of the environment list request when creating a task. @EricGao888

I mean Alarm Group. Environments works on dev branch for me, as I've mentioned above: #11249 (comment)

I got u, but the alarm group works for me on dev branch. Can you reproduce this? @zhongjiajie

Hi @Amy0104 , may I ask which user you used for testing? If u choose admin, it works. But if u choose some ordinary user, it happens. Probably something related to user / permission.

I only test in branch 3.0.0-prepare

@zhongjiajie It does exist on dev branch.

Just pulled the latest code of dev branch and retested it, the alarm group issue still exists. cc @zhongjiajie @SbloodyS @Amy0104

I tested it on branch dev. It is working for me if I set a worker group to the environment. Could you provide the response of the environment list request when creating a task. @EricGao888

I mean Alarm Group. Environments works on dev branch for me, as I've mentioned above: #11249 (comment)

I got u, but the alarm group works for me on dev branch. Can you reproduce this? @zhongjiajie

Hi @Amy0104 , may I ask which user you used for testing? If u choose admin, it works. But if u choose some ordinary user, it happens. Probably something related to user / permission.

I created a alarm group with admin account, and then changed to a ordinary user.

I cannot see the alerm group with ordinary user :)

+1
I cannot see the alerm group with ordinary user :)

+1
I cannot see the alerm group with ordinary user :)

I find this is caused by the back-end has a authority logic when query AlertGroup.

+1
I cannot see the alerm group with ordinary user :)

I find this is caused by the back-end has a authority logic when query AlertGroup.

Yes, when a non-Admin user queries an AlertGroup, the condition is whether it is created by the current user. I will check the data query logic of other resources and submit a PR. A reasonable form should be able to authorize all data resources in the system, and Now the unified management of permissions has been extracted in the system.

This should be fixed by #11301


When moving units with a railroad through a city, the movement count should be reduced

If the city has railroad placed in its vicinity, the units moving with a railroad through a city should have their movement reduced by 1/3. Cities always act as having a normal road tile, even with the invention of railroad.
Frankly this is one of the most annoying bugs in Civ1 and you should probably just ignore this issue. They fixed this in Civ2.

I will implement this anyway, sorry. ;-)

is this still true if the city is built on a square which already contains RR?

iStruggle - yes it's still true


Fix NullPointerException at com.sun.source.util.TreePath.

Fixes https://netbeans.org/bugzilla/show_bug.cgi?id=271772

I haven't tested this but the patch looks good to me.

The change looks save and in the worst case it masks the underlying bug. I'm pulling this in.


Can't get hover value on resource timeline

Checked for duplicates
No - I haven't checked
Is this a regression?
No - This is a new bug
Version
1.6
Describe the bug
If you zoom in on time such that all of a resource's points are outside the time window (as shown in the screenshot below), hovering the mouse over the timeline shows no time/value tooltip.  It's arguably not a bug since this is the intended behavior: the tooltip only shows up when hovering over a point, not just the line.  But, given that you can't see an exact value at a particular point in time (whether zoomed in or out) is a problem.

So, as a feature request, I'd like to be able to get a tooltip wherever I hover on the plotted line and see the interpolated value at that point and maybe also even the times/values of the preceding and following points.   See how RAVEN does it.
Reproduction
Zoom in on plot between a resource's plotted points.
See that the specific value cannot be ascertained and only determined by judging against the y-axis markers.
Logs
No response
System Info
chrome, macos

Severity
Moderate

https://github.com/NASA-AMMOS/aerie-ui/issues/856 supersedes this


feat: migrate the ollama provider from python to rust

feat: This PR migrates the Ollama provider from Python to Rust implementation.
Key changes include:

Implemented OllamaProvider with async/await support
Added spawn_blocking for health checks
Implemented comprehensive test suite including:

Unit tests with mocks
Integration tests with real Ollama server
Error case testing

Added integration test feature flag
Maintained parity with Python implementation

Test Plan:

Unit tests can be run with:
```bash
cargo test --package goose --lib providers::ollama::tests
```

Integration tests (requires running Ollama server) can be run with:
```bash
cargo test --package goose --lib providers::ollama::tests --features integration
```

Migration Details:

Ported all functionality from old-goose/goose/packages/exchange/src/exchange/providers/ollama.py
Maintained test parity with old-goose/goose/packages/exchange/tests/providers/test_ollama.py
Added additional error case testing not present in Python version

nice one @meenalc !