Fixing issue 2223

Updated tests to match desired sql syntax for preceding and following
Updated WindowRows to produce the proper syntax for preceding and
following
NOTE: I looked up several documents on the expected sql syntax for preceding and following, and all of them had the integers prior to the keyword.
Here is an example: https://www.sqlite.org/windowfunctions.html

This is for issue: https://github.com/querydsl/querydsl/issues/2223

Doesn't this just break it for other dialects?
It seems a rather strange "fix".

@jwgmeligmeyling I'm new to this code base, so any feedback would be appreciated.
I did do a search for what the accepted syntax is, and didn't find any that were the other way around. Also, I couldn't find where either the tests or the windowsrows class had support for different behavior for different dialects.
If you could provide additional guidance on how to handle supporting multiple dialects (perhaps point me to another area of the codebase that has the existing pattern), and I'll look into it.

@jwgmeligmeyling I've  been looking through the code and trying to figure out how to templatize the changes.
This is what I've done so far, but it isn't entirely working yet.
https://github.com/allanhaywood/querydsl/tree/2223_WIP
For the WindowFunctionTest, the all test passes, it uses the SQLExpressions directly)
For the tests that use WIndowsRows, those are failing for unknown operation.
Any guidance would be appreciated.
Thanks!


FlipTheView just one time

hi, how can i use flipTheView to flip just one time ?

Well, there's no support for that yet. But its a great idea. I will add it in the next update. For now, you can do it by adding any counter variable and manually flipping the view based on the condition and value of the counter.

I am working on this.
Will update when I get it going.

Thanks @adzo261 👍 I will be looking forward to it 😄

I have done implementing.
Check my pull request!

Thanks @adzo261 for your contributions and congratulations for the first one 😄
I am a little confused as to why the pull request #32 has been closed?

I have opened pull request #33 .

Thank you @adzo261 . Can you please add an snapshot of the the Activity you created and add that image in Art directory of the repository?

Yes, I have added a demo gif.

Thank you for considering me 👍


SSLv2 Problem

So, I go ahead and attempt to download a playlist:

metalhead33@localhost ~/haguichi $ youtube-dl -citk --max-quality FORMAT --extract-audio --audio-format mp3 https://www.youtube.com/playlist?list=PLX5XLCxTj60mLQ9PqTiwq5PnzP7mZYwun

And the result is:
Traceback (most recent call last):
  File "/usr/bin/youtube-dl", line 3, in <module>
    import youtube_dl
  File "/usr/lib64/python2.7/site-packages/youtube_dl/__init__.py", line 15, in <module>
    from .options import (
  File "/usr/lib64/python2.7/site-packages/youtube_dl/options.py", line 7, in <module>
    from .downloader.external import list_external_downloaders
  File "/usr/lib64/python2.7/site-packages/youtube_dl/downloader/__init__.py", line 3, in <module>
    from .common import FileDownloader
  File "/usr/lib64/python2.7/site-packages/youtube_dl/downloader/common.py", line 8, in <module>
    from ..utils import (
  File "/usr/lib64/python2.7/site-packages/youtube_dl/utils.py", line 27, in <module>
    import ssl
  File "/usr/lib64/python2.7/ssl.py", line 97, in <module>
    import _ssl             # if we can't import it, let the error propagate
ImportError: /usr/lib64/python2.7/lib-dynload/_ssl.so: undefined symbol: SSLv2_method

My platform is:
Gentoo Linux X64, Kernel 4.4.3.  I have openssl 0.9.8z_p8, pyopenssl 0.15.1-r1, Python 2.7.9-r2, 3.3.5-r1 and 3.4.3

Can you run the following command without errors?
python2.7 -c "import _ssl; print(_ssl)"

If not, there's something wrong in your Python build. Try to uninstall openssl and Python and rebuild them.
pyopenssl is not used in youtube-dl, so it should be irrelevant.

No, I can't.

metalhead33@localhost ~/haguichi $ python2.7 -c "import _ssl; print(_ssl)"

Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: /usr/lib64/python2.7/lib-dynload/_ssl.so: undefined symbol: SSLv2_method

I will try reinstalling Python and OpenSSL then.

I re-emerged both Python and OpenSSL. Yay, it works completely perfectly now! Thanks!


Show only starred talks on event schedule page

This PR adds the ability to show only starred talks. If there are no starred talks in a certain time slot, that time is no longer shown.
You can switch between list/grid and starred/unstarred without losing your selection. We don't currently set a cookie for starred/unstarred like we do for layout, but could do if required. Personally, I think seeing all talks at once is more useful.
I've attached screenshots of how this looks. This is my first contribution in a long time so please do review closely and let me know if there are any changes to be made.
List view

Grid view

Thanks for the PR Michael.
I haven’t fully reviewed the code yet, but am unsure of the functionality.  If it does not display any talks for a time slot that does not have a starred talk, then how are you to see the talks in that slot to be able to star them?
Maybe I’m thinking about this wrong but that seems like a pretty big issue to me.
Thanks again,
Mark
Sent from my iPhone

On 3 Oct 2017, at 21:10, Michael Heap<EMAIL_ADDRESS>wrote:
This PR adds the ability to show only starred talks. If there are no starred talks in a certain time slot, that time is no longer shown.
You can switch between list/grid and starred/unstarred without losing your selection. We don't currently set a cookie for starred/unstarred like we do for layout, but could do if required. Personally, I think seeing all talks at once is more useful.
I've attached screenshots of how this looks. This is my first contribution in a long time so please do review closely and let me know if there are any changes to be made.
List view
Grid view
You can view, comment on, or merge this pull request online at:
https://github.com/joindin/joindin-web2/pull/418
Commit Summary
Show only starred talks on event schedule page
File Changes
M app/src/Event/EventController.php (22)
M app/templates/Event/schedule-grid.html.twig (30)
M app/templates/Event/schedule-list.html.twig (14)
Patch Links:
https://github.com/joindin/joindin-web2/pull/418.patch
https://github.com/joindin/joindin-web2/pull/418.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry, I wasn’t clear with my explanation. By default all sessions are shown. The behaviour
I described occurs when you select “Starred only” (see links on screenshot)

On 3 Oct 2017, at 22:25, Mark Railton<EMAIL_ADDRESS>wrote:
Thanks for the PR Michael.
I haven’t fully reviewed the code yet, but am unsure of the functionality. If it does not display any talks for a time slot that does not have a starred talk, then how are you to see the talks in that slot to be able to star them?
Maybe I’m thinking about this wrong but that seems like a pretty big issue to me.
Thanks again,
Mark
Sent from my iPhone

On 3 Oct 2017, at 21:10, Michael Heap<EMAIL_ADDRESS>wrote:
This PR adds the ability to show only starred talks. If there are no starred talks in a certain time slot, that time is no longer shown.
You can switch between list/grid and starred/unstarred without losing your selection. We don't currently set a cookie for starred/unstarred like we do for layout, but could do if required. Personally, I think seeing all talks at once is more useful.
I've attached screenshots of how this looks. This is my first contribution in a long time so please do review closely and let me know if there are any changes to be made.
List view
Grid view
You can view, comment on, or merge this pull request online at:
https://github.com/joindin/joindin-web2/pull/418
Commit Summary
Show only starred talks on event schedule page
File Changes
M app/src/Event/EventController.php (22)
M app/templates/Event/schedule-grid.html.twig (30)
M app/templates/Event/schedule-list.html.twig (14)
Patch Links:
https://github.com/joindin/joindin-web2/pull/418.patch
https://github.com/joindin/joindin-web2/pull/418.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for the PR @mheap  - this is a feature I've wanted for ages :D
One thing I have noticed - from the 'base' event URL - e.g. http://dev.joind.in/event/php-meetup you see the schedule tab by default, which means you can still click on the 'Starred Only' button, however that then produces a URL such as http://dev.joind.in/event/php-meetup/starred which results in a 404.
Suggest that you check the currently URL, and if it's the base URL for the event you force the 'Starred Only' button to go to /schedule/list/starred ?
Thanks!

@liam-wiltshire All done! I've checked if the URL ends in /schedule/list or /schedule/grid and behave accordingly.
Though this fixes the issue, I'm not sure it's the correct fix. The event default page calls the correct action (https://github.com/joindin/joindin-web2/blob/master/app/src/Event/EventController.php#L178-L198), where as the schedule default page redirects (https://github.com/joindin/joindin-web2/blob/master/app/src/Event/EventController.php#L308-L319).
Whilst I'm happy for this to be merged as-is, it may be worth revisiting the delegation/redirection inconsistency and deciding which behaviour is preferable.


Testing Flows for Outbound Provisioning in IS 7.0

Is your suggestion a test requirement/change or improvements of the test framework? Please describe.
This task is aimed at thoroughly testing the outbound provisioning flows from IS 7.0 , Beta4 based to trusted identity providers. The flows to be tested include provisioning to Google, Salesforce, SCIM, role-based provisioning, and rule-based provisioning.
Steps to Reproduce:

[x] #18846

Verify that user data is correctly provisioned from WSO2 Identity Server to a target system supporting SCIM.
Check for any errors or inconsistencies in the provisioned data.

[ ] Salesforce Outbound Provisioning:

Confirm that user data is accurately provisioned from WSO2 Identity Server to Salesforce.
Ensure that Salesforce receives the necessary information without any data loss.

[ ] Google Outbound Provisioning:

Validate the outbound provisioning process to Google, ensuring accurate user data transmission.
Check if Google receives the correct information from WSO2 Identity Server.
Waiting for gsuite Test Account - "Requesting a google cloud account for IS Onprem Testing"

[ ] Role-Based Provisioning:

Test the provisioning of user data based on assigned roles in WSO2 Identity Server.
Confirm that users are provisioned according to their roles with no discrepancies.

[ ] Rule-Based Provisioning:

Verify the dynamic provisioning decisions based on specified rules.
Ensure that rule-based provisioning works as expected, adapting to defined conditions.
Expected Results:
All outbound provisioning flows should execute without errors.
User data should be accurately and securely transmitted to the respective identity providers.
Role-based and rule-based provisioning should follow the specified criteria.
Additional Information:
Reference the documentation for outbound provisioning in WSO2 Identity Server for further details. - https://is.docs.wso2.com/en/latest/guides/identity-lifecycles/outbound-provisioning/

Outbound provisioning - SCIM is blocked https://github.com/wso2/product-is/issues/18840

Outbound Provisioning Google - Blocked due to https://github.com/wso2/product-is/issues/18856


VALID_CONNECTION_PROVIDERTYPE to list and added GH and GH Enterprise

As per Amazon's documentation the following provider types are allowed:

Bitbucket
GitHub
GitHubEnterpriseServer

Thanks!


Allow Symfony 4

@nicolas-grekas added support for Symfony 4.0, but only on the master branch, which is yet to be released. As Symfony 4 will start to be in beta really soon now (next week), having support for it in Doctrine 2.5 is critical.
I know that's a lot to ask, but is it possible to merge this PR and release 2.5.12?
Thank you a lot for your help on this one.

Besides not being able to actively work on OSS for a few weeks at the
moment, you know the drill: new things for new minor releases.
On 28 Sep 2017 00:34, "Fabien Potencier"<EMAIL_ADDRESS>wrote:

@nicolas-grekas https://github.com/nicolas-grekas added support for
Symfony 4.0, but only on the master branch, which is yet to be released. As
Symfony 4 will start to be in beta really soon now (next week), having
support for it in Doctrine 2.5 is critical.
I know that's a lot to ask, but is it possible to merge this PR and
release 2.5.12?
Thank you a lot for your help on this one.
You can view, comment on, or merge this pull request online at:
https://github.com/doctrine/doctrine2/pull/6733
Commit Summary

Allow Symfony 4

File Changes

M composer.json
https://github.com/doctrine/doctrine2/pull/6733/files#diff-0 (4)

Patch Links:

https://github.com/doctrine/doctrine2/pull/6733.patch
https://github.com/doctrine/doctrine2/pull/6733.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/pull/6733, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakKzKObQh6tnWgdXl658AWQpXunxfks5sms1fgaJpZM4PmfPe
.

Is it really a new feature? Any ETA for the next Doctrine version? Not merging this pull request means no Doctrine for Symfony 4. Anybody else able to work with us on this issue before you have time?

Note that the only change is about the console component, nothing core to Doctrine.

I might be able to do the release on Sunday, since I'm commuting ~10h via :train:.
It must be clear that ORM 2.5 will not have this addition though, sorry.

@fabpot When are you planning to release Symfony 4.0?

I believe this weekend or very early next week. Feature freeze is technically Saturday.

@Ocramius why can we not include this in a 2.5.x release? I am :+1: unless I hear a compelling reason not to. /cc @beberlei

@jwage the scenario is quite simple, and it is the reason for never updating dependencies in patch releases:

somebody requires "doctrine/orm": "2.5.*"
that somebody uses Symfony\Component\* in their codebase, has no direct dependency to it though (their mistake, but that's how it is)
run composer update and things break

I'm fine with bumping in a minor release, not in a patch release, since any environment must always be able to upgrade patch releases at any time due to possible security releases.

@Ocramius

that somebody uses Symfony\Component\* in their codebase, has no direct dependency to it though (their mistake, but that's how it is)

That would most likely blow up in their face regardless of a patch or minor release: The current version constraint for doctrine/orm in the Symfony Standard Edition is ^2.5 and it has been that (or ~2.5, which is equivalent) since Symfony 2.3.something. Thus, once we release ORM 2.6 with such a change it would blow up anyways.
TBH, I wouldn't consider that a problem: if you use something through an implicit dependency you shouldn't be surprised if that implicit dependency is no longer filled. Also, since we'd add |~4.0 to the Symfony constraints, any package with a hard requirement on a specific Symfony version would still continue to work. All in all, it's ok merging this into 2.5, not only 2.6.

@alcaeus I'm fine with changing this decision if there's enough consensus and this kind of crash is just removed from the BC compliance issues on our side: just need to make that very clear.
Just to add to https://github.com/doctrine/doctrine2/pull/6733#issuecomment-333460708, the removal of supported dependency versions should absolutely never happen (unrelated to this issue). The addition of a range is still a risk, IMO.

I agree on the BC compliance issue, but then I'd always put blame on the user if an implicit dependency blows up in their face.

I'd always put blame on the user if an implicit dependency blows up in their face

I'm fine with this stance. If nobody has an issue with it, then we can backport to 2.5 too.

:+1: Sounds good. Thanks!

I'm fine with this stance. If nobody has an issue with it, then we can backport to 2.5 too.

Looks reasonable.
Currently trying to install Doctrine or any package depending of Doctrien with Symfony 4 (already in beta) get the following error:
  Problem 1
    - doctrine/orm v2.5.9 requires symfony/console ~2.5|~3.0 -> satisfiable by symfony/console[2.5.x-dev, 2.6.x-dev, 2.7.x-dev, 2.8.x-dev, 3.0.x-dev, 3.1.x-dev, 3.2.x-dev, 3.3.x-dev, 3.4.x-dev, v2.5.0, v2.5.0-BETA1, v2.5.0-BETA2, v2.5.0-RC1, v2.5.1, v2.5.10, v2.5.11, v2.5.12, v2.5.2, v2.5.3, v2.5.4, v2.5.5, v2.5.6, v2.5.7, v2.5.8, v2.5.9, v2.6.0, v2.6.0-BETA1, v2.6.0-BETA2, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.0-BETA1, v2.7.0-BETA2, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.3, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.0-BETA1, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.0-BETA1, v3.1.0-RC1, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.0-BETA1, v3.2.0-RC1, v3.2.0-RC2, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.0-BETA1, v3.3.0-RC1, v3.3.1, v3.3.10, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0-BETA1] but these conflict with your requirements or minimum-stability.

Not really a good user experience.

+1 for backporting to 2.5 if possible, especially as I'm not sure when 2.6 would be landing.

👍 Backporting to 2.5 would be great. Thanks!

:+1: for backporting to 2.5

Cool, I can confirm it works now with Symfony 4. There is still an issue with the integration bundle and Symfony 3.4, but it is just pending on a new release.
Issue here: https://github.com/doctrine/DoctrineBundle/issues/720


add YDL-UI v2.5.1

another youtube-dl GUI

sorry for this mess... not really familiar with github and forgot the checkver part.


SQL: Add support for star wildcard

Adding support for star wildcard.

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

@dprokop seems like you need to sign the CLA too now that you have committed to this branch. :)


Use Better Card Identification

MTGJSON may not update the multiverseid field for cards, but the uuid field seems to always exist.  Try several methods of identifying a card:

uuid
multiverseid
Name + Expansion

This may cause items that aren't real cards, like tokens to appear in the inventory.  This can be solved by removing non-card layouts and skipping items that aren't cards (or adding them and giving them a flag saying they aren't real cards).

This doesn't seem to be necessary anymore.  It can be reopened later if it becomes a problem again.


82 Refactor DataGettingWrapper & ApiWrapper

I would change the names from "initial" to "lastUsed" after merging the branches so we wont run into problems druing the merge.

You could already do that since we will have merge conflicts that we need to manually edit anyways, since two parties might change names in the same method for different reasons


Registrar.activity() is null

A fluent project imported using module
Other plug-ins have been imported into the fluent project
Now I'm reporting an error
otherPlugin include is flutter project >> pubspec.yaml
in OtherPlugin code
OtherPlugin(Registrar r){
Activity activity = r. activity() / / but activity  is null
}
//-------------------------------
evaluate(new File(
settingsDir,
'../flutter/job/.android/include_flutter.groovy'  /
))
implementation project(":flutter")

@bxxasn
Can you provide flutter doctor -v and sample repo or minimal reproducible code sample that we can directly run to verify this issue ?

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Is the developer mode of the kiwibrowser extension not working?

Tampermonkey needs to turn on developer mode to run scripts, but it doesn't work after turning it on in the extension, and the scripts in Tampermonkey have no effect

The problem happened to me, too

I also noticed this. Any way to solve this?

I also noticed this. Any way to solve this?

Change script cat

I'm having this problem as well

I don't have such problem with Violentmonkey.

Yes, it worked. Thanks a lot

Caused by or duplicate of #1135.


Add support for mixtral 8x7b or more generic support for MoE models.

I don't know if this is possible, but I'll just create this for the future :)

There's a discussion in #357. It depends on llama.cpp implementation and we'll support it once llama.cpp supports it.

Relevant upstream issues:

https://github.com/ggerganov/llama.cpp/pull/4406
https://github.com/ggerganov/llama.cpp/pull/4428

I saw that the llama libraries were updated in the llamasharp repo and tried it.
Loading the weights took over a minute and 42 GB out of 128GB memory, 80% CPU, 28% GPU and then threw a native load failed exception.
Regards,
Ash

Could you link the GGUF file you were trying to use, I'll see if I can reproduce the problem.

Thanks @martindevans
GGUF file - https://huggingface.co/TheBloke/Mixtral-8x7B-Instruct-v0.1-GGUF/resolve/main/mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf
These are my parameters
var p = new ModelParams(modelPath) { ContextSize = 4096, GpuLayerCount = 12,UseMemoryLock = true, UseMemorymap = true, Threads = 12,  BatchSize = 128, EmbeddingMode = true };
var w = LLamaWeights.LoadFromFile(p);

CPU - i9 13th Gen, GPU RTX 4090, 128GB
Thanks,
Ash

I'm downloading it now, but it's going to take a while!
However I've actually been testing with the Q5_K_M model from that same repo, so I'm expecting it to work.
I'd suggest trying out getting rid of all your params options there, most of them are automatically set and you shouldn't need to change them unless you have a good reason to override the defaults. The only one you do actually need to set is the GpuLayerCount, but I'd suggest setting that to zero as a test first.

Using this
var p = new ModelParams(modelPath) { GpuLayerCount = 0};
Same error. model_ptr returns IntPtr.Zero
var model_ptr = NativeApi.llama_load_model_from_file(modelPath, lparams);
Thanks,
Ash

I tested out that mode, but it seems to work perfectly for me on both CPU and GPU.
if NativeApi.llama_load_model_from_file is failing, that would normall indicate an error with the model file itself or something more fundamental. Have you tried this file with one of the llama.cpp demos?

Thanks @martindevans for your help in debugging this issue.
It works! The issue was it was picking up the llama dll from cuda11 folder and I assumed was picking it up from cuda11.7.1 folder.
I could offload 18 layers to the GPU. Token generation was around 7.5 tokens/sec.
Are you seeing similar numbers?  Is a webpage that you are aware of that has the best parameters to set based on the model?
Model output was better than the Mistral Instruct v0.2 for some of the prompts I tried.
Thanks,
Ash

I'm using CPU inference, so it's slower for me. But as a rough guide it should be around the same speed as a 13B model.

Is a webpage that you are aware of that has the best parameters to set based on the model?

Almost all of the parameters should be automatically set (they're baked into the GGUF file).
The GPU layer count I don't know much about. As I understand it you just have to experiment to see how many layers you can fit and what speedup it gets you.

Thanks @martindevans
As you said, the GPU Layer count setting is more of - try to see how many you can fit in your GPU :-)

v0.9.1 added support for Mixtral, so I'll close this issue now.


[Feature request] Ability to skip first line

Hey @jahewson,
First of all thanks for all the effort you put in this amazing module.
When processing CSV or TSV files it would be very handy to have an option to skip the first line.
E.g.
import { createReadStream } from 'fs';
import byline from 'byline';

const sourceFile = 'somefile.csv';

byline.createStream(
  createReadStream(sourceFile, {
    skipFirstLine: true
  })
);

This functionality might help to keep the user code cleaner and shorter, but I understand it's a quite specific extra feature you might not want to include and leave to the users.
If it makes sense to you to include it I can try to submit a PR as soon as I have some free time.

Hi, I don't think that byline needs to ship this functionality but thanks for the suggestion.


Errors on First-Time Run

Everything installed easily. On running my app, I get this console message:

Error: Can't find npm module 'path-to-regexp'. Did you forget to call 'Npm.depends' in package.js within the 'meteorhacks_picker' package?

I ran npm install path-to-regexp. I then started getting these console error messages:

router.js:296 There is no route for the path: /navigators?specialty=MySpecialty%20etcetera

I installed the code from the read.me section, "Example setup using FlowRouter (Meteor 1.3)", in my router. I then received this console error message:

app.js:131 Uncaught Error: Accounts.ui.config: Invalid option for passwordSignupFields: NO_PASSWORD

How can I correct this?

I wasn't doing this:
import { FlowRouter } from 'meteor/kadira:flow-router-ssr';
I already had FlowRouter imported, of course, and my eye missed the "-ssr" at the end of the import {FlowRouter}... statement in the docs.
To help keep other people who might make the same mistake I did, it might be helpful to revise the Read.Me file:


Can this be used with Core Data?

If yes, could you give an example with it?
Thanks!

Did you figure out how to implement RATreeView with CoreData?

Closing. Please enter discussion in #119 if necessary.


Autodiscovery

Added autodiscovery for service provider.
Solves https://github.com/madewithlove/elasticsearcher-laravel/issues/3

Please test it before merge

This probably needs some additional cleanup in the README

Can you first check if it has any effect?
After I changed this locally the provider wasn't discovered. It might be related to composer caching or something. I cannot spot a problem within the modification.

I’ll try it on a clean install later this week


What is the 'BioMedGPT'？

Really appreciate your work! However, I noticed two papers referenced in the documentation, one being "Empowering AI drug discovery with explicit and implicit knowledge", and the other "Large-Scale Cell Representation Learning via Divide-and-Conquer Contrastive Learning"(CellLM). Neither of these papers seem to mention BioMedGPT. Could you provide a link to the paper on BioMedGPT?

Thank you for your interest in BioMedGPT! We appreciate your attention. However, please note that we are still in the process of releasing the BioMedGPT paper. In the meantime, you can refer to the project OpenBioMed_project when citing BioMedGPT

Looking forward to your paper!!!🥺🥺🥺🥺🥺🥺


The parameters for the weather？

How were the parameters for the weather dataset set? I cannot replicate the results following the .sh file.

ps=8 your paper in arxiv v1
ps=64 your .sh file

How were the parameters for the weather dataset set? I cannot replicate the results following the .sh file.

ps=8 your paper in arxiv v1
ps=64 your .sh file

I get similar results to yours and I'm confused ....

How were the parameters for the weather dataset set? I cannot replicate the results following the .sh file.

ps=8 your paper in arxiv v1
ps=64 your .sh file

I get similar results to yours and I'm confused ....

--seq_len 336

How were the parameters for the weather dataset set? I cannot replicate the results following the .sh file.

ps=8 your paper in arxiv v1
ps=64 your .sh file

I get similar results to yours and I'm confused ....

--seq_len 336

Did you get the right result after adjusting the seq_len to 336?

How were the parameters for the weather dataset set? I cannot replicate the results following the .sh file.

ps=8 your paper in arxiv v1
ps=64 your .sh file

I get similar results to yours and I'm confused ....

--seq_len 336

Did you get the right result after adjusting the seq_len to 336?

yeap


HADOOP-18143. toString method of RpcCall throws IllegalArgumentException

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 43s

trunk passed

+1 :green_heart:
compile
23m 53s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
20m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m  8s

trunk passed

+1 :green_heart:
mvnsite
1m 40s

trunk passed

+1 :green_heart:
javadoc
1m 14s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 42s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 28s

trunk passed

+1 :green_heart:
shadedclient
22m 39s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m  0s

the patch passed

+1 :green_heart:
compile
23m  1s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
23m  1s

the patch passed

+1 :green_heart:
compile
20m 37s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
20m 37s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  4s

the patch passed

+1 :green_heart:
mvnsite
1m 39s

the patch passed

+1 :green_heart:
javadoc
1m  9s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 40s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 43s

the patch passed

+1 :green_heart:
shadedclient
22m 44s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m  6s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 55s

The patch does not generate ASF License warnings.

204m 43s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4030/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4030

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux ecc3a7dae72f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / efdfab807f4dffd48dfd1c1e4d0af5ffbdc64136

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4030/1/testReport/

Max. process+thread count
1251 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4030/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
35m 22s

trunk passed

+1 :green_heart:
compile
24m 18s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
20m 43s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 59s

trunk passed

+1 :green_heart:
mvnsite
1m 36s

trunk passed

+1 :green_heart:
javadoc
1m  7s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 41s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 34s

trunk passed

+1 :green_heart:
shadedclient
25m  5s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m  1s

the patch passed

+1 :green_heart:
compile
23m 42s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
23m 42s

the patch passed

+1 :green_heart:
compile
20m 47s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
20m 47s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 58s

the patch passed

+1 :green_heart:
mvnsite
1m 34s

the patch passed

+1 :green_heart:
javadoc
1m  4s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 36s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 38s

the patch passed

+1 :green_heart:
shadedclient
25m 11s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m  0s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 50s

The patch does not generate ASF License warnings.

211m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4030/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4030

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux d886e284ded2 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 1ecdcf0ef1cecbd5aa7c0b28cb03043edfcc5a98

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4030/2/testReport/

Max. process+thread count
2356 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4030/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


FBPP.SetString() not consistently working

This is a really weird one and there's absolutely no errors to come with it.  I want to save the level when the user hits their End Trigger, so I've put this in my OnTriggerEnter2D method
        // if the last level
        if (SceneManager.GetActiveScene().buildIndex == SceneManager.sceneCountInBuildSettings - 1)
        {
            FBPP.SetString("LastLevel", sceneName);
            FBPP.Save();
            Debug.Log("Save current scene for last level");
        }
        else // if not the last level, i.e current scene
        {
            FBPP.SetString("LastLevel", nextSceneName);
            FBPP.Save();
            Debug.Log("Save next scene for last level");
        }

Just before this runs, I'm running FBPP.SetInt("key", value) and that is working consistently across plays and builds etc.
Any idea why this wouldn't be saving?  It only seems to be with this one part as well, SetString() seems to work fine elsewhere, it's just on this one trigger.

Oh, I'm on v2.0.2 as well.

2 debugging ideas that might help
Could sceneName or nextSceneName be null?
A way to debug it would be to call FBPP.GetSaveFileAsJson(); and print that in a log, that will show the saved data and you can see if it's in there.

Also, can you post the code where you read the value? If everything else is working fine, including GetString, then that suggests an issue with your implementation, and I can't help you fix that unless you share a lot more code.

Closed due to no response or repro


does the --ddns flag exist?

As described on this page https://kube-vip.io/control-plane/,  "A new flag --ddns is introduced. Once enabled, kube-vip expects the input --address will be a FQDN etc"
Following instructions, I've tried variations of
sudo docker run --network host
--rm plndr/kube-vip:0.3.2
manifest pod
--interface ens192
--address "my-kubu-vip-addr"
--ddns "true"
--arp
--leaderElection | sudo tee /etc/kubernetes/manifests/vip.yaml
I'm in home lab environment on a <IP_ADDRESS>/16 network, my router provides leases.
Ubuntu 20.04
kubelet/kubeadm 1.20.4-00
kube-vip 0.3.2
My expectation was that a new IP would be provided by my home router DNS and get assigned to the --address FQDN, but I get
Error: unknown flag: --ddns
unknown flag: --ddns
Usage:
kube-vip manifest pod [flags]

I built the main Dockerfile from this repo but got the same with that image. Also the ran the Makefile (make all) and got a binary with the same (not so familiar with Go).  Any pointers please?

Ah! I'm a fool, it was never migrated over to the hybrid UX.. i'll raise a PR and get that fixed, and update the tests.
https://github.com/plunder-app/kube-vip/blob/afdbac7a58c9b629c80e6057a5fb4bd23d6feaa7/cmd/kube-vip-start.go#L31


Implement dead-letter queue redrive actions

First of all, thank you for this tool! :heart:
These new actions were released recently https://aws.amazon.com/about-aws/whats-new/2023/06/amazon-sqs-dead-letter-queue-redrive-aws-sdk-cli/ (StartMessageMoveTask,  ListMessageMoveTasks,  CancelMessageMoveTask)
Will these actions be added?

Thanks, we'll add this to our tasks list.

Released in v1.6.0


feat(log): add log service so you can log things to console and syslog

Log module should be used to log important things to console (using cat-log) and syslog (using ain2 module from npm).
I can probably improve it, but I think this is enough for the first iteration.
Would need to propagate this module in other modules (instead of loading cat-log everywhere, we should load Log -> Helpers, Route, Server).

Coverage increased (+0.03%) to 98.213% when pulling 2f3cd79881c946d2c3a6a9d4c536c16ff0afd4ca on goschevski:feature/log into c0fc70738dcae894819cfa996c98001cc72d8e93 on adonisjs:develop.

Coverage increased (+0.03%) to 98.213% when pulling 2f3cd79881c946d2c3a6a9d4c536c16ff0afd4ca on goschevski:feature/log into c0fc70738dcae894819cfa996c98001cc72d8e93 on adonisjs:develop.

I just saw this https://github.com/adonisjs/adonis-framework/issues/52
Anyway, I think adonis should have predefined Log component. That's something that's every node app needs to have.

@goschevski I'll keep this PR open and will clear my intentions first on what all I need from a logging component.

@thetutlage sure thing! I should have asked you guys first on gitter what do you think. :)

Maybe we should hold off this for the moment and create a discussion in the adonis-discussion repository?

Closing since AdonisJs has different plans, I will create a dicussion for same


feat(addEnvFrom): possibility to inject env variables

What
Allows users to create a configmap and directly inject env variables into the pods
Why
You may need to inject some custom defines variables such as but not limited to proxy configuration , for exemple.

Cucu Julien! Ca fait bizarre de te voir ici! 😁
Thank you for the PR, we will review it and get back to you!

J'attendais le bon moment pour faire une PR et me montrer. :pinched_fingers:

I don't feel the unit-tests are failing due to my changes.  At least i cannot find anything relevant in the logs.


Collect tld.js dependents feedback

Intent
This issues complements #124 and seeks to collect feedbacks of tld.js dependants.
Ultimately, it will help understand why they did not migrate to<EMAIL_ADDRESS>what would make them feel safe to upgrade to<EMAIL_ADDRESS>and what would be a bummer to upgrade to<EMAIL_ADDRESS>Packages to investigate

[ ] @activeprospect/freemail - version: ^1.5.2 - feedback issue - Only tldjs.getDomain is used.
[ ] @cliqz/adblocker - version: ?? - feedback issue
[ ] @helpdotcom/is - version: ?? - feedback issue
[ ] @mapbox/swot-simple - version: ^1.5.2 - feedback issue - Only tldjs.getDomain and tldjs.getDomain are used.
[ ] @passmarked/seo - version: ^2.2.0 - feedback issue - Only tldjs.getDomain is used.
[ ] @standuply/socket-tunnel - version: 2.1.X - feedback issue - Only tldjs.getSubdomain is used.
[ ] @twistly/shelf - version: ^2.0.0 - feedback issue - isValid, tldExists are used => domain validation
[ ] asset-server - version: ~1.5.2 - feedback issue - isValid, getSubdomain
[ ] awsome - version: ^2.2.0 - feedback issue - uses parse but seems to only need getDomain.
[ ] bat-ledger - version: 2.2.0 - feedback issue - getPublicSuffix, getSubdomain used.
[ ] bat-publisher - version: 2.2.0 - feedback issue - a bit of everything!
[ ] brave-browser - version: ^2.3.1 - feedback issue - isValid, getDomain
[ ] certstreamcatcher - version: ^2.2.0 - feedback issue - subdomain, publicsuffix from parse.
[ ] chrome-cookies - version: ^1.6.2 - feedback issue - getDomain
[ ] chrome-cookies-secure - version: ^1.5.1 - feedback issue - getDomain
[ ] diglet - version: ^1.7.0 - feedback issue - getDomain.
[ ] domain-info - version: ^1.6.2 - feedback issue - tldExists
[ ] freemail - version: ^1.5.2 - feedback issue - getDomain
[ ] freemail-webpack - version: ^1.5.2 - feedback issue - getDomain
[ ] gq-core - version: ^1.6.2 - feedback issue - isValid used to validate URLs.
[ ] gq-server - version: ^1.6.2 - feedback issue - isValid used to validate URLs.
[ ] halfpass - version: 1.* - feedback issue - getDomain
[ ] hubot-cloudflare-ddns - version: ^1.5.3 - feedback issue - getDomain
[ ] hwa-cli - version: ^1.6.1 - feedback issue - getDomain
[ ] jh - version: ^1.5.2 - feedback issue - getDomain and getSubdomain
[ ] koapi - version: ^2.2.0 - feedback issue - getSubdomain
[ ] nameserver - version: ^1.7.0 - feedback issue - getDomain
[ ] node-parse-url - version: ^2.2.0 - feedback issue - getDomain
[ ] node-werist - version: 2.2.0 - feedback issue - tldExists for validation
[ ] painless-crawler - version: ^1.5.3 - feedback issue - getDomain used to check if two URLs have same origin
[ ] pressless - version: ^1.7.0 - feedback issue - isValid used to validate domains
[ ] roboto - version: ~1.5.0 - feedback issue - getDomain
[ ] sdch - version: * - feedback issue - getPublicSuffix used to check if a domain is also a tld
[ ] sief - version: ~1.5.0 - feedback issue - getDomain
[ ] social-url - version: ^1.6.2 - feedback issue - getDomain and getSubDomain
[ ] spf-parse - version: ^1.7.0 - feedback issue - isValid used for domain validation
[ ] stream-sitemap-parser - version: ^2.2.0 - feedback issue - getDomain
[ ] tonel - version: ^1.6.2 - feedback issue - getSubdomain
[ ] vanitizer - version: ^2.2.0 - feedback issue - parse

@oncletom Thanks for creating the issue. I updated it with a list of extracted packages depending on tld.js. I ignored a few which did not have any repository specified on npm.

Updated the list with version of tldjs + methods used in each project.

Also found a few interesting projects using tldjs:
https://github.com/mozilla/gombot-chrome -
https://github.com/duckduckgo/privacy-grade - 2.3.1
https://github.com/duckduckgo/duckduckgo-privacy-extension - 2.2.0
https://github.com/localtunnel/server - 2.3.1 (getSubdomain)
https://github.com/ghostwords/chameleon - ~1.5.0
https://github.com/flattr/flattr-extension - ^1.6.2
https://github.com/brave/browser-laptop/ - ^2.3.1
https://github.com/herber/cargo - ^2.2.0


ZCAM results are slightly different from the paper

The results of our ZCAM implementation are slightly different from the official ZCAM examples in the supplementary document. For example, the paper provides the following values for Example 1 (chromatically adapted to D65 using Luxpy's implementation of CAT02, because we don't support chromatic adaptation yet):
hz = 196.3524
Qz = 321.3464
Jz = 92.2520
Mz = 10.5252
Cz = 3.0216
Sz = 19.1314
Vz = 34.7022
Kz = 25.2994
Wz = 91.6837

Our results:
hz =<PHONE_NUMBER>9109085
Qz =<PHONE_NUMBER>522057
Jz = 92.25198613424337
Mz = 10.519364954372517
Cz = 3.0198964626876563
Sz = 19.12610852817541
Vz = 34.70166837393559
Kz = 25.88274309285123
Wz = 91.68426229915165

I've reached out to the authors for clarification, but I haven't gotten an answer for the discrepancies and it appears that they're not willing to provide source code for the reference implementation.
This is probably related to D65 adaptation because the example inputs are not relative to D65. As such, it's unlikely to affect our primary use case where all colors come from sRGB and thus do not need adaptation, but it's still worth investigating.
Adapted XYZ values for Example 1 (colorio, ASTM D65, CAT02, average surround, La = 264):<PHONE_NUMBER>6,<PHONE_NUMBER>9,<PHONE_NUMBER>3

This is the same issue as https://github.com/ksmet1977/luxpy/issues/17, but that doesn't seem to have been fixed.

By adapting the sample inputs with CAT02 parameters that match the example viewing conditions and leaving the reference white unadapted, our results are now much closer to the examples, but still not exactly the same.


Allow use of --vscode-XXX color variables in <span> style in Markdown

This code permits hex colors to be specified in styling of <span> tags in Markdown where HTML is permitted:
https://github.com/microsoft/vscode/blob/83f1dc99ede69bf863c3f0a6bab951b0007d50e2/src/vs/base/browser/markdownRenderer.ts#L361-L364
I would like the constraint relaxed slightly so I can use color variables, for example:
<span style='color:var(--vscode-charts-green);'>

This should give me a green (say) that displays well regardless of what color theme the user has picked.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


added password reset feature through otp verification

Related Issue
added password reset feature through otp verification
Closes: #286
Describe the changes you've made
Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Mention any unusual behaviour of your code (Write NA if not)
Any unusual behaviour of your code
Additional Info (optional)
Any additional information you want to give
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly whereever it was hard to understand.
[x] My changes generate no new warnings.
[ ] Any dependent changes have been merged and published in downstream modules.

https://user-images.githubusercontent.com/55352601/119663748-44734c00-be50-11eb-9e5f-35891ec0fdd8.mp4

@adarshvulli @ankitapuri i had implemented the password reset feature through otp verification .
please review this PR carefully .

As soon this approved i will add some more error success msg. and will take care of some exceptions
like user can't go otp page without entering email
like user cant go to reset password page 'with out entering otp etc etc
Its not possible to add all these things in one PR it takes a lots of testing

hey @arpit456jain, i see this issue during the sign up
 rest all are fine, and if there is a possibility, we can even include the error 404 pages in some wrong routings along with the bootstrap alerts

hey @arpit456jain, i see this issue during the sign up
 rest all are fine, and if there is a possibility, we can even include the error 404 pages in some wrong routings along with the bootstrap alerts

@adarshvulli don't worry about wrong routing i will handle every possible case in next PR . but i can't add 404 page since it wil work only when debug is false and if debug is false locally all css will be removed . that's why its not good to do

and @adarshvulli i think i solved that bug in sign up will make PR for that very soon as this PR got merged

and @adarshvulli i think i solved that bug in sign up will make PR for that very soon as this PR got merged

ohh okay then I will approve this!

@adarshvulli should i make PR for that bug first or complete the otp verification process

@adarshvulli i will commit change in next PR


[Snyk] Upgrade sass from 1.70.0 to 1.71.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade sass from 1.70.0 to 1.71.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2024-02-16.

Release notes

Package name: sass

1.71.0 - 2024-02-16To install Sass 1.71.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
For more information about pkg: importers, see the announcement on the Sass blog.
Command-Line Interface

Add a --pkg-importer flag to enable built-in pkg: importers. Currently this only supports the Node.js package resolution algorithm, via --pkg-importer=node. For example, @ use "pkg:bootstrap" will load node_modules/bootstrap/scss/bootstrap.scss.

JavaScript API

Add a NodePackageImporter importer that can be passed to the importers option. This loads files using the pkg: URL scheme according to the Node.js package resolution algorithm. For example, @ use "pkg:bootstrap" will load node_modules/bootstrap/scss/bootstrap.scss. The constructor takes a single optional argument, which indicates the base directory to use when locating node_modules directories. It defaults to path.dirname(require.main.filename).

Dart API

Add a NodePackageImporter importer that can be passed to the importers option. This loads files using the pkg: URL scheme according to the Node.js package resolution algorithm. For example, @ use "pkg:bootstrap" will load node_modules/bootstrap/scss/bootstrap.scss. The constructor takes a single argument, which indicates the base directory to use when locating node_modules directories.

See the full changelog for changes in earlier releases.

1.70.0 - 2024-01-18To install Sass 1.70.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
JavaScript API

Add a sass.initCompiler() function that returns a sass.Compiler object which supports compile() and compileString() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.Compiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

Add a sass.initAsyncCompiler() function that returns a sass.AsyncCompiler object which supports compileAsync() and compileStringAsync() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.AsynCompiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

Embedded Sass

Support the CompileRequest.silent field. This allows compilations with no logging to avoid unnecessary request/response cycles.

The Dart Sass embedded compiler now reports its name as "dart-sass" rather than "Dart Sass", to match the JS API's info field.

See the full changelog for changes in earlier releases.

    from sass GitHub release notes

Commit messages

Package name: sass

3e6721e Fix new static warnings with Dart 3.3 (#2173)
2cab33e Update the language revision in Homebrew on release (#2171)
84ededd Use musl support in cli_pkg (#2172)
00571ec Add a `--pkg-importer` flag (#2169)
84f31f0 Update pubspec/changelog for `pkg:` importers (#2168)
9ee5408 [Package Importer] Dart Implementation (#2130)
9423aa5 Use macos-14 runner instead of macos-latest-xlarge runner (#2167)
bbf97b4 Remove the sass dependency from package.json (#2162)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

duplicate #197 #201 and merged #204


Fix: "docker compose up: issue because of canvas package solved

PR Fixes:

1 docker compose up command was giving an error

Resolve:
The issue was because of canvas package, it internally used some packages which wasn't correctly installed in docker. I have made changes in the Dockerfile and have added those, now it works prefectly. The minor change in the CourseCard is coz Button and ChevronRight wasn't imported in the file, have commented it for the time being.
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure there is no similar/duplicate pull request regarding same issue

we've gotten rid of the canvas library altogether now


snzip: new package added

snzip is a compression/decompression tool based on Google's snappy library.

Added in 6c49bba362cd3a86fc5478340a52992747a5cc41 without patch and with fixed dependencies.


Make Zendesk ticket tagging compulsory in Zendesk

What
Make ticket tagging within each Zendesk ticket compulsory for the person who is on support
Why
Currently the PA
Who needs to work on this
PA, DM
Who needs to review this
Someone on support rota to check it works in practice, PA
Done when

[ ] List of taxonomy is agreed on
[ ] We've asked for this to be done by David Williams
[ ] It has been put live

This is now live - taxonomy of ticket tags can be found here: https://docs.google.com/spreadsheets/d/1SjvBSf15RR6J3dRD-1JQuiDoOOHjSjDl_MXtmcyKmV4/edit#gid=1549450134


Custom environment DNS Suffix does not seem to work with internal vNet

This issue is a: (mark with an x)

[X] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
I have created a Container App Environment with the Consumption + Dedicated plan i West Europe, and followed the documentation here: https://learn.microsoft.com/en-us/azure/container-apps/environment-custom-dns-suffix on how to add Custom DNS Suffix.
I added the DNS entry both on the External and Internal DNS in Azure. and added a LetsEncrypt certificate with wildcard for this DNS Suffix, and added.
I do not get any errors when it is added, but I do see a success message. But the issue is, when I try to contact the DNS address internally, it resolves correctly, but the Apps cannot be contacted on the new DNS suffix. And I do not see anywhere that the Container Apps has added the DNS suffix either.
Steps to reproduce

Create a vNet with Hub-Spoke style and DNS Server in Hub (Azure ADDS)
Create a Container Apps Environment in West Europe with Consumption + Dedicated plan, with Internal only traffic on vNet
Create a Container Apps with ingress from vNet
Add Custom DNS Suffix and Valid certificate

Expected behavior
I expect that I will be able to connect to Apps using .
Actual behavior
I do not get a response from App with custom DNS Suffix, but I do get response if I enter the generated DNS suffix
Additional context
I have deployed via portal and Bicep but get the same issue. I have only tested in West Europe, not tested in any other region

@mortenf1984 can you email details of your environment name to acasupport[at]microsoft[dot]com, so we can follow-up and investigate?

I have sent a mail to the supplied E-Mail. If there is anything else that is needed, let me know.

can this be done via terraform?

We have exactly the same issue. Let's encrypt wildcard certificate and custom suffix set up, no app reachable.
@mortenf1984 I am not sure what do you mean by "the certificate needs both *."prefix" and *.internal."prefix" in it to work internally and externally". Do I miss some info that you received from microsoft by email?
@cachai2 what is the point of having github issue but using email to solve it.

The custom domain suffix itself doesn't have an external or internal concept. Let's say your custom domain suffix is *.foobar.com. You need to configure the custom domain ARecord to the Environment inbound IP address, in the internal environment, it is the internal load balance inbound IP address.
The DNS can be public DNS (although not recommended for internal environments) or private DNS. As long as the client are in the VNet who can access the ILB inbound IP and the DNS can be resolved correctly, it should work fine.
For troubleshooting, please try to do the "nslookup app.foobar.com" from your client and see if the DNS can be resolve correctly.

can this be done via terraform?

as of today. It seems that it's still not available (maybe after the preview)


Integrating hourly forecast into home assistant

Hello,
@bieniu I was not sure how to reach you so I've created this issue.
I see that this project has the ability to fetch hourly forecast from Accuweather API.
However the hourly forecast is not present in the home assistant integration: https://github.com/home-assistant/core/tree/dev/homeassistant/components/accuweather (you are also the author of this integration)
I thought that I could tackle adding hourly forecast into /homeassistant/components/accuweather . Are there any obstacles for this that I should be aware of? It seems to be quite easy and I can prepare a PR for this. However maybe there are some problems and you have intentionally avoided adding hourly forecast into /homeassistant/components/accuweather .
Please let me know :)
Marek

We can only make 50 requests to AccuWeather API per day. Currently the integration uses 36 requests per day for current weather conditions (updated every 40 minutes) and 4 requests for daily forecast (updated every 6 hours). The remaining 10 requests are needed in case of Home Assistant restarts (every restart needs 2 requests).
Adding hourly forecast updated every 6 hours will reduce the number of possible HA restarts or reduce the frequency of fetching daily forecast data and current conditions. IMO both options are bad. This is the main blocker in this case :) If you have an idea how to solve it, there are no other contraindications to implement hourly forecast.

Ok, I see :)
Hmm and what about allowing a second, optional api key for hourly forecast in the home assistant integration configuration. If somebody will provide it, than we can fetch hourly forecast every 40 min. using this second optional API key 😎 .
I need to have a reliable weather forecast that allows me to manage charging and discharging battery of my hybrid inverter. It's not doable without hourly forecast.
Maybe you know about other hourly forecast HA integrations that are reliable for Poland. I thought about implementing HA component for https://www.pogodairadar.pl/ (web scraping as they have no API) - as it is the most accurate from my perspective.
But it seems that Accuweather is also quite solid ... hence the need for hourly weather forecast ☀

what about allowing a second, optional api key for hourly forecast in the home assistant integration configuration

This would be a violation of AccuWeather's terms of use, so we can't do it in the official integration... but it is doable if you turn it into a custom integration.

I've prepared a custom integration by modifying your code: https://github.com/rotgier/home-assistant-accuweather/pull/1/files
Could you take a look at this PR and provide your feedback?
I was not sure if I need a separate websession for AccuWeatherHourlyForecastDataUpdateCoordinator (probably not).
Also I've noticed that when I try to fetch more than 12 hours of hourly forecast then I get an API error. Is this expected from your experience?
Otherwise, it seems to be working just fine 😎

Also I've noticed that when I try to fetch more than 12 hours of hourly forecast then I get an API error. Is this expected from your experience?

For free API keys only 12h forecast is available

I was not sure if I need a separate websession for AccuWeatherHourlyForecastDataUpdateCoordinator (probably not).

No

Thanks! :)

The PR is ready steady: https://github.com/rotgier/home-assistant-accuweather/pull/1/commits
Let me know if there are no issues and I can merge it.
I would like to prepare a similar integration with (wetter-online.de) pogodairadar.pl .
Since I'm new to HA development (and python in general 🤠 ) it would be great if you could review the code. If so let me know how I can contact you, other then creating issue in your repo :). If needed you can reach me via my email<EMAIL_ADDRESS>I also wonder  ... when you will be pushing updates to the official Accuweather integration, what would be the easiest way of propagating them to the custom integration 🤔

@bieniu Thanks for reviewing https://github.com/rotgier/home-assistant-accuweather/pull/1/ - I've fixed all comments and I'm merging this.
As mentioned before, I've prepared integration for wetteronline.de (pogodairadar.pl).
I've used the code from your accuweather integration and adapted it for another weather forecast source :)
This is my first HA integration. If you could take a look and let me know If I've done any obvious mistakes, then I would be very grateful.
If you are too busy then maybe you could point me to a place where some HA devs could take a look at a first integration of a HA newcomer :)

If you are creating a new integration, I encourage you to try adding it to the HA core repository. This is definitely the best way to reach users. Of course, it requires a bit more work, but the HA developer community is happy to help, and you can count on me too. Unfortunately, if your integration is based on web scraping, it cannot be added to the core.  I see that the site is based on some API, and that is the direction I would go.


bundle-loader 404

in react-router-dom，code split，url path （pushState），webpack load bundle by the path relative to new path，but the bundle file in root path？
how resolve？

@warfrogsdf can you provide minimum reproducible test repo?

@warfrogsdf, if I understand you correctly, I had the same issue. Mentioning of the output path in publicPath inside output section of webpack config fixed it for me. You may see in documentation what mentioning of publicPath does.

this problem id done，may cache。


请问一下，这个里面方差具体是怎么预测的？

PLEASE FOLLOW THESE INSTRUCTIONS BEFORE POSTING

Please thoroughly read README.md, INSTALL.md, GETTING_STARTED.md, and FAQ.md
Please search existing open and closed issues in case your issue has already been reported
Please try to debug the issue in case you can solve it on your own before posting

After following steps 1-3 above and agreeing to provide the detailed information requested below, you may continue with posting your issue
(Delete this line and the text above it.)
Expected results
What did you expect to see?
Actual results
What did you observe instead?
Detailed steps to reproduce
E.g.:
The command that you ran

System information

Operating system: ?
Compiler version: ?
CUDA version: ?
cuDNN version: ?
NVIDIA driver version: ?
GPU models (for all devices if they are not all the same): ?
PYTHONPATH environment variable: ?
python --version output: ?
Anything else that seems relevant: ?

Duplicate of #5


Add Bucket Policies to dotkegg Domain Redirect Buckets Preventing S3 Operations

The following buckets should never contain any objects.  Therefore, they should all be given a bucket policy in the CloudFormation template that explicitly allows only the most basic S3 operations.

dotkegg.net
dotkegg.org
dotkegg.com
www.dotkegg.net
www.dotkegg.org
www.dotkegg.com

No groups other than account admins and S3 admins have permission to do anything to these buckets, and they're the only ones that would really need these permissions anyway.  We're also leaning away from having per-service admins, so at that point, the only group whose permissions to modify these buckets would need to be denied are the account admins, which is unnecessary.  Plus, CloudFormation doesn't make it very easy to add a single bucket policy to multiple buckets, and we should really lean away from resource-based policies anyway.  Therefore, this issue shall be closed and cancelled.


Question : use application properties or UI conf for sonar server configuration ? (still on Docker image)

Hi,
When i configure the application properties (through env var and properties-builder.sh as docker cmd), the sonar servers configuration is well used. But if I make modification using the UI, the configuration is overridden.
I only want to know which is the best way to configure sonar servers (which is the "normal" or "wished" way) ? By env var or using the UI.
Thank you

This a duplicate of https://github.com/Hygieia/hygieia-codequality-sonar-collector/issues/14 sorry


Add support for blogger-posts and blogger-posts-likers

What would you like to be added:

Interact with blogger-posts
Interact with blogger-posts-likers

Why is this needed:
https://youtu.be/EPIl0IJjBrw?t=107

If we can fit this in easily, let's add to 1.3.0. Otherwise it may be delayed.

#196 done


Support all emojis from www.emoji-cheat-sheet.com

Updated the emoji collection to support the full list from www.emoji-cheat-sheet.com

CI now passing

Wow

Wow? :-)

301 files changed

Haha :) Well to be fair, lots of the emojis were missing. I know it was kind of a sucky PR. Thanks for taking this in!

@graffen It was not a "sucky" PR at all. My emoji ZEN :pray: is on the RISE thanks to you!


chore: clarify that the internal dependency resolver is exclusive

@bitgopatmcl This is actually a breaking change, since we're renaming something in the public API. I'll force a release

Whoops, this one snuck out as 4.3.5 because of #217!
Since the upgrade path is near-trivial, I don't think it's urgent to revert this diff in the 4.x branch. I'll leave this as a note to any future traveler as a compromise.


gtkwave: 3.3.108 -> 3.3.109

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gtkwave/versions.
meta.description for gtkwave is: "VCD/Waveform viewer for Unix and Win32"
meta.homepage for gtkwave is: "http://gtkwave.sourceforge.net"
meta.changelog for gtkwave is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/evcd2vcd passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/fst2vcd passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/vcd2fst passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/fstminer passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/ghwdump passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/lxt2miner passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/lxt2vcd passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/shmidcat passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/vcd2lxt passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/vcd2lxt2 passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/vcd2vzt passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/vzt2vcd passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/vztminer passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/gtkwave passed the binary check.

Warning: no invocation of /nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/twinwave had a zero exit code or showed the expected version

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/rtlbrowse passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/xml2stems passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.evcd2vcd-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.fst2vcd-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.vcd2fst-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.fstminer-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.ghwdump-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.lxt2miner-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.lxt2vcd-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.shmidcat-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.vcd2lxt-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.vcd2lxt2-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.vcd2vzt-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.vzt2vcd-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.vztminer-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.gtkwave-wrapped passed the binary check.

Warning: no invocation of /nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.twinwave-wrapped had a zero exit code or showed the expected version

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.rtlbrowse-wrapped passed the binary check.

/nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin/.xml2stems-wrapped passed the binary check.

30 of 34 passed binary check by having a zero exit code.

30 of 34 passed binary check by having the new version present in output.

found 3.3.109 with grep in /nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109

found 3.3.109 in filename of file in /nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109

directory tree listing: https://gist.github.com/4886914a7924d0525d94e9b398fdc2e3

du listing: https://gist.github.com/19dcbd44bf45a1d665c5962e8de24cde

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gtkwave

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gtkwave https://github.com/r-ryantm/nixpkgs/archive/919ca6eb957e9d7f86fb471d5f4e41833d2c24df.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109
ls -la /nix/store/aa6y8lvvkqm3pqpcvz1ksa1lr5w4zvqx-gtkwave-3.3.109/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

gtkwave

Maintainer pings
cc @thoughtpolice for testing.

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

1 package built:

gtkwave

It builds and it runs :+1:


Update database drivers

We pin the version on 3 database-specific (MySQL) packages.  They are all getting long in the tooth.  Updating them could give us better performance, but might also cause problems or require non-trivial changes:

https://github.com/cmu-delphi/delphi-epidata/blob/bc7e37590d22c541d87430684e12c747b71c6fd0/requirements.api.txt#L7

1.5y old
https://pypi.org/project/mysqlclient/#history

https://github.com/cmu-delphi/delphi-epidata/blob/bc7e37590d22c541d87430684e12c747b71c6fd0/requirements.dev.txt#L16

almost 3y old!
https://pypi.org/project/pymysql/#history

https://github.com/cmu-delphi/delphi-epidata/blob/bc7e37590d22c541d87430684e12c747b71c6fd0/requirements.dev.txt#L13

~4.5y old!!!
was: https://pypi.org/project/mysql-connector/#history
replaced by: https://pypi.org/project/mysql-connector-python/#history

I went looking for places these db packages are actually referenced/used...
pymysql seems vestigial and doesnt appear to be used anywhere, and thus should probably be removed.
In all of our python ( https://github.com/search?q=repo%3Acmu-delphi%2Fdelphi-epidata+%2Fmysql%2F+language%3Apython&type=code ), we really only use mysql-connector/mysql-connector-python aka mysql.connector.  This amounts to just the acquisition and test code.
In non-python ( https://github.com/search?q=repo%3Acmu-delphi%2Fdelphi-epidata+%2Fmysql%2F+-language%3Apython&type=code ), the only places we see mysqlclient aka mysqldb are in requirements files and as a 'dialect' in SQLAlchemy DBURIs.
It seems silly to use two different adapters/drivers across this single repository.  I was going to suggest settling on using only mysql-connector because it would not require changing code and could be done with a very small diff, but the SQLAlchemy documentation has some scary-sounding commentary on it AND it was mysql-connector that was in play when i noticed the behavior that caused me to file this issue in the first place (see https://github.com/cmu-delphi/delphi-epidata/pull/1356).  That makes me think it may be safer in the long run to have all of our stuff use mysqlclient instead.  The programming interface for mysqlclient (at a glance) looks fairly similar to what we are already using, so it might be enough to just find and replace
import mysql.connector  -->  from MySQLdb import _mysql as mysqldb
and then
mysql.connector  -->  mysqldb
but realistically, all of the usages of the module in our repo should be individually checked for compatibility.
So, at this point, we can either:

just remove the one package and update versions for the other two (and leave the other work for a new and separate GH issue)
OR remove two packages and update the version for the third, plus make python code changes to consolidate on the third.


Make it possible to iterate over arguments in a for/of if it's passed to another function

As documented at https://github.com/google/closure-compiler/wiki/Lint-warning-about-`arguments` we can't transpile the "arguments" object correctly if you iterate over it in a for/of loop, after passing it off to another function. This is because we weren't sure of a good way to identify that it is an Arguments object at runtime. @concavelenz pointed out that we can use Object.prototype.toString.call( item ) === '[object Arguments]'; which feels slightly hacky to me, but will work pretty much everywhere (I think -- we should double check). We can skip adding that check, if the lint warning mentioned in that wiki page never fires.

Sigh. The Arguments object's toString() returns [object Object] (not [object Arguments]) on IE8.

Discussed with @concavelenz and we agree the simplest path is when creating an iterator from an object, just assume the object is "array like". The downside is that incorrect code may actually run instead of throwing errors, but if users enable typechecking this is unlikely to happen.


android-safetynet

I used this lib to implement a fingerprint login on Android+Chrome. But then I received "android-safetynet" value in server/src/registration.js, where there is only "fido-u2f" and "packed" supported. So I forked and added the the option (but I'm no expert). Might be useful to others.
What I don't understand is why no one else had the issue ? Did I do smthg wrong on the client ?
Also I can't get this to work on Chrome on Windows. More exactly the fingerprint options is not proposed, only the security key. I feel this is more related to Windows than to the lib but I'd like to hear if someone has succeded using this on Windows ?

Hi @tnokin,
This library was released to fulfill the needs of an authentication with a FIDO2 key only.
All other authentication methods weren't implemented. See the roadmap at the end of the README:

To my knowledge, it is not planned to implement the support of the other authentication methods any time soon.
But this repository is open-source, feel free to contribute!


ODB Unit Tests

@donn are process_input.py.ref replacing process_input.py? If yes then lefover process_input.py should be removed.


[Config.h] Make all the defines in config.h be override-able by the build system

Per issue #4411 this PR makes all the config defines first check if they have been set by the build system, and doesn't just check for the define, but instead check the value.
This allows the config.h values to be individually set by the build system.

Are you sure this is enough? Anything you pass on the command line will still get redefined in config.h itself.
This lets you turn on extra things, but not turn off things, and not change the value of anything.

Are you sure this is enough? Anything you pass on the command line will still get redefined in config.h itself.

Yes because config.h now checks if the label is not already defined first before defining it, so things on the command line will be defined before the preprocessor runs and config.h will not replace them. This ensures that all things are still defined. I have tested this in msvc and get expected results, I can build raylib with a define in the build system only to disable screenshots. Please test it in other systems.
What this won't do is disable things at runtime, since it's all still baked into the compile with preprocessor directives.

I missed the change to config.h because GitHub collapsed it, sorry! I will test this with gcc/make on Linux later.

I tested this with:
make CUSTOM_CFLAGS="-DSUPPORT_FILEFORMAT_PNG=0 and I was then unable to load PNGs as expected
LGTM

@JeffM2501 I see the usefulness of this big change but trying to understand what problem it is currently addressing. As per the issue description:

This limitation makes it difficult to selectively disable certain features without manually editing config.h, especially when working with different build systems or when trying to configure raylib via command-line flags alone.

Yeah, that's right but, afaik, there have been no real use-case issues related since config.h was introduced. Also, this change, makes config.h bigger and less readable for new users. For my specific use cases, the tools I develop, I just overwhite config.h (defining EXTERNAL_CONFIG_FLAGS) and define the flags I want, depending on the build system I use (VS2022 example, Linux/Web). I have to see how this change affects my pipelines because it could require updating +40 projects...
I don't know... I got the feeling this redesign addresses a potential issue that nobody really had... at least yet.

I am trying to make a game where I allow the user to map items to F12, I can not because the built in screen capture and recording is using that key. That is my real world case.

You can still overwrite config.h and it will be the same as before. This just means you do not have to if you want another option. You are the author of raylib so it's not that big of a deal for you to just make a new config for each project, You always know what is in config.h. But if someone does not want to fork raylib, or does not know everything that is in raylib, that makes it much harder for them to keep raylib up to date.

@JeffM2501 Thanks for the further explanation, just one last concern, if I define make -DSUPPORT_FILEFORMAT_KTX, does it default to 1 and gets enabled? Or is it required to make -DSUPPORT_FILEFORMAT_KTX=1?

@JeffM2501 Thanks for the further explanation, just one last concern, if I define make -DSUPPORT_FILEFORMAT_KTX, does it default to 1 and gets enabled? Or is it required to make -DSUPPORT_FILEFORMAT_KTX=1?

It is required that you set the value to 1.
#define NAME does not add any default value, since #define is just a string replacement, The previous version simply checked if the define existed, not what it's value is. This was the core problem, there was no way to change it's value once it's defined. #define NAME defines NAME  as nothing, so when anything that uses NAME, it gets replaced with nothing.
so #if NAME comes out to just #if and is a syntax error.

@JeffM2501 @raysan5  That's not true!!! I just tested myself
#include <stdio.h>
int main(void)
{
#if EXAMPLE_OPTION
                puts("option enabled");
#else
                puts("option disabled");
#endif
}

$ gcc test.c && ./a.exe
option disabled
$ gcc test.c -DEXAMPLE_OPTION && ./a.exe
option enabled
$ gcc test.c -DEXAMPLE_OPTION=0 && ./a.exe
option disabled
$ gcc test.c -DEXAMPLE_OPTION=1 && ./a.exe
option enabled

It doesn't need to be =1 to enable, no compromise necessary

@Peter0x44 thanks for the test! that's really great to know! Is that behaviour consistent between compilers or it is actually "Undefined Behaviour" and could be managed in other ways by other compilers? I'm trying to find this info but I couldn't...
UPDATE: ChatGPT tells me:
Yes, if you define a macro using the -D flag without specifying a value, it implicitly evaluates to 1. This behavior follows the convention of the C preprocessor.

https://gcc.gnu.org/onlinedocs/gcc/Preprocessor-Options.html

-D name
Predefine name as a macro, with definition 1.

**Testing ChatGPT, quite impressive! 😄 **

The choice between checking if a flag is defined (#ifdef/#if defined()) or checking its value (#if CUSTOM_FLAG) depends on your specific use case and coding style. Here's a breakdown of the two approaches and their implications:

1. Checking if a Flag is Defined (#ifdef or #if defined())
Syntax:
#ifdef CUSTOM_FLAG
// Code for enabled feature
#endif

Or:
#if defined(CUSTOM_FLAG)
// Code for enabled feature
#endif

Behavior:

The feature is considered "enabled" if CUSTOM_FLAG is defined, regardless of its value.
The flag does not need to have a numeric value.
If CUSTOM_FLAG is not defined, the code is excluded.

Use Case:

When you only care whether a flag is defined or not.
Ideal for simple on/off toggles without requiring numeric or value-based logic.

Pros:

Simple and clean for basic feature toggles.
Does not require explicitly setting the value of the flag.

Cons:

Cannot easily support more complex configurations (e.g., different modes).
The code behavior depends solely on whether the flag exists, not its value.

2. Checking a Flag's Value (#if CUSTOM_FLAG)
Syntax:
#if CUSTOM_FLAG
// Code for enabled feature
#endif

Behavior:

The feature is considered "enabled" if CUSTOM_FLAG evaluates to a truthy value (non-zero).
The flag must either be defined with a numeric value (-DCUSTOM_FLAG=1) or default to 1 when defined with -DCUSTOM_FLAG.

Use Case:

When you might want to assign the flag a specific value, or use it in numeric or multi-level configurations.
Ideal for more flexible setups, e.g., enabling multiple modes or levels of a feature.

Pros:

Supports more nuanced configurations (e.g., -DFEATURE_MODE=2 for mode-specific behavior).
Explicitly checking values makes the intent clearer when toggling features programmatically.

Cons:

If the macro is not defined, you need to ensure it defaults to 0 to prevent compilation errors. Use:#ifndef CUSTOM_FLAG
#define CUSTOM_FLAG 0
#endif

Comparison

Aspect
#if defined(CUSTOM_FLAG)
#if CUSTOM_FLAG

Simplicity
Good for simple on/off toggles
Slightly more complex

Flexibility
Limited to "defined" vs "not"
Can use numeric values

Error Handling
No issues if undefined
Requires #ifndef fallback

Multi-level Config
Not supported
Supported

Code Clarity
Clearly indicates "defined check"
Explicit about value logic

Best Practice

For simple toggles (e.g., enable/disable a feature):
Use #if defined(CUSTOM_FLAG) or #ifdef CUSTOM_FLAG.

For configurable features (e.g., modes, levels):
Use #if CUSTOM_FLAG and assign meaningful values during compilation (e.g., -DFEATURE_LEVEL=2).

To ensure robustness:
Combine both patterns by defining defaults for macros in your code to avoid accidental undefined behavior:
#ifndef CUSTOM_FLAG
#define CUSTOM_FLAG 0
#endif

#if CUSTOM_FLAG
// Feature is enabled
#endif

This way, your code is safer and can handle cases where the macro is not defined.

This is exactly what this PR does.


SAP HANA XS Advanced, Creating an OData Service with Create Operation and XSJS Exit

Tutorials: https://developers.sap.com/tutorials/xsa-xsodata-create.html
Is it always mandatory to create xsjslib to POST data to xsOData?

No not mandatory. But the feature allows you to perform addition validation before the update or control how the update is done. But as long as the target entity is a single table, the generic framework can perform the update/create/delete operation for you without an exit.

Thank you very much for your reply, I will try first simply post operation
without xsjslib through Postman using created xsodata service 😊
On Fri, 7 Jan 2022, 6:07 pm Thomas Jung, @.***> wrote:

No not mandatory. But the feature allows you to perform addition
validation before the update or control how the update is done. But as long
as the target entity is a single table, the generic framework can perform
the update/create/delete operation for you without an exit.
—
Reply to this email directly, view it on GitHub
https://github.com/sap-tutorials/Tutorials/issues/7960#issuecomment-1007577435,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFIKWCPLAWGUPPUOWR5AYE3UU4MVNANCNFSM5LPGY6WQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


~!18+NEW SEX<EMAIL_ADDRESS>Baltasar Engonga Viral Video Trending Leaked Original videos on social x twitter #2212 TFLiteConverter

10 sec ago Balthazar Baltasar Ebang Engonga ʟᴇᴀᴋᴇᴅ ᴠɪᴅᴇᴏ Viral On Social Media.
𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐  𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 altasar Ebang Engonga
 🔴 ➤► 𝖶𝖺𝗍𝖼𝗁👉👉 altasar Ebang Engonga
🟢 ➤ ➤ ➤ 🌐  𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 altasar Ebang Engonga
 🔴 ➤►𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 altasar Ebang Engonga
Balthazar Baltasar Ebang Engonga latest video has taken the internet by storm, sparking lively discussions across various social media platforms. The rising digital influencer, known for her captivating content—particularly her recent Spiderman-themed video—has experienced a tremendous surge in popularity, with fans eagerly awaiting the full version. Audiences are flocking to Instagram, X (formerly Twitter), and Discord to join the conversation and engage with her latest creation.
As the excitement continues to build, fans are actively sharing their thoughts online, underscoring the pivotal role social media plays in propelling creators like Balthazar Baltasar Ebang Engonga into the limelight. With her distinctive style and creative approach, Nila has made a significant impact on the digital scene, leaving her audience eager to see what she will do next.


Install fails with Python 3.7

Due to pinning of sklearn version, it fails on 3.7. Need to change the dep for sklearn from == in requirements.txt to =>

@mattharrison got it!

I've just pushed a new release; I hope this is working!

Successfully installed pyjanitor-0.3.2


Log rotation?

Does the base vaultwarden image do log rotation? Or is there log rotation otherwise set up? I set it up on my fork of the old setup, and slowly trying to PR my changes into this new setup so I can get caught up with your latest changes.

According to https://docs.docker.com/config/containers/logging/configure/ and running the command docker info --format '{{.LoggingDriver}}', docker is using the json-file format. This format appears to default to a single log file of unlimited size, so it could indeed become a problem in the future.
I am changing the docker-compose file to use log rotation, and pulling the persistent logs from the Caddyfile.


apparmor: create an apparmor namespace for each container

Note that this only allows privileged containers to load apparmor profiles, and
only then with something like:
diff --git a/config/apparmor/abstractions/container-base b/config/apparmor/abstractions/container-base
index fe24ff3..7138249 100644
--- a/config/apparmor/abstractions/container-base
+++ b/config/apparmor/abstractions/container-base
@@ -93,7 +93,7 @@
mount fstype=sysfs -> /sys/,
mount options=(rw, nosuid, nodev, noexec, remount) -> /sys/,
deny /sys/firmware/efi/efivars/** rwklx,

deny /sys/kernel/security/** rwklx,

deny /sys/kernel/security/** rwklx,
mount options=(move) /sys/fs/cgroup/cgmanager/ -> /sys/fs/cgroup/cgmanager.lower/,
mount options=(ro, nosuid, nodev, noexec, remount, strictatime) -> /sys/fs/cgroup/,

Signed-off-by: Tycho Andersen<EMAIL_ADDRESS>

I'm gonna close this and try and rebase it. I'll send another PR whenever I get that done :)

Ok, I rebased this and it seems to being the userspace stuff correctly. I'm getting some DENIEDs that I probably shouldn't be, working with the security team on those now.


Fixes #3407. Border Subviews

Fixes

Fixes #3407

Proposed Changes/Todos

[ ] Todo 1

Pull Request checklist:

[ ] I've named my PR in the form of "Fixes #issue. Terse description."
[ ] My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
[ ] My code follows the Terminal.Gui library design guidelines
[ ] I ran dotnet test before commit
[ ] I have made corresponding changes to the API documentation (using /// style comments)
[ ] My changes generate no new warnings
[ ] I have checked my code and corrected any poor grammar or misspellings
[ ] I conducted basic QA to assure all features are working

TextField is drawing over the Border. Clipping problem?

Please don't look at this yet. It is almost completely broken.

abandoning - Will submit a new PR.


added new Zanata 0.6.0 project

Created on Zanata a new project 0.6.0 (copied from the existing Zanata project 0.5.0).
Master branch should point to this new project.
The existing 0.5.0 projects will be removed. A new 0.5.0 Zanata project will be created based on Zanata project 0.4.0.
The new dashbuilder branch 0.5.x (will be branche tomorrow) will point to the new Zanata project 0.5.0.

@dgutierr
Can you pls review this and merge this PR as this is needed before we branch the new 0.9.x

+1


Keyboard Manager: Unable to select specific app for remapping shortcut

Microsoft PowerToys version
0.77.0
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
Keyboard Manager
Steps to reproduce
When remapping a shortcut, nothing populates if you try to type into the target app field.
✔ Expected Behavior
A list of apps to show as I type, like an active filter for me to select the app.
❌ Actual Behavior
The field is focused, and I am able to type into it, but nothing happens.

Other Software
No response

Reproduced in 0.80.0.
More info: I believe this is a stateful error. My sequence of events:

I remapped Win+W to something, limited to target app = "Google Chrome".
I deleted the remapping.
Now when I try to remap Win+W again, I cannot type into "Target app". (As described in this issue.)
However, the new Win+W mapping, which has target app set to blank (i.e. it should be effective in all apps) only works in Google Chrome (!).