Document empty string for configOverride

For https://github.com/orgs/stackabletech/discussions/30

@dmasice would you consider this helpful information or is something missing?

@sbernauer Looks good to me, but maybe reference it too from the "Configuration & Environment Overrides" in the operator docs?

@dmasice linking needs to be done in every operator individually, so we can mgere this change and add the linking afterards


Current working directory added to prompt.

Current working directory added to prompt. Also i have add hardcoded version info.

I appreciate the work, but I'm not currently looking to add new features to lsh right now (only bug fixes).  I'd rather keep the code as close to the original version from my tutorial as I can.  But feel free to keep working on your own fork of the shell -- there's plenty of stuff to do with it.


Rename the color prop to just c

💬 Questions and Help
Here is an example:
import React, { ComponentPropsWithoutRef } from 'react';
import styled, { x, type SystemProps } from '@xstyled/styled-components';

type ReactDiv = ComponentPropsWithoutRef<'div'>;

export interface BoxProps extends ReactDiv, SystemProps {}

function Box(props: BoxProps) {
  return (
    <BoxBase {...props} />
  );
}

const BoxBase = styled(x.div)``;

export default Box;

The code above pisses typescript because the react color prop type (string) is different than the xstyled one ( string | ThemeProp<string, Theme>).

If I were to omit the color prop from the react div type it would work perfectly fine
type ReactDiv = Omit<ComponentPropsWithoutRef<'div'>, 'color'>;

The question is, wouldn't it be better to rename the xstyled color prop to something else, for example just c, following a similar pattern with w and h?

@probablyup any comments, if you don't like the idea that's fine

Personally I prefer the long form of all the props because it's less confusing, albeit somewhat less convenient

It's more about not having TS conflict that changing the prop name to a shorter name. What is the suggested way of using cattle's when authoring component libraries like the example above?

I simply omit the html color property from the types, it's redundant anyway

Why do we have w, h, p, m then?

Why do we have w, h, p, m then?

Legacy decision. Given that it's been around for a while, hesitant to remove, but don't want to add more of them.

Why do we have w, h, p, m then?

Legacy decision. Given that it's been around for a while, hesitant to remove, but don't want to add more of them.

The quicker they go the less painful it will be 😄 Realistically though deprecation warnings can be added before completely removing them. Imo replacing them in a code base should be rather straight forward to automate anyway

As far as I remember, w and h were added, so we would avoid conflicts with the image height and width attribute.

How was that request different than the current request?

Also the request doesn't revolve around renaming the prop necessarily to c. It could be colour or hue for example. As long it does not introduce type conflicts, personally I don't mind.


children is not a function error using with Gatsbyjs

Got the following error:
Error in function Scrollspy in ./node_modules/@makotot/ghostui/dist/ghostui.esm.js:438
children is not a function
./node_modules/@makotot/ghostui/dist/ghostui.esm.js:438
` 436 |       currentElementIndexInViewport = _useScrollspy.currentElementIndexInViewport;
437 |

438 |   return children({
439 |     elementsStatusInViewport: elementsStatusInViewport,
440 |     currentElementIndexInViewport: currentElementIndexInViewport
441 |   });`

It looks like you are probably using it incorrectly.
Please check here for more information on how to use it.
https://ghostui.netlify.app/Scrollspy
If checking here doesn't seem to solve the problem, can you give me the code to reproduce it?
I close this issue, but feel free to reopen it.


Custom Calendar

Hi,
Is there anyway to implement custom calendar such as persian calendar?

This component behind the hood uses react-native's own DatePickerAndroid, TimePickerAndroid and DatePickerIOS.
This means that a feature like the one you're proposing must be supported by both DatePickerAndroid/TimePickerAndroid and DatePickerIOS for being implemented correctly on react-native-modal-datetime-picker.
Do the native picker implementations work with the persian calendar?

Closing, feel free to create a new issue if needed 👍
Also, please be aware that I created the following "new issue template" that, if followed correctly, will speed up a lot the issue resolution:

When reporting a bug, please be sure to check if the issue still persists with react-native original date/time pickers:
Under the hood react-native-modal-datetime-picker react-native original DatePickerAndroid, TimePickerAndroid and DatePickerIOS.
Before reporting a bug, try swapping react-native-datetime-picker with react-native original date/time pickers to check if the problem persists.
When reporting a bug, please be sure to include the following:

[ ] The outcome of the react-native-modal-datetime-picker swap described above
[ ] A descriptive title
[ ] An isolated way to reproduce the behavior (example: GitHub repository with code isolated to the issue that anyone can clone to observe the problem)
[ ] What version of react-native-modal-datetime-picker you're using, and the platform(s) you're running it on (iOS, Android, device)
[ ] What packages or other dependencies you're using
[ ] The behavior you expect to see, and the actual behavior

When you open an issue for a feature request, please add as much detail as possible:

[ ] A descriptive title
[ ] A description of the problem you're trying to solve, including why you think this is a problem
[ ] An overview of the suggested solution
[ ] If the feature changes current behavior, reasons why your solution is better

Please note by far the quickest way to get a new feature is to file a Pull Request.


Remove MissingNativeRCTNetworkingShim; revert MissingNativeAppStateShim

Summary
setupDevtools.js is accessing AppState.currentState without checking its availability. In environments where 1) __DEV__ == true, and 2) no RCTAppState native module is provided thus resorting to MissingNativeAppStateShim, this will result in an exception:
Cannot use 'AppState' module when native 'RCTAppState' is not included in the build. Either include it, or check 'AppState'.isAvailable before calling any methods.
(Interestingly, MissingNativeAppStateShim.currentState did have a default null value that was later removed.)
Update: Following @cpojer's suggestion of reverting https://github.com/facebook/react-native/commit/a93b7a2da0849f15708afef1ff99022d8cc55b14. Title also updated to reflect this.
Changelog

[General] [Fixed] - Remove MissingNativeRCTNetworkingShim; revert MissingNativeAppStateShim
Test Plan
No crashes in the same environments.

Hey @statm,
thanks for this PR. I actually think this is probably not the right solution but you linked to the PR that introduced this change and I dug into why it was made in the first place. Long story short, I think we don't need all the complexity that was introduced in https://github.com/facebook/react-native/commit/a93b7a2da0849f15708afef1ff99022d8cc55b14 at all. Would you mind simply making a revert of that commit and updating your PR with it? That should get rid of the isAvailable check (WebSocket should always be there in RN) and also restore the behavior from before where the currentState is simply null and doesn't throw. What do you think?

Also please do sign the CLA :)

@statm can you verify that this fixes the issue you are trying to solve and also can you sign the CLA under code.facebook.com/cla? Otherwise I can't merge this.

@cpojer Sure! I'm currently working/waiting on 3 things:

#24381 so CI will pass
Legal folks (MS) adding me to CLA
Locally re-bundle and validate

Hi @cpojer, reverting https://github.com/facebook/react-native/commit/a93b7a2da0849f15708afef1ff99022d8cc55b14 did fix the crash, thanks for your suggestion.
We are running RN in a unit test environment, therefore have stripped out most default native modules, including AppState. Further investigation revealed that when AppState native module is not present, this code in setupDevtools.js will assume app is active, and attempt connections to reactDevTools via WebSocket:
const isAppActive = () => AppState.currentState !== 'background';
These connections will timeout after a few seconds, slowing down all tests that involve JS code. I'm considering adding a check here, like in my initial commit:
const isAppActive = () => AppState.isAvailable && AppState.currentState !== 'background';
When AppState native module is absent, do not connect to reactDevTools. What do you think?

Hi @cpojer, reverting https://github.com/facebook/react-native/commit/a93b7a2da0849f15708afef1ff99022d8cc55b14 did fix the crash, thanks for your suggestion.
We are running RN in a unit test environment, therefore have stripped out most default native modules, including AppState. Further investigation revealed that when AppState native module is not present, this code in setupDevtools.js will assume app is active, and attempt connections to reactDevTools via WebSocket:
const isAppActive = () => AppState.currentState !== 'background';
These connections will timeout after a few seconds, slowing down all tests that involve JS code. I'm considering adding a check here, like in my initial commit:
const isAppActive = () => AppState.isAvailable && AppState.currentState !== 'background';
When AppState native module is absent, do not connect to reactDevTools. What do you think?

@statm let me know once the CLA is figured out and then I can merge it :)
I'd prefer to handle the issue about unit test environment that you mentioned in a separate PR if possible (this revert needs to happen either way). First though I'd like to understand which test framework you are using and whether we could shim out this setup file altogether? In general I'm hesitant to change code to make unit testing easier when you can easily mock things like this with a framework like Jest.

@cpojer Our UTs run on a native (C++) framework, focusing on managing facebook::react::Instances. You can think of them like a bunch of e2e tests, each with its own pre-built bundle. I'll try to add a dummy AppState module that always report 'background' just for testing and see if it blocks devtools connection.

@cpojer CLA done :)


Custom Balloon Paths Not Recognized

Describe the bug
I’m experiencing an issue with the Dialogue Manager 2.39.1 in Godot 4.2.2-stable where the runtime does not recognize custom balloon paths. Regardless of the custom path I set, whether it’s a scene path unrelated to dialogue or not, the runtime consistently defaults to the default balloon.
Affected version

Dialogue Manager version: 2.39.1
Godot version: 4.2.2-stable

To Reproduce
Steps to reproduce the behavior:

Create a copy of dialogue example balloon and customize it
Set the run time path to that balloon in dialogue manager
Observe that it always runs the balloon at res://addons/dialogue_manager/example_balloon/example_balloon.tscn regardless of the runtime path set.

Expected behavior
The Dialogue Manager should run my custom balloon as specified in the runtime path. I attempted to replace my custom dialogue at the path res://addons/dialogue_manager/example_balloon/example_balloon.tscn, which interestingly results in the runtime pointing to a different path and displaying my custom dialogue. This suggests that the paths I set are not being read properly.

You can see the custom balloon has a portrait, and the path is correct, but in the game, there’s no portrait:

When I use the default test scene, it should point to the default scene in the dialogue manager because I don’t have my custom test scene, but it actually tests the runtime path.

I have checked the dialogue balloon in the dialogue manager; it should have no portrait:

Can you show me the code you're using to start the dialogue in your game? It should be calling DialogueManager.show_dialogue_balloon().

Oh. I did forget to use show_dialogue_balloon(). I use show_dialogue_example_balloon() instead.
So now the runtime is correctly showing my custom balloon.
but the test still showing the runtime path balloon.

The "test dialogue" button will use whichever balloon is configured to be your runtime balloon (it uses show_dialogue_balloon() internally).
So is your game working as expected now? If so, I'll close the issue.

Yes. it's working as expected now. Thank you. Please close the issue


[Feature Request]: User-Friendly Notification System

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
User-Friendly Notification System: Adding a simple notification system to inform users about important updates or messages.
Use Case
Adding a User-Friendly Notification System to the Bobble AI project enhances the user experience by providing timely updates and alerts, which encourages engagement and interaction. The key benefits of this feature include immediate feedback on user actions, important alerts about system updates or new features, improved usability through clear communication, and increased user trust in the app.
Benefits
No response
Priority
High
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

@mansiruhil13 please assign me this issue i want to work on it
i hope youll consider this


HDDS-8119. Remove loosely related AutoCloseable from SendContainerOutputStream

What changes were proposed in this pull request?
Minor refactoring to simplify closing of GrpcReplicationClient.
https://issues.apache.org/jira/browse/HDDS-8119
How was this patch tested?
Existing unit/integration tests.
https://github.com/adoroszlai/hadoop-ozone/actions/runs/4368446905

Thanks @duongkame, @fapifta for the review.


Enable check suite

Codecov Report

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

@@          Coverage Diff          @@
##           master   #212   +/-   ##
=====================================
  Coverage      74%    74%
=====================================
  Files          32     32
  Lines         350    350
=====================================
  Hits          259    259
  Misses         91     91

Continue to review full report at Codecov.

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


help will print *.py files under ~/Documents/bin

I'm not great with debugging, but I'll do my best here.
Basically, I had a directory structure as so:
~/Documents/bin/remove_metadata.py
~/Documents/bin/noop.py
Then, when I go into stash and type help, the help messages would print up until rm, but it would also list noop in the help commands.
So basically, stash is reading the wrong bin directory (instead of ~/Documents/site-packages/stash/bin, it's also reading ~/Documents/bin
I solved the issue by moving any *.py files from under ~/Documents/bin
Error screen paste

Both bin directories are by default the locations where StaSh searches for command scripts. This is intentional as it is recommended to place user scripts under ~/Documents/bin/ so they do not interfere StaSh's internal bin (~/Document/site-packages/stash/bin/) but can still be called from StaSh's console.
With above said, you are right that the help command should only look into the internal bin folder. It can only hope sensible help messages to be generated for builtin commands NOT user scripts. It should not assume user scripts to follow a certain format or even complete. I'll make the change.
Thanks!

Yeah, in the cases where there are no help docs there's no issue with the parsing, since it lists the file name (command) only.
Thanks again!

This issue is fixed with commit 29ff695934719e03178ead05e60e2d558e873924
It is currently available in the dev branch and will be merged to master soon.


Add arg to not execute docker build instructions

Pull Request Test Coverage Report for Build 794

9 of 19 (47.37%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+8.9%) to 42.753%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

docker.go
7
17
41.18%

Totals

Change from base Build 789:
8.9%

Covered Lines:
410

Relevant Lines:
959

💛  - Coveralls


Master

Thank you very much for your pull David. I find it very useful. Maybe I'll made minor modifications but definitively is a useful improvement.


rp: Fix indexing for pins >31 on rp235xb

Does not handle using PIO with pins > 31, which is still broken.

spurious failure, forcing merge.


Feature/check custom settings

Critical Changes
The check_org_settings_value task uses the metadata tooling API, which does not support custom objects. However, many of our packages, such as NPSP, use custom settings objects. Here we add support for preflight checks for custom settings objects through the standard API.
Changes
Issues Closed

@erikperkins Thanks for working on this. Is there any existing discussion of this enhancement that would provide additional context for how you intend to use the check, and why you chose to add a new task rather than adjusting the existing one to handle both standard settings and custom settings?
My gut feeling is that it might make more sense to have a single task that uses the Tooling API when the entity doesn't end with __c, or the normal REST API when it does.
I guess using this check with custom settings will always need to be used in conjunction with another check that verifies the package providing the custom settings object is installed.

@davisagli There isn't specific documentation for the need for this sort of check. In NPSP, there is a check for Enhanced Recurring Donations which (improperly) relies on a locally defined task. For Insights Analytics, we need a preflight check for Enhanced Recurring Donations. It seemed obvious to build on the existing settings check.
As for introducing a separate check for custom settings, the idea was basically separation of concerns for custom settings objects. However, I agree with your point about simply extending the existing check.
Addressed in 8b1e10b229061969def43fd0db645d6d199c2f8e

@davisagli There isn't specific documentation for the need for this sort of check. In NPSP, there is a check for Enhanced Recurring Donations which (improperly) relies on a locally defined task. For Insights Analytics, we need a preflight check for Enhanced Recurring Donations. It seemed obvious to build on the existing settings check.
As for introducing a separate check for custom settings, the idea was basically separation of concerns for custom settings objects. However, I agree with your point about simply extending the existing check.
Addressed in 8b1e10b229061969def43fd0db645d6d199c2f8e


Add Trace level logging

It would be very convenient if logrus had a TRACE level. There are times when I want to differentiate between log messages indicating where I am in the program vs. the on the wire messages (which can be very large).

I added a PR https://github.com/sirupsen/logrus/pull/652 to help.

I noticed there have been no commits since mid-August.  Is there a roadmap of releases and if so, what can I do to get this feature (with completed PR) into that release?

Well, I think that the author is seeking assistance with this project as he has many other commitments. I guess that there is no concrete roadmap as a result.

IMO having lots of log levels (eg.: a trace level) is a bad idea.
I prefer turning detailed trace/debug logs on/off with specific switches (bool variable or something similar) only in specific parts of the application instead of controlling this with one global switch (loglevel) that turns on trace everywhere and makes a larger piece of software completely unusable and/or undebuggable.

I'm inclined to disagree @pasztorpisti and in fact how do you implement trace in sub-components if it's not supported at a higher level? I mean to get the functionality of trace, it sounds like you are using Debug.
Component level log levels sounds like a cool feature of your system and potentially even in a logging framework but the levels still need to be supported at a higher level.
To your point on creating unusable, undebuggable software. No, trace would only get turned on for short periods of time. In any case, when in the depths of a production level issue, I would much rather have a bunch of verbose trace statements than much less of debug, which can only lead to taking longer to solve the problem.

Either way, Logrus is an open project for people to use with different use cases. To add trace would be trivial and in doing so would be enriching the library and cater for a wider audience and requirement set. If you don't agree with the log level, don't use it.
Perhaps I am missing the point..?

@chackett I'm pretty sure there are programmers who think trace is a good idea (and have some use cases for it) but my guess is that these programmers are a minority. The majority of projects never use or need trace even when it's available. For this reason I treat trace as a narrow purpose feature.
A good library (open source or not) has a simple, unambiguous, focused interface that solves the most important problems.

Trace doesn't create ambiguity .. it's another log level, which is explained in most good articles that explain logging. :/

For what it is worth, the way I use trace (and IMO a great use case for it) is to create specialized loggers with a messaging library and log the wire format messages at trace level while logging other less interesting and verbose things (like the endpoints being hit) at debug level.  Being able to distinguish wireformat logs from less verbose, but still debug only messages is extremely valuable.

@chackett @xandrewrampulla
For me trace is just debug log. Many devs have a similar opinion - I guess their number is higher than average in the go community that often follows KISS principles. Here is an article explaining exactly what I think about trace:

I personally discourage the use of the TRACE/FINEST level (and I’m not alone, see for example here). I don’t see big difference between DEBUG and TRACE and it is usually difficult for the young team members to decide which one, DEBUG or TRACE, to use. Following the Kiss principle, I suggest to use ERROR, WARN, INFO and DEBUG levels only.

If we wanted to define a line between debug and trace based on verbosity: unfortunately it's subjective.
What happens if someone wants to differentiate 3 or 4 or more different debug log message categories, not only 2? Do we add another log level? (like log4j's fine, finest) In my opinion categorising debug log should be done in a different way, for example by adding a log field with different values: verbosity=1, verbosity=2, etc... and filter the log based on this field. I'd rather add an effective field-filtering mechanism than a new log level.
Filtering for multiple fields would make it possible to do interesting things like "subsystem=something level=debug verbosity=2"

solved by #844


Fix image component not visible in WATT's DE.

[Issue] https://github.com/Samsung/WATT/issues/114
[Problem] Image component not visible in WATT's DE
[Cause] When doing npm install for DE grunt task is executed
(contents/Gruntfile.js) which copies files from
dist/1.0.0/components
to
tau-component-packages/libs/closet
closet-component-packages/libs/closet
closet-component-packages/components
Version of image component located in dist/1.0.0/components
was not up-to-date
[Solution]
Update image component in src location
Remove unneeded files
Update .gitignore
Add lock.json files to repository
Signed-off-by: Lukasz Slachciak<EMAIL_ADDRESS>

@singa2000  this PR resolves also issue that some files are checked out when git status is executed

I just updated PR. Decided to fix only issue not doing additional improvements like committing packagelock.json files or removing unneeded directories due to the risk of regression


Python Workflow

Adds workflows for:

tests in Python with nox
tests in Rust
building the Python documentation

This raises another question - who do we say the author is? The individual(s), or the team, or the company? Do you already use a standard on the python side of things?

Yeah, we are using always the company for this, it is used for the copyright notice for example, so it should be the company for our projects.


Frontend: Enable two ports for HTTP and HTTPS

This issue relates to #268
Tornjak Frontend should support appropriate connection HTTP and HTTPS according to what Backend supports.
When TLS or mTLS enabled, HTTP should permanently redirect to HTTPS.

@mrsabath to test it


Add post release check to publish job on Travis

Migrated this job from Gitlab due to lack of chrome-headless
on our Gitlab images.
Resolves: OLPEDGE-2321
Signed-off-by: Yaroslav Stefinko<EMAIL_ADDRESS>

Codecov Report

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

@@             Coverage Diff             @@
##             master       #383   +/-   ##
===========================================
  Coverage   88.0983%   88.0983%
===========================================
  Files            72         72
  Lines          2403       2403
  Branches        264        264
===========================================
  Hits           2117       2117
  Misses          161        161
  Partials        125        125

Continue to review full report at Codecov.

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


Server-side with IIFE

If your .js is using the IIFE style ReactJS fail to load the component on the server depending on how the component is scoped
example using var or window fail
(function (){
var DivBox = React.createElement('div', null, 'Just a div')
}())
this will fail
but
(function (){
DivBox = React.createElement('div', null, 'Just a div')
}())
without var or window will work.
why this behavior ?

The documentation page on Webpack touches on this when using Webpack: http://reactjs.net/guides/webpack.html. Documentation for other module systems or "vanilla" IIFEs can be added in the future if we like. Closing this out. Thanks!


Saving the audio from the WebSocket stream in the backend

Hey, I've been trying to accumulate the samples sent through the JS websocket on a python server, but I cant figure out how to save it to a wav file.
when I save them and write to a wav file, the result is a very loud static noise.
I've tried using the np.frombuffer method as well as the utilities here.

there was a buffer mutation before np.frombuffer that I missed, the method is working properly.
closing the issue.


RBAC Problems with Concourse on GKE

Configuration:
k8s: 1.7.12-gke.0
Deployment: GKE
helm: v2.8.0
Error
I'm unable to deploy the 0.11 concourse helm chart on GKE due to RBAC security policies
concourse@builder:~$ helm install stable/concourse --name concourse -f concourse.yaml --version 0.11.0 --namespace concourse
Error: release concourse failed: roles.rbac.authorization.k8s.io "concourse-worker" is forbidden: attempt to grant extra privileges: [PolicyRule{Resources:["podsecuritypolicies"], ResourceNames:["privileged"], APIGroups:["extensions"], Verbs:["use"]}] user=&{system:serviceaccount:kube-system:default 7af9748c-00aa-11e8-a75c-42010a8000d4 [system:serviceaccounts system:serviceaccounts:kube-system system:authenticated] map[]} ownerrules=[PolicyRule{Resources:["selfsubjectaccessreviews"], APIGroups:["authorization.k8s.io"], Verbs:["create"]} PolicyRule{NonResourceURLs:["/api" "/api/*" "/apis" "/apis/*" "/healthz" "/swaggerapi" "/swaggerapi/*" "/version"], Verbs:["get"]}] ruleResolutionErrors=[]

I tried granting cluster-admin capabilities to my user but this also failed on GKE
concourse@builder:~$ kubectl create clusterrolebinding myname-cluster-admin-binding --clusterrole=cluster-admin<EMAIL_ADDRESS>Error from server (Forbidden): User "11266002853573390253" cannot create clusterrolebindings.rbac.authorization.k8s.io at the cluster scope.: "No policy matched.\nRequired \"container.clusterRoleBindings.create\" permission." (post clusterrolebindings.rbac.authorization.k8s.io)

I had to do something similar with https://github.com/flant/loghouse/issues/28#issuecomment-349274259 to fix the issue. The difference is that I needed to delete the deployment by hand too, as suggested by https://github.com/kubernetes/helm/issues/3130#issuecomment-345506262

Hey! We try to keep chart-related issues over at kubernetes/charts as this issue looks quite likely to be a chart-related bug than a bug in Helm itself. Would you mind opening this ticket over there? Thanks!


Use -strict-concurrency=off as the default for Swift 5.x mode.

Emulate the behavior of Swift 5.5/5.6 by default, using
-strict-concurrency=off.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Homee integration does not work properly with new Homee version 2.40.2 (with 2.40.1 it was working)

Type of problem

[x] I have a question.
[x] A feature does not work as expected.
[x] I found a bug (see error log below).

Version

Homee 2.40.2
HomeAssistant 2024.9.3
homee Plugin in HA 2.7.0
Detailed description
I was updating my Homee to the new version 2.40.2 Homee, HomeAssistant etc. was also restarted. I can see the devices but espacially the lights are all not working. Hopefully I sent you the correct part of the log. If anything else is needed please let me know
Error log

2024-09-27 07:15:11.379 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'homee' calls async_forward_entry_setup for integration, homee with title:<PHONE_NUMBER>C2 (<IP_ADDRESS>) and entry_id: 6533fad6f5fb57dad2b3d597e0983c2d, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/homee/__init__.py, line 145: hass.async_create_task(, please create a bug report at https://github.com/Taraman17/hacs-homee/issues
2024-09-27 07:15:11.748 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from waterkotte_heatpump, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'waterkotte_heatpump' custom integration
2024-09-27 07:15:12.121 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.homee.light.HomeeLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 19> and color modes, please create a bug report at https://github.com/Taraman17/hacs-homee/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-09-27 07:15:12.121 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.homee.light.HomeeLight'>) does not set supported color modes, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/Taraman17/hacs-homee/issues
2024-09-27 07:15:12.122 WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.homee.light.HomeeLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 19> and color modes, please create a bug report at https://github.com/Taraman17/hacs-homee/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-09-27 07:15:12.122 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.homee.light.HomeeLight'>) does not set supported color modes, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/Taraman17/hacs-homee/issues
2024-09-27 07:15:12.123 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration homee with title:<PHONE_NUMBER>C2 (<IP_ADDRESS>) and entry_id: 6533fad6f5fb57dad2b3d597e0983c2d, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2184, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-27 07:15:12.128 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration homee with title:<PHONE_NUMBER>C2 (<IP_ADDRESS>) and entry_id: 6533fad6f5fb57dad2b3d597e0983c2d, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2184, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-09-27 07:15:12.130 ERROR (MainThread) [homeassistant.components.binary_sensor] Error adding entity binary_sensor.turkontakt_terasse_opening for domain binary_sensor with platform homee
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 595, in _async_add_entities
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 909, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1366, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1069, in __async_calculate_state
    if state_attributes := self.state_attributes:
                           ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/homee/__init__.py", line 285, in state_attributes
    data = self._entity.__class__.__bases__[1].state_attributes.fget(self)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Hi,
you are using quite an old version of the homee integration there. Current one is 2.9.6.
At least the warnings logged there are fixed meanwhile.
Also the code referenced in the error message has changed till then.
So I assume, the error will be gone with the current version.

Hi,
you are using quite an old version of the homee integration there. Current one is 2.9.6. At least the warnings logged there are fixed meanwhile.
Also the code referenced in the error message has changed till then. So I assume, the error will be gone with the current version.

Thanks a lot. I dont know why (I was already on the "new" repo) but i never got an update shown up. I manually changed to the newest version in hacks and it worked!


[Backuport][BUG] Longhorn UI: XHR request URL sometimes wrong when UI is proxied

Backport fix from #3191 (longhorn/longhorn-ui@45144ea5eed2fc79eba728ffb2a33a11e87d28a7)

Validation - PASSED
Tested with latest v1.2.x images(ui: 742a5d7), the xhr/wss errors no longer shows.


Add Org files to the list of supported languages

This PR adds support to Org files.
This solution was originally reported on #126.

Any progress on this? Can the org file be use with this language server? 😖

Any progress on this? Can the org file be use with this language server? confounded

Yeah, it is staled.
I suggest you follow the instructions in the mentioned issue and change it locally for now.

Can we remove the file extension restrictions? The restriction doesn't make sense to me.


Update README.md

GitSecure Vulnerablility Report

Control ID
Section
Description

RA-5
Risk Assessment
Vulnerability Scanning

CA-7
Security Assessment and Authorization
Continuous Monitoring

SA-12
System and Services Acquisition
Supply Chain Protection

SI-2
System and Information Integrity
Flaw Remediation

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

   For Dockerfile: Dockerfile  Stage: shri4u/myapp-base:0.1

:white_check_mark: OS Packages Safe
:white_check_mark: Pip Packages Safe
Vulnerability Analysis
Vulnerable OS Packages
No vulnerable os packages found
Vulnerable Python Packages
No vulnerable pip packages found
Detailed Package Analysis
Contains vulnerability, license and pedigree information for each package

  OS Packages [Expand for more information]

  Python Packages [Expand for more information]

 Package Name: Django | Current Version: 1.2

Python Vulnerabilities:
No Vulnerabilities Present in this Pip Package
Compliance:
OSSC Compliant:
Last Reviewed License Version: Not Available
Pedigree Reviewed:
Last Reviewed Pedigree Version: Not Available

 Package Name: feedgen | Current Version: 0.8.0

Python Vulnerabilities:
No Vulnerabilities Present in this Pip Package
Compliance:
OSSC Compliant:
Last Reviewed License Version: Not Available
Pedigree Reviewed:
Last Reviewed Pedigree Version: Not Available

GitSecure Auto-remediation
  PR Created at:  https://github.com/cmadam/myapp/pull/37

GitSecure Bill of Material

Control ID
Section
Description

CM-8
Configuration Management
Information System Component Inventory

 Download Bill of Material Report: [JSON Format]

Docker CIS Community Edition 1.13

Control ID
Section
Description

CM-6
Configuration Management
Configuration Settings

CA-2
Security Assessment and Authorization
Security Assessments

Dockerfile: redis.yaml

ID
Rule
Compliant?

5.6
Ensure ssh is not run within containers
?

5.7
Ensure privileged ports are not mapped within containers
:heavy_check_mark:

5.8
Ensure only needed ports are open on the container
?

5.10
Ensure memory usage for container is limited
:x:

5.25
Ensure the container is restricted from acquiring additional privileges
?

5.26
Ensure container health is checked at runtime
?

5.4
Ensure privileged containers are not used
:heavy_check_mark:

5.16
Ensure the host's IPC namespace is not shared
:heavy_check_mark:

5.22
Ensure docker exec commands are not used with privileged option
?

5.27
Ensure docker commands always get the latest version of the image
?

5.5
Ensure sensitive host system directories are not mounted on containers
:heavy_check_mark:

5.30
Ensure the host's user namespaces is not shared
?

5.19
Ensure mount propagation mode is not set to shared
?

5.23
Ensure docker exec commands are not used with user option
?

5.28
Ensure PIDs cgroup limit is used
?

5.9
Ensure the host's network namespace is not shared
:heavy_check_mark:

5.3
Ensure Linux Kernel Capabilities are restricted within containers
:heavy_check_mark:

5.13
Ensure incoming container traffic is binded to a specific host interface
?

5.14
Ensure 'on-failure' container restart policy is set to '5'
?

5.15
Ensure the host's process namespace is not shared
:heavy_check_mark:

5.18
Ensure the default ulimit is overwritten at runtime, only if needed
?

5.24
Ensure cgroup usage is confirmed
?

5.2
Ensure SELinux security options are set, if applicable
?

5.11
Ensure CPU priority is set appropriately on the container
:heavy_check_mark:

5.21
Ensure the default seccomp profile is not Disabled
?

5.31
Ensure the Docker socket is not mounted inside any containers
:heavy_check_mark:

5.1
Ensure AppArmor Profile is Enabled
?

5.17
Ensure host devices are not directly exposed to containers
?

5.12
Ensure the container's root filesystem is mounted as read only
?

5.29
Ensure Docker's default bridge docker0 is not used
?

5.20
Ensure the host's UTS namespace is not shared
?

GitSecure Dockerfile Linter
Checks powered by Hadolint
Haolint is a smarter Dockerfile linter that helps you build best practice Docker images.

Control ID
Section
Description

SA-11 (1)
System and Services Acquisition
Developer Security Testing and Evaluation - Static Code Analysis

Dockefile : /Dockerfile

Line #
ID
Description

2
DL3008
Pin versions in apt get install. Instead of apt-get install <package> use apt-get install <package>=<version>

2
DL3009
Delete the apt-get lists after installing something

2
DL3015
Avoid additional packages by specifying --no-install-recommends

GitSecure Vulnerablility Report

Control ID
Section
Description

RA-5
Risk Assessment
Vulnerability Scanning

CA-7
Security Assessment and Authorization
Continuous Monitoring

SA-12
System and Services Acquisition
Supply Chain Protection

SI-2
System and Information Integrity
Flaw Remediation

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

   For Dockerfile: Dockerfile  Stage: shri4u/myapp-base:0.1

:white_check_mark: OS Packages Safe
:white_check_mark: Pip Packages Safe
Vulnerability Analysis
Vulnerable OS Packages
No vulnerable os packages found
Vulnerable Python Packages
No vulnerable pip packages found
Detailed Package Analysis
Contains vulnerability, license and pedigree information for each package

  OS Packages [Expand for more information]

  Python Packages [Expand for more information]

 Package Name: Django | Current Version: 1.2

Python Vulnerabilities:
No Vulnerabilities Present in this Pip Package
Compliance:
OSSC Compliant:
Last Reviewed License Version: Not Available
Pedigree Reviewed:
Last Reviewed Pedigree Version: Not Available

 Package Name: feedgen | Current Version: 0.8.0

Python Vulnerabilities:
No Vulnerabilities Present in this Pip Package
Compliance:
OSSC Compliant:
Last Reviewed License Version: Not Available
Pedigree Reviewed:
Last Reviewed Pedigree Version: Not Available

GitSecure Auto-remediation
  PR Created at:  https://github.com/cmadam/myapp/pull/38

Docker CIS Community Edition 1.13

Control ID
Section
Description

CM-6
Configuration Management
Configuration Settings

CA-2
Security Assessment and Authorization
Security Assessments

Dockerfile: redis.yaml

ID
Rule
Compliant?

5.6
Ensure ssh is not run within containers
?

5.7
Ensure privileged ports are not mapped within containers
:heavy_check_mark:

5.23
Ensure docker exec commands are not used with user option
?

5.21
Ensure the default seccomp profile is not Disabled
?

5.30
Ensure the host's user namespaces is not shared
?

5.8
Ensure only needed ports are open on the container
?

5.13
Ensure incoming container traffic is binded to a specific host interface
?

5.16
Ensure the host's IPC namespace is not shared
:heavy_check_mark:

5.4
Ensure privileged containers are not used
:heavy_check_mark:

5.12
Ensure the container's root filesystem is mounted as read only
?

5.24
Ensure cgroup usage is confirmed
?

5.29
Ensure Docker's default bridge docker0 is not used
?

5.2
Ensure SELinux security options are set, if applicable
?

5.14
Ensure 'on-failure' container restart policy is set to '5'
?

5.17
Ensure host devices are not directly exposed to containers
?

5.18
Ensure the default ulimit is overwritten at runtime, only if needed
?

5.22
Ensure docker exec commands are not used with privileged option
?

5.28
Ensure PIDs cgroup limit is used
?

5.1
Ensure AppArmor Profile is Enabled
?

5.5
Ensure sensitive host system directories are not mounted on containers
:heavy_check_mark:

5.9
Ensure the host's network namespace is not shared
:heavy_check_mark:

5.15
Ensure the host's process namespace is not shared
:heavy_check_mark:

5.26
Ensure container health is checked at runtime
?

5.27
Ensure docker commands always get the latest version of the image
?

5.3
Ensure Linux Kernel Capabilities are restricted within containers
:heavy_check_mark:

5.20
Ensure the host's UTS namespace is not shared
?

5.25
Ensure the container is restricted from acquiring additional privileges
?

5.31
Ensure the Docker socket is not mounted inside any containers
:heavy_check_mark:

5.10
Ensure memory usage for container is limited
:x:

5.11
Ensure CPU priority is set appropriately on the container
:heavy_check_mark:

5.19
Ensure mount propagation mode is not set to shared
?

GitSecure Bill of Material

Control ID
Section
Description

CM-8
Configuration Management
Information System Component Inventory

 Download Bill of Material Report: [JSON Format]

GitSecure Dockerfile Linter
Checks powered by Hadolint
Haolint is a smarter Dockerfile linter that helps you build best practice Docker images.

Control ID
Section
Description

SA-11 (1)
System and Services Acquisition
Developer Security Testing and Evaluation - Static Code Analysis

Dockefile : /Dockerfile

Line #
ID
Description

2
DL3008
Pin versions in apt get install. Instead of apt-get install <package> use apt-get install <package>=<version>

2
DL3009
Delete the apt-get lists after installing something

2
DL3015
Avoid additional packages by specifying --no-install-recommends

❌ GitSecure Open Source License Assessment: Needs Review
FedRAMP Controls covered:

Control ID
Section
Description

CM-7(5)
Configuration Management
Least Functionality - Authorized Software / Whitelisting

CM-10
Configuration Management
Software Usage Restrictions

CM-11
Configuration Management
User-Installed Software

CA-6
Security Assessment and Authorization
Security Authorization

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

❌ Python PackagesSelf-Certifiable Packages
enum34 version 1.1.6MarkupSafe version 1.1.1validators version 0.12.2Flask_Cors version 3.0.8python_dateutil version 2.8.1pytz version 2019.3visitor version 0.1.3zipp version 2.1.0wheel version 0.34.2Werkzeug version 0.16.1Jinja2 version 2.11.1Flask_API version 1.1WTForms version 2.2.1Flask_Bootstrap version <IP_ADDRESS>Mako version 1.0.7pathvalidate version 0.29.0decorator version 4.4.1Flask_WTF version 0.14.2MarkupSafe version 1.0itsdangerous version 1.1.0pyrsistent version 0.15.7aniso8601 version 8.0.0Flask version 1.1.1Flask_HTTPAuth version 3.3.0flask_nav version 0.6importlib_metadata version 1.5.0attrs version 19.3.0six version 1.14.0Click version 7.0Packages that Need Review
feedgen version 0.8.0lxml version 4.5.0setuptools version 45.1.0setuptools version 44.0.0Django version 1.2flask_restplus version 0.13.0dominate version 2.4.0jsonschema version 3.2.0pip version 20.0.2
Download Open Source Steering Committee (OSSC) Report: [JSON Format]  [HTML Format]


Can't type in Cmd+` in Keyboard Shortcut UI

Issue Type: Bug
Open Keyboard Shortcuts tab. Click to edit any. In the input try holding Cmd and press '`' key. It is not appearing in the input field.
Workaround: enter any non-existing combo (like shift-), then open Keyboard Shortcuts JSON and find that entry, replace string to "cmd+".
VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:42:05.236Z)
OS version: Darwin arm64 21.1.0
Restricted Mode: No

System Info

Item
Value

CPUs
Apple M1 Pro (8 x 24)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
32.00GB (0.08GB free)

Process Argv
--crash-reporter-id 7c274816-b412-4d9f-ad5b-d50b8a8f63bf

Screen Reader
no

VM
0%

Extensions (26)

Extension
Author (truncated)
Version

jest-snippets
and
1.8.0

csharpier-vscode
csh
1.2.1

xml
Dot
2.5.1

es7-react-js-snippets
dsz
4.4.3

gitlens
eam
12.0.5

prettier-vscode
esb
9.5.0

unity-code-snippets
kle
1.3.0

vscode-docker
ms-
1.21.0

csharp
ms-
1.24.3

vscode-kubernetes-tools
ms-
1.3.7

python
ms-
2022.4.0

vscode-pylance
ms-
2022.3.4

jupyter
ms-
2022.2.1030672458

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.6

remote-containers
ms-
0.231.3

vsliveshare
ms-
1.0.5449

vscode-yaml
red
1.6.0

html-to-jsx
ria
0.0.1

scala
sca
0.5.5

metals
sca
1.13.0

prettier-vscode
Sim
2.0.7

paste-clean-diff
siv
1.1.0

unity-debug
Uni
3.0.2

errorlens
use
3.4.2

propertylist
zho
0.0.2

/needsMoreInfo
Please follow steps from https://github.com/microsoft/vscode/wiki/Keybinding-Issues to check if VS Code receives this shortcut

/needsMoreInfo
Please follow steps from https://github.com/microsoft/vscode/wiki/Keybinding-Issues to check if VS Code receives this shortcut

Before I'll get lost in that manual page, I'd like to testify: the VS Code receives this shortcut as I specified in the workaround – I'm using this shortcut 'cmd+`' after I configured it via workaround :)
Please say if I do need to go through that manual to perform other checks, @IllusionMH

@aleksandr-vin cmd + ` is typically predefined on macos as a command to switch windows of the same application. To be able to use it in applications, you would need to remove it from the OS settings:

Have you removed it from there?

@alexdima thanks for that tip. I've checked: I don't have it removed from there and it works both in VS Code and in macOs.
So what I experience now:

When I have it configured in JSON, then it does work in VS Code in both versions: when removed (disabled) from System Preferences > Shortcuts > Keyboard and when enabled. By work I mean VS Code opens (and closes on next hit) Terminal when I hit `cmd + `` in VS Code.
When I have it configured in JSON, then I can't enter it in Keyboard Shortcuts (not JSON) in VS Code: it opens Terminal instead of putting the keystrokes in the input field. That behaviour is not affected by enabling/disabling it in System Preferences.
When I have it not configured in JSON (when I set different combo for Open Terminal command), then I can't enter it in Keyboard Shortcuts (not JSON) in VS Code: it just does register it only like cmd is pressed. That behavior is not affected by enabling/disabling it in System Preferences.

Hey @alexdima, this issue might need further attention.
@aleksandr-vin, you can help us out by closing this issue if the problem no longer exists, or adding more information.

OK, I think I have some idea towards what might be going on. The command View: Toggle Terminal (workbench.action.terminal.toggleTerminal) is rendered in the native macOS menu under View > Terminal.  Our menus respect the keybindings.json when rendering a keybinding next to the menu entries. So, when configuring:
{ "key": "cmd+`", "command": "workbench.action.terminal.toggleTerminal"}

This keybinding will be reflected in the native macOS menus (under View > Terminal):

As soon as a keybinding is displayed in the native macOS menu, it will be dispatched by the OS, and not by us. So, the OS now knows that we have a command bound to cmd + ` and when pressing cmd + ` the OS will behave as if the menu was clicked (on our side we just get to learn that the menu action was invoked). So we still don't receive the keybinding, the OS invokes the menu action for us. That is why the keyboard shortcut UI cannot log or capture the keybinding.
To sum up:

when configuring cmd + ` for workbench.action.terminal.toggleTerminal, it is shown in the menus
when pressing cmd + `, this keybinding will not reach us and the OS will invoke our menu action directly

I don't really know what would be the best way to improve things here. @deepak1556 Are you aware if there are native macOS APIs around the way menus are created that would give us some sort of setting to control this behavior?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Update GRT with the necessary custom hooks for editing content in gatewayEdit (useEdit custom hook)

Most likely an issue for @mannycolon

Should be able to test editing translation words and translation academy articles

Looks good in v1.0.0 build 1c04778.
Able to edit tW and tA articles. Working correctly as per the test notes in #263.


list of users with access to the webs is missing

@claratee that list was very hard to maintain from a technical perspective, so hence why I'm implementing an admin view that will allow us to see all the webs, with the team members etc. I'm closing this ticket in favour of that.


fix(e2e): remove keyvault tests from feature validation (for now)

What this PR does / why we need it:

we're removing keyvault tests while we refactor our e2e test runners and create necessary infra.
don't run e2e tests (four tests) when running on master branch as we run a full 24-set feature validation suite.
store e2e logs as test artifacts
use a different subscription for feature validation tests

This change is

@anhowe We just need to add them back. Dmitry and I looked at the Jenkins KV infra and decided we could temporarily remove KV feature tests while we setup the KV infra (we'll need to document the reproducible steps to do, currently a gap there). The work is prioritized: https://github.com/Azure/acs-engine/issues/1156

I'll approve this, but please assure me we have concurrent coverage in Jenkin's regression.

Regression tests remain unchanged, so as long as Jenkins is running they'll continue to test KV: https://github.com/Azure/acs-engine/blob/master/test/acse-conf/acse-regression.json


Parallel kanji fix

This allows Dmak to run multiple independent drawings in different elements.

Sorry, there was a bug in there


Ignoring strict-aliasing in client.cpp.

Compiles without warnings with gcc 4.9.2 and clang 3.5.

Please re-create without the old commits and merge
This seems a bit much, would it make more sense to disable the flag in CMake?

Creating a seperate pull request with only the changes to client.cpp. Closing this pull request.


Remove all unncessary fields in manifest.yml

Clean up manifest.yml to remove all unnecessary fields on it

https://github.com/jina-ai/executors/pull/207

This is done


Prevent an empty drawing panel in layer view

Case:
layer where we allow only delete  - as creation may come from a custom plugin.
Can we prevent layer editing panel from being created if the only entry is delete: true?
At the moment it's created empty.

actually hiding the panel would work

I made mistake to check whether cards array exist rather than checking the cards array length.
Should be fixed here.
https://github.com/GEOLYTIX/xyz/commit/7e94f801c9c9d09f6dc4e5cb15bf356e4f5f3350


Add complex example in README - Based on @danobot contribution

Hi @danobot ,
Following our discussion on: Patch now_is_between, I updated the readme.
What do you think of this?
Would this have been helpful if it were present in the readme when you first read it? Would you phrase it differently, implement the example in another way?

@danobot I'm merging this one. If you have any comment, feel free to share. We can always update to better reflect your original intent if that's needed ;)


Call benchmark specific cleanup() when there is exception

@ehankland PTAL. I've tested this by manually insert an exception in my benchmark run and validated all is cleaned up properly, here is an excerpt from the log:
2015-05-01 14:31:25,243 63d67cea MainThread object_storage_service(1/1) INFO
Running benchmark object_storage_service
2015-05-01 14:31:25,243 63d67cea MainThread object_storage_service(1/1) INFO
Start benchmarking object storage service, scenario is api_data, storage provid
er is Azure.

2015-05-01 14:31:25,243 63d67cea MainThread object_storage_service(1/1) ERROR
Error during benchmark object_storage_service
Traceback (most recent call last):
File "/usr/local/google/home/stfeng/github/PerfKitBenchmarker/perfkitbenchmark
er/pkb.py", line 271, in RunBenchmark
DoRunPhase(benchmark, benchmark_name, spec, collector, detailed_timer)
File "/usr/local/google/home/stfeng/github/PerfKitBenchmarker/perfkitbenchmark
er/pkb.py", line 205, in DoRunPhase
samples = benchmark.Run(spec)
File "/usr/local/google/home/stfeng/github/PerfKitBenchmarker/perfkitbenchmark
er/benchmarks/object_storage_service_benchmark.py", line 863, in Run
raise
TypeError: exceptions must be old-style classes or derived from BaseException, n
ot NoneType
<observe benchmark.cleanup() is called>
2015-05-01 14:31:25,244 63d67cea MainThread object_storage_service(1/1) INFO
Cleaning up benchmark object_storage_service
2015-05-01 14:31:25,245 63d67cea MainThread object_storage_service(1/1) INFO
Performing removal action, cmd is /scratch0/run/object_storage_api_tests.py --b
ucket=pkb63d67cea --storage_provider=AZURE  --scenario=CleanupBucket
<....>
And vms got deleted, etc, etc.

LGTM


Replace images with font icons on Button Group editing/reordering page

Trello task: https://trello.com/c/dNu0u279/153-8-replace-images-with-font-icons-in-forms
Before:

After:

Before:

After:

@epwinchell, @dclarizio can you review?

@miq-bot remove_label wip

@dclarizio Looks good

@miq-bot add_label enhancement


Autogenerate docs from existing READMEs

Syncing documentation manually is a tedious, error prone task.
Since we have Docusaurus with per-commit deployments it should be fairly straightforward to auto-sync all information from the READMEs.
Related: #593

Should we have a subset of READMEs that get synced with the docs? Deployment examples are 1:1 but quickstart is intentionally not 1:1 and takes advantage of mdx features.

Should we have a subset of READMEs that get synced with the docs? Deployment examples are 1:1 but quickstart is intentionally not 1:1 and takes advantage of mdx features.

SGTM. I think the most important thing at the moment is to have any sort of syncing at all. We can always exempt certain files if it makes more sense like that.

Fixed by

#1056


Role Permission Improvement

Use Role and permission not fully implemented.
Create permissions for viewing/editing/deleting each pipeline on all pages.
Group policy is not defined.
Ensure compatibility of Mage with Google SSO.

hey @dadmand can you elaborate on some of these requests?
what do you mean by group policy?
what issue are you running into with mage and google sso?


Please consider adding a LICENSE

Hi, this looks really good!
Is this an open source template? If so, then can you please add a compatible license?
Some more details on why open source projects should always have a license:
https://choosealicense.com/no-permission/

Yes also saw this, really cool stuff would love to use It if it had a license :)

MIT license added

MIT license added

Thanks @leoMirandaa


[JDK18] Correctly exclude StringBuilder/HugeCapacity

Excluding StringBuilder/HugeCapacity sub-tests does not work.
So, the StringBuilder/HugeCapacity changes in adoptium/aqa-tests#3211 have
been reverted.
The original StringBuilder/HugeCapacity exclude change has been re-added.
Signed-off-by: Babneet Singh<EMAIL_ADDRESS>

This addresses https://github.com/ibmruntimes/openj9-openjdk-jdk18/pull/5#issuecomment-1012651763.
Reviewers: @llxia @LongyuZhang
fyi: @pshipton


Logo transparency

As discussed in PM, after the screen artifact fix, the logo has developed that white transparency error again, where by background colours come through white areas of the logo, effects some images but not all! My cherry picker PNG logo (lol) for example, works ok.
Cosmetic only.
👍

Strange, Andrej has already fixed a similar problem before, I'll look at what he did to see if I broke it


Virtual field breaks searching

Link to reproduction
No response
Environment Info
Payload: v3.0.0-beta.110
Describe the Bug
Virtual field is used as search column which causes errors when searching in collection. Additionally, if such a field is used as "useAsTitle", it spoils the relationship search here: UI/Relationship
Reproduction Steps
Create collection like this:
{
  slug: 'students',
  admin: {
    useAsTitle: 'fullName',
  },
  fields: [
    {
      name: 'firstName',
      type: 'text',
    },
    {
      name: 'lastName',
      type: 'text',
    },
    {
      name: 'fullName',
      type: 'text',
      virtual: true,
      hooks: {
        afterRead: [
          (args) => {
            const { firstName, lastName } = args.siblingData
            return `${firstName} ${lastName}`
          }
        ]
      }
    },
  ],
}

Now searching in collection search is broken.
Adapters and Plugins
No response

Virtual fields aren't supposed to search by them. This PR https://github.com/payloadcms/payload/pull/8541 removes a field from the search list if it's virtual and used as useAsTtile.
Don't use virtual: true, if you care about filtering by it.


step to support HTTP Basic Auth

I'm going to vote for closing this since there isn't any development on this. The issue is still open.
https://github.com/brightcove/brine/issues/141

Up for me picking this up and writing tests?

@Lewiscowles1986 Sure, that would be great, thanks! Sorry for the late reply, this got slightly buried in my inbox.
As part of the initial PR it should likely have an entry in the Step Reference and appropriate specs. An article is planned/desired for more in-depth info for authentication pieces.

Yeah I got a bit lost in the specs using quoted strings.

Interesting issue.
I think it probably makes sense to shuffle the way the specs are executed around. The current approach of having one spec file which defines another one to run was I think borrowed from the Cucumber project, but the main files end up as mostly boilerplate. It probably makes more sense to change the way the tests are run so that the specs can just be what are currently the inner files which are all expected to pass. This should be a lot cleaner and will also likely make it easier to make the specs portable (rather than relying on or recreating potentially Ruby specific libraries like Aruba).
I'll see about swapping that over in the next day or so.


Feature: mini personal center with milestones

For now, users can only watch the collections, repository and developer analysis one by one. Although there is a feature allow them compare any two repositories at the same time. When repositories and collections achieve milestones, users are not immediately notified.
Potential Solution:
Create a mini personal center which gets the minimum login authorization from GitHub. Then users could login with their GitHub account without creating a new account for ossinsight. What can users do with personal center:
- Get personal analytics without searching by GitHub ID
- Get notification of repositories and collections when they achieve milestones
Design draft:

Keep it simple.

Update the design draft.

Could you please review this sketch？@Mini256

"this month" refers to which month, is the month of the current milestone or the current month when the user browses, the single repo analysis currently only supports data viewing in the current month when the user browses.

Today here will make people misunderstand.

What is the criterion for judgment of “Active"?

Does it mean that the repository acquired the 20,000th stars at this point in time, or did it acquire 2w stars in a certain time period?

"this month" refers to which month, is the month of the current milestone or the current month when the user browses, the single repo analysis currently only supports data viewing in the current month when the user browses.

Today here will make people misunderstand.

What is the criterion for judgment of “Active"?

Does it mean that the repository acquired the 20,000th stars at this point in time, or did it acquire 2w stars in a certain time period?

Thank you for re-checking my design.

'this month' here links to the contributor ranking in repository analyze page.

'today' will be replaced by the monthly date, like '2022-10' and the please see design draft here:

To measure whether a repository is 'active' , you can check whether it has contribution related events (commit, push code, review code, submit issue, etc.) . Note that the watch event needs to be excluded here.

It means this repo has reached 20,000+ stars in that day.

@sykp241095 @Mini256 @634750802 @CaitinChen PTAL～

I suggest that we first implement a separate page that does not require users to log in, the endpoint can be:
https://ossinsight.io/analyze/pingcap/tidb/milestones


Remove OpenSSL binary dependancy, use pure python RSA instead

There are a lot of pull requests open trying to fix ctypes for specific platforms.
As requested earlier, this patch gets rid of ctypes and linking in with the OpenSSL library directly and replaces it with a pure native python implementation of RSA - https://pypi.python.org/pypi/rsa
I've tested this on python versions 2.6, 2.7, 3.4 and 3.5.

I have this integrated into my repo here:
https://github.com/freimer/pychef

What are the advantages of this approach?

The biggest advantages are:

Reduces the number of external dependencies
This code is then able to run on any system or CPU architecture that has a python interpreter

I am attempting to maintain an active fork of pychef. I will attempt to pull this into my repo and verify it still works. I will update the MR here once done.


Compiling numba code failes on Ubuntu 16.04

numba.errors.LoweringError: Failed at nopython (nopython mode backend)
Buffer dtype cannot be buffer
File "hyperlearn/numba.py", line 126:
def squaresum(v):

s = v[0]**2
for i in prange(1,len(v)):
^
[1] During: lowering "id=6[LoopNest(index_variable = parfor_index.395, range = ($const28.2, $28.5, 1))]{44: <ir.Block at /home/lee/hyperlearn/hyperlearn/numba.py (126)>}Var(parfor_index.395, /home/lee/hyperlearn/hyperlearn/numba.py (126))" at /home/lee/hyperlearn/hyperlearn/numba.py (126)

Oh interesting. I'll check that. By the way I'll continue pushing commits more frequently by the end of this week.


brPop does not trigger when members appear in empty list

Using Redis->brPop in multi process mode (32 workers) started on two empty lists does not catch new ly appeared members in second list.
When script set is restarted after that situation, everything works fine (queue is being parsed normally).
This bug does not appeared on original Redis 3.2.11 (Debian 8 repo).

are u using latest code from git or just use the code in release?

The build was made on Feb 19 19:09 using the latest code at that moment.


Feature/2309/workflow entryname hosted and apps

Ticket: https://ucsc-cgl.atlassian.net/browse/DOCK-633
Fixing previous issues regarding handling HOSTED tools and workflows and DOCKSTORE_YML workflows.
Added integration tests.
Changes were very small, hiding whitespace will help.

Looks like there are some unexpected TravisCI errors, I'll remove reviewers until after fixing them.
Sorry for the email clutter.

FYI, this was mostly about trying out the various changes to the build, webservice (cache, rate limit behaviour)


Weight search index fields

Should I deploy to staging and run index-all to test?

Need to test after #733, to see what weights are necessary to fix it.

On staging:


[Release-0.18] Pin deps to release-0.18

The result is generated by running hack/update-deps.sh --upgrade

/assign @mattmoor
/assign @n3wscott

@ZhiminXiang this seems to have broken things

/lgtm
/approve


fix(extension): add navigation and title into the recieve drawer in the staking flow

Checklist

[x] https://input-output.atlassian.net/browse/LW-6440
[x] Proper tests implemented
[x] Screenshots added.

Proposed solution
Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.
Testing
pass proper values into the setDrawerConfig util.
Screenshots

Allure report
allure-report-publisher generated test report!

smokeTests: ✅ test report for dea9a3f2

passed
failed
skipped
flaky
total
result

Total
19
0
0
0
19
✅

testing


[APIView GPT] Investigate having GPT generate linter rules

Deterministic linter rules are much cheaper to run than ChatGPT. We should investigate how successful ChatGPT is at generating linter rules. If a linter rule can be generated, we should ensure that the GPT reviewer runs the linter rather than querying ChatGPT

Experiment 1
Prompt
This is what a client class looks like
class Foo:

  def __init__(self, credential, **kwargs)

  def get_foo(self, *args, **kwargs)

  def list_foos(self, *args, **kwargs)

  def delete_foo(self, *args, **kwargs)

  def update_foo(self, *args, **kwargs)

  def create_foo(self, *args, **kwargs)

This is what a model class looks like
class Bar:

  ivar name: str
  ivar age: int
  ivar desc: str

  def __init__(self, name: str, age: int, desc: str)

Given the above, write me python code that accepts a code snippet as a string and decides whether the code describes a client or a model class.
Result
Here's a simple Python script that uses the ast module to parse the code and determine whether it describes a client or a model class. This script assumes that a client class has methods like get_, list_, delete_, update_, and create_, while a model class has instance variables and an init method.
import ast

def classify_code(code):
    tree = ast.parse(code)
    class_node = tree.body[0]  # assuming the class is the first statement in the code

    if isinstance(class_node, ast.ClassDef):
        methods = [node.name for node in class_node.body if isinstance(node, ast.FunctionDef)]
        attributes = [node.targets[0].id for node in class_node.body if isinstance(node, ast.Assign)]

        if any(method.startswith(('get_', 'list_', 'delete_', 'update_', 'create_')) for method in methods):
            return 'Client class'
        elif attributes and '__init__' in methods:
            return 'Model class'

    return 'Unknown'

# Test the function
client_class_code = """
class Foo:
    def __init__(self, credential, **kwargs):
        pass
    def get_foo(self, *args, **kwargs):
        pass
"""

model_class_code = """
class Bar:
    name: str
    age: int
    desc: str
    def __init__(self, name: str, age: int, desc: str):
        pass
"""

print(classify_code(client_class_code))  # prints: Client class
print(classify_code(model_class_code))  # prints: Model class

This script is a very basic classifier and might not work correctly for all possible Python classes. For a more robust solution, you might want to use a Python parsing library that can handle more complex syntax and provide more detailed information about the code structure.


Add crate: Rustacuda

Please add crate to category: GPU Computing
Pro-tip: a quick PR to _data/crates.yaml often gets merged quicker.
https://github.com/bheisler/RustaCUDA

Added via #61


How can I start/stop my rig through automation in Home Assistant?

Is it a device, service or something else in the actions? I have a trigger. I can't figure out what to fire. Sorry, a bit new to Home Assistant.

Or is it this (a service)

Bump

Also interested to know

I was able to get automation bumping the power mode when my solar is exporting excess energy to the grid. I have one in reverse too for when there's no longer any surplus, setting power mode to LOW. But as far as I can tell there is no complete START/STOP

I got it to work with a service > switch, then added the entities...
Issue is though that NH on my PC seems to lock up and become unresponsive after an API start, followed by an API stop. I can't even start/stop in the desktop app. I couldn't even exit it at one point and had to reboot my PC.

I can't find the switches in list of entities. Am I possibly missing something important?

I can't find the switches in list of entities. Am I possibly missing something important?

In automation add a Service. In services add a Switch. In Switch add the Nicehash Entity.

I can't find the switches in list of entities. Am I possibly missing something important?

In automation add a Service. In services add a Switch. In Switch add the Nicehash Entity.

Like I tried telling above, I can't find the Nicehash switches as Entities.
Here is a complete list of all switch entities that can be selected and they are not either shown in Devicese _& Servicec entity list

@jseppeli have you installed this integration per the instructions via HACS?

@old-square-eyes yes and I have even checked that API has the same permissions as in the instructions

Hi. Is there a follow up here? I'm exactly at this pojnt as well. Cannot find the switches.  Did you get it to work?

Hi. Is there a follow up here? I'm exactly at this pojnt as well. Cannot find the switches. Did you get it to work?

No, never got it working

@jseppeli @eavogels
Do get the Power Switches you've to do a change at the switch.py File in custom_components/nicehash.
Changes that have to be done are listed here:
https://github.com/RomRider/ha_nicehash/compare/master...RoaringSon:ha_nicehash:master


Update unguarded-action-lib.ql to catch uses of actions-util.ts

I'm not 100% sure this change is correct but the PR checks should tell us as this should introduce at least one alert because it'll now spot accesses of actions-util.ts. Because it's using matches but then with a string with no wildcards in it I'm assuming this must be a mistake.
Alternatively we could probably just use getImportedPath().getValue() = "./actions-util") since we currently have all our source in one directory. Is that better? Using matches lets us catch this potential future edge case.
Merge / deployment checklist

[x] Confirm this change is backwards compatible with existing workflows.
[x] Confirm the readme has been updated if necessary.
[x] Confirm the changelog has been updated if necessary.

Thanks for the fix. It's not showing any new alerts. Is that expected?

It's not showing any new alerts. Is that expected?

I was hoping this would generate a new alert. I think that it should be catching the import of setMode in runner.ts should be triggering an alert. I made this PR just off a hunch but probably someone will need to try the query out locally to work it why it's not catching that. Unless of course I'm mistaken and you think that shouldn't be an alert.

Actually, I think the reason is that you based this change on main, but the offending code was still in a PR. When I rebased #539 on main, I started seeing the warning.

Ah thanks for working that out. That makes perfect sense.


EOL style per platform

I made a change to select the end-of-line code depending on the platform type.
The patch also fixed the typo of '\n' in the session support string and package.json, which was apparently fixed in the 2.x branch.
Thank you.

cool thanks


One setInterval to rule them all?

Hi there,
I guess one interval timer is spun per component.
Is it reasonable to think we could have a way to have a mutual timer?
On a page with 200 items refreshed at the same time, there is no much point of having 200 timers but rather one which triggers 200 updates. Or not – if it's not performance compliant.
What do you think?

Sounds very sensible :-)
Could you put together a PR for this?
On Tue, Nov 3, 2015 at 9:08 AM Thomas Parisot<EMAIL_ADDRESS>wrote:

Hi there,
I guess one interval timer is spun per component.
Is it reasonable to think we could have a way to have a mutual timer?
On a page with 200 items refreshed at the same time, there is no much
point of having 200 timers but rather one which triggers 200 updates. Or
not.
What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/KyleAMathews/react-autoupdate-time/issues/4.


improved release pipeline

LGTM
Could you share the link for eim_gui_release.json to check ? I could also use it to populate download from vscode extension options.

https://dl.espressif.com/dl/eim/index.html
https://dl.espressif.com/dl/eim/eim_gui_release.json
https://dl.espressif.com/dl/eim/eim_cli_release.json


Two websites in one

I was wondering to know if I can create an external website for a project made with hugo and how to mix it with my own website also made with hugo. So people can access for instance: mywebsite.com and mywebsite.com/projectx.

You can use GitHub pages to do that.

There are two approaches for this:

generate your two public folders by running Hugo on each of your websites, rename one to projectx and put it in your main public folder
or deploy to two separate places and redirect mywebsite.com/projectx to the appropriate URL (Netlify has options to easily configure this)

If you need further support, please reach out to whoever you are deploying with (Github Pages, Netlify etc.) or Hugo support forums.


Investigate: Sentry technical issues that could affect a user's completion of level 1

User Story
As a developer and Product Owner,
I want to view the Sentry reports to see if there are any large spikes of issues that might be causing interference with progression to completing the first level and document them as task cards,
So that we begin investigating other avenues besides just UX that might be impacting engagement.
Acceptance Criteria
Given that I have access to Sentry,
When I view the reports,
Then I should note any trends of things we might want to investigate technically and document them as a new task card for a future sprint.

Hi @burrage, when i try to login Sentry to check reports, it says that membership has to be upgraded

Thanks for letting me know @rakshith-arch . See Slack channel for further details!

Sure @burrage thank you!

Hi @burrage @jeffoberlander , i have shared a report, for issues in the sentry.

@rakshith-arch What's the timeframe of this report?
If the only issue that's sticking out is only affecting 6 users out of the 92,000+ active users we have that's phenomenal.

Moving it to Done as per internal discussion during sprint planning


Deploy Checklist: New Expensify 2021-09-28

Release Version: 1.1.3-1
Compare Changes: https://github.com/Expensify/App/compare/production...staging
This release contains changes from the following pull requests:

[x] https://github.com/Expensify/App/pull/5255
[x] https://github.com/Expensify/App/pull/5302
[x] https://github.com/Expensify/App/pull/5417
[x] https://github.com/Expensify/App/pull/5473
[x] https://github.com/Expensify/App/pull/5485
[x] https://github.com/Expensify/App/pull/5495
[x] https://github.com/Expensify/App/pull/5501
[x] https://github.com/Expensify/App/pull/5513
[x] https://github.com/Expensify/App/pull/5515
[x] https://github.com/Expensify/App/pull/5517
[x] https://github.com/Expensify/App/pull/5524
[x] https://github.com/Expensify/App/pull/5535
[x] https://github.com/Expensify/App/pull/5540
[x] https://github.com/Expensify/App/pull/5558
[x] https://github.com/Expensify/App/pull/5584

Deploy Blockers:

[x] https://github.com/Expensify/App/issues/5580

cc @Expensify/applauseleads

Starting QA

Regression is finished!
Issues found:

https://github.com/Expensify/App/issues/5580
https://github.com/Expensify/App/issues/5577
https://github.com/Expensify/App/issues/5579

PRs are finished too.

https://github.com/Expensify/App/issues/5580 is failing https://github.com/Expensify/App/pull/5255

Thanks!

Retest of https://github.com/Expensify/App/issues/5580 is a pass!
Checking off:

https://github.com/Expensify/App/issues/5580
https://github.com/Expensify/App/pull/5584
https://github.com/Expensify/App/pull/5255

Nice! Closing this to trigger the deploy.

This issue either has unchecked QA steps or has not yet been marked with the :shipit: emoji of approval.
Reopening!

:shipit:


#47 - terraform 1.2.8 breaks without SA removal - critical fix

see full clean org testing in #47

Summary: the unsupported argument error - is an expected result of an API change
Fix is usually to adapt the module or inherit the variable - here is is just to remove the reference in projects.tf
admin_@cloudshell:~/cloudshell_open/accelerators_accelerateurs-gcp/deployment-templates/Terraform/guardrails/1-guardrails (ggz-seed-project)$ terraform apply -var-file variables.tfvar
╷
│ Error: Unsupported argument
│
│   on projects.tf line 5, in module "administration":
│    5:   impersonate_service_account = var.terraform_service_account
│
│ An argument named "impersonate_service_account" is not expected here.


CLN: Remote Datetime-like Index.array_finalize

I understand these are never used because Index is no longer the subclass of np.array. Correct?

yep I think you could take them out. as np.array(index) will coerce to a ndarray (and not an index sub-class). This is done by _shallow_copy in any event.

No, we need this. Otherwise np.sin(idx) returns an ndarray.
It's not documented, but __array_finalize__ works even on non-subclasses.

ok let's add some tests and clean up the code
I suspect this should be in core/base then
eg to support the example above

IIRC there is another issue where for example:
In [22]: np.sin(Index(range(5)))
Out[22]: Int64Index([0.0, 0.841470984808, 0.909297426826, 0.14112000806, -0.756802495308], dtype='float64')

which is wrong, this needs to be created w/o slightly differently, e.g.
Index(func(...), **self._get_attributes_dict())

so that the attributes get propogates AND the correct type gets inferred (e.g. this would return a FloatI64Index in this case)

Thanks. I'll fix Index.__array_wraps__ to make ufunc work.
https://github.com/pydata/pandas/blob/master/pandas/core/index.py#L253
Am I correct that defining __array_finalize__ is not needed if __array_wraps__ is defined? Looks __array_finalize__ is not defined in normal Index.
http://docs.scipy.org/doc/numpy/reference/arrays.classes.html

This is correct -- array_wraps is what we need.
On Tue, Jul 21, 2015 at 5:44 AM, Sinhrks<EMAIL_ADDRESS>wrote:

Thanks. I'll fix Index.__array_wraps__ to make ufunc work.
https://github.com/pydata/pandas/blob/master/pandas/core/index.py#L253
Am I correct that defining __array_finalize__ is not needed if __array_wraps__ is defined? Looks __array_finalize__ is not defined in normal Index.
http://docs.scipy.org/doc/numpy/reference/arrays.classes.html
Reply to this email directly or view it on GitHub:
https://github.com/pydata/pandas/pull/10638#issuecomment-123293039

Let me confirm 2 points:

Invalid ops for datetime-like indexes.

I understand numeric ufuncs (like np.sin) for datetime-like is almost meaningless. PeriodIndex is likely to return unexpected result because of current __array__ definition. One idea is to raise error when PeriodIndex get float (invalid) result.
import pandas as pd

# OK
np.sin(pd.DatetimeIndex(['2015-07', '2015-08']))
# TypeError: ufunc 'sin' not supported for the input types, and the inputs could not be safely coerced to   any supported types according to the casting rule ''safe''

# NG
pidx = pd.PeriodIndex(['2015-07', '2015-08'], freq='M')
np.sin(pidx)
# Float64Index([-0.594884318359, 0.354966539136], dtype='float64')

# ufunc is applied to i8 values
pidx.__array__()
# array([546, 547])

Some ufunc returns bool dtype. In such cases, it should return bool array as it is (like Index.duplicated)

np.isnan(pidx)
# Index([False, False], dtype='object')

@sinhrks both of those points look right

Yes, agreed
On Thu, Jul 23, 2015 at 4:14 AM, jreback<EMAIL_ADDRESS>wrote:

@sinhrks both of those points look right
Reply to this email directly or view it on GitHub:
https://github.com/pydata/pandas/pull/10638#issuecomment-124060978

@sinhrks you might want to steal tests from #9974

@sinhrks how's this coming along?

@sinhrks how's this coming?

@sinhrks if you can get to this in the next couple of days gr8, otherwise will defer this.

I've looked through _add_numeric_operations. You mean to define PeriodIndex.sin and so on used by np.sin and raise error?

@sinhrks I think PeriodIndex needs to override __array_wrap__. and raise if context is not None (I think). This is the return call from a ufunc type of operation, so it will 'succed' but we should raise an error. I don't know if their is a way to intercept it up front (their is if you are sub-class I think), but not sure about a duck-like

@jreback Thanks, will check this.

Updated and now green.

this doesn't seeem to close #9966 ?
In [9]: df = pd.DataFrame({'i': np.linspace(0, 5, 6).astype(np.int64),
               'j': np.linspace(2, 3, 6)}).set_index('i')

In [10]: df
Out[10]:
     j
i
0  2.0
1  2.2
2  2.4
3  2.6
4  2.8
5  3.0

In [11]: df.index
Out[11]: Int64Index([0, 1, 2, 3, 4, 5], dtype='int64', name=u'i')

In [12]: df.index = df.index / 10.

In [13]: df.index
Out[13]: Int64Index([0.0, 0.1, 0.2, 0.3, 0.4, 0.5], dtype='float64', name=u'i')

@jreback Standard arithmetic is handled by _numeric_binop. Now fixed.
df.index / 2.
# Float64Index([0.0, 0.5, 1.0, 1.5, 2.0, 2.5], dtype='float64', name=u'i')

np.divide(df.index, 2.)
# Float64Index([0.0, 0.5, 1.0, 1.5, 2.0, 2.5], dtype='float64', name=u'i')

Failed in Timedelta ops. On current master, mult and div doesn't affect to existing freq, but it should?
import pandas as pd
idx = pd.timedelta_range('2 days', periods=3, freq='2D')

idx * 2
# TimedeltaIndex(['4 days', '8 days', '12 days'], dtype='timedelta64[ns]', freq='2D')
# -> freq should be "4D"?

idx / 2
# TimedeltaIndex(['1 days', '2 days', '3 days'], dtype='timedelta64[ns]', freq='2D')
# -> freq should be "D"?

@sinhrks hmm I think you need to set the freq=None so it get's reinferred (or maybe can et it to 'infer')

@sinhrks thanks!


refactor: remove all uses of unsafe code in ic-certified-map

This change removes all uses of unsafe Rust by replacing raw pointers
to nodes with Option<Box<Node>>.
The behavior of the RbTree is not changed.

This is the same PR as https://github.com/dfinity/cdk-rs/pull/134, I had to create a new one because the CI has issues with forks.


Wrong image in Kerberos Section

The wrong image is captured at this step
https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/akamai-tutorial#step-3-configure-delegation
It is a duplication of the image from step 2.

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

ID: db7ee04d-5eda-eb78-0063-cbe60c380674
Version Independent ID: b3d0b1e3-0cb1-2744-b520-fd54799fc1d7
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with Akamai
Content Source: articles/active-directory/saas-apps/akamai-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

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


Removing leading backslash from array instances

Rationale: The IEEE1800 doc says that the leading backslash is not part of the identifier, just a way to write the identifier in source code.
Note: I had to hack regression.tcl since for some reason it was not stripping my local run directory properly.

We should remove the trailing space too?

Yes, pushed.


mgmt, prepare release 2.39.0

Description
reverted core-test unreleased version in https://github.com/Azure/azure-sdk-for-java/compare/main...release/azure-resourcemanager/2.39.0
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

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


cleanup CHANGELOG

This project uses semver, please check the scope of this pr:

[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Updated cleaned up CHANGELOG.md

👍  self merging - I just cleaned up the CHANGELOG so we will have a fresh start.

👍

I don't think pull-approve picks up the 👍 if it's not the only thing in the comment 😞

👍


Resource-as-argument implicitly passed as string

Bicep version
0.4.1272
Describe the bug
When passing resource into a module as-is, is implicitly transformed to resourceId and does not yield type error.
To Reproduce

demo.bicep

param location string = 'bar'

resource appInsights 'Microsoft.Insights/components@2020-02-02' = {
  name: 'foo'
  location: location
  kind: 'other'
}

module module 'appInsights.bicep' = {
  name: 'my-module'
  params: {
    appInsightsResource: appInsights
  }
}

appInsights.bicep

param appInsightsResource object
output resId string = appInsightsResource.id

Output

"parameters": {
    "appInsightsResource": {
        "value": "[resourceId('Microsoft.Insights/components', 'foo')]"
    }
}

The actual parameter is a string and this is not errored-out by Bicep about type mismatch.
Additional context
Passing a resource as a param is equivalent to passing appInsightsResource: appInsights.id (from the above example), which correctly triggers type-mismatch.

Should the value be reference(resourceId('Microsoft.Insights/components', 'foo'))?


Jio tv 2.3.8 error

Jio tv installation failed in my smart tv in kodi 20.1 version 2.3.7 was not working also please give me solution

Same error, non of the channels are playing

Clean installation helped, just wiped data of Kodi and reinstalled the addon, working fine now

Botallean add source code


HoloLens(1st) Cannot Load Map

This project can run well in Unity(2018.3.7f),but it cannot load map in HoloLens(1st).
Target Sdk Version: 18362 ,Min Sdk Version: 10240. Scripting Backend:IL2CPP

Hello, thanks for reporting!
I've been unable to reproduce this using 2018.3.7, IL2CPP backend, target/min of 1836/10240, using HoloLens 1 (OS version 17763.380).
I used the WeatherCube sample scene to confirm the map data is loading.
Ensure you have supplied the Bing Maps developer key on the MapRenderer in the scene, and ensure you have an active internet connection on the HoloLen, Both would be required to stream the map data.
To further investigate, feel free to share the UnityPlayer log which can be pulled off the HoloLens using the device portal's file explorer. Check the LocalAppData folder and under the corresponding app folder, there should be a TempState folder with a UnityPlayer.log.

Please reopen if the map is still not loading.


Add support for Linux host

We're currently limited to Windows host because I was lazy to write the clang shim batch file in Bash.
https://github.com/MichalStrehovsky/PublishAotCross/blob/8fbc8fad1c943228c191c998d3995e5d300f7741/src/clang.cmd#L1-L26
Windows host is also guarded here:
https://github.com/MichalStrehovsky/PublishAotCross/blob/8fbc8fad1c943228c191c998d3995e5d300f7741/src/PublishAotCross.targets#L4

I managed to get Linux to Windows cross-compilation working via msvc-wine; may I file a PR for that?
demo: https://github.com/scgm0/NativeAotTest


Plans for CodeGeneration for Serializer, WebServices, CodeDom

What are the plans for generating code for serializers, CodeDom etc?
Will there be no generation support (like I think it is in MonoTouch) and generating will only be possible if you generate the code already before compilation?

Yes Reflection.Emit related APIs like the C# compiler. But more like for Generating Implementations for Interfaces/Abstract classes, less for performance optimizations.
The Code should be used on server side (where performance optimizations using Reflection.Emit like APIs make sense) and (Javascript) Client Side (Where as you stated, it does not make sense for javascript).
One option I thought of is sending the instructions for generating the code to the server, which compiles a DLL (using for example the C# Compiler), which is then again downloaded by the blazor runtime.
Is there yet an option to load DLLs Just in Time? I saw the Blazor Runtime currently uses the Method to compile the .NET DLLs on the Client to WebAssembly Files.
Otherwiese I would try to solve it by AoT-Compilation and without Performance optimizations using Code Generation.
I will also ask the mono team :) Thank you for the answer.


optional new

I'm using vim-lsc with dart_language_server and flutter. How can I get the dart_language_server to no longer highlight usages of constructors that omit the new keyword? new is optional in Dart 2 and my code compiles and runs successfully.

Was using old dart sdk

Sorry I didn't respond sooner - glad you were able to get it worked out.


Make Work in Progress outgoing CL's (with comments) not count as requiring my attention

My use case is:

Someone leaves a bunch of comments.
I decide that I need to reconsider the approach or do some other things before continuing the review. I mark the change as "work in progress".

After this the CL doesn't really need my attention.

If you just upload a CL and forget to assign reviewers, the default status is not WIP, is it?

The default (git push origin HEAD:refs/for/master) is not WIP, but some teams build wrapper scripts to upload CLs, and those wrapper scripts might pass the WIP option to the Gerrit backend. Ex. Chromium's git cl upload script uses the WIP option but Android's repo upload does not.

Given this plugin is not chromium-specific, could we make the behavior not chromium-specific?

I would love a configuration option. I often have 10+ CLs marked as WIP that I don't intend to send out for review yet, and it would be great if I could make them not appear in the plugin.

My pull request #21 should fix this.

I've merged pull request #21 and published a new version on the Chrome store. This is going to be called version 1.0.8. Due to the current global situation, the review may take some time (up to 30 days), so I don't really know when the version is going to be available.
Once the new version become available, could you tell whether this is an improvement for you?

If the gerrit server has attention set, then I would suggest it should just follow that. That would allow user to turn off notifications by removing themselves from the attention set in gerrit. However it seems that even with "Only use Attention Set to judge required attention" is enabled, Gerrit Monitor currently notifies for cases beyond attention set - for example approved #43 and new CLs #42.