Create FenderString type

Our current string type uses a rust string, which can't be indexed by character. We should switch to a string type which holds a Vec<char>.

this is done and an optimization was added to increase the performance of modifying strings by updating the cached version of the string as well but this could cause a performance hit in some scenarios so we should do some bench-marking to see if this is a good idea or not
since this is a further and technically unnecessary optimization I believe we can leave it to after the beta launch as more of a improving the language steps rather than just creating the initial version of it

possible solutions are:

separate the two forms into separate functions giving the control to the user so they can use what is best for their scenario

basically one set of functions would work like a string builder where the actual string needs to get built at a later time
and the other would reflect just modifying a string, like in rust

have it be a feature to enable the other form of modification
a mix of both where there is a feature to set the default function to be used but either could be used if specified
so there are 3 functions, each of the 2 forms and one that is an alias to one of them

I feel like we should go with either the first or third and then if we go with the third say something in the docs that the default form should only be used in the repl or maybe personal scripts and that any code that gets shared should use the specific forms to maintain performance
this might also make no difference and its just faster to never do it in which case im putting too much thought into this thing that I am saying we shouldn't think about right now anyway

I think storing strings strictly as Vec<char> with no other representation will be the best long term solution. It would also allow us to create a substring type so you could get a substring of a string in O(1).

Well with the current implementation and the potential optimization you can do that
cause the strings are just a Vec but there is a cached version of the printable version of the string so that if you print the same piece of text multiple times you don't need to iterate over the Vec each time
the optimization I am talking about is if the cached string is up to date and another string or character gets appended then it will also append the character to the cached rust string

the more I think about it the more ways I can see for optimizing it in different ways and for prioritizing different things, like compute time vs memory. So I wanna say push off trying to do all these now so we can get a better idea of what will be usable and work best in real scenarios during the beta. So for now lets just either have the cached string get updated when quickly possible or just remove it for now and just have it get dropped when the cached string is de-synced.
Then at a later time after evaluating it in the real world we can decide if that was the right call, or if the cached string should just not exist at all, or if you should have to specify if you want to have one or not when creating the string so that short and constantly reprinted strings can be cached; but longer, and constantly being modified strings will just never cache their printable forms.

actually having the caching be an optional opt in thing sounds like a good idea to just implement now if you agree


refactor(docs): theme-common shouldn't depend on docs content

Motivation
Follow-up of https://github.com/facebook/docusaurus/pull/10313
Note that I added a retro compatibility workaround for APIs from @docusaurus/theme-common that have been moved around. They are public API surfaces although only useCurrentSidebarCategory has ever been documented before v2.1 (not anymore)
Test Plan
CI + preview
Test links
https://deploy-preview-10316--docusaurus-2.netlify.app/
Related issues/PRs

Does this fix https://github.com/facebook/docusaurus/issues/7207 or is that issue really worth fixing?


[JavaScript]Getting following error "initializeIcons is not a function" when trying to use adaptivecards-fabric.js

I was trying to directly include the output adaptivecards-fabric.js file to my HTML file and use it to style my adaptive cards. I also included the dependencies cdn urls to my html.
<script src="https://unpkg.com/adaptivecards/dist/adaptivecards.js"></script>
<script<EMAIL_ADDRESS><script src="https://cdnjs.cloudflare.com/ajax/libs/react/16.8.6/umd/react.development.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react-dom/16.8.6/umd/react-dom.development.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/fluentui-react/7.123.7/fluentui-react.js"></script>
<link rel="stylesheet" href="https://static2.sharepointonline.com/files/fabric/office-ui-fabric-js/1.4.0/css/fabric.min.css" />
<link rel="stylesheet" href="https://static2.sharepointonline.com/files/fabric/office-ui-fabric-js/1.4.0/css/fabric.components.min.css" />
<script src="https://static2.sharepointonline.com/files/fabric/office-ui-fabric-js/1.4.0/js/fabric.min.js"></script>

Can you please tell me what iam doing wrong here? I guess initializeIcons is from fluentui-react, which I have included.

If this is still an issue for you please reopen


[SC-868] Patch CurveOracle

Codecov Report
Patch coverage: 92.00% and project coverage change: +0.83% :tada:

Comparison is base (31d8614) 77.77% compared to head (2c1bb6a) 78.60%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
+ Coverage   77.77%   78.60%   +0.83%
==========================================
  Files          30       30
  Lines         765      762       -3
  Branches      158      158
==========================================
+ Hits          595      599       +4
+ Misses        170      163       -7

Files Changed
Coverage Δ

contracts/oracles/CurveOracle.sol
93.75% <92.00%> (+19.46%)
:arrow_up:

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


Validate user access token

This PR allows us to validate a user token and bring back some token details.
Since there is no way to easily avoid modifying the auth type (Bearer vs OAuth), a conditional check against the validation URL was put into setRequestHeaders. It's not the cleanest, but it's the only path that doesn't require a significant refactor.

Pull Request Test Coverage Report for Build 167

25 of 27 (92.59%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 89.931%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

authentication.go
19
21
90.48%

Totals

Change from base Build 166:
0.09%

Covered Lines:
652

Relevant Lines:
725

💛  - Coveralls


AttributeError: module 'src.algorithms.classify' has no attribute 'trained_model'

I'm using the official Docker development configuration. I only cloned repository, set up the docker environment (copy-paste from the instructions), and opened the page at localhost:8001
I expected to see the sort of welcome page, but I saw just the debugger page, with the error you read in the title.
A possible solution:
In the file:
concept-to-clinic/prediction/src/views.py
change two rows:
#from .algorithms import classify
to
from .algorithms.classify import trained_model
and
#'classify': classify.trained_model.predict,
to
'classify': trained_model.predict,
Steps to Reproduce

set up a clean environment
run docker-compose -f local.yml up
open http://localhost:8001

Checklist before submitting

[x] I have confirmed this using the officially supported Docker Compose setup using the local.py configuration and ensured that I built the containers again and they reflect the most recent version of the project at the HEAD commit on the master branch
[x ] I have searched through the other currently open issues and am confident this is not a duplicate of an existing bug
[x] I provided a minimal code snippet or list of steps that reproduces the bug.
[] I provided screenshots where appropriate
[x] I filled out all the relevant sections of this template

P.S.
'local.py' in the checklist should be 'local.yml', right?

Thanks for filing the issue @vlavorini . I think I resolved it by adding the missing content to __init__.py, which has been added for the identify and segment algorithm folders but not for the classify one. Can you pull my branch 123_attribute_error and verify whether it works for you there as well?

very thanks @vlavorini This was my problem hours ago.

'local.py' in the checklist should be 'local.yml', right?

Is there a typo somewhere in the docs? If so, mind submitting another issue about it? Thanks!


RFC 0002 - principles needs translation

The RFC0002 has landed and needs to be translated into French.

File: https://github.com/cds-snc/docs/blob/main/development/rfcs/0002-principles.md
Raw: https://raw.githubusercontent.com/cds-snc/docs/main/development/rfcs/0002-principles.md


x/tokenfactory create denom fee

Closes: #XXX
What is the purpose of the change
*Add a description of the overall background and high level changes that this PR introduces *
(E.g.: This pull request improves documation of area A by adding ....
Brief change log
(for example:)

The metadata is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
Daemons retrieve the RPC data from the blob cache

Testing and Verifying
(Please pick one of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added unit test that validates ...
Added integration tests for end-to-end deployment with ...
Extended integration test for ...
Manually verified the change by ...

Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (yes / no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (yes / no)
How is the feature or change documented? (not applicable   /   specification (x/<module>/spec/)  /  Osmosis docs repo   /   not documented)

Codecov Report

Merging #1435 (6b2b682) into main (f56fbe5) will decrease coverage by 0.51%.
The diff coverage is 15.64%.

@@            Coverage Diff             @@
##             main    #1435      +/-   ##
==========================================
- Coverage   19.82%   19.31%   -0.52%
==========================================
  Files         202      229      +27
  Lines       27685    31398    +3713
==========================================
+ Hits         5489     6065     +576
- Misses      21175    24224    +3049
- Partials     1021     1109      +88

Impacted Files
Coverage Δ

x/epochs/client/cli/query.go
0.00% <ø> (ø)

x/gamm/client/cli/query.go
36.74% <0.00%> (-0.36%)
:arrow_down:

x/gamm/pool-models/stableswap/amm.go
40.27% <0.00%> (-15.50%)
:arrow_down:

x/gamm/pool-models/stableswap/msgs.go
0.00% <0.00%> (ø)

x/gamm/pool-models/stableswap/pool.go
0.00% <0.00%> (ø)

x/gamm/pool-models/stableswap/stableswap_pool.go
0.00% <0.00%> (ø)

.../gamm/pool-models/stableswap/stableswap_pool.pb.go
0.58% <0.00%> (-0.09%)
:arrow_down:

x/gamm/types/pool.go
0.00% <ø> (ø)

x/incentives/client/cli/query.go
0.00% <ø> (ø)

x/incentives/keeper/distribute.go
61.00% <0.00%> (ø)

... and 52 more

Continue to review full report at Codecov.

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


Sort options

I'm trying to sort by date desc but I can only find examples of sorting by cloud cover. Also, is there a list of fields available to sort by?

A bit late on this, but you can sort by any field and you can use shortcuts:
sortby = "-properties.datetime"

Sorts by datetime, descending


Add RestApiCreation using OAS doc tests, and resources

Purpose

Add tests for RestApiCreation using OAS doc test case.
Add resources : swagger files json/yaml.
Update test.sh to copy reports for 1.1.2 level.
Update pom file to locate the resources from test case level.

Closed due to repo structure changed.


Table INSERT subscriptions fail with Error 401: Not Unauthorized

Describe the bug
I've subscribed to inserts on a table using the supabase api, when I add a row into that same table on the supabase web interface I receive notice that a change has occurred but not the content of the row that was inserted. I've ensured that the table has been added to the supabase-realtime channel just like the guide. I have tried to disable/enable RLS, giving all permissions to both anon and public roles, and also tried to use the api service key. None of these resolved the 401: unauthorized error.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Code to subscribe to channel, which I copied from the API tab on the web interface.
const { createClient } = require('@supabase/supabase-js')

const supabase = createClient(process.env.SUPABASE_URL, process.env.SUPABASE_KEY)

const coachMessages = supabase.channel('custom-insert-channel')
  .on(
    'postgres_changes',
    { event: 'INSERT', schema: 'public', table: 'coach_messages' },
    (payload: any) => {
      console.log('Change received!', payload)
    }
  )
  .subscribe()

console.log(coachMessages)

and the error:

Row insertion and database actions are done using the supabase web interface.
Expected behavior
A clear and concise description of what you expected to happen.
The payload to contain the row that was just inserted in the payload.new property.
System information

OS: macOS
Browser: Firefox
Version of supabase-js: 2.33.1
Version of Node.js: 18.16.0

I am having the same problem.

Ok, I think I got this to work but I am not sure as to why, maybe someone who is advanced in this topic maybe able to shed some light.
I turned off RLS for the table followed by:
grant select on table to anon;
as documented in  Bring your own database
after I did that, I get the payload.

Ok, I think I got this to work but I am not sure as to why, maybe someone who is advanced in this topic maybe able to shed some light.
I turned off RLS for the table followed by:
grant select on table to anon;
as documented in Bring your own database
after I did that, I get the payload.
UPDATE: I needed both anon and authenticated for my shopping cart so:
grant select on transactions to anon, authenticated;

That makes it work.

Ok, I think I got this to work but I am not sure as to why, maybe someone who is advanced in this topic maybe able to shed some light.
I turned off RLS for the table followed by:
grant select on table to anon;
as documented in Bring your own database
after I did that, I get the payload.
UPDATE: I needed both anon and authenticated for my shopping cart so:
grant select on transactions to anon, authenticated;

This worked for me as well, thank a lot.

Make sure you have the Authorization header set on the webhook as well, as that can cause a 401

The "Missing grants" section in the troubleshooting docs helper me fix this issue: https://supabase.com/partners/integrations/prisma#troubleshooting

I get an error when I try to set anon for my table, any other workaround?

I am hitting this problem as well.
I am watching for UPDATEs like so:
...
.on(
  "postgres_changes", { schema: "public", table: "Feed", event: "UPDATE" },
  (payload) => console.log("UPDATE", payload)
)
.subscribe()

All of my requests are via an authenticated client, so I only worry about the authenticated role.
I am finding that if I do not run grant select on "public"."Feed" to authenticated; then I get the 401 error, regardless of whether RLS is enabled for the given table.
If I run the grant command, then if RLS is enabled, the events don't fire -> now nothing gets console logged.
If I remove RLS, then the events fire properly, without the 401 error.
I am not sure why RLS would block the event like that - my only guess would be that the RLS is too restrictive, but this is my RLS policy:
create policy "policy_name"
on "public"."Feed"
as PERMISSIVE
for ALL
to authenticated
using (
  true
);

so I am being as insecure as possible with my RLS policy.

Same:

Ok, I think I got this to work but I am not sure as to why, maybe someone who is advanced in this topic maybe able to shed some light.
I turned off RLS for the table followed by:
grant select on table to anon;
as documented in Bring your own database
after I did that, I get the payload.
UPDATE: I needed both anon and authenticated for my shopping cart so:
grant select on transactions to anon, authenticated;

Thanks! That solves the problem.


large texts get really confused

When I apply tags to a very large text, the attributes start getting applied to strange locations in text. I tried playing with this but haven't yet detected a pattern.
Question: Is there a size limit for the text being tagged?

The problem might be in my text. I tried a very large "lorem ipsum" text and it worked fine. I'm trying to figure out what the problem is with my text. I hope to either figure out what's wrong with my text, or to be able to reproduce a problematic scenario.

If you have an example I'll be happy to check it thanks

Problem has been fixed in 2.x branch where the parser has been rewritten.
Attached the rendered version (with different colors) and the 2.x code (much simpler than before).
let styleBold = Style {
	$0.font = SystemFonts.Helvetica_Bold
	$0.size = 14
}

let styleCenter = Style {
	$0.alignment = .center
}

let styleStore = Style {
	$0.color = UIColor.red //UIColor(red: 255, green: 210, blue: 0, alpha: 1)
}

let def = Style {
	$0.font = SystemFonts.Helvetica
	$0.size = 14
	$0.color = UIColor.black //UIColor(red: 255.00, green: 255.00, blue: 255.00, alpha: 1.00)
}

let attributedString = body.set(style: StyleGroup(base: def, [
	"bold" : styleBold,
	"center" : styleCenter,
	"store" : styleStore
]))


Jenkinsfile

node('jdk11-mvn3.8.4') {
properties([pipelineTriggers([cron('0 */1 * * *')])])
stage('git') {
git 'https://github.com/GitPracticeRepo/java11-examples.git'
}
stage('build') {
sh '''
echo "PATH=${PATH}"
echo "M2_HOME=${M2_HOME}"
'''
sh '/usr/local/apache-maven-3.8.4/bin/mvn clean package'
}

@bhargavi-vaduguri Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

hi share me


Server side rendering

Currently, It is doing server-side rendering for post only. For feeds and users page actions need to changes to be promisable and work with route. For other pages, this can be broken into different PR.

@adcpm can you check now?
Sidebar is not loading because it is not using redux state.
Server rendering is working only post as of now So we should not remove title and description meta.

I try to share on Facebook and findout it doesnt link to busy but to steemit. Issue is og:url, it should always be busy.org, it's not same as canonical.

Also can you add " - Busy" on the end of article title?

Hum. For some reason, sharing on Facebook would not show image & description anymore.

Strange because that was not the case on last deployment. Something that may cause this is that we have actually 2  tag:

Maybe Facebook create image and description based on the URL of og:url.

yes that can be.
should we try with pr app url?

You can make that og:url use the current url origin.

Updated. Now it is working.

The method of setting origin now(using global)  is not good. we should eventually switch to env variable in future.


Django 1.9 Warnings

I just thought I should leave some warnings I got from Django because of moving to 1.8:
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/site-packages/social/apps/django_app/default/models.py:29: RemovedInDjango19Warning: Model class social.apps.django_app.default.models.UserSocialAuth doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class UserSocialAuth(models.Model, DjangoUserMixin):
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/site-packages/social/apps/django_app/default/models.py:67: RemovedInDjango19Warning: Model class social.apps.django_app.default.models.Nonce doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class Nonce(models.Model, DjangoNonceMixin):
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/site-packages/social/apps/django_app/default/models.py:78: RemovedInDjango19Warning: Model class social.apps.django_app.default.models.Association doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class Association(models.Model, DjangoAssociationMixin):
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/site-packages/social/apps/django_app/default/models.py:91: RemovedInDjango19Warning: Model class social.apps.django_app.default.models.Code doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class Code(models.Model, DjangoCodeMixin):
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/importlib/_bootstrap.py:321: RemovedInDjango19Warning: django.utils.importlib will be removed in Django 1.9.
return f(*args, **kwds)
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/importlib/_bootstrap.py:321: RemovedInDjango19Warning: The django.forms.util module has been renamed. Use django.forms.utils instead.
return f(*args, **kwds)
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/importlib/_bootstrap.py:321: RemovedInDjango19Warning: django.contrib.contenttypes.generic is deprecated and will be removed in Django 1.9. Its contents have been moved to the fields, forms, and admin submodules of django.contrib.contenttypes.
return f(*args, **kwds)
/Users/JJZ/Dropbox/AU/AUrepo/athletesunited/athletesunited/comments/models.py:19: RemovedInDjango19Warning: Model class athletesunited.comments.models.Comment doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class Comment(models.Model):
/Users/JJZ/Dropbox/AU/AUrepo/athletesunited/athletesunited/comments/models.py:134: RemovedInDjango19Warning: Model class athletesunited.comments.models.CommentFlag doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class CommentFlag(models.Model):
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/importlib/_bootstrap.py:321: RemovedInDjango19Warning: The utilities in django.db.models.loading are deprecated in favor of the new application loading system.
return f(*args, **kwds)
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/site-packages/social/apps/django_app/default/models.py:29: RemovedInDjango19Warning: Model class social.apps.django_app.default.models.UserSocialAuth doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class UserSocialAuth(models.Model, DjangoUserMixin):
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/site-packages/social/apps/django_app/default/models.py:67: RemovedInDjango19Warning: Model class social.apps.django_app.default.models.Nonce doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class Nonce(models.Model, DjangoNonceMixin):
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/site-packages/social/apps/django_app/default/models.py:78: RemovedInDjango19Warning: Model class social.apps.django_app.default.models.Association doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class Association(models.Model, DjangoAssociationMixin):
/Users/JJZ/.virtualenvs/athletesunited/lib/python3.4/site-packages/social/apps/django_app/default/models.py:91: RemovedInDjango19Warning: Model class social.apps.django_app.default.models.Code doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.
class Code(models.Model, DjangoCodeMixin):
I assume contributers are already aware because it's just a natural shift to Django 1.8 that caused these Django 1.9 warnings.
Thanks for your consideration.
JJ

See #551 which has been fixed.

These are already solved by #550

Oh that's weird, I will have to try to update my PSA again because I was pretty sure I made sure to update the package for this exact reason and I saw those warnings after I had updated. Maybe it's just a rookie mistake on my end in terms of missing something in terms of updating the package and it not fully updating but I was pretty sure I did it right. I will dig into this again and try again and see if all is good and report back any findings.

The change is not released into pypi yet.

Oh that must be it because I see that the versioning was updated to 0.2.4 but I only have 0.2.3 so yeah when the next release comes out like you already know and have said I think I'll be in good shape.

btw is there a timetable for when it would be released to the pypi? sorry if i don't know where i should be looking because i don't haha.

I do releases mostly by demand or when I feel the amount of changes are worthy a release. I've released v0.2.4 a few minutes ago.


EvolveAll not working?

config.json
      {
        "type": "EvolveAll",
        "config": {
          "evolve_all": "all",
          "evolve_cp_min": 0,
          "evolve_speed": 20,
          "use_lucky_egg": true
        }
nothing happens
a90a77abe0f6a59f1adc330ea7db40eb24470a7d

Look a few lines below, i guess after evolve all it says none in your config
"evolve_all": "Pidgey,Rattata,Weedle,Spearow,Drowzee",
"evolve_cp_min": 300,
"evolve_captured": "Rattata",

Under your item filter list theres another evolve option
"evolve_all": "Pidgey,Rattata,Weedle,Spearow,Drowzee",
"evolve_cp_min": 300,
"evolve_captured": "Rattata",

in the tasks you should just use
"type": "EvolveAll",
"config": {
"evolve_speed": 20,
"use_lucky_egg": false

Confirm that doesn't work. Even on this configuration.

@Nathanian not working for me

Same problem!

hm works for me, post you configs please

Are you sure you are on the latest dev commit?

Not sure my last update was 20 hours ago

Yes, your config file would be invalid on the latest commit.

Oh, i guess then its good that i didnt update yet, i hope your bugs get fixed soon

So i updated now and caught a few pidgeys and its evlolving just fine

{
"auth_service": "google",
"username": "xxx",
"password": "xxxx",
"location": "xxxxxx",
"gmapkey": "xxxxxxx",
"tasks": [{
"type": "HandleSoftBan"
}, {
"type": "CollectLevelUpReward"
}, {
"type": "IncubateEggs",
"config": {
"longer_eggs_first": true
}
}, {
"type": "TransferPokemon"
}, {
"type": "EvolveAll",
"config": {
"evolve_all": "Pidgey",
"evolve_cp_min": 0,
"evolve_speed": 20,
"use_lucky_egg": false
}
}, {
"type": "RecycleItems",
"config": {
"item_filter": {
"Pokeball": {
"keep": 100
},
"Greatball": {
"keep": 70
},
"Ultraball": {
"keep": 80
},
"Potion": {
"keep": 0
},
"Super Potion": {
"keep": 40
},
"Hyper Potion": {
"keep": 30
},
"Revive": {
"keep": 30
},
"Razz Berry": {
"keep": 50
}
}
}
}, {
"type": "CatchVisiblePokemon"
}, {
"type": "CatchLuredPokemon"
}, {
"type": "SpinFort"
}, {
"type": "MoveToFort"
}
],
"max_steps": 5,
"forts": {
	"avoid_circles": true,
	"max_circle_size": 50
},
"websocket_server": false,
"walk": 11.16,
"action_wait_min": 1,
"action_wait_max": 4,
"debug": false,
"test": false,
"health_record": true,
"location_cache": false,
"distance_unit": "km",
"reconnecting_timeout": 15,
"evolve_captured": "NONE",
"catch_randomize_reticle_factor": 1.0,
"catch_randomize_spin_factor": 1.0,
"catch": {
	"any": {
		"catch_above_cp": 0,
		"catch_above_iv": 0,
		"logic": "or"
	},
	"// Example of always catching Rattata:": {},
	"// Rattata": {
		"always_catch": true
	}
},
	"release": {
		"Magikarp": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Dratini": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Dragonair": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Eevee": {
			"keep_best_cp": 3,
			"keep_best_iv": 0
		},
		"Electabuzz": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Jynx": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Goldeen": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Horsea": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Krabby": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Hypno": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Gastly": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Haunter": {
			"keep_best_cp": 2,
			"keep_best_iv": 0
		},
		"Shellder": {
			"keep_best_cp": 3,
			"keep_best_iv": 0
		},
		"Cloyster": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Magnemite": {
			"keep_best_cp": 2,
			"keep_best_iv": 0
		},
		"Abra": {
			"keep_best_cp": 2,
			"keep_best_iv": 0
		},
		"Poliwag": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Golbat": {
			"keep_best_cp": 2,
			"keep_best_iv": 0
		},
		"Zubat": {
			"keep_best_cp": 3,
			"keep_best_iv": 0
		},
		"Jigglypuff": {
			"keep_best_cp": 2,
			"keep_best_iv": 0
		},
		"Fearow": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Spearow": {
			"keep_best_cp": 4,
			"keep_best_iv": 0
		},
		"Raticate": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Pidgeotto": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Pidgey": {
			"keep_best_cp": 5,
			"keep_best_iv": 0
		},
		"Rattata": {
			"keep_best_cp": 5,
			"keep_best_iv": 0
		},
		"Bellsprout": {
			"keep_best_cp": 2,
			"keep_best_iv": 0
		},
		"Seel": {
			"keep_best_cp": 10,
			"keep_best_iv": 0
		},
		"Magmar": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"Seadra": {
			"keep_best_cp": 1,
			"keep_best_iv": 0
		},
		"any": {
			"keep_best_cp": 5,
			"keep_best_iv": 0
		},
		"// Example of always releasing Rattata:": {},
		"// Rattata": {
			"always_release": true
		},
		"// Example of keeping 3 stronger (based on CP) Pidgey:": {},
		"// Pidgey": {
			"keep_best_cp": 3
		},
		"// Example of keeping 2 stronger (based on IV) Zubat:": {},
		"// Zubat": {
			"keep_best_iv": 2
		},
		"// Also, it is working with any": {},
		"// any": {
			"keep_best_iv": 3
		},
		"// Example of keeping the 2 strongest (based on CP) and 3 best (based on IV) Zubat:": {},
		"// Zubat": {
			"keep_best_cp": 2,
			"keep_best_iv": 3
		}
	},
	"vips": {
		"Any pokemon put here directly force to use Berry & Best Ball to capture, to secure the capture rate!": {},
		"any": {
			"catch_above_cp": 1200,
			"catch_above_iv": 0.9,
			"logic": "or"
		},
		"Lapras": {},
		"Moltres": {},
		"Zapdos": {},
		"Articuno": {},

		"// S-Tier pokemons (if pokemon can be evolved into tier, list the representative)": {},
		"Mewtwo": {},
		"Dragonite": {},
		"Snorlax": {},
		"// Mew evolves to Mewtwo": {},
		"Mew": {},
		"Arcanine": {},
		"Vaporeon": {},
		"Gyarados": {},
		"Exeggutor": {},
		"Muk": {},
		"Weezing": {},
		"Flareon": {}

	}

}

I have the same issue with the same configuration proposed by sample json


Edge controller: only define GCP credentials env var when secret exists

This is what we do for the other charts as well, and makes it possible to use the edge controller from e.g minikube using CLI credentials in a testing context. This is convenient for development and for potential users who just want to kick the tires without provisioning service accounts.

Do we still want this? Has it gone stale?

Closing for inactivity. If we want this we can revisit - I've not heard complaints about it.


Support Revision and Branch attributes

Whats New

Package Generator Support revision attribute
Package Generate Support branch attribute
Adds Tests
Updates Readme

@victor-sarda @albertodebortoli would it be possible for any of you guys to take a look?

Hi @emans thank you so much for your contribution! 👏
Changes look good to me and I've run the tests locally (we'll add a GitHub Actions workflow for pull requests later).
Just waiting for a check from @victor-sarda.


Release 0.3.23

@JuliaRegistrator register(branch=release)

Registration pull request created: JuliaRegistries/General/15324
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.23 -m "<description of version>" 675d740a0b92446449f2dee284a1ae34c2cabf3e
git push origin v0.3.23


about some implementation issues

Thank you for your sharing~
However I have some doubts,

this code represents the weight value is calculation by using channel dimension on the same spatial position, rather than applying spatial region?
https://github.com/alexandrosstergiou/SoftPool/blob/7cd12c72b7096bc70d136e6b001eb2c338461bb2/pytorch/SoftPool/idea.py#L181

for the last pooling layer, global avg pooling is better than softpool?

Looking forward to your reply

Hi @dlyldxwl,
Thank you for pointing (1.) out. The non-native CUDA functions have not been updated for a while. I'll include this in the latest commit. Do note that you are encouraged to use the CUDA-native versions CUDA_SOFTPOOLxd for better performance. The in-place alternatives are less stable by nature.
As for using SoftPool for vectorisation, we have not tested this as the paper was focusing on sub-sampling image/video regions. But you can of course try it out yourself. I would be interested in the results as well if you do!
Best,
Alex

Hi @dlyldxwl,
Thank you for pointing (1.) out. The non-native CUDA functions have not been updated for a while. I'll include this in the latest commit. Do note that you are encouraged to use the CUDA-native versions CUDA_SOFTPOOLxd for better performance. The in-place alternatives are less stable by nature.
As for using SoftPool for vectorisation, we have not tested this as the paper was focusing on sub-sampling image/video regions. But you can of course try it out yourself. I would be interested in the results as well if you do!
Best,
Alex


chore: correct copy/paste error and add debugging print stmt

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Correcting copy/paste error
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[x] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[x] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

/azp run


Automatically generate MAGICC worker root directory

Automatically generate MAGICC worker root directory as a temporary directory if MAGICC_WORKER_ROOT_DIR is not given. This is just a quality-of-life change to make it easier to "just run" magicc with as little boilerplate as possible.
I also did some light refactoring while understanding the code:

added type hints to various functions
reordered a try/finally block to make sure uninitialized variables aren't used in the finallyblock.

This PR is based on https://github.com/openscm/openscm-runner/pull/66 to avoid merge conflicts in CHANGELOG.rst down the line, so #66 should be merged before this one here.

[ ] Tests added
[x] Documentation added
[ ] Example added (in the documentation, to an existing notebook, or in a new notebook)
[x] Description in CHANGELOG.rst added (single line such as: (`#XX <https://github.com/openscm/openscm-runner/pull/XX>`_) Added feature which does something)

Uh, the CI doesn't have pymagicc, so the type hinting doesn't work on Python pre-3.10.

Yay, the CI likes my PR too! :blush:


SOLR-16002: don't double-cache FilterQuery

See: SOLR-16002

@dsmiley I merged main into this branch (including PR #529), and the test still fails for me without the modifications in SolrIndexSearcher (I'm pretty sure about this).
Also addressed the refactoring comments; thanks for the review!

I'm confused at our differing experience.  I just updated and added an assert false; immediately before the docCache = false; you added in SIS.  The test still passes for me.  A breakpoint doesn't make it there either.  If you see a failure, then can you share the stacktrace for the assertion?

That's definitely strange!

on f29144a849c5758b053ae30b8e0e95126824ec97 (PR branch current HEAD)
run git diff apache-solr/main... -- solr/core/src/java/org/apache/solr/search/SolrIndexSearcher.java | git apply -R (reverts the changes this PR made to SolrIndexSearcher, wrt merge-base with main)
gradlew :solr:core:test --tests "org.apache.solr.search.TestFiltersQueryCaching.testRecursiveFilter" -Ptests.jvms=4 -Ptests.jvmargs=-XX:TieredStopAtLevel=1 -Ptests.seed=8983C499E841DCAC -Ptests.file.encoding=ISO-8859-1:

   >     java.lang.AssertionError: expected:<1> but was:<2>
   >         at __randomizedtesting.SeedInfo.seed([8983C499E841DCAC:E754A78A6DD76190]:0)
   >         at org.junit.Assert.fail(Assert.java:89)
   >         at org.junit.Assert.failNotEquals(Assert.java:835)
   >         at org.junit.Assert.assertEquals(Assert.java:647)
   >         at org.junit.Assert.assertEquals(Assert.java:633)
   >         at org.apache.solr.search.TestFiltersQueryCaching.testRecursiveFilter(TestFiltersQueryCaching.java:87)
   >         at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   >         at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   >         at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   >         at java.base/java.lang.reflect.Method.invoke(Method.java:566)
   >         at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1754)
   >         at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:942)
   >         at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:978)
   >         at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:992)
   >         at com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
   >         at org.junit.rules.RunRules.evaluate(RunRules.java:20)
   >         at org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:44)
   >         at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
   >         at org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
   >         at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
   >         at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
   >         at org.junit.rules.RunRules.evaluate(RunRules.java:20)
...

immediately before the docCache = false; you added in SIS
docCache=false had to be added in two places in SIS ... just making sure, because if you only reverted one place, maybe the other code path is the relevant one in the context of the test?

WrappedQuery would then be non-final, but it's constructor would be package-private to restrain abuse.  Instead it could have a "wrap" static.  For even greater ease-of-use, that wrap method could take the cache & cost values as parameters and only conditionally actually wrap if they differ from defaults.  Just an idea.

Hmm... the danger with that is that although FilterQuery does wrap a query, the semantics of WrappedQuery are that the inner query should be accessible, and that at a certain point in the docset-creation-from-query code it is proper to "unwrap" the query and run the inner query.
The semantics of FilterQuery are different. If there's a way to provide access to the backing query, it can't/shouldn't be leveraged in the same way that it is for WrappedQuery, so the "instanceof" checks for WrappedQuery would not be appropriate to use I think.
What if FilterQuery (which already extends ExtendedQueryBase) simply overrode getCache() to be final and always return false? Then we'd have the "paradoxically" note in that overridden method, no special cases in SIS.

what I didn't like about it is that it blocks using FilterQuery to mean filter but not cache.

I think I follow? Yes, FilterQuery here is as in FilterQuery.java, which is really specific, almost always invoked via filter([backing_query]), when you want consult the filterCache for the backing query in a context where it would normally not consult the filterCache. This is particulary useful, e.g., for fine-grained control of how subclauses in queries are cached. That use-case/concept doesn't go away if there's a closer relationship between fq and FilterQuery ... if anything I could see renaming FilterQuery to be more clearly distinct from fq (in fact, it's hard to search Jira for issues related to FilterQuery because that term is indeed often used informally to refer to fq).
So, just to clarify, your comment above should no longer be a concern (i.e., fq={!cache=false}foo:bar would definitely still work as it currently does)? What this PR does is make it so that fq=filter(foo:bar) would only cache one query, not two. And, for good measure, fq={!cache=false}filter(foo:bar) would still hit the filterCache via the filter(...) wrapper.

Sorry, I misunderstood what you meant in your comment above. But in any event I still think the concern is not warranted:

fq=filter({!cache=false}foo:bar) would currently cache the FilterQuery, but not the inner query, so subsequent requests for fq=foo:bar would not be a cache hit.
fq=filter(foo:bar) currently caches twice, this PR would cause to only cache foo:bar
fq={!cache=false}filter(foo:bar), oddly, would currently only cache the inner query (behavior equivalent to what this PR introduces as the default for fq=filter(foo:bar)
fq={!cache=true}filter(foo:bar) -- i.e., explicitly requesting that the FilterQuery per se be cached, would throw an IllegalArgumentException under the new PR, and on current main the behavior of this would be equivalent to fq=filter(foo:bar): double-caching. I mean, we could skip the IAE, but this is really really wrong -- I can't think of any circumstance where you'd actually want this.
And yes, you'd be better off with (foo:bar)^=1 for an explicit ConstantScoreQuery; currently in order to support the use case you mention (using FilterQuery to filter but not cache), iiuc you'd have to do this: filter({!cache=false}foo:bar)!

Well fq=filter(foo:bar) OR foo:baz is already supported, and this PR wouldn't change that particular example; and yes this example illustrates one reasonable use of filter(...): to separately consult the filterCache for the foo:bar subclause, in addition to consulting filterCache (in this example) for the overall fq.
So appropriately, this example would result in two filterCache consultations. This PR addresses the case where fq and filter(...) are coterminous -- where they represent exactly the same fundamental query, but would currently be cached twice.
I guess the way I think about it, filter(...) gives you arbitrarily granular control over how subclauses get cached. The fq=filter(...) example is really straightforward, but is admittedly unlikely to come up in "real world" use. The use that initially motivated my interest in this is perhaps informative: the relatedness JSON facet function accepts a single query arg to define its "foreground set". For obvious reasons, I wanted to define the foreground set to be "the combination of main query and filters", but I found that doing so via the FiltersQParser ({!filters param=$q param=$fq}) resulted in consulting the filterCache for the top-level combination of q&fq, not finding it (of course), and running all the underlying queries without consulting the cache! Having fixed FiltersQParser to generate FilterQuery instances for its individual subclauses (separate PR forthcoming), I found that each of the subclauses was getting cached twice: once as the clause's underlying query, and once as the clause's FIlterQuery wrapper. That behavior is what this PR fixes, and the behavior that the associated test is designed to evaluate.

Thanks again David and Mike; I just wanted to call out one minor change (in 1b4d7d1a380ae420ea99328929e8b7b52e9a0e33): instead of throwing an IllegalArgumentException upon attempting FilterQuery.setCache(true), we now silently ignore this at the implementation level, considering that because of what FilterQuery is, the higher-level semantics of setCache(...) are actually better respected by a lenient approach. I've added a detailed comment in the setCache() method, and built out the test method to cover related cases.
I plan to commit tomorrow, pending further feedback/concerns.


Upgrade auth dependencies to 0.14.0.

To then upgrade gax in google-cloud-java.

@vam-google PTAL

Can the com.google.http-client be updated to 1.29.0? https://github.com/googleapis/google-auth-library-java/blob/6ad960441490636afd8d260e04a588a30efbba1a/pom.xml#L47

good catch, yes!


[Docs Cloud Native app Configuration] - Grammar adjustment

Current State
Link: Configuring your Cloud Native Infrastructure and Applications

Section: Creating a Meshery Design
Currently, this sentence reads as follows: "You have your choice of how are you would like to create an infrastructure design."
Desired State
For increased readability and user experience the sentence could read as follows: "You are free to choose how you would like to create an infrastructure design."
Screenshots

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Hi @sandramsc , I would like to work on this issue!

Hi @shourya2002-geek I have assigned this to you.


Support placement of other type of locations than recycling trash cans

Currently the main purpose is to guide towards recycling trashcans. However we can easily add the capability to place other type of markers, such as campus buildings and landmarks. This would just need and extra field (comma separated addition to the existing comma separated XML content rows). Then we can switch to the regular red map pin marker (both in 2D and 3D).
This would make the app more universal.

The Science 2, Planetarium and the P5/P6 link is still a little bit off (looks like GMaps is off in general compared to Google Earth!), but good to go for test

Related ticket for the companion website https://github.com/RecyclingTrashCans/RecyclingTrashCans.github.io/issues/11

Released


Add Argon2 hashes

Vote on this issue by adding a 👍 reaction.
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Is your feature request related to a problem? Please describe.
I miss possibility to use argon2 hashers.
Describe the solution you'd like
I'd love to be able to hash a string using argon2i/argon2d/argon2id.
Describe alternatives you've considered
Use the https://argon2.online/
Additional context
It should be separate option, as this hash needs salt, parallelism factor, memory cost, iterations and hash length

I'd like to work on that. I already implemented a simple version for Argon2i Hashes

Just let me know what you think could be enhanced or if you are happy with the layout 👍

@david-ruitter Wow, I'm so glad you want to work on that!
I would have a few suggestions to your design, but foremost I want to say it's excellent, and I can't wait to see it in work. What I want to suggest is:

Add the result field for encoded hash (i.e. $argon2i$v=19$m=16,t=2,p=1$blNMdWl5RVZ2bGgyc2tucw$Km2yJvJPsf2sp8TRyliTVA).
Add the ability to choose between Argon2i, Argon2d and Argon2id.
Add the ability to randomize 16-chars salt (including upper and lower case letters and digits).

I'm also wondering if every row of the configuration must take the whole width, a lot of space is wasted. However, the description can be quite long and shorter field can look far worst. It's simply to consider.
But as I said, I'm so happy you are going to implement it. Kudos from me!

@Andret2344 Thanks for the nice feedback!
I'm going to start working on the points you stated here 👍
As for the design i took inspiration of how other tools look like, maybe @veler could also add his opinion on this.
Best Regards

Hi,
Thank you for suggesting this idea and thank you @david-ruitter for starting an early implementation!
I should admit I'm not familiar with Argon2 at all. I'm discovering it while reading this ticket. :)
I'm not opposed to the addition of such a tool but would like to make sure I understand a few things:

My understanding from Argon2 is that it's a hashing technique for password (mostly? please educate me on the subject since I'm not familiar with it 😅). In what scenario would you need to manually generate such a hash? (I think I have an answer but would love reading an example from you folks)
In term of implementation, is there an existing .Net library for it or do we need to implement it ourselves?
Any idea of how often Argon2 is used? Just asking because, again, I never heard of it before (it's been years I didn't deal with passwords) 😅

Regarding the UI, I like it overall. Of course, we will need to figure out a good icon for it but that's something we can figure out later.
I second what @Andret2344 mentioned. In short, having the exact same set of features than https://argon2.online/ may be the right thing to do, unless you have arguments against that (I don't know, perhaps these extra features aren't that useful?).
For generating a salt automatically, we may need to add a button next to Paste. The current Paste button, TextBox and Header are all part of a same control CustomTextBox. We will need to edit this control to add the button for generating the salt.
Since this extra button isn't common to other tools, I'd suggest making the button customizable through some new properties in the control that would allow to:

Set the text of the button. Having a text defined could be a sufficient condition to make the control visible.
The button could appear to the left of other ones above the TextBox.
Let's add a ICommand property that would allow to execute a command when clicking the button.

This way, when consuming the control in the tool's UI, we would have to set the button text and a command to be able to run something when the user clicks on it. What do you think of this approach?
Alternatively, we could simply put a button outside of the CustomTextBox control, either above or to the right of it.

Thanks, @veler for taking part in discussion ;)
To answer your doubts:

You're right, Argon2 hashes are used mostly (if not only) in password hashing.
The scenario to manually generate it is something I faced multiple times, when developing symfony (PHP) backend webpage. I choose to use Argon2 as the most secure option, as in 2015 it won the Password Hashing Competition and is dedicated to password hashing since then. When I want to test logging to my service, I need to manually change passwords in database (assuming my service is growing, and no dedicated way exists), or creating new users to test. In general, authentication testing purpose.
Due to O letter in SOLID acronym, what means "Open-close principle" defined as "Open for extensions, closed for modifications", I agree that extending the component to optionally added fourth button and add its behavior is better than separated component. However, I'm not familiar with C# at all (#javadev here), so I may be wrong.

In addition, @david-ruitter, when you are ready with all the functionality, ping me, I can translate to Polish :D
BR

Gotcha, thank you for all these explanations. :)
@david-ruitter, feel free to keep working on it at your rythme.

node -e "require('argon2').hash('12345').then(data => console.log(data));" the poor man's argon example hash :D

Hi,
This is a good idea for an extension, but I don't think it fits DevToys' default tools.
Thanks


[kwokctl] Add test to create two clusters for all runtimes

What would you like to be added?
TODO
Why is this needed?
Verify that the two cluster ports do not conflict.

/triage accepted
/good-first-issue


[mwc-icon-button] display label as hint (tool tip)

Imagine many mwc-icon-button are placed on mwc-top-app-bar.
It is desirable for users to see the label value of 'mwc-icon-button' as hint or tool tip when they hover their mouses over each of these elements just as legacy polymer paper-icon-button does.

Hey @masaoliou !
Thanks for this suggestion, I think that's a good suggestion. I will talk to the team!

Hey @masaoliou
After conferring with the team, we have a screen reader accessible tooltip in the pipeline (feel free to track our progress with #1499). Currently we don't recommend the feature you're trying to implement. But, again, we have a tooltip in development.
You can provide a "title" attribute to any of our elements and the browser will render the text, however it has accessibility issues which is why we recommend waiting for our official tooltip.
Thanks


package.json browser field cannot be converted in acquireWebNodePaths

Does this issue occur when all extensions are disabled?: Yes.
In the fact, this problem is not encountered in actual use, but a bug encountered when I tried to modify VS Code.

VS Code Version:   1.73.0   be022daa1af42d
OS Version:   Macos 12.2.1  Intel

Steps to Reproduce:

Clone VS Code source code
yarn install
Add dependencies to remote/web/package.json.For example, add react-dom to simulate scenarios where dependencies need to be added to vscode-web., then yarn add react-dom under the root directory.
Use cmd + shift + B shortcut keys to perform  Core - Build and Ext - Build tasks. Then you will find that the mission unexpectedly quit.

The problem is that browser fields can be not only string but also objects.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.72.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!


[llc] Add "no auth" support

Fixes https://github.com/Azure/autorest.csharp/issues/1221

Checklist
To ensure a quick review and merge, please ensure:

[x] The PR has a understandable title and description explaining the why and what.
[x] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[x] The branch is recent enough to not have merge conflicts upon creation.

Just realized we have protocol_method_client.md to update.


Web - Emoji selector covers LHN when clicking add reaction bubble below a comment

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to any chat.
React to a comment.
Click on the "add reaction bubble"

Expected Result:
Emoji picker should not cover the LHN and should be shown towards right.
Actual Result:
Emoji picker partly covers the LHN
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.55-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/2ece5051-4c63-4041-abfc-b833f274edd5
https://github.com/Expensify/App/assets/115492554/56765d7c-8996-4eec-9c7c-ab2f8b7fd31a
Expensify/Expensify Issue URL:
Issue reported by: @c3024
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691314449495069
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
Emoji picker should be moved to the right so that it doesn't cover LHN
What is the root cause of that problem?
The root cause of the problem is how anchor for the Emoji Popover is calculated, and how it's origin is set. The popover is anchored to top right corner and facing the left side, which causes it to cover LHN.
What changes do you think we should make in order to solve the problem?

The easiest and quickest solution (1-line change) would be to make the popover face right-hand side instead of left-hand side.
We could tweak how emoji picker origin is set, this way the position of emoji picker will be calculated properly, and it will stick to top right corner of Emoji picker button facing right-hand side. Here you can see how it is displayed after the changes:

Screen shots

What alternative solutions did you explore? (Optional)
Another way to solve this problem (which may be better in terms of UX) would be to tweak emoji popover so that it behaves just like the one in slack (screenshot below), in a nutshell it would be anchored to top left corner of Emoji picker button while facing right-hand side.
However we would need to change a little more in the code itself as it requires some customization in the way that the position of popover is calculated.

How slack emoji popover reacts (Screen shot)

Here you can see how emoji picker is anchored differently

Proposal
Please re-state the problem that we are trying to solve in this issue.
The problem is that when we click add reaction bubble below a comment. Emoji selector covers LHN
What is the root cause of that problem?
The root cause of the problem is here:
https://github.com/Expensify/App/blob/6319e59c29bf7304654e4ede3c2215a6e65016bf/src/components/EmojiPicker/EmojiPicker.js#L47
Prop anchorOrigin is undefined  So it was set to the default value.
https://github.com/Expensify/App/blob/6319e59c29bf7304654e4ede3c2215a6e65016bf/src/components/EmojiPicker/EmojiPicker.js#L14
And the horizontal origin is ‘right’
What changes do you think we should make in order to solve the problem?
We can pass in the anchorOrigin value with a horizontal origin of 'center', or simply set the default horizontal origin  to ‘center'
What alternative solutions did you explore? (Optional)
None
Result

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01225df0c309fea73e

I don't think this is a bug or one worth solving right now, closing and thanks for reporting!


Use same beacon API ports for all Eth2 clients

Consider using the same beacon API port for all the eth2 clients for consistency (for instance the dappmanager could require this API for the module chain drivers to get beacon sync status)
Use port 3500 for Prysm, Lighthouse, Teku, ?

closed by https://github.com/dappnode/DAppNodePackage-Teku-Prater/pull/24


Use an init method for the SDK to handle SSL pinning cert name

Description:

The public key certificate name for SSL pinning in the sendRequest method is currently hardcoded.
As an init method can be used for initializing some of the functions in the SDK, the name of the certificate can be passed as a param to that method. In production mode, it can be set to initialize without the cert name argument by which a default value will be used in the method.

Duplicate: https://github.com/wso2-incubator/identity-outbound-auth-push/issues/103


Question about better quality models for 48 kHz

Do you have better quality models for 48 kHz?
I've been helpful if you add 32 kbps, 48 kbps, 64 kbps and 96 kbps models to compare to MP3 / AAC / Windows Media Audio.
Thanks for the support!

@StephanAXX: I'm not from Meta :-) Question to you: do you know if the 48 kHz model can do mono coding? Or is it only stereo?

(In reply from listen17):

@StephanAXX: I'm not from Meta :-) Question to you: do you know if the 48 kHz model can do mono coding? Or is it only stereo?

Only stereo, the 48 kHz model can't do mono! The 24 kHz model can do only mono, no stereo! Mono encoding to the 48 kHz model will be added soon!


Thanks for maintaining this!

I just want to thank you all for open sourcing ZetaSQL and constantly keeping it up to date. I haven't even discovered its full potential but it's helped a lot to build really nice column level lineage tools.
I've written a small blog post about how we are using it right now to parse all our dbt models in BigQuery https://medium.com/data-monzo/mapping-our-data-journey-with-column-lineage-56209c00606d
Again, thanks team!! ❤

Thanks for the note!


Add batch search

First of all, thanks a lot for your work, it's really great !
In order to user the search on lots of documents, it would be great if we could :

[ search batches of elements] : embeddings.search(queries, top_k) which would return a list of top_k results for each query in queries
[use fastest lib to do so  ]  (I use hnsw implem of nmslib which provides a batch search and great implementation of hnsw).

Keep up the good work !

Thank you for the suggestion and kind words! Will look into batch search.
Regarding nmslib, the reason I went with the header library was that nmslib was fuzzy on the license. It mentioned a core piece was GPL. I'll research this further.

Thanks for your answer
Sorry I did not look a the license issue.
As hnswlib is created by the same team, it provides batched queries with knn_query :

I believe Faiss supports it the same way by juste passing matrix queries instead of vector query.
Annoy doesn't seem to expose such a functionnality.

Better late than never but this is addressed in v2.0 of txtai

Better late than never but this is addressed in v2.0 of txtai


Cue not applying constraints properly

What version of CUE are you using (cue version)?

$ cue version
cue version v0.2.2 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What did you do?

Given a CUE file
import networkingv1 "k8s.io/api/networking/v1"

network_policy: networkingv1.NetworkPolicyList & {
	apiVersion: "v1"
	kind:       "List"
}

network_policy: items: [{
        this_field: "should not work"
}]

What did you expect to see?
This should not compile, as the kind of items is ...networkingv1.#NetworkPolicy, which are closed structs.
What did you see instead?
It compiles.

The following snippet works as expected.
import networkingv1 "k8s.io/api/networking/v1"

network_policy: [...networkingv1.#NetworkPolicy]

network_policy: [{
        this_field: "should not work"
}]

Output
network_policy.0: field "this_field" not allowed in closed struct:
    ./test.cue:6:21

@uhthomas Can you try with CUE v0.3.0-beta.7?
There have been significant changes since v0.2.x and we are nearing a v0.3.0 release
Could you also show a more complete example (the NetworkPolicyList is missing above`)
Preferably, if you could create a reproducer with beta.7 using the guide found at this link, that would be great.
https://github.com/cuelang/cue/wiki/Creating-test-or-performance-reproducers

Yes, sorry.
I was actually using v0.3.0-beta.5. Have confirmed the same behavior with v0.3.0-beta.7.
The NetworkPolicyList is gettable via cue get go k8s.io/api/networking/v1.
For convenience however, please refer to automata to see the generated definition.

is the network_policy: networkingv1.NetworkPolicyList & { (without the # for a definition a typo?)

This appears to have your desired output, both cases fail. I believe this represents the situation
cue eval
-- cue.mod/module.cue --
module: ""
-- cue.mod/pkg/foo.bar/lib/main.cue --
package lib

#A: {
        foo: string | *"bar"
}

#L: {
        name: string
        items: [...#A]
}
-- main.cue --
package repro

import (
        "foo.bar/lib"
)

ex1: lib.#L & {
        name: "ex1"
}

ex1: items: [{
        this_field: "should not work"
}]

ex2: [...lib.#A]
ex2: [{
        this_field: "should not work"
}]

ex1.items.0: field this_field not allowed:
    ./cue.mod/pkg/foo.bar/lib/main.cue:3:5
    ./cue.mod/pkg/foo.bar/lib/main.cue:9:13
    ./main.cue:7:6
    ./main.cue:12:2
ex2.0: field this_field not allowed:
    ./cue.mod/pkg/foo.bar/lib/main.cue:3:5
    ./main.cue:15:10
    ./main.cue:17:2

You're correct, I was missing the #. 😬
Thank you.
Although this was definitely a confusing typo, I still imagine CUE probably shouldn't compile under these conditions.
Both the following do not compile:
a: [...A]

#A: {}

b: [...A]

As such, I would have expected my example earlier to also not compile.

Although interestingly, when packages get involved, it does...
cue eval
-- cue.mod/module.cue --
module: ""
-- cue.mod/pkg/foo.bar/lib/main.cue --
import "foo.bar/lib/other"

[...other.A]
-- cue.mod/pkg/foo.bar/lib/other/other.cue --
package other

cue export will likely fail, cue eval prints an incomplete object. This is because imported packages are open, there's a comment from @mpvl about considering changing this, but that is why an error is not occuring unless you ask for a concrete value.

Have just tested and cue export is happy too, which is consistent with what I was seeing earlier.
I assume it shouldn't be?

I'd guess there is another typo?
I cannot repro given the examples above which are producing the expected results

I didn't populate it was any data, so it looks like it didn't fully evaluate in my example.
Pass:
import networkingv1 "k8s.io/api/networking/v1"

a: [...networkingv1.NetworkPolicyList]

Fail:
import networkingv1 "k8s.io/api/networking/v1"

a: [...networkingv1.NetworkPolicyList]

a: [{}]

Not sure if that is a bug or expected behavior.

I definitely see that it was exported incorrectly, as kubectl complains about it.
For context, I'm using Bazel and rules_cue which seems to use cue def, so maybe it gets skipped?

cue def does not enforce concreteness, maybe that should be a cue export

It looks like it ends up collecting all those defs and then exports them. See here. I wonder if something in the chain breaks it.

Yeah, so cue export does fail as expected when the # is removed, but exporting with Bazel works okay.
I am inclined to say this probably isn't a fault with rules_cue simply because it's using the standard cue tool under the hood.
Should cue def have better enforcement of correctness?

I'm not familiar with Bazel
In https://github.com/uhthomas/rules_cue/blob/master/cue/cue.bzl
with the dep / merge stuff
is that

for each dep, cue def, zip
for each dep, zip... later cue def the entire tree with the root?

cue def is not meant to enforce concreteness by default. You might look at cue vet -c as a check

Okay, have done some playing and it looks like cue def behaves really weirdly.
Given the CUE file
import networkingv1 "k8s.io/api/networking/v1"

a: networkingv1.NetworkPolicyList & {}

Fail
$ cue def test.cue -o d.json
a: undefined field NetworkPolicyList:
    ./test.cue:3:17

Pass (incorrect)
cue def test.cue > d.json

d.json then contains an invalid definition.

in the first case, you are asking CUE to output JSON, which requires a concrete value
in the second case, you are asking the shell to put CUE's output into a file called d.json .There is no type information here and cue def defaults to outputting CUE code

Note, there are inconsistencies in CUE's commands which have a work item to clean them up and make them consistent. I'm not finding a specific issue, but it has been raised in comments somewhere

@uhthomas what commands where your running when you say "compile"?
Yes, it should fail. The faulty v1.NetworkingPolicyList results in an incomplete error because v1 exists and is not closed (arguably imports should be implicitly closed, as they are fully resolved at the time they are used, but that is another topic). This means it does not generate an error as it could theoretically still be resolved later.
However, at some point it should change that temporary error into a permanent error, which seems to fail to happen here.
The def behavior is explainable: for generating CUE using def incomplete errors are ignored, as they could still be satisfied later by making a configuration more concrete. In this case, of course, that would require making a package more concrete, which is maybe being too optimistic.
Using cue def -o x.json, however, exporting it to a json file, effectively turns cue def into an export. CUE is aware of the filetype you're exporting to here, and knows. Note that for cue def > x.json CUE is not aware of the file type: in this case it is a file redirect, which is a shell feature. In this case CUE outputs to CUE, and since it is cue def, permitting incomplete errors.
There should be an open issue related to this, but cannot find it. @myitcv?

Okay, it took a little bit of playing but I have got a working example of cue export misbehaving.
Please refer to https://github.com/uhthomas/cue854 which explains in detail.

@uhthomas - thanks for reproducing this issue.
@mpvl the related issue that comes to mind is https://github.com/cuelang/cue/issues/629, although that's a slightly different context because it's talking about disjunctions masking issues/errors.
In this case I think there is actually a genuine error here. The regression happened as part of bedb047a988217bab040c29eeb8a51988ce23b76, so post-beta.3:
! exec cue export
cmp stderr stderr.golden

-- a.cue --
package a

import "mod.com/b"

theb: b.name
-- b/b.cue --
package b

import "mod.com/c"

b: c.c & {
	other: "name"
}

name: b.other
-- c/c.cue --
package c
-- cue.mod/module.cue --
module: "mod.com"
-- stderr.golden --
b: undefined field c:
    ./b/b.cue:5:6

With beta.3 this passes; with beta.4 (or indeed any commit including bedb047a988217bab040c29eeb8a51988ce23b76) fails with:
> ! exec cue export
[stdout]
{
    "theb": "name"
}
FAIL: /tmp/testscript235319619/repro.txt/script.txt:1: unexpected command success

I'll update the description with this repro to save others have to read through the entire thread to get to the punchline.

This issue has been migrated to https://github.com/cue-lang/cue/issues/854.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


bad gateway error: php7.0-fpm.sock not working

After a clean install a bad gateway error is shown.
In the error log you will find this:
2016/02/04 15:33:47 [crit] 1634#0: *13 connect() to unix:/var/run/php/php7.0-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: <IP_ADDRESS>, server: homestead.app, request: "GET / HTTP/1.1", upstream: "$
My quickfix:
Change the fastcgi_pass item in the config file of the virtual host to:
fastcgi_pass unix:/var/run/php5-fpm.sock;

Your vagrant box is outdated. Run vagrant box update while in a homestead improved cloned folder and the problem will be solved.
Homestead Improved now uses PHP 7 by default, which is why your error appears (it's still using the old box but new configuration).

Thank you,
Tried vagrant box update
that still gives this error on provision:
==> default: php7.0-fpm: unrecognized service
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
And still gives the 502 Bad Gateway

An update won't automatically update the box you're in, counter-intuitively. You need to start a new box in order for this to work. Could you give that a go?

Worked like a charm, txs for the hint.
(deleted all homestead boxes and ran vagrant up)


Input is blurred whenever a letter is typed (iOS)

🐛 Bug Report
I'm trying to use an input component and setState as in the example in this repo. However, for whatever reason, when the user types a letter, the input is blurred and the keyboard disappears meaning you can only type one letter at a time
To Reproduce
I'm currently using it paired with List & renderHeader:
import React, { useState } from 'react'
import { View } from 'react-native'
import ConversationSummary from '../../components/ConversationSummary'
import { Wrapper, List, Header } from './styles'
import { useTheme, Input } from '@ui-kitten/components'

export default function ConversationList() {
  const theme = useTheme()
  const [searchTerm, setSearchTerm] = useState('')
  const backgroundColor = theme['background-basic-color-4']
  const conversations = [null, null, null, null]

  const renderHeader = () => (
    <Header level="1" backgroundColour={backgroundColor}>
      <Input placeholder="Search" value={searchTerm} onChangeText={(searchTerm) => setSearchTerm(searchTerm)} />
    </Header>
  )

  const renderItem = (info) => <ConversationSummary key={`conversation-${info.index}`} conversation={info.item} />

  return (
    <View>
      <Wrapper backgroundColour={backgroundColor}>
        <List
          renderItem={renderItem}
          data={conversations}
          ListHeaderComponent={renderHeader}
          backgroundColour={backgroundColor}
        />
      </Wrapper>
    </View>
  )
}

Expected behavior
The keyboard shouldn't disappear and the input should remain focused
Link to runnable example or repository (highly encouraged)
https://snack.expo.io/0dhL6ZXE!
UI Kitten and Eva version

Package
Version

@eva-design/eva
2.0.0

@ui-kitten/components
^5.0.0

Environment information

  System:
    OS: macOS 10.15.4
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
  Binaries:
    Node: 12.4.0 - /usr/local/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
  SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
  IDEs:
    Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild
  npmPackages:
    react: ~16.9.0 => 16.9.0
    react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4

@andyhmltn it becomes blurred because of incorrect usage of ListHeaderComponent property. Whenever you do a search, the List also becomes updated, calling state changes in Input.
You may solve this case by avoiding rendering Input with that property, e.g:
<Input />
<List />

Brilliant, that works and makes sense. Thanks for the fast reply @artyorsh

FYI, the reason I did this was this example in the demo app:
https://github.com/akveo/kittenTricks/blob/master/src/layouts/messaging/conversation-list/index.tsx
I guess this works in the demo app, because there's no state changing. But when adding state, the way it's laid out there doesn't work


FIX: notebooks

There is still one issue in the PyDDA Notebook (but at the very end).
Another issue is with data retrieval for baltrad2wradlib notebook. In the hub this works on the second run.
Going to merge this. To get everyone a fresh and almost fixed repo.


Week 2: Integration of Slurm Cluster Monitoring with Grafana

Topic: Ensure that Slurm is correctly set up
Tasks:
- Slurm, Node Exporter, Prometheus and Grafana is installed, configured and working correctly.
It is important that they work independently first before attempting to integrate them

Hey team @smasuku @Rosemary2301 @LesegoSenamela @Karabo-Lekolwane
Just checking in as we approach the end of week 2. Hope everything is going well.
Good Luck!

Hi Team,
If you are done with these tasks, let us know so that this issue can be closed.


Web receiver QA

Documenting QA bugs/fixes on current version of web receiver experience. May need to break out into individual issues.
Overall

[ ] Clean links without extensions

Okta

[x] On login I get Cannot GET /signin/data-index.html
[ ] Add logo-only navbar

Error pages

[ ] 404 page: not wired up (ex: /foobar = blank page with text Cannot GET /foobar)
[ ] 404 page: add navigation partial
[ ] Unsupported browser page: does someone have access to an old version of Windows to test this?

Index
Signed out

[x] Sign in button doesn't appear in top right of navigation
[ ] Should "Daily Data" be visible when not logged in?
[ ] Should we bump up the presence of the "contact us" CTA?

Signed in

[ ] Need to dynamically check your logged in status (You lose your username and logout link when viewing )

Navigation

[ ] Improve placement of navigation links, currently they're sort of right-ish of center-ish
[ ] Mobile: menu icon not present

Footer

[ ] Make footer sticky
[ ] Add some top margin/padding so it doesn't collide with content

Documentation

[ ] Ajust col spacing
[ ] Link up current pdf files
[ ] Need terms and conditions content
[ ] typo "eb" instead of "be" in data retention

Signed in

[ ] You lose your username and logout link when viewing

Download index

[ ] Edit table cols for daily data
[ ] Add link to each show page for daily data
[ ] CSV link goes back to /index
[ ] Edit viz -- add labels, etc

Download show

[ ] Use UWDS breadcrumb
[ ] H_n_ size
[ ] Delivered label color

Closing, checklist items here are duplicated in #744


Move parser and segmenter into webvtt directory

This prevents the parer library from having a naming collision with
other top level parser libraries by moving it into the webvtt directory.

:+1:

:+1:

Merged. Thanks


Provide support for multiple triggers

Provide support for multiple triggers that act as an AND.
Use-Case
Queue processing that persists orders in the database.
As of today, we can autoscale based on message count but if our DB DTU is at 99% capacity we'll only make it worse.
Specification
apiVersion: keda.k8s.io/v1alpha1
kind: ScaledObject
metadata:
  name: {scaled-object-name}
  labels:
    deploymentName: my-queue-worker
spec:
  scaleTargetRef:
    deploymentName: my-queue-worker
  triggers:
  - type: azure-servicebus
    metadata:
      queueName: functions-sbqueue
      queueLength: "5" # Optional. Subscription length target for HPA. Default: 5 messages
  - type: azure-monitor # Requested here: https://github.com/kedacore/keda/issues/155
    metadata:
      resourceUri: <uri>

Kudos to @jornbeyers for idea

Thoughts @jeffhollan?

Interesting. How would this exactly calculate the final replicas count? Sum across all triggers? Or what is the idea on the scaling logic here?

I would say that we just scale out if both criteria has met.
As far as I know we just add one instance every time based on the metric but you're more thinking in terms of the HPA underneath it or?

Yeah, but it is interesting scenario for sure. We should look into this.

Hi, is there any update on where this feature stands?
Our use case is a service that consumes multiple queues

We have a similar use case as we watch multiple Redis lists from same deployment.. it would be nice if I could also specify a single trigger with a regex on the queue name, and get the scaler to watch all matching queues then allow also scale on total sum of elements across all queues.

I think the change is not hard to implement, i have an idea even where to put it, i can probably work on it in the next weeks.

This will be finalized with https://github.com/kedacore/keda/issues/733, right @zroubalik ?

@tomkerkhove yes!

Solved in #733

Just verifying - This is only for ScaledObject I presume?

I think it should work for ScaledJob as well.
@TsuyoshiUshio could you please confirm?

Hi,
Could you please provide an example for multiple triggers for rabbitmq?
I have deleted KEDA 1.5 and deployed KEDA 2.0.0-rc2 in our dev cluster.
If I create following yaml (single trigger), everything works:
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: <deployment-name>
  namespace: default
spec:
  scaleTargetRef:
    name: <deployment-name>
  pollingInterval: 2
  cooldownPeriod: 60
  minReplicaCount: 1
  maxReplicaCount: 100
  triggers:
  - type: rabbitmq
    metadata:
      hostFromEnv: MQ_INFO
      protocol: amqp
      queueLength: '30'
      queueName: <queue name>

If I add triggers it breaks (I need 5 but even 2 breaks it):
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: <deployment-name>
  namespace: default
spec:
  scaleTargetRef:
    name: <deployment-name>
  pollingInterval: 2
  cooldownPeriod: 60
  minReplicaCount: 1
  maxReplicaCount: 100
  triggers:
  - type: rabbitmq
    metadata:
      hostFromEnv: MQ_INFO
      protocol: amqp
      queueLength: '30'
      queueName: <queue # 1>
  - type: rabbitmq
    metadata:
      hostFromEnv: MQ_INFO
      protocol: amqp
      queueLength: '30'
      queueName:  <queue # 2>

Also, in the documentation:
https://keda.sh/docs/2.0/scalers/rabbitmq-queue/
It shows apiVersion: keda.k8s.io/v1alpha1 but I believe its a mistake so I used keda.sh/v1alpha1

@alegmal and what problem are you exactly facing?

Figured it out.
Apparently scaledobjects.keda.k8s.io was not really deleted and it did not let me delete it.
Workaround that worked was:
kubectl patch crd/scaledobjects.keda.k8s.io -p '{"metadata":{"finalizers":[]}}' --type=merge
After running that command it instantly deleted crd/scaledobjects.keda.k8s.io and now everything seems to work!

@alegmal glad to hear that :) Yeah it is important to delete the old CRDs first (https://keda.sh/docs/2.0/migration/#migrating-from-keda-v1-to-v2)


DOC: Better docs for jnp.fmin and jnp.fmax

Part of #21461

@rajasekharporeddy — Since https://github.com/google/jax/pull/23103 was merged, can you rebase onto main?

Thanks! Rebased onto main.


Show tournament standings / results

Update live in a thread? screenshot of the trophies?

If screenshot is a problem, icons can be added like LiseBot 🏆🥈🥉🥇


WYSIWYG not loading content_css from _config.php and not able to have multiple configs

SS 4.0.1
In version 3.6.1 we were able to set different configurations for different WYSIWYG (HTMLText Fields) in the admin, for instance if I had a page on the site with a black background and white text, I would have a specific configuration for that page type content WYSIWYG with an editor.css file different than the default one.
In old projects in 3.6.1 I'd have something like this in my _config.php file:
HtmlEditorConfig::get(‘cms’)->setOption(‘content_css’,  ‘mysite/css/editor.css’);

HtmlEditorConfig::get(‘my_other’)->setOption(‘content_css’,  ‘mysite/css/othereditorstyles.css’);

In SS 4.0.1  I see that, as per documentation, by default silverstripe tries to load any editor.css file that exists in your current theme or you can set up a different one in your yml file like:
---
name: MyCSS
---
SilverStripe\Forms\HTMLEditor\TinyMCEConfig:
  editor_css:
    - 'mysite/css/editor.css'

The yml file doesn't give me the option to have separate css files for different HTML Fields.
There are 2 pages on the current documentation on how to edit the html editor field or WYSIWYG:
https://docs.silverstripe.org/en/4/developer_guides/forms/field_types/htmleditorfield/
https://docs.silverstripe.org/en/4/developer_guides/customising_the_admin_interface/typography/
So I believe that the the class SilverStripe\Forms\HTMLEditor\TinyMCEConfig is the one I should be using, but I expect that something like the following works:
TinyMCEConfig::get('cms')
->addButtonsToLine(1, 'styleselect')
->setOption( 'content_css', 'themes/next/css/customeditor.css');

TinyMCEConfig::get('my_other_config')
->addButtonsToLine(1, 'styleselect')
->setOption('content_css' ,'themes/next/css/my_other_editor.css');

And the do something like:
new HTMLEditorField('OtherContent', 'Other content', $this->OtherContent, 'my_other_config');
in the object as per section "Specify which configuration to use" in the documentation page: https://docs.silverstripe.org/en/4/developer_guides/forms/field_types/htmleditorfield/

I'm investigating this now. :)

Implemented at https://github.com/silverstripe/silverstripe-framework/pull/7910

@tractorcow with the fix implemented do we then use:
HtmlEditorConfig::get('cms') or TinyMCEConfig::get('cms') in the config file?

Both should work fine. :D


Does DSC 5.1 support SQL Server?

After walking through the xDscWebService DSC resource,  the xDscWebService to install pull DSC server on the WMF 5.1 just support ESE  for file DB and OLE for Access DB rather than SQL Server database. For the small scale of application, it is enough on the performance; however, for a large scale of servers(more than >3000 servers), how about performance? Is there any solution to support SQL Server in the DSC 5.1? Thanks in advanced.

This repo is for discussion and development of DSC resources. You can file general DSC requests and questions on UserVoice.
This particular issue has a UserVoice suggestion here: https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/11088516-change-from-edb-file-to-sql-server-database-for-de

Look at powershell.org and youll find discussion about it and how people have solved it with using SQL Server as the backend. That said, its not MS supported yet afaik and to be honest if you have over 3000 you dont place them on the same pullserver, you create a few of them, so each gets less nodes to communicate with. You just have the gather all reports to a central place to ro full blow report, but when you think about it, its exactly what you when you want to gather windows sys event logs to once central place to create reports. I've split mine into Production servers and everything else and appropriate built2 reporting services to separate the chatting between clients and server.

Thanks ArieHein, good suggestion.
@ArieHein  Could you share the url of post that solved it with using SQL server as the backend?

https://powershell.org/forums/topic/dsc-edb-logs/
Follow the replies, especially Zuldans' link

Great!!! We will follow it:)
https://leandrowpblog.wordpress.com/2016/10/26/using-sql-server-db-for-dsc/

We are gonna get native support for SQL Server. Below are snippet from DSC pull service in Windows Server

Starting in release 17090 of Windows Server Insider Preview, SQL Server is a supported option for the Pull Service (Windows Feature DSC-Service).
Note: SQL Server support will not be added to previous versions of WMF 5.1 (or earlier) and will only be available on Windows Server versions greater than or equal to 17090.

@chancein007 did you get your questions answered?

More information here how to set up SQL Server with Pull Server: https://docs.microsoft.com/en-us/powershell/dsc/pullserver
Closing this as resolved.


-Wsign-conversion error when building with Clang 6.0

Please answer these questions before submitting your issue.
Should this be an issue in the gRPC issue tracker? Yes
Create new issues for bugs and feature requests. An issue needs to be actionable. General gRPC discussions and usage questions belong to:

grpc.io mailing list
StackOverflow, with grpc tag

Please don't double post your questions in more locations; we are monitoring both channels, and the time spent de-duplicating questions is better spent answering more user questions.
What version of gRPC and what language are you using? language is C, version is 1.3
What operating system (Linux, Windows, …) and version? ChromeOS (a version of Linux)
What runtime / compiler are you using (e.g. python version or version of gcc)
Clang 6.0
What did you do?
If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.
x86_64-pc-linux-gnu-clang -pthread  -Ithird_party/googletest/googletest/include  -g -Wall -Wextra -Werror -Wno-long-long -Wno-unused-parameter -DOSATOMIC_USE_INLINED=1 -O2 -fPIC -I. -Iinclude -I/var/tmp/portage/dev-libs/grpc-1.3.0-r1/work/grpc-1.3.0/gens -DNDEBUG -DINSTALL_PREFIX="/usr"     -DTSI_OPENSSL_ALPN_SUPPORT=0 -O2 -pipe -std=c99 -Wsign-conversion -Wconversion -Wshadow -Wextra-semi   -MMD -MF /var/tmp/portage/dev-libs/grpc-1.3.0-r1/work/grpc-1.3.0/objs/opt/src/core/lib/channel/channel_args.dep -c -o /var/tmp/portage/dev-libs/grpc-1.3.0-r1/work/grpc-1.3.0/objs/opt/src/core/lib/channel/channel_args.o src/core/lib/channel/channel_args.c
What did you expect to see?
The file compiled.
What did you see instead?
src/core/lib/channel/channel_args.c:228:23: error: implicit conversion changes signedness:
'grpc_compression_algorithm' to 'int' [-Werror,-Wsign-conversion]
tmp.value.integer = algorithm;
~ ^~~~~~~~~
1 error generated.
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment?

What was your command line for compiling?

x86_64-pc-linux-gnu-clang -pthread
-Ithird_party/googletest/googletest/include  -g -Wall -Wextra -Werror
-Wno-long-long -Wno-unused-parameter -DOSATOMIC_USE_INLINED=1 -O2 -fPIC -I.
-Iinclude -I/var/tmp/portage/dev-libs/grpc-1.3.0-r2/work/grpc-1.3.0/gens
-DNDEBUG -DINSTALL_PREFIX="/usr"     -DTSI_OPENSSL_ALPN_SUPPORT=0 -O2
-pipe -std=c99 -Wsign-conversion -Wconversion -Wshadow -Wextra-semi   -MMD
-MF
/var/tmp/portage/dev-libs/grpc-1.3.0-r2/work/grpc-1.3.0/objs/opt/src/core/lib/channel/channel_args.dep
-c -o
/var/tmp/portage/dev-libs/grpc-1.3.0-r2/work/grpc-1.3.0/objs/opt/src/core/lib/channel/channel_args.o
src/core/lib/channel/channel_args.c
Applying -v & -save-temps to get the .i file & command line;
"/usr/bin/clang-6.0" -cc1 -triple x86_64-pc-linux-gnu -emit-llvm-bc
-emit-llvm-uselists -disable-free -main-file-name channel_args.c
-mrelocation-model pic -pic-level 2 -mthread-model posix -fmath-errno
-masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array
-target-cpu x86-64 -dwarf-column-info -debug-info-kind=limited
-dwarf-version=4 -debugger-tuning=gdb -momit-leaf-frame-pointer -v
-coverage-notes-file
/var/tmp/portage/dev-libs/grpc-1.3.0-r2/work/grpc-1.3.0/objs/opt/src/core/lib/channel/channel_args.gcno
-resource-dir /usr/lib64/clang/6.0.0 -O2 -Wno-tautological-constant-compare
-Wno-unused-local-typedefs -Wno-tautological-unsigned-enum-zero-compare
-Wno-unknown-warning-option -Wno-deprecated-declarations -Wall -Wextra
-Werror -Wno-long-long -Wno-unused-parameter -Wsign-conversion -Wconversion
-Wshadow -Wextra-semi -std=c99 -fdebug-compilation-dir
/var/tmp/portage/dev-libs/grpc-1.3.0-r2/work/grpc-1.3.0 -ferror-limit 19
-fmessage-length 82 -pthread -fobjc-runtime=gcc -fdiagnostics-show-option
-fcolor-diagnostics -vectorize-loops -vectorize-slp -disable-llvm-passes -o
channel_args.bc -x cpp-output channel_args.i -dwarf-debug-flags
"/usr/bin/clang-6.0 -Qunused-arguments -grecord-gcc-switches
-Wno-tautological-constant-compare -Wno-unused-local-typedefs
-Wno-tautological-unsigned-enum-zero-compare -Wno-unknown-warning-option
-Wno-deprecated-declarations -pthread -I
third_party/googletest/googletest/include -g -Wall -Wextra -Werror
-Wno-long-long -Wno-unused-parameter -D OSATOMIC_USE_INLINED=1 -O2 -fPIC -I
. -I include -I
/var/tmp/portage/dev-libs/grpc-1.3.0-r2/work/grpc-1.3.0/gens -D NDEBUG -D
INSTALL_PREFIX="/usr" -D TSI_OPENSSL_ALPN_SUPPORT=0 -O2 -pipe -std=c99
-Wsign-conversion -Wconversion -Wshadow -Wextra-semi -MMD -MF
/var/tmp/portage/dev-libs/grpc-1.3.0-r2/work/grpc-1.3.0/objs/opt/src/core/lib/channel/channel_args.dep
-c -o
/var/tmp/portage/dev-libs/grpc-1.3.0-r2/work/grpc-1.3.0/objs/opt/src/core/lib/channel/channel_args.o
src/core/lib/channel/channel_args.c -v -save-temps=cwd"
I'll attach the .i file to this email.  Also, fyi, the version of clang we
are using;
$ /usr/bin/clang-6.0 --version
Chromium OS 6.0_pre316199_p20171105-r1 clang version 6.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/clang.git
4d085086c74a8fbce197f61548f488a63f300933)
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm.git
66af8bde13a515b8d0fa76201f0d5b428187fd13) (based on LLVM 6.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
It's based on r317203.
-- Caroline
<EMAIL_ADDRESS>On Mon, Dec 11, 2017 at 11:37 AM, Noah Eisen<EMAIL_ADDRESS>wrote:

What was your command line for compiling?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/issues/13597#issuecomment-350833623, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFTbSk6gGl9wMt70F4pnx8KiwKDLxLPDks5s_YR-gaJpZM4Qy63H
.

channel_args.i.txt
Previous attempt to attach channel_args.i failed.  Renamed it to 'channel_args.i.txt' and attached it here.

Added a cast to fix in #13714

For what reason are you using v1.3? Can you try HEAD? We have a policy against backporting fixes to such old versions (I just learned this).
Please re open if this occurs against a more current version


Chore/prune depreciate request code

https://www.pivotaltracker.com/story/show/150680543
Includes removing unused code, cleanup of depreciated states,  renaming misleading files, ensuring everything works as it did previously.
The other thing we did here @serenamarie125 was restore the requests list in the order details screen (was pulled because it was also being used for requests explorer https://github.com/ManageIQ/manageiq-ui-service/pull/709 ).  Find attached below a ss with the list restored, please note, nothing has changed from the original design, just restored what was accidentally pulled.

working on coverage

@chriskacerguis coveralls is 😀

No UX changes, just code removal.

@serenamarie125 if we need to change, just let us know...but, as @AllenBW said this was something that was previous there (which I thought was approved...could be wrong); that through a bug disappeared.


[Feature]: adeptus mechanicus mode

Describe the solution
For ironic immersion. Find audio, quotables, dialogue lines, music
Related issues
No response
Example usage
No response
Alternative solutions
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Also add visual theme (just quake bar/page/browser?


Add stemflow

Insert URLs to the project here: https://github.com/chenyangkang/stemflow

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All new projects listed will be posted on our Mastodon channel.

@chenyangkang

Awesome! Thank you for maintaining this collection!


Not working with telescope 0.1.2

But worked with 0.1.1

Thanks @d-chirkov! I've not been using neovim for past few months at work but will try to have a look at what the cause might be in the next week or two. Also happy to accept PRs if you happen to know the cause already!


KServe VLLM cpu image

/kind feature
Describe the solution you'd like
Currently, the image: kserve/vllmserver:latest only supports GPU workloads. I'd like an image that supports running VLLM via KServe using CPU.
Anything else you would like to add:
The VLLM dockerfile for CPU is here: https://github.com/vllm-project/vllm/blob/main/Dockerfile.cpu

Coincidentally, I am having the same problem.  Is anybody currently working on this?
Some immediate avenues to explore:

Bake CPU support into the docker image and pass an arg at runtime specify. Of course, at this point, we don't need CUDA so we are taking on a lot of bloat there. This may require require huggingface server be capable of processing the arg, too.
We could do something similar to torchserve and default to a -cpu image if no GPU is provided.

@johnugeorge Are you guys planning to work on this?

@johnugeorge Are you guys planning to work on this?

Yes @yuzisun, we have started on this task. Will have the PR open shortly

/assign

@yuzisun @gavrissh @johnugeorge
awesome. excitedly awaiting the PR.
can you point to where in the code the kserve images are built/published?

awesome. excitedly awaiting the PR.

@gavrissh I am also waiting for the PR. I feel it's really difficult to write the mock tests for vLLM

/assign

can you point to where in the code the kserve images are built/published?

@jyono The Fix PR changes would show the workflow for the above query #4049

@gavrissh huge! thanks :)


commands: Fix server panic regression

And now with a proper server test.
Fixes #9518
Fixes #9530
Fixes #9539

I have admittingly only tested one of the cases above (which is now also added as an integration test), but I assume the cause is the same.

I have admittingly only tested one of the cases above

I just build hugo v0.93.0-DEV with the change you comitted and tested it for the issue addressed with #9539. For me, the error persist. Can you please doublecheck? Thanks.

Can you please double check? Thanks.

Just did, and I don't see how you could get the stack trace your reported after my patch, which must suggest that you 1. Either did not build this version or 2. Got a different error.

@deining deining
If you continue to experience problems, please continue our forum discussion. Thanks.


Add python version check and if python is even present on PATH.

Note for maintainers: The version detection looks weird because findstr is weird. https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/findstr