text:
OCS status code zero

While bumping the core commit id for API tests, there is this new failure:
https://drone.owncloud.com/owncloud/ocis/11072/27/6
  Scenario: Keep usergroup shares when the user renames the share within the Shares folder(#22143) # /srv/app/testrunner/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature:32
    Given group "grp1" has been created                                                            # FeatureContext::groupHasBeenCreated()
    And user "Brian" has been added to group "grp1"                                                # FeatureContext::userHasBeenAddedToGroup()
    And user "Carol" has been added to group "grp1"                                                # FeatureContext::userHasBeenAddedToGroup()
    And user "Alice" has created folder "/TMP"                                                     # FeatureContext::userHasCreatedFolder()
    When user "Alice" shares folder "TMP" with group "grp1" using the sharing API                  # FeatureContext::userSharesFileWithGroupUsingTheSharingApi()
    And user "Brian" accepts share "/TMP" offered by user "Alice" using the sharing API            # FeatureContext::userReactsToShareOfferedBy()
    And user "Carol" accepts share "/TMP" offered by user "Alice" using the sharing API            # FeatureContext::userReactsToShareOfferedBy()
    And user "Brian" moves folder "/Shares/TMP" to "/Shares/new" using the WebDAV API              # FeatureContext::userMovesFileUsingTheAPI()
    And the administrator deletes user "Carol" using the provisioning API                          # FeatureContext::theAdminDeletesUserUsingTheProvisioningApi()
    Then the OCS status code of responses on all endpoints should be "100"                         # FeatureContext::theOCSStatusCodeOfResponsesOnAllEndpointsShouldBe()
      Responses did not return expected ocs status code
      Failed asserting that 0 is identical to 100.

This test scenario has recently been adjusted to check all the status codes. It passes in oC10 core.
First investigate if this is a test problem - maybe there is some problem with the test processing the status codes.
Then, if there is a real problem with oCIS, raise an issue about it.

@phil-davis Does that fix the problem?

@phil-davis Does that fix the problem?

https://drone.owncloud.com/owncloud/ocis/11704/43/6
  Scenario: Keep usergroup shares when the user renames the share within the Shares folder(#22143) # /srv/app/testrunner/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature:32
    Given group "grp1" has been created                                                            # FeatureContext::groupHasBeenCreated()
    And user "Brian" has been added to group "grp1"                                                # FeatureContext::userHasBeenAddedToGroup()
    And user "Carol" has been added to group "grp1"                                                # FeatureContext::userHasBeenAddedToGroup()
    And user "Alice" has created folder "/TMP"                                                     # FeatureContext::userHasCreatedFolder()
    When user "Alice" shares folder "TMP" with group "grp1" using the sharing API                  # FeatureContext::userSharesFileWithGroupUsingTheSharingApi()
    And user "Brian" accepts share "/TMP" offered by user "Alice" using the sharing API            # FeatureContext::userReactsToShareOfferedBy()
    And user "Carol" accepts share "/TMP" offered by user "Alice" using the sharing API            # FeatureContext::userReactsToShareOfferedBy()
    And user "Brian" moves folder "/Shares/TMP" to "/Shares/new" using the WebDAV API              # FeatureContext::userMovesFileUsingTheAPI()
    And the administrator deletes user "Carol" using the provisioning API                          # FeatureContext::theAdminDeletesUserUsingTheProvisioningApi()
    Then the OCS status code of responses on all endpoints should be "100"                         # FeatureContext::theOCSStatusCodeOfResponsesOnAllEndpointsShouldBe()
      Responses did not return expected ocs status code
      Failed asserting that 0 is identical to 100.
    And the HTTP status code of responses on all endpoints should be "200"                         # FeatureContext::theHTTPStatusCodeOfResponsesOnAllEndpointsShouldBe()
    And user "Brian" should see the following elements                                             # FeatureContext::userShouldSeeTheElements()
      | /Shares/new/ |

A recent oCIS CI run still has the same reason for failing.
I will find a recent reva CI run and post that also.

https://drone.cernbox.cern.ch/cs3org/reva/7058/14/6
  Scenario: Keep usergroup shares when the user renames the share within the Shares folder(#22143) # /drone/src/tmp/testrunner/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature:32
    Given group "grp1" has been created                                                            # FeatureContext::groupHasBeenCreated()
    And user "Brian" has been added to group "grp1"                                                # FeatureContext::userHasBeenAddedToGroup()
    And user "Carol" has been added to group "grp1"                                                # FeatureContext::userHasBeenAddedToGroup()
    And user "Alice" has created folder "/TMP"                                                     # FeatureContext::userHasCreatedFolder()
    When user "Alice" shares folder "TMP" with group "grp1" using the sharing API                  # FeatureContext::userSharesFileWithGroupUsingTheSharingApi()
    And user "Brian" accepts share "/TMP" offered by user "Alice" using the sharing API            # FeatureContext::userReactsToShareOfferedBy()
    And user "Carol" accepts share "/TMP" offered by user "Alice" using the sharing API            # FeatureContext::userReactsToShareOfferedBy()
    And user "Brian" moves folder "/Shares/TMP" to "/Shares/new" using the WebDAV API              # FeatureContext::userMovesFileUsingTheAPI()
INFORMATION: could not delete user 'Carol' 401
    And the administrator deletes user "Carol" using the provisioning API                          # FeatureContext::theAdminDeletesUserUsingTheProvisioningApi()
    Then the OCS status code of responses on all endpoints should be "100"                         # FeatureContext::theOCSStatusCodeOfResponsesOnAllEndpointsShouldBe()
      Responses did not return expected ocs status code
      Failed asserting that 0 is identical to 100.
    And the HTTP status code of responses on all endpoints should be "200"                         # FeatureContext::theHTTPStatusCodeOfResponsesOnAllEndpointsShouldBe()
    And user "Brian" should see the following elements                                             # FeatureContext::userShouldSeeTheElements()
      | /Shares/new/ |

It still fails the same in reva edge.

@butonic I thought we fixed it?

In the test code, $this->emptyLastHTTPStatusCodesArray() and $this->emptyLastOCSStatusCodesArray() was used before the user deletion step and thus OCS response is found as 0.  This step is passed in this PR https://github.com/owncloud/ocis/pull/7020 and this issue can be closed.

won't be fixed because we're going to get rid of OCS api.

authors: S-Panta ScharfViktor micbar phil-davis

repo: owncloud/ocis


text:
institutions drop down menu is hidden behind elements below

@tbsbdr add more details

This should be fixed via https://github.com/owncloud/web/pull/11349.

source: gharchive/issue

authors: JammingBen tbsbdr

license_type: permissive

license_source: github-api


text:
WL-3918 Add support for OLI courses.

We explicitly support the additional namespace.

There should be better tests for this, but for now just add support.

source: gharchive/pull-request

repo: ox-it/wl-course-signup

license_source: bigquery


text:
Cal.com transformer benchmark showing lots of variance

Appears to be due to a hashbrown::HashSet resizing unpredictably.
See flamegraph for: https://codspeed.io/oxc-project/oxc/branches/08-27-feat_wasm_output_symbol_ids_in_scope_tree
Maybe can fix by reserving additional capacity in hash maps upfront.
Wonder why it's only showing up on the Cal.com benchmark, and why it's non-deterministic.

I traced the code and I suspect this:
https://github.com/oxc-project/oxc/blob/10279f55d92df80d9d5ce6b034a230e2a8a89e19/crates/oxc_transformer/src/env/data/babel.rs#L10-L13
I'll move this constructor out of the benchmark and see what happens.

I have unignored the benchmark.

Unclear if the variance is still there or not. Possible it is, but is masked by the massive increase in time that benchmark is now taking to run - #5457.
What was particularly confusing me wasn't so much what was causing the HashSet to resize, but why it was displaying indeterminism in doing so. I can't see the reason for that. Figuring that out might give us a clue how to reduce variance in the benchmarks overall.
We can see if the problem returns or not once #5457 is resolved.

authors: Boshen overlookmotel

repo: oxc-project/oxc

license: MIT


text:
IRI converted with STR is not comparable with another literal

Describe the bug
IRI converted with STR is not comparable to a literal of the same value
To Reproduce
Steps to reproduce the behavior:

Which version of Oxigraph are you using? On which platform?

Official oxigraph/oxigraph:v0.3.19 docker image

A command line or a code snippet that triggers the bug.

Execute the following query PREFIX p_prefix1: <some:ns>
 PREFIX p_prefix2: <some:ns>

SELECT * {
   # All three BINDs have literal type in response
   BIND(STR(p_prefix1:) AS ?x)
   BIND(STR(p_prefix2:) AS ?y)
   BIND('some:ns' AS ?z)
   # True (expected)
   FILTER(?x = ?y)
   # Both of these are unexpectedly False
   FILTER(?z = ?z)
   FILTER(?x = 'some:ns')
}

The above works fine in a few other triple stores I've tried

Hi! Thank you for this great bug report! I have understood the bug: Oxigraph encodes all IRIs using a dictionnary and reuses the same dictionnary for long strings but short strings are inlined. The STR function implementation just casts the IRI dictionnary id to a string dictionnary id so in the FILTER(?x = 'some:ns') we end up with a comparision between a dictionnary id (left) and an inline string (right) leading to false even if they are actually the same string.
Some possible fix:

allow inlined IRI when the IRI is small but it will break the on-disk encoding and would require a migration script
when casting an IRI to a string, check if the string is small (it will require a read, hence a performance penalty but it's very likely the string will be read anyway at some point when processing the same query result so it might not introduce new I/O reads in a lot of cases).

I would tend to prefer solution 2 for now and plan to do 1 in a future release that will change the on-disk formart.

Thanks, I tried ghcr.io/oxigraph/oxigraph:main docker image and it's working :+1:

@vtermanis Amazing! Thank you!

Released in 0.3.20. Thank you again!

authors: Tpt vtermanis

repo: oxigraph/oxigraph


text:
Access to line,column position for triples

I am currently using the RdfXmlParser to parse OWL files. While this works well, debugging my parser or the OWL file is fairly hard because my error messages are poor. I'd like to improve this. The main issue advance would be to get some line position information from the parser as it is going. Currently, I can't see any mechanism of getting this information out from the RdfXmlParser -- the underlying quick_xml parser could at least provide access to the buffer position which would be easy enough to uncover.
I am not sure if this is a good solution or not, although it is cheap and cheerful. So I thought to ask before I sent in a PR to see if there is a better design.

Hi! Indeed having proper error location would be amazing. Thank you! It's sad that quick-xml does not provide column/row position indeed. Using the buffer position seems also to me the least bad way to go. Feel free to submit a minimal not working PR to see if we agree on a design before spending too much time on it.
The Turtle parser has already positioning support it might be a useful reference.

I think quick-xml doesn't know the column/row information it passes through, but, yes, it's a PITA.
But the turtle approach isn't enough for me. I need access to it all the time even during normal functioning. Most of my errors come not from the RDF parsing (my files are generally valid) but because the OWL that is produced is not valid for one reason or another. As I make sense of the triples after I have parsed them all, I have no choice put to collect the buffer positions as I go and keep them alongside the triples.

Hello, what about position access even when there are no errors?
I would like to know how many bytes were already read from a graph, or the start and end offset of a triple on the parse_step callback (perfect for grabbing the relevant text directly from the source file or for knowing how much of the file has been read already).
I'm mainly interested in the Turtle/NTriples parsers but I imagine this might be helpful for other parsers as well.

authors: Tpt andrefs phillord

repo: oxigraph/rio


text:
propose updates to sourmash to make kmers_and_hashes code less cumbersome

code in #40 could benefit from making SeqToHashes less opaque over in sourmash.
Some ideas:

simple and lightweight: provide access to kmer_index per https://github.com/oxli-bio/oxli/pull/40#issuecomment-2370737286 to make
better, but more: provide an iterator in sourmash that yields canonical k-mers and hashes;

ref https://github.com/sourmash-bio/sourmash/issues/3339

repo: oxli-bio/oxli


text:
Failed to run code

File "/home/xxx/anaconda3/envs/LIIR/lib/python3.6/site-packages/smac/env/starcraft2/starcraft2.py", line 292, in _launch
self._run_config = run_configs.get(version=self.game_version)
TypeError: get() got an unexpected keyword argument 'version'
TypeError: get() got an unexpected keyword argument 'version'
TypeError: get() got an unexpected keyword argument 'version'

Are you using the latest version of PySC2 on the master branch?

No,I'm using pysc2==2.0.2

SMAC requires that you use pysc2>=3.0.0. Please update it!

Should  I use the latest version of PySC2 ？Such as 3.0?

OK,thanks,I'll try.

repo: oxwhirl/pymarl


text:
Feature request: Support command-line usage

I'd love to be able to automate this as part of a CI/CD process; to do that, I need to be able to call this from the command-line.

This seems feasible. We'll try to find some time to look into this.

+1 from another one of our end users:
 Is it possible to have an external script like a Jenkins build pipeline or other trigger the translation package builder to create a package and generate a new milestone?
 A company with hundreds of maps would like to automate the process as much as possible. thanks for any advice.

authors: raducoravu saanvik


text:
More updates from previous review

I regularized the width of the pages, especially for large screens
Changed the yellow buttons
Corrected text sizes
Reduced the length of the sections on the home page
Removed gradient on testimonials section
Made all buttons match the design
etc

This is really good, thank you for your work @Shopiley @Tolu-Mals. It's very appreciated!
@Shopiley there are some more UI changes we need to make, but I don't think they block using this website for the announcement. I'll communicate these offline
There are some changes that block the release though:

The cohort pages don't have the right data (please ask Tosin for a list)
The testimonials are still placeholder (pls ask Ehis to provide real testimonials for us to use)
You haven't updated the schedule yet based on our discussions

Okay, I'm open to discussing the UI changes later.
I'll work on getting the content you've mentioned.

authors: Shopiley oyekanmiayo

repo: oyekanmiayo/wdsa-website


text:
feat: Create new post button not present, when going through posts

Description
The button to add/create new posts is missing, when viewing the posts
Screenshots

Ready to Work?

[X] I want to work on this issue

assigned to you

Can you please add hacktoberfest tag?

repo: oyepriyansh/DevTweet


text:
Callbacks

Added a callback framework to make then general. Implemented Earlystopping, Modelcheckpoint and Logger form this interface. Seems to work.

Please merge!


text:
Fix duplicated deps (HATE EPOCH)

[ ] byteorder
[x] lazy_static
[ ] log
[x] rand
[ ] syn
[ ] unreachable

$ cargo tree -d
byteorder v0.4.2
└── stb_truetype v0.2.1
    └── rusttype v0.3.0
        └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate)
            └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)

byteorder v1.2.1
└── deflate v0.7.17
    └── png v0.11.0
        └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate)
            └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)

lazy_static v0.2.11
├── wayland-kbd v0.13.0
│   └── winit v0.10.0
│       └── glutin v0.12.0
│           ├── gfx_window_glutin v0.20.0
│           │   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate)
│           │       └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)
│           └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)
└── wayland-sys v0.12.4
    ├── wayland-client v0.12.4
    │   ├── glutin v0.12.0 (*)
    │   ├── wayland-kbd v0.13.0 (*)
    │   ├── wayland-protocols v0.12.4
    │   │   ├── wayland-window v0.13.2
    │   │   │   └── winit v0.10.0 (*)
    │   │   └── winit v0.10.0 (*)
    │   ├── wayland-window v0.13.2 (*)
    │   └── winit v0.10.0 (*)
    └── wayland-protocols v0.12.4 (*)

lazy_static v1.0.0
├── glutin v0.12.0
│   ├── gfx_window_glutin v0.20.0
│   │   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate)
│   │       └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)
│   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)
├── libloading v0.4.3
│   └── dlib v0.4.0
│       ├── wayland-kbd v0.13.0
│       │   └── winit v0.10.0
│       │       └── glutin v0.12.0 (*)
│       └── wayland-sys v0.12.4
│           ├── wayland-client v0.12.4
│           │   ├── glutin v0.12.0 (*)
│           │   ├── wayland-kbd v0.13.0 (*)
│           │   ├── wayland-protocols v0.12.4
│           │   │   ├── wayland-window v0.13.2
│           │   │   │   └── winit v0.10.0 (*)
│           │   │   └── winit v0.10.0 (*)
│           │   ├── wayland-window v0.13.2 (*)
│           │   └── winit v0.10.0 (*)
│           └── wayland-protocols v0.12.4 (*)
├── shared_library v0.1.8
│   ├── glutin v0.12.0 (*)
│   └── osmesa-sys v0.1.2
│       └── glutin v0.12.0 (*)
├── thread_local v0.3.5
│   └── regex v0.2.5
│       └── env_logger v0.4.3
│           └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main) (*)
├── winit v0.10.0 (*)
└── x11-dl v2.17.2
    ├── glutin v0.12.0 (*)
    └── winit v0.10.0 (*)

log v0.3.9
├── env_logger v0.4.3
│   └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)
└── gl_generator v0.7.0

log v0.4.1
├── gfx v0.17.0
│   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate)
│       └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)
├── gfx_core v0.8.0
│   ├── gfx v0.17.0 (*)
│   ├── gfx_device_gl v0.15.0
│   │   ├── gfx_window_glutin v0.20.0
│   │   │   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)
│   │   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)
│   ├── gfx_window_glutin v0.20.0 (*)
│   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)
├── gfx_device_gl v0.15.0 (*)
├── log v0.3.9
│   ├── env_logger v0.4.3
│   │   └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main) (*)
│   └── gl_generator v0.7.0
└── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main) (*)

rand v0.3.19
├── cgmath v0.15.0
│   ├── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate)
│   │   └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)
│   └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main) (*)
└── tempfile v2.2.0
    └── wayland-window v0.13.2
        └── winit v0.10.0
            └── glutin v0.12.0
                ├── gfx_window_glutin v0.20.0
                │   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)
                └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)

rand v0.4.1
└── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)

syn v0.10.8
└── derivative v1.0.0
    ├── gfx v0.17.0
    │   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate)
    │       └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)
    └── gfx_core v0.8.0
        ├── gfx v0.17.0 (*)
        ├── gfx_device_gl v0.15.0
        │   ├── gfx_window_glutin v0.20.0
        │   │   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)
        │   └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)
        ├── gfx_window_glutin v0.20.0 (*)
        └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)

syn v0.11.11
├── serde_derive v1.0.27
│   ├── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate)
│   │   └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)
│   ├── serde v1.0.27
│   │   ├── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate) (*)
│   │   ├── ron v0.1.5
│   │   │   └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main) (*)
│   │   └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main) (*)
│   └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main) (*)
└── serde_derive_internals v0.19.0
    └── serde_derive v1.0.27 (*)

unreachable v0.1.1
└── ordered-float v0.5.0
    └── rusttype v0.3.0
        └── hate v0.1.0 (file:///home/ozkriff/zemeroth/main/hate)
            └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)

unreachable v1.0.0
└── thread_local v0.3.5
    └── regex v0.2.5
        └── env_logger v0.4.3
            └── zemeroth v0.1.0 (file:///home/ozkriff/zemeroth/main)

As #237 is merged, this issue is outdated. Closing in favour of https://github.com/ozkriff/zemeroth/issues/251

repo: ozkriff/zemeroth


text:
chore(styling): Fix link color in notification dropdown

@wski

:+1:

:-1:  Let me know if I've tested this incorrectly, but I still see:

Yikes. You're still getting the dropdown scrollbar as well? @wski @clarkjefcoat

@wski @clarkjefcoat check again?

:+1:

:+1: looks good to me

authors: akonsowski bhalt clarkjefcoat wski

repo: ozone-development/ozp-react-commons


text:
Publish .NET Core builds to Nuget

Currently, the Microsoft.PSharp NuGet package only supports .NET Framework projects. It would be good to make netstandard2.1 builds available so we don't have to import P#'s source code as a Git submodule in the P compiler repo.
The last release was 1.3.5, 8 months ago. When will the next release be made available? I see there are tags for versions 1.3.6 - 1.3.9 and the README instructs users to get the "latest" release from NuGet.

We plan to have a new package uploaded on nuget.org next week.

Thanks, Akash. Will that version of P# support .NET Core?

Yes!

Awesome! 😄

Was there a delay, here?

Is this lack of control on the process only because this is the first time through the new process?  If this nondeterminism is possible every time a fresh release is published on nuget, perhaps we need to consider a new process.

This is a one time thing and we are close now.
Akash
Sent from my iPhone

On 29-Sep-2018, at 11:48 PM, Shaz Qadeer notifications@github.com wrote:
Is this lack of control on the process only because this is the first time through the new process? If this nondeterminism is possible every time a fresh release is published on nuget, perhaps we need to consider a new process.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Any updates?

@alexreinking we finally got unblocked and our package is ready. We need to go through some final admin processing to be able to upload to nuget.org (as there were very strict new requirements that were put in place for public MS-owned packages and we had to conform, this is what caused this massive delay). Please note that both @akashlal and me are OOF soon for a week or so, so might not be able to get the final green light before that. But its coming very soon now. Thanks for your patience.

@alexreinking @shazqadeer we are now finally able to publish again! I just uploaded the latest NuGet package (1.4.0) which should be indexed very soon and available for consumption. Closing this issue.

Hooray! I see 1.4.0 in the Nuget Gallery already!

authors: akashlal alexreinking pdeligia shazqadeer

repo: p-org/PSharp

license: mit


text:
Force unwrapping will crash.

Maybe we should treat force unwrpping as same as optional ?
Code:
@available(iOS 16.0, *)
@AssociatedObject(.OBJC_ASSOCIATION_RETAIN_NONATOMIC)
private var interaction: ImageAnalysisInteraction! = .init()

Expanded:
{
    get {
        if !self.__associated_interactionIsSet {
            let value: ImageAnalysisInteraction! = .init()
            objc_setAssociatedObject(
                self,
                Self.__associated_interactionKey,
                value,
                .OBJC_ASSOCIATION_RETAIN_NONATOMIC
            )
            self.__associated_interactionIsSet = true
            return value
        } else {
            return objc_getAssociatedObject(
                self,
                Self.__associated_interactionKey
            ) as! ImageAnalysisInteraction  // <-- This force unwrapping will crash if value is nil.
        }
    }
    set {
        objc_setAssociatedObject(
            self,
            Self.__associated_interactionKey,
            newValue,
            .OBJC_ASSOCIATION_RETAIN_NONATOMIC
        )
    }
}

This is a problem because it is certainly possible to assign nil.
I think the following part is the cause.
https://github.com/p-x9/AssociatedObject/blob/a82277a628bf40251c4459794ed1503b7ace06c1/Sources/AssociatedObjectPlugin/AssociatedObjectMacro.swift#L256
I will fix it later.
Thanks.


text:
Support Mackup Backup

Mackup helps me keep my application settings in sync.
More → https://github.com/lra/mackup
I think supporting it for Maccy would be great. I saw you recommend copy pasting $HOME/Library/Containers/org.p0deje.Maccy/Data/Library/Application Support/Maccy — is there a config file?

This is how you can help https://github.com/lra/mackup/tree/master/doc#get-official-support-for-an-application

I guess you can simply configure it to keep the following:

$HOME/Library/Containers/org.p0deje.Maccy/Data/Library/Application Support/Maccy/
$HOME/Library/Containers/org.p0deje.Maccy/Data/Library/Preferences/org.p0deje.Maccy.plist

Or simply the whole directory: $HOME/Library/Containers/org.p0deje.Maccy.

I know I can do that, but it'd be great if you can bring support for Mackup which will allow all the users using Mackup to not have to worry about backup these files separately.

I guess you can open PR for Mackup in this case ;)

Is there anything else that needs to be done here?

Closing due to inactivity. Please re-open if the issue still happens and provide requested info.


text:
No fullscreen on mobile

Initiating via link acts as if the targeted content is opened then closed, i.e., on desktop if I don't style via onexit: function() {...} then I have inappropriately styled content once I esc fullscreen.
Any insight into getting this to work on iOS would be appreciated.
Seems to work on Chrome/Firefox on Android.

Thanks,

open/close issue should be fixed, you can try with the new version.
unfortunately iOS safari is not supported by the Full screen api, http://caniuse.com/#search=fullscreen


text:
Support languages other than Go

Our entire API is defined via GRPC which should, in theory, make it very easy for us to create clients in any language that supports grpc. In practice of course it's a little bit more difficult but should be doable. Languages we'd like to support in approximate order of importance:

PYTHON
Java
C++
Ruby
Rust

Probably many more that would interesting to people.

I would very much like to see C# on that list if possible :)
It is a gRPC/Protobuf supported language after all. and it's gaining in popularity now with .NET Core being open source and multi-platform.

We're in the process of transitioning a 3rd party python client for official support. That'll inform how we support other languages going forward.

authors: jdoliner sjezewski teodimache

repo: pachyderm/pachyderm


text:
Add test to validate dash image exists

This will allow PRs that only bump the dash version to be merged after CI passes.
Fixes #1733

Simple enough, LGTM.

authors: jdoliner sjezewski


text:
No archived commits in fuse

Changes the default with fuse mounts to not show archived and cancelled commits.
You can get the old behavior back with a flag. -a

Fixes #794


text:
Deploy script setupcfg2rpm.py

Script setupcfg2rpm.py parses setup.cfg, extracts python packages from options->install_requires
section and wraps them into python3dist(package) so output can by used with dnf package installer.
Example:
$ dnf install $(setupcfg2rpm.py path_to_setupcfg)
python3dist(some_package)
python3dist(other_package)
$

looks good

thanks, sorry for not waiting for your approval, thought you're busy and because @csomh gave me good feedback i decided to move forward instead of bothering you. same applies for @jpopelka and others

repo: packit-service/deployment


text:
Testing-farm in the default jobs

background: We want to simlify the config file as much as possible and want to have testing-farm turned on by default.

Which chroots will by used by default? fedora-stable (since rawhide is usually broken)
What needs to be done on the packit side?
What needs to be done on the testing-farm side? (@thrix , @psss )
What about package without fmf setup?

Leave everything to testing-farm: no .fmf => empty test suite => return "Installation successful`
Try to generate .fmf with some basic ci.fmf on our side. (Not sure, how we can send it to testing farm.)

So is the idea that by default we run artifact installation if not other tests added? Stef also wanted to have a no-fmf way how people can add a test script directly into packit config without the need to specify any FMF file.

Anyay, in the current state of things, we did not expect to have an install only test scenario. If there is no .fmf nothing will be run and an error will be returned.
Better to think about this sooner the later. Of course, we can implement it as we want :) @psss what do you think?

Running tests by default to simplify config makes sense to me. But I'd say only if there is at least one plan defined. The following tmt command can be used to check if there are any plans available:
tmt plans ls

If there is no plan defined I would suggest to do nothing (from the testing perspective).

Most of the projects will not have fmf defined at all.

We probably don't want to show error states for those projects.

=> Show error to force them to setup fmf.
=> Do not show anything.
=> Show installation successfull. The success/failure of  the installation of the package from the copr repo can be useful.

Since we have a default behaviour on the testing-farm side, we can probably turn on the tests by default (=when people don't specify the jobs section in the config).
Do we want to have both copr-build and tests. Or only the tests status for each chroot?

I would say only tests, but as you wish, I am ready for the load :)

I would say only tests, but as you wish, I am ready for the load :)

Just to make it 100% clear, the build and tests will be run in all cases. It's only about UX -- if we want to have both build-??? and test-?? checks in the PR and a message with the copr instructions. If we don't add the build, there will be only test-??? checks without any message about copr.

Unless there is a problem with building the package I would go with test-* messages only.

Unless there is a problem with building the package I would go with test-* messages only.

Yes, we comment about the (s)rpm build errors in all cases.

authors: lachmanfrantisek psss thrix

repo: packit-service/packit-service


text:
How to tag our team in the comments

Is there some way, how to tag our team in the github comments?
See this comment, the @packit-service/the-packit-team was not parsed correctly:

What about tagging all members of the team? (Looks bad, but should work.)

test @packit-service/the-packit-team  test

no idea how come it works in my comment but not in the app added one

The comment is from the PR in the external project so maybe we can tag the team only in our organisation.

you're right

authors: jpopelka lachmanfrantisek


text:
WIP: let handlers use jobconfig only

[x] finish code
[ ] fix tests
[ ] get a beer

With this insane refactor, handlers would only use jobconfig and not
packageconfig.
Fixes #418
Fixes #393
I'm pretty sure this will conflict with #675 a lot.

I had to start from scratch, lol

Thanks for the review, merging.
@lbarcziova sorry for the rebase hell :angel:


text:
Missing underscores in yaml examples

In the files we specify yaml syntax (```yaml), but it is ignored as if there was unsupported format specified.

Probably the Hugo Theme that we use does that.
A quick workaround is in #81

authors: dhodovsk jpopelka


text:
Update of chroots of Copr Project owned by Packit rises an error

If someone creates the PR with a set of chroots and change it later on, there is a permission problem.
See this example: https://github.com/RedHat-SP-Security/keylime-tests/pull/13#issuecomment-967206007

It's not, the issue you cannot update targets while there is a running build (for that target you want to remove? ← might not be true)

@mfocko what can we do here?

Check for the real cause (#1118 ) and provide a better comment.
Retrigger or suggest to retrigger once the build is finished. Or, can we cancel the build?

• Retrigger or suggest to retrigger once the build is finished. Or, can we cancel the build?

that's probably related to an even older issue #5

So, let's start with getting a better comment. The situation is not so common and asking for some human interaction looks ok to me in this case.

We now produce a better error message: https://github.com/packit/packit-service/pull/1397
Since this is a limitation of Copr, I'm not sure if there is anything we can do our side. We could possibly cancel the build or work with Copr to implement this on their side.

authors: TomasTomecek lachmanfrantisek mfocko

repo: packit/packit-service


text:
srpm builds started to fail with packaging.version.InvalidVersion: Invalid version: '287.32.g9eba04e'

What happened? What is the problem?
A few days ago, most of our projects started to fail srpm builds during upstream GitHub PR tests. E. g. in https://github.com/cockpit-project/cockpit-machines/pull/1021 , whose SRPM build fails like this:
2023-04-14 18:38:19.213 upstream.py       DEBUG  No ref given or is not glob pattern
2023-04-14 18:38:19.213 upstream.py       DEBUG  We're about to `git-describe` the upstream repository /tmp/tmpma26yg7g.
2023-04-14 18:38:19.213 commands.py       DEBUG  Command: git describe --tags --abbrev=0 --match=?*
2023-04-14 18:38:19.217 logging.py        DEBUG  287
2023-04-14 18:38:19.218 upstream.py       DEBUG  Version: 287
2023-04-14 18:38:19.218 upstream.py       DEBUG  Sanitized version: 287
2023-04-14 18:38:19.218 upstream.py       DEBUG  Name + version = cockpit-machines-287
[...]
2023-04-14 18:38:25.011 upstream.py       INFO   Created archive:
2023-04-14 18:38:25.011 upstream.py       INFO   	parsed   path: /tmp/tmpma26yg7g/cockpit-machines-287.32.g9eba04e.tar.xz
2023-04-14 18:38:25.012 upstream.py       INFO   	absolute path: /tmp/tmpma26yg7g/cockpit-machines-287.32.g9eba04e.tar.xz
2023-04-14 18:38:25.079 commands.py       DEBUG  Command: git describe --tags --long --match *
2023-04-14 18:38:25.082 logging.py        DEBUG  287-32-g9eba04e
2023-04-14 18:38:25.088 commands.py       DEBUG  Command: git describe --tags --long --match *
2023-04-14 18:38:25.091 logging.py        DEBUG  287-32-g9eba04e
2023-04-14 18:38:25.091 base_git.py       DEBUG  Running ActionName.fix_spec.
2023-04-14 18:38:25.091 base_git.py       DEBUG  Running default implementation for ActionName.fix_spec.
2023-04-14 18:38:25.285 upstream.py       INFO   Version in upstream registries is '287'.
2023-04-14 18:38:25.309 upstream.py       INFO   Version in spec file is '287.32.g9eba04e'.
2023-04-14 18:38:25.310 utils.py          ERROR  Preparation of the repository for creation of an SRPM failed: Invalid version: '287.32.g9eba04e'

AFAIK our packit.yaml does not do anything magic wrt. the version, and it hasn't changed in months (other than a Fedora version list update in February). Our make dist rule does call git describe to figure out the upstream version, but it already adjusts to RPM rules with tr '-' '.' -- an upstream version like "287.32.g9eba04e" should be totally fine.
The log says it uses packit 0.72.0-1.fc38. Locally I have F37, but packit-0.72.0-1.fc37.noarch is the same upstream version, so it should behave the same. When I run packit srpm in cockpit-machines.git, it succeeds, but curiously produces a different version format:
2023-04-17 07:48:11.012 upstream.py       INFO   Created archive:
2023-04-17 07:48:11.012 upstream.py       INFO   	parsed   path: /var/home/martin/upstream/cockpit-machines/cockpit-machines-287.29.g00f191f.tar.xz
2023-04-17 07:48:11.012 upstream.py       INFO   	absolute path: /var/home/martin/upstream/cockpit-machines/cockpit-machines-287.29.g00f191f.tar.xz
2023-04-17 07:48:11.639 upstream.py       INFO   Version in upstream registries is '287'.
2023-04-17 07:48:11.710 upstream.py       INFO   Version in spec file is '287.29.g00f191f'.
2023-04-17 07:48:11.710 upstream.py       WARNING Version '287.29.g00f191f' in spec file is outdated.
2023-04-17 07:48:11.710 upstream.py       INFO   Picking version '287' from upstream registry.
2023-04-17 07:48:11.900 api.py            INFO   Directory with sources: /var/home/martin/upstream/cockpit-machines
2023-04-17 07:48:11.986 command_handler.py INFO   Nothing to clean.
2023-04-17 07:48:11.987 srpm.py           INFO   SRPM: /var/home/martin/upstream/cockpit-machines/cockpit-machines-287-1.20230417074811108593.main.29.g00f191f.fc37.src.rpm

So I'm a bit confused what to do here. Do we need to change anything on our side? Is that a regression in the service? Or in packit itself?
Thanks!
@skobyda @kkoukiou FYI
What did you expect to happen?
SRPM build should succeed.
Example URL(s)

https://github.com/cockpit-project/cockpit-machines/pull/1021
https://download.copr.fedorainfracloud.org/results/packit/cockpit-project-cockpit-machines-1021/srpm-builds/05785729/builder-live.log.gz
https://github.com/cockpit-project/cockpit-podman/pull/1268

Steps to reproduce
Any upstream PR against cockpit-podman or cockpit-machines
What is the impacted category (job)?
Copr builds
Workaround

[ ] There is an existing workaround that can be used until this issue is fixed.

Participation

[ ] I am willing to submit a pull request for this issue. (Packit team is happy to help!)

hi! Thank you for the report, from quickly comparing the logs, I can see that the failing line comes from python3-packaging:
So I checked the versions for the current runs and the previous (successful) runs and since we run the SRPMs in fedora-latest-stable environment and f38 is now considered stable, they differ:

previously, when run on f37: 21.3-6.fc37
now, running no f38: 23.0-1.fc38

Related to https://github.com/packit/packit/pull/1858. Before packaging 22.0, a string like 287.32.g9eba04e produced LegacyVersion, now it raises InvalidVersion exception. The fix should be simple knowing that LegacyVersion always sorts lower than Version.

Should we move this to packit?

authors: lbarcziova martinpitt nforro


text:
Process message task improvements

Fixes #2323
Related to #2290

RELEASE NOTES BEGIN
N/A
RELEASE NOTES END

Just a little nitpick, I'd maybe factor out the HandlerTaskWithRetry rename to a separate commit for more clarity.

I have adjusted the commit message to mention the renaming, but to me it makes sense to have it in one commit as it explains why was the renaming done.


text:
Better Testing-farm response for cluster problems

Response to testing-farm errors.
Link centos-ci issue on known problem.

recheck


text:
Failure during Ansible playbook execution

Under https://github.com/oamg/convert2rhel/pull/194 (and others) we see:
@packit-as-a-service packit/testing-farm-epel-6-x86_64 — Failure during Ansible playbook execution
The associated link does not load anything: http://artifacts.dev.testing-farm.io/880b7020-ebd8-4dac-abb4-16468d69555e

I can see this is EPEL 6.
@thrix is there a plan to support el6 in the new architecture?

yes, I need to add hopefully 1 playbook to fix the repos. Sorry for not having it yet. Will do it today.

@thrix no worries, thanks for addressing this so promptly!

We're not seeing this issue anymore.

authors: TomasTomecek bocekm thrix

repo: packit/packit


text:
z88dk-produced fast tape loading with $SCREEN fails

rustzx fails to load tape attached to this issue with repetitive  Bytes: ... messages
Expected result:

Actual result:

Tape
loading.zip

The command which produced this file
z88dk-appmake +zx -b simple_tape/loading.scr -o out/loading.tap --blockname screen --org 16384 --noloader

Interesting findings:

fuse emulator fails to load this tap w/o fast loading (trap-loading)
speccy fails to load that tape too

After further investigation It has become clear that it is not a bug, it was a just not valid tape file for loading via LOAD "". The tape file contained only screen bytes block without any loader, and it indeed should be loaded with the command LOAD "" SCREEN$. Fuse opened this file correctly because it has special handling for such kind of files. However, for all practical purposes, there is no need to implement fast loading for tap files without a basic loader, it is really rare occasion, and If users want to load such file anyway, they can co it with correct load command... Closign for now.

repo: pacmancoder/rustzx


text:
feat(txpool): add consomptional fee model

Description
Add estimated minimum and consumption fee
Related issue(s)

Resolves #1543 #1544 #1545

Thanks @Ja7ad
The code quality is much better now...

repo: pactus-project/pactus


text:
activerecord namespace and concern

hi,
how do i ensure models/concern is loaded in padrino?
and models/mynamespace/*.rb is loaded?
how do i specify the loading criteria in padrino configuration?
and how do i configure it to work with rake ar:migrate?
i have this in my rakefile, but my concern is, if i require all ar file, my other non active record tasks will also load all models into the rake task, causing overhead...
is there any better way to do it?
thank you :)

require 'bundler/setup'
require 'padrino-core/cli/rake'

RACK_ENV = ENV['RACK_ENV']
# puts "out: #{RACK_ENV.inspect}"
PadrinoTasks.use(:database)
PadrinoTasks.use(:activerecord)
PadrinoTasks.init

how do i ensure models/concern is loaded in padrino?
and models/mynamespace/*.rb is loaded?

Your concerns will be loaded. See this code.

how do i specify the loading criteria in padrino configuration?
and how do i configure it to work with rake ar:migrate?

Maybe you can use $LOAD_PATH  or Padrino::Application.prerequisites

i have this in my rakefile, but my concern is, if i require all ar file, my other non active record tasks will also load all models into the rake task, causing overhead...
is there any better way to do it?
thank you :)

That is a default settings for Padrino project. You can avoid one by removing the line and specifing database task name on your original task.

repo: padrino/padrino-framework


text:
ManyToMany Relation with Data

class User {

// code

/** @ManyToMany(targetEntity="Item", tableTrough="Rating",keyTroughFrom="user_id", keyThroughTo="item_id")*/
public $items

//code

}

My rating table has more column in addition to the primary and foreign keys:

rating
date

If I define a ManyToMany Assoction in the User Entity I loose information of the single relations. Is there a way to fetch it in the User Entity or should I create a Entity for this User-Item-Relation?

Yes, then you actually retrieve the User from the database, you'll add the related conditions for the subquery e.g. try:
User::query()->related('items.rating', 'items.date')->get();

authors: Smeaven janschoenherr

repo: pagekit/pagekit


text:
Possible regression: http2, nginx, chrome and windows

Possible regression for https://github.com/pagespeed/ngx_pagespeed/issues/788
nginx 1.9.12, pagespeed 1.10.33.6-beta and the same configuration as posted here https://github.com/pagespeed/ngx_pagespeed/issues/1140
We are using SSL with a Let's Encrypt cert. Only Windows + Chrome users are seeing this issue. It ended up bringing the site to a stand still.
Here are a few errors we are getting in errors.log
2016/03/07 05:01:16 [error] 3692#0: *360332 upstream timed out (110: Connection timed out) while reading response header from upstream, client: XXX.XXX.XXX.XXX, server: www.XXXXXX.com, request: "GET /forums/ HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm/php-fpm.sock", host: "www.XXXXX.com"
2016/03/07 06:19:46 [error] 3691#0: *372356 connect() to unix:/var/run/php-fpm/php-fpm.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX, server: www.XXXXX.com, request: "GET /path/to/file.jpg,g38273.pagespeed.ic.38c76x.jpg HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm/php-fpm.sock:", host: "www.XXXXX.com", referrer: "https://www.XXXXX.com/url/"
2016/03/07 15:59:53 [alert] 3688#0: *524522 http request count is zero while closing request, client: XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX, server: [::]:443
2016/03/07 16:31:45 [alert] 3690#0: *525244 open socket #45 left in connection 30
2016/03/07 17:53:23 [alert] 11173#0: *41609 http request count is zero while closing request, client: XXX.XXX.XXX.XXX, server: 0.0.0.0:443

I had to turn off pagespeed and it appears to be working better. I can get logs. Don't have any core dump, but I don't think it caused any.

@jdelgad If you could forward logs that may help figuring this out. Having logs files written with the log level set at debug would help even more.

I can post them. The next month is a big month for my site so I probably can't do this before the weekend (and even then under limited time frames). Where should I upload them? I can do some limited testing in debug.

If the logs aren't too big, you could share them to oschaaf@we-amp.com
Are you also seeing the ERR_SPDY_PROTOCOL_ERROR in chrome as mentioned in https://github.com/pagespeed/ngx_pagespeed/issues/788 ?

Using Chrome on Windows 10, I tried to reproduce these log messages: ... http request count is zero while closing request ..., but they do not show up for me.

@oschaaf The other admin is reporting ERR_SPDY_PROTOCOL_ERROR and took a screenshot.  It even suggests Uncaught ReferenceError: mod_pagespeed_fKCT0dPM24 is not defined. We do have a user reporting they had problems with the site on OS X, but still on Chrome.
The site had been up for days prior to experiencing breaking issues for some. Others reported weird visual artifacts almost immediately.  I'll send you the logs tonight.

@jdelgad could you pm the site's url so I can have a look?

Reproduction of attempting to finalize a request with r->count already zero succeeded by refreshing a page in Chrome on Windows as fast as possible by holding ctrl+r on a page which results in a built-in 403/not allowed response.
We attempt to finalize when we should not when:

a RST_FRAME was received
we are processing an IPRO header-event which ends up hitting ngx_http_send_special_response

This sequence of events is similar to https://github.com/pagespeed/ngx_pagespeed/issues/788, but subtly different.
Looking into a fix.

After having upgraded recently to nginx 1.9.12 and switched from SPDY to HTTP/2 I'm getting often ERR_SPDY_PROTOCOL_ERROR in chrome on windows, especially when i try to login to the administrator panel  the POST request fails.
I don't know if it's related to pagespeed or nginx itself, as i don't get anything in the logs.
I'll anyway test your patch now to say you it it can help also my case

I'm testing the patch in production now, and it seems it fix my issue: I'm not getting anymore ERR_SPDY_PROTOCOL_ERROR (I was getting it very often during POST requests)
Anyway let me run it for some days, I'll report you if i see it anymore...

Sorry for my messages here, but i still don't want open another ticket. I stopped the testing: it wasn't my case. My issue is due to an incompatibility of ngx_pagespeed and this nginx patch i applied:
https://trac.nginx.org/nginx/ticket/907

I restarted my server and got this shortly after I staged it up.
2016/03/12 17:52:47 [info] 12677#0: [ngx_pagespeed 1.10.33.6-0] No threading detected. Own threads: 1 Rewrite, 1 Expensive Rewrite. 2016/03/12 17:56:40 [alert] 12685#0: *944 open socket #29 left in connection 18 2016/03/12 17:56:40 [alert] 12685#0: aborting ```

I'll notice it for more anomalies before I turn on debug mode. So far it looks fine, but it took 2-3 days for it to become more noticeable. Loading time is much better with it on and I'm not seeing artifacts on Chrome.

Sorry to revive this thread (if it's already closed), but I'm getting the same error on my logs.  Was this fixed and at what version?  I'm using pagespeed 1.11.33.4-0 on nginx 1.10.0
Relevant logs:
2016/11/18 13:59:56 [alert] 45869#0: *57213 http request count is zero while closing request, client: xxxx, server: 0.0.0.0:443
2016/11/18 13:59:56 [alert] 45869#0: *57213 http request count is zero while closing request, client: xxxxx, server: 0.0.0.0:443

We are no longer using pagespeed. We have disabled http2 since it isn't really supported on CentOS 7 due to the issues pointed at https://www.nginx.com/blog/supporting-http2-google-chrome-users/
At some point early next year I intend to re-enable this. I don't believe it is an issue with http.

I need to come in here as well, as it's the only reference of the error we're expriencing right now. Unfortunately the logs show nothing more than that:
"http request count is zero while closing request"
With nginx 1.12.0 and pagespeed 1.11.33.4 (old version, as there is no newer PSOL download available). This happens regularly but very rarely (About 3-4 log entries every few hours on both loadbalancers with about 100'000 req/min).
Previously we've had nginx 1.10.2 with 1.11.33.4 and no problems to report.

Deactivation of http/2 doesn't do any difference
Deactivation of pagespeed makes the problem disappear, but is kinda no (definite) option
It happens not only in chrome, as it seems, even our uptime checks and other browsers seem to trigger it

@msebel Thanks for the detailed report. If I understand correctly, it may be worth looking at the code changes between nginx versions 1.10.2 and 1.12.0 for clues then.

Something new (causing a 502) popped up in the logs:
[ngx_pagespeed 1.11.33.4-0] [0510/091950:FATAL:rate_controller.cc(188)] Check failed: controller_->current_global_fetch_queue_size_->Get() > 0 (0 vs. 0)
But that seems to have happened the first and only time since we've updated nginx ten days ago.
Other then that we have a lot of [error]s in our logs stating that a directory can't be created because there already is one. Not sure if that's a problem though. It happend before, but we've never seen the same problems before our upgrade.

@msebel See https://github.com/pagespeed/ngx_pagespeed/issues/915
(also, this should only occur in debug builds, not release builds)

Also note: a fix for that exists in 1.12.
On Wed, May 10, 2017 at 3:25 PM, Otto van der Schaaf <
notifications@github.com> wrote:

@msebel https://github.com/msebel See #915
https://github.com/pagespeed/ngx_pagespeed/issues/915
(also, this should only occur in debug builds, not release builds)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pagespeed/ngx_pagespeed/issues/1146#issuecomment-300587352,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2kPTeXGJuejCB2AEvbK4_RornYTE40ks5r4g85gaJpZM4HrdSP
.

authors: creativeprogramming froilanmendoza jdelgad jmarantz msebel oschaaf


text:
[IOAPPX-283] Deprecate GradientScrollView for IOScrollView

Short description
This PR deprecates the GradientScroll and GradientBottomActions components.

[!important]
This PR was added as part of the refactoring of the GradientScroll component, but we preferred to move the screen component to the main repo for easier maintenance.
To learn more about the new IOScrollView component, please refer to:

https://github.com/pagopa/io-app/pull/5704

List of changes proposed in this pull request

Add deprecation note to the GradientScroll and GradientBottomActions components

How to test
N/A

@CrisTofani This PR has been re-purposed to deprecate GradientScrollView for IOScrollView. Please continue to discuss the code architecture in the new PR mentioned above.

repo: pagopa/io-app-design-system


text:
[PAGOPA-1012] feat: added queries for search by broker description

This PR contains two new queries that will be used by APIConfig core service in order to permits a search by broker description.
List of Changes

Added two queries for search by broker description.

Motivation and Context
These changes are required in order to permits the seach by broker description by APIConfig core backend and by the frontend portal.
How Has This Been Tested?

Tested in local environment

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as
expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

update_code

repo: pagopa/pagopa-api-config-starter


text:
Rank under Messages sent on my User profile not updating (for months)

If you go to my user profile here: https://xqc.pajbot.com/user/aubycek , you can see that I am Rank 473 under Messages sent. "Messages sent" alone works perfectly, but my Rank has been stuck on this particular number (473) for several months now (6+months). Don't know about other people, but I'm pretty sure it's broken at least for me.

Might be related to #970 or #966

Sounds interesting

Entirely intentional.

authors: Aubycek TroyDota alazymeme

repo: pajbot/pajbot


text:
Auto accept duel under a certain amount

Since its sometimes hard to keep track of duels, maybe it would be a good idea to add some sort of auto accept. That should include some sort of limit (so people don't abuse it on someone).
Example:
!autoduelon 100
!autodueloff
It could maybe also be possible to whitelist or blacklist certain people for the auto accept. This might be a bit too complicated together with the limit though.

this would be pretty dank, but i'm setting it as low priority, as the amount of work required to make this work well is really high.

This could be easy done with two new information about the user in mysql or redis.

duel_auto - Boolean True / False
duel_points - Int - Limit for autoduels

If must check if duel_auto is 1 and will accept the duel for the user.
But yeah this is maybe just useless data for mysql and redis that you don't really need.

repo: pajlada/pajbot


text:
changed current_time

The old current_time was the time when the app.py started, it never updates.
I changed the way it works, now it's actually the current time.
This should fix the VOD link for the pleblist and the calendar where it's used too.
(never noticed an issue for calendar, but the bot was always restarted every day)

Tested it and works now for online streams with a video_url :radio:
With this we can now use {{current_time|localize|strftime('%A, %B %d %Y %H:%M:%S %Z')}} to show the current time on the website, if we need this at some point.

looks good :up:


text:
Set/Retrieve value in BAS from native application.

I found few helper functions, but there's no documentation on the arguments they intake.
Therefore i few questions.

How can i set a 'test=2' value or pass value from native C application to the BAS ?
How can i retrieve the value of 'test' to process in native application after the BAS is executed ?

 struct mb_interpreter_t* bas = NULL;
  mb_init();
  mb_open(&bas);
  if (mb_load_string(bas, "test = 1+2+3; print test", true) == MB_FUNC_OK)
  {
    int iResult = mb_run(bas, true);

    mb_value_t val0;
    void **l = NULL;
    int iRes = mb_get_value_by_name(bas,l,"test",&val0);
    printf("VALU:%i RES:%i\n", val0.value.integer,iRes);
  }
  else
    printf("Failed\n");

6
VALU:0 RES:0

What are the arguments voidl**  in the following functions ?

MBAPI int mb_get_value_by_name(struct mb_interpreter_t* s, void** l, const char* n, mb_value_t* val);
MBAPI int mb_add_var(struct mb_interpreter_t* s, void** l, const char* n, mb_value_t val, bool_t force);
MBAPI int mb_get_var(struct mb_interpreter_t* s, void** l, void** v, bool_t redir);
MBAPI int mb_get_var_name(struct mb_interpreter_t* s, void* v, char** n);
MBAPI int mb_get_var_value(struct mb_interpreter_t* s, void* v, mb_value_t* val);
MBAPI int mb_set_var_value(struct mb_interpreter_t* s, void* v, mb_value_t val);

Found it myself
 void **l = NULL;
  struct mb_interpreter_t* bas = NULL;
  mb_init();
  mb_open(&bas);
  if (mb_load_string(bas, "test = 1+NATIVE; print test", true) == MB_FUNC_OK)
  {

    // Define a value
    mb_value_t valAdd;
    valAdd.type=MB_DT_INT;
    valAdd.value.integer = 1;
    mb_add_var(bas,l,"NATIVE",valAdd,true);

    // Run
    int iResult = mb_run(bas, true);
    printf("\n");

    // get value (NEEDS TO BE UPPERCASE)
    mb_value_t valGet;
    int iRes = mb_get_value_by_name(bas,l,"TEST",&valGet);
    printf("VALU:%i TYPE:%i RES:%i\n", valGet.value.integer,valGet.type,iRes);

  }
  else
    printf("Failed\n");

    mb_close(&bas);
    mb_dispose();

Interesting find. Two questions for @paladin-t maybe, at what point is void** l initialized? In the above example, it's first referenced at mb_add_var, does that write something to l? What does l even stand for? And, why does the name of a variable in mb_get_value_by_name need to be uppercase?

Lets' reopen to get more clarity on the follow up questions

void** l stores the program pointer, it is used to determine what's being executed and what will be next step internally. It is exposed to most API for manual save/restore externally sometimes.
The full flow might be following in some cases:

BASIC calls a native API
the native API calls mb_add_var
if there's any error, mb_add_var reports it with the current program position retrieved from void** l

mb_get_value_by_name expects uppercase due to a historical reason. BASIC is case-insensitive, and MY-BASIC stores almost everything in uppercase, then mb_get_value_by_name was introduced at some timepoint after that.

Thanks very much.

authors: iUltimateLP invpe paladin-t


text:
Unicode Printing Issue

Trying out the unicode example in the Wiki, I get this output on Windows 10:

, 5

Unicode characters are saved in UTF-16, GBK, etc rather than UTF-8 by many editors on Windows. Try re-saving it in UTF-8, it will work as expected.

I did and using sublimetext, set to utf-8. I assume this would also involve setting the localization and not working directly since it is printing to the console.

I will make a full debug when I get back to my win 10 in a few days.

Updated, please try again.

No longer blank, but I get this now:
Σ╜áσÑ╜Σ╕ûτòî
πüôπéôπü½πüíπü», 5


text:
Improve error handling

Errors are currently hard to catch, they’re not strongly typed so I had to let my code throw the error first, then find the name, then add an catch clause to check for that error name
Being able to do instance checking would be much nicer
if isinstance(e, ResourceNameAlreadyExistsError):
    ...

or at least an enum of error types per namespace:
if e.name == core.Errors.RESOURCE_NAME_ALREADY_EXISTS:
    ...

or something like:
if isResourceNameAlreadyExistsException(e):
    ...

There is ongoing work to improve error handling in both the Python SDK but also the API in general. I'll keep this FR up-to-date when this feature has been released. We'll likely be going with the first option where we subclass PalantirRPCException for each error.

authors: jettdc jsmith

repo: palantir/foundry-platform-python


text:
FailoverFeignTarget uses ThreadLocalInteger so will be biased to 0th server

Especially when you're running inside a server, where each request gives you a new thread.
@bavardage pointed this out in a stemma PR.

(if you're making new threads...)
for a small-ish fixed threadpool, should be fine?

fixed

repo: palantir/http-remoting


text:
Copy dataframe to ensure arrow metadata is properly set

We've seen issues when attempting to write back a dataframe read from Foundry using palantir::read_table. This seems to be caused by a bug in arrow which doesn't set the metadata properly: simply copying the dataframe resolves the issue.

Released 0.5.0

authors: AlexandreGuinaudeau svc-autorelease

repo: palantir/palantir-r-sdk


text:
Custom CatalogFileIndex

@pwoody
not quite sure if we want to specify the factory to avoid reflection on every datasource creation

Yeah I think we should just clean up the reflection and just create a factory interface that can produce with a .create(sparkSession, table, sizeInBytes): CatalogFileIndex

repo: palantir/spark


text:
Don't error for misplaced braces for 'else' if there are no braces

Fixes #400.
PR checklist

[X] Addresses an existing issue: #400
[X] New feature, bugfix, or enhancement

[X] Includes tests

[ ] Documentation update

What changes did you make?
Stop one-line from reporting an error for else when there are no braces.

@andy-hanson thanks!

repo: palantir/tslint


text:
Fix typo

PR checklist

[ ] Addresses an existing issue: #0000
[ ] New feature, bugfix, or enhancement

[ ] Includes tests

[X] Documentation update
[X] Enable CircleCI for your fork (https://circleci.com/add-projects)

What changes did you make?
Fixed a typo.

Your tests are failing even though your fork appears to pass when merged. I think you might need to clear the cache in CircleCI


text:
Allow for searching by taxonomic rank through /taxa route

Something like this...
/data1.2/taxa/list.json?rank=family
/data1.2/taxa/list.json?rank_no=25
Currently rank can be used to further filter a query for a specific taxnomic group. What I'm looking for is not a filter, but rather being able to pull a list of all families/genera etc.

Never mind this is my mistake. We can already do this.

repo: paleobiodb/pbdb-new


text:
Scaffolding filters with polymorphic inheritance leads to AttributeError

Hi!
I'm getting 'Join' object has no attribute 'name' error when trying to add inherited object as one of the column filters.
visible_name = '%s / %s' % (self.get_column_name(attr.prop.target.name),
                                                self.get_column_name(p.key))

If you look here, you may notice, that attr.prop.target may be a JOIN object - that's my case when I've got a Candidate model as a child of User model, trying to implement it as a column filter.
class User(db.Model):
    __mapper_args__ = {
        'polymorphic_identity': 'user',
        'polymorphic_on': role,
    }

class Candidate(User):
    __mapper_args__ = {
        'polymorphic_identity': 'candidate',
    }

from flask_sqlalchemy import SQLAlchemy
from flask_admin.contrib.sqla import ModelView

db = SQLAlchemy()

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    role = db.Column(db.String(50))

    __mapper_args__ = {
        'polymorphic_identity': 'user',
        'polymorphic_on': role,
    }

class Candidate(User):
    __mapper_args__ = {
        'polymorphic_identity': 'candidate',
    }

class MyModelView(ModelView):

    def scaffold_filters(self, name):
        filters = []
        for attr in self.model._sa_class_manager.mapper.iterate_properties:
            if hasattr(attr, 'direction'):
                if hasattr(attr.prop, 'target'):
                    # Check if attr.prop.target is a join object
                    if isinstance(attr.prop.target, db.Table):
                        visible_name = '%s / %s' % (self.get_column_name(attr.key), attr.prop.target.name)
                    else:
                        visible_name = '%s / %s' % (self.get_column_name(attr.prop.target.name),
                                                    self.get_column_name(attr.key))
                    filters.append((attr.key, visible_name))
                else:
                    filters.append((attr.key, self.get_column_name(attr.key)))
            else:
                filters.append((attr.key, self.get_column_name(attr.key)))
        return filters

    def get_column_name(self, name):
        # Customize column names as needed
        return name.capitalize()

# Add your views to the admin
from flask_admin import Admin
from flask import Flask

app = Flask(__name__)
app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///mydatabase.db'
app.config['SQLALCHEMY_TRACK_MODIFICATIONS'] = False
db.init_app(app)

admin = Admin(app)
admin.add_view(MyModelView(User, db.session))
admin.add_view(MyModelView(Candidate, db.session))

if __name__ == '__main__':
    app.run(debug=True)

authors: ljluestc yujinio

repo: pallets-eco/flask-admin


text:
pymongo v4 support + bug fixes

pymongo 4.0 required operators in update func
fixed comparison between datetime and document expiration

I've decided to just make my own version as this one seems to be dead.

Hi @zachlagden I have put in some time over the last few weeks attempting to get his repo up to date (It was not originally made by me) and we should have a release soon. If you would like to test my changes on Development branch that would be very helpful.

Hi @zachlagden I have put in some time over the last few weeks attempting to get his repo up to date (It was not originally made by me) and we should have a release soon. If you would like to test my changes on Development branch that would be very helpful.

oh yeah for sure man, I'll take a look

authors: Lxstr zachlagden

repo: pallets-eco/flask-session


text:
raise TypeError when duplicate flags are used

fixes #1465

Looks like a duplicate of #1594

repo: pallets/click


text:
Identify the common API between Flask and Blueprint classes

Blueprints are supposed to provide a very similar API to the Flask object itself, the difference being that Blueprints defer registration until later. Currently, blueprints can only be registered on apps, they're not nestable, and apps can't be registered with other apps, but this is something that #593 and #1548 want to change.
Blueprint and Flask do derive from helpers._PackageBoundObject, but this is mostly concerned with managing static files, templates, and other resource files. I think identifying the common API between the two and extracting it to a common base class may be a good step towards understanding how we can support app and blueprint nesting. Hopefully, it may at least make the code cleaner and easier to maintain.

Hey! Can I work on this?

Please i have an issue running the docker-compose file on my ubuntu terminal

Hi, maybe Flask have this functionality?
https://flask.palletsprojects.com/en/1.1.x/patterns/appdispatch/
I think this good idea, only Flask -> Blueprint.
If you need to expand the application, then use from werkzeug.middleware.dispatcher import DispatcherMiddleware.

`
class NewBlueprint(Blueprint):
def register_blueprint(self, blueprint, **options):
def deferred(state):
blueprint.name = f'{state.blueprint.name}.{blueprint.name}'
options['url_prefix'] = f'{state.url_prefix or ""}{options.get("url_prefix", blueprint.url_prefix) or ""}'
state.app.register_blueprint(blueprint, **options)
self.record(deferred)
def register(self, app, options, first_registration=False):
    self.record(self._prepare_before_request_funcs)
    self.record(self._prepare_after_request_funcs)
    super().register(app, options, first_registration=first_registration)

def _prepare_before_request_funcs(self, state):
    self._prepare_request_funcs(state, state.app.before_request_funcs)

def _prepare_after_request_funcs(self, state):
    self._prepare_request_funcs(state, state.app.after_request_funcs)

def _prepare_request_funcs(self, state, funcs):
    if '.' not in state.blueprint.name:
        for name in funcs:
            if name is not None and name.startswith(state.blueprint.name) and '.' in name:
                parent_name = '.'.join(name.split('.')[:-1])
                funcs[name] = funcs.get(parent_name, []) + funcs.get(name, [])

`

Hi, this way is correct?
from flask import Flask, Blueprint

class NewBlueprint(Blueprint):
    def register_blueprint(self, blueprint, **options):
        def deferred(state):
            blueprint.name = f'{state.blueprint.name}.{blueprint.name}'
            options['url_prefix'] = f'{state.url_prefix or ""}{options.get("url_prefix", blueprint.url_prefix) or ""}'
            state.app.register_blueprint(blueprint, **options)
        self.record(deferred)

    def register(self, app, options, first_registration=False):
        self.record(self._prepare_before_request_funcs)
        self.record(self._prepare_after_request_funcs)
        super().register(app, options, first_registration=first_registration)

    def _prepare_before_request_funcs(self, state):
        self._prepare_request_funcs(state, state.app.before_request_funcs)

    def _prepare_after_request_funcs(self, state):
        self._prepare_request_funcs(state, state.app.after_request_funcs)

    def _prepare_request_funcs(self, state, funcs):
        if '.' not in state.blueprint.name:
            for name in funcs:
                if name is not None and name.startswith(state.blueprint.name) and '.' in name:
                    parent_name = '.'.join(name.split('.')[:-1])
                    funcs[name] = funcs.get(parent_name, []) + funcs.get(name, [])
            print(funcs)

app = Flask(__name__)

@app.before_request
def app_before_request():
    print(app_before_request.__name__)

api = NewBlueprint('api', __name__, url_prefix='/api')

@api.before_request
def api_before_request():
    print(api_before_request.__name__)

v1 = NewBlueprint('v1', __name__, url_prefix='/v1')

@v1.before_request
def v1_before_request():
    print(v1_before_request.__name__)

account = NewBlueprint('account', __name__, url_prefix='/account')

@account.before_request
def account_before_request():
    print(account_before_request.__name__)

@account.after_request
def account_after_request(resp):
    print(account_after_request.__name__)
    return resp

@account.route('/')
def account_index():
    return account_index.__name__

project = NewBlueprint('project', __name__, url_prefix='/project')

@project.before_request
def project_before_request():
    print(project_before_request.__name__)

@project.route('/')
def project_index():
    return project_index.__name__

v1.register_blueprint(account)
v1.register_blueprint(project)
api.register_blueprint(v1)
app.register_blueprint(api)
app.run()

{None: [<function app_before_request at 0x00AEE738>], 'api': [<function api_before_request at 0x038ACDB0>], 'api.v1': [<function api_before_request at 0x038ACDB0>, <function v1_before_request at 0x038ACE88>], 'api.v1.account': [<function api_before_request at 0x038ACDB0>, <function v1_before_request at 0x038ACE88>, <function account_before_request at 0x038ACF60>], 'api.v1.project': [<function api_before_request at 0x038ACDB0>, <function v1_before_request at 0x038ACE88>, <function project_before_request at 0x038B61E0>]}
{'api.v1.account': [<function account_after_request at 0x038ACED0>]}

@davidism
Thanks for clarification.

Hi all,
Can I work on this issue?

Here's an example of what I'm thinking of. Flask and Blueprint both have a before_request decorator. They both take a function and record it. The difference is how they're recorded. The app stores them in a dict of lists, the blueprint records a lambda that runs the first time its registered.
add_url_rule is again different in both, the app registers the route with the map, the blueprint records a lambda. But route is implemented exactly the same in both, it only calls add_url_rule.
So a theoretical _FlaskCommon (need a better name) would define before_request and route and implement them as Flask does, then Blueprint would override route to store things for later instead of registering the route (since a blueprint doesn't have a route map).
class _FlaskCommon:
    def __init__(self, ...):
        self._before_request_funcs = {}

    def before_request(self, f):
        self._before_request_funcs.setdefault(None, []).append(f)

    def add_url_rule(self, ...):
        raise NotImplementedError

    def route(self, ..., **kwargs):
        def decorator(f):
            self.add_url_rule(view_func=f, **kwargs)
            return f

        return decorator

class Flask(_FlaskCommon):
    def add_url_rule(self, ...):
        ...

class Blueprint(_FlaskCommon):
    def add_url_rule(self, ...):
        ...

@YKo20010 and I will be working on this! 👍

I want to learn
On Wed, Jul 22, 2020, 1:35 PM Chris N. notifications@github.com wrote:

@YKo20010 https://github.com/YKo20010 and I will be working 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/pallets/flask/issues/3215#issuecomment-662617549, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANGF7MU2UMETV5XI7JSNLO3R44WQZANCNFSM4HPRXZ5A
.

Is there any way for you to trace who has been hacking me?
On Tue, Jul 28, 2020, 4:04 PM David Alton altondavid3@gmail.com wrote:

I want to learn
On Wed, Jul 22, 2020, 1:35 PM Chris N. notifications@github.com wrote:

@YKo20010 https://github.com/YKo20010 and I will be working 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/pallets/flask/issues/3215#issuecomment-662617549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANGF7MU2UMETV5XI7JSNLO3R44WQZANCNFSM4HPRXZ5A
.

@david-stack Stop posting crap. Thanks.

Hey man I'm not posting someone hacked my GitHub cyberspace-max . Thanks
On Tue, Jul 28, 2020, 4:16 PM Adrian notifications@github.com wrote:

@david-stack https://github.com/david-stack Stop posting crap. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pallets/flask/issues/3215#issuecomment-665287511, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANGF7MVKZDXQ2JKLMZFYCELR545ZZANCNFSM4HPRXZ5A
.

authors: Maksych ThiefMaster anirudhnarayanan chrisngyn david-stack davidism sridk thecraftman

repo: pallets/flask


text:
url_for() does not percent encode /

url_for does not percent encode /
from flask import Blueprint, url_for, Flask

bp = Blueprint('test', __name__)

@bp.route('/bogus')
def bogus():
    pass

app = Flask(__name__)
app.register_blueprint(bp)

with app.test_request_context("/bogus"):

    url = url_for('test.bogus', query="bob smith")
    print(url)
    assert url != "/bogus?query=bob smith"

    url = url_for('test.bogus', query="bob/smith")
    print(url)
    assert url != "/bogus?query=bob/smith"

$ python --version
Python 3.10.6
$ pip show flask
Name: Flask
Version: 3.0.0
Summary: A simple framework for building complex web applications.
Home-page:
Author:
Author-email:
License:
Location: /home/xxx/.pyenv/versions/3.10.6/envs/flask30/lib/python3.10/site-packages
Requires: blinker, click, itsdangerous, Jinja2, Werkzeug
Required-by:
$ python test.py
/bogus?query=bob+smith
/bogus?query=bob/smith
Traceback (most recent call last):
  File "/home/xxx/src/flaks30/test.py", line 22, in <module>
    assert url != "/bogus?query=bob/smith"
AssertionError

Expected that / would be percent encoded as specified in RFC3986
https://datatracker.ietf.org/doc/html/rfc3986#section-2.1
I believe this is a regression because I have a unit test that fails with this version of Flask but passed with earlier versions.
Environment:

Python version: 3.10.6
Flask version: 3.0.0

That character does not need to be escaped in the query party of a URL, because the path part has ended at that point. See https://url.spec.whatwg.org/ for the current URL standard.


text:
Declare support for Python 3.8

Hello,
Python 3.8 is released, so I believe that it would be nice to declare support for it.
Python 3.8.0 release announcement:
https://discuss.python.org/t/python-3-8-0-is-now-available/2478
Best regards!
P.S. Unfortunately, Azure Pipelines don't support Python 3.8 yet.
https://github.com/microsoft/azure-pipelines-image-generation/issues/1317

Thanks. I can't merge this until a CI entry is added.
Please check the docs to ensure 3.8 is mentioned as a supported version.

authors: Jamim davidism


text:
authorization parsing should catch base64 errors

Steps to reproduce
>>> from werkzeug.datastructures import Authorization
>>> Authorization.from_header("Basic foo")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/private/tmp/.venv/lib/python3.11/site-packages/werkzeug/datastructures/auth.py", line 109, in from_header
    username, _, password = base64.b64decode(rest).decode().partition(":")
                            ^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/python@3.11/3.11.3/Frameworks/Python.framework/Versions/3.11/lib/python3.11/base64.py", line 88, in b64decode
    return binascii.a2b_base64(s, strict_mode=validate)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
binascii.Error: Incorrect padding

Expected behavior
I would expect Werkzeug to handle this situation and return None.
Environment

Python version: 3.11.3
Werkzeug version: 2.3.4

I've updated the title to describe the actual issue you're asking to fix.

authors: ckoehn davidism

repo: pallets/werkzeug


text:
doesn't send uuid type parameters

Actual Behavior
operator does not exist: uuid = character varying
Steps to Reproduce the Problem
 const result = await connection.query(
  'select * from users where uid = $1',
  {values: ['3f680a7f-6f86-11eb-bd8b-02004c4f4f50']});

Specifications

Version: 1.14.0

Fixed in version 1.14.1

authors: erayhanoglu mutavci

repo: panates/postgresql-client


text:
About this

Hi. Your project looks really cool. Is it supposed to be something like Skript? So a Minecraft plugin. If so, do you have a JAR file, or do I need to compile it myself?
Thanks,
Daniel

Hey @Dmunch04,
The Light is independent programming language based on Panda Framework. Unfortunately, at this moment we are focused on Panda, Reposilite and panda-lang website to built whole environment structure. It's also required for Light to have these foundations. There are also some plans to support Minecraft (https://github.com/dzikoysk/lightmc <-- really old)

Oh okay. The example just really looks like something from Skript. Well sounds cool. I'll keep an eye out!
Thanks

The example in README is just a concept ofc. At this moment the syntax looks like https://github.com/panda-lang/light/blob/master/examples/current_test.light
I think that Light should get updates after release of alpha version of Panda.

repo: panda-lang/light


text:
Migrate big blogs of text into PANDA.text.*

Or even PANDA.trans.en.*

Nevermind, the need for this is obviated by moving the tooltips into inline templates. Better solution for now.

repo: pandaproject/panda


text:
Integrate Seasonal Ingredients for Sustainability Education

Description:
As part of our game's educational goal on sustainability, integrating a mechanic that emphasizes the use of seasonal and local ingredients is crucial. This feature will teach players about the environmental benefits of seasonal cooking and encourage strategic thinking around ingredient selection. While optional, this mechanic could enrich the gameplay experience and reinforce the game's sustainability theme.
Acceptance Criteria:

Development of a seasonal ingredient system that changes available ingredients based on in-game seasons.
Educational pop-ups or tips that explain the benefits of using seasonal ingredients.
Bonus points or rewards for dishes that utilize seasonal ingredients effectively.
Optional: A visual indicator or filter in the recipe book for seasonal ingredients.

#48


text:
Availability of baseline model

Hi @bowenliu16!
The paper associated with this repository describes a baseline model with "2868 unique retrosynthetic reaction rules, defined by SMARTS strings." Is that baseline model available in this repository or elsewhere?
Thanks!

Hi @rmcgibbo!
The baseline that we adapted can be found here:
https://github.com/connorcoley/ochem_predict_nn


text:
Use markdown instead of rst for basic text files

Markdown is designed to be readable without being compiled, while RST is more focused on the compiled output.
Top level text files, such as the changelog, README, contributing info, are often not going to be rendered and will be looked at as plain text and so should be in Markdown format.
The documentation under docs should remain as rst since it is primarily used to render the documentation output.

I'd be fine with either of these changes. We may decide to move the changelog and contributing info to the documentation, in which case, it may make more sense to keep them as RST. I don't have strong feeling here either way though.

Makes sense, I moved contributing entirely to the docs, and then references that from the README.
The changelog I changed to .md as I think the vast majority of readers are going to look at this as a text file or rendered in GitHub.
Closing as resolved.

authors: jhamman matthewhanson

repo: pangeo-data/intake-stac


text:
Add jupyter-sshd-proxy

Over at LEAP we have been testing https://github.com/yuvipanda/jupyter-sshd-proxy (thanks @yuvipanda )and it works really nicely to connect to cloud hubs e.g. using vscode. I think this is a pretty broadly requested functionality and thus would be a good addition here.
Not sure about the pip dependency in this file. Should live somewhere else?
cc @dhruvbalwada

/condalock

Thanks folks! Appreciate the quick turnaround!

repo: pangeo-data/pangeo-docker-images


text:
Do Not Alert on Child Documents When Parent Folder Permissions Update

Background
Drive will create an alert for every document contained within a folder as they inherit permissions from a change to the parent folder permissions. We do not want to alert on every document in that folder as that is only noise.
Changes
In visibility change rule added tuple containing log event titles that indicate the inherited permissions update, then returned False for any event matching those types
Testing
Created two new unit tests based on events from security.panther.tools, test suite passes with old and new tests
https://app.asana.com/0/1200819885715474/1200720820393300/f

Nice!

You might already know this, but if you add "Closes <asana_urL>" to the description there is an automation that will move the task to "in review" when the PR opens and then will auto close the task when the PR merges. There are other keywords too like "Relates to" which won't auto-close the task.

I did not know that! Thank you for the tip 😄

repo: panther-labs/panther-analysis


text:
Release 1.4.0

docket:

Complete manylinux support in pex. (#480)
Add manylinux wheel support and fix a few bugs along the way (#316)
Skip failing tests on pypy shard. (#478)
Bump travis image to Trusty. (#476)
Mock PATH for problematic interpreter selection test in CI (#474)
Skip two failing integration tests. (#472)
Better error handling for missing setuptools. (#471)
Add tracebacks to IntegResults. (#469)
Fix failing tests in master (#466)
Repair isort-check failure in master. (#465)
Repair style issues in master. (#464)
Fixup PATH handling in travis.yml. (#462)

notably, this release ships with full support for #281

this is complete: https://pypi.org/project/pex/1.4.0

repo: pantsbuild/pex


text:
Handle locking all direct reference URL forms.

Previously, it was assumed that direct reference URLs were either VCS
URLs or else wheel or sdist URLs. This neglected two remaining cases,
both of which failed to lock with better or worse error messages. The
two missed cases were:

URLs of source archives not conforming to the sdist quasi-standard
naming convention of <project name>-<version>.{.tar.gz,.zip}.
Local file:// URLs pointing at project directories.

A notable case of the 1st are project archives provided by GitHub.
A notable need for the 2nd case comes from Pants where Pip proprietary
requirement strings are not handled (e.g.: /path/to/project) and a
direct reference URL must be used instead (e.g.: projectname @ file:///path/to/project).
Fixes #2057

This last commit represents a very large change. I'll may close this out after vetting green across the various Pip permutations checked by CI and post a new PR with the changes split up.

Alright 83583e2 is now solid. PTAL.


text:
The "Service" does not show consumers, in the "Eligible Consumers" section

The "Service - httpin3" have a ACL plugin active and the consumer is in the same group.
My version is 0.12.0 and Kong is 0.14.
However, this problem does not occur with the "Routes".
Regards.

Since the servise has no acls or auth plugins attached, It means all consumers are eligible.
No point of showing them.

authors: pabduran pantsel

repo: pantsel/konga


text:
⚠ Feedaty widget has degraded performance

In 383c2cd, Feedaty widget (https://widget.feedaty.com/public/js/feedaty.js?merchant=10213975&style_ver=2021&data-sku=36263) experienced degraded performance:

HTTP code: 200
Response time: 1597 ms

Resolved: Feedaty widget performance has improved in d4f9a8b after 11 minutes.

repo: papies/upptime


text:
Install importlib_metadata in the virtualenv

Hello,
I'm currently experiencing a small issue (not a blocking one at all).
I started to use coc, with coc-jedi using a python version >=3.8 and that worked perfectly.
But recently, I launched vim inside a project which uses python 3.6.6. And update coc plugins.
Seems like coc-jedi needed an update (and jedi-language-server too was outdated). So coc-jedi ran the update but it ran it using the python 3.6.6 interpreter.
So the virtualenv created is based on python 3.6.6 and now each time coc-jedi starts to run, it tries to get the version, but it cannot retrieve it because if we're below 3.8, we have to use importlib_metadata (see here) which is not installed. So it recreate the virtualenv each time.
I can fix the issue either by:

reinstalling coc-jedi using a python version > 3.8
install importlib_metadata inside actual coc-jedi virtualenv (which will break once new update is installed if I'm using python <3.8 interpreter)

Can we add importlib_metadata package installation inside the virtualenv? Or maybe there is another solution :)
Anyway, thanks for the plugin!

Should be resolved in version 0.25.2!

Works perfectly, thanks for the quick fix!

authors: Fenkiou pappasam

repo: pappasam/coc-jedi


text:
Update notebooks

Provides more thorough explanations, renames some titles for clearer concepts, fixes some typos and deletes some spare texts.

Gracias @nimbusaeta, aprobado!!!

authors: chucheria nimbusaeta

repo: paradigmadigital/Promptmeteo


text:
feat: launch with experimental engine

Description
Launch alphanet node with experimental engine by default.

Current plan:

After bumps on Reth (and in turn Alphanet), we rebase this branch on top of main to get the latest EIPs working
I'll open up a PR based off of this one with engine payload validator fixes, which will allow op-node to post payloads over engine v3 while Prague is active. Currently these payloads would be rejected because requests_root would be missing
@Rjected to bump op-node deps as well
Finally, we run Kurtosis on this branch to check if engine experimental works

Point 1 is done and point 2 seems like it doesn't need more work for now, the chain is progressing on Kurtosis. Point 3 is done as well

authors: onbjerg rkrasiuk

repo: paradigmxyz/alphanet


text:
Upstream reth_primitives::{Chain,NamedChain} to Alloy

The NamedChain enum is not sustainable and requires too much maintenance for a single crate. We should be able to define a few core chains (like Eth mainnet and testnets), and let users define their own.
Current ideas:

Chain trait to integrate with a future Network alloy trait (?)
Chain struct with a global registry
...

See: https://github.com/alloy-rs/chains
cc @gakonst @Evalir @mattsse @prestwich

This has been temporarily mitigated by #4808, where we re-implemented a small fraction of the ethers_core::types::Chain methods and variants as reth_primitives::NamedChain.

repo: paradigmxyz/reth


text:
Implement p2p related tools

Describe the feature
There are some p2p related tools geth, like:
https://geth.ethereum.org/docs/tools/devp2p
https://github.com/ethereum/go-ethereum/tree/master/p2p/simulations
If it's meaningful to implement related tools in reth, I'd like to do it!
@mattsse @emhane WDTY?
Additional context
No response

sgtm!
if you want, you can add these as standalone crates first

devp2p command TODO list:

enrump: Pretty-prints node records

[ ] enrdump

key: Operations on node keys

[ ] generate: Generate node key files
[ ] to-id: Create a node ID from a node key file
[ ] to-encode: Creates an encode URL from a node key file
[ ] to-enr: Creates an ENR from a node key file

discv4: Node Discovery v4 tools

[ ] ping: Sends ping to a node
[ ] requestenr: Requests a node record using EIP-868 enrRequest
[ ] resolve: Finds a node in the DHT
[ ] resolve-json: Re-resolves node in a nodes.json file
[ ] crawl: Updates a nodes.json file with random nodes found in the DHT
[ ] test: Runs tests against a node

discv5: Node Discovery v5 tools

[ ] ping: Sends ping to a node
[ ] resolve: Finds a node in the DHT
[ ] crawl: Updates a nodes.json file with random nodes found in the DHT
[ ] test: Runs test against a node
[ ] listen: Runs a node

dns: DNS Discovery Commands

[ ] sync: Download a DNS discovery tree
[ ] sign: Sign a DNS discovery tree
[ ] to-txt: Creates a DNS TXT records for a discovery tree
[ ] to-cloudflare: Deploy DNS TXT records to CloudFlare
[ ] to-route53: Deploy DNS TXT records to Amazon Route53
[ ] nuke-route53: Deletes DNS TXT records of a subdomain on Amazon Route53

nodeset: Node set tools

[ ] info: Show statistics about a node set
[ ] filter: Filters a node set

rlpx: RLPx Commands

[ ] ping: ping
[ ] eth-test: Runs eth protocol tests against a node
[ ] snap-test: Runs snap protocol tests against a node

for sure! really nice idea

I'd tackle each  todo as a separate new issue, adding to task list here. that way it's easier for us to review, more overseeable to give you specific hints for impl in that issue, and less merge conflicts with main for you since each topic branch would be short-lived.
a hint for discv5 already, is to use this method
https://github.com/paradigmxyz/reth/blob/ef3f67743d517b2b15692949efae4671168bccbd/crates/net/discv5/src/lib.rs#L381-L387
and then read the sigp Discv5 public api thoroughly, should be possible to impl all commands with those existing methods
https://github.com/sigp/discv5/blob/master/src/discv5.rs

make sure to try this tool out first https://github.com/AgeManning/discv5-cli, no need to impl same thing again in reth imo

agree, as well as enr-cli: https://github.com/agemanning/enr-cli
cargo install makes using these really easy

agree, as well as enr-cli: https://github.com/agemanning/enr-cli

true this tool exists too
I updated your list @int88 based on review https://github.com/paradigmxyz/reth/pull/8403#pullrequestreview-2102458098 and https://github.com/paradigmxyz/reth/pull/8403#pullrequestreview-2102435753

Thanks for all of your kind reviews @mattsse @Rjected @emhane .
So I would implement the commands filtered by @emhane .
One last concern, should these commands should be integrated into reth p2p or as a separate binary?
IMO, I agree with @Rjected , integrated into reth p2p maybe better :)

One last concern, should these commands should be integrated into reth p2p or as a separate binary?

yes, see the text I added to the list in bold @int88. check out how it is done for the db subcommand clear with subsubcommands mdbx and static-file
https://github.com/paradigmxyz/reth/blob/e0c22ace34e520b6276af2f54acb634363b7979f/bin/reth/src/commands/db/clear.rs#L13-L16
so for example, p2p would be the command, rlpx is a subcommand (like clear), and ping is a sub subcommand (like mdbx)

@int88 focus on rlpx
ok so, going through this in more detail, regarding the remaining rlpx commands:

the ping command would be nice to have! which would somehow access P2PStream::send_ping via a new p2p sub command for rlpx https://github.com/paradigmxyz/reth/blob/e97e379e43b69e15d8dcea14d60f3d791be72328/crates/net/eth-wire/src/p2pstream.rs#L304-L307
eth tests are run in hive using rpc, right @Rjected ?
we don't have support for live snap sync yet.

in general, it would be nice to have a complete rlpx command, to manually send all the EthMessages.

authors: Rjected emhane int88 mattsse


text:
feat(cli): add implementation for verbose flag

Previously the --verbose flag wasn't really doing anything. This PR adds the functionality needed for it to work.
Brief explanation: without specifying the flag, the default is error level tracing, and for each one specified thereafter, the level increases, up to trace level at a count of 4.

Codecov Report

Merging #541 (b2f434a) into main (c2ad7b1) will increase coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #541      +/-   ##
==========================================
+ Coverage   72.54%   72.58%   +0.03%
==========================================
  Files         243      243
  Lines       24589    24598       +9
==========================================
+ Hits        17838    17854      +16
+ Misses       6751     6744       -7

Impacted Files
Coverage Δ

bin/reth/src/cli.rs
0.00% <0.00%> (ø)

bin/reth/src/util/mod.rs
0.00% <0.00%> (ø)

crates/net/discv4/src/lib.rs
51.61% <0.00%> (-0.10%)
:arrow_down:

crates/primitives/src/forkid.rs
96.01% <0.00%> (-0.08%)
:arrow_down:

crates/transaction-pool/src/pool/txpool.rs
58.73% <0.00%> (+0.52%)
:arrow_up:

crates/transaction-pool/src/test_util/mock.rs
60.37% <0.00%> (+6.66%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: MegaRedHand codecov-commenter


text:
Save As - Save a file into a different project

Split out from #108

Labelled as UX because we need to understand how the process should be visualized for the user, especially on tablet or mobile devices.

This is related to issue #154.

authors: PropGit phated urbantumbleweed

repo: parallaxinc/Parallax-IDE


text:
Issue with code comment

The following comment seems to be wrong:
https://github.com/parallaxsecond/rust-cryptoki/blob/916f9bbb208ba8a671c593a36313f09c60cd0255/cryptoki/src/functions/slot_token_management.rs#L86-L87
32 is used not because it's a code for space but because the spec requires 32 bytes. Also: the space is encoded as a first argument (b' ') as the it is required that the label is space-padded.

I digged hard to find the reason for this but found it here 😆
Forgot to remove the comment so now it's very confusing. You are right, should be removed!

authors: hug-dev wiktor-k

repo: parallaxsecond/rust-cryptoki