no CIDR blocks or IP ranges

Hello,
Is it possible to know if in the future the CIDR blocks or IP ranges will be supported?
In the scenario we have the following:

Deployed basic Security Baseline policy that enabled Network Protection
The Engineering team (works with 3rd party devices via consoles, mostly NAT IPs used) complains that if they use Upload, the upload speed immediately starts slowing down and then stuck forever on almost 0

So we have to work with two policies to filter in one all Engineering team devices and set Network Protection to Disabled,
And all rest users devices with Network Protection to Enabled.
But it would be good if we have one single policy and then we simply whitelist NAT IPs, but because NAT is a quite large range, the IP ranges solution would be very useful :)

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

ID: 0362931f-fb4c-ca1f-801e-b58a18613eae
Version Independent ID: ed70b560-7c32-81b4-f138-6f58af9ef696
Content: Create indicators for IPs and URLs/domains
Content Source: microsoft-365/security/defender-endpoint/indicator-ip-domain.md
Product: m365-security
Technology: mde
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@lightupdifire Thank you for your feedback. I do not see this in the Roadmap items. The best way to get the design change request passed to the Dev/product team is to post the feedback in our main feedback portal - https://feedbackportal.microsoft.com/
This way one of the product team members will be able to analyze the request and respond to you directly.
Hope this helps!
Thanks
Sri

@msbemba Thanks!


Supported ordered broadcast notification pattern

A likely thing to do from a WakefulIntentService is to send an ordered broadcast, to be picked up by one of N possible foreground activities, or to be picked up by a manifest-registered BroadcastReceiver. The latter case would raise a Notification, if a foreground activity did not consume this event.
However, calling sendOrderedBroadcast() from doWakefulWork() does not keep the device awake, so we get inconsistent results.
WakefulIntentService could help here by implementing a pair of BroadcastReceivers that manage the WakeLock and ensure that we will keep the device awake long enough process this request.
One BroadcastReceiver would be used by the activity. The receiver would manage the WakeLock and would abort the broadcast. It would call some listener interface before any of that to pass control to the activity (or an activity-supplied listener) to update its UI based upon the event. A static method would register the receiver at an appropriate priority level with a library-supplied IntentFilter.
The other BroadcastReceiver would be registered in the manifest, and it would raise a Notification (supplied via an Intent extra on the broadcast), plus handle the WakeLock.

Closing as out of date.


Enable local start config/admin/portal

Coverage decreased (-0.09%) to 44.705% when pulling 4f65346151bc7a31747abe541d23d532e98f148f on yiming187:local into 434343835a9a4f12574b3b0a4461a6613e08d191 on ctripcorp:master.


Editing a time entry is destructive

💻 Environment
Platform: Linux
OS Version: Ubuntu MATE 18.04
Toggl Version: 7.4.528
🐞 Actual behavior
Using the scroll wheel changes the focused element, e.g. date, start/end time.
Changes are saved immediately, with no option to undo.
This is highly destructive.
💯 Expected behavior
Scroll wheel should not have any effect (it is too likely that people just fiddle around with it).
There should be "save", "cancel", "reset" options, instead of saving immediately.
Modified fields should be visually highlighted in some way.
There should be an undo function, perhaps even some kind of versioning / revisions.
🔨 Steps to reproduce
Click on a time entry to edit.
Use tab to navigate around between the input elements.
Use the mouse scrollwheel.
📦 Additional info
This has always been a problem in the Linux desktop app.
It is one of the basic principles of interaction design to not destroy or jeopardize the user's work and data. And in this case, the numbers can equate to real money!

#2695 was supposed to have introduced undo functionality with eg Cmd-Z

#2695 was supposed to have introduced undo functionality with eg Cmd-Z

I confirm that Ctrl-Z (on Linux) undoes changes in the textfield.
But not in the other input elements.
Also the main problem here is you can do accidental changes and then don't even know what you want to undo..

I'll note that I proposed moving away from an automatic updating model in #2470, but it was closed. I'd prefer, like you've proposed, an interface that requires a button press or an Enter key to commit changes.
I suppose that's up to Toggl's discretion, however.
If they intend to keep that approach, it seems like at the bare minimum supporting undoing all changes with Ctrl/Cmd-Z is a must.

It is too easy to send a time entry into the previous year, and then never find it again..

Interestingly, I had an email exchange once in the past with the support, and someone there agreed with me ..

Also found some QAs on stackexchange, but not sure if they are helpful. Perhaps they are mostly about settings forms.
https://stackoverflow.com/questions/3066108/usability-save-changes-using-apply-button-or-after-every-single-change#3066181
https://ux.stackexchange.com/questions/12289/guidelines-for-when-to-auto-save-settings-vs-save-button?noredirect=1&lq=1
https://ux.stackexchange.com/questions/37602/saving-global-save-vs-sectional-save-vs-item-save-vs-instant-save
I would say the main criterion for whether "instant save" is a good idea is whether the controls are operated with intent and awareness, and the before/after is fully transparent to the user. Another criterion is the possible damage and recovery options.
Toggl time entries are especially problematic, because

changing the date can move a time entry into a place where you cannot find it easily afterwards.
the same UI is used to inspect a time entry and to modify it.
various kinds of input can modify the time entry.
there is a risk of delayed mode changes which change the effect of input events.

To the last point:
While looking at the list, scroll wheel means to scroll up and down, which is a zero-risk operation.
In the edit view, the scroll wheel can modify data.
Mouse clicks also have different effect in the list view vs the edit view.
Changing between the list view and the edit view can be delayed due to a sluggish network. This means a click or scroll event intended for mode A can then actually fire in mode B, causing an unintended effect.
This has happened to me more than once: In edit mode, I clicked "Done", nothing happened, I was impatient and wanted to click "Done" again, but while I was clicking it went into list mode, so the click opened another time entry for editing.
I doubt that the "instant save is better" principle applies in this scenario.

Thank you for the detailed feedback. We'll take another look at the editing and reverting logic. I think that instant save is a great logic, but there should also be a way to discard changes when user has not stopped editing an entry ( has not closed edit popup for the entry )

For my taste you could simply get rid of the instant edit in the desktop client edit dialog.
Then:

if nothing was modified, simply provide a "Cancel" button.
if something was modified, show "Save", "Cancel" and "Discard changes".

a way to discard changes when user has not stopped editing an entry ( has not closed edit popup for the entry )
with or without the instant edit, it could be useful to have a global "changelog" where you see a log of manual changes on all time entries.

The discard option in the dialog itself can be useful, but I think there may be cases where a user does not notice they modified anything.


automatic setting of the 'disabled' flag

[ ] It's mainly about automatically discovered accounts. Setting after a few (e.g. 5) attempts.
[x] Increasing the time using the factorial formula guarantees a sufficiently long time to check (5!).

automatic adding to monitoring will be removed in the next version


Rush install ends with error

Hi,
I tried (mostly just for curiosity) to build imodeljs using rush install, but it ends with error:
No matching version found for puppeteer@chrome-stable.

The latest release of puppeteer is "3.0.1".

Other releases are:
  * chrome-67: 1.3.0
  * chrome-68: 1.4.0
  * chrome-69: 1.6.2
  * chrome-70: 1.7.0
  * chrome-71: 1.9.0
  * chrome-72: 1.11.0
  * chrome-73: 1.12.2
  * chrome-74: 1.13.0
  * chrome-66: 1.1.1
  * chrome-65: 1.0.0
  * chrome-75: 1.15.0
  * chrome-76: 1.17.0
  * chrome-77: 1.19.0
  * chrome-78: 1.20.0
  * chrome-79: 2.0.0
  * chrome-81: 3.0.1
  * chrome-80: 2.1.0

If you need the full list of all 681 published versions run "$ pnpm view puppeteer versions".
Resolving: total 1973, reused 0, downloaded 1850

I guess the next error is mostly a consequence:
The command failed:
 C:\dev-iModelJS\imodeljs\common\temp\pnpm-local\node_modules\.bin\pnpm install
--store C:\dev-iModelJS\imodeljs\common\temp\pnpm-store
--no-lock
--no-prefer-frozen-shrinkwrap
--resolution-strategy fewer-dependencies
ERROR: Error: The command failed with exit code 1

Did I do anything wrong (e.g. not all prerequisites installed)?
Unfortunately my knowledge of building workflow is still not good enough to identify the problem quickly :-(
My repo is cloned with not any modifications. Node 12.16.2, Windows Pro 64bit (latest with all updates installed), Chrome version 81.0.4044.122 (the latest).
Regards,
Jan

@LabyrinthTechnology the issue is puppeteer removed the 'chrome-stable' dist tag from npmjs which a few of our packages were relying on. An update has just been pushed to change the tag to 'chrome-80' (from the list in the error message) in a 1.14.1 release.
Could you pull and try again?  Thanks!

@calebmshafer Thanks a lot for the committed fix.
rush install now runs fine and finished without error, so I close this issue.


LargeModels Support: Slow Mode

Add intermediate device argument for submodule materialization

A comment about the scheme:
If (just an if) each RankWorker or PipeStageExecutor knows its device, can we potentially save the ask for an intermediate device argument at the PipelineDriver API? I am thinking if the PipelineDriver could just send the submodule as it is passed in by the user, and let the PipeStageExecutors materialize their own submodule locally. There would be some parallelism here since the executors would perform the materialization in parallel.


⚠ Bofrost.de has degraded performance

In 42523b4, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1401 ms

Resolved: Bofrost.de performance has improved in bc43ba6.


[SETUP] Add optional dependencies to extras_require

Hi @tqchen @yurivict
Following issue #4413, this PR is going to add optional dependencies into  extras_require fields in setup.py. I would appreciate that if you can help to review/manage it, thanks.

Thanks @cchung100m !


Remove tmpfile after pip_install() finishes.

The hotfix for tmp files did not address pipenv--requirement.txt files that were left behind when pip_install was called with r==None.

I imagine this would require some safe guard around the unlink call in case Windows complains. But @techalchemy is the expert here.

Yeah it’s not this simple unfortunately. On mobile, more review in a bit.

@mteiste thanks for your input, I didn't make my decision based on test failures but rather based on specific concerns about the implementation around removal of temporary file objects which are owned by forked process groups on windows. I closed this PR because you actually have no way of knowing if the file descriptor is actually in use based simply on your own context manager, because forked processes (e.g. pip) are explicitly passed those resources.
More exhaustively, processes forked in pip_install are not all returned or completed there, which is one of many reasons why simply calling os.unlink is not a safe operation on windows. This code is not the sole owner of the file, so when the unlink inevitably fails due to another process reading it (that is sufficient to cause unlink to fail on windows), there is no wait or retry here.

if the unlink() fails due to errors like file handle leakage issues in windows subprocess handling, I cannot comment, but I would imagine we've lost at that time anyways :)

Windows is a first class citizen, so this is unfortunately not going to work as an approach. I'm sorry about this pull request, but I didn't close it out of spite or ignorance, there is legitimately a lot of nuance underlying this that I just finished sorting out with our tests. I am far from an expert but I do know that the naive approach doesn't work in this case

You have to admit the "I know where you are coming from was quite condescending" :) Just so you know where I actually come from here is how I arrived in the naive solution.

this function only creates the file if it is called with r == None, hence no unlinking is ever done unless the file was specifically created by this function itself.
first unlink is just before sys.exit(1) so if that fails it is not an issue
second unlink was done after we have processed all the sources and executed all the pip commands. [What apparently lead me to astray was the assumption that checking for return_code of delegator.run() also means that the subprocess has finished and when the loop has finished no more pip commands requiring the existence of the tmp file will be launched]

So, did the change, run tests -> failed -> reverted the change -> run tests -> same failures ergo not likely to have been introduced by the change.
So initially based on these assumptions the naive solution looked like the simplest, hence to me the preferred one (and has been working just fine on my environment (which is windows by the way :) ) but that is anecdotal not real proof and I stand corrected that basically my assumption 3 is faulty rendering the "fix" unusable. If you had not told me that the processes using the tmpfile are not guaranteed to have finished at the time pip_install() returns I would've argued that surrounding the latter unlink() in try...except would've been enough to make this safe, but alas that seems not to be the case, so I stop arguing and let you forget this patch attempt ever existed :).
Anyways, I thank you for the education and hope the issue gets a proper fix at some point in the future.

Forking commands into the background which themselves fork commands into the background isnt something you can assume is going to be a completed task just because the function returned. I said I know where you’re coming from because I do, I just happened to have worked on this in the context of our test runner which regularly had failures on windows due to concurrency issues.
As far as hoping for a fix, we’ll probably merge #1538 today which relies on a backport of TemporaryDirectory and weakref.finalize() to handle removal of these files. Exception handling here would be an alternative but the implementation of finalize allows TemporaryDirectory objects to handle removal more cleanly, plus this will fall back on our own ResourceWarning automatically if it fails rather than raising an exception at all. Thanks again for the PR, and for the engagement on this, hopefully this helps explain where I’m coming from!


translations PR 20200106

Ideally this PR should be review by community members for each language.
Note: In the event that you see an english translation instead of the desired language is because this PR was submitted before the translation was made on the Mattermost Translation Server and probably will be submitted for the next PR.

@migbot changes cannot be fix on the PR, they should be fixed on the translation server and will be submitted with the next automation

@migbot Good catch! Would you be open to sharing your proposed changes with our Romanian translators at https://community.mattermost.com/core/channels/i18n-romanian-ro ?
They can then fix it in the Translation server.
I can share too, if you'd prefer :)

Sure, done

Checking now.

Fixed them those what I've found.

@jasonblais Could you share it please? I think the {timezone} and {timezones} should also be updated to {fus orar} and {fusuri orare}, respectively.

Need to see what is the issue with the {} content, still havent realised yet what is to be translated and visible and what not.

@uhlhosting To be honest, I'm a little confused by the correct translations myself. I opened a discussion in our localization channel and hope to publish guidelines in our process documentation:
Conversation: https://community.mattermost.com/core/pl/arze9ho4btgs9y1h6gqtic8n7a
Process doc: http://docs.mattermost.com/developer/localization.html


Using package DeviceId.Wmi - MotherboardSerialNumber gives WPF scroll issues

For a full stack WPF application with multiple projects the DeviceId.Wmi library for some reason gives touch scroll issues when used.
Adding the library as Nuget package to my Infrastructure layer project would make my WPF UI layer project give touch scroll issues. The touch still works but the scrollviewer in particular could not easily be scrolled anymore (PanningMode is set to Both).
I have created a simple project where the issue is active: TestTouchScroll-issue.zip. If you comment the lines in the MainWindow.xaml.cs - line 15 to 18 the problem is fixed. So it has to do something with the .AddMotherboardSerialNumber()  or .AddMachineGuid() method that is called. I also found out that removing the MotherboardSerialNumber method fixes the issue. (the MachineGuid method doesn't use the Wmi library, i suspect the problem to lie in the Wmi library).
Hopefully this information is useful enough and feel free to ask for more information if required! Thank you in advance! Great library never the less!
Cheers, Pepijn

That's a very strange one!
Doing a bit of research, I see the following similar issues:

https://github.com/dotnet/runtime/issues/522
https://github.com/dotnet/wpf/issues/2393

I notice a workaround is posted in those issues. Does using that workaround help for your case?
Cheers

Thank you for the quick response. The workaround (adding _ = Tablet.TabletDevices; to the ) does work for the TestTouchScroll project but unfortunately not for the full stack application I am working on. The startup there is more complex (using async). For now I will not use the MotherboardSerialNumber anymore to work around this issue!


pull from upstream.

📝 Changed routes:

/404
/

(view full size)
(view full size)

1 deleted route:

/

Commit 0911ed89e1ed9fe21e460f8c189cab9d225b24b5 (https://running-page-g9t5f57uv-lizhimiao.vercel.app).


ModuleNotFoundError: No module named 'transformers.pytorch_transformers'

Hi, thank for your work.
I'm trying to finetune for image captioning task. When i run
python oscar/run_captioning.py \
    --model_name_or_path pretrained_models/base-vg-labels/ep_67_588997 \
    --do_train \
    --do_lower_case \
    --evaluate_during_training \
    --add_od_labels \
    --learning_rate 0.00003 \
    --per_gpu_train_batch_size 64 \
    --num_train_epochs 30 \
    --save_steps 5000 \
    --output_dir output/

I encounter this error
2021-02-04 06:41:10.151589: W tensorflow/stream_executor/platform/default/dso_loader.cc:60] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/local/cuda/lib:/usr/local/cuda/lib64:/usr/local/nvidia/lib:/usr/local/nvidia/lib64
2021-02-04 06:41:10.151621: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
Traceback (most recent call last):
  File "test.py", line 5, in <module>
    from transformers.pytorch_transformers.modeling_utils import PreTrainedModel
ModuleNotFoundError: No module named 'transformers.pytorch_transformers'

I clone this repo with cmd
git clone https://github.com/microsoft/Oscar.git
git submodule init
git submodule update

How could i fix this issue?

Check if u have a transformers folder and files and put right directory path on the code.

Hi @brightbsit,
I have transformers folder, i git cloned that folder in above comment. I checked file in that folder too. There are folder pytorch_transformers.
And what do you mean about " put right directory path on the code"?
I clone from this git, both main and submodule. Am I supposed to put folder "transformers" somewhere else?

I also have the same error and change the path on the code.
change the line 5 in file "test.py"

How shoud i change that line ?
This is line 5
from transformers.pytorch_transformers.modeling_utils import PreTrainedModel

What should i change it too?

Umm it depends on the folder states. I think i just add .  In the beginning

Is this what you mean?
from .transformers.pytorch_transformers.modeling_utils import PreTrainedModel

If so then the error is:
Traceback (most recent call last):
  File "test.py", line 5, in <module>
    from .transformers.pytorch_transformers.modeling_utils import PreTrainedModel
ImportError: attempted relative import with no known parent package

And what do you mean about folder states? I leaves the folder structure as in git.
And python setup.py build develop doesn't work either.

I don't have any problem with the test. But I can't find test.py file on my oscar folder. Where did u get test.py file?
the code will be gone when you fix the path.

test.py is a file i created.

To reduce time, i copy import code from oscar/run_captioning.py
To replicate error, you can run above cmd.
It creates exactly same error.

what is the error code when you type python setup.py build develop?

I don't see any error when i run sudo python3.7 setup.py build develop.
Thank you for your patience.
I just build a docker and run it in docker.
I suspect this error has something to do with call library.

thank you @alice-cool


fix the error that occures when a class have no methods

Given the following exapmle file (`test.js):
/**
 * Test class.
 *
 * @class Test
 * @param {*} a First parameter.
 * @param {*} b Second parameter.
 */
function Test(a, b) {

    /**
     * @member {*} a First member.
     */
    this.a = a;

    /**
     * @member {*} b Second member.
     */
    this.b = b;
}

jsdox fails with the following messages:
.../node_modules/jsdox/jsdox.js:164
          if (data.functions[j].className === undefined) {
                               ^
TypeError: Cannot read property 'className' of undefined
    at .../node_modules/jsdox/jsdox.js:164:32
    at jsdocParser._onComplete (.../node_modules/jsdox/node_modules/jsdoc3-parser/index.js:43:3)
    at ChildProcess.exithandler (child_process.js:646:7)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:756:16)
    at Socket.<anonymous> (child_process.js:969:11)
    at Socket.emit (events.js:95:17)
    at Pipe.close (net.js:465:12)

The new test file (fixtures/test7.js) tests this scenario, and the pull request fixes this issue.

thanks for the fix, @gaborsar :)


Refactor: Remove WillPopScope Widget in liked.dart

Remove WillPopScope widget:

The WillPopScope widget was initially used to intercept the back button press and navigate the user to the DashboardPage.
Upon reviewing the code, it became apparent that this functionality could be achieved without the need for the WillPopScope widget.
By directly specifying the route to navigate back using Navigator.pushReplacementNamed(context, DashboardPage.routeName), the purpose of the WillPopScope widget became redundant.
Thus, removing it not only simplifies the code but also eliminates unnecessary complexity.

File to be Edited
liked.dart
PS: Could you please assign this issue to me under GSSOC 24?

@Yashshukla11 please assign this to me i am GSSOC'24 contributor and have 2+ years of experience in flutter


stripe: Add cron-based plan invoicing to remote realm/server billing system.

Email to Zulip team:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Updates in the recent push:

Addressed the review comments -- see respective comments
Added a commit to fix a small variable renaming issue (first commit)

Updates in the recent push:

Addressed the review comments -- see respective comments
Added a commit to fix a small variable renaming issue (first commit)

This looks good without the transaction commit; posted in Zulip but I think probably that commit should just be its own future project.
Merged, thanks for all the work on this @prakhar1144!


bandWidth should be a number & called bandwidth (lowercase)

Thanks for fixing #1 :)
https://github.com/iamssen/typings-d3/blob/master/d3-scale/index.d.ts#L299

https://github.com/typings/registry/pull/610
Thank you : )


Convert string refs to callback refs

Summary
Convert string refs to callback refs based on React team statements of likely future deprecation of string refs.  https://facebook.github.io/react/docs/more-about-refs.html#the-ref-string-attribute
Test Plan
No additional testing needed.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Thanks for doing this! Just a comment about the Flow types, which I suppose aren't currently being checked properly...

@hellendag Thanks, I'll make adjustments.  I'm new flowtype, I would change () => void to editor: React.Element ?  and leaf: span ?

Added revision.

Will this be merged for v0.11 ?

Wow! Glad I just came across this - super happy to have this change! Looks like it just needs rebased. I can try to tidy this up, and then we'd be happy to merge it. :)

Hey @flarnie, I rebased this PR.  LMK if there is anything else that needs to change.

I've also added you as a contributor to my branch if you'd like to change anything and I'm not available.

Thanks! Seems like we just need to resolve the flow errors. I will look at that when I get a chance, either tonight or tomorrow morning, unless you beat me to it. :)

@flarnie Is it preferred to use a maybe type ?HTMLElement or only assign the ref if not null?

Other parts of the src use maybe types, so I opted for that.

Interesting - this change seems to make one of our internal integration tests fail. I will look into it more - still want to get this in but need to resolve the test failure before landing.

Manually testing and re-running the tests locally, things look ok to me. I don't expect anyone to be depending on these refs outside of Draft, hopefully I'm right. Will try landing this again on Monday. 🍀

Thanks for the update!  LMK if there is anything I can do.


How to display topic frequence info on rviz2?

Hello everyone, is it possible to display topic hz info on rviz2 just like command "ros2 topic hz xxx"?
If it is possible, how?

I don't think we keep track of the frequency for a topic but this could be easily implemented by extending the definition of RosTopicDisplay::incomingMessage and managing a subscription_start_time member everytime onEnable()/onDsiable() is invoked.  You can then calculate the frequency by dividing the messages_received_ by the elapsed time since subscription was started.

I don't think we keep track of the frequency for a topic but this could be easily implemented by extending the definition of RosTopicDisplay::incomingMessage and managing a subscription_start_time member everytime onEnable()/onDsiable() is invoked. You can then calculate the frequency by dividing the messages_received_ by the elapsed time since subscription was started.

It means that the only way to resolve my problem is to change the source code and build my own version of rviz2?

I don't think we keep track of the frequency for a topic but this could be easily implemented by extending the definition of RosTopicDisplay::incomingMessage and managing a subscription_start_time member everytime onEnable()/onDsiable() is invoked. You can then calculate the frequency by dividing the messages_received_ by the elapsed time since subscription was started.

It means that the only way to resolve my problem is to change the source code and build my own version of rviz2?

Yes, this feature is not implemented, but you can consider contribute back this and open a PR. Then you don't need to compile your own version because this feautre will be available for all the community.

I don't think we keep track of the frequency for a topic but this could be easily implemented by extending the definition of RosTopicDisplay::incomingMessage and managing a subscription_start_time member everytime onEnable()/onDsiable() is invoked. You can then calculate the frequency by dividing the messages_received_ by the elapsed time since subscription was started.

It means that the only way to resolve my problem is to change the source code and build my own version of rviz2?

Yes, this feature is not implemented, but you can consider contribute back this and open a PR. Then you don't need to compile your own version because this feautre will be available for all the community.

OK, thank you guys for answering my question.

I'm closing this issue, but feel free to reopen it if you are going to work on this feature

@yang19900808 I opened https://github.com/ros2/rviz/pull/1113 to add this feature.


Error No permission to call sandboxed `thread_send_message(_7532,_7534,_7536)'

Hello.
This initiative is very good but I cannot run some of the apps.
The error above is when I run the expert_system example.
Can this error be dealt with?
Thank you

See Help/Limitations and Help/Caveats.   You cannot call thread_send_message because message passing is what makes all tasks in SWISH cooperate.   If you could find out about threads and send them messages you can easily interfere with other users.
Possibly this is an indirect consequence of using some higher level library predicate.  In that case report that, but in general we will not allow for the concurrency predicates to avoid overloading the server.
You can run a local copy in which you disable sandboxing.

See https://github.com/SWI-Prolog/swish#running-swish-without-sandbox-limitations


How to migrate a custom pegdown extension to flexmark

First sorry if this is not the right place to ask question. I didn't find other proper place to ask.
I want to migrate my project from pegdown to flexmark. But I have some custom pegdown extension in my project. How can I still use these custom extension in my project ? Thanks

@zjffdu, flexmark-java parser architecture differs from pegdown, this is what makes it so much faster but it does require that pegdown extensions be re-implemented. The difficulty depends on what exactly your extension does. Overview docs in the wiki Writing Extensions
Q: Can you be more specific about what your extension does? For example LinkRenderer, parser extensions, HTML renderer, etc.
There are a few samples in the flexmark-java-samples, including pegdown options adapter, link resolver, node renderer, attribute provider for customizing HTML attributes.
All the extension modules can also be a source of inspiration since all extras beyond the CommonMark Spec 0.27 are implemented as extensions and can be used as a starting point for your customizations. Description in the wiki Extensions


support pasting text

I can copy text just fine in my browser, but pasting doesn't seem to work.  Is there some other way to paste into tty.js?  (ie: right-click brings up a context menu for a div on a webpage not as if it is on an editable field).

Still an issue, but thanks to https://gist.github.com/risacher/7837761 I managed to workaround this.


feat: [filter_box] disable instant_filtering by defult

SUMMARY
Currently filter_box's setting instant_filtering is set to true by default. We found airbnb users usually make large filter_box with multiple filter_fields. When user change filter fields one by one,  instant filtering will generate many temporary queries but no use.
This PR is to set default value be false. This change will not affect any existed filter_box settings.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN
CI
ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #9952 into master will decrease coverage by 5.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9952      +/-   ##
==========================================
- Coverage   71.33%   66.28%   -5.06%
==========================================
  Files         585      585
  Lines       30889    30775     -114
  Branches     3237     3237
==========================================
- Hits        22036    20399    -1637
- Misses       8744    10197    +1453
- Partials      109      179      +70

Flag
Coverage Δ

#cypress
?

#javascript
59.40% <ø> (ø)

#python
71.14% <ø> (-0.40%)
:arrow_down:

Impacted Files
Coverage Δ

...t-frontend/src/explore/controlPanels/FilterBox.jsx
0.00% <ø> (ø)

...rontend/src/visualizations/FilterBox/FilterBox.jsx
4.91% <ø> (-68.04%)
:arrow_down:

superset-frontend/src/SqlLab/App.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/explore/App.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/SqlLab/index.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/dashboard/App.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/explore/index.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/dashboard/index.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/setup/setupColors.js
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/chart/ChartContainer.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 167 more

Continue to review full report at Codecov.

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

I will use Zuzana's comment.

Should we consider moving the apply button to the right?


:compileJava FAILED

FAILURE:  Build failed with an exception. What went wrong: Execution failed for task ':compileJava'. Could not find tools.jar. Please check that C:\Program Files\Java\jre1.8.0_151 contains a valid JDK installation.
Platform: Windows
The command I used was .\launchClient
Java version: jre1.8.0_151, x64
Tools.jar is not included in jre1.8.0_151

Turns out the simple solution was to install the JDK Development kit instead of regular Java. Oops.
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html


ddclient: Fix ip command with usev4 and usev6

Fixes https://github.com/nixos/nixpkgs/issues/336189
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Sorry, I made a mistake here


Feature Request Color variation by absolute value

It would be useful to have the values 0 and 1/0 by the colors black and white and all other complex numbers
with intermediate colors (where the hue of the color only depends on the angle, the lightness or saturation from the absolute value).

Initial implementation in latest commit on main.


command not found: ^M on zsh start

/home/savitsky/.zshrc:3: command not found: ^M
/home/savitsky/.zshrc:9: command not found: ^M
/home/savitsky/.zshrc:13: command not found: ^M
/home/savitsky/.zshrc:16: command not found: ^M
/home/savitsky/.zshrc:19: command not found: ^M
/home/savitsky/.zshrc:22: command not found: ^M
/home/savitsky/.zshrc:25: command not found: ^M
/home/savitsky/.zshrc:28: command not found: ^M
/home/savitsky/.zshrc:32: command not found: ^M
/home/savitsky/.zshrc:33: command not found: ^M
/home/savitsky/.zshrc:source:34: no such file or directory: /home/savitsky/.oh-my-zsh^M/oh-my-zsh.sh^M
/home/savitsky/.zshrc:35: command not found: ^M
After clean manual install (through git and template copy).

themgt  answer is helpful

Thanks themgt, your answer worked for me

Please, help. I have the same problem, but I can't solve it by your advices
/home/nb/.zshrc:3: command not found: ^M /home/nb/.zshrc:9: command not found: ^M ... ... gateway%
And defaul directory became gateway%  instead of ~

@themgt suggestion worked for me thanks mate!

I did almost similar to what @bradjenn did. Changed the line endings to unix. The above command did not work for me. so i opened particular file which was causing this issue using tool - (Sublime, notepad++ any such) and then choose view --> line ending --> unix.

I had to remove autocrlf = true from ~/.gitconfig

I have to fix it manually by going to each file
by opening each file in vim and then
:e ++ff=dos
The :e ++ff=dos command tells Vim to read the file again, forcing dos file format. Vim will remove CRLF and LF-only line endings, leaving only the text of each line in the buffer.
then
:set ff=unix
and finally
:wq


Combine tool should print message

The "Combine (merge) selected features" tool should print a message that lasts a while on the screen.
"Combined X and Y".
Else we aren't sure if we did or didn't use it, or used it when we didn't expect to etc.

This was implemented as part of f5036db97894bdca33f02349e93dd55f8bfb195d for #370. I can reproduce the message in the latest development version. Are you still seeing a missing message?

You know what it's doing?
Its thinking my "C"'s are looking for a feature!

Oops, I wanted to respond to #9896.


chore: update title in README

This is a testing PR.

Depends on https://github.com/operator-framework/operator-registry/pull/1175 for ec check


If page has RTL Language support that time all grid broken

It works perfect while default language is english but when i switch to arabic language all images comes in one column and right side no gallery work in RTL language.

@giotiskl  Did you fixed the RTL issue yet?
I see the issue open till 2019 or have any quick solution for RTL.


Add some tools for AI-driven asset generation.

Various tools for generating consistent images of characters in different poses.

For the sdxl then 6GB or 8GB VRAM should be fine, and it is super fast
For auraflow we need to find someone with a 16GB GPU


Centered mode should keep position when opening sidebar

When opening the sidebar the centered view (editor) is no longer centered in the window so I need to shift my view. I would prefer it to stay where it was. Of course, if the sidebar is too wide then the editor would have to shift to the right to accomodate but not more than necessary.
I drew a picture to explain :D

Maybe the current should continue to be the default behavior so I'm proposing that this is added as a setting to VS Code.

Thanks for the artistic picture
Dup of https://github.com/Microsoft/vscode/issues/60900


Services

@Profpatsch @shlevy and I had a meeting last week about managing development time services for lorri project environments.
Background
The story here is for a developer whose software has run-time service dependencies, possibly complicated ones. These services should start when the user is working on the project and should eventually shut down after the user stops work.
Services might be easy to "pre-package", (for example, but not necessarily using NixOS modules): mysql, postgres, kafka, zookeeper
Or might be custom to the user's organization, like another repo might be used to build software, and run that software as a service.
Or it might even be provided by the project itself, where the repo builds several executables, and lorri starts/restarts them.
Immediate Questions
How do we want to express service definitions? We should probably aim for simple to configure than very flexible .
Because a project might coexist on the same host as many other projects, do we want to ensure ports are assigned instead of requested?
Do we want to be able to run services remotely like using docker run?
Do we want to be able to run services in CI?
Long Term Implementation Ideas

"Compiling" service definitions to launchd or systemd units, for use in the "user" agents. Requires expertise in how launchd works for implementation and users (for debugging and diagnosing issues.)
Expressing the services using a subset of systemd's service definition format, and implementing a systemd-to-launchd converter (same trouble as above.)
Use something like s6 (possible other inits?) to manage process starting. Ideally something with minimal bash scripts necessary.
Build and launch services with Docker. Might work real nicely overall, though for services provided by the local repo, might be a bit awkward / slow.
Support many copies of a given service. Ideally we can tightly limit the access a service has to the host, so their state can be carefully isolated, and erased.
Developers should be able to replace a local service with a remote service (ie: staging, production.)

Example application
The implementation of this feature should include an example application. Right now the thinking is a trivial "todo" manager written in Rust, backed by Redis.
Entering the directory and running lorri services start should start the services and make the webserver available on some local port.
Recompiling the code to the Rust application should cause the server to stop and start once the project has rebuilt. Because the application is hosted in the local repository, this restart should be triggered after the user runs cargo build.
Dogfood
Developers working on this project should use lorri services to manage their project's dependencies, and report bugs or fixes for UX problems. I'll be using it on OfBorg, as it depends on several external services, and several services built out of the local source.

cc https://github.com/target/lorri/issues/104

I like the idea of using something like https://www.nomadproject.io/ as a driver because the wheel wouldn't need to be reinvented and it seems to serve many of the short and long term goals while still being flexible enough to meet most use cases.

Nomad gives you the bonus of high-availability built-in, e.g. for shared/company-wide environments (it uses Raft under the hood).

Another benefit of this approach is that secret management is already a solved problem.
The nomad-vault integration could allow users to authenticate via token, username/password, kubernetes or against an existing backend / service and once authorized retrieve api keys, encryption keys, and other sensitive data that then can be injected into their environment.

I like the idea of using something like https://www.nomadproject.io/ under the hood because the wheel wouldn't need to be reinvented

I agree that it’s not a good idea to reinvent the wheel, but I don’t know if it would be wise to tie ourselves to a specific solution that is itself tied to a company ecosystem (Hashicorp in this case).
From a quick skim of the documentation, Nomad seems to indeed cover a lot of the points we talked about, but also many, many more, which makes it hard to integrate into our small project. Maybe the right step here is to not implement anything at all, but provide some templates for users on how to integrate with frameworks that are popular at the moment (but might not be anymore in two years time).

Maybe the right step here is to not implement anything at all, but provide some templates for users on how to integrate with frameworks that are popular at the moment (but might not be anymore in two years time).
This sounds like coming up with service interface/abstraction that can be implemented in user space. It sound like reasonable idea to me, though I'm not sure what the interface points would be (CLI, Rust API, plugins?).

Sounds reasonable idea to me, though I'm not sure what the interface points should be (CLI, Rust API, plugins?).

That’s a design space to be explored, I’d tentatively suggest something that can be described in either Nix or Rust, to keep with the theme.
I’d start out with something fairly restricted (but with well-defined semantics) and expand it or scrap parts based on user needs, until we have a good feeling of the scope we want to handle.

I like the idea of using something like https://www.nomadproject.io/ under the hood because the wheel wouldn't need to be reinvented

I agree that it’s not a good idea to reinvent the wheel, but I don’t know if it would be wise to tie ourselves to a specific solution that is itself tied to a company ecosystem (Hashicorp in this case).
From a quick skim of the documentation, Nomad seems to indeed cover a lot of the points we talked about, but also many, many more, which makes it hard to integrate into our small project. Maybe the right step here is to not implement anything at all, but provide some templates for users on how to integrate with frameworks that are popular at the moment (but might not be anymore in two years time).
But thanks for the links, please keep them coming! (especially if they describe the generic problem space and well-known (or proposed) solutions)
Here’s the link collection issue: #104

I agree, that makes a lot of sense!
The one thought I'd like to add is that many, like myself, currently use nomad across multiple environments(production, staging, development).  Maintaining the ability to describe tasks in a single format across environments is a huge win.
Without native nomad integration the idea that lorri requires a minimal amount of job-related configuration and allows execution of executables provided by nix/lorri(defined in shell.nix) in the current workspace would be incredible if possible.


python38Packages.nunavut: 1.0.2 -> 1.0.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.nunavut is: "A UAVCAN DSDL template engine"
meta.homepage for python38Packages.nunavut is: "https://nunavut.readthedocs.io/"
meta.changelog for python38Packages.nunavut is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

/nix/store/96jmj3sghzxsnhcv4imbz0krxg0p6kjd-python3.8-nunavut-1.0.3/bin/nnvg passed the binary check.

/nix/store/96jmj3sghzxsnhcv4imbz0krxg0p6kjd-python3.8-nunavut-1.0.3/bin/.nnvg-wrapped passed the binary check.

2 of 2 passed binary check by having a zero exit code.

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

found 1.0.3 with grep in /nix/store/96jmj3sghzxsnhcv4imbz0krxg0p6kjd-python3.8-nunavut-1.0.3

found 1.0.3 in filename of file in /nix/store/96jmj3sghzxsnhcv4imbz0krxg0p6kjd-python3.8-nunavut-1.0.3

directory tree listing: https://gist.github.com/f211fc2016749d7e1cc1e623f2379084

du listing: https://gist.github.com/372487403f7a17a31c86ee7eb32b3dbc

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

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.nunavut
python39Packages.nunavut

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/96jmj3sghzxsnhcv4imbz0krxg0p6kjd-python3.8-nunavut-1.0.3 \
  --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 python38Packages.nunavut https://github.com/r-ryantm/nixpkgs/archive/fd2b493072a769fc1f517c77934618a18b78dbf3.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/96jmj3sghzxsnhcv4imbz0krxg0p6kjd-python3.8-nunavut-1.0.3
ls -la /nix/store/96jmj3sghzxsnhcv4imbz0krxg0p6kjd-python3.8-nunavut-1.0.3/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

2 packages built:

python38Packages.nunavut
python39Packages.nunavut

Maintainer pings
cc @wucke13 for testing.

Result of nixpkgs-review pr 117721 at fd2b4930 run on aarch64-linux 1

2 packages built successfully:

python38Packages.nunavut
python39Packages.nunavut

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

2 packages built:

python38Packages.nunavut
python39Packages.nunavut


[stable/chronograf] Update to the recommended pvc patterns.

This is a split-off of PR #408 to just contain the chart chronograf.
If there's any commonality in changes nessary between this PR and the others that are being submitted at once, please mention them in #408.
Some things to note:

This initial PR will not be updating the Chart.yaml's version string, as I feel it should be done manually per-pr once each chart's otherwise acceptable.
An automated script created the splits and the PRs, on a per-folder basis under stable, after copying the relevent files from a backup of my local copy of #408

@k8s-bot ok to test


proxy: lower udp timeout

For https://github.com/GoogleCloudPlatform/kubernetes/issues/6738
change from 1 Minute -> 10 second
Or any suggested value?

LGTM, I wonder if it is worth doing more here.  Given the other thread about detecting too many file descriptors, maybe we should close idle UDP sessions if we detect it?  Obviously not this PR.  I can imagine someone using all the FDs in less than 10 seconds by doing repeated nslookups

@thockin What I have done before is to monitor the fd usage and start killing idle ones if it exceeds say 80%.


Fix an issue where the thread title is 2 lines

Before:

After:

Made the title wrap nicely if it exceeds a certain length

Please pull the master branch and fix the conflict in order to merging this PR, thanks!

Fixed


add support for client secrets

Add support for cognito apps with client secrets.

@mcchas FYI #34


Thaumcraft Outer Lands Not Generating

It would seem something in your mod is preventing the Outer Lands from generating properly; it's possible that this is related to the current Nether Issues but it's not clear. I can tell you that it seems to only be an issue with version 0.28.0 and onwards.

Duplicate of #224


Clarify slow start+locality weighted lb

Clarify how slow start works with weighted locality load balancing during cross zone routing. This came out as TODO from #29008.
Commit Message:
Additional Description:
Risk Level: Low
Testing:
Docs Changes: Done
Release Notes:
Platform Specific Features:
Fixes #29008

cc @wbpcode @adisuissa

FYI @palmobar


keep state inside SearchDelegate

I have  FutureBuilder>>ListView widgets  Inside @override buildResults(BuildContext context) method. I navigate to a new screen on list view item tap. but when i pop from the new screen the future is called again. Also i have pagination in the main list view, so when the user tap on item 100 for ex. after popping from the new screen, the main listview it will  rebuild from the beginning
class DataSearch extends SearchDelegate<String>{

  @override
  List<Widget> buildActions(BuildContext context) {
    return [
      IconButton(
          icon: Icon(Icons.clear),
          onPressed: () {
            query = '';
          })
    ];
  }

  @override
  ThemeData appBarTheme(BuildContext context) {
    final ThemeData theme = Theme.of(context);
    return theme.copyWith(
        inputDecorationTheme: InputDecorationTheme(
            hintStyle: TextStyle(color: theme.primaryTextTheme.title.color)),
        primaryColor: theme.primaryColor,
        primaryIconTheme: theme.primaryIconTheme,
        primaryColorBrightness: theme.primaryColorBrightness,
        primaryTextTheme: theme.primaryTextTheme,
        textTheme: theme.textTheme.copyWith(
            title: theme.textTheme.title
                .copyWith(color: theme.primaryTextTheme.title.color)));
  }

  @override
  Widget buildLeading(BuildContext context) {
    return IconButton(
        icon: AnimatedIcon(
            icon: AnimatedIcons.menu_arrow, progress: transitionAnimation),
        onPressed: () {
          close(context, null);
        });
  }

  @override
  Widget buildResults(BuildContext context) {
     SearchProvider searchProvider =
        Provider.of<SearchProvider>(context, listen: false);

    return query.isEmpty == true ? Container() : FutureBuilder(
        future:  searchProvider.fetchData(query),
        builder: (context, snapshot) {
          switch (snapshot.connectionState) {
            case ConnectionState.waiting:
              return Center(
                  child: SpinKitHourGlass(
                color: Colors.greenAccent,
              ));
              break;
            default:
              if (snapshot.hasError) {
                return Center(child: Text("Error: ${snapshot.error}"));
              } else {
                return Consumer<SearchProvider>(
                  builder: (context, provider, child) => ImageList(
                    models: snapshot.data,
                    isSearch: true,
                  ),
                );
              }
          }
        });
  }

  @override
  Widget buildSuggestions(BuildContext context) {
    return Container();
  }
}

I have tried to wrap the Futurebuilder widget inside a statefull widget and use AutomaticKeepAliveClientMixin but in vain
class SearchWidget extends StatefulWidget {
  final String query;
  SearchWidget(this.query);
  @override
  _SearchWidgetState createState() => _SearchWidgetState();
}

class _SearchWidgetState extends State<SearchWidget>
    with AutomaticKeepAliveClientMixin {
  Future _future;
  @override
  void initState() {
    super.initState();
    SearchProvider searchProvider =
        Provider.of<SearchProvider>(context, listen: false);
    _future = searchProvider.fetchData(widget.query);
  }

  @override
  Widget build(BuildContext context) {
    super.build(context);
    return FutureBuilder(
        future: _future,
        builder: (context, snapshot) {
          switch (snapshot.connectionState) {
            case ConnectionState.waiting:
              return Center(
                  child: SpinKitHourGlass(
                color: Colors.greenAccent,
              ));
              break;
            default:
              if (snapshot.hasError) {
                return Center(child: Text("Error: ${snapshot.error}"));
              } else {
                return Consumer<SearchProvider>(
                  builder: (context, provider, child) => ImageList(
                    models: snapshot.data,
                    isSearch: true,
                  ),
                );
              }
          }
        });
  }

  @override
  bool get wantKeepAlive => true;
}

Would like to see this feature get implemented! Thanks!

Any possible workaround for this?

I also facing this issue. Hopefully this can be implemented.

ctrl click on SearchDelegate it will open class material\search.dart
change bool get maintainState => false;
to bool get maintainState => true;

I am also facing this issue. Please implement this.

我一直以为是我学艺不精，原来是源码有问题^_^!

I'm having the same issue too!

I'm having the same issue too!

modify search.dart file.
@override   bool get maintainState => false;
to
@override   bool get maintainState => true;

modify search.dart file.
@override   bool get maintainState => false;
to
@override   bool get maintainState => true;

I have the same issue

I also have the same issue. Is there an alternative to copying search.dart?

ctrl click on SearchDelegate it will open class material\search.dart change bool get maintainState => false; to bool get maintainState => true;

You legend! Thank you!

Sad that still we don't have proper solution from flutter team

ctrl click on SearchDelegate it will open class material\search.dart change bool get maintainState => false; to bool get maintainState => true;

Better option is to copy search.dart file to your project and change maintainState property from there.
Rename showSearch to exampleShowSearch and SearchDelegate to ExampleSearchDelegate
and use them instead.

It has past 4 years, and none of one want to fix it at the framework level.  [Emm][Emm][Emm]


API version 2022-03-01 does not have operation group 'virtual_machines'

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az ssh vm Extension Name: ssh. Version: 1.1.2.
Errors:
The command failed with an unexpected error. Here is the traceback:
API version 2022-03-01 does not have operation group 'virtual_machines'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/home/catman/.azure/cliextensions/ssh/azext_ssh/custom.py", line 64, in ssh_vm
    ssh_session.resource_type = _decide_resource_type(cmd, ssh_session)
  File "/home/catman/.azure/cliextensions/ssh/azext_ssh/custom.py", line 391, in _decide_resource_type
    vm, vm_error, is_azure_vm = _check_if_azure_vm(cmd, op_info.resource_group_name, op_info.vm_name)
  File "/home/catman/.azure/cliextensions/ssh/azext_ssh/custom.py", line 443, in _check_if_azure_vm
    vm = compute_client.virtual_machines.get(resource_group_name, vm_name)
  File "/usr/lib/python3/dist-packages/azure/mgmt/compute/_compute_management_client.py", line 1982, in virtual_machines
    raise ValueError("API version {} does not have operation group 'virtual_machines'".format(api_version))
ValueError: API version 2022-03-01 does not have operation group 'virtual_machines'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az ssh vm --name {} --resource-group {}

Expected Behavior
Environment Summary
Linux-5.18.0-kali5-amd64-x86_64-with-glibc2.33, Kali GNU/Linux Rolling
Python 3.10.5
Installer: DEB

azure-cli 2.39.0

Extensions:
ssh 1.1.2
azure-devops 0.24.0

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.0.0

Additional Context

route to CXP team

@matiasveritone Can you please uninstall cli and use pip to install official Azure CLI from PyPI: https://pypi.org/project/azure-cli/ on you Kali linux machine.

@matiasveritone Please let me know if you still having any issues else, we will proceed with the closure of this case.

@SaurabhSharma-MSFT sorry for the delay.
Indeed it was solved by running in Python, which isn't ideal, but it did work!
Thx!

@matiasveritone We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


[ECP-9344]Critical - Cannot pay via apple pay express cart page

Describe the bug
Cannot pay via apple pay Adyen express on cart page.
First Error:
Shipping methods do not load which result in 'Payment not complete' and the error in the console.

Second Error:
Update onShippingContactSelect / onShippingMethodSelect to that of the code in https://github.com/Adyen/adyen-magento2-express-checkout/blob/1.1.2/view/frontend/web/js/applepay/button.js
The error above does not happen anymore, however you still get 'Payment not complete' and the error in the console -

And when you set a breakpoint in vendor/adyen/module-payment/Gateway/Validator/CheckoutResponseValidator.php line 123 you can see the error 'Required object 'paymentMethod' is not provided.'

To Reproduce
Steps to reproduce the behavior:

Add product to cart
Go to cart page
Click apple pay button
See debugging above.

Expected behavior
Order is submitted and redirected to success page with no errors.
Screenshots
Above.
Desktop (please complete the following information):

OS 14.5
Browser safari
Version 17.5

Smartphone (please complete the following information):
NA
Additional context
magento/product-enterprise-edition version 2.4.6-p6
adyen/module-payment version 9.6.0
adyen/adyen-magento2-expresscheckout version 2.1.0
On a blank Luma theme with no changes to the module, other than the testing as described above.
Using Adyen Test account.

Hello @alicedfisheye,
Thank you for bringing this to our attention.
We have created an internal ticket to investigate the scenario you mentioned. Our team is looking into it, and we will provide an update as soon as we have more information.
Thank you for your patience.
Best regards,
Khushboo Singhvi


Load Extension is not supported in QV

The Load ... Extension ... syntax is not supported in QlikView. The QV examples which included the syntax are updated.
Status
[ ] Under development
[ ] Waiting for code review
[x] Waiting for merge

Information
[ ] Contains breaking changes
[ ] Contains new API(s)
[ ] Contains documentation
[ ] Contains test
[x] Contains examples

I have cloned this branch and successfully run the load scripts in the two changed qvw-files on QlikView November 2017 SR3 (12.20.20400.0).


biome_overrides.json water color and transparency are ignored when Sodium mod is installed

With Sodium:

Without Sodium:

The underwater fog colors still work with Sodium, but the surface color and transparency always use the default colors.
Full mod list:
architectury-11.0.11-fabric
fabric-api-0.95.1+1.20.4
Minecraft-Legacy-1.20.4-1.3.2-fabric
sodium-fabric-mc1.20.3-0.5.5
Side note — this is not related to my previous report about ImmediatelyFast being incompatible. I solved that bug by creating a new, clean instance. This is a mod compatibility issue.

Unfortunately, even with some workarounds, Sodium uses the alpha for the lighting of the water too (for some reason), so the water transparency with sodium is broken, because the difference of light/transparency causes this blending issue:

But the water color with this fix works well

Fixed in version 1.3.3, there are some incompatibilities with newer versions of the Fabric API.


Use absolute URL for menu items

Menu items won't link to their correct pages in some cases.
Example: https://www.rust-lang.org/404/

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Hm, I would prefer not to do this, as it means that every user using the main menu needs a redirect.
@edunham @alexcrichton how is the 404 page handled? I don't even see it in this repo.

how is the 404 page handled?

https://github.com/rust-lang/rust-www/blob/master/error.html

Ah interesting. I wonder why it's coming up as /404 in the URL though.

@steveklabnik Ah, that was just me giving an example of a nonexistent page with a trailing slash.

Ohhhhhhhh I see now. Hm.

Yeah I'm not sure what the best solution would be for this otherwise, we can perhaps refine the logic over time but I'm gonna merge for now to at least prevent the breakage.


Loosen constraints on SBOM/SPDX validation

Reduce the validation of input values and required fields that is performed on deserializing SBOM/SPDX files. Values previously deserialized as enums will now be deserialized as strings and non-essential attributes have had the JsonRequired attribute removed. These changes allow us to deserialize a wider range of 2.x SPDX files, instead of constraining us to 2.2.1 SPDX produced only by the sbom-tool.

Codecov Report
Attention: Patch coverage is 60.00000% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 58.37%. Comparing base (8141070) to head (cd5ae31).

Files
Patch %
Lines

...crosoft.Sbom.Parsers.Spdx22SbomParser/Generator.cs
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #572      +/-   ##
==========================================
- Coverage   58.41%   58.37%   -0.04%
==========================================
  Files         250      250
  Lines        7796     7796
  Branches      916      916
==========================================
- Hits         4554     4551       -3
- Misses       2826     2829       +3
  Partials      416      416

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


[New platform] Equilibre on Kava

@MirthFutures wanted to do a final revision on safuness I think so waiting on that or anyone willing to verify.

Actually due to some errors emissions are kicked a whole week, no urgency


on iPhone / Safari after expanding, the page refreshed and lose your spot

visit site on iPhone (Safari)
expand the default results
after a few seconds the content collapses and loses your spot

I assume you're grouping?

-on my iPhone, in the Outlook app, I followed the link to issuesof.net here
-at that time 1 group was displayed (i now see 2 groups)
-after expanding the group and scrolling down through the issues, the page refreshed or the group collapsed (not sure which)

Yeah, that's an issue because I don't have a good way to store expansion / collapsing state when re-running queries. I've disabled automatic page refresh when an issue changes, which at least addresses this issue.


Feature add append method

Description
Adding new functionality, an append() static method.  This will allow for appending to an existing array or creating a new array if one did not exist previously at the key location.
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Additional unit tests have been added to ensure the expected functionality is achieved.
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

This will be pulled into the feature branch for #8


about the origin traffic

I am very interested in the work of your encrypted traffic classification.
But I see that only the extracted data about the header is in your dataset directory。
I am looking for the original pcap traffic file，thank you very much.

Hi
Unfortunately we don't have access to the original pcap files as they were handed over to Napatech. I would however think that it should be possible to generate some quite easily.


maintainer scripts: init check-hydra-by-maintainer.nix

Motivation for this change
There was no easy way to do this.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Looks like the packagesWith function is copied from maintainers/scripts/build.nix, perhaps eventually we could have some standard library for querying package metadata.

Thats true. My Nix is not that good yet.
I am open to improvements.

(sidenote: as soon as https://github.com/NixOS/hydra/pull/743 is merged, we could simplify this. Unfortunately I need to find some time to implement a proper DB migration here first)

LGTM. Tried it on myself, it was a bit slow probably due to hydra rate limiting requests. Looks like the packagesWith function is copied from maintainers/scripts/build.nix, perhaps eventually we could have some standard library for querying package metadata.

I think hydra got a bit faster lately.

So I'm sorry if I wasn't sufficiently clear last time, my PR in Hydra shouldn't block this PR. IIRC I briefly tested it last time and it appeared fine to me. So if someone else approves it, it should be good to go.


fix 'array initializer must be an initializer list', https://github.c…

…om/clMathLibraries/clBLAS/issues/153
Fix https://github.com/clMathLibraries/clBLAS/issues/153

Thanks!


Lumen's LOAD function conflicts with Lua's LOAD

Lumen defines load globally, but Lua already has a global load function. This causes problems when attempting to use Lua modules that try to call Lua's load function:
$ LUMEN_HOST=lua5.3 lumen
> (require "luarocks.path")
error: rocks_trees = {
   { name = [[user]], root = home..[[/.luarocks]] },
   { name = [[system]], root = [[/usr/local]] }
}
: No such file or directory
stack traceback:
	lumen/bin/lumen.lua:1031: in function <lumen/bin/lumen.lua:1030>
	[C]: in function 'error'
	lumen/bin/system.lua:4: in upvalue 'call_with_file'
	lumen/bin/system.lua:11: in function 'system.read-file'
	lumen/bin/lumen.lua:1088: in function 'compile_file'
	lumen/bin/lumen.lua:1094: in function 'load'
	/usr/local/share/lua/5.3/luarocks/persist.lua:37: in upvalue 'run_file'
	/usr/local/share/lua/5.3/luarocks/persist.lua:75: in function 'luarocks.persist.load_into_table'
	/usr/local/share/lua/5.3/luarocks/cfg.lua:201: in local 'load_config_file'
	/usr/local/share/lua/5.3/luarocks/cfg.lua:220: in main chunk
	...
	[string "_37result = require("luarocks.path")"]:1: in local 'f'
	lumen/bin/compiler.lua:1003: in function 'compiler.run'
	lumen/bin/compiler.lua:1014: in function 'compiler.eval'
	lumen/bin/lumen.lua:1028: in function <lumen/bin/lumen.lua:1027>
	[C]: in function 'xpcall'
	lumen/bin/lumen.lua:1027: in upvalue 'eval_print'
	lumen/bin/lumen.lua:1072: in local 'rep1'
	lumen/bin/lumen.lua:1081: in upvalue 'repl'
	lumen/bin/lumen.lua:1170: in local 'main'
	lumen/bin/lumen.lua:1186: in main chunk

I propose renaming Lumen's load function to load-file.
Alternatively, we could move Lumen's load function into system, and export it as system.load. That way it's not defined globally.

Another idea: make load a reserved word. It's technically a part of Lua, so this might make sense.

One way to solve this is to create a host object, which stores the host language's functions on startup:
runtime.l
(target lua: (define global _G))

(unless (get global 'environment)
  (define-global environment (list (obj)))
  (define-global target (language)))

(unless (get global 'host)
  (define-global host (obj require: require eval: eval))
  (target lua:
    (set (get host 'load) load
         (get host 'loadstring) loadstring)))

(define-global nil? (x)
  (target
    js: (or (= x nil) (= x null))
    lua: (= x nil)))
...

That way if users want to access language features that Lumen shadows, e.g. eval on JS or load on Lua, they can write (host.eval ...) or (host.load ...).
The above change would also have the nice effect of making runtime.l reloadable, so (load "runtime.l") re-populates the function definitions without corrupting your environment.
I really like this so I'll throw a PR your way to see what you think.

I don't like that it makes the runtime.l file less pretty, though. I tried hard to avoid that, but it's hard for me to think of a way to simplify it any further.


Note: basename is not suppported in createMemoryHistory.

Why?

The explanation I have heard is that memory history is supposed to be used server-side, or during testing where you have full control over the environment so can modify the URL however you want before calling into history.
Clientside, you're a lot more constrained in your deployment so basename is provided as a helper.

Wrong.
"server-side" must not be mentally separated from "client-side".
Javascript is isomorphic, React is, and if this library chooses not to then it's out of my preferences.

Pull requests. Use them.

@halt-hammerzeit The explanation given by @KaySackey is exactly right. When using memory history, you have complete control over what the URL is. In the browser, you don't. It's not a question of "mentally separating" server-side vs. client. Memory history isn't even supposed to be used on the server. Instead, it's used for testing, native, vr, and other scenarios where you're not constrained by the browser. In these situations, you have full control over what the URL is, so basename is totally superfluous.

Memory history isn't even supposed to be used on the server.

Then what does this library provide for server-side usage?
Nothing?
Then it's not worthy.

Whaaaaat?
Realy?
Oh, I get it, that's a bug in your README.
Fear not, I'M MAKING A PR.
YEAH, LIKE A GOOD CONTRIBUTOR.

@ryancole Yo, man, check this out: https://github.com/mjackson/history/pull/410
Happy now?

@halt-hammerzeit Sorry, but this behavior is super childish. You're blocked.

When using memory history, you have complete control over what the URL is. In

This is only true if you're using the history directly, but not if you pass it to a library that allows you to pass any history object. E.g. a very common use for the history api is react-router. In an isomorphic app you would use browserHistory client-side, and memoryHistory serverside. This works as long as you don't use a basename, but as soon as you want a basename you run into issues. Most prominently, the <link> component uses the history to create urls. This means that if you use a browserHistory (with basename) clientside you'll get different urls in the client than on the server. I might be missing something obvious, but it seems that currently it simply isn't possible to use a basename in an isomorphic app since memoryHistory lacks support for it.

I also like to add that this is specifically an issue when using react-router-redux: without redux you can use the StaticRouter which has its own basename support.


raysect.org doesn't support https

This breaks linking for external projects (like https://github.com/cherab/core/issues/314) but also from within github with extensions like https everywhere.
https://letsencrypt.org/ could be used to get certificates. Please let me know if there is something I can do to help.
PS: I would have reported this at https://github.com/raysect/documentation but the issue tracker there is disabled ...

I've reconfigured github pages and the domain DNS. HTTPS should now be supported. The URL is now cleaner too as github redirects to raysect.org domain. Could you check it is working for you? If so, I'll close the issue.

Thanks, much nicer now :+1:


[Feature Request] Option to 1. Resize Window and 2. Adjust Font Size

Problem:

Window size is fixed with a row size of 5 boxarts and column size somewhere between 2 and 3. The non-integer column size creates improper aesthetics. The fixed window size also gives no option to have custom row and column boxart count.
Buttons and fonts are too large

Possible Solution:

Allow window size adjustments so that I can have custom count of rows and columns of boxarts. Preferable if the window size is remembered across sessions
Allow global font and button scaling options (e.g. 0.5 to scale all sizes by half)

I will be honest, my UI skills aren't the greatest, hence why I made it that specific size with no ability to resize (although I might change that it in the future).

I wrote a comment and then I think I didn't submit it. I am not a coder but I think I should be able to help if you are ok with that. The font and icon scaling should be possible in the form xml files or if you have hardcoded, I will just need a little help locating those parts in the code. Window being resizable should be a flag that you need to keep on while creating the window.
Let me know what you think

Oh no, I meant in a way where I'm not really creative, but I can replicate things.

Hehe, alright! But I didn't mean if you don't know the area, I meant if you don't have time and need a hand. Anyway, looking forward to more releases! You have no idea how many have waited so long for this. We only had a youtube video to hold on to, hehe. Absolutely loving it!


Implement ignore_blank option for closing #16

Closes #16

Closing for the reason explained in https://github.com/nicolasblanco/rails_param/issues/16#issuecomment-392355114


[ZF3] Forward plugin doesn't detach problem listeners anymore.

Looks like there was a regressions as part of a v2 compatibility removable commit. The detachProblemListeners code builds the list of listeners to remove but doesn't actually remove them. For me, this manifests as my resulting ViewModel being double-rendered due to the InjectViewModelListener not actually being detached.
I will submit a PR to restore the block of code that actually detaches the listener.

@froschdesign What do I need to do to get this moving forward? I think this is the last issue preventing my team from upgrading to ZF3. My PR includes tests for both the attachment and detachment of the listeners.


FreeTime Overlapping Tag

Check for adding duplicate tags

Example:
If there is a current free time tag Mon:1300-1400 and I want to add Mon:1300-1500.
Since the new tag overlaps, the current free time tag should be removed and the new free time tag (Mon:1300-1500) will be added in.
But if the current tag is Mon:1200-1300 and the new tag is Mon:1300-1400, then the contact will have both the free time tags, AKA: Mon:1200-1300 and Mon:1300-1400 (tldr no need to merge intervals)


Not conpatible with nikic/php-parser v2.0.0

$ composer require --dev mamuz/php-dependency-analysis
Using version ^0.6.1 for mamuz/php-dependency-analysis
./composer.json has been updated
> php artisan clear-compiled
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for mamuz/php-dependency-analysis ^0.6.1 -> satisfiable by mamuz/php-dependency-analysis[v0.6.1].
    - Conclusion: remove nikic/php-parser v2.0.0
    - Conclusion: don't install nikic/php-parser v2.0.0
    - mamuz/php-dependency-analysis v0.6.1 requires nikic/php-parser ~1.3 -> satisfiable by nikic/php-parser[v1.3.0, v1.4.0, v1.4.1].
    - Can only install one of: nikic/php-parser[v1.3.0, v2.0.0].
    - Can only install one of: nikic/php-parser[v1.4.0, v2.0.0].
    - Can only install one of: nikic/php-parser[v1.4.1, v2.0.0].
    - Installation request for nikic/php-parser == <IP_ADDRESS> -> satisfiable by nikic/php-parser[v2.0.0].

Installation failed, reverting ./composer.json to its original content.

Fixed with release v1.0.0


NIFI-7361 - increase actions column width for reporting tasks

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] 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 file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@pvillard31 Is this still an issue?  If you can update the destination branch to main and confirm, I can review the changes.

Hi @exceptionfactory - yes the change is still valid. I just changed the base branch on the PR. Thanks!

Thanks @pvillard31, I will confirm the changes and plan on merging unless I notice any issues.

Confirmed changes, looks good. +1 Merging.


middleware in go json rest

anyone have example writing middleware before access the api ? Pls , middleware of author I cant  custom. :(

The middleware interface is here https://github.com/ant0ine/go-json-rest/blob/master/rest/middleware.go
If you have middleware struct you should implement method 'MiddlewareFunc', but if you have function you can use type 'MiddlewareSimple' to create it


[Bug]: Allure Report is not allowed to be opened with size less than 400 mb

Problem:
Allure Report not opening after being downloaded with file less than 400mb and Shaft Version 8.2.20240411
Screenshots

@mostafamohab I think this is related to allure dear not to SHAFT.
From our side, all our allure reports in our GitHub actions pipeline are less than 400mb in size and all of them are working fine after download.


semver

pending
See #92

I dunno how i duplicate my commits

@uael You can add includes ../sv/include to xmake/makefile.xmake_INC_DIRS
xmake_INC_DIRS += \
                               ../luajit/src \
                               ../sv/include

semver/prefix.h:33:20: fatal error: semver.h: No such file or directory
Build Fail

@uael duplicate commits? cherry-pick?

@waruqi where to link -lsv ?

duplicate commits? cherry-pick?

Didn't used it, just rebased like you sowed me, weird

@uael

where to link -lsv ?

demo/makefile:  demo_LIBS += xmake$(DTYPE) luajit$(DTYPE) sv$(DTYPE)

Didn't used it, just rebased like you sowed me, weird

But the new PR seems no problem

Ok! I going to test the make build system before commit in future..

👍

It's great! 😄  ❤


Is there any reasons why description of this package says it is compatible only with mocha 2-3?

I read the description and it says it is compatible only with old versions of mocha.

Compatible with node 0.10+, and Mocha 2.3.5 - 3.3.x.

But I have tried examples with mocha 5.2 and they work fine.
So, my question is pretty simple: is there any pitfalls in work with mocha 5?
Thanks,
Oleh

I tried to run tests with mocha 3 and mocha 5 and after removing styles from stdout they both passed all tests. I will create a PR with the updated test. But the last version is working fine with mocha 5.


c++ fixes

Fixes for C++ code:
Add explicit assignment operator where required and use new instead of malloc.

The C++ bindings were done as an experiment back in the day. Thanks for giving them some love.


Invalid "undefined symbol" error for captured variable after an if check

Description:
$title.
Steps to reproduce:
public function main() returns error? {
    string username = "";

    // Works when this is commented out.
    if username == "" {
    }

    int x = 1;

    int _ = x; // OK

    worker w {
        int _ = x; // error: undefined symbol 'x'
    }

    function _ = function () {
        int _ = x; // error: undefined symbol 'x'
    };
}

Affected Versions:
stage-swan-lake

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/34594


move core off of testbot

This change moves the core container off of the Worker, onto the client. This is towards merging core and client - having tests execute remotely and have a simple interface for the worker.
Big changes at a glance:

worker endpoint for start - to reserve the worker for a given test run. Includes heartbeat with client in case of connection loss
Commands are executed on the DUT by SSH'ing into the worker via the balena proxy, and then SSH'ing from there into the DUT. The test suite must be updated to register an ssh key with the cloud so these commands are authenticated
Tunnels can be made from the client/core to the DUT. This is useful for communicating with the DUT supervisor from tests, and also for doing "local" pushes of containers to the DUT. This is done by establishing a tunnel from the worker to the DUT, and then from the core to the worker.
HDMI capture now sends the captured images to the core upon request
Serial logs can be fetched from the worker directly

Todo:

[ ]  tests must be updated to work with this setup. In progress atm
[ ]  Hup suite
[ ]  test cloud suite - but in theory should work

Resolves: https://github.com/balena-os/leviathan/issues/651
Change-type: major
Signed-off-by: Ryan Cooke<EMAIL_ADDRESS>

@jakogut @vipulgupta2048 @klutchell I've used an npm ssh package where I can.
I've also tried to take into account the scenario where there is a virtualised worker (in this case the core can SSH directly to the DUT, and local push directly to the DUT) and a local-mode testbot worker (in this case you don't access the worker through the VPN). The resulting code is quite messy imo - a lot of if-else statements. Any ideas of how to clean that up are appreciated.

@jakogut this commit I'm about to push cleans things up also - it creates 3 ssh tunnels (only if a testbot is being used). If its a qemu test, this isn't needed and the DUT can be ssh'd and local pushed to directly.

port 43434 to the DUT supervisor
port 1375 to the DUT engine
port 22222 to the DUT openssh server

In the case of a testbot being used to drive the DUT, the DUT can be ssh'd into "directly" using localhost:22222, using a node ssh library like ssh2. Using a node library. (In my commit I've stuck to the one being used at the moment, node-ssh).
I've used the worker url given to the test as part of the config to determine whether or not its a virtualised or testbot scenario.

Once this PR is merged I think we can make another PR to merge core and client. I imagine that it would be a case of spawning suite subprocesses from the client container, and executing the tests in there, instead of having the client speak to the intermediate core container.

This PR still also doesn't include a solution for the HUP suite. To carry out the HUP suite, we agreed we would try to fix the script that allows you to HUP from a file locally - until that is done, then this version of leviathan won't be able to do the hup suite

Once this PR is merged I think we can make another PR to merge core and client.

@rcooke-warwick Agreed, that's a good plan.

This PR still also doesn't include a solution for the HUP suite. To carry out the HUP suite, we agreed we would try to fix the script that allows you to HUP from a file locally - until that is done, then this version of leviathan won't be able to do the hup suite

I don't want to block this PR any further, and the existing HUP suite is pretty broken anyway. Why don't we disable the HUP suite at the jenkins or meta-balena level for now to unblock everything else? That way we are testing against the new leviathan architecture going forward.
Also, do we have a PR in meta-balena for the suite changes required with this PR? They need to be merged around the same time obviously.

Will clean this up so we can merge asap. Also will make the corresponding meta balena PR

@klutchell just cleaning up formatting and will squash the commits. I've tested the OS and cloud suite with the testbot worker, and with the qemu worker and all tests pass (both production and development mode images) (given some minor changes to the os test suite) - After the cleanup I'll run the tests one more time on each worker to be sure, and then remove the draft tag.
I think while there may be some things that aren't optimal in this PR - we should probably consider getting it through the gate, and make further improvements iterative. There's already a bunch of big changes here and I think further removal of endpoints in the worker etc will just delay things further. Once this change is merged, further improvements become a lot quicker and easier as most of the logic sits outside the app on the hardware.
As for the hup suite, this PR adds a function to send a file/folder to the DUT using rsync over ssh - we can use that to send the image to the DUT and when the hup script is fixed, hup from the local file we just transferred

@balena-ci rebase

@klutchell, with latest commits to this and the meta balena PR, I have all 3 suites passing on both testbot + qemu

I have had to revert: https://github.com/balena-os/leviathan/pull/624 - as to preload the image, we need to find its path from the hsotOS, as we're using the hosts docker daemon to do the preloading. AFAIK, to do that we need the image to sit in a volume.

I have had to revert: #624 - as to preload the image, we need to find its path from the hsotOS, as we're using the hosts docker daemon to do the preloading. AFAIK, to do that we need the image to sit in a volume.

Yeah, I found the same thing actually, we do need the image to be on a volume to make it easier to find on the host.

@klutchell that change also had the added problem of us not clearing that /tmp directory at the end of every test run, so unpacked images get stockpiled

@balena-ci rebase

@klutchell @vipulgupta2048 , thoughts on this PR? All suites pass for me on testbot + qemu

@rcooke-warwick Let's merge it and retest the changes to the suites. Worst case, we can pin Jenkins leviathan-genericx86-64 to an older release via the branch field.
Note that we are NOT bumping the testbot fleet today as we need balena-raspberrypi to pick up the new suites.

One more test I want to run, on Jenkins, hang tight.

@rcooke-warwick I think we can't merge this until we have solved the cloud suite failing to connect to the dashboard.
If we merge this we will be blocked on merging the corresponding suite changes until we get lucky on a build of the new suites, as the issue is still present last time I tested both of these branches in Jenkins.
Also, I would like to add some code to the updated suites to indicate which leviathan branch (or version) they are using. We can make some assumptions in the Jenkins job that if we do not provide a leviathan branch/version we should assume the version prior to this merge.
I hope to have something soon, but it might just be a text file that is read by the yocto-device job and sets the leviathanBranch job parameter.

Can one of the admins verify this patch?

@rcooke-warwick I am seeing good results with qemu but I've seen this a few times when testing on the balena/testbot-personal rig with my testbot running this release.
client_1  | [2022-02-25T23:03:38.698Z][8f854c3-cloud] Preparing to flash

client_1  | [2022-02-25T23:05:56.345Z][8f854c3-cloud] # Subtest: Managed BalenaOS release suite
client_1  | [2022-02-25T23:05:56.346Z][8f854c3-cloud]     not ok 1 - Unexpected end of TCP connection

hey @klutchell I haven't been able to reproduce the above 2 errors locally.
As for the first, I will add a retry to the flashing mechanism in case the VPN flakes mid flash
As for the second, that error signals that post flashing, your DUT never came online. I haven't been able to repdouce that, what image were you testing with?

hey @klutchell I haven't been able to reproduce the above 2 errors locally.
As for the first, I will add a retry to the flashing mechanism in case the VPN flakes mid flash As for the second, that error signals that post flashing, your DUT never came online. I haven't been able to repdouce that, what image were you testing with?

Thanks for checking! I will revisit these tests after we get some other things out of the way. In theory we can merge this after addressing Joseph's comments because we will be able to retest with the rig when bumping meta-balena in balena-raspberrypi.


Bump carbon identity framework version and identity apps version

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/1077282250

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/1077282250
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/1077282250

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/1077282250
Status: failure


minifix(GUI): negate predicate to show help icon

Change-Type: patch

Accidentally removed the ! while refactoring


Add cover page Title elements

Full name of M3AAWG
Title
Date of document

Below are first pages of two 2015 and 2010 documents.

rfc6350.doc.zip


Adds "segmented controls" theme for tabs

There's a theme variant for that now; https://v-herd.eu/jonte-vaadinplus/tabs.


Board activity panel sizing and resizing

Sizing:
The Board Activity should be a fixed 320px wide unless resized. If I resize it, I'd like that resized window to be sticky across workspaces and when I open breadboard up again.
Panel pinning:

When I resize a browser window with breadboard the Board Activity should stay pinned to the right edge, unless it's more than 50 pixels from the right edge.
Similarly, if the board activity is within 50px of the top and bottom of the canvas, it should keep it's margins when i resize the canvas.

This is an interesting one because if we persist across sessions but your environment changes (browser resize, external monitor) then it could look very broken very quickly. Not entirely sure what the best approach is here.
The pinning makes sense, though.


Update diffx-scalatest to 0.5.0

Updates com.softwaremill.diffx:diffx-scalatest from 0.3.30 to 0.5.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.diffx", artifactId = "diffx-scalatest" } ]

labels: test-library-update, semver-minor

Superseded by #105.