QA Programs script updates: Auto-assign Super Admins Tolaland role and permissions, auto-generate test users

Issue
Whenever we re-run the QA script, Super Admins need to re-do their permissions. To save time, it'd be nice if the script could take care of it.
Acceptance criteria
When we run the Create QA Programs script...

[ ] 1. All Super Admins are automatically assigned the Basic Admin role in beautiful Tolaland.

[ ] 2. Super Admins automatically get access to all programs in Tolaland. (Not sure if we get this for free, or need to handle it separately.)

[ ] 3. Test users are automatically generated with the same easy-to-type password for all of them.

username
MC employee?
base country
role
program permissions
notes

mc-low
yes
United States
User
LOW for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Okta login

mc-medium
yes
United States
User
MEDIUM for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Okta login

mc-high
yes
United States
User
HIGH for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Okta login

mc-basicadmin
yes
United States
Basic Admin
HIGH for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Okta login, Basic Admin permissions for all countries, in addition to High permissions for assigned programs

external-low
no
N/A
Individual programs only
LOW for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Django username and password

external-medium
no
N/A
Individual programs only
MEDIUM for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Django username and password

external-high
no
N/A
Individual programs only
HIGH for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Django username and password

gmail-low
no
N/A
Individual programs only
LOW for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Gmail username and password

gmail-medium
no
N/A
Individual programs only
MEDIUM for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Gmail username and password

gmail-high
no
N/A
Individual programs only
HIGH for all programs in Afghanistan, Haiti, Jordan, Tolaland, United States
Gmail username and password

demo1
yes
Ethiopia
Individual programs only
LOW for all programs in Ethiopia
Simulating a Mercy Corps regular user, can be set to Admin if the demo-er wants to show Admin functionality.

demo2
no
N/A
Individual programs only
MEDIUM only for program Collaboration in Cross-Border Areas in Ethiopia
Gmail username and password

demo3
no
N/A
Individual programs only
HIGH only for program Collaboration in Cross-Border Areas in Ethiopia
Django username and password

@hannalcamp We are going to automatically generate test users when we refresh QA (and maybe Dev2?) servers, so that we don't have to manually set them up again and again when we want to test anything related to roles and permissions.
Can you please take a look at the table and add any test users I missed, that would be useful to have?

My sense is we could make life simpler for ourselves if we name the 3 MC/External/Gmail accounts numerically instead of with user roles as part of the name itself. When demo-ing I typically pick one account to work with and modify the roles/programs on it to show how that works, rather than switching between multiple pre-made accounts.

@hannalcamp I'm having trouble understanding your recommendations -- which accounts they refer to, how you'd differentiate them if they're just numbered, and what exactly you have in mind for them. I think that's because the demo use case is very different from the testing use case. The test users I outlined are specific to QA/testing and it's important that their roles and permissions remain stable.
It sounds like we ALSO need a few demo users whose permissions you can manipulate as part of your demo'ing -- and that the requirements for those are different than the test users. I just added three rows for demo users at the bottom of the table. Can you fill those in, and add any others you'd like?
Regarding your suggestion of making Basic Admins LOW on all programs because that's the out-of-the-box default... In practice, do you expect Basic Admins to keep their own program permissions low, given their admin responsibilities and interests? For testing purposes, I'm trying to simulate what their actual permissions are likely to be, in the long run.

@jennyhavah Got it, sorry for the lack of clarity. I think you're right that I'm focusing on demo rather than test. I think we might therefore want to keep all of the test accounts as you detail and stable for testing, and also create three Demo users, one each for the different type of login. Those might at any point have a number of programs and roles. I'll add them.
On Basic Admins, I think it varies. Some Admins in my experience are extremely involved and Program Managers or MEL managers themselves, so yes they'll set all their permissions to High, most likely. But some admins are more general country persons, like IT. That said, I think the distribution is probably 75-25, in favor of the former case (program-involved admins). So I think it's fine to leave yours as is.

Also updated your table to reflect non-MC users should only have Individual programs only as their Country role, not User.

@hannalcamp and @jennyhavah, can you assign existing test users to each of these roles.  I suspect that we don't have enough existing logins to cover all of these users, so we may need to request/create new Okta/Gmail accounts.  We should probably do this mapping in Slack since this is a public board.

@sanjuroj I don't understand the request, but hopefully @hannalcamp  will know what you're asking for.

@sanjuroj I think you mean we should add a column to the table detailing which already existing emails go with which roles, so we know which emails need to be created?

Yep, that's what I mean.

@jennyhavah I added the email addresses I know of that we have credentials for documented on Slack - can you add others you might have set up you'd like to continue using? We can add more then once we've organized all the ones we know of.

@jennyhavah Scratch that, I'm deleting the emails and moving this over to slack

@jennyhavah I'm curious if there are any other changes that we want to include with these updates to the QA program.  One possibility is adding old-style levels to all of the personal programs and maybe adding another special program that doesn't have old-style levels to simulate an older program.  Is some combo of those changes of interest?  Anything else?

@sanjuroj I did notice that the old levels had gone missing from the QA programs. Ideally, those programs would have OldLevels AND would also have their automatically generated indicators assigned to the automatically-generated results framework.
Second best would be to just assign them to the RF and not worry about also giving them OldLevels.
(Thinking about what we'll want to test going forward... We do have a pretty large sampling of old programs in QA with OldLevels, that we can use to test migration related issues.)

@jennyhavah Any problem with having mc-basicadmin be an external user instead of an Okta user? They can still be part of the MC org and have basic admin rights, it just means we don't have to ask for a 4th Okta login.

@sanjuroj For real users, I'm pretty sure we've put rules in place preventing any external user from becoming a Basic Admin and accessing that set of features. So I wonder if in bypassing those rules to avoid requesting another Okta login, we might inadvertently skew QA testing in certain scenarios.

In the UI, I just tried to make a non-Okta user part of the MC org and a Basic Admin and it worked, so I think it is possible.  It's not possible to make someone in an org that is not MC a basic admin.

Ah, maybe that's to enable temporary MC employees to be Basic Admins without needing an MC email. Though.... It seems odd to me that someone would have that level of responsibility but not an MC email account.
@hannalcamp Just out of caution, can you confirm that it's ok for someone without an OKTA account (and presumably without an MC email account) to be a Basic Admin, as long as their organization is set to MC?

Since only a Super Admin can set an organization to MC, my vision is that
it would be done only under special circumstances, if we had a new employee
or someone technically independent but really closely associated to us who
had a need to manage a country. I think it would be incredibly rare and it
would require the involvement of a Super Admin to make it happen. I think
it's fine as is, but I don't think it would break anything to restrict to
only MC addesses - it's just that organization was to me a logical way of
restricting.
On Wed, Jul 24, 2019 at 10:32 AM jennyhavah<EMAIL_ADDRESS>wrote:

Ah, maybe that's to enable temporary MC employees to be Basic Admins
without needing an MC email. Though.... It seems odd to me that someone
would have that level of responsibility but not an MC email account.
@hannalcamp https://github.com/hannalcamp Just out of caution, can you
confirm that it's ok for someone without an OKTA account (and presumably
without an MC email account) to be a Basic Admin, as long as their
organization is set to MC?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mercycorps/TolaActivity/issues/1550?email_source=notifications&email_token=AJCCLEBHUIKKT3QQRU64YTDQBB73XA5CNFSM4HLDR3KKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2W4U7Y#issuecomment-514706047,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJCCLEDFTHBIOYY67ORRIA3QBB73XANCNFSM4HLDR3KA
.

--
Hanna Camp
Senior Advisor, Technology for Development
MERCY CORPS
cell<PHONE_NUMBER> | skype hannalcamp
Denver CO 80209 | USA https://www.mercycorps.org/email-signature-creator#
Powered by the belief that a better world is possible.
Join us at mercycorps.org https://www.mercycorps.org/
Facebook https://facebook.com/mercycorps | Twitter
https://twitter.com/mercycorps

In theory, it shouldn't matter how the user gets to have this access, once they are given a basic admin role, it should function just like any other user with a basic admin role.  However, another possibility is to give the mc-high user a Basic Admin role in one of the countries they're assigned to.  No additional Okta accounts needed and it's possible to test a high role with and without being a basic admin as well.
@jennyhavah Another, completely separate, question:  assigning MC users all of the programs in the countries listed in the program permissions column above is most easily accomplished by giving them country level access.  This is not possible for the non-MC users. I'm assuming you want them to have program-level access to all programs in the countries you mentioned (i.e. if you created a new program in those countries, the non-MC users would not have access to it).  If this is not the case, let me know.

@sanjuroj For QA purposes, I think it's important -- as much as possible -- to mimic the actual roles and permissions enforced by the system -- even for fake users.
Non-MC users should never have country level access granting them automatic access to all new programs in the country. So no, I wouldn't expect (or want) our non-MC fake users to have automatic access to all new programs. If I need to make sure I'm looking at all programs in a country for QA purposes, I ought to log in as an MC user.

@jennyhavah Rather than have a specific admin user, I added mc-high as a basic-admin for Tolaland, but no other countries (though still a 'high' user for all programs listed).  I think between this and the external-high user, it should be possible to check all of the permutations of permissions?  I'd really prefer not to add another Okta account, but if there is ground you think we're not covering, we can do so.

@sanjuroj I see some risk in combining scenarios scenarios -- the basic admin and the high -- that would lead me to continue manually creating accounts if they're not part of the QA script.
It's all about the edge cases -- for example, a basic admin somehow getting access to features and actions despite not having Medium or High access. Or a High user not being able to do something they should be able to do because we inadvertently created a dependency on that role also being a basic admin. Stuff like that.
I'm curious why there's a concern about the number of Okta accounts. Is the concern financial -- a per license fee -- or something else?

Limiting the number of Okta accounts is just about keeping track of what all of them are for.  The TolaData Test account writ large.  Tracking which ones are used for what and how they're being used is inevitably messy.
Which edge cases are you missing with this set of users? A high user who only has basic admin access to a limited number of countries can still be used to test high (non-admin) permissions by using a country where that user doesn't have admin rights.  The other non-MC high users can be  used as well.  One thing to keep in mind is that once you're logged in, how you logged in is not a factor in setting permissions.  So a non-MC high user is the same as an MC high user.

That makes sense, @sanjuroj. Let's go with your recommendation, and we can always revisit later if I happen to stumble on a bunch of use case scenarios we can't test for some reason.

Note to self: Report only bugs for this ticket -- adjustments / new QA programs in separate ticket.

@sanjuroj Before I test this, just double checking: Have you run this script on QA since completing this ticket?

@jennyhavah I don't think it has been run on QA yet.  Is it ok to refresh the whole database?  Or should I just recreate the QA programs.

Whichever is easier is fine by me... Can't really think of a downside to refreshing the whole database. Maybe just give everyone a heads up on Slack first and ask if anyone is in the middle of testing something with the existing data...

@jennyhavah  Is it ok if the admin user just has a Django login (we can make a Django login an admin user)?  So you wouldn't be able to log in using Okta, but it would still be a separate admin user.

@sanjuroj That's fine -- I've been logging in using the Django login/password combo for all test users.

New pre-Satsuma program is created. All other QA programs appear to be post-Satsuma. I'm able to login as external-whatever and gmail-whatever. Passing this ticket and will start a new ticket for any new QA program requests.


throw error when using module concatenation and cacheUnaffected

What kind of change does this PR introduce?
feature

Did you add tests for your changes?
no

Does this PR introduce a breaking change?
nothing

What needs to be documented once your changes are merged?
nothing

Thanks


Add the Headlamp article as a resource

There were a few articles hosted on weave.works but they are not accessible anymore, so had to be removed.
I am testing this feature to be sure I know how it works, since we do not have any live examples today!
(I'd like to add this one too:)

https://medium.com/@mohamednoureldinn/fluxcd-azure-devops-oidc-authentication-916cc7bfe11f

We need to add thumbnails and/or description text in order to use this feature effectively. I wonder if there is a streamlined way to do this.


Feature Importance

More explanation needed on Feature_importance() function. We are unable to understand why the fairness measure will change to find the feature importance.
Also, the fairness conclusion is not tallying with the result in the attached file(chosen Threshold is 80).

we use leave-one-covariate-out to justify the use of protected variables (refer to phase 1 https://www.mas.gov.sg/-/media/MAS/News/Media-Releases/2021/Veritas-Document-2-FEAT-Fairness-Principles-Assessment-Case-Studies.pdf)
e.g. after removing SEX, we retrain the model and measure the prediction to see how balanced_acc and equal_opp changes compared to the original model.
widget shows the fairness conclusion for the original model. the "fair conclusion" column in the output of Feature_importance() shows the change of conclusion, i.e. the term before "to" is for original model and the term after is for retrained model, e.g. "fair to unfair" means original model is fair and retrained model is unfair.


gazebo_ros/node.hpp build errors

i believe the following lines require the addition of  ${gazebo_ros_INCLUDE_DIRS}
https://github.com/osrf/traffic_editor/blob/master/building_gazebo_plugins/CMakeLists.txt#L60
https://github.com/osrf/traffic_editor/blob/master/building_gazebo_plugins/CMakeLists.txt#L99
https://github.com/osrf/rmf_demos/blob/master/rmf_gazebo_plugins/CMakeLists.txt#L56
https://github.com/osrf/rmf_demos/blob/master/rmf_gazebo_plugins/CMakeLists.txt#L82
https://github.com/osrf/rmf_demos/blob/master/rmf_gazebo_plugins/CMakeLists.txt#L108

Otherwise these errors seem to appear non-deterministically :
11:30

--- stderr: rmf_gazebo_plugins
/home/bhan/rmf_integration_challenge/challenge_trials_workspace/src/rmf/rmf_demos/rmf_gazebo_plugins/src/readonly.cpp:22:10: fatal error: gazebo_ros/node.hpp: No such file or directory
 #include <gazebo_ros/node.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/readonly.dir/src/readonly.cpp.o] Error 1
make[1]: *** [CMakeFiles/readonly.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
/home/bhan/rmf_integration_challenge/challenge_trials_workspace/src/rmf/rmf_demos/rmf_gazebo_plugins/src/TeleportDispenser.cpp:27:10: fatal error: gazebo_ros/node.hpp: No such file or directory
 #include <gazebo_ros/node.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/teleport_dispenser.dir/src/TeleportDispenser.cpp.o] Error 1
make[1]: *** [CMakeFiles/teleport_dispenser.dir/all] Error 2
/home/bhan/rmf_integration_challenge/challenge_trials_workspace/src/rmf/rmf_demos/rmf_gazebo_plugins/src/TeleportIngestor.cpp:27:10: fatal error: gazebo_ros/node.hpp: No such file or directory
 #include <gazebo_ros/node.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.

This affects both master and develop.

Can you provide some details on how you're building? Are you just using plain colcon build or are you passing certain arguments to it? I can't think of any way that a normal colcon build can have non-deterministic build failures.

Sorry, that was a bad description, I meant to say the build fails deterministically, for my given machine. However, for other machines I have, the packages successfully build deterministically.
I'm unable to provide anything now, but hopefully in a few hours.

@cnboonhan94 any chance you had installed ros2 from source earlier on the machine where the building is failing?

If that is the case, could you check if running this command resolves the problem in your machine.
sudo apt install ros-eloquent-gazebo-ros*

Using an Eloquent Version built from source could be the reason, it does seem consistent. However, sudo apt install ros-eloquent-gazebo-ros* did not seem to help. I wonder if you would have to source stock Eloquent. My steps:
# In workspace
# source Eloquent when built from source
colcon build # fails
sudo apt install ros-eloquent-gazebo-ros*
colcon build # also fails

did you source the binary-installed Eloquent (/opt/ros/eloquent/setup.bash) before building Eloquent from source? I believe the apt installed package won't be found unless the binary-installation was sourced at the start

If sourcing the debian package versions of the eloquent overlay works when sourcing a local build fails, then that would indicate something is wrong with either the source code or with colcon (or with how colcon is being used).
If explicitly including the Gazebo headers will allow our packages to build successfully on top of local builds of eloquent, then I think we should go ahead and do that, in parallel to identifying why there would be an inconsistency between the local build vs the pre-built packages.

We should consider making a minimum example that demonstrates the problem and opening an issue on the gazebo_ros repo.

to answer @aaronchongth , i didnt source binary Eloquent before building. I will try to get this example when i best can.

Sorry for the long delay. I did some further experiments and i get the following results, using a minimal setup of building traffic-editor with rmf_core:
Reproducible Steps

Install ros-eloquent-desktop using this.
Install gazebo_ros_pkgs binary dependencies using this.
Download Eloquent sources using this in $HOME/source_eloquent_ws
Create a minimal build workspace containing rmf-core and traffic-editor and install its dependencies, in $HOME/debug_ws.

Hashes:

traffic_editor: f8498a9c642926d084d4716ef63c45ec8155d1dd
rmf_core: 4099921bea576c2fde87c3dc852cc4d8f86a5d1a

All builds are clean: deleting the install build log folders before building.
Build with Binary Eloquent and binary gazebo_ros_pkgs:  Success
source /opt/ros/eloquent/setup.bash
cd $HOME/debug_ws
colcon build

Build with Build-From-Source Eloquent and binary gazebo_ros_pkgs: Failed
cd $HOME/source_eloquent_ws
colcon build

source $HOME/source_eloquent_ws/install/setup.bash
cd $HOME/debug_ws
colcon build

Error Messages:
CMake Error at CMakeLists.txt:26 (find_package):
  By not providing "Findgazebo_ros.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "gazebo_ros", but CMake did not find one.

  Could not find a package configuration file provided by "gazebo_ros" with
  any of the following names:

    gazebo_rosConfig.cmake
    gazebo_ros-config.cmake

  Add the installation prefix of "gazebo_ros" to CMAKE_PREFIX_PATH or set
  "gazebo_ros_DIR" to a directory containing one of the above files.  If
  "gazebo_ros" provides a separate development package or SDK, be sure it has
  been installed.

Build with Build-From-Source Eloquent and Build-From-Source gazebo_ros_pkgs: Failed
cd $HOME/source_eloquent_ws
colcon build

source $HOME/source_eloquent_ws/install/setup.bash

cd $HOME/debug_ws
# Add gazebo_ros_pkgs source files following http://gazebosim.org/tutorials?tut=ros2_installing&cat=connect_ros
colcon build

Error Messages:
--- stderr: building_gazebo_plugins
/home/bhan/dev/debug_ws/src/traffic_editor/building_gazebo_plugins/src/door.cpp:5:10: fatal error: gazebo_ros/node.hpp: No such file or directory
 #include <gazebo_ros/node.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/door.dir/src/door.cpp.o] Error 1
make[1]: *** [CMakeFiles/door.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
/home/bhan/dev/debug_ws/src/traffic_editor/building_gazebo_plugins/src/slotcar.cpp:5:10: fatal error: gazebo_ros/node.hpp: No such file or directory
 #include <gazebo_ros/node.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/slotcar.dir/src/slotcar.cpp.o] Error 1
make[1]: *** [CMakeFiles/slotcar.dir/all] Error 2
make: *** [all] Error 2
---

Source Binary Eloquent, then Build Eloquent from Source, then use only Build-From-Source Eloquent: Failed
# Terminal 1
source /opt/ros/eloquent/setup.bash
cd $HOME/source_eloquent_ws
colcon build

# Terminal 2
source $HOME/source_eloquent_ws/install/setup.bash
cd $HOME/debug_ws
colcon build

Error Messages:
/home/bhan/dev/debug_ws/src/traffic_editor/building_gazebo_plugins/src/slotcar.cpp:5:10: fatal error: gazebo_ros/node.hpp: No such file or directory
 #include <gazebo_ros/node.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/slotcar.dir/src/slotcar.cpp.o] Error 1
make[1]: *** [CMakeFiles/slotcar.dir/all] Error 2
make: *** [all] Error 2
---
Failed   <<< building_gazebo_plugins    [ Exited with code 2 ]
Aborted  <<< rmf_task_msgs
Aborted  <<< traffic_editor
Aborted  <<< rmf_traffic_msgs
Aborted  <<< rmf_traffic

Install extra gazebo_ros packages, Source Binary Eloquent, then Build Eloquent from Source, then use Build-From-Source Eloquent: Failed
# Terminal 1
sudo apt install ros-eloquent-gazebo-ros*
source /opt/ros/eloquent/setup.bash
cd $HOME/source_eloquent_ws
colcon build

# Terminal 2
source $HOME/source_eloquent_ws/install/setup.bash
cd $HOME/debug_ws
colcon build

Error Messages:
--- stderr: building_gazebo_plugins
/home/bhan/dev/debug_ws/src/traffic_editor/building_gazebo_plugins/src/slotcar.cpp:5:10: fatal error: gazebo_ros/node.hpp: No such file or directory
 #include <gazebo_ros/node.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/slotcar.dir/src/slotcar.cpp.o] Error 1
make[1]: *** [CMakeFiles/slotcar.dir/all] Error 2
make: *** [all] Error 2
---
Failed   <<< building_gazebo_plugins    [ Exited with code 2 ]
Aborted  <<< traffic_editor
Aborted  <<< rmf_traffic
Aborted  <<< rmf_traffic_msgs

Would like to know if these are all permutations that i should try. I am happy to proceed with an issue ticket otherwise.

Any update on this issue? i am having same problem in colcon build the rmf_demos package.
i have the same environment as @cnboonhan94 described:

install eloquent via debian packages
follow the setup guide and compilation instruction as described in readme
error in colcon build:

--- stderr: building_gazebo_plugins
/home/prd-robotics/ROS/rmf_demos_ws/src/rmf/traffic_editor/building_gazebo_plugins/src/door.cpp:5:10: fatal error: gazebo_ros/node.hpp: No such file or directory
 #include <gazebo_ros/node.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/door.dir/src/door.cpp.o] Error 1
make[1]: *** [CMakeFiles/door.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
/home/prd-robotics/ROS/rmf_demos_ws/src/rmf/traffic_editor/building_gazebo_plugins/src/slotcar.cpp:5:10: fatal error: gazebo_ros/node.hpp: No such file or directory
 #include <gazebo_ros/node.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/slotcar.dir/src/slotcar.cpp.o] Error 1
make[1]: *** [CMakeFiles/slotcar.dir/all] Error 2
make: *** [all] Error 2

@simk0024 I faced the same issue and have the same setup as yours (using eloquent debian). As mentioned previously, sudo apt install ros-eloquent-gazebo-ros* resolves this.
As for the case of "build-from-source" eloquent, I havn't attempted it yet. But since you are using eloquent deb, this might work.

should be handled by https://github.com/osrf/rmf_demos/pull/106


Lost container  static IP setting when swarm rescheduling

I create a private network by bridge on two swarm nodes(node01/node02) :
docker network create \
  --driver=bridge --subnet=<IP_ADDRESS>/24 --ip-range=<IP_ADDRESS>/24 \
  --gateway=<IP_ADDRESS> \
  -o "com.docker.network.bridge.name"="br0" br0

run a container by swarm manager:
docker -H $SWARM_MANAGER \
     run -d -P  --name dahuang002  --hostname dahuang002 \
     --ip <IP_ADDRESS> --net br0 \
     -e reschedule:on-node-failure --restart=always   my-nginx:v1

of course , swarm lunch a container get static IP <IP_ADDRESS> on node01 in my envirement , perfect work .

Container dahuang002 start on node02 as I want，but it lost static IP。
Inspect container dahuang002，it got another static IP <IP_ADDRESS>，lost the parameter --IP config.

Any Idea ?

I have this problem, too.

@killkill @dvenza
Can you please put here the output for network ls?
Those two bridges are not the same network they just have the same name do they not?


Add support for URL encode/decode methods added in Java 10

Java 10 added versions of URL encode/decode that take the Charset instance as an argument rather than the charset name. This means the user of these methods no longer has to handle the UnsupportedEncodingException (since the presence of a Charset instance indicates the character encoding is known to exist).
This method was already present in the URLDecoder, but not yet in the URLEncoder.

Sorry, I forgot to merge this PR. However, you added commit that is not related to initial purpose of PR. Please, remove it so that I can squash commits related to URL


Use destination as a query param, instead of target_url

Also,

if user attempts goto login page directly, then after authentication, redirect it to default service
removed some of the benign operations executed in the Future contexts

Current coverage is 95.19%

Merging #141 into master will increase coverage by +0.71% as of be7bd0d

@@            master    #141   diff @@
======================================
  Files           36      36
  Stmts          997     999     +2
  Branches        42      42
  Methods          0       0
======================================
+ Hit            942     951     +9
  Partial          0       0
+ Missed          55      48     -7

Review entire Coverage Diff as of be7bd0d

Powered by Codecov. Updated on successful CI builds.


update POST response code

production testing shows that this returns a 200, not a 201.
Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @jacobmovingfwd,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Hello @jacobmovingfwd,Thanks again for the PR!                                         We noticed that you have earned 1 out of the 5 points needed to receive glorious SendGrid Hacktoberfest swag.                                         Please take a moment to checkout this link to find more issues to get you past the required threshold.                                         Also, please be sure that you have officially registered here.                                         Thank you and Happy Hacktobering!                                         Team SendGrid DX

Hello @jacobmovingfwd,Thanks again for the PR!                                         You have earned 1 out of the 5 points needed to receive glorious SendGrid Hacktoberfest swag.                                         Please take a moment to checkout this link to find more issues to get you past the required threshold or to simply continue the celebration.                                         Also, please be sure you have officially registered with us here by November 1, 2018 to qualify.                                         If you have any questions you can email us at<EMAIL_ADDRESS>                                        Thank you and Happy Hacktobering!                                         Team SendGrid


Should we add a "non_textual_categories" key in config?

"labels": ...
"non_textual_categories": [
        "Figure", "Table", "Algorithm"
    ]
"relations": ...
}

It would be interesting to add higher-level tags as well. Like document type tag.


Ethan: Watch propccrack.net

Ethan requests the watch of the watch_keyword propccrack\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

propccrack\.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


emacs template

AngularJS templates that follow these styles and guidelines.

    M-x ngcontroller // creates an Angular controller
    M-x ngdirective // creates an Angular directive
    M-x ngfactory // creates an Angular factory
    M-x ngmodule // creates an Angular module

please revise to reflect what the sublime snippets do, move to a emacs folder under assets, and update the PR and I will merge

I'd like to add these but it cannot be merged now. Can you update this and make a new PR? Notice that it would be style 255 now

wow, sorry i didnt get to this. id like to pull it in. can you update so we can merge?

going to close this due to unmergable. if someone wants to get it later, go for it


I don't understand how it is work

I try to run it in GIT and Phyton 3.6 but every command is not found

Install git from here.
Install Python from here.


HDDS-6728. Refactor getRatisRoles of SCM

What changes were proposed in this pull request?
The current logic to decide the LEADER of SCM is to check if the RaftPeer is local, https://github.com/apache/ozone/blob/master/hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/ha/SCMRatisServerImpl.java#L268
I assuem this is because the "scm roles" requests are forwarded to the LEADER SCM, so the invoker is always the leader, thus "isLocal" is used to decide which SCM is LEADER.
But in SCM UI, the "SCM HA (roles)" information are retrived by invoking "getRatisRoles" by each SCM, not forwarded to the LEADER SCM, thus each SCM will consider itself as the LEADER in UI.
This ticket is to fix this issue.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6728
How was this patch tested?
unit test.

@adoroszlai @bharatviswa504 @ghuangups Could you help to review this PR?

@adoroszlai Thanks for the review.
I think #3144 haven't fixed the root cause until @ChenSammi 's comment is fulfilled.
Since with "isLocal" to check the leadership, Followers will still think they are the leader, only in UI we covered it by removing the strings.

I think #3144 haven't fixed the root cause until @ChenSammi 's comment is fulfilled.

Correct, that's why it's not merged yet. ;)

Sure, I'll mark this ticket as replicated.

@sadanand48 would you like to take a look?

Thanks @symious for the fix, @sadanand48 for the review.


Kyverno Adapter: Occurs Index Out of Range

Error index out of range when trying to access the first element due to OwnerReferences being empty in the kyverno policy applied by default.
When trying to access kcp.OwnerReferences[0], the issue occurred because the OwnerReferences slice could be empty, but we tried to access it directly without checking.

Hi @b0m313 could you please tell me the steps to reproduce this error?

I can reproduce this, thanks @b0m313 for opening the ticket!

When trying to access kcp.OwnerReferences[0], the issue occurred because the OwnerReferences slice could be empty

Right.
Here is the root cause.
https://github.com/5GSEC/nimbus/blob/d6cf41614c9833c645f015dcd4ba148aaad11d11/pkg/adapter/nimbus-kyverno/manager/manager.go#L271
To reproduce

Run any adapter,
Create a policy by hand i.e., without any owners,
Apply a SI & SIB

and then the adapter crashes due to accessing the first element of empty ownerrefs slice.


Configuration import/export

It would be useful to import and export schema and test configuration (variables, labels, transformers...) to a file.

Implemented in 5e9533b6d297893319d7f41d6bd88dee86d66b2a, 350693c0f9670630de10a300721f1da605bf3207, bd5ff8c2134d6013169e4fa909021a836a6aa568 and 2f424cd4a9cbbf04a779d0430cb80e31a7fa7f81


compile error: bool KCFTracker::createHanningMats() in kcftracker.cpp have no return value

hi,
compile error: bool KCFTracker::createHanningMats() in kcftracker.cpp have no return value .

Thanks for pointing that, I made some changes to that function and I forgot to change the type. KCFTracker::createHanningMats() is now void.


More companies

There are some companies that might be remote and have offered one job and have been included in this list almost by error

Thanks @dougaitken! I caused a merge conflict :( Mind resolving?

Psht, I removed Coupa as well so that should resolve #156 / #154
:shipit:

Fantastic! Thanks so much!!


Toasts instead of error-texts

fixes #416
fixes #417
Also changed for projectspage & state history page

Codecov Report

Merging #444 (c28950c) into develop (cf5c309) will decrease coverage by 0.37923%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##             develop        #444         +/-   ##
===================================================
- Coverage   96.23517%   95.85594%   -0.37923%
===================================================
  Files             81          82          +1
  Lines           1939        2027         +88
===================================================
+ Hits            1866        1943         +77
- Misses            73          84         +11

Impacted Files
Coverage Δ

backend/src/app/routers/editions/editions.py
80.43478% <0.00000%> (-19.56522%)
:arrow_down:

backend/src/database/crud/projects.py
77.41935% <0.00000%> (-2.29080%)
:arrow_down:

backend/src/app/utils/dependencies.py
83.90805% <0.00000%> (-1.63412%)
:arrow_down:

backend/src/app/app.py
100.00000% <0.00000%> (ø)

backend/src/database/models.py
100.00000% <0.00000%> (ø)

backend/src/database/crud/projects_students.py
100.00000% <0.00000%> (ø)

...kend/src/app/routers/editions/projects/projects.py
92.68293% <0.00000%> (ø)

...kend/src/app/routers/editions/students/students.py
100.00000% <0.00000%> (ø)

...uters/editions/students/suggestions/suggestions.py
100.00000% <0.00000%> (ø)

...rs/editions/projects/students/projects_students.py
100.00000% <0.00000%> (ø)

... and 1 more

Instead of using try catch blocks you can do toast.promise
https://fkhadra.github.io/react-toastify/promise

Great catch, the promise toasts are fancy as hell.


Instructions for rolling the kerberos key need to be updated

The first step in the instructions for "rolling the kerberos key" sends the audience to download the AzureAD powershell module. This module does NOT contain the commandlets listed in subsequent steps.
These commandlets are found in Microsoft Azure Active Directory Connect https://www.microsoft.com/en-us/download/details.aspx?id=47594
which is an MSI that installs more than the powershell module(s). Also, it only runs on Server OS so the commandlets cannot be run from a workstation.

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

ID: 9eb97eff-d72e-ffa6-1365-5419e93ed82a
Version Independent ID: 5c8b677b-f4cd-0bb5-c7d6-9b1ef903dad4
Content: Azure AD Connect: Seamless Single Sign-On - Frequently asked questions
Content Source: articles/active-directory/hybrid/how-to-connect-sso-faq.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@davyyd  Thanks for your feedback! We will investigate and update as appropriate.

@davyyd Thank you for your query. I will answer your queries one by one.

The first step in the instructions for "rolling the kerberos key" sends the audience to download the AzureAD powershell module. This module does NOT contain the commandlets listed in subsequent steps.

We completely agree to what you are saying about the Azure AD module not containing the cmdlets related to AzureADSSO.psd1 module because this module is part of AAD connect powershell modules which gets installed along with Azure AD connect MSI . However we ask to install Azure AD module first because the  AAD Seamless SSO module AzureADSSO.psd1 is dependent on the Azure AD module for operation of rolling over Kerberos Keys.

These commandlets are found in Microsoft Azure Active Directory Connect  which is an MSI that installs more than the powershell module(s). Also, it only runs on Server OS so the commandlets cannot be run from a workstation.

Yes the cmdlets are found in Azure AD connect and can only be run on the server where azure AD connect is already installed and running. The first line before the step 1 instructions asks the users to follow the steps on the on-premise server where you are already running Azure AD connect . I have quoted that part of the article below.
Follow these steps on the on-premises server where you are running Azure AD Connect:
Step 1. Get list of AD forests where Seamless SSO has been enabled
  - First, download, and install Azure AD PowerShell.
  - Navigate to the '%programfiles%\Microsoft Azure Active Directory Connect' folder.
  - Import the Seamless SSO PowerShell module using this command: 'Import-Module .\AzureADSSO.psd1'.

...

I hope this clarifies any doubts. We will now close this issue. Please tag me or the author @billmath to your reply and we will help you with your queries related to this.
Thank you.


tests: fix misspelled check prefixes

In the rebranch this is an error (lit got more picky), but it also makes sense to fix the tests in the main branch
Also match optional nonnull attributes. They are inserted by the new LLVM (rebranch). It doesn't harm to match those attributes conditionally also in the main branch.
Also fix SILOptimizer/OSLogFullOptTest.swift and re-enable it. rdar://102078974

@swift-ci smoke test

@swift-ci smoke test


Implement RocksStore checkpoints using Rocks Checkpoints

Previously we used Rocks BackupEngine to create backups,
and build our checkpoints from those. That was slow because
backups require copying the full metastore. Checkpoints are
faster because they use hard links instead of copying. With
this change, the time needed to take checkpoints and restore
checkpoints is reduced by 40%.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3020/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3022/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3024/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3025/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3030/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3038/
Test PASSed.

alluxio-bot, merge this please.


feat: Placement Group Support

Fixes #3324
Description
Allows for the configuration of a Placement Group when defining an AWSNodeTemplate resource. Based on existing work by @preflightsiren on PR #4553.
How was this change tested?
Does this change impact docs?

[x] Yes, PR includes docs updates (in progress!)
[ ] Yes, issue opened: #
[ ] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

63 of 85 (74.12%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 82.368%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/operator/operator.go
0
3
0.0%

pkg/controllers/nodeclass/controller.go
10
14
71.43%

pkg/fake/ec2api.go
6
10
60.0%

pkg/providers/amifamily/resolver.go
10
14
71.43%

pkg/providers/placementgroup/placementgroup.go
33
40
82.5%

Files with Coverage Reduction
New Missed Lines
%

pkg/operator/operator.go
1
9.47%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
4975

Relevant Lines:
6040

💛  - Coveralls


Allow Accept Routes

Problem/Motivation
In trying to provide some routing between various networks it would be nice for the add-on to allow me to accept routes so I don't have to send metrics over the open internet.
Expected behavior
Being able to bring up the plugin to Accept Routes from TailScale.
Proposed changes
Add the ability to accept routes from within HomeAssistant so that items can be sent over TailScale.

It accepts the routes on start, so a restart will work:
See: https://github.com/hassio-addons/addon-tailscale/blob/main/tailscale/rootfs/etc/services.d/tailscaled/post#L56

Add the ability to accept routes from within HomeAssistant

From within Home Assistant? If you mean as a switch in HA... This is not an integration. Add-ons don't provide entities.


Run under XWayland

I understand that Wayland is not currently supported, but is it possible to execute alacritty using XWayland?

Try running like this:
WAYLAND_DISPLAY= alacritty

That did the trick, thanks!

We should add this tip to the README until true Wayland support arrives.


phi2 support

llama.cpp now supports the phi2 model by microsoft: phi2 support in llama.cpp
How can we update the fork/implementation/binary of llama.cpp in llmsearch to support this new update?

Hi, this was solved, by updating llama-cpp-python to latest version.


FileTarget rotation is not multiprocess-safe

I found (unfortunately in the hardest way possible - by receiving a useless set of logs from a production issue) that FileTarget rotation is not multiprocess-safe - there may be races between one process checking that rotation is needed, another process performing rotation, yet another process also performing rotation etc.
I implemented a fix in "double-checked locking" style: I use a multiprocess mutex and double-check ShouldAutoArchive within the mutex.
This seems to work fine: I did a test where several instances of an app were constantly writing consecutive numbers to the same log file, with a small rotation threshold (20kb), and I checked that not a
single number was missed.
Without double-checked locking, or without the solution altogether, there were large gaps.
See my implementation in commit https://github.com/jkff/NLog/commit/8399f0467f1fcffb657db3e72c82f8e1748f75c7 .
The fix I introduced has since survived several months of extremely heavy production testing, so I think it should be safe to merge.

@Xharze do you think we should do something with this old issue?

@304NotModified I think we should decide if we want to support multiple processes writing to the same file. By supporting this we decreases performance. I don't think we should support this scenario.

I think also no support. Performance is important and also I think writing multiple processes to the same file isn't a good idea.

So closing for now.

Resolved by #1771


Hide a tab

Version

react-native-router-flux v4.0.0-beta.28
react-native v0.53.0

I have a Tabs Scene and I would like that one of the tabs to be visible only on Android. Is there a propery that I can use to hide a tab?

You can do the trick using https://facebook.github.io/react-native/docs/platform-specific-code.html


use the now generic cloud integrator charm

Issue
Grafana agent needs to be able to write to multiple backends.
Solution
The grafana-cloud-integrator charm has been made more generic to support any endpoint which accepts Prometheus remote writes. This PR contains the changes necessary in this charm to make use of that.

This PR is waiting for https://github.com/canonical/grafana-cloud-integrator/pull/6, to be able to charmcraft fetch-lib the new library.


Doesn't take into account lifecycle prefixes

I am working on a challenge and it repeatedly offers some places that use the lifecycle prefix, and the tasks seem to include those features when they shouldn't
https://maproulette.org/challenge/429/task/496966

Thanks for reporting, @wolfy1339. I'm not quite following the issue, probably due to my inexperience.  Can you provide clarification, perhaps with a screenshot?  Thanks.

There is a node tagged with disused:railway=station. Relevant wiki article on OSM
It probably shoud not match railway=station

Sorry for the late response! This is a problem with the Challenge, not with MapRoulette itself. If the Challenge shows irrelevant tasks, the Challenge owner used an incorrect query. The best step is to contact the challenge owner.


AMD Processors

Hi, does the Azure Kinect work with AMD processors or is it strictly Intel ones?
Thanks

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

ID: 4b679a0f-1dd5-60dd-b6e2-4a7e3341379b
Version Independent ID: 37baf258-c14f-1871-58a3-c642c38cbb34
Content: Azure Kinect Sensor SDK system requirements
Content Source: articles/kinect-dk/system-requirements.md
Product: kinect-dk
GitHub Login: @tesych
Microsoft Alias: tesych

@djesko1 Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@djesko1 , it should work with AMD processors.

@AshokPeddakotla-MSFT please close this issue.


Error code 500 returned in Blocks tab-Bitcoin  and Anchor link

Environment:Testnet
PR:https://github.com/blockstack/explorer/pull/493
User selects the Blocks tab under Explorer:https://explorer-git-feat-microblocks-final-blockstack.vercel.app/block/0x473cdafb9127bf8822a622c660590b76c5c28b29fb3a166345580e077d748aa5?chain=testnet
User selects Bitcoin hash block and also the anchor transaction id
Both threw error 500

@Eshwari007 I think this is expected -- not sure exactly which bitcoin testnet we're using. @zone117x or @lgalabru , is there a better URL for testnet btc blocks?


dbt_project.yml models config not respected within dependencies

I've specified model configurations for the open source quickbooks models that I've created, but when I pull them into a new project and run a compile, all of them are compiled as views. Two models should be created as tables according to the config, but that is not happening. This forces me to copy the configuration into the config of the primary project repo.

just merged in a fix for this! closing


[RFC] Monitoring support

The CE version of mattermost doesn't expose monitoring data.
We use mattermost-docker internaly and we use telegraf/grafana/influxdb for monitoring the all stack.
We extended the docker-compose of that project and add  a telegraf config file.
But our telegraf configuration is very basic.
But it would be great addition for this project to provide out-of the box monitoring.
If the maintainers (@pichouk  and @xcompass) are Okay,  with that proposition, I will propose a basic MVP of that monitoring stack.
My telegraf skills are limited so the help of other contributors is more than welcome.

I disagree to add more containers to the docker-compose.yml because I want it to be the most generic possible.
BUT I am thinking of a way to allow users to propose some contribution examples (and a monitoring example is a good idea). It will be part of the "web image deprecation project", it is stale for now because I'm running out of time but I will work on this as soon as I can.
So I'll let your request open and I will ping you when things will move on, thanks for your proposal :)

We will probably deprecate the use of a docker-compose.yml file in this repository on #366. I'll let you know.


Latest versions are not published to NPM

At the moment, version 0.0.4 is installed via "npm install l2js-client". Later versions are not available.
Taking the fact, that the config was changed in newer versions, it is impossible to run examples from readme  file.
Please, publish fresh versions to npm. :)

Hi @Tamango92  - yes, you are right, I have to publish the latest version, but before that I just want to make sure all breaking changes I did (configuration) will pass some tests.

Lates version is now published.


Code used to generate benchmarks should be collected and documented

At the moment, we are validating CCL against benchmark datafiles generated by a variety of different codes -- mostly ones that were used during the code comparison project. We only keep the datafiles in version control, not the code, meaning that we can't systematically regenerate the benchmarks themselves, e.g. if we wanted to try different sets of cosmological parameters. The codes (versions, settings used etc.) that were used to generate the benchmarks are not documented in CCL either, which makes the whole validation procedure we are relying upon a little opaque.
We should collect the benchmark code together in one place, with run scripts and/or documentation to allow others to regenerate the benchmark files if they want to. If we can't collect all of it, we should at least have specific instructions on how to obtain and run the code, and what settings were used to generate the current set of benchmarks.

If we have the benchmark code available in one place, we can also automate running it for different sets of cosmological parameters. I can then add the data into the VARRIC visualisation tool.

@philbull Would you consider this resolved now? Should we close it?

Resolved with the CCL paper.


i messed windows 10 ltsc with something

i am on windows 10 enterprise ltsc version 1809 os build 17753.973
yesterday, after some update, rdp access stopped working. i had tried to use ini files from here but nothing changed.
i somehow managed to stop remote desktop services in services  and after restart, that is refusing to start back again thowing a error 1067. the processs terminated unexpectedly. windows could not start the remote desktop service on local computer.
RDP check used to show
wrapper state: installed ver <IP_ADDRESS>
service state: started ver. 10.0.17763.771
listener state: not listening {not supported]
now after stopping the service,
service state: stopped

@test2a
[10.0.17763.771-SLInit]
bInitialized.x86 =CD79C
bServerSku.x86 =CD7A0
lMaxUserSessions.x86 =CD7A4
bAppServerAllowed.x86 =CD7AC
bRemoteConnAllowed.x86=CD7B0
bMultimonAllowed.x86 =CD7B4
ulMaxDebugSessions.x86=CD7B8
bFUSEnabled.x86 =CD7BC

bServerSku.x64 =ECAB8
lMaxUserSessions.x64 =ECABC
bAppServerAllowed.x64 =ECAC4
bInitialized.x64 =ECAB4
bRemoteConnAllowed.x64=ECAC8
bMultimonAllowed.x64 =ECACC
ulMaxDebugSessions.x64=ECAD0
bFUSEnabled.x64 =ECAD4

[10.0.17763.771]
LocalOnlyPatch.x86=1
LocalOnlyOffset.x86=AFEB4
LocalOnlyCode.x86=jmpshort
SingleUserPatch.x86=1
SingleUserOffset.x86=4D7F5
SingleUserCode.x86=nop
DefPolicyPatch.x86=1
DefPolicyOffset.x86=4BFF9
DefPolicyCode.x86=CDefPolicy_Query_eax_ecx
SLInitHook.x86=1
SLInitOffset.x86=5B30A
SLInitFunc.x86=New_CSLQuery_Initialize


⚠ Bofrost.es has degraded performance

In 15f86d1, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1407 ms

Resolved: Bofrost.es performance has improved in bee7d8c after 10 minutes.


Tie a transition matrix to a BoxSet?

As it stands, a BoxSet is unordered, so by assigning an ordering, we introduce additional structure.  We do not necessarily need this when constructing a graph (i.e. for computing strongly connected components), but we do need it when computing a transition (probability) matrix.  The problem is - and this has been a problem since the early days - that the information that one typically computes from a transition matrix (e.g. eigenvectors) is later linked back to the BoxSet (by, e.g., assiging a color to each Boxaccording to the corresponding entry in the eigenvector), so one must not change the BoxSet in the meantime or otherwise the information from the transition matrix is no longer valid for the BoxSet.  So the question is whether we should somehow 'tie' a transition matrix to a BoxSet, i.e. whether we should define something like BoxTransitionMatrix which, e.g., takes a BoxSet and a BoxMap for construction.
Originally posted by @gaioguy in https://github.com/gaioguy/GAIO.jl/pull/1#issuecomment-654901328

I have to following two ideas to deal with this:

We delay putting an order onto a BoxSet as long as possible. Once the user requests a transition matrix, we additionally return an ordered boxset. This is the currently implemented approach in #20. There, the ordered boxset is a function that takes a set of integers and returns the corresponding boxset.

We give the user an explicit way to order a boxset:

boxlist = order(boxset) # put an arbitrary order on the elements in the boxset
G = transition_graph(g, boxlist)
mat = matrix(G)
# mat[1,1] corresponds to the weight of the edge boxlist[1] -> boxlist[1]
# boxlist[3,45,7] returns a boxset

Such a boxlist would be immutable.

Personally, I find 2. to be more intuitive. As you said, having an additional interface along the lines of
function transition_graph(g::BoxMap,boxset::BoxSet)
    return transition_graph(g,order(boxset))
end

(or maybe a little bit more sophisticated/optimized) would solve the issue, right?
By the way, I'm not yet super sure about this, but I think I'd prefer that  boxlist[[3,45,7]] returns a boxlist again, and have boxlist really act like a list of boxes. Maybe we can have an additional constructor BoxSet(boxlist) or something like that to convert a boxlist or a sublist of it back to a boxset?

Good point. As discussed, I will work on a PR for the second approach.


Near.org/ai

Context
NEAR Foundation is beginning a larger revamp of the near.org website. This process will take three to four months with an anticipated launch date in mid-late Sept 2024. In the interim period, NF needs to have a location where we can consolidate all the relevant activities, partners, and calls to action for engaging with our emerging AI ecosystem, and direct interested founders and builders to it.
Requirements
Figma design
Specific links and assets:
Hero section CTA links:

Work with us - https://airtable.com/appc0ZVhbKj8hMLvH/pagsVjkk5LZ66MbJm/form
NEAR AI R&D - near.ai

Ecosystem Logos:

Pond, Mizu and Nevermined logos - https://drive.google.com/drive/folders/1onZrXcFbbkR1P_suHYgXe-8EiTj-O9wP
Pond URL - https://cryptopond.xyz/
Mizu URL - https://mizu.global/
Nevermined URL - https://nevermined.io/
Hyperbolic - URL - https://hyperbolic.xyz/
Bitte - URL - https://www.bitte.ai/
Jutsu - URL - https://jutsu.ai/
Nillion - URL - https://nillion.com/
Masa - URL - https://www.masa.ai/

Get Involved:

Are you an early stage AI Founder? --> https://www.hzn.xyz/hzn
Are you interested in a partnership with us? --> https://airtable.com/appc0ZVhbKj8hMLvH/pagsVjkk5LZ66MbJm/form
Are you an AI researcher? --> near.ai
Just want to learn more about User-Owned AI? --> https://www.youtube.com/playlist?list=PL9tzQn_TEuFWMuPiQOXhaE5lpOTnxLPZY

Events:

Please embed the following Luma calendar - [(https://lu.ma/edgeAGI)]

@shelegdmitriy - updated the ticket with a link to the luma FYI

@LCCCunningham is it possible to add this user<EMAIL_ADDRESS>to that luma calendar? Otherwise, I can't get those events

I found another way to get a list of events I think

@LCCCunningham checkout this preview link. If this link doesn't work for you then try to open it from linked pull request.
cc @gabehamilton

Hey @vanessadespain! I received this image

and it seems I should put it somewhere on the page but I don't understand where? The figma design still looks the same

Maybe I should swap this section

with the provided image?
cc @vanessadespain @LCCCunningham

Hey Dmitriy,
I'm receiving your email but I don't see the comments in GitHub, perhaps
because the ticket is closed?
I'm not in the loop on this design change, but I assume you're correct that
this image you were provided is swapping for the section you highlighted.
One note of caution, I'm typically against putting a lot of text inside of
an image for accessibility reasons. This image will require a lot of Alt
text to fully describe the image/table for folks who use screen readers. In
the past I've worked with a dev who solved this by providing a table inside
of the alt text to read out the contents.
cc @LCCCunningham https://github.com/LCCCunningham
On Tue, Jun 25, 2024 at 10:47 AM Dmitriy @.***> wrote:

Maybe I should swap this section
2024-06-<IP_ADDRESS>.png (view on web)
https://github.com/near/near-discovery/assets/34593263/ef603dbe-933a-4686-b26a-f59aa5e0568e
with the provided image?
cc @vanessadespain https://github.com/vanessadespain @LCCCunningham
https://github.com/LCCCunningham
—
Reply to this email directly, view it on GitHub
https://github.com/near/near-discovery/issues/1207#issuecomment-2189604123,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7VWBWOMWHP4NDJXH6XFITZJGUKBAVCNFSM6AAAAABJK55LPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBZGYYDIMJSGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Update of dependencies to comply with Whitesource security scan

At our company we're using Whitesource software for detection of the security issues. Unfortunately the newest version (2.11.1) of aws-xray-recorder-sdk-core doesn't comply with our policy. Some libraries have serious vulnerabilities and some are just old (joda-time is 7 years old). Below is the list of libraries that were rejected in a security scan.
Most if not all of these problematic dependencies come from aws-java-sdk-core library which should also be updated.

aws-xray-recorder-sdk-core-2.11.1.jar
└---aws-java-sdk-xray-1.11.903.jar
       └---aws-java-sdk-core-1.11.903.jar
                └---ion-java-1.0.2.jar - **_reject old libraries_**
                └---jackson-databind-<IP_ADDRESS>.jar - **_reject high vulnerable libraries_**
                        └---jackson-annotations-2.6.0.jar - **_reject old libraries_**
                        └---jackson-core-2.6.7.jar - **_reject old libraries_**
                └---jackson-dataformat-cbor-2.6.7.jar - **_reject high vulnerable libraries_**
                └---joda-time-2.8.1.jar - **_reject old libraries_**

Please consider this request as without these changes it becomes impossible to use xray.

Thanks for raising this question, we are working on upgrade the aws-java-sdk-core to the latest version 1.12.

@SebastianCelejewski Unfortunately it looks like the AWS Java SDK team doesn't have any plans to remove Joda Time like they did for Jackson. They need to maintain backwards compatibility with Java 6 and that's why they can't remove it. See https://github.com/aws/aws-sdk-java/issues/1580.
As always, ADOT (AWS Distro for OTel) Java has full GA support by the X-Ray team, so it is a great alternative to the X-Ray Java SDK with a superset of features.

@NathanielRN joda-time by itself is fine, it's just this obsolete version what is the problem. If they could update it to some more recent version it would be fine. I see that the last version is 2.10.14 from March 2022. It's still version 2 so probably there aren't any breaking changes.

@PiotrWu Do you think we can continue the conversation on that GitHub issue there in that case? Since without a newer AWS Java SDK, we can’t unblock the issue here on X-Ray side, unless we used V2 somehow but that would be a bigger feature request for the X-Ray SDK here.

@NathanielRN sure.


[BUG] Bloxstrap wont run.

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
Whenever i launch roblox it doesnt run, and i noticed when i go to my tray, when i launch it and let it load a little a caution triangle comes up for a split second than goes away and closes bloxstrap.

Are you able to at least open the Bloxstrap Menu?

I can open the bloxstrap menu, but it will not launch with my game/roblox
On Wed, Apr 10, 2024 at 10:21 AM pizzaboxer @.***>
wrote:

Are you able to at least open the Bloxstrap Menu?
—
Reply to this email directly, view it on GitHub
https://github.com/pizzaboxer/bloxstrap/issues/1588#issuecomment-2047688474,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44H35YNNFN5LXSHGSWKAYTY4VDHRAVCNFSM6AAAAABF7FRED6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBXGY4DQNBXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Try and launch Roblox again (through the Play Roblox shortcut), and afterwards, get Bloxstrap's latest log file from the %localappdata%\Bloxstrap\Logs folder and send it here please.

Thanks so much for helping me, sorry that I didn't send it earlier.
Here is the log after launching.
On Wed, Apr 10, 2024 at 7:35 PM pizzaboxer @.***> wrote:

Try and launch Roblox again (through the Play Roblox shortcut), and
afterwards, get Bloxstrap's latest log file from the
%localappdata%\Bloxstrap\Logs folder and send it here please.
—
Reply to this email directly, view it on GitHub
https://github.com/pizzaboxer/bloxstrap/issues/1588#issuecomment-2048601800,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44H35ZTVMAAK6VBYXHMEZDY4XECNAVCNFSM6AAAAABF7FRED6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBYGYYDCOBQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Where's the log?

It’s at the bottom of the page
On Thu, Apr 11, 2024 at 9:19 AM pizzaboxer @.***> wrote:

Where's the log?
—
Reply to this email directly, view it on GitHub
https://github.com/pizzaboxer/bloxstrap/issues/1588#issuecomment-2049677576,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44H3535UUUDLI4FM6KBGZDY42EUPAVCNFSM6AAAAABF7FRED6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBZGY3TONJXGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Bloxstrap_20240411T000419Z (1).log

Please let me know if there is a fix for this.
On Thu, Apr 11, 2024 at 12:08 PM hecker cat @.***> wrote:

It’s at the bottom of the page
On Thu, Apr 11, 2024 at 9:19 AM pizzaboxer @.***>
wrote:

Where's the log?
—
Reply to this email directly, view it on GitHub
https://github.com/pizzaboxer/bloxstrap/issues/1588#issuecomment-2049677576,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44H3535UUUDLI4FM6KBGZDY42EUPAVCNFSM6AAAAABF7FRED6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBZGY3TONJXGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh, I misunderstood your issue, my bad.
Does Roblox work if you use the original launcher? https://github.com/pizzaboxer/bloxstrap/wiki/Switching-between-Roblox-and-Bloxstrap

No it does not, but with bloxstrap uninstalled it does.
I reinstalled twice. Sorry if I miss understand your question
On Fri, Apr 12, 2024 at 8:39 AM pizzaboxer @.***> wrote:

Oh, I misunderstood your issue, my bad.
Does Roblox work if you use the original launcher?
https://github.com/pizzaboxer/bloxstrap/wiki/Switching-between-Roblox-and-Bloxstrap
—
Reply to this email directly, view it on GitHub
https://github.com/pizzaboxer/bloxstrap/issues/1588#issuecomment-2051683850,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44H35YZPSTGEZMRSZ74LALY47IW3AVCNFSM6AAAAABF7FRED6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRGY4DGOBVGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Roblox works only when Bloxstrap isn't installed? You're sure of that?

I tried once more, and it does
On Fri, Apr 12, 2024 at 4:18 PM pizzaboxer @.***> wrote:

Roblox works only when Bloxstrap isn't installed? You're sure of that?
—
Reply to this email directly, view it on GitHub
https://github.com/pizzaboxer/bloxstrap/issues/1588#issuecomment-2052467838,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44H35YTFR7K2BCECAXFNGDY5A6QPAVCNFSM6AAAAABF7FRED6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSGQ3DOOBTHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Any fix?
On Fri, Apr 12, 2024 at 4:47 PM hecker cat @.***> wrote:

I tried once more, and it does
On Fri, Apr 12, 2024 at 4:18 PM pizzaboxer @.***>
wrote:

Roblox works only when Bloxstrap isn't installed? You're sure of that?
—
Reply to this email directly, view it on GitHub
https://github.com/pizzaboxer/bloxstrap/issues/1588#issuecomment-2052467838,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44H35YTFR7K2BCECAXFNGDY5A6QPAVCNFSM6AAAAABF7FRED6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSGQ3DOOBTHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Not really, because it doesn't really make any sense as to why that would be happening. I don't think I've seen an issue like this before, because the original launcher should be working at the very least.
Just to clarify, you were using the "Roblox Player" shortcut, right?


'SerialBLE' was not declared in this scope

hi, i have this message error.
i have read the various solutions but its don't work anyway. I have followed the instruction to install libraries but when i upload the sketch to my arduino uno or mega error is the same. i use code from the site, codes example but its make the same error. how can i fix?
i have windows 10 s.o.

change: SoftwareSerial SwSerial(10, 11); // RX, TX
for: SoftwareSerial SerialBLE(10, 11); // RX, TX

I have learned this the hard way, I should of come here and read this error note! This took me days lol this is my very first analog read project, and went balls deep with the hc-05 ble blynk app- way too much to learn on on your own once starting out btw aha.  I was about to report this problem till I found this thread! Always check Google if you don't wanna figure it out I guess is my lesson learned today!

BLE is currently not supported in Blynk 2.0


If multiple items are bought, only one shows as unassigned item

I have tried your autobuyer for the first time on my mac. After setting up a random filter to test it, I managed to buy a couple of players as also confirmed in the log. However, only one showed as unassigned item in the home page. Is it possible that the other one was maybe sent to my club directly?

Hi, I have this on my laptop, is it possible for you to give me a step by step install for a mac? My friend wants it but only has a mac. Thanks

Hi, I have this on my laptop, is it possible for you to give me a step by step install for a mac? My friend wants it but only has a mac. Thanks

@rv1985 , yeah it should be in club

@rv1985 , yeah it should be in club


jwt-issuer renamed to vc-jwt-issuer

Every entity in the OAuth/OpenID is potentially a JWT issuer, then I found the name of this endpoint misleading.
Considering that this brand new specification defines a profile for SD JWT verifiable credentials, I'd propose to change the pathname to
.well-known/vc-jwt-issuer

The idea is that the JWT Issuer could be used with any JWT, not necessarily VCs only.

@tlodderstedt what do you think?

@peppelinux is there a reason the JWT Issuer should not be used with something else than VCs?

There are well known endpoints like openid-configuration or openid-federation that publish entities metadata, including jwks
Since this specs Is related to VC based on sd-jwt,  this specs should not be in conflict to pre existing Oauth2/OpenID ecosystem
SD-JWT-VC should define only the resources needed for the solution It defines

I'm ok with the proposed change.

I agree @tlodderstedt,
Key attestation alone Is not enough, this endpoint deserves a proper identity with a specialized protocol metadata
Also the verifiable attestations related to the entity may be available in it

(As a record, I repeat my question I made elsewhere in the past.)
Why is it necessary to introduce a new /.well-known path, especially if the expected content is just like below (excerpt from "5.2. JWT Issuer Metadata Response")?
{
   "issuer":"https://example.com/",
   "jwks_uri":"https://jwt-issuer.example.org/my_public_keys.jwks"
}

Isn't the jku JWS header parameter (RFC 7515 Section 4.1.2) like below sufficient?
{
  "alg": "ES256",
  "typ": "vc+sd-jwt",
  "jku": "https://jwt-issuer.example.org/my_public_keys.jwks"
}

(For the record, I repeat my answer I gave on Slack and add more context)
The jku header is not sufficient for the intended purpose. The purpose of the well-know endpoint is to establish a stable issuer identifier independent of the jwks location. This issuer identifier can be used in other structures to establish trust, e.g. it can be added to trusted lists (verifier end or trusted 3rd party). Additionally, it fits nicely with the other well-known locations, like openid-credential-issuer and oauth-authorization-server. So the issuer can distribute the role specific metadata in different location residing under the same issuer identifier. And not to forget, this well-known location also could work well with openid-federation.
Moreover, any additional VC issuer metadata we will come across can be added to this endpoint.
BTW: I think a dedicated issue would be the better place for this discussion.
Am 8. Juni 2023, 17:15 +0200 schrieb Takahiko Kawasaki @.***>:

(As a record, I repeat my question I made elsewhere in the past.)
Why is it necessary to introduce a new /.well-known path, especially if the expected content is just like below (excerpt from "5.2. JWT Issuer Metadata Response")?
{
"issuer":"https://example.com/",
"jwks_uri":"https://jwt-issuer.example.org/my_public_keys.jwks"
}
Isn't the jku JWS header parameter (RFC 7515 Section 4.1.2) like below sufficient?
{
"alg": "ES256",
"typ": "vc+sd-jwt",
"jku": "https://jwt-issuer.example.org/my_public_keys.jwks"
}
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

I am actually in favor of jwt-issuer. This mechanism is meant to be general enough to be used with not just a 'verifiable credential'. and I don't think anyone would think to use .well-known/jwt-issuer with ID Tokens and Access Tokens, UserInfo responses , etc. that are JWTs.

I understand your point @Sakurann, below my thoughts

Why defining jwt-issuer for general purpose in a spec that's specialized for VC? Requirement: definition of a specs in IETF for general purpose JWT Issuer metadata (enabling client metadata, that today is only available in openid-federation...)

I agree that jwt-vc-issuer semantically collides with credential-issuer, and we should do collisions

why are can't use .well-known/openid-federation? Federation entity discovery is required for the entities that builds trust chain according to the federation specs, nothing prevent to publish all the metadata of all thw "JWT-role" in a single metadata, that could not be signed if request (content-type) in plain text

I suggest to use .well-known/openid-federation to consolidate a unique way to publish all the metadata types and roles of an entity.
coming back to the name change proposal. Why we use the term issuer since the metadata contains also general capabilities not related to the issuance?
in a more general purpose way, wouldn't it be a .well-known/oauth-entity?
then the question: if that entity has more functionalities and roles, being at the same time a RP and a AS, how the metadata should be organized?
We've resolved this issue in openid-federation, with the below schema, where a RP can be also a OP, AS, Client, credential-issuer and so on:
https://github.com/italia/spid-cie-oidc-docs/blob/versione-corrente/docs/common/common_examples.rst#en-11-entity-configuration-response-relying-party

I'm a little embarrassed, but to be honest, I still don't understand the reasoning. "A stable issuer identifier" is represented by the iss claim, not by the URL of the well-known endpoint, isn't it?
A possible reason for necessity of a well-known path I guess is "to make sure that the host identified by the issuer identifier actually exists and is accessible, by forcing JWT verifiers to access a path under the domain."
An example with concrete values would be "to make sure that the host example.com identified by the issuer identifier https://example.com actually exists and is accessible, by forcing JWT verifiers to access a path (/.well-known/{whatever}) under the domain (example.com)."
It might be beneficial to define /.well-known/jwt-issuer as the ultimate fallback general-purpose option for locating the public key required to verify the JWT's signature (not as the sole rule for every VC to follow), especially when it is challenging to reach a consensus on a single method within a limited timeframe among the following.

jwk
x5c
kid starting with did:
jku
trust_chain
/.well-known/openid-configuration
/.well-known/openid-federation
/.well-known/vc-jwt-issuer
./well-known/openid-credential-issuer
/.well-known/jwt-issuer
Others

However, maybe I'm still missing something, sorry.

The well-known endpoint is indeed also a stable identifier. But it depends on a certain well-known location, i.e. different well-known locations are different identifiers.
I'm looking for a stable identifier for the issuer that works across .well-known locations and is not bound to a certain key. That's pretty simple with well-known locations as the iss value can be extended by several different .well-known locations, but the identifier is still the same, right?
So for example, the issuer could use the jwt-issuer mechanism share keys and (at the same time) be part of an OpenID Federation as shown in the following:
/.well-known/jwt-issuer
/.well-known/openid-federation
The same issuer's URL could also at the same time used in an external data structure at the verifier or at a trusted 3rd party.
Effect: I can establish trust in a certain issuer/entity/server that works across different roles/perspectives.
I hope that explains better.

I'm looking for a stable identifier for the issuer that works across .well-known locations and is not bound to a certain key

this would allow an entity to use different keys to sign ID Tokens, VCs, access tokens, etc.

my question is
how to differentiate different capabilities for different metadata protocols?
this is an example in oidc federation
https://github.com/italia/eidas-it-wallet-docs/pull/14/files#diff-f44e126e298004564899b4b86fc1f5e074b5ca6a96e9f546b7a1ed8987e61735R542
here we're saying, this is the wallet provider metadata, where multiple metadata/roles cohexists in a single .well-known
how jwt-issuer endpoint handles this?

If the typ JWS header indicates that the JWT is a VC (e.g. "typ":"vc+sd-jwt"), the following paths also can work.

/.well-known/openid-credential-issuer (defined in OID4VCI)
/.well-known/vc-jwt-issuer (proposed by this issue)

I'd like to understand why the generic name jwt-issuer is chosen. The generic name is subject to interpretation where authorization servers, relying parties and any JWT-issuing systems should provide /.well-known/jwt-issuer to expose their metadata (at least jwks_uri or jwks) as the last resort. What if one server behaves as both an authorization server and a credential issuer? Should the authorization server publish the same content at both /.well-known/openid-configuration and /.well-known/jwt-issuer? Should intermediate authorities and trust anchors of OIDC Federation also provide /.well-known/jwt-issuer? Such a conflict is what I'm (and ordinary server implementers will be) concerned about.
The latest draft of "SD-JWT-based Verifiable Credentials with JSON payloads (SD-JWT VC)" defines jwks_uri and jwks jwt-issuer metadata. If so, there is no reason to prevent adding the same metadata to OID4VCI Credential Issuer Metadata as well. Basically, I believe the metadata should be added to OID4VCI regardless of the discussion about jwt-issuer.

@TakahikoKawasaki raises an important question that we need to address, at least by giving guidance. I don't have a good answer to that at the moment.
Besides that, I don't see a need to rename to jwt-vc-issuer.

@TakahikoKawasaki correct me if I'm wrong. I understand you prefer vc-jwt-issuer over jwt-issuer, right? And whether the key data will be added to the openid-credential-issuer is a different topic (that's how I read your last statement).
Please conform.

We will need more discussions on that topic. Potentially at IETF 117. This means, we won't be able to resolve this issue for our individual draft 03.

@TakahikoKawasaki raises an important question that we need to address, at least by giving guidance. I don't have a good answer to that at the moment.
Besides that, I don't see a need to rename to jwt-vc-issuer.

We had a small discussion on this and I created a new issue #143 so we can separate between the 2 discussions overlapping here (name of the endpoint and intended usage).

Regarding the /.well-known/jwt-issuer path, I have been losing confidence in my own opinion. As an implementer who has implemented numerous OAuth/OIDC specifications and been leading development of Authlete that holds the most OpenID certifications in the world, my intuition told me "The /.well-known/jwt-issuer path should be avoided due to possible conflicts with other specifications." However, I haven't received as much support for my opinion as I expected. For now, I will implement my OID4VCI implementation using the /.well-known/jwt-issuer path. Please let me withdraw my opinion.

I agree @TakahikoKawasaki position, while in the italian solution we're implementing openid-credential-issuer as metadata within the .well-known/openid-federation endpoint, according to OpenID Federation 1.0.
This doesn't prevent to include also a jwt-issuer metadata type but there's the decision by our side to wait and the same time time give evidence of our implementation to help the consolidation of vc-jwt-issuer specs

@peppelinux
An off-topic question out of curiosity. If an authorization server / OpenID provider and a credential issuer are hosted on the same server, the payload of the entity configuration published at /.well-known/openid-configuration of the server contains the following, right?
"metadata": {
  "openid_provider": { "...":"..." },
  "openid-credential-issuer": { "...":"..." }
}

Hey @TakahikoKawasaki, I'm sure that you meant openid-federation
The answer Is yes, even if we have used a snake case like openid_credential_issuer here
https://italia.github.io/eidas-it-wallet-docs/en/pid-issuing.html
It's still an initial draft without an official release, several editorials and implementation compromises needs to be resolved but the most of the work Is there, feelfree to open issue for discussion here
https://github.com/italia/eidas-it-wallet-docs

To make progress with this.
Are folks comfortable with renaming "JWT Issuer Metadata"? And if so, would folks be fine with "SD-JWT VC Issuer Metadata" or "VC Issuer Metadata"? I like "VC Issuer Metadata" better because it is more future looking.
What do folks think? cc @danielfett @Sakurann @tlodderstedt @TakahikoKawasaki @c2bo
After we agreed on a new name I'd ask @peppelinux to update PR #118 .

Agree that "jwt-issuer" is too general and am in favor of a renaming.


[BUG] Upgrade: a re-run upgrade_node job might miss some version-based patches

Describe the bug

We have seen pre-drain or post-drain jobs fail, and users start a new upgrade again.
Due to the system version is already upgraded, the previous version detection in upgrade_node is not reliable.
To Reproduce
Steps to reproduce the behavior:

Upgrade from v1.0.3 to v1.1.0.
Try to fail a node post-drain job.
Re-run the upgrade again.
patch_logging_event_audit and convert_nodenetwork_to_vlanconfig function won't execute.

Expected behavior

We still need to patch various configuration on nodes.

We could detect the correct version with /etc/harvester-release.yaml on a node.
We also need to check if patch_logging_event_audit and convert_nodenetwork_to_vlanconfig calls are idempotent.

Support bundle

Environment

Harvester ISO version:
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

Verified fixed on master-f854772-head (11/08) . Close this issue.
Result
When we manually made the first node failed at post-drain then rerun the upgrade again.

We can resume to complete the post-drain job on the first node and finish the whole cluster upgrade process.

All v1.0.3 patches have updated in pre-drain pod

NODE_CURRENT_HARVESTER_VERSION is: v1.0.3
2022-11-09T06:35:30.819865719Z stderr F + echo 'The UPGRADE_PREVIOUS_VERSION is master-5a18d059-head, NODE_CURRENT_HARVESTER_VERSION is v1.0.3, will check Logging Event Audit upgrade node option'
2022-11-09T06:35:30.819898187Z stderr F + test master-5a18d059-head = v1.0.3
2022-11-09T06:35:30.81987791Z stdout F The UPGRADE_PREVIOUS_VERSION is master-5a18d059-head, NODE_CURRENT_HARVESTER_VERSION is v1.0.3, will check Logging Event Audit upgrade node option
2022-11-09T06:35:30.819920924Z stderr F + test v1.0.3 = v1.0.3
2022-11-09T06:35:30.820501475Z stderr F + echo 'Patch kube-audit policy file'
2022-11-09T06:35:30.820532592Z stderr F + ls /host/etc/rancher/rke2/config.yaml.d/ -alt
2022-11-09T06:35:30.820512635Z stdout F Patch kube-audit policy file

All v1.0.3 post-drain pod logs in post-drain pod

NODE_CURRENT_HARVESTER_VERSION=v1.0.3
2022-11-09T06:38:13.250461509Z stderr F + echo 'NODE_CURRENT_HARVESTER_VERSION is: v1.0.3'
2022-11-09T06:38:13.250611121Z stderr F + echo 'The UPGRADE_PREVIOUS_VERSION is master-5a18d059-head, NODE_CURRENT_HARVESTER_VERSION is v1.0.3, will check nodenetwork upgrade node option'
2022-11-09T06:38:13.250626445Z stderr F + test master-5a18d059-head '!=' v1.0.3
2022-11-09T06:38:13.250633464Z stderr F + test v1.0.3 '!=' v1.0.3
2022-11-09T06:38:13.250669403Z stdout F NODE_CURRENT_HARVESTER_VERSION is: v1.0.3
2022-11-09T06:38:13.250697355Z stdout F The UPGRADE_PREVIOUS_VERSION is master-5a18d059-head, NODE_CURRENT_HARVESTER_VERSION is v1.0.3, will check nodenetwork upgrade node option

Test Information

Test Environment: 4 nodes Harvester bare machines
Harvester version: master-f854772-head (11/08)

Verify Steps
Ref to https://github.com/harvester/harvester/pull/3102#issuecomment-1303769203

Prepare a 4 nodes v1.0.3 Harvester cluster
Enable network on available NIC
Create two available VLANs
Upgrade from v1.0.3 to master release
After the harvester upgraded in apply-manifest stage, the server-version is changed
Make the first post-drain failed by running

node-0:~ # touch /tmp/elemental
node-0:~ # mount --bind /tmp/elemental /usr/bin/elemental

Wait for upgrade proceed to first node in pre-drain and post-drain status
Apply the rescue steps here, wait for the cluster state to become "Provisioned"

Execute ./post-drain

Restart the upgrade, can follow the instruction in https://docs.harvesterhci.io/v1.0/upgrade/troubleshooting/#start-over-an-upgrade
Remove the mess on the first node $ umount /usr/bin/elemental
Check the pre/post-drain Job on node-0 ends up successfully, all v1.0.3 patches are applied

Additional context

pre-drain.log
hvst-upgrade-9dmpk-pre-drain-harvester-z622q.log
post-drain.log
hvst-upgrade-9dmpk-post-drain-harvester-z622q.log


do not skip windows

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

ref.: https://github.com/conda-forge/swig-feedstock/issues/24


code blocks

Is there a plan to roll out adding code blocks?
Since Quilljs has added code blocks support in its beta release:
https://github.com/quilljs/quill/issues/116
The first thing is to make react-quill compatible with Quilljs version 1.0. Here is a guide to upgrade:http://beta.quilljs.com/guides/upgrading-to-1-0/
Shall I put up a pull request for this?

Pull Request #98

Appears to be working with demo on master: https://zenoamaro.github.io/react-quill/

The code-block feature seems not working anymore in the latest version. Got warning: "quill:toolbar ignoring attaching to disabled format code-block". Is this feature deprecate?

You need to add the format to the formats prop
On Tue, May 16, 2017, 1:11 AM CristinaWang<EMAIL_ADDRESS>wrote:

The code-block feature seems not working anymore in the latest version.
Got warning: "quill:toolbar ignoring attaching to disabled format
code-block". Is this feature deprecate?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/zenoamaro/react-quill/issues/92#issuecomment-301708536,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABf7UyrPc135fu87AaSEuLvLEnZdf5WYks5r6Vo8gaJpZM4IZlFi
.

Yeah, I figure out after I added the comments so I delete it. Thank you.

fggcddcd


QMR results not getting alerted via email

We have deployed this utility in our environment correctly. stl_wlm_rule_action.actions table is also getting updated but we are not getting notified via mail.
Can anybody help where might be the disconnect??

Screenshot attached for the lambda function

Hi @da-prateeka, I am not sure if you have already confirmed subscription to SNS ? "You must confirm the subscription before the email address can start to receive messages."
Also, there was an issue in README regarding generating encrypting password for CIPHERTEXT parameter. The issue has been already fixed.
Could you please follow all steps again and reopen the issue if the problem persists? Please send Lambda log output.


[Entitas] Generate attribute [Input]

Hi, i can't  get how to create Input attribute.  I'm trying to create match1 from scratch, but it's too hard without any tutorials. I see there must be generated file for this.
using Entitas;

[Input]
public sealed class InputComponent : IComponent {

    public int x;
    public int y;
}

Common steps:

start with an empty project
define contexts in Entitas Preferences
Generate (this will generate a few files including context attributes)
create a new IComponent and use the generates context attribute (e.g. [Input])

thanx!


Advanced Params are not honored or logged correctly

Bug Report
Installation Method
Helm 0.3.21
Using openai compatible endpoint (not ollama)
Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[ ] I have included the browser console logs.
[x] I have included the Docker container logs.
[x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

When Advanced params are updated for a model under workspace, all the modified params will be logged
When Advanced params are overridden in the chat controls in a particular thread they will work (overriding the workspace params) and they will also be logged correctly

Actual Behavior:

Advanced params set in the workspace are not all logged correctly (top_k or min_p are not logged)
Advanced params modified in the chat controls do NOT override the workspace advanced params and also do not log correctly (top_k, min_p)

Description
Bug Summary:
Advanced params are not logged all the time and overriding them in the chat thread does not work.
This means i don't know if the setting (e.g. top_k) is actually honored and being sent correctly to the backend AND i can't give users the ability to modify things to their liking
Reproduction Details
Steps to Reproduce:
My situation today was needing to modify the defaults of LLAMA3-70b to Top_k = 10, Temp=0.7, Top_P=1
When i went to the logs to check if it had worked i saw that only Temp and Top_P were logged
In my chat thread advanced params i:

Modified all three items again to be the same as the workspace settings above, still didn't log Top_k
Modified all three items to be something different than the workspace settings above, still didn't log Top_K AND still logged temp=.7 and top_p=1 even though i had changed them
Modified 2 other Advanced params in the chat controls just to see if it was more than these 3:

Modified Min_P and it didn't log
Modified Frequency Penalty and it did log
Modified Batch size and it didn't log
Modified context length and it didn't log

Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
Screenshots/Screen Recordings (if applicable):
Here is a screenshot of the workspace params:

Here is a screenshot of the advanced params being modified after the workspace params have been modified:

here is the cooresponding log of the request that was sent
[open_webui.apps.openai.main] {"stream": true, "model": "meta-llama/Meta-Llama-3-70B-Instruct", "messages": [{"role": "user", "content": "tell me a short story"}, {"role": "assistant", "content": "Here is a short story:\n\nThe Old Piano\n\nEmma had always been fascinated by the old piano that sat silently in the corner of her grandmother's attic. As a child, she would sneak up to the attic and run her fingers over the yellowed keys, imagining the stories it could tell.\n\nYears went by, and Emma grew up. She moved away from home and started a family of her own. But when her grandmother passed away, Emma returned to the old house to sort through her belongings.\n\nAs she was packing up boxes and trunks, Emma stumbled upon an old diary hidden beneath the piano bench. It was worn and dusty, but as she opened it, she saw that it belonged to a young woman named Sophia.\n\nSophia had lived"}, {"role": "user", "content": "tell me another story"}, {"role": "assistant", "content": "Here is another short story:\n\nThe Starlight Serenaders\n\nIn a small village nestled in the rolling hills of Tuscany, there lived a group of elderly men who called themselves the Starlight Serenaders. For years, they had been gathering under the stars on warm summer evenings to play their instruments and sing together.\n\nTheir music was like nothing anyone had ever heard before. It was as if the stars themselves were singing in harmony with the men's rustic voices and worn instruments. People would come from all around to listen, mesmerized by the beauty of the music.\n\nBut as time went on, one by one, the Serenaders began to pass away. The villagers thought that would be the end of the magical performances. However,"}, {"role": "user", "content": "write me anothe story"}], "temperature": 0.7, "top_p": 1, "frequency_penalty": 1.05}

Additional Information
i have tried new threads, continuing threads, almost every combination but i can't get these items to log or be used
i took LLAMA3-70 out of the mix and tried a different model with NO workspace param modifications. Instead i modified just the chat control advanced params and had the same issue in a brand new thread:
[open_webui.apps.openai.main] {"stream": true, "model": "meta-llama/Llama-2-70b-chat-hf", "messages": [{"role": "user", "content": "Tell me a story"}], "temperature": 1}

Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

I can confirm this specific issue:

Modified context length and it didn't log

In the requests when the context has been modified at the chat level we see something like this:
{
	"options": {
		"num_ctx": 32000
	}
}

However when the default in Advanced Parameters has been modified I don't see it taking effect at all:
{
	"options": {
	}
}

Am I configuring something wrong? 😕

After upgrading versions I modified and saved the global setting again, then refreshed the UI. Now it appears to be sticky on new chats. Perhaps something weird in the initial migration for settings that were previously saved?

Models accessible via openai connections do not support all the advanced params.


docs: openshift+crc howto

CRC allows developers to install minimal OpenShift4 cluster on their local host machine for testing. Provide minimal how-to documentations on how to setup cluster with crc, deploy samba-operator with live share, and test it using samba toolbox.
Depends on PR293

This looks really great on first look. I can't wait to try it out!


Add support for Docker Compose API v2

add a way for getting container ID using v2 API
use container ID through v2 API if legacy API fails to locate that ID
V2 API filtering is prone to name clashes so added scaling instance suffix when filtering running services

Any ETA on this PR?  It seems to solve the issue.  Docker Compose 1 files have been overcome twice now by v2 and v3.  It's becoming harder for developers to even install older version of Docker Compose making use of this project harder.


Request: s around  contents

It would be a big boon to accessibility and usability if the contents of task list <li>s were wrapped in <label>s, so that the whole item was clickable.

I've worked round this in my app with this bit of jQuery, that's bound to a click handler on the li elements:
$(event.target).closest('li').find('> input.task-list-item-checkbox').click()

Arguably not an ideal solution, but might be useful to somebody in the interim.

What are your thoughts on adding labels @mtodd ? I'd also find it very helpful for styling individual tasks, and would consider doing a pull request for it if you like the idea.

We originally had <label>s but removed them due to usability problems. For background, see https://github.com/github/task_list/issues/5 and https://github.com/github/task_list/issues/3.
To answer your question, my thoughts are that we won't add <label>s back to github.com which uses this library. That doesn't mean they aren't useful in your application. With that in mind, I'd be open to considering changes to optionally wrap items in <label>, but I won't guarantee I'll merge it.
What might be more feasible and immediate would be to subclass the TaskList::Filter class to override render_task_list_item to wrap the item with a <label>. Assuming you're using HTML::Pipeline, you would just swap out TaskList::Filter with your subclass and get the benefits immediately.

Some interesting background info there; I hadn't considered what it would be like on mobile. Thanks for linking to the background info. I'll give it some thought – I may want to disable clicking on the text myself…

Going to close this as a duplicate now!


Work, energy and power

Description
Create the markdown file for Work, energy and power as per the reference content.
Lesson PDF (Tamil and English)
4. Work, energy and power.pdf
4. வேலை, ஆற்றல் மற்றும் திறன்.pdf

assigning to @sukrith12345


Need a python file

Hello !
You can set the flag USE_LOCAL_DATASETS to 0 and pip install bitsandbytes !


url_helper current_url https fix.

hi guys,
`
function current_url(bool $returnObject = false)
{
$url	= \CodeIgniter\Config\Services::request()->uri;
	if (\CodeIgniter\Config\Services::request()->isSecure())
	{
		$scheme = 'https';
	}

	if (isset($scheme))
	{
		$url->setScheme($scheme);
	}

	return $returnObject === true ? $url : (string) $url;
}

`

It should be already from the Request class. Are you not seeing that?

I see,
base_url() https fix. not be use current_url().
see https://blabla.com/foo/bar
current_url() - http://blabla.com/foo/bar

What is your baseURL set to in application/Config/App.php?  base_url uses that to generate the URL.