Hex/Binary diff and formatting for number collections

Hello, I really like using this crate for my tests as it makes it a lot easier to spot which byte has changed or regressed from a change. It would be nice if the crate supported hex and/or binary formatting for collections of numbers (e.g. &[u8]), so that you could see much more easily on the bit level what changed about a number, as currently see the difference between two base-10 numbers isn't that useful for me when comparing binary serialisation output.

Hey, thanks for your feedback. Custom formatting is a widely requested feature - it's good to have the additional data points of binary/hex output format.
I have some ideas on how this could be supported with an opt-in feature, I will keep you posted if I implement them.

FWIW since it is a macro, you could always add an additional argument to the macro that accepts a Settings type, this would keep it being compatible with std::assert_* but allow people to opt in on a case by case basis, as at least right now I don't I would want it to be something that's crate wide enabled or disabled.
assert_eq!([0x80, 0x70], [0x70, 0x80], "binary output mismatched", pretty_assertions::Settings::hex());


[BUG] Can't download anything on Linux.

Describe the bug
Installed Hydra v2.0.3 using AppImage on Manjaro Linux today, tried downloading SIGNALIS, but, once got to the game page - it says "No downloads available", then, tried opening main page and looking at "Trending" games, but, they had 0 downloads and so far, no dowloads available.
Steps to Reproduce

Download 2.0.3 Hydra
Open any game page
See the error

Expected behavior
I expect to be at least able to download games.
Screenshots
No response
Operating System
Manjaro Linux
Hydra Version
2.0.3
Additional Information
No response

Fixed. For everyone having the same issue - join their discord community and follow steps there.


Marathon don't match correctly the resources for a defined role

Using Marathon 0.8.2-RC2 and Mesos 0.22.1
I started Marathon with  mesos_role setted as "fixed", a role to aggregate apps with fixed ports. I have another Marathon without mesos_role.
--mesos_role fixed
The mesos-slave has the following config:
--resources=ports(fixed):[31999-32000, 8080-8080, 80-80, 8081-8081, 9000-9000];ports(*):[31000-31998]
When I launch the app on Marathon, I have this log:
[2015-05-13 04:01:50,542] INFO All assigned host ports must be present in the resource offer.
Assigned: [PortMapping(8000,31999,10000,tcp), PortMapping(8080,8080,10001,tcp), PortMapping(80,80,10002,tcp)] (mesosphere.marathon.tasks.PortsMatcher:49)
[2015-05-13 04:01:50,542] WARN App ports are not available in the offer. (mesosphere.mesos.ResourceMatcher$:50)
[2015-05-13 04:01:50,543] INFO No matching offer for /bamboo-sd/v1 (need cpus=1.0, mem=1024.0, disk=0.0, ports=Vector(31999, 8080, 80)) : id {
  value: "20150510-200829-1403029514-5050-25155-O3746573"
}
framework_id {
  value: "20150508-182649-1403029514-5050-22921-0000"
}
slave_id {
  value: "20150510-200829-1403029514-5050-25155-S63"
}
hostname: "<IP_ADDRESS>"
resources {
  name: "ports"
  type: RANGES
  ranges {
    range {
      begin: 31000
      end: 31499
    }
    range {
      begin: 31503
      end: 31998
    }
  }
  role: "*"
}
resources {
  name: "cpus"
  type: SCALAR
  scalar {
    value: 7.6000000000000005
  }
  role: "*"
}
resources {
  name: "mem"
  type: SCALAR
  scalar {
    value: 14256.0
  }
  role: "*"
}
resources {
  name: "disk"
  type: SCALAR
  scalar {
    value: 25084.0
  }
  role: "*"
}
resources {
  name: "ports"
  type: RANGES
  ranges {
    range {
      begin: 31999
      end: 32000
    }
    range {
      begin: 8080
      end: 8080
    }
    range {
      begin: 80
      end: 80
    }
    range {
      begin: 8081
      end: 8081
    }
    range {
      begin: 9000
      end: 9000
    }
  }
  role: "fixed"
}
 (mesosphere.mesos.TaskBuilder:37)

My app needs ports 31999, 8080 and 80, the slave did the offer, but Marathon don't match.

Thanks for reporting this issue. It seems to be a bug in the mesos-utils library (https://github.com/mesosphere/mesos-utils). Expect it to be fixed in the next release. For now a workaround is to set the port ranges on the slave to the port you want and the next higher one. E.g. for port 8080 set it to 8080-8081, for 9000 to 9000-9001 and so on. I know this is not a great solution, but it will work until it has been fixed in Marathon.

Hm, I may have misinterpreted something in the mesos-utils code. I will keep investigating and let you know when I find the cause.


IE7/IE8 failure since 2.0.0

Hi,
In the process of trying to update mocha's dependencies, I found diff >= 2.0.0 breaks in IE8.
This is why:
exports.default = Stuff;

default cannot be used this way in IE8.  It can be used like this:
exports['default'] = Stuff;

I did find this module, but I couldn't get it to work.

This is an artifact of the babel setup. I don't really have time to look at the config to fix this right now, but I'm glad to accept pull requests.

Yeah, interested in a fix as well so Mocha can upgrade, but I'm in same boat

Released in 3.0.1


Add sample tasks

Fixes #106

I added assignment between tasks and persons for the default data! @JayPeeTeeDee


python311Packages.nibe: 2.5.1 -> 2.5.2

Diff: https://github.com/yozik04/nibe/compare/refs/tags/2.5.1...2.5.2
Changelog: https://github.com/yozik04/nibe/releases/tag/2.5.2
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] 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/)
23.11 Release Notes (or backporting 23.05 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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 270887 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.nibe_heatpump
python310Packages.nibe
python310Packages.nibe.dist
python311Packages.nibe
python311Packages.nibe.dist


Add support for Bluetooth captures

Motivation: Although there is a tool for this in the Windows Driver Kit, it is a bit annoying to have to install 1GB of things you don't need just for the one tool.
I basically worked this out through reverse engineering a .etl file by converting it to .xml with tracerpt.exe.
FYI, the log command in the README comes from here. Not sure if all of it is actually necessary.
The resulting .pcap file was verified to be correct compared to the .cfa file generated by btetlparse .exe from the Windows Driver Kit. This was done using a short capture of an interaction with a Bluetooth Low Energy device.

Thanks for the contribution! Is it useful to look at a packet capture alongside the bluetooth capture? If not, then I'd say this should be its own tool (perhaps it could be in the same repo to share the pcapng helper functions). I ask because I didn't see an explicit mention of doing this in the PR desc.

Thanks for the review. I would not expect anyone to be parsing network and Bluetooth traffic at the same time (which answers the inline question about GetInterface(0)), so I suppose having a separate tool would be fine. It's been so long since I did this I don't remember for sure, but I think I didn't want to spend time deduplicating the code until I was sure there was interest in including these changes for sure (which answers the other two questions).
Would you like me to look at creating a separate etl2pcapng-bt.exe?

Would you like me to look at creating a separate etl2pcapng-bt.exe?
Sounds good, thanks! Sorry for the delay in review; I wasn't notified of this until csujedihy pointed it out to me.


How to install

How to install statbar ?

Install Xcode and build from source or just download the app from release page.

App needs to be updated on Catalina i guess.
“Statbar” can’t be opened because Apple cannot check it for malicious software.This software needs to be updated. Contact the developer for more information."


proposal: encoding/json: add support of wrapped error in addErrorContext function

What version of Go are you using (go version)?

$ go version
go version go1.15.5 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOTOOLDIR="/usr/local/opt/go/libexec/pkg/tool/darwin_amd64"

What did you do?
https://play.golang.org/p/fwgQFqafa3S
What did you expect to see?
Expected to see proper values set to err.Field and err.Struct even if error was wrapped by fmt.Errorf() in UnmarshalJSON of custom structure.
What did you see instead?
In decode.go in addErrorContext function, switch won't work as expected because type mismatch.
So err.Field and err.Struct will be empty even if d.errorContext.Struct != nil || len(d.errorContext.FieldStack) > 0 condition was passed.
What did you propose?
Maybe it is better to use errors.As() instead of switch?
Like this:
// addErrorContext returns a new error enhanced with information from d.errorContext
func (d *decodeState) addErrorContext(err error) error {
	if d.errorContext.Struct != nil || len(d.errorContext.FieldStack) > 0 {
		var e *UnmarshalTypeError
		if errors.As(err, &e) {
			e.Struct = d.errorContext.Struct.Name()
			e.Field = strings.Join(d.errorContext.FieldStack, ".")
		}
	}
	return err
}

/cc @dsnet

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

cc @mvdan

The idea of using errors.As instead of a direct type assertion seems reasonable at face value, but I think we should be careful about how we proceed here. Currently, the error reporting is already a bit non-sensible. I'd like to see #43126 be addressed first before addressing this.

Putting on hold for #43126.
(If the investigation in #43126 ends up finding a suggested change then it would in turn become its own proposal.)

Placed on hold.
— rsc for the proposal review group

Another issue happening on this same function is that when a custom error is returned, and this error does not wrap any JSON errors, I lose context on which field the error happened.
If possible, please wrap all error types for keeping this context.


gnuradio: general improvements

Motivation for this change
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build gnuradio3_9
@ofborg build gnuradio3_9Minimal
@ofborg build gnuradio3_8
@ofborg build gnuradio3_8Minimal

@ofborg build gnuradio3_9
@ofborg build gnuradio3_9Minimal
@ofborg build gnuradio3_8
@ofborg build gnuradio3_8Minimal
@ofborg build gnuradio3_8.pkgs.osmosdr

@ofborg build gnuradio3_9
@ofborg build gnuradio3_9Minimal
@ofborg build gnuradio3_8
@ofborg build gnuradio3_8Minimal
@ofborg build gnuradio3_8.pkgs.osmosdr

@ofborg build gnuradio3_9
@ofborg build gnuradio3_9Minimal
@ofborg build gnuradio3_8
@ofborg build gnuradio3_8Minimal
@ofborg build gnuradio3_8.pkgs.osmosdr

@ofborg build gnuradio3_9
@ofborg build gnuradio3_9Minimal
@ofborg build gnuradio3_8
@ofborg build gnuradio3_8Minimal
@ofborg build gnuradio3_8.pkgs.osmosdr

@ofborg build gnuradio
@ofborg build gnuradio.pkgs.osmosdr
@ofborg build gnuradio3_9
@ofborg build gnuradio3_9Minimal
@ofborg build gnuradio3_9.pkgs.osmosdr
@ofborg build gnuradio3_8
@ofborg build gnuradio3_8Minimal
@ofborg build gnuradio3_8.pkgs.osmosdr

@ofborg build gnuradio
@ofborg build gnuradioMinimal
@ofborg build gnuradio.pkgs.osmosdr
@ofborg build gnuradio3_9
@ofborg build gnuradio3_9Minimal
@ofborg build gnuradio3_9.pkgs.osmosdr
@ofborg build gnuradio3_8
@ofborg build gnuradio3_8Minimal
@ofborg build gnuradio3_8.pkgs.osmosdr

@ofborg build gnuradio
@ofborg build gnuradioMinimal
@ofborg build gnuradio.pkgs.osmosdr
@ofborg build gnuradio3_9
@ofborg build gnuradio3_9Minimal
@ofborg build gnuradio3_9.pkgs.osmosdr
@ofborg build gnuradio3_8
@ofborg build gnuradio3_8Minimal
@ofborg build gnuradio3_8.pkgs.osmosdr

Wierd, all the build times-out on x86_64-darwin. I barely touched the darwin derivations, as the tests enabled are affecting only Linux, so I feel confident to merge this, also thanks to the approval by @fpletz .


Post permalink is missing /homepage/

Hi @JiaKunUp
Hope you are doing well ..
I just created  a new test post. The url for the post is  automatically assigned as  'https://ashutoshmjain.github.io/foss/2017/01/17/testpost.html'
As you will notice , its missing  '/homepage/' .. so I am getting a 404 error .  (foss is one of my categories)
Wondering if there is an easy way to fix it
Thanks in advance for all the help

btw - I tried changing permalink in foss.html from '/foss/' to '/homepage/foss/'  .. If i do that than the foss page itself ends into a 404 error ...

Hi @ashutoshmjain , thanks again for continuous improving this theme!
When I designed this website, I didn't take suburl as homepage into my consideration.So I haven't noticed this bug yet, but thanks anyway for finding this bug!
I see you have edited a lot of in your reposotory, I think the easiest way of fix this bug is:
at blog/blog.html line 26, change  to .
In addition, another blog url you need to edit is file _includes/category.html line 21, change  to .
If you find other urls can't work, this is mainly because the url doesn't have prepend url, you can add it yourself.
I have a new push to fix this bug. Baseurl is '', url is http://www.jack003.com now, if you are intrested on this new commit, you can review my code. Thanks!

Sure ..thanks
I will check it out and close the issue

It worked  .. thanks

Btw  - I just made changes to the code you suggested above :1st_place_medal:
I am not well aware of how I could pull a specific commit. May be I will learn later if things fell apart

@ashutoshmjain  If you have some links can't work, you can inspect this dom element and check if this url is you want, in the above error: your post url should be like http://ashutoshmjain.github.io/homepage/bernie/2017/01/17/test-post-02.html but error post url is http://ashutoshmjain.github.io/bernie/2017/01/17/test-post-02.html,  homepage is missing, so add {{ site.baseurl }} before post url can work.
Thanks.


make vfu_region_to_offset public

This is required for SPDK to access the migration region.
Signed-off-by: Thanos Makatos<EMAIL_ADDRESS>

I'm how quite clear how this is used? I think it needs some docs too?

I'm how quite clear how this is used? I think it needs some docs too?

I'm how quite clear how this is used? I think it needs some docs too?

It's used by the SPDK migration example to access the migration region (https://github.com/tmakatos/spdk/blob/migr/examples/nvme/migrate/migrate.c#L190)
I'll add documentation.

I'm how quite clear how this is used? I think it needs some docs too?

It's used by the SPDK migration example to access the migration region (https://github.com/tmakatos/spdk/blob/migr/examples/nvme/migrate/migrate.c#L190)
I'll add documentation.


Adding current database to firebase

moved database from LocalStorage to firebase.
some modifications in package.json performed by Diego, so that the URL is fixed.

@damfernandes , Sorry for the delay and the amount of lines, I had some problems, normal.


[Question] JSONPath Sort Array

Insomnia Version: 7.0.0
Operating System: Win10

Details
Hi folks,
I try to use the Insomnia JSONPath implementation to play with the JSON output I get from the REST call.
Can someone tell me how to do the following things on the JSON example below?

Sort the array
Select second element
Select elements starting with ....

[
  "myResponse1",
  "myResponse4",
  "myResponse3",
  "myResponse3"
]

The only filter that worked for me was $.* but this is nonsense ... -.-
Thanks!
Regards
-Sergei

sort - not part of the default jsonpath
second element - $.[1] should do it
Select elements starting with .... - unfortunately $.[?(@=~ /myR.*/i)] is valid on http://jsonpath.herokuapp.com/ but this doesn't seem to be part of the package insomnia uses

You can type JS into the filter so $..[?(@.match(/^foo/))] should work (untested)

Thanks @gschier its working!
Any idea how to extend this with sorting function? I am not that familiar with JavaScript... :/

I don't think the library we use supports sorting unfortunately https://github.com/dchester/jsonpath/blob/master/README.md

You can use the following to select element starting with my
$[?(@.match(/my.+/i))]


khmer doc file extensions trip up GitHub rich text editor

I think if they had the '.rst' extension then GitHub would show the rich text editor and diffs. Needs investigating to see if Sphinx will be okay with that.

On Sun, Apr 05, 2015 at 03:05:55AM -0700, Michael R. Crusoe wrote:

I think if they had the '.rst' extension then GitHub would show the rich text editor and diffs. Needs investigating to see if Sphinx will be okay with that.

Yes, this is straightforward; see source_suffix in doc/conf.py.  +1.

Fixed by #912


Error running python script

When running the python script I keep getting this error message
[NULL @ 0x2996aa0] Failed to parse extradata
[h264_omx @ 0x29ab1c0] /opt/vc/lib/libopenmaxil.so not found
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
Conversion failed!
Would you have any idea what could be wrong with this?

This is an error with the encoding process. Ensure that your gpu_mem is set to 128 or greater.

Thanks. I have set this in /boot/config.txt to 256, and rebooted. Same error message is appearing.

The ffmpeg-hls-pts-discontinuity-reclock compiling process likely failed. What compile flags were set when it was compiled?

cd ~ && git clone --depth 1 https://github.com/jjustman/ffmpeg-hls-pts-discontinuity-reclock.git
&& cd ~/ffmpeg-hls-pts-discontinuity-reclock
&& ./configure
--extra-cflags="-I/usr/local/include"
--extra-ldflags="-L/usr/local/lib"
--extra-libs="-lpthread -lm -latomic"
--arch=armel
--enable-gmp
--enable-gpl
--enable-libaom
--enable-libass
--enable-libdrm
--enable-libfdk-aac
--enable-libfreetype
--enable-libkvazaar
--enable-libmp3lame
--enable-libopencore-amrnb
--enable-libopencore-amrwb
--enable-libopus
--enable-librtmp
--enable-libsnappy
--enable-libsoxr
--enable-libssh
--enable-libvorbis
--enable-libvpx
--enable-libzimg
--enable-libwebp
--enable-libx264
--enable-libx265
--enable-libxml2
--enable-mmal
--enable-nonfree
--enable-omx
--enable-omx-rpi
--enable-version3
--target-os=linux
--enable-pthreads
--enable-openssl
--enable-hardcoded-tables
&& make -j$(nproc)
&& sudo make install

If the entirety of /opt/vc is missing, it may be possible to restore the needed files by installing libraspberrypi-bin with apt.
Additionally, --enable-librtmp will need to be changed to --disable-librtmp as librtmp itself will not work with this project.

Still nothing there after an reinstalling libraspberrypi-bin, so I don’t know if it’s putting it somewhere else.
I think I’m going to scrap this and start from scratch again. I have Raspbian Bullseye on this now, the 64 bit version, would it be better to just get a copy of the lite version? Thanks!

The instance running OTCS is based on Raspbian OS Lite Buster 32-bit. The only adjustment made prior to installation was to set gpu_mem to 256. Searching for similar errors to this issue returned reports of other users needing to reinstall the Raspberry Pi firmware package, so I believed it would have corrected it here. I have not tested other versions of Raspbian OS, but I believe there should be no issues with a clean installation of any recent version. Good luck.

The /opt/vc directory has been restored after running rpi-update.
This broadcom.video_encode, if im getting an error with this, does it point towards there being a problem during compile time for ffmpeg? Thanks.
Press [q] to stop, [?] for help
[NULL @ 0x39afaa0] Failed to parse extradata
[h264_omx @ 0x39c41c0] Using OMX.broadcom.video_encode
[h264_omx @ 0x39c41c0] OMX_GetHandle(OMX.broadcom.video_encode) failed: 800010
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or heig
Conversion failed!

If you're still getting errors about metadata, it could be an issue with the video you're trying to transcode. What is the nature of the source video?

The video I'm testing with is a mkv file. I'll find some other formats and see if they're the same.

This is due to the use of the h264_omx codec in Raspberry Pi OS Bullseye. To resolve this, the codec must be changed to h264_v4l2m2m. However, in version 1.x, this requires the script to be edited to use a newer version of ffmpeg alongside the RTMP encoder, which is the default configuration in version 2.0.


Lazily evaluate the IAM Role

Description
Lazily evaluate the IAM Role. At the moment we are evaluating Terragrunt configurations for the IAM Role parameters regardless of whether the CLI args are set. When running Terragrunt commands against a large repo, the performance penalty quickly adds up.

TODOs
Read the Gruntwork contribution guidelines.

[ ] Update the docs.
[ ] Run the relevant tests successfully, including pre-commit checks.
[x] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[ ] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].
Migration Guide

Hey @denis256, I wonder if I can improve how we evaluate the IAM roles with this PR? At the moment we partially evaluate a Terragrunt configuration for the IAM role regardless of whether or not the CLI args are set. This happens for every file. I'm aware of https://github.com/gruntwork-io/terragrunt/issues/1853, but am I actually regressing anything with this PR?
The one catch with this approach is that any missing IAM CLI arguments won't get merged with what's in a Terragrunt configuration.

So far I thought about 2 approaches that require more refinement/tests:

parallel evaluation of HCL files
lazy evaluation of IAM role (and other fields too) - single parsing of HCL files and fetching of "promises" for fields which are evaluated(once and cached) on reading value

@denis256

So far I thought about 2 approaches that require more refinement/tests:
parallel evaluation of HCL files
lazy evaluation of IAM role (and other fields too) - single parsing of HCL files and fetching of "promises" for fields which are evaluated(once and cached) on reading value

Ok nice! Do you think they'll take a while to implement? I guess I'm primarily trying to see if we can find a quick win that is mostly backwards compatible. At the moment on some basic benchmarks, we're spending about ~15% of the CPU budget in the config.setIAMRole function. I was hoping to dramatically reduce that if the user specifies one (--terragrunt-iam-role) or all of the IAM CLI args.

It is not easy a simple change - both approaches will require a significant change in the handling of HCL files

@denis256 okay just so I gather this correctly. We cannot merge this PR "as-is", even if the tests pass? Do I need to take a different approach?

@denis256 hey Denis, just a friendly bump on the message above.

I think with implemented changes, will be good enough to validate through existing integration tests, which seems to pass now

@denis256 okay, thats good to hear! Hopefully I haven't regressed anything.


Options for which cookies to block

I don't know if this an issue anymore, but upgrading form older versions I noticed that I don't have the option to allow user to only allow certain type of cookies.
Is there a setting not documented, or this option is not available anymore? I would really like to use certain mandatory cookies, but allow the users to not use tracking cookies, for example.

I am also interested in this option, since I believe it is required for GDPR compliance.

Users must implement the blocking of the cookies themselves. We cannot know what cookies you use and thus that makes it hard for us to disable them for you.
We are currently working on a new plugin that is GDPR compliant and will disable your cookies automatically for you. We are still working on this

The request was not to block the cookies yourself, but have those options like "necessary", "social", "tracking", etc, which users may check themselves. According to their option I could load or not load certain scripts.
In the new version of cookie consent there is only the option to agree or not to cookies generally.

Ah sorry, my bad. Yes there is currently no way to do this in V3 and no plans to do it either, as CookieConsent was originally designed to work with the "ePrivacy Directive". We are writing a new plugin that will be GDPR compliant. When that comes out, CookieConsent will be deprecated


time_prob handling results in AttributeError

Instead of computing an event probability the basic way, p = beta * stuff, where beta here is a time_prob (ss.beta), I would like to use the more accurate approximation, p = 1 - exp(-beta * stuff).
However, -beta doesn't work:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/dklein/GIT/starsim/starsim/timepars.py", line 298, in __neg__
    def __neg__(self): return self.asnew().set(v=-self.v)
  File "/Users/dklein/GIT/starsim/starsim/timepars.py", line 218, in set
    self.update_cached()
  File "/Users/dklein/GIT/starsim/starsim/timepars.py", line 233, in update_cached
    raise E
  File "/Users/dklein/GIT/starsim/starsim/timepars.py", line 226, in update_cached
    self.update_values()
  File "/Users/dklein/GIT/starsim/starsim/timepars.py", line 362, in update_values
    errormsg = f'Invalid value {self.value} for {self}: must be 0-1'
  File "/Users/dklein/GIT/starsim/starsim/arrays.py", line 35, in __getattr__
    return object.__getattribute__(self, 'values').__getattribute__(attr) # Be explicit to avoid possible recurison
AttributeError: 'numpy.float64' object has no attribute 'value'

Fixed the bug and added a more helpful error message, pointing the user to -beta.values:
ValueError: Invalid value -0.1 for ss.beta(-0.1, unit=None): must be 0-1. If using in a calculation, use .values instead.


Parallel read for json compressed files when it should not

Describe the bug
When reading a compressed json file, with repartition_file_scans = true (default value), datafusion try to uncompress the file with parallel read. This will cause ArrowError(IoError("invalid gzip header", Custom { kind: InvalidInput, error: "invalid gzip header" }), None) because there is no gzip header in the middle.
To Reproduce
let df = ctx.read_json(
        "C:/path/to/file.gz",
        NdJsonReadOptions::default()
        .file_compression_type(FileCompressionType::GZIP)
        .file_extension("gz")
        .schema(&s3_user_schema())
    ).await.unwrap();

Expected behavior
the data should read correctly without errors
Additional context
by put a print statement before the JsonOpener, we can see
GetResult { payload: GetResultPayload(File), meta: ObjectMeta { location: Path { raw: "C:/some/path/foo.gz" }, last_modified: 2024-03-06T00:01:02Z, size: 149873338, e_tag: Some("0-612f2a7828b80-8eee2ba"), version: None }, range: 0..4685075 }
GetResult { payload: GetResultPayload(File), meta: ObjectMeta { location: Path { raw: "C:/some/path/foo.gz" }, last_modified: 2024-03-06T00:01:02Z, size: 149873338, e_tag: Some("0-612f2a7828b80-8eee2ba"), version: None }, range: 37468620..42151887 }
GetResult { payload: GetResultPayload(File), meta: ObjectMeta { location: Path { raw: "C:/some/path/foo.gz" }, last_modified: 2024-03-06T00:01:02Z, size: 149873338, e_tag: Some("0-6.......

which suggest it's indeed reading a compressed json file in parallel.

take

Could you provide more information about the file and the schema? Since I tried a simple gzip file and it work out fine

I agree it is not possible to repartition a json compressed file -- so when the file is compressed we should not repartition
You can probably reproduce this issue with a single json file (maybe repeat the same record over and over again) and then try to read it in


apply constraints in optimizer

How to apply constraints in the optimizer (i.e. somehow change params each time after opt_update function)?

There are some functions in optimizers.py for learning rate schedules, but for other parameters I don't think there's an easy way.

Thanks for the question! Are you thinking of something like, as one example, projected gradient algorithms?
In general, I recommend just treating JAX like you would treat NumPy here: just write it! The JAX API is meant to be just the NumPy API plus function transformations (grad, jit, vmap, etc.). So: how would you write such an algorithm in NumPy?
It's true that we have example libraries like jax.experimental.optimizers, but I wouldn't think of those as a framework. They're meant to be inspirational snippets for you to fork for your own purposes. Don't feel constrained by them! Perhaps you can adapt them to constrained optimization, or perhaps for the constrained optimization case you need something different.

cc @mblondel @froystig who might have some related work and expertise.

@mattjj yes, smth like a projected gradient. Right now I am performing weird stuff like optimizers.unpack_optimizer_state -> update parameters inside this state in the first item of JoinPoint.subtree tuple -> optimizers.pack_optimizer_state, but it looks like I am using private information of optimizer state (i.e. the fact, that parameters would always be in the first item of the tuple).

If we want to think of the projector as problem instance data (rather than being built-in to the optimization routine), maybe you could write things like:
import jax.numpy as np
from jax.experimental.optimizers import optimizer

@optimizer
def pgd(step_size, projector):
  def init(x0):
    return x0
  def update(i, g, x):
    return projector(x - step_size * g)
  def get_params(x):
    return x
  return init, update, get_params

The idea is that projector does the projection you want, like Euclidean projection onto the nonnegative orthant or whatever, operating only on arrays. (The optimizer decorator just serves to map the triple of functions that work on arrays to a triple of functions that work on nested lists/tuples/dicts of arrays via mapping over them.)
You can then use it and instantiate it like this:
# problem instance from Matlab docs:
# https://www.mathworks.com/help/matlab/ref/lsqnonneg.html
A = np.array([[0.0372, 0.2869],
              [0.6861, 0.7071],
              [0.6233, 0.6245],
              [0.6344, 0.6170]]);
y = np.array([0.8587, 0.1781, 0.0747, 0.8405])

import numpy as onp  # no lstsq in jax.numpy.linalg yet, but there's a PR!
unc_x, *_ = onp.linalg.lstsq(A, y)
print(unc_x)  # [-2.5627463  3.1107764]

# nnls via pgd
from jax import grad

def loss(A, x, y):
  prediction = np.dot(A, x)
  return np.sum((prediction - y) ** 2)

def nonnegative_projector(x):
  return np.maximum(x, 0)

x_init = np.ones(2)
init, update, get_params = pgd(1e-2, nonnegative_projector)

opt_state = init(x_init)
for i in range(1000):
  x = get_params(opt_state)
  g = grad(loss, 1)(A, x, y)
  opt_state = update(i, g, opt_state)
x = get_params(opt_state)

optimality = nonnegative_projector(-grad(loss, 1)(A, x, y))
print(np.allclose(optimality, 0., atol=1e-4, rtol=1e-4))  # True
print(x)  # [0.        0.6929333]

WDYT? Is this what you have in mind?

If you're not going to use momentum and stuff, then having init and get_params is a bit heavy-handed and you could get rid of them. Also, if you're not going to use tuples/lists/dicts for decision variables then you don't need @optimizer either. At that point, you might as well ignore optimizers.py entirely and just write things directly with grad:
x = x_init
for i in range(1000):
  g = grad(loss, 1)(A, x, y)
  x = nonnegative_projector(x - 1e-2 * g)

optimality = nonnegative_projector(-grad(loss, 1)(A, x, y))
print(np.allclose(optimality, 0., atol=1e-4, rtol=1e-4))
print(x)

Much cleaner!
I just want to make sure you are getting something out of using any of optimizers.py. If you don't need it, don't use it!

I think we covered this issue, so I'm going to close it. Please open more as questions arise!

It appears that the "constraints" and "bounds" arguments have not been implemented in jax.scipy.optimize.minimize. Is that correct? Or more broadly, is the above the best way to go about constrained optimization while using jax for now?

The above is still an option, but today you might look into using JAXopt. Specifically, see jaxopt.ScipyBoundedMinimize, which is differentiable with respect to bounds. The docs provide an example as well.
cc @mblondel

Thanks @froystig for pointing out JAXopt! will look into it more.


(docs) Carbon Labs on core

Closes https://github.com/carbon-design-system/carbon-website/issues/4181
Changelog
Changed

Added "Carbon Labs" section on "Contributing/Getting Started" page
Added "Carbon Labs" section under "Discovery" on PDLC page

@alisonjoseph Could you help me figure out why my build is failing?

@aagonzales should be good now, I pulled it down and ran yarn format

Thank you! I'll remember to try that first next time

@alisonjoseph sorry to bug you again, but could you restart the vercel build?


Fix regression in test

This snuck in when we merged #4308 after #4307 without a rebase.

Ready for review/merge, @nobodxbodon @mattbk et al.


added two new functions under python

added fibonacci_series.py and lucas_series.py which will print n-elements of Fibonacci and Lucas Series.

Will create PR when hackoberfest 2021 will start!?

Will create PR when hackoberfest 2021 will start!?

yes for hactoberfest from oct 1


Feature request i want to localsend in virtual machine

Is your feature request related to a problem? Please describe.
i use virtual machine, but localsend in virtual machine cannot send file,
Describe the solution you'd like
I have a idea, its:
many people have more virtual machine , so , if localsend can transfer file over second virtual machine , it will be awesome

Describe alternatives you've considered
No response
Additional context
No response

hi, me too, the virtual machines of the two computers can detect each other, but they can't detect the physical machine

That is not an issue we can fix on LocalSend's end. You probably need to configure your VM's network adapter in a way for both computers to be on the same network.


Error: @vercel/kv: Missing required environment variables KV_REST_API_URL and KV_REST_API_TOKEN

I created my kv store and just installed vercel cli for first time and followed basic guide
It created my .env.development.local file with the filled-in values
when I add the import kv from "@vercel/kv" to  +page.server.js file i get Error: @vercel/kv: Missing required environment variables KV_REST_API_URL and KV_REST_API_TOKEN however if I add import { KV_REST_API_URL, KV_REST_API_TOKEN } from "$env/static/private" I can see the actual values show up.
Do i need to do something else, is this a bug, or should i just use rest way. I actually just added upstash last week ironically and got the basics working with that but now going to switch over to staying in vercel ecosystem.
even if i try
import { KV_REST_API_URL, KV_REST_API_TOKEN } from "$env/static/private"
import { createClient } from "@vercel/kv"

// const kv = createClient({
//   url: KV_REST_API_URL,
//   token: KV_REST_API_TOKEN,
// })

i get that error

+1. Get same error.

This sounds similar to https://github.com/vercel/community/discussions/2281. Are you getting this error in server-side code, or in client side code?

This sounds similar to vercel/community#2281. Are you getting this error in server-side code, or in client side code?

I wanna implement Vercel KV into my portfolio website, all config you can see here: https://github.com/LWJerri/lwjerri.dev


Allow yaml file to be empty

This pull request allows having empty host_vars or group_vars YAML files.
If there is something I can change/improve, let me know.

you're quick :D also, tests 😍 LGTM, will smack merge once ci is happy! thanks a bunch!

Thank you very much!


Default HTML5 "Please fill out this field" not appearing

Prerequisites

[√] I have read the documentation;

Description
I am using a simple form with a few fields in it and they are set as required.
I have set
liveValidation={true}
showErrorList={true}

and its not displaying the error message. I just went through the docs again and I am unable to figure out why its not working.

Closing due to inactivity.


Create layout for documentation files

The next step for our documentation is to start organizing the various files we're going to have on the RTD landing page. Currently, it pulls from the ReadMe and the docstrings. However, there are a number of additional files we're going to have for giving more in-depth explanation of different parts of the pipeline. Likely we won't just to paste them all in the readme. Instead, we'll have markdown versions of the files stored in the docs section of the github, and these can get rendered on readthedocs.
Let's put together an example layout of what that would look like. There's a lot of flexibility here in terms of organization, so feel free to adapt any of these suggestions if you have ideas.
The landing page: This should have the basic information about the repo, and link to the following:
Getting started for users: installation instructions using docker and bash script
getting started for developers: virtual-env instructions
Overview of the pipeline (#211)
Overview of different data types (#210), including xarrays (#209)
A link to our contributing guidelines (currently in docs)
What would be great is to create a placeholder file to represent each of these categories, so that we can see how it will look on RTD, how to link from one to another, etc. If you have other ideas for useful sections feel free to make a mockup of them as well.
Then, once we're happy with the organization, we can actually go in and fill in the content for each of them.

So the basic idea I have is to have a separate _rtd folder in the docs directory. We can put all of our landing pages/virtual-env instructions/pipeline overview/etc. here, then include links to these in index.rst with the help of m2r2 and modify our toctree to format our table of contents more cleanly. Because _markdown is created remotely by ReadTheDocs, we can also link to these separately as well if need be.

Because _markdown is created remotely by ReadTheDocs, we can also link to these separately as well if need be.

Could you explain this part? Everything else sounds good

Because _markdown is created remotely by ReadTheDocs, we can also link to these separately as well if need be.

Could you explain this part? Everything else sounds good

Yes, so originally, we were storing the documentation-specific .md files in the folder _markdown on GitHub. However, we're now telling ReadTheDocs to make that documentation on their end, eliminating the need for us to have our own _markdown directory. Instead, we now entrust the ReadTheDocs server to make the folder on their end, completely hidden from us.
Although we cannot see the folder on our end, we can still access the files in the folder in index.rst, because when ReadTheDocs parses it, it will have them for us.

Got it. What will the format be for the files in the _rtd folder?

Got it. What will the format be for the files in the _rtd folder?

All static .md files. Can't think of a reason to have additional subdirectories inside of _rtd for now unless we plan on having a lot of pages outside of our documentation.
Just to clarify, we're splitting this into 2 PRs: the first to define the structure (aka the _rtd folder, blank .md files inside, etc), and the second to actually fill the files with contents? Or am I thinking about this wrong?

That's exactly right. The templates will allow us to see how they look on
RTD, as well as think about what categories we need. Then different people
can contribute to different portions of the next PR with the actual text
On Mon, Sep 14, 2020 at 4:38 PM alex-l-kong<EMAIL_ADDRESS>wrote:

Got it. What will the format be for the files in the _rtd folder?
All static .md files. Can't think of a reason to have additional
subdirectories inside of _rtd for now unless we plan on having a lot of
pages outside of our documentation.
Just to clarify, we're splitting this into 2 PRs: the first to define the
structure (aka the _rtd folder, blank .md files inside, etc), and the
second to actually fill the files with contents? Or am I thinking about
this wrong?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angelolab/ark-analysis/issues/213#issuecomment-692374041,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJB47MGZXF6X6F2HCJUK33SF2SO3ANCNFSM4Q3ODP2A
.


pythonPackages.pyqt5 is broken on master

Issue description
pyqt5 is broken on master.
While I didn't let it finish, it did seem to build on 5e5165ec6f9171ea831b4f05c141ad74d888a5f0 that is, before some changes by @ttuegel.
Steps to reproduce
$ nix-shell -p python35Packages.pyqt5 -I nixpkgs=.
these derivations will be built:
  /nix/store/dqbdd8fl5dhc6jshfzvz3hq4xfm39ixr-python3.5-PyQt-5.5.1.drv
building path(s) ‘/nix/store/y6qf6k25d53lgh3dncin48l9g92mvy32-python3.5-PyQt-5.5.1’
unpacking sources
unpacking source archive /nix/store/c962n5b434y99k11rmmp4vg96nwp5kkl-PyQt-gpl-5.5.1.tar.gz
source root is PyQt-gpl-5.5.1
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file PyQt-gpl-5.5.1/doc/html/signals_slots.html
patching sources
configuring
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/share:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/share/doc:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/share/doc/dbus-python:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/include:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/include/dbus-1.0:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/include/dbus-1.0/dbus:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/lib:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/lib/pkgconfig:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/lib/python3.5:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/lib/python3.5/site-packages:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/lib/python3.5/site-packages/dbus:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/lib/python3.5/site-packages/dbus/__pycache__:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/lib/python3.5/site-packages/dbus/mainloop:
/nix/store/c9b2l1hykl4mabgw53rk2z76d5q05vrm-dbus-python-1.2.4/lib/python3.5/site-packages/dbus/mainloop/__pycache__:
Error: Failed to determine the detail of your Qt installation. Try again using
the --verbose flag to see more detail about the problem.
Querying qmake about your Qt installation...
Determining the details of your Qt installation...
/nix/store/517s8rgjl7yda8s3kfzlxnp0zapsix13-qtbase-5.5.1-dev/bin/qmake -o qtdetail.mk qtdetail.pro
Could not find qmake configuration file linux-g++.
Error processing project file: qtdetail.pro
builder for ‘/nix/store/dqbdd8fl5dhc6jshfzvz3hq4xfm39ixr-python3.5-PyQt-5.5.1.drv’ failed with exit code 1
error: build of ‘/nix/store/dqbdd8fl5dhc6jshfzvz3hq4xfm39ixr-python3.5-PyQt-5.5.1.drv’ failed
/run/current-system/sw/bin/nix-shell: failed to build all dependencies

Technical details

Nixpkgs version: 23c1d17e9d555a2855fc000e3458e05c0991832f

The qmake binary the builder detects, /nix/store/517s8rgjl7yda8s3kfzlxnp0zapsix13-qtbase-5.5.1-dev/bin/qmake, is not the correct one. pyqt5 should depend on qmakeHook, this is probably the cause of the error.

I am not familiar with qmakehook. It is already a buildInput of pyqt5.
There is a configure option to specify a specific qmake

--qmake
Qt’s qmake program is used to determine how your Qt installation is laid out. Normally qmake is found on your PATH. This option can be used to specify a particular instance of qmake to use.

Normally qmake is found on your PATH.

This is not correct. Qt specifies that it should be found from the environment variable $QMAKE first. I expect you need to pass --qmake $QMAKE to your configure script.

Is a qmake in a tmp folder correct?
Error: Failed to determine the detail of your Qt installation. Try again using
the --verbose flag to see more detail about the problem.
Querying qmake about your Qt installation...
Determining the details of your Qt installation...
/tmp/nix-build-python3.5-PyQt-5.5.1.drv-0/tmp.lCVdYMDn0I/bin/qmake -o qtdetail.mk qtdetail.pro
Could not find qmake configuration file linux-g++.
Error processing project file: qtdetail.pro
builder for ‘/nix/store/d1va4yd70akmvqwlknsy25kf8c7rqlhn-python3.5-PyQt-5.5.1.drv’ failed with exit code 1
error: build of ‘/nix/store/d1va4yd70akmvqwlknsy25kf8c7rqlhn-python3.5-PyQt-5.5.1.drv’ failed

Yes, that is the correct qmake.

$ echo $(QMAKE -query)
QT_SYSROOT: QT_INSTALL_PREFIX:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2 QT_INSTALL_ARCHDATA:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2 QT_INSTALL_DATA:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2 QT_INSTALL_DOCS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/share/doc/qt5 QT_INSTALL_HEADERS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/include QT_INSTALL_LIBS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/lib QT_INSTALL_LIBEXECS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/libexec QT_INSTALL_BINS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/bin QT_INSTALL_TESTS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/tests QT_INSTALL_PLUGINS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/lib/qt5/plugins QT_INSTALL_IMPORTS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/lib/qt5/imports QT_INSTALL_QML:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/lib/qt5/qml QT_INSTALL_TRANSLATIONS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/translations QT_INSTALL_CONFIGURATION:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2 QT_INSTALL_EXAMPLES:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/examples QT_INSTALL_DEMOS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/examples QT_HOST_PREFIX:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2 QT_HOST_DATA:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2 QT_HOST_BINS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/bin QT_HOST_LIBS:/tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/lib QMAKE_SPEC:linux-g++ QMAKE_XSPEC:linux-g++ QMAKE_VERSION:3.0 QT_VERSION:5.5.1

Shouldn't this be a path?
QMAKE_XSPEC:linux-g++

Shouldn't this be a path?

It is a path relative to /tmp/nix-build-python3.5-PyQt-5.6.drv-0/tmp.gobMYXvQi2/mkspecs. I reproduced this build locally and found out that directory is not being populated! I will have to investigate further.


re-enable DSS subscription in non prod envs

On service deployment, dev, integration and staging environments will recreate a DSS subscription for test bundles only. This change is to re-enable the matrix service in DCP wide integration tests and does not enable the matrix service to respond to AUDR updates. A number of updates to the DSS subscription are included with its reintroduction:

implement HMAC auth

the HMAC secret key is regenerated on every deployment and is stored in AWS SecretsManager

update JMESPath query

subscribes only to test bundles, updated SS2 and 10x filters to select via library_construction_method.ontology
metadata schema version logic added but unused. This is a decision to enable MS to test against the latest metadata schema versions during DCP wide integration tests.

moved notification endpoint from /v0/dss/notification to /dss/notification (removed from Swagger)

Closes #372

Does chalice still create a /notifications endpoint in API gateway if it's not in the swagger?

Yup. The routes defined in app/core.py (includes /dss/notification) are available in API Gateway


Update github pr docs actions

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


removed pplib usage in lib

Implementation of #10

PPLib is already removed when upgrading to wpilib 2025, merged anyway.


Skywalking can not support weblogic fuction

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion

My problem is that springmvc3.0 Web project is deployed in the Weblogic 10.3.6 environment, and @RequestMapping Get or Post requests cannot be viewed in Skywalking's Trace .
And the same war package is deployed in Tomcat ,the @RequestMapping  requests can be displayed. .Because there is: tomcat-7.x-8.x-plugin-5.0.0-beta2,
If there are pictures attached to &#x4EF6 (6, 1-3 are Weblogic's request, 4-6 is Tomcat's request).
My env is:
tomcat 8 /weblogic 10.3.6
SpringMVC-Demo-master.war

[ ] Bug

[ ] Requirement

[ ] Feature or performance improvement

Can the skywalking support the weblogic plugins ?

Question

What do you want to know

Bug

Which version of SkyWalking, OS and JRE?

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement

Please describe about your requirements or improvement suggestions.

Repeat submit , shut down


Demo link does not load

Steps to reproduce:

click on Demo link

Observed:

page has:

Loading text
An unhandled error has occurred. Reload

errors in Google Chrome console:

Failed to find a valid digest in the 'integrity' attribute for resource 'https://excubo-ag.github.io/Blazor.Canvas/_framework/TestProject_ClientSide.dll' with computed SHA-256 integrity '94Sr2R0Ne5tEy7lcHJOOMHcdEwvXzFKXhpEXVXW4iW4='. The resource has been blocked.
excubo-ag.github.io/:1 Unknown error occurred while trying to verify integrity.
excubo-ag.github.io/:1 Failed to find a valid digest in the 'integrity' attribute for resource 'https://excubo-ag.github.io/Blazor.Canvas/_framework/System.Collections.Concurrent.dll' with computed SHA-256 integrity 'bRXqW6Ih7fwtfPX2uP9TMWVV+Au+Bpu2L0nLwGBxS/o='. The resource has been blocked.
excubo-ag.github.io/:1 Unknown error occurred while trying to verify integrity.

etc
Expected:

demo to load without error

Configuration:

Google Chrome
Version 92.0.4515.107 (Official Build) (64-bit)

Thanks for reporting this. I can't quite see the reason for it, as the build process is identical to other demo sites in the same org, which seem to work. I've just triggered a re-run of the last action workflow to see whether that does anything.

Please try again now. You may need to force a reload / empty the browser cache. It works again for me

Working now.  Thanks for the prompt response.


Fixes #107 - Update build task for don`t repeat templates

Change  ngtemplates in Gruntfile.js for replace (not add in the end of file) template.
Removed ngtemplatesOptions.append because by default is false and it's necesary for not duplicate templates

Thanks for the PR. I believe the original issue has been fixed.


Broken response headers with NextJS api route

Describe the bug
It will response a broken headers with NextJS api route
HTTP/1.1 200 OK
1: 7
c: o
a: c
h: t
v: a
o: r
t: r
date: Mon, 19 Jun 2023 09:33:21 GMT
connection: close
transfer-encoding: chunked

It will occur graphql-request query error
Fine with 3.9.1
Your Example Website or App
https://github.com/filenwind/graphql-yoga-res-header-broken
Steps to Reproduce the Bug or Issue

git clone git@github.com:filenwind/graphql-yoga-res-header-broken.git
npm install
npm run dev
browse http://localhost:3000/api/graphql
open developer tools
Refresh page or make a any query
check the network graphql's with strange Response Headers

Expected behavior
Should be normal response header
You can install 3.9.1 to see the different
npm i -E<EMAIL_ADDRESS>HTTP/1.1 200 OK
content-type: application/graphql-response+json; charset=utf-8
access-control-allow-origin: http://localhost:3000
vary: Origin, Accept-Encoding
access-control-allow-credentials: true
date: Mon, 19 Jun 2023 09:46:21 GMT
content-encoding: gzip
connection: close
transfer-encoding: chunked

Screenshots or Videos
No response
Platform

OS: macOS
NodeJS: 16.14.0
@graphql-yoga/* version(s): 4.0.1

Additional context
No response

So glad someone has the same problem! Just spent a day debugging, downgrading to GraphQL Yoga v3.9.1 also fixed the issue.
I get similar response headers with v4.0.1 which will throw an graphql-request error:
HTTP/1.1 200 OK
3: 8
set-cookie: [-- omitting this --]
c: o
a: c
h: t
p: O
t: r
date: Tue, 20 Jun 2023 04:35:02 GMT
connection: close
transfer-encoding: chunked

v3.9.1 Response headers:
HTTP/1.1 200 OK
set-cookie: [-- omitting this --]
04:37:27 GMT; HttpOnly; SameSite=Lax
content-type: application/json; charset=utf-8
access-control-allow-origin: http://localhost:3000
access-control-allow-methods: POST
access-control-allow-credentials: true
vary: Accept-Encoding
date: Tue, 20 Jun 2023 04:37:27 GMT
content-encoding: gzip
connection: close
transfer-encoding: chunked

I couldn't reproduce it in our CI.
https://github.com/dotansimha/graphql-yoga/pull/2880
Could you update the versions and try again? Also recreating the lockfile might be helpful to get the latest version.

No dice on my end. I installed GraphQL 4.0.2 and blew away my package.lock and node_modules just for fun.
Same result. Response headers are all messed up.

Hi, @ardatan
I update the repository (remove package-lock.json)
And I have tested below browsers, all have the same problem.
Chrome is up to date
Version 114.0.5735.133 (Official Build) (x86_64)

Safari
Version 16.5 (186<IP_ADDRESS>.4)

Firefox Release
114.0.2

Maybe it only happens in the browser?
Thanks your help!

@ardatan I've made some tests. We probably have some other packages in the monorepo that are interfering and that changes a package version between their example and ours.
I have extracted our example outside the monorepo, it has the same behaviour in the browser. And the problem is not even the same when trying to fetch from node using fetch (the headers are ok, they are just not matching the snapshot).
I'm still investigating, but since the result is not the same on browser and on node, it's very dificult to see what really happens.

Seems that the problem comes from @whatwg-node/server. On the mono-repo, we are using version 0.8.1 while a fresh install is installing 0.8.12.
The bug appears starting with version 0.8.8 (this commit). The only obvious thing that rings a bell for me is the @ts-expect-error Node supports arrays as headers, it is probably not that true after all 😅

Here is a PR reproducing the bug in the CI : #2889

Confirmed! Issue is resolved. Thank you 🥇

Thank you very much!


Unable to rename resource

Observed/problematic behavior
Unable to rename resource
Expected behavior
Rename resource successfully
Steps to reproduce

Create organisation
Create resource
Try to rename it

Other

interesting, the rename happened for the first attempt regardless of the error
https://hangar.papermc.dev/HiddenOrgOnMyProfile/CheapSpigotForkPremium

Resolved.


Explanation about Input's Id and Value attributes

Added explanation about what to put into the Id and Value attributes of the Input tag. Also added how to get list from global list.
As follow up to issue #20 .

@ndc,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@ndc, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

@ndc Thanks for the update!


Function App Execution Error: Parsing Issue with Azure Sentinel Template

Describe the bug
One of our clients has created a function app using this template (https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Fortinet FortiGate Next-Generation Firewall connector for Microsoft Sentinel/Playbooks/FortinetFortigateFunctionApp).
The customer is using this project to configure a playbook in Sentinel for automating the Function app. However, when the client executes it, they encounter the same error as the previous issue (https://github.com/Azure/Azure-Sentinel/issues/2874): "Unexpected character encountered while parsing value: <. Path '', line 0, position 0."
To Reproduce
You could take the same action in 'To Reproduce' section in https://github.com/Azure/Azure-Sentinel/issues/2874.
Expected behavior
Function could execute successfully and the logic app can complete.
Screenshots

Additional context
1.We have used two templates, but the function app runtime version created by both templates is 3.20. However, version 3.20 has not been supported by Azure since December last year, so I would like to know if you have any new templates similar to 'https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Fortinet FortiGate Next-Generation Firewall connector for Microsoft Sentinel/Playbooks/FortinetFortigateFunctionApp'.
2.Our coding capabilities are limited, so we cannot rewrite as mentioned by scottbrien01 in the previous issue. Could you please help us modify the relevant code in the github template or kindly guide us how to change it?
Thanks in advance!

Hi team, Merry Christmas! May I kindly inquire if there are any updates? Looking forward to hearing from you at your earliest convenience.

Hi @cryanskl, Merry Christmas!, team still checking on this issue, and will share an update you by - 29-12-2023. Thanks!

Hi @v-sudkharat, thank you for your prompt response! Looking forward to hearing from you at your earliest convenience.

Hi @cryanskl ,I tried check the existing ARM template and its not behaving expected,Please find below screen shot for reference

Could you please share your requirement in detail, want to pass the Authorization with Bearer token?

Hi @cryanskl ,Gentle reminder,Could you please share your requirement in detail, want to pass the Authorization with Bearer token?,so will proceed with the changes.

Hi @cryanskl ,Since we have not received a response in the last 5 days, we are closing your issue (https://github.com/Azure/Azure-Sentinel/issues/9636) as per our standard operating procedures. If you still need support for 	this issue, feel free to re-open at any time. Thank you for your co-operation!


Hide details of error implementation, to not make changes into breaking changes

As discussed in the office. Having errors simply be public enums with associated data makes the implementation details part of the public API. Then almost all changes to the error are breaking changes. Here I show two potential ways to implement errors so that their internals are hidden, but it's equally easy to match for a library consumer.
This is currently split into two commits, one per proposed solution. So view it per commit if you want to compare them. I personally like the second solution the best. That error implementation could fairly easily be generated by a macro. I'm sure we are not the first people to come to this conclusion, maybe there is such a macro crate on crates.io already?

This change is

I like 2 as well. Took the liberty of mocking up a solution that involves more macros (here).
Sadly this adds 2 more dependencies (thiserror and strum), but could be worth exploring.


Add term table, accomodate multiple terms, fix course.sis_id bug (#113, #117)

This PR modifies the COURSE_INVENTORYjob and the database schema as to be able to collect and store data related to multiple academic terms. Some additional details are provided in the task list below. This PR aims to resolve issues #113 and #117.

[x] Add migration with new term table and with a term_id column and foreign key constraint to the course table.
[x] Make CANVAS_TERM_ID configuration variable plural, i.e. CANVAS_TERM_IDS.
[x] Add function that checks for existing terms and pulls data from the Canvas API for new ones.
[x] Modify get_course_data_from_api function to accept multiple terms, nest fetching process insidefor loop, and then combine all results into one course_df (ensuring that future processes will consider courses from the multiple terms specified).
[x] Write contents of new_term_df to database.
[x] Add migration changing the data type of course.sis_id to VARCHAR(15) and type coercion to string of those values (see issue #117 for details).
[x] Update online_meetings/canvas_zoom_meetings.py to handle multiple terms.
[x] Update README.

@ssciolla, any idea why Codacy claims zoom_course_report is using "%s as argument"?  (Which Codacy can't even display correctly!)
Can we use comments to tell Codacy (or in this case, PyLint specifically) to ignore this error for this section of code? (https://github.com/tl-its-umich-edu/course-inventory/pull/115/files#diff-9e1a06acd700cfb38555dc5980f1cdb0R163)

@ssciolla, any idea why Codacy claims zoom_course_report is using "%s as argument"? (Which Codacy can't even display correctly!)
Can we use comments to tell Codacy (or in this case, PyLint specifically) to ignore this error for this section of code? (https://github.com/tl-its-umich-edu/course-inventory/pull/115/files#diff-9e1a06acd700cfb38555dc5980f1cdb0R163)

I think that's an issue that was there before; it doesn't like the default mutable argument of []. I'm not really sure I get why it's an issue; if we agree, maybe it's something we can configure in Codacy?


Setup a CI system for ClangSharp

As per https://github.com/Microsoft/ClangSharp/pull/34#issuecomment-486877211, it would be nice if ClangSharp could be connected to Azure DevOps for CI and other build infrastructure niceties.
It may be possible to utilize dotnet/arcade for this, or to setup a smaller localized infrastructure.

for up-to-date nuget packages 🙂

I put up a PR which sets up most of the infrastructure required: https://github.com/microsoft/ClangSharp/pull/60
The only thing really missing is an AzDO project so I can configure the azure-pipelines.yml

This is largely resolved now. It would still be nice to get signing support setup and to get new nuget packages for ClangSharp proper uploaded.


Drop the  node if found

Hope I've done this right! Fairly new to raising PR.
My perl isn't the best either so let me know if there's a better way to do it!

Great! Thanks, have you tested this patch against a release?

I went ahead and tested. Amazing! Fixes #5
Thanks for using the library and I'm sure other's will appreciate it. :)


PowerToys Run
Steps to reproduce
pops error message on launch
I tried store version and winget, both experienced the same issue.
✔ Expected Behavior
no error
❌ Actual Behavior

Other Software
vscode v1.81.1 from msstore

the compressed file didn't appear on the desktop, even if I executed 'C:\Program Files\PowerToys\Tools\PowerToys.BugReportTool.exe' directly. Therefore, I manually compressed the folder at ~\AppData\Local\Temp\PowerToys.
BugReport.zip

[2023-08-31 14:15:40.7050] [ERROR] [C:\a\_work\1\s\src\modules\launcher\Wox.Plugin\PluginPair.cs::176]
-------------------------- Begin exception --------------------------
Message: Can't create instance for <VS Code Workspaces> in C:\Program Files\PowerToys\RunPlugins\VSCodeWorkspace\Community.PowerToys.Run.Plugin.VSCodeWorkspaces.dll

Exception full name  : System.Reflection.TargetInvocationException
Exception message    : Exception has been thrown by the target of an invocation.
Exception stack trace:
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)
   at Wox.Plugin.PluginPair.CreatePluginInstance()
Exception source     : System.Private.CoreLib
Exception target site: System.Object CreateInstanceDefaultCtor(Boolean, Boolean)
Exception HResult    : -2146232828

Exception full name  : System.IO.FileNotFoundException
Exception message    : Could not load file or assembly 'C:\Users\peng2\AppData\Local\Programs\Microsoft VS Code\bin\Code.exe'. 系統找不到指定的檔案。
Exception stack trace:
   at System.Drawing.Icon.ExtractAssociatedIcon(String filePath, Int32 index)
   at Community.PowerToys.Run.Plugin.VSCodeWorkspaces.VSCodeHelper.VSCodeInstances.LoadVSCodeInstances()
   at Community.PowerToys.Run.Plugin.VSCodeWorkspaces.Main..ctor()
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)
Exception source     : System.Drawing.Common
Exception target site: System.Drawing.Icon ExtractAssociatedIcon(System.String, Int32)
Exception HResult    : -2147024894
-------------------------- End exception --------------------------

Do you have the following file C:\Users\peng2\AppData\Local\Programs\Microsoft VS Code\bin\Code.exe?
/needinfo

no, I only have ~\AppData\Local\Programs\Microsoft VS Code\bin\code.cmd, code.exe is at it's parent ~\AppData\Local\Programs\Microsoft VS Code

@shively @8LWXpg @jaimecbernardo
Assuming that the logic used to identify the VS Code version is correct...
https://github.com/microsoft/PowerToys/blob/66f4f69841612ad5971a13e208f035ea98364847/src/modules/launcher/Plugins/Community.PowerToys.Run.Plugin.VSCodeWorkspaces/VSCodeHelper/VSCodeInstances.cs#L92-L116
...I have been able to reproduce the issue adding a trailing backslash to the VS Code PATH environment variable.

C:\Users\david\AppData\Local\Programs\Microsoft VS Code\bin\ fail
C:\Users\david\AppData\Local\Programs\Microsoft VS Code\bin working

I think the code needs to handle this while finding the VS Code directory and is missing some extra checks to prevent the crash.
Will take a look into this and create a PR with a possible fix.
In the meanwhile if you are experiencing this issue check your PATH.

The work associated with this issue has been released as part of the 0.76 sprint. Please update PowerToys to the latest. https://github.com/microsoft/PowerToys/releases


Functional api/causal estimators

Introduce fit() method to estimators.
Refactor constructors to avoid using *args and **kwargs and have more explicit parameters.
Refactor refuters and other parts of the code to use fit() and modify arguments to estimate_effect()

test advanced


Improve ergonomics for "request name clashes"

Both xproto and shm have a CreatePixmap request. Thus, I had to write this:
https://github.com/psychon/x11rb/blob/79c97a7d032a44e8602c9c47a2cbe892092a2f10/examples/shared_memory.rs#L38
I think it would be better if one could write
shm::create_pixmap(conn, other arguments here)?;

The idea here is to add back the API that commit 6ad7969701261f1e6a023d89187cd2ececba5627 removed. So, each request would be available in two places: as a module-level function and on the extension trait (and the function in the trait would just delegate to the module-level function).

What about adding a prefix to trait functions? We would have conn.create_pixmap(...) and conn.shm_create_pixmap(...). For cases without name clashes, it would still help to quickly identify the extension of a request by looking at the method call.
For example, in randr there is add_output_mode, which has a unique name, but if someone sees conn.add_output_mode(...) might need some time to identify it as a randr request.

And xproto would get an empty prefix? Yeah, that sounds like a good idea.
(Also, what I proposed in this issue is long implemented.

And xproto would get an empty prefix? Yeah, that sounds like a good idea.

Exactly. I can work on it and send a PR unless you have started with it.

Feel free


Suppress output console

This is pretty annoying. Output console turns up anytime it wants and there is no way to get rid of it. Could you please fix rust plugin and stop doing this.

@pronebird,
Read the page.

@KalitaAlexey thanks, I have "rust.showOutput": false set and it doesn't work :/ RLS pops up the console each time it outputs something in there.

Oh. You use RLS.
Read.

@pronebird,
Have it helped you?

@KalitaAlexey Tested it with nightly RLS from rustup, new Rust plugin and new VSCode and it seems  to be working now!

It's nice.


Rental Start is always UTC

Bug: Rental Start is always UTC
Problem Description

What happens: A user inserts the rental start date in his/her local timezone but the system assumes all inputs are UTC.
What is the expected behaviour: The system accesses the timezone of the user and converts the input to UTC before writing it into the database
Why is this a problem: A user does not want to deal with converting the timezones before inserting his/her data. A developer does not want to deal with different timezones in the database. All dates should be in UTC.

Steps For Reproduction

add a new item with 12:00 in UTC+1 (Berlin time) as rental start
access the database and find the item
the time in the database is 12:00 in UTC (London time)
Furthermore if you now try to show the time in a view the time will be automatically converted to UTC+1 (Berlin time)

Hi, I tried to recreate the issue but it seems to save the correct time - added at 3.10 local time, duration 0 sec and it shows up as created/edited at 2.10 utc when checking the Database. That said i can’t find a view that shows more than just the date, so I don’t know how to check the last part.
Could you maybe double-check if you can still recreate it on the newest dev?


hypridle doesn't respect systemd-inhibit inhibitors

I think you have to implement something like this for swayidle: https://github.com/swaywm/swayidle/pull/48
To reproduce:
systemd-inhibit --what=idle --who=me --why="testing reasons" sleep infinity

And watch hypridle still lock (it's easy to test with this conf file:
listener {
    timeout = 2
    on-timeout = notify-send "idle"
    on-resume = notify-send "resumed"
}

#57 has been merged. This issue can be closed now.


[BEAM-8537] Update docstring of ManualWatermarkEstimator.set_watermark()

Follow up with Luke's comment: https://github.com/apache/beam/pull/10375#discussion_r382727370
R: @lukecwik

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Fix python formatting.

All tests passed. I'm going to merge it.


Updates go, golangci-lint, cosign

What type of PR is this?
/kind cleanup
/kind feature
What this PR does / why we need it:

set minimum go version to 1.20
bump cosign to v2.2.0
bump golangci-lint to v1.54.2

/hold for test-infra job change to test with go1.21
/assign @saschagrunert @xmudrii @Verolop
cc @kubernetes-sigs/release-engineering
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?

- set minimum go version to 1.20
- bump cosign to v2.2.0
- bump golangci-lint to v1.54.2

/test all

/unhold


Can you run it on the LUMEN with the DINGO API

from google translate

Actually, I never tested it with Lumen... You can try it yourself. Also I don't expect any problems with dingo/api.


Replacing constraints

Can you support replacing constraints? such as Cartography
let group = ConstraintGroup()

// Attach `view` to the top left corner of its superview
constrain(view, replace: group) { view in
    view.top  == view.superview!.top
    view.left == view.superview!.left
}

/* Later */

// Move the view to the bottom right corner of its superview
constrain(view, replace: group) { view in
    view.bottom == view.superview!.bottom
    view.right  == view.superview!.right
}

UIView.animateWithDuration(0.5, animations: view.layoutIfNeeded)

Hi @cp3hnu,
Updating constraints is already supported :)
Here is how your example translates with Stevia :
// Attach `view` to the top left corner of its superview
view.top(0).left(0)

/* Later */

// Move the view to the bottom right corner of its superview
removeConstraint(view.topConstraint!)
removeConstraint(view.leftConstraint!)
view.bottom(0).right(0)

UIView.animateWithDuration(0.5, animations: view.layoutIfNeeded)

In your case we have to remove previously set constraints.
Oftentimes though, we just want to update existing ones. For instance if we wanted to add some margins  to our previous example :
view.topConstraint?.constant = 20
view.leftConstraint?.constant = 20

// Animate it if we want
UIView.animateWithDuration(0.5, animations: view.layoutIfNeeded)

Hope it helps :)

Thank you. It's very helpful to me.


Brunch doesn't compile files at all since version 2.7.2, if they aren't located in the default directories ('app', 'test', 'vendor')

Description
I'm continuing learning Elixir/Phoenix using the default mix phoenix.new app, and yesterday I got an issue after receiving the new Brunch version 2.7.2. It just does not compile anything at all.
I looked at the changes in the last version and debugged the Brunch code a little bit.
I found out that if I comment line 438 in config.js, Brunch works correctly, as the previous version.
paths.watched = ['app', 'test', 'vendor'].map(joinRoot);

It seems that this line overwrites the value specified in the config with the default value ('app', 'test', 'vendor') and Brunch doesn't watch my files at all (they are located in web/static, my config is attached below, it's the default config of the phoenix.new app).
Expected behavior
I run brunch -build and it compiles .js files into app.js as described in the config file.
Actual behavior
app.js isn't created at all
Environment

Brunch: 2.7.2
Node: 5.10.1
NPM: 3.8.3
Operating system: Ubuntu 15.10

package.json contents
{
  "repository": {
  },
  "dependencies": {
    "babel-brunch": ">=6.0.0",
    "brunch": "2.7.2",
    "clean-css-brunch": ">=1.8.0",
    "css-brunch": ">=1.7.0",
    "javascript-brunch": ">=1.8.0",
    "uglify-js-brunch": ">=1.7.0",
    "phoenix": "file:deps/phoenix",
    "phoenix_html": "file:deps/phoenix_html"
  }
}

brunch config contents
  files: {
    javascripts: {
      joinTo: "js/app.js"
    },
    stylesheets: {
      joinTo: "css/app.css"
    },
    templates: {
      joinTo: "js/app.js"
    }
  },

  conventions: {
    assets: /^(web\/static\/assets)/
  },

  paths: {
    watched: [
      "web/static",
      "test/static"
    ],
    public: "priv/static"
  },

  plugins: {
    babel: {
      ignore: [/web\/static\/vendor/]
    }
  },

  modules: {
    autoRequire: {
      "js/app.js": ["web/static/js/app"]
    }
  },

  npm: {
    enabled: true,
    whitelist: ["phoenix", "phoenix_html"]
  }
};

Other useful files, when present (log, bower.json etc.)
@ubuntu:~/Sources/Elixir/sketch-guess$ ./node_modules/brunch/bin/brunch --version
2.7.2
@ubuntu:~/Sources/Elixir/sketch-guess$ ./node_modules/brunch/bin/brunch build -d
  brunch:config Trying to load brunch-config +0ms
  brunch:plugins Loaded plugins: babel-brunch, css-brunch, javascript-brunch +375ms
  brunch:watch add package.json +19ms
  brunch:watch add brunch-config.js +1ms
  brunch:watch add test/test_helper.exs +6ms
  brunch:list Reading test/test_helper.exs +1ms
  brunch:watch add test/controllers/page_controller_test.exs +10ms
  brunch:list Reading test/controllers/page_controller_test.exs +1ms
  brunch:watch add test/support/channel_case.ex +0ms
  brunch:list Reading test/support/channel_case.ex +0ms
  brunch:watch add test/support/conn_case.ex +0ms
  brunch:list Reading test/support/conn_case.ex +0ms
  brunch:watch add test/support/model_case.ex +1ms
  brunch:list Reading test/support/model_case.ex +0ms
  brunch:watch add test/views/error_view_test.exs +0ms
  brunch:list Reading test/views/error_view_test.exs +1ms
  brunch:watch add test/views/layout_view_test.exs +1ms
  brunch:list Reading test/views/layout_view_test.exs +0ms
  brunch:watch add test/views/page_view_test.exs +0ms
  brunch:list Reading test/views/page_view_test.exs +0ms
  brunch:write Writing 0/0 files +69ms
24 Apr 08:22:01 - info: compiled in 757ms

Wow, thanks for pointing that out! I must have forgotten to change it to paths.watched.map... https://github.com/brunch/brunch/pull/1314 will fix it! 🙈
Sorry for that!

Thanks! :)
I'd like to use an opportunity and ask a kind of off-topic question about practices in Brunch.
Let's imagine I made some changes / features / refactorings and want to create a pull request.

Should I write some tests for my changes or new features?
How could I make sure that I didn't break something?

Brunch isn't a very small project and it's suggested as a 'default solution' for some frameworks, but I found only ~10 tests in this repository. Is it something like an issue or there are some other ways to ensure its consistency? :)
Thank you again!


chore: latest backport changes

:tada: This PR is included in version 6.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Backport 2.9] Fix the retry-on-conflict logic in the systemcharts package

Backport for https://github.com/rancher/rancher/issues/47914

Closing this issue as the relevant code does not exist in this branch.


add export keyword

add export keyword
While working on setting up aiconfig, there was a bit of confusion surrounding the OPENAI_API_KEY. Thought we should be explicit in including the export keyword in all of the comments.

Is this diff ready to be merged?

Is this diff ready to be merged?

Yes it is, this is Victor's first OS pull request, so he didn't realize he needed to click "Merge pull request". Synced with him offline :)


nixpkgs docs: syntax highlight

Motivation for this change

Closes https://github.com/NixOS/nixpkgs/issues/4901
Supersedes https://github.com/NixOS/nixpkgs/pull/7034

Should backport to 18.03.
I plan on merging this in 12-24hrs.

:tada:


Recognition using DWT algorithm

Implement Recognition using DWT DISCRETE WAVELET TRANSFORM

@akshitagupta15june  Can I work On this issue? please let me know

Assigning

Thanks , @akshitagupta15june


Support reading data that uses old NdArray name

Revert part of #608, allowing the continued use of older datasets.

Could we make it entirely case-insensitive?

Could we make it entirely case-insensitive?

We could, but that really doesn't solve the underlying problem (which IMHO is a missing test and code that doesn't clearly differentiate between the class name and the storage format "magic string").
Probably better to create a set of global Literal variables that contain the magic strings used in the storage format, rather than assuming they are eq with the class name and/or SOMA type....

Could we make it entirely case-insensitive?

Discussed off-GitHub: everyone is OK with this as-is.


Workers can't be gen_servers?

Hi,
from a quick look at the respective mzbench modules, worker processes can't be gen_servers, right?
Just want to be sure. Sorry for asking basic questions.

Yeah, you right.
Basically worker module is just the implementation of functions you want to use in your script.

Got it. Thanks.


FoldAll() only folds top level

Am I doing soemthin wrong or is it intentional that FoldAll() only folds top level foldings ?
I found that the below code effectively folds all levels :
foreach (Line thisLine in tbPyScriptCode.Lines) thisLine.FoldLine(FoldAction.Contract);

At the same time, FoldAll(FoldAction.Expand) does unfold all levels. So why does it not fold all levels ?

You can read about FoldAll in the original Scintilla documentation here: http://www.scintilla.org/ScintillaDoc.html#SCI_FOLDALL.
As I understand it, your observations match the documentation. FoldAll will not affect child folds.
You might be able to enhance your workaround above by switching to thisLine.FoldChildren(FoldAction.Contract);

Thank you for the quick answer.


Add support for OpenEncryptedFileRaw and related functions.

Issue by alphaleonis from Friday Jan 02, 2015 at 19:33 GMT
Originally opened as https://github.com/alphaleonis/AlphaFS/issues/3

Encryption/decryption happens automatically with most of the regular api calls if the right cert is installed.
However there are situations when if the drive was taken out of the computer for forensic analysis, you would need to access the encrypted files.
In that situation there is usually a delegated decryption user's certificate is stated in the encrypted files metadata, usually it is a active directory primary administrator who allowed the EFS to be used by regular users. So you would need to acquire the cert from that admin to the computer which will try to decrypt affected files.
I think think we could add some extra methods when the right Windows license with EFS lands on one of our hands.

Comment by alphaleonis from Friday Jan 02, 2015 at 19:34 GMT

Copied from CodePlex. Comments:
lambchops wrote Feb 14, 2013 at 3:27 AM
Downloaded src to have a look at implementing these functions.... but a little lost as it appears that in the releases folder, there is 1.0 and not 1.5. Looking at the changes log it seems that you are up to 1.6? Functions like File.OpenBackupRead do not seem to be there.
Please advise :) thnx
Yomodo wrote Feb 14, 2013 at 10:37 AM
Hi,
Just download and use the latest development build to start implementing.
Perhaps the BackupFileStream() and/or BackupStreamInfo() classes have what you need.
Regards,
Yomodo


foolstools

Fool's Tools
Created by accident, destined to greatness.

Thank you for considering our project!

Developers who applied for the program should provide their KuCoin UID in their PR, and KCC will contact them via the email address linked with the UID.

Thanks, just did:
https://github.com/kcc-community/kcc-grants/pull/7/commits/3c3d121db21dbf19f4119cf96e2f1c4b8e0210ff
Sorry for the delay, the notification ended up in a busy folder.
Il giorno lun 9 ago 2021 alle ore 06:09 Leandre @.***>
ha scritto:

Developers who applied for the program should provide their KuCoin UID in
their PR, and KCC will contact them via the email address linked with the
UID.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kcc-community/kcc-grants/pull/7#issuecomment-894936863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALFIGQGHLBAZSVFPM43XDTT35IHJANCNFSM47PXXYXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

No email bind on your KUCOIN account, please bind an email.

No email bind on your KUCOIN account, please bind an email.

Done.

No email bind on your KUCOIN account, please bind an email.

Also submitted ID verification

No email bind on your KUCOIN account, please bind an email.

Also submitted ID verification

check your email

Just did, but if there was anything related to this I didn't see it.
Il giorno lun 16 ago 2021 alle ore 10:18 Leandre @.***>
ha scritto:

No email bind on your KUCOIN account, please bind an email.
Also submitted ID verification
check your email
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kcc-community/kcc-grants/pull/7#issuecomment-899317604,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALFIGS3VISEY3XEM6ZHQALT5DCVDANCNFSM47PXXYXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

email was sent to<EMAIL_ADDRESS>

email was sent to<EMAIL_ADDRESS>
Hi, the last mail I see is from Aug 12th, asking to link an email in Kucoin. I replied Aug 12th telling that the linked email is<EMAIL_ADDRESS>(for convenience, since that address it's always checked despite individual holidays).


fix double encryption when sending dms, when login with external signer set privKey to null to be sure we have no private keys

hum... We need to figure out a better way to converge the two signing procedures between Local and Amber.


eufy platform error: maximum recursion depth exceeded while calling a Python object

Using this package through Home Assistant's Eufy core integration results to the following error. It's unclear to me how this arises though as to me it seems random. It can work fine for a long time and then one day it no longer does.
2021-10-13 19:09:42 ERROR (MainThread) [homeassistant.components.switch] Error while setting up eufy platform for switch
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/eufy/switch.py", line 11, in setup_platform
    add_entities([EufySwitch(discovery_info)], True)
  File "/usr/src/homeassistant/homeassistant/components/eufy/switch.py", line 26, in __init__
    self._switch.connect()
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 229, in connect
    return device.connect(self)
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 66, in connect
    self.update()
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 246, in update
    response = self.get_status()
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 242, in get_status
    response = self.send_packet(packet, True)
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 232, in send_packet
    return device.send_packet(self, packet, response)
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 90, in send_packet
    self.connect()
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 229, in connect
    return device.connect(self)
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 66, in connect
    self.update()
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 246, in update
    response = self.get_status()
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 239, in get_status
    packet.sequence = self.get_sequence()
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 235, in get_sequence
    return device.get_sequence(self)
  File "/usr/local/lib/python3.9/site-packages/lakeside/__init__.py", line 112, in get_sequence
    packet.sequence = random.randrange(3000000)
  File "/usr/local/lib/python3.9/site-packages/google/protobuf/internal/python_message.py", line 702, in field_setter
    new_value = type_checker.CheckValue(new_value)
  File "/usr/local/lib/python3.9/site-packages/google/protobuf/internal/type_checkers.py", line 152, in CheckValue
    if not isinstance(proposed_value, numbers.Integral):
  File "/usr/local/lib/python3.9/abc.py", line 119, in __instancecheck__
    return _abc_instancecheck(cls, instance)
  File "/usr/local/lib/python3.9/abc.py", line 123, in __subclasscheck__
    return _abc_subclasscheck(cls, subclass)
RecursionError: maximum recursion depth exceeded while calling a Python object

The actual log is 2K lines long and Github won't let me upload it. Full log here

It sounds like #15 might be the same issue, but more details of what's happening.


Manage Submission Windows

As an administrator I want to open and close submission windows so that I an control the ability for users to submit emissions data.

Will need the ability to open and close general windows and single windows for particular units. During a single window the unit may only submit once and only once.


Unrecoverable fork at 2140569 and forked checkpoint

Describe the bug
Unrecoverable fork issued at 2140569.
Current checkpoint (from 2023-03-18) provides forked chain at height 2140978 (best block: a34b9c3b175e89f394971041aeab914ab759a8437de15cf0230efaac42036cd5).
To Reproduce

Install forked checkpoint
Run node and wait for outbound connections to other nodes
Following messages in debug.log:

2023-03-18T21:35:33Z New outbound peer connected: version: 70016, blocks=2142704, peer=0, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-03-18T21:35:33Z Synchronizing blockheaders, height: 2142704 (~100.00%)
2023-03-18T21:35:33Z     Block checked with result 1: Height: 2140569 BH: aeb0a0458361adbe49e7cca4330c9ce5128f52288947f13506984189678ba592
2023-03-18T21:35:33Z Rollback current block to prev at height 2140977
2023-03-18T21:35:37Z Rollback current block to prev at height 2140976
...
2023-03-18T22:02:25Z Rollback current block to prev at height 2140569
2023-03-18T22:02:29Z Rollback current block to prev at height 2140568
2023-03-18T22:02:36Z Warning: SocialConsensus type:305 validate tx:0597aa5dc60e70a16d497b89d58ef337749f4cd751ba967e232099d905c35bdc blk:aeb0a0458361adbe49e7cca4330c9ce5128f52288947f13506984189678ba592 failed with result:23 at height:2140569
2023-03-18T22:02:36Z WARNING: SocialConsensus validating failed with result 23 for block aeb0a0458361adbe49e7cca4330c9ce5128f52288947f13506984189678ba592
2023-03-18T22:02:36Z ERROR: ConnectTip: ConnectBlock aeb0a0458361adbe49e7cca4330c9ce5128f52288947f13506984189678ba592 failed, failed-validate-social-consensus
2023-03-18T22:02:47Z     Block validated: 2140569 BH: 7aec19f7c5f7673fe46c3ba56ec8d3ed0ab7bd3da4354d62b11c8a48231b97a9
2023-03-18T22:03:04Z     Block indexed: 2140569 BH: 7aec19f7c5f7673fe46c3ba56ec8d3ed0ab7bd3da4354d62b11c8a48231b97a9
2023-03-18T22:03:04Z +++ Block connected to chain: 2140569 BH: 7aec19f7c5f7673fe46c3ba56ec8d3ed0ab7bd3da4354d62b11c8a48231b97a9
2023-03-18T22:03:05Z     Block validated: 2140570 BH: 5fbd6e7ceda9118ad4ad366c58c52af0cbfbea838afe10b1d45b84a10f4e3200
2023-03-18T22:03:05Z     Block indexed: 2140570 BH: 5fbd6e7ceda9118ad4ad366c58c52af0cbfbea838afe10b1d45b84a10f4e3200
2023-03-18T22:03:05Z +++ Block connected to chain: 2140570 BH: 5fbd6e7ceda9118ad4ad366c58c52af0cbfbea838afe10b1d45b84a10f4e3200
...
2023-03-18T22:17:45Z     Block validated: 2140978 BH: a34b9c3b175e89f394971041aeab914ab759a8437de15cf0230efaac42036cd5
2023-03-18T22:17:46Z     Block indexed: 2140978 BH: a34b9c3b175e89f394971041aeab914ab759a8437de15cf0230efaac42036cd5
2023-03-18T22:17:46Z +++ Block connected to chain: 2140978 BH: a34b9c3b175e89f394971041aeab914ab759a8437de15cf0230efaac42036cd5
2023-03-18T22:17:46Z Disconnecting and discouraging peer 0!
2023-03-18T22:17:47Z New outbound peer connected: version: 70016, blocks=2142742, peer=2, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-03-18T22:17:47Z Synchronizing blockheaders, height: 2142742 (~100.00%)
2023-03-18T22:17:47Z     Block checked with result 1: Height: 2140569 BH: aeb0a0458361adbe49e7cca4330c9ce5128f52288947f13506984189678ba592
2023-03-18T22:17:48Z Rollback current block to prev at height 2140977
2023-03-18T22:17:52Z Rollback current block to prev at height 2140976
...

Expected behavior
Rollback to 2140568 block then validating and connecting 2140569 block to chain with valid hash (aeb0a0458361adbe49e7cca4330c9ce5128f52288947f13506984189678ba592).
Host and node version:

OS: Ubuntu (docker container)
Version: 0.21.2

We are dealing with the problem

When you do a bug report like this in future. I highly suggest giving a list of the connected nodes. Old versions of nodes can influence and cause this issues (and have done in the past).
Where there any versions of the node software lower than V21 connected at the time?
@AOK can you give us an update of what's possibly causing this because lots of node operators are getting this or similar at the moment. An update in the node chat would be good.

When you do a bug report like this in future. I highly suggest giving a list of the connected nodes.
According to provided report and log there were no connections as it was cold start from forked checkpoint (at height 2140978) obtained from snapshot.pocketnet.app!
If we see at first line of log:
''''
2023-03-18T21:35:33Z New outbound peer connected: version: 70016, blocks=2142704, peer=0, peeraddr=<IP_ADDRESS>:37070 (full-relay)
''''
Then we found that first connection (due to peer=0) was made to <IP_ADDRESS> peer with strange 70016 version!
Unfortunately node software versions (like 0.21.1) not dumped to logs!

If we analyze log further then we found that fork was detected and node began rollback to 2140568 best block.
Unfortunately 2140569 block was not correctly validated and new fork began:
2023-03-18T22:02:36Z Warning: SocialConsensus type:305 validate tx:0597aa5dc60e70a16d497b89d58ef337749f4cd751ba967e232099d905c35bdc blk:aeb0a0458361adbe49e7cca4330c9ce5128f52288947f13506984189678ba592 failed with result:23 at height:2140569
2023-03-18T22:02:36Z WARNING: SocialConsensus validating failed with result 23 for block aeb0a0458361adbe49e7cca4330c9ce5128f52288947f13506984189678ba592
2023-03-18T22:02:36Z ERROR: ConnectTip: ConnectBlock aeb0a0458361adbe49e7cca4330c9ce5128f52288947f13506984189678ba592 failed, failed-validate-social-consensus
2023-03-18T22:02:47Z     Block validated: 2140569 BH: 7aec19f7c5f7673fe46c3ba56ec8d3ed0ab7bd3da4354d62b11c8a48231b97a9
2023-03-18T22:03:04Z     Block indexed: 2140569 BH: 7aec19f7c5f7673fe46c3ba56ec8d3ed0ab7bd3da4354d62b11c8a48231b97a9
2023-03-18T22:03:04Z +++ Block connected to chain: 2140569 BH: 7aec19f7c5f7673fe46c3ba56ec8d3ed0ab7bd3da4354d62b11c8a48231b97a9

At the moment, together with @lostystyg, we are studying this problem, although at our stand the error is different - number 12, which indicates that there is no necessary data to connect the block from the main chain and (here's the problem) goes into fork again.

I can share forked checkpoint (from 2023-03-18) to help reproduce error number 23!

We have one copy for analysis, but please leave yours just in case. After yesterday's study, we have so far come to the preliminary conclusion that the forks are related to the late update of some nodes, as some releases include consensus changes (adding new types of transactions or changing their behavior). Maybe you still have a log file that shows the version of the node starting from 0.20.29?

I have 2 log files with node forking (banner.log and debug.log).
In banner.log there were following lines regarding old node (time in GMT+3):
2023-03-16 13:25:52 === Old node version banned (0.20.29): 2023-03-16 13:25:52 <IP_ADDRESS>:12362        /Satoshi:0.20.29/       2019352 -1      -1      328     7711    2023-03-16 13:25:02     inbound

What is the date of the first record in debug.log?

Near about 2023-03-16T21:50:00Z.
Can't attach debug.log as a file.
Seems that my node was forked by <IP_ADDRESS> peer with 0.20.29 version.

Found connected node list dumped about 2023-03-16T23:06:35Z:
$ pocketcoin-cli getpeerinfo | jq -r '.[] | [.addr, .subver, .pingtime, .startingheight, .synced_headers, .synced_blocks, .bytesrecv, .bytessent, (.conntime|todate), .timeoffset, .connection_type] | @tsv' | column -t
<IP_ADDRESS>:37070     /Satoshi:0.21.1/  0.012638  2139830  2139929  2139929  445910   9142    2023-03-16T21:58:53Z  0   block-relay-only
<IP_ADDRESS>:37070    /Satoshi:0.21.1/  0.010894  2139830  2139931  2139931  952776   17250   2023-03-16T21:58:54Z  -1  block-relay-only
<IP_ADDRESS>:37070     /Satoshi:0.21.1/  0.201046  2139830  2139929  2139929  691146   251659  2023-03-16T21:59:16Z  1   outbound-full-relay
<IP_ADDRESS>:37070    /Satoshi:0.21.2/  0.129884  2139831  2139929  2139929  498847   94594   2023-03-16T21:59:24Z  1   outbound-full-relay
<IP_ADDRESS>:37070  /Satoshi:0.21.2/  0.017554  2139831  2139931  2139931  551241   419525  2023-03-16T21:59:34Z  2   outbound-full-relay
<IP_ADDRESS>:37070    /Satoshi:0.21.2/  0.038438  2139831  2139931  2139931  312999   107954  2023-03-16T21:59:35Z  1   outbound-full-relay
<IP_ADDRESS>:37070   /Satoshi:0.21.1/  0.132026  2139831  2139931  2139931  571476   96049   2023-03-16T21:59:35Z  1   outbound-full-relay
<IP_ADDRESS>:37070   /Satoshi:0.21.1/  0.022291  2139831  2139931  2139931  1216752  95616   2023-03-16T21:59:54Z  -1  outbound-full-relay
<IP_ADDRESS>:37070   /Satoshi:0.21.1/  0.161434  2139832  2139929  2139929  161682   107349  2023-03-16T22:00:06Z  2   outbound-full-relay
<IP_ADDRESS>:54132    /Satoshi:0.21.2/  0.018141  2139871  2139930  2139930  462779   90495   2023-03-16T22:30:16Z  2   inbound
<IP_ADDRESS>:37070     /Satoshi:0.21.2/  0.042353  2139903  2139931  2139931  57315    20569   2023-03-16T23:06:35Z  1   outbound-full-relay

<IP_ADDRESS> was not connected and therefore not banned by banner script! It was connected and banned only at 2023-03-17 18:05.
I thought that one of 0.21 connected node was forked and then poisoned my node.

I am inclined to the fact that there are several nodes in the fork in the network. I have no idea how to return all nodes to the main chain - this situation is normal and should be resolved over time

In version 0.22, an optional disconnectold argument has been added to disable old nodes or nodes in the fork - this should solve some of the problems with outdated nodes and the potential forks they cause.