Cookie pop-up on home page

Related Issue
cookie pop up on the home page added
Fixes Issue :  #519
Description
This popup has 3 options to customize, reject or accept the cookies...and a link to view the cookie policy of the website.
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[x] I have made this change from my own.
[x] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@Amulya-B28 Your pull request has been successfully merged! Don't stop here—continue contributing by addressing more issues and aiming to become a top contributor. Exclusive swag awaits for those who go the extra mile!
Great contribution ! 🎉


PMM-7 fix UI matrix

RBAC has been fixed:
https://github.com/percona/pmm-ui-tests/actions/runs/5329109699
https://github.com/percona/pmm-ui-tests/actions/runs/5333776814
https://github.com/percona/pmm-ui-tests/actions/runs/5334145513


Add the scripts menu definition to nuke

Brief description
As for maya, scriptmenu  integration for nuke.
Description
Scriptsmenu will help you to easily organize your scripts into a customizable menu that users can quickly browse and search.
Additional info
You have to update scriptmenu with the latest version.

It's normal, the problem has been fixed in the script menu .You have to update scriptmenu with the latest version.

thank you @ClementHector ;)


[AetheryteLinkInChat] Some aetherites do not contribute to distance calculations

Which plugin are you referring to?
AetheryteLinkInChat
Describe the bug
Some aetherites do not contribute to the distance calculation, so in reality, a more distant route is presented as the shortest route.
e.g. Yanxia (12, 30) for rank S Gamma
We should teleport to Doman Enclave but AetheryteLinkInChat suggests Namai village.

Most of issues i had with this was due to the fact that we only have an 2d coords, which means height is not accounted in the calculations, theres the fact that the calculation is not an path finder, its just an straight line from the aetherites to the flag ignoring walls, terrain, etc
The only solution i could come up with was to add negative weight to some aetherites to account for that, while this will work well for places like Tertium - Garlemald, it might not work well on others.


Option to disable linting in order to support es6/7 features

I've put together a plunk of the Aurelia navigation skeleton : http://plnkr.co/edit/uNVEk2
It uses jspm/babel to transpile es6/7 features.
However some features like decorators are not supported yet with jshint, so i have to add a //jshint ignore:true at the end of each line that jshint doesn't support yet.
If i don't do that and ignore the linting then the files do not get served by plunker...
Is there a way to disable linting for all files of a paricular plunk ? That would make it much easier for now to use es/7 features.

:+1:
Even better - let us use custom lint config.

There shouldn't be any reason that changing the linting options would affect plunker's ability to serve files. Perhaps this affects babel's treatment of these files.
I'm no babel expert but for those of you with experience, here is the code that transforms .6to5.js files into .js files: https://github.com/ggoodman/plunker-run-plugin/blob/master/adapters/transformers/6to5.js And .es6.js files into .js files: https://github.com/ggoodman/plunker-run-plugin/blob/master/adapters/transformers/es6.js
Bother are quite naive, simple translations. Are there any compiler flags for these libs (or conventions regarding these) to change the behaviour during compilation?

The linting does indeed not interfere with the compiling after all. The plunkers are working just fine with the lint errors
For babel experimental features can be enabled using the stage or the optional property : http://babeljs.io/docs/usage/experimental/

Can we just treat all .js files like ES6+ w/Babel and use ESLint? ES6 is the current recommended JavaScript spec. =)
See How to Use ES6 for Universal JavaScript, and prod-module-boilerplate.

I'm working on a nice ES6 compilation solution. As to linting, that needs
to be added to ACE and I don't have the bandwidth for that these days.
Geoff
On Fri, Jul 10, 2015, 9:33 PM Eric Elliott<EMAIL_ADDRESS>wrote:

Can we just treat all .js files like ES6+ w/Babel and use ESLint? ES6 is
the current recommended JavaScript spec. =)
See How to Use ES6 for Universal JavaScript
https://medium.com/javascript-scene/how-to-use-es6-for-isomorphic-javascript-apps-2a9c3abe5ea2,
and prod-module-boilerplate
https://github.com/cloverfield-tools/prod-module-boilerplate.
—
Reply to this email directly or view it on GitHub
https://github.com/filearts/plunker/issues/87#issuecomment-120561575.

:+1:

Note that there is also babel lint , that seems to work the best for now : https://github.com/babel/babel-eslint

That may be a good temporary solution. Long-term lint config should be user configurable.

I've re-written the ggoodman/plunker-run-plugin to support a new method of invoking compilation:

You can now use standard .js files but add the directive "use traceur"; or "use babel"; to cause those files to be passed through the respective compilers.
You can also pass options to these compilers with the following syntax: "use babel({stage: 0})" for when you would like to use settings that are not part of the default behaviour of these compilers.

What do you think? Let me know how it works for you.

@ggoodman

I've re-written the ggoodman/plunker-run-plugin to support a new method of invoking compilation:

Cool. Have you documented where / how to do this configuration?

I have not. Unfortunately, I don't really have any documentation. Those directives are to be put on the first line of your .js files. The actual directive will be stripped out (but not the newline).
 My JS files are examples for a JavaScript course. Can't config options like this be sourced from configuration files, instead?

What is the industry standard for holding this type of configuration file (babel, traceur, etc...). Linting is another discussion but it would be nice to know how that is configured as well.

.babelrc & .eslintrc are the standard ways to configure babel & ESLint, respectively. I haven't heard of anybody using traceur lately. I don't know the best way to configure it.
You could have a custom plunker config key in package.json and use that to configure anything you want...

I've updated the run server to read the file .babelrc in the current plunk and apply the configuration options therein to babel when compiling .babel.js, .6to5.js and .jsx to .js (also applies with the "use babel"; directive in a normal .js file).
This should fit pretty well with normal practices. Let me know what you think.

:+1:


[Enhancement]: candy crush

Is your enhancement request related to a problem? Please describe.➕
it is not working only displaying a page
Describe the solution you'd like
make  it working
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @priyanshibhatn , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#2778

Hey @priyanshibhatn ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @priyanshibhatn !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹


Picker now can easily chage color of bubbles + changed deployment target

I added to picker method setBubbleColor:selectedColor:, so user of picker can easily manage color of bubbles.
Deployment target changed from 6.0 to 4.3. It work nice on 4.3, so why not to use it there.
And also I've done some minor changes in .gitignore

@dvor how do I use this? The current master doesn't seem to have this feature :-1:  =/

@marcoscurvello take a look at THContactViewStyle

@dvor thanks for the heads up mate! :+1:


what is the replacement for isort --apply in 5.0.4?

Hi, thanks for the update 5.0.4 . According to the changelog for 5.0.4, --apply is removed and the functionality is default behavior now(https://timothycrosley.github.io/isort/CHANGELOG/)? I tried removing --apply (using via tox) but I still get the prompt before fixing any of my imports. Am I missing something here? Thank you.

I am facing this issue while running via tox.. --apply is required while running from a tox environment it seems otherwise I get the prompts. Any ideas on how to fix that?

Hi @Sahil-Ajmera, --apply simply doesn't exist in isort 5.0.0. If you need it within your tox environment, that means that your tox environment has isort 4.x.x installed within it. This makes sense as something that can happen, as tox intention is to isolate environments. I would ensure your dependency is set to 5 and delete your existing tox environment.

Thanks @timothycrosley


Update RelationExtractionVisualizer according to latest NumPy version

I am getting the following error stack when using the Numpy 1.25.x version
error stack:
..../spark-nlp-display/sparknlp_display/relation_extraction.py](https://localhost:8080/#) in __gen_graph(self, rdf, selected_text, exclude_relations, show_relations)
    369
    370         relation_distances = np.array(relation_distances)
--> 371         relation_coordinates = np.array(relation_coordinates)
    372         temp_ind = np.argsort(relation_distances)
    373         relation_distances = relation_distances[temp_ind]

ValueError: setting an array element with a sequence. The requested array has an inhomogeneous shape after 2 dimensions. The detected shape was (10, 3) + inhomogeneous part.

solution:
line 371:  add dtype=object
relation_coordinates = np.array(relation_coordinates, dtype=object)

fixed in version 5.0. https://github.com/JohnSnowLabs/spark-nlp-display/releases/tag/5.0


feat(mention): search event add a prefix param

Types of changes

[x] New feature
[ ] Bug fix
[ ] Enhancement
[ ] Component style change
[ ] Typescript definition change
[x] Documentation change
[ ] Coding style change
[ ] Refactoring
[ ] Test cases
[ ] Continuous integration
[ ] Breaking change
[ ] Others

Background and context

Solution

How is the change tested?

Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

Checklist:

[x] Test suite passes (npm run test)
[x] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[x] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others
should be submitted to main branch)

Other information

相关issues #2354

@flsion,有时间帮忙看一下，合一下代码发个版本，项目继续这个功能


Add message to ContentView metadata

This should greatly increase the flexibility of custom ContentViews

@pravic already convinced me in #3218 that this may be useful, even though content views should ideally not depend on any context. I'm happy to accept a PR that also exposes the flow object, but that needs to adjust all relevant calls to get_message_content_view.


Ensure DogStatsD source has full data type support.

Context
The DogStatsD source must have full data type support to match what can be accepted in the Datadog Agent and what can be sent by official DogStatsD clients:

counters
gauges
timers
histograms
distributions
sets
events
service checks

(Full list, with more detail, here: https://docs.datadoghq.com/developers/dogstatsd/datagram_shell/?tab=metrics#the-dogstatsd-protocol)
In scope

Decoding DogStatsD payloads with any of the above data types
Emitting a Metric that faithfully represents those decoded payloads

Out of scope
There's a number of very related items that are out of scope for this particular issue, but will be addressed separately as a follow-up.

Forwarding all data types to the Datadog platform.

Work items
(non-exhaustive, living list)

[x] #123
[x] #124
[x] #125

This is complete.
This source has full support for all relevant StatsD and DogStatsD data types, and those data types can be faithfully represented within Saluki.


Getting started with multiplexed samples

Add information about getting started with the multiplexed samples to the Getting Started. We want to make sure we cover how to filter to a sample of interest.

We're going to link to this section from the download modals for multiplexed samples. The first part needs to reiterate what a multiplex sample is (#77).


Feature/lru caching 2

What type of PR is this? (check all applicable)

[ ] Refactor
[X] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Have you discussed this change with the InvokeAI team?

[X] Yes
[ ] No, because:

Have you updated all relevant documentation?

[ ] Yes
[ ] No
[X] N/A

Description
This PR does two things:

It changes the Cache to LRU, i.e. when cache is full, Least Recently Used are removed first
It adds a thread lock to ensure that all cache operations are thread safe

Related Tickets & Documents

Related Issue #
Closes #

QA Instructions, Screenshots, Recordings

Added/updated tests?

[ ] Yes
[X] No : Too much work and unsure where to put them (not good!)
Honestly, I would sleep better if this had tests

[optional] Are there any post deployment tasks we need to perform?

I was just skimming and noticed that ThreadLock is not thread-safe in several places. It also doesn't lock reading during a write.
I'll hold off on reviewing in detail for now, since I saw some discussion on Discord that this might get re-implemented in a different way. Let me know when it's ready for a full review.

@RyanJDick - thanks for the comment. Would you mind elaborating on the lack of thread safety on the ThreadLock? I think I see one place that could be a problem and may or may not have an idea for a solution. Anyway, maybe you see something I don't. The count increments and decrements should be atomic in python so I don't see an issue there (correct me if I'm wrong, though). The gap between checking if the read lock is locked and acquiring it, that could be an issue.
The write decorator does pick up both read and write lock, though.

Probably for a different PR, but do you think it's feasible to provide an alternate cache limit strategy based on memory consumption?
I think that would be preferable in most cases to a numerical limit on entries. I wouldn't mind giving the cache a gig or so, if that means I my invoke just continually, incrementally accelerates.
I did some brief searching and saw some built-ins that measure the size of objects in memory in python, but also there were warnings that this was unreliable, so I didn't pursue it further.

@psychedelicious - yeah, I know what you mean. That would probably be the better way to go. It is not something that I have worked a ton with in the past but enough to know that, like you said, it's a bit iffy. It might still make sense to look into it at some point and get something approximate working. One of the issues that I can remember is garbage collection, which is automatic with an option to manually override. If a reference still exists elsewhere to an object that was deleted from the cache, it'll remain in memory, of course, so deleting it might not affect memory consumption. This is also why circular referencing can be a problem, because then the garbage collector can't always figure out if it can free up a chunk of memory. I'm sure there's other stuff I'm forgetting.

Gotcha, def a future exploration then.

I had another thought - if an invocation fails, do we want to cache its outputs? In a perfect world, invoke() would be a pure function, but it's not. We grab images, latents, models, who knows what else, from a wider context.
What if something transient caused a failure? If we cache that output, but then the transient issue is resolved, we end up with failures that should have been successes.
Probably cache-enabled call to invoke() in BaseInvocation.invoke_internal() should be wrapped in a try/except. We'd re-raise an exception untouched, but skip setting the cache in that case.
I wonder if the queue should default to pause-on-fail as well.

If it's okay with you, I'd rather not put more in this PR. Mostly just to avoid more back and forth if the text ends up being unclear or something.


pachage have deep problem :)

we have some problem, in package file, i run python file for login in panel and get_inbouds, but we have some errors for packages file.

 we have some problem, in package file, i run python file for login in panel and get_inbouds, but we have some errors for packages file.

solved:
pip install -U pyxui


Is it possible to add is-valid class after validation

I understand there is a way to add error css class, is there a way to add the is-valid class after validation?

{%if form.is_valid %}
{{form.field|add_class="is-valid"}}
{% endif %}

with render_field i am currently doing it like this:
{% if form.myfield.errors %}
    {% render_field form.myfield class+="form-control is-invalid" title=form.myfield.label %}
{% else %}
    {% render_field form.myfield class+="form-control" title=form.myfield.label %}
{% endif %}

lot's of repeated code. is there a better way?
i'd imagine something like an "error_class" argument would be nice, eg:
{% render_field form.myfield class+="form-control" error_class="is-invalid" title=form.myfield.label %}

I found this ticket right after submitting #126 , as far as I can tell,
{% if form.myfield.errors %}
    {% render_field form.myfield class+="form-control is-invalid" title=form.myfield.label %}
{% else %}
    {% render_field form.myfield class+="form-control" title=form.myfield.label %}
{% endif %}

does not handle the case of valid field from validated form, and we need something like
{% if form.myfield.errors %}
    {% render_field form.myfield class+="form-control is-invalid" title=form.myfield.label %}
{% elif form.bounded and not myfield.errors %}
    {% render_field form.myfield class+="form-control is-valid" title=form.myfield.label %}
{% else %}
    {% render_field form.myfield class+="form-control" title=form.myfield.label %}
{% endif %}

This is quite tedious if we are doing this for all fields, #126 proposes the shortening of the above to
{% render_field form.myfield|add_class:"form-control"|add_valid_class:"form-control is-valid"|add_error_class:"form-control is-invalid" title=form.myfield.label %}

or even better
{% with WIDGET_ERROR_CLASS='is-invalid' WIDGET_VALID_CLASS="is-valid" %}
    {% render_field form.field1|add_class:"form-control" %}
{% endwith %}


set block(breakable: false) twice

https://github.com/glambrechts/slydst/blob/9704ef9190842536866688ed4db314299a6a47cf/slydst.typ#L125C1-L127C1
  show stack: set block(breakable: false)
  show stack: set block(breakable: false, above: 0.8em, below: 0.5em)

Isn't the first line redundant?
PS: very nice minimalist package.

Hi, sorry for my late reply! Thank you for having spotted that. I'll remove the first line ;-)


Support Changesets

Now that we're comfortable enabling Git(Hub) things in our commands and Buildkite configs, we could conceivably build a Changesets-based workflow into skuba as an alternative to the existing semantic-release default in skuba release.

https://github.com/SEEK-Jobs/buildkite-changesets addresses our need to do this internally.


Fix request normalization for request body with a list as a JSON root

Fixes #536

Codecov Report

Merging #538 (a4312c3) into master (6399848) will decrease coverage by 0.14%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##           master     #538      +/-   ##
==========================================
- Coverage   98.53%   98.38%   -0.15%
==========================================
  Files          18       18
  Lines        1294     1302       +8
  Branches      204      207       +3
==========================================
+ Hits         1275     1281       +6
- Misses         10       11       +1
- Partials        9       10       +1

Impacted Files
Coverage Δ

requests_cache/cache_keys.py
95.78% <77.77%> (-1.92%)
:arrow_down:

Continue to review full report at Codecov.

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


Smoke tests are failing due to quick pick

1) VSCode Smoke Tests (Electron)
       Quick Access
         quick access search produces correct result:
     Error: Timeout: get elements '.quick-input-widget .quick-input-list .monaco-list-row .label-name' after 20 seconds.
      at poll (D:\a\1\s\test\automation\out\code.js:178:19)
      at async Code.waitForElements (D:\a\1\s\test\automation\out\code.js:258:16)
      at async QuickInput.waitForQuickInputElements (D:\a\1\s\test\automation\out\quickinput.js:25:9)
      at async Context.<anonymous> (out\areas\search\search.test.js:78:13)

  2) VSCode Smoke Tests (Electron)
       Language Features
         verifies quick outline:
     Error: Timeout: get elements '.quick-input-widget .quick-input-list .monaco-list-row .label-name' after 20 seconds.
      at poll (D:\a\1\s\test\automation\out\code.js:178:19)
      at async Code.waitForElements (D:\a\1\s\test\automation\out\code.js:258:16)
      at async QuickInput.waitForQuickInputElements (D:\a\1\s\test\automation\out\quickinput.js:25:9)
      at async QuickAccess.openFile (D:\a\1\s\test\automation\out\quickaccess.js:42:9)
      at async Context.<anonymous> (out\areas\languages\languages.test.js:16:13)

https://dev.azure.com/monacotools/Monaco/_build/results?buildId=132359&view=logs&j=672276a2-8d3a-5fab-615d-090c51352f92&t=316b23c8-21ca-5aab-3515-3225235af7bb
Failing tests are always not same but those tests which are failing are always due to quick pick widget

If this is from changes in gettingStarted.ts I wonder if our CLI argument to disable any welcome content in tests is not working anymore. I.e. I would not expect any welcome/getting-started etc. to interfer with smoke or integration tests.


[5.8] Only use $_SERVER for env variables

This change:

Tells phpdotenv to only write to $_SERVER and to only read from $_SERVER for resolving nested environment variables.
Changes Laravel's env function to only look at $_SERVER
Stops Laravel's env function stripping quotes.

Why?

In Local development, people are still confused when other websites are interfering with the environment variables. Moreover, the interference is both way, so Laravel variables are leaking out. By instead only reading and writing to the server superglobal, and avoiding putenv and getenv, we avoid this issue.
As mentioned in the first point, getenv is also not threadsafe, so variables may leak into Laravel apps even though we're not calling putenv ourselves. The only other consequence of this change I envisage will be case sensitivity of variable resolution, however I don't envisage this being an issue, as I think most people will be getting their case correct when they do the calls, since nearly everyone uses uppercase, and is used to typing it.
phpdotenv already natively handles quoted variables, so I don't see the need to strip quotes off again. This is only going to be annoying if you'd escaped the quotes in the env file, then laravel strips then anyway.

Sounds good

Do we need to write to $_SERVER at all? Can't we just use it for reading only and combine them with the .env values? In production it's also not written to the super globals, right?

phpdotenv is made for development environments, and generally should not be used in production. In production, the actual environment variables should be set so that there is no overhead of loading the .env file on each request.

I know we have the ability to cache the contents of the .env file so the production thing is sort of moot, but will this change affect people storing config in actual environment variables, rather than the file in production?
If we no longer use $_ENV, that is? Or do proper environment values end up in $_SERVER, as well?

phpdotenv is made for development environments, and generally should not be used in production. In production, the actual environment variables should be set so that there is no overhead of loading the .env file on each request.

This is no longer the case for v3. I should probably update the readme.

Do we need to write to $_SERVER at all? Can't we just use it for reading only and combine them with the .env values?

Yes, actually we could do that instead if we wanted (https://github.com/vlucas/phpdotenv/blob/master/src/Environment/Adapter/ArrayAdapter.php). The side effect would be that nested env variables would break though, if they were loaded outside of the env file. We'd also need to find a good way to share this adapter instance.

If we no longer use $_ENV, that is?

That was actually never used, and is kinda badly named. The sever superglobal behaves as you might expect env to.

Or do proper environment values end up in $_SERVER, as well?

Yes, always, and not always in the env supergloal.

In production it's also not written to the super globals, right?

Yeh, so no changes there. :)

Rock on 🤘🏻

@GrahamCampbell can you send in the same PR to lumen-framework?

Yes, of course. :)

Is a 5.8 branch getting split off there soon also?

@driesvints here we are: https://github.com/laravel/lumen-framework/pull/877 and https://github.com/laravel/lumen/pull/128.

Is a 5.8 branch getting split off there soon also?

We're going to do this after the framework release.

@GrahamCampbell or @driesvints is this a breaking change for when you upgrade from 5.7 to 5.8? If so we maybe also need to update the "Upgrade Guide" for the docs to tell people to change the phpunit.xml file

phpunit config does not need changing actually.

See https://github.com/laravel/framework/pull/27519.

We had to update our phpunit.xml file to add force="true" on our environment variables. I can't say with 100% confidence it's related to this change, but perhaps someone else will see this and want to give it a try.

Sorry for posting 6 years too late, but I made a package that provides env() standalone, and in a way that preserves Laravel 5.7's behavior:
https://github.com/PHPExpertsInc/Laravel57-env-polyfill
composer require phpexperts/env


Add flags to toolchain Info.plist to allow using macros from Apple's SDKs with an open-source toolchain when building in Xcode

Add the required build settings overrides to the toolchain's info.plist to allow loading macros from the Xcode default

@swift-ci please build toolchain

fixed typo
@swift-ci please build toolchain macOS

fixed one more escaping issue
@swift-ci please build toolchain macOS

Verified that https://ci.swift.org/job/swift-PR-toolchain-macos/728/artifact/branch-main/swift-PR-66365-728-osx.tar.gz contains the correct Info.plist content, and that using macros from the SDK works in Xcode 15 beta with this toolchain selected. Also verified that the unknown frontend flags are correctly ignored when building using Xcode 14.3

@swift-ci please smoke test

Adding @shahmishal since this affects the swift.org toolchains


Fix #5 - auto-format on save removes CDATA block

Bug fixed and added some tests for the auto-format feature.

If you write fixes #5 in your PR description, github will auto-close the issue for you.


Convert ParameterizedBenchmark to tf.test.Benchmark.

Add PerfZeroBenchmark into benchmarks folder and use PerfZeroBenchmark as base class. It can be run both on Bazel tests and PerfZero script.
We decide to use tf.test.Benchmark for our benchmark.

@xingyu-long Can you please resolve conflicts? Thanks!

@xingyu-long Can you please resolve conflicts? Thanks!

Since host and I decided to hold this PR for now, but I will talk to her about this.

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

Already update in another PR


video quality and network detection

Hello,
We are the using the old version of plyr.io video player and recently we have added the video quality feature, where the user can select the preferred video quality. We just had a question. If we add 3 videos for 3 different video resolution, which one will be selected as default? Does the Plyr automatically detects the network speed and plays the best suitable one? or is it related to ordering of the 'source' tag?

You can set the default quality when you initialize Plyr like this:
var players = Plyr.setup('.js-player',
  {
    quality:
      {
        default: 720
      }
  }

If the default quality isn't there in the markup, the highest one is probably selected.
From my knowledge, Plyr won't switch quality based on network speed, you'd have to do it yourself.

Hi, we have achieved it.
But we have a new query, in the quality section it shows the quality as 1080,720,480 and so on, according to the value assigned in the size section. can we change it and provide a title for the sources quality, so that in the player it shows as High, medium and low instead of the actual resolution value? (1080,720,480)

Yes, you can do it like this:
var players = Plyr.setup('.js-player',
  {
    // your config
    i18n:
      {
        qualityLabel:
          {
            1080: 'High',
            720: 'Medium',
            // and so on...
          }
      }
  });

Hi, thank you for your help.
we are setting up the player in this manner,
const player = new Plyr(video, {captions: {active: true, update: true, language: 'en'}});
player.source = {
type: 'video',
title: '576 resolution video',
poster: poster,
sources: [
{
src: lowSrc,
type: 'video/mp4',
size: 480,
},
{
src: medSrc,
type: 'video/mp4',
size: 720,
},
{
src: highSrc,
type: 'video/mp4',
size: 1080,
}
],
};
if I put the i18n object inside the sources object it does not work. Can you please suggest where we are going wrong?

It doesn't go in sources, it goes in the options, like this:
const player = new Plyr(video,
  {
    captions:
      {
        active: true,
        update: true,
        language: 'en'
      },
    i18n:
      {
        qualityLabel:
          {
            1080: 'High',
            720: 'Medium',
          }
      }
  });

// your sources

@suvamkundu what was the solution for the network detection part? ended up doing it manually?


Reduce the Number of Migration Files

I noticed when adding the forem engine to our website that there were a total of 32 migration files generated. I took the liberty of merging them into 9 individual table files, 1 admin file, and 1 update file. This change has been tested and thus far works without issue.

My bad, I stumbled upon the 'CONTRIBUTING.md' file several hours after creating this pull request. I am currently in the process of fixing those errors presented in the 'rspec spec' tests.

If you are talking about the Travis CI test failures then all of them are currently caused by Forem specifying
s.add_dependency 'rails', '~> 4.0', '<= 4.2'

in the gemspec even though there is no Rails 4.2 support right now. This means that the tests are run in the context of a Rails 4.2 app and results in a lot of errors. Rails 4.2 support and all the errors have been fixed but not yet pushed to Forem since there is a bug in Rails 4.2 that prevents the push. More details here: https://github.com/radar/forem/issues/640

Good to know; I will push my updates based on the contribution standards.


Lazy_Dataset not up to date

Hello,
I got following error, trying to start a training:
Traceback (most recent calls WITHOUT Sacred internals):   File "/workspaces/pb_sed/pb_sed/experiments/strong_label_crnn/training.py", line 355, in train     trainer.test_run(train_set, validate_set)   File "/root/.local/lib/python3.9/site-packages/padertorch/train/trainer.py", line 190, in test_run     test_run(   File "/root/.local/lib/python3.9/site-packages/padertorch/train/runtime_tests.py", line 201, in test_run     sub_train_iterator = list(itertools.islice(train_iterator, 2 * virtual_minibatch_size))   File "/root/.local/lib/python3.9/site-packages/lazy_dataset/core.py", line 1725, in __iter__     yield from map(self.map_function, self.input_dataset)   File "/root/.local/lib/python3.9/site-packages/lazy_dataset/core.py", line 2071, in __iter__     yield from self._single_thread_prefetch()   File "/root/.local/lib/python3.9/site-packages/lazy_dataset/parallel_utils.py", line 301, in single_thread_prefetch     raise exc_info[1].with_traceback(exc_info[2])   File "/root/.local/lib/python3.9/site-packages/lazy_dataset/parallel_utils.py", line 263, in worker     for item in generator:   File "/root/.local/lib/python3.9/site-packages/lazy_dataset/core.py", line 1725, in __iter__     yield from map(self.map_function, self.input_dataset)   File "/root/.local/lib/python3.9/site-packages/lazy_dataset/core.py", line 3355, in __iter__     bucket = self.bucket_cls(example, **self.bucket_kwargs)   File "/root/.local/lib/python3.9/site-packages/padertorch/contrib/je/data/utils.py", line 26, in __init__     super().__init__(init_example, **kwargs) TypeError: __init__() got an unexpected keyword argument 'max_buffered_examples'
I saw, that this variable max_buffered_examples exists in the current master branch of the lazy_dataset, but not in the tagged version 0.0.14 which is downloaded by following the installing instructions for the pb_sed repo. Is this a mistake that can be fixed by applying a new tag to the changes you made to lazy_datasets two month ago by adding/renaming the max_buffered_examples  variable?
Best Regards

Hi, actually the tag lazy_dataset.git@dc9f487bd433a9ccc8e157d58e338074e3cd8705 should already include the renaming. It could be that sed_scores_eval installation overwrites it by installing lazy_dataset from pypi, which is an older version I guess. Therefore I updated the readme so that lazy_dataset should be installed after sed_scores_eval. Simply rerun pip install --user git+https://github.com/fgnt/lazy_dataset.git@dc9f487bd433a9ccc8e157d58e338074e3cd8705and you should be good.


Import Chat Module and Getting Crash On Splash

Hi
I just import basic chat sdk and I'm getting crash on Splash. I didn't know I'm getting AUTH crash please check screenshot ->

@DevAppcrates have you gone through this video?
https://github.com/chat-sdk/chat-sdk-android#quick-start
This problem comes from an incorrect Chat SDK setup. The auth service is null. It can also happen when you don't setup the Chat SDK in the main Application class.

Closing due to inactivity.


smoke tests should use short tmp directories to store files needed for test

The smoke tests store the files generated by the tests (blocks, databases, logs, and most relevantly in this case, .sock files) inside the directory in which they are run from, which is the build directory. As part of the test, keosd runs with unix-socket-path set to the eosio-ignition-wd/keosd.sock file within the build directory. The problem is that the length of the path for a Unix socket cannot exceed approximately 100 characters. So depending on how long is the path of the build folder, the smoke tests may fail.
The smoke tests should be updated to place their files inside a unique temporary directory in /tmp with a short enough name to guarantee that the .sock file does not exceed 90 characters.

I ran into this issue today.
Apple NP tests worked on the eosio pipeline, where the path to /build/eosio-ignition-wd/keosd.sock on mac was 99 characters. But using eosio-beta for the pipeline slug resulted in a path to /build/eosio-ignition-wd/keosd.sock which was 104 characters, causing all NP tests on both High Sierra and Mojave to fail except the first two.

But using eosio-beta for the pipeline slug resulted in a path to /build/eosio-ignition-wd/keosd.sock which was 104 characters, causing all NP tests on both High Sierra and Mojave to fail except the first two.

Unfortunately the eosio-beta pipeline containing the history and logs of which tests were effected by this issue was deleted because it was just a temporary pipeline for testing. I recreated the eosio-beta pipeline here and it should still exhibit the same behavior. I also created a pipeline with an even longer pipeline slug, eosio-beta-with-some-very-long-pipeline-slug, here.
This issue can also be replicated on any machine by cloning the eos repo to a spot in your filesystem where the path to /build/eosio-ignition-wd/keosd.sock from root / is greater than 100 characters.

hi @kj4ezj @arhag I think it is pretty likely that the eosio-ignition-wallet will only be created by the bios_boot.sh script which is created by eosio-launcher. If PR https://github.com/EOSIO/eos/pull/7444 is merged, eosio-launcher will always assign a tcp port number for ignition wallet by the logic of calculate_port(cluster_id, 0, port_type::keosd). And because of this, we might not need to relocate the path of keosd.sock.

In order to focus our efforts on issues that are currently creating difficulty for the community we are closing tickets that were created prior to the EOSIO 2.0 release.  If you believe this issue is still relevant please feel free to reopen it or create a new one.  Thank you for your continued support of EOSIO!


Security Policy

What article on docs.github.com is affected?

What part(s) of the article would you like to see updated?

Additional information

(#1302

Sent from my Galaxy S9+ using FastHub

This issue is blank and appears have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in discussions!


Unable to find workflow in example.png

Hello, I'm curious if the feature of reading workflows from images is related to the workspace itself. I've encountered an issue where, every time I try to drag PNG/JPG files that contain workflows into ComfyUI—including examples from new plugins and unfamiliar PNGs that I've never brought into ComfyUI before—I receive a notification stating that the workflow cannot be read. Strikingly, PNG files that I had imported into ComfyUI previously can still have their workflows recognized without any problems!
Despite trying multiple different ComfyUI package integrations, the issue remains unresolved. Could you shed some light on why this might be occurring or recommend steps for addressing it?

hi i don't think this is related to comfyui workspace manager. its probably the problem with comfyui itself.

OK, although I answered very late, thank you very much. I have solved it myself and there is no problem

I had the same problem, how did you solve it?

OK, although I answered very late, thank you very much. I have solved it myself and there is no problem

I had the same problem, how did you solve it?

OK, although I answered very late, thank you very much. I have solved it myself and there is no problem

OK, although I answered very late, thank you very much. I have solved it myself and there is no problem

I had the same problem, how did you solve it?

OK, although I answered very late, thank you very much. I have solved it myself and there is no problem

I had the same problem, how did you solve it?


Propose Middleware Solution

This is a proposal and code sample for adding middleware to the light bug project.
Proposal
The chain of responsibility design pattern is used to chain together pieces of middleware that will each handle some aspect of the Request/Response.  This allows someone to choose which middleware they want and allow them to remove or replace anything they need.  It also supports adding their own custom middleware.
The Context is used to wrap the HTTPRequest and provided a dictionary of parameters.  It should support AnyType of value so you can add middleware to handle authentication or parsing cookies, query strings, paths and provide that to other middleware or handlers.
In the middleware package, I've provided 8 example middleware handlers: Error, Compression, Logger, CORS, Basic Authentication, Static, Router, and NotFound.
The Router middleware is special in that it allows for different leaf nodes to be registered for a particular Request Pattern.  This can become complex with routing based on any method, path, header combination.  Also, it will need to support variable paths.  The one provided is very rudimentary.  We will want one that uses a high speed tree structure for the best performance.
The HTTPHandler trait is used by the Router for the leaf nodes.  We can add a LambdaHandler and support Lambdas when they become available.
The NotFound is the last item in the chain.  If no other middleware handles the Request, it will return a 404, not found response.  By not hard coding this in the Router, we can support multiple routers in the chain which provides flexibility for mounting other projects or have Authorized vs Unauthorized routes.
The MiddlewareChain handles creating the linked list of Middleware.  I added support for the existing HTTPService trait so it can easily be used instead of the existing services.
The lightbug_http.mojo was modified to demonstrate the use of the Middleware.
I also renamed the lightbug_welcome.html to index.html so the StaticMiddleware could be used.
Current Issues:

Traits are not fully supported yet so the next in the middleware and the root in the chain are failing to compile:

/middleware/router.mojo:11:5: error: TODO: dynamic traits not supported yet, please use a compile time generic inste
ad of 'Middleware'
    var next: Middleware

The Dict collection requires the value to support the CollectionElement trait.  Both the HTTPHandler and AnyType are traits and not implementations so this causes issues with the Dict in the Router and Dict in the Context that holds the parameters.

/middleware/router.mojo:12:30: error: 'Dict' parameter #1 has 'CollectionElement' type, but value has type 'AnyTrait
[HTTPHandler]'
    var routes: Dict[String, HTTPHandler]

This looks really good! Thank you for this contribution.
For me the most important question is how to distribute this functionality between this library (lightbug_http) and potential future libraries like lightbug_api or lightbug_web which are all supposed to build on each other.
I looked at how this is done in other languages. Seems like middleware infrastructure is normally already included in basic libraries like lightbug_http, e.g. Python's Starlette that I'm heavily using as inspiration for lightbug_http includes the middleware class and two implementations: ServerErrorMiddleware and ExceptionMiddleware.
Deciding where to put the context part is a bit more challenging. I've noticed at least 2-3 different approaches to this.

Starlette does not include context by default in the library, there's a third-party package that can be imported to provide this.
In Golang, context is part of the standard library and usually just imported in addition to a framework, which is nice. Not sure if it will be added to Mojo stdlib, at least it is not there currently.
In Rust, e.g. Actix, which I think lightbug_http is also in spirit of, does include context in the package, but it also has the concept of actors which carry context, which we probably (?) wouldn't want to explore.

About the technical issues you mentioned:

For issue 1, I had to deal with this before. The way I did this is to actually cut down on the use of traits so far due to e.g no support for dynamic traits. Same here, we could just remove traits or make them serve purely as a reference. For example, the BasicAuthMiddleware might not inherit Middleware for now. Not pretty, but should allow us to start using/iterating on this early. Maybe there's a better solution for this, not sure...
Issue 2 is trickier, because we don't know what kind of handlers the users will write. Maybe we can just pass a fn() instead of a handler trait. I know this is done in systems programming, e.g see this Golang library for middlewares. But if we find a way to make the trait work this is of course preferred

Thanks for taking a look at the proposal.
It looks like Mojo will need to mature a bit before we can build out a proper web framework.  I'm hoping they provide a standard for creating middleware built-in to the Mojo standard library.  The Crystal language did this and it helped with compatibility between frameworks.
Regarding the issues, I think rust like traits, go like interfaces or OO inheritance will be needed for the duck typing to work.  Looking forward to when Mojo properly supports this capability.

Posted a thread on the questions channel in Discord, perhaps the community will have some ideas.

@drujensen artemiogr97 from Discord suggested we do this:
@value
struct RouterMiddleware[HTTPHandlerType: HTTPHandler](Middleware):
    var next: Middleware
    var routes: Dict[String, HTTPHandlerType]

    fn __init__(inout self):
        self.routes = Dict[String, HTTPHandlerType]()

I tried it out, seems to work! Compiler error went away. Guess I should've read Mojo docs more closely 😅

@drujensen should we continue to pursue this, since duck typing seems to work?

@savioran I have tried the approach but haven't figured it out yet.  I'm a nooby to Mojo and the metaprogramming stuff takes a bit to get used too.  The documentation is sparse and copilot is useless.  I do have the lsp working in neovim so that should help make the process a bit smoother.  I will continue to look into this and see if I can get a working version.


CopyToDma: Fold CastOp and ExpandShapeOp into air::DmaMemcpyOp

It seems like condenseMemrefDataReorderingToAIRDma is a canonicalization pattern? Should it be implemented as one so that it runs whenever the canonicalilzer runs and not just during this pass? It might also simplify the code to consider each case as a simple canonicalization pattern, instead of as nested if's trying to do the whole thing at once.

Totally agreed. The lack of such canonicalizer has been creating issues for air.dma_memcpy_nd and air.channel.put/get, as subsequent passes can no longer handle those memref ops. I updated the issue https://github.com/Xilinx/mlir-air/issues/707 to keep track of this.


Fixes #431 by changing the order of the database upgrade

This solves my database upgrade issue. Fixes #431
Looking at the other upgrade queries, I don't see other dependencies that could have been broken by the different order.

The failing flutter test seems unrelated to my change, I'm not sure why it fails (or why it didn't fail before). Any idea?


How to add additional argument to qsub.

Hi,
I want to submit my cgat pipeline jobs to a gpu, and it requires additional arguments in the qsub command specifically
qsub -q short.qg -l gpu=N,gputype=XYZ
How can I specify  the -l gpu=N,gputype=XYZ bit in my cgat pipeline?
Thanks
Charlotte

Ah I worked this out once and wrote some code but I can't remember if I ended up committing code or not. I will check when I have time tomorrow.

Any luck with this?

Im wondering if you add this to your .cgat.yml for the batch section

so it would be
cluster:
  queue: short.qg short.qg -l gpu=N,gputype=XYZ

Thats much simpler than I expected, thanks!
I actually wanted to submit just one job in the pipeline to the gpu but coding the job as in
P.run(cmd, job_queue="short.qg -l gpu=N,gputype=XYZ") within the pipeline script works also.

Sorry it took a while, just been very busy so didn't really have time to think about it until this morning


test parse_radio_block done

^^^

this pr should make the checking of the block contents easier once implemented. Until then can you also add some tests to ensure that we catch errors correctly?

Surely

I'm not sure what this is testing that isn't covered by test_block_data and test_block_header in the tests/parsing/ directory. Was there something those test cases don't cover that you were hoping to implement? Could that test be added to one of the other test files?

I wanted to test that the parse_radio_block function works correctly when applied generally to the received information, whereas test_block_data tests for specific block types.

I'm not sure what this is testing that isn't covered by test_block_data and test_block_header in the tests/parsing/ directory. Was there something those test cases don't cover that you were hoping to implement? Could that test be added to one of the other test files?

I wanted to test that the parse_radio_block function works correctly when applied generally to the received information, whereas test_block_data tests for specific block types.

Gotcha, makes sense!

This PR conflicts with main so make sure you merge main and re-request a review.

nvm it broke


Crd docs

Description

Spawned from https://github.com/kubewarden/docs/pull/428.

Test

Additional Information
Tradeoff

Potential improvement

Added the request for review from @kubewarden/kubewarden-documentation manually on this PR, once the new CODEOWNERS file is in main, it should be automatic.


Root CA certificate not readable by Ansible (create-local-ca)

Running the build-a-bastion playbook fails because of permission issues in the CA files.  The create-local-ca task uses the incorrect group for setting permission on the new private key file, and then the signing of the certificate fails because the root CA file is not readable.

Updated permissions in the Ansible playbooks (it has broken my dev systems in Sydney temporarily because they aren't based originally on the Endicott lxocpb01, but this can be pushed out).
Moving milestone to release-10. since it's not a bug for moving to beta test.

Recent deploy seems like this is now fixed. 👍


Haste is always on!

So, I just started playing with Haste and love that I can always be hasted!  In talking with @nwinter I realize that the issue is the fact that haste is affecting the passage of time toward the cooldown allowing me to haste in 5 seconds instead of 10 seconds.  If we just changed all the specific cooldowns to 15 seconds that would amount to 10 real seconds as the first 5 seconds would be hasted and count as 10 seconds, leaving another 5 seconds of cooldown after the haste has expired.
Of course, this only works if the haste is cast on self.  If haste is cast on someone else then this wouldn't be good.
I was going to change the specific cooldown in the thang, but I guess maybe it needs to be done on the code side, will see if I can figure out a way to do it there.
OK, so in action.Acts I see this line:
    @actionHeats[@action] = action.specificCooldown if action.specificCooldown

I was thinking of adding something like this:
    @actionHeats[@action] = action.specificCooldown*1.5 if @getActionName() == 'haste' and @target == @

I'm not sure if I have the syntax correct or if it will work anyway.  The thinking is checking if the action is 'haste' and the target is self.  Would this work?

So I was thinking about this a little more.  As it stands, even if haste were to have a 10 second cooldown, with the way that cooldowns are affected by haste as well, you could conceivably keep the enemy slowed for 75% of the time while you are hasted for 50% of the time:
t=0 haste on, slow on
t=5 haste off, slow recast
t=10 haste on, slow off
t=12.5 slow recast
t=15 haste off
t=17.5 slow off
t=20 repeat cycle
So the enemy is slowed for 15 out of 20 seconds.  Maybe the speed up shouldn't affect spell cooldowns at all?  Or maybe haste and slow should have the same cooldown or be on different items so you can't have both of them or...

So I was thinking about this a little more.  As it stands, even if haste were to have a 10 second cooldown, with the way that cooldowns are affected by haste as well, you could conceivably keep the enemy slowed for 75% of the time while you are hasted for 50% of the time:
t=0 haste on, slow on
t=5 haste off, slow recast
t=10 haste on, slow off
t=12.5 slow recast
t=15 haste off
t=17.5 slow off
t=20 repeat cycle
So the enemy is slowed for 15 out of 20 seconds.  Maybe the speed up shouldn't affect spell cooldowns at all?  Or maybe haste and slow should have the same cooldown or be on different items so you can't have both of them or...

I've changed it so that any sort of haste/slow doesn't affect specificCooldowns, just general cooldowns. So you'll still attack and move faster or slower, but your spells and bashes and things will follow the regular intervals.


Add a 'download' language for fetching pre-built binaries

This implements https://github.com/pre-commit/pre-commit/issues/1453#issuecomment-1702880253

The latest WIP is a96e3ba8c3e6dc5f2c3f379b5e7d19805386ae9f. Feel free to have a look. I haven't done the netrc and modification to health_check yet.

I did everything, other than netrc changes. I will try and do it tomorrow.

I added netrc, but I haven't added any tests for testing authentication.


When will m series chips be supported?

Windows 11 installed by PD cannot install the virtual network card driver normally.

please provide output of systeminfo
(I own laptop win 11 installed, everything works like a charm)

I am the m1max chip of macos

主机名:           SHUID7EE
OS 名称:          Microsoft Windows 11 专业版
OS 版本:          10.0.22631 暂缺 Build 22631
OS 制造商:        Microsoft Corporation
OS 配置:          独立工作站
OS 构建类型:      Multiprocessor Free
注册的所有人:     Shui
注册的组织:
产品 ID:          00330-80000-00000-AA353
初始安装日期:     2024/7/9, 20:26:08
系统启动时间:     2024/7/10, 3:46:27
系统制造商:       Parallels International GmbH.
系统型号:         Parallels ARM Virtual Machine
系统类型:         ARM64-based PC
处理器:           安装了 8 个处理器。
[01]: ARMv8 (64-bit) Family 8 Model 0 Revision   0   ~3200 Mhz
[02]: ARMv8 (64-bit) Family 8 Model 0 Revision   0   ~3200 Mhz
[03]: ARMv8 (64-bit) Family 8 Model 0 Revision   0   ~3200 Mhz
[04]: ARMv8 (64-bit) Family 8 Model 0 Revision   0   ~3200 Mhz
[05]: ARMv8 (64-bit) Family 8 Model 0 Revision   0   ~3200 Mhz
[06]: ARMv8 (64-bit) Family 8 Model 0 Revision   0   ~3200 Mhz
[07]: ARMv8 (64-bit) Family 8 Model 0 Revision   0   ~3200 Mhz
[08]: ARMv8 (64-bit) Family 8 Model 0 Revision   0   ~3200 Mhz

is it Windows 11 ARM64 ?
I guess windows on arm64 requires drivers to be certified https://learn.microsoft.com/en-us/windows-hardware/design/compatibility/whcp-certification-process
(not sure if that is available to be turned off)

Well, I couldn't solve this problem, but I successfully installed the virtual network card through openvpn. Next, I will test whether softethervpn can normally access through openvpn.


Error in the "@foreach(var items in Items)"

Description
Following the example on this page (see Page URL below), the "Items" in the @foreach loop has the error:
foreach statement cannot operate on variables of type 'RenderFragment' because 'RenderFragment' does not contain a public instance or extension definition for 'GetEnumerator'
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/templated-components?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/templated-components.md
Document ID
ae663e33-6a08-0b24-aa19-3fc3c9edccfc
Article author
@guardrex

Thanks for the report @goCORA ... I'll check on this and get back to you shortly. I happen to be working on the snippet sample apps right now, and I'll place this code, repro the error here, and then take it from there. Stand-by .............

I have corrected it. My mistake. Sorry for the false indication of an issue

No worries. Closing now.


Change application icon to indicate notifications are present

For the duration of the presence of a notification on the VSCode screen, VSCode's icon should be changed to indicate that the notification exists.  (Like a mail reader's icon changes in the task bar when you have e-mail.)
In issue #80285 , I also suggest that notifications that happen while VSCode is not in focused should not disappear until 15 seconds after VSCode comes into focus.
The point of this is to enable VSCode extensions that monitor for events outside of VSCode - e.g. a pull request or a work item being assigned to the user, or somebody pushing code to the branch that the user is working on.

Add this at the start of this issue's title:  [FEATURE REQUEST]
Cheers!

@bpasero - we might be committed enough to this idea to contribute the code ourselves.  If we did that, would you be receptive to it?

Thanks for the offer, but currently not. We appreciate help for issues marked as "help wanted" or "good first issue".
Note that meanwhile, I pushed a change that notifications will remain visible when the window has no focus, even from extensions.


List of vendors + contracts used by a specific department

From Debra's feedback on 5/6: the goal of this feature would quickly show a list of contracts used by her department, I&P. When she's paying a stack of invoices, she prefers to see a list of vendors (like on her paper spreadsheet), instead of looking up vendors one at a time in Wex.
Ideas for implementing:

[ ] Use departments already associated with contracts (and consequently, vendors) from Bill/Ed's spreadsheet
[ ] Create lists from contracts your team is following

Should we be moving wexplorer issues to pittsburgh-purchasing-suite or keep them here @bsmithgall?

Yeah this should be moved, it's not really achievable under the current Wex backend setup.


Failed to compile with dependency:majicc

Basically, I tried to compile pleroma, and this has caused this one error regarding majicc. I gave it linux-headers in addition, but it's not compiling properly. Also would postgresql-13 be affecting it? should i go lower of a version?
The full screenshot is below

I'm on the latest version of Debian 10, docker and docker-compose are installed as well. This is in a VM.

Thanks for the report, I've added the new dependency to the Dockerfile :)


Rewrite GradleCommandHandler for NetBeans 12.6. (#8)

And rename the support for the old separate Gradle plugin (NetBeans <
10) to GradlePluginCommandHandler. Note that I have not tested any
intermediate versions between 8.2 and 12.6, only version 8.2 and version
12.6.
com.tusharjoshi.runargs.Constants (GRADLEPROJECT): Rename to
GRADLEPLUGINPROJECT. Add a new constant GRADLEPROJECT equal to
"org.netbeans.modules.gradle.NbGradleProjectImpl" for the new built-in
NetBeans gradle module.
com.tusharjoshi.runargs.GradleCommandHandler: Rename (copy) to
GradlePluginCommandHandler. Rewrite (mostly) this class for the new
built-in NetBeans gradle module:
(CMD_LINE_ARGS_PLACEHOLDER): Remove this private static constant.
(CMD_LINE_ARGS_GRADLE_ARG, RUN_CLASS_NAME_GRADLE_ARG,
RUN_ARGS_GRADLE_ARG): New private static constants of type String.
(SELECTED_CLASS_PLACEHOLDER): Update the value of this private static
constant from "${selected-class}" to "${selectedClass}".
(replacePlaceholder): Remove this no longer used private method.
(actionImpl): Rewrite this method completely.
com.tusharjoshi.runargs.ProjectAction (lookupChanged): Add
Constants.GRADLEPLUGINPROJECT to the supported project classes.
com.tusharjoshi.runargs.CommandHandler (createCommandHandler):
Add a case for Constants.GRADLEPLUGINPROJECT, returning a new
GradlePluginCommandHandler.
Fixes #8.

I have merged the PR, and will check for making a release in some days.  Thanks for the changes.

Yes Ok. I will test the changes for the new version and will make a release for the new version then


Enhancement Request: Skip Button

Rubengees,
No Skip button feature could be found inthe Wiki for the Introduction library. Would it be possible to add a Skip Button to add Slides to allow the user to exit more easily?
Thanks,
Jeff

Yes it is not in now, I will look into it.

https://github.com/rubengees/introduction/releases/tag/1.1.5
Take a look if the setSkipEnabled(String text) and setSkipEnabled(int resource) methods fit your expectations.

Thanks for quick response. It may take me a few days to try it. I ran into an unrelated issue that I have been unable to resolve with an Android library. See Android Issue 198963 (https://code.google.com/p/android/issues/detail?id=198963) if interested.

I appreciate the adding of the Skip button, but my app is compiled for API 10 and above which is one of the main reasons that I chose the Introduction library. Per the url in your last message that by adding the skip button, API 11 or above is now required. Any possibility to keep the API requirements to 10 or above?

It should not. I can compile release 1.1.5 with api 10.
What is the error message or the relevant code?

Ahh you mean 'Animations for the previous and next button on Api >= 11' ?
That only means that for Api >= 11 there will be animations and lower than that there are simply none, but works nevertheless.

I tried to add the withSkipEnabled method to my Android Studio project, but Android Studio does not find it. I can see the following code at this url https://github.com/rubengees/introduction/blob/master/library/src/main/java/com/rubengees/introduction/IntroductionBuilder.java
@NonNull
public IntroductionBuilder withSkipEnabled(@NonNull String text) {
    this.skipString = text;
    this.skipResource = null;

    return this;
}

I tried to build the project anyways, and I got the following with error. It appears that the Introduction library has not been updated yet on the GitHub website yet.
Error:(400, 17) error: cannot find symbol method withSkipEnabled(int)

What is in your build.gradle?
Hava you upgraded to
compile ('com.github.rubengees:introduction:1.1.5@aar'){
        transitive = true;
}

?

My build gradle is pasted below. Do you need to change the version number to allow the changes to be recognized in GitHub because it was 1.1.5 before the addition of Skip button code?
compile('com.github.rubengees:introduction:1.1.5@aar') {
    transitive = true;
}

Before I added the skip button it was 1.1.4. Now it's 1.1.5. Don't you get the feature with that build.gradle?

No...I can not get the skip button feature to be recognized in Android Studio, but all of the other Introduction library features that I am using works. I have tried the String and resource versions of the method, but neither one works for me. Also, tried using the library in another project, but while the features are recognized by Android Studio, the withSkipEnabled method is not.
    result.add(new Slide()
            .withTitle(R.string.slidetitle1)
            .withDescription(R.string.slidedesc1)
            .withColorResource(R.color.orange)
            .withSkipEnabled("Skip")
            .withImage(R.drawable.slide1));

Very weird. Check the following and report back:

Rebuild your Project in Android Studio (Build -> Rebuild)
Clone this project and try to run the sample

I also let JitPack rebuild the library, maybe that helps.

I tried the following steps that you suggested, but it did not work.
Delete the .gradle folder in your home directory
Rebuild your Project in Android Studio (Build -> Rebuild)
I am not sure of the meaning of the other 2 suggestions
Clone this project and try to run the sample
I also let JitPack rebuild the library, maybe that helps.
However, I downloaded the zip file of the library and imported it into Android Studio on my system. It appears that you may need to update the Slide.java file with the withSkipEnabled method like the other public methods.

Ah I might know what your problem is. The skip methode is called on the IntroductionBuilder and not on a single Slide. Take a look at the sample.

Thanks pointing in the right direction! It works now. I closed out this enhancement/issue.


Install optional dependencies for tests

Description
I've noticed when I added new test dependencies while working on https://github.com/serverless/console/pull/556 they were not installed in the CI/CD. I've fixed the CI flows so that the test dependencies are installed before the tests.
Testing done
We'll see it in the CI 🤞

@medikoo ready for review please 🙏


feat: add pubsub to libp2p

CI is green (we need to support Windows at some point, wink wink @richardschneider :))


[BUG] - Can't build standalone cardano-node with Nix

External
Area
Other:   Documentation / Manual build.
Summary
New build instructions for Nix are here https://github.com/input-output-hk/cardano-node/blob/master/doc/getting-started/building-the-node-using-nix.md and only allow to build pre-packaged versions of the node with default options filled in. Following these build instructions, it seems that I can't get a standalone cardano-node binary to which I can provide my own options (for example, another database location).
I use to simply be able to do:
$ nix-build -A haskellPackages.cardano-node.components.exes

but haskellPackages is no longer in scope of the default.nix and at this point, I don't know where to look.
Steps to reproduce
Try running the nix build instructions. You end up with a single pre-packaged binary:
testnet-node-local
└── bin
    └── cardano-node-testnet

which accepts no options or commands and is pre-configured for testnet.
Expected behavior

I can only build once, and get a cardano-node executable working for mainnet, testnet and actually custom private clusters.
The manual build spits back a statically linked executable that I can run with custom options, as before.

System info (please complete the following information):

OS Name: N/A
OS Version [e.g. 20.04]: N/A
Node version (output of cardano-node --version): can't run that command anymore.
CLI version  (output of cardano-cli --version): N/A

Currently building out of 1.35.0-rc1.

nix build .#cardano-node

@KtorZ, doesn't https://github.com/input-output-hk/cardano-node/blob/master/doc/getting-started/building-the-node-using-nix.md cover this?
This link is mentioned in the top-level CONTRIBUTING.rst.

@KtorZ, can you suggest a change to https://github.com/input-output-hk/cardano-node/blob/master/doc/getting-started/building-the-node-using-nix.md that would express the purpose you find unfulfilled?
Asking you to do it, because only you know the proper formulation for the question that's unanswered there.

I thought my question was pretty clear already, at least @disassembler answered it.
I was interested in building a standalone executable for the node, not a bundle tied with a configuration (.#mainnet/node) as the documentation highlight.
So the ask here is to simply document the magic incantation that Sam provided above.


Bug: Results cannot be displayed (exam ID 301)

When I want to see the results of my exam (id = 301), I see the loader but no results displayed.
Before opening this issue, I tried to check the following things:

"contrainte globale pour accéder à la correction" ==> True
Each copy has been correctly assigned to students
I waited more than 5 min to see if it was a time-consuming process
Get my grades from the export buttons at the root of the module "Export grades [...]" ==> same error

When I open the dev console, I get the errors in the image below:

It's a 500 error, providing from the GET on URL : https://api.gradescope.barais.fr/api/showResult/301
JSON Response : {"details":"java.lang.NullPointerExceptionError id 2f9913a4-83b6-4d01-a5ed-23b447f9dbd9-30","stack":""}
Thanks in advance for fixing :slightly_smiling_face:

Thanks ! It's working fine now !
Quentin


ONNX to NCNN conversion (.param look litttle different)

Hi,
I have converted my .param and .bin but does not look like yours. Can you tell me is there any further steps needs to be considered before NCNN conversion? Because ONNX inference is working fine.
I attach below my .param file in .txt format. Can you please check it if you have time it would be much appreciated. Thank you in advance
bestv5.txt

after removing layers and optimizing param bin, now my .param file looks almost similar like you except last line in yours (which is actually the output). I have 180 layers and you have 181 layers.
This one is missing in mine
Reshape                  Reshape_402              1 1 345 seg 0=-1 1=32
I also attached my optimized new param file in .txt format.
If possible then please look into it if I have done any mistake. Thank you in advance.
bestv5-opt.txt

There are still differences in parameters (64 vs 32, for example).
However the topology is identical, so I would give it a try.
After putting the last line in the param file, of course.

Thank you for your response. Thank you for trying out. You an also share your steps for conversion with version of ONNX, NCNN etc. It might help me to follow steps. In case, versioning is the isssue.


[SCB-706]change filters to discovery filters and support invocation based filters

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.09%) to 87.039% when pulling f6a460c7ba872c9b31a76957bf557337ada46b60 on liubao68:test-11 into b00f4c748122460ba1484815ed9c98eadf9eba31 on apache:master.


 It's hard to say why that's happening or what's doing that. Maybe they are consuming too much memory or too many CPU resources.
You could try adjusting the values of [query_server_config] os_process_limit = 100 and [query_server_config] os_process_soft_limit = 100 to some other value, higher or lower and see if would make a difference.  See the config reference: https://docs.couchdb.org/en/stable/config/query-servers.html#query_server_config for more details.
Alternatively, try adding more CPU or memory resources to your container/server.


Encode elements of query parameter array instead of the entire array string

Resolves https://github.com/Azure/autorest.nodejs/issues/61.
Resolves https://github.com/Azure/azure-sdk-for-node/issues/3445.

This change actually breaks a lot of existing functionality. I think it might be wiser for the service to properly decode query parameters instead of changing our generators.


Deaths in hp

The no of deaths in hp is 1 and the no of recovered is 2
And active cases are 25
3 jamatis from una
12 others una
1 from kangra
3 Solan
4 chamba
Do check and update

@ridiis please use this form to report cases
https://docs.google.com/forms/d/1HVXi3-0ckxGTS81yAN1RmgrVnvg9cg2pyPTuPgBeVEo


Use skip=["importlib._bootstrap"] by default

Codecov Report

Merging #167 into master will increase coverage by 0.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #167      +/-   ##
==========================================
+ Coverage   24.22%   24.35%   +0.13%
==========================================
  Files           2        2
  Lines        1701     1704       +3
  Branches      156      156
==========================================
+ Hits          412      415       +3
  Misses       1275     1275
  Partials       14       14

Impacted Files
Coverage Δ

pdb.py
27.09% <100%> (+0.27%)
:arrow_up:

Continue to review full report at Codecov.

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

More likely to trigger https://bugs.python.org/issue36130, but backported in https://github.com/antocuni/pdb/commit/be085308b9cc532766d7b3f9cbd39f9a78c5205f.


Generate API docs

Needs:

[ ] API docs generated from ipfs-pinning-service.yaml

[ ] in master
[ ] PRs

[ ] Link to generated API docs added to README

Also an entry point from docs.ipfs.io 😊

Is there a preferred doc generator? Happy to tackle this.

@GregTheGreek afaik there is no preference, the initial draft uses Swagger YAML format, at this stage anything that produces human-readable docs will do. Do you think you could also tackle #3?

@GregTheGreek turns out https://mrin9.github.io/RapiDoc/ was super easy to set up as a quick way to get docs for master branch:

https://ipfs.github.io/pinning-services-api-spec/

If you want to add something more advanced to add preview to PRs, PR welcome, but I think its good enough.


phase_func(): failed to handle RPC_EXTRA_INFO: unsupported info type: 2,

Issue description
Environment

your apisix-java-plugin-runner version 2.10.3
when  i try to open  requiredBody , I have  error  about :" phase_func(): failed to handle RPC_EXTRA_INFO: unsupported info type: 2, "
how to solvel  this problem

Hi, Please provide specific steps to reproduce


PTH false positive with Django FieldFile

Example of false positive for PTH110 and PTH116:
import os
from django.db import models
from django.test import TestCase

class Document(models.Model):
    file = models.FileField()

class MyTest(TestCase):
    def test_foo(self):
        file_path = Document.objects.last().file.path
        self.assertTrue(os.path.exists(file_path))
        self.assertEqual(os.stat(file_path).st_mode & 0o777, 0o660)

Output :
test.py:13:25: PTH110 `os.path.exists()` should be replaced by `Path.exists()`
test.py:14:26: PTH116 `os.stat()` should be replaced by `Path.stat()`, `Path.owner()`, or `Path.group()

Document.objects.last().file.path is str.
Tested on ruff 0.0.272.
Django code : https://github.com/django/django/blob/4.2/django/db/models/fields/files.py#L60
Note: sample code can not be launched, I can provide a full working example with Django if you really need.

I think the diagnostics are correct. What it's suggesting is the following:
file_path = "foo/bar.py"

os.path.exists(file_path)

# Instead use
Path(file_path).exists()

Do you think it could be useful to include the variable name in the message like so:
test.py:13:25: PTH110 `os.path.exists(file_path)` should be replaced by `Path(file_path).exists()`
test.py:14:26: PTH116 `os.stat(file_path)` should be replaced by `Path(file_path).stat()`, `Path(file_path).owner()`, or `Path(file_path).group()

No problem at all :)