link_with in the Podfile is now unsupported, please use target blocks instead

When I execute pod install:
[!] Invalid Podfile file: [!] The specification of link_with in the Podfile is now unsupported, please use target blocks instead..
from /Users/Ray/demos/RestKit/Podfile:31
-------------------------------------------
platform :ios, '5.1.1'

link_with 'RestKitTests'
import_pods
-------------------------------------------

then I change 'link_with' with 'target', still get error:
[!] Unable to find a target named ios, did find RestKit, RestKitTests, RestKitFramework, and RestKitFrameworkTests.
what should I do?

RestKit still requires CocoaPods 0.39, please use the Gemfile.

any instructions to follow? not familiar with Gemfile

Having similar issue... Trying to build a gba4ios xcode project for testing on my phone and am getting the same error. SOS

The latest version of RestKit is compatible with Cocoapods 1.3.1, so you need to use the latest cocoapods syntax in the podfile.


server,sql,pgwire: let client conns timeout on unavailable clusters

PR: https://github.com/cockroachdb/cockroach/pull/44022
From release notes:

CockroachDB will now report a timeout error when a client attempts to connect via SQL or the Admin UI and some system ranges are unavailable. The previous behavior was to wait indefinitely. The timeout is configurable via the cluster setting server.user_login.timeout and is set to 10 seconds by default. The value "0" means "indefinitely" and can be used to restore the pre-v20.1 behavior. This timeout does not apply to the root user, which is always able to login on unavailable clusters. [#44022][#44022] {% comment %}doc{% endcomment %}

Closing since this variable's documentation is already up on the 20.1 cluster settings page.


Add VerifySecureRunner + SecureRun config flag

Codecov Report

Merging #303 (18d9553) into runFromEntrypoint (b7684cd) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@                  Coverage Diff                  @@
##           runFromEntrypoint     #303      +/-   ##
=====================================================
- Coverage              56.48%   56.46%   -0.02%
=====================================================
  Files                     47       48       +1
  Lines                   6069     6071       +2
=====================================================
  Hits                    3428     3428
- Misses                  2303     2305       +2
  Partials                 338      338

Files
Coverage Δ

pkg/runners/security.go
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Can we add a cairo_run_test example with secure_run == true?

Can you add a cairo_run_test example with secure_run == true?

secure_run should be always enabled if proof_mode is not, so Ill change the field in the testProgram utils


”Rediu Mitropoliei”, ”Țipilești”, ”Vânători”, ”Vulturi” are listed in the drop-down menu

Description:
When user writes ”Rediu Mitropoliei”, ”Țipilești”, ”Vânători”, ”Vulturi” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Rediu Mitropoliei"

Expected results
The location appears in the drop-down menu as "Sat Rediu Mitropoliei, IAȘI (Popricani)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Țipilești"

Expected results
The location appears in the drop-down menu as "Sat Țipilești, IAȘI (Popricani)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Vânători"

Expected results
The location appears in the drop-down menu as "Sat Vânători, IAȘI (Popricani)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Vulturi"

Expected results
The location appears in the drop-down menu as "Sat Vulturi, IAȘI (Popricani)".


[QUESTION] 0x52000062 error

Hi Experts,
We got following errors, would it cause re-connecting in the SDK, and try to get data endpoint thereafter?
Upload handle 14. Fragment timecode in 100ns:<PHONE_NUMBER>5540000. Error status: 0x52000062
Thank you!

This is 0x52000062 | STATUS_ACK_ERR_INVALID_MKV_DATA | Invalid MKV data as defined in https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/producer-sdk-errors.html
Any backend error means the backend will terminate the connection so yes, it will evaluate to termination.
This is likely caused by the partially submitted frame being dropped on the buffer pressure. We have a fix in the later versions of the SDK that will attempt to not drop the partial frame which would still cause a frame drop on the pressure but will avoid the syntactic error causing this.
Recommend updating to latest to minimize the chance of getting INVALID_MKV. The SDK will attempt to reset the connection on the buffer pressure which evaluates to another PutMedia call but this is done in hopes that the new connection will be faster and will allow clearing the buffer.

@MushMal thank you for the answer!
One more question, we registered error callback at client side, and didn't see errors, however cloudwatch still showed PutMedia.ConnectionErrors, a couple of questions

what's connectionerrors exactly?
is it possible to query what are the connection errors?
we see much lower PutMedia.Requests after some fixes, what's PutMedia.Requests exactly?

Thank you!

There are different types of errors. For this conversation we should focus on the runtime or dynamic errors that happen during the transmission. Those fall into two categories.

Errors that are related to the actual streamed data and we have a graceful reporting of an Error ACK from the backend following by a connection closure.
Not graceful errors which simply terminate the connection - these can be due to the ingestion host death for example or LB dropping the connection or anything else that can terminate the connection.

In the first case, we do report an error via the error callback and you could also subscribe to the fragment ACK received callback and listen to the error ACK type.
In the latter case, it will depend - most of the errors will reach the SDK in a form of terminated connection or connection staleness, etc... The SDK will automatically recover (default configuration) so the errors will not be reported.
Connection errors reported in the CW is the collective count of all of the errors - including the transient ones like the termination of the connection. This CW metric does not show the actual error - tracking those will be cost prohibitive and we only do deep dive into the logs per need.
PutMedia requests means how many streaming sessions there is. For example, if your device is streaming continuously and no interruptions happen then you will have a single putmedia request. However, any time there is token rotation or a disconnect, the SDK will retry to connect and send - each streaming session is a single PutMedia.
Please resolve the issue if you have your questions answered. I would encourage you to cut a new issue if the question is unrelated to the original question posted in this issue.


Restructure folders and procjects.

I have restructed the solution and ran the tests (100% pass). I have also added an unit test project for the Process Manager. I will talk to Lasse about the number of test projects, before moving the actual tests.

What about the namespaces? Are they supposed to come in another PR?

What namespaces do you have in mind?


Update initializers.py

Summary
Fix unused dtype argument for Identity
Related Issues
PR Overview

[N] This PR requires new unit tests [y/n] (make sure tests are included)
[N] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[Y] This PR is backwards compatible [y/n]
[N] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

You will need to rebase the PR. Currently it contain all changes to the codebase since the PR was opened. Alternatively, you can also close the PR and reopen a new one.

Closing PR. Reopening as #12552


Inconsistent CVE reporting documentation

Title: Inconsistent CVE reporting documentation
Description:
On https://github.com/envoyproxy/envoy/blob/main/SECURITY.md#security-reporting-process it says to send an email. If you go to "Create Issue", you get directed to https://github.com/envoyproxy/envoy/security/advisories/new though.
Which should be used to report CVEs these days? Is either fine?
Note: this is basically a nitpick, not a major concern at all

Thanks for pointing out this inconsistency.
I think the Github vulnerability reporting is a new feature, and we should better document it.
cc @envoyproxy/security-team for thoughts.

I think the Github vulnerability reporting is a new feature, and we should better document it.

yep, and probably make better use of it


feat: add theme ladder

Sorry for the delay. There's an issue with your theme.toml (it's not valid TOML).
I need to close this (there's also a merge conflict, please open a new PR).


feat: update sprig to version 2.22

sprig introduced some new interesting functions in 2.21 (deepCopy for instance).
I tried to update to sprig to version 3.0 (which is used on master) but couldn't: for some reason glide fails at finding github.com/Masterminds/semver/v3 (I suppose this is due to their move to Go modules or something).

Thanks for the PR @johanfleury 😁 🎉
Looks like @mattfarina helps maintain sprig. He might be able to help if you want to use v3 . I'll also check what's going wrong.
Also, on a side note, this PR looks like a feature addition to me. Looking at sprig changelog, yes, there were some fixes in v2.21.0 in sprig, v2.22.0 only has features. If you've been following the helm announcements, you might have noticed that we are doing only bug fixes for helm v2, and no more features. Not sure how to consider this PR 🙈
If you notice, in master, helm v3 already has v3 sprig in this commit https://github.com/helm/helm/commit/967f4fed42d0347405aa71fb441b054f761ee8e2 by @mattfarina . Not sure if it was intentional to leave v2 as is.
ccing @mattfarina to help review.

Also, if you are looking to work on more PRs, you are always welcome 😄
Do checkout https://github.com/helm/helm/#community-discussion-contribution-and-support for details about the mailing lists, discussions in slack and the developer calls on Thursdays 9:30 am -10 am Pacific time .

@johanfleury Can you please rebase from dev-v2. There was a change there.

@mattfarina done.
@karuppiah7890 thank you for the explanations.

I'm not used to neither Golang nor glide, but is their a way to only update a single dependency without updating all the others? (I didn't meant to update github.com/pkg/errors, golang.org/x/sync or google.golang.org/genproto)

There is no method with Glide. To give a little history, Glide was superseded by dep which is in the process of being superseded by Go modules. Both dep and Go modules provide this ability. It was in the glide roadmap but was not implemented because of being overcome by events.
Helm v3 uses Go modules.


Update exit value in hooks to valid code

Apparently -1 is invalid

As hinted at by @pg9182 in https://github.com/R2Northstar/NorthstarLauncher/pull/353#discussion_r1037360833


Request failed with status code 500

Hi friends,

I tried running this setup for the document question answering, its giving this error
Error building node VectorStoreAgent: 1 validation error for VectorStoreToolkit llm Can't instantiate abstract class BaseLLM with abstract methods _agenerate, _generate, _llm_type (type=type_error)
also I am not able to integrate prompt template in this setup.

Did you try with OpenAI instead of ChatOpenAI? (you would be using GTP3 instead of GPT4).  I had to to that to make it work.  I think there's issues with the chat version of OpenAI, which are now fixed in langchain, but langflow uses month old version of langchain where issues are still not resolved.  I'm not 100% sure of this though, but was waiting for future releases where langchain version is bumped up to see if that fixes it.

Haven't tried myself yet. Maybe this issue is related to your question https://github.com/logspace-ai/langflow/issues/206


Local Network

Hi. I found the solution
https://stackoverflow.com/a/65800221/3419059
it works good

Thank you for the information. 👍 I have studied it and I think that it will be supported since the next library update.

Thank you for the information. 👍 I have studied it and I think that it will be supported since the next library update.

I could not stand and released it just now

I could not stand and released it just now


Google-Auth shows Blank popup after clicking on "Not Now" on Suggestions Screen

Summary
My Google Auth flow in popup window works for most of the google users who have completed their profiles and have added recovery options.
For some of the users who haven't completed their google profile, the following Suggestions screen come up:

Please notice the url in the popup window is now https://gds.google.com (and earlier it was accounts.google.com).
Upon clicking on "Not Now",

The auth flow breaks and Blank Screen appears. Please notice that we're being redirected from gds.google.com to accounts.google.com

The error trace in the browser's console is
Cannot read property ‘postMessage’ of undefined
I feel the popup lost it's reference to my website's window in that redirection from accounts.google.com to gds.google.com
My webapp has the header Cross-Origin-Opener-Policy: same-origin-allow-popups set.

Browser(s)/Version(s)
All browsers
Expected Behavior
After clicking on "Not Now" in the Suggestions should continue to authenticate and call the callback registered in the initialize statement. window.google.accounts.id.initialize({callback})
Actual Behavior
After clicking on "Not Now" in the Suggestions screen, popup goes blank and browser gives the following error in console
Cannot read property ‘postMessage’ of undefined

Any suggestions here?

do you have any details to share on the auth setup within your app?

@jankrynauw Yes.
I have a react application on<EMAIL_ADDRESS>It's a client side rendered application.
Google scripts are loaded asynchronously after pageLoad event,
<Script
src="https://accounts.google.com/gsi/client"
        strategy="afterInteractive"
/>

Then when our Login Component is loaded, we wait for the parent div element's to be mounted before calling initialize and rendering the button.
const [googleSecureSignInRef, setGoogleSecureSignInRef] = useState(null);

useEffect(() => {
    if (googleSecureSignInRef && window.google) {
      window.google.accounts.id.initialize({
        client_id : config.GOOGLE_CLIENT_ID,
        callback  : onAuthenticationResponse,
      });
      window.google.accounts.id.renderButton(googleSecureSignInRef, {
        theme          : 'outline',
        size           : 'large',
        type           : 'standard',
        shape          : 'pill',
        logo_alignment : 'center',
        width          : 300,
        height         : '54',
      });
    }
  }, [googleSecureSignInRef, window.google]);

  return (

      <div
        className={className}
        ref={setGoogleSecureSignInRef}
      />

  );

any suggestions please?

Any suggestions !??

can anyone please suggest something?

Anyone got anything?

anyone has anything here? Please?


Comment bounties

Ability to add bounties to comments
Requires this PR to work: https://github.com/ResearchHub/researchhub-backend/pull/1130
UX: https://www.loom.com/share/07f0bb6753924818b07233125a18ca17

--Should probably do--

One of the core use-cases of what we are after is not entirely possible - That is, creating a bounty for a peer review. The reason it is not possible is because replies do not support "peer review". Only top-level threads do. I think we can still launch but we should really address this issue.

Ah this is gonna be tough.. Will need to think about how to make this possible, but I think we should release without it at the moment.


Update green to pass 4.5:1

On the road to #30548, and as mentionned in #30468, our current $green is not contrasted enough.
My first attempt was too far from other colors, so here's another one (and this PR will only try those greens). I tried to keep consistency by using the current .btn-success hover color, so this is basically the current green darkened from 7.5%.
Preview in color swatches — Preview in buttons

It's so dark. 😭
Is this the bare minimum to hit 4.5, or does this go past it a bit? I'd like to take as much as I can on the lightness/vibrancy of it since green is such a difficult color to get right.

I'll try to suggest a few other greens. 4.5 is the minimum indeed, but playing with hue or saturation it should be possible to get a lighter green.
I only used this as a startong point, this is the simpler variant to try since we already have it 😄

It's so dark. 😭

Yeah, I agree, the button looks like it's pressed. Here are some alternative colors, but as expected, they are all darker: https://contrast-finder.tanaguru.com/result.html?foreground=%23FFFFFF&background=%2328A745&ratio=4.5&isBackgroundTested=true&algo=Rgb&distanceSort=asc

BTW, is the white text color a requirement? Switching to dark or black would allow us to keep existing green.

BTW, is the white text color a requirement? Switching to dark or black would allow us to keep existing green.

Kinda? I like the consistency but I’d be open to dark text since we have that for our warning buttons.

I'm trying another green: #0a8a1d
FWIW, here's a great link to see how complicated it is to improve the current green: https://color.review/check/28A745-FFFFFF
Either playing with, hue, sturation or lightness gives us weird greens.
FYI to get dark text on success, it'll require to increase the $min-contrast-ratio:

it'll also change .btn-info color
it has to increase from a pretty large amount, to ensure hover keeps the same text color.
and in fact this should be the end, with #30548

One thing to consider is also to switch between darken() or lighten() for hover & active states, depending on the contrast color (PR incoming).
This makes sense for every hoverable colored background, I guess.

Still thinking out loud: if #30989 is accepted, then changing the green might not be valuable anymore.
The issue in #30468 was that foreground color changed on hover: that was because we always darkened the background, and got the foreground by using color-contrast(). With that in mind, if we try to bump $min-contrast-ratio to 4.5, this wouldn't happen anymore (however success and info buttons would have dark text color).
@mdo if this makes sense, we should consider to simply close this one and keep the current green and cyan. Just notice that the current green with a dark text color is not very happy, IMHO. We may end up lightening it :D

Closing this since it's tackled with #31276 :tada:


Multiple Details page pushed one on top of other in landscape mode

Hi, I ran your example app, and rotate the phone to landscape to have both panes.
Then I click successively on many tiles.
Then I rotate back the phone to portrait.
The last tile detail is shown. then I click the back button and the last tile is popped, but while I expected to get the master pane, it's the previous tile that is shown.
I have to continue popping all the tiles that were clicked.
Is this the expected behavior or some this is wrong.
Thanks

Should add that navigation is left for developers to implement i.e. what you're seeing is being handled by the navigation app


iOS simulator target

Hello.
Is it possible to build a library for the ios simulator (iosSimulatorArm64)? It could simplify testing many times.

I should be easy but I have not tried and only have a very limited experience with iOS.
You would first add the iosSimulatorArm64 {} target to the root build file (build.gradle.kts), modify secp256k1CInterop() to handle a new iosSimulatorArm65 target, and update build files in the native directory to handle the new target (build.gradle.kts and possibly xconfigure.sh).

@sstone Hi! I've made a pull request with this feature. Could you review it, please?

Ping-ping

I have made it in the fork and waiting until all targets are available from this repo.

Sounds like this issue is still not resolved in this repository, could we keep the ticket open please?

Yes, OP closed this issue because they have their own solution but we don't yet, we will probably use what they implemented (thanks!) once our next iOS release is out.

Another vote for this getting done. We could use it too.


Add missing context data to initialize_request function.

I want to merge this change because it adds missing data to the dummy request used in subscription webhooks. This will fix returning fields that need data like contex.plugins or context.discounts in resolver methods.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-7117 Missing discounts, plugins, and current site in subscription webhooks context


hot reload not working - solutions

Thanks a lot for your interest in helping the project but this doesn't belong to the vue-cli project.
It's better to file an issue if there's a bug first though 🙂


Create npm-publish.yml

Node.js package

Hi,
I am interested in this project, as I need the software for my own use.
ps - I have not changed anything - just want to connect
Thanks


Make sure we have documentation for functions in Emoji Logit Lens

Docstrings are not complete for functions. We can prioritize our public facing tutorials, and the functions they use, in terms of what we should document first.
Document all the vit_prisma functions imported into the Emoji Logit Lens Demo: https://colab.research.google.com/drive/1yAHrEoIgkaVqdWC4GY-GQ46ZCnorkIVo#scrollTo=8nN9gDe0OcCW
Ensure that we have type and shape for all input and outputs for the functions. Follow best documentation practices.

The Emoji Demo shares the same functions as the main demo so they are already documented.


Pause timer when user open setting menu?

Sey you start game... realized don't know how to play the game or want to stop animation... and open the settings view.
Should the timer stop counting while user is seeing settings view?

It's debatable whether it should pause or not. Being able to pause could be seen as 'cheating'. I'm happy to ship without pausing. WDYT @surma?

fair enough, one less thing to worry for deadline :)


Bug fix max items

Bug fix for unwanted maxItems on the root level of a JSON Schema validation

Linked to #133


Scan begins to run but then freezes and doesn't output a report

🐛 Summary
What's wrong? Please be specific.
To reproduce
os:
Windows
python:
3.12.2.
ScubaGoggles Binary Version:
0.57.0
Steps to reproduce the behavior:

Run scubagoggles gws
Then the command appears to begin running with one or more status bars, it creates the output directory, but then it appears to freeze up, and doesn't output anything.

Expected behavior
I expected the command to show progress and then complete with output, or even an error message.
Any helpful log output or screenshots
I tried the --debug option, but I didn't observe any additional output.

Hi David,
Thanks for the quick response!
I started over, but this time with the main branch -- instead of the latest release.
The scanning no longer freezes, but I'm not observing new error messages:
Terminal Output:
C:\redacted.venv\Lib\site-packages\scubagoggles\provider.py:454: RuntimeWarning: Exception thrown while getting group settings; outputs will be incorrect: 'NoneType' object is not iterable
warnings.warn(
Report Output:
This test depends on the following API call(s) which did not execute successfully: directory/v1/groups/list, groups-settings/v1/groups/get. See terminal output for more details.
Thanks,
Tony

Closing due to lack of activity. Feel free to reach out again if the problem persists.


The default value of the region option is us-east-1

I am using cls3 version 0.5.1.
The README.md says that the default value of the region option is ap-northeast-1, but the actual default value seems to be us-east-1.
https://github.com/go-to-k/cls3/blob/29ab161874a3223e2b3fa6fbfc6ebda7d139a5e7/README.md?plain=1#L35-L36
https://github.com/go-to-k/cls3/blob/29ab161874a3223e2b3fa6fbfc6ebda7d139a5e7/aws_config.go#L10
When I tried to delete an S3 bucket in ap-northeast-1 without specifying region, I got an error.
ERR PermanentRedirectError: Are you sure you are specifying the correct region?

Which is the default value you want I don't know, but I am reporting it because the README.md and the actual value seem to be different.
The blog post is also ap-northeast-1, so is ap-northeast-1 correct?

@t4kamura
Hi, Thanks for your reports.
It was a complete blind spot... As documented, I fixed it to ap-northeast-1 in v0.5.2 and released it!
Please use it again if you like!
https://github.com/go-to-k/cls3/releases/tag/v0.5.2

@go-to-k
Thank you for your swift response!
I have and will continue to use it!


Can't render profile photo component as image

I have a profile photo field in my database to store the link to the profile photo of the user. I want to render it in admin bro as an image but somehow the 'components' attribute of properties object is not working, and the link is being rendered as a simple span tag with text.
Here is my code inside the properties object :
resource:Members, options:{     properties:{                     profilePhoto:{                                       components:AdminBro.require('./components/profile-photo-comp')                                   }                      }      }
And here is the component :
const PhotoComp = props=>{
                      return (
                    ```
                        <div>
                            <img src={props.record.params.profilePhoto} alt="profile-photo" />
                         </div>
                   ```
                     );

export default PhotoComp;

there is a where missing.
resource:Members,
options:{
  properties:{
   profilePhoto:{
     **where**: components:AdminBro.require('./components/profile-photo-comp')
   }
  }
}

where can be either: list, show, edit or filter - in your case probably you will have to override list and show.

Nope, doesn't work. Still the same issue - photo link is rendered as a span tag, instead of img tag

sorry - my mistake:
resource:Members,
options:{
  properties:{
   profilePhoto:{
    components: {
     **where**: AdminBro.require('./components/profile-photo-comp')
    }
   }
  }
}


Apparent crash in resvg/raqote when rendering SVG in iced

Don't sure whether it applies here, but looks like there is a SVG that crashes a certain version of resvg. For more information please have a look at https://github.com/hecrj/iced/issues/466
Hope this helps.

raqote backend was removed.


thats a bad material design

this design forgot material animation. i recommend github.com/daemonite/material

According to the Guidelines you are Correct, I will work on this witching the next month

hm

This has been fixed.


Add Code Review

https://github.com/joho/awesome-code-review
List of code review tools, books, papers, talks etc. Code review is a very common engineering practice and there are lot of interesting resources going back ~40 years and new talks and tools coming out all the time.
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.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

[x] Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
[x] Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

[x] 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.
[x] It's the result of hard work and the best I could possibly produce.
[x] Non-generated Markdown file in a GitHub repo.
[x] Includes a succinct description of the project/theme at the top of the readme. (Example)
[x] The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
[x] Not a duplicate.
[x] Only has awesome items. Awesome lists are curations of the best, not everything.
[x] Includes a project logo/illustration whenever possible.

Either 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.

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

Should be placed on the right side of the readme heading.
Should link back to this list.

[x] 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 sub-lists, preferably none.

[x] Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.

[x] Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

[x] 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.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

[x] Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

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.

Hi @sindresorhus thanks for the speedy reply.
I've converted the list over to checkboxes and ticked the ones I think I'm safely in.
(if you think i should untick any please let me know). I used the yeoman generator recommended to set the structure so I'd hope the nitty gritty was all right (though I did have to manually change "Table of contents" to "contents" to comply with the list)
That leaves

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
(in your list) None of the surrounding entries had descriptions and I believe the title is descriptive enough, if you disagree I'm happy to add it.

Includes a project logo/illustration whenever possible.
I can jam something in there if you feel strongly about it but it didn't seem to me a consistent thing in lists I'd read, and doing it just to do it didn't seem high value to me.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
(in my list) Less than half have descriptions, but I thought I had the balance right here. Happy to hear otherwise

OK I've updated my awesome list as per the checklist, actually checked off the checklist, and tidied up the commit history on this branch.
Could I request a re-review and a merge please?

Includes a succinct description of the project/theme at the top of the readme. (Example)

This is not done. It should be a description that succinctly describes what a code review is. You could take something from: https://en.m.wikipedia.org/wiki/Code_review Also linkify the word code review to the Wikipedia page.

Fixed in https://github.com/joho/awesome-code-review/commit/6a5fd047927342808007662f3c8c04bfaea6669a

I think it would look better as:

A curated list of tools, articles, books, and any other resource related to code review.

Code review is the systematic examination (sometimes referred to as peer review) of computer source code.


Any way to "unload" a controlnet model from memory when Controlnet is disabled?

I know I'm really pushing it with a 1660TI 6GB on a laptop but, I've noticed if I use a difference control and then use a different one I get CUDA OOM errors and I have to restart the webUI completely to use another. So my guess is they just hang around in memory even if you don't have Controlnet enabled.
I don't know if this is the right place to ask this question/suggestion.

Hello! If you are using automatic1111 webui, you may want to ask from there. link


Make Settings editable

Refactor settings to make them editable, including:

[ ] Call blocking modes
[ ] Regex pattern for names
[ ] Regex pattern for numbers
[ ] Phone number formatting

I intend to implement the settings configuration via a config.py file.

I'm not happy with the current config implementation: there is no provision for default values if the config file is missing or if values are missing.

Command line options
Usage: python callattendant.py -c [FILE]
-c, --config=[FILE]	load a python configuration file
-h, --help		displays this help text

python callattendant/src/callattendant.py -c app.cfg

Config file
The config file can be an absolute path or a path relative to the root of the application (i.e., the location of callattendant.py)
Example
#!/usr/bin/env python
#
# file: app.cfg
#
# ==============================================================================
# This file contains the configuration settings for the callattendant
# ==============================================================================

# ENV: production or development environment. development implies
# incomplete features and/or debugging
ENV = 'production'

# DEBUG: If true additional assertions and output may be generated
DEBUG = False

# TESTING: If true test scaffolding/behavior may be implmented
TESTING = False

# DATABASE: Sqlite database for incoming call log, whitelist and blacklist
DATABASE = "callattendant.db"

# SCREENING_MODE: no_screening, whitelist_only, whitelist_and_blacklist, blacklist_only
SCREENING_MODE = "whitelist_and_blacklist"

# BLOCK_ENABED: if true calls that fail screening will be blocked
BLOCK_ENABED = True

# BLOCK_NAME_PATTERNS: A regex expression dict applied to the CID names
# Example: {"V[0-9]{15}": "Telemarketer Caller ID", "O": "Unknownd caller"}
BLOCK_NAME_PATTERNS = {"V[0-9]{15}": "Telemarketer Caller ID",}

# BLOCK_NUMBER_PATTERNS: A regx expression dict applied to the CID numbers
# Example: {"P": "Private number",}
BLOCK_NUMBER_PATTERNS = { }

# BLOCKED_MESSAGE_ENABLED: If true the blocked message file will be played to the caller
BLOCKED_MESSAGE_ENABLED = False

# BLOCKED_MESSAGE_FILE: The wav file to be played to blocked callers
BLOCKED_MESSAGE_FILE = "hardware/sample.wav"


Android fails to run basic example compiled with openblas (in emulator)

Hi,
I'm running into the following error: arm-linux-androideabi-gcc -mfloat-abi=hard ex.cpp -I/opt/arm-tools/include  /opt/arm-tools/lib/libopenblas.a
arm-linux-androideabi/bin/ld: error:  uses VFP register arguments, output does not
ex.cpp is a simple example taken from the web:
#include <cblas.h>
#include <stdio.h>
int main()
{
int i=0;
double A[6] = {1.0,2.0,1.0,-3.0,4.0,-1.0};
double B[6] = {1.0,2.0,1.0,-3.0,4.0,-1.0};
double C[9] = {.5,.5,.5,.5,.5,.5,.5,.5,.5};
cblas_dgemm(CblasColMajor, CblasNoTrans, CblasTrans,3,3,2,1,A, 3, B, 3,2,C,3);
for(i=0; i<9; i++)
printf("%lf ", C[i]);
printf("\n");
return 0;
}
I compiled the android toolchain following instructions here: http://developer.android.com/ndk/guides/standalone_toolchain.html
make-standalone-toolchain.sh --arch=arm --platform=android-21 --install-dir=/tmp/my-android-toolchain
I compiled OpenBlas following instructions here: https://github.com/xianyi/OpenBLAS/wiki/How-to-build-OpenBLAS-for-Android
make HOSTCC=gcc CC=arm-linux-androideabi-gcc NO_LAPACK=1 TARGET=ARMV7
I have noticed that this error goes away when I edit Makefile.arm, and replace -mfloat-abi=hard with -mfloat-abi=soft (had to do this for building and linking ex.cpp as well).
Reading the ABI compatibility section of the standalone toolchain page:
If you want to target the armeabi-v7a ABI, you must set the following flags:
CFLAGS= -march=armv7-a -mfloat-abi=softfp -mfpu=vfpv3-d16
I think that while I've built ex.cpp, the binary will be slower than if it was build to use the FPU. Could someone help me figure out how to build this properly?
Thanks,
Kevin

Is that ld error complete? There should be some library name + preceding command line at least.

Here is the full output:
/tmp/my-android-toolchain/bin/arm-linux-androideabi-gcc -mfloat-abi=hard  ex.cpp -I/opt/arm-tools/include  /opt/arm-tools/lib/libopenblas.a
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /var/folders/5l/kndj2q_1371gmqd_sr703fl40000gn/T//ccKe1jnm.o uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(cblas_dgemm.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(dgemm_nn.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(dgemm_nt.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(dgemm_tn.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(dgemm_tt.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(dgemm_thread_nn.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(dgemm_thread_nt.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(dgemm_thread_tn.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(dgemm_thread_tt.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(memory.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(xerbla.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(blas_server.o) uses VFP register arguments, output does not
/private/tmp/my-android-toolchain/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /opt/arm-tools/lib/libopenblas.a(dgemm_beta.o) uses VFP register arguments, output does not
collect2: error: ld returned 1 exit status

Are you sure these 2 are set?
TARGET_CFLAGS += -mhard-float -D_NDK_MATH_NO_SOFTFP=1
TARGET_LDFLAGS += -Wl,--no-warn-mismatch -lm_hard

Looking at the build output, I don't think I've set those properly, how can I set those, besides editing Makefile.arm?

Ok, I think I've figured it out, those flags are meant for when I compile and link ex.cpp, not for compiling the existing library. I'll go ahead and close the issue.

Closed it a little too fast. I've edited the OpenBLAS wiki page with new build instructions so I can build ex.cpp.
The problem now is I cannot run the compiled executable, I can get printouts before the call to cblas_dgemm, but not after.
Here's how I'm running it.

I'm using android emulator, with default choices for spinning up a new avd.
adb push ./a.out /
adb shell
./a.out

Here's I get that the shell exited (no printouts). I don't have a segfault, but I don't get the expected printout of the matrix either.

So are you building with hardfp or softfp option now ? An emulator may not show the exact same behaviour as the actual hardware, which might explain the exit without an accompanying segfault.
From #777 I understand that the assembler notation used in the optimized kernels would have to be completely different for softfp, hence the current requirement for building everything for the hardfp API as that is what is used in the OpenBLAS routines.

I figured this out. I was mixing up hard and soft floating point in the compiles. The issue went away after I cleaned and started from scratch.

To be clear Android are already removed the armeabi-v7a-hard


Rails 5.1 capybara integration

Hi, I've on request/question, but don't know if it make sens ... so, sorry if not.
Rails 5.1, Capybara is integrate to rails http://edgeguides.rubyonrails.org/5_1_release_notes.html#system-tests, with commit https://github.com/rails/rails/pull/26703
This feature should avoid to use DatabaseCleaner for request spec. Example in rails doc is only with rails integrated test. Can we use this integration with rspec ? Rspec-rails should add this features or a possible way exist to do this right now ? Or maybe it's not possible ?

Rails has introduced something called system tests in 5.1, these use capybara to drive selenium for full stack testing, something we already support as 'feature' tests with capybara, potentially we could support there setup as well but you'd still need database cleaner where appropriate with both Rails own system tests and out setup

Additionally it seems transactional tests now won't require seperate rollback when the server is the same thread as the tests, which might be what your referring to, but has no change required for anything we use see https://github.com/rails/rails/pull/28083

Ok, thanks for your precision

@kaluznyo the only actual change I had to make for Rails 5.1 in terms of specs was removing DatabaseCleaner and changing my spec_helper.rb to have  config.use_transactional_fixtures = true

@maschwenk does RSpec also pickup the Capybara configuration found in test/application_system_test_case.rb?

I've never used that, can't say

@tomekr unlikely, most rspec uses won't have a test folder, and we don't require it or look for it

Hi Friends
We will be providing a type: :system example group which uses rails' new testing api. It will not use the test/application_system_test_case.rb configuration, but will allow you to use a similar API to specify your system test configuration.

I've just pushed a WIP pr here: https://github.com/rspec/rspec-rails/pull/1813

Could someone shed some light on the difference between existing feature specs and @samphippen 's upcoming system specs?  type: :feature vs type: :system They both use capybara and seem to do the same thing.

@pickerflicker type: :system will follow the blessed Rails approach, which uses puma and it's own stack rather than capybara's like currently.

Closing in favour of #1813


include manymine.enabled=true label

Would you consider adding the manymine.enabled=true to your docker image? For those running on Synology docker containers it would greatly simplify creating servers that support the manymine container.

Does it need to be a label on the image? If so, can you point me to documentation why that is?

...you add that label to your container:

Add the label 'manymine.enable=true' to each server container you want manymine to announce to clients.

from https://github.com/illiteratealliterator/manymine#manymine
such as
  minecraft-a:
    image: itzg/minecraft-bedrock-server
    container_name: minecraft-a
    environment:
      - EULA=TRUE
      - SERVER_NAME=Server A
      - SERVER_PORT=60601
    volumes:
      - minecraft-a-data:/data
    ports:
      - '60601:60601/udp'
    labels:
      - manymine.enable=true

and refer to https://community.synology.com/enu/forum/1/post/125907

I believe it can be a label created in the dockerfile or it can be done during creation. However on Synology devices when using their supported method of creating containers you can not define labels at creation unfortunately, they lack that functionality. I understand if you wish not to, just a thought to make it work easily for those working with a GUI that's limited.

No, it's not that I don't want to. What I'm trying to say is that the image labels are totally different from the container labels. So applying container labels is beyond my control as the image author.
The last link describes you can use compose files with Synology to do more advanced things like container labels.

It is possible to SSH into the Synology and do things via commandline, it's just not officially supported, and a lot of people are uncomfortable doing so. As for labels. My understanding was that the label metadata that is created as part of an image, or added to the container afterwards are one and the same when being viewed. They are simply metadata that can be viewed, I thought the same command to view a label would list all labels for a container regardless of where they are defined. Image  defined labels can be over-ridden at container creation time though. I could be incorrect on that.
It actually might be an idea to add the multiple mine broadcast feature directly into your container. Thank you for all of your work on making and maintaining this image.

OK, I didn't realize that a container picks up the image labels also. I just confirmed that's the case.
I'll double check with the manymine project that defaulting the label to be enabled seems ok with them also.

...to answer your question, yes, it does seem to be possible to SSH into Synology's Linux shell and I thought it was officially supported.

I've read it's not supported, but that doesn't mean that was accurate information. I work within SSH on the synology all the time myself, but many people don't. This is my first look into a docker container besides using them, so this has been a fun learning experience for me so far.

The latest image now includes the manymine.enable=true label.

Thank you! I'll test it shortly.

I have tried it, but I am not seeing the label. It's the latest I should download or is there a different tag? (I may be having a caching issue on the synology, not sure)

nevermind, I didn't see the tag first time, sorry. I am testing it now

Works great, thank you!


Issue warning when OpenPose may be CPU bottlenecked

If you get a beefy GPU, but only have one CPU core, OpenPose can become CPU bottlenecked. It's quite easy to do this by accident in SLURM by not asking for enough cores. It would be good to try and avoid this situation by issuing a warning.

Oddly this often seems to be the case even when multiple processors are assigned. I don't think anything can be done apart from improving OpenPose or using a more efficient pose estimator.


Create a new release

Hello, I'm using K-9 Mail installed via F-Droid and the newest release available there is a year old (v5.600). Is there a plan to make a new release soon? I'd like to start using protected headers on K-9 but wouldn't know how to compile it from source.

Yes, there are plans to create a new release. A new beta version should be available soon. It might be a while until we get to a stable release, though.


Docker authentication

What does this PR do?
This PR:

enables docker hub authentication
upgrades golangci-lint

/sem-approve

/sem-approve

/sem-approve


Failed to set git-bash as terminal

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.57.1
OS Version: windows 10.0.19042

Steps to Reproduce:
This is my setting.json

Before restarting vscode, a fault was reported directly.

After restarting vscode, this problem will still be reported, and git-bash is not added to vscode.
The question helps to configure #terminal.integrated.shell.windows# or #terminal.integrated.shellArgs.windows#, but both of them seem to be no longer supported.

I'd suggest deleting the entry you have for "Git Bash". I suspect that path is invalid.

@meganrogge Not sure but this is related to VSCode restricting from setting any terminal name other than "Command prompt" and "Powershell". I had the same problem and bypassed it by setting the path of bash with name of Command prompt.

Also the option to edit is only available in OSX and linux, and a dropdown is available in Windows.
Please check the images once. Thanks!

I tried to install git in the C:\Program Files\Git path, and VScode can use git-bash. This bug seems a bit ridiculous, why can't git be installed in a custom directory!

This warning and it not showing up in the dropdown means that the profile failed validation which likely means the path is wrong as @meganrogge mentioned. The reason it worked when you reinstalled to the default path is we have a pretty extensive list of paths to check for the default path:
https://github.com/microsoft/vscode/blob/c4f332d5e642cd702e79ff74489095f6eda536dd/src/vs/platform/terminal/node/terminalProfiles.ts#L196-L209
So chances are you just had the path wrong, if you have more info/proof that the path is correct we could try repro though.


Test mechanism failure, failed to clean up state under Eclipse PDE

From<EMAIL_ADDRESS>on January 25, 2011 07:34:33
What steps will reproduce the problem? 1. Run a JUnit test case with @PowerMockRunner as Eclipse PDE plugin test. What is the expected output? What do you see instead? Expected to see test run successfully. Test ran, but post test failure from PowerMock clean up. What version of the product are you using? On what operating system? PowerMock 1.4.7 EasyMock 3.0
Eclipse 3.5
Windows XP
Java 1.6 Please provide any additional information below. Stack trace is attached.
Key lines in the trace:
java.lang.RuntimeException: Failed to clean up state
at org.powermock.api.easymock.PowerMock$EasyMockStateCleaner.invokeReportLastControlFromSystemCL(PowerMock.java:2310)
at org.powermock.api.easymock.PowerMock$EasyMockStateCleaner.run(PowerMock.java:2298)
at org.powermock.core.MockRepository.clear(MockRepository.java:125)
at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
...
org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(WorkbenchTestable.java:71)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: org.easymock.internal.LastControl
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at org.powermock.api.easymock.PowerMock$EasyMockStateCleaner.invokeReportLastControlFromSystemCL(PowerMock.java:2304)
... 30 more
I suspect that the OSGi class loading framework is not compatible with the technique being used in test finish method to clean up EasyMock state.
Attachment: powermock-1.4.7-failed-cleanup-stacktrace
Original issue: http://code.google.com/p/powermock/issues/detail?id=309

From<EMAIL_ADDRESS>on February 09, 2011 23:07:57
Thanks for reporting. Could you please attach a small example that demonstrates the issue? Otherwise it's hard to debug and to know when it's fixed (I don't even have Eclipse anymore).

From<EMAIL_ADDRESS>on April 07, 2011 03:57:52
I can reproduce the problem with running powermock with maven/tycho, which spawns a new OSGi runtime for the tests.

From<EMAIL_ADDRESS>on April 07, 2011 04:11:32
The problem is that in an OSGI envoronment the LastControl.class and the MocksControl.class are not loaded by the current or the system class loader, but by the class loader of the bundle the classes are into. It may help to use:
...
final ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
final Class lastControlClassBySystemCL = Class.forName(LastControl.class.getName(), true, classLoader);
                final Class mocksControlClassBySystemCL = Class.forName(MocksControl.class.getName(), true, classLoader);
...

From<EMAIL_ADDRESS>on April 07, 2011 04:29:37
It might help but it's hard for me to verify it without help. If I commit it to trunk could you build PowerMock from source (it's easy, mvn clean install will work) and give it a try in your project?

From<EMAIL_ADDRESS>on April 07, 2011 06:03:50
I'd forgotten this was our blocker for upgrading version of PowerMock. If you commit changes, I can test it. I have a trunk checkout already and have built many times before.

From<EMAIL_ADDRESS>on April 07, 2011 06:18:24
Awesome. I'll try to find time to try it out it later this evening.

From<EMAIL_ADDRESS>on April 07, 2011 13:29:18
I've committed the changes to trunk now. Please verify if it solves the problem for you.
Status: Accepted

From<EMAIL_ADDRESS>on April 11, 2011 04:23:10
I have the same issue when running a test through an Ant-script. Instead of building successful it says "build failed" with a similar stack trace (due to PowerMock clean up).
I made my 1st PowerMock-built from the trunk, replaced the 1.4.8.jar with the newly built jar and ran the Ant-script again. Now the script runs successfully, so problem is solved (for me).

From<EMAIL_ADDRESS>on April 11, 2011 04:54:06
Great! Thanks for helping out.

From<EMAIL_ADDRESS>on April 11, 2011 13:26:57
I'm closing the issue now.


CSS Optimisation

Consolidate CSS selectors and properties while adding descriptive commentary.

Unsure what to leave as descriptive commentary.


geographic coordinate needs a definition

Description of the issue
The class geographic coordinate (subclass of immaterial entity) doesn't have a definition.
Ideas of solution
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

A geographic coordinate is rather an information content entity about an immaterial entity / 0-dim spatial region.
A geographic coordinate is an information content entity about the geografic position of a 0-dim spatial region on Earth.

I agree that geographic coordinate is an information content entity. Maybe we can extend the definition a bit:
A geographic coordinate is an information content entity specifying the geographic position of a 0-dim spatial region on Earth using a set of numbers.
This would exclude descriptions like "next to this building" which are not coordinates in my understanding.

Ok. I'd extend it even more:
A geographic coordinate is an information content entity explicitly stating the geographic position of a 0-dim spatial region on Earth, by using a set of numbers with respect to a geografic coordinate system.


[BUG] Groupby with single column for grouping and calculating results throws an error

Describe the bug
This functionality is important because often we might want to group by an identifier column (such as customer_id for instance), perform some calculations on the groupings and separately return the column that we grouped by on (for instance, to add some sort of target using that column, or even juts to be able to tell what subset of data each calculated value relates to).
Having this functionality would be very useful, because often we might want to still run some additional preprocessing on the numerical values that are returned by the original grouping. Essentially, we need to process the identifier column separately.
Currently, doing so throws an error as below

Steps/Code to reproduce bug
Reproducer code:
import cudf
import nvtabular as nvt
import numpy as np
import datetime

purchases = cudf.DataFrame(
    data={
        'customer_id': np.random.randint(0, 10, 1000),
        'purchase_date': [datetime.date(2022, np.random.randint(1,13), np.random.randint(1,29)) for i in range(1000)],
        'quantity': np.random.randint(1, 50, 1000)
})
purchases.head()

ds = nvt.Dataset(purchases)

last_purchase_quantity = ['quantity', 'purchase_date'] >> nvt.ops.Groupby(
    groupby_cols='customer_id',
    sort_cols='purchase_date',
    aggs={'quantity': 'last'}
) >> nvt.ops.Normalize()

customer_id = ['customer_id', 'purchase_date'] >> nvt.ops.Groupby(
    groupby_cols='customer_id',
    sort_cols='purchase_date',
    aggs={'customer_id': 'last'}
)

wf = nvt.Workflow(last_purchase_quantity + customer_id)

wf.fit_transform(ds).compute()

Expected behavior
No error is raised and the values are returned correctly
Environment details (please complete the following information):
current NVTabular main

It looks like the column names are getting mangled by the GroupBy op somehow:
z> /nvtabular/nvtabular/workflow/workflow.py(523)_transform_partition()
-> col_series = output_df[col_name]
(Pdb) output_df
   c_u_s_t_o_m_e_r___i_d
0                      5
1                      0
2                      6
3                      2
4                      8
5                      4
6                      1
7                      9
8                      7
9                      3
(Pdb) col_name
'customer_id'

This is being worked on under #1636


Documentation of different FFB effects

An overview of all the different force feedback effects with their usecases und parameters would be amazing.
For example I figured out that the "condition" effect can be used to make the steering wheel spring back to center. The strength can then be varied by adjusting "Effect Right/Left Sat"

Took some time to get around to this but I've documented some things here:
https://github.com/JaydenMaalouf/JoystickPlugin/wiki/Effects
It's a shame there isn't much documentation around this. I built this plugin with the intention on building out these effects for my own project but I still haven't got something I'm happy with haha


useAsyncData cannot be refreshed with ref-value in 'composables'

Environment

Operating System: Linux
Node Version:     v18.20.3
Nuxt Version:     3.13.2
CLI Version:      3.14.0
Nitro Version:    -
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-bpyqqk?embed=1&file=pages%2Fbad.vue
good case
const ss_sl = ref(0);
// useGoodSSRFetch defined in composables
const { data, error, refresh } = useGoodSSRFetch(
  'https://api.kuleu.com/api/suijimima',
  'GET',
  { ss_sl } // The parameter type is:  ref
);

const next = async () => {
  ss_sl.value++;
  console.log('count-->', ss_sl.value);

  refresh();
};

bad case
const ss_sl = ref(0);
// useBadSSRFetch defined in composables
const { data, error, refresh } = useBadSSRFetch(
  'https://api.kuleu.com/api/suijimima',
  'GET',
  { ss_sl: ss_sl.value } // The parameter type is:  value
);

const next = async () => {
  ss_sl.value++;
  console.log('count-->', ss_sl.value);

  refresh();
};

Describe the bug
I encapsulated the useAsyncData function under ‘composables’, and the call in the vue file was successful and I got the first page data, but when I wanted to get the second page data via 'refresh', I found that if the 'page' parameter is of the value type, I can only get the first page forever, but if the input parameter is a ref, I can get the subsequent pages normally.
我在‘composables’目录下对‘useAsyncData’进行了封装，在vue文件中成功调用并得到了第1页数据，但当我想通过‘refresh’获取第2页数据时，我发现如果传入的'page'参数是值类型时，虽然我修改了'page'参数的值为2，但我仍然获取到第1页；但如果传入参数是ref类型则可以正常获取后续的页面。
Additional context
No response
Logs
No response

This is not a bug, this is how Vue reactivity works.
With ss_sl.value you are just passing a number not a reactive object, so you lose reactivity.
You can learn more here.

This is not a bug, this is how Vue reactivity works. With ss_sl.value you are just passing a number not a reactive object, so you lose reactivity. You can learn more here.

I can understand. Actually my goodcase gets the data after passing the ref variable, but in fact I'm using useAsyncData outside of the vue file, in which case I prefer it to be handled automatically rather than passing the reactive variable to an external js.
https://stackblitz.com/edit/nuxt-starter-bpyqqk?file=pages%2Fgood.vue

This is not a bug, this is how Vue reactivity works. With ss_sl.value you are just passing a number not a reactive object, so you lose reactivity. You can learn more here.

I can understand. Actually my goodcase gets the data after passing the ref variable, but in fact I'm using useAsyncData outside of the vue file, in which case I prefer it to be handled automatically rather than passing the reactive variable to an external js.
https://stackblitz.com/edit/nuxt-starter-bpyqqk?file=pages%2Fgood.vue

And when I actually pass multiple parameters, I have to take out the value of refs again, just like that:
const format_ref_params_dic = (ref_dic)=>{
    let formated_dic = {}
    for (const key in ref_dic) {
        formated_dic[key] = ref_dic[key].value
    }
    return formated_dic

}

----

const {data, error, refresh} = await useAsyncData(()=>$fetch(url, {
        method,
        params: format_ref_params_dic (params)   // eg: params = { page: ref<1> ,  size: ref<10>,  order: ref<'desc'> }
 })

it's a bit redundant, isn't it?

This is not a bug but the behavior of Vue's reactivity. The following article might be helpful:
https://antfu.me/posts/composable-vue-vueday-2021


Integer parameter value changed to floating type

Describe the bug
Integer parameter values defined in search space are changed to floating type during optimization.
Code to reproduce the behavior
search_space = dict(my_para = range(100, 200, 10))
opt = RandomSearchOptimizer(search_space)
opt.search(obj_func, n_iter=100)

# inside obj_func
def obj_func(my_para):
    for i in range(my_para):
        do_something()
    return score

Error message from command line
TypeError: 'numpy.float64' object cannot be interpreted as an integer
System information:

Ubuntu 21.04
Python version: 3.9.4
Gradient-Free-Optimizers version: 0.3.2

Additional context

This issue is reopened because if a related problem in Hyperactive.
The error can be replicated with this example:
from gradient_free_optimizers import RandomSearchOptimizer

search_space = dict(my_para=range(100, 200, 10), my_para_2=[0.1, 0.2, 0.3])

def obj_func(para):
    score = 1
    my_para = para["my_para"]
    print("my_para", my_para)
    for i in range(my_para):
        pass
    return score

opt = RandomSearchOptimizer(search_space)
opt.search(obj_func, n_iter=100)

@0liu,
the fix of the problem in issue 34 of Hyperactive seems very similar to this problem here, because the GFO Converter-class contains very similar methods (position2value, ...). Maybe you could fix the problem in GFO in a pull request. If you do so, make sure to test it in a simple script.

Yes I can make similar PR for GFO. Allow me a few days delay, maybe next week. Thanks.

Thanks @0liu for the pull request SimonBlanke/Gradient-Free-Optimizers#17. I wrote some additional fixes in 13821b1a2c4036ebab62dbbf8db23423d4db7982 and moved your tests in d0ef41b5f2327c50e055e8f59c9ba0b749b2e9f6. I also tested these changes against the current Hyperactive API and it all seems to work fine (but I did not test SimonBlanke/Hyperactive#34, yet).


change table of contents in Getting started with emotibit

Description
Type of correction

[ ] Documentation structure change
[x] Documentation update
[ ] Permission Issue(Any page you do not have access to)
[ ] Inaccurate content
[ ] Inappropriate content
[x] Outdated/Deprecated content

Link

Add Link to the page where the problem exits here

Screenshots

done


Make supply problems with factory production obvious to the user

Currently when a factory is unable to continue production due to a lack of resources, the factory just breaks out of the update loop and ignores the call with no notification to the user.
I haven't decided if this should raise a notification that is displayed to the user, if the Factory should go into a soft idle state (with the factory production window indicating the issue) or something else.
See the forum topic over at OPU for a discussion surrounding this.

Moving this to a later revision as part of the 'notifications' UI update. In the mean time the new Master Factory Report serves this purpose.

Setting as intermediate because it will require a thorough combing through of a large number of course files to ensure consistency. This is something that may be remedied by taking advantage of @Brett208 's efforts with the StringTable implementations in #458 #466 and #475


Move prefix and noprefix from internal to experimental

Previously, they were aliases into experimental but this does not work very well for ScalaDoc.
Contributor Checklist

[x] Did you add Scaladoc to every public function/method?
[ ] Did you add at least one test demonstrating the PR?
[x] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?
[x] Did you add appropriate documentation in docs/src?
[x] Did you state the API impact?
[x] Did you specify the code generation impact?
[x] Did you request a desired merge strategy?
[x] Did you add text to be included in the Release Notes for this change?

Type of Improvement

code refactoring

API Impact
This is a binary API breakage, but it is source compatible.
Backend Code Generation Impact
No impact
Desired Merge Strategy

Squash

Release Notes
Move implementation of prefix and noprefix from chisel3.internal to chisel3.experimental. They were previously aliased in experimental which does not work very well in the generated API docs.
Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (Bug fix: 3.4.x, [small] API extension: 3.5.x, API modification or big change: 3.6.0)?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you do one of the following when ready to merge:

[ ] Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
[ ] Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

I think there are some docs with this in the naming cookbook? Let's make sure they don't show the now-deprecated version

I think there are some docs with this in the naming cookbook? Let's make sure they don't show the now-deprecated version

The docs already import from chisel3.experimental.prefix because we were aliasing from there back to internal--now the alias is reversed.
This is failing CI because it is a binary incompatible change and thus the published chiseltest artifact does not work. We have the label to skip chiseltest CI but the problem is it will still fail on the push to master and thus new SNAPSHOTs will not be published. I could change this to not use an alias but rather use a deprecated object in package internal that has it's own apply method that just invokes the version in experimental. I'll do this tomorrow.

I cannot figure out how to avoid the binary compatibility issue. Keeping around the old object doesn't seem to do it so I'm at a loss. I'll just stick with the deprecated alias and manually publish SNAPSHOTs to deal with the integration test crash.

I'm confused about the binary compatibility issue, doesn't that check only exist on backport branches?


NLog does not output anything on webgl platform

We use Unity IL2CPP to compile codes (include NLog) in csharp to c++(il2cpp), and then use emscripten to compile codes to the final wasm. There are no errors either in compilation time or in the runtime, but nothing outputs. Does NLog support webgl platform?

Have you tried to enable NLog InternalLogger from code, and checked the output ? Maybe it is just something simple like not able to find NLog.config. See also: https://github.com/NLog/NLog/wiki/Logging-Troubleshooting
I have not used NLog with WebGL or IL2CPP, so I think you have to do your own investigations. If you see that code-changes are required for a better experience with WebGL, then pull-requests are always wellcome.

We finally get the outputs from the web console by providing a custom target, and in the target's Write method we send the message to UnityEngine's log system. In this way all the codes can be compiled to wasm and run successfully.

Thank you for sharing your experience. Good to know that NLog doesn't explode when running with WebGL / WASM.

Closing issue as resolved, due to inactivity


[zh] translate tutorial guestbook-logs-metrics-with-elk

translate tutorial guestbook-logs-metrics-with-elk into Chinese.
close #24505

/retitle [zh] translate tutorial guestbook-logs-metrics-with-elk

Overall looks good.
I'm proposing a tweak to the English content in #24675. Hopefully you can rebase the translation onto it so we don't need to resync again.
Thanks.

@zhiguo-lu since #24675 is in, please help rebase your PR onto the master for a resync.

@zhiguo-lu since #24675 is in, please help rebase your PR onto the master for a resync.

好的，很高兴收到你的comment和提醒。

谢谢订正。

/approve


fix(ScheduledSnapshotController): Confirm pod restoration before advancing

Closes https://github.com/strangelove-ventures/cosmos-operator/issues/182
Even though we delete appropriate data from the fullNodeRef status object AND check for the error, we've seen instances where the fullnode's status contains stale data. i.e. status data was never deleted. Therefore, the pod stays deleted even though the ScheduledSnapshotController expects it to be present.
I'm unsure of the root cause. I've yet to catch it in the act. I'm hoping this confirmation step solves this bug. The controller will continually retry restoring the pod until it's able to find it in a list query.

Related known edge case: https://github.com/strangelove-ventures/cosmos-operator/issues/196


A better way to do upsert

I have recently found out a better way to do upsert. Use the update method at the Dbcontext level. See the Microsoft docs:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.entityframeworkcore.dbcontext.update?view=efcore-6.0

Thank you for your interest in this project. This repository has been archived and is no longer actively maintained or supported. We appreciate your understanding. Feel free to explore the codebase and adapt it to your own needs if it serves as a useful reference. If you have any further questions or concerns, please refer to the README for more information.


use custom markers on map

i need to change the markers and use my custom markers... i could not find any provision to change it .... is there any way to so???

This is not related with my library.
See https://developers.google.com/maps/documentation/android-api/marker?hl=th#customize_a_marker


Use LokiJS instead of localStorage

This should fix #10. Map() is never persisted to disk, so I replaced it with LokiJS.

I did, but actually I think I'm going to close this for now. This may have worked for my implementation (which actually I ended up scrapping anyway), but I think it's too hacky and might break other people's projects.


Add customizable search

Overloaded contains function in UniqueItemList. Allows searching for a item using a given lambda function instead of only through isSame.

Codecov Report

Merging #73 (2ae5903) into master (ebe816c) will decrease coverage by 0.01%.
The diff coverage is 75.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@             Coverage Diff              @@
##             master      #73      +/-   ##
============================================
- Coverage     76.49%   76.49%   -0.01%
- Complexity      471      475       +4
============================================
  Files            77       77
  Lines          1455     1459       +4
  Branches        144      144
============================================
+ Hits           1113     1116       +3
  Misses          308      308
- Partials         34       35       +1

Files
Coverage Δ

...u/address/model/person/patient/UniqueItemList.java
82.00% <75.00%> (-0.61%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fail to compile in Swift4 Xcode9b4 -  'init()' is internal and cannot be referenced

First of all, great work! This excellent library worked very well for me. But now I am updating my apps to Swift4 (Xcode9b4) and suddenly have some errors.
ExtensionArray.swift:76:63: Initializer 'init()' is internal and cannot be referenced from a default argument value
ExtensionDecodable.swift:38:52: Initializer 'init()' is internal and cannot be referenced from a default argument value
I did download the swift_4-branch with no success.

Are those errors from building your app or from building Gloss?
I'm able to build Gloss from swift_4.0 branch using swift build && swift test normally (tests fail, but I have created PR #303 to have them pass). It's also "buildable" on Travis as you can see here: https://travis-ci.org/rbukovansky/Gloss/jobs/260950618

Thanks for your reply! It's coming from ExtensionArray.swift and ExtensionDecodable.swift found inside the Gloss project.
The project is it self a just migrated from Swift 3 to Swift 4.
I created a new fresh project with Gloss swift_4 and it does indeed compile but not my migrated project. I don't know if it's Xcode9-beta is pulling my legs. Cannot understand why it should be different?

from the sound of the error message it's that a public initializer needs to be added to GlossJSONSerializer as such:
public init() { }
can you try making that change to the pod locally and seeing if it fixes the issue?

Ah, that's it! Seems to compile just fine now.

Needed to add public init() { } in GlossLogger as well. The app is now running.

I'll update the swift_4.0 branch accordingly. thanks!

@jannejava merged - you can now work off branch swift_4.0


[bug] hide() does not appear to be working anymore

What happened?
A bug happened!
import play
tekst = play.new_text(
words='Je hebt gewonnen!',
x=0,
y=0,
)
tekst.hide()
play.start_program()
the text does not hide
Version
latest
Relevant log output
No response

This is due to us not caring about is_hidden and instead calling .update() always, we'll fix by introducing a way to "LOCK" updates on a sprite, which prevents the .update() method from being called, this will also pave a way for future features, for example .lock() stops all graphical updates on a sprite, allowing you to run for example a physics simulation and only after it's finished update the screen.


Logging DOM Document objects causes test failures (PhantomJS, Chrome)

I have the following basic Mocha test case that runs via Karma:
it.only("shouldn't fail when logging a DOM Document object", function() {
	var parser = new DOMParser();
	var doc = parser.parseFromString("<test></test>", "application/xml");
	console.log(doc); //Causes the test to fail
});

Running the test under PhantomJS triggers a test failure with the following error:
PhantomJS 1.9.7 (Mac OS X)  shouldn't fail when logging a DOM Document object FAILED
	Error: SECURITY_ERR: DOM Exception 18
	    at stringify (http://localhost:9876/karma.js:327)
	    at stringify (http://localhost:9876/karma.js:327)
	    at stringify (http://localhost:9876/karma.js:327)
	    at http://localhost:9876/karma.js:107
	    at http://localhost:9876/karma.js:85
	    ...

A similar but more informative error appears when running the same test in Chrome:
Chrome 35.0.1916 (Mac OS X 10.9.3)  shouldn't fail when logging a DOM Document object FAILED
	Error: Failed to read the 'cookie' property from 'Document': Access is denied for this document.
	    at Error (native)
	    at stringify (http://localhost:9876/karma.js:327:47)
	    at log (http://localhost:9876/karma.js:107:24)
	    at Console.localConsole.(anonymous function) [as log] (http://localhost:9876/karma.js:85:16)
	    ...

I wouldn't expect doing a console.log() to cause a test failure, but it looks like Karma's internal stringify() function accesses the Document object's cookie property which the browsers don't allow, and hence causes the browsers to throw exceptions which then fail the test.
Is this correct behavior? Should Karma's stringify() function handle this better? Manually running the same code in Chrome's console shows an exception for cookie property alone but still shows the other properties in the object.
(Note: The test code as presented here was simplified, but I ran into this issue by trying to log a backone.js model that referenced a DOM Document object internally.)

I am facing the same problem with a unit test of code that uses DOMParser().
Any chance of a fix for this?

+1 same issue as @hindsholm


Landing page update

not done yet with landing page, requesting to merge early!
also contains- Invoice Download

Seems good, does this complete the task in review?

Yes! But have a follow up as I mentioned


Handle Service Account auto mount with Deployment Spec token auto mount

The Deployment Spec token auto mount takes precendese over Service Account token
auto mount. Now both token auto mount properties should be set to true in order
to not mount volume.

A bit confused about what's being fixed and why it's being fixed this way. Could we not ignore these options and instead always include the service account token mounts / volumes?

A bit confused about what's being fixed and why it's being fixed this way. Could we not ignore these options and instead always include the service account token mounts / volumes?

You are right. I will just mount service account token, but only when service account is created. If user would like to disable Service Account, then PodTemplate would need to be used to mount service account token with service account name.


fix: 404 status error on new documents

Fix #244

:tada: This PR is included in version 6.7.6 :tada:
The release is available on:

GitHub release
v6.7.6

Your semantic-release bot :package::rocket:


Add details to README.md about how exactly this extension works

At the moment, the information provided is not enough to understand what exactly is meant by the wording "the important content", and based on what criteria this content will be searched for in the text of web pages.

I implemented this a long time ago (over 9 years ago), and don't recall the details.
It looks like a sentence's importance is calculated by assigning a score for each word in the sentence, and summing the scores. A word's score is based on its frequency throughout the document (higher scores for higher frequency).
https://github.com/dstein64/highlight/blob/3bf1319748af0760d901853b2719b3549cb6d542/src/content.js#L1067-L1186


L2: modify persistent-setup to require "Welcome Screen"

Then modify bails-wallet into bails-signer which will refuse to run if networking is on and warn and prompt to shutdown.
A new autostart will do the same thing on startup if it doesn't detect offline mode. It will not be practically possible to remove these features or connect to Tor if starting with networking. It will also prompt to turn the persistent feature of welcome screen, dotfiles, gnupg back on.
bails-signercreates and recovers the same BUT the wallet name step only has amnesic option. And it will always display the QR for its descriptors on creation. A way to redisplay the descriptor QRs in bails-menu is needed.
Instructions will clearly say not to store your bails-signer USB with your Bails Node for security reasons. Nor both devices together.
The two devices will be a 2-of-2 together
We need two evil maids in two locations to wreck this setup.
It's looking like the most effective way is to add a key or two to your "High" security hot wallet and store them in locations where only you know and then give 100% of the shares of bails-signer to heirs, family, friends, and professionals. All of whom must be instructed at least inside the envelope if not explicitly to only release their shares under specific conditions which ensure your freedom and safety and verified.
The default threshold will be 3 for this wallet. But a lower and higher level will be available as well as the usual customization. This is because people differ wildly in the number of heirs they have from just their parents and maybe one best friend or trusted professional to dozens.
3 is best however as the shares people are holding will not reveal the use of the 2-of-2 multisig scheme while threshold 3 would.
Assuming wallet is persisted on the offline signer the minimum security level is 2 things you have 1 thing you know (the passphrase).
If the offline signer wallet is amnesic. Then it will take 1 share from loved ones, the passphrase and the public key fingerprint of the online Bails to recover.  This is still "3 things" passphrase, ability to watch the L1 wallet and a share from bails-signer
Adding a share to the L1 setup will be MANDATORYotherwise going to multi-sig inevitably increases their risk of accidental loss since it's 2-of-2.
It's possible this setup can optionally decay to 1-of-2 after many years. 5-10 seems reasonable to discourage murder and incarceration.

@BenWestgate: convert this to a discussion "L2 design"


Add support for FreeBSD/aarch64

Yes, it's just a symlink to the amd64 folder. It Just Worked™.
Compiler binary for FreeBSD 12: https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/crystal/crystal-0.25.1-freebsd12.0-aarch64
Works great with LLVM 5.0.2. LLVM 6.0.1 results in assertion failures:
Assertion failed: (cast<DISubprogram>(Scope)->describes(&MF->getFunction())), function getOrCreateRegularScope, file /wrkdirs/usr/ports/devel/llvm60/work/llvm-6.0.1.src/lib/CodeGen/LexicalScopes.cpp, line 176.

Assertion failed: (SizeInBits != 0 && "invalid zero-sized type"), function getLLTForType, file /wrkdirs/usr/ports/devel/llvm60/work/llvm-6.0.1.src/lib/CodeGen/LowLevelType.cpp, line 34.

Assertion failed: (Index + MRI->getType(Res).getSizeInBits() <= MRI->getType(Src).getSizeInBits() && "extracting off end of register"), function buildExtract, file /wrkdirs/usr/ports/devel/llvm60/work/llvm-6.0.1.src/lib/CodeGen/GlobalISel/MachineIRBuilder.cpp, line 409.

On amd64, these don't appear.
Also, some spec failures:
  1) File symlink? gives true
     Failure/Error: File.symlink?(datapath("symlink.txt")).should be_true

       Expected: true
            got: false

     # spec/std/file_spec.cr:255

  2) File gets info for a symlink
     Failure/Error: info.type.should eq(File::Type::Symlink)

       Expected: Symlink
            got: File

     # spec/std/file_spec.cr:405

  3) String encode raises if illegal byte sequence
     Failure/Error: expect_raises ArgumentError, "Invalid multibyte sequence" do

       Expected ArgumentError but nothing was raised

     # spec/std/string_spec.cr:2298

  4) IO encoding decode says invalid byte sequence
     Failure/Error: expect_raises ArgumentError, "Invalid multibyte sequence" do

       Expected ArgumentError with "Invalid multibyte sequence", got #<ArgumentError: Incomplete multibyte sequence> with backtrace:
         # Iconv#handle_invalid<Pointer(Pointer(UInt8)), Pointer(UInt64)>:(UInt64 | Nil)
         # IO::Decoder#read</usr/home/greg/crystal/spec/std/io/io_spec.cr::SimpleIOMemory>:Nil
         # IO::Decoder#read_byte</usr/home/greg/crystal/spec/std/io/io_spec.cr::SimpleIOMemory>:(UInt8 | Nil)
         # /usr/home/greg/crystal/spec/std/io/io_spec.cr::SimpleIOMemory
         # /usr/home/greg/crystal/spec/std/io/io_spec.cr::SimpleIOMemory
         # /usr/home/greg/crystal/spec/std/io/io_spec.cr::SimpleIOMemory
         # /usr/home/greg/crystal/spec/std/io/io_spec.cr::SimpleIOMemory
         # ~procProc(Nil)
         # it<String, String, Int32, Int32, &Proc(Nil)>:(Array(Spec::Result) | Nil)
         # ~procProc(Nil)
         # Spec::RootContext::describe<String, String, Int32, &Proc(Nil)>:Spec::Context+
         # describe<String, String, Int32, &Proc(Nil)>:Spec::Context+
         # ~procProc(Nil)
         # Spec::RootContext::describe<String, String, Int32, &Proc(Nil)>:Spec::Context+
         # describe<String, String, Int32, &Proc(Nil)>:Spec::Context+
         # ~procProc(Nil)
         # Spec::RootContext::describe<String, String, Int32, &Proc(Nil)>:Spec::Context+
         # describe<IO:Class, String, Int32, &Proc(Nil)>:Spec::Context+
         # __crystal_main
         # Crystal::main_user_code<Int32, Pointer(Pointer(UInt8))>:Nil
         # Crystal::main<Int32, Pointer(Pointer(UInt8))>:Int32
         # main

     # spec/std/io/io_spec.cr:659

  5) IO encoding encode raises on invalid byte sequence
     Failure/Error: expect_raises ArgumentError, "Invalid multibyte sequence" do

       Expected ArgumentError but nothing was raised

     # spec/std/io/io_spec.cr:821

  6) Time::Location .load_local
     Failure/Error: Location.load_local.name.should eq "Local"

       Expected: "Local"
            got: "UTC"

     # spec/std/time/location_spec.cr:166

Finished in 1:08 minutes
13906 examples, 6 failures, 0 errors, 14 pending

Failed examples:

crystal spec spec/std/file_spec.cr:254 # File symlink? gives true
crystal spec spec/std/file_spec.cr:403 # File gets info for a symlink
crystal spec spec/std/string_spec.cr:2297 # String encode raises if illegal byte sequence
crystal spec spec/std/io/io_spec.cr:656 # IO encoding decode says invalid byte sequence
crystal spec spec/std/io/io_spec.cr:818 # IO encoding encode raises on invalid byte sequence
crystal spec spec/std/time/location_spec.cr:164 # Time::Location .load_local

They don't look very aarch64 related. I never ran spec on amd64 though…

Thanks!
About LLVM errors, I'm afraid you'll have to dig to understand where they come from. Maybe we have an issue with Crystal+LLVM6 on AArch64 :cry:
About spec failures:

maybe a wrong value for LibC::S_IFLNK? Or the issue was caused by the File::Stats to File::Info change?
ditto;
depending on iconv library maybe we can't detect all issues, or FreeBSD needs a specific check (see https://github.com/crystal-lang/crystal/issues?utf8=✓&q=iconv+freebsd);
probably the iconv/errno message is different on FreeBSD that what the spec expects;
same as 3.
maybe we fail to find tzdata files (see https://github.com/crystal-lang/crystal/blob/master/src/crystal/system/unix/time.cr) or related to TZ environment variable.

It would be interesting to see which specs also fail on x86_64-freebsd12.

No 6 is either an issue with environment variables (nil interpreted as "") or the platform-specific Crystal::System::Time.load_localtime (i.e. loading /etc/localtime).
For debugging, just add the following expression before the failing spec line:
pp ENV["TZ"]?, Crystal::System::Time.load_localtime

No. 6 should be fixed by #6740.

@myfreeweb This needs an update after #7282. Also would be great if you could revisit the previously found issues.

Updated the symlink (the patch here). I don't have the time to work on spec failures, unfortunately.

Does this still work on recent LLVM versions?

Why wouldn't it? There's nothing llvm dependent here, this PR simply adds symlinks for platform libc bindings (because there's no difference to amd64).
We do build the downstream package (currently 1.1.1 with llvm10 yes i know it's time to update) for aarch64 using the same symlinks.


Auto publish NPM module upon merge to main

As a by product of this, the main branch should be locked to PR only

[x] Main branch is now locked to merge only
[x] Feat: type merges will trigger a breaking change release
[x] fix, chore, etc. type merges will trigger patch releases


Don't let backgroundColor overflow past borderRadius

Re-opening #904, note the orange corners that shouldn't be there:

Should be:

overflow: 'hidden' fixes it, but it should not be needed – not showing the backgroundColor should be the default behavior.
v0.31.0, mac, iOS

@lorensr you're probably right, this should be fixed without relying on the overflow: 'hidden' work around. At the very least, we should mention this in the docs. React native is a community project and so we rely on the community to help improve things. Would you be willing to submit a PR that either fixes this properly or at least updates the docs to help others understand the work around?

Don't have time right now, but whereabouts in the code would the fix be?
On Wednesday, September 7, 2016, Chris Geirman<EMAIL_ADDRESS>wrote:

@lorensr https://github.com/lorensr you're probably right, this should
be fixed without relying on the overflow: 'hidden' work around. At the
very least, we should mention this in the docs. React native is a community
project and so we rely on the community to help improve things. Would you
be willing to submit a PR that either fixes this properly or at least
updates the docs to help others understand the work around?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/9494#issuecomment-245433776,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPVmJXY2J6VZ5qEORB5BlkIpsqLyobGks5qnzTmgaJpZM4JpKLu
.

¯_(ツ)_/¯

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/dont-let-backgroundcolor-overflow-past-borderradius
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.

@facebook-github-bot label Icebox

@facebook-github-bot close


where can i get bcms/train.txt and bcms/dev.txt?

where can i get bcms/train.txt and bcms/dev.txt?

Hi, the BCMS data used for building the available BCMS model was part of the VarDial 2020 evaluation campaign, social media variety geolocation task: https://sites.google.com/view/vardial2020/evaluation-campaign. I think it is best you contact the task contact person (yves.scherrer(at)helsinki.fi) to obtain the data from the shared task.
Otherwise, you can use your own data to train a model.


Pagination is very slow

Hello,
I am writing about an issue that I encountered with the "ShareGPT" repository on GitHub. When attempting to retrieve conversations by page, I noticed that as the number of pages increases, the query becomes slower, eventually leading to a timeout on the Vercel Serverless Functions. Specifically, I found it almost impossible to retrieve conversations beyond page 200.
As an example, I tried to retrieve conversations from page 1000 using the following query:
https://sharegpt.com/api/conversations?page=1000
However, the query resulted in a 504 error with the message "GATEWAY_TIMEOUT" and the code "FUNCTION_INVOCATION_TIMEOUT."

Update: We removed the Explore page on ShareGPT recently so this issue is no longer relevant – closing it now!


Problem with STDDEV strategy error

Hello,
I'm using zenbot with this command line
./zenbot.sh trade --paper kraken.XXLM-ZEUR --strategy stddev --period=5000ms
it works for like 10 minutes, i can see some information about last exchange but it stops with this
/home/antoine/zenbot/extensions/strategies/stddev/strategy.js:24
for (let i = 0; i < s.options.trendtrades_1; i++) { tl0.push(s.lookback[i].close) }
^
TypeError: Cannot read property 'close' of undefined
at Object.onPeriod (/home/antoine/zenbot/extensions/strategies/stddev/strategy.js:24:82)
at onTrade (/home/antoine/zenbot/lib/engine.js:921:27)
at /home/antoine/zenbot/lib/engine.js:899:5
at /home/antoine/zenbot/node_modules/async/dist/async.js:4096:9
at Object.process (/home/antoine/zenbot/node_modules/async/dist/async.js:2344:17)
at /home/antoine/zenbot/node_modules/async/dist/async.js:2252:19
at Immediate._onImmediate (/home/antoine/zenbot/node_modules/async/dist/async.js:119:16)
at runCallback (timers.js:810:20)
at tryOnImmediate (timers.js:768:5)
at processImmediate [as _immediateCallback] (timers.js:745:5)
Can you help me because I would like to put this bot in a raspberry py in the futur, my actual system OS is kali linux

Same problem here, running Ubuntu 18.04 LTS in a VM:
(node:2836) DeprecationWarning: collection.save is deprecated. Use insertOne, insertMany, updateOne,│········································································································
 or updateMany instead.                                                                             │········································································································
2018-12-04 09:42:06  3491.19 BTC-EUR                 0                       0.01588 BTC  0.55 EUR  │········································································································
 -0.96%   -2.98%                                                                                │········································································································
2018-12-04 09:42:25  3489.49 BTC-EUR   -0.05%        0                       0.01588 BTC  0.55 EUR  │········································································································
 -1.01%   -2.98%                                                                                │········································································································
/home/david/repos/zenbot/extensions/strategies/stddev/strategy.js:24                                │········································································································
      for (let i = 0; i < s.options.trendtrades_1; i++) { tl0.push(s.lookback[i].close) }           │········································································································
                                                                                ^                  │········································································································
                                                                                │········································································································
TypeError: Cannot read property 'close' of undefined                                                │········································································································
    at Object.onPeriod (/home/david/repos/zenbot/extensions/strategies/stddev/strategy.js:24:82)    │········································································································
    at onTrade (/home/david/repos/zenbot/lib/engine.js:920:27)                                      │········································································································
    at /home/david/repos/zenbot/lib/engine.js:898:5                                                 │········································································································
    at /home/david/repos/zenbot/node_modules/async/dist/async.js:4096:9                             │········································································································
    at Object.process (/home/david/repos/zenbot/node_modules/async/dist/async.js:2344:17)           │········································································································
    at /home/david/repos/zenbot/node_modules/async/dist/async.js:2252:19                            │········································································································
    at Immediate._onImmediate (/home/david/repos/zenbot/node_modules/async/dist/async.js:119:16)    │········································································································
    at runCallback (timers.js:810:20)                                                               │········································································································
    at tryOnImmediate (timers.js:768:5)                                                             │········································································································
    at processImmediate [as _immediateCallback] (timers.js:745:5)

Any idea?

Same problem

bump


add site support for collapsible panes

is it possible to add site support for collapsible panes?

An even better idea would be to have multi-tabbed content areas.


Implement initial support for STM32L4P5 (and therefore STM32L4Q5)

This pull request adds initial support for STM32L4P5 (and therefore STM32L4Q5).
It replaces Pull Request #773 which contained merges.
Done:

Mmaps compared to reference manual revision 9 (should fully match now)
Enumerated values added where available / possible

Known issues:

few peripherals missing (most notably TAMPER peripheral).

As this is quite a lot of patches and also new enumerated values I would kindly ask for feedback in case things should be organized differently.

@adamgreig @burrbull Any chances to merge this?

bors r=@newAM

bors r+

Thank you so much @newAM!
I'm gonna test it anyways in the weeks coming up so if any issues pop up I will do another pull request.
The RM is pretty bad in some parts. Firewall I never used myself so sometimes it was a guessing game what the RM means...