Revamped search interface to use the support library SearchView

The new SearchView looks really nice, but I've seen two issues when giving it a try:

Once in the search activity (after the first search), if you try to search again and you press on a recently search item, the search input doesn't get updated, so you can't see the search text nor search again.
In b201ba888504b145fa5146cb7ef25151ea71fca4 I added a functionality to allow editing the last search. I find this useful for fixing typos or when adding more search terms. This feature is gone with the new SearchView.

Good catches. I'll fix those issues.

That should resolve the remaining issues. In the results activity, the search view is now permanently expanded to make it easy to refine the query.

Anything else I need to do here?

Sorry, I haven't had time to test it yet. I'll try to look at it tonight.

I've been testing this and I still have some issues.

First, I think you accidentally remove this line when merging: https://github.com/jonan/ForkHub/pull/166/commits/bbc5bc7824c784fdc589767561348a620920099b#diff-dd1e125e3fae1baf04c3bc756062096eL39. Please rebase your branch with current master so we can fix it.

I find weird that after going to the search view, pressing back sends you to the home activity with the search bar active. I think it should be deactivated once you go to the search view.

I don't like how the button to create a new issues moves when you press search. Can we hide it or find another solution?

Those commits should solve your first two bullets. I'm not quite sure what you mean by the third one. In the Repository view on the Issues tab, pressing the search icon will hide the "+" in the toolbar (technically, it's moved to the overflow menu). Are you seeing different behavior?

I was, but you seem to have solve it with the new searchView listeners.
Everything looks fine now, I'll do a bit more testing and merge it tonight if nothing comes up.
Many thanks!

Sorry, I found one more issue (hopefully the last one).
There's no search button in IssueSearchActivity, so after searching for an issue, you can't search again without going back :disappointed:
BTW, note that you're including some useless imports and that we don't indent case statements.

I'll work on those issues.
Is there a way to change how the IDE formats switch statements? I'm using the official Android code style, which indents case by defult, and I couldn't find an option in Android Studio to change that behavior.

Sure, Settings > Editor > Code Style > Java > Wrapping and Braces > 'switch' statement.

I've added three very picky comments, the rest is perfect and ready for merge :wink:

There you go! Props to you for having the patience to go through everything with such a fine-toothed comb :stuck_out_tongue:

Thank you @nwalters512! Expect a new release soon :+1:


Allow selecting color of text when drawn

Right now, text can only be draw in white. It would be helpful to me if I could pick which color the text was drawn as.

What do you think of making the font characters invert the pixels where they are drawn? Then text is white when drawn over a black background, and black when drawn over a white background.

In that case, you could $draw_filled_rect over the text area with your desired background color prior to text rendering. Even the current mode of text rendering doesn't overwrite the background -- in addition to performance reasons, doing it this way allows more freedom, particularly with a large font where you might not want the background of each glyph automatically cleared when rendering.

That sounds good as a flexible solution without eating too much performance!

Pushed -- let me know if there's any issues. Thanks for the report!


tests/dart2js/boolean_conversion_test fails with sound null safety

tools/test.py -n dart2js-hostasserts-strong-linux-x64-d8 dart2js/boolean_conversion_test fails.
/cc @rakudrama - we never quite wrapped our discussion about this one.

The test relies on making a specific decision when faced with an inconsistency.
I think we could parlay the inconsistency into any failure, for example  a ? b : c and !a ? c : b might simplify differently if we know a is ⊥.
In one part of the test we have bool b = null as dynamic; with an elided (trusted) always-failing check.
The HTypeKnown for the elided implicit as bool narrows to ⊥.
We should experiment with a Halt-and-Catch-Fire (HCF) instruction which throws an Error if reached.
We would inject HCF after any HTypeKnown that strengthens to ⊥.
HCF would take the strengthened ⊥ value as an input and report it using the most concise code pattern possible.
Inserting a throwing instruction at the point of strengthening detects the inconsistency without inserting useless throws after calls to functions that always throw. If the function returns ⊥, either it always throws, or a return is an infeasible path due to a strengthening to ⊥, so the responsibility to HCF is pushed into the function.
Compiling without --omit-implicit-checks would give a better diagnostic by identifying the earliest failed check that cascaded into the detected inconsistency.
Dead code elimination would be modified to remove code dominated by HCF.
It is not necessary to extend dead code elimination test out how often this occurs, but I expect we well get some tree-shaking benefit from doing so. It would be interesting to see if inserting HCF and deleting code that it dominates might be a net win in code size.
See also #43456.


Native posix advanced uart

Add SERIAL_SUPPORT_INTERRUPT to native_posix serial driver
Add dynamic configuration (baud and RTS/CTS) to native_posix serial driver
Optional host device to zephyr serial device mapping

we're going to look at changes to the native_posix timer model that will support external interrupt sources. Meanwhile I'm closing this PR. Thanks for your time and input.


Support RestSharp 105.0.1

I seem to be getting an
Additional information: Method not found: 'Void RestSharp.RestClient.set_BaseUrl(System.String)'.

when calling
client.Update(CounterWidget, new Numbers {Delta = 1});

from a project that already depends on RestSharp 105.0.1. Any plans to support this version as well?
Edit:
there seems to be breaking changes
https://github.com/restsharp/RestSharp/blob/master/releasenotes.markdown#new-featuresimprovements

I'd gladly take a pull request to support the latest version of RestSharp.


Failed to set permit join to false

Description of problem:
After installing the latest version of zigbee2mqtt 1.19.0 this error appeared in the log:
Zigbee2MQTT:error 2021-06-02 15:39:04: Failed to set permit join to false

All my zigbee devices are perfectly working but I’m wondering if joining procedure has been broken.
Unfortunately I don't have any other zigbee devices to test it.
I’ve upgraded HA to 2021.6.1 and zigbee2mqtt to 1.19.1 but those errors are still there….
When pairing is activated, this error also appears:
Zigbee2MQTT:error 2021-06-02 23:17:37: Failed to call 'BridgeLegacy' 'onMQTTMessage' (Error: SRSP - UTIL - ledControl after 6000ms
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:37:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))

Zigbee2mqtt add-on version (if edge, please report commit hash):
><EMAIL_ADDRESS>start /app

Your entire configuration from the frontend (with sensitive fields redacted):
data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://homeassistant
  user: ***********
  password: *************
serial:
  port: /dev/ttyUSB0
advanced:
  rtscts: false
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: '-d -d'
  log: false
zigbee_herdsman_debug: false

Running platform (details from Suypervisor > System)
// Example
Core: core-2021.6.1
Supervisor: supervisor-2021.05.4
Operating System: HassOS 5.13

Your logs from Home Assistant Supervisor
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing...
[15:38:44] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing...
[15:38:45] INFO: MQTT available, fetching server detail ...
[15:38:46] INFO: Previous config file found, checking backup
[15:38:46] INFO: Creating backup config in '/share/zigbee2mqtt/.configuration.yaml.bk'
[15:38:46] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[15:38:47] INFO: Handing over control to Zigbee2mqtt Core ...
><EMAIL_ADDRESS>start /app
> node index.js
Zigbee2MQTT:error 2021-06-02 15:39:04: Failed to set permit join to false
Zigbee2MQTT:error 2021-06-02 23:17:37: Failed to call 'BridgeLegacy' 'onMQTTMessage' (Error: SRSP - UTIL - ledControl after 6000ms
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:37:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))

Error has disappeared after installing zigbee2mqtt 1.20.0-1


Telegram failed with: Unable to find channel. The channel is non-existing or non-public.

Recently been receiving the below error with all public telegram channels.
Exception: Unable to find channel. The channel is non-existing or non-public. in bridges/TelegramBridge.php line 46

index.php(68): RssBridge->main()
lib/RssBridge.php(39): RssBridge->{closure}()
lib/RssBridge.php(37): CacheMiddleware->__invoke()
middlewares/CacheMiddleware.php(44): RssBridge->{closure}()
lib/RssBridge.php(37): ExceptionMiddleware->__invoke()
middlewares/ExceptionMiddleware.php(17): RssBridge->{closure}()
lib/RssBridge.php(37): SecurityMiddleware->__invoke()
middlewares/SecurityMiddleware.php(19): RssBridge->{closure}()
lib/RssBridge.php(37): MaintenanceMiddleware->__invoke()
middlewares/MaintenanceMiddleware.php(10): RssBridge->{closure}()
lib/RssBridge.php(37): BasicAuthMiddleware->__invoke()
middlewares/BasicAuthMiddleware.php(13): RssBridge->{closure}()
lib/RssBridge.php(37): TokenAuthenticationMiddleware->__invoke()
middlewares/TokenAuthenticationMiddleware.php(10): RssBridge->{closure}()
lib/RssBridge.php(34): DisplayAction->__invoke()
actions/DisplayAction.php(54): DisplayAction->createResponse()
actions/DisplayAction.php(89): TelegramBridge->collectData()
bridges/TelegramBridge.php(46)

Query string: action=display&bridge=TelegramBridge&username=disclosetv&format=Html
Version: 2024-02-02 (git.master.80c43f1)
Os: Linux
PHP version: 8.2.20

Maintainer: @VerifiedJoseph

I can reproduce this issue locally but not on the official instance or when using the docker image.
How are you running rss-bridge?
I'd recommend switching a docker based setup if possible. See the link below for how.
https://github.com/RSS-Bridge/rss-bridge?tab=readme-ov-file#install-from-docker-hub

I am currently running rss-bridge using the rssbridge/rss-bridge:latest docker image.
I am able to reproduce with the official  instance here as well as local:
https://rss-bridge.org/bridge01/?action=display&bridge=TelegramBridge&username=disclosetv&format=Html

Looks like the channel can't be viewed or previewed outside of telegram's app.

I had the same thought, but I tried five different public channels, and they all produced the same result. Have you been able to get it working with any channel? I use RSS-Bridge with multiple channels, and they all stopped working around the same time, so I suspect something may have changed on Telegram’s side that is causing this issue.

Have you been able to get it working with any channel?

Yes. with @rssbridge, @telegram and a few others.


Fix "yarn start:server" in dev mode for new repositories

After setting the project to ESM ( https://github.com/serlo/ece-as-a-service/pull/103 ) the command yarn start:server does not work in new repositories. There is a strange error:
[start:server    ] wait  - compiling /_error (client and server)...
[start:server    ] error - ./node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[3].oneOf[7].use[1]!./node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[3].oneOf[7].use[2]!./node_modules/katex/dist/katex.min.css
[start:server    ] /home/runner/work/ece-as-a-service/ece-as-a-service/tailwind.config.cjs:17
[start:server    ] export {};
[start:server    ] ^^^^^^
[start:server    ]
[start:server    ] SyntaxError: Unexpected token 'export'
[start:server    ]     at compileFunction (<anonymous>)
[start:server    ]     at runMicrotasks (<anonymous>)

However yarn next dev works and once we have run this command in the repo yarn start:server works again.

ts-node seems to be the problem. Let's take the following source code
// code in test.ts / test.js

import express from 'express'
import next from 'next'

const app = next({ dev: true })
const server = express()

await app.prepare()

server.all('*', (req, res) => app.getRequestHandler()(req, res))

server.listen(3000, () => console.log('ready'))

Running yarn ts-node test.ts fails while yarn node test.js runs smoothly


fix terminal and preview running url

I dont know why after making this open source code-server lost functionality in previewing url where the app is running in the container and bash terminal lost its color . when they will be available again??

This is a coder.com issue.
https://github.com/codercom/bugs/issues/359
https://github.com/codercom/bugs/issues/361
These issues will have accurate tracking data :)


Resolve Heroku PostgreSQL connection

Resolve the error "ValueError: invalid literal for int() with base 10: '6 (Ubuntu 10'" when try to connect with Heroku PostgreSQL

Hi, thanks for the patch, but this is already being managed downstream by debian (and ubuntu?). Debian packaging, apparently, introduced the inconsistent PostgreSQL version string and resolved the incompatibility local to their packaging system with a patched py-postgresql. Alternatively, using a different build of PostgreSQL with an unmodified version string will resolve your issue.

Hi, the version of PostgreSQL that I'm using is Heroku's default and it's not possible to change how the version string is returned. I am currently using the fork with these changes and it has worked normally


Variance of letter case on logs

Hello Prometheans,
Unsure whenever this is best suited as a bug report, but I've observed different letter casing in log lines and was wondering whenever this is indented.
I think there might be a pattern but would like to confirm. It seems that for components starting and stopping (e.g. scrape manager, remote write, tsdb, Prometheus itself) log lines are capitalized.
For everything else that appears to be operational (e.g. scrape manager), it seems to be lower case.
However, sometimes even this pattern is broken (e.g. remote write).
Do we have any consensus on when to use which? I couldn't find any documentation that indicates that, and I'd be happy to fix/create anything that might need it.

Log messages should be capitalised, however for go errors should not be as they'll likely be prefixed. That can sometimes result in an uncapitalised log message. If there's cases that are easy to fix, we should fix them.

I can work on this.

Create a fork on github and push it to your fork.

ping me if you need any help @thaniri, I think a first step you can do (mostly for the benefit on getting familiar with the different Prometheus areas) is to identify which are the different areas we have to look for the log lines (e.g. storage, tsdb, scrape, service discovery).
Then, make a checklist as part of this issue so that we can keep track of which areas we have scanned already. Then, either you (or others) can each take up on the different areas and submit the PRs for them.
I think this makes it easier for everything, you can keep track of what you're doing and the reviewers only need to look at a particular area at a time.

It is my personal opinion that creating a different PR for each package within the repository will result in such a trivial change taking too much time as too many people will need to get involved in this change. Really this PR could have probably been done with a sed command and some review :)
Here is the PR ready for review. I am hoping that I have followed the contributing guidelines correctly.
https://github.com/prometheus/prometheus/pull/7043

Whatever works for you, works for me 😄

Tests pass now, just needed to keep pulling from master and kicking off new CI builds until it worked :)

I think we can close this now @brian-brazil, right?


I found a broken link

The nearest header is: https://docs.docker.com/edge/engine/reference/commandline/build/#build-with-path
The text of the broken link is: ADD

Thanks for sharing this issue. The docs have changed since you reported the issue, so some context was lost. The link for the "ADD" text now links to https://docs.docker.com/engine/reference/builder/#add . If there's still any issue, please let us know.


find the median of a stream added in Cpp

Please read the new Contributing.md and make changes in your PR accordingly. Thank you


sqlite: view: reuse connection

Makes for an easier resource management than before, but still is pretty messy as view could re-connect and leave the new connection hanging.
Connection mgmt will get revisited a little later for something more comprehensive.

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.03 :tada:

Comparison is base (7f99053) 79.34% compared to head (a00db2d) 79.38%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
+ Coverage   79.34%   79.38%   +0.03%
==========================================
  Files          11       11
  Lines         581      582       +1
  Branches      101      101
==========================================
+ Hits          461      462       +1
  Misses        109      109
  Partials       11       11

Impacted Files
Coverage Δ

src/sqltrie/sqlite/sqlite.py
85.79% <100.00%> (+0.08%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


refactor: Simplify logic around get method color

Description
This small refactor eliminates the need for switch-case.
Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[ ] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

Nice. Merged! Thanks @iamsushantk !


Clean up test bundling implementation

This will happen after #1205 is merged to develop.

See https://github.com/leancodepl/patrol/issues/1214

This is done.


147 use react for regestration form

resolves #147

Links

https://blog.jakoblind.no/css-modules-webpack/
https://medium.com/clover-platform-blog/modular-scss-and-why-you-need-it-6bb2d8c40fd8
https://github.com/webpack-contrib/css-loader
https://github.com/css-modules/css-modules
https://www.valentinog.com/blog/webpack/
https://reactjs.org/docs/getting-started.html


Missing Admin Bdy Shapefiles not being logged correctly

When the admin boundary shapefiles can't be found, a fatal log entry should be output. The code should trap this, but it's not working
Failing to trap this causes a large number of SQL errors when trying to prep the admin bdys. Making it hard for users to determine the source of the errors

Closing as related to issue #29


fix reading scope start

in case when the mdb file is out of sync, we might endup with
start_instruction being null

it is regression introduced by
7c8e0f767d7b2f652a430e4e26f1d98a20f9e125

It is cherry-picked from upstream cecil to fix bugs #58173 and #58511 for d15-4 XA


[Slider] RTL behavior is broken.

Followed the guide, don't have problems with other components, been using material ui for over 7 month on this project, RTL is just fine.
tried implementing a Slider, but it's broken.

[x ] This is not a v0.x issue.
[ x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

this should not happen
https://i.gyazo.com/9258b17c7bc7aa1764c939f4d9382d7a.mp4
Current Behavior

this what happens
https://i.gyazo.com/9258b17c7bc7aa1764c939f4d9382d7a.mp4
Your Environment

Tech
Version

Material-UI
^3.0.1

React
latest

Browser
chrome

TypeScript
x

etc.
lab is ^3.0.0-alpha.18

Confirmed in https://codesandbox.io/s/wym4m8jw6l
It's working on the current docs. Seems like an issue with jss-rtl

It's really not clear, first it says Internally, we are dynamically enabling this plugin when , I though that part 3 was explaining what happens internally, and afterwards you can look at the demo, and see that they don't use part 3 at all, and it works fine.

It's really not clear, first it says

@wangwenpei I agree, it's not clear. What do you think of:
-Internally, we are dynamically enabling this plugin when direction: 'rtl' is set on the theme.
+Internally, we are dynamically using this plugin when installed and direction: 'rtl' is set on the theme.

Why isn't it dynamically used in Slider ? :(
right now I need to use the RTL wrapper in slider and switch

Why it isn't dynamically used in Slider ?  Maybe we can add warning message.

@eps1lon Still, I don't understand why setting 'direction': 'rtl' isn't enough for the Slider to flip?

Why it isn't dynamically used in Slider ? :( right now I need to use the RTL wrapper in Slider and Switch

I don't understand. The JSS plugin has to be installed. We don't do it by default because most people don't need it. This way, we save bundle size for 80% of the people. This is step 3.

@eps1lon so theme.direction set to rtl results in 'dynamically' flipping inline styles only, while loading jss-rtl will flip jss? is that correct?
no matter what I'm not sure this behavior is good

@wenduzer Yes
It assumes you have the plugin loaded if you set theme wide direction. In a perfect world a warning would be logged. Flipping inline styles globally would require quite the perf overhead for very minor use cases that are only caused by incomplete documentation.

In a perfect world a warning would be logged.

:100: for that. I have been chatting about it a long time ago with @kof. Best solution to know if a plugin is loader or not is to use feature detection.

Is there any plugins system out there that allows certain plugin installation detection? I haven't seen one so far and I wonder what could be a solution. Having some sort of isPluginApplied(Symbol) would be possible, but feels evil.

Internally, we are dynamically enabling this plugin when direction: 'rtl' is set on the theme. The CSS-in-JS documentation explains a bit more how this plugin is working. Head to the plugin README to know everything about it.

This makes it sound like the plugin is getting installed automatically and on Slide API there is no mention that in order "direction" prop to work it needs the plugin used.
Looks like mostly documentation issue to me.

I'd go with "documentation issue" as well, makes sense that it should be external if I want rtl support for specific components, but, if so, it should be written in the docs.
something like that,

Internally, we are dynamically enabling this plugin when direction: 'rtl' is set on the theme. Even though you installed the plugin in your project some components require loading it to the jss instance as described below.
The CSS-in-JS documentation explains a bit more how this plugin is working. Head to the plugin README to know everything about it.

Perfect world will be a list of components that require this behavior.
If you ever think of a better solution, maybe creating a clone MUI containing only rtl or manually changing styles according to theme.direction, feel free to mention me, I'd love to do that, just can't find the perfect solution yet.

@wenduzer I would replace some components by components, it's required by 90% of  them.

Oh, I though you had a global use case for RTL, my bad.

The project is RTL, but I use jss as my main styiling solution so I flips all my jss not only the material-ui ones


New added icons are missing

I have few icons that I added from rofi-fontawesome. One is battery, and a 'leaf' icon which shows different things. But, now when I add new icons, it's not displaying it there. I reloaded i3 everytime after Changing. displaying fine. And, fontawesome is also declared.   I can change existing icons and those are displaying too. But, extra icons other than these aren't displaying. Currently, it's only 4 icons. And I have enough space there in the bar. So, what's going on? I've linked my polybar config. The Music and Uptime are those which are not showing. Config: https://github.com/b3nsh4/i3stuff/blob/master/polybar_config

See: this and that.
Please also note that the bug tracker is only for bug report. See this page for more information.


Irrelevant? - ESLINT considers import a keyword

Should import.meta be somethingElse.meta?
Look at the issue I'm having with ESLINT:
https://stackoverflow.com/questions/54337576/
And look at this discussion regarding the matter:
https://github.com/eslint/eslint/issues/11514
To me, it seems like eslint shouldn't consider import. (notice the dot) the same thing as import. They won't address the matter until import.meta reaches stage 4.
I'm not posting here trying to get you to fix ESLINT. I'm posting here because I thought the issue might be relevant in some way to the import.meta project.
Could naming this object import be problematic to other things (beyond linters that won't yet support import.meta)?
There's import, import(), and import.meta. Maybe all that use of the word "import" for 3 separate things is just fine, but I'm reporting anyway, just in case it is something that should be taken into consideration. Thanks.

@Lonniebiz the proposal is stage 4 and there is an active issue tracking proper integration into eslint. Until that lands you can use the babel-eslint parser to get support
https://github.com/eslint/eslint/issues/13133


[Pricing cards] White screen when try go to page tariffs

Environment: Windows 10 PRO, Google Chrome
Reproducible: always
Build found: 14.05.2023
Preconditions
Not Log in as super admin
Steps to reproduce

Go to (https://www.testgreencity.ga/#/ubs-admin/tariffs)

Actual result
White screen and no message error
Expected result
Redirect to Log in form and error message "forbidden"
User story and test case links
E.g.: "User story #4256
Test case"
Video

It is not a bug
Credentials:
<EMAIL_ADDRESS>Test-User123

If I not log in , not anything error message, or redirect to login form. It's okey ?


Document which task components are auto-generated

Are these generated automatically? Or does the task author have to write them?

Benchmarking pipeline
Resource generation scripts
Test resource generation scripts

This could probably be clarified by going over the different parts and listing all of the headings that have "Step X" in them.

Fair point!  :)


Add emitter option

API change check
APIView has identified API level changes in this PR and created following API reviews.
@typespec/http-client-csharp


Is it possible to get first k entities for query (h,r,?)

Hello,
I was wondering is there a way to get the first k entities(and associated score) that give the top k highest score for the query like (h, r, ?) or (?, r, t). This would be quite helpful to understand the behavior of the model.
Right now given (h,r,t) the library can compute the rank of h/t for query (?, r, t)/(h, r, ?).

Hi @Chen-Cai-OSU,
Great suggestion! I've been working on a knowledge discovery API and have a need for a similar function, so: yes, I'll implement something like this into a high-level function.
In the mean time, the following snippet should get the job done (for the <h, r, ?> case at any rate, the rest is left as an exercise for the reader ;-) ):
hr = X[0,0:2] # np.array
top_k = 15

C = np.array([np.append(hr, x) for x in list(model.ent_to_idx.keys())])

results = pd.DataFrame(np.hstack([C, model.predict(C)]), columns=['head', 'relation', 'tail', 'score'])

results.sort_values('score', ascending=False, inplace=True)

print(results[:top_k])

Thanks for your code. This works like a charm and is exactly what I want!


!squadjs restartsubsystem logparser is allowing unauthroized user to run the command

Description of Issue
When we run the command !squadjs restartsubsystem logparser a unauthorized user is able to run the command.
Errors or Screenshots of Issue

     "plugin": "DiscordSubsystemRestarter",       "enabled": true,       "discordClient": "discord",       "role": "794603603317751838"
Squad Information

SquadJS Version: beta branch
Squad Version: current v1

System Information

Operating System: 10
NodeJS Version: 12.19.1
Yarn Version: latest

Fixed in: https://github.com/Thomas-Smyth/SquadJS/pull/117

Fixed in: https://github.com/Thomas-Smyth/SquadJS/pull/117


feat: integrate django authentication system

Add a backend to integrate django authentication system.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: BustDot:x: semantic-release-botYou have signed the CLA already but the status is still pending? Let us recheck it.

@leeqvip plz review


[WIP] bin: custom git commands

This implements a custom git command git node that automate the landing process.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #98   +/-   ##
=======================================
  Coverage   98.17%   98.17%
=======================================
  Files          14       14
  Lines         492      492
=======================================
  Hits          483      483
  Misses          9        9

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 491e2b2...617a4a1. Read the comment docs.

@joyeecheung this PR looks great! Great Work.

Oh....I know why my pushed commits didn't show up here now, it's being merged from the branch here now that this repo has been transferred.....I'll close this and open another one from my fork.


A11y_Azure Data Studio_Azure tree item_Screenreader: Screenreader announce unnecessary content when keyboard focus goes to selected Azure account Tree Item after pressing tab or UP/down arrow key.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags: #A11yMAS;#A11yTCS;#A11ySev2;#SH_AzureDataStudio_Feb2021;#SQL Azure Data Studio;#Win10;#FTP;#DesktopApp;#WCAG1.3.1;#Screenreader;#JAWS;#NVDA;#STP;#AINotInScope;
Environment Details:
Application Name: Azure Data Studio
Version: 1.26.0-insider (user setup)
Windows Version: Windows10
Screenreader: JAWS, NVDA
Repro Steps:
1.Launch Azure Data Studio insiders application.
2.Tab to Connections from left menu and in servers button and hit enter on "New Connection" button.
3.Connections section will get open.
4.Tab to "Browse Preview" Tab item and hit enter.
5.Navigate to "Azure account" present in "Azure" tree item with the help of Tab or up/down arrow key.
6.Start JAWS and verify issue.
Actual:
Screenreader announce unnecessary content when keyboard focus goes to selected Azure account Tree Item after pressing tab or UP/down arrow key.
Same issue is also observed with all the tree items present in this section.
Expected:
After pressing Tab or Up/Down arrow key and move to selected Azure Account tree item , Screenreader should announce account detail only instead of unnecessary detail.
User Impact:
Screen reader user will not  get correct information and not ne able to understand which one tree item is selected if screenreader does not announce detail correctly.

I have verified the issue in the version 1.41.1
Issue is not reproducible.
GithubTags:#Closed;#Regressed:03-02-23;


Toolbar: fix blueprint search

The blueprint list can be sorted and filtered by name. Also, the Manage
sources modal is no longer hidden by a dropdown kebab.


[Bug] [dolphinscheduler-service] error was raised when copy processDefinition

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
As bug title said:

What you expected to happen
No error occurred
How to reproduce
As shown in the figure：
In Workflow Definition Page，click button ‘copy workflow’。
Anything else
the cause is that :

In Method org.apache.dolphinscheduler.api.service.impl.ProcessDefinitionServiceImpl#doBatchOperateProcessDefinition
the target processDefinition obj's id set to 0

2.while In Next Step Method org.apache.dolphinscheduler.service.process.ProcessServiceImpl#saveProcessDefine
it determines whether the obj's ID is null , and only is null then creating an object , if not then throw an error.

So there are two ways to fix this problem : set id to null  or determines whether the obj's ID is 0 or null before creating the target
processDefinition
Version
dev
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This bug is too simple. I'm not going to mention a PR to fix it

same issue: #12081


Enable rultor for this repository

@rultor hello

@rultor hello

@meetmangukiya Hi there! I understand a few simple commands: "merge", "deploy", etc. This page explains them briefly. Any questions or bug reports are welcome. Have fun :)

@rultor hello

@meetmangukiya Hi there! I understand a few simple commands: "merge", "deploy", etc. This page explains them briefly. Any questions or bug reports are welcome. Have fun :)


Update to jfr-mappers 1.0.0

jfr-mappers has reached 1.0.0, so we should update the reporter to use that.
Would also be a good opportunity to upgrade to sdk version 0.9.0.
  It's not too bad, though.

the update has been completed
https://github.com/newrelic/newrelic-jfr-reporter/blob/28e62c7182e847e19cf67eb770faba53c240b147/build.gradle.kts#L39

the update has been completed
https://github.com/newrelic/newrelic-jfr-reporter/blob/28e62c7182e847e19cf67eb770faba53c240b147/build.gradle.kts#L39


Code improvements

This aims to improve the code in various aspects, including readability, consistency, abstraction and elegance.
Regarding styles: there must either be a style ruleset. Since this is not my project, I won't be enforcing any styles, thus won't be making any changes to the code style that is inconsistently applied.

Thanks for the code improvements. There certainly is some housekeeping to be done.
If you're happy with the current commits, I'll merge them and you can make another pull request if you want to, with any other improvements.

I have updated the contributing file with some basic style guidelines. We'll be progressively be fixing style inconsistencies.

You may merge the current changes, I'll be making another PR containing style maintenance. You may focus on more functional parts of the project.

Could you reopen the PR and merge to the dev branch? I'd like to keep master for releases only.


Screenshots Differ Across Resolutions

Problem
When employing the cypress-visual-regression plugin for testing, I've encountered a notable issue with discrepancies in screenshots captured across devices with varying resolutions. Interestingly, despite setting the viewport of Cypress to 1920x1080, the problem persists. Tests execute smoothly on my 1920x1080 resolution device, yet inconsistencies between the base and actual screenshots emerge when transitioning to another device with a distinct resolution (in my case, 2550x1440). These disparities ultimately lead to test failures, complicating the reliability of visual regression testing across multiple devices.
One of the failed tests:

Error on Cypress UI Console:

Related Code:

Expected Behavior
The screenshots captured during testing should remain consistent across devices with varying resolutions, ensuring accurate comparison and reliable test results regardless of the device used.
Steps to Reproduce

Set up Cypress plugin for testing.
Set up the viewport of Cypress to 1920x1080
Run tests on a device with resolution A (e.g., 1920x1080).
Observe and record the screenshots captured during testing.
Switch to a device with resolution B (e.g., 2550x1440).
Run the same tests on the device with resolution B.
Compare the screenshots captured during testing on devices A and B.
Note the discrepancies between the base and actual screenshots.

I had similar issues and noticed that this could be a Cypress-related issue, as that is where essentially a screenshot is being taken. This library just handles files and a few other nuances, but does not really take screenshots into PNG.

I had similar issues and noticed that this could be a Cypress-related issue, as that is where essentially a screenshot is being taken. This library just handles files and a few other nuances, but does not really take screenshots into PNG.

Yup, I've come to the conclusion that it's something related to Cypress. It works well on my 1920x1080 resolution laptop, but it turns out to fail on a 2550x1440 resolution monitor, even if I generate the base image using 2550x1440 and test it in the same resolution. Interestingly, when I zoom out the Chrome browser to around 80% while testing, the actual threshold limit value decreases, and some tests might even pass.

I don't know if this is the same issue but if you run your test on a Mac with retina display your snapshots are going to be double size ( do to Cypress and Chrome config).

Different resolutions naturally generate different looking UIs, this is neither a bug nor the Cypress problem. If you want to test different resolutions, then you have to generate dedicated base images for all different resolutions you want. You can parameterize this if you want to run the same test for all the different resolutions, but you HAVE to generate dedicated base images for all of them.


Fixes #33

With these changes library will pass all unit tests for numpy==2.0.0

Thank you! You probably use numba 0.60.0 for this to work. Could you downgrade numba to 0.59.1 and see if the tests fail? From a CI perspective I want to understand if a potential largestinteriorrectangle 0.3.0 will be numpy 1 compatibile or not. If not, we additionally need to explicitely set the minimum numba version to 0.60.0 in setup.cfg

Sorry I just saw that np.inf is not something new that came with numpy 2.0, but has already existed in numpy 1.x. Inf was just an alias to np.inf


Allow showStarChoices to change the colors

Allow the user to change the text color in spectroscopic showStarChoices

Added in commit https://github.com/eas342/tshirt/commit/070b75b070903aeb6dc953d5c5867bd6ac9c8f5b


Add to documentation - Different Python Version

I noticed you are using urllib.requests which after doing some research is not in Python 2.7.

@smadarasmi can you close this PR and update your branch and raise another PR. Otherwise merge branch master into add-to-documentation

@rahuldecoded I have rebased it so now the only difference is this commit. Is this good?

LGTM 😃 Thank you.

@madar007 @smadarasmi feel free raise an issue and work on them.


French translating, minor bug correction, Profit Optimization optimization

-I have started to translate the frFR locals into french (copy from enUS)
-Optimization process for Profit Optimization
-Fix the multiple row deleting when deleting one row in the craftqueue

Adding fix for tool/gear

Sorry for the late review ^^'

might be able to take a look tmr :)


todo: test small rollout group size with 2fire

also experiment with larger cap on MR, maybe this would help discover more novel solutions?
unlikely though, since there is lots of diversity in the population already


Suggest Type Annotations Using Mypy Daemon

MyPy recently introduced the ability to suggest type annotations for functions: https://mypy.readthedocs.io/en/latest/mypy_daemon.html#static-inference-of-annotations. It would be great to have this integrated into VS Code's UI, so you could get a suggestion for type hints. From their docs, it seems like this is already supported in PyCharm.
It looks like this would depend on first getting MyPy daemon supported  in VS Code: https://github.com/microsoft/vscode-python/issues/1577

Clearly regardless this request popularity, "needs decision" label was not removed even after 8 months....

@ssbarnea I don't the tone in your message is really necessary. And while I understand your frustration that a feature you would find useful has not been implemented yet, this specific issue is the 28th most popular feature request, so it is not a top priority for us ATM. This would also require a deep integration with mypy that goes farther than probably any other tool we support, which makes this not a simple "let's do it" decision as we have to also decide if that's the direction we want to take the extension overall.

Thanks! Having that label does send a really good message, as it invites someone to try to make a PR for this popular request.

Now that we have Pylance, that would be the best place to get this support from.

Indeed, now that we have the closed-source pylance, we can avoid using the open-source type checker.

@ssbarnea We have two language servers JediLSP (https://github.com/pappasam/jedi-language-server) and Pylance you can make this recommendation on either of them.


REDIS_URL required

Hello,
I tried to run 'docker-compose up brp', but it fails with the following error:
Starting biorepoportal_memcached_1
Starting biorepoportal_ehb_1
Starting biorepoportal_brp_1
Attaching to biorepoportal_brp_1
brp_1 | Traceback (most recent call last):
brp_1 |   File "./bin/manage.py", line 20, in <module>
brp_1 |     execute_from_command_line()
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
brp_1 |     utility.execute()
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
brp_1 |     self.fetch_command(subcommand).run_from_argv(self.argv)
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 272, in fetch_command
brp_1 |     klass = load_command_class(app_name, subcommand)
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 75, in load_command_class
brp_1 |     module = import_module('%s.management.commands.%s' % (app_name, name))
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
brp_1 |     __import__(name)
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/core/management/commands/syncdb.py", line 9, in <module>
brp_1 |     from django.core.management.sql import custom_sql_for_model, emit_post_sync_signal, emit_pre_sync_signal
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/core/management/sql.py", line 9, in <module>
brp_1 |     from django.db import models
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/db/models/__init__.py", line 5, in <module>
brp_1 |     from django.db.models.query import Q
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 17, in <module>
brp_1 |     from django.db.models.deletion import Collector
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/db/models/deletion.py", line 4, in <module>
brp_1 |     from django.db.models import signals, sql
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/__init__.py", line 4, in <module>
brp_1 |     from django.db.models.sql.subqueries import *
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/subqueries.py", line 12, in <module>
brp_1 |     from django.db.models.sql.query import Query
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/query.py", line 22, in <module>
brp_1 |     from django.db.models.sql import aggregates as base_aggregates_module
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/aggregates.py", line 9, in <module>
brp_1 |     ordinal_aggregate_field = IntegerField()
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/db/models/fields/__init__.py", line 116, in __init__
brp_1 |     self.db_tablespace = db_tablespace or settings.DEFAULT_INDEX_TABLESPACE
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/conf/__init__.py", line 54, in __getattr__
brp_1 |     self._setup(name)
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/conf/__init__.py", line 49, in _setup
brp_1 |     self._wrapped = Settings(settings_module)
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/conf/__init__.py", line 128, in __init__
brp_1 |     mod = importlib.import_module(self.SETTINGS_MODULE)
brp_1 |   File "/usr/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
brp_1 |     __import__(name)
brp_1 |   File "/opt/app/brp/conf/settings.py", line 25, in <module>
brp_1 |     'redis': env.cache('REDIS_URL')
brp_1 |   File "/usr/local/lib/python2.7/site-packages/environ/environ.py", line 188, in cache_url
brp_1 |     return self.cache_url_config(self.url(var, default=default), backend=backend)
brp_1 |   File "/usr/local/lib/python2.7/site-packages/environ/environ.py", line 173, in url
brp_1 |     return self.get_value(var, cast=urlparse.urlparse, default=default, parse_default=True)
brp_1 |   File "/usr/local/lib/python2.7/site-packages/environ/environ.py", line 250, in get_value
brp_1 |     raise ImproperlyConfigured(error_msg)
brp_1 | django.core.exceptions.ImproperlyConfigured: Set the REDIS_URL environment variable
brp_1 | Unknown command: 'migrate'
brp_1 | Type 'manage.py help' for usage.
brp_1 | Unknown command: 'collectstatic'
brp_1 | Type 'manage.py help' for usage.
brp_1 | [uwsgi-static] added mapping for /static => /opt/app/_site/static
brp_1 | [uwsgi-static] added mapping for /static => /usr/local/lib/python2.7/site-packages/django/contrib/admin/static
brp_1 | *** Starting uWSGI <IP_ADDRESS> (64bit) on [Tue Dec 15 10:53:00 2015] ***
brp_1 | compiled with version: 4.7.2 on 15 December 2015 10:49:11
brp_1 | os: Linux-4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 18:25:50 UTC 2015
brp_1 | nodename: b8228347632b
brp_1 | machine: x86_64
brp_1 | clock source: unix
brp_1 | pcre jit disabled
brp_1 | detected number of CPU cores: 8
brp_1 | current working directory: /opt/app
brp_1 | detected binary path: /usr/local/bin/uwsgi
brp_1 | uWSGI running as root, you can use --uid/--gid/--chroot options
brp_1 | *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
brp_1 | chdir() to /opt/app/
brp_1 | your processes number limit is 1048576
brp_1 | your memory page size is 4096 bytes
brp_1 | detected max file descriptor number: 1048576
brp_1 | building mime-types dictionary from file /etc/mime.types...532 entry found
brp_1 | lock engine: pthread robust mutexes
brp_1 | thunder lock: disabled (you can enable it with --thunder-lock)
brp_1 | uwsgi socket 0 bound to TCP address <IP_ADDRESS>:8000 fd 3
brp_1 | Python version: 2.7.8 (default, Dec  3 2014, 02:51:48)  [GCC 4.7.2]
brp_1 | Python main interpreter initialized at 0x751e00
brp_1 | python threads support enabled
brp_1 | your server socket listen backlog is limited to 100 connections
brp_1 | your mercy for graceful operations on workers is 60 seconds
brp_1 | mapped 304320 bytes (297 KB) for 2 cores
brp_1 | *** Operational MODE: preforking ***
brp_1 | WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x751e00 pid: 1 (default app)
brp_1 | *** uWSGI is running in multiple interpreter mode ***
brp_1 | spawned uWSGI master process (pid: 1)
brp_1 | spawned uWSGI worker 1 (pid: 12, cores: 1)
brp_1 | spawned uWSGI worker 2 (pid: 13, cores: 1)

thanks @ludovicc!


RETEST:Last modified by field not populating properly  in BETA

Context
In the BETA Enviornment, the "last modified by" field displays as WINMGMT instead of the last user who modified the data. Last modified by field was WINMGMT after import from historical and then missing after submission (expected behaviour is that it is the user who modified the data)
Private Zenhub Image
Steps to Reproduce

Navigate to the BETA environment and Log into ECMPS
Check out a facility (Oris Code: 55418 config: CT-1)
Navigate to QA or Emissions module and import data from historical
Navigate to evaluation module and find the recently imported data

The "last modified by" field displays as WINMGMT instead of the last user who modified the data. The expected behaviour is that the last modified by" field is the user who modified the data.

Pulling this bug back. Tech Team will need to make some backend fixes before this issue can be addressed

Note: WINMGMT likely showing in tst and beta for 2023 Q3 windows because a job keeps reopening them.
On dev, check Last Modified By field in Evaluate screen for:

MP with no changes (revert to official)

QA test with closed window

Import from historical
Import from file

EM file with closed window

Import from historical
Import from file

MP with open window

Manual change in interface
Import from file

QA test with open window

Import from historical
Import from file

EM file with open window

Import from historical
Import from file

Evaluate and submit MP, QA, EM data

Revert to official and check column again after submissions

Repeat tests in tst environment.

Repeat tests in beta environment.

The original issue reported in this ticket was related to WINMGMT displaying in the beta environment and the Evaluate screen. This is the same in the test environment for 2023 Q3 windows because a job keeps reopening them.
Closing this ticket. New findings related to this field are documented in #6251.


Add alpha3Code to the the selector-search criteria

I renamed the Country.countryCode to alpha2Code.
The search criteria I added matches any country where the Country.alpha3Code starts with the users search query.
For example: USA matches United States of America.

I actually had a second thought but I will merge it thanks, @ClemaX.✨


Update chcp command to use full path.

In the, probably very rare, case you don't have System32 on your path the
chcp command will fail. Changed to use the full path off of %SystemRoot%.

:+1:

Looks good


Fixed some issues in the sos form

The SOS form to report any critical animal doesn't currently have the address as a required field but should have. Also, it doesn't ask for a contact number which seems essential.
I added these things and also gave some appropriate margins.

add some screenshots


fix(trading): market icons snags

Related issues 🔗
Closes #6287
Description ℹ

[x] center all pills and icons
[x] enable emblem for markets to have different sizes
[x] adjust fees market cells
[x] if market emblem is smaller, then chain icons need to have their position adjusted, come with set sizes

Demo 📺

Technical 👨🔧
Details of technical implementation that reviewers may need to be aware of, if applicable.

Tested on the deploy preview, looks like it's working nicely.
One question I have is why https://github.com/vegaprotocol/frontend-monorepo/pull/6525/files#diff-cb3dfb1f734245233f203c9072dea69719913f6e1533f51c433100f6d37b347cR12 has been added? Not very important, but I haven't seen what else in this PR makes it neccessary.

Answer: to import classnames


Broken Fisherman Job?

Everytime I load the server, the fisherman job fails to follow suit and makes it unavailable to my players.  Here are the errors that I receive below:
https://pastebin.com/yfZtThFN
I'm unsure as to what might've happened, as I discovered the error a couple days after it began happening.  I've only edited jobs from the game through /jobs editjobs, and not the .yml, though I did edit the fisherman job.
Here's what the .yml file looks like, just in case:
https://pastebin.com/eGw1qHJD
I'm using the latest <IP_ADDRESS> update.
I am using a 1.17 (not 1.17.1) Spigot server.
/ver command result:
[13:43:54] [Server thread/INFO]: This server is running CraftBukkit version 3170-Spigot-a483d2c-ec116f6 (MC: 1.17) (Implementing API version 1.17-R0.1-SNAPSHOT)
[13:43:54] [Server thread/INFO]: Checking version, please wait...
[13:43:54] [Thread-47/INFO]: You are 10 version(s) behind

You have miss formated file. Correct one should look like
Fisherman:
  fullname: Fisherman
  shortname: Fi
  FullDescription:
  - Earns money from fishing.
  ChatColour: AQUA
  chat-display: full
  max-level: 200
  leveling-progression-equation: 10*(joblevel)+(joblevel*joblevel*4)
  income-progression-equation: baseincome+(baseincome*(joblevel-1)*0.01)-((baseincome+(baseincome*(joblevel-1)*0.01))
    * ((numjobs-1)*0.05))
  points-progression-equation: basepoints+(basepoints*(joblevel-1)*0.01)-((basepoints+(basepoints*(joblevel-1)*0.01))
    * ((numjobs-1)*0.05))
  experience-progression-equation: baseexperience-(baseexperience*((numjobs-1) *0.01))
  rejoinCooldown: 10
  maxDailyQuests: 1
  Quests:
    '1':
      Name: Catcher
      Objectives:
      - Fish;cod;2
      - Fish;salmon;2
      - Fish;tropical_fish;2
      RewardCommands:
      - eco give [playerName] 100
      - msg [playerName] Completed quest!
      RewardDesc:
      - Catch fish and get money
      - Get 100 for this!
  Gui:
    Item: fishing_rod
  Fish:
    cod:
      income: 15.0
      points: 15.0
      experience: 15.0
    salmon:
      income: 20.0
      points: 20.0
      experience: 25.0
    tropical_fish:
      income: 25.0
      points: 25.0
      experience: 25.0
    pufferfish:
      income: 25.0
      points: 25.0
      experience: 25.0
  Kill:
    cod:
      income: 15.0
      points: 15.0
      experience: 15.0
    salmon:
      income: 20.0
      points: 20.0
      experience: 25.0
    tropical_fish:
      income: 25.0
      points: 25.0
      experience: 25.0
    pufferfish:
      income: 25.0
      points: 25.0
      experience: 25.0
    dolphin:
      income: 30.0
      points: 30.0
      experience: 30.0

One missing and 2 extra spaces for salmon section


Testing the CLA process again

Hello @audreythomas,Thank you for the PR! We will be reviewing this PR soon, in the mean                                              time, if you have not, please be sure to                                                                                sign our CLA so that we can merge your changes. Thanks again!                                             Team DX


UnicodeEncodeError: 'latin-1' codec can't encode characters in position 8-9: ordinal not in range(256)

When I am trying to combine two pdf together, this error occurs. Both pdf are written in chinese, and I convert them from word document(.docx) to pdf using win32com. If I print these word into pdf, no error will occur. Any ideas?
Traceback (most recent call last):
File "handle.py", line 154, in
fire.Fire(handle)
File "C:\Users\cqzhao\Anaconda3\lib\site-packages\fire\core.py", line 127, in Fire
component_trace = _Fire(component, args, context, name)
File "C:\Users\cqzhao\Anaconda3\lib\site-packages\fire\core.py", line 366, in _Fire
component, remaining_args)
File "C:\Users\cqzhao\Anaconda3\lib\site-packages\fire\core.py", line 542, in _CallCallable
result = fn(*varargs, **kwargs)
File "handle.py", line 32, in combine
self.combine(outFile,flist)
File "handle.py", line 91, in combine
output.write(outputStream)
File "C:\Users\cqzhao\Anaconda3\lib\site-packages\PyPDF2\pdf.py", line 501, in write
obj.writeToStream(stream, key)
File "C:\Users\cqzhao\Anaconda3\lib\site-packages\PyPDF2\generic.py", line 549, in writeToStream
value.writeToStream(stream, encryption_key)
File "C:\Users\cqzhao\Anaconda3\lib\site-packages\PyPDF2\generic.py", line 472, in writeToStream
stream.write(b(self))
File "C:\Users\cqzhao\Anaconda3\lib\site-packages\PyPDF2\utils.py", line 238, in b
r = s.encode('latin-1')
UnicodeEncodeError: 'latin-1' codec can't encode characters in position 8-9: ordinal not in range(256)

Just make sure other person can see the solution. Please refer to the link "https://blog.csdn.net/weixin_43116153/article/details/105218309"


Laptop's touchpad scroll doesn't smooth

VSCode Version: 1.18.1
OS Version: Win10 1709

Problem:
when you scrolling with laptop's touchpad, it just doesn't smooth,
but it was smoothly in other software like chrome.
Regards.

Reproduces without extensions: Yes/No

VSCode Version: Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:32:36.026Z)
OS Version: Windows_NT ia32 10.0.15063
Hardware: Lenovo Yoga 910
Extensions:

Extension
Author (truncated)
Version

vscode-instant-markdown
dba
1.3.0

solidity
Jua
0.0.31

cpptools
ms-
0.14.2

vetur
oct
0.11.3

node-tdd
pra
0.2.4

(11 theme extensions excluded)

Steps to Reproduce:

Open a file (larger than one screen)
Scroll down with touchpad
Scroll up with touchpad

Expected Results:
Should scroll smoothly
Actual Results:
Scrolling halts for a second or two. Basically anytime you stop scrolling you can't immediately scroll again.
Dragging the scroll bar does not reproduce the problem.

Reproduces without extensions: Yes

/duplicate of https://github.com/Microsoft/vscode/issues/35191


vl_kdforest_build() does not seem to build a tree

vl_kdforest_build() does not seem to build a tree: I am not sure if I am doing something wrong here or I discovered a bug.
I am trying to build a kd-tree (one only) for 3D points. I followed the API and a few examples I found. However, it seems that the tree is not really built as vl_kdforest_get_depth_of_tree(forest, 0) reports a tree depth of 0, which basically indicates that "no tree was built at all".
This is the code I use:
vector< IdxPt_<DIMS, T> >& pts = ... custom point type ...
const size_t numPoints = pts.size();

vl_size dimensions = DIMS;
vl_size numTrees   = 1;

T* dataPts = new T[numPoints*DIMS];
for(size_t i=0; i<numPoints; i++){
    for(size_t k=0; k<DIMS; k++)
        dataPts[i*DIMS+k] = pts[i].data[k];
}

VlKDForest* forest = vl_kdforest_new(VL_TYPE_FLOAT, dimensions, numTrees, VlDistanceL2);
vl_kdforest_build(forest, numPoints, dataPts);

cout << "DIMS:                              " << DIMS << endl;
cout << "numPoints:                         " << numPoints << endl;
cout << "vl_kdforest_get_data_dimension:    " << vl_kdforest_get_data_dimension(forest) << endl;
cout << "vl_kdforest_get_num_trees:         " << vl_kdforest_get_num_trees(forest) << endl;
cout << "vl_kdforest_get_depth_of_tree:     " << vl_kdforest_get_depth_of_tree(forest, 0) << endl;
cout << "vl_kdforest_get_num_nodes_of_tree: " << vl_kdforest_get_num_nodes_of_tree(forest, 0) << endl;

if( forest )
    vl_kdforest_delete(forest);
if( dataPts )
    delete[] dataPts;

And the output I get is as follows:
DIMS:                              3
numPoints:                         1000000
vl_kdforest_get_data_dimension:    3
vl_kdforest_get_num_trees:         1
vl_kdforest_get_depth_of_tree:     0
vl_kdforest_get_num_nodes_of_tree: 1

Why is the depth of the three 0? I suspect I am using the API in the wrong manner although I tried to follow the docs. What is wrong here?

This is likely a problem with the data. E.g. if all data is identical then the tree has just one leaf node. For instance, in MATLAB:
run toolbox/vl_setup.m ;

x = zeros(3,10000) ; % all identical, trees collapse
forest = vl_kdtreebuild(x,'verbose') ;

x = randn(3,10000) ; % fine
forest = vl_kdtreebuild(x,'verbose') ;

demonstrates what happens in the two cases:
vl_kdforestbuild: data double [3 x 10000]
vl_kdforestbuild: threshold selection method: median
vl_kdforestbuild: number of trees: 1
vl_kdforestbuild: tree 0: depth 0, num nodes 1

vl_kdforestbuild: data double [3 x 10000]
vl_kdforestbuild: threshold selection method: median
vl_kdforestbuild: number of trees: 1
vl_kdforestbuild: tree 0: depth 14, num nodes 19999


Layout fixes

@mariobuikhuizen I realized I forgot a use case.  See index_dynamic.html.  It won't make much difference I think to the CSS fixes but it's an example of a page where we send a request to the notebook and dynamically load the Jdaviz application. This was the original reason behind putting the Jdaviz app inside a v.Col since we couldn't add an event_handler directly to the Jdaviz app.  Maybe you can fold this example into your CSS tweaks to make it look nice?  I tried swapping the v.Col or a generic v.Container, and that mostly worked, but it added some padding that maybe we can avoid?

@mariobuikhuizen Also, the vuetify 2.2.26 is fairly old at this moment.  The latest version is 2.4.9.  Do you have a version of your hacked package for any later version of Vuetify?

I added a commit for the dynamic case. It needs the updated version of https://github.com/spacetelescope/jdaviz/pull/505.
I don't have a newer version of the modified Vuetify package, but I can make one. I will then also update ipyvuetify with that version.

Ok, thanks!  I'll take a look at the dynamic case.  I guess an updated modified Vuetify package isn't critical, especially if it requires coordination with ipyvuetify and jdaviz, or if it introduces any breaking changes to ipyvuetify.


Type declarations not found

Typescript compiler doesn't seem to find zod type declarations in nuxtjs 3 :point_down:
Cannot find module 'zod' or its corresponding type declarations.ts(2307)

It seems it was a cache issue. I only needed to restart my IDE.


EchoStar SAGE206612 Doorbell Sensor -  Error in Domoticz log when adding

Issue description
Errors when trying to add device. Device shows up in Zigbee2MQTT but Domoticz cannot add device.
Please let me know any other info that would be useful, thanks.
Additional information
Zigbee2MQTT version: Latest
Python version: 3.7.?
Domoticz version: Latest
Plugin version: Latest (updated an hour before this post)
Logs
2021-02-10 15:07:09.684 Error: (Zigbee2MQTT) 0x0017880106a30bc3: can not process numeric item "color_temp_startup"
2021-02-10 15:07:09.685 Error: (Zigbee2MQTT) 0x0017880106a30bc3: can not process feature type "composite"
2021-02-10 15:07:09.686 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-10 15:07:09.686 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-10 15:07:09.686 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-10 15:07:09.687 Error: (Zigbee2MQTT) 0x00124b00222e14f5: can not process numeric item "color_temp_startup"
2021-02-10 15:07:09.688 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-10 15:07:09.688 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-10 15:07:09.688 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-10 15:07:09.690 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-10 15:07:09.690 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-10 15:07:09.690 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-10 15:07:09.691 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-10 15:07:09.691 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-10 15:07:09.691 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-10 15:07:09.691 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-10 15:07:09.691 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-10 15:07:09.691 Error: Device creation failed, Device object is not associated with a plugin.

Could you please enable debug mode in the plugin and post here the log

Sure. The gaps in the log below are where I've removed log entries from other hardware.
Thanks.
Also, probably unrelated and perhaps you'd prefer I opened a new issue, but after updating yesterday I got an error about unable to load plugin.py (and referencing AV201021.py) so I commented out the line referencing AV201021.py in domoticz/plugins/zigbee2mqtt/adapters/bitron/init.py
That allowed the plugin to start.
Anyway, here are the logs:
2021-02-11 08:29:25.181 (Zigbee2MQTT) Zigbee2mqtt bridge is online
2021-02-11 08:29:25.181 (Zigbee2MQTT) MqttClient::publish zigbee2mqtt/bridge/config/groups ()
2021-02-11 08:29:25.189 (Zigbee2MQTT) Received available devices list from bridge
2021-02-11 08:29:25.189 (Zigbee2MQTT) Coordinator address is 0x00124b00216000b9
2021-02-11 08:29:25.219 (Zigbee2MQTT) {"access": 7, "description": "Color temperature after cold power on of this light", "name": "color_temp_startup", "presets": [{"description": "Coolest temperature supported", "name": "coolest", "value": 150}, {"description": "Cool temperature (250 mireds / 4000 Kelvin)", "name": "cool", "value": 250}, {"description": "Neutral temperature (370 mireds / 2700 Kelvin)", "name": "neutral", "value": 370}, {"description": "Warm temperature (454 mireds / 2200 Kelvin)", "name": "warm", "value": 454}, {"description": "Warmest temperature supported", "name": "warmest", "value": 500}, {"description": "Restore previous color_temp on cold power on", "name": "previous", "value": 65535}], "property": "color_temp_startup", "type": "numeric", "unit": "mired", "value_max": 500, "value_min": 150}
2021-02-11 08:29:25.219 (Zigbee2MQTT) {"description": "Color of this light expressed as hue/saturation", "features": [{"access": 7, "name": "hue", "property": "hue", "type": "numeric"}, {"access": 7, "name": "saturation", "property": "saturation", "type": "numeric"}], "name": "color_hs", "property": "color", "type": "composite"}
2021-02-11 08:29:25.220 (Zigbee2MQTT) Creating domoticz device to handle "effect" key for device with ieeeAddr 0x0017880106a30bc3
2021-02-11 08:29:25.221 (Zigbee2MQTT) {"access": 7, "description": "Color temperature after cold power on of this light", "name": "color_temp_startup", "presets": [{"description": "Coolest temperature supported", "name": "coolest", "value": 150}, {"description": "Cool temperature (250 mireds / 4000 Kelvin)", "name": "cool", "value": 250}, {"description": "Neutral temperature (370 mireds / 2700 Kelvin)", "name": "neutral", "value": 370}, {"description": "Warm temperature (454 mireds / 2200 Kelvin)", "name": "warm", "value": 454}, {"description": "Warmest temperature supported", "name": "warmest", "value": 500}, {"description": "Restore previous color_temp on cold power on", "name": "previous", "value": 65535}], "property": "color_temp_startup", "type": "numeric", "unit": "mired", "value_max": 500, "value_min": 150}
2021-02-11 08:29:25.221 (Zigbee2MQTT) Creating domoticz device to handle "effect" key for device with ieeeAddr 0x00124b00222e14f5
2021-02-11 08:29:25.222 (Zigbee2MQTT) MqttClient::subscribe
2021-02-11 08:29:25.222 (Zigbee2MQTT) Zigbee2mqtt log level is debug
2021-02-11 08:29:25.222 (Zigbee2MQTT) Joining new devices is disabled on the zigbee bridge
2021-02-11 08:29:25.275 (Zigbee2MQTT) onMQTTSubscribed
2021-02-11 08:29:25.219 Error: (Zigbee2MQTT) 0x0017880106a30bc3: can not process numeric item "color_temp_startup"
2021-02-11 08:29:25.219 Error: (Zigbee2MQTT) 0x0017880106a30bc3: can not process feature type "composite"
2021-02-11 08:29:25.220 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-11 08:29:25.220 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-11 08:29:25.220 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-11 08:29:25.221 Error: (Zigbee2MQTT) 0x00124b00222e14f5: can not process numeric item "color_temp_startup"
2021-02-11 08:29:25.222 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-11 08:29:25.222 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-11 08:29:25.222 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-11 08:29:26.257 (Zigbee2MQTT) Unable to find selector switch level for value "heat", device: Zigbee2MQTT - ZB-TRV3 - KitchenTRV (Mode)
2021-02-11 08:29:26.257 (Zigbee2MQTT) Unable to find selector switch level for value "heat", device: Zigbee2MQTT - ZB-TRV3 - KitchenTRV (Mode)
2021-02-11 08:29:26.289 (Zigbee2MQTT) Unable to find selector switch level for value "heat", device: Zigbee2MQTT - ZB-TRV6 - Bedroom (door) (Mode)
2021-02-11 08:29:26.289 (Zigbee2MQTT) Unable to find selector switch level for value "heat", device: Zigbee2MQTT - ZB-TRV6 - Bedroom (door) (Mode)
2021-02-11 08:29:26.311 (Zigbee2MQTT) Unable to find selector switch level for value "heat", device: Zigbee2MQTT - ZB-TRV8 - LivingRoomTRV (Mode)
2021-02-11 08:29:26.311 (Zigbee2MQTT) Unable to find selector switch level for value "heat", device: Zigbee2MQTT - ZB-TRV8 - LivingRoomTRV (Mode)
2021-02-11 08:29:26.323 (Zigbee2MQTT) Unable to find selector switch level for value "wakeup", device: Smart Cube - Action
2021-02-11 08:29:26.323 (Zigbee2MQTT) Unable to find selector switch level for value "wakeup", device: Smart Cube - Action
2021-02-11 08:29:26.340 (Zigbee2MQTT) Creating domoticz device to handle "effect" key for device with ieeeAddr 0x0017880106a30bc3
2021-02-11 08:29:26.356 (Zigbee2MQTT) Creating domoticz device to handle "effect" key for device with ieeeAddr 0x00124b00222e14f5
2021-02-11 08:29:26.358 (Zigbee2MQTT) Received groups list from bridge
2021-02-11 08:29:26.341 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-11 08:29:26.341 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-11 08:29:26.341 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-11 08:29:26.356 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-11 08:29:26.356 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-11 08:29:26.356 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-11 08:29:31.769 (Zigbee2MQTT) New request: [1] bridge_getstatus({})
2021-02-11 08:29:31.769 (Zigbee2MQTT) MqttClient::publish zigbee2mqtt/bridge/config/permit_join ()
2021-02-11 08:29:32.181 (Zigbee2MQTT) Zigbee2mqtt log level is debug
2021-02-11 08:29:32.181 (Zigbee2MQTT) Joining new devices is disabled on the zigbee bridge
2021-02-11 08:29:32.232 (Zigbee2MQTT) New request: [2] devices_get({})
2021-02-11 08:29:32.232 (Zigbee2MQTT) MqttClient::publish zigbee2mqtt/bridge/config/devices/get ()
2021-02-11 08:29:32.352 (Zigbee2MQTT) New request: [3] groups_get({})
2021-02-11 08:29:32.352 (Zigbee2MQTT) MqttClient::publish zigbee2mqtt/bridge/config/groups ()
2021-02-11 08:29:32.412 (Zigbee2MQTT) Received groups list from bridge
2021-02-11 08:29:33.314 (Zigbee2MQTT) New request: [4] bridge_set_permitjoin("true")
2021-02-11 08:29:33.314 (Zigbee2MQTT) MqttClient::publish zigbee2mqtt/bridge/config/permit_join (true)
2021-02-11 08:29:33.730 (Zigbee2MQTT) Zigbee2mqtt log level is debug
2021-02-11 08:29:33.730 (Zigbee2MQTT) Joining new devices is enabled on the zigbee bridge
2021-02-11 08:29:34.282 (Zigbee2MQTT) New request: [5] bridge_set_permitjoin("true")
2021-02-11 08:29:34.282 (Zigbee2MQTT) MqttClient::publish zigbee2mqtt/bridge/config/permit_join (true)
2021-02-11 08:29:35.897 (Zigbee2MQTT) MqttClient::ping
2021-02-11 08:29:45.875 (Zigbee2MQTT) MqttClient::ping
2021-02-11 08:29:48.335 (Zigbee2MQTT) MqttClient::publish zigbee2mqtt/bridge/config/devices/get ()
2021-02-11 08:29:55.912 (Zigbee2MQTT) MqttClient::ping
2021-02-11 08:30:00.654 (Zigbee2MQTT) Received available devices list from bridge
2021-02-11 08:30:00.655 (Zigbee2MQTT) Coordinator address is 0x00124b00216000b9
2021-02-11 08:30:00.688 (Zigbee2MQTT) {"access": 7, "description": "Color temperature after cold power on of this light", "name": "color_temp_startup", "presets": [{"description": "Coolest temperature supported", "name": "coolest", "value": 150}, {"description": "Cool temperature (250 mireds / 4000 Kelvin)", "name": "cool", "value": 250}, {"description": "Neutral temperature (370 mireds / 2700 Kelvin)", "name": "neutral", "value": 370}, {"description": "Warm temperature (454 mireds / 2200 Kelvin)", "name": "warm", "value": 454}, {"description": "Warmest temperature supported", "name": "warmest", "value": 500}, {"description": "Restore previous color_temp on cold power on", "name": "previous", "value": 65535}], "property": "color_temp_startup", "type": "numeric", "unit": "mired", "value_max": 500, "value_min": 150}
2021-02-11 08:30:00.688 (Zigbee2MQTT) {"description": "Color of this light expressed as hue/saturation", "features": [{"access": 7, "name": "hue", "property": "hue", "type": "numeric"}, {"access": 7, "name": "saturation", "property": "saturation", "type": "numeric"}], "name": "color_hs", "property": "color", "type": "composite"}
2021-02-11 08:30:00.688 (Zigbee2MQTT) Creating domoticz device to handle "effect" key for device with ieeeAddr 0x0017880106a30bc3
2021-02-11 08:30:00.690 (Zigbee2MQTT) {"access": 7, "description": "Color temperature after cold power on of this light", "name": "color_temp_startup", "presets": [{"description": "Coolest temperature supported", "name": "coolest", "value": 150}, {"description": "Cool temperature (250 mireds / 4000 Kelvin)", "name": "cool", "value": 250}, {"description": "Neutral temperature (370 mireds / 2700 Kelvin)", "name": "neutral", "value": 370}, {"description": "Warm temperature (454 mireds / 2200 Kelvin)", "name": "warm", "value": 454}, {"description": "Warmest temperature supported", "name": "warmest", "value": 500}, {"description": "Restore previous color_temp on cold power on", "name": "previous", "value": 65535}], "property": "color_temp_startup", "type": "numeric", "unit": "mired", "value_max": 500, "value_min": 150}
2021-02-11 08:30:00.691 (Zigbee2MQTT) Creating domoticz device to handle "effect" key for device with ieeeAddr 0x00124b00222e14f5
2021-02-11 08:30:00.692 (Zigbee2MQTT) Creating domoticz device to handle "battery" key for device with ieeeAddr 0x0008890001d9f7e1
2021-02-11 08:30:00.693 (Zigbee2MQTT) Creating domoticz device to handle "action" key for device with ieeeAddr 0x0008890001d9f7e1
2021-02-11 08:30:00.696 (Zigbee2MQTT) Creating domoticz device to handle "linkquality" key for device with ieeeAddr 0x0008890001d9f7e1
2021-02-11 08:30:00.687 Error: (Zigbee2MQTT) 0x0017880106a30bc3: can not process numeric item "color_temp_startup"
2021-02-11 08:30:00.688 Error: (Zigbee2MQTT) 0x0017880106a30bc3: can not process feature type "composite"
2021-02-11 08:30:00.689 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-11 08:30:00.689 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-11 08:30:00.689 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-11 08:30:00.690 Error: (Zigbee2MQTT) 0x00124b00222e14f5: can not process numeric item "color_temp_startup"
2021-02-11 08:30:00.691 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-11 08:30:00.691 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-11 08:30:00.691 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-11 08:30:00.692 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-11 08:30:00.692 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-11 08:30:00.692 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-11 08:30:00.695 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-11 08:30:00.695 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-11 08:30:00.695 Error: Device creation failed, Device object is not associated with a plugin.
2021-02-11 08:30:00.696 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2021-02-11 08:30:00.696 Error: (Zigbee2MQTT) 'CDevice_init' failed 'TypeError':'an integer is required (got type NoneType)'.
2021-02-11 08:30:00.696 Error: Device creation failed, Device object is not associated with a plugin.

Is the issue still valid?


PolicyMode parameter not effective

#13 not resolved as the PolicyMode parameter is not used to change the policy file.
Due to this line being commented out
https://github.com/jklotzsche-msft/PS.MTA-STS/blob/93d559fe85245214335bd4c3fbee027053d33c9a/PS.MTA-STS/functions/New-PSMTASTSFunctionAppDeployment.ps1#L215

is fixed already. Will be published with the new version today.


Add additional logic to the tweet posting, to only actually tweet from CI

There's probably a standard Actions env variable to check

Implemented in 08d73c4.


add mmio interface and mmio_region class

The first commit re-writes line endings for a couple of files that were saved in DOS format.

How does this tie in with the discussion last week about MMIO (really CSR) access for devices without actual memory mapped I/O? I believe the result of the discussion was that the explicit read/write calls would work despite the CSRs not being mappable.

@michael-adler In the case that MMIO is not supported, we would need a mechanism to swap the concrete class to an alternate implementation in the factory.  In that case, we might want the factory function in the MMIO class itself, and we might also want it to be given a flag of how to behave if MMIO is not supported (whether to fail to allocate an mmio or to give an alternate concrete).

An alternative implementation has been requested.


Release azure-cli-profile 0.1.2rc2

Reviewers, please verify the following for this PR:

[ ] The PR title has format Release <component-name> <version>.
[ ] setup.py has been modified with the same version as in the PR title.
[ ] HISTORY.rst has been modified with appropriate release notes.
[ ] If releasing azure-cli or azure-cli-core, __version__ defined in __init__.py should also be modified to match.

Release of 'azure-cli-profile' with version '0.1.2rc2' successful. View at https://pypi.python.org/pypi/azure-cli-profile/0.1.2rc2.

GitHub release created. https://github.com/Azure/azure-cli/releases.


Discovery work required by Data Viz to enable spatial visualizations based off visium and slide-seq datasets

Product discovery proposed for Q4 (Sep - Nov)
In no particular order:

User Research: Conduct interviews and surveys with data submitters and consumers to understand their needs, pain points, and expectations when it comes to visualizing Visium and Slide-seq data.
Competitive Analysis: Review other tools or platforms that support Visium and Slide-seq data visualization to identify their strengths, weaknesses, and unique features.
Technical Feasibility: Assess the technical requirements and feasibility of supporting visualization of these data types. Aligns with DP Discovery work points 1 and 2
UI/Usability: How can CELLxGENE ensure a user-friendly experience for data submitters and consumers when they are working with these new data types? What UI/UX principles would need to be applied?
Wireframe Development: Create initial wireframes of the new visualization features based on the early findings from user research and technical feasibility studies.

From early reading and in no particular order, Data Viz would need to prioritize and complete some form of discovery work on the possible features required for spatial visualizations:

Spatial Visualization Tools: Integration of spatial coordinates to display gene expression data overlaid on tissue images. Users should be able to zoom into regions of interest and select individual cells or cell clusters to view detailed gene expression profiles (demo from current user does highlight some of this already - https://github.com/chanzuckerberg/cellxgene/issues/2056#issuecomment-1667568140). Based on the comments from the thread, we could use some of the code from VIP to expand on our prototype).

Integrated Histological Data: Allow users to toggle between gene expression heatmaps and traditional histology or immunohistochemistry images.

Spatial Clustering: Algorithms designed specifically for spatial data that can identify clusters or regions of interest based on spatial gene expression patterns. This would require some comp bio resourcing

3D Visualization: If 3D spatial transcriptomics data become more common, tools to visualize gene expression in a 3D context would be invaluable.

Spatial Differential Expression: Tools to identify genes that are differentially expressed in specific spatial regions or between different tissue types.

Advanced Image Processing: Tools that help clean up and enhance tissue images, adjust for artifacts, or even integrate with other imaging modalities.

Integration with Non-spatial Data: Tools to integrate spatial data with traditional single-cell RNA sequencing data, enabling users to correlate spatial and non-spatial findings.

Also see Spatial Talking Points related to the earlier prototype.


setVisibleRange() is not working

Hello.
I want to show the price information for the last 2 months.
But unlike Javascript, it was not applied in Android kotlin.
//chartData has 365 days of information
val fromT = Time.StringTime((chartData.get(chartData.length() - 60) as JSONObject).getString("time")) // 2021-08-15
val nowT = Time.StringTime((chartData.get(chartData.length() - 1) as JSONObject).getString("time")) // 2021-10-15
chartsView.api.timeScale.setVisibleRange(TimeRange(fromT, nowT))
However, the results always show the widest range of data that can be displayed on the screen.
How can I apply it to get the results I want?
Thank you so much.

Hi. This is my app logs.
I make a virtual investment application, so all data have the future date.

The bridge between js and native seems ok because we see logs in the Chrome inspector. So I guess this is a tricky case.
Can you make a demo with reproducing of this bug?
Also, can you send a version name of WebView implementation?

It would be helpful if you will provide code. I've tried to reproduce your case but no luck


Save / Cancel / Delete buttons in YAML editor

We need some feedback about where to define the Save / Cancel / Delete buttons in the editor.
There is a WIP following the recommendation from patternfly:

On this WIP the approach was to move the "Delete" from an "Actions" placed in top-right of the editor to put them together but we have feedback from QE about it.
Note, that one main difference in terms of "feature" is Kiali won't move automatically to the list view when click "Save" button.

what JIRA is this for?
Is this seeking recommendation regarding only the location of the buttons or also about the expected behavior when they are pressed?
Please provide the link to the patternfly recommendation this is based on.

On this WIP the approach was to move the "Delete" from an "Actions" placed in top-right of the editor to put them together but we have feedback from QE about it.

what is the feedback from QE? please provide some details.

Note, that one main difference in terms of "feature" is Kiali won't move automatically to the list view when click "Save" button.

difference from what?
what is the behavior when clicking on Delete?

what JIRA is this for?

https://issues.jboss.org/browse/KIALI-1655

Is this seeking recommendation regarding only the location of the buttons or also about the expected behavior when they are pressed?

Only the location of the buttons.

Please provide the link to the patternfly recommendation this is based on.

https://www.patternfly.org/pattern-library/forms-and-controls/buttons-on-forms/#overview
and
https://www.patternfly.org/pattern-library/forms-and-controls/buttons-on-forms/#design

On this WIP the approach was to move the "Delete" from an "Actions" placed in top-right of the editor to put them together but we have feedback from QE about it.

what is the feedback from QE? please provide some details.

To maintain Save / Cancel buttons below the editor but maintain the Delete action on top / right editor.

Note, that one main difference in terms of "feature" is Kiali won't move automatically to the list view when click "Save" button.

difference from what?

OpenShift YAML editor moves to list view on save.
On Kiali we don't want to move automatically to list as we want to continue editing and showing the validations coming from the backend.

what is the behavior when clicking on Delete?

On this case, as the editing object doesn't exist, it moves back to the list view.

@serenamarie125 @cshinn please review ^^

Summary:

have Save/Cancel buttons
Cancel will discards the changes
Cancel will go back to overview page if it exists, if not (in Istio config) it will move the user to the list page.
Delete will remove the object
Delete should be moved to actions menu on the top of the screen, make it available in both overview and yaml tabs.
Yaml view can be now of 2 types: for users with no permissions to edit it will remain "vew only" like today. For users with permissions to edit it will become always an "editable view".
Suggestion for another feature - A reload button + a notification indicating that the object has been modified by someone else.

@lucasponce if we got everything we need here, I suggest closing the issue

I think we have a side effect related to this.
In theory it's a pure implementation aspect but I think it will have implications in the UX side.
Today, Kiali can browse VirtualServices and DestinationRules from two places:

Under Service details page.
Under Istio Config details page.

As part of a pure implementation approach, we are trying to unify to maintain just a single component, not two.
But, there is an important use case not discussed, accesing to a VirtualService/DestinationRule from the Service details and edit them can "unlink" the object with the Service.
Under this scenario the current breadcrumb navigation is not valid as the Service is not linked with the object anymore.
So, discussed with the team, we think that probably best approach is to maintain a single component under Istio Config details and when user browse the details of the VS/DR from Service details will move to IstioConfig details.
On this case, IstioConfig details would support OverView / YAML views for VS/DR objects and when coming from a Service details we can enable a "Back to service" link, but we can't maintain the breadcrumb as it is today maintaining the technical debt we have today.
We need to comment this as it is blocking other areas.
The main implication from user perspective will be that when he/she clicks into a VR/DR instead to have a breadcrumb like today:

It will have something like:

With an additional link to implement the "Back to Service" functionality.

Not sure I get that, but one thing related. Suppose you edit a VS - will you have (view) access to the matching DR? E.g. if the DR defines subsets, you want to be able to see them while editing the VS, so that you can refer to the correct ones.

@pilhuhn the scope of this one is in the YAML editor, at the moment we are not (yet) thinking in pure GUI create/update scenario.

Yes I am talking about the Yaml editor. Very often a VS or DR does not come alone, but they refer to each other. Suppose you edit a DR and change the subset name. This may by itself be no issue, but it may render the VS invalid.

This may by itself be no issue, but it may render the VS invalid.

Yes, the Kiali validations coming from backend are untouched.
But we need to have an agreement on this, as currently we can't continue the implementation without clarifying this issue.

is this a purely navigation aspect that needs to be solved @lucasponce ?

@lucasponce this issue was defined about "where to define the Save / Cancel / Delete buttons in the editor."
As we discussed it in prior comments:
"Is this seeking recommendation regarding only the location of the buttons or also about the expected behavior when they are pressed?"
"Only the location of the buttons."
And for the above I believe we received all the needed input from UX.
So though you are raising very good points, they should be first sorted out on a functional level and in a separate issue. Like for example "should user be able to unlink a DR from a service while being in the context of that service"? And even more basic "should user be able to unlink a DR from a service"

When clicking on VS/DR details, user will move to a unified location under IstioConfig details.
IstioConfig details will support Overview / YAML for VS/DR (as today) and only YAML for rest of the types.
IstioConfig details will have a "Back to Service" link in case that user comes from Service Details page.

The functional context is missing here IMO.
For all the 3 points above I think that some examples/explanations/use cases are needed, otherwise it is hard to see if there is an agreement.
For example - why should the user be moved to VS/DR in IstioConfig unlike today?
And again, it is less related to where to place the Save/Cancel buttons, or the recommendation to move the Delete button to the top menu.

@abonas we cannot progress with the recommendation defined in
https://github.com/kiali/kiali-design/issues/68#issuecomment-445860194
Explanation with all details are defined in
https://github.com/kiali/kiali-design/issues/68#issuecomment-446591844
Again, this is related, we can't split it in more minor issues without missing the context of the whole discussion.

@lucasponce I think are mixing things here

position of the buttons
behaviour on exit of the editor

The 1st one is clear I guess
The 2nd one is indeed a bit more complicated when you think of "unlinking" by accidentally overwriting a part of the yaml in a bad way (e.g. mistyping the target host). We should cache some properties of the content like the target host when the user starts editing and then upon (trying to exit) compare with the saved value. If they match, we go back to where we came from.
If they do not match, we display a warning popup "You unlinked - did you really want to do that?" If the user confirms, we go to istio-config list. Otherwise we go where we came from. We should even have a 3rd button "edit again".
Does that help you?

@lucasponce I think are mixing things here

position of the buttons
behaviour on exit of the editor

The 1st one is clear I guess
The 2nd one is indeed a bit more complicated when you think of "unlinking" by accidentally overwriting a part of the yaml in a bad way (e.g. mistyping the target host). We should cache some properties of the content like the target host when the user starts editing and then upon (trying to exit) compare with the saved value. If they match, we go back to where we came from.
If they do not match, we display a warning popup "You unlinked - did you really want to do that?" If the user confirms, we go to istio-config list.

I think that switching to the istio config "in the middle" of editing is going to surprise users
unless you meant only after they press "save"
Otherwise we go where we came from. We should even have a 3rd button "edit again".
I'm not clear what is this third button for :)
It sounds non standard.
and please let's not suggest new buttons on this thread, but instead define a use case and ask the UX team what kind of control and behavior should apply to it.
The initial thread here got answered by the UX team in full.
Hence keeping the current thread open with new questions and ideas will be a source of a great confusion.

Does that help you?

@lucasponce I think are mixing things here

position of the buttons
behaviour on exit of the editor

The 1st one is clear I guess
The 2nd one is indeed a bit more complicated when you think of "unlinking" by accidentally overwriting a part of the yaml in a bad way (e.g. mistyping the target host).
We should cache some properties of the content like the target host when the user starts editing and then upon (trying to exit) compare with the saved value.

If they (saved host and host after editing) match, we go back to where we came from.
If they do not match, we display a warning popup "You unlinked - did you really want to do that?"
**  If the user confirms, we go to istio-config list.
**  Otherwise we go where we came from.
** We should even have a 3rd option "edit again". So that the user can fix the mistake before the config gets applied

I'm not clear what is this third option about exactly :)
It sounds non standard.
And please let's not suggest new buttons on this thread, but instead define a use case and ask the UX team what kind of control and behavior should apply to it.
The initial thread here got answered by the UX team in full.
Hence keeping the current thread open with new questions and ideas will be a source of a great confusion.

Does that help you?

Hence keeping the current thread open with new questions and ideas will be a source of a great confusion.

The position of the buttons is clear (thanks).
But I guess this is raising another discussion that is related and it's causing some situations not clear.
I will close this one and open a new one.


[SPARK-45791][CONNECT][TESTS] Rename SparkConnectSessionHodlerSuite.scala to SparkConnectSessionHolderSuite.scala

What changes were proposed in this pull request?
This PR aims to fix a typo Hodler in file name.

SparkConnectSessionHodlerSuite.scala (from)
SparkConnectSessionHolderSuite.scala (to)

It's also unmatched with the class name in the file because class name itself is correct.
https://github.com/apache/spark/blob/3363c2af3f6a59363135451d251f25e328a4fddf/connector/connect/server/src/test/scala/org/apache/spark/sql/connect/service/SparkConnectSessionHodlerSuite.scala#L37
Why are the changes needed?
This is a typo from the original PR.

https://github.com/apache/spark/pull/41580

Since the original PR is shipped as Apache Spark 3.5.0, I created a JIRA instead of a follow-up. We need to backport this patch to branch-3.5.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @HyukjinKwon and @rangadi

Thank you, @yaooqinn ! Merged to master/3.5.

Thanks for fixing this!

Now that ReleaseSession exists, we don't HODL the session excessively anymore :-)


"Extend this..." refactor

I want to extend somebody else's types. In figuring out how to do so, I generally use "Go to Type Definition" to go and get a better idea of how the types are written so that I can figure out how to extend the types in question.
Then, without fail, I end up googling "typescript extend third-party types" and get answers from 2015-2018, ranging from "Based on how the definition is currently written you can't extend it externally" to "do this":
declare module "koa" {
    interface Context {
        resource: any;
    }
}

I find these really confusing to write (namespace vs. module vs. interface; should it be declare global?) and it requires a lot of guess and check.
It would be nice if I could right-click on an import or be able to have a "Quick fix" for Property 'foo' does not exist on type 'bar'. that would insert the appropriate code to extend that particular type.
(I don't actually think a "Quick fix" would be a good idea since that is in most cases not what you want to be doing, but hopefully you get my point).
Alternatively, maybe this is an opportunity for improvement on https://www.typescriptlang.org/docs/handbook/declaration-merging.html.

Sounds like a good candidate for a TypeScript service plugin


Update vcpkg port

The latest vcpkg port is on 10f148cef0dfd34ae1a9373b9396beb1581c992a, which seems to be a bit over two years old:
// D3D12MemAlloc.h

<b>Version 2.0.0-development</b> (2021-03-11)

I am sorry but vcpkg port is not managed by us. This library is offered through this GitHub repository. Every port or binding to a different programming language or distribution platform is out of scope. We welcome external contributions and we can link to them from README, as we do in this case.


Ui-Form

I can't find the Ui-Form in myui.Maybe you haven't provide it

Sorry, I forgot that. Now, I upload these related files.


fix #42 fix getting sidebars

Looks like this is an alternative implementation to #46 :sweat_smile:


Feature request: color coding for pre-processor directives

It would be nice to see code in pre-processor directives grayed.
Thanks for the project,
Have a nice day

C# extension now supports semantic highlighting which would grey code when not not included.