text:
Many log warnings when changing scale of TextFields inside SwiftUI views

When you dynamically change the scale of a TextField (like when a @State changes) inside a SwiftUI view inside a Settings Panel, a warning appears in the XCode log:
<_TtGC7SwiftUI16PlatformViewHostGVS_P10$1d0f7449832PlatformViewRepresentableAdaptorVS_P10$1d104826024PlatformTextFieldAdaptor__: 0x12576d9e0> has an maximum length (21.666667) that doesn't satisfy min (21.666667) <= max (21.666667).

It also seems to log that warning on every change of scale, so when you change the scale with animation or apply a scale transition to a TextField,  hundreds of warnings are printed on the log.
It seems to happen even when you don't scale the TextField directly (it also happens if you change scale of a View with a child TextField).
I don't think many people use scaling on TextField, but I ended up writing a nice effect using .scale and when I'm using it on a VStack with like, 5 TextFields, I got a ton of warnings.
Oh, thanks for making this package btw. The work you've done for the Swift open source community is ridiculous. Thanks a lot!

I would first make sure that it doesn't happen if you do it directly in a SwiftUI app instead of in a settings view.

@sindresorhus sorry for the delay, I actually tested that, but forgot to include int he bug report, sorry. It doesn't happen when doing that outside the Settings view.

authors: Kinark sindresorhus

repo: sindresorhus/Settings


text:
Add cyber

https://github.com/CipherDogs/awesome-cyber#readme
cyber is a brand new protocol (a procedure that helps computers to do things in a certain way) for adding and searching information onto a knowledge graph (a compilation of facts about something that provides meaning to the user). And rank this information. In other words, it's a decentralized google
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Hey, here just a few things awesome-lint throws:
✖   1:1    Main heading must be in title case                                                        remark-lint:awesome-heading
✖   1:1    Missing file contributing.md                                                              remark-lint:awesome-contributing
✖   1:1    The repository should have "awesome" as a GitHub topic                                    remark-lint:awesome-github
✖   1:1    The repository should have "awesome-list" as a GitHub topic                               remark-lint:awesome-github
✖   9:1    ToC item "Official resource" does not match corresponding heading "Official"              remark-lint:awesome-toc

Hey, here just a few things awesome-lint throws:
✖   1:1    Main heading must be in title case                                                        remark-lint:awesome-heading
✖   1:1    Missing file contributing.md                                                              remark-lint:awesome-contributing
✖   1:1    The repository should have "awesome" as a GitHub topic                                    remark-lint:awesome-github
✖   1:1    The repository should have "awesome-list" as a GitHub topic                               remark-lint:awesome-github
✖   9:1    ToC item "Official resource" does not match corresponding heading "Official"              remark-lint:awesome-toc

@jnmcfly Fixed these errors

@jnmcfly Fixed these errors

source: gharchive/pull-request

authors: deadblackclover jnmcfly sindresorhus

repo: sindresorhus/awesome

license_type: permissive

license_source: github-api


text:
Could open dev tools in packaged app with Cmd+Alt+I

The readme states that there is "no need to guard it for production". I built my Electron app via electron-builder and was able to invoke the dev tools with Cmd+Alt+I (but not F12) after launching the app.
electron-debug is installed as dev dependency.
This is my call to debug:
debug({
  devToolsMode: "detach",
  showDevTools: false
});

Let me know if you need additional information for reproduction.
electron 7.1.11
electron-builder 21.2.0
electron-debug 3.0.2
macOS 10.14.6

This is actually unrelated to electron-debug. Sorry for the noise.

source: gharchive/issue

repo: sindresorhus/electron-debug

license: mit

license_source: bigquery


text:
Fixes #70.

Also:

changed the first test so that it will work with the --color flag added
fixed a hidden bug in the second test - done was called multiple times because the grunt process wasn't killed immediately

Closed and reopened for test rerun.

repo: sindresorhus/grunt-concurrent


text:
Extension options are reset when changing site access

When I change this to "When you click the extension", all my extension options get reset:

That's nuts. It doesn't seem to happen for https://github.com/fregante/github-issue-link-status (but it uses a slightly older webext-options-sync version)

And you've just recommended me another great extension 😄
Yeah, it's really weird but on the plus side for me, I finally found some possible explanation why my token in the extension was disappearing sometimes, I never had anything specific to report so I might have ignored it...

I finally found some possible explanation why my token in the extension was disappearing sometimes

I definitely like this bug report than a "my data is inexplicably lost" issue, I dread that in my https://github.com/fregante/webext-options-sync/

This bug might be related to permissions.onRemoved and the features around GH Enterprise support. Help debugging this would be appreciated.

Well, yeah. This removes the permission to github.com and when you do that, Refined GitHub cleans the options for that domain.
https://github.com/sindresorhus/refined-github/blob/7c5745bb4a7db9c07aceff98f54c58bfb3771838/source/options-storage.ts#L74-L80
PR welcome to filter out github.com from the origins

repo: sindresorhus/refined-github


text:
Drop faster-pr-diff-options feature

https://github.com/sindresorhus/refined-github/issues/3551#issuecomment-692278619

As someone who uses this multiple times a day, why?

As someone who uses this multiple times a day, why?

ohhh its still there on enterprise... did not know that

ohhh its still there on enterprise... did not know that

It's not just on Enterprise, but on any commit. The feature is only disabled on PRs, so the readme is still up to date.

authors: busches fregante yakov116


text:
PUT /events/{id}

Path: /events/{id}
Method: PUT
Description:
Edits an event (name, dates and id)
Auth: COORDINATION
Payload:
{
  name: String,
  begin: Date,
  end: Date,
  id: Number
}

Response:
{
  name: String,
  begin: Date,
  end: Date,
  themes: [String],
  id: Number,
  teams: [Team],
  packages: [{
    template: Package,
    avaliable: Boolean
  }],
  items: [{
    item: Item,
    avaliable: Number
  }],
  meetings: [Meeting],
  sessions: [Session]
}

Notes:

id corresponds to an _id index of mongodb.
All params on payload are optional, but can't be empty

Status codes:

Code
Rule

404
Specified object not found

400
Payload missing fields

200
Otherwise

Tests:

No event with id
Should return a status code 404.

Empty payload
Should return a 400 status code.

Invalid date format(s)
Should return a 400 status code.

Valid info
Should return the updated event.

You shouldn't change the id of an event. This is incremental.

Fixed

Close this: https://github.com/sinfo/deck2/issues/73
Put that functionality here.

Remove the {id} form the URL. We should always modify the latest event (none of the information stored by the event should be changed after it occurs).

Edit:

Removed {id} from URL.
Upped the auth level to COORDINATOR

license: MIT


text:
Fixed: setState() called after dispose()

#50

Thanks!

repo: singerdmx/flutter-quill


text:
[r/ci] Set options(pkgType = "binary") for MacOS

Force binary-only installation for macOS. By setting as an option in ~/.Rprofile; this should affect both package installation and updating through utils::install.packages(), utils::update.packages(), and remotes::install_deps()
resolves #2254

Note:
As the two pbmc3k dataset packages are source-only, I've added a new stanza to install these separately on macOS. This calls a separate R script apis/r/tools/install_missing_deps.R which

finds dependencies of tiledbsoma that were not installed due to the binary-only installation earlier
find the upstream dependencies of the missing packages that are source-only (because Bioconductor)

This stanza runs on macOS only

I'll stay out of it.  I provided a much simpler code example to @mojaveazure that attacked a simpler sub-task and that is what I might have done, but I didn't and I won't rewrite this. If it works it works.

authors: eddelbuettel mojaveazure

repo: single-cell-data/TileDB-SOMA


text:
sqlsmith: Feature is not yet implemented: GreaterThan[Boolean, Varchar]

Describe the bug
test tests::run_sqlsmith_on_frontend ... Panic on SQL:
--
  | SELECT FLOAT '38.88696329213421' AS col_0, INT '24' AS col_1 FROM supplier AS t0, partsupp AS t1, supplier AS t2 WHERE true > t2.s_phone LIKE '9GZdDV5UDG'
  | Reason:
  | panicked at 'Failed to bind:
  | SELECT FLOAT '38.88696329213421' AS col_0, INT '24' AS col_1 FROM supplier AS t0, partsupp AS t1, supplier AS t2 WHERE true > t2.s_phone LIKE '9GZdDV5UDG'
  | Reason:
  | Feature is not yet implemented: GreaterThan[Boolean, Varchar], Tracking issue: https://github.com/singularity-data/risingwave/issues/112', src/tests/sqlsmith/tests/test_runner.rs:95:45
  | FAILED

Shall we allow this test to fail?
To Reproduce
Expected behavior
Additional context

This is the fault of sqlsmith. Techinically, it should wrap the expr tree with necessarh parenthesizes,

I think I've fixed this problem in https://github.com/singularity-data/risingwave/pull/3370 (tested with many rounds), I'm waiting for the CI to complete.

Shall we close this now?

authors: lmatz neverchanje skyzh

repo: singularity-data/risingwave


text:
chore: lifetime error

What's changed and what's your intention?
Similar to #2704,

Refer to a related PR or issue link (optional)
#2704

Suddenly it does not error anymore, let's close it and reopen when needed.


text:
feat(sqlsmith): generate with

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Ran sqlsmith e2e locally.

Summarize your change (mandatory)
Implement gen_with.
How does this PR work? Need a brief introduction for the changed logic (optional)

Control complexity of gen_query by providing terminating branch. This is required because it is mutually recursive with gen_with.
Provide local context for selected query in generated with clause.
Pass with_tables to gen_from. Once we generate with clauses, we expect they are used in the FROM clause.

Describe any limitations of the current code (optional)

Only generate simple with query, we only generate a single CTE. In the future can generate more complex queries if required.

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)
Closes #3959
Workaround for #4025

Describe any limitations of the current code (optional)

Only generate simple with query, we only generate a single CTE. In the future can generate more complex queries if required.

FYI current support of multiple CTEs at different level is incomplete: #3174 This limitation on tests can only be removed after we have finished implementation.

authors: kwannoel xiangjinwu


text:
ref: remove leading spaces in docker run command

Leading spaces in the docker run command prevented successful copy+paste into terminal.

Thanks!

authors: chrisfilo kaczmarj


text:
Long running command does not come back and does not stream

I tried this
SSH("192.168.1.5") {
  client =>
    val result = client.exec("find .").right.get
    val stream = new SequenceInputStream(result.stdOutStream, result.stdErrStream)
    val buff = new BufferedSource(stream)
    buff.getLines().foreach { println }
}

And I do not get what I expect (the results of the find, and it works if I do something smaller, like "ls ~/"). Instead I get a bunch of the following in the log:
21:55:25.621 [reader] DEBUG n.s.s.c.channel.Window$Remote - Increasing by 2097152 up to 2097152
21:55:25.621 [reader] DEBUG net.schmizz.concurrent.Promise - Setting <<chan#0 / chanreq for exec>> to SOME
21:55:25.622 [ScalaTest-main-running-SSHTest] DEBUG net.schmizz.concurrent.Promise - Awaiting <<chan#0 / close>>
21:55:25.633 [reader] DEBUG n.s.s.c.channel.Window$Local - Consuming by 4096 down to 2093056
21:55:25.636 [reader] DEBUG n.s.s.c.channel.Window$Local - Consuming by 4096 down to 2088960
21:55:25.637 [reader] DEBUG n.s.s.c.channel.Window$Local - Consuming by 4096 down to 2084864
21:55:25.640 [reader] DEBUG n.s.s.c.channel.Window$Local - Consuming by 4096 down to 2080768
21:55:25.642 [reader] DEBUG n.s.s.c.channel.Window$Local - Consuming by 4096 down to 2076672
21:55:25.644 [reader] DEBUG n.s.s.c.channel.Window$Local - Consuming by 4096 down to 2072576
21:55:25.645 [reader] DEBUG n.s.s.c.channel.Window$Local - Consuming by 4096 down to 2068480
21:55:25.647 [reader] DEBUG n.s.s.c.channel.Window$Local - Consuming by 4096 down to 2064384
And so on...
It's almost like reading from the streams is not really reading from them.

Thanks for your input!
A better async stream-based API would indeed be great.
Maybe something based on reactive streams (www.reactive-streams.org).

authors: rleibman sirthias

repo: sirthias/scala-ssh


text:
Preview Image

Hello!
I want to add support for bookmark thumbnails. I've made a rough implementation, but I'm not sure I'm going in the right direction. please tell me what else I should consider or change in the code.
todo:

[x] check and fix tests
[x] add more tests
[x] handle relative path in og:image
[x] download previews and serve it from local dir
[x] show preview image in edit form
[x] show preview image in details popup
[ ] squash commits and write good commit message

Thanks for your effort, looks promising but I'll have to take some time to think about how this should work. Some initial thoughts:

Having two fields for storing the preview image (url or downloaded image) feels a bit weird. I can see the benefit though, as that allows showing the preview image right in the form after loading website metadata. And downloading the image later helps in case the website goes offline. Though for a start, maybe just storing the URL would be enough, would also make the PR a bit smaller and easier to review.
Not sure if the image really needs to show up in the create / edit form. It's kind of neat, but also takes up a lot of space.
The bookmark list is kind of hard to read at the moment. Having the images at the start of each row makes it harder to distinguish individual bookmarks in case some of them are missing a preview image. It's also very noisy - preview and favicon are next to each other, preview images have different sizes. I think it would be better to put the images at the end of each line, give them a fixed size, and make each image cover the full size. Quick prototype below. It also takes up a lot of space on mobile, I would consider hiding the preview there.
There needs to be some way to load preview images for existing bookmarks, similar to the refresh favicons button. Makes sense to do this in a separate PR though.

I'll try to take a closer look soon, no need to do any further changes to the PR for now. I might also decide to make some changes directly myself if it turns out to be low effort.

Having two fields for storing the preview image (url or downloaded image) feels a bit weird. I can see the benefit though, as that allows showing the preview image right in the form after loading website metadata. And downloading the image later helps in case the website goes offline. Though for a start, maybe just storing the URL would be enough, would also make the PR a bit smaller and easier to review.

I started with one column, replacing the remote URL with the local URL after downloading. But to do that you have to do schema checks for the URL in many places in the code, which didn't seem as convenient as keeping two links. But yeah, you could keep one field.
But anyways I see it as important to be able to store images locally, as it has many advantages:

external resources won't know about every time I visit my bookmarks;
external sites may respond slowly, making my UX worse;
external sites die regularly.

Perhaps you can make two settings: enabling the preview viewing feature, and enabling the preview download feature, which are independent of each other.

Not sure if the image really needs to show up in the create / edit form. It's kind of neat, but also takes up a lot of space.

Agree

The bookmark list is kind of hard to read at the moment. Having the images at the start of each row makes it harder to distinguish individual bookmarks in case some of them are missing a preview image. It's also very noisy - preview and favicon are next to each other, preview images have different sizes. I think it would be better to put the images at the end of each line, give them a fixed size, and make each image cover the full size. Quick prototype below. It also takes up a lot of space on mobile, I would consider hiding the preview there.

Agree

There needs to be some way to load preview images for existing bookmarks, similar to the refresh favicons button. Makes sense to do this in a separate PR though.

Agree :)

I would consider hiding the preview there

I think that if a person enables previews, they should work on mobiles. Or at least it should be possible to configure it.
My use case implies that I want to see previews on mobile, because I keep many YouTube links and by previews I can read faster what kind of content it is than by description.

To make it a bit simpler I've removed the model field for storing the URL and only kept the field for storing the file. With that it works the same way as the favicons. That means it might take a while until the preview image shows up, basically until the respective task has been run. But that should be fine for regular usage.
Styles could maybe use some tweaking here and there, but should be good enough for a start. Long term it would be good to have an option for showing separators in the bookmark list, I think that would really help with distinguishing the bookmarks and their images from each other. For now some custom CSS could be added as a workaround.
Thanks again for the contribution, apart from some minor tweaks it was pretty complete. Note that it might take me a few weeks to release this, I currently don't have access to the machine where I cross compile the Docker images.

authors: sissbruecker vslinko

repo: sissbruecker/linkding


text:
Add option --custom to perform test with custom servers

Hello. I added the --custom argument so that users can include a URL like https://www.speedtest.net/api/js/servers?engine=js&search=orange&https_functional=true&limit=1 and perform speedtests against a server of their liking.
Update 7/3/2022:

added interoperability feature to make --custom work alongside with --server that way we can choose a specific server from custom link.

For instance, a command like speedtest --custom "https://www.speedtest.net/api/js/servers?engine=js&search=Comcast&https_functional=true" --server 37808 should ping Comcast (Atlanta, GA)

Thank you for this update edseldim, @sivel Please review this pull request its much needed

repo: sivel/speedtest-cli


text:
Error while installing mailmatcher

Hello,
I am running parrot OS, and facing error while installing mailmatcher with gem install mailmatcher. The error thrown is like :
ERROR:  Error installing mailcatcher:
        ERROR: Failed to build gem native extension.

    current directory: /home/arpeetrathi/.gem/gems/eventmachine-1.0.9.1/ext
/snap/bin/ruby -I /snap/ruby/212/lib/ruby/3.0.0 -r ./siteconf20210527-121559-djhbqp.rb extconf.rb
checking for -lcrypto... yes
checking for -lssl... yes
checking for openssl/ssl.h... yes
checking for openssl/err.h... yes
checking for rb_trap_immediate in ruby.h,rubysig.h... no
checking for rb_thread_blocking_region()... no
checking for ruby/thread.h... yes
checking for rb_thread_call_without_gvl() in ruby/thread.h... no
checking for inotify_init() in sys/inotify.h... yes
checking for writev() in sys/uio.h... yes
checking for rb_thread_fd_select()... no
checking for rb_fdset_t in ruby/intern.h... yes
checking for pipe2() in unistd.h... yes
checking for accept4() in sys/socket.h... yes
checking for SOCK_CLOEXEC in sys/socket.h... yes
checking for rb_wait_for_single_fd()... no
checking for rb_enable_interrupt()... no
checking for rb_time_new()... no
checking for sys/event.h... no
checking for epoll_create() in sys/epoll.h... yes
checking for clock_gettime()... yes
checking for CLOCK_MONOTONIC_RAW in time.h... yes
checking for CLOCK_MONOTONIC in time.h... yes
CXXFLAGS= -Wall -Wextra -Wno-deprecated-declarations -Wno-ignored-qualifiers -Wno-unused-result -Wno-address
creating Makefile

current directory: /home/arpeetrathi/.gem/gems/eventmachine-1.0.9.1/ext
make DESTDIR\= clean

current directory: /home/arpeetrathi/.gem/gems/eventmachine-1.0.9.1/ext
make DESTDIR\=
compiling binder.cpp
compiling cmain.cpp
compiling ed.cpp
compiling em.cpp
em.cpp: In member function ‘void EventMachine_t::_RunEpollOnce()’:
em.cpp:631:13: error: ‘rb_thread_select’ was not declared in this scope; did you mean ‘rb_thread_fd_select’?
  631 |  if ((ret = rb_thread_select(epfd + 1, &fdreads, NULL, NULL, &tv)) < 1) {
      |             ^~~~~~~~~~~~~~~~
      |             rb_thread_fd_select
In file included from project.h:165,
                 from em.cpp:23:
em.h:29:22: error: ‘rb_thread_select’ was not declared in this scope; did you mean ‘rb_thread_fd_select’?
   29 |     #define EmSelect rb_thread_select
      |                      ^~~~~~~~~~~~~~~~
em.cpp:673:3: note: in expansion of macro ‘EmSelect’
  673 |   EmSelect (0, NULL, NULL, NULL, &tv);
      |   ^~~~~~~~
em.cpp: In member function ‘int SelectData_t::_Select()’:
em.h:29:22: error: ‘rb_thread_select’ was not declared in this scope; did you mean ‘rb_thread_fd_select’?
   29 |     #define EmSelect rb_thread_select
      |                      ^~~~~~~~~~~~~~~~
em.cpp:941:9: note: in expansion of macro ‘EmSelect’
  941 |  return EmSelect (maxsocket+1, &fdreads, &fdwrites, &fderrors, &tv);
      |         ^~~~~~~~
em.cpp: In member function ‘void EventMachine_t::_RunSelectOnce()’:
em.h:29:22: error: ‘rb_thread_select’ was not declared in this scope; did you mean ‘rb_thread_fd_select’?
   29 |     #define EmSelect rb_thread_select
      |                      ^~~~~~~~~~~~~~~~
em.cpp:1065:6: note: in expansion of macro ‘EmSelect’
 1065 |      EmSelect (0, NULL, NULL, NULL, &tv);
      |      ^~~~~~~~
make: *** [Makefile:237: em.o] Error 1

make failed, exit code 2

Gem files will remain installed in /home/arpeetrathi/.gem/gems/eventmachine-1.0.9.1 for inspection.
Results logged to /home/arpeetrathi/.gem/extensions/x86_64-linux/3.0.0/eventmachine-1.0.9.1/gem_make.out

Btw , my

ruby version - ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-linux]
gem version - 3.2.15

How can I fix it, at many places I searched for it . And it was mentioned to install the thin package with gem. I tried but, no use because there was similar error like this.
Thank You In Advance <3

Sounds like Parrot OS is based on Debian, have you tried:
apt install build-essential ruby-dev

I notice ruby is installed via snap, perhaps there's a way to install the headers with snap instead?

Should I install it with apt install build-essential ruby-dev? Than try to install mailmatcher with gem? Or that won't change anything ?

Damn, after installing it with
apt install build-essential ruby-dev
and than executing gem install mailmatcher produce following error :
ERROR:  Could not find a valid gem 'mailmatcher' (>= 0) in any repository
ERROR:  Possible alternatives: rspec-mail-matchers, rspec-mail_matcher, mailcatcher, mail_fetcher, mailsnatcher, ada_matcher, image_matcher, imatcher, mailMapper, mail_hatch

What's mailmatcher?

Oh yes. Sorry same error like the previous one! :(
The one which I mentioned in first message.

Damn, after installing it with
apt install build-essential ruby-dev
and than executing gem install mailmatcher produce following error :
ERROR:  Could not find a valid gem 'mailmatcher' (>= 0) in any repository
ERROR:  Possible alternatives: rspec-mail-matchers, rspec-mail_matcher, mailcatcher, mail_fetcher, mailsnatcher, ada_matcher, image_matcher, imatcher, mailMapper, mail_hatch

This error was due to my typo. So sorry no such error.

Sorry I'm not sure what's wrong 😔

:disappointed:

This is not a mailcatcher issue, please install the ruby and development tools appropriate for your platform.


text:
[warn] https://d1.web2.qq.com/channel/poll2 请求失败: 502 Bad Gateway

已更新到1.6.6
TX真。。

更新到1.6.6 还会502 bad gateway吗？

恩。。就是更新到1.6.6还是502

@F0ur 会不会是你那边局部网络的问题，因为我这边访问这个api都是正常的，可以多试试几次看看？

@sjdy521 问题找到了，登录参数设置
security设置为1
就会有这个问题，关了就好了。。

这让我联想到腾讯的smartqq的js代码里的这几行，把所有https的请求都替换为http了
又把所有d.web2.qq.com都替换为d1.web2.qq.com了，这种细节，我没怎么去关注，看来新的d1.web2.qq.com接口不支持https的样子
this.require = function(E) {
            var G = E.data || E.param || {},
            O = E.url,
            u = E.action,
            s = E.https,
            A;
            if (/^(http|https):\/\/d.web2.qq.com/.test(O)) {
                O = O.replace(/https/, "http");
                if (A = g.cookie.get("uin")) {
                    A = A.replace("o", "");
                    O = O.replace(/^http:\/\/d.web2.qq.com/, "http://d1.web2.qq.com")
                }
            }

只能说Web QQ的代码写极其糟糕。。


text:
Add support for React 19

Describe the solution you'd like
React 19 was just released. It would be great if mdx-mermaid would support this version as peer dependency.

Released in v2.0.3

authors: rothsandro sjwall

repo: sjwall/mdx-mermaid


text:
Judge real-time data

I have a csv training data, when I don't know how to use my trained model to predict my network real-time data.

I seem to have found a way, Thank you very much for the project team

repo: sjwhitworth/golearn


text:
Bitbucket:583 使用許諾の再表示

MnMnで出来てたことがなぜできてないのか。
(まぁ時間的な都合だけど)

BitBucket から移植

項目
内容

元課題
#583

起票日時
2020-03-13T23:15:31Z

起票者
sk_0520

あかん、めんどい

BitBucket から移植

項目
内容

元コメント
#583 コメント

コメント日時
2020-03-20T12:01:30Z

コメントユーザー
sk_0520

license: WTFPL


text:
Change log for latest release

Preparing 0.1.4 release

Includes package documentation

Great, just check the docs for getting started are accurate.  E.g. for installing from PYPI is no longer "in the near future", and remove duplication from the readme.

@ajoubertza / @kmadisa , Ready for release.

authors: Athanaseus ajoubertza

repo: ska-sa/tango-simlib


text:
chore(react): Updates peerDependencies to allow React 16

[x] Chore/Feature

Rationale
Allows React 16 to be used without warnings

Thanks!

Published!

🙇

authors: deini treshugart

repo: skatejs/skatejs


text:
Test report not sending to Testrail with cypress:run --browser chrome command

Everything is fine when I run my tests with cypress:run command in headless electron
but when I run tests using cypress:run --browser chrome then the plugin is not sending the report to Testrail! Any configuration change needed to make it workable with chrome?

From my observation I've found that it is not related to any browser issue.
It doesn't work when the video property is set to video: false  in cypress.json.

Ah! finally found that it doesn't work in single run mode. If anyone wants to send the report when using chrome as the browser then just use  cypress run  --browser chrome --no-exit flag.

Finally It works on me, using chrome browser: yarn cypress run --browser chrome

authors: canrosinabutar iamsjn


text:
Enhancement: Drawer

Describe the feature in detail (code, mocks, or screenshots encouraged)
Need prop for managing Esc button action activity.
The component is multifunctional but without a hack for global keyboard listening on side module, we can't use it like a loading screen, anyone can close it wherever he wants.
What type of pull request would this be?
None
Provide relevant links or additional information.
No response

@Mero-Plaform first off I'm going to have to ask you slow down on the posts. Skeleton is open source, and we are glad to accept feature requests. But I would ask that you pace yourself. We're a small team and can only do so much at a time. If you would like to create a thread in Discussions to run a few ideas by me and the team, we would be happy to discuss a few things we might consider. But the shotgun approach isn't the right way to go about this.
Also keep in mind that Skeleton is open source, we do encourage community members to not only request features, but actively contribute them to help everyone. We take our contribution guidelines very seriously, which can be found here:
https://www.skeleton.dev/docs/contributing
Per this issue, this is not likely something we would be interested in implementing. Skeleton leans into accessibility and base a lot of functionally off the WAI-ARIA APG guidelines. Per most components we implement a link to the guidelines for each feature via a button like this on the doc page:

Here's where this leads for Drawers:
https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/
Per the accessibility outlines the ESC button works as intended. Diverting from that would be harmful to the accessibility guidelines. If you need or want different behavior you'll need to clone our feature (we're open source, you can do this) or implement your own approach.

repo: skeletonlabs/skeleton


text:
feat: update report function to report multiple objects

Resolves #21

This change is shelved until we've explored the design and native implications, and additionally explored how it relates to violation ignoring.

Parent branch has diverged sufficiently such that this branch and PR is going to be a pain to merge. I'm going to re-make it and cherry pick what I need.

repo: sketch-hq/sketch-assistants


text:
Enabled plugin to work with grunt 1.0.0

Updated dependencies and listed the peerDependencies based on the recommendations to allow the plugin to work with npm 2
This pull request fixes #23

@skhatri please have a look.

Please merge this PR.

repo: skhatri/grunt-sonar-runner


text:
[Bug] Step 1.3 Search for "Simple workflow".

Describe the bug
Step 1.3 Search for "Simple workflow" isn't visible in the Actions tab until clicking New Workflow.  This wasn't obvious (at least to me) and isn't mentioned in the write up.
To Reproduce
Steps to reproduce the behavior:

Try to follow the steps described in Step 1

Expected behavior
Step 3 could read : Click new workflow and then search for "Simple workflow"

Hi. I think I noticed the same mismatch and submitted the following PR. Does this resolve your concern?

https://github.com/skills/continuous-integration/pull/6

I believe this issue was resolved by https://github.com/skills/continuous-integration/pull/6/files, but let us know if the issue persists.

authors: heiskr liam-parker-risk parroty

repo: skills/continuous-integration


text:
ClientConnectorCertificateError when running myskoda gen-fixtures on Windows

I tried running the myskoda gen-fixtures on my Windows machine after installing Python (version 3.13)  and myskoda (version 0.8.1).
Unfortunalty this gives a ClientConnectorCertificateError
aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host identity.vwgroup.io:443 ssl:True [SSLCertVerificationError: (5, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1020)')] 2024-10-16 20:11:12 NB0781 asyncio[27264] ERROR Unclosed client session client_session: <aiohttp.client.ClientSession object at 0x0000022A5DA91400>
I am wondering if this is  a myskoda or a general Python issue...
And if this is to be fixed with not much effort

This is a general Windows issue, which I think a quick search on stackoverflow can help solve. The issue here is, that Windows for some reason does not trust the certificate served by the authentication server of Skoda/Volkswagen

Yeah....
My browser (Edge) does not have any issues with the certififcate for identity.vwgroup.io
I tried something with certifi to add the certificate to the Python store, but also that did not help.
Will ook into this some more in hope to get this fixed locally.

It seems my 'fix' with certifi did the job.. but I had to restart/reboot my system as well.
I will close this issue

authors: WebSpider reharmsen

repo: skodaconnect/myskoda


text:
fix(core): fix ResXmlGenTest fails on Windows

The ResXmlGenTest always failed on Windows because of paths using backslash instead of slash and generated XML content containing \r\n but only \n was expected.

Oh, thanks.
Look like we really need to implement line break options (already requested in #1948) and set it to fixed value for tests.
Also, I will add windows build host for tests in github workflows.

@jpstotz I added tests run on windows host (868e99e), but also I add .gitattributes file to always use unix line breaks. So looks like we don't need part about autocrlf option in code format wiki. And it will be nice if you can verify that my changes not broke/interfere with git autocrlf option :slightly_smiling_face:

@skylot Great, that simplifies the whole process for Jadx developers on Windows. Just tried it, performed a fresh git clone (my default git CRLF settings is the system default) and all files were cloned using Linux (LF) only mode. Executing gradlew spotlessApply on this repo (which previously caused all line endings to be converted to LF which means all files had changes) and a git diff afterwards did not show any changes. Therefore the .gitattributes definition seem to work well. I did not know that git provides such an easy way for solving the line ending problem, thanks.

authors: jpstotz skylot

repo: skylot/jadx


text:
entt.wiki has filenames with : in them, which probably causes problems with Git on Windows

Cloning the entt.wiki project causes problems with Git 2.45.2.windows.1 on Windows.
Here's a shell session showing the issue:
$ git clone https://github.com/skypjack/entt.wiki.git entt_wiki

Cloning into 'entt_wiki'...
remote: Enumerating objects: 1374, done.
remote: Counting objects: 100% (3/3), done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 1374 (delta 0), reused 0 (delta 0), pack-reused 1371
Receiving objects: 100% (1374/1374), 578.79 KiB | 7.52 MiB/s, done.
Resolving deltas: 100% (913/913), done.
error: invalid path 'Crash-Course:-configuration.md'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

$ cd entt_wiki
$ git status

On branch master
Your branch is up to date with 'origin/master'.

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        deleted:    Crash-Course:-configuration.md
        deleted:    Crash-Course:-containers.md
        deleted:    Crash-Course:-cooperative-scheduler.md
        deleted:    Crash-Course:-core-functionalities.md
        deleted:    Crash-Course:-entity-component-system.md
        deleted:    Crash-Course:-events,-signals-and-everything-in-between.md
        deleted:    Crash-Course:-graph.md
        deleted:    Crash-Course:-poly.md
        deleted:    Crash-Course:-resource-management.md
        deleted:    Crash-Course:-runtime-reflection-system.md
        deleted:    Crash-Course:-service-locator.md
        deleted:    EnTT-and-Unreal-Engine.md
        deleted:    EnTT-in-Action.md
        deleted:    Frequently-Asked-Questions.md
        deleted:    Home.md
        deleted:    Push-EnTT-across-boundaries.md
        deleted:    Similar-projects.md
        deleted:    _Footer.md

$ _

Issuing git restore --source=HEAD :/ just repeats the problem.
I can't say that I know, but perhaps this problem is caused by colons : in some of the filenames?
I've read on the Internet (StackOverflow #63727594) that this can perhaps be worked around by flipping some magical NTFS-setting in git. I haven't tried it. My hope is this issue report will have a similar but more wide-spread effect : )
Cheers!
Kind regards
/kraybit

I didn't even know cloning the wiki was possible 😅 why are you doing it btw? All wiki files are in the main project too.

Yeahno, the entt.wiki repos isn't "available", as far as I can see, but I found this little button in the lower right corner:

Perhaps this could be seen as a Github bug, really?
Either way, the reason I tried to clone it was twofold:

In case I'd like to make a PR. But I understand/respect that's not supported.
Just nice to have locally (Think in case of no Internet connection)

Hm, to be honest, as far as I'm concerned, you can close this -- it's a non-issue. Sorry for taking up time.
Cheers!
Kind regards
/kraybit

The wiki is in the main project because the same doc is also used for doxygen. So, it's not the wiki, technically speaking. It's also the wiki 🙂 if you get what I mean.  Btw I never realized GH wikis can be forked, really. TIL something I didn't expect. 😅
That said, don't worry. I'll be away for a few days in August, so I can't look into it right away. However, feel free to leave the issue open and I'll take a quick look at it when I'm back. If it can be fixed, well, why not then. I'll close the issue if it gets too complicated otherwise. 🤷♂

I can't say that I know, but perhaps this problem is caused by colons : in some of the filenames?

Sorry for the late reply. You were right! Removed the colons and managed to clone it properly.
A double check would be appreciated though. Also, thanks for pointing this out! 🙏

authors: kraybit skypjack

repo: skypjack/entt


text:
fix: support new select menu types

Discord added channel, role, user, mentionable select menus. This pr adds support for these.

And did you also update any other package using the library?

Sorry, but I don't understand what I need to do to fix that

This:

Don't worry, I'm updating it myself while I check if the types are right on my editor.

authors: Bobby-McBobface kyranet

repo: skyra-project/archid-components


text:
Feature/add tests

Closes #16

npm run test:webpack and npm run test:router are now broken. I should rename them to npm run playground:* since they aren't tests per se.

repo: skyrpex/vue-jsx-hot-loader


text:
Addiontal let user select part of photo which one will be profile photo

Container(
                  width: 150,
                  height: 150,
                  decoration: BoxDecoration(
                    shape: BoxShape.circle,
                    color: Colors.white,
                    image: DecorationImage(
                      fit: BoxFit.fill,
                      image: FileImage(photo!),
                    ),
                  ),
                ),

use CircleAvatar

lib/utilites/crop_image/crop_image.dart  ---> where is function
lib/view/app/account/editprofile/view/edit_profile_view.dart ---> where is used
https://pub.dev/packages/image_cropper ---> package
helpful sources
https://www.youtube.com/watch?v=nIMfayjbE4k


text:
Added basic authentication when requesting data.

As requested by some people in the community and also see issue #2

could the basic authentication pull please be added to main please? I can't connect to my Piko 5.5 due to authentication issues

@gerosil do you know the firmware version of your inverter?
I can rebase this changes to the main branch then you can test if it would solve your issue, if you like.
Currently this is untested code and I need someone to test it.

@gerosil do you know the firmware version of your inverter? I can rebase this changes to the main branch then you can test if it would solve your issue, if you like. Currently this is untested code and I need someone to test it.
you can also try https://github.com/scheidtdav/homeassistant-kostal-piko since that will be integrated into HA directly in the future which makes this integration obsolete.

I have fw 3.75. Happy to test your Code. I will also look into mentioned repository, though i fear it requests newer FW for PIKO 5.5

Can you please show the output of your error log please? I fear you have to use this integration https://github.com/rcasula/kostalpiko-homeassistant

yeah, guess I have to stick with the scraping mechanism. FW3.x doesn't have any API. Thanks, anyway


text:
Quill does not use  for bullet lists

Steps for Reproduction

Visit this playground

https://quilljs.com/playground/snow#codeN4Ig9AlgdgJgpgDwHQAsAuBbANiAXCAHhggDcACCGAXgB0Q5i0B7AJzoD4CxiT2ap+BAM4BjFhAAOaMkJYja4aPGQArIRy6jxU9iAA0i2IiRq8IEUyhDpARwCuELFjJUyUOAHcyARQdOAFADkAMQMEMwsgXpkwPxkZBhMMHZYcEK4MXHxZMxMWABGAIYsGQDaWdlkpcBkWBDWGYGs8CwMgWQAvtE1dQ1kgfkpqWjtHQC6ehVkE1ldWWgocBhwjUJQTB5R-B0AlADc-Pz2jlhIlkFoiGgAtCIohVAA5nBRZP47LuyZUPEWVnlwJBYJiPfzHJxIFhMJhoJDQdwsAASABUALIAGX2232IA6QA

Open browser console
Insert a bullet list in the playground
You should get the output

Try this output in other systems, e.g. JsFiddle ( https://jsfiddle.net/j47v6rf9/ )
See that other systems will render an ordered list ( numbers, not bullets )

Expected behavior:
I would expect Quill to output an unordered list for bullet lists
Actual behavior:
Quill uses ordered lists with a data-list="bullet" tag
Version:
Latest

Seems to be a duplicate of #4437 and #3957

repo: slab/quill


text:
gldcore/autotest/test_modify.glm fails intermittently

Problem description
The validation test for #input modify fails intermittently with the following error:
ERROR    [2020-01-01 00:00:00 UTC] : assert:1: assert failed on  test.var. +2 == +2
ERROR    [2020-01-01 00:00:00 UTC] : commit_all() failure: object assert:1 commit failed

Changing the variable type from double to char32 makes the test reliable. The problem remains but it's much less visible now.

repo: slacgismo/gridlabd


text:
Rename docs/Weather-subcommand.md to docs/Subcommand/Weather.md

This PR allows links to weather subcommands from develop.
Current issues
None
Code changes
None
Documentation changes

Moved weather subcommand markdown file to folder consistent with develop branch.

Test and Validation Notes
None

It looks like this PR was already merged into master. Closing due to no changes.


text:
New AWS Lambda Example error: Failure: serverlessExpress is not a function

Description
Due to the new guidelines about the deprecation of aws-serverless-express - i've updated my code to the new app.js example, as well as updated @slack/bolt to 3.2.0. I have the latest @vendia/serverless-express@3.4.0. Here is my npm list of serverless - (does it need to not be a dependency of aws-serverless-express@3.4.0 ?)
_user$ npm list @vendia/serverless-express
myl-app@1.0.0 /Library/WebServer/Documents/App/my-app
└─┬ aws-serverless-express@3.4.0
  └── @vendia/serverless-express@3.4.0_

-- running my app code that worked before the updgrade, i receive this error:
**offline: POST /slack/events (λ: slack)
offline: Failure: serverlessExpress is not a function
TypeError: serverlessExpress is not a function
    at Object.<anonymous> (/Library/WebServer/Documents/App/my-app/app.js:60:26)
    at Module._compile (internal/modules/cjs/loader.js:1137:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
    at Module.load (internal/modules/cjs/loader.js:985:32)
    at Function.Module._load (internal/modules/cjs/loader.js:878:14)
    at Module.require (internal/modules/cjs/loader.js:1025:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at /Library/WebServer/Documents/App/my-app/node_modules/serverless-offline/dist/lambda/handler-runner/in-process-runner/InProcessRunner.js:145:133
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at InProcessRunner.run (/Library/WebServer/Documents/App/my-app/node_modules/serverless-offline/dist/lambda/handler-runner/in-process-runner/InProcessRunner.js:145:9)**

Thinking that it was my code that caused the issue, i just ran the exact code from here: https://github.com/slackapi/bolt-js/blob/main/examples/deploy-aws-lambda/app.js
Still getting the same error.
Here is the serverless local app start:
_Serverless: Deprecation warning: Starting with next major version, default value of provider.lambdaHashingVersion will be equal to "20201221"
            More Info: https://www.serverless.com/framework/docs/deprecations/#LAMBDA_HASHING_VERSION_V2
Serverless: Deprecation warning: Starting with next major version, API Gateway naming will be changed from "{stage}-{service}" to "{service}-{stage}".
            Set "provider.apiGateway.shouldStartNameWithService" to "true" to adapt to the new behavior now.
            More Info: https://www.serverless.com/framework/docs/deprecations/#AWS_API_GATEWAY_NAME_STARTING_WITH_SERVICE
offline: Starting Offline: dev/us-east-1.
offline: Offline [http for lambda] listening on http://localhost:3002
offline: Function names exposed for local invocation by aws-sdk:
           * slack: serverless-bolt-js-dev-slack

   ┌─────────────────────────────────────────────────────────────────────────┐
   │                                                                         │
   │   POST | http://localhost:3000/slack/events                             │
   │   POST | http://localhost:3000/2015-03-31/functions/slack/invocations   │
   │   GET  | http://localhost:3000/slack/install                            │
   │   POST | http://localhost:3000/2015-03-31/functions/slack/invocations   │
   │   GET  | http://localhost:3000/slack/oauth_redirect                     │
   │   POST | http://localhost:3000/2015-03-31/functions/slack/invocations   │
   │                                                                         │
   └─────────────────────────────────────────────────────────────────────────┘

offline: [HTTP] server ready: http://localhost:3000 🚀
offline:
offline: Enter "rp" to replay the last request_

Your help is greatly appreciated. Thank you very much for your attention :-)
Andy
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[X] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[X] I've read and agree to the Code of Conduct.
[X] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
@slack/bolt 3.2.0
@vendia/serverless-express@3.4.0
node version: v12.18.3
OS version(s): mac os sierra 10.12.6 (16G2136)
Steps to reproduce:
1.Follow the steps here exactly: https://slack.dev/bolt-js/deployments/aws-lambda
2.
3.
Expected result:
Local app to process Slack request / input
Actual result:
Error processing the Slack request / input
offline: POST /slack/events (λ: slack)
offline: Failure: serverlessExpress is not a function
TypeError: serverlessExpress is not a function
    at Object.<anonymous> (/Library/WebServer/Documents/HeyAxl/hey-axl-app/app.js:60:26)
    at Module._compile (internal/modules/cjs/loader.js:1137:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
    at Module.load (internal/modules/cjs/loader.js:985:32)
    at Function.Module._load (internal/modules/cjs/loader.js:878:14)
    at Module.require (internal/modules/cjs/loader.js:1025:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at /Library/WebServer/Documents/HeyAxl/hey-axl-app/node_modules/serverless-offline/dist/lambda/handler-runner/in-process-runner/InProcessRunner.js:145:133
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at InProcessRunner.run (/Library/WebServer/Documents/HeyAxl/hey-axl-app/node_modules/serverless-offline/dist/lambda/handler-runner/in-process-runner/InProcessRunner.js:145:9)

Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

This looks a duplicate with #804

repo: slackapi/bolt-js


text:
Help with building add-on slack bots into my product

Hi,
I am working on cloud-based integration product.
I want to develop add-on bot capabilities (if users are interested, they can subscribe for slack bots that can notify on certain events like high memory consumption, long running task without any output, etc).
I am presently working on this use-case:
- A message arrives at a slack channel.
- Based on the message (if it contains few phrases), I want to ask follow-up questions.
- Based on the responses, I want to perform the action.
May I know whats the best way to achieve my above use case, and also to build intelligent slack bots?  Any references that I can go through?

👋 Hi @Syed-SnapLogic, thanks for asking the question!
Utilizing the Events API feature would be the way to go for your use case: https://slack.dev/java-slack-sdk/guides/events-api Your app can subscribe to the "message" events and your event listener can do anything (such as sending a reply message in the channel or DM) in response to incoming requests from Slack.
Feel free to write in if you have any follow up questions!

Thanks v much for the response.  The latest artefacts available at Maven are 1.21.2.  However, are you aware of the CVEs?  https://mvnrepository.com/artifact/com.slack.api/bolt-socket-mode/1.21.2
Any plans/roadmap to address those?  Because if we use these artefacts in my project, we have vulnerability scanner that could highlight the risks of using these slack SDKs.

I created a slack app with socket mode enabled.  And I developed this java app to reply to messages.  The code is here: https://github.com/Syed-SnapLogic/SyedsPublicRepo/tree/master/slackbot
Note: I have hidden the app and bot tokens in my source code.
When I launch the app, I continuously get this error:

Can you help me getting a working app both in socket mode, and in non-socket mode?  I am willing to get on a zoom call and discuss if needed.  Let me know.

@Syed-SnapLogic I'm glad to hear that you've figured all the things out here!

If I need more help in building bots, I shall surely reach out to you. Let me know if this is the best way to reach out to you (via raising issues) or you prefer other means.

When you have new questions on how to use this SDK and/or feedback to this SDK, please feel free to open a new issue here. Another place to ask questions would be community.slack.com workspace. #lang-java #tools-bolt and some other channels should be helpful for you. If you haven't joined the workspace, you can join from this link.
Let me close this issue now.

I am unable to use this link https://j.mp/community-slack.com.
It takes me to bitfly page (where I created new account) but still don't know how to get along from there.

@Syed-SnapLogic sorry, the link was invalid. Corrected ✅

I joined, thnx.

authors: Syed-SnapLogic seratch

repo: slackapi/java-slack-sdk


text:
Add more tutorials and sample code

What tutorials or sample code would you like to see?
I want to build a #Slack app for you! Tell me about a workflow that you'd like to see built. If it's useful for others, I'll create a tutorial in Github on how to build it using this SDK. This will be similar to the existing tutorial that can be found here.
What type of issue is this?

[x] enhancement (feature request)
[x] documentation related
[x] discussion

Flask + Slack dialogs with the example of the "coffee order"

As we will do this separately in collaboration with the Slack's DevRel content team, let me close this issue now.
In addition to the PythOnBoardingBot tutorial, I've added some working samples here: https://github.com/slackapi/python-slackclient/tree/master/integration_tests/samples
If you're looking for complete versions of code snippets in this library's documents, access those samples.

authors: RodneyU215 seratch tobenary

repo: slackapi/python-slackclient


text:
When a Markdown Formatting Symbol has been registered, a double space in empty SLKTextView results in a NSRangeException

As the very descriptive title suggests, when a Markdown Formatting Symbol has been registered, a double space in empty SLKTextView results in a NSRangeException
To reproduce:

Add pod 'SlackTextViewController' to your project
Use an empty SLKTextViewController subclass that implements [self.textView registerMarkdownFormattingSymbol:@"*" withTitle:@"Bold"]; in - (void)viewDidLoad
Enter a double space in the SLKTextView in your SLKTextViewController subclass
The NSRangeException will occur

Note:

I also tested if the /Examples have the same problem, but the NSRangeException does not occur for pod 'SlackTextViewController', :path => '../SlackTextViewController.podspec' (obviously when you use pod 'SlackTextViewController' instead, the NSRangeException does occur)
Checked on iOS 8.4 and iOS 9.3 simulators and have number of crash reports from users ranging from iOS 7.1.2 to iOS 9.2.1

Hope this makes it clear how to reproduce the issue :)
Rgds,
Brecht Bakker

Great, thanks for checking it out :)

repo: slackhq/SlackTextViewController


text:
Remove LogMessage and use Trace.Span to create lucene documents

Summary
Part 3 - This PR aims to standardize the Trace.Span format the indexer knows how to parse into a lucene document.
The preprocessor today creates Trace.Span objects. In https://github.com/slackhq/kaldb/pull/778 we will add field type info for each field and we want the ability to reference that to create a lucene document.
Removing LogMessage which today adds an indirection makes this tougher.
Kaldb Schema PR breakdown - 5 part series to introduce schema configs to Kaldb

introduce a concept of int and float to trace.proto
remove the concept of index transformer - it's always trace.span
use trace.span to create lucene documents instead of LogMessage
insert schema info to trace.proto in the preprocessor
leverage schema in the indexer

Some Trace.Span objects for posterity when we fix nested fields
 Trace.Span span =
        Trace.Span.newBuilder()
            .setId(ByteString.copyFromUtf8("1"))
            .addTags(
                Trace.KeyValue.newBuilder()
                    .setVStr("Test message")
                    .setKey(LogMessage.ReservedField.MESSAGE.fieldName)
                    .setVType(Trace.ValueType.STRING)
                    .build())
            .addTags(
                Trace.KeyValue.newBuilder()
                    .setVStr("duplicate1")
                    .setKey("duplicateproperty")
                    .setVType(Trace.ValueType.STRING)
                    .build())
            .addTags(
                Trace.KeyValue.newBuilder()
                    .setVFloat32(3.0f)
                    .setKey(floatStrConflictField)
                    .setVType(Trace.ValueType.FLOAT32)
                    .build())
            .addTags(
                Trace.KeyValue.newBuilder()
                    .setVStr("value1")
                    .setKey("nested.leaf1")
                    .setVType(Trace.ValueType.STRING)
                    .build())
            .addTags(
                Trace.KeyValue.newBuilder()
                    .setVStr("value2")
                    .setKey("nested.nested.leaf2")
                    .setVType(Trace.ValueType.STRING)
                    .build())
            .addTags(
                Trace.KeyValue.newBuilder()
                    .setVInt32(3)
                    .setKey("nested.nested.leaf21")
                    .setVType(Trace.ValueType.INT32)
                    .build())
            .addTags(
                Trace.KeyValue.newBuilder()
                    .setVInt32(1)
                    .setKey("nested.nested.nestedList")
                    .setVType(Trace.ValueType.INT32)
                    .build())
            .build();

and
Trace.Span span2 =
            Trace.Span.newBuilder()
                    .setId(ByteString.copyFromUtf8("1"))
                    .addTags(
                            Trace.KeyValue.newBuilder()
                                    .setVStr("Test message")
                                    .setKey(LogMessage.ReservedField.MESSAGE.fieldName)
                                    .setVType(Trace.ValueType.STRING)
                                    .build())
                    .addTags(
                            Trace.KeyValue.newBuilder()
                                    .setVStr("duplicate1")
                                    .setKey("duplicateproperty")
                                    .setVType(Trace.ValueType.STRING)
                                    .build())
                    .addTags(
                            Trace.KeyValue.newBuilder()
                                    .setVStr("blah")
                                    .setKey(floatStrConflictField)
                                    .setVType(Trace.ValueType.STRING)
                                    .build())
                    .addTags(
                            Trace.KeyValue.newBuilder()
                                    .setVStr("value1")
                                    .setKey("nested.leaf1")
                                    .setVType(Trace.ValueType.STRING)
                                    .build())
                    .addTags(
                            Trace.KeyValue.newBuilder()
                                    .setVStr("value2")
                                    .setKey("nested.nested.leaf1")
                                    .setVType(Trace.ValueType.STRING)
                                    .build())
                    .addTags(
                            Trace.KeyValue.newBuilder()
                                    .setVInt32(3)
                                    .setKey("nested.nested.leaf21")
                                    .setVType(Trace.ValueType.INT32)
                                    .build())
                    .addTags(
                            Trace.KeyValue.newBuilder()
                                    .setVInt32(1)
                                    .setKey("nested.nested.nestedList")
                                    .setVType(Trace.ValueType.INT32)
                                    .build())
                    .build();

repo: slackhq/astra


text:
Add support for replacing back stack root Screen

Consider the case of a multi-screen sign-in process. Once the user has successfully authenticated, it would be reasonable to clear the back stack (to prevent accidentally returning to the sign-in flow) and replace the root record with a new Screen (say the default landing Screen).
Currently, you can call  popUntil (Navigator.popUntil(predicate: (Screen) -> Boolean)) to remove multiple screens, followed by Navigator.goTo - as long as the root Screen is untouched. Attempts to pop the root screen trigger a call to the Navigator's onRootPop lambda which (by default) calls the Android back handler.
A couple ideas to achieve this use case:

support popping the root screen if a replacement is provided. This would likely require a new method on the Navigator interface
provide a mechanism for swapping the back stack managed by the Circuit navigator. This would likely be more complex and may not possible give the current architecture.

My sense is that a case like this is that the sign in flow should be on its own backstack and then root-pop itself off when done, any reason to do differently?

Yeah, I think that could work in some situations. It would effectively mean tearing down the running Circuit environment though wouldn't it? Ideally it would be nice to be able to clear or replace the backstack without having to leave the running Circuit environment.
Just to confirm I'm on the same page:

User lands on Activity A, Screen A
They are redirected to special flow - Activity B, Screen B1
Last step of flow (ie. Screen Bn) pops until the triggering the root pop callback
Activity B is destroyed and user is taken back to Activity A, Screen A

Addressed by #339

authors: ZacSweers kierse

repo: slackhq/circuit


text:
🐛 FEATURE: Accept stdin for nebula-cert print

What version of nebula are you using?
1.6.0
What operating system are you using?
openSUSE Leap 15.4
Describe the Bug
nebula-cert requires the path to be on disk and does not accept - to indicate stdin. It would be nice if nebula-cert supported this so that the bare certificate doesn't need to be saved to disk.
This doesn't work.
yq '.pki.ca | .' < config.yml | nebula-cert print -path -
Error: unable to read cert; open -: no such file or directory

This works.
yq '.pki.ca | .' < config.yml > temp.crt
nebula-cert print -path temp.crt -json | jq '.details.notAfter'
rm temp.crt

Logs from affected hosts
N/A
Config files from affected hosts
N/A

Anyone care if I plan on doing this for hacktoberfest?

I usually work around this by using:
nebula-cert print -path /dev/stdin

But I agree that making this easier with - would be nice.

This is the way I'd work around the issue:
nebula-cert print -path <(yq '.pki.ca | .' < config.yml)

authors: NiceGuyIT jrwren jstasiak wadey

repo: slackhq/nebula


text:
🛑 Ctear is down

In 2cb10b2, Ctear (http://ctear.com.ar/) was down:

HTTP code: 500
Response time: 8886 ms

Resolved: Ctear is back up in 6759f6f.


text:
🛑 Ctear is down

In b9a66b6, Ctear (http://ctear.com.ar/) was down:

HTTP code: 500
Response time: 737 ms

Resolved: Ctear is back up in 15d023d.


text:
added new notation

added new eval notation proposed for latex-math

 Add new eval notation to latex-math & check eval/tuning cheatsheet


text:
Drop rows with NaN locations (Longitude / Latitude)

Test with Code Commune = 59030

Fixed with simple dropna:
df.dropna(subset=['valeur_fonciere','surface_reelle_bati','longitude','latitude'])


text:
Extract the x-axis data (wavelength) from captured spectrum

Hi @sliakat,
Thanks for uploading the example scripts on LF Automation. We have a PI Spectrometer in the lab and, currently working on automating the data collection using Python. I have a couple of questions regarding the recorded spectrum and how to parse the data from the LF application to python
(1) Which experiment method should I be using between experiment.Acquire() and experiment.Capture(1) to record a spectrum? Acquire() returns nothing but displays the spectrum on the application, Capture returns a dataset but doesn't display the captured spectrum.
(2) I can extract the counts on each pixel in a given ROI, but I am not sure if there is a way to extract the x-axis (wavelength) of the recorded spectrum. Do you have any suggestions?
Looking forward to hearing from you.

Hi Ankur,
The wavelength calibration can be extracted from Experiment.SystemColumnCalibration or read directly from the spe file. To apply to an ROI, you'd want to take the x position of the ROI and use the slice x:width on the calibration extracted from automation / spe.
The difference between Acquire and Capture is explained in one of my tutorials in the Python automation folder (https://github.com/sliakat/SpeReadPy/tree/main/LFAutomation/PythonWebinar). Acquire() is asynchronous and returns immediately after asking LightField to acquire data and generate an spe file. Capture(n) holds the data in memory -- the LightField viewer does not see / display this data.

Hi @sliakat,
Thank you so much for your message.
I think it would be great to add an example script which configures the spectrometer and collects a spectrum from the camera.

repo: sliakat/SpeReadPy


text:
Maintenance/switch cgmath to nalgebra

Checklist

n/a I've added tests for all code changes and additions (where applicable)
n/a I've added a demonstration of the new feature to one or more examples
n/a I've updated the book to reflect my changes
n/a Usage of new public items is shown in the API docs

API changes
shrev version bumped from 1.0 to 1.1

bors r+

repo: slide-rs/specs


text:
Add name param to Clients.openWindow() method

OpenWindow creates a new window which can be accessed through the postMessage of the resulting Client object. It would be nice to add a 'name' param, like window.openWindow in order to allow the caller to communicate with the new window of the same domain using the 'name' instead of having to send a postMessage to the service worker and to the new clientWindow. In that way, we can get a reference to the new window opened in the service worker.

Instead of:

From page, postMessage service worker
From service worker, open window
From page, postMessage service worker
From service worker, postMessage page

Why not just:

From page, open window

We would like to use a window as a way of calling WebApis that cannot run on workers, let's call it WindowWorker.
The sw could be in charge of opening this WindowWorker, if necessary that could be share across different documents (windows) related to the same web app.
A simple way of getting a reference to this WindowWorker could be something like:
var handler = window.open('', 'window_worker');
And from there we could postMessage or anything else.
This also makes openWindow closer to window.open as we could interact with windows opened via SW.

@jakearchibald suppose I'm in a team management software application and I receive a push notification for an incomming chat request. The SW open a client window with the incoming conversation via openWindow(). After chatting, I want to close all the conversation through the main window. To do this, I need a reference of each incoming chat.
A feasible solution is to add the name parameter so the SW could generate and store the name for the open window in such a way the main application could get the list of open chats and close them all.
It makes sense to track new open windows. We have this mechanism for window.open() (the name parameter) and for iframes (the iframe itself) but those window contexts open from current implementation of openWindow() are untraceable.
Does it makes sense for you?

@lodr in that use case, wouldn't a much simpler system be for the SW to be able to close windows?

@jakearchibald but the SW could be terminated by the time you want to close the windows and telling the SW to close these window could only be possible if you have some way to mark the clients which are chat windows (and not other kind of clients). You need some way to relate references with information and we don't have even the references.

The window.name method:

Push message into SW
SW opens window with name 'chat-with-steve'
SW adds 'chat-with-steve' to IDB data store 'chat-window-names'
User clicks 'close all chat windows' in window
Window gathers window names from IDB 'chat-window-names'
For each, calls window.open, then calls .close on the handler
Window empties 'chat-window-names' IDB store

In this model you must keep the IDB store up to date, else window.open is going to open a new window.
The windowClient.close() method:

Push message into SW
SW opens window
SW adds new client.id to IDB data store 'chat-window-ids'
User clicks 'close all chat windows' in window
Window sends postMessage to SW, asking it to close all chat windows
SW gathers client IDs from IDB 'chat-window-ids'
SW gathers clients
For each client, calls .close if ID is in 'chat-window-ids'
SW empties 'chat-window-ids' IDB store

So doing it via the SW is a few more steps, but won't result in windows opening up. Also, by using IDs, the SW can "GC" the list in 'chat-window-ids' easily.

@jakearchibald I see. Though, it is quite a limitation to be forced to use the SW as a proxy for whatever operation you want to do with those window open by the SW. Communicating with the SW has its cost, more expensive than retrieving the window reference via window.open() if you realize the SW could be terminated and the awakening introduces its costs.
Furthermore I'm not really convinced you want the service worker to hold business logic. It makes perfect sense to allow opening a window as it's the common use case for a push or even sync events but forcing the SW to act as an intermediate for the business rules and its window causes one of two things:

Putting code in the service worker itself
Or putting it in another context and make the SW and this context to communicate via new postMessage() invokations.

What do you think?

authors: acperez arcturus jakearchibald lodr

repo: slightlyoff/ServiceWorker


text:
🛑 Synergy Webinar is down

In 5803730, Synergy Webinar (https://webinar.synergy.ru) was down:

HTTP code: 502
Response time: 723 ms

Resolved: Synergy Webinar is back up in 4608843.

repo: slimpdev/uptime


text:
Get Name of router

Hi, I am converting my project from v2 to v3 of Slim.Previously I was using middleware as a security clearance before user reach the specific route by checking the route name.
How could I access the routeName? Previously I was using $app->router()->getCurrentRoute()->getName();
Thank you.

$request->getAttribute("routeInfo"); should have the information you need.
Note that you'll also need the determineRouteBeforeAppMiddleware setting:
$settings = [
    'settings' => [
        'determineRouteBeforeAppMiddleware' => true,
    ]
];
$app = new Slim\App($settings);
// ...

Noted; Thank you for your help!

authors: akrabat matthewappbox

repo: slimphp/Slim


text:
Added getBasePath method to Router

Added docblock for new method
Added tests for new method

fixes #1964

Coverage increased (+0.001%) to 97.815% when pulling 0b3209b02874f3e5cb884c14d1889167fb0bee75 on chantron:router-get-base-path into 6d347477d09ab7910e625cee74c8108b7b85c7f9 on slimphp:3.x.

👍

Thank you.

authors: BoGnY akrabat chantron coveralls


text:
[4.x]  Simplifying queuing internal middleware

This PR addresses #2762.
Not sure, if the test cases test everything that needs to be tested.

Coverage remained the same at 100.0% when pulling 7246effc6e30c06d5e79e348cf4f3e4145e85cf0 on adriansuter:patch-middleware-helpers into 04be46919d42ee26e294a7426dd5bb68d013ff8f on slimphp:4.x.

Looks good to me @adriansuter, great work! As for the tests, the middleware test suite was already covering most of this anyway but it's good you went above and beyond with it! We just need to update the docs to reflect those changes. I'm going to merge.

authors: adriansuter coveralls l0gicgate


text:
Is it possible to set multi validate webhook on multi path?

Is it possible to set multi validate webhook on multi path on one server?
if done, i can deploy multi webhook in k8s which will run in parallel to achieve better performance

wrap after whhttp.MustHandlerFor(wh)

repo: slok/kubewebhook


text:
Improve UX for SLO's with more than 2 9's

Thanks for the awesome code! I had to do the equivalent of this a couple years ago with nothing but sed!
If I have a service with two objectives of 99.9 and another objective of 99.99, I get numbers like these:
$ sloth generate -i slo.yml 2>/dev/null | grep -Eo '0\.[0-9]{4}[0-9]+'
0.9990000000000001
0.9990000000000001
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.9990000000000001
0.9990000000000001
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.0009999999999999432
0.9998999999999999
0.9998999999999999
0.00010000000000005117
0.00010000000000005117
0.00010000000000005117
0.00010000000000005117
0.00010000000000005117
0.00010000000000005117
0.00010000000000005117
0.00010000000000005117

... where what I probably want is
0.9990000000000001 -> 0.999
0.0009999999999999432 -> 0.001
0.9998999999999999 -> 0.9999
0.00010000000000005117 -> 0.0001

I think the implementation might be something like "don't use floats".
Related to this issue: the grafana board reports a 99.99 objective as 100%, which is dismaying to people who only see the dashboard and not the actual values in the promql queries.

Hi @winmillwill!
From my side I don't see a problem with those numbers because they happen under the hood, it is an implementation detail, how they are being represented on a dashboard is another thing and I'm with you.
I see from your example that is affecting you on how is being visualized, right? In what other sense affects you those Prometheus rules numbers?
The dashboard you are referring to is the default dashboard? what version of Grafana are you using?

I see from your example that is affecting you on how is being visualized, right? In what other sense affects you those Prometheus rules numbers?

I don't think these numbers (the ones in the PrometheusRule resources) affect the visualization per se ... I think that's down to the dashboard json not specifying a precision ... though it could be that it's an issue with grafana rounding because of all the trailing 9's.
As you say, it probably isn't having any other effect: the computation that prometheus does with these values is most likely the same either way. I guess I see this as an opportunity to remove a source of confusion, because the only computation we ever want to do is 1 - {{objectiveAsDecimal}} ... and I think we can just pass that term into the promql queries and let prometheus do the math. For my use case, I will probably be running the CLI in a CI/CD pipeline or storing the output in a repo. In either case, developers will review the diff of the PrometheusRules yaml and end up going "but that's not what I wanted". Again, I agree that it probably doesn't matter in terms of prometheus and grafana working as expected ... I just don't want to have the same conversation with N different teams as I help them adopt SLO's.

The dashboard you are referring to is the default dashboard? what version of Grafana are you using?

Yes, the one at grafana.com. I'm using grafana version 7.5.7.
To be clear I'm seeing a panel like this:

... and I'd like it to say 99.99% instead of 100.0%

Yesterday I checked and as you said Grafana, rounds automatically after 2 decimals, it happens the same with percentages and ratios, so the problem is not the 0.99900000000... (I did the same tests with 0.9999, 99.99...).
I was thinking about putting explicitly 3 decimals, however, I also don't like to have a 99 represented as 99.000, So I need to research a bit more of how to solve this in the best way, any way, this doesn't affect Sloth's Prometheus implementation in this sense.

After merging #172 and changing Sloth's dashboard with the 4th revision this issue is fixed.
Before:

After:

authors: slok winmillwill

repo: slok/sloth


text:
[bug] nginx not available

See https://github.com/google/flatbuffers/runs/7966069802?check_suite_focus=true
Retrieving signed certificate...

        Note that there may be personally identifiable information associated with this signed artifact.
        This may include the email address associated with the account with which you authenticate.
        This information will be used for signing this artifact and will be stored in public transparency logs and cannot be removed later.
creating fulcio signer: retrieving cert:
<title>503 Service Temporarily Unavailable</title>

503 Service Temporarily Unavailable

nginx

/cc @asraa @bobcallaway

I hope this is a temporary issue?

Has it happened again since? I believe we resolved the root issue last
week.
On Mon, Aug 29, 2022 at 9:32 PM Ian Lewis @.***> wrote:

I hope this is a temporary issue?
—
Reply to this email directly, view it on GitHub
https://github.com/slsa-framework/slsa-github-generator/issues/759#issuecomment-1231039388,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVWTJOB2FKASGE5YTQ5JUDV3VQBPANCNFSM57LKWCAQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yeah, I would hope they could just re-run the job.

It has been fixed. Thanks @bobcallaway . Let's close the issue.

authors: bobcallaway ianlewis laurentsimon

repo: slsa-framework/slsa-github-generator


text:
[bug] goreleaser integration fails to upload intoto file to already existing GitHub release

Describe the bug
In a normal goreleaser pipeline goreleaser is responsible for creating a GitHub release and uploading all artifacts.
However, even when I specify upload-assets: true, the artifact is only seen on on the Action and not the github release.
The create-version step is marked as skipped.
To Reproduce
name: release

on:
  push:
    branches: [main, master]

jobs:
  goreleaser:
    runs-on: ubuntu-latest
    outputs:
      hashes: ${{ steps.hashes.outputs.hashes }}
    steps:
    -
      name: Checkout
      uses: actions/checkout@v3
      with:
        fetch-depth: 0
    -
      id: vars
      run: |
        goVersion=$(grep '^FROM go' .github/go/Dockerfile | cut -d ' ' -f 2 | cut -d ':' -f 2)
        echo ::set-output name=go_version::${goVersion}
        echo "Using Go version ${goVersion}"
    -
      name: Set up Go
      uses: actions/setup-go@v3
      with:
        go-version: ${{ steps.vars.outputs.go_version }}
    -
      name: Run Trivy in GitHub SBOM mode and submit results to Dependency Snapshots
      uses: aquasecurity/trivy-action@master
      with:
        scan-type: 'fs'
        format: 'github'
        output: 'dependency-results.sbom.json'
        image-ref: '.'
        github-pat: ${{ secrets.GH_PRIVATEREPO_TOKEN }}
    -
      name: Remove SBOM result
      run: |
        rm dependency-results.sbom.json
    -
      name: Setup git for private go module access
      run: |
        go env -w GOPRIVATE=github.com/intigriti
        echo "machine github.com login ${{ secrets.GH_PRIVATEREPO_TOKEN }}" >> ~/.netrc
    -
      name: Install syft
      run: |
        curl -sSfL https://raw.githubusercontent.com/anchore/syft/main/install.sh | sh -s -- -b /usr/local/bin
    -
      name: Create release tag
      uses: go-semantic-release/action@v1
      id: semrel
      with:
        github-token: ${{ secrets.GITHUB_TOKEN }}
    -
      run: git fetch -a
      if: steps.semrel.outputs.version != ''
    -
      name: Release
      uses: goreleaser/goreleaser-action@v3.1.0
      id: goreleaser
      if: steps.semrel.outputs.version != ''
      with:
        version: latest
        args: release --config=.github/goreleaser.yml --rm-dist
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    -
      name: Generate dist hashes
      id: hashes
      if: steps.semrel.outputs.version != ''
      env:
        ARTIFACTS: "${{ steps.goreleaser.outputs.artifacts }}"
      run: |
        checksum_file=$(echo "$ARTIFACTS" | jq -r '.[] | select (.type=="Checksum") | .path')
        echo "::set-output name=hashes::$(cat $checksum_file | base64 -w0)"

  provenance:
    needs: [goreleaser]
    if: needs.goreleaser.outputs.hashes != ''
    permissions:
      actions: read # To read the workflow path.
      id-token: write # To sign the provenance.
      contents: write # To add assets to a release.
    uses: slsa-framework/slsa-github-generator/.github/workflows/generator_generic_slsa3.yml@v1.2.0
    with:
      base64-subjects: "${{ needs.goreleaser.outputs.hashes }}"
      upload-assets: true

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

This potentially is because we release on the main branch and not on a tag branch.

Yes, that makes sense. 👍🏼

Yeah, we've been talking about allowing users to specify the tag_name on #710 and corresponding PR #713. Hopefully we'll have that supported soon.

I'm working on https://github.com/slsa-framework/slsa-github-generator/pull/713, should be landed soon. Since you have a temporary solution, let's close this issue. Please subscribe to https://github.com/slsa-framework/slsa-github-generator/issues/710 to know what it's merged. Thanks again for the report!

authors: hazcod ianlewis laurentsimon


text:
Using External Datasets with SHAP?

Hi,
I am a bit confused about using SHAP. I have  a dataset, with X and y (a regression problem). X has 8-10 features. I see that before using shap,
*shap.dataset is done.  --> does shap link with the dataset here?
How could I use shap with my own dataset?
Sorry if this seems too naive.

SHAP is designed to explain the predictions of an ML model you have trained. What type of model are you using?

@slundberg thanks for the reply, I am using a regression model..

Oh I think get your question now. shap.datasets just has a few example data sets. To use your own data just the load your feature matrix as a numpy array or pandas data frame, and your labels as a numpy array. In all the examples X is the feature matrix and y is the label vector.

authors: andymancodes slundberg

repo: slundberg/shap


text:
Profile access added to admin

Profiles now editable and searchable in admin interface.

My browser is not letting me comment for some reason.
I agree, you should see the user and probably search on the user too.
I'll look at it tomorrow and revise.
A bigger question is whether a "profile" table is the right place for
a telephone number - or were you thinking of expanding it?

@typonaut Yes, I think the profile is a good place to collect all user-related information.

authors: slyapustin typonaut

repo: slyapustin/django-classified


text:
🛑 Cekdata Website (tunnel) is down

In ddec037, Cekdata Website (tunnel) (https://cekdata.sman3palu.sch.id) was down:

HTTP code: 530
Response time: 99 ms

Resolved: Cekdata Website (tunnel) is back up in 5800113 after 33 minutes.

repo: smantriplw/uptime-services


text:
Calling docker compose down appears to wipe volumes

I have tried a few times running the node with docker compose up -d
Checking the logs, all seems to be working well and I can see the block/batch numbers increasing.
When I go to shutdown with docker compose down and then restart the node again, the block/batch numbers restart from zero and the node appears to have completely reset.
Is there something I am doing wrong here?

docker-compose down won't wipe anything unless you use the -v or --volumes option which will wipe the volumes that store data. Does op-node start from zero or does op-geth get reset to zero too?

Stale
docker compose down doesn't wipe volume

repo: smartcontracts/simple-optimism-node


text:
version v2.1.0  msg/min 横轴疑惑

刚刚接触efak，我认为横轴是时间，但是咋会这样？

默认按照数据量大小排序，非时间排序  ！！！

默认按照数据量大小排序，非时间排序 ！！！

repo: smartloli/EFAK


text:
Can't restore to a different mailbox

Hi - I'm using the pip installed latest version on Ubuntu. i've just taken my first full backup and im trying to restore it to a different (new) gmail account. I've got the creds etc for both.
I'm attempting to do the restore using the following command:
gwbackupy --credentials-filepath restore-account-creds.json --workdir /mnt/gmail  gmail restore --restore-deleted --email test-backup@gmail.com --to-email test-recovery@gmail.com
I get the following output but nothing is restored.....am i doing something wrong?
thanks!
        INFO 2023-04-18 14:04:05,019 - Filter options: deleted
        INFO 2023-04-18 14:04:05,019 - Scanning backup storage...
        INFO 2023-04-18 14:04:10,497 - Stored items: 476545
        INFO 2023-04-18 14:04:10,497 - Loading labels...
        INFO 2023-04-18 14:04:10,695 - Labels loaded successfully (23)
        INFO 2023-04-18 14:04:10,695 - Getting labels from server (test-backup@gmail.com)
        INFO 2023-04-18 14:04:10,703 - file_cache is only supported with oauth2client<4.0.0
        INFO 2023-04-18 14:04:10,922 - Filtering messages...
        INFO 2023-04-18 14:04:12,848 - Number of potentially affected messages: 0
        INFO 2023-04-18 14:04:12,848 - Upload messages...
        INFO 2023-04-18 14:04:13,852 - Messages uploaded successfully

PS. if i change the task to "--restore-missing" - I get the following output
INFO 2023-04-18 14:18:02,454 - Filter options: missing
INFO 2023-04-18 14:18:02,455 - Scanning backup storage...
INFO 2023-04-18 14:18:07,923 - Stored items: 476545
INFO 2023-04-18 14:18:07,923 - Loading labels...
INFO 2023-04-18 14:18:08,044 - Labels loaded successfully (23)
INFO 2023-04-18 14:18:08,044 - Getting labels from server (test-backup@gmail.com)
INFO 2023-04-18 14:18:08,049 - file_cache is only supported with oauth2client<4.0.0
INFO 2023-04-18 14:18:08,260 - Filtering messages...
INFO 2023-04-18 14:18:10,367 - Number of potentially affected messages: 238272
INFO 2023-04-18 14:18:10,367 - Upload messages...
INFO 2023-04-18 14:18:10,368 - 104aab753596579e Restoring message...
INFO 2023-04-18 14:18:10,369 - 104a8d63e4dbd03e Restoring message...
INFO 2023-04-18 14:18:10,369 - 104a8db2bbbbffb8 Restoring message...
INFO 2023-04-18 14:18:10,370 - 104a8b534dcad747 Restoring message...
ERROR 2023-04-18 14:18:10,370 - 104a8d63e4dbd03e Exception: Not implemented for different emails
Traceback (most recent call last):
File "/home/russ/.local/lib/python3.8/site-packages/gwbackupy/gmail.py", line 453, in __restore_message
label_ids = self.__get_restore_label_ids(
File "/home/russ/.local/lib/python3.8/site-packages/gwbackupy/gmail.py", line 374, in __get_restore_label_ids
raise NotImplementedError("Not implemented for different emails")
NotImplementedError: Not implemented for different emails
INFO 2023-04-18 14:18:10,371 - 104a95fc5b5a2356 Restoring message...
ERROR 2023-04-18 14:18:10,382 - 104aab753596579e Exception: Not implemented for different emails
Traceback (most recent call last):
File "/home/russ/.local/lib/python3.8/site-packages/gwbackupy/gmail.py", line 453, in __restore_message
label_ids = self.__get_restore_label_ids(
File "/home/russ/.local/lib/python3.8/site-packages/gwbackupy/gmail.py", line 374, in __get_restore_label_ids
raise NotImplementedError("Not implemented for different emails")
NotImplementedError: Not implemented for different emails
ERROR 2023-04-18 14:18:10,392 - 104a8db2bbbbffb8 Exception: Not implemented for different emails
Traceback (most recent call last):
File "/home/russ/.local/lib/python3.8/site-packages/gwbackupy/gmail.py", line 453, in __restore_message
label_ids = self.__get_restore_label_ids(
File "/home/russ/.local/lib/python3.8/site-packages/gwbackupy/gmail.py", line 374, in __get_restore_label_ids
raise NotImplementedError("Not implemented for different emails")
NotImplementedError: Not implemented for different emails

What happen if remove --restore-deleted parameter?
gwbackupy --credentials-filepath restore-account-creds.json --workdir /mnt/gmail gmail restore --email test-backup@gmail.com --to-email test-recovery@gmail.com

@beamends if possible, please test it. Within a few days, the package will have a new release version.
pip3 uninstall gwbackupy
pip3 install https://github.com/smartondev/gwbackupy/archive/72-implement-and-fix-gmail-restore-to-another-account.zip

Use --restore-missing parameter to restore different account.
Please note that the issue #26 still persists, causing repeated restorations to result in redundant email restorations in the destination account.

fixed in 0.11.0

authors: beamends kamarton

repo: smartondev/gwbackupy


text:
[FR] Add Minimalist Pop-Up Light & Media Cards

Add minimalist pop-up light & media card to every light card for better control

[ ] Add box shadow to polio slider cards to make readability easier

Specific Fixes (Phone)
Home Page

[ ] Phone Weather Popup, fix button press it's for back and radar
[ ] Fix people card map pop ups to actually show location
[ ] Room card pop ups

Hall

[ ] Lights
[ ] Fix Scene Automations #30

Living Room

[ ] Lights
[ ] Fix Scene Automations #30
[ ] Media

Bedroom

[ ] Lights
[ ] Fix Scene Automations #30
[ ] Media

Office

[ ] Lights
[ ] Fix Scene Automations #30
[ ] Media

Kitchen

[ ] Lights
[ ] Fix Scene Automations #30
[ ] Media

Specific Fixes (Tablet)
Home Page

[ ] Phone Weather Popup, fix button press it's for back and radar
[ ] Fix people card map pop ups to actually show location
[ ] Room card pop ups
[ ] Right side pop ups

Hall

[ ] Lights
[ ] Fix Scene Automations #30

Living Room

[ ] Lights
[ ] Fix Scene Automations #30
[ ] Media

Bedroom

[ ] Lights
[ ] Fix Scene Automations #30
[ ] Media

Office

[ ] Lights
[ ] Fix Scene Automations #30
[ ] Media

Kitchen

[ ] Lights
[ ] Fix Scene Automations #30
[ ] Media

Awaiting new update on UI Lovelace Minimalist to fix with Browser-Mod Update


text:
FIT3D smplx ground truth

I am currently trying to visualize the SMPLX mesh with pyrender and trimesh.
Using default values (equal to 0), it works and takes more or less good poses, after that I experimented with fit3D ground truth values that are in the format [706, N, 3, 3] depending on the specific parameter.
For example, let's take body_pose [706, 21, 3, 3], let's not consider the 706 because it's related to the fact that it's a video so for each parameter we have 706 of them. To visualize the SMPLX object, it accepts a vector of dimensions [1, 63], I understand that 21x3=63 but I'm confused about the extra dimension or in general about how to work with the data effectively.
I just want to visualize the SMPLX mesh corresponding to the first frame for example
Thank you very much for the help

digging through this notebook should be a good example on how to read the GT smplx parameters, camera parameters, generate the mesh and render the mesh.

authors: alessandrofolloni mihaifieraru