Update for Vuetify 2

Not sure when you were planning on updating to Vuetify 2.  The only real change is a minor adjustment to the activator for the menu in the datepicker.  Here is a fix, if you are interested in updating I can submit a PR.
https://github.com/praveenpuglia/vuetify-daterange-picker/compare/master...user3483203:master

It also uses scss and stylus. That bit needs to change too.

I feel ya, no pressure.  I'm pretty sure I fixed all of the issues with the new scss as well in that commit.  I've been using it in my projects that were previously on vuetify ~1.5 and it seems to be working well.

Hey, @praveenpuglia . I have an interest in this update. Can I help you?

Hey @Adrear - I would love some support. Absolutely feel free to send a PR and I'll help you the best I can. :)

@paolog22 how you make it work?
I have an error The activator slot must be bound, try '<template v-slot:activator="{ on }"><v-btn v-on="on">'

just wanna share and thanks for this project vue + vuetify (latest release v2.2.4) + typescript

Where can i find your updated version

@praveenpuglia can i contribute? @govza @wackyapps sorry guys i left the company i was working with this project and the codebase are also left. but i am willing to support this project .

@paolog22 sure. Feel free to contribute and make it your own

NP @paolog22 , I ended up using only Vuetify to create preset. codesandbox

Is it now compatible with Vuetify 2 and Vue 2?


dist/polyfill.min.js missing v8.1.2 fix

@taylorhakes, your commit https://github.com/taylorhakes/promise-polyfill/commit/03f6f9a0d19e721b4167fdafbe96f0418718a12a that later has been released as v8.1.2 in missing in dist/polyfill.min.js, it should be updated accordingly too.

Fixed. Thanks for the bug report


Apotheosis + EMI

Apotheosis-1.19.2-6.4.1.jar
Emi-1.1.1+1.19.2+forge.jar
Superimposing attribute characteristics on top of an EMI Recipe book

This is on Apotheosis's end, there seems to be no exclusion area at all present so EMI doesn't know to move.


How to select text/copy messages to clipboard?

Hello, I am having issues copying the text from messages to the clipboard. What is the best practice for this?
I have tried wrapping my DashChat inside a SelectableArea() and also using Clipboard.setData() with no luck. Any advice would be appreciated!

What works for me is the following:
onLongPressMessage: (ChatMessage message) =>           Clipboard.setData(ClipboardData(text: message.text))

I'm closing it, let me know if your need more help

Hi @SebastienBtr
I am having issues implementing this, where would I place:
onLongPressMessage: (ChatMessage message) => Clipboard.setData(ClipboardData(text: message.text))

Also, could I apply this to an icon next to the text of the avatar icon?
Any help would be greatly appreciated.


want to know about keywords and contentUrl

I am using google_mobile_ads and there I see  keywords and contentUrl parameter in AdRequest.
Can anyone please help me like what are these, how to use it correctly and is it necessary to use??
Thanks.

The documentation could be explained in the readme as well
https://github.com/googleads/googleads-mobile-flutter/blob/eb4da7b039e6e82d21840d07cccea1170b388c5c/packages/google_mobile_ads/lib/src/ad_containers.dart#L160-L162

keywords are words or phrases describing the current user activity such as "Sports Scores" or "Football". Set this property to null or nil to clear the keywords.

How to manage your keywords.
Tips for building a keyword list

When requesting an ad, apps may pass the URL of the content (contentUrl) they are serving. This enables keyword targeting to match the ad with the content.

For example, if your app is requesting an ad while showing content from https://awesome.new.idea, you can pass this URL to target keywords relevant to the content (thus helping the publisher / developer a bit, with the keyword list).


Deploy site x to IPNS when site x source is updated in github

When we update a project's source in github, we would like to deploy it via IPNS to (some path at or subdomain of) ipfs.io.
The first project we use project-repos.ipfs.io (https://github.com/ipfs/project-repos/issues/9) as the first test case.  In the steps below, we call this generically PROJECT.
Steps:

[ ] name a new repo: proposed: deployer -- please propose other names in this thread
[ ] create the above repo, with me as an admin plz
[ ] deployer creates/starts an IPFS node on startup
[ ] deployer sets peer ID and private key from env vars (optional)
[ ] deployer receives github hooks, for all repos in IPFS org (or just for specific repos)
[ ] deployer recognizes updates to master branch of PROJECT
[ ] deployer executes build command, ideally a universal command that can work for all repos.  Propose: make build, which might delegate to the project's build, eg npm run build
[ ] deployer build's output is ideally in a consistent place.  Propose: ./dist/
[ ] deployer copies build output contents to the directory publish/PROJECT.
[ ] deployer runs ipfs add -r publish.
[ ] deployer publishes the resulting hash to IPNS, so PEER_ID/PROJECT now contains the project files
[ ] only one time for each project, someone directs a subdomain or path of ipfs.io to PEER_ID/PROJECT.

I expect to reuse most of this code for the deployer.

Alternatively, as @jbenet pointed out in https://github.com/ipfs/project-repos/pull/11#issuecomment-163578826, we could do the building on CI, and just pass the hash of PROJECT/dist to our own deployer server, which could then publish to IPNS.

@lierth can you lay out what you are doing to publish the blog on ipns?  What are the steps, be they manual or scripted?

this sounds pretty good :+1:

@lgierth can you lay out what you are doing to publish the blog on ipns? What are the steps, be they manual or scripted?

The reason I ask is in an attempt to de-duplicate deployment pathways, and in order to understand all the moving parts around this.

I will leave this open, but putting on the back burner for now.  project-repos is going to use a workaround.
IMO, We need a unified strategy for how we deploy all of the sites from our org to IPFS/IPNS, whether as outlined above or some other strategy.

Jenkins is now deploying stuff to IPFS and updates dnslinks -- examples: ipfs/website ipfs/docs


Move cluster validator out of test framework

Issue #, if available:
#1015

Description of changes:
This PR is the first part addressing the issue linked above. It moves the cluster validator out of the test framework in addition to one of the validations. Additionally, it contains some refactoring changes that further decouple the cluster validator related logic from the e2e tests.
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold
I think it probably makes sense to move and write unit tests for the existing validations in this one PR

/test eks-anywhere-release-tooling-test-presubmit

/approve


Moved the search bar display into the fetch callback. We should only …

…display a search bar if we set the hidden property and we have folder items.

Verified that @jdizoglio has signed the CLA. Thanks for the pull request!

+2 LGTM
:bouquet:


Implement visual component for setting up the board

04e139bb2561f5a35bbe4b56da9e97fe144ba652

e182eb739af27500ca31b6e88d0a6384eb4cef30

68755370c2d2a2af19770f4c610159c35f74cb31
Created the visual component of piece, square and board


Convert setup.py to pyproject.toml

Fixes https://github.com/egeakman/python-docs-bootstrapper/issues/4.
I used two tools for this:

https://github.com/gvalkov/setuptools-py2cfg
https://github.com/abravalheri/ini2toml

I used the first to convert setup.py to setup.cfg, and the second from setup.cfg to pyproject.toml, something like this:
pip install setuptools-py2cfg ini2toml
setuptools-py2cfg setup.py > setup.cfg
ini2toml setup.cfg > pyproject.toml
rm setup.*

Next, I added a few more pre-commit hooks, one to format pyproject.toml to make it easy to compare against other projects, and some others to check TOML and YAML files.
Then to check the output is okay, I ran:
pip install build
python -m build

Which creates an sdist and wheel in the dist directory. I compared the output from master and from this branch, and there were no unexpected differences.
We're still using setuptools here as the "build backend", which is just fine. We can also easily change it to others too. I tend to use hatchling, but it doesn't make too much difference.

Thanks Hugo!


added apis for point data

added access to a Points' vertices, which is needed to generate a pointcloud

Points.vertices has been added to the official SDK


Hide the Actor did not work as before System Update[BUG]

Module Version: v0.8.30
Describe the bug
Before the Foundry 9.0 System Update i used the function to hide the actor for the players, so the cant use the Trigger. Hide Actor = canot use Trigger / Unhide Actor = can use Trigger. Since the System Update the Player can use the Trigger doesnt matter it is hide or not.
Im Not sure thats a bug or just a chance, but i would love when it get back to the "Hide = cannot use Trigger" State :P
To Reproduce
Steps to reproduce the behavior:

Create a 'Trigger Actor'
Click on 'Switch visible Mode' (to invisible Mode) Button of 'Trigger Actor'
Click on 'Trigger Actor'
Trigger will trigger (that's the 'Error')

Expected behavior
Trigger will not Trigger (like it was before)
Screenshots

Browser:
Mozilla Firefox
Foundry Version:
9.0
Game System:
Das Schwarze Auge 5th Edition
Additional context
Add any other context (like other modules installed) about the problem here.
THANK YOU :) It's such a wonderful & great Module! ^-^

I don't know exactly what you mean, I don't think the module has ever worked that way. But the module takes into account the permissions, so maybe you managed the permissions in such a way that the hidden elements were managed only by the gm?
However it was a simple thing and I added a module setting for your use case. I also added two new options onlyIfHidden and onlyIfUnHidden so you can specify at the single line trigger whether to fire only when it is hidden or not. The details can be found in the readme.
Try out version 0.8.31 and let me know .

Hey p4535992,
i didnt know why it worked like the discribes way in my case before. But you change solved my Problem, so really thank you :)!
I really love Trigger Happy, coud not image to use Foundry without it, so thank you so much for the work!
All the best for 2022 for you! ;)
Best wishes,
The Story


Add latest kafka versions 3.1.1 and 3.2.0

Same procedure like in
https://github.com/yahoo/CMAK/pull/871
https://github.com/yahoo/CMAK/commit/204288bc41f407640ffc3cbe816cd8eb1219be7c
Signed-off-by: Jürgen Walter<EMAIL_ADDRESS>I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

If you provide me admin rights I could build and contribute a github release.

Ok, needed to shout out to see the build happens with Kafka 2.4. Will try to update if I find the time.

Thank you @patelh! Is there a way to reach you faster, e.g., to provide security relevant fixes?


The meat tag could be replaced with FoodComponent#isMeat()

Good point, I didn't even know that was a property! Thanks for the pointer. :)

I've added it alongside the meat tag - isMeat is used by Minecraft only determine whether a wolf will eat the food. That's why I think it's good to have a tag, to include things such as spider eyes and fish, which are not edible by wolves.

What's the status on this? Foods with isMeat don't appear to be working.

This seems to have gotten lost when I switched to the data-driven power system. Will re-add this in the next update, sorry for the inconvenience.


Add parameters back to ConsLaborModel and fix up to match new distribution code

addresses https://github.com/econ-ark/HARK/issues/721, https://github.com/econ-ark/HARK/issues/684, https://github.com/econ-ark/HARK/issues/681

As this runs black on the codebase it may have added to much to the files changed tab, so have a look at the specific commits
https://github.com/econ-ark/HARK/pull/729/commits/e3d6f2dd0f0f629c225531022ed40f3842bef265 (changes to ConsLaborModel)
and
https://github.com/econ-ark/HARK/pull/729/commits/5c43e0287b6151417cf563ad448a530b645f5bea (adds tests)
to review this PR. :)

I'm loving the blackify style.

This looks good to me except for the typo in the test.


Add support for Notion Home Monitoring

Description:
This PR adds support for Notion Home Monitoring sensors. This PR does not automatically discover new sensors; that will come in a future PR.
Related issue (if applicable): N/A
Pull request with documentation for home-assistant.io (if applicable): https://github.com/home-assistant/home-assistant.io/pull/9665
Example entry for configuration.yaml (if applicable):
notion:
  username: !secret notion_email
  password: !secret notion_password

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

This looks great ! There a couple of small tweaks, especially look up dicts will clean up the code a lot


fix(preparePath): Will now check if the data is an array and iterate it

What does it do?
After preparepath was modified it would no longer iterate over arrays, this pull request fixes that
How to test it?
Try finding many of an entity in the current version and in this version. In this PR it will populate the url_path.

Hey @boazpoolman could you take a look at this. I am sorry I completely missed this while reviewing the changes before the release. But would be cool if you could merge this and create a new release :)


Use functions to map column indexes to IDs.

As @kurapov-peter noticed in one of his reviews, there are many +/-1 expressions used to transform column index to column ID and back. That scheme is not obvious to the reader and is error-prone. So, this patch replaces these expressions with function calls. Also, it introduces a new first-column ID for ArrowStorage (1000) and ResultSetRegistry (2000). Thus, it would be trivial to catch an error when the column index is used as ID and vice-versa, or wrong storage is used to fetch the column (we still might have code that assumes table IDs are unique).

Looks good! Maybe also call it columnIndex instead of columnIdx to be able to distinguish them easier? Stared at it for some time to figure out the difference in the signatures.

Done


FIX: pull frontmatter from proper key

In executablebooks/mystmd#960, @choldgraf observed that opengraph metadata is missing from the static MyST sites. It turns out it's also missing from the dynamic routes too.
I believe the root cause is fixed by this PR, though I have not tested the static export!
Fixes executablebooks/mystmd#960

I don't think this is quite right yet and doesn't address the _index route either.
I think the documentation is a bit unclear here: https://mystmd.org/guide/seo-and-social as in, where are those fields defined? in project, page or site sections or all?
as @agoose77 points out there are page and project frontmatter that are not directly merged, i.e. are treated independently by mystmd.
However there is also SiteFrontmatter that also has title, description and thumbnail fields, (this is returned by the meta function in root.tsx).
I think we should agree on the behaviour we want for the meta responses for the _index.tsx and $.tsx routes, which may be slightly different(?).
Here is a proposal for fixing book-theme (typescripty psuedocode):
_index.tsx
Motivation here is that we are on the main page of the "book" and so site and project frontmatterare used.

field
proposed value

title
myst.yml#site.title ? "myst.yml#site.title - myst.yml#project.title" : "myst.yml#project.title"

description
myst.yml#site.description ?? myst.yml#project.title

thumbnail
myst.yml#project.thumbnail ?? myst.yml#site.thumbnail

(@fwkoch **note that the SiteFrontmatter type does have a .thumbnail field in the type definition, however when setting a thumbnail in myst.yml#site.thumbnail, it seems like that's not picked up, optimised or added to the site config - is that a bug?)
$.tsx
Here page frontmatter takes precedence

field
proposed value

title
"page.title - {myst.yml#project.title ?? myst.yml#site.title}"

description
"page.description ?? myst.yml#project.description ?? myst.yml#site.description

thumbnail
page.thumbnail ?? myst.yml#project.thumbnail ?? myst.yml#site.thumbnail

** NOTE: it is proposed that thumbnailOptimized ahead of thumbnail but that is omitted from the above for brevity

Ah yes, I meant to add a note about the suspicion that inheritance wasn't applied here. Thanks for catching that!

What I am not clear on is the role of the myst.yml#site.* fields, are they intended as overrides or fallbacks? the current proposal above treats them as fallbacks (cc @rowanc1)

My understanding is that the site: key in myst.yml is SiteConfig, which is an intersection type of SiteFrontMatter and other config fields. So, I would expect to be able to add site-specific frontmatter there.
The documentation somewhat disagrees with this, suggesting that if you only have site: and want to add frontmatter, you should add project: to myst.yml.
It's not clear to me what the inheritance order should be either -- in my view there's no point in having site: frontmatter unless you want to change something w.r.t project: for a site deployment. Or, it has a purpose, which is to separate web config from non-web config. I don't think we want to go down that path; better to define all the config in one place and pick-and-choose what makes sense for different exports.
With MyST, I think we're at a stage where things exist for a reason, so I welcome Rowan's thoughts on why we have site frontmatter in addition to project. With my level of knowledge, I'd be tempted to remove frontmatter from site: altogether, though I am no doubt missing something.

Pinging @rowanc1 as this probably needs a wider discussion.

yes, that is why I was thinking that site is perhaps useful as an override -- it's worth just saying that although myst sites are single project by default, and certainly the documentation is all pointed there, they do support multiple projects -- this is case where the site frontmatter starts to make more sense maybe.
👍🏼 on wider dicussion

Just quickly noting that, from my perspective (a user with no knowledge of how the implementation is done), my expectations were:

Anything defined in myst.yml applies to every page in my documentation.
Anything defined on a page overrides anything in myst.yml.
The project and site keys are disjoint (AKA they share none of the same keys)
If (3) is an incorrect assumption, my assumption would be that site keys will over-ride project keys, and that page metadata will override both.

The _index route serves back meta based on the project but overridden by the site

Other routes serve back page meta falling back to project meta, in the case of title they are merged.

Pulled some of the site frontmatter discussion over to this issue: https://github.com/executablebooks/mystmd/issues/1103

@stevejpurves can we merge this now? :)


Delete ERD.pdf

Fixes #857
Describe the changes you have made in this pr -
I have removed this file
Screenshots of the changes (If any) - NA

Coverage remained the same at 83.902% when pulling 71dc7f8783d13f71b169bfd32581da7184e91986 on Shivansh2407:patch-14 into 6f09b19bc35175fcb827fee214dc06db31c5f7cc on CircuitVerse:master.


wip womp part 4

wip womp -1% e z win

Will fix if no one else has when I get to it (seems like it's very easy, just set the minimum value to 0%)

doesn't it has anything to do in RS backend?

No, its just that the progress is 0/ that likely causes the -1% to be shown

https://github.com/RatterScanner/RatterscannerSite/commit/2c7ee3b80615113b8eca26da4b84e07b2c2cfb51


Provisioning failed

Reporting an issue provisioning the Microsoft 365 Learning Pathways template.
Your request to provision "Microsoft 365 learning pathways" template failed!
Please report the issue here providing the following provisioning action correlation ID: a6add676-6398-40db-8f9a-a95f46bc8a42 !

Hi, Thanks for your feedback. I'm closing this item because it is now outdated.


Device Registration GPO

[There is a second GPO setting that should be used for AutoEnrolling into Intune. It should follow (or be included with) step 7 in the section "Verify auto-enrollment requirements and settings".
https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.WorkplaceJoin%3A%3AWJ_AutoJoin
Set that GPO setting to Enable.
]

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

ID: ad012591-5c74-f1cd-d3a2-443768e8ceee
Version Independent ID: 918ea4bc-0849-3745-5d9d-a21a973bcd3b
Content: Enroll a Windows 10 device automatically using Group Policy - Windows Client Management
Content Source: windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md
Product: w10
Technology: windows
GitHub Login: @vinaypamnani-msft
Microsoft Alias: vinpa

Hi @tpl2488, thank you for your feedback.
The verification of the registration of the device to Azure AD is the step 4. I understand that there is no need for that GPO setting.

@dariomws Thank you very much for the contribution and sharing this explanation. @tpl2488 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


AssocList for dictionaries

Work-in-progress implementation of an association list, which can become the foundation of a 'pure Roc' Dict implementation, as well as being an example of a custom datastructure.
Fixes (at least partially) #3245

[x] Basic implementation of most of the interface.
[x] union, intersection, difference. insertAll.
[x] A runnable example to manually test whether the code is correct.
[x] Actual tests.

@Qqwy can we close this since your AssocList implementation landed in-line for the stdlib Dict?

Yes!
I would do it myself but I'm out of town right now and only have access to my PC tomorrow evening again, so feel free to do it earlier
On October 8, 2022 7:34:00 PM UTC, Ayaz @.> wrote:
@. can we close this since your AssocList implementation landed in-line for the stdlib Dict?

--
Reply to this email directly or view it on GitHub:
https://github.com/roc-lang/roc/pull/3258#issuecomment-1272384119
You are receiving this because you were mentioned.
Message ID: @.***>
--
Met vriendelijke groet / Sincerely,
~W-M

Have fun out of town!


CI: test release blocks a real release by using the same version string

Releasing a test version with the tag next uses the same version string as a release with the tag latest, which means that you can't release a test version, test it and then release that as an official version without incrementing the version.
e.g.

6.1.0 was released with the next tag
6.1.0 could not be released with the latest tag, because it was already released as next.  Received NPM error "You cannot publish over the previously published versions: 6.1.0."
6.1.1 had to be released with the latest tag which contained the same code as 6.1.0, in order to provide an official release for that version.

A release with a different tag from 'latest' should append the tag to the version string, e.g. 6.1.0-next.0, 6.1.0-beta.2.  If a release with the same version string exists, the last digit should be incremented.  This should result in the ability to have multiple unique versions utilising the same tag and also enable the following workflow:

Release 6.x.y-next.0, test it manually - fail
Release 6.x.y-next.1, test it manually - fail
Release 6.x.y-next.2, test it manually - pass
Release 6.x.y (same code as 6.x.y-next.2)

I'm going to go out on a limb and guess it's this line:
https://github.com/webdriverio-community/wdio-electron-service/blob/d0afaeb713d83cf0146f1ca41ce0f97c076eba89/.github/workflows/release.yml#L52
For npm, we'd need the -- before the args:
-  run: pnpm run release:ci --npm.tag=${{github.event.inputs.distTag}} -- ${{github.event.inputs.releaseType}}
+  run: pnpm run release:ci --  --npm.tag=${{github.event.inputs.distTag}} ${{github.event.inputs.releaseType}}

Let me know if you want a PR.

@seanpoulter It would be nice if the fix is as simple as that, I'm happy to test it!

@seanpoulter That didn't fix it - output here.  It didn't release anything, I'll revert as the solution is more complex.  I'll update the description as it's not as detailed as it could be.

Sorry @goosewobbler.
To build on that, I double checked the pnpm docs and the the -- is not required:

Any arguments after the command's name are added to the executed script. So if watch runs webpack --watch, then this command:
pnpm run watch --no-color

will run:
webpack --watch --no-color

--
To go back to the root cause, I believe we published 6.1.0 as a regular release with the next tag, not as a pre-release. Reading the release-it docs for a pre-release it looks like we want either --preRelease=next or --preRelease which will:

Add the "next" npm tag is set
Create a pre-release on GitHub

We can test this using the --dry-run flag:
$ pnpm run release:ci --preRelease=next --dry-run

--
That leads to the question of how do we fix this in code? The solution is pretty simple in webdriverio/webdriverio. They've left a comment saying add --canary which for us would be --preRelease like this:
      distTag:
        description: 'NPM tag (e.g. use "next --canary" to release a test version, add "--force-publish" to release all packages)'

Which leads to just:
        distTag:
-         description: 'NPM tag (e.g. use "next" to release a test version)'
+        description: 'NPM tag (e.g. use "next --preRelease" to release a test version'

That means we should be able to test this right now with that --dry-run flag. :)

Let's try the Manual NPM Publish with:
next --preRelease --dry-run

(Christian recently invited me to the org but I'm timid to trigger a release.)

@seanpoulter Thanks for diving into this.  I tested next --preRelease and also next --preRelease=next with the --dry-run switch, they both seem to work, resulting in 6.3.3-0 and 6.3.3-next.0, respectively.
https://github.com/webdriverio-community/wdio-electron-service/actions/runs/8057272785/job/22008037235
https://github.com/webdriverio-community/wdio-electron-service/actions/runs/8057187507/job/22007774002
We should be able to get the workflow in the ticket by using a conditional to add --preRelease=${{ github.event.inputs.distTag }} to the command when the distTag is not latest.  Seems it's not as simple as a ternary though:
https://github.com/actions/runner/issues/409
https://7tonshark.com/posts/github-actions-ternary-operator/
I am assuming that the last version number will increment with subsequent releases of the same tag, we can test this once the above works.

Let's make sure to document the release process as part of this effort.

Thanks @goosewobbler. You're right, the last digit is incremented by the underlying tool, release-it. That'd be quick with an if like:
  - name: Pre-release
    if: inputs.distTag != "latest"
    ...
  - name: Release
    if: inputs.distTag == "latest"
    ...

--
For the docs, are we good with the input description or should we add a section at the bottom of docs/development.md like?

Development

...

Release

Pre-release -- Run the workflow with "latest". Creates an npm verison, GitHub version, etc.
Release -- Run with "next". The suffix is auto-incremented. It Link to the release-it docs. etc.

--
TIL GitHub doesn't support conditional insertion like Azure DevOps:
${{ if inputs.distTag == "latest" }}
  run: pnpm ... --npm.tag=latest
${{ else }}
  run: ..

For the docs, are we good with the input description or should we add a section at the bottom of docs/development.md like?
* Development

  * ...

* Release

  * Pre-release -- Run the workflow with `"latest"`. Creates an npm verison, GitHub version, etc.
  * Release -- Run with `"next"`. The suffix is auto-incremented. It Link to the release-it docs. etc.

As Christian says I think the whole release process should be documented, we'll want to explicitly link to release-it, the workflow itself and also mention that the WDIO bot updates the package version as part of the full release.  I think having a section at the bottom of that doc is a good place for it.

--
TIL GitHub doesn't support conditional insertion like Azure DevOps:
${{ if inputs.distTag == "latest" }}
  run: pnpm ... --npm.tag=latest
${{ else }}
  run: ..

Yeah, annoying isn't it?  Though more verbose, at least we can use the conditional steps as you detailed above.

I'll test the workflow changes merged in #444 as part of releasing 6.4.0, and then close this issue or comment here according to the results.

Tested dry runs, they were successful - now releasing a couple of versions of 6.4.0-next.*.

Ok, this still needs some work to get multiple, subsequent pre-releases working - the WDIO bot updated the version of the package to 6.4.0-next.0, I then created another minor pre-release and we ended up with 6.5.0-next.0.  I then released a patch dry-run pre-release and got 6.5.1-next.0.  Ideally we want to be incrementing the last digit when there is an existing pre-release.  I think having a checkbox to apply --dry-run would be nice too.

Oh, how fascinating. I understand the example in the release-it docs now. They don't use a major/minor/patch arg:

Consecutive beta releases (2.0.0-beta.1 and so on):
release-it --preRelease

We always provided it so we see the behavior you described. :facepalm: The solution seems to be make that releaseType optional for pre-releases which would support your initial use case, but also let you publish a pre-release for a future version:

Given I am at v6.3.2
When I publish a major pre-release with the tag "alpha"
Then I expect v7.0.0-alpha.0 to be published

Any preference on the final result?

Have a look at #460. That might do it. :thinking:

@seanpoulter That looks great - I think ultimately this sort of logic should be extracted into an action but there are certainly higher priorities for the service development - I'm happy to merge #460 and give it a test run.

I've made it ready for review. I was debating creating two workflows.

I tested subsequent pre-releases, seems to work although getting 422 when creating the github release.  Is this because there are no changes?  The npm version is published and the WDIO bot updates the package version.
https://github.com/webdriverio-community/wdio-electron-service/actions/runs/8211588209/job/22460721293
https://github.com/webdriverio-community/wdio-electron-service/actions/runs/8211712054/job/22461024964

Interesting.
The 422 Unprocessable Entity is documented here. https://docs.github.com/en/rest/using-the-rest-api/troubleshooting-the-rest-api?apiVersion=2022-11-28#invalid-request. It reads like the response body should explain exactly what's wrong. The logs say:
✖ GitHub create release
ERROR 422 (Invalid request.

For 'properties/body', nil is not a string. - https://docs.github.com/rest/releases/releases#create-a-release)

When I read that I believe the body is not set when we try to create the release.
It sounds like it might be expected ooks like we could add the --ci flag to skip the release if there are

Interesting.
The 422 Unprocessable Entity is documented here. https://docs.github.com/en/rest/using-the-rest-api/troubleshooting-the-rest-api?apiVersion=2022-11-28#invalid-request. It reads like the response body should explain exactly what's wrong. The logs say:
✖ GitHub create release
ERROR 422 (Invalid request.

For 'properties/body', nil is not a string. - https://docs.github.com/rest/releases/releases#create-a-release)

When I read that I believe the body is not set when we try to create the release.
Based on the API docs the body is not a required property. I wonder if we're sending null or nil and it breaks. :thinking:
Based on https://github.com/release-it/release-it/issues/1014#issuecomment-1591160357 it seems like we could prevent this using the --ci flag.

For what it's worth I've documented the issue in https://github.com/release-it/release-it/issues/1014#issuecomment-1986725953 and proposed a fix. :wink:

@seanpoulter thanks again for your work, digging through all this.  I think we are applying the --ci flag:
https://github.com/webdriverio-community/wdio-electron-service/blob/main/package.json#L59
You can see it in the output here.

Technically this ticket is completed with the updates to the release workflow already merged.  I'll raise new tickets for anything outstanding.


Bot thinks I don't have items that I have contained in a set

🐛 Bug Report
https://i.gyazo.com/9fb088a7de39fe9ffa4cd6cc64b05a9f.png
https://i.gyazo.com/ec14cc4634c12934720a08d61e3f0d82.png

If they're in a set, then you don't "have" those items in the set, you have the set item, so you need to unpack it.


fixed the icons issue

I have fixed the icons issue in the contact section. Now you can hover on the each box and it will behave normally.

Hey @Brainiac-M can you please update your forked repo

Hi @PritamSarbajna, I think my branch is up to date now.

You're welcome.


chunkHighMark ignored when it is a big number

I'm trying to let polipo make use of large memory, so I increased chunkHighMark to 2G-8K, it works.
If I set it to 2G+1-8K, it would be ignored and set to default value 25165824.
Is this limit desired? or by accident?

That's expected.  There are many places in Polipo where 32-bit overflow is not handled correctly.

I think it would be useful to mention this limitation in document if it
doesn’t worth fixing.
On Fri, May 11, 2018 at 21:54, Juliusz Chroboczek<EMAIL_ADDRESS>wrote:

That's expected. There are many places in Polipo where 32-bit overflow is
not handled correctly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jech/polipo/issues/101#issuecomment-388370496, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD9Q99y8Ggb9nniiEv4PTX9LHwfkuPQwks5txZgAgaJpZM4S2Zuh
.

I think it would be useful to mention this limitation in document if it
doesn’t worth fixing.

Polipo is no longer being updated, sorry.


Weird color and size shift on Next Js

So for some reason when the page is first loaded in the production server it makes the text grow bigger or change different color.
is there any fix?
website here:
https://zion-producers.vercel.app/

I think that daisyui is loading after the page is already served, but I don't really know

Do you have this issue without daisyUI?
Can you share your code?

I'm closing this due to no answers and no code examples.
Please re-open after providing an example repo to reproduce the issue.

https://user-images.githubusercontent.com/77029802/160286747-64186512-23eb-42a6-bf21-7bf3558b5acf.mp4
The code has changed so I don't have the original code


Debian package edits user dotfiles

I took a look at https://toolbelt.heroku.com/install-ubuntu.sh before I ran it, so imagine my surprise when I got through running it and my .zlogin had been molested. I'll skip the rant and get right to the obvious question: why not a /usr/bin/heroku symlink? This is what Google Chrome does, for example.

I believe this stuff is all gone now

oops, no it isn't. Once more of the v4 CLI stuff is out I'll be sure to resolve it though: https://github.com/heroku/heroku/blob/master/resources/deb/heroku/postinst

Did a87da812 remove the last bit of this maybe? Can this maybe be closed (again)?


E2E test runner guide document.

What would you like to be added:
An E2E test runner guide document.
Why is this needed:
After developing the e2e test cases, it would be a good idea to write an e2e test runner guide document. This could help other team members independently run the e2e tests.

/assign


Drafted 2.6 release notes.

Description
Drafted 2.6 release notes.
Issues Resolved
https://github.com/opensearch-project/security-analytics/issues/333
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #353 (03a6164) into 2.x (591662c) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##                2.x     #353   +/-   ##
=========================================
  Coverage     36.49%   36.49%
  Complexity      885      885
=========================================
  Files           185      185
  Lines          7110     7110
  Branches        860      860
=========================================
  Hits           2595     2595
  Misses         4278     4278
  Partials        237      237

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update grafana_datasource.rb

Quick and dirty extend it with AWS CloudWatch and zabbix data sources.

As I know correct type for zabbix
"type":"alexanderzobnin-zabbix-datasource"

@bfraser what do you think is it better add all custom 'plugable' datasources here or add possibility to set any value for type?

Is there any progress on this feature?


Feature Request: Static Cromwell Servers

Investigate the potential for lapdog engines to connect with permanent cromwells.
Cromwell would need existing lapdog wdl_runner and additional scripts to:

listen for inbound requests and hand them into cromwell while respecting batch and query limits
Move output files into the bucket? Local cromwell will probably be able to handle this w/ gcs file system configured properly

Cromwell should only trust a fixed set of projects. Engine should produce a signature which the cromwell can use to verify the authenticity of the request.

How does local lapdog handle this? Operation IDs will not be present, which necessitates UI changes. Additionally, a new set of adapters will be required ☹ to handle lack of operation ids and event records

I don't think this change is feasible at the moment. Maybe once other, more pressing, changes are made and if there is renewed interest, I will re-open the issue


Get babar log without using Yarn

Hey Criteo team,
I was wondering if it was possible to get babar.log without using yarn.
I already tried to create a RollingFileAppender in a log4j file in order to store the output from criteo.babar package :
log4j.logger.com.criteo.babar=myConsoleAppender, Profiler
log4j.additivty.com.criteo.babar=false

This solution didn't work and I might miss something.
Thank you for the help and the cool library you developed.

Hello @antoinegargot !
You should be able to use Babar without YARN, we use Yarn for 2 things that you can do another way:

each container logs to a file in its local yarn log directory
When aggregating the results with babar-processor, we parse the log file that has been aggregated by yarn from all the containers' yarn log files.

for 1., If your are not running on Yarn, your babar.log file should be written locally on each node in ./logs. You should also be able to specify the log dir in the agent parameters with
-javaagent:/path/to/babar-agent.jar=dir=/my/logs/path,...

(you can see https://github.com/criteo/babar/blob/master/babar-agent/src/main/java/com/criteo/babar/agent/reporter/LogReporter.java#L67)
for 2. If you have multiple logs file, you'll need to concatenate them as one large text file before aggregating them with the babar-processor. If you have only one file you can directly process this one.
For log4j, we couldn't use it as it doesn't seem to be possible log inside the ShutdownHook of the JVM. We log at that point so that the last stack traces of the JVM on shutdown are correctly captured and reported.
Let me know if you have any issue running it this way :)
Best,
Benoit

Hey @BenoitHanotte,
Thanks for the useful tips, I didn't find this getLogDir when I went through the code. I will try this solution and will let you know how it goes.
Regarding log4j, is it still possible to use your logger and ignore the last stack traces of the JVM?
Thank you again for the help and the great work you're doing.
Best,
Antoine


Add support for more jsonschema builtin string formats

From http://spacetelescope.github.io/understanding-json-schema/reference/string.html
The following is the list of formats specified in the JSON Schema specification.

"date-time": Date representation, as defined by RFC 3339, section 5.6.
"email": Internet email address, see RFC 5322, section 3.4.1.
"hostname": Internet host name, see RFC 1034, section 3.1.
"ipv4": IPv4 address, according to dotted-quad ABNF syntax as defined in RFC 2673, section 3.2.
"ipv6": IPv6 address, as defined in RFC 2373, section 2.2.
"uri": A universal resource identifier (URI), according to RFC3986.

date-time string format support has landed in #116.

Fixed by #113.


Error starting rds instance RDS:xxx (Shape is missing required key 'type': OrderedDict([('members', OrderedDict([('SourceRegion', OrderedDict([('shape', 'String')

RDS instances are not starting after stopping successfully with the Instance Scheduler:
2021-03-26 - 08:00:28.186 - ERROR   : Error starting rds instance RDS:xxx
(Shape is missing required key 'type': OrderedDict([('members', OrderedDict([('SourceRegion', OrderedDict([('shape', 'String'),
('documentation', '
The ID of the region that contains the source for the db instance.
')]))]))]))

We are using the aws-instance-scheduler version v1.3.3 (SO0030).
CloudFormation parameters:

DefaultTimezone: America/Sao_Paulo
LogRetentionDays: 1
MemorySize: 1024
Regions: us-east-2
ScheduleLambdaAccount: Yes
ScheduleRdsClusters: Yes
ScheduledServices: Both
SchedulerFrequency: 1
SchedulingActive: Yes
SendAnonymousData: Yes
StartedTags: -
StoppedTags: -
TagName: Schedule
Trace: Yes
UseCloudWatchMetrics: Yes

We created the period and schedule using the scheduler-cli tool running the following commands:
scheduler-cli create-period --name cwb-office-hours --weekdays mon-fri --begintime 06:00 --endtime 20:00 --stack Instance-Scheduler
scheduler-cli create-schedule --name cwb-office-hours --periods cwb-office-hours --stack Instance-Scheduler

DynamoDB ConfigTable:

We are using the tag Schedule with the value cwb-office-hours with RDS Instances (MySQL, PostgreSQL) and RDS Clusters (Aurora MySQL).

Hi @esaporski Can you confirm if the Schedule tag has been added to any of the instances within the cluster?
Refer to the Implementation Guide. Section Amazon RDS.

Hi, @gockle :)
Yep, the instances/clusters are tagged correctly:

The scheduler can stop the instances/clusters successfully, but cannot start them afterwards.

@esaporski Is it possible to update the lambda code and try a workaround? the file rds_service.py in the ./lambda/schedulers folder, update the method start_instances(...) by removing the return statement at the end. This is a know issue, when there is an error in one of the instances the code exits the method without completing the start for all the instances in the list. We will be adding a change to our next release to address this issue, but let me know if the workaround resolves the issue and starts all the instances.

Absolutely @gockle :)
I'm going to update the lambda code and monitor the instances/clusters tomorrow.
I will update the issue to tell you if the workaround worked or not.
Thanks a lot!

It worked :)
I checked the logs and it is behaving a little bit erratically though:
2021-04-06 - 09:00:32.886 - DEBUG   : Desired state for instance from schedule "cwb-office-hours" is stopped,
last desired state was unknown, actual state is running

Thanks a lot, @gockle!


Add Audit Logfile Capability

It would be great for auditing purposes if the ldap2pg tool could write verbose output to a logfile with timestamps - while it may retain the current output format without timestamps for the console for readability purposes.
Alternatively a flag to just enable timestamps in the current verbose console output would work also - in which case the output can then be redirected to a file if needed. An ISO 8601 formatted timestamp with millisecond granularity (e.g. 2021-11-10 15:52:10.200) should be good enough for a start.
This will also help in a corporate context where logfiles are often consumed by tools such as Splunk. They often struggle to parse messages correctly without timestamps - i.e. multiple log lines may end up being treated as one single message.

Hi @patcamen . Interesting. I'm willing to make ldap2pg a good citizen with splunk and other auditing tools. Can you forge some sample of log lines you expect ?
For auditing, do you need only CHANGES,  WARNING, INFO and ERROR messages ? Please share me a sample audit file you would like ldap2pg to generate. Or do you need the full verbose log for auditing ? Do you need to configure auditing
Do you want a cli swithc like ldap2pg --config my-ldap2pg.yml --audit-file my-ldap2pg-audit.log ? That would be independant from color and verbosity.
Another option would be to configure auditing in yml file:
auditlog:
  destination: /var/log/audit/ldap2pg.log
  level: DEBUG

sync_map:
 ...

That would be still configurable through env vars AUDITLOG_DESTINATION, etc.
Thanks for the feedback.

Hi @bersace ,
attached you find a mocked sample for what would be my ideal audit log format - ldap2pg_audit_log_sample.txt
Note: the real audit log would not feature the same timestamp on all lines of course.
The sample contains a subset of the current DEBUG messages only that I would consider as audit relevant plus all INFO level and higher messages.
The idea being to prove the exact changes that were applied to the PostgreSQL server and why (based on what information found in LDAP and YAML file).
If it was too complex to log only certain DEBUG messages to the audit file it would be also fine to log all current DEBUG messages instead.
As shown in the attached sample it would be great if the INFO LDAP coordinates would be logged in full length to the audit file - as in the console they currently get cropped. Alternatively the current DEBUG ldapsearch messages would be needed to evidence what exactly was queried from LDAP.
If I were to chose, I would probably want the audit log to be configured inside the yml file like you have shown above - as indeed other users might want to chose a different log level to go to the audit log. Also like this the audit log would be decoupled from the console verbosity set.
Thanks.

Maybe a switch option would raise some debug message like ldapsearch commands and query to INFO level.


Allow custom components to access existing components and helper functions

Feature Description
Allow custom components to access other components or helper functions within a project.
I'm building a custom component within a standalone project and found myself reaching for a couple of things which my custom component file doesn't have access to:

Evidence components (e.g., if I want to include a DataTable in my component)
Helper functions (number formatting and title formatting most important here I think)

Goal of Feature
Reuse existing components and functions to build something for a specific use case, without having to contribute it into the main Evidence project.
Current Solution
Build the component within the monorepo and contribute it into the open source project.
Alternative Ideas
There may be a way to import the components I want to use in the script tag. I think ideal solution is to not require an import for things already in the project, but if there's an import statement that can be copy-pasted and then modified, that would work as well.

Ah nice, that does work for components - great. I was using the wrong syntax when I tried the import.
So I think this narrows this issue down to the formatting functions (and any other helper functions we think are important to have access to). I think the formatValue function gets solved if we add an accessible fmt function as we've discussed before. Maybe we also add a fmtTitle function that is generally accessible as well, or a way to import it into a custom component file

fmt is also now in main.
I suspect you could import { formatValue as fmt } from '$lib/modules/formatting';
It's undocumented, and doesn't happen by default!

@ItsMeBrianD after working with a few custom components, I think we need the utility functions to be importable in a custom component.
How hard would it be to have parts of component-utilities be importable?
Some functions I reached for recently when developing custom components:

fmt (or formatValue)
formatTitle
getDistinctCount
getDistinctValues
getSortedData
checkInputs

One other piece that may complicate this. In the Waterfall Chart I built, it needs to access the following because it uses the Chart component under the hood. Is there a way to access context?
import { getContext, beforeUpdate } from 'svelte';
import { propKey, configKey } from './context';
$: props = getContext(propKey);
$: config = getContext(configKey);

Everything in component-utilities should be importable; here's an example
https://github.com/evidence-dev/evidence/blob/main/packages/core-components/src/lib/unsorted/QueryStatus.svelte#L11

Ah perfect, thanks! Sorry, I missed this before. I was making mistakes on when to use named imports vs. a default + I was trying to import from the package as a whole rather than the individual js files.
Got it working with the utility functions.
Last question - how would I do these imports from core-components?
import { propKey, configKey } from './context';


Ignore refunds. Improve layout

Coverage remained the same at 71.824% when pulling db0af1d16a277e2b2348c03824fb86eede05ef16 on monthlyReport into 108d99ad598c24e6c681c4c17c7491f7f0f22bf1 on master.


Ear Piece support

I saw that there is a PR for ear piece support on this module but I didn't saw any documentation about it.
#145
Is there any way that this feature will be added on the latest release build of this module?

Thanks @CmerCy132. I've added this to the Project and raised it again for discussion/review.


Features for better managing services and packages

added puppet-syntax gem to Gemfile
added new parameters server_package_ensure, manage_server_service, manage_server_servicehelper, manage_client_service  for better managing service and packages

amazing thanks! can we have also the packages to trigger services restart?

Hey, i've pushed the needed changes to https://github.com/derdanne/puppet-nfs/tree/feature_notify_services_from_packages.
Could you please verify the patch.

sure checking

client/server_package_ensure remove the validation please. It can be also a version

We can remove it for server packages, client packages will be in most cases an array, where versions of each package do not necessarily match.

Oh, i see that this also counts for the server packages ... i have to rethink this, maybe we need anothe solution here

I opened a new issue for that problem: #37

$notify_services = suffix(prefix(keys($::nfs::effective_nfsv4_client_services), 'Service[\''), '\']')
this is too complex. Service can take an array as argument iirc, so it can be simplified to Service[keys($::nfs::effective...)]. But I'm not 100% sure about this, need to verify it first

Yes, but i thought this is not compatible with older puppet versions, but maybe i am wrong - just had it in my mind ...

Just checked:
https://docs.puppet.com/puppet/latest/reference/lang_data_resource_reference.html#multi-resource-references
So your approach should be fine!

@tampakrap
Hey, the best way should be to manage package versions (if needed) outside the module, so i think of a manage_package switch - so you can completely define the packages yourself.
What do you think? Any better approach?

The manage_package switch is fine and would be a step forward, but it does not solve entirely the problem. The appropriate approach would be to create different variables for each package unfortunately, but I understand that there is quite a variety of package names along the distros, as seen in params.pp. So what I would suggest is just to remove the validation for the package_ensure, and let the users overwrite the package list in their profile module if they want to override stuff.
As an example, I did it in my infrastructure. I am using osfamily suse, and I removed nfsidmap and rpcbind from the client_packages array, as they are properly pulled in by my package manager. In case I would like to lock their versions in the future I can do it in my profile module (same for client_packages, which is only 'nfs-client' for me now, assuming the validation wouldn't be there).
Does that make sense?

Another idea that I just thought of: let server_packages and client_packages contain only the necessary packages and their subpackages, and create variables like server_pkg_dependencies to provide an array of packages as dependencies (controlled by a server_pkg_deps_manage switch). I don't like this idea very much though, as the _pkg_dependencies packages will have exactly the same issue that we are trying to solve. Tbh I would just remove the validation and let users figure it out themselves from then

OK, ithink i will do both, i will set the validation for the package_ensure to string and i will add a manage_package switch, so the user has the full control, and can do whatever he wants do do.


Extract rom/changeset gem from rom/repository

Everything related to Changeset can be moved from rom/repository to rom/changeset which will become a separate gem

Hey! New to contributing to rom but I've been using gem for a while. Would love to help with this, and sounds like a good first PR?

@kwando hey, thank you :) it's definitely a good candidate, as it's mostly moving things from one place to another.

@kwngo hey, thank you :) it's definitely a good candidate, as it's mostly moving things from one place to another.

Awesome! I'll take a look at the structure of the other directories and get started..

Cool, let me know if you have any questions.

@kwngo no pressure whatsoever but did you make any progress? We're trying to move fast and hit 4.0 beta in a couple weeks so if this doesn't feel like a good task for you after all, please let me know.

Can we close this one? @solnic

Yes, closing now via #426


Closes #53

Closing to remove the branch and undo SessionPlanSequenceInstance implementation.

Closing to remove the branch and undo SessionPlanSequenceInstance implementation.


integrate ghminer into dataset build pipeline

as mentioned here, let's integrate this tool into our process of dataset building

We need to remove old /data sources too

moved to https://github.com/h1alexbel/srdataset


Randomize the table names used in BigQuery integration tests

Randomizes the table names used in BigQuery integration tests to reduce flakiness regarding the 1,500 updates per day limit: https://cloud.google.com/bigquery/quotas#tablesinsert_requests

We should probably also port to the new repo.

Will do.


Add interdomain healing examples

Overview
We need to check scenarious from single cluster testing in multicluster scenarious.

@NikitaSkrynnik Thanks!


Ng-model support

This directive need ng-model implementation so it's more intuitive.

[ ] Remove selected attribute and create emptyText for display text instead.
[ ] Recognize selected option when model is giving.


feat(): add labelType to paymentSheet

at iOS or Android: https://github.com/capacitor-community/stripe#screenshots
PaymentSheet:

"Add your payment information"(Android)
"Add your payment information"(iOS)
"Pay"

PaymentFlow:

"Add your payment information"(Android)
"Add a card"(iOS)
"Add"(Android)
"Add card"(iOS)

We should add labelType or paymentType, and judge iOS or Android.
Thanks.

Could you describe it in more detail?
What property do you want to expect the attribute to?
Or share the use-case as a code.
@rdlabo

This is about Title, and Label of payment button:

I think it would be great if web design could follow natives.

How about the title and buttonLabel attribute instead?

Now we have no plan to support both way by default.

PaymentSheet
PaymentFlow

So you can customize the title and button label as an attribute.
@rdlabo

I and @rdlabo talk about the idea.
And here is the specification we decided.

Sheet title: sheet-title attribute
Button label: button-label attribute
Both OS default text should be ready to translate.
We can put another text to these atts, but will not translate inside the component.

https://github.com/stripe-elements/stripe-elements/releases/tag/v1.0.0-canary.0


Merging pull requests not working with tracked LFS files

Description
Branches can be merged by local clients(git cli/Github for Windows) with push but not with web interface.
gitea.log have errors like this:
Apr 01 05:01:02 ip-172-31-41-184 gitea[3613493]:         batch request: missing protocol: ""
Apr 01 05:01:02 ip-172-31-41-184 gitea[3613493]:         batch request: missing protocol: ""
Apr 01 05:01:02 ip-172-31-41-184 gitea[3613493]:         batch request: missing protocol: ""
Apr 01 05:01:02 ip-172-31-41-184 gitea[3613493]:         batch request: missing protocol: ""
Apr 01 05:01:02 ip-172-31-41-184 gitea[3613493]:         batch request: missing protocol: ""
Apr 01 05:01:02 ip-172-31-41-184 gitea[3613493]:         error: failed to push some refs to....
...
Somebody else too getting the error. Mentioned here. https://discourse.gitea.io/t/merging-pull-requests-not-working-with-tracked-lfs-files/435/1
Gitea Version
gitea-1.19.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots

Git Version
No response
Operating System
ubuntu
How are you running Gitea?
Native build on ubuntu, running using systemctl
Database
SQLite

I am using LFS too, haven't encounter the problem.

Could you help to provide more clues, or provide a minimal reproducible setup (eg: docker)?

Feel free to re-open if you can provide reproducible steps.


[BEANUTILS-509] Wrap WeakHashMap in Collections.synchronizedMap

@garydgregory Just pinging you again about a potential BeanUtils2 release?

Closing this PR in favor of #37


more details about the output file

hi,
I would like to know what is meaning of "count" and "copy" in the output file 'blastout.filtered.txt'.
thank you

count -> read counts
copy -> gene copies (sum of genes' coverage)

Thank you for your reply


feat: enable windows and macos build

Signed-off-by: Derek Ho<EMAIL_ADDRESS>Description
Enable windows and macos builds
Issues Resolved
#192
#191
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #504 (dc71755) into main (32d22c6) will decrease coverage by 2.41%.
The diff coverage is n/a.

:exclamation: Current head dc71755 differs from pull request most recent head 670f703. Consider uploading reports for the commit 670f703 to get more accurate results

@@             Coverage Diff              @@
##               main     #504      +/-   ##
============================================
- Coverage     74.27%   71.85%   -2.42%
  Complexity      383      383
============================================
  Files            94       64      -30
  Lines          3984     2061    -1923
  Branches        641      229     -412
============================================
- Hits           2959     1481    -1478
+ Misses          891      449     -442
+ Partials        134      131       -3

Flag
Coverage Δ

dashboards-reports
?

reports-scheduler
71.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...r/routes/utils/visual_report/visualReportHelper.ts

...main/__tests__/__utils__/main_utils_test_utils.tsx

...ashboards-reports/server/utils/validationHelper.ts

...eports/public/components/utils/settings_service.ts

.../components/main/report_details/report_details.tsx

...ashboards-reports/server/routes/utils/constants.ts

...s-reports/public/components/main/reports_table.tsx

dashboards-reports/test/propsMock.js

...ublic/components/report_definitions/utils/index.ts

...itions/report_trigger/report_trigger_constants.tsx

... and 20 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

This is blocked on incompatibility between windows chromium binary and puppeteer. CC @joshuali925


Linux support

@airblade Please add a note with the settings/values you need to implement support for Kite on Linux.

The shell commands to:

detect whether and where Kite is installed;
detect whether Kite is running;

currently using ps -axco command and grepping for ^Kite$

launch Kite.

This is how kite will be installed on Linux:

binary name kited, default location is /usr/bin/kited. This is a script which launches a kited binary from a subdirectory of /opt/kited/
Detection: The ps command and grepping for ^kite$ should be fine
Launching: launch kited from $PATH

Done in #152.


Nature of the VM

Hi there. :D
Which kind of VM is that one of Gluon? Stack based?
And which kind of threads does it use?
Thanks :hugs:

Yes, it is a stack based VM with green threads which, since they are threads safe, be ran on different OS threads. The only really special thing about it is that objects have limited form of sharing between each green thread which avoids copying in many cases while also avoid full heap scans https://github.com/gluon-lang/gluon/blob/b7309dcb483c16c963cae2b50106d671ed85c5c8/vm/src/gc.rs#L161-L179

Thanks a lot. You can put this in the documentation, if you think that is fine. Nice day :D


Change linux-setup to linutil in 1-compile-setup.sh, closing #50

It still had the old repo name and had to be changed so the clone worked as expected.

This closes #50.


 It is Spark streaming app which reads data from Kafka and upsert it in Hudi. Below is the psuedocode

var df=  read kafka
df.persist() // we persist the dataframe because we can have both upsert and delete records in single dataframe. SO filter them based or U or D
Filter only upsert records and insert it in hudi
Filter only Hudi records and insert it in Hudi
df.unpersist()

While doing delete, it is throwing below error. My Question, should we need to sync with Hive even for delete operation?Pls confirm.
20/07/05 10:19:20 ERROR hive.HiveSyncTool: Got runtime exception when hive syncing
18039 java.lang.IllegalArgumentException: Could not find any data file written for commit [20200705101913__commit__COMPLETED], could not get schema for table /user/admin/hudi/users, Metadata       :HoodieCommitMetadata{partitionToWriteStats={}, compacted=false, extraMetadata={ROLLING_STAT={
18040   "partitionToRollingStats" : {
18041     "" : {
18042       "d398058e-f8f4-4772-9fcb-012318ac8f47-0" : {
18043         "fileId" : "d398058e-f8f4-4772-9fcb-012318ac8f47-0",
18044         "inserts" : 989333,
18045         "upserts" : 11,
18046         "deletes" : 0,
18047         "totalInputWriteBytesToDisk" : 0,
18048         "totalInputWriteBytesOnDisk" : 49443028
18049       },
18050       "eed1f67c-8c46-425f-b740-2e21b84c6f13-0" : {
18051         "fileId" : "eed1f67c-8c46-425f-b740-2e21b84c6f13-0",
18052         "inserts" : 1263360,
18053         "upserts" : 16,
18054         "deletes" : 0,
18055         "totalInputWriteBytesToDisk" : 0,
18056         "totalInputWriteBytesOnDisk" : 49672386
18057       },
18058       "e9f38e55-acf2-4bd2-b568-def7361f2f29-0" : {
18059         "fileId" : "e9f38e55-acf2-4bd2-b568-def7361f2f29-0",
18060         "inserts" : 946616,
18061         "upserts" : 6,
18062         "deletes" : 0,
18063         "totalInputWriteBytesToDisk" : 0,
18064         "totalInputWriteBytesOnDisk" : 45686395
18065       },
18066       "8a93afac-d60e-41bb-a3e1-edd793e2a932-0" : {
18067         "fileId" : "8a93afac-d60e-41bb-a3e1-edd793e2a932-0",
18068         "inserts" : 482202,
18069         "upserts" : 0,
18070         "deletes" : 0,
18071         "totalInputWriteBytesToDisk" : 0,
18072         "totalInputWriteBytesOnDisk" : 49744729

Expected behavior
A clear and concise description of what you expected to happen.
Environment Description

Hudi version : 0.5.2

Spark version : CLoudera spark 2.2.0

Hive version : Cloudera Hive 1.1

Hadoop version :2.6

Storage (HDFS/S3/GCS..) :HDFS

Running on Docker? (yes/no) :No

@RajasekarSribalan  quick questions for clarity:

You intend to also take the deletes from Kafka and apply to Hudi right? Or is that strictly a transformation logic that you want to filter out in Spark Streaming before even loading into Hudi table?
If yes to above question, how are you doing delete - soft or hard delete ? https://hudi.apache.org/docs/writing_data.html#deletes

@bhasudha

We have transformation logic for deletes and hence we are filtering the delete records.

We are doing hard delete and "delete" is the operation we use in spark write operation for delete records

@bhasudha  just an update, our jobs are not failing but we get this error for hard delete operation and below is the command that we use on dataframe for delete operation.
My concern is, whether hudi is doing rollback before the error? I hope it is not,  pls confirm.
ERROR hive.HiveSyncTool: Got runtime exception when hive syncing
18039 java.lang.IllegalArgumentException: Could not find any data file written for commit [20200705101913__commit__COMPLETED], could not get schema for table /user/admin/hudi/users, Metadata :HoodieCommitMetadata{partitionToWriteStats={}, compacted=false, extraMetadata={ROLLING_STAT={
18040 "partitionToRollingStats" : {
18041 "" : {
18042 "d398058e-f8f4-4772-9fcb-012318ac8f47-0" : {
18043 "fileId" : "d398058e-f8f4-4772-9fcb-012318ac8f47-0",
18044 "inserts" : 989333,
deleteDataframe.write
.format("hudi")
.options(getQuickstartWriteConfigs)
.option(OPERATION_OPT_KEY, "delete")
.option(PRECOMBINE_FIELD_OPT_KEY, hudi_precombine_key)
.option(RECORDKEY_FIELD_OPT_KEY, hudi_key)
.option(PARTITIONPATH_FIELD_OPT_KEY, "")
.option(TABLE_NAME, tablename)
.option(TABLE_TYPE_OPT_KEY, "COPY_ON_WRITE")
.option(HIVE_SYNC_ENABLED_OPT_KEY, "true")
.option(HIVE_URL_OPT_KEY, "jdbc:hive2://XXXXXX:10000/;principal=XXXX/XXXXXXX)
.option(HIVE_DATABASE_OPT_KEY, hudi_db)
.option(HIVE_TABLE_OPT_KEY, tablename)
.option(HIVE_PARTITION_EXTRACTOR_CLASS_OPT_KEY, classOf[NonPartitionedExtractor].getName)
.option(PAYLOAD_CLASS_OPT_KEY, "org.apache.hudi.EmptyHoodieRecordPayload")
.mode(Append)
.save("/user/XXXXX/hudi/" + tablename)

20200705101913__commit__COMPLETED indicates the commit was completed successfully actually.. I think it's saying the commit file does not have a data file, from which it can fetch schema. ..
Do you mind sharing the<PHONE_NUMBER>1913.commit file from timeline? @bhasudha  can you check if there are any changes in 0.5.3 around this. My understanding is that currently we are writing the schema together with the commit file, so it does not even have to look for a data file..
@RajasekarSribalan if you are up for it, and easy to do, can you give master branch a shot?

Thanks Vinoth. I ll try to fetch the commit file but as of now I have now
disabled hive sync for delete operation and now I don't get this error at
all? Do you have any comment on this?.
As I said,when I enable hive sync for delete operation I get this error but
not when I disable it.
On Wed, 8 Jul 2020, 6:07 am vinoth chandar<EMAIL_ADDRESS>wrote:

20200705101913__commit__COMPLETED indicates the commit was completed
successfully actually.. I think it's saying the commit file does not have a
data file, from which it can fetch schema. ..
Do you mind sharing the<PHONE_NUMBER>1913.commit file from timeline?
@bhasudha https://github.com/bhasudha can you check if there are any
changes in 0.5.3 around this. My understanding is that currently we are
writing the schema together with the commit file, so it does not even have
to look for a data file..
@RajasekarSribalan https://github.com/RajasekarSribalan if you are up
for it, and easy to do, can you give master branch a shot?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/hudi/issues/1794#issuecomment-655211543, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFMO6I26H5UBJRHI5LMVJPDR2O5TBANCNFSM4OQ2GZNQ
.

@nsivabalan  might be worth reproducing this in the docker environment?

Sure. I will try to reproduce. Will update in two days.

I couldn't repro it locally (everything was ok). But in general, hive sync is required only if there are changes to partitions list (like new partitions added, removed, etc). When I tried, changes were reflected even w/o doing an hive sync. So, you are good to skip hive sync for those commits which has only deletes.

please reopen if you need anything.

Thank you for your response 😊
On Fri, 17 Jul 2020, 4:02 pm Sivabalan Narayanan<EMAIL_ADDRESS>wrote:

Closed #1794 https://github.com/apache/hudi/issues/1794.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/hudi/issues/1794#event-3557508625, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFMO6IY7WMYUC32D6VR4MH3R4ASD7ANCNFSM4OQ2GZNQ
.


Use data wrangler package in AWS Lambda exceed maximum size 262144000 bytes

I tried to use data wrangler in AWS Lambda function as a dependency, but the package is too large to import(about 259M)
And we got below error.
botocore.errorfactory.InvalidParameterValueException:An error occurred(InvalidParameterValueException) when calling the PublishLayerVersion operation: Unzipped size must be smaller than 262144000 bytes
Do we expect the data wrangler to be used as a dependency in Lambda? If so, how to use it?

You can use the provided Lambda Layer for using awswrangler inside of Lambda functions.
Instructions for it can be found in the Install documentation: https://aws-data-wrangler.readthedocs.io/en/2.4.0-docs/install.html#aws-lambda-layer

I would prefer not to use a lambda layer, because that involves changing my tooling for deployment and unit testing.
What about if I write a PR to install this library like moto.
i.e. pip install awswrangler installs everything, but if I do pip install awswrangler[athena] that will only install the components required for connecting to Athena (i.e. no pyodbc, no openpyxl etc)?

The problem is that the extras feature in python only supports extending the required packages. This means that it is not possible that pip install awswrangler[athena] installs less than pip install awswrangler as it would always install all packages which are required by awswrangler.


clickhouse system tables are becoming HUGE

I use jitsu-chart (v1.9.1) and I noticed that all the tables of xxx_log of the system database of the clickhouse pod are becoming HUGE .
For example:

For now, I must delete there lines manually.
Is there a solution for this ?

Using https://gist.github.com/sanchezzzhak/511fd140e8809857f8f1d84ddb937015?permalink_comment_id=3159885#gistcomment-3159885,
I got this in few weeks with default config of jitsu-charts :

This chart only applies minor changes on top of what Bitnami's ClickHouse chart sets by default, and the default subchart provided services' primary purpose is just to provide a minimal working example. They shouldn't be broken or dysfunctional in any way, but their lifecycle won't be managed beyond what Bitnami provides or what's specifically required by Jitsu, as that falls outside the scope of the chart.
Nevertheless, those tables are managed by ClickHouse itself, which by default doesn't clean up anything. It's possible to configure these to either remove rows after some time or disable them all together. Here are some articles that describe how to do that, and some more general information about these tables:
https://kb.altinity.com/altinity-kb-setup-and-maintenance/altinity-kb-system-tables-eat-my-disk/
https://clickhouse.com/docs/en/operations/system-tables#system-tables-introduction
Whatever configuration changes you want to add can be added to clickhouse.extraOverrides as a string value.


REQ-5: Add OpenAI API.

It will be responsible to generate the dashboard.

We are going to use the gpt-4o-mini


How to run visualize sbml model?

How do I run a visual simulation of an sbml model? I tried tviz.sp_view(r) but that just gives me a static image.

see #187 for an example

Thanks, I got it working


Implement getDefaultBlockSize(Path f) method

Alluxio Version:
2.2.0
Describe the bug
Currently on HDFS interface, Alluxio returns one global block size
regardless of file path, which may not be true. In case different
paths use different HDFS block size, this will cause issues.
  @Override
  public long getDefaultBlockSize() {
    return mFileSystem.getConf()
        .getBytes(PropertyKey.USER_BLOCK_SIZE_BYTES_DEFAULT);
  }

To Reproduce
Expected behavior
Block size should be
It should be replaced by:
  @Override
  public long getDefaultBlockSize(Path path)
  {
    AlluxioURI uri = getAlluxioPath(path);
    try {
      URIStatus status = mFileSystem.getStatus(uri);
      return status.getBlockSizeBytes();
    } catch (AlluxioException | IOException e) {
      throw new RuntimeException(e);
    }
  }

Urgency
Medium
Additional context
This  issue is reported and fix proposed by @iAlaska

close now since we have page store now


Numbering is messed up in one spot

https://eriolhugotest.github.io/devs-guide-to/conducting-a-user-test/#the-structure-

Number 12 should be number 4. In the code it seems ok. I don't know how to fix this.

I figured out how to fix this as it was happening on the synthesis page - it's the machine getting confused between 'li' and 'ol' and 'ul' markdown/html.
take a look here and see if you think this compromise from my local environment is ok:

@smithkelseyj

Added context it's because in the code we had:

text

tips text
across multiple
lines

next point
next point

sub
points

So the machine thinks that the sub lines are also numbered but is asked not to display numbers so doesn't and displays '-' and then starts counting again from 5 because there are 3 -'s after the number 1.
code 🤦

I like the first option!

looks good now!


Forbid usage of object

Is there a rule with that we can forbid the usage of some specific functions or objects like console.log ?

I think such a rule belongs more to a tool like eslint or jshint. jscs is about the format of the code.
If you are only concerned about console, there is a rule in eslint addressing your needs.

@janbaer thanks for contributing. @alawatthe is exactly correct, as JSCS is only concerned with style, and this is better suited for either JSHint or ESLint. Thanks again!

Thanks for the answer. We're using currently jshint but it's not really extendable with custom rules. So we decide to use additionally jscs to have more flexibility with code checks in a semantic way and with formatting. There is a rule that can check for forbidden keywords like debugger in the production code . Why not extend the jscs to check also the usage of some functions. The console was just an example. Before some weeks I used the jasmine function ddescribe to just run a specific test. But I forgot to change it back to describe. So for some days our ci just executed one test. With a check with jscs for example in this wouldn't happen.

So I gave this a second thought. I think a rule like
disallowVariableNames: ['temp', 'foo', 'bar', 'baz', 'asdf']

could make sense, as this is a stylistic choice about the code.
@janbaer This should fit your use case, too.
I am just not a too big fan of a rule like
disallowUseOfObject: ['console']

Since it is impossible to completely prohibit the use of an object through static analysis.
@mikesherov should we reopen this issue?

Duplicate of #41


Make hotkeys configurable

At the moment, all hot keys are hard wired.  Provide a way for users to configure them.

Hi, i have a couple of ideas on how to implement this and i need advice on which one is better.
1:
Have the Global script Create actions in the Input Map for all the hotkeys if they don't exist
This way Users can configure hotkeys in a way they are familiar with but it will add a lot of new actions to the Input Map which may be undesirable
2:
Add a variable for each hotkey to the Global script so users can configure the hotkeys by changing the values of the variables
Feel free to assign me to work on this issue or implement this on your own.


[0.8] getDistributedNodes() does not update when distributed content changes

_distributedNodes array does not get updated when underlying nodes are added/removed.
If you start off with:
    <dom-module id="bug-distributor">
      <template>
        <content id="pcontent" select="p"></content>
      </template>
    </dom-module>

    <bug-distributor>

Paragraph 1

Paragraph 2

Paragraph 3

    </bug-distributor>

bug-distributor.getDistributedNodes().length is 3.
Then you remove all the distributed nodes:
document.querySelectorAll('p').forEach( p.remove())

bug-distributor.getDistributedNodes().length is 3, should be 0.
Is there a workaround, call one can make to update the list of distributedNodes?

I think you should be using Polymer.dom to remove the nodes.

I've tried using Polymer.dom, same result.
    var allPs = document.querySelectorAll('p');
    Array.prototype.forEach.call( allPs, function(p) {
      Polymer.dom((Polymer.dom(p).parentNode)).removeChild(p);
    });

Ah, sorry. I see what's wrong. These operations may be async, so you need to call flush() after removing the children.
Call Polymer.dom.flush() before calling getDistributedNodes the second time:
http://jsbin.com/rusoro/4/edit?html,console,output
I think this was just shorthand in your description, but I believe that getDistributedNodes needs to be called on the content node, not the host element.

Thanks for helping out with this. Still not quite up to speed with Polymer dom.


The && and || are not available now (2023-03)

          The && and || are not available now at 2023-03

I intend to save the expression as data configuration, so that the code does not need to be changed when modifying
Originally posted by @litao09h in https://github.com/tidwall/gjson/issues/64#issuecomment-1461210161

@litao09h I've added a reply to the old issue for the requests raised there, see #64 (comment). If those examples don't cover your use case feel free to expand in this issue what are your needs.

that's helpful , multipaths is work for me.
thank you for the anwser


Not throwing InvalidCountException

I try to use functions related to times() but cannot catch InvalidCountException like this
class HogeTest extends \PHPUnit_Framework_TestCase
{
    /**
     * @expectedException \Mockery\Exception\InvalidCountException
     */
    function test_hoge()
    {
        $t = Mockery::mock('Hoge');
        $t->shouldReceive('test_func')->never();

        $t->test_func();
    }
}

The result is here
$ ./vendor/bin/phpunit HogeTest.php
F

Time: 250 ms, Memory: 5.50Mb

There was 1 failure:

1) HogeTest::test_hoge
Failed asserting that exception of type "\Mockery\Exception\InvalidCountException" is thrown.

FAILURES!
Tests: 1, Assertions: 1, Failures: 1.

Is this a bug or is my usage wrong?

Try using \Mockery::close() after the test_func() method call. This will trigger the mock assertions.

@TiagoMaiaL
It's fine! Thanks a lot :)


fs.isdir latency 200x slower beginning with version 2023.09.01

Hello,
I'm running the following code to measure the latency of isdir:
fs = GCSFileSystem(
    token="google_default", projectstring="..."
)

datadir = "<path to GCS directory with thousands of files>"
filenames = ["gs://" + x["name"] for x in fs.listdir(datadir)][:500]
times = []
for f in tqdm(filenames):
    begin = time.time()

    fs.isdir(f)

    end = time.time()
    times.append(end - begin)

print("Average time: ", sum(times) / len(times))

In version 2023.09.01, the average time per fs.isdir() call is 0.05 seconds. In version 2023.09.00, the average time is 0.0001 seconds. This causes a significant slowdown (from 2 seconds to several minutes) when multiplied by the thousands of files in our GCS directory.
Thank you for your help,
Devin

I can confirm that the directory cache is ot working correctly - will look into it tomorrow.


feat: upgrade to capacitor 6

Discussed in https://github.com/jonz94/capacitor-azure-notification-hubs/discussions/6

Originally posted by Tramb-dev April 27, 2024
Hi,
As Capacitor 6 was recently released, I want to know if you plan to make this great plugin compatible with this new version of Capacitor?
Best regards.

v3.0.0 was just released, and it supports Capacitor 6.
npm i<EMAIL_ADDRESS>
full changelog: https://github.com/jonz94/capacitor-azure-notification-hubs/compare/v2.0.0...v3.0.0


[SPARK-15087][CORE][SQL] Remove AccumulatorV2.localValue and keep only value

What changes were proposed in this pull request?
Remove AccumulatorV2.localValue and keep only value
How was this patch tested?
existing tests

Test build #57623 has started for PR 12865 at commit eab690f.

Test build #57623 has finished for PR 12865 at commit eab690f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57623/
Test FAILed.

@cloud-fan fixed 👍

Test build #57635 has started for PR 12865 at commit cc0a7ff.

Test build #57637 has started for PR 12865 at commit 322f570.

(This is a pretty minor but I think cc @rxin can be removed but in the comments because the PR description explains the PR itself and the names of reviewers might not be related with the PR itself. @ will be removed by Python merge script when merging but cc and mengxr will still remain, eg. https://github.com/apache/spark/commit/4514aebd1e807a665c270bfdc3f1127b3a1da898. Also I remember I was told so by one of committers)

LGTM, cc @rxin for another look

Test build #57635 has finished for PR 12865 at commit cc0a7ff.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57635/
Test FAILed.

Merged build finished. Test FAILed.

Test build #57637 has finished for PR 12865 at commit 322f570.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57637/
Test PASSed.

Thanks - merging in master.


Failed to load the native TensorFlow runtime.

Trying to run a captcha solving python script and got this error;
Traceback (most recent call last):
File "C:\Users\micha\AppData\Local\Programs\Python\Python312\Lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 70, in
from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\micha\Documents\PythonProgramming\IG\pytesseract_solver.py", line 9, in
import tensorflow
File "C:\Users\micha\AppData\Local\Programs\Python\Python312\Lib\site-packages\tensorflow_init_.py", line 37, in
from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow  # pylint: disable=unused-import
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\micha\AppData\Local\Programs\Python\Python312\Lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 85, in
raise ImportError(
ImportError: Traceback (most recent call last):
File "C:\Users\micha\AppData\Local\Programs\Python\Python312\Lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 70, in
from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors for some common causes and solutions.
If you need help, create an issue at https://github.com/tensorflow/tensorflow/issues and include the entire stack trace above this error message.

@MikeyD-rbg,
Could you please provide the tensorflow and the compatible version which you are trying to install. Also there are at least 3 possible scenarios:
- You need to install the MSVC 2019 redistributable
- Your CPU does not support AVX2 instructions
- Your CPU/Python is on 32 bits
- There is a library that is in a different location/not installed on your system that cannot be loaded.

https://github.com/tensorflow/tensorflow/issues/61887
Thank you!


RKE2 Custom Cluster details page taking long time to show after creating a cluster and No Registration command displayed on creation

On 2.6.0-rc1

Deploy rancher server
Deploy a custom RKE2 cluster - enter a name and hit Create
It takes almost like 15 seconds to load the next page. It is stuck in loading
And there is no registration command seen

Note:

But when the user goes back to Cluster Management page and returns to detail page of ^^ custom cluster, registration command is available
Any further custom rke2 clusters have the registration command right after creation

Highly likely related to #3396, specifically incoming fix mentioned in https://github.com/rancher/dashboard/issues/3396#issuecomment-893470097

The second part will be fixed via #3711. The first part is most probably an issue when making the request to saving the provisioning cluster but requires confirmation, specifically having monitoring the request in dev tools network tab. Will mark as fixed to validate fix for second part and confirm network request for first.

Verified on v2.6-head - c47122a
Steps taken to see the issue is fixed:

Fresh rancher setup, created the first custom cluster.
After creation, user is taken to the detail page, and the cluster registration command is immediately available. NO delay.


Update Advisor.json

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@DO-CS Can you check on the appropriate items in the previous comment of the PR

Hi @keryul - I have added a new lowCpuThreshold value "100" to the enum and updated the default value to "100". This change might be treated as a bug fix and should be available for all previous versions.

@konrad-jamrozik should we approve the BreakingChange

@DO-CS you wrote:

and should be available for all previous versions.

But to my understanding that is exactly the problem: it is not available in previous versions, hence it is a breaking change. @rkmanda FYI.


List of pages or frameworks you might think have an rss or atom feed but actually dont. (Or are limited in some way)

Facebook (removed)
Twitter (removed)
9gag (no nativ api)
hackernews (https://news.ycombinator.com) only main feed

note to self: dont use 3rd party sites to provide rss feeds, ... if the site itself has no feeds, ... thats it.


[Bug]: -c flag not working in read-nexus

Contact Details
No response
What happened?
When passing the -c flag in read_nexus, there is no output to the command line.
Relevant log output
No response

@sanbrock maybe you can just share the changes you made during the workshop to get it to work?

I actually used an old version from Aug 31, 2023:
de1cc043e250933173c685f242ac7322845eeac0
with nexus definitions of
81c3229100a9a8b1be4085cf16a65b279975757d

I think the problem is related to which shell you are using.
In git bash, if I pass read_nexus -c /NXarpes/ENTRY/title and print the concept within the HandleNexus class, actually the following path is passed as the concept to the HandleNexus.process_nexus_master_filemethod:
C:/Users/pielsticker/AppData/Local/Programs/Git/NXarpes/ENTRY/title

Somehow, git bash concatenates the shell path with /NXarpes/ENTRY/title.
Whereas if I use the vscode terminal (i.e., powershell), printing of the concept yields:
/NXarpes/ENTRY/title

and the output is correct: INFO: entry/title.

We could get rid of the leading / in /NXarpes/ENTRY/title and slightly modify the function that picks up the concept. That way we would be shell-independant. What do you think @sanbrock @sherjeelshabih?

We could get rid of the leading / in /NXarpes/ENTRY/title and slightly modify the function that picks up the concept. That way we would be shell-independant. What do you think @sanbrock @sherjeelshabih?

We might have to change the idea of a NeXus concept path everywhere in the code then. Otherwise, users will be confused.
We can also try setting this ENV variable in our Python code if we are on Windows:
MSYS_NO_PATHCONV=1
I found this here.


Feature: fake success

Instead of validation errors - even "stealth" ones, I think there should be a way to make it look like the form was submitted successfully. I'm not yet sure how this could work. Maybe an option to throw an exception that can be listened to and converted into/redirected to a "thank you for submitting page"
Ref: https://blog.stefanolaru.com/how-to-make-the-honeypot-field-more-effective (specifically this)

Considered this, but I don't yet really see a way to do this generically from the bundle - it would always require invasive code changes on the form handling end.

I have some ideas on how to utilize the results of running in passive mode, so currently this is blocked by #4

but I don't yet really see a way to do this generically from the bundle

True enough, what I would do (which I believe is currently possible using events), is listen to the validation failed event, throw a custom exception, catch this exception and convert to a homepage redirect with a "thank you for filling out the form" flash message.
Like you say, pretty app specific.

"Fake pass" is now a thing  \o/
https://omines.github.io/antispam-bundle/advanced/#fake-pass


Telemetry SDK: Traces

Our Telemetry SDKs are an open source set of API client libraries that send metrics and trace data to the New Relic platform. This implementation will support the Trace API
Aha! Link: https://newrelic.aha.io/features/RUBY-72

Telemetry SDK supporting Trace version 0.1 was released on Oct 30th.
https://github.com/newrelic/newrelic-telemetry-sdk-ruby/releases.


Improving Twitter API Integration Code - Updating an existing thread feature?

Updating an existing tweet thread
We will not probably need this. But I want to cover this scenario in case a future need arises.
Easy enough to accomplish this by tracking the tweet_id and conversation_id in the custom twitter response that we create for pdf rendering.
So given a conversation_id, we need to find tweets later than a specific tweet_id. We may need to modify the twit_thread.json format a little. Need some direction on this.

Been inactive for 6 days. Is it resolved yet?
If it is, then please Close it.

@Mira-Alf @PuruVJ  any progress?

I still don't understand what this is for 😅


Number with big precision cannot be changed with direct input representation

I have no idea how to title this ticket properly.
Anyway, assume SuperBigDecimalField with maximum fraction length 3 and scientific notation support. Entering 1e-5 will assign the value to be, well, 1e-5 represented by 0,0. Entering exactly that string into the number field will not trigger value change and hence will not modify the value of the number field to be 0.
This should not happen, entering any string should overwrite the value of the field to whatever the value represents. Note this only happens when scientific notation is supported in SuperBigDecimalField.

fixed, and as a side effect numbers entered with scientific notation are no longer reformatted (so 2e-5 stays formatted as 2e-5 even when the cursor leaves)


Rewrite template

Hello, I am using this extension, is there any possibility to rewrite teplate dynamically (I need default sheet2 as well)?
ps. I tried pipe the fs stream, but with no luck.

Hello, actually this is not possible to handle 2 sheets, the focus was really on CSV like replacement.
Nevertheless, I think it could be done by adding some logic to the stream transform like sending to the pipe specific "command" like "new sheet" and catch this in order to end sheet1 and append sheet2 to the zip stream and redirect the input stream to this new sheet stream... Plus the need to handle properly different headers by sheets etc.
I am not planning to do it by myself, but if you want to do a PR, you are welcome and I can help you answering your questions. :slightly_smiling_face:
A good starting point for understanding what is done under the hood:
https://github.com/atomictech/xlsx-write-stream/blob/14600fd47e01c87f5e35303ab76c77451e6b5f5d/src/XLSXWriteStream.js#L59-L89

thanks, I will make a PR if I am able to acomplish  :)


User_Setup_Select.h contents for T-Embed show selected device at a resolution of 240*240

I own three LilyGo boards, a T-Display, a T-Display Touch and a T-Embed and I am having trouble using the TFT_eSPI library when switching to the T-Embed device.
In the User_Setup_Select.h file which is I believe, the file responsible for determining the correct device configuration for the attached board.  The one selected in this file in the Xinyuan-LilyGo/T-Embed git hub respiratory is line 52;
#include <User_Setups/Setup24_ST7789.h>            // Setup file for DSTIKE/ESP32/ESP8266 configured for ST7789 240 x 240
However, the description in the file refers to a display resolution of 240*240, which of course is not correct for the T-Embed board as this has a resolution of 320 x 170.
So this leads me to ask is this the correct configuration file for this device, can you confirm please and explain why the description resolution states 240 x 240.
ta

Updated<TFT_ ESPI>Library. and submit the configuration file to the main branch. Thank you for your support
https://github.com/Bodmer/TFT_eSPI/pull/2510