Error: migrate:ovm - L2 gas limit too low: 0, use at least 100000

Overview
When running the migration to ovm command npm run migrate:ovm --network=optimistic_kovan there is the following error returned: L2 gas limit too low: 0, use at least 100000
Review
I notice in this project README that "to bypass this error, you may need to increase the gas value in the optimistic_kovan network configuration in truffle-config.ovm.js to the value the error indicates. Gas price should be set at the transaction level, like so: { gasPrice: 15000000 }."
I have tried doing this, as well as various combinations thereof, and I've also dug into the reported issue in Truffle here. However, I've so far not been able to deploy the SimpleStorage contract to Kovan Optimism.
Any advice on the settings to use to get around this issue would be appreciated! Many thanks.

Hi again @jensendarren. :) Unfortunately I'm aware of this issue and actively working to solve it. You can try to set gas: 0 which will force a gas estimation on the Truffle side, but I believe will result in a block limit error. I'm hoping to have a fix in this week's release and will update this issue when I do!
Does the local docker testnet give you an error as well, or are you able to deploy there to test out your project? I've been working on the Kovan piece but will be checking that part of it as well. Thanks so much for your patience as I figure this issue out!

Hi @fainashalts, Thank you again for your support.
I tried with a gas: 0 setting when deploying to optimistic_kovan but that did not work unfortunately. I'll keep a look out for the fix that you mentioned!
The local Docker testnet works fine, by the way, and I am able to deploy the contract there and interact with it without any issues.
Many thanks!

I notice that Truffle just released version 5.4.11 which I thought might fix this issue. However, after upgrading Truffle to this version, I still experienced the same issue.
After some trial and error, I did manage to get this working and I have deployed the SimpleStore contract to the Optimistic Kovan network.
There were two things I needed to do.

Set gas: 0 in the  optimistic_kovan network settings of truffle-config.ovm.js.
Add SimpleStorage.gasMultiplier = 0.9 to the migration file to fix the "exceeded the block limit" error

Perhaps I am mistaken but I had thought the version 5.4.11 release of truffle fixed this issue?
Either way, I hope this solution helps others to deploy onto Optimistic Kovan should they want to!

HI @jensendarren this is interesting, thank you for bringing it up! The release last week should have ensured that gas estimation occurs, thus obviating the need for gas: 0 in the config. However, the block limit error is still being worked on. Glad you found a temporary workaround! Is there any way you can check whether this works when you remove gas: 0 (but leave step #2 as is)? It does appear to on my end.

Thank you @fainashalts. So I just tried this out again and I removed both of the modifications that I mentioned previously and I ran the deployment and it works every time. I did not change anything else, and am still using Truffle version 5.4.11.  So it would appear that everything is working as expected and no need for the gas or gasMultiplier  hacks at all.  Many thanks again for your support with this issue!

Closing this since it's a bit stale, glad to hear this issue was resolved!


Reset paging data on server side filtering

Hi,
How do i reset the Pagenumber after applying and returning a subset of the data?
Imagine that

i'm at page 3
apply filtering, then i returned a subset with 3 elements ...so i need to reset the pagenumber.

thanks

In my case
Just use it like this.


Electron Authenticate Issue

Hello, I am trying to implement a basic Twitch OAuth flow into my Electron app (I'm using Electron forge), and I get the following error: [https://anonfiles.com/hbo5gap3z1/Unbenannt_PNG
How does the overall workflow look like to implement the package into Electron? Do I need to put everything in the main process, or which processes need to communicate with each other? I already asked on your Discord, but I wasn't able to find any information there.

Don't waste your time - Twitch made this provider obsolete by stopping to support embedded Electron as a "browser". See #503.


there is produced a zombie process for each played video

Start any video, after the player-window closed there are a zombie process of player.
Clearly, after closing of gtk-youtube-viewer all of zombies are wiped out, but anyway, it could be fixed, I think.

Thank you for reporting this issue. It has been fixed here: https://github.com/trizen/youtube-viewer/commit/bdd29c8e5f319044b831ce751fdc7203165983bc


When Digma backend is not availalbe, user should not see an error

Behavior should be similar to vscode instead.

fixed in this PR
https://github.com/digma-ai/digma-intellij-plugin/pull/139

fixed in v1.0.19


Remove unnecessary uses of the search API [phab:D925]

Created by schroederc at 2016-06-13 19:06:33:
This works towards #948.

zarko accepted this revision at 2016-06-13 19:26:43

schroederc closed via commit 5ea62f99d973fa684bf79f2ebe8493e5f0bcbd08 at 2016-06-13 19:27:34


[bug]There will be a empty tr left if i delete the last row of a table

This will cause the bottom border of the table to disappear.

The extra empty tr is unreasonable

@kagol Fix in v1.2.3. Thanks for your report:)

@kagol Sorry, I forgot to bundle the module before publish.
Please update to quill-better-table v1.2.4.

Thank you for responding quickly and fixing this problem.


Implement dynamic GUI for v1.2

Fully implement basic functionality of controllers. Dynamically accept user commands in CLI section and display relevant content in Graphics Section by calling relevant methods in Logic and Model.

Closing this issue since merged.


Getting started with Data Preprocessing in R

Article checklist
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
This fixes #1797

Hi @Daniel695. Please update the article with the suggested changes.

Thank you v much for your patience as we worked through our Repo re-structuring process.
The purpose behind this restructure - was to better allow us to handle more volume and allow students to publish more articles and get more involved with the community (with open-source contribution and suggestions).
With most of the changes coming to completion - we will be sure to get your article published asap.
Thank you again - and we are looking forward to more amazing articles.

@zolomohan suggested changes made

@Daniel695 Please make these changes ASAP.

@zolomohan I have made the requested changes.

Hi @Daniel695. Can you please update your branch to the updated directory structure?

Pull the main branch into your branch.
Move your article folder from articles/ to content/articles.
Create an author in content/author containing a bio. Take a look at how the other authors have done it.
Commit and Push to your branch.

If you need further assistance, please ping me via slack.

@Daniel695
Can you please provide us with an author page.

@zolomohan  I have added the author page.


Upgrade Astria's Celestia images to use rc5 for app and node

Current celestia-app and celestia-node images are quite out of date. We need to update both images to the latest release candidate.
App rc5:
https://github.com/celestiaorg/celestia-app/pkgs/container/celestia-app/104158389?tag=v1.0.0-rc5
Node rc5:
https://github.com/celestiaorg/celestia-node/pkgs/container/celestia-node/105006714?tag=v0.11.0-rc5

Blocks https://github.com/astriaorg/astria/issues/11

Very close to the finish line on this one. I have successfully deployed contracts, but it is not consistent and sometimes the deployment hangs. There is still an issue that we believe is related to block timing.
Locally, I tried using the following in init-celestia-appd.sh:
sed -i'.bak' 's/timeout_propose = "10s"/timeout_propose = "1s"/g' $home_dir/config/config.toml
sed -i'.bak' 's/target_height_duration = "15s"/target_height_duration = "1s"/g' $home_dir/config/config.toml

but it was still inconsistent.

Upgrading to app v1.0.0-rc9 w/
sed -i'.bak' 's/timeout_propose = "10s"/timeout_propose = "1s"/g' $home_dir/config/config.toml
sed -i'.bak' 's/timeout_commit = "11s"/timeout_commit = "1s"/g' $home_dir/config/config.toml

Resolved the issues above.


License is not in line with your intentions

In the README, you state (emphasis mine):

Feather is released under the MIT License. In short, you are free to use Feather in any personal, open-source or commercial work. Attribution is optional but appreciated.

However, that goes counter to the MIT License. With the MIT License, attribution is not optional. If you look at the page for your posted license, Github even describes the license at the top.

So it cannot be done both ways. To keep the MIT License, the note about attribution being optional should be removed. But if you want to keep attribution optional you should consider another license, such as The Unlicense. It has no conditions.

Thanks for letting me know! I've updated the README. Please let me know if you find any more inconsistencies.

I’m a bit surprised, though. Why keep the MIT license if you were fine about not having attribution? Wouldn’t releasing into the public domain be more in line with your initial goal?

@vitorgalvao I haven't given it too much thought yet. For now, I'll keep the MIT license because it seems to be the Open Source standard. I'm definitely considering The Unlicense though. Thanks for sending that to me!

In case that eases your mind a bit, The Unlicense is also supported by Github automatically. It’s one of the options when you start a new repo.

As far as I can tell, using a handful of these icons on a website is not a "substantial portions of" this project, so most of the license would not apply in that case any way?

As the OP suggests an unconditional license is desirable for users. The MIT notice condition requires copying the license terms, notice and copyright line into works using the icons which isn't usually ideal. Here's another unconditional license you could consider:
https://choosealicense.com/licenses/0bsd/
And some relevant conversation occurring right now on HN:
https://news.ycombinator.com/item?id=20503612


Add FPv2: 2022 Subaru Outback Wilderness

Description Add missing fw values for 2022 Subaru Outback Wilderness
Route
Route: 7e051e2bb863d0b6|2022-11-17--17-45-50--49

Thanks for the PR! Think it's worth having the wilderness subbrand as its own CarInfo? Do people assume that they're the same car?


[TextareaAutosize] Add inputProps

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
TextareaAutosize should behave as the other inputs and should support inputProps property
Examples 🌈
<TextareaAutosize   inputProps={{data-cy="comments"}} />
should output a textarea  like the following:
<textarea data-cy="comments"></textarea>
Motivation 🔦
Im making some tests with cypress, I add an attribute for each input that I want to check to find the element easier on the test, so in case the element changes their classname, id or html structure, it wont affect the test, but looks like TextareaAutosize doesnt support this property

EDIT: I just noticed that I can add the attribute directy on the component and it will add it into the textarea element, maybe adding that information into the documentation would help in the future. Close this issue if needed

All MUI components spread the props to the root element. The TextareaAutosize component does not render any input in order to support inputProps. So yes, you can add any prop in the component and it will be appended to the root element. I hope this explanation helps.


Update active-directory-ds-getting-started.md

@mahesh-unnikrishnan,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

#sign-off

@mahesh-unnikrishnan : Thanks for your contribution to the Azure documentation! The author, @mahesh-unnikrishnan, has been notified to review your proposed change.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.
It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We've closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


Replace with a better method to delete duplicates

Replace with a better method to delete duplicates

Hi Eitan,
Thank you for submitting this PR, We are reviewing this further internally and will update this thread in the next few days.
Regards.
Ramu.

Thanks for the submission Eitan - your query does offer a more elegant solution.
A few suggestions:

Could we also add the create table and a few inserts at the beginning to make this example self-contained

create table original_table (key_value int )
insert into original_table values (1)
insert into original_table values (1)
insert into original_table values (1)
insert into original_table values (2)
insert into original_table values (2)
insert into original_table values (2)
insert into original_table values (2)

Could we potentially leave both solutions in the article - as I believe this KB was originally written way before the times of ROW_NUMBER() and someone could take advantage of the older method. Leave the new proposed one as Method 1 and the older one as Method 2.

Thank you

Thanks for the suggestions @PiJoCoder .
I committed a few more changes.
Can you please review?

Thanks @EitanBlumin . @ramakoni1 , feel free to make a call on the structure of the KB - keeping Summary and More Information as the standard KB format.
Thank you, @EitanBlumin  for your contribution. Keep them coming.

I sent another commit with the Summary and More information headings back.
I restructured the page a bit to make more sense with the KB headings.

@EitanBlumin  and @PiJoCoder , thank you both for your contributions - our content team will review these further and merge into public branch in the next few days.

Sorry for the delays on this. We are still working on these. Please give us few more days to merge this..

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

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

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


failed to flush the buffer error in graylog output

Describe the bug
Hi there,
we are experiencing buffer errors while sending messages from fluentd to graylog.
Maybe somebody is able to help here?
Thanks in advance!
To Reproduce
try to send mesages to graylog, using the following config
Expected behavior
Buffer is flushed without errors
Your Environment
- Fluentd version: 1.14.5 (docker/kubernetes)

Your Configuration
...
    <match **>
      @type copy
      <store>
        @type gelf
        @id out_graylog
        include_tag_key true
        host "#{ENV['FLUENT_GRAYLOG_HOST']}"
        port "#{ENV['FLUENT_GRAYLOG_PORT']}"
        protocol "#{ENV['FLUENT_GRAYLOG_PROTOCOL'] || 'udp'}"
        <buffer>
          @type memory
          path /fluentd/log/elastic-buffer
          flush_thread_count 16
          flush_at_shutdown true
          flush_mode interval
          flush_interval 1s
          flush_thread_interval 1
          flush_thread_burst_interval 1
          retry_forever true
          retry_type exponential_backoff
          retry_max_interval 30
          chunk_limit_size 10M
          queue_limit_length 512
        </buffer>
      </store>
    </match>
...

### Your Error Log

```shell
...
2022-03-01 12:25:35 +0000 [warn]: #0 [out_graylog] bad chunk is moved to /tmp/fluent/backup/worker0/out_graylog/5d92742e938cdff64556210b516f5eea.log
2022-03-01 12:26:01 +0000 [warn]: #0 [out_graylog] failed to flush the buffer. error_class="ArgumentError" error="Data too big (1002429 bytes), would create more than 128 chunks!" plugin_id="out_graylog"
2022-03-01 12:26:01 +0000 [warn]: #0 [out_graylog] got unrecoverable error in primary and no secondary error_class=ArgumentError error="Data too big (1002429 bytes), would create more than 128 chunks!"
  2022-03-01 12:26:01 +0000 [warn]: #0 suppressed same stacktrace
2022-03-01 12:26:01 +0000 [warn]: #0 [out_graylog] bad chunk is moved to /tmp/fluent/backup/worker0/out_graylog/5d92744666904e7380fb20c8cc7cfa0b.log
2022-03-01 12:26:11 +0000 [warn]: #0 [out_graylog] failed to flush the buffer. error_class="ArgumentError" error="Data too big (1002427 bytes), would create more than 128 chunks!" plugin_id="out_graylog"
2022-03-01 12:26:11 +0000 [warn]: #0 [out_graylog] got unrecoverable error in primary and no secondary error_class=ArgumentError error="Data too big (1002427 bytes), would create more than 128 chunks!"
  2022-03-01 12:26:11 +0000 [warn]: #0 suppressed same stacktrace
...

### Additional context

_No response_

It seems that the above error is thrown from here:
https://github.com/graylog-labs/gelf-rb/blob/eb2d31cdc4b37c316de880122279bcac52a08ba2/lib/gelf/notifier.rb#L241-L243
It may be udp specific restriction, so using the protocol tcp option may solve as a workaround.

Hi there,
changed to tcp protocol and this error seems to be gone.
Thank you very much!


Support vanilla glide

This might be helpful for users that want to run the desktop version of this app but don't have a very powerful GPU.

Not bothering with this. no longer planning on a desktop version


[Proposal] Support for LVM thin provision

thin provision is very useful.

Storage space can be used more effectively. More users can be accommodated for the same amount of storage space when compared to thick provisioning. This significantly reduces upfront hardware cost for the storage admins.
Faster clones and snapshots.

We can consider to support
ref to https://github.com/topolvm/topolvm/blob/main/docs/proposals/thin-volumes.md

@yankay
Thanks for your proposal.
Now, LVM Thin Provision has been added in Roadmap.


Wip/ss/add ".lsp" file to project

Objective

Abstractions

Tests performed
Screen shot

These tests seem to be working for me.
Unrelated, but bringing it to your attention. A while back we ran into an issues (#36) with spaces in PRJ names. It might not be a bad idea to create a test to insure this code remains intact:
https://github.com/Autodesk-AutoCAD/AutoLispExt/blob/47985cdca3cda633312e2fc9b9d923c34769d98e/extension/src/project/openProject.ts#L67-L73

Will submit PR with another new branch.


Allow changie batch auto behavior while having kind configs with empty AutoLevel

When configuring changie kinds without AutoLevel (e.g. we do not want to release even a patch if we just add a test), changie batch auto will currently fail, even if other changes with kind config are present.

A "major" auto level might prevent changie from failing, but this is not garanteed, depending on the order changie is reading the change files.  (e.g. one change file with major AutoLevel while another change file with a kind without AutoLevel)

I am preparing a PR to address the first point

I am not sure I fully understand the use case for number one. Are you saying you have a change, that you want listed in the release, that does not count as any version bump?
Your example of a test is odd to me because to me, that wouldn't include a change fragment at all.
This would be similar to the chore label from other tools, these are things that you do that won't affect or be included in a release.
Such as updating CI, adding docs, fixing typos that sort of thing.

Yes, exactly. So having a .changie.yaml like so:
  - label: Feature
    description: new feature
    auto: minor
  - label: Chore
    key: Chore
    description: Minor tasks

If i have change files with both kind types, at the moment i will have an error. Error: no unreleased changes found for automatic bumping I would like to have a minor version bump.

The PR is introducing a flag to get the desired behavior (HighestAutoLevel does not error out if one of the change files is a kind withour an AutoLevel)

The design of changie suggests you do not include any chores in the release notes as they would not be user affecting changes. This is similar to the discussions around dependency updates.
That is to say, a change fragment indicates a user would be affected in some way and releasing would update some value in the version.
Supporting non-change changes feels outside scope unfortunately. But, maybe there is something you are doing with chores that require them to be part of the changelog.

Essentially I want to have changes that I want to track in the changelog but that won't warrant a version bump. This is not server - compatible behavior - but will allow me to have semver-compatible behavior in an environment with multiple repos forming a version.
Not every change is visible to every user or affecting every user.  So controlling visibility of the changes to whom they might affect is the goal.
I understand it's a super specific need

I am just not sure it adds any benefit to just assigning chores to patch updates and just waiting for another non chore change to come in before publishing?

Yeah the benefit for me is to use the change entries to determine the version to be published.
So changie next auto should determine the next tag, changie batch auto updates the changelog.  This works super good, until i have changes i want to be described but not update the version.

I am just not sure it adds any benefit to just assigning chores to patch updates and just waiting for another non chore change to come in before publishing?

I could do as you describe and filter the changes before running changie, checking if there is a change entry that should trigger a version bump and only call changie if its needed.
Since the tool you created is really great in what it does and the modifications i did are really minor (and require a flag set to have effect), using changie seems easier than working around this limitation by pre-filtering the change entries. The behavior is optional: Using the AllowSkippedEntries flag (probably suboptimal naming and description)  allows changie to determine the next version with kinds withouth auto, while setting this flag allows changelog entries that do not bump a version.
I could think of multiple ways how someone could use this flag even more creative e.g. automatically adding change fragments describing metadata like the PR#, the author, and such things while not adding them to the changes manually set by a user. There is probably more use cases for kindConfigs with empty AutoLevel that do not conflict with semver rules as much as my use case.

Hmm let me think about this, I am still not sold but maybe we add a preview label to whatever config option we add we can get feedback.

OK, I think, since I have had sort of similar requests, this feature is fine but I am wondering if we can just drop the error if auto is empty. Such that, an empty auto config is just effectively skipped. However, we should still error if you ONLY have empty auto configs. I think. Still not entirely sure on some of these edge cases.
I am also wondering if we can mark this change as something in preview or not, it feels like it may be a backwards incompatible change but not? Like, it used to fail but now is fine? Would that be a breaking change? I am not sure it needs to be an opt-in change via a config flag as its rather specific anyway. I am not sure if anyone is relying on the error in there use case or if it was an edge case that doesn't need to exist.
Open to thoughts of course.

I introduced the configuration flag AllowSkippedEntries to keep the behavior backwards compatible while still allow to skip.
The behavior with the flag not set should match the existing behavior.
The behavior with the flag set to true should be:

if a change file without auto: AND at least another change with auto: patch or higher, bump version to the highest auto:
if only change files without auto, throw an error
So the configuration flag makes the new behavior optional, keeps the existing api. Its optional to deprecate the existing api in favor of the new behavior (error only if only empty auto: changes), but the way i would ask devs to use changie and feature flags in the project i want to implement this behavior: use a feature flag to enable the new api, announce old api deprecated and if there is no complaints, drop the old api.

Right, I think the configuration is fine as a temporary "hey, for now you have to opt-in to this behavior" but will be the default in say 3 months or something. And the reason I am ok with that is, in order for the existing behavior to be triggered you almost needed to do something by accident. Such as, calling changie batch auto without actually configuring auto mode. This will still fail if you didn't configure any auto modes. But in the event that you intentionally went out of your way to make only one or some of your kinds auto mode we just let it slide.
To be a little more explicit the following configs are currently valid:

You do not use auto mode and have not configured any auto modes on any kinds, trying to batch auto will result in an error
You have configured auto mode on all kinds, using batch auto will work

These two requirements are still maintained with or without the flag.
However, we are adding additional options of:

You want auto mode, but one or more kinds are non-user changes you just want included without an explicit bump ( such as chores ). You can keep the auto value as empty which will no longer break if a change is found.
If your release would only contain non-user changes, you get an error ( cause it wouldn't bump anything )
If your release has a user change, we use that changes bump as normal

This is all just me agreeing with you btw, just being extra specific so that we can include these sorts of notes in the docs for auto mode. I believe this is basically what you already coded but since you created the issue and PR basically at the same time I wanted to make sure we were clear on the goal before giving my feedback on the PR.

This is also duplicated here https://github.com/miniscruff/changie/discussions/522 which I did decline to do, but if two completely separate people are asking maybe there is something I am missing.

You do not use auto mode and have not configured auto modes on all kinds, trying to batch auto might result in an error

There is still this edge case in the existing behavior (and the reason why i did not open this issue earlier). Depending on the order of change files parsed by changie, if you have a auto:major change parsed before a change without auto:, you will have a major version bump.
Other than that i agree with your summary

oh right yea, cause I early returned on finding a major so it wouldn't fail in that case.
Hmm, I am still so torn on this, in my eyes this still feels slightly out of scope for changie. It is like the edge case for standard commits chores that are just parsed out but is being asked to be put in. But it's also not like, a huge amount of code changes to support and it seems to keep coming up.
Going to see if anyone else chimes in, I know sheldon did ask for this exact thing already.

One thing I’ve realized lately is that the dependency updates actually do matter for the versioning. Let’s say renovate or dependabot provide a vulnerability fix that gets merged. I need the version to increment to actually publish this.
Innoway, I know have an extra step where I need to go add a change the entry manually to increment. With a protected branch this also can result in the need to run a PR and all status checks unless I have status check rules filtered down.
However, do I actually need to put this in a release note? It’s a bit subjective perhaps. Mostly not except this drives changie so currently I would need to.
I’ll also see that a lot of my work has been related to the developer audience in repos. Even if it’s not “customer facing” some of the changes relate to CI or build automation that has to trigger a release to make sure it works. Right now I just bump the patch version and designate some type of changes as related to CICD.
I don’t have an immediate proposal, but I will say these are some of the cases I’ve been working through to find the right balance with the changie approach, and still do more continual delivery.

Very insightful stuff sheldon. Would you say there is a missing feature here or it works as intended?
Testing CI/CD changes via releases is a weird thing for sure, but I would probably say that is true for any release notes tool. I would say if a downstream vulnerability was patched then updating that would count as a patch to your tool as well imo. Does it need a call out in your changelog, I think so, especially if you have a CVE link.
One thing I have thought about for a while is adding a github action bot thing that will let you create change fragments directly in PR comments. That might help some annoyances of having to make extra PRs for just changie fragments.
Like imagine if a comment like:
/changie new -k Fixed -b "upgrade curl to fix vulnerability" --custom Issue=${PR}
/changie batch auto
/changie merge
And the action would run all the commands for you, this would be useful for like, dependabot/renovate bot PRs that should be released.

I have to stay github agnostic, as I mix github + azure repos. So for me, "PR ops" commands aren't useful.
I don't want to call out dependencies in detail. The PR can serve as a link for the CVE being patched. I say this because I regularly update with Renovate, and it's just wasting time for me to have to add that each time. Not only that but Renovate will block any updates once it gets updated by someone else. This means I'd have to merge the dependency and then do another PR each time for a change entry for it, just doesn't make sense.
I do like the PR ops idea, but I think changie should stick to being CLI driven. You could wrap those workflows up in github or mage tasks perhaps, but I wouldn't be able to leverage that personally. I drive all my automation as much as possible from mage (go tasks) instead of the logic being in the actions. So I actually don't get a lot of benefit from relying on github actions anyway. Example workflow helper codified bump

good discussion :-)

oh yea, I should of remembered that, you mentioned it before.
Ok what about this @adlotsof what if, as an experimental thing, the value of "none" for an auto was the indicator that its ok to skip this change. Since its not the zero value of the config we know you manually set this value. Saves the config and it will be much easier to drop/change the value of if it doesn't end up working out.

Implemented this in the pr


WIP:  #155_Aplicar_Redux_para_controle_de_estados

Nesse pull request foi feito:
Issue #155
Correção de bugs

Pull Request Test Coverage Report for Build 274

27 of 60 (45.0%) changed or added relevant lines in 11 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage increased (+4.1%) to 38.683%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

App.js
1
2
50.0%

src/Screens/NewManager.js
0
6
0.0%

src/Screens/LoginScreen.js
4
13
30.77%

src/Screens/InitialScreen.js
3
20
15.0%

Files with Coverage Reduction
New Missed Lines
%

src/Screens/InitialScreen.js
1
13.04%

src/Screens/ProfileScreen.js
1
8.33%

src/Screens/NewManager.js
2
26.19%

Totals

Change from base Build 251:
4.1%

Covered Lines:
77

Relevant Lines:
189

💛  - Coveralls

Ok joão, vamos adicionar o id

Já adicionamos o id @egewarth


add last modified headers and conditional processing

sanity checked this on the test site, seems to be working fine


Set max output tokens with Ollama + Llama index

I'm trying to set an output max tokens with llama index but it doesn't work. Can someone help me?
import pandas as pd
import os
from llama_index.llms.ollama import Ollama
from transformers import AutoTokenizer
from llama_index.core import Settings
Configure the settings for the LLM
Settings.llm = Ollama(model="mixtral:8x7b-instruct-v0.1-q5_K_M", max_tokens=5)
Initialize the Ollama model with the modified settings
llm = Settings.llm

You might have better luck in the llama index repo since it looks like the main interface is llama_index.llms.ollama.Ollama.
Ollama supports limiting token output (and many other options) through the JSON field options in the generate or chat request, e.g.
curl http://<IP_ADDRESS>:11434/api/generate -d '{"model":"mistral","prompt":"What is the meaning of life?","options":{"num_predict":10}}'

You can just pass the num_predict to the ollama class:
from llama_index.llms.ollama import Ollama

Settings.llm = Ollama(model="llama3", request_timeout=100.0, additional_kwargs={"num_predict": 10})
resp = Settings.llm.complete("Who is nikola Tesla?")
print(resp)


Encryption support in Kafka Adaptor

Is your feature request related to a problem? Please describe.
We need to encrypt the data in transit and at rest, so the ideal option for us is to use End-to-End Encryption feature. But as we are porting our Kafka application to Pulsar, we have plans to use Kafka Adaptor so that, we can port our application as is with only few configuration changes (Pulsar URL and Topic URL). In this case, as the Kafka Adaptor doesn't support both TLS based Encryption / End-to-End Encryption, we are not able to use our application as is on top of Pulsar.
Describe the solution you'd like
It would be great to have a configuration / provision to provide the encryption entities to Kafka Adaptor. This will help us to use existing Kafka Application as is on Pulsar and also encrypt the data between Producer and Consumer both at rest and in-transit.
Describe alternatives you've considered
As of now, we don't see any alternative apart from porting our Kafka application to Pulsar in order to use one of the encryption mechanism.
Additional context
Submitting this request based on @sijie confirmation in user mailing list.

Closed as stale and no one seems to work on it. Please create a new issue if it's still relevant to the maintained versions.
IIRC kafka adapter is no longer maintained.


provenance & msParts; removed stucco from taxonomy and files

that's an awesome amount of work, thank you!


Generate a diff between gencode releases

This will be used to determine what need to be updated in the datasets
Question: where should this be stored, or should it be generated when doing the dataset conversions?

The diff information should live in or near the script that automates the migration. Have we established where those scripts live?


Add a pop up dialog box for Polls/Survey done ! #563 🌟🌟🌟

Hello, PR
Add new feature - #563
Add a pop up dialog box for Polls/Survey done properly -
https://github.com/user-attachments/assets/9b2762a9-9c93-490f-8943-8aa1c625c6b0

📄 Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (adds or updates related documentation)

✅ Checklist

[x] I am a participant of GSSoC-ext.
[x] I have followed the contribution guidelines of this project.
[x] I have made this change from my own.
[x] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have added documentation to explain my changes.

Mandatory Tasks

[x] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

🤝 GSSoC Participation

[x] This PR is submitted under the GSSoC program.
[x] I have taken prior approval for this feature/fix.

@YadavAkhileshh done, please merge my PR with level 3, If you check other projects, they are also giving level 3 for this..
You can check my code..
Thank you 🙏🏻

@YadavAkhileshh sir done, please merge my PR with level 3, If you check other projects, they are also giving level 3 for this..

You can check my code..
Thank you 🙏🏻

@YadavAkhileshh sir kindly🙏🏻 upgrade the level 2 to 3, If you check other projects, they are also giving level 3 for this..

@YadavAkhileshh sir kindly🙏🏻 upgrade the level 2 to 3, If you check other projects, they are also giving level 3 for this..

@YadavAkhileshh sir please 🙏🏻🙏🏻

@YadavAkhileshh sir please 🙏🏻🙏🏻

@YadavAkhileshh sir please 🙏🏻🙏🏻

@YadavAkhileshh sir please add level 3 🙏🏻🙏🏻=

@YadavAkhileshh sir please add level 3 🙏🏻🙏🏻

Thank You sir 🥹🙏🏻


Plan for remote participation

evaluate potential channels for remote participation

e.g.

live stream (video and/ or audio)
presentations online before talk starts
Twitter hashtag(s)
GitHub tickets
collaborative note-taking

review existing tickets as to whether remote and on-site participants should be treated differently (e.g. we don't need food preferences for remote attendees)

If we have individuals assisting in sessions, questions/comments could be invited via Twitter (or whatever other means) and shared by that facilitator like any other question.

I'd like to remain open to more active remote participation too, e.g. some talks could be given remotely.

+1 to questions or comments via Twitter

Discussion from Steering Committee call 7/19/17 and comments during Program Committee call 7/201/17:
ACTION: Find out how many people actually were on the live streaming to decide if it is a good return on investment and look into the difference in cost between streaming all events in one room vs only the keynotes or plenary sessions.

Q (BK) How about live-streaming vs. recording? I.e. if we don’t livestream, would we still record and put recordings up on website or figshare?

Doing audio in the breakout session rooms seems like enough but without losing the knowledge shared. (KC)

Remark [BK] Return-on-investment is also dependent on a) how people who used livestream appreciated it (can we evaluate that?) and b) how much outreach is done around livestream, esp. when we focus on inclusivity.

This issue was moved to force11/force2018#12


alloc profiler: record pool allocs, even though they'll be missing a type

merges onto https://github.com/JuliaLang/julia/pull/42768
touches https://github.com/JuliaLang/julia/issues/43688
Description
Some allocations go through the jl_gc_pool_alloc codepath, which doesn't get type. This PR captures the stacktrace and size from that codepath anyway. The real solution involves possibly changing LLVM codegen to generate code which pass in a type to jl_gc_pool_alloc.
The alloc profiler decoder will mark these as having type UnknownType.
Evaluation
Experimentation on https://github.com/vilterp/HeapSnapshotParser.jl/blob/master/test/runtests.jl shows it's only picking up an additional 1% of allocs:
# this PR
julia> res = Profile.Allocs.@profile sample_rate=0.01 HeapSnapshotParser.parse_snapshot("testdata/empty-repl.heapsnapshot")
julia> prof = Profile.Allocs.fetch()
julia> num_allocs = length(prof.allocs)
29605

# base alloc profiler
julia> res = Profile.Allocs.@profile sample_rate=0.01 HeapSnapshotParser.parse_snapshot("testdata/empty-repl.heapsnapshot")
julia> prof = Profile.Allocs.fetch()
julia> num_allocs = length(prof.allocs)
29335

julia> 29335.0 / 29605.0
0.990879918932612

A larger proprietary codebase was showing ~10%.

@NHDaly don't have to merge this now; just something to have in our back pocket in case it comes up in code review discussion…

@vchuravy does it seem reasonable that only a small percentage of allocs would go through jl_gc_pool_alloc? What makes the decision of whether it uses that or jl_gc_alloc_? Thanks.

hold on, this is not right, since jl_gc_alloc calls jl_gc_pool_alloc…

I am surprised that only the minority of allocations are type-less. Effectively all small allocation that happen in compiled code will go directly to  jl_gc_pool_alloc instead of jl_gc_alloc
cc: @pchintalapudi

Julia has quite a few different allocating methods, mixed in at the Julia/LLVM level and at the C level.
So all julia.gc_alloc_obj intrinsics are first lowered to GCAllocBytes intrinsics in late-gc-lowering, and then those calls are inlined in final-gc-lowering to point to either jl_gc_pool_alloc or jl_gc_big_alloc as-if jl_gc_alloc_ had been called, which is why those bare calls appear in the final compiled output.
However, array and string allocations are handled in C, and are therefore not seen or inlined by the optimization passes. My guess is that most of the allocations in whatever benchmark is being used are primarily array or string allocations, and that's why only a small percentage of allocations seem to skip jl_gc_alloc. If one was to create benchmark primarily allocating structs without arrays or strings, I'd guess that'd show 100% of allocations being missed.

Thanks for the info. I’m pretty sure my benchmark allocated a few thousand structs, but I’m not sure I was counting right. Will take another pass at getting these percentages on different workloads.

Superseded by https://github.com/vilterp/julia/pull/14, which avoids double counting


Bug🐛: Add files to Orphan Check exclusion list

Describe the bug.
The following files are not "true orphans" and thus should be added to the orphan page check GHA's exclusion list.
To exclude from orphan check:
Only in ./_site: 404.html
Only in ./_site: dir.html
Describe the steps to reproduce the behavior
n/a
Expected behavior.
The above listed pages should not appear in future orphan page check runs.
Screenshots.
No response
Operating environment
GitHub
Additional context
This is related to issue #239

PR #246 closes this issue.


cell color controlling minions

Hi - I noticed in this new version when you hit Q to control the minions the player cell color doesn't change to Grey. In the older version 1.3.5 it did. Is there a setting for it in 1.4.2?

@cowpits it was removed a while ago for performance reasons, see this commit: https://github.com/Megabyte918/MultiOgar-Edited/commit/5a067fb882aba14e6fe19a3c65f04bee2af2c10a
If you want it back you can add the code that was removed, I'm not going to be adding it back to the repo because it required a massive amount of code.


Refactored hijack to intercept for brevity.

The principle of the "hijack" command was to intercept a running
container and modify it's runtime. While hijacking can be accurate from
a point of view, intercepting is the intended purpose and specifically
describes the action taken. Hijacking, especially in the context of
aerospace, is a socially murky topic due to numerous events in the past
20 years and can be negatively received by consumers of the tool.
Signed-off-by: Mike Lloyd<EMAIL_ADDRESS>

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

@mxplusb Thank you for signing the Contributor License Agreement!

Updated the commit with a rebase and with my Pivotal email and re-ran the CLA check.

You might also have to rebase and recreate this PR based on head of fly.

Rebased with no errors.

Thanks @mxplusb can you look at the one review we made?

Sure, where can I find it? I don't see any comments in the files changed tab.

@mxplusb sorry about that I'm still getting used to this Github UI. does it show up now?

I'm not seeing it, but I'm not super familiar with the review UI either, feel free to inline them here if it's easier! 😄

Nvm, see it!

This command borrows from some internals of Garden (which we use for containerization), and its implementation in the Attach function here. We've already aliased intercept, and I don't think we need to remove all reference to hijacking since it is based on a concept in Garden.


Fix manual process about restore a deleted database

Hi @buchizo, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@elfisher
Please review approve/disapprove with a comment. Thanks.

Follow-up mail sent for review request.

Hi buchizo,
The proposed change is not the correct workflow for restoring a deleted database. The current documentation is correct. I think there is a misunderstanding though. The proposed change will restore a database, however it is the workflow for restoring using Geo-Restore as illustrated in the documentation here: https://azure.microsoft.com/en-us/documentation/articles/sql-database-disaster-recovery/#recover-using-geo-restore
If you have more questions let me know.
Thanks,
-Eli

Thank you, both. I'll close this PR unmerged.

Hi Eli,
If I am not mistaken, I can't do that operation on portal.azure.com, because I can't look 'deleted database' on server's blade.
https://azure.microsoft.com/en-us/documentation/articles/sql-database-user-error-recovery/

Are you able to access your server blade?  If you are unable to access your server blade, do you have any role based access control permissions set?
Regards,
-Eli

Hi @elfisher ,
I found it! Sorry, I had a mistake. I'd like to close this PR.

Suggestion:

Now: Under Operations on you server's blade, select Deleted Databases.
My Suggestion: Under Operations on you server's blade, click Deleted Databases tile.

Great suggestion!
Thanks!


Awesome Font Files returns an 404

Hi,
we are using Icingaweb2 v2.11.2 with ipl v0.10.0.
The webinterface tries to load the Awesome Font Files via this URL lib/icinga/icinga-php-library/font/awesome/fa-solid-900.woff2, but we get back an 404 HTTP Error Code.
Since the 404 Page is empty, i believe that the php code throws this error. The Font files are in the corrent path:
root@master-0:/usr/share/icingaweb2# ls -la /usr/share/icinga-php/ipl/asset/static/font/awesome/
total 952
drwxr-xr-x 2 root root   4096 Nov  1 16:58 .
drwxr-xr-x 3 root root   4096 Nov  1 16:58 ..
-rw-r--r-- 1 root root 186112 Nov  1 16:58 fa-brands-400.ttf
-rw-r--r-- 1 root root 107460 Nov  1 16:58 fa-brands-400.woff2
-rw-r--r-- 1 root root  62048 Nov  1 16:58 fa-regular-400.ttf
-rw-r--r-- 1 root root  25084 Nov  1 16:58 fa-regular-400.woff2
-rw-r--r-- 1 root root 397728 Nov  1 16:58 fa-solid-900.ttf
-rw-r--r-- 1 root root 150468 Nov  1 16:58 fa-solid-900.woff2
-rw-r--r-- 1 root root  10136 Nov  1 16:58 fa-v4compatibility.ttf
-rw-r--r-- 1 root root   4584 Nov  1 16:58 fa-v4compatibility.woff2

Used Versions:
Icinga Web 2 Version    2.11.2
PHP Version 7.4.30

Loaded Libraries
icinga/icinga-php-library   0.10.0
icinga/icinga-php-thirdparty    0.11.0

Loaded Modules
azure       0.6.3
businessprocess     2.4.0
cube        1.2.2
director        1.9.1
grafana     master
idoreports      0.10.0
incubator       0.19.0
map     1.1.0
monitoring      2.11.2
pdfexport       0.10.2
reporting       0.10.0

The Webinterface works fine, but since the font does not load, all icons using the font are not visible.

Hi,
the UI does not return a 404 without a message. (Just checked) I suspect a webserver configuration issue. If you can't find it yourself, please head over to the forums and ask for help.
If you then still think this is a bug, please create an issue here and include steps to reproduce it. The steps shown here only describe a common installation, which can't be the problem. Otherwise we'd have more reports by now.
Best,
Johannes

The UI throws 404 Errors on some pathes without messages, see here: https://github.com/Icinga/icingaweb2/blob/master/library/Icinga/Web/Controller/StaticController.php#L56
Our Problem was that an Apache Reverse Proxy configuration which is in front of our Icingaweb2 added an additional slash (/) at the beginning of every URL, so the Webserver sees //lib/icinga/icinga-php-library/font/awesome/fa-solid-900.woff2 as the URL.
This works wihtout any problems for everything but this font.
We fixed this at the reverse proxy, so this is working now.


Can I SetCellHyperLink in stream mode?

Description
We learned DONT use File method and StreamWriter at same time. Now we need to set cell hyper link, could excelize add support of StreamWriter.SetCellHyperLink? Thanks!

Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Output of go version:
(paste your output here)

Excelize version or commit ID:
(paste here)

Environment details (OS, Microsoft Excel™ version, physical, etc.):

At the moment, one workaround for this is to use the HYPERLINK function and set it inside the Formula field.
For example
data := []interface{}{
  excelize.Cell{Formula: `=HYPERLINK("http://localhost", "http://localhost")`},
}
sw.SetRow("A1", data)

Moreover excel has a hard limit for not-formula-hyperlinks that equals 65530 links per worksheet. So it might be better to use hyperlink as formula while writing via stream.


removeTitle

I didn't manage to make this plugin work
is this the right syntax?
svgo --enable=removeTitle  -s '<svg version="1.1"><title>foo</title></svg>' -o -

why
removeTitle
disabled by default?

For accessibility reasons–there could be description that helps people to understand an image.


Limitation of scoring function to only 'accuracy'

Excellent work on this library. Love it.  😄
https://github.com/modAL-python/modAL/blob/master/modAL/models/learners.py#L363 <-- we are only allow to use accuracy for the score(). There are variety of scoring functions (e.g., F1) which are more solid than accuracy in sklearn: https://scikit-learn.org/stable/modules/model_evaluation.html for model evaluation. May be this can be implemented in the next release of modAL?

Thanks, I am glad you have found it useful! :)
Sure, it is a good idea! Judging from this comment in the score method, this has been come up before :) One simple solution I have in mind is to allow the specification of the metric in the arguments.
Until this is implemented, a workaround for this is to use the scikit-learn scoring functions directly, since this is not too difficult, thanks to the general implementations in scikit-learn.

Great. 👍


missing " in output for string schema

If the top-level schema is string, the output from llgtrt seems to be missing the initial quote. Not sure if this is llgtrt or llguidance problem.
Example schema:
{
    "$schema": "http://json-schema.org/draft-06/schema#",
    "type": "string",
    "enum": [
        "1",
        "2-two",
        "3 three",
        null
    ]
}

build grammar: 78.938µs; optimize: 18.004µs
initial lexer cost: regexps: 4 with 23 nodes (+ 0 derived via 0 derivatives with total fuel 151), states: 3; transitions: 0; bytes: 1862; alphabet size: 14
prompt: ""
prompt+grm: "\""
ini_tokens: "\""
res_prompt: "\""

compute_mask()
parser_done: false; lexer_bytes: true; can_advance: true (eos:false); accept: false; empty_token_prefix: true
compute_mask
step-stats: 59us; 47 lex fuel; 0 items; regexps: 4 with 23 nodes (+ 5 derived via 10 derivatives with total fuel 198), states: 7; transitions: 40; bytes: 3267; alphabet size: 14
bias: (pref: ""; accpt: false; temp: 0.000) TokenSet: 3/128256; "1", "2", "3"
JSON-OUT: {"object":"text","str":"\"","hex":"22","log_prob":0.0,"num_tokens":1,"is_generated":false,"stats":{"runtime_us":96,"rows":1,"definitive_bytes":1,"lexer_ops":0,"num_lex_errors":0,"num_lexemes":0,"all_items":4,"lexer_cost":198,"compute_time_us":56}}

commit_token("2") at #1
parser_done: false; lexer_bytes: true; can_advance: true (eos:false); accept: false; empty_token_prefix: true
JSON-OUT: {"object":"text","str":"2","hex":"32","log_prob":0.0,"num_tokens":1,"is_generated":true,"stats":{"runtime_us":1598349,"rows":0,"definitive_bytes":1,"lexer_ops":0,"num_lex_errors":0,"num_lexemes":0,"all_items":0,"lexer_cost":0,"compute_time_us":0}}

also when the schema is const the output seems to be empty


import helpers from tslib.es6.js when module is >= es6 and moduleResolution = node

Currently Node supports ES6 modules behind the flag --experimental-modules. It also supports customizing the module resolution. Just like TypeScript has compiler options that change the emit output.
When I set the module compiler option is to something newer than es5 (like es6 or esnext) and I set moduleResolution to node, I can run a module as follows and it all works out fine:
node --experimental-modules --es-module-specifier-resolution=node ./path/to/module.js

However when I enable the importHelpers option, the following import is emitted:
import * as tslib_1 from "tslib";
// code is calling these helpers like so:
tslib_1.__decorate(...) // "TypeError: tslib_1.__decorate is not a function" because tslib_1 === { default: { __decorate: ... } }

I think using the file at node_modules/tslib/tslib.es6.js would be sufficient.
import * as tslib_1 from "tslib/tslib.es6.js"; // I think this would do it

Related to https://github.com/microsoft/tslib/pull/44

I believe this is resolved by https://github.com/microsoft/tslib/pull/126. The latest version of tslib supports NodeJS conditional exports and will import tslib.es6.js automatically.


migration fail with unable to find parent lfn

this is for migration inserted today, after all fixes.
e.g. migrationId 3348710
[2022-08-30 15:48:58.227060473 +0000 UTC m=+63798.146615751] migrate.go:1335: update migration request 3348710 to status 9
I deleted it and created a new one for same block, 3351829
same error
[2022-08-30 20:09:07.804204816 +0000 UTC m=+784.055890124] migrate.go:1114: insert bulkblocks for mid 3351829 error DBSError Code:101 Description:DBS DB error Function:dbs.bulkblocks.InsertBulkBlocksConcurrently Message:unable to find parent lfn /store/mc/Run3Summer21DRPremix/DYToLL_M-50_TuneCP5_14TeV-pythia8/GEN-SIM-DIGI-RAW/120X_mcRun3_2021_realistic_v6-v2/80001/71031b41-0fe1-4594-9177-f304ca501173.root Error: nested DBSError Code:103 Description:DBS DB query error, e.g. mailformed SQL statement Function:dbs.GetID Message: Error: sql: no rows in result set
and now it is in state 9 again:
[crab3@crab-prod-tw01 migrations]$ scurl  https://cmsweb-prod.cern.ch:8443/dbs/prod/phys03/DBSMigrate/status?migration_rqst_id=3351829
[
{"create_by":"/DC=ch/DC=cern/OU=computers/CN=tw/crab-prod-tw01.cern.ch","creation_date":1661890111,"last_modification_date":1661890111,"last_modified_by":"/DC=ch/DC=cern/OU=computers/CN=tw/crab-prod-tw01.cern.ch","migration_input":"/DYToLL_M-50_TuneCP5_14TeV-pythia8/Run3Summer21DRPremix-120X_mcRun3_2021_realistic_v6-v2/AODSIM#a4092e5b-7ae6-4788-b07f-ed9959d39f92","migration_request_id":3351829,"migration_server":"dbs2go-phys03-migration-566cc878db-ldstl","migration_status":9,"migration_url":"https://cmsweb-prod.cern.ch/dbs/prod/global/DBSReader","retry_count":4}
]

btw there is no migration failure reported in dashboard
https://monit-grafana.cern.ch/d/kJOvR2h7k/dbs2go?orgId=11&var-Instance=migration&var-Env=All&var-Host=All&var-Apod=All
which looks a but to me.

I removed all failed migrations again, and now all blocks are properly migrated.
I suspect that somehow parents migrations were delayed with respect to child. Last night there was a very large amount of migrations going on at same time as I cleared the backlog. Now that we are in normal situation this is likely not going to happen again.
Currently we do no observe any issue.
I am not closing this, in case when @vkuznet comes back he wants to check that things happen with proper before-after relation.
Valentin, feel free to close at your discretion. I am not a fan of chasing un-reproducible problems.

hmm... it is happening again:
[2022-08-31 10:51:43.066426904 +0000 UTC m=+53739.318112213] migrate.go:1114: insert bulkblocks for mid 3357277 error DBSError Code:101 Description:DBS DB error Function:dbs.bulkblocks.InsertBulkBlocksConcurrently Message:unable to find parent lfn /store/data/Run2022C/JetMET/RAW/v1/000/356/578/00000/035fde56-6455-4cb8-9c5b-ba02e7526c95.root Error: nested DBSError Code:103 Description:DBS DB query error, e.g. mailformed SQL statement Function:dbs.GetID Message: Error: sql: no rows in result set
[2022-08-31 10:51:43.067479921 +0000 UTC m=+53739.319165231] migrate.go:1373: update migration request 3357277 to status 3
	'3357277'
[2022-08-31 10:51:43.14844369 +0000 UTC m=+53739.400128998] migrate.go:1125: updated migration request 3357277 with status 3
[2022-08-31 10:51:43.14891126 +0000 UTC m=+53739.400596595] migration_server.go:86: migration process map[migration_request_id:3357277 migration_request_url:https://cmsweb-prod.cern.ch:8443/dbs/prod/global/DBSReader] finished in 596.021373ms
[2022-08-31 10:52:42.542668214 +0000 UTC m=+53798.794353582] migration_server.go:72: process {MIGRATION_REQUEST_ID:3357277 MIGRATION_URL:https://cmsweb-prod.cern.ch:8443/dbs/prod/global/DBSReader MIGRATION_INPUT:/JetMET/Run2022C-PromptReco-v1/MINIAOD#1c30cf46-c86b-40a4-b175-0a06d9e8eacc MIGRATION_STATUS:1 MIGRATION_SERVER:dbs2go-phys03-migration-566cc878db-ldstl CREATE_BY:/DC=ch/DC=cern/OU=computers/CN=tw/crab-prod-tw01.cern.ch CREATION_DATE:1661942888 LAST_MODIFIED_BY:/DC=ch/DC=cern/OU=computers/CN=tw/crab-prod-tw01.cern.ch LAST_MODIFICATION_DATE:1661942888 RETRY_COUNT:4}
[2022-08-31 10:52:42.542868832 +0000 UTC m=+53798.794554142] migrate.go:1373: update migration request 3357277 to status 9

We will keep removing and re-inserting, which seems to cure.

Stefano, I had a look at failed block /DYToLL_M-50_TuneCP5_14TeV-pythia8/Run3Summer21DRPremix-120X_mcRun3_2021_realistic_v6-v2/AODSIM#a4092e5b-7ae6-4788-b07f-ed9959d39f92 and I was able to insert it successfully into my dev setup. So I doubt it is an issue with migration server per-se. Said that, what I fear is that it is an concurrency issue (or better say order one) where some blocks (may be from the same dataset) may share some information (e.g. I do not know if block-lfn relationship is always unique and if not it is an issue with order of parent file insertion). This can explains what you saw, i.e. with large backlog we got some failures, and when you resubmit them they proceed fine. I need time to think about it and will comeback to this issue once I back in town next week.

I have found at least one case where the parent block migration was attempted and failed with old server and thus needed cleanup. We are currently only removing failed migration discovered during publication process, i.e. for childs. At some point all old (before Aug 30) migrations should be removed and that may likely solve all problems.

finding those "migrations of parent failed earlier in August" is very cumbersome from where I am. I think it will be better to wait for you to be back and do an SQL query.  Otherwise we can possibly parse migration server log for "unable to find parent lfn". The action to do is to go from lfn to block, find the old failed migration for that block and remove it.

@belforte , I put in /afs/cern.ch/user/v/valya/public/DBS/status9.txt.gz the data with status=9. This is order list starting with creation_date, followed by migration_request_id and migation_input, i.e.
<PHONE_NUMBER>                70376 /SinglePhoton/Run2012D-v1/RAW#87f5ab72-2691-11e2-96c7-842b2b4671d8
<PHONE_NUMBER>                70466 /CMSSM_tanb-30_m0-2100to3000_m12-400to575_TuneZ2star_8TeV-pythia6/Summer12-START53_V19_FSIM_PU_S12-v1/AODSIM#dcc4a33c-a75b-11e3-b935-003048f0e38c
<PHONE_NUMBER>                80006 /MinBias_TuneZ2star_13TeV_pythia6/Fall13-POSTLS162_V1_castor-v4/GEN-SIM#791892c0-a004-11e3-90a8-003048f0e7dc
<PHONE_NUMBER>                80286 /TauParked/Run2012D-v1/RAW#c96bfa5c-10a2-11e2-ab8d-842b2b4671d8
<PHONE_NUMBER>                80309 /TauParked/Run2012D-v1/RAW#b3441f18-2545-11e2-96c7-842b2b4671d8
...

So, you can parse it and get input for creation_date of your choice, e.g.  the creation date<PHONE_NUMBER> is Aug 9th
date -d @1660000000
Tue Aug  9 01:06:40 CEST 2022

SO, you can get datasets which fails on Aug 9th and forward as simple as
zcat /afs/cern.ch/user/v/valya/public/DBS/status9.txt.gz | awk '{print $1,$2,$3}' | grep ^166

in total of 9466 datasets/blocks.

@belforte , @mapellidario do we need to keep this ticket open?

this was understood and solved. You can close. Thanks


Remove {% load url from future %} calls. — Fixes #119

This will break the 1.4 LTS version and will start supporting the new 1.8 LTS version.


Does this work anymore?

https://github.com/sferik/t/issues/458
It seems to me as with lot of problem not being able to authorize, this doesn't work anymore.

Works fine for me fwiw

Also having an auth issue

What is the structure of the .trc file?

Structure of two trc with two sets of users
---
profiles:
  <username>:
    <consumer_key>:
      username: <username>
      consumer_key: <consumer_key>
      consumer_secret: <consumer_secret>
      token: <api_token>
      secret: <api_secret>
  <second_user>:
    <second_user_key>:
      username: <second_user>
      consumer_key: <second_user_key>
      consumer_secret: <second_user_secret>
      token: <second_api_token>
      secret: <second_api_secret>
configuration:
  default_profile:
  - <username>
  - <consumer_key>
  shitposter:
  - <second_user>
  - <second_user_key>

I was using this last week and I upgraded so broekn now. Needs to be ruby 2.7 I think really. I patched the http issue and got another issue with Proc.new

I can't get it to work. I was able to generate config file following this comment, but I can't t update because of 'force_encoding': can't modify frozen String, even though #452 is closed as completed via sferik/twitter@0f8ff35c.
I've tried on Ruby 2.7.5, 3.0.4 and 3.1.2 via asdf.

I am trying to export all the people I follow to a .csv and it does not work no matter what I try. I give up.
C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/http-3.3.0/lib/http/response/body.rb:52:in force_encoding': can't modify frozen String: "" (FrozenError)
from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/http-3.3.0/lib/http/response/body.rb:52:in to_s'         from C:/Ruby32-x64/lib/ruby/3.2.0/forwardable.rb:234:in empty?'
from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/twitter-6.2.0/lib/twitter/rest/request.rb:37:in perform'         from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/twitter-6.2.0/lib/twitter/rest/utils.rb:50:in perform_request'
from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/twitter-6.2.0/lib/twitter/rest/utils.rb:72:in perform_request_with_object'         from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/twitter-6.2.0/lib/twitter/rest/utils.rb:57:in perform_get_with_object'
from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/twitter-6.2.0/lib/twitter/rest/users.rb:53:in verify_credentials'         from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/twitter-6.2.0/lib/twitter/rest/utils.rb:166:in user_id'
from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/twitter-6.2.0/lib/twitter/rest/utils.rb:161:in cursor_from_response_with_user'         from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/twitter-6.2.0/lib/twitter/rest/friends_and_followers.rb:30:in friend_ids'
from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/t-3.1.0/lib/t/cli.rb:317:in followings'         from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/thor-1.2.1/lib/thor/command.rb:27:in run'
from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in invoke_command'         from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/thor-1.2.1/lib/thor.rb:392:in dispatch'
from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/thor-1.2.1/lib/thor/base.rb:485:in start'         from C:/Ruby32-x64/lib/ruby/gems/3.2.0/gems/t-3.1.0/bin/t:20:in <top (required)>'
from C:/Ruby32-x64/bin/t:32:in load'         from C:/Ruby32-x64/bin/t:32:in '`


[LLVMCPU] Add conv2d nchw tiling to enable vectorization

@hanhanW I was thinking of adding a simple e2e conv nchw test to ensure that it's working in case upstream breaks some patterns. What are your thoughts? or do you think upstream tests for decomposition and vectorization it's safe enough? If not, where is a good place to add it, seems kind of awkward to put in any of the directory within tests/e2e 😅

I'm missing context but perhaps you can add a test to compiler/src/iree/compiler/Codegen/LLVMCPU/test and only run the applicable pipeline and match the resulting vector IR. You can take a look at transpose_avx2_lowering.mlir. It's doing something similar.

We'll need at least two tests here.

Add a test to materialize_x86_64_launch_configuration.mlir like this
Add an e2e test. You can add a test to xla_ops/convolution.mlir or add a new test file to tests/e2e/tosa_ops/.

Sounds good, for materializing launch config test I can do that.
However for the e2e test, xla/convolution is only for mhlo.convolution which is nhwc no? Looking at tosa ops it is also similar, it seems to be lowering to nhwc as seen here. Can I start a new directory for linalg convs to fill with nchw test?

I'm missing context but perhaps you can add a test to compiler/src/iree/compiler/Codegen/LLVMCPU/test and only run the applicable pipeline and match the resulting vector IR. You can take a look at transpose_avx2_lowering.mlir. It's doing something similar.

Thanks for the suggestion, I was thinking more in the line of e2e test for correctness, just because I think this conv2d nchw vectorization pass will be evolving very quickly through the next few weeks as we tune and tweak the passes to gain more performance and come closer to nhwc. But once we get to a stable point for the vectorization, we can add this :)

Yes, mhlo.convolution might not support NCHW lowering at this moment... Let's start a tests/linalg directory and put the test to there. (I'm not too worried about numerical issues because they should be caught in integration tests. I assume that it's enabled in SHARK Tank nightly tests.)

Yes, mhlo.convolution might not support NCHW lowering at this moment... Let's start a tests/linalg directory and put the test to there. (I'm not too worried about numerical issues because they should be caught in integration tests. I assume that it's enabled in SHARK Tank nightly tests. It's still a good thing to do.)

Sounds good! I was thinking would be also good for quick test when we develop more conv2d vectorizations.

@hanhanW added the test, lmk what you think :)


Initial settings for labeler, templates, workflows

Docs Build status updates of commit 070f587:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.ghal.rules.json
:white_check_mark:Succeeded

.github/ISSUE_TEMPLATE/config.yml
:white_check_mark:Succeeded

.github/ISSUE_TEMPLATE/doc-issue.md
:white_check_mark:Succeeded

.github/ISSUE_TEMPLATE/docs-request.md
:white_check_mark:Succeeded

.github/ISSUE_TEMPLATE/dotnet-breaking-change.md
:white_check_mark:Succeeded

.github/PULL_REQUEST_TEMPLATE.md
:white_check_mark:Succeeded

.github/no-response.yml
:white_check_mark:Succeeded

.github/workflows/bcnotify.yaml
:white_check_mark:Succeeded

.github/workflows/build-validation.yml
:white_check_mark:Succeeded

.github/workflows/dependencies/DotnetDocsTools.LocateProjects.1.0.8.nupkg
:white_check_mark:Succeeded

.github/workflows/dependencies/Get-MSBuildResults.ps1
:white_check_mark:Succeeded

.github/workflows/dependencies/Out-GithubActionStatus.ps1
:white_check_mark:Succeeded

.github/workflows/markdownlint-problem-matcher.json
:white_check_mark:Succeeded

.github/workflows/markdownlint.yml
:white_check_mark:Succeeded

.gitignore
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


faster dataloader

I changed DataLoader.loadMany to create only a single promise instead of O(n), and it reduced memory usage by a significant amount
Ran this against our integration test suite and everything worked great
Gonna try to run this against the dataloader test suite against this as well

The only breaking change (I believe) I made is that maxBatchSize behaves a bit differently; will see if I can fix this.
BEFORE
===== Results =====
orgSize batchSize sampleIndex latency(s) usr-cpu(s) sys-cpu(s) heapUsed(mb) minHeapNeeded(mb) maxPrmCntActive maxPrmCntInMem totPrmCnt avgEllMS p90EllMS p99EllMS maxEllMS
300     1000      0           10         15.776     0.976      863.8        870.4             1243524         1202098        1496290   789      3555     5255     5355
300     1000      1           9.8        14.768     0.984      648.1        654.9             1243746         1398456        1496249   731      3236     5036     5136
300     1000      2           10.4       15.168     0.944      624.4        631.4             1252455         1430316        1528216   805      3600     5400     5500
300     1000      3           10.1       15.088     0.792      652.3        655.3             1248241         1416718        1512412   820      3615     5415     5515
300     1000      4           10.9       15.552     0.836      655.1        657.3             1245289         1403847        1501508   989      4206     6006     6206
300     1000      5           11.3       15.804     0.824      644.3        649.3             1258445         1427909        1549688   1082     4546     6346     6546
300     1000      6           11.2       15.88      0.784      710.8        716.4             1241243         1387790        1485766   1141     4721     6521     6721
300     1000      7           11.9       16.612     0.872      753.6        756.5             1254319         1438214        1533612   1183     4848     6748     6948
300     1000      8           13.3       18.44      0.896      958.6        938.9             1252403         1409395        1528248   1653     6289     8289     8489
300     1000      9           11.3       16.728     0.684      643          646.7             1257259         1389457        1544147   930      3992     5792     5992

AFTER
===== Results =====
orgSize batchSize sampleIndex latency(s) usr-cpu(s) sys-cpu(s) heapUsed(mb) minHeapNeeded(mb) maxPrmCntActive maxPrmCntInMem totPrmCnt avgEllMS p90EllMS p99EllMS maxEllMS
300     1000      0           6.5        11.652     0.884      514.2        509.5             111295          108568         236557    365      1818     3218     3318
300     1000      1           6          10.368     0.748      438.4        431.2             111589          136653         237056    337      1670     3070     3170
300     1000      2           6.4        10.24      0.892      470.1        452.4             113189          187717         239496    379      1863     3263     3363
300     1000      3           5.5        10.244     0.732      372.3        368.4             112011          144712         237326    359      1734     3134     3234
300     1000      4           6.1        10.036     0.62       420.5        409               112685          168874         239624    340      1701     3101     3201
300     1000      5           6.1        10.416     0.772      435.4        424.2             111360          106222         235897    326      1617     3017     3117
300     1000      6           6.2        10.6       0.768      425.3        412.2             112091          127949         236891    385      1904     3304     3404
300     1000      7           6.3        10.368     0.84       431.4        416.8             111417          117292         236515    339      1690     3090     3190
300     1000      8           6.5        10.74      0.88       451.3        437.9             112486          112218         237637    387      1933     3333     3433
300     1000      9           6.2        10.436     0.74       435          421.8             111893          129313         236824    341      1677     3077     3177

Note: the results above are with promise counting and async hooks turned on. However, even with async hooks and promise counting turned off (below), heap usage is reduced by about 25%. (In the results below, ignore latency- it's inaccurate because I had to turn off async hooks and we rely on async hooks to determine when the process is idle).
Before
[$TROOT]*(jon) cp node_modules/dataloader/index_original.js node_modules/dataloader/index.js && sync_file node_modules/dataloader/index.js && c exec more/perf_tests/CreateBigOrg.test.js
===== Results =====
orgSize batchSize sampleIndex latency(s) usr-cpu(s) sys-cpu(s) heapUsed(mb) minHeapNeeded(mb) avgEllMS p90EllMS p99EllMS maxEllMS
500     1000      0           23.9       25.292     1.772      2375.6       2360.8            1764     7468     10368    10668
500     1000      1           25.6       27.4       1.936      1723.5       1697.2            1682     7190     10390    10690
500     1000      2           26.4       27.756     1.84       1732.8       1699.4            1606     7045     10245    10545
500     1000      3           26.5       31.548     1.956      1700.9       1702.2            1599     6969     10169    10469

After
cp ../dataloader/dist/index.js node_modules/dataloader/index.js && sync_file node_modules/dataloader/index.js && c exec more/perf_tests/CreateBigOrg.test.js
orgSize batchSize sampleIndex latency(s) usr-cpu(s) sys-cpu(s) heapUsed(mb) minHeapNeeded(mb) avgEllMS p90EllMS p99EllMS maxEllMS
500     1000      0           27.6       29.036     2.44       1845.5       1798.2            1206     5630     8930     9230
500     1000      1           26.4       33.208     1.968      1401.2       1362.1            1398     6370     9570     9870
500     1000      2           26.4       32.972     1.964      1397.8       1357.6            1344     6170     9370     9670
500     1000      3           26.2       32.848     1.92       1387.7       1357.2            1365     6226     9426     9726

Nice! Also were you able to retest the perf results after fixing the batch/key param issue?
I think that before, in __prepOneKey, key was always undefined, which means we always returned the same valueIndex in that function? Not sure how that might affect things

Ah yes. Sorry, I was switching between coding in this repo and coding in a temp (pre-built) file which I would c sync to cloud-dev node modules, so the code in this PR wasn't actually reflecting the code that was running.

See https://github.com/ThreadsHQ/Web/pull/7471/files instead


feat: Allow overriding Gateway API version

Description of the change

Removed

Fixed

Added

Allows to override the default Gateway API version used in the route object.
Changed

Benefits

Possible drawbacks

Applicable issues

fixes #

Additional information

https://github.com/kubernetes-sigs/gateway-api/releases/tag/v0.8.0
Version 0.8.0 of Gateway API drops v1alpha2 version for Gateway, GatewayClass, and HTTPRoute.
Checklist

[x] Title of the PR conforms to the Conventional Commits standard.
[x] Scope of the of the PR title contains the chart name.
[x] Chart version in Chart.yaml has been bumped according to Semantic Versioning.
[x] Chart artifacthub.io/changes changelog annotation has been updated in Chart.yaml. See Artifact Hub documentation for more info.
[x] Variables have been documented in the values.yaml file.

@bjw-s should I rebase this into the rewrite branch instead ?
WDYT of updating the default to v1beta1 version ? The TCP/UDP along with some other types still use v1alpha2, so its likely useful to keep it configurable.

I'm going to be merging the rewrite branch into development tonight or tomorrow. Then I will use development as a staging area to update docs etc before the initial release of 2.0.

@bjw-s thanks, rebased, should we take the opportunity of the major bump and change the default API version to v1beta1 ?

@bjw-s thanks, rebased, should we take the opportunity of the major bump and change the default API version to v1beta1 ?

I'm definitely not against bumping the version. But since I don't use the Gateway API yet I have no idea about any other potential implications of the change, which is why I'm a bit hesitant to make it configurable through the values.yaml

I'm definitely not against bumping the version. But since I don't use the Gateway API yet I have no idea about any other potential implications of the change, which is why I'm a bit hesitant to make it configurable through the values.yaml

We could bump it directly, however it would break the non-http types (routeKind) since they are only available in v1alpha2.
Basically the >= 0.8.0 spec dropped HTTPRoute from v1alpha2 and is now exclusively available in v1beta1.
Spec at https://gateway-api.sigs.k8s.io/references/spec/#api-specification
Depending on what version of Gateway API CRDs someone is using, they will need different API versions to get it working.
Alternatively we could try to check capabilities and set the version automatically, WDYT ?

Alternatively we could try to check capabilities and set the version automatically

Something like:
  {{- $routeKind := $routeObject.kind | default "HTTPRoute" -}}
  {{- $apiVersion := "gateway.networking.k8s.io/v1alpha2" -}}
  {{- if $rootContext.Capabilities.APIVersions.Has (printf "gateway.networking.k8s.io/v1beta1/%s" $routeKind) }}
    {{- $apiVersion = "gateway.networking.k8s.io/v1beta1" -}}
  {{- end -}}

I'd be cool with a solution like that, that would keep it relatively clean. Hopefully those APIs reach v1 relatively soon to get all the versions aligned again.

@bjw-s updated to check capabilities.

Thanks for this, I've merged in to development so it should be in the next beta soon


Fixed Mark as complete

PR Fixes:

Mark as complete feature fixed

Resolves #623
Checklist before requesting a review

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

already fixed


BZ1248978: Prevent NPE's in Bpmn2JsonMarshaller.java caused by DataOu…

…tputAssociations referencing renamed or deleted process variables.

@jlindop is this change still needed? If so, would it be possible to add a test case?

@psiroky - No, it's not required - I'll close this PR. Thanks for the reminder!


🚀 [Feature] : Covert it to svelte components with the same design

Is your feature request related to a problem? Please describe.
I am looking to convert a single index.html file into Svelte components while maintaining the same design. This will allow for better component management, reusability, and easier maintenance.
Describe the solution you'd like
I would like the index.html file to be broken down into individual Svelte components, with each part of the HTML being converted into a corresponding Svelte component. The resulting Svelte components should retain the same design and functionality as the original HTML file.
Describe alternatives you've considered
An alternative could be to use another JavaScript framework like React or Vue, but Svelte is preferred due to its simplicity and performance benefits.
Additional context
The index.html file contains the entire structure and styling for the current design. Converting it to Svelte components should preserve the existing layout and styles while enhancing the codebase's modularity. Screenshots or additional context can be provided if needed.
If you want speed up process of this issue, please send 🚀 as a reaction.

@jakebogan01 , Are you interested in ?

Optional: If you think that tailwind css fits here well, you also can implement it here.

@xuelink Yeah I can see what I can do next week with this 👍

@xuelink Yeah I can see what I can do next week with this 👍

Going to be awesome ! :) How much you can do im ok then, I can join your PR as well.
Feel free to add this website to your portfolio ;) Thanks you again @jakebogan01

@xuelink No problem, I'll start on it tomorrow

@xuelink I made a PR here However, I wasn't able to finish the main titles and animation. Things like SplitText I don't have access to, in order to use it as a module

@xuelink I made a PR here However, I wasn't able to finish the main titles and animation. Things like SplitText I don't have access to, in order to use it as a module

So from what I understand, those modules like SplitText are just in the previous website, but we'd need a special lib for it to work with Svelte?
Or we coule also just code it all from scratch :D

@xuelink I made a PR here However, I wasn't able to finish the main titles and animation. Things like SplitText I don't have access to, in order to use it as a module

So from what I understand, those modules like SplitText are just in the previous website, but we'd need a special lib for it to work with Svelte?
Or we coule also just code it all from scratch :D

Without adding special lib, can we do as components with html and css ? if its not gonna be, i can close that issue that we can contiue with simple HTML and CSS with index.html not a big deal.

@xuelink I made a PR here However, I wasn't able to finish the main titles and animation. Things like SplitText I don't have access to, in order to use it as a module

So from what I understand, those modules like SplitText are just in the previous website, but we'd need a special lib for it to work with Svelte?
Or we coule also just code it all from scratch :D

Without adding special lib, can we do as components with html and css ? if its not gonna be, i can close that issue that we can contiue with simple HTML and CSS with index.html not a big deal.

Yeah, that actually sounds pretty good. We may look into the special libraries later, but now just get the basics working.

@xuelink I made a PR here However, I wasn't able to finish the main titles and animation. Things like SplitText I don't have access to, in order to use it as a module

So from what I understand, those modules like SplitText are just in the previous website, but we'd need a special lib for it to work with Svelte?
Or we coule also just code it all from scratch :D

Without adding special lib, can we do as components with html and css ? if its not gonna be, i can close that issue that we can contiue with simple HTML and CSS with index.html not a big deal.

Yeah, that actually sounds pretty good. We may look into the special libraries later, but now just get the basics working.

OK, When it will be in case later, we can take a look here again but for now, i am also closing this issue as well.


Black Box when mouse over on non-open tab in Editor

Godot version
v4.0.beta8.official [45cac42c0]
System information
Ubuntu  20.04.5 LTS  - Nvidia GeForce GTX 960M - Vulkan
Issue description
When mouse over a tab in the Game Editor, looks like instead of showing a hint something is broken and it shows a black box instead:

Steps to reproduce

Create new project
Save scene, give it any name, this is important, only happens when is saved
Click in new scene (plus + sign on tabs), it will create a new tab
Once on the new scene opened, mouse over the previous tab with the first created and just saved scene
You'll see the black box

Minimal reproduction project
N/A

You'll see the black box

I think it's called scene preview. Sometimes it's showed incorrectly.

这个应该是场景预览，被预览的场景中有可见的东西时鼠标悬浮上去就可以在小窗口中看到，如果原场景的节点不是可显示的就是个小黑框。

Duplicate of https://github.com/godotengine/godot/issues/30439 (same cause).


Compiled tkfxo file with tkfxc.exe is not loaded.

After downloading SharpDX-SDK-2.6.3, I compiled Inverted.fx with DIrectX11-net40\tkfxc.exe.
Inverted.fx file is used at following sample project.
http://developer.nokia.com/community/wiki/Creating_a_Lens_application_that_uses_HLSL_effects_for_filters
I changed LIB/ARM/. with DirectX11_1-WP8-ARM/..
and changed Content/Inverted.tkfxo with new built Inverted.tkfxo.
It cause run time error. "could not find asset." at following code:
inversionEffect = Content.Load("Inverted.tkfxo");

The way to use it is to compile with the msbuild action ToolkitFxc as it is done for all toolkit samples. tkfxc is generating a filename with an extension while the Content manager is not using it


subsonic: init at 5.2.1

Add a package and NixOS service for the Subsonic media streamer, version 5.2.1, by downloading its tarball from the Sourceforge download link on the Subsonic site. The tarball includes a wrapper script to pass the right Java arguments to the server, but I've decided to run the server directly as a systemd service without the wrapper to remove the need to run it as a forking service and to more easily capture the server's logging output on standard error for the journal. I've tested this by installing and running it on my own system.

Don't forget to rename commits as it said in CONTRIBUTING.md.

Do you want me to squash everything down to one commit?

You can left Add... commits. And squash others. But also rename them to a proper format.

I believe I've made all the changes you requested.


⚠ Sinister has degraded performance

In cca8659, Sinister (http://sinister.ly/index.php) experienced degraded performance:

HTTP code: 200
Response time: 27337 ms

Resolved: Sinister performance has improved in 7c7f0ed.


Allow calling processEvents() from listener callbacks

Currently such pending events are passed to PendingEventHandler and there are three options:

to throw exception in this case (default)
ignore such events
store them in user managed queue (user is responsible for calling processEvent for them when current processing completes)

Such queue may be implemented on library side allowing processing of pending events by default.

Done in https://github.com/nsk90/kstatemachine/releases/tag/v0.13.0


add support for readonly in operator

What changes are proposed in this pull request?
add support for read-only flag in operator config. Readonly flag lets you indicate if an operator only perform read only actions
Usage:
Python:
class MyPyOperator(foo.Operator):
    @property
    def config(self):
        return foo.OperatorConfig(
            name="my_py_operator",
            label="My Python Operator",
            read_only=True # Indicates that operator only performs read-only actions
        )
    # ...rest of operator implementation

JavaScript
class MyJSOperator extends Operator {
  get config() {
    return new OperatorConfig({
      name: 'my_js_operator',
      label: 'My JavaScript Operator',
      readOnly: true // Indicates that operator only performs read-only actions
    })
  }
  // ...rest of operator implementation

How is this patch tested? If it is not, please explain why.
Interactively within the app + vitests
Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[ ] No. You can skip the rest of this section.
[ ] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[ ] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

Discussed offline. No longer required. Closing.


How to seed your data in your tests

Currently in the Django instance we're manually creating our data that we're testing against.
https://github.com/kjaymiller/cookiecutter-relecloud/blob/911bf6ca37211325c909c6b22ee5ae479c6c803d/{{cookiecutter.__src_folder_name}}/tests/test_playwright.py#L59-L92
We need to create fixtures (for each web framework) that seeds a transactional database (for live server)
Seeding Data in Django
You can call the loaddata from django.core.management and then the db setup and blocker from pytest-django
@pytest.fixture(scope="session")
def django_db_setup(django_db_setup, django_db_blocker):
    with django_db_blocker.unblock():
        call_command("loaddata", "seed_data.json")

Currently working and will be updated in in upcoming PR


added the class heading-text and in dark mode css change its colour

Added the class heading-text to the heading Quotes and in the css changed its colour for the dark mode to #ddd that is same as the colour for the quotes in the dark mode. This is done for better readability

to clarify this if before and after of the page
before :

after:

ok, thanks, I'll merge it soon..

@all-contributors please add @Ramya-Clg for design


Logstash Grok::PatternError: pattern %{SNORT} not defined

Describe the bug
Data does not flow to elasticksearch.
To Reproduce
Configured by default. Changed only ip Pfsence and maxmind added in docker. In logs logstash See error
[ERROR] 2020-06-10 08:57:49.898 [[main]-pipeline-manager] javapipeline - Pipeline aborted due to error {:pipeline_id=>"main", :exception=>#<Grok::PatternError: pattern %{SNORT} not defined>, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/jls-grok-0.11.5/lib/grok-pure.rb:123:in block in compile'", "org/jruby/RubyKernel.java:1442:in loop'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/jls-grok-0.11.5/lib/grok-pure.rb:93:in compile'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-filter-grok-4.3.0/lib/logstash/filters/grok.rb:288:in block in register'", "org/jruby/RubyArray.java:1809:in each'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-filter-grok-4.3.0/lib/logstash/filters/grok.rb:282:in block in register'", "org/jruby/RubyHash.java:1415:in each'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-filter-grok-4.3.0/lib/logstash/filters/grok.rb:277:in register'", "org/logstash/config/ir/compiler/AbstractFilterDelegatorExt.java:75:in register'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:216:in block in register_plugins'", "org/jruby/RubyArray.java:1809:in each'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:215:in register_plugins'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:521:in maybe_setup_out_plugins'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:228:in start_workers'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:170:in run'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:125:in block in start'"], "pipeline.sources"=>["/usr/share/logstash/etc/logstash/conf.d/01-inputs.conf", "/usr/share/logstash/etc/logstash/conf.d/05-firewall.conf", "/usr/share/logstash/etc/logstash/conf.d/10-others.conf", "/usr/share/logstash/etc/logstash/conf.d/20-suricata.conf", "/usr/share/logstash/etc/logstash/conf.d/25-snort.conf", "/usr/share/logstash/etc/logstash/conf.d/30-geoip.conf", "/usr/share/logstash/etc/logstash/conf.d/40-dns.conf", "/usr/share/logstash/etc/logstash/conf.d/45-cleanup.conf", "/usr/share/logstash/etc/logstash/conf.d/50-outputs.conf"], :thread=>"#<Thread:0x66ea3b06@/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:121 run>"}
[ERROR] 2020-06-10 08:57:49.913 [Converge PipelineAction::Create] agent - Failed to execute action {:id=>:main, :action_type=>LogStash::ConvergeResult::FailedAction, :message=>"Could not execute action: PipelineAction::Create, action_result: false", :backtrace=>nil}
Screenshots
kibana
https://www.dropbox.com/s/xwl1x9578mfdpfo/Снимок.PNG?dl=0
Operating System (please complete the following information):

OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
Linux 4.19.0-9-amd64 x86_64
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Version of Docker (docker -v):
Docker version 19.03.11, build 42e35e61f3

Version of Docker-Compose (docker-compose -v):
docker-compose version 1.26.0, build unknown
Elasticsearch, Logstash, Kibana (please complete the following information):

Version of ELK (cat /docker-pfelk/.env)
ELK_VERSION=7.7.0
**Service logs

docker-compose logs pfelk01

docker-compose logs pfelk02

docker-compose logs pfelk03

docker-compose logs logstash

docker-compose logs kibana
https://www.dropbox.com/s/r4knplbwaxkwi6e/logs.zip?dl=0
Additional context
Add any other context about the problem here.

@SaymonDzen - thanks and I’ll test and troubleshoot this within the week.
Initially, it appears there may be an issue with the setup more so an issue communicating with elastic.  The error indicating the referenced snort pattern is missing and likely a missing or misplace file location of the grok pattern.

this issue resolved!


TST: stats.studentized_range: fix incorrect test

Reference issue
Closes gh-17124
What does this implement/fix?
gh-17124 reported a failure in scipy.stats.tests.test_distributions.TestStudentizedRange.test_ppf_against_tables. The test would have always failed when executed on its own, but the failure was hidden: it is supposed to loop over an iterator that is an attribute of the class, but that iterator is exhausted after running another test.
This PR corrects the test, which passed the arguments to studentized_range.ppf in the wrong order and had too tight a tolerance. The coarse tolerance required for the test to pass is understandable, considering the low precision of the reference table.

Thanks Tyler!


Log the correct url when the 'https' option is specified.

Currently, the log entry that outputs the server address has http:// hard coded. This uses the opt.https option to log https:// when applicable.

I'm trying to submit a PR improving this commit, currently it still logs https:// even with we set opt.https:  false, but am receiving permission denied.

remote: Permission to AveVlad/gulp-connect.git denied to BernardoMariano.
fatal: unable to access 'https://github.com/AveVlad/gulp-connect.git/': The requested URL returned error: 403


[TrafficManager] Prepare 1.1.0-beta.1 release

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.TrafficManager