What is the status of this vs. AWSLambdaPSCore?

I am confused by the existence of this project.
Is it a replacement for AWSLambdaPSCore? If so, why isn't this project formally documented in the AWS documentation as an alternative to that? The doc, AFAIK, still refers only to AWSLambdaPSCore.
A blog post from 2022 and a seven-minute demo YouTube video are insufficient to determine the production viability of this project for pwsh devs want the durability and production support of AWSLambdaPSCore. Is AWS recommending new functions developed in PowerShell should be deployed using this technique? Is there a deprecation date for AWSLambdaPSCore?
These questions, and many more that devs need to assess the production quality and future of this project are unanswered.
Also, I'm not sure that the benefits of editing code in the AWS console outweigh the clumsy (and poorly documented) deployment process and added size. I'd appreciate knowing why running in a container with a layer of indeterminate durability is better than bundling a supported .Net runtime with known, specific versions of AWS.Tools modules.
Clearly, I don't "get it." :-)

Thanks for the detailed, throughtful reply, @julianwood.
Personally, and since I've been using it for years, I don't find New-AWSPowerShellLambdaPackage all that difficult to use. And I'm hardly what one would call a .Net dev. Maybe it's familiarity -- I've been using it since 2018. Functions created using this process run reliably and are supported.
And relates to my real concern: is this project a project or a product? If it's the latter, it needs to be "official," whatever that means in AWS. (I have no idea what your internal product management process is so I can't offer any suggestions on that point.)
In the enterprise world where I work, if it's not in the documentation and AWS Support doesn't provide support for it, it's not something I can recommend to or implement for clients. It's not enough to say to a defense contractor, "One of the Github contributors says that lots of people inside AWS use this."
You ask how to improve the experience and doc? Offer it as a formal alternative, documented here. List all the requirements, work on multiple examples and tutorials and, if possible, eliminate the requirement for SAM.
Thanks again.

We are looking to have this included in the AWS documentation as an option.

@julianwood, has your team made progress in this area?
My team is onboarding to Lambda for the first time with a PowerShell codebase we've developed. Comparing the feature-set of this runtime against what's supported by the .NET runtime has been very difficult.
I filed an AWS support case<PHONE_NUMBER>00577) to ask for specifics, but even AWS support wasn't able to answer my questions.
Given the relatively small intersectional niche of "PowerShell" x "AWS Lambda", trying to piece together coherent guidance between AWS docs, this repo, community members' repos, and so on has been very difficult.
It would be very helpful if AWS support - both written docs and human support agents - had enough context on the .NET/PowerShell custom runtimes to present a reasonably comprehensive comparison between the two. As a new user of Lambda (coming from Azure Automation &co), getting started has been really difficult.


⚠ Bofrost.lu has degraded performance

In f26a26b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 993 ms

Resolved: Bofrost.lu performance has improved in 4904977 after 6 minutes.


add usage on CI

Codecov Report

Merging #81 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #81   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines         126    126
=====================================
  Hits          126    126

Continue to review full report at Codecov.

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

@kentcdodds Changed. Also added usage with a lerna repo


feat: improve performance with buffered I/O (bufio) for large file handling

This pull request addresses issue #22 by improving the performance of reading contents (e.g., file nor stdin) in Clipper using buffered I/O (bufio).
Changes:

Refactor: Implement buffered I/O for reading content

Use bufio.Reader to handle large sums of data efficiently.
Extract common read logic into a new ReadContent function.

Test: Add unit tests for ReadContent function

Added test cases for single line, multiple lines, empty content, and EOF error scenarios.
Organized tests using t.Run for better readability.

Tasks:

[x] Implement buffered I/O with bufio.Reader
[x] Extract common read logic into ReadContent function
[x] Add unit tests for ReadContent
[x] Organize tests using t.Run

These changes were an attempt to enhance the performance of Clipper, especially when dealing with large files. However, based on the benchmark results, the non-buffered I/O implementation remains the better option for Clipper's performance needs.
Reference

See Clipper Performance Evaluation of Buffered I/O Implementation

Either here or in #22, it would be interesting to provide a benchmark
You could use Go native benchmark

Either here or in #22, it would be interesting to provide a benchmark
You could use Go native benchmark

I'm working on it using testing.B. Later I'll add the results and reasoning behind the decision to either add this PR or close it.

Here's a concise comment to close PR #33 and link to the performance evaluation report:
After extensive benchmarking, I have concluded that the non-buffered implementation provides superior performance. You can find the detailed Clipper Performance Evaluation of Buffered I/O Implementation report here.
Based on these findings, we will close this PR. We appreciate your efforts and contributions.
Closes #33.

After extensive benchmarking, I have concluded that the non-buffered implementation provides superior performance.
Find the detailed Clipper Performance Evaluation of Buffered I/O Implementation report here.
Based on these findings, I will close this PR.

It's always a good thing to do benchmarking and a great things to publish the results.
Especially because, you can find them back later with search, and copy paste to run them again if there is a need to compare again.


BUG: Bilinear dtype promotion

Currently bilinear regridding gives unexpected results for source data which is of boolean or unsigned integer type due to the way that type promotion is currently handled here
An easy fix is the following:
dtype = np.promote_types(dtype, 'float16')

Any reasons against this change before I make the change?

@cpelley Are you suggesting that you promote the dtype regardless?

Regardless of what sorry?
I should clarify what this does and why this makes sense:
>>> np.promote_types('int64', 'float16')
dtype('float64')
>>> np.promote_types('int32', 'float16')
dtype('float64')
>>> np.promote_types('int8', 'float16')
dtype('float16')
>>> np.promote_types('uint8', 'float16')
dtype('float16')
>>> np.promote_types('bool', 'float16')
dtype('float16')

So this change means the resulting array that bilinear populates is always a float array (taking the minimum kind allowed).
Currently bilinear regrid can return a boolean array when the source is boolean.  It makes no sense for bilnear regrid to return a boolean array.  This extends the current existing thought that integer type is cast as 16-bit float

@cpelley What I meant was, are you simply proposing to replace
if method = 'linear':
    if dtype.kind == 'i':
        dtype = np.promote_types(dtype, np.float16)

with
if method == 'linear':
    dtype = np.promote_types(dtype, np.float16)

i.e. execute the promote_types regardlessly.

The change sound sensible to me, it'll be interesting whether it breaks any tests though ...

Ah OK, yes that is what I meant :)
Thanks for your input @bjlittle, I'll get onto it!

@cpelley - is this still an issue. I've just closed the experiment PR in #2088, but there has been a merge from #2203. Does that address the bug being raised here? If not, would you like to revive #2088 and we will get it in? Otherwise, I don't think this issue needs to hang around.
Cheers,


[MLDBFB-320] related to MLDB-957, built-in function names should be c…

…ase-sensitive
This was causing some instability since part of the code was interpreting a function as being an aggregator when some other parts were not!

+1


Test icebergs script against MIZ

Required some decent modification from the icebergs scripts, but is tested locally and I think addresses this! Let me know what y'all think


find a bug

if the file name have character '/' ，UABEA can't export it

Are you still on release 3? Pretty sure this has already been fixed.


Unclear error messages when misconfiguring data

In my project, the following config works:
runner.py task=segmentation task/model=enet data=radrec data.dataset_path=<DATASET_PATH>
Here is the error I get if I omit the data.* args:
runner.py task=segmentation task/model=enet
omegaconf.errors.MissingMandatoryValue: Missing mandatory value: data._target_
    full_key: data._target_
    object_type=dict

This message does not inform of the real problem, which is that data is not set. I'm thinking it might be better if we make data mandatory. That way, the error message would clearly say that data is missing, instead of one of its keys.
The following is another unclear error message that is related.
I have created a new task in my project by copy-pasting segmentation.yaml. I only changed the _target_. Here is what happens when I omit data.* like above, but with my own task:
runner.py task=radrec task/model=enet
task=radrec task/model=enet
omegaconf.errors.InterpolationKeyError: Interpolation key 'data.image_tag' not found
    full_key: task.image_tag
    object_type=dict

It's weird that I don't get the same message. But also, it seems like making data mandatory would help. (By the way, after setting data and data.dataset_path, it works.)
Another error that I find unclear is when I omit just data.dataset_path; the error does not mention the actual argument name:
hydra.errors.InstantiationException: Error in call to target 'radrec.dataset.datamodule.RadrecDataModule':
TypeError('expected str, bytes or os.PathLike object, not NoneType')
full_key: data

Note that data/radrec.yaml contains dataset_path: null.
Any thoughts?

I'll start by adressing the specific errors (especially where I can explain them), before we take a step back to properly discuss the design of the data config.

I have created a new task in my project by copy-pasting segmentation.yaml. I only changed the _target_. Here is what happens when I omit data.* like above, but with my own task: runner.py task=radrec task/model=enet
task=radrec task/model=enet
omegaconf.errors.InterpolationKeyError: Interpolation key 'data.image_tag' not found
    full_key: task.image_tag
    object_type=dict

It's weird that I don't get the same message. But also, it seems like making data mandatory would help. (By the way, after setting data and data.dataset_path, it works.)

I'm not able to properly explain why the error message changes between the 2 commands. Out of curiosity, did you implement your project inside vital (as its own git branch), or did you create a separate project that depends on vital (in the same vein as my CASTOR project)?
Because the only thing that comes to mind as an explanation would be a difference in the order in which different configs are resolved (maybe across projects hence my previous question), which would cause one error or the other to trigger first.

Another error that I find unclear is when I omit just data.dataset_path; the error does not mention the actual argument name:
hydra.errors.InstantiationException: Error in call to target 'radrec.dataset.datamodule.RadrecDataModule':
TypeError('expected str, bytes or os.PathLike object, not NoneType')
full_key: data

Note that data/radrec.yaml contains dataset_path: null.

I admit that it's not especially intuitive, but in my experience it's how Hydra outputs errors, especially in multirun mode where each individual run is a subprocess (or thread? I'm not sure), which can obfuscate a bit where the error originally came from. The error that is printed last is not especially clear, but if you scroll up the stack trace you'll eventually find the original "native python" error, which ought to be clearer.
In your case, what the error is telling you line-by-line is this:

An error happened when trying to instantiate an config node of target radrec.dataset.datamodule.RadrecDataModule;
The very end of whatever error message was produced by the failed instantiation of the class. In your case, the message makes sense because dataset_path: null is not providing no dataset_path, it's setting None as its value (but a string or path is expected) ;
This is telling you the "name" of the config node whose instantiation failed with the above error. The target provided earlier is the target of this config node.

So, in your case, if you want a clear error message, you should set dataset_path: ??? so that Hydra would not try to instantiate the object with dataset_path=None, but would rather give a clear error message.

Merci beaucoup! J'apprécie que tu aies pris le temps de répondre, car ce n'est clairement pas prioritaire.
To answer your question, my projects depends on vital as a git submodule.
Thanks for the suggestion about setting dataset_path: ???, that's what I should have used in the first place.
Now, a question remains unanswered: why isn't data mandatory? Maybe because it some cases the info is contained in a checkpoint that is loaded?


Change of groups by the user

Description
Add functionality to let an user change his group or select all groups.
Use case
An user that belongs to more than one group could change his primary group. When an user select a group:

The primary group of the user has to be changed.
The user can only see resources of the group selected.

Also, the user could select the All option to see all the resources of all the groups that the user belongs.
Interface Changes
FireEdge Sunstone will have a menu (as the views menu) to select beetween All option and the groups that the user belongs. If a groups it's selected:

Make a request to change primary group of the user.
Filter every resources GET request with filter=-4 to get only the resources of the primary group.

Progress Status

[ ] Code committed
[ ] Testing - QA
[ ] Documentation (Release notes - resolved issues, compatibility, known issues)

developed in #6122


Unable to install TensorFlow: No matching distribution found for TensorFlow!

When trying to install TensorFlow via pip, I encounter an error stating that no matching distribution can be found. The command I used and the error message are as follows:
C:\Users\Enes> pip install tensorflow
ERROR: Could not find a version that satisfies the requirement tensorflow (from versions: none)
ERROR: No matching distribution found for tensorflow

Operating System: Windows 10
Python Version: (Python 3.13.0)
I am currently using Python 3.13. Could this be related to compatibility with this specific Python version?
Could you provide guidance on how to resolve this issue, or suggest any compatible alternatives?

@bajramienes,
The error which you are facing is due to the mismatch of tensorflow compatible versions. I request the latest tensorflow v2.18 is compatible with the python 3.9-312. Kindly take a look at the official document for the compatible versions.
https://www.tensorflow.org/install/source_windows#cpu
Thank you!

All brand new Fedora 41 installations will face this. Please update TF to work with 3.13 default installs where we have no easy choice. Why is this even a problem?

the latest version, TensorFlow 2.18.0, supports Python versions 3.9–3.12, We have to wait to supports Python 3.13.0.

Hello @atrigupta, any news about this issue?

I'm afraid we'll have to wait may be next year for a new tensorflow release supporting Python 3.13... See here
I think the only alternative for the time being is to use Python 3.12.


PyTest not working in dev

Describe the bug
pytest does not start in dev, since it could not recognize arguments.
To Reproduce
Steps to reproduce the behavior:

Clean environment with Python 3.12.3: python -m venv venv
Activate env: source venv/bin/activate
Install project: pip install .
Try testing: pytest (Maybe add as depedency, for easy use)

$ pytest
ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: unrecognized arguments: --cov=PQAnalysis --cov-report=html
  inifile: /home/jog/projects/PQAnalysis/pytest.ini
  rootdir: /home/jog/projects/PQAnalysis

Expected behavior
Should result in test execution.

Did you try pip install .[test]?
The test dependencies are only optional dependencies. In the next release
to main this will be included in the developer guide in the documentation.
On Thu, 25 Apr 2024, 15:09 Josef M. Gallmetzer, @.***>
wrote:

Assigned #21 https://github.com/MolarVerse/PQAnalysis/issues/21 to
@97gamjak https://github.com/97gamjak.
—
Reply to this email directly, view it on GitHub
https://github.com/MolarVerse/PQAnalysis/issues/21#event-12608264751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASNGWAUH6QCFJN26XAVYWELY7D6AFAVCNFSM6AAAAABGY3QFG2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGYYDQMRWGQ3TKMI
.
You are receiving this because you were assigned.Message ID:
@.***>

pip install '.[test]' did work, but still same issue

Ok, I'll check it out.
On Thu, 25 Apr 2024, 16:41 Josef M. Gallmetzer, @.***>
wrote:

pip install '.[test]' did work, but still same issue
—
Reply to this email directly, view it on GitHub
https://github.com/MolarVerse/PQAnalysis/issues/21#issuecomment-2077381644,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASNGWARLHE4ATAJTMCUIJBLY7EIZZAVCNFSM6AAAAABGY3QFG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXGM4DCNRUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@galjos I reproduced now exactly each step as given in the description and it works on my side.
Could you try to write python -m pytest  instead

Works


Add checkbox specimen selection to data browser table.

One of the most requested features. Allow users to select multiple specimens from browser via checkbox.
┆Issue Number: HCAB-248

Dup of #992?

superseded by dx


No Blank or Null Defaults

Summary
Preference option: columns do not have a specified default
Please describe the problem you are trying to solve.
Talend really wants to respect the defaults, and so I often end up going back in and clearing defaults.
Like, just don't include default in the column definition at all.
Instead of
create table `Account` (`Id` varchar(18) default '', `Name` varchar(255) default '')

I'd do
create table `Account` (`Id` varchar(18), `Name` varchar(255))

I ended up doing this with my Contacts table anyway, and Talend liked it much better, honestly.
Proposed Solution
Add it to the preferences list.

I'm perfectly happy to get the defaults that actually mean something. I just don't like the ones that make Talend fight with me more.

Will need to check if this is a behavior of the library being used for SQL generation.  Blank vs null is important and nearly always annoying when it matters.

What happens when you uncheck the box to set blank default in preferences?  Does that achieve the desired result?

@allisonletts I think this is supported currently. Please re-open if there is a bug I should address or I misunderstood the ask.


build: Fix shellcheck errors

specify the path to cni-version.sh
only lint executable shell scripts
remove unused variable

This is a follow-up to https://github.com/cilium/cilium/pull/12013, as I forgot to run linter on the latest iteration of the code.

Coverage increased (+0.02%) to 36.926% when pulling a1e912605514ae85ad397c689a2c2c6a6e93790d on pr/errordeveloper/fix-images-lint-error into f2e181e0b330c6e644f7905dfefc7232c93798c6 on master.

@aanm thanks, I've update the commit message.


Support for CJS config file?

Hi! Would it be possible to also support a config file with a CJS export? All JS files located under /config contain CJS exports and are also linted with the node plugin for EsLint. Linting (with the default Ember EsLint configuration) fails when creating a configuration file for ember-intl-analyzer as suggested in the docs. At the moment I just ignore that file.
Thanks!

I think that should already be supported due to our use of https://github.com/standard-things/esm

Isn't that package meant for importing ES modules in Node land? I've tried the following, but it doesn't work:
module.exports = {
  whitelist: []
}

Isn't that package meant for importing ES modules in Node land?

yes, but their README says "By default, 💯 percent CJS interoperability is enabled so you can get stuff done." so I was assuming that it would just work with the snippet you posted above. if not I'm open to merging PRs that make both work.

Aha okay, I think I know what's up. I'm guessing .default on L86 is causing TypeError: Cannot read property 'whitelist' of undefined.
I thought it was the import that didn't work.


Update config_machines.xml and corresponding files

In this PR, I updated the file config_machines.xml, and likewise updated the module names and versions in chrysalis_gnu_openmpi.yaml. I did not notice any other place where it was obvious to make changes, but there are a lot of little changes and I'm not sure if we need to account for those. I will make some comments highlighting these changes to clarify whether they should or should not be updated in a different file.

Checklist

[ ] Testing comment in the PR documents testing used to verify the changes

@xylar Sorry about the comment confusion, I actually had several that I wanted your feedback on. I just re-wrote them so you could see them (instead of including them, accidentally, in a review). Would you mind looking at the other questions when you get a chance?

Little progress update: Just added what I think is the last of the changes from the E3SM update, and I am about to start adding all the other missing environment variables.

Everything looks good.  Let's see how testing with the pr suite goes on Chrysalis and Perlmutter with these changes.

@xylar I forgot to finish and push the last bit of the pm files. These are basically the same changes, except I did add what appeared to be a missing NETCDF env var - I can remove this if necessary but I figured I'd add it for now since I was in the files anyways. I figured since there were other NETCDF env vars that it might be OK to add the extra one. I can start testing now.

@xylar Just set up the conda env on pm and it appears to have been successful! These are the flags I tested with for reference:
./configure_polaris_envs.py --conda ~/miniforge3/ --env_name polaris_test --verbose --update_spack --spack $SCRATCH/spack_test --tmpdir $SCRATCH/spack_tmp --compiler gnu --machine pm-cpu --mache_fork altheaden/mache --mache_branch update-config-machines

@xylar gnu run of the pr suite on pm passed all tests, intel run failed the 10km threads test but passed all others. I will take a look at the environment variables again in the morning and see if there's anything that might have screwed up threading in particular. Here is the log file from the failed run:
threads-out.log

@altheaden, great!  It seems like it might be worth having me explore whether commenting back in one or more of these flags makes things pass for that thread test:
## purposefully omitting OMP variables that cause trouble in ESMF
# export OMP_STACKSIZE=128M
# export OMP_PROC_BIND=spread
# export OMP_PLACES=threads

In the meantime, I think we can proceed.  We will just want to make a Polaris issue reporting that that particular test on that particular machine and compiler is not producing bit-for-bit results as expected.  It's a little too early to add that report but if we see the same thing right before we're ready to merge the branch that updates to Polaris 0.4.0-alpha.1, we will post an issue and link to it in the comments about testing that version of Polaris.

@xylar After the if-statement change, the intel test had the same results as I got last night.

@altheaden, yes, that's what I saw, too.  I also reran after commenting in the OMP* environment variables and I still see small differences.  So this is a bug we're going to have to report to MPAS-Ocean developers to investigate.

Testing
@altheaden and I have used this branch to build Polaris' spack environment for:

Chrysalis

intel
gnu

Perlmutter-CPU

gnu
intel
nvidia

Perlmutter-GPU

gnugpu
nvidiagpu (not quite done yet)

We have run the Polaris pr suite with the first 4 configurations (the last 3 are not supported).  The one test thread test failed with intel on Perlmutter-CPU but we don't think that's related to these changes and will be reported for later investigation.
We ran the Omega CTests on Chrysalis with intel and gnu, and on Perlmutter-GPU with gnugpu.  This required #174 and some modifications to Polaris that will be included in the next update.


False negative build result for swift-sharing

https://swiftpackageindex.com/pointfreeco/swift-sharing/builds
Resolve Package Graph
unknown package 'swift-sharing' in dependencies of target 'WasmDemo'; valid packages are: 'spi-builder-workspace' (at '/Users/admin/builder/spi-builder-workspace'), 'swift-navigation' (from 'https://github.com/pointfreeco/swift-navigation'), 'carton' (from 'https://github.com/swiftwasm/carton'), 'JavaScriptKit' (from 'https://github.com/swiftwasm/JavaScriptKit')

Demo project is getting in the way. I thought we were dealing with this, need to check what we can do here.

Also visionOS and Linux should pass. visionOS has the same problem as above (which is for iOS), Linux fails with
<unknown>:0: error: upcoming feature 'StrictConcurrency' is already enabled as of Swift version 6
<unknown>:0: error: upcoming feature 'DisableOutwardActorInference' is already enabled as of Swift version 6
<unknown>:0: error: upcoming feature 'GlobalActorIsolatedTypesUsability' is already enabled as of Swift version 6
<unknown>:0: error: upcoming feature 'InferSendableFromCaptures' is already enabled as of Swift version 6

which should have been fixed by #3529

The Linux build fails with a plain Swift image:
❯ git clone https://github.com/pointfreeco/swift-sharing.git
❯ cd swift-sharing
❯ git rev-parse @
a8e2aa1c1655c2c295a5391bf969a4d7a7b4f548
❯ docker run --rm -it -v $PWD:/host -w /host swift:6.0.2 swift build
...
Building for debugging...
/host/Sources/Sharing/SharedKeys/AppStorageKey.swift:434:18: error: cannot find type 'NSKeyValueChangeKey' in scope
432 |         forKeyPath keyPath: String?,
433 |         of object: Any?,
434 |         change: [NSKeyValueChangeKey: Any]?,
    |                  `- error: cannot find type 'NSKeyValueChangeKey' in scope
435 |         context: UnsafeMutableRawPointer?
436 |       ) {

While we're getting a different error, I'll skip this for now.

I've deployed builder 4.58.2 and re-triggered the Swift 6 builds.


Add support for Magento AMQP configuration

Environment variable names have been based on what Magento names things here: https://devdocs.magento.com/guides/v2.0/install-gde/prereq/install-rabbitmq.html

In the base image here would be fantastic!


How i can call step.Run or step.Invoke concurrently in goroutines

Example code inside function that run step.Run / step.Invoke in parallel and collect results
			var wg sync.WaitGroup

			inputs := []string{"a", "b", "c"}
			inputsLength := len(inputs)

			results := make([]string, inputsLength)
			errs := make([]error, inputsLength)

			for index, item := range inputs {
				wg.Add(1)
				go func(index int, argument string) {
					defer wg.Done()
					run, err := step.Run(ctx, "my-step", func(ctx context.Context) (string, error) {
						// some computation
						// use argument
						return argument, nil
					})

					if err != nil {
						errs[index] = err
						return
					}

					results[index] = run
				}(index, item)
			}

			wg.Wait()

			/// use results

Looking forward to it

@rullyalves, this is the approach we're considering:
https://github.com/inngest/inngestgo/pull/51
Even though waitgroups are super common in Go, we can't support them right now because we use panics to interrupt control flow. This may change in the future if we find a replacement for our panic-based interruption approach

@goodoldneon Wouldn't it be possible to use recover to recover possible panics?

@goodoldneon I checked the implementation (https://github.com/inngest/inngestgo/pull/51) and it looks great to me

We could get waitgroups working if users were diligent about applying the following recover-and-repanic pattern to every goroutine:
func Fn(ctx context.Context, input inngestgo.Input[any]) (any, error) {
	var recovered any
	wg := sync.WaitGroup{}
	wg.Add(1)

	go func() {
		defer wg.Done()
		defer func() {
			if r := recover(); r != nil {
				// Store panic so we can repanic outside this goroutine
				recovered = r
			}
		}()

		_, _ = step.Run(ctx, "fetch todo", func(ctx context.Context) (int, error) {
			return 1, nil
		})
	}()
	if recovered != nil {
		// Repanic so the SDK's recover logic can run
		panic(recovered)
	}

	return nil, nil
}

But we think that pattern hurts readability and is a footgun. That footgun is exacerbated by our intentional panics and the fact that a Go process crashes on unrecovered panics in goroutines

Would something at that level work ?
type FnStep[T any] struct {
	ID string
	Fn func(ctx context.Context) (T, error)
}

type ResultFn[T any] struct {
	result T
	error
}

func RunStepOnParallel(ctx context.Context, fns []FnStep[any]) []ResultFn[any] {
	var recovered any
	mut := sync.Mutex{}
	wg := sync.WaitGroup{}

	results := make([]ResultFn[any], len(fns))

	for i, fn := range fns {
		wg.Add(1)
		go func(index int, fn FnStep[any], mut *sync.Mutex) {
			defer wg.Done()
			defer func() {
				mut.Lock()
				if r := recover(); r != nil {
					// Store panic so we can repanic outside this goroutine
					recovered = r
				}
				mut.Unlock()
			}()
			result, err := step.Run(ctx, fn.ID, fn.Fn)

			results[index] = ResultFn[any]{result: result, error: err}
		}(i, fn, &mut)
	}

	if recovered != nil {
		// Repanic so the SDK's recover logic can run
		panic(recovered)
	}

	return results
}

I think we could get your example working, but that's a lot of stuff that users need to remember to do every time. Supporting common concurrency patterns in Go is important to us, but we're afraid that all the extra panic-related stuff cancels out the benefit of common patterns

I thought about maybe incorporating the function I gave as an example into the ingest sdk, it seems like it would be a relatively simple solution to meet this standard, I will test it in my codebase, but do you think it has promise ?

So isn't it enough to execute the steps in different goroutines and wait for them? Is it also necessary to find out which steps are parallel and send them to ingest? Why?

We never want to execute multiple steps within the same HTTP request since that decreases our "as close to exactly-once execution as we can get" guarantee.
Let's say we execute 2 steps in parallel within the same HTTP request.
Happy path
We wait until both steps are done and then put their outputs in the response back to the Inngest Server. Great! No issues.
Unhappy path
Step 1 completes but then step 2 irrecoverably panics. The whole Go process crashes and step 1's output isn't sent back the to Inngest Server. Now the Inngest Server thinks step 1 didn't finish so it tries to run it again. Now we ran the logic in step 1 twice.

in the worst case, some step would be executed more than once, right?
so the code I posted could work, but there would be this possible case where one of the steps could fail irreparably, right? ok, I think for my use case I can deal with this while there is no official update with this function

I don't think it would work now because our control flow interrupt of the first completed step would leave the other steps hanging. Also, Inngest Servers are incapable of handling multiple step outputs in a single HTTP response.
I'll ask the team if they're OK with merging the group.Parallel PR to unblock you. I think we can get it in soon

Thank you, I look forward to hearing from you, if I can help in any way, please let me know.

@rullyalves, we released an experimental version of group.Parallel in v0.7.4. Here's our integration test that gives an idea about how to use it:
https://github.com/inngest/inngestgo/blob/v0.7.4/tests/parallel_test.go#L55-L84

Thanks for your attention, I will update my workflows with this version of the library and tests, but this should greatly improve the execution time of the steps

We don't have a specific limit for parallel steps. They're subject to the overall 1000 step limit for a function run, so you should be able to do 1000 steps in parallel if there are no other steps.
That said, right now our parallel step execution model is kind of inefficient: each parallel step requires 2 HTTP requests. We'll change this in the near future, but for now it's something to consider since it affects your ingress bandwidth

I made a code, in theory this would be the use ?
I will call the steps in parallel, collect the list of Result, and if there is an error, I return it so that the function tries again and re-executes the steps that resulted in an error?
			rs := group.Parallel(ctx, func(ctx context.Context) (any, error) {
				return step.Run(ctx, "step a", func(ctx context.Context) (any, error) {
					return nil, nil
				})
			}, func(ctx context.Context) (any, error) {
				return step.Invoke[any](ctx, "moderate-texts", step.InvokeOpts{
					FunctionId: "step b",
				})
			})

			anyError := collections.FirstWhereOrNil(rs, func(result group.Result) bool {
				return result.Error != nil
			})

			if anyError != nil {
				return nil, anyError.Error
			}

			classifyTextResult := rs[0].Value
			moderateTextResult := rs[1].Value

Retries are already handled automatically. A step.Run call only returns an error after retries are exhausted.
Note that step.Invoke's retries are the responsibility of the invoked function. In other words, if you invoke a function with 3 retries and it fails, then step.Invoke will return an error with no further retries

Returning the step.Run error won't cause any more retries since the retries already happened.
Try running this function:
inngestgo.CreateFunction(
	inngestgo.FunctionOpts{
		ID:      "my-fn",
		Name:    "my-fn",
		Retries: inngestgo.IntPtr(1),
	},
	inngestgo.EventTrigger("my-event", nil),
	func(ctx context.Context, input inngestgo.Input[any]) (any, error) {
		_, err := step.Run(ctx, "a", func(ctx context.Context) (any, error) {
			fmt.Println("inside step")
			return nil, fmt.Errorf("oh no")
		})
		fmt.Println("after step")
		return nil, err
	},
)

Since it's configured for 1 retry, you'll see the following in your terminal:
inside step
inside step
after step

And then the function will fail. The 2 retries are for the step, which means step.Run returns the error after the retry is done

sorry, English is not my native language, so I may not be expressing myself well, but I wanted to ask if the implementation I put in the code example is correct, I understand that steps by default try again and only return error or success after exhausting the attempts and that the same happens for a function

That code is the most common way people use parallel steps: fail the function if at least 1 parallel step errors. The code looks good, except the comment would be:
// check if there is any error, if there is then fail the function

The return nil, anyError.Error will immediately fail the function because retries have already been exhausted


[x] add --no-doc option to disable doctests for xtest

Doc tests add significant overhead when quickly iterating on tests, so it's often convenient to disable them.
Open to any better suggestions for the name --no-doc.

I think cargo uses --tests. Maybe do the same?

@phlip9 Yeah lets try and keep the options similar to what cargo uses, so if  you want --lib passed then x test should also take an option named --lib

@phlip9 Yeah lets try and keep the options similar to what cargo uses, so if you want --lib passed then x test should also take an option named --lib

@bmwill Indeed I would prefer to have named this --lib but the description seems to conflict with --unit "Only run unit tests" vs cargo test --lib "Test only this package's library unit tests".

I'm fine if we tweak the documentation for --unit then, since it basically just doesn't run testsuite tests

@bmwill ok! renamed --no-doc to --lib and (hopefully) clarified the command descriptions

@bors-libra r+

:pushpin: Commit f719b2b has been approved by bmwill

:hourglass: Testing commit f719b2b537cd4a5cb49a226b87340e655e43befd with merge ab0283dacd84ef10fe19f7ae69cbb52143f2bd82...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra retry

:hourglass: Testing commit f719b2b537cd4a5cb49a226b87340e655e43befd with merge f7e70cab188adc0967f8b3d152536df7594d1e57...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: bmwill
Pushing f7e70cab188adc0967f8b3d152536df7594d1e57 to master...


⚠ Homepage (omg.lol) has degraded performance

In afab759, Homepage (omg.lol) (https://8bit.lol/) experienced degraded performance:

HTTP code: 503
Response time: 2774 ms

Resolved: Homepage (omg.lol) performance has improved in a9dd232 after 15 minutes.


UI: pressing "Reload" button in certain list views messes up pagination

In either of these list views:
Configure -> Tasks
Services -> Requests

hitting the "Reload" button messes up pagination of the displayed view.
For example in Configure -> Tasks, when navigating back and forth through the list of displayed
view, I'm making the following HTTP requests:
GET "/miq_proxy/change_tab?page=2&tab=2"
GET "/miq_proxy/change_tab?page=3&tab=2"
GET "/miq_proxy/change_tab?page=4&tab=2"

Now I hit the "Reload" button:
POST "/miq_proxy/button?pressed=miq_task_reload"

And now I try to navigate to the next list page again:
GET "/miq_proxy/button?page=2&pressed=miq_task_reload"

which results into an ISE.
Similarly, if I use the "Filter By" form to change the parameters of the displayed list and then
try to navigate through the list:
GET "/miq_proxy/tasks_button?button=apply&page=2"

Which -- again -- results into ISE.

I believe this issue should be now closed, the problem described here has been
addressed with pull request #1231


pull request for e2e test at 11/11/2016 01:26:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Market card incorrectly states "No liquidity"

This makes has a pool but no volume (567 on testnet):

Closed in #713


"User is not logged in." displayed on website

I have a weird problem I am unable to fix. When I login into my site I encounter 3 problems:

The URL has a weird extension I am unable to remove.
The two buttons "Jackpot" and "Coinflip" are shifted down a bit.
If you remove the navbar and the background in through the Chrome console you see a "User is not logged in." text in the top left corner of the page, even though I clearly am logged (I see my avatar and name on the top right of the navbar).

You can check it out yourself on the website: http://www.csgoorb.com
Here is a screenshot of all 3 problems: https://gyazo.com/8ae693682a1e109a8585c9b38527e8a6
I would be really thankful if you could tell me what is causing this problem and tell me a fix for it! I am still a beginner, so I am not very experienced with php. :)

I fixed it. The problem was a wrong path for the login and logout page. It orginally was '#', I changed it to '../' and now it works :)


⚠ Bofrost.fr has degraded performance

In b9a42d3, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 903 ms

Resolved: Bofrost.fr performance has improved in 875ab66 after 6 minutes.


How crop works?

Hi,
I couldn't figure out if I can crop at arbitrary points, similarly as with ImageMagick/GraphicsMagick:
crop
Crops the image to the given width and height at the given x and y position.

gm("img.png").crop(width, height, x, y)

So, I would like to crop a small portion of an image at exactly x, y. Is this possible?
Thanks.

I just realized, that extract seems to do what I was asking.
I'll close this now as it's resolved. However, it's not totally clear what crop now does then :) Maybe make it more clear and point to the extract function from where the crop is explained?

Hello, you're not the first to run into the *magick crop vs libvips extract confusion.
I expect the existing crop function to soon be deprecated, instead becoming an optional parameter of the resize operation. Whether we (eventually) recycle crop to become a synonym for extract remains to be seen :)

@lovell any update on this? I think it's pretty confusing to everyone coming from any kind of photo manipulation tool to have an API called crop that doesn't accept coordinates. Extract doesn't seem very intuitive either as the method for "cropping with coordinates" as indicated by a few Issues that ask how to crop with coordinates.

Please subscribe to #1135 for updates.


Update Ginkgo due to deprecation warning

When running testes locally (via go test ./...), I see the following output:
You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

  You are using a custom reporter.  Support for custom reporters will likely be removed in V2.  Most users were using them to generate junit or teamcity reports and this functionality will be merged into the core reporter.  In addition, Ginkgo 2.0 will support emitting a JSON-formatted report that users can then manipulate to generate custom reports.

  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.5

I upgraded all dependencies and fixed Gingko in 0.9.10.


Bump Polars Version to 0.34

Is your feature request related to a problem? Please describe.
Faer right now doesn't work with Polars 0.34. We should update it and make sure nothing breaks and the tests still pass.
Describe the solution you'd like
polars = { version = "0.34", optional = true, features = ["lazy"] }
and see if existing functions still work.
Describe alternatives you've considered
NA
Additional context
NA
Thanks in advance

updated to 0.34 in the latest release (0.15.0)


DOC: sparse: Several functions are missing the 'Returns' section of their docstring

Issue with current documentation:
The docstrings of the following functions in scipy.sparse are missing the 'Returns' section:

diags
diags_array
eye
eye_array
identity
save_npz
spdiags

Nothing urgent here--what each function returns is pretty obvious in all cases--but it would be nice to fix these to conform to the docstring standard.
save_npz is pretty clearly a "side effects only" function and returns None, so it doesn't necessarily need a 'Returns' section.

working on it

It would be pretty easy to add an automated check for this. There are false positives - that is, functions with no return section which we might not care about - and we can add exceptions for those. But it would catch the addition of new functions without important sections.

I've been using my own script find_docstring_issue.py, but numpydoc probably already covers all that and more.  For example, here's the report generated by `numpydoc lint scipy/sparse/_construct.py:

We have some checking of docstrings in refguide-check.py still. Would be great to consolidate that with numpydoc validation and turn it on across the whole scipy codebase.
This a lot of churn though (SA02, PR08 above). Lots of "good first issue" material, too.

that would be a lot for the whole SciPy codebase 😅 but might be manageable if there is a good system for selecting which files to lint piece by piece. I'm using the numpydoc pre-commit hook in array-api-extra now (https://github.com/data-apis/array-api-extra/pull/67) and it's working well so far (modulo https://github.com/numpy/numpydoc/issues/561)


⚠ Bofrost.fr has degraded performance

In 6fb5d15, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 991 ms

Resolved: Bofrost.fr performance has improved in b86417c after 6 minutes.


bitcoind changed datadir

i changed datadir in bitcoind.conf and now it wont output nothing? is there a ways to fix it?

Hi,
The status script communicates with bitcoind via RPC, so any issues with bitcoind aren't really my area I'm afraid.
What happens when you load the status page with debug switched to true in php/config.php?
Thanks,
Craig

it works now, probably cache or so :)


ModalPortal not being cleaned up after componentWillReceiveProps

Summary:
In my codebase, react-modal leaves behind its current ModalPortal element after receiving new props. It creates a new portal with the new data as expected, but it does not clean up the old ModalPortal element.
Steps to reproduce:
I've tried to reproduce the behavior in a Codepen and in a separate demo app, but I couldn't reproduce the issue. I only encounter the issue in an (unfortunately closed-source) application I'm developing.
Expected behavior:
Only one ModalPortal should exist. ModalPortal elements should not be left behind.
Additional notes:
I was encountering this issue both before and after the 3.0.0 release.
I assume this issue may be somehow external to react-modal, since I can't reproduce it elsewhere. But I have no idea how my application environment could be getting in react-modal's way of removing its portal, and I'm running out of ideas.

@B-Reif Can you give a little bit more info about how your modal is setup, defined and/or used?

I've faced similar issue when ModalPortal was not removed. In my case the problem was in lifecycle of root element for my React app. In my scenario root element was vanished, but React did not get notification about it, so child Modal component was not unmounted and as result ModalPortal was not unmounted too. I've solved my issue by direct call of ReactDOM.unmountComponentAtNode() at appropriate moment.

@slava-osipov-qs can you make a reproducible example with this?

I guess such example will not be usefull. The problem was not in react-modal component, problem was in environment. I injected React app into Angular app, so it was my responsibility to manage React app initialization and destroying. I.e. it is not a responsibility of react-modal.
But this issue caused me to think about single instance of ModalPortal associated with AppElement, that is assigned with Modal.setAppElement(). Could you think about possibility to have only single instance of ModalPortal? It also could reduce memory usage, if one want to have thousands of Modal instances in app.


Kubernetes Dashboard proxy: scrolling pages not working

Pages are not working, you can click 'next page', and it appears to work, showing the page has changed. But the data doesn't change.

Same with pod filtering, but not a huge priorit.
On Mon, Apr 15, 2019 at 09:15 Marcus Bowyer<EMAIL_ADDRESS>wrote:

Pages are not working, you can click 'next page', and it appears to work,
showing the page has changed. But the data doesn't change.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nforgeio/neonKUBE/issues/493, or mute the thread
https://github.com/notifications/unsubscribe-auth/AJA3zAJv-_LAg8nlKII-dhejBRUTNPCxks5vhKWmgaJpZM4cwXUS
.

Fixed


[Bug] No such config pack "DEFAULT"

recently im updated multiverse core and this started happening

mv create world_name NORMAL -g Terra:DEFAULT
[10:45:54 WARN]: [Multiverse-Core] Failed to get the default chunk generator: java.lang.IllegalArgumentException: No such config pack "DEFAULT"
[10:45:54 WARN]: [Multiverse-Core] This is a bug in Terra, NOT a bug in Multiverse!
[10:45:54 INFO]: Invalid generator! 'Terra:DEFAULT'. Aborting world creation.

Server version: Paper spigot 1.15.2
Client version: Vanilla 1.15.2
Terra version: Terra 5.1.0-BETA (i also tried to use older)

can you show me what's in the /plugins/Terra/packs/ directory?

Paper spigot 1.15.2

Read the installation instructions for legacy versions. You will need to downgrade the legacy pack.


need access right for pretrained model

thanks for your great job!
I want to try, but there need access rights for the pretrained model.
by the way, how to train?

same

same

thanks for your great job! I want to try, but there need access rights for the pretrained model. by the way, how to train?

Has it been resolved? You need permission, but there is no message after applying. If you have already downloaded it, could you please send me a copy? Thank you very much


Split misc routines from math.cc

Part of #7143.
~Depends on #7261.~
~Depends on #7270.~

Jenkins, test this please

Jenkins, test this please

Jenkins CI test (for commit 78aa9448d864e369ddfe69c930ad67582c7a3bd3, target branch master) succeeded!


Fixing schema.{min,max}Items message mixup.

Currently maxItems is shown for to short arrays and minItems for to long arrays.
It should be exactly the other way around:

Woops! Good catch, and thanks for the PR!

No problem, they call me the code review :grin:
Thanks for the fast merge.


[Cobalt] Cobalt v7 api has been shut down

Extension
https://www.raycast.com/aelew/cobalt
Raycast Version
1.85.2
macOS Version
15.0.1 (24A348)
Description
This extension no longer works due to the following error when trying to download anything from YouTube.
the cobalt v7 api has been shut down on nov 11th 2024. see https://github.com/imputnet/ cobalt/discussions/860 for more information.

Steps To Reproduce

Using the latest Raycast and Cobalt version
Open extension and paste YouTube video link
Hit Start Download
Error!

Current Behaviour
No response
Expected Behaviour
No response

@raycastbot assign me


Is @babel/core unused and can it be removed?

Your Environment

Prettier version: 3.3.3
node version: 22.10.0
package manager: npm@9
IDE: VSCode

Describe the bug
@babel/core does not seem to be used at all in the package, and I believe it is unnecessarily adding 21MB / 20 dependencies to the bundle. See the package's dependency graph with and without @babel/core.
I am unfamiliar with Babel, so I apologize if just having it installed is doing something behind the scenes. If not, could @babel/core be removed?

Good callout.  I think this is a holdover from the upstream we forked from.  We get the parser from @babel/parser instead of @babel/core, so I believe you're right that we can remove the dependency.  Would you like to submit a PR and we can try it out?

Thanks for addressing this! Sorry I wasn't able to make a PR, I've been busy.

Thank you!

Thanks for bringing it up!  We'll try to get it released asap.


LIS-Jekyll site needs 'Cite LIS' info in a prominent location.

I couldn't find 'How to cite LIS' info in our new site like we have in our legacy cite front page top paragraph.
So,
a.  we should add it in the new front page in a prominent place and
b.  include the past relevant publications, NAR 2005 and 2016 in addition to Redsun et al. 2022 Methods in Mol Bio article.
For the attention of @cann0010 and @adf-ncgr to assign this task.
c. Should we add the 2022 publication in our legacy site too? Many still look at it judging from the contact LIS emails we get.

@alancleary proposes a new page for all publications relevant to the project with the cite us at the top.


Update ActiveEffectConfig to Foundry VTT 0.7.9

Which class should be updated?
ActiveEffectConfig
For which version should the class be updated?
Foundry VTT 0.7.9

Taking this

Fixed by #282


migrate to v4 yolo for plates search

Trained yolov4 for plates search: russian individual/taxi/police/motobikes/military/government plates
Updated script for downloading weights

Merging due conflicts

Also need to retrain YOLOv4 with last stable release of Darknet by AlexeyAB


Remove Super prefix from supertexttransformer

the static failures are due to an issue with the pre-commit checker that is being worked on.  I will comment again when it is fixed.

Thank You!

The issue should now be resolved.  Please rebase against the latest master branch and run pre-commit run -a to ensure that all of your files are correctly formatted with the updated linter versions.

There may occur some import errors as valid autoai-libs are still on the feature branch

@shinnar  I've run the failing test locally with the autoai-libs from test pypi (<IP_ADDRESS>) and it run successfully. Although, to make an official release of core and libs we would like to test everything together with lale. Is there any possibility to make a test pypi lale release from my fork ?

Locally the tests work for me fine with latest autoai-libs from prod pypi (1.12.6, https://pypi.org/project/autoai-libs/). I can see in the install dependencies section of failing tests that the latest autoai-libs version is not installed:
 Requirement already satisfied: autoai-libs in /opt/hostedtoolcache/Python/3.6.13/x64/lib/python3.6/site-packages (from lale==0.4.15) (1.12.5)
Should I add a requirement to autoai-libs >=1.12.6 ?

yes, that makes sense.


[RE-OPEN] Include .ipynb to sphinx-docs via myst-nb

Re-opened #521 with the local branch

Looks nice. Can we remove the subheadings on the overview page in Examples -> Contents?

Looks nice. Can we remove the subheadings on the overview page in Examples -> Contents?

Done in 161298d.


fix(theme): apply tw nested group

closes #3544
closes #2324
closes #2959

📝 Description

Applied nested group to components so that styles from other components won't mess up with others.
⛳ Current behavior (updates)
let's say there is a switch component inside a table row with select button. clicking select button would also toggle the switch. The reason is that when we click select, data-selected for select will be set to true. However, all group-data-[selected=true]:* in switch component will be applied as well since all components share the same parent group.
original PR: https://github.com/nextui-org/nextui/pull/3658. rollback due to breaking changes and not all components are required to apply.
pr3909-before-demo.webm
🚀 New behavior

pr3909-after-demo.webm
💣 Is this a breaking change (Yes/No):

Yes. Users need to add /tr or /th to custom styles for table.
📝 Additional Information

Summary by CodeRabbit

New Features

Introduced a nested group feature for enhanced Tailwind CSS styling.
Improved styling capabilities for table components with updated class names.

Bug Fixes

Enhanced specificity in table row styling to ensure correct visual representation.

With version 2.6.8 the issues are getting worse

Checkbox design is broken
The checkboxes, all checkboxes and switch nothing is working in UX (under the hood the switches are working)
Switch design is buggy (some text might be trying to sneak peek)

"@nextui-org/react": "^2.6.8",
"@nextui-org/system": "2.2.5",
"@nextui-org/theme": "2.2.9",
"next": "^14.2.12",
"next-themes": "^0.2.1",
"react": "18.3.1",
"react-dom": "18.3.1",

@mayeenulislam why are you using the latest @nextui-org/react and outdated @nextui-org/system and @nextui-org/theme? In fact, system and theme packages are also in @nextui-org/react. They are only required if you use individual packages. Therefore, you may try remove @nextui-org/system and @nextui-org/theme, change the import from @nextui-org/react and try again. If the issue still persists, please create a new issue with a minimal reproducible sandbox. Thanks.

The issue is resolved after removing the unnecessary packages as suggested by @wingkwong
Thank you so much.


(Mix) Could not start application, returned an error: shutdown: failed to start child: Boltx

I've added Boltx to my Supervision tree.
Config:
config :boltx, Bolt,
  uri: System.get_env("NEO4J_HOST") || "bolt://localhost:7687",
  auth: [username: "neo4j", password: System.get_env("NEO4J_PASSWORD") || "password"],
  user_agent: "boltxTest/1",
  pool_size: 15,
  max_overflow: 3,
  prefix: :default

application.ex
%{
       id: Boltx,
       start: {Boltx, :start_link, Application.get_env(:boltx, Bolt)}
}

While starting the server, I got the following error.
** (Mix) Could not start application accounts_service: AccountsService.Application.start(:normal, []) returned an error: shutdown: failed to start child: Boltx
    ** (EXIT) an exception was raised:
        ** (UndefinedFunctionError) function Boltx.start_link/6 is undefined or private
            (boltx 0.0.3) Boltx.start_link({:uri, "bolt://localhost:7687"}, {:auth, [username: "neo4j", password: "password"]}, {:user_agent, "boltxTest/1"}, {:pool_size, 15}, {:max_overflow, 3}, {:prefix, :default})
            (stdlib 3.17.2) supervisor.erl:414: :supervisor.do_start_child_i/3
            (stdlib 3.17.2) supervisor.erl:400: :supervisor.do_start_child/2
            (stdlib 3.17.2) supervisor.erl:384: anonymous fn/3 in :supervisor.start_children/2
            (stdlib 3.17.2) supervisor.erl:1250: :supervisor.children_map/4
            (stdlib 3.17.2) supervisor.erl:350: :supervisor.init_children/2
            (stdlib 3.17.2) gen_server.erl:423: :gen_server.init_it/2
            (stdlib 3.17.2) gen_server.erl:390: :gen_server.init_it/6
            (stdlib 3.17.2) proc_lib.erl:226: :proc_lib.init_p_do_apply/3

Can you please check this, and suggest a better way to add Boltx to the application supervisor?

Thanks for reporting.
It should work, I'll check and send a fix :smiley:

I have been reviewing and noticed that, when refactoring Bolt Sips, I removed the functionality as an application. Initially, Boltx was designed as a library with the intention of creating an adapter for Ecto, similar to how postgrex, myxql, and ecto_sql do.
However, at that time, it doesn't make much sense to not provide an adapter or application. Therefore, I plan to initiate a minimal adapter in this repository to later migrate it to a standalone repository.
This would be the minimum needed to integrate it into an application, like Bolt_Sips does.

I made a correction that prevents the process from starting and added documentation on how to integrate it into an application. The documentation is available in the README. A new version, v0.0.4, is now available.
You need to make two changes to your configuration. First, you have to add the 'name' key to be able to give a name to the process, and second, send the configuration as a list.
application.ex
%{
  id: Boltx,
  start: {Boltx, :start_link, [Application.get_env(:boltx, Bolt)] },
}

config.ex
config :boltx, Bolt,
  uri: "bolt://localhost:7687",
  auth: [username: "neo4j", password: "password"],
  user_agent: "boltxTest/1",
  pool_size: 15,
  max_overflow: 3,
  prefix: :default,
  name: Boltx

Then you can use it like this:
iex> Boltx.query!(Boltx, "return 1 as n") |> Boltx.Response.first()
%{"n" => 1}


resource/nifcloud_security_group_rule: Change import specification

Description

resource/nifcloud_security_group_rule: Change import specification

How Has This Been Tested?

[ ] Acceptable 🍋
[ ] Run the acceptance test.

TF_ACC=1 go test ./nifcloud/acc/... -v -count 1 -parallel 20 -timeout 360m -run TestAcc_SecurityGroupRule_Cidr

TF_ACC=1 go test ./nifcloud/acc/... -v -count 1 -parallel 20 -timeout 360m -run TestAcc_SecurityGroupRule_Source

[ ] Successful import as the example in the documentation

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (improves code quality but has no user-facing effect)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation

Test Result
$ TF_ACC=1 go test ./nifcloud/acc/... -v -count 1 -parallel 20 -timeout 360m -run TestAcc_SecurityGroupRule_Cidr
go: downloading github.com/apparentlymart/go-cidr v1.1.0
=== RUN   TestAcc_SecurityGroupRule_Cidr
=== PAUSE TestAcc_SecurityGroupRule_Cidr
=== CONT  TestAcc_SecurityGroupRule_Cidr
--- PASS: TestAcc_SecurityGroupRule_Cidr (181.49s)
PASS
ok      github.com/nifcloud/terraform-provider-nifcloud/nifcloud/acc    181.513s
?       github.com/nifcloud/terraform-provider-nifcloud/nifcloud/acc/helper     [no test files]
$
$ TF_ACC=1 go test ./nifcloud/acc/... -v -count 1 -parallel 20 -timeout 360m -run TestAcc_SecurityGroupRule_Source
=== RUN   TestAcc_SecurityGroupRule_Source
=== PAUSE TestAcc_SecurityGroupRule_Source
=== CONT  TestAcc_SecurityGroupRule_Source
--- PASS: TestAcc_SecurityGroupRule_Source (183.65s)
PASS
ok      github.com/nifcloud/terraform-provider-nifcloud/nifcloud/acc    183.667s
?       github.com/nifcloud/terraform-provider-nifcloud/nifcloud/acc/helper     [no test files]
$

$ terraform import nifcloud_security_group_rule.example IN_TCP_0_65535_<IP_ADDRESS>/0_allo
wtcp
nifcloud_security_group_rule.example: Importing from ID "IN_TCP_0_65535_<IP_ADDRESS>/0_allowtcp"...
nifcloud_security_group_rule.example: Import prepared!
  Prepared nifcloud_security_group_rule for import
nifcloud_security_group_rule.example: Refreshing state... [id=IN_TCP_0_65535_<IP_ADDRESS>/0_allowtcp]

Import successful!

The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.

$


gone from the chrome store??

Is this extension still being worked on?  It seems to have disappeared from the Chrome store.

Any chance to get it back? This was really the best tool of all the alternatives.

I need to rework the icon to get it back in the store, as the current icon uses the Chrome logo in a manner that doesn't comply with Google's branding standards. I haven't gotten to it yet; I'll do so this weekend.

Good news, thanks for the update.

Submitted an updated version this morning. I'd expect it to be back in the web store shortly.

thank you so much! It has been published now.

Yup, sorry about the delay. Glad you're still using the extension, despite the brief period of unavailability! :)


Migrating datapackage-validat-py to this repository

This fixes #37

@vitorbaptista ready to merge.


Added comma

Added comma after introductory clause to be grammatically correct.

Brief introductory phrases of five words of fewer do not require a comma.

Brief introductory phrases of five words or fewer do not require a comma.


Bump versions for the subset errors computation

This PR updates the versions so that we can update rustc to compute subset errors:

the test polonius-parser crate now supports placeholder loans and known subsets
the polonius-engine crate now supports the new input facts, new output errors, and computes subset errors where some outlives annotations might be required between free regions, for a function to be valid
the polonius crate now supports the new facts for the ./inputs datasets, and tests these new errors

r? @matthewjasper


group utilities files in folder

create a folder named gb_utils and add the following files to it
greenberry_print
greenberry_lex
greenberry_parse
greenberry_plot
greenberry_search
greenberry_var_type

fix imports in greenBerry.py after

I would like to help with this issue but I'm not entirely sure on how to fix the imports in the greenBerry.py afterwards

@phamt2 just add an init.py in utils folder then from utils.greenberry_print import ...

Hi, can I work on this, if no one is?

Is anybody currently assigned to this? Otherwise I want to work on this.


Fixed issues based on comments.

Signed-off-by: Patrick-LuoYu<EMAIL_ADDRESS>/assign @FeynmanZhou @duanjiong @zheng1

/lgtm

/lgtm


Updating Github workflows

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
see 2 files with indirect coverage changes


Choosing your own tasks as a SD is good, but some had the impression it kept people form doing tasks

Simon our PO did a poll, and most of us voted for picking tasks as soon as you start working on the task and thus they are in progress.

Closing this as the last retro during sprint-06 accepted closing this impediment.


Translate CONTRIBUTING.md to spanish

What does this PR do?
Improve repo
For resources
Description
Translate CONTRIBUTING.md to spanish.
Why is this valuable (or not)?
Spanish is the third most spoken language in the world. Completing transversal files to spanish.
How do we know it's really free?
N/A
For book lists, is it a book? For course lists, is it a course? etc.
N/A
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Followup

Check the output of Travis-CI for linter errors!

excellent!


Translate login/sign up/password recover pages

The SolidusI18n::ControllerLocaleHelper module is required to translate pages.
This is included on Spree::BaseController but not on the solidus_auth_devise controllers.
This PR adds the module to the missing controllers.
Closes #10

🚢

@alepore could you please rebase

@alepore sorry, can you rebase again (last time)? I’m going to merge as soon as specs pass. Thanks!

😭


sex

Dear rsource:
Please add the sex map script immediately. I believe it will improve the quality (and availability) this repo aims for.
To you, Arcs <3

Dear @arcy-at,
This has always been a planned script to be added to the repository, our developers are at hard work creating this script to bypass the ROBLOX filter and run on unfortunate-resourced machines, we are working on this as priority and as fast as we can!
Thank you for reaching out to us about your input!


Change Skylark load statements to use labels rather than paths. [phab:D753]

Created by shahms at 2016-03-03 21:39:21:
Load from labels

schroederc accepted this revision at 2016-03-03 21:40:46

shahms closed via commit fbaf499c581bb228adc83ea476c5bcb28461615c at 2016-03-03 21:42:18


[1.16.5] The latest version is incompatible with realms.

Mod Version: DynamicSurroundings-1.16.4-<IP_ADDRESS>.jar
Forge Version: 1.16.5-forge-36.0.43
Description:
The game did not crash. When I tried the latest version of the mod on Realms, it froze me in place and set me in survival mode, no matter what mode I was on previously. I could only interact with the blocks around me. My movement wasn't working.
I tested switching back to an earlier version of the mod(DynamicSurroundings-1.16.4-<IP_ADDRESS>.jar) and everything was fine again. I was back to creative mode and I could move.
This was also the case when there was no Dynamic Surroundings Mod.
DynamicSurroundings-1.16.4-<IP_ADDRESS>.jar worked fine in a single-player world, just not on realms.
I have 15 other mods (including OptiFine) that I have downloaded. I updated Forge a couple of days ago.
I'm new to mods so I'm just starting to figure things out.

Can you link the debug.log file from a session that gives you the problem?  You can find it in the logs folder where the Minecraft instance is located.

I am also having this same issue.  On this same note, DynamicSurroundings was also crashing any clients that connected to a server with SimplyJetpacks version <IP_ADDRESS> installed, for whatever reason.  Downgrading either of the mods fixes that problem, though I think the problem with the other mod is due to a non-existent null pointer check.
With that being said, the file that contains my log is buried somewhere in my logs file and I'm not sure which one it is; I'd rather not give you false information.  I'll immediately report back if I encounter the issue again.

@FoxMcloud5655 I would like to see the log with the crash even it is the other mod.  Maybe there is something I can tighten up in code on my side.  Also, as it relates to the LAN question - is it hosting, or when trying to connect to another?

Try out this JAR: https://github.com/OreCruncher/DynamicSurroundings2/releases/tag/1.16.4-<IP_ADDRESS>

It's when connecting to another instance of the Minecraft client via LAN.  Most everything loads up fine and you're able to see the hotbar and the sky, but before any chunks actually load in, the game crashes.
I see you added some extra debug stuff to the latest release, so I'll try it out and report back.

I apologize; I didn't see that you had a separate repository for 1.16.4+, otherwise I would have created another issue there.
I've tested both versions multiple times and the new version fixes the issue on my end.  Attached are logs for both runs so you can compare the two if you'd like.  One is labeled as the crash and the other is using the version you just linked.
Log Files

Yeah, that's what stumped me at first.  I had originally made an issue on their GitHub repo, but through working down all 200 of my own mods, I eventually came to Dynamic Surroundings and Simply Jetpacks having an incompatibility for whatever reason.

It looks like timing.  Their logic assumes that a property on the player is initialized to a non-null value.  It is possible it is null and has not been set because their handler is firing during the client tick.  I have seen similar things when working on DS.

@HereToSaySomething @spicypepperoni Have you tried the linked jar to see if it resolves your Realms issues?

I'm having the same issue on a custom modpack server. Seems this mod is the culprit as the issue doesn't come up without the mod enabled.
I tried the version linked and it didn't fix the issue.
It looks like you have the right idea here, I noticed that you can still break things, however the speed is very slow even when on the ground (flying breaking speed). You also get kicked for flying if the block under you is clear.

@CelluloidRacer2 What prior version did you use that worked?

@OreCruncher I haven't had any versions work

Then it is something entirely different.  Not sure about the flying stuff - DS has nothing to do with that.  It also does not affect movement.  Can you open a new issue, and link your debug.log to the incident?

The game did not crash. When I tried the latest version of the mod on Realms, it froze me in place and set me in survival mode, no matter what mode I was on previously. I could only interact with the blocks around me. My movement wasn't working.

@OreCruncher if you re-read the original post, this is the same issue, just outside realms.
Whenever you join a server, it holds the player in place, and you can only interact with the blocks immediately around you. If the DynamicSurroundings mod is NOT present, it doesn't occur. If flight is disabled on the server and there's a block missing under the player, you get kicked after a second because "flying is not enabled".
This issue is not related to SimplyJetpacks, it's not installed on the pack I'm using. It's related to a bug in DS.

As mentioned do you have a debug.log available?

Hey there!  Not either of the other OPs, but I also found this issue when converting my forge server to a mohist server.  Never had the issue on forge only, but mohist caused me to be frozen in place and unable to move.  Also realized the perspective was locked because I casted a couple spells from Ars Nouveau that all went the same direction.  My character was also invisible when in 3rd person.
I've included the log from the last login with it.  It's a little messy because I was testing a bunch of mods, so let me know if there's something else I can do to help.
dynsurroundings_freeze_in_place.log

Argh!  Yet another Paper/Spigot/Bukkit/Cheetah thing!  This is going to be fun. :\

Try out this JAR: https://github.com/OreCruncher/DynamicSurroundings2/releases/tag/1.16.4-<IP_ADDRESS>

I had this issue, where in a realm I couldn't move on spawning in, this jar fixed the issue! Good dev support!!! A++

I'm having this same exact issue, but with my own dedicated server. The strangest part is that it only happens to me, while my friends can log in and move around without any issues. I solved it by rolling back one version of DS but it's really strange.

Try this updated JAR and let me know if there is a difference. I changed how the handshake works when connecting to a server. https://github.com/OreCruncher/DynamicSurroundings2/releases/tag/1.16.4-<IP_ADDRESS>

The issue has been fixed for me. Thank you.

I am going to leave this open until I push the new bits to CurseForge.  Thanks for updating me on this - I appreciate it.


5.6.0 missing on PECL

https://github.com/Microsoft/msphpsql/releases/tag/v5.6.0 is tagged, but not available in PECL (still at 5.3.0/stable and 5.5.0preview/devel)

We are preparing for the next release, which is expected to happen within the next week, but first we need to wait for the ODBC driver release, which is expected in the next few days. The tag is there because it's necessary for some of our testing, but does not necessarily mean the release is ready.

5.6.0 is now released! Closing this issue.


"code 404: No such image" when adding or updating AUR package

I tried adding or even updating a package but the build fails with log:
Pulling image: ghcr.io/lukas-heiligenbrunner/aurcache-builder:latest
Digest: sha256:a5aa452bb86f928efee5aa84f67e91044787f1695be0ce634c03683bd37dd1c2
Status: Image is up to date for ghcr.io/lukas-heiligenbrunner/aurcache-builder:latest
Docker responded with status code 404: No such image: latest:latest

The package in question is mystiq but its not limited to it, I think all package does this, I even tried adding hyprgui-bin and updating firefox-pwa-bin with the same error.
This is my compose file:
version: "3"
services:
  aur-cache:
    container_name: aur-cache
    image: ghcr.io/lukas-heiligenbrunner/aurcache:latest
    network_mode: bridge
    ports:
      - 8180:8080
      - 8181:8081
    restart: always
    volumes:
      - ${VOL1}/extra/a:/home/podman/.local/share/containers
      - ${VOL2}/db:/app/db
      - ${VOL1}/extra/b:/var/lib/containers
      - ${VOL1}/repo:/app/repo
      - /var/run/docker.sock:/var/run/docker.sock
      - ${VOL1}/builds:/app/builds
    environment:
      - BUILD_ARTIFACT_DIR=${VOL1}/builds

this came from version v0.1.5 to now v0.2.0, was there a breaking change?
I also tried using version v0.1.5 to git before with same issue except I tried starting over (deleting ${VOL1} and ${VOL2} contents)
No helpful logs in the container

Thanks for your report! There are only the two breaking changes as described in the release infos here: https://github.com/Lukas-Heiligenbrunner/AURCache/releases/tag/v0.2.0
I'll have a look why this is happening for you. I've changed the builder base-image to a self built one ghcr.io/lukas-heiligenbrunner/aurcache-builder:latest bc. the other AUR helper image I used didn't accept PRs. It seems the right image gets downloaded but then it tries to build the container with latest:latest which is weird. Lets see. :)

Thanks.
Can you send the relevant output of docker images and docker ps -a maybe? So I can see if the build image was fetched correctly and the build container created. If it got created but not started it should still be there...


TSLint errors and deprecation

TSLint has been deprecated and should be migrated to ESLint. Also there are like 1000 linting errors. Fixing these errors would require removing types like any and object and replacing them with proper types (e.g. API request/response types). It would improve readability, IntelliSense, type safety and make the code less vulnerable to common mistakes. If this is not already in the works, I'd like to work this and propose a PR on this issue by the weekend.
Reference: https://github.com/palantir/tslint/issues/4534.

Great idea! I will take a look myself sometime this week.

Added in 0.2.0 👍


Callback option to ignore hidden directories and/or other specified...

I created this simple modification to the Walk function, so that in the Callback options there are two more variables. A boolean (NoHidden), that if left as it is does not affect at all the main function, and a string slice (Ignore) that again if left as it is (empty) it just gets ignored by main function.
If boolean is set to true in Callback function, then the Walk ignores hidden files (only UNIX) and does not go through them. The same with the Ignore slice. If slice has a string the same as any folder name, then the Walk ignores that folder.
THIS IS MY FIRST EVER PULL REQUEST.
I hope you be gentle if you think this is not worthy adding or is not to be considered.
I am using your library and is amazing, but i wanted to have control when to show hidden files and when to ignore them, and sometime to ignore just specified complex folders (looking at you node modules folder).
I just thought that if someone else wants to use, i might as-well contribute those mini lines of code.
Have nice day (and happy new year)

Duplicate of #3


Add link to BSONify

HI, just wondering if you could please add a link to my BSON encode/decode package in the "Generic serialization of all Julia types to BSON" line in the README?

Hi, I had look at your package and as far as I can tell it's adding methods to functions defined in Mongoc.jl for types it doesn't own, i.e., type piracy. Since this can introduce behaviour changes to users who don't expect it (e.g., your package is imported transitively through another dependency), it's not to be encouraged. Have you considered instead to see about upstreaming extensions to Mongoc.jl directly?

Hmm, the last line of the Avoid type piracy section is "Another example might be a package that acts as a thin wrapper for some C code, which another package might then pirate to implement a higher-level, Julia-friendly API," and Mongoc.jl self-describes as a thin wrapper for a c library... In any case I did contact the author of Mongoc.jl about extending their package: https://github.com/felipenoris/Mongoc.jl/issues/74


ERROR 3050003 when erasing a table

I've got a Smart Contract Named izsjtpjbqtxy on testnet
It has an action as below, which is used to clear the whole table.
Here is the full code.
    [[eosio::action]] void erase(uint64_t nonce)
    {
        auto it = session_table.begin();

        while (it != session_table.end()) {
            session_table.erase(it);
            it = session_table.begin();
        }

        print(nonce);
    }

I was trying to invoke this action with payload
{
    "nonce": 1927
}

Here's the request body
{
    "signatures": [
        "SIG_K1_KX1UKQbo6bA3TtbRgXfrDVRZPGCyudMgTaJCKr8xoJYKw2stLJ6ntdHxwsJ1HNTaaRrqBR5UYENx9nJ6R7c4XERAssxzaJ"
    ],
    "compression": 0,
    "packed_context_free_data": "",
    "packed_trx": "dd3dc25ef41d04fc201e0000000001e07bb6e7d5fcf077000000000085cd5501e07bb6e7d5fcf07700000000a8ed323208870700000000000000"
}

But it returned
{
    "code": 500,
    "message": "Internal Service Error",
    "error": {
        "code": 3050003,
        "name": "eosio_assert_message_exception",
        "what": "eosio_assert_message assertion failure",
        "details": [
            {
                "message": "assertion failure with message: get",
                "file": "wasm_interface.cpp",
                "line_number": 1075,
                "method": "eosio_assert"
            },
            {
                "message": "pending console output: ",
                "file": "apply_context.cpp",
                "line_number": 113,
                "method": "exec_one"
            }
        ]
    }
}

I've tried many different modifications, but all failed.

I did a simple test with your code. transaction id is : 562F97AB8E70B2EF2F177BAE0DA46FC09E7224577E87CC03D4808841B03054B1
it works well

I did a simple test with your code. transaction id is : 562F97AB8E70B2EF2F177BAE0DA46FC09E7224577E87CC03D4808841B03054B1
it works well

Thanks for your work!
I tried to push some data to your contract, and it works indeed.

Maybe there's something wrong on the history of this contract?

hi @LuminousXLB
Did you modify your table structure? because you cannot erase data after modifying the structure.
If you modified then revert it to the previous structure, then erase data, then modify the structure.

Yes I modified the structure sometime.
That should be the reason...
Thanks a lot


imprecise/inaccurate content.

Hello,
In the "Important" box after step 6 of "Deploy the integrated scanner to your Azure and hybrid machines"
The following text needs to be more precise/accurate:
"If your machine is in a European Azure region"
Does this mean just North Europe and West Europe or all Azure regions in the Europe Geography not region?
This text needs to be VMs in which Azure regions  send metadata to the US or EU regions.

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

ID: 4fdbbf80-92cd-d6b2-85fd-a830589a8ed9
Version Independent ID: d89d9eef-daed-636d-7414-0b15f3195734
Content: Defender for Cloud's integrated vulnerability assessment solution for Azure, hybrid, and multicloud machines
Content Source: articles/defender-for-cloud/deploy-vulnerability-assessment-vm.md
Service: defender-for-cloud
GitHub Login: @ElazarK
Microsoft Alias: elkrieger

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

@sdaytelefonicatechuk
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

#reassign: bmansheim

Based on feedback from Engineering, I updated the statements to say:
If your machine is in a region in a European geography (such as Europe, France, Germany), its artifacts will be processed in Qualys' European data center. Artifacts for virtual machines located elsewhere are sent to the US data center.
What do you think, @sdaytelefonicatechuk ?

Hello @bmansheim thanks for looking at this. At this time I need clear information for my UK customers which data center will be used. So that is my focus.
However it would be ideal to get wider clarity for all nation-specific Azure Regions.
Adding to the confusion, in some documentation the UK is included in the Europe "geography" with the main North and West Europe Azure regions in addition to the following countries: France, Germany, Norway, Sweden, Switzerland.
In other documentation the Europe "geography" just consists of the paired North and West Europe Azure regions

I can understand the confusion. The only defined list of regions in Europe I found is https://azure.microsoft.com/en-us/global-infrastructure/geographies/#geographies, select "Europe" and select "Show nearby geographies". The geographies shown are the ones that are scanned by Qualys EU, which includes UK.
I can add UK to the "such as" in the statement above to make it more clear for UK customers. I think the other geographies are more straight forward.

@bmansheim sounds great. Many thanks.

#please-close


Build android shared library error: error: expected STT_<TYPE_IN_UPPER_CASE>, '#', '%' or ""         .type   invokeNative, @function

Hi, I'm follow the tutorial  to build an android so, but there is some error
When I try to build shared library for android  using https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/build_wamr.md  on mac. when run make, the error output is :
➜  build git:(master) ✗ make
Scanning dependencies of target iwasm
[  2%] Building ASM object CMakeFiles/iwasm.dir/Users/tk/projects/myproject/myproject-runtime/core/iwasm/common/arch/invokeNative_arm.s.o
clang: warning: argument unused during compilation: '-D BH_FREE=wasm_runtime_free' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D BH_MALLOC=wasm_runtime_malloc' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D BH_PLATFORM_ANDROID' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D BUILD_TARGET="ARM.*"' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D BUILD_TARGET_ARM' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WASM_ENABLE_AOT=1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WASM_ENABLE_BULK_MEMORY=0' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WASM_ENABLE_FAST_INTERP=0' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WASM_ENABLE_INTERP=1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WASM_ENABLE_LIBC_BUILTIN=1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WASM_ENABLE_MINI_LOADER=0' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WASM_ENABLE_MULTI_MODULE=0' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WASM_ENABLE_SHARED_MEMORY=0' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D iwasm_EXPORTS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D ANDROID' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-fdata-sections' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-ffunction-sections' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-funwind-tables' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-fstack-protector-strong' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _FORTIFY_SOURCE=2' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D NDEBUG' [-Wunused-command-line-argument]
/Users/tk/projects/myproject/myproject-runtime/core/iwasm/common/arch/invokeNative_arm.s:9:31: error: expected STT_<TYPE_IN_UPPER_CASE>, '#<type>', '%<type>' or "<type>"
        .type   invokeNative, @function
                              ^
make[2]: *** [CMakeFiles/iwasm.dir/Users/tk/projects/myproject/myproject-runtime/core/iwasm/common/arch/invokeNative_arm.s.o] Error 1
make[1]: *** [CMakeFiles/iwasm.dir/all] Error 2
make: *** [all] Error 2

something went wrong in #395


MLEM Release blog post

What's the concept behind the image? Dog in rocket to the moon looks a bit like some cryptocurrency meme

What's the concept behind the image? Dog in rocket "to the moon" looks a bit like some cryptocurrency meme. Maybe it's just my bias but that could be misleading.

MLEM takes the different models (on the mlem rocket ship with the mlem dog) and deliver to deploying to the different stars in space.  It's too late to change image.

Why has this not been deployed? @julieg18

@aguschin the structure makes sense

Intro: feel free to provide even more background and motivation if you want. You can add a link to jump to TL;DR ("With MLEM, ML teams get") if it gets long.
+ State that MLEM is a Python-specific tool (currently not explicit anywhere).

Model metadata codification: Not sure we should emphasize "human-readable" (really that depends on whether you're familiar with YAML). I think that the key aspect here is the special "magic" (ML framework integrations) to automatically capture all the relevant modeling context.

Run models anywhere: Good catchy title. Should we also use buzz word "productionize" more though? That would include packaging & distributing, running in batch (ETL), containerize/cloud deploy, or serve directly -- all MLEM features. I don't think "to deploy" captures all of that.

Git-native model registry: This section doesn't really talk about MLEM.
The core registry features would be provided by GTO right? So should this be about making Git-based model catalogs (link to GTO+DVC use case) deployable? Although that could be redundant with 2....

Maybe this can be reduced to a short note somewhere and wait for the GTO release post (is there one planned) to give more details.

Git-native model registry: This section doesn't really talk about MLEM.

p.s. I think I know what the issue is: we mention Git in the abstract and intro but never explain (in the codification section) that you can version .mlem files with Git, bringing you to GitOps. That context is a missing piece of the puzzle rn.

Is this ready for release @aguschin ?


Do not instantiate label service on main side

Currently we instantiate the label service both on the main side and on the renderer. Whenever a formatter is registered on the renderer this is passed to the main side which is a bit ugly.
We should re-structure the menu such that the open recent list is coming from the renderer. Once we do that the label service will no longer be needed on the main side at all.
fyi @bpasero @sbatten @alexandrudima

Now it is only instantiated on the renderers. Thus closing this.


Diabling async TestHost.Tests on Mono #507

As part of re-enabling hosting tests for CoreCLR in #422 on the CI.
Disabling tests that can potentially hang on Mono since the CI always run tests on Mono.

:shipit:


Version Spec syntax specification

Changed the description of the option "Version Spec" according to @steved0x 's answer to this closed issue: https://github.com/MicrosoftDocs/vsts-docs/issues/1393

Hi @vijayma - Could you review this pull request? Thanks.

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

@viyjayma Would you review this pull request? Thanks.

@steved0x @ramiMSFT @vijayma Would any of you be able to make a call on this submission in the public repository? Thanks.

#sign-off

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


Twig version 1.42-dev

Thank you for the tutorial Patrick,
Working through part: 11-page-menu of the tutorial Twig throws an exception (see below), I'm sure I did everything right; IMHO 'as a student of PHP' this is a result of changes long after you published this and an update to the content might be required. I'll let you be the judge of that.
LogicException: You must set a loader first.
at Line 819 in /var/www/vendor/twig/twig/src/Environment.php
My composer.json uses
"twig/twig": "~1.0"
which installed version "1.42-dev"
I found https://github.com/twigphp/Twig/issues/2907 that helped me to get it working by:
Changing Dependencies.php for Twig
from
$injector->delegate('Twig_Environment', function () use ($injector) {
to
$injector->delegate('\Twig\Environment', function () use ($injector) {
and changing the constructor in TwigRenderer.php
from
public function __construct(Twig_Environment $renderer)
to
public function __construct(\Twig\Environment $renderer)
Thanks again for the great tutorial!

whoa! I get the same error, and I went here and thats work. I think this is for a Pull Request to tutorial

sorry, PR had done: https://github.com/PatrickLouys/no-framework-tutorial/pull/69

Checking in May 2021 with the same error at the same step and this solution worked!


Dual LG Ultrafine 27" Primary Monitor Only Adjusted

Before opening the issue, have you...?

[X] Searched for existing issues
[X] Looked through the wiki
[X] Updated MonitorControl to the latest version (if applicable)

Describe the bug
When using dual LG ultrafine 27" monitors, the controls, specifically brightness only works on the primary monitor and adjusting the secondary (extended display) adjusts the primary.    The hardware is M2 Max Pro MBP 2023 May build running Ventura 13.5.
Steps to reproduce
Upon startup using dropdown adjust monitor brightness
Expected behavior
To control both displays independently
Anything else?
No response
Environment Information (please complete the following information)
- macOS version:13.5
- Mac model:M2 Max Pro MBP
- MonitorControl version:4.1.0
- Monitor(s):LG Ultrafine 27"
- Apple Silicon/M1 (yes or no): yes

Apple M2 Max:

  Chipset Model:	Apple M2 Max
  Type:	GPU
  Bus:	Built-In
  Total Number of Cores:	38
  Vendor:	Apple (0x106b)
  Metal Support:	Metal 3
  Displays:
LG UltraFine:
  Resolution:	5120x2880 (5K/UHD+ - Ultra High Definition Plus)
  UI Looks like:	2560 x 1440 @ 60.00Hz
  Main Display:	Yes
  Mirror:	Off
  Online:	Yes
  Rotation:	Supported
  Automatically Adjust Brightness:	No
LG UltraFine:
  Resolution:	5120x2880 (5K/UHD+ - Ultra High Definition Plus)
  UI Looks like:	2560 x 1440 @ 60.00Hz
  Mirror:	Off
  Online:	Yes
  Rotation:	Supported
  Automatically Adjust Brightness:	No

This issue has complex reasons with multi-monitor setups and addressing them in MonitorControl would require some deeper changes. You can try the latest 2.x version of BetterDisplay to see if you have this issue: https://github.com/waydabber/BetterDisplay/releases


Update dependencies

updates integration tests: profile tests auth tests testimony tests
updates to tests common.ts moderations.test.ts moderationcompontents.test.tesx modifyAccount.test.ts testutils.ts
updates profile test for change from default private to default public
fixed report toast: moved to top and z-indexed to move to front
get testimony.test.ts passing
Configure CI to run allow-list of test files
manually merge common.ts
Update Testimony type and script
fixing profile tests addresses Tom's comments
modify accounts passing addresses pr comments
address PR comments re docs and tests
profile, moderation, modifyAccount test suites passing fixes firestore rule for reading profile resource
cleans up modifyAccounts cleans up imports
moderation.tests passing moves modifyAccount tests into moderation.tests file
enabling/disabling tests to run
runs prettier
disables tests not passing ci env
runs prettier
updates moderation tests
adds object validation to created bills and drafts/testimony removes search tests from ci list
runs prettier
disables backfill tests
Fix formatting of workflow.
Remove log
attempt to update jest.

This PR attempted to update Jest in order to have better test run reporting in CI. we instead achieved this using jest-summary-reporter in https://github.com/codeforboston/maple/pull/1192 . At this time, it's not worth trying to upgrade the Jest version, as what we have still works.


UI: default content security policy

An attempt to fix CORS again

Manual workflow deploy fixed the CORS issue I was seeing 🎉 admin merging


Add Carthage Cartfile dependency analyzer

Simple analyzer for checking Cartfile dependencies.

This looks good, thanks for the help!


Loading analyzer engine & recognizer registry from configuration file

Change Description
This PR adds a file-based configuration for presidio-analyzer. It allows users to:

Configure their app (either Python or REST) using a set of three yaml files for each main engine:

Analyzer
Recognizer Registry
NLP Engine

Pass those files into the Docker image and read them when the REST version of Presidio (in flask) is loaded
Easily define which recognizer to use, which language they should support + specific configuration for each (for example, a list of context words per language)

/azp run


Disabled Tailwind Base CSS Reset, Adjusted stream and agenda page sty…

…les to account for the change

I removed the CSS I was originally using to combat this issue.


wrong redirection while deploying new solution on VDC

Description
Every time I try to deploy a solution, I got redirected to authenticate myself, then after that, I got redirected again to authenticate myself, and so on.

vdc devnet machine was using a wrong branch


SASS-42: Added auth login steps for initial sign in for agents and in…

…dividuals
Added changes to be able to login as an agent or individual including routing via agent test route

Adam and I have reviewed this branch and are happy for it to be merged


refactor: create new testenv module

Description
https://github.com/openclarity/vmclarity/blob/main/rfc/multiple-go-modules.md

Create new testenv module

Type of Change
[ ] Bug Fix
[ ] New Feature
[ ] Breaking Change
[x] Refactor
[ ] Documentation
[ ] Other (please describe)
Checklist

[x] I have read the contributing guidelines
[ ] Existing issues have been referenced (where applicable)
[x] I have verified this change is not present in other open pull requests
[ ] Functionality is documented
[x] All code style checks pass
[ ] New code contribution is covered by automated tests
[x] All new and existing tests pass

@chrisgacsal thanks for reviewing!