Configure Azure pipelines

This configuration builds the application and produces builds for both Debug and Release configurations.

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


Normalize extra_vars support for Ansible Tower playbooks.

Refactor the support of extra_vars for ServiceAnsiblePalybook and automate playbook method.
Add extra_vars support for ServiceAnsibleTower.

Includes https://github.com/ManageIQ/manageiq-automation_engine/pull/244
Fixes https://github.com/ManageIQ/manageiq/issues/18005.
@miq-bot assign @gmcculloug
@miq-bot add_label enhancement, services
cc @mkanoor

@lfu @mkanoor Should these changes be linked to https://bugzilla.redhat.com/show_bug.cgi?id=1611946
Can we solve the automate_workspace  issue from that ticket (see https://bugzilla.redhat.com/show_bug.cgi?id=1611946#c16) with these changes?

@lfu - Regarding @gmcculloug's comment it seems there would need to be the addition of the automate_workspace key in the manageiq_connection hash to solve that issue.

@gmcculloug @syncrou Regarding ServiceAnsiblePalybook, this PR only refactor the existing code for extra_vars which won't fix the issue in https://bugzilla.redhat.com/show_bug.cgi?id=1611946.

Tested with Ansible Tower Service, Ansible Playbook Service and automate playbook method. manageiq_env and manageiq_connection_env hashes were added into playbooks' extra_vars.

The playbook I used for testing is this one.


uv pip install fails from inside docker.

On my mac the install works just fine.
In docker though, I'm getting this error:
 => ERROR [builder  9/10] RUN --mount=type=ssh /root/.cargo/bin/uv pip install --system --no-cache -r requirements.txt   2.5s
------
 > [builder  9/10] RUN --mount=type=ssh /root/.cargo/bin/uv pip install --system --no-cache -r requirements.txt:
2.433 error: error sending request for url (https://northamerica-northeast2-python.pkg.dev/private-pypi-418615/ritual-pypi/simple/huggingface-hub/)
2.433   Caused by: client error (Connect)
2.433   Caused by: invalid peer certificate: BadSignature

This is my dockerfile:
# syntax=docker/dockerfile:1

# Comments are provided throughout this file to help you get started.
# If you need more help, visit the Dockerfile reference guide at
# https://docs.docker.com/engine/reference/builder/

ARG PYTHON_VERSION=3.11
FROM python:${PYTHON_VERSION}-slim as base

# Prevents Python from writing pyc files.
ENV PYTHONDONTWRITEBYTECODE=1

# Keeps Python from buffering stdout and stderr to avoid situations where
# the application crashes without emitting any logs due to buffering.
ENV PYTHONUNBUFFERED=1
ENV RUNTIME docker

WORKDIR /app

# Create a non-privileged user that the frenrug will run under.
# See https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#user
ARG UID=10001
RUN adduser \
    --disabled-password \
    --gecos "" \
    --home "/nonexistent" \
    --shell "/sbin/nologin" \
    --no-create-home \
    --uid "${UID}" \
    appuser

RUN apt-get update
RUN apt-get install -y curl

# Install UV
ADD --chmod=755 https://astral.sh/uv/install.sh /install.sh
RUN /install.sh && rm /install.sh

# Download dependencies as a separate step to take advantage of Docker's caching.
# Leverage a cache mount to /root/.cache/uv to speed up subsequent builds.
# Leverage a bind mount to requirements to avoid having to copy them into
# into this layer.
RUN --mount=type=cache,target=/root/.cache/uv \
    --mount=type=bind,source=requirements.txt,target=requirements.txt \
    /root/.cargo/bin/uv pip install --system -r requirements.txt

# Install some executables
RUN apt-get update \
    && apt-get install -y curl procps sysstat ifstat \
    && rm -rf /var/lib/apt/lists/*

# Copy the source code into the container.
COPY src/ src/
COPY entrypoint.sh .

# Run the application.
ENTRYPOINT ["/app/entrypoint.sh"]

Since I'm installing uv every time, it must use the latest version of uv.
It's using python's official docker, so I'm assuming the certificates are outdated whenever installing from a debian environment?

Same issue here, latest MacOS 14.5. I worked yesterday.

I have the same issue, small workaround is by using yesterday version
RUN curl -LsSf https://astral.sh/uv/install.sh -o install.sh
RUN sed -i 's/0.1.43/0.1.42/g' install.sh
RUN sh install.sh

if anyone has a better way to set the version I would gladly take it

Following @Max0u experiment, can install older version directly:
pip install uv==0.1.42

This works if you're already using the curl setup and don't want to make any other changes:
curl -LsSf https://github.com/astral-sh/uv/releases/download/0.1.42/uv-installer.sh | sh

Looking into this...

I did not reproduce this with
ARG PYTHON_VERSION=3.11
FROM python:${PYTHON_VERSION}-slim as base

RUN apt-get update
RUN apt-get install -y curl

ADD --chmod=755 https://astral.sh/uv/install.sh /install.sh
RUN /install.sh && rm /install.sh

RUN /root/.cargo/bin/uv pip install anyio --system

In my case, it fails on a different library in my requirements.txt file every time I run install.

Has anyone seen this behavior on a host machine other than macOS?

Okay I've confirmed

Does not occur on Linux host machines
Does reproduce on a macOS host machine

I'll look into the cause now.

I'm using
ADD --chmod=755 https://github.com/astral-sh/uv/releases/download/0.1.42/uv-installer.sh /uv-installer.sh
RUN /uv-installer.sh && rm /uv-installer.sh

For now

@zanieb https://github.com/astral-sh/uv/pull/3444 looks like it might affect SSL

I'll release a revert to that — it is indeed suspicious.

By downloading some intermediate artifacts I've confirmed reverting that resolves the issue. v0.1.44 is on its way out.

It's fixed for me now. Re-running the same docker image today works.

Thank you for this quick turnaround! I also pinned to previous to resolve, and was wondering why it wasn't affecting the Intel nodes. Makes sense!

Thanks for checking back in! Great to know it's resolved.


EventDispatcher set_handler and remove_handler do not use WeakMethod

Describe the bug
set_handler and remove_handler do not wrap methods in WeakMethod.  There are a few implications from this:

Using set_handler to register a handler method creates strong reference
Using set_handler to add, then remove_handlers (plural) to remove, will fail.  Because WeakMethod(self.method) != self.method
Switching between set_handler to set_handlers` changes this behavior.  From user's perspective, this is confusing.  The API and docs give the impression that this is a stylistic choice, not a behavioral change.

System Information:
How To Reproduce
from pyglet.event import EventDispatcher

class MyEventDispatcher(EventDispatcher): pass
MyEventDispatcher.register_event_type('on_foo')

class Observer:
    def on_foo(self):
        print('Observer.on_foo called')

    def log_foo_event(self):
        print('Observer.log_foo_event called')

print('Use-case A: When handler method and event names do not match, encouraging use of set_handler')
e = MyEventDispatcher()
o = Observer()
e.push_handlers()
e.set_handler('on_foo', o.log_foo_event)
e.dispatch_event('on_foo')
o = None
# Error: o is strongly held, handler will fire again
e.dispatch_event('on_foo')

print('---')

print('Use-case B: Subscribe using a different technique than unsubscribe')
e = MyEventDispatcher()
o = Observer()
e.push_handlers(o)
e.dispatch_event('on_foo')
e.remove_handler('on_foo', o.on_foo)
# Error: handler was not removed
e.dispatch_event('on_foo')

print('---')

Thanks for opening the ticket. There has already been a bit of work on refactoring the event module, but it has not yet been merged due to some issues with references:  https://github.com/pyglet/pyglet/tree/event_refactor
This was initially stated for 2.0, but got put on the back burner.

Thanks, is there an issue or PR tracking this work?  It could serve as a description of the intended changes.  As-is, it's not clear whether or not the refactor would change the behavior described in this issue.

The original pull request is here, which includes a description of the changes.
It actually was merged, but had to be revered at the last minute before pyglet 2.0 was released (so it didn't block the release).
The main issue (if I recall correctly), is that it was keeping some hard references that were preventing garbage collection.

@cspotcode As a quick immediate fix, the following should do it:
def my_set_handler(self, name, handler):
        if type(self._event_stack) is tuple:
            self._event_stack = [{}]

        if inspect.ismethod(handler):
            handler = WeakMethod(handler, partial(self._remove_handler, name))

        self._event_stack[0][name] = handler

EventDispatcher.set_handler = my_set_handler

If you have a chance, can you see if that fixes it for you as well?

a little ping, is this issue still exist?

Yes, this has not yet been fixed. It got overlooked :( but shouldn't be too difficult.


Update ClickHouse to <IP_ADDRESS>

Hi, @andyone.
Please, update ClickHouse to the latest version.

Looks good now, merged. Thanks!

The package was added to kaos-testing repository for CentOS 7.


Is it possible to use the autograph-compiled code on older Tensorflow versions?

Describe the problem
I have tried autograph on the nightly channel. It works and is very useful to me. I could not hope to write such code myself. However, it is not a very good idea to stay on the nightly channel for the whole time. Since autograph can generate the code, it seems natural to me to use such code and migrate back to a more stable channel.
However, the generated code doesn't seem to be readily usable. It contains unrecognized tokens like __ag. I cannot get past that. Is it even possible? Can you disclose some of the plans on that?

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce
Mobile device

@aquariusjay @alexbw can you comment on whether working at nightly is the intended use-method for AG, or reassign to someone who can, please?

Hey @phizaz great to hear that AutoGraph is useful to you. If you are able, we'd love if you could share the code that you used it in!
We're still actively working on AutoGraph, so to get the most out of it (before TF 2.0 is released), staying on nightly gets you the most bug-fixes and functionality.
However, if that's not possible, try using the 1.10 release or later.

@alexbw r1.10 doesn't seem to support list appending and tf.stack. However, I found it work on r1.11 (compiled from source).
I think I could share the code here, I simplify the code a bit:
@autograph.convert()
def chunkify(tensor, max_chunk_size):
    Agrs:
        tensor: the tensor to be chunked
        max_chunk_size: maximum size of a chunk
    """
    s = tf.shape(tensor)
    i = 0
    out = []
    autograph.set_element_type(out, tensor.dtype)

    while i < s[0]:
        # cut a new tensor
        t = tensor[i:i+max_chunk_size]

        ...

        out.append(t)
        i += max_chunk_size

    out = tf.stack(out)

    return out

@mdanatg

Nagging Assignee @aquariusjay: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @aquariusjay: It has been 30 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @aquariusjay: It has been 59 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @aquariusjay: It has been 76 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @aquariusjay: It has been 90 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Now that the stable release reached 1.13, I believe you will find the basic autograph functionality in the stable branch.


Compiler: make sure to remove literal types before instantiating matches

Fixes #6239
When initial lookup matches fail, we do a second lookup with "literal types", for the automatic cast. If there are matches, those literal types must be converted back to the real types (because those literal types are just used for the lookup, they are fictitious). This was done in a few places, but apparently not in all of them.
This PR changes the code to make sure that, before instantiating those matches, if the lookup was done with those literal types, they are removed.

Weird CI failure on macOS.


file.day does not work

What happened?
The file.day function does not work as expected under certain conditions.
Situation:
Consider the following files:

History/2024-01-01 Test1
History/2024-01-02 Test2
History/Backup/2024-01-03 Test3

I created the following query to retrieve the dates from the files under the History folder:
LIST file.day
FROM "History"

However, the file.day could not retrieve the date for the file located in the Backup folder.
Expected

2024-01-01 Test1: 2024-01-01
2024-01-02 Test2: 2024-01-02
2024-01-03 Test3: 2024-01-03

Actual

2024-01-01 Test1: 2024-01-01
2024-01-02 Test2: 2024-01-02
2024-01-03 Test3: -

DQL
LIST file.day
FROM "History"

JS
No response
Dataview Version
0.5.67
Obsidian Version
1.6.7
OS
Windows

Don't you mean file.cday / file.mday?
i don't see any file.day in the dataview docs!

Don't you mean file.cday / file.mday? i don't see any file.day in the dataview docs!

https://blacksmithgu.github.io/obsidian-dataview/annotation/metadata-pages/

@capitanhazel
I used file.day.
@haoduoyu
Thank you for the additional information!

The reason is unclear, but the symptoms are no longer recurring. Thank you.


createjs.com home page display a blank page when using Ghostery addon

CreateJS.com is ridiculously over dependant of typekit.net.
If typekit is down or blocked (like with the Ghostery addon/extension) the site displays a blank page.
Here is the log in the console (on chromium):
GET http://use.typekit.net/cek3iwo.js net::ERR_BLOCKED_BY_CLIENT
(index):2 Uncaught ReferenceError: Typekit is not defined

Adn the blank page (well, it's blank)

Thanks, we are definitely looking at replacements :)

I think this was solved ages ago when this bug surfaced. Checking before we close it.

I think this was solved ages ago when this bug surfaced. Checking before we close it.

Yep it was solved. Thanks again for the report :)


Add tool to upload to IBM Quantum Learning

This moves a custom tool from https://github.com/frankharkins/learning-content-tools to this repo as per request.
This tool is not actually used in this repo, it will just live here to be owned by the Qiskit organisation.

It's working! The API changed how it guessed file types, so I've specified it explicitly in d507f54dec94976f94698034eeed34dd005cc2b8. I've also added a test to simulate using the script so hopefully I can catch things like this in the future.


stop github actions from executing specific tasks on forks

Currently github actions keep sending me mails about things that should only run on the prometheus organisation actions. This change makes sure to check who owns the repository before running the CI workflow.
I'm not fully convinced that this is the correct action to take, but it can function as a discussion starter.
@roidelapluie

Is there an attribute that could run it if the repo is not a fork instead of hardcoding prometheus?

@roidelapluie to my knowledge there is no attribute that would allow us to differentiate like that. There is a feature request open on github action for something that would allow ignoring forks, but even there the initial idea seems to be hardcoding organisations/repos.

So after looking over some further documentation, it might be possible to insert a check based on gh repo view $(git config --get remote.origin.url) --json isFork to the CI workflow, which would cause it to only run when not on a fork.

Some tests seem to fail, but the 2 step process and checking the output result of gh CLI seems to work. Only question is … does everything have the “remote.origin.url”? 🤔

I am convinced we could hardcode     if: github.repository_owner == 'prometheus' for now.

rebased on main and switched to the hard-coded community check

Thanks!


Data Prepper - Pipeline Creations in Runtime

Is your feature request related to a problem? Please describe.
I wanted to have pipeline creation in runtime because as of now due to manually restarting the data prepper container doesn't full fill my need.
Describe the solution you'd like
As a solution, it would be great to have feature in which we can add, delete and edit the pipelines in running data prepper.

Related issue: https://github.com/opensearch-project/data-prepper/issues/973


feat: add vitepress preset

This PR includes:

vitepress preset: we need to add also vue to use composition-api
vitepress example
update pnpm-lock.yaml file to include vitepress  and esbuild-register dev dependencies

don't merge yet, missing vue dependency on vitepress example


TAnalysisTreeBuilder::SortFragmentTreeByTimeStamp: switched from std:…

…:multiset::insert to std::multiset::emplace

"emplace"? My compilation throws an error here:
Compiling .build/libraries/TGRSIAnalysis/TAnalysisTreeBuilder/TAnalysisTreeBuilder.o[ERROR]
In file included from /opt/root/include/TNamed.h:29,
                 from /opt/root/include/TDirectory.h:25,
                 from /opt/root/include/TDirectoryFile.h:25,
                 from /opt/root/include/TFile.h:28,
                 from /home/jsmith/packages/GRSISort/include/TAnalysisTreeBuilder.h:20,
                 from libraries/TGRSIAnalysis/TAnalysisTreeBuilder/TAnalysisTreeBuilder.cxx:1:
/opt/root/include/TString.h: In member function ‘TString& TString::operator+=(Long64_t)’:
/opt/root/include/TString.h:537: warning: ISO C++ does not support the ‘ll’ gnu_printf length modifier
/opt/root/include/TString.h: In member function ‘TString& TString::operator+=(ULong64_t)’:
/opt/root/include/TString.h:545: warning: ISO C++ does not support the ‘ll’ gnu_printf length modifier
libraries/TGRSIAnalysis/TAnalysisTreeBuilder/TAnalysisTreeBuilder.cxx: In member function ‘void TAnalysisTreeBuilder::SortFragmentTreeByTimeStamp()’:
libraries/TGRSIAnalysis/TAnalysisTreeBuilder/TAnalysisTreeBuilder.cxx:361: error: ‘class std::multiset<TFragment, std::less<TFragment>, std::allocator<TFragment> >’ has no member named ‘emplace’
make: *** [.build/libraries/TGRSIAnalysis/TAnalysisTreeBuilder/TAnalysisTreeBuilder.o] Error 1

Looks like this is a C++11 only function - that will explain it.

It works with gcc 4.9 using just c++0x, so I thought it would work for everyone, but apparently no such luck. One more reason to switch to modern compilers, I guess. We can revert it for now, and test in Guelph how much emplace helps with the performance?

We can also maybe write our own version of emplace for the time being. I can’t imagine it is that hard.

On Nov 20, 2015, at 11:13 PM, Vinzenz Bildstein<EMAIL_ADDRESS>wrote:
It works with gcc 4.9 using just c++0x, so I thought it would work for everyone, but apparently no such luck. One more reason to switch to modern compilers, I guess. We can revert it for now, and test in Guelph how much emplace helps with the performance?
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/pull/621#issuecomment-158586347.

We're working on the "switching to modern compilers" thing over here. In the meantime, yes, let's revert it.

Can we revert just this pull request? Or will others need to be reverted as well?

I’d rather mock up emplace than revert at this point. Or go back to not emplacing using an #ifdef gcc < too old don’t emplace.

On Nov 23, 2015, at 4:00 PM, SmithJK<EMAIL_ADDRESS>wrote:
Can we revert just this pull request? Or will others need to be reverted as well?
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/pull/621#issuecomment-159062636.


WalkSpeed and RunSpeed should be normalized to TT rules

From a discussion on RT crew:
@FrostRaptor conversation over in ME discord reminds me of couple things I noticed in CBTBE movement calcs.
1. in ME we assume single MP is 25 meters, in CBTBE in heat penalties the hardcoded (unless I am blind) assumption is 30 meters.
2. Run speed for odd numbers of MP should be rounded up, from what I see, you just do flat multiplication in meters
Maybe allow a setting for assumed distance per MP, and do rounding for RunSpeed from that?
like ceiling(runspeed/metersMP)*metersMP
FrostRaptorToday at 8:39 AM
@Interactive Rubber Dolphin I can certainly make the 30f a variable in config, that's easy enough
Does the round up actually change that much, given that runSpeed is a float?
Interactive Rubber DolphinToday at 8:40 AM
I assume pathfinder gives you available movement locations with it's own algorithm, but I have no idea how it works
FrostRaptorToday at 8:41 AM
I'm still early in my coffee and half-listening to a boring work meeting
But if your speed is 5/7, that's ... what 5*25 = 125 base
125 * 1.5 = 187.5
Interactive Rubber DolphinToday at 8:41 AM
187.5 vs 200
I dunno if it's a big enough difference for you not reaching needed hex
considering it's 3d distance
FrostRaptorToday at 8:42 AM
Where are you getting 200, I'm not following?
Interactive Rubber DolphinToday at 8:42 AM
"""hex""""
because TT movement is 5/8
not 5/7
8*25 = 200
FrostRaptorToday at 8:43 AM
So...
Interactive Rubber DolphinToday at 8:47 AM
or probably round, yes
FrostRaptorToday at 8:47 AM
Does that have weird knock-on effects with the different engine sizes?
Interactive Rubber DolphinToday at 8:48 AM
yes, now that I think about it round would be better for different sizes
FrostRaptorToday at 8:49 AM
So that's going to leave the 'weird' behavior
Interactive Rubber DolphinToday at 8:49 AM
In general it should pretty handily only change runspeed on tonnage increments
FrostRaptorToday at 8:50 AM
Where someone gets the weird hex breakage if they have an engine that's not above the breakpoints
Well, walkSpeed is going to change but runSpeed won't?
Because we're normalizing runSpeed to TT rules, but not walkSpeed?
Interactive Rubber DolphinToday at 8:51 AM
Sure, our usual line is "it might have a difference sometimes, but usually better stick to tonnage"
Okay, so, considering it's CBT behaviours, and you can't have fractional MP in CBT... normalize both?
FrostRaptorToday at 8:53 AM
Man, I walked into that one, didn't I?
sigh
Interactive Rubber DolphinToday at 8:53 AM
then we can say for certain that fractional tonnage engines don't do anything :wink:

Should be fixed in 0.4.7


fix(types): fix types for Field component

Closes #11
Co-authored-by: @emi2k01

Codecov Report

Merging #13 (a7ca452) into main (49cd58b) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #13   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines          359       358    -1
  Branches        63        63
=========================================
- Hits           359       358    -1

Impacted Files
Coverage Δ

src/index.tsx
100.00% <100.00%> (ø)

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


Fix problem with get with no parameters.

There is another pull request for this one, but that one will lose the pagination_add_ons().
Fixes issue #10

This looks good. Thank you for also addressing our usage of the "--use-mirrors" flag in travis.yml


Use jasonschema to validate CRD objects

https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/pull/76


Where to test the reCaptcha ?

I want to test my captcha solving method but can't find any page with captcha triggered. Maybe there is some test pages or something ? Because I don't want to configure cf by myself. And I need "alive" page (not the one in fixtures folder) for domain/host mocking on local machine.

I'll turn the CAPTCHA on for https://pro-src.com. Give me one sec to do it.

Thanks a lot :)

You're welcome. Issue solved?

Yep.

I'm looking for a consistent way to trigger CF's CAPTCHA on site's that don't have enabled in the same I've done for testing purposes. No luck yet..

Theres a chance that if using cloudscraper though Tor that you'll get a CAPTCHA consistently. I haven't confirmed yet. The reason I suspect this is because this article mentions that the Tor team had to make a small change at the request of CF to avoid the CAPTCHAs and it only works for newer version of the Tor Browser. If that change was only made in Tor Browser, maybe we'll have some luck there.
Article: https://www.zdnet.com/article/cloudflare-ends-captcha-challenges-for-tor-users/

Confirmed. You must override the headers entirely.
torsocks node -e 'var cf = require("."); cf.debug = true; cf.defaultParams.headers = {}; cf.get("http://gktorrent.net/torrents/series").then(console.log);'

Cool. Thanks for headers "trick".

I better option that seems to be Cloudflare approved is https://captcha.website

https://fuckmehard.fun/HIT
But it doesn't trigger onCaptcha for some reason...


Error while loading : Can't find dependent libraries

While trying to test the library under Windows I have the folowing error. The  webp-imageio.dll is in the temporary directory but it seems that there are dependent libraries...
Can someone help me ?
déc. 11, 2020 7:20:51 PM org.scijava.nativelib.NativeLibraryUtil loadNativeLibrary
AVERTISSEMENT: Problem with library
java.lang.UnsatisfiedLinkError: C:\Users\pnv_vmo.ASP\AppData\Local\Temp\webp-imageio3809737815982273834.dll: Can't find dependent libraries
	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
	at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1965)
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1890)
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1851)
	at java.lang.Runtime.load0(Runtime.java:795)
	at java.lang.System.load(System.java:1062)
	at org.scijava.nativelib.NativeLibraryUtil.loadNativeLibrary(NativeLibraryUtil.java:291)
	at com.luciad.imageio.webp.WebP.loadNativeLibrary(WebP.java:29)
	at com.luciad.imageio.webp.WebP.<clinit>(WebP.java:34)
	at com.luciad.imageio.webp.WebPEncoderOptions.<clinit>(WebPEncoderOptions.java:20)
	at com.luciad.imageio.webp.WebPWriteParam.<init>(WebPWriteParam.java:30)
	at example.EncodeTest.main(EncodeTest.java:26)

me too.

me too.

me too.

just  windows not work

me too.

just  windows not work

me too

me too

别用maven ,使用jar包导入试试

i too

Windows平台的dll， 作者使用了VS2017的DEBUG模式下编译的依赖VCRUNTIME140D.dll

me too, but solve by use v1.0。

me too

别用maven ,使用jar包导入试试

你的正常了吗

I had the same issue on a Windows System. I solved this by analyzing and installing the dll dependencies of the temporary \webp-imageio.dll. In my case the following dependencies have been missing

vcruntime140d.dll
ucrtbased.dll


Problems with MPRIS seek

#188 bugs
Seeking backwards via MPRIS doesn't work. ("Could not parse position") this is because the offset of the seek, is cast to u32 instead of staying as i32.
^ Sorry about this can't believe I didn't think to test with negative seek
@xou816 reports seek not working (need to look into more)
Could potential try to report track id as a DBUS object to silence the warning about reporting as a string.

Documentation about the trackid

The mpris:trackid attribute must always be present, and must be of D-Bus type "o". This contains a D-Bus path that uniquely identifies the track within the scope of the playlist. There may or may not be an actual D-Bus object at that path; this specification says nothing about what interfaces such an object may implement.

https://specifications.freedesktop.org/mpris-spec/latest/Track_List_Interface.html#Mapping:Metadata_Map

Again, no worries, and thanks for the very quick fix, looking into it!

The seek is was fixed, when #206 was merged.
I'm closing this as I don't think reporting trackid as a String instead of DBUS object is an issue at this time.


Strange syntax error only with zero '0' converted to int

With this extremely simple grammar "1" succeeds but "0" fails.   Can anyone shed light on this issue?  Thanks
zero-fails.py
from prettyprinter import pprint as pp

from pegen.grammar_parser import GeneratedParser as GrammarParser
from pegen.utils import generate_parser, parse_string

grammar_spec = """
    start  : a=num

    num    : a=NUMBER { float(a.string) if '.' in a.string else int(a.string) }
"""

numbers = [ 1, 0 ]

for n in numbers :
    grammar = parse_string(grammar_spec, GrammarParser)
    # print() ; pp(grammar)
    grammar_parser_class = generate_parser(grammar)
    tree = parse_string(str(n), grammar_parser_class, verbose=True)
    verdict = 'PASSED' if tree is not None else 'FAILED'
    pp([ verdict, tree ]) ; print()

Output
start() ... (looking at 1.0: NUMBER:'1')
  num() ... (looking at 1.0: NUMBER:'1')
    number() ... (looking at 1.0: NUMBER:'1')
    ... number() -> TokenInfo(type=2 (NUMBER), string='1', start=(1, 0), end=(1, 1), line='1')
  ... num() -> 1
... start() -> 1
['PASSED', 1]

start() ... (looking at 1.0: NUMBER:'0')
  num() ... (looking at 1.0: NUMBER:'0')
    number() ... (looking at 1.0: NUMBER:'0')
    ... number() -> TokenInfo(type=2 (NUMBER), string='0', start=(1, 0), end=(1, 1), line='0')
  ... num() -> 0
... start() -> None
Traceback (most recent call last):
  File "/home/phdyex/src/python/grammar-tool/test-files/pegen/gunit/simple/issue/zero-syntax-error/./zero-fails.py", line 20, in <module>
    tree = parse_string(str(n), grammar_parser_class, verbose=True)
  File "/home/phdyex/.cache/pypoetry/virtualenvs/grammar-tool-srSGyud3-py3.10/lib/python3.10/site-packages/pegen/utils.py", line 66, in parse_string
    return run_parser(file, parser_class, verbose=verbose)  # type: ignore # typeshed issue #3515
  File "/home/phdyex/.cache/pypoetry/virtualenvs/grammar-tool-srSGyud3-py3.10/lib/python3.10/site-packages/pegen/utils.py", line 55, in run_parser
    raise parser.make_syntax_error("invalid syntax")
  File "<unknown>", line 1
    0
    ^
SyntaxError: invalid syntax

I suspect it is the same problem of testing the boolean value of the result and not actually checking if the node was matched.
If you look at the generated code you probably will see something like
if self.num() which will fail if the result is 0 as bool(0) == False
It was not taken care of before, because all ast.X are classes and always evaluate to True
The other issue caused by this behavior is #81
#82 and #84 are trying to fix this issue, but the maintainers are busy right now and unable to review/merge
In the meantime you can use values that don't evaluate to False, probably the best choice is to wrap the number in your class, i.e.
@dataclass
class NumberNode:
    value: int | float

And then create it like NumberNode(...) and use it like number.value

Also, personally I want to ask you to check if #82 fixes this issue and report about it if possible

@pablogsal if you have time, it would be nice of you to take a look at the PRs

For the moment, I edited the loop accepting num:
was:
    @memoize
    def _loop1_1(self) -> Optional[Any]:
        # _loop1_1: num
        mark = self._mark()
        children = []
        while (
            (num := self.num())       # <== 0 and None both fail when 0 should succeed
        ):
            children.append(num)
            mark = self._mark()
        self._reset(mark)
        return children;

Fix _loop1_1 by adding is not None :
    @memoize
    def _loop1_1(self) -> Optional[Any]:
        # _loop1_1: num
        mark = self._mark()
        children = []
        while (
            (num := self.num()) is not None  # Now only None will fail and 0 will succeed
        ):
            children.append(num)
            mark = self._mark()
        self._reset(mark)
        return children;

This fixed it for me.  All differences in the generated code look good but it might have an unwanted side affect I haven't seen.  I ran pegen's test suite before and after.  The number of failing tests remained 94.
 $ diff -c src/pegen/python_generator.py{.original,}
*** src/pegen/python_generator.py.original      2023-04-23 05:04:44.422841674 -0400
--- src/pegen/python_generator.py       2023-04-23 05:19:20.662866388 -0400
***************
*** 417,423 ****
                      else:
                          self.print("and")
                      self.visit(item, used=used, unreachable=unreachable)
!                     if True: # is_gather:
                          self.print("is not None")

              self.print("):")
--- 417,423 ----
                      else:
                          self.print("and")
                      self.visit(item, used=used, unreachable=unreachable)
!                     if False: # self.is_gather:
                          self.print("is not None")

              self.print("):")

Making a global "fix" in src/pegen/python_generator.py sadly results in 94 newly failing tests.
Essentially, my action coercing the strings to integers or floats is the fundamental cause if PEGEN requires that actions always result in a value that is semantically True.  My apologies if this is documented somewhere.  If not, I would suggest adding it.
Thanks


2021-10-12 equity dashboard chart data update

Equity dashboard stats updates in this PR may be reviewed on staging - here.
After reviewing, if all looks well, approve and merge this Pull Request.
If there are issues with the data:

Note concerns or issues here by commenting on this PR
Work with Triston directly to resolve data issues
Alert the COVID19 site team in Slack (in the Equity page channel)

Good morning all,
Github Data Review Uploaded —
I have one “red flag” I would like to confirm:
:question: For Deaths/100K rates by R&E, would it be possible to confirm NHPI’s sub-11 value? While NHPI Deaths/100K has been <11 in the past for large stretches of time (refer to screenshot below, dates ~7/17 to 8/17), it has remained the highest COVID Deaths/100K rate since ~09/01. Therefore, if possible, I would like to confirm its jump from being the highest rate last week to <11 this week.

Other than this, I observe no major red flags.
:bulb:  Noticeable Highlights:
:bulb:  While HE Quartile positivity has been greater than Statewide Positivity since Sep. 12, Quartile & Statewide positivity are now both equal to 2.4% as of Oct. 3 data.
Thank you!
1. Blue Box Updates:
:heavy_check_mark: All percentage values are identical to last week, except for Death rate for Black people (Box 3) — after 3 weeks at 14%, increases by 1% to 15%.
2. Death Rate/100K by R&E:
:heavy_check_mark: Statewide COVID Deaths/100K remains identical to the last two weeks, at 4. All R&E COVID Deaths/100K show a decrease, except for Multi-Race (which increases from <11 total last week to 1.2/100K).
3. Case Rate/100K by R&E:
:heavy_check_mark: Like the last four weeks, this week shows decreases in all Case/100K rates. However, the rate of decrease this week is generally smaller than that of last week. Statewide decreases from 354 to 313. All values appear reasonable. NHPI Cases/100K remains the highest rate. Multi-Race Cases/100K remains the lowest rate.
4. Testing Rate/100K by R&E:
:heavy_check_mark: Unlike last week’s universal decreases, this week we see mixed, category-dependent changes. The Testing Rate/100K in some categories (such as NHPI, Black, AI/AN, Multi-Race) decrease, while the remaining rates (White, Asian American, Latino) show increases. Statewide increases.
:heavy_check_mark: All values appear reasonable. NHPI Testing/100K remains the highest rate, Multi-Race Testing/100K remains the lowest rate.
5. Sanity Checks
:heavy_check_mark: Mortality rate/100K < Case rate/100K for all categories (as expected).
:heavy_check_mark: % of state population remains consistent across all categories for Cases/Deaths/Testing by R&E
6. Community case rate/100K by median annual household income bracket:
:heavy_check_mark: Like the last two weeks, statewide & all income brackets’ case rates decrease this week. Statewide decreases from 14.4 to 12.7, a value between the $40-60K & $60-80K income brackets.
7. HE Metric:
:bulb:  While HE Quartile positivity has been greater than Statewide Positivity since Sep. 12, Quartile & Statewide positivity are now both equal to 2.4% as of Oct. 3 data.
:heavy_check_mark: (Dates) successfully extended. Both Statewide & HE Quartile Positivity continue with decreasing trend.


How to play MP3 on ios?

How to play MP3 on ios, try to compile libmpg123, but it fails, is there a solution?

Try the recent version with the minimp3, should be much easier. The libMPG123 is tricky to build on some platforms due to assembly fragments.

The latest code has support for playing MP3 on iOS and doesn't require libmpg123.
Cheers,


looks like credentials have changed again.

don't read from a file; have the runner prompt and save, etc.

actually, no; this is just part of the IAM policy thing. would probably be better to create an account on the amazon side of things anyway. also, downloading key files was confusing for users.


profile statistics do not match activity

okay, so from clarity i found one user that was struggling with activity in profile
https://kodadot.xyz/ahp/u/1246pXonxsWRB1AFrWswiRxsdSArq6R6vyd719g6A1WWasH5?tab=activity&buy=true&sale=true&mint=true&transfer=true&list=true
it shows that he sold one item and bought 6

but when you click to activity, there is no sale activity

:wave:

@preschian could you finish this one sir?


exp/services/recoverysigner: add admin port serving accounts count metric

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[x] This PR adds tests for the most critical parts of the new functionality or fixes.
[x] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[x] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[x] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
Add an admin port that serves Prometheus metrics with a single metric for the number of accounts in addition to the default metrics the Go prometheus library exposes for Go applications.
Why
As a starting point to adding other metrics and so that an operator can monitor the number of accounts without looking at the database directly.
Known limitations
N/A
Example metrics outputted
# HELP go_gc_duration_seconds A summary of the GC invocation durations.
# TYPE go_gc_duration_seconds summary
go_gc_duration_seconds{quantile="0"} 0
go_gc_duration_seconds{quantile="0.25"} 0
go_gc_duration_seconds{quantile="0.5"} 0
go_gc_duration_seconds{quantile="0.75"} 0
go_gc_duration_seconds{quantile="1"} 0
go_gc_duration_seconds_sum 0
go_gc_duration_seconds_count 0
# HELP go_goroutines Number of goroutines that currently exist.
# TYPE go_goroutines gauge
go_goroutines 15
# HELP go_info Information about the Go environment.
# TYPE go_info gauge
go_info{version="go1.14.2"} 1
# HELP go_memstats_alloc_bytes Number of bytes allocated and still in
use.
# TYPE go_memstats_alloc_bytes gauge
go_memstats_alloc_bytes 2.546128e+06
# HELP go_memstats_alloc_bytes_total Total number of bytes allocated,
even if freed.
# TYPE go_memstats_alloc_bytes_total counter
go_memstats_alloc_bytes_total 2.546128e+06
# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the
profiling bucket hash table.
# TYPE go_memstats_buck_hash_sys_bytes gauge
go_memstats_buck_hash_sys_bytes 1.444914e+06
# HELP go_memstats_frees_total Total number of frees.
# TYPE go_memstats_frees_total counter
go_memstats_frees_total 809
# HELP go_memstats_gc_cpu_fraction The fraction of this program's
available CPU time used by the GC since the program started.
# TYPE go_memstats_gc_cpu_fraction gauge
go_memstats_gc_cpu_fraction 0
# HELP go_memstats_gc_sys_bytes Number of bytes used for garbage
collection system metadata.
# TYPE go_memstats_gc_sys_bytes gauge
go_memstats_gc_sys_bytes 3.436808e+06
# HELP go_memstats_heap_alloc_bytes Number of heap bytes allocated and
still in use.
# TYPE go_memstats_heap_alloc_bytes gauge
go_memstats_heap_alloc_bytes 2.546128e+06
# HELP go_memstats_heap_idle_bytes Number of heap bytes waiting to be
used.
# TYPE go_memstats_heap_idle_bytes gauge
go_memstats_heap_idle_bytes 6.2005248e+07
# HELP go_memstats_heap_inuse_bytes Number of heap bytes that are in
use.
# TYPE go_memstats_heap_inuse_bytes gauge
go_memstats_heap_inuse_bytes 4.05504e+06
# HELP go_memstats_heap_objects Number of allocated objects.
# TYPE go_memstats_heap_objects gauge
go_memstats_heap_objects 14650
# HELP go_memstats_heap_released_bytes Number of heap bytes released to
OS.
# TYPE go_memstats_heap_released_bytes gauge
go_memstats_heap_released_bytes 6.197248e+07
# HELP go_memstats_heap_sys_bytes Number of heap bytes obtained from
system.
# TYPE go_memstats_heap_sys_bytes gauge
go_memstats_heap_sys_bytes 6.6060288e+07
# HELP go_memstats_last_gc_time_seconds Number of seconds since 1970 of
last garbage collection.
# TYPE go_memstats_last_gc_time_seconds gauge
go_memstats_last_gc_time_seconds 0
# HELP go_memstats_lookups_total Total number of pointer lookups.
# TYPE go_memstats_lookups_total counter
go_memstats_lookups_total 0
# HELP go_memstats_mallocs_total Total number of mallocs.
# TYPE go_memstats_mallocs_total counter
go_memstats_mallocs_total 15459
# HELP go_memstats_mcache_inuse_bytes Number of bytes in use by mcache
structures.
# TYPE go_memstats_mcache_inuse_bytes gauge
go_memstats_mcache_inuse_bytes 6944
# HELP go_memstats_mcache_sys_bytes Number of bytes used for mcache
structures obtained from system.
# TYPE go_memstats_mcache_sys_bytes gauge
go_memstats_mcache_sys_bytes 16384
# HELP go_memstats_mspan_inuse_bytes Number of bytes in use by mspan
structures.
# TYPE go_memstats_mspan_inuse_bytes gauge
go_memstats_mspan_inuse_bytes 63376
# HELP go_memstats_mspan_sys_bytes Number of bytes used for mspan
structures obtained from system.
# TYPE go_memstats_mspan_sys_bytes gauge
go_memstats_mspan_sys_bytes 65536
# HELP go_memstats_next_gc_bytes Number of heap bytes when next garbage
collection will take place.
# TYPE go_memstats_next_gc_bytes gauge
go_memstats_next_gc_bytes 4.473924e+06
# HELP go_memstats_other_sys_bytes Number of bytes used for other system
allocations.
# TYPE go_memstats_other_sys_bytes gauge
go_memstats_other_sys_bytes 1.016774e+06
# HELP go_memstats_stack_inuse_bytes Number of bytes in use by the stack
allocator.
# TYPE go_memstats_stack_inuse_bytes gauge
go_memstats_stack_inuse_bytes 1.048576e+06
# HELP go_memstats_stack_sys_bytes Number of bytes obtained from system
for stack allocator.
# TYPE go_memstats_stack_sys_bytes gauge
go_memstats_stack_sys_bytes 1.048576e+06
# HELP go_memstats_sys_bytes Number of bytes obtained from system.
# TYPE go_memstats_sys_bytes gauge
go_memstats_sys_bytes 7.308928e+07
# HELP go_threads Number of OS threads created.
# TYPE go_threads gauge
go_threads 10
# HELP process_cpu_seconds_total Total user and system CPU time spent in
seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 0.01
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1.048576e+06
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 11
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 1.7330176e+07
# HELP process_start_time_seconds Start time of the process since unix
epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.5898461919e+09
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 1.344884736e+09
# HELP process_virtual_memory_max_bytes Maximum amount of virtual memory
available in bytes.
# TYPE process_virtual_memory_max_bytes gauge
process_virtual_memory_max_bytes -1
# HELP recoverysigner_accounts_count Number of active accounts.
# TYPE recoverysigner_accounts_count gauge
recoverysigner_accounts_count 0

CC
@stellar/ops-team

After chatting to @brahman81 I altered which metrics get the namespace removing the namespace from the process metrics. In the process of doing that I realized there was a better way to add the prefix to our custom metrics. This is a pretty minor change though so I'm going to merge.


Withholding a post body in AuthBase until a security context has been established

Background
I'm working with a server which uses SPNEGO/GSS authentication, to keep it simple lets say the GSS mechanism is NTLM. As usual, the client and server exchange tokens to establish the context. What's different here is that once the context is established I want wrap (encrypt) the request body using the negotiated GSS context (in this case it would use NTLMv2 Session Security) and send it.
The authentication and encryption is not a problem. I'm using AuthBase and a response hook to exchange the tokens in the authenticate header.
Problem
My AuthBase derived class is sending the plaintext request body every time during the token exchange. I only want to send it in its encrypted form on the final exchange.
Looking at the PizzaAuth example on the Requests page:
from requests.auth import AuthBase

class PizzaAuth(AuthBase):
    """Attaches HTTP Pizza Authentication to the given Request object."""
    def __init__(self, username):
        # setup any auth-related data here
        self.username = username

    def __call__(self, r):
        # !! = !! = !! = !! = !! = !! = !! = !! = !! = !! = !! = !! =
        # I want to manipulate the request body here and ensure the request
        # that is returned is empty, or is otherwise encrypted
        # !! = !! = !! = !! = !! = !! = !! = !! = !! = !! = !! = !! =
        r.headers['X-Pizza'] = self.username
        return r

If I change the request body to an empty string
r.body = ""
I find that the remote server does not respond. This is because I have changed the body, but the Content-Length header is not re-calculated, and so my empty request is sent with a non-zero content-length - leaving the server waiting for more bytes. Now, I can also set the Body and the Content-Length header to zero - and that seems to work.
Question
Is is safe to manipulate the request body in AuthBase, will this cause a memory leak or any quality problems? Is it safe to simply set the body to an empty string and set the Content-Length to 0 until my final response, and then simply set the body and set the right content length?

Yes, it is safe to set the request body. This will not cause memory leaks because we do not have any reference deletion anywhere in requests' codebase. Leaking the reference to the body will be absolutely fine. Yes, it should be safe to simply set the body to an empty string and set the content-length appropriately, then set them back on the final response.
Note that this is one possible approach. Another approach would be to issue new requests in __call__.
In future, these questions are better asked on StackOverflow: the users there have much higher bandwidth to provide quality answers to questions like this one.

Thanks Lukasa!


Question : Why Lights make FPS drop ? and why only 7 or 8 lights can effect one object ?

Godot version:
Godot 3.0.2 Stable
OS/device including version:
windows 7 x64
8 GB Ram
GTX 980
i7 4790K
Issue description:
Why any light source make the FPS Drop ?
i have a very very simple scene .. the FPS is about 200 , Added 4 Spot lights + 4 Omni lights .. the FPS dropped to about 125 , i know the lights and shadows cost ... but not that much
Another question .. i noticed a single object can be affected only with 7 or 8 lights ?

Yes, maximum of lights that can affect an object is 8.
Also you should not look at absolute FPS value, but at the ms timings. The difference in timings between 200 fps and 125 fps is not that huge - 5 ms vs 8 ms per frame.

@Zireael07 why it's limited to 8 lights ? is it OpenGL limitation ?
where / how can i find ms timing ?

Yes, maximum of lights that can affect an object is 8.

I find it a bit confusing that lights are performed in a forward rendering fashion, as Godot is presendet as a forward/deferred rendering hybrid on the homepage. One of the main benefits you get from deferred rendering is unlimited lights per object.

i hope someone can answer

Yes, lights are limited. Clustered rendering is in the roadmap https://github.com/godotengine/godot-roadmap/blob/master/ROADMAP.md and will probably come when Vulkan is added.

actually this rendering of the shadows make them unusable in VR at the moment :
when activated, just one shadow makes the framerate to 1/4th of previous fps or less ...
imho something is not ordered correctly here I think not just waiting vulkan ;)
https://github.com/GodotVR/godot_openvr/issues/24#issuecomment-409710775

The 8-lights-per-mesh limit has been removed in the master branch thanks to clustered forward rendering, closing.


Image as background cannot set background position

I have a variable image coming from the web that I need to use as the background of a container. So this works fine. The only problem is I don't know how to set the position of the background. I want to use something like background-position so that my background is in the top left.
Here is a code snippet:
export default function App({ uri }) {
  return (
    <Image source={{ uri }} style={styles.container}>
      <Text>HELLO WORLD</Text>
    </Image>
  );
}
const styles = StyleSheet.create({
  container: {
    padding: 5,
    height: 150,
    width: WINDOW_WIDTH,
    resizeMode: 'cover',
    backgroundColor: 'transparent',
  },
});

The default background position seems to be the center of the image. Anyway to get this to work?

We're cutting down on the number of outstanding issues, in order to allow us to focus. I'm closing this issue because it has been open for over 60 days with no activity. If you think it should still be opened let us know why. PRs are always welcome.

I am also looking for something similar like background position

Me too.

Was looking for background position
Unable to find any solution.

+1

@hramos can this issue be reopened? It seems to be gaining some interest.

@sscaff1 I'd re-open it, but the original post does not adhere to the issue template we're using. Unless the OP edits it, it's probably best to open a new issue.

Will do thank you.


Feature requests for v0.0.1

We would like to provide some features in our initial release, and as suggested in our slack thread, we would like to have these features (sorted by votes).

[x] getWilayaList() @Fcmam5
[x] getAdjacentWilayas(number) @Fcmam5 (#6 )
[x] getWilayaByCode(number) @oussamabouchikhi (#8 )
[x] getWilayaByZipCode(number) @abachi (#9 )
[x] getZipCodesForWilaya(number) @anuragsati (#10 )
[ ] getDairatsForWilaya(number)

If you'd like to contribute:

Comment on this issue with the feature you want to work on, and we will edit it to add your name, as in getWilayaList() example.
Read our contributing guidelines and code of conduct.
Add your feature (with tests of course 😄 ).
Document it in the Readme (example: getWilayaList(projection) )
Submit a new pull request and point your branch to develop.

Please take your time, and if you need any help we will be very happy to help you. You can find us in #repo-leblad channel on our Slack.

I will take getAdjacentWilayas

I will take getWilayaByZipCode

Hello ! can i take getZipCodesForWilaya

Hello ! can i take getZipCodesForWilaya

Please go ahead @anuragsati 😃 !

Hello @Fcmam5 can i take getDairatsForWilaya for Hacktoberfest?

Hello @Fcmam5 can i take getDairatsForWilaya for Hacktoberfest?

Hi @anuragsati, I would say we finish with v0.0.1 for now, and we'll create another issue with more features to add, for sure they will be for Hacktoberfest.

sure, so can i work on getDairatsForWilaya for now?

Sure thing, please go ahead 😄 🙏 !

@oussamabouchikhi, @abachi and @anuragsati Thank you very much for working on v0.0.1 🙏 .

@oussamabouchikhi, @abachi and @anuragsati Thank you very much for working on v0.0.1 🙏 .

It was a pleasure working with you @Fcmam5 hope it's not the last time

@anuragsati , as I promised we started creating issues for hacktoberfest, welcome again 😄


Fix Time.now casting causing false positive in verify_at

Fixes #353

Im wondering if the condition should be inclusive (>=) to handle cases where the verification happen on the same second the token has ben issued.
Also a test verifying the "same-second" token would be good. Mocking the Time.now.to_i in a test could be a way to tackle the different cases.


Small fixes

Hi @Etienne42,
I'm working on some additions to your TestRail client.
My first PR includes some small fixes. There will be more coming.
Please let me know if there are any issues.
Thanks,
Gavrie

Hi @gavrie,
thank you for the PR.
I think we should keep the custom fields for the results, as we omit them if empty they shouldn't be a problem.
Regarding the 3XX status on the sendRequest method, I'm not sure if we should treat them as an error or not.

@Etienne42: See my comments above. We can keep checking for status codes > 299, I see no issue with that. Regarding the custom fields, I hope I cleared it up in the comment, let me know if not.


Update Spring Cloud to 2021.0.5 in Spring Cloud Alibaba 2021.x branch

我们鼓励使用英文，如果不能直接使用，可以使用翻译软件，您仍旧可以保留中文原文。
We recommend using English. If you are non-native English speaker, you can use the translation software.
Which Component
eg. Seata,
Is your feature request related to a problem? Please describe.
We are prepared to release a new version of Spring Cloud Alibaba in 2021.x branch, we are plan to update some components.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Update Spring Cloud to 2021.0.5 in Spring Cloud Alibaba 2021.x branch, and test the reliability.

I updated the spring cloud version. Please see #3059

I updated the spring cloud version. Please see #3059

Thanks !


Running a tensorflow situation slows down perf of the extension host

Run this code:
import tensorflow as tf
mnist = tf.keras.datasets.mnist

(x_train, y_train),(x_test, y_test) = mnist.load_data()
x_train, x_test = x_train / 255.0, x_test / 255.0

model = tf.keras.models.Sequential([
  tf.keras.layers.Flatten(input_shape=(28, 28)),
  tf.keras.layers.Dense(128, activation='relu'),
  tf.keras.layers.Dropout(0.2),
  tf.keras.layers.Dense(10, activation='softmax')
])

model.compile(optimizer='adam',
              loss='sparse_categorical_crossentropy',
              metrics=['accuracy'])

model.fit(x_train, y_train, epochs=5)
model.evaluate(x_test, y_test)

The extension host will peg the cpu and take up gigs of memory.
My only guess is that we're copying text around. A lot of it.

Thanks for reporting this issue, @rchiodo  get back to you asap :)


WIP: Tooltip update

update styles/design as to current design in Figma
render children or text (add children prop)
add semantic variants with stories and tests
keep non-semantic variant as a default
add open prop so the Tooltip can be programmatically opened from outside the component
resolve local/nested component
accept onClick handler on the toggle
don't render in Portal for now (we will try to use react-popper and get the desired positioning etc without the need to render in a portal)

Obsolete, done with #193 .


Protect ID Bug

Bug report received from e-mail.

Hi,
I'm at PHP version 8.0.9 and your latest version of Protect Track ID gives an error when Matomo build the reports, it puts this in matomo-archive.log en exits
Uncaught exception in /home/httpd/html/dmp.imcreatives.com/public_html/matomo/plugins/ProtectTrackID/ProtectTrackID.php line 101:
syntax error, unexpected ')'
I have no idea what to do, I can't downgrade as Matomo requires this new version of your plugin
Thanks,
Marcel

Hi again ;-)
I got it fixed by replacing your new regex code to one from an older version… note that your codes is having a ) too much in it.. for some reason Matomo just worked fine with that extra ) but the reports build cron function not
So.. I replaced this...
$regex = sprintf(
            '/^(%s){%s}$/',
            implode('|', str_split($settings->base)),
            $settings->length,
        );

With…
$regex = '/^('.implode('|', str_split($settings->base)).'){'.$settings->length.'}$/‘;
And things are back working and reports being build again…
Cheers
Marcel

I tested here with same PHP version and wasn't possible to reproduce issue here. The strange behavior is about him log, the issue was in ProtectTrackID.php on line 101 about syntax error, but on version 2.3.0 this file have only 78 lines.
This issue is about isValidHash, a function that validates if value received is hashed or not, then I'm going to investigate more about it.
dev@Devs-MacBook-Pro ~/source/joubertredrat/matomo (4.x-dev)> docker compose logs -f
matomo-matomo-1  | [Tue Jan 17 13:18:12 2023] PHP 8.0.9 Development Server (http://<IP_ADDRESS>:8080) started
matomo-matomo-1  | [Tue Jan 17 13:18:49 2023] <IP_ADDRESS>:55352 Accepted

I executed console and was fine.
/var/www # ./console core:archive --url=http://<IP_ADDRESS>
INFO [2023-01-17 15:38:22] 55  ---------------------------
INFO [2023-01-17 15:38:22] 55  INIT
INFO [2023-01-17 15:38:22] 55  Running Matomo 4.13.1 as Super User
INFO [2023-01-17 15:38:22] 55  ---------------------------
INFO [2023-01-17 15:38:22] 55  NOTES
INFO [2023-01-17 15:38:22] 55  - If you execute this script at least once per hour (or more often) in a crontab, you may disable 'Browser trigger archiving' in Matomo UI > Settings > General Settings.
INFO [2023-01-17 15:38:22] 55    See the doc at: https://matomo.org/docs/setup-auto-archiving/
INFO [2023-01-17 15:38:22] 55  - Async process archiving supported, using CliMulti.
INFO [2023-01-17 15:38:22] 55  - Reports for today will be processed at most every 900 seconds. You can change this value in Matomo UI > Settings > General Settings.
INFO [2023-01-17 15:38:22] 55  ---------------------------
INFO [2023-01-17 15:38:22] 55  START
INFO [2023-01-17 15:38:22] 55  Starting Matomo reports archiving...
INFO [2023-01-17 15:38:22] 55  Start processing archives for site 1.
INFO [2023-01-17 15:38:22] 55    Will invalidate archived reports for today in site ID = 1's timezone (2023-01-17 00:00:00).
INFO [2023-01-17 15:38:25] 55  Archived website id 1, period = day, date = 2023-01-17, segment = '', 1 visits found. Time elapsed: 3.063s
INFO [2023-01-17 15:38:25] 55  Archived website id 1, period = day, date = 2022-12-26, segment = '', 2 visits found. Time elapsed: 3.066s
INFO [2023-01-17 15:38:25] 55  Archived website id 1, period = day, date = 2022-12-23, segment = '', 1 visits found. Time elapsed: 3.069s
INFO [2023-01-17 15:38:28] 55  Archived website id 1, period = week, date = 2023-01-16, segment = '', 1 visits found. Time elapsed: 3.064s
INFO [2023-01-17 15:38:28] 55  Archived website id 1, period = week, date = 2022-12-26, segment = '', 2 visits found. Time elapsed: 3.068s
INFO [2023-01-17 15:38:28] 55  Archived website id 1, period = week, date = 2022-12-19, segment = '', 1 visits found. Time elapsed: 3.072s
INFO [2023-01-17 15:38:32] 55  Archived website id 1, period = month, date = 2023-01-01, segment = '', 1 visits found. Time elapsed: 2.795s
INFO [2023-01-17 15:38:32] 55  Archived website id 1, period = month, date = 2022-12-01, segment = '', 4 visits found. Time elapsed: 3.557s
INFO [2023-01-17 15:38:35] 55  Archived website id 1, period = year, date = 2023-01-01, segment = '', 1 visits found. Time elapsed: 2.283s
INFO [2023-01-17 15:38:35] 55  Archived website id 1, period = year, date = 2022-01-01, segment = '', 4 visits found. Time elapsed: 2.539s
INFO [2023-01-17 15:38:35] 55  Finished archiving for site 1, 10 API requests, Time elapsed: 13.155s [1 / 3 done]
INFO [2023-01-17 15:38:35] 55  Start processing archives for site 2.
INFO [2023-01-17 15:38:35] 55  Finished archiving for site 2, 0 API requests, Time elapsed: 0.018s [2 / 3 done]
INFO [2023-01-17 15:38:35] 55  Start processing archives for site 3.
INFO [2023-01-17 15:38:35] 55  Finished archiving for site 3, 0 API requests, Time elapsed: 0.013s [3 / 3 done]
INFO [2023-01-17 15:38:35] 55  Done archiving!
INFO [2023-01-17 15:38:35] 55  ---------------------------
INFO [2023-01-17 15:38:35] 55  SUMMARY
INFO [2023-01-17 15:38:35] 55  Processed 10 archives.
INFO [2023-01-17 15:38:35] 55  Total API requests: 10
INFO [2023-01-17 15:38:35] 55  done: 10 req, 13248 ms, no error
INFO [2023-01-17 15:38:35] 55  Time elapsed: 13.248s
INFO [2023-01-17 15:38:35] 55  ---------------------------
INFO [2023-01-17 15:38:35] 55  SCHEDULED TASKS
INFO [2023-01-17 15:38:35] 55  Starting Scheduled tasks...
INFO [2023-01-17 15:38:35] 55  Scheduler: executing task Piwik\Plugins\CustomJsTracker\Tasks.updateTracker...
INFO [2023-01-17 15:38:35] 55  Scheduler: finished. Time elapsed: 0.108s
INFO [2023-01-17 15:38:35] 55  Scheduler: executing task Piwik\Plugins\PrivacyManager\Tasks.deleteLogData...
INFO [2023-01-17 15:38:35] 55  Scheduler: finished. Time elapsed: 0.000s
INFO [2023-01-17 15:38:35] 55  Scheduler: executing task Piwik\Plugins\PrivacyManager\Tasks.anonymizePastData...
INFO [2023-01-17 15:38:35] 55  Scheduler: finished. Time elapsed: 0.002s
INFO [2023-01-17 15:38:35] 55  Scheduler: executing task Piwik\Plugins\GeoIp2\GeoIP2AutoUpdater.update...
INFO [2023-01-17 15:38:35] 55  Downloading https://download.db-ip.com/free/dbip-city-lite-2023-01.mmdb.gz to /var/www/tmp/latest/DBIP-City.mmdb.gz.download.
INFO [2023-01-17 15:38:41] 55  GeoIP2AutoUpdater: successfully downloaded 'https://download.db-ip.com/free/dbip-city-lite-2023-01.mmdb.gz'
INFO [2023-01-17 15:38:42] 55  GeoIP2AutoUpdater: successfully updated GeoIP 2 database 'https://download.db-ip.com/free/dbip-city-lite-2023-01.mmdb.gz'
INFO [2023-01-17 15:38:42] 55  Scheduler: finished. Time elapsed: 6.889s
INFO [2023-01-17 15:38:42] 55  done
INFO [2023-01-17 15:38:42] 55  ---------------------------

The problem wasn't trailing comma because was implemented in PHP 7.3. https://wiki.php.net/rfc/trailing-comma-function-calls

Tested with PHP 7.2.9 and I got the issue, probably their php-fpm version is different from php-cli.


Xattr

no tests written yet in this repo but I've tried them in goofys side and they seem to work. Want to get some input on interfaces and SetXattrOp.Flags handling

addressed review comments

Thanks. Please ping this when ivaxer/go-xattr#1 is resolved.

upstream doesn't seem active, any opinion on having the constants in this project?

This project really doesn't seem like the place to put them. I would recommend either adding the entire functionality of that project to an internal/ project here (complete with constants), or forking that package and fixing the issue in your fork.

maintaining a fork for 2 constants seems silly, an argument for putting them here is that any fuse filesystems that want to implement xattrs will want to use those constants too. In a way it's not that different from other fuse error codes that you already export.

Forking an unmaintained project for the sake of making a reasonable change to it is a totally sane thing to do. The impetus for the change doesn't matter; the point is that it's unmaintained.
Stuffing two constants here that are relevant only for an entirely different project doesn't make sense. Please either fix the upstream project (by upstreaming or forking), or pull the entirety of its functionality here, and give it a sane API.

amended last commit to switch to my fork of go-xattr

Thanks!


Point in Time IRIs

Use UUIDv5 for IRIs names-paced by the UUID of the class_of_point_in_time.

I now think this is a bad idea, because there will be PointInTime entities that don't have a known time value, so these will need random IRIs rather than deterministic UUIDv5 IRIs, and they would need to be treated differently to those with known time values that would be using UUIDv5 IRIs.


BUG: Multiple Enhancements needed

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
1. The feedback section hyperlink was removed; needs to be fixed

2. The navbar text looks distorted due to the shadows

3. Heading Font sizes problem

4. Join discord button alignment

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign me the issue @Its-Aman-Yadav
Thank youu

Sure @debangi29


feat: Remove deprecated Persister.name and Adapter.name

Description
Since we're going to publish a major release, this is a good time to fully remove support for Factory.name.
Types of Changes

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

Checklist

[ ] I have added tests to cover my changes.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] My code follows the code style of this project.
[x] My commits and the title of this PR follow the Conventional Commits Specification.
[x] I have read the contributing guidelines.

LGTM just need to delete the tests around this as well


Add addTag override

This allows you to disable the prefix from parallel commands so:
[foo]: output

Is just produced as:
output

This is useful when you want to run multiple tools in parallel and parse
the output, and don't particularly care which tool produced the line.

Thanks for the PR. Could you add a test please? You may just copy one of the existing ones and tweak the expected output. Cheers.

Thanks added!

Thanks!


Remove existing transmit from storage handling

This is in continuation of https://github.com/Azure/azure-sdk-for-net/pull/35017. This PR only removes the existing handling of transmitting telemetry from storage. Will integrate the changes done in https://github.com/Azure/azure-sdk-for-net/pull/35017 and https://github.com/Azure/azure-sdk-for-net/pull/34926 in the next PR.

API change check
API changes are not detected in this pull request.


Grouping check items

Hi, Tyler. Mind having a look at this?
Basically Olena thought it would be a good UI improvement to have some of the checks grouped by category. This task gave me a lot of trouble, because I kept trying to do things the hard way, like by assigning an attribute to each check, then filtering the returned checks by them for each part of the report.
Turns out the checks are all returned in the order they were done anyway, so I just made a few dummy checks that serve as section headers, and deal with them a bit differently in the Jinja template.
Let me know what you think. I think what the section headers ultimately end up being might change, but the code will be the same idea.

Made Tyler's mentioned changes


Liort mpath issue

This change is

Coverage decreased (-0.2%) to 52.247% when pulling 5e3ae22327106776995370daa3e3d4770b4b4ab9 on liort_mpath into 520a30840c213d107c9b84cce562bfc44054d3f2 on dev.

Review status: 0 of 4 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

remote/mounter/block_device_mounter_utils/block_device_mounter_utils.go, line 126 at r2 (raw file):

		return b.logger.ErrorRet(err, "Rescan failed", logs.Args{{"protocol", block_device_utils.SCSI}})
	}
	if !rescanForCleanUp {

please don't forget to return this back
its not related to the rescan issue

remote/mounter/block_device_mounter_utils/block_device_utils_mounter_test.go, line 187 at r2 (raw file):

			Expect(err).To(MatchError(callErr))
		})
		It("should fail if Cleanup failed", func() {

Please open ticket in jira to add these UT to the new location of the cleanup.

remote/mounter/block_device_utils/mpath.go, line 88 at r2 (raw file):

		return b.logger.ErrorRet(&commandExecuteError{dmsetupCmd, err}, "failed")
	}
	time.Sleep(5000 * time.Millisecond)

Please delete this sleep
lets make sure everything works without this sleep. if we will encounter issues we can add it back to see if it helps.
I don't want to have sleep 5 seconds every attach\detach, its too long.

Comments from Reviewable

Review status: 0 of 3 files reviewed at latest revision, 4 unresolved discussions.

remote/mounter/block_device_mounter_utils/block_device_mounter_utils.go, line 78 at r2 (raw file):
Tzur, i just saw that you move the cleanup to ActionAfterDetach, But you forgot to take the locking for this operation.
The reason we put a lock around the multipath cleanup is due to some issue we encounter while detach multiple volumes at the same time - which case the multipath -f to work very slowly.
So i think we should preserve this locking over the cleanup even if we moved to to ActionAfterDetach.

r.Debug("Ask for cleanMPDeviceLock for device", logs.Args{{"device", devicePath}})
b.cleanMPDeviceLock.Lock()
b.logger.Debug("Recived cleanMPDeviceLock for device", logs.Args{{"device", devicePath}})
defer b.cleanMPDeviceLock.Unlock()
defer b

Comments from Reviewable

Coverage decreased (-0.2%) to 52.247% when pulling 59bd6ce9ac860fd87b0a91302010434a0a9ea6e0 on liort_mpath into 520a30840c213d107c9b84cce562bfc44054d3f2 on dev.

Coverage decreased (-0.5%) to 51.977% when pulling 75da43581c7d364a98b8de91f4b57bec37903869 on liort_mpath into 520a30840c213d107c9b84cce562bfc44054d3f2 on dev.

Coverage decreased (-0.1%) to 52.319% when pulling 41ed67c85cd9fe4c2c9440539e248eba79d06c4d on liort_mpath into 520a30840c213d107c9b84cce562bfc44054d3f2 on dev.

Coverage increased (+5.3%) to 57.769% when pulling 7b3bc7750cdb4f9c86271e3b3f24fbfb404089e2 on liort_mpath into 520a30840c213d107c9b84cce562bfc44054d3f2 on dev.

Coverage decreased (-0.1%) to 52.319% when pulling 7b3bc7750cdb4f9c86271e3b3f24fbfb404089e2 on liort_mpath into 520a30840c213d107c9b84cce562bfc44054d3f2 on dev.

Coverage increased (+0.6%) to 53.003% when pulling 100a5c7e477c8458572e865bd20113ff5bc9ad19 on liort_mpath into 520a30840c213d107c9b84cce562bfc44054d3f2 on dev.

Coverage decreased (-0.3%) to 52.864% when pulling c4f3e07e7996411857f767a26d2ac968b9e1c094 on liort_mpath into<PHONE_NUMBER>6c8a1cc59c6620c891528076690d52 on dev.

Coverage decreased (-0.3%) to 52.864% when pulling f8a84df30fb25e060481f7eb16a60c650b92cb99 on liort_mpath into<PHONE_NUMBER>6c8a1cc59c6620c891528076690d52 on dev.

Coverage decreased (-0.3%) to 52.864% when pulling 347289edf699685518baa06a35c65f128ab6781c on liort_mpath into 07849f53419fcb42f6c82e753faa0750bff8d06b on dev.

closing this PR since its not relevant any more
no merge to dev


Extend XBOS plug to include monitoring

Review requested @gtfierro @jhkolb

why do we have an interface in non SI units.

Hahah we should probably switch that soon. I've made a note of it https://github.com/SoftwareDefinedBuildings/XBOS/issues/34


Pasting doesn't work properly in ConEmu

Operating System: Windows 10
Micro version: 1.0.1
ConEmu version: 160828 [64 bit]
Pasting doesn't work properly in ConEmu (using CtrlV). It is almost as if the text gets cut off, but some strange things happen when it is an URL.
Example 1 (Regular Text):

The full text was PASTE ME PLEASE, it gets cut down to PASTE ME PLE
Example 2 (URL):

The full URL was https://github.com/zyedidia/micro/tree/master/cmd/micro, it gets the https://gith part, and then it appears to append "random" parts of the string after.
I am not sure if this is an issue related to Micro, or ConEmu.

A temporary fix is to go to ConEmu Settings -> Keys & Macro -> Paste and change "Paste mode 2" to "Do nothing."

@rbrick wow, how did you record those gifs?

@zyedidia The temporary fix worked. Thank you!
@techtonik I used ShareX to record the GIFs.


Wrong Typing for mockRoute jsdoc allow Regex than typescript don't

What are you trying to achieve?
I want to use mockRoute() function with regex as params url as describe in the doc and allowed by playwright
Playwright docs
url <string|RegExp|function(URL):boolean> A glob pattern, regex pattern or predicate receiving URL to match while routing.
 I.mockRoute(/api\/private/, route => {
...
})

What do you get instead?
I get typescript error
Argument of type 'RegExp' is not assignable to parameter of type 'string'.

Provide test source code if related

        /**
         * Mocks network request using [`browserContext.route`](https://playwright.dev/docs/api/class-browsercontext#browser-context-route) of Playwright
         *
         * ```js
         * I.mockRoute(/(\.png$)|(\.jpg$)/, route => route.abort());
         * ```
         * This method allows intercepting and mocking requests & responses. [Learn more about it](https://playwright.dev/docs/network#handle-requests)
         * @param [url] - URL, regex or pattern for to match URL
         * @param [handler] - a function to process request
         */
        mockRoute(url?: string, handler?: (...params: any[]) => any): void;

Details

CodeceptJS version:  "codeceptjs": "^3.3.0",
NodeJS Version: v16.9.1
Playwright: "playwright": "^1.20.2"

Proposition
Modify mockRoute() typings to allow regex and match the JSDoc provide by codecept and match signature of on.route() by playwright

        mockRoute(url?: string, handler?: (...params: any[]) => any): void;

        mockRoute(url?: string|RegExp, handler?: (...params: any[]) => any): void;

Same problem on stopMockingRoute()


⚠ Jenkins Plugins Artifactory has degraded performance

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

HTTP code: 200
Response time: 1444 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 40bea32 after 17 minutes.


SOLVED: OpenVR-Autostarter not showing up in SteamVR Settings

Hello, I have the same problem as #12  .
I installed everything but when i look in the SteamVR settings windows, the OpenVR-Autostarter doesn't show up. (Picture Below)

Also, there is no dreiekk.OpenVR-Autostarter.vrappconfig file in my steam wrappconfig folder. (Pic Below)

I figured out the problem. The OpenVR-Autostarter manifest.vrmanifest file wasn't added to the steamvr appconfig.json file.
Here is a guide on how to fix the problem manually :

Go to your OpenVR-Autostarter folder (Usually C:\Program Files\OpenVR-Autostarter\ but might change if you choose a different installation directory during the OpenVR-Autostarter install)
Copy the path of the manifest.vrmanifest in the folder
Go to your Steam config directory (Usually C:\Program Files (x86)\Steam\config\ but again, might change if you choose a different directory when you installed steam)
Open the appconfig.json file (Use notepad, vscode, nano, anything really)
Add the OpenVR-Autostarter manifest.vrmanifest path to the manifest path list.

Your appconfig.json file should look like on the picture below

DEV PART:
I think the problem occured because my steam folder isn't the default one, the OpenVR-Autostarter program might not have been able to locate the appconfig.json file because of that, and so it failed at adding its manifest.vrmanifest path to the appconfig.json file.
To fix this, you should ask for the steam directory if it is not automatically detected (Look if the default path exists, if not, ask for the steam path)
Anyways, I hope this solved any issues you might have encountered. Have a nice day !


Fixed bug that boolean was not parsed correct

This bugged me for ours: The boolean values are not parsed correct inside the defaultParser.
I found this, when loading a LitElement asynchronously by Vue.js like this:
<loading-blocker :loading="loading"></loading-blocker>

I added my CLA, however this test must be triggered again.

Thank you for the contribution but I don't agree with this change. For the case of booleans, we want to return a boolean and never null. The value coming in to fromAttribute() is either string if any attribute exists including empty string, or null if the attribute does not exist. If the attribute does not exist, and the value is null, we need to return false. Anything else, we return true. This is the existing implementation.
This change would assign null to the value of a boolean property when the attribute doesn't exist, and incorrectly assign false when the attribute exists with the value of empty string.
It seems the issue you're having is more a problem that Vue can't tell that particular attribute on the custom element should behave as a boolean attribute so providing false in the attribute binding could result in the property having true value. You should instead use .prop to bind it as a property instead. See https://github.com/vuejs/docs/issues/1972#issuecomment-1259245520
Please file an issue if you think Lit is handling incorrectly.

I feel the "From attribute to property" table above this does a good job of explaining this behavior of the default converter.
https://lit.dev/docs/components/properties/#conversion-type

That's true. I clicked on the ToC to go straight to boolean properties and it wasn't as clear then.


Link header pagination only parsing first rel

Steps to reproduce
$uri_base = 'https://MYDEVORG.okta.com'
$apikey = 'MYAPIKEY'
$uri = $uri_base + '/api/v1/users/?filter=status eq "STAGED"&limit=200'
$method = 'GET'
$headers = @{'Accept'='application/json';'Content-Type'='application/json';'Authorization'="SSWS $apikey"}

PS /> $json = Invoke-RestMethod -Uri $uri -Method $method -Headers $headers -FollowRelLink
PS /> $json.Count
200
PS /> $webreq= Invoke-WebRequest -Uri $uri -Method $method -Headers $headers
PS /> $webreq.RelationLink

Key  Value
---  -----
self https://MYDEVORG.okta.com/api/v1/users?limit=200&filter=status+eq+%22STAGED%22

PS /> $webreq.Headers.Link
<https://MYDEVORG.okta.com/api/v1/users?limit=200&filter=status+eq+%22STAGED%22>; rel="self"
<https://MYDEVORG.okta.com/api/v1/users?after=OKTAUSERID&limit=200&filter=status+eq+%22STAGED%22>; rel="next"
PS />

Expected behavior
Invoke-RestMethod should follow the next rel link and return additional results.
Invoke-WebRequest RelationLink dictionary should contain both "self" and "next".
Actual behavior
Only the first value from $webreq.Headers.Link is parsed into RelationLink.
Environment data
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial

> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.0-beta.9
PSEdition                      Core
GitCommitId                    v6.0.0-beta.9
OS                             Linux 4.4.0-43-Microsoft #1-Microsoft Wed Dec 31 14:42:53 PST 2014
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

References
Related commit: https://github.com/PowerShell/PowerShell/commit/40446c80a705f71260a9258ebc6477982789e82e
Related RFC: https://github.com/PowerShell/PowerShell-RFC/blob/master/2-Draft-Accepted/RFC0021-Link-header-based-pagination-for-WebCmdlets.md

May be due to WebRequestPSCmdlet.CoreClr.cs ParseLinkHeader function using .FirstOrDefault() in the foreach? Also appears that IWR Headers.Link is a comma-separated string on Windows PowerShell, but an array of strings on PowerShell Core.

@dddugan can you post the the header section of the RawContent property of the result using Invoke-WebRequest?  Feel free to scrub the data, but I'd like to see the format of the returned headers specifically the Link header.

There seem to be multiple headers for the multiple values.
HTTP/1.1 200 OK
Date: Fri, 27 Oct 2017 14:50:47 GMT
Server: nginx
Public-Key-Pins-Report-Only: pin-sha256="abcdzZxQVvQpKo3AgYRaT7X2bDO/kj3ACwmxfdT2zt8="; pin-sha256="abcdcUgk2mvY/RFSGeSwBRkI+rZ6/dxe/DuQfBT/vnQ="; pin-sha256="abcdIEvDEWn+EThf3qjR7/bQSWaS2ZSLqolhnO6iyJI="; pin-sha256="abcdCLCCvqnk89gWibYT0JO6fNQ8cCit7GGoiVTjCOg="; max-age=60; report-uri="https://okta.report-uri.io/r/default/hpkp/reportOnly"
Vary: Accept-Encoding
X-Okta-Request-Id: ABCDx63U6bS-Mj9BfeJtBgAACIA
P3P: CP="HONK"
X-Rate-Limit-Limit: 600
X-Rate-Limit-Remaining: 596
X-Rate-Limit-Reset:<PHONE_NUMBER>
Cache-Control: no-store, no-cache
Pragma: no-cache
Link: <https://MYDEVORG.okta.com/api/v1/users?limit=200&filter=status+eq+%22STAGED%22>; rel="self"
Link: <https://MYDEVORG.okta.com/api/v1/users?after=OKTAID&limit=200&filter=status+eq+%22STAGED%22>; rel="next"
Strict-Transport-Security: max-age=315360000
Set-Cookie: sid=""; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/
Set-Cookie: JSESSIONID=00ABCD87967C1854E80C4BB1245B549E; Path=/
Transfer-Encoding: chunked
Content-Type: application/json; charset=UTF-8
Expires: 0

My reading of the RFC particularly:
   Multiple message-header fields with the same field-name MAY be
   present in a message if and only if the entire field-value for that
   header field is defined as a comma-separated list [i.e., #(values)].

Is that multiple headers with the same name MUST be comma separated.  So having two Link: headers that aren't a comma separated list seems to not be conforming.

@SteveL-MSFT that RFC is so poorly worded, What it means is that the following two must be equvilent:
X-Header: Value1
X-Header: Value2

X-Header: Value1, Value2

That means that you cannot do
X-Header: Value1, Value2
X-Header: Value3

instead,  Value1, Value2 becomes Value1. This allows for multiple headers to support commas as a character where as a single header, commas are always a value separator with no escape character.
In Full CLR they mash these all together for you. In CoreFX they treat multiple headers as separate elements in the header collection.
The solution is to implement something like what is in #4494 in ParseLinkHeader(). Since I'm familiar with it, I'll take this one. but it should be High Priority.

Thanks, friends! Appreciate the quick response. Looking forward to testing the fix.

@dddugan If you want to validate it now you can build from the MultipleRelLinkFix brand on my repo: https://github.com/markekraus/PowerShell/tree/MultipleRelLinkFix
On windows you can use the MSI or zip  produced by AppVeyor  https://ci.appveyor.com/project/PowerShell/powershell/build/6.0.0-beta.9-6425/artifacts


JAVA-1209: ProtocolOptions.getProtocolVersion() should return null instead of throwing NPE if Cluster has not been init'd

LGTM.
One minor thing: I'm not sure if having a unit test in a class extending CCMTestsSupport works well; @adutra?

One minor thing: I'm not sure if having a unit test in a class extending CCMTestsSupport works well; @adutra?

It looks like the test runs and is included as part of the unit tests, so it appears to work.  I think it is because all of the CCM logic is done as part of @Before/@BeforeClass annotations that are bound to short/long profiles.

One minor thing: I'm not sure if having a unit test in a class extending CCMTestsSupport works well; @adutra?

Yes, it works, we have some other occurrences of this in our test codebase.

Merged to 3.0.x.
Very minor remark: we tend to use AssertJ assertions (assertThat syntax) instead of TestNG's in new tests. I changed that in the merge commit.


Stop pinning dependencies

Use case
One of the biggest pain points for package authors (and probably app developers too) that have been brought up during the Dart & Flutter Package Ecosystem Summits is that Flutter has pinned versions of its dependencies.
Why do we not want pinned dependencies? Because it leads to a lot trickier dependency version resolution than it needs to be for the end user. I would say almost all Flutter developers have at some point ended up in dependency resolution hell, before they realize that some dependencies needs to be treated with special care.
Since all of the pinned dependencies are controlled by Google it should be fairly straight forward to set up a process so that they all have some tests towards Flutter before doing a new non-breaking release or doing deprecations.
The main ones are: intl, meta, collection path, vector_math and async.
The Flutter team’s rationale for using pinned versions is outlined in this document but I have been told that removing the dependency pinning is on the radar, so I just want to open this so that we can track it somewhere.
Proposal
Things that needs to be solved:

[ ] Flutter builds should be hermetic.
[ ] When dependencies bump their versions they should not be able to break Flutter.

For the first one I'm thinking that it could be solved with a lock file that isn't shipped with Flutter, but used for the builds.
For the second one my suggestion is that we introduce CI checks that needs to run before releasing a new version of the dependencies to make sure that they don't break anything in Flutter. Deprecations have to be taken into consideration here too, since they are not counted as breaking in semver.

We could also flip this around a little bit, if the flutter repo migrated to use the "workspaces" feature from pub. Then, we would manually curate these packages and their pinned versions - and this would transitively enforce the versions in the other packages in the workspace.

That sounds like a great idea! Then it should be very easy to properly check that a change is not breaking anything in Flutter too.

I'm not sure if there's an issue tracking it, but the other approach that's been floated for this in vendoring all of our dependencies. That doesn't work for anything we want to use in public APIs though.

Many of the pinned deps come from flutter_test which depends on (and re-exports) test_api, which also definitely leaks various things from its own public APIs. So, I don't think vendoring is really an option for flutter_test at least.

Re:

For the second one my suggestion is that we introduce CI checks that needs to run before releasing a new version of the dependencies to make sure that they don't break anything in Flutter.

For most Dart core packages, we do already vet them before publishing; this is done by rolling them into the dart sdk repo and into google3. This helps flush out breakages before a publish. We could introduce a process where we also do a test roll into flutter (testing by doing a dependency override on a -dev publish? by an override via a git dep?).
The pinned packages in package:flutter are:
  characters: 1.3.0
  collection: 1.19.0
  material_color_utilities: 0.11.1
  meta: 1.15.0
  vector_math: 2.1.4

Changing to using semver might look something like:
  characters: ^1.3.0
  collection: ^1.19.0
  material_color_utilities: ^0.11.0
  meta: ^1.15.0
  vector_math: ^2.1.0

If after a stable release, an incompatible release of a package occurred, there would be a number of options:

the semver constraint above could be changed to not include the problem version; that fix could be patched into the stable channel of flutter (collection: '>=1.19.0 <1.19.2')
the package version itself could be retracted
the package could publish a new forword-fix version

if the flutter repo migrated to use the "workspaces" feature from pub. Then, we would manually curate these packages and their pinned versions

For this, what would the package constraints look like in the pubspec for package:flutter? I.e. what would users be solving against.

For this, what would the package constraints look like in the pubspec for package:flutter? I.e. what would users be solving against.

Just like what you linked above, normal constraints. Only these new packages whose only purpose is to pin deps would have specific versions.
Because all packages in a workspace share a version solve, you only need one package in the workspace to pin deps to effectively pin all packages. It also occurred to me that flutter packages could have a dev dependency on that package, and also get the pinning for themselves but not leak it to all consumers.

We could introduce a process where we also do a test roll into flutter (testing by doing a dependency override on a -dev publish? by an override via a git dep?).

This could be automated for sure, similar to how flutter customer tests run we could run some set of flutters tests in any of our repos. See as one example the workflow in package:build which runs tests from the drift package https://github.com/dart-lang/build/blob/master/.github/workflows/community.yml.


Over-aggressive auto-completion?

Hello,
I wanted to share some feedback regarding the new autocompletion feature.
While using the autocompletion, I've noticed a behavior that has led to a few unintended mistakes in my code. For instance, consider the following cell:
#%% test cell
variable_50_name = 10

print('=' * 40)

In a scenario where I intend to change "40" to "50" and rerun the cell, I found that the autocompletion occasionally interrupts my workflow. Specifically, when attempting to modify "4" to "5," the autocompletion feature can inadvertently trigger, causing unexpected behavior when I press Ctrl+Enter to run the cell. See pics below:
I edit 4 into 5...

I just do not realise the autocompletion suggestion and I press ctrl+enter

I believe a smoother experience could be achieved if the autocompletion were to be more seamlessly integrated during editing, avoiding unintended interactions during code modification and execution. Actually, now, I have to pay more attention to IGNORE autocompletion advices than before. I think that most of the conflict is due to the fact that {enter} is used both for autocompletion (instead of TAB) and for cell running.
A similar unwanted behavior happens when I want to write hust the name of a function , say foo, then go to a new line.
When I press enter, foo is automatically replaced into foo(), which is not what I want.
Thank you for considering this feedback. It's intended to foster a more user-friendly experience for all users.
BEsts,
Mike
EDIT
Spyder IDE version 5.4.3

Hi @capitanevs thank you for the feedback! Actually, I think the autocompletion when you do Ctrl +Enter is a bug 🤔 Since a modifier is being used alongside Enter, I would say that the completion widget should be dismissed and instead the action with an associated shortcut triggered. But in general, what do you think @spyder-ide/core-developers ?

Would this be fixed if #12728 was implemented?
As a cell user this one gets me too from time to time.

Hi @bcolsen ! Actually this seems like a duplicate of #12728 indeed :+1:

Thank you for checking #12728 and confirming that both issues are asking for the same option @capitanevs ! I will close this as a duplicate of #12728 then but feel free to provide further feedback over #12728 :)


Various errors found in the aix playbook

Yum yum update dependency error. Most machines
--> Finished Dependency Resolution
Error: Package: openldap-2.5.12-1.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: sudo-1.9.13p2-1.ppc (AIX_Toolbox)
           Requires: libssl.a(libssl.so.1.1)
Error: Package: curl-8.0.1-1.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: python3-3.7.15-2.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: python-pycurl-<IP_ADDRESS>-1.ppc (AIX_Toolbox)
           Requires: libssl.a(libssl.so.1.1)
Error: Package: krb5-libs-1.20.1-1.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: python-2.7.18-4.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: curl-8.0.1-1.ppc (AIX_Toolbox)
           Requires: libssl.a(libssl.so.1.1)
Error: Package: git-core-2.38.3-1.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: libssh2-1.10.0-2.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: git-core-2.38.3-1.ppc (AIX_Toolbox)
           Requires: libssl.a(libssl.so.1.1)
Error: Package: sudo-1.9.13p2-1.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: python3-3.7.15-2.ppc (AIX_Toolbox)
           Requires: libssl.a(libssl.so.1.1)
Error: Package: rsync-3.2.7-1.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: python-pycurl-<IP_ADDRESS>-1.ppc (AIX_Toolbox)
           Requires: libcrypto.a(libcrypto.so.1.1)
Error: Package: krb5-libs-1.20.1-1.ppc (AIX_Toolbox)
           Requires: libssl.a(libssl.so.1.1)
Error: Package: python-2.7.18-4.ppc (AIX_Toolbox)
           Requires: libssl.a(libssl.so.1.1)
Error: Package: openldap-2.5.12-1.ppc (AIX_Toolbox)
           Requires: libssl.a(libssl.so.1.1)

rbac ✅
https://github.com/adoptium/infrastructure/blob/e9c555980680e72a4ecb748d254fec942761ef8f/ansible/playbooks/AdoptOpenJDK_AIX_Playbook/roles/rbac/tasks/setsecattr.yml#L15 fails for /usr/bin/ksh
TASK [rbac : Add authorization to command /usr/bin/ksh] ************************
fatal: [test-osuosl-aix72-ppc64-2]: FAILED! => {"changed": true, "cmd": "setsecattr -c accessauths=ojdk.rtclk,ojdk.proccore innateprivs=PV_PROC_RTCLK,PV_PROC_CORE inheritprivs=PV_PROC_RTCLK,PV_PROC_CORE secflags=FSF_EPS
 \"/usr/bin/ksh\"", "delta": "0:00:00.063116", "end": "2023-05-25 17:20:23.736530", "msg": "non-zero return code", "rc": 22,
"start": "2023-05-25 17:20:23.673414", "stderr": "1420-001 Authorization \"ojdk.proccore\" does not exist.\n1420-016 Attribute
\"accessauths\" has an invalid value \"ojdk.rtclk,ojdk.proccore\".", "stderr_lines": ["1420-001 Authorization \"ojdk.proccore\"
does not exist.", "1420-016 Attribute \"accessauths\" has an invalid value \"ojdk.rtclk,ojdk.proccore\"."], "stdout": "",
"stdout_lines": []}

Users ✅
https://github.com/adoptium/infrastructure/blob/e9c555980680e72a4ecb748d254fec942761ef8f/ansible/playbooks/AdoptOpenJDK_AIX_Playbook/roles/users/tasks/jenkins.yml#L12
TASK [users : Set authorized key for jenkins user] *****************************
fatal: [test-osuosl-aix715-ppc64-1 -> localhost]: FAILED! => {"changed": false, "msg": "Failed to lookup user jenkins:
\"getpwnam(): name not found: 'jenkins'\""}

disable_sendmail ✅
https://github.com/adoptium/infrastructure/blob/e9c555980680e72a4ecb748d254fec942761ef8f/ansible/playbooks/AdoptOpenJDK_AIX_Playbook/roles/disable_sendmail/tasks/main.yml#L5
TASK [disable_sendmail : Ensure sendmail is stopped] ***************************
fatal: [test-osuosl-aix72-ppc64-4]: FAILED! => {"changed": false, "msg": "0513-086 The sendmail Group is not on file.\n"}

aixfs
In https://github.com/adoptium/infrastructure/blob/master/ansible/playbooks/AdoptOpenJDK_AIX_Playbook/roles/aixfs/tasks/main.yml, if ansible detects that the filesystems are larger than the desired amount it should not shrink it. I feel like this will cause loss of data
failed: [test-osuosl-aix715-ppc64-1] (item={'mount': '/var', 'size': 4}) => {"ansible_loop_var": "item", "changed": true, "cmd":
["/usr/sbin/chfs", "-a", "size=4G", "/var"], "delta": "0:00:00.098215", "end": "2023-05-25 12:44:26.555219", "item": {"mount":
"/var", "size": 4}, "msg": "non-zero return code", "rc": 28, "start": "2023-05-25 12:44:26.457004", "stderr": "", "stderr_lines":
[], "stdout": "chfs: There is not enough free space to shrink the file system.", "stdout_lines": ["chfs: There is not enough free
space to shrink the file system."]}

The Security error is just a case of a few machines having now space in /tmp, disregard that one

https://github.com/adoptium/infrastructure/pull/3088 fixes the sendmail error

The rbac error comes on systems that had not had the renewed RBAC task run. AND it had not been tested on existing systems that had the old RBAC names. Unlucky choice on my part to not have tested for both ojdk.rtclk and ojdk.proccore.
I'll rewrite this one to test/make if needed for each of the authorizations required.

As to openldap. imho: that is a yum error - forcing openldap upon us. And if openldap is required - contact IBM and get them to repackage it so that it works with SSL provided as part of AIX base. Noone wants to have to watch two packages of SSL when one is enough.

rbac fixed by https://github.com/adoptium/infrastructure/pull/3090 Thanks Michael

I am curious to know which system passed (as you said most failed.

I did a more thorough check, It is affecting all machines

OK. Well I assume it means they all need a later version of openssl installed, and sadly, my IBMid no longer lets me download stuff.
I would consider limiting openldap to the previous version (2.4.X) rather than the newer 2.5 - and/or signal IBM (AIX Toolbox that is provided asis iirc) that AIX 7.2 should also support, ie, work with, openssl 1.0.2.

Happy me too!

rbac fixed by #3090 Thanks Michael

Any news on this? If yum fails - I would look at the way AIX Toolbox is managing things - rather than blame to playbook. But, yes, sadly, modifying the playbook is probably the way to 'patch' around those packaging issues.


#64 updated to json 2.0

@jrbeilke is it ok?

spec tests dont pass for me on master, so they also didnt pass on this

It doesn't work only with old ruby version. I think we should merge it, remove ruby 1.9.3 from Travis and bump zabbixapi version to 3.0.

Hmm, i wonder what i was doing wrong. Im using ruby 2.2.4 and ran bundle exec rspec spec/*
Another idea would be test in travis with multiple gemfiles, one using json ~> 1.8 and another using json ~> 2.0.

@atheiman check https://github.com/express42/zabbixapi/blob/master/.travis.yml You need run postgresql and zabbix for tests.

Ahh thank you, ill update to make Travis work with multiple gemfiles and get the specs working in travis https://travis-ci.org/express42/zabbixapi/builds/191019782
Ill also update to make 1.9.3 an acceptable failure in travis.

https://travis-ci.org/express42/zabbixapi/builds/191510761 looks good, i think this is ready.

Yeah, looks good. I`ll merge it after #66

Agreed, would be nice to see a bump in the zabbixapi major version to indicate a possible breaking change with the move to Ruby >= 2 and support for Zabbix >= 3.
Ruby 1.9 is already EOL along with Zabbix 2.4, and Zabbix 2.2 LTS loses full support this year as well.
Before we create a new zabbixapi 3.x.x branch we should probably merge #63 into the 2.2.x and 2.4.x branches

any updates on this @postgred @jrbeilke
I dont think this warrants a major version change
If there is any development I can do to help this get merged and released let me know

I hope to merge this PR.