UTF-8 issue

Issue Type: Bug
Hi I was recently working on python project where I had to use UTF-8 charapters (georgian) and when I compiled the program I saw that one letter was into another It happens everytime when I'm trying to compile program please fix it it's very annoying!
VS Code version: Code 1.36.0 (0f3794b38477eea13fb47fbe15a42798e6129338, 2019-07-03T13:25:46.372Z)
OS version: Windows_NT x64 10.0.18362
Extensions (4)

Extension
Author (truncated)
Version

vsc-material-theme
Equ
29.2.0

fontsize-shortcuts
fos
1.5.0

python
ms-
2019.6.22090

vscode-icons
vsc
8.8.0

(1 theme extensions excluded)

Can you please provide a screenshot showing what you are seeing. Where do you see these mixed characters?

Can you please provide a screenshot showing what you are seeing. Where do you see these mixed characters?
Sure so first image is from vs code and second image is from atom to see how it should be
First:
Second:

@michaaa123 you see that in the editor pane. Right?

@michaaa123 Can you please provide that text in a copy-paste friendly format?

@michaaa123 you see that in the editor pane. Right?

No the issue is presented in the terminal after when I try to get some text on the screen for instance  in the above picture I was asking to user for input some information and when the text was presented words were mixed

@michaaa123 Can you please provide that text in a copy-paste friendly format?

sure: ჩაწერეთ პინ კოდი რათა შეხვიდეთ:

I could not reproduce it on macOS, it might be a Windows specific issue in the terminal:

Adding this setting might help:
"terminal.integrated.rendererType": "dom"

But I think this is mainly that the terminal doesn't support RTL languages https://github.com/xtermjs/xterm.js/issues/701


jekyll doesn't seem to work

My channel is pointing at nixos-16.03pre73106.b1dca6c.
$ nix-shell -p jekyll

[nix-shell:~]$ jekyll
/nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/execjs-2.5.2/lib/execjs/runtimes.rb:48:in `autodetect': Could not find a JavaScript runtime. See https://github.com/rails/execjs for a list of available runtimes. (ExecJS::RuntimeUnavailable)
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/execjs-2.5.2/lib/execjs.rb:5:in `<module:ExecJS>'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/execjs-2.5.2/lib/execjs.rb:4:in `<top (required)>'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/coffee-script-2.4.1/lib/coffee_script.rb:1:in `require'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/coffee-script-2.4.1/lib/coffee_script.rb:1:in `<top (required)>'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/coffee-script-2.4.1/lib/coffee-script.rb:1:in `require'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/coffee-script-2.4.1/lib/coffee-script.rb:1:in `<top (required)>'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/jekyll-coffeescript-1.0.1/lib/jekyll-coffeescript.rb:2:in `require'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/jekyll-coffeescript-1.0.1/lib/jekyll-coffeescript.rb:2:in `<top (required)>'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/jekyll-2.5.3/lib/jekyll/deprecator.rb:46:in `require'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/jekyll-2.5.3/lib/jekyll/deprecator.rb:46:in `block in gracefully_require'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/jekyll-2.5.3/lib/jekyll/deprecator.rb:44:in `each'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/jekyll-2.5.3/lib/jekyll/deprecator.rb:44:in `gracefully_require'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/jekyll-2.5.3/lib/jekyll.rb:166:in `<top (required)>'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/jekyll-2.5.3/bin/jekyll:6:in `require'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/lib/ruby/gems/2.1.6/gems/jekyll-2.5.3/bin/jekyll:6:in `<top (required)>'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/bin/jekyll:21:in `load'
	from /nix/store/ymbp77pi88prxd1q43i9r3cmd3fcf0xi-jekyll-2.5.3/bin/jekyll:21:in `<main>'

cc @pesterhazy

Works for me, but I also have nodejs installed.

Ah, so that implicit dependency should probably be added to the package, right?

I'd guess so, but v8 is probably the better choice here because it is a lot lighter.

execjs is just a dispatcher to one of the compatible JavaScript engines but you need at least one. The nodejs-one is really the most stable in my experience.

Makes sense, but it still seems like the dispatcher chosen should be represented in the expression and not via environment at runtime, right? I can make the change if interested parties agree on that.

On Dec 9, 2015, at 12:42, zimbatm<EMAIL_ADDRESS>wrote:
execjs is just a dispatcher to one of the compatible JavaScript engines but you need at least one. The nodejs-one is really the most stable in my experience.
―
Reply to this email directly or view it on GitHub.

v8 is what node uses anyhow, but node also comes with npm and a lot of other stuff. And yes, we all want packages to work after installing them, therefore the expression should depend on a javascript engine.

@copumpkin agreed, it shouldn't depend on the user's environment
@jgillich do you mean v8 as a standalone executable or the ruby bindings (aka therubyracer) ? I didn't know the former was an option. The latter is not really good in my experience, having two GC in the same process and referencing each-other's objects tend to not go very well.

v8 standalone is also listed, so I guess it supports both?

This is also fixed by #12226, since Jekyll v3 no longer depends on ExecJS.

:beers:

This can be closed I think.

yup, thanks!


Project Screen needs to be improved (use videos?)

Overview
We've got really great welcome screen after @shashigharti 's PR #164 (playing a role of the create dialog of the same time):

What is missing is some help texts especially on a first run of the application (countFIles() == 0).
Implementation

[ ] add a dialog title
[ ] add really short general help messages
[ ] add really short help messages to every button
[ ] probably disable some buttons if there are no files (e.g. can't have a chart if no table)

@roll  I'm closing this issue since we are working on this in #418


Adding dynamicvoronoi to documentation index for distro

Please add dynamicvoronoi to documentation index for distro.
I want to publish catkinized version of http://wiki.ros.org/dynamicvoronoi which I use in another package.

The two commits together are a no-op?


Hue init action misconfigures webhdfs on HA

Hue has a warning like this.
hadoop.hdfs_clusters.default.webhdfs_url

Current value: http://<IP_ADDRESS>:9870/webhdfs/v1
Failed to access filesystem root

This is sort of due to a bug in Dataproc -- we set the namenode http (aka webhdfs) port to 9870 on standard clusters, and use dfs.namenode.address. HA clusters have this set as well. However, HA namenodes use a different config called dfs.namenode.address.<name-service-id>.<namenode-id>, but we set that to 50070.
We're fixing that in Dataproc 1.3 to be port 9870, even on HA clusters.
In the mean time, the Hue init action will need a better way to discover the NN's web address.

Dataproc 1.3 is the default image version now, so closing this issue.


optimize kafka computePartitionGroupMetadata with KafkaAdminClient

we recently had some dns instability issues w/ our kafka cluster that caused consumer creation to fail since it couldn't resolve broker dns. while investigating, we noticed that we were creating N consumers every time a new realtime segment was created where N is the number of partitions on the topic. we have some topics w/ a high partition count like 200.
[2023-06-27 02:50:30.459797] INFO [KafkaConsumer] [HelixTaskExecutor-message_handle_thread_27:17] [Consumer clientId=example_table-example_topic-5, groupId=pinot-table-group1] Subscribed to partition(s): example_topic-100
[2023-06-27 02:50:30.459840] INFO [KafkaConsumer] [HelixTaskExecutor-message_handle_thread_27:17] [Consumer clientId=example_table-example_topic-5, groupId=pinot-table-group1] Subscribed to partition(s): example_topic-132
...

it seems like the default implementation of computePartitionGroupMetadata creates all these consumers. i'm wondering if there are any blockers to using the KafkaAdminClient's listOffsets call to achieve the same thing: https://kafka.apache.org/28/javadoc/org/apache/kafka/clients/admin/KafkaAdminClient.html#listOffsets(java.util.Map,org.apache.kafka.clients.admin.ListOffsetsOptions)
here is where it's getting called for new realtime segment creation: https://github.com/apache/pinot/blob/fc26d6d8975b4cd46e26e460236a30e8b1eb2cde/pinot-core/src/main/java/org/apache/pinot/core/data/manager/realtime/LLRealtimeSegmentDataManager.java#L1547-L1549

@dang-stripe The number of consumers created in a single server is same as the number of partitions being consumed on the server. Additionally, it creates multiple short-lived consumer instances to fetch topic metadata, which is what you see in _partitionMetadataProvider .
This is purely due to how the code is organized in the kafka consumer plugin in Pinot (KafkaStreamMetadataProvider inherits from KafkaPartitionLevelConnectionHandler). I also mention it in this issue - https://github.com/apache/pinot/issues/10014#issue-1505401315 (see description Note)

i'm wondering if there are any blockers to using the KafkaAdminClient's listOffsets call to achieve the same thing:

I don't think there are any. KafkaAdminClient didn't exist or was not stable when Pinot's kafka consumer was written. We should replace it avoid all the short-lived consumers.


devportal: Added page for static ip address pricing information HELP-140

Added pricing information on static ip addresses

Very open to layout suggestions as I realise the tables don't look the nicest.. Cheers :)

Hi @allypascoe-aiven thanks for this contribution. Is there a GitHub issue for this task or is this a migration article?
In my understanding, pricing information is a reference and can go under docs/platform/reference with other content like https://docs.aiven.io/docs/platform/reference/list_of_clouds.html
Rather than "The below prices are all in USD and are on a per hourly basis.", the Pricing column could have ** Pricing (USD per hour)** to make it easier for the reader.
Since AWS and Azure have the same pricing across regions, could we make the list smaller by doing something like this:
Amazon Web Services static IP pricing

Cloud Region
Pricing (USD per hour)

any region
0.025

Azure static IP pricing

Cloud Region
Pricing (USD per hour)

any region
0.03

I understand that ^ this might need a confirmation from a solution architect.
I'm OK with the table formatting which look similar to how we have https://docs.aiven.io/docs/platform/reference/list_of_clouds.html
Looking forward to the next revision and please ping me once it's ready for review :)

@dewan-ahmed thanks for the helpful feedback!
Yes, the Github issue is here: https://github.com/aiven/devportal/issues/1141
Relates to this Jira: https://aiven.atlassian.net/browse/HELP-140
I will work on making those changes now - thanks again!

@dewan-ahmed changes have been made and are ready for review - thanks!

Thanks for the changes @allypascoe-aiven
We're currently discussing the best place to host this content and rather than docs.aiven.io, it might be aiven.io/pricing.
I'll comment on this PR once I have some update on this.

Closing this PR since aiven.io/pricing will be a better home for the content will per discussion. Thanks for your contribution @allypascoe-aiven


fix: bad working directory in go runtime push

Fixes working directory syntax for go runtime push action by using
context instead of env var.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: ed5b46015e4d24ac350f4d11ee55c396d77ca479
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


[PowerToys Run] Calculator using floating point math but should use decimal

Environment
Microsoft Windows [Version 10.0.18363.900]
PowerToys version: v0.18.2
PowerToy Run

Steps to reproduce
[Alt][Space] 950.70-40.40
Expected behavior
expected to be shown 910.30  or 910.3
Actual behavior
actual result<PHONE_NUMBER>000001
Screenshots

Yes, it's a known issue. Being worked on. See also #3697

Thanks Jay,  BTW I can't believe how often I use the calculator function.

Yup, #3697 is the issue.


Bug: Default Key generator ignores params (URLSearchParams) changes

What happened?
I am using this project for the first time. I did setup for a Vue 3 project like this:
import { setupCache, buildKeyGenerator } from 'axios-cache-interceptor';

// configura cache.
const axios = setupCache(Axios);

const app = createApp(App)
app.use(VueAxios, axios)

but when I noticed that some requests are cached, even when I change my params. This is my request
    carregarFerias() {
      if (this.unidadeSelecionada && this.startDate && this.endDate) {
        const params = new URLSearchParams([['startDate', this.startDate], ['endDate', this.endDate]]);
        this.axios.get(`./api/lotacao/${this.unidadeSelecionada}`, { params }).then(response => {
          const ferias = response.data;
          console.info('ferias', ferias)
          this.items = ferias.map(this.convertToCalendar);
        })
      }
    },

I only was able to make distinct using a custom key generator:
const axios = setupCache(Axios, {
    generateKey: buildKeyGenerator((request) => ({
        method: request.method,
        baseURL: request.baseURL,
        query: request.query,
        params: request.params,
        data: request.data,
        url: request.url,
        custom: JSON.stringify(request?.params?.toString())
    }))
  });

This works. Then, I used toString directly in params key and took out the custom:
const axios = setupCache(Axios, {
    generateKey: buildKeyGenerator((request) => ({
        method: request.method,
        baseURL: request.baseURL,
        query: request.query,
        params: request.params?.toString(),
        data: request.data,
        url: request.url,
    }))
  });

These two last ways works as I expected.
The docs says it uses params to create a hash

By default, it extracts method, baseURL, query, params, data and url properties from the request object and hashes it into a number with object-code.

I think I should not have to create my own key generator to be able to use this tool.
Please let me know if I am doing something wrong.
Best Regards,
A. Lucas
axios-cache-interceptor version
v1.3.2
Node / Browser Version
node -v v18.18.0 / Firefox 119.0 / Microsoft Edge Version 119.0.2151.72
Axios Version
"axios": "^1.5.1",
What storage is being used
Web Storage
Relevant debugging log output
I did not found anything relevant. By default, all my requests to the same endpoint are cached by the first, ignoring my params:

carregar ferias ASSJUR 2023-12-01 2023-12-31 Unidade-75ea745c.js:554:15
Object { id: "261329920", msg: "Sending request, waiting for response", data: {…} }
index-7b0f523b.js:10468:335
Object { id: "261329920", msg: "Useful response configuration found", data: {…} }
index-7b0f523b.js:10550:129
Object { id: "261329920", msg: "Found waiting deferred(s) and resolved them" }
index-7b0f523b.js:10552:69
Object { id: "261329920", msg: "Response cached", data: {…} }
index-7b0f523b.js:10552:184
ferias
Array [ {…} ]
Unidade-75ea745c.js:559:19
periodChanged watch Unidade-75ea745c.js:570:15
2023-11-01 2023-11-30 Unidade-75ea745c.js:573:15
carregar ferias ASSJUR 2023-11-01 2023-11-30 Unidade-75ea745c.js:554:15
Object { id: "261329920", msg: "Returning cached response" }
index-7b0f523b.js:10485:11
Object { id: "261329920", msg: "Returned cached response" }
index-7b0f523b.js:10529:17
ferias
Array [ {…} ]

Implemented at v1.3.2


[BUG] Latest main branch cannot pass unittest, missing few python files

Describe the bug
Latest main branch cannot pass unittest, missing few python files
To Reproduce
Steps to reproduce the behavior:

make test

Screenshots
If applicable, add screenshots to help explain your problem. ImportError while loading conftest '/home/graphscope/GraphScope/python/graphscope/tests/conftest.py'. graphscope/__init__.py:19: in <module>     from graphscope.analytical.app import * graphscope/analytical/app/__init__.py:21: in <module>     from graphscope.analytical.app.attribute_assortativity import \ graphscope/analytical/app/attribute_assortativity.py:22: in <module>     from graphscope.framework.app import AppAssets graphscope/framework/app.py:30: in <module>     from graphscope.framework.context import create_context_node graphscope/framework/context.py:28: in <module>     from graphscope.framework import dag_utils graphscope/framework/dag_utils.py:22: in <module>     from graphscope.framework import utils graphscope/framework/utils.py:39: in <module>     from graphscope.framework.errors import check_argument graphscope/framework/errors.py:21: in <module>     from graphscope.proto import error_codes_pb2 E   ImportError: cannot import name 'error_codes_pb2' from 'graphscope.proto' (/home/graphscope/GraphScope/python/graphscope/proto/__init__.py) make: *** [unittest] Error 4
Environment (please complete the following information):

GraphScope version: master
OS: Linux
Version Ubuntu 20.04

Hi， may I ask if this is a fresh environment / repo, or you updated from the previous version?
The latest PR #1547 has a directory change of proto files.

You need to make graphscope first

You need to make graphscope first

neglected from my description, yes, by all means, I have done make graphscope

Hi， may I ask if this is a fresh environment / repo, or you updated from the previous version? The latest PR #1547 has a directory change of proto files.

checked out from the latest main branch.

Thanks for sharing, I will try to reproduce the bug.

Can you do ls /home/graphscope/GraphScope/python/graphscope/proto/ and copy the output to here?

Can you do ls /home/graphscope/GraphScope/python/graphscope/proto/ and copy the output to here?

-rw-rw-r-- 1 1006 1006 2707 May 18 09:41 attr_value.proto -rw-rw-r-- 1 1006 1006 1405 May 18 09:41 coordinator_service.proto -rw-rw-r-- 1 1006 1006 2330 May 18 09:41 data_types.proto -rw-rw-r-- 1 1006 1006 2445 May 18 09:41 ddl_service.proto -rw-rw-r-- 1 1006 1006  993 May 18 09:41 engine_service.proto -rw-rw-r-- 1 1006 1006 2649 May 18 09:41 error_codes.proto -rw-rw-r-- 1 1006 1006 3762 May 18 09:41 graph_def.proto -rw-rw-r-- 1 1006 1006  683 May 18 09:41 __init__.py -rw-rw-r-- 1 1006 1006 4751 May 18 09:41 message.proto -rw-rw-r-- 1 1006 1006 2453 May 18 09:41 op_def.proto -rw-rw-r-- 1 1006 1006 4135 May 18 09:41 proto_generator.py -rw-rw-r-- 1 1006 1006 6687 May 18 09:41 types.proto -rw-rw-r-- 1 1006 1006 2063 May 18 09:41 write_service.proto

The python proto files should be generated in this place while there is none. So I guess the make graphscope may have some errors.
You can generate it manually by cd /home/graphscope/GraphScope/python && python3 setup.py build_proto. Then the tests should pass.

Closed as stale.
@hh2712 Thanks for the reporting and feel free to reopen if you are still blocked by this issue.


PinYin.permlink sometimes missed the first word or the last word

[1] pry(main)> PinYin.permlink('编A0_1三级标签')
=> "A0-1-san-ji-biao-qian"
[2] pry(main)> PinYin.permlink('编写A0_1三级标签')
=> "bian-xie-A0-1-san-ji-biao"
[3] pry(main)> PinYin.backend = PinYin::Backend::Simple.new
=> #<PinYin::Backend::Simple:0x000000000e7e28f0 @override_files=[]>
[4] pry(main)> PinYin.permlink('编写A0_1三级标签')
=> "bian-xie-A01-san-ji-biao-qian"

There is a workround:
def convert_to_pingyin(string, sep='_')
  result = []
  chars = string.split("")
  chars.each_with_index do |char, index|
    if char =~ /\p{Han}/
      converted_char = PinYin.permlink(char)
      result << converted_char
    else
      result << char
    end

    if index < chars.length - 1
      next_char = chars[index + 1]
      if (char =~ /\p{Han}/ || next_char =~ /\p{Han}/) && [char, next_char].exclude?(sep)
        result << '_'
      end
    end
  end
  result.join('')
end

[160] pry(main)> convert_to_pingyin('编A0_1三级标签')
=> "bian_A0_1_san_ji_biao_qian"
[161] pry(main)> convert_to_pingyin('编写A0_1三级标签')
=> "bian_xie_A0_1_san_ji_biao_qian"
[162] pry(main)> convert_to_pingyin('编写A0_1三级标签_')
=> "bian_xie_A0_1_san_ji_biao_qian_"
[163] pry(main)> convert_to_pingyin('_编写A0_1三级标签_')
=> "_bian_xie_A0_1_san_ji_biao_qian_"
[164] pry(main)> convert_to_pingyin('_编写_A0__1三级标签_')
=> "_bian_xie_A0__1_san_ji_biao_qian_"
[165] pry(main)> convert_to_pingyin('_编写_A0__1三级标签_哦')
=> "_bian_xie_A0__1_san_ji_biao_qian_o"


Support for socket AF_BLUETOOTH in python standard lib

⚠ Disclaimer: I'm new around here. ⚠
As mentioned in https://github.com/docker-library/python/issues/444 , python 3 has native support for bluetooth sockets, with socket family AF_BLUETOOTH
However, it only has support for it if built with bluetooth.h in the dependencies
Before:
└─▪docker run -it python:3.7 python
Unable to find image 'python:3.7' locally
3.7: Pulling from library/python
16ea0e8c8879: Pull complete
50024b0106d5: Pull complete
ff95660c6937: Pull complete
9c7d0e5c0bc2: Pull complete
29c4fb388fdf: Pull complete
8659dae93050: Pull complete
c8208a94eb32: Pull complete
465b26a31c40: Pull complete
84af071ddf6f: Pull complete
Digest: sha256:4ce3a6ba2c2103d50ac59d18d46a484ad1b489b89609f548ef78f02d43eaecf9
Status: Downloaded newer image for python:3.7
Python 3.7.6 (default, Dec 20 2019, 22:36:14)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from socket import AF_BLUETOOTH"
  File "<stdin>", line 1
    from socket import AF_BLUETOOTH"
                                   ^
SyntaxError: EOL while scanning string literal
>>> from socket import AF_BLUETOOTH
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'AF_BLUETOOTH' from 'socket' (/usr/local/lib/python3.7/socket.py)

After:
└─▪docker run -it sergio/py37 python
Python 3.7.6 (default, Dec 21 2019, 23:33:58)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from socket import AF_BLUETOOTH
>>> AF_BLUETOOTH
<AddressFamily.AF_BLUETOOTH: 31>
>>>

This might be a bit too much to add to the slim images, but since this is a native python support, I was wondering if it would make sense to include in these images.
Some mentions of the issue:

https://github.com/ContinuumIO/anaconda-issues/issues/1035
https://stackoverflow.com/questions/29107537/missing-socket-af-bluetooth-in-anaconda-python
https://gitlab.alpinelinux.org/alpine/aports/issues/7352

I have not ran update.sh. I have ran update.sh but the pip version commit hash is broken. Had to hard-code it to generate the Dockerfiles
This change does not apply to 2.x, but since 2.x is deprecated in 9 days anyway

Update: On Ubuntu 18 python comes built with bluetooth support, so this change makes the behaviour similar to, for example, doing a apt install python

Since https://github.com/docker-library/python/pull/442 was merged this now needs a rebase. We can help if you like.

Ok, if I understood correctly, I'll:

Rebase
Move the dep to temporarily dependencies
Lint so that the deps are ordered alphabetically
Double check that this does not apply to 2.x and if so, remove this from caveman templates

Got it!

Double checked that AF_BLUETOOTH is never mentioned in the python 2.x docs for the sockets family, so I removed the deps from the caveman templates


singleton script update

@EmpireWorld can you check if this is better, then can replace with it?
// current
https://github.com/UnityCommunity/UnityLibrary/blob/master/Assets/Scripts/Utilities/Singleton.cs
// better?
https://gist.github.com/lordlycastle/64821426eedf222e66218f70e2498757

It is almost better @unitycoder, maybe we just needs to add the missing features from that singleton, instead of replacing it fully.

Bump!!!


Offscreen rendering

It would be useful to be able to render offscreen, thus producing with higher resolution than the physical display.
Suggested by @leighorf

@leighorf There is now a prototype of this capability in a Git branch named "high-res". We will plan on hardening it to include for the 3.2 release

That is great to know!!
On Fri, Jun 21, 2019 at 2:47 PM clyne<EMAIL_ADDRESS>wrote:

@leighorf https://github.com/leighorf There is now a prototype of this
capability in a Git branch named "high-res". We will plan on hardening it
to include for the 3.2 release
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/VAPOR/issues/1126?email_source=notifications&email_token=ABAVIYGBY5C4OVEXTBIF76DP3UV3LA5CNFSM4GLUMHV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYJNPSI#issuecomment-504551369,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAVIYH33EO2TKNRTBYQMELP3UV3LANCNFSM4GLUMHVQ
.

Curious - is this functionality in the 3.2alpha build that I recently got? If so, how do I access offscreen rendering options?

Hi Leigh,
Yes it is. You can enable it under Navigation -> Viewpoint -> Framebuffer
Settings.
Stas
On Fri, Nov 29, 2019 at 10:42 AM Leigh Orf<EMAIL_ADDRESS>wrote:

Curious - is this functionality in the 3.2alpha build that I recently got?
If so, how do I access offscreen rendering options?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/VAPOR/issues/1126?email_source=notifications&email_token=AAVE5TYSLWXXLXWJ7OBC7HDQWFH6VA5CNFSM4GLUMHV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPK6GA#issuecomment-559853336,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVE5TYFNNJNTJUPTRI7QDLQWFH6VANCNFSM4GLUMHVQ
.


[PDI-20038] - Pentaho <IP_ADDRESS> - Getting java.lang.OutOfMemoryError: Java heap space when running PDI Jobs

Backport of https://github.com/pentaho/pentaho-kettle/pull/9198

Wingman executed successfully for the 10.1 branch (check pentaho-kettle#9201).


README.md Update and Documentation Proposal

Hi Team,
This Pull Request updates the README.md and adds essential Documentation for testing, from which further comments/documentation can be built on.
How to test this PR? (3 steps):
1- Start from scratch, do as it is the first time you use slicer. Follow Installation steps from the README.
2- Try QuickSTART in the README.md.
3- Read Documentation from Documentation Welcome Page.
Question to ask yourself (examples):
A. Was the installation process without obstruction and difficulties (Slicer and SlicerCART)?
B. Was I able to load images from my dataset? Once loaded, was I able to do manual segmentation as written in the QuickStart?
C. Any feedback/comments regarding the organization set-up of the documentation? When you read those instructions, are they easy for you to understand?
Important Note.
This PR is a pre-beta-release version of SlicerCART. That means the actual main script is really NOT READY for deployment. Only one basic scenario is intended to be tested for now (viewing images and annotate them). Essential functionalities remain to be implemented (bugs fixing e.g. changing labels, load previous segmentations, compare segments, go automatically to the next case, etc.). Accordingly, you should approach this PR as a Documentation PR as mentioned above: are the steps for begin using SlicerCART clear? (Your feedback will be wanted in future PR related to specific functionalities)
This PR addresses issue https://github.com/neuropoly/slicer-manual-annotation/issues/62.
Thank you for your consideration.
Maxime

Ok! Thanks for the input. If you copy paste this command in the slicer python console, and then try to use the module, what does it says? (success or error in python console)
import slicer
from slicer.util import qt

import slicer
from slicer.util import qtTraceback (most recent call last):
  File "<string>", line 2, in <module>
ImportError: cannot import name 'qt' from 'slicer.util' (/Applications/Slicer.app/Contents/bin/Python/slicer/util.py)

yes Qt needs to be installed, this is in the troubleshooting section, it should be in the requirements no?

Ok! Thanks for the input. If you copy paste this command in the slicer python console, and then try to use the module, what does it says? (success or error in python console)
import slicer
from slicer.util import qt

import slicer
from slicer.util import qtTraceback (most recent call last):
  File "<string>", line 2, in <module>
ImportError: cannot import name 'qt' from 'slicer.util' (/Applications/Slicer.app/Contents/bin/Python/slicer/util.py)

yes Qt needs to be installed, this is in the troubleshooting section, it should be in the requirements no?

Yes I will add it. First I think it might be relevant to test with your case until it work, so we can see if there are also other packages that might provide troubleshooting: what do you think?
Can you try:
import slicer
slicer.util.pip_install('qt')

Does this provide an error?

2- Can you open the python console and screenshot the line where there is the error? (there should have some errors when a slicer module cannot be instantiated).

same thing again, here is the error in the python console:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Applications/Slicer.app/Contents/lib/Python/lib/python3.9/imp.py", line 169, in load_source
    module = _exec(spec, sys.modules[name])
  File "<frozen importlib._bootstrap>", line 613, in _exec
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/Users/sandrinebedard/code/slicer-manual-annotation/SlicerCART/src/SlicerCART.py", line 10, in <module>
    from utils import * # Import all modules, packages and global variables
  File "/Users/sandrinebedard/code/slicer-manual-annotation/SlicerCART/src/utils/__init__.py", line 1, in <module>
    from .global_variables import *
  File "/Users/sandrinebedard/code/slicer-manual-annotation/SlicerCART/src/utils/global_variables.py", line 3, in <module>
    from utils.requirements import *
  File "/Users/sandrinebedard/code/slicer-manual-annotation/SlicerCART/src/utils/requirements.py", line 27, in <module>
    check_and_install_python_packages()
  File "/Users/sandrinebedard/code/slicer-manual-annotation/SlicerCART/src/utils/install_python_packages.py", line 31, in check_and_install_python_packages
    response = qt.QMessageBox.question(slicer.util.mainWindow(),
NameError: name 'qt' is not defined
[Qt] loadSourceAsModule - Failed to load file "/Users/sandrinebedard/code/slicer-manual-annotation/SlicerCART/src/SlicerCART.py"  as module "SlicerCART" !
[Qt] Fail to instantiate module  "SlicerCART"
[Qt] The following modules failed to be instantiated:
[Qt]    SlicerCART
[Qt] Populating font family aliases took 138 ms. Replace uses of missing font family ".AppleSystemUIFont" with one that exists to avoid this cost.

added in the code. see comments that you are tagged (I don't know how to refer from here to the code).

Can you try:
import slicer
slicer.util.pip_install('qt')

or using the expresion 'Qt' with capital letters? (also for from slicer.util import Qt)
Does this provide an error?

does not work, even with Qt

Ok. Will look further in the following days. If ever you know find out how to install Qt , please comment it so I can add it in the procedural steps. Thanks for your insight.

@maxradx a lot of suggested commits are a month-old. Can you please accept them so we can make additional commit suggestions?


Hyperparameters

Hi, can you specify what is meant by: "In this case the expected number of GPUs is four, you may need to adjust learning_rate and/or gradient-accumulation-steps accordingly." I would like to replicate the training conditions you used as closely as possible, so I will use 4 GPUs and wanted to check what the right lr and gradient accumulation values should be.

Hi, with four GPUs, use the default hyperparameters.

Ah okay, I think I misread the sentence cited above. Thanks!


grass tiles bug

a bug appears  when drawing trees with the first brush (a green square inside the tiles)

Should not happen anymore now. Toolbar will have a visual bug (will visually select something it should not select), but it is not actually selected. Might be a bug from the EFL.

Thanks !  ^-^


Amazing

Hi, Friend, I am a new leaner in game programming, I am interested in game engine. I need a Guru to assist me in mastering all the skills.

Hi Friend,
While I admire your enthusiasm, my time is extremely limited, I am afraid that you have to walk the path of mastery on your own. Good luck!


Question..

When evaluating performance such as TP, TF, etc., do you evaluate performance by pixel difference between predict_label and correct label?
Is there a source code that evaluates performance among the source codes?

initialize network with normal
cuda:0
================ (Tue Apr 23 17:40:35 2024) ================
gpu_ids: [0] project_name: ChangeFormer checkpoint_root: checkpoints vis_root: vis num_workers: 2 dataset: CDDataset data_name: LEVIR batch_size: 16 split: train split_val: val img_size: 256 shuffle_AB: False n_class: 2 embed_dim: 64 pretrain: None multi_scale_train: False multi_scale_infer: False multi_pred_weights: [0.5, 0.5, 0.5, 0.8, 1.0] net_G: base_transformer_pos_s4_dd8 loss: ce optimizer: sgd lr: 0.01 max_epochs: 1000 lr_policy: linear lr_decay_iters: 100 checkpoint_dir: checkpoints/ChangeFormer vis_dir: vis/ChangeFormer
training from scratch...
lr: 0.0100000
0%|                                                   | 0/445 [00:00<?, ?it/s]Segmentation fault (core dumped)
Why do these errors occur?


meshoptimizer: State used version explicitly

Given that meshoptimizer uses a stable release (v0.20) of https://github.com/zeux/meshoptimizer, I think it's better to have it written explicitly in the README.md file as opposed to the ambiguous "git".

Thanks!


Text Of SnackBars

Hi
Text of SnackBars dont change while font of snackBar Button changes

Got some code to reproduce?


Lockfile changes on the second run

The lockfile can change on the second uv lock, collapsing previously forking dependencies into a single one. I believe this due to how preferences are handled.
Minimal example:
[project]
name = "transformers"
version = "4.39.0.dev0"
requires-python = ">=3.9.0"
dependencies = [
  "datasets",
  "librosa",
  "onnxruntime",
]

$ rm -f uv.lock && cargo run -q lock --preview && wc -l uv.lock && cargo run -q lock --preview && wc -l uv.lock && cargo run -q lock --preview && wc -l uv.lock
Resolved 60 packages in 169ms
1462 uv.lock
Resolved 58 packages in 33ms
1375 uv.lock
Resolved 58 packages in 28ms
1375 uv.lock

We have 3 different forkings until it converges:
$ rm -f uv.lock && cargo run -q lock --preview -v 2>&1 | rg -i split
DEBUG Adding split to cover possibly incomplete markers: python_version >= '3.11' and python_version != '3.11' and python_version < '3.12'
DEBUG Splitting resolution on pandas==2.2.2 over numpy
DEBUG Pre-fork split universal took 0.007s
DEBUG Solving split python_version >= '3.12' (requires-python: python_version >= '3.9' and python_full_version >= '3.9.0')
DEBUG Split (python_version >= '3.12') resolution took 0.003s
DEBUG Solving split python_version == '3.11' (requires-python: python_version >= '3.9' and python_full_version >= '3.9.0')
DEBUG Split (python_version == '3.11') resolution took 0.001s
DEBUG Solving split python_version < '3.11' (requires-python: python_version >= '3.9' and python_full_version >= '3.9.0')
DEBUG Split (python_version < '3.11') resolution took 0.001s
DEBUG Solving split python_version < '3.12' and python_version >= '3.11' and (python_version < '3.11' or python_version > '3.11') (requires-python: python_version >= '3.9' and python_full_version >= '3.9.0')
DEBUG Split (python_version < '3.12' and python_version >= '3.11' and (python_version < '3.11' or python_version > '3.11')) resolution took 0.002s
$ cargo run -q lock --preview -v 2>&1 | rg -i split
DEBUG Adding split to cover possibly incomplete markers: python_version > '3.11' and python_version < '3.12'
DEBUG Splitting resolution on pandas==2.2.2 over numpy
DEBUG Pre-fork split universal took 0.001s
DEBUG Solving split python_version >= '3.12' (requires-python: python_version >= '3.9' and python_full_version >= '3.9.0')
DEBUG Split (python_version >= '3.12') resolution took 0.001s
DEBUG Solving split python_version <= '3.11' (requires-python: python_version >= '3.9' and python_full_version >= '3.9.0')
DEBUG Split (python_version <= '3.11') resolution took 0.001s
DEBUG Solving split python_version < '3.12' and python_version > '3.11' (requires-python: python_version >= '3.9' and python_full_version >= '3.9.0')
DEBUG Split (python_version < '3.12' and python_version > '3.11') resolution took 0.001s
$ cargo run -q lock --preview -v 2>&1 | rg -i split
DEBUG Split universal resolution took 0.002s
$ cargo run -q lock --preview -v 2>&1 | rg -i split
DEBUG Split universal resolution took 0.002s

I think we need #4926 (to not create duplicate dependencies in the first run) and we need to marker- or fork-tag preferences if that heuristic fails.

A detailed write-up on the problem can be found in https://github.com/astral-sh/packse/pull/203.
My plan to solve this is to:

[ ] Merge forks with identical resolutions so we have as few forks as possible in the end
[ ] Solve https://github.com/astral-sh/uv/issues/4926 as a follow-up so we have diverging forks less often
[ ] When we still have diverging versions, preserve the fork markers from the resolution and for packages with diverging versions in the lockfile
[ ] When resolving from an existing lockfile, start already forked into the forks from the lockfile
[ ] Change the preferences so that we only use those applicable to the current fork. When we use the preserved forks, this will be a 1-to-1 mapping, what we do otherwise TBD
[ ] Add https://github.com/astral-sh/packse/pull/203 to the test suite

Background reading: https://github.com/astral-sh/packse/pull/203
The root problem is that preferences can influence which fork points we get and thereby which forks we have in the eventual merge resolution.
In the worst case we could have a bistable system that flip-flops for every uv lock invocation: We start with preference I for lockfile I. These contain foo==1, and starting with foo==! causes us to fork on python_version. The two python_version forks both end up rejecting foo==1 and we write lockfile II with foo==2. In the next uv lock invocation, we read preferences II from lockfile II with foo==2. Starting with foo==2 causes us to fork on sys_platform instead. With those forks, we end up rejecting foo==2 and write lockfile I with foo==1 instead; we're back in the other state, switching on every uv lock.
The solution is to lock store the forks in the lockfile and to start the resolution with the locked forks. For simplicity and to make it easier to understand for users why there are multiple versions per package in their lockfile, for each package with multiple versions, we write write the forks a version belongs to next to the fork. When we resolve, in each fork, we will find exactly one matching preference, the one that is the result in the fork in the previous resolution. This way, we get a stable resolution.


Releasing owned resources on Generator drop

I notice that there's no Drop implementation for Generator, and so it looks like it's owned stack won't get unwound, and so any resources owned by a Generator's stack will get leaked.
So, it seems that that the only way currently to forcefully unwind a generator's stack is to pass in a value that asks it to panic, such as in this example. Is that right?
I notice that context-rs has the ability to spawn a function on top of a recovered stack, which might be an option for future implementation. But that seems quite risky.

See #52


how to stop the timer?

Hello,
when I call reset method to stop the timer, it resets the timer value back to initial set value and restarts counting down.
How can I stop the timer and set the timer back to 0:00:00?
I am using Xcode 7 and ios9.
thanks!

This is also true for Xcode 6 and iOS8.4... how can I stop the countdown timer? Many thanks!

Nevermind... I found another solution. :-)


Progress component: let the user disable the animation

Feature request type
Enhance component
Component name
MudProgressLinea
Is your feature request related to a problem?
The MudProgressLinear component could used as time bar for a custom video player as well, however as of now such component has an animation which makes it quite unsuitable for being used like that. Custom video players are useful in many occasions, like when you need to show a video that "under the hood" is actually composed by multiple videos
Describe the solution you'd like
There should be the possibility of disabling the MudProgressLinear component animation. That way it would feel more like a video player time bar.
Have you seen this feature anywhere else?
It can be seen of whathever video player, e.g. here
Describe alternatives you've considered
No response
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

Hi @xfxJeroen. No, actually 'indeterminate' specifies whether an indicator (a progress bar) should be indeterminate or not. From the doc:

Indeterminate indicators express an unspecified amount of wait time. They should be used when progress isn't estimable, or when it's not necessary to indicate how long an activity will take.

(please see Progress component documentation, section Linear Progress, Determinate vs Indeterminate)

But MudProgressLinear does not animate by default. https://try.mudblazor.com/snippet/GucGFGbXVuRqjyZI

Hi @BieleckiLtd,
I've modified your example in order to show you the animation I'm talking about.

https://try.mudblazor.com/snippet/GucGFGbXVuRqjyZI

As you can see, each time you change the Progress value, there is an animation that causes the progress bar status change not to be instantaneous.
As I was mentioning in the initial post, I'm aware that a Progress component is meant to be animated by a process that is doing some work, but giving the possibility to remove the animation would give the opportunity to use the Progress component for many other tasks as well.

Yes, ok I see what you mean. Components should allow to disable animations for accessibility reasons. If this is not possible you can make workaround by overriding default style like so (just add this at the top of your example):
<style>
    .mud-progress-linear .mud-progress-linear-bar { transition: none; }
</style>

Also, you might want to consider MudSlider. You would be able to move video progress by dragging the dot, and it has no animations baked in:
<MudSlider @bind-Value="@_myValue" Class="mt-12" />

Thank you very much!

<style>
    .mud-progress-linear .mud-progress-linear-bar { transition: none; }
</style>

this is what I was looking for

Also, you might want to consider MudSlider. You would be able to move video progress by dragging the dot, and it has no animations baked in:

but this is even better. I was not aware of the existence of the MudSlider component. Actually, there is no Slider menu item in the MudBlazor docs Components menu (while there is in the API menu).
Thank you again

Glad to help. You can find MudSlider in the docs in the Form & Inputs sub menu :)

You can find MudSlider in the docs in the Form & Inputs sub menu :)

Right you are, thank you again!


minDate do not affect time options

Hi all,
When minDate is set, only days before that date are disabled. The time picker are all available no matter what hour the Date object is.
For exemple:
This date (Fri Sep 04 2020 16:00:00 GMT+0200) makes the datapicker show like:

As you can see, all hours before 16:00 are enabled when is expected to be disabled for this day.
I'm not sure if it is the expected behaviour of there is another way to do this.
Greetings,

minDate only filters the date section of the picker, as far as I know; it ignores the time portion of that value. You'll want to enter minTime to filter the time list.
Also if I recall correctly, the value you pass to minTime needs to be that time on today's date, regardless of which date is selected in the calendar. So in your case, right now you would set minTime to Tue Sep 8 2020 16:00:00.


Pretty print output of .Html()

Currently, there aren't any good pretty printers for html written in go. It would be nice if goquery could have the option of pretty printing the html.

Hello Patrick,
I agree that an HTML pretty-printer would be nice (I don't know of any either), but I don't think this belongs in goquery. Something that would work directly with a golang.org/x/net/html node would be better, and it would be trivial to call it from a goquery Selection.
Martin

I partly agree with your point, but the thing is that goquery seems to unpretty the code, and make it really unreadable.
Also, not much of an issue, but goquery mangles the  tag, and turns it into a comment (but I just fix this manually).
BTW, I am using this library in https://github.com/geek1011/kepubify

Some unprettifying I have come across so far:

Puts <!DOCTYPE html> in one line
Puts  in one line
Adds random newlines everywhere
Puts contents of p tag in one line, even when it contains child elements
pre tags causes indentation to be really unusual from there on
Some other things I cannot remember off the top of my head

What you're describing is the behaviour of Go's net/html parser used by goquery, not goquery itself:
var data = `
<!doctype html>

			Text

`

func main() {
	n, err := html.Parse(strings.NewReader(data))
	if err != nil {
		log.Fatal(err)
	}

	if err := html.Render(os.Stdout, n); err != nil {
		log.Fatal(err)
	}
}

// Output:
<!DOCTYPE html>

			Text

Note that it doesn't change the semantics of the document. I understand wanting a pretty-printer for humans (or to compare docs against some canonical format, but then an html minifier is probably better), but for code this shouldn't matter, this is an equivalent html document.

Your tool seems pretty cool btw!

@mna Thanks!
I do care sometimes though, such as when I make one-off tools in go to do some transformations on my html.

Closing this issue, since as I said it doesn't belong in goquery, but it would be nice to have one in Go for sure. I may hack on one in the next few weeks if I have some free time (no promises!) as this is a fun project for sure.

@mna OK, I'll work on one too if I have time ;)

I came here looking for this too.
I noted that https://github.com/ericchiang/pup did almost what I wanted (it actually did far too much), but didn't support anything other than CLI usage, so I forked it, chopped it down and refactored a little to https://github.com/a-h/htmlformat
It uses net/html to parse (document fragments by default), and prints the results.


Adding missing file.

Hi Avi,
Thanks for the steps. I am ready to create a pull request with just 1 file change.
Regarding binary: Docker file does not work without the jar file.
Entire Oracle WebCenter Sites installation and configuration is done by the groovy scripts packaged inside the jar.
We have obtained all the required approvals for publishing binaries to GitHub.
We are also providing all the groovy scripts in human readable format.
Since it's an open source, these scripts can be modified by clients as per their need and recompile the jar and use it.
Instructions: https://github.com/oracle/docker-images/tree/master/OracleWebCenterSites/dockerfiles/<IP_ADDRESS>/wcs-wls-docker-install
Send you all the approval emails including approvals for binaries to your email separately.
Please let me know if any additional information required.
Thanks,
Ashish

This repository is designed specifically not to include any binary files, regardless of approvals. I still have to reject this pull request. Even if I were to merge in this pull request, users would not see the jar file as git will ignore it as per the .gitignore file in the root of the repository.
You will need to modify your Dockerfile to build the jar file as part of the build process of the image itself.


Paypal payment check out

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
@TohaAbir/PayPal. Me

@TohaAbir Please provide more information on the feature you are requesting.


include additional optional parameters in Add post request

I like the simplicity of django-easycart, but there is one feature I am not sure how to accomplish.
Using the jquery POST add request, I would like to push additional optional options, in addition to the quantity param such as size or color, how would I accomplish that?

Take a look at:
http://django-easycart.readthedocs.io/en/latest/cookbook.html#associating-arbitrary-data-with-cart-items

Yes, I can pass additional arguments on the backend using the add method, however, I can only pass the pk, and quantity arguments with the add POST request. I can't include any additional parameters. Looking at the source code on line 117 of
https://github.com/nevimov/django-easycart/blob/master/easycart/views.py
I see that the quantity param is the only optional parameter I can pass after the POST AJAX request, every other additional parameter is filtered out.

Yep, looks like you're right. I'll fix the problem within a week.

I've added a quick fix for the problem. See branch 'allow-passing-arbitrary-data'.
However, I've realized that the project needs some serious refactoring. The thing is, I don't use the app anymore and have no time/desire to work on it further. So, I recommend to use another app. I'll put a notice on the main page later.

@mozilla-rowvigor can you ping me if you keep development? We are using it in soon-to-be production

Sure.


WIP: new feature multiprocessing

CAUTION this is experimental, although working so far.
Please feel free to try it out!
Description
This adds a command line argument:
  -M MULTIPROCESSING, --multiprocessing MULTIPROCESSING
                        Use multi-processing to run the checks. The argument is the
                        number of worker processes. Use -1 to specify the number returned
                        by os.cpu_count()( = 8).
To Do

[ ] better code organization?
[ ] I'm not very happy how STARTSECTION/ENDSECTION are handled, but the solution may be to replace these statuses by something else (SECTIONSUMMARY?). However, this could break stuff external to this project, we don't know.
[ ] There's some room to implement this more elegantly, but would e.g. involve touching CheckRunner or try to avoid pickling the module etc. I'll have a look myself after a few days.
[ ] update CHANGELOG.md
[ ] wait for checks to pass (except github/pages, which is stuck)
[ ] request a review

Whatever the fonts on my ~/Desktop are, it's not very comparable and since bigger jobs make a bigger difference, here's another timed run. I have 8 sub-processes when I run with -1 on this machine:
$ time fontbakery check-googlefonts -M -1 path/to/google/fonts/ofl/montserrat/*.ttf
real	1m8.232s
user	4m53.444s
sys	0m10.525s

$ time fontbakery check-googlefonts -M 0 path/to/google/fonts/ofl/montserrat/*.ttf
real	5m9.258s
user	2m14.299s
sys	0m31.257s

~ 4m1s faster or  a ~ 4.5 times speedup


Revoke unnecessary exec permission for text files

755 -> 644

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fix eraseLines

Current eraseLines function does not work with specified line count. This PR fixes this.

thanks


Make "api-port" a cluster Host property.

It was wrongfully considered a VirtualBridge property but it fits better as a per-host one.  This also allows cleaning up the api port detection.
Moreover, the per-bridge config was not correct in case auto-detection was used.

LGTM I think it makes more sense to have this be a property of a cluster host.
Tested this patch w/ #143 and this is working for our use case: https://net-hw-ci-jenkins-csb-nst.apps.ocp-c1.prod.psi.redhat.com/view/Custom OVNK8 Testing (NIC Mode)/job/99_Lab227_NIC_Mode/585/console


Tree structure: show all organizations in the tree where someone has access to

@robvanmieghem does this relate to the view on the user page, or the structure on the organization detail page?

Either this is related to the user page, in which case its fixed, or it is related to the org page, which is more accurately tracked by #474


(Partially) generate Rust type & function declarations from TypeScript type definiton file

Of course this does not work for some types..
This might belong in another repo.

Nah definitely! I could totally see something like
wasm_bindgen_typescript!("foo.d.ts");

being used

I thought of it as a separate nodejs tool since the Typescript parser is a node module. I could attempt writing a provisional script, but I know nothing about macros... yet.

TypeScript also has modules and interfaces, which could be directly translated to Rust modules and traits with ease, so support for these would be great.

Yeah I'm not sure what the best way to do this would be. I'd naively prefer to start off with a syn-based parser (just in the procedural macro itself) rather than picking up a dependendy through node, but I'm not sure how easily that'll work.
Alternatively there could be a JS tool which takes a foo.d.ts and emits a foo.rs with #[wasm_bindgen] anntoations maybe

This is similar to https://github.com/alexcrichton/wasm-bindgen/issues/42 as well

Experimental support for this is now in the repository and future work is tracked with a label, so I'm gonna close this for now


[Session] Compat -> Root

Prep for a potential rollout approach to landing this code

Actually I'm going to merge this and then split out the previous root PR 👍


Atlas Backfill

Meeting with Micah / Sasha today, and we have Leonard pairing with Roger

Lenny currently onboarding, James pairing with Josh this week


Fix erroneous array count in parallel gufunc kernel generation.

As title.

Observation: The code path for ufunc and gufunc both run through the code changed in the diff, I think the +1 to the array count is only needed in the case of a ufunc. Next thing to try is branching on types.none return type to skip adding the 1.

xref reproducer: https://github.com/numba/numba/pull/8032#issuecomment-1131991661
xref debug: https://github.com/numba/numba/pull/8032#issuecomment-1132662142


Add note about restarting OMERO.web

In response to QA 17257 where a user commented that it doesn't say you need to restart OMERO.web on the customization page.
Staged at https://www.openmicroscopy.org/site/support/omero5.3-staging/sysadmins/unix/install-web.html#customizing-your-omero-web-installation and https://www.openmicroscopy.org/site/support/omero5.3-staging/sysadmins/customization.html

Rebuilding staging now

As a start, :+1:. I do wonder if we're getting lost in "Note:" boxes though especially on customization.html. (3 boxes with more vertical space than the introductory text). It might be that we need an intro to customization that shows the general steps, but that may be part of a larger restructuring. (At which point the install-web.html "Customizing" section could be folded under?)

General tidy up on staging now, have cut down the note boxes on customization page and rejigged the section at the bottom of the web deployment page too.

:+1: from me. Still think there's room for us to handle more rejigging, but I think that's beyond the scope of this PR.

Agreed.
Once we are clear on our recommendations for deploying OMERO.web for 5.3, these sections could probably do with an overhaul similar to the installation docs - I'll add it to a card.

--rebased-to #1505


Make aec_chain_state use database rather than a functional state

Blocks and headers are stored unless they are blatantly malformed.
Blocks are stored in db as headers + transactions
Previous hash is indexed in db
The top block hash is driving top header hash rather than the opposite
Avoid giving error messages for other nodes than the one currently added
Add stricter checking before adding state to db
If a node has a stored state in the db, it needs no more checking
Better restart from persisted states

https://www.pivotaltracker.com/n/projects/2124891/stories/153442321
https://www.pivotaltracker.com/n/projects/2124891/stories/154877787

@lucafavatella
Currently, the index is not persisted by default, but mnesia rebuilds the index on start. This will eventually increase the startup time, but not not increase the disk usage.
I expect the increased disk/memory for the index to be much smaller than the copy of all blocks/headers that was the previous behavior, so I expect this to be significantly smaller in RAM for disk db, and "a bit" smaller for non-persisted db.
We should probably observe the RAM behavior in UAT nodes, and we can update the recommendations to the next release.


datetime.timetuple returns a tuple, not a time.timetuple

Unlike the built-in datetime, cftime.datetime.timetuple() returns a tuple and not a time.timetuple. I'll submit a PR to correct this.

@mcgibbon - have you had any time to work on this?

@jswhit The PR was completed and merged, so this issue is resolved.


Reverse rope to navigate backwards from specific position

Hello,
I would like to navigate some file contents backwards from a specific position and want to therefore use splitAtPosition and then reverse the first part of the return value, is there an efficient way to do this using Ropes and without having to convert back to Text?
What I was using previously in Text was: reverse $ take lineposition bigFileContents.

Great, thank you for the quick response!


Misconfiguration for typescript projects using module node16/nodenext

Hi.
I'm currently working on ESM repo with tsconfig moduleResolution set to node16, and this library has misconfigured type definition that confusing typescript when we try to import default export from the module.
In current configuration, the library's seems to have so-called double-default problem described in typescript repo.
Reproduce
In a project with
package.json "type": "module"
tsconfig.json  "moduleResolution": "node16"
While trying to import default export from weaviate-ts-client, typescript's expectation and actual runtime value mismatches
import weaviate from 'weaviate-ts-client';
console.log(weaviate.client); // ts error; Property 'client' does not exist on type

// Typescript expect it to be
// {
//   default: {
//     client: (params: ConnectionParams) => WeaviateClient;
//     ApiKey: typeof ApiKey;
//     AuthUserPasswordCredentials: typeof AuthUserPasswordCredentials;
//     AuthAccessTokenCredentials: typeof AuthAccessTokenCredentials;
//     AuthClientCredentials: typeof AuthClientCredentials;
//     EmbeddedOptions: typeof EmbeddedOptions;
//   };
// }

// But it's actual value in runtime is
// {
//   client: (params: ConnectionParams) => WeaviateClient;
//   ApiKey: typeof ApiKey;
//   AuthUserPasswordCredentials: typeof AuthUserPasswordCredentials;
//   AuthAccessTokenCredentials: typeof AuthAccessTokenCredentials;
//   AuthClientCredentials: typeof AuthClientCredentials;
//   EmbeddedOptions: typeof EmbeddedOptions;
// };

You can see arethetypeswrong also indicates the repo is misconfigured in the exact way as I described above.
It seems like node16's module resolution strategy and typescript's following implementations making a lot of trouble in ecosystem and making quite a bit of confusions all over the place, as you can see from
https://github.com/microsoft/TypeScript/issues/50058
https://github.com/microsoft/TypeScript/issues/49160
https://github.com/vitejs/vite-plugin-react/issues/104
I'm afraid that I can't really tell what's the workaround for this as it's really confusing for me that what's the problem at the first place..
I might be wrong here, so feel free to point me out.
It'd be much appreciated if someone can analyze the details regarding to the problem.

Still not fixed. Alternatively, go back to "moduleResolution": "node"

Can you just make a named export for client function? Because that's the only thing we can't get without using the default export.
 })

@MellKam thanks, that is working!


New version of magicmirror does not work in docker

Hello,
I am getting this issue when I am trying to launch the latest version of docker:
[22.07.2021 12:16.03.454] [LOG]   Starting MagicMirror: v2.16.0
[22.07.2021 12:16.03.462] [LOG]   Loading config ...
[22.07.2021 12:16.03.474] [LOG]   Loading module helpers ...
[22.07.2021 12:16.03.497] [ERROR] WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'request'
Require stack:
- /opt/magic_mirror/modules/MMM-quote-of-the-day/node_helper.js
- /opt/magic_mirror/js/app.js
- /opt/magic_mirror/serveronly/index.js
[22.07.2021 12:16.03.499] [LOG]   Loading module helpers ...
[22.07.2021 12:16.03.504] [ERROR] Whoops! There was an uncaught exception...
[22.07.2021 12:16.03.514] [ERROR] Error: Cannot find module 'request'
Require stack:
- /opt/magic_mirror/modules/MMM-quote-of-the-day/node_helper.js
- /opt/magic_mirror/js/app.js
- /opt/magic_mirror/serveronly/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._resolveFilename (/opt/magic_mirror/node_modules/module-alias/index.js:49:29)
    at Function.Module._load (internal/modules/cjs/loader.js:746:27)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:92:18)
    at Object.<anonymous> (/opt/magic_mirror/modules/MMM-quote-of-the-day/node_helper.js:2:17)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:14) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/opt/magic_mirror/modules/MMM-quote-of-the-day/node_helper.js',
    '/opt/magic_mirror/js/app.js',
    '/opt/magic_mirror/serveronly/index.js'
  ]
}
[22.07.2021 12:16.03.515] [ERROR] MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[22.07.2021 12:16.03.516] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

Can you please advise me what I am doing wrong? v2.15 is working fine.

Hi, The docker implementation is not part of the core repo, so i can't really give any support on this.
It looks like not all required modules are installed in the docket container.

see this content from discord mm support channel
in the docs https://khassel.gitlab.io/magicmirror/configuration/ you find a way how to log in into the running container. The key is docker exec -it mm bash, with this command you are in the container and navigate to the module folder and in the module folder you can install the missing packages with npm install xy

I agree that depreciated software should no longer be used, but there are some truly great Magicmirror modules that have not been maintained for years and still require the "request" module. These mm modules simply stopped working since the lastest release.
I've also tried to install the "request" module as you have suggested, but the problem is that the Docker container or Magicmirror itself restarts after ~15 seconds.  In this short time it is not possible to run the npm install command successfully.
Any ideas?

@theskyisthelimit This is more of an issue with the docker container. I don't think anyone can really help you here. Is it an option to post an issue in de docker container repo?

@theskyisthelimit there is documentation in the docker site that says you have to docker exec into the container and do the npm install in the module folder there

The problem is that you can't exec into the container because the container always restarts because of the request errors.
To solve this you have to do this with a working config. You can disable the modules in your config which are causing the errors or you can use the default config for this.

Thanks @khassel for the suggestion. That's a great idea! I will try it later.
As far as I understad, this is only a termporary solution until a new version of magicmirror is pushed, correct?
I was using your docker image with the tag "latest" for years but now I will have to do this step manually every time a new version is pushed?
Could we have a dedicated tag for "latest release + request npm module"?

Another (maybe simpler) workaround ist to change (temporarily) the command section in the docker-compose.yml from
    command:
      - npm
      - run
      - server

to
    command:
      - sleep
      - infinity

To be clear where to install request: Not in the main folder of mm but in every module folder where it is missing, so e.g. in the first post here it was missing in modules/MMM-quote-of-the-day so you have to cd into this folder an run npm install request there.
If you run it in the main folder it will not survive a container restart.
You have to do this only once (for every module where it is missing) until a new version of a module is released (where its may fixed because this is a problem of the module).

Thank you @khassel
I was able to locate the MM Plugins (MMM-homeassistant-sensors, MMM-cryptocurrency, MMM-Sonos) and ran the npm install request command in each folder. Then I was able to start the container with the latest magic mirror release.
Everything still seems to be working after a restart of the docker container, unfortunately if I do a full recreation of the docker image (with portainer) it's back to it's old failing behaviour. What will happen when a new release of MM is released?

If there are so many modules still depending on the request module, I have no problem adding it back again as a npm dependency. What do you think, @khassel?

the 'problem' here is that the modules didn't have a package.json (mostly) or didn't has request listed in the package JSON at all.
so, installing it in every   needing module will require scanning then all for node_helper and checking their maybe non-existing node_modules for theissing modules ( not just request, bit valid-url, UUID, and a couple others so far,)
on EVERY startup
cause the user could have installed another module
oh  and waiting for author on used and no longer maintaned modules

What do you think, @khassel?

I'm not for adding it back again.
As @sdetweil  already mentioned this happens only if the author of this modules has "forgotten" to put e.g. request into the package.json of his module.
We should try to get rid of old components here and as long as workarounds exist, I think that's okay. I also see this as a reminder for the users of such modules to consider whether they really want to continue using such old and unmaintained modules. When I find the time I will add the problem with instructions on how to fix it in my FAQ.
Of course there have already been some support requests on the subject but the release has been out for 4 weeks and such requests should decrease.
If we would add it back again, it would only take effect with the next release (October 1st), by then we will be through with the topic anyway.

You convinced me. 😂

unfortunately if I do a full recreation of the docker image (with portainer) it's back to it's old failing behaviour.

I don't understand what you are doing here

What will happen when a new release of MM is released?

Nothing, same situation as with current release.

Better solution than changing the docker is to send a PR to the problematic modules to fix the issue and use your own fork in the meantime.

most of the old modules will never be fixed

@MichMich  Its not only a problem with the docker setup, when you install without devDependencies you have the same problem with a classic install.

That's why docker is a "non officially supported" method of installation. 😅
@sdetweil, I know. But if someone really needs a specific module that stopped working, they can always fork the module and make the necessary modifications. That's the beauty of open source. 😁

I hope not!
I do prod only installs to keep the disk space usage down

When I find the time I will add the problem with instructions on how to fix it in my FAQ.

have updated my FAQ

I hope not!

I'm using npm ci --only=prod (or npm install --only=prod when i build from the develop branch) and there is no request installed afterwards.

unfortunately if I do a full recreation of the docker image (with portainer) it's back to it's old failing behaviour.

I don't understand what you are doing here

@khassel The container is being discarded, the latest images is being pulled and it creates a new, fresh docker container. The only thing that stays are the persistent files within the attached volumes.

What will happen when a new release of MM is released?

Nothing, same situation as with current release.

So about 5 hours ago, the version v2.16.0 was pushed and my watchtower pulled the newest docker image and recreated the magicmirror container. Now magicmirror has the same problem because the request module is missing from those 3 mm modules. That's what I meant yesterday.
Is it a possible solution to fork the failing modules and only add that package.json with the request module? Does this do the trick?

@theskyisthelimit yes, forking and adding a package.json and adding the dependency will 'fix' the problem.

Thank you @sdetweil
So I tried and forked the MMM-Sonos Repository and added the file like this: https://github.com/theskyisthelimit/MMM-Sonos/blob/master/package.json
I deleted the old folder without the package.json, did a git clone from my forked repository and an npm install but it didn't work.
Did I miss anything?

I would have done npm init, and then npm install request --save

@theskyisthelimit  so now we come closer why it was not persistent, checked it in my environment.
If such a module e.g. MMM-Sonos comes without a package.json file the workaround with "install request in the module folder" does not work. I found the installed request package after this installation in the node_modules folder of mm and not under the module folder.
In this case you have to execute npm init and then npm install request (both in the module folder).

yes,  without a package.json, npm install will look up the file system to find the next nearest node_modules folder to install and record it in.

@MichMich @sdetweil Thank's guys it worked.
I forked all 3 repositories and created or added the request module to the package.json in each repository.
npm init and npm install request did the trick.

Great to hear. No that you have a fork anyway, it might be worth sending a pull request to the original repos. That way other can benefit from your contribution.

That's a good idea. The package.json looks like this atm
{   "name": "test",   "version": "0.1.0",   "dependencies": {     "request": "*"   } }
Can I leave it like this or do we need some additional informations?

Maybe 3rd-party modules shouldn't be able to access dependencies of MagicMirror at all to avoid this kind of problems in the future?
Or maybe it would be enough to update the module development to actually encourage people to create a package.json

@buxxi many of these modules are many years.old, no longer maintained. the developers ( probably nearly all not professional developers)  didn't know  and it worked just fine.

Of course I know that's the case, just think it's kind of bad design to depend on an internal dependency which could probably be solved by a stricter api for how modules are implemented.
Breaking 3rd-party modules will always be a part of releasing new versions, if it's not a dependency it will be a tag in the html changing name, having another css-class or accessing a "private" field in MagicMirror. Being clear with what you should do and not do could at least make the "professional" developers not make this mistake in their modules (I started my own modules without package.json, so maybe one of my own could have this problem).
I know too little about the whole npm ecosystem, just thought maybe it was possible to sandbox each node_helper to only have access to its own node_modules. If not denying it, maybe a warn log would be enough if that's possible?

Here the node documentation: https://nodejs.org/api/modules.html#modules_loading_from_node_modules_folders

Yeah, doesn't seem to be anything there.
Being a professional Java-dev I thought maybe something like a custom class loader would be possible in other languages too (like application servers isolate each app).

Fixed the issue in the Sonos module.


Cache directory for HTMLPurifier is not writable

When navigating locally to

http://modules.zendframework.dev/neoglez/BatchManager

the following error is triggered

( ! ) Warning: Directory /Users/am/Sites/zendframework/modules.zendframework.com/vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer not writable, please chmod to 777 in /Users/am/Sites/zendframework/modules.zendframework.com/vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer.php on line 272

@ins0
Do you want to take a look at this since you introduced the view helper?  I think it needs proper configuration, maybe something in data/cache/html-purifier/ or so, otherwise it will fall back to its own default. Had this issue myself before in a different project.

i will

Permissions error fixing now
On 23 Jan 2015 19:22, "Marco Rieger"<EMAIL_ADDRESS>wrote:

i will
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/modules.zendframework.com/issues/315#issuecomment-71238617
.

I was wrong, I missed the development.
On 23 January 2015 at 19:22:01, Marco Rieger<EMAIL_ADDRESS>wrote:
i will
—
Reply to this email directly or view it on GitHub.

pr will show up in a few minutes

Awesome, great job @ins0!


chore(main): release base 0.0.30

:robot: I have created a release beep boop
0.0.30 (2024-10-21)
Bug Fixes

🐛 Variety of adjustments (#158) (abab3c6)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

base-v0.0.30
:sunflower:


mkdocs: update urls

https://github.com/functime-org/functime/blob/de448b7b8dabb370f189245c0cd3c429392f5792/mkdocs.yml#L1-L4

This was actually addressed by @FBruzzesi in #172


Add missing property 'id' in ICounterfactualData

Description
It seems SDK is adding this property but UI doesn't have this listed in ICounterfactualData.

Checklist

[x] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #1834 (b6c3a1b) into main (c1bcfdc) will decrease coverage by 2.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1834      +/-   ##
==========================================
- Coverage   75.94%   73.82%   -2.12%
==========================================
  Files          42       25      -17
  Lines        1671     1276     -395
==========================================
- Hits         1269      942     -327
+ Misses        402      334      -68

Flag
Coverage Δ

unittests
73.82% <ø> (-2.12%)
:arrow_down:

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

Impacted Files
Coverage Δ

raiutils/raiutils/webservice/__init__.py

..._flask/environments/credentialed_vm_environment.py

...i_core_flask/environments/public_vm_environment.py

...ai_core_flask/environments/azure_nb_environment.py

.../raiutils/data_processing/data_processing_utils.py

...core_flask/rai_core_flask/environments/__init__.py

raiutils/raiutils/webservice/webservice.py

..._core_flask/rai_core_flask/environment_detector.py

raiutils/raiutils/data_processing/__init__.py

raiutils/raiutils/dataset/dataset.py

... and 7 more

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


GUI jobs failing due to multiple UI screen changes

In DOP 1.11.0-rc2.ee release multiple GUI jobs are failing due UI screen changes pushed to RC2 build.
We need to  refactor the GUI code with current changes .

Multiple GUI jobs failed because HTML labels or attribute change happens in some pages , because of that selenium code unable to find specific action buttons and input fields .

Cluster test was failing due to cluster name field attribute change
Teaming test case was failing because of Invite button attribute change.
Authentication test was failing due to Change Password button attribute change.
Dmaas tests were failing because introduction of Retention Count feature into screen and some other UI changes in Dmaas page
ref: https://github.com/mayadata-io/gui-automation/pull/40

Stage : Director-Gui-Check
Job : TCID-DIR-TEAMING-USER-INVITE  , TCID-DIR-TEAMING-USER-ROLE-UPDATE-NEGATIVE

Job : TCID-GUI-DASHBOARD

job : TCID-GUI-CLUSTER

Job : TCID-DIR-DMAAS-CSTOR-NON-RESTIC , TCID-DIR-DMAAS-MINIO-DELETE , TCID-DIR-DMAAS-SCHD-CSTOR-AWS-BUCKET , TCID-DIR-DMAAS-SCHD-CSTOR-MINIO-BUCKET , TCID-DIR-DMAAS-SCHD-JIVA-AWS-BUCKET , TCID-DIR-DMAAS-SCHD-JIVA-MINIO-BUCKET , TCID-DIR-DMAAS-SCHD-JIVA-MYSQL-BUCKET , TCID-DIR-DMAAS-SCHD-LOCAL-HP-AWS-BUCKET , TCID-DIR-DMAAS-SCHD-LOCAL-HP-MINIO-BUCKET
Dmaas Jobs run as synchronous manner ,
- Some of the jobs got failed because of new input text box ( Retention count ) added in before clicking `schedule now` button .
- For Minio cloudprovider url field missing .


X11: Send IME update notification deferred

Fixes #82338
Fixes #82608
I suggest only merging this once the ibus issue is resolved. The error message is not directly linked to the problem with accented characters not inserting, but it will help users who encounter the problem to find the related issue on Github.

Isn't this PR meant to workaround the ibus issue?

No, it doesn't fix the IBus issue. It fixes the fact that the event is coming from a state where it's not thread-safe for nodes.

I'm still confused, it claims to fix the issues which were pinpointed as caused by the ibus regression.

Well, it fixes the ERROR: Caller thread can't call this function in this node (/root). Use call_deferred() or call_thread_group() instead. part.

If I understand correctly, this will fix crash with IBus, but not missing dead keys (which is IBus bug).

Cherry-picked for 4.2.1.


Abbreviate

As a developer
I want to be able use a Abbreviate component
so that I can easily add an abbreviate
The component should contain:

[x] embedded className called dcx-abbreviate
[x] relevant classes for shared / reusable styling
[x] the ability to specify the value of the label
[x]  the ability to specify other props (...props)

Abbreviate behind the scenes is a abbr tag:
WHO

The final user will use in this way:
<Abbreviate title="World Health Organization">WHO</Abbreviate>

and the outcome will be something like this:
WHO

Tasks:

[x] Add unit tests
[x] Add Application code with commented props
[x] Add the ability to specify other props (...props)
[x] Add Demo use of component
[x] Add to storybook documentation file with examples (.mdx)  in a section called Typography
[x] Add to live demo

Please follow the below to create your branch
git checkout release/0.8
git pull
git checkout -b 'feature/abbreviate'

closed by https://github.com/Capgemini/dcx-react-library/pull/512


Fix dependency management

Delay calling service to reload dependencies until changes are saved.

@Rikkola @manstis same fix as we sent to 6.4.x branch, please have a look.

+1 to merge.


[master] Automated Bump DC/OS UI v2.150.2

High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (required)
DCOS-59786
Related tickets (optional)

DCOS-59786
Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

Please update CHANGES.md file (Add or update DC/OS UI line in Notable Changes section of newest version).
* Updated DC/OS UI to [master+v2.150.2](https://github.com/dcos/dcos-ui/releases/tag/master+v2.150.2).

You can edit CHANGES.md directly here: https://github.com/mesosphere/dcos/edit/dcos-ui/bump/2019-10-16-08-05-46/master+v2.150.2/CHANGES.md?pr=%2Fdcos%2Fdcos%2Fpull%2F6418

@mesosphere-mergebot label [Ready for Review]


Installation with npm includes older code

After executing npm install pluralize --save, pluralize('passerby') outputs "passerbies".
Your GitHub repo actually already accounts for this irregular rule (passerby should be passersby). I see the rule on line 321 in pluralize.js. But my local version is missing ['passerby', 'passersby'] in the array.
Any way the updated version can be published to npm?

Published as 8.0.


testing access to session doesn't work with custom sessionengine

I have to do t.SessionEngine = InitRedisSessionEngine() in Before()

@ptman can you give me some more context? What should you be able to do?
@notzippy since you developed the session engine, do you have any insight?

I wrote a custom session engine. Sessions weren't working in tests. https://github.com/revel/revel/blob/a3d7a7c23ca885cc5036d3641ede49ce4a14ee2e/testing/testsuite.go#L49 always sets the default session engine, instead of the one configured.


Tween.RotateGameObject needs a bit of work

Hi.
Thanks for the awesome job you've done with your Unity DOTS Tween library.
There are a few issues I've spotted there.  The RotateGameObject method needs a system to push the rotation lerp back into the game object transform.  You can probably add that as part of TweenTransformSystem.
We also need a method to allow tweening the local position and local rotation of game objects.
I am working on that at the moment, if you want I can send a pull request after I'm done.

Hey, aeldron.
I apologize for the long answer, at the moment I do not have enough time to work on the project, so you can send your pull request.


[DO NOT MERGE] Used to debug CD-CI, IT tests

[DO NOT MERGE] Used to debug CD-CI, IT tests

Done debugging!

(Restoring branch temporarily for running CI again)


(foreman role) add foreman discovery plugin

Related to https://github.com/lsst-it/foreman_templates/pull/2

I'm going to change this PR back to draft status to look at BMC management.  When discovery creates a host, it is add a BMC type interface to the host, which is sort of strange as BMC support is disabled.

I have enabled foreman's bmc support (and manually tested it as working with one of the new k8s nodes) and de-duplicated some of the tests.


Brooklyn.initializers example with sensor from windows command

org.apache.brooklyn.core.sensor.windows.WinRmCommandSensor is already listed in brooklyn-docs/guide/yaml/yaml-reference.md but it could be nice to have it here as well.

@drigodwin could you check again.


ARTEMIS-4244 Fix testSetWebBindingProperties

Fixup for #4441 where I missed that during the updates, oopsie :)


Remove translation from 404 page

The 404 translations were filling up the translation allocation - so removing the translations from 404 pages.

New page looks like this:

I checked Japanese and could you use following ?
1st sentence
ページがどこかにいってしましました
button
ホームに戻る

I checked Japanese and could you use following ?
1st sentence ページがどこかにいってしましました
button ホームに戻る

I replaced the translations with the ones that you proposed. Thanks a lot!

here is my opinion for 404 page that you shared.
1st line : 페이지를 찾을 수 없습니다. (404)
2nd line : 이 페이지는 존재하지 않습니다. 페이지 상단의 검색창을 사용해 원하는 문서를 찾아보세요.
button : 홈화면으로 돌아가기 (edited)

Thanks everyone for your input. Unfortunately the design isn't approved so I will revert the 404 page for now and look at incorporating your text updates in a new version of the 404 page in the future.


fix(event_handler): custom serializer recursive values when using data validation

Issue number: #4658
Summary
Recursively include custom serializer for all supported data types (dicts, sequences, dataclasses, Pydantic Models).
Previously, we were only using a custom_serializer for top-level keys. That meant the custom_serializer reference was getting lost during recursion.
With this change, we can now correctly serialize custom items in a list, custom values in a dict, custom values in a dataclass/Pydantic model, etc. however deep.
Changes

Please provide a summary of what's being changed

User experience

Please share what the user experience looks like before and after this change

from aws_lambda_powertools.event_handler.openapi.encoders import jsonable_encoder
from bson import Decimal128

def custom_serializer(obj):
    if isinstance(obj, Decimal128):
        return int(obj.to_decimal())

    return obj

# work
print(jsonable_encoder(Decimal128('123'), custom_serializer=custom_serializer))

# works AFTER this PR gets merged
print(jsonable_encoder({'dec': Decimal128('123')}, custom_serializer=custom_serializer))

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[x] Meet tenets criteria
[x] I have performed a self-review of this change
[x] Changes have been tested
[x] Changes are documented
[x] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Will check CI later this afternoon.

@leandrodamascena when you can, I'm gonna need your help on how to best test pydantic version differences to get this to pass.
I'll get back to this late afternoon / evening

@leandrodamascena when you can, I'm gonna need your help on how to best test pydantic version differences to get this to pass.
I'll get back to this late afternoon / evening

Hey @heitorlessa! Two things here:
1 - I found a bug in the Nox tests that is installing Pydantic 2.0 in the v1.0 test only in some situations, I don't know why, but it is. To fix this, I'll change this line to @nox.parametrize(" pydantic", ["1.10,<2.0", "2.0"]).
2 - This test is wrong because it is not possible to do this with Pydantic to dump JSON. The first thing we do when we detect that it is a Pydantic model is to dump it into JSON and then invoke the jsonable_encoder function again with this JSON, and in this new invocation it is possible to use custom_serializer. I understand what you tried to do, but we need to change this test a little.

I'll fix both problems tomorrow morning! Thanks for working on this.

Gotcha! thanks a lot @leandrodamascena and for fixing the pydantic nox unrelated bug too; I didn't know field_serializer existed.
class MyResult(BaseModel):
    name: str
    token_list: TokenList

    @field_serializer('token_list')
    def token_list_serializer(self, token_list: TokenList, _info):
        return orjson.Fragment(orjson.dumps(token_list.model_dump()))

@sthulb need your approval as Leandro pushed a fix to this PR


Use dvcs-link

Why adding a dependency?

Separating the logic from a specific editor means that functionality can be more easily implemented in multiple editors. It introduces a separation of concerns between the functionality offered and the interface through which it is accessed.


Bug #782 Manifest fix

Issue number
Relevant issue number

Resolves #782

Please check the following

[x] Do the tests still pass? (see Run the Tests)
[x] Is the code formatted properly? (see Linting (Formatting))
For New Features:

[ ] Have tests been added to cover any new features or fixes?
[ ] Has the documentation been updated accordingly?

Please describe additional details for testing this change

Move manifest to /public
Added missing logo
Added screenshots for install window

@Haviles04 have you tried building the frontend with npm run build and then checking it out at localhost:1337 to see if the manifest etc is picked up?

I have not, but I'll try that and report back

@Haviles04 have you tried building the frontend with npm run build and then checking it out at localhost:1337 to see if the manifest etc is picked up?

I have not, but I'll try that and report back

@itsalaidbacklife confirmed everything works after running npm run preview and opening on localhost:1337


brew cleanup --help features incorrect linebreaks

brew config output
HOMEBREW_VERSION: 3.3.9-122-g578286a-dirty
ORIGIN: https://github.com/Homebrew/brew
HEAD: 578286a94701a2f9c013266e76f02a41079edbaf
Last commit: 14 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: c2eb6bdb7f29f5b341461366b82be847aa6894f5
Core tap last commit: 4 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_CORE_GIT_REMOTE: https://github.com/Homebrew/homebrew-core
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.Jz9hsDzhLP/org.macosforge.xquartz:0
HOMEBREW_EDITOR: subl
HOMEBREW_GITHUB_PACKAGES_TOKEN: set
HOMEBREW_GITHUB_PACKAGES_USER: mistydemeo
HOMEBREW_MAKE_JOBS: 8
HOMEBREW_NO_AUTO_UPDATE: set
HOMEBREW_NO_INSTALL_CLEANUP: set
Homebrew Ruby: 2.6.8 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: octa-core 64-bit arm_firestorm_icestorm
Clang: 13.0.0 build 1300
Git: 2.31.1 => /opt/homebrew/bin/git
Curl: 7.77.0 => /usr/bin/curl
macOS: 12.1-arm64
CLT: <IP_ADDRESS>.1.1638488800
Xcode: 13.2.1
Rosetta 2: false

### `brew doctor` output

```shell
Only errors about uncommitted changes that I used to generate the "expect to happen" result below.

Verification

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
brew cleanup --help has a surprising line wrap error which causes the last bit of text, --cache)", to be wrapped back to the start of the command alongside the short flag. It incorrectly implies that --cache is the long-form flag for -s, which has no long-form flag.
This was "introduced" in f426f1f51fb728618a9c1d756a4a5b7c0b6bed8f in that an extra word was added to the switch description that pushed the last word onto a new line, triggering the bug, but I haven't yet identified the root cause.
What happened (include all command output)?
  -s, --cache)"                   Scrub the cache, including downloads for
                                   even the latest versions. Note that
                                   downloads for any installed formulae or
                                   casks will still not be deleted. If you
                                   want to delete those too: rm -rf "$(brew

What did you expect to happen?
  -s                               Scrub the cache, including downloads for
                                   even the latest versions. Note downloads
                                   for any installed formulae or casks will
                                   still not be deleted. If you want to delete
                                   those too: rm -rf "$(brew --cache)"

Step-by-step reproduction instructions (by running brew commands)
`brew cleanup --help`

Think I figured out what's going on. In our CLI parser code, we dispatch to the underlying OptionParser's #on here: https://github.com/Homebrew/brew/blob/master/Library/Homebrew/cli/parser.rb#L162-L167
In other words, we call @parser.on(*names, *wrap_option_desc(description)). wrap_option_desc(description) splits the description across multiple lines and, thanks for the aforementioned extra word, pops --cache from the description on the last line. OptionParser's underlying #make_switch command here doesn't distinguish between arguments positionally: it just gets everything in one args array: https://github.com/ruby/optparse/blob/master/lib/optparse.rb#L1325 And operates on them based on whether they "look like" an option: https://github.com/ruby/optparse/blob/master/lib/optparse.rb#L1398-L1407
Which leads to our bug. Because our own line-splitting code has now put the --cache)" from the end of the help text on its own line, OptionParser sees it as a new switch definition and not a continuation of the description text. This ambiguity is, arguably, a bug in OptionParser: I don't think it makes any sense for it to start taking switches again after it's accepted non-switch strings. As written, however, it's doing the "right" thing and our code does have a weird ambiguity here that leads to this.
A workaround here would be to make sure our line-splitter never begins a line with - or --, gross as that feels.

I opened #12672 with a possible solution (different from what you suggested)

@mistydemeo Nice debugging, thanks ❤


How to update a docker-built container?

What are the steps to update a previously built docker container?
I’d imagine an update of the repository
git pull origin master  ?
a (manual?) review of .env changes?
then somehow updating the database without losing data? perhaps there’s a new schema. this is where I’m conceptually stuck.
I also notice that the docs require the database to be run first, which my existing installation logs suggest is new?
then docker build?

tagging @zomars here. Since the schema update during compilation is very recent, there may be relevant steps for even the non-container build that are documented and can be adapted

But the Prisma migrations in the build are safe for existing databases, correct? Wasn't sure if there were any recommendations for upgrading in production and running the build against a shadow db

They should be safe yes


[Storage] Update dependencies in storage-file-datalake's sample and update changelogs.

/azp run js - storage-blob - tests


[stable/openebs] admission server deployment doesn't honor imagePullPolicy

Deployment should use value from values.yaml here.

Thanks @Prototik, will fix the pull policy to use it from the values.yaml, in upcoming PR.


Pause menu has lights shining through

See screenshot. Perhaps an engine bug??

I haven't found a way to fix this.


As a user, I want to upload a document to cloud storage, attach it to a project and specify document versions

Description:
How do we upload documents to cloud storage, attach those documents to a project, and define a version history of documents?
Development Checklist:

[ ] Figure out the entire skeleton that supports the above user story
[ ] How do we define storage?
[ ] How do we define versioning of documents?
[ ] Set up developers meeting/discussion
[ ] Identify pros/cons, investigate available solutions, document what was investigated and why a certain decision was made (document in the repo)
[ ] Meets the DOD

Notes:

This is code skeleton that we can iterate on
Code that we keep
Look at document storage that was created for the WALLY app / GWELLS

Hi @AlexZorkin! I tested in Dev:

select link 'attachments'
select button 'upload'
file browser opened and I was able to select documents (tried a jpg and PDF). However, nothing happened after this. Should I be able to see a list of uploaded files?

Hi @AlexZorkin ! Following up on this ticket. I'm still experiencing the same issue, where I upload a document, but then nothing happens.

@matthieu-foucault Is the ticket title accurate because it reads like attachments would first be uploaded and then associated with a project, but my understanding is a project would first be created and then attachments upload to it. Thoughts?


New instrument request: ncas-cam-11

Instrument Manufacturer
Canon
Instrument Model
EOS 6D Mark II
Instrument Serial Number
583053001031
Instrument Scientist Name
James Groves
Instrument Scientist ORCID
https://orcid.org/0000-0002-7073-2085
Instrument Owner (and ROR ID)
National Centre for Atmospheric Science (https://ror.org/01wwwe276)
If "Other" selected above, please type the owner and ROR ID (if known) below.
No response
NCAS Observatory
mobile
Instrument description
The Instrument is part of an automated camera system built to enable a better understanding of how cloud formations develop. . Each camera system has: a Canon EOS 6D Mark II camera, a UV lens filter, a Raspberry Pi, a Mikrotik Wifi transmitter/receiver, an 8Gb SD card and a 2Tb External hard-disk. The camera had an f/1.8 50mm prime lens giving angles-of-view of 40º, 27º,46º in the horizontal, vertical, and diagonal respectively, captured within 6240 x 4160 pixels.
The timelapse images this system provides a useful perspective on the development of the clouds, and in addition can be used to estimate properties such as the height of cloud base and cloud top.

@lecjlg: Josh and I have looked over this request and believe we have settled on the various required fields. Are you happy with these before we move to adding them to the vocab?

Yes all fine. thank you

Instrument details added to vocab list


Suggestion: Spell Rotate

Hi, I was wondering if it can be possible instead of having that spell selection inside your inventory to just rotate through the spells when you right-click on your wand.

Whoops apparently you can on individual wands.

Ah, yup "mode: cycle". Glad you found it :)