write: fix reserving empty section error

if we copy a elf with a empty section and the sh_addralign(align_start) is not 0, it will return a unaligned offset.

Thanks for the PR. However, it does not look correct. Can you give an in depth explanation so I can better understand the problem? Are you running the elfcopy example? How does the unaligned offset cause an error?

Thanks for the PR. However, it does not look correct. Can you give an in depth explanation so I can better understand the problem? Are you running the elfcopy example? How does the unaligned offset cause an error?

for example, the reserved_len is 64. then the first section's len is 42, align_start is 16. the offset is 64. But next section's len is 0,  align_start is 16. the offset should be 112, but the offset is 106.
you can run elfcopy with this elf https://github.com/lzw3232/test.

Ok, and does that offset of 106 causes problems? It does sound like something that needs fixing, but I want to understand the problem first.

Ok, and does that offset of 106 causes problems? It does sound like something that needs fixing, but I want to understand the problem first.

yes，the 106/16 is not a integer.

Ok, and does that offset of 106 causes problems? It does sound like something that needs fixing, but I want to understand the problem first.

yes，the 106/16 is not a integer.

so it is a unaligned offset.

Yes I understand what an unaligned offset is. What were you doing that caused you to notice that this is a problem?
I see that running elfcopy on it gives an error:
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `106`,
 right: `112`', crates/examples/src/bin/elfcopy.rs:506:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Is that all that you were trying to do, or are you trying to use this code in something else where the unaligned offset causes a problem?

Yes I understand what an unaligned offset is. What were you doing that caused you to notice that this is a problem?
I see that running elfcopy on it gives an error:
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `106`,
 right: `112`', crates/examples/src/bin/elfcopy.rs:506:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Is that all that you were trying to do, or are you trying to use this code in something else where the unaligned offset causes a problem?

I just want to copy a elf with a empty section. This function said that "Returns the aligned offset of the start of the range". But if len is 0, it doesn't call "util::align" just return "self.len". Then I think this is a problem.


🐛  Use new user image properties for image upload

closes TryGhost/Ghost#8521
The image uploader modals in user.hbs used the old image properties instead of coverImage and profileImage.

Changes Unknown when pulling 7009c81b9c20c577e28e1c257b1d52a648f7c15b on AileenCGN:1.0.0-dev/user-image-fix into ** on TryGhost:master**.

@kevinansfield merge?🎊


Switch OwnTracks HTTP to use webhook component

Description:
The purpose is to update owntracks to work with the new auth system and to remove the dependency on legacy_api_password.
Following the discussion in #15376 my understanding is that components that do not support OAuth2 should implement their own authentication solution, so here I see two possibilities:

Use token in the URL setting of the OwnTracks app, similar to the Camera Push, or
Implement a Basic authentication, which the OwnTracks app supports.

My personal preference would be option 2. but I haven't tried to implement it yet, so I need some feedback on whether it's OK to implement Basic Auth in the Owntracks HTTP component, or should it be made to work with a simple token setting, as the proposed change?
I haven't written any tests yet, since this approach might not be desirable
Related issue (if applicable): Partial fix for #15376
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#6863
Example entry for configuration.yaml (if applicable):
device_tracker:
     - platform: owntracks_http
       webhook_id: long-randomly-generated-string

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

We should migrate it to use the new webhook component. Example IFTTT component using webhook component: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/ifttt/init.py#L77-L88

OK. I'll change it in that direction. Thanks for the advice!

I've replaced the config flow with a static webhook_id set in config, however in this new implementation, I think the communication between the webhook and the code is unidirectional, and it will return a 200 status even if there was an error in the owntracks code and that won't be returned to the OwnTracks app.
I tried to make a communication between handle_webhook and handle_event using events, but that got pretty messy, so I scrapped it. Maybe I missed something in the docs, but I don't see any other way for communication between the components other than the event bus?

use helpers/dispatcher.py

Can you convert it back from __init__.py to owntracks_http.py ?

I completely refactored the code. I don't know why I thought I had to keep the webhook handler outside of the setup scanner and can't just access the variables directly. I don't think using partials will be necessary.

Looks great ! Missing docs.

Looks great ! Missing docs.

If you mean updating the ones for the website they're ready, awaiting the approval of the code changes -
https://github.com/home-assistant/home-assistant.io/pull/6863

oh my bad ! perfect. Merge when Travis is 👍

I might look into converting owntracks into a component before the next release and use our new webhook helper.

That sounds good. I have the idea to implement the "friends" feature for the HTTP component, but wanted to get this through before moving forward with it. I found out HTTP is much milder on the battery than MQTT is.

For friend feature, it would be nice if we had Persons

I'll look into this! I'm currently implementing "Persons" using Groups :-)


Issue with HTTP integration to multiple endpoints

Description
The HTTP integration accepts multiple endpoints as a comma separated list. If posting to an endpoint fails, no request is sent to the remaining endpoints.
Steps to reproduce
Create an HTTP integration with two endpoints where the first is invalid (e.g., wrong IP, port, hostname). No data is received by the second endpoint.
Tested with the latest Docker images (v4) using commit a281b17.

Thanks for reporting, I'm looking into this. Next time please report this issue at: https://github.com/chirpstack/chirpstack/.
This issue is related to the ChirpStack source, not to the Docker configuration example.


update @emits decorator to latest decorator spec (Stage 3 at time of writing)

Stage 3 decos are spec'd! 🎉

We're not using the decorator, and its been deleted for now. If we determine it would be useful, we'll add a new one on top of the new decorator format.


400 error on triggering stack analysis

"Generate stack report on manifest" gives 400 error for twitter-core folder, works for workspace but with default maven, analyses dependencies are reported as 0.
Repository: https://github.com/yusuke/twitter4j
tried with https://github.com/yusuke/twitter4j/tree/master/twitter4j-core
/cc @sara-02 You might want to add additional info here.

As we observed, the objects are all empty, the generating pom path is not giving any error, infact when run locally the effective pom is getting successfully build, but after then when the stack analysis is called, the objects are not allocated the correct values, leading to the Manifest file not correct 400 error

@sara-02 I tried with latest version , it works for me i.e Stack analysis for workspace as well as individual manifest's were working fine.
I'll request to try again with proper VSIX cc @samuzzal-choudhury @rootAvish

@invincibleJai I tried with
vscode [ 1.25.1 ]
LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	Fedora
Description:	Fedora release 28 (Twenty Eight)
Release:	28
Codename:	TwentyEight
```  still facing the issue.

fixed with https://github.com/fabric8-analytics/fabric8-analytics-vscode-extension/pull/149
Thanks :)

This issue was moved to openshiftio/openshift.io#4252


Add the .. notation to the documentation

I noticed in this source file the following
  digit  (a digit)
    = "0".."9"

The .. is used here, but it is not mentioned in the documentation's syntax reference.
Is this an oversight, or is the .. notation applicable only to the built-in rules? If the intent is to make it available to everyone, I can write something up for the docs and submit a PR.

Hi Ray,
That is indeed an oversight! A PR adding documentation would be welcome.
On Tue, 28 Feb 2017 at 07:35, Ray Toal<EMAIL_ADDRESS>wrote:

I noticed in this source file
https://github.com/harc/ohm/blob/master/src/built-in-rules.ohm the
following
digit  (a digit)
= "0".."9"
The .. is used here, but it is not mentioned in the documentation's
syntax reference
https://github.com/harc/ohm/blob/master/doc/syntax-reference.md.
Is this an oversight, or is the .. notation applicable only to the
built-in rules. If the intent is to make it available to everyone, I can
write something up for the docs and submit a PR.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/harc/ohm/issues/192, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABDjXkiUJND6RGJVEcz4OX2WWk5q4mOks5rg8BBgaJpZM4MOBbq
.

I started trying to write something up but I am not sure of the existing behavior.
Ohm allows me to write
C {
  c = "abc".."rst"
}

But it seems to treat it as the same as "a".."r".
Also if I try to write:
C {
  c = "a"..last
  last = "x"
}

it says it expects " where the word last appears.
Perhaps if the intent is to allow only one-character terminals in double quotes on each side of the range operator, then maybe Ohm could enforce that before trying to document the feature? I'll be happy to contribute once there's some direction from the project maintainers.

Allowing only terminals is definitely the intended behaviour.
I think the current semantics is that if you have <terminal1>..<terminal2>, any string that is >= to terminal1 and <= terminal2 will match. I know at some point we discussed restricting it to only one-character terminals, but I can't remember what we decided, and unfortunately I can't find any issue related to it or anything in Slack.
@alexwarth, do you remember what we decided? Or any thoughts on whether we should stick with the current semantics?

Looks like the <= / >= does not work for multicharacter terminals (see screenshot)

Oh, you're right. I tested that this morning but I must have done something wrong.
I think we did end up deciding that it should only allow single characters -- that seems to be the assumption in pexprs-eval.js. So the bug here is that we should be throwing an error at grammar instantiation time if both ends of the range are not single character terminals.

Fixed: https://github.com/harc/ohm/commit/cb3fd3b2b98e65374d216a0271be005f8419709c


Change temp file prefix used by BufferedRemoteTaskLogger

This PR fixes a bug that BufferedRemoteTaskLogger cannot upload log files on S3 correctly. The BufferedRemoteTaskLogger writes logs tmp files first before uploading them on S3. The tmp file prefix uses task name, if task name is too long, it cannot create tmp files.
In this PR, the prefix is changed with combination with projectId, workflowName and sessionTime. sessionTime is formatted by ISO-8601 and used as string.
Reported on https://github.com/treasure-data/digdag/issues/729 and assumes #751.

Merged.


Unfortunate autocomplete in yoda condition

From @andy-hanson on June 10, 2017 0:34
Not sure if this is the right repository for this. I'm getting this issue in VSCode in a C# file.
Type:
static bool isLetter(char ch) =>
	'a' <= ch && ch <= 'z';

Get:
static bool isLetter(char ch) =>
	'a' <AccessViolationException= ch && ch <AccessViolationException= 'z';

Copied from original issue: OmniSharp/omnisharp-roslyn#890

Duplicate of https://github.com/OmniSharp/omnisharp-vscode/issues/1521 and https://github.com/OmniSharp/omnisharp-vscode/issues/1553.


Protocol handling layer shared as a separate module

Automattic, the company behind socket.io has separated the protocol from the socket.io framework:

Protocol - https://github.com/Automattic/engine.io-protocol
Protocol Implementation - https://github.com/Automattic/engine.io
Socket.io - https://github.com/Automattic/socket.io

This implementation is by far the best I have found in Java. Since there isn't any active support for socket.io in Vert.x server, besides it uses Netty inside for communication, porting this module could be the best option instead of writing one from scratch. In the worse case scenario, the protocol handling layer could be shared as a separate module, and eventually any Java implementation of socket.io can take advantage of it.
I am starting this conversation to get your guys feedback on that, /cc @igorspasic, @rauchg, @mrniko, @purplefox.

Some things probably could be stripped, like store package. The idea is to have clean java ScoketIo implementation regardless the transportation layer; so all inputs to this would be wrapped in adapters.


loadbalancer module: only one BidirectionalVipRoutes

I setup a topology with one switch connecting three hosts for testing module loadbalancer of floodlight.
One host(<IP_ADDRESS>) is as client and the other two(<IP_ADDRESS>, <IP_ADDRESS>) are as members of pool-01(vip-01 <IP_ADDRESS> is binded)
I try to use commond: curl http://<IP_ADDRESS>/index.html on <IP_ADDRESS> to get html page and it actually can get the page. The problem is that when using curl for one more time to get page, there are always 2 flow entries(one BidirectionalVipRoutes) on flow table, which SHOULD BE 2 MORE flow entries.
This is the flow entries when first curl:
cookie=0xa000000be7d0d7, duration=5.029s, table=0, n_packets=4, n_bytes=781, idle_age=3, tcp,in_port=2,nw_dst=<IP_ADDRESS>,tp_dst=43239 actions=mod_dl_src:12:34:56:78:90:12,mod_nw_src:<IP_ADDRESS>,output:3 cookie=*0xa00000de08a278*, duration=5.041s, table=0, n_packets=7, n_bytes=598, idle_age=3, tcp,in_port=3,nw_src=<IP_ADDRESS>,tp_src=43239 actions=mod_dl_dst:00:00:00:00:00:02,mod_nw_dst:<IP_ADDRESS>,output:2
And after second curl:
cookie=0xa000000be7d0d7, duration=6.372s, table=0, n_packets=4, n_bytes=781, idle_age=4, tcp,in_port=2,nw_dst=<IP_ADDRESS>,tp_dst=43240 actions=mod_dl_src:12:34:56:78:90:12,mod_nw_src:<IP_ADDRESS>,output:3 cookie=0xa00000de08a278, duration=6.376s, table=0, n_packets=7, n_bytes=598, idle_age=4, tcp,in_port=3,nw_src=<IP_ADDRESS>,tp_src=43240 actions=mod_dl_dst:00:00:00:00:00:02,mod_nw_dst:<IP_ADDRESS>,output:2
Moreover, Floodlight console output:
08:31:17.771 ERROR [n.f.s.StaticFlowEntryPusher:New I/O worker #12] Got a FlowRemove message for a infinite timeout flow: OFFlowRemovedVer13(xid=0, cookie=0x00a00000de08a278, priority=32768, reason=2, tableId=0x0, durationSec=13, durationNsec=24000000, idleTimeout=0, hardTimeout=0, packetCount=0x0000000000000007, byteCount=0x0000000000000256, match=OFMatchV3Ver13(in_port=3, eth_type=800, ip_proto=6, ipv4_src=<IP_ADDRESS>, tcp_src=43239)) from switch OFSwitchBase DPID[00:00:8e:0b:7f:6b:41:4a] 08:31:17.773 ERROR [n.f.s.StaticFlowEntryPusher:New I/O worker #12] Got a FlowRemove message for a infinite timeout flow: OFFlowRemovedVer13(xid=0, cookie=0x00a000000be7d0d7, priority=32768, reason=2, tableId=0x0, durationSec=13, durationNsec=16000000, idleTimeout=0, hardTimeout=0, packetCount=0x0000000000000004, byteCount=0x000000000000030d, match=OFMatchV3Ver13(in_port=2, eth_type=800, ip_proto=6, ipv4_dst=<IP_ADDRESS>, tcp_dst=43239)) from switch OFSwitchBase DPID[00:00:8e:0b:7f:6b:41:4a]
Is that ERRORs happen because the cookie of flow entry should be UNIQUE(two flow entries after first curl has the same cookies as the two after second curl)
Environment: Debian7.8, OVS 2.3.1, Floodlight master

@woniu17 The cookie isn't the problem. The cookie is just an ID you can give a flow to help you reference one or more flows more easily later. For example, the SFP uses a set cookie ID for all SFP flows that allow the SFP to detect when a flow it inserted was removed by the flow removed message.
The problem is that the LB is presently designed to balance between multiple source hosts between multiple destination hosts. If you use the same source again, the LB isn't presently smart enough to detect the difference. So, it removes the old flows and adds the new ones.
This is an easy fix though I think. The string key the LB uses to identify flows in the SFP does not include the client source port as the name (only the target, which is 80 in both cases for you). If we include the source port too, it'll fix the problem methinks. What say you?

Thanks! I mistook client.targetPort as the port the client used. I think if it would be understood well to make vipId followed by targetPort.
"inbound-vip-"+ member.vipId+"-client-"+client.ipAddress+"-port-"+client.targetPort+"-srcswitch-"+path.get(0).getNodeId()+"-sw-"+sw;
"inbound-vip-"+ member.vipId+"-port-"+client.targetPort+"-client-"+client.ipAddress+"-srcswitch-"+path.get(0).getNodeId()+"-sw-"+sw;
The LB will not work well if the same source simultaneously takes one more HTTP requests, which browser Firefox does. I think that is because the old flows are alternated by new flows again and again. Now I know it would be solved if I include the source port into SFP's entry name.
Thanks, again!

@woniu17 I agree. If you want to make the change and issue a pull request, the help would be appreciated! Make sure you run the unit tests afterwards to ensure nothing broke.

@woniu17 https://github.com/floodlight/floodlight/pull/592


Fix resolve_file_name called twice to the same file

We identified a bug where the resolve_file_name is called twice to the same file.
If we have a resolve file name function like suggested in the docs:
file_name = Path.basename(file.file_name, Path.extname(file.file_name))

"#{version}_#{file_name}"

If that function is called twice for the same file, instead of having "thumb_filename.jpg", we end having "thumb_thumb_filename.jpg".
The resolve_file_name is called first in the abstract logic: https://github.com/elixir-waffle/waffle/blob/c781d5a7e7058d297783669ad1a830bd8928c73d/lib/waffle/actions/store.ex#L134
Then again here. The code change I'm proposing basically imitates the AWS adapter that just call file.file_name:
https://github.com/elixir-waffle/waffle/blob/c781d5a7e7058d297783669ad1a830bd8928c73d/lib/waffle/storage/s3.ex#L144

@petermueller We're running this fix in production for a couple of months. I think it's good to do.
We could merge this one first, release a patch. Then merge the Goth support upgrade as minor release.
What do you think?

@ulissesalmeida, sorry, let me take a look this weekend

I'll check why it's failing later

Ok ☺
I was looking through it a little bit this weekend and I'm a little confused. It seems like path_for just combines the result of the storage_dir and filename callback so if there were an issue it would seem like it's with those, as far as I can tell at least.

@petermueller All good now. I had to change how we set up the test to reflect better the reality. The file name is resolved before the GCS calls.


fix(predictions): Serialize the dispatch of web socket events

Issue #

Some customer Liveness sessions using the Amplify iOS SDK fail midway through the session with the error:
InvalidSignatureException: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.

Description

Video and client events over the web socket from different threads. If a video and client event are sent at identical time, prior signatures may get mixed up, causing an invalid signature event. This PR introduces a change to use a serial dispatch queue to send web socket events.
General Checklist

[ ] Added new tests to cover change, if needed
[x] Build succeeds with all target using Swift Package Manager
[x] All unit tests pass
[x] All integration tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[x] PR title conforms to conventional commit style
[ ] New or updated tests include Given When Then inline code documentation and are named accordingly testThing_condition_expectation()
[ ] If breaking change, documentation/changelog update with migration instructions

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

Codecov Report
Attention: Patch coverage is 0% with 30 lines in your changes are missing coverage. Please review.

Project coverage is 68.19%. Comparing base (358699c) to head (353691d).
Report is 4 commits behind head on main.

Files
Patch %
Lines

...sPlugin/Liveness/Service/FaceLivenessSession.swift
0.00%
30 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3558      +/-   ##
==========================================
- Coverage   68.47%   68.19%   -0.28%
==========================================
  Files        1077     1077
  Lines       36282    36287       +5
==========================================
- Hits        24844    24747      -97
- Misses      11438    11540     +102

Flag
Coverage Δ

API_plugin_unit_test
67.50% <ø> (ø)

AWSPluginsCore
66.90% <ø> (ø)

Amplify
48.10% <ø> (-0.02%)
:arrow_down:

Analytics_plugin_unit_test
81.16% <ø> (ø)

Auth_plugin_unit_test
78.92% <ø> (-0.20%)
:arrow_down:

CoreMLPredictions_plugin_unit_test
59.44% <ø> (ø)

DataStore_plugin_unit_test
81.32% <ø> (-1.13%)
:arrow_down:

Geo_plugin_unit_test
70.75% <ø> (ø)

Logging_plugin_unit_test
62.87% <ø> (ø)

Predictions_plugin_unit_test
37.10% <0.00%> (-0.06%)
:arrow_down:

PushNotifications_plugin_unit_test
87.13% <ø> (ø)

Storage_plugin_unit_test
77.61% <ø> (ø)

unit_tests
68.19% <0.00%> (-0.28%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Revert Implement winio.GetFileStandardInfo FileInfo commits

Addresses issue mentioned in https://github.com/moby/moby/pull/42307

@TBBle @awmirantis @thaJeztah

Thank you 🙏
Was it a clean revert? (making sure if reviewers need to pay extra attention to the changes)

Was it a clean revert? (making sure if reviewers need to pay extra attention to the changes)

@thaJeztah yep! just git reverted and that was it.


The timestamp of capture name vs 1st split time name for small files

The Phenomenon;
The timestamp of display unmatch capturedata time.
See attached picture.
Opertion:

Did capture(QUICK).
Menu-[FILES]-"FIlename"
Select [udp]
Select [split_1sec]

Add information
When selected [tcp] ot [port 0], happend same phenomenon.
This phenomenon is happen FW3300 and FW3392.
20160928_isuue_timestamp_unmatch.zip

further clarification. the split time as shown in the GUI is not matching the first packet in the downloaded PCAP.

the time in capture stream name is based on capture start time.
time split is based on 1st captured packet.
if there is large delay between capture start to first captured packet, then the GUI can be confusing as the first time split != capture start time. Need to updated split time output to start from capture start time (not 1st captured packet)

narrowed down to the spliter reading the previous captures last chunk, and using that as the starting time stamp.
in this example capture size was 3 chunks, with the length likely wrong for some reason.

probably related to not cycling though the stream indexs. e.g. the previous chunnk has the same streamindex (because its not cycling).
it now cycles though all the stream indexes


[Bug] [Jdbc] NullPointerException of jdbc engine connection clickhouse

Search before asking

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

Linkis Component
linkis-cg-engineConnplugin
What happened + What you expected to happen
Exception in thread "main" java.lang.NullPointerException
	at java.util.Hashtable.put(Hashtable.java:460)
	at org.apache.linkis.manager.engineplugin.jdbc.ConnectionManager.createDataSources(ConnectionManager.java:140)
	at org.apache.linkis.manager.engineplugin.jdbc.ConnectionManager.main(ConnectionManager.java:311)

        Properties props = new Properties();
        props.put("driverClassName", supportedDBs.get(dbType));
        props.put("url", url);
        props.put("maxIdle", 5);
        props.put("minIdle", 0);
        props.put("maxActive", 20);
        props.put("initialSize", 1);
        props.put("testOnBorrow", false);
        props.put("testWhileIdle", true);
        props.put("validationQuery", this.supportedDBsValidQuery.get(dbType));

props.put("validationQuery", this.supportedDBsValidQuery.get(dbType));  put with null
val JDBC_SUPPORT_DBS_VALIDATION_QUERY = CommonVars("wds.linkis.jdbc.support.dbs.validation.query", "mysql=>SELECT 1,postgresql=>SELECT 1,oracle=>SELECT 1 FROM dual,hive2=>SELECT 1,presto=>SELECT 1")

for wds.linkis.jdbc.support.dbs.validation.query, new dbtype should with default value or  without put props.put("validationQuery", this.supportedDBsValidQuery.get(dbType))
Relevent platform
linkis-1.1.3
Reproduction script
none
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

can i  fix it ?

can i fix it ?

The community has already followed up to fix this problem. Welcome to solve other unresolved issues

has been fix in  #2196


add dz_bottom and dz_top to command line arguments

PULL REQUEST
Purpose and Content
Adds dz_bottom and dz_top for grid stretching to command line arguments
Benefits and Risks
Linked Issues
PR Checklist

[ ] This PR has a corresponding issue OR is linked to an SDI.
[x] I have followed CliMA's codebase contribution and style guidelines OR N/A.
[x] I have followed CliMA's documentation policy.
[x] I have checked all issues and PRs and I certify that this PR does not duplicate an open PR.
[x] I linted my code on my local machine prior to submission OR N/A.
[x] Unit tests are included OR N/A.
[x] Code used in an integration test OR N/A.
[x] All tests ran successfully on my local machine OR N/A.
[x] All classes, modules, and function contain docstrings OR N/A.
[x] Documentation has been added/updated OR N/A.

bors r+


the implement of repair the error replications of the volume

based on the gRPC function VolumeServer.ReplicateVolume()，this future implementing the function of repairing a error replication of the volume

Good job! Thanks!

Please move changes related to weed/topology/replication_health_checker.go to a different PR.
Fix build issues.

btw: for health check, I am thinking to keep master/topology logic simple, but use shell commands to apply different administrative operations.


Support format for handlebars file

although VS Code recognize that the markup is indeed handlebars, it is unable to format it.
So format code option does nothing

It is currently just not implemented.

@bpasero thank you

@bpasero is it on the roadmap though?

@gpluta not on the immediate roadmap and it depends on contributions from the community.

@egamma Thanks for clarifying!

Ember Handlebar templates are having very bad format in VSCode , that is only one thing i am going back to atom.
All the existing extensions can't do it well too. Would be very nice vscode look into it. Over a year now.

Duplicate of #7011 / #32916 (I know this issue is older, but those two issue seem to have more relevant information on them)


Allow copy

Enable long press to copy words to clipboard

Thanks for bringing this issue up. I'm this functionality isn't already present

This feature will be added to the next update, which should go out in a couple days.


Fix model-index structure and misc minor fixes

This PR has multiple changes, including:

Allowing to push an unversioned whl name (recall that repos in HF have whl files with any version in the name, and the extraction happens differently for those).
Add the task to the metric name
Change the model-index in the metadata to match latest specification.

This will enable showing a "Evaluation Results" section in the model card

FYI @julien-c

Yay! 👍


Add Leaflet backend to enable custom map providers e.g. OpenStreetMap

First of all: Thanks for the great Django plugin! Extending your code was straight forward, although I have never written custom Django widgets myself.
The existing JS code was not modified, to maintain backward compatibility. Instead there was a new settings.py parameter introduced: GEOPOSITION_BACKEND. Only the JS and CSS files needed for the specified backend will be loaded. While google is the default backend, there is no need for existing users to change their configuration files.
To use the new backend add GEOPOSITION_BACKEND = 'leaflet' to settings.py. This will load Leaflet to display the default OpenStreetMap. As Leaflet is provider agnostic, you could use any other map provider from the following list: http://leaflet-extras.github.io/leaflet-providers/preview
Here is an example configuration displaying satellite imagery with some more custom map options:
GEOPOSITION_BACKEND = 'leaflet'
GEOPOSITION_MAP_OPTIONS = {
    'url': 'https://server.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer/tile/{z}/{y}/{x}',
    'attribution': 'Tiles © Esri — Source: Esri, i-cubed, USDA, USGS, AEX, GeoEye, Getmapping, Aerogrid, IGN, IGP, UPR-EGP, and the GIS User Community',
    'dataZoom': 15,  # zoom for records with geposition set already
    'initialZoom': 9,  # zoom for records without geoposition set
    'initialCenter': [51, 13.45]  # center for records without geoposition set
}

If you are OK with the proposed architecture, I'll add documentation and examples to the readme accordingly.

Looks like PR #86 needs to be merged to fix the CI build errors.


Add support for .cube LUTs

Previous forum discussion: https://forum.babylonjs.com/t/support-for-cube-luts/32630/2
Right now colorGradingTexture only supports .3dl file.
The problem is very simple: a lot of tools (e.g. Davinci Resolve) can only export .cube files. It'd be nice to have first class support for that format to avoid extra conversion. Also, after hours of searching, I found no open-source utility to convert between the two formats, so I'm not sure that such conversion is even available.
An example .cube loader can be found in the amazing postprocessing library: https://github.com/pmndrs/postprocessing/blob/main/src/loaders/LUTCubeLoader.js

Still something I need 😇

Would you want to contribute a loader for it ?

Not right now, but if nobody else does it in like two months or so, then I will.

14 days? Seriously?
On Sat, 30 Mar 2024, 02:19 github-actions[bot], @.***>
wrote:

This issue has been automatically staled because it has been inactive for
more than 14 days. Please update to "unstale".
—
Reply to this email directly, view it on GitHub
https://github.com/BabylonJS/Babylon.js/issues/14090#issuecomment-2027840245,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKATL7ENCS7E7WYJOXV6LLY2YAK7AVCNFSM6AAAAAA22D5CLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXHA2DAMRUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Agree it is too short, I ll change it tonight.

https://forum.babylonjs.com/t/add-support-for-cube-luts/52134

Does anyone know how to apply the cube file format to a video? Just overlay a filter on the  tag? I really need an example.


Failed on run the third step

I successfully finished the first two steps. When I did "roslaunch astra_launch astra.launch", there was a warning in the terminal:
Warning: USB events thread - failed to set priority. This might cause loss of data....
As a result, in Rviz, I cannot receive the data from the following topics:
/camera/rgb/camera/depth_registered/sw_registered/image_rect
/camera/rgb/camera/depth_registered/sw_registered/image_rect_raw
/camera/rgb/camera/rgb/image_raw
/camera/rgb/camera/rgb/image_rect_color

@xiaoyuchhusky I am receiving the following error when I try to perform the first two steps.
aswin@aswin-laptop:~/camera$ catkin_make
Base path: /home/aswin/camera
Source space: /home/aswin/camera/src
Build space: /home/aswin/camera/build
Devel space: /home/aswin/camera/devel
Install space: /home/aswin/camera/install
####
#### Running command: "make cmake_check_build_system" in "/home/aswin/camera/build"
####
####
#### Running command: "make -j8 -l8" in "/home/aswin/camera/build"
####
[  3%] [  7%] Built target astra_camera_gencfg
[ 11%] Built target astra_usb_reset
Performing update step for 'astra_openni2'
[ 11%] Built target _astra_camera_generate_messages_check_deps_GetSerial
[ 22%] [ 22%] [ 25%] Built target astra_camera_generate_messages_lisp
Built target astra_camera_generate_messages_py
Built target astra_camera_generate_messages_cpp
[ 25%] Built target astra_camera_generate_messages
Already on 'orbbec_ros'
Your branch is up-to-date with 'origin/orbbec_ros'.
[ 29%] Performing configure step for 'astra_openni2'
no need to configure
[ 33%] Performing build step for 'astra_openni2'
make[3]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
[ 37%] Performing install step for 'astra_openni2'
[ 40%] Completed 'astra_openni2'
[ 51%] Built target astra_openni2
Linking CXX shared library /home/aswin/camera/devel/lib/libastra_wrapper.so
/usr/bin/ld: cannot find -lOpenNI2Orbbec
collect2: error: ld returned 1 exit status
make[2]: *** [/home/aswin/camera/devel/lib/libastra_wrapper.so] Error 1
make[1]: *** [ros_astra_camera/CMakeFiles/astra_wrapper.dir/all] Error 2
make: *** [all] Error 2
Invoking "make -j8 -l8" failed


Ping automatically changes the port to 1434. I used the connection string with Port 1433. I can connect but when I ping it is getting timedout.

Describe the bug
@LuisBosquez
When I tried to connect to SQL Server, it got connected. Unable to ping or query the tables.
connString := fmt.Sprintf("server=%s;user id=%s;password=%s;port=%d;",
MES_DB_SERVER, MES_USERNAME, MES_PASSWORD, MES_PORT)
fmt.Println(connString)
//conS := fmt.Sprintf("sqlserver://%s:%s@%s:$d/")
// create connection pool
dbcon, err = sql.Open(MES_DB_TYPE, connString)
if err != nil {
log.Fatal("Error creating connection pool: " + err.Error())
}
log.Printf("Connected!\n")
When I ping I am getting error
ctx := context.Background()
err := dbcon.PingContext(ctx)
if err != nil {
	log.Fatal("Error pinging DB : ", err.Error())
}

If you see the error message it says udp with 1434. I checked TCP is enabled and restarted the db several times. Any help will be appreciated.
Error message:
PS C:\Users\g_nan\Documents\Goworkspace\DatabaseSQLGo> go run main.go
server=NANDU\SQLEXPRESS;user id=SA;password=Sapwd1298;port=1433;
2023/12/22 23:27:48 Connected!
2023/12/22 23:28:03 Error pinging DB : unable to get instances from Sql Server Browser on host NANDU: read udp [fe80::c635:3f67:afd0:eaef%Ethernet 3]:63108->[fe80::c635:3f67:afd0:eaef%Ethernet 3]:1434: i/o timeout
exit status 1
If you are seeing an exception, include the full exceptions details (message and stack trace).
Exception message:
PS C:\Users\g_nan\Documents\Goworkspace\DatabaseSQLGo> go run main.go
server=NANDU\\SQLEXPRESS;user id=SA;password=Sapwd1298;port=1433;
2023/12/22 23:27:48 Connected!
2023/12/22 23:28:03 Error pinging DB : unable to get instances from Sql Server Browser on host NANDU: read udp [fe80::c635:3f67:afd0:eaef%Ethernet 3]:63108->[fe80::c635:3f67:afd0:eaef%Ethernet 3]:1434: i/o timeout
exit status 1

Stack trace:

To Reproduce
Include a complete code listing that we can run to reproduce the issue.
Partial code listings, or multiple fragments of code, will slow down our response or cause us to push the issue back to you to provide code to reproduce the issue.
Expected behavior
A clear and concise description of what you expected to happen.
Further technical details
SQL Server version: express edition
Operating system: windows 11
Table schema
Additional context
Add any other context about the problem here.

same issue for me, I've set port to 1433
read udp <IP_ADDRESS>:49834-><IP_ADDRESS>:1434: i/o timeout

Same issue


Adding a forward proxy AuTest.

This adds a basic forward proxy test.

This will start passing once the following revert PR is merged in:
https://github.com/apache/trafficserver/pull/8486

WIth this PR is #8449 also needed?

[approve ci autest]

[approve ci autest]


Upgrade to sbt 1.0.2

This updates to sbt 1.0.2 which required updating all the plugins and changing a few bits and pieces. It also fixes the mostly busted publishing process. Thanks @eed3si9n for the help and encouragement.

Codecov Report

Merging #68 into series/0.6.x will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           series/0.6.x      #68   +/-   ##
=============================================
  Coverage         64.51%   64.51%
=============================================
  Files                 9        9
  Lines               248      248
  Branches              8        8
=============================================
  Hits                160      160
  Misses               88       88

Continue to review full report at Codecov.

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


[Concurrent Segment Search] shard_min_doc_count and shard_size should not be evaluated at the slice level

Subtask for https://github.com/opensearch-project/OpenSearch/issues/7357 to focus on the test failures related to shard size parameter:
REPRODUCE WITH: ./gradlew 'null' --tests "org.opensearch.search.aggregations.bucket.TermsShardMinDocCountIT.testShardMinDocCountSignificantTermsTest" -Dtests.seed=A749B9CB2092798B -Dtests.locale=en-IE -Dtests.timezone=Europe/Madrid -Druntime.java=17

java.lang.AssertionError:
Expected: <0>
     but: was <1>
Expected :<0>
Actual   :<1>
<Click to see difference>

	at __randomizedtesting.SeedInfo.seed([A749B9CB2092798B:D251D3457B327719]:0)
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
	at org.junit.Assert.assertThat(Assert.java:964)
	at org.junit.Assert.assertThat(Assert.java:930)
	at org.opensearch.search.aggregations.bucket.TermsShardMinDocCountIT.testShardMinDocCountSignificantTermsTest(TermsShardMinDocCountIT.java:103)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)

REPRODUCE WITH: ./gradlew 'null' --tests "org.opensearch.search.aggregations.bucket.TermsShardMinDocCountIT.testShardMinDocCountTermsTest" -Dtests.seed=A749B9CB2092798B -Dtests.locale=en-IE -Dtests.timezone=Europe/Madrid -Druntime.java=17

java.lang.AssertionError:
Expected: <0>
     but: was <2>
Expected :<0>
Actual   :<2>
<Click to see difference>

	at __randomizedtesting.SeedInfo.seed([A749B9CB2092798B:BD5353BCAD8763C8]:0)
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
	at org.junit.Assert.assertThat(Assert.java:964)
	at org.junit.Assert.assertThat(Assert.java:930)
	at org.opensearch.search.aggregations.bucket.TermsShardMinDocCountIT.testShardMinDocCountTermsTest(TermsShardMinDocCountIT.java:169)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	a

 - org.opensearch.search.aggregations.bucket.ShardSizeTermsIT.testShardSizeEqualsSizeDouble
 - org.opensearch.search.aggregations.bucket.ShardSizeTermsIT.testShardSizeEqualsSizeString

@sohami @reta @andrross Would like to get your input on this. It seems difficult to completely preserve the behavior between concurrent and non-concurrent search cases here.

I didn't understand what you mean my it could grow unbounded. For sequential case as well, the shard_size limit is applied after document collection is done on the shards and before returning the output (i.e. in buildAggregation).

You are right that at the shard level the same bounds would still be applied, so from the coordinator perspective concurrent and non-concurrent search would look the same. However, the unbounded growth I am concerned about here is basically the size of the priority queue at the slice level, which is also the number of buckets being returned at the slice level. Today this is bounded by the shard_size parameter, but if we ignore that then each slice would return a bucket for every single ordinal, which looks like a serious scaling issue to me. I think this is the same reason why shard_size parameter exists at all instead of just returning every single bucket to the coordinator and doing the size bound there.


fix(parser) Resolve issue with missing TS property

Using highlightElement with version 10.7.2 causes the following TypeScript build error:
error TS2339: Property 'highlightElement' does not exist on type 'HLJSApi'.

Changes
fix(parser) Resolves issue with missing TypeScript property
Checklist

[x] Added markup tests, or they don't apply here because only modified types definitions
[x] Updated the changelog at CHANGES.md

Fixed with release of 10.7.3.

Awesome, thanks!


Fixing config links in the AWS Lambda docs

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2021-12-06T12:52:25.043+0000

Duration: 4 min 33 sec

Commit: f9ec996032805ab16b6194de676503476c961c33

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark test.

run compatibility tests : Run the JDK Compatibility test.

run integration tests : Run the APM-ITs.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


Custom Require variable

I'm currently using tailor with webpack which means I'm not using require as it's supposed to work. Basically, I'm just using it to load the file if it isn't already loaded. My problem is that the "require" variable is causing conflicts. Would it be possible to have an option to change the "require" variable here: https://github.com/zalando/tailor/blob/ffe52cafe0a5b47daf4ad773037e8b9fae5d54e2/index.js#L34
I've replaced the line with: return new Buffer(memoizedDefinition + ${pipeInstanceName} = new Pipe(${options.amdLoaderName || 'require'})\n);
My amd loader file for reference:
(function (window, undefined) {
	let loaded = {};
	function loadModule(src, el) {
        // need to add new script to the browser
        el = window.document.createElement('script');
        el.src = src;
        window.document.head.appendChild(el);
    }

	function req(dependencyNames) {
		if (!loaded[dependencyNames[0]]) {
			loaded[dependencyNames[0]] = true;
			loadModule(dependencyNames[0]);
		}
    }
	window['tailor_require'] = req;
}(this));

@SimeonC Sorry for the delay. missed this issue.
I got your concern. But you could totally send your own AMD loader which satisfies the API of require.js
Check this example on how you can modify the same here https://github.com/zalando/tailor/blob/master/examples/multiple-fragments-with-custom-amd/index.js#L10

No problems, thanks for getting back to me. I did this while trying to workaround using React and Webpack and thought it was conflicting with hot-loading js files - I later realised that webpack doesn't use the window.require variable anyway so it's not really an issue.
I guess thinking back what I was trying to do probably was going to cause even more issues than it solved.


Fix around session detail behavior.

Description

Fix speaker icon.
Hide X link button when link is empty.
Use root Navigator to show session detail page.

Fixes #issue_number
Type of change
Please delete options that are not relevant.

[ ] New feature
[x] Bug fix
[ ] Refactor
[ ] Style
[ ] Documentation
[ ] CI/CD
[ ] Other

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.
Provide instructions so we can reproduce.

Checklist

[x] My code follows the style guidelines of this project.
[x] My code has been formatted with flutter format lib.
[x] My code has been fixed with dart fix --apply lib.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

セッション詳細のナビゲーション方法を変更した経緯：

Router.go を使った遷移の場合、Router.pop を使って戻ろうとしてもクエリパラメータの情報が保持されない
iOSで戻るジェスチャーが効かない（ドロワーの判定に吸われてしまう）


auto-targeting problem on CN

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
CN
FGA build number
1501
Describe the bug
see https://github.com/Fate-Grand-Automata/FGA/issues/861#issuecomment-919146804

detecting danger failed
Video
add lator
Device model
Emulator
Android version
7
Screen size
No response
RAM
No response

Video
add lator

Video is not really needed for this, but, can you atleast post a full-screen screenshot of both servant and danger cases?

https://b23.tv/96vwzi
sorry for late
Screenshot on the way

Can you give screenshots without the emulator border? I'm not able to precisely crop out the border sadly.
Your emulator should have an option to take screenshots in it.
I tried taking images from that video but the quality turned out lower that way.

danger left 1

all servant

Try this build: https://github.com/Fate-Grand-Automata/FGA/actions/runs/1273027821

Seems no problem


New songs to add - July 2018

Hello,
More songs in English & Tamil to be added to your app. Really appreciate your help on this.
Looking to see these songs soon.
New song - July 2018.zip
God bless you :)

Hi,
Thanks for the new songs
We will add these songs too.
Thanks

Noted.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mcruncher/worshipsongs-db-dev/issues/250#event-1746835940,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkkX-Ko90Mz8u6cuzQLDcDQCtfBPjqB7ks5uJVlegaJpZM4VIsGf
.

--
Cheers,
Seetha


Feature/av2 401/unit test for chat service

Jira - https://intersective.atlassian.net/browse/AV2-401

PR still not ready for code review


Import wallet from seed

Would it be possible to add the ability to import a wallet from seed?

Sorry for the delay.
Does "seed" mean this? -> new MnemonicJS(words).toHex();


Sync does not work with crash-looping container anymore (since 4.13)

What happened?
I upgraded from 4.12 to 4.13 today. Running devspace dev does sync my golang application to the container. Since the new version 4.13 the sync breaks if the container is in a crash-loop due a syntax error.
In 4.12 I was able to fix the code issue and devspace dev synced  the change (magically?) to the crash-looping container and restarted it with the fixed version. Now I need to re-run the devspace dev command in such case and wait since devspace can't sync the fixed code inside the crashing container?
Logs:
[sc1-backend-api]
[sc1-backend-api] ############### Restart container ###############
[sc1-backend-api]
[sc1-backend-api] # syscore.one/backend/api/pkg/api
[sc1-backend-api] api/pkg/api/project.go:226:1: syntax error: unexpected EOF, expecting }
[error]  Error restarting sync: Error selecting pod: Pod 'sc1-backend-api-65c45967f4-d5qbv' has critical status 'Error'

To get more information about this pod's status, run: kubectl describe pod sc1-backend-api-65c45967f4-d5qbv
[error]  Will try again in 5 seconds
[error]  Error restarting sync: Error selecting pod: Pod 'sc1-backend-api-65c45967f4-d5qbv' has critical status 'CrashLoopBackOff'

To get more information about this pod's status, run: kubectl describe pod sc1-backend-api-65c45967f4-d5qbv
[error]  Will try again in 5 seconds
[error]  Error restarting sync: Error selecting pod: Pod 'sc1-backend-api-65c45967f4-d5qbv' has critical status 'CrashLoopBackOff'

To get more information about this pod's status, run: kubectl describe pod sc1-backend-api-65c45967f4-d5qbv
[error]  Will try again in 5 seconds

Before 4.13 the logs showed me the issue, I was able to fix the code and the upload work fine and the container got restarted with a working version.
Now I can fix the syntax error but the container keeps crashing since the sync seems no longer to work.
What did you expect to happen instead?
devspace dev should be able to sync code inside a crash looping container as it worked in 4.12.
I downgraded back to 4.12 and tested the same file change, and it worked:
[sc1-backend-api] ############### Restart container ###############
[sc1-backend-api]
[sc1-backend-api] # syscore.one/backend/api/pkg/api
[sc1-backend-api] api/pkg/api/project.go:226:1: syntax error: unexpected EOF, expecting }
[sc1-backend-api]
[sc1-backend-api] Container exited with 2. Will restart in 7 seconds...
[sc1-backend-api]
[sc1-backend-api]
[sc1-backend-api] ############### Restart container ###############
[sc1-backend-api]
[sc1-backend-api] 2020-06-30T17:51:23.85405259Z [DEBUG]: /app/shared/sentry/client.go:24 Sentry has been activated.

How can we reproduce the bug? (as minimally and precisely as possible)
Local Environment:

DevSpace Version: 4.13.0
Operating System: mac
Deployment method: helm | kubectl apply

Kubernetes Cluster:

Cloud Provider: other
Kubernetes Version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.5", GitCommit:"e6503f8d8f769ace2f338794c914a96fc335df0f", GitTreeState:"clean", BuildDate:"2020-06-27T00:38:11Z", GoVersion:"go1.14.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:43:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

/kind bug

@BirknerAlex thanks for reporting this issue! Good catch, this problem occurs because we renamed the sync helper binary to devspacehelper and the restart script now thinks the sync helper binary is missing and fails instead of just restarts the container.

@BirknerAlex should be fixed with v4.13.1

@FabianKramm Thanks for the fast fix. Tested the new release, works fine! :heart:


enh: implement metadata aggregator for asset summary

This PR implements the computation of asset summary for a dandiset to this library.

slight changes to regexes required pattern updates (so new schema will be released)

addresses part 1 of https://github.com/dandi/dandi-api/issues/337
will file a PR on API to use this.

Let's proceed!


[Event Request] PAGE 234 "Apply Employee Entries" OnBeforePostDirectApplication

local procedure PostDirectApplication(PreviewMode: Boolean)
var
    .
    .
    .

IsHandled: Boolean;

   begin

IsHandled := false;
OnBeforePostDirectApplication(Rec, PreviewMode, IsHandled);
if IsHandled then
exit;

    if CalcType = CalcType::Direct then begin
    .
    .
    .

[IntegrationEvent(false, false)]
local procedure OnBeforePostDirectApplication(var EmplLedgerEntry: Record "Employee Ledger Entry"; PreviewMode: Boolean; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Add test cases and refactor code

Codecov Report

Merging #263 (4f94021) into master (759e5d6) will increase coverage by 0.11%.
The diff coverage is 53.84%.

@@             Coverage Diff              @@
##             master     #263      +/-   ##
============================================
+ Coverage     59.97%   60.09%   +0.11%
- Complexity      750      760      +10
============================================
  Files           138      140       +2
  Lines          2856     2887      +31
  Branches        373      375       +2
============================================
+ Hits           1713     1735      +22
- Misses         1015     1022       +7
- Partials        128      130       +2

Impacted Files
Coverage Δ

...in/java/seedu/address/logic/parser/ParserUtil.java
31.00% <0.00%> (+0.70%)
:arrow_up:

...ddress/logic/parser/task/AddTaskCommandParser.java
0.00% <0.00%> (ø)

...ss/logic/parser/task/ArchiveTaskCommandParser.java
0.00% <0.00%> (ø)

...dress/logic/parser/task/FindTaskCommandParser.java
0.00% <0.00%> (ø)

.../logic/parser/task/UnarchiveTaskCommandParser.java
0.00% <0.00%> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
76.85% <0.00%> (ø)

...java/seedu/address/model/VersionedAddressBook.java
40.00% <ø> (ø)

...ress/model/task/TaskContainsKeywordsPredicate.java
34.78% <0.00%> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
12.50% <0.00%> (+1.38%)
:arrow_up:

src/main/java/seedu/address/ui/TaskCard.java
0.00% <0.00%> (ø)

... and 8 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


validity checking of detected secrets ?

I'm submitting a ...

[ ] bug report
[X] feature request

Just a quick question, are there any plans to implement validity checking of detected secrets ?

Hi @Gby56, could you please explain what you mean by "validity checking of detected secrets"?

Hi ! Something like Trufflehog's checks, most of them seem to be pure HTTP requests to use the token and see if it's still valid
https://github.com/trufflesecurity/trufflehog/blob/main/pkg/detectors/slack/slack.go#L91

@Gby56 detect-secrets does do secret verification: https://github.com/Yelp/detect-secrets/blob/master/docs/plugins.md#Verified-Secrets
Not all the plug-ins have implemented it, not as many as Trufflehog, but it wouldn't be very difficult for people to add more; the plugin framework supports it.

Thank you @gpflaum for helping out answering this issue :)

Thank you both ! :)


Error and Failure in Creating entry.worker.ts during Remix PWA Upgrade

Hello,
I encountered an issue while trying to upgrade Remix PWA by executing npx remix-pwa sw. The process advises that this command is soon to be deprecated and suggests using npx remix-pwa@latest init instead. However, following through with the instructions leads to a failure in creating the entry.worker.ts file, accompanied by an error.
Here is the error message when executing npx remix-pwa sw:
$ npx remix-pwa sw
This command is getting deprecated soon. Please use `npx remix-pwa@latest init` instead.
✔ Is this a TypeScript or JavaScript project? Pick the opposite for chaos! · ts
✔ Do you want to integrate workbox into your project? (y/N) · false
✔ Do you want to utilise precaching in this project? (y/N) · false
✔ What features of remix-pwa do you need?  (Y/n) · true
⠋ Integrating Service Worker...
file:///Users/tsuyoshihiguchi/develop/mulligan/repositories/front-end/node_modules/@remix-pwa/dev/dist/cli/getPkgVersion.js:5
    return pkgJson[0].version;
                      ^

TypeError: Cannot read properties of undefined (reading 'version')
    at getPkgVersion (file:///Users/tsuyoshihiguchi/develop/mulligan/repositories/front-end/node_modules/@remix-pwa/dev/dist/cli/getPkgVersion.js:5:23)
    at createPWA (file:///Users/tsuyoshihiguchi/develop/mulligan/repositories/front-end/node_modules/@remix-pwa/dev/dist/cli/create.js:152:74)
    at async Module.init (file:///Users/tsuyoshihiguchi/develop/mulligan/repositories/front-end/node_modules/@remix-pwa/dev/dist/cli/commands.js:16:5)
    at async Module.run (file:///Users/tsuyoshihiguchi/develop/mulligan/repositories/front-end/node_modules/@remix-pwa/dev/dist/cli/run.js:261:13)
    at async cli (file:///Users/tsuyoshihiguchi/develop/mulligan/repositories/front-end/node_modules/remix-pwa/dist/cli.js:4:5)

Node.js v18.18.0

Following the suggestion to use npx remix-pwa@latest init, I encountered another issue:
$ npx remix-pwa@latest init
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y
error: unknown command 'init'
This error suggests that the init command is unknown, which is contrary to the recommendation provided in the deprecation warning.

I am unable to proceed with the integration and upgrade process due to these errors.
Best Regard,

Hello,
I have an update regarding the issue I previously posted. I decided to run the help command to further understand the available commands and their purposes:
Commands:
  manifest [options] Generate a web manifest file
  sw|service-worker [options] Generate a service worker file
  help [command] display help for command

It became apparent that the correct command to create a service worker file is npx remix-pwa@latest sw , not npx remix-pwa@latest init as I initially thought. Additionally, it's crucial to include the @latest keyword in the command.
However, I discovered that using npx remix-pwa@latest sw directly generates a basic entry.worker.ts file, bypassing any setup wizard or interactive prompts.
The command executed was:
$ npx remix-pwa@latest sw
Generating TypeScript service worker file...

And this resulted in the following entry.worker.ts file being generated:
/// <reference lib="WebWorker" />

export {};

declare let self: ServiceWorkerGlobalScope;

self.addEventListener('install', event => {
  console.log('Service worker installed');

  event.waitUntil(self.skipWaiting());
});

self.addEventListener('activate', event => {
  console.log('Service worker activated');

  event.waitUntil(self.clients.claim());
});

This outcome clarifies the process for generating a service worker file, albeit without the guided options initially expected.

Hello @tyshgc 👋, I am yet to publish the changelog to the documentation site but the CLI no longer scaffolds a PWA. Due to<EMAIL_ADDRESS>migrating to vite, there doesn't seem to be anything to scaffold as everything is wrapped in a plugin. Because of that, the CLI now allows you to generate the various components of PWA - manifest, service worker. Without jeopardizing your Vite App

Regarding the use of latest, that is crucial when you have multiple versions of remix-pwa available. You can remove the old versions by clearing out your npm cache (If you didn't install it globally), but I guess you have other packages you would love to keep in the cache that you use regularly, so the solution is to use the latest tag as npm randomly picks versions (in my own experience) without a tag present

I now understand that with the migration of remix-pwa@4 to Vite, the previous building process through the CLI has been transitioned, and the importance of using the latest tag. Thank you for your support!

This issue appears to be solved. Closing


Deploy on Tron Shasta

Chain Name
Tron Shasta
Chain ID
2494104990
RPC URL
https://api.shasta.trongrid.io
Block Explorer URL
https://shasta.tronscan.org/
Deployment Funds
No

Tron addresses are not EVM compatible so I am going to close this issue, as I do not want to use up the nonce in case it becomes EVM compatible


added dev attribute to interface source

Signed-off-by: Daniel Kucera<EMAIL_ADDRESS>

BTW, i merged your first 3 commits already - just the Q for the last one

All patches merged now.


Karist should use funcml instead of re-implementing it

We should separate the Karist CLI and its mutative engine to let it be useful in other contexts than Kubernetes. Separating this project in two parts:

the mutative language part, called "funcml-lang"
the Karist CLI that can generate examples and apply changes to Kubernetes specifically

Karist would have a new Rubygems.org dependency: "funcml". Unit tests would not perform any test on funcml mutations but should be focus on CLI tasks, such as files generation and exception management.

funcml-lang repository: https://github.com/mimopotato/funcml-lang


Details Section

This is a pull request to review the details section of the website.
Some features implemented include:

UI
Redux

I have fixed the errors. You can check it out.


How to recover/subscribe to unacknowledged messages?

Is there any way to either recover the unacknowledged messages and publish back to the queue or subscribe to unacknowledged messages?

AFAIK, the only way to do this is for the message consumer to a) nack the message, or b) disconnect, which will automatically nack the message.
if you're stuck in a state where the code has errored and messages are in limbo, you will need to shut down and restart the process to get the message back in to the queue.

What's happens if I nack the message? Currently I have a queue with couple of unack messages and to get them back into the queue. I need to do the restart?

If you nack a message, it will be returned to the end of the line in the queue.
Say a Q has m1, m2 and m3 in that order. If your consumer picks up m1 and then calls nack on that message, the Q will now have m2, m3, and m1 in that order. The message has been re-queued, so it will no longer be held by the consumer. It will now be at the back of the line in the queue.
The only time you should need to restart your consumer process to clear an unacknowledged message, is when the code is stuck and cannot ack or nack the message. This typically means something has crashed, or you had a mis-configured message type handler in wascally.
If you are dealing with misconfigured message types, or message types that your consumer should not be handling, check the wascally documentation for unhandled messages https://github.com/LeanKit-Labs/wascally#unhandled-messages (and look right above that for error handling)

@derickbailey  Thanks a lot for a quick response. I really appreciate you for answering my questions patiently. I'm fairly new this and I'm trying to wrap my head around it.
So let's says there is Q and with messages m1, m2, m3 and consumer A subscribed to the Q.
Now consumer gets the m1, m2, m3 since it is subscribed right. Out of the three message m1 is nacked and m2, m3 are acknowledged. m2 and m3 will be remove from the queue and will the consumer A get that m1 message again? If no how do I get it?

@dirajkumar you're welcome! happy to help when i can. :)
Yeah, in that scenario Consumer A would receive m1 a 2nd time... and 3rd, 4th, 5th, etc. if you keep nacking the same message. so, you have to be careful here. i've seen messages go in to infinite loops by accident, with a consumer nacking them over and over and over again.
If you're looking for a way to prevent Consumer A from receiving that same message over and over again, but you still want to process it somewhere else, look in to dead letter exchanges and reject the message so it goes to the dlx. https://www.rabbitmq.com/dlx.html


Find widget in Jupyter Notebook in VS Code gives inconsistent, high number of results

Type: Bug
No idea how to reproduce the problem. The find widget works fine in most of my scripts. It displays the number of matches, and takes me to a specific match. But when I use the find widget for one specific script, the resulting number of matches is inconsistent (ranging from 180-500) when it should be single digits. It also does not take me to the location of the "match".
 It looks like you may be using an old version of VS Code, the latest stable release is 1.82.3. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I just updated it, and the issue is still occurring.

Related on Stack Overflow: Find widget in Jupyter Notebook in VS Code gives inconsistent, high number of results

Yeah, that is also my post.

Can you please share the notebook in which you can reproduce this issue?

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


Mesa Darwin support

Fixes Mesa on Darwin and simplifies some flags. Should go to staging
This fixes the darwin build, while also using Meson’s auto features as
much as possible. As a result, we avoid using having to specify
default drivers and instead delegate that to Mesa’s build system.
Removed other flags that were specified to the default in Mesa.
The -fno-common is needed to address undefined symbol _lp_dummy_tile
in the build.
@eadwu

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Builds fine for me, as for the differences in configuration summary, the only differences are the addition of r100 and the removal of omxbellagio for me.
old -> new
<         DRI drivers:     r200 nouveau i915 i965
---
>         DRI drivers:     i915 i965 r100 r200 nouveau

<         Gallium st:      mesa xa xvmc xvmc vdpau omxbellagio va nine
---
>         Gallium st:      mesa xa xvmc xvmc vdpau va nine

< Build targets in project: 206
---
> Build targets in project: 205

On the current staging-next iteration https://github.com/NixOS/nixpkgs/pull/64236 we have thousands of darwin failures due to mesa not building (even though only headers would be used anyway IIRC).  This can be re-based with a trivial conflict, but I don't have time to give it a proper review now.

aarch64 changes are larger ATM:
-       DRI drivers:     nouveau
+       DRI drivers:     no

-       Vulkan drivers:  amd
-       Vulkan ICD dir:  share/vulkan/icd.d
+       Vulkan drivers:  no

-       Gallium drivers: virgl nouveau vc4 freedreno etnaviv swrast
-       Gallium st:      mesa xa xvmc xvmc vdpau omxbellagio va nine
+       Gallium drivers: kmsro v3d vc4 freedreno etnaviv nouveau tegra virgl lima swrast
+       Gallium st:      mesa xa xvmc xvmc vdpau va nine

I shall hope that their defaults are generally better than what we had :woman_shrugging:  No critical problem seems likely.  I pushed the rebase to staging-next as 5c8472a2a17.

The omxbellagio removal looks bad though! It probably needs its own flag.

You mean, make it configurable but keep the default from upstream?  I must admit I don't know how much this feature is significant in practice.


Feature: sorting rooms

I would love to have the option to sort Rooms by alphanumerics in addition to activity.
I'm one of those who looks for conversations based on their position on the screen. So having Rooms move when activity changes inside of them is problematic for me.
I do see that after activity (highlights, unread messages), you are sorting by alphanumeric name. I'm not sure whether I really like lowercase letters being sorted after uppercase, but as long as they just don't move, I can put up with either.

Thanks for opening this issue! I definitely agree that the room organization could do with some improvements. I'll add the option to sort alphanumerically, ignoring activity indicators. I want to also explore the option to manually sort rooms, but I'm not totally sure if SwiftUI supports that.


When clear a reactive array object in effect function, the array.length is not 0, all ways has a element in it.

Vue version
3.2.22
Link to minimal reproduction
https://github.com/vuejs/core/discussions/6017
Steps to reproduce
just copy the code to HTML file, load page in browser.
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title>reactivity test</title>
    <script src="https://unpkg.com/<EMAIL_ADDRESS>    <script>
        const store = VueReactivity.ref([])
        // const store = VueReactivity.reactive({
        //     value: []
        // })

        let counterForRun = 0
        const effectRunner = VueReactivity.effect(() => {
            console.log(`effect run times is ${counterForRun}`)
            if (store.value.length > 0) {
                // do some thing...
                console.log(`store value is ${JSON.stringify(store.value)}`)
                // clear store
                // store.value.length = 0
                store.value.splice(0) // trigger effect again
            }
            counterForRun += 1
        })

        let intervalTimes = 0
        const intervalId = setInterval(() => {
            if (intervalTimes === 2) {
                clearInterval(intervalId)
                // VueReactivity.stop(effectRunner)
                return
            }
            store.value.push(intervalTimes)
            intervalTimes += 1
        }, 1000)

    </script>
</head>
<body>

</body>
</html>

store.value.splice(0) trigger effect callback run again, but in the effect callback, store.value.length is not 0.
Did I use @vue/reactivity it in the right way ???
What is expected?
When clear store.value, the store.value.length=0 .
What is actually happening?
Clear reactive array store, but the store.value.length=1, not 0.
System Info
5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.64 Safari/537.36 Edg/101.0.1210.53

Any additional comments?
Maybe I use it in the wrong way.

same issue   https://sfc.vuejs.org/#eNp9kcFugzAMhl/FywUqpaBut4qiTdphb7DDsgMFU+hCEiWh1YR49zlhrapO2iWK7d/fn9gTezEmO43Itqxwte2NB4d+NKVQ/WC09TDBufJ1x8FiG46q9v0JYYbW6gES6k2EEqrWynkY3AF2QZkmbyilhndtZfOQrC6CytooWCjpx4Y/8qdPKkeTlMoc0tWuhEkogNCjJWZSH9IkKgIg4eHMnOxrTFfUO3OYWjm6bguJ+1Z1Ml/9uko1El9RokcyTldwYUeEiYwN31DDnd3VKBgIVeTLeGgwFHgcjKw8UgRQdJtymuLf57nIKYrZ/ei9VvBck8fXTrDbpwhWNvFS5IuMWor8SmWcLdNfD5XJjk4r2k98tfgtOMG2yz9CjpYQYvLw3rhtnru2Dls9ukzbQ063zI7K9wNm6Ib13uqzQ0tgwfgNI6fkCe3aomrQov2PeSf9ww1YGtvM5h/o7dGM

I got exactly the same problem.
When splicing an element out of an reactive Array, computed values are triggered too early.
The item has been sucessfully removed, but the array.length is unchanged when the computed value recompution is triggered.
Which causes errors when looping over that array.

This isn't really an edge-case. There should be a warning somewhere in the docs, that you should not use  watch with flush: sync, or computedEager for large arrays.
And that splice(), shift(), etc. are not atomic operations with Vue.

Fixed by #5912.


subprocess module

Create a pure Kuroko module providing the subprocess.Popen interfaces.

ya subprocess is a necessity, any plans for adding this soon? also consider re module and json.dumps


allow newer versions to load the mod

tested, it works fine.
Given that this is a super light 1-mixin mod there's a super low chance of it breaking, so I think this is reasonable.

I'm going to do it a different way so I'm not going to merge


De-dupe some code

Create static methods in ClientContext for ZooKeeperInstance

Nice deduplication.
ZooUtil is probably a better place for the static method than embedded in ClientContext (it's better to keep the ZK stuff isolated to one spot, rather than intermingled with the rest of our utilities/internal code; it'll be easier to abstract ZK later).

Good idea.  I wasn't sure of where the best place was for these methods.
I wanted to talk to @keith-turner about using Ample for deduping ZooKeeperInstance.getRootTabletLocation() but wasn't sure how to use it with the old code.

I wanted to talk to @keith-turner about using Ample for deduping ZooKeeperInstance.getRootTabletLocation() but wasn't sure how to use it with the old code.

I think that code needed special case because Ample's impl requires a ClientContext but that code is happening before everything needed for a ClientContext exists.

@milleruntime I believe this PR breaks ZooKeeperInstanceTest cases for testGetInstanceID_IDMissingForID and testGetInstanceID_IDMissingForName.
I'm trying to get the unit tests to pass on Java 11, and this is one I noticed was failing and seemed unrelated. These test methods are expecting a RuntimeException, but nothing is thrown. It could be that the test needs to be updated... but it could also be that the code didn't preserve prior behavior. I haven't investigated yet, and considering reverting this so I can get the UTs to pass under Java 11, before re-applying this change.

After some investigation, I realized this needs to be reverted. It doesn't handle some situations correctly (details in revert message). This can probably be fixed and re-applied after the unit tests are passing again (I'm working on that now).

@milleruntime I believe this PR breaks ZooKeeperInstanceTest cases for testGetInstanceID_IDMissingForID and testGetInstanceID_IDMissingForName.
I'm trying to get the unit tests to pass on Java 11, and this is one I noticed was failing and seemed unrelated. These test methods are expecting a RuntimeException, but nothing is thrown. It could be that the test needs to be updated... but it could also be that the code didn't preserve prior behavior. I haven't investigated yet, and considering reverting this so I can get the UTs to pass under Java 11, before re-applying this change.

Tests were failing when I merged... why revert?  I could have just applied a fix.

I reverted because the code was broken and I wasn't prepared to fix it. It seemed the prudent thing to do, so I could get the build working again. Now that I fixed the build, this should be easy to reapply and isolate the failures to triage the breakage, and I had intended to do that today if you don't get to it first.


Capturing installation times on rosa installations

New active waiting for all nodes to be ready after the installation process.
Uploading installation times to openshift-install-timings elasticsearch index

All intermediate status until cluster is installing. Waiting, Validating and Pending
Installation : Time until cluster is on ready status when asking rosa api
Cluster Ready time: Time until all nodes are on ready status
Cleanup: Time to execute rosa delete cluster

Execution example: http://morenod-rosa-timing-airflow.apps.sailplane.perf.lab.eng.rdu2.redhat.com/log?dag_id=4.10-rosa-sdn-control-plane&task_id=install&execution_date=2022-04-18T16%3A08%3A32.687472%2B00%3A00
Data uploaded to ES: https://perf-results-kibana.apps.observability.perfscale.devcluster.openshift.com/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now%2Fw,to:now%2Fw))&_a=(columns:!(),filters:!(),index:'9213e890-a42b-11ec-8892-4bcee73a8de1',interval:auto,query:(language:kuery,query:'platform.keyword:%20%22ROSA%22'),sort:!(!(timestamp,desc)))

Codecov Report

Merging #168 (5700658) into master (701f25d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #168   +/-   ##
=======================================
  Coverage   93.45%   93.45%
=======================================
  Files          24       24
  Lines         993      993
=======================================
  Hits          928      928
  Misses         65       65

Flag
Coverage Δ

gha
93.45% <ø> (ø)

python-3.9
93.45% <ø> (ø)

unit
93.45% <ø> (ø)

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

Continue to review full report at Codecov.

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

ES uploaded documents: https://perf-results-kibana.apps.observability.perfscale.devcluster.openshift.com/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now%2Fd,to:now%2Fd))&_a=(columns:!(),filters:!(),index:'9213e890-a42b-11ec-8892-4bcee73a8de1',interval:auto,query:(language:kuery,query:'platform.keyword:%20%22ROSA%22%20and%20rosa_cluster_name.keyword:%20%22perf-410-d562%22'),sort:!(!(timestamp,desc)))
Installation log: http://morenod-rosa-timing-airflow.apps.sailplane.perf.lab.eng.rdu2.redhat.com/log?dag_id=4.10-rosa-sdn-control-plane&task_id=install&execution_date=2022-04-21T12%3A02%3A02.681374%2B00%3A00

ES uploaded documents: https://perf-results-kibana.apps.observability.perfscale.devcluster.openshift.com/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now%2Fd,to:now%2Fd))&_a=(columns:!(),filters:!(),index:'9213e890-a42b-11ec-8892-4bcee73a8de1',interval:auto,query:(language:kuery,query:'platform.keyword:%20%22ROSA%22%20and%20rosa_cluster_name.keyword:%20%22perf-410-d562%22'),sort:!(!(timestamp,desc)))
Installation log: http://morenod-rosa-timing-airflow.apps.sailplane.perf.lab.eng.rdu2.redhat.com/log?dag_id=4.10-rosa-sdn-control-plane&task_id=install&execution_date=2022-04-21T12%3A02%3A02.681374%2B00%3A00

Checked the docs at the ES link, looks good. We need a dashboard in grafana/Kibana with X-Axis having the ocp version and Y-Axis having stacked column charts to track this over releases. Would be cool to have this data captured over time to see if we are doing better/regressing.

@morenod Since some fields like the networkType, cluster name, cluster version, master_count and worker_count are only available when the cluster has been installed and not when its validating or installing, we would be missing important metadata to do run to run comparisons. Anyway we can capture that? (I know the oc command doesn't provide it before the cluster has been installed, but wondering if we can set some of these statically based on what was passed on the rosa cli. Thoughts?

I'm not a fan of statics assignments, that's why I have added the Rosa cluster name which will be available on all documents of the same installation but also UUID will be also the same. Maybe we could wait until we build some dashboard associated with this timers and, if we have any problem showing the info, we can change to static assignments based on installation parameters

I'm not a fan of statics assignments, that's why I have added the Rosa cluster name which will be available on all documents of the same installation but also UUID will be also the same. Maybe we could wait until we build some dashboard associated with this timers and, if we have any problem showing the info, we can change to static assignments based on installation parameters

I don't disagree with you but we atleast need the OCP version to be able to aggregate multiple runs so we can compare across versions over the dozens of runs we have. I think it's safe to atleast assign version because we don't really expect a different version to be installed than what was passed on the cli :)

I'm not a fan of statics assignments, that's why I have added the Rosa cluster name which will be available on all documents of the same installation but also UUID will be also the same. Maybe we could wait until we build some dashboard associated with this timers and, if we have any problem showing the info, we can change to static assignments based on installation parameters

I don't disagree with you but we atleast need the OCP version to be able to aggregate multiple runs so we can compare across versions over the dozens of runs we have. I think it's safe to atleast assign version because we don't really expect a different version to be installed than what was passed on the cli :)

OK, so I have recheck all the parameters we are adding on the doc.
I have statically set platform, networktype, aws authentication, version and rosa cluster name, because they are parameters which wont change during or after the installation, and we now their value before the installation starts
Master and infra node counts cannot be set, they are dependant on the AWS region.
We could set workers and workload nodes, but they dont give important information on the phases that they cannot be calculated
OCP_cluster_name is rosa_cluster_name+4chars hash directly generated on OCP, we cannot set until we get from the cluster


Notebook 42 error

Thank you for catching this. I recently modernized a few notebooks (#766) and must have messed this one up.
I'll put in a fix.

my pleasure
On Thu, 22 Aug 2024 at 01:50, David Mezzetti @.***>
wrote:

Closed #768 https://github.com/neuml/txtai/issues/768 as completed via
5f297ab
https://github.com/neuml/txtai/commit/5f297abe27b35469d99f27037dbcab8de29d4fee
.
—
Reply to this email directly, view it on GitHub
https://github.com/neuml/txtai/issues/768#event-13968332813, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAX7BV7UVN2QP5DUIKH3XB3ZSURU7AVCNFSM6AAAAABM45EVJSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTHE3DQMZTGI4DCMY
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Bjorn Heijligers
+31620106733


Blank extension icon in Marketplace gallery

Extension icon isn't showing up in Marketplace galler

y

It wasn't invisible, it had transparent background and in the gallery both the background and the icon text was white... 🤦♂


Add neotoma to extra_applications for elixir 1.15 compatibility

Needed to avoid a compilation failure with 1.15
** (UndefinedFunctionError) function :neotoma.file/2 is undefined (module :neotoma is not available)
    (neotoma 1.7.3) :neotoma.file(~c"/tmp/slime/src/slime_parser.peg", [transform_module: :slime_parser_transform])
    tasks/compile.peg.exs:37: Mix.Tasks.Compile.Peg.compile_grammar/2
    (mix 1.15.4) lib/mix/task.ex:447: anonymous fn/3 in Mix.Task.run_task/5
    (mix 1.15.4) lib/mix/tasks/compile.all.ex:124: Mix.Tasks.Compile.All.run_compiler/2
    (mix 1.15.4) lib/mix/tasks/compile.all.ex:104: Mix.Tasks.Compile.All.compile/4
    (mix 1.15.4) lib/mix/tasks/compile.all.ex:93: Mix.Tasks.Compile.All.with_logger_app/2
    (mix 1.15.4) lib/mix/tasks/compile.all.ex:56: Mix.Tasks.Compile.All.run/1
    (mix 1.15.4) lib/mix/task.ex:447: anonymous fn/3 in Mix.Task.run_task/5

Hi @liamwhite
I'm using your fork with Elixir >= 1.15 and it solves the neotoma missing module problem.
But, I get this warning:
both :extra_applications and :applications was found in your mix.exs. You most likely want to remove the :applications key, as all applications are derived from your dependencies

So, I believe the change should be:
  def application do
    [
-     applications: [:eex]
+     extra_applications: [:eex, :neotoma]
    ]
  end

I would really appreciate if this (or a similar PR) was merged as slime is a dependency of a library that I maintain and I cannot release it (for Elixir >- 1.15) without this change.
Any chance of getting this merged and released?

For anyone else who might need Elixir >= 1.15 compatibility, I've released my fork as jgy_slime.
I'll discontinue the fork as/when this gets merged, of course :)

@joeyates do you mind creating a PR upgrading the package to Elixir >= 1.15

Hi @yordis
I believe this PR has this covered.
@liamwhite 's update to this PR on March 4th uses :extra_applications exclusively, which I think is the correct approach.


evm/loader: assertion failed: !values.is_empty()

This happens with the test branch: test branch: https://github.com/privacy-scaling-explorations/zkevm-chain/compare/master...pinkiebell:zkevm-chain-fork:verifier
The examples/ from plonk-verifier are working but not with the super circuit.
backtrace:
thread 'verifier_autogen' panicked at 'assertion failed: !values.is_empty()', /target/cargo/git/checkouts/plonk-verifier-755858dad3193220/9fa07d1/src/loader/evm/loader.rs:939:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/015a824f2dffe32707fceb59c47effaf7b73486c/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/015a824f2dffe32707fceb59c47effaf7b73486c/library/core/src/panicking.rs:142:14
   2: core::panicking::panic
             at /rustc/015a824f2dffe32707fceb59c47effaf7b73486c/library/core/src/panicking.rs:48:5
   3: plonk_verifier::loader::LoadedScalar::sum_products
   4: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::fold
   5: <core::iter::adapters::chain::Chain<A,B> as core::iter::traits::iterator::Iterator>::fold
   6: <std::collections::hash::map::HashMap<K,V,S> as core::iter::traits::collect::FromIterator<(K,V)>>::from_iter
   7: <plonk_verifier::scheme::kzg::accumulation::plonk::PlonkAccumulationScheme as plonk_verifier::scheme::kzg::accumulation::AccumulationScheme<C,L,T,S>>::accumulate
   8: core::ops::function::FnOnce::call_once
   9: core::ops::function::FnOnce::call_once
             at /rustc/015a824f2dffe32707fceb59c47effaf7b73486c/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
test verifier_autogen ... FAILED

Note: the plonk-verifier fork is based on #5 . This fork includes fixes to make cargo happy. But it also removes
-halo2_proofs = { git = "https://github.com/han0110/halo2", branch = "feature/configurable-instance-query", package = "halo2_proofs" }

and uses upstream pse instead. Could that be the reason?

Thanks for reporting! I think it's a mistake I have made (I assume input of sum should always be some values, but the example you are using has a instance column without value, so it panics), will push a fix soon.

Hey @pinkiebell, I have push a commit in the same branch to fix this issue, but it also contains some breaking changes, please update the test you are trying with these major changes:

Major changes

# ...
- use plonk_verifier::{
-     loader::evm::{EvmLoader, EvmTranscript},
-     protocol::halo2::{compile, Config},
-     scheme::kzg::{AccumulationScheme, PlonkAccumulationScheme, SameCurveAccumulation},
-     util::TranscriptRead,
- };
+ use plonk_verifier::{
+     loader::evm::{EvmLoader, EvmTranscript},
+     pcs::kzg::{Gwc19, KzgOnSameCurve},
+     system::halo2::{compile, Config},
+     util::transcript::TranscriptRead,
+     verifier::{Plonk, PlonkVerifier},
+ };
# ...
-    let instances = num_instance
-        .into_iter()
-        .map(|len| {
-            iter::repeat_with(|| transcript.read_scalar().unwrap())
-                .take(len)
-                .collect_vec()
-        })
-        .collect_vec();
-
-    let mut strategy = SameCurveAccumulation::<_, _, LIMBS, BITS>::default();
-    PlonkAccumulationScheme::accumulate(
-        &protocol,
-        &loader,
-        instances,
-        &mut transcript,
-        &mut strategy,
-    )
-    .unwrap();
-    strategy.finalize(params.get_g()[0], params.g2(), params.s_g2());
+    let instances = num_instance
+        .into_iter()
+        .map(|len| transcript.read_n_scalars(len).unwrap())
+        .collect::<Vec<_>>();
+    Plonk::<KzgOnSameCurve<Bn256, Gwc19<Bn256>, LIMBS, BITS>>::verify(
+        &params.get_g()[0],
+        &(params.g2(), params.s_g2()),
+        &protocol,
+        &instances,
+        &mut transcript,
+    )
+    .unwrap();
# ...

@han0110 Thanks! This works now. The runtime code is  > 1GiB . So this probably depends on #6  ?
I can test with a minimal PublicInput circuit in the meantime, but this will probably be also too big to deploy

I wasn't able to test the aggregation with the supercircuit yet because the memory requirements seems to be grown heavily. But that's another problem. This issue is resolved :)


mizu : Command not found after installation

I have installed mizu on my Linux Ubuntu instance (EC2 instance)  with
curl -Lo mizu https://github.com/up9inc/mizu/releases/latest/download/mizu_darwin_amd64 && chmod 755 mizu
but when I run _mizu version_ I get error "Command not found".
I have done the same installation on my Windows PC (Win 11) and I get similar error "Command not found".
What am I missing ?

Hi @Ed87 ,
it looks like you are downloading the incorrect file (this link is downloading the darwin (mac os) installation.
you should use
curl -Lo mizu https://github.com/up9inc/mizu/releases/download/34.0-dev3/mizu_linux_amd64 && chmod 755 mizu

on linux  or
curl -LO https://github.com/up9inc/mizu/releases/download/34.0-dev3/mizu.exe

on windows.

@gadotroee  same error even after using that version . I have tried on Windows :

Do I need to do anything config related after this?

Ok I see,
Whem you work on windows the executable called mizu.exe, so you need to run mizu.exe version.. I don't know why it didn't work on Linux machine but if you can try to run the executable (abd check that you really have file that called mizu.exe after running the command it will be good.

@gadotroee  Same error still . Even when I use mizu.exe version
Should it be installed at a particular path?
Any need to setup environment variables

You just need to be in the same folder.
This command (the curl) dowoad the mizu cli. (You should see mizu.exe file in the directory you are currently in).
Then mizu.exe will be valid command.

I am in the same path, I dont know why it cant run

Can you check if the "mizu.exe" file exists in the directory?

users-MacBook-Pro:Applications marcuss$ cd /Users/marcuss/code/
users-MacBook-Pro:code marcuss$ curl -Lo mizu https://github.com/up9inc/mizu/releases/latest/download/mizu_linux_amd64 && chmod 755 miz
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 49.3M  100 49.3M    0     0  5512k      0  0:00:09  0:00:09 --:--:-- 4275k
chmod: miz: No such file or directory
users-MacBook-Pro:code marcuss$ mizu
-bash: mizu: command not found
It is happening to me to, altho I'm in a MAC