Following pagination

Hi,
Nice little gem so far. I'm trying for scrape info across a number of pages. What I'd like to do is something such as this pseudo code:
load page
scrap page content
if next page link, follow link and loop to top
else done

Is there any way I can achieve this currently?
Thanks

I solved my issues by not using Wombat, instead using Mechanize directly.


Support for unmarshalling top-level links

Is your feature request related to a problem? Please describe.
The package does not support unmarshalling top-level links, usually utilizes for pagination.
Describe the solution you'd like
UnmarshalOption to export the links from top-level, which has been done with meta.  for example:
body := `{"data":{"id":"1","type":"articles","attributes":{"title":"Hello World"}},"links":{"self":"foobar"}}`

type Article struct {
    ID    string `jsonapi:"primary,articles"`
    Title string `jsonapi:"attribute"        json:"title"`
}

var (
    a Article
    l jsonapi.Link
)

err := jsonapi.Unmarshal([]byte(body), &a, jsonapi.UnmarshalLinks(&l))
// l.self = "foobar"

Describe alternatives you've considered
n/a

Thanks for the contribution! This feature is now supported as of v0.10.0


Adding support for custom accessibility actions on iOS.

Motivation
This feature has been requested by customers.  Our previous (pre-react) application had support for custom accessibility actions.
This feature allows UI elements to provide a list of custom actions that can be read when VoiceOver is enabled.  UI elements expose one accessibility action by default.  Some UI elements may support multiple actions though other mechanisms like tap and hold.  To expose these actions in an accessible way iOS provides custom accessibility actions.
Test Plan
Feature was tested in the iOS simulator using the Accessibility Inspector.  Custom actions were added to a button and observed in the tool.  Custom actions were also invoked using the tool and then stepped through in the debugger.
The feature was also tested on an iPhone.  VoiceOver was enabled on the device and custom actions were observed for controls that exposed them.
We have been using this feature in our app for some time as well.
Release Notes
[IOS] [ENHANCEMENT] [Accessibility] - Added support for custom accessibility actions
Eric Davison
Microsoft Corp.

Thanks for adding this! Can you update the website docs as well? https://github.com/facebook/react-native-website/blob/master/docs/view.md


Detect existing Wireguard tunnels and choose a different port

When installing on a Linux machine that has existing Wireguard tunnels, Netbird still tires to use port 51820. Editing the config.json to a new port gets things running, but having it automatically detect that port 51820 is in use at first "up" would be great, as it could then pick an unused port

Thanks, @timwsuqld, for the suggestion. This makes sense, and we have initial support for custom ports by editing the config file at /etc/netbird/config.json and changing the value of WgPort.
relates to #566


drivers: remove unimplemented open/close/ioctl interfaces

Summary

Remove unimplemented open/close/ioctl interfaces
Fix style issues
Use sizeof in snprintf

Impact
None
Testing
Pass CI

@xiaoxiang781216 could you please merge the PR?

Yes, I was thought that the compiler error doesn't fix yet.


feat: support 2fa

Fix: #81
Signed-off-by: sh1luo<EMAIL_ADDRESS>

demo link: http://testb.rescld.cn/

@Kininaru plz review.

@sh1luo plz resolve conflicts.

@sh1luo plz resolve conflicts.

ok

@hsluoyz ok, done. current demo link: http://testb.rescld.cn/

@sh1luo resolve conflicts:

I'm solving this problem, it's a little tricky

@sh1luo resolve conflicts:

ok, done.

@sh1luo link committer to github:

@hsluoyz what's wrong with this PR?

@hsluoyz  done, now demo link: http://testb.rescld.cn/

@hsluoyz  plz review

@hsluoyz plz review

@hsluoyz plz review

@hsluoyz This time I enhanced maintainability and code readability, plz review
demo link: http://testb.rescld.cn/

@hsluoyz plz review

@hsluoyz review plz

@sh1luo if verification code is wrong, then button hangs.

@sh1luo plz fix conflicts

@sh1luo plz fix conflicts

I know, but I don’t know why there are so many commits. I need to solve this problem first.

@hsluoyz everything is ok, plz review.
Demo link: http://testb.rescld.cn/

@hsluoyz  Why this pr is closed, and where is it not good enough?

Why this pr is rejected?
Any update?

The frontend code quality is not good. @yorkane can you make a new PR?


"Failed processing buffer payload" on start_acquisition()

Describe the Bug
I got 4 cameras on 2 framegrabbers. Each of the cameras occupies 2 coaxpress lanes on the framegrabber. I can detect all of the cameras via harvester, and also read and write to the framegrabbers and cameras (e.g. exposure time) via the node map. For testing purposes I unplugged 3 of the 4 cameras. As soon as I try acquiring images (ia.start_acquisition()), I get the following error message:
GenTL producer does not implement IFGetParentTL
GenTL producer does not implement DevGetParentIF
GenTL producer does not implement DSGetParentDev
GenTL producer does not implement DSGetNumBufferParts
GenTL producer does not implement DSGetBufferPartInfo
[(id_='Channel #1', vendor='Unknown Vendor', model='Unknown Model', tl_type='CXP', user_defined_name=None, serial_number='SN1234', version=None), (id_='Channel #3', vendor='Unknown Vendor', model='Unknown Model', tl_type='CXP', user_defined_name=None, serial_number='SN1234', version=None), (id_='Channel #1', vendor='Unknown Vendor', model='Unknown Model', tl_type='CXP', user_defined_name=None, serial_number='SN1234', version=None), (id_='Channel #3<PHONE_NUMBER>00122)', vendor='Mikrotron GmbH', model='MC1289', tl_type='CXP', user_defined_name=None, serial_number='SN1234', version=None)]

Traceback (most recent call last):
  File "c:/Users/friff/02-Harvesters/harvester_test.py", line 94, in <module>
    ia.start_acquisition()
  File "C:\Users\friff\02-Harvesters\env\lib\site-packages\harvesters\core.py", line 2507, in start_acquisition
    data_stream=ds, buffers=self._announced_buffers
  File "C:\Users\friff\02-Harvesters\env\lib\site-packages\harvesters\core.py", line 2916, in _queue_announced_buffers
    data_stream.queue_buffer(buffer)
  File "C:\Users\friff\02-Harvesters\env\lib\site-packages\harvesters\core.py", line 212, in queue_buffer
    self._module.queue_buffer(announced_buffer)
  File "C:\Users\friff\02-Harvesters\env\lib\site-packages\genicam\gentl.py", line 3813, in queue_buffer
    return _gentl.DataStream_queue_buffer(self, buffer, clear_buffer)
_gentl.ErrorException: GenTL exception: Unspecified runtime exception. (Message from the source: Failed processing buffer payload (PHX_BUFFER_MAKE_READY) Failed to Read CXP Device Addr=0x00000004, NumBytesToRead=0x00000004, BytesRead=0x00000000, with Library Error 0x0000000f (MDA_CxpIoctl returned error code 0xf) [DSGetBufferInfo]) (ID: -1001)

To narrow down possible subjects causing the issue above, I shortened the code to the bare minimum. The code raising the exception above is as follows:
from harvesters.core import Harvester
import os

h = Harvester()
path = os.getenv("GENICAM_GENTL64_PATH") + "TLActiveSilicon.cti"

h.add_file(path)
h.update()

print(h.device_info_list)
print("\n\n")

ia = h.create_image_acquirer(3)

ia.start_acquisition()

exit()

However, using ActiveCapture I can view a live stream. As far as I understand, this software uses the GenTL interface as well. Further, using another firmware on the framegrabber (but also only 2 lanes for one camera), which supports only one camera per framegrabber, I can obtain images. Unfortunately I would need the complete setup with all four cameras on two framegrabbers working.
Configuration
I am using the following setup:

Framegrabber: 2x FireBird CoaXPress Frame Grabber (Quad CXP-6)  (AS-FBD-4XCXP6-2PE8)
Camera: 4x Mikrotron  EoSens 12CXP+  (MC1289)
OS: Windows 10
Python 3.7.9
Harvester: 1.3.2
GenTL Producer: ActiveSilicon (TLActiveSilicon.cti)

Actions You Have Taken

[x] I've read the Harvester FAQ page.

Also had a look into all documentation (cameras, framegrabbers, phx references, harvester documentation, core.py..) I could find. Unfortunately I was not able to find any further information on "MDA_CxpIoctl" which seems to be the C++ (?) function causing the issue.
Any help would be greatly appreciated!

I was able to resolve the issue, the cti file was faulty. Active Silicon was able to provide me with an updated one.


Postinstall script doesn't work on Windows

><EMAIL_ADDRESS>postinstall
> mkdir -p ./public && cp -R ./node_modules/@uswds/uswds/dist/ ./public/uswds/

The syntax of the command is incorrect.
npm ERR! code 1
npm ERR! path C:\Users\Hollenshead.Sawyer.Q\Dev\claim-status-prototype\app
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c mkdir -p ./public && cp -R ./node_modules/@uswds/uswds/dist/ ./public/uswds/

cp doesn't appear to work, but this did:
Copy-Item ".\node_modules\@uswds\uswds\dist\*" -Destination ".\public\uswds" -Recurse

Is this because you are using powershell? If so, that makes a lot of sense.

@rocketnova Yea, I think that's what this Dell defaulted to in VS Code. I assume you mean the alternative being running in Docker? Or is there an instance where this should work on Windows outside of Docker currently?

@sawyerh Yeah, I expect that this won't work out of the box on Windows/powershell outside of docker and that you'd need to use Copy-Item in that case.


Don't call static() when constructing HalloPlugins

This isn't necessary, since Django form media fills in static paths itself - and doing it at module level will break on startup with certain staticfiles configurations if collectstatic hasn't run yet. Fixes #3829

Note: this will need testing against Django 1.8, because the Django form media was only updated to use django.contrib.staticfiles in Django 1.10:
https://docs.djangoproject.com/en/1.11/topics/forms/media/#paths-in-asset-definitions

On Django 1.8, removing the explicit static means that ManifestStaticFilesStorage hash suffixes aren't added - so if a user happens to be running Django 1.8 and relying on ManifestStaticFilesStorage, then this is a regression. (As it happens, wagtail.contrib.settings and wagtail.contrib.table_block already use form media without explicit static, so these would already be affected by the lack of cache-busting on such a setup.)
I think this is more of a Django bug than a Wagtail one, though: converting a relative static path to a full URL is something that Django form media was meant to do all along, and the fact that it didn't do so in a staticfiles-compliant way is not something Wagtail should be expected to work around, IMO.

Merged in 92b4f68c67e36ee63b0902dbbf5187e8cf243b0c (master) and 28907c14db284f7889b15262709a5cf2d18fd6e5 (stable/1.12.x).


Color shifting & slight changes to unmasked area when outpainting

Seeing some strange shifts to the unmasked (not supposed to be edited) region of images when outpainting:

I started with the left image (512x512), and extended to the right with a mask preserving the original image. However, the preserved section is changed, as you can see in the image above. I repeated this to extend further right, and the same thing happened. Each time the image seems to get a little darker, and on close inspection, the fine details seem sharper.
The image being passed into do_run() is unchanged from the original (I saved a copy just before inference to be sure).
Any ideas how to fix this?

could you upload the initial image and the command you used? Are the seams present in the outpainted image, or just when comparing against the original image?

Yes of course - here is another example with images saved at each step. Note that instead of using the repo's outpainting code, I'm generating shifted images and masks and then calling the model programatically.
Original image generated with standard Stable Diffusion:

Next, I create a new image that shifts to 50% to the right, and create a mask so the left half (containing part of the original image) is preserved, and the right half is masked for inpainting.

Left side (white) will be original image, right side (black) is the region to be outpainted.
Leaving the "extended" / masked area of the image blank seems to lead to some huge seams along the edge. I've been experimenting with filling the empty area with a mirrored version of the image, along with other ideas for filling the space, and it helps a lot.
With mirroring, my input image becomes:

(the white lines on the bottom/right are a bug in my mirroring code but don't seem to actually impact anything)
Running the model on these images outputs this:

You can tell where the mask edge was, but that's not a big deal. (Though if you have thoughts on how to fix that too I'd be interested...)
The output image looks good on its own, however, if I overlay part of the input image, you can tell that the whole image has been slightly changed, including the unmasked half:

The left quarter is overlayed from the input image, and the rest is the output image.

ok I see. The first thing is that the model doesn't like hard edges - it sees the edge and thinks it's the beginning of a separate frame. I usually just roughly paint over the straight edge of the mask and it works a lot better. I think this means the model is undertrained, because the training procedure does expose the model to hard edges like this.
the root cause of the color cast is the latent diffusion VAE, there's not a lot that can be done other than post processing unfortunately.
for repeated inpaint/outpaints I'd try using the output_npy/00000.npy files instead of the output/00000.png images. The npy files contain the latent diffusion codes so it won't suffer re-compression when you encode the image.
The latent diffusion VAE is a form of lossy compression so if you put the output pngs back through it'll slowly accumulate VAE artifacts and color cast. Using the .npy files will still incur one instance of VAE compression though, if you're staring with a png.
The VAE throws out a lot of color information it deems to be unimportant perceptually. If you encode then decode any image with this VAE there's almost always a color cast.

Ah OK, that makes sense. I wondered if it might be some kind of image compression but didn't know the VAE was responsible. For now I'll explore using the npy files and fixing things up with postprocessing.
Thanks for the help!


Add accessibility support for easier acceptance tests with KIF

I added an accessibilityLabel for each cell, which is a NSString representation of the NSIndexPath.
This makes it easier to do acceptance tests with KIF for apps that use the component and maybe in the future to write acceptance tests for the component itself.
I tried using the KIF built-in methods to select a row in a UITableView but in this particular case it didn't work.
If this PR is merged, it will be enough to write:

[tester tapViewWithAccessibilityLabel:[MLPAutoCompleteTextField accessibilityLabelForIndexPath:[NSIndexPath indexPathForItem:0 inSection:0]]];

This doesn't seem right. This makes it unusable by blind people who rely on accessibility labels!

You made a good point! Somebody has to create another PR with the fixes necessary to make it work reliably with KIF and usable for people who rely on the accessibility label!


Support Unicode 9 prepended concatenation marks

It’s still a proposal for now, but hey. http://blog.unicode.org/2015/11/new-character-property-for-prepended.html Prepended_Concatenation_Mark

Just curious... it looks like Prepended_Concatenation_Marks were added in Unicode 8 (ref)? I do see mention of these marks in Unicode 9, but I can't tell if any new ones were added.
And on that note... the package.json for this library is still using Unicode 8, shouldn't it be updated for v9?

http://unicode.org/reports/tr29/#Table_Combining_Char_Sequences_and_Grapheme_Clusters


Can't make flash esp32-at.

make flash in esp32-at directory result in:
In function at_setupCmdBleAddr': (.text.at_setupCmdBleAddr+0x1d): undefined reference to esp_ble_gap_clear_rand_addr'
collect2.exe: error: ld returned 1 exit status
Can anyone helpme?

Noob question here but how do I update the ESP_IDF in the esp-at project ?


File/Character Encoding

Issue Type: Bug
This occurs with VS Code under Linux.
Open a text file in vi/notepad or similar basic editor.
Paste the text from the "escape" BNF grammar found here into the text file as a C++ comment (or code, see below) and save as a .cpp file.  Verify that you can compile this with GCC/Clang.
https://www.w3.org/TR/CSS1/#appendix-b
escape		{unicode}|\[ -~¡-ÿ]
i.e.
bool CssParser::IsEscaped()
{
	// @reference [http://www.w3.org/TR/CSS1#appendix-b]
	// unicode		\\[0-9a-f]{1,4}
	// escape		{unicode}|\\[ -~¡-ÿ]

	return (Is('\\') && (IsHex(1) || IsPrintable(1) || IsRange(1,'¡','ÿ')));
}

Open the same file in VS Code then modify something and then save, the text will have been converted into UTF8 with 3 bytes being used to represent the Latin1 ASCII character that was previously there.
This then becomes un-compilable since C++ doesn't natively compile UTF8 strings.
bool CssParser::IsEscaped()
{
	// @reference [http://www.w3.org/TR/CSS1#appendix-b]
	// unicode		\\[0-9a-f]{1,4}
	// escape		{unicode}|\\[ -~�-�]

	return (Is('\\') && (IsHex(1) || IsPrintable(1) || IsRange(1,'�','�')));
}

You will get a compiler error similar to the following:
``
error: character too large for enclosing character literal type
return (Is('\') && (IsHex(1) || IsPrintable(1) || IsRange(1,'�','�')));

VS Code version: Code 1.54.2 (fd6f3bce6709b121a895d042d343d71f317d74e7, 2021-03-11T00:56:11.840Z)
OS version: Linux x64 5.9.0-kali1-amd64

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (4 x 2592)|
|GPU Status|2d_canvas: unavailable_software
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: disabled_off
protected_video_decode: disabled_off
rasterization: disabled_software
skia_renderer: enabled_on
video_decode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software|
|Load (avg)|1, 1, 1|
|Memory (System)|7.75GB (0.13GB free)|
|Process Argv|--no-sandbox --unity-launch|
|Screen Reader|no|
|VM|100%|
|DESKTOP_SESSION|lightdm-xsession|
|XDG_CURRENT_DESKTOP|XFCE|
|XDG_SESSION_DESKTOP|lightdm-xsession|
|XDG_SESSION_TYPE|x11|
Extensions (2)

Extension|Author (truncated)|Version
---|---|---
cpptools|ms-|1.2.2
material-theme|zhu|3.9.15

(3 theme extensions excluded)

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30256636
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
dockersubset:30270708
vspre833:30267464

Replacing the literals with \x encoded C++ characters allows me to continue to compile, but this is not an issue on Windows or in Visual Studio (not Code) as the characters remain ASCII Latin1 encoded as they should.
bool CssParser::IsEscaped()
{
// @reference [http://www.w3.org/TR/CSS1#appendix-b]
// unicode		\[0-9a-f]{1,4}
// escape		{unicode}|\[ -~\xa1-\xff]
return (Is('\\') && (IsHex(1) || IsPrintable(1) || IsRange(1,'\xa1','\xff')));

}

VS Code supports a wide range of file encodings. You can see the full list when you click on the lower right status bar where the encoding is shown and then choose to either reopen the file with a specific encoding or save the file with a specific encoding:

There are two options how to configure the encoding for files
Configure the encoding as a setting for all files or files of specific type
We provide a files.encoding setting that you can use to set an encoding for all files. You can also configure this encoding for specific file types, e.g. like this:
"[markdown]": {
    "files.encoding": "utf8"
}

Configure VS Code to automatically detect the encoding when opening files
We provide a files.autoGuessEncoding setting that you can enable to let VS Code detect the encoding of every file automatically. Note that this approach is known to not be accurate in all cases. This guessing of encoding is rather a heuristic that can produce wrong results (that is also why this setting is not enabled by default).
Please also check out issues that are already reported with the files-encoding label: https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afile-encoding

Thanks for looking into it, that's great that its configurable.
I guess a reasonable argument could be made that the default encoding for .cpp .hpp .c .h files should not be UTF-8 though ?
And also, why was a file that only has high ASCII bytes (\xa1,\xff) auto detected as UTF-8 and not Windows 1250 (Latin1)  ??

That wasn't a question.  I was politely pointing out an obvious bug.  C++ source files are not UTF-8, ill spell it out.


Support affinities for scan jobs

Hello! 👋
I would like to allow node-level jobs to run on any node with taints, except some. Currently, a config with the exhaustive list of acceptable taints is required, and every time a new taint is added to the cluster, it also needs to be added to the scan job tolerations:
nodeCollector.excludeNodes: type=virtual-kubelet
scanJob.tolerations: '[ many many many taints ]'

Ideally, I would like to tolerate all taints, but exclude some nodes with a node anti-affinity instead:
nodeCollector.excludeNodes: type=virtual-kubelet
scanJob.affinity: '{"nodeAffinity":{"requiredDuringSchedulingIgnoredDuringExecution":{"nodeSelectorTerms":[{"matchExpressions":[{"key":"virtual-kubelet.io/provider","operator":"DoesNotExist"}]}]}}}'
scanJob.tolerations: '[{"operator":"Exists"}]'

A scanJob.affinity option would be nice for this purpose.
Please let me know if there is already a way to achieve that or if I am missing something.

@maxbrunet sound a vital config for your use-case contribution are welcome if you have time.

In the implementation should the Linux node-affinity just become the default value of scanJob.affinity which that means it could be overwritten? I guess this default would be set from the Helm chart? Or should a strategic merge happen with scanJob.affinity? The later might not be as obvious to the user about what the effects are since it involves lists
https://github.com/aquasecurity/trivy-operator/blob/29b5c8347c79bc02ac189a9e1c84966dc20988df/pkg/trivyoperator/config.go#L519-L520
I will see if I can find the time.


[BUG] Could not resolve dependencies

Have tried to build the plugin! But, only this comes:

Could not resolve dependencies for project xyz.geik.farmer:Farmer:jar:v6-b005: The following artifacts could not be resolved: bukkit.org:craftbukkit:jar:1.7.9, spigotmc.org:spigot-1.9.2:jar:1.9.2, spigotmc.org:spigot-1.9.4:jar:1.9.4, spigotmc.org:spigot-1.12:jar:1.12, spigotmc.org:spigot-1.10:jar:1.10, spigotmc.org:spigot-1.11:jar:1.11, spigotmc.org:spigot-1.9:jar:1.9, spigotmc.org:spigot-1.8:jar:1.8, spigotmc.org:spigot.1.8.3:jar:1.8.3, spigotmc.org:spigot.1.8.4:jar:1.8.4, spigotmc.org:spigot.1.8.6:jar:1.8.6, spigotmc.org:spigot.1.8.8:jar:1.8.8, spigotmc.org:spigot-1649:jar:1.7.10: Could not find artifact bukkit.org:craftbukkit:jar:1.7.9 at specified path /root/.m2/repository/com/wasteofplastic/askyblock/<IP_ADDRESS>/lib/craftbukkit-1.7.9-R0.3-20140705.002733-4.jar

Can you try develop branch

Can you try to compile develop branch

Have tried with both branches

Can you try to compile develop branch

Have tried with both branches

How you try to compile the plugin

Can you try to compile develop branch

Have tried with both branches

How you try to compile the plugin

With the main branch
git init
git pull https://github.com/Geik-xyz/Farmer-v6.git
mvn package

With the develope branch
git init
git remote add origin https://github.com/Geik-xyz/Farmer-v6.git
git pull origin develope
mvn package

Can you try to use commands below.
One of them should fix your issue.

mvn compile
mvn test-compile
maven install

mvn package tries to package everything together. But you should download dependencies first to use this command. One of the 3 command should download the requirements of project.

Can you try to use commands below. One of them should fix your issue.
1. mvn compile

2. mvn test-compile

3. maven install

mvn package tries to package everything together. But you should download dependencies first to use this command. One of the 3 command should download the requirements of project.

None of them work

Run mvn dependency:copy-dependencies, to download all your dependencies and save them in the target/dependency folder.

Run mvn dependency:copy-dependencies, to download all your dependencies and save them in the target/dependency folder.

Also not

Then please use intellij idea to compile

Then please use intellij idea to compile

Habe es in einer IDE versucht! nun kommt ein anderer Fehler:

Could not resolve dependencies for project xyz.geik.farmer:Farmer:jar:v6-b100: Failed to collect dependencies at com.github.Geik-xyz:GLib:jar:cd0ced12e5 -> eu.okaeri:okaeri-configs-yaml-bukkit:jar:4.0.4: Failed to read artifact descriptor for eu.okaeri:okaeri-configs-yaml-bukkit:jar:4.0.4: The following artifacts could not be resolved: eu.okaeri:okaeri-configs-yaml-bukkit:pom:4.0.4 (absent): Could not transfer artifact eu.okaeri:okaeri-configs-yaml-bukkit:pom:4.0.4 from/to okaeri-repo (https://storehouse.okaeri.eu/repository/maven-public/)

Then please use intellij idea to compile

I tried it in an IDE! now I get another error:

Could not resolve dependencies for project xyz.geik.farmer:Farmer:jar:v6-b100: Failed to collect dependencies at com.github.Geik-xyz:GLib:jar:cd0ced12e5 -> eu.okaeri:okaeri-configs-yaml-bukkit:jar:4.0.4: Failed to read artifact descriptor for eu.okaeri:okaeri-configs-yaml-bukkit:jar:4.0.4: The following artifacts could not be resolved: eu.okaeri:okaeri-configs-yaml-bukkit:pom:4.0.4 (absent): Could not transfer artifact eu.okaeri:okaeri-configs-yaml-bukkit:pom:4.0.4 from/to okaeri-repo (https://storehouse.okaeri.eu/repository/maven-public/)

Then please use intellij idea to compile

I tried it in an IDE! Now I get another error:

Could not resolve dependencies for project xyz.geik.farmer:Farmer:jar:v6-b100: Failed to collect dependencies at com.github.Geik-xyz:GLib:jar:cd0ced12e5 -> eu.okaeri:okaeri-configs-yaml-bukkit:jar:4.0.4: Failed to read artifact descriptor for eu.okaeri:okaeri-configs-yaml-bukkit:jar:4.0.4: The following artifacts could not be resolved: eu.okaeri:okaeri-configs-yaml-bukkit:pom:4.0.4 (absent): Could not transfer artifact eu.okaeri:okaeri-configs-yaml-bukkit:pom:4.0.4 from/to okaeri-repo (https://storehouse.okaeri.eu/repository/maven-public/)

@poyrazinan

@poyrazinan
WHY CLOSED?


Missing "zone" variable in variables.tf

Following the Jump Start Solution sample using the Terraform CLI, I got a warning regarding a missing "zone" variable. I've checked variables.tf and indeed it is not present there.
This variable (zone) is indicated to be added to terraform.tfvars in the sample steps, and the warning indicates that it can see it but it cannot use it because it does not override an existing variable, and then suggests adding the variable to variables.tf. I did so on the console and the warning was removed.
I apologize for not having the exact warning message, after fixing I closed the broswer and I cannot see it again.

Same issue. Here's the error:
│ Warning: Value for undeclared variable
│
│ The root module does not declare a variable named "zone" but a value was found in file "terraform.tfvars". If you meant to use this value, add a "variable" block to the configuration.
│
│ To silence these warnings, use TF_VAR_... environment variables to provide certain "global" settings to all configurations in your organization. To reduce the verbosity of these warnings, use the
│ -compact-warnings option.

So remove or comment out the zones section in the terraform.tfvars file.
# Google Cloud zone where you want to deploy the solution
# Example: us-central1-a
# zone = "us-central1-a"

Note to maintainers
The Jump Start Solution: Dynamic web application with JavaScript tutorial prompts the user to add a zone to the terraform.tfvars.


Node Structure improvement

By node based structures, I mean Linkedlists and trees
as of this issue, trees has not been implemented but as decided earlier, it was going to be designed similar to linkedlists

Taking an example using ARgorithmToolkit.linkedlist.LinkedListNode and ARgorithmToolkit.linkedlist.LinkedList
We use LinkedListNode which gives us the functionality of the linkedlist and tracks the internal functions of the linkedlist such as change in it's values and change in it's pointers. The LinkedList class just acts as a container for nodes so we can track which node is head in a linkedlist. This works pretty well for linkedlist operations as we are able to keep track of linkedlist manipulations.
>>> from ARgorithmToolkit import StateSet, LinkedListNode , LinkedList

>>> algo = StateSet()
>>> llist = LinkedList("list" , algo)
>>> llist.head = LinkedListNode(algo,1)
>>> llist.head.next = LinkedListNode(algo,2)

>>> temp = llist.head
>>> while not temp is None:
>>> 	print(temp)
>>> 	temp = temp.next

>>> for x in algo.states:
>>>		print(x)
{'state_type': 'll_declare', 'state_def': {'id': '140471461519440', 'variable_name': 'list', 'head': 'none'}, 'comments': ''}
{'state_type': 'llnode_declare', 'state_def': {'id': '140471461516560', 'variable_name': '140471461516560', 'value': 1, 'next': 'none'}, 'comments': ''}
{'state_type': 'll_head', 'state_def': {'id': '140471461519440', 'variable_name': 'list', 'head': '140471461516560', 'last_head': 'none'}, 'comments': 'head pointer shifts'}
{'state_type': 'llnode_declare', 'state_def': {'id': '140471461518608', 'variable_name': '140471461518608', 'value': 2, 'next': 'none'}, 'comments': ''}
{'state_type': 'llnode_next', 'state_def': {'id': '140471461516560', 'variable_name': '140471461516560', 'value': 1, 'next': '140471461518608', 'last_next': 'none'}, 'comments': 'next pointer updated'}

The states are generated correctly and show the creation of linkedlist and how the head pointer (attribute of LinkedList) and next pointer (attribute of LinkedListNode) behave. But it does not track the access of linkedlist node and the behavior of temp. Which is important to explaining the operations of linkedlist and other node based data structures.
Possible Solution
Making the LinkedListNode callable by using the __call__  function.
Instead of having a LinkedList class which is used to hold the value of head, we have a LinkedListRef class which can store "named pointers" to a particular node. By calling the LinkedListNode object with a name we can create LinkedListRef   which would work somewhat like this
head = None
temp = None
for i in range(0,10):
    if head is None:
		head = LinkedListNode(algo,i)("head")
        temp = head("temp")
   	else:
        temp.next = LinkedListNode(algo,i)
        temp = temp.next()

temp = head
while temp is not None:
    print(temp)
    temp = temp.next()

Not thought over it that much but I think its more convenient than the whole LinkedListNode and LinkedList class design currently deployed

@yatharthmathur
Can be solved with @property decorator (which I have no idea why we didnt use in the first place). This should remove the need for the separate LinkedList class.


update development doc and regenerate clustermanagementaddons crd

Updates:

added steps for generating CRDs & generating deepcopy.zz
updated docker image to use fedora:32 to support golang 1.14.4+
updated clustermanagementaddon's printcolumn by regenerating

/approve
on @qiujian16 for lgtm

/lgtm
thanks! @hanqiuzh


Be on brand

Rebrand this as "radiospectra", as a place to keep the current functionality while we develop more general tools in core sunpy / other packages.
Also need to move docs.

We also need:

[ ] release package
[ ] brand sphinx

I mean we did this?


Speed up rainforests prediction

Add an option to speed up rainforests prediction.
The improved efficiency is achieved by observing that for sets of grid points having very similar values for their features, the features will be binned by LightGBM in the same way for each point, and therefore the predicted value of each point will be the same. Thus we only need to predict once for the whole set of points. This yields a reduction of around 20-40% in processing time for gridded forecasts (depending on file).
Description
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

This is still current.

Scheduled tests are failing with the latest env. We should pin the treelite package in latest.yml to resolve.

Thanks for reviewing @benowen-bom and @bomRob, all changes are merged now.

I realised after merging that the fix to envs/latest.yml to pin the treelite package wasn't included here. I'll add a PR tomorrow to enact this change.


Update the manifests into 0.15.0 and refactor the test scripts

Fixes #
Proposed Changes

Update the manifests of serving and eventing into 0.15.0.
Refactor the test scripts for serving and eventing operators' consolidation.
Update the test cases.
Remove the redundant resources in knative eventing 0.14.

/hold
I am waiting for replies from the community about how we proceed the 0.15 release for operator.

/hold cancel

ready for review and even merge, since we will release 0.15 in a week for operator, with what features we have now.


text-splitter: support for trust_remote_code and not loading model in SentenceTransformersTokenTextSplitter

Thank you for contributing to LangChain!

Description: Trust remote code parameter was not there due to which we could not load external models, also there is no need to load the model and increase the memory footprint.

Dependencies: Transformers

Twitter handle: @anchit2000

[ ] Add tests and docs: If you're adding a new integration, please include

a test for the integration, preferably unit tests that do not rely on network access,
an example notebook showing its use. It lives in docs/docs/integrations directory.

[ ] Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

Additional guidelines:

Make sure optional dependencies are imported within a function.
Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
Most PRs should not touch more than one package.
Changes should be backwards compatible.
If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.

This is important for not downloading and loading the model when it’s not needed while tokenising.

Also, we can’t use models on the hub where trust remote code parameter is required.


Add NetBSD install instructions

I've rewritten the jless website and updated the installation section, which now includes these instructions. (Code for the website is on the website branch.)

Thanks!


variable is not defined, if created in window object

(function(){
window.myvar = true;
}();
alert(myvar); //jshint -> myvar is not defined
jshint  should understand that "myvar" is a global variable.

You would have to know the environment global name and work out/know if that global is being shadowed outside of the current class.

ok, understand. Are there any solution or workaround for this problem without a new implementation in jshint. I could define each of these variables in the "globals" object in jshint settings, but I have about 100 global variables in the window object. Any idea?

You could define a single global namespace object:
window.myApp = {};

and attach your "global" variables as properties of that object:
myApp.myvar = true;

This solve your immediate problem with configuring JSHint:
{ "globals": { "myApp": true } }

...but I wouldn't recommend changing your code just to satisfy JSHint. This approach is widely regarded as a best practice for browser code (regardless of whether/how you lint your code) because it limits the amount of "pollution" in the global scope (helping avoid accidental collisions with third-party code), and it makes your code a little easier to read (references to shared global values are visually distinct from locally-scoped variables) and to debug (compare Object.keys(myApp) to Object.keys(window)).
Although this avoids the "problem" of declaring all your globals in your JSHint configuration, it also makes it impossible to statically detect incorrect references. If you had defined globals as in your original example and configured JSHint with all 100 of them, then JSHint would be able to correctly identify the typo here:
console.log(myVar); // note the incorrect capitalization

but with the approach I've suggested, the equivalent code will pass lint (despite still being a typo):
console.log(myApp.myVar);

The long-term solution is to consider using a formal module format to manage references between files explicitly; the most common options are AMD, CommonJS, and ES6 modules. That will be a lot of work, so my initial recommendation stands as a short-term fix. But when you have time to research those formats, I think you'll find the benefits to formal dependency management make the required refactoring worthwhile in the long run.


<EMAIL_ADDRESS>return false

If quoted, it may contain Space, Horizontal Tab (HT), any ASCII graphic except Backslash and Quote and a quoted-pair consisting of a Backslash followed by HT, Space or any ASCII graphic; it may also be split between lines anywhere that HT or Space appears. In contrast to unquoted local-parts, the addresses<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>are allowed.

https://en.wikipedia.org/wiki/Email_address

I rather to be "false" than "true" because the Gmail email validator disallow you to set dots back to back


Add list of supported social networks in README

Don't know whether this is actually needed but I feel it is better to show the list of social networks in README so that users can know which sites are included in the project.

That does sound like a good idea, but typing all of the sites in the readme again seems very error prone. It is not very possible to audit as sites are added and subtracted.
What would be a good way to deal with this?  Add a script that would populate the list from data in the JSON?  It would be nice to have a file format for the site data which would also be easy for people to read.

Hi @hoadlck, I did not add those sites to the list manually.  Before sending the PR, I wrote a small piece of code that reads the data.json file and performs some string operations to generate a .txt file consisting of the site name and url in Markdown syntax.
The contents of the .txt file where then copy-pasted into this PR. I'm more comfortable with JavaScript and hence I wrote a JS code. But if we are planning to maintain the script as well, I'll rewrite it in Python if needed :smile:
This is the code that I wrote:
const fs = require('fs');
const siteInfo = require('./data.json');
const sites = Object.keys(siteInfo).sort();
const stream = fs.createWriteStream("sites.txt", { flags:'a' });

sites.forEach(function(site, index) {
    let url = siteInfo[site].url;
    let slashPosition = getSlashPosition(url);
    url = slashPosition ? url.slice(0, slashPosition) : url;
    url = url.replace('{}', 'www');
    stream.write(`${index+1}. [${site}](${url})\n`);
});

function getSlashPosition(url) {
    let position = 3;
    for (i=0; i<url.length; i++) {
        if (url.charAt(i) === '/') {
            if (!--position) {
                return i;
            }
        }
    }
    return false;
}

Actually, as part of other development, I added data to the JSON file which now explicitly says what the main URL entry point is.  I wanted this to be available for the csv report, and I thought it would be useful for this report as well.
If you look at the tip of master, you will see that the JSON file now has a "urlMain" attribute.  It turns out that it is not always possible to derive the main social media site based on the URL that is used for the user.  For example, Blogger uses blogger.com for the entry point, but the user blogs are hosted on blogspot.com.
So, now it is much simpler to generate the list.
Do you think it would be better to have a sites.md file or have the new Python script find the right place in the readme.md and insert it there?

The addition of urlMain does make things a lot simpler now. I'd suggest maintaining a separate sites.md file and not populate the readme with the sites list.
Let the readme have instructions, usage and other stuff along with a link to the sites.md file.
Also, so as to ensure that the list of sites are updated we have to enforce a contribution guideline stating that everytime a support for new site is added, the site has to be added to the list in site.md as well.
What do you think about this? Also, is there a way of automatically updating the site.md every time a new site is added to data.json? I personally feel, enforcing the guideline would be enough, it will do the job and it's easier than automating (if automation is possible).

I think we can integrate this script into a script that runs during the release process.  This way any check of the tests will result in an up to date sites.md file.  Any developer that contributes should run the tests anyway, so it will always be up to date.
I am not quite sure what form the tests will take, but if you create the generation script, someone can integrate it into the larger process when that is defined.

Have added a script for listing out all the sites in data.json to sites.md file. Contributors will have to run this file manually before sending a PR until we integrate it with the release process. I've run the script to include all sites currently in data.json.
Let me know if any changes required. Thank you.

Thanks for this.
I did update the script to use with-as structure for reading/writing the files.  I also added the number of supported sites to the title.


The do_queue deprecation in PennyLane breaks Catalyst tests

Looks like the do_queue deprecation in PennyLane led to failed tests in Catalyst. The error messages using PennyLane 0.31.0-dev:
warnings.warn(do_queue_deprecation_warning, UserWarning)
jax._src.traceback_util.UnfilteredStackTrace: UserWarning: The do_queue keyword argument is deprecated. Instead of setting it to False, use qml.queuing.QueuingManager.stop_recording()

Just a note, the tests that are failing are failing because we explicitly check that no warnings are issued when re-compilation is unnecessary via type promotion. If recompilation happens, a warning is issued. We still need to make sure to remove our dependency on the do_queue=False to avoid the future deprecation, but the tests can succeed by making the filter more specific towards the recompilation warning.

@erick-xanadu yes, indeed! Fixed this in the PR following the recommended way.


an error got when building

I got an error when using this plugin

node v6.10.1
webpack 2.6.1

@zzzgit seems your use babel-loader and something don't compile to ES5, can your give more information about version plugin and example code from 5.js?

@zzzgit can u try using the ecma option? ex:
new UglifyJsPlugin ({ uglifyjsOptions: { ecma: 8 } })

Also, make sure you're not using a module transforn babel plugin... For ex... set  modules: false if you're using babel-preset-es2015 or babel-preset-env.

@zzzgit Ensure to either transpile your JS to ES5 when using <= v0.4.6 or if you use >= v1.0.0-beta.0 see @hulkish's comment and feel free to reopen if still regressions :)

update to v1.0.0-beta.0, and then { uglifyjsOptions: { ecma: 8 } }, now it works


Remove dead ttnn sweeps docs code from docs build

cc: @dimitri-tenstorrent
Context: This is a sensitive part of the initial docs build. We don't publish sweeps results anymore to docs, so we can get rid of it.

this has been causing recent build failures on main.

@tt-rkim What is the folder where this exists?
This one https://github.com/tenstorrent/tt-metal/tree/main/docs/source/ttnn/ttnn_sweeps

This is automatically generated during the build via tests/ttnn/sweep_tests/build_rst_sweep_results.py
The TTNN team has agreed to get rid of it cc: @ntarafdar


How to use the SS7 module

Hi @SigPloiter
Thank you for the code provided, I have installed it correctly，
Can you explain this in detail? Can you provide a detailed guide? thanks
"In order to attach the SS7 on real life target you should have an access to the SS7 network. It is often provided by VoIP providers, SMS providers, HLR lookup web application providers, you just need to dig deeper to find a suitable provider"

Hello , thanks for installing the tool. As mentioned to Be able to work in
a real environment you need to get SS7 access. Other than that the server
side code provided could be used for simulation for education and hands on
On Sunday, 23 September 2018, xiaoxie1979<EMAIL_ADDRESS>wrote:

Hi @SigPloiter https://github.com/SigPloiter
Thank you for the code provided, I have installed it correctly，
Can you explain this in detail? Can you provide a detailed guide? thanks
"In order to attach the SS7 on real life target you should have an access
to the SS7 network. It is often provided by VoIP providers, SMS providers,
HLR lookup web application providers, you just need to dig deeper to find a
suitable provider"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SigPloiter/SigPloit/issues/143, or mute the thread
https://github.com/notifications/unsubscribe-auth/AXXuvxcN4ksg3eGi52tk4ONu44g2LwbHks5udx8VgaJpZM4W1kcq
.


Awesome version on mac

When I use c++11 features, like ‘auto’, when I type ':w' on the vim, it consistently reports an warning
auto' type specifier is a C++11 extension [-        Wc++11-extensions]
Do you have ways to fix that? Thanks!  (BTW, I already specify alias on the bashrc file.)

Please see the configuration options of https://github.com/vim-syntastic/syntastic and my_configs.vim 👍


package changes

Description

A clear and concise summary of the change and which issue (if any) it fixes. Should also include relevant motivation and context.
Resolved or fixed issue:
Affirmation

[ ] My code follows the CONTRIBUTING.md guidelines

Checkmarx One – Scan Summary & Details – a56d8881-3686-4cdb-9fba-cd6f2c98349a
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

Cxa45b0853-bee2
Npm-momnet-2.29.1
Vulnerable Package

Cxfd197ca1-b64b
Npm-momnet-2.29.1
Vulnerable Package

Cx743605c8-a95e
Npm-momnet-2.29.1
Vulnerable Package


Reference typo fix

Correct me if I'm wrong and that's something about RO-crates, but there's a typo in the preparation_method reference.

cc: @sherwoodf


updated Readme tag

Fixes
Checklist

[x] I have made a material change to the repo (functionality, testing, spelling, grammar)
[ ] I have read the [Contribution Guide] and my PR follows them.
[ ] I updated my branch with the master branch.
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation about the functionality in the appropriate .md file
[ ] I have added in line documentation to the code I modified

Short description of what this PR does:

If you have questions, please send an email to Sendgrid, or file a Github Issue in this repository.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @af4ro,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Acknowledge community contribution in the changelog

Follow up after #4982.
Thank you, @phoebusm!

@LarryOsterman, we have it captured here - #4668 - hopefully we can get to it during MQ.


cleanup(storage): dedup MinimalIamCredentials

Use the implementation in google/cloud/internal/.
Part of the work for #9659

This change is

/gcbrun


lib32-* packages

Currently building lib32-* packages fails since dependency installation is run with --noconfirm preventing user from choosing to replace gcc with gcc-multilib interactively.
One solution would be to construct a chroot image with group multilib-devel preinstalled but since we don't want to force users to use the multilib repo this would have to be a flag ie. -m for multilib or more generally -p <packages> for including additional packages when building the root image.

How about:

Check if multilib is configured with pacconf, and if yes, install the gcc-multilib package
Add a note to aurbuild(1) on how to install packages to the chroot

I believe the best way to go about this would be to get upstream to add a possibility of overriding the default flags in makechrootpkg since this will come up every time there's a package conflict, although I'm not sure if requiring user input during the build process is desirable

Added a note to aurbuild(1). Upstream progress is tracked in #20.


New version: mesonbuild.meson version 0.61.3

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 410
Microsoft Reviewers: Open in CodeFlow

/azp run


The generalize() API of Python SDK does not work for Windows VM

Hi
The Azure Python SDK generalize() API for VirtualMachineOperations in Compute Client does not "sysprep" the VM. Instead, one must leverage the CustomerScriptsExtension to perform Sysprep on the VM before capturing its image. Curious what is the intended purpose of generalize API, and why it does not result in Sysprep of Windows VM?
Thanks

@lmazuel can you please help address this item?

Duplicate of https://github.com/Azure-Samples/virtual-machines-python-manage/issues/18
This is a RestAPI question and has nothing to do with Python:

We should raise to Compute team
@yugangw-msft might know part of his work in the CLI team on Compute

Closing this issue as a duplicate.


Changes to C++ DQN

Hi @Asugawara, I'm opening a PR to track some changes to C++ DQN in order to try to explain what is happening with catch, and to add a few things.

@googlebot I fixed it!
:)

@googlebot I fixed it!
Again! :)

☹ Sorry, but only Googlers may change the label cla: yes.

@googlebot I fixed it!

@googlebot I signed it!


tests: tests for option settings are not comprehensive

Problem: tests for option settings are not comprehensive
Solution: add help-based black box testing
This PR is split part of #15835.

thanks, that is much better to review!


Undefined method visit_d for an "optional" validation

From @chikamichi on December 15, 2016 11:5
Hi,
Using dry-types 0.9.3 through dry-validation, this simple rule:
optional('draft').maybe(:str?)

triggers:
/var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:15:in `visit': undefined method `visit_d' for #<Dry::Types::Compiler:0x000000055df778 @registry=Dry:
:Types> (NoMethodError)
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:35:in `block in visit_sum'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:35:in `map'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:35:in `visit_sum'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:15:in `visit'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:80:in `block in merge_with'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:80:in `map'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:80:in `merge_with'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:52:in `visit_hash'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:28:in `visit_type'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:15:in `visit'
        from /var/lib/gems/2.2.0/gems/dry-types-0.9.3/lib/dry/types/compiler.rb:11:in `call'
        from /var/lib/gems/2.2.0/gems/dry-validation-0.10.4/lib/dry/validation/input_processor_compiler.rb:16:in `call'
        from /var/lib/gems/2.2.0/gems/dry-validation-0.10.4/lib/dry/validation/schema/deprecated.rb:14:in `input_processor'
        from /var/lib/gems/2.2.0/gems/dry-validation-0.10.4/lib/dry/validation/schema/class_interface.rb:163:in `default_options'
        from /var/lib/gems/2.2.0/gems/dry-validation-0.10.4/lib/dry/validation/schema/class_interface.rb:34:in `new'
        from /var/lib/gems/2.2.0/gems/dry-validation-0.10.4/lib/dry/validation.rb:26:in `Schema'

Nothing fancy about the way I use dry-validation here. required works just fine, the error only gets triggered by optional with a block, therefore I suspect either visit_sum to be doing something wrong, or what's fed to visit_sum to be incorrect.
Copied from original issue: dry-rb/dry-types#172

From @chikamichi on December 16, 2016 12:24
I've found that the error only occurs when activating dry-validation's sanitizer (config.input_processor = :sanitizer). Let me know if you'd like me to report the bug on the dry-validation issue tracker instead.

From @flash-gordon on February 1, 2018 23:17
I'll close this issue since it's on the dry-v side mostly. We are working on dry-validation 1.0, it's going to take a while but we hope to push a beta in two to three months (optimistic mode on). It's probably a good idea to check if this will work fine there so pls bring this issue to dry-validation's repo.

Can confirm the issue. Thanks!


SSL verification is Failed - [BRIEF DESCRIPTION]

App Id: d2fmotv2l2kmz3
Region: us-east-2
Step: SSL verification
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.
Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Hello @yassati,
Could you try to follow the guide here as see if it helps: https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html#custom-domain-troubleshoot-guide. Linking to a similar issue's resolution: https://github.com/aws-amplify/amplify-console/issues/15#issuecomment-515232292


Pagination for UsageDetails List api requires parsing Response().NextLink to get the skiptoken

Feature Request

Related to https://github.com/Azure/azure-sdk-for-go/issues/2399

@ramaganesan-rg Please confirm the swagger was fixed for the missing skiptokenver and id query params in the swagger for manual paging.
Azure/azure-rest-api-specs#11351


Automated Database Dumps

It would be nice if there was a way for the MySQL database dumps to be automated, rather than relying on Undo to make them.

Create a new dump on user request (with ratelimit?), or create a new dump nightly/weekly and allow anyone to download?
Host on AWS S3, github, or other?
Open to all, or core only?

Need to do the math on bandwidth cost - that'd determine how restrictive it is, if I'm hosting it on S3. Of course, folks can always email it to each other or do whatever they want with it, so it'd always be 'open to all' in some respects.

@Undo1 a quick calculation using the calculator, assuming 50 downloads of a 500mb database per month, results in an estimated extra cost of 50 cents per month. I'm pretty sure that the database is much smaller than that, so the cost would probably be quite a bit less.

We could also think of using torrent for the database download. This allows members of the community  to help seeding by just keeping their computer on, and because of the p2p nature of torrents, it would mean less bandwidth usage for the main server (we could even impose a max upload speed server side on it, and unlike most http servers, this max upload speed is for all connections together.)

If we write a script to generate a dump, then we can have a route that calls said script and emails the requesting user when it's done with a link to the dump. We can also tie that into a Backup model so that we only generate a dump a day at maximum.

Alternatively @ArtOfCode-, just generate it every day (cheap) and overwrite it in S3 (free). Doesn't need to be user-triggered at all, IMO.
Heck, I already do it with nightly backups, just need to get redaction working for this one.

996a6abf6a5cfa761619afe4e91a6c7ab2b02666; b64fc6cbedb7b27444f77782c563e72e91dc9d94

Subtle hint? ;)

I'd do it myself, but I'm not the one with server & S3 access ;)

Completed


Please let me know solution for this "Android resource linking failed"

hi i am using ionic 4 and before adding this plugin my app is build fine but after adding this plugin and re ad the platform and try to build then i got this error
Execution failed for task ':app:processDebugResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > Android resource linking failed

can someone know this issue how to fix

Hi @mehraj786 ,
Share full details of error.
Thanks

Hi @mehraj786 ,
Intall jetifier and run "npx jetifier"


pyrealsense2_net module not found when using pypi package on pc

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 18

Kernel Version (Linux Only)
5.4.0-91-generic

Platform
PC

SDK Version
2.50.0

Language
python

Segment
Robot

Issue Description
I'm trying to run the net_viewer example but get an error when it tries to import pyrealsense2_net module.
ModuleNotFoundError: No module named 'pyrealsense2_net'
These are the versions That I have installed:

pyrealsense2 version(from pypi): <IP_ADDRESS>12
librealsense version (as part of ros melodic): 2.50.0-1bionic.20211115.141014

Any ideas what I could be doing wrong?

Hi @elishafer  There is a previous report at https://github.com/IntelRealSense/librealsense/issues/9946 of the ModuleNotFoundError: No module named 'pyrealsense2_net' occurring when using the rs_viewer.py example program.
The main list of examples in the Python wrapper documentation provides the description "Shows how to connect to rs-server over network" for the rs_viewer.py example.
You may have already come across rs_server if you have read Intel's white-paper document on the subject of open-source ethernet networking.
https://dev.intelrealsense.com/docs/open-source-ethernet-networking-for-intel-realsense-depth-cameras
If you built librealsense and the RealSense ROS wrapper together from packages with the wrapper's Method 1 instructions then librealsense would not have been built with networking support included.  This support can be included in the SDK by building it from source with CMake with the build flag -DBUILD_NETWORK_DEVICE=ON included in the CMake build instruction, as described in https://github.com/IntelRealSense/librealsense/issues/7606#issuecomment-714169261
Including the -DBUILD_NETWORK_DEVICE=ON build flag in the CMake build instruction when building librealsense from source code causes the 'realsense2-net' module and the 'rs-server' tool to be built.

is the wrapper supported for python 3.10?  cant find the module on pip? is there clear instructions on building from source if that is the only option?
on windows 10

Hi @Niko-La  At the time of writing this, the most recent Python version that pip install of pyrealsense2 supports is Python 3.9.  Further information about this can be found at https://github.com/IntelRealSense/librealsense/issues/10057
Users of newer Python versions than 3.9 should build the wrapper from source code.  The simplest approach to buiding from source would be to build librealsense and the Python wrapper together at the same time using the BUILD_PYTHON_BINDINGS CMake build flag with CMake's visual GUI. There is a clearly written tutorial for doing so on Windows 10 at the link below.
https://rahulvishwakarma.wordpress.com/2019/08/17/realsense-435i-depth-rgb-multi-camera-setup-and-opencv-python-wrapper-intel-realsense-sdk-2-0-compiled-from-source-on-win10/
This guide is based on Intel's official documentation for building librealsense on Windows from source code:
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_windows.md
The alternative approach is to build the wrapper from source code on its own after librealsense has already been installed.  The guide at https://github.com/IntelRealSense/librealsense/issues/6964#issuecomment-665650908 may be useful for doing this on a PC.
If you decide to revert to Python 3.9 so that you can use pip install, a guide for a pip install on Windows that I wrote in the past is at https://github.com/IntelRealSense/librealsense/issues/6402#issuecomment-629763906

Hi @Niko-La   Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


The SystemBackdrop of the window will turn solid black if it is none, and will not respond to theme changes

The SystemBackdrop of the window will turn solid black if it is none, and will not respond to theme changes

this is normal!
if you want to use Backdrop (no matter it is None or Mica or Acrylic...) you should remove any background from your page or window. that theme changes does not work as expected!
If you want theme changes to work well, you should consider a background for your window or page.


Removed some unused methods in TM, deprecated TO client methods

What does this PR (Pull Request) do?
Removes some unused methods in TM, removes some deprecated TO Go client methods, changed some TO Go client methods to use DeliveryServiceNullable structs instead of the non-nullable struct, and marked the non-nullable DeliveryService structs as deprecated.

[x] This PR is related to #2546

Which Traffic Control components are affected by this PR?

CDN in a Box
Documentation
Grove
Traffic Control Client (Go)
Traffic Monitor

What is the best way to verify this PR?
Run the Go unit tests, TO API tests (v1 - v3), make sure they all pass. Rebuild RPMs and CIAB, verify that the readiness container exits successfully.
The following criteria are ALL met by this PR

[x] This PR adjusts tests
[x] No doc changes necessary
[x] This PR includes an update to CHANGELOG.md
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Looks great! code looks good, unit tests pass, API tests v1-v3 all pass, RPMs build, CIAB builds and runs successfully, and the readiness container exits successfully. nice work!


bugfix: failed to fetch upstream, apisix may be starting.

todo: add a test case.
it is not easy to add a test case for this bug. added comment in source code.
we can fix it later when we found a good way.
fix: https://github.com/apache/incubator-apisix/issues/1688

@membphis please rebase master and add test cases.

we can close this PR, it has been fixed in the master branch.
https://github.com/apache/incubator-apisix/blob/master/apisix/init.lua#L374-L378
    if up_id then
        local upstreams = core.config.fetch_created_obj("/upstreams")
        if upstreams then
            local upstream = upstreams:get(tostring(up_id))
            if not upstream then
                core.log.error("failed to find upstream by id: " .. up_id)
                return core.response.exit(500)
            end


Add iran flag

@amirghazi87 I made a review into your code here.
Sorry for not metion you before

@amirghazi87 I made a review into your code here.
Sorry for not mention you before

I fix conflict but I can't see the review

@amirghazi87 following the review:

@amirghazi87 following the review:

Oh, I'm sorry, i think now is correct ( when i was write that i can't test it , like now )


Revised train-test splitter to support artist conditioning and distribution matching

Fixes #24
This PR overhauls the train-test split generator in three ways:

The metadata has been de-duped at the artist id level using a nearest-neighbor search in vggish feature space.  The process is described in #24 comment thread, with a link the corresponding notebook.  The process is deterministic and easy to reproduce.
Train-test splits are now artist-conditional, and can optionally use the de-dupe index produced by (1) above.  This effectively eliminates the most obvious cases of train-test leakage by (near) duplication.
Shuffle splits are now done with rejection sampling based on a probability ratio match.  For each proposed split, the distribution of positive and negative examples for each instrument cannot deviate by more than a constant factor from the full sample.

For step (3), I have checked in a generated train-test split with tolerance of 0.875 (closer to 1 meaning a tighter match to the full distribution).  I haven't been able to improve on this yet, and we're probably hitting the limits imposed by the data (e.g. the Bach effect mentioned in #24), but I think this ratio is pretty good.
Aside from CR, what I need from @ejhumphrey and/or @simondurand is instructions for where to put the dedupe index data.  Otherwise, I think this resolves all of the major issues known in the previous train-test split logic.

Pull Request Test Coverage Report for Build 26

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.068%

Totals

Change from base Build 14:
0.0%

Covered Lines:
222

Relevant Lines:
236

💛  - Coveralls

LGTM for the most part, just a couple parts that could use a comment or two to help readability.

high-level question: how big is the "dedupe index data"? is that just the dupe_file named here that falls out of the notebook?

Yep, exactly:
-rw-rw-r--   1 bmcfee bmcfee    378583 Sep  3 15:50 openmic-20k-dedupe-artistids.csv

20001 lines (header + dedupe id for each sample key).

LGTM for the most part, just a couple parts that could use a comment or two to help readability.

I made the requested comments, and think we're good to merge.  Travis is currently failing on most platforms for reasons independent of this PR (dependency installation).

ah, okay, I wondered what the hell was going on with Travis, same thing was happening for the full label aggregation. We don't actually add any tests here, so I suppose it's fine to mail on through?
only thing that stands out now is the notebook that produced the de-duped index ... I know it's linked in a gist, that's linked in the PR ... but perhaps that's a little bit buried? maybe if we don't want to add the notebook directly to the repo, we could add the link to a description in the README.md? this is definitely non-blocking though, since we can add it anytime.

We don't actually add any tests here, so I suppose it's fine to mail on through?

:+1:

this is definitely non-blocking though, since we can add it anytime.

:+1: yeah.  I think it makes sense to have it in the repo, but it's non-blocking.  Maybe we can just have a separate folder for supplemental materials / derived data?

travis is complaining about env issues and taking forever to run, this PR is fine...


Feature Request: Integrate Intel TBB download/build into Module_ITKTBB

Currently, Module_ITKTBB is configured to support the binary distribution of TBB, however, on many HPC, they do not want to use binaries and would rather support custom compiled packages optimized for the architectures and special compilers.
Unfortunately, the current TBB source releases don't provide a canned method to compile the package and generate the required TBBConfig.cmake file.
If ITK were to switch to using this method:
https://github.com/01org/tbb/tree/tbb_2019/cmake#source-code-integration-of-intel-tbb-to-the-sub-string-finder-sample-linux-os
Then, when enabled Module_ITKBB would build TBB using the same configuration that ITK is using.

This would of course require a submodule or similar configuration so that Module_ITKBB also downloads the package first.

I was under the impression that you could download TBB sources, configure and build using CMake, and then point ITK's TBB_DIR to your custom compiled TBB. Is this not so?
Also, @blowekamp started a patch to download TBB binaries during ITK configure/build process. That might be of interest to you.

TBB_DIR to your custom compiled TBB. Is this not so?

NO!  Not even close.  TBB build system is a raw makefile, wrapped in python, with a cmake cleanup post-processing nightmare.  I have begged them to improve the processes, and have made a little progress.
see: https://github.com/BRAINSia/BRAINSTools/blob/fix-tbb-bld/SuperBuild/build_tbb.sh
for details that only works with changes that have recently been worked on, and hopefully incorporated in the next release of TBB.


major poc

Changes
Major

Migrate to separate NPM packages and publish @imtbl/sdk and @imtbl/checkout-widgets, and their workspace dependencies recursively
Checkout widgets javascript is now loaded from the @imtbl/checkout-widgets package instead of needing to be copied to the @imtbl/sdk package
Removed browser bundle being created from @imtbl/sdk (This was not being exported correctly by our sdk so it was unused unless it was consumed from a CDN rather than as an npm node_module)
All packages now create both an esm and cjs javascript output file (Checkout remains the same)

Tooling

Migrate to Pnpm from yarn
Migrate to tsup from rollup (Checkout remains the same)
Upgrade NX to support pnpm v9
Migrate release process from release-it and custom scripts to nx release
Setup changelog generation to be handled via conventional commits

Misc

Make workspace versioning explicit
Cleanup cypress from Checkout
Add missing dependencies to package.jsons that were imported from previously (pnpm will not allow importing from dependencies that aren't listed in the package's package.json, unlike yarn)
Cleanup and remove many custom scripts not needed anymore

Outcomes

Heavily improved build times for SDK (~2 m -> ~35 seconds)
Reduced overhead on executed commands (~1 s -> ~400 ms)
Automated changelog generation from PR titles
No russian doll nesting in output bundles
Each package can be consumed separately now
Much more easier to maintain processes due to clean up and removal of many custom scripts
More robust and resilient codebase/SDK
Support for conditional exports in commonjs environments

Todo

Update docs to reflect changes
Attempt to introduce breaking change updates to dependencies (ethers v5 -> ethers v6 for eg)
Setup automated conventional commit PR title comment

Have a thinking about how do we indicate alpha packages in a release.


Additional output plugin for writing to OpenTSDB using telnet mode

Hi,
This additonal output plugin enables to write from telegraf to OpenTSDB using the telnet mode.
My Unit Tests are not 100% code coverage, at the moment I will write a MOC for OpenTSDB emulation which will follows in a second pull request.
I have signed already the CLA
Thanks for pulling in advance!

This is great, thanks much @rplessl! I can tell that you read the contributing guidelines :-) :+1: :+1:
re: unit tests, I'm not sure how much work it's going to be to mock openTSDB, but have you considered trying out a docker image of openTSDB rather than mocking it? The kafka output sink utilizes that for unit testing and it simplified things enormously.

thanks for the hint for unit tests- I will also take a docker image

You can do one or the other....basically would require adding the docker image to the scipts/docker-compose.yml file, then using testutil to get the host that the docker openTSDB is at. That would also make it part of a "long" unit test suite

Hi @sparrc:
As discussed last week, I have added several unit tests using OpenTSDB a docker image.
Could you pull it?

thanks @rplessl, I'm going to try to merge this today :+1:


cleanup unused service account token secrets

When a service account token is created, but the service account update fails we need to clean up the token we created.
Also, if the update failure was a conflict, there's no reason to error because we'll get another attempt when we receive the update.
@liggitt ptal

ok to test

add to whitelist

LGTM.  @liggitt are you good with this?

I actually opened #9009 which included this and a couple other improvements, with some additional test cases

closed in favor of #9009


Lots of Questions ( Your Life's Misery Short Version)!

Nandu Presents
Lots of Questions ( Your Life's Misery Short Version)!

Chapter 1: Why Life Exists?

How do you find the phishing links?
How do you verify that a domain is used for phishing (other than actually seeing people use the links to hack into people's account.   Well you can't get this much large list of domains if you only found it that way)
What if a domain was originally used for phishing but later change it into a non dangerous website for doing good deeds. Will you then remove the domain from the list if the owner of the domain contacted you personally?
Does domains from the suspicious-list.json serve any purpose? I am pretty sure no one verifies the domain ever again after it is added to the suspicious-list.json to check wheather it surely is used for phishing. So doesn't it just serve as a safeguard for the domains in the suspicious-list.json if it is not ever moved into the main list.

Chapter 2: Why this world?

I also hate this!

Chapter 3: Who was he?

There is no restriction mentioned for submitting domains which are not used for phishing.

Chapter 4: Why me?

I don't understand what you meant by "Cause for some false positive flags ". By my 2 years of English education i think it meant that that domain was a friendly website but was accused of being a phishing website. Well if what I thought was correct, why does it still redirect me to a malware website?. If what I thought was wrong ignore the question.

Chapter 5: Why soul exist?

For people who don't know what this is this is .gitignore file. This file contains all the files and folders which will be ignored by GitHub so basically all the names of the folders and files won't be shown to you. This is used to hide .env file or config file to hide your bot token/secret, database username and password.

Chapter 1: Why Life Exists

And we should stop the @actions-user bot from steal the top contributer place from @nikolaischunk .

Forgive me for my grammar or spelling mistake!
BTW Admire my affords on styling this!
I also should get a award on best issue presented!

This is halarious!!!
Thank you for brighten my day 😂

To answer your questions (there are a lot of them)
Chapter 1

There are scanning services that check 24/7 on newly registered Domains if they could be used for phishing. There are other places where Domains are discord phishing links are being collected, so if you crosscheck them with the current list you can find matches that are not on the list yet.
Tools like https://urlscan.io/ help you do that. Other than this often Domains get reported and then collected.
If this happens the Domain Owner can reach out to me.
The purpose is, to provide a list of domains that are used for phishing in some way but not necessarily in connection with Discord. As the Repository name suggests, this is about Discord Phishing Links.

Chapter 2
Feel free to rewrite the Readme if this bothers you :)
Chapter 3
That is true, I should update the Contributing.md sometimes
Chapter 4
This domain is the cause of some false positive flags. translate this into your main language, it should make sense. (hopefully)
Chapter 5
Adding node modules is just a best practice. The other one is to ensure that if someone uses some additional npm packages to sort the package, for example, this is not pushable to the repository.
Chapter 6
True, but not sure how to do this.
Chapter 7
Very very well done Issue by you, kudos!
Love the Styling and the effort put into it!

Fair enough answers.
I will close this for now!

So long nerds!!!!!!!

So long Nerds!!


Bug: Local Option TF permissions on Azure Storage Account (State file storage)

Is there an existing issue for this?

[X] I have searched the existing issues

Infrastrcuture as Code Type? (Required)
terraform
Module Versions (Required)
ALZ PowerShell Module: x.x.x
Accelerator Bootstrap Modules: x.x.x
Terraform Starter Modules: x.x.x
Bicep Starter Modules: x.x.x
Input arguments of the ALZ-PowerShell-Module (Optional)
No response
Debug Output/Panic Output (Optional)
No response
Expected Behaviour (Required)
For the Local Option with TF, storing state in Azure, running an Apply results in the follow error:
Error: Failed to get existing workspaces: containers.Client#ListBlobs: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="AuthorizationPermissionMismatch" Message="This request is not authorized to perform this operation using this permission.\nRequestId:daf66ed3-001e-0041-4143-13c92c000000\nTime:2024-09-30T14:14:45.9666737Z"
Actual Behaviour (Required)
Default storage account behavior does not allow key/SAS only auth, and rather requires Entra auth (service principal/managed identity). I see a managed identity for "plan" and "apply" are created, but I would expect that the "apply" managed identity is then use to authenticate against the storage account.
Steps to Reproduce (Optional)
No response
Important Factoids (Optional)
No response
References (Optional)
No response

This has been resolved in https://github.com/Azure/ALZ-PowerShell-Module/releases/tag/4.0.0 via https://github.com/Azure/accelerator-bootstrap-modules/pull/43


Grunt error on lift

Hoping someone could point me in the right direction. I was farting around with updating global npm's today, and now I'm getting a grunt error when I lift my app locally:
error: ** Grunt :: An error occurred. **
error:
------------------------------------------------------------------------
Aborted due to warnings.
Loading "jst.js" tasks...ERROR
>> Error: Cannot find module 'chalk'
Warning: Task "jst:dev" not found.

This error only seems to come up in my local dev environment, as when it deploys in its future production environment on Modulus, the logs show all clear.

Looks like removing the node_modules directory, cleaning the cache, and doing a fresh npm install did the trick.


Add an example for no_longer_matching

This PR addresses the misunderstanding around the EntityStateUpdate.no_longer_matching field.
See #1211.

@alexander-yevsyukov, PTAL.


Add support for the builder pattern

WinRT properties that are writable should return a reference to self (D const&) to allow chaining calls to various properties.

Shouldn't that be a mutable reference then?

No, the reference itself is not mutable. It is the COM object being pointed to by the reference that is changed.

Usually in a builder pattern at least commonly used in Java/Android, the class you use to build with is a mutable builder class, that once you call .build(), will return an immutable non-builder class.
I think that WinRT properties in general are quite "unstable", as some setters actually trigger state changes. A builder should be a stand-in for a constructor, and allowing normal WinRT setters to operate as builders will make for a messy codebase.
Right now the .prop(value) setter pattern in cppwinrt puts the onus on the developer to understand side-effects on setters.

Feel free to reopen if there's interest in exploring this further.


withModifiers(() => {}, ['right']) is failed

Vue version
lastest
Link to minimal reproduction
https://sfc.vuejs.org/#__DEV__eNp9Uj2PnDAQ/SsTNwaJBW2L2FWia9KkThGnIDAsvuAP2YaLhOjT5zfmf2Rs2NXlIkVCwjPvzbPnzazsg7XlMiOrWeM7J20Aj2G2V6GlssYFWMHhABsMzijgROVCAxzgk1H2QMoqBmXwhAvdGe0DKH+DS6zP+EecJgOfjZv6dzy/E7pJdt+JkuVwudJV7YQuZOccNqGban8QPYWCgMpObUCKAJrxDO9TbenkbQyldbigDhfBUlaw67qm27etqcbzXiS1nQMsJ2V6nIhKOBETlPqo6NxUj4tYwfYuT6q15bM3mkxaI10cgBeshpSJObImxoKNIVhfV5Ufumjtsy+Nu1V0Kt2sg1RYolenb868eHQkLFjxSqOi5ILu5FD36ND9T/MN9R/dKEtObtTKMRxq4THXHgepMQJGk3kFjAW8yDB+Mr0cJDr/ZupC449USoXtPKX/a4EsWaFbhTXwmOWpr7RPNODDKEeh08fEx4z3cuHFHQQw+ilOsP77JdmxIHcWPDblntkK+MLTMpAaP/aBf80Pawnmv3/93L+4f7sxOdv+AJ5PAwQ=
Steps to reproduce
I use withModifiers at ts(x) file to achieve the same as @click.right.prevent, but I found that it's failed

right click the <h1>, I can see the right result

but used in ts(x) will be failed
What is expected?
use withModifiers(() => {}, ['right']) can handle right click method
What is actually happening?
it's failed
System Info
No response
Any additional comments?
No response

it not a bug, you should use onContextmenu
import { defineComponent, h, withModifiers } from 'vue'

export default defineComponent({
  name: 'Comp',
  setup() {
    return () => h('div', {
      onContextmenu: withModifiers(() => {
        alert(1)
      }, ['right', 'prevent']),
    }, '哈哈哈')
  }
})

it not a bug, you should use onContextmenu
import { defineComponent, h, withModifiers } from 'vue'

export default defineComponent({
  name: 'Comp',
  setup() {
    return () => h('div', {
      onContextmenu: withModifiers(() => {
        alert(1)
      }, ['right', 'prevent']),
    }, '哈哈哈')
  }
})

Thx! but maybe onClick also support?
because withModifiers(, ['right']) is not actually say that not support for onClick
https://github.com/vuejs/core/blob/9a09e476679040fcec3257d42cd0dab29e95b9f2/packages/runtime-dom/src/directives/vOn.ts#L27


Erro with Container component type

Description
Error with "Container" component type,
the children prop is omitted
Steps to reproduce
1.Create React functional component
2. returns Container component with Graphics component as children
<Container>       <Graphics />     </Container>
Additional info

@inlet/react-pixi version: 6.8.0
React version: 17.0.1
ReactDOM version: 17.0.1
PIXI version: 6.5.2

I've experienced this too, you can turn off typescript using @ts-ignore and it somewhat works for some props like position, however height and width doesn't. I've had to revert to pixi.js.

I dived into the type def and looks like the they are omitting the children props. Not sure if this is intentional.
type Container<T extends PIXI.DisplayObject, U = {}> = Partial<
    Omit<T, 'children' | P | ReadonlyKeys<T> | keyof U> &
    WithPointLike<P>
    > & U & InteractionEvents & { ref?: React.Ref<T> };

 type IContainer = Container<PIXI.Container>;

 export const Container: React.FC<_ReactPixi.IContainer>;

OP was using react 17 so it can't be a version issue. I also tried rolling back with no luck

@Firas88Alkhatib can you provide a repro? I'm struggling to understand the issue. As for the react 18 they did remove childern prop from FC and Component, but none of the topic starter version suggests it's react 18 issue

mb I wasnt paying attention to op's react version but I was also facing the same problem when using react 17. I think its because the Container component doesnt have the children prop from the type def I found in the previous comment.

@nanachi-code this is done intentionally so the pixi children class field (which is omitted) won't clash with react concept of children (which effectively replaces pixi one). If you have repro we can investigate, but otherwise I don't really understand what may cause it

I also faced the same issue, and it should be because I forgot to downgrade @types/react and @types/react-dom. It might solve to downgrade those to version 17 manually, or I recommend you to use typesync(https://github.com/jeffijoe/typesync), which automatically install missing TypeScript typings for dependencies.

It was working fine on React 17. But after migration to 18 it stoped working due to children props removal in React.FC (as @saitonakamura mentioned).

It seems that this error hasn't been corrected in v7.0.0. There was a change made in #338 that was correcting it but it didn't go through. As @sebastian-budka-mir stated and ryohey explained in the Draft, changing React.FC<_ReactPixi.IContainer> into React.FC<React.PropsWithChildren<_ReactPixi.IContainer>> do the trick.

Released in v7.0.1


Slack connector: use the valid connection id to check the new Slack config

https://dust4ai.slack.com/archives/C05F84CFP0E/p1700843510306139?thread_ts=1700834532.463349&cid=C05F84CFP0E

Yes indeed


Embed reply for PEP detection

[ ]  Add an option to allow the default link embed in the /pep command
[ ] During detection for a message with pep in it, instead of sending links, send one embed listing all PEPs that were mentioned and their respective links.

nah, but I was thinking about making the entire reply an embed so you can have hyperlinks when multiple PEPs are mentioned maybe

Originally posted by @trag1c in https://github.com/mcb-dev/mCodingBot/pull/39#discussion_r968876667

The default embed has no useful information. Might be worth trying to scrape the page to get information though.


Unhandled Exception when click Report a problem...

Describe the bug

Default value of ProcessStartInfo.UseShellExecute is changed to false on .NET Core. .NET Docs
So i think this code in src/RoslynPad.Common.UI/ViewModels/MainViewModelBase.cs
private static void ReportProblem()
{
    Task.Run(() => Process.Start("https://github.com/aelij/RoslynPad/issues"));
}

should be changed to
private static void ReportProblem()
{
    Task.Run(() => Process.Start(
        new ProcessStartInfo
        {
            FileName = "https://github.com/aelij/RoslynPad/issues",
            UseShellExecute = true,
        }));
}

To Reproduce
Just click. Always happen.
Expected behavior
Open https://github.com/aelij/RoslynPad/issues by default web browser.
Version

OS: Windows 10 20H2
Build (or commit ID if built from source): v15.1

Fixed in #379


Fix issues with supplier question tracking

Change needed for this story:
https://www.pivotaltracker.com/story/show/119634865
...and fixes problems with the code merged in https://github.com/alphagov/digitalmarketplace-supplier-frontend/pull/487.
The regexp that looks for the banner telling users their question was submitted didn't take whitespace into consideration so wasn't finding it. This didn't show up in the unit tests because the HTML mock used had no whitespace in its banner text:
Banner text in the page
\n\s\s\s\sYour question has been sent. The buyer will post your question and their answer on the ‘Dissolve a company’ page.\n

Banner test in our HTML mock
Your question has been sent. The buyer will post your question and their answer on the ‘Dissolve a company’ page.

This detecting the banner messages is starting to feel quite brittle - if the wording of the messages changes then it's unlikely anyone will remember to update the JavaScript at the same time...
Perhaps dummy url parameters are the way to go everywhere? They feel much less likely to break.
What do you think?

I think you're right. It does feel a bit too brittle to fire the analytics based on parts of the page that we could change for design/content reasons.
I've changed the JS so it's based on the data coming into the template instead.

Nice - looks like it will work.  Let's let Andrew get his mitts on it for retesting  :+1:


blog:  Jekyll/Ruby configuration  files

Run actions/configure-pages@v5
with:
token: ***
enablement: false
Error: Get Pages site failed. Please verify that the repository has Pages enabled and configured to build using GitHub Actions, or consider exploring the enablement parameter for this action. Error: Not Found - https://docs.github.com/rest/pages/pages#get-a-apiname-pages-site
Error: HttpError: Not Found - https://docs.github.com/rest/pages/pages#get-a-apiname-pages-site


chore(main): release 6.0.0

:robot: I have created a release beep boop
6.0.0 (2024-03-15)
⚠ BREAKING CHANGES

buffers: the ReplayBuffer and TrajectoryBuffer classes don't take a rew_dim argument anymore.
package: The package should now be used as stable_learning_control instead of bayesian_learning_control.
This package now depends on Gymnasium instead of Gym. Furthermore, it also requires Gymnasium>=26 (see https://gymnasium.farama.org/content/migration-guide/) for more information.
The simzoo package is no longer included and has to be installed separately through the stable-gym repository.

Features

add docker container (#379) (972079f)
add hyperparameter variant support for exp config files (6ea47f0)
add small policy test script (c701d69)
add support for dictionary type observation spaces (e3bf761)
add torch reproducibility code (#320) (89ef5a2)
enable GPU device selection (#406) (73c1374)
exp_cfg: fix 'start_policy' empty config bug (e7f3cf9)
exp: add lambda lr check experiments (fedfa16)
exp: add min statistics to rstaa2024 data analysis (16ff564)
exp: add rstaa 2024 data analysis script (f0df0a4)
exp: rename CompOscillator lambda experiment (ec7103c)
improve 'eval_robustness' utility (#313) (3985867)
improve hyperparmeter tuning, logger and add W&B logging (#314) (74afd65)
lac: add finite-horizon Lyapunov Candidate (#328) (ed2c85d)
lac: implement Han et al. 2020 hyperparameters (#399) (574b651)
latc: add LATC algorithm (#323) (d74c64f)
package: renames the package to stable-learning-control (#257) (1133d0a)
plot: improve plotter arguments (#425) (c7202a2)
pytorch: add alpha/lambda learning rate customization (#412) (6feb749)
replace OpenAi gym with Gymnasium (#255) (9873a03)
tf2: add alpha/lambda learning rate customization (#416) (712e94b)
wandb: add 'wandb_run_name' argument (#325) (e0a0b9d)

Bug Fixes

Address flake8 and black formatting issues (#395) (517ee30)
correct finite horizon buffer calculation (#398) (779201c)
correctly close gymnasium environments (#340) (a179176)
ensure 'test_policy' works with gymnasium>=0.28.1 (#276) (80fe370)
fix 'test_policy' episode length bug (#292) (6d34f74)
fix 'test_policy' rendering (#291) (48443ca)
fix environment validation (#280) (a8a0346)
fix plot dataframe loading (#338) (90e16e9)
fix several env/policy load bugs (dddd4d8)
fix several policy loading problems (51a664e)
improve tensorflow lazy import (#272) (75192a4)
pytorch: correct epoch-based learning rate decay behavior (#410) (a8df90f)
pytorch: correct step-based learning rate decay (#405) (7d7ac76)
pytorch: ensure correct application of constant learning rate (#411) (2b3693e)
pytorch: fix learning rate decay defaults (#414) (27964fe)
pytorch: resolve critical action rescaling bug (#403) (71d4f64)
remove 'simzoo' submodule (#246) (0122aae)
Resolve ruamel safe_load deprecation issue (#396) (cfcf81c)
run: resolve issue with data_dir input argument (#409) (8d93610)
tf2: correct off-by-one error in learning rate decay calculation (#415) (6ab5001)
tf2: correct step-based learning rate decay (#407) (642a193)
tf2: fix critical tf2 gradient update bug (#322) (dfc239b)
torch: handle 'update_after' set to zero (#408) (7999590)
wandb: fix wandb config format and run name (#317) (ca048de)

Documentation

add docker ownership admonition (58a8e70)
add policy test utility to docker page (5d39316)
add pre-commit note (#341) (9853d05)
add ros-gazebo-gym positive reward comment (#349) (9f5c434)
add snapshots comment to CONTRIBUTING (c2031b2)
add zenodo reference information (#300) (7180fb3)
contributing: updates the contributing documentation (bac8787)
fix broken external links (51317c0)
fix contribution links (#245) (cccc5a7)
fix doc code highlights (#404) (99126f7)
fix documentation (#377) (c3b47c5)
fix documentation latex formulas (#383) (#385) (582568b)
fix incorrect package naming (#282) (5337841)
fix incorrect run command (43df73f)
fix links (#268) (21c5bcf)
fix SAC alg run command (#380) (cf0a7a3)
fix typos (30df6cb)
improve code API documentation (#306) (16d5e26)
improve docs (#344) (908fd78)
improve documentation and package.json (#331) (e9fb90e)
improve documentation defaults (be99008)
improve documentation urls and syntax (#346) (22037cb)
improve package description (#260) (eabfef3)
improve polyak description (#417) (2404a4e)
improve the documentation (#265) (829eb05)
incorporate Docker usage instructions (#401) (2ba8031)
sphinx: fixes documentation errors (38f2da0)
sphinx: updates documentation installation instructions (ddadeb6)
update admonitions to new GFM specs (ae7d3bc)
update contribution note (#316) (44a35af)
update docs make file (6eeb56e)
update documentation (7ceee46)
update documentation and docstrings (5548505)
update numpy intersphinx link (581333d)
update sandbox description (#329) (f60cc3b)
updates code guidelines documentation (4f96a46)
updates docs ci readme badge (074b369)

Code Refactoring

buffers: remove unused 'rew_dim' argument (#327) (a69a7f6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rickstaa/stable-learning-control/releases/tag/v6.0.0 :sunflower:


individual distance tests

Expands the distance tests, similarly to https://github.com/lmcinnes/umap/pull/223

Pull Request Test Coverage Report for Build 10

121 of 122 (99.18%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 94.365%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pynndescent/tests/test_distances.py
121
122
99.18%

Totals

Change from base Build 9:
0.2%

Covered Lines:
1708

Relevant Lines:
1810

💛  - Coveralls


Issues using deployed Lambda function

Describe the bug
I am having trouble with using my deployed Lambda function following this deployment guide. When I invoke a test event I am getting the attached error.
To Reproduce
Steps to reproduce the issue:

Follow steps in this deployment guide to deploy the IrisClassifier to AWS
Go to AWS Lambda function console
Create a test event with the same input as in the deployment guide
Invoke test event

Expected behavior
The classifier returns the classification result.
Screenshots/Logs
Attached
message (2).txt
Environment (Tried multiple versions):

OS: Windows
Python (3.7/3.8)
BentoML (0.8.3/0.11.0)

Additional context
I also run into this issue with a classifier I use for another project

@bbrucee We updated the lambda deployment to this new tool.  It will deploy it as docker container with no size limits.  This should fix your issue.  Feel free to reopen this issue, if the problem still occurs.


[WIP] Add .travis.yml build recipe

@SkyLothar This mirrors PR https://github.com/axa-assistance/lua-resty-jwt/pull/1 (build log at https://travis-ci.org/axa-assistance/lua-resty-jwt/builds/120833073) which seems to show that the tests were already failing beore the changes from #13

thank you!

@SkyLothar Thank you so much for having fixed the tests! I'll keep working on my wip, feeling more confident, now :heart_eyes:


OLCNE - Istio module fails to install

If Istio module is enable, the following error is presented when creating the module:
 Error: unable to build kubernetes objects from release manifest: [unable to recognize “”: no matches for kind “DestinationRule” in version “networking.istio.io/v1alpha3”, unable to recognize “”: no matches for kind “attributemanifest” in version “config.istio.io/v1alpha2”, unable to recognize “”: no matches for kind “handler” in version “config.istio.io/v1alpha2”, unable to recognize “”: no matches for kind “instance” in version “config.istio.io/v1alpha2”, unable to recognize “”: no matches for kind “rule” in version “config.istio.io/v1alpha2”]”

Fixed by #228


curl return code is 0 if download file is redirected

curl return code is 0 if download file is redirected.
curl -OLJks ${curl_options} $file
		if [ $? -ne 0 ]; then
	...

	fi

The code need to update
12:24:42 curl -OLJks  https://api.adoptopenjdk.net/v2/binary/nightly/openjdk8?openjdk_impl=openj9&os=linux&arch=x64&release=latest&type=jdk 12:24:42 unzip file: openjdk8?openjdk_impl=openj9&os=linux&arch=x64&release=latest&type=jdk ... 12:24:42 12:24:42 gzip: openjdk8?openjdk_impl=openj9&os=linux&arch=x64&release=latest&type=jdk: not in gzip format 12:24:42 tar: This does not look like a tar archive 12:24:42 tar: Exiting with failure status due to previous errors 12:24:42 ls: cannot access '*/': No such file or directory 12:24:42 chmod: cannot access 'j2sdk-image': No such file or directory

This is fixed by #1099 and close it.


[AutoPR keyvault/data-plane] RSA key size examples, ECC descriptions

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3136

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/1909


Fix how we aggregate user presence

See getAggregatedPresence:
https://github.com/zulip/zulip-mobile/blob/1baf7aec1/src/utils/presence.js#L16
As the comment there says, this should have the same behavior that the webapp implements in status_from_timestamp.
Comparing those two functions, there are two differences in behavior where we should adjust to match:

When a user doesn't have any presence info more recent than OFFLINE_THRESHOLD_SECS, i.e. 140 seconds, we return a timestamp of 0. The webapp instead records the time of the latest presence we have -- making it possible to distinguish between someone being away for 3 minutes, 3 hours, or 3 weeks.
We include a client property in the returned object, corresponding to whichever client we ended up taking the information from. This can be pretty arbitrary if a user has several clients online, so it doesn't mean much; probably anything that used that property would be making a mistake. We should follow the webapp in not returning that.

On the other hand, we can continue to skip computing the mobile property; as our jsdoc on ClientPresence says, the feature that was meant for was never completed as planned and is now legacy.
The timestamp fix may confuse some other code of ours that relies on the current behavior; I haven't traced through everything. Part of resolving this issue will be to check for that, and if so to (a) when first making this fix, adjust that code in the same commit so its behavior doesn't change; then (b) as a followup, make everything take full advantage of the new more-complete information.

A few weeks ago, @rishig reported (out of band):

I feel like active/inactive state on mobile is sometimes not correct (e.g. currently it thinks I’m offline and have been for 49 years, and also got the report from [a user])

And just now I was looking for some other issue, and happened across this issue's title! And this detail above, which I spotted from reading the code, looks awfully suspicious:

When a user doesn't have any presence info more recent than OFFLINE_THRESHOLD_SECS, i.e. 140 seconds, we return a timestamp of 0.

A quick git diff 1baf7ae src/utils/presence.js shows that that logic hasn't changed since the version I referred to above, so we're still doing that. And that timestamp of 0 sounds awfully likely to cause the symptom Rishi reported.
Bumping this to a priority issue, since we now know of user-visible symptoms that this is probably causing.