text:
Diff generates invalid patch if an object becomes an array

There seems to be an issue with the json_patch::diff function. The path op Add is returned before Remove. Added failing test case as an example:
    async fn failing_test() {
        let left = json!({ "style": { "ref": "name" } });
        let right = json!({ "style": [{ "ref": "hello" }]});

        let patch = json_patch::diff(&left, &right);

        let mut initial = left.clone();
        json_patch::patch(&mut initial, &patch);

        assert_eq!(
            serde_json::to_string(&right).unwrap(),
            serde_json::to_string(&initial).unwrap()
        );
    }

gives output
assertion `left == right` failed
  left: "{\"style\":[{\"ref\":\"hello\"}]}"
 right: "{\"style\":{\"0\":{\"ref\":\"hello\"}}}"

If I try this same with some other diff tool eg (https://json-patch-builder-online.github.io/) it gives the patches in right order eg.:
[
    {
        "op": "remove",
        "path": "/style/ref"
    },
    {
        "op": "add",
        "path": "/style/0",
        "value": {
            "ref": "hello"
        }
    }
]

while this lib gives the Add op first.

Ah, that's annoying. Seems like library I use, treediff, does not distinguish enough between arrays and objects.
I'll try to rewrite the whole diffing myself. Doing it directly against serde_json::Value should be easier than try to coerce this library for my needs... And then I would only "diff" same-kinded nodes, any time node kind changes ("object" vs "string" or "object" vs "array"), I would simply issue patch "replace" operation.

Should be fixed in 1.3.0.

Should be fixed in 1.3.0.

that was fast, I'll try it out! thanks 😄

authors: idubrov vileanco

repo: idubrov/json-patch


text:
Add prompt message for 'Refresh View'

Where click the button 'Refresh View', pop up a model form including prompt message  and two buttons 'Continue refreshing' and 'Check view'.
Prompt Message:  'Please check view and correct related issues firstly, then refresh view'.
Button 'Check view' direct to tab 'Check View'.
Button 'Continue refreshing' execute 'refresh view'.

Updated.  Please test it.

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Motion Detection: Add optical flow subsampler + store numpy arrays in npz metadata

will let us do dense optical flow in the 2nd stage (after downloading)
TODO
CV2

[x] implement cv2 optical flow detection
[x] parameterize the optical flow hyperparams (let user specify)
[x] figure out file extension when saving optical flow -- ideally we'd want to be able to np.load() the optical flow data directly
[x] Temporal subsampling
[x] Test end2end WDS input -> Files
[x] Test end2end WDS input -> WDS
[x] Test magnitude metric

lgtm, we can iron out the last few things in future PR's

source: gharchive/pull-request

authors: danielmend iejMac

license: MIT


text:
Remove vendored code

This fixes #1 by moving to from @dutchcoders's go-clamd to @Freeaqingme's fork, that removes annoying logging and adds more structured responses.

@atzoum wdyt? :-)

@jblackman your feedback is also very welcome

Looks good. The @dutchcoders guys move pretty slowly, but keep an eye out for them merging in the changes from the @Freeaqingme fork, assuming he ever bothers with a merge request.

Thanks both! Merging and cutting a v0.6.0 release.

authors: jblackman vjt

repo: ifad/clammit

license: mit

license_source: bigquery


text:
Update pkgs and added new ones

Following changes were made:

Updated gnome/gtk4 from 4.7.0 to 4.8.1
Added gui/libva allowing the usage of VA-API
Added extra/ruby

We should think about adding libva to the base repo perhaps.

Remove gui/libva; that should go in the main repo. Remove merge commits. other than that LGTM (though i'm not sure if we should wait for the muon switch in the main repo or not)

thanks babes. merged now :3

repo: iglunix/community


text:
How change ocr language?

How change it? I dont find method

Check File | Options | Language in OneNote

I mean in code how set language)

Sorry, I do not have a good one.

authors: Radzhab ignatandrei

repo: ignatandrei/OneNoteOCR


text:
Normalize normal vectors from OBJ.

Normal vectors that are not normalized might cause incorrect rendering results.

This pull request has been mentioned on Gazebo Community. There might be relevant details there:
https://community.gazebosim.org/t/new-ignition-releases-2022-01-24-citadel-edifice-fortress/1241/1

authors: mahiuchun osrf-triage

repo: ignitionrobotics/ign-common


text:
LogSystemTest.RecordAndPlayback fails in ign-gazebo4

The pull #410 was merge with failures in Github actions.
 [ RUN      ] LogSystemTest.RecordAndPlayback
  [Msg] Loading SDF world file[/github/workspace/test/worlds/log_record_dbl_pendulum.sdf].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [2251689575469537287] / [ign_gazebo_components.World].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [13994732549916512682] / [ign_gazebo_components.Name].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [12592746352568925681] / [ign_gazebo_components.Gravity].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [13224937992534617849] / [ign_gazebo_components.MagneticField].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [3630648173860223239] / [ign_gazebo_components.PhysicsEnginePlugin].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [17459188283658606303] / [ign_gazebo_components.RenderEngineServerPlugin].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [8705992680619689917] / [ign_gazebo_components.RenderEngineGuiPlugin].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [8753193699724811771] / [ign_gazebo_components.Wind].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [12173050716021724529] / [ign_gazebo_components.WorldLinearVelocity].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [15943768124495574352] / [ign_gazebo_components.WorldLinearVelocitySeed].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [3297509811873971798] / [ign_gazebo_components.ParentEntity].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [17100615127981600159] / [ign_gazebo_components.Scene].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [17605309075052480649] / [ign_gazebo_components.Atmosphere].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [8064491505919932473] / [ign_gazebo_components.Level].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [2668898242563798256] / [ign_gazebo_components.DefaultLevel].
  [Dbg] [EntityComponentManager.cc:661] Using components of type [11371360182141354106] / [ign_gazebo_components.LevelEntityNames].
  [Dbg] [Physics.cc:620] Loaded [ignition::physics::dartsim::Plugin] from library [/usr/lib/x86_64-linux-gnu/ign-physics-3/engine-plugins/libignition-physics-dartsim-plugin.so]
  [Dbg] [SimulationRunner.cc:765] Loaded system [ignition::gazebo::systems::Physics] for entity [1]

...

  [Msg] Found no publishers on /stats, adding root stats topic
  [Msg] Found no publishers on /clock, adding root clock topic
  [Dbg] [SimulationRunner.cc:403] Creating PostUpdate worker threads: 2
  [Dbg] [SimulationRunner.cc:416] Creating postupdate worker thread (0)
  [Msg] Serving scene information on [/world/default/scene/info]
  [Msg] Serving graph information on [/world/default/scene/graph]
  [Msg] Serving full state on [/world/default/state]
  [Msg] Publishing scene information on [/world/default/scene/info]
  [Msg] Publishing entity deletions on [/world/default/scene/deletion]
  [Msg] Publishing state changes on [/world/default/state]
  [Msg] Publishing pose messages on [/world/default/pose/info]
  [Msg] Publishing dynamic pose messages on [/world/default/dynamic_pose/info]
  /github/workspace/test/integration/log_system.cc:895: Failure
  Value of: nTotal == expectedPoseCount || nTotal == expectedPoseCount + 1
    Actual: false
  Expected: true
  nTotal [32] expectedPoseCount [30]
  [Dbg] [SimulationRunner.cc:432] Exiting postupdate worker thread (0)
  [  FAILED  ] LogSystemTest.RecordAndPlayback (1960 ms)

Seems to me like a possible timing/race condition problem. The test is disable for APPLE, not sure if this is related.

Seems to me like a possible timing/race condition problem.

Yeah this test has been flaky. We added the || condition to relax it a bit and it still fails sometimes. I'll see what I can do.

authors: chapulina j-rivero

repo: ignitionrobotics/ign-gazebo


text:
Refactor Image Display to use ConvertToRGB function

Signed-off-by: Ian Chen ichen@osrfoundation.org
🎉 New feature
Summary
Depends on https://github.com/ignitionrobotics/ign-common/pull/205
Updated Image Display to use the new Image::ConvertToRGB function for visualizing depth and thermal camera sensor images, see https://github.com/ignitionrobotics/ign-common/pull/205
Test it
Run the sensors_demo.sdf world and you should see that the images in the the Image Display should be correctly rendered the same way as before.
ign gazebo -v 4 sensors_demo.sdf

Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

Would this by chance close https://github.com/ignitionrobotics/ign-gui/issues/177?

Would this by chance close #177?

ah forgot about that one - yes it'll close the issue

repo: ignitionrobotics/ign-gui


text:
[Bullet] Removing GetContactsFromLastStepFeature from Simulation Features

🎉 New feature
Closes #
Summary
Removed GetContactsFromLastStepFeature from the engine's features.
Test it
Compile and try running any simulation with bullet engine, depends on https://github.com/ignitionrobotics/ign-gazebo/pull/690
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

Merging as https://github.com/ignitionrobotics/ign-gazebo/commit/a84ec51c2fddcc09eeb0ed26b31f8de669c1ce56 is in place

repo: ignitionrobotics/ign-physics


text:
🛑 Nexus: Fonts CDN is down

In 2bca370, Nexus: Fonts CDN (https://fonts-cdn.nexuspipe.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nexus: Fonts CDN is back up in 109e8b8 after 8 minutes.

repo: ignore-me-lol/personal-uptime-monitor


text:
提问：https://www.infineon.de握手？

和https://www.infineon.de握手，会和那个ip握手。是vps 就近 和https://www.infineon.de握手？

感觉s-t的延迟好慢，慢一倍。就近握手的话，延迟 就接近 本来的延迟 了？

TLS 握手本来就慢，但是只有建立连接的延迟较高。可以考虑选用离 vps 较近的握手服务器，以及尽可能使用 TLS1.3。

repo: ihciah/shadow-tls


text:
Add option to strip tag from file link

Added an option for inserting roam tag to file link.

Heh, guess I should have read your original comment better. I interpreted your comment to read that you didn't like the tags appearing in the description in the quick panel not in the link. :)
So I made it possible just to turn them off globally. Both options have utility though, so might as well just keep both.

Yeah. I totally agree with you that tags should be searchable. I just don't like the tag appears in the link. I'll resolve the conflict.

authors: ihdavids waynezhang

repo: ihdavids/orgextended


text:
Reporter.describe modified to not print by default

Per suggestion by @awais307 via issue #271, this PR slightly modifies the code in Reporter.describe() so that the output is not printed by default.
How to review
The method can be run without passing any argument to quiet, and the results shouldn't be printed.
PR checklist

[x] ~Tests added.~ Minor change in behaviour, no test and documentation is needed.

 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.

@awais307 since this is your issue, I'll ask you to work with @behnam-zakeri to ensure the change is as desired.

Excellent! Thanks both.

authors: CLAassistant behnam-zakeri khaeru

repo: iiasa/ixmp


text:
messageix-config causes error on windows

It has to do with trying to write the json file. Will add more details asap.

I can not reproduce on my machine, fresh conda install, fresh message_ix install.


text:
关于代码转换成图片的一点建议

毫无疑问，Next是一款非常出色的主题。
希望添加一个能够把代码直接转换成图片的功能，其实在我看来，这是最后一公里。
我相信大家肯定注意到了，在android端或者ios端，看自己的博客的时候，文字的适配没问题，但是code，代码的适配却很糟糕。
为此，我能想到就是，希望有一个功能，能够把贴上去的代码，直接能转换成图片，方便阅览，那简直是太棒了。

Duplicated with #1885, closed.

authors: Acris YanHuiLi

repo: iissnan/hexo-theme-next


text:
页面显示不正常 GET /css/main.css?v=5.1.2 404

I agree and want to create new issue

[x] Yes, I was on Hexo Docs page, especially on Templates, Variables, Helpers and Troubleshooting.
[x] Yes, I was on NexT Documentation Site.
[x] And yes, I already searched for current issues and this is not help to me.

Expected behavior
能正常使用
Actual behavior

Steps to reproduce the behavior

git clone https://github.com/iissnan/hexo-theme-next themes/next
theme: next
hexo clean && hexo g && hexo s --debug

Link to demo site with this issue: https://dinghmcn.github.io/
Link(s) to source code or any usefull link(s): https://github.com/dinghmcn/dinghmcn.github.io

NexT Information
NexT Version:

[x] Latest Master branch.
[] Latest Release version.
[] Old version -

NexT Scheme:

[] All schemes
[x] Muse
[] Mist
[] Pisces
[] Gemini

Other Information
错误日志：
16:18:14.511 DEBUG Generator: asset
16:18:14.520 INFO  Hexo is running at http://localhost:4000/. Press Ctrl+C to stop.
16:18:14.527 DEBUG Database saved
16:18:18.589 DEBUG Rendering index: index.html
GET / 200 84.027 ms - -
GET /css/main.css?v=5.1.2 404 4.637 ms - -
GET /lib/fancybox/source/jquery.fancybox.css?v=2.1.5 200 7.384 ms - -
GET /lib/font-awesome/css/font-awesome.min.css?v=4.6.2 200 6.697 ms - -
public/css/ 下只有 main.styl
~:cat public/css/main.styl
// CSS Style Guide: http://codeguide.co/#css
$scheme    = hexo-config('scheme') ? hexo-config('scheme') : 'Muse';
$variables = base $scheme custom;
$mixins    = base $scheme custom;
// Variables Layer
// --------------------------------------------------
for $variable in $variables
@import "_variables/" + $variable
// Mixins Layer
// --------------------------------------------------
for $mixin in $mixins
@import "_mixins/" + $mixin;
// Common Layer
// --------------------------------------------------
// Scaffolding
@import "_common/scaffolding";
// Layout
@import "_common/outline";
// Components
@import "_common/components";
// Schemes Layer
// --------------------------------------------------
@import "_schemes/" + $scheme;
// Custom Layer
// --------------------------------------------------
@import "_custom/custom";

Try to use standart Hexo theme, is there errors too?

我刚也有这个问题，样式显示不出，然后把 font enable 关了就恢复正常了

重新创建hexo init blog就可以了，应该是我的hexo目录有问题，感谢大家回复。

authors: dinghmcn ivan-nginx unclejimbo


text:
🛑 Penyanyi VF v3 is down

In 9496325, Penyanyi VF v3 (https://discord-musicbot.nexter32.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Penyanyi VF v3 is back up in 1af9908.


text:
🛑 MusicBot UITM is down

In 6f5c9f4, MusicBot UITM (https://MusicBot-UITM.nexter32.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MusicBot UITM is back up in 1404ddd.


text:
coalesce in the where clause

fdw for some reason does not push down coalesce in the where clause:
pg: explain verbose select count(*) from clickhouse.test where coalesce(id, 0) = 123:
Limit  (cost=0.00..0.01 rows=1 width=8)
  Output: (count(*))
  ->  Aggregate  (cost=0.00..0.01 rows=1 width=8)
        Output: count(*)
        ->  Foreign Scan on clickhouse.test  (cost=0.00..0.00 rows=0 width=0)
              ...
              Filter: (COALESCE(test.id, 0) = 123)
              Remote SQL: SELECT id FROM default.test

fixed

authors: ildus mkabilov


text:
Get article by path route

Adds the route getArticleByPath from https://docs.forem.com/api/#operation/getArticleByPath
Also snuck in the repository field into package.json to link to this repo from npm
https://github.com/ilyamkin/dev-to-js/issues/6

Thanks, looks good!

authors: a-axton ilyamkin

repo: ilyamkin/dev-to-js


text:
🛑 Gitlab is down

In 693a06f, Gitlab (https://git.stis.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Gitlab is back up in 6bbbbde.

repo: im-perativa/stis-uptime


text:
No matching distribution found for langchain==0.0.174

ERROR: Could not find a version that satisfies the requirement langchain==0.0.174 (from versions: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.10, 0.0.11, 0.0.12, 0.0.13, 0.0.14, 0.0.15, 0.0.16, 0.0.17, 0.0.18, 0.0.19, 0.0.20, 0.0.21, 0.0.22, 0.0.23, 0.0.24, 0.0.25, 0.0.26, 0.0.27, 0.0.28, 0.0.29, 0.0.30, 0.0.31, 0.0.32, 0.0.33, 0.0.34, 0.0.35, 0.0.36, 0.0.37, 0.0.38, 0.0.39, 0.0.40, 0.0.41, 0.0.42, 0.0.43, 0.0.44, 0.0.45, 0.0.46, 0.0.47, 0.0.48, 0.0.49, 0.0.50, 0.0.51, 0.0.52, 0.0.53, 0.0.54, 0.0.55, 0.0.56, 0.0.57, 0.0.58, 0.0.59, 0.0.60, 0.0.61, 0.0.63, 0.0.64, 0.0.65, 0.0.66, 0.0.67, 0.0.68, 0.0.69, 0.0.70, 0.0.71, 0.0.72, 0.0.73, 0.0.74, 0.0.75, 0.0.76, 0.0.77, 0.0.78, 0.0.79, 0.0.80, 0.0.81, 0.0.82, 0.0.83, 0.0.84, 0.0.85, 0.0.86, 0.0.87, 0.0.88, 0.0.89, 0.0.90, 0.0.91, 0.0.92, 0.0.93, 0.0.94, 0.0.95, 0.0.96, 0.0.97, 0.0.98, 0.0.99rc0, 0.0.99, 0.0.100, 0.0.101rc0, 0.0.101, 0.0.102rc0, 0.0.102, 0.0.103, 0.0.104, 0.0.105, 0.0.106, 0.0.107, 0.0.108, 0.0.109, 0.0.110, 0.0.111, 0.0.112, 0.0.113, 0.0.114, 0.0.115, 0.0.116, 0.0.117, 0.0.118, 0.0.119, 0.0.120, 0.0.121, 0.0.122, 0.0.123, 0.0.124, 0.0.125, 0.0.126, 0.0.127, 0.0.128, 0.0.129, 0.0.130, 0.0.131, 0.0.132, 0.0.133, 0.0.134, 0.0.135, 0.0.136, 0.0.137, 0.0.138, 0.0.139, 0.0.140, 0.0.141, 0.0.142, 0.0.143, 0.0.144, 0.0.145, 0.0.146, 0.0.147, 0.0.148, 0.0.149, 0.0.150, 0.0.151, 0.0.152, 0.0.153, 0.0.154, 0.0.155, 0.0.156, 0.0.157, 0.0.158, 0.0.159, 0.0.160, 0.0.161, 0.0.162, 0.0.163, 0.0.164, 0.0.165, 0.0.166)
ERROR: No matching distribution found for langchain==0.0.174

换个pypi源试一下，最好直接用pypi.org
zhubao315 @.***>于2023年5月23日 周二10:36写道：

ERROR: Could not find a version that satisfies the requirement
langchain==0.0.174 (from versions: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5,
0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.10, 0.0.11, 0.0.12, 0.0.13, 0.0.14, 0.0.15,
0.0.16, 0.0.17, 0.0.18, 0.0.19, 0.0.20, 0.0.21, 0.0.22, 0.0.23, 0.0.24,
0.0.25, 0.0.26, 0.0.27, 0.0.28, 0.0.29, 0.0.30, 0.0.31, 0.0.32, 0.0.33,
0.0.34, 0.0.35, 0.0.36, 0.0.37, 0.0.38, 0.0.39, 0.0.40, 0.0.41, 0.0.42,
0.0.43, 0.0.44, 0.0.45, 0.0.46, 0.0.47, 0.0.48, 0.0.49, 0.0.50, 0.0.51,
0.0.52, 0.0.53, 0.0.54, 0.0.55, 0.0.56, 0.0.57, 0.0.58, 0.0.59, 0.0.60,
0.0.61, 0.0.63, 0.0.64, 0.0.65, 0.0.66, 0.0.67, 0.0.68, 0.0.69, 0.0.70,
0.0.71, 0.0.72, 0.0.73, 0.0.74, 0.0.75, 0.0.76, 0.0.77, 0.0.78, 0.0.79,
0.0.80, 0.0.81, 0.0.82, 0.0.83, 0.0.84, 0.0.85, 0.0.86, 0.0.87, 0.0.88,
0.0.89, 0.0.90, 0.0.91, 0.0.92, 0.0.93, 0.0.94, 0.0.95, 0.0.96, 0.0.97,
0.0.98, 0.0.99rc0, 0.0.99, 0.0.100, 0.0.101rc0, 0.0.101, 0.0.102rc0,
0.0.102, 0.0.103, 0.0.104, 0.0.105, 0.0.106, 0.0.107, 0.0.108, 0.0.109,
0.0.110, 0.0.111, 0.0.112, 0.0.113, 0.0.114, 0.0.115, 0.0.116, 0.0.117,
0.0.118, 0.0.119, 0.0.120, 0.0.121, 0.0.122, 0.0.123, 0.0.124, 0.0.125,
0.0.126, 0.0.127, 0.0.128, 0.0.129, 0.0.130, 0.0.131, 0.0.132, 0.0.133,
0.0.134, 0.0.135, 0.0.136, 0.0.137, 0.0.138, 0.0.139, 0.0.140, 0.0.141,
0.0.142, 0.0.143, 0.0.144, 0.0.145, 0.0.146, 0.0.147, 0.0.148, 0.0.149,
0.0.150, 0.0.151, 0.0.152, 0.0.153, 0.0.154, 0.0.155, 0.0.156, 0.0.157,
0.0.158, 0.0.159, 0.0.160, 0.0.161, 0.0.162, 0.0.163, 0.0.164, 0.0.165,
0.0.166)
ERROR: No matching distribution found for langchain==0.0.174
—
Reply to this email directly, view it on GitHub
https://github.com/imClumsyPanda/langchain-ChatGLM/issues/436, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLH5EQLZ5VYWCEEUIMDCNLXHQPEJANCNFSM6AAAAAAYLG2Y2Y
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

ok，RUN pip3 install -r requirements.txt -i https://pypi.mirrors.ustc.edu.cn/simple/ && rm -rf pip3 cache dir

repo: imClumsyPanda/langchain-ChatGLM


text:
error enabling dangerous caves 2

.... [17:28:51 ERROR]: Error occurred while enabling DangerousCaves v2.2.2;16 (Is it up to date?)

java.lang.NullPointerException: null
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:770) ~[patched_1.15.2.jar:git-Tuinity-"d8b8905"]
at com.sk89q.worldguard.WorldGuard.getPlatform(WorldGuard.java:100) ~[?:?]
at me.imdanix.caves.regions.WorldGuard7Manager.onEnable(WorldGuard7Manager.java:63) ~[?:?]
at java.util.HashMap$Values.forEach(HashMap.java:976) ~[?:?]
at me.imdanix.caves.regions.Regions.onEnable(Regions.java:72) ~[?:?]
at me.imdanix.caves.DangerousCaves.onEnable(DangerousCaves.java:63) ~[?:?]
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:263) ~[patched_1.15.2.jar:git-Tuinity-"d8b8905"]
at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:380) ~[patched_1.15.2.jar:git-Tuinity-"d8b8905"]
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:483) ~[patched_1.15.2.jar:git-Tuinity-"d8b8905"]
at org.bukkit.craftbukkit.v1_15_R1.CraftServer.enablePlugin(CraftServer.java:472) ~[patched_1.15.2.jar:git-Tuinity-"d8b8905"]
at org.bukkit.craftbukkit.v1_15_R1.CraftServer.enablePlugins(CraftServer.java:386) ~[patched_1.15.2.jar:git-Tuinity-"d8b8905"]
at net.minecraft.server.v1_15_R1.MinecraftServer.a(MinecraftServer.java:488) ~[patched_1.15.2.jar:git-Tuinity-"d8b8905"]
at net.minecraft.server.v1_15_R1.DedicatedServer.init(DedicatedServer.java:299) ~[patched_1.15.2.jar:git-Tuinity-"d8b8905"]
at net.minecraft.server.v1_15_R1.MinecraftServer.run(MinecraftServer.java:905) ~[patched_1.15.2.jar:git-Tuinity-"d8b8905"]
at java.lang.Thread.run(Thread.java:834) [?:?]
.... [17:28:51 INFO]: [DangerousCaves] Disabling DangerousCaves v2.2.2;16

Server: Tuinity Build #106
Plugin: Dangerous caves versión: 2.2.2

Do you have WorldGuard installed?

Do you have WorldGuard installed?

yes, i have worldguard installed, this error happens when i try to install some plugin on my server such as: WorldGuardExtraFlags
But it also happened to me when I try to install another plugin like: PVPManager
I have never had this problem before.

Do you have WorldGuard installed?

Plugins (47): AnimatedScoreboard, antiRedstoneClock, BloodMoon, ChatControl, CMI, CMIPaperLib, CommandCooldown*, CoreLibs, CoreProtect, DangerousCaves, DiscordSRV, DragonEggDrop, Duels, ExtraHardMode, FastCraft, Graves, IllegalStack, InventoryRollback, LastLoginAPI, LimitPillagers, LuckPerms, MaintenanceSpigot, Matrix, Multiverse-Core, MyPet, nLogin, Oh_the_dungeons_youll_go, Parties, PerWorldInventory, PlaceholderAPI, PlayerKits, ProtectionStones, ProtocolLib, RecipeManager, ServerBooster, ServerlistMOTD*, Shopkeepers, SkinsRestorer, SmoothSleep, TAB, TabCompleteFilter, TradeSystem, UltimateTimber, Vault, VillagerOptimiser, WorldEdit, WorldGuard

And you don't use /reload command, yeah?

And you don't use /reload command, yeah?

I have not tried using the reload command

Good. Thank you for the report.

Please try latest build.

Please try latest build.

Thank you very much, when I have time to try it, I will let you know around here.

Please try latest build.

the error is already solved, try to install the wordguardextraflags plugin and the pvpmanager again and everything worked perfectly, it no longer gives an error when starting.
Thanks

That's good. Will close the issue then.

authors: frogglen imDaniX


text:
Avoid iterating in uninitialized result

Ref: https://github.com/HelloZeroNet/ZeroNet/issues/2557

LGTM, thanks!

The fix has landed in v2.1.0.

authors: gqgs imachug

repo: imachug/gevent-ws


text:
Discussions about the 'Mask'

Here is the result of the discussion that should be implemented
https://hackmd.io/@_iS0Gi_TQUqygrd9EH3-8g/r144ihxYF
@opatiny It should be divided in many issues and you may start to implement this.

Functions to implement:

[ ] setBit
[ ] getBit
[ ] getBitByIndex
[ ] setBitByIndex
[ ] setValue
[ ] getValue
[ ] getValueByIndex
[ ] setValueByIndex
[ ] convertColor
[ ] fill
[ ] clone
[ ] invert

Mask specific functions:

[ ] erode
[ ] dilate
[ ] open

To modify:

[ ] threshold should return a Mask

Should we implement all morphology functions of MatLab?
https://ch.mathworks.com/help/images/morphological-filtering.html

authors: lpatiny opatiny

repo: image-js/image-js-typescript


text:
Formatting issue

@neilmispelaar
I just handed in the assignment, but I just wanted to let you know that my cite looks best in google chrome. The reset.css is linked in my html, but when I tested my cite in different browsers, some things were off.
Thank you for all the help!

Congratulations! 🎉🚀
I’ll definitely test in a chromium based browser  and have a look at your code to see if anything stands out.

Thank you!

authors: naomileron neilmispelaar


text:
🛑 OCC is down

In 628ccea, OCC (https://occ.imedicalcloud.net/$SECRET_ENDPOINT_IMEDICAL) was down:

HTTP code: 503
Response time: 424 ms

Resolved: OCC is back up in 11dbe1e after 12 minutes.

repo: imedicalservices/statuspage


text:
WebGL2 wrong resize

https://github.com/immersive-web/cardboard-vr-display/blob/b2fd5b03fa579fecead1b3842782d7640e8ae61f/src/cardboard-vr-display.js#L298
This dosenot work if context is WebGL2
Should be:
var gl = this.layer_.source.getContext('webgl'); if (!gl) gl = this.layer_.source.getContext('experimental-webgl'); if (!gl) gl = this.layer_.source.getContext('webgl2');

Good catch, and thanks for filing! Do you have a webgl2 scene to test this on, or interested in making a PR?

Yeah, here it is -  https://github.com/immersive-web/cardboard-vr-display/pull/35
I tested this on my scene with WebGL 2 engine

Fixed via #35 -- will be in next release

authors: jsantell supervitas

repo: immersive-web/cardboard-vr-display


text:
GPIO ported

This is a minimal port of what was in the gpio module, but needs to be made safe.

So I looked closer at how the stm Hal is written here and I think a few changes would probably be beneficial. The gpio port handling is especially interesting as they do avoid the issue by using safe rust rules to avoid the issue. For imxrt the separation of the iomuxc and pads means perhaps some more rethinking is needed on that front to make it work correctly with awkward issues. For now I'm going to wrap this in a critical section from cortex-m as it's safe and correct then. I'd rather release a version that matches the API of your teensy Hal and then iterate on improvements, even if drastic, because we might have a few samples to see how the API looks and works in practice better.

repo: imxrt-rs/imxrt-rs


text:
Add a "no results for _____" to Search Results page if there are no exact hits

via bouteloua:
The search results page will show results that are close to what the search term was, which may be confusing. For example, before the genus Viettealna was added to iNat, this was the results page:

Adding a large "no results for Viettealna" above the suggested results would make it more straightforward that the search term itself had no match.

While I'm not convinced this is desirable, I'm also not entirely sure this is possible. Is the intent to make this only work for taxa? What do we do when search returns a taxon b/c it matched an outdated name, or a common name that you don't see by default? For example, if I search for "oregon myrtle" I see a taxon named "California Bay" b/c that's the common name in California, and there's no mention of Oregon myrtle. Do we show the "no results" notice then even though there clearly is a result?
IMO, we should just not do this.

Could be for any type of thing, not just taxa.
I personally wouldn't mind if the "no results found for [search query]" alert did not display when it's matching on "hidden" information like the common name Oregon myrtle.
But ideally, and this is really a separate issue/suggestion, the search results would hint at why it's matching on Oregon myrtle in the first place, e.g.:
search: oregon myrtle
instead of the text:

"Umbellularia californica is a large hardwood tree native to coastal forests of California, as well as to coastal forests extending into Oregon. It is endemic to the California Floristic Province. It is the sole species in the genus Umbellularia."

it might clarify why it's in the results by including and bolding the search query text like:

"Umbellularia californica is a large hardwood tree native to coastal forests of California, as well as to coastal forests extending into Oregon....Common Names: California bay, California bay laurel, Oregon myrtle, pepperwood...

Here's how Google handles it in their snippet from the WP page:

"Umbellularia californica is a large hardwood tree native to coastal forests of California, as well ... In Oregon, this tree is known as Oregon myrtle, while in California it is called California bay laurel, which may be shortened to California bay or ..."

IMO, term highlighting is addressing part of the issue here, and it's not entirely clear to me if we even can know when there was no exact match, so I'm going to close.

The term highlighting is great to have and I agree, a reasonable alternative to a "no exact results for _____" message if that's not possible. But it looks like it's currently highlighting some non-matching text.
Example: https://www.inaturalist.org/search?q=bouteloia
There are no actual results for "bouteloia" but it highlights fuzzy matches "bouteloua", "Bouteldja, ET, DZ", t"boutelier", and "Boutelou".

authors: boucur kueda tiwane

repo: inaturalist/inaturalist


text:
isis-module-excel-dom add column order

I found there is no way to specified column order.

maybe can use pivot excel to deal with this.

repo: incodehq/incode-platform


text:
The examples scripts are not working, need to change makeStory

makeStory -> runStory in examples folder

现在这个问题已经修好了，谢谢你的帮助！

authors: incrediblesound zoopigzoo

repo: incrediblesound/story-graph


text:
Fix typo

Fix the typo on this line.

Closed in #9.


text:
feat: implement tda consent configuration support

ENG-1394 implement tda consent configuration support

Checklist

[x] make test passes
[x] tests and/or benchmarks are included
[ ] documentation is changed or added
[x] commit message follows commit guidelines
[ ] is breaking change

Description of change

I tested locally and you can also see the tests in https://github.com/indykite/terraform-provider-indykite/actions/runs/10109999277/job/27959020793?pr=74

repo: indykite/terraform-provider-indykite


text:
Removing "Loading" text after loading?

Hello,
I couldn't find anything in the docs about how to get rid of the "Loading..." text fully after the loading is "finished"? I tried it in a Jupyter Notebook and this is the result:

Any suggestions?

Thanks for the report. It seems like in the notebook, the sequence used to erase a line and flush is somehow interpreted differently? Relevant code is here:
https://github.com/ines/wasabi/blob/2beb8fe98cdfe9cafcae0a7c7b18c9738119e337/wasabi/printer.py#L201-L202
I'd need to investigate this. The whole cursor movement stuff, erasing lines etc. is definitiely one of the trickier parts – at least, I've always found it kinda difficult to get right across platforms and configurations and there might still be cases where it fails.

I know!! I am so happy to have come across your package though! (Found it when I looked over the spaCy code!) I have had so much trouble with flushing... ugh.

I have looked into this issue myself now and cannot find a solution!

@ines do you think the newest release will help with this issue?

@kallewesterling  any solution ?

@ardyfeb I have nothing to do with the dev of this package. Ask @ines! :)

@ines Revisited this issue and it now looks like it works better, in a way. At last, the .good() message displays at the end of the loop:

However, the context manager does not generate any output in the Notebook. This is what it looks like when inside the with msg.loading() manager:

authors: ardyfeb ines kallewesterling

repo: ines/wasabi


text:
[Question]: I want to pull the new version, how to ensure that the current data is not lost.

Describe your problem
First of all, thank you very much. I love your project and have followed it since the beginning. I see that the new version has been updated a lot, I want to try, but I already have a lot of local data, can I directly pull the new project to retain the original data? Or it's already mounted in a local directory

Hello, here some recommendations:

First, make a backup copy of your current ragflow setup including your data
I recommend that you use the latest release v0.9.0 it is more stable that current dev version (i.e. in current dev version using Cohere break the Chat pages for all Knowledge Base that use Cohere LLMs)
Edit your /docker/.env file and change the line from RAGFLOW_VERSION=dev to RAGFLOW_VERSION=v0.9.0
Restart ragflow and  the new docker image for v0.9.0 will be pull, run and connect to your current Docker volumes
If roll back is needed then change back to your previous value RAGFLOW_VERSION and restart ragflow
If the update works then delete previos ragflow image to save almost 19GB
I've tested this procedure myself and it works.
Hope it helps.

Theoretically, you're not gona loss data by upgrade.
In term of data security, just backup the docker volumes.

authors: KevinHuSh apulache robertshuai

repo: infiniflow/ragflow


text:
ISPN-1625 No need to throw IllegalStateException on receiving a new view...

... on a stopped cache

Closing my own but still needing feedback about the issue

repo: infinispan/infinispan


text:
ISPN-5329 Reduce number of allocations

I have analyzed allocations during put() (into local cache) and removed some of the low-hanging fruits. Some of those could be already handled by escape analysis, but most of them cannot, IMO. Though, the difference between performance before and after was within the margin of error of the benchmark.
You can find both the benchmark and Byteman tooling for analysis at https://github.com/rvansa/benchmarks/tree/master/ispntest

Looking into this... do you have some numbers/data to compare what allocation rates were like before the fix and after?

@galderz I have attached those data to JIRA https://issues.jboss.org/browse/ISPN-5329 - I'll yet add the rates before the PR.

Updated JIRA with pre and post allocation data.

@wburns @pruivo Updated PR

@pruivo You're right, I've replaced the calls with add/addAll. And thanks for spotting the other bugs; I was considering adding guava testlib as test dependency so that I could test those collections properly, but I got some problems with that (and haven't spent much time with it, hoping that the general testsuite will catch bugs anyway - apparently it can't). I don't want to write standard collection test myself.

@rvansa one last comment... the iterators should in MiniSet should check for modifications. If the type of the set moves (eg. from SINGLE -> ARRAY or from ARRAY -> MAP) you will get a bunch of weird exceptions (ClassCastException) or results

@pruivo I didn't want to burden it with another field for modcount (MiniList gets that inherited from AbstractList, AbstractSet does not contain it), but if you think that it's beneficial, I can go for that.

@rvansa well, if you don't want to add the modcout, at least check if the MiniSet type is the same as the Iterator type...
and it would be good to see what happen if the type of the MiniSet changes during the iteration:
Set<String> set = new MiniSet<>("single-value");
Iterator<String> iterator = set.iterator();
set.add("another-value");
assertTrue(iterator.hasNext())
assertEquals("single-value", iterator.next());

and a similar with the array => map change

@rvansa The data in the JIRA only mentions the number of allocations, not the actual performance... And speaking of the number of allocations, it's pretty hard to read the numbers in the issue, maybe you change the format to something more diff-like? I used this:
diff -u <(sort -k1.20 before.txt| sed 's/(.*)//') <(sort -k1.20 after.txt | sed 's/(.*)//')

TBH I'm not convinced the additional branching in MiniList is worth the memory savings, as it makes the job of the CPU (and maybe the JIT) harder.
The MiniSet benefit seems clearer, because HashSet needs so many allocations, but here too I think a simpler implementation with only two storage options (Object[] and HashMap) may be better.
For both of them, I'm not sure the type field is needed. Since you can't really put an Object[] in the cache we can just say these collections don't work with Object[].
The synchronized versions look good, although they probably won't be as useful once we baseline on Java 9: http://openjdk.java.net/jeps/169 ;)

I also agree with @pruivo that the collections need at least some minimal tests. The core testsuite may expose bugs by itself, but why make you life harder and rely on random test failures when this should be so much easier to test than almost everything else in Infinispan? :)

Great initiative :+1:
Dan, asking to measure results as direct performance impact is very hard. All we know is that in a full system (which does many other things and runs lots of user code too) you'll generally end up in trouble with memory because of Infinispan using it all/most up for himself.
You might not be able to measure this at all by just measuring Infinispan; the problem is crossing the threshold of how much is sensible to allocate in terms of temporary objects. As long as you don't cross the threshold, it might look like (almost) free to allocate some temporary helpers, so like making a defensive copy of a Map might look like "free". But when doing such things extensively, the system falls over.
At that point the memory bandwidth is saturated, and the CPU will be mostly sitting idle. Ironically, that means that making some code less efficient will not be measured by any benchmark either, as you'll be putting to better use some CPU cycles which are otherwise wasted in idle waits for main memory, or worse trigger additional context switching exacerbating the problem of unpredictable performance per operation.
It's measurable that there is such a problem of excess heap utilization as it's pretty easy to cross all these boundaries even when using Infinispan with a pretty well written client application. The solution is to keep working on these patches, however we'll need many of these before any difference can be measured.
That said, @rvansa make sure you don't focus just on instance numbers but prioritize based on size of instances? I'm not sure how you're measuring, but the JIRA mentions that among others you're ignoring arrays.
I've sent an email many months ago highlighting the urgency of getting rid of some Collections altogether (not just optimise them), as I had used several tools (among others flight recorder and java object layout), these can also help you to identify the biggest offenders.

Well looks like that was 16+ months ago when I wrote about those tools...!
http://lists.jboss.org/pipermail/infinispan-dev/2013-December/014311.html
But I fixed it only recently:

https://issues.jboss.org/browse/ISPN-5032

Combined with this much older one, that saved approx. 130GB / second of pointless allocations on our benchmark:

https://issues.jboss.org/browse/ISPN-1678

+1 to add thourough unit tests BTW
Couldn't MiniList be replaced by LinkedList? If you expect the lists to be small, that's not much overhead over an array. Certainly all the System.arraycopy you have to perform on add/remove will defeat the point of not polluting heap with small objects.
Also, in the smallest case I think LinkedList would perform not worse than this new implementation.
Generally speaking, you're replacing some concurrent sets with "mini" concurrent sets. Can you 100% guarantee that these use cases are small? Maybe at least checking initialCapacity is in order?

@Sanne I have to disagree with you here...
When optimizing, there are clean-cut cases where we can just stop doing unnecessary stuff, but most of the time we also have to do something else instead. We can guess beforehand that that "something else" is going to be faster than the old stuff beforehand, but we also need to test that assumption after making our changes. And if we can't write a single test that shows an improvement, we have to accept that our initial assumption was wrong.
To use your LinkedList suggestion as an example... how can we possibly decide which is better, MiniList or LinkedList? Is it true for all tx sizes, or is there an "unreasonable" tx size threshold that we will ignore in our tests? My personal theory is that a specialized singly-linked list that doesn't support null values or removing elements should be the fastest option for small txs, but who knows...

@danberindei yea you're right, I overreacted a bit to highlight the other point of view. Just making the point that it's not easy to measure at all.
Sometimes one has to simply trust it, but I agree only if the difference can be "read" in the source code. As in the LinkedList example, I'm not sure of that.
To find out though, one would need a micro benchmark comparing just the List implementation behaviour and focusing on memory allocation costs only, I don't see how one could measure the difference in a full-stack Infinispan benchmark.
One would also want to see the computational difference in such a benchmark, but I'd argue that we know enough of Infinispan to know that if the memory benefit is significant, a small cost (if it's small) should be worth it.
What concerns me the most here is that some collections are replaced with "mini" implementations, but I'm not seeing strong evidence that those collections will really be small in practice.

@Sanne I can't tell you how many writes will the user usually do in one transaction. However, MiniSet set shouldn't be ever worse than HashSet (which delegates to internal HashMap anyway) and MiniList shouldn't be worse than ArrayList (for directly implemented operations), besides single switch.
I've seen similar optimizations in competitor products, therefore I've implemented this PR.
I am not objecting the fact that I should add the collections tests. And regarding performance - I've tried to do full-stack comparison of puts and gets, but for some reason I had much faster outliers sometimes so I don't trust the results :-/

@rvansa You can always ignore the outliers :) What test were you using?

@danberindei JMH, doing puts and gets against local cache. Code here https://github.com/rvansa/benchmarks/tree/master/ispntest
@Sanne And regarding LinkedList, the idea of MiniList was to replace allocating another instance (Node) with having that single object directly in the list. But I appreciate your note that size of the object is what matters rather than number of instances, I should bear that in mind, too.

Needs rebasing

Added the additional check as recommended by @pruivo and rebased. Beyond that, I ran JMH benchmark few days ago and I can see little improvement in writes (testPutImplicit inserts single entry, possibly using auto-commit transaction with transactional cache):
https://gist.github.com/rvansa/ba6195ff6ebecfdf6011

Temporarily closing.

authors: Sanne danberindei galderz pruivo rvansa


text:
ISPN-5826 Caches should be stopped in the right order in tests

https://issues.jboss.org/browse/ISPN-5826

Integrated. Thanks!

authors: anistor gustavonalle


text:
ISPN-9934 infinispan-protocol-parser-generator-maven-plugin fails on …

…Windows
https://issues.jboss.org/browse/ISPN-9934

Duplicate


text:
ISPN-12598 Log warning when switching to initial server list

The fix is already done, this just changes the debug message to a warning as suggested in https://github.com/infinispan/infinispan/pull/9474#discussion_r684257049

Thanks @danberindei

authors: danberindei ryanemerson


text:
IPROTO-392 Remove @private javadoc from generated sources

https://issues.redhat.com/browse/IPROTO-392

Thanks @tristantarrant

Solves https://github.com/infinispan/protostream/issues/327

authors: ryanemerson tristantarrant

repo: infinispan/protostream


text:
🛑 Homepage is down

In bfcd6fe, Homepage (https://infinite8.co) was down:

HTTP code: 404
Response time: 191 ms

Resolved: Homepage is back up in c70d8d5.


text:
Fresh app can't yarn install

Describe the bug
After running the command
npx ignite-cli@latest new PizzaApp
And successfully finish. Then I cd into the app folder and run yarn install. Then the following error appears:
success Saved lockfile.
$ patch-package
patch-package 8.0.0
Applying patches...
Error: Patch file found for package react-native-drawer-layout which is not present at node_modules/react-native-drawer-layout
---
patch-package finished with 1 error(s).
✨  Done in 28.40s

I have tested with node versions 18 and 20.
How can I solve this issue?
Ignite version
9.8.2
Additional info
Need to install the following packages:
ignite-cli@9.8.2
Ok to proceed? (y) y
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
System
platform           darwin
arch               arm64
cpu                16 cores     Apple M3 Max
directory          PizzaApp     /Users/user/Dev/Mobile/NewApp/PizzaApp
JavaScript (and globally-installed packages)
node               20.16.0      /Users/user/.nvm/versions/node/v20.16.0/bin/node
npm                10.8.1       /Users/user/.nvm/versions/node/v20.16.0/bin/npm
corepack         0.28.2
npm              10.8.1
yarn               1.22.22      /opt/homebrew/bin/yarn
pnpm               -            not installed
bun                -            not installed
expo               51.0.28      managed
Ignite
ignite-cli         9.8.2        /Users/user/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
ignite src         build        /Users/user/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build
Android
java               17.0.12      /usr/bin/java
android home       -            /Users/user/Library/Android/sdk
iOS
xcode              15.4
cocoapods          1.15.2       /opt/homebrew/bin/pod
Tools
git                git version 2.39.3 (Apple Git-146)   /usr/bin/git

Hi! This should be fixed by https://github.com/infinitered/ignite/pull/2736. You can try with master branch or apply the changes in the PR until we release a new version. I'm going to close this issue but feel free to reopen if that doesn't help. :+1:

Hi! This should be fixed by #2736. You can try with master branch or apply the changes from the PR until we release a new version. I'm going to close this issue but feel free to reopen if that doesn't help. 👍

Thank you for your response, can you please tell me how can I achieve that? I haven't found that on the documentation.
How can use master instead of latest version ?
Thanks in advanced

@jorgtz  No worries! You can achieve that by these steps:

git clone https://github.com/infinitered/ignite.git
cd ignite
yarn install
cd ..
./ignite/bin/ignite new PizzaApp

After running all the commands, you will have PizzaApp, and now you can run it.

cd PizzaApp
yarn ios or yarn android

Hope you can ignite your project this time!

@leonskim thanks for the instructions. I have done what you pointed me, but unfornunately the error persist.
I had to manually delete the patches/react-native-drawer-layout+4.0.0-alpha.9.patc to fix the error.
Thanks again :)

authors: jorgtz leonskim

repo: infinitered/ignite


text:
Improve types for button.presets.ts

Please verify the following:

[x] yarn ci:test jest tests pass with new tests, if relevant
[x] README.md has been updated with your changes, if relevant

Describe your PR
Improving the typings on the buttons preset by using Record<string, VIewStyle | TextStyle>.
I ran into a cryptic error that took a very long time to debug until I realized one of the custom presets I added in the textPresets was not inline-typed with an as TextStyle. Putting these top-level types on the object made the blunder easier to spot.

:tada: This PR is included in version 6.8.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: danyim infinitered-circleci


text:
Create a voting classifier ensemble for more advanced accuracy

Currently, we have two models.  The more accurate one that has type 2 errors, and the slightly less accurate one that has far more type 1 errors
We can combine them with a voting classifier and get higher accuracy.
https://medium.com/@sanchitamangale12/voting-classifier-1be10db6d7a5
Thoughts?

This can be accomplished with the simple JavaScript to weight one model over another, too.
https://tinyurl.com/yjv3ohz4

repo: infinitered/nsfwjs


text:
APK will be increased by 28 MB when adding this package

Description
When adding this package, will this increase the size of the APK by 28 MB.
APK with this package: 45.5 MB
APK without the asset folder: 17 MB
Is the asset folder with all the GIFs really needed? I assume the GIFs and images in the asset are only for the README.md, right?

Yeah assets are used only in README.

Available in 2.0.0+2

authors: lukaknezic nilsreichardt

repo: infinum/flutter-charts


text:
improved documentation for timestamp in points

I can't determine what the format for my points should be. perhaps I've missed something in the docs. If not, could you please describe what time format write_points expects?
I try epoch nanoseconds but it is not parsed:
  File "/usr/lib/python2.7/calendar.py", line 113, in weekday
    return datetime.date(year, month, day).weekday()
           │             │     │      └ 1
           │             │     └ 5
           │             └ 1493920000000000000
           └ <module 'datetime' (built-in)>
OverflowError: signed integer is greater than maximum

In the examples from the tutorial, you can see the timestamps in python datetime format (https://github.com/influxdata/influxdb-python/blob/master/examples/tutorial.py)

repo: influxdata/influxdb-python


text:
Influxdb old data not getting removed

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

Changed retention policy
drop measurement.
Delete measurement

Expected behavior:
Expected to have old data cleared off
Actual behavior:
Data is still there and none of the above commands seems to be working

I'm also having problems with DELETE not actually deleting data: https://github.com/influxdata/influxdb/issues/14612
There has also been a lot of issues reported around "drop" as well. It seems data can get into influxdb but it can never leave :)

I'll try to reproduce this today.

@disha94 @yellowpattern what version of InfluxDB are you using?

@disha94 Please describe the reproduce steps more verbosely. I tried the following with inmem and tsi1 indexes.
> select * from autogen.m
name: m
time f
---- -
0    82
> select * from hour.m
name: m
time                f
----                -
1568671625237647000 83
> drop measurement m
> select * from m
> select * from autogen.m
> select * from hour.m
>

not stale

I have tried to repro the issue using basic scenarios.
Environment:

InfluxDB OSS 1.8.1 (Since this ticket was created more than a year ago, most likely the InfluxDB version was in 1.7.x, but without a specific info I am using the latest released, at the time, influxdb)
Using all default settings in config file, e.g. index version = inmem
Data is being loaded into two databases _internal and telegraf via telegraf running locally.
_internal database has monitor RP:

name    duration shardGroupDuration replicaN default
----    -------- ------------------ -------- -------
monitor 168h0m0s 24h0m0s             1        true

telegraf database has autogen RP:

name    duration shardGroupDuration replicaN default
----    -------- ------------------ -------- -------
autogen 0s  168h0m0s             1        true

Scenario and Basic Tests:

Let telegraf write data into telegraf database and let influxdb write data into _internal database for a day

name: _internal
id database  retention_policy shard_group start_time           end_time             expiry_time          owners
-- --------  ---------------- ----------- ----------           --------             -----------          ------
1  _internal monitor          1           2020-08-18T00:00:00Z 2020-08-19T00:00:00Z 2020-08-26T00:00:00Z
3  _internal monitor          3           2020-08-19T00:00:00Z 2020-08-20T00:00:00Z 2020-08-27T00:00:00Z
4  _internal monitor          4           2020-08-20T00:00:00Z 2020-08-21T00:00:00Z 2020-08-28T00:00:00Z

name: telegraf
id database retention_policy shard_group start_time           end_time             expiry_time          owners
-- -------- ---------------- ----------- ----------           --------             -----------          ------
2  telegraf autogen          2           2020-08-17T00:00:00Z 2020-08-24T00:00:00Z 2020-08-25T00:00:00Z

Update Retention Policies on both databases:

ALTER RETENTION POLICY monitor on _internal DURATION 7d REPLICATION 1 SHARD DURATION 1h

ALTER RETENTION POLICY autogen on telegraf DURATION 1d REPLICATION 1 SHARD DURATION 1h

authors: disha94 gshif jacobmarble yellowpattern

repo: influxdata/influxdb


text:
SHOW TAG VALUES WITH key = mykey WHERE foo = 'bar' : panic

Bug report
We recently upgraded influxdb from 1.4.2 to 1.5.0 and now we have a panic when retrieving tag values : SHOW TAG VALUES FROM my_measurement WITH KEY = stack_name WHERE application_name = 'foo' [panic:runtime error: invalid memory address or nil pointer dereference]
Here is the detailed log of influxdb when the query occurs.
Mar 13 14:46:54 servername influxd[3228]: ts=2018-03-13T13:46:54.327234Z lvl=error msg="SHOW TAG VALUES FROM my_measurement WITH KEY = stack_name WHERE application_name = 'foo'
[panic:runtime error: invalid memory address or nil pointer dereference] goroutine 3100870 [running]:\n
runtime/debug.Stack(0xc5381cada0, 0xc5473e8060, 0x5e)\n
	\t/usr/local/go/src/runtime/debug/stack.go:24 +0xa7\n
github.com/influxdata/influxdb/query.(*QueryExecutor).recover(0xc420210ed0, 0xc5381cada0, 0xc5210c6420)\n
	\t/go/src/github.com/influxdata/influxdb/query/query_executor.go:451 +0xaf\n
panic(0xce4120, 0x1302970)\n
	\t/usr/local/go/src/runtime/panic.go:491 +0x283\n
github.com/influxdata/influxdb/tsdb.(*MeasurementFields).HasField(0x0, 0xc4f0060410, 0x10, 0x99c937)\n
	\t/go/src/github.com/influxdata/influxdb/tsdb/shard.go:1408 +0x26\n
github.com/influxdata/influxdb/tsdb.IndexSet.seriesByBinaryExprIterator(0xc558510000, 0x10, 0x10, 0xc4202419a0, 0xc436279344, 0x14, 0x1b9, 0xc4bae002a0, 0x0, 0x7800000000d4d240, ...)\n
	\t/go/src/github.com/influxdata/influxdb/tsdb/index.go:1833 +0xdd2\n
github.com/influxdata/influxdb/tsdb.IndexSet.seriesByExprIterator(0xc558510000, 0x10, 0x10, 0xc4202419a0, 0xc436279344, 0x14, 0x1b9, 0x12cae00, 0xc4bae002a0, 0x0, ...)\n
	\t/go/src/github.com/influxdata/influxdb/tsdb/index.go:1786 +0x476\n
github.com/influxdata/influxdb/tsdb.IndexSet.tagValuesByKeyAndExpr(0xc558510000, 0x10, 0x10, 0xc4202419a0, 0x12ce9c0, 0x1336238, 0xc436279344, 0x14, 0x1b9, 0xc5482afc50, ...)\n
	\t/go/src/github.com/influxdata/influxdb/tsdb/index.go:2144 +0x1a0\n
github.com/influxdata/influxdb/tsdb.IndexSet.MeasurementTagKeyValuesByExpr(0xc558510000, 0x10, 0x10, 0xc4202419a0, 0x12ce9c0, 0x1336238, 0xc436279344, 0x14, 0x1b9, 0xc5482afc50, ...)\n
	\t/go/src/github.com/influxdata/influxdb/tsdb/index.go:2293 +0xca1\n
github.com/influxdata/influxdb/tsdb.(*Store).TagValues(0xc420001980, 0x12ce9c0, 0x1336238, 0xc4dcb1ce00, 0x10, 0x10, 0x12cae00, 0xc50f583f50, 0x10, 0x40, ...)\n
	\t/go/src/github.com/influxdata/influxdb/tsdb/store.go:1517 +0x946\n
github.com/influxdata/influxdb/coordinator.LocalTSDBStor
Mar 13 14:46:54 servername influxd[3228]: e.TagValues(0xc420001980, 0x12ce9c0, 0x1336238, 0xc4dcb1ce00, 0x10, 0x10, 0x12cae00, 0xc50f583f50, 0x32f2d7fe, 0x109d537404, ...)\n
	\t<autogenerated>:1 +0x97\n
github.com/influxdata/influxdb/coordinator.(*StatementExecutor).executeShowTagValues(0xc4202378f0, 0xc52cc83500, 0xc4668afc48, 0xdf7588, 0xf)\n
	\t/go/src/github.com/influxdata/influxdb/coordinator/statement_executor.go:1066 +0x840\n
github.com/influxdata/influxdb/coordinator.(*StatementExecutor).ExecuteStatement(0xc4202378f0, 0x12ce780, 0xc52cc83500, 0x0, 0x11f4, 0xc4255a5810, 0xc5210c6420, 0xc4a10735c0, 0xc4e663801c, 0x6, ...)\n
	\t/go/src/github.com/influxdata/influxdb/coordinator/statement_executor.go:194 +0x2937\n
github.com/influxdata/influxdb/query.(*QueryExecutor).executeQuery(0xc420210ed0, 0xc5381cada0, 0xc4e663801c, 0x6, 0x12ce9c0, 0x1336238, 0x2710, 0x0, 0x0, 0x0, ...)\n
	\t/go/src/github.com/influxdata/influxdb/query/query_executor.go:389 +0xae8\n
created by github.com/influxdata/influxdb/query.(*QueryExecutor).ExecuteQuery\n
	\t/go/src/github.com/influxdata/influxdb/query/query_executor.go:285 +0xc3\n" log_id=06ohrsP0000 service=query

I work with seuf, In grafana all dashboard where 2 variables are linked are broken :(
I liked Grafana / influxdb a lot :(
Something strange, many measurement have a fake column call "" due to comma in tag_value maybe
---->SHOW MEASUREMENTS WHERE ""=''<-----
return no value before 1.5
make quality back again

I work with seuf, In grafana all dashboard where 2 variables are linked are broken :(
I liked Grafana / influxdb a lot :(
Something strange, many measurement have a fake column call "" due to comma in tag_value maybe
---->SHOW MEASUREMENTS WHERE ""=''<-----
return no value before 1.5
make influxdb great again

Trouble with user_agent
This makes trouble :
Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36
This does not :
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0
Maybe parentheses with simple comma inside in tag value !!!

It seems inserting key value like (,,)***
stuff separated by comma(s) inside parenthesis generate extra columns with empty title
make a simple test demain (means tomorrow)

This is fixed in #9551. It will be part of a 1.5.1 release, currently due the end of this week or early next.
@lipoteFR your issue looks to be a duplicate of #9545, which I'm looking at today. If you have some extra information on reproducing it, could you add it to that issue?

@lipoteFR I just found your other issue. Thanks for the repro steps!

authors: e-dard lipoteFR seuf


text:
Wire up DIFFERENCE aggregate

If the query is like this:
SELECT DIFFERENCE(value)
FROM cpu
WHERE time > now() - 4h

It will return a series with the difference between each value.
If the query is like this:
SELECT DIFFERENCE(MIN(value))
FROM cpu
WHERE time > now() - 4h
GROUP BY time(5m)

It will return the difference if the min value for each 5 minute window of time.

From (tsdb/executor.go#L443)[https://github.com/influxdb/influxdb/blob/master/tsdb/executor.go#L443] this seems to be implemented now, is that correct?

Any news on when this might come?

I don't see this issue on 9.5 changelog https://github.com/influxdb/influxdb/blob/master/CHANGELOG.md

@Vebryn it hasn't been completed, so it is not on the CHANGELOG.

Ok, thank you, let's wait and see

Looking forward to this.

The query engine is undergoing heavy refactoring.  Removing help wanted label for now.

@corylanou - what kind of heavy refactoring? Are you intending to support joins, more complex multi-measurement queries, etc?

We use collectd to collect metrics from all our infrastructure. For A LOT of metrics sends the total cumulative values up until a certain point (CPU time for example). Without difference we have no way to show this values in a meaningfull way correctly. When will this be implemented in the 0.9 line?

Hi, Are there any ETA for this when it will be released?
Or what is other way of displaying bandwidth usage? We know that linux increases this number over and over: /sys/class/net/eth0/statistics/rx_bytes, so is there any way to do difference on InfluxDB level, or so far I have to do that differently by "collector"?

What about non_negative_derivative?

Could you please add a shorter alias for this function, like "diff" or "delta" instead of "non_negative_derivative"!

Is there currently anyway to define different grouping functions for time and between series? So we can do mean_series(last("value") - first("value")).

@jazdw no, there are no composite functions yet. That specific case is an interesting feature request, can you open a new issue to track it?

As mentioned in my post to the mailing list we are experimenting with simplifying our open GitHub Issues. This feature request has been rolled into an aggregate issue for all function requests, so that we can close this issue until we are ready to work on it.
You may continue to make comments here. Closing the issue does not mean we are rejecting this idea.

I'm beginning to work on this.

I know this is an old closed issue, but it still pops up when googling.
As requested by some previous commenters, the solution for computing bandwidth usage for a specific time period (or disk usage increase / decrease) is described in the final comments of https://github.com/influxdata/influxdb/issues/7076 and involves the usage of difference and cumulative_sum.

authors: Gibheer Placinta Vebryn beckettsean corylanou jazdw jchauncey jsternberg marcinpraczko mirath pauldix superdump tothandor

repo: influxdb/influxdb


text:
Implemented support for multiple types.db files in config.toml.

[ ] CHANGELOG.md updated
[x] Rebased/mergable
[x] Tests pass
[x] Sign CLA (if not already signed)

Fixes #1110

Unfortunately this is a breaking change. Existing collectd configuration will not work with this code.
Hmmm, need to think about this.

Instead, supporting a directory where multiple types files could be imported from would not be a breaking change. The path for that could be added as a new config option, and would not be a breaking change. And if that directory is non-zero, then the types files are loaded from there (every file in the directory is imported).
@pires ?

@otoolep yes, I agree.

@otoolep done. I have decided to support both typesdb for single file (current behavior) and typesdb-dirs for multiple directories.
However, if any of these directories include a file that can't be parsed, the entire operation will fail. Comments on this?

@otoolep tests are failing but none related to this PR, am I right?
--- FAIL: TestServer_Query_Aggregates_FloatMany (10.06s)
	server_test.go:2544: distinct as call - float: unexpected results
		query:  SELECT DISTINCT(value) FROM floatmany
		exp:    {"results":[{"series":[{"name":"floatmany","columns":["time","distinct"],"values":[["1970-01-01T00:00:00Z",[2,4,5,7,9]]]}]}]}
		actual: {"results":[{"series":[{"name":"floatmany","columns":["time","distinct"],"values":[["1970-01-01T00:00:00Z",null]]}]}]}

@pires -- yeah those test failures are something else we're working on.

@otoolep fixed the test nit. Anything else?

This looks sane to me, though I need to study the gollectd code to ensure what we are doing to merge the files is actually valid. I'm sure you've done this, obviously we need peer review.
Thanks @pires

@otoolep I have a couple checks for that on both tests I added. See https://github.com/influxdb/influxdb/pull/4740/files#diff-1706d1356c016e994827ad3d884a501aR242 onwards.

First test-case should load a specific file with doesn't include custom-metric.
Second test-case should load both files in directory and have custom-metric.
Both test-cases should have all the keys included in the specific file loaded in the first test-case, but I chose to validate only absolute.

Do you think I should add more tests? If so, can you provide more details?
Thank you!

@kimor79 the user should take care of that, if and only if directories are configured.
@otoolep anything missing?

The code looks good, but I need to study it more closely and I may also need to actually test with a collectd setup. It might be a little while before we merge this.

@otoolep thank you for the feedback. Let me know if there's anything we can do to improve it.

@pires -- can you actually perform some system test on this? Have collectd send the data to your system, and ensure it actually works the way you expect?

@AndrejKorshikov want to try what @otoolep as asked for?

@pires -- yes, I'll try it in a couple of days, with my collectd setup getting info from UPSes and cooling systems.

OK, thanks for any help you can provide. We must be sure not to break existing collectd functionality, as well be sure that the new functionality works, at a system-test level.

@AndrejKorshikov eagerly awaiting on your feedback.

@pires sorry for delay, I have no access to my collectd setup at this moment. I hope I'll be able to perform tests this week.

hey, any updates on this?

@xaniasd we need system tests to validate the PR behavior.

@pires hi, glad to help if possible, what kind of system tests are needed? the test cases described above can be executed with a single VM, unless I'm missing something.
Another remark, if I may: collectd configures the types.db files in a space-separated list of strings, like so:
TypesDB "/usr/share/collectd/types.db" "/etc/collectd/my_types.db"
wouldn't this work here too? and I believe it's not a breaking change like this (@otoolep?)

I'm a little confused when reading the code. The added test (and other comments) refer to the *.db names as files, but they are processed as directories in the code (and the name is typesdb-dirs).
Is the goal to list multiple directories where every file found in them is treated as a typesdb file to be proccessed? Or is the goal to explicitly list additional typesdb files that should be processed?
@kimor79 made the comment that other files might exist alongside custom types.db files, and @xaniasd mentioned that the TypesDB config option in collectd is a list of files, not directories.
Given all that, I would think the new config option should be typesdb-extra and be a list of files to be processed, not directories. The current PR code overrides existing entries with the extra files. Is that the desired behavior? Or should the extra files only add new entries, leaving existing entries untouched.
I'm not familiar with collectd, so I'm not sure if overriding defaults or just adding custom types is more common/desired. Either way, the behavior should at least be documented in a comment somewhere (probably the new config field), and ideally there would be a test with multiple files to ensure the code matches the expected behavior (override or otherwise).
Also, @xaniasd, we can't use space separated strings because InfluxDB uses toml config files, which treat strings and arrays of strings differently.

@joelegasse we use collectd quite extensively, so to clarify:

I think that it's more common to add custom types (for custom metrics) than overriding defaults (web interfaces for collectd use predefined/default collectd settings so changing them is not useful).
Syntax for TypesDB in collectd configuration is space separated string of paths (as @xaniasd mentioned):

TypesDB File [File ...]
Set one or more files that contain the data-set descriptions.

(from https://collectd.org/documentation/manpages/collectd.conf.5.shtml#global_options)

Closing this in favor of #6908 since that one isn't a breaking change.

authors: AndrejKorshikov joelegasse jsternberg mengelmann otoolep pires xaniasd


text:
Update documentation on uninterpreted types

Closes #1218
Update documentation on new format of uninterpreted constants introduced by #1130.

Codecov Report

Merging #1312 (518328a) into unstable (bf7f7a0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           unstable    #1312   +/-   ##
=========================================
  Coverage     74.81%   74.81%
=========================================
  Files           333      333
  Lines         10787    10787
  Branches        536      536
=========================================
  Hits           8070     8070
  Misses         2717     2717

Impacted Files
Coverage Δ

...he/io/annotations/parser/CommentPreprocessor.scala
92.77% <0.00%> (-1.21%)
:arrow_down:

.../forsyte/apalache/tla/pp/ConstSimplifierBase.scala
97.43% <0.00%> (+1.28%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-commenter thpani

repo: informalsystems/apalache


text:
End user installation instructions

INSTALLATION.md
Closes #94.

I pushed a commit with my suggestions.
What I tried to accomplish with the changes is the following:

give a solution to people who are looking for a quick c/p  (I added a section in the end and linked it from the beginning)
give a solution for obtaining python 3.10 without having to go through those lengthy realpython.com installation instructions.

Let me know how it looks to you, @andrey-kuprianov . (It is quite an intervention to the original text so feel free to modify further or insist on reverting it if it looks like a completely wrong direction.)

Wow, it looks terrific, @ivan-gavran! Thanks for the additions:)

Before merging, I'd like to get feedback from @rnbguy , especially for the TL;DR section: does this go through on Linux? In particular, is it true that pyenv is not needed there and that python 3.10 will be installed when apt is updated?

authors: andrey-kuprianov ivan-gavran

repo: informalsystems/atomkraft


text:
🛑 Uvirtual is down

In 3f10899, Uvirtual (https://uvirtual.unimonserrate.edu.co/) was down:

HTTP code: 503
Response time: 1215 ms

Resolved: Uvirtual is back up in dbc600c after 565 days, 17 hours, 51 minutes.

repo: infraestructuraidt/status


text:
🛑 Academusoft is down

In c4f4801, Academusoft ($SECRET_ACADEMUSOFT) was down:

HTTP code: 503
Response time: 1545 ms

Resolved: Academusoft is back up in 0b4631c.


text:
🛑 Academusoft is down

In 93e7bdf, Academusoft ($SECRET_ACADEMUSOFT) was down:

HTTP code: 503
Response time: 1311 ms

Resolved: Academusoft is back up in ac58aa3.


text:
Confusion about the dataset setting of the paper

Thanks for the cool work.
However i am a little bit confused about the experiment setting.
In fig 1, it says given a set of monocular multi-view images and camera poses.
In section 3.2, it says "this can be practical for an MVS capture at a certain moment but not for a monocular capture in a temporal sequence". It means your method is not a Multi-view capture.
My question is what's the real setting of your dataset and experiment?
I am not really familiar with dynamic scene reconstruction so my question might be stupid.
Thanks again.

Hi, thanks for your interest in our work.
I have updated a new version on arxiv. What we want to express is that the method proposed by Dynamic Gaussian can only be used to represent multi-view scenes, while our method can be applied to monocular scenes. Therefore, in the paper, we expanded our method from the application of monocular scenes. Our dataset in the experiment is definitely monocular (except for the ablation figure, which is a multi-view scene from Neu3D).


text:
Make sure the appropriate error message is returned when creating a token while authentication is disabled

Description
closes #3900
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Failed to merge changes into iso4 due to merge conflict.Please open a pull request for these branches separately.

Merged into branches master in 9edfda9b40b823b768848fe0bd67d3c8a00ce59c

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches. You can safely close this pull request and delete the source branch.

This branch was not deleted as it seems to still be in use.

Processing #4201.

authors: andraskvr inmantaci

repo: inmanta/inmanta-core


text:
Add support to cancel background tasks when the server is stopped

Description
Same PR as #4045, but applies on the iso4 branch. The original PR was never merged on the iso4 branch.
Self Check:

[ ] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches iso4 in 25a8305bb4c921c8d3ae87a6f9ccc048a9520ac6

authors: arnaudsjs inmantaci


text:
Improve logging in VirtualEnv class

Description
closes #4343
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] ~End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )~

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Failed to merge changes into iso4 due to merge conflict.Please open a pull request for these branches separately.

Merged into branches master in dd6e87f59f0b647f6f1c8ab59f2f936fde4f7a4e

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches. You can safely close this pull request and delete the source branch.

This branch was not deleted as it seems to still be in use.

Processing #4380.


text:
Issue/1871 fix create instance button (#2073)

Pull request opened by the merge tool on behalf of #2073

Merged in 628bdbd39fd6bb8116c17618dd37455fd8dd1797

repo: inmanta/web-console


text:
Issue/2266 deploy state color resources

Description

Add labels with colors for deploy status
Small cleanup of Resources page components
Small cleanup of color configs

closes #2266
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Code is clear and sufficiently documented
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master, iso4 in e66419ee0724562de999609065de7a9c7ffd9e72

authors: Stijnkool inmantaci


text:
Build(deps-dev): Bump @typescript-eslint/eslint-plugin from 5.37.0 to 5.38.0 (#4068)

Pull request opened by the merge tool on behalf of #4068

Merged in c1cfcde2187cedf7c3381dfae5d66f1d661c220b


text:
Block editing instances with strict_modifier in the composer

Description
Review after merging pull request #5672 - I based that branch on it to avoid unneccesary conflicts
closes #5343
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Code is clear and sufficiently documented
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

I'll reopen after the merge


text:
Vite manifest not found at: /home/???????/cart_shop/public/build/manifest.json

I Working on project that working with laravel 9 and Vite with  laravel-vite,
In Dev environment all thing working fine, but in production cPanel server I has this issue
Vite manifest not found at: /home/???????/cart_shop/public/build/manifest.json

# With

Missing Vite Manifest File
Did you forget to run `npm install && npm run dev`?

I tried to solve the problem but nothing work, I need to change the public folder and the sup folder build file place  from vite.config.js but I don't find the way to do that.
Note that: the file sequence is changed in cPanel shared server from
- home
    - public_html
        - cart_shop
           - Root
           - public
           - etc

To
- home
    - public_html
       - public files and folders  // I changed the index URLs too.
- cart_shop
    - Root
    - etc

Can you check https://github.com/innocenzi/laravel-vite/tree/feat/custom-manifest-path if that fits your use case?
You would do this in a service provider:
Vite::findManifestPathWith(function (Configuration $configuration) {
    // Custom manifest path generation logic
    $buildPath = $configuration->getConfig('build_path');

    return base_path($buildPath . '/public_html/manifest.json'); // adapt for your needs
});

Dear @innocenzi
where I can Add this configuration .

Use the branch instead of the published package (look up "composer repositories"), and use the snippet above (adapt it) in AppServiceProvider.

@sumer5020 did it work?

@sumer5020 did it work?

Yup, many thanks bro.

repo: innocenzi/laravel-vite


text:
import issues

Describe the bug
When I made the PR I tested using the storybook app, now Im trying to use in another application and getting errors:
if I try the default import:
import docx from "remark-docx";

// error
C:\Users\55119\Elucidário.art\elucidario\node_modules\.pnpm\remark-docx@0.1.2\node_modules\remark-docx\lib\index.js:4
var unistUtilVisit = require('unist-util-visit');
                     ^

Error [ERR_REQUIRE_ESM]: require() of ES Module C:\Users\55119\Elucidário.art\elucidario\node_modules\.pnpm\unist-util-visit@4.1.2\node_modules\unist-util-visit\index.js from C:\Users\55119\Elucidário.art\elucidario\node_modules\.pnpm\remark-docx@0.1.2\node_modules\remark-docx\lib\index.js not supported.
Instead change the require of C:\Users\55119\Elucidário.art\elucidario\node_modules\.pnpm\unist-util-visit@4.1.2\node_modules\unist-util-visit\index.js in C:\Users\55119\Elucidário.art\elucidario\node_modules\.pnpm\remark-docx@0.1.2\node_modules\remark-docx\lib\index.js to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (C:\Users\55119\Elucidário.art\elucidario\node_modules\.pnpm\remark-docx@0.1.2\node_modules\remark-docx\lib\index.js:4:22)
    at async Promise.all (index 0) {
  code: 'ERR_REQUIRE_ESM'
}

Node.js v18.12.1
 ELIFECYCLE  Command failed with exit code 1.

if I try to import the mjs module:
import docx from "remark-docx/lib/index.mjs";

// error
file:///C:/Users/55119/Elucid%C3%A1rio.art/elucidario/node_modules/.pnpm/remark-docx@0.1.2/node_modules/remark-docx/lib/index.mjs:4
import { convertInchesToTwip, Packer } from 'docx';
                              ^^^^^^
SyntaxError: Named export 'Packer' not found. The requested module 'docx' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'docx';
const { convertInchesToTwip, Packer } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
    at async loadESM (node:internal/process/esm_loader:91:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)

Node.js v18.12.1
 ELIFECYCLE  Command failed with exit code 1.

It seems that default import of remark-docx is treated as commonjs but unist-util-visit is published as esm only.
So it may be solved if you transpile unist-util-visit to commonjs, such as transpilePackages in Next.js.
I'm not sure why remark-docx is detected as commonjs. It depends on your build tools.

Actually I'm not using any building script.
I created this repo with a minimal test, just as documented in README.md and the error still occurs: https://github.com/hgodinho/remark-docx-test

Published in 0.1.4.

authors: hgodinho inokawa

repo: inokawa/remark-docx


text:
How can I implement countries and cities?

I've tried doing it with groups but then I'd need to create the same section for each city multiple times - a cumbersome task.

This feature is currently not implemented.
I think the best way is to create extra models for Country/City and add it as extra fields to the Item models.

Hi @songproducer !
I added Areas which you can use now to separate items while having the same Section/Group structure!

authors: inoks songproducer

repo: inoks/django-classified


text:
Possible breaking changes in config files for NodeConfigFile attribute

From this Slack thread: https://input-output-rnd.slack.com/archives/CA919E6Q6/p1661278131542139
it looks like cardano-node configuration files under https://github.com/input-output-hk/cardano-node/tree/master/configuration
may be removed in the near future. Some of our db-sync configs rely on those files, like mainnet:
https://github.com/input-output-hk/cardano-db-sync/blob/master/config/mainnet-config.yaml#L15
The current source of truth for config files is: https://book.world.dev.cardano.org/environments.html

Would it be reasonable to only keep configs for mainnet in repositories, as an alternative way to the book? For anything else we can link the book. This is what db-sync does.
We can delete the configs and adjust documentation if node also deletes them.

Btw I would avoid private (slack) links in github. We're trying to turn db-sync more into an open source project and private links may discourage people.

Would it be reasonable to only keep configs for mainnet in repositories, as an alternative way to the book? For anything else we can link the book. This is what db-sync does.
We can delete the configs and adjust documentation if node also deletes them. Thank you for bringing this up!

I think that's a good idea @kderme .

authors: ArturWieczorek kderme

repo: input-output-hk/cardano-db-sync


text:
SRE-118 multi-node cluster test framework for QA.

The user-supplied test script is run on an edge node and can use cardano-cli and cardano-node in PATH, as well as the following environment variable :

CARDANO_NODE_SOCKET_PATH
CONFIG_DIR (containing genesis and all genesis and core nodes keys)
TOPOLOGY (path to topology file with all other nodes of the cluster);

To run the test:
nix build -f default.nix nixosTests.qaCluster
(test to be duplicated with different arguments if needed).

replaced by #2026.

repo: input-output-hk/cardano-node


text:
Enable more hlint rules

Enable the following default hlint rules:

Move brackets to avoid $
Redundant bracket
Redundant flip
Use camelCase
Use newtype instead of data
Redundant $
Reduce duplication
Use first
Use record patterns
Use :
Use const

In some cases, I've selectively re-enabled the rule on a file-by-file bases by adding HLINT ignore pragmas to the file.  I did this in cases where it seemed stylistically sensible to relax those rules in those circumstances.  For example we break the camelCase rule in function names of property tests.

Probably worth squashing those down to a single commit, and listing the current commit messages as points.

Is HLint enforced by CI? If not, I'm afraid you'll have to clean up HLint warnings created by others from time to time.

Is HLint enforced by CI? If not, I'm afraid you'll have to clean up HLint warnings created by others from time to time.

HLint is already enforced by CI.

bors merge

authors: erikd mrBliss newhoggy


text:
Rework storage layer to store blocks and undos in the same file.

This is an attempt at "simplest possible change" which moves us in the
direction of using fewer files for the block storage. However, this also
tries to tidy up some of the way 'SerializedBlunds' were handled. It avoids
cases where we end up doing serialize/deserialize loops, and tries to remove
a bunch of unneeded functions.
I still don't like this way of handling things - in particular, the contract
on how exactly a Blund is stored is completely implicit, yet not isolated
to this module.
Description

Linked issue

Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🛠 New feature (non-breaking change which adds functionality)
[x] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[x] I have read the style guide document, and my code follows the code style of this project.
[~] If my code deals with exceptions, it follows the guidelines.
[x] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

QA Steps
Run against an existing node DB and verify that existing blocks load correctly.
Screenshots (if available)

This looks good Nick, but I don't want to merge we get some pretty thorough testing on it. I've asked devops for some help on this.
I suspect that in it current state it, if the software is installed on a clean machine and syncs the whole blockchain, then everything will just work.
What happens on a machine that already has the separate block/undo files?

Tested:
Create a new network with this version. Start daedalus. Create a new wallet, send it 500ADA from the bootstrap wallet. Remove the wallet DB, then restart the wallet and restore from backup. Confirm that wallet is successfully restored with 500ADA balance.
Create a new network on develop. Let a number of blocks get processed. Start daedalus. Create a new wallet, send it 500ADA from the bootstrap wallet. Stop this network, copy across the node DB to a clean checkout of this commit. Run the network without rebuilding the DB. Load daedalus and restore the wallet - confirm its balance.

I would love to get all the testing infra for launching nodes etc into Haskell so we can more easily write that exact integration test.
Can you paste  a list of commands you ran in order to do that, so I can reproduce it locally?

@parsonsmatt I can give a rough idea, though a bunch of it was done through the actual Daedalus client. It should be possible by poking the API directly, though I haven't done this.
git worktree add ../cardano-sl.develop develop
cd ../cardano-sl.develop/
stack build
mkdir run && cp -r ./scripts/tls-files/ ./run/
./scripts/launch/demo-with-wallet-api.sh

At this point one can launch the 'develop' version. Import the genesis wallet from daedalus/features/support/default-wallet.key. Create a new wallet, transfer some ADA. Make sure it gets confirmed in some blocks.
./scripts/launch/kill-demo.sh
cp -R ./run ../cardano-sl/
cd ../cardano-sl
NO_REBUILD=1 ./scripts/launch/demo-with-wallet-api.sh

Launch daedalus again. It will take a while to connect since it's rebuilding the wallet DB. You should be able to restore the wallet from backup and confirm the balance.

@cleverca22 asks (in Slack but copied here):

1: we need to somehow clean up all .undo files on startup, to regain the lost space

Yes, forgot about that. Is it worth, having a process that checks for separate block/undo files, compacting them into blund files and deleting the old ones?

2: do the old .block files still contain enough data to reconstruct those undos?

No. The solution chosen puts the block and undo in a single file, so we actually keep the undos for now.

3: what happens if an older cardano is ever ran on this state?

It would need to download all the blocks again. I can't see a way around this. We simply can't make old software compatible with the new code.

one thought i had on how to migrate things
any time you read a .block and .undo pair, re-write them as a .blund and then delete the input pair

One option to address this issue would be to write a trivial tool that can be manually run and splits the blund files into separate block and undo files.

We could call it the "unblundler".

Closing this as #2905 was built on top of this and has already been merged.

repo: input-output-hk/cardano-sl


text:
Translate integration tests for active/next delegation into unit tests.

Context
When reviewing and testing https://github.com/input-output-hk/cardano-wallet/issues/1342 we have created 12 integration tests (tagged STAKE_POOL_NEXT) that fairly comprehensively test the requirement. They have been quite long to execute adding ~9 minutes of execution to the overal integration test suite exec time and as a result made CI to timeout.
The idea here is to translate all or of some of them into unit tests to cut on test execution time and still have reliable tests.
There is an open PR with the integration tests -> https://github.com/input-output-hk/cardano-wallet/pull/1374. It can be used to translate the tests.
Decision
Translate STAKE_POOL_NEXT tests from https://github.com/input-output-hk/cardano-wallet/pull/1374 into unit tests.
Acceptance Criteria

Development

QA

@piotr-iohk @paweljakubas I've factored out the logic responsible for controlling the delegation transitions as guardJoin and guardQuit.
From these two pure functions, we can now easily tests various delegation scenarios given some initial WalletDelegation state, and control that the outcome is as expected. I didn't think much through it but I believe there also exists some nice properties to try out.
See: https://github.com/input-output-hk/cardano-wallet/commit/718f931ef53846a325b816a09169adb927b987be on KtorZ/1386/unit-tests-delegation-transitions. Feel free to add anything you want on this branch :+1:

authors: KtorZ piotr-iohk

repo: input-output-hk/cardano-wallet


text:
Can't build: Unsupported tarball from /tmp/with-repo-archive4121/foo.tar

Information
-

Version
master

Platform
Linux

Steps to Reproduce
git clone https://github.com/input-output-hk/cardano-wallet.git
cd cardano-wallet
git checkout master
stack build --test --no-run-tests
Expected behavior
Build completed.
Actual behavior
Cloning 460ee17d22cacb3ac4d90536ebe90500a356a1c9 from https://github.com/input-output-hk/cardano-ledger-specs
Unsupported tarball from /tmp/with-repo-archive4121/foo.tar: Symbolic link dest not found from shelley/chain-and-ledger/cddl-spec to executable-spec/cddl-files/, looking for shelley/chain-and-ledger/executable-spec/cddl-files.
This may indicate that the source is a git archive which uses git-annex.
See https://github.com/commercialhaskell/stack/issues/4579 for further information.

Yes, the ledger revision from master is currently broken. See https://github.com/input-output-hk/cardano-wallet/pull/2056

Fixed in fece720cb18d9676c4f1f6b0d3a69a37fab93f1c.

authors: Fell-x27 KtorZ rvl


text:
Fix haskell-language-server build

Issue Number
ADP-1612
Summary
I've fixed the haskell-language-server build so that I could include it in my nix developer documentation (ADP-1536).

Alters the hie-bios invocation to skip files:

In the prototype/ directory, because this directory has a separate cabal.project file and so will need a separate hie-bios invocation.
In the lib/core-integration/extra/ directory, because these are Plutus scripts intended to be serialised and placed in the tests, they are not intended to be built with the project.

Includes a hie-bios invocation in the Buildkite build so that the haskell-language-server and hie-bios can be tested on each commit (preventing future breakages).
Adds documentation on how to configure, use, and troubleshoot haskell-language-server.
Setup haskell-language-server to check every file in the project on a nightly basis (takes >30 mins on Buildkite, so don't want to do it per-commit). I've also signed myself up to be notified of nightly build failures.

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+


text:
Implement new /api/v0/challenges/{id}/{voter_group_id} endpoint

Adding new /api/v0/challenges/{id}/{voter_group_id} endpoint which acts mostly the same as /api/v0/challenges/{id} but also filtering proposals by voter_group_id

@dkijania agreed, will do it in the separate PR. Will create a ticket for testing all endpoints from the "challenges" group

repo: input-output-hk/catalyst-core


text:
standardise keystore

This PR is about making our keystore meet the standards set out in: https://github.com/ethereum/wiki/wiki/Web3-Secret-Storage-Definition
Implemented:

2 AES cipher modes: CBC and CTR
2 key derivation functions: scrypt and pbkdf2-hmac-sha256

Both parity and geth follow this standard. Both use AES-CTR. Geth uses scrypt, and parity uses pbkdf2.
The names of key JSON files are not defined in the standard. This implementation name the files along the pattern UTC--[ISO8601 date]--[account address]. Geth and parity use similar but different (also among themselves) names. Our implementation relies on the address being part of the name (it can be changed).
At the moment the PR lacks good test vectors for AES-CBC and AES-CTR ciphers.

I'm having an issue when testing, maybe I'm doing something wrong but it seems that the personal_newAccount method is taking too long to run and I'm getting the error:
The server was not able to produce a timely response to your request.
Please try again in a short while!

I'm having an issue when testing, maybe I'm doing something wrong but it seems that the personal_newAccount method is taking too long to run and I'm getting the error

@ntallar I'd say it must be your setup. I used this exact branch in the demo last week where I showed personal_newAccount working. Is that the only method that fails for you?

@adamsmo @ntallar I've addressed all your comments

authors: ntallar rtkaczyk

repo: input-output-hk/etc-client


text:
Document capturing counters

we can capture a number of different counters/metrics:
data CounterType = MonotonicClockTime
                 | MemoryCounter
                 | StatInfo
                 | IOCounter
                 | CpuCounter
                 | RTSStats

provide an example for each and add to documentation.

maybe we can simplify this:
        tr' <- appendName "observeDownload" tr
        bracketObserveIO tr' "" $ do
             logNotice tr' "msg"

to something like:
        bracketObserveIO tr' "observeDownload" $ \tr' -> do
             logNotice tr' "msg"


text:
Less I/O

description

[x] removing hard dependencies on IO, replaced with MonadIO m => m,
and also added bracketObserveX which does not depend on MonadCatch m
this was necessary to make benchmarking in cardano-ledger work.

checklist

[x] compiles (cabal new-clean; cabal new-build)
[x] tests run successfully (cabal new-test)
[ ] documentation added and created (cd docs; nix-shell --run make)
[x] link to an issue
[ ] link to an epic
[x] add estimate points
[x] add milestone (the same as the linked issue)

bors r+

bors try

bors r+

bors r+

bors r+

bors r+

bors r-

authors: CodiePP denisshevchenko


text:
Byron proxy works with new ImmutableDB indexing scheme

Note the merge target: mrBliss/slot-immutabledb.

There's a Byron proxy DB type, which admits reads by point or by hash. This is used to support the Byron proxy logic layer, and is used by the executable to save downloaded blocks.
The sqlite index changes: no more child hash forward link as it's not needed, and the relative slot of EBBs is -1.
EBBs are packed in the 0th slot of their epoch alongside the main block for that slot if there is one.

This was included (rebased) in #341.

authors: avieth edsko

repo: input-output-hk/ouroboros-network