Cannot set network.http.useToken to true via xml config

Also see: #6478
OrientDB Version, operating system, or hardware.

v2.2.7 (Docker)

ORIENTJS

v2.2.2

Operating System

[ ] Linux

Expected behaviour and actual behaviour
The following config in orientdb-server-config.xml appears to accomplish nothing
    <properties>
        <entry name="network.http.useToken" value="true"/>
    </properties>

relevant config settings from console orientdb>config command result:
|109 |network.http.sessionExpireTimeout                  |300                                                                                |
|110 |network.http.useToken                              |false                                                                                |
|111 |network.token.secretyKey                           |                                                                                |
|112 |network.token.encriptionAlgorithm                  |HmacSHA256                                                                                |
|113 |network.token.expireTimeout                        |60                                                                                |

I can use config set on the console to enable but otherwise adding the above in the server config doesn't appear to set these props.
I am trying to enable tokens as I am getting frequent errors like this in OrientJS:
{ OrientDB.RequestError: The token provided is expired
    at Operation.parseError (/usr/local/lib/node_modules/.../node_modules/orientjs/lib/transport/binary/protocol33/operation.js:864:13)
    at Operation.consume (/usr/local/lib/node_modules/.../node_modules/orientjs/lib/transport/binary/protocol33/operation.js:455:35)
    at Connection.process (/usr/local/lib/node_modules/.../node_modules/orientjs/lib/transport/binary/connection.js:399:17)
    at Connection.handleSocketData (/usr/local/lib/node_modules/.../node_modules/orientjs/lib/transport/binary/connection.js:290:20)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:177:18)
    at Socket.Readable.push (_stream_readable.js:135:10)
    at TCP.onread (net.js:542:20)
  name: 'OrientDB.RequestError',
  message: 'The token provided is expired',
  data: {},
  previous: [],
  id: 1,
  type: 'com.orientechnologies.orient.enterprise.channel.binary.OTokenSecurityException',
  hasMore: 0 }

@jpstrikesback
how do you configure the Connection?
do you use
useToken: true

Indeed I do :)

try to increase the token timeout
http://orientdb.com/docs/2.2/Configuration.html#networktokenexpiretimeout

I had it set to 360000 I believe, but that was another setting that didn't
register
On Wednesday, 31 August 2016, Enrico Risa<EMAIL_ADDRESS>wrote:

try to increase the token timeout
http://orientdb.com/docs/2.2/Configuration.html#networktokenexpiretimeout
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/orientechnologies/orientdb/issues/6633#issuecomment-243749088,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbMe6cnWijZ9970W63qS4HM1PIxbxJFks5qlXQUgaJpZM4JwJdl
.

Can you check the config  in Studio?
http://<ip>:<httpPort>/studio/index.html#/dashboard/general

then Global Cfg tab
Thanks

Ok, so, the timeout (and key) were settings I added after initially reporting:
    <properties>
        <entry value="1" name="db.pool.min"/>
        <entry value="50" name="db.pool.max"/>
        <entry value="false" name="profiler.enabled"/>
        <entry name="network.http.useToken" value="true"/>
        <entry name="network.token.secretKey" value="...."/>
        <entry name="network.token.expireTimeout" value="60000"/>
    </properties>

They still didn't & don't show up in the console config list BUT I haven't had the error since I added them and the dash shows that the settings are enabled (the console still shows them as disabled)
On dash:

I'd like to narrow it down but since it's working I've run out of time to play. Feel free to leave this open or close it until I can repeat it.
Cheers!
JP

@jpstrikesback
i think you don't see from console settings list because it's showing the default one instead of asking to the server.
Thanks
Enrico


Add transaction mapping to accounts

Allow transactions to be mapped to accounts (send & receive) and stored inmem and in db

I'll start working on this in https://github.com/AgustinCB/lachesis/tree/issue-13. Expect to complete in a couple days. Collaborations welcomed!

Will move this over to a custom EVM implementation instead of a babble implementation.


Documentation📄: Sync Open Horizon documentation

What is the current documentation state?
This issue will be used to sync edits between the upstream Open Horizon documentation and the downstream IBM product documentation. Some edits might flow in the both directions.
Where is this stated?
No response
Why do you want to improve the statement?
No response
Proposed Statement
No response
Additional context.
No response

I have visited  / reviewed the fixed pages.  Two pages still have formatting issues.

https://open-horizon.github.io/docs/hub/cluster_sizing.html
https://open-horizon.github.io/docs/developing/further_reading_devices.html
https://open-horizon.github.io/docs/developing/service_containers.html

this page has ordered bullets that are not correct in the MacOS section.

https://open-horizon.github.io/docs/getting_started/faq.html
https://open-horizon.github.io/docs/getting_started/components.html
https://open-horizon.github.io/docs/hub/configuration.html
https://open-horizon.github.io/docs/installing/advanced_man_install.html
https://open-horizon.github.io/docs/installing/edge_cluster_agent.html

this page has ordered bullets that are not correct in the Installing agent on OCP Kubernetes edge cluster section
Several code blocks are not indented correctly.

https://open-horizon.github.io/docs/using_edge_services/cpu_load_example.html
https://open-horizon.github.io/docs/installing/sdo.html

I will open a new Issue to fix the problems identified above.


Unable to create codable object for the specific json in swift

For the following json:
{ "explore_category_collection": [ { "entity_id": "112", "attribute_set_id": "3", "parent_id": "2", "created_at": "2018-05-01 09:48:07", "updated_at": "2018-08-30 15:00:25", "path": "1/2/112", "position": "4", "level": "2", "children_count": "0", "is_deal": "1", "name": "Summer Girls", "image": "Summer_Girls-02_-_Copy.jpg", "url_key": "summer-girls", "deal_end": "2018-10-31 00:00:00", "start_from": "99" } ] }
It is giving me let exploreCategoryCollection: [[String: String]]? but it supposed to be give a codable object.
Thank You.

quicktype is guessing that that's a map, since it has a lot of keys and all the values are strings.  You can turn that off in the UI:


Crashing on moving winodw in child windows

Fixed in this commit https://github.com/leanflutter/window_manager/commit/8fa23db7f4c2cf8cf3085d5fc06e4ceb7857a2f5


mat-stroked-button with matBadge is cropped

Bug, feature request, or proposal:
On a mat-stroked-button with a matBadge, the badge is cropped.

What is the current behavior?
matbadge is cropped.
What are the steps to reproduce?
Change the mat-raised-button to a mat-stroked-button here :
https://stackblitz.com/angular/gxraooqgqod?file=app%2Fbadge-overview-example.html
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 7
Angular Material 7.0.2
Browser: Chrome

Good catch. This is caused by https://github.com/angular/material2/commit/4cdf5bafd6af0085d3fe93c755a92c92bfd3e483.
We should consider removing the overflow: hidden again, and just expanding the overlays by the amount of pixels the border takes up.
This is how it would be if we just remove the overflow and specify a border-radius for the underlying ripple container, and focus overlay.

As mentioned above, we could technically expand the focus-overlay and ripple container by the width of the border, in order to be able to remove the overflow: hidden.

The trade-off here would be just that it won't work properly if someone changes the border-width of the stroked button. Any thoughts @crisbeto?

It should be fine, as long as we put the border width in a variable.


python310Packages.chispa: disable tests and adjust inputs

Description of changes
Fix build (https://hydra.nixos.org/build/196355105)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 198273 run on x86_64-linux 1

4 packages failed to build:

python310Packages.gradient
python310Packages.gradient-utils
python39Packages.gradient
python39Packages.gradient-utils

8 packages built:

python310Packages.chispa
python310Packages.hyperopt
python310Packages.pyspark
python310Packages.shap
python39Packages.chispa
python39Packages.hyperopt
python39Packages.pyspark
python39Packages.shap


Bring CI up to latest and greatest, drop upper bounds

This is following the patterns of https://github.com/freckle/faktory_worker_haskell/pull/59
The only ways this differs are that it

updates the CHANGELOG and
includes the .cabal file

I'm gonna rename master to main now too... What could go wrong...

@mjgpy3 The drop upper bounds LGTM. Nothing stood out in the CI changes, but I have to admit that I couldn't tell you what that is doing exactly.

base bound breaks release when removed. Putting it back now.


Prep templates not deleting correctly

We need to make the delete function (and really all the stuf like it) a transaction block. We are already seeing issues where everything but the actual reference in the prep_template table is deleted, causing issues with processing.

Can this be closed? I think this was addressed in https://github.com/biocore/qiita/pull/866 and https://github.com/biocore/qiita/pull/850, right? If not please describe what's missing.

Not really... I think the deletion of the prep templates should be also a transaction block. I used transaction blocks for template creation, but not deletion...

OK, thanks for checking.


feat: add tabs component

Feature request
Add tabs component
Documentation links
Documentation: https://www.decathlon.design/726f8c765/p/705308-tabs-beta/b/68fc78
Figma: https://www.figma.com/file/zDZIyayUlr1yTWrsi7cFoo/Vitamin---Web-UI-kit-(v0)?node-id=6840%3A14866
Checklist

[X] CSS (Thanks @GaspardMathon)
[ ] React
[ ] Svelte
[ ] Vue

Hello! I am not sure if I am supposed to ask it here. Currently, the tabs component seems to only show an active state on focus, and when the focus is lost, there is no indication on with tab is active. For example, it could be nice to show that state with a .active class on a child. Or maybe there is another way that I didn't think about?


Merge with Regular Expressions?

If you want to merge this with RegularExpressions.jl, I could make you a collaborator over there, or submit a pull request here, whichever you'd prefer.

I haven't really thought about yet which parts are better in which package. I only got the feeling that the syntax in mine is a bit more concise but some features are missing that you have. Do you have some specific ideas right now what you'd merge?

That's the sense I got too. No particular ideas, just thought it would be nice to have the best of both


Feature/#38 blockquote styling

This feature adds some much needed blockquote styling.
Blockquote on mobile

Blockquote on Desktop

Additional updates

Add blockquotes to latest block to help improve content visuals.

Closing to tryout branch deploy feature.


(Erlang) Apps should be used for include_lib too

Just a small one - include_lib should work for multiple app projects as well and this PR does that.

Merged, thank you.


[WIP] feat: add Github Codespaces development environment support

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

fix #396
Related PR: #568
2. What is the scope of this PR (e.g. component or file name):

.devcontainer/devcontainer.json

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.988%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2300

Relevant Lines:
2614

💛  - Coveralls

Usually, the image tag is used in the .devcontainer.json file instead of the build tag, which allows Github Codespace to start up more quickly by avoiding the time it takes to build the image. However, the kclvm-builder:latest image on Dockerhub hasn't been updated in three months. I need to wait for the new kclvm-builder image, which includes PR #568, to be available on Dockerhub.


Makisu Use in K8

Hi,
Could someone please  help me out? This is not an issue. Need some help to use Makisu and not sure where to post.

I want to use Makisu to build images and push to the docker registry from the Kubernetes cluster. So, do I need to install Makisu in my MAC or in Kubernetes?
I have kubectl in my MAC and configured it to use my remote Kubernetes cluster.

Do I need any special root or elevated permissions to use Makisu or to  build and push the image using Makisu in my private registry ?

Appreciate your help!!
If this is not the right forum, could you please let me know where to post this type of questions. Sorry again for opening this as an issue.

No need to install anything, just use makisu image for you job. You can checkout our k8s setup example.
You don't need elevated permissions, but might need root user.

You are welcome to join our slack channel.

Thanks Much!
I will use the slack channel. Could you please confirm whether I need to run Makes as root user. You mentioned it might need root user. I do have RUN commands and doing some installs in my Dockerfile. Appreciate your help.
Thanks in advance!

It depends on the content of the base image and your container setup - if it's a public base image like ubuntu:latest, then you do need to run as root user inside the container.


It is more apparent with bigger sizes.
To be fair, it is the same in Vaadin 7 and in Vaadin 8 compatibility packages.
See also open issue https://github.com/vaadin/framework/issues/8333
Apparently only in monthly View.

separate issue created ;-) for the second one

fixed!
next release

I'm experiencing this problem in beta 3 when I set the calendar to full size (setSizeFull). The bottom of the calendar month view is cut off - the week and day calendars are fine. Shouldn't this have been fixed en beta 3?

still found this in BETA4 - any chance to get this fixed?


do a write up of the animate function and its arguments

Worth pulling together various discussion and examples from existing .Rmd and collate a decription about when, why to use thus function and the various arguments including ... args that are passed to other methods e.g. type also see #17

Happy to help if no one else has this one. I'll be starting on it today

@adam-gruer is there any objection to rendering the animate tutorial as an html doc instead of github doc? The tutorial shows how to render videos instead of gifs, but I don't think github docs are capable of showing videos.

Indeed, I got the file too large problem. No worries, I'll just move back to github docs and leave videos as external links.

Closing because @will-r-chase is amazing - see 55cbbd555386511eb1f0c80fe4c5a0e0ecf52920 and parent commits and the output https://github.com/ropenscilabs/learngganimate/blob/master/animate.md


[FEATURE] Llama Integration

If any one integrated with Llama please can you help me with that?

sure first off all run below command in cmd
ollama pull llava
then once it done then its simple first close user lama runing locally and then again open
lama and use command  ollama serve
then open new cmd and then use command operate -m llava
one note its not that good


Added IR code for Rinnai Heaters

Added code for Rinnai Heaters
Enduro 13
Dynamo 15
Avenger 25

Hey, just wanted to say that I just tested this on my Rinnai, Unsure of model but might be a Royale, and it works great.
Thank you for sharing this.


Roll Flutter Engine from 774cb34d3ff5 to 782e1bf55e62 (4 revisions)

https://github.com/flutter/engine/compare/774cb34d3ff5...782e1bf55e62
2022-10-28<EMAIL_ADDRESS>Roll Skia from e474903a0236 to b0a3c0802163 (5 revisions) (flutter/engine#37127)
2022-10-28<EMAIL_ADDRESS>Revert "Announce alerts through SemanticsService on Windows (#36966)" (flutter/engine#37120)
2022-10-28<EMAIL_ADDRESS>Remove deprecated calls to updateSemantics in PlatformDispatcher (flutter/engine#36673)
2022-10-28<EMAIL_ADDRESS>Remove deprecated TextInputClient scribble method code (flutter/engine#36970)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Improving Hover Effect

I want to improve the hover effect on each text and titles of every blog card and other logos>
Please assign me this issue under GSSCO23

Hi @Swapnil-Singh-99, you may work on this and please refer to the Contribution guidelines on the readme once.
All the best!


Thought about redux and GraphQL?

This is a pretty interesting development, though have you seen redux and GraphQL? The GraphQL technology is pretty cool and redux as a store is super simple.
Scott

Hello @smolinari
Thank you. The PR that I'm going to merge today has even more structure to it.
I have heard about those, but I haven't really worked with them yet. I'm not sure how they apply to this module. Don't they solve different problems? Perhaps you can explain to me what benefit they could bring this module.
What I wanted to make, was a simple but organized way to talk to my REST API. I have worked with a lot of ORM systems, in both PHP and Node and this is me trying to combine what I liked.

GraphQL solves a lot of problems that come up with REST APIs. One of the most important one's is the issue of versioning. With GraphQL you have a single end point. It allows client applications to evolve completely independent of the backend. Another is multiple requests. GraphQL aggregates the queries needed and then sends it off to the server in a single package. Great for mobile. Plus, with GraphQL queries, you can have the components themselves (like in React JSX) query for the data they need.
I am not a professional front end developer. But I do understand a lot of the concepts and issues with different technologies and GraphQL is an answer to a lot of web API issues.
Here is some reading and viewing on GraphQL.
https://www.youtube.com/watch?v=WQLzZf34FJ8
https://www.youtube.com/watch?v=Cfna8gwt9h8
https://facebook.github.io/react/blog/2015/05/01/graphql-introduction.html
Scott

Hello again @smolinari
That sounds interesting, but as I expected solves a different problem. In most cases, I prefer working entity based. I'll dive into the resources you posted to educate myself further on the subject.
I'll close this ticket now as it doesn't apply to this repository.


LibraryInitializer not running on module initialisation

Hi, have been using corert for a few days and its been a really great experience, however I have been trying to get something to run on module load (similar to a dllmain or a c++ global initializer).
I saw the LibraryInitializer that can be enabled for autoinit libraries however whilst this results in il compiling in my code this initializer is never run (and looking at a disassembly it doesnt look like it should be run).
Is there any reason for this that I am missing? Otherwise is there any possibility that this functionality could be added through some other mechanism?
Thanks,
Em.

The --initassembly command line option should do that (this is exposed through <ItemGroup><AutoInitializedAssemblies Include="YourLibraryName" /></ItemGroup> in project files if you use a csproj to publish).
Can you make sure that things are named the right way in the assembly? Should be Internal.Runtime.CompilerHelpers namespace, LibraryInitializer type, and InitializeLibrary static method.

namespace Internal.Runtime.CompilerHelpers
{
    public static class LibraryInitializer
    {
        public static void InitializeLibrary()
        {
            Loader.OutputDebugString("******* InitializeLibrary() *******");
            new Thread(Loader.OnAttach).Start();
        }
    }
}

is what I have in my library - Looking at disassembly it is added in __managed_Startup which is where it should be (It is however at the top of the init list rather than the bottom which could be an issue).
However neither the OutputDebugString happens (As seen from the vs debugger output panel) nor the thread starts (which would call Kernel32 AllocConsole() and do other stuff).
No breakpoints are hit in that function which is fine but I am compiling in debug mode so i would expect breakpoints in Loader.OnAttach to happen.
There are also no exceptions thrown and the starting thread appears to exit fine.

Yeah, if this gets ordered before the class libraries initialize themselves, it's very early and things might not work great. If you're fluent in debugging assembly you could step through it and see what's going on.
Now I'm just shooting random ideas - this is where the list is set - maybe setting IlcSystemModule property to System.Private.CoreLib would make this not run and then you can define this list in your project with the right ordering):
https://github.com/dotnet/corert/blob/43e327cbc0321c3dbf47590bbeea02c102affcc2/src/BuildIntegration/Microsoft.NETCore.Native.targets#L92-L97

Oh and this is the rest of the list:
https://github.com/dotnet/corert/blob/43e327cbc0321c3dbf47590bbeea02c102affcc2/src/BuildIntegration/Microsoft.NETCore.Native.targets#L99-L105

InitializeRuntime() calls __managed__Startup(). InitalizeRuntime() is called by a dynamic initializer and is the first item in the init list
Dispite this it never appears to get called (having put breakpoints on both of them
The dynamic initializer loads InitializeRuntime into a function pointer that is appears to be used to initialize the runtime but becuase no one touches that function pointer the runtime is never initialized and none of the functions in __managed__Startup() are ever called.

Im assuming this creates the behaviour that the runtime is lazily initialized when the module is called into - which makes sense, however I would like a way to get the runtime to initialize at module load time

Ah, you're doing a library not an EXE. Missed that detail.
We initialize lazily on purpose. Doing things in DllMain is scary (googling for "old new thing dllmain" has many stories). Could you just expose your own Intialize method (that can be empty - it doesn't matter) to provide an explicit way to initialize?

This is true. My solution right now is to CreateThread() inside of dllmain to call my initialise function
#include <Windows.h>

// Exposed by the dotnet lib
void Initialise();

// This isnt defined in bootstrapperdll?
// In the CppCodeGen version this is just a throw
// so we dont need to do anything here other than show that this has
// failed
void ConstrainedCallSupport_GetStubs(void *a, void *b) {
    __fastfail(0xDEADBEEF);
}

void on_attach(HMODULE param) {
    Initialise();
}

void on_detach() {
}

BOOL APIENTRY DllMain(HMODULE hModule,
                      DWORD   ul_reason_for_call,
                      LPVOID  lpReserved) {
    switch (ul_reason_for_call) {
    case DLL_PROCESS_ATTACH: {
        // Create a new thread and detach it
        // the dllmain thread has a ton of limitations
        // and this is good practise anyway
        CreateThread(NULL, 0, &on_attach, hModule, 0, NULL);
    } break;
    case DLL_THREAD_ATTACH:
    case DLL_THREAD_DETACH:
    case DLL_PROCESS_DETACH:
        on_detach();
        break;
    }
    return TRUE;
}

And by creating a static lib and then linking I can do what I want. Ideally I would like a way to be able to do this from inside C# and not have to have this single file in another language.

Im gonna close this issue because this its clearly not one - however I will open one regarding getting some functionality like this and maybe try to pr it myself. Thanks for the help Michal!


ADS: Fix maestro tests for ExpandableView

Task/Issue URL: https://app.asana.com/0/488551667048375/1205707058640578/f
Description
Fixes maestro tests that were broken after the release of ExpandableMenu
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #3663   👈

This comment was auto-generated by Graphite.


JIRA 745 - modifying center setting notifications to have a type field

@aml-development/ozp-backend-team
Requires

ozp-react-commons branch orgstewardNotifications https://github.com/aml-development/ozp-react-commons/pull/105
ozp-backend branch orgstewardNotification (no s at the end) https://github.com/aml-development/ozp-backend/pull/375

Use Case:

An admin has the ability to send out a notification to all Content Stewards, notifying them to review their org's Listings and make any necessary changes.
Content Steward updates Listing as needed via Create New Listing Form (the usual means of updating listings)
Content Steward and listing owner(s) are notified when listing has been updated and approved

Acceptance Criteria:

Only admins can send notifications to content stewards
All content stewards receive the notification to update their apps
Only content stewards receive the "update app" notification type
Content stewards can click on a link in the in-site notification to go to the same Listing Management Recent Activity tab. (I chose this tab because all org stewards will have it and they can easily go to published listings from overview list on the left. They can also see which ones have been updated recently)
The system notification type still functions as before there was no "Type" dropdown

To test:
As bigbrother,

Go to Center Settings (from the dropdown menu)
Go to the Notifications Tab
Select the Update Request type
See that the Notification text is populated with a default message (you can change this message if you like)
Set expires on date
Press send

Login as david, julia, obrien and wsmith to make sure that they have received the message and that it has the link as detailed in acceptance criteria
bigbrother should not receive the notification
hodor should not receive the notification
jones should not receive the notification

Logged in as obrien
Went to Listing Management from drop down menu on top right
Clicked 'See More' in notifications drop down
Clicked on 'Go to Listing Management' link
In the background you can see the page changes. However, once you click out of the 'See More' notifications modal, URL changes back to 'My Listings'

I can not reproduce the error @mleeBoeing found.  Can someone else also look?
Otherwise, the notification sends, org stewards (and not regular users) see the message, and the link in the message take them to the Listing Management page.
👍

I'm testing now

Most likely issues with my local box as machine was kickstarted that day

@mleeBoeing - please test again before we merge

Update - Bug is reproducible.
Additionally, closing the Notification modal, going to another tab in the user-managment url root, and opening the Notifications modal again, results in not being able to close the Notification modal.

@blynch11p, @mleeBoeing - I pulled MLs branch and tested with BLs OZP-RC #106 branch.
:+1:

👍
I'm going to close this PR, referencing https://github.com/aml-development/ozp-center/pull/900 and merge in #900


let out anything from firewall host itself rules generated incorrectly

The "to !" networks on the openvpn rules have no basis in reality
It is worth noting that the OpenVPN interfaces that this affects are each assigned to interfaces with ipv4 and ipv6 configuration both set to None, to let openvpn handle all that itself.

pass out  route-to ( ovpnc5 <IP_ADDRESS> ) from <IP_ADDRESS> to !<IP_ADDRESS>/12 keep state allow-opts label "let out anything from firewall host itself" # this is a /24 not a /12
pass out  route-to ( ovpnc6 <IP_ADDRESS> ) from <IP_ADDRESS> to !<IP_ADDRESS>/15 keep state allow-opts label "let out anything from firewall host itself" # this is a /32, not /15
pass out  route-to ( ovpns3 <IP_ADDRESS> ) from <IP_ADDRESS> to !<IP_ADDRESS>/11 keep state allow-opts label "let out anything from firewall host itself" # this is another /24, not /11
pass out  route-to ( igb0 24.224.x.x ) from 24.224.x.x to !24.224.x.x/24 keep state allow-opts label "let out anything from firewall host itself" # the /24 here is correct

@djGrrr is it working now, or still a bit of trouble reading the ifconfig output?

@fichtner with #1395, this is now fixed :)


chore: avoid creating kv buckets when watermark is disabled

If watermark is enabled later, will the buckets be created?

And what is the reason we want to skip creating?

this could cause regressions.


DAG matching to prevent joining redundant instructions

We have several pruning rules in our enumerative algorithm that prevents us from enumerating on silly combinations. An example of such a rule would be sub %0, %0. The pruning rules work great but these pruning rules are not respected when holes are involved and we have to join two instructions.
Consider this example:
%0:i8 = var ; 0
%1:i1 = hole
%2:i1 = hole
%3:i1 = usub.sat %1, %2
infer %2

%1 can take the form of trunc %0 and then %2 can also take the same form afterwards. The problem is that when joining the instruction, the instruction joiner is not smart enough to know that it would lead to a silly instruction at %3 (for which a pruning rule exists) where we will be substracting the same thing from the same thing.
One way to solve this problem which also seems correct is to fix instruction joiner such that whenever a new form is taking the place of a hole, we check if that form has already been present in the current
candidate. If it's already present, enumerative algorithm should already have taken care of reusing that operand as many times as required or it wouldn't have reused it if pruning rule exist to prevent same operand from being used (like our previous example).
DAG matching:
To be able to accomplish this, I did a DAG matching in the candidate. I will take the new instruction just generated and try to find if an "equivalent" of it already exists in the candidate containing the hole. All the instruction are matched by their op type and all the terminal insts like reserved const, holes, and variables are matched by their address. If a DAG is found in the tree, we ignore the guess and move on.
This is a O(mn) algorithm where m = number of nodes in haystack DAG and n = number of nodes in needle DAG. Since in our case m and n will mostly be small, we should be fine with this.

plz refresh, it looks like the diffs shown here are including the other pull req too

I'd like you to do a quick experiment where you generate all guesses (for 3-4 instructions -- make it take some time), but don't call the solver at all, and measure the time before and after this patch, let's make sure it's not slowing things down too much

Here's the data. Not much difference for num-instrs<=3. Noticeable but still small difference when num-instrs=4.

perfect. thanks. I think this amount of overhead of totally acceptable, since it allows us to avoid expensive solver calls.

sorry, one more thing: how many fewer guesses do you get after this patch at n=4?

(5_2 means 5th example and num-instrs=2, etc.). All other RHS were only tested for num-instrs=2 as search space was quite huge because I am ignoring the cost of RHSes while doing this experiment.
This is the data. Here are the LHSes.
0:
%0:i32 = var
%1 = sub %0, 1
%2 = add %1, %1
%3 = shl %2, 1
infer %3

1:
%0:i32 = var
%1 = add %0, 1
%2 = and %1, 5
%3 = or %2, 42
infer %3

2:
%A:i8 = var
%B:i8 = var
%na = xor %A, -1
%op1 = xor %na, %B
%r = or %A, %op1
infer %r

3:
%0:i64 = var
%1:i64 = var
%2:i64 = var
%1b = xor %1, 23513542
%2b = xor %2,<PHONE_NUMBER>98
%3 = shl %0, %1b
%4 = lshr %3, %2b
infer %4

4:
%0:i32 = var
%1 = add %0, 1
%2 = and %1, 5
%3 = or %2, 42
%4 = sle %3, 1000
%5 = select %4, %1, %2
infer %5

5:
%0:i8 = var
%1:i16 = var
%2:i16 = sext %0
%3 = slt %2, %1
infer %3

I discussed it with @zhengyangl the other day and we were convinced that this will be missing some cases. Given that the benefit of this is not huge (and risks of missing cases are higher), let's just close this.


Server Error | Get Support

I'm 100% sure this has been asked probably over 100 times but I'm going to ask. I'm trying to download a transcription of the Merry Go Round of Life from Howl's Moving Castle, but every time and every format I try to download it in, it says Server Error and to the right, Get Support which leads me to a Discord Sever that I really don't wan to join. Any fixes? I am using the latest version (from https://github.com/LibreScore/app-librescore/releases/latest/download/LibreScore.exe), and I am running Windows 10 version 1703 (I like this version of the OS). I have resorted to using the command line interface and that so far has worked.
Thank you and happy 4th
Edit: Added details of MuseScore song, OS Specs and librescore app version

Wrong repository, duplicate of https://github.com/LibreScore/dl-librescore/issues/4


[Addition]: Ban Passive Ebony Lobster

Hotspot b58 Addresses
139FS4hTowt8UJQsBTW6itDx6zwbhoMJeB9JBVuUkDPa9yn3nfs
Discord Handle
No response
Reason(s)
All around are Midas HS. Fake Places. Spoofing. Check all HS Midas Around it.

Your Joined 22 hours ago Github.com?
The first move up is Denylist!
Since you care so much about helium? Why use a new account?
Have you been treated unfairly?
Doubt your motives?

Hello. I've been a Helium user for months now, I've used github for numerous days but I seem to remember never signing up. In my community we have found this anomaly and we want to solve it.
We are here to eliminate hs with misuse of the network, not to criticize people who collaborate with the community.
Is it necessary to join a long time ago? Can you stop wasting your time criticizing others and help the community?
Thank you


[BG] Add current time and add to shopping list

Looks good. Only for the hassGetCurrentTime there might be some changes in future, as some of the TTS services does not pronounce the time as they should. I already spoke about this problem with MIke Hansen.


Support sample-based expectation in PauliSum

It is very important to support sample-based expectation in PauliSum for real & simulating QPU devices. Given num_shots (or we can name it as repetitions. which one do you prefer?), the result of cirq.Sampler().run() is a list of qubit measurements. Based on the result, a helper to calculate (estimated) expectation value of given PauliSum is really nice to have.
I suggest cirq.PauliSum.expectation_from_samples() and the usage is identical to that of cirq.PauliSum.expectation_from_wavefunction() and cirq.PauliSum.expectation_from_density_matrix() except input signature has measurements rather than final_state or final_density_matrix. It also output float expectation value.
It is assumed that the given measurements have the shape [num_shots, num_qubits] for example. so the function expectation_from_samples() doesn't need to have num_shots as an additional input.

I want to work on it.

@mpharrigan

This is more complicated than it looks. I'd say someone with some experimental quantum computing experience should do this.

I'm putting the finishing touches on a design doc for a full solution to executing circuits to estimate a bunch of observables. That may be more than what you're asking for here. Specifically

I suggest cirq.PauliSum.expectation_from_samples() and the usage is identical to that of cirq.PauliSum.expectation_from_wavefunction() and cirq.PauliSum.expectation_from_density_matrix() except input signature has measurements rather than final_state or final_density_matrix. It also output float expectation value.

This is a rather modest request. The difficulty is that the input measurements need to somehow be guaranteed to have come from modified circuits that include pre-measurement single-qubit change-of-basis rotations. This is generally the challenging part.

Gonna leave a few comments/notes that came up from a cirq meeting months ago:

minimizing the number of terms required for a given pauli-sum expectation is NP hard
Previous work:
https://arxiv.org/abs/1907.13623)
https://arxiv.org/abs/1908.05628 (includes table of similar work)
This seems like something that should be done with respect to gate sets (e.g. readout circuits in the first link are composed from CNOT, which is may not be a good choice for some hardware)

Thank you for the comments @mpharrigan & @peterse. Do you think we have brute force algorithm first, and then optimize it later as Evan suggested?

Also, I am rethinking about cirq.PauliSum.expectation_from_samples() because it requires PauliSum, and measurements can't be obtained without knowing PauliSum. I guess cirq.PauliSum.expectation_from_wavefunction_and_samples() might be the right name, and give it the right to perform pre-measurement circuit for change of basis. What do you think?


test run 3

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2727476

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2727477

bot bench $ -v UPSTREAM_MERGE=n all

bot bench -v UPSTREAM_MERGE=n $ all

Very sloppy to open these PRs and not close them after tests are run! Please close the PRs when you are done to avoid cluttering the tracker.

Ohhh, i was not aware that i made some inconvenience. I don't wanna close them until i finished with comparing results from all PRs. I thought that draft PR is not monitored anywhere. Could you please explain me more how do they cluttering the tracker and what is the tracker?

bot bench -v UPSTREAM_MERGE=n $ all

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2760879

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2760880

It looks like i'm still be able to run command bot commands after PR is closed, so i will close those PRs as you asked. But i still would appreciate if you explain me more about this situation. Thank you.


Allow independent distribution releases

Our current release problem has a couple problems:

We cannot release distributions independently.  If we want to release a patch for the Contrib Distribution we have to also release a patch for the Core distribution.

Related, if the job fails after 1 distribution is published but not the other, we can't rerun the job, we have to push new tags.

We have run into diskspace issues in the past where the job fills up the allotted amount. The more we add to contrib and the more distributions we create the more this will be an issue.

As we look to support more distributions the connectedness of our CI will be a roadblock.
I propose we split the release of each distribution into it's own workflow with their own tags, such as v0.90.0-contrib or v0.90.0-core. The logic of each workflow can reuse a shared action, but I believe we'd need a goreleaser.yaml per distribution.
If each distribution has its own workflow we can:

Release each distribution independently via their own tags. If necessary we can add a make target to simplify the Release Manager's steps.
Each distribution will have more disk space (or any resource, including time) to work with.

Based on https://github.com/open-telemetry/opentelemetry-collector-releases/issues/357#issuecomment-1593537385.

I agree with that. I've been experimenting with splitting the distributions on their own workflows as well on a personal repository, and I prefer that approach than what I originally built in this repo here.
While I think it's great to have the ability to release different distributions separately, I don't think it's a good idea to do so: I think it might be confusing for users to have, say, otelcol-contrib-v1.0.1 and not an otelcol-core-v1.0.1 (and vice-versa).

Related, if the job fails after 1 distribution is published but not the other, we can't rerun the job, we have to push new tags.

Care to expand on this part? Is this only about the step where tags are pushed, or is it something else? I think the release should already be idempotent for most steps.

When there's an issue with a release, we delete the tags and push them again. There's a note about tags in the README:

⚠ Important note: Git tags in this repository may change at any time to fix any issues found during a release. They are only meant to trigger Github releases and should not be relied upon.

I agree that there needs to be separate workflows for the distros, otherwise we're limited in what we can release in the future. We've already seen this in the past.
Re. different versions for different distros, I'm not sure I agree that we should always keep the different versions in sync. I'm thinking of the world of the future where most of the components in core are stable and no longer need to release on a frequent cadence. This would mean that we could end up in a scenario where core and contrib are at different versions and that should be perfectly acceptable.
I understand that's not where we are today, but I also don't see this as a dealbreaker when it comes to how releases should be made.

Care to expand on this part? Is this only about the step where tags are pushed, or is it something else? I think the release should already be idempotent for most steps.

I've not looked into it in depth, but if the action goreleaser/goreleaser-action@v5 we use for publishing has an error it may be possible to push 1 image but not others. This is currently a theoretic issue.
It sounds like we are in agreement to split up the release jobs.  I could get started on that as we continue to discuss tagging.

Spent some time on this today and ran into this problem: https://github.com/orgs/goreleaser/discussions/4469.  A workaround would be to use multiple goreleaser configuration files, but I'd like to avoid that if possible.

@jpkrohling looking at your repo I do like how there are individual gorelease configs.  This will be really useful for certain distributions, like k8s or sidecar, that don't need to build specific images/binaries.
If we went that route I think we'd no longer auto-generate the file, are you ok with that?

I'm fine with that, but I'd do it as part of a next step, so that we have smaller changes applied at each iteration.

If we went that route I think we'd no longer auto-generate the file, are you ok with that?

Can you clarify this part? I see benefit in still generating this, but perhaps you found limitations around that?

I was wrong, we can still generate the files like you do in your repo.

@jpkrohling here is a PR for what the generated files can look like: https://github.com/open-telemetry/opentelemetry-collector-releases/pull/486.
I think the auto-generated files will break down if we ever make any specific distributions, like a Windows distribution, but it is possible that we can adjust the code for those cases.  For now, generating the files ensures the distributions are the same.

We now have a CI process that separates the builds!


undefined is not an object (evaluating '_state$viewState.backgroundStyle')

I am trying to run the Advance example given on Readme and getting this error "undefined is not an object (evaluating '_state$viewState.backgroundStyle')"
"react-native": "0.41.2",
"react-native-awesome-button": "^1.8.2"

getting this same error :(

Could it be, that you removed the default state entry?

I am getting the same error as mentioned above. Anyone who got the solution?


Week 1 - Primitives

Code.org

primitives
bash
capture thinking

Grade: 2.7+

3/3
Grader: Kian Pasokhi
Did all of the Install Check Hacks, "checks for python modules" Also did prints within a file. Customized fastpages to be more personal. Did hacks in primitives notebook and demonstrated learning from code.org. Coded a pound to kilogram calculator and did a compounds assignment.


Brightness Settings and Screen Saver

May I suggest something

You should let user set the default brightness via text input field 1-255. The capture current brightness is so confused.
You should let user set the dim brightness via text input field 1-255. Less confused and more control.
Add just a plain black screen as an option besides the clock and wallpaper screensaver. Combine this with the ability to set brightness to 1 (from #2) will be the closest to turning off the screen.
Or even better, let user choose the url as the screen saver. With this, user can customize what they want for the screen saver.

Thanks,
Klang

I would happy to accept pull requests for features you think would improve the project.

=)


Deployment reported failure after success.

I created a new DO server and installed the latest version of this project. The deployment did actually work (I can access my app), however mup reported a failure.
Everything went well until the very last moment:
Verifying Deployment: FAILED

Error:
-----------------------------------STDERR-----------------------------------
 run:
npm WARN deprecated
npm WARN deprecated   npm -g install npm@latest
npm WARN deprecated
npm WARN deprecated (Depending on how Node.js was installed on your system, you
npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
npm WARN deprecated on Windows, run them from an Administrator prompt.)
npm WARN deprecated
npm WARN deprecated If you're running the version of npm bundled with
npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
npm WARN deprecated will be bundled with a version of npm@2, which has some small
npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
npm WARN deprecated semver behavior.
npm WARN package.json<EMAIL_ADDRESS>No description
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>No README data

><EMAIL_ADDRESS>install /bundle/bundle/programs/server/node_modules/fibers
> node build.js || nodejs build.js

-----------------------------------STDOUT-----------------------------------

To see more logs type 'mup logs --tail=50'

----------------------------------------------------------------------------
    at /Users/Tim/Development/meteor-up/node_modules/nodemiral/lib/coreTasks.js:39:16
    at /Users/Tim/Development/meteor-up/node_modules/nodemiral/lib/session.js:146:9
    at Channel.<anonymous> (/Users/Tim/Development/meteor-up/node_modules/nodemiral/lib/ssh.js:125:9)
    at emitOne (events.js:90:13)
    at Channel.emit (events.js:182:7)
    at SSH2Stream.<anonymous> (/Users/Tim/Development/meteor-up/node_modules/ssh2/lib/Channel.js:124:14)
    at SSH2Stream.g (events.js:273:16)
    at emitNone (events.js:80:13)
    at SSH2Stream.emit (events.js:179:7)
    at parsePacket (/Users/Tim/Development/meteor-up/node_modules/ssh2-streams/lib/ssh.js:3435:10)
    at SSH2Stream._transform (/Users/Tim/Development/meteor-up/node_modules/ssh2-streams/lib/ssh.js:551:13)
    at SSH2Stream.Transform._read (_stream_transform.js:167:10)
    at SSH2Stream._read (/Users/Tim/Development/meteor-up/node_modules/ssh2-streams/lib/ssh.js:212:15)
    at SSH2Stream.Transform._write (_stream_transform.js:155:12)
    at doWrite (_stream_writable.js:301:12)
    at writeOrBuffer (_stream_writable.js:287:5)

If I get the logs:
macpro:do-newmup Tim$ mup logs --tail=1000
[xx.xx.xx.xxx]npm WARN deprecated This version of npm lacks support for important features,
[xx.xx.xx.xxx]npm WARN deprecated such as scoped packages, offered by the primary npm
[xx.xx.xx.xxx]npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
[xx.xx.xx.xxx]npm WARN deprecated latest stable version. To upgrade to npm@2, run:
[xx.xx.xx.xxx]npm WARN deprecated
[xx.xx.xx.xxx]npm WARN deprecated   npm -g install npm@latest-2
[xx.xx.xx.xxx]npm WARN deprecated
[xx.xx.xx.xxx]npm WARN deprecated To upgrade to the latest stable version, run:
[xx.xx.xx.xxx]npm WARN deprecated
[xx.xx.xx.xxx]npm WARN deprecated   npm -g install npm@latest
[xx.xx.xx.xxx]npm WARN deprecated
[xx.xx.xx.xxx]npm WARN deprecated (Depending on how Node.js was installed on your system, you
[xx.xx.xx.xxx]npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
[xx.xx.xx.xxx]npm WARN deprecated on Windows, run them from an Administrator prompt.)
[xx.xx.xx.xxx]npm WARN deprecated
[xx.xx.xx.xxx]npm WARN deprecated If you're running the version of npm bundled with
[xx.xx.xx.xxx]npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
[xx.xx.xx.xxx]npm WARN deprecated will be bundled with a version of npm@2, which has some small
[xx.xx.xx.xxx]npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
[xx.xx.xx.xxx]npm WARN deprecated semver behavior.
[xx.xx.xx.xxx]npm WARN package.json<EMAIL_ADDRESS>No description
[xx.xx.xx.xxx]npm WARN package.json<EMAIL_ADDRESS>No repository field.
[xx.xx.xx.xxx]npm WARN package.json<EMAIL_ADDRESS>No README data
[xx.xx.xx.xxx]
[xx.xx.xx.xxx]><EMAIL_ADDRESS>install /bundle/bundle/programs/server/node_modules/fibers
[xx.xx.xx.xxx]> node build.js || nodejs build.js
[xx.xx.xx.xxx]
[xx.xx.xx.xxx]make: Entering directory `/bundle/bundle/programs/server/node_modules/fibers/build'
[xx.xx.xx.xxx]  CXX(target) Release/obj.target/fibers/src/fibers.o
[xx.xx.xx.xxx]  CXX(target) Release/obj.target/fibers/src/coroutine.o
[xx.xx.xx.xxx]  CC(target) Release/obj.target/fibers/src/libcoro/coro.o
[xx.xx.xx.xxx]  SOLINK_MODULE(target) Release/obj.target/fibers.node
[xx.xx.xx.xxx]  SOLINK_MODULE(target) Release/obj.target/fibers.node: Finished
[xx.xx.xx.xxx]  COPY Release/fibers.node
[xx.xx.xx.xxx]make: Leaving directory `/bundle/bundle/programs/server/node_modules/fibers/build'
[xx.xx.xx.xxx]Installed in `/bundle/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.14/fibers.node`
<EMAIL_ADDRESS>node_modules/ansi-regex
<EMAIL_ADDRESS>node_modules/ansi-styles
<EMAIL_ADDRESS>node_modules/escape-string-regexp
<EMAIL_ADDRESS>node_modules/chalk
<EMAIL_ADDRESS>node_modules/supports-color
<EMAIL_ADDRESS>node_modules/has-ansi
<EMAIL_ADDRESS>node_modules/strip-ansi
<EMAIL_ADDRESS>node_modules/eachline
<EMAIL_ADDRESS>node_modules/type-of
<EMAIL_ADDRESS>node_modules/amdefine
<EMAIL_ADDRESS>node_modules/asap
<EMAIL_ADDRESS>node_modules/underscore
<EMAIL_ADDRESS>node_modules/meteor-promise
<EMAIL_ADDRESS>node_modules/promise
<EMAIL_ADDRESS>node_modules/source-map-support
<EMAIL_ADDRESS>node_modules/semver
<EMAIL_ADDRESS>node_modules/source-map
<EMAIL_ADDRESS>node_modules/fibers
[xx.xx.xx.xxx]=> Starting meteor app on port:80
[xx.xx.xx.xxx]Kadira: completed instrumenting the app

Sorry, I posted this to the wrong project!

No problem!


Where is the implementation of domain balance loss?

dear author, thanks for this nice repo. However, I am unable to locate the "domain balance loss" anywhere in the codebase. Can you give me a guide on this? Thanks!

https://github.com/WangWenhao0716/DomainMix/blob/main/dg/trainers.py
Line 121 - Line 122

Thanks, I see.


Fix grapghql list resolve

This PR adds support for image arrays and other custom types in GraphQL.
E.g. you can now write
title: Test
images:
  - "./image1.jpg"
  - "./image2.jpg"
  - "./image3.jpg"

and the images will be resolved correctly, including support for arguments in GraphQL queries:
testPost (id: "1") {
  title
  images (width: 300, height: 300)
}

Thanks! Realy great work! I'll take a closer look at this later tonight :)

Seems to work pretty well and I like how you re-use the arguments and resolver :)


Add security policy

See: https://help.github.com/en/articles/adding-a-security-policy-to-your-repository

Please also check if you are conform to the supported version.


Stop or cancel coroutine

Hello, sorry for my question. I use your UE5Coro to learn Coroutines and UE5. I need to stop or cancel running/suspended coroutine. Is there any possibility to do that under FAsyncCoroutine? Big thanks in advance.

There's currently no explicit support for this, but the good news is that you don't need any!

Latent coroutines (FLatentActionInfo parameter) are implemented as latent actions and can be canceled with built-in engine functionality (e.g., FLatentActionManager::RemoveActionsForObject).
Async coroutines (no FLatentActionInfo) can and should be canceled cooperatively. This can be as simple as passing a bool&, TSharedPtr/std::shared_ptr<std::atomic<bool>>, or something in between depending on your multithreading needs, then co_returning early if you notice that it got flipped from the outside. This will also work for latent coroutines of course, but it doesn't match how most BP latent nodes behave.

Built-in support for this is a highly-requested feature that's relatively high on my list of things to implement. I want to do something more convenient than simply reinventing CancellationTokens, which is basically the shared bool pointer approach with lipstick on. Unified support for BP latent actions and "true" async makes this difficult from both an implementation complexity and a runtime performance standpoint, which is mainly why this hasn't shipped yet. I don't want to commit to a subpar implementation.

Thank you for answer. The second solution is not what i need really. I want something like this FAsyncCoroutine::Cancel(). Okay, i will try to think how implement it better for my approach and needs.
Big thanks for your time, hope you will find a better solution =)

This feature will ship in 1.8.


[Vidio] Add new extractor (Closes #7195)

Cherry-picked in 7def35712a7047578643f18eaf6dda79fd8c9291, thanks.

@dstftw Thanks for accepting the PR. Could you close issue #7195 as the request is now fulfilled?


Adapt info.description to Security and Interoperablity Profile

What type of PR is this?

correction

What this PR does / why we need it:
The issue https://github.com/camaraproject/IdentityAndConsentManagement/issues/154 requests:

Clean up and update the CAMARA-API-access-and-user-consent.md document to reflect the latest profile decisions and/or to include references(*) to the new profile document where appropriate.

This PR updates the info.description section of CAMARA-API-access-and-user-consent.md that the information that API subgroups are requested to put into their OpenAPI yaml file points to the Camara Security and Interoperability Profile.
Which issue(s) this PR fixes:
Related issue: https://github.com/camaraproject/IdentityAndConsentManagement/issues/154

Could you explain why we need to change the reference pointing to ICM profile instead of CAMARA-API-access-and-user-consent.md? The content of CAMARA-API-access-and-user-consent.md is already aligned with the ICM profile, it provides a friendly description of the CAMARA defined AuthN/AuthZ flows, the technical rule set and it points to the ICM profile when needed. This info.description template is already included in multiple APIs and it would be necessary to change the content again in all of those subprojects. If it is changed, there should be a benefit.

CAMARA-Security-Interoperability.md defines everything an API consumer and especially their developers  and maybe SW-architects needs to know about getting an access token.
E.g.

which optional CIBA parameters are ignored by the Camara AZ.
how to get offline access
...

CAMARA-Security-Interoperability.md is THE document for API consumers and their developers should read.
I agree that CAMARA-API-access-and-user-consent.md is a "friendly description" not only of the flows but about what we want and mandate regarding consent.
But I think that technical documents like the API yaml file should reference technical and normative documents, which means info.description should reference CAMARA-Security-Interoperability.md

CAMARA-Security-Interoperability.md defines everything an API consumer and especially their developers and maybe SW-architects needs to know about getting an access token. E.g.

which optional CIBA parameters are ignored by the Camara AZ.
how to get offline access
...

CAMARA-Security-Interoperability.md is THE document for API consumers and their developers should read.
I agree that CAMARA-API-access-and-user-consent.md is a "friendly description" not only of the flows but about what we want and mandate regarding consent.
But I think that technical documents like the API yaml file should reference technical and normative documents, which means info.description should reference CAMARA-Security-Interoperability.md

CAMARA-API-access-and-user-consent.md has been normative so far and now also refers to the ICM profile when needed. So I don't agree, as long as I don't see a real benefit in modifying the template just to change a reference when that guideline is already applied (and/or is being applied) in multiple API subprojects. But of course that's my personal opinion, let's see what other WG participants think.

CAMARA-API-access-and-user-consent.md has been normative so far and now also refers to the ICM profile when needed. So I don't agree, as long as I don't see a real benefit in modifying the template just to change a reference when that guideline is already applied (and/or is being applied) in multiple API subprojects. But of course that's my personal opinion, let's see what other WG participants think.

As stated during the ICM meeting, the change is small and many subprojects did not adapt their documents, so have to touch them anyway e.g. to use the common security scheme. Every subproject knows that changes in guidelines in Commonalities and/or ICM might require them to adapt.

Almost all API files will undergo a change before the upcoming meta-release, as the release management group has recommended changes for the info object. The upcoming meta-release is a good opportunity to get the needed changes in across subprojects.


Which type of diodes

Hi,
I saw in the circuit diagram in the PDF that you use 2 diodes.
Can you please specify which types of diodes you suggest using?

The diodes are not critical.  I used 1N5148.


Warnings about file access with live reload

I recently ran into a problem (http://forum.ionicframework.com/t/image-uris-from-camera-plugin-and-live-reload/18767/3) where basic camera stuff wouldn't work while using live reload. From what I can see, this is a known issue when using live reload and expected. However, I can definitely see this tripping people up.
I think the CLI should issue a short, quick warning, about this issue just as a reminder. I know you can't output too much there and you already output a list of helpful commands, but I honestly think it would be worthwhile to remind folks about potential issues here. Here are some random examples.
Warning: File URIs (such as those from the Camera plugin) will not work.
or
Warning: Anything using file URIs (Camera, File, File-Transfer plugins) will not work correctly.
or
Warning: Using File URI type crap will cause zombies to appear.

Also had the same issue. Were you able to find a workaround for this? File URIs were also not loading for me and returns a "Not allowed to load local resource" error. Returning the file as a Data URI seem to have worked but it doesn't really address the problem though.

As I said above, I don't think there is a fix. Hence me suggesting a warning of some sort.

Also ran into this problem. My app uses the file system heavily, which means I can't use live reload with the emulation at all, which is a real shame.

:+1: having this issue as well.

It's unfortunate. To get around this, I had to force my app to use placeholder images if it couldn't access the picture it just took.

I'm getting the same issue, this works:
ionic run android

onFinished() [content://com.android.providers.media.documents/document/image%3A2834]
File locaton is: /storage/emulated/0/Movies/overlay.png
[INFO:CONSOLE(23)] "url", source: file:///android_asset/www/index.html (23)

And this doesn't (seems like because you load on http and file it is a )
ionic run android --livereload --consolelogs

onFinished() [content://com.android.providers.media.documents/document/image%3A2834]
File locaton is: /storage/emulated/0/Movies/overlay.png
[INFO:CONSOLE(29)] "url", source: http://<IP_ADDRESS>:8100/ (29)
[INFO:CONSOLE(0)] "Not allowed to load local resource: content://com.android.providers.media.documents/document/image%3A2834", source: http://<IP_ADDRESS>:8100/ (0)

Even if I adjust the url manually to have the local file path it doesn't work. Seems like a cross origin issue.
This issue seems to be related, with some suggestions of fixes:
https://github.com/driftyco/ionic-cli/issues/89
And another blog post about using proxies to workaround CORS issues:
http://blog.ionic.io/handling-cors-issues-in-ionic/

Here is workaround for this issue: http://stackoverflow.com/a/38796506
It uses cdfile:// protocol to access files.

The method referenced by @yura-pakhuchiy absolutely works as far as cdvfile:// is whitelisted both on native side (<access origin="cdvfile:*"/> in config.xml) and angular (via  $compileProvider.imgSrcSanitizationWhitelist).

@enricodeleo did you have to do anything else other than the access origin & the provider whitelist?
I am running :
cli packages: (C:\Users\ppatarinski\AppData\Roaming\npm\node_modules)

    @ionic/cli-utils  : 1.19.1
    ionic (Ionic CLI) : 3.19.1

global packages:

    cordova (Cordova CLI) : not installed

local packages:

    Cordova Platforms : android 6.4.1-dev
    Ionic Framework   : unknown

System:

    Android SDK Tools : 25.2.5
    Node              : v8.9.4
    npm               : 5.6.0
    OS                : Windows 10

Environment Variables:

    ANDROID_HOME : C:\Android\android-sdk

Misc:

    backend : pro

with the following changes :
config.xml
    <access origin="cdvfile:*" />

&
 $compileProvider.imgSrcSanitizationWhitelist(/^\s*(https|ftp|mailto|cdvfile|file|tel|content|blob):|data:image|/);

and getting the following error
cdvfile://storage/emulated/0/Android/data/com.paylocity.paylocityqa/cache/1E938687A1B94C0D910BB2317A777477.png:1 GET cdvfile://storage/emulated/0/Android/data/com.paylocity.paylocityqa/cache/1E938687A1B94C0D910BB2317A777477.png net::ERR_UNKNOWN_URL_SCHEME


Add YAML Frontmattter support to ConvertFrom-Markdown

Summary of the new feature / enhancement
As a contributor to a Markdown wiki repo, I would like to be able to (cleanly) parse YAML frontmatter blocks in PowerShell via ConvertFrom-Markdown.
While there's a workaround available by manually extracting the HeaderBlock from parsed tokens and feeding its inline content to a YAML parser, this is very counterintuitive. Moreover, YAML frontmatter is rendered to HTML in the generated document, which isn't ideal either. (Normally, Markdig suppresses HTML generation for these tokens).
Proposed technical implementation details (optional)
This is already a native feature of Markdig, so it should be as easy as calling .UseYamlFrontMatter() on MarkdownPipelineBuilder before .Build().
Given that these are essentially document properties, a property added to [Microsoft.PowerShell.MarkdownRender.MarkdownInfo] instances that extracts YAML frontmatter (if present) and deserializes to a CLR object would likely be the most sensible to use.

It looks like this would require augmentation to [MarkdownConverter], where the underlying parser pipeline is built - let me know if I should cut an issue for PowerShell/MarkdownRender as well.

Since it doesn't involve new dependencies I am ok with the enhancement PowerShell/MarkdownRender

Yup I am OK with it too.


UE can't connect to the network

Hi,
I am deploying 5G SA with COTS UE, and the USRP is working fine as GNB and the UE is getting the PLMN being set but not able to get connected.
Can anyone help on this.
I am sharing gnb log and config files below.
gnb.log.log
gnb_conf.txt
Regards,
meena-devi

issue resolved


fix(types): make Arbitrum, Arbitrum Goerli, Arbitrum Nova EIP1559 comp

Motivation
Arbitrum mainnet, Arbitrum Goerli and Arbitrum Nova recently switched to EIP1559 as can be seen from those example transactions:

https://arbiscan.io/tx/0x379eea89ec6c41ad8df678bbb49cd51e30aa444ed9d8c69a2c3bc522ced1155b
https://goerli.arbiscan.io/tx/0xaf9263c706c05cc024410fc6745ccf096ce5b56cd8ebb837f9b0cb21274628cf
https://nova.arbiscan.io/tx/0x38956afabf59ce8dc99c3a82ebff760ad1e78df0e3cd25f69d43adbf4276d30f

This PR updates ethers to indicate all of the chains above as non legacy.
Solution
Change the is_legacy function to return false for Arbitrum mainnet, Arbitrum Goerli and Arbitrum Nova.
PR Checklist

[ ] Added Tests
[ ] Added Documentation
[ ] Breaking changes

Clippy unrelated


[Acceptance Test] Signup and Login

Description and Goal of Test
A user can create a new account and enter the application with proper credentials
Acceptance Criteria

[x] Create a new account with email and password
[x] Login using email and password
[x] Logout of account
[x] Cannot create account with email already existing
[x] Cannot login with improper email or password

Reviewed all login tasks mentioned above with @DerekRuiz  @shash3.
All good to go!


HSEARCH-4788 + HSEARCH-4823 Documentation fixes

HSEARCH-4823: Clarify the documentation of the configuration property about the Elasticsearch version
HSEARCH-4788: Fix some out-of-date javadoc for configuration properties

Thanks, I applied your suggestions. Waiting for CI...


Added solution in C lang for Allocation Round A

Issue Number for which I'm assigned & worked: #3

Good to go!🚀


add unit tests for policy specification

New tests to validate desire behavior:

tokenGenerateNewParticipantNoPolicySpecified
tokenGenerateNewParticipantWrongPolicySpecified
tokenGenerateNewParticipantNoPolicySpecifiedOlderKeySuccessful
tokenGenerateNewParticipantWrongPolicySpecifiedOlderKeySuccessful
identityMapNewParticipantNoPolicySpecified
identityMapNewParticipantWrongPolicySpecified
identityMapNewParticipantNoPolicySpecifiedOlderKeySuccessful
identityMapNewParticipantWrongPolicySpecifiedOlderKeySuccessful

Existing tests to validate desired behavior:

tokenGenerateRespectOptOutOption
identityMapRespectOptOutOption
other existing identity map and token generate tests that do not specify policy for old participants

This PR was combined with https://github.com/IABTechLab/uid2-operator/pull/207 and merged into Master branch.


Pushing file to artifactory use relative path of the file.

In the artifactory
artifactory(             username: "username",             password: "password",             endpoint: "https://artifactory.example.com/artifactory/",             file: "example.ipa",                                # File to upload             repo: "mobile_artifacts",                           # Artifactory repo             repo_path: "/ios/appname/example-major.minor.ipa"   # Path to place the artifact including its filename             properties: {               status: "DEV",               rating: 5,               branch: "master"             }           )
why does fastlane expect file to be present in the same directory
Here is the source code
require 'artifactory'         file_path = File.absolute_path(params[:file])         if File.exist? file_path           client = connect_to_artifactory(params)           artifact = Artifactory::Resource::Artifact.new           artifact.client = client           artifact.local_path = file_path           artifact.checksums = {               "sha1" => Digest::SHA1.file(file_path),               "md5" => Digest::MD5.file(file_path)           }
The file can be anywhere in the project. How do we specify the path of the file?

I see,
file name also take the absolute path of the file.


Add PostCSS to slate.config.js

Is there any documentation for adding a PostCSS plugin in the build process? I'd like to use Tailwind CSS.

I am using PostCSS in the webpack build. I can make it configurable via slate.config.js. I'm going to change the title of this and use this issue to keep track of the progress.

@t-kelly Any progress on the use of PostCSS plugins? I'd love to be able to start using TailwindCSS soon.

Sorry to be a bother - any update on this? @t-kelly you'd mentioned that your'e using PostCSS in the webpack build - can you explain a little more on how that works? I saw your comment about slate.config.js and webpack configs here  so I wasn't sure if that's where I should start or not.

+1 -- looking to add some CSS Grid support in IE11 and add some PostCSS plugins to the build.

I don't think that it quite fits with this issue but i've implemented PostCSS using slate.config.js here: https://github.com/Shopify/slate/issues/670
It does basically replace Sass with PostCSS so it's not really using PostCSS in addition to Sass but i thought it may be helpful.

I'm sure there's more to it than what i've done here but i've started a PR that could get a decent initial version of this going: https://github.com/Shopify/slate/pull/683

@mrobit Did you already manage to get the tailwind x Slate working, i want to start with this combination but only if it isn't a big hassle?


fix: minio path for songs

:tada: This PR is included in version 1.0.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Assuming traffic from spoke subnet to on-prem goes via Azure Firewall, do we need "-UseRemoteGateways"?

When there is an Azure Firewall (or NVA) in the HUB vNET, can you clarify if/why the spoke-to-hub peering needs to have " -UseRemoteGateways" configured?
... I thought the purpose of that setting was to prompt route propagation from the GatewaySubnet to the peered (remote) vNet? In this case the routing from spoke to on-prem is via Azure Firewall in the hub.
This being the case, in this context, is the "-UseRemoteGateways" option required (or invalid) for the peering from spoke to hub?
Many thanks for any clarification!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6992344b-e177-d268-f308-2be505a2db93
Version Independent ID: 10263b55-b03c-9e1c-f0b8-ac887eb1b411
Content: Deploy & configure Azure Firewall in hybrid network using PowerShell
Content Source: articles/firewall/tutorial-hybrid-ps.md
Service: firewall
GitHub Login: @vhorne
Microsoft Alias: victorh

Thanks for the feedback! We are currently investigating and will update you shortly.

@kahawai-sre Apologize for the delay in response. This option is needed if traffic is going from a spoke to the hub gateway since you can have more than one peerings from a VNet, so we need a flag to know which one we will use as a gateway. Hope this helps. Let me know if you have any more questions and I will be glad to answer. Thank you!

... but in this case we are already controlling the preferred path for traffic that needs to egress via the gateway with routes to an Azure Firewall which itself is in the hub vNet that has the gateway (and should use it based on the effective routes in AzureFirewallSubnet).
i.e. in this context, why does the spoke vNet need to know which peered vNet has the gateway?

Thanks SaiKishor that helps. Is there a reference to that information in the docs that you can provide?

https://github.com/microsoft/Common-Design-Principles-for-a-Hub-and-Spoke-VNET-Archiecture/blob/master/README.md

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[HACKTOBERFEST 2024] - Recursion Quiz

[!IMPORTANT]
This issue is part of our 2024 Hacktoberfest initiative. If you are interested in working on this issue, refer to our top-level tasks to see if this issue is claimed, or to claim it if it is not.

This issue is to create the Recursion quiz.
The file you should be working on is found in /curriculum/challenges/english/25-front-end-development/quiz-recursion.
All quiz questions need to relate to one of these topics:

Recursion
base cases
call stack
tail-call and head-call

[!CAUTION]
Questions which do not fall under these topics will be rejected.

You are welcome to include code blocks in your questions, but please keep them short (four lines or less).
Please do NOT open a pull request until you have completed all questions. Your quiz should have exactly 20 questions.

Thank you for your interest in contributing. This issue will be opened for contribution when Hacktoberfest starts on October 1st.

[!CAUTION]
Pull requests which are created before October 1st will not be eligible for Hacktoberfest. We appreciate enthusiasm, but encourage you to hold off on contributing to this issue until the event has begun.

If you wish to be notified when this issue is opened for contribution, subscribe to notifications:

This issue is now open
If you would like to work on this issue, please leave a comment so we can assign it to you.
Be sure to read our contributing guidelines.

I'd like to help with this issue. Could you please assign it to me?

#56214 ill do this

Hey @siddharthbaleja7,
you are already assigned to different issue - https://github.com/freeCodeCamp/freeCodeCamp/issues/56183.

Hey @prachidoddi,
you are already assigned to different issue - https://github.com/freeCodeCamp/freeCodeCamp/issues/56211.

@naomi-lgbt Please assign me this task I would love to work over it .

This issue has been assigned a contributor. To prevent extraneous notifications, the issue is now locked. If you have any questions, please reach out to me in our Discord community.

I would like to work on this issue.

So did this one ever get taken care of?
Because if not I would be happy to jump on it and make a quiz 🤓
Thanks

@petercr go for it!


Implement the Go Wasm plugin: bot-detect

Ⅰ. Describe what this PR did
Implement the Golang version of the existing CPP Wasm plugin: bot-detect
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (e84f998) 38.24% compared to head (c03b25e) 38.27%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #747      +/-   ##
==========================================
+ Coverage   38.24%   38.27%   +0.03%
==========================================
  Files          60       60
  Lines        9979     9979
==========================================
+ Hits         3816     3819       +3
+ Misses       5871     5869       -2
+ Partials      292      291       -1

see 1 file with indirect coverage changes

cc @WeixinX

@OnlyPiglet Please add an e2e test for it like this PR: #720

@OnlyPiglet Please add an e2e test for it like this PR: #720

👌

@OnlyPiglet hello，这块e2e test补充有进展吗

@OnlyPiglet hello，这块e2e test补充有进展吗

finished will merge this


upgraded to grails 3... todays rebase... All unit tests passed.

Grails 3 upgrade. All unit tests passed but I did not upgrade the scripts.... The plugin descriptor may need some work.
Separate branch recommended.

Ok thanks, will create a separate branch and merge this in via command line, it is a good start

Ok.

@Omasiri The webxml plugin won't work in Grails 3.0 as there is no web.xml file

Good to know... : )
Thanks.

good to know that this great plugin will have a grails 3 branch.
Is there any blocking issue ?

is it possible to create the grails3 branch ?
I'm interested to participate to grails3 migration

Will get on this soon, next week hopefully. Focusing on the 2.0 GA release first.

I've opened a pull request for grails 3 acl plugin.

Thanks a ton for your help - this has saved me a lot of work and I'm looking forward to getting an M1 release of the plugin for Grails 3 out ASAP.

Good waiting for this release !

@burtbeckwith awesome, can't wait!  this has been my only blocker in upgrading to grails 3

Will there be an update on the documentation as well. Also will s2-quickstart be still available

@burtbeckwith Are you considering using spring security v4 in any future release?


connection to home-assistant fails.

Hello,
When I try to onncet, I get the message :
$ sudo snap connect code-server:vscs-content home-assistant-snap:configurations
erreur : cannot perform the following tasks:

Connecter code-server:vscs-content à home-assistant-snap:configurations (connection not allowed by slot rule of interface "content")

Hi,
Connect to the slot home-assistant-snap:vscs-content instead.

Thanx for your help : anything works fine!
Le mar. 1 nov. 2022 à 13:42, Joachim Marthinsen Giæver <
@.***> a écrit :

Closed #1 https://github.com/giaever-online-iot/code-server/issues/1 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/giaever-online-iot/code-server/issues/1#event-7712952028,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALCJVHU5UC666YUUMDAPKGDWGEF3NANCNFSM6AAAAAARSQ6PF4
.
You are receiving this because you authored the thread.Message ID:
@.***>


simple car entity

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 37 lines in your changes missing coverage. Please review.

Project coverage is 58.87%. Comparing base (33c5383) to head (71cc3de).

Files with missing lines
Patch %
Lines

...ava/org/hdcola/carnet/Validation/VinValidator.java
0.00%
37 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##               main      #17       +/-   ##
=============================================
- Coverage     83.90%   58.87%   -25.04%
  Complexity       32       32
=============================================
  Files             8        9        +1
  Lines            87      124       +37
  Branches          4        7        +3
=============================================
  Hits             73       73
- Misses           12       49       +37
  Partials          2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Feature Request] Support PettingZoo for Multi-agent testbed

From https://github.com/sail-sg/envpool/issues/89#issuecomment-1111713904

[ ] pistonball
[ ] atari

We are going to support matari first because pistonball needs pygame integration.
Resource:

https://github.com/Farama-Foundation/Multi-Agent-ALE
https://github.com/Farama-Foundation/PettingZoo/tree/master/pettingzoo/atari

Thanks for the amazing repo! Do you guys by chance have any update on when multi-agent PettingZoo atari will be integrated?


Use Hamcrest assertions instead of JUnit in  examples/quickstarts/helidon-quickstart-mp (#1749)

Part of #1749
I've already signed OCA. It's an automation problem.
Backport 2.x

/trigger


update: added example-typescript-project

📝 Description
Added Typescript example project template
✔ Dev Complete Checklist

[x] PR template filled out
[x] Change is tested by submitter
[] PR follows all linting and coding standards
[x] Github Issue exists (if applicable)
[x] Team member has been assigned
[] At least one commit message is in Conventional Commit format

@diegobrsign if you could please help me identify why the linting is failing that would be awesome

@lherlein @jdmedlin1 is this an active PR, or should it be moved to Draft?
Looks like this PR is related to PE-330.

@bhastings1019 not active, needs to be fully reviewed and merged. I believe it's a working example


Playground: spurious popup "please log in again"

Reproduce in Chrome:

refresh
enter a program
press "Run"

Just had a look. This was introduced in the recent achievements PR. Every trigger of the EVAL_EDITOR reducer logs an achievement event, after which processEvents is triggered and a request is sent to the backend. However the user is not logged in, and this causes an error in the request. This is also causing issues in the Github Assessments PR now.
Should be able to disable this with a conditional in processEvents


Starting incognito window and interacting with main window

I am writing tests for co-viewing functionality: user is filling out form in his browser and controller can view entered data in his browser.
When I just open new window, then the same role is applied (of controller) and I am not able to use user role (so, no cookies or whatever).
I have tried new instance, but did not succeed to run new testcafe instance inside testcafe test.
What are possibilities to run two different windows, which do not share storages/cookies, but I should be able to interact between windows (passing data, entering data in one window, checking entered data in another window)?

It is not possible at the moment. We will work on this functionality in the context of the #5291 issue. Please track it to be aware of our progress.
As a workaround, you can implement your script using parallel execution with child_process.exec or Web Workers API, but it is a complex task and such a test will be difficult to debug.
Try rewriting your tests to remove interactivity and run scripts for different roles in sequence.


MAINT: update codeowners.

Please update as wished 😃
(Reminder that only people listed in the maintainer team can be listed in this file, it's a GH thing.)

Thanks all. There is no rush so I will leave this open a bit in case.

@tupui thanks for updating this. Would you mind adding me for all meson.build files?

@tupui thanks for updating this. Would you mind adding me for all meson.build files?

Done. I did meson* to cover the option file. If I understood the syntax correctly that should work.
Feel free to adjust in general 😃

While thinking about #18298, I was wondering who the codeowner for scipy/integrate is, and it seems this entry is missing.
Other folders that are missing AFAICT:
scipy/_build_utils
scipy/_lib
scipy/cluster
scipy/constants
scipy/datasets
scipy/io
scipy/misc
scipy/ndimage
scipy/odr

Those don't have a dedicated owner. For some, like _build_utils, it may be me as the default/fallback - but I don't want to be listed, because I don't want to get pinged for each PR that touches them. CODEOWNERS is not intended to be a comprehensive listing of all maintainers, instead it is for folks who want to actively opt into getting pings for each PR that touches that file/directory.

CODEOWNERS is not intended to be a comprehensive listing of all maintainers, instead it is for folks who want to actively opt into getting pings for each PR that touches that file/directory.

Is there something in between "gets pinged for every PR that touches a given path" and "can be asked if there are fundamental questions/decisions about that module"? If not, would it make sense to introduce something like that (even informally)?

There isn't really an in-between. We had the kind of list you're interested in here, it was doc/MAINTAINERS.rst. It was well out of date more often than not though, so we decided to get rid of it. I'm not too interested in reintroducing it, because it's a bunch of churn and it's never clear where some lines are (when do you remove some folks when they're inactive for a while, etc.).

We had the kind of list you're interested in here, it was doc/MAINTAINERS.rst. It was well out of date more often than not though, so we decided to get rid of it.

Fine by me, thanks for the context. Realistically, that means any fundamental questions in such modules fall to you or @larsoner, seeing that Pauli isn't really that active anymore. I'm fine with that too, but wanted to at least ask if there's a more fine-grained fallback.

The merge conflict was because main already had the Azure config deleted, so that was trivial to resolve. I squash-merged this in--it has approvals, and release branching is coming in ~10 days or so (optimistically, at least...).
The GitHub UI also shows a green check in the diff for a valid codeowners file, so flushing the CI is pointless.


Fix fmt errors and CLA authentication

Fix fmt errors and CLA authentication

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.423%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1050

Relevant Lines:
1491

💛  - Coveralls

6d2a800e-868a-44b3-81e4-4e7a48c9a895


feat: global move from scripts to trampoline executable

I took a few shortcuts but this is a prototype of the trampoline.
upd @nichmor : no more a prototype :D
things on how to test this:

[ ] verify that it correctly migrates a global installed binary from .sh/.bat to trampoline.
this can be done by following:
using previous pixi:
pixi global install python and then  cargo run -- global install python.
python should be in a working state, and by looking into cat /Users/graf/.pixi/bin/python you should see that is a binary code , not a script anymore
[ ] using following code,  and when running it with global installed python and pressing CTRL-C you should see
CTRL-C caught! Successful termination.

import signal
import time

def signal_handler(sig, frame):
    print("\nCTRL-C caught! Successful termination.")
    exit(0)

# Register the signal handler for SIGINT (CTRL-C)
signal.signal(signal.SIGINT, signal_handler)

print("Press CTRL-C to stop the script.")

# Simulating some work with an infinite loop
try:
    while True:
        time.sleep(1)  # Keeps the script running
except KeyboardInterrupt:
    # You can also handle it here, but we already have the signal handler
    pass

[ ] test if pixi global install behave correctly in different shells

A few thoughts about this approach:
It will bring the following improvements:

Proper CTRL-C handling on Windows
git bash users will not have to append .bat anymore when calling CLI apps
Caching of activation scripts

This is pretty impressive, and I think we should go for it for all platforms.
It will also add complexity:

Migration and binary cleanup will have to be extended
We have to either add a build step to embed the binary or add our first runtime dependency

Things still to solve:

How to ship. I see the following possibilities:

Compile the binary as a pixi task and embed it into the pixi binary (my preferred solution)
Do the same, but with build.rs instead of pixi. That way people don't need pixi to build pixi
Require the binary during runtime (That way we would move away from our single-binary-claim)

At the moment, we just ignore binaries in ~/.pixi/bin. Should we move back to adding a special case for pixi and remove all other binaries we don't know about?
Should we stop support for scripts in ~/.pixi/bin at some point. I say yes, but the question is: when?

Just a few notes:

the activation caching could be done already (by using export / set in the scripts).
We should also already re-create the scripts whenever the environment changes because the activation scripts could change.

The additional build step is indeed the main pain point, and wether we should include it in pixi with something like include_bytes!(...). I could hack further on this, or we can wait until the dust is settled with the new pixi global. Up to you :)
The release build with some size optimizations is 300kB on macOS arm.
I am sure we could get it down a bit more by reimplementing this in C, not using a JSON parser, etc.
When I compress the binary with zstd it shrinks to
./target/release/trampoline : 45.11%   (   361 KiB =>    163 KiB, ./target/release/trampoline.zst)

I removed serde and serde_json:
./target/release/trampoline : 43.09%   (   329 KiB =>    142 KiB, ./target/release/trampoline.zst)

I could hack further on this, or we can wait until the dust is settled with the new pixi global. Up to you :)

As discussed, this is really useful, so let's continue on it.
As soon as the trampoline is usable, we can merge it into a feature branch. That feature branch will be extended until migration & binary cleanup works and tests are added. Then we merge it into main.

I get a warning like this now:
warning: profiles for the non root package will be ignored, specify profiles at the workspace root:
package:   /Users/wolfv/Programs/pixi/crates/pixi_trampoline/Cargo.toml
workspace: /Users/wolfv/Programs/pixi/Cargo.toml
Maybe we can figure out hwo to avoid it?

I tried to run global install ripgrep but it failed with the following:
  × Couldn't install ripgrep
  ╰─▶ 'pixi' is not allowed as exposed name in the map

I don't have pixi in my manifest, but I do have ~/.pixi/bin/pixi.
I think pixi global should ignore all files that are not hard-links to the trampoline.

There are two things that I would like to have tests for

Test that activation scripts are cached
Test that activation scripts are invalidated when necessary

there is already a test for caching of activation scripts ( https://github.com/prefix-dev/pixi/pull/2277/files#diff-25b4f24912cba16497385a2cb46f356069a6c048707ad384237c596310145314R7 )
for invalidation, I will add another one ( I think it should be just caching new set of them when new version of package is installed )

Let's move the json to a subfolder of bin. For examples trampolines.

On linux it all seems to work like it should! The only problem I found was that it would log all the exposed executable s everytime I run pixi global sync:
✔ Exposed executable node20 from environment node20.
✔ Exposed executable pre-commit from environment pre-commit.
✔ Exposed executables from environment python:
   - python
   - python3-config
   - pydoc3.13
   - python3.1
   - idle3.13
   - python3.13-config
   - pydoc3
   - python3
   - python3.13
   - idle3
   - pydoc
✔ Exposed executable nu from environment nushell.
✔ Exposed executable python3100 from environment python310.
✔ Exposed executable pixi0.32 from environment pixi32.
✔ Exposed executables from environment nodejs:
   - corepack
   - npm
   - node
   - npx
✔ Exposed executable hyperfine from environment hyperfine.
✔ Exposed executable npm22 from environment nodejs22.
✔ Exposed executable starship from environment starship.
✔ Exposed executable zoxide from environment zoxide.
✔ Exposed executable jupyter from environment jupyter.
✔ Exposed executable rg from environment ripgrep.
✔ Exposed executable poetry from environment poetry.
✔ Exposed executable scipython from environment science.
✔ Exposed executables from environment pytest:
   - py.test
   - pytest
✔ Exposed executable pixi0.30 from environment pixi30.
✔ Exposed executables from environment ipython:
   - ipython
   - ipython3
✔ Exposed executables from environment uv:
   - uv
   - uvx
✔ Exposed executables from environment ansible:
   - ansible-community
   - ansible
✔ Exposed executable pixi-pack from environment pixi-pack.
✔ Exposed executable asciinema from environment asciinema.
✔ Exposed executable bat from environment bat.
✔ Exposed executable rattler-build from environment rattler-build.
✔ Exposed executable gh from environment gh.
✔ Exposed executable git-lfs from environment git-lfs.
✔ Exposed executable pixi33 from environment pixi33.
✔ Exposed executable snakemake from environment snakemake.
✔ Exposed executable micromamba from environment micromamba.
✔ Exposed executable tree from environment tree.
✔ Exposed executable ruff from environment ruff.
✔ Exposed executable zsh from environment zsh.
✔ Exposed executables from environment vim:
   - rvim
   - xxd
   - view
   - blabla
   - vimdiff
   - vim
   - vimtutor
   - rview
   - ex
✔ Exposed executable node22 from environment node22.

Not sure if that was fixed by something @Hofer-Julian was working on.

Nice find. I don't expect one of my PRs to fix this

Now testing on windows. If I pixi global install git it says that I already have it installed. And also gives me the correct version but that is the "normal" git installed with my microsoft store. Which was not tracked by pixi is this the expected behavior? The old version of pixi would just install it.
Also pixi g sync actually starts updating everything to the latest version. Which is also not what I would expect. It should just be fine with the environment if it matches the manifest state.

On linux it all seems to work like it should! The only problem I found was that it would log all the exposed executable s everytime I run pixi global sync:
✔ Exposed executable node20 from environment node20.
✔ Exposed executable pre-commit from environment pre-commit.
✔ Exposed executables from environment python:
   - python
   - python3-config
   - pydoc3.13
   - python3.1
   - idle3.13
   - python3.13-config
   - pydoc3
   - python3
   - python3.13
   - idle3
   - pydoc
✔ Exposed executable nu from environment nushell.
✔ Exposed executable python3100 from environment python310.
✔ Exposed executable pixi0.32 from environment pixi32.
✔ Exposed executables from environment nodejs:
   - corepack
   - npm
   - node
   - npx
✔ Exposed executable hyperfine from environment hyperfine.
✔ Exposed executable npm22 from environment nodejs22.
✔ Exposed executable starship from environment starship.
✔ Exposed executable zoxide from environment zoxide.
✔ Exposed executable jupyter from environment jupyter.
✔ Exposed executable rg from environment ripgrep.
✔ Exposed executable poetry from environment poetry.
✔ Exposed executable scipython from environment science.
✔ Exposed executables from environment pytest:
   - py.test
   - pytest
✔ Exposed executable pixi0.30 from environment pixi30.
✔ Exposed executables from environment ipython:
   - ipython
   - ipython3
✔ Exposed executables from environment uv:
   - uv
   - uvx
✔ Exposed executables from environment ansible:
   - ansible-community
   - ansible
✔ Exposed executable pixi-pack from environment pixi-pack.
✔ Exposed executable asciinema from environment asciinema.
✔ Exposed executable bat from environment bat.
✔ Exposed executable rattler-build from environment rattler-build.
✔ Exposed executable gh from environment gh.
✔ Exposed executable git-lfs from environment git-lfs.
✔ Exposed executable pixi33 from environment pixi33.
✔ Exposed executable snakemake from environment snakemake.
✔ Exposed executable micromamba from environment micromamba.
✔ Exposed executable tree from environment tree.
✔ Exposed executable ruff from environment ruff.
✔ Exposed executable zsh from environment zsh.
✔ Exposed executables from environment vim:
   - rvim
   - xxd
   - view
   - blabla
   - vimdiff
   - vim
   - vimtutor
   - rview
   - ex
✔ Exposed executable node22 from environment node22.

Not sure if that was fixed by something @Hofer-Julian was working on.

fixed this ✔


Google\Service\Datastore\ReadOnly class is a parse error in PHP 8.1

Environment details

OS: Ubuntu 20.04 (in WSL)
PHP version: 8.1.0
Package name and version: google/apiclient v2.12.1

Steps to reproduce

Upgrade to PHP 8.1

A class named ReadOnly is no longer possible in PHP 8.1 as readonly is now a reserved word.

@dwsupplee @bshaffer for vis

This is tricky as renaming ReadOnly will constitute a BC-breaking change.

This has been fixed in https://github.com/googleapis/google-api-php-client-services/pull/925 and the new clients have been released and tagged in https://github.com/googleapis/google-api-php-client-services/releases/tag/v0.245.0


fixed sec issue for github.com/coreos/prometheus-operator  package

https://github.ibm.com/IBMPrivateCloud/roadmap/issues/59409

/lgtm


Nimble blecent_test.py is missing after 5.1.1 (IDFGH-11685)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hello, I'm working through the BLE Nimble Examples and the README directs my to use the python utility blecent_test.py, but it has been removed from the codebase in v5.1.1.  Is there a reason it was removed?  Is there an alternative?  Thank you.

The newer IDF version deprecated the TTFW framework. This is why files referring to old framework were removed.

I see, thank you.  Is there a new framework that is used now?  Is there a different example project I should be following?  Thanks for your time.

I would like to get an example project running where I can communicate between a host and two peripherals.  Thank you.

pytest is the new framework that is to be used.  here are the sample example files you can refer and develop on top of it as per your usecase / requirement.
pytest_bleprph.txt
pytest_blecent.txt

thank you!!!