YAML lint config (.yamllint) is overwritten after molecule init

Issue Type

Bug report

Molecule and Ansible details
ansible 2.7.5
  config file = ~/dev/ansible/ansible-control/ansible.cfg
  configured module search path = ['~/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = ~/dev/ansible/ansible-control/.venv/lib/python3.7/site-packages/ansible
  executable location = ~/dev/ansible/ansible-control/.venv/bin/ansible
  python version = 3.7.1 (default, Nov  6 2018, 18:49:54) [Clang 9.0.0 (clang-9<IP_ADDRESS>)]
molecule, version 2.19.0

Molecule installation method: pip
Ansible installation method (one of): OS package (Homebrew)
Desired Behaviour
My .yamllint should remain intact, and not be overwritten :-)
Actual Behaviour

Create or make changes to .yamllint, e.g.

extends: default

rules:
  braces:
    max-spaces-inside: 1
    level: error
  brackets:
    max-spaces-inside: 1
    level: error
  line-length: disable
  indentation:
    spaces: 2
    indent-sequences: consistent

Run molecule init scenario --role-name <role-name> --scenario-name <run-this>
Open .yamllint in fav editor, and it's back to the default from molecule:

extends: default

rules:
  braces:
    max-spaces-inside: 1
    level: error
  brackets:
    max-spaces-inside: 1
    level: error
  line-length: disable
  # NOTE(retr0h): Templates no longer fail this lint rule.
  #               Uncomment if running old Molecule templates.
  # truthy: disable

Thanks!

I'd be happy to take a stab at changing said logic.  From a cursory look, it appears that the code is calling Cookiecutter to template out the folders/files, and as far as I can tell, it's doing it in a non-granular way, i.e. just writing out all of the relevant files in the molecule/cookiecutter directory:
https://github.com/ansible/molecule/blob/cb53404db7b4920d05c311a6d5af43ec4dfd02fa/molecule/command/init/base.py#L56-L62
I can dig more into the code and Cookiecutter but was hoping someone here (@decentral1se @samdoran) could toss me a few pointers as to the direction to take.  Thanks, I'd be much obliged :-)

Thanks for the offer @rockpenguin! It would be great to have this fixed and will happily review a PR. As far as pointers go, I think you're on track and I haven't touched that code much yet. We basically want to stop any overwriting happening. Unsure if we can functionally test this (see https://github.com/ansible/molecule/tree/master/test/scenarios, maybe we can) but I will also be happy to manually test for now.
I've also just re-reviewed https://github.com/ansible/molecule/pull/1659 and it looks good to go!

Awesome!  I'll try changing overwrite_if_exists first and do some manual testing from there to see what breaks :-)

:rocket:

AFAIK this no longer happens.

It would appear this problem still exists and molecule completely overwrites .yamllint instead of appending or modifying.  I just installed molecule on a new machine and had this behavior.
➜   molecule --version
molecule 3.0.4
   ansible==2.9.9 python==3.7

➜ molecule init scenario -r ansible-influx

➜  git diff
diff --git a/.yamllint b/.yamllint
index bb3d6e5..8827676 100644
--- a/.yamllint
+++ b/.yamllint
@@ -1,12 +1,33 @@
 ---
+# Based on ansible-lint config
 extends: default

 rules:
-  truthy:
-    allowed-values:
-      - 'true'
-      - 'false'
-      - 'yes'
-      - 'no'
-  line-length:
-    max: 160
+  braces:
+    max-spaces-inside: 1
+    level: error
+  brackets:
+    max-spaces-inside: 1
+    level: error
+  colons:
+    max-spaces-after: -1
+    level: error
+  commas:
+    max-spaces-after: -1
+    level: error
+  comments: disable
+  comments-indentation: disable
+  document-start: disable
+  empty-lines:
+    max: 3
+    level: error
+  hyphens:
+    level: error
+  indentation: disable
+  key-duplicates: enable
+  line-length: disable
+  new-line-at-end-of-file: disable
+  new-lines:
+    type: unix
+  trailing-spaces: disable
+  truthy: disable```

A patch to address that is more than welcomed, even if I am not sure which is the desired behavior. Appending does not make sense and is not possible. Still, I see other valid options: fail to run, raise warning that the file is present, prompt to override or ignore.


Docs: Add section on how to contribute tests to the overall project

What were you searching in the docs?
I was trying to find a section on how to setup a local test harness so I could write some tests
Is this related to an existing documentation section?
No response
How can we improve?
There needs to be a contributing/testing section in the docs to help people get up to speed faster with writing tests for the project.
Got a suggestion in mind?
No response
Acknowledgment

[X] I understand the final update might be different from my proposed suggestion, or refused.

Hi @sthulb! Are you talking about testing in general with Powertools? In our contributing guide we have a GitPod template ready to run the Powertools tests (local + e2e) and I wonder if that's not enough.
https://github.com/aws-powertools/powertools-lambda-python/blob/develop/CONTRIBUTING.md#contributing-via-pull-requests
Thank you.

@leandrodamascena I was thinking more like adding a section like: https://developer.hashicorp.com/terraform/plugin/testing/testing-patterns

While there may not be a dedicated "testing" section in the documentation, it's worth noting that each utility within the aws-powertools library typically includes a "Testing Your Code" section. (Example: batch processing. This section provides guidance on how to write tests specifically for that utility.
Expanding this with a dedicated section for testing will exponentially increase the effort to maintain the code. For now I will close the issue, and I ask you to reopen if necessary.

@heitorlessa is working on this documentation.
Reopening.


Update Grunt SASS for compatibility with Node 0.12

By default Brew installs Node 0.12 which doesn't work with the version of Node SASS being used, which is only compatible with versions up to 0.10.
This commit updates the version of Grunt SASS to 0.18.0, which incorporates Node SASS version 2.0.0, which is compatible with Node 0.12.

this still fails for me - looks like node-sass needs to be 2.1.1

@joelanman Thanks for digging into that. Weird that it needs Node SASS and Grunt SASS installed but works locally for me now on Node 0.10.35.


Publish a .dll on NuGet too?

IIUC, forge is today only published as a command line utility. Would it be possible and/or desirable to publish a library to NuGet, in addition to the CLI tool published today, which exposes the same functionality?
The use case would be for tools like https://github.com/fsprojects/Mechanic to not have to re-implement the fsproj parsing and patching features, but rather just call Forge for that.
(Of course, that could be done anyway, but it would require shelling out to start a separate process for each command, which obviously would be much slower...)

Will be done as part of 3.0 Update (https://github.com/ionide/Forge/pull/120)


Bug: ContentTypeGroupChatMemberAdded

Describe the bug
I'm experiencing a consistent error in the Playground when attempting to utilize ContentTypeGroupChatMemberAdded

Expected behavior
No response
Steps to reproduce the bug

Git clone the playground
npm install
npm run dev

Environment Details:
Os X
node v18.16.1 (npm v9.5.1)

The V2 implementation of group chat has been removed from the playground in favor of a V3 implementation coming soon.


python310Packages.azure-mgmt-datafactory: 2.10.0 -> 3.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.azure-mgmt-datafactory is: This is the Microsoft Azure Data Factory Management Client Library
meta.homepage for python310Packages.azure-mgmt-datafactory is: https://github.com/Azure/azure-sdk-for-python
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.0 with grep in /nix/store/4qpnggdv4czlfr48zz14v45x1y86qknj-python3.10-azure-mgmt-datafactory-3.0.0
found 3.0.0 in filename of file in /nix/store/4qpnggdv4czlfr48zz14v45x1y86qknj-python3.10-azure-mgmt-datafactory-3.0.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.azure-mgmt-datafactory
python311Packages.azure-mgmt-datafactory

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4qpnggdv4czlfr48zz14v45x1y86qknj-python3.10-azure-mgmt-datafactory-3.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4qpnggdv4czlfr48zz14v45x1y86qknj-python3.10-azure-mgmt-datafactory-3.0.0
ls -la /nix/store/4qpnggdv4czlfr48zz14v45x1y86qknj-python3.10-azure-mgmt-datafactory-3.0.0/bin

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

2 packages built:

python310Packages.azure-mgmt-datafactory
python311Packages.azure-mgmt-datafactory

Maintainer pings
cc @mwilsoncoding for testing.

Result of nixpkgs-review pr 217640 run on aarch64-darwin 1

2 packages built:

python310Packages.azure-mgmt-datafactory
python311Packages.azure-mgmt-datafactory


Remove unnecessary exception handling

Created transaction exception mapper that sends the cause of the exception to the user, here we probably need to censor the messages being sent.
created also authorization exception mapper that can be used to send unauthorized status code when glassfish access local exception is thrown. (when a person tries to access resource with out logging in.)
removed unnecessary exception handling that can be handled by the mappers.


Failed to load new database: Malformed database

Testing database: '/opt/clamav/share/clamav/tmp.67896b982e/clamav-a65697386397c627a324ac8995cfced2.tmp-twinclams.ldb' ...
WARNING: [LibClamAV] cli_parse_add(): Problem adding signature (3).
WARNING: [LibClamAV] Problem parsing database at line 2394
WARNING: [LibClamAV] Can't load /opt/clamav/share/clamav/tmp.67896b982e/clamav-a65697386397c627a324ac8995cfced2.tmp-twinclams.ldb: Malformed database
ERROR: Failed to load new database: Malformed database
WARNING: Database load exited with "Test failed"
ERROR: Database test FAILED.
Unexpected error when attempting to update from custom database URL: https://raw.githubusercontent.com/twinwave-security/twinclams/master/twinclams.ldb
WARNING: fc_download_url_databases: fc_download_url_database failed: Test failed (8)
ERROR: Database update process failed: Test failed
ERROR: Update failed.

Fixed!


Prisma can't finding any environmental variables when Nuxt is in production

Environment

Operating System: Windows_NT
Node Version:     v16.16.0
Nuxt Version:     3.6.0
Nitro Version:    2.5.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
I have created this repo repo that recreates the issue. In summary if you load the DATABASE_URL from a .env, prisma wont find it when Nuxt is in production.
Describe the bug
When nuxt is in dev, prisma functions perfectly. However when I build the nuxt app, prisma can no longer find any of the environmental variables that were in the .env file and it fails.
Additional context
No response
Logs
[nuxt] [request error] [unhandled] [500]
Invalid `prisma.user.findMany()` invocation:

error: Environment variable not found: DATABASE_URL.
  -->  schema.prisma:10
   |
 9 |   provider = "sqlite"
10 |   url      = env("DATABASE_URL")
   |

Validation Error Count: 1
  at Rn.handleRequestError (C:\Users\petal\Desktop\Work\nuxt-prisma\.output\server\node_modules\@prisma\client\runtime\library.js:174:7601)
  at Rn.handleAndLogRequestError (C:\Users\petal\Desktop\Work\nuxt-prisma\.output\server\node_modules\@prisma\client\runtime\library.js:174:6754)
  at C:\Users\petal\Desktop\Work\nuxt-prisma\.output\server\node_modules\@prisma\client\runtime\library.js:177:3010
  at async C:\Users\petal\Desktop\Work\nuxt-prisma\.output\server\node_modules\@prisma\client\runtime\library.js:177:3225
  at async t._executeRequest (C:\Users\petal\Desktop\Work\nuxt-prisma\.output\server\node_modules\@prisma\client\runtime\library.js:177:11403)
  at async /C:/Users/petal/Desktop/Work/nuxt-prisma/.output/server/chunks/data.get.mjs:6:16
  at async Object.handler (/C:/Users/petal/Desktop/Work/nuxt-prisma/.output/server/node_modules/h3/dist/index.mjs:1285:19)
  at async toNodeHandle (/C:/Users/petal/Desktop/Work/nuxt-prisma/.output/server/node_modules/h3/dist/index.mjs:1360:7)
  at async ufetch (/C:/Users/petal/Desktop/Work/nuxt-prisma/.output/server/node_modules/unenv/runtime/fetch/index.mjs:9:17)
  at async $fetchRaw2 (/C:/Users/petal/Desktop/Work/nuxt-prisma/.output/server/node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:206:26)

You need to manually set those variables in production.
We are considering changing this within nitro.

Ok thank you.
Le dim. 25 juin 2023 à 15:10, Daniel Roe @.***> a
écrit :

You need to manually set those variables in production.
We are considering changing this within nitro.
—
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt/issues/21753#issuecomment-1606085284, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBX5VURITAVCQNPI2PDVYDXNA2FZANCNFSM6AAAAAAZSZQXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

How did you fixed it?
I don't understand the "You need to manually set those variables in production." and why the behaviour is different in dev/build mode

Ok thank you. Le dim. 25 juin 2023 à 15:10, Daniel Roe @.> a écrit :
…
You need to manually set those variables in production. We are considering changing this within nitro. — Reply to this email directly, view it on GitHub <#21753 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGBX5VURITAVCQNPI2PDVYDXNA2FZANCNFSM6AAAAAAZSZQXGQ . You are receiving this because you authored the thread.Message ID: @.>

Hi, so I don't know what server you are deploying your Nuxt App but I
wanted to deploy on an Apache server on Ubuntu, for that you need to find
the /etc/environment file and there you paste in your environmental
variables from your .env file
Le lun. 24 juil. 2023 à 17:49, bertrand @.***> a écrit :

How did you fixed it?
I don't understand the "You need to manually set those variables in
production." and why the behaviour is different in dev/build mode
Ok thank you. Le dim. 25 juin 2023 à 15:10, Daniel Roe @.
> a écrit : … <#m_-3821636810308598352_> You need to manually set those
variables in production. We are considering changing this within nitro. —
Reply to this email directly, view it on GitHub <#21753 (comment)
https://github.com/nuxt/nuxt/issues/21753#issuecomment-1606085284>, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBX5VURITAVCQNPI2PDVYDXNA2FZANCNFSM6AAAAAAZSZQXGQ
https://github.com/notifications/unsubscribe-auth/AGBX5VURITAVCQNPI2PDVYDXNA2FZANCNFSM6AAAAAAZSZQXGQ
. You are receiving this because you authored the thread.Message ID: @.>
—
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt/issues/21753#issuecomment-1648173984, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBX5VU34LSNJWL3WGRIWLLXR2KPTANCNFSM6AAAAAAZSZQXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks so much! I've deleted my comment because i learned how to fix it with pm2
Actually, reading this page helped https://nuxt.com/docs/guide/directory-structure/env (coming from nuxt 2 didn't make it easier)

Thanks so much! I've deleted my comment because i learned how to fix it with pm2 Actually, reading this page helped https://nuxt.com/docs/guide/directory-structure/env (coming from nuxt 2 didn't make it easier)

I am in the same trouble. Could you explain the origin of the problem? And you solution?
Thanks!

Hi Sébastien, so the assumption is that you will use nuxt in production
only in a server environment and on the server in is best practice to use
environment variables rather than to use a .env file like we do in
development.
Le mar. 19 sept. 2023 à 11:18, Sébastien MASSE @.***> a
écrit :

Thanks so much! I've deleted my comment because i learned how to fix it
with pm2 Actually, reading this page helped
https://nuxt.com/docs/guide/directory-structure/env (coming from nuxt 2
didn't make it easier)
I am in the same trouble. Could you explain the origin of the problem? And
you solution?
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt/issues/21753#issuecomment-1725133245, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBX5VV2RNWQTMK5IZPGRRTX3FPP3ANCNFSM6AAAAAAZSZQXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

We're facing the exact same problem with AWS Amplify. Any ideas how to fix it?

We're facing the exact same problem with AWS Amplify. Any ideas how to fix it?

Hi there, did you manage to fix it by any chance? I'm facing the same issue

We're facing the exact same problem with AWS Amplify. Any ideas how to fix it?

Hi there, did you manage to fix it by any chance? I'm facing the same issue

The way I managed to fix this in our case was to first define the url as a runtimeConfig in nuxt.config.ts something like this:
runtimeConfig: {
    baseUrl: process.env.BASE_URL
  },

And then when initializing the prisma client we just pass the url
const config = useRuntimeConfig();
const client = new PrismaClient({
    datasources: {
      db: {
        url: config.bdUrl
      }
    }
  });

This worked for us on amplify


Improve type of schema

Currently, the schema's type is:
schemas: keyof Schemas extends keyof Request
	? z.ZodObject<Schemas>
	: z.ZodObject<{ [key in Exclude<keyof Schemas, keyof Request>]: never }>,

This checks that there are no fields in schemas which are not in Request, and if there are gives this weird TypeError:
Argument of type 'ZodObject<{ unknownPropertyName: ZodString; body: ZodObject<{ name: ZodString; age: ZodOptional<ZodNumber>; }, "strip", ZodTypeAny, { ...; }, { ...; }>; }, "strip", ZodTypeAny, { ...; }, { ...; }>' is not assignable to parameter of type 'ZodObject<{ unknownPropertyName: never; }, UnknownKeysParam, ZodTypeAny, { unknownPropertyName: never; }, { unknownPropertyName: never; }>'.   The types of '_getCached().shape' are incompatible between these types.     Type '{ unknownPropertyName: z.ZodString; body: z.ZodObject<{ name: z.ZodString; age: z.ZodOptional<z.ZodNumber>; }, "strip", z.ZodTypeAny, { age?: number | undefined; name: string; }, { ...; }>; }' is not assignable to type '{ unknownPropertyName: never; }'.ts(2345)
I would like this to be better phrased, and, if possible, also check if the types match (so that writing query: z.string(), for example, would be a TypeError).

Not that typescript does not check for excess properties on non-literal objects


Fixes #21032 - Updates outdated SignalR package reference in custom logging example

Fixes #21032

@BrennanConroy ... If this is ok, shouldn't we version it? If so, which version(s) should show the change?

@guardrex I was thinking about that as well.  I believe the switch was after 3.0 - so the old example would be for 2.x and the new example would be 3.0 and greater.

We're starting to drop 2.x coverage these days; so if that's the case (>=3.1 ... note that 3.0 is already out of support as of last March), then the update on the PR is fine. We'll make one more change tho to set the versioning on the whole topic from 2.1 to 3.1. If that's what we'll do, then the change is from ...
monikerRange: '>= aspnetcore-2.1'

... to ...
monikerRange: '>= aspnetcore-3.1'

... in the topic's metadata on Line 5.
Hold off for a sec tho until @BrennanConroy advises us on the versioning for this.

We're starting to drop 2.x coverage these days

2.1 is still supported, and on full framework will basically be supported forever. So not sure why we are dropping coverage there.
2.1 should reference @aspnet/signalr (although the client is backwards compatible so @microsoft/signalr will work with a 2.1 server)
And 3.1+ should reference @microsoft/signalr.

So not sure why we are dropping coverage there.

For efficiency given that readers are mostly off of 2.x. If the update requires jumping through hoops (as it does here) to add or maintain the coverage, we've been dropping 2.x. This has been going on for a little while now. We're only strictly required to cover the current release via MS guidelines. In this case, we can keep this covered for 2.x. However ... indeed ... there be hoops here ...
@1kevgriff, you need to modify the PR to version the content, which unfortunately can take longer for us to explain than for one of us to just perform on a new PR. If you want that explanation, one of us can provide it. Alternatively, you'd close this PR and open an issue from the bottom of the associated topic. One of us would take the issue and work up the PR.

@guardrex I'm pretty sure I can get this versioned correctly.  Give me a few minutes and I'll update the PR for review.

@guardrex PR updated.  How's that?

Thanks again @1kevgriff ... I'll merge to live now, and these updates should hit the live site within 15 minutes.


An error when start is the same as the initial value of the registered time array, running SpacecraftFile/source_interval

When running ori_filetered = ori.source_interval(ori.get_time()[0], ori.get_time()[5000]),  I got an error ValueError: array of sample points is empty
It seems because start_idx = self._load_time.searchsorted(start.value) - 1 gives -1 in such a case.

@hiyoneda @saurabhmittal23 @Yong2Sheng What's the status on this one?

Hi @israelmcmc, I tested ori_filetered = ori.source_interval(ori.get_time()[0], ori.get_time()[5000]) using the 3-month orientation file of DC2, and there is no error now. So it has been fixed.

Thanks! I'm closing it then


Incompatible with IntelliJ Version 2022.2 EAP Build #IC-222.2680.4

Describe the bug
Plugin 'Atom Material Icons' (version 64.0.0) was explicitly marked as incompatible with the current version of the IDE therefore the plugin doesn't work at all. Is there any plans to update this to work with the EAP or will it work once there is an official release of this version.
To Reproduce

Install plugin with IntelliJ version listed above.

Expected Behavior
Plugin should load if compatible.
Environment
IntelliJ IDEA 2022.2 EAP (Community Edition)
Build #IC-222.2680.4, built on May 25, 2022
Runtime version: 17.0.3+7-b463.3 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 7000M
Cores: 8
Registry:
ide.balloon.shadow.size=0
Non-Bundled Plugins:
com.intellij.javafx (1.0.4)
net.scrumplex.fxmlhelper (1.0)
com.github.copilot (<IP_ADDRESS>0)
com.andrey4623.rainbowcsv (2.0.2)
Statistic (4.1.10)
Docker (222.2680.7)
org.dpytel.intellij.plugin.maventest (0.0.21)
zielu.gittoolbox (212.9.0)
com.chrisrm.idea.MaterialThemeUI (<IP_ADDRESS>)
izhangzhihao.rainbow.brackets (6.23)
Kotlin: 222-1.6.21-release-357-IJ2680.4
Screenshots

Already submitted for moderation, this will be available in a few days


Update Settings app shortcut in FalconX

Why did you change version?

To force update of the app

What? It will stay only for 1 hour max. Then it will be fixed by bot.
Remove the version change

Okay, if you say so. Done


Feat/rewrite - [merged]

In GitLab by @arcln on Mar 11, 2020, 04:50
Merges feat/rewrite -> develop

In GitLab by @arcln on Mar 11, 2020, 04:50
merged

In GitLab by @arcln on Mar 11, 2020, 04:50
mentioned in commit aea2f684516d10f719726dad8f18946f5c7d6417


Investigate MLflow model registry and how we might implement

What API does MLflow provide for model registry? how difficult for FML?

This looks pretty straightforward -- a set of entities and associated CRUD endpoints (RegisteredModel, ModelVersion, etc). However, it looks like we'd also need to introduce support for "log_model" endpoint, which would create a model in our backend store. (Artifact support is currently read-only.) This could be challenging with HTTP since the model files are so large.

created epic #1006 to capture stories. Probably 1 dev / 1 sprint of work.


AlwaysShow and classes

Hi,
If you use the alwaysShow property to display the counter whenever the input is selected, it by default uses the warning class. Is it possible to add an extra property so I can have:
Label is green when 0 -> threshold characters are present
Label is amber when threshold -> max characters are present
Label is red when max characters are present
Thanks

I agree, this would be the ideal behavior. Perhaps using a defaultClass option that is used until threshold is reached.

I vote this feature! 👍

Hey, does anyone have any news on this?
I want this feature really.
My working project won't wait for this feature to be implemented,
so I've implemented a temporary solution.
You can see it in the demo below.
https://codepen.io/qwe001/pen/LYGYxMa
I hope something close to this will be implemented as an official option!


Factoring out checks

I believe it's a easier-to-read and easier-to-tune version of regular checks on backend
The biggest problem of this PR is that it's going to be hard to blame code because most of it just moved.

Feel free to add comments after the merge.
e2e check fails because it uses production wamp and the scheme changed in this PR


Please address these license issues

Please address these license issues
https://github.com/hyperledger/indy-sdk/blob/ae9f8a252bb99e8b80c6d34c6c985fd95abfadef/vcx/libvcx/build_scripts/android/openssl/make_openssl.sh#L4-L5
https://github.com/hyperledger/indy-sdk/blob/ae9f8a252bb99e8b80c6d34c6c985fd95abfadef/Specs/libzmq/4.2.3/libzmq.podspec.json#L7-L9
https://github.com/hyperledger/indy-sdk/blob/ae9f8a252bb99e8b80c6d34c6c985fd95abfadef/Specs/libzmq-pw/4.2.2/libzmq-pw.podspec.json#L7-L10

The main concern here is the LGPLv3 license.  The OpenSSL license should not be a concern.

I can answer the questions posed.  I don’t know what is required to “address these license issues”.
AFAIK — libzmq is used within the Indy SDK, and libzmq-pw seems to be a fork of libzmq created by Evernym.   From the codebase I found this about libzmq-pw: "ZeroMQ fork with PairwiseCurveCP support”. I don’t see any documentation in the Evernym repo.
I don’t know if it matters, but it looks to me like libzmq is downloaded as binary artifact in builds - e.g. a dll.

From the linked report:
Priority: High
This metadata file indicates it is for components under LGPL-3.0, libzmq / libzmq-pw. Are these two components used by indy, and/or is their code contained anywhere in the repo?

I saw that. It asks a question and I’ve tried to answer it, but it doesn’t say what to do given the answer I provided.

Gotcha. @jeffcshapiro ?

Sorry, the question should have been worded as a recommendation:  If LGPL licensed code is in your repo as source code it can contaminate the codebase.  If it is only used as a binary (DLL) then it is OK.

@brentzundel — can you please confirm that libzmq is only used in binary form in this repo?  Same applies for libzmq-pw.
Thanks

To my understanding, libzmq and libzmq-pw are only used as binaries.

Thanks. @jeffcshapiro — now that we know that libzmq and -pw are binary only, what action do we need to take?

I think @jeffcshapiro makes note of it in his tool and closes the issue

Issue resolved, no license conflict - ZeroMQ used as binaries only

looks like I can't close the issue, please close


merge: dev to master

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix for #350

fixes #350: erroneous arguments were passed to test cases causing event emitter tests to fail

@indexzero Any progress on this?

This is also breaking. I'd like to get a stable 0.9.x out before merging.

@indexzero
I have discontinued using vows in favor of mocha as I am transitioning to babel/ES. If you need further work done on this, please suit yourself.
I also have no longer need for my clone containing the branch on which this PR is based upon. I can transfer this clone to you, if you want. So drop me a note.

Github will keep the PR around.

Great, will delete my fork then.


--clone flag doesn't work with private hosted repo

Version
2.9.3
Reproduction link
https://github.com/vuejs/vue-cli/tree/master
Steps to reproduce
Please forgive the invalid repro link, not sure what to put for a cli issue
My template repo is within a subgroup, I'm running the following:
vue init --clone my-project gitlab:my-own-gitlab.com:group-a/subgroup-a/template-repo
What is expected?
Template should be initialized from:
my-own-gitlab.com/group-a/subgroup-a/template-repo
What is actually happening?
vue-cli · Failed to download repo ... 'git clone' failed with status 128

@affanshahid same here, is there any way solutions for this problem?

i get it done finally after i check out the repo ‘download-git-repo’ . it has listed the solutions.
repo
@affanshahid
@andreasvirkus

@yyx990803 The issue is also present for 3.x

3.x init is just a bridge to 2.x code.

Fixed by #1880

With 3.0.2 I'm still having an issue with getting this to work.
This is the command I'm using with a privately hosted bitbucket server at stash.myserver.com:
vue create --preset stash.myserver.com/projects/EXP/repos/vue-cli-plugin-init --clone my-project
Returns with an error of:
✔  Fetching remote preset stash.myserver.com/projects/EXP/repos/vue-cli-plugin-init...
ERROR  Failed fetching remote preset stash.myserver.com/projects/EXP/repos/vue-cli-plugin-init:
 ERROR  Error: 'git clone' failed with status 128
Error: 'git clone' failed with status 128
    at ChildProcess.<anonymous> (/Users/ .... /.nvm/versions/node/v8.11.3/lib/node_modules/@vue/cli/node_modules/git-clone/index.js:33:22)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Socket.stream.socket.on (internal/child_process.js:346:11)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at Pipe._handle.close [as _onclose] (net.js:557:12)

Here is a second failed test, as I'm not 100% certain about the command syntax. In this case it just sits forever with no error:
vue create --preset bitbucket:stash.myserver.com:myusername/exp/vue-cli-plugin-init --clone my-project-test
⠹  Fetching remote preset bitbucket:stash.myserver.com:myusername/exp/vue-cli-plugin-init...The authenticity of host 'stash.myserver.com (xx.xxx.xxx.xx)' can't be established.
ECDSA key fingerprint is SHA256:......
⠸  Fetching remote preset bitbucket:stash.myserver.com:myusername/exp/vue-cli-plugin-init...

I've also tried various iterations of the git path, but always have one of the two same issues.
For reference, the git clone URL looks like this. Note the specified port in the ssh url - not sure if that matters:
ssh://git@stash.myserver.com:PORT/exp/vue-cli-plugin-init.git
<EMAIL_ADDRESS>

I'm also getting the status 128 message when trying to clone down a private GitHub repo that I've made for a custom Vue preset.

I am also seeing this issue with vue-cli version 3.2.1.
Furthermore I have published my preset in a private npm registry with a scope and running vue create --preset @myscope/vue-cli-preset-mypreset --clone myapp does not work either, but I guess this is a separate feature request, isn‘t it?


Update eventmodel.html.md.erb

@haginot You should merge this branch into the livedoc branch as well.


Add Airflow 2.0.2 constraint to requirements.txt

Issue #, if available:
Not applicable
Description of changes:
Adding the constraints file to the top of requirements.txt as per the best practice page https://docs.aws.amazon.com/mwaa/latest/userguide/best-practices-dependencies.html
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

As MWAA does not force this constraint, local-runner should not either.


fix: login design adjustments

Description

Adjusted design to meet figma

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read and ran all relevant commands as specififed in the Running Tests section of the Contributor Guide.
[ ] The title of the PR follows the Conventional Commits guideline
[ ] My local branch follows the naming standards in the Deepsource Branch Naming Convention or Biodiversity Branch Naming Convention
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy,
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[ ] All existing and new tests are passing.

You bro please resolve this conflict so I can merge it

This PR fix was resolved with another created PR https://github.com/FlutterPlaza/FinFlow/pull/140
so closing this PR now


Add Options for Hide Password/License Key

and also update Samples

hi @tpcarman or @rebelinux can you merge ?

I do not have privileges to do the merge in this repository :(


CWBI-test time series get endpoint is not working user not authorized error.

getting a user not authorized for getting time series values in CWBI-test.  I have tried multiple offices and getting the same error.  It might be an issue with the schema update since after I updated the schema I had to give CWMS permissions to office 'HQ' for CWMS_A2W to work again.  I am not sure if this is a similar issue with CDA.

I attempted to deploy the latest release of CDA to cwms-data earlier this week and failed due to this same error.
I reverted back and am awaiting a resolution to this issue to proceed.

good to know then it isn't a database schema issue it is a CDA issue since the new schema wasn't rolled out to the DMZ.

Could be the HQ office issue, that's the office it likely defaults to for the session for read, the office provide in that case is just used for lookup in the tables, not permissions.

what user would I need to give HQ permissions to? Also would we need to add that to every district database as well?  is this a database schema thing or a change in CDA?  seems to be CDA since the database Charles was looking at was not updated to the latest schema.

i think it's called "radar user", but the name will be the secrets you can lookup.
For the districts. no, those default to the office in the context name (e.g. spk-data) for the session.

@MikeNeilson so I had to give RADAR permissions to CWMS_USER for MVP to get data form MVP.  Looks like we would need to do this for all offices?  Writing seems to be fine since I am able to still write data from LRL.  Also appears to only be an issues with timeseries data so far as I can tell.  Should we assign permissions to all offices or should we make a fix on the CDA side?

do you mean you granted the role? It should also have web_user which should take care of that.
If you meant CWMS Users, then yeah, all of the weba users should already have it, not sure why it wouldn't gone away.

yeah CWMS Users to RADAR
BEGIN cwms_20.cwms_sec.create_user('RADAR',null,cwms_20.char_32_array_type('CWMS Users'),'MVP'); END;

Oh you had to add MVS, wow. Hmm, well, probably the easiest thing to do is just add them all. I'll look at it later. Was planning to revamp some of that design anyways so would rather not get too hung up on it right now.


Upgrade notify to v5

This also switches from the default FSEvents implementation to the new kqueue-based implementation, which I've measured to be significantly faster.
However, the new implementation also runs into the Too many open files (os error 24) error much earlier. I had to add an eprintln log to surface this error, which would otherwise go unreported by turbopack. A solution right now is to manually run ulimit -n unlimited in the shell session you want to run turbopack in. This could possibly be done by turbopack itself instead.

This also switches from the default FSEvents implementation to the new inotify-based implementation, which I've measured to be significantly faster.

Nit: do you mean kqueue here? I think inotify is a Linux thing, whereas FSEvents is on macOS

@wbinnssmith Yes, I meant kqueue.

Have also looked into this a while ago, don't know if it's of any value, but here's the old patch
https://gist.github.com/ForsakenHarmony/80b2d574670158dc0d7cc1b0930b504a


command run doesn't close when functionality contains observable calls via @nestjs/microservices clientProxy.send()

Is there an existing issue for this?

[X] I have searched the existing issues

Current behavior
When calling the logic via an HTTP request, it works as expected and request completes.
When calling the logic via a nest-commander command execution, the command hangs after successfully completing all logic.
given the following microservice client:
import { firstValueFrom } from 'rxjs';

import { Injectable } from '@nestjs/common';
import { ClientProxy, ClientProxyFactory } from '@nestjs/microservices';

import { MessagingConfigService } from './messaging.config';

@Injectable()
export class MessagingService {
  private eventsClient: ClientProxy;
  constructor(private readonly configService: MessagingConfigService) {
    this.eventsClient = ClientProxyFactory.create(this.configService.eventsConfig);
  }

  send<R, I = unknown>(pattern: string, data: I) {
    return this.eventsClient.send<R, I>(pattern, data);
  }

  async sendAsync<R, I = unknown>(pattern: string, data: I) {
    return await firstValueFrom(this.send<R, I>(pattern, data));
  }

  emit<R, I = unknown>(pattern: string, data: I) {
    return this.eventsClient.emit<R, I>(pattern, data);
  }

  async emitAsync<R, I = unknown>(pattern: string, data: I) {
    return await firstValueFrom(this.emit<R, I>(pattern, data));
  }
}

calling await this.messagingService.sendAsync('message-pattern', payload) results in the command hanging even though this call returns values.  Mind you, running the logic from an HTTP request works as expected, just not from the cli.
Also note that I have tested removing the microservice call and instead hard coded the response value, and it works fine in that instance.
Minimum reproduction code
@Command({
  name: 'test',
  arguments: '<action>',
  description: 'test command'
})
export class TestCommand implements CommandRunner {
  constructor(
    private readonly messagingService: MessagingService
  ) {}

  run(): Promise<void> {
     return this.messagingService.sendAsync('test-subject', {foo: 'bar'})
  }

Expected behavior
Command execution closes on response from sendAsync call.
Package

[X] nest-commander
[ ] nest-commander-schematics
[ ] nest-commander-testing

Package version
2.3.5
Node.js version
14.18.1
In which operating systems have you tested?

[ ] macOS
[ ] Windows
[X] Linux

Other
No response

Please provide a minimum reproduction repository. Most likely, the ClientProxy isn't being closed, but I can take a look

Please provide a minimum reproduction repository. Most likely, the ClientProxy isn't being closed, but I can take a look

sure thing! see: https://github.com/jubairsaidi/nest-examples
Note the screenshot of the example requests.  note that the last one I had to ctrl-c out get it to terminate

Thanks for the reproduction. I was able to reproduce with your code (woohoo), and I have a fix for it. But first, a little background as to what's happening:
When Nest creates a microservice client (your EventsClient) it's created lazily. It's not connected off the bat, and will only connect on manually calling connect as shown in the Nest docs (scroll up just slightly) or when the first event is sent. Because you don't end up calling sendAsync or send in your MessagingService code unless you use cli examples nats, the client is never connected and you never end up having the hang. But when you do use cli examples nats you connect the client, and it won't disconnect until told to.
There are two easy solutions here:

Change your send or sendAsync to include a close() call for this.eventsClient. This works okay, but you'll have to remember it each time, and if you end up making multiple sends you'll end up opening and closing connections which is slow

Add an OnModuleDestory or OnApplicationShutdown hook and call await this.eventsClient.close(). The top of the service could look like this:

@Injectable()
export class MessagingService implements OnModuleDestroy {
  private eventsClient: ClientProxy;
  private reqClient: AxiosInstance;
  constructor(private readonly configService: MessagingConfigService) {
    this.eventsClient = ClientProxyFactory.create(this.configService.eventsConfig);
    this.reqClient = axios.create();
  }

  async onModuleDestroy() {
    await this.eventsClient.close();
  }

With this, the event was sent, response was logged, and the command exited correctly.

this helped! thanks!!
Slight modification to get it working when making multiple calls though:
@Injectable()
export class MessagingService implements OnApplicationShutdown, OnApplicationBootstrap {
  private eventsClient: ClientProxy;
  constructor(private readonly configService: MessagingConfigService) {
    this.eventsClient = ClientProxyFactory.create(this.configService.eventsConfig);
  }

  async onApplicationBootstrap() {
    await this.eventsClient.connect();
  }

  async onApplicationShutdown() {
    await this.eventsClient.close();
  }
}

Seems we have to create a connection for this client (I assume that otherwise it creates a new connection on each request automatically?)
When omitting the onApplicationBootstrap I noticed onApplicationShutdown did get fired but the connection was still hanging when I'm making multiple calls in a given command execution.

Seems so, thanks for adding the modification! Glad I could help


Auto junction give-way/priority (on priority routes)

On a priority route (as defined via road info view panel), any junctions without traffic lights could be given automatic give-way and priority settings.
The calculations would be performed whenever user:

Marks or unmarks a road as 'priority route' (via road info panel)
Connects or disconnects a road to an existing priority route
Removes traffic lights at a junction that has at least one priority route attached

In cases where a junction has two or more priority routes, the primary route can be determined via metrics such as:

Number of lanes (more = higher priority)
Speed of road and/or lane (faster = higher priority)
Width of road and/or lane (wider = higher priority)

In game, yes, I believe marking a route as priority will cause connecting roads to be given stop signs.
However, what I'm seeking is tighter integration between TMPE and vanilla.
So TMPE should apply it's priority/yeild signs as applicable along a priority route.
There is already TMPE option of Shift+Click when adding priority signs to apply them to all junctions for the given road (not tested this myself yet, but see docs here: https://tmpe.viathinksoft.com/wiki/index.php?title=Priority_signs#Priority_roads ).
So in theory the heavy lifting code is already done, it just needs a little extra wiring so that when user first marks a route as 'priority' (using vanilla functionality) TMPE at that point sets up the priority/yield signs. Users can subsequently go in and change any junctions as desired.

That's an interesting way to look at it. Awesome idea +1

This was implemented by #631 - vanilla 'Priority road' checkbox replaced with TMPE priority toolbar.


updating url addresses

What does this PR do?
Improve repo
For resources
Description
Why is this valuable (or not)?
better current url structure
How do we know it's really free?
i am the author
For book lists, is it a book? For course lists, is it a course? etc.
book (online guide)
Checklist:

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

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Hmmm the link check report has a lots. https://github.com/EbookFoundation/free-programming-books/actions/runs/6389161328

have you verified that all the changed links work?

@eshellman yes the 2 urls changed for the Arabic and English version of the html guide has been checked and works.

it also seems that  librebooks.org is out of service (temporarily) and that is the source of a lot of Arabic books. i will try to contact the maintainer of the site to check if it will be back soon or not.

Thanks


the reconstructed features may have been calculated incorrectly

https://github.com/perrying/ssn-pytorch/blob/25c69d341beb412a9b5cd62dd92a3ae11b9d2971/lib/utils/loss.py#L49-L53
I have a question with line 53 in lib/utils/loss.py. According the paper 'superpixel sampling networks', the reconstructed pixel features are , and  means the row-normalized association matrix Q. however, the code in line 53 seems not using row-normalized Q but the Q itself to compute the reconstructed label.

In my view, assignment is a column-normalized matrix, and permuted assignment is the transpose matrix of assignment, meaning that permuted assignment is a row-normalized matrix.

if the assignment is a column-normalized matrix, the calculation of super-pixel feature should be torch.bmm(assignment, pixel_feat). however, the codes show that super-pixel feature is calculated by torch.bmm(assignment, pixel_feat) / assignment.sum(dim=2)
https://github.com/perrying/ssn-pytorch/blob/25c69d341beb412a9b5cd62dd92a3ae11b9d2971/lib/utils/loss.py#L48-L53
so i am confused why line 48 uses normalized assignment but line 53 not

Here is a simple example.
Assignment is a column-normalized ($nspix \times npix$) matrix, so column #j is the probability of pixel #j belonging to each spixel. Row #i of assignment is the cardinality of the spixel #i, like $(1, 1, 1, 0, \ldots, 0)$ means that the first 3 pixels belong to spixel #i (though they may not be 1).
Column #k of permuted label (labels in Line 48) means that each pixel belongs to class #k or not. If the cluster is of precision and belongs to class #k, column #k should be $(1, 1, 1, 0, \ldots, 0)^\mathrm{T}$.
After multiplication, the (i, k) element of spixelWithoutMean (if spixel_mean is not be divided by assignment.sum(...)) is 3. But this matrix represents probability, meaning that each element should be not greater than 1. So this matrix should be divided by the cardinality of spixels.
As for Line 53, permuted_assignment is a row-normalized matrix, so the sum of each row (dim is 2) is 1. Besides, it is on the left side, meaning that it is not necessary to obtain a sum vector.

ok, i see. thanks a lot for your reply.


Fix flakey test: TestPendingRetryWorkflowWithRetryStrategy

This test is failing master builds. It looks like the test is flakey rather than incorrect.
This test was introduced in #2385.

@jamhed I think you introduced the test? Before we disable it, do you want to investigate?
The first actually failing build appears to be the one after yours, but as that is UI only changes, it cannot be that one:
Failures

https://circleci.com/gh/argoproj/argo/9235
https://circleci.com/gh/argoproj/argo/9238

Argo builds have become unstable on master. As previously, Ive enabled "Require branches to be up to date before merging". The flakey  test is TestPendingRetryWorkflowWithRetryStrategy .
@whynowy @sarabala1979 @simster7

I own this test, I’ll self assign.

@alexec The flakey-ness of this test is because of this line:
https://github.com/argoproj/argo/blob/32fc2f78212d031f99f1dfc5ad3a3642617ce7e7/test/e2e/fixtures/e2e_suite.go#L103-L104
From the sack trace:
...
            github.com/argoproj/argo/test/e2e/fixtures.(*E2ESuite).DeleteResources(0xc000a0c3f0, 0x1f282d2, 0x8)
            	/home/circleci/.go_workspace/src/github.com/argoproj/argo/test/e2e/fixtures/e2e_suite.go:104 +0x1699
...

The test passes reliably in my local machine. Thoughts?

TODO - may make tests flakey

😂

That code is several weeks old and this test has only just started failing the exact commit the PR was merge at.
But, that comment is clear about it, so leave it with me.

Test is currently being skipped


[HAWKULAR-1316] Added info on docs about oc 3.7 command

I could not use the the command to generate secrets ( oc create secret generic hawkular-javaagent-example-ca --from-file=hawkular-services-ca.crt=/opt/hawkular/hawkular-services-public.pem) because it is specific from oc 3.7+.
I think it should be good to advise the users to have that version to use the command

@mwringe Can you review it?


fp-ts bind

Hello! Thanks for fp-go! It's real FP revolution in Go 😄
fp-ts contains bind for any Monad
Example, https://gcanti.github.io/fp-ts/modules/Either.ts.html#bind
It's allows to pass value through pipe, which very useful
Maybe it's possible to implement it somehow in fp-go?

Hi @darky I have started to implement the do functions for Option, Either and IO. More to come. You can check on the https://github.com/IBM/fp-go/tree/cleue-bind branch.
The implementation is not identical to the fp-ts one since it should be type safe, but go does not have a way to create ad-hoc types with keys that are passed in dynamically.
So the approach I took is similar to the pattern used in optics. Instead of passing in the name of a field as a first parameter and assume that the bound state is a record, we assume that the state is of an arbitrary type S1 and binding the new value results in a type S2. So the first parameter to the do functions is a function of the form
func(T) func(S1) S2

where

T is the value to be added to the state
S1 is the base state
S2 is the new state

this follows the design for the setters in optics that have the signature
func(T) func(S) S

i.e. a special case of the above.
Let me know what you think or if you have other suggestions.

Great, thanks! It's best possible solution for Go at this moment IMO! 👍

I merged the bind branch, I believe I covered all monads. Pls. let me know if anything is missing.


Adding api.delete() and removing Key.delete().

Also:

Changing api.get() back to accept only keys and
returns only a list (a lot of headache for not much
gain).
Factored out behavior to extract shared dataset_id from
a set of keys into _get_dataset_id_from_keys().
Updated docstrings and other tests that rely on changed /
removed methods.

See #518 for some context.

Coverage remained the same when pulling c5a634f160732dbc8ac13085b8012b0d9b83f6db on dhermes:add-delete-method into 0525530ad7a76e408ca2e842b883d49c353ed56d on GoogleCloudPlatform:master.

@tseaver I took a stab at testing / integrating the implementation from your comment.
If you already wrote this up, feel free to close.
Also, viewing _get_dataset_id_from_keys in light of #447, we should remove dataset_id from the Batch constructor and instead rely on Batch.put(), Batch.add_auto_id_entity(), and Batch.delete() to set / check the dataset ID. (This also means Batch.begin() has to move outside of __enter__.)

LGTM.

Merge broken?
======================================================================
ERROR: test_delete_existing_batch (gcloud.datastore.test_api.Test_delete_function)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/travis/build/GoogleCloudPlatform/gcloud-python/gcloud/datastore/test_api.py", line 322, in test_delete_existing_batch
connection._deleted,
AttributeError: '_Connection' object has no attribute '_deleted'
======================================================================
ERROR: test_delete_implicit_connection (gcloud.datastore.test_api.Test_delete_function)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/travis/build/GoogleCloudPlatform/gcloud-python/gcloud/datastore/test_api.py", line 350, in test_delete_implicit_connection
connection._deleted,
AttributeError: '_Connection' object has no attribute '_deleted'

No, merge was fine, just changes to test_batch._Connection from #524 broke my tests (rightfully so).
I fixed in 2908d6f8cb389ace2b28a495fdd253c039335beb.

Coverage remained the same when pulling 2908d6f8cb389ace2b28a495fdd253c039335beb on dhermes:add-delete-method into 51c1069bef888ed982cb889745b4b9f90584503d on GoogleCloudPlatform:master.


TouchableWithoutFeedback crashes when SVG component is a direct child of it

Description
After moving my app to Expo SDK 50, hence<EMAIL_ADDRESS>I got following error:
Exception thrown while executing UI block: - [RNSVGSvgView setOnClick:]: unrecognized selector sent to instance 0x7f8f3b8e3c00

After some time of debugging, I understood, that the problem in part of the code that looks like this:
import SvgIcon from "../assets/icon.svg;
...
<TouchableWithoutFeedback onPress={() => console.log("pressed")}
  <SvgIcon />
</TouchableWithoutFeedback>
...

If I wrap SvgIcon with View component, everyting works just fine.
Steps to reproduce

I am using Expo dev-build, which were initialized from npx react-native@latest init <project-name>.
Also use react-native-svg-transformer to be able to import svg directly into the code

React Native Version
0.73.4
Affected Platforms
Runtime - iOS
Output of npx react-native info
System:
  OS: macOS 14.1.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 442.61 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.1
    path: ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn:
    version: 1.22.21
    path: ~/.nvm/versions/node/v20.11.1/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.nvm/versions/node/v20.11.1/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.13.0
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.4
      - iOS 17.4
      - macOS 14.4
      - tvOS 17.4
      - visionOS 1.1
      - watchOS 10.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.1 AI-221.6008.13.2211.9619390
  Xcode:
    version: 15.3/15E204a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.18
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.4
    wanted: 0.73.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: true
  newArchEnabled: false

Stacktrace or Logs
No console/debugger output, only on my iOS Simulator screen (provided screenshot)

Reproducer
https://snack.expo.dev/@amoka/upbeat-orange-crackers
Screenshots and Videos

Hi @am0ka
Thanks for reporting this issue.
You should open this issue here first:
https://github.com/kristerkari/react-native-svg-transformer/issues
And get back to us if the library authors report that this is a React Native core issue


Add missing promote tab to ObjectList permission example

As per https://github.com/wagtail/wagtail/issues/10117#issuecomment-2002393424

Merged in 9dc38076ed9d12d63dc40258e6135b43d4054d96 (main) / 53ccb4c102 (stable/6.1.x)

Legend, thank you.


Some work on wireframe screens, changed urls to more reasonable

Slowly moving forward with wireframe views. Now you can go to /mui/landing, click on "check it out" and there is some working navigation.
Changed /mui/requestRide to my RequestRideScreen component, inside of which you can find the map that was previously there
Also changed the map loading part on GoogleMap component, left the old version commented out, please take a look. Also added export to GoogleMap component, so I can use it elsewhere.

Just some general notes  (missed to say this last PR)

Filenames in https://github.com/vilnius/vilnius-carpool/tree/master/src/packages/carpool-view-mui/views doesn't need Mui... prefix - (thus this is required for templates to stay unique)


Include Link to Python Implementation of Standard

There's currently a link in the readme to the Javascript implementation of the standard. It seems nice to also add a link to the Python implementation here: https://github.com/namehash/ens-normalize-python
What do you think? 😄

Updated, also added to ens-normalize.js readme
FYI this repo is out of date.  Latest updates in branch of ENS docs.


cmd: ignore the directory named go.mod

The existing implementation does not check in all cases whether go.mod is a regular file.
Fixes #30788

I signed it!


New package: Webview v0.99.0

Registering package: Webview
Repository: https://github.com/congzhangzh/Webview.jl
Created by: @congzhangzh
Version: v0.99.0
Commit: 8f8db27d39763c78aab3f9765cb17fe3cea4807d
Reviewed by: @congzhangzh
Reference: https://github.com/congzhangzh/Webview.jl/commit/8f8db27d39763c78aab3f9765cb17fe3cea4807d#commitcomment-148962001
Description: a webview julia binding inspired by webview_deno

With the existing Webviews.jl, I’m not sure there is space for another webview implementation. Or at least, I think it would have to very clearly delineate itself, and be in a pretty mature state

It would also need a name that does not clash with existing packages.

Hi, it’s just more simple in implementation and using, if it’s not fit JULIA package guidelines, hope keep it as a alternative. But, if acceptable, it will be great for community to have another choice


OAuth popup window redirects to base url

Hi,
Just started using this and there's an irritating issue with the OAuth popup window.
Most of the times I get redirected to the base url of my site in the popup window as soon as it opens and the first request is made (in case of Facebook), and after selecting the account (in case of Google). If I then close the popup, I get an error saying "Authentication canceled".
Do you have any suggestions in how to fix this?
Thanks.

You should catch the "Authentication Cancelled" and handle or ignore it (it's "by design"). It's a good thing to handle exceptions whenever they throw.
As for the redirection, you can specify in the provider redirectUri: 'https://my-domain.com/anything' just remember to approve it in your provider's site (google/facebook console).

Thanks. The problem is that the redirection happens inside the pop-up and it is not being closed. The redirectUri is being loaded inside the pop-up.

Your redirectUri must be under the same host as your login page.
So if your login page is under my-site.com the redirection must also be under my-site.com and not www.my-site.com or anything else.


Fix syntax errors

Signed-off-by: dcwbq<EMAIL_ADDRESS>What type of PR is this?
/kind bug
What this PR does / why we need it:
Fix syntax errors
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

/assign @bowei

@bowei Please help approve. Thx


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118585

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118611

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119064

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119086

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119098

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119538

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120290


feat: generate code as side effect of build

Hey @oscartbeaumont, I'm super excited about this library.
I believe it would be cleaner and simpler if .build() would generate the typescript definitions as side effect instead of having to call     router.export("..").unwrap();
Additionally, it may be a  good idea to have a default name for the exported file or dir {ts_root}/rspc/index.ts/{ts_src_root}/rspc.ts;
For that to be configurable, a method like set_export_ts_root. I'm adding ts here because maybe in the future another languages can be supported, for example I'm hoping to add lua support somehow

The idea of automatically exporting the bindings is great but it's worth remembering that when you build the app into a binary for release it would continue exporting the bindings which wouldn't be great for most use cases. I have been doing the following in most of my projects but a helper for it would be great.
let router = Router::new().build();

#[cfg(debug_assertions)] // This will only export the bindings when the app is in development mode
router.export(TRPC_BINDING_EXPORT_PATH).unwrap();

I just pushed an commit which lets you do:
let router = <Router>::new()
        .config(Config::new().export_ts_bindings("./ts"))
        .query("version", |_, _: ()| env!("CARGO_PKG_VERSION"))
        .build();

This feature will only export the bindings in debug mode like the sample I showed above. If you need to export the bindings in a release build you will have to do them manually. We couldn't have a default file name as the system exports to a directory and I don't really think a default directory makes sense. People will end up structing their projects differently and I don't think providing a path is too much work to warrant a default but if you do really disagree with this I would be interested to hear why.

The idea of automatically exporting the bindings is great but it's worth remembering that when you build the app into a binary for release it would continue exporting the bindings which wouldn't be great for most use cases. I have been doing the following in most of my projects but a helper for it would be great.

let router = Router::new().build();

#[cfg(debug_assertions)] // This will only export the bindings when the app is in development mode

router.export(TRPC_BINDING_EXPORT_PATH).unwrap();

I just pushed an commit which lets you do:

let router = <Router>::new()

        .config(Config::new().export_ts_bindings("./ts"))

        .query("version", |_, _: ()| env!("CARGO_PKG_VERSION"))

        .build();

This feature will only export the bindings in debug mode like the sample I showed above. If you need to export the bindings in a release build you will have to do them manually. We couldn't have a default file name as the system exports to a directory and I don't really think a default directory makes sense. People will end up structing their projects differently and I don't think providing a path is too much work to warrant a default but if you do really disagree with this I would be interested to hear why.

I agree, awesome turn around, I like it 😍 thanks


chore: remove leftover code

Summary
Since the mmkv was migrated to a pure c++ turbo module, there is no longer need for the adapter which anyway includes useless code

Thank you!


Create externalDependencies.xml

This will ensure IntelliJ IDEA will prompt the user to install these plugins when contributing to the project.
https://www.jetbrains.com/help/idea/managing-plugins.html#required-plugins

I'm not in favour of adding this as it implies that we support IntelliJ IDEA for development. Obviously external contributors are welcome to use whatever IDE they like to contribute as long as the code conforms to our guidelines, but Android Studio is the only officially supported IDE.
I will leave open and raise with the team though to see if there are other opinions.

When I said IntelliJ IDEA, I also meant Android Studio. Both share the same settings.
externalDependencies.xml is developped on the IntelliJ IDE but is compatible with all IDE based on it.


FOSDEM 2024: feedback

Would be great if anyone has any feedback from our FOSDEM 2024 talk and demo.
This can be feature requests, bug reports, or just a discussion.
Talk - https://fosdem.org/2024/schedule/event/fosdem-2024-2960-quartz-solar-os-building-an-open-source-ai-solar-forecast-for-everyone/

I think you mean FOSDEM (not FORSDEM)
I did not catch the start but found the presentation interesting
I do some pottery/ceramics and whilst I don't have an electric Kiln and PV panels, I have friends and fellows who do and see the software and forcast as a very useful tool.
I hate reinventing the wheel so before I try and develop something, are you aware of anybody who has written a WordPress plug in for generating and displaying a forecast?

The link in Installation section of https://github.com/openclimatefix/Open-Source-Quartz-Solar-Forecast is missing a the "t" in Forecast https://github.com/openclimatefix/Open-Source-Quartz-Solar-Forecas

I have a WeatherFlow Tempest weather station and I also have it feed Weather Underground https://www.wunderground.com/dashboard/pws/IWINCH75/graph/2024-01-24/2024-01-24/daily
I thought I might be interesting to see how well a forecast matched what the weather station saw.
The tool displays Kilowatt Capacity? I assume from the example based on the parameter capacity_kwp=1.25.
Now my understand is that not all PV are equal and they have different efficiencies in term of converting solar radiation energy to electricity energy, so couple of questions.

What efficiency does the model assume?
Can I modify an option to assume 100% efficiency so that I can directly compare what the model predicted to the Solar Radiation that my weather station is allegedly measuring?

The README has

Which does not produce the plot shown. What is needed to produce the plot is in the the examples Juypter Notebook

HI @KeithSloan
Thanks so much for your feedback. We really appreciate it.

Wordpress plugin
This library is fairly new, so I would be very surprised if someone has. It would be great to hear how you get on with this. I have to admit I don't know much about Wordpress plugins.

missing t
Thanks for pointing this out, we'll make sure to fix this

PV efficiency
Great question, and it's a slightly complicated answer. We don't assume any efficiency of the panels. This is because we trained the model using variable weather variables directly to KW values. The efficiency of the panels can be effected by temperature humidity e.t.c. I would probably adjust the capacity value until it matches up, please do let us know what you found, I find this really interesting.

Also note once #36 is done, you could add your live values in, and the forecast would be more accurate.

Readme.md example plot
Thanks for pointing this out. We'll adjust this. I think if you use 2023-10-31 you get the plot in the readme.md

Thanks again @KeithSloan, please do let us know anything else

@zakwatts @rachel-labri-tipton is it worth adding a link to the talk you did to the readme? We could always host the video ourselves on youtube, if we are worried about the link breaking

Yes I think that's a good idea.

that sounds like a good idea, @peterdudfield

Whats the link? And I cant put it into the readme

Heres a link to the video on youtube: https://www.youtube.com/watch?v=NAZ2VeiN1N8
Heres a link to the original FOSDEM video: https://fosdem.org/2024/schedule/event/fosdem-2024-2960-quartz-solar-os-building-an-open-source-ai-solar-forecast-for-everyone/

@zakwatts, I see the video link hasn't been added to readme yet. If this is something pending, should I add the video link with a bit of an introduction to FOSDEM? Maybe, also OCF YouTube channel link?

Hi @roshnaeem. Yes you are correct this hasn't been completed yet. I have created a PR to do this so please feel free to add it! #96


Electron app doesn't show icons and content

Describe the bug
I can't see any icons nor edit any values within the Electron version of composer. I assume this has something to do with our proxy, but I havn't found any setttings to configure a proxy for the Electron app
Version
aca7358
Application SHA  test
SDK runtime packages  4.7.0-preview-191208-1
Browser

[ ] Chrome
[ ] Safari
[x] Firefox
[ ] Edge

OS

[ ] macOS
[x] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Start Electron app

Expected behavior
I should be able to edit the different fields and values
Screenshots

Additional context

@bgeissler are you behind a corporate firewall that disallows resolving public resources on the internet over https?

Yes, I'm behind a corporate firewall, but using our proxy I should (hopefully) be able to load the required data. I just don't know how to configure the Electron app to use our proxy or is this done automatically?

We do not expose currently this ability. This may take some investigation before we can resolve this. You're asking for the application to accept a proxy url to be used for all external network calls?

Yes, either the application should accept a proxy url or use the default proxy setting from the os, like Firefox is doing it for example

@tonyanziano tagging you to take a look at this after the auto-update pieces land.

@cwhitten : Should this be slotted for R14?


Fixing filters format (buyAPI)

I was trying the module with your examples, but I found that when you add "filter" to a searchItems() (example: filter: { conditions: "NEW" } ) the filter is added to the query url including the quotation marks and the app crash because of this. I added a replace (just like the one there is for the brackets) to fix that.

@paradox-ng  thanks.

Is this not sending ?SECURITY-APPNAME= or whatever is needed when calling searchItems?

I have had a lot of trouble getting this to work correctly....
Might I suggest just simply changing this line:
if (searchConfig.filter != undefined) queryParam = queryParam + "&filter=" + JSON.stringify(searchConfig.filter).replace(/[{}]/g, "").replace(/[""]/g, "");
to:
if (searchConfig.filter != undefined) queryParam = queryParam + "&filter=" + encodeURIComponent(searchConfig.filter);
and just expecting a properly formatted string as per the Ebay documentation such as:
'conditionIds:{1000}, buyingOptions:{FIXED_PRICE}'

@smulder Thanks for digging into it. Free feel to create Pull Request.

so I have my own clone which is updated and a fork for my own use. The worry I have is that, though I don't see how the search worked the way it was, from my limited tests, my change is certainly not compatible with anyone who is using what you have there now. So, submitting a pull request may be a bit more major than expected. If you like I can still submit it and you could reject or change as you see fit. I also updated the documentation to match what would be needed for the string based approach.
Would you like me to submit it anyway?

Yes you can. I appreciate it.
I will verify it and modify accordingly. I will test it by writing test cases.


Unable to change port with SSL

It is not possible to set a new port AND use SSL with the JSS::API.connect method. This is due to the following in api_connect.rb:
  # ssl or not?
  ssl = SSL_PORT == args[:port].to_i ? "s" : ''
  @rest_url = URI::encode "http#{ssl}://#{args[:server]}:#{args[:port]}/#{RSRC}"

Ideally, there would be a flag that can be passed in connect to be able to enable/disable SSL.

Thanks for the report!  I've just added args[:use_ssl] to fix this.
If you supply an non-standard port, you have to specify :use_ssl to be false (defaults to true)
The standard JSS ssl port 8443 is always treated as ssl.
      # we're using ssl if 1) args[:use_ssl] is anything but false
      # or 2) the port is the default casper ssl port.
      args[:use_ssl] = true if args[:use_ssl].nil? or args[:port] == SSL_PORT

      # and here's the URL
      ssl =  args[:use_ssl] ? "s" : ''
      @rest_url = URI::encode "http#{ssl}://#{args[:server]}:#{args[:port]}/#{RSRC}"

I'll get the changed pushed in a few..
Cheers,
-Chris

Oops, this was resolved months go... :-)


Potential issue in recipe_filler

I have tried to use the recipe_filler.py script to fill a recipe.
I created a recipe in the utils directory, recipe_test.yml identical to the example. And ran recipe_filler.py
python3 recipe_filler.py recipe_test.yml
I get the following:
2021-03-19 13:29:27,929 UTC [9510] INFO    Using user configuration file: /home/users/aschurer/.esmvaltool/config-user.yml
2021-03-19 13:29:27,929 UTC [9510] INFO    Using pilot recipe file: recipe_test.yml
2021-03-19 13:29:27,930 UTC [9510] INFO    Writing filled out recipe to: /home/users/aschurer/ESMValTool/esmvaltool/utils/recipe_autofilled.yml
2021-03-19 13:29:27,930 UTC [9510] INFO    Writing program log files to:
/gws/nopw/j04/edin_cesd/aschurer/ESMVALtools/recipe_filler_20210319_132926/recipe_filler/main_log.txt

/gws/nopw/j04/edin_cesd/aschurer/ESMVALtools/recipe_filler_20210319_132926/recipe_filler/main_log_debug.txt
2021-03-19 13:29:27,932 UTC [9510] INFO    Looking for data for variable ta in diagnostic diagnostic
2021-03-19 13:29:27,939 UTC [9510] DEBUG   CMIP5 root directory /badc/cmip5/data/cmip5/output1
2021-03-19 13:29:28,006 UTC [9510] DEBUG   CMIP6 root directory /badc/cmip6/data/CMIP6
2021-03-19 13:29:28,109 UTC [9510] INFO    Single ['*'] experiment requested
2021-03-19 13:29:28,114 UTC [9510] INFO    Seeking data for dataset: bcc-csm1-1
2021-03-19 13:29:28,116 UTC [9510] WARNING Could not find CMIP5 CMOR table for variable * with mip Amon
2021-03-19 13:29:28,117 UTC [9510] WARNING Could not find CMIP6 CMOR table for variable * with mip Amon

.....
And similar for all the other models
......
The autofilled recipe is the same as the orignial - i.e. not filled.
I got this to work by changing the lines:
if "short_name" not in recipe_dict:
     recipe_dict['short_name'] = variable

to
if "short_name" not in recipe_dict:
     recipe_dict['short_name'] = variable
elif recipe_dict['short_name']='*'
     recipe_dict['short_name'] = variable

which means if the short_name does not exist or if it is a wildcard it assigns it the variable string. I don't know if this will fix the issue for all applications but it worked for me.

@aschurer could you please post the recipe_test.yml you used? Cheers :beer:

The recipe I used was just the basic example given.
diagnostics:
diagnostic:
variables:
ta:
mip: Amon
start_year: 1850
end_year: 1900

cheers! For now just add a short_name: ta inside your ta: variable to start the runner, I will add an exception handler there, cheers for raising this! :beer:

cheers for raising @aschurer - fix in #2104 if you could have a look please, and approve upon review :+1:


implement polymorphism-based implementation of the RS friction laws

merges into Jeena's branch implementing the slip law.
state_rhs a pure virtual function in the abstract class DieterichRuinaBase, which is implemented in DieterichRuinaAging and DieterichRuinaSlip.

Looks good and compiling well. Thanks, Thomas.


Nonce must be greater than x you provided y

System information

Have I written custom code (as opposed to using zenbot vanilla): Vanilla
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
Zenbot version: Master from yesterday
NodeJS version:  Recommend by guide, so 8.X
Python version: "2.7
Exact command to reproduce: zenbot.sh trade poloniex.LTC-USDT

Describe the problem
Receiving the following error when live trading.
{ error: 'Nonce must be greater than<PHONE_NUMBER>19200. You provided<PHONE_NUMBER>06900.' }
I've search in older issues and found several suggestions, e.g. new API key, etc, however, none of them solved my issue, and because of that, I'm not able to sell and buy.
Thanks in advance.

I had this problem, and finally resolved it using this code.   Note - this is for Python3.x .
For safety you can call set_nonce() prior to executing any sell/buy.   So far this has been bullet-proof for me.
import traceback
import itertools
import poloniex
from poloniex import Poloniex
def say_exception() :
exc_type, exc_value, exc_traceback = sys.exc_info()
lines = traceback.format_exception(exc_type, exc_value, exc_traceback)
return ''.join('!! ' + line for line in lines)
def set_nonce():
try :
polo.returnBalances()  # forces a failure.  We pluck out the necessary nonce from the error msg
except :
reason = say_exception()
phrase = 'Nonce must be greater than'
pos = reason.find(phrase)
if pos > 0 :
rest = reason[pos+len(phrase):]
num = int(rest.split('.')[0])
polo.nonce_iter=itertools.count(num + int(time.time()))
print ('Poloniex nonce set to ' + str(polo._nonce))


[Issue]:Updated Dark Mode Button

name: Dark Mode Button Updated
about: Dark mode button was not working i have fixed that issue.
title: '[FIX] '
labels: ''
assignees: ''

name: Dark Mode button
Description
I encountered an issue with the dark mode feature in the project. When I tried to toggle the dark mode using the designated button, it did not work as expected. The page did not switch to the dark mode styling, and the background color remained unchanged.

Fixes # (issue)

Screenshots (if applicable)
How it appears before change

How it appears after change

Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update

Checklist

[x] I have read the contributing document.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have added necessary tests to ensure my changes are effective.
[x] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Additional Information

@mansiruhil13 I have updated the Dark Mode button. Please have a look and let me know if anything else is needed. I kindly request you to merge the PR.


[SPARK-38956][TESTS] Fix FAILED_EXECUTE_UDF test case on Java 17

What changes were proposed in this pull request?
This PR aims to fix FAILED_EXECUTE_UDF test case on Java 17.
Why are the changes needed?
BEFORE (Java17)
[info] QueryExecutionErrorsSuite:
16:04:22.234 WARN org.apache.hadoop.util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
16:04:24.377 ERROR org.apache.spark.executor.Executor: Exception in task 0.0 in stage 0.0 (TID 0)
org.apache.spark.SparkException: Failed to execute user defined function (QueryExecutionErrorsSuite$$Lambda$1582/0x0000000801653be8: (string, int) => string)

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually test on Java 17.

cc @MaxGekk

Merged to master.


Capabilities

Allow implementations to declare which capabilities they support.

Codecov Report
Attention: Patch coverage is 51.02041% with 24 lines in your changes missing coverage. Please review.

Project coverage is 47.59%. Comparing base (32752cb) to head (7e04284).
Report is 26 commits behind head on main.

Files
Patch %
Lines

src/desktop_notifier/dbus.py
0.00%
12 Missing :warning:

src/desktop_notifier/macos.py
20.00%
4 Missing :warning:

src/desktop_notifier/winrt.py
0.00%
4 Missing :warning:

src/desktop_notifier/main.py
57.14%
3 Missing :warning:

src/desktop_notifier/base.py
95.23%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #137       +/-   ##
===========================================
- Coverage   71.23%   47.59%   -23.65%
===========================================
  Files           8        8
  Lines         657      706       +49
===========================================
- Hits          468      336      -132
- Misses        189      370      +181

Flag
Coverage Δ

pytest
47.59% <51.02%> (-23.65%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Add octomap support

Based off of the LCMGL vtk renderer and the Octomap libbot renderer, I created this mash up.
The rendering GL code originated in the actual octomap library.
https://www.dropbox.com/s/k73quafcyj60hnl/octomap-in-director.m4v?dl=0
for reference:
https://www.dropbox.com/s/09lnwkeudmydci1/2015-09-fusion01b.mp4?dl=0
This is not fully finished feature, it doesn't have these features from the libbot version:

the properties are not properly sync'ed between python and c++ yet:

no min/max properties for showing part of a map
no min/max properties for coloring red/blue

also ~2 transmits of the octree are needed to send the cloud - even though the data arrives in the designer. not sure why.

Also includes an libbot function to return a jet color. maybe this is not needed.
@iamwolf  is going to take it on know, but wanted to get feedback from @patmarion at this stage.

Can you share a log with the octomap messages or tell me how to run the process that publishes octomap from lidar?

the .bt files here are in octomap format:
https://www.dropbox.com/sh/pmny97snn1tnu55/AACju6ih9R-UIxQNG6dXW7SRa?dl=0
to publish the octomap as an LCM message:
octomap-server octomap.bt
if you want to see a side-by-side, the old gtk viewer renderers in the pronto viewer:
pronto-viewer -c atlas/robot.cfg

Cool, thanks.  I hope to try it tomorrow.  I read thru the code in this pull request, looks great.  Plus, you took care of the all fun stuff adding the octomap options to cmakelists, nice!
I'm not sure how performance will vary (improve or not) but there may be some advantages to taking the approach where you generate geometry and let VTK handle the opengl drawing.  But, this current implementation seems to work fine, too.  In your video the framerate seemed decent.  It looked like there was not lighting / illumination though, just flat color.  Maybe I'm wrong about that.  Perhaps that's easy to toggle on as one of the opengl bits?
Let me know what you think, I'm happy to merge this now if you'd like to get it in, and you guys can do more work on it from there.

Rendering performance seems to be fine. (its a function of the level of the tree). It seems to render as efficiently as the other version.
You are right, the rendering is just flat color. I haven't dug into the opengl code to look at illumination and alpha. I'm happy to bring it in and improve it from there.
We are working on connecting collision free planning to real perception data.

BTW, more recent version of the rendering library comes with the octomap library itself. It looks like it wouldn't be difficult to move to using it.
This is their own application built on it:
https://www.dropbox.com/s/361fkx1w5uthc34/octovis-gui.m4v?dl=0

+1 for upgrading OctoMap.  I think there was something like a compile error in common_utils, perhaps the libbot renderer or something like that.  But I think it's worth upgrading and fixing the compile error if we can.

Note, here is some discussion about upgrading OctoMap and the associated compile errors:
https://github.com/openhumanoids/main-distro/issues/2067