Parser crashes with KeyError

When trying to run the parser, it crashes with KeyError.
>>> from diaparser.parsers import Parser
>>> parser = Parser.load("fi_tdt.turkunlp")
>>> parser.predict([['Kissa', 'kävelee', 'kadulla', '.']])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/iikka/.local/lib/python3.9/site-packages/diaparser/parsers/biaffine_dependency.py", line 129, in predict
    return super().predict(**Config().update(locals()))
  File "/home/iikka/.local/lib/python3.9/site-packages/diaparser/parsers/parser.py", line 191, in predict
    dataset.build(args.batch_size, args.buckets)
  File "/home/iikka/.local/lib/python3.9/site-packages/diaparser/utils/data.py", line 94, in build
    self.loader = DataLoader(dataset=self,
  File "/home/iikka/.local/lib/python3.9/site-packages/diaparser/utils/data.py", line 108, in __init__
    super().__init__(*args, **kwargs)
  File "/home/iikka/.local/lib/python3.9/site-packages/torch/utils/data/dataloader.py", line 200, in __init__
    if isinstance(dataset, IterableDataset):
  File "/usr/lib64/python3.9/typing.py", line 1114, in __instancecheck__
    if all(hasattr(instance, attr) and
  File "/usr/lib64/python3.9/typing.py", line 1114, in <genexpr>
    if all(hasattr(instance, attr) and
  File "/home/iikka/.local/lib/python3.9/site-packages/diaparser/utils/data.py", line 65, in __getattr__
    return [getattr(sentence, name) for sentence in self.sentences]
  File "/home/iikka/.local/lib/python3.9/site-packages/diaparser/utils/data.py", line 65, in <listcomp>
    return [getattr(sentence, name) for sentence in self.sentences]
  File "/home/iikka/.local/lib/python3.9/site-packages/diaparser/utils/transform.py", line 117, in __getattr__
    return self.values[self.maps[name]]
KeyError: 'register_function'

I have Python 3.9.6, pytorch 1.9.0, transformers 4.10.2.

This can be fixed by changing transform.py around line 113 to:
   def __getattr__(self, name):
        if name in self.__dict__:
            return self.__dict__[name]
        elif name in self.maps:
            return self.values[self.maps[name]]
        else:
            raise AttributeError()

@fergusq I fixed this downstream now https://github.com/TurkuNLP/Turku-neural-parser-pipeline/issues/34   I didn't notice this issue you opened here.

Fixed.


TeamsMeetingBroadcastPolicy

Pull Request (PR) description
New Resource TeamsMeetingBroadcastPolicy
This Pull Request (PR) fixes the following issues
N/A

This change is

Codecov Report

:exclamation: No coverage uploaded for pull request base (Dev@47368f7). Click here to learn what that means.
The diff coverage is 98.64%.

@@          Coverage Diff           @@
##             Dev     #318   +/-   ##
======================================
  Coverage       ?   90.18%
======================================
  Files          ?       73
  Lines          ?     7416
  Branches       ?       11
======================================
  Hits           ?     6688
  Misses         ?      717
  Partials       ?       11

Impacted Files
Coverage Δ

...adcastPolicy/MSFT_TeamsMeetingBroadcastPolicy.psm1
98.64% <98.64%> (ø)

Continue to review full report at Codecov.

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

@ykuijs for review

@ykuijs ready for second review


[feature] refactored communication creation in MOE

refactored communication creation in MOE to support PR-MOE
changed moe gradient handler to adapt new feature

Hi @1SAA , can you avoid having a large number of files in one PR next time? It is tough to review in detail with too many changes.

I understand. But this feature needs to change the fundamental communication functions when using MoE.
Any code about MoE can't run properly or even crashed, when any fundamental changes occur.
In order to make MoE example runs properly, I have to change so much code. I'm sorry about that.


Web app

Filtered out companies with no positions. Added nav w/Search functionality. Fixed empty title in AgileTrailblazers.

If you find that you need to change the information on a company. Please edit the individual company file found in the companies folder (ie companies/AgileTrailblazers.json). The correction was almost reverted when I ran the merge script.

Sorry about that will do next time I've been meaning to check out the script, should have done that beforehand.


IDVA6-1912 - Bug fix - user not being logged out when removing themselves

Link to Jira:
https://companieshouse.atlassian.net/browse/IDVA6-1912
Changes:

Updated security middleware to allow for sign out after user removes themselves

CI: Security warnings found!


Support executing test cases in a range for JUnit4Runner

For some long-running tests, we may want to debug failing tests cases one by one. For this case, executing test class from a certain id rather than the very beginning every time may save us a lot of time.

The pull request was merged.
Thank you for filing and the PR!


Provider produced inconsistent final plan

Provider produced inconsistent final plan
Error: Provider produced inconsistent final plan.
Changes have been applied, but those errors appeared.
Versions

Terraform: 0.12.31

Provider(s): aws 3.69.0

Module: aws_autsocaling

Reproduction

Steps to reproduce the behavior:
 no
 yes

Code Snippet to Reproduce

Changes applied without those errors because it shows that pipeline job failed, but it's not.
Expected behavior

Applied changes without that errors
Actual behavior

Output Error: Provider produced inconsistent final plan error
Error: Provider produced inconsistent final plan
When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" changed the planned action from Update to
DeleteThenCreate.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for .arn: was
known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.availability_zones: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.max_instance_lifetime: was cty.NumberIntVal(0), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.capacity_rebalance: was cty.False, but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.default_cooldown: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.service_linked_role_arn: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.suspended_processes: was cty.SetValEmpty(cty.String), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for .id: was
known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.placement_group: was cty.StringVal(""), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.health_check_type: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.launch_configuration: was cty.StringVal(""), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.load_balancers: was cty.SetValEmpty(cty.String), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for .name_prefix:
was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for .name: was
cty.StringVal("bpm-eu1int-45"), but now cty.StringVal("bpm-eu1int-46").

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.launch_template[0].name: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

ERROR: Terraform apply failed with exit code 1``

Hi!
This is a bug in the provider, which should be reported in the provider's own issue tracker. and please provide input Terraform code snippet which produces an error.

@antonbabenko thanks for tips, where exactly, here? https://github.com/hashicorp/terraform-provider-aws/issues/new?assignees=&labels=&template=Bug_Report.md

Yes


16079 Many fixed to Approval Type

Issue #: bcgov/entity#16079
Description of changes:

added invalid-section styling
fixed whitespace
simplified v-radio template
fixed validations
fixed change/input/error handling
added validate prop
updated court order number rules text
fixed initial state (when mounted)
fixed validation
fixed lint issues

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the business-filings-ui license (Apache 2.0).

Hello. Please review these changes while I work on the unit tests.
I am aware that some of these changes will break existing users of this component. For this reason, I will update the minor version number of this component (ie, from 1.0.61 to 1.1.0). (I can't use 2.x.x because it's already used for Vue3 code.)

See https://github.com/bcgov/entity/issues/16079 for more screenshots.


V0.8 - ASI Timeout

So, I've removed the previous allsky folder, and re-cloned the new one (0.8), putting back in all my settings.
Initially, I had an image appear, no problem, but after changing a couple of settings (in the camera settings I think, I haven't touched anything I don't understand) I now have a black image with the following in the log:
Aug  6 14:03:10 allsky allsky.sh[1831]: ==========
Aug  6 14:03:10 allsky allsky.sh[1831]: === Starting daytime capture ===
Aug  6 14:03:10 allsky allsky.sh[1831]: ==========
Aug  6 14:03:10 allsky allsky.sh[1831]: Saving images with delay of 60,000 ms (60 sec)
Aug  6 14:03:11 allsky allsky.sh[1831]:   > ERROR: Failed getting image, status = 11 (ASI_ERROR_TIMEOUT)
Aug  6 14:03:13 allsky allsky.sh[1831]:   > ERROR: Failed getting image, status = 11 (ASI_ERROR_TIMEOUT)

I know the camera is fine, as after a reboot etc. I can open it in another program on the PI and it's fine.
I'm going to reset the settings to default, but I've mentioned it here in case anyone else sees the same and collectively, we can give the devs the info to find a possible issue.

No, that hasn't worked - here's more of the log, showing the camera detected, initialised and ready to go:
Aug  6 14:07:49 allsky allsky.sh[3725]:      ***** Starting AllSky *****
Aug  6 14:07:49 allsky allsky.sh[3725]: Making sure allsky.sh is not already running...
Aug  6 14:07:49 allsky allsky.sh[3725]: Trying to automatically choose between ZWO and RPI camera
Aug  6 14:07:49 allsky allsky.sh[3725]: /home/pi/allsky/allsky.sh: line 89: /home/pi/allsky/scripts/copy_notification_image.sh: Permission denied
Aug  6 14:07:49 allsky allsky.sh[3725]: CAMERA: ZWO
Aug  6 14:07:49 allsky allsky.sh[3725]: CAMERA_SETTINGS: /etc/raspap/settings_ZWO.json
Aug  6 14:07:49 allsky allsky.sh[3725]: Starting allsky camera...
Aug  6 14:07:51 allsky allsky.sh[3725]: #033[32m ******************************************
Aug  6 14:07:51 allsky allsky.sh[3725]: #033[32m *** Allsky Camera Software v0.8 | 2021 ***
Aug  6 14:07:51 allsky allsky.sh[3725]: #033[32m ******************************************
Aug  6 14:07:51 allsky allsky.sh[3725]: #033[32mCapture images of the sky with a Raspberry Pi and an ASI Camera
Aug  6 14:07:51 allsky allsky.sh[3725]: #033[33mAdd -h or -help for available options
Aug  6 14:07:51 allsky allsky.sh[3725]: #033[0mAuthor: Thomas Jacquin -<EMAIL_ADDRESS>Aug  6 14:07:51 allsky allsky.sh[3725]: #033[0mContributors:
Aug  6 14:07:51 allsky allsky.sh[3725]: -Knut Olav Klo
Aug  6 14:07:51 allsky allsky.sh[3725]: -Daniel Johnsen
Aug  6 14:07:51 allsky allsky.sh[3725]: -Yang and Sam from ZWO
Aug  6 14:07:51 allsky allsky.sh[3725]: -Robert Wagner
Aug  6 14:07:51 allsky allsky.sh[3725]: -Michael J. Kidd -<EMAIL_ADDRESS>Aug  6 14:07:51 allsky allsky.sh[3725]: -Chris Kuethe
Aug  6 14:07:51 allsky allsky.sh[3725]: #033[0m
Aug  6 14:07:51 allsky allsky.sh[3725]: Listing Attached Cameras:
Aug  6 14:07:51 allsky allsky.sh[3725]:   - 0 ZWO ASI178MC
Aug  6 14:07:51 allsky allsky.sh[3725]: ZWO ASI178MC Information:
Aug  6 14:07:51 allsky allsky.sh[3725]:   - Resolution:3096x2080
Aug  6 14:07:51 allsky allsky.sh[3725]:   - Pixel Size: 2.4ÃŽÂ¼m
Aug  6 14:07:51 allsky allsky.sh[3725]:   - Supported Bin: 1 2 3 4
Aug  6 14:07:51 allsky allsky.sh[3725]:   - Color Camera: bayer pattern:RG
Aug  6 14:07:51 allsky allsky.sh[3725]:   - SDK version 1, 19, 0, 0
Aug  6 14:07:51 allsky allsky.sh[3725]:   - Initialise Camera OK
Aug  6 14:07:51 allsky allsky.sh[3725]: - Sensor temperature:37.60
Aug  6 14:07:51 allsky allsky.sh[3725]: #033[32m
Aug  6 14:07:51 allsky allsky.sh[3725]: Capture Settings:
Aug  6 14:07:51 allsky allsky.sh[3725]:  Image Type: ASI_IMG_RGB24
Aug  6 14:07:51 allsky allsky.sh[3725]:  Resolution (before any binning): 3096x2080
Aug  6 14:07:51 allsky allsky.sh[3725]:  Quality: 95
Aug  6 14:07:51 allsky allsky.sh[3725]:  Daytime capture: 1 (yes)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Exposure (day): 0.500ms
Aug  6 14:07:51 allsky allsky.sh[3725]:  Auto Exposure (day): 1 (yes)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Exposure (night): 10000ms
Aug  6 14:07:51 allsky allsky.sh[3725]:  Max Exposure (night): 20000ms
Aug  6 14:07:51 allsky allsky.sh[3725]:  Auto Exposure (night): 1 (yes)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Delay (day): 5000ms
Aug  6 14:07:51 allsky allsky.sh[3725]:  Delay (night): 10ms
Aug  6 14:07:51 allsky allsky.sh[3725]:  Gain (night only): 50
Aug  6 14:07:51 allsky allsky.sh[3725]:  Auto Gain (night only): 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Max Gain (night only): 200
Aug  6 14:07:51 allsky allsky.sh[3725]:  Gain Transition Time: 1800 seconds
Aug  6 14:07:51 allsky allsky.sh[3725]:  Brightness (day): 50
Aug  6 14:07:51 allsky allsky.sh[3725]:  Brightness (night): 50
Aug  6 14:07:51 allsky allsky.sh[3725]:  Cooler Enabled: 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Target Temperature: 0C
Aug  6 14:07:51 allsky allsky.sh[3725]:  Gamma: 50
Aug  6 14:07:51 allsky allsky.sh[3725]:  WB Red: 53
Aug  6 14:07:51 allsky allsky.sh[3725]:  WB Blue: 90
Aug  6 14:07:51 allsky allsky.sh[3725]:  Auto WB: 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Binning (day): 1
Aug  6 14:07:51 allsky allsky.sh[3725]:  Binning (night): 1
Aug  6 14:07:51 allsky allsky.sh[3725]:  USB Speed: 40
Aug  6 14:07:51 allsky allsky.sh[3725]:  Auto USB Speed: 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Text Overlay: [none]
Aug  6 14:07:51 allsky allsky.sh[3725]:  Text Extra Filename: [none]
Aug  6 14:07:51 allsky allsky.sh[3725]:  Text Extra Filename Age: 0
Aug  6 14:07:51 allsky allsky.sh[3725]:  Text Line Height 30px
Aug  6 14:07:51 allsky allsky.sh[3725]:  Text Position: 15px left, 35px top
Aug  6 14:07:51 allsky allsky.sh[3725]:  Font Name:  0 (SIMPLEX)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Font Color: 255 , 255, 255
Aug  6 14:07:51 allsky allsky.sh[3725]:  Small Font Color: 0 , 0, 255
Aug  6 14:07:51 allsky allsky.sh[3725]:  Font Line Type: 16
Aug  6 14:07:51 allsky allsky.sh[3725]:  Font Size: 7.0
Aug  6 14:07:51 allsky allsky.sh[3725]:  Font Line: 1
Aug  6 14:07:51 allsky allsky.sh[3725]:  Outline Font : 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Flip Image: 0
Aug  6 14:07:51 allsky allsky.sh[3725]:  Filename: image.jpg
Aug  6 14:07:51 allsky allsky.sh[3725]:  Latitude: 60.7N
Aug  6 14:07:51 allsky allsky.sh[3725]:  Longitude: 135.05W
Aug  6 14:07:51 allsky allsky.sh[3725]:  Sun Elevation: -6
Aug  6 14:07:51 allsky allsky.sh[3725]:  Locale: en_US.UTF-8
Aug  6 14:07:51 allsky allsky.sh[3725]:  Notification Images: 1 (yes)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Histogram Box: 500 500 50 50
Aug  6 14:07:51 allsky allsky.sh[3725]:  Show Histogram Box: 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Show Histogram Mean: 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Show Time: 1 (yes) (format: %Y%m%d %H:%M:%S)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Show Details: 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Show Temperature: 1 (yes)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Temperature Type: C
Aug  6 14:07:51 allsky allsky.sh[3725]:  Show Exposure: 1 (yes)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Show Gain: 1 (yes)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Show Brightness: 1 (yes)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Preview: 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Darkframe: 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]:  Debug Level: 0
Aug  6 14:07:51 allsky allsky.sh[3725]:  TTY: 0 (no)
Aug  6 14:07:51 allsky allsky.sh[3725]: #033[0m
Aug  6 14:07:51 allsky allsky.sh[3725]: Will adjust gain at transitions
Aug  6 14:07:51 allsky allsky.sh[3725]: Stop the allsky service to end this process.
Aug  6 14:07:51 allsky allsky.sh[3725]: ==========
Aug  6 14:07:51 allsky allsky.sh[3725]: === Starting daytime capture ===
Aug  6 14:07:51 allsky allsky.sh[3725]: ==========
Aug  6 14:07:51 allsky allsky.sh[3725]: Saving images with delay of 5000 ms (5 sec)
Aug  6 14:07:52 allsky allsky.sh[3725]:   > ERROR: Failed getting image, status = 11 (ASI_ERROR_TIMEOUT)
Aug  6 14:07:55 allsky allsky.sh[3725]:   > ERROR: Failed getting image, status = 11 (ASI_ERROR_TIMEOUT)

I also notice this:

Aug  6 14:07:39 allsky allsky.sh[3593]:   > ERROR: Failed getting image, status = 11 (ASI_ERROR_TIMEOUT)
Aug  6 14:07:41 allsky allsky.sh[3593]: sh: 1: scripts/copy_notification_image.sh: Permission denied
Aug  6 14:07:41 allsky allsky.sh[3593]: saveImageDay.sh: Uploading 'image.jpg' with timestamp: 14:07:41
Aug  6 14:07:44 allsky allsky.sh[3593]:      ***** Stopping AllSky *****
Aug  6 14:07:44 allsky allsky.sh[3593]: capture exited with retcode=2
Aug  6 14:07:44 allsky allsky.sh[3593]: /home/pi/allsky/allsky.sh: line 152: /home/pi/allsky/scripts/copy_notification_image.sh: Permission denied

Something to check?

I've deleted the allsky folder, and settings files from raspap, cloned a fresh copy, ran the install.sh and gui installation.
Rebooted the PI and cleared browser cahse to log back into the web interface.
I still have a black image with the same permission denied entries in the log, and the camera is fine in another capture package.
Soooooo....what's next?

I've change the permissions on scripts/copy_notification_image.sh to match the others (755) and I now see 'Allsky is not running' in red in place of the black image, and this changes to 'Allsky is starting up' in green. They alternate every 5 seconds (probably tied to the image auto-refresh on the browser?).
In the log, it is 'Starting AllSky' every 20 seconds, each time ending with the ASI_ERROR_TIMEOUT.

I've moved the camera onto one of the USB3 ports, having previously moved it to the USB2 port and it's now working. That must have caused the issue.
Food for thought - why does it not work on the USB2 port when in other programs it's fine?

Jon,
I'll have to ask Thomas about the permissions on scripts/copy_notification_image.sh, but you did the right thing.
Some people have found it helpful to change the USB speed (either higher or lower) when the software can't get pictures.  I don't know why it didn't work on your USB2 port when it used to.
When you say you got "a black image", was there a black "image.jpg" file, or the web browser simply didn't show any image?
After two failed attempts to get an image, the software exits and displays the "Allsky is not running" message.  If you have the service start allsky, it restarts the software and one of the first things it does is display the "Allsky is starting up" message.  If Allsky gets 2 failed images it'll exit, get restarted.... for ever.
Eric

Eric,
A new file has been added byt Thomas, with the correct permissions.
Is was a black background or placeholder, i.e. no image - I didn't dig any deeper, but let's say you took a complete black jpg and displayed it, that's what it looked like - there was no 'broken link' image or anything like that.
Regarding the ASI timeout, as mentioned on another thread, it may have been the bandwidth setting. May I suggest that you set it to auto by default for all new installs, and make it clear that the user can specify if they want to, rather than setting it to 40 default and finding it may not work?
i suppose it could easily be tested, reduce the bandwidth figure until a timeout occurs, then increase until the error is no longer valid. That would prove it.
I will close this now as this appears to be resolved, at least from an understanding point of view.


Custom query parameter bug - missing $

Adding a custom query parameter to a request does not work because the "$" is not inserted:
client.entity_sets.BusinessRole.get_entities().top(1).custom("filter", "Language eq 'FR'")
should be the same as
client.entity_sets.BusinessRole.get_entities().top(1).filter("Language eq 'FR'")   .
The urllib logs from the first snipped (custom) clarfiy the problem:
GET /odata.svc/BusinessRole?filter=Language+eq+%27FR%27&%24top=1
NOTE the missing "$" (%24) in front of the query param!
If one runs:
client.entity_sets.BusinessRole.get_entities().top(1).custom("$filter", "Language eq 'FR'")
it works properly and the urllib logs state:
GET /odata.svc/BusinessRole?%24filter=Language+eq+%27FR%27&%24top=1

Hi @jkminder,
I believe this works as designed. "Adding a custom query parameter to a request does not work" sentence is not entirely true, it is IMHO just this edge case of "first and only" query parameter.

The documentation is maybe sparse, but custom was added as a possibility to add something after standard odata query parameters.
Is there any reason why you need to run filter query trough custom instead of the standard filter (same doc page, used in the get_entities().top(1).filter("Language eq 'FR'") example)?
You were able to create an workaround easily anyway for your scenario anyway, knowing that it is the only query parameter in such code.  If the pyodata would be able to detect that edge case, for what exact purpose? If most of the OData requests will be built using only the custom query builder, then IMHO you are in almost similar scenario to building the entire URLs from scratch with just requests library.

If there is solid use case / explanation to point 2, I am happy to review a PR request from you for such new enhancement (with new tests). Otherwise I am more inclined to close this issue as "works as designed".

Hi @jkminder,
before the answer, I have spent anyway quite a time inside a debugger and checking the tests. It was fun, I also learned about requests.PreparedRequest for checking if somehow the URL maybe generated incorrectly (urllib3 is nice, but I wanted to investigate if it is possible to access that inside the  pyodata execute() method).
The custom("$skiptoken",... is really a correct and expected way, as you noted (that you get the desired result, the two code samples from last comment are really different just in the $ character.). Therefore I see no bug, in both code samples the generated full URL is as expected.
client.entity_sets.BusinessRole.get_entities().filter("Language eq 'DE'").custom("$skiptoken", "guid'e3f9d8d3-c36e-4f3b-94fa-00031672b6e1','FR'").top(10).execute()
client.entity_sets.BusinessRole.get_entities().filter("Language eq 'DE'").custom("skiptoken", "guid'e3f9d8d3-c36e-4f3b-94fa-00031672b6e1','FR'").top(10).execute()

The custom gives you complete control over the url parameters, so it must be a valid, generic URL parameters string. And those begins with ? and are separated by  &.  Some, odata relevant url parameters start with $prefix, true, but that does not mean every url parameter in custom should have - for example the sap-client, noted in documentation is just normal url parameter for SAP gateway, if sometimes needed.
I am not sure what exactly you mean by with get_entity it seems to work) - I have checked that get_entity and get_entities behave exactly the same, in respect to custom():
example:
service.entity_sets.MasterEntities.get_entity(1).custom("skiptoken", "guid'e3f9d8d3-c36e-4f3b-94fa-00031672b6e1','FR'")
/MasterEntities('1')?skiptoken=guid%27e3f9d8d3-c36e-4f3b-94fa-00031672b6e1%27%2C%27FR%27

And to consider this as a feature request - to maintain special whitelist of parameters that should be automatically added with $ prefix if they are present inside custom() without it - well, that would be completely magic code. Definitely better to leave it to current "developer should know about specifics of what is needed to the URL".
I will close this issue as "Works as designed/ Not a bug". It must have been an "invalid URL generation" case to be a valid issue.
But thanks for taking the time for an improvement proposal.

Hi thanks for taking time to investigate this. I completely see you point and agree. Not inserting the '$' by default gives one much better control. I think a hint in the docs that, if the url parameter passed into custom requires a $ one must provide this. Just in case other people stumble upon this issue.

Hi @jkminder - true, may be unexpected - feel free to create PR to https://github.com/SAP/python-pyodata/blob/master/docs/usage/querying.rst so it is understandable from a point of view of first glance at this.

Doc example update in 34a5c33, after merge of new unit tests.
Closing.


dynamically scrape year  for indygo org.

@SimmonsRitchie
What's this PR do?
Edit the committees for Indygo to dynamically retrieve the current year.
Why are we doing this?
Previously, these committees had the year '2023' hardcoded into the date. Better if the entire date is dynamically scraped.
Steps to manually test
Reviewer can check the source webpage to check that the dates are correctly scraped. Reviewer should also run pytest.
Are there any smells or added technical debt to note?
The pytest is not passing for any of the scrapers. I updated the html files for each of the organizations, but the startdate and meeting ids are still coming back as failed.

Delete any spider with 'indianapolis_' prefix
Looking at the repo, I thought that might be the case. After we get through this PR could you do me a big favor and create a new PR that deletes these spiders and any other files that may be unnecessary or obsolete? Might be a good PR to fit in any other clean up chores.
IvyTech
This is the page I saw but I wasn't sure if there was something else here that I might be missing. Yes, I think this is a good example of a spider we should mark for deactivation. I will communicate this to Max. Lets just delete this spider entirely.
Indygo Question
There's a few different ways we can skin this cat! I'd suggest getting the section titles before looping over the li tags. I'd also suggest removing calls to methods that aren't needed and cleaning up some of the methods and method calls more generally. Eg.
    def parse(self, response):
        """Parse meeting information from IndyGo Board page"""

        meeting_section = response.css(".content-section:nth-child(4)")
        section_title = meeting_section.css("h2::text").get()
        meeting_year =  #<-- parse year from section_title here
        for date_str in meeting_section.css("ul li"):
            meeting = Meeting(
                # Below, remove method calls that aren't needed or args that aren't needed
                title="IndyGo Board", # <-- eg. no need for item arg here
                description=self._parse_description(item),
                classification=self._parse_classification(item),
                # Update _parse_start method
                start=self._parse_start(date_str, meeting_year),
                end=self._parse_end(item),
                all_day=self._parse_all_day(item),
                time_notes=self._parse_time_notes(item),
                location=self._parse_location(item),
                links=self._parse_links(item),
                source=self._parse_source(response),
            )
            meeting["status"] = self._get_status(meeting)
            meeting["id"] = self._get_id(meeting)

            yield meeting

@SimmonsRitchie Hello.
Thank you for the help, it was very useful. Now, the next time I need to get the parent of an element, I know how to do it.
OK, all the scrapers and pytests are fixed. The CI is failing at 'Validate Output' step. Not sure what it means.

Thank you for all your work on this fix, @haileyhoyat! I appreciate you working with me on this.
I have to run out shortly to catch a flight but I'll try to look at your changes while I'm on the plane or tomorrow if I have time. I'll investigate that error. The last part of our CI process is not something I've looked closely at yet.

@haileyhoyat, my flight ended up getting delayed so I had a bit more time. In a nutshell: can you do a bit more clean up on the methods and method calls in these files as I suggested both in my comment above and my inline comments? I see cases where values are still being assigned via method calls where they probably can just be assigned directly to the Meeting item and the methods deleted entirely.
Also, re: hardcoded 2023 dates, setting aside the files prefixed indianapolis_ and the Ivy Tech spider, I see a hardcoded 2023 here. Do we need to address that?

@SimmonsRitchie Hi. I'm so sorry, I promise I wasn't ignoring you. I have made sure to turn on Github notifications for whenever I'm tagged in something.
OK, I think you'll be happy with the Indygo spiders now. Since there are so many constants, the Indygo spiders only need the _parse_start() method.
For the ind_school_board. Still working. The source for meetings is boarddocs, a popular software for school districts to post their meetings: https://go.boarddocs.com/in/indps/Board.nsf/Public
Rumor on the street is there's a way to get the XML data for a school's meeting. Here is the XML for Indianapolis, and what I'm scraping from: https://go.boarddocs.com/in/indps/Board.nsf/XML-ActiveMeetings

@SimmonsRitchie
For the ind_school_board. Still working on it. The source for meetings is boarddocs, a popular software for school districts to post their meetings: https://go.boarddocs.com/in/indps/Board.nsf/Public
Rumor on the street is there's a way to get the XML data for a school's meeting. Here is the XML for Indianapolis, and what I'm scraping from: https://go.boarddocs.com/in/indps/Board.nsf/XML-ActiveMeetings
When I try to scrape from the xml link, I get the error: 'DEBUG: Forbidden by robots.txt: <GET https://go.boarddocs.com/in/indps/Board.nsf/XML-ActiveMeetings>'
Thoughts on how to get past this? I know there's a way.

@SimmonsRitchie Hello. OK The XML for ind_school_baord is going OK. I am getting stuck on two parts:

On line#68, _get_status(item) is throwing an error if i use that line for meeting["status"]. For now I've commented it out and below made meeting["status"] = 'passed'

Line#88 for _parse_start(). If a time is provided for a meeting, it appears in the  element. I am getting the text from , and doing a regex search for the time. If the regex search turns up empty, then time_str = "".
All of the returned meetings have a time of "", so are returning with a start time of 12AM. This is not correct. At least half of the meetings have a time in their  element. Below is a screen shot of the last meeting scraped, indicating a time of 4:30PM, but the meeting is returning with a time of 12AM.

@SimmonsRitchie Update for ind_school_board. I am scraping the XML but have run into a problem with the start time:
Meeting times are in the  element. Some meetings have an indicated time while others do not. On line#95, I am extracting the  text, and searching if there's a time in the text. For some reason all of the meetings are returning with an empty string. As an example, below is a screenshot of the very last meeting scraped in the XML, it has a meeting time of 4:30PM. I think in my _parse_start() method, I'm doing my regex search incorrect, which is why none of the meeting times are being found.

Heya, @haileyhoyat! My apologies for my own belated response. I was at a City Bureau staff retreat in Chicago for most of last week and I was out of the office for most of yesterday too. I'll be off again from noon tomorrow but I I've dug back into this now. Let's get to it 🚀
Thank you!
First off, thank you for addressing some of the big issues I cited in my last comments, particularly re: tests. I really appreciate it, as always!
Clean code
I just left another big salvo of comments. Most of these are minor code style things. We all make mistakes but please, please do your best to remove dead code, avoid committing code using for debugging (like print statements), and try to fix linting issues rather than suppressing them. This keeps our code clean and makes it easier for reviewers (like myself) to review changes. I tried to flag as much as I could but please be on the lookout for any remaining code style issues I might have missed 🙏
isort
Looking at the CI failure, it looks like isort is flagging some import style issues. If you can run isort . from the pipenv shell and commit those fixes I'd be appreciative 🙏
parse start date issue
Having run your school board spider and taking a quick look at your time parsing method here, my sense here is that your regex is probably doing what it needs to do. You're extracting this from the meeting title of each meeting and without doing a deep dive on this issue, it looks like some of the meeting titles don't include time information (which is unfortunate). The best we can do is provide a sensible default time in these situations.
Big XML response
Running the school board spider, it looks like the XML we get in the HTTP response is pretty big, with meetings stretching all the way back to 2006. This is more of a polish question than a "must have" but have you tinkered with the HTTP requests for this site at all? Are there any query params or request body key-values we can provide that might return a more limited XML response (eg. the most recent 50 items or, say, X months of meeting data)? If you can't figure this out, no worries, but a smaller response would definitely speed up this particular spider. When I request this URL in Postman it
seems to be returning a full 4MB of data:

@SimmonsRitchie Hello. Thank you for the feedback. I will get better at writing these spiders. I appreciate you helping me and assure you that I'm making strong mental notes of everything so my spiders get better moving forward.
I cleaned a lot up this morning but am not done yet. Will continue this afternoon (yes, I know you're off).

@SimmonsRitchie Hello. OK, these scrapers should be good now. Code is clean and readable, no dead code, noqa only used on long lines, all tests pass.
Two things:

I was not able to figure out how to shorten the XML response for ind_school_board yet. The scraper and unit tests are good to go right now, but is still collecting all of the meetings. I will take another run at it, but at least the scraper is working as is now.

The CI is failing but it's not because of the spiders or unit tests. The error happens on the validate results step. "AttributeError: 'ScrapyArgumentParser' object has no attribute 'add_option' " . I found this thread that maybe is the answer.
I think either 'add_option'  should be changed to '_add_option', or something else with the repo architecture. I don't want to touch anything on the architecture side.

https://github.com/scrapinghub/scrapinghub-entrypoint-scrapy/issues/64

Thank you as always for your work here, @haileyhoyat. I'll take a more detailed look at this PR soon but for the moment:

I was not able to figure out how to shorten the XML response for ind_school_board yet. The scraper and unit tests are good to go right now, but is still collecting all of the meetings. I will take another run at it, but at least the scraper is working as is now.

That's okay, thank you for trying anyway.

The CI is failing but it's not because of the spiders or unit tests. The error happens on the validate results step. "AttributeError: 'ScrapyArgumentParser' object has no attribute 'add_option' " . I found this thread that maybe is the answer.
I think either 'add_option'  should be changed to '_add_option', or something else with the repo architecture. I don't want to touch anything on the architecture side unless I'm 100% certain of what I'm doing.

scrapinghub/scrapinghub-entrypoint-scrapy#64

So this is an issue with a custom Scrapy command called scrapy validate that's provided by city-scrapers-core. It's intended to make sure the output of a spider is good. In your pipenv virtual env you can run it like so:
scrapy validate <spider-name>

or, to validate all spiders.
scrapy validate --all

In our case, if I understand the script in our CI process correctly, we're just running scrapy validate on the spiders that have changed in the PR compared to the main/master branch.
The error we're encountering doesn't appear to relate to any of the changes in your PR. If you run scrapy validate --all locally on the main branch you'll encounter the same error. The exact cause of the error is a bit mysterious to me, but it seems to relate to another strange dependency conflict. Making some tweaks to our pipfile and then re-generating the lock file seems to have fixed it.
Try the following to see if it resolves the issue for you:

Delete the existing pipenv virtual env for this project:

pipenv --rm

Fetch the latest version of the main branch and merge it into this branch. Resolve any conflicts if they exist.

git fetch origin main && git merge origin/main

Reinstall the project

pipenv sync --dev

Make sure scrapy validate works as expected and doesn't throw any errors:

pipenv run scrapy validate --all

If that works, push the changes to your remote branch and that will hopefully resolve the CI issue.

Alrighty, @haileyhoyat! I think this is look pretty good! My apologies, I blew up the scope of this PR a bit but it is nice to have those spiders looking a bit cleaner and it made reviewing the changes a lot easier.
I didn't precisely check the scraped data with each target site but based on my rough eyeballing it looked pretty good. I really wish we could figure out a way to limit the size of that XML response for the school board spider but – if there is a way to do that – we can save it for another day.
I think we're good here. Thanks for all your work on this. Merge when you're ready 🚀


Phone Number Management

WIP

Hi Andrew. I'm pretty excited for this code to land and appreciate you working on it. I think at one point you asked for an early code review and I was negligent. My apologies for that! Overall the code looks great. The only part I would request you reconsider is adding Boolean types. My personal preference would be to just make them pointers to bool and if needed create functions around them. I know pointers to bools can be annoying to work with but to me it makes more sense than seeing a Boolean type.

@sfreiberg
Fair enough. Thoughts on my new approach?
twilio.NewBoolean(true)
twilio.NewBoolean(false)

LGTM. Are you ready for me to merge it or did you have more changes you wanted to make?

LGTM. Are you ready for me to merge it or did you have more changes you wanted to make?

You know, while I'm at it, I might as well flesh out the update and delete too. I'll get back to you in a couple days.

As a user of this library, I would like to quickly state that I am glad I found this pull request. Updating and deleting incoming phone number webhook URLs would be very welcome, since it would allow for application self-configuration.
That way when the application URLs change, it can automatically re-configure itself to work and set the appropriate webhooks URLs to the correct handlers when it is launched.

As a user of this library, I would like to quickly state that I am glad I found this pull request. Updating and deleting incoming phone number webhook URLs would be very welcome, since it would allow for application self-configuration.
That way when the application URLs change, it can automatically re-configure itself to work and set the appropriate webhooks URLs to the correct handlers when it is launched.

this is exactly how I'm using this :)

@sfreiberg I've implemented the Update and Delete operations.

LGTM


Kali Linux "sh: 1: color: Permission denied"

The termcolor module works on Windows but when I try to run it on Kali Linux, it says "sh: 1: color: Permission denied" on my terminal. However, my program still works. Do you know what the cause of the message is? Thank you!

Please can you give more details? For example:
What did you do?
What did you expect to happen?
What actually happened?
What versions are you using?

OS:
Python:
termcolor:

Please include code that reproduces the issue.
The best reproductions are self-contained scripts
with minimal dependencies.

Why It Happened: This issue usually pops up because Windows and Linux treat file permissions a bit differently. In Linux, newly created files typically aren't given execute permissions by default. So, if you try running a script and bump into a permission error like "sh: 1: color: Permission denied," it means you're trying to execute a script called "color" which lacks the necessary permissions. Here, "sh" refers to the shell or command interpreter that Linux uses by default for scripts, and "1" indicates that the problem is cropping up right at the first line.
Solution: To fix this, simply run the command "chmod +x color". This command adjusts the file's settings so you can execute it. If your script is named something other than "color," just swap out "color" for whatever your script's name is.
Also, make sure to insert this line at the top of your script: "#!/bin/python" — it's the path to the Python interpreter on your system and it tells the shell exactly how to run your script.
If you still run into some issues, provide more details, please.

Thank you for letting me know! I tried running the command that you provided and I also added "#!bin/python" at the top of my script. However, I still see the error (see the first image below for the error and the second image for a section of my code). I am using Python 3.11.6, the latest version. The operating system of my PC is Windows 11 but I installed the Kali Linux terminal as a partition on my disk, which is what I am using to run my program. As I mentioned before, my script works. I am just wondering if there is a way to make it so the "sh: 1: color: Permission denied" message does not show. Also, I am coding a Discord bot in case you are wondering.

Issue Explained: The problem stems from the 22nd line in your script: os.system('color'). The os library, part of Python's standard offerings, facilitates lower-level operating system interactions. In your case, you're using the python3 command typical on Kali Linux, which is based on CPython. This command utilizes the system() function from C's stdlib.h, creating a sub-process that executes a shell command specified as a string.
On Unix-like systems, such as Kali Linux, this results in the execution of /bin/sh -c . This is why you see "sh" errors even if you're using a ZSH shell. On Windows, it corresponds to running cmd.exe /C .
The output of the function depends on the underlying operating systems (as the system() command really just calls the OS API, for instance, the "CreateProcess" function which is part of the Windows API, or function such as, "fork()", "exec()" and other function for Unix-like systems). Therefore, the fact that it is on a different partition doesn't seem to matter much.
Why the Error Happens: It's not entirely clear why you're using the command "color", but you've given enough details to figure out what's wrong. In Windows, "color" is a built-in command in cmd.exe, and running it there won't cause any issues. However, in Unix-like systems (like Kali Linux), there is no "color" command, which means trying to run it will just lead to an error.
That said, it seems like you're not attempting to use a built-in command. Given the context, it makes sense that you're trying to execute a script named "color". If "color" is a script in your PATH but doesn't have execute permissions, trying to run it would result in the error "sh: 1: color: Permission denied". If it wasn’t in your PATH at all, you'd probably see "sh: 1: color: not found" instead.
You also mentioned that your script continued to work despite the error. This happens because if a command outputs to stderr or stdout, that output will appear in the Terminal, but no exception will be raised. In fact only the return value of the function "os.system" will change to reflect the error (e.g., 32512 for "sh: 1: color: Permission denied").
If you have some file named "color" that you're trying to execute, then make sure to supply it with execute permissions (note that your "main.py" file doesn’t need to be executable since you’re running it directly with the "python3" command; you don't need to use "./main.py" to execute it.).
Further notes:
If you run a Python script in the following way: "python3 ", then it's okay if the file doesn't have an execute permission. By giving the script (in your case, "main.py") the execute permission and adding the line "#!/bin/python" at the top, it is possible to run the script in the following way: "./" (if you're in the same directory of the script, otherwise, add it to the PATH or specify the relative/absolute path to it).

Thanks @L01i74 for the explanations, closing as not a termcolor issue.

Thank you for letting me know!


Hack Session 587 ✼ Remotely

02.08.2023
Wrap-up of our Gōng-fu I/O Weekly · Hack Session #587  ✼ Remotely ✼ meetup.
Projects
• Svelte, SvelteKit — @olange and @ColasDroin
• ‹Bouboucle› generative art with Javascript — @andreaskundig and @david-hodgetts
See also

#586 Previous session
#588 Next session

Feedback on session #587 of @ColasDroin and @olange
TODO
See also

#575 Previous feedback


.aar is missing

The libraries for manual installation are missing.
https://github.com/Estimote/Android-SDK/blob/master/EstimoteSDK/estimote-sdk.aar

Hi @DogFive
That's true - currently we are not delivering our SDK as a single package to be downloaded manually. As for now, the only supported way to get our SDKs is to use JCenter repository.
This is because we are  just switch to new SDK/Libraries structure which (we hope) will be easier and much more pleasant to be used. I'm sure we'll resume manual installation support for our new SDKs bundles, however I cannot provide you any exact date when it will  happen - just stay tuned :).
In  the meantime you can download our artifacts straight from JCenter repo - the latest version is available here:
https://jcenter.bintray.com/com/estimote/sdk/1.4.0/
Regards
Wojtek


feat: New tool to Google Search

Related to #199
Motivation: SerpAPI is very expensive and scrapping can cause problems.
Solution: Implemented the new Google search API done through the Programmable search engine.
It is a bit longer to set up but worth it as it gives 10,000 search queries per day for free.
Instructions:
1. Install google-api-python-client
- If you don't already have a Google account, sign up.
- If you have never created a Google APIs Console project,
read the Managing Projects page and create a project in the Google API Console.
- Install the library using pip install google-api-python-client
The current version of the library is 2.70.0 at this time
2. To create an API key:
- Navigate to the APIs & Services→Credentials panel in Cloud Console.
- Select Create credentials, then select API key from the drop-down menu.
- The API key created dialog box displays your newly created key.
- You now have an `API_KEY`

3. Setup Custom Search Engine so you can search the entire web
- Create a custom search engine in this link.
- In Sites to search, add any valid URL (i.e. www.stackoverflow.com).
- That’s all you have to fill up, the rest doesn’t matter.
In the left-side menu, click Edit search engine → {your search engine name}
→ Setup Set Search the entire web to ON. Remove the URL you added from
 the list of Sites to search.
- Under Search engine ID you’ll find the `search-engine-ID`.

4. Enable the Custom Search API
- Navigate to the APIs & Services→Dashboard panel in Cloud Console.
- Click Enable APIs and Services.
- Search for Custom Search API and click on it.
- Click Enable.
URL for it: https://console.cloud.google.com/apis/library/customsearch.googleapis
.com
Adapted from: Instructions adapated from https://stackoverflow.com/questions/37083058/programmatically-searching-google-in-python-using-custom-search

[X] Implementation
[X] Tests, Inline Docs, Formatting
[ ] Add it to load_tools.
[ ] Improve external documentation

I think it still needs some general work here. Has been a while since I've coded in Python. I tried my best to follow the steps provided in the resources.

Is this feature now released? I don't see any references to it in documentation.


Self-Referential Types in Redb Wrapper

I am facing an issue while trying to create a wrapper for the redb library to automate some table creation and insertion tasks. I am attempting to use WriteTransaction and Table within the same structure, which leads to a self-referential type that causes problems.
Here's an example of the structure UseTransaction with WriteTransaction and Table as fields:
...
struct UseTransaction<'db, 'txn> {
    txn_write: WriteTransaction<'db>,
    cache_table: Option<Table<'db, 'txn>>,
}

impl<'db,'txn> UseTransaction<'db,'txn> {
    fn open_table(&'txn mut self) { // I need to specify 'txn here, otherwise I get the error "lifetime may not live long enough" for &mut self.
        let table = self.txn_write.open_table();
        self.cache_table = Some(table);
    }
}
...

The issue is that this generates an exclusive borrow of UseTransaction<'db> which makes it unusable afterward and conflicts with the Drop method of Table ./src/table.rs#L177-L180.
Here's a simulation of what happens when using the redb types: Rust Playground.
I request advice on resolving this issue or alternative approaches to achieve the goal.

Related topics: Lifetime error with nested struct (redb::WriteTransaction)

Table borrows the WriteTransaction and Rust does not allow self referential structs, so I don't think that is possible. You will have to split it into two wrapper structs: one for Table and one for Transaction


feat: add empty sets support

@larkee, implementing a small feature. Most of the dialects do the very same things to get an empty set casted to a particular type.


JS Error thrown on desktop when exiting VR

Load any A-Frame site in Firefox w/ WebVR Enabler Add-on
Enter VR
Exit VR
Notice these JS errors:

TypeError: window.screen.orientation is undefined aframe.min.js:30:9216
NotSupportedError: Operation is not supported

I noticed this last week but forgot to file. We simply need to check for window.screen before calling window.screen.orientation.

fixed by #731


Add support for Python 3.7 and Django 2.1

I had to adjust one minor issue with login views, but this only affected the tests.
The tests expect the warning issued by SelectRelatedMixin now and test for it.  Before the warnings were printed which let me believe that the tests where outdated which was not the case.
This also adds django master to the test matrix to capture incompatibilities as early as possible.

@kennethlove Can you push the missing tags (1.10+) to github?

By now Django 2.0 has reached its EOL and Django 2.2 LTS is available.
@kennethlove Any change to get this merged?  If so, I would add Django 2.2 to the test matrix as well.

Sorry for the delay (what an understatement). Thank you very much for the PR and the work you did! I've used it, in part, in the work I'm doing for the next version of django-braces.
Please submit a new PR adding yourself to the CONTRIBUTORS.md file.


[JavaScript] Add Echo-Proxy Bot sample

#minor
Description
This PR adds a new sample for Javascript_nodejs that shows how to configure the proxy settings to run the bot behind a proxy.

NOTE: The bot uses botbuilder version 4.22.1 because it contains the changes to use the proxy settings from ConnectorClientOptions.

Proposed Changes

Added the new sample echo-proxy-bot.
Added a README file with the instructions to configure the proxy settings.

Testing
These images show the bot working and the requests routed to the proxy's port.

/promoted 3944


Support length/substring/concat functions for string type

Reference to doc of neo4j: https://www.tutorialspoint.com/neo4j/neo4j_string_functions.htm

Fixed in #364


Move section-local image into section folder

Originally posted by @chalin in https://github.com/open-telemetry/opentelemetry.io/pull/5480#pullrequestreview-2411986003

@DIANAAJAMBO: move the image added by this PR to content/en/docs/concepts/instrumentation.

@chalin I have moved the image and here is the new PR #5523 . Thank you

Thanks @DIANAAJAMBO. I've added my comments to the new PR.


Removing unnecessary parenthesis

This is simply removing unnecessary parenthesis from various places. This change is because of a change to the unnecessary_parentesis lint that will trigger there. Here is the CL https://dart-review.googlesource.com/c/sdk/+/390161.

https://github.com/dart-lang/linter/issues/4996

Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[ ] I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
[x] All existing and new tests are passing.

If anything else is needed please let me know.
I'd like to ask for this PR to wait a bit until the bots are run again on that CL so that I can be sure nothing else will trigger, I will come back here and update this whenever everything is complete. Thanks!

I'm holding off on merging per the description:

I'd like to ask for this PR to wait a bit until the bots are run again on that CL so that I can be sure nothing else will trigger, I will come back here and update this whenever everything is complete. Thanks!

Sorry I forgot to mention here! I did mention on the issue itself, but anyway.  The last run showed me that everything is triggering the same way as this PR and that I could merge this. Thanks for the help!


More flake8 plugins

Expected behaviour
The development of the new plugin should be as easy as possible. Some of this can be achieved with a good set of Flake8 plugins.
Current behaviour
There are few plugins, but there could always be more...
Additional context
Here is a list of some of the useful plugins:

flake8-print
flake8-tidy-imports
flake8-comprehensions
flake8-simplify
flake8-pytest-style
flake8-pie

@LKajan, what do you think?

We sure can add some more flake8 checks. I don't think the overhead of flake8 plugins is too much. I would still consider if the plugin is more just a personal preference or if it really helps to write better quality code.
From the proposed list of plugins I might question the usefullness of tidy-imports and maybe pie. And would probably add flake8-builtins, flake8-mutable, flake8-docstrings.
Here's a nice list of plugins that might be useful https://github.com/DmytroLitvinov/awesome-flake8-extensions. All the proposed plugins are on the list.
Maybe we could add a parameter to cookiecutter generation "Add code quality checks [Recommended, Minimal, None]".

Great idea! What do you propose to be included on each level of quality checks?


Reorder aggregate-report Steps

This PR re-orders a few steps in the aggregate-report pipeline. Most notably it moves link validation to the end of the pipeline run as this check is always safe to run but it failing early in the pipeline prevents other checks from being able to run. Additionally, the component governance check is modified to only run when building all libraries passes as it requires the most up-to-date version of the libraries.

/azp run java - aggregate-reports

/azp run java - aggregate-reports


Update for Jetty 9.3.0

Jetty 9.3.0 is the latest update of Jetty with some API changes.

Update InstrumentedConnectionFactory to support instrumentation for Jetty 9.3.
The update should be backward-compatible with Jetty 9.1 and 9.2, because we only implement a new method.

The obvious downside is that we can't run tests under Java 7, because Jetty 9.3.0 is compiled against Java 8.

I'd like to be able to run tests against Jetty 9.2 and Java 7.  Any idea how we can make that happen?

What do you think about using reflection to access the ConnectionFactory#getProtocols method?
We keep Java 7 compile-time dependency, and in the same time comply with Jetty 9.3.* in runtime.

Ping. @ryantenney, could you take a look, please?

Just found this while trying to figure out why my app was failing when I tired to use Jetty 9.3.
Any news when this will be merged?

@arteam is this good to merge now?

Yes, the patch should be good to merge. Last time I checked, it worked both on Jetty 9.2.* and Jetty 9.3.*.

And Java7?

I didn't check against Java 7, but the tests passed on Travis CI. I used reflection precisely for the reason to avoid any Java 8 dependency.

I've created #1037 to backport this feature to the 3.2 branch. For the 4.0.0 branch we can actually just avoid reflection and just implement a new method.

The implementation for 4.0.0 is tracked in #1039.


Update to Alpine 3.18

See also https://alpinelinux.org/posts/Alpine-3.18.0-released.html.

Nice....now millions of pipelines using still docker-compose won't run anymore.

Nice....now millions of pipelines using still docker-compose won't run anymore.

I'm not sure what you mean by this, docker compose is still functional in the new image AFAICS:
$ docker container run --rm docker:cli /bin/sh -c docker-compose --help
Usage:  docker compose [OPTIONS] COMMAND

Docker Compose

Options:
      --ansi string                Control when to print ANSI control
                                   characters ("never"|"always"|"auto")
                                   (default "auto")
      --compatibility              Run compose in backward compatibility mode
      --env-file stringArray       Specify an alternate environment file.
  -f, --file stringArray           Compose configuration files
      --parallel int               Control max parallelism, -1 for
                                   unlimited (default -1)
      --profile stringArray        Specify a profile to enable
      --project-directory string   Specify an alternate working directory
                                   (default: the path of the, first
                                   specified, Compose file)
  -p, --project-name string        Project name

Commands:
  build       Build or rebuild services
  config      Parse, resolve and render compose file in canonical format
  cp          Copy files/folders between a service container and the local filesystem
  create      Creates containers for a service.
  down        Stop and remove containers, networks
  events      Receive real time events from containers.
  exec        Execute a command in a running container.
  images      List images used by the created containers
  kill        Force stop service containers.
  logs        View output from containers
  ls          List running compose projects
  pause       Pause services
  port        Print the public port for a port binding.
  ps          List containers
  pull        Pull service images
  push        Push service images
  restart     Restart service containers
  rm          Removes stopped service containers
  run         Run a one-off command on a service.
  start       Start services
  stop        Stop services
  top         Display the running processes
  unpause     Unpause services
  up          Create and start containers
  version     Show the Docker Compose version information

Run 'docker compose COMMAND --help' for more information on a command.

Indeed, a little elaboration would be helpful :sweat_smile:

Sorry. Yes. What you mean, is the "new" docker compose....this is indeed in there.
My CI pipelines were still using docker-compose, so they stopped working. The switch to docker compose was a no-brainer of course, but we have multiple services relying on a gitlab-ci template, that is using this command for creating an environment for integration testing.
Here you go for some context:
$ apk add --no-cache docker-compose
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
ERROR: unable to select packages:
  docker-compose (no such package):
    required by: world[docker-compose]

I understand the confusion now! When running apk add --no-cache docker-compose, you are actually installing the (old v1) docker-compose binary from the Alpine package registry; however, the docker-compose plugin is already pre-installed in this image, so installing it is unnecessary.
The issue is this package is removed from Alpine as docker compose v1 is no longer supported. Note this is mostly unrelated to the docker-compose vs. docker compose syntax change, as the new v2 version still also support using docker-compose (see also my example above).
So my guess is you can remove the apk add --no-cache docker-compose from your workflow and everything should be working exactly as before, since the binary installed by apk was most likely ignored before. Alternatively, if you really need the v1 binary, you could just use alpine:3.17 as base image and install the old package (see https://pkgs.alpinelinux.org/package/v3.17/community/x86_64/docker-compose); the new binary is now installable through the docker-cli-compose package (see https://pkgs.alpinelinux.org/package/v3.18/community/x86_64/docker-cli-compose).
Tl;dr: remove apk add --no-cache docker-compose and you should most likely be fine.

All cool. As I said, I just removed the "-" from the lines in the gitlab-ci.yaml and removed the line, where the docker-compose apk was installed. So it's better then before, but some of us run in circles in panic, as we first need to find out what was wrong/what has changed ^^

Just to thread the needle all the way back, https://github.com/docker-library/docker/pull/361 is where docker-compose was added to the image. :blush:


Modify Give command to handle currency

Be able to give other players currency!

It is done. We might also want to modify the 'load' command to load currency.


More Aggresive Autoderiving of Traits

Tracking: https://github.com/rust-lang/rust/issues/31844
Once we have some form of negative reasoning, it should be possible to automagically derive ElasticType for mapping types that implement one of the Elastic*Mapping traits.
That'll eliminate some boilerplate, and make it impossible to implement a mapping type for more than a single Elasticsearch type.
How this plays out for object mapping is a different story, but object mapping meta is usually less important than the mapping of the fields it contains.

Ideally, we'd like to be able to do this:
#![feature(optin_builtin_traits)]

//Traits
trait FieldMapping<F> { }

trait DateFormat { }
trait DateMapping {
	type Format: DateFormat;
}

impl <T: DateMapping<Format = F>, F: DateFormat> FieldMapping<F> for T {

}

trait GeoFormat { }
trait GeoMapping {
	type Format: GeoFormat;
}

impl <T: GeoMapping<Format = F>, F: GeoFormat> FieldMapping<F> for T {

}

struct BoolFormat;
trait BoolMapping { }

impl <T: BoolMapping> FieldMapping<BoolFormat> for T { }

struct IntFormat;
trait IntMapping { }

impl <T: IntMapping> FieldMapping<IntFormat> for T { }

//Impls
struct DateFormatImpl;
impl DateFormat for DateFormatImpl { }

struct DateMappingImpl;
impl DateMapping for DateMappingImpl {
	type Format = DateFormatImpl;
}

struct BoolMappingImpl;
impl BoolMapping for BoolMappingImpl { }

The issue currently is that FieldMapping<_> is considered a duplicate implementation for FieldMapping<T: DateFormat> and FieldMapping<T: GeoFormat>.

Interestingly, this does work:
//Traits
trait FieldMapping<F> { }

trait DateFormat { }
struct DateFormatMarker<F: DateFormat> {
	_marker: ::std::marker::PhantomData<F>
}
trait DateMapping {
	type Format: DateFormat;
}

impl <T: DateMapping<Format = F>, F: DateFormat> FieldMapping<DateFormatMarker<F>> for T {

}

trait GeoFormat { }
struct GeoFormatMarker<F: GeoFormat> {
	_marker: ::std::marker::PhantomData<F>
}
trait GeoMapping {
	type Format: GeoFormat;
}

impl <T: GeoMapping<Format = F>, F: GeoFormat> FieldMapping<GeoFormatMarker<F>> for T {

}

struct BoolFormat;
trait BoolMapping { }

impl <T: BoolMapping> FieldMapping<BoolFormat> for T { }

struct IntFormat;
trait IntMapping { }

impl <T: IntMapping> FieldMapping<IntFormat> for T { }

//Impls
struct DateFormatImpl;
impl DateFormat for DateFormatImpl { }

struct DateMappingImpl;
impl DateMapping for DateMappingImpl {
	type Format = DateFormatImpl;
}

struct BoolMappingImpl;
impl BoolMapping for BoolMappingImpl { }

fn main() {}

I think I'll have to ponder this some more...

For object mapping, the properties serialisation should be separate, so we can auto derive that with the procedural macro, and support the scebario where someone wants to map the same type multiple times but differently, like so:
struct SubType<M: ObjectMapping> {
    ...
}

struct ParentType1 {
    pub field: SubType<SubTypeMapping1>
}

struct ParentType2 {
    pub field: SubType<SubTypeMapping2>
}

We don't want to have to implement the property serialisation for this type twice to support mapping as object in one place and nested in another.

We're also going to need to pull the type name out into its own trait, so if a user provides #[elastic(mapping="MyMapping", ty="my_type")], then we should implement NamedMapping (or something) with "my_type", and let the user implement ObjectMapping for MyMapping.
Otherwise the behavior is going to be weird and unpredictable. It does mean more code to implement mapping, but with stable auto derive on the way this shouldn't be too much of a problem.

Actually this is totally not necessary. If you need to rename the type, you'll just have to provide an implementation of ObjectMapping yourself and use it in the mapping attribute. It keeps the API simple.
Using already existing mapping types is the next thing that needs to be reimplemented.

If possible, we should be implementing Deref for our wrapper types (so FieldMappingWrapper and stuff like Date).
That way we can be more transient about what type we're actually using.


⚠ Bofrost.at has degraded performance

In 8d308b0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2090 ms

Resolved: Bofrost.at performance has improved in 6810158 after 8 minutes.


Padrino::Cache::Helpers::Page Content-Type Issue

store both response_buffer and content_type in cache; tests fix

Why no one of these pull requests was merged?

This one will be merged soon, thanks

Merged: https://github.com/padrino/padrino-framework/commit/8f746e0ec8e9225400efaf4cf3b1c86c20011c82
Thanks!


Fixes Issue#82 Brand Logo added on navbar in Explore/index.php page and navbar enhanced.

Previously brand logo was missing on navbar in Explore/index.php and list items gets fade out on small screen.

Now navbar looks like :

@rupeshmohanty Please mention the level of issue(i.e. level 2) on this PR. And kindly review it.

@ishubham21 Done changes as requested.


System.Globalization.NumberFormatInfo.get_CurrentInfo is not compiled

Run:
Console.WriteLine(123.ToString());
will he following stack
#0  0x00007ffff6c01cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007ffff6c050d8 in __GI_abort () at abort.c:89
#2  0x00007ffff7b36535 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00007ffff7b346d6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007ffff7b34703 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007ffff7b34922 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x000000000044fd51 in System_Private_CoreLib::System::Globalization::NumberFormatInfo::get_CurrentInfo () at obj/Debug/dnxcore50/native/Hello.cpp:25581
#7  0x00000000004562f1 in System_Private_CoreLib::System::Globalization::FormatProvider_Number::FormatInt32 (value=123, format=0x0, provider=0x0) at obj/Debug/dnxcore50/native/Hello.cpp:27618
#8  0x0000000000404ea4 in System_Private_CoreLib::System::Globalization::FormatProvider::FormatInt32 (value=123, format=0x0, provider=0x0) at /home/tarek/oss/corert/tests/src/Simple/Hello/Hello.cs:1267
#9  0x00000000004054fd in System_Private_CoreLib::System::Int32::ToString (_this=0x7fffffffddf4) at obj/Debug/dnxcore50/native/Hello.cpp:5837
#10 0x000000000048f38a in Hello::Program::Main (args=0x7fffdebcb060) at /home/tarek/oss/corert/tests/src/Simple/Hello/Hello.cs:11
#11 0x000000000048f0ea in Hello::Module::StartupCodeMain (_a0=0, _a1=140737488346992) at obj/Debug/dnxcore50/native/Hello.cpp:45085
#12 0x00000000004aa73c in main (argc=1, argv=0x7fffffffdf68) at /home/tarek/oss/corert/tests/src/Simple/Hello/Hello.cs:7311

It is failing because of the following line requires reflection that is not hooked up yet:
formatProvider.GetFormat(typeof(NumberFormatInfo))

@tarekgh There are already workarounds checked in for other cases when reflection blocks a scenario. If it's blocking you, please check in a workaround with a TODO. If it's not blocking you, I see little point in filing bugs for all the code paths that can potentially call into reflection (I recommend we close this).

I will take a look at implementing the workaround

thanks @jkotas. I'll try to test my changing without hitting any of such code paths. it is so far not really blocking. if you are going to check in a workaround, it'll be nice to do the work around for the stringBuilder case as it is used by many code paths. thanks for looking at that.


CLI Improvements and Bugfix

Fix issue where files wouldn't compile properly when using the CLI
Adds the option to specify the port the server will be hosted at
Missing optional files won't fail the CI build
Catch KeyErrors caused by the CI check

Coverage decreased (-0.3%) to 60.447% when pulling daec0778716572fc4b136c250b9073377deaa345 on allow-missing-optional-files into 8b0e2bce58724df00d646d4ac99e3206a4cd8a41 on master.

I think we'll be ready for another release soon. Maybe at the beginning of next week in case I find anything else to add/fix this weekend?

Sure


TypeError: Components.classes is undefined in background.js:6:9

TypeError: Components.classes is undefined
background.js:6:9

I found this: https://stackoverflow.com/questions/21378058/why-components-classes-is-undefined

Fixed on master, solution was to use browser.history instead.


Fixed Cloudflare DNS name

Cloudflare DNS is spelled "Cloudflare" not "Cloud Flare"

Actually cloudflare is always one word https://www.cloudflare.com/
This is the first time I've seen it separated.

Actually cloudflare is always one word https://www.cloudflare.com/
This is the first time I've seen it separated.

He fixed it

Actually cloudflare is always one word https://www.cloudflare.com/
This is the first time I've seen it separated.

I am aware of this? Your script has it seperated? I fixed this in my pull request


Local web build fails with no Internet connection

Where to find the issue
This repository https://github.com/corona-warn-app/cwa-website.
Describe the issue
Attempting to build a local copy of the web to test, when no internet connection is available, fails with an error message:
FetchError: request to https://obs.eu-de.otc.t-systems.com/obs-public-dashboard/json/v1/nested_cwa_public_dashboard_data.json failed, reason: getaddrinfo ENOTFOUND obs.eu-de.otc.t-systems.com
Another error occurs if there is an internet connection but the json file cannot be fetched fast enough. Unfortunately I didn't save this error message. The error message is something like public//analyseData.json not found.
Steps to reproduce

On a local system enable flight mode i.e. no internet connection
Type npm start at a bash command prompt

$ npm start

><EMAIL_ADDRESS>start C:\Users\mikem\github\cwa-website
> gulp

[19:04:49] Using gulpfile ~\github\cwa-website\gulpfile.js
[19:04:49] Starting 'default'...
[19:04:49] Starting 'build'...
[19:04:49] Starting 'clean'...
[19:04:49] Finished 'clean' after 15 ms
[19:04:49] Starting 'cleanBlogs'...
[19:04:49] Finished 'cleanBlogs' after 83 ms
[19:04:49] Starting 'cleanScienceBlogs'...
[19:04:49] Finished 'cleanScienceBlogs' after 5.5 ms
[19:04:49] Starting 'buildBlogFiles'...
[19:04:50] Finished 'buildBlogFiles' after 681 ms
[19:04:50] Starting 'buildScienceBlogFiles'...
[19:04:50] Finished 'buildScienceBlogFiles' after 352 ms
[19:04:50] Starting 'analyseData'...
[19:04:50] 'analyseData' errored after 85 ms
[19:04:50] FetchError: request to https://obs.eu-de.otc.t-systems.com/obs-public-dashboard/json/v1/nested_cwa_public_dashboard_data.json failed, reason: getaddrinfo ENOTFOUND obs.eu-de.otc.t-systems.com
    at ClientRequest.<anonymous> (C:\Users\mikem\github\cwa-website\node_modules\node-fetch\lib\index.js:1483:11)
    at ClientRequest.emit (events.js:400:28)
    at ClientRequest.emit (domain.js:470:12)
    at TLSSocket.socketErrorListener (_http_client.js:475:9)
    at TLSSocket.emit (events.js:400:28)
    at TLSSocket.emit (domain.js:470:12)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
[19:04:50] 'build' errored after 1.23 s
[19:04:50] 'default' errored after 1.23 s

Expected behavior
It should be possible to build the web reproducibly using a clone of the repository without downloading any dynamic information from another source, therefore it should be possible to build the web without an internet connection.
Suggested change
Remove the reliance on accessing a remote file during build which is not part of the committed git controlled repository on https://github.com/corona-warn-app/cwa-website.

@MikeMcC399 without fetching the dynamic data for the analysis dashboard, the dashboard will not work on local dev env.

@FabioFuschi-SNK

without fetching the dynamic data for the analysis dashboard, the dashboard will not work on local dev env.

I understand that the dashboard needs dynamic data. I don't understand though why that must be part of the build process.
Is it possible to pull the dynamic data in real time after the web is started instead of making it part of the build?
If the data is only downloaded when the web is built, what happens to data updates which happen days later?


Failed assertion

Hello, I received a bug and got the following message encouraging me to report here, so I am:
======== Exception caught by widgets library =======================================================
The following assertion was thrown building Navigator-[GlobalObjectKey _WidgetsAppState#589fe](dirty, dependencies: [UnmanagedRestorationScope, HeroControllerScope], state: NavigatorState#548b9(tickers: tracking 4 tickers)):
'package:flutter/src/widgets/navigator.dart': Failed assertion: line 5307 pos 12: '!_debugLocked': is not true.
Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=2_bug.md
The relevant error-causing widget was:
MaterialApp file:///D:/AndroidStudioProjectsAndAssets/projectapp/lib/main.dart:42:20
When the exception was thrown, this was the stack:
#2      NavigatorState.build (package:flutter/src/widgets/navigator.dart:5307:12)
#3      StatefulElement.build (package:flutter/src/widgets/framework.dart:4691:27)
#4      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4574:15)
#5      StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:4746:11)
#6      Element.rebuild (package:flutter/src/widgets/framework.dart:4267:5)
...

Do you have a reproducible sample? And what is the flutter doctor -v?

Hi @stfn3000
Can you please provide your flutter doctor -v, a complete reproducible minimal code sample, and complete flutter run --verbose logs running the minimal code sample?
Thank you


Four 'new' signs

About the PR

Added four signs that are from /tg/.
Why / Balance

Mostly to allow an easier time finding the custodian/janitor, psychologist or lawyer office/court.
Technical details

N/A
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

Mostly dependant on mappers adding it to their map so no changelog

We don't refer to the janitor in-game as "custodian" so this abbreviation might be a bit confusing, especially for non-native speakers. This would be better changed to "JANI", in which case you should double check this doesn't duplicate an existing sprite.

in which case you should double check this doesn't duplicate an existing sprite.

We don't have a poster-sized Jani yet, and we could really use one!

5000 years in photoshop

wooo signs my beloved


Updated AspNet.Identity.Mongo from 2.0.4 (pre) to 2.0.8 (stable)

rebasing

I think the examples should stay as is, the update to 2.0.8 doesn't contribute to the understanding provided by the example.

Okay, but the example doesn't build because NuGet is unable to restore the 2.0.4-alpha package.

Ahh, that makes sense, didn't know they yanked the package. Will you remove
the references to EntityFramework? EntityFramework and
Microsoft.AspNet.Identity.EntityFramework
On Mon, Aug 24, 2015 at 6:17 PM, Vincent Kyle Eusebio <
<EMAIL_ADDRESS>wrote:

Okay, but the example doesn't build because NuGet is unable to restore the
2.0.4-alpha package.
—
Reply to this email directly or view it on GitHub
https://github.com/g0t4/aspnet-identity-mongo-sample/pull/2#issuecomment-134397833
.


Autonominous integration with TravisCI

I plan to work on this issue

Please see the following (pull request)[https://github.com/hibyguy/Throwable-RESTful-API/pull/8]


No actual data from mock (only with variables)

Hello,
I have an issue with this code (v0.8.1):
mockServer(executableSchema, mocks).query(query, variableValues);

This works fine instead:
mockServer(executableSchema, mocks).query(query);

I only removed the variableValues argument.
I followed the example here.
The issue is that, if I don't pass the variableValues argument above, query responses contain data.
If I pass the variableValues argument, instead, query responses do not contain any actual data (but just an empty-ish errors array, which wasn't there before).
This is surprising, because I sent the same queries using GraphiQL, and I only tried to add or remove the variables.
Example query:
{
  allUsers {
    nodes {
      __id
    }
  }
}

Results without arguments:
{
  "data": {
    "allUsers": {
      "nodes": [
        {
          "__id": "600a76ed-c1e8-4443-a297-dce44c07730a"
        },
        {
          "__id": "25f4b824-46d6-4daf-88b7-9c43e9a1b2cd"
        }
      ]
    }
  }
}

Results with {"input": "foo"} as argument:
{
  "errors": [
    {}
  ]
}

I omit the schema.
I'll also share some findings.
mockServer calls a function from graphql-js at this line.
The graphql-js function that gets called is defined at this line.
Could the issue be related to graphql-js instead?
Thanks

@josieusa sorry for the slow reply. I think this might be an issue with the formatError function, not with mockServer. In your example the query doesn't have a variable named input, which means that validation will fail ("unused variable 'input'").
I'm not sure why the error message isn't there. What version of graphql-js are you using?

Closing this because there hasn't been any activity in a while.


Add salvage option for any drops that can give conset materials

Now that items have salvage results info, is there a chance to turn salvage kits into their ultimate form by adding a new option to only salvage items that give conset materials regardless of item rarity, could be named: "Salvage into conset materials". This way it adds a single extra option and not 4 (one for each rarity).

Main points here are that salvage kits are inexpensive, salvaging all items whilst giving a checkbox list as it is at the moment frees up inventory space, and material value of items salvaged is usually more valuable than the item itself.
The only benefit to your approach would be saving salvage uses, and you’ll end up wanting to salvage more than that for the reasons mentioned above


[1.12.2] 1.12.2 FTB Utilities Server Crash & bqforestry-1.1.3b

Getting a server crash on the new version.
Forge 2847
FTB Util <IP_ADDRESS>
bqforestry-1.1.3b
Crash log: https://pastebin.com/xW26NPDq
Full mod list: https://pastebin.com/xZb8nTjg
https://github.com/FTBTeam/FTB-Utilities/issues/1042

The issue was a piece of code calling for a client only method. It should be resolved in <IP_ADDRESS>b, going up on CurseForge now. Let me know if your issue is resolved!

Thx, I'll let you know


highlight is incorrect

I want to highlight LESS
but I get the backlight another language :(
what am I doing wrong?
http://codepen.io/nicothin/pen/MbBXYx?editors=1000 — example

You're using a CDN-hosted build of highlight.js which only contains a dozen of common languages, and Less is not one of them. Either get yourself a custom build with all the languages you need from https://highlightjs.org/download/ or include a separate Less definition from the same CDN:
<script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.8.0/languages/less.min.js"></script>

And make sure to read through README :-)


Use aiohttp._parser for client response parsing

Should be relatively easy to add aiohttp._parser.HttpResponseParser implementation
anyone want to work on this?

I can work on it
El 16/02/2017 02:10, "Nikolay Kim"<EMAIL_ADDRESS>escribió:

Should be relatively easy to add aiohttp._parser.HttpResponseParser
implementation
anyone want to work on this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/KeepSafe/aiohttp/issues/1641, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABK1iZHZb6RkKkaRzqs0Un6MOqaE02NVks5rc6IagaJpZM4MCdZ_
.

it is in master already. it was easier than i excepted. thanks anyway


ccp_nodemx_data_disk pq: value "18446744073709551615" is out of range for type bigint

Hi,
We have an OpenShift cluster with CrunchyData postgres-operator with enabled prometheus metrics. In the export container we have found the following error:
time="2021-09-20T07:27:57Z" level=info msg="Error running query on database "<IP_ADDRESS>:5432": ccp_nodemx_data_disk pq: value "18446744073709551615" is out of range for type bigint" source="postgres_exporter.go:1356"
I found that the monitor.fsinfo() function provides this data. For fsinfo('/') I got proper data, but for fsinfo('/pgdata') I got the number is too big for bigint like above.
We use rook-ceph for persistent volumes. Probably ceph cannot provide this data or reach a limit, maybe selinux didn't allow to collect something. Please help me what is wrong here.
Environment

Platform: OpenShift
Platform Version: 4.7.0
PGO Image Tag: centos8-12.8-4.7.2
Postgres Version: 12
Storage: rook-ceph

Steps to Reproduce
REPRO
Create cluster with metrics enabled.
EXPECTED
No error, metrics collection.
ACTUAL
ccp_nodemx_data_disk pq: value "18446744073709551615" is out of range for type bigint
Additional Information
Recently we upgraded our postgres operator from 4.5.1 to 4.7.2 but I found the same in the old logs as well.

Sorry for the delay, but we will have a fix committed and new release out shortly.

Sorry for the delay, but we will have a fix committed and new release out shortly.

Thank you for your response. What does shortly mean? :) Days, weeks, ...

Thank you @pgguru. Can you tell me when it will be in the postgres operator? Will I find it in the next release?

@douggutaby The folks who work on pgnodemx are independent from those on the Postgres Operator. They do not know when it will be released in that project.
For PGO releases, information is shared on the mailing list, which can be found here: https://access.crunchydata.com/documentation/postgres-operator/v5/support/


[feat] build chromium with vanadium patches

Increasingly, new hardening changes are needed in the form of code changes and can't be sufficiently replicated with config or policy changes.

Maybe you can kang some old ones from Hexavalent
https://github.com/Hexavalent-Browser/Hexavalent-Archive

@TommyTran732 those are largely just a subset of the vanadium ones I believe.
The time consuming part here is the CICD. Pulling in patches is the easy part :smile:

I'm working on it here https://github.com/qoijjj/chromium-copr-experimental

Oh yeah, speaking of which, is there a reason why you don't bring these to the secureblue namespace?
I mean, you have the builds under secureblue on copr, but the source is on your personal

@TommyTran732 what? All of the rpm specs currently shipped in secureblue are in the secureblue organization https://github.com/orgs/secureblue/repositories
I'm currently playing around with this in a sandbox repo in my personal account, which seems appropriate given the current stage of development. Why would I move it to the secureblue org now?

Okay fair.
Hardened Malloc is still inside of your personal account through and not the org, at least according to this: https://copr.fedorainfracloud.org/coprs/secureblue/hardened_malloc/build/7573649/

Edit:
Looks like you moved it recently but might be a good idea to update the copr to it stops referencing the old URL as well.

@TommyTran732 ah you're right, that hasn't been updated since the project moved to the secureblue repo. i'll do it now

Might be a good idea to have to have a look at this as well: https://simonwillison.net/2024/Jul/9/hangout_servicesthunkjs/
I just noticed its also in Edge's build for macOS and Linux... very jackwagon

@TommyTran732 for specific chromium hardening improvements, please open a new issue. this issue is just for tracking the effort to move to a custom build
Also, that's probably relevant to vanadium as well. Might be worth asking them.

Already did privately. Will lyk.

https://github.com/secureblue/hardened-chromium


Allow to specify the version of terraform-docs for the hook to use

Currently, terraform_docs (and similar) hooks will use the version of terraform-docs installed on the system.
With each major release of the terraform-docs the output format changes and users need to regenerate the docs.
We need to be able to pin a specific version in the hook so that we have more control over README.md.
Proposal:

Use args to define a specific version of docker image - https://terraform-docs.io/user-guide/installation/#docker

Sample:
repos:
  - repo: git://github.com/antonbabenko/pre-commit-terraform
    rev: v1.48.0
    hooks:
      - id: terraform_fmt
      - id: terraform_docs
        args: ['--version=0.12']

@bryantbiggs I just want to link this one with the PR (eg, https://github.com/terraform-aws-modules/terraform-aws-alb/pull/190 ).

Yes, this is a good option. If it would be implemented in pre-commit-terraform maybe we can also take care of installing the required version (not sure if it is a good idea though).

In my opinion, since using .terraform-docs.yml as a single source for configuration becomes more popular it makes sense to delegate these kind of configurations and restrictions to terraform-docs itself. But on the other hand installing the required version as part of the hook is gonna be very useful I think.

Can be possible to implement by https://github.com/antonbabenko/pre-commit-terraform/issues/418#issuecomment-2040209926


Is the FHIR Attachment datatype a proper implementation of ED?

Currently, the zib datatype ED is mapped to FHIR datatype base64Binary, according to the profiling guidelines. However, there are several different ways to add Encoded Data to a FHIR message. By mapping the ED datatype to Attachment, implementers can choose the preferred way (by reference, url or inline data)
If we agree that ED can be mapped to Attachment, this should be added to the profiling guidelines and to the zib compliance tool.

I think we can make a mapping of the datatype ED to Attachment. With both methods of Attachment (inline or reference), you will get to the encoded data. Shall we proceed with adding this to the guidelines and compliance tool?


AzureConnection: remove our dependency on cpprestsdk

This pull request removes, in full, our dependency on cpprestsdk. This
allows us to shed 500KiB-1.2MiB from our package off the top and enables
the following future investments:

Removal of the App CRT forwarders (this is already possible in the
Windows 11 builds) to save an additional ~500KiB
Switching over to the HybridCRT and removing our dependency on any
CRT.

cpprest was built on my dev box two or so years ago, and is in utter
violation of our compliance guidelines on SBOM et al.
In addition, this change allows us to use the proxy server configured
in Windows Settings.
I did this in four steps (represented roughly by the individual commits):

Switch from cpprest's http_client/json to Windows.Web.Http and
Windows.Data.Json
Switch from websocketpp to winhttp.dll's WebSocket implementation¹
Remove all remaining utility classes
Purge all dependencies from all projects and scripts on cpprest.

I also took this opportunity to add a feature flag that allows Dev
builds to run AzureConnection in-process.
¹ Windows.Networking.Sockets' API is so unergonomic that it was simply
infeasible (and also horrible) to use it.
Validation Steps
I've run the Azure Connection quite a bit inproc.
Closes #4575.
Might be related to #5977, #11714, and with the user agent thing maybe #14403.

gsl::narrow -> done


unable to locate sharepoint library

as O365 admin, unable to locate the site for which i want to export the site usage report in O365 admin

@bilal-docusign - May we know which Microsoft document link you used in reference to this issue?
Please share it with us so we can investigate further. Thank you.

@bilal-docusign - We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
If there is a specific area of the docs that we can improve on, please feel free to open a new issue by clicking on the Feedback section on the specific Microsoft doc which is found at the bottom of the page. Thank you.


Accessing pyaedt from IronPython Command window

To access the pyaedt from the IronPython command window, I copied the pyaedt folder from the installed location to the this folder
C:\Users....................\Documents\Ansoft\PersonalLib\pyeaedt
but I get this error message when I try to use pyaedt

What should I do now ?

Hi @SK-mechcoder
So there are a few things wrong here.  1) is that you should be posting this to the PyAEDT GitHub Issues site and not PyMAPDL.

PyAEDT is a CPython language library and not IronPython, for CPython versons 3.8-3.12.

It's normally not....let's say proper to use PyAEDT from within PyAEDT.  I suppose there could be a reason to run this way but normally we run PyAEDT from some Python development environment like Jupyter Lab or CS Studio Code etc.

3b) So part 3 is based in part on what I know of AEDT, which is very little, but more with PyMAPDL.  There are a few very specific reasons why I might run PyMAPDL from MAPDL interactive but it is not a standard procedure.
Mike


Add Python checks to Travis

Travis should run some checks to determine whether the Python shell is ready for release (unit tests, pylint/PEP8 checks etc)

I've added config to travis to run all python tests. This has been merged into develop.
I will leave this issue open as we still need to write some more tests.

We haven't added any pylint/PEP8 checks, I have opened a separate issue to do that https://github.com/gchq/gaffer-tools/issues/137.

Merged into develop.


(GH-179) Replace custom logging with serilog implementation

Description

This PR adds the implementation of using serilog instead of our custom logging class.
Related Issue

fixes #179 (Eventually when done)
Motivation and Context

How Has This Been Tested?

Locally by calling the different commands and looking at the output
Screenshots (if appropriate):
Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] All new and existing tests passed.

Tasks Checklist
Tasks left to do (of what I remember right now), will be added additional tasks when/if I come across them.

[x] Remove the Logging level prefix when outputting informational messages (Requires two console sinks to be implemented)
[x] Add additional debug logging (especially for calls to github)
[x] Move pragma suppressions to global suppresions file or remove
Add additional argument switches to control logging level (Because I don't agree with the current logging decisions implemented by Serilog. Debug > Verbose)

[ ] Add --verbose switch for enabling verbose logging
[ ] Add --debug switch for enabling debug logging

[x] Add Visual Studio debug sink (only for debug builds)

@gep13 quick question, should informational messages be outputted without the logging level?
I think it makes sense to have the logging level for Verbose,Debug,Warning,Error and Fatal. But not necessarily for Information.

I have updated the initial issue description with the remaining tasks I need to do.

Just got the --verbose and --debug switches left, then this PR would be ready for a review.

@AdmiringWorm your changes have been merged, thanks for your contribution 👍

@gep13 I seem to have forgotten 1 thing.
I was meant to also change the logger to only log stacktraces when a user is running with either --verbose or --debug switches, or do you want the stacktraces to be outputted no matter what?


identify memory leak in long-running map with random transitions

See json created by https://github.com/bdon/TileSiege

related to CanvasPool