Validation feature

Would be nice to have the ability to block users from getting past a given page based on some sort of policy:
public interface PageContinuePolicy{
    boolean canGoToPage(int oldPosition, int newPosition);
}

That way we could also check for permissions and such. You could also disallow users to go back.

@HeinrichReimer Sure, there's a need of such policy. Hoping to see it soon. Thank you.

Hi.
Please apply my pull request.
I added possibility which allow to lock and unlock next/previous (and swipe left/right) navigation.
Instructions:
1. Create FragmentSlide with build option "allowNext(boolean value)" or "allowPrevious(boolean value)". Warning!!! - Your fragment should be extended from SlideFragment. E.g.:
slides.add(new FragmentSlide.Builder()
                    .background(R.color.color_custom_fragment_1)
                    .backgroundDark(R.color.color_dark_custom_fragment_1)
                    .fragment(LoginFragment.newInstance())
                    **.allowNext(false)**
                    .build());

2.  Set NavigationInterface in MaterialIntroActivity by calling
setNavigationInterface(NavigationInterface navigationInterface). E.g.:
setNavigationInterface(new NavigationInterface() {
           @Override
           public boolean onNextClick(int position) {
               return slides.get(position).isAllowSlideNext();
           }

           @Override
           public boolean onPreviousClick(int position) {
               return slides.get(position).isAllowSlidePrevious();
           }

           @Override
           public void onImpossibleToNavigate(int position, int direction) {
               Toast.makeText(getApplicationContext(), R.string.toast_impossible_to_navigate, Toast.LENGTH_LONG).show();
           }
       });

3. For lock or unlock slide page you need to call allowNextSlide() or allowPreviousSlide() from your fragment (e.g.: you may call this methods after successfull user autorization). Also you may call showNextSlide() and showPreviousSlide() for imidiately go to next or previous slide.
You can see the sample code in demo files.

Fixed by #24


[test-failed]: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/embeddable/dashboard·js - maps app  embeddable embed in dashboard should populate inspector with requests for map embeddable

Version: 7.3
Class: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/embeddable/dashboard·js
Stack Trace:
    Error: expected '' to equal 'geo_shapes*,meta_for_geo_shapes*.shape_name'
at Assertion.assert (/private/var/lib/jenkins/workspace/elastic+estf-kibana+7.3-snapshot+multijob-x-pack-darwin/kibana/packages/kbn-expect/expect.js:100:11)
at Assertion.be.Assertion.equal (/private/var/lib/jenkins/workspace/elastic+estf-kibana+7.3-snapshot+multijob-x-pack-darwin/kibana/packages/kbn-expect/expect.js:221:8)
at Context.equal (test/functional/apps/maps/embeddable/dashboard.js:50:42)
at process._tickCallback (internal/process/next_tick.js:68:7)

Build Num: 27

Version: 7.3
Class: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/embeddable/dashboard·js
Stack Trace:
    Error: expected '' to equal 'geo_shapes*,meta_for_geo_shapes*.shape_name'
at Assertion.assert (/private/var/lib/jenkins/workspace/elastic+estf-kibana+7.3-snapshot+multijob-x-pack-darwin/kibana/packages/kbn-expect/expect.js:100:11)
at Assertion.be.Assertion.equal (/private/var/lib/jenkins/workspace/elastic+estf-kibana+7.3-snapshot+multijob-x-pack-darwin/kibana/packages/kbn-expect/expect.js:221:8)
at Context.equal (test/functional/apps/maps/embeddable/dashboard.js:50:42)
at process._tickCallback (internal/process/next_tick.js:68:7)

Platform: darwin
Build Num: 27


Ink Badge being cut off

I can't for the life of me figure out why my badges when they get to a certain number start to wrap but are cut off
So for example look at the Visual Studio tag in the Editors section

added className="column-group" to surrounding div


Remove "interface imports" from binary syntax, expand accepted strings

This PR is the spiritual successor of https://github.com/bytecodealliance/wasm-tools/pull/1146 and is an implementation of these PRs together for this repository:

https://github.com/WebAssembly/component-model/pull/222
https://github.com/WebAssembly/component-model/pull/259
https://github.com/WebAssembly/component-model/pull/263

This is technically a breaking change to the binary format, but the breaking change is so minor that a gradual rollout is implemented here. Previously import/export names had a discriminator byte of 0x00 or 0x01 depending on if they were a "plain name" or an "interface name". They no longer have a discriminator byte and instead always use 0x00. This means that old binaries are easily read by discarding the 0x00 or 0x01 byte. New binaries are, for now, temporarily created with the 0x01 byte still to ensure that binaries produced with this tooling is still compatible with older tooling. Once this tooling has permeated enough I plan to change the default emission to be 0x00 instead of 0x01.
The text syntax was changed in this PR as well. Previously where (interface "a:b/c") was printed only "a:b/c" is printed now. Like the binary format the text format still parses the old form with the intention of being deleted eventually.
Finally this PR additionally expands the set of accepted syntax within import and export strings. This now includes imports of implementations (locked/unlocked deps), imports of URLs (relative and not), and integrity-based imports.

TODO items:

[ ] Validate that exports can't use urls/implementations/etc, basically only imports get the new syntax
[ ] Parsing integrity-metadata currently does nothing but is defined by w3c. Should figure out what to do in the component model

Ok I've updated with parsing of what I believe is the format of integrity-metadata so this is good to go I think


Add support for serving profile banner and avatar

Description
Add an endpoint to serve pictures as static files. The endpoint should have following specifications:
Acceptance Criteria

URL:  profiles/photos
Parameters

profileID: string, required
type: string An option of banner and avatar, required.

Response

200: File return, if the entity exists
404: If the entity does not exist
500: Internal error

We decided to take a different approach and this ticket is no longer valid.


Enable wildcard with prefix.

Use case:
We use the Aurora scheduler in Mesos which assign tasks names using a
jobkey which consists of: "role/environment/jobname".  We often end up
in a scenario where we want all jobs running under a given "role" or
"role/environment" combination to have access to a Vault role.  Under
the current implementation this would require us to iterate all of the
possible combination and install policy files.
Previous versions of Vault gatekeeper allowed us to do wildcards with
prefixes as they used a simple glob match.  Moving to the radix tree
implementation broke this behaviour.
This patch changes the matching behaviour slightly.  Whenever we detect
a wildcard match we flag the policy as such.
When performing policy matching for wildcards we do a prefix search,
rather than looking for the last character being ":". Policy matching
for non wildcard policies is unchanged.
No changes to the radix tree structure are required.

Thanks


Update community.tsx

Padding adjustments: Added padding to the section for better spacing on smaller screens.
Title: Changed the title to "Join Our Community" for a warmer, more welcoming message.
Subtitle: Increased the text size for a more prominent and balanced appearance.
Grid layout: Improved the responsiveness and added spacing between grid items.
Gaps and spacing: Adjusted gaps for better spacing between sections and elements.
Alignment: Kept everything centered for a clean, cohesive look.

Closes #
📝 Description

⛳ Current behavior (updates)

🚀 New behavior

💣 Is this a breaking change (Yes/No):

📝 Additional Information

Summary by CodeRabbit

New Features

Updated the title of the community section to "Join Our Community."
Enhanced the layout of the community section for better responsiveness across devices.

Bug Fixes

Adjusted spacing for improved visual presentation between elements.

prefer the existing one.


Often getting ConnectionFailureException

Hi,
I am often getting ConnectionFailureException with this lib and miniflux, however I am not sure which one is to blame. Most of the time, I can just reload the page and it works.
Fatal error: Uncaught JsonRPC\ConnectionFailureException: Unable to establish a connection in /srv/http/miniflux_api/vendor/fguillot/json-rpc/src/JsonRPC/Client.php:319 Stack trace: #0 /srv/http/miniflux_api/vendor/fguillot/json-rpc/src/JsonRPC/Client.php(201): JsonRPC\Client->doRequest(Array) #1 /srv/http/miniflux_api/index.php(36): JsonRPC\Client->execute('feed.update', Array) #2 {main} thrown in /srv/http/miniflux_api/vendor/fguillot/json-rpc/src/JsonRPC/Client.php on line 319

It is coming from this line of my (very simple) script based on examples in Miniflux doc, but I cannot find what is going wrong with either Miniflux or this lib.
Thanks

Maybe it's coming from your web server, too busy or too slow to handle too many connections? I don't know, it's hard to say.

I am making requests on a Miniflux instance. Both Miniflux and my script using JSONRPC runs on the same computer (which is actually my laptop). So there should not be communication problems between the two of them, since it's basically localhost.
I use the standard Nginx + PHP-FPM setup, and I did not find any evidence of the webserver being too slow in the logs.

Ok, found a bit more about it, and I would tend to think this is due to Miniflux being synchronous in the update call, and then getting a timeout if a feed is not reachable.

The default timeout is now 5 seconds in the client, if the processing is too slow, you will have an exception.


Fusion Core bugging after breaking at least one electromagnet

When I tried placing cooler to test cooling with gelid cryotheum, I accidentally broke 1 electromagnet and all the pink fluid got out of the fusion reactor, when I put back the electromagnet, the reactor core started heating up back to 8k kK and when it got there (with power provided the whole time and electromagnets powered), it was just going between 7990 kK and 8010 kK without the reactor starting up (I may add that it had everything it needed to start up). If I save and quit and load the world back up, it starts working (note: If there is no fuel in it after loading the world back up then you need to put fuel in it and save and quit and load back up again)
I am playing enigmatica 2 expert mode with the mod version 2.16f-1.12.2

I can only reproduce aboves bug by inserting power into the reactor core before the structure is complete, the setup is simple:
I doubt toroid size matters but for this i used toroid size 3:
I doubt that fuel matters but i am using deuterium/tritium.
Place the structure, but destroy an electromagnet, heat up the core by your favorite infinite power source (using RFtools creative powercell).
Have it at ignition temperature, add the destroyed electromagnet back and see how the temperature goes above ignition temp and goes down again. Never actually igniting.
I tested this with plasma from a previously succesful ignition (through normal means) and without, both will fail.

I suppose a good way to prevent this from happening is to check wether the structure is verified, if not it should not accept any power. At the end, it already does turn off when the structure is destroyed, so the idea would be to use that trigger to go through this power accepting process too (Is structure verified? if true -> acceptPower = true)

Thanks for the details! I knew there was some bug like this, but wasn’t exactly sure what was causing it :P

@Dubl33 @derdotte Turns out I'm not actually able to recreate either of these issues. Are you both using 2.16f, or are you perhaps using the latest version derdotte?

@turbodiesel4598 Currently using NuclearCraft-2.16f-1.12.2.jar its part of the enigmatica 2 expert skyblock modpack. There i was also able to reproduce this multiple times succesfully.

Could you try updating to the latest version of the mod and see if it happens then?

Doing so right now, gonna update in a few mins.

@turbodiesel4598 yep, the newest version fixes this issue.
I used the same method as above multiple times and even checked wether it would reignite even if you broke the structure multiple times. I also checked wether if you were to drop below 8kk Kelvin it would reignite after giving it energy prior to fixing the structure, which also worked.
I read the changelog during startup and i cant really see what you fixed between 2.16f and 2.17a.
It still regularly occurs on 2.16f using aboves method though.
For testing i simply exchanged nuclearcraft versions on a duplicated profile of enigmatica 2 expert skyblock.

I'm not sure what fixed it either, but at least it is! I'll close this issue then, as it's fixed as of the latest build ;)


Proposal Update

Created the proposal. @NatsuD99 @tanmay8103 Please update the Schedule for the project and also feel free to make any changes.

Added the schedule. Cross check once and it should be done.

Proposal Completed


Update measure.service.js

Summary
This is a companion update to a change in node server core (here)
New behavior
const id = args.id || req.params.id; was changed to always use args.id since it shouldn't be undefined once the change to node server core is merged and used
Code changes
measure.service.js - made a minor change to always use args.id
Testing guidance
Made the same change referenced here: link to prin the asymetrik version of the server and sent a measure request, noted the server didn't crash or behave oddly after the request was sent. (also double checked against the unit tests to be sure that nothing was broken there

Per discussion, closing this as we encountered scope creep for updating the whole server to use @projecttacoma/node-fhir-server-core.
We will have a new task/PR for updating the whole repo to our package, and in that PR we will include this code as part of the sweeping changes.


Stopping training

Hello everyone, i am a newbie yolo user, i am training my own model in order to detect fishes, i used around 4k labelled images as a database, now i am training yolo, my question might be dumb but i don’t want to ruin the work that i have done si apologies for my following question:
When i decide to stop training i just press control+C on cmd to stop ? Will the training done be saved ?

training saves weights every 1k iteration i think.  hey, wanna share those labelled images :D


Danger doesn't have access to the PR from circle

In #450 we missed the CHANGELOG changes, that usually caught by Danger, but the CI was green. After checking the logs I found:
All green. Nice work.

Danger does not have write access to the PR to set a PR status.

So probably something has changed, so Danger lost access to the PRs.

something else had to happen on that PR, that message is expected since we didn't add bot as the user of the repo per http://danger.systems/guides/faq.html#danger-is-not-posting-to-github-prs-but-everything-looks-fine
I refreshed the api token anyway, you can see that danger commented on #461
Lets keep an eye on it for next pr in case its still funky


Fix README changes not appearing on documentation at https://solace.js.org

Currently in https://github.com/solacejs/solace.js/blob/main/website/src/app/page.tsx I just fetch the README from the repo so it can just refer to the README and have it show up on the vercel deployed website. However, it seems like it is only using an older version of the README. Not sure why, I am fetching from https://raw.githubusercontent.com/solacejs/solace.js/main/README.md  which should show all of the current README I think. It seems to have the same issues when the website is locally hosted as well. The website uses next.js if anyone is wondering. I do wonder if it could be some sort of overflow error as well, but probably not.

Hi. I would like to work on this. Can you please assign this to me?

It looks like someone may have already fixed the issue though, I'll have to take a look at it later

Seems like the issues is still occurring for some reason

The issue happens because GitHub has a 5 minute cache policy when new changes are pushed to the repository.
Either add a delay of 5 minutes in your build process, or find a way to import the readme file directly instead of accessing it via a URL.

Okay thank you, I'll look into adding a 5 minute delay into the build as well if I can

No need to add the delay in the build process now. I found a way to bypass caching.

I noticed that just now. Learning new things about GitHub everyday, you can add a query string for token to fix the issue, thanks!


Add newlines to autotag prompts to make them readable

This is simply a usability aid; before this, all autotag prompts are piled atop one another without any spacing in between.

Ack; thanks for catching this bug I recently inserted. I committed a slightly different fix.


Setting pillar_root to /usr/share/ceph-salt/pillar breaks ceph-salt

/etc/salt/master has the following contents
    master: ++ cat /etc/salt/master
    master: user: salt
    master: syndic_user: salt
    master: log_level: info
    master: pillar_roots:
    master:   base:
    master:     - /usr/share/ceph-salt/pillar

ceph-salt is installed from RPM, version is:
master:~ # ceph-salt --version
ceph-salt 15.2.12+1601288307.gf6c5fd7

The directory exists and within it ceph-salt.sls:
master:~ # rpm -ql ceph-salt-formula | head
/usr/share/ceph-salt
/usr/share/ceph-salt/pillar
/usr/share/ceph-salt/pillar.conf.example
/usr/share/ceph-salt/pillar/ceph-salt.sls
/usr/share/ceph-salt/pillar/top.sls

The contents of /usr/share/ceph-salt/pillar/ceph-salt.sls are from ceph-salt.spec:
master:~ # cat /usr/share/ceph-salt/pillar/ceph-salt.sls
ceph-salt:

Invocation of ceph-salt config fails like this:
master:~ # ceph-salt config
Traceback (most recent call last):
  File "/usr/bin/ceph-salt", line 11, in <module>
    load_entry_point('ceph-salt==15.2.12+1601288307.gf6c5fd7', 'console_scripts', 'ceph-salt')()
  File "/usr/lib/python3.6/site-packages/ceph_salt/__init__.py", line 23, in ceph_salt_main
    cli(prog_name='ceph-salt')
  File "/usr/lib/python3.6/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3.6/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3.6/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3.6/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/ceph_salt/__init__.py", line 58, in config_shell
    if not run_config_shell():
  File "/usr/lib/python3.6/site-packages/ceph_salt/config_shell.py", line 1268, in run_config_shell
    generate_config_shell_tree(shell)
  File "/usr/lib/python3.6/site-packages/ceph_salt/config_shell.py", line 1189, in generate_config_shell_tree
    _generate_group_node(group_name, group_dict, root_node)
  File "/usr/lib/python3.6/site-packages/ceph_salt/config_shell.py", line 1183, in _generate_group_node
    _generate_option_node(option_name, option_dict, group_node)
  File "/usr/lib/python3.6/site-packages/ceph_salt/config_shell.py", line 1144, in _generate_option_node
    _generate_group_node(option_name, option_dict, parent)
  File "/usr/lib/python3.6/site-packages/ceph_salt/config_shell.py", line 1179, in _generate_group_node
    if handler and handler.default() is not None and handler.value()[0] is None:
  File "/usr/lib/python3.6/site-packages/ceph_salt/config_shell.py", line 276, in value
    val, _ = super().value()
  File "/usr/lib/python3.6/site-packages/ceph_salt/config_shell.py", line 71, in value
    return PillarManager.get(self.pillar_path), None
  File "/usr/lib/python3.6/site-packages/ceph_salt/salt_utils.py", line 285, in get
    res = cls._get_dict_value(cls.pillar_data, key)
  File "/usr/lib/python3.6/site-packages/ceph_salt/salt_utils.py", line 204, in _get_dict_value
    if path[0] in _dict:
TypeError: argument of type 'NoneType' is not iterable

Ah, invalid. The correct way to set it is:
pillar_roots:
  base:
    - /usr/share/ceph-salt


Update tutorial.md , delete the extra words in line 482.

delete the extra words in line482
What type of PR is this?
docs: Documentation only changes.
Check the PR title.
delete the extra words so that we readers can understand it better.
(Optional) Translate the PR title into Chinese.
删除了第482行多余的字
(Optional) More detailed description for this PR(en: English/zh: Chinese).
the extra word is in line 482
(Optional) Which issue(s) this PR fixes:

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

Thanks, please sign CLA mentioned above.


Allowed page option for users and posts browse

closes #10029
The page query param was not forwarding to the query, meaning that when
the admin client requested the next page of users or posts, it would
recieve the first page again.

I think we should add a routing test to check pages/users can fetch multiple pages. Otherwise LGTM 😄

Would it make sense to add page option to tags as well? Don't know of the place where it would be used, but probably makes sense just for consistency sake :thinking:

I think we should add a routing test to check pages/users can fetch multiple pages

Regression tests would definitely be useful I think if they're quick to add.

Would it make sense to add page option to tags as well?

Yes, tags are a paginated resource too, as are invites but that one appears to already have the page param allowed.

@kevinansfield cool :) so just need to take care of page option in tags and this PR is ready to go :tada:


Initial setup

What was wrong?
Issue #
How was it fixed?
Summary of approach.
Cute Animal Picture

merging since this is the very basic setup


[Bug]

After installing BDA and restart Discord, it refuses to load.
Yesterday I just installed BDA on my clean installation of Discord, and it worked fine, I installed some plugins and themes [Screenshots], but today when I tried to load it again, it just refuses to load.

Discord Stable, last version.
I'm going to download again the installer and trying to repair BDA, if it don't work I'm just going to reinstall.

Update:
Repairing don't work, and unistalling just made Discord stay like this:

Trying to restart again...

https://cdn.discordapp.com/attachments/119918741516451840/814871571498795058/config.json

Trying...
¡Thanks dude!
If it works i'm going to close the issue

https://cdn.discordapp.com/attachments/119918741516451840/814871571498795058/config.json
Note that this will be fixed upon the release of the development branch being merged.

¡Looks like it works!
Thanks a lot, really
Closing issue...

Issue closed


Add semantic release badge

:tada: This PR is included in version 0.8.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Requests

Changed get() in BookFactory and made changes in a few other files to accompany it.

Realized I needed to merge some stuff first since requests is pretty far behind dev


Stephen/v1 jobspec deprecation

@spooktheducks
This is a new PR with the 12 commits from https://github.com/smartcontractkit/documentation/pull/229 squashed and then all of my changes as a commit on top of it. I think this is ready to go. Take a look. If there aren't any objections or discussions, then I'll squash my commit into Sam's and we can get this merged ASAP.

@PatrickAlphaC can I can an approval from you? I believe @spooktheducks has already verbally approved this.

These are beautiful.
I'd just add that we've removed the "initiator" concept in favor of just "job type".


Implement the Server Protocol

This implements a new improved version of the server protocol. The following changes have been made:

The protocol is based on JSON messages. This allows for example for more structured commands where it's easier to multiple arguments for a command and even have optional arguments.
For each command, there is a corresponding response. It is either a success response with possibly the value that you requested, or an error response with an error code.
On top of the responses you also get sent event messages that indicate changes to the timer. These can either be changes triggered via a command that you sent or by changes that happened through other sources, such as the user directly interacting with the timer or an auto splitter.

The protocol is still work in progress and we will evolve it into a protocol that fully allows synchronizing timers over the network. #260
The event sink has now been renamed to command sink, because there is now a clear distinction between incoming commands and events that are the results of these commands.

Oh and because we now have specific error conditions for all the commands (split, undo_split, ...), there's a test for every possible error on every command. I think that should really help with robustness.


cannot import name 'Screener' from 'tradingview_screener'

I'm trying to run my python script, even on Replit i get everytime
"Traceback (most recent call last):
File "C:\xxx\tradinview\index.py", line 1, in
from tradingview_screener import Screener
ImportError: cannot import name 'Screener' from 'tradingview_screener'"

It's
from tradingview_screener import Scanner


Beacon

This is another suggestion for a beacon API. It replaces most fields with three key-value maps.

Suggest have the values in key-value maps as arrays of strings.
This removes the need to come up with magic syntax that then has
to be parsed for both complex values and multi-valued
attributes.
Maximilian Haeussler<EMAIL_ADDRESS>writes:

This is another suggestion for a beacon API. It replaces most fields with three
key-value maps.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
You can view, comment on, or merge this pull request online at:
https://github.com/ga4gh/schemas/pull/540
Commit Summary
• Fixed the type of beacon's queries field.
• Changing the type of exists to boolean.
• Initialized beacon's frequency field to null as it's optional.
• reverting removal of beacon.avdl
• Merge pull request #375 from mcupak/beacon
• Changing the type of exists to boolean.
• Merge branch 'response_fix' of github.com:mcupak/schemas into response_fix
• Fixed the type of beacon's queries field.
• Merge branch 'queries_type' of github.com:mcupak/schemas into queries_type
• Initialized beacon's frequency field to null as it's optional.
• Merge branch 'initialize_fields' of github.com:mcupak/schemas into
initialize_fields
• Merge pull request #388 from mcupak/initialize_fields
• Merge pull request #386 from mcupak/queries_type
• Merge pull request #384 from mcupak/response_fix
• another suggestion for a beacon API
• removing accidentally comitted file
File Changes
• A src/main/resources/avro/beacon.avdl (109)
Patch Links:
• https://github.com/ga4gh/schemas/pull/540.patch
• https://github.com/ga4gh/schemas/pull/540.diff
—
Reply to this email directly or view it on GitHub.*

@maximilianh @mcupak Can we remove this in favour of current Beacon development?

I don't think I have the permissions needed to close this, but whoever does, please do so. This is out of date.

Closed in favour of current Beacon development efforts.


Extend containerrun helper with UDS command channel

Description
Containerrun is modified to listen on a container local UDS for commands to stop/start the processes it controls. Enables temporary suspensions for (human) operator work without making it visible to higher kube layers
Motivation and Context

https://jira.suse.com/browse/CAP-1305

How Has This Been Tested?
Additional unit tests.
Types of changes

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

Checklist:

[x] My code has security implications.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Certainly. And apologies for not thinking of the docs at all from the beginning.

@f0rmiga Pushed reworked containerrun helper and changes to factory. Passes vet, lint, unit tests. Cluster starts ok with the modified operator.
(Today was pretty all just fixing the issues in the redo which prevented that).
Still has issues when actually used.
While it reacts to STOP commands it kills the targeted container somehow, still.
I tried this using the nats pod.
Self-killed nats-nats once,
and killed the loggregator-agent-loggregator-agent from the nats-nats container through the visible socket on second attempt.
Find it weird that the nc ... command is not exiting after sending the packet.
I currently have no log data telling me what is going on.
Might be looking in the wrong place (kube container logs).

Wrt side note: It seems by default nc will listen for a response, even for datagrams. As the helper does not send any nc waits forever. Solution is -w 1 to set a single-second timeout.
Using stern does not really help ... Looking just at the nats pod the operation generates no logs at all in all of the containers. ... And looking at the entire system swamps whatever signal there might be in noise from everything else.
It seems that adding log output to containerrun itself might be the best bet for investigating this.
Right now the only idea I have is that containerrun sends the kill signal not just to its children, but to itself as well. Oh! That or the children going away is treated as some kind of error (it should not react to sigchld and such, there is code to prevent that).

@f0rmiga @viovanov
With the logging it became clear that my assumption on what Wait would return, and how to handle the datagram listener were wrong.
So, this looks to be working as intended now, STOP and START cause containerun to kill and restart the job processes.
We are still fighting the system however.
Stop the blobstore, for example. Then wait for kube to realize that the job is not properly responding, through its probes (live, readiness, whichever), and see it restarting the job container. Very unwanted.
To the system our removal of the job process is nothing more than a problem in the component it has to solve, and then does, by creating a working component from scratch.

I am beginning to think that we are on the wrong path here.
As it is EOD I will defer discussion of other possible paths for migration to tomorrow.
That said, I currently have no proper ideas on how to work with the system, instead of against it.
Except in general to look at the parts where we have to restore something and then see if the running component can be convinced to perform the restoration for us in some way.
The old instructions do that in part by going through mysql and mysqld for the CCDB. In part only because it still assumes that the CC and anything else talking to the database will be (made to be) quiet while the new database gets uploaded.


Fix bug in HTTP-Anatomy module

Fix error in the README.md inside of the HTTP-Anatomy module. Syntax error was throwing off the getTitleFromHTML function.

actually I merged this and am going to make another ticket


Docker packaging

Hi,
The Docker can provide OS abstraction allowing to get rid of OS-specific package managers.
There are a couple of projects that create images from pgBadger tgz but they are outdated.
Bringing docker-packaging to the main repo will keep the tool in a form of Docker image up-to-date and available for a broader audience.
Example of a file taken from https://github.com/uphold/docker-pgbadger/blob/master/Dockerfile:
FROM alpine:latest

LABEL maintainer="Rui Marinho<EMAIL_ADDRESS>(@ruimarinho)"

ENV PGBADGER_DATA=/data
ENV PGBADGER_VERSION=11.1
ENV PGBADGER_PREFIX=/opt/pgbadger-${PGBADGER_VERSION}
ENV PATH=${PGBADGER_PREFIX}:$PATH

RUN apk --no-cache add coreutils \
    openssl \
    perl \
  && mkdir -p /data /opt \
  && wget -O - https://github.com/darold/pgbadger/archive/v${PGBADGER_VERSION}.tar.gz | tar -zxvf - -C /opt \
  && chmod +x ${PGBADGER_PREFIX}/pgbadger

COPY docker-entrypoint.sh /entrypoint.sh

VOLUME $PGBADGER_DATA

ENTRYPOINT ["/entrypoint.sh"]

CMD ["pgbadger"]

WDYT?

Missed related pull request - https://github.com/darold/pgbadger/pull/543, closing as duplicate.


Add ability to support more browsers (remove check if key exists in defaults)

Removed check if key exists in defaults as I would like the ability to add more browsers than whats supported in the defaults list.

+1, would like to do that as well, specifically for Baidu and Samsung Internet.
Looking at Samsung Internet though, it's useragent contains a Chrome version too, so potentially that falls back to the Chrome setting, need to test how the useragent is handled.

https://github.com/faisalman/ua-parser-js in the readme seems to say that .name will return "Samsung browser" so would be good if we can get this change in as it'll allow us to give our own values for our browsers. Then I might feel more safe turning on the banner for unknown browsers too.

bump

@mikemaccana you not rebuild dist after this changes


Highlight course when id targeted in url

Creates a highlight when linking to a specific course so the user knows what exactly is being linked to.

Hold on I need to fix a bug first


You should be able to use diamonds as chance shapes

(you can currently only do it with rectangles)

Not sure what it should actually do though?


Unable to get the ".srv " file of the ble device

Hello, i am running ws-slave on pi 3 and the other end on Laptop(Kali).
i am able to get the ".adv file" and not the ".srv" file. I have run the "gatttool" and i'm able to see the primary sevices and the characteristics of the BLE device but didn't have the luck to find the "services" on the "ws-slave"(pi 3).Could you shed some information on the same?.

Hi,
have you tried scanning the services without reading the characteristics values (scan -r option)?
In some cases - e.g. when device requires BLE link-layer auth (=encryption) to read specific characteristic value, the scan may "stall" at this point. Scanning without reading values should not trigger the auth - the services+characteristics are generally available without BLE bonding.

i tried it just now with the "-r "but still not working.

Can you also share logs of the ws-slave script? Hcidump of the interface ws-slave is working on would also be useful (hcidump -i hciX -X). You can compare hcidump of ws-slave vs gatttool on the same interface - you mentioned it worked.
BTW, the NOBLE_HCI_DEVICE_ID is for ws-slave. you don't need to set it for scan script - it just connects using websocket to the ws-slave. And you can configure it in config.env - in case you have multiple adapters on the same host. If you have only one adapter, you can leave default setting (commented).

How do i save the hcidump to a file?

Oops i will post the log file in a few mins.

Here's the dump of hci using"gatttool"
=NewgatttoolDump.zip

Here's the dump of hci using "ws-slave"
=ws-slavedump.zip

Hi,
based on your hcidumps, it looks like there is a problem with initial connection to the device.
In your gatttool dump, after "LE Create Connection" follows "LE Meta (LE Connection Complete)", and connection is established. On the contrary, in the ws-slave dump after the "create connection" command, controller does not return the "connection complete" to host.
There may be several reasons for that.
For starters, you can try to:

run ws-slave on a different laptop/host. So far I guess you ran ws-slave on localhost.You mentioned Raspberry - just set Raspberry IP as WS_SLAVE in config.env, and try again.
try to explore the services+characteristics using node.js noble example script. This will help us to pinpoint the problem, as GATTacker uses noble to connect to devices:
node_modules/noble/examples $ node peripheral-explorer.js <MAC>

Hello there, was facing the same error while trying to scan my smart watch for the services file, I'm running my ws-slave on my Laptop and the ws-master on the Raspberry Pi, it was possible for me to successfully perform a MiTM with a Bluetooth Bulb, not sure why it doens't work with the watch.

Hi,
have you tried scanning the services without reading the characteristics values (scan -r option), like mentioned in the comments above?
The watch may use secure link-layer Bluetooth pairing. You can confirm it in the Bluetooth settings of your phone - whether it is on the list of paired devices. In such case, some characteristics may require prior "authentication" (pairing) to access. That's why scanning - that by default reads the characteristics values - will not work. You should be able to scan only services + characteristics UUIDS without reading values (-r), but in case the connection is link-layer encrypted, you won't be able to MITM it anyway (GATTacker does not support it).

scan -r option didn't work :| And I think the watch is listed on the list of paired devices. Thanks for the help.


Moduli python da installare e import ridondante

Some Python modules (Pillow [formerly PIL] and xdg) require manual installation from PIP, you should include those into README.md
Some imports are redundant:
22 from PIL import Image, ImageDraw
23 from xdg.BaseDirectory import xdg_config_home
24 from contextlib import suppress
25 from PIL import Image, ImageFilter, ImageEnhance
Can be simplified with:
22 from xdg.BaseDirectory import xdg_config_home
23 from contextlib import suppress
24 from PIL import Image, ImageFilter, ImageEnhance, ImageDraw
Seems to work nicely. Great job.

Thanks!
I suggest you to create a pull request containing those changes on two separate commits to get contribution officially recognized :)
Are you willing to do that or shall I just write the commit myself? let me know!
PS: Also remember to use english on this repo as it's of worldwide potential interest.

Will make a pull request tomorrow.

Created pull-request. Closing


Clicking on typing svg opens github link

Clicking the dynamic text in "About" sections open up the repo of the library, is that really required? https://github.com/DenverCoder1/readme-typing-svg

@shubhammalhotra1708 fixed the issue. Thank you for your input.


update to add-react-to-a-new-app

the sequence of commands for install using npm is a bit confusing because it looks like (because of the blank line) the npm install and the create-react-app is one command with line wrapping. Adding a blank line makes it clear these are two commands.

closing this out since this has been moved to a different section now. Thanks


Please populate the "Releases" section.

Hello.
Can you please put the Kore releases here for better vibility? And in the Kodi site, please!
http://mirrors.kodi.tv/tools/kore/releases/
Kind regards.

It IS in the releases section...
As for the website, it has the link to Google Play, which is the preferred distribution platform.

I don't use Google Play services, but F-Droid.
On Mon, Jan 4, 2016 at 9:41 AM, Synced Synapse<EMAIL_ADDRESS>wrote:

It IS in the releases section...
As for the website, it has the link to Google Play, which is the preferred
distribution platform.
—
Reply to this email directly or view it on GitHub
https://github.com/xbmc/Kore/issues/172#issuecomment-168612103.

So, get it from F-Droid. It is there.

Yes, you are right.
Thanks again!
On Mon, Jan 4, 2016 at 9:44 AM, Synced Synapse<EMAIL_ADDRESS>wrote:

So, get it from F-Droid. It is there.
—
Reply to this email directly or view it on GitHub
https://github.com/xbmc/Kore/issues/172#issuecomment-168612921.


add support for synced_block.

fix the bug when querying children blocks for synced_block.

Can you elaborate on the bug you encountered?

When I use the original code, it can't get the child block of synced_block.
Because the child block can't be queried with the ID of the parent block, what I found when I debug with notion API, it should be queried with synced_block.synced_from.block_id.

So the content of the synced_block is not getting rendered right? If that is the case then, it works fine on my end:
This is the parent page with a synced block and the child page (Page-1) includes the same synced block.

output:

if this is not the issue then please provide steps to reproduce the bug.

It works fine for the referenced page (page A) but not for the slave page (page B) refers to page A.
For example, when you write something on page A, then copy and sync it to page B, the exported markdown files only work fine for page A, not page B.
You can find the reason in the response from notion API.

the UUID of the block is d87824d6-b706-4a1e-b060-878b0c2909b5, and it appeared as the block id for page A, but as synced_block.synced_from.block_id for page B. And the output of sycned_block for page B will be empty if you query its content without using synced_block.synced_from.block_id.

Thanks for explaining. That makes it clear. I'll merge it and it should be live in the upcoming update. Thank you for your contribution.


Compilation fails when cross compiling for windows

I'm working on a project that uses C++20 features and uses this library, I primarily develop under linux but like testing windows support from time to time. When trying to crosscompile for windows using x86_64-w64-mingw32, I get the following error (even when compiling the example):
error: ‘::aligned_alloc’ has not been declared; did you mean ‘pocketfft::detail::aligned_alloc’?
  156 |   void *ptr = ::aligned_alloc(align,(size+align-1)&(~(align-1)));

After looking into it, this seems to be due to the fact that windows doesn't support said function, despite it being part of the C++17 standard (as detailed here). So simply checking for __cplusplus >= 201703L isn't enough for guaranteeing the existence of said function.
I also tested manually forcing the use of the portable version of the function and both the example and my project worked flawlessly under windows.
I think the solution should be as simple as checking for either the mingw specific macro __MINGW32__ or for windows altogether with _WIN32.

Thanks for the report!

I think the solution should be as simple as checking for either the mingw specific macro MINGW32 or for windows altogether with _WIN32.

Hmm, checking for __MINGW32__ is probably too weak, since the problem will probably also occur when compiling with MSVC, correct?
On the other hand, I know that https://gitlab.mpcdf.mpg.de/mtr/ducc compiles fine with MSVC, even though I have the same macros in src/ducc0/infra/aligned_array.h. Strange...
Rather than adding more guesswork to the code, would it be an acceptable solution for you if I intopduced a macro called POCKETFFT_USE_PORTABLE_ALLOC that switches to the portable version unconditionally?

Hmm, checking for __MINGW32__ is probably too weak, since the problem will probably also occur when compiling with MSVC, correct?
On the other hand, I know that https://gitlab.mpcdf.mpg.de/mtr/ducc compiles fine with MSVC, even though I have the same macros in src/ducc0/infra/aligned_array.h. Strange...

Ah, that's because MSVC doesn't define the correct macros, at least according to this
so checking for MinGW should be enough

Rather than adding more guesswork to the code, would it be an acceptable solution for you if I introduced a macro called POCKETFFT_USE_PORTABLE_ALLOC that switches to the portable version unconditionally?

However, this is also acceptable and I could add the neccessary logic during the configure step

Ah, that's because MSVC doesn't define the correct macros, at least according to this
so checking for MinGW should be enough

Oh wow, thanks for pointing that out! (I never have direct contact with the compiler, I just see whether CI succeeds or fails, so I never made detailed experiments.)
In this case I think it's fine to try the MINGW version.
So we should replace
#if __cplusplus >= 201703L
with
#if (__cplusplus >= 201703L) && (!defined(__MINGW32__))
correct?


CupertinoAlertDialog allows empty actions

CupertinoAlertDialog should not allow a dialog with no actions to be created.
An attempt has been made to disallow this with an assert:
https://github.com/flutter/flutter/blob/7f134d860d05e9deb2b965962637bdab12db414c/packages/flutter/lib/src/cupertino/dialog.dart#L134
but the actions parameter is initialized to a blank list:
https://github.com/flutter/flutter/blob/7f134d860d05e9deb2b965962637bdab12db414c/packages/flutter/lib/src/cupertino/dialog.dart#L129
The result is a dialog that cannot be dismissed:

this could be fixed if not initialize the action or if list assert check is not empty?

@xster I would like to work on this issue....can I?

@hasnentai certainly, happy to take your pull request

@xster CupertinoAlertDialog() class does not contain any @required parameter and using default constructor leads to showing up the only backdrop as shown in the below image. Will be a good idea to add @required  for actions and content

?

@xster Native behavior of IOS is showing "OK" by Default if no action is null.
I guess it will be a good idea to implement the same

@xster I have made PR.
This is my first PR so I might not be up to date.
Please review the PR :)

I think this is intended? Here's a screenshot of what UIAlertController(title: "title", message: "message", preferredStyle: .alert) looks like:

\cc @hasnentai

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Add documentation for needed transform to Broadway

Closes #114
Change description
Added a section to the Broadway plugin documentation that points out the use of a transform to add correct 'acknowledger'.
What problem does this solve?
Incorrectly tagged values that cannot be found by the Grafana Broadway dashboard, when the 'acknowledger' is set to the default, namely the name of the Broadway producer module.
Issue number: #114
Example usage
Examine docs to verify the change.
Additional details and screenshots
Built docs

Checklist

[ ] I have added unit tests to cover my changes.
[X] I have added documentation to cover my changes.
[X] My changes have passed unit tests and have been tested E2E in an example project.

Coverage decreased (-0.1%) to 83.933% when pulling cbe30dd4a33fe195e9e419b72ae78e77ac3489a9 on dsschneidermann:patch-1 into d4346eb0ca87ffba5276ffaf0723b8f7c4f5b4fd on akoutmos:master.

Let me check this mix --formatter thing and revert

Thanks for the contribution! Really appreciate it. Looking back at this issue, I recall there not being any other way to determine what module was responsible for servicing the message aside from using the transformer. Thanks for making this easier for future users 😃 .

This example is wrong (as of 2022-10-11).
The event parameter is a full %Message{}.
And now I have to implement an ack() function that I have no idea how.
I'm using the RabbitMQ producer btw.

@moniquelive Yes this was subsequently discovered, see https://github.com/akoutmos/prom_ex/issues/114#issuecomment-1232752492
Documentation should be updated to match the above


joanfm / jina-embeddings-v2-base-en and -de fail with error code 500

What is the issue?
I tried to integerate the german embedding model joanfm/jina-embeddings-v2-base-de , into my LlamaIndex RAG application. During the creation of the embeddings the process ollama fails with error 500:  llama runner process has terminated: exit status 0xc0000409.
When calling:
pass_embedding = Settings.embed_model.get_text_embedding_batch(
    ["This is a passage!", "This is another passage"], show_progress=True
)

ValueError                                Traceback (most recent call last)
Cell In[16], [line 2](vscode-notebook-cell:?execution_count=16&line=2)
      [1](vscode-notebook-cell:?execution_count=16&line=1) # Test the embedding model
----> [2](vscode-notebook-cell:?execution_count=16&line=2) pass_embedding = Settings.embed_model.get_text_embedding_batch(
      [3](vscode-notebook-cell:?execution_count=16&line=3)     ["This is a passage!", "This is another passage"], show_progress=True
      [4](vscode-notebook-cell:?execution_count=16&line=4) )
      [5](vscode-notebook-cell:?execution_count=16&line=5) print(pass_embedding)
      [7](vscode-notebook-cell:?execution_count=16&line=7) query_embedding = Settings.embed_model.get_query_embedding("Where is blue?")

File c:\Users\Stefan.Mueller\AppData\Local\miniconda3\envs\llamaindex\Lib\site-packages\llama_index\core\instrumentation\dispatcher.py:274, in Dispatcher.span.<locals>.wrapper(func, instance, args, kwargs)
    [270](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/instrumentation/dispatcher.py:270) self.span_enter(
    [271](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/instrumentation/dispatcher.py:271)     id_=id_, bound_args=bound_args, instance=instance, parent_id=parent_id
    [272](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/instrumentation/dispatcher.py:272) )
    [273](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/instrumentation/dispatcher.py:273) try:
--> [274](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/instrumentation/dispatcher.py:274)     result = func(*args, **kwargs)
    [275](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/instrumentation/dispatcher.py:275) except BaseException as e:
    [276](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/instrumentation/dispatcher.py:276)     self.event(SpanDropEvent(span_id=id_, err_str=str(e)))

File c:\Users\Stefan.Mueller\AppData\Local\miniconda3\envs\llamaindex\Lib\site-packages\llama_index\core\base\embeddings\base.py:331, in BaseEmbedding.get_text_embedding_batch(self, texts, show_progress, **kwargs)
    [322](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/base/embeddings/base.py:322) dispatch_event(
    [323](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/base/embeddings/base.py:323)     EmbeddingStartEvent(
    [324](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/base/embeddings/base.py:324)         model_dict=self.to_dict(),
    [325](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/base/embeddings/base.py:325)     )
    [326](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/core/base/embeddings/base.py:326) )
...
    [100](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/embeddings/ollama/base.py:100)     )
    [102](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/embeddings/ollama/base.py:102) try:
    [103](file:///C:/Users/Stefan.Mueller/AppData/Local/miniconda3/envs/llamaindex/Lib/site-packages/llama_index/embeddings/ollama/base.py:103)     return response.json()["embedding"]

With mxbai-embed-large:latest this works without an error.
OS
Windows
GPU
Nvidia
CPU
Intel
Ollama version
0.1.37

Ollama doesn't currently support Jina Embeddings v2, it should be supported after https://github.com/ollama/ollama/pull/4414 gets merged, so you'd likely have to wait for the new Ollama release or build from source after the PR has been merged.

hey @qsdhj,
Indeed, there is a need for ollama to update its dependency on llama.cpp and to release a new version for Jina Embeddings V2 to be available.
I created and tested those models by building it manually.

hey @JoanFM,
thanks for your reply.
Do you or some other here, now what the status of batch processing of embeddings with ollama is?
Without it, the feature is useless for my intended use.

Hey @qsdhj ,
I am not sure about this

Is this still a problem on the latest version with the llama.cpp update?

This works with the latest llama.cpp update.
BTW, I recommend using the jina/jina-embeddings-v2-base-en as this one was just a test account


Add the possibility to deal with DCU files

Add the possibility to deal with DCU files, when I have no access to the .PAs file

Merged!


Delete boxes and last transaction

implement delete boxes in the backend
will implement delete last transaction after confirming with NPO on how boxes are displayed on the map

/cib delete box

Branch 32-delete-box created!


Jenkins tests always returns 'invalid'

The following markup:
[![Jenkins tests](https://img.shields.io/jenkins/t/https/builds.apache.org/Any23-trunk.svg?maxAge=86400)](https://builds.apache.org/job/Any23-trunk)
produces:

Closing as fixed via #1777


Adding authentification with keycloak gatekeeper

Need: Authentication with keycloak Gatekeeper.
Headers sent by gatekeeper to identify the user are X-Auth-Token and X-Auth-Username.
We use these headers to re-assign the value of X-Keycloak-Sec-Auth header.
Behaviour:
The header X-Keycloak-Sec-Auth is first checked. If present, we have the same behaviour than before.
If not present, we checked if headers X-Auth-Token and X-Auth-Username are present.
We needed this quickly enough to our developments. Therefore, there are some part of code that could be configurable (trusted connexion as we use auto-sign certificate).
Thx !

@marctanguy Thanks for your PR. I will check it in couple of days.

@marctanguy I have created my own supporting code ca0e830 . You can check it or use the pre-release version 0.4.0-prev0-SNAPSHOT.
If there isn't problem with it, I will close the PR. Thanks for your job. :)

@flytreeleft You can close the PR ! Thx ! ;)