Make editor panel icons more discreet

The Godot panel icons in the main editor window is very "shouty".
Also, not knowing what it was, I actually initially thought the icon was missing or bugged, as it's just a white square!

This alternative uses a dialog/window symbol to achieve the same effect while using only outlines so as to take less attention.

See also:

https://github.com/godotengine/godot/pull/84450

See also:
* [Use unfilled panel splitting icons #84450](https://github.com/godotengine/godot/pull/84450)

That PR uses different icons (the bar on the top isn't wider than the other bars), which I think makes it a bit less intuitive.

I like this more too. I say let's get this one in.

@eobet I've squashed the commits together and force-pushed the result to your fork, so this PR should be in a mergeable state now. 4.3 is in release freeze, so this should be good to go early in the 4.4 cycle.

Need to run the svg cleaning to handle CI

Need to run the svg cleaning to handle CI

That is strange, because I did that before I uploaded and if I try again on the file I get this:
eobet@surface:~/Downloads/svgcleaner_linux_x86_64_0.9.5$ ./svgcleaner --multipass Panels1.svg Panels1.svg
Your image is 0.00% smaller now.

@Calinou I just outlined, unioned and ran everything through svgclean again, with hopefully the correct color. Could you please double check this?

The PR is now not squashed so needs to be squashed again, and it doesn't look like you updated any files but will run CI to see if it passes

Ok, I found this. Did I finally manage? 😰

The commits were not squashed, and it seems that you used svgcleaner but the CI doesn't use that now, but instead svgo, which is handled as part of the pre-commit hooks, lots of steps I'm sorry it's quite complicated, but setting it up is pretty straightforward if you're interested in attempting, otherwise I'm sure Calinou can work it out or I can help as well, but for the setup (it just requires setting up once and then you're ready) see here (the page is for code style but the hooks are the same), after you've done that you need to do git commit --amend to make it apply to your files, possibly after squashing

I've applied svgo and squashed the commits together.

Thank you for all your help! 🙏 I see various change attempts to fix my mess from even you experienced developers who know this system, so I know there would be zero chance for me as an artist/designer to get it right. 😰 I commented in Rocket Chat that there should be an easier avenue for artists/designers to contribute, and I hope that will be considered in the future. 💖

Thanks! And congrats for your first merged Godot contribution :tada:


JS error while opening profitbricks driver

Hi there,
I have added profitbricks driver to Rancher's drivers list, but when I try to open the profitbricks, the UI part does not show up and I get this js error on browser console.
Uncaught TypeError: r.buildRenderNodes is not a function
at Function.u.build (ember.prod.js:43508)
I found out that this happens because of ember version 2.11 and I changed the ember version to use 2.9.1 (ember:"2.9.1") instead of higher versions (ember:"^2.9.1"). Which seems to get rid of that JS error and being able to work with UI part of the driver. It would be nice solving this issue by whether to change the dependencies in bower.json to use absolute ember 2.9.1 or finding out why ember 2.11 is not compatible with your UI code.
I also saw another issue after creating a host via driver's UI, by giving a name (eg. 'node') and selecting quantity of 2, which I assumed according to the description written under the Name field I will have two nodes (hosts) called node1 and node2, but instead I ended up on profitbricks platform with two hosts which both were called node1. It would be very helpful to have created hosts as it is described in UI.
Thank you!
Hadi

Hello @hnategh - Thank you for trying the Rancher UI driver and identifying the issue with the ember version. We appreciate your contribution of a proposed solution. This should be a relatively easy fix.
We will need to investigate the node quantity issue you describe. We will update the ticket as soon as these issues are addressed.

Hello @hnategh I was trying to follow the steps you mentioned to investigate the issue with the nodes name, i was not able to encounter the problem you had, i have tried with/without providing a datacenterId and in each case the driver created two servers at ProfitBricks, could you maybe provide more information about the properties you provided, maybe the steps you followed to add the profitbricks driver to rancher ui?
Thanks

@hnategh The issue with duplicate naming has been fixed in this Release, for now we have set the ember version to a fixed 2.9.1, ember changed the way the templates are being generated, we will continue to investigate the issue and possibly solve it but for now the 2.9.1 is good to use.
Please let us know if the release solved the issue for you and probably close this issue.
Thanks!

@alibazlamit The problem is gone in the new release. Thank you very much for the fix!


Suggestion : continuous calls of StringBuilder.append

Hi,
    I have found some continuous calls about StringBuilder.append(..) in some files. For example, there are several continuous calls from line 241 to 245 in the file  https://github.com/ehcache/ehcache3/blob/master/clustered/client/src/main/java/org/ehcache/clustered/client/config/ClusteringServiceConfiguration.java.
private String readablePoolsString() {
    StringBuilder pools = new StringBuilder("resourcePools:\n");
    serverConfiguration.getResourcePools().forEach((key, value) -> {
      pools.append("        ");
      pools.append(key);
      pools.append(": ");
      pools.append(value);
      pools.append("\n");
    });
    return pools.toString();
}

    If it was achieved like StringBuilder.append(..).append(..)append(..), it will promote its performance.
PS:
https://github.com/ehcache/ehcache3/blob/master/clustered/client/src/main/java/org/ehcache/clustered/client/internal/config/DedicatedClusteredResourcePoolImpl.java | 78-84

What makes you think it will be faster? pools.append returns this so both syntaxes should be identical. From a quick benchmark it seems indeed a tiny bit faster but nothing outside the error margin.

As @henri-tremblay indicates, we're not convinced this will have any effect on performance, and this isn't performance sensitive code in the first place... voting for the status quo.


Topic filters in ACL rule should support 'eq'  tag

For example:
{deny, all, subscribe, [{eq, "$SYS/#"}, {eq, "#"}]}.

Means all cannot subscribe "$SYS/#", "#". but:
{deny, all, subscribe, ["$SYS/#", "#"]}.

Means that cannot subscribe any topics.

--- a/apps/emqttd/src/emqttd_access_rule.erl
+++ b/apps/emqttd/src/emqttd_access_rule.erl
@@ -58,7 +58,7 @@ compile({A, all}) when (A =:= allow) orelse (A =:= deny) ->
{A, all};
compile({A, Who, Access, TopicFilters}) when (A =:= allow) orelse (A =:= deny) ->

{A, compile(who, Who), Access, [compile(topic, bin(Topic)) || Topic <- TopicFilters]}.

{A, compile(who, Who), Access, [compile(topic, Topic) || Topic <- TopicFilters]}.

compile(who, all) ->
all;
@@ -74,8 +74,10 @@ compile(who, {user, all}) ->
compile(who, {user, Username}) ->
{user, bin(Username)};
+compile(topic, {eq, Topic}) ->

{eq, emqtt_topic:words(bin(Topic))};
compile(topic, Topic) ->

Words = emqtt_topic:words(Topic),

Words = emqtt_topic:words(bin(Topic)),
case 'pattern?'(Words) of
true -> {pattern, Words};
false -> Words
@@ -138,6 +140,8 @@ match_topics(Client, Topic, [TopicFilter|Filters]) ->
false -> match_topics(Client, Topic, Filters)
end.

+match_topic(Topic, {eq, TopicFilter}) ->

Topic =:= TopicFilter;
match_topic(Topic, TopicFilter) ->
emqtt_topic:match(Topic, TopicFilter).


chore(project): upgrade dependencies to latest

@jonahkagan, this PR bumps the jshint dependency to 2.9.2.
Please consider merging it in and releasing a new version.

@cueedee we're no longer using coffee-jshint at Clever. Would you like to take ownership over the repo/npm package so that you can continue to upgrade it as necessary?

@jonahkagan, sure would like to, but before we proceed; I'm investigating with my employer, marviq, whether they would like to take the ownership instead of just me personally; Would you or Clever mind that idea? I'd still be happy to do it myself though, should either party have any objections.

Yep, that would be fine.

Hi @jonahkagan, marviq have indicated their willingness to take the ownership. So we are ready whenever you are.

@cueedee awesome! We'll need to know the Github org you want it transferred to (assuming https://github.com/marviq) as well as the npm username who should own the package. I think that should do it.

The GitHub org is https://github.com/marviq indeed. My npm username is cueedee<EMAIL_ADDRESS>

@cueedee I transferred you ownership of the npm package.
We can't transfer the repo to marviq because we aren't admins of the org. We can only transfer to a user, not an org.
We tried to transfer ownership to you but weren't able to because you already have a fork of it. I see three ways forward:

You delete your fork and we transfer the repo to you
We delete this repo and your fork becomes the source repo (not sure if this will work)
You tell us the username of someone else at marviq and we transfer it to them

Let me know what you want to do!

Understood. I have deleted my fork. Try transfering it to me first. I figure I should be able to transfer it to marviq myself once that's completed.

Guys, @cozmo, I see only now that you've attempted a transfer and I realize I've missed the window of opportunity for accepting it. My apologies; could you please retry?

@cueedee I've re-initiated the transfer. Want to try again?

@cozmo; Thank you! It's done.

Guys, @cozmo, @jonahkagan, I've done the chores. On GitHub, I removed lingering webhooks & services and replaced references to Clever wherever I could find them. On npm, all maintainers @ clever were removed.
Afaict, that should complete it but to be sure, is there anything that you think remains to be done or undone?
In any case, thanks for being cool!

Sounds good to me. We'll let you know if we find anything else. Thanks for taking this on!


Oracle query tuning

Please describe the problem that your request should resolve.
Some values needs to be adjusted because was not delivered by MDW
Describe the solution you'd like
Once the MDW response will be updated, we can accommodate it on our side
Tracking: https://github.com/aeternity/ae_mdw/issues/1295

[ ] Replace N/A values with values from response
[ ] Enable 4 versions of query panel (Response available, Query timed out, Response expired, ...)

Is it already possible to achieve the same outcome in any other way? If so, how?
Not possible
Additional context
Current status

This can now be implemented with Queried At and Respond At columns.
The endpoint https://mainnet.aeternity.io/mdw/v2/oracles/oracleId/queries should be used.

Already implemented.


Support Eurosport Player

Possible to add https://www.eurosportplayer.com to youtube-dl supported websites?
I have an annually paid subscription and if it's needed please let me know.
No need to say it's a very complicated website and I deeply believe just only youtube-dl python experts are able to make a way to download its videos.
Cheers

Yes, Obviously its name indicates it only broadcasts in European countries.

post an example of the urls you're trying to watch.
an account would be needed to work on this site, i'm getting this message when i try access any video:
Commencer à regarder Eurosport Player.

Regardez des événements, des matchs, des temps forts et des vidéos de vos sports préférés!
S'abonner

OU Connexion

It's probably encrypted with something not yet cracked, like Adobe Pass. See #14004

It's not legal. I've just receive the answer from Eurosport Customer Support. So, please skip this request because of the potential copyright issues.

Hi,
Thank you for contacting the Eurosport Player team and I apologize for the delayed answer.
From your e-mail I understand that you wish to download videos from our plate-form.
I would like to inform you that as the broadcast rights for sports events are strongly regulated, we are not allowed to let you:
Record or download videos
Obtain the event images broadcasted on our antenna
I hope you are enjoying your favorite sports on Eurosport Player.
I remain at your disposal for any further information.
Best,
Elisabeth

IMO that doesn't mean that the Eurosport Player shouldn't be supported. If the downloaded videos are not distributed online, there should not be an issue.

@beta2k if you want this service to be supported then you can open a new issue for that.

done: #17365


refactor(server): Add AutoCausalLM to avoid skipping CausalLM's constructor

Currently BLOOMSharded is a subclass of CausalLM, while it skips CausalLM's constructor. This is a surprising behavior that we might want to avoid.
This PR extracts CausalLM's constructor to AutoCausalLM to detect settings from model_id, so that we don't have to skip CausalLM's constructor in custom models.

Makes sense to me. On thought HF transformers has high redundancy in their code, keeping inheritance footprint rather minimal. https://github.com/huggingface/transformers/tree/main/src/transformers/models This enabled running and integrating the latest changes fast.

Changes in this PR is already in our internal repository and get tested there. The possibility to break this repository is minimal but not zero because of the lack of publicly visible CI. I am merging this PR. If you encountered any issue, feel free to report it.

Exactly, I think modularization is a goal that we want to do different from HuggingFace's repositories.


[Bug]: Internal Server Error after updating container

Describe the bug
Internal Server Error when trying to access the webUI after updating the container automatically last night.
Debug Output
TypeError: Cannot read properties of undefined (reading 'NUT_HOST')
at o.loadFromEnvVars (/.next/server/chunks/161.js:1:573)
at o.initWithEnvVars (/.next/server/chunks/161.js:1:787)
at Module.em (/.next/server/instrumentation.js:5:10240)
at async NextNodeServer.runInstrumentationHookIfAvailable (/node_modules/.pnpm/next@15.0.0_@babel+core@7.23.6_@playwright+test@1.48.1_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/next-server.js:493:9)
at async NextNodeServer.prepareImpl (/node_modules/.pnpm/next@15.0.0_@babel+core@7.23.6_@playwright+test@1.48.1_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/next-server.js:487:9)
Steps to reproduce
Not sure
Device Type
Unraid - Docker
UPS Device
APC Back-UPS XS 1050M - usbhid-ups
Last Working Version
No response

can you share your docker run or compose?

I have the exact same issue here, with no mapped settings.yml and only using env variables.

I have the exact same issue here, with no mapped settings.yml and only
using env variables.
śr., 23 paź 2024 o 19:43 Armond Avanes @.***>
napisał(a):

I have the exact same issue here, with no mapped settings.yml and only
using env variables.
—
Reply to this email directly, view it on GitHub
https://github.com/Brandawg93/PeaNUT/issues/82#issuecomment-2432982072,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4MSZSAGT2UEYYUXJITW3DZ47N2HAVCNFSM6AAAAABQOS4GZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZSHE4DEMBXGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I’m working on this. Check back soon!

Could someone please test my latest test version? If it works, I'll push an update for everyone else.
test version
https://github.com/Brandawg93/PeaNUT/pull/83

Could someone please test my latest test version? If it works, I'll push an update for everyone else.
test version #83

Switched repo to :test. Seems to have fixed the issue. Any chance you could add my feature request too? :p

Awesome! And I’m still looking into UI customization like that. For now, you could use the persistent data example to build a grafana graph with that feature.

Fixed in v3.1.2!


[Question] How to add global methods like paginate()

I use a paginate plugin: https://www.npmjs.com/package/mongoose-paginate-v2
So I have to add a paginate() method in all models like this:
static paginate: (where: object, options: PaginateOptions) => Promise<PaginateResult<SiteSchema>>;

Is there any way to add this declaration globally?

as far as i can tell (from a rough look at the readme/doc of this module), it is global across all models, and only a model function, so you could make a base model that has this function and all others can extend from it(so that not every model/schema has to include the definition)

Thanks, but how could I pass SiteSchema to  the BaseSchema ?

i dont know what these schemas are (i couldnt find it in the supplied link), i can only generally say this:
typegoose cant extend normal schemas, at least not without the user doing something, like if its a
plugin: the plugin functions must be defined in the class itself,
if its a schema that should be added: use buildSchema and modify your schema, use addModelToTypegoose (version 6.0.0+), this function still needs a class for the type definitions, otherwise the point of typegoose is not used

@Ben305 this can be closed as "solved" / "fixed"
to give a final answer:
to use global methods, create a class that has the type on it, and any class that should have this type should extend it, and then apply the plugin globally to mongoose (i cant say for sure, because i dont work with plugins)


Transcript parsing? Pattern [Question]:

What is your question?
I've been messing around with the youtube and audio transcription features for a project I am actively involved in where Im utilizing it for data gathering purposes. Specifically, for the use of gathering interview data.
However, one thing I will note is that while it is good at providing complete transcripts, it does not provide any grammatical punctuation nor attribution of who is talking.
I have attempted to create a pattern that actually goes through and identifies when a person is speaking, making sure that things are properly punctuated (as well as unrolling some of the filters --basically filling in adequate swear words that have been censored), however, for some reason I cannot get fabric to apply the pattern and provide the FULL transcript. I am utilizing only local models, and have even tried using ones that have significantly higher context windows, and have even attempted to utilize customized modified patterns but alas to no avail.
Does anyone have any ideas how I might remedy this?  If I could remedy this, this would actually significantly speed up some of my data gathering purposes.  I've created TWO patterns one involving agents and one not involving agents. The agents one seems to work far better from the limited outputs I have seen. Is there any means of expanding the token output of a pattern, or, setting a universal max token limit for responses?

Hey, this bugged me as well. My fix is one line & the one and only change in this pull request: https://github.com/danielmiessler/fabric/pull/600


Add: Unifi Sports 1

Channel Name
Unifi Sports 1
Native Name (optional)
No response
Network (optional)
No response
Country
MY
Subdivision (optional)
No response
City (optional)
No response
Broadcast Area
c/MY
Languages
msa;eng
Categories (optional)
sports
NSFW
FALSE
Launched (optional)
2020-02-28
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://unifi.com.my/tv/shows-category/sports
Logo
https://upload.wikimedia.org/wikipedia/commons/thumb/f/f3/Unifi_Sports.png/1200px-Unifi_Sports.png
Notes
Channel stream link: https://unifi-live05.secureswiftcontent.com/UnifiHD/live11.mpd

Added in https://github.com/iptv-org/database/commit/5ed3cb4357a9223750e65ff08f2eb10c871a5a4d


Coinomi compatibility

A throwaway comment about Trezor on reddit:
http://www.reddit.com/r/Bitcoin/comments/32z4kg/trezor_omg/
The seed is compatible with the coinomi wallet.

Worth checking out sometime for MBHD compatibility

Agreed. I've pushed it further down the time line for now.

I don't think we should spend time on this - we use Lighthouse compatibility as the go to wallet.
Closing


Address already in use ('<IP_ADDRESS>', 65432)

Describe the bug
g'day... The continue server won't start on OSX Ventura 13.5 with:
python3 --version
Python 3.11.4
python --version
Python 3.11.4
python2 --version
Python 2.7.18

The continue.log file reads
Started server process [36787]
Waiting for application startup.
Application startup complete.
Uvicorn running on http://<IP_ADDRESS>:65432 (Press CTRL+C to quit)
Shutting down
Waiting for application shutdown.
Application shutdown complete.
Finished server process [36787]
Using selector: KqueueSelector
INFO:     Started server process [5629]
INFO:     Started server process [5627]
INFO:     Started server process [5632]
INFO:     Waiting for application startup.
INFO:     Waiting for application startup.
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Application startup complete.
INFO:     Application startup complete.
ERROR:    [Errno 48] error while attempting to bind on address ('<IP_ADDRESS>', 65432): address already in use
ERROR:    [Errno 48] error while attempting to bind on address ('<IP_ADDRESS>', 65432): address already in use
INFO:     Waiting for application shutdown.
INFO:     Uvicorn running on http://<IP_ADDRESS>:65432 (Press CTRL+C to quit)
INFO:     Waiting for application shutdown.
INFO:     Application shutdown complete.
INFO:     Application shutdown complete.
Testing logs
Cleaning up sessions
Testing logs
Cleaning up sessions
Task exception was never retrieved
future: <Task finished name='Task-1' coro=<Server.serve() done, defined at /Users/renzor/.continue/server/env/lib/python3.11/site-packages/uvicorn/server.py:61> exception=SystemExit(1)>
Traceback (most recent call last):
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/uvicorn/server.py", line 159, in startup
    server = await loop.create_server(
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 1525, in create_server
    raise OSError(err.errno, 'error while attempting '
OSError: [Errno 48] error while attempting to bind on address ('<IP_ADDRESS>', 65432): address already in use

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/nest_asyncio.py", line 35, in run
    return loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/nest_asyncio.py", line 84, in run_until_complete
    self._run_once()
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/nest_asyncio.py", line 120, in _run_once
    handle._run()
  File<EMAIL_ADDRESS>line 80, in _run
    self._context.run(self._callback, *self._args)
  File<EMAIL_ADDRESS>line 350, in __wakeup
    self.__step()
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/nest_asyncio.py", line 196, in step
    step_orig(task, exc)
  File<EMAIL_ADDRESS>line 267, in __step
    result = coro.send(None)
             ^^^^^^^^^^^^^^^
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/uvicorn/server.py", line 76, in serve
    await self.startup(sockets=sockets)
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/uvicorn/server.py", line 169, in startup
    sys.exit(1)
SystemExit: 1
Task exception was never retrieved
future: <Task finished name='Task-1' coro=<Server.serve() done, defined at /Users/renzor/.continue/server/env/lib/python3.11/site-packages/uvicorn/server.py:61> exception=SystemExit(1)>
Traceback (most recent call last):
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/uvicorn/server.py", line 159, in startup
    server = await loop.create_server(
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 1525, in create_server
    raise OSError(err.errno, 'error while attempting '
OSError: [Errno 48] error while attempting to bind on address ('<IP_ADDRESS>', 65432): address already in use

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/nest_asyncio.py", line 35, in run
    return loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/nest_asyncio.py", line 84, in run_until_complete
    self._run_once()
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/nest_asyncio.py", line 120, in _run_once
    handle._run()
  File<EMAIL_ADDRESS>line 80, in _run
    self._context.run(self._callback, *self._args)
  File<EMAIL_ADDRESS>line 350, in __wakeup
    self.__step()
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/nest_asyncio.py", line 196, in step
    step_orig(task, exc)
  File<EMAIL_ADDRESS>line 267, in __step
    result = coro.send(None)
             ^^^^^^^^^^^^^^^
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/uvicorn/server.py", line 76, in serve
    await self.startup(sockets=sockets)
  File "/Users/renzor/.continue/server/env/lib/python3.11/site-packages/uvicorn/server.py", line 169, in startup
    sys.exit(1)
SystemExit: 1

But lsof -i:65432 shows nothing running on that port.

@renzor-fist g'day. Looking into this now. I'm curious whether you have more than one VS Code window open - perhaps two instances are attempting to start the server at the same time. Also, I assume this is latest version, v0.0.300?
As a temporary solution, does reloading the window do any good?

Alright, thank you. This must be a zombie process stemming from the Node.js error encountered yesterday. Probably a force kill should do the trick, I'll update you soon

@renzor-fist Given that this was a new problem as of yesterday, I believe I understand the source of the problem and have solved it. Definitely want to keep this issue open until it's confidently verified that this was indeed fixed. Newest versions (v0.0.302+) include the relevant update.

Ok, looking back into it today. One possibility is that the process was somehow started by a different user, which would explain why it doesn't show when using lsof.
It would be useful to know whether a sudo lsof shows the process, or alternatively something like: sudo netstat -tanl | grep 65432

Hi @renzor-fist, I've successfully solved what I believe was the cause of your problem. It is available in v0.0.307.
What I believe was the problem was that my GitHub Actions was not successfully updating the binary, leading to me falsely telling you that the problem was solved. I've also solved a few bugs along the way that additionally would have led to this outcome, and have made sure that "View Logs" will show what's going on.

That seems like the right intuition about what's wrong. You can check ~/.vscode/extensions/continue.continue-0.0.307/server/exe/run is the binary

@renzor-fist I've been looking into this today. There's a switch in pyinstaller to specify architecture, but GitHub Actions doesn't yet support Apple Silicon. I can build a binary on my machine for arm64, but this isn't a reliable solution.
Depending on how much time you were willing to spend on this, it would be useful to know
a) (quick) whether Rosetta is installed (can check by open Applications in Finder, right clicking on Safari, "Show Info", and checking whether there is a checkbox like in the image below for "Open with Rosetta"). If it isn't already installed, then installing Rosetta could be a temporary solution.

b) (less quick, don't worry about it unless you are legitimately curious)

install pyinstaller with pip3 install pyinstaller
git clone https://github.com/continuedev/continue
cd continue/continuedev
poetry install (if poetry isn't installed yet, then curl -sSL https://install.python-poetry.org | python3 -)
cd ..
pyinstaller run.spec, which will create the binary at ./dist/run, and you can then test to see whether a binary built on your own machine works

@renzor-fist ...finally...we are shipping with an M1-built binary, which I believe will solve this bug. The new version 0.0.323, and it should work out-of-the-box. If not, please let me know, don't want to keep you waiting any longer

@renzor-fist I'm going to close this issue since we've verified with other M1 users that it is solved—other problems should probably be classified in another issue, but if anything is still broken please create one or comment here : )


Add contrast - game text to background

Possibly:

Modify text (font, colour, placement etc.)
Modify background (change image, edit background, opacity etc.)

Part of #7

Can I take up this issue?

Sure, assigning it to you @piba941


Error reading custom ACPI table. (VERR_PATH_NOT_FOUND)

When I exported image in ova file and tried to run in another machine I got the below error.
Error reading custom ACPI table. (VERR_PATH_NOT_FOUND).   Result Code:  E_FAIL (0x80004005) Component:  ConsoleWrap Interface:  IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
VirtualBox Logs:
00:00:02.259913 ACPI: Reading custom ACPI table(0) from file '/home/nav/Desktop/antivm/DSDT_OptiPlex9020.bin' (0 bytes)
00:00:02.259924 VMSetError: F:\tinderbox\win-6.0\src\VBox\Devices\PC\DevACPI.cpp(4013) int __cdecl acpiR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_PATH_NOT_FOUND
00:00:02.259929 VMSetError: Error reading custom ACPI table.
00:00:02.259937 PDM: Failed to construct 'acpi'/0! VERR_PATH_NOT_FOUND (-103) - Path not found.
How to run the imgae in other machines?
Do I have to run the script in that machine also?

Just run this:
VBoxManage.exe setextradata REPLACEME1 VBoxInternal/Devices/acpi/0/Config/CustomTable C:\Users\SOMETHING\SOMETHING\REPLACEME2.bin
were REPLACEME1: name of your vm and REPLACEME2: name of your ACPI tables
hope that helps

@anilplp did the suggestion that @ThisIsNotMalware fix the issue?

Apologies for late reply
@ThisIsNotMalware  that commmand worked fine.
@nsmfoo yes it fixed the issue

@anilplp  no apologies needed, I'm a master of slow responses myself ;)
Great, then I will close this case

How do you run this command in linux?

@alanjsebas Just use vboxmanage command. See https://github.com/DeepVAC/MLab/issues/61


the request AST should be merged before invoking middlewares

Nested inline fragments and fragment spreads should be resolved/merged before invoking the first middleware. This should simplify the middleware development because middlewares don't need to traverse complex nested structures but only work on a "clean" graph.

A uniform way to access the arguments of a field. That does handle default arguments, literal arguments and variables as arguments would be helpful too. This could be done in the same step by inlining defaults & variables.

Implemented in the next branch.


Button: The states should be passed down to all child elements

The Button widget has a label widget as a child element. These child elements should inherit the states of a the parent widget (e.g. "hover") should be inherited by the parent element.

Commit 3c4a00f belons to issue #49


Finish some tasks to set up the repository.

[x] make config dummy to ensure it works
[x] use pyproject.toml instead of setup.py, requirements.txt
[x] change testing to unittest
[x] add some additional issue templates
[x] update readme, pyproject.toml, gitignore
[x] add a dummy test to be filled in later
[x] add model files using lsf -> for tests

@iulusoy would you like to have a look at this? not much happened - just added some files (model files for testing, etc, see description...). Haven't worked a lot with setting up python projects...

made a mistake: added on accident a binary file and a bunch humongous csv files for the google-perch model, which should probably live in git lsf... should this be done separately?

@iulusoy

re-added pytest
resolved an issue with the gitignore (forgotten "!")
removed the experimental "main.py"


[HUDI-6096] Update table name in hoodie.properties from the write config when it is changed.

[HUDI-6096] Update table name in hoodie.properties from the write config when it is changed.
Change Logs

Check for table name change within initTable
If table name is changed, hoodie.properties is updated
Added a unit test

Impact
Makes it easy to update table name of a dataset
Risk level (write none, low medium or high below)
No known risk
Documentation Update
None required
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Yes, we can update anything in hoodie.properties. But not all configs should be updated and some may not work directly.
e.g. changing table type from MOR to COW will surely not work (what happens to data in log files?)

Yes, we can update anything in hoodie.properties. But not all configs should be updated and some may not work directly. e.g. changing table type from MOR to COW will surely not work (what happens to data in log files?)

I don't think we should change table name with just write config change from an ingestion job, somehow we need to confine the name change to entrance like the catalog operations.

yes. I also inclined towards, not letting changing table properties via write config.
we should advise users to go via alter table or via hudi cli for such admin operations.

Abandoning as the consensus is to not update this automatically.


Why is my repository suddenly consider nearly 50% XML?

I have a repo which was considered 75% F# and 25% C#. Now that make sense. I pushed up four commits in which I only added F# code, refreshed the page, and suddenly my project was considered nearly 50% XML. (Is this a coincidence that I just pushed then? Did Linguist just update between page loads?) The only XML I have in the project are NuGet configuration files and Visual Studio project and solution files. So true, there is XML under source control, but it's not a project done in XML... it feels weird to have it reporting nearly 50% XML.

A similar project is not showing any XML, which is evidence that this is a misidentification.

Same thing happened to be yesterday.  I have a predominately PHP project and now it is showing mostly as XML.

This is because of #2097.

@larsbrinkhoff Interesting. I can see why they did that, but in the case of .csproj, .nuspec, .fsproj, .sln and other such files, XML is not so much a markup language that is part of the project as a configuration language that is part of its metadata.

In your own repositories, you can override file classification in the .gitattributes file.

@larsbrinkhoff I added this, and it doesn't seem to have fixed it. What did I do wrong?

I'm not sure linguist-type is implemented yet?  I believe linguist-vendored should work:
https://github.com/github/linguist#overrides

@Kazark The best solution for you here is to use linguist-documentation I think. Unlike linguist-vendored it will still show the files in diffs.

This seems to have fixed it:
*.[cC]onfig linguist-documentation
*.sln linguist-documentation
*.fsproj linguist-documentation
*.csproj linguist-documentation
*.shproj linguist-documentation
*.projitems linguist-documentation
*.targets linguist-documentation
*.plist linguist-documentation

@aroben Should I leave this issue open?

Yes please. I'm working on changing Linguist to exclude these project files by default.

Awesome. I was just telling my wife how much I love GitHub. This is just one more example.

This is now fixed on github.com.

This is now fixed on github.com.

Super! That was quick.


Date decoding issue in JWT

When we decode the expiration date sent to our JWT handler it decodes it as only a few seconds after the current time. Even if the date set on the cookie is 24 hours in the future. We will need to fix this before pushing the change to use owner_id from our authentication middleware.
This seems like a new issue

I think I already pushed the fix for this, the jsonwebtoken lib docs are wrong so I switched to adding our own date.


Error: Failed to load gRPC binary module

Expected behavior
Should run npm start, gauge should execute the specifications in the /specs folder.
Actual behavior
    throw error;
    ^

Error: Failed to load gRPC binary module because it was not installed for the current system
Expected directory: node-v67-win32-x64-unknown
Found: [node-v57-win32-x64-unknown]
This problem can often be fixed by running "npm rebuild" on the current system
Original error: Cannot find module 'C:\Users\Void Scroll\AppData\Roaming\gauge\plugins\js\2.3.2\node_modules\grpc\src\node\extension_binary\node-v67-win32-x64-unknown\grpc_node.node'
    at Object.<anonymous> (C:\Users\Void Scroll\AppData\Roaming\gauge\plugins\js\2.3.2\node_modules\grpc\src\grpc_extension.js:53:17)
    at Module._compile (internal/modules/cjs/loader.js:722:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:733:10)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
    at Function.Module._load (internal/modules/cjs/loader.js:552:3)
    at Module.require (internal/modules/cjs/loader.js:658:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (C:\Users\Void Scroll\AppData\Roaming\gauge\plugins\js\2.3.2\node_modules\grpc\src\client_interceptors.js:145:12)
    at Module._compile (internal/modules/cjs/loader.js:722:30)

Whenever the script is run, this happens. I have updated Node.js with which I use Gauge to the latest release. Reverting back to my previous version does not fix the error.
Steps to reproduce

Update Node.js to 11.2.0
Run specifications

Gauge version
Commit Hash: ff6c0c3

Plugins
-------
html-report (4.0.6)
js (2.3.2)
screenshot (0.0.1)

@VoidScroll  This happens after the nodejs update. gauge-js plugin uses grpc which is a native binding. When you install the gauge-js install all the required npm modules. Since you have grpc cached in npm it will install the older one which will not be compatible.
Can you please try to run npm rebuild in the gauge-js plugin directory?
In your case the dir is C:\Users\Void Scroll\AppData\Roaming\gauge\plugins\js\2.3.2 (from the stacktrace).

I have resolved the issue.
I may have gone overboard, but I removed Node and all its installation files, I removed Gauge on my machine, I have removed NPM, I removed every module in my working directory, and I did a clean reinstall of everything. Good reminder not to update NodeJS
Thanks for the help 👍


warnings coming from library's .cabal

Warning: libraries/text/text.cabal:4:1: The field "bug-reports" is specified
more than once at positions 4:1, 42:1
Warning: libraries/haskeline/haskeline.cabal:4:1: The field "category" is
specified more than once at positions 4:1, 10:1
Warning: utils/hpc/hpc-bin.cabal:11:2: Tabs used as indentation at 11:2
Warning: libraries/text/text.cabal:4:1: The field "bug-reports" is specified
more than once at positions 4:1, 42:1

Indeed, it's the Cabal library (which we use directly now, instead of ghc-cabal) that emits those, we don't really have a handle on them.


lxd-runin.sh doesn't work on Fedora

✗ bin/lxd-runin.sh
Creating container 'linux' (fedora:30)
Error: The remote "fedora" doesn't exist
Error: not found
Error: not found

@techtonik ping.

$ lxc launch ubuntu:18.10
Creating the container
Container name is: talented-deer
Starting talented-deer
$ lxc launch fedora:30
Error: The remote "fedora" doesn't exist

Didn't work for fedora, because ubuntu: is lxc remote.
$ lxc remote list -q
+-----------------+---------------------------------------------------+---------------+-------------+--------+--------+
|      NAME       |                        URL                        |   PROTOCOL    |  AUTH TYPE  | PUBLIC | STATIC |
+-----------------+---------------------------------------------------+---------------+-------------+--------+--------+
| images          | https://images.linuxcontainers.org                | simplestreams | none        | YES    | NO     |
+-----------------+---------------------------------------------------+---------------+-------------+--------+--------+
| local (default) | unix://                                           | lxd           | file access | NO     | YES    |
+-----------------+---------------------------------------------------+---------------+-------------+--------+--------+
| ubuntu          | https://cloud-images.ubuntu.com/releases          | simplestreams | none        | YES    | YES    |
+-----------------+---------------------------------------------------+---------------+-------------+--------+--------+
| ubuntu-daily    | https://cloud-images.ubuntu.com/daily             | simplestreams | none        | YES    | YES    |
+-----------------+---------------------------------------------------+---------------+-------------+--------+--------+
| ubuntu-minimal  | https://cloud-images.ubuntu.com/minimal/releases/ | simplestreams | none        | YES    | NO     |
+-----------------+---------------------------------------------------+---------------+-------------+--------+--------+

It can be fixed by usinh images: remote for all OS.
$ lxc launch images:ubuntu/18.10
Creating the container
``

Now container starts successfully, and then the scripts fails with the below error.
✗ bin/lxd-runin.sh
Creating container 'linux' (fedora/30)
Creating linux
Starting linux
Error: Add disk devices: Failed to setup device: Source path /var/lib/snapd/hostfs/home/anatoli/a/linux doesn't exist for device linux-shared
/bin/sh: line 0: cd: linux: No such file or directory

@abitrolly looks like you're running lxc from a snap. It really looks like https://github.com/lxc/lxd/issues/3660 Can you tell your lxc version?

✗ lxc version
Client version: 3.16
Server version: 3.16

I forgot that I am using remote LXD server to run containers. It probably can not add local disk device to remote host.
✗ lxc remote list
+----------------+------------------------------------------+---------------+-------------+--------+--------+
|      NAME      |                   URL                    |   PROTOCOL    |  AUTH TYPE  | PUBLIC | STATIC |
+----------------+------------------------------------------+---------------+-------------+--------+--------+
| images         | https://images.linuxcontainers.org       | simplestreams | none        | YES    | NO     |
+----------------+------------------------------------------+---------------+-------------+--------+--------+
| local          | unix://                                  | lxd           | file access | NO     | YES    |
+----------------+------------------------------------------+---------------+-------------+--------+--------+
| ubuntu         | https://cloud-images.ubuntu.com/releases | simplestreams | none        | YES    | YES    |
+----------------+------------------------------------------+---------------+-------------+--------+--------+
| ubuntu-daily   | https://cloud-images.ubuntu.com/daily    | simplestreams | none        | YES    | YES    |
+----------------+------------------------------------------+---------------+-------------+--------+--------+
| srxd (default) | https://<IP_ADDRESS>:3443                | lxd           | tls         | NO     | NO     |

Well, I am not sure that's LXD is capable to do anything on client side. After all, it is just a Go API over standard Linux containers, and magic happens on containers host. Therefore, yes - device add won't work from your remove Fedora.


Unable to update database - wrong directory reference

Describe the bug
Update-Database is not possible due to wrong working directory.
To Reproduce
Steps to reproduce the behavior:
Have project with multiple solutions.
Open aspnet-core directory.
Here is your working solution and src directory with project folders.
To update database, in command line open aspnet-core\src\MyProject.EntityFrameworkCore project directory and type 'dotnet ef database update'.
Even if this directory is open in the terminal, rider-efcore GUI doesn't respect it and picks root, which causes:
"C:\Program Files\dotnet\dotnet.exe" ef database update --project src\MyProject.EntityFrameworkCore\MyProject.EntityFrameworkCore.csproj --startup-project src\MyProject.Web.Host\MyProject.Web.Host.csproj --context MyProject.EntityFrameworkCore.MyProjectDbContext --configuration Debug<PHONE_NUMBER>1111_AddSomeEntities
Specify which project file to use because this 'D:\MyProjects\MyProject1\src\server\aspnet-core' contains more than one project file.
Process terminated with exit code 1

Expected behavior
Allow to select working directory or set Migrations project as working directory (can full path for projects solve this issue?)
Screenshots

Environment (please complete the following information):

OS: Win 11 x64 build 23511
.NET SDK info (installed ones and version used within Rider): 7.0.306
Plugin version: 232.0.0-rc1
Rider version: 2023.2 RC

Additional context
stable version has the same issues.

Hi @pawelel, thanks for the issue! Do you have a minimal repro of the issue? It's not clear to me why EF Core fails to execute the command line, because both Migrations and Startup projects paths seems valid and they are relative to the solution directory (which is considered as /aspnet-core)

Do you have your projects in a completely different folder than the .sln file?

Hmm, I think similar situation can be found here: https://aspnetboilerplate.com/Templates https://github.com/aspnetboilerplate/aspnetboilerplate

@seclerp removing .dcproj files allowed me to update. Is it possible to ignore those files somehow?

Unfortunately, not really. There is an issue on dotnet ef side, not sure if we can address it.
We can't change the working directory for the command because then it will not work with the locally installed dotnet ef. I suggest you describe your case at the issue above.
From our side, I'll try to find some workarounds, as a temporary solution.

Thanks, luckily now we know the reason why migration doesn't work. The solution may be to temporarily move the *proj, .sln files from the working directory

Thanks for the investigation!
However, I still have no clue how to reproduce the issue with provided template:
> dotnet ef migrations add --project src/EFCoreIssue.EntityFrameworkCore/EFCoreIssue.EntityFrameworkCore.csproj --startup-project src/EFCoreIssue.Web.Host/EFCoreIssue.Web.Host.csproj --context EFCoreIssue.EntityFrameworkCore.EFCoreIssueDbContext --configuration Debug blablablablablabla
Build started...
Build succeeded.
The Entity Framework tools version '7.0.1' is older than that of the runtime '7.0.3'. Update the tools for the latest features and bug fixes. See https://aka.ms/AAc1fbw for more information.
Done. To undo this action, use 'ef migrations remove`

The same with database update. Maybe you can provide some step-by-step guide to reproduce? It will be very helpful and will provide the necessary info to look into possible workarounds.

Yeah, now it's reproducing. Unfortunately, the only option right now is to tweak with the .dcproj files location.
Closing this for now.
P.S. It's funny that the issue will not be reproduced when you have only 1 .*proj file near .sln, only more than one (source). Why it's treated like a project directory - I think because of local tools infrastructure, so fix may not be so trivial.


Correct URIs in resourcemap.xml

The URIs in the resourcemap.xml are created incorrectly.  I tested both generic resource and time series resource and both had problems.
Testing on dev.hydroshare.org.  See this generic resource for reference:
http://dev.hydroshare.org/resource/26973647d27d46b58be3dcd1d889f6bb/
The URI to the content file was created with what looks like a relative path:
/tmp/hydroshare/26973647d27d46b58be3dcd1d889f6bb/2<IP_ADDRESS>.03.01/contents/TWDaniels_Temperature.csv
Instead, this should be:
http://dev.hydroshare.org/resource/26973647d27d46b58be3dcd1d889f6bb/2<IP_ADDRESS>.03.01/contents/TWDaniels_Temperature.csv
The URI to the science metadata file was created with the name of the resource in the path AND refers to a JSON file that doesn't exist:
http://hydroshare.org/resources/Air Temperature at the TW Daniels Experimental Forest/resourcemetadata.json
Instead, this should be:
http://dev.hydroshare.org/resource/26973647d27d46b58be3dcd1d889f6bb/2<IP_ADDRESS>.03.01/data/resourcemetadata.xml
The URI to the resource map file has the same problem as the URI to the science metadata document.
Final Note:  When I looked at the resource map for the time series resource that I created (http://dev.hydroshare.org/resource/f5e4c6083e8d4e91be216295f7b6282e/), it did not have the issue with referencing a JSON file as the resource metadata, but the URIs had all of the other problems described above.

@horsburgh Should the URL for the content file be (added 'data' sub path):
http://dev.hydroshare.org/resource/26973647d27d46b58be3dcd1d889f6bb/2<IP_ADDRESS>.03.01/data /contents/TWDaniels_Temperature.csv

Yes, because that URI should resolve directly to the file. I am assuming we have resolved for sure that we are versioning via a timestamp in the URL?

You mean we need the timestamp as shown above for the content file URI?

I think that having the time stamp in the URL may be awkward and I am not sure how feasible it is.  @mjstealey please comment on how you suggest we resolve this.  At present a URL like @pkdash wrote above resolves to a 404 error and the pattern for retrieving a single file from a resource is different.

I think the timestamp in the URL is a hold-over from when HydroShare was creating a new bag every time an edit was made to the metadata.  Our documentation about identifiers and formal publication of HydroShare resources states that HydroShare will create a new unique identifier (and hence a new resource) for all subsequent versions of a resource.  So, if we stick with that, versioning shouldn't be done using timestamps in the URL.
This is also related to #170.

In addition to URI issues (as described above) there are many other issues with the generation of the resourcemap.xml document. I think I have fixed all the URI issues now. The other issues may take a while as I have to learn how the tool used for creating this xml document works.

Will be implementing these additional changes as suggested by Jeff.
Pabitra,
What you have now as 'ore:isDocumentedBy' should be 'citoterms:isDocumentedBy'.  This just needs to be relabeled.
Also, perhaps we should bag the hsterms xmlns.  We are only using one term in the resource maps – "hydroshareResourceType" and I'm not sure it warrants using a separate namespace for one term.  As it turns out (and after studying Dublin Core a bit more, there is a "dcterms:type" term that we could use instead.  There is a suggested vocabulary for that element here (http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/). But we don't necessarily have to use it.  I think the reason I didn't suggest this in the first place is the fact that Dublin Core has this vocabulary already and the HydroShare resource types are not in the list.  But, the definition of the "dcterms:type" element works for our needs.  It is as follows:
http://purl.org/dc/terms/type - The nature or genre of the resource.
So, my proposal is to change the element "hsterms:hydroShareResourceType" to just "dcterms:type".
Other than those two things, I think the resource map looks good given that I think you have already removed the timestamps from the URIs.
I noted in testing alpha that the URL to a resource landing page is like this:
http://alpha.hydroshare.org/resource/21eebbe42eaa423da197edf74f4a289e/
Notice the singular "resource" in the URL.  I just reviewed this issue that has already been closed and that deals with URL patterns for HydroShare:
https://github.com/hydroshare/hydroshare/issues/63
So, it looks like we need to make the URIs in the Resource Map Documents to have "resource" instead of "resources" to match what has already been implemented.  Do you want me to post this to GitHub or do you want to just fix it when you make the other fixes you will make today?

There is still repetition between dc and dcterms.  Perhaps this is OK.  @horsburgh if you are happy with this you can close.  I've written a new issue #258 for migration of old resources to be consistent with this, and a new issue #259 to make URL's work.


Run terraform fmt as githook and GH Action

This PR brings some sanity to our Terraform formatting by using terraform fmt.
Changes

Adds a pre-commit githook that validates all Terraform files are formatted per terraform fmt specs before committing

The pre-commit githook provides details for fixing the files, including running the hook with the --fix option

Runs a verification of Terraform formatting as part of GitHub Action as an added failsafe
Formats all existing Terraform files

This will make for some merge conflicts, but it's a necessary evil

Updates our .editorconfig to help the IDE make the same formatting choice at terraform fmt

Checklist
Testing

[x] Tested locally?
[ ] Ran quickTest all?
[ ] Ran ./prime test against local Docker ReportStream container?
[ ] Downloaded a file from http://localhost:7071/api/download?
[ ] Added tests?

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[x] Includes a summary of what a code reviewer should verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Fixes
List GitHub issues this PR fixes

#issue

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

@td-usds Ready for review again. I took your suggestions, cleaned up the auto-formatting, and added a .editorconfig adjustment to help IDEs match the formatting.


update security-analytics roles to add correlation engine apis

Description
update security-analytics roles to add correlation engine apis

Category (Enhancement)
Why these changes are required?
What is the old behavior before changes and new behavior after changes?

Issues Resolved
[List any issues this PR will resolve]
Is this a backport? If so, please add backport PR # and/or commits #
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2732 (ccdd782) into main (a5489a2) will decrease coverage by 0.04%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main    #2732      +/-   ##
============================================
- Coverage     61.51%   61.47%   -0.04%
+ Complexity     3396     3392       -4
============================================
  Files           272      272
  Lines         18740    18740
  Branches       3284     3284
============================================
- Hits          11528    11521       -7
- Misses         5613     5616       +3
- Partials       1599     1603       +4

see 2 files with indirect coverage changes

Please make the changes to the roles in alphabetical order so its easier for a administrator to read

hi @peternied , made changes as per your suggestions.


Changes under "Covid Section" page

Expected Behaviour: Put these section "dos" & don't in separate boxes and add CSS to the boxes.

For Reference: https://skpandey885.github.io/HealhUb/pages/covidSection.html

I want to work on this issue under JWOC.


[RELEASE-1.10][Flink-16662] [table-blink/clients]Fix the bug that the blink Planner failed to generate JobGraph when use the udf in checkpointing mode.

What is the purpose of the change
This pull request is to fix the bug that the blink Planner failed to generate JobGraph when use the udf in checkpointing mode.
Brief change log

Use the user classloader in PackagedProgramUtils as the thread context classloader before FlinkPipelineTranslationUtil#getJobGraph method

Verifying this change

Crate TableEnvironment use blink planner
UDFs being shipped.
Checkpointing enabled.
Created table through a sql query that references a UDF.
The table is converted to a retract stream.

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

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

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Merged


Manual Arrow draw feature (output only, maintain predefined structure, ugly arrows)

manualArrowPad option for enabling the manual arrow pad and connections feature.
This allows:

joining two steps into single output
looping by going back to previous step
jumping to step in completely different part of workflow if you want

Dragscroll options now an array of choices for mouse button: ('LEFT' | 'MIDDLE' | 'RIGHT')[]

resolves #37

resolves #44

resolves #47

resolves #58


Singlefield baseadapter

Coverage decreased (-11.7%) to 34.872% when pulling a4dc5fe164d833e0f151be0c6c871eb3aff67e79 on rfecher:singlefield-baseadapter into ec1e143abc65fb3d0db6f7c3745628ca27e1776c on locationtech:master.

Coverage decreased (-11.7%) to 34.872% when pulling a4dc5fe164d833e0f151be0c6c871eb3aff67e79 on rfecher:singlefield-baseadapter into ec1e143abc65fb3d0db6f7c3745628ca27e1776c on locationtech:master.


OpenShift compatibility

I think our images have previously aimed at v3 OpenShift compatibility but may not be v4 compatible. In particular we set USER 1000 but may rely on hardcoded /home/x. For some of our tools we rely on them finding config in their home directory.
I found a discussion prior to v4 which gives some hope that we might still be able to put them in /home/x and it works despite random UIDs: https://github.com/openshift/origin/issues/23369#issuecomment-511387505
If as that comment indicates we can set HOME=/home/x and ensure it's writable by group 0 then it could be enough for tools to find their "home directory config" regardless of what UID they run as.
Another question remains though: is it forbidden to set USER 1000 in our images for OpenShift compatibility as seemed to be recommended in OpenShift v3, or we just need to be aware of its limitations.

https://www.openshift.com/blog/a-guide-to-openshift-and-uids

Problematic tools

nix #799
poetry renovatebot/github-action#736


Removed unused use statements

grep result revealed those unused uses while searching on this lib.
So I've corrected it using http://cs.sensiolabs.org/ tool.
Even though it isn't really important, less is better I think. :)

Thanks!


[Fabric] - iOS - Profile - The Profile section is not clickable

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
Go to Settings -> Profile

Expected Result:
The "Profile" section should be clickable
Actual Result:
The Profile section is not clickable.
Workaround:
Unknown
Platforms:

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

[ ] Android / native
[ ] Android / Chrome
[x] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: NO
Reproducible in production?:
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
https://user-images.githubusercontent.com/93399543/229125088-bad8c33d-6e0b-4c7a-b2c0-9bfb28a1e4ac.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Hi! I'll be working on this issue.

Hi! I'll be working on this issue.

It seems to be working as expected when building the app from the current (https://github.com/WoLewicki/App/commit/e12c1cfd8a9a9eef4bab9471c1c2a0547a4504f5) andrew-fabric branch:
https://github.com/Expensify/App/assets/21055725/eafc4e8d-99f2-41ea-8869-d40230a9e7a6


Ansible Operator runs continually

Bug Report
What did you do?
Created a simple operator to declare objects under config management. Source: https://github.com/aweiteka/opsconfig-operator
I annotated the custom resource ansible.operator-sdk/reconcile-period: "30s"
What did you expect to see?
I expected the operator to watch the custom resource and run playbook if the cr changes. Otherwise I expected the playbook to wait until next reconcile-period (30s)
What did you see instead? Under which circumstances?
The playbook runs constantly. Unclear what this error is: did not receive playbook_on_stats event (full output below)
Environment

operator-sdk version: v0.1.0+git

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.0", GitCommit:"fff5156092b56e6bd60fff75aad4dc9de6b6ef37", GitTreeState:"clean", BuildDate:"2017-03-28T16:36:33Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2018-11-09T01:25:16Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind: minishift

Are you writing your operator in ansible or go? Ansible

Additional context
OUTPUT
$  operator-sdk up local --namespace opsconfig
INFO[0000] Go Version: go1.9.7
INFO[0000] Go OS/Arch: linux/amd64
INFO[0000] operator-sdk Version: v0.1.0+git
INFO[0000] watching namespace: opsconfig
INFO[0000] Starting to serve on <IP_ADDRESS>:8888
INFO[0000] Watching ops.openshift.com/v1alpha1, Opsconfig
INFO[0004] ansible-runner exited successfully            component=runner job=4544230080896754932 name=post-install namespace=opsconfig
ERRO[0004] did not receive playbook_on_stats event
INFO[0008] ansible-runner exited successfully            component=runner job=5677574673867650771 name=post-install namespace=opsconfig
ERRO[0008] did not receive playbook_on_stats event
INFO[0013] ansible-runner exited successfully            component=runner job=1646352905985815204 name=post-install namespace=opsconfig
ERRO[0013] did not receive playbook_on_stats event
INFO[0018] ansible-runner exited successfully            component=runner job=6349805690248942967 name=post-install namespace=opsconfig
ERRO[0018] did not receive playbook_on_stats event

I think something in your ansible code is failing. If you build from the latest master, you should see more info in the log.

@aweiteka Did you manage to add more logs or resolve the problem?

I haven't been able to resolve it due to some environment issues but let's close this now and I'll open a new issue with more detail if there's still an issue. Thanks.


test.py error - ValueError: not enough values to unpack (expected 3, got 2)

Hi, I would appriciate your help.
I tried to run the test.py file but i get the following error:
__,contours,_ = cv2.findContours(search_hand_mask, cv2.RETR_TREE, cv2.CHAIN_APPROX_SIMPLE)
 ValueError: not enough values to unpack (expected 3, got 2)_

After i tried to change the 'Contours' (see below changes) i received the following error:
  _File "/home/pi/Downloads/SmartMirror-master/Motion/gesture.py", line 44, in CheckForPalm
  for i in range(self.defects.shape[1]):
  AttributeError: 'NoneType' object has no attribute 'shape'_

Changes 'Contours':
    def InitFromMask(self, search_hand_mask):
    # Check each contours
    contours, _= cv2.findContours(search_hand_mask, cv2.RETR_TREE, cv2.CHAIN_APPROX_SIMPLE)

    for contour in contours:
        if self.InitFromContour(contour):
            return True
    return False

def InitFromMaskAndPosition(self, search_hand_mask, nearestFromX, nearestfromY):
    # Check each contours
    contours, _= cv2.findContours(search_hand_mask, cv2.RETR_TREE, cv2.CHAIN_APPROX_SIMPLE)
    distanceContours = []`

Hello there,
It seems that your OpenCV version is not the same than the one I used, and not returning the correct amount of values for the function. Which version are you using ?
Also this project of mine is becoming pretty old, there are now better community oriented project like this one on Github, if you didn't give them a try yet.

Hi,
I am proud to say that i  already found the fix :)
It was really because that my version is newer then what you developed.
What i did in my case was as follow:
Before:
 `def InitFromMask(self, search_hand_mask):
    # Check each contours
    (_, contours, _) = cv2.findContours(search_hand_mask, cv2.RETR_TREE, cv2.CHAIN_APPROX_SIMPLE)

    for contour in contours:
        if self.InitFromContour(contour):
            return True
    return False

def InitFromMaskAndPosition(self, search_hand_mask, nearestFromX, nearestfromY):
    # Check each contours
    (_, contours, _) = cv2.findContours(search_hand_mask, cv2.RETR_TREE, cv2.CHAIN_APPROX_SIMPLE)
    distanceContours = []`

Now:
 `def InitFromMask(self, search_hand_mask):
  # Check each contours
    contours = cv2.findContours(search_hand_mask.copy(), cv2.RETR_TREE,
    cv2.CHAIN_APPROX_SIMPLE)[0]

    for contour in contours:
        if self.InitFromContour(contour):
            return True
    return False

def InitFromMaskAndPosition(self, search_hand_mask, nearestFromX, nearestfromY):
    # Check each contours
    contours= cv2.findContours(search_hand_mask.copy(), cv2.RETR_TREE, cv2.CHAIN_APPROX_SIMPLE)[0]
    distanceContours = []`

Now i am stuck on tweaking HSV values so it will see my hand mask and that gesture will be recognize.
Still couldn't make it work.

Make sure you run the debug version so that you can see what the camera capture and how the HSV values min/max takes from that capture, finally just tweak the value so all you get is your hands.

I tried but i can't get all gestures to be recognized :( it's taking long time.

Do you have any assumptions on why the debug work very very slowly (in your demo it working smooth and fast). ?

I was using my PC and not the raspberry for the demo. Also make sure that your first gesture is a palm so that it can know where your hand is for your next gestures


Update description lines 39-40

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Hello there,
Thank you for opening this PR. We recommend reviewing the contribution guidelines. In general, issues labelled help wanted or first timers only are open for contributions.
The issue related to this PR has not been discussed or triaged yet.

Hello there,
Thank you for opening this PR. We recommend reviewing the contribution guidelines. In general, issues labelled help wanted or first timers only are open for contributions.
The issue related to this PR has not been discussed or triaged yet.

@atopp25, Thank you for your pull request. As discussed in the issue, it makes sense to keep the wording as is for the time being.
I am closing this pull-request accordingly.

@atopp25, Thank you for your pull request. As discussed in the issue, it makes sense to keep the wording as is for the time being.
I am closing this pull-request accordingly.


OSS Supply Chain Working Group - DevOps Automation - June 6, 2023

June 6, 2023
Thursday 06 Jun 2023 - 09:00 EST / 14:00 UK
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene, roll call, welcome new people
[ ] Approve previous meeting minutes
[ ] Review DevOps SIG project board
[ ] Add Items Here
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom info
Join Zoom Meeting

https://zoom.us/j/95521041942?pwd=dHgwREU2TzBsS242ak1zYWZsUW9OUT09
Meeting ID: 955 2104 1942
Passcode: 443820
Find your local number: https://zoom.us/u/aesEqmNODb

Github Repo: https://github.com/finos/devops-automation/
Project Board: https://github.com/orgs/finos/projects/33
Working Group Board: https://github.com/orgs/finos/projects/65
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

hi - Bruno from Morgan Stanley


Triplet-Triplet components of SOC matrix

Is it possible to calculate not only Singlet-Triplet components of the SOC matrix but also the Triplet-Triplet components/the full matrix?

Is it possible to calculate not only Singlet-Triplet components of the SOC matrix but also the Triplet-Triplet components/the full matrix?

Which kind of coupling between two Triplets? direct coupling?

Essentially, what I am asking is if it is possible to calculate the elements just the elements of the form
<T|H_{SO}|T> in addition to the default <S|H_{SO}|T> ones.
(like e.g. in Q-Chem: http://www.q-chem.com/qchem-website/manual/qchem50_manual/sect-tddft.html equations 6.26 and 6.27)

Essentially, what I am asking is if it is possible to calculate the elements just the elements of the form
<T|H_{SO}|T> in addition to the default <S|H_{SO}|T> ones.
(like e.g. in Q-Chem: http://www.q-chem.com/qchem-website/manual/qchem50_manual/sect-tddft.html equations 6.26 and 6.27)

Thank you. Now I see. <T|H_{SO}|T> can be calculated in the current scheme, but one needs to modify the original code to output relevant elements, especially soc_state.f90.
I would like to help you, but I am really busy working on other stuff...


Add readiness & liveness status check handlers

This PR adds readiness and liveness status check handlers to the agent, which help ensure the health of the application in
Kubernetes.
Changes Made:

Added /readiness endpoint to check if the service is ready.
Added /liveness endpoint to check if the service is running.
Kept the existing root endpoint handler. (not sure if this is OK)

It should work in Kubernetes like,
        readinessProbe:
          httpGet:
            path: /readiness
            port: 8080
          initialDelaySeconds: 5
          periodSeconds: 10
        livenessProbe:
          httpGet:
            path: /liveness
            port: 8080
          initialDelaySeconds: 5
          periodSeconds: 10

Sadly I cannot test this because it needs some Google Cloud auth:
2024-07-29T23:01:12.775+0300    FATAL   cmd/main.go:92  failed to create firestore client       {"error": "google: could not find default credentials. See https://cloud.google.com/docs/authentication/external/set-up-adc for more information"}

I believe CI fails because it's a fork of the repository?

Thanks for the PR! The ticket could've been more specific but the additional endpoints aren't actually necessary. We also don't use Kubernetes to deploy, really we only need some configuration set up in the GCP console. That being said, since the agent code hasn't changed much in the last few years, the utility of doing so it not very high.
I appreciate the help though, if you're interested we'd be more than happy to work in any frontend improvements you can think of.


New package: GPUPolynomials v1.0.0-DEV

Registering package: GPUPolynomials
Repository: https://github.com/alexp616/GPUPolynomials.jl
Created by: @alexp616
Version: v1.0.0-DEV
Commit: f936aee3f88d0706c75297217504d306a28bc9b1
Git reference: main

Closing in favor of https://github.com/JuliaRegistries/General/pull/115811


clean code: update syllabus index page

update syllabus index page so it doesn't just have DS specific stuff: Rather link to topics/clean-code and then allow that page to link to other specific things

Also make sure that the "clean-code" holding topic is set up so that it can point to various sub-topics


Support Postgres jsonb columns

Hi I'm interested in parsing jsonb columns from postgres. currently I do the following:
type MyData struct {
    Model
    JsonData    string `gorm:"type:jsonb;not null"`
}

But serializing the struct again would lead to an escaped json string in the JsonData field. I would prefer something like this:
type MyData struct {
    Model
    JsonData    interface{} `gorm:"type:jsonb;not null"`
}

Where the data gets automatically parsed on query.
I'm not familiar with the callbacks. Is there a way I could add the type conversion my self? Any hint's would be helpful.

Would it be more suitable for MyData.JsonData to be of type json.RawMessage? I think you'd have to implement the sql.Scanner interface but I think it'd be worth it.

yes json.RawMessage might be the right way. When I implement sqlScanner on a custom type that embeds json.RawMessage it just works? I will try it.

@Niondir Hmm good point... Is it possible to do:
func (json *json.RawMessage) Value() (driver.Value, error) {
 //code
}

This seems to work <3
type PostgresJson struct {
	json.RawMessage
}

func (j PostgresJson) Value() (driver.Value, error) {
	return j.MarshalJSON()
}

func (j *PostgresJson) Scan(src interface{}) error {
	if bytes, ok := src.([]byte); ok {
		return json.Unmarshal(bytes, j)

	}
	return errors.New(fmt.Sprint("Failed to unmarshal JSON from DB", src))
}

Maybe add this to the pg driver?

@Niondir Yes, it`s cool feature.

@jinzhu  would you accept a PR for @Niondir 's method? If so I can prep it.

@MaerF0x0 yes, would accept it if put it into there. https://github.com/jinzhu/gorm/blob/master/dialects/postgres/postgres.go

Hello 👋
Now that this has been merged, is there any way you could show me an example on how to use this ? 👍
Thanks a lot

Not sure if you still need this given that it's been a few months, @Depado , but for all the other folks who are curious:
Assuming you have a "documents" table, and in that documents you have a "metadata" jsonb column, your resulting model struct definition may look something like this:
package yourPackageName

import (
	"time"
	"github.com/jinzhu/gorm/dialects/postgres"
)

type Document struct {
	Metadata postgres.Jsonb		`json:"requirements"`
	Body string				        `json:"body"`

	//housekeeping attributes
	ID        int					        `json:"id"`
	CreatedAt time.Time			`json:"created_at"`
	UpdatedAt time.Time			`json:"updated_at"`
}

Assuming you wanted to access the value of "Metadata" in a specific "Document" as a string ...
func GetMetadataOfDocument(dbConn *gorm.DB, documentId int) string {
    doc := Document{}
    dbConn.Where("id = ?", documentId).First(&doc)

    stringVal := string(doc.Metadata.RawMessage)
    return stringVal;
}

@Aetheus thanks a lot !
I managed to get it to work on my own but that's a great example for the documentation 👍

@Aetheus thanks for the code snippet. I've pulled gorm from master and when I run your example code I end up with a metadata field that's typed to a byteA instead of jsonB.
I'm running the following:

PostgreSQL v9.6.6 in a Docker container - (postgres:9.6-alpine)
Go v1.9.3
latest from gorm (master)

sampleDoc := Document{}
sampleDoc.Body = "buildscientist"

dbHandle.CreateTable(Document{})
dbHandle.Create(&sampleDoc)

doc := Document{}
dbHandle.Where("id = ?", 1).First(&doc)
stringVal := string(doc.Metadata.RawMessage) //this is set to null

Stepping through gorm scope.createTable() executes a raw SQL statement of the following:
CREATE TABLE "documents" ("metadata" bytea,"body" text,"id" serial,"created_at" timestamp with time zone,"updated_at" timestamp with time zone , PRIMARY KEY ("id"))

@Aetheus
I think I figured out what the issue is - have a look at:
Line 68 of dialect_postgres.DateTypeOf()
Looks like jsonB isn't a case in that switch statement so it's automatically defaulting to byteA.

@buildscientist - actually, I think that your original suggestion was a good one. In fact, dialect_postgres.go already has a check in the DataTypeOf method for the "Hstore" type (which is also defined in dialects/postgres.go), so there is precedence for expecting the provided "loader" structs to actually be able to be used for other purposes.
Thanks for bringing it up! I haven't been using gorm for database migrations, so the thought of how the "loader" types would interact with it never crossed my mind.  I'm not sure if I should open another issue for it, but I'll do a PR regardless and see where it goes from there.

I still think the original suggestion is a very good one.
I would prefer that gorm automatically marshal/unmarshal struct field tagged as type:jsonb.
I am ready to dig into this if it is possible from design/architecture point.

+1 for this feature but this would be specific to PgSQL right? Unless you maintain a map of other DB vendors JSONB (or JSON) types.

I still think the original suggestion is a very good one.
I would prefer that gorm automatically marshal/unmarshal struct field tagged as type:jsonb.
I am ready to dig into this if it is possible from design/architecture point.

Any updates on this?

+1 for the original suggestion.
I like the idea of leaving the model as agnostic as possible to the underlying db impl.
It'd be nice if we could model all db specificities as tags that gorm could interpret, but leave field types as being as db-agnostic as possible, just so business layers wouldn't need to be aware of any db details when manipulating the model.


Added default value to securityConfigSecret to fix issue #702

Signed-off-by: David Calvert<EMAIL_ADDRESS>Issue #, if available: https://github.com/opendistro-for-elasticsearch/opendistro-build/issues/702
Description of changes: Added a default value to securityConfigSecret to make this feature work straight away. I didn't find any instructions on bumping the chart version so I left it unchanged. Let me know if you want me to bump it in this PR.
Test Results:
Note: If this PR is related to Helm, please also update the README for related documentation changes. Thanks.
https://github.com/opendistro-for-elasticsearch/opendistro-build/blob/master/helm/README.md
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on signing off your commits, please check here.

Hi @dotdc dotdc
Can you please provide some test results, which will be helpful in the review.
Thanks for your contribution
Thanks
Sreekar

Hi @sreekarjami,
What kind of tests do you need?
If the value internalUsersSecret isn't set, the changes made to files under elasticsearch.securityConfig.config.data will not work.
When you look at the the current values.yaml file, is it not obvious that this must be set, and several people like me had trouble to figure this out. This PR will just add a default value to make it work by default for all users.
Let me know if you need more information.
Regards,
David

Hi @dotdc  we have moved to OpenSearch (opensearch.org)
And we just merged the 1st version of Helm there opensearch-project/opensearch-devops#4
Could you close this PR and migrate there? Thanks.

Hi @peterzhuamazon, sorry I missed this one, it's done : https://github.com/opensearch-project/helm-charts/pull/142


Update mbedtls to 3.6.2

Mbed TLS 3.6.2 is the latest release in the long-term support 3.6.x series. It brings in some critical security fixes and is the recommended release of Mbed TLS from that community.
One of the fixes updates the certifi version referenced by Mbed TLS to one that fixes this CVE:
https://nvd.nist.gov/vuln/detail/CVE-2023-37920. CVE scanning tools pick up the version of certifi in Mbed TLS 3.6.0 and report libspdm in violation, even though it is not as libspdm does not use these mbedtls pip modules, as they are used only to build mbedtls's ReadTheDocs site.

Not sure why the builds are failing. 3.6.2 should still have the mbedcrypto target. They only recently changed mbedcrypto to tfpsacrypto.

Not sure why the builds are failing. 3.6.2 should still have the mbedcrypto target. They only recently changed mbedcrypto to tfpsacrypto.

Yeah, I'm looking into it now. It may be part of the deprecation of the mbedtls_sha3_* functions: https://github.com/Mbed-TLS/mbedtls/blob/v3.6.2/docs/psa-transition.md#summary-of-api-modules. If it does involve changing apisets, I will file an issue for this, as that is beyond the scope of what I am able to contribute here. I'm hoping the old apiset can continue to be used. Regardless, it does look like this is a change that libspdm will have to consume by MbedTLS 4.0.

@steven-bellock , it was just added the SHA3 define to config, but it is strange that it wasn't needed before, because v3.6.0 had the same define: https://github.com/Mbed-TLS/mbedtls/blob/v3.6.0/library/sha3.c#L15

@psrisoontorn you confirmed that SHA3 "really" works with your pull requests, correct?

@psrisoontorn you confirmed that SHA3 "really" works with your pull requests, correct?

Yes, I've tested SHA3 with mbedtls. I think the reason why I didn't see any issue is because 'MBEDTLS_SHA3_C' is already defined in "config_adjust_legacy_from_psa.h". There is a comment in the code indicating that the corresponding MBEDTLS_XXX settings would be enabled automatically if PSA_WANT_XXX symbols are defined.
Note: PSA_WANT_ALG_SHA3_XXX symbols are defined in crypto_config.h.

Anyway, I think adding the define for 'MBEDTLS_SHA3_C' to config.h is the right thing to do.


Adopt nested discriminator cadl ranch spec

Fixes https://github.com/microsoft/typespec/issues/4003

API change check
API changes are not detected in this pull request.


Show the search paths in case of an import error

The import errors were hard to debug due to the lack of information about directories being searched.
I filled the search_path in order for it to be displayed when an import error occurs.
To test, uncomment the test test_no_extension (it is failing because of an import), run the tests and check the error message.

Sorry @PhilipGarnero I merged your other pull request before this one. Now this one doesn't work any more. Do you mind rebasing that onto master?
Thanks.

I was expecting it ;)


update - samp_type [MIXS:0000998]

Current term details
Term name - sample type
Term ID - MIXS:0000998
Structured comment name - samp_type
Definition - Type of material (i.e. sample) collected. Includes types like core, rock trimmings, drill cuttings, piping section, coupon, pigging debris, solid deposit, produced fluid, produced water, injected water, swabs, etc. If "other" is specified, please propose entry in "additional info" field
Expected value - enumeration
Value syntax - [core|rock trimmings|drill cuttings|piping section|coupon|pigging debris|solid deposit|produced fluid|produced water|injected water|water from treatment plant|fresh water|sea water|drilling fluid|procedural blank|positive control|negative control|other]
Example - solid deposit
Preferred unit -
Package(s) - hydrocarbon resources-cores, hydrocarbon resources-fluids/swabs, food-food production facility, food-farm environment

Suggested update(s)
Definition - The type of material from which the sample was obtained. Samples are usually categorized as food, body products or tissues, or environmental material. This field accepts terms listed under environmental specimen (http://purl.obolibrary.org/obo/GENEPIO_0001246).
Expected value - GENEPIO:0001246
Value syntax - {termLabel} {[termID]}
Example - built environment sample [GENEPIO:0001248]

Additional context
Updates suggested during review of Food packages.
I'm not convinced that the changes suggested would work for all use cases, as the suggested "environmental specimen" ontology only contains a small number of terms and appears to overlap with the ENVO terms collected elsewhere.

Agreed, these represent the same entity.

@lschriml , the question here is; is the new suggested definition of samp_type better or worse than the current definition? i.e. do we update samp_type definition or not.

Leave value syntax as is. Change the example. Change definition to make it less specific.
The type of material from which the sample was obtained. For the Hydrocarbon package, samples include types like core, rock trimmings, drill cuttings, piping section, coupon, pigging debris, solid deposit, produced fluid, produced water, injected water, swabs, etc. For the Food Package, samples are usually categorized as food, body products or tissues, or environmental material. This field accepts terms listed under environmental specimen (http://purl.obolibrary.org/obo/GENEPIO_0001246).
Note that TDWG has a task group to define minimum metadata for a material. We should coordinate with them.
In NCBI, sample_type is defined as e.g. cell culture, tissue culture,...  Value from this term can be derived directly from BioProject. We need to figure out where this is coming from for sure.
TODO: Update this per above for MIxS 6, but open a new ticket to resolve general issues around this term for MIxS 7.

This change was approved by Chris from the food package.

all instances in v6 spreadsheet updated to suggestions at the start of this ticket, and added to the change log.


why would you add a disabled block?

https://github.com/ItinerisLtd/acf-gutenblocks/blob/b33e2dcb292ca15ab23620bd50fe323308920830/src/Block.php#L120
in other words, why not remove it?

I expect there would be scenarios where you would conditionally enable it.
Don't see us making use of it, but maybe someone will.


Format of config.json

What is the format of the file config.json, which is accepted by the command line argument --registry-config? I did not find any specification in the documentation.
My goal is to specify registry URL, username, password in this config file.
Output of helm version:
version.BuildInfo{Version:"v3.9.1", GitCommit:"a7c043acb5ff905c261cfdc923a35776ba5e66e4", GitTreeState:"clean", GoVersion:"go1.17.5"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.0", GitCommit:"b46a3f887ca979b1a5d14fd39cb1af43e7e5d12d", GitTreeState:"clean", BuildDate:"2022-12-08T19:51:43Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.10", GitCommit:"eae22ba6238096f5dec1ceb62766e97783f0ba2f", GitTreeState:"clean", BuildDate:"2022-05-24T12:50:52Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): On premise

It's a docker ConfigFile that is used for storing auths to registries and other docker configuration. If you've logged in to docker hub, look at ~/.docker/config.json for the most common use case.

Thanks. Maybe makes sense add a reference in Helm documentation


Allow customizing the location (and name) of the "env" directory

Is your feature request related to a problem? Please describe.
In some cases, it's desirable to not have the "env" directory (containing .properties files for various environments) at the project root, particularly in monorepos. "env" is also quite generic and could lead to conflicts/confusion in a team.
Describe the solution you'd like
The location of the "env" directory could be configured as a CLI flag to gauge run e.g. gauge run --env-dir foo/bar/baz --env ci or as an environment variable e.g. GAUGE_ENV_DIRECTORY=foo/bar/baz gauge run. The choice between "dir" vs "directory" is up to your discretion or the current standards. The value itself could follow the same conventions as other path-like settings i.e. either as an absolute path or as a path relative to the project root.
Describe alternatives you've considered

Allow loading default env directory from .gauge/env (in the project root).

Additional context
The same feature would be nice for manifest.json i.e. either allow customizing its location or also support loading it from .gauge inside the project.

Thank you for the suggestion.
Of the options you propose, I personally favour the environment variable approach, for two reasons:

it is consistent with how gauge allows configuration of specs/implementations/logs etc.
the --env flag is already in use and adding another flag to specify the env dir makes it a bit verbose.


Remove docker restart always

Remove restart: always from docker-compose.yml ? It made the project "up" automatically every time docker start and it's a bit anoying as it takes a port used by other project.

:+1: thanks


refactor(lib1): Split video generation and remove queue

Closes #60
This merge request changes the functionality and flow of lib1.
The image processing is now split into three parts. In the init function the framerecorder is set up. When calling the loadFrame function the image is added via the framerecorder. When calling the save function the framerecorder is stopped and the final video is saved.

instead of forcing the user to save you can try finalize() see link

I added a finalize method so the user of the library can use the save inside of their android app or the library falls back to finalize if the user forgets to use save.

I think this is now finally ready for review and then merging. @fs3itz


rename with rly-network organization name

Required prep step before publishing to npm

We should communicate in the CG slack channel about this breaking change. That way Luis knows to update imports if/when he updates.


Update zio-logging to 2.1.15

About this PR
📦 Updates dev.zio:zio-logging from 2.1.13 to 2.1.15
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio", artifactId = "zio-logging" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio", artifactId = "zio-logging" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #552.


autograd.scipy.stats.multivariate_normal.logpdf does not work within a function.

I seem to be unable to get multivariate_normal.logpdf to work with autograd when wrapped in another function.  Below are steps to reproduce.
If this is not a bug, I would like to know what I'm doing wrong.
import autograd
import autograd.numpy as np
import autograd.scipy as sp
from autograd.test_util import check_grads

num_obs = 1000

# Some valid values
true_sigma = \
    np.eye(3) * np.diag(np.array([1, 2, 3])) + \
    np.random.random((3, 3)) * 0.1
true_sigma = 0.5 * (true_sigma + true_sigma.T)

true_mu = np.array([0, 1, 2])

x = np.random.multivariate_normal(
    mean=true_mu, cov=true_sigma, size=(num_obs, ))

# Succeeds
print('Differentiation succeeds')
check_grads(autograd.scipy.stats.multivariate_normal.logpdf, modes=['rev'])(x, true_mu, true_sigma)

# Fails
try:
    def logpdf_mu(mu):
        return np.sum(autograd.scipy.stats.multivariate_normal.logpdf(x, mu, true_sigma))
    print('Can evaluate the function: ', logpdf_mu(true_mu))
    check_grads(logpdf_mu, modes=['rev'])(true_mu)
except AssertionError as err:
    print('Differentiation fails:\ntest_util.py 31:\tassert vspace(vjp_y) == x_vs')

try:
    def logpdf_mu(mu):
        return np.sum(autograd.scipy.stats.multivariate_normal.logpdf(x, mean=mu, cov=true_sigma))
    print('Can evaluate the function: ', logpdf_mu(true_mu))
    check_grads(logpdf_mu, modes=['rev'])(true_mu)
except TypeError as err:
    print('Differentiation fails: ' + str(err))

Output:
Succeeds
Can evaluate the function:  -5165.838149252399
Differentiation fails:
test_util.py 31:	assert vspace(vjp_y) == x_vs
Can evaluate the function:  -5165.838149252399
Differentiation fails: Can't differentiate w.r.t. type <class 'numpy.int64'>

Hey there! Sorry, I guess our error messages might be a bit opaque here. The error Can't differentiate w.r.t. type <class 'numpy.int64'> is raised whenever you try to differentiate w.r.t. an argument that is not a numpy float dtype (which breaks Autograd). Here you're differentiating w.r.t. true_mu, which you instantiate as an array of integers (dtype int64). You can fix this by changing
true_mu = np.array([0, 1, 2])

to
true_mu = np.array([0., 1., 2.])

That makes the first version of your function work, i.e. this one
try:
    def logpdf_mu(mu):
        return np.sum(autograd.scipy.stats.multivariate_normal.logpdf(x, mu, true_sigma))
    print('Can evaluate the function: ', logpdf_mu(true_mu))
    check_grads(logpdf_mu, modes=['rev'])(true_mu)
except AssertionError as err:
    print('Differentiation fails:\ntest_util.py 31:\tassert vspace(vjp_y) == x_vs')

The second still doesn't work, because unfortunately we don't support differentiating numpy and scipy primitives (like multivariate_normal.logpdf) through keyword arguments. That limitation probably ought to be documented in the tutorial.

Ok, that fixes that problem!  This actually failed in a more complicated context, and still fails even with this fix.  Let me try to work up to the more complicated context step by step.
The following code also fails, using the same setup as the previous example.  (It will also fail without the symmetriziation, but I just put that in to remove that potential cause from consideration and to match up with the autograd unit tests.  Note that, as seen above, the ordinary autograd.scipy.stats.multivariate_normal.logpdf function passes checks without symmetrization.)
def sym_logpdf(sigma):
    sigma_sym = 0.5 * (sigma + sigma.T)
    return np.sum(
        autograd.scipy.stats.multivariate_normal.logpdf(
            x, true_mu, sigma_sym))

# Fails
try:
    check_grads(sym_logpdf, modes=['rev'])(true_sigma)
except AssertionError as err:
    print('Differentiation fails: {}'.format(err))

The failure error is
Differentiation fails: Derivative (VJP) check of sym_logpdf failed with arg [[1.00118248 0.06698002 0.05511756]
 [0.06698002 2.02959295 0.0582546 ]
 [0.05511756 0.0582546  3.07846635]]:
analytic: -6.174144913879758
numeric:  6.174144955055192

Can you try running against the master branch from the Github repo (if you aren't already doing so)? I think the above might have been fixed by https://github.com/HIPS/autograd/pull/412.