How to build the link for polymorphic files?

Since the files are saved in different folder, how can I build the link based on the information saved on database?
The documentation doesn't have anything about it.
Could anyone give an example?

echo $this->Html->image('../files/Model/field/' . $data['Image']['image_dir'] . '/' . $data['Image']['image']);

Where $data is the data from your database for that image. This is why you store the dir in your database. In the example above I have used image as my upload field and image_dir as my dir field.


update schedule section of cookiecutter

As per this commen from #39

Just copying over the comment from @JessicaS11:
@lsetiawan in my most recent commit I intentionally broke the cookiecutter/splash page by adding a few items to the book/schedule.yaml that aren't currently parsed by the cookiecutter. Would you be able to take on making some changes to the cookiecutter index?

[ ] make location optional (ideal for virtual events)
[ ] add a note to the top of the schedule about the timezone (you can just use the one from book/schedule.md for an example, which includes an "in-your-timezone" link); I added a timezone block to the yaml to start this.
[ ] add an optional video block (or even more generic a resource that allows for a title and url, so it can be used for videos or slides)
[ ] tell me how (assuming it's possible) to include a list of items in a description, since that's often a great visual way to list a few objectives for a given session

Alternatively, if you'd like to recommend an approach that is not me trying to brute-force, manually write and format html correctly I'd be willing to try and work on some of these. : )

@JessicaS11 I won't have time today to look over this. But I will check it out tomorrow! I think I understand what you're asking. Shouldn't be to difficult 👍🏽

@JessicaS11 I got all your requested features I think. Let me know if I missed anything. Also please help on the build 😭

Thanks @lsetiawan - this looks great (I am quite satisfied)! It builds fine for me locally, so let's see what GH has to say.

Anyone know why the "this branch is out of sync with the base" button isn't showing up? Sure I can merge manually, but that button is mighty handy...

Anyone know why the "this branch is out of sync with the base"

Not sure, but if you can merge the current main branch in that would be great!

Anyone know why the "this branch is out of sync with the base"

Not sure, but if you can merge the current main branch in that would be great!

Far fetched guess is that there might be a merge conflict, which needs be resolved locally and hence no button here?

Oops 🙊 hopefully that didn't mess anything up... I pressed the update branch button thing! Sorry!

Oops 🙊 hopefully that didn't mess anything up... I pressed the update branch button thing! Sorry!

Perfect! I was lamenting the lack of update branch button!

Jessica, after editing the environment.yml there needs to be an update to the .lock files.
Execute the lock-environment.sh script and commit the changes. Note, that you need to be inside the conda folder when executing.


Windows Scaling Support

Windows has the concept of scaling:

Which scales everything up, such that a high-resolution screen can be scaled to see things more clearly.
Since revery isn't currently respecting that, apps can look very different since they aren't scaled the same way that most other apps are.
It looks like GLFW 3.3 has more reliable ways of picking up DPI settings, so this should help here.
We should update GLFW, then investigate if any further updates are needed.
For reference, here is Oni2 on a 4K screen at 150% scaling:

I have the same issue on Linux with SwayWM (wayland). Except that Sway will attempt to scale the app, so it's not too small, but fonts are quite blurry.

With the latest SDL2 work - we should have this fixed in Windows. We exposed a new API to get the Win32 scale factor, and pick that up in our scaling - so once this PR is in: https://github.com/revery-ui/revery/pull/555 - the situation on Windows should be improved.
We're also trying to have better behavior on Linux - by respecting the GDK_SCALE environment variable, and falling back to measuring DPI otherwise.

I think the bulk of this can be considered complete now, and any follow up tasks can probably go under a less general issue.


Master to Live

Docs Build status updates of commit 5300df9:
:clock10: Full build: the average full build time is 11 min(s) 55 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 5300df9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/advanced-threat-protection/New-AntiPhishPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/antispam-antimalware/Get-QuarantineMessage.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/antispam-antimalware/New-MalwareFilterPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/antispam-antimalware/Set-MalwareFilterPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mail-flow/Get-MessageTrace.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/sharing-and-collaboration/Get-PublicFolderItemStatistics.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/sharepoint-ps/sharepoint-online/ConvertTo-SPOMigrationTargetedPackage.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOTenantServicePrincipal.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteScriptFromWeb.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTheme.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBrowserIdleSignOut.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBuiltInDesignPackageVisibility.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHideDefaultThemes.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHomeSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOStorageEntity.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOWebTheme.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUnifiedGroupMove.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Stop-SPOSiteContentMove.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Update-SPODataEncryptionPolicy.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Update-UserType.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHealthScore.md
:white_check_mark:Succeeded
View (sharepoint-ps)

skype/skype-ps/skype/New-CsOnlinePSTNGateway.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlinePSTNGateway.md
:white_check_mark:Succeeded
View (skype-ps)

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


KAFKA-6042: Avoid deadlock between two groups with delayed operations

@ijuma @hachikuji Can you review please? I was trying to avoid changing group/txnMetadata locking last time,  but that was a mistake. This goes back to the previous way of overriding locks, but with ReentrantLock.

@rajinisivaram Hmm.. Do we need to update DelayedHeartbeat also to use the group lock as the operation lock.

@hachikuji I updated DelayedHeartbeat to use group lock and DelayedTxnMarker to use state lock. Also added comments in GroupCoordinator and TransactionStateManager. Can you take another look? Thank you!

The updates look good to me. I'll wait for @guozhangwang to take a second look before merging.

@guozhangwang The PR fixes deadlocks in both group coordinator and transaction manager. For groups, the group lock is now used as the delayed operation lock . The deadlock reported was exactly as you described. Now, when offset commit  request for groupA tries to complete groupB, the completion is performed if and only if it is able to acquire groupB lock (using tryLock). And similarly for groupB completing groupA. So we may acquire two group locks in any order, but the cycle is broken by tryLock, preventing deadlock.

please retest this

retest this please

And similarly for groupB completing groupA. So we may acquire two group locks in any order, but the cycle is broken by tryLock, preventing deadlock.

Thanks for the explanation. LGTM.

The jenkins failures seem un-related. I'm going to merge to trunk and 1.0.

Merged to 1.0, and cherry-picked to trunk.

@ijuma @hachikuji @guozhangwang Hi, I wonder if this patch can completely solve this problem. Because I found the order of the parameters passed from replicaManager.appendRecords is wrong. So the group.lock is not passed to delayedProduce, so there is also the risk of deadlock. Please check it.


Adding libffi-dev to alpine images

We need libffi-dev to pip install cffi which is a dependency of our ssh_check.

👍


Website should also mention the Firefox Addon

justdeleteme.xyz should also mention justdelete.me-firefox-addon not only justdelete.me-chrome-extension.

To add this text, it would be needed to edit every translation in _data/trans. I could submit a draft for it later.


unit test output is too verbose

Problem statement
unit tests suite verbosity now makes difficult to read and understand the output of our CI engines.
For instance, I spent hours figuring out a regression specific to windows trying to read the output from Appveyor, only on a trivial change.
Will soon push a PR to discard most logs or capture output to perform some basic asserts on output (such as "generation completed" on build tests).
Steps to reproduce
go test -v 1>stdout.log 2>stderr.log
Environment
swagger version: 0.13.x
go version: 1.9
OS:   Ubuntu / Windows 10

Merged with 1299-fix-unit-test-verbosity #1300


Remove user retrieve from leaderboard command

parts of this PR are included in https://github.com/knightzmc/DevDenBot/pull/25/ - @knightzmc, You might want to have a look at that PR before merging this one


Won't execute

After hitting Start I get this error in console
VM81:171 Uncaught (in promise) TypeError: Cannot read property 'type' of undefined
at :171:65
at Array.filter ()
at recurse (:171:47)
at async deleteMessages (:249:16)

Try again with the latest revision

This was probably fixed in later commits


Import CSS in JSX throws exception - ReferenceError: 'document' is not defined

Thanks for filing a bug! To save time, if you're having trouble using the library, please check off the items you have tried. If you are just asking a question, skip right to the bottom.
Please verify these steps before filing an issue, and check them off as you go

[X] The relevant native JavascriptEngineSwitcher library packages are installed (such as JavaScriptEngineSwitcher.V8.Native.win-x64)
[ ] The VC++ 2017 runtime is installed
[X] The value of SetUseReact and SetUseBabel is correct in ReactConfig.cs or Startup.cs
[X] I've looked at the sample projects in this repo to verify that my app is configured correctly

I'm using these library versions:

ReactJS.NET: 5.2
JavaScriptEngineSwitcher: V8
react and react-dom: 16.8.2
webpack: 5.46
node: v14.15.5
--

Runtime environment:

OS: (Mac, Windows, Linux flavor. Include 32-bit/64-bit and version)
.NET Framework or .NET Core Version: 4.5

Steps to reproduce

Add - import "./some.css"; on Component.jsx file
Build npm (npm run build)
Run application

Exception is thrown:
ReferenceError: 'document' is not defined
Related to #1231
The desired outcome is to be able to define external component-specific css files that can be imported to JSX components.

I am having the same issue when importing a CSS module e.g.
import styles from './news.module.scss';
...

...
An unhandled exception occurred while processing the request.
ScriptEngineException: ReferenceError: document is not defined
Microsoft.ClearScript.V8.SplitProxy.V8SplitProxyNative.ThrowScheduledException()
JsRuntimeException: ReferenceError: document is not defined
at e.exports (bundle.js:2:302096) -> … "use strict"; e.exports = function (e) { var t = document.createElement("style"); return e.setAttri...

Same issue here.
JsScriptException: Script threw an exception.
JavaScriptEngineSwitcher.ChakraCore.JsRt.JsErrorHelpers.ThrowIfError(JsErrorCode errorCode)
JsRuntimeException: ReferenceError: 'document' is not defined
JavaScriptEngineSwitcher.ChakraCore.ChakraCoreJsEngine+<>c__DisplayClass25_0.b__0()
ReactScriptLoadException: Error while loading "/dist/vendor.1b5e647d.js": ReferenceError: 'document' is not defined
React.JavaScriptEngineFactory.EnsureValidState()

This is the relevant code where this happens when using Emotion for SSR rendering.
var ssrStyles = document.querySelectorAll("style[data-emotion]:not([data-s])"); // get SSRed styles out of the way of React's hydration
    // document.head is a safe place to move them to(though note document.head is not necessarily the last place they will be)
    // note this very very intentionally targets all style elements regardless of the key to ensure
    // that creating a cache works inside of render of a React component

This code mentions SSR, so seems it should run on the server, but the ChakraCore won't have any document property will it?

I'm experiencing this issue as well and have not found a workaround.


Design: Pluggable visualizations

These are notes on  "pluggable visualizations" (cell outputs) that will be added to DFN v2.
Work on this is in progress and partially complete.
Core plugins can be found under the plugins directory in the mono repo.

A visualization plugin is a simple web page hosted in DFN via an iframe. Anyone who can make a static web page can upgrade DFN v2 with custom visualisation capabilities.
DFN automatically chooses a particular plugin by matching data against a set or rules. The data to be rendered by the plugin is passed to the display function.
A user can then override the automatic plugin selection and choose a different visualization plugin.
DFN controls what the plugin displays by sending it a JSON file that contains configuration and data to initialise the plugin.
There will be a sequence of messages (a handshake) to initialise a plugin (this is yet to be spec'd out).
There will also be communication between DFN and the plugin where one side wants to inform the other of an event (e.g. DFN informing the plugin that the window size has changed).
It is my hope that all current output components in DFN v1 will be rewritten using the new plugin system.
A dependency injected PluginRepo is responsible for providing the PluggableVisualization UI component with a plugin to render. That way the rules of how plugins are found can be provided differently depending on the environment (e.g. browser or Electron).
PluginRepo should be able to hand PluggableVisualization a URL for a plugin (which could be file:// for the Electron build) or it can give it the plugin content directly (allowing plugins to be embedded directly in the Electron build).
In the current implementation plugins can be loaded from URL (allowing local plugins to be loaded) or inline (HTML for plugins are compiled into the bundle).
DFN needs to provide a UI for choosing a plugin (output will go to the default, but the user can choose any output plugin they like) and configuring a plugin (a simple settings UI). A plugin must be able to expose the settings it supports and their data types to allow them to be edits. Plugin settings should be stored in the notebook for each cell output.
It is also possible that each plugin might want to allow itself to be visually configured in the plugin UI. For this to happen there needs to be a way to communicate edited settings from the plugin to the "visualization host" (eg DFN) so they can be saved against the notebook.

Long term

Want some kind of "plugin registry" that allows other people to more easily contribute viz plugins.
Want a "plugin playground" that's a way to search for and play with configuration for viz plugins.

Prototype code

There is a prototype here showing how a user pluggable visualization can be embedded in an iframe:

https://github.com/data-forge-notebook/pluggable-output-prototype

Here is the first official plugin (for visualizing structured JavaScript data):

https://github.com/data-forge-notebook/output-plugin-structured-data

The editor-core repository shows an example of this plugin in action to visualization a small set of JavaScript data:

https://github.com/data-forge-notebook/editor-core/

The core plugins are now included in the editor-core mono-repo. This means a plugin registry is not needed in the early days of v2.

Backward compatibility

The old method of having displayType and data for each cell output still works. Although I'd like to to factor displayType out to displayType and dataType. So data type could be array and display type could be table.
Old notebooks still need to work. This means functions like display.plot must still work. Plugins should be able to register functions on the display method. This means that plugins need some kind of queryable API that's independent of he visualization. How will this be structured?

I could potentially polyfill the old methods using an npm installed library.

Open questions

How will DFN determine which plugin to use for a particular data blog? Ideally the plugin itself would publish some code to determine if it is appropriate for a particular data blob.
How will DFN know which plugins are available/published? (Maybe some kind of manifest file?)

Todo

Create a plugin authors guide.
Create a template plugin.

The new system for making pluggable visualizations is working out well. Anyone can potentially add a new plugin by forking the repo and submitting a PR.


Update zksrv.sh

fix the error : no java binary found
If I installed the java without yum or apt-get, but by setting the environment variable JAVA_HOME and PATH,the script with rise error :no java binary found
So we should consider the java binary installed manuelly

I think we should consider merge the pr to fix the bug


Range filter not generating nested queries in Kibana 6.2.2

Plugin version:
5.6.6-1.0.2, 6.2.2-1.0.3
Kibana version:
5.6.6, 6.2.2
Plugins installed:
KNQL only
Description of the problem including expected versus actual behavior:
The test data was generated using scripts/nested-support/genData.py
In Kibana 5.6.6, applying range filters does the right thing and produces a nested query.
In Kibana 6.2.2, applying range filters does the wrong thing and does not produce a nested query.
Kibana 5.6.6 does the right thing:

Kibana 6.2.2 does the wrong thing:

This also happens in discover.
Right thing:

Wrong thing:

While investigating this, I also found that some filters (built using the "Add a filter" UI) work only in certain versions of Kibana:

is - Works in Kibana 5 and 6
is one of - Does not work in Kibana 5 nor 6
is between - Works in Kibana 5, does not work in 6
exists - Does not work in Kibana 5, works in 6

Now THIS is a bug report! Many thanks for the details. I should be able to resolve most of these in the next day or so.

Ok.. There was a major update in Kibana that happened from 5.x to 6.x, and it looks like the work I did on range filters did not make it... should be fixed in the latest 6.2.2-1.04.
Please take a look if it solves the issue, please update this issue, but don't close it. I'll use this to port the fix to other releases, and close this when done.

Wow, thanks for the quick response! I can confirm that it fixes the range filter issue :)

Back ported to all supported 6.X+++ releases

Ported to: 5.6.7, 5.6.8 and 5.6.9

done


Screen jumps when secureTextEntry is set and the keyboard suggests passwords before focusing on the input with secureTextEntry prop

Description
The screen jumps when one of the inputs has the secureTextEntry prop because the keyboard suggests passwords even when typing in a different input that doesn’t have secureTextEntry prop. This happens when focusing on an input placed before the one with secureTextEntry, and as you type, the password suggestion appears and disappears, causing the screen to jump.
https://github.com/user-attachments/assets/14403cee-3d9c-4951-855e-7591f18c4fb8
Steps to reproduce
As you can see in the code, username input doesn't have sceureTextEntry prop set and still suggests passwords above the keyboard, this suggestion appears and disappears as you type causing the app to jump, this only happens when focusing the input just before the one that has the secureTextProp set to true.
`export default function HomeScreen() {
const passRef = useRef(null)
const usernameRef = useRef(null)
return (

<KeyboardAvoidingView
behavior={Platform.OS === 'ios' ? 'padding' : 'height'}
style={styles.container}
>

Header
<TextInput
placeholder='Email'
keyboardType='email-address'
returnKeyType='next'
blurOnSubmit={false}
onSubmitEditing={() => usernameRef.current?.focus()}
style={styles.textInput}
/>
<TextInput
ref={usernameRef}
placeholder='Username'
returnKeyType='next'
blurOnSubmit={false}
onSubmitEditing={() => passRef.current?.focus()}
style={styles.textInput}
/>

<Button title='Submit' onPress={() => null} />

)
}`
React Native Version
0.74.5
Affected Platforms
Runtime - iOS
Output of npx react-native info
System:
  OS: macOS 14.6.1
  CPU: (8) arm64 Apple M1
  Memory: 819.86 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.17.0
    path: ~/.nvm/versions/node/v20.17.0/bin/node
  Yarn:
    version: 3.6.4
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.8.2
    path: ~/.nvm/versions/node/v20.17.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.4
      - iOS 17.4
      - macOS 14.4
      - tvOS 17.4
      - visionOS 1.1
      - watchOS 10.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.18034.62.2412.12266719
  Xcode:
    version: 15.3/15E204a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.12
    path: /usr/bin/javac
  Ruby:
    version: 3.3.5
alejandrovega@Mac-mini-de-Alejandro inputtest % npx react-native info
info Fetching system and libraries information...
System:
  OS: macOS 14.6.1
  CPU: (8) arm64 Apple M1
  Memory: 521.91 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.17.0
    path: ~/.nvm/versions/node/v20.17.0/bin/node
  Yarn:
    version: 3.6.4
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.8.2
    path: ~/.nvm/versions/node/v20.17.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.4
      - iOS 17.4
      - macOS 14.4
      - tvOS 17.4
      - visionOS 1.1
      - watchOS 10.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.18034.62.2412.12266719
  Xcode:
    version: 15.3/15E204a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.12
    path: /usr/bin/javac
  Ruby:
    version: 3.3.5
    path: /opt/homebrew/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.5
    wanted: 0.74.5
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Stacktrace or Logs
No stacktrace error or logs

Reproducer
https://github.com/avega99/SecureTextEntryJump
Screenshots and Videos
https://github.com/user-attachments/assets/9eb7f18f-7247-4140-9905-a9d1940b48d5

This is still an issue in 0.76.3.
Here is an updated repro: Snack
https://github.com/user-attachments/assets/96a40988-9c2f-46a9-b24c-a03e1ba503f7
The problem can be caused by multiple things, including textContentType={'username'} on the former TextInput, secureTextEntry={true} on the letter TextInput, and presumably any other condition that pops the Passwords button in iOS.


Add Closure and Remainder transforms

These transforms are being moved from the CoDa.jl package.

Codecov Report

Merging #211 (2442f59) into master (ba766a2) will increase coverage by 0.15%.
The diff coverage is 96.29%.

@@            Coverage Diff             @@
##           master     #211      +/-   ##
==========================================
+ Coverage   92.93%   93.08%   +0.15%
==========================================
  Files          34       36       +2
  Lines        1146     1200      +54
==========================================
+ Hits         1065     1117      +52
- Misses         81       83       +2

Files
Coverage Δ

src/TableTransforms.jl
100.00% <ø> (ø)

src/transforms.jl
100.00% <ø> (ø)

src/transforms/closure.jl
95.00% <95.00%> (ø)

src/transforms/remainder.jl
97.05% <97.05%> (ø)


federation: kubectl --cascade should be false by default for federation

 Issue by nikhiljindal
Friday Dec 16, 2016 at 20:18 GMT
Originally opened as https://github.com/kubernetes/kubernetes/issues/38897

Ref https://github.com/kubernetes/kubernetes/issues/33612.
Cascading deletion is true by default for kubectl.
For federation, we want it to be false since deleting a federation resource with cascade=true will delete the resource from all clusters as well which can lead to a global outage. So we want --cascade to be false by default but users can pass --cascade=true if they do want cascading deletion.
cc @kubernetes/sig-federation-misc @kubernetes/sig-cli-misc @quinton-hoole @caesarxuchao

 Comment by nikhiljindal
Friday Dec 16, 2016 at 20:20 GMT

A hacky way to do this is for kubectl to first determine if it is talking to federation apiserver and if yes, then set the default to false, else keep it to true.
Open to other suggestions on how to implement this.

 Comment by liggitt
Monday Dec 19, 2016 at 21:10 GMT

why would we want orphaning to be the default for federation? I didn't think federation allowed adopting cluster-level resources, so if a federated resource originated with the federation server, it seems natural that it would end there as well

 Comment by madhusudancs
Tuesday Dec 20, 2016 at 05:32 GMT

@liggit federation does adopt resources.
@nikhiljindal the hacky way is a documentation challenge though. It is difficult for obvious reasons to generate the help text dynamically. Example: people might run kubectl delete -h, but actually delete by running kubectl --context=federation delete .... An alternative is to just statically print if federation cascade=false else cascade=true in the help text. But this might be confusing for users. Now they have to remember the behavior based on the server they are sending the request to. But I don't have a better solution in mind.

 Comment by liggitt
Tuesday Dec 20, 2016 at 20:22 GMT

cascade has potential to be disruptive in a single cluster as well, yet it was chosen as the default there.

 Comment by quinton-hoole
Friday Dec 23, 2016 at 00:44 GMT

@liggitt I can't speak to why the disruptive option was chosen as the default in the single cluster case (do you perhaps know?), however avoiding global outages is one of the primary use cases of Federation, so making global cascading deletion the default for Federation does not seem wise. Other than the consistency argument, can you think of any good reasons why global cascading deletion should be the default?

 Comment by shashidharatd
Tuesday Jan 03, 2017 at 04:45 GMT

@nikhiljindal, Maybe kubectl can determine, if it is talking to federation apiserver or kubernetes apiserver by checking the support for cluster object. is there a better way?

 Comment by liggitt
Tuesday Jan 03, 2017 at 04:49 GMT

I think changing CLI defaults based on the server being spoken to is very difficult to understand, and seems like a bad precedent to set

 Comment by shashidharatd
Tuesday Jan 03, 2017 at 04:53 GMT

otherwise, we could introduce a new flag for federation object cascade deletion maybe with suitable name

 Comment by shashidharatd
Tuesday Jan 03, 2017 at 04:55 GMT

sorry, ignore my previous comment. as we are discussing default behaviour

 Comment by quinton-hoole
Thursday Jan 05, 2017 at 17:01 GMT

@liggitt Do you have answers to my questions above? https://github.com/kubernetes/kubernetes/issues/38897#issuecomment-268921918

 Comment by liggitt
Thursday Jan 05, 2017 at 17:47 GMT

I think the reasons are identical to the ones made for local cascading being on by default (I wasn't a fan of it there either). See https://github.com/kubernetes/kubernetes/pull/7210

 Comment by ualtinok
Friday Jan 06, 2017 at 09:16 GMT

How about having kubectl to ask user for confirmation when the command is directed to federation apiserver? I never saw kubectl asking for user confirmation for anything so this may be a silly proposition.

 Comment by liggitt
Friday Jan 06, 2017 at 15:01 GMT

yeah, none of those are interactive commands

 Comment by nikhiljindal
Wednesday Jan 25, 2017 at 06:56 GMT

I discussed this with @bgrant0607 and he didnt like the idea of changing the default based on which server is kubectl talking to. He pointed out that total outage is a problem in kubernetes as well and we need generic ways to prevent that rather than change the default in federation.
Cascading deletion with kubectl is pretty broken in federation right now. Some resources do part cascading deletion and some dont at all. We need to fix this soon.

 Comment by bgrant0607
Wednesday Jan 25, 2017 at 08:29 GMT

#10179

 Comment by bgrant0607
Wednesday Jan 25, 2017 at 08:31 GMT

The whole point of the approach with federation is that it looks like a K8s cluster. Therefore, behavior must be the same, by definition.

 Comment by quinton-hoole
Wednesday Jan 25, 2017 at 14:59 GMT

I strongly disagree Brian. More later...
On Jan 25, 2017 12:31 AM, "Brian Grant"<EMAIL_ADDRESS>wrote:

The whole point of the approach with federation is that it looks like a
K8s cluster. Therefore, behavior must be the same, by definition.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes/issues/38897#issuecomment-275048012,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ6NAfaQi4PQgQU_qmEf24sTeLqjKuBxks5rVwhqgaJpZM4LPjtK
.

 Comment by quinton-hoole
Wednesday Jan 25, 2017 at 18:52 GMT

@bgrant0607
TL;DR:

I would like to understand the rationale behind why destructive cascading deletion is currently the default in kubernetes (both in the API, and in kubectl).  I suspect that that might have been the wrong decision (although I would be happy to be convinced otherwise).
It is my opinion (and this seems to be shared by several others) that in some cases, defaulting to destructive cascading deletion is especially dangerous, and should be avoided, even at the expense of consistency/compatibility.  Federation is one example of this.
Statefulset persistent volumes are another such concrete example.

PS:  It might be quicker to resolve this with a brief verbal discussion.  I'll email you my phone number.
Detail:
Why is cascading deletion the default in kubernetes (both in the API, where DeleteOptions.orphanDependents defaults to false, and in kubectl, where --cascade defaults to true )?
Given that the overwhelming majority of familiar command line tools and API's default to false for destructive cascading and/or recursive deletions (e.g. rm, rmdir, libc remove, etcd delete, consol delete and just about any other one I can think of), I assume that we have a good reason for being inconsistent with the user expectation that that creates (principle of least surprise etc, etc)?  The reasoning behind not having such destructive operations be the default are fairly obvious, and the reason why it is not the norm in API's and command line tools.  I've looked through the issues and PR's you quoted above, and I can't find any explanation of why this default behavior was adopted in Kubernetes. What I can find is objections to it being the default behavior (e.g. @liggitt  in  https://github.com/kubernetes/kubernetes/pull/7210#issuecomment-95765644).
And now a clarification: cluster federation's primary purpose is to be able to easily manage applications across multiple clusters, the main use case of which is avoiding application outages (although there are of course other use cases, like geo-locality, hybrid cloud etc). The fact that cluster federation implements the kubernetes API is somewhat of an implementation detail, and in fact there were some fairly vigorous arguments that it should not.  In the end we decided to try to remain true to the Kubernetes API as far is is practical, for reasons of user familiarity and tool compatibility, but recognized that that will not always be tenable/sensible. I think that this is a case where there is a strong reason not to be consistent with the kubernetes API and tool default to perform destructive cascading deletion.  StatefulSet provides another example of a similar case where full cascading deletion is not the default (the underlying persistent volumes are explicitly not deleted when statefulsets are deleted).
I'm not for the moment concerned about exactly how we go about implementing non-default cascading deletion (and I share your distaste for special-casing it in kubectl).  I think we should first decide what the default behavior should be.
Full disclosure: Based on what I currently know, it seems that both kubernetes and federation API's should default to "orphanChildren=true" (i.e. cascadingDelete=false) at both the API and kubectl level, with an option to explicitly trigger cascading deletion when required.  This would be both safer and more consistent with other similar API's and tools.

 Comment by bgrant0607
Wednesday Jan 25, 2017 at 22:00 GMT

@quinton-hoole
Some history may be traced from #1535. Cascading by default is the behavior expected by the vast majority of users. Most users want to think of Deployments, ReplicaSets, etc. as atomic entities. Originally we orphaned by default and it was a significant cause of user friction.
The default in kubectl is not changing without evidence that it is the cause of catastrophies and without consensus among the broader user base, since it would increase user friction and break pretty much every use of kubectl in the ecosystem.
I'd be happy for a default preference to be added that users could change if someone would add a reasonable preference mechanism. #10693
The API couldn't be changed to cascade by default because GC was added much, much later, and doing so would break compatibility. Until we added GC, lack of cascading deletion continued to be a pain point for clients other than kubectl. It's part of the broader effort to make the API simpler for common operations. #12143 Note that when we add new resources under existing ones, cascading deletion must be applied to them by default so as not to break existing clients. If/when we have a v2 API, I'll make cascading deletion the default in the API as well.
If federation were not compatible with standard Kubernetes, then many tools, scripts, clients, etc. wouldn't work. Additionally, this issue isn't unique to federation and shouldn't be solved in a one-off manner. Deletion-prevention could be solved with authorization policy, which would prevent catastrophic updates as well, or with a generalized deletion-prevention mechanism, which is desired for system components in individual clusters #10179.
Cascading deletion was also added when deleting namespaces. That is the default behavior, since the namespace cannot be removed while it still contains resources.

 Comment by quinton-hoole
Wednesday Jan 25, 2017 at 22:44 GMT

@bgrant0607 OK, I now understand your basic argument to be that ease of use trumps safety (where safety in this case means requiring a relatively simple positive indication in the API or tool, along the lines of --cascade/--recursive/--force to confirm that large, non-obvious destructive operations will be performed automatically, like terminating an application globally, in this case, or deleting a bunch of valuable persistent data in the case of statefulset persistent volumes).  That's contrary to what most other API's and tools have decided (see examples above), despite their motivations being very similar ("Id' like to think of a directory tree as being a single logical thing, and be able to simply do 'rmdir mydir', but it doesn't work - I have to specify '--recurse --force'").  Having read through the various threads you've sent me, it also seems to be contrary to what many other Kubernetes contributors have opined (for example @thockin in https://github.com/kubernetes/kubernetes/issues/1535#issuecomment-91454268 and there are several others like it). And it's contrary to what I think :-)
However, as you say, reverting those decisions now will be disruptive.
For federation, I guess we will have to figure out another way to reduce the likelihood of accidental global cascading deletions and the resulting global service outages.  That solution will probably be more complex and/or dangerous for users than what's proposed above, but so be it.

 Comment by bgrant0607
Thursday Jan 26, 2017 at 00:39 GMT

@quinton-hoole It sounds like you want an equivalent of alias rm='/bin/rm -i'. A simple preference mechanism in kubectl would solve that.

 Comment by bgrant0607
Thursday Jan 26, 2017 at 00:41 GMT

@quinton-hoole I'll also point out that tools like helm will be able to tear down even more resources in a single command line.

 Comment by quinton-hoole
Thursday Jan 26, 2017 at 00:59 GMT

@bgrant0607 The alias you mention is definitely one solution.  Although rm actually works exactly the way I want, in the absence of the alias (i.e. by default).
   By default, rm does not remove directories.  Use the --recursive (-r
   or  -R)  option to remove each listed directory, too, along with all
   of its contents.

It's not clear to me how we could automatically populate most or all user's preferences (both for kubectl, and the API) with the safer options.  If we can work out a way to do that, I'd be less concerned.  But making it the default in the API and tool seems simpler and more sensible.
As for helm, I have no problem whatsoever with being able to wreck havoc with a single command line invocation, so long as it's obvious what I'm doing, and not the default, flagless behavior.
I can delete an entire file server with 'rm --recursive --force /' but not with 'rm /' :-)

 Comment by nikhiljindal
Friday Jan 27, 2017 at 00:14 GMT

Why is cascading deletion the default in kubernetes (both in the API, where DeleteOptions.orphanDependents defaults to false, and in kubectl, where --cascade defaults to true )?

To clarify, cascading deletion is not the default in the API (neither in kubernetes nor in federation).
It is the default in kubectl for kubernetes.

 Comment by quinton-hoole
Friday Jan 27, 2017 at 17:35 GMT

@nikhiljindal @bgrant0607 Yes, thanks for bringing that up.  I was about to ask for clarification.  As far as I can tell from both the API documentation (https://kubernetes.io/docs/api-reference/v1/definitions/#_v1_deleteoptions), and the code, cascading deletion is the default in the API
orphanDependents

Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object’s finalizers list.

required: false
type: boolean
default: false

Am I misunderstanding something?

 Comment by bgrant0607
Friday Jan 27, 2017 at 17:52 GMT

@quinton-hoole Yes, that documentation is confusing/wrong. It should be API-dependent.
@lavalamp @pwittrock @caesarxuchao Where is the correct documentation about orphaning/cascading deletion behavior for individual APIs / API groups?

 Comment by caesarxuchao
Monday Jan 30, 2017 at 10:30 GMT

It looks like the API doc marks the default value of every boolean variable to be false, and boolean is the only type that has a default value. We should remove the "default" column. @pwittrock is default values fixed in the new versions of API docs?
"correct" documentation on GC:
In the GC user-guide: "If you specify deleteOptions.orphanDependents=true, or leave it blank, then the GC will first reset the ownerReferences in the dependents, then delete the owner"
The description is true if user doesn't manually set OwnerRef. As Brian said, default orphaning/cascading deletion is per API group.
As of today, the default GC policy is "orphan" for RC, RS and Deployment. For other resources, the default GC policy is "cascading", however, because no ownerRefs are automatically set to point to these resources, so no GC action will be triggered by their deletion.

 Comment by pwittrock
Monday Jan 30, 2017 at 22:42 GMT

The new API docs don't have a default value in the documentation.  I think this was because I noticed the information was missing / incorrect.
https://kubernetes.io/docs/resources-reference/v1.5/#deleteoptions-v1
I don't see the default value for orphanDependents in the swagger:
https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json
A simple fix for the new api docs is to include the default value in the description text.

 Comment by nikhiljindal
Monday Mar 20, 2017 at 05:48 GMT

As per the discussion above, defaults for cascading deletion in federation will be same as in kubernetes i.e --cascade=true by default for kubectl delete.
Closing this issue.

 Comment by quinton-hoole
Monday Mar 20, 2017 at 15:14 GMT

Please don't close this yet. It's not resolved.

cc @nikhiljindal


Remove redundant fieldType.stored() check [LUCENE-9603]

No need to check fieldType.stored() here because already checked.https://github.com/apache/lucene-solr/blob/5897d14fe4f5dd785a561b18c939ea31186c4971/lucene/core/src/java/org/apache/lucene/index/IndexingChain.java#L587

Migrated from LUCENE-9603 by Shintaro Murakami (@mrkm4ntr), updated Nov 12 2020
Pull requests: https://github.com/apache/lucene-solr/pull/2076

This can be resolved, it was removed in https://github.com/apache/lucene/commit/d1297e52d91dbbcd83012c438ee0122d96808fa8 .

Ahh yes this is indeed done -- I'll close this issue.  Thanks @hurutoriya and @slow-J and @mrkm4ntr!


ci: make error message in "🌈 Go Style Check" more readable

Signed-off-by: seeflood<EMAIL_ADDRESS>
What this PR does:
I spent some time telling @dzdx how to fix the CI error in https://github.com/mosn/layotto/pull/676 .
It's not cool.
So I think we should make error message in "🌈 Go Style Check" more readable

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

I am going to merge this, ci failed no related to this PR.


Change VECTOR C++ implementation to unordered_map and simplify it

LDPL does not care about the order of the elements in a map so we can use unordered_map which is much faster for the average case. There were also many unnecessary overloads since most of them can be implicitly converted.

I'm most grateful for your exquisite pull request, Mr. Noitatum.


New tag? :)

Question
Hi there!
When are all the fixes made in the past few months due for a release in a tag?
Thanks!

@Thulium-Drake,
We should have the release today or tomorrow. It will include the new 2.0.0 benchmark updates as well as all of the fixes that have come through the last few months.
-George


Screenshot

You need to add result screenshot in readme file

Hi @umardev500,
Thank you for pointing that out!
The issue has been addressed, and the screenshot has now been added to the README in PR https://github.com/mkafonso/schema/pull/3.
Appreciate you taking the time to suggest the improvement :tada:


implement get_hosted_zone_count() api

Resolves issue #4813

Codecov Report

Merging #4814 (90eab85) into master (4f1dcc5) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #4814   +/-   ##
=======================================
  Coverage   95.04%   95.04%
=======================================
  Files         586      586
  Lines       62584    62592    +8
=======================================
+ Hits        59484    59492    +8
  Misses       3100     3100

Flag
Coverage Δ

servertests
36.13% <37.50%> (+<0.01%)
:arrow_up:

unittests
94.98% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

moto/route53/urls.py
85.71% <ø> (ø)

moto/route53/models.py
94.21% <100.00%> (+0.03%)
:arrow_up:

moto/route53/responses.py
97.20% <100.00%> (+0.08%)
:arrow_up:

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 4f1dcc5...90eab85. Read the comment docs.


Added more tests for specific points.

Some points designed to test for underflow of x^3-ax.

Thanks!


Refs #24996 -- Removed unused BaseDatabaseFeatures.supports_select_related.

Unused since 0c7633178fa9410f102e4708cef979b873bccb76.

This parameter is not used by any backend from the 3rd-party-database-backends list.

buildbot


Github is a scary app, JEITweaker docs part 1, vital information

Co-Authored-By: Silk<EMAIL_ADDRESS>Example from underdog will come soon once I get to porting that.
LMK if you see anything horribly wrong

Don't forget the docs.json changes

why is that not in the commit
fixing now

After discussion on Discord, I'll be reviewing this, but since automatically generated docs are out, I'm going to convert this to a draft until Part 2 is also available


Invalid headers

This fixes the reason the travis CI builds are failing.
One thing I noticed in the travis configuration is that we are not running unit tests.  Is there a reason?

👍
IIRC unit testing was disabled because travis builds were timing out.
However it looks like they may no longer have a time-out, so we could try enabling.

thanks for cleaning these up. better to check for headers during development than while trying to release.


(PUP-8556) Add glob support to modulepath in environment.conf

CLA signed by all contributors.

Hey @seanmil any thoughts on my earlier comment? I'd like to see consistency between these different ways of defining modulepath.

Personally, I don't think there is as much of a (any?) need for Puppet to handle globs in the modulepath on the command line. If you are passing in a command line parameter then you should theoretically already have various ways of pre-expanding any required globs before passing the parameter in (e.g. in the shell before invoking Puppet) or otherwise running through logic that will get you the desired resulting set of paths.
When working with environments from within a Puppetmaster context though you don't have that option, only what environment.conf provides.

I still believe there is a case where a user might expect to be able to specify the same path with a glob both in environment.conf and on the command line. I don't think that inconsistency is something we need to solve here though.
I'm satisfied with the rest of this PR. I'll try to get more eyes on this today so we can merge it in.


Cool

I apologize in advance for messaging you through submitting issue, i dont really know how to contact you directly, im new here.
Rift Explorer isnt working for me anymore, tried everything, and because you could make an skin grabber and icon changer as an manual application, i want to ask, are you able to make an profile background changer, to any skin/champ you want without having it? I was able to make it through rift explorer, and i dont really know any other way to access riot api.
Thanks

If it was possible through rift explorer its possible to make an application to do it. I never knew you were able to change your profile background to anything in rift explorer, are others able to see it or just you?

I saw people doing that, and other players can see it too.

www.youtube.com/watch?v=Z-pK6VlOgYw&t=
heres video for example


Cargo confused about broken Cargo.toml in $HOME

Problem

Sometimes, I just temporarily copy or move files to my $HOME (during a rebase or something). I did that with Cargo.toml today.
If I try to run cargo build in any project, it then tries to load the Cargo.toml in the $HOME too ‒ which is likely unrelated to the current project and is likely broken (because $HOME/src does not exist, so it can't decide what to compile there). That is quite confusing behaviour.
$ cargo new stuff
     Created binary (application) `stuff` package
$ cd stuff/
$ cargo build
   Compiling stuff v0.1.0 (/home/vorner/stuff)
    Finished dev [unoptimized + debuginfo] target(s) in 0.15s
$ cp Cargo.toml ~
$ cargo build
error: failed to parse manifest at `/home/vorner/Cargo.toml`

Caused by:
  no targets specified in the manifest
  either src/lib.rs, src/main.rs, a [lib] section, or [[bin]] section must be present

Notes
Output of cargo version:
cargo 1.34.0-nightly (5c6aa46e6 2019-02-22) (but happens with stable too, so I guess it's there for a while)

This is because core::workspace::find_root() first tries to figure out if the current crate is part of a workspace and then falls for the orphaned manifest in $HOME.
There is a legitimate use case for having a ws-manifest in $HOME (e.g. a container image being built) so we can't ignore this case. Maybe find_root() should be modified to identify a manifest as the root if and only if it's an actual workspace-manifest (and ignore it if it's a stray package manifest).

Maybe somehow make the errors from parsing/interpretting that one a soft error or warning? If it doesn't look like toml (or package manifest at all), then warn about its existence, but don't fail. Would that be possible?

My concern about a warning is that if the actual workspace had an error in it then that would be silently incorrect at worse and product a lot of unrelated errors at best.
Workaround: add a [workspace]  to your manifest to prevent searching for the workspace.
rust-lang/rfcs#3279 will allow some control over finding an implied Cargo.toml or a workspace root.
I have considered the idea of allowing package.workspace = false to opt-out of workspace detection for "cargo script".


Transparent background

Is transparent background supported with the Cog Launcher?
I'm trying to run application on the imx6 where gstreamer is sending video to the /dev/fb0 and I need to have a transparent UI that would be drawn on the /dev/fb1.

Is the GStreamer video rendered with a <video> element?
Is your use-case about overlaying html over foreign (non-WebKit app) video?

Second scenario.
GStreamer is ouputing video directly to the /dev/fb0.
Webkit app is rendering UI to the /dev/fb1 (overlay).
IMX6 is merging both framebuffers together. Probbably it is better explained here starting from slide 35.
http://cache.freescale.com/files/training/doc/ftf/2014/FTF-CON-F0223.pdf
For examaple if I output png image with transparent parts to the FB1, then I will see video under image.
I'm new to the WPE and still in the process of understanding how does it work. What I found is that WPEBrowser have a setting to enable transparent background and was hoping that it is also possible with the Cog Launcher.
https://github.com/WebPlatformForEmbedded/meta-wpe/wiki/WPEFramework

Can you please reach out by e-mail<EMAIL_ADDRESS>

This new API for WPE should solve the problem: https://bugs.webkit.org/show_bug.cgi?id=192305


Jest tests failing with "TypeError: Constructor is not a constructor"

As the title says, using the library causes my Jest tests to fail with an error TypeError: Constructor is not a constructor.

Nevermind again, had to mock ResizeObserver


Create an enum for currency codes

contracts.proto is lax regarding currency codes:
    string acceptedCurrency          = 5;
    string pricingCurrency           = 6;

Instead of a plain string, I think it would make sense to enum the possible values, similar to countrycodes.proto.
Duo Search has recently seen a vendor use currency code US instead of USD, and this broke our client-side JavaScript.

I suppose we could do that. The issue is if people end up creating an altcoin fork in the future, then the contract wont be able to parse enums for altcoins it doesn't know if. It would probably cause the contract to display.


Review of os.path.join()

Verify that all code in Python uses the os.path.join() functionality to allow Windows integration

Reviewed (and corrected 1 item).  Remembered I was "quick" in one place.


Update Content Type will not update fields visiblity

In admin/content on select any content type under the Fields, we are showing all fields which each textbox type field we have a checkbox to select whether to show that field in a list or not? It will work fine when we create new Content Type But it will not work while editing.

@mahnouman This issue was already fixed in commit d64519b9dcb05cf63fce91043f09f82f64c1c1e8 So it can be closed now


fix regression, consistent lib directory

@conda-forge/core can someone set the previous builds to broken.
After testing it looks like osx and linux used a wrong lib-directory.
the checked builds should be set to broken:
osx/ linux  netgen-6.2.1802-py36_1.tar.bz2 & netgen-6.2.1802-py35_1.tar.bz2

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@looooo I just did that. Can you check if I got it right?

@ocefpaf thanks, perfect!


Update Theming Training for Plone Conference 2017

Lots of fixes and enhancements for the theming  training. I will continue to update the last 3 chapters next week, but it would be helpful if this can already be merged and be available online.
Thanks,
Thomas

Can someone else, rebase and merge for some reason I can't get git do it. It keeps complaining,
Thanks !

I'll rebase

Not 100% sur if the file ttw/ttw-advanced-2.rst should be there or not, since rebasing was kinda messy. But not it should be easy to clean up any remaining issues.

I fixed some links and such, build is green and it is deployed.

Cool, thanks!


GitHub Copilot but for VSCode Terminal

It'd be nice to give the copilot ability to the integrated terminal.
Specifically,

shell agnostic copilot - suggestions are prompted while typing the command.
auto explains last error message and potential actions to take
give examples of the typed command
...

We're planning on doing this soon, an exploration was tracked in https://github.com/microsoft/vscode/issues/170485. Closing off as we're tracking it internally


Add known issues to pr template

Reviewers
Functional: @MDunitz
Readability: @seve

Changes

add know issues to PR template

Sorry, I think I missed this conversation -- what is the purpose of the "Known Issues" section of a PR?

For anything we think might be an issue. It could be blind spots in the DoD that might need to be addressed now or in the future, conditions that cause unintended behavior that won't be addressed in this PR, and stuff of that nature. This will make it easier to track and bring to the attention of reviewers and the PM during a review.


Disconnect after selecting large amount of text (Ubuntu 21.04, xrdp, x11vnc)

Ubuntu Budgie 21.04 (but same issue on 20.10), xrdp 0.9.12.
All I did on my homeserver:
sudo apt install xrdp && sudo apt install x11vnc
Changed the xrdp.ini file, x11vnc section to connect to port 5900. Goal is to share the local desktop session that is currently running (instead of a new remote session):
[Xvnc]
name=Xvnc
lib=libvnc.so
ip=<IP_ADDRESS>
port=5900

I have Guacamole in Docker running on the server and access guacamole via my laptop within my LAN. Via guacamole I simply connect to xrdp protocol, rdp://<IP_ADDRESS>. Connection works instantly, it is plenty fast.
Only issue is this one:
https://github.com/neutrinolabs/xrdp/issues/755
As soon as I select a large/semi-large amount of text, I am disconnected within seconds.
I can reconnect, but after a fixed amount of time (about 10-15sec) I always get disconnected.
Unless I use the little time I have after reconnecting to select a single word, when I do that, connection stays.
It seems this was fixed before in the past..
When I connect (using guacamole) directly with x11vnc: vnc://<IP_ADDRESS>:5900 I do not have this issue. I prefer the xrdp>x11vnc route though because it is slightly faster.

Hi @zilexa
Thanks for reporting this. I've managed to reproduce it with Guacamole, but not with the Microsoft client. It's a buffer overflow in the VNC code for large copy-and-paste operations.
It's not the same as #755, although the symptoms are similar.
I must also say that although your setup should work, cut-and-paste probably won't. For that you';; need to run xrdp-chansrv, and we only recently fixed a bug which allows this to happen on DISPLAY 0. So you'd need xrdp v0.9.16 for that.

Thanks for the swift feedback!
I use this setup because the documentation of guacamole (and several other articles and fora) recommend this (xrdp + x11vnc) is THE best way to share local desktop session with opensource software. So I thought it would be pretty common.
I guess I should do 3 things:

From the 0.9.16 release notes I understand all I need to do is add chansrvport=DISPLAY(0) to the [Xvnc] section in my xrdp.ini.
Updating to that version would mean building from source and installing.
File a bug with guacamole (already did guacamole-1345) and add information to it.

@matt335672: Could you clarify this statement a bit:

Thanks for reporting this. I've managed to reproduce it with Guacamole, but not with the Microsoft client. It's a buffer overflow in the VNC code for large copy-and-paste operations.

With Guacamole, when connecting to xrdp, the VNC code would not be used at all (even if xrdp is using VNC on the back-end), so I'm not sure how this could be a buffer overflow in the Guacamole VNC code?
Can you provide any further detail about where you see this buffer overflow?

Both - there's definitely a bug on our side which needs sorting out. This may still be nothing to do with guacamole.
@zilexa - as regards your list :-

In your session you need to run xrdp-chansrv before you connect to the session. Otherwise you'll see a delay while xrdp tries to talk to a non-existent process. Be aware that when you log out of the session it will be necessary (somehow) to fusermount -u ~/thinclient_drives before starting another xrdp-chansrv.
That's correct.
That's possibly a bit premature, and I apologise if I gave you that impression.

Also, there's some basic text-only cut-and-paste code which is supported in x11vnc mode which is what seems to be broken here.
@necouchman - @zilexa is talking RDP from guacamole to xrdp, and then using the xrdp VNC backend to connect to an existing x11vnc server.
I think there's a linguistic confusion here - both projects have a VNC backend and the problem I've found is in the xrdp VNC backend and not the guacamole VNC backend. I think that's been lost in translation.
Does that make sense?
A bit more detail which may help - xrdp is receiving a CLIPRDR_FORMAT_DATA_REQUEST PDU MS-RDPECLIP <IP_ADDRESS> and then trying to squeeze a large amount of VNC copy text into an inappropriately sized buffer.
I think the problem comes down to when the client sends  CLIPRDR_FORMAT_DATA_REQUEST, and this is just something which is more likely to happen with guacamole. I'm planning to test that hypothesis this afternoon, in which case I can rule out guacamole.
The reason we don't see this all the time is that in this configuration the process which normally handles the clipboard is not running, and so we're falling back on some rarely used codepaths.

I can confirm this is nothing to do with guacamole.
The Windows client sends the CLIPRDR_FORMAT_DATA_REQUEST on a request to paste the data rather than earlier.
@necouchman - I think you can close 1345 on your side. I don't have an Apache account myself.

@matt335672: Thank you for the additional testing and detail on this - makes sense and is much appreciated. I'll close out the ticket on the Guacamole end.

Just fyi, without xrdp-chansrv, the connection is fast and stable, I am not noticing any delay..
Only when selecting large text the connection gets interrupted.
A bit offtopic, but is x11vnc essential to connect to the current local session via xrdp or can this also be achieved without vnc? I haven't found any documentation online describing alternatives for vnc when using xrdp to connect to the local session.

The only way to connect to the console I'm aware of is to (somehow) go via VNC.


Update drawer.tsx

support rtl

@aashahin Please note that we have a wip PR for adding RTL support to all components. See https://github.com/shadcn-ui/ui/pull/1638 (Thanks for the PR)

I noticed an imbalance in ingredients that take virtual values right and left instead of start and end in margin and directions


feat(BB): PrepareProposal Chain

@davidterpay for me to come in and help here, can you start adding medium-detail comments to PRs?


How to Change the Lane Width of the Road?

Hi ,
In the RoadArchitect ， Default Lane width is 5M of the Road .
But in the Inspector of Road，when I change the "Lane Width" to other Value (ex. 8M )  in Road options ，
I couldn't found any change of the Road .
If I press the icon like "enter" in the Road options , the value of Lane width will return 5 M .
So......Would you provide the rule about "How to Change the Lane Width of the Road ? "
Thanks

@johnny77lee Try changing the value to 8 meters and then clicking on another textbox. The "enter" icon actually means "reset to default value".

This Issue was already answered by embeddedt; I do want to add some Lines to this.
You can change the Road width by changing the "Lane width" to the desired value and then clicking onto another check box. The Road then should automatically update itself. You could also enter the value into the field and manually press the "Update Road" Button.
I hope this answered your question.
This answer closes this Issue.
Feel free to reopen this Issue, if you have further questions regarding the Lane width.
You can also open new Tickets for other Questions.
Best Regards


Test cases

Failing unit test case of habApi corrected
Added unit tests for couple of common components

PR checklist
Docs

[ ] If you added new code; is it self documenting? (all the variable names clear, comments added where appropriate)
[ ] If you touched existing code; did you refactor existing naming, added comments where necessary?

Tests

[ ] If your ticket adds new functionality; have you added unit tests to verify behaviour?
[ ] If your ticket alters user interaction with the UI; have you added integration tests?
[x] Do your tests check for every convievable user behabviour? (all behaviours the user can perform)

Typing

[ ] If you added new code; have you added typing?
[ ] If you touched existing code; have you improved its typing?

Styling

[ ] If new styles were created; Did you refactor/add more styles in css-in-js style?

A simple integration test is added and console.log warning.
Axios mock adapter setup is somehow giving a lot of trouble. However the test is passing, its still loading from hosted domain. tried adding .env.test and defined full url in onGet but still the same so written test on hosted api as of now.

Thanks for the changes! I made some comments regarding removing files and had a question about a line of code. Could you resolve these?


Make work in browser environment

Prevent ReferenceError: Can't find variable: module

Thanks for the PR.


DR-357 Add perms to github iam policy

Description

Context

Type of changes

[ ] Refactoring (non-breaking change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Bug fix (non-breaking change which fixes an issue)

Checklist

[ ] I am familiar with the contributing guidelines
[ ] I have followed the code style of the project
[ ] I have added tests to cover my changes
[ ] I have updated the documentation accordingly
[ ] This PR is a result of pair or mob programming

Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

[ ] I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

infrastructure/local/versions.tf commented out code has been removed in dos-service-search

Good spot Tamara - have removed dead code


Create ashish561980

hi @ashish561980 it looks like you did everything right except you did not include the .yml extension on your filename. If you repeat the steps and include the .yml extension in your filename, that ill trigger an automated workflow that will process your request within 1-3 minutes.
Thanks!


some equations in The pdf doc of RL spinningup are wrong

Thank you very much for your resources that help people learn fast. But one thing I found is that some equations in the pdf doc is not the same as those on html. And some figures are lost. For example,

You are correct, but unfortunately I am not sure what, if anything I can actually do about this. It seems that some custom commands are getting ignored and I do not know why.

Maybe we should take down the incorrect (improperly-rendered) documentation and leave a note referencing this bug and fixes welcome?

I notice the error comes from
 \underE
Could you please try
\mathop{\mathbb{E}} to set notation expectation  E to be a math operator and then you can apply the \limits to set subscript symbols to the bottom of E.
for example:
$\mathop{\mathbb{E}}\limits_\tau\sim\pi$

You are correct, but unfortunately I am not sure what, if anything I can actually do about this. It seems that some custom commands are getting ignored and I do not know why.

I notice the error comes from
\underE
Could you please try
\mathop{\mathbb{E}} to set notation expectation E to be a math operator and then you can apply the \limits to set subscript symbols to the bottom of E.
for example:
$\mathop{\mathbb{E}}\limits_\tau\sim\pi$

This has now been fixed!


Remove -m$(MODEL) build flag

According to the GCC manual this flag is only useful on x86_64 and the Debian package has been patching it out in their builds.

Got it!


Update tns-core-modules to @nativescript/core

Good morning jibon57,
Thanks for the development of an amazing plugin including camera and gallery functionalities, we find it very useful. However, your plugin currently depends on tns-core-modules (which seems deprecated: https://www.npmjs.com/package/tns-core-modules). Nativescript team recommends using @nativescript/core instead.
We would like to make a request of updating the imports to the recommended package by the Nativescript team, not by us.
Thanks for your time.

Nativescript 7 no longer supports tns-core-modules, so this update is critical for anyone upgrading. @jibon57 is this fix on your radar? We appreciate the work you have put into it.

Not really, we were able to solve it by setting some aliases in our webpack configuration. So if anyone has a similar problem he can do that. Thanks for all @mreall.

@mreall  @danielorihuela would you guys please share the solution? It's so bad there's a solution but the community can't see it :)

@csimpi you have to go in to the alias section of your webpack config and add a new alias for tns-core-modules.
Example:
alias: {
    "tns-core-modules": "@nativescript/core",
    "nativescript-angular": "@nativescript/angular"
}

https://webpack.js.org/configuration/resolve/#resolvealias

@danielorihuela Thank you! It seems this has already been a part of my webpack and still having issues with NS7 :(

Considering how long this and other issues have been open with no feedback from @jibon57, I ultimately had to go with another plugin.

@mreall Is there any reliable file-picker plugin for nativescript? I didn't find any suitable replace.

@mreall BTW, I'm trying to update this to NS7 I'll let you know if you can test my forked version. Maybe I can do it within a reasonable time.

Hello everyone, I'm no longer using NativeScript now. Will be happy to get some contributor.

@jibon57 - Thank you for the update! We're working on the migration with the NS community, I'll update you guys with the fork's address soon. Maybe tomorrow.
Basically forking this and making these changes can be a temporary solution:
https://nativescript.org/blog/nativescript-7-for-plugin-authors/


Doesn't work with update CVE-2019-1181.

After install this update https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1181 on Windows 10 version 1607, LTSB.
After uninstalling this update everything works fine!

Same here...waiting for a fix.

https://github.com/stascorp/rdpwrap/issues/846#issuecomment-518548281


New version: Setfield v0.4.1

Registering package: Setfield
Repository: https://github.com/jw3126/Setfield.jl
Created by: @tkf
Version: v0.4.1
Commit: c2d0c2bf947b15f7813cd09db459bc419b2d7d28
Reviewed by: @tkf
Reference: https://github.com/jw3126/Setfield.jl/commit/c2d0c2bf947b15f7813cd09db459bc419b2d7d28#commitcomment-35260598

Can I cancel this for the moment and re-register it later?


Use inspector warning colour on properties in inherited scenes.

According to comments, the inspector uses the warning colour on the editable children of instanced scenes to warn that the changes to the properties could be lost. This PR applies the same rule to inherited scenes for consistency.

How would one lose changes from inherited scene properties? In case of instances, they are lost when disabling editable children. But there is no option that removes inheritance and discards data AFAIK.

Sorry, I kind of forgot about this, but yeah, on reflection, I'm less confident now about whether this should apply to inherited scenes or not. I really thought of it more as a signifier of instancing or inheritance, but it kind of isn't that. Hmm, since I've been exploring the usage of this colour as design pattern, I will think on it some more and reconsider whether I still feel this is worthwhile. I think in general, some firmer design rules need to be agreed.


inline Entry::clone

It showed up in in the profiler.

Thanks for the PR, I have fixed the ci issue on master, can you rebase it?

Not exactly what you requested, but I am a git noob... I hope it works.
I also have another PR ready once this is done to address the repeated flag reads.

Or just add the inline yourself, a PR is overkill.

Thank you!


Analytics pageview on /guides is no longer being recorded after router update

On page load, GA is loaded just fine. But I suspect it's b/c of the router change that no longer creates new pages as you navigate.
Repo:

Goto https://elements.polymer-project.org/guides/
Click to other guides

Network panel only shows one request for the collect endpoint.

:(

We removed a few infinite async loops. :'(


Quotation - Amount in line is not update

In Quotation page, after the Qty changed, Amount on Quotation line is not updated automatically.

fix: https://github.com/nfco/netforce/commit/57cf1ddc317a954a398b44b3a43cbd8188b8d8f0


Add missing DescribeExportTasks

Add missing DescribeExportTasks.
It is missing from the IAM Visual Editor as well.
Issue #, if available:
Description of changes:
Add missing DescribeExportTasks.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you for your feedback! I am checking this with the AWS Application Discovery Service writer, who will follow up.

Hello again! We've reviewed your PR and you are correct. This page is automatically generated from the service’s files and we’re working with the teams to get it updated. When it’s ready, we’ll accept your pull request. Thanks for helping us make the docs better!

We are still waiting on the Application Disovery team to update the source.

I'm notifying the Application Discovery team again.

I contacted the Application Discovery team again.

I contacted them again. We have not forgotten about this issue.

I confirmed that it's been fixed. Thanks for reporting this!


It does not render the Map on Firefox

Basically everything work, but the map just does not load in Firefox
Trying the url with Chromium works, so I assume its a Browser compatibility problem.

Gonna need more info because it works just fine on firefox for me.

Interesting. I checked with a Private window and no extensions enabled and it still does not render the map.
The Devtools Network tab shows no error. But i just looked into the Console tab, which shows a WebGL error.
deck: Failed to create WebGL context: WebGL creation failed:
* WebglAllowWindowsNativeGl:false restricts context creation on this system. ()
* Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS) undefined (https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js)
    onError https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:902
    (Async: promise callback)
    start https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:52
    B_ https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:902
    aH https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:953
    cO https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:953
    C_ https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:40
    od https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:40
    hC https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:40
    Pc https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:38
    Q5 https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:40
    nu https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:40
    aR https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:40
    K https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:25
    Ve https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:25
    (Async: EventHandlerNonNull)
    <anonym> https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:25
    <anonym> https://honzaap.github.io/Pathfinding/assets/index.cbdbad04.js:25

It doesn't look like something I can change. According to this post you could try openinig the about:config page and search for webgl.force-enabled, then setting it to true if it's not already. You might have to restart the browser after that.

A full system upgrade and a restart fixed the issue. (I hate my GPU sometimes.)
Sorry to bother you.


[feat] automatically set thread title.

Summary

automatically set thread title based on last message.

it looks like it includes commits from its previous pr:
https://github.com/ainft-team/ainft-js/pull/286
how about reviewing it, once its previous pr is merged?

Thank you for review @platfowner! now merging...


Test cases

Purpose
To write the test cases for the key operations of Dropbox connector
Issue Title: Introduce a Ballerina connector for Dropbox REST API
Issue link: https://github.com/ballerina-platform/ballerina-library/issues/7054
Examples
Checklist

[x] Linked to an issue
[ ] Updated the changelog
[x] Added tests
[ ] Updated the spec
[ ] Checked native-image compatibility

@lnash94 @Nuvindu @shafreenAnfar @NipunaRanasinghe please review.

Hi @rahul1995
If you don’t mind, could you please sync the PRs with the main branch? I noticed a few previous commits in client generation
showing up here.

@lnash94 my bad! I have updated it now.

@NipunaRanasinghe thanks for pointing that out. Added the README file.
A small suggestion: Please update the project structure in Step 1 point 4 of https://ballerina.io/learn/create-your-first-connector-with-ballerina/ so that new connector modules also follow this practice (probably the reason why I missed it too).

@NipunaRanasinghe thanks for pointing that out. Added the README file.
@rahul1995 LGTM! Approved the PR

A small suggestion: Please update the project structure in Step 1 point 4 of https://ballerina.io/learn/create-your-first-connector-with-ballerina/ so that new connector modules also follow this practice (probably the reason why I missed it too).

Yeah your suggestion makes sense. We'll update the section with the expanded view of tests/ directory. Thanks for pointing that out! 🙂


In Kubeflow deployment without MLflow we cannot deploy model with Seldon from Minio

The secret to accessing Minio for models is created only if the deployment has MLflow added.
There is a valid use case for deploying a model stored in Minio without MLflow (ie sklearn model hosting using Seldon).

Workaround - manually create a secret:
apiVersion: v1
kind: Secret
metadata:
  name: seldon-init-container-secret
type: Opaque
stringData:
  RCLONE_CONFIG_S3_TYPE: s3
  RCLONE_CONFIG_S3_PROVIDER: minio
  RCLONE_CONFIG_S3_ACCESS_KEY_ID: minio123
  RCLONE_CONFIG_S3_SECRET_ACCESS_KEY: minio123
  RCLONE_CONFIG_S3_ENDPOINT: http://minio.kubeflow.svc.cluster.local:9000
  RCLONE_CONFIG_S3_ENV_AUTH: "false"


Added multiple random Responses

Instead of giving a single response every time, this can provide a random response from the set of given responses, all you need to do is enter multiple response in new line while creating/editing story.

The expected behaviour for the same is as follows,

Interactive UI to add/edit multiple responses
responses are stored in a list in the backend and a random response is returned from this list.

Please resubmit your pull request with these changes and we'll be more than happy to merge it.


Improve client-server protocol

Consider features at https://github.com/vega113/Wiab.pro

After some improvements in the websocket transport and fixed cs-protocol bug, this issue has no priority


Test whether the stubs work right with MinGW64

The Appveyor build shows up as successful, but it seems Appveyor still had two problems:

Related to cmake
Somehow it seemed like it couldn't find the executable(s)

@Andne - it builds CppUTestTests.exe and CppUTestExtTests.exe, but it attempts to run AllTests.exe. I thought our latest cmake build handles this itself via ctest?

The first one is just the results of the cmake generation, I haven't figured out how to keep it from showing up as an error yet, but it doesn't interfer with the build, so I've ignored it.
Yeah, I don't know how ctest does/doesn't work, so for now I was just trying to tie into the test logic I already had running for the Visual C++ builds.

Ah, I see. Well on Travis, ctest is part of running cmake. So maybe we can glean some information from there. Otherwise, simply running the executables would serve just fine. At least it seems I got my error fixed.
Great stuff -- this is really helpful.

Part of the reason I was avoiding CTest was since I don't know how to make its results show up on the tests tab.  I have that working for Visual C++ and thought it would be nice to have for MinGW as well.  I don't know if anyone actually pays attention to it, but it seems like a nice feature.


New model: eq-3, HmIP-BDT

Manufacturer: eq-3
Model: HmIP

Device information

https://de.elv.com/p/homematic-ip-smart-home-dimmaktor-hmip-bdt-fuer-markenschalter-P143166/?itemId=143166
Dimming actor for outlets

Home Assistant Device information

Checklist

[x] I have created a single PR per device. When you have multiple submissions please create separate PR's.
[ ] For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
[ ] For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

Data taken from technical specs of manufacturer.
11 Technische Daten
Geräte-Kurzbezeichnung: HmIP-BDT
Versorgungsspannung: 230 V/50 Hz
Stromaufnahme: 0,35 A
Minimallast: 3 VA
Maximale Schaltleistung: 80 VA
Leistungsaufnahme im
Ruhebetrieb: 0,4 W
Dimmverfahren: Phasenabschnitt
Lastart: ohmsche und kapazitive Lampenlast
Leitungsart u. -querschnitt: starre und flexible Leitung, 0,75 - 1,5 mm²
Installation: nur in Schalterdosen (Gerätedosen) gemäß DIN 49073-1
Schutzart: IP20
Schutzklasse: II
Geräteschutz: Überlastsicherung, Temperatursicherung
Umgebungstemperatur: 5 bis 35 °C
Abmessung (B x H x T ): 71 x 71 x 37 mm
Gewicht: 47 g
Funk-Frequenzband: 868,0-868,6 MHz
 869,4-869,65 MHz
Max. Funk-Sendeleistung: 10 dBm
Empfängerkategorie: SRD category 2
Typ. Funk-Freifeldreichweite: 270 m
Duty Cycle: < 1% pro h / < 10% pro h

I don't think this PR was a good idea. As the description already mentions, it only provides the standby power. There is no way to specify the power the connected lamp draws (which is the part we are probably actually interested in), so a separate manual power sensor must be created for that.
I know that we cannot do better because we don't know what lamp is connected. But I argue that not adding official support for devices is better than this. PowerCalc should either provide a way in the GUI to set the fixed power that a connected lamp draws for devices like this one (while making it very clear that this needs to be specified to measure anything useful) or not add the device at all - that way, the user will know that the device wasn't automagically found by PowerCalc and needs to be manually added.
Just my 2 cents.
Same goes for #2692 - #2701, by the way.

I don't think this PR was a good idea. As the description already mentions, it only provides the standby power. There is no way to specify the power the connected lamp draws (which is the part we are probably actually interested in), so a separate manual power sensor must be created for that.

Sorry, but I have to disagree strongly. You are entitled to you opinion which is as mine is as well byased by how you use HA and powercalc. I in contrast to you would actually really love to have at least the option to configure a seperate standby and "in-use" sensor-pair. Tracking standby is very important to me. But just ignoring this for a moment...
This smart device is one of many similar devices such as all SONOFF, Shelly etc. that are used in homes to replace dumb light switches without needing smart lamps. With your argument you would deny all of them as well (such as pm mini gen3 and similar).
The main difference to point out here is that only the device you added your comment here (eq-3, HmIP-BDT) and HmIP-FDT) are exposed ad lights by the corresponding integration of Homematic compared to the other devices I added which are exposed as switches.
If you check the difference in your powercalc installation you will notice that switches do have the option to change the fixed power consumption in th UI. This is missing when the device type is light.

I know that we cannot do better because we don't know what lamp is connected. But I argue that not adding official support for devices is better than this.

No, I don't agree. You do not need to use the device but others want to. They are not bothing anyone as all the devices I do not use and are present in the database do not bother me.

PowerCalc should either provide a way in the GUI to set the fixed power that a connected lamp draws for devices like this one (while making it very clear that this needs to be specified to measure anything useful) or not add the device at all - that way, the user will know that the device wasn't automagically found by PowerCalc and needs to be manually added.

This actually is a very good point. Please add a feature request for light devices to be able to change fixed power consumption the same way as with switches. But wait... Don't forget that this smart light switch is a dimmer so, the feature requst needs to take this into account and make it possible that the user can at least choose between fixed and linear strategy. I guess the UI needs to expose something more like with covers. Please open a request for this.
When it comes to "making it very clear..." users installing these devices pretty much are aware of this fact, same as smart plug users know that they need to specify the power draw and it is not magically appearing.

Same goes for #2692 - #2701, by the way.

No, it does not.

When it comes to "making it very clear..." users installing these devices pretty much are aware of this fact, same as smart plug users know that they need to specify the power draw and it is not magically appearing.

I disagree. For devices without an exchangeable load in the library and smart plugs with integrated power metering, you don't need to specify the power draw manually. When a new user installs PowerCalc for the first time and it detects 20 devices, the UI has to make it obvious to the user that there's one or two of them that don't have integrated power monitoring and need manual configuration. I don't think everybody knows off the top of their head whether HmIP-BDT supports power monitoring or not and thinks through all the implications.

The main difference to point out here is that only the device you added your comment here (eq-3, HmIP-BDT) and HmIP-FDT) are exposed ad lights by the corresponding integration of Homematic compared to the other devices I added which are exposed as switches.
If you check the difference in your powercalc installation you will notice that switches do have the option to change the fixed power consumption in th UI. This is missing when the device type is light.

Ah, that's a crucial piece of information. I didn't know that. So I just got unlucky; I don't have any of the other devices, so this is the only one I tested. I agree, the option to override fixed power consumption should be added for dimmers and lights.

Added the feature request: #2754

@mintar Thanks for chiming in. there is a feature where fixed consumption of connected appliance can already be set for smart_switch devices during discovery flow as @dagobert also indicated.
Makes sense to also do that for lights, which this profile is about, so thanks for the feature request. I've overseen that the device_type was light for this PR, and merged without considering that.
Need to find some time to actually implement this feature. Probably will have a look next weekend or week after.
There is a possibility to set config_flow_discovery_remarks in model.json which will be presented to the user in the GUI.
So we might add some remark in the meantime that these profiles will only capture self-usage of the device, but not of the connected light.

We can make a remark but I still don't think that anyone buying these devices thinks that powercalc will magically measure the dumb equipment power draw.
But adding the power draw option is important, I agree


Add 'math' topic to relevant exercises in track config

The new site lets people filter optional exercises by topic, and this
makes it easy for people to skip past them.
This is important since the math-y exercises are not key to learning
the language, and a lot of people find them intimidating and demotivating.
This updates any 'mathematics' topics to be 'math' since it's shorter
and won't get cropped in the UI.
It also removes the math topics for any exercises that are not in the
canonical math-y list.
exercism/exercism.io#4110

@celavek this is not a very controversial PR, so if I don't hear anything to the contrary in the next 2 days I'm going to go ahead and merge it.


Interop interfaces

Hi,
I'm using the debug engine interop interfaces (as well as CLRMD) and some methods accept IntPtr instead of the "proper" interface (e.g. IDebugClient.SetEventCallbacks). I've tried to replace the IntPtr with the "real" interface and use it - and it works just fine (maybe adding MarshalAs with Unmanaged.Interface for safety... but it works regardless).
Would it be possible to set the interfaces? I can certainly do that.
Is there a reason to not do it?
Pavel

Thanks for the report!
I begun the work to change those from IntPtr over to the real interfaces yesterday, but I see I missed a few.  I just fixed the remaining ones I could find.  Please report any more issues like this (or send a pull request if you have the interest in fixing them yourself).

Is there a reason to not do it?

Nope!  These should definitely be the real interfaces and not IntPtr.  Originally the interfaces here came from another team within Microsoft who used them slightly differently.  I hadn't gotten around to updating them until this week.
Thanks!
-Lee Culver


Add mesos-slave versions 0.25.0 and 0.26.0 for Centos 7 and Ubuntu 14.04

Hi --
I added support for mesos-slave version 0.25.0 and 0.26.0 for both CentOS 7 and Ubuntu 14.04.
Thanks!
Kevin

+1


ML Fusion Labs Logo in Navbar Should Be Centered

Description
The ML Fusion Labs logo in the navbar is not currently centered, which impacts the visual balance and user interface. For a cleaner and more professional appearance, the logo should be centered to improve the overall layout.
Steps to Reproduce

Navigate to any page with the navbar.
Observe that the ML Fusion Labs logo is not centered.

Expected Behavior

The ML Fusion Labs logo should be horizontally centered in the navbar for a balanced and consistent design.

Actual Behavior

The ML Fusion Labs logo is misaligned in the navbar and does not appear in the center, disrupting the visual harmony of the navigation bar.

Screenshots

Additional Information
I am currently contributing as a participant in GSSoC'24 Extended Edition. I would like to kindly request a Level 1 tag for this contribution.
What browser are you seeing the problem on?

[ ] Firefox
[X] Chrome
[ ] Safari
[ ] Microsoft Edge

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@ansiace assigning this issue to you.
make sure to complete this very fast.


orthographic mistake setup-core-components.md

orthographic mistake 'ByA'

Docs Build status updates of commit c27d930:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

power-platform/guidance/coe/setup-core-components.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


user projects

now that we have the ability to log-in, each user in the main pkpd app should have a list of projects that they are working on. There is a many-to-many relationship between users and projects.
Each user, while logged in, will have one currently active project, and everything that the user sees in the different apps (data analysis, simulation, inference etc) will depict the state of the currently active project.
Eg.

you upload a data file while project A is active, that data file is associated with project A, and if you log back into the app and select project A, the data file will be already there.
If you perform an optimisation to get a set of likely parameter while project A is active, that optimisation result (parameters, associated data file and model) will be associated with project A, and be available to view whenever project A is active

The scope of this issue is to:

create a project model and the many-to-many relationship
add UI to be able to create a new project, see a list of previously created projects, and select the currently active project

@martinjrobins
That seems doable! I am guessing we at some places we just render the web interface personalised to the user?
Probably exceeding this ticket, but something I am not sure about is: how will we distribute computing resources once we have multiple users interacting with the app? Is this done automatically by the server?

yes, that's right, each tab should be specific both to the user, and the currently active project.
re distributed computing resources, this is indeed the responsibility of the web server, so in general we don't have to worry about this. We will, however, have to worry about this for long-running simulations and inference algorithms.

yes, that's right, each tab should be specific both to the user, and the currently active project.
re distributed computing resources, this is indeed the responsibility of the web server, so in general we don't have to worry about this. We will, however, have to worry about this for long-running simulations and inference algorithms.

Ah ok thanks! That is what I was wondering.


named key - PUT and DELETE support

Combined previous DELETE PR with PUT support.
Pending are tests for  PUT authorization - held off because those are going to b identical to the DELETE auth tests, and I'd like to find a way to do that sanely.

Looks good overall. I just have some minor stylistic / readability issues. Also, we should make sure to document in the readme any conventions we added to rspec such as shared.


Open namespace/module and fully-qualified name?

Hey guys,
I noticed something lately.
Let's say User is defined in Namespace.ModuleB, and my cursor is located at $
module Namespace.ModuleA

let f (u: $User) = ()

Then I am suggested to add open ModuleB instead of open Namespace.ModuleB.
Shouldn't we prefer to use the fully qualified name by default, so as to avoid potential ambiguities?

Yes, fully qualified names seem better.
I don't recall why we use short names; maybe @vasily-kirichenko remembers the reason :-).

I do not remember either :) It seems the right thing though:
namespace My.Long.Name.Space.Here

module A = let foo x = x
module B =
    open A
    let x = foo 1

Do you think that the following is better?
namespace My.Long.Name.Space.Here

module A = let foo x = x
module B =
    open My.Long.Name.Space.Here.A
    let x = foo 1

Can we easily distinguish between 'top level modules' (1 module for the entire file) vs explicit modules like in your example?

I think using open A might be wrong in some cases if there are multiple A modules from different namespaces. But we don't yet see any bug related to this; so keeping short names is good because it is aesthetically pleasing.


iOS 10 issue : need to press home button to see the permission alert

I installed this plugin and it is working fine on all major platform. But it is having an issue when I used it on iOS 10. When I click on button to select a image, the permission box appear in the background. I need to press home button and again need to open the app then it displays photo library.

I have the same problem. I did the project in Win8 32bit and I copy whole code and try to build project in Mac. The Error show me that Base64x.... something. I create new project and copy all Files in WWW. everything work fine but only imagepicker is not work. Then I install plugin again and now I got this problem.

It happened to me too. Do you have any solution?

I fixed it. For me it's because i added "Content-Security-Policy" in the index.html. I just comment this line and it's worked.
see my code below. I copied it from  of index.html
//Do not use this line for IOS

@best1678  "Content-Security-Policy" would not be the problem, just make sure all the access file types is included and allowed. providing my app setting for reference
`

`

@januslo  I gonna remove my comment in this lane and try it one again. By the way can U please check this line? is it correct?

@januslo  I'm really sorry. I can't test it now because This problem occurred only in IOS. I gonna check it and reply to you later.

I am current running this line on my app.
发自我的 iPhone

在 2017年2月22日，下午1:00，best1678<EMAIL_ADDRESS>写道：
@januslo I'm really sorry. I can't test it now because This problem occurred only in IOS. I gonna check it and reply to you later.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

It's rare but both solutions works. Removing the line and adding more parameters to the meta tag.


Packmule pkg installation user/group creation failure

Problem:
Installing packages under $pkgroot fails if "pkg" cannot lock the user or groups files. Discovered when loading custom install image with mongodb.  Need to find a way to save (worst case is drop) the created user and groups needed by installed programs.
Example:
my $pkgroot = "/tmp/bsd_iso_pkgs/";
`pkg install -r $pkgroot mongodb`

Fixed, but pre-install scripts can still cause issues. Added the --no-pkg-scripts option as a last resort workaround.