Show preferences panel bar doesn't fit the small screens.

The show preferences panel doesn't fit with the screen width.
Show preferences panel does not fit the width of the screen on small scale devices(width < 365px).
To reproduce
Steps to reproduce the behavior:

Go to  https://floeproject.org
Open Chrome dev tools and click on the toggle device toolbar icon.
Scroll and set the width less than 365px and then see the error.

Expected behavior
The show preferences panel div should occupy the 100% width of the device screen.
Screenshots
1. iPhone 5/SE (Chrome dev tools simulator)

2.  Samsung galaxy S5 (Chrome dev tools simulator)

Technical details
This bug is evident because the size of the images doesn't scale down when the width of the device goes small.
Are you working on this issue? (yes/no)
Yes

Hi I have fixed this issue #118  will send a request for it

Hi! I want to fix this issue #118

I'm closing this as we are currently beginning a redesign process which will address this among other improvements. Thanks for reporting it!

Fixed in #232


feat: Decouple libraries and policies from each other

Currently both libraries and policies are enabled under a single flag. This is cumbersome for cases where one is required but not the other.
This PR https://github.com/aquasecurity/defsec/pull/1298 has the defsec work which is needed, currently it has been reverted as the change for Trivy needs to happen at the same time.
Trivy PR is here https://github.com/aquasecurity/trivy/pull/4070
Both should be merged together.

Closing in favour of https://github.com/aquasecurity/trivy/issues/4181


Drift_dev analyzer needs to be updated

Describe the bug
When I try to run the build_runner, the logs as seen below are in the output, and it fails to run.
Error: The non-abstract class '_AddFromDartType' is missing implementations for these members:
 - TypeVisitor.visitInvalidType

When looking at the repository of the analyzer, I can see that the change was made just a few days ago, in this commit:
https://github.com/dart-lang/sdk/commit/2e6bdc29de69eda869522bce094f6fe76f13bdf1
Meaning that the _AddFromDartType class will need to be updated with this new override (which, from what I understand, is similar to what DynamicType previously did).
> flutter pub run build_runner build
[INFO] Generating build script...
[INFO] Generating build script completed, took 323ms

[INFO] Precompiling build script......
[WARNING] ../../../AppData/Local/Pub/Cache/hosted/pub.dev/drift_dev-2.7.0/lib/src/analysis/results/dart.dart:249:7: Error: The non-abstract class '_AddFromDartType' is missing implementations for these members:
 - TypeVisitor.visitInvalidType
Try to either
 - provide an implementation,
 - inherit an implementation from a superclass or mixin,
 - mark the class as abstract, or
 - provide a 'noSuchMethod' implementation.

class _AddFromDartType extends TypeVisitor<void> {
      ^^^^^^^^^^^^^^^^
../../../AppData/Local/Pub/Cache/hosted/pub.dev/analyzer-5.12.0/lib/dart/element/type_visitor.dart:19:5: Context: 'TypeVisitor.visitInvalidType' is defined here
.
  R visitInvalidType(InvalidType type);
    ^^^^^^^^^^^^^^^^
[INFO] Precompiling build script... completed, took 800ms

[SEVERE] Failed to precompile build script .dart_tool/build/entrypoint/build.dart.
This is likely caused by a misconfigured builder definition.

pub finished with exit code 78

I just realised this change was already proposed as a PR by the author of the commit, so I'm closing this issue :)
https://github.com/simolus3/drift/pull/2417

Welp, and the documentation explicitly states that we shouldn't extend that class... Oops.

Fixed in drift_dev: 2.8.0.


Feature rework

Redo configs (remove autoconfig)
Custom player height
3d Skin layers
Cosmetics
Player sync so you can see other peoples cosmetics/height

Merge all-new features to master.


Failed to run custom build command for libsodium-sys v0.0.8

OS: Debian Jessie
Nightly Rust, updated system.
Pulling straight from your git repo for all safe code. Occurred while attempting to build safe_ffi.
Note: I also installed libsodium as per the directions on README.md for safe_ffi
Compiling libsodium-sys v0.0.8
Running /home/patrick/sodiumoxide/sodiumoxide/target/debug/build/libsodium-sys-1bd84c2c2959fcd6/build-script-build
Fresh pkg-config v0.3.5
Fresh rustc-serialize v0.3.16
Fresh byteorder v0.3.13
Fresh libc v0.1.10
Fresh cbor v0.3.16
failed to run custom build command for libsodium-sys v0.0.8
Process didn't exit successfully: /home/patrick/sodiumoxide/sodiumoxide/target/debug/build/libsodium-sys-1bd84c2c2959fcd6/build-script-build (exit code: 101)
--- stderr
thread '' panicked at 'called Result::unwrap() on an Err value: "failed to run \"pkg-config\" \"--libs\" \"--cflags\" \"libsodium\": No such file or directory (os error 2)"', ../src/libcore/result.rs:734

UPDATE: I installed pkg-config and this error disappeared


libssh2: bind ssh library to v

Finish binding of libssh2 (via https://github.com/maxux/vssh) to crystallib.

In progress

what is status?

Blocked, had no time to finish it. Will put it on todo list for next scheduled project.

Unblocked, working on it.

Current status, coming features are really interesting !

[x] Supports keyboard-interactive, old password and ssh-agent login
[x] Support sending commands
[ ] Efficient stdout management
[ ] Streaming callback support
[ ] File upload / download (scp)


Stack traceback with :Telescope frecency

After the recent OO refactor, running :Telescope frecency gives me the following error:
Error executing Lua callback: ...im/lazy/telescope-frecency.nvim/lua/frecency/recency.lua:30: bad argument #1 to 'ipairs' (table expected, got nil)
stack traceback:
	[C]: in function 'ipairs'
	...im/lazy/telescope-frecency.nvim/lua/frecency/recency.lua:30: in function 'calculate'
	...vim/lazy/telescope-frecency.nvim/lua/frecency/picker.lua:205: in function 'fetch_results'
	...vim/lazy/telescope-frecency.nvim/lua/frecency/picker.lua:83: in function 'start'
	...m/lazy/telescope-frecency.nvim/lua/frecency/frecency.lua:104: in function 'start'
	.../nvim/lazy/telescope-frecency.nvim/lua/frecency/init.lua:13: in function <.../nvim/lazy/telescope-frecency.nvim/lua/frecency/init.lua:11>
	...share/nvim/lazy/telescope.nvim/lua/telescope/command.lua:193: in function 'run_command'
	...share/nvim/lazy/telescope.nvim/lua/telescope/command.lua:253: in function 'load_command'
	...ocal/share/nvim/lazy/telescope.nvim/plugin/telescope.lua:108: in function <...ocal/share/nvim/lazy/telescope.nvim/plugin/telescope.lua:107>

This is with a nightly Neovim build (v0.10.0-dev-766+gef44e5972). Please feel free to close this if it's just a bug on nightly, and if you need more info, please let me know. Thanks!

It seems your DB has file entries that have no related timestamps. I did a fix for those cases in #120.


Internal EPEL mirrors are broken - affects all CI jobs #125

Issue Details
https://bugs.centos.org/view.php?id=16337

Fixed by upstream, not relevant anymore.


Inline function related changes

The PR is to introduce inline function decoding from debug_info info compared to previous symbols from symbol table.
Meanwhile, some fixes to fit for the inline function change.
With these changes,

module name + file name can be used as the uniq id for file mapping
header files and inline functions can be distinguished.

I've reviewed only the first 2 commits for now:
pkg/cover: show module in /funccover and /filecover
qcom: show percent of covered pcs in funcs
They look good to me. The other look more complex.
If you split these 2 commits into a separate PR, we can merge them sooner. It will help to make the remaining part more manageable.

pkg/cover: show module in /funccover and /filecover
qcom: show percent of covered pcs in funcs

Split into https://github.com/google/syzkaller/pull/3157

I tried to compare the upstream syzkaller vs this PR using v5.18.1 Linux (0047d57e6c91177bb731bed5ada6c211868bc27c, compiled using this config with gcc 11.2.0)
I applied this simple patch to measure time.
For the current syzkaller code:
2022/06/03 18:31:51 initializing coverage information...
2022/06/03 18:31:53 MakeReportGenerator took 2.123130372s
2022/06/03 18:31:53 128209 PCs symbolized in 214.958776ms (avg. 1.676µs)
2022/06/03 18:31:56 VMs 4, executed 23995, cover 128335, signal 182206/183516, crashes 0, repro 0
<...>
2022/06/03 18:33:58 rg.prepareFileMap took 2m4.755647766s

For this PR something went wrong.
2022/06/03 18:46:15 initializing coverage information...
2022/06/03 18:46:25 VMs 4, executed 25617, cover 127498, signal 179347/181538, crashes 0, repro 0
2022/06/03 18:46:35 VMs 4, executed 26020, cover 127977, signal 180287/182510, crashes 0, repro 0
2022/06/03 18:46:45 VMs 4, executed 26931, cover 129257, signal 182880/185004, crashes 0, repro 0
2022/06/03 18:46:55 VMs 4, executed 27737, cover 130117, signal 184399/186491, crashes 0, repro 0
2022/06/03 18:47:05 VMs 4, executed 28394, cover 130595, signal 185344/187480, crashes 0, repro 0
2022/06/03 18:47:15 VMs 4, executed 28867, cover 131216, signal 186593/188635, crashes 0, repro 0
2022/06/03 18:47:25 VMs 4, executed 29627, cover 132303, signal 188728/190766, crashes 0, repro 0
2022/06/03 18:47:35 VMs 4, executed 29938, cover 132855, signal 190436/191572, crashes 0, repro 0
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x80ed9e]

goroutine 291076 [running]:
github.com/google/syzkaller/pkg/cover/backend.readAllInlinedSubroutines(0xc00073a180, 0x9b312a?, 0xc0aeb489c0)
        /home/nogikh/syzkaller/pkg/cover/backend/dwarf.go:780 +0x23e
github.com/google/syzkaller/pkg/cover/backend.readSymbolsFromDwarf.func1.1(0x15c71b0?)
        /home/nogikh/syzkaller/pkg/cover/backend/dwarf.go:829 +0x45
created by github.com/google/syzkaller/pkg/cover/backend.readSymbolsFromDwarf.func1
        /home/nogikh/syzkaller/pkg/cover/backend/dwarf.go:828 +0x47b

dwarf

you are right, only tested linux kernel compiled by clang. let me check. I think gcc encodes into different gwarf info.

Verified gcc compiled kernel won't work, as the dwarf is encoded into different format.
DW_AT_sibling is used, and cap_task_setnice doesn't have range att
0x02ffd135:   DW_TAG_subprogram
                DW_AT_external  (true)
                DW_AT_name      ("cap_task_setnice")
                DW_AT_decl_line (1148)
                DW_AT_prototyped        (true)
                DW_AT_type      (0x02fe81c6 "int")
                DW_AT_sibling   (0x02ffd15d)
0x02ffd15d:   DW_TAG_subprogram
                DW_AT_external  (true)
                DW_AT_name      ("cap_task_setioprio")
                DW_AT_decl_line (1135)
                DW_AT_prototyped        (true)
                DW_AT_type      (0x02fe81c6 "int")
                DW_AT_inline    (DW_INL_inlined)
                DW_AT_sibling   (0x02ffd185)
0x02ffd185:   DW_TAG_subprogram
                DW_AT_external  (true)
                DW_AT_name      ("cap_task_setscheduler")
                DW_AT_decl_line (1122)
                DW_AT_prototyped        (true)
                DW_AT_type      (0x02fe81c6 "int")
                DW_AT_low_pc    (0xffffffff8067d190)
                DW_AT_high_pc   (0xffffffff8067d1a2)
                DW_AT_frame_base        (DW_OP_call_frame_cfa)
                DW_AT_GNU_all_call_sites        (true)
                DW_AT_sibling   (0x02ffd1d0)
0x02ffd1d0:   DW_TAG_subprogram
                DW_AT_name      ("cap_safe_nice")
                DW_AT_decl_line (1101)
                DW_AT_prototyped        (true)
                DW_AT_type      (0x02fe81c6 "int")
                DW_AT_low_pc    (0xffffffff8067d090)
                DW_AT_high_pc   (0xffffffff8067d181)
                DW_AT_frame_base        (DW_OP_call_frame_cfa)
                DW_AT_GNU_all_call_sites        (true)
                DW_AT_sibling   (0x02ffd52f)
0x02ffd52f:   DW_TAG_array_type
                DW_AT_type      (0x02fe8156 "char")
                DW_AT_sibling   (0x02ffd53f)
0x02ffd53f:   DW_TAG_subprogram
                DW_AT_external  (true)
                DW_AT_name      ("cap_task_fix_setuid")
                DW_AT_decl_line (1052)
                DW_AT_prototyped        (true)
                DW_AT_type      (0x02fe81c6 "int")
                DW_AT_low_pc    (0xffffffff8067cad0)
                DW_AT_high_pc   (0xffffffff8067ce8f)
                DW_AT_frame_base        (DW_OP_call_frame_cfa)
                DW_AT_GNU_all_call_sites        (true)
                DW_AT_sibling   (0x02ffdb61)

Below shows clang compiled kernel can have range info.
grep cap_task_setnice -A 10 -B 10 dwarf-vmlinux.txt

0x01f50383:       NULL

0x01f50384:     NULL

0x01f50385:   DW_TAG_subprogram
                DW_AT_low_pc    (0xffffffff80722c60)
                DW_AT_high_pc   (0xffffffff80722d19)
                DW_AT_frame_base        (DW_OP_reg7 RSP)
                DW_AT_GNU_all_call_sites        (true)
                DW_AT_name      ("cap_task_setnice")
                DW_AT_decl_line (1148)
                DW_AT_prototyped        (true)
                DW_AT_type      (0x01f3fd2b "int")
                DW_AT_external  (true)

0x01f5039f:     DW_TAG_formal_parameter
                  DW_AT_location        (0x00ac9cff:
                     [0xffffffff80722c60, 0xffffffff80722c6d): DW_OP_reg5 RDI
                     [0xffffffff80722c6d, 0xffffffff80722c91): DW_OP_reg3 RBX

Syzkaller should definitely be able to adequately handle both gcc- and clang- compiled kernels.

Syzkaller should definitely be able to adequately handle both gcc- and clang- compiled kernels.

Right, I'm recoding some of the logic, it works for both gcc and clang now, but still need some tests before pushing.

@a-nogikh pushed the new code, please review again
Tested on linux master with both gcc-9, gcc-11, clang-14.

Hi Joey,
Yes, now I was able to run it. It's a bit slower (by ~15%, it seems, but I did not do many runs), which is not a big deal. The generated HTML file was also somewhat different.
And it's about the expected difference in behavior that I now want to ask you (yeah, that should have been my first question here, but better later than never :) ).

What was your specific problem you were trying to solve with this PR?
What difference should a person that explores the HTML coverage report notice? It would be great if you gave some specific examples.

Some examples that seemed a bit confusing to me.

Different sets of non-covered coverage points (red)

Upstream syzkaller:

Syzkaller from your PR:

What made that possible?

Different sets of covered coverage points (black)

Upstream:

Your PR:

Right now syzkaller anyway extracts the specific affected lines via addr2line, and that tool also shows to which inlined functions belongs each PC we ask it about. So, which changes in this PR made for the difference between these two screenshots?

@a-nogikh

What was your specific problem you were trying to solve with this PR?

The PR is mainly to solve PCs inside inline function and header files are not separated during /subsystemcover shown. So, header files and/or inline functions in header files can be used by multiple c files. If the header file is shared among different subsystems, we might not be care about coverage rate insider header files.
And it also fixes confusing part of during coverage shown and pcs not selected into correct symbols in some corner cases in current buildSymbols.

What difference should a person that explores the HTML coverage report notice? It would be great if you gave some specific examples.
The coverage shown difference is mainly caused by the change below. I think we shouldn't filter out other frames with the same PC.

-       uniqueFrames := make(map[uint64]bool)
-       var finalFrames []backend.Frame
-       for _, frame := range rg.Frames {
-               if !uniqueFrames[frame.PC] {
-                       uniqueFrames[frame.PC] = true
-                       finalFrames = append(finalFrames, frame)
-               }
-       }
-       rg.Frames = finalFrames
+       sort.Slice(rg.Frames, func(i, j int) bool {
+               return rg.Frames[i].PC < rg.Frames[j].PC
+       })

We know when addr2line decodes one PC which has multiple frames, we should show these multiple frames to explictly show that the function is hit too. The reason behind is for the inline function, it can have multiple callers, and multiple repensentation in dwarf section with different ranges.
For example, inline function A is called by two normal functions B and C, and so A at least have range r[start1, end1] and r[start2, end2]. When one PC is decoded, it shows A is hitted in current syzkaller, but we don't know which normal function is called. By applying below fix, then we know it can be from B or C.
I think it's more reasonable now for developer to understand more similiar way as gcov or lcov style.
For Some examples that seemed a bit confusing to me.
Let me try to explain.
By looking at below dwarf extraction, we know audit_log_start is a normal function, if any pc inside it is hit, it means the function is hit too. The current syzkaller cover page shows L1591 is hit, but we don't know if audit_log_start is hit and so we have to search the function to check. But with the PR, we don't need to do so. It's the same case for current_cred function.
0x0129b33f: DW_TAG_subprogram
              DW_AT_low_pc      (0xffffffff817fc940)
              DW_AT_high_pc     (0xffffffff817fcd0b)
              DW_AT_frame_base  (DW_OP_reg6 RBP)
              DW_AT_call_all_calls      (true)
              DW_AT_name        ("audit_log_multicast")
              DW_AT_decl_file   ("/local/mnt/workspace/xx/linux/kernel/audit.c")
              DW_AT_decl_line   (1584)
              DW_AT_prototyped  (true)

0x0129ce93: DW_TAG_subprogram
              DW_AT_low_pc      (0xffffffff817f3320)
              DW_AT_high_pc     (0xffffffff817f3ce5)
              DW_AT_frame_base  (DW_OP_reg6 RBP)
              DW_AT_call_all_calls      (true)
              DW_AT_name        ("audit_log_start")
              DW_AT_decl_file   ("/local/mnt/workspace/xx/linux/kernel/audit.c")
              DW_AT_decl_line   (1846)
              DW_AT_prototyped  (true)
              DW_AT_type        (0x0129cd57 "audit_buffer *")
              DW_AT_external    (true)

0x012b813a: DW_TAG_subprogram
              DW_AT_name        ("audit_log_start")
              DW_AT_decl_file   ("/local/mnt/workspace/xx/linux/./include/linux/audit.h")
              DW_AT_decl_line   (162)
              DW_AT_prototyped  (true)
              DW_AT_type        (0x012b8153 "audit_buffer *")
              DW_AT_declaration (true)
              DW_AT_external    (true)

For audit_log_format, the same case for L1600. It's more reasonable to say there is a PC can be reachable from L1600.
0x0129d319: DW_TAG_subprogram
              DW_AT_low_pc      (0xffffffff817f3cf0)
              DW_AT_high_pc     (0xffffffff817f3e00)
              DW_AT_frame_base  (DW_OP_reg6 RBP)
              DW_AT_call_all_calls      (true)
              DW_AT_name        ("audit_log_format")
              DW_AT_decl_file   ("/local/mnt/workspace/jiangenj/linux/kernel/audit.c")
              DW_AT_decl_line   (1992)
              DW_AT_prototyped  (true)
              DW_AT_external    (true)

0xffffffff8176f315
get_current
arch/x86/include/asm/current.h:15 (discriminator 2)
audit_log_multicast
kernel/audit.c:1600 (discriminator 2)

Different sets of covered coverage points (black)
You can see there is a PC at ffffffff8176c4e2. It should be colored not matter if it's hit.
0x022ba17a: DW_TAG_inlined_subroutine
              DW_AT_abstract_origin     (0x022b82b3 "audit_ctl_owner_current")
              DW_AT_entry_pc    (0xffffffff8176c4e2)
              DW_AT_GNU_entry_view      (0x0000)
              DW_AT_low_pc      (0xffffffff8176c4e2)
              DW_AT_high_pc     (0xffffffff8176c4e7)
              DW_AT_call_file   ("/local/mnt/workspace/xx/linux.gcc/kernel/audit.c")
              DW_AT_call_line   (1868)
              DW_AT_call_column (0x25)
              DW_AT_sibling     (0x022ba21a)

ffffffff8176c4dc:       0f 85 98 01 00 00       jne    ffffffff8176c67a <audit_log_start.part.0+0x24a>
ffffffff8176c4e2:       e8 99 18 03 00          callq  ffffffff8179dd80 <__sanitizer_cov_trace_pc>
ffffffff8176c4e7:       48 39 2d 02 33 e7 0e    cmp    %rbp,0xee73302(%rip)        # ffffffff905df7f0 <audit_cmd_mutex+0x90>
ffffffff8176c4ee:       0f 84 86 01 00 00       je     ffffffff8176c67a <audit_log_start.part.0+0x24a>

Hope it answers all the doubts.


updated readme

[x] Added the correct info
[x] Stared the repo :wink:
[x] Looked over the Code of Conduct and this content is inline with it

@hdrpknc  Congrats on your first PR!

I think somehow the sections aren't right anymore. But I don't know why

which sections?

Sorry, i didn't explain it good. I mean the readme file used to look like:
Name: Joe Bob
Bio: I am a great guy!
Place: City of the Joe
Website: joethecannonball.fakewebsite.com
Twitter: JoeBobTheCannonFakeUser
Facebook: JoeBobTheCannonFakeUser
But now it looks like:
Name: Joe Bob Bio: I am a great guy! Place: City of the Joe Website: joethecannonball.fakewebsite.com Twitter: JoeBobTheCannonFakeUser Facebook: JoeBobTheCannonFakeUser

That is because some one replaced the readme with out two space indent after each item.

I used sublime Text for editing. My guess is somehow sublime did this. But
on  my local Maschine it still looks right.
Am 19.10.2017 11:52 nachm. schrieb "Steven Copeland" <
<EMAIL_ADDRESS>
That is because some one replaced the readme with out two space indent
after each item.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StevenCopeland/first-timers-hacktoberfest/pull/54#issuecomment-338048465,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATBft8SQSPklhcOthQ1aqph48TgYCu1Fks5st8SIgaJpZM4P_2_s
.

Oh no! Now I have to go and add two space indent after every thing!

Don't worry about it. I'll can do that pretty easily. If you want to do it then you can create a new PR with the new content. Also, I recommend Atom.

Sure, i will fix that.
Am 20.10.2017 12:00 vorm. schrieb "Steven Copeland" <
<EMAIL_ADDRESS>
Don't worry about it. I'll can do that pretty easily. If you want to do it
then you can create a new PR with the new content. Also, I recommend Atom.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StevenCopeland/first-timers-hacktoberfest/pull/54#issuecomment-338050280,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATBft336U8TiREwzlMwayeNtpY2XMF5kks5st8Z4gaJpZM4P_2_s
.


written basic tests

Looks alright, but I believe this project uses zero external dependencies?

Well the dependencies are for testing and not for the actual framework


Replace Base.download() with Downloads.download()

Ok, thank you @pywugate!
I will look into how I can configure the repository so that CI also runs on your commits so that I don't have to trigger that manually.
@JuliaRegistrator register

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.


Using jquery plugin in Next.js

Question about Next.js
When I try to load the jquery plugin width the following code to pages/myFullcalendar.js
`import React, { Component } from 'react';
import './App.css';
import $ from 'jquery';
import 'moment/min/moment.min.js';
import 'fullcalendar/dist/fullcalendar.css';
import 'fullcalendar/dist/fullcalendar.print.min.css';
import 'fullcalendar/dist/fullcalendar.js';`
I got this trouble

But In reacte-react-app project,It doesn't exists.
Can you offer me a solution?
Questions should be posted on https://spectrum.chat/next-js

Have same question, no one answered the spectrum chat


esbuild: 0.14.50 -> 0.14.51

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/evanw/esbuild/releases.
meta.description for esbuild is: "An extremely fast JavaScript bundler"
meta.homepage for esbuild is: "https://esbuild.github.io"
meta.changelog for esbuild is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.14.51 with grep in /nix/store/7jk3p2vc0rwmiwgckw2qdjivr0k918vq-esbuild-0.14.51
found 0.14.51 in filename of file in /nix/store/7jk3p2vc0rwmiwgckw2qdjivr0k918vq-esbuild-0.14.51

Rebuild report (if merged into master) (click to expand)

11 total rebuild path(s)

11 package rebuild(s)

First fifty rebuilds by attrpath
code-server
deltachat-desktop
esbuild
libsForQt5.bismuth
libsForQt512.bismuth
libsForQt514.bismuth
libsForQt515.bismuth
openvscode-server
plasma5Packages.bismuth
vscode-extensions.matklad.rust-analyzer
vscode-extensions.rust-lang.rust-analyzer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7jk3p2vc0rwmiwgckw2qdjivr0k918vq-esbuild-0.14.51 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A esbuild https://github.com/r-ryantm/nixpkgs/archive/a2b3b7593440cbd1726bb0ec4616347652b2adb5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7jk3p2vc0rwmiwgckw2qdjivr0k918vq-esbuild-0.14.51
ls -la /nix/store/7jk3p2vc0rwmiwgckw2qdjivr0k918vq-esbuild-0.14.51/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages marked as broken and skipped:

libsForQt512.bismuth
libsForQt514.bismuth

1 package failed to build:

deltachat-desktop (deltachat-electron)

5 packages built:

code-server
esbuild
libsForQt5.bismuth
openvscode-server
vscode-extensions.matklad.rust-analyzer

Maintainer pings
cc @Lucus16 @marsam for testing.

deltachat-desktop is already broken on master @dotlambda


Introduce general traction motor class

Description of the issue
From PR #1027:
We currently/soon have:

motor: A motor is an energy converting component that converts other forms of energy into kinetic energy.

electric motor: An electric motor is a motor that converts electrical energy into kinetic energy.

traction motor: A traction motor is an electric motor used for propulsion.

internal combustion engine: An internal combustion engine is a motor that converts chemical energy into kinetic energy using a cyclic combustion process.
diesel engine: A diesel engine is an internal combustion engine that uses a diesel fuel.
gasoline engine: A gasoline engine is an internal combustion engine that uses a gasoline fuel.

Also for internal combustion engines one can distinguish between traction motors for propulsion and other motors, e.g. in stationary CHP plants.
Ideas of solution
Introduce a (general) traction motor class and relabel existing traction motor class to something like electric traction motor. This new class could be e.g. equivalent to motor and 'participates' in some 'traction process', so we need to define this traction process, too (alternative term maybe propulsion?).
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

No reaction on this issue apart from a thumbs up. In interpret this as no one objects the proposals and these can therefore be implemented.

So here some proposals:

traction motor: A traction motor is a motor used for propulsion.
Wikipedia defines/describes propulsion as: Propulsion means the action or process of pushing or pulling to drive an object. With slight changes that would already make a useful OEO definition: Propulsion is a process of pushing or pulling to drive an object.

Regarding the label propulsion or traction process I am agnostic.

@OpenEnergyPlatform/oeo-domain-expert-energy-modelling : Any thoughts on these proposals?

I did not get any responses for a month, so I assume no one objects my proposals and I will implement these.


custom fields: CLI POC

closes https://github.com/inveniosoftware/invenio-cli/issues/302#issuecomment-1173918959

Example CLI call, for all fields:
invenio custom-fields create

For one or more specific fields (by name)
invenio custom-fields create -f experiment -f department

Open Questions:

CF registration: blueprint vs config loading (post app, e.g. in the views - a bit dirty tho).
Who handles the prefix. If we plan to store the custom fields inside a custom field as we do for metadata we need a place that takes care of that without the user knowing that (e.g. for exists command).

Would this be the registry? then exists command might have issues since it does not pass by registry (unless we also check that, see code TODO/FIXME for more info).
what about the BaseCF? Then we need a way to pass the prefix to it, unless its not configurable (hardcoded). Not that bad since it affects also UI displays and all the data model flow (e.g. field name for Marshmallow)

@zzacharo closing this, since we have https://github.com/inveniosoftware/invenio-rdm-records/pull/997 ? then we can pass to a feature branch


Option to preserve directories in out artifacts

Component
Forge
Describe the feature you would like
Forge writes out Solidity artifacts in a flat structure. Is it possible to allow for maintaining the directory structure (or at least the top level directories like src lib and test) inside the artifacts out?
I am using TypeChain to generate TS types for contracts and when I point it at the out directory, I get a lot of typed files for Solidity that I'll never end up using (mostly test stuff). I am able to exclude files with .t.sol extensions but it doesn't help for transitive dependencies like Test.sol and Vm.sol and console.sol from forge-std.
My typechain command looks something like:
typechain --target ethers-v5 "out/**/!(*.t|test).sol/!(*.abi).json" --out-dir types

I'd rather not have to maintain a list of every contract/solidity file to generate types for and update that as I add more to the list. A slightly more nested directory structure in out would help with this and could use a glob like:
typechain --target ethers-v5 "out/src/**/!(*.abi).json" --out-dir types

Also open to other ideas!
Additional context
Here's an example repo using forge: https://github.com/holic/web3-scaffold
And a recent PR that moves from ds-test to forge-std: https://github.com/holic/web3-scaffold/pull/20
I've opted to generate types (and compile down to JS) + check them into the repo for ease of use when importing them into/using them from the app package. I have a CI script that ensures the built files are up to date with the source files. (This was all previously done at deploy time but added too much time to the deploy step, which happens more often than editing Solidity).

Ref #1488

this is a reasonable request and probably the best solution for #1488
I think I can make this happen on ethers-solc which is responsible for emitting artifacts.
I'll make this optional first and then we can decide whether we make this or some adjacent layout the default

Rad, thanks ya'll 🙏

We use typechain with https://github.com/foundry-rs/hardhat which creates hardhat style artifacts that typechain can consume

Note here: This should be an optional mode

We use typechain with https://github.com/foundry-rs/hardhat which creates hardhat style artifacts that typechain can consume

In order to not tempt coworkers into using Hardhat functionality when there's an alternative within Foundry itself, I've opted to write a script that generates & executes a TypeChain command based upon the files available in ./src/
import { glob } from "glob";
import { basename, normalize } from "node:path";

const files = (await glob("./src/**/*.sol")).map((str) => basename(str));

const { stdout, stderr } = Bun.spawn([
  "npx",
  "typechain",
  "--target=ethers-v6",
  normalize(`./out/{${files.join(",")}}/*.json`),
]);

It's written with Bun, though it should be fairly simple to convert it to node.

Typechain has been deprecated and successors like Viem have Foundry support out of the box
Marking this as not planned.


Enhanced Moistness moisture isn't saved in entity data, so it is lost when the entity is unloaded

Entities immediately become dry when they are unloaded, such as if a player moves far away, the server restarts, or a singleplayer world is closed. Reproducing the issue can be a bit tricky due to the need to unload chunks with deliberate timing, so I built a world with a simple mechanism to test this. I also recorded a short video of myself using the mechanism to demonstrate the issue, in case that would be more convenient than downloading the world and using it yourself.
Recording: https://user-images.githubusercontent.com/49110090/151140675-b44924e7-98da-43e0-81ba-da8cd036dab8.mp4
World download: EnhancedMoistness Testing.zip
I don't imagine that a log file would actually be very relevant to this, but here's one anyways: Link
One of the big reasons I'd love to see Moistness as NBT data is actually so that I can then check for it with other mods' scripting systems, such as KubeJS and Figura. It'd be neat to be able to make playermodels that can react to getting wet, or KubeJS models that can add custom functionality for Enhanced Moistness :)

Would break vanilla compatibility since data would have to be replicated to clients, especially if you want to be able to use it with other mods.
Could potentially be considered for Fabrication X?

other mods' scripting systems, such as KubeJS and Figura
do they not hook into isWet in any way? L78

Ah! Thank you very much for reminding me of that function, somehow it slipped my mind that the function would still be overridden when called by a script. Took a bit of hunting through mappings for KubeJS, but it turns out it and Figura do both have a way to call isWet and it works perfectly. :) Thanks!

The wetness state not saving is intentional as it's a transient state and is unimportant to keep across chunk unload/load.

Would break vanilla compatibility since data would have to be replicated to clients

No, just adding something to server-side NBT doesn't break vanilla compat. Adding a field to the DataManager would, however.

it looks like isWet isn't actually overridden on the client?

It is, but it's not synced from the server. Syncing this from the server is possible but kind of a hassle, and would generate a lot of network traffic.

it looks like isWet isn't actually overridden on the client
i am deeply unfamiliar with anything post zenscript (exception being fscript obviously)
but since isWet can be read server-side could you script it to write to nbt / sync somehow?

It is, but it's not synced from the server

Ahh, I see, I was thinking that both the client and server were independently tracking wetness so that the client could do the particles/sounds, and the server could do Impaling, fire extinguishing, etc - it hadn't occurred to me that the server can just tell the client to do the particles/sounds, although now I realize that that's how it'd have to work in order for vanilla clients to get the effects. Although having the client also independently process wetness would let it use that data to use for a fancy new visual indicator, without the need for any syncing, right? I don't know exactly how reliable that would be, though.

could you script it to write to nbt / sync somehow?

That'd definitely be possible for KubeJS, although Figura runs exclusively on the client, so playermodels wouldn't be able to access that unless a server-side KubeJS script is storing it in NBT for Figura to use.


TiFlash read snapshot can't be released

Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)

ch workload and random ddl

2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiFlash version? (Required)
[2023/04/22 20:38:43.106 +08:00] [INFO] [client.go:509] ["Cluster version information"] [type=tidb] [version=7.2.0-alpha
] [git_hash=8aa7ae292bc9b8ca67e8f304e7d88b1ebc2fc92a]
[2023/04/22 20:38:43.106 +08:00] [INFO] [client.go:509] ["Cluster version information"] [type=tiflash] [version=7.2.0-al
pha] [git_hash=dff6653b958da7419a7a74b1ca2d289579e92cd7]
[2023/04/22 20:38:43.106 +08:00] [INFO] [client.go:509] ["Cluster version information"] [type=pd] [version=7.2.0-alpha]
[git_hash=a746a3e4d8fbae109f69fd3be163cea8a9ef26fa]
[2023/04/22 20:38:43.106 +08:00] [INFO] [client.go:509] ["Cluster version information"] [type=tikv] [version=7.2.0-alpha
] [git_hash=20b75dc4436dc19f1d41acadde9704041dbb7c0c]

Should be the same problem as #7337


Update for FSR 1.02

ffx_fsr1.zip
Based on: https://github.com/GPUOpen-Effects/FidelityFX-FSR/commit/a21ffb8f6c13233ba336352bdff293894c706575

Updated to 1.02.


CBL-3989 : Update API doc about android files / temp dir

Updated recommendation for Android’s files and temp directory.

Ported from the same recommendation in helium branch : e99bc41537904986d9a20eb374ea8d196d8b9c25.

The correct ticket is CBL-3989.


Drop dependency that requires png_img

Rebuild our version as we depend on it via a git URL. Medium term plan is to migrate away from it, but this should unblock Node 16 builds of our projects that depend on this.

Ended up just pushing this to a microbit-node-16 branch so other projects can upgrade one at a time. Closing.


Error of the size mismatch for pos_embed

We load our pretrained model of vit-base trained with mae method, and we meet the size mismatch for pos_embed. Is there any solution to this problem please?
RuntimeError: Error(s) in loading state_dict for VisionTransformer: size mismatch for pos_embed: copying a param with shape torch.Size([1, 785, 768]) from checkpoint, the shape in current model is torch.Size([1, 578, 768]).

Hello! To my knowledge, MAE use 2D sin-cos pos embed and YOLOS use 1D abs learnable pos embed.
I suggest changing the original YOLOS pos embed to MAE's.


Fixed spelling of isDisplayAttributeUsed property

Just a simple spelling fix on the property name to clean it up a little.

Thanks! 😄


Project setup

Implementing most important things like movement, collisions, rendering, etc.
Please look at this code as it is important.

This now fixes #2.

Movement is good, jittering and and slight backwards movements all removed, with the screen panning a bit longer than movement creating a nice look. Should we merge into main soon and branch off individually?

Yeah, sounds good. Need a full review from anyone then we can merge. I have no idea what causes the jitter, I tried to link velocity to deltatime which seemed to fix it on my end. I have looked at previous versions and the jitter persists.


atom 1.26.1 crashes

Prerequisites

[X ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
[Description of the issue]
atom 1.26.1 crashes after few mins of running; I have tried to follow some of steps mentioned above but
don't see it running any good; i don't know the specific reason. There is another issue for v1.24.X mentioned it appears to be the same
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expect to happen]
not to crash
Actual behavior: [What actually happens]
crash
Reproduces how often: [What percentage of the time does it reproduce?]
100%
Versions

You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
Atom    : 1.26.1
Electron: 1.7.11
Chrome  : 58.0.3029.110
Node    : 7.9.0
apm  1.19.0
npm  3.10.10
node 6.9.5 x64
atom 1.26.1
python
git 2.17.0.windows.1
windows 10
Additional Information
this happen just after windows April update any significance? until previously use to work fine on 1.25.0
I have tried reinstalled 1.25.0 but also crashes!
Any additional information, configuration or data that might be necessary to reproduce the issue.

Thanks for the report -

atom 1.26.1 crashes after few mins of running;

Are you doing anything in particular when Atom crashes or does it happen if you just leave Atom running for a few minutes?

I have tried to follow some of steps mentioned above but

Which specific debugging steps have you tried?

There is another issue for v1.24.X mentioned it appears to be the same

Can you share a link?

Nothing in particular.. once opened it just crashes after few minutes, I leave it running.
I have tried reinstalling it along with few steps at https://flight-manual.atom.io/hacking-atom/sections/debugging/
Opening atom in safe mode; removing  all other packages except those that come with it! Checked for Linked packages.
https://github.com/atom/atom/issues/17253
This happen just after windows 10 home April update for me; I have also tried & install previous version 1.25.0 same result..

So.. I read to the debugging page... & I happen to found the following in console.....
Uncaught (in promise) Error: Git status failed
:133934 Uncaught (in promise) Error: Git status failed
:230849 Uncaught (in promise) TypeError: Cannot read property 'ahead' of undefined
at C:\Users\sandeep\AppData\Local\atom\app-1.27.0\resources\app\node_modules\github\lib\models\repository-states\present.js:775:45
at Generator.next ()
at step (C:\Users\sandeep\AppData\Local\atom\app-1.27.0\resources\app\node_modules\github\lib\models\repository-states\present.js:84:197)
at C:\Users\sandeep\AppData\Local\atom\app-1.27.0\resources\app\node_modules\github\lib\models\repository-states\present.js:84:367
at
(anonymous) @ :230849
step @ :230158
(anonymous) @ :230158
:133934 Uncaught (in promise) Error: Git status failed
This happens when i try open file that is not in a git repo.. otherwise it works fine .. i don't know weather this was intended to be... also happy to receive update 1.27

Thanks @saba06 - I don't know if that error is particularly related to the crash you're seeing.  Just to confirm, if you temporarily disable the GitHub package, do you still see the crash after letting Atom run for a while?

Having disabled git-diff, GitHub, open on GitHub packages one by one.. nope it still crashes.. But after some time… the console outputs “Git status Failed” a couple of time when this happens!
From: Robert Sese
Sent: Wednesday, May 16, 2018 2:54 PM
To: atom/atom
Cc: sandeep; Mention
Subject: Re: [atom/atom] atom 1.26.1 crashes (#17308)
Thanks @saba06 - I don't know if that error is particularly related to the crash you're seeing. Just to confirm, if you temporarily disable the GitHub package, do you still see the crash after letting Atom run for a while?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Having disabled git-diff, GitHub, open on GitHub packages one by one.. nope it still crashes.. But after some time… the console outputs “Git status Failed” a couple of time when this happens!

Can you confirm that you disabled the GitHub package, quit Atom, and then restarted in safe mode and you still see this behavior?  Also, are you opening Atom with a Git project?  If you start Atom with no project open, does Atom still crash?

yes

yes; I disabled GitHub package quit to restart in safe mode. With no project open the consoles is clean; only when I open a project NOT a Git project. this behavior happens! I get "Git status Failed" uncaught exception a few times before it crashes. I re-did it just to be sure!

Hmmm can you check if you happen to have a .git directory in your home directory?  On Windows this would be something like C:\Users\YOUR_USERNAME\.git (this would be a hidden folder I think so you would have to enable showing hidden files and folders to see it).

yes I do

I'm assuming that wasn't intentional to have your whole home directory as a Git repository?  In Windows Explorer you can rename it to something like .git.tmp and I believe that will stop the crash you're seeing.

Awesome! works great now... Thank you! No it wasn't intentional. is it something to be deleted?

If it wasn't intentional you can delete that directory if you want :+1:


use concrete type instead of abstract Point2

Should address #22
Key change is that a concrete type Point2f is used for the datapoints in scatter (and axis) instead of the abstract type Point2. This essentially led to an Any type ending up somewhere down in the Makie stack where it didn't belong.

@stelmo @theogf I think this fixes the reported issue (#22); would be ready for merging in my opinion. + registering the bugfix release would be great.

Struggling a little with the image sizes still. It seems to be dependent on what display one is working.

Hi guys, sorry for being permanently afk on this repo. This PR looks good to me, I will merge it and release. Thanks for helping out here!


rsync: 3.2.5 -> 3.2.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/rsync/versions.
meta.description for rsync is: "Fast incremental file transfer utility"
meta.homepage for rsync is: "https://rsync.samba.org/"
meta.changelog for rsync is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 3.2.6 with grep in /nix/store/dcq95vz2mrs2w9myckw7s3q7qmvjgylb-rsync-3.2.6
found 3.2.6 in filename of file in /nix/store/dcq95vz2mrs2w9myckw7s3q7qmvjgylb-rsync-3.2.6

Rebuild report (if merged into master) (click to expand)

22087 total rebuild path(s)

22087 package rebuild(s)

First fifty rebuilds by attrpath

AusweisApp2
CHOWTapeModel
ChowKick
ChowPhaser
CuboCore.coreaction
CuboCore.corearchiver
CuboCore.corefm
CuboCore.coregarage
CuboCore.corehunt
CuboCore.coreimage
CuboCore.coreinfo
CuboCore.corekeyboard
CuboCore.corepad
CuboCore.corepaint
CuboCore.corepdf
CuboCore.corepins
CuboCore.corerenamer
CuboCore.coreshot
CuboCore.corestats
CuboCore.corestuff
CuboCore.coreterminal
CuboCore.coretime
CuboCore.coretoppings
CuboCore.coreuniverse
CuboCore.libcprime
CuboCore.libcsys
DisnixWebService
EBTKS
EmptyEpsilon
HentaiAtHome
Literate
MIDIVisualizer
OSCAR
OVMF
OVMFFull
PageEdit
R
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net
SDL2_sound
SDL2_ttf
SDL2_ttf_2_0_15
SDL_audiolib
SDL_compat
SDL_gpu
SDL_mixer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dcq95vz2mrs2w9myckw7s3q7qmvjgylb-rsync-3.2.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rsync https://github.com/r-ryantm/nixpkgs/archive/00c175ee167aa082be72227469cec5f657053edd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dcq95vz2mrs2w9myckw7s3q7qmvjgylb-rsync-3.2.6
ls -la /nix/store/dcq95vz2mrs2w9myckw7s3q7qmvjgylb-rsync-3.2.6/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @ehmry @kampfschlaefer @ivan for testing.

nixos/tests/rsyncd.nix broken by aed1deab0574f663be2d401861bef303a9d023ba.


[hazelcast-cpp-client] Add new port

Added Hazelcast C++ client (https://github.com/hazelcast/hazelcast-cpp-client) port for Hazelcast in-memory database.

Which triplets are supported/not supported? Have you updated the CI baseline?
It should support all triplets.

Does your PR follow the maintainer guide?
Yes

The regressions caused by gsoap should be fixed by PR #16270.

/azp run

LGTM now, thanks for adding this port.

@NancyLi1013 @ras0219-msft Do you know who can merge the PR?

@ras0219-msft
Could you please help merge this PR?

Thanks again!


[Event Request] Page402 “Sales Order Statistics”  – CheckAllowInvDisc

[Event Request] Page402 “Sales Order Statistics”  – CheckAllowInvDisc
Could we please have a in publisher OnCheckAllowInvDisc in function CheckAllowInvDisc Page402 “Sales Order Statistics”?
    local procedure CheckAllowInvDisc()
    begin
        if not AllowInvDisc then
            Error(Text005, "Invoice Disc. Code");

        // >>>>>>>>
        OnCheckAllowInvDisc(Rec);
        // <<<<<<<<
    end;
..
   // >>>>>>>>
 [IntegrationEvent(false, false)]
 local procedure OnCheckAllowInvDisc(SalesHeader: Record "Sales Header");
 begin
 end;
   // <<<<<<<<

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

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


Typos in mol.fromstring and mol.fromfile

Found several typos in those two routines. Should be "self" instead of "mol". In self.self_geom_, the first argument ('self') should be removed. PySCF version 1.7.

Thanks for inspecting these functions. They were fixed in
adbdcbdd426356485d9a249d7461f668d19d6f9e
On Thu, Jun 11, 2020 at 09:28:51PM -0700, alexmir18 wrote:

Found several typos in those two routines. Should be "self" instead of "mol". In self.self_geom_, the first argument ('self') should be removed. PySCF version 1.7.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/pyscf/pyscf/issues/634

--


NIFI-9688 Improve Logback shutdown handling

Description of PR
NIFI-9688 Improves Logback shutdown handling, avoiding premature closure of the Logback context during application shutdown, and enabling log messages to be written during application termination.
The default LogbackServletContainerInitializer registers a LogbackServletContainerListener that closes the Logback context on web application shutdown. When Jetty registers NiFi web applications, it configures the Logback initializer using the standard Java ServiceLoader. With this behavior, Jetty calls contextDestroyed on the Logback Listener before NiFi termination has completed. This results is missing a number of log messages when shutting down NiFi.
Setting the logbackDisableServletContainerInitializer environment variable to true disables the default Logback listener registration, avoiding the premature context shutdown. Adding the DelayingShutdownHook to the logback.xml configuration allows Logback to perform a clean shutdown after NiFi termination has finished.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Thanks @exceptionfactory ! Definitely a great catch. I was really confused just the other day because i wasn't seeing some logs that I expected on shutdown. And then I found this Jira. Thanks for fixing!


Better link for running function locally

Purpose
Replaces link with more appropriate link
Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X] Documentation content changes
[ ] Other... Please describe:

@vrdmr Small link change, can you take a look? I just went back through the tutorial again yesterday and it worked well otherwise.


Fix generator example

The downToOne example returned the list in a reversed order
See screenshot for proof

Good catch 👍 Thank you !


hepatocytes in heart

There are a significant amount of hepatocytes (liver specific) in heart organ, however there are no other knowledge to agree with this result. Plus heart cardiomyocytes might be contaminated.

@yma3t thanks for your question. We are in the process of revising the annotations and will be publishing an updated version of Tabula Sapiens (v2) in the coming months


feat: 404 page

Description
Adds a new custom 404 page that shows dev cards from various users.
TODO

[ ] Needs the users/top api endpoint to support more than 10 users, cc @OgDev-01  @brandonroberts is there a ticket for this?

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
Closes #910
Mobile & Desktop Screenshots/Recordings
https://github.com/open-sauced/insights/assets/555044/61a5cbb4-d3e6-4394-bedb-2e203af2891d

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[x] 📕 storybook
[ ] 🙅 no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

@foxyblocks This looks great. One ask is the card page allows key navigation and enhances the accessibility. Are we able to key bindings for navigating different cards to this PR.

@foxyblocks This looks great. One ask is the card page allows key navigation and enhances the accessibility. Are we able to key bindings for navigating different cards to this PR.

It currently supports the "left" arrow key for navigation to coincide with the arrow button. Did you want another key??

It currently supports the "left" arrow key for navigation to coincide with the arrow button. Did you want another key??

Oh. I was going up and down. Lol
Perhaps we can include "down" and have it do the same as "left." Not sure if that is help for accessibility but would be for me.

@foxyblocks the last build failed with some prettier changes, will you take a look?


Fix: Update modeladmin to preserve compatibility with RelatedFieldListFilter in Django 2.2+

Resolves #5105

Do the tests still pass? Yes
Does the code comply with the style guide? Yes

Tests in wagtail.contrib.modeladmin.tests.test_simple_modeladmin.TestBookIndexView should no longer error when running against Django's master branch

@gasman Have successfully rebased onto master so we can see the affect on tests
This is the first time i've ever rebased without messing it up, so 😀

@auvipy This is essentially already tested, in the sense that if you look at previous builds against Django 2.2 (e.g. https://travis-ci.org/wagtail/wagtail/jobs/500952790), there are a 9 test errors relating to this issue.
If you look at the same tests for this environment following these changes (https://travis-ci.org/wagtail/wagtail/jobs/499394096), you'll see that the AttributeError: 'BookModelAdmin' object has no attribute 'admin_site' errors are now gone.

Thanks @ababic!


Bug: Youtube shortcode error

Bug description
The latest Hugo version (0.125.0) seems to introduce a bug in the Youtube shortcode.
ERROR The "youtube" shortcode was unable to get remote resource "https://www.youtube.com/oembed?format=json&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAmnu5FBL58g". failed to fetch remote resource: Unauthorized. See "/home/pedro/Documentos/GitHub/pushevs.com/content/posts/pedro/2020-05-21-svolt-unveiled-its-new-cobalt-free-battery-cell.md:130:1"
What version of Hugo are you using (hugo version)?

hugo v0.125.0+extended linux/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?
Yes, this bug didn't exist on previous versions.

OK, so it's a feature, not a bug.


add dirname to fashion mnist dataset

Fashion mnist dataset‘s path is written in the program and cannot be configed by programmer.
Summary
Related Issues
PR Overview

[ ] This PR requires new unit tests [y/n] (make sure tests are included)
[ ] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[ ] This PR is backwards compatible [y/n]
[ ] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

What is your use case? Why do you need this to be configurable?

Because I have downloaded this dataset in other project. And I put all the datasets in my /home/data path to save disk space . Many project can share one dataset .

Maybe I should create an issue rather than a pull request.
So you can close this pull request.

I think the right solution for you is to use a symbolic link since you are using linux. That will be much easier to do.

But other datasets under the package keras.datasets has a load_data function which has a ·path· parameter. The fashion mnist dataset is the only special case .
So I think the better way is to give freedom to users to config where to put the downloaded data .
(x_train, y_train), (x_test, y_test) = reuters.load_data("/data/reuters.npz",num_words=max_words,test_split=0.2)

fashion mnist is different from other dataset, it's very ugly.
And I cannot think up why don't give freedom to users.

def load_data():
    """Loads the Fashion-MNIST dataset.

    # Returns
        Tuple of Numpy arrays: `(x_train, y_train), (x_test, y_test)`.
    """
    dirname = os.path.join('datasets', 'fashion-mnist')
    base = 'http://fashion-mnist.s3-website.eu-central-1.amazonaws.com/'
    files = ['train-labels-idx1-ubyte.gz', 'train-images-idx3-ubyte.gz',
             't10k-labels-idx1-ubyte.gz', 't10k-images-idx3-ubyte.gz']

I see what you mean. It's true that it's inconsistent. I'll open this issue again and will let @fchollet review it since he's responsible for all changes in the API.

I can't open the pull request again. Did you deleted your fork of keras?

No problem. I don't think you need to create an issue. You can make a pull request directly.


Add .vscode to .gitignore file

Some temp file like .vscode should not commit to github repo
Signed-off-by: Nguyen Quang Huy<EMAIL_ADDRESS>

Thx!


Is there a Java 11 compatible version for notsoserial?

I see that notsoserial is dependent on tools.jar for javac. I believe since Java 9 this has been removed, is there a Java 11 compatible version on the way?

Nothing on the way, but if you make a PR we'll try to release it

Hi apologies for such a late reply. I was able to compile the notsoserial code with Java 11, I just had to remove jdk internal api references to xalan packages and replace them with standalone implementations and add below line to maven-failsafe-plugin config to allow agent self attach since it's disabled by default in Java 11 .
<argLine>-Djdk.attach.allowAttachSelf=true</argLine>
However, I can't get the test cases to run. Could someone with a little more insight into the code provide a few pointers to help me out?
In particular I the below issues:

org.apache.commons : commons-collections4 (v4.0) suffers from CVE-2015-7450. v4.1 fixes it by making InvokerTransformer not implement the Serializable interface anymore but that breaks the test cases since I can't use InvokerTransformer to insert values into the priority queue and then serialize it.

Not sure if this is a side affect of something but seeing multiple test failures, pasting test results below:

[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.kantega.notsoserial.CustomNotSoSerialIT
21352@shankarvive-w02
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.089 s <<< FAILURE! - in org.kantega.notsoserial.CustomNotSoSerialIT
[ERROR] shouldCollectUsingCustomNotSoSerial(org.kantega.notsoserial.CustomNotSoSerialIT)  Time elapsed: 0.109 s  <<< FAILURE!
java.lang.AssertionError:

Expected: a collection containing "java.util.PriorityQueue"
     but:
        at org.kantega.notsoserial.CustomNotSoSerialIT.shouldCollectUsingCustomNotSoSerial(CustomNotSoSerialIT.java:69)

[INFO] Running org.kantega.notsoserial.WithAgentIT
15056@shankarvive-w02
HMM..
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.854 s <<< FAILURE! - in org.kantega.notsoserial.WithAgentIT
[ERROR] attackShouldBePreventedWithAgent(org.kantega.notsoserial.WithAgentIT)  Time elapsed: 0.671 s  <<< FAILURE!
java.lang.AssertionError:

Expected: is "false"
     but: was "true"
        at org.kantega.notsoserial.WithAgentIT.attackShouldBePreventedWithAgent(WithAgentIT.java:63)

[INFO] Running org.kantega.notsoserial.WithCustomBlackListFileIT
17308@shankarvive-w02
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.546 s <<< FAILURE! - in org.kantega.notsoserial.WithCustomBlackListFileIT
[ERROR] javaBlackListShouldRejectDeserialization(org.kantega.notsoserial.WithCustomBlackListFileIT)  Time elapsed: 0.421 s  <<< FAILURE!
java.lang.AssertionError: Expected exception: java.lang.UnsupportedOperationException

[INFO] Running org.kantega.notsoserial.WithDryRunWhitelistAndTraceIT
21772@shankarvive-w02
HMM..
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.078 s <<< FAILURE! - in org.kantega.notsoserial.WithDryRunWhitelistAndTraceIT
[ERROR] shouldRecordClassesAsDeserialized(org.kantega.notsoserial.WithDryRunWhitelistAndTraceIT)  Time elapsed: 0.223 s  <<< FAILURE!
java.lang.AssertionError:

Expected: a collection containing "org.apache.commons.collections4.functors.InvokerTransformer"
     but:
        at org.kantega.notsoserial.WithDryRunWhitelistAndTraceIT.shouldRecordClassesAsDeserialized(WithDryRunWhitelistAndTraceIT.java:68)

[INFO] Running org.kantega.notsoserial.WithDryRunWhitelistIT
21480@shankarvive-w02
HMM..
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.016 s <<< FAILURE! - in org.kantega.notsoserial.WithDryRunWhitelistIT
[ERROR] shouldRecordClassesAsDeserialized(org.kantega.notsoserial.WithDryRunWhitelistIT)  Time elapsed: 0.157 s  <<< FAILURE!
java.lang.AssertionError:

Expected: a collection containing "org.apache.commons.collections4.functors.InvokerTransformer"
     but:
        at org.kantega.notsoserial.WithDryRunWhitelistIT.shouldRecordClassesAsDeserialized(WithDryRunWhitelistIT.java:67)

[INFO] Running org.kantega.notsoserial.WithNonEmptyWhitelistIT
16992@shankarvive-w02
HMM..
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.883 s <<< FAILURE! - in org.kantega.notsoserial.WithNonEmptyWhitelistIT
[ERROR] javaWhiteListShouldPreventAttachYetAllowArrayList(org.kantega.notsoserial.WithNonEmptyWhitelistIT)  Time elapsed: 0.108 s  <<< FAILURE!
java.lang.AssertionError:

Expected: is "false"
     but: was "true"
        at org.kantega.notsoserial.WithNonEmptyWhitelistIT.javaWhiteListShouldPreventAttachYetAllowArrayList(WithNonEmptyWhitelistIT.java:63)

[INFO] Running org.kantega.notsoserial.WithoutAgentIT
HMM..
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.608 s - in org.kantega.notsoserial.WithoutAgentIT
[INFO] Running org.kantega.notsoserial.WithWhitelistIT
2756@shankarvive-w02
HMM..
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.747 s <<< FAILURE! - in org.kantega.notsoserial.WithWhitelistIT
[ERROR] emptyWhitelistShouldPreventAttack(org.kantega.notsoserial.WithWhitelistIT)  Time elapsed: 0.109 s  <<< FAILURE!
java.lang.AssertionError:

Expected: is "false"
     but: was "true"
        at org.kantega.notsoserial.WithWhitelistIT.emptyWhitelistShouldPreventAttack(WithWhitelistIT.java:61)

[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   CustomNotSoSerialIT.shouldCollectUsingCustomNotSoSerial:69
Expected: a collection containing "java.util.PriorityQueue"
     but:
[ERROR]   WithAgentIT.attackShouldBePreventedWithAgent:63
Expected: is "false"
     but: was "true"
[ERROR]   WithCustomBlackListFileIT.javaBlackListShouldRejectDeserialization Expected exception: java.lang.UnsupportedOperationException
[ERROR]   WithDryRunWhitelistAndTraceIT.shouldRecordClassesAsDeserialized:68
Expected: a collection containing "org.apache.commons.collections4.functors.InvokerTransformer"
     but:
[ERROR]   WithDryRunWhitelistIT.shouldRecordClassesAsDeserialized:67
Expected: a collection containing "org.apache.commons.collections4.functors.InvokerTransformer"
     but:
[ERROR]   WithNonEmptyWhitelistIT.javaWhiteListShouldPreventAttachYetAllowArrayList:63
Expected: is "false"
     but: was "true"
[ERROR]   WithWhitelistIT.emptyWhitelistShouldPreventAttack:61
Expected: is "false"
     but: was "true"
[INFO]
[ERROR] Tests run: 8, Failures: 7, Errors: 0, Skipped: 0

@oven @eirbjo @wsargent @computerlove I'd very much appreciate any help here.
Thanks


Passwort Protected Links in README.md

Please update the links in README.md to non-password-protected links or share a way to access the linked documents, at least for partners.

Hi @holgerimbery , thanks for raising this. I have raised a PR to get this removed from the README.

The link is removed from README. Hence closing this issue.

@vertikapandey:
you closed the issue,
but "Set up D365 Contact Center embedded experience" --> https://review.learn.microsoft.com/en-us/dynamics365/contact-center/administer/set-up-embedded-experience?branch=main is still a non-public link, as it is pointing to the review site instead of the documentation.
It should be https://learn.microsoft.com/en-us/dynamics365/contact-center/administer/set-up-embedded-experience


Custom datasets

Hi there,
I just learned about Oxen, and it looks very promising. I have a bit of an unusual use case and I'm trying to figure out whether Oxen could be the appropriate solution here.
I deal with planetary ephemeris files which store, in binary format, the trajectory of planets and spacecraft for possibly hundreds of years. This format was originally created by JPL in the 80s -- the specs are here: https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/req/daf.html . The main library that reads these files is by NASA itself (through the NAIF division) and is called SPICE ... but I've rewritten it in full in Rust (because the original code is FORTRAN transliterated in C and absolutely not thread safe). This rewrite is called ANISE -- https://github.com/nyx-space/anise.
Every year, NASA releases a new and improved prediction of where the planets will be in the future -- https://naif.jpl.nasa.gov/pub/naif/generic_kernels/spk/planets/. Every day, NASA also releases the Earth orientation parameters, which specify how the Earth is actually aligned with respect to the stars (we can't predict it super well crazy enough) -- https://naif.jpl.nasa.gov/pub/naif/generic_kernels/pck/ (specifically the earth_latest_high_prec.bpc file). These files aren't typically big (ranging from single digit MB to typically ~100s MB).
In spacecraft operations, we need to ensure that the whole team of flight dynamics engineer use either the latest data (for some computations), or a specific agreed-upon version of these data. The way I've solved this in ANISE is by having a "MetaFile" structure which is pretty simple and stores the URL to the file and optionally its CRC32, so that it can be redownloaded if the CRC is unspecified or if the CRC does not match the local copy (config file example: https://github.com/nyx-space/anise/blob/master/data/latest.dhall ; basic docs: https://docs.rs/anise/latest/anise/almanac/metaload/struct.MetaFile.html ). Another related use case is that we need to publish new datasets, namely a new ephemeris file whenever we compute a new trajectory. In this case, we have consumers of this data in other teams who need to be sure that they're using the latest version of all our data prior to whatever work they're up to. At the moment, we use Kedro to organize our workflows but also to version our data on AWS S3. It works perfectly fine, but Oxen's visualization of datasets is very appealing (especially as most people in this industry are not tech savvy).
In other words, versioning of datasets is crucial. Oxen solves the versioning of datasets and provides visualizations. But Oxen doesn't support NASA's DAF format (and it's such a niche case that it probably should not). Hence my questions:

Is it possible to have extensions to Oxen so that I could upload and visualize in the Oxen web UI the difference between two ephemeris files (even better if I could plot specific things with them, but that's probably a huge stretch)?
~Is it possible to upload arbitrary blobs of data on Oxen?~ (This already works!) If so, I could use ANISE to build a "companion" delivery for new ephemeris files that we deliver and users could diff the companion version. Interestingly, Oxen tries to parse this as text.
~Is it possible to download these datasets with a generic URLs that include the version, e.g. similar to how AWS S3 can have a unique link? In my experience, it's hard enough to convince the IT teams in my industry to install updates to Python, so I can't imagine the trials and tribulations to convince them to install a new binary on operational machines, but if all that's needed is curl/wget with a token, that would be fine (especially if it runs a local deployment of Oxen (which you could/should charge for in my view)).~ (This already works too!)
Would it be possible to separate the Oxen crate into a workspace so that the CLI and lib don't depend on actix since that's a server req? (I'd be more than happy to work on that myself).

That's all my questions for now, and again, this is a very exciting project, so I'll be keeping a close eye on it regardless.
Thanks

Hey Christopher! Thanks for your super detailed post.
1) Data Viz
I actually think the ability to have extensions for custom visualization would be super interesting - and useful in a bunch of industries.
What sort of libraries do you typically use to visualize? Our front end is written in JS and React. We've been trying to think how we could make renderers more configurable based on the data types on the backend.
2) File types and diff
That's interesting, we sniff the first few bytes of files to detect if they are UTF-8 or not so maybe some of those files are false positives. Custom diffs would be interesting too, happy to chat more on that.
3) Generic URLs
Glad you found the download URL (let us know if it could be documented better). We are also working direct S3 integrations if that is interesting as well.
4) Oxen Crates
Currently the lib and CLI crates shouldn't depend on Actix, I'd have to double check the Cargo.toml files but there's a separate one per module. I actually think it would be awesome if the liboxen crate could be used as a library in other tools eventually. We are working on cleaning up the APIs there as we speak.

Hey Greg,

Consider data viz, I typically using plotly from Python because I haven't coded in Javascript in a decade and usually export computations or raw data in a parquet file.
The first nine bytes are ASCII, so that would explain why the platform thinks it's text based. To my surprise, file magic gets it right: de440s.bsp: NASA SPICE file (binary format).
I was too eager to read the documentation in full, sorry about that.
I'll have a closer look, my eagerness probably got the best of me here too.

Cheers


Make sure the quickstart guide is working correctly

The quickstart guide is pretty ok, but it's not completely correct. Make sure this is up and running so it will be easy for users to actually try and test BitMaelum

Seems pretty up to date

Seems pretty up to date


Ability to disable some mutators

Atm, stryker does not work with TypeScript, I need intermediate step to compiler ts source to at least to ES6.
Stryker mangles decorators which leads to guaranteed runtime exception.
Obviously, it is not very useful mutants.
-   FeatureRoutingModule = tslib_1.__decorate([
-       core_1.NgModule({
-           imports: [router_1.RouterModule.forChild(featureRoutes)],
-           exports: [router_1.RouterModule]
-       })
-   ], FeatureRoutingModule);
+   FeatureRoutingModule = tslib_1.__decorate([], FeatureRoutingModule);

True. We're working on native TypeScript support behind the scenes but it will take some.
In the mean time you might want to enable the importHelpers compiler flag. That would already help you quite a lot by minimizing the boiler plate code it would normally emit. But the example you give would still be there.
How would you like the disabling of mutators to work? Have a disabledMutators flag in the config? Every mutator has a name, in your example it is the ["ArrayDeclarator"] (https://github.com/stryker-mutator/stryker/blob/master/packages/stryker/src/mutators/ArrayDeclaratorMutator.ts)
It could look like this:
{
  disabledMutators: [
   'ArrayDeclarator',
   'BinaryOperator'
}

Its important to note that errors during mutation testing are reported separately as type error, which do not impact the mutation score (as explained in the FAQ)

This feature request seems to be a duplicate of #13.

Duplicate of #13 (thanks @shybyte )


Add a property to components such as decoders that sets the gap between the pins.

Decoders, encoders, multiplexers, de-multiplexers.
They always have a 2-square gap between the pins. It would be really useful to be able to set the gap between the pins as to avoid additional wiring. #

This can be done as follows
Add an additional attribute called spacing type in the objects. Set it to 1 for 2-square gap and 0 for 1-square gap. This has to be implemented using mutableProperties attribute. When the property value is changed, delete the object and create a new one at the same position. This will be neat and easy.

[ ] Add attribute spacingType set it according to the current default type. For example, for Multiplexer, current default is 2 for control signal size 1,2,3 and 1 after 3.
[ ] Make appropriate changes changeControlSignalSize()
[ ] Add a property in mutableProperties so that it shows on the property menu.
[ ] Make appropriate changes in the initialization Code (constructor) - such that the nodes are spaced accordingly.
[ ] Make appropriate changes in customSave function

@HypheX do you feel a choice between 1 and 2 square gap is enough, or would you prefer more?

I think a larger gap choice would be better. Many circuits have gaps of 15 or more, and the wiring gets really crazy in small spaces.

is this issue open to be taken?? GSSOC19

@ME-ON1 Please go forward.

Has something similar to this been implemented yet?

Has something similar to this been implemented yet?

No. It is actually quite difficult to introduce now as there should be backward compatibility as well.

@HypheX Whats the progress on this? This issue can be taken under Google Code In-2019 as no PR has been raised yet. What say @satu0king @ankitkataria . Perhaps

Is this issue still up? If yes, I would like to take it up.


Documentation needed

I was just about to use this seemingly really good library, but I cannot find any documentation whatsoever. #618 leads me to believe there must be documentation though, but I could not find anything even when going back a few versions on docs.rs. There is no Wiki in the repository either.
Is there no documentation? If there is, can it be linked somewhere?

Well, there isn't much to document for resvg, because all it does is render an SVG onto a pixmap.
Maybe you arr looking for the documentation of usvg?

Hmm does this library not also enable creating new images programmatically? I was under the impression it did that (though maybe that was just me, since I was looking to do so). usvg as a parser is the wrong way round, so to say.

I'm not sure I'm following... You mean creating an image from an existing SVG, or creating an image from scratch?
What part are you missing documentation from exactly?

Is there no documentation?

Documentation of what? Everything you have to know about it can be found here.

Hmm does this library not also enable creating new images programmatically?

Nope. It's a parser/renderer.

You mean creating an image from an existing SVG, or creating an image from scratch?
Creating an image from scratch.

Nope. It's a parser/renderer.
Then I was mistaken about what this does, sorry.

Everything you have to know about it can be found here.
No offense, but an example file that is neither linked to nor contains any comments / explanation is not documentation. I don't know why this is so prevalent nowadays.

Thanks for your quick responses

I don't know why this is so prevalent nowadays.

Because writing documentation takes time and I'm already low on it.


Precip Accumulation is incorrect

I'm seeing some discrepancies with the precip_accumulation_Xd sensor values when compared to Merry Sky (https://merrysky.net/forecast/48.360169781921684,-116.61274232147296/us) which I believe is using the same data...
Using the same GPS coordinate, you can see that the accumulations for sunday are drastically different; 11.4in vs 4in. Is this perhaps a unit conversion bug? 11.4cm = 4.48in?

If you display the sensor directly do you see the same value as the weather card?
I tested this earlier and I was getting 12mm for non-US units and 30mm for US units. I was using a Canadian location but that shouldn't matter in this case.
There definitely seems to be a bug in the integration as the API results are correct. I'll mention @alexander0042 so he can come and investigate.

I am so sorry for not getting to this one earlier- I didn't realize the extent of it at first, but it turns out I just flat out missed precipitation accumulation in the unit conversion routine, so it's always returning in SI but claiming to be whatever unit is requested. Long story short, not good!
At least it's an easy fix, so I'll push out a new version ASAP!

And it's live! Thanks again for pointing this out, and feel free to re-open if anything else comes up!


fix(kube) only add to scheme.Scheme once

Multiple call to AddToScheme is (1) redundant and (2) destroying concurrency of New.
Closes #6566
Signed-off-by: Jakub Bielecki<EMAIL_ADDRESS>

Note to other maintainers: this conflicts with #7245. Once one of these have been merged, the other will have to be rebased.

Whichever PR merges first, the other can be easily rebased. Nothing complicated. @bacongobbler

@bacongobbler I will rebase if needed.

would you mind rebasing this now that #7245 has been merged?


buildcatrust: use pep517 builder

Up until now this project was build using the setup.py shim, that flit creates for tools that don't support PEP 517 yet.
#!/usr/bin/env python
# setup.py generated by flit for tools that don't yet use PEP 517

from distutils.core import setup

packages = \
['buildcatrust', 'buildcatrust.tests']

package_data = \
{'': ['*'],
 'buildcatrust': ['.pytest_cache/*',
                  '.pytest_cache/v/*',
                  '.pytest_cache/v/cache/*',
                  'tools/*'],
 'buildcatrust.tests': ['.pytest_cache/*',
                        '.pytest_cache/v/*',
                        '.pytest_cache/v/cache/*',
                        'testdata/*',
                        'testdata/local/*']}

entry_points = \
{'console_scripts': ['buildcatrust = buildcatrust.cli:main']}

setup(name='buildcatrust',
      version='0.1.3',
      description='Utilities for turning one trust store into another.',
      author='Luke Granger-Brown',
<EMAIL_ADDRESS>      url='https://github.com/lukegb/buildcatrust',
      packages=packages,
      package_data=package_data,
      entry_points=entry_points,
     )

On top of that an implicit format implies setuptools and makes a call to python setup.py install, which is deprecated.
buildcatrust> Executing setuptoolsBuildPhase
buildcatrust> /nix/store/y8yq448xka665bqyd5gvdhajqdbsnyys-python3.11-setuptools-68.2.2/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
buildcatrust> !!
buildcatrust>
buildcatrust>         ********************************************************************************
buildcatrust>         Please avoid running ``setup.py`` directly.
buildcatrust>         Instead, use pypa/build, pypa/installer or other
buildcatrust>         standards-based tools.
buildcatrust>
buildcatrust>         See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
buildcatrust>         ********************************************************************************
buildcatrust>
buildcatrust> !!
buildcatrust>   self.initialize_options()
buildcatrust> Finished executing setuptoolsBuildPhase

Added some light reformatting on top.
The commit sits on top of the merge base between master/staging, so it is cheap to test.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build cacert

Seems fine - we need to take some care to avoid introducing a dependency loop into building cacerts but flit-core should be fine.

We used to use setuptools for bootstrapping python3Packages, now we use flit-core (to get build & installer), so if push comes to shove, we cann use the bootstrap version of flit-core, that depends on nothing fancy at all.


add document for windows support

What type of this PR

Document

This is part of Windows support #1223.

readme should be updated


ForkChoiceTest failing intermittently

Description
It looks like ForkChoiceTest is failing intermittently.  We should look into these failures.  See:

https://app.circleci.com/pipelines/github/PegaSysEng/teku/6616/workflows/bcf8722e-dd23-44e9-b853-14a52b7fb30d/jobs/41573
https://app.circleci.com/pipelines/github/PegaSysEng/teku/6534/workflows/5262e966-6230-468c-a446-d3ca94a2c3c7/jobs/41059

Duplicate of #2699.


Issue while the keyboard remapping turned on

So, since I like to use the hhkb layout, to reach that, I remap the keys and shortcuts in the system therefore I could use all my keyboards to be similar to the hhkb. Meanwhile, the issue comes out, I am using a live translation app which means that it is translating the text that you selected, and it pop up by pressing the middle button, since I am using touchpad, the way to press the middle is three finger click or four, but even I change it or restart the computer, the gesture does not functioned as middle button but the windows search or the tab. Also, the live translation could not get text selected useless I right click the highlight, I do not know what happened with it, and my system is dev build 21390, the issue happend since 21332.

So that I understand that right. This only happens when Keyboard Manager is on, right?

Yes

Well, I guess it would probably about the system problem. After I test all the set of the remapping, I found out that the only set of remapping that may cause this issue is if you set the Control(left) and the Control remaps to the key that does not input anything like the VK, disable, or undefined. No affecting the Control(right) though.

I think this is actually #3703.

All of these bugs with keyboard remapping have been closed out and referenced to https://github.com/microsoft/PowerToys/issues/3703 but years later, it does not appear that, in https://github.com/microsoft/PowerToys/issues/3703 anything has been done to fix this problem.


Make Application macroable

Making the Application macroable would allow, for example, things like https://github.com/laravel/framework/pull/21529#issuecomment-334206590.

No tests?

@sisve The Macroable trait has its own tests, there's no need to add an specific Macroable test to every Macroable class.

Why would you not also add this to the Console application?

Going to hold off on this for now.


Update ecosystem.json

New projects to be added to ecosystem page
What changed? Why?
Notes to reviewers
How has it been tested?
Does this PR add a new token to the bridge?

[ ] No, this PR does not add a new token to the bridge
[ ] I've confirmed this token doesn't use a bridge override
[ ] I've confirmed this token is an OptimismMintableERC20

Please include evidence of both confirmations above for your reviewers.

Review Error for katsnow08 @ 2024-04-05 15:10:29 UTC
User failed mfa authentication, public email is not set on your github profile. see go/mfa-help


U transfers don't work?

Originally mentioned here, but will start a new issue: https://github.com/arconnectio/ArConnect/issues/128#issuecomment-1746816556
Neither my first or 2nd transaction resulted in a successful U transfer, but the UI gives confirmation of success and a tx.  My balance does not decrease, and the recipient's does not increase.
1st tx:  https://viewblock.io/arweave/tx/DZ4LH5Udq4pAaban8gXhJEDBlCuvXL-bTA_ggsHZ6XA
2nd tx:  https://viewblock.io/arweave/tx/6L-AzvLM3FJdpn2bfKFkp2uKxLRG13hdhUoAFVbYWDI

With the latest version, I now get a "transaction sent" message, but no transaction details and it doesn't look like a tx is generated.

Any updates on this?

@tzarebczan hey sorry for the delayed response! this fix is rolling out on the next release

Thank you! I also tried to go to AR://getu recently and transfers fail there...I thought this was all related ,but maybe not. It seems to want to use dre-6 to make the API call, which doesn't have the contract. I've let some of the other folks know about this issue too, not sure who controls what DRE is selected.

@tzarebczan This should be fixed now with version 1.0.10 - https://github.com/arconnectio/ArConnect/releases/tag/1.0.10


⚠ Jenkins Plugins Artifactory has degraded performance

In d95d68f, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1293 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 4e039db after 12 minutes.


Page Headers

Left Margin: Align with blue section text
Right Margin: Make a space/ gap with photo
Intro blurb: font size twice as big, Use Ebony LT

Photo and color block Overlap:

Make all the overlaps more consistent across pages.
Make them overlap more


Hackatom seoul

Change the stargate querier for cosmwasm to use json

@mattverse please don't merge things like this without more review -- this looks quite senstiive, and definitely underdocumented.


Docs: indexing.rst finetuning

Just some minor documentation tweaks, feel free to cherry pick.
FYI: for https://docs.xarray.dev/en/stable/user-guide/indexing.html#indexing-with-dimension-names  I swapped the two ways for dimension name based indexing, to be in line with order from the "quick overview"
Side question: is it intentional to use dict(space=0)  in dimension name based indexing  instead of {"space": 0} (which is shorter and probably more widely known) everywhere?

Great improvements @soxofaan !

Side question: is it intentional to use dict(space=0) in dimension name based indexing instead of {"space": 0} (which is shorter and probably more widely known) everywhere?

Personally I find it easier to read; partly because the kwargs are cleaner than the dict syntax. I think others have said that they are more ambivalent. I certainly don't have a strong view, and on the "intro" pages we should use whatever is most understandable to a new user, so happy to take a PR to change those.

Thanks!
In some situations I also find constructor style dict()  better suited than literal {}, but my default/musclememory pick would be the latter still.
I'd just expect that new users are mainly exposed to the literal syntax and are not familiar with the constructor style.


More configurable join/leave messages across proxies

One feature I was missing from the Bungee-plugin we used was the option to display different messages for switching servers etc.
Tested it locally and seems to work just fine but please tell me if you want anything changed.

I added the migrator (IJ used the wrong commit message lol). I'll test it soon.
Thanks for your PR


No context request for failed logins signals

When spawning failed login signals, the system does not pass to them any request data.
This is uncomfortable for whoever may want to track failed logins IP for monitoring purposes and attack prevenction.

Feel free to elaborate a PR and help us improve this package.
Thanks.


Removing default integtest.sh.

Coming from https://github.com/opensearch-project/opensearch-build/issues/497, removing default integtest.sh.

Codecov Report

Merging #829 (ba87113) into main (67b5408) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #829   +/-   ##
=======================================
  Coverage   71.98%   71.98%
=======================================
  Files          87       87
  Lines        1906     1906
  Branches      242      242
=======================================
  Hits         1372     1372
  Misses        480      480
  Partials       54       54

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 67b5408...ba87113. Read the comment docs.


Getting prebuilt binaries

When building an Electron App on Mac containing node-sqlite3, the app doesn't work on Windows because it's missing a binary. I would like to be able to build the app on Mac for all platforms (Mac,Win & Linux). I understand it has something to do with prebuilt binaries, but can't figure it out from the docs, can you please help?

Need the same.
Im using node-sqlite3 with node-webkit.

i had compiled binding for electron-1.4-win32-ia32 and electron-1.4-win32-x64. want to try my prebuilt binding binary?

@jefpmn Yes, could you post it?

of course, i just uploaded here. this binding compiled with electron 1.4.12 header. just tell me if you need another version.

Thank you very much!

Would you be able to try with v5.0.3? 🙂


removed posthog secret

All Submissions:

[x] Have you followed the guidelines stated in CONTRIBUTING.md file?
[x] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Dear maintainer(s), you have leaked a posthog secret in the source code. I have replaced it with os.getenv. Please edit my code if it's incorrect.

This is a public key that is needed to send the data for the telemetry.
Your fix would make it not work out of the box.
Since we want telemetry to work on any basic install (unless turned off by user) then we need to have the key part of the installable package.

This is an API key that is needed to send the data for the telemetry.
Your fix would make it not work out of the box.
Since we want telemetry to work on any basic install (unless turned off by user) then we need to have the key part of the installable package.

So, it's not dangerous to keep the secret public?


Implement allow_none=False for Path trait, fixes #1759

This properly implements the default / validation / allow_none part of the traitlets API for our Path traitlet.

The repr_html of Tool is broken after the tool has been run, due to the subcomponents being setup.
This is also broken in master, however for some reason the notebook only prints the error in repr_html, (I guess jupyter ignores exceptions in repr functions).
For now, I fixed it by just skipping the subcompents in the repr, but maybe we want to do a follow up also including subcomponents in the repr. However, I don't really see a big usecase for a html repr of a Tool


"load"-command + " ' " around the world name in removeWorldFromList()

Added loadWorld(String name) to the WorldManager and made it accessible with a command: /mv load {WORLD}, as the opposite of /mv unload {WORLD}
Added ' around the name of the world in removeWorldFromList()

Damn, I just discovered that there IS a case when loadWorld() should return false: When the world doesn't exist! Fixing that...

Fixed


Input Labels Spec Documents

Related Issue
#203
Description
Design spec for input labels. Includes:

InputLabels.md, which discusses design options for input labels
Updated Input.Text.Json file for proposed design, and generated downstream Input.Text.md & adaptive-card.json files. Will update other Input.*.Json files if we agree on approach (both for this feature and for workflow).
Updated Input.Text.md file Renderer section with relevant details
Sample file in Input.Label.json (will make sure to run UWP test app before checking this change in)

Microsoft Reviewers: Open in CodeFlow

Matt: What about other inputs? Consider how this works against non Input.Text inputs.

@matthidinger Added a section with examples of all input types. I don't think there are any special considerations for other types, but let me know if you have further concerns.

In reply to: 554560109 [](ancestors = 554560109)


Is it possible to use sub tenants?

Description
Would like to make it possible to have some sort of sub tenant. For example I make a paas app for my customers/ tenants (main tenants). These tenants have their own customers/ tenants (sub tenants) that would also use the app. Would be nice to make it possible to identify the main tenants by subdomain and the sub tenants by path. The main tenants could each have their own database while the sub tenants are in the main tenants database.
Why this should be added

This is extremely useful and what I'm looking for, I'm going to try to experiment myself and hack a bit building several tenants, have you tried this with the current setup?

@killua99 no, at the moment I haven't tried anything yet. At the moment I could think of two possible solution for now.

Create sub routes use another tenant identifier. But I think this is not going to work as the tenant identifiers could work against each other. Or not work at all as they both use the same methods making it impossible knowing when which tenant needs to be used.
Use another packages such as such as spatie tenancy. Altough not convenient it might work as you can use different methods to identify tenants. Also different methods for the current tenant are used.

A way to make something like this possible would be for example with a "level" of tenancy or relations. Then when using the tenant() and tenancy() methods add a "level" parameter. It could then look like tenant(0) for the main tenant and tenant(1) and so on for lower level tenants.

I'd need a very specific example of how this would be structured (including identification, database structure, etc) to consider this.

@SuperDJ could this be implemented by creating tenants as per normal but setting up a self reference type relationship?
Essentially a parent_id in your tenants table.
This article shows something similar:
https://joaorbrandao.medium.com/self-reference-laravel-model-fa8a7b37360d

@avenjamin at the moment I don't think it will be possible to do in one package. As both the tenant and subtenant must somehow be accessible by tenant() and yet you need to distinguish between them. So for now I went with my second option use a second package so you can use tenant() and a method of that package for the subtenant, Subtenant::current() in case of Spatie.

Didn't get the details asked for above, closing for now.