Fix missing filters for get settings validator

This PR fixes the missing filters to get the settings validators for plugins to work again.

@wolflu05 you might need to merge/wait for https://github.com/inventree/InvenTree/pull/5486 to fix the doc's errors

@wolflu05 please check out the CI errors

I didn't manage to identify why I sometimes not get the kwargs but in the tests I get them. This is the easiest fix that works. Do you have a better idea of fixing the validators for plugins?

@wolflu05 happy with this fix, but given this might change some pretty low-level stuff, can you please provide some updated unit tests? In particular related to the edge cases you were seeing

@wolflu05 would you be able to throw in some extra unit tests here?

@SchrodingersGat I now found the place where the clean function is called with additional kwargs which is against Django's implementation, so I removed the kwargs completely and replaced them with the self.get_filters_for_instance() function. I added two tests, one directly for the Settings and one more integrated into the plugin registry to make sure validators actually work with settings that have extra relations too. Now I only need to find out, why the test passes locally but not in CI.

These types of errors are always very frustrating to track down! Thanks for adding the tests

@SchrodingersGat I found the culprit. I came across this after connecting via tmate and adding several prints to the code while running the tests over and over and see how far it runs. I then discovered that the validator doesn't run because it's not callable, but he is a static method. I then googled why static methods are sometimes not callable (I used a static method for the validator) and found this. I then asked myself why it works on my machine and on ci not and then found out, I run python 3.10 in the devcontainer and ci 3.9. Python must have changed that behavior. I can validate that by running the provided snippet in the StackOverflow post and on my machine with 3.10 it returns True for both and on ci only for the direct check.
So TL;DR, make sure we don't use static methods for validators anywhere, as they are not marked as callable in some circumstances. The tests should pass now after moving the validator into the global scope as a normal function.

@wolflu05 that's some fine detective work, well done!

💚 All backports created successfully

Status
Branch
Result

✅
0.12.x

Questions ?
Please refer to the Backport tool documentation


make: *** No targets specified and no makefile found.  Stop.

I have an issue,it seens no makefile
OS:ubuntu18.04
cmake version:3.20.3
,this is CLI print:

The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:3 (project):
No CMAKE_CXX_COMPILER could be found.
Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred!
See also "/chia-plotter/build/CMakeFiles/CMakeOutput.log".
See also "/chia-plotter/build/CMakeFiles/CMakeError.log".
make: *** No targets specified and no makefile found.  Stop.
root@yui-virtual-machine:/chia-plotter#
cmake error log:
Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
Compiler: CMAKE_CXX_COMPILER-NOTFOUND
Build flags:
Id flags: --target=arm-arm-none-eabi;-mcpu=cortex-m3
The output was:
No such file or directory
Can anyone solved it?
regards!

Do you have cmake installed?

no, which directory should I run cmake？

Try installing build-essential if you haven't already.

The same problem, looking forward to solving

Same problem here, earlier version compiled just fine

Try installing build-essential if you haven't already.

Thx,but it still not work

Id flags: --target=arm-arm-none-eabi;-mcpu=cortex-m3
Are you compiling on a RPI?

Try making sure g++ is installed: it should be included in build-essential, but just in case,
apt-get install g++
Then do gcc --version and post its output here.

Id flags: --target=arm-arm-none-eabi;-mcpu=cortex-m3
Are you compiling on a RPI?

No,compiling on X86 ubuntu 20.04,
Dependencies:
libsodium-dev/focal,now 1.0.18-1 amd64
libgmp3-dev/focal,now 2:6.2.0+dfsg-4 amd64
cmake version 3.16.3

calling make -j8 $@ manually seems to work.

It seems that something with your cmake/gcc installation is messed up. Basically cmake cannot even compile a test program to figure out if your compiler works...

Maybe reinstall cmake if it continues to not work? This post is linked in the readme if that helps at all. I had to make some tweaks to get my cmake to install on 20.04 - let me know if you need them.

calling make -j8 $@ manually seems to work.

make: *** No targets specified and no makefile found.  Stop.
the makefile doesn't found

you cross compiling?
because that's not intel:
Build flags:
Id flags: --target=arm-arm-none-eabi;-mcpu=cortex-m3
run a ./clean_all.sh

It seems that something with your cmake/gcc installation is messed up. Basically cmake cannot even compile a test program to figure out if your compiler works...

I run cmake it out out put :make: *** No targets specified and no makefile found. Stop.maybe is not cmake/gcc problem

you cross compiling?
because that's not intel:
Build flags:
Id flags: --target=arm-arm-none-eabi;-mcpu=cortex-m3
run a ./clean_all.sh

you cross compiling?
because that's not intel:
Build flags:
Id flags: --target=arm-arm-none-eabi;-mcpu=cortex-m3
run a ./clean_all.sh

My CPU is I5 7400 running ubuntu in VMware workstation 14, and how do I  build this flag?

This: sudo apt-get install libssl-dev and sudo apt-get install build-essentials fixed it for me. Fresh Ubuntu 20.04 server install in VirtualBox.

This: sudo apt-get install libssl-dev and sudo apt-get install build-essentials fixed it for me. Fresh Ubuntu 20.04 server install in VirtualBox.

Thx a lot I gonna try it later~

Hi all! I solve the issue, is the command"git submodule update --init" doesn't get makefile into my directory /chia-plotter/lib/bls-signatures, I have this command "rerun git submodule update --init" redownload the make files,  The compiling working~
Maybe this information can help someone else! By the way, thx guys all!


Docs stopped getting updates on releases

New Regression Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Regression Information

Breaking version: 2.221.0+
Last working version: 2.220.0

Regression Description
Since moving version bumps to GH Releases automation, documentation updates are not being pushed (their PR opened) against fastlane/docs [list]

"Is it somehow possible that these new bump lanes now avoid the release lane, which is the only place to run :update_docs and it's not being pushed now?"

— Originally posted by @janbrasna in https://github.com/fastlane/fastlane/pull/22090#discussion_r1660308917

"I'm trying to trace the Fastfile lanes to when they're being called (:release to :update_docs) but with not much luck, it only seems as the new bump logic somehow avoids these calls?

basically here https://github.com/fastlane/fastlane/pull/22080#issuecomment-2159671381 is mentioned the moving to GHA, but I can't seem to locate some bigger epic tracking what's being done, what's done, what's known to be missing for now etc., so can't tell if it's a known issue, or is supposed to be run manually somehow etc.?
but it feels that in the new automation this ought to be called upon cutting a Release on GH, so that'd be perhaps during :create_github_release?"

— Originally posted by @janbrasna in https://github.com/fastlane/fastlane/pull/22090#discussion_r1676834000
Environment
GHA/CI

THis is cool!!! What you did?


Re-order and flatten the documentation hierarchy to make navigating easier

As an effort to improve the Windows Search documentation, this initial change restructured the document hierarchy to bring relevant information forward and make navigating easier

This looks good to me Tim, any other steps we need to do to get this approved @mcleanbyron?

This PR came from an internal Microsoft engineering team. I am routing them through the internal process for doc updates, and am therefore closing this PR.


Review user-centered report evaluation results

Hey all -- Like I said, I was working on reviewing all the things in econ-ark / HARK to try to focus on improving the project to both users and contributing users. This doc is not done, but I think it is good jumping off point.
https://docs.google.com/document/d/1MztmMO0IJy-xagnluJjqZmPrVkI1pAAfp3Lm-g6ijNY/edit#
(Please explicitly ask for permission. I didn't just want to open to the world.)
2 things to do in this ticket to consider it "Done":

Review the doc and add to it if anything is missing.
Go through the doc and the existing tickets and add links to the doc to the tickets if something is already in progress.

P.S. I used a checklist from a talk I have done a couple of times to create this list. I was thinking of taking this evaluation and turning it into a blog post and using HARK as an example.... it has a solid start, but just hasn't done this before. Is there a specific blog that you think might go well on? (if not, I can post it on medium.)

Quick thing: Where it's relevant, I refer to branches by name in Issues, where applicable.  But I didn't know you could associate a branch with an Issue.  How do you do that?

@mnwhite I didn't realize that was happening. I was looking at it the other way....
here is a screenshot of branches...

I was approaching it from... how do I know which branch goes with which ticket?
Let's take your approach for OpenCL-dev branch.
For the sake of this description, let's say this is the ticket https://github.com/econ-ark/HARK/issues/136 - (Assumes that is the right ticket and someone forgot to explicitly add it.)
^^ If that is the case, then that is valid approach. When I wrote that, I was thinking... OpenCL-dev.136 and putting the ticket number in the branch name.

First: Now that I look around, I can only find a couple examples of what I referred to above.  There are probably older ones on closed issues.
But now I understand what you're talking about.  Going forward, that is a good policy.  I've tried to make issues to describe what I'm working on in the dev branches, but there's no indication of that from the branches themselves.
As your document alludes to, this will be more visible / transparent when we have a real webpage with a What's Happening (or whatever the kids are saying these days) section with descriptions of work in progress.

Is this relevant still?

Huh!  I didn't know this existed.  But we've implemented most of the suggestions by now, so I think we can close this.


Logging loop

If FluentLogger is used as an appender with logback (such as https://github.com/sndyuk/logback-more-appenders) then any logging by FluentLogger and related classes such as RawSocketSender can end up creating a nice little logging loop.
For instance, RawSocketSender will log "Created messages" or a message when the buffer is full... all of which get routed back into slf4j and then likely routed right back into FluentLogger for logging....
While the obvious answer is to drop any org.fluentd.logger.* messages that would end up routed to the FluentLogger appender (thereby possibly leaving them routed to other appends) that would then mask any real messages but I wonder if there is a better solution?
I don't have any ideas but figured I'd throw the problem out there and maybe someone would have a good idea.
It may also be helpful to enable some type of throttling on messages--- like if the buffer is full due to a down fluentd.
Also cross posted here: https://github.com/sndyuk/logback-more-appenders/issues/2

Agreed.  I just encountered this issue in RawSocketSender.  Our log file filled up the filesystem with messages like the following:
ERROR 16-04-20_14:16:18 [pool-1-thread-1] o.f.l.s.RawSocketSender send Cannot send logs to /<IP_ADDRESS>:24224
It seems that the RawSocketSender was having issues flushing the buffer.  Every log message that was sent in to fluentd (including these messages sent by RawSocketSender) would attempt to trigger another flush, which would fail and send the error again.
It seems like there could be several options to improve this.  Any preferences, and I can create a pull request?

Throttle / rate limit the number of times RawSocketSender will print this message.
Move the error message into the flushBuffer() method inside the enableReconnection if statement.  This would at least limit the error message to only as often as it attempts to reconnect, instead of on every log message.
Configure our system to explicitly filter or limit log messages from the RawSocketSender or other fluentd classes. We are actually using logback instead of directly using fluentd.

It also seems like the send() method could be simplified.  It's currently calling flush() twice if the pending buffer is full.  It seems like it might only need to call flush() once, and only if the pending buffer is full.

I am having the same problem. RawSocketSender shouldn't have a Logger instance capable of writing logs himself otherwise it will have an infinite loop.
public class RawSocketSender implements Sender {     private static final Logger LOG = LoggerFactory.getLogger(RawSocketSender.class); }
As a quick solution I've downloaded RawSocketSender and removed all LOG.* calls.


private and public methods sorted by name to simplify syncing with Playn HtmlGl20

Both variants have some independent improvements that may make sense to carry over.
Sorting simplifies the comparison.

ping?

Pong :)

Sorting the glXyz methods makes sense, but sorting the special methods (ensureCapacity(), allocateUniform(), ... ) doesn't imo.

I'll delete them in a followup
On Tue, Jun 21, 2016 at 10:36 PM intrigus<EMAIL_ADDRESS>wrote:

Sorting the glXyz methods makes sense, but sorting the special methods
(ensureCapacity(), allocateUniform(), ... ) doesn't imo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/libgdx/libgdx/pull/4153#issuecomment-227563513, or mute
the thread
https://github.com/notifications/unsubscribe/AEFXz1vR5Rwf3p-79aXH8baMVSkxex3Sks5qOEtMgaJpZM4I30qr
.


Dell Latitude 3340

Description of changes
The Dell Latitude 3340 does not have the same touchpad situation as later Latitudes.
Things done

[x] Tested the changes in your own NixOS Configuration here
[x] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

(I'm not actually sure what an end to end test would be)

End-to-end means you are importing your nixos-hardware fork and testing the options on actual hardware.

I made a new PR which was a squashed version of yours. This has been merged now: https://github.com/NixOS/nixos-hardware/pull/500


[Request] A safe cast operation in the standard library

A common issue when interacting with java code (an even more so when interacting with non typesafe languages such as clojure) is converting an object at runtime depending on its concrete type.
Because of the hierarchical structure of the java class system this is often most conveniently done by attempting to cast the object in question to the desired class and providing a backup in case of failure.
This is a prime use case of Maybe.
I therefore propose the addition of a safe casting function to the standard library.
-- `safeCast` as pendant to `unsafeCast`
safeCast :: Extends a b => b -> Maybe a

A typical use case would be like so:
data {-# CLASS "my.library.Binding" #-} Binding = Binding (Object# Binding) deriving Class

data FnReturn = Direct Binding | Destructure [Binding]

-- in clojure we will will either have the binding direct or a collection of them, since the support for ADT's is not as good
convertFromNative :: Object -> FnReturn
convertFromNative o = maybe (Direct $ unsafeCast o) (Destructure . fromJava) (safeCast o :: Maybe (Collection Binding))

Run git pull.
Go into libraries/base and run epm install --solver=topdown.
Go to your working project and do epm clean and then epm build. The clean will remove references to the old base library.


Need more tsdb log

What did you do?
stop graceful prometheus or killed hard prometheus
What did you expect to see?
Want to see more tsdb starting logs
Whatever stop graceful or killed hard, tsdb start will spend long time (1 minute - 10 minute) or hang at starting tsdb log. and I cannot figure out what cause the long time start.
What did you see instead? Under which circumstances?
time="2017-09-18T14:47:08+08:00" level=info msg="Starting tsdb" source="main.go:224"
time="2017-09-18T14:48:19+08:00" level=info msg="tsdb started" source="main.go:230"

Environment

System information:

Linux 2.6.32-696.3.2.el6.v6.2.x86_64 x86_64

Prometheus version:

prometheus, version 2.0.0-beta.4 (branch: HEAD, revision: 1b80f631a88a01473c1356d50da12eb49b462050)
build user:       root@c5b3f10ffc51
build date:       20170914-11:22:50
go version:       go1.8.3

Prometheus configuration file:

global:
  scrape_interval:     15s
  evaluation_interval: 15s
  external_labels:
      monitor: 'codelab-monitor'
      slave: 1

rule_files:
  - "alert_rules/*"
  - "query_rules/*"

scrape_configs:
  - job_name: 'app-exporter'
    scrape_interval:     30s
    static_configs:
#with a lot of static server targets

  - job_name: 'qm'
    scrape_interval: 5s
    file_sd_configs:
      - files: ['/usr/local/prometheus/qmgroups/*.json']

  - job_name: 'kubernetes-controller-manager'
    scheme: http
    static_configs:
      - targets:
          - 'a.net:10252'
    relabel_configs:
      - target_label: hulkid
        replacement: 2936

  - job_name: 'kubernetes-scheduler'
    scheme: http
    static_configs:
      - targets:
          - 'a.net:10251'

  - job_name: 'kubernetes-apiserver'
    scheme: https
    kubernetes_sd_configs:
       - api_server: ['b.net:6443']
        role: endpoints
        tls_config:
          ca_file: /usr/local/prometheus/ssl/ca.pem
          cert_file: /usr/local/prometheus/ssl/kube-admin.pem
          key_file:  /usr/local/prometheus/ssl/kube-admin-key.pem
    tls_config:
      ca_file: /usr/local/prometheus/ssl/ca.pem
      cert_file: /usr/local/prometheus/ssl/kube-admin.pem
      key_file:  /usr/local/prometheus/ssl/kube-admin-key.pem
      insecure_skip_verify: true
    relabel_configs:
    - source_labels: [__meta_kubernetes_namespace, __meta_kubernetes_service_name, __meta_kubernetes_endpoint_port_name]
      action: keep
      regex: default;kubernetes;https

alerting:
  alertmanagers:
  - scheme: http
    static_configs:
    - targets:
      - "alertmanager-1:9093"
      - "alertmanager-2:9093"

Hi, on startup we read the write ahead log (WAL) and that could several be Gigs in size which could take several mins. But that is essentially the only thing that happens on startup so I am not sure if we should print anything else.

@tinytub this should've been a deadlock in TSDB (fixed in prometheus/tsdb#146). More logging would generally not help as @Gouthamve pointed out but #3186 should improve debugging capabilities if such things come up in the future.

@fabxc thx a lot, hope for next prerelease


Update IronPython.nuspec

System.Memory was updated from 4.5.4 to 4.5.5 because of issue https://github.com/IronLanguages/ironpython3/issues/1562 and PR https://github.com/IronLanguages/ironpython3/pull/1565/
This change is to align the version in nuspec

Thanks!


[BUG] 调用deepflow-app查询接口同样的参数，多次请求返回结果报错

Search before asking

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

DeepFlow Component
Server
What you expected to happen
调用deepflow-app /v1/stats/querier/tracing-completion-by-external-app-spans 接口时，同样的参数多次请求后结果不一样，其中有的请求可以正常返回，个别请求会报错，返回结果： {"OPT_STATUS":"INTERNAL_SERVER_ERROR","DESCRIPTION":"sequence item 0: expected str instance, tuple found"}
How to reproduce
curl  -XPOST  -d @res.json  http://deepflow-app:20418/v1/stats/querier/tracing-completion-by-external-app-spans
res.json 请求参数内容如下：
{
"max_iteration": 30,
"network_delay_us": 3000000,
"app_spans": [
{
"trace_id": "6e0d4e8400d6245cd7d79bd3e93a9331",
"span_id": "9b4f811a79ae2e23",
"parent_span_id": "c6de620aad290f5b",
"span_kind": 3,
"start_time_us":<PHONE_NUMBER>000000,
"end_time_us":<PHONE_NUMBER>000000
}
]
}
多次请求过程如下：
[root@iZbp1cwk6wj01xgalmbmxwZ ~]# date && sh deepflow-res.sh
Mon Feb 26 18:18:12 CST 2024
{"OPT_STATUS":"SUCCESS","DESCRIPTION":"","DATA":{"tracing":[{"_ids":["194515355480136"],"related_ids":[],"start_time_us":1708912800000000,"end_time_us":1708914000000000,"duration":1200000000,"tap_side":"c-app","l7_protocol":0,"l7_protocol_str":"","endpoint":"","request_type":"","request_resource":"","response_status":0,"flow_id":"0","request_id":0,"x_request_id_0":"","x_request_id_1":"","trace_id":"6e0d4e8400d6245cd7d79bd3e93a9331","span_id":"9b4f811a79ae2e23","parent_span_id":"c6de620aad290f5b","req_tcp_seq":0,"resp_tcp_seq":0,"syscall_trace_id_request":"0","syscall_trace_id_response":"0","syscall_cap_seq_0":0,"syscall_cap_seq_1":0,"attribute":null,"process_id":null,"vtap_id":0,"app_service":"","app_instance":"","tap_id":0,"tap":"","deepflow_span_id":"9b4f811a79ae2e23","deepflow_parent_span_id":""}]},"TYPE":"tracing-completion-by-external-app-spans"}
[root@iZbp1cwk6wj01xgalmbmxwZ ~]# date && sh deepflow-res.sh
Mon Feb 26 18:18:17 CST 2024
{"OPT_STATUS":"SUCCESS","DESCRIPTION":"","DATA":{"tracing":[{"_ids":["229096304877981"],"related_ids":[],"start_time_us":1708912800000000,"end_time_us":1708914000000000,"duration":1200000000,"tap_side":"c-app","l7_protocol":0,"l7_protocol_str":"","endpoint":"","request_type":"","request_resource":"","response_status":0,"flow_id":"0","request_id":0,"x_request_id_0":"","x_request_id_1":"","trace_id":"6e0d4e8400d6245cd7d79bd3e93a9331","span_id":"9b4f811a79ae2e23","parent_span_id":"c6de620aad290f5b","req_tcp_seq":0,"resp_tcp_seq":0,"syscall_trace_id_request":"0","syscall_trace_id_response":"0","syscall_cap_seq_0":0,"syscall_cap_seq_1":0,"attribute":null,"process_id":null,"vtap_id":0,"app_service":"","app_instance":"","tap_id":0,"tap":"","deepflow_span_id":"9b4f811a79ae2e23","deepflow_parent_span_id":""}]},"TYPE":"tracing-completion-by-external-app-spans"}
[root@iZbp1cwk6wj01xgalmbmxwZ ~]# date && sh deepflow-res.sh
Mon Feb 26 18:18:20 CST 2024
{"OPT_STATUS":"SUCCESS","DESCRIPTION":"","DATA":{"tracing":[{"_ids":["130641604982580"],"related_ids":[],"start_time_us":1708912800000000,"end_time_us":1708914000000000,"duration":1200000000,"tap_side":"c-app","l7_protocol":0,"l7_protocol_str":"","endpoint":"","request_type":"","request_resource":"","response_status":0,"flow_id":"0","request_id":0,"x_request_id_0":"","x_request_id_1":"","trace_id":"6e0d4e8400d6245cd7d79bd3e93a9331","span_id":"9b4f811a79ae2e23","parent_span_id":"c6de620aad290f5b","req_tcp_seq":0,"resp_tcp_seq":0,"syscall_trace_id_request":"0","syscall_trace_id_response":"0","syscall_cap_seq_0":0,"syscall_cap_seq_1":0,"attribute":null,"process_id":null,"vtap_id":0,"app_service":"","app_instance":"","tap_id":0,"tap":"","deepflow_span_id":"9b4f811a79ae2e23","deepflow_parent_span_id":""}]},"TYPE":"tracing-completion-by-external-app-spans"}
[root@iZbp1cwk6wj01xgalmbmxwZ ~]# date && sh deepflow-res.sh
Mon Feb 26 18:18:23 CST 2024
{"OPT_STATUS":"INTERNAL_SERVER_ERROR","DESCRIPTION":"sequence item 0: expected str instance, tuple found"}
DeepFlow version
deepflow-server: v6.4.9
deepflow-agent: v6.4.9
DeepFlow agent list
No response
Kubernetes CNI
flannel
Operation-System/Kernel version
"Alibaba Cloud Linux (Aliyun Linux) 2.1903 LTS (Hunting Beagle)"
4.19.91-27.6.al7.x86_64
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

这个问题正在修复中

可以提供下报错时的日志吗

这个是当时使用deepflow-app查询时日志报错的截图


CLDC-3264: Setup to allow using future form on staging for testing

There is a bit of "just be sensible" here: the allow_future_form_use toggle as defined here will allow you to fill in logs on the service with dates arbitrarily far in the future, although e.g. they won't show up on the relevant logs page because even with no filters selected that does filter to the available years (current, previous, next, and when relevant archived). For bulk upload it only allows the next year - but it will show you the option of that even if we've not actually defined a row parser for that year yet.
I reckon we're probably fine with this.


Nested TabLayout inherit parent style

When nesting TabLayout the child inherit parent CSS.
It's annoying when you want to nest a TabLayout with tabsPosition to top in a TabLayout with tabsPosition to left, it result in the second TabLayout to not draw title and to display them to the left.

Code sample:
new photonui.TabLayout({
    tabsPosition: "left",
    children: [
        new photonui.TabItem({
            title: room.label,
            child: new photonui.GridLayout({
                horizontalSpacing: 5,
                verticalSpacing: 5,
                children: [
                    new photonui.Text({
                        rawHtml: "<strong>" + _("Superficie") + "</strong>",
                        layoutOptions: {
                            x: 0, y: 0,
                            cols: 1, rows: 1
                        }
                    }),
                    new photonui.Label({
                        text:  (room.area / 10000).toFixed(2) + "m²",
                        layoutOptions: {
                            x: 1, y: 0,
                            cols: 1, rows: 1
                        }
                    }),
                    new photonui.TabLayout({
                        tabsPosition: "top",
                        children: [
                            new photonui.TabItem({
                                title: _("Menuiserie"),
                                child: new photonui.Label({text: "Test"})
                            })
                        ],
                        layoutOptions: {
                            x: 0, y: 1,
                            cols: 1, rows: 2
                        }
                    })
                ]
            })
        })
    ]
})

Hi @pstkweb, I just propose a PR to fix your problem. You just need to get the new css files (base + themes).
You could give it a try waiting @flozz validation.

Thanks for the fix @MangelMaxime

Merged on develop :)

Fixed in PhotonUI 1.4.1


Migrate / support MSW 2

With the new release of MSW, it would be great if playwright-msw supports it as well.
[edit]
Gonne give it a go to provide a PR if I can find some time this week

Let me know if you have any questions/need help. Should be rather straightforward. The Migration guide should be all that you need. Thanks for this amazing project!

Sorry, been crazy busy. Actually gonna give it a new try next week

Hey @the-ult, thanks for the polite nudge to support MSW 2.0. I appreciate the offer for help and completely understand that you've been quite busy. I've started working on the migration and should hopefully have it done this weekend.
@kettanaito Thanks for creating this amazing library and sharing the migration guide. Absolutely love all the examples, it's making this conversion a breeze 🙂

Thank you @valendres. That's awesome!

@the-ult I've got a PR up for the migration. I'd love to get your review if you have a chance: https://github.com/valendres/playwright-msw/pull/77

Hey everyone<EMAIL_ADDRESS>is now available, bringing compatibility with MSW 2.
A huge thank you goes to @the-ult and @kettanaito for your detailed reviews, and @mamidenn for your initiative in addressing the feedback, as discussed in the corresponding PR. Your efforts have been crucial and are deeply appreciated.
I apologize for the delay in supporting MSW 2. Balancing house moving, renovations, and attending AWS re:INVENT has made my schedule quite tight. But with re:INVENT behind us and the move nearly complete, I’m thrilled to bring this new version to you all.
Although all of the integration tests in this repo are passing, the real-world usage is the ultimate test. I’m eager to hear your experiences with upgrading. If you encounter any issues or have feedback, please don’t hesitate to respond here, open a new issue, or submit a pull request. Your contributions are always welcomed and valued!

Thank you for your incredible work on this, @valendres! 👏

@valendres - although it's not really a "real-world" case yet, this library (at v3.0.1) worked well for me with Playwright and handlers created using MSW's http.get function to test a client-side fetch in a Next.js example repo (https://github.com/chrisb2244/msw-nextjs-example).
Thanks for the library!


[SPARK-37266][SQL] Optimize the analysis for view text of persistent view and fix security vulnerabilities caused by sql tampering

What changes were proposed in this pull request?
The current implementation of persistent view is create hive table with view text.
The view text is just a query string, so the hackers may tamper with it through various means.
Such as, select * from tab1 tampered with drop table tab1.
Why are the changes needed?
First, the view text is query string, parser.parsePlan(viewText) occurs more overhead than parser.parseQuery(viewText).
Second, the view text can be tampered by hackers and issue security vulnerabilities.
Does this PR introduce any user-facing change?
'No'. Unless hackers tamper view text, user will not see any change.
How was this patch tested?
New tests.

Test build #145054 has started for PR 34543 at commit dc46ba4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49524/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49524/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49524/

Test build #145054 has finished for PR 34543 at commit dc46ba4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #145064 has started for PR 34543 at commit b3f898c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49534/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49534/

Test build #145064 has finished for PR 34543 at commit b3f898c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145064/

ping @MaxGekk @gengliangwang
cc @cloud-fan

Test build #145113 has started for PR 34543 at commit a51a184.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49583/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49583/

Test build #145113 has finished for PR 34543 at commit a51a184.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145113/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49583/

Test build #145126 has started for PR 34543 at commit 81f0ba1.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49597/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49597/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49597/

Test build #145137 has started for PR 34543 at commit 1d8495c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49608/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49608/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49608/

Test build #145126 has finished for PR 34543 at commit 81f0ba1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145126/

Test build #145137 has finished for PR 34543 at commit 1d8495c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145137/

Test build #145169 has started for PR 34543 at commit 77cbbdf.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49639/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49639/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49639/

Test build #145169 has finished for PR 34543 at commit 77cbbdf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145169/

Test build #145178 has started for PR 34543 at commit 0f46831.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49647/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49647/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49647/

Test build #145178 has finished for PR 34543 at commit 0f46831.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145178/

thanks, merging to master/3.2!


Escape breaks fullscreen view

Great work Benjamin ;-) .. I found an issue though:

Click to open an image and view the image
Press Escape to close the image view
Try to click on another image

No other image opens by clicking anymore.
Tested on Chrome 53.0.2767.4 dev-m (64-bit)

Thanks Florian. Took me some time to continue the work on this project .. :)
I fixed this issue in current master.


Parameters are not bound in the MCRY gate

Environment

Qiskit Terra version: sources(https://github.com/Qiskit/qiskit-terra/commit/0df0d29fc44fb571e38530d20743a6e70e230865)
Python version: 3.8
Operating system: MacOS

What is happening?
When a circuit has a parameterized MCRY gate and noancilla mode is selected by the gate, the gate parameter is not bound after calling assign_parameters(). This causes Aer simulator to fail when such a circuit is executed. Since the mode is chosen automatically when it is not set explicitly, the bug appears not in every circuit where mcry is applied. This problem may be overcome by setting use_basis_gates to True. I guess, the same issue is valid for MCRX and MCRZ gates.
How can we reproduce the issue?
Run the snippet:
from qiskit import QuantumCircuit
from qiskit.circuit import Parameter
from qiskit_aer import AerSimulator

qc = QuantumCircuit(3)
p = Parameter("x")
qc.mcry(p, q_controls=list(range(0, 2)), q_target=2, mode="noancilla")
qc = qc.bind_parameters({p: 5.0})
print(qc)
print(f"num parameters: {qc.num_parameters}")

simulator = AerSimulator()
simulator.run(qc)

What should happen?
The output:
                       ┌───┐                   ┌───┐
q_0: ──────────────────┤ X ├─────────■─────────┤ X ├────────■─────────
                       └─┬─┘         │         └─┬─┘        │
q_1: ────────■───────────■───────────┼───────────■──────────┼─────────
     ┌───────┴────────┐     ┌────────┴────────┐     ┌───────┴────────┐
q_2: ┤ U(0.5*x,0,0,0) ├─────┤ U(-0.5*x,0,0,0) ├─────┤ U(0.5*x,0,0,0) ├
     └────────────────┘     └─────────────────┘     └────────────────┘
num parameters: 0
Simulation failed and returned the following error message:
ERROR: Failed to load qobj: Unable to cast Python instance to C++ type (#define PYBIND11_DETAILED_ERROR_MESSAGES or compile in debug mode for details)

Any suggestions?
If I set use_basis_gate="True" in the snippet above everything is fine. But this is just a workaround.

I think #8301 is a similar same issue. Also #9514 seems related

This particular issue was fixed by #11032.


Expose Win32 COMMTIMEOUTS values as platform-specific settings

This adds a pair of methods (Get/SetPlatformSpecificSettings()) to allow the user to configure settings that are only relevant to specific platforms in a generic manner by exposing them through an IDictionary<string,object>.
This then fixes #74 by making the Win32 COMMTIMEOUTS values configurable via these methods.
The keys for the COMMTIMEOUTS settings are:

CommTimeouts.ReadIntervalTimeout
CommTimeouts.ReadTotalTimeoutConstant
CommTimeouts.ReadTotalTimeoutMultiplier
CommTimeouts.WriteTotalTimeoutConstant
CommTimeouts.WriteTotalTimeoutMultiplier

You can configure the COMMTIMEOUTS values with the following code:
var settings = new Dictionary<string, object>();
settings["CommTimeouts.ReadIntervalTimeout"] = 100;
settings["CommTimeouts.ReadTotalTimeoutConstant"] = 0;
settings["CommTimeouts.ReadTotalTimeoutMultiplier"] = 0;
settings["CommTimeouts.WriteTotalTimeoutConstant"] = 0;
settings["CommTimeouts.WriteTotalTimeoutMultiplier"] = 0;
stream.SetPlatformSpecificSettings(settings);

Thanks for the patch! I do have concerns about cross platform support, as it now makes it very "windows" centric. I have to think about this. In particular, I see advantages to using strings for the API for stability, but there's no feedback for any way the user can query what settings are actually supported (say that this could be done on Linux, but there are different settings?)
If I were to integrate this, I think there needs to be:

A way to query what settings are supported, which might change based on the OS or other driver information at the time (e.g. the compilation of the underlying Linux support library)
Be able to change individual settings without having to always provide our own dictionary, by exposing a property instead.

In addition to what you've got:
stream.PlatformSpecificSettings["win32.CommTimeouts.ReadTotalTimeoutMultiplier"] = 0;
foreach (string setting in stream.PlatformSpecificSettings.SupportedKeys) {
  Console.WriteLine("Setting: {0} = {1}", setting, stream.PlatformSpecificSettings[setting]);
}

I did include a GetPlatformSpecificSettings() method to retrieve the current values of those settings, though with my current implementation, I think you'd get an empty dictionary unless the port is already open.  It probably wouldn't be hard to change the implementation so that it puts default values for the properties into the dictionary (possibly by moving the default values out of the CommTimeouts constructor and into WinNativeSerial).
I do have one concern with exposing the settings dictionary with a property.  Suppose you were to update all of the COMMTIMEOUTS values one at a time that way while the port is already open.  Which behavior would you want to see?

The changes are applied immediately, so each property update results in calling SetCommTimeouts() on the port to update the value you just changed (for a total of 5 calls).
The changes are buffered until you explicitly call some other method that will apply them all at once.

I'm open to other suggestions as to how to handle that better.

I would argue that programming with properties and code structures is much cleaner and easier to manage than a dictionary of string settings. For something like the WinAPI COMMTIMEOUT feature, I'd stick with having a single structure to contain all the info and you provide only one property to update, thus the call to SetCommTimeouts() is only required once.
However I'm not sure I can provide a decent way of adding OS-specific features to a cross-platform library and personally I would strive to have consistency across platforms rather than feature completeness.

To let you know, I'm considering a different approach on how to do this, and expose the values via a property. This will result in multiple classes (I'll be using Generics)
We all know the current implementation SerialPortStream. Then add a new class:
public class SerialPortStream<T> : SerialPortStream {
  public T Settings { get; }

And T is a type that could be an interface for setting the properties. For this, I'm thinking of doing something (I have to look in the details, still got some other work to do first), that there's a "Native" library.
public class SerialPortStream<T> : SerialPortStream {
  public SerialPortStream(INativeSerialPort<T>) { ... }

  public T Settings { get { return nativeSerial.Settings; } }

This way, it works with implementations already using SerialPortStream. When writing code, the compiler can check and ensure the properties work. A user can derive or provide their own implementation for the native parts (e.g. integration tests that doesn't need specific hardware).
Comments?

That is an excellent idea.

I've provided a different solution now on the master branch (v3.x) with 76253971d133791332e2f3b6df5d2fbee83dcd87. I still need to upload all the other support repositories to build the master. But this PR is now closed.


Can't find a way to render error page

Turbo doesn't render web pages when it encounters a 400..<600 HTTP status code. Is there a way around this? Can you force a page to render despite receiving a visitRequestFailed error?

You might consider implementing your own WebView on the default error native view.

Yeah it's an option but then I lose the native navigation for links on the error page and would have to manually intercept those. Ideally, there would be a solution within Turbo to force render the page.

The standard approach is to render a native error screen for these status codes.
The Demo project shows how you can implement this on your own. Or, check out Turbo Navigator which will handle this for you automatically.


provide a dockerfile

Could you please provide the necessary dockerfile, so that we can use the library in any linux distribution?

Seconded. I've tried building owlcpp from source, but the build script has hardcoded library dependencies (e.g. RAPtor and FaCT++) of some versions I can't find online anywhere. It seems owlcpp doesn't support the latest releases of RAPtor and FaCT++.


Profiler issues

Fixes search for profiler tools and improves the error message when they aren't found.
We still need to properly handle the case where it is not found - the call logic is crazy and handling the exception in the right place for all entry points is not trivial.

👍


latent diffusion training code

 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.

add txt-img data pairs reading code in easynlp/appzoo/latent_diffusion/data.
add ldm_utils.py and lr_scheduler.py in easynlp/utils.
add original class LatentDiffusion(DDPM) in easynlp/modelzoo/models/latent_diffusion/ddpm.py.
add readme.md and update main.py for finetune latent diffusion in examples/latent_diffusion.


Feature request: let the user choose the position of the icon

The icon is positioned at the upper left corner. Is it possible to let the user choose the position (top-left, top-right, bottom-left or bottom-right)? See #8

Feature included by #10


⚠ Bofrost.lu has degraded performance

In 5c4ddb9, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2196 ms

Resolved: Bofrost.lu performance has improved in 9a712b6 after 9 minutes.


US County Level Data

First off, thanks for this valuable resource!
Do you have any plans to parse the county-level info as well for the US?
The aggregate data on a State basis is not really as actionable...
Thanks again!

Google now publishes a CSV along with the PDF which has all the necessary including county-level data..https://www.gstatic.com/covid19/mobility/Global_Mobility_Report.csv

Parsing County level data is a lot of work, and I'd recommend you use the official CSVs for that. Thanks.


mask: optional parameter 'mask-dimensions'

While writing the process graph for use case 1 with @claxn, we had to mask two cubes with dimension (x,y,t_1,s_1) and (x,y,t_2,s_2)
The mask needed is defined in dimensions (x,y), but following the 'mask' process definition, it has to have the same dimensions as the input raster cube to be masked. So in the process graph, we create the 'same' mask twice.
What about adding an optional argument to the process definition <mask-dimensions:(dim_1, dim_2, ...)>
If this option is present, the back-end knows in which dimensions the mask is defined and will apply it to the input cube for all elements of the other dimensions (t and s in the example above). And if it isn't specified, it would work as currently defined and the back-end would expect the mask to have identical dimensions and cardinality as the raster cube to be masked.
What do you think?
note: the name 'mask-dimensions' can be interpreted in two opposing ways, so if people like the idea, we may come up with a better name for this option.

Add a parameter dimensions that name which dimensions the mask applies to.

Isn't this something that can be inferred by the backend? At least applying a 2D mask to a 3D datacube seems straightforward.
We could for instance say that the dimension names of the mask should match the ones in the datacube, and missing dimensions simply means that the mask is to be applied for each label of the missing dimension.
Seems to me that this would be easier to use.

this works when the mask is a datacube with its dimensions and I'm happy with this suggestion.
What about when a user want to use a user-uploaded raster as mask? We need to create a cube with dimensions out of it before applying the mask?

What about when a user want to use a user-uploaded raster as mask? We need to create a cube with dimensions out of it before applying the mask?

Yes, accepted types for the mask are: geojson, raster-cube (, vector-cube). There's no simple "raster" data type in openEO?!

I agree with Jeroen - if mask axes are a subset of data axes, we can automatically apply it. If mask has extra dimensions, we should probably fail. Same if mask has missing labels on any of the common axes.

Anyone up for a PR? I'm a bit lost what the conclusion is...
Is it the following? @mkadunc @jdries @lforesta

Don't add a new parameter?
The data cube and the mask have to be compatible, but dimensions can be missing in the mask.
Each dimension available in mask must be available in the data cube with the same name, type, reference system, resolution and labels.
Missing dimensions in mask means that the mask is to be applied for each label of the missing dimension in the data cube.
A GeoJSON is applies on the x and y axis (and z if available in both).
In all other cases the process fails.

Yes, looks good to me.

Okay, waiting for approvals on #110 so that I can base further changes on that.

See also https://github.com/Open-EO/openeo-processes/pull/110#discussion_r365336523


support https urls

When clicking an http link to youtube kore is listed as one of the apps to open the link with, but not when its an https link. I'm guessing it has to do with the intent filter in AndroidManifest.xml specifying "http" but not "https".
Would the fix be as simple as a copy/paste in the intent filter section changing
android:scheme="http"
to
android:scheme="https"
?

Maybe. Can you try it?

If someone makes the change and compiles the apk, sure. I've never developed for android, i just did some googling to come up with what i did.

done in #292


OpenGL render states show as opposite of what they are

Noticed while using RenderDoc to debug an OpenGL 4.1 application.
The "Multisample", "Sample Shading", "Alpha to Coverage", "Alpha to One" are incorrectly reported.
I believe the following code in "renderdoc/renderdocui/Windows/PipelineState/GLPipelineStateViewer.cs", lines 1358-1362" is responsible. Notice setting the image to cross when the value is true, and to tick when it's false:
multisampleEnable.Image = state.m_RS.m_State.MultisampleEnable ? cross : tick;
sampleShading.Image = state.m_RS.m_State.SampleShading ? cross : tick;
minSampleShadingRate.Text = Formatter.Format(state.m_RS.m_State.MinSampleShadingRate);
alphaToCoverage.Image = state.m_RS.m_State.SampleAlphaToCoverage ? cross : tick;
alphaToOne.Image = state.m_RS.m_State.SampleAlphaToOne ? cross : tick;

Also Scissor test state is not updated correctly. The variable anyScissorEnable is set to false, never updated and then used to display scissor state:
scissorEnable.Image = anyScissorEnable  ? tick : cross;

Good catch! It looks like maybe just a copy-paste error or something. I believe the above commit should fix it.

I snuck this in just before v0.34 so I'm going to close it down as it's fairly evident that it's fixed. If I missed a case or didn't fix it correctly, do let me know. Thanks again for catching this :smile: .


Is there some complete tutorial about how to put into myself data/model/trainer and run a FL task?

Hi, I am trying to follow up on the guidance here: https://federatedscope.io/docs/own-case/, to add the data/model/trainer etc.,  into the project and run up an FL task.
However, this guidance is not that clear, particularly, 1). what does the config section work; 2). how to unify the customized data/model/trainer/config together to complete an FL task.
Is that possible to have complete guidance by using something like mnist/cifar10?

Thanks for your attention!
You can try our playground, where you will get hands-on guidance with MNIST.


Switch to z up in MengeVis

Modifications to the visualization system

Undid the ancient confusion of mapping the 2D x-y plane to a left-handed coordinate x-z plane. It now uses a right-handed frame and draws directly to the x-y plane.
Added (optional) camera names.
Cameras can report their current projection mode (orthographic vs perspective) and write out their XML representation.
Updated all the examples to use the new info (z-up flag and camera names -- at least for circleV.xml).
Provided const axis to the spatial query and its obstacles.

Just patched a typo -- "GLLight.H" --> "GLLight.h" corrected unix build problem.


fix(route): 607 route labels fix

Welcome to Cryostat! 👋
Before contributing, make sure you have:

[x] Read the contributing guidelines
[x] Linked a relevant issue which this PR resolves
[x] Linked any other relevant issues, PR's, or documentation, if any
[x] Resolved all conflicts, if any
[x] Rebased your branch PR on top of the latest upstream main branch
[x] Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
[x] Signed all commits: git commit -S -m "YOUR_COMMIT_MESSAGE"

Fixes: #607

While we are here, I think we should apply these changes to managed Services too.

And Ingress too.


witness_node --replay-blockchain  # i686 # armv7l

I have a recurring issue on both i686 and ARM processors.
The witness_node will not replay the blockchain or restart from the last block.
I have to delete the chain and start from scratch.
rm object_database/ witness_node_data_dir/blockchain/ witness_node_data_dir/p2p/ witness_node_data_dir/logs/ witness_node_data_dir/db_version -fr
witness_node

Would like to run more ARM nodes. How can I resolve this?

May be due to #492, or some reflection bug like #562 or #575.  Fixes are currently in develop and will be included in the next release.  Feel free to re-open this (or file a new ticket) if you still have problems after upgrading.

Recurring issue --replay-blockchain error on both i686 and ARM processors.

I have to delete the chain and start from scratch.
Build 2.0.160316b

Recurring issue --replay-blockchain error on both i686 and ARM processors.
uname -a
Linux i4p 3.14.65-2-ARCH #1 SMP Sun Mar 27 13:58:54 MDT 2016 armv7l GNU/Linux

I have to delete the chain and start from scratch.
about
{
  "client_version": "2.0.160328",
  "graphene_revision": "3865dd15738e1a1853a28d951eeea5f403c8d06f",
  "graphene_revision_age": "5 days ago",
  "fc_revision": "31adee49d91275cc63aa3a47b3a9e3c826baccca",
  "fc_revision_age": "9 days ago",
  "compile_date": "compiled on Mar 30 2016 at 02:31:06",
  "boost_version": "1.60",
  "openssl_version": "OpenSSL 1.0.2g  1 Mar 2016",
  "build": "linux 32-bit"
}


torch version

Hi there, thank you for sharing your implementation.
I wonder your torch version is 1.3-1.5 or old version such as 1.1?

Hi!
I have tested it on version 1.4 and 1.5. Let me know if it also works on older versions!

Hi, it seems not work in older version-I tried it on version 1.1 and failed.


Implement OS X Cmd+W to close windows, clicking dock icon to open windows

This updates Photon to implement native OS X Window handling (e.g. Cmd+W closes windows, clicking dock icon opens windows, and Cmd+Q quits the app).
This implements what I proposed in #12.

As it is, your code will only work on OS X; on other platforms it will always be hidden in the background, as you simply hide the window on close and the all windows closed event will never fire.
Is it also not true that in most applications when you use cmd-w or the red button that the window IS actually destroyed and when clicking the dock icon a fresh one is created (e.g. with no opened documents)?
It looks as though what you're doing with a simple window could easily be done by putting the new BrowserWindow & loadUrl in a function and call that from both the ready handler & activate handler instead of hiding it.
In your issue comment you mention audio playing in the background; hiding the window is an alternative to playing in a hidden background window, but I don't think it should be the default behaviour.
I would suggest making it a separate example file.


Revise API

Working on some revisions to the API to:

Expose a useful node module for programmatic use
Improve ergonomics for forward, reverse, and forward+reverse reprojections.
Consider replacing some of our CLI code w/ a combination of ndjson-cli and d3-geo-projection
'forward' and 'forward+reverse' correspond roughly to 'use with tippecanoe' and 'use as geojson' (the latter of which we didn't do in wapo, but would likely be useful in general) -- update the docs to reflect this.

This looks solid to me, see my comment in #5 regarding the third bullet point on how to proceed there.

@dereklieu I think this is ready for 👀 .

exposes reproject(options, coordinates)
brings as named projections all the projections provided by d3-geo and de-geo-projection that don't require a parameter
dirty-reproject CLI script (installed with npm install -g)

accepts --forward, --reverse, or both (with --reverse defaulting to 'mercator')

Decided not to go with the d3-geo-projection CLI scripts, because to make this convenient for web-map use, we want to have default translate/scale values set on each of the projections -- much easier to do that programmatically.

Sweet. Looks good. Merging.


Test for rendering nested partials.

I'm assuming this is expected behavior due to already having a test for recursive partials, and that the ruby implementation handles this behavior (from my limited testing).

Makes sense to add a test for this IMHO.


Killed: 9

I'm on Apple silicon running Monterey 12.6 (21G115). The only thing that happens when I try to run codeowners-validator locally is that I get a Killed: 9 message.
 $ codeowners-validator
Killed: 9

Hi @jebl01
Could you tell me how you installed the codeowners-validator? And which version?
CI produces the ARM64 binary too for macOS (with Apple Silicon chips) but I have Intel for now so I was not able to test it.
The issue that you reported looks like the binary was wrongly compressed by upx that I use on CI (I found a related issue https://github.com/upx/upx/issues/446).
Here is a binary that I built from 0.7.4 tag for darwin/arm64 without running the upx tool
codeowners-validator.zip
Let me know if that worked. If yes, I will exclude the upx for arm architectures.

You can also do the same on your local machine:

Checkout this repository: git clone git@github.com:mszostok/codeowners-validator.git
Checkout to v0.7.4 tag: git co v0.7.4
Run goreleaser: goreleaser release --rm-dist --skip-publish --skip-validate --snapshot
NOTE: To run it successfully,  install Go and goreleaser
Use the binary from ./bin/codeowners-validator_darwin_arm64/codeowners-validator.

your zip didn't work (same error), but building locally did!
got this error at the end?!:
⨯ release failed after 24s                 error=post hook failed: failed to run 'upx -9 /Users/jesperblomquist/dev/codeowners-validator/bin/codeowners-validator_darwin_arm64/codeowners-validator': exec: "upx": executable file not found in $PATH

Hey, I was able to build the binary in a Mac M1 and the result is the same
➜  codeowners-validator git:(7f3f5e2)  ./bin/codeowners-validator_darwin_arm64/codeowners-validator
[1]    87227 killed     ./bin/codeowners-validator_darwin_arm64/codeowners-validator

Same here, codeowners-validator version 0.7.4, running on Mac OS X Ventura 13.2, Apple M1 silicon.
I installed via Homebrew:
brew install mszostok/tap/codeowners-validator

But I get:
$ codeowners-validator
Killed: 9

I'm also experiencing this very same bug on Apple silicon chip. No hands on knowledge of go releaser but I feel the config could be updated to something similar to this one which provides a dedicated build entry for the Darwin/arm64

Yeah im getting the same issue on M2

Looks like the file may have been corrupted when UPX was run on it here: https://github.com/mszostok/codeowners-validator/blob/84b4fa2742240c05af8c81185e91947d90222106/.goreleaser.yml#L22

Calling out that this appears to still be an issue on a M2 that installed via brew.