helpim trying to deply a zip package that has a jar file of my project

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp deploy
Errors:
The command failed with an unexpected error. Here is the traceback:
list index out of range
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 658, in execute
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 721, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 692, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 4239, in perform_onedeploy
    return _perform_onedeploy_internal(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 4401, in _perform_onedeploy_internal
    _update_artifact_type(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 4340, in _update_artifact_type
    file_extension = file_name.split(".", 1)[1]
IndexError: list index out of range

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp deploy --resource-group {} --name {} --src-path {}

Expected Behavior
Environment Summary
Linux-5.4.0-1065-azure-x86_64-with-debian-10.2 (Cloud Shell), Common Base Linux Delridge (quinault)
Python 3.6.10
Installer: DEB

azure-cli 2.32.0

Extensions:
ai-examples 0.2.5
ssh 1.0.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

route to service team

@ThayananthKumaresan does the filename you passed in not have an extension? You should ensure that the file name passed in for --src-path has an extension, such as "name.zip"

closing due to lack of response, if the suggestion resolved the issue.


reload workspace on rust project

Newly added crates aren't detected unless reopening nvim or restarting server. I think restarting server isn't a good idea especially for large project since rust-analyzer always run cargo check the whole project.
I think rust-analyzer have cargo autoreload option in the settings, but it's not working. Other option is reloading workspace by triggering rust-analyzer/reloadWorkspace (coc have this).
I can have a PR though for the second one, it's adapted from texlab command and working so far, but i'm unsure if it's the desired choice

I would go ahead and file the PR and we can discuss. What settings did you send to the server for autoreload? Is there a case where this is undesirable?
If it's not working (and we're doing things right on our end), we should file a bug upstream.

Maybe you can test it ?

Closed by #755


refactor: add etcd_connect_options for metasrv

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
The original create_etcd_client() uses None for ConnectOptions and can't configure some important arguments for connecting etcd.
In this PR, I created the EtcdConnectOptions, a subset of ConnectOptions, in the MetasrvOptions. I also added the covert function to let EtcdConnectOptions convert ConnectOptions easily.
btw, it's convenient to add TLS configurations in the future in the same structure(I will add it in the next PR).
Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.
[x]  This PR does not require documentation updates.

Let me refactor again for adding the BackendStorageProvider.

Close it temporarily. I will re-open it when the PR is ready for review.


nicerfits2presto.py error when --dec DEC is a negative value

When I run nicerfits2presto.py for a target with a negative declination, I get an error:
>  nicerfits2presto.py --dt 0.125 --ra 17:32:03.3 --dec -34:45:18 merged_cut_barycorr.evt usage: nicerfits2presto.py [-h] [--dt DT] [--ra RA] [--dec DEC]                            [--observer OBSERVER]                            evfile nicerfits2presto.py: error: argument --dec: expected one argument
This does not happen if the --dec is positive

One solution could be to input RA and DEC as float in decimal degrees, and convert to hh:mm:ss.sss and dd:mm:ss.sss for the *inf file.

It is getting confused by the  minus sign. You can also just say --dec=-34:45:18

Ah, that's a good old-fashioned astro-coding bug!  Lovely.  :-)


feat(client): add jest snapshot for settings button and certification…

… page consistency
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #48695

run jest snapshot
npm run test:source client/src/__tests__/settings-button.test.js

npm run test:source client/src/__tests__/timeline-buttons.test.js

Let us know when this is ready for review @nayabatir1 👍 Also, do you mind completing the checklist in the PR description template (just put an x in the brackets if you've done the thing mentioned).

Hi @nayabatir1, thank you for all of your hard work here on these tests.
Before moving forward with these snapshot tests, we may need to discuss them a bit more. I'm not as familiar with snapshot testing as @ahmadabdolsaheb and @ojeytonwilliams probably are, but I noticed a couple of things while going through this PR and looking at output from the failed tests.
First, because dates are rendered on the timeline, timezone differences may cause tests to fail. I believe that's what's happening here: https://github.com/freeCodeCamp/freeCodeCamp/actions/runs/3721578044/jobs/6324704916#step:6:2355
It may be possible to set a timezone in package.json before running the tests scripts ("test": "cross-env TZ=America/New_York run-s create:* build:curriculum build-workers test:*"), though I'm not sure if we want to go that route.
Next, since dates are being localized based on the client's locale, the Chinese and Spanish test suites will always fail against the English snapshot: https://github.com/freeCodeCamp/freeCodeCamp/actions/runs/3721578044/jobs/6324704756#step:6:2713
It might be possible to have different snapshots for each locale and run tests against those. Or only run snapshot tests against the English client. But again, we probably don't want to go that route.
What might be better is to have more granular tests similar to the ones in client/src/components/settings/certification.test.tsx, or even E2E tests in Cypress to check these views and buttons.
What do you all think?

@scissorsneedfoodtoo thanks,
I can try to mock dates too.
If you could let me know the file name.

@scissorsneedfoodtoo I'm not sure it's the best approach, but setting TZ was how I handled this for Chapter.  I added a global-setup file
module.exports = async () => {
  process.env.TZ = 'UTC';
};

and used that in the jest config as
  globalSetup: './global-setup.js',

Here's the PR https://github.com/freeCodeCamp/chapter/pull/631

We are officially on Node.js 18 now. We have changed the merge requirements accordingly.
You will need to rebase this PR against the main branch OR Click the "Update branch" button to get the new checks going.
Thanks for your contribution.

Hey,
I'm mocking Date.prototype.toLocaleString and Date.prototype.toISOString. So irrespective to time-zone you'll get same output. Hopefully it will solve the ci/cd failed tests

Need suggestion.
ci/cd issue
showUpcomingChanges value in env.json is false due to which while contructing link jsAlgoBase is used instead of jsAlgo22Base
Shall I update env.json and snapshot ?

I definitely feel like we shouldn't be mocking the Date API.

Do let me know if I missed something, as this PR is marked as draft.

Do let me know if I missed something, as this PR is marked as draft.

Draft PRs are not ready for review or same as WIP PRs. The idea is to cut the noise while you are not done with it.
In this particular PR's case the last few comments seem to suggest you are not sure of the approach and need more help (can be done here or on discord chat) and the tests arent passing yet.
You can just mark it ready when it is ready for review again (the approach is finalised and the tests are green).
Cheers.

[x] You need to move the mocks away to someplace else where they are not bundled with the "source" code.
[x]  Change the files to use kebab-case in their naming.
[x] I am not sure why we could not have json data for the mocks? We already have such a copy in the seeding scripts.

Sorry, I should have spelled this out. I think we have a mocks location at client/src/__mocks__, we should use that.

I used this jest gatsby for all the necessary configuration.

I'm marking this PR as draft as I'll be making a lot of pull request.
Bear with me while I try to fix failed test cases.


Uncaught (in promise) Error: Git status failed

*Edit by @rsese: tracked down to libgit2 issue with split indices, blocked on libgit2/libgit2#4857

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
When inside a specific git repository, the git status is not shown (no modified files in the tree view, git-diff does not show in the gutter). The console shows the message Uncaught (in promise) Error: Git status failed - first without backtrace, then repeatedly from refreshStatus.

When doing a new clone of the repo, this error goes away. However, the original repo behaves correctly as far as actual git is concerned. "git status" and friends work fine, "git fsck" only complains about a few dangling commits.
The problem is still present in a pristine configuration when ~/.atom is moved.
How can I help debug this?
Versions
Atom    : 1.32.0
Electron: 2.0.9
Chrome  : 61.0.3163.100
Node    : 8.9.3
apm  2.1.2
npm  6.2.0
node 8.9.3 x64
atom 1.32.0
python 2.7.15+
git 2.19.1
Running on Ubuntu cosmic.
Additional Information
While trying to track down the problem, I've created two virtually identical repositories (config, refs, logs, ...): Atom has problems in d1, but d2 works fine:
$ diff -rq d1 d2
Files d1/.git/index and d2/.git/index differ
Only in d1/.git/objects: 11
Only in d1/.git/objects: 5f
Only in d1/.git/objects: 68
Only in d1/.git/objects: b4
Files d1/.git/objects/info/packs and d2/.git/objects/info/packs differ
Only in d1/.git/objects/pack: pack-20a94249e63269d7b59974d0d529c07a5e29807d.idx
Only in d1/.git/objects/pack: pack-20a94249e63269d7b59974d0d529c07a5e29807d.pack
Only in d2/.git/objects/pack: pack-8aff7d7262227cb2a24cf3f65e1f30c400c55ab6.idx
Only in d2/.git/objects/pack: pack-8aff7d7262227cb2a24cf3f65e1f30c400c55ab6.pack
Only in d1/.git: sharedindex.16d97c0a7524fd1b515c287d74b47367e57c221f
Only in d1/.git: sharedindex.a4ce308bc375047ee0159e068e3feaab60f3c98f
Only in d1/.git: sharedindex.ec671bc7c8d35eead5907da03e51948439ad3c7d

Hey, thanks for your reply. Unfortunately, I can't share the repository.
I managed to access the repository directly using libgit (with pygit2) and got a more meaningful error message: "invalid data in index - invalid entry"
It appears to be caused by libgit not supporting split indices. To reproduce:
git init test && cd test
touch README.md
git add README.md
git commit -m "Import"
atom . # Everything should work fine
git update-index --split-index
atom . # Git support is now broken
git update-index --no-split-index
atom . # ... and it's back to working

So it's not a bug in Atom but a missing feature in libgit, feel free to close this. It would be great though, if the error message from Atom would at least point in the right direction :grinning:

It appears to be caused by libgit not supporting split indices. To reproduce:

Ahhh thanks for tracking that down, seems like this is the issue:
https://github.com/libgit2/libgit2/issues/4857
We'll keep this open and note that it's blocked in that issue.

Since I've updated to v1.40.x the issue appeared on some of my repositories.
I've tried the steps @tribut suggested on his last comment but the issue still appears.
Any updates to when this will be fixed?

Same issue here, and git update-index --no-split-index does not fix it either. git config -l shows no differences between working and non-working directories. I tried reinstalling and also removing .atom and .config/Atom, but it did not help.

Hi, I have same issue!
In "Dev tool" console was Uncaught (in promise) Error: Git status failed message.
It happened when I upgrade to Ubuntu 19.10 and upgrade Atom to 1.41.0
The reason was a line !/db/structure.sql
in .gitignore file
To inspect .gitignore file, I was inspired by this issue

Wow, I tried removing !webpack.config.js from .gitignore, and it worked for me too. It's the default .gitignore file, so there are other ! files, but only this one was causing this issue (because the file exists, I think).
Thanks!! :-)


query re: sri

If I know what the hash of a module should be ahead of time, is it possible to await import(url, {integrity: 'sha384-' + hash});, which would use the usual subresource integrity mechanics of the user agent to throw an error if the module doesn't match?

closing as duplicate of #76


[Question] Asset Share Commons Cart Issue - Publish Instance Only

The Asset Share Commons code is working well on our author instance, but after replicating a bunch of code and content packages to our publish instance I’m seeing the following errors in my browser’s JavaScript console when loading an Asset Share page:

Additionally, if I click on the “ADD TO CART” link I see the following error:

And finally, if I click on the shopping cart icon I see the following error:

Since everything is working perfectly on our author instance, I suspect that a code package is missing on our publish instance and needs to be replicated from the author to the publish instance, but I’m not sure which code package(s) might contain the ContextHub object.

@artdirk can you check that /etc/cloudsettings/asset-share-commons/contexthub has been published?

Hi @godanny86, /etc/cloudsettings/asset-share-commons/contexthub was already published, but I was able to fix this issue just now by activating the following two packages from our author instance to our publish instance:

adobe/granite/com.adobe.granite.contexthub.content-0.0.276-CQ610-B0002.zip
adobe/granite/com.adobe.granite.contexthub.content-1.0.20.zip

This is in our AMS AEM 6.3 development hosted instance, so I'm a bit surprised I needed to activate these packages (my assumption was that all relevant ContextHub packages would be automatically activated from the author instance to the publish instance by AMS).
When I checked our publish instance before doing the activation these packages did appear to be there, so I'll follow up with AMS to see if they have any thoughts on what may have been going on.
Thanks so much for your quick attention and help with this issue!

@artdirk is your page using your own implementation of the search page? I believe the AEM Contexthub JS should be included via the last line in: https://github.com/Adobe-Marketing-Cloud/asset-share-commons/blob/develop/ui.apps/src/main/content/jcr_root/apps/asset-share-commons/components/structure/page/customheaderlibs.html
Sounds like the ASC contexthub cart JS In included, but that OOTB include for context hub is not.

Hi David,
I was speaking with another engineer on my team, and it turns out the package activation I did was actually a “red herring” which only fixed one aspect of the Asset Share functionality without addressing a proper global fix.
We found that the Asset Share pages were not working as expected because nobody had read permissions on the following folders on our publish instance, and this makes sense because our accounts were set up before we deployed the Asset Share Commons code onto it:

conf (which contains the asset-share-commons folder underneath it)
etc/cloudsettings (which contains the asset-share-commons and default folders underneath it)

Once we granted read permission on these two folders to the everyone group people were able to access Asset Share pages on the publish instance without any issues, so I'm closing this issue.
Thanks again!
Art

@artdirk thanks for posting  the solution!!


Slow Launch on iOS

Describe the bug
When launching Obsidian, Todoist Sync plugin takes many seconds to load (shortest is 1.2sec)
To Reproduce
Steps to reproduce the behavior:
Force close Obsidian on iOS then launch
Happens even if Obsidian is still open in background
Expected behavior
Either faster loading time
Or full sync once a day then manual for rest?
Screenshots
Attached
iPhone 16 Pro Max; iOS 18.2

Plugin Version: 1.13
Obsidian Version: 1.7.7

Additional context
Add any other context about the problem here.

Duplicate of https://github.com/jamiebrynes7/obsidian-todoist-plugin/issues/347


Smelting ore in order to create shielding

Smelting ore in order to produce shielding seems more reasonable for a base than using pressed poo. :)
I kept the same conversion rate of the Waste Compressor. Let me know what you think.

"Ore Smelter" sounds awfully vague.  Also what metal is this shielding?  Kerbalism processes usually include comments specifying what chemical reaction the process is balanced based on.

It was just a starting point. :)
Heavy metals extraction?
Iron extraction?
Lead is not common, but iron concentration is actually pretty good in Mars/Moon/asteroids soils.

@lordcirth Apparently iron is actually used in lead-free radiation shielding applications, is just less effective then lead. For example with gamma rays it requires more or less twice the thickness of a lead shielding.
http://www.eichrom.com/PDF/gamma-ray-attenuation-white-paper-by-d.m.-rev-4.pdf
Do you like "Iron Extractor --> Process Ore to extract metal, for use in radiation shielding"?

Cool, good to know.  So, I just looked it up in the source:
https://github.com/ShotgunNinja/Kerbalism/blob/master/GameData/Kerbalism/Profiles/Default.cfg#L348
And apparently Kerbalism assumes that Ore is Ilmenite, which contains iron and titanium!  So all you need to do is calculate the masses to balance your input/output.  Although, iron being heavier than lead per shielding might be a problem...
https://en.wikipedia.org/wiki/Ilmenite

@lordcirth  I was not aware that real molten regolith electrolysis actually produces metal at the cathode. It is very interesting... I guess that we can discard the smelter idea and just insert shielding as byproduct of MRE.
I will do the math and I will write something on the forum because we should rethink a bit the MRE.


cmd/lemming starts gRIBI and Sysrib services.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

19 of 27 (70.37%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 68.926%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lemming.go
19
27
70.37%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
3234

Relevant Lines:
4692

💛  - Coveralls


[WFLY-16917] Upgrade to Jandex 3.0.0

https://issues.redhat.com/browse/WFLY-16917
Marking as a draft as this is not ready yet.

Hello, Ladicek. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

@Ladicek We need to have this PR without conflicts in other to merge the wildfly-core counterpart. Could you take a look at the conflicts and confirm when you are ready for this one? thanks!

Requires https://github.com/wildfly/wildfly-core/pull/5190

Ah, let me rebase then.

Rebased.

Hi @Ladicek , besides the required WildFly Core upgrade, is now this PR ready to test?

@yersan Yes.

Marked as ready.

Superseded by: https://github.com/wildfly/wildfly/pull/16083

Merged as part of #16083.
Thanks, @Ladicek!


Create a new MLOptimizer logo and unify it

Updated in https://github.com/Caparrini/mloptimizer-static
Palette used: https://colorhunt.co/palette/201e43134b70508c9beeeeee


In dashboard main view console error, Error in render: "TypeError: Cannot read property

Description
Error appears in the console while opening the mainview
Version information

OS: Ubuntu 20.04
project commit/version: latest development branch
Browser: chrome 84.0.4147.105

Steps to reproduce

Just go to https://localhost/admin

Traceback/Logs/Alerts

verified


PersonPicture using WAY too much ram

Describe the bug
When using the PersonPicture control and binding an actual image, the RAM usage skyrockets. Just by loading 30 images separately, the RAM usage goes to 3GB. The images are 2MB each. When using the normal Image control with a circular-mask border around it, the usage barely goes up at all, proving it's not the images causing the load, but the control itself, somehow.
Steps to reproduce the bug

Insert a PersonPicture control
Assign an image to it, either via binding or via direct URi
Watch the RAM usage skyrocket to insanity in mere seconds
Replace it with an Image control
Assign it the same exact image
Watch the RAM barely go up at all in comparison

Expected behavior
The control should use the same amount of RAM that the Image control does, with small differences due to the classes' base differences.
Screenshots

NuGet package version
Microsoft.UI.Xaml 2.7.1
Windows app type

[X] UWP
[ ] Win32

Device form factor
Desktop
Windows version
Windows 11 (21H2): Build 22000
Additional context
Using the 2.8.0 prerelease 220413001.

I was able to fix this by adding DecodePixelWidth/Height, but I still can't understand why the RAM usage is so dramatic without them.


Changes var name to reflect purpose (not terms of service)

Yeah, there's probably a better name. It just needs a different one.

distrustConfirmed?

If you're working on the code, you should be aware that a user should not trust the site.

distrustConfirmed?

Yeah, that's much better IMHO

Updated the name and renames the toggling function too.


Is ObserveRequest need payload

lwM2mServer.getRegistrationService().addListener(new RegistrationListener() {
            @Override
            public void registered(Registration registration, Registration previousReg, Collection<Observation> previousObsersations) {
            ObserveRequest request = new ObserveRequest(CHANNEL_ID, 0, 0);
                        lwM2mServer.send(registration, request,lifeTimeInMillSec, observeResponse ...);
    }
}

I send ObserveRequest to the client,but exception throwed like this
java.lang.IllegalArgumentException: The validated object is null
        at org.eclipse.leshan.util.Validate.notNull(Validate.java:222)
        at org.eclipse.leshan.util.Validate.notNull(Validate.java:205)
        at org.eclipse.leshan.core.node.LwM2mSingleResource.<init>(LwM2mSingleResource.java:38)
        at org.eclipse.leshan.core.node.LwM2mSingleResource.newBinaryResource(LwM2mSingleResource.java:106)

code in class CoapRequestBuilder , no set payload
   @Override
    public void visit(ObserveRequest request) {
        coapRequest = Request.newGet();
        if (request.getContentFormat() != null)
            coapRequest.getOptions().setAccept(request.getContentFormat().getCode());
        coapRequest.setObserve();
        setTarget(coapRequest, request.getPath());

        // add context info to the observe request
        coapRequest.setUserContext(ObserveUtil.createCoapObserveRequestContext(endpoint, registrationId, request));
    }

Whether a problem?

It seems that the binary value returned by the device is null... :male_detective:
is it the expected behavior ? I mean : does the resource /CHANNEL_ID/0/0 is equals to null or an empty byte array at device side ?
Maybe we do not support this correctly, I will check this one my side.
I suspect the stacktrace is not complete, could you please share the full error stacktrace ?
(By the way I have doubt that this error was raised in CoapRequestBuilder :thinking: ...)

(If you have a wireshark capture this could help too)

I pushed a commit (d44a562) which should fix an issue with empty value when using OPAQUE content format.
I'm not sure this is directly link to your issue.

Should it fixed your issue could we close this one ?

Do not hesitate to reopen if the issue is still here.


feat: change ConnectKit to WalletConnect v3

What does this PR do?

change ConnectKit to WalletConnect v3
view more button

Type of change

[ ] Chore
[x] Bug fix
[x] New feature
[ ] Documentation update

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (760ff23) 93.63% compared to head (176a251) 93.63%.
Report is 1 commits behind head on dev.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #480   +/-   ##
=======================================
  Coverage   93.63%   93.63%
=======================================
  Files          20       20
  Lines         330      330
  Branches       76       76
=======================================
  Hits          309      309
  Misses         10       10
  Partials       11       11

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Support for "data-" attributes

Hi Productive Rage,
Could you add support for "data-" attributes please?
Many thanks!

+1 with a more abstract goal for just adding general custom attributes to ReactElements.
I think you might be able to inherit from ReactDomElementAttributes to generate your own Attribute classes. It would be convenient to extend InputAttributes, but it's sealed.

@badcommandorfilename I'm not keen on the idea of InputAttributes being un-sealed for two reasons.
Firstly, the aim of the bindings is to add type safety to React and to avoid being able to set properties that React does not support for particular elements - if you could create a class that derived from InputAttributes then the C# type system would allow you to pass an instance of that class into the DOM.Input factory helper method but the new properties on the derived class would not be applicable to regular inputs.
Secondly, I'm not convinced that there's a good case to extend InputAttributes for your own types. If you had some sort of specialised or enhanced input element, would you really want it to support every input element option? For example, you would have to support every single InputType option - if you were creating some sort of enhanced text box element then the InputType value would not be applicable (you would have to ignore any value other "Text" or you would have to throw a runtime exception to say "only Text is supported" - which is moving away from compile time type safety). If you were creating some sort of labelled text input or text-input-with-validation-error component then it would make more sense to allow an input element as a child element - that way you don't need to try to pass all of the InputAttribute values directly into your custom component props.
I'm not saying that there are zero use cases where inheriting from the classes like InputAttributes would be appropriate but I do think that they would be edge cases and that it's a better compromise to leave them sealed.

I've added a way to add any "data-*" properties. The change has been pushed and should arrive in a Bridge.React pre-release NuGet package either tomorrow or early next week.
There is a new dynamic "Data" property that allows you to set any values that you want. Any property name within the Data object will be extracted into individual "data-*" properties when passed to React - eg.
new Attributes { ClassName = "toggler", Data = new { toggle_me = "yes-please" } }
will become
{ "className": "toggler", "data-toggle-me": "yes-please" }
Since C# does not allow hyphens in property names but these are quite common in data attribute names, any underscores in the Data reference property names will be replaced with hyphens (hopefully there aren't any / many "data-*" attribute names in use that want underscores!).
You can include as many or as few properties in the Data object as you want to. Ensure that you don't repeat the "Data" part of the names, though - note that in the above example, the Data property is called "toggle_me" and not "data_toggle_me".


Customize annotations on vpn-shoot service

How to categorize this issue?
/area audit-logging
/area monitoring
/area networking
/area security
What would you like to be added:
The ability to add custom annotations to the managed service vpn-shoot in kube-system namespace inside the shoot. Right now the service is pretty much static and not configurable:
https://github.com/gardener/gardener/blob/v1.11.1/charts/shoot-core/components/charts/vpn-shoot/templates/service.yaml
Why is this needed:
Adding annotations allows to configure some properties in the underlying ELB that is created in AWS. Specifically speaking, adding these annotations causes the service controller to configure access logs on the load balancer:

service.beta.kubernetes.io/aws-load-balancer-access-log-enabled
service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name
service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix

more info here
https://kubernetes.io/docs/concepts/services-networking/service/#elb-access-logs-on-aws

I wonder if this is rather an issue for the AWS provider - or could that be implemented in the Gardener?
Not sure if that should be implemented as a generic possibility to add Annotations to resources in the Shoot - or expose functionality via the providerConfig where the provider then adds a webhook.

This is a
/duplicate #2705
Generally, the Shoot API cannot cater for all possible, not-foreseeable use-cases. In #2705 it is being discussed to allow adding a set of annotations for all components without fine-granular configurability (i.e., which of those annotations are added to which resource). The proper solution for this is to build a webhook that adds whatever you need to whatever resource you want.


remove_version feature

As per #10

@SpacemanPaul this is how it would look
shell

sphinx
https://deprecat--11.org.readthedocs.build/en/11/source/api.html#deprecat.example.test_deprecat_on_class_method
let me know what do you think

@SpacemanPaul this is how it would look

Yes exactly!  Thanks so much!

Hi Meenal.  Any idea when this will be merged/released?

Hi, apologies for the delay, I'll make a release this week!

Hi, apologies for the delay, I'll make a release this week!

Any update on this?

done! will fix the sphinx string tests later, it's mostly minor bugs, as the examples.py api example works https://deprecat.readthedocs.io/en/latest/source/api.html#examples

Thanks Meenal - I really appreciate it.

The new release hasn't been pushed to PyPI.


[BUG] groups field dropdown shift layout while suggestions are shown

Has this bug been raised before?

[X] I have checked "open" AND "closed" issues and this is not a duplicate

Where did you find this bug?
production
Version of BioDrop (for example "v1.2.3")
2.99.8
Description
Just implementing the solution that we used for icon suggestion drop down here is the link for the https://github.com/EddieHubCommunity/BioDrop/pull/9898
Steps to Reproduce
Steps to reproduce

Go to http://localhost:3000/account/manage/link page.
Type on the group field if you already have some ths will shift the layout

Screenshots
No response
Do you want to work on this issue?
No
If "yes" to above, please explain how you would technically implement this
No response

I think the fix will be similar to the icons drop down https://github.com/EddieHubCommunity/BioDrop/pull/9898

Hello @eddiejaoude , This would be my first time contributing to this project, and I have already read the contributing guide. Would it be okay for me to work on this issue?

Sure, I will assign it to you @tix980

Hello @eddiejaoude its almost been a week so can you assign this issue to me too?

Hello eddiejaoude its almost been a week so can you assign this issue to me too?

@TheShiveshNetwork please read the contributing guide https://github.com/EddieHubCommunity/BioDrop/blob/main/CONTRIBUTING.md

Sorry, this is my first time contributing. I have finally figured out how to set up the environment, understand the code, and fix the problem. I will read the contribution guide again and proceed with the merge PR shortly.


How to write a test for flutter_i18n

Is it possible to write tests when using this library?  I've tried a few different ways of building the test widget, but I always get the same error message.
strings_en.arb
{
  "login": "LOGIN"
}

i18n_test.dart
import 'package:ad_mobile_flutter/generated/i18n.dart';
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';

class TestWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: "test",
      localizationsDelegates: [S.delegate],
      supportedLocales: S.delegate.supportedLocales,
      localeResolutionCallback: S.delegate.resolution(fallback: new Locale("en", "")),
      locale: new Locale("en", ""),
      home: Scaffold(
        body: Container(
          child: Text(S.of(context).login),
          key: Key('login'),
        ),
      ),
    );
   }
}

void main() {
  testWidgets('locale test', (WidgetTester tester) async {
    await tester.pumpWidget(TestWidget());
  });
}

This results in:
══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following NoSuchMethodError was thrown building TestWidget(dirty):
The getter 'login' was called on null.
Receiver: null
Tried calling: login

When the exception was thrown, this was the stack:
#0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:46:5)
#1      TestWidget.build (file:///Users/jmj/Documents/Development/level11/ad_mobile_flutter/test/i18n_test.dart:17:37)
#2      StatelessElement.build (package:flutter/src/widgets/framework.dart:3695:28)
#3      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3642:15)
#4      Element.rebuild (package:flutter/src/widgets/framework.dart:3495:5)
#5      ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:3622:5)
#6      ComponentElement.mount (package:flutter/src/widgets/framework.dart:3617:5)
#7      Element.inflateWidget (package:flutter/src/widgets/framework.dart:2907:14)
[38 more...]
════════════════════════════════════════════════════════════════════════════════════════════════════

I figured it out.  For some reason I need to create a widget class to pass into the tester.  I added a working example below.
strings_en.arb:
{
  "app_title": "My App Title"
}

i18n_test.dart
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:myapp_mobile/generated/i18n.dart';

class WidgetUnderTest extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      localizationsDelegates: [S.delegate],
      supportedLocales: S.delegate.supportedLocales,
      localeResolutionCallback: S.delegate.resolution(fallback: new Locale("en", "")),
      home: Center(child: Text(S.of(context).app_title)),
    );
  }
}

void main() {

  testWidgets('Uses strings from i18n library', (WidgetTester tester) async {
    // GIVEN I create the app with internationalization support (i18n)
    await tester.pumpWidget(MaterialApp(
      home: WidgetUnderTest(),
      localizationsDelegates: [S.delegate],
      supportedLocales: S.delegate.supportedLocales,
      localeResolutionCallback: S.delegate.resolution(fallback: new Locale("en", "")),
    ));

    // WHEN I search for a string that is supplied by the library (S.of(context).app_title)
    // THEN I find it
    expect(find.text("My App Title"), findsOneWidget);
  });

}

Please add this to README 👍

Wait. You're nesting two MaterialApp widgets? That seems counter intuitive.

Doesnt make much sense this nesting :thinking:  Is this the recommended way?


khepri_fun: Support binary handling instructions

Pull Request Test Coverage Report for Build 227

32 of 35 (91.43%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 81.812%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/khepri_fun.erl
25
28
89.29%

Totals

Change from base Build 213:
0.4%

Covered Lines:
1246

Relevant Lines:
1523

💛  - Coveralls


[fix] Parse Scala 3 diagnostics without id

DiagnosticID is not always present in diagnostic messages of Scala compiler:
MessageRendering.scala#L185

hmm,
the unit tests all passed for me locally.
I reran the CI to see if it changes anything.

indeed seems something wrong with CI, ill take a look in a few hours
in the meantime, you can force merge it for now if tests pass locally


docs: update adapter-node.md

Fix the npm ci command line for actual version
Extend ORIGIN samples for local development
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

A note to other reviewers as to the difference here: if a package is listed in both dependencies and devDependencies the updated command will install it whereas the prior command will not. I suppose this seems like a reasonable change

the updated command will install it whereas the prior command will not

wait npm ci --prod will omit things that are in dependencies and devDependencies but npm ci --omit-dev won't? that seems... surprising

wait npm ci --prod will omit things that are in dependencies and devDependencies but npm ci --omit-dev won't? that seems... surprising

According to ChatGPT, which is what I asked when I was confused by the motivation for this PR. Not sure how much you trust it. It's told me things I know to be blatantly wrong before, so probably wouldn't hurt to verify :grin:

The docs don't mention a --prod flag at all, no idea where that came from
https://docs.npmjs.com/cli/v9/commands/npm-ci

Ah. npm install has a --production flag.


simplify: do not stage config

Not writing to disk in the ConfigGenApi  makes it easier to reason about the behaviour of the ConfigGenApi struct as it is conceptually encapsulated. Now FedimintServers behaviour only depends on files that it has written to disk itself while ConfigGenApi has no side effects. Furthermore, a crashed config gen starts from a clean slate and does not have to deal with potential remnants.

@elsirion Could you please elaborate on the issue and why staging avoids it?

We only have code that can delete files in staging, not the final config directory, so if that function is called by accident nothing too had should happen.

@elsirion This pr does not introduce any code to delete the config files either; the config is only written to disk after the start_consensus method has been called.

After taking a deeper look at the code what you want to do is postponing writing of the config till DKG is finished and configs have been verified. That way we don't have to delete anything anymore when resetting the cofiggen process. One drawback of this is that you cannot restart fedimintd mid-setup anymore, which iirc was the reason for going with this approach, but we never really tested it, so I think we could just do away with this feature and this PR looks ok at a high level.

Needs rebase :(


chore: Use SQLAlchemy 2 and support psycopg[binary]

This will supersede (unless we feel like updating it in main before Meltano v3 is released):

#7546

Having a few problems testing mssql locally: https://github.com/pymssql/pymssql/issues/822

I'm splitting this PR into 3 smaller changes to make it easier to debug what's causing MSSQL to fail:

https://github.com/meltano/meltano/pull/7960
Bump SQLAlchemy to 2.0
Add new postgres extra and psycopg[binary] dependency

All items above have been addressed in their own PRs


add tooltips to show who reacted to your post/comment on main feed

This needs someone's eyes, it's not optimized for styling.
notes

had to remove overflow:hidden style on parent div, it was causing the tooltip to not render on thread-view.

I tested a long sequence of reacts, it looks like they wrap onto more lines fine.

also shows tooltip on expanded view, as it's the same function that renders the reactions in both styles. it could in theory take an argument but that feels inconsistent with the coding style.

Loom Video
Reactions with many clicks are clipping at the edge of posts-feed. Possible solution: make a tooltip that is flush with the start of the reactions instead, limit the number of characters it shows.


format patterns

see http://doc.rust-lang.org/stable/syntax/ast/enum.Pat_.html

Woops, this is a dupe of https://github.com/nrc/rustfmt/issues/18.


Proctored MC 3

AP Testers - MCQ Testing -Finals-Week3-Quiz5 on CB

[x] GH Indi Page, Review Ticket, Crossover graded, Study Plan
[x] Quiz5 MCQ results >50%, (1 or 0) and test corrections

1.5/2


Create jency1 - unmerged PR's

Total unmerged PR's :

Improved the UI of Amantran Food Ordering - (https://github.com/khushi-joshi-05/Food-ordering-website/pull/1613) - level 3

Improved the UI of Frosa - (https://github.com/khushi-joshi-05/Food-ordering-website/pull/1610) - level 2

Bug fixed - Fixed the footer - (https://github.com/khushi-joshi-05/Food-ordering-website/pull/1608) - level 2

Added coding platform - TopCoder in DSA - (https://github.com/jfmartinz/ResourceHub/pull/1583) - level 1

Added coding platform - codewars for DSA - (https://github.com/jfmartinz/ResourceHub/pull/1581) - level 1

Added resource for Interview Questions asked in DSA - (https://github.com/jfmartinz/ResourceHub/pull/1579) - level 1

Added Trie data structure in DSA - (https://github.com/jfmartinz/ResourceHub/pull/1577) - level 1

Added heap data structure in DSA - (https://github.com/jfmartinz/ResourceHub/pull/1575) - level 1

Added Hash Map data structure in DSA - (https://github.com/jfmartinz/ResourceHub/pull/1573) - level 1

Made Navbar Sticky - (https://github.com/CSEdgeOfficial/learn.csedge.courses/pull/486)

@sanjay-kv Please merge all this PR's by adding the level labels as soon as possible.

you have to raise mutiple pr here.

Ok. I will raise multiple PR's within 1 hour. Thanks for the information. @sanjay-kv

@sanjay-kv Please assign this PR to me. Else this won't be counted in the leaderboard as per the rules.


Final tweaks before JOSS submission

Add paper figure, check for typos, final pluto notebook version.

Codecov Report

Merging #39 (0efb3ad) into master (fd3ad40) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #39   +/-   ##
=======================================
  Coverage   93.87%   93.87%
=======================================
  Files           9        9
  Lines         408      408
=======================================
  Hits          383      383
  Misses         25       25


The border color of slider dotBorderActive is not a variable

TuSimple/naive-ui version (版本)
2.34.3
Vue version (Vue 版本)
3.3.0-alpha.8
Browser and its version (浏览器及其版本)
Edge
System and its version (系统及其版本)
Win11
Node version (Node 版本)
Reappearance link (重现链接)
https://www.naiveui.com/zh-CN/os-theme/components/slider
Reappearance steps (重现步骤)

Open the theme editor.
Find the dotBorderActive of the slider.
The borderColor of dotBorderActive is a fixed value and does not change with fillColor. It is recommended to set it to follow fillColor changes.

Expected results (期望的结果)
The borderColor of dotBorderActive will follow fillColor changes.
Actual results (实际的结果)
The borderColor of dotBorderActive is a fixed value and does not change with fillColor
Remarks (补充说明)

For more flexible use by users, dotBorderActive has corresponding configuration items:

This issue does not have any recent activity. If you are still experiencing similar problems, open a new error, including a minimal copy of the problem


Update env to include delete-im, remove-EnvVal changes

What
Update env to include delete-im, remove-EnvVal changes
Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]

I would consider getting rid of the EnvVal and EnvObj types.

I would love so as well. I already removed EnvVal.
However, when I replace EnvObj (replacing with Env + Object) for Map and Vec:
pub struct Map<K, V>(Env, Object, PhantomData<K>, PhantomData<V>);
repr(transparent) was giving me problem "transparent struct needs at most one non-zero-sized field, but has 2". Is it ok that we remove repr(transparent)?

Is it ok that we remove repr(transparent)?

I think yes. The attributes guarantees that the ABI of the inner value and struct are the same, so that you could transmute between them. More details here. We only need it on types that cross extern/exported functions, and the only types we have that do that are RawVal and Object. So it is critical that we keep it on those types, but other types no.


Syncing latest changes from master for odf-console

PR containing the latest commits from master branch

@red-hat-storage/odf-console-admins can we please get this PR merged, if everything looks fine to you all?

@Nikhil-Ladha I am not sure what is happening here? Why do we need to manually merge the syncing PR? Also we have multiple release branches so I am not sure this is going to be enough. We have a compatibility branch as well.

@Nikhil-Ladha I am not sure what is happening here? Why do we need to manually merge the syncing PR? Also we have multiple release branches so I am not sure this is going to be enough. We have a compatibility branch as well.

By merging, I meant adding the lgtm and approve labels.
This syncing is happening is only for the upcoming release version, that too only till dev freeze.
And, regarding the compatibility branch, I saw that we are picking up the commits for both odf-console and odf-console-compatibility from the main itself, that's the reason I didn't create the compatibility branch.

@Nikhil-Ladha I still don't understand it if we need to sync release branches then we need to sync the compatibility branch too for every release. Also if PR creation really required? I think Openshift teams sync release branches without creating these PRs. Is that something we can do as well?

/approve

/lgtm


Leg bone rotation axis off by 45 degrees

The 4 leg bone rotation axis are wrong.
I double checked to compare them to the Unity importer, so I know it' s just the vrm to blender importer.

I can't understand what you say.
Please show me about difference of you expected and current by images and so on.

If you say about bone local axis, it is technical specifications.
VRM(gltf) gives only joint position, so vrm importer presumes bone tail position (it makes bone local axis) by bone childlen positions.
Thanks.


default location of splunk.secret is wrong?

Affected Puppet, Ruby, OS and module versions/distributions

Puppet: 6.24
Ruby:
Distribution: Debian 10
Module version: 9.0.0
Splunk version: 8.1.0

How to reproduce (e.g Puppet code you use)
What are you seeing
I noticed that in params.pp the secret file location is set to '${homedir}/etc/splunk.secret'.
What behaviour did you expect instead
In our instances the splunk.secret file is in ${homedir}/etc/auth/. Also in splunk::enterprise::service::nix the /etc/auth/splunk.secret is used as hard-coded location for the exec creates.
Output log
Any additional information you'd like to impart
I was wondering if this default is correct, and, if yes, which magic I'm missing here. If the default location is indeed incorrect I can supply a patch for this.

Both of my environments have it in ${homedir}/etc/splunk.secret as you suggest.
Forwarder installed by Puppet:
VERSION=8.2.2 BUILD=87344edfcdb4 PRODUCT=splunk PLATFORM=Linux-x86_64
Enterprise never touched by Puppet:
VERSION=8.1.4 BUILD=17f862b42a7c PRODUCT=splunk PLATFORM=Linux-x86_64

The oldest version I was able to check for the splunk.secret location is version 6.3.14. This version already has this file in etc/auth.

Looking through Splunk's official documentation from 7.0.0-9.3.0, the location for the splunk.secret file should be $SPLUNK_HOME/etc/auth.


tests: kernel: mem_protect: fix incorrect skip on mem_map test

The mem_map test was skipped on all the phsical x86 boards when running twister to test them.
This error happens when migrating the new ztest. Remove the incorrect platform allow to fix this error.
Signed-off-by: Enjia Mai<EMAIL_ADDRESS>

Sorry, this error was introduced by me and we did not catch this issue until I try to verify the mem_map PRs.


Whitelist or blacklist specific forms

There are some forms we may not want to track like password forms, credit cards, addresses and may want to exclude them.  If we enable form tracking on a page we should have a way to to either whitelist or blacklist certain forms by either class name, id or some sort of attribute.

For link click tracking, you can have either a whitelist of links to track, a blacklist of links not to track, or a filter function which determines which links to track. We could have something similar for both forms and fields. For example this
{
  forms: {
    filter: function (elt) {return elt.id === "formToTrack"}
  },
  fields: {
    blacklist: ["password", "address"]
  }
}

would track every field other than password and address in all forms with ID "formToTrack".
One flaw in this API is that if you have two forms with "address" fields, it is difficult to blacklist the address field in only one of them.

This looks good. Can you clarify what the argument is to the filter function?

The argument to the filter function is either the form element under consideration or the field element under consideration.
So
{
  forms: {
    filter: function (elt) {return elt.id === "formToTrack"}
  },
  fields: {
    filter: function (elt) {return elt.name !== "password"}
  }
}

would track every field in the form with ID "formToTrack" whose name is not "password".
Whitelisting for fields would probably work differently than whitelisting for forms or links. With links and forms a whitelist is a list of HTML classes such that only elements with one of those classes are tracked. With fields it might make more sense to whitelist based on field name rather than field classes.
(And a similar statement holds true for blacklisting.)

Understood. Why the opting for names vs classes for fields?

Usually field elements in forms are identified by their name property: http://www.w3schools.com/tags/att_form_name.asp
We could use classes instead, but I think people are more likely to already have fields with the name property.

Sounds good to me - thanks @fblundun !

The way I implemented this makes a breaking change to the form tracking API because the position of the context argument has changed: https://github.com/snowplow/snowplow-javascript-tracker/commit/fe84b37bffece671dccd561fee4d0c133e807b85#diff-862f48f6fbba902dce9286abfa48db47L1026

Okay Fred - thanks for the heads-up...


Css not included ?

Hello,
it looks the AdminLTE style (.css) is not included ?
i tried to install and setup, eveything is working well unless there is no style. is it normal ?
Thanks

maybe you can see the 'yii2-adminlte3/assets/AdminLteAsset '


Update contribution.md

@vidushisinha contribute here https://github.com/Ishaan28malik/Get-Dev-Resources


Consistent coordinate ordering

Issue #21 was caused by a confusion about coordinate ordering: in most contexts coordinates into a diagram are ordered in such a way that we can arrive at the point they address by iteratively taking slices of the diagram at the coordinate heights in sequence. In the 2d graphics the traditional (x, y) coordinate system is used, which happens to be the other way around. This is more confusing than just using the (y, x) orientation in the renderer instead and can cause many potential problems.

I fixed this because it's a prerequisite to migrating the 2d renderer to the new cubical mesh extraction.

Highlight2D still uses the wrong ordering, so I reopened the issue.


Advice on what am I doing wrong

Hey Noam,
I am a DevOps engineer and I can code in Node.js but I never used Python before.
Probably I am doing something pretty basic wrong, can you point me to the right direction?

if I use the python console it works, it only does not work if I call it as a file

I noticed that setting the motor mode using .mode fails when executed too quickly after starting the hub connection. Possibly due to some setup that happens with the motors. For me, it helps to wait around 1 second after starting the hub connection before accessing motors.
Also see #3

thank you!


[GitRepository] Prefer set-url instead of adding/removing remotes

git remote set-url is better to change the remote URL because removing
the remote and then adding it causes issues when the remote is
referenced in the global git config.

https://bugs.swift.org/browse/SR-3402

@swift-ci please test

@ddunbar I am merging this as it is pretty straight forward but can you take a quick look, just in case.

I am wondering if we should have a test mocking a global git config file, though I am not sure that matters anymore after this change


New binding for returning List[List] instead of numpy array

Often it's useful to return lists instead of numpy arrays. This is especially useful when using filtering if k > num of items returned after filtering.  There may also be instances where you'd like to return noncontigous 2d arrays. This PR adds a new binding that will return a List of Lists instead of a numpy array.
This pr should fix contigious 2D array.
cc @yurymalkov

@Scikud Thank you for the PR!
Could you please modify the existing function knnQuery_return_numpy instead of creating a new one?
You can take a look at the getData function as an example. It has a return_type parameter that can be set to either numpy or list. Then we will need to rename the knnQuery_return_numpy function to something like knnQuery.


[CODE] Using some Python coding best practices for open source repositories

I propose that tis project adopts some of the standard Python development tools to make contributions easier and reduce some of the burden of new contributors.

black and black-disable-checker for code formatting
isort to systematically sorting the imports
pylint to spot and fix mistakes, errors and code smells

Further tools that are not yet very useful here but might become handy in the future

blacken-docs for documentation
mypy if type annotations become a thing in this package.

Agreed. Do you know how we can enforce that by code or linting etc. Another question, do you know how to validate that with IDE as Pycharm?

For the branch protection an admin needs to go to Setttings -> Branches and then click the "Add rule" in the "Branch protection rules" section, type the name of the branch to be protected (master) and then check at least the top two protections "Require a pull request before merging" and "Require status checks to pass before merging". That should do it.

I will protect the master.

For the branch protection an admin needs to go to Setttings -> Branches and then click the "Add rule" in the "Branch protection rules" section, type the name of the branch to be protected (master) and then check at least the top two protections "Require a pull request before merging" and "Require status checks to pass before merging". That should do it.

DONE.


fixed the broken link issue#21

Signed-off-by: siddhantprateek<EMAIL_ADDRESS>

thank you for reviewing it


Allow the package to be compiled on OCaml 4.12

The master branch currently compiles perfectly with the soon upcoming OCaml 4.12.
Would it be possible to get a release to get the compatibility with OCaml 4.11 and 4.12? I can release it on opam like last time if you need.

Were you able to build reason on ocaml 4.12 then build reanalyze with it?
Tried quickly and even reason master does not seem to support 4.12 yet.

Yes it compiles perfectly using this PR/branch: https://github.com/facebook/reason/pull/2635
If you use opam you can try adding this repository: https://github.com/kit-ty-kate/opam-alpha-repository/ and everything should be taken care of.

Thanks, I could build and things look fine. In fact, the typed ast is mostly unchanged between 4.11 and 4.12.

@kit-ty-kate creating release 2.12 now.


certificate verify failed with edgeHub Mqtt Broker

i am experimenting with Azure IoT Edge MQTT broker to publish and subscribe
from below link : https://docs.microsoft.com/en-us/azure/iot-edge/how-to-publish-subscribe?view=iotedge-2020-11#pre-requisites
i was able to test successfully  with SAS Token
but when i tried with x509 i am getting below Error
#Error
Traceback (most recent call last):
File "cert_pub.py", line 41, in
client.connect("localhost", 8883,60)
File "/home/challal/.local/lib/python2.7/site-packages/paho/mqtt/client.py", line 941, in connect
return self.reconnect()
File "/home/challal/.local/lib/python2.7/site-packages/paho/mqtt/client.py", line 1104, in reconnect
sock.do_handshake()
File "/usr/lib/python2.7/ssl.py", line 828, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:727)
#Edge runtime version :
iotedge 1.2.0~rc1
#System containers version:
challal@challal:~/Downloads$ docker ps
CONTAINER ID        IMAGE                                            COMMAND                   CREATED             STATUS              PORTS                                                                                NAMES
b8487c368cf5        mcr.microsoft.com/azureiotedge-hub:1.2.0-rc2     "/bin/sh -c 'echo "$…"   4 hours ago         Up 2 hours          <IP_ADDRESS>:443->443/tcp, <IP_ADDRESS>:1883->1883/tcp, <IP_ADDRESS>:5671->5671/tcp, <IP_ADDRESS>:8883->8883/tcp   edgeHub
305ff643a56a        mcr.microsoft.com/azureiotedge-agent:1.2.0-rc2   "/bin/sh -c 'exec /a…"    4 hours ago         Up 2 hours                                                                                edgeAgent
#Code i tried :
from paho.mqtt import client as mqtt
import ssl
path_to_root_cert = "/home/challal/Downloads/cacert.pem"
#path_to_root_cert = "/home/challal/Downloads/certs/azure-iot-test-only.root.ca.cert.pem"
device_id = "pub_cert"
def on_connect(client, userdata, flags, rc):
print("Device connected with result code: " + str(rc))
def on_disconnect(client, userdata, rc):
print("Device disconnected with result code: " + str(rc))
def on_publish(client, userdata, mid):
print("Device sent message")
client = mqtt.Client(client_id=device_id,clean_session=True,userdata=None,protocol=mqtt.MQTTv311,transport="tcp")
client.on_connect = on_connect
client.on_disconnect = on_disconnect
client.on_publish = on_publish
client.username_pw_set(username="WE-SB-DEV-SC-iothub02.azure-devices.net/pub_cert/?api-version=2018-06-30", password=None)
cert_file = "/home/challal/Downloads/pub_cert/new-device.cert.pem"
key_file = "/home/challal/Downloads/pub_cert/new-device.key.pem"
client.tls_set(ca_certs=path_to_root_cert, certfile=cert_file, keyfile=key_file,
cert_reqs=ssl.CERT_REQUIRED, tls_version=ssl.PROTOCOL_TLSv1_2, ciphers=None)
#client.connect("WE-SB-DEV-SC-iothub02.azure-devices.net", 8883,60)
#client.publish("devices/pub_cert/messages/events/", "{id=123}", qos=1)
client.connect("localhost", 8883,60)
client.publish("test_topic", "{id=123}", qos=1)
client.loop_forever()
#Deployment json:
{
"$schema-template": "2.0.0",
"modulesContent": {
"$edgeAgent": {
"properties.desired": {
"schemaVersion": "1.0",
"runtime": {
"type": "docker",
"settings": {
"minDockerVersion": "v1.25",
"loggingOptions": "",
"registryCredentials": {}
}
},
"systemModules": {
"edgeAgent": {
"type": "docker",
"settings": {
"image": "mcr.microsoft.com/azureiotedge-agent:1.2.0-rc2",
"createOptions": {}
}
},
"edgeHub": {
"type": "docker",
"status": "running",
"env": {
"experimentalFeatures__enabled": {
"value": "true"
},
"experimentalFeatures__mqttBrokerEnabled": {
"value": "true"
}
},
"restartPolicy": "always",
"settings": {
"image": "mcr.microsoft.com/azureiotedge-hub:1.2.0-rc2",
"createOptions": {
"HostConfig": {
"PortBindings": {
"5671/tcp": [
{
"HostPort": "5671"
}
],
"8883/tcp": [
{
"HostPort": "8883"
}
],
"443/tcp": [
{
"HostPort": "443"
}
],
"1883/tcp": [
{
"HostPort": "1883"
}
]
}
}
}
}
}
},
"modules": {
"TemperatureSensorModule": {
"version": "1.0",
"type": "docker",
"status": "running",
"restartPolicy": "always",
"settings": {
"image": "${MODULES.TemperatureSensorModule}",
"createOptions": {}
}
}
}
}
},
"$edgeHub":{
"properties.desired":{
"schemaVersion":"1.2",
"routes":{
"Route1":"FROM /messages/* INTO $upstream"
},
"storeAndForwardConfiguration":{
"timeToLiveSecs":7200
},
"mqttBroker":{
"authorizations":[
{
"identities": [
"{{iot:identity}}"
],
"allow":[
{
"operations":[
"mqtt:connect"
]
}
]
},
{
"identities": [
"{{iot:identity}}"
],
"allow":[
{
"operations":[
"mqtt:subscribe",
"mqtt:publish"
],
"resources":[
"test_topic",
"$iothub/methods/POST/#",
"$iothub/twin/res/#"
]
}
]
},
{
"identities": [
"{{iot:identity}}"
],
"allow":[
{
"operations":[
"mqtt:publish"
],
"resources":[
"test_topic"
]
}
]
}
]
}
}
}
}
}

@lakshmisivareddy, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey

@lakshmisivareddy, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey


Move Javadoc for JsonNodes

moving javadoc comment which was technically in the wrong place

why are there 19 commits on this PR?

Hmm should be ok once it's squashed. Will merge this.


Add release channel support to differentiate environments

This PR adds support of release channel to be able to set different environments in CI
Reference: https://docs.expo.io/versions/latest/guides/release-channels.html

@teddyviking thank you for this! I haven't used Expo release channels so far. Do you think it would be feasible to replace the home-grown namespacing appr currently does by modifying the name of the app entirely by just creating a new release channel for each branch?
Reading the example workflow documentation, it doesn't sound like there would be a problem creating transient channels:

If you have a new version that you dont want v1 users getting, release v2 of your app by running exp publish --release-channel prod-v2 and building it with exp build:ios --release-channel prod-v2. Users with the prod-v2 ipa will only be pulling releases from that channel.

@teddyviking I seemed to have accidentally closed this PR - apologies. Reopened. May not land this exactly as-is, we are looking to migrate to release channels as the primary way of deploying PRs.

@teddyviking thanks for this PR! I couldn't merge this diff since we decided to go a bit different direction and use release channels as the default publishing strategy from now on.
This feature has now landed in<EMAIL_ADDRESS>https://github.com/FormidableLabs/appr/releases/tag/v2.0.0


[RESTEASY-2456]: JVM Heap leak fix.

I agree on the Apache License 2.0 terms.

thanks for the PR @artzag ; I've added a comment to jira, would you mind checking and answering (either there or here). Thanks a lot!


Kong Manager Portal Editor - unable to delete folder

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
<IP_ADDRESS>
Current Behavior
When using the editor, right clicking and selecting delete folder brings up a pop-up. Clicking [Proceed] in this pop-up does not do anything. No network requests are made; and the pop-up remains open.
Expected Behavior
The folder is deleted.
Steps To Reproduce
1. Make a workspace
2. Enable Portal
3. Go to Portal Editor
4. Right click on folder
5. choose Delete folder
6. Choose proceed

Anything else?
No response

Hi @meesvandongen, thanks for reporting this issue.
I've created an internal ticket to track the process to solve the problem :)
We are trying to reprod and solve that ASAP.

The bugfix was included in the <IP_ADDRESS> release.


Rescan Attachments in Current File always put renamed attachments at "assets" folder of root of vault

I have Obsidian settings under "Files & Links" -> Default location for new attachments -> In subfolder under current folder.
When editing a file, invoke plugin command "Attachment Name Formatting: Rescan Attachments in Current File" from Obsidian Command Palette menu. The renamed attachments are relocated to "assets" folder under Vault root, instead of "assets" folder under the current folder.
Expected behaviour: the renamed attachments should move to location following the Obsidian settings under "Files & Links" -> Default location for new attachments".

Thanks for reporting, should be fixed in 1.9.5.
If failed to rename some attachments, may need to re-insert the attachment into the note file.

Sorry to say its not really fixed in 1.9.5 release.
When I set Obsidian settings under "Files & Links" -> Default location for new attachments -> In subfolder under current folder. When editing a file for example "Travel/France Food.md", with plug in "Automatic Formatting" turn off, when I add an image attachment let say IMG4588.png, Obsidian will place the image file into "Travel/assets/IMG4588.png".
So I would expect the plugin command "Attachment Name Formatting: Rescan Attachments in Current File" to rename the image and place under "Travel/assets/France Food_image_1.png".
For 1.9.5 when you invoke the command, the image file however is renamed to "assets/Travel/France Food_image_1.png", which is not in subfolder of current folder.

Just checked again, I think should fix now. Please raise again if there is still some problems.


ConditionalAccessPolicy

Hello,
Seems the "ConditionalAccessPolicy: ReadOnly" blocking .txt or .log files on unmanaged PC's if use Webmail,
While PDF or Word files displayed just fine... any explanation for this?

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

ID: 022da80e-29cd-f6b5-aa00-48e2d16c4be8
Version Independent ID: c3353c03-e416-f693-104f-6b6f5955b721
Content: Set-OwaMailboxPolicy (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@lightupdifire, I would suggest opening a support case on this. If you find anything that requires a content update, report back here, and we'll make the update.

@chrisda
I will open a Support ticket, but if it is a Real limitation, would be good to include in the document information about this limitation, you agree?

@lightupdifire, yes. Absolutely. The support case will confirm whether this is a known limitation that needs to be documented, or some type of bug that will get fixed (and will therefore not require documentation updates).
Report back here with their findings.

@chrisda Thank you very much for sharing this explanation. @lightupdifire Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed here to close it.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Can we kustomize (or otherwise patch/modify) a helm chart with loftsman?

Hi there,
We've a vendor supplied helm chart that's deployed via loftsman that we need to modify as it's deployed to pull in some sealed secrets from our customizations.yaml file (otherwise the pods will fail to start as they cannot find the secrets they need).  We believe that helm can do this via its "post-rendering" functionality (see https://helm.sh/docs/topics/advanced/ ) and was wondering if there's a way to take advantage of that via loftsman?
All the best,
Chris

Hey Chris, yeah this post-rendering capability in Helm is still pretty new. I've been trying to wrap my head around the reasons it was added at the Helm level before we decided exactly what we may or may not do with it in the context of Loftsman. So far, I've seen it as something that's there simply to be able to support those who have legacy kustomize templates primarily and just making sure they have some way to integrate with Helm.
Regarding sealed secrets/customizations.yaml, etc. I'd recommend you sync with Cray/Shasta folks on this specifically. That's all very much specific to other tooling around Loftsman in the context of Cray, and everything should be set up to do exactly what you need. E.g. customizations defines a secret, gets fed into a given chart via customization values, and the chart can then has access to the secret in a secure way. The current Shasta team will be able to help you on this one I'm sure.

Hi Patrick,
Thanks for that - we're basically wanting to insert a template cribbed from another helm chart that we hope does what we need into the chart that is missing it.  I opened Cray case 279976 around the same time last night for that specific question, so I think that covers all our bases, fingers crossed.
All the best,
Chris

Gotcha, and yeah, I think I'm seeing a use-case I wasn't before in the new post-rendering capabilities of Helm: being able to adjust or tweak third-party charts without forking them. That's actually a really powerful use-case, so I'm going to mark this as a feature request for supporting that capability of Helm.

Sounds great @rockholla!
I wonder if that might help with another question I've got, but I'll make a new issue for that in case there's something I've missed first.


Adding "Apply for beta access" form with Google Sheet

As discussed with Tom, I have added the form for "Get in touch / Apply for beta access" which stores the email address in a Google Sheet. Please let me know who needs access to this! 😄

This has been replicated in new design


Android - LHN - Free space below FAB modal window

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the App
Login with any account
Tap on FAB button (1-st issue)
Go to any chat
Tap on "+" button (2-nd issue)
Tap on Emoji (3-nd issue)

Expected Result:
No free space below
Actual Result:
Free space below
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

NOTE: this issue is specific to https://github.com/Expensify/App/pull/13767#issuecomment-1370007287 CC @WoLewicki

Not overdue, I will try reproducing this.

Hey @techievivek, this is an unique report because it is from a new React native architecture branch -- so Software Mansion are handling this

Hello, I will be working on this issue.

Me too

Assigned you both

https://github.com/WoLewicki/App/commit/2d98d4e4aa0276afbbc0a07853164e20dff0fdf0 should fix the problem.

This issue has not been updated in over 14 days. @j-piasecki, @WoLewicki eroding to Weekly issue.

This issue has not been updated in over 15 days. @j-piasecki, @WoLewicki eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!


TMDB Genre list() changed to movie_list()

In Section 3 when looking at returning Genres from TMDB the instructions state to use the .list() method of the Genre object returned by tmdb.Genres().
There has been an update to the API and list() no longer exists. There are separate lists for movies, tv, etc. Currently the function we're looking for is movie_list(), which returns the list of movie genres.

Responded on the pull request conversation. As this issue doesn't require discussion between multiple people, we can take it up there in the PR conversation. Closing the issue here :)


Corner View not shown

  This is my xml file

     `<com.evrencoskun.tableview.TableView
    android:id="@+id/tableView"
    android:layout_below="@id/rel"
    android:layout_width="match_parent"
    android:layout_height="match_parent"

    app:row_header_width="@dimen/_80sdp"
    app:column_header_height="@dimen/_30sdp"
    app:selected_color="@color/white"
    app:shadow_color="@color/white"
    app:allow_click_inside_cell="true"
    app:allow_click_inside_row_header="true"
    app:allow_click_inside_column_header="true"

    app:unselected_color="@color/white"
    app:layout_constraintLeft_toLeftOf="parent"
    app:layout_constraintRight_toRightOf="parent"
    app:layout_constraintTop_toTopOf="parent"
    />`

My corner view
`

<TextView
    android:layout_width="wrap_content"
    android:layout_height="wrap_content"
    android:text="States/UT"
    android:textSize="@dimen/_12ssp"
    android:padding="@dimen/_5sdp"
    android:textColor="@color/black"/>

`
i have returned this view from method onCreateCornerView()

same problem to me

@juanlabrador @aashitshah26
There's a bug in the library. If you use methods for separate columns, rows & cells setting instead of setAllItems() - corner view is not added to the layout. I had to fix it for myself manually in the code. So for now there are 3 options:

Wait for the fix
Add the library as a module to your project and fix the problem manually (add code with the corner view adding to the container FrameLayout)
Use setAllItems() method

Corner View is currently not shown if any of the column or row headers or cells have no data.
In my case I have column headings but no data for the rows (cells and row headings)>
This produces an odd view of:-

I think it a fairly normal case if your have column headings you would want to display the corner view (which is a column heading of the row headings)
If you have zero column heading, zero row heading and zero data then you would expect no corner view as well.
As this is a change in behaviour I feel that this should be optional not to break people who expect the existing behaviour.
I have a change prepared to optionally produced:-

Once I have fully tested it I'll make a pull request for this.

I faced that problem and I found the easiest solution is
calling getCornerView() and update view visibility after calling setAllItems() method
getCornerView().visibility = View.VISIBLE

@Mohamadkotb no, not works for me. I have to added empty row to end table for showing corner. Thanks @Zardozz

This should be able to be closed with the release of <IP_ADDRESS>
You can now call setShowCornerView(true) on the tableView before you set the adapter, so that the cornerview is drawn even if you don't have any row headers (and rows)
Results as per comment https://github.com/evrencoskun/TableView/issues/308#issuecomment-651248087

This should be able to be closed with the release of <IP_ADDRESS>
You can now call setShowCornerView(true) on the tableView before you set the adapter, so that the cornerview is drawn even if you don't have any row headers (and rows)
Results as per comment #308 (comment)

This should be able to be closed with the release of <IP_ADDRESS>
You can now call setShowCornerView(true) on the tableView before you set the adapter, so that the cornerview is drawn even if you don't have any row headers (and rows)
Results as per comment #308 (comment)

calling showCornerView = true on the tableView before setting the adapter. However, the corners are not shown.
binding.tableView.showCornerView = true

binding.tableView.setAdapter<ColumnHeader, RowHeader, Cell>(tableViewAdapter)
binding.tableView.setTableViewListener(TableViewListener(binding.tableView))
tableViewAdapter.setAllItems(
    tableViewModel.combinedTableData[0].columnHeaders,
    tableViewModel.combinedTableData[0].rowHeaders,
    tableViewModel.combinedTableData[0].cells
)


arrays.xor

Creates an array of unique values that is the symmetric difference of the given arrays.
Checklist

[x] implementation
[x] tests
[x] jsdoc

Details
const result = xor([2, 1, 'a'],[2, 3], ['a', 'a', 'c'])
console.log(result)
> [1, 3, 'c']

References

_.xor

Added in 0.65

@jkvyff Great Job! That concludes the arrays operators for 1.0. I'll run through the planning for the strings operators so you have more to pick and choose from.


CCCD: Remove "day 2 onwards" text from application to dismiss a charge

To allow this fee to be used for any applications to dismiss a charge regardless of length of trial

Needs sizing and maybe refining.  I'm not sure what was needed was clear enough

Found in the Misc fees section


Add an optional CIFS security option to fill in the mount.cifs sec field

I have an Apple Time Capsule. When you connect to these you need to define sec=ntlm. Without this option I get a permission denied error.
Let me know if there is anything I need to change.
Interestingly, when I had the drive manually mounted with the sec option and setup my containers with netshare, it connects fine, making it confusing to figure out what the problem was!

@gondor, is there anything I should change so you can pull this in?

This looks great! Sorry for the delay.  Been relocating due to a new job. I'm back now!  Merging


the new visual appearance of the option button

Detailed description
After using the newest version of DS, areas in our application look different and are now different from our previous developed mockup:
This is about the change of the visual appearance of the option button component. It now contains in addition
a circle (probably an option field) in addition to the label.
In addition, the option buttons no longer extend the whole width of the area.
We in the team are not happy with this appearance and fear that the user will be confused by this unknown component. And our application no longer looks as "beautiful" as before.
Suggested solution:
Is it possible to switch the circle in the component on and off via parameter?
Another parameter for expand over the complete width?
We are available for discussions in person
this is the original design

In our eyes, these areas no longer look optimal:

Hey @tklueber
we moved this issue to "after go live" - therefore we won't work on this before november.
If you have questions or want to discuss, feel free to contact me.


⚠ Samsung has degraded performance

In c1a3ab7, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2621 ms

Resolved: Samsung performance has improved in 43cd4b3.


WIP: Fixed broken install process on MacOS/Linux

The patch application fails on macOS and Linux both, and the process crashes out with a deceptive error message. To be honest, I'm not entirely sure what the purpose of the patch being applied is, but it looks like a lot of those changes have been merged into the vision repository. Maybe we could do away with this process?
Strangely enough, C++ 14 doesn't seem to pick up putenv -- however, setenv seems to work just fine.
The bin/ directory for the vision build does not seem to be generated. However, lib/ does exist, which is where the lylib files live. So I copy over from that directory instead.

I'm not sure if this is related or unrelated, but with this process, I see TypeError: c.toObject is not a function while trying to execute node tests/runTorch.js

@arition I've spent some time on this, but I'm not sure where the seg fault's coming from. The error looks like this:
TypeError: c.toObject is not a function
    at Object.<anonymous> (/Users/raghav/Projects/pytorch-js/torch-js/tests/runTorch.js:19:15)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
Segmentation fault: 11

Would appreciate it if you have any ideas -- if you think this looks good, I'd also be willing to work on a unit test suite for this project

@raghavmecheri Thanks for your contribution! All of three issues you mentioned do exists on MacOS/Linux, but these are essential parts on Windows. I changed your code and added conditional switches for them. If that looks good to you, I can merge the pr.

For the seg fault problem
https://github.com/arition/torch-js/blob/67136eef1b4dcb211200a86979dcf599bc89b542/tests/runTorch.js#L18
I change the forward function to return a promise, but I forget to change test file. Add await ketword before the forward function should fix the problem.

For the seg fault problem
https://github.com/arition/torch-js/blob/67136eef1b4dcb211200a86979dcf599bc89b542/tests/runTorch.js#L18
I changed the forward function to return a promise, but I forgot to change test file. Adding await keyword before the forward function should fix the problem.

Got it -- let me fix that, ensure that this builds, and then push a final commit? We should be good to merge after that

The "${CMAKE_SIZEOF_VOID_P}" STREQUAL "4" condition doesn't work as expected in my case -- I'm on a 64-bit machine, but a lib64 build doesn't exist. OSX lib files can use multiple architectures, as detailed [here]("${CMAKE_SIZEOF_VOID_P}" STREQUAL "4") -- we can probably put a condition around this, will push a change for the same.

@arition We should be good to go now.
I also patched tests/runTorch.js -- admittedly this should have been a separate commit, sorry about that haha

LGTM


Bug: Kargo Cannot Render Manifests with Same Name

Checklist

[X] I've searched the issue queue to verify this is not a duplicate bug report.
[X] I've included steps to reproduce the bug.
[X] I've pasted the output of kargo version.
[x] I've pasted logs, if applicable.

Description
If there are multiple manifests of the same kind with the same name but in different namespaces then Kargo Render will only save one of those manifest files to the Rendered Manifest branch.  This is happening because the rendered manifests are generated with names formatted like "<manifest_name>-.yaml" which does not include the namespace.  Some products like Open Cluster Management/Red Hat Advanced Cluster Management have strict requirements for the name.
Screenshots
Thi screenshot shows the input manifest files (view code in https://github.com/BenjaminNeale-Heritage/manifests-overwritten/tree/main/components/rhacm/resources/overlays/hub-cluster).

Thi screenshot shows the rendered manifest files (view code in https://github.com/BenjaminNeale-Heritage/manifests-overwritten/tree/cluster/hub-cluster/components/rhacm).

Steps to Reproduce
View config within the https://github.com/BenjaminNeale-Heritage/manifests-overwritten repository.
Version
uses<EMAIL_ADDRESS>
Logs
N/A

Just ran into this as well. Our case was managing namespaces and a service account with the same name in each. To work around we've changed the service account name to be different between the namespaces. Another workaround would be to enable the combine manifests option so you just have all.yaml.


[Feature Request] dec -> hex and hex -> dec

Something similar to https://www.rapidtables.com/convert/number/hex-to-decimal.html
would be really helpful for bitcoin development!

This is perfect for my use case. Thanks!


Adding cryptographic hash extensions

Adding MD5/SHA1/SHA256/SHA512 cryptographic hash/digest PopClip extensions.
Signed-off-by: Alen Puzic<EMAIL_ADDRESS>

These are great! Thanks.

Awesome. I have a few more that I find useful in my daily routine that I'll send later on.


Support for Babel JSX

The only one light theme I can work, though sometimes I work with React (.JSX) files, and could use proper syntax highlighting.

Added  React.js (.jsx) to the backlog

Sorry for the long waiting period, but I've been busy on my job (one week SCRUM sprints are hectic :smile: ). I'll try to implement it this week, but no later than at the weekend.

@Pszek Could you post example code and describe what the part where syntax highlighting is missing?
Tried some code from the official React JSX tutorial and for me everythings colored fine (since Atom detects JSX as a subtype of JavaScript). Only thing I've found was the missing coloring for HTML syntax code (like tag- and attribute names) returned in the return() function (this can be easily fixed by adding the .source.js, .source.js.jsx scopes to the HTML language file).

Thank You for Your effort. Here is the screenshot:

Generally it lacks colours for HTML tags and attributes.

Thanks, looks like something is not in sync with the other theme variations because onClick and closing- and opening tag brackets are not colored too (tested it in northem-atom-syntax yesterday and it worked fine).

Here's a draft of the current changes:

I like it! Could you update the source?

I'll push an update as soon as I'm back from work, just waited for your response before merging it into the next release branch :smile:

I've released v0.18.0.
This will close the backlog item  React.js (.jsx).

Thanks, it works and I like it. Although a little bit more differentiation between dark and dark-grey could be useful.


fix: bump edge-runtime to 1.58.13

What kind of change does this PR introduce?
Bump edge-runtime to 1.58.13
Changes
1.58.13 (2024-10-13)
Bug Fixes

graceful shutdown should wait until the event worker has finished all its work (#426) (fbddb16)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 60.211%

Files with Coverage Reduction
New Missed Lines
%

internal/gen/keys/keys.go
5
12.9%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.03%

Covered Lines:
6516

Relevant Lines:
10822

💛  - Coveralls


Use upstream openWakeWord

Switches to using the upstream openWakeWord Python library instead of a custom fork.
Some things not yet implemented:

Custom verifier models

I'm new to this repository, and I wanted to test this branch out because master was giving me issues.
I checked it out, installed the requirements, and it is running successfully... but I had to remove the --preload-model parameter. I use a custom wake word model that works in master (by specifying --custom-model-dir and --preload-model), but I couldn't get that to work on this branch.
I guessed that maybe OWW would be configured via Home Assistant then (since you can change the wake word there), but when I went to add it to the Wyoming Protocol like this:

But it fails:

I also tried "ok nabu" and "hey jarvis", figuring maybe it was hard-coded for testing... and nope. Didn't work either. 🙃
What am I missing here? I'd love to help test this branch!

Thanks for trying out the branch! Do you see any errors in the logs when the connection fails? I'll double check, but it was working for me.
I removed the preload model argument since it isn't needed with OWW proper.

Thanks for trying out the branch! Do you see any errors in the logs when the connection fails? I'll double check, but it was working for me.

I didn't see anything, but let me try again with --debug and I'll report back.
For what it's worth, on the same device, the Satellite can connect just fine on :10700.

If you restart OpenWakeWord with Satellites already connected to it, handle_event crashes because self.model is None.
 This is obnoxious when you're running multiple remote satellites that aren't on the same machine as the OpenWakeWord container. 😛
Screenshot shows satellites up and container restarting ( and erroring ). Then satellites off and OpenWakeWord container restarting successfully and allowing the client to connect.
You'll probably want to put some sort of self.model init function in for if you get an AudioChunk type message and self.model is None

Thanks @Graimalkin this is easy to fix 👍

hi @synesthesiam, thanks for the great work!
as a developer, is there anything that I can help to get custom verifier model support?

I was able to finally test this, and while it does show up in Home Assistant correctly, I'm getting this error on startup:
Jul 14 21:49:49 voice systemd[1]: Started wyoming-openwakeword.service - Wyoming OpenWakeWord.
Jul 14 21:49:52 voice run[10677]: INFO:root:Ready
Jul 14 21:49:53 voice run[10677]: ERROR:asyncio:Task exception was never retrieved
Jul 14 21:49:53 voice run[10677]: future: <Task finished name='wyoming event handler' coro=<AsyncEventHandler.run() done, defined at /home/voice/wyoming-openwakeword/.venv/lib/python3.11/site-packages/wyoming/server.py:31> exception=AssertionError()>
Jul 14 21:49:53 voice run[10677]: Traceback (most recent call last):
Jul 14 21:49:53 voice run[10677]:   File "/home/voice/wyoming-openwakeword/.venv/lib/python3.11/site-packages/wyoming/server.py", line 41, in run
Jul 14 21:49:53 voice run[10677]:     if not (await self.handle_event(event)):
Jul 14 21:49:53 voice run[10677]:             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 14 21:49:53 voice run[10677]:   File "/home/voice/wyoming-openwakeword/wyoming_openwakeword/handler.py", line 124, in handle_event
Jul 14 21:49:53 voice run[10677]:     assert self.model is not None
Jul 14 21:49:53 voice run[10677]:            ^^^^^^^^^^^^^^^^^^^^^^
Jul 14 21:49:53 voice run[10677]: AssertionError

Any ideas? I'm no good with Python async. 😁

I've been running this PR for a while now and it works well.
However, I can't get the VAD to work. I always get this error:
Dec 18 21:37:40 homie wyoming-openwakeword[354739]: DEBUG:root:Namespace(models_dir=PosixPath('/nix/store/3sgs163lbwd7ghzpjkl03z5cj2ida5vf-wyoming-openwakeword-1.10.0-unstable/lib/python3.11/site-packages/wyoming_openwakeword/models'), uri='tcp://<IP_ADDRESS>:10400', custom_model_dir=['/nix/store/asbacij2gzpr0jadj0rvaadq6gffxacb-source/en/yo_homie'], threshold=0.55, output_dir=None, refractory_seconds=0.5, vad_threshold=0.5, debug=True, log_format='%(levelname)s:%(name)s:%(message)s', debug_probability=False, version=False)
Dec 18 21:37:40 homie wyoming-openwakeword[354739]: DEBUG:root:Using Silero VAD (threshold=0.5)
Dec 18 21:37:40 homie wyoming-openwakeword[354739]: INFO:root:Ready
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: DEBUG:wyoming_openwakeword.handler:Client connected:<PHONE_NUMBER>8204
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: DEBUG:wyoming_openwakeword.handler:Loading openWakeWord models: ['/nix/store/asbacij2gzpr0jadj0rvaadq6gffxacb-source/en/yo_homie/yo_homie.tflite']
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: DEBUG:wyoming_openwakeword.handler:Receiving audio from client:<PHONE_NUMBER>8204
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: 2024-12-18 21:38:46.553334408 [E:onnxruntime:, sequential_executor.cc:516 ExecuteKernel] Non-zero status code returned while running Conv node. Name:'Conv_132' Status Message: Invalid input shape: {4}
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: 2024-12-18 21:38:46.553359767 [E:onnxruntime:, sequential_executor.cc:516 ExecuteKernel] Non-zero status code returned while running If node. Name:'If_25' Status Message: Non-zero status code returned while running Conv node. Name:'Conv_132' Status Message: Invalid input shape: {4}
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: DEBUG:wyoming_openwakeword.handler:Client disconnected:<PHONE_NUMBER>8204
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: ERROR:asyncio:Task exception was never retrieved
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: future: <Task finished name='wyoming event handler' coro=<AsyncEventHandler.run() done, defined at /nix/store/jir30wdrp85nff14idbw4n9p4zb713vv-python3.11-wyoming-1.5.4/lib/python3.11/site-packages/wyoming/server.py:31> exception=InvalidArgument("[ONNXRuntimeError] : 2 : INVALID_ARGUMENT : Non-zero status code returned while running If node. Name:'If_25' Status Message: Non-zero status code returned while running Conv node. Name:'Conv_132' Status Message: Invalid input shape: {4}")>
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: Traceback (most recent call last):
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:   File "/nix/store/jir30wdrp85nff14idbw4n9p4zb713vv-python3.11-wyoming-1.5.4/lib/python3.11/site-packages/wyoming/server.py", line 41, in run
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:     if not (await self.handle_event(event)):
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:   File "/nix/store/3sgs163lbwd7ghzpjkl03z5cj2ida5vf-wyoming-openwakeword-1.10.0-unstable/lib/python3.11/site-packages/wyoming_openwakeword/handler.py", line 133, in handle_event
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:     self.model.predict(chunk_array)
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:   File "/nix/store/rpwz5r4y0bqs6zpwjcvpp11y0lg9kara-openwakeword-0.6.0/lib/python3.11/site-packages/openwakeword/model.py", line 370, in predict
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:     self.vad(x)
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:   File "/nix/store/rpwz5r4y0bqs6zpwjcvpp11y0lg9kara-openwakeword-0.6.0/lib/python3.11/site-packages/openwakeword/vad.py", line 130, in __call__
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:     self.prediction_buffer.append(self.predict(x, frame_size))
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:   File "/nix/store/rpwz5r4y0bqs6zpwjcvpp11y0lg9kara-openwakeword-0.6.0/lib/python3.11/site-packages/openwakeword/vad.py", line 123, in predict
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:     ort_outs = self.model.run(None, ort_inputs)
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:   File "/nix/store/axm3krv1lrhz3n794p11qli7a44xs9dx-python3.11-onnxruntime-1.18.1/lib/python3.11/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 220, in run
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:     return self._sess.run(output_names, input_feed, run_options)
Dec 18 21:38:46 homie wyoming-openwakeword[354739]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 18 21:38:46 homie wyoming-openwakeword[354739]: onnxruntime.capi.onnxruntime_pybind11_state.InvalidArgument: [ONNXRuntimeError] : 2 : INVALID_ARGUMENT : Non-zero status code returned while running If node. Name:'If_25' Status Message: Non-zero status code returned while running Conv node. Name:'Conv_132' Status Message: Invalid input shape: {4}

I was able to finally test this, and while it does show up in Home Assistant correctly, I'm getting this error on startup:
Jul 14 21:49:49 voice systemd[1]: Started wyoming-openwakeword.service - Wyoming OpenWakeWord.
Jul 14 21:49:52 voice run[10677]: INFO:root:Ready
Jul 14 21:49:53 voice run[10677]: ERROR:asyncio:Task exception was never retrieved
Jul 14 21:49:53 voice run[10677]: future: <Task finished name='wyoming event handler' coro=<AsyncEventHandler.run() done, defined at /home/voice/wyoming-openwakeword/.venv/lib/python3.11/site-packages/wyoming/server.py:31> exception=AssertionError()>
Jul 14 21:49:53 voice run[10677]: Traceback (most recent call last):
Jul 14 21:49:53 voice run[10677]:   File "/home/voice/wyoming-openwakeword/.venv/lib/python3.11/site-packages/wyoming/server.py", line 41, in run
Jul 14 21:49:53 voice run[10677]:     if not (await self.handle_event(event)):
Jul 14 21:49:53 voice run[10677]:             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 14 21:49:53 voice run[10677]:   File "/home/voice/wyoming-openwakeword/wyoming_openwakeword/handler.py", line 124, in handle_event
Jul 14 21:49:53 voice run[10677]:     assert self.model is not None
Jul 14 21:49:53 voice run[10677]:            ^^^^^^^^^^^^^^^^^^^^^^
Jul 14 21:49:53 voice run[10677]: AssertionError

Any ideas? I'm no good with Python async. 😁

I get the same. @matt1432 , since you say this has been working well, can you share setup steps so I can quickly find what I may be doing differently to cause this?