Perform Deterministic Build

Description
Perform deterministic build when publishing package.
Type of Change

[x] Bug Fix
[ ] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[ ] Other (please describe)

Checklist

[x] I have read the contributing guidelines
[x] Existing issues have been referenced (where applicable)
[x] I have verified this change is not present in other open pull requests
[x] Functionality is documented
[x] All code style checks pass
[x] New code contribution is covered by automated tests
[x] All new and existing tests pass

Codecov Report
Patch and project coverage have no change.

Comparison is base (4c27c2a) 100.00% compared to head (d523de8) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           41        41
  Branches         2         2
=========================================
  Hits            41        41

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add custom type mapping for find method

I'm not sure if this is right or not, but my custom types are failing to load when using findOne or find methods.
Debugging I realized the find method in AbstractSqlDriver creates a QueryBuilder with the convertCustomTypes flag set to false.
I changed it to true and now I get the results as expected.
Am I missing something?
Shouldn't the find methods return the mapped custom types as I defined them in the entities?

As you can see in the tests, your change would break something (namely #446).
Custom types should be already converted at the driver level.
Please provide a repro for your problem first.

Sorry, I tried to run the tests but I could not get them to work.
Anyway, I figured something like this would happen.
What I don't understand is, aren't findOne and find supposed to convert values also? How are they going to convert values if the driver method they use is hardcoded to false?
Shouldn't the driver method at least have a parameter just like nativeUpdate indicating whether we want conversion or not?

As I already said, custom types are converted at the EM level, what gets to driver should be already converted. Most probably you have a different issue - that is why I am asking for a reproduction.
One way or the other, I won't merge anything that does not have a test case to prove the change is needed. You should always first build the failing test before you start changing the code.

Sure, I'm not asking you to re-open this nor merge something without tests, I was just wondering.
Anyway, if you are curious I found the problem, it was the other thing I fixed in #1415, it looks like because of that the EM was not doing its job properly, but with that fix in everything works and I don't need this flag anymore.

Makes sense, if the property was retrived from db with wrong casing, the ORM will see it as undefined, hence ignore it.
Btw you can already try the dev version with your fix: 4.4.3-dev.19

I noticed the next package on npm, thanks.
I'm already using it.


Improve ergonomics of creating and importing keys

Creating a KeyPair from a PrivateKey
Creating PrivateKeys and PublicKeys from hex doesn't need to take self

thanks!


"supernode" command should be a verb

All commands are verbs (clean, compose, start, stop, ...). It is unclear what action the supernode command does.
I suggest registerSupernode or something similar.
This should be changed before the supernode program goes public or we will be stuck with this API!

released on 0.4.2


2.22 shows errors on install, currently being fixed

Current behaviour of 2.22:

Plan:

deprecate postinstall
set ignore-scripts true in the .npmrc

we can't set ignore-scripts to true in the .npmrc as this also prevents npm run xxx commands.   The best we can do is to disable scripts when running npm i
So there is no need to deprecate postinstall and we can use it for applying git hooks

fixed in #687


Unselected Radio Buttons are white colored on Light Theme

[x] I have verified there are no duplicate active or recent bugs, questions, or requests
[x] I have verified that I am using the latest version of Material Dialogs.
[x] I have given my issue a non-generic title.
[x] I have read over the documentation (before asking questions on how to do something).

Include the following:

Material Dialogs version: <IP_ADDRESS>
Device OS version: 6.0.1
Device Manufacturer: LG
Device Name: Nexus 5X

Also, please wrap Java with correct syntax highlighting.
System.out.println("Hello, world!");

Reproduction Steps

Make Single Choice List Dialog on Material Dialogs version: <IP_ADDRESS>
Change Material Dialogs version to: <IP_ADDRESS>

Expected Result

Actual Result

I've experienced no issues here.
The color of unchecked radio buttons is derived from R.attr.colorControlNormal. You may want to check if you're overriding that in your Activity theme.
Your Activity theme also needs to be derived from the AppCompat themes.

I had the same problem before. And my textColorSecondary was #FFFFFF. I changed it and it worked.

same happen with me, i can't change , when i change
@color/white
it changes , but i can't do this for my theme, because this will change other component colors too,
any way to change this only for the radio button ?


Feature/ellipsis

Rebrand of Ellipsis - no CSS update needed

A similar pull request was merged yesterday, so why open a new one?


NPM Fix and NPM Check Not Producing Output

On Linux the tasks for NPM Fix and NPM Check are not producing any output to the log.

Will be fixed with 1.3


Adding in functionality to return Subtasks and Components to search_issues

get_issue currently has the ability to enable flags to include an issue's Subtasks and Components.
However, this is also an available flag for search via the API, where you can include Subtasks and Components for issues which are returned by the JQL search query.
This PR adds the include_subtasks and include_components flags to the search_issue action. I've tested these changes locally by modifying the existing action, and there seems to be no impact on other functionality by adding these flags.
CHANGES.md has been updated, and pack.yaml version has been incremented to 2.4.1.

@floatingstatic Updated! Thanks.


RC keeps creating new pods if there's an issue starting a container, even after RC is deleted

The scenario is when a replication controller is created which starts a pod that will always error (an issue in a CMD start.sh script for example), the failed pod is left 'Exited' and 30 seconds later a new pod is scheduled.
This continues to happen even if the replication controller is deleted, the pods are still endlessly scheduled resulting in many many failed containers.  This seems to result in high CPU usage of the docker process if left for a while.

I wonder if we need to do a better job of aggressively garbage collecting repeated failures of containers on the host (if the Kubelet detects a pod is in a repeat fail loop, only the last N pods should be kept, instead of using the regular garbage collection policy).

The rc will keep trying to match its replica count. It only knows to detect the status of a pod. So if the container exiting leaves it in a non-running state (i.e Failed or Succeeded) the rc will create a new one. What status is your crashing pod?

 So the other components of the system (scheduler, kubelet) will keep trying to run them.

Container gc https://github.com/GoogleCloudPlatform/kubernetes/issues/3649

The rc will keep trying to match its replica count. It only knows to detect the status of a pod. So if the container exiting leaves it in a non-running state (i.e Failed or Succeeded) the rc will create a new one. What status is your crashing pod?

 So the other components of the system (scheduler, kubelet) will keep trying to run them.

Yep that makes complete sense, I didn't stop the RC first

Seems like the gc issue is discussed on another bug, and the solution to the rc problem is to call stop. Please re-open if this isn't the case.

Agreed thanks.

I'm confused - for a run-forever pod, why would it get mark failed and why wouldn't the replication controller back off?  This has changed from previous behavior if so.

RestartPolicy should be honored. I didn't see a mention of RestartPolicy=Never in the initial report, is that what's happening? I believe the default policy is restart always for pods created through an rc (https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/api/validation/validation.go#L910).

Replication controller only work with RestartPolicy=Always pods.
There is one scenario where the pod status may be failed even though the restart policy is always -- when kubelet explicitly rejects the pod.
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/kubelet.go#L1595

James, do you have the json/yaml for the replication controller that was creating the pods?
----- Original Message -----

Replication controller only work with RestartPolicy=Always pods.
There is one scenario where the pod status may be failed even though the
restart policy is always -- when kubelet explicitly rejects the pod.
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/kubelet.go#L1595

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/issues/6291#issuecomment-88624460

The rc can only create a pod with restartpolicy=always, it will manage pods with restart=never because it checks selectors and nothing else. So if you have:

rc:

replicas: 1
selectors: foo

pod1:

restartpolicy: Always
labels: foo

and you create:

pod2:

restartpolicy: Never
labels: foo

And the rc picks pod1 to kill, and pod2 dies, a new pod will be created with RestartPolicy=Always. This has always happened AFAIK, essentially we treat RestartPolicy like any other field in the spec, nothing special to the rc.
Re kubelet: That's desirable IIUC. In almost every case that the kubelet rejects pods, the scheduler will too, unless you have static pods on the kubelet the scheduler doesn't know about. In that case, the Failed status is desirable because the rc will recreate the pod, and hopefully the scheduler will send it to another host.

I think what I'm getting at though is that creating a process that fails to start doesn't sound like Failed (failed was very specific, meaning that it's been rejected).  I don't think that's the case yujuhong was describing here.  So I wouldn't expect a pod process that dies unexpectedly to trigger Failed in a way that schedules new pods.  I know whether a "Never" pod was involved or not.

Ah, then it's a 'pod shouldn't be in failed' bug. The contract of the rc is that it will restart failed pods that have matching selectors, changing this doesn't make sense to me. @rawlingsj if you can provide more info about the pods failure mode please reopen (and re-title).

The only criteria I was aware of for a RestartAlways pod being in failed was kubelet rejected.  Are you saying that's not the case?

On Apr 1, 2015, at 6:25 PM, Prashanth B<EMAIL_ADDRESS>wrote:
Ah, then it's a 'pod shouldn't be in failed' bug. The contract of the rc is that it will restart failed pods that have matching selectors, changing this doesn't make sense to me. @rawlingsj if you can provide more info about the pods failure mode please reopen (and re-title).
—
Reply to this email directly or view it on GitHub.

That sounds like what the bug is about, from my somewhat limited comprehension of https://github.com/GoogleCloudPlatform/kubernetes/issues/6291#issuecomment-88522471 at least.

@smarterclayton sorry I missed your request for json / yaml.  I can put a test case together quickly and add a comment today.

Ok so I've created a really basic example to hopefully demonstrate the issue.  The container will always fail, in the example it hard codes an error exit code to simulate something going wrong in a start script..
https://github.com/rawlingsj/kubernetes6291/blob/master/start.sh#L1
This is the replication controller config I'm using..
{
  "id": "kubernetes6291-controller",
  "kind": "ReplicationController",
  "apiVersion": "v1beta1",
  "desiredState": {
    "replicas": 1,
    "replicaSelector": {"name": "kubernetes6291"},
    "podTemplate": {
      "desiredState": {
        "manifest": {
          "version": "v1beta1",
          "id": "kubernetes6291",
          "containers": [{
            "name": "kubernetes6291",
            "image": "rawlingsj/kubernetes6291"
          }]
        }
      },
      "labels": {
        "name": "kubernetes6291"
      }
    }
  },
  "labels": {
    "name": "kubernetes6291"
  }
}

This results in the replication controller endlessly scheduling pods that will fail.  This is only meant to demonstrate the issue but there doesn't seem to be any fail safe limits that prevent thousands of pods being created which can eventually leave a machine unresponsive if left unnoticed.

We have limits and quota, they're just not turned on by default.  The kubelet should be delaying the failure of pods eventually.  I think the real point of this issue should be that the system should reduce the impact of perm-failed containers on the rest of the system (we've noticed this in real use, that a perm failing container starts to drain both Kubelet and Master resources due to the increased traffic of client requests and polling).

So quota does not really help here if I understand the issue.  A pod whose restart policy is set to always is always counted against your quota even if its in a failed state because we know the kubelet will just restart it.  It's not like there are new pods being created in this scenario.  To the apiserver, its just the same pod getting restarted.  I think this topic is more an issue with the Kubelet and what it should do if it sees the same container repeatedly fail in a quick period.

See also #2529

Do we want to track the kubelet part of this issue (kubelet retries every 3 seconds FOREVER to restart perm failed pods) or the other?

A POD with phase=Failed should never be restarted by Kubelet. It shouldn't reach that phase for mere container failures if RestartPolicy=Always. If that is happening, it is most definitely a bug.

If the Kubelet issue is the only one remaining, we might as well just use this issue.

If I read the issue correctly, this is not a problem of creating new pods, but rather about creating new containers. If a container is doomed to fail and the restart policy for the pod is "always", kubelet will periodically examine the pod status and creates new containers if needed. This could potentially stress the system unnecessarily.
@bgrant0607, I don't think the issue is about kubelet restarting failed pods. The pod should be in the running state with an increasing number of dead containers.
There is an open issue to back off restarting containers to resolve issue like this (#4121). I had written some code, but the PR is currently on hold due to the container runtime refactoring in kubelet. I think we can close this as a dupe. Please reopen if this is not true.


Network format-disconnected doesn't allow Unicode characters

If I have this in my config (if the chars don't show, I'm using Font Awesome chars):
    "network": {
        "tooltip": true,
        "tooltip-format-ethernet": "{ifname} ({ipaddr})",
        "tooltip-format-wifi": "{essid} ({ipaddr}) {signalStrength}",
        "tooltip-format-disconnected": "DISCONNECTED",
        "format-ethernet": "  ",
        "format-wifi": "  ",
        "format-disconnected": "  ",
        "on-click": "nm-connection-editor"
    },

when the ethernet is disconnected (and there is no wifi), the ethernet connected icon shows. However, the field is red as determined by its disconnected status and my style.css, so Waybar does know it's disconnected, it's just showing the wrong icon.
If I change the format-disconnected to eg:
        "format-disconnected": " -- ",

then it correctly displays "--" when it is disconnected.

Ok this is weird. If I change the disconnected format to:
"format-disconnected": " H ",
then it shows it correctly when disconnected.

Yep, it seems it's literally only a problem when the icon is just surrounded with spaces.

If it just has one space to the left of it, or one to the right, it works fine. If there is one space on either side (and nothing else, "  ") then that's the only situation in which it doesn't work.

If I change the ethernet and disconnected formats to:
"format-ethernet": "  l",
"format-disconnected": "  ",

then they work fine. Is there a map somewhere, which uses the format as a key, and it's getting them mixed up (possibly because the unicode chars gets turned into the same char)?

I think I might have found the problem.
https://github.com/Alexays/Waybar/blob/master/src/modules/network.cpp
line 282:
if (text != label_.get_label()) {

I bet that text comparison doesn't cope with the unicode characters. So it doesn't change the label text when the ethernet is disconnected, because it thinks the new text is identical.

Created pull request https://github.com/Alexays/Waybar/pull/589


MAISTRA-1921: Support dynamic crypto based on environment

This PR modifies the defaults used when running within a FIPS environment.

/retest

/retest

I'm going to revert the code tomorrow, back to the logging version, and then try to bypass the level settings to always display

I had a long think about this while on a bike ride
The following options have been tried

variable initialiser with logging framework (impacts some fragile Envoy tests which break with the extra output since logging levels have not been set to warning)
on demand initialisation with logging framework (logging level is at warning so no output)
on demand initialisation with cout - Success but not ideal solution

since each of these causes issues, or is undesirable in some way, I've decided to revert to the original variable initialisation and not log the status.

/retest

Test failure is IpVersions/IntegrationTest.ResponseFramedByConnectionCloseWithReadLimits/IPv4 which seems to be a flaky test, it has happened with previous PRs.

I had a long think about this while on a bike ride
The following options have been tried
* variable initialiser with logging framework (impacts some fragile Envoy tests which break with the extra output since logging levels have not been set to warning)

* on demand initialisation with logging framework (logging level is at warning so no output)

* on demand initialisation with cout - Success but not ideal solution

since each of these causes issues, or is undesirable in some way, I've decided to revert to the original variable initialisation and not log the status.

If you wish, you can append something like "/FIPS" in the output of --version command here: https://github.com/maistra/envoy/blob/maistra-1.1/source/common/common/version.cc#L22

@jwendell that's a good idea, although at this point I've spent more time on fixing the logging than I did on fixing the actual issue


Make it possible to run only a part of the tests.

Partially done with --specification (2cc4ad4f0f73be4d49e51d065bd8116071ccfb18)

Done with #11


Update sbt-scalajs, scalajs-compiler, ... to 1.10.1

Updates

org.scala-js:sbt-scalajs
org.scala-js:scalajs-compiler
org.scala-js:scalajs-library
org.scala-js:scalajs-test-bridge

from 1.9.0 to 1.10.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-js" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #267.


Cannot get boolean values in translations

dd(Lang::get('test.key'));
Lang test.php file
return [
    "key" => 1,
];

Does not return booleans from translation. Only if i type 1 as string "1" will dump it.
Laravel Framework version 5.1.21

It's only intended for use with strings.


change: Replace block expression with eval expression.

What

Resolve #189
Why

Additional info (optional)

一旦close

作業完了


Understanding kube_node_status_condition metric

I see this metric has the following dimensions -

status - (values I see: true, True, Unknown, False)
status2 - (values I see: Ready, Unknown, NotReady)
condition - (values I see: Ready)
node - (values I see: as I expect, node names)

Can I get some help on how to make use of the above dimensions to say whether a given node is ready or not?
Thanks!

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

ID: a0a586c4-71fd-e60b-9c4c-1a3eb2443c74
Version Independent ID: 2f3706cc-073b-a310-8da4-2a5a90da6473
Content: Azure Monitor supported metrics by resource type
Content Source: articles/azure-monitor/platform/metrics-supported.md
Service: azure-monitor
GitHub Login: @anirudhcavale
Microsoft Alias: ancav

@sgoings can you help out here?

Walkthrough on the metric / dimensions here: https://github.com/Azure/azure-libraries-for-java/issues/563

Thanks @sgoings.
We will now close this issue. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


[Issue] Creating multiple invites limit broken

No need to explain:

The limit was changed to 100. Must've forgotten to change the text too...


lootconditions

Introducing Loot Conditions: Building on Ability Scores & Characters, Conditions add or subtract from ‘existing’ attributes.
Some example follow up contracts:
Spells: Mint spells which can apply conditions to character/ability scores.
Enchanted Artifacts: Apply conditions to Loot items such that when wielded, a character’s attributes are affected.

LGTM, thanks!


IBM-426 As a user I want to be able to extract a report of events from the IRC so that I can better understand what has happened at the IRC

Coverage increased (+0.005%) to 99.179% when pulling 03e7595a51bca00e06e5b632088130787f34dcdb on feature/IBM-426 into beb2a24d24f7fb98b915f450e8c65a337a0fe4f0 on master.


More navigation shortcuts between moves

Player should be able to go to the next/previous branching move or to the next/previous last move in variations

This feels a duplicate of future lichess functionality. Also, probably going to be addressed in https://github.com/Siderite/lichessTools/issues/204. Closing for now.


Replace Emoji in usernames

I've updated the function that is used for the tweets emoji replacement to also replace them in usernames, either when looking at the stream or when viewing a user profile directly. I'm looking into how to replace them when viewing DMs and I'll update the pull-request later.
@sindresorhus Any reason to restrict emoji replacement with the #stream-items-id?

Messed up repository, I'll open this again!


Reenabled Rust checks [ECR-2750]

Overview
Re-enabled Rust checks on Travis
See: https://jira.bf.local/browse/ECR-2750
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 85.666% when pulling f9e1f77f49147190415b4d01ec161867484f3373 on reenable-rust-checks-ecr-2750 into 57aa684f45d8501bba7bf1c1b25eed257d2b94e7 on master.


How can I get the New message from instagram?

I am very interested in this api, so I was tring to understand what is the node.js.
Currently, I am availablt to tourch anything using Node.js and typescript.
In this case, I am wondering how can I get the new messages from instagram using this api.
My example look like:
const ig = new IgApiClient();
ig.state.generateDevice(process.env.IG_USERNAME);
ig.state.proxyUrl = process.env.IG_PROXY;
await ig.account.login(process.env.IG_USERNAME, process.env.IG_PASSWORD);
const dmFeedPending = await ig.feed.directPending();
const dmFeedPendingItems = await dmFeedPending.items();
// tslint:disable-next-line:no-console
console.log('dmFeedPendingItems', dmFeedPendingItems);

But result is look like:

Could you teach me how can I get the un-read messages from instagram using this API with realtime or ...?

DirectPendingFeed contains the pending requests for your account. It may boe empty because you have no requests. In order to get the unread threads use:
const items = await ig.feed.directInbox().items();
// get more[...]
const unread = items.filter(x => x.read_state > 0);

Hello Nerixyz thanks for reaching me out.

My code is look like, currently I was fetch the X on filter, there are variable to show me.

but I don't know what was my mistake on my progress. Should I need to conver the x.read_state?

read_state should exist on the thread. You can suppress that error.


Single User Creation wizard  user store filed is enable by default.

Describe the issue:
In IS Single User Creation wizard  user store filed is enable by default and in cloud it available only once we create user store only.
Cloud

IS

How to reproduce:

Login to console
Select the user management -> select users
Click Add user
Select single user

Expected behavior:
Single User Creation wizard  user store filed is enable by default in IS and in cloud its not.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

This is expected since in Asgardeo we don't need to show the default asgardeo user store name.


linter in CI doesn't work as expected

What happened:
If you run this command
golangci-lint run --issues-exit-code=1 --timeout 5m0s --tests=false
you will see the below errors:
internal/cache/error_resolver.go:37:30: printf: non-constant format string in call to fmt.Errorf (govet)
		return v.Value, fmt.Errorf(v.Error)
		                           ^
syft/internal/packagemetadata/discover_type_names.go:81:26: printf: non-constant format string in call to fmt.Errorf (govet)
		return nil, fmt.Errorf("not enough metadata definitions found (discovered: " + fmt.Sprintf("%d", len(strNames)) + ")")
		                       ^
syft/internal/sourcemetadata/discover_type_names.go:71:26: printf: non-constant format string in call to fmt.Errorf (govet)
		return nil, fmt.Errorf("not enough metadata definitions found (discovered: " + fmt.Sprintf("%d", len(strNames)) + ")")
		                       ^
cmd/syft/internal/commands/scan.go:164:21: printf: non-constant format string in call to fmt.Errorf (govet)
		return fmt.Errorf(error)
		                  ^
cmd/syft/internal/commands/scan.go:164:10: SA1006: printf-style function with dynamic format string and no further arguments should use print-style function instead (staticcheck)
		return fmt.Errorf(error)
		       ^
syft/pkg/cataloger/cpp/parse_conanfile.go:27:8: SA1032: arguments have the wrong order (staticcheck)
		case errors.Is(io.EOF, err):
		     ^
syft/pkg/cataloger/cpp/parse_conaninfo.go:102:8: SA1032: arguments have the wrong order (staticcheck)
		case errors.Is(io.EOF, err):
		     ^
syft/pkg/cataloger/elixir/parse_mix_lock.go:31:8: SA1032: arguments have the wrong order (staticcheck)
		case errors.Is(io.EOF, err):
		     ^
syft/pkg/cataloger/haskell/parse_cabal_freeze.go:26:8: SA1032: arguments have the wrong order (staticcheck)
		case errors.Is(io.EOF, err):

However it seems the CI doesn't fail.
What you expected to happen:
CI should detect these errors
Steps to reproduce the issue:
as I mentioned above
run manually the command from the root directory of syft
Anything else we need to know?:
Environment:

Output of syft version: 1.11.0
OS (e.g: cat /etc/os-release or similar): mac

Are you running the version of golangci-lint that is installed by Syft's Taskfile? ./.tool/golangci-lint run --issues-exit-code=1 --timeout 5m0s --tests=false succeeds for me on main.
It's possible the version of golangci-lint on path is newer or older than the one in .tool and that is causing this difference.

hi,
My version is:
golangci-lint has version 1.60.1 built with go1.22.6 from 3298c10 on 2024-08-14T01:09:25Z

we're working on fixing the current code to match the latest linter updates for new golangci-lint

The issue description reads that syft v1.11.0 source tree was scanned, which has golangci-lint pinned at v1.59.1 where as from your comment above you're using version v1.60.1. This can result in inconsistent results as you're reporting. For development you'll need to use the local tooling as Will described.
Here are some helpful make/task targets:
make tools      # download all tools
make lint       # run all linter rules (golangci-lint + others)
make lint-fix   # run linter + auto fixers


JSHint error

modules/sl-ember-components/components/sl-alert.js: line 18, col 10, 'Theme' is not defined.

May become resolved by https://github.com/softlayer/sl-ember-components/issues/545

Resolved by https://github.com/softlayer/sl-ember-components/pull/609


Improve the flight search

Is your feature request related to a problem? Please describe.

I'm trying to get the flight search form to work, with the "only show/allow flights from current location" option enabled.

Keeping that when you try to make the booking it tells you that you are not at the departure airport.
This way, a pilot could see, for example, all the routes he can fly with a certain sub-fleet or flight duration, and after do a jumpseat/aircraft transfer.
Actually, with show/allow option enabled and joined, a pilot only can search in their current airport, so leaves the search engine useless.

Additionally, many pilots are asking to be able to see a list of flights they have not yet flown.

Describe the solution you'd like

I found two ways, I think it is best to do the simplest and least change-intensive one for core and third-party addons.

First manner:
Separate the option "only show/allow flights from current location" in two:
"only show flights from current location" False
"only allow flights from the current location" True

Second manner:
Create other option in admin side settings to search flights tool:
I commented this code:
phpvms\app\Http\Controllers\Frontend\FlightController.php

97         // default restrictions on the flights shown. Handle search differently
98         /*if (setting('pilots.only_flights_from_current')) {
99             $where['dpt_airport_id'] = $user->curr_airport_id;
100        }*/

I think that last solution is the most affordable, an option in admin settings to enable/disable that code. But I am not an expert, hehe.

To the second feature, I think a checkbox could be added that says "exclude flights already flown" or similar.
Clicking the button to start the search would return a list of flights that meet the criteria, but exclude flights that the pilot has already flown.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

"Exclude flights already flown" part is kind of non schedule logic, I mean not realistic considering "flight schedule" displaying. (Can be done, not impossible but how do you want to match pireps with flights? Id match or city pair match or flight number match, what will happen if you update your schedule etc... all those checks mean server load and processing time, imagine a va with 20k flights and a user with 5k pireps)
First part of your request, the part for seperation of allowing and displaying options, is understandable and may fit more to a realistic "flight schedule" system.

"Exclude flights already flown" part is kind of non schedule logic, I mean not realistic considering "flight schedule" displaying. (Can be done, not impossible but how do you want to match pireps with flights? Id match or city pair match or flight number match, what will happen if you update your schedule etc... all those checks mean server load and processing time, imagine a va with 20k flights and a user with 5k pireps)
First part of your request, the part for seperation of allowing and displaying options, is understandable and may fit more to a realistic "flight schedule" system.

I know, compare flight number in user and in flights is heavy load to server. Is what I replied to them when they asked me that.
I don't think there is a solution where there is no such workload. I don't know how it could be done either.
I suppose I could export a sql query and send it as a pdf to interested pilots.

It is not just server load, it is a complex logic. Imagine you have 10 flights between MAD - AMS replicating a real airline, all with different departure times, different flight numbers, and as expected different flight id's and all can be flown with different aircraft. And a pilot only used 2 of them in the past.
If you filter out with just flight id's, then you will not show 2 of it, but there will be 8 more MAD - AMS flights to list.
If you filter out with DEP-ARR airports, all will be hidden if a pilot flies only one flight between MAD - AMS.
Add multiple airlines to the equation, it will be really a complex matching logic which will never please everyone at the same time. You will request filtering with DEP-ARR match, another person will like to filter out with flight id's, another VA or admin will wish to filter out if all aircraft options are used etc.
This is why I did not liked that idea, a pilot can track his/her own flights if he/she does not want to fly the same city pair again, it is a personal choice and task.

a pilot can track his/her own flights if he/she does not want to fly the same city pair again,

Currently, is that possible?
I told them that on the map they could see this, but apparently it shows by city not by flight, so they don't know if they've done a round trip or a return, anyway you are right in your argument.

The idea is interesting but needs more thought


Help! logging to 2 different files for 2 different modules of the same sofware

Hi, This is not exactly an issue, but I couldn't find a way to log to 2 different files.
we use this logger module in a software being developed by two developers, and each developer needs the log of his module to be in a separate file. going through the manual I could not find out how to do that using this log module. how is that possible? thanks

You essentially need two seperate loggers for each module.
Doc: https://github.com/easylogging/easyloggingpp#registering-new-loggers
You may also be interested in Multi logger support (Sample: https://github.com/easylogging/easyloggingpp/blob/master/samples/STL/multiple-loggers.cpp) which means logging same message to different multiple loggers
You may also be interested in this sample or this project that makes use of logging really well and in depth with modules (extensions)


executionHistory.bin is constantly increasing its dimensions

Expected Behavior
rootProject/.gradle/4.7/taskHistory/taskHistory.bin should not grow so big: in the order of GB
Current Behavior
taskHistory.bin is slowly but constantly growing up to 2, 5 or 10 GB.
gradle clean doesn't clean this file because it's part of the deamon cache I think.
Context
I have about 200 java projects with gradle nature, the root project has a gradle wrapper in it.
I use many java analysis tools to find errors and bugs.
Executing gradle build in eclipse or via command line, during the build process, taskHistory.bin changes and grows its dimensions.
This fact triggers the error java.io.IOException: No space left on device in Jenkins server.
This happens even with older gradle versions.
Steps to Reproduce (for bugs)
project example: projectA.zip
In the zip, there is a root project with 3 subprojects, if you run from the wrapper ./gradlew build the file ./.gradle/4.7/taskHistory/taskHistory.bin is created.
After that, duplicate ApiClazz.java in another class, run ./gradlew build , the file taskHistory.bin changes. Do the same with DriversClazz.java and the size increases again.
With lots of plugins and many changes, taskHistory.bin becomes really big.
Your Environment
Gradle 4.7
java 8
eclipse oxygen 4.7.3a
buildship eclipse plugin 2.2.1
java analysis tools:
spotless
error prone

This is somewhat related to https://github.com/gradle/gradle/issues/1085, but not very much.
In general, Gradle does not do a very good job in cleanup up its caches. For the task history it is also somewhat hard to decide what to clean up. On running a clean, taskHistory.bin becomes pretty useless, since all the tasks will be out of date anyway.
Currently, taskHistory.bin will hold the history of the last time any task was executed, but not any more. So if the task names do not change much, the history should also not have stale entries and should grow proportional to the number of files the tasks have as inputs and outputs.

So if the task names do not change much, the history should also not have stale entries and should grow proportional to the number of files the tasks have as inputs and outputs.

Well, my test case shows up that even adding new classes to the plugin increases the size of taskHistory.bin

@regrog You are right, we still have some problems cleaning up the task history. Note that it is expected that the task history grows if there are more files as inputs/outputs (i.e. adding a source file), but it should recover the space at some point if files are only renamed/changed.

Any improvements about this?

/still valid

FTR, we are investigating moving to H2/MVStore for execution history and other local caches. Doing so will allow us to implement regular cleanups for these caches. (Gradle only has cache cleanup for file-based caches, i.e. where individual entries are represented by entire files.)

what is lost if the executionHistory.bin is deleted?  will it degrade the ability for future builds to skip doing work?
we have some persistent gradle caching, and I'm trying to figure out the right timeline for cleaning out this file. Nightly? weekly? Every run?

Any update on this issue?


Java 17 support and official distributions

Currently Jenkinsfile Runner ships only with Java 11. @timja @basil and other contributors made a lot of work to ship Java 17 preview support in the Jenkins core, and it would be awesome to ship Jenkinsfile Runner distributions for it too
Scope

[ ] Add test automation fo Java 17 compatibility
[ ] Create preview Docker distributions for Java 17
[ ] Document Java 17 support policy

I started on a PR https://github.com/jenkinsci/jenkinsfile-runner/pull/723 to upgrade to Java 17 and newer Jenkins release 2.462.3. Having trouble getting the builds to work in the PR. But locally I was able to compile and build the docker image with Maven 3.9.9 and Java 17
mvn clean install -Denvironment=test -Ppackage-app,package-vanilla,jacoco,run-its -DargLine="--add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED"

podman build -t jenkins4eval/jenkinsfile-runner -f packaging/docker/unix/eclipse-temurin-17-jre/Dockerfile . --arch x86_64

Yes, Java 17 or even 21 are fine
On Wed, Nov 13, 2024 at 3:38 PM Shawn Thompson @.***>
wrote:

I started on a PR #723
https://github.com/jenkinsci/jenkinsfile-runner/pull/723 to upgrade to
Java 17 and newer Jenkins release 2.462.3. Having trouble getting the
builds to work in the PR. But locally I was able to compile and build the
docker image with Maven 3.9.9 and Java 17
mvn clean install -Denvironment=test -Ppackage-app,package-vanilla,jacoco,run-its -DargLine="--add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED"
podman build -t jenkins4eval/jenkinsfile-runner -f packaging/docker/unix/eclipse-temurin-17-jre/Dockerfile . --arch x86_64
—
Reply to this email directly, view it on GitHub
https://github.com/jenkinsci/jenkinsfile-runner/issues/569#issuecomment-2473805662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW4RIASJXSRYYYVWQI64UD2ANP5XAVCNFSM6AAAAABRWUTFPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZTHAYDKNRWGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Factor out mutation-setting logic from 'Connection'.

Toward #514.

Coverage remained the same when pulling 5f28d27bc90bf8b294554ffc51b7ba6110a952cf on tseaver:disuse_connection_save_delete_from_batch into 7c01fcc992032b8e82d8dfd642f7af64df2e8d88 on GoogleCloudPlatform:master.

@tseaver

This is just a part of the third bullet in #514? I.E., slowly reduce dependencies on save_entity() and delete_entities()?
ISTM delete() and put() are ready to go in datastore.api as you outlined in #518, yes? I can do that if you like or just sit back and watch.

Mostly LGTM other than small comments

@dhermes: rebased / updated to address your concerns in 8bd5059.  PTAL.

Coverage remained the same when pulling 8bd5059b6611eb46868f731aae0a3471699a15bf on tseaver:disuse_connection_save_delete_from_batch into 0525530ad7a76e408ca2e842b883d49c353ed56d on GoogleCloudPlatform:master.

One concern still dangling at
     if auto_id:
         insert = mutation_pb.insert_auto_id.add()
         auto_id_entities.append(entity)
     else:
         insert = mutation_pb.upsert.add()

Can you add a comment above here explaining that we don't use insert or update
but are aware of their existence and may add in future?

Can you address my two questions above? See #527 regarding point 2) above.

Good catch:  0525530 has the comment, which I hadn't saved to disk :(.
WRT #527: I really don't want to have begin() moved outside the context manager:  it removes most of the point of the CM in the first place.

Coverage remained the same when pulling 6af6e6d638b21f41a24bf268e1fdf21dec165486 on tseaver:disuse_connection_save_delete_from_batch into 0525530ad7a76e408ca2e842b883d49c353ed56d on GoogleCloudPlatform:master.

LGTM


On entity killed doesn't fire when entity dies from "natural" causes

an entity dying by fire, or lava, or even fall damage doesn't cause the on entity killed event to fire..
This leaved a gap for metadata to be retrievable between on entity death and on entity killed.... :(
Please fix <3

That... doesn't make much sense, unless @Talamar1 broke something and made it require a damager or something.

On entity killed only does when it is killed by another entity

Try the latest dev build, I possibly fixed it maybe.

Okay will when I surface

Did you test it?

@mcmonkey4eva I did yesterday, told you in IRC it works.. :heart:


Impossible to use react-router-native with redux

Version
4.0.0
Problem
As I understand it is impossible to use out of the box react-router-native with redux, because react-router-redux ConnectedRouter import web version of react-router.

That isn't the web version. That would be react-router-dom. You can pass a memory history into ConnectedRouter with native, as far as I know.


Broken docs link

Docs link is broken on the link below.
https://foundation.zurb.com/sites/getting-started.html

And there is also See Upcomming Classes hwich should be See Upcoming Classes.
Not sure where the templates for the website can be edited here. Did not find them in the zurb org on GitHub.

I don't think the site lives inside this repo.
Tagging and assigning to @rafibomb.

Seems to be fixed. Closing.


ci: Use Ubuntu 22 instead of 18

CI Vulkan-Tools build queued with queue ID 52218.

CI Vulkan-Tools build queued with queue ID 52218.

CI Vulkan-Tools build # 956 running.

CI Vulkan-Tools build # 956 passed.

CI Vulkan-Tools build queued with queue ID 52228.

CI Vulkan-Tools build queued with queue ID 52228.

CI Vulkan-Tools build # 957 running.

CI Vulkan-Tools build # 957 passed.

CI Vulkan-Tools build queued with queue ID 52306.

CI Vulkan-Tools build queued with queue ID 52306.

CI Vulkan-Tools build # 958 running.

CI Vulkan-Tools build # 958 passed.


Invalid authentication:

I'm trying to connect to clickhouse with such jdbc url (clickhouse-jdbc 0.4.0):
jdbc:clickhouse://host:port/?socket_timeout=6000000&custom_settings=user%3Ddefault%2Cpassword%3Dpassword
But got an error:
Execution error (IOException) at com.clickhouse.client.http.HttpUrlConnectionImpl/checkResponse (HttpUrlConnectionImpl.java:184).
Code: 516. DB::Exception: Invalid authentication: it is not allowed to use SSL certificate authentication and authentication via parameters simultaneously simultaneously. (AUTHENTICATION_FAILED) (version <IP_ADDRESS> (official build))

UPD: I also tried to pass creds in ordinary url params, in params using //user:pass@, add ssl=false, sslmode=none

Hi @ilevd, it looks like the default user is configured to use SSL certificate for authentication? Have you checked config.xml in ClickHouse server?

Hi @zhicwu, settings are standards, I'm migrating from ru.yandex.clickhouse/clickhouse-jdbc "0.3.1" driver, with it it connects normally with user/password in url string.

Might be an issue similar to #1114, will try to fix it in the upcoming connection string parser.
As a workaround, perhaps you may use connection properties to set credentials instead of putting them in url?

It seems that the problem was on my side, because now it works, maybe it was some typo ot smth else. Sorry for bothering, I think we can close the issue.

Thanks for the update. Will close this one after checking against new connection string parser.


Remove spa mode by default

Currently the panel is configured to always be in spa mode, with no ability for the developer to override that.
Now you can set spa mode when you configure other stuff in the panel like so:
KnowledgeBasePanel::configureUsing(
            fn (KnowledgeBasePanel $panel) => $panel->spa()
);

Technically this is a "breaking" change as anyone who updates will have spa mode turned off until they manually enable it.

Ah good catch, thanks for the PR. Merging.


KinematicBody2D and move_and_slide with no velocity causes wrong movements

Godot version: 3.1
OS/device including version: Windows 10
Issue description:
When moving a KinematicBody2D using move_and_slide(): If it hits another KinematicBody2D that is using move_and_slide(Vector2(0, 0)), it push it. The collider should not be moved on impact, it feels like the physic engine glitch and tries to replace bodies causing a body that should not move to move.
Steps to reproduce:
Basically:

Create two KinematicBody2D with collision shape (one circle and another one with rectangle)
Attach scripts to them
use _physics_process to move_and_slide() the rectangle one into the second one
use _physics_process to move_and_slide(Vector2(0, 0)) the second one

Minimal reproduction project:
Minimal project here: https://github.com/T4g1/gd-test/tree/issue_kinematic
Workaround: Simply check the velocity length applied to any body for value equal to zero and don't call move_and_slide on bodies that should not move if the velocity is null.

I am not sure if I understand, but not calling it is up to you...

Nope, the second body isn't pushed anymore.


PREreviewer workflows A and B

PREreviewer workflow as presented by @elena-herrera:

My comment:
Here I think there are two workflows: A) The general PREreviewer workflow, which is when a PREreviewer submits a rapid review and possibly a long-form review to a preprint that is published on OPS-based preprint server independently of it appearing as having a request for feedback or not. This would mean establishing a direct stream of reviews with the preprint server similar to what currently happens on bioRxiv/medRxiv right now e.g., https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>583v1, https://www.medrxiv.org/content/10.1101/2<IP_ADDRESS>25460v2. SciELO would NOT activate this workflow. B) The responder to feedback PREreviewer workflow, which is when a PREreviewer filters for and finds on PREreview a preprint published on OPS-based servers for which the author has solicited feedback. Once they submit a rapid review and possibly a long-form review, notification(s) is/are sent to the preprint server who requested that feedback so that 1) that review can be linked/displayed alongside the preprint and b) the authors can get an email notifying them that someone has reviewed their preprint with links to the reviews.

@dasaderi: I share with you a couple of new diagrams, according to your comment, I consider that in this case, the most viable option is option B.

This looks good. Thank you, @elena-herrera.


gretty.baseURI returns <IP_ADDRESS>:8080 instead of localhost:8080 for Jetty9 server

Hello,
I'm writing some IntegrationTests and I noticed that the gretty.baseURI variable changed from returning http://localhost:8080 when using tomcat7 to http://<IP_ADDRESS>:8080 when using jetty9.
Using open("/") correctly returns http://localhost:8080/
Not sure if this is intended? Or a bug? Or related to configuration on my side? I couldn't find any similar topics on this problem, hence this post.
Thanks,
Joachim

I'll have a look at the problem.

I confirm, it is localhost under tomcat7 and <IP_ADDRESS> under jetty9. Looking further...

Fixed in Gretty 1.2.1-SNAPSHOT.
Release 1.2.1 is coming soon.

Gretty release 1.2.1 is out, please test.

Hello,
This is not working correctly. Thanks for the quick response.
Thanks,
Joachim

Not working correctly? Could you, please, give more details?

Woops, sorry! Monday morning... :)
Edited response: it IS working correctly.

I'm happy to hear that :+1:


RSA encrypting data which is larger then the key causes an uninformative error message

Using RSA with large blocks of data seems to be a common issue. Some wrappers handle this by splitting the data into smaller blocks and encrypting every block separately. But since RSA isn't intended to encrypt large blocks of data this won't be implemented in this wrapper. (Better combine RSA with something like AES if you need features of both worlds.)
At the moment (RELEASE-0.3.2) the error message is:
 error: Error Domain=MIHOpenSSLErrorDomain Code=67522668 "OpenSLL internal error! (Code=67522668,Description=error:0406506C:rsa routines:RSA_EAY_PRIVATE_DECRYPT:data greater than mod len)" UserInfo=0x170275700 {NSLocalizedDescription=OpenSLL internal error! (Code=67522668,Description=error:0406506C:rsa routines:RSA_EAY_PRIVATE_DECRYPT:data greater than mod len)}

But it would be more informative if it would be something more descriptive.
Writing some sample and/or wiki page on how to use AES and RSA in combination would be a good idea too.

Related issues: #23, #17

Hi Michael,
Can you let me know how to use RSA in combination with AES in current MIHCrypto ios library?

There is no automated way, but it's quite simple.
A does: Generate a random key for use with AES
B does: Generate a private/public key pair for RSA (see MIHRSAKeyFactory)
A does: Download the public key of A (it's up to yours how to transport the key, maybe via HTTP?)
A does: Encrypt the generated AES key via the public RSA key of B (see MIHRSAPublicKey)
A does: Send the encrypted AES key to B
A does: Encrypt the data with the shared AES key and send it to B (see MIHAESSymmetricKey)
B does: Receive the data and decrypt it with the shared AES key (see MIHAESSymmetricKey again)

Thank you for your detailed instructions.


how to make the generated text always end with a complete sentence？

I find that when I generate text on a web page, the endings are all one complete sentence, starting with "." but when I use the api to generate it, it always ends with an incomplete sentence. I have changed "global_settings.generate_until_sentence = True" in the api, because I find that the request in the web page is "True" here but the api defaults to "false". But I found it didn't work. So I would like to know: how can I make the api generate text that always ends with a complete sentence.Can anyone answer my question? Thanks
Translated with www.DeepL.com/Translator (free version)

I see no bug here. Setting the generate_until_sentence to True does reflect on the request sent to the server when fed to the high_level.generate or high_level.generate_stream.
Note that it will continue sentence only if a period is actually found in the 20 tokens after the end. It means it is affected by context, preset, biases, bans, etc.
If you see an issue, it is likely incomplete copy of the settings on your side. For a deterministic comparison, set the top_k to 1 on both, and you should see the exact same content if both settings are the same.

Thanks for the answer! My problem is solved, I double checked the "preset" parameter in the api and the parameter in the web request and found the difference between them. Finally I found that it was the "repetition_penalty" that was affecting the output. I used to think it had no effect. When I set the "repetition_penalty" from the default "2.25" to "1.148125", the output text starts with The output text ends with a complete sentence.
Translated with www.DeepL.com/Translator (free version)

It seems there is an obscure scaling done on repetition penalty, adjusting the value following 0.525*(X - 1)/7 + 1 (with X previous rep pen - formula extracted from minified JavaScript code). Seems kind of weird for it to exist frontend-side and not backend-side.
A fix is coming along with new sanity tests checking compliancy instead of just "nothing is broken".


Exclude description sections of automations.yaml (entities noted in comment sections)

Problem: Currently Watchman also finds and lists entities which are used in the comment sections of automations. This triggers false positives - and makes (based on the intensity of individual documentation/commenting) using this basically absolutely great integration a bit useless. 😞
Feature Request: Ignore all entites from the description: sections of automations.yaml
Example:
+--------------------------------------------------------------+-----------------+--------------------------------------------------------------+
| Entity ID                                                    | State           | Location                                                     |
+--------------------------------------------------------------+-----------------+--------------------------------------------------------------+
| group.anwesenheit_zuhause                                    | missing         | automations.yaml:1575,3896,4151,8725                         |

Actual automations.yaml snippet:
- id: 'XXXXXXXXXXXXXX'
  alias: Automation
  description: '...
    ...
    - Von "group.anwesenheit_zuhause" (state: home|not_home) auf "zone.home" (numeric_state:
    0|!0) umgestellt
    ...'

This should remove false positives massively. Looking at some (former) issues and reports, plenty of those findings for others too.
Manually setting those entities on the ignore list is only workaround - if at all.

ignore everything with example: domain.entity_id from /config/custom_components (example:  as keyword) (again: https://github.com/dummylabs/thewatchman#ignored-files-option-example is just a workaround for this)

This part is pretty much same as  https://github.com/dummylabs/thewatchman/issues/56

This also affects automation blueprints.
input:
power_sensor_1_entity:
name: Power Sensor 1
description: This is the main power sensor that will be used to measure load (e.g. sensor.main_meter_power)
selector:
entity:
filter:
- domain: sensor
device_class: power

In version 0.6.4, single-line descriptions will be excluded from parsing. As far as I can see, multiline descriptions are not prohibited in YAML configuration, but they are not encouraged by the Home Assistant UI. For example, in the automations editor, they are collapsed into a single line when displayed or updated via the UI.
Supporting multiline descriptions in parsing requires significant changes, we might address this later.

I really like the recent work you are putting in this integration.
Looking forward to see the improvement running 0.6.4. Any estimations when it will be released?


Doesn't work avec ReactNative 0.41

Hi,
I tried this react native module but it doesn't work with react native 0.41.
How can I do?
Sincerely,

This package is not compatible for RN 0.40+. see #78
Use RN 0.39

Will you upgrade it as soon as possible?

Will you upgrade it as soon as possible?

Anyone that have one PR merged, become a contributor.
But to merge PR needs to be a collaborator.

Published https://github.com/sbugert/react-native-admob/releases/tag/v1.2.0
Please feel free to ping me if anything is wrong.


Remove --host from cargo {publish,search}

Some usage of --host was removed from https://github.com/rust-lang/cargo/pull/10145 but as https://github.com/rust-lang/cargo/pull/10145#issuecomment-1013462753 points out there's a few more locations where --host has been deprecated which should be removed.

@rustbot claim


Add helm chart installation in circleci

This pull request adds helm chart installation in circleci config file.

lgtm


Reddit login support

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm requesting a site-specific feature
[X] I've verified that I'm running yt-dlp version 2023.03.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
United states
Example URLs
https://old.reddit.com/r/GenZedong/comments/12fujy3/based_hasan/
Provide a description that is worded well enough to be understood
Currently the site lacks of login option for downloading private/quarantined videos
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--username', 'PRIVATE', '--password', 'PRIVATE', 'https://old.reddit.com/r/GenZedong/comments/12fujy3/based_hasan/']
[debug] User config "C:\Users\japri\AppData\Roaming\yt-dlp\config.txt": ['--downloader', 'aria2c']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[17ba4343c] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg n6.0-7-gadb4688bfb-20230316 (setts), ffprobe n6.0-7-gadb4688bfb-20230316
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.2
[debug] Proxy map: {}
[debug] Loaded 1810 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: c6e73ff15a5c05d8938eb5d9bf1f38089f67b13671be1b4fa637fead35f217cd
yt-dlp is up to date<EMAIL_ADDRESS>WARNING: [Reddit] Login with password is not supported for this website. Use --cookies-from-browser or --cookies for the authentication. See  https://github.com/yt-dlp/yt-dlp/wiki/FAQ#how-do-i-pass-cookies-to-yt-dlp  for how to manually pass cookies
[Reddit] Extracting URL: https://old.reddit.com/r/GenZedong/comments/12fujy3/based_hasan/
[Reddit] 12fujy3: Downloading JSON metadata
ERROR: [Reddit] 12fujy3: Quarantined subreddit; an account that has opted in is required. Use --cookies-from-browser or --cookies for the authentication. See  https://github.com/yt-dlp/yt-dlp/wiki/FAQ#how-do-i-pass-cookies-to-yt-dlp  for how to manually pass cookies
  File "yt_dlp\extractor\common.py", line 694, in extract
  File "yt_dlp\extractor\reddit.py", line 193, in _real_extract
  File "yt_dlp\extractor\common.py", line 1154, in raise_login_required

Use --cookies-from-browser or --cookies for the authentication. See  https://github.com/yt-dlp/yt-dlp/wiki/FAQ#how-do-i-pass-cookies-to-yt-dlp  for how to manually pass cookies

Or are you specifically asking for username/password support?


Please do not share the solutions

I would not recommed you to share the problems solutions of the all courses

the course certification will be taken also by people which dose not know anything about machine learning and will get a certification and will share it in the CVs and in Linkedin
boasting about deep learning certifications

As second inside the course you signed up a document in which you can not share the code solutions

please do not share more solutions or i will send your link to cursera and the repository will be closed.
so stop it.

thank you.

@frankbass3  This is so immature. You must understand that scope of coursera solution sharing must & should only limit to Coursera Discussion threads. It has no say over if a student save his work in github. @Kulbear has not told anyone to look in to his code or repository.  Are you aware that Coursera assignment notebooks will not be accessible once course schedule is over & we need to raise a coursera ticket to get our code back? We are living in knowledge sharing era. If some one copies code & gets certificate, then he will never master skills, so he will be already at loss. Just having certificate has no merits. I follow others & many people follow my codes, just to understand the variations/share ideas, so please understand that that is also a form of knowledge sharing.  I had to be harsh because, I absolutely don't tolerate who threaten the good people publicly by using the words "stop it" and so on.

i think this is over the rules of coursera.
Il Mar 28 Nov 2017, 17:08 meethariprasad<EMAIL_ADDRESS>ha
scritto:

@frankbass3 https://github.com/frankbass3 This is so immature. You must
understand that scope of coursera solution sharing must & should only limit
to Coursera Discussion threads. It has no say over if a student save his
work in github. @Kulbear https://github.com/kulbear has not told anyone
to look in to his code or repository. Are you aware that Coursera
assignment notebooks will not be accessible once course schedule is over &
we need to raise a coursera ticket to get our code back? We are living in
knowledge sharing era. If some one copies code & gets certificate, then he
will never master skills, so he will be already at loss. Just having
certificate has no merits. I follow others & many people follow my codes,
just to understand the variations/share ideas, so please understand that
that is also a form of knowledge sharing.  I had to be harsh
because, I absolutely don't tolerate who threaten the good people publicly
by using the words "stop it" and so on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Kulbear/deep-learning-coursera/issues/22#issuecomment-347572991,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAW77a_gYC9nkf7Y7jZK5EfyjL5RlOyuks5s7C_ngaJpZM4Qta-N
.

@frankbass3 I understand your concerns and @meethariprasad explained some of my thoughts (but not all). I original post some notebooks here just for my friend who is interested in related research BUT NOT going to take the Coursera courses. I've working on deep learning for a long time so basically I'll have a quick look on the course and complete the assignment in maybe just a half hour. So originally I pushed the code very early, that's probably why this repo got a lot of attention. There are some people, probably, use the solution to pass the course, as @meethariprasad mentioned, they will benefit nobody. Also, in order to avoid such cases, I didn't have a plan to upload notebooks and quiz for CNN course (and the RNN course) recently. There are hundreds of repo contain the solution for the courses but it seems mine will be presented on the top of search result.
You can never stop cheaters, but a mature person knows what to do to benefit himself/herself/?self.


Add trailing text to indicate approximate dates for work experiences

Context
Update manage interface to indicate if work experience start/end dates have been flagged as 'approximate' by candidate.
Link to Trello card
https://trello.com/c/p5bxyt7C/3567-work-history-mark-approximate-dates-in-manage
Things to check

[X] This code does not rely on migrations in the same Pull Request
[X] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[X] API release notes have been updated if necessary
[X] This code does not rely on the addition/removal of Azure config environment variables in the same Pull Request
[X] New environment variables have been added to the Azure config

Given the duplication can this code also be extracted to a reusable private method.

Minor comments inline, otherwise looking good!


Improve medication result sorting

[ ] Sort options by best fit to search term (not alphabetically)
[ ] Add warning level highlighting and icons to search (should also think about short descriptions) covered by #441

This is deprecated as we want to change the search logic from searching to filtering (see #441)


add coreif.java

@Chirag-Mathur  @Monik09 please review it.

@Chirag-Mathur @Monik09 please review it


Solution to Day 20 with go

Hi,
I solve the exercise of day 20 with go, it is on the hacker rank page.
I could not found exercises in go in days 15, 16, 17, 18, 19 in the hacker rank page.
Hope it helps.

@gmgalvan , it's already assigned to someone else. you can looks into 26,27,28 and let me know if they are available to be solved will assign them to you.


Update sbt-version-policy from 2.1.3 to 3.2.0

About this PR
📦 Updates ch.epfl.scala:sbt-version-policy from 2.1.3 to 3.2.0 ⚠
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.epfl.scala", artifactId = "sbt-version-policy" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.epfl.scala", artifactId = "sbt-version-policy" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-major, version-scheme:early-semver, commit-count:1

Superseded by #1138.


after assertions

@rultor release, tag is 0.21.0

@rultor release, tag is 0.21.0

@yegor256 Done! FYI, the full log is here (took me 9min)


Time to publish

Hey @crn3 how about we turn on GitHub pages and publish the game?

@crn3 maybe we should review the project files and ensure we are good to go. Can you create an issue and complete this task please?


The "fb-root" div has not been created, auto-creating

I am getting this warning after installing meteor-blog. The sad part is that this warning is on all the pages on the site and not just blog posts. How can this be fixed?
Thanks. :)

This is an error you'll see on many, many websites that load the Facebook JS library. It's only a warning and has never caused me any harm.
While the absence of the div does not cause harm, my fear is that if your app already includes the div, and then the blog package includes the div, then there will be two divs with the same ID. So I've left it out.

Thanks @hellogerard :)
I was wondering why does it appear on every page? Is the facebook JS library loaded on pages other than blog pages too?
Is there a way to limit the addition of fb js lib to only blog pages?
Thank you!

I've done this to get over it:-
// FB Like/Share buttons
if ($('#fb-root').length > 0) {
	(function (d, s, id) {
		var js, fjs = d.getElementsByTagName(s)[0];
		if (d.getElementById(id)) return;
		js = d.createElement(s); js.id = id;
		js.src = "//connect.facebook.net/en_GB/sdk.js#xfbml=1&appId=12345678910111&version=v2.0";
		fjs.parentNode.insertBefore(js, fjs);
	}(document, 'script', 'facebook-jssdk'));
}

The "fb-root" div has not been created, auto-creating
Same here.

I'm seeing the same issue.
@craigs100 Do you mind if I ask where you placed that bit of code. I've tried inserting it into multiple places but I can't seem to solve the issue.

I am also facing same issue.
"The "fb-root" div has not been created, auto-creating"


contributor type Lead project centre should be only Lead project entity?

In order to make CG Core usable outside CGIAR, the contributor type "Project Lead Centre" can be made more generic by being just "Project Lead Entity"

Looks good to me. :+1: Seems appropriate for the field name to be more generic. In the schema itself we can give a description that this indicates the center, institute, organization, etc that is leading the project.


Still getting 401 and 429 errors

Hi!
I installed the node set directly from github for v 0.1.4. I'm still getting a 429 and 401 errors on status.
Am I doing anything wrong?

Hi there, thanks for creating an issue. Can you please provide some screenshots or copy the error messages into this issue? That way I can better check the issue. This issue should have been fixed upstream - at least nobody complained about it. https://github.com/d4v3y0rk/ffpass-module/issues/11#issuecomment-1012867950
How did you install the node set from github? Did you just import the source code as zip? I never actually tried that so I don't know if there might be issues related to that.
Also I just updated the version on the node-red website: https://flows.nodered.org/node/node-red-contrib-ffpass, maybe also try using that version.

I'm seeing the same thing. Stopped working a few days ago. But the FordPass app still works.

Yeah - I also left an issue on ffpass: https://github.com/d4v3y0rk/ffpass-module/issues/16

Here are some screen shots regarding the 429 and 401 error which I have also


[3531] Amended admin users to be less involved

Context
Admin user are omnipotent
Changes proposed in this pull request
Amended admin users to be less involved
Guidance to review
Admin users are basically omnipotent and serves a different purpose.
If an admin user is associated to organisation then that is removed.

this removes the user associations provider

If an admin user is associated user notification then that is removed.

see the above
if remained then there is discrepancies with expectations as business rules are applied

An admin user is not the same as a normal user, so will not have the exacting functionality.
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Remove all DfE users / admins from providers


Migrate Tealium article from Help Center

migrate tealium doc from help center
migrate tealium doc from help center

Amplitude Developer Docs PR
Description
An integration guide for Tealium was posted in the Help Center. Migrating it to Dev Docs for consistency.
Deadline
No rush
Change type

[ ] Doc bug fix. Fixes #[insert issue number]. Amplitude contributors include Jira issue number.
[ ] Doc update.
[x] New documentation.
[ ] Non-documentation related fix or update.

PR checklist:

[x] My documentation follows the style guidelines of this project.
[x] I previewed my documentation on a local server using mkdocs serve.
[x] Running mkdocs serve didn't generate any failures.
[x] I have performed a self-review of my own documentation.

@amplitude-dev-docs

Thanks @justin-fiedler. Not sure why Spell Check is hitting on code samples.
Let me dig in to CSpell to see if I can sort that out.


Add optional flush param when storing in MetaStore

Added a new method store_and_maybe_flush in MetaStore, which gives you an option to flush the config changes to disk.
The previous store method behaviour is not changed. It internally calls store_and_maybe_flush method, stores the config and flushes to disk.
This patch fixes a bug in fork. Earlier, we were flushing the target config before actually creating a fork. If the fork failed, MetaStore would have invalid data. Now, we store the config, without flush, create the fork. Iff successful, flush the target config to disk.

We still have one test to fix it seems


Rails 8 support

Version: git, master branch

Could not find compatible versions

Because every version of devise_token_auth depends on rails >= 4.2.0, < 7.3
  and rails >= 4.2.0, < 7.3 could not be found in https://github.com/rails/rails.git (at main@429f400),
  devise_token_auth cannot be used.
So, because Gemfile depends on devise_token_auth >= 0,
  version solving has failed.

I merged into a master a version that supports it, but I won't release a version yet because there is no official release of rails 8 (just release candidate)

Rails 8 released ... :-)


cleanup redundant code in MultiControlledX, use MultiControlledPauli

partially fixes #1131

In the linked issue, it's proposed to beef up MultiControlledPauli into a MultiControlledU and (then?) do the migration. How much extra effort would it be to do it in this direction? It's a shame to get rid of a readable, qualtran-native decomposition.

That should be easy, I can do that first

handled in #1155


Weave Scope not starting

[root@dockerHostCentOS7 ~]# uname -a
Linux dockerHostCentOS7 3.10.0-229.11.1.el7.x86_64 #1 SMP Thu Aug 6 01:06:18 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[root@dockerHostCentOS7 ~]# docker version
Client:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 02:19:43 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 02:19:43 UTC 2015
 OS/Arch:      linux/amd64

[root@dockerHostCentOS7 ~]# docker info
Containers: 8
Images: 89
Storage Driver: btrfs
 Build Version: Btrfs v3.16.2
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.10.0-229.11.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
CPUs: 2
Total Memory: 1.066 GiB
Name: dockerHostCentOS7
ID: MYTC:UAFQ:UKFU:UTRY:HFDU:O6IK:BH3C:65PJ:SJPA:5P5B:5GZE:IOOX
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
[root@dockerHostCentOS7 ~]#

Weave Scope installation, ( Weave DNS is already working on the same machine )
[root@dockerHostCentOS7 dockerBckUps]# cd /usr/local/bin/
[root@dockerHostCentOS7 bin]# curl -O https://github.com/weaveworks/scope/releases/download/latest_release/scope && chmod a+x /usr/local/bin/scope
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   381    0   381    0     0    235      0 --:--:--  0:00:01 --:--:--   235
[root@dockerHostCentOS7 bin]# scope launch
/usr/local/bin/scope: line 1: syntax error near unexpected token `<'
/usr/local/bin/scope: line 1: `You are being redirected.'

Hi there; thanks for the bug report.  We recommend you use wget instead of curl, but if you insist, the command is:
sudo curl -L https://github.com/weaveworks/scope/releases/download/latest_release/scope -o /usr/local/bin/scope
sudo chmod a+x /usr/local/bin/scope

Thanks, Tom


Update How_to_use_MorphTargets.md

Added documentation and playground example for accessing morph targets from a glTF file.

All good! Thanks


How to override/overwrite twill blade templates in our theme view folder?

I'm try to add logo in Admin Login Blade and admin internal pages.
But got no way to override the templates.

Hi @vrdvishwas,
You can override any template under resources/views/vendor/twill. I would suggest to only override the _title partial if you're trying to add a logo there.

Thanks It works.


Loading metadata returns an error if key does not exist

Loading metadata should return Ok(None) for files that are not stored instead of an Err().

Closed in b6dc5c2b040aec1e0f0607f027a393ef13738b31


Add ENABLE_BUILT_IN_PLUGINS environment variable

Hey Guys,
I've added some lightweight logic to the docker-entrypoint.sh file to allow easy configuration and usage of the plugins that come pre-packaged with the Flink distribution. For our use-case specifically we need the S3 Filesystem plugin for our AWS ECS-hosted cluster.
To use the new variable, you provide a list of all the jars you want moved from the flink/opt folder to the flink/plugins folder, delimited by semicolons. So, for example:
ENABLE_BUILT_IN_PLUGINS=flink-s3-fs-presto-1.9.1.jar;flink-s3-fs-hadoop-1.9.1.jar

If you don't provide the variable, nothing happens.
If you provide the variable but point to a jar NOT present in flink/opt then the container will fail to start.
I would really appreciate a speedy review and merge of this as it is currently blocking us. I am ready to make any changes required at the drop of a hat. Just let me know.
Tom

@patricklucas when do you think we'll see the updated entrypoint get deployed to the official images on Docker Hub? I see they were updated recently but they're still containing the older version of the script.

@Jamalarm check out the issue I linked earlier today (docker-library/official-images#7398). Once that's merged—typically within a day—it usually doesn't take long for the updated images to become available.


Update README.md for those new to PRs

I am documenting my process to understand how a repository works. I am currently making a pull request based of changes I made to a commit.

huh


Classes implementation

Some working prototype

Good team work.
The very next thing to add is initial conditions.


Transitive, unused dependencies are downgraded

When the TOML file contains dependencies that aren't declared in the build file, but are pulled in as a transitive dependency the version in the TOML file might be downgraded.
The root cause here is that the report.json from the dependency updates plugin will put transitive dependencies as "current" so it seems (e.g. it doesn't check dependency versions of dependencies which makes sense). Because that dependency is then declared in the TOML file it's also not removed, even though it is unused from the perspective of declared dependencies.
When merging the dependency versions with the TOML file the dependency then gets the incorrect "current" version replaced. This would then also impact any existing version groups if that dependency was using a version reference.
I think a situation like this should be treated as "unused" so that it would be removed from the TOML file unless any keep entries prevent that, in which case the original entry should be retained. The trigger could be detecting that a current entry from the incoming report has changed versions vs the TOML file.

Unfortunately just checking if the version mismatches is not sufficient because a version in the catalog can be used and be transitively be updated. In that case we definitely don't want to have it filtered out as it's actually being used.
It looks like the best we can do here is a warning similar to what is done for exceeded: proceed with the update as reflected in the dependency report and tell the user what happened and how to fix it.


NASCAR update truck series and account for missing data

truck series has changed names as of end of 2022 season.  this is an interim update to reflect the new name, while a layout redesign takes place for the next version

closing this to add in time TBD fix


Avoid drag handle repaint due to height change.

The editor itself still glitches — I'll look at that separately.


Question: Is there a way to read just a scalar value from the query?

I'm trying out Fumble at the moment for a small project and tried reading just a scalar value from the DB:
SELECT COUNT(*) FROM Test.
But then I don't know how to get the resulting number (which does not have a column name) with the SqlRowReader.
I for now use a workaround (naming the resulting count as a column with AS in the statement). Just wanted to know if there's a shorter way.
Thanks for the great library!

  [<Literal>]
  let countAuthors =
    """
    SELECT count(*) from authors
  """

  member this.countAuthors  () =

    conn
    |> Sql.connect
    |> Sql.query countAuthors
    |> Sql.executeNonQuery


Initialize scripts

Use run-base and bootstrap to install dependencies. Start script copies
$HOME from bundle and source dnx dependencies from it. Starts a server
on 8080.

:+1:


Feedback Request

Created this pr for feedback.

@arshad-6093
Thank you for the solution. I'll add comments here since it is easier to review your changes.
However, I had meant opening a PR from the master branch to another branch so that the diff could be displayed on Github. But this is OK.
I have some questions:

What performance implications do you foresee with having the entire cache store inside of a TVar? How can that be optimised?
What are the disadvantages of using String as your cache key? Can another datatype be used? How would you design it?
What happens to the cleanupCache thread once the program exits? Does the behaviour remain the same if running main from the REPL?

@asheshambasta Thank you for your review.

If the entire cache store inside of a TVar, any read or write operation on the catche involves locking the TVar which holds the entire Map. Incase of multiple threads try to read or write simultaneously, they will block each other as STM enforces atomicity. And as cache size increases, Map.lookup will become slower. In optimization point of view, instead of storing in single TVar, we can use a Sharded Cache for scalability and efficiency. We can split the cache into multiple shards (each a TVar) based on a hash of the key, allowing threads to operate on different shards concurrently with reduced contention.
type Cache = [TVar (Map.Map String (Categories, UTCTime))]

Comparison and hashing operations will be slower in String than Text or ByteString. And also it lacks type safety too. Using a custom data type with derived Ord or Hashable instance is efficient than String.

data CacheKey = CacheKey
  { keyName  :: Maybe String
  , keyLevel :: Maybe String
  } deriving (Eq, Ord, Show, Generic)

instance Hashable CacheKey

For improved performance with Hashed keys, we can use Data.HashMap.Strict .
type Cache = [TVar (HashMap.HashMap CacheKey (Categories, UTCTime))]

cleanupCache  thread created with forkIO terminated when the main thread exits. But in REPL,  cleanupCache  thread might continue running because the REPL does not terminate the process when main finishes. Using withAsync from Control.Concurrent.Async or bracket will ensure proper cleanup.

withAsync (cleanupCache cacheTVar) $ \_ -> do
    putStrLn $ "Running server on http://localhost:" ++ show port
    run port (app cacheTVar)

Question 2 was relatively straightforward for me. For questions 1 and 3, I took the time to research and better understand the nuances. Thank you for providing these questions. If you have additional feedback or questions, I’d be happy to address them!


soroban-rpc: Remove getEvents.endLedger param

What problem does your feature solve?
In the getEvents method, endLedger and pagination.limit conflict somewhat, and having both is unnecessary.
What would you like to see?
We should remove endLedger, and just use startLedger combined with pagination.limit.
So that clients can detect when they are out-of-bounds, we should also make sure that startLedger errors if it is:

< oldest ledger this node has stored
> latestLedger

This is a very breaking change, so we'll need to update all the clients at the same time.

endLedger and pagination.limit conflict somewhat, and having both is unnecessary.

What is the pagination limit?
If I wish to iterate over all events between two ledgers, how do I work out what the pagination limit should be too get them all?
Secting a start ledger and page limit is not particularly intuitive to me. My application probably doesn't care how many pages there are.

If there are more than 10,000 events, will this mean if you try and get all events between two ledgers where more than 10,000 events occurred between them, it might appear like you've gotten all the events when in fact you've only gotten the events that fit in the first 10,000?


Does esdoc es7 plugin have a problem with decorators that are further parameterized?

I have a decorator that takes additional parameters, e.g.
@deco({fancy: true})
export default class foo {}

Here, deco takes additional arguments and will return a decorator that is then used by the babel runtime, e.g.
foo = (0, _deco.deco)({ fancy : true })(foo) || foo;

Yet, and in spite of actually using the es7 plugin, it will still warn 'error' about it, e.g.
error: could not parse the following code. if you want to use ES7, see esdoc-es7-plugin(https://github.com/esdoc/esdoc-es7-plugin)

Or is it the export default, I can see that you have a TODO for that in the es7 plugin, e.g.
 99     ExportDefaultSpecifier: [], // todo

And, in fact, it is a CallExpression:
[ Node {
    type: 'Decorator',
    start: 797,
    end: 827,
    loc: SourceLocation { start: [Object], end: [Object] },
    expression:
     Node {
       type: 'CallExpression',

Can it be that espree has a problem with such constructs?

I can not reproduce the error.
{
  "source": "./src",
  "destination": "./doc",
  "plugins": [
    {"name": "esdoc-es7-plugin"}
  ]
}

@deco({fancy: true})
export default class foo {}

Result:
$ esdoc -c esdoc.json
badge.svg
identifiers.html
index.html
class/src/foo.js~foo.html
file/src/foo.js.html
./css
./script
./image
script/search_index.js
source.html
==================================
Coverage: 0% (0/1)
==================================

Post your code in order to reproduce the error.


test-branch/execute-job/quoted-authorization/494a2cb9-b8e9-4c56-afd7-1ffdb39c39b6

PR for testing 03dae631e00b73702d3f00b4e96a3ff92a49652e

/canonical/self-hosted-runners/run-workflows 03dae631e00b73702d3f00b4e96a3ff92a49652e


trigger-control: init at unstable-2023-06-18

homepage: https://github.com/Etaash-mathamsetty/trigger-control
description: Control the dualsense's triggers on Linux (and Windows) with a gui and C++ api
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

you are at least missing the entry in pkgs/top-level/all-packages.nix

Done in the latest push.
Tested the pkg on my own overlays, and forget about pkgs/top-level/all-packages.nix 😂

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2363


Use new enum string APIs

libbpf 1.0 has 4 new APIs for treating enums as strings:

[ ] libbpf_bpf_prog_type_str();
[ ] libbpf_bpf_map_type_str();
[ ] libbpf_bpf_link_type_str();
[ ] libbpf_bpf_attach_type_str();

These can possibly be used in our maps that map types into strings.

Being tackled by https://github.com/aquasecurity/libbpfgo/pull/372.
The libbpf_bpf_link_type_str wasn't managed since LinkType is not 1:1 with libbpf. It needs to be handled in a different task.


Download error: Unable to connect to the remote server

Hi , i tried to install BetterDiscord but im getting some errors at installer , any solution for this ?

Did you try installing on the Desktop

Did you try installing on the Desktop

Tried everywhere , on desktop , in C:\ , in D:\ , in downloads , with admin rights and without

Then try visiting the BetterDiscord server for assistance


Broken on Version v1.6.3?

Hi! For some reason all my files are auto aligned, no matter which setting I use. I don't remember enabling anything new besides the auto update.
Using plugin version 1.2.2

Indeed, Obsidian 1.6.3 introduces its own RTL support and the obsidian-rtl plugin is mostly redundant.
I was in a dilemma whether its little added value (mostly adding per-file settings) is worth its maintenance, so it makes me happy to hear one user noticed :smile:

Hey! I was rather hoping you would continue support, as Obsidians RTL is Paragraph dependent, rather than global, as yours is... ant its causing issues for me with Callouts OBV. I am just one person but I could ask and hope...??

Hello @esm7 , Your plugin is unmatchable in comparison to the Obsidian built-in feature. I want to turn their feature off but I am not sure how to do so. I was so happy with your plugin and many thanks for that!

I don't think there's a way to turn off Obsidian's new built-in RTL support, but I think it's a great step forward, and this plugin will just complement the built-in support with some added features.
I think these should be:

Assign notes to be LTR and RTL (not mixed) when required, like today.
Remember this setting per file like today.
Allow setting this via front matter like today.

Anything else I'm missing and should be in the plugin's 2.0.0 version?

I'm mostly here since I want all my files to be LTR, whereas the new Obsidian feature makes each paragraph separate, making everything look awful in my files which have mixed languages (see forum post here).

Anything else I'm missing and should be in the plugin's 2.0.0 version?

That being the case, I would like a per vault default if that's possible, so I don't have to go through and change all my files (unless this plugin does that already, setting files by default to LTR if not specified?).

That being the case, I would like a per vault default if that's possible, so I don't have to go through and change all my files (unless this plugin does that already, setting files by default to LTR if not specified?).

Good point, that's already the case now but I should keep in mind to preserve this behavior.

Your plugin was a crucial point in my decision to work with Obsidian.
Keeping points/bullets on the same RTL/LTR regardless of the first-word language is very important.
Otherwise, it is a real mess when points start to jump from side to side.
Also, having some notes as RTL and some as LTR is essential.

I'll work on it this week, hopefully it goes smoothly. I verified ahead of time with the Obsidian devs that the plugin will be able to override the default behavior but haven't got a chance to try yet.

I agree with all previous comments, in many cases it become a real mess when you can't decide the text direction by yourself. The ideal solution is to provide the ability to manually specify the direction of each paragraph like in Word.

Hi all, I did the changes required to support Obsidian 1.6.x, but since it's a very big overhaul to the code, it would be great if some of you could test it. I probably overlooked a few edge cases or more.
I created a branch with the new version here: https://github.com/esm7/obsidian-rtl/tree/v2.0
A build is attached as a zip file -- to try it, extract the 3 files to your VAULT_PATH/.obsidian/plugins/obsidian-rtl folder (best to back up the old plugin just in case).
@zoli -- as the biggest contributor to the code base, I'd love to get your impression on the updated code. I simplified it a whole lot, as detection by line is no longer necessary etc -- hope you'll be ok with many of the great things you did being no longer needed :black_heart:
Help appreciated :pray:
rtl.zip

Thank you very much! I've tested it and as long as I can see it working well.

Here's a related bug report I've submitted:
https://forum.obsidian.md/t/unicode-ltr-and-rtl-character-marks-do-not-work/84276
My idea is that resolving the above issue will let the user decide the text direction of each line by simply inserting the LTR or RTL marks in the selected lines or all lines in the chosen note.
I think this is a simpler, more effective approach and more stable because less maintenance required after future Obsidian updates.

Plugin is working great for me, no issues seen so far

Version 2.0.0 is now formally released, thanks everyone!

There is a problem, when pressing the home button on the keyboard which should take you to the start of the line, the curser is instead placed after the first character, and not before it.


Lua: Out of range error

Hello,
I am getting the following error:
Error executing lua callback: ...share/nvim/lazy/nvim-biscuits/lua/nvim-biscuits/init.lua:156: Invalid 'line': out of range
stack traceback:
	[C]: in function 'nvim_buf_set_extmark'
	...share/nvim/lazy/nvim-biscuits/lua/nvim-biscuits/init.lua:156: in function 'decorate_nodes'
	...share/nvim/lazy/nvim-biscuits/lua/nvim-biscuits/init.lua:206: in function <...share/nvim/lazy/nvim-biscuits/lua/nvim-biscuits/init.lua:206>

Thanks for the bug report. Could you maybe paste a code snippet or a link to a file I can use to try and reproduce this?


"error": {         "code": -32022,         "message": "Device limit on this license has been reached."

This problem occurs when the same code runs on different computers
I don't understand what the device limit means.

"device" mean your computer. That mean your new computer can not use the license

"device" mean your computer. That mean your new computer can not use the license

"device" mean your computer. That mean your new computer can not use the license

This is so inconvenient, is there any way to deal with this?

"device" mean your computer. That mean your new computer can not use the license

"device" mean your computer. That mean your new computer can not use the license

"device" mean your computer. That mean your new computer can not use the license

This is so inconvenient, is there any way to deal with this?

Or if I can change the device

@a1848580190 , you can contact our support team to reset device for your license.

I can change the device

ok ,thanks


asyncresolv won't build on Debian

asyncresolv in xDAQ uses -Werror but triggers unused-result warnings that terminate the build. It could be solved by setting CXXFLAGS=-Wno-error=unused-result if asynreslov didn't use the following construct in its configure.in:
# Warning options
CXXFLAGS="${CXXFLAGS} -Werror -Wall -Winline"

I propose that we change it to:
# Warning options
CXXFLAGS="-Werror -Wall -Winline ${CXXFLAGS}"

This way -W flags we can be overriden from the environment.

I agree with the bug, but I'm not convinced with the proposed solution as a first try. It will require patch to the sources and CXXFLAGS applied to the full xDAQ compilation. :-/
As it compiles without errors on CC7 and Archlinux, I would first try to investigate why the compilation fails on Debian. Maybe some hardening options such as FORTIFY_SOURCE are enabled by default. The error lies in a read() function call which is not usually marked as warn_unused_result.

As you mentioned in private, this seems to be indeed caused by FORTIFY_SOURCE. There is no way around it other than disabling -Werror=unused-result.
A solution would be to replace -Wall by the list of -Wxxx flags that it enabled when the library was written. This would respect the intent of the original developer. Another would be to drop -Werror altogether. After seeing this problem, I don't think that -Werror should be used in release mode anyway...
Patching configure.in is in any case needed.

Have you tried to set CXXFLAGS=-U_FORTIFY_SOURCE and/or CXXFLAGS=-D_FORTIFY_SOURCE=0  ?
Though, that might not be the best solution since it disables the functionality for all xDAQ pacakges. I agree with you, -Werror should not be used in release mode. Can you provide a patch for configure.in since I don't have an easy access to a Debian machine? Or a PR ?
Anyway, I'm curious about the output of g++ -Q -v <dummy>.cpp on Debian. Could you provide me the output of the command ? Maybe in a private discussion.

Fixed by #9.


Feature/dependency catalogs

What's new

Update Gradle Wrapper to 8.6
Migrate from dependencies.gradle to gradle/libs.versions.toml to reduce the need to recompile if versions are changed

🤨


[Enhancement Request] More options for adding to visuals/datapoints

Currently, when using the library, I am able to do minor items, but, it would be great if there were more options.  For example, I would like to highlight a single data point by either changing isn't color or some attribute to bring attention to a specific data point.  It would also be good if I could inject some HTML and/or an icon into the title of a visual.
I have built a discussion system for a project using power bi embedded and I would like to directly highlight or identify where comments are placed in the embedded report.  There is not an option to do this programmatically from JavaScript.

Or, if it was possible to append text to a title that is bold while the rest of the title is not.  That would be useful.  Right now, I can only update the entire text and the entire format.

Thank you for reporting this issue. We closed the issue because it's old.