Problem with sync of operations

When I run this JS file through Run in Webstorm IDE, I get a strange order of operations
var records = [];

console.log('hello start');

var sqlite3 = require('sqlite3').verbose();
var db = new sqlite3.Database(':memory:');

db.serialize(function() {
  db.run("CREATE TABLE lorem (info TEXT)");

  var stmt = db.prepare("INSERT INTO lorem VALUES (?)");
  for (var i = 0; i < 10; i++) {
    stmt.run("Ipsum " + i);
  }
  stmt.finalize();

  db.each("SELECT rowid AS id, info FROM lorem",
      function(err, row) {
        console.log('in for each loop: ',row.id, row.info);
        records.push({"rowid": row.id, "rowinfo": row.info});
      }, function(err, noOfRows) {
        console.log('completed each, rows:'+noOfRows);
      }
  );
});

console.log('before db close');
db.close();

console.log('hello end');

Here is the console output:
"C:\Program Files (x86)\JetBrains\WebStorm 11.0.1\bin\runnerw.exe" "C:\Program Files (x86)\Nodist\bin\node.exe" test.js
hello start
before db close
hello end
in for each loop:  1 Ipsum 0
in for each loop:  2 Ipsum 1
in for each loop:  3 Ipsum 2
in for each loop:  4 Ipsum 3
in for each loop:  5 Ipsum 4
in for each loop:  6 Ipsum 5
in for each loop:  7 Ipsum 6
in for each loop:  8 Ipsum 7
in for each loop:  9 Ipsum 8
in for each loop:  10 Ipsum 9
completed each, rows:10
Process finished with exit code 0
So the problem is that I have "hello end" before my "in for loop" logs which is just incomprehensible. Is the operations running in parallel or is there something wrong with my code? I would appreciate any help on this matter.

。。。poor English.. node runs asynchronous.and there is an event quene...I donnot know how to explain.feeling powerless to help.

The API documentation can be found here: https://github.com/mapbox/node-sqlite3/wiki/API
The problem lies with your code, if you wanted something to execute after calling db.close() you would pass a callback:
db.close(function () {
 console.log('hello end');
});

Most of node works with callbacks that take an error as the first argument, and the response/result of your operation as the second.

Asynchronous events are like saying to a friend "call me when you get
back." You have no idea when they will get back AND you are not going to
wait for them. The code inside db.serialize() is the part about call me
when you get back. The world doesn't stop while your friend is gone  and
your program doesn't either. It continues to execute what it can - and
that is why the "hello end" gets printed.
If you search for "javascript event loop explained" there are some
articles about this.
It is hard to explain even for native English speakers. :-)
On Wed, 09 Dec 2015 08:22:36 -0500, Suminzhang<EMAIL_ADDRESS>wrote:

。。。poor English.. node runs asynchronous.and there is an event
quene...I donnot know how to explain.feeling powerless to help.
—
Reply to this email directly or view it on GitHub.

This should be documented in the API. The callbacks in the legacy API are optional which implies (to me at least) that leaving them out should make it run synchronously..

This is now documented in the Wiki 🙂


Ci/fix-docker-names

fix makefile to use version package
try go releaser
Signed-off-by: Bobby DeSimone<EMAIL_ADDRESS>

This no longer publishes for PRs.


[suggestion] Make BotBase users to force add their config file to staging area (because they don't know that committing secrets are bad)

To make sure that pajeets aren't getting triggered when accidentally committed their secrets (such as API_ID, API_HASH, and BOT_TOKEN), I gitignored it and instead prompt users to copy the example file.

Yeah, that makes sense, thanks!


[GitHub Indexer] GitHub Indexer does not clean up properly after deployment

The GitHub Indexer job does not properly clean up its state if it is is deployed while it is running. This happens b/c the job stores its state in it's working directory, and the working directory changes on each deployment. Instead, the job should use one known location to store its state.

After deploying this fix, go to all environments and clean up old folders.


Added a simple utility for master election and pod creation.

cc @timothysc

@brendandburns are you just gating the whole master here?
cc @rrati

@timothysc this is only used to gate the launching of the scheduler, or the controller-manager.  See:
https://github.com/brendandburns/kubernetes/blob/docs/docs/high-availability.md#running-the-podmaster
for more details.
please take another look.
Thanks!
--brendan

Mostly LGTM, a few nits.

Comments mostly addressed, ptal.
Thanks!
--brendan

LGTM

cc @smarterclayton @jayunit100 @rrati
Once there we should validate post haste.


[Vue] Menu @select event no longer send selected item

Description
Hey there! 👋🏻
Since version 0.9.0, the @select event in the Menu.Root component no longer returns the selected item.
Reverting back to 0.8.0 makes the Menu work again.
Link to Reproduction (or Detailed Explanation)
Version 0.9.0 (with bug): https://stackblitz.com/edit/vitejs-vite-rzhfml?file=src%2Fcomponents%2FMenuBug.vue
Version 0.8.0 (without bug): https://stackblitz.com/edit/vitejs-vite-ajq8zw?file=src%2Fcomponents%2FMenuBug.vue
Steps to Reproduce

Go to https://stackblitz.com/edit/vitejs-vite-rzhfml?file=src%2Fcomponents%2FMenuBug.vue
Open the Console
Click on Open
Select any item
Notice the [] logged value.

Ark UI Version
0.9.0
Framework

[ ] React
[ ] Solid
[X] Vue

Browser
Arc
Additional Information
No response

Thanks for the notice. I took a look at the problem and your example works on the main branch again.
Btw, you accidentally installed vue 0.9 on the 0.8 example.

Btw, you accidentally installed vue 0.9 on the 0.8 example.

Ooops. 😅

It was fixed in https://github.com/chakra-ui/ark/pull/1906

Good to know!
Thanks.

You can use the main branch instead of v0.9 right now. There are so many helpful changes you'll notice in an instant.
You can tell me about new problems thanks to this ;D


Removing kuadrantctl install & uninstall

Removes:
kuadrantctl install
&
kuadrantctl uninstall
Patches docs to remove refs. Points users at single-cluster quickstart as a means to get a working Kuadrant local cluster.

@azgabur FYI ^


Passed generic not giving exact return type in callbacks

🔎 Search Terms
"exact return type", "generic return type", "return type excess property checks"
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about exact types, return types, generics and excess property checks

⏯ Playground Link
https://www.typescriptlang.org/play/?#code/GYVwdgxgLglg9mABABwIYCdUFsDOAxcCAHgBUA+ACjUywC5ESBKRAbwF8BYAKFElgUQQARgUilKw+hWYBeMg2btu3KAE9kAU0QBZVSXVaZrbolOJgcOPRxR0MMAHNunLtwD0bxAEEciAO5aqAA2QYgA1mBwfigY2L4YWrYaqFAaACaIqL4aAB6o0Ihqmr5+MFAAFogOGmAadhA43NRxosS6+pqULOaW9ADkQhh9ADSIg+j9gwBefWyMylweiABCIFCF5TC+W4iR6xVaEFlafuU1G1o42FrVtfWIOyA46ZnxiOgaUCDoSEUa3MJWkR2gZKNJEHJEBQWCYzBYrIgBkNhrDTONJqgZs5GPNXItPKt1jBgIgAJKIXLIIIwCBlIKqQoGB5QUZlRA4EBpNI1en+ODoMLxByoewAkSEYF6UEUaT0EGaCHyaGonoIpHoEYq9GI6Z9bGMIA
💻 Code
function paramsFunc<T>(param: T) {}
function cbFunc<T>(cb: () => T) {}

type MyType = {
    foo: string
}

// As we all know params are treated as exact types with generics. "bar" gives an error
paramsFunc<MyType>({ foo: 'bar', bar: 'baz'})

// But this is not the case when the same generic is used as a return type. "bar" does NOT give an error
cbFunc<MyType>(() => ({
    foo: 'bar',
    bar: 'baz'
}))

// But if I explicitly type it, it suddenly works again. "bar" gives an error
cbFunc<MyType>((): MyType => ({
    foo: 'bar',
    bar: 'baz'
}))

🙁 Actual behavior
When passing an explicit generic, when that generic is used as a return type, the excess property check is not running
🙂 Expected behavior
When passing an explicit generic, the excess property check should run regardless of how that generic type is used
Additional information about the issue
As a library author you might provide callbacks to some public API of the library to generate values. These callbacks can have a return type that needs to be defined by the consumer of the API. In library world you typically pass required types as part of some constructor as the type is used to infer different aspects of consuming the API. Currently library authors has to either:

Document that consumers has to both pass the type as a generic and explicitly use it as a return type on the callbacks
Create an artificial utility function to trigger excess property check on the params to the utility function, just to return the param

An example of this would be:
type State = {
  status: 'ON'
} | {
  status: 'OFF'
}

type Event = {
  type: 'TOGGLE'
}

const transitions = createTransitions<State, Action>({
  ON: {
    TOGGLE: () => ({ status: 'OFF' })
  },
  OFF: {
    TOGGLE: () => ({ status: 'ON' })
  }
})

In this example the excess property check is not triggered for the return type of these callbacks, even though the State generic was explicitly defined. As mentioned in the points above, you would need to either have to remember to explicitly add the return type to the callbacks:
const transitions = createTransitions<State, Action>({
  ON: {
    TOGGLE: (): State => ({ status: 'OFF' })
  },
  OFF: {
    TOGGLE: (): State => ({ status: 'ON' })
  }
})

This is easily missed as there is nothing initially indicating that a type is missing. It is only when you start changing the types that you have unused and confusing properties that is not part of the type, but is not erroring either.
Or you can:
const transitions = createTransitions<State, Action>((transition) => ({
  ON: {
    TOGGLE: () => transition({ status: 'OFF' })
  },
  OFF: {
    TOGGLE: (): State => transition({ status: 'ON' })
  }
}))

But this makes the API more verbose than necessary and the utility function makes no sense for someone consuming the library without TypeScript.
Sorry if this is already an addressed issue, but it seems to sit between generics, exact return types and esxcess property checks... so difficult to pin down if this is a bug, something that requires changes to TS or is expected behaviour. If this is expected behaviour I want to argue that explicitly typed generics should trigger excess property checks.
Thanks a bunch for taking the time to look through my issue 😄

This is essentially a duplicate of #241. Check the linked issues.

Thanks for the reference @MartinJohns! My "Excess property checks on return types" search did not hit  "widen return types" it seems 😂
But okay, great. I also see there was a design discussion on this https://github.com/microsoft/TypeScript/issues/56965.
It seems it is planned to be fixed, hm

Okay, so I get a response that the referenced discussion (https://github.com/microsoft/TypeScript/issues/56965) is related, but not a fix for this issue. So yeah, not sure how much attention this deserves and how to ensure it gets that deserved attention 🤔

Not sure if this is considered related, but this also doesn't work:
cbFunc<MyType>((): MyType => {
    const value = {
        foo: 'bar',
        bar: 'baz'
    }

    return value
})

@essenmitsosse That is working as intended. The type of your variables inferred to { foo: string; bar: string } due to the lack of type annotation, and when returning the value the compiler only checks compatibility. { foo: string; bar: string } is compatible with the type { foo: string }.
See the FAQ entry: (Indirect) Excess Properties Are OK

It's probably time for my once-every-few-years attempt to look at #241 again and see what doesn't work these days


[AMBARI-22939]. Ambari throws NPE when deleting a service (amagyar)

What changes were proposed in this pull request?
When a config group exists with service_name = null, ambari will throw a NullPointerException after removing a service. Ambari tries to remove config groups after deleting a service which causes the NPE
How was this patch tested?

created a config group with service_name = null
successfully deleted a service

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/491/
Test PASSed.


AbstractProductAttribute.save_value does not support option groups

I've run into an issue where something like the following doesn't work when the attribute uses an option group with Oscar 1.6.x:
my_attribute.save_value(my_product, 'example')

If this is a use case which is intended to be supported, then I believe that this issue still exists in the most recent version of Oscar as well.
Since 'example' is a valid option for this option group in this example, I would expect the call to work. Looking at the code, it seems to not take option groups into account here. The code also does not throw an error in this case, but the attribute value will not be changed. So, it seems like an error should be thrown in the case that this is not an intended use case.
Is there a better method by which to solve this problem in Oscar, or is this possibly an oversight in the codebase?

Thanks, @v1kku!


Train pnr status checker

Script Title -
Brief -
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md in your folder for program Instructions
add requirements.txt if needed

Programming Language

[x] Python

Happy Coding

Can you please assign it to me? Also, a doubt regarding this, should i create dummy databases?

You can, for testing

initally i'll try to do it with list. Later on I'll introduce databases.

@pawangeek  hey can you assign me this issue . I would like to work on this using REGEX

do you need it with the api to check with the actual database of indian railways or just with a local database

If there is any free workaround/api, to see on actual indian railways, it will be more good, else go with a local one


Added support for the DRFDocs module to auto-generate HTTP API docume…

…ntation and expose it on /docs.

:+1: merging


Fix for Ubuntu 16.04 hang

According: http://www.sdrplay.com/community/viewtopic.php?f=5&t=726&e=1&view=unread#p3344
Added mir_sdr_SetTransferMode(mir_sdr_BULK);  before mir_sdr_Init statements

@bilbolodz seems reasonable to me; will merge it in -- thanks!


Add label projection for Grid Layer

Add an option to grid allowing the labels to be in a projection other than the map projection.

Looks good for me :-)


Truncate data refresh percent change report to 3 digits after the decimal

Description

PR #636 added a count difference reporting message after the data refresh has been run. Part of this count is the percent change, which is given as a float. The difficulty with printing a straight float is that the numbers after the decimal can vary wildly. Here are a few examples:

Record count difference for audio: 174,290 → 817,198
Change: +642,908 (+368.8725687073269% Δ)

Record count difference for image: 563,561,088 → 564,775,616
Change: +1,214,528 (+0.21550955625949816% Δ)

Record count difference for image: 579,553,984 → 579,554,880
Change: +896 (+0.0001546016462204149% Δ)

We have a wide range of potential digits (in the hundreds to hundredths of a percent) and it can be hard to capture the level of information we would like for all cases. I think it would be best for us to have 3 significant digits after the decimal or closest zero, rounded up. This would mean for the above three cases the output would be:

368.8725687073269 -> 368.873
0.21550955625949816 -> 0.216
0.0001546016462204149 -> 0.000155

Alternatives

Leave as is, or do some basic string truncation which could leave us with values like 0.000%.
Implementation

[ ] 🙋 I would be interested in implementing this feature.

Hello, I've worked on this issue and written a function to truncate changes to 3 significant digits after the decimal and produces output exactly as the examples given.
But for very long decimals like 0.000001432153 the result gets rounded like 0.000001. Is this acceptable?

That is more than acceptable in my mind! Would you like to contribute the code? I can assign this issue to you if so 😄


[wip] Split reply button into reply + drop down menu

This puts [new private message] and [new topic] buttons into a dropdown menu, attached to the reply button.

This is implemented in a somewhat re-usable way, though could be vastly improved on this front, if dropdown buttons like this are a UX idiom we could re-use elsewhere.
I discovered popovers by discovering the mobile (+) button while starting mobile testing for this, and didn't have time to go back and re-work this to use popovers, though I think it has advantages over the existing popover code in some small dovetaily ways.
Handles clicking in the  anywhere to close the menu.
Not fully adapted to mobile yet, seems like it could potentially replace or be merged with the existing mobile [+] button? I did remove the conditional CSS hiding of the popup menu items in CSS. Need to consider whether to remove the existing mobile popup button?

Testing Plan:

Make sure reply, private, and topic buttons still work
Make sure clicking menu items closes the menu
Make sure clicking elsewhere closes the menu
Make sure keyboard shortcuts still work

GIFs or Screenshots:

We should rework this to use the popover code, and make improvements to popovers as needed to get UX parity as a separate step. Currently blocking on https://github.com/zulip/zulip/pull/11804 merging to continue this.

Feel free to do the popovers change either by cherry-picking the first three commits from https://github.com/zulip/zulip/pull/11804 or by building off master. The change in #11804 is small and will be easy to replicate/undo if needed.

Hey Seth -- I'm going to assign this to someone else so we can get it merged, but there is plenty to do so we can definitely find another project when you're free :).

Closing as our current redesign has a different direction for the closed-compose area of the app.


167 make a hamburger in navbar

🛠 Fixes Issue 167
Closes #167

👨💻 Changes proposed
Making the navbar responsive by adding a hamburger for mobile versions.

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

Attach a video wanna look how it works @Vijeth56


Idea for a "responsive" page design

Just a thought … a point for future discussion.
Perhaps as the screen / window gets smaller, the web page presenting the design problem could progressively display fewer and fewer columns.  The left-most column containing the variable names should stay at the left.  The remaining space, perhaps only enough for a single column at a time, could scroll horizontally so that the remaining columns can be accessed.

Another alternative could parallel the current use of IOOPT.  A preference setting could reduce the number of columns displayed.  Specifically, columns displaying violations could get dropped.


PTC cable for shell element

PTC cable for shell element
Originally posted by @andosca in https://github.com/strusoft/femdesign-api/issues/78#issuecomment-940925884

Will add on request.


Mouse long-press triggers QPanGesture

A specific example: when someone long-presses left mouse button while not moving the mouse around, a pan gesture is triggered. At first I thought it was my Apple Magic mouse which is touch-sensitive, but later tested with plain USB mouse, producing the same results. According to common sense, mouse clicks should never trigger gestures. Needs some further research about this.
As a workaround, gestures are temporarily disabled on Mac OS X.

For reference, https://github.com/realXtend/naali/commit/fec62428c88f0d2ee9ae9635b7968738e958633a .


fix(amplify-category-function): include files starting with a period on packaging

Description of changes
I use prisma with lambda function and it creates node_modules/.prisma folder to add query-engines. When packaging process, Amplify does not include this folder into build.zip . Adding dot: true option to archiver will solve this issue. But it will copy the unwanted files which is starting with period like .env. So I am not sure this is the best solution. I hope you will find this useful.
Description of how you validated changes
Manual
Checklist

[x] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #7861 (c0421a7) into master (28d49b4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7861   +/-   ##
=======================================
  Coverage   53.27%   53.27%
=======================================
  Files         555      555
  Lines       28051    28051
  Branches     5442     5442
=======================================
  Hits        14945    14945
  Misses      12121    12121
  Partials      985      985

Continue to review full report at Codecov.

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


3D ARRAYS in PYTHON

@Rohith2201 im added 3D array handling through python here coz python file still looks very empty and 3D array handling is something unique to so why not please assign me this and add labels thanks

i actually need one more contribution to complete my goal so please help me out here @Rohith2201

@Anuraj-IND make a pull request

@Rohith2201 i already sent pull request too

@Anuraj-IND make a pull request

already did see


chore(avm): add/improve tests for AvmContext, tagged memory, etc

Missing:

Cannot compare/test journals due to cyclic structure.
Field division is broken.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

master

PR #4476

PR #4484   👈

This stack of pull requests is managed by Graphite.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 545b3341 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,636
180,516
720,036

l1_rollup_calldata_gas
222,540
871,080
3,465,816

l1_rollup_execution_gas
315,027
988,820
3,685,473

l2_block_processing_time_in_ms
1,155
4,369 (+1%)
17,226

note_successful_decrypting_time_in_ms
306
987 (+3%)
3,617 (+1%)

note_trial_decrypting_time_in_ms
14.8 (-27%)
115 (+24%)
143 (+1%)

l2_block_building_time_in_ms
17,898
70,961 (+1%)
284,691

l2_block_rollup_simulation_time_in_ms
13,083
51,729
208,455

l2_block_public_tx_process_time_in_ms
4,784 (-1%)
19,149 (+1%)
75,975

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,704 (-10%)
26,103 (-11%)

note_history_successful_decrypting_time_in_ms
2,314 (-4%)
4,567 (+1%)

note_history_trial_decrypting_time_in_ms
78.0 (-9%)
215 (+7%)

node_database_size_in_bytes
17,330,256
33,030,224

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
311
44,476
26,153

private-kernel-ordering
199 (+1%)
44,473
16,553

base-rollup
1,408
128,930
881

root-rollup
82.3
4,088
677

private-kernel-inner
446
71,607
26,153

public-kernel-private-input
247
32,563
26,153

public-kernel-non-first-iteration
246
32,605
26,153

merge-rollup
7.62 (+1%)
2,608
881

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
17,187
39,991

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
584 (+5%)
1,322

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.521 (-13%)
591 (+1%)

Merge activity

Feb 7, 12:50 PM EST: @fcarreiro merged this pull request with Graphite.


Choose method dont triggers the 'change' event.

I have a 3 radio buttons.
I also have a 'change' event binded to that radio buttons via a delegated call.
node.on 'change', ':radio', @enableOrDisableRejectReasonField

When the third radio button, labeled with "Other (specify)", is chosen, a text field next to it should be enabled.
In my test I do that:
# I have a disabled field
page.should have_css '#availability_answer_reject_reason_explanation[disabled]'
# I choose the radio button that should enable that field
choose 'Other (specify)'
find_field('Other (specify)').trigger('change')  #=> I need to manualy trigger the change event only with capybara-webkit
# The field is not disabled now
page.should have_no_css '#availability_answer_reject_reason_explanation[disabled]'

With selenium I have no need to manually trigger the event. Capybara-webkit doesn't seem to fire the change event.
Is this behavior intended or known?

I'm seeing the same issue, upgraded to Capybara-webkit 1.6 but unfortunately that makes no difference.


Input k array and baryon boost

When one passes the option k for the pk_nl with baryon boost, get_ functions return a list instead of the standard array. This breaks the line https://github.com/MariaTsedrik/HMcode2020Emu/blob/48dded475f96668977288512042c138d68b9eb05/HMcode2020Emu/matter_powerspectrum.py#L321
Locally, I fixed it by transforming to np.array the lists in lines 146, 218, 282. The changes in lines 146 and 218 are to uniformize the output from the trained model and the one after the interpolations with input k.

Thank you so much for spotting this! In the newest version this issue is fixed.


Add search functionality for models

It would be nice to be able to search by account email, group name, workspace name, etc.

@jmcarson nothing needed yet but eventually we will need some search functionality.

Decision: add model-specific search that does simple text matching (e.g., using icontains). We can probalby use django-filter + django-tables2 for this (see docs).
Implementation: there should be some sort of text box at the top of the list views for BillingProjects, ManagedGroups, Workspaces, and Accounts that lets you filter the data in the table to a specific query.

What to search:

Billing projects: billing_project.name
Managed Groups: group.name
Workspaces: workspace.name
Accounts are more complicated, but they will probably need to leverage the Account adapter. By default the search should be over account.email.


'Rancher Prime' Landing Page

SURE-6856
Add description of prime subscription to Integrations tab (where the tiles for each project/product will be).

Reopening as additional review/updates need to be made. Initial PR was merged so some stakeholders had access to a preview.


perf - Improve MySQL/PostgreSQL meta concurrency

1, Optimize the ForUpdate call of doMknod/Link/Unlink/Rmdir/Rename operation
2, Change nlink operation from "Nlink = ?" to "nlink = nlink + (?)" for atomic
3, Move the parent update operation to the end of transaction
4, Remove txLock for MySQL/PostgreSQL meta engine

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Fangxin Lou seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Readme refers to github.com/streadway

Is this good enough, as in the top README.md, or do I miss something there?
Packages

Instrumentation is provided for the following packages, with the following caveats:

github.com/streadway/amqp: Client and server instrumentation. Only supported with Go 1.7 and later.

If you have detailed godocs you can point to that. For example, see how examples are shown for https://godoc.org/github.com/opentracing-contrib/go-stdlib/nethttp

Added the reference to the github.com/streadway/amqp as below.  I'll take care of the example aspect, both README.md as well as godoc under the other issue #2.
https://godoc.org/github.com/opentracing-contrib/go-amqp/amqptracer

@yurishkuro please re-open, if I miss something there, though.


Add To Last Commit fails

Command Name
Add To Last Commit
Steps to Reproduce

Stage a modified file.
Select the Add To Last Commit command and observe the confirmation dialog does not display the file name.
Press the Add To Last Commit button on the confirmation dialog.

Expected Behavior
The commit is amended with the staged files.
Actual Behavior

Observe two notifications regarding nothing to commit.
The file is no longer staged.

Environment

OS: Linux Mint 20.2 - Cinnamon
apm --version:

apm  2.6.2
npm  6.14.13
node 12.14.1 x64
atom 1.57.0
python
git 2.32.0

When select the Add To Last Commit command (step 2) is the staged file the active file?
The "Add To Last Commit" command (almost all of the commands really) do not act on the staged files but the selected files, the files that are selected in the tree-view or active editors. Actually I think the commit commands actually unstage all files before running the command.

or we should include git panel in selection. Currently it only checks tree-view or tab selection otherwise falls back to active editor.

I strongly prefer git-menu be made to work in the git panel.


add decode check for application

Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

Codecov Report
Patch coverage: 48.88% and project coverage change: +0.11 :tada:

Comparison is base (ca522b1) 18.68% compared to head (e823d30) 18.79%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2093      +/-   ##
==========================================
+ Coverage   18.68%   18.79%   +0.11%
==========================================
  Files          95       96       +1
  Lines        8874     8921      +47
==========================================
+ Hits         1658     1677      +19
- Misses       6995     7017      +22
- Partials      221      227       +6

Impacted Files
Coverage Δ

pkg/clusterfile/decoder.go
48.20% <40.00%> (-3.59%)
:arrow_down:

cmd/sealer/cmd/utils/application.go
60.00% <60.00%> (ø)

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

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

pls add description


build warning about parameter "localRepository" after upgrading to maven 3.9.1

[INFO] --- forbiddenapis:3.3:check (default) @ mycompany-common ---
[WARNING] Parameter 'localRepository' is deprecated core expression; Avoid use of ArtifactRepository type. If you need access to local repository, switch to '${repositorySystemSession}' expression and get LRM from it instead.

the warning seems to come from:
https://issues.apache.org/jira/browse/MNG-7706
where there are suggestions on how mojos should address it
it would be nice to avoid these build warnings in the next forbidden-apis release
thank you!

I do not think this can be quickly fixed, as forbiddenapis needs to raise the minimum Maven version first.
Does the warning always appear? IMHO, it should only appear if you use the localRepository parameter in the signaturesArtifacts. If you don't refer to those artifacts and just use plain forbiddenapis with bundled sogatures or local files, it should not ptint any warning. If yes, I would recommend to open a bug report at Maven to only print the deprectaed warning when the feature in question is actually used.

thanks for the quick feedback!
yes our build is using <signaturesArtifacts> in the parent pom for all other modules like this:
<signaturesArtifacts>
  <signaturesArtifact>
    <groupId>com.mycompany.tools</groupId>
    <artifactId>mycompany-build-tools</artifactId>
    <version>${project.version}</version>
    <type>jar</type>
    <path>mycompany-forbiddenapis/signatures.txt</path>
  </signaturesArtifact>
</signaturesArtifacts>

if you dont do that i doubt the warning will appear (but i havent tried that out)

I do not think this can be quickly fixed, as forbiddenapis needs to raise the minimum Maven version first.

just wondering: what minimum version would we be needing?
according to my understanding the deprecation warning was only introduced in 3.9.1. however the alternative and more correct way to acquire the same information could be available in much earlier maven versions already (we'd need to try that out i guess).
for example https://github.com/apache/maven-help-plugin/pull/88/files seems to show that having a single MavenProject parameter can be used as a replacement...
and i am guessing that functionality has been available in maven for a longer time already

All fine, I will check this. The next release is going to come out the next days, so this won't be included.

just wondering: what minimum version would we be needing?

At moment it compiles against Maven 2.0 API, because nothing more was needed for this plugin to work correctly. Upgrading to minimum version 3.0 would be possible, but needs some work. I will check how this can be resolved, but I am on business trip at the moment, so I will only release the current "main" branch soon when ASM has been upgraded and the Java 20 release came out tomorrow.

It looks like this is the problem, correct? https://github.com/policeman-tools/forbidden-apis/blob/0267abf82c03d65a46ecc8b8a10085d9d5430442/src/main/java/de/thetaphi/forbiddenapis/maven/AbstractCheckMojo.java#L241-L245

i am guessing it's:
https://github.com/policeman-tools/forbidden-apis/blob/0267abf82c03d65a46ecc8b8a10085d9d5430442/src/main/java/de/thetaphi/forbiddenapis/maven/AbstractCheckMojo.java#L250-L251
but if you check the PR i've linked earlier it seems that both these parameters can be replaced by going through a MavenProject parameter

You need to leverage the Resolver API instead which ships with Maven since 3.1.0 (https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup?focusedCommentId=217389433#MavenEcosystemCleanup-resolverMavenResolver(akaMavenArtifactResolver)). I would recommend to require a newer Maven 3.5 version (as the resolver moved then from Eclipse to ASF). Further details at https://maven.apache.org/resolver/api-compatibility.html#inside-of-maven

Thanks this information is helpful. I will look into this in the next days.

Does the warning always appear? IMHO, it should only appear if you use the localRepository parameter in the signaturesArtifacts.

Our build uses bundledSignatures rather than signaturesArtifacts, and we also see the warning. The changes in #230 make it go away. :+1:

@uschindler Gentle ping. Any chance you can look at the PR and afterwards spin a new release?

Hi, thanks. Sorry for the delay. It is busy to me at moment. Merging is one part, but the release won't come directly afterwards as this needs a bit of planning. I have not yet checked if this causes major API headaches (so 4.0 needs to be released, it that case done other features are on my list). If it can be merged and works with Java 7, no problem to have a release soon.

Yes, Java 7 is still supported: https://maven.apache.org/docs/history.html#maven-3-6-x-and-before

@kwin @uschindler Java 7 is very hypothetical. If you have up-to-date plugins, most will already require Java 8. But yes, Maven 3.x Core is still Java 7. May I ask why you would like to support Java 7?

@kwin @uschindler Java 7 is very hypothetical. If you have up-to-date plugins, most will already require Java 8. But yes, Maven 3.x Core is still Java 7. May I ask why you would like to support Java 7?

Actually I don't want to. It's just that I wanted more time to release a new version 4 with java 8, some rewritten parts.
Version 3 has just backwards compatibility, still signatures files for 7. It also compules with 7 and some commons projects of Apache were still using 7.
But actually we can still parse java 7 classes, just the runtime needs to be 8.
So in short: it's a temporal problem. I am very busy and people here want to get a new release just to get rid of warnings.... I do t understand that. Just ignore the warnings and give me some time! Unfortunately Maven is not my highest priority, the build system in version 4 of the plugin will be Gradle du to it's more flexible Scripting possibilities for building the plugin.

I merged this but tests fail....
I also had to downgrade the maven-plugin-plugin to stay compatible with java 7.

I will fix the remaining problems on main branch, looks like nobody ran tests because those use an earlier version. There are also Maven 2 tests!

I fixed the remaining issues after merging in multiple commits on main branch.
A release may take some time as I have to verify the test infrastructure and other stuff; also the minimum required Maven version in documentation and anywhere else.
The PR also used the "test" Maven version as minimum hardcoded into the plugin's minimum version. This is not related to each other.
So please don't hurry again with new releases, I have not much time at moment. You may use snapshot builds if you are annoyed by warnings...

I merged this but tests fail....
I also had to downgrade the maven-plugin-plugin to stay compatible with java 7.

I get why you would want run-time compatibility with Java 8, but trying to stay on Java 7 for builds is just unnecessary. Java 17 --release=7 and then test with 7 using toolchains will allow you to upgrade plugins.
Or is there any other reason?

The test failure happened on all versions. It is fixed now. The problem was that the Maven 3 tests were running against Maven 3.0.4.

This will change with forbiddenapis 4 and Gradle as it's build system. The old Ant based build is too inflexible.
I just don't want to rush that.

I will fix the remaining problems of the PR and fix the rest of inconsistencies and update documentation.
The main problem was not plugin versions (but actually I don't know why it had to be upgraded at all because the build was working and maven-plugin-plugin's only job is to setup the pom file and create documentation). The version change was IMHO an unrelated change that complicated everything more. I would wish people would concentrate on the required changes in PRs only.
The minimum Maven version change and the fixes for the Maven artifact download are well done, just the build system of the project is a bit crazy.
I want to change that, together with other version 4 features. I have a detailed plan for it ready, but just no time.

this one is also incorrect, because the POM variant that goes to Maven central should not contain properties: https://oss.sonatype.org/content/repositories/snapshots/de/thetaphi/forbiddenapis/3.6-SNAPSHOT/forbiddenapis-3.6-20230520.190405-4.pom
The minimum Maven version needs to be hardcoded in that file. I wonder why Maven accepts this when installing the plugin?

Hi,
I now changed the dependencies and did extensive testing:

Maven 3.1.0 is the minimum version now: It works with Java 7 and it is the first version using "Aether Resolver API".
The build time dependencies are now aether-api 0.9.0.M2 (as used by Maven 1.0). The utils package is not needed. Please don't complain here: That's just the minim version needed to be compatible with Maven 3.1.0
I hardcoded the minimum Maven version also into the deployed POM
Testing is also done with minimum version

Please don't complain again about "outdated versions". Forbiddenapis does not ship with any of those "outdated" dependencies. It only compiles against those versions to only use those APIs that are provided.
I also restored the mavn-plugin-plugin version back to the original version. The changes done in #229 were not needed and totally unrelated to an update of Maven minimum versions (this PR was a documentation update only).

I also restored the mavn-plugin-plugin version back to the original version. The changes done in https://github.com/policeman-tools/forbidden-apis/pull/229 were not needed and totally unrelated to an update of Maven minimum versions (this PR was a documentation update only).

Right, those relate to #228 as stated in https://github.com/policeman-tools/forbidden-apis/issues/228#issuecomment-1497795364.

Here are now all changes with updates to Maven version and Maven documentation: https://github.com/policeman-tools/forbidden-apis/compare/beaaa9c362d7ab3e95848f769fd15443373e4cb4..3166176ab2716f6fbc79d467c93efd467a9e4ac8

I also restored the mavn-plugin-plugin version back to the original version. The changes done in #229 were not needed and totally unrelated to an update of Maven minimum versions (this PR was a documentation update only).

Right, those relate to #228 as stated in #228 (comment).

Rendering of links works. And links to Oracle's Javadocs are not needed, so 3.4 is fine. The reason why the build uses the plugin-plugin (v3.4) is to just render the documentation. This versions produces the minimal possible hassle, later versions then complain about missing source code and other things. So please don't change that version.

Thanks @ all for reporting this issue and the discussions. Thank you @kwin for implementing the aether resolver API.

P.S.: It looks like Sonatype snapshots repository is not working at moment. Jenkins gets HTTP errors 502 and 504 while uploading the artifacts. Please try the snapshot version later this day.

Build was now successful: https://jenkins.thetaphi.de/job/Forbidden-APIs/499/console
Artifacts are here: https://oss.sonatype.org/content/repositories/snapshots/de/thetaphi/forbiddenapis/3.6-SNAPSHOT/


feat: Fix when object loses Error instance

If object has the properties: name, message, and stack, treat the object as an Error instance.

Stack trace is sometimes duplicated in message and stack :/


Email wasn't sent, no feedback

So this is very unpleasant but I tried sending an email and it just disappeared into the void.
Describe the bug
Spent some time writing an email, minimized it couple of times (wonder why it wasn't saved to drafts...), when finished pressed send and it just disappeared without any notification or update (very very bad UX guys). Therefore I decided to check if it was even sent, and it wasn't, I checked both app and server web, email is not there. After that I tried pulling logs using adb and nothing there because probably I can access only logs during adb session. Tried sending another email and it was sent.
Environment (please complete the following information):

K-9 Mail version: 5.806
Android version: 11
Device: One Plus Nord 1
Account type: IMAP & SMTP

Logs
As I've said they are not helpful but I will post them anyways:
https://pastebin.com/chLjCq0W
Log is to big to post on github

I'm aware that with these logs bug is not reproducible so you can close it right way. But I feel like it needs to be posted here anyways.

K-9 Mail creates an error notification when there was an error sending a message.
It looks like your K-9 Mail configuration leads to sent messages not being uploaded. So it's not too surprising that sent messages don't show up on the server. Make sure you've configured a Sent folder under Settings > [Account] > Folders > Sent folder and Settings > [Account] > Sending mail > Upload sent messages is checked.
Similarly, drafts are not saved if no Drafts folder is configured.
For providers accepting messages via SUBMIT but not actually sending them to the recipient, see https://forum.k9mail.app/t/5-8-showing-as-sent-but-not-always-arriving-at-destination/2481

It looks like your K-9 Mail configuration leads to sent messages not being uploaded. So it's not too surprising that sent messages don't show up on the server. Make sure you've configured a Sent folder under Settings > [Account] > Folders > Sent folder

That might be the case, thanks, I've set those settings. Sad that they are not set by default when folder equals one to one to setting (Sent === Sent).

and Settings > [Account] > Sending mail > Upload sent messages is checked.

It was but probability wasn't uploaded due to Sent folder not set.
Thank you for your support.


Example notebook is only working on clusters with version 6.4

I was trying out the mlflow integration for R with different cluster configs (9.1 LTS ML, 8.3, 10.0 ML, 7.3 LTS) but the install_mlflow() command is always failing with an error message (different error messages depending on the cluster version) e.g.: for 9.1 LTS ML it is:
Error : Error installing package(s): 'mlflow==1.20.2'
Some( Error: Error installing package(s): 'mlflow==1.20.2' )
The notebook seems to work fine for 6.4 but that is already in extended support. If there are any other steps necessary to get the notebook to run it would be beneficial to include that in the documentation.

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

ID: 90af26e0-7984-56f7-6abb-9ae93f7d6661
Version Independent ID: 00748395-42c4-8dec-c9db-57b93fc7a5b0
Content: Quickstart R - Azure Databricks
Content Source: databricks/applications/mlflow/quick-start-r.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

I actually found the solution today: https://stackoverflow.com/questions/60641337/mlflow-r-installation-mlflow-python-bin
instead of using install_mlflow() the system variables can be set directly since mlflow is already installed by default:
Sys.setenv(MLFLOW_BIN=system("which mlflow", intern=TRUE))
Sys.setenv(MLFLOW_PYTHON_BIN=system("which python", intern=TRUE))

@jbreunung  : Thanks for the sharing the solution , Going ahead and closing the issue now

well, the notebook in question has not been adjusted: https://docs.microsoft.com/en-us/azure/databricks/_static/notebooks/mlflow/mlflow-quick-start-r.html so I don't really understand how the issue can be closed...


Fixed example with defaultProps helper

Actually, we don't have a defaultProps helper.
Since this is in-library anyway, it's usually sufficient to directly set .defaultProps on the component anyway.


extend IsZero() to handle nil directly

User description
no need to go through reflection to known nil counts as a zero.

PR Type
enhancement

Description

The IsZero function in zero.go has been enhanced to directly return true for nil values, improving performance by avoiding unnecessary reflection.

Changes walkthrough 📝
Relevant filesEnhancement

zero.goEnhance IsZero Function to Directly Handle nil

zero.go
Added a direct check for nil in IsZero function to return true.  Simplified the handling of zero value checks by avoiding reflection for nil values.

+3/-1

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

refactored as suggested by the bot

@karasz I updated the comment, does it make sense? in my mind IsZero() is used to answer anything usable here? and should I set the default value?

v0.13.1 tagged


[FEATURE REQUEST] : Create a login page for the Website

Description
Is your feature request related to a problem? Please describe.
To create a more personalized environment for the individual , create a page where they can login themselves to their accounts
Describe the solution you'd like
Creating a login page using HTML,CSS,JavaScript

Please assign me this issue under JWOC'24

Please assign this to me under GSSoC'24.

Hello there,
Please assign me this under GSSoC'24.

I can make authenication system for the website.
I have exoerience on the similar type of project.
@akshitagupta15june please assign this task to me under Gssoc'24

Hi!! I am Anshdeep singh, contributor in GSSoC'24. I would like to address this issue and make the respective changes.

@akshitagupta15june
Problem Description and Steps to Reproduce:
Navigate to any section of the website.
Switch to dark mode.
Observe that only certain parts of the website are affected by the dark mode, leaving some sections in light mode.
Expected Behavior:
Dark mode should be consistently applied across the entire website, including all sections and pages.
Current Behavior:
Dark mode only partially changes the appearance, leaving some content areas in light mode.
Solution Proposal:
Implement a comprehensive dark mode that covers all elements of the website. Ensure that all text, backgrounds, and interactive elements are appropriately styled for dark mode.
Additional Information:
This feature will significantly enhance the user experience by providing a consistent and visually appealing dark mode across the entire website.
Please add the "gssoc24" label and assign this issue to me. I am excited to contribute to improving the project's user experience by implementing dark mode for all content on the website.
[FEATURE REQUEST] : Create a login page for the Website filled above but related to this topic and add Please add the "gssoc24" label and assign this issue to me. I'm excited to contribute to improving the project's user experience
ChatGPT
[FEATURE REQUEST] Create a Login Page for the Website
Problem Description and Steps to Reproduce:
Navigate to the website's homepage.
Attempt to find an option to log in.
Observe that there is no dedicated login page or functionality for user authentication.
Expected Behavior:
Users should be able to navigate to a dedicated login page where they can enter their credentials to access personalized features of the website.
Current Behavior:
The website currently lacks a login page, preventing users from signing in to access personalized content and features.
Solution Proposal:
Develop a login page where users can enter their email and password to authenticate themselves. This page should include form validation, error handling, and a "Forgot Password" option. Ensure the design is consistent with the overall theme of the website.
Additional Information:
This feature will enhance user experience by allowing users to access personalized features and content, thereby increasing user engagement and retention.
Please add the "gssoc24" label and assign this issue to me. I am excited to contribute to improving the project's user experience by creating a dedicated login page.

@akshitagupta15june
Problem Description and Steps to Reproduce:

Navigate to the website's homepage.
Attempt to find an option to log in.
Observe that there is no dedicated login page or functionality for user authentication.
Expected Behavior:

Users should be able to navigate to a dedicated login page where they can enter their credentials to access personalized
features of the website.
Current Behavior:

The website currently lacks a login page, preventing users from signing in to access personalized content and features.

Solution Proposal:
*Develop a login page where users can enter their email and password to authenticate themselves. This page should include form validation, error handling, and a "Forgot Password" option. Ensure the design is consistent with the overall theme of the website.
Additional Information:
*This feature will enhance user experience by allowing users to access personalized features and content, thereby increasing user engagement and retention.
Please add the "gssoc24" label and assign this issue to me. I am excited to contribute to improving the project's user experience by creating a dedicated login page.


Krakend 1.1.1 cannot parse roles in large token

Hello,
Sometimes (depending on the token), krakend seems unable to properly parse a token and the roles end up not working. I am using a short-payload token that has the following content:
{
  "iss": "https://nico-test.us.auth0.com/",
  "sub": "oZ4Qwz7G3ep60tcNblYttUWFl4NqD3tT@clients",
  "aud": "https://el.pulpo.com",
  "iat":<PHONE_NUMBER>,
  "exp":<PHONE_NUMBER>,
  "azp": "oZ4Qwz7G3ep60tcNblYttUWFl4NqD3tT",
  "gty": "client-credentials",
  "permissions": [
    "foo",
    "bar"
  ]
}

With the following endpoint config:
      "endpoint": "/rests-partners-gateway/rests-partners-accounts/info/",
      "method": "GET",
      "output_encoding": "no-op",
      "extra_config": {
              "github.com/devopsfaith/krakend-jose/validator": {
                  "roles_key": "permissions",
                  "roles": ["bar"],
                  "jwk-url" : "https://nico-test.us.auth0.com/.well-known/jwks.json",
                  "disable_jwk_security": true,
                  "alg" : "RS256"
              }
      },

In this case, kraken is able to check the "permissions" key and verify if the role "bar" is in there. When using a different role in the token, I get a 403 (as expected).
Thing is, with the following token:
{
  "https://partners.foo.com/roles": [
    "krakend"
  ],
  "nickname": "carlos.castro",
  "name"<EMAIL_ADDRESS>  "picture": "https://s.gravatar.com/avatar/077bc3b0517eb18354e0f3ebfb6a0220?s=480&r=pg&d=https%3A%2F%2Fcdn.auth0.com%2Favatars%2Fca.png",
  "updated_at": "2020-11-26T17:56:18.066Z",
  "email"<EMAIL_ADDRESS>  "email_verified": true,
  "iss": "https://partners-foo.auth0.com/",
  "sub": "auth0|5dcc9086defff70f095a1610",
  "aud": "A1YdFI6mIhG0NjozZsjISe1BDx7FdfJR",
  "iat":<PHONE_NUMBER>,
  "exp":<PHONE_NUMBER>,
  "at_hash": "c5WgSZhJAAqS_uH9pgFMVg",
  "nonce": "PZ~o1BijmVPeFYK-a0xjBeICMfJfm03k"
}

and the following endpoint config:
      "endpoint": "/rests-partners-gateway/rests-partners-accounts/info2/",
      "method": "GET",
      "output_encoding": "no-op",
      "extra_config": {
              "github.com/devopsfaith/krakend-jose/validator": {
                  "roles_key": "https://partners.foo.com/roles",
                  "roles": ["krakend"],
                  "jwk-url" : "https://partners-foo.auth0.com/.well-known/jwks.json",
                  "disable_jwk_security": true,
                  "alg" : "RS256"
              }
      },

I get a 403 every time, as if the token didn't have the role "krakend" in the key "https://partners.foo.com/roles". Besides attempting to change the key for something else/simpler, is there anything in the JWT that would cause this strange behavior?
Thanks a lot, kind regards.

Thanks for the heads up!!!
The issue was related to the namespace containing .. this char is also used to signal nested keys, so the validator wasn't able to locate the roles claim at the passed token


[BOT PR] to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
bf52d975a5190abb1f9ece6a3b3677e9bf51bb77
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
bf52d975a5190abb1f9ece6a3b3677e9bf51bb77
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
bf52d975a5190abb1f9ece6a3b3677e9bf51bb77
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
bf52d975a5190abb1f9ece6a3b3677e9bf51bb77
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
bf52d975a5190abb1f9ece6a3b3677e9bf51bb77
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
bf52d975a5190abb1f9ece6a3b3677e9bf51bb77
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


I have checked out the version 3.1.0 but could not find  Algorithm algorithm = Algorithm.RSA256(publicKey, privateKey);

I have checked out the version 3.1.0 ,but could not find this method in the api:
Algorithm algorithm = Algorithm.RSA256(publicKey, privateKey);
have I made something wrong?

It hasn't been released yet. Meanwhile, check https://github.com/auth0/java-jwt/tree/3.1.0

OK,Thanks so much,we expect to see this released version soon.

@QuanGangDeng This was just released and in a few hours it should be available.


Installing

Ok i am trying to install permissionsex on sponge 1.8 and cannot i have created the files and gives me a bunch of errors whenever i type a command when it is installed then fine when it is not installed please help.
Error:
19.12 15:27:07 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@2952f4e7(success)
19.12 15:27:07 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@53c2ce60(success)
19.12 15:27:07 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@4102932e(success)
19.12 15:27:07 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@5dc8ac69(success)
19.12 15:27:07 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@59bfca9b(success)
19.12 15:27:07 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@13d9134(success)
19.12 15:27:04 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@6e8d329f(success)
19.12 15:27:03 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@3dfb2e9c(success)
19.12 15:27:02 [Server] INFO at java.lang.Thread.run(Unknown Source) [?:1.8.0_25]
19.12 15:27:02 [Server] INFO at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:478) [MinecraftServer.class:?]
19.12 15:27:02 [Server] INFO at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:598) [MinecraftServer.class:?]
19.12 15:27:02 [Server] INFO at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:364) [po.class:?]
19.12 15:27:02 [Server] INFO at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:656) [MinecraftServer.class:?]
19.12 15:27:02 [Server] INFO at net.minecraftforge.fml.common.FMLCommonHandler.callFuture(FMLCommonHandler.java:714) [FMLCommonHandler.class:?]
19.12 15:27:02 [Server] INFO at java.util.concurrent.FutureTask.run(Unknown Source) [?:1.8.0_25]
19.12 15:27:02 [Server] INFO at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.8.0_25]
19.12 15:27:02 [Server] INFO at net.minecraft.network.PacketThreadUtil$1.run(SourceFile:13) [ih.class:?]
19.12 15:27:02 [Server] INFO at net.minecraft.network.PacketThreadUtil$1.onProcessPacket(SourceFile:84) [ih.class:?]
19.12 15:27:02 [Server] INFO at net.minecraft.network.play.client.C01PacketChatMessage.func_148833_a(SourceFile:9) [lu.class:?]
19.12 15:27:02 [Server] INFO at net.minecraft.network.play.client.C01PacketChatMessage.func_180757_a(SourceFile:37) [lu.class:?]
19.12 15:27:02 [Server] INFO at net.minecraft.network.NetHandlerPlayServer.func_147354_a(NetHandlerPlayServer.java:791) [rj.class:?]
19.12 15:27:02 [Server] INFO at net.minecraft.network.NetHandlerPlayServer.func_147361_d(NetHandlerPlayServer.java:812) [rj.class:?]
19.12 15:27:02 [Server] INFO at net.minecraft.command.ServerCommandManager.func_71556_a(SourceFile:80) [cl.class:?]
19.12 15:27:02 [Server] INFO at org.spongepowered.api.command.SimpleCommandManager.process(SimpleCommandManager.java:249) [SimpleCommandManager.class:1.8-1577-2.1-DEV-0]
19.12 15:27:02 [Server] INFO at org.spongepowered.api.command.dispatcher.SimpleDispatcher.process(SimpleDispatcher.java:334) ~[SimpleDispatcher.class:1.8-1577-2.1-DEV-0]
19.12 15:27:02 [Server] INFO at ninja.leaping.permissionsex.sponge.PEXSpongeCommand.process(PEXSpongeCommand.java:43) ~[PEXSpongeCommand.class:?]
19.12 15:27:02 [Server] INFO at ninja.leaping.permissionsex.util.command.CommandSpec.process(CommandSpec.java:166) ~[CommandSpec.class:?]
19.12 15:27:02 [Server] INFO at ninja.leaping.permissionsex.util.command.CommandSpec.getUsage(CommandSpec.java:238) ~[CommandSpec.class:?]
19.12 15:27:02 [Server] INFO at ninja.leaping.permissionsex.util.command.args.GenericArguments$OptionalCommandElement.getUsage(GenericArguments.java:746) ~[GenericArguments$OptionalCommandElement.class:?]
19.12 15:27:02 [Server] INFO at ninja.leaping.permissionsex.util.command.args.GenericArguments$FirstParsingCommandElement.getUsage(GenericArguments.java:637) ~[GenericArguments$FirstParsingCommandElement.class:?]
19.12 15:27:02 [Server] INFO at ninja.leaping.permissionsex.util.command.ChildCommands$ChildCommandElement.getUsage(ChildCommands.java:130) ~[ChildCommands$ChildCommandElement.class:?]
19.12 15:27:02 [Server] INFO at ninja.leaping.permissionsex.sponge.SpongeMessageFormatter.combined(SpongeMessageFormatter.java:46) ~[SpongeMessageFormatter.class:?]
19.12 15:27:02 [Server] INFO at ninja.leaping.permissionsex.sponge.SpongeMessageFormatter.combined(SpongeMessageFormatter.java:149) ~[SpongeMessageFormatter.class:?]
19.12 15:27:02 [Server] INFO java.lang.NoSuchMethodError: org.spongepowered.api.text.Texts.builder()Lorg/spongepowered/api/text/TextBuilder$Literal;
19.12 15:27:02 [Server] Server thread/ERROR [Sponge]: Error occurred while executing command 'pex help' for source EntityPlayerMP['TwistedCreeperYT'/39, l='world', x=216.70, y=70.00, z=246.72]: org.spongepowered.api.text.Texts.builder()Lorg/spongepowered/api/text/TextBuilder$Literal;
19.12 15:27:01 [Multicraft] Waiting for log file...
19.12 15:27:01 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@12eb3f40(success)
19.12 15:27:01 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@20197cfa(success)
19.12 15:27:00 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@300f77d1(success)
19.12 15:27:00 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@9cb74e2(success)
19.12 15:27:00 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@4513962c(success)
19.12 15:26:56 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@47a5c3db(success)
19.12 15:26:56 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@2ff2ee7e(success)
19.12 15:26:53 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@1a336c06(success)
19.12 15:26:53 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@3bdfe500(success)
19.12 15:26:52 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@653f1ad(success)
19.12 15:26:52 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@7659f8ad(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@77ddefb6(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@1e807f2b(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@ee51499(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@1f84d30a(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@113a42d7(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@65f3b0e1(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@3105236(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@1c4e307c(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@63d6bc58(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@798749ef(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@52ae9b6c(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@6be7b8d3(success)
19.12 15:26:48 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@6ad6b38(success)
19.12 15:26:46 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@6e38059d(success)
19.12 15:26:46 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@1693f9cb(success)
19.12 15:26:46 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@3c6ac93(success)
19.12 15:26:46 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@7d9559e8(success)
19.12 15:26:46 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@300713d8(success)
19.12 15:26:41 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@7f4be07e(success)
19.12 15:26:40 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@25b8091f(success)
19.12 15:26:40 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@2aa9de02(success)
19.12 15:26:38 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@2870c004(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@43aec657(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@6844c600(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@370e81f7(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@4faf9864(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@2c0a4107(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@1f3e3831(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@53616ecf(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@34f0a988(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@3f324a82(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@3ee1cd11(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@5c65f4d0(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@873eb0f(success)
19.12 15:26:36 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@32fbeaaf(success)
19.12 15:26:35 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@18108891(success)
19.12 15:26:31 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@6c33f2c9(success)
19.12 15:26:31 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@4fc27d96(success)
19.12 15:26:25 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@303ceb99(success)
19.12 15:26:24 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@63e93c24(success)
19.12 15:26:23 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@b9b5333(success)
19.12 15:26:23 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@4a45d98a(success)
19.12 15:26:23 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@5e739fb4(success)
19.12 15:26:23 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@71b3d817(success)
19.12 15:26:18 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@562dda21(success)
19.12 15:26:18 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@48d1063(success)
19.12 15:26:18 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@264fe8f5(success)
19.12 15:26:18 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@6d0d89e1(success)
19.12 15:26:17 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@d82be01(success)
19.12 15:26:17 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@5774c104(success)
19.12 15:26:17 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@2ab3f02a(success)
19.12 15:26:17 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@4eadb68e(success)
19.12 15:26:17 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@8045da9(success)
19.12 15:26:17 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@13c6b75b(success)
19.12 15:26:15 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@4a88400e(success)
19.12 15:26:11 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@365f3026(success)
19.12 15:26:11 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@44933a6c(success)
19.12 15:26:11 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@11d63a61(success)
19.12 15:26:11 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@5e4c3c39(success)
19.12 15:26:11 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@2050c2dc(success)
19.12 15:26:11 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@1afdad8a(success)
19.12 15:26:11 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@31e1677b(success)
19.12 15:26:10 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@20b42ac3(success)
19.12 15:26:08 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@527b2f10(success)
19.12 15:26:08 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@47b38060(success)
19.12 15:26:07 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@28eb4e18(success)
19.12 15:26:07 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@7381a958(success)
19.12 15:26:07 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@2368291a(success)
19.12 15:26:03 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@36219bcb(success)
19.12 15:26:03 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@6fd08968(success)
19.12 15:26:02 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@2b359d6d(success)
19.12 15:26:02 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@51e8735c(success)
19.12 15:26:02 [Server] Server thread/WARN [io.netty.channel.ChannelOutboundBuffer]: Failed to mark a promise as success because it is done already: DefaultChannelPromise@4e50520e(success)
Error in chat when type any command:
http://imgur.com/n2KxGcY

Update to the latest builds of PEX and Sponge.


输入框自定义高度的场景下，padding溢出，会出现鼠标还没有进入输入框内鼠标样式就发生变化了（padding区域）

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome<IP_ADDRESS>

https://github.com/arco-design/arco-design/assets/40122311/b57834e6-ee86-4cf8-88aa-8b8173244851


summary prefix ignored for aggregate (when fn[ds] is passed)

When passing an aggregation function, the "summary" prefix cannot be changed. In this example the column names start with "summary", but they should not.
(-> (tc/dataset {:l [:x :x :y :y :y]
                   :a [1 2 3 4 5]
                   :b [5 5 5 5 5]})
      (tc/group-by :l)
      (tc/aggregate (fn [ds]
                      {:sum-of-b (reduce + (ds :b))}
                      )
                    {:default-column-name-prefix "xxx"}
                    ))

thanks a lot!!


About the naming policy?

Hello @ddproxy ,
I am the member of cdnjs project.
We want to host this library.
The js file has a minified release, but the css file doesn't, so that we need to manually minify it.
The most common naming policy is leaflet.draw.css -> leaflet.draw.min.css.
But the js file naming policy is leaflet.draw-src.js -> leaflet.draw.js.
So the js file and css file will have different naming policy.
Maybe you could provide the minified css file.
Or change the js file naming policy, file name -> leaflet.draw.js, minified file name -> leaflet.draw.min.js.
Thanks for your help!
https://github.com/cdnjs/cdnjs/issues/6746

Is there a mechanism for me to automatically or manually push these files to cdnjs? I'm interested in making this easier for new updates to be pushed more rapidly while reducing the overall code - which includes possibly removing the dist directory.

@kennynaoh These minified files can also be put a standard minifier rather than being generated on our end...


Use publishTo value when it is defined.

Don't give error about missing repository if publishArtifact is false

Ping @dwijnand

I'll rebase to the correct branch

The travis failure is from MIMA:
method getPublishTo(scala.Option)sbt.librarymanagement.Resolver in object sbt.Classpaths does not have a correspondent in current version

[error]    filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("sbt.Classpaths.getPublishTo")

Yeah, you need to create new method.

done, needs new review and approval

Closing this in favor of https://github.com/sbt/sbt/pull/4934


[Kernel] Support running GPTQ 8-bit models in Marlin

This PR adds 8-bit weight support to the Marlin GPU kernel and the Marlin on-the-fly repack. As a result, all GPTQ 8-bit models (with any group size or act_order) can run via Marlin (for Ampere GPUs and up).

Here are vLLM server TTFT and TPOT benchmark results for 8-bit GPTQ Llama-3-8B and Yi-34B on A100 GPU on GCP instance (based on benchmark_serving.py):
vLLM Server - Llama-3-8B 8-bit.pdf
vLLM Server - Yi-34B 8-bit.pdf

Thanks for fixing the comments, this looks much nicer :)

@alexm-nm the model test failed


Making realtime reading from subprocess pipes work as expected

The way to think about pipes is as if they were files (which they basically are). One process writes to them (ls in the test code) and the other process reads (the parent python program). They can be bidirectional too, but we aren't using them that way here. The problem arises because the natural (ie. the most basic tools the operating system provides) way of reading from files is blocking which means that if the file isn't marked with an EOF (end of file) then your process will sit and wait until someone writes data to the file so you can read it. Pipes get EOF once the process writing to them exits. That means that normally you can't get data out of the pipe until the end of the process you've launched. But for long lived processes that's bad because you'd really like to have access to intermediate outputs in real time.
 The OS provides several tools (select, poll and some others) for checking if data is available so you know when to do your reads. You can build a real time pipe reader using those but I don't understand them very well so I chose not to. They are the traditional way of doing it. Recently (10 years? Probably more) people have started abstracting those low level tools up into non-blocking IO systems which give you different ways of talking about these problems. asyncio is an example of a non-blocking IO system and it happens to be part of the python standard library, so awesome.
asyncio works by giving you the ability to schedule coroutines which are basically threads but managed by the python VM rather than the host OS. Coroutines never run concurrently, meaning there's only ever one of them executing at a time, but they can release control back to the VM to allow other coroutines to run (this happens whenever you see a yield in that code). This is a model called cooperative scheduling as opposed to preemptive scheduling where the host environment forces threads to give up control so other code can run, that's what the OS does with regular threads and processes.
So in this code I create three coroutines. One of them runs the subprocess until it finishes and the other two attach to the pipes and read data out until the pipes close. Once I've launched all three, I go back and wait for each of them to finish. Under the hood the asyncio system is managing the reads from the pipes for me so I don't have to muck around with select or whatnot. In my code I get to treat reads like regular blocking reads because I don't care if one of the coroutines blocks, the others can keep running if they need to.
Anyway, I don't know if that makes what's going on any clearer. There's a bunch of concepts there which is why Drew is talking about "code of this complexity" but it's all worth understanding. Though we probably won't need to do much with this kind of IO elsewhere in this project.


Reading database in a loop while something is being added to it

Is this the use case where this should work?
I had bigg issues and after switching to mongoose and mongo, this didn't happen in the exact same code.
So basically I had one autoloaded database on disk and I was reading it from one script every 2s while another script was putting objects into the collection... the first script never saw the new items until after I restarted it, then they showed... but not the further ones being added, for this another restart was required and so on...
Is this a bug or just the design consequence?
Apart from this I was seeing things like:
Error: ENOENT: no such file or directory, rename './repositories/data/accounts.db~' -> './repositories/data/accounts.db'
which doesn't make much sense to me at all.
I expected this lib to be more robust, maybe I'm doing something wrong, not sure.. I'd still like to have one good option for file databases and the feature that api is a subset of mongo is very cool.

There is no such "close database" function in nedb yet and the storage
file may stay exclusively open while the other process tries to read
from. This may cause the failure you've described.
On 06/03/16 11:51, David Krmpotic wrote:

Is this the use case where this should work?
I had bigg issues and after switching to mongoose and mongo, this didn't
happen in the exact same code.
So basically I had one autoloaded database on disk and I was reading it
from one script every 2s while another script was putting objects into
the collection... the first script never saw the new items until after I
restarted it, then they showed... but not the further ones being added,
for this another restart was required and so on...
Is this a bug or just the design consequence?
Apart from this I was seeing things like:
|Error: ENOENT: no such file or directory, rename
'./repositories/data/accounts.db~' -> './repositories/data/accounts.db'|
which doesn't make much sense to me at all.
I expected this lib to be more robust, maybe I'm doing something wrong,
not sure.. I'd still like to have one good option for file databases and
the feature that api is a subset of mongo is very cool.
—
Reply to this email directly or view it on GitHub
https://github.com/louischatriot/nedb/issues/394.

What's the recommended approach to avoid this? I have cron jobs and users calling the same app with NeDB, and I am seeing this error all the time.

A database that should be accessible from multiple processes always needs a central process that manages the database. Embedded databases like NeDB don't have that because they are, well, embedded, so they shouldn't be used by multiple processes at the same time.
Recommended approach: Don't use NeDB, use a proper database like Mongo.

To confirm what @lukasbestle said: if you need multi client access to a database, there are high chances you need a full blown database such as Mongo. If you really want to do that with NeDB you need to wrap it in an HTTP server that will run in a standalone process (much like what MongoDB does to expose its API), but again that probably just means your project has outgrown NeDB.


Fixed systemHasAnsiSupport() when STDOUT is not undefined

Util/System/Linux::systemHasAnsiSupport() throws an error in the cases where the constant STDOUT is undefined.
Fixed systemHasAnsiSupport() to return false in this instance.
Closes: #172
See: https://stackoverflow.com/questions/17769041/notice-use-of-undefined-constant-stdout-assumed-stdout/28898174

DELETING this mess of a PR... Need to rebase before submitting again.


Fix/file switching bugs

Problem
Closes #126
Closes #127
Solution
Short explanation:
Prevent simulariumController.gotoTime from requesting a new time when the viewer is in the middle of changing files.
Long explanation:
The Antd Slider component's componentDidUpdate method is fired for some reason (probably because its parent's props change, but regardless of the reason, I don't think I have control over it?) when we're switching files but when we haven't finished loading the new file. And when that method fires, it triggers its onChange handler which eventually calls simulariumController.gotoTime(arg), with the arg being the time that the slider was displaying for the trajectory we're trying to change out. This all leads to time data from the old trajectory file coming into and mixing with the cache of the new trajectory file and interfering with the determination of the new file's firstFrameTime and lastFrameTime among other things.
simulariumController already has a boolean property called fileChanged that becomes true for the duration of a file change (loading period). If we disable simulariumController.gotoTime() when a file is still loading then we can prevent unwanted new time requests/messages during the file change period. This seems to fix the above two issues.
I think that the reason these bugs came up after this simularium-website commit is because the rounding of time values we were doing previously were simply masking some issues.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Steps to Verify:

Pull this branch and link your local viewer to a locally running simularium-website
Try to reproduce the bugs above, and also check that you can switch files without problem in general

Nice fix but it leads me to think of two things:

should we be doing this check in more places?  you kind of want to disable a whole lot of things during that transitional time

Probably. I'm not sure exactly where else at this point but will keep an eye out.

should the variable have a better name like "isChanging" rather than "changed" and use something like trajectory instead of file...   naming things is hard.

Agreed, I changed fileChanged to isFileChanging but left file as file for consistency with other functions that refer to file.


Variables leaking into global namespace from AMD module

I found these two variables defined in engine.js becoming global variables:

dwr
httpMethod

dwr seems to be globally assigned in line 620ff. by purpose(?) although it is not quite clear to me, why.
However, httpMethod is IMHO missing its variable declaration and thus, is erroneously interpreted as global variable in line 1669.

httpMethod
Good catch, thanks for letting us know! Fix arriving shortly.
dwr global
Yes, as you suspect this is intentional. Explaining the reason needs a fairly deep technical understanding of the effects of different DWR features, but in short this is how it goes:

the AMD loader allows several independent DWR instances to be loaded in the same page ("multi-version support")
when using script tag remoting the responses from the server need to be executed in the global scope
therefore each DWR instance is assigned an instanceId and registered in the global array dwr._ so remote responses may look up the correct instance to execute in

Note that the instance array _[] is the only child of the global dwr variable in AMD environments. The full DWR API is exposed under the respective instance.
We would of course like to avoid any globals at all, but removing this dependency is non-trivial as that would require the server to be aware of what kind of Javascript module system configuration is used in the client, to be able to look up the correct DWR instance.

thanks for reacting so quickly.
😺
just one follow-up question regarding the global dwr variable: if i knew for sure i only used one instance of dwr would maybe a configuration option make sense? this, way i could deliberately disable the global definition.
of course, only given i actually can be sure about the amount of instances used, i.e. if this is not beyond my control…?

A global would still be required for script tag remoting to work (to find the one DWR instance).
Honestly, we haven't regarded the dwr global as a big enough problem to take any actions against it in the current DWR 3.x codebase. And there are already too many settings. The next time we do a major refactoring of the DWR protocol and the client-side code we will for sure fix it though, but there are no plans at the moment.

ok, that makes sense. thanks for the clarification!