Automatic graph layout

Following techniques outlined in this paper, we should implement an automatic graph layout algorithm.

One issue with the paper is needing to properly be able to control drawing transitions. Looking at JFLAP the degree tree layout algorithm seems to give pretty good results
Before: Using a messy graph where I just kept drawing transitions

After

The algorithm seems pretty simple, ~200 lines* of Java in JFLAPs implementation (which also includes a hierarchical based algorithm along with degree based)
*Excluding comments, also I might've miscounted

We sadly ran out of time before being able to implement this.
Good luck group 4 🫡

I've begun progress in the feat/auto-layout branch but not happy enough with it to make a PR for the final sprint. It's been a headache so good luck future team 🫡.


Journal Entry: Long-term Storage

See #184 for context.

[ ] common requirements
[ ] Fabrikam's requirements
[ ] logical solutions
[ ] technology options
[ ] security concerns
[ ] learnings

Fabrikam's requirements
Fabrikam wants to keep the raw event data from devices indefinitely. Their business motivations are two-fold:

Legal accounability - They want to be able have as much data as possible available should any contention arise.
Future insights - They believe that they will be able to analysize the data at some point in the future (perhaps even the very near future). They believe that this insight will open up new and unforeseen business value.

The have the following requirements:

The storage should be as inexpensive as possible since thethe events indefinitely.
Low latency access to the data is not expected.
The data should be accessible to a batch analytics process. Fabrikam expects to use Hadoop (Hive in particular).
They do not want to lose any events. Duplicate events in the long-term storage are acceptable. It is assumed that duplicates can be detected and addressed after the fact (or even as part of the batch analytics).


BaseUrl problem

Is anyone run into baseUrl problem in tsconfig.json?

In tsconfig.json I have "baseUrl": "./".
When I"m importing from scss from assets, sticking with error "Can't find stylesheet to import".
Changing to @import "../../../../../../../assets/styles/colors.scss" fixes the error, but it's not a solution... @manfredsteyer


Login and use cookie not working

I am trying to access a login form, login and then access a page behind the login.
I have tried the below code. Logging out the body of the POST call just returns the login page before login has happened.
Logging out the next call is returning the second page but not logged in.
Any ideas?
var request = require('request').defaults({jar: true});

request({
    method: 'POST',
    url: 'https://localhost/login',
    form: {
      username: 'username',
      password: 'password'
    },
  }, function (err, resp, body) {
    console.log(body);
   request('https://localhost/user', function (err, resp, body) {
       console.log(body);
   });
})

My Login URL turned out to be incorrect for the post!


Make Communicator and Group traits "object safe"

This PR makes the Communicator and Group traits "object safe," it will allow you to write things like:
fn foo(comm: &dyn Communicator) { }
fn bar(gp: &dyn Group) { }

fixes #108

Thanks; pipeline is running. Would you be able to add a simple test in this PR?

I could probably do that. How and where should I add it?

Add or modify an existing example (those are run with 2..4 processes) or add in tests/ (which will be run sequentially, but that's faster and probably sufficient). I'd just like a test so we don't accidentally lose object safety in the future.


Upgrade AWS SDK here as well.

I could be wrong, only had a quick look but I think it's the name of your branch. Because it starts with aws I don't think it's allowing you to create param store values with that name and hence TF is failing. I'd start a branch with a different name that doesn't start with AWS and it should work fine :)

Thanks Jim, will move to a different branch name.


Warning: findDOMNode is deprecated and will be removed in the next major release.

Warning: findDOMNode is deprecated and will be removed in the next major release. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here:

Hello, we tried to solve the issue.
This is what we did:
Updated the DropzoneComponent to use React.createRef() instead of ReactDOM.findDOMNode() to address the deprecation warning. This change maintains the existing functionality while using the recommended React API for referencing DOM elements.
You can review changes in this commit: https://github.com/zxsa89675/felixrieseberg-React-Dropzone-Component-238/commit/80e54499e407bb63246641f67239857f95e83b10.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.

ok , so  i need to reinstall version 3.1.3 right ?

i still have the same issue , what do i need to do


Inactive on startup. Throws NullPointerException

Ripme version:

ripme -v
1.7.94

Java version:

java -version
openjdk version "15.0.2" 2021-01-19
OpenJDK Runtime Environment (build 15.0.2+7)
OpenJDK 64-Bit Server VM (build 15.0.2+7, mixed mode)

Results are the same for openjdk8

Operating system:

ArchLinux 5.11.2-arch1-1
Using XFCE

I just installed RipMe and it launches in the dock. I have not made any configuration. Execution stalls at:
ripme
Loaded file:/usr/share/java/ripme.jar!/rip.properties
Setting locale to default
Loaded log4j.properties
Initialized ripme v1.7.94
Getting key select.save.dir in en_US value Select Save Directory
Getting key loading.history.from.configuration in en_US value Loading history from configuration
Loading history from configuration
Exception in thread "main" java.lang.NullPointerException: Cannot read the array length because "<local3>" is null
        at com.rarchives.ripme.ui.MainWindow.loadHistory(MainWindow.java:1186)
        at com.rarchives.ripme.ui.MainWindow.<init>(MainWindow.java:186)
        at com.rarchives.ripme.App.main(App.java:89)

Like #446 it says it's inactive and does not work.
It prints: Getting key tray.hide in en_US value Hide when switching windows.

so this is the relevant code: https://github.com/RipMeApp/ripme/blob/master/src/main/java/com/rarchives/ripme/ui/MainWindow.java#L1186
                String[] dirs = Utils.getWorkingDirectory()
                        .list((dir, file) -> new File(dir.getAbsolutePath() + File.separator + file).isDirectory());
                for (String dir : dirs) {

stackoverflow says:
https://stackoverflow.com/questions/65737245/java-lang-nullpointerexception-cannot-read-the-array-length-because-local3
"This way your member variable stays uninitialized."

please try latest from here:
https://github.com/ripmeapp2/ripme/releases

please try latest from here:
https://github.com/ripmeapp2/ripme/releases

This one did work. Thanks.


Use with no prediction

Could ggrs set prediction to 0?
Currently it crashs with max_prediction 0 or 1.
This would be useful when it is difficult to provide savestate, ex; unofficial netbattle project.

Sorry, I posted this in the wrong place.


blopentype support is broken

If I try to run
https://texlive.net/run?%25 !TEX luatex
\input blot
hello world!
\bye
the system cannot run the macro package.
This issue has been reported on the blopentype repository here:
https://github.com/jarnosz/blopentype/issues/2#issuecomment-1608263537
And is similar to the question on CygWin64 posted on TeX/StackExchange.
The error cannot be reproduced with the native Win64 TeXLive installation.

Sorry, I can't see  any  issue for the server which is running a standard texlive 2023 on linux.
As far as I can see the code errors in any linux/cygwin texlive and that error is correctly reported by the server here.


Most referenced projects page

List top 100

No need to limit the amount. Make leaderboard table have pages and this also fixes #24


Add CI workflow to validate generated Docker image

Summary

Resolves #30

Changes

added a ci workflow to validate docker image against jaeger and jaeger-idl
this workflow runs proto build step of both repos

ran successfully on my fork

https://github.com/akagami-harsh/docker-protobuf/actions/runs/6839377378/job/18597466239?pr=2


[Starfinder By Roll20] Removing Equipment

Removing an item from the equipment section does not update carried bulk or wealth.

Thank you for the report MTVExtreme,
I've found the problem, and will hopefully have the fix out soon.

Closing issue as a pull request has been merge to fix this. If its not fixed after tomorrow we can open it again.


The error message on unresolved implicits are poor if implicits are imported via { ? }

If an implicit argument could not be resolved the typechecker displays a list of all bindings that were considered. This works well for bindings that can be refereed to directly but when an implicit were imported via { ? } there is no proper binding to refer to.
What happens instead is that the error will display implicit?<number>  which is the name of a generated variable.
let { ? } = import! std.option
let { List } = import! std.list
Cons 1 Nil == Nil
// ^ Unable to resolve impliciit ... candidates: implicit?123.eq, ...

One way of fixing this would be to make implicit imports (?) be bound on identifiers instead of records. That way there is always an identifier to refer to.
Another way would be to track the position of the import better and say something akin to
Unable to resolve implicit candidates:
eq: Eq String imported from line x, column y
let { ? } = import! std.string
       ^


parts of process vote; PendingVotesSpec (not used)

Signed-off-by: Harold Carr<EMAIL_ADDRESS>This contains an incomplete implementation of RoundManager.processVoteMsgM.
If it is needed before I am available again, go ahead and complete it.  Otherwise, it is fine to leave it as is.
There are places in this request that have IMPL-TODO - it would be good to have feedback/fixes for those places.

@mark-moir - I think you meant to @haroldcarr who, if I do say so myself, has a lovely first name.
Looks like a fun project, best of luck with the verification.

@harold, yes indeed I meant @haroldcarr, thanks for the heads up.

@mark-moir I agree with your proposal to split off the fake and real implementation. I am at a point where it make sense to start connecting the work on proving properties about a single peer step to invariants of the system, and this split would make that much easier.


[BUG][OpenSearch Dashboards] Use of plugins.installList fails because access denied to plugin images

Describe the bug
I attempted to limit which plugins were loaded with OpenSearch Dashboards by using the plugins.installList key.  The OpenSearch Dashboards pod failed to come up and displayed messages indicating the URL (pointing to the plugin zip file) was not valid.  When I attempt to access that URL in my browser, it indicates that I do not have access.  (Specific error messages included below.)
To Reproduce
Steps to reproduce the behavior:

I added the following to my user-values.yaml file:

plugins:
  enabled: true
  installList:
  - opensearch-alerting
  - opensearch-index-management
  - opensearch-job-scheduler
  - opensearch-reports-scheduler
  - opensearch-security
  - opensearch-sql

I then deployed OpenSearch Dashboards using the Helm chart and pointing to my user-values.yaml file
I confirmed that the values were picked up and used to construct a command within the OpenSearch Dashboard pod defintion (as shown below):

      containers:
        - name: dashboards
          image: opensearchproject/opensearch-dashboards:2.4.1
          command:
            - sh
            - '-c'
            - >
              #!/usr/bin/bash
              set -e
              ./bin/opensearch-dashboards-plugin install opensearch-alerting
              ./bin/opensearch-dashboards-plugin install opensearch-index-management
              ./bin/opensearch-dashboards-plugin install opensearch-job-scheduler
              ./bin/opensearch-dashboards-plugin install opensearch-reports-scheduler
              ./bin/opensearch-dashboards-plugin install opensearch-security
              ./bin/opensearch-dashboards-plugin install opensearch-sql
              bash opensearch-dashboards-docker-entrypoint.sh     opensearch-dashboards

I then watched the OpenSearch Dashboards pod logs signs of success.  However, I only see the following messages:

Attempting to transfer from opensearch-alerting
Attempting to transfer from https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.4.1/latest/linux/x64/tar/builds/opensearch-dashboards/plugins/opensearch-alerting-2.4.1.zip
Plugin installation was unsuccessful due to error "No valid url specified."

When I attempt to access that URL via my browser, it fails with the following XML error indicating that I do not have access

<Error>
AccessDenied
<Message>Access Denied</Message>
<RequestId>RCBX79B9PSDAPH2H</RequestId>
<HostId>
UEXoSll4fjiMSQOUNb3y59M94H9p8U/4U0wvoptBP4UMUpwrKa+gPQ5NkWRTA/fVMCUvEUAsnhE=
</HostId>
</Error>

Expected behavior
I had expected that OpenSearch Dashboards would deploy successfully and only include the plugins I had specified
Chart Name
OpenSearch Dashboards (version 2.7.0)
Host/Environment (please complete the following information):

Helm Version: 3.7.0
Kubernetes Version: 1.22.3

Additional context
Add any other context about the problem here.

Will debug this.

@gsmith-sas It seems you are trying to install OpenSearch plugins inside OpenSearch Dashboards docker image. Please use the OpenSearch chart to install opensearch supported plugins.

Hey @gsmith-sas FYI the dashboard plugins list https://opensearch.org/docs/latest/install-and-configure/install-dashboards/plugins#install.
Thank you

Hey @gsmith-sas you could try with for example ./bin/opensearch-dashboards-plugin install alertingDashboards to install dashboards plugin.
https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.4.1/latest/linux/x64/tar/builds/opensearch-dashboards/plugins/alertingDashboards-2.4.1.zip is an available URL link.

@rishabh6788 @prudhvigodithi @zelinh Thank you all for responding and pointing out I was trying to use OpenSearch plugins with OpenSearch Dashboards.
I just tried again being careful to only list specific OpenSearch Dashboards plugins in the user-values.yaml file passed to the OpenSearch Dashboards helm chart.  I got a little further along this time but still no success.  The OpenSearch Dashboards pod attempted to start and, looking at the pod logs, I can see that it was able to download the Alerting dashboards plugin.  Here are the pod log messages:
Attempting to transfer from alertingDashboards
Attempting to transfer from https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.4.1/latest/linux/x64/tar/builds/opensearch-dashboards/plugins/alertingDashboards-2.4.1.zip
Transferring 7147208 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Extracting plugin archive
Extraction complete
Plugin alertingDashboards already exists, please remove before installing a new version

The OpenSearch Dashboards pod also restarts after this.  Most of the time, the messages about transferring and extracting the plugin archive appear twice.  But it isn't clear to me whether that happens twice before the pod restarts or if the 2nd set of messages is from after the restart.
By the way, I am using the publicly available OpenSearch Dashboards container image (opensearchproject/opensearch-dashboards:2.4.1).  Does that image have all of the plugins already installed?  If so, is there an alternative container image that does not have plugins pre-installed?

@gsmith-sas The OpenSearch and OpensSearch Dashbords images come pre-installed with all the plugins. Not sure why you are trying to install again?

@rishabh6788 I wasn't (intentionally) trying to re-install all of the plugins.  But I was hoping to limit which ones were loaded.  As I mentioned in my updated comments, our application doesn't make use of several plugins (e.g. Anomaly Detection, Observability, etc.).  I was hoping to exclude those plugins from the installation to eliminate menu items related to those plugins from appearing in OpenSearch Dashboards.  That would help us minimize confusion among our end-users and eliminate the need to tell them to ignore various options.
Is is possible to exclude certain plugins when deploying via the Helm charts?  Or, alternatively, is is possible to use security settings to "hide" options that the user doesn't have access to?

@gsmith-sas to remove plugins you can just replace install with remove keyword in your command, e.g., ./bin/opensearch-dashboards-plugin remove opensearch-alerting. Let me know if that helps.

Thanks @rishabh6788.  But I'm trying to use what the Helm chart supports and it doesn't seem to support a plugins.excludelist option.  Maybe that's something I should open a feature request for.  But would that work?  If the pod's container definition already includes all of the 'standard' plugins, could we still remove them using the command you shared?  If so, I suspect it could be implemented similar to the existing logic for deploying additional plugins.

@prudhvigodithi Can you please take a look at above request?

Hey @gsmith-sas thanks for the explanation, the plugins cannot be removed using helm chart, the helm chart purpose is to install new plugins from the given defaults, also since the OpenSearch dashboard bundle comes with the default, the official helm chart of the OpenSearch dashboard should honor them.
Secondly removing the defaults is not recommended, also adding a flag to add/remove in helm chart is dangerous switch, as it could remove the installed settings when chart is redeployed.
With this we have 2 options.

Build a custom Image of your choice of installed plugins (by removing the not required ones).
Hack the postStart from the chart lifecycle settings to remove the plugin.

Tagging other maintainers to get some more feedback.
@bbarani @peterzhuamazon @TheAlgo @DandyDeveloper


Replace error summary and fields with shared templates from MTP-utils

will not pass tests until mtp-utils#13 is merged and on pypi

retest this please


how to show only one validation error message per field

I have a registration form and a user has to submit email address in the form (along with other fields). my validation rule for the email field with 'express-validator' is
req.checkBody('email', 'Email field is required').notEmpty().isEmail().withMessage('Invalid email address');
and I am using jade to print out the errors as (with bootstrap)
  if errors.length
    .alert.alert-danger
      a.close(href='#', data-dismiss='alert', aria-label='close') ×
      for error in errors
         div=error.msg

the above code print out all the form errors of the fields, now the problem is, if email field is empty, it shows two error messages 'Email field is required' and 'Invalid email address'
I want to evaluate the second validation isEmail() only if the email is not empty. If empty then it need to show only one error message 'Email field is required'. Is there any solution to this ?

Maybe this will help - according to the docs if you specify:
var mappedErrors = req.validationErrors(true);
You only get 1 error per field.

@james-siteclick that will not help in this case, still both validations isEmpty() and isEmail() will be executed. req.validationErrors(true) will return only last error which will be something like:
{
  "email": {
    "param": "email",
    "msg": "Invalid email address"
  }
}

@grandcoder
As it seems to me from source code this is not possible at the moment because regardless of validation status true/false all further validations will be executed. I will put enhancement label to this issue and will look into this in details as soon as possible.

Hi everyone! The fix for this has finally landed in v3.0.0!
req.getValidationResult().then( result => {
  var errors = result.useFirstErrorOnly().array(); // enjoy an array with no duplicated errors for any given parameter!
})

Do you prefer the old style of mapped errors? We've got you covered:
req.getValidationResult().then( result => {
  var errors = result.useFirstErrorOnly().mapped();
})

But it is NOT the same issue as break validation chain. When I want to use exist() validator there is no need to validate an empty field by other validators. Isn't it obvious ? And if the field is not empty I want see ALL possible errors ! But this lib can't do that unfortunately.

Hi @deveArt!
Let's break your comment into parts:

When I want to use exist() validator there is no need to validate an empty field by other validators. Isn't it obvious ?

The exists() validator was added as of v4. It's mainly a measure for users who simply want to check that a field is present. You can combine it with other validators as well, but it doesn't make much sense.
What does make sense though is to use optional(). Fields that are tagged as optional will not run thru any of the other validators. This behaviour remained the same since v2.

And if the field is not empty I want see ALL possible errors ! But this lib can't do that unfortunately.

It does.
When v3 was first introduced, the .array() method in the validation result would return all errors by default. You could, however, combine it with useFirstErrorOnly() method, which would then skip all errors but the first one for each field.
v4 still allows you to do both when using the array() method of the validation result.
Thanks!

I have a situation where I should break the chain before passing to the next validation method:
check('source')
    .isLength({ min: 1 }).withMessage('Required')
    .isMongoId()
    .custom(rules.existSource)

// existSource will check if the id exist in sources collection and return true or false

If I send an empty source I get an error:

Cast to ObjectId failed for value "" at path "_id" for model "Source"

this error is throwing because the existSource validator expect a valid mongoID, I think it would be faster if the chain stopped at the first occurring error.
you can for example pass it as an option:
 const validator = require('express-validator');
 const check = validator.check({ StopValidationOnFirstError: true });

Thanks


When using chained select, dependent doesn't clear value when the field it depends on clears

If using chained selects with filter_by,

Select a value in the filtering select field
Select a value in the filtered (dependent) select field
Change the filtering select field to a new value

The filtered select should be cleared out, because its existing value depended on the previous value of the filtering select, and may not actually be valid any longer.

Resolved in 2024.12.2


feat: Make Facsimile of paper-translation's cover.

fix: https://github.com/BITNP/BIThesis/issues/97

fix: https://github.com/BITNP/BIThesis/issues/97


Feature request: support a Ruby DSL

How about something like this?
# config/settings/foo.rb

Figleaf::Settings.configure(:foo) do
  default do
    foo_enabled = true
  end

  env(:development) do
    foo_enabled = false
  end
end

# When RAILS_ENV = 'development'
Figleaf::Settings.foo.foo_enabled? #=> false

# When RAILS_ENV is any other value:
Figleaf::Settings.foo.foo_enabled? #=> true

CC @delwaterman @jcmuller

@agibralter is the idea to move configuration completely out of YAML?

Nah. It's just an alternative configuration style that would give us more flexibility. YAML+ERB would still be supported.


fix: added constraint

Summary of changes:

Added memory constraint to MySQL charm deployment.

NOTE: This is debug PR.

Looks like this time out did the trick.

I think we can close this PR, it seems like the CI in main does not have problems anymore.

This was a debug PR. Closing.


stop parsing init script at the "### END INIT INFO" marker.

Signed-off-by: Guido Schoening<EMAIL_ADDRESS>Description
Spring Boot Webapps cat contain an init script as a header of the jar.
By stopping to parse the init script at the marker the binary part of the file is no longer parsed which avoids errors trying to parse binary data as a string. Furthermore to iterate over lines after the marker is unnecessary
Issues Resolved
[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussion that's relevant]
Check List

[x] New functionality includes tests
[x] All tests pass
[x] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Thanks @goblin23


Increase kubernetes libs version

Hello. Some k8s manifest fields not supported by old libs version. For example, startupProbe , which added in k8s 1.16.

@preved911 did you try to test with e2e from ./tests/ folder?

@Slach if I understand correctly, all the necessary tests pass:
Passing

✔ [ OK ] /main/operator/test_001. 1 node
✔ [ OK ] /main/operator/test_002. useTemplates for pod, volume templates, and distribution
✔ [ OK ] /main/operator/test_004. Compatibility test if old syntax with volumeClaimTemplate is still supported
✔ [ OK ] /main/operator/test_005. Test manifest created by ACM
✔ [ OK ] /main/operator/test_006. Test clickhouse version upgrade from one version to another using podTemplate change
✔ [ OK ] /main/operator/test_007. Test template with custom clickhouse ports
✔ [ OK ] /main/operator/test_008. Test operator restart
✔ [ OK ] /main/operator/test_010. Test zookeeper initialization
✔ [ OK ] /main/operator/test_011. Test user security and network isolation
✔ [ OK ] /main/operator/test_011_1. Test default user security
✔ [ OK ] /main/operator/test_012. Test service templates
✔ [ OK ] /main/operator/test_013. Test adding shards and creating local and distributed tables automatically
✔ [ OK ] /main/operator/test_014. Test that replication works
✔ [ OK ] /main/operator/test_015. Test circular replication with hostNetwork
✔ [ OK ] /main/operator/test_016. Test advanced settings options
✔ [ OK ] /main/operator/test_017. Test deployment of multiple versions in a cluster
✔ [ OK ] /main/operator/test_019. Test that volume is correctly retained and can be re-attached
✔ [ OK ] /main/operator/test_020. Test multi-volume configuration
✔ [ OK ] /main/operator/test_021. Test rescaling storage
✔ [ OK ] /main/operator/test_023. Test auto templates
✔ [ OK ] /main/operator/test_024. Test annotations for various template types
✔ [ OK ] /main/operator/test_025. Test that service is available during re-scalaling, upgades etc.
✔ [ OK ] /main/operator
✔ [ OK ] /main

Known

✘ [ XFail ] /main/operator/test_009. Test operator upgrade ᐅ May fail due to label changes
✘ [ XFail ] /main/operator/test_024. Test annotations for various template types/PV annotations should be populated ᐅ Not supported yet
✘ [ XError ] /main/operator/test_022. Test that chi with broken image can be deleted ᐅ Not supported yet. Timeout

2 modules (2 ok)
24 scenarios (22 ok, 1 xfail, 1 xerror)
566 steps (559 ok, 4 failed, 2 errored, 1 xfail)

Total time 1h 7m

Executed on Mar 22,2021 22:13
TestFlows.com Open-Source Software Testing Framework v1.6.201216.1172002

The notion of context execution is already introduced in 0.14.0 and it would be correct to leverage it instead of creating a separate independent context for each API call.


No extension logs displayed

Raycast version: 1.31.0
Description
I wanted to debug Home Assistant extension and see its logs but when I ran npm run dev the extension was successfully loaded into Raycast, but I did not manage to get any logs in the terminal window. Here are the logs:
><EMAIL_ADDRESS>dev
> ray develop

info  - entry points [src/index.tsx src/covers.tsx src/lights.tsx src/persons.tsx src/sensors.tsx src/binarysensors.tsx src/mediaplayers.tsx src/automations.tsx src/dashboard.tsx src/climate.tsx src/attributes.tsx src/batteries.tsx src/motions.tsx src/vacuums.tsx src/cameras.tsx src/scripts.tsx src/buttons.tsx src/scenes.tsx src/switches.tsx]
log: Must be admin to run 'stream' command
event - stopped development mode

I am wondering if the log: Must be admin to run 'stream' command might be related?
Not sure what other info you need about my setup. Happy to help debug it.

Hey @AuHau – does the same happen when you run npm run dev (instead of ray develop)? If that leads to the same error, you could check whether sudo npm run dev works; however, chances are something is off with the npm setup on your machine in that case since you shouldn't require admin rights. Did you install node and npm through nvm?

I have run npm run dev without a change and also the same with sudo without a change. Yes, I have my Node installed through nvm (Node v16.14.0)

Ok, so in the CLI, we use the system log stream command log under the hood to capture and print the log stream during dev mode. It looks like your login user does not have admin rights? If it's a managed machine, you could ask for getting access to the sys command under /usr/bin/log (there's a sys config file where sudo "exceptions" can be configured).

Yeah that will be most probably the reason. My day-to-day account is a non-admin user because of security reasons. But I don't understand why it did not work when I have used sudo 🤔  I will try to work around this, but it is not my priority atm as I am not really working on any extensions atm. Feel free to close this as it seems like this is my local issue.


Part3

Continuing with part 3 of 4-part tutorial Detecting Changes in Sentinel-1 Imagery
Here is a link to the Colab notebook for part 3.
https://colab.research.google.com/drive/1pw7H845MbmwIKbn4MyIpaHY7gZoS5_4k?usp=sharing

Hi Mort - nice to see the 3rd tutorial!
Unfortunately there are some conflicts. I think the problem stems from not syncing your "master" branch to the google/earthengine-community repo before making your part3 branch.
I wonder if you would try a new PR where you first sync to google/earthengine-community

Go to https://github.com/mortcanty/earthengine-community/
Make sure that the "master" branch is selected
Click the "Pull request" button
On the next screen, press the "try switching the base" link
On the next screen click the green "Create pull request button"
On the next screen - add a title: "Sync to head" - click the green "Create pull request button"
At the bottom of the next screen, press the green "Merge pull request" button, confirm the merge

If that worked, create a new branch for part 3 from the now-synced master branch, upload the files again to the new branch, and submit a PR.
My toolset for resolving conflicts is pretty limited - if the above doesn't work, you might also delete your fork of the google/earthengine-community repo (make sure you have local copies of any changes e.g. edited/new files in any branches) to start fresh.

#245 resolves conflicts - closing this.


Update server-logger to function with multiple securityContext settings

What this PR does:
Modifies the server-logger to use an EmptyVolume to ensure that it doesn't have securityContext restrictions.

Update the CI tests to using a :version instead of :latest so that we don't accidentially test with incorrect version
Deprecate runDockerAsCassandraUser since our current security changes have made it non-functional.

Which issue(s) this PR fixes:
Fixes #553
Fixes #554
Checklist

[x] Changes manually tested
[x] Automated Tests added/updated
[x] Documentation added/updated
[x] CHANGELOG.md updated (not required for documentation PRs)
[x] CLA Signed:  DataStax CLA

That CI error is not relevant, it's really just CI issue with download issue (originally, later the date won't match so it won't work).


Expiration time for UNL to be user configurable

https://github.com/antIggl/xrpl-unl-manager/blob/b9667d3d921ba1b05a5f794e01a679e2a7e48a85/utils.py#L192 is hard coded to 1 year from moment of running. This should be configurable as an argument.

Nice point @alloynetworks.
My initial goal was to create a tool to generate custom UNLs for our testnet, in order to test various connectivity scenarios between validators. Anyway, not an issue, I have already done it.
Expiration date added as argument in all createUNL() function. Defaults to 1 year later.
Additionally, encodeUNL.py  script can be used to set both expiration date and sequence/version of the UNL.
I am closing this issue.


docs: update go/crd docs with semantic version info

ref: https://github.com/akuity/kargo/pull/2521#discussion_r1814010960

We can move this to be inline in the Go/CRD docs.

It turns out it is already mentioned here:
https://github.com/akuity/kargo/blob/1a7ab783e48cd04be0343bf4e1ff689090352fc3/api/v1alpha1/warehouse_types.go#L241-L253
(Although the comment about referring to Image Updater documentation ought to be removed. That is leftover from a time when image selection functionality was borrowed from Image Updater. That is no longer the case.)
This is another spot where semver constraints are mentioned -- this time for commit selection:
https://github.com/akuity/kargo/blob/1a7ab783e48cd04be0343bf4e1ff689090352fc3/api/v1alpha1/warehouse_types.go#L137-L146
Run codegen after updating these comments.

@fykaa you could consider addressing #2880 in tandem with this as they are very closely related.


What should the default value be for attr?

In the latest pull request @williamsbdev found that by default an attributes value is undefined. This in itself might not be totally incorrect but because of how we "protect against" the "" (empty string) when you set the value using attr it behaves strange / incorrectly (as shown below)
test("today if you expect empty string to be a default value you will be sad", function(assert){
    brandon = Person.create({id: 1, firstName: "", lastName: "Williams"});
    assert.equal(undefined, brandon.get("firstName")); // this feels broken
    brandon.set("firstName", "");
    assert.equal(undefined, brandon.get("firstName")); // this also feels broken
    brandon.set("firstName", "baz");
    brandon.set("firstName", "");
    assert.equal("", brandon.get("firstName"));
});

This isn't by accident so let me explain why this occurs today so we can find a way to move forward.
When I first wrote attr I wanted to keep the extra "type" information out of scope. For example - instead of attr("string") or attr("number") I just wanted to write attr(). This design decision let me to believe that using "undefined" as the default value was correct (as I knew nothing of the type and didn't care for sake of the model/ dirty tracking/ rollbacks / etc).
Later I started writing a validation library that would take a dependency on the store / model and attr. The attr was used to determine if the "field" was dirty - if yes I would then fire the validation and show the user what the field required to be "valid".
The UX requirements that I cared about are:

If you started typing into the field (now dirty) I wanted to show the error. If they backspaced out I still wanted to show the error as they clearly started typing so it seemed logical to show them what was expected of them.

If you open a new (empty) form and just hit tab to jump from one field to the next - you wouldn't see any of the validation errors (ie- the field should not be set as dirty / changed)

The 2nd item above was the reason I protected the "attr" from setting "" (empty string) - it turns out that when you go from undefined to empty string the field and model is now dirty (showing the validation error). ** problem for ux
To fix this issue I default all attr values to "" (empty string) so when the user "tabs through" a form it will only "set" each to the already default value of "" (empty string). And because it's the same the field won't be dirty -so it won't fire the validation :)
The downside of this "fix" was that if you start typing (error shows up) - and you then backspace (to nothing) the value of the attr is back to the original /default value "" (empty string) so ... it's no longer dirty (hiding the validation error we said should be showing at this point) **jsbin to show how this is broken
http://jsbin.com/cebuziquji/1/
Solving this requires 2 changes that are worth talking about in this thread

should we make "" (empty string) the default value for attr or should it remain undefined. Thinking about non input model fields (like checkbox / radio button / selectbox) this seems like it might not be correct ... unsure so I'm open to the discussion

if we make "" (empty string) the default - the validation library will need to use another field to determine if it's time to "show errors". Instead of isDirty (at the field level) I think I could just as easily use something like "isPrimed" at the field level to alert the validation component that "yes they've starting using this field so it's safe to show stuff" (though even this computed will need a special "protection" to stop isPrimed from being true when "only" empty string is the value being set on the models attr) - again the user should be able to tab through a form without firing off the world **part of the ux requirement

Whatever we decide I'm planning to leave the 0.9 series as is (using undefined) because this will likely be a breaking api change for people using the library today. The 1.0 (and 1.0 betas) will use this new "default attr value" when we determine what it should be.

After talking w/ @williamsbdev today it's clear that a default value of "undefined" is the best option today. The (small) change required to fix the "setter" of empty string will be available in both the 0.9 and 1.0 series as it's non breaking.
The issue I'll need to solve before merging that is "how to keep the ux in validation" (once this change is in master). I don't currently have an idea on this but I'm planning to devote the week to solving this.

The more I think through this, the more I think it's actually fine the way it is with the caveat that it seems strange to see a unit test that fails to set a value of empty string on a new model.
example:
when you create a new model and you are ready to save it /fire off an xhr. You usually turn the objects properties into json first like so
import Ember from "ember";
import PromiseMixin from "ember-promise/mixins/promise";

export default Ember.Object.extend({
    save: function(model) {
        var hash = {
            data: JSON.stringify({title: model.get("title")})
        };
        return PromiseMixin.xhr("/api/todos", "POST", hash);
    }
});

If your model has a title of empty string it's just the same as not sending it to your backend (as both should fail any validation you have server side). The only thing to be aware of that might cause users pain is if that title property is truly the ONLY value you JSON stringify because "undefined" will return something fun
"{}"

I feel confident this isn't a true issue you run up against in production because I hacked our node modules (on a client project) to change this and not a single test failed (meaning if we expected nothing to hit the server / nothing went with either configuration).
Without this change it's easy to leave the default value as undefined. This allows us to support the scenario where you have a radio button w/ int values or a input with string values (without prescribing the default value be a string/or making the user provide more meta data about the type itself).
Also after searching around the web I couldn't find another way to provide the same great UX you get in validation once we alter the behavior I mentioned above. This along w/ the paragraph above leads me to think we should avoid any changes to this for the moment.
Thoughts?

When I originally found this, it was only in a unit test. At that point, we had been using this library in our production app for quite some time without issue. I do not feel this is worth addressing at this point as you said if it breaks some desired UX. I have not seen issues related to AJAX requests but will keep this mind in case I do run into trouble.
Thanks!


Failed to initialize DSP Pipeline!

Hi!
I have managed to change your project to use a custom analogue microphone. It works fine with various sample rates from 16000 up to 100,000 samples per second which is what I need.
However when I change the FFT_SIZE from 256 to something greater such as 512 or 1024 the program stops at "dsp_pipeline.init()".
if (arm_rfft_init_q15(&_S_q15, _fft_size, 0, 1) != ARM_MATH_SUCCESS) {
        return 0;
    }

However if I use the arduino sketch provided in your article https://medium.com/towards-data-science/fixed-point-dsp-for-data-scientists-d773a4271f7f#2960 it work well with 100000 samples per second at window size of 1024. Weird.
Could you pls help me with any idea?

Found the problem: the arm_rfft_init_q15 instance is initialized with an fft size of 256.
In CMakeLists.txt can be found a line
set(RFFT_Q15_256 ON)
Change the value to whatever it is needed, for example for a fft window size of 1024:
set(RFFT_Q15_1024 ON)


success: false Error

Hi
Sir i am getting  success: false, error for every video from past 2 days
May i know How i can solve the issue
ThankYou

Hi Sir i am getting success: false, error for every video from past 2 days May i know How i can solve the issue
ThankYou

bcz response from fdownloader.net return a encrypted result. you can check in DevTools on tab network after you click download


More details about Inference time

Hi ,I see you believe that your algorithm can work at real time speeds ,based on your observations can you predict how much time this will take to stitch 4 ,1280x720 images into one Panorama , I plan to use RTX3070 GPU and hope to use this method for video stitching

In our experiments, it usually takes less than 30s per iteration to merge the pre-processed 9000x4000 images when using a much older GPU. If you use RTX3070 to merge 1280x720 images, I think it should take less than 1s per iteration because your image is much smaller.
Then, the execution time depends on how many iterations are needed. If no more than 2 images overlap in the same area, you can merge all 4 images in one iteration (see ./Test_data_4Input for example). If three or more images overlap in the same area, you need to merge them iteratively (see ./Test_data for example); in this case, you might need up to 3 iterations to merge all 4 images.
Besides, you need to consider the time of pre-processing. This time depends on what parkage/algorthim you choose.

If all cameras are fixed, is it possible to save a "stitched" configuration file and then only perform "inference" in real-time. If the cameras is moved relative to each other will the image be stitched wrong, and a new "stitched" configuration-file is required to be generated for the new extrinsics (camera poses).

If all cameras are fixed, I think it's possible to save a configuration file for all position-specific operations, such as the first pre-processing stage (coarse registration). In the second image-blending stage, the global blending coefficient is calculated merely based on position, which could be saved as configuration. However, the optical flow is calculated based on photo pixels, which have to be computed every time.


GDScript: Add @export_custom annotation

Allows setting any arbitrary hint and hint string. Useful for more complex hints or potential future hints not available as a dedicated annotation.
Closes #61325
Supersedes #65935

Looks good. But, it seems to me that {substitutions} in Godot are more common than %SUBSTITUTIONS%. The property hint syntax does not use either % or {}.

I'll leave this on hold for now since it won't be merged for 4.0. I'm open to suggestions about the substitution syntax and what values are needed.

I do prefer {type_value} or {TYPE_VALUE}, but I'm more curious about example values for each substitution and how they might be used in the hint string.

At first I was thinking on some array hints that require the element type on the hint string. But later I reconsidered as that might not really come from the variable type (unless there's a substitution for the element type).
I'll probably remove the substitutions once I revisit this. This also comes because IINM the % formatting operator is not reduced at compile time and thus cannot be used in annotations, so maybe solving that is a better option.

 As this was possible in 3.x and not in 4.x i thought it was a choice to reduce what was possible to do with exports. So I had made my own solution that i have been maintaining. I cleaned it a bit and published it here.
The major difference between what i did and this ¨R is that instead of a new export annotation i added a complementary annotation that is added between any export annotation and its variable and that enables the user to modify the type hint and the hint string.

Postponed to 4.3 due to feature freeze.

I rebased this and removed the template substitutions. If they're needed we can find a good way to add them later.

Should we allow specifying usage as well? Everything else from property's metadata can be defined by other means (name, type, class), but usage cannot.

I guess it does make sense to specify the usage too.

I think it's a nice addition. I also support the idea to allow specifying the usage flags.

Note that users may accidentally remove PROPERTY_USAGE_SCRIPT_VARIABLE, PROPERTY_USAGE_NIL_IS_VARIANT, PROPERTY_USAGE_CLASS_IS_ENUM, and other flags. Of course, users can already do this in _get_property_list() for "virtual" properties or in _validate_property() for existing variables. But the question arises: should annotation flags be added to existing ones (|=) or should they overwrite the initial ones (=)?

@dalexeev I think they should behave exactly as properties added dynamically with _get_property_list. I would not want any hidden behavior. As far as footguns go, this is not a severe problem and it can be explained in the docs for the annotation.

@vnen Do you plan to work on this soon? 🙃

Added the usage flags.

Updated to apply the suggestions and fix conflicts.

Thanks!

Is there any reason not to allow overriding class_name? It doesn't have a ton of use cases, but there are some, eg. PROPERTY_USAGE_ARRAY (though since the script has to be a tool for that regardless, I guess that _validate_property takes care of this...?)

For the same reason as type. We do have a few exceptions when class_name is used due to the small number of fields in the PropertyInfo structure, but in most cases you should not overwrite type and class_name.


Delete sub-01_ses-01_task-balloonanalogrisktask_run-01_events.tsv

While I updated FullExample_events.tsv ,I forgot to delete this file in the func folder.
This file is no longer required in the repository.

thank you!


Profile doesn't load in pwsh6 (but does in 5.1)

I have pwsh6 installed alongside Windows Powershell 5.1 that comes installed with Win10.
I have a profile, profile.ps1, in my Documents\WindowsPowerShell directory.
That profile isn't loading in pwsh6.
That led me to look at about_profile, to see if the profile names or some other behavior changed.
And the text of that statement in pwsh6, unlike 5.1, is almost unreadable.
The, I think, applicable portion:
  ---------------------------------------------------------------------------------------------------------------------------------
  Description                  Path
  ---------------------------- ----------------------------------------------------------------------------------------------------
  Current user, Current Host   $Home\\[My ]Documents\\WindowsPowerShell | | | \\Profile.ps1 | |Current User, All Hosts |$Home\[My
                               ]Documents\Profile.ps1

  All Users, Current Host      $PsHome\Microsoft.PowerShell_profile.ps1 | |All Users, All Hosts |$PsHome.ps1
  ---------------------------------------------------------------------------------------------------------------------------------

I can't make heads or tails of that. There are double-backslashes where there don't need to be, there are two and three consecutive pipe symbols for unknown reasons, there are names that don't make any sense, e.g. \Profile.ps1, $PsHome.ps1 ($PsHome is a directory, so $PsHome.ps1 is nonsense), there are what appear to be descriptions embedded in the middle of a line (| |Current User, All Hosts).
The end result is I can't tell if this is a real problem, because I can't tell from that documentation what the valid profile locations and names are. If they are the same as 5.1, then this would appear to be a real problem; the profile loads correctly in 5.1 and does not in 6.0.2.
Also, if I dot source the file in pwsh6, it loads without error. So the not loading doesn't appear to be because of a problem with the profile itself.
Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.2
PSEdition                      Core
GitCommitId                    v6.0.2
OS                             Microsoft Windows 10.0.16299
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Profiles load from ..Documents\PowerShell\Microsoft.PowerShell_Profile.ps1 (you can just use $profile to show the path in the console) instead of WindowsPowerShell path.  Looks like the doc needs to be updated.  If you want the same profile loaded in both, you can create a symlink.  The markdown that you see will look a bit strange as backslashes need to be escaped, but the rendered HTML should read fine: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_profiles?view=powershell-6.
Can you open an issue in the doc repo to get the documentation corrected?  https://github.com/PowerShell/PowerShell-Docs/issues

What I posted is what actually displayed on the screen. There should be no double-underscores on the screen. (Oh, you mean what's displayed on the screen is the Markdown because something happened to keep it from rendering in the help text. That makes sense.)
Yes, I will.


Add a third option which replaces newlines by spaces when pasting content with multiple lines

Description of the new feature/enhancement
When pasting in the Terminal a command line that ends with a line break, my options are either to paste and run the command, or abort the operation. Most of the times, I actually want to paste while trimming the trailing line break, such that I can edit the command I am pasting.

Proposed technical implementation details (optional)
When pasting, a new button would appear in the confirmation dialog, that would allow to paste while trimming line breaks (if the string contains line breaks that are not trimmed, replace them by a space?)

Adding a third button might require some refactoring, because the dialog is only meant to have two buttons:
https://github.com/microsoft/terminal/blob/f26c246c7c081c0222dd8ebd4738f6a0d574f66c/src/cascadia/TerminalApp/TerminalPage.cpp#L2145-L2165

I don't hate this idea. But with bracketed paste feature in 1.7, this does not really bother me when I'm using bash/zsh. The shell will not execute the command and let you edit it. Sadly powershell does not support bracketed paste, though.

I don't think this is a terrible idea. Looks like the ContentDialog supports 3 buttons, it would just take a bit of refactoring.

I've just taken a crack at this and I think I've got it working without any substantial refactoring at all. I'm still pretty intimidated by C++ though, so I'm not sure if I'm doing anything stupid/careless, but I'm happy to submit this in a PR if anyone wants to take a look.

Could you simply add an option to terminal, the values can be: 1. trim trailing newline, 2. don't trim, 3, interactive dialog

Merging some discussion from #10502

I do think we should be more intelligent here... text that is a single line and ends in a newline with no further content should just strip it by default, I think. I am opposed to adding a button to every paste dialog that folks will have to process when they paste. Perhaps there's a middle ground!

Who's really wanting to paste all these lines with spaces between them (instead of newlines) here?

After thinking about it myself for a bit, I am inclined to agree with you. My PR on this is pretty stale anyway because we hadn't decided what the button text should be and then I think I just forgot about it. But yes, I am struggling to think of a situation where you would actually want to strip breaks from the middle of the paste. I suppose maybe if you copied from some poorly formatted source (PDFs, for example, move in mysterious ways) wherein the command was supposed to be one line but for some reason contains line breaks? Feels like a stretch, though.
Anecdotally, this warning only shows up for me because either I am indeed pasting multiple commands or I just accidentally copied the wrong thing.

trimSingleTrailingNewline (default:true) for "if there's just one newline at the end then trim that", so folks could set this to false to be able to paste a command in one go?

Automatically trimming the trailing new line makes sense to me, but I wonder does it really matter if it's just one? As long as there's no other characters in between, multiple line breaks at the end of the string seems practically equivalent to a single one to me.

Single trailing new line stripping sounds good to me as well.

Huge thanks @lovef, @zadjii-msft and all the contributors!
I was pulling my hair out every time I was trying to paste a command into a terminal. Can't wait for the next release!


feat(component-index): 1555-component-index-filter-ui-functionality

Closes #1555
Updates
This is the final step for a soft release on the component filter. This PR should have the following functionality:

[ ] Filter by different categories

[ ] Filter and sort different categories

[ ] Match the following filter

@andreancardona just saw the review re-request, still had those comments from above but beside that should be good 👍

Side-note, do we want to add it to the side nav with this PR? @aagonzales @andreancardona ?

The search filter styles are different than we have on the icon search page. @aagonzales should we try and normalize them? Our search pattern shows dropdowns inline.

@vpicone Its purposefully different. The icons dropdown is a sub category of search. In the index sort is a different function and didn't make sense to be inline with search. It also throws off page alignment. The design team talked it through awhile ago and Mike was also involved.

@aagonzales okay thanks for clarifying, let me know if we'd rather have the index use the darker border.


fix: Add explicit ON DELETE CASCADE for dashboard_roles

SUMMARY
Fixes https://github.com/apache/superset/issues/25305. See https://github.com/apache/superset/pull/24628 for more details.
I'm somewhat perplexes as to why the test_cannot_get_draft_dashboard_with_roles_by_uuid test didn't surface said issue, i.e., deleting a dashboard with a role associated with it. Note that the insert_dashboard method does flush (and commit) to the dashboard.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS
CI.
ADDITIONAL INFORMATION

[x] Has associated issue: https://github.com/apache/superset/issues/25305
[ ] Required feature flags:
[ ] Changes UI
[x] Includes DB Migration (follow approval process in SIP-59)

[x] Migration is atomic, supports rollback & is backwards-compatible
[x] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

This caused migration failure in 3.0.0rc3.
The solution should be
DashboardRoles = Table(
    "dashboard_roles",
    metadata,
    Column("id", Integer, primary_key=True),
    Column(
        "dashboard_id",
        Integer,
        ForeignKey("dashboards.id", ondelete="CASCADE"),
        nullable=False,
    ),
    Column(
        "role_id",
        Integer,
        ForeignKey("ab_role.id", ondelete="CASCADE"),
        nullable=False,
    ),
)

should delete ondelete cascade on the foreign key, not the entire column

You're right @raghulprashath! I'll submit a fix.


feat: App token refreshing

This PR implements app token refreshing!  Thank you for your patience with the previous refactoring PRs that prepared for this one.

As part of has_calls_remaining, the amount of time left until estimated token expiry is checked, and tokens are refreshed if expiry is close.
A new config option expiry_time_buffer is added, controlling how many minutes before expiry the app token will be refreshed.  This parallels how rate_limit_buffer is used to ensure we don't push tokens all the way to their limits.

👋 I ran some large extractions over the weekend using this PR's SHA and a single app key.
The good news is that it ran smoothly for several hours at a time without any authenticator related failure. The longest job I ran took about 8.5 hours, and I can see the GitHub app token refresh succeeded. logging at regular intervals.
One slightly confusing find is that whenever the expiry time approached a refresh would happen, and then another refresh would happen say 3-6 minutes later.  Log excerpt demonstrating it:
2024-08-10 03:58:53,256 | INFO     | tap-github           | Tap will run with 1 auth tokens
2024-08-10 04:48:55,891 | INFO     | tap-github           | GitHub app token refresh succeeded.
2024-08-10 04:53:55,361 | INFO     | tap-github           | GitHub app token refresh succeeded.
2024-08-10 05:38:55,944 | INFO     | tap-github           | GitHub app token refresh succeeded.
2024-08-10 05:44:31,833 | INFO     | tap-github           | GitHub app token refresh succeeded.
2024-08-10 06:28:56,078 | INFO     | tap-github           | GitHub app token refresh succeeded.
2024-08-10 06:34:59,825 | INFO     | tap-github           | GitHub app token refresh succeeded.

I was extracting the issues stream, and when I look at where GitHubTokenAuthenticator is initialized it looks like maybe the parent stream (repos) and child stream (issues) are each constructing and maintaining a GitHubTokenAuthenticator object, meaning there would be two installation access tokens at any given time and each would need to be updated periodically.    As long as we understand why it's refreshing twice and believe it isn't due to a bug, I don't think this is a problem - multiple installation access tokens can exist for the same app and will just cumulatively contribute to the app's rate limit.

If it helps in anyway, we've been using app tokens with this method without issues since last year, but i haven't refactored the code to address Meltano's feedback: https://github.com/MeltanoLabs/tap-github/pull/201

Does that match your mental model @edgarrmondragon?

That makes sense to me. We could always make it singleton in the future, but I don't think it causes issues at the moment?

We could always make it singleton in the future, but I don't think it causes issues at the moment?

Agreed. 👍

Thanks @TrishGillett, this is a monumental improvement!


Mark AZURE_CONFIG_DIR as code

Docs Build status updates of commit eb976c0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/use-cli-effectively.md
:white_check_mark:Succeeded
View

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


Bayesian classifier sample size is far too small

Linguist is using a bayesian classifier to detect languages. However, the sample data provided to it is far too small. According to `wc -l samples// there are just 309505 lines of sample code for about 220 "languages", making for an average of 1400 lines of sample code for each language.
I am surprised that despite this, linguist manages to work reasonably well -- my guess is that this is mostly due to the fact that data is pre-binned based on file extensions (fair enough). But as soon as more than one language uses the same extension, detection rates break down, as the tons of reports on Objective C vs C++ vs C show.
Which is not surprising -- the current approach linguist takes is akin to showing a spam filter half a dozen spam mails, no regular mails, and then expecting it to work well.
So, if linguist wants to keep using a Bayesian filter, it seems to me that the sample size should be enlarged substantially.
An alternative would be to use more hand-crafted heuristics, as has been suggested by many people on many issue reports and pull requests, but that has its drawbacks, too -- on the one hand, heuristics are hard to maintain, and on the other, they are surprisingly hard to get right, too -- most people are pretty bad at doing it. This is indeed something were Bayesian classifiers usually outperform humans. But only if fed with enough sample data...

We're planning on working on this extensively over the coming months https://github.com/github/gsoc#linguist so closing this out. Thanks for your thoughts @fingolfin.


Development setup is very hard.   to run flutter  apps  becuse of  android-studio  incudes   emulator .  GenyMotion  Given emulator separate run  emulator for developer  it not easy  ways to do  in flutter  with virtual device geny-motion. not given  tutorials in flutter site.   why not we can write  in sublime or vscode  editor  fluttter  program  and  run virtual emulator. without android-studio.    why  should i download  amdroid-studo  heavy file .. it not able  run properly in linux  ubuto system ...  I am gettin build issue

android-studio bundle editor . it is huge file .. it not portable  in all device linux ubutu. i
i am getting issue build  flutter app in  vitual device geny motion ,  i hate android-studio included emualtor  very very heavy file while donloading edutor  its take full  night and days

Questions like these are better suited for Q&A sites like StackOverflow or on one of the flutter community sites at https://flutter.dev/community


"Calvini", "Bâscenii de Jos", "Bâscenii de Sus", "Frăsinet" and "Olari" are listed in the drop-down menu

Description:
"Calvini", "Bâscenii de Jos", "Bâscenii de Sus", "Frăsinet" and "Olari" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Calvini" in the search bar.

Expected results
The location is listed in the drop-down menu as "Calvini, Buzău(Calvini)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Bâscenii de Jos" in the search bar.

Expected results
The location is listed in the drop-down menu as "Bâscenii de Jos, Buzău(Calvini)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Bâscenii de Sus" in the search bar.

Expected results
The location is listed in the drop-down menu as "Bâscenii de Sus, Buzău(Calvini)".

Step 7
Type "Frăsinet" in the search bar.

Expected results
The location is listed in the drop-down menu as "Frăsinet, Buzău(Calvini)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Type "Olari" in the search bar.

Expected results
The location is listed in the drop-down menu as "Olari, Buzău(Calvini)".


Fix for selected year in highlight threads mobile (curric visualiser)

Description
Fix for selected year in highlight threads mobile (curric visualiser)
Issue(s)
Fixes CUR-1033
How to test

Go to https://deploy-preview-2967--oak-web-application.netlify.thenational.academy
Navigate to mobile filters, check counts are correct

:tada: This PR is included in version 1.621.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


normalized vector dot product

Hi! I noticed that in this paper you directly multiply the embedding vectors without normalizing them, as many of the recent self-supervised learning paper has done. Is there a specific reason for not doing the normalization? Thanks!

Hi,
We have not seen any improvements when performing cosine similarity with temperature instead of a simple dot product.

Thank you!


RigidBody will not go to sleep anymore if 'set_can_sleep()' is used

Godot version:
Windows 10 x64 / NVIDIA GeForce GTX 1060 6GB / Intel Core i7 4790K
OS/device including version:
3.2 dev
Issue description:
If I $RigidBody.set_can_sleep(false) once, even after I $RigidBody.set_can_sleep(true), the $RigidBody.is_sleeping() will always show false (RigidBody will not sleep anymore).

Steps to reproduce:

Open the attached project
Press F5
Look at the bottom left status (Is sleeping will be true automatically after some seconds)
Left click and hold anywhere (both statuses will be false)
Release mouse button (is_sleeping will not be true anymore)

Minimal reproduction project:
sleep.zip

In the past year or so of using the engine, I've never had any luck with the sleep functionality, at least for 2D.  It seems very rare and random if anything ever comes to rest or can be forced into rest.  I wonder if this flagging issue is part of the reason why.

This could create a HUGE PERFORMANCE PROBLEM, because if there are hundreds of RigidBodies that have been changed by set_can_sleep (), their physics will be processed FOREVER, even if they are still.
This correction should be a PRIORITY.


Properly serialize unicode emojis in Emoji#mention

Summary
Allow Emoji#mention to be used for unicode emojis.

Added

Emoji#mention will return #name if #id is nil, where it would previously return <:name:>
Tests for serialization of unicode emojis via mention

This was merged via shardlab/discordrb@0a32817190e0ce649e59d44722aa4114be0c2a25 in the new repo and released in v3.4.0 and can be closed.


Remove spring dependency from RulesPolicy

Convert RulesPolicy to Kotlin data class and remove dependency from spring annotations.

Replace Array with List in RulesPolicy
Remove equals and hashCode functions from RulesPolicy
Fix unit tests
Add ConversionService to support props => List<String> conversion by spring
Fix integration test assertions to provide a proper assertion error

Fixes: #560

:+1:

Codecov Report

Merging #1101 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master   #1101      +/-   ##
===========================================
+ Coverage     85.18%   85.2%   +0.02%
- Complexity     1114    1118       +4
===========================================
  Files           176     178       +2
  Lines          2814    2818       +4
  Branches        467     467
===========================================
+ Hits           2397    2401       +4
  Misses          202     202
  Partials        215     215

Impacted Files
Coverage Δ
Complexity Δ

...src/main/java/de/zalando/zally/rule/RulesPolicy.kt
100% <100%> (ø)
4 <1> (ø)
:arrow_down:

...do/zally/configuration/RulesPolicyConfiguration.kt
100% <100%> (ø)
2 <2> (?)

...ly/configuration/ConversionServiceConfiguration.kt
100% <100%> (ø)
2 <2> (?)

Continue to review full report at Codecov.

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

:+1:

@tkrop do you want to review it or I can merge it?


[Radio] Value is not set when the button are clicked

focus-components : v0.6.2
The onChange is fired but the value isn't updated.

That's normal.
When you define an onChange function, you have to handle the state of the component.
Please refer to the source code:
https://github.com/KleeGroup/focus-components/blob/develop/src/common/select/checkbox/index.js#L61
 /**
     * Handle a change of value.
     * @param  {[type]} key       the key
     * @param  {[type]} newStatus the new status
     */
    _handleCheckboxChange(key, newStatus) {
        if(this.props.onChange) {
            this.props.onChange(key, newStatus);
            return;
        }
        const selectedValues = this.state.selectedValues;
        if(newStatus) {
            selectedValues.push(key);
        } else {
            pull(selectedValues, key);
        }
        this.setState({value: selectedValues});
    },

Nothing happen when I remove the onChange property

_handleCheckboxChange(key, newStatus) is never called
_onInputChange is called instead

The problem is the onChange function  is given by the field for to the select radio


Strangely, "source <(...)" in .envrc doesn't work with my Bash v3.2.57

When I go into the bucc project for the first time, then direnv allow doesn't modify the PATHenvironment variable:
$ git clone https://github.com/starkandwayne/bucc.git
...
$ cd bucc/
$ direnv allow
direnv: loading .envrc

Whereas if I just put eval "$(./bin/bucc env)" in .envrc then it works:
$ echo 'eval "$(./bin/bucc env)"' > .envrc
$ direnv allow
direnv: loading .envrc
direnv: export ~PATH

I didn't test this with the ${vars_store} file being present yet.
But anyway, maybe you should just simplify your .envrc and just leave  eval "$(./bin/bucc env)" for both bash and zsh, don't you think?
Cheers,
/Benjamin

Hi there,
I see the same issue (macOS Sierra 10.12.6, Terminal 2.7.3, Bash 3.2.57)
~/projects$ cd bucc/
direnv: loading .envrc
~/projects/bucc [master]$ echo $BOSH_ENVIRONMENT

~/projects/bucc [master]$

If I switch to eval "$(./bin/bucc env)" for bash in .envrc it exports all the ENV vars, but all of BOSH_CA_CERT is on a single line, which is causing issues.
~/projects/bucc [master]$ echo $BOSH_ENVIRONMENT
<IP_ADDRESS>
~/projects/bucc [master]$ echo $BOSH_CA_CERT
-----BEGIN CERTIFICATE----- MIIDEzCCAfugAwIBAgIQBl9j942cZLLl34bGT9yJcTANBgkqhkiG9w0BAQsFADAz MQwwCgYDVQQGEwNVU0ExFjAUBgNVBAoTDUNsb3VkIEZvdW5kcnkxCzAJBgNVBAMT AmNhMB4XDTE3MDgzMDA5MDM0N1oXDTE4MDgzMDA5MDM0N1owMzEMMAoGA1UEBhMD VVNBMRYwFAYDVQQKEw1DbG91ZCBGb3VuZHJ5MQswCQYDVQQDEwJjYTCCASIwDQYJ KoZIhvcNAQEBBQADggEPADCCAQoCggEBALq0aVrWma1rye8YYoAE60KZsDuaZzoH 7caVtUAO2rt9Q0WcwrDMgztQckWo9J7Ghqwgd6rno4O+j8um/r84sjY5SwqkMp6L h8xXFy9SdboY3UIPsjaohGMUNNh9wYDQrVBsDBdXmDT0ymJWNKa+Wp7nw4bKAM1L kmPSWWedvwNMEOILhePJYDqiYnihMgEhjcRqcYWmEwno8aRl3W/6wcCFhv1fiuL+ iTZyAyHIkGgTg9xVMZ3IoaValP9yUAAT34jcqb/aexM16UVdty5g2xCyB8dQqsoc qFLJk7qGoZj2RR55rik0s3+wuL/yXZ4lYbtukZSMRq5h6PNbPKFLb9MCAwEAAaMj MCEwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQEL BQADggEBAIo/5HDcdnjKCQ8M+Y+wX8Q+mLhzdiz9mCOsPzpPJhAbZ6eHIelFpqRk r2sM4oVERYXYNU/T1LMtxqqIFPAzep2/COoot40XTF87rcvX9pda5SmMYZ0fGy/d /hWHK5fzMjYxdxEs1EMoXZBOBOCU3RsQ+aehls89jaUBRQiELUHWyaY+LnfObH/t aYUA4kUe+8553suxWOH31hwqX+a5nGDwZbKSUJmMMYaTJ8XdIAaM8ZmORdFAtA2q k66Ya/Grjd4a/GQ3zHCw2M7OtZl+N+NAL9UpxoCo/CoEWGH0JzC69msrmTJNJiNs KM/F0gCvhrOM9hTHf4tOs4Jrwtz14zw= -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- MIIDIzCCAgugAwIBAgIQeWDvnbg2opJdajmjpxIyZDANBgkqhkiG9w0BAQsFADA7 MQwwCgYDVQQGEwNVU0ExFjAUBgNVBAoTDUNsb3VkIEZvdW5kcnkxEzARBgNVBAMT CkNyZWRIdWIgQ0EwHhcNMTcwODMwMDkwMzQ5WhcNMTgwODMwMDkwMzQ5WjA7MQww CgYDVQQGEwNVU0ExFjAUBgNVBAoTDUNsb3VkIEZvdW5kcnkxEzARBgNVBAMTCkNy ZWRIdWIgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgcwzvm0KM z2Ncgaf8PmoNM4uR+YbP6SKSqgZAsWVWGg5J+uyBrwMbo3JKhyphQDubqJn1D6Tn HM0ms4hJ1x4IDA/0ftvkOfXwJ3THL4BMcprtYQ/NjGZo47E4ztw+a1xLoSsDr04Y YXUsNunSoxcCSmg489sYLPH5dDNzGXFKYPAuCl5ltI/T2tfOqOVBoPlPmPD5ZQX1 hvB3YzLQ4V0BiWLT+r0yVkMc22ubxxtKl+hJ+vffRR7+OjK6nx5/czLY5of/Q+V7 z/iPR7esC8ouj8fUUdqNAA4Ty/38YTekcSw8S9a/l5URAC9ZKAAm5S/r6JgC7EKB BMvssvfxP77TAgMBAAGjIzAhMA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTAD AQH/MA0GCSqGSIb3DQEBCwUAA4IBAQAhpFlTiTMSUlGFimz6DSWQVFWdAQlMCoVZ qzSghlkylobGWXAETXwILxYzlDzGD3McMQyCOGwD8HPwsqGx3XQlx+qeUlQ9xmUt jCRmTYe8wTD3Ken5NWSxyplqR3noJEvnWNJ3dJLRWRf9+UyrbZ3k6f5KjCVFsskE SEJd8ygwaIU1huhfUCTgO6ZWWWqX/k48U9QfC4MEHwRXm4Yj+hrN8sG/Pxc5m1UJ qIYS2iWe5MEuflA+ZZfqMj2Z7z6qaGOl6h3Dc8Hd9iLog0DvOudiwduW2Ls2QCK6 kgXPYLtFIVFczsAcb4mrbyJ325f8Kjj3SEvzWEqQ2U+lVUkMOruH -----END CERTIFICATE-----

So far my workaround is to dump output of ./bin/bucc env into a file and source it.

Process substitution is a bash 4.X addition.

Unrelated: OMG I love process substitution.

From: Norman Abramovitz<EMAIL_ADDRESS>Sent: Friday, November 10, 2017 10:23:20 AM
To: starkandwayne/bucc
Cc: Subscribed
Subject: Re: [starkandwayne/bucc] Strangely, "source <(...)" in .envrc doesn't work with my Bash v3.2.57 (#52)
Process substitution is a bash 4.X addition.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/starkandwayne/bucc/issues/52#issuecomment-343335631, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAAAbMz_o6eBlcqGaGz2Yc82Ni5iNZAGks5s05d4gaJpZM4QY0SB.

Yeah, I love process substitution too and I think we have this in Bash 3, for example
$ wc <(cat /usr/share/dict/words)
  235886<PHONE_NUMBER>109 /dev/fd/63

I've read something that when you do source <() it happens in subprocess and once it's done you lose all these exports.
Anyway, thanks for the work on making Bosh and friends easier to start with, I'll keep to my workaround for now.

@krasio @bgandon
Can one of you try the following code in your .envrc file and let me know if it solves the issue?
Thanks
case $SHELL in
*zsh)
eval "$(./bin/bucc env)"
;;
*bash)
source /dev/stdin <<<"$(./bin/bucc env)"
esac

Well, this seems even more complicated and I'm sorry, I didn't get the reason yet...
For which reason should we not do as eval "$(./bin/bucc env)" with Bash? In my case it works.

I ran into issues where eval would fail with multiline input and needing to do escaping all over the place where this approach does not.

Ok, source /dev/stdin <<<"$(./bin/bucc env)" is very slow, but it works for me.

thanks.   I know the original code (source using process substitution) seemed slow as well.   At least I know I have a valid working case to compare to.

maybe it's time to add tests for this, because I don't know what we will break when we change this..

We can always to it the long way which is probably clearer to everyone.   The both previous syntax styles just hides the temporary file.
bucc env >| tempfile
source tempfile
rm tempfile

I realise how late this is answer is, sorry for that, but looks like source /dev/stdin <<<"$(./bin/bucc env)" is working fine for me.


Kafka pubsub inbound retries endlessly if dead letter topic not configured

Expected Behavior
When using a specified retry policy on inbound pubsub component, the policy's maxRetries should be honored and the sidecar should stop retrying after that many times, even if the subscription doesn't specify a dead letter topic.
Actual Behavior
The sidecar ignores maxRetries and retries indefinitely when the subscription doesn't specify a dead letter topic. It does honor the specified policy (constant) and duration (3s) settings.
When the subscription does specify a dead letter topic, the sidecar honors maxRetries and publishes to the DLT after that many failed retries.
Steps to Reproduce the Problem
Using dapr v1.9.0 on MacOS BigSur 11.6.8:

Enable resiliency preview feature
Run dapr in self-hosted mode with debug logging with the following components
Publish a message to the topic being subscribed to
Watch dapr endlessly call the subscribed endpoint, whether it returns 200 with body {"status":"RETRY"} or returns 500

resiliency.yaml:
apiVersion: dapr.io/v1alpha1
kind: Resiliency
metadata:
  name: myresiliency
spec:
  # policies is where timeouts, retries and circuit breaker policies are defined.
  # each is given a name so they can be referred to from the targets section in the resiliency spec.
  policies:
    # retries are named templates for retry configurations and are instantiated for life of the operation.
    retries:
      pubsubRetry:
        policy: constant
        duration: 3s
        maxRetries: 2

  # targets are what named policies are applied to. Dapr supports 3 target types - apps, components and actors
  targets:
    components:
      dev-aws-heart-rate-pubsub: # any component name -- happens to be a pubsub broker here
        inbound:
          retry: pubsubRetry

pubsub.yaml:
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: dev-aws-heart-rate-pubsub
spec:
  type: pubsub.kafka
  version: v1
  metadata:
    - name: brokers
      value: "ingress:9092"
    - name: disableTls
      value: true
    - name: consumerGroup
      value: "dapr-heart-rate"
    - name: authType
      value: "none"
    - name: maxMessageBytes
      value: 100000

sub.yaml:
apiVersion: dapr.io/v1alpha1
kind: Subscription
metadata:
  name: kafka-dev-aws-heart-rate-readings
spec:
  topic: livongo.private.service.demo.template.heartRate.readings2
  route: /dev/dapr/kafka/consume
  pubsubname: dev-aws-heart-rate-pubsub
  metadata:
    rawPayload: "true"
    consumeRetryEnabled: false # (or true, same behavior)

Relevant dapr log msgs:
DEBU[0000] Found 1 resiliency configurations.            app_id=myapp instance=ip-192-168-4-31.ec2.internal scope=dapr.runtime type=log ver=1.9.0
INFO[0000] Loading Resiliency configuration: myresiliency  app_id=myapp instance=ip-192-168-4-31.ec2.internal scope=dapr.runtime type=log ver=1.9.0
DEBU[0000] Resiliency configuration (myresiliency): &{TypeMeta:{Kind:Resiliency APIVersion:dapr.io/v1alpha1} ObjectMeta:{Name:myresiliency GenerateName: Namespace: SelfLink: UID: ResourceVersion: Generation:0 CreationTimestamp:0001-01-01 00:00:00 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[] OwnerReferences:[] Finalizers:[] ClusterName: ManagedFields:[]} Spec:{Policies:{Timeouts:map[] Retries:map[pubsubRetry:{Policy:constant Duration:3s MaxInterval: MaxRetries:2}] CircuitBreakers:map[]} Targets:{Apps:map[] Actors:map[] Components:map[dev-aws-heart-rate-pubsub:{Inbound:{Timeout: Retry:pubsubRetry CircuitBreaker:} Outbound:{Timeout: Retry: CircuitBreaker:}}]}} Scopes:[]}  app_id=myapp instance=ip-192-168-4-31.ec2.internal scope=dapr.runtime type=log ver=1.9.0
INFO[0000] Resiliency configuration loaded.              app_id=myapp instance=ip-192-168-4-31.ec2.internal scope=dapr.runtime type=log ver=1.9.0
...
DEBU[0021] Found Component Inbound Policy for component dev-aws-heart-rate-pubsub: {Inbound:{Timeout: Retry:pubsubRetry CircuitBreaker:} Outbound:{Timeout: Retry: CircuitBreaker:}}  app_id=myapp instance=ip-192-168-4-31.ec2.internal scope=dapr.runtime type=log ver=1.9.0
...
== APP == 2022-10-25 18:32:43.147 9ba92019-740c-4546-a477-144ca9964aec - <IP_ADDRESS> "POST /dev/dapr/kafka/consume HTTP/1.1" 500 null "-" "fasthttp" 126 "-" <IP_ADDRESS>
INFO[0027] Error processing operation component[dev-aws-heart-rate-pubsub] input. Retrying...  app_id=myapp instance=ip-192-168-4-31.ec2.internal scope=dapr.runtime type=log ver=1.9.0
...

Release Note
RELEASE NOTE: FIX Kafka pubsub inbound maxRetries honored

/keep-alive

I ma facing the same issue. Any help on this would be appreciated


[SPARK-23217][ML] Add cosine distance measure to ClusteringEvaluator

What changes were proposed in this pull request?
The PR provided an implementation of ClusteringEvaluator using the cosine distance measure.
This allows to evaluate clustering results created using the cosine distance, introduced in SPARK-22119.
In the corresponding JIRA, there is a design document for the algorithm implemented here.
How was this patch tested?
Added UT which compares the result to the one provided by python sklearn.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/666/
Test PASSed.

Test build #87161 has started for PR 20396 at commit 39d3695.

Test build #87161 has finished for PR 20396 at commit 39d3695.

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

Merged build finished. Test PASSed.

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

kindly ping @jkbradley @MLnick @viirya

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/856/
Test PASSed.

Test build #87394 has finished for PR 20396 at commit ab34243.

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

Merged build finished. Test PASSed.

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

Merged to master

@srowen sorry, this needs also to add the parameter to the python API; given our discussion on JIRA, what should I do? Create a follow-up PR or a new ticket on JIRA?
Thanks.

I think you can just add a follow-up


w

node -v
10.15.3
npm -v
6.9.0

Please fill out the issue template if you want us to be able to help you.


1.7.2 release assets are SNAPSHOT

The release assets filename end with SNAPSHOT.tar.gz.  It may need update without SNAPSHOT as 1.7.1.

Hi @yjqg6666
Thanks for reporting this.
The release has been updated accordingly.
Thanks!


custom looking scrollbar

please integrate this into backlog:
https://github.serafin.io/vuebar/

check this out:
https://github.com/KingSora/OverlayScrollbars
there is also vue wrapper.


Could not load dynamic library 'libcusolver.so.10' with official TF 2.4, even though it's installed

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04 LTS
TensorFlow installed from (source or binary): official 2.4 binary, installed via Python pip
TensorFlow version (use command below): 2.4.0 (git version v2.4.0-rc4-71-g582c8d236cb)
Python version: 3.8.5
CUDA/cuDNN version: 11.2.0-1 / <IP_ADDRESS>-1 (both installed from Nvidia repo)
GPU model and memory: Tesla P100 (16 GB)

Describe the current behavior
After installing latest CUDA and cuDNN via the Nvidia repo I installed latest TF 2.4 via Python pip. Then I run the following:
In [1]: import tensorflow as tf
2020-12-18 14:38:28.563109: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0

In [2]: tf.config.list_physical_devices('GPU')
2020-12-18 14:38:30.711190: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2020-12-18 14:38:30.711736: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcuda.so.1
2020-12-18 14:38:30.738163: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-12-18 14:38:30.738690: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: Tesla P100-PCIE-16GB computeCapability: 6.0
coreClock: 1.3285GHz coreCount: 56 deviceMemorySize: 15.90GiB deviceMemoryBandwidth: 681.88GiB/s
2020-12-18 14:38:30.738710: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2020-12-18 14:38:30.741099: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2020-12-18 14:38:30.741136: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublasLt.so.11
2020-12-18 14:38:30.741931: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcufft.so.10
2020-12-18 14:38:30.742126: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcurand.so.10
2020-12-18 14:38:30.742245: W tensorflow/stream_executor/platform/default/dso_loader.cc:60] Could not load dynamic library 'libcusolver.so.10'; dlerror: libcusolver.so.10: cannot open shared object file: No such file or directory
2020-12-18 14:38:30.742805: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusparse.so.11
2020-12-18 14:38:30.742917: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudnn.so.8
2020-12-18 14:38:30.742930: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1757] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...

So apparently the library libcusolver.so.10 cannot be found.
However, this library file is installed on my machine:
$ locate libcusolver.so.10
/usr/lib/x86_64-linux-gnu/libcusolver.so.10
/usr/lib/x86_64-linux-gnu/libcusolver.so.<IP_ADDRESS>

Any ideas what I am missing here?

@haimat,
TensorFlow 2.4 is built and tested against CUDA 11.0 (not 11.1) and cuDNN 8. Fore more information, please take a look at the tested build configurations.
Could you please install CUDA 11.0 with cuDNN 8 and check if you are facing the same issue. Thanks!

@amahendrakar
Thanks, you're right - installing CUDA 11.0 works with TF 2.4 👍

@amahendrakar I have CUDA 11.1 and tensorflow-gpu 2.4.0 installed in a docker container and I still get the same issue.
I don't know why, but tensorflow is looking for some .so files with 10 in it and some with 11:
2021-01-19 22:40:59.100213: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2021-01-19 22:41:00.124800: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-01-19 22:41:00.125384: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcuda.so.1
2021-01-19 22:41:00.164179: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-01-19 22:41:00.164771: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:42:00.0 name: GeForce RTX 2080 Ti computeCapability: 7.5
coreClock: 1.545GHz coreCount: 68 deviceMemorySize: 10.76GiB deviceMemoryBandwidth: 573.69GiB/s
2021-01-19 22:41:00.164794: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2021-01-19 22:41:00.166734: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2021-01-19 22:41:00.166783: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublasLt.so.11
2021-01-19 22:41:00.167460: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcufft.so.10
2021-01-19 22:41:00.167659: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcurand.so.10
2021-01-19 22:41:00.167849: W tensorflow/stream_executor/platform/default/dso_loader.cc:60] Could not load dynamic library 'libcusolver.so.10'; dlerror: libcusolver.so.10: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/local/nvidia/lib:/usr/local/nvidia/lib64
2021-01-19 22:41:00.168343: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusparse.so.11
2021-01-19 22:41:00.168470: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudnn.so.8
2021-01-19 22:41:00.168486: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1757] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
2021-01-19 22:41:01.228883: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-01-19 22:41:01.228934: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1261] Device interconnect StreamExecutor with strength 1 edge matrix:
2021-01-19 22:41:01.228942: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1267]
2021-01-19 22:41:01.341088: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:116] None of the MLIR optimization passes are enabled (registered 2)
2021-01-19 22:41:01.376711: I tensorflow/core/platform/profile_utils/cpu_utils.cc:112] CPU Frequency:<PHONE_NUMBER> Hz

@amahendrakar I have CUDA 11.1 and tensorflow-gpu 2.4.0 installed in a docker container and I still get the same issue.
I don't know why, but tensorflow is looking for some .so files with 10 in it and some with 11:
2021-01-19 22:40:59.100213: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2021-01-19 22:41:00.124800: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-01-19 22:41:00.125384: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcuda.so.1
2021-01-19 22:41:00.164179: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-01-19 22:41:00.164771: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:42:00.0 name: GeForce RTX 2080 Ti computeCapability: 7.5
coreClock: 1.545GHz coreCount: 68 deviceMemorySize: 10.76GiB deviceMemoryBandwidth: 573.69GiB/s
2021-01-19 22:41:00.164794: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2021-01-19 22:41:00.166734: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2021-01-19 22:41:00.166783: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublasLt.so.11
2021-01-19 22:41:00.167460: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcufft.so.10
2021-01-19 22:41:00.167659: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcurand.so.10
2021-01-19 22:41:00.167849: W tensorflow/stream_executor/platform/default/dso_loader.cc:60] Could not load dynamic library 'libcusolver.so.10'; dlerror: libcusolver.so.10: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/local/nvidia/lib:/usr/local/nvidia/lib64
2021-01-19 22:41:00.168343: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusparse.so.11
2021-01-19 22:41:00.168470: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudnn.so.8
2021-01-19 22:41:00.168486: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1757] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
2021-01-19 22:41:01.228883: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-01-19 22:41:01.228934: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1261] Device interconnect StreamExecutor with strength 1 edge matrix:
2021-01-19 22:41:01.228942: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1267]
2021-01-19 22:41:01.341088: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:116] None of the MLIR optimization passes are enabled (registered 2)
2021-01-19 22:41:01.376711: I tensorflow/core/platform/profile_utils/cpu_utils.cc:112] CPU Frequency:<PHONE_NUMBER> Hz

I also had this issue using a nvidia/cuda container with tensor flow 2.4. Switching from nvidia/cuda:11.1.1-cudnn8-runtime-ubuntu20.04 to nvidia/cuda:11.0.3-cudnn8-runtime-ubuntu20.04 fixed my issue.
https://github.com/argosopentech/onmt-models/commit/d944572d2d9ef57febc7a2854b09e7827e0677ee

I also had this issue using a nvidia/cuda container with tensor flow 2.4. Switching from nvidia/cuda:11.1.1-cudnn8-runtime-ubuntu20.04 to nvidia/cuda:11.0.3-cudnn8-runtime-ubuntu20.04 fixed my issue.
https://github.com/argosopentech/onmt-models/commit/d944572d2d9ef57febc7a2854b09e7827e0677ee

Libcusolver.so.10 is renamed to .11, as CUDA updates from 11.0 to 11.1, so the following works.
sudo ln -s /usr/local/cuda-11.1/lib64/libcusolver.so.11 /usr/local/cuda-11.1/lib64/libcusolver.so.10


Is it possible to use resnet backbone in Yolo v3?

Is there any possibilities to use for instance resnet101 in the Yolo v3? If it is, any resource to find the .cfg and .weights file? Because when I referred to https://pjreddie.com/darknet/yolo/ there was not any resources for resnet backbone.
And I'm just curious, what is the backbone that being used in YOLOv3-320 model provided in pjreddie site?

The backbone used in Yolo v3 is called Darknet-53.
To change the backbone, you should this function to fit the resnet101 architecture and later load its weights.

The backbone used in Yolo v3 is called Darknet-53.
To change the backbone, you should this function to fit the resnet101 architecture and later load its weights.

How can I modify this function so I can change the backbone? What function do I have to modify? Or do I have to make my own function to fit the resnet101?
I'm also wondering because I just found the .cfg link in the pjreddie site here, can I use this .cfg and .weights files and then convert them to create new .h5 file contained resnet101 model, instead modify the model.py?

You have to make your own function to fit the resnet101 architecture.
The .h5 file is just to load the weights into an already built NN.

You have to make your own function to fit the resnet101 architecture.
The .h5 file is just to load the weights into an already built NN.

Alright then. Thank you for the answers!

@dmadhitama Did you find please a solution to  use resnet backbone in Yolo v3 ?

Were you able to implement it? @dmadhitama


License related question

Hello @adigunhammedolalekan ,
We would like to use your package for another open source project (https://github.com/hpcng/singularity) as part of our e2e tests and as github licensing help mentioned:

You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The Open Source Guide provides additional guidance on choosing the correct license for your project.

So we can't really use it either without your consent or with an appropriate license. Is it ok for you that we duplicate your code and set appropriate header and license attached to it ?
I also take the opportunity to mention an import issue with go modules because the module name in go.mod is github.com/adigunhammedolalekan/docker-registry-auth while github repo is github.com/adigunhammedolalekan/registry-auth leading to use a replace directive to import it without any error

Hi, i have just added MIT license. Feel free to use it now.
Also, could you maybe make a PR that fixes the go.mod issue so that other future package users would not have this problem?

Sure, thanks for the quick response :+1: !

Closing the issue and submitted go.mod fix #2 . Thanks !


[Feature] Automatic mixer configuration (Alsa mode)

When allowed, through new variable ALSA_AUTO_FIND_MIXER set to yes, and if MIXER_CONTROL is empty, try to obtain the mixer control name using amixer.

Available in 2022-11-15


Library asymmetry in Categories.Diagram.*

Hi, thanks for this excellent library.
I needed an up-to-iso for pushouts and noticed that is was missing, even though the dual theorem is available for pullbacks.
This led me to notice some other pullback/pushout quirks and inconsistencies. For example:

There are two versions of pullback-resp-≈, one in Categories.Diagram.Pullback and one in Categories.Diagram.Pullback.Properties
unique′ , id-unique, and unique-diagram are treated as properties for pushouts and exported by Categories.Diagram.Pushout.Properties, whereas they are treated as conservative extensions (i.e. record fields) for pullbacks and exported by Categories.Diagram.Pullback
Pullbacks come in bundled and unbundled form, while pushouts only come bundled

I'd like to make things consistent between pullbacks and pushouts, and a cursory look at the other modules in Categories.Diagram.* suggests that a few of the other Thing / Cothing pairs could benefit from a similar cleanup.

All of these are typical warts of libraries that grow organically. Thanks for noticing and listing them explicitly.
A bunch of small PRs fixing this would be most welcome. Definitely best to do it piece-by-piece, so that the uncontroversial stuff can just go in, and anything that needs discussion doesn't hold anything up.
For some of these, it might be wise to first open an issue, to discuss which way we'd like to resolve the inconsistency. That way you won't waste your time implementing a solution that goes in the opposite direction of expectations. But each one of these inconsistencies should get fixed.