Activate POE after pressing omni key to make it more "safe"?

hey,
just downloaded Lailloken-UI. looks very impressive, thanks for sharing!
one thing i noticed right away: if i press the omni-key, while the menu is open, most key presses do not get registered by POE (flasks, movementskill, guardskill etc.),
would it be possible to activate the POE window after bringing up the omni-key menu, just to make this thing more safe? lets say i press the omni key on an item in my inventory, only to notice that i am standing in some random degen ground effect. pressing my life flask wont register. i first have to click in the POE screen to use any keybinds.
thanks!

It closes as soon as the PoE-client is activated, so one can close it by clicking somewhere else, without having to click an option or press ESC (just like the context-menu in Windows). If I take that out and activate the client after opening context-menu, the user will be forced to click an option or press ESC.
Which feature are you trying to access in the middle of a map? Just curious because I've kinda lost track what's in there, but I don't think there's anything that would be accessed mid-map. Maybe I'm missing something here.

yea, i guess the chances for this to RIP a char are astronomically low.


Babel Error: @babel/plugin-proposal-private-property-in-object  explicit dependency

Hitting a newly introduced error message in babel version 7.22.5 causes the following error:
--- PLACEHOLDER PACKAGE ---
This @babel/plugin-proposal-private-property-in-object version is not meant to
be imported. Something is importing
@babel/plugi-proposal-private-property-in-object without declaring it in its
dependencies (or devDependencies) in the package.json file.
Add "@babel/plugin-proposal-private-property-in-object" to your devDependencies
to work around this error. This will make this message go away.

Since packemon uses @babel/plugin-proposal-private-property-in-object for babel config, it needs to explicitly declare it as a dependency.
https://github.com/milesj/packemon/blob/76085236fb1b246ae8a0c1e468737910cee6976d/packages/packemon/src/babel/config.ts#L140
Related:
https://github.com/babel/babel-plugin-proposal-private-property-in-object
https://github.com/babel/babel/pull/15687
https://github.com/babel/babel/issues/15694

@j3tan This is a weird one. I'm not importing @babel/plugin-proposal-private-property-in-object anywhere.
But I am importing @babel/plugin-transform-private-property-in-object which is different (note transform vs proposal). Maybe node modules in a weird state? Does deduping fix it?
I'll dig a bit deeper anyways.

I can't seem to reproduce this. Is it just being logged to the console during a build?

@milesj My bad, this may be due to using an older version of packemon . I had not realized you moved away from the proposal package 2 weeks ago and we definitely haven't bumped since before that.
I'll verify and close if that is the case

Some repos are still using<EMAIL_ADDRESS>so we're using yarn resolutions to bypass the warning for now.

Yea this was fixed in 3.1.1. I'll leave this open for now in case there's more issues around it.

how to solve this error im a beginner id dont know much technical terms, can anyone tell me how to solve in simple words??!!


Authentication support for remote charts repositories

This pull request adds support for sending credentials (username and password) to remote charts repositories. This will allow vendors of charts repositories to restrict access to privileged users only.
This new functionality is optional of course.
Please let us know what you think.
We'd be happy to add more commits as needed.
Thank you in advance.

My CLA appears as unsigned, probably because I signed with a different email address<EMAIL_ADDRESS>than my github user's email (eyalb@jfrog.com).
Since I'm unable to sign the CLA again, I sent an email to the CNCF helpdesk, asking for help.

Your local git config is set to an incorrect email address when they're being signed.
commit 3e84ba1940b0e42e988433a8b2836e2a077c9019 (HEAD, eyalbe4/master)
Author: eyalbe4 <00Rotshild00>
Date:   Mon Nov 27 22:49:06 2017 +0200

    Ran 'go fmt' and 'make docs'.

You can change that with git config --global user.email<EMAIL_ADDRESS>and fix them up using git remote add upstream https://github.com/kubernetes/helm && git fetch upstream master && git rebase -i upstream/master.

Thanks you for your help @bacongobbler!
All looks okay now.

@bacongobbler,
We've been using the authentication mechanism in this PR for a few weeks already and it works great for us.
Any chance this can be merged? Please let us know if you'd like us to add or change anything.
Thanks

Who is approver for this?  @michelleN ?  @erictune ?

Anyone from helm's OWNERS file can review/approve. I can take a look.

Thanks for reviewing the code @bacongobbler.
I implemented both comments.
Please let me know if additional changes are needed.

Not sure it helps the cause, but I also successfully pushed and pulled from Artifactory helm repository using the forked version maintained by JFrog.

@bacongobbler  - Anything in particular blocking this?  It's been on my dashboard for quite a while...

Sorry, been blocked by higher priority work (helm 2.8.1, helm dev summit, etc). I’ll take a look at this tomorrow.

Hi @michelleN,
Thank you for the feedback and code review!
I pushed a commit fixing the issues you mentioned.
As for the questions you asked about the * findChartURL* function, please see my replies, and let me know if you'd like me to make the changes you proposed.
If you'd like to leverage the username and password in a future pull request, please let me know when the time comes and I'll gladly contribute the code.
Thanks again for spending the time and helping push this important functionality further. I really appreciate it.
Please let me know if there are other changes you'd like to see, and I'll add them.

@michelleN,
Thanks for reviewing the code again. I changed the code according to your suggestions:
I regenerated the docs and committed the updated helm-fetch.md.
I also add a new method signature, so that the old method signature remains as it was.
As for the usage of the username and password by the various commands, I think that the behaviour you experienced is expected. Here's why:
All commands take the username and password flags values (if sent) or the configured username and password (if configured) and send them to the remote chart repository, by adding them as a basic auth header. If the chart repository however is not configured to validate the credentials, it will just ignore the header and the request should not fail. Please let me know if you have more questions about this, and I'd be happy to elaborate.
I can see that there are a few conflicting files. Since all of them are under helm/docs, they can be easily resolved once this branch is synched with the latest code. I thought is might be easier to do this once, when the code in this PR is approved. If you however prefer I do the sync now, please let me know.
Thanks again @michelleN and @bacongobbler for the review and please let me know if there's anything else you'd like to see.

Thanks @eyalbe4 I did another round of manual tests and read through the code and it all looks great to me. Please resolve the merge conflicts so we can merge after @bacongobbler has had a chance to review!

@bacongobbler,
I rebased the commits and resolved the conflicts.
As for your comments, see my inline questions and let me know what you think.
Thanks

@bacongobbler,
Can you please take a look at my question following your requested change and let me know how you'd like me to proceed?

This PR is only interesting to me in that I am trying to figure out how to NOT let PRs languish for months on end.  @bacongobbler do you actually have time for it?

We were just at Helm summit last week; I will take a look again tomorrow.

This PR is only interesting to me in that I am trying to figure out how to NOT let PRs languish for months on end.

OK, I feel like I need to explain why this PR has been sitting in the queue for a long period of time. The short form is that both parties here (being myself and @eyalbe4) are equally to blame.
Let's start with my end first.
When first triaging this issue, this PR did not have any discussion in the dev calls, there were no bugs referenced, and no documentation. That made it incredibly difficult to triage, test and/or assess the impact this feature had on the project. What I should have done is immediately ask for clarification on the PR, which I didn't do until several months later. I'll take the blame on that front and learn from this for future discussions.
Now, on @eyalbe4's end...
When this PR was originally posted, there was no discussion, referenced bugs in the OP or documentation in any shape or form. That made this PR nearly impossible to test because there were no existing chart repositories to test against asides JFrog's artifactory. I'll note that Artifactory was referenced in a follow-up commit, but it was unclear how someone could utilize this new feature against Artifactory, as well as why it was better than the previous form (again, we didn't ask for clarification until several months later).
From @eyalbe4's end, it would have been much more useful if there was a documented list of issues this PR solved, a set of steps to test this PR with Artifactory or a reference architecture we could test with. Through our own frustration, we gave up testing with Artifactory and @michelleN made her own mock chart repository to test this PR against which worked for demonstration and testing purposes.
Hopefully that clarifies the situation a bit. Now, let's get back to actually moving this PR forward.

To be clear: no blame.  Just want to try to make it better for people.
Would be good to augment some of the contributor docs to explain the
best-practices for streamlining a PR.
On Tue, Feb 27, 2018 at 8:36 AM, Matthew Fisher<EMAIL_ADDRESS>wrote:

This PR is only interesting to me in that I am trying to figure out how to
NOT let PRs languish for months on end.
OK, I feel like I need to explain why this PR has been sitting in the
queue for a long period of time. The short form is that both parties here
(being myself and @eyalbe4 https://github.com/eyalbe4) are equally to
blame.
Let's start with my end first.
When first triaging this issue, this PR did not have any discussion in the
dev calls, there were no bugs referenced, and no documentation. That made
it incredibly difficult to triage, test and/or assess the impact this
feature had on the project. What I should have done is immediately ask for
clarification on the PR, which I didn't do until several months later
https://github.com/kubernetes/helm/pull/3206#issuecomment-358885158.
I'll take the blame on that front and learn from this for future
discussions.
Now, on @eyalbe4 https://github.com/eyalbe4's end...
When this PR was originally posted, there was no discussion, referenced
bugs in the OP or documentation in any shape or form. That made this PR
nearly impossible to test because there were no existing chart repositories
to test against asides JFrog's artifactory. I'll note that Artifactory was
referenced in a follow-up commit, but it was unclear how someone could
utilize this new feature against Artifactory, as well as why it was better
than the previous form (again, we didn't ask for clarification until
several months later
https://github.com/kubernetes/helm/pull/3206#issuecomment-359267577).
From @eyalbe4 https://github.com/eyalbe4's end, it would have been
much more useful if there was a documented list of issues this PR
solved, a set of steps to test this PR with Artifactory or a reference
architecture we could test with. Through our own frustration, we gave up
testing with Artifactory and @michelleN https://github.com/michellen
made her own mock chart repository
https://github.com/michelleN/secure-chart-repo to test this PR against
which worked for demonstration and testing purposes.
Hopefully that clarifies the situation a bit. Now, let's get back to
actually moving this PR forward.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/helm/pull/3206#issuecomment-368940767, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFVgVP9GiI2Ja3JcO6NuhbnPBfPJ3avVks5tZC8dgaJpZM4QsJ2n
.

@bacongobbler,
Thank you for sharing these guidelines for requesting new functionalities and submitting pull requests. I wasn't aware that testing this can be challenging. Since servers which allow anonymous access are not affected by this, all we needed to test, was that the basic auth header is passed for every command (in addition for the commands functionality of course).
Since this functionality can be used by any future charts repo vendor (we tested it with Artifactory before every commit of course), I didn't think that you'd be interested in testing it specifically with Artifactory.
I will make sure to follow all of these guidelines for future requests and contributions.
I implemented the changes you requested and removed the GetWithCredentials API. This change required the following changes which I also implemented:

getter.httpGetter was renamed to getter.HttpGetter, because it now needs to be available also outside of the getter package.
The ResolveChartVersionAndGetRepo method now also returns a getter.HttpGetter argument.
A new getter.NewHTTPGetter function has been added (in addition to the existing getter.newHTTPGetter function), to allow the ResolveChartVersionAndGetRepo to obtain and return a getter.HttpGetter argument.

Looking forward to your review and feedback. Thanks.

@bacongobbler,
If we manage to reduce our response time while working on this, we should be able to finish the work quickly.
Please LMK what you think.

@bacongobbler any update on this one ? Thanks for your help

@eyalbe4 ok for you to rebase ?
Sorry guys but I really need this feature :-)

Absolutely @mfilotto.
I'll rebase this today.

@bacongobbler,
The code has been rebased, but the tests are failing, probably as a result of a different commit added to the master:
# k8s.io/helm/cmd/helm
./history_test.go:61:8: unknown field 'cmds' in struct literal of type releaseCase
./history_test.go:62:8: unknown field 'desc' in struct literal of type releaseCase
./history_test.go:64:8: cannot use []*release.Release literal (type []*release.Release) as type *release.Release in field value
./history_test.go:68:8: unknown field 'xout' in struct literal of type releaseCase
./history_test.go:71:8: unknown field 'cmds' in struct literal of type releaseCase
./history_test.go:72:8: unknown field 'desc' in struct literal of type releaseCase
./history_test.go:74:8: cannot use []*release.Release literal (type []*release.Release) as type *release.Release in field value
./history_test.go:78:8: unknown field 'xout' in struct literal of type releaseCase
FAIL	k8s.io/helm/cmd/helm [build failed]

@eyalbe4 Are you sure all the commits should show up in this branch, this seems unusual? I would normally do a git fetch first, update my local master branch, change to the local feature branch and do:
git rebase master
git push -f origin foo:foo

This should lead to a branch/PR to only contain the actual changes, exactly as the branch would be created based on recent master.

See https://github.com/kubernetes/helm/pull/3717

@cmeury,
You're probably right and I could have been smarter about how I did the rebase...
I think we're good though. All of this PR's commits are now at the top. Fixed inspect.go following rebase. is the only new commit I had to add following the rebase.
I hope that after https://github.com/kubernetes/helm/pull/3717 is committed, we'll be good to go.

Tests look good now.

Congrats! Very glad to see this merged. Thanks to all involved.
I held off with commenting as I didn't want to derail your discussions.
The Artifactory set-up I'm using also requires a client-side SSL cert. When I noticed that this PR just adds support for Basic Auth, I had a look at the diff to see how much work it'd be to add support for client-side ssl certs. By the looks of things, there's no centralised "HTTP client configuration" or similar - instead the username/password are passed around throughout the code.
So, I'm wondering - if I were to add client-side SSL cert support, would it be OK to do it in the way that was done in this PR, or would the maintainers (ping @bacongobbler @michelleN) feel that this is the time to do a more involved refactoring and store this HTTP client configuration somewhere centralised?
The reason I ask is that I have absolutely 0 Go experience, but have been wanting to get into it for some time. I feel this would be a nice starter project, and could easily get it done by emulating the approach in this PR. If a big refactoring was to be done, however, I'd perhaps need someone to dictate the design a little.

@kopf I think that client-side TLS certs are already supported in the Helm client?
https://github.com/kubernetes/helm/issues/1038#issuecomment-297043419
(As an aside, since I'm also about to set up Artifactory - is Artifactory itself doing the client-cert checking, or is it just behind some proxy that does the check? If Artifactory itself, how did you set that up?)

@jgiles - ah, super - thanks for the heads-up!
I didn't set it up personally, but if I were going to do it, I'd personally use an nginx ssl-offloader.

I didn't set up Artifactory either when testing. I'd ask JFrog directly :)

Did someone try to download dependencies from  an authenticated repository ?
I did a helm dependency update with no luck
I get an error  401 Unauthorized
@eyalbe4 an idea ?
[root@dbk-miniont-01v nginx-ingress-sln]$ cat requirements.yaml
# requirements.yaml
dependencies:
 - name: consul
   version: "1.3.5"
   repository: "@stable"

[root@dbk-miniont-01v nginx-ingress-sln]$ helm repo list
NAME    URL
stable  https://artifactory.sln.nc/artifactory/helm

[root@dbk-miniont-01v nginx-ingress-sln]$ helm dependency update
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "stable" chart repository (https://artifactory.sln.nc/artifactory/helm):
        Failed to fetch https://artifactory.sln.nc/artifactory/helm/index.yaml : 401 Unauthorized
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading consul from repo https://artifactory.sln.nc/artifactory/helm
Save error occurred:  could not download https://artifactory.sln.nc:443/artifactory/helm/consul-1.3.5.tgz: Failed to fetch https://artifactory.sln.nc:443/artifactory/helm/consul-1.3.5.tgz : 401 Unauthorized
Deleting newly downloaded charts, restoring pre-update state
Error: could not download https://artifactory.sln.nc:443/artifactory/helm/consul-1.3.5.tgz: Failed to fetch https://artifactory.sln.nc:443/artifactory/helm/consul-1.3.5.tgz : 401 Unauthorized

Hey! Which version of helm are you running? This is only available in the canaries and 2.9.0-rc4 at this point.

I use v2.9.0-rc4 with a repo added with username/password

I'm looking into this @mfilotto.
In the meantime, can you look in Artifactory's request log (available through the UI) and let me know if the request sent by helm includes the user configured in helm?
Just in case we'll need to debug this on your end, which operating system are you running helm on?

@mfilotto,
Artifactory currently supports updates from virtual repositories only.
Could it be that you're getting the 401 Unauthorised because your repositories.yaml is not referencing a virtual repository? I've just tested this with a virtual repository and it seems to be working as expected (401 if my credentials are incorrect and a successful update if they are correct.
I did manage to get a 401 when I replaced it with a remote repository.

@eyalbe4 Here is my config

Artifactory : 5.10.1
Helm : helm-v2.9.0-rc4-linux-amd64
Helm OS: CentOS 7.1.1503

I use an helm virtual repository.
The search command list all availables charts : user auhtenticated
The dependencies update return 401: non_authenticated_user
20180426115727|1678|REQUEST|<IP_ADDRESS>|mathieu.filotto|GET|/helm/index.yaml|HTTP/1.0|200|1967664
20180426115729|0|REQUEST|<IP_ADDRESS>|non_authenticated_user|GET|/helm/consul-1.3.5.tgz|HTTP/1.0|401|0

Helm version v2.9.0-rc5 solved my issue :smiley:
:+1:


mod does not work and gives exit error 1 error

When I install the mod, when I press the start game button, the game loading screen comes up and closes. After it closes, it gives Minecraft launcher exit error 1 error. There is no file in the crash-reports folder. Only the latest.log file gets this text:
[27Dec2023 16:56:32.344] [main/FATAL] [mixin/]: Mixin apply failed createdieselgenerators.mixins.json:EntityMixin -> net.minecraft.world.entity.Entity: org.spongepowered.asm.mixin.injection.throwables.InvalidInjectionException Critical injection failure: @Inject annotation on tick could not find any targets matching 'tick()V' in net.minecraft.world.entity.Entity. Using refmap mixin.refmap.json [PREINJECT Applicator Phase -> createdieselgenerators.mixins.json:EntityMixin -> Prepare Injections ->  -> handler$bcd001$tick(Lorg/spongepowered/asm/mixin/injection/callback/CallbackInfo;)V -> Parse]
org.spongepowered.asm.mixin.injection.throwables.InvalidInjectionException: Critical injection failure: @Inject annotation on tick could not find any targets matching 'tick()V' in net.minecraft.world.entity.Entity. Using refmap mixin.refmap.json [PREINJECT Applicator Phase -> createdieselgenerators.mixins.json:EntityMixin -> Prepare Injections ->  -> handler$bcd001$tick(Lorg/spongepowered/asm/mixin/injection/callback/CallbackInfo;)V -> Parse]

mod version: createdieselgenerators-1.20.1-1.2f
create version: create-1.20.1-0.5.1.f
forge version: 1.20.1 - 47.2.18
how can i fix this?

You can unzip the jar, modify createdieselgenerrators.mixin.json, remove "EntityMixin", from the array and it should work.
There is some random issue that randomly 1.20 has a mixin error that happens randomly that is super ridiculous, as it can't find tick() in the Entity class

thank you, it worked


Adding USB support for BBB

Updating the Linux config for the BBB in order to expose USB functionality.
Also adding the lsusb command so that connected devices can be easily seen
Corresponds with issue #201

 USB Support for BBB


The download has finished but it doesn't install

After downloading, It shows me 2 options. Download Again and Install Manually, the Install Manually option doesn't do anything.
In a genymotion emulator with Android 6 It works perfectly but in others devices it behaves different.
It starts to fail after I change the minor 1.0.14 (10014) to 1.1.0 (10100).
Any idea?

linked to #107

I am facing this issue several times on Android 6.0.
I think that, in my case, there is an issue between this plugin and the cordova-plugin-kiosk, which inhibit the autorestart (and update) of the app.
I still haven't solve this issue.


Add some emojis

Modified article list & reply list flex box to match #140 and #141 's mockup. Follows @PenguinRun 's contribution in #150 and #151.
Article list

Add different emoji for different similarity
Adjust margin between header and body
Tweak wording

Reply list

Add emoji
Adjust margin between header and body
Tweak wording

Pull Request Test Coverage Report for Build 601

6 of 6 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 96.25%

Totals

Change from base Build 598:
0.04%

Covered Lines:
219

Relevant Lines:
225

💛  - Coveralls


Add code of conduct to contributing guidelines

We are intending to adopt the soon-to-be-announced Open Code of Conduct for all @github projects. This adds it to the contributing guidelines. Let me know if you have any questions or concerns.

Looks like they miss some url parsing on their side. Should we file an issue? Using a space in the URL also fixes it.

Since this links to text on a third party site rather than incorporates the text into the repo I'm wondering if there's any mechanism in place to notify maintainers of any changes to the CoC text?

I opened https://github.com/todogroup/opencodeofconduct/issues/15 to report the issue.

The Code of Conduct looks good to me. However, like @rubyist, I am a bit concerned about the technical implementation of this. The todo group site is also just http, leaving a tiny chance that man in the middle attack could drastically change the contents without our knowledge.
I'd like a model where I could register to have a bot send pull requests for a ./CODE-OF-CONDUCT.md file or something. Then the content is hosted inside the repository, and changes are clearly visible to contributors.
I'm :+1: to merge this right now though and get the ball rolling.

Agree with all of that :+1: on a merge

That's all really great feedback.

The todo group site is also just http, leaving a tiny chance that man in the middle attack could drastically change the contents without our knowledge.

It is currently a Pages site, so it would need to be moved somewhere else since pages doesn't support https.

I'd like a model where I could register to have a bot send pull requests for a ./CODE-OF-CONDUCT.md file or something. Then the content is hosted inside the repository, and changes are clearly visible to contributors.

That came up as an option at some point. I'm not opposed.
The thinking for the current approach is that, unlike a license, which applies to the code no matter where it exists, the code of conduct applies to online interactions.
Most other people that are adopting the code of conduct do it by posting the text on their own website. We could certainly do that as well.

Ah, Pages. I hope we can support SSL there one day :)

The thinking for the current approach is that, unlike a license, which applies to the code no matter where it exists, the code of conduct applies to online interactions.

That's legit. Until people start being jerks in commit messages :trollface: Anyways, I'm happy with this PR for now.


ipset: Set cannot be destroyed when running alongside keepalived-vip on the same host

When keepalived-vip and Weave run on the same host, the weave-npc container constantly crashes:
# docker logs -f a95eb6b0429ea321c5494f8321413b082c5f3593dbbcea4b1dda1e5a7f140c0b
time="2017-01-25T10:17:01Z" level=info msg="Starting Weaveworks NPC 1.8.2"
time="2017-01-25T10:17:01Z" level=info msg="Serving /metrics on :6781"
Wed Jan 25 10:17:01 2017 <5> ulogd.c:843 building new pluginstance stack: 'log1:NFLOG,base1:BASE,pcap1:PCAP'
time="2017-01-25T10:17:02Z" level=fatal msg="ipset [destroy] failed: ipset v6.29: Set cannot be destroyed: it is in use by a kernel component\n: exit status 1"

Apparently Weave does not expect ipsets created by others. Only solution to bring Weave back working at the moment is to remove keepalived-vip and reboot the host.
Any ideas on how to make Weave co-exist with keepalived-vip on the same host?
Environment: Kubernetes 1.5, CentOS 7.3

Any ideas on how to make Weave co-exist with keepalived-vip on the same host?

Yes, fix this: https://github.com/weaveworks/weave/blob/master/prog/weave-npc/main.go#L75

Closed by #2846 (for some reason it didn't get automatically closed by the PR).


[C++] Fix thread safety issue for multi topic consumer

Motivation
In C++ client, if a consumer subscribes multiple topics, a
MultiTopicsConsumerImpl object, which manages a vector of
ConsumerImpls (consumers_ field), will be created. However,
consumers_ could be accessed by multiple threads, while no
mutex is locked to protect the access to make it thread safe.
Modifications

Add a SynchronizedHashMap class, which implements some thread safe
methods of traverse, remove, find, clear operations. Since the
forEach methods could call other methods, use the recursive mutex
instead of the default mutex.
Add a related test SynchronizedHashMapTest to test the methods and
the thread safety of SynchronizedHashMap.
Use SynchronizedHashMap as the type of
MultiTopicsConsumerImpl::consumers_.

Hi @merlimat could you take a look at this PR?


Mysql Connector Not Handling Table Names with Upper Case

Problem Description: Table names which are created in Upper case in MYSQL is not searchable. Problem Cause: Under QualifiedName we are standardizing to lowercase for all database and table names. Its better to leave them as is as relational databases might be case sensitive. Problem Solution: Not standardizing the database, table and view Names

Early on, we made a decision to lower case names in Metacat. QualifiedName represents the identifier for an object in a catalog, where we standardize the names to be lower-cased.

mysql is case sensitive. It wont accept search with lowercase for table names with upper case.

if this is not the right approach then atleast we have to check for harvester is mysql and in that case we shouldn't standardize. Please provide your thoughts on the same.


How to configure Language.

The default language is Language.Java
How to set Language to Language.XLANG
I didn't find any configuration in FuryBuildTimeConfig either!

No, there is no such configuration currently. Just curious, what are your requirement to use XLANG?

Fury designed and implemented multiple binary protocols for different scenarios:

xlang serialization format:

Cross-language serialize any object automatically, no need for IDL definition, schema compilation and object to/from
protocol conversion.
Support optional shared reference and circular reference, no duplicate data or recursion error.
Support object polymorphism.

Java serialization format: Highly-optimized and drop-in replacement > for Java serialization.
Row format format: A cache-friendly binary random access format, > supports skipping serialization and
partial serialization, and can convert to column-format automatically.

I'm going to use fury to replace json in our web project.
This will require support for serialization in at least two languages, java and javascript.
Also go, python is becoming more and more popular in the backend and it's becoming more and more common to have a mixed language stack in microservices.
If I understand correctly, according to the documentation, the cross-language should use the xlang serialization format

@chaokunyang can you check it? I think we can add such Language Configuration but you maybe know more details.

The xlang serialization in Fury Java doesn't support graalvm yet. Currently only Fury Java serialization protocol support graalvm. We are working on xlang format for graalvm, But it may still needs several weeks

Yeah, We should introduce this configuration option


Kitchen Sink: Build A Virtual Whiteboard

Build a collaborative virtual whiteboard for drawing and brainstorming; you can keep it simple too if you want to that you'll add to the kitchen sink. Feel free to use any existing projects of yours or start one from scratch.
For more information about the Kitchen sink; check out:

https://sink.million.dev/
https://github.com/aidenybai/million/blob/main/packages/kitchen-sink/README.md

N.B: Upon PR review, your usage of Million.js is a plus

I'd like to be assigned this issue. Thx.

Sure thing! Go ahead 😁.

Hey there @one2code, any updates on this at all?

@tobySolutions PR is in. I ended up starting a bit later than expected and encountered more technical challenges than I initially anticipated. Overall, I'm satisfied with the PR and had a lot of fun. Was a great learning experience!

Awesome work @one2code! I love all the work and the whole building in public is just amazing. I can't wait to go review this PR.

Closed by #742


new RegExp broken with concat unicode string

REPL link
var ws = '\x09\x0A\x0B\x0C\x0D\x20\xA0\u1680\u180E\u2000\u2001\u2002\u2003' +
           '\u2004\u2005\u2006\u2007\u2008\u2009\u200A\u202F\u205F\u3000\u2028' +
           '\u2029\uFEFF';
new RegExp('^[' + ws + '][' + ws + ']*')

Run the output on console, will throw the error:
Uncaught SyntaxError: Invalid regular expression: missing /

I got this problem from https://github.com/jhen0409/react-native-debugger/pull/35, it bundled  ramda/src/trim.js.

Looks like it has been fixed by #304, any news for release?

It's released


feat: style clear button focus state

style SearchInput clear button
style SearchSelectInput clear button
fix (un)controlled state of SearchInput
focus SearchInput after clear

I could be mistaken, but it doesn't seem to be completely well-aligned vertically?


chore: add logging for traces on LLM responses and tool usage

This adds a trace logger to log more granular user and assistant messages and tool usage, primarily for debugging purposes.

maybe in your PR desc when ready add a triple backtick block of some real data (washed of secrets if there are any)


Position of X-UA-Compatible  tag should be mentioned in the "Browser and device support" doc

Recently I had some issues with the IE compatibility mode. The X-UA-Compatible meta tag was present in the head section of my page. Nevertheless, in IE 8 the compatibility mode button was still visible in the browser status bar.
The solution was to include the meta tag as the first entry of the head section.

Well, really the charset meta tag needs to come first if you're using all 3 tags used in our examples.

Maybe we could add a comment to the templates?:
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
    <title>Bootstrap 101 Template</title>

Sounds good. I can test this with a WinXP 32 bit IE8 system.

Hi Chris,
I have tested the IE8 behavior. The compatibility mode pops in when a link tag comes before the X-UA-Compatible tag. So the comment you suggested should be enough.
Thanks

To clarify out and hopefully save some time to other people:

meta charset has to be the very first tag, ever.
meta X-UA-Compatible has to come before link tags, according to above statement by cweinreben. So, 2nd position is a fine place.
meta viewport doesn't seem to cause trouble (refs https://github.com/twbs/bootstrap/pull/15658#issuecomment-72626810). So, 3rd position to keep it close to the others.


Color use in error messages

If I have a type error when defining a record the compiler will give an error message with the most valuable information using color alone.
E.g.
type alias Model =
    { count : Int
    , a: String
    , b: List String
    , c: Float
    }

initialModel : Model
initialModel =
    { count = 0
    , a = 1
    , b = []
    , c = 0
    }

Error:
Something is off with the body of the `initialModel` definition:

18|>    { count = 0
19|>    , a = 1
20|>    , b = []
21|>    , c = 0
22|>    }

The body is a record of type:

    { a : number, b : List String, c : Float, count : Int }

But the type annotation on `initialModel` says it should be:

    Model

In a terminal with colors, number will be highlighted. But apart from that you cannot tell where the error is.
This has some issues:

Relying on color alone is not a great accessibility practice
In several environments the colors are gone. e.g. when showing an error in the Browser dev console or when using something like Docker for development.

It would be great if the error is spelled out in text.

I didn't know this error message had helpful hints on what you did wrong, because I've been seeing it without colors for years! It's a pretty unhelpful error message without them.
This problem is made worse by the choice to not fix https://github.com/elm/compiler/issues/1803, because sometimes you cannot wrap Elm in a PTY.

would love a specific error here.  I too have never noticed the color thing and have had to figure out the problem myself rather than from the error.


Release v0.27.0

:book: CHANGELOG

[ ] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Added entry in .changelog/

Codecov Report

Merging #1240 (93b59da) into main (e1468e2) will decrease coverage by 0.0%.
The diff coverage is n/a.

:exclamation: Current head 93b59da differs from pull request most recent head c145683. Consider uploading reports for the commit c145683 to get more accurate results

@@           Coverage Diff           @@
##            main   #1240     +/-   ##
=======================================
- Coverage   64.3%   64.3%   -0.1%
=======================================
  Files        245     245
  Lines      21485   21485
=======================================
- Hits       13827   13826      -1
- Misses      7658    7659      +1

Impacted Files
Coverage Δ

light-client/src/lib.rs
100.0% <ø> (ø)

proto/src/lib.rs
100.0% <ø> (ø)

tendermint/src/lib.rs
100.0% <ø> (ø)

testgen/src/vote.rs
84.8% <0.0%> (-0.9%)
:arrow_down:

testgen/src/light_block.rs
76.1% <0.0%> (-0.6%)
:arrow_down:

light-client-verifier/src/types.rs
39.0% <0.0%> (ø)

tendermint/src/timeout.rs
85.9% <0.0%> (+1.7%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Redo] Add Spanish Syllable-based Phonemizer (now with dictionary) + small Delta English Phonemizer fix

Again, you can ignore the other commits, they don't actually change anything about the files.

Dictionary file not needed; apologies.


Rate limiting for Imagegenerator

I am encountering a technical issue while attempting to convert SAP Signavio Academic models into event logs (XES) using the sap-sam Image Generator module.
I have been following the process outlined in the python notebooks (https://github.com/signavio/sap-sam/blob/main/notebooks/3_images_and_XMLs.ipynb) and utilizing the sap-sam Image Generator module (https://github.com/signavio/sap-sam/blob/main/src/sapsam/ImageGenerator.py) to convert the models. I have successfully converted approximately 50 BPMN JSON files from the CSV format to .bpmn files.
However, I am now facing an issue with the generate_xml method within the Image Generator module. After successfully converting the initial set of files, the method suddenly stops returning any output, and the conversion process halts without generating any errors or indications of failure. I have reviewed the logs and examined my code to ensure there are no obvious errors or misconfigurations.
Despite my efforts, I have not been able to identify the root cause of this issue. To provide more context, I am utilizing the SAP Signavio Academic models available at this link: https://zenodo.org/record/7012043.

@sap-dianasola @TimKam do you have a solution for this? It seems like the Image Generator Module does not terminate. Is there a limit per user? Or does the function have no timeout?
We really would like to use all BPMN models but without converting them via the Image Generator module it seems like we are stuck here.

@ppfeiff @colodenn Thanks for the @mention, without it I don't get a notification :-)
Can you try to artificially slow down your image generation?
Perhaps you send too many requests in a short time.

We added a delay between requests and it sems like we are able to get more successful conversions. We will report back.


[FR] MIDI Input for live/step recording

MIDI input would be killer, either in a step mode or in a live recording situation. I'm unaware of the complexities though.

x: We can listen to midi in without issues. There will be some concurrency issues in a live recording situation though (reading and writing steps at the same time) so we would need to add some mutexes on steps data.
Do you use step recording on the digitakt? I own a syntakt, and I only use the live recording mode. Step mode has always seemed weird to me.

To be honest I do not use step recording as much neither, I can see some use cases for some styles of music though.
My original though was to allow the user to press a key if it has the "note" parameter focused to set the note.
While on this topic, this kind of behavior (midi input for interacting with current parameter) could be potentially beneficial for a future basic midi learn: focus a param, press midi learn keymap, move knob, an that parameter is now controllable via midi. It would react to the 'selected step' though. Just an idea.


Visualization labels should support multiple group by

When using multiple groupBy in a query, the API returns a response with all these fields in the result, but the visualization tool uses only one of the fields as label. This makes it kinda hard to figure out which value it is as multiple values are getting the same label (the point of using multiple group by is precisely because none of the column is identifying the group uniquely by itself).
It would be great to build default labels with all grouping fields taken into account (maybe joining them with a separator like - or /), or to give an easy way to build labels for such cases

is there any news about it ? It is unfortunate that the JS visualization tool does not handle multiple groupBy clauses while the API does.

@stof apologies for the late reply. This one took some time, but we've recently released this here: https://github.com/keen/keen-js/releases/tag/v3.4.0-rc4
CDN: https://d26b395fwzu5fz.cloudfront.net/3.4.0-rc4/keen.min.js
We'll get this rolled into an official (non-rc) release soon, but feel free to use this version.. it's running in the Explorer right now, without issue.


Domain access request from sandbox for common XYZ tile services

What domain(s) needed? Please describe.
https://server.arcgisonline.com
http://server.arcgisonline.com
https://tile.stamen.com
http://tile.stamen.com
https://tile.openstreetmap.org
http://tile.openstreetmap.org
Why this domain(s) needed? Please describe.
These domains will allow access to common XYZ tile services to serve as basemaps/image underlays for plots, e.g.:
https://server.arcgisonline.com/ArcGIS/rest/services/{variant}/MapServer/tile/{z}/{y}/{x}
Provide impacted notebook reference and purpose.
STAC code here: https://docs.dea.ga.gov.au/notebooks/Frequently_used_code/Downloading_data_with_STAC.html

Also need to add the http/https versions of the above; updated

Confirm that this now works correctly - thanks @mmochan!


pekkoParadoxCopyright property should respect new lines

We need to be able to space the copyright statement over multiple lines.
pekkoParadoxCopyright :=
  """© 2011-2022 Lightbend, Inc.
    |Apache Pekko, Pekko, and its feather logo are trademarks of The Apache Software Foundation.""".stripMargin

These 2 lines should appear on 2 separate lines instead of appearing on same line in the generated HTML.

This is HTML, so you can use
 for newlines where needed.


Qingwei/fix empty array

Work in progress, dont merge =)

I am done, if it's ok, you can merge =)


Rename itk to libitk in README

This documentation update follows the package rename.
For #10

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

@jjhelmus @msarahan Do you have the admin privileges or do you know who does to enable conda-forge/libitk-feedstock in AppVeyor?

@jjhelmus @msarahan Can we get some help with enabling AppVeyor for this repo after it was renamed?
Thanks!

Returning from vacation. I can take a look later tonight.
On Jul 31, 2017 12:40, "Bradley Lowekamp"<EMAIL_ADDRESS>wrote:

@jjhelmus https://github.com/jjhelmus @msarahan
https://github.com/msarahan Can we get some help with enabling AppVeyor
for this repo after it was renamed?
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/libitk-feedstock/pull/11#issuecomment-319141077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACV-eFmuVaPkOMYXmW9uQ0HiscxlgvKks5sThF-gaJpZM4ObmOv
.

Sorry guys, looks like I don't have adequate permissions to change anything about the conda-forge stuff on appveyor.  @ocefpaf @jakirkham may be better equipped.

Sorry guys, looks like I don't have adequate permissions to change anything about the conda-forge stuff on appveyor.

We need to fix that :smile:
But here it is: https://ci.appveyor.com/project/conda-forge/libitk-feedstock

Super, thanks @ocefpaf @msarahan !


Default use owner function to get address

Description
Confidential EVMs such as Sapphire prevents direct getStorageAt calls from accessing raw slot data in order to allow a smart contract to permission access to its own state.
The default proxy supports the EIP173 spec function owner which appears to be the smoothest path towards supporting additional EVM like networks.
Would y'all find this compatible? An alternative solution would be to compare msg.data with a set of predefined keys and to return the storage slot.
https://github.com/wighawag/hardhat-deploy/blob/e3727896a812fe1a17e04f52a4aecc42c7b13ed4/solc_0.8/proxy/EIP173Proxy.sol#L29-L31
Relates to issue https://github.com/wighawag/hardhat-deploy/issues/530.

Happy to have that in, but it should support both.
it should check if the proxy has an owner function and uses it if it does, else fallback on reading storage slot

Happy to have that in, but it should support both. it should check if the proxy has an owner function and uses it if it does, else fallback on reading storage slot

Appreciate the feedback. Will do.

@wighawag one more look please?

Thanks!
available in 0.12.3


[Workbench] Warning message during startup for database.conf mount

When database.conf is defined, the below warning is triggered during startup. The permissions are correct (root:root) and likely don't ever need an update in an k8s environment. I guess the check comes from an internal WB process but is likely only relevant for non-k8s envs?
Would be good to account for it as one cannot do so because the referenced mount is initiated by the chart. AFAICS this affects all deployments which don't use the built-in SQLITE DB.
config:
  secret:
    database.conf
      provider: postgresql

2024-01-09T15:53:17.928385Z [rserver] WARNING Failed attempt to update ownership of database configuration file /mnt/secret-configmap/rstudio/database.conf to root user: Read-only file system - please ensur │
│ e that the file owner is root if it contains sensitive information; LOGGED FROM: rstudio::core::Error rstudio::server_core::database::{anonymous}::readOptions(const string&, const rstudio_boost::optional<rs │
│ tudio::core::system::User>&, rstudio::core::database::ConnectionOptions*, std::string) src/cpp/server_core/ServerDatabase.cpp:343

Thanks for reporting this! I do think we are a bit too verbose here and should update the product accordingly! I will pass this along 😄


Enabled authorization header obfuscation by default

Coverage remained the same at 100.0% when pulling bc53dacd045764ea4567347ac11d13ee6796d91c on whiskeysierra:feature/obfuscate-authorization into ceb2921ef961a56a55068700e62ce5cd58c54738 on zalando:master.


Remove libnvjitlink dependency.

PR #85 added a dependency on libnvjitlink. This was needed only temporarily, due to an issue with a particular build of cupy that caused an undesired conda environment. This should be safe to remove.

/merge


[RFC]: document usage with typescript

Description
I'm tying to use some of the libs with TS and it's very unclear how to do this.
import * as ss from "@stdlib/nlp-sentencize"
gives an error:
This module can only be referenced with ECMAScript imports/exports by turning on the 'allowSyntheticDefaultImports' flag and referencing its default export.ts(2497)
so should i add that to a tsconfig ?
allowSyntheticDefaultImports: true
doesn't seem to help.
it seems most people write TS nowadays so a bit less of an onboarding brick wall would be helpful.
I searched the docs and can find no mention of how to import into a typescript project.
Related Issues
Related issues # , # , and # .
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@Planeshifter Would you be able to help out with this?

i can help you in this please assign me this

We don't want to complicate our build step; shipping both CommonJS and ES6 modules is notoriously riddled with gotchas. As you said, one can configure one's TypeScript project to be able to consume CommonJS seamlessly. There should be plenty of guides available online and I have used @stdlib packages in TypeScript projects myself on multiple occasions.
To anyone facing this issue and not being able to resolve it, feel free to send a link to a repository where the problem is reproducible and I am happy to assist in updating the tsconfig.json to get it to work.


<IP_ADDRESS> [BACKLOG-15685] As a Chris, I want to be able to disable steps when r…

…unning on Spark
Remove steps following inactive input.
Backport of https://github.com/pentaho/pentaho-kettle/pull/3838
@mkambol

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/ael/adapters/TransMetaConverter.java
  engine/test-src/org/pentaho/di/trans/ael/adapters/TransMetaConverterTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.14%:small_red_triangle_down:
Complexity Change: -7.69%:small_red_triangle_down:

org.pentaho.di.job.entries.getpop.MailConnectionMeta

Branch Change:  + 1.00%
Complexity Change:  + 1.41%
Instruction Change:  + .30%

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.28%:small_red_triangle_down:
Line Change: -3.87%:small_red_triangle_down:

org.pentaho.di.trans.ael.adapters.TransMetaConverter

Complexity Change:  + .17%
Instruction Change:  + .28%
Line Change:  + .35%
Method Change:  + .26%

org.pentaho.di.trans.step.StepMeta

Branch Change:  + .68%
Complexity Change:  + .58%
Instruction Change:  + .19%
Line Change:  + .26%

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -.11%:small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change:  + 4.17%
Complexity Change:  + 4.21%
Instruction Change:  + .28%
Line Change:  + .74%

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2.00%:small_red_triangle_down:
Complexity Change: -1.89%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -.06%:small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 4.71%
Complexity Change:  + 5.41%

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change:  + .07%

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -.10%:small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -.18%:small_red_triangle_down:

org.pentaho.di.trans.steps.systemdata.SystemDataMeta

Branch Change: -2.04%:small_red_triangle_down:
Complexity Change: -2.04%:small_red_triangle_down:
Instruction Change: -.32%:small_red_triangle_down:
Line Change: -.81%:small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change: -.53%:small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change:  + .18%

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change:  + 1.79%
Complexity Change:  + 1.19%
Instruction Change:  + .07%


Integration Test - Release - 2019/06/04 19:04:32

Auto create for integration test. IssueCommandFlow

@PRMergerTest2 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Added database agnostic case insensitive search option

Hi, so i finally managed to deal with all the composer & co sh*t :p
This is the PR i promised, i have NOT tested it with mysql, but i have used all plain standard SQL stuff so it should work without issues with all engines.
It would be great if you can take a look at this and consider merging.
Cheers!
// Diego

Im sorry that i left out a commented debug line, you might want to remove that for code prettiness on line 203.

Great!
You can remove that line in another commit to the branch, it will update your PR.
What I don't like right now is the implication that if this option is not set, the search is case-sensitive, which is not true for MySQL etc.
Maybe we have to think about the wording a bit.

Im not a mysql person per-se, but it is my understanding that mysql will be case sensitive or insensitive depending on the collation used. Please correct me if im wrong, but i have been using PostgreSQL (and a few other non cakephp supported rdbes) for almost the past 10 years so im not certain anymore of what mysql does or does not. But at least based on what im reading, unless you specifically usa one of the _ci collations in mysql, the behavior will be just like in postgres...
About the wording, how about something like 'ignoreQueryCasing'  ? I think thats actually closer to what my patch is actually doing...

You are absolutely on point with this one. However the default collation is a ci collation.
What do you think of having default option array
search => [
    'prefix' => true, // use "LIKE …%" instead of "LIKE %…%"
    'ignoreCase' => true, // use "LOWER(·)"
],

This leads to a bit more work but makes the configuration clearer to follow. Would you like to do that?
I have another concern though. I don't think SQL LOWER() always behaves the same as strtolower() in PHP does. Think about encoding issues, e.g. latin1 vs unicode. On the side of the database this will be controlled by the collation yet again.
I think both LOWER operations should be done in SQL, however more work needs to be done to do this in a safe way (pass $right as extra argument).

I assume $condition = ["LOWER({$column}) LIKE" => "LOWER({$right})"]; would be fine.

Yeah i was actually doing that, however, according to the mysql documentation that might not work as expected for BINARY, VARBINARY and BLOB types, but i guess those 3 are rares for the kind of data u are likely to display on a table, and much less for the kind of data you might end up filtering against a string.
I will update this PR with the whole changes if you are ok with it.
More info about mysql marginal issues here
// Diego

A problem might occur with boolean columns, calling a LOWER on it will produce errors, same goes with date fields.

@DeadKat is right, thinking of alternatives.

I have updated the code to cover all the stuff we discussed in here @ypnos-web and @DeadKat. I tested it on my local postgresql 9.5 development DB and it seems to work just fine, even when intentionally trying to search on ridiculous field types.
Let me know what u think.

I can't test right now on a POSTGRESQL project but will do asap, looking fine to me .

It's still using strtolower() though.

Yes @ypnos-web , on that specific case, i personally think that if safety is the concern, it is better to use php's own method which we know will always give us back the same result, than relying on an SQL implementation that might return slightly different results across different sql engines under rare borderline scenarios. If you really think that for lowercasing the input query it is better to rely on an sql method, i can change it, but i certainly think its not the best approach :) Can you tell me what is the concern that you have with strtolower() because i might be just missing something here :p
// Diego

Maybe my reasoning was not stated clearly enough.
Imagine a string "ÄÖÜ". Depending on the locale on the server etc., `strtolower()´ will make this "äöü" or keep it at "ÄÖÜ". In the worst case, if the string is unicode, it might also destroy it completely (see http://stackoverflow.com/questions/2516448/problems-with-strtolower-function).
We have the same problem on the server side. Consider the field in the database is set to "ÄÖÜ". Depending on the collation, the database might make it "äöü" or keep it at "ÄÖÜ".
The only way to have this addressed in a consistent matter in all situations so that the comparison of "ÄÖÜ" with "ÄÖÜ" will always return true, is to do both conversions either on the PHP side or the SQL side. Obviously the first is not an option, so it is wise to do it in SQL.
My safety concern however was only that you do not write:
$condition = ["LOWER({$column}) LIKE LOWER({$right})"];
But instead write:
$condition = ["LOWER({$column}) LIKE" => "LOWER({$right})"];

This is straight from the docs:
You should remember to use the function builder whenever you need to put untrusted data into SQL functions or stored procedures:
// Use a stored procedure
$query = $articles->find();
$lev = $query->func()->levenshtein([$search, 'LOWER(title)' => 'literal']);
$query->where(function ($exp) use ($lev) {
    return $exp->between($lev, 0, $tolerance);
});

// Generated SQL would be
WHERE levenshtein(:c0, lower(street)) BETWEEN :c1 AND :c2

Source: http://book.cakephp.org/3.0/en/orm/query-builder.html#using-sql-functions

Fair enough.

Well, i have implemented it the sql way, however, for some weird reason it doesnt seem to like it (no matter what, the query returns no results).
I have even debugged the generated SQL, which is correct, and gives me the proper results when i run the query manually, so there must be something else that im missing at some other part of your code that might be exploding because of this change.
I have been writing code for a long time and my brain is kind of burned now, i will give this another taught later and maybe figure out why and where it is exploding.
Thanks for your help.

Sorry I gave a wrong guidance first and then was not specific enough when I realized my mistake!

Oh i see, makes sense and is clear now that you say it. I wish i was so well versed on the internals of this framework.
Your explanation was spot on, the problem is that im just getting to know this ORM and the framework itself.

No worries, at least this gives you the opportunity to learn new stuff :)

This now works as expected.

Thank you for the great work! I have a couple comments in the code that you might go over real quick before I merge this?

Sure thing, i will take care of all of them and update this branch, thanks to you for this great time saver!

Hello Diego, it would be great if you could have a final look so we can merge this PR soon. Thanks!

I'm Closing this PR in favor of a newer one.

Hello @DiegoMax, based on some new developments regarding proper comparisons of non-string types, I implemented this feature in the feat-lower branch. Would you like to have a look and test it?

@ypnos-web hey, sorry about it, i ended up forking this and doing some other mods cause i could not wait for you to merge my changes (i needed to put  project in production).
I will take a look and see if maybe i can (even manually) merge your and my code somehow 📦
https://github.com/DiegoMax/cakephp-datatables/blob/dev-master/src/Controller/Component/DataTablesComponent.php
You can take a look there ^^.
Thanks.
Diego.

Yes, I have seen your work in your repository. I think you can benefit from a merge, the code is a bit cleaner, and staying in sync should make maintenance easier for you. Obviously your call, just wanted to let you know.

Of course im 100% on the side of merging, my fork was just a quick fix for my own benefit, im not intending to fork this project for any other reason. I will take a look and see if i can merge. Thanks for your time, really appreciated!


Test Field Absolute Driving/Pose orientation

We need to make absolutely sure that our pose code is correct.  to do this, we have to do tests that permute these conditions:

Red or Blue
Power up in a spot vs pressing pose reset button
start facing each one of these 4 locations: amp, speaker ( straight on, left side angle, right side angle)

together, this results in 4x2x2 = 16 tests

To test the different positions, we need to run each auto in path planner, and make sure that the robot drives correctly after each of these paths has run, with correctly as:

right direction
pose doesnt get messed up

Unit testing of some kind would make this less labor intensive

consider testing #94 along with this one


Create a dcm4che docker image

Create dcm4che docker image to use in the image pathway

Implemented, given by DCM4CHE themselves


Update new tracker

Add Kubernetes Job to track metrics
Details of the job could be found in https://github.com/IBM/metrics-collector-client-kubernetes
You can find your repository stats at https://metrics-tracker.mybluemix.net/stats
Feel free to give any feedback for this approach.

LGTM. Will be testing and gonna merge it once #15 is merged


Update font-terminus-nerd-font-mono to 1.1.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] sha256 changed but version stayed the same (what is this?).
I’m providing public confirmation below.

Thank you for the contribution. It was merged directly as 71fc89b1f8f4b0c969f7ef6b33cd58b7943bb478. Your contribution is still credited to you.


Support Grease Behavior

Problem:
Grease extensions and values sent by clients may cause errors in s2n server if not handled correctly
Proposed Solution:
Ensure s2n handle grease correctly according to ~~https://tools.ietf.org/html/draft-davidben-tls-grease-00~~ https://tools.ietf.org/html/draft-ietf-tls-grease-04
Grease Checklist

[x]  cipher_suites

[x] tests

[x] client extensions receive

[x] tests

[x] name group values, supported_groups, key share entries

[x] tests

[x] signature_algorithms

[x] tests

[x] supported versions

[x] tests

[ ] psk_key_exchange_modes

[ ] tests

[x] ALPN

[x] tests

We already ignore any unknown extensions, which includes those in the GREASE range:
https://github.com/awslabs/s2n/blob/f77fc9fe976f7d0d6a4d8d823c706ec4aff9bc99/tls/s2n_client_extensions.c#L258-L302
We have a switch statement that handles all the extensions we do know about, without a default case, which causes us to ignore anything undefined.
This issue should probably track adding a unit test to validate this behavior since I don't think we have one for GREASE right now.

I've updated the issue's description with a checklist to track grease tests for client extensions along with other grease-able portions of the TLS handshake.

Moving this to the backlog. Next step is to plan GREASE support in the client.


"Cannot resolve method using[...]"

https://stackoverflow.com/questions/44832599/cannot-resolve-method-usingcom-firebase-ui-storage-images-firebaseimageloader
I'm having the same problem on my end. It tells me nothing more than
"Cannot resolve method using(com.ui.firebase.storage.images.FirebaseImageLoader)".
Everything else seems to be working fine.

FirebaseUI version: 1.2.0
Glide version: 4.0.0-RC1

It appears this library is using the 3.x version of Glide, and you're using the newer 4.0.0 branch. We need to update the version used in FirebaseUI-Android, but for now, you'll have to use version 3.
@SUPERCILEX Are we down for a PR?

@TheCraftKid you can give it a shot, but I think it'll take far more effort than simply changing the version number.  Because of that

We'll have to migrate away from using
I dunno how it's going to work out in terms of backwards compatibility

Do give it a shot though! 😄
FYI: this is a dup of #731.

@TheCraftKid the big issue is backwards compatibility if we want to make it into the 2.1 release.  Otherwise we need to wait for a major version, and I don't think we should do that again too soon since 2.0 is so fresh.

As @SUPERCILEX said, closing as a dup of #731

Dear all,
Following
Git Wiki for Storage
Dependencies
compile 'com.firebaseui:firebase-ui-storage:3.1.0'
compile 'com.github.bumptech.glide:glide:4.1.1'
annotationProcessor 'com.github.bumptech.glide:compiler:4.1.1'
In MyAppGlideModule, on the following line...
registry.append(StorageReference.class, InputStream.class,                 new FirebaseImageLoader.Factory());
I'm getting Cannot Resolve Symbol on Factory(). Screenshot below...

I checked the source code and the Inner Static class Factory is present in the code.
What could be wrong? I'm stuck and cannot complete the Image Download part, so any help would be appreciated!
Thanks in advance...
SG


Date Format in Generate Members reports

The date format of all dates in the PDF and xls formats are in mm/dd/yyyy rather than dd/mm/yyyy.
This is both "Patrol List" and "Member List"

Thanks for that.
Didn't take you long to find this. What do you think of it?

Hi James, it seems all dates on reports are in US format rather AU format - so maybe a general setting somewhere.
I do like the layout and think the design is awesome. Happy to review each part as they keep coming out.

Updated Azure function to en-AU culture


Issue #1: Update to modern metadata

Fixes #1
This PR updates the _MinimalHIToolbox bindings to the prefered metadata system for PyObjC.
I've manually created the metadata file because generating it through my tooling results in too many definitions.

The PR requires PyObjC 10 due to using a newer way to initialise the _MinimalHIToolbox module (use __getattr__ instead of a subclass of types.ModuleType).
Given the small size of these bindings and the stability of the API I could also do a PR that drops the _metadata module and just initialises the various types, constants and functions manually.  Using PyObjC's lazy loading system is not really useful here.

Tested this branch and it seems to work, so I will merge and address follow-ups later.


Fix spacing issues in sidebar nav menu

Issue #116
The sidebar nav menu for the docs has spacing issues
Changes

Reduced side padding for the list elements
Added a margin to stop the list elements from touching the scrollbar

Will look like this:

Related Issues

Issue #116

LGTM! Thanks for your contribution @nithilan4


Logo

I'm not sure if this pull request is intentional or whether it was an accident. Either way, please make sure to never share your APS Client Secret as you did here. Since the client secret has already been exposed, I would suggest that you go to https://aps.autodesk.com/myapps, find your application with Client ID GaKVwWTJYRo9zkpKtv60Y5SAgQkbxH0p, and generate a new secret.

I apologize, I am not a developer and am really struggling to simply create viewers that can work with my iLogic forms.
I am really struggling and do not want to learn how to be a full developer, just want to build apps to streamline interactive product catalogs of all shapes and sizes.

From: Petr Broz @.>
Sent: Monday, September 18, 2023 5:23 AM
To: autodesk-platform-services/aps-simple-viewer-nodejs @.>
Cc: Ron King @.>; Author @.>
Subject: Re: [autodesk-platform-services/aps-simple-viewer-nodejs] Logo (PR #15)
I'm not sure if this pull request is intentional or whether it was an accident. Either way, please make sure to never share your APS Client Secret as you did here. Since the client secret has already been exposed, I would suggest that you go to https://aps.autodesk.com/myapps, find your application with Client ID GaKVwWTJYRo9zkpKtv60Y5SAgQkbxH0p, and generate a new secret.
—
Reply to this email directly, view it on GitHubhttps://github.com/autodesk-platform-services/aps-simple-viewer-nodejs/pull/15#issuecomment-1723130525, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BB4LNQ3XFG6SOPVS3XEU2U3X3AOJJANCNFSM6AAAAAA4SLZLZA.
You are receiving this because you authored the thread.Message ID: @.***>


Merge pull request #12 from ClownMonster/Django-practice-P1

Django practice p1

from Django branch


Need Help to create headlessly Firefox for server

Hi,
How can I run Firefox on Linux server heedlessly any option for this in here

@nitinrakhpune,
Thx for the feedback.
Added moz:firefoxOptions and slightly refactored code, now you can add arguments in browser session.
Reference: https://github.com/GermanAizek/webdriverxx/commit/b85a2cb1ed608eb48b0acf5032999a7737367c00
Please before using example, clone repo with latest changes.
Example:
FirefoxOptions opts;
opts.SetFirefoxArgs({"--headless"});
WebDriver ff = Start(Firefox().SetFirefoxOptions(opts));
ff.Get("https://nyanpasu.com");

@nitinrakhpune,
Please note I updated the syntax for Firefox capabilities.
Reference: https://github.com/GermanAizek/webdriverxx/commit/a39597b653afc5fc648168e7f5347dec76b3490f#diff-27c7f224e283858603465fb43e88c3380acc9807eaf5054b3229343c22c498ed

Hi
Thanks for your valuable support , I would like to contribute to this
framework.
Thanks
Nitin
On Tue, May 4, 2021 at 6:26 PM Herman @.***> wrote:

@nitinrakhpune https://github.com/nitinrakhpune,
Please note I updated the syntax for Firefox capabilities.
Reference: a39597b
#diff-27c7f224e283858603465fb43e88c3380acc9807eaf5054b3229343c22c498ed
https://github.com/GermanAizek/webdriverxx/commit/a39597b653afc5fc648168e7f5347dec76b3490f#diff-27c7f224e283858603465fb43e88c3380acc9807eaf5054b3229343c22c498ed
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GermanAizek/webdriverxx/issues/19#issuecomment-831919964,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT5PIJZMTIZGYGGHH2WWKLTTL7VH7ANCNFSM437XOZHQ
.

@nitinrakhpune,
Okay, just stick to our code style. Create pull requests and I review it.
I was surprised I helped you so quickly.

@nitinrakhpune,
We can organize a party in any social network or messenger, it is preferable to raise our IRC or XMPP server. You can also fully deploy a bagtracker with full documentation on the site.

Hi
Sure, will do that.
Thanks
nitin
On Fri, May 7, 2021 at 3:34 AM Herman @.***> wrote:

@nitinrakhpune https://github.com/nitinrakhpune,
We can organize a party in any social network or messenger, it is
preferable to raise our IRC or XMPP server. You can also fully deploy a
bagtracker with full documentation on the site.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GermanAizek/webdriverxx/issues/19#issuecomment-833901375,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT5PIJ43BU2PYMVD5LWQWO3TMMG73ANCNFSM437XOZHQ
.


⚠ Bofrost.at has degraded performance

In 13ae65a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1799 ms

Resolved: Bofrost.at performance has improved in 4fc3601.


Fixed #33626 -- Cleared cache when unregistering a lookup.

Signed-off-by: Himanshu-Balasamanta<EMAIL_ADDRESS>Problems fixed

Running tests individually and running all tests of a module would give different results due to incorrect pending data in cache
Fixed one test case that was passing due to incorrect pending cache

Fixed ticket#33626

@Himanshu-Balasamanta You can look at the flake8 and black errors if you like. 🙂
There's some guidance on the using pre-commit to run these here: Coding Style | Django Documentation | Django

@carltongibson , do you want me to reopen the PR with commit message "Fixed #33626" or should I just push another commit to this PR?

If you update the commit you can force push to this branch. (Or we can do it later, but ideally... 👍)

@carltongibson, Done.

Super. Thanks.


Q3 Mega-issue: Joe's Goals

My goals this quarter are more numerous, so I'm putting everything in one issue. Here we go.
Goal 1: Make sure we have successful launch plans for new products

[ ] Data Warehouse launch
[ ] Web Analytics launch
[ ] Mobile Replay launch
[x] Launch Onboarding 6.0 to support new growth strategy

Goal 2: Run another YC S24 campaign, but with less direct work

[x] Add the PMF guide to the YC kit
[x] Run the YC kit as before, with no additional work
[x] Arrange/support a Tim & James talk in SF if the opportunity arises
[ ] Report on success internally as the program continues

Goal 3: Onboard community manager

[ ] Hire a Community Manager and complete their onboarding
[ ] Get that person set up for success, with their own Q3 goals
[ ] Arm that person to find two more influencers we can work with

Goal 4: Continue to support CS & Sales

[ ] Get the SF x C.io pipeline working, or find a replacement
[ ] Create an automated email flow for demo follow-ups
[ ] Create an automated process for users on timed place (YC + Startups)
[ ] Continue to arm CS & Sales with case studies for all new products
[ ] Create a long-term nurture flow for unconverted users from demos
[ ] https://github.com/PostHog/posthog/issues/22036

This is a great list!


Update readme with existing Prometheus setup

How to set up an existing Prometheus for alertmanager feature.

Closing this since the samples contains some examples how to enable the alertmanager feature for the koperator with some rules as well. https://github.com/banzaicloud/koperator/blob/master/config/samples/kafkacluster-prometheus.yaml


Nested calls doesn't return the value

When I use one function inside another the font size doesn't return properly:
font-size: ${size(prop('fontSize'))};

But when I use only one of the functions the return is correct:
font-size: ${({ fontSize }) => key(['sizes', fontSize])};

This is the intended way to use the lib or its some kind of bug? I analyzed the return from prop function and see that is a function, can this be the problem that can't be used in nested calls?

I had the same problem.
for those who have the same, it is possible to get the theme by props:
font-size: ${({ fontSize, theme }) => theme[pathToVariable] )};


Update forc README for recent out/ directory and lock file changes

Related PRs #825, #796.
Also moves the forc update section to follow the section related to the lock file and pinning.

Totally, good call! I'll land this for now and open an issue.


pageSize propType missing [V6]

https://github.com/tannerlinsley/react-table/blob/v6/src/propTypes.js
@tannerlinsley I see pageSize propType missing in proptypes. Because of this I am getting this warning:
checkPropTypes.js:23 Warning: Failed prop type: t: prop type pageSizeis invalid; it must be a function, usually from theprop-typespackage, but receivedundefined``
Can this be fixed?

V6 is no longer maintained. I would suggest forking the v6 branch, implementing any changes you see fit, and using that branch until you can upgrade to v7.


Conventional way to configure client

Httplug interfaces does not provide a way to configure client behaviour such as timeouts, SSL settings or other parameters that cannot be set in the RequestInterface.
For example. In dev environments we want our HTTP client to ignore SSL errors. But we can do this only when instantiating particular implementation. It has two disadvantages:

we can't use HttpClientDiscovery;
code, where the client is introduced through the interface, can't change these settings.

imho this is the responsibility of the bootstrapping code, not of code using a client.
there can also be some overlap between the plugins we offer for HTTPlug and features of the client used (guzzle or even curl can do some of the things the plugins can do, but often we will want to make them "dumb" to have control in the plugins.)
but this setup needs to be the job of either the adapter or the bootstrap code of an application. e.g. in symfony, there are elegant ways to do that.
the discovery is a highly opinionated way of doing things, looking like the thing laravel misnames "facade". dependency injection is much cleaner and more flexible.
but its possible to set the client that should be discovered manually. so the bootstrap code can configure the discovery to its liking, as long as its executed before discovery is triggered.

I mostly agree with the things @dbu said.
One addition (actually a highligh of something that is already mentioned): discoveries have two purposes:

provide easy, zero-configuration client construction
provide defaults

And what about different option names of client or request? For example, Guzzle6 has an option connect_timeout, but in CurlHttpClient it is named connection_timeout. How to abstract from client-specific option names?

Are you asking froma convenience point of view or a standardizing point of view?
Client configuration is always "manual", so as we said above, having a conventional way of doing it doesn't make much sense.
However it's a nice idea to have the same conventions for option names. It would cause less confusion.
Not sure if it is possible though, as I saw, some of the options are named after cURL variable names.
@mekras Could give a better insight.

In the context written above, I think that CurlHttpClient should just accept PHP cURL constants as options keys.

Are you asking froma convenience point of view or a standardizing point of view?

I'm just trying to understand, if and how I can make an universal configuration for client in my application. So if my app component is using Httplug with Guzzle6 adapter, I'm configuring the component with an array like this:
[
    'base_uri' => 'http://httpbin.org',
    'allow_redirects' => false,
    'connect_timeout' => 10,
    'timeout' => 30,
]

But when I'll decide to use another adapter, I will need to use something like this:
[
    'url' => 'http://httpbin.org',
    'redirects' => false,
    'connection_timeout' => 10,
    'response_timeout' => 30,
]

Maybe we need some kind of options adapter? Or add constants for common option names to Http\Client\HttpClient?

This may be solved in the particular framework adapter like https://github.com/php-http/HttplugBundle

We have already discussed this earlier and decided not including it in the contract. The possible number of options and ways to configure a client simply doesn't allow that.
If you decide to use another client, you should configure it, which is the only point where you know what client you use.
In a DI context this shouldn't be a hassle, like in the bundle @mekras linked.

So, you think that it must be an application (or component/module/bundle) logic. I understand, thanks.

Absolutely, this is the whole idea about httplug: rely on contract in reusable component, rely on actual implementation, config in the application.

I think this issue can be closed.

And another question: I can't use HttpClientDiscovery in this case, right? Because I don't see the way to configure Guzzle6 with HttpClientDiscovery. Maybe you can provide a sample code with Guzzle6 adapter?

No, you can't. If you need any configuration, you already have to know which client you use.
Discovery is a zero-knowlege, zero-configuration thing.

@RomeroMsk We are available on slack, you can ask for help there. Can I close this?

I can understand the confusion. It is not clear enough how it differs in usage of Httplug when writing a library and when writing a library.
@RomeroMsk When writing a library you should always know what client to use, you should instantiate it yourself and configure it as you want.
The HttpClientDiscovery is used when writing a library. =)

when writing a library and when writing a library.

Hm..sorry? :stuck_out_tongue:

When writing a library you should always know what client to use, you should instantiate it yourself and configure it as you want.

When writting a library, you should accept an HttpClient which should be preconfigured. Inside your library, you don't need to know what client you have.

The HttpClientDiscovery is used when writing a library. =)

See this comment for the use cases of discoveries.

Sorry, I've updated the comment =)

Thank you, guys, now it is more clear for me! Of course, you can close the issue.

I guess we will have to provide an example application to clear the confusion. Libraries using Httplug will be good examples as libraries.

I guess we will have to provide an example application to clear the confusion. Libraries using Httplug will be good examples as libraries.

Exactly ;)

I'm not feeling good on this. I'm trying to write a project using omnipay/omnipay-common development version which need extra  php-http/client-implementation package ,so i choose php-http/guzzle6-adapter, then i'm getting trouble with requests using https  ,I want to set SSL things on client init ,cant do so now. anyone knows how to fix it?

@php-cpm if this is about a reusable library, it should provide instructions how to configure the client, but not tie to guzzle6. if this is an application and you chose httplug with guzzle6-adapter, you can also simply pass an instance of the correctly configured GuzzleHttp\ClientInterface instance to the Http\Adapter\Guzzle6\Client constructor.

it is a reusable library.
lib  lokielse/omnipay-wechatpay depends on omnipay/omnipay-common v2 which binds to guzzle3, too old
so I'm working on update its depend to omnipay/omnipay-common v3 which   finds httpClient auto.
yet without binding to guzzle6, I have no idea how to set options
        $options = [
            'curl' => [
                CURLOPT_SSL_VERIFYPEER => true,
                CURLOPT_SSL_VERIFYHOST => 2,
                CURLOPT_SSLCERTTYPE    => 'PEM',
                CURLOPT_SSLKEYTYPE     => 'PEM',
                CURLOPT_SSLCERT        => $this->getCertPath(),
                CURLOPT_SSLKEY         => $this->getKeyPath(),
            ]
        ];

these settings should be hidden for lib users ,so finally I do so.


Support for backup api endpoint

We needed a way to clean up backups on remote storage on a schedule since FMC doesn't natively seem to have a backup retention policy. This should be enough to get us where we wanted and still use fmcapi lib.

thanks for the PR


Annotation data does not correspond to image data

First of all, thank you for the AbdomenCT-1K dataset, which really solved the problem of partition generalization I encountered.However, when I downloaded the data, I found that the Mask data did not correspond to the Image data, for example, the Image data was 1~1000, but the maximum file of the Mask data was 1062, and the total number of mask was 1000. How to correspond to these data?

the Image data was 1~1000,

We invite some guys to download the dataset but we can not reproduce your problem. The number of image cases is 1062.

When I read data through SimpleItk, I said "No Orthonormal Definition found!"

It is interesting. Basically, we usually use itk-snap and nibabel to handle the data. Both of them work well with this case.

Thank you for your reply. Sorry for that, I didn't unzip the "Case_1000-.7z" file. However, there are only 1000 Mask data, which does not correspond to the number of image data (1-1063).  However, a cursory reading of the data set still shows an error  "No Orthonormal Definition found!" Data such as the following:
['00433','00405','00051','00702','00232','00423','00432','00401','00240','00244','00217','00403','00438','00687','00213','00549','00251','00681','00205','00221','00756','00448','00011','00049','00712','00021','00057','00249','00238','00219']

Please read the Readme. we keep the remained label hidden in the grandchallenge.
You can obtain the evaluation results by submitting the results.
Does nibabel also have this problem?

Thank you for your patience.
Do you mean the "HiddenTestSet1063-1112.txt" file?50 cases (1063~1112) of Mark data are hidden, but there is no intersection with Image dataset 1~1062.Moreover, there are 63 marks difference between Mark data and Image data.
Yep, "nibabel" reads fine, I prefer "Simpleitk" to read and write data, maybe I should switch to "nibabel" which is more compatible.

Please check the readme file in the mask folder
To avoid the ground truth leakage in AbdomenCT-1K benchmarks, we made 1000 annotations publicly available.
The hidden annotations can be accessed on the grand-challenge by submitting your segmentation results.
- Fully superivsed learning: https://abdomenct-1k-fully-supervised-learning.grand-challenge.org/
- Semi-superivsed learning: https://abdomenct-1k-semi-supervised-learning.grand-challenge.org/
- Weakly supervised learning: https://abdomenct-1k-weaklysupervisedlearning.grand-challenge.org/
- Continual learning: https://abdomenct-1k-continual-learning.grand-challenge.org/


[Company] Get Contact IDs at a Company

Adds API support for Get Contact IDs at a Company

Sweet, thanks!

Published to npm as 1.03


Adds isMatch method to Str and Stringable helpers

CI 报错是这个问题 https://github.com/filp/whoops/pull/751


Dashboard documentation seems hard to find

No direct link from https://dashboard.stryker-mutator.io
Starting from https://stryker-mutator.io I had to follow one link to the handbook on GitHub and then find dashboard.md.
I would really favor some kind of a direct link from https://dashboard.stryker-mutator.io.

Thanks for making us aware of this! Right now a link is in the app when you enable a repo:

But it would be good if you would have some documentation before you reach that point.
Would it be clear if there is a menu item docs in the header which links to the handbook?

Related to #33.

I think this is already fixed, we provide instructions on the homepage for a while now (they also link to the docs).


Allow releases to be tagged as security-related

Summary
When uploading a new release to NuGet.org, the package author should be able to choose to indicate whether the new version contains security fixes and which versions are affected.
Details
Tracking vulnerable NuGet packages is currently not an easy task. A lot of projects do not issue CVEs and if they do, they do not correlate the CVEs to their NuGet package. NuGet should support at a gallery layer indicating whether a package version should be avoided due to known vulnerabilities.
This proposal would have 3 main changes:

Add new UI elements on the package upload page to indicate a security release and affected versions
Change the "Version History" page to indicate previous versions that may contain vulnerabilities
Add additional info to the API response to include a flag on versions which contain vulnerabilities and which package version they should upgrade to

Implementation
Here are some examples of UI changes that may occur:

@anangaur

I think this is tied to package deprecation feature where authors can deprecate certain packages  and provide reasons and recommended package+versions: https://github.com/NuGet/Home/issues/2867

Closing this one. Pls use https://github.com/NuGet/Home/issues/2867 for any discussion related to deprecation, flagging vulnerable packages etc.


Make PersistentTopicsBase some methods async

Motivation
PersistentTopicsBase has some sync methods. Decide to make them async.
Volunteers wanted for this.
Methods

[x] createNonPartitionedTopic @Technoboy- #14030
[ ] updatePartitionedTopic @Technoboy-
[ ] getPartitionedMetadata @Technoboy-
[ ] getPartitionedTopicList @mattisonchao
[ ] getStats @mattisonchao
[ ] getInternalStats @mattisonchao
[ ] getManagedLedgerInfo @shibd
[ ] getBacklog @shibd
[ ] getPermissionsOnTopic @liudezhi2098
[ ] grantPermissionsOnTopic @liudezhi2098
[ ] revokePermissionsOnTopic @liudezhi2098
[ ] skipMessages @liudezhi2098
[ ] peekNthMessage @liudezhi2098
[ ] examineMessage @RobertIndie
[ ] terminate @RobertIndie
[ ] compactionStatus @RobertIndie
[ ] deleteTopic @RobertIndie
[ ] triggerOffload @HQebupt
[x] offloadStatus @HQebupt #14027

getPermissionsOnTopic
grantPermissionsOnTopic
revokePermissionsOnTopic
skipMessages
peekNthMessage

I  can fix some @Technoboy-

I can fix some @Technoboy-

Thanks for your help. assigned.

Hi, I can fix some @Technoboy-

getPermissionsOnTopic
grantPermissionsOnTopic
revokePermissionsOnTopic
skipMessages
peekNthMessage

I can fix some of them. @liudezhi2098

@mattisonchao Can I fix getStats and getInternalStats ? Thanks in advance.

@Technoboy- Current getManagedLedgerInfo  method are already async.

[x]  examineMessage @RobertIndie https://github.com/apache/pulsar/pull/14062
[x]  terminate @RobertIndie https://github.com/apache/pulsar/pull/14064
[x]  compactionStatus @RobertIndie https://github.com/apache/pulsar/pull/14066
[x]  deleteTopic @RobertIndie https://github.com/apache/pulsar/pull/14069

PersistentTopicsBase has some sync methods. Decide to make them async.
Volunteers wanted for this.

@Technoboy- @codelipenghui @merlimat Why are these changes made? The issue description doesn't describe any problem, just a decision.
Since there are a lot of these sync -> async changes, it would be good to always open a discussion on the dev-mailing list to get a consensus of the problem that is being solved. In Apache Pulsar, we make all major decisions on the mailing list.
@Technoboy- Could you start a dev-mailing list thread on the topic which describes the problem, the assumptions and the solution? /cc @mattisonchao

I didn't receive a reply to my questions. I have taken these sync->async changes to discussion on the mailing list in the 2.10.0 release thread. https://lists.apache.org/thread/ggsywqsvwpb1yw8wh490mp8mbgzgxch5 .

@codelipenghui Thank you for replying on the mailing list in thread https://lists.apache.org/thread/tn7rt59cd1k724l4ytfcmzx1w2sbtw7l . I have followed up with PR #14320 .

All the tracked methods have been resolved.


Add flag to "ng test" to specify whether or not it should build the code first

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.
ng --version outputs 3.10.10
node --version outputs v6.10.1
npm --version outputs v3.10.10
Windows 7
Repro steps.
N/A
The log given by the failure.
N/A
Desired functionality.
On our CI server we run ng build, followed by ng test. This causes the code to be built twice and significantly slows down the build plan . It would be good if ng test could be given a flag to specify whether or not the code should be built or not.
Mention any other details that might be useful.
N/A

That is unfortunately not how the build system in the CLI works. The testing pipeline and the building pipeline are different and need to support different things. It is not possible to reuse the built artifacts.

@filipesilva , please could you explain?
In a standard Javascript (non-Angular) project, I assume it's possible to run the tests with Karma without any build process necessary.
In an Angular project, surely the Typescript is compiled to Javascript, which is then run by Karma? ng build produces Javascript files - can't these be run by Karma without having to rebuild the Typescript again?

In my node typescript projects I can run npm test on the last build.  Having to rebuild every time you run tests is incredibly slow.


broken input styles

should be completely hidden, but has a black border by default
should be overlayed exactly on top of visible elements, but gets shifted by text-align: center

see discusstion in https://github.com/andreaswilli/react-verification-input/issues/77#issuecomment-1242365147

Fixed in 3.1.1


[Source] kafka events uses ce-key instead of ce-partitionkey

See: https://github.com/cloudevents/spec/blob/v1.0.1/extensions/partitioning.md#partitionkey
/cc @lionelvillard

/remove-lifecycle stale


docs(i18n-id): translate disableReferencedProjectLoad.md, disableSizeLimit.md, disableSolutionSearching.md, and several config into Indonesia

Overview
This is part of #938
Changes
Translate the following files

[x] disableReferencedProjectLoad.md
[x] disableSizeLimit.md
[x] disableSolutionSearching.md

@R1dwanMaulana Hi! Looks like we have and issue with CODEOWNERS file. I was accidentally assigned to code-review Indonesian version. Opened a PR with a fix: https://github.com/microsoft/TypeScript-Website/pull/1161
@jefrydco @nusendra @mazipan @mandaputtra FYI

@R1dwanMaulana you can create pull request again after the fix get merged, for now just wait or you can open this pull request again we will check and @AMashoshyna will help us merge this translation. Thanks.
IMO better wait till fix get merged.

ok

still in trouble?

Yep, PR still open. But I can approve the PR with "LGTM", as @mandaputtra suggested

Omg, I'm sorry. I did not mean to actually merge the PR. Soo sorry.
FYI @jefrydco @nusendra @mazipan @mandaputtra

No problem @AMashoshyna  :ok_hand: I will fix it later. I guess the bot need some improvement :laughing:

need bot repair 😅

ha - looks like we didn't add the prefixes paths here - https://github.com/microsoft/TypeScript-Website/blob/23d08a49a912f1fdb7628a907c7c8941a02fe584/.github/CODEOWNERS#L46-L50

@orta Yup, this is the fix for that https://github.com/microsoft/TypeScript-Website/pull/1161


Cleanup unused node metadata

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
c2dd7045770045a888eefc92c7ef3f6e66bc0e97
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Clarify and distinguish errors around missing/unresponsive targets

Closes #78

I'll likely want to see the impact on PB before merging this. I published a pre-release and I'll test it out tomorrow-ish.
I'm trying to make sense of the errors that the messaging API and the Messenger throw. There are so many variations based on whether a target exists, any target exists, the type of the target, the sender’s context, etc. 🙈  plus our own additional logic, forwarding, named targets, etc.🙉
Hopefully with these messages we get a better idea of what's happening and stop surfacing low-level errors like "Could not establish connection"

Thank god for the testing suite. This couldn't be possible without the (semi-)automated tests.


hipRAND is missing from the repo manifest file

There is no entry for hipRAND in the default.xml repo manifest file: https://github.com/RadeonOpenCompute/ROCm/blob/roc-5.7.x/default.xml
This makes it unnecessarily difficult to build a complete set of ROCm components.

rocRAND contains a submodule for hipRAND in 5.7.1. Please see https://github.com/ROCmSoftwarePlatform/rocRAND/tree/rocm-5.7.1. hipRAND code was historically included in the rocRAND repo. The slow separate of the code bases is nearly complete. ROCm 6.0 will contain hipRAND in the manifest.

Hi @BenWibking, please close the ticket if your issue has been fixed in ROCm6.0.0.  Thanks.


[Feature] Ray Serve CR and Controller

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
We would like to contribute a controller embedded in kuberay the operate a Ray Serve application on top of kuberay cluster.
apiVersion: serve.ray.io/v1
kind: ServingCluster
metadata:
  name: .
  # status is populated by the operator, user can `kubectl get serve_deployments name | jq .medata.status` to receive the field.
  status: UPDATING|HEALTHY|UNHEALTHY
spec:
  healthCheckConfig:  # optional
    health_period_s: 5s
    consecutive_failures_threshold: 3

  serveConfig:
    - deploymentClass: .
      numReplicas: 2
      rayActorOptions: .

  rayClusterConfig:
    apiVersion: cluster.ray.io/v1
    kind: RayCluster
    metadata:
      generatedName: .
    spec:
      maxWorkers: 2
      podTypes:
        - name: head
          rayResources: .
          podConfig:
            apiVersion: 1
            kind: Pod
            metadata:
              generatedName: .
            spec:
              containers:
                - name: ray-node
                  image: my_registry/container:v1

This operator performs health checks, initial and redeployment of Serve app on kuberay cluster, and rotate cluster if the Serve application fails. The CR will exposes health checking status of Serve application.
You can find more information from this design doc
Conceptually this is similar to SparkJob and FlinkJob in their respective operator. It is a high level concept built on top of existing CRs.
Comparing to the Ray Jobs controller/CR design, service CR is designed to be long running and should outlive cluster failure. However, both workload uses Ray's REST API endpoint to perform operation on the Ray cluster.
Use case

Deploy Ray Serve application reliability on K8s cluster.
Manage Serve application in a cloud native way
Entrypoint to highly available application on Ray

Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Hi. We have finalized some discuss about the design of the new k8s operator for Serve Deployment and RayCluster management. Here is our design doc. We would like to hear the feedbacks from the committee to make the alignment.
Also @simon-mo .
One example thing we want to discuss is how to add this new operator, how should the repo package structure look like.

This has been done.


feature/Fogotpassword/CLK32 956-Fogotpassword-Implement-API

Prerequisite

[x] Self-review :monocle_face:
[x] No Crashes ☠

Root cause

Fogotpassword

Solution

update integrate forgotpassword

Impact
-Fogotpassword

[ ] I understand that "ForgotPass.TitleMail" is now existed in Localized service

  Generated by :no_entry_sign: Danger


docs(AjaxObservable): fix esdoc generation

Description:
Fix esdoc generation for AjaxResponse and AjaxError:

Due to doc generation process member info provided not in
constructor is missed.
esdoc does not recognize desciption provided as a param for type
annotation.

Add documentation for constructor parameters.
Related issue (if exists):
N/A

Coverage remained the same at 97.078% when pulling 319284bf8aff02682871c611f44f05005c7dbcd3 on grumblerchester:doc-for-AjaxResponse into cd9626a4f93cac6f631d5a97dd9c9b2aa8e4b5db on ReactiveX:master.

this has a lot of conflicts since the type was refactored. We don't really want people using the ctor directly anymore, so the documentation here isn't really necessary. Thank you for your thoughful contribution and your time, sorry I didn't work out this time. Hopefully you continue to contribute!