New icon animation: sort ascending, sort descending, sort remove

Name of icon to be animated as shown in Carbon Icon Library:
sort ascending, sort descending, sort remove
Category of icon:
opeations
Team/product requesting:
icon motion group
Contacts:
@kristastarr @johnbister
When is this needed?

optional - is there a specific deadline

Additional context

optional - is there anything else we should know?

@johnbister, @davidmenendez is going to do these to take some off your plate! 😅
@davidmenendez Since these are related to the other "sort",  icons (Caret sort, Chevron sort etc) you can reference the keyframes animations on those for consistency, maybe even re-use some of them directly if you think it looks good

@kristastarr @davidmenendez Hey! Thanks for offering, but I actually tackled these already #165
If you want to do some others, I can put up other issues! Sorry to snag it already if you were looking forward to it!


Profile https requests made by jdk http client

Fix #8019 and add profiler.jdk.http config to enable/disable.
https get:

https post:

http get:

http post:

https exception(with connect call):

https exception(without connect call):

@yjqg6666
I Added testweb for HTTPS
It seems that the https test of jdk-http-plugin-test is not normal.
Check please.

https://github.com/pinpoint-apm/pinpoint/pull/8024/commits/69394fdb9610206132774f69221bd3358683f3d2#diff-d0b6f9a4cfc9c43ccbd0064567af336985fa7ea243390fd40fdf9d67d8f76972R68
JDK version : AdoptOpenJDK jdk-8.0.292.10-hotspot

Ok I will check it later.

@emeroad This is what i get:

That's my fault. Rebuild agent and there is no problem.


Doc update

Description
Update of the document concerning the In-Band peering phase.
Hope that it's clear.

LGTM. Thanks!


Numeric Traits | Broken Filtering

Cool project thanks for sharing with us.
Using numeric trait values causes the build-rarities script to miss actual tokens at this line:
https://github.com/cryptoDevAmigos/rarity-analyzer/blob/main/packages/common-node/src/build-rarities.ts#L133
It ends up showing as [Missing] in the filtering functionality on the left nav which is undesirable given that the value is not actually missing;
I solved this on my fork by coercing the value to a string for equality matching:
.filter(t=>t.attributeRarities.some(a=>a.trait_type === x.trait_type && String(a.value) === String(x.value)))

There may be a better solution but this worked for me.

Worth noting that due to the rarity calculator 0 is still not a valid trait value:
This line filters out 0
const allAttributesRaw = metadata.flatMap(x => x.attributes).filter(x => !!x.value);

Nice chart here
 value     │  !value  │  !!value
━━━━━━━━━━━┿━━━━━━━━━━┿━━━━━━━━━━━
 false     │ ✔ true   │   false
 true      │   false  │ ✔ true
 null      │ ✔ true   │   false
 undefined │ ✔ true   │   false
 0         │ ✔ true   │   false
 -0        │ ✔ true   │   false
 1         │   false  │ ✔ true
 -5        │   false  │ ✔ true
 NaN       │ ✔ true   │   false
 ''        │ ✔ true   │   false
 'hello'   │   false  │ ✔ true


JBPM-5405: Stunner - Add TaskName property to UserTask

+1

@jlindop @tsurdilo @romartin this commit seems to be causing a compilation error (despite in being "green" here originally). I have to revert this commit. Can you please reopen/submit again.

Problem is that BPMNDiagramMarshallerTest doesn't compile:  https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/kie-wb-common/1394/org.kie.workbench.stunner$kie-wb-common-stunner-bpmn-backend/console

@csadilek Yes, I'll redo this.


Add an API for converting an error to an exit code

Description
This provides a method on all ParsableArguments/ParsableCommand types that lets you retrieve the exit code associated with an error.
Detailed Design

Add an exitCode(for:) method that converts an error to an ExitCode instance.

extension ParsableArguments {
  /// Returns the exit code for the given error.
  ///
  /// - Parameter error: An error to generate a message for.
  /// - Returns: The exit code for the `error`.
  public static func exitCode(for error: Error) -> ExitCode
}

Upgrade the ExitCode type to be a bit more useful, making it RawRepresentable and  Hashable. The represented code is now available through the rawValue property.

Documentation Plan
I included symbol documentation for the new APIs.
Test Plan
I added unit tests for the exitCode(for) method and converted the integration test helper to use ExitCodes instead of plain Int32s.
Source Impact
No source impact or deprecations.
Checklist

[x] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

Are there any guides on how one might use this API to give custom exit codes?


Clean up code under ./mobile folder

Description
As discussed with @Omar-Belghaouti after #361 , we can now clean up code under ./mobile
Check List

[ ] remove JSX.Element redundant annotation on all FC components.
[ ] Remove comments where the code is self explanatory.
[ ] Use named exports instead of default exports whenever possible
[ ] Use fetch instead of Axios, and create a wrapper around it that takes care of setting up endpoints type checking.
[ ] Removed dead code from the latest Redux integration.
[ ] Change UI to Screen.
[ ] Make Drawer.Screen.name lowercase
[ ] sort imports

Additional Comments
Feel free to disagree/discuss any points, or add missing points

my suggested improvements over the current folder structure is the following:
.
├── .common   <-- auto-generated
├── assets    <-- with the following format assets/[extension]/[file name].[extension]
│   │── ttf
│   │    └── spacemono-regular.ttf
│   └── png
│        └── branching.png
├── components    <-- contains shared components
│   ├── app-bar
│   │    │── style.ts
│   │    └── index.tsx
│   └── loading
│        │── style.ts
│        └── index.tsx
├── screens    <-- contains screens, sub-screens and non-shared components
│   ├── landing
│   │    │── style.ts
│   │    └── index.tsx
│   └── contribute
│        │── style.ts
│        |── index.tsx    <-- the screen itself, which display both components: contributions and filters.
│        |── contributions    <-- component that is only used inside contribute screen
│        │    |── style.ts
│        │    └── index.tsx
│        └── filters          <-- component that is only used inside contribute screen
│             |── style.ts
│             └── index.tsx
├── config    <-- contains global config such fullStackConfig
├── redux     <-- The whole state of the app (data layer)
│   ├── index.ts
│   │── actions <-- functions that modify the state (called by UI)
│   │    |── contribute-page
│   │    │    └── index.ts
│   │    └── general
│   │         └── index.ts
│   └── reducers <-- functions that form the state
│        |── index.ts
│        |── contribute-page
│        │    └── index.ts
│        └── general
│             └── index.ts
└── utils     <-- All the util functionalities that are only used inside the mobile code.

instead of writing ./component.tsx, we write ./component/index.tsx, this way the import still works the same way, and as a plus, we get to write different files inside ./component such as ./component/style.ts or ./component/sub-component/index.tsx.
things that we get from ./.common we require them directly, abstracting them even more defeats the purpose.
inside the view layer (./components/** and ./screens/**), we get the data from the state using Redux selector hook useSelector. we never modify the state directly from the view layer, we instead call (dispatch) action creators (functions inside ./redux/actions/**) which will handle modifying the state. We dispatch these actions using Redux dispatch hook useDispatch.
inside the data layer (./redux/**), the actions creators are the only code that should modify the state, by using the first two params: dispatch to modify the state or dispatch more actions, getState calling it will get us the state, which we may need to check on our state.
well, the previous two point is not 100% true, cuz, we can still call actions (not action creators) directly from the view layer, to do small modification to the state. such as updating an input value in onChange event, using the same Redux Dispatch hook.

@ZibanPirate sounds a good structure to me ☄ that I'll work on it in my next PR, it'll be more readable this way, however in the redux section we need a place where we define our action types (i.e constants/index.ts). Also it'll be better to work only with action creators whenever we change the state in the cache, even for small functionalities, that way the code can be more readable as well! 🐱🏍

reopening to finish the last tasks with #368


Issue with running TF 2.1.0 with validation_data tuple present

Weights and Biases version: wandb, version 0.8.28
Python version: Python 3.7.2
Operating System: Darwin

Description
I am not able to train TF models when passing validation_data on TF 2.1.0.
What I Did
import tensorflow_core as tf
from wandb.keras import WandbCallback
import wandb

wandb.init(
    project="test",
)

model = tf.keras.models.Sequential()
...
 model.fit(
                x=train_features,
                y=train_values,
                validation_data=(test_features, test_values),
                epochs=5,
                callbacks=[WandbCallback()],
                verbose=2
)

Results in:
  File "[redacted project file]", line 57, in run_training
    self.sequential = self._train_network(train_features, test_features, train_values, test_values)
  File "[redacted project file]", line 128, in _train_network
    verbose=2
  File "[redacted project loc]/venv/lib/python3.7/site-packages/tensorflow_core/python/keras/engine/training.py", line 819, in fit
    use_multiprocessing=use_multiprocessing)
  File "[redacted project loc]/venv/lib/python3.7/site-packages/wandb/keras/__init__.py", line 111, in new_v2
    set_wandb_attrs(cbk, val_data)
  File "[redacted project loc]/venv/lib/python3.7/site-packages/wandb/keras/__init__.py", line 79, in set_wandb_attrs
    elif isinstance(val_data, tuple) and isinstance(val_data[0], tf.Tensor):
AttributeError: module 'tensorflow' has no attribute 'Tensor'

Note 1: I am using tensorflow==2.1.0.
Note 2: The issue does not occur if I remove validation_data

Thanks for reporting this! @raubitsj could you please take a look.

I used model.fit as well. I am not getting the attribute error mentioned above. However, when I run the training with model.fit, the training metrics are logged at all. The training process is taken care by Tf+Keras without any issues but no live-logging/logging is available under the Chart tab in the WandB page. Please advise

If you use the WandbCallback in your fit function you can pass validation_data directly to the WandbCallback as a keyword argument.  In older version of keras we picked this up for you automatically.  We'll look into the root cause and do this automatically for you, but until then just pass the same validation_data to the WandbCallback.

Closing this as @vanpelt has already mentioned a workaround for the ticket.


Make sure double retractions are not inserted. Fixes #818

@ncalexan this is failing tests on 1.25.0 for reasons seemingly unrelated to the patch itself.


Nimble table spec

Pull Request
🤨 Rationale
We need a spec for the nimble-table.

Is there a need to specifically callout theme support in this spec?

Is there a need to specifically callout theme support in this spec?

I don't believe so, as, ultimately, the Design XD document specifies that implicitly. Other specs haven't explicitly called it out afaik.


Throws an error, if $orderItem->getSku() returns null

https://github.com/exponea/bloomreach-magento2-integration/blob/e4cf0f2f7b19c8c487379288a189eaea2ff100e1/Model/DataMapping/FieldValueRenderer/Order/ProductList.php#L62
quick fix: return $product ? $product->getSku() : ($orderItem->getSku() ?? "");

Hi @pip77, that's really weird that the sku doesn't exist for your order item. However, since the DB column can be null, then we'll have this fixed within next releases.
Thank you for reporting this one.


✨ Python 3.12

Description
Upgrades to Python 3.12 using hatch-pip-compile to manage lockfiles between versions

This PR is blocked by https://github.com/dateutil/dateutil/issues/1314

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


Issue 105 : Dark Mode + Theming #118

Created separate branch for dark mode, as I maybe submitting another PR.

Sounds good I'll make the change by Wednesday latest.

Made the requested change. If you require a rebased version I can make another pull request using the master branch : https://github.com/Jongwoo-Shim/al-folio/tree/master


Ability to found ored constants even if no enumeration type is set

I'm not sure if this is a bug or missing feature. In the example below 0xf0 actually means PAGE_EXECUTE_WRITECOPY|PAGE_EXECUTE_READWRITE|PAGE_EXECUTE_READ|PAGE_EXECUTE but I cannot set that value to enumeration. It would be very useful if BN can do that when I try to set enumeration with M shortcut.
int64_t query_mem_info(int64_t addr)

MEMORY_BASIC_INFORMATION lpBuffer
VirtualQuery(addr, &lpBuffer, 0x30)

if (lpBuffer.State == MEM_COMMIT && (lpBuffer.Protect.b & 0xf0) != 0) {
  return 1
}

return 0

Actually I found other examples where BN automatically did that. For example:
uint32_t uMode = SetErrorMode(SEM_FAILCRITICALERRORS | SEM_NOOPENFILEERRORBOX)

SetErrorMode have a type like this: uint32_t SetErrorMode(enum THREAD_ERROR_MODE uMode). So I assume BN do this automatically if enumeration type is set. I tried to change the type of Protect from DWORD to PAGE_PROTECTION_FLAGS but it didn't work. Also I don't think that this should be the solution for this issue, instead, BN should be able to do it even if there is no enumeration type is set.

@op2786 do you have a binary to reproduce this?

I think the problem here is that the enumeration we have defined is not an un-ambiguous bit field enumeration
For instance:
PAGE_ENCLAVE_SS_FIRST  == PAGE_ENCLAVE_DECOMMIT  |  PAGE_NOACCESS
and
PAGE_ENCLAVE_MASK == PAGE_ENCLAVE_DECOMMIT
Currently we don't have any way to disambiguate enumeration masks. Or provide multiple different ways to view an enumeration's component parts. I bet if you remove SEC_IMAGE_NO_EXECUTE and PAGE_ENCLAVE_* then it would work as you expect.
So I see one of 3 possibilities here:

We provide a number of possible representations the user can chose from (I think this is my preferred way)
We add some additional information to the enumeration to specificially mark "mask" type enumeration values.
We add an explicit __bitfield_enum designator that is then able to automatically idendify "masks" and warn when the bitfield is ambiguous.

Hmm I guess there is one other way of doing this 🤔 ... perhaps we don't need to guarantee the whole enumeration is a bitfield but instead we can just ensure that they constants in use are unambiguous.... this could actually be pretty easy to do.

v35 folks should search springbuck suffusive rustles neoplastic benzine to find the binary


[Bug]: The first requests when streaming (range requests) uses a GET instead of a HEAD, breaks compatibility with dotnet servers

Attach (recommended) or Link to PDF file
https://mozilla.github.io/pdf.js/web/viewer.html?file=https://d2tkmshiozsr4v.cloudfront.net/documents/files/000/041/350/original/ad41798557504b40d26e11b4f059c0945bb5ca14/750614main_NASA_FY_2014_Budget_Estimates-508.pdf?1401953041#disableAutoFetch=true&disableStream=true
Web browser and its version
Google Chrome latest
Operating system and its version
Windows 11
PDF.js version
https://mozilla.github.io/pdf.js/web/viewer.html
Is the bug present in the latest PDF.js version?
Yes
Is a browser extension
No
Steps to reproduce the problem
Go the following link: https://mozilla.github.io/pdf.js/web/viewer.html?file=https://d2tkmshiozsr4v.cloudfront.net/documents/files/000/041/350/original/ad41798557504b40d26e11b4f059c0945bb5ca14/750614main_NASA_FY_2014_Budget_Estimates-508.pdf?1401953041#disableAutoFetch=true&disableStream=true
Open up the network inspector, disable caching and do a refresh so you can see the latest requests
The first request you will see will be a GET with a 200 response, this initiates the streaming process for PDF js
What is the expected behavior?
Per https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests this first request should be a HEAD request.
What went wrong?
The latest version of dotnet (8 at the time of writing) has logic in their Kestrel server to prevent Content-Length mismatches when performing GET requests, this is done to avoid a class of exploits known as HTTP request smuggling where an attacked can sneak bytes in at the end of a request.
This means that dotnet servers will not work as efficiently with the streaming feature.
Link to a viewer
No response
Additional context
No response

Is anyone familiar enough with the network layer to tell me if my proposed fix is correct?
I believe this fetch request should be a HEAD not a GET
https://github.com/mozilla/pdf.js/blob/7199c967e68fde48bf2a105296e0b278edc6ffe9/src/display/fetch_stream.js#L130

Duplicate of #11669


Deploy the project

Is your feature request related to a problem? Please describe.
I need to view the project without cloning
Describe the solution you'd like
Deploy on netlify , it will also provide PR preview
Describe alternatives you've considered
No response
Additional context
No response

Go ahead @VenomFate-619 ✅. It's good to have it on netlify along with the Docker image we already have.

Any updates @VenomFate-619 ?

sorry, forget to update.
I had deployed it on netlify but getting a white screen and error in the console

sorry, forget to update you.
https://dulcet-scone-d98f2d.netlify.app/
deployed URL

I would recommend deploying the project yourself because currently, the deployed site is linked to my fork repo.
So whenever I pull or commit then only it will be updated.
you can have a look at my forked repo what changes need to be made to deploy it on netlify.
https://github.com/VenomFate-619/amazon-clone


Update README.md

Hi, I've never contributed before, but on my way through setting up my own Rocket.Chat server I found a couple of errors in this document and thought I might actually be able to contribute to something for once. Let me know if it's not appreciated. I am a bit of a grammar gestapo, and found these lines a touch confusing. Hope you don't mind! Thanks for all your hard work on this project!

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

I would be happy to do a deep dive on your docs to clean them up, but am not sure how best to approach such a task. Should I fork and make a  bunch of changes at a time, and submit a heavy pull request, or would you prefer I update a few files at a time and try to merge in smaller batches?

@deenski your best change of success and quick review is smaller more focused PR's :)


[feature] jsx props to js object

for example:
<Test
  className="some-class"
  style={{ color: 'red' }}
  onClick={() => this.doSomething()}
  other
/>

becomes:
{
  className: 'some-class',
  style: { color: 'red' },
  onClick: () => this.doSomething(),
  other: true,
}

It is live now. 😃 https://transform.now.sh/jsx-to-js-object/

You are amazing ✨

It isn't yet feature complete. Like it won't be able to handle functions for now. I will do that when I get time.


Release 2.0.0

Placeholder issue for tracking things that need to be done for a 2.0.0 release:

[x] Update to Brave 4
[ ] Update Readme/docs/examples

@llinder originally there were a few things I figured we might want to include in the release. For example, bringing back some of the stuff you used to be able to configure in the module. But a) not sure if they're still necessary and b) the upgrade to Brave 4 is probably enough.
If you can think of anything else that might need to be done, polished, etc. let me know :)

@hyleung originally I thought we might want to bring back some of the HTTP abstractions.  Now that Brave 4 includes these I don't think there is anything else needed.  As far as configuration options I think the ServerTracingModule covers all of the major Tracing configuration options.
Once 2.0 is released I would like to revisit context propagation fixes for ParallelBatch.  That can probably wait until this is out though.

@llinder re.

I would like to revisit context propagation fixes for ParallelBatch.

...is that related to your comments here on #35 ?

@hyleung sorry for the delayed response.  Yes the changes in #35 covers my comment about ParallelBatch work.
What do you think about making a 2.0 release?  I would like to start using this in several services in proprod environments this week if possible.  Maybe a milestone release like 2.0.0-M1 until we get the docs up to date?

@llinder I think the only other thing I wanted to do (other than update the README) is quickly test the ParallelBatch stuff. Other than that I think we're good to do a release in the next day or so. That sound good? If you want something sooner, I'm happy to do a milestone release today...

Thanks @hyleung... sometime in the next few days works for me.  Mostly I didn't want to put pressure on anyone to get docs or examples updated.  If we find that more time is needed for docs or testing then maybe we can revisit a milestone release in a couple days if necessary.

@llinder had a quick test of the ParallelBatch stuff, works as advertised 😄
Also did a quick pass to update the README and some Javadoc in #38

Released v2.0.0!


State mismatch in libp2p: Expected alive incoming. Got None.

This error seems to be printed once per hour on average on our nodes:

2020-05-22 01:18:55.134 tokio-runtime-worker ERROR sub-libp2p  State mismatch in libp2p: Expected alive incoming. Got None.

This can either be caused by a bug in the peerset sending inconsistent messages or by a bug in the state machine that handles the peerset's messages.

For what it is worth, I don't see this error any more in the Kibana logs for the "logstash-kusama" index family since June 14th. Are there other places or log indices to check?

Let's assumed that it is fixed. We can always reopen if the error is seen in the logs again.


Add support for disabling root viewBox attribute in stack mode

This is the PR to fix: https://github.com/svg-sprite/svg-sprite/issues/303
With it you can disable viewBox attribute rendering in the root element. By default the attribute is rendered with true, but when you set false, it's not added.

Hello @Arkkimaagi! Thank you for this PR. I have few thoughts about it.

Maybe the config attribute name should be named with camelCase. And since it is boolean, it should have more boolean-specific name, like setRootViewBox or somewhat like that
This branch of code at least should have been tested with integration tests of stack mode (we currently haven't covered modes by unit tests yet). My suggestion is to add rootviewbox config in stack test configuration of SVGSprite

@XhmikosR what do you think?

I actually had it at first in camel case, but since I did not see other configs in camel case, I converted it to this. I wanted to match the convention. I'm okay with any change tho. Just let me know.

I'd say better be consistent with the existent options for now, although I agree they are not optimal.

I'm going to need help with the tests. 🤔

@XhmikosR are you saying about options naming or about adding new option?

@Kreeg Both; @Arkkimaagi is consistent with the options pattern we follow here.

Thanks @Kreeg, I hope I cherry-picked it properly :D

Hmm, I seriously hope I got these things done correctly. If this is getting messy, you can just use my code on a new branch or what ever. I'd just love to see this feature in svg-sprite, I do not care who gets the "credit" of writing it. :)

@Arkkimaagi sorry but it went worse. I created a new pr #666. Closing this now


fix: updates cicd

What
fix: updates cicd

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


Maximum number of 10 projects reached, and Error: Loading Projects

Describe the bug
Load up a new page, click save, and gets the above message. Click the projects button and it gives red text saying "Error: Loading Projects"
To Reproduce
Load up the default URL https://play.flow.com/local-project hit save
Expected behavior
To save and not error
Screenshots

Desktop (please complete the following information):

OS: iOS
Browser Chrome
Version Version 111.0.5563.146 (Official Build) (x86_64)

Additional context
Seems to work in firefox.

From https://github.com/onflow/flow-playground/issues/617:

To Reproduce
Steps to reproduce the behavior:
For me, I only have to go to playground for the error to occur. I'm assuming this is due to previous projects cached in my browser, as I don't have the problem in incognito or other browser windows.

MacOS, Chrome

I've just checked play.staging.onflow.org and this error doesn't reappear.
Happy days!


feat: allow using both prettier and standardjs

Proposed changes

Allow using both Prettier and StandardJS at the same time by removing
JAVASCRIPT_DEFAULT_STYLE and TYPESCRIPT_DEFAULT_STYLE
configuration variables. They create a confusing corner case that
Super-linter already handles with its core logic that's in place to
enable and disable linters.
Document VALIDATE_JAVASCRIPT_PRETTIER and VALIDATE_TYPESCRIPT_PRETTIER
because they were missing from the README.
Add missing TYPESCRIPT_PRETTIER tests. We didn't notice it was missing because we weren't running TYPESCRIPT_PRETTIER at all.

Readiness checklist
In order to have this pull request merged, complete the following tasks.
Pull request author tasks

[x] I included all the needed documentation for this change.
[x] I provided the necessary tests.
[x] I squashed all the commits into a single commit.
[x] I followed the Conventional Commit v1.0.0 spec.
[x] I wrote the necessary upgrade instructions in the upgrade guide.
[x] If this pull request is about and existing issue,
I added the Fix #ISSUE_NUMBER label to the description of the pull request.

Super-linter maintainer tasks

[x] Label as breaking if this change breaks compatibility with the previous released version.
[x] Label as either: automation, bug, documentation, enhancement, infrastructure.

@zkoppert can you please review this one? Thanks a lot!

Document VALIDATE_JAVASCRIPT_PRETTIER and VALIDATE_TYPESCRIPT_PRETTIER
because they were missing from the README.
Add missing TYPESCRIPT_PRETTIER tests. We didn't notice it was missing because we weren't running TYPESCRIPT_PRETTIER at all.

😅

sorry, forgot to fix the upgrade guide :)

Hi!
You might have a point here, although the reason why we didn't mark this as a breaking change is that enabling this behavior has always been possible, but it wasn't documented.
The fact that they didn't run at the same time created a confusing corner case, which we classified as a bug, as you can also see from the fact that we were missing both documentation and a test case.

The thing that makes it a "confusing corner case" is that standard and prettier are formatters, not linters.  It makes sense to run lots of linters to pick up issues in a variety of file types.  IMO it never makes sense to run multiple formatters (for the same file type), as they are not going to agree on the correct style - if they did then one of them would be redundant.  The old config option made much more sense to me that what was introduced here.
Layer on top of that the fact it breaks existing configuration without a major version bump, and probably breaks out-of-the-box default configuration for JS/TS files, then my suggestion would be to roll back the change and re-consider how and when the changes should be re-introduced.

Again, you have a point in suggesting that users might want to run only one formatter per file type.
The confusing corner case I'm referring to is that, before this change, to do that for Standard and Prettier, you would need to set the JAVASCRIPT_DEFAULT_STYLE and TYPESCRIPT_DEFAULT_STYLE variables, while all other tools (both linters and formatters) that Super-linter ships use VALIDATE_xxxx variables for that. After this change, you can use VALIDATE_JAVASCRIPT_PRETTIER, VALIDATE_JAVASCRIPT_STANDARD, VALIDATE_TYPESCRIPT_PRETTIER, and VALIDATE_TYPESCRIPT_STANDARD for the same purpose, bringing this in line with what you do with other linters and formatters.
The issue, in this case, is that the VALIDATE_JAVASCRIPT_PRETTIER, VALIDATE_JAVASCRIPT_STANDARD, VALIDATE_TYPESCRIPT_PRETTIER, and VALIDATE_TYPESCRIPT_STANDARD variables were breaking the behavior described in the Configure Super-linter section of the readme, reported here for convenience:

The VALIDATE_[LANGUAGE] variables work as follows:
super-linter runs all supported linters by default.
If you set any of the VALIDATE_[LANGUAGE] variables to true, super-linter defaults to leaving any unset variable to false (only validate those languages).
If you set any of the VALIDATE_[LANGUAGE] variables to false, super-linter defaults to leaving any unset variable to true (only exclude those languages).
If you set any of the VALIDATE_[LANGUAGE] variables to both true and false, super-linter fails reporting an error.

This is why this change was necessary.
The points you're raising warrant an addition to the upgrade guide, though. I'll provide it in a separate PR.

Thanks for raising this @gavllew . I just sent https://github.com/super-linter/super-linter/pull/5948 to help with the configuration update.


TypeError: rxjs_1.fromEvent is not a function

I keep getting this error, I have all the basic code. Nothing new.
"Uncaught (in promise): TypeError: rxjs_1.fromEvent is not a function\nScrollObservable.prototype._getGlobalObservable@webpack-internal:///../../../../angular-inport/dist/utils/scroll-observable.js:19:29\nScrollObservable@webpack-internal:///../../../../angular-inport/dist/utils/scroll-observable.js:11:50\n_createClass@webpack-internal:///../../../core/esm5/core.js:11107:20\n_createProviderInstance$1@webpack-internal:///../../../core/esm5/core.js:11081:26\nresolveNgModuleDep@webpack-internal:///../../../core/esm5/core.js:11066:17\nNgModuleRef_.prototype.get@webpack-internal:///../../../core/esm5/core.js:12303:16\nresolveDep@webpack-internal:///../../../core/esm5/core.js:12793:12\ncreateClass@webpack-internal:///../../../core/esm5/core.js:12663:32\ncreateDirectiveInstance@webpack-internal:///../../../core/esm5/core.js:12500:37\ncreateViewNodes@webpack-internal:///../../../core/esm5/core.js:13958:53\ncallViewAction@webpack-internal:///../../../core/esm5/core.js:14392:13\nexecComponentViewsAction@webp…

@iki789  Which version of rxjs you are using in the project?
FYI rxjs version should be > 6.

@CoderAjay I'm using rxjs 5.5.6 with angular 5.2.0 and i'm facing the same problem

@yassinesabri
Two options

You can use<EMAIL_ADDRESS>which gonna work with rxjs 5.5.x.

You can upgrade rxjs version to 6 and to support angular@5 use rxjs-compact.

@CoderAjay Thank you the error is gone.

That's great.


Revise getBestMove and add test

Coverage decreased (-0.7%) to 96.506% when pulling df1fe558d3f873e5d33dc35cd4c83a3a4c90bf4a on huanfachen:tabuSearch/add_variant into f6bfd50ac978d1d392ab6bf8cefccfad712ff077 on hdbeukel:master.

No need to create this second pull request, the first one is still open and includes any further changes you make to huanfachen:tabuSearch/add_variant.


:postbox: Update ci-scripts

Nothing important in this update, just updates to the README and example .travis.yml in the submodule.

:rocket: deployed to http://profiles-pr-72.dev.c2s.nhschoices.net


Circle PyQt5 failure

circle CI is failing at the "CheckPyQt5" stage with this:
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.

version used (from the "get python running" stage):
Collecting PyQt5>=5.11.3imageio>=2.5.0
  Downloading PyQt5-5.15.2-5.15.2-cp35.cp36.cp37.cp38.cp39-abi3-manylinux2014_x86_64.whl (68.3 MB)

I can fix this with an LD_DEBUG=libs + "Rerun with SSH", let me look...


[Feature] add schematic.kube  section to align with spec 0.2.2

apiVersion: core.oam.dev/v1beta1
kind: ComponentDefinition
metadata:
  name: webservice
  namespace: foo # install this component in namespace foo
spec:
  workload: # workload type descriptor
    type: containerizedworkloads.core.oam.dev # ref to a WorkloadDefinition via name
  schematic:
    kube: # this section is same with v0.2.1 component spec (i.e. raw k8s resource template)
      template:
        apiVersion: core.oam.dev/v1alpha2
        kind: ContainerizedWorkload
        spec:
        ...
          containers:
          - name: my-cool-workload
            image: example/very-cool-workload:0.1.2@sha256:verytrustworthyhash
            resources:
              cpu:
                required: 1.0
              memory:
                required: 100MB
            cmd:
            - "bash lscpu"
      parameters:
      - name: image
        required: true
        fieldPaths:
        - "spec.containers[0].image"
      - name: cmd
        required: true
        fieldPaths:
        - "spec.containers[0].cmd"
    cue:
      # cue template and parameters
    helm:
      # a helm chart

status:
  parameters: # a generated json schema of parameters, equivalent to spec.parameters but friendly to k8s impl

https://github.com/oam-dev/spec/issues/443

I would like to help with this issue.


Update README.md

coverage: 79.518%. remained the same
when pulling 0834d2f83df26dff1422f365868f8d066bb98c98 on readme
into b8db58e6a52deee34acaef6d6953791b3731403c on main.


buildroot: fix lisa-buildroot-update-kernel-config

Use KConfig fragments, which are not trying to detect features of GCC
when merged. Using make oldconfig can break the configuration if the
host version of GCC is wildly different than the one used to
cross-compile. KConfig fragment also has the added benefit of reporting
what was modified in the config.

Sorry for the late response - just seen this.
If you can expand the comment about the UID and GID then I'm ok with this change in general. Although I am still surprised that the GCC version thingy is causing a break - I think there's something else fishy. But if this is giving more reliable results then yeah let's go for it.
Although if you can expand in the commit message on how the break happens (paste an error message or something) that'd be great.

Although I am still surprised that the GCC version thingy is causing a break - I think there's something else fishy

It's just that Kconfig runs some autodections on the version of GCC that is being used and has a notion of GCC plugins somehow, that gets enabled/disabled. It's not a purely lexical operation on the config file, it does other things in the background as well

@qais-yousef Updated with sample output of Kconfig issues

make olddefrconfig requries ARCH=arm64 yes because you must always specify the arch when running any config config including menuconfig. Why this is bad? You can't skip this really as it is by design required. Otherwise it'll pick the host architecture by default and apply x86 configs - which will screw things up

My original script had setting the arch bit - not sure why it disappeared in next. I think this is the real problem you're trying to fix here?

Looks like kconfig fragments just try to merge config files when called with -m, without trying to understand what is supposed to be there or not, or what are the possible dependencies. Haven't found a lot of documentation around that, and grepping for fragment or merge_config in Documentation/ does not give any relevant result.

My original script had setting the arch bit - not sure why it disappeared in next. I think this is the real problem you're trying to fix here?

So we have multiple solutions here:

As you suggest, define ARCH=arm64 when calling merge_config.sh without -m. That misdetects GCC version (it picks up the host compiler version), but that seems fixed under the hood quietly when running ARCH=arm64 make Image. CROSS_COMPILE is not needed when doing that, which is ideal.
Set a couple of options that have a default as done in that PR, which is not great since we have to maintain that copy/paste of Kconfig defaults.
Set CONFIG_INITRAMFS_SOURCE, call merge_config.sh with-m, and when building the kernel, call make in an equivalent way to what merge_config.sh would do without -m:

make olddefconfig Image dtbs

Options 2) and 3) have the benefit of not having to set either ARCH or CROSS_COMPILE when updating the conf file, but a base config is needed, which itself would need ARCH anyway.
Option 1) is probably the best one as it fully decouples config file creation from building the kernel itself, I'll make the corresponding change in that PR to bring back ARCH autodection.

When dealing with configs ARCH is compulsory and usually inferred to be the host's arch if not specified by the user. Cross compile is not important if you're just executing config related comamnds ie: defconfig, menuconfig, olddefconfig, savedefconfg etc. So re-instating the ARCH setup is the right thing for sure as it's not really an optional argument.
Hopefully I looked at the right version of your latest commit - mind updating the commit message to reflect the new findings?
Thanks for taking care of it :)

Yes, ARCH is definitely needed. CROSS_COMPILE is not needed but defining it to something stupid seems to make it fail, even though it's not supposed to be involved in the process:
>>> CROSS_COMPILE=foobar lisa-buildroot-update-kernel-config ~lisa/integration-lisa-next/src/buildroot/output/images/rootfs.cpio .
Assuming ARCH=arm64
Merging Kconfig fragment into ./.config
CONFIG_INITRAMFS_SOURCE="/home/dourai01/Data/Git/lisa/integration-lisa-next/src/buildroot/output/images/rootfs.cpio"
Using ./.config as base
Merging /tmp/tmp.3ImcjxrQfO
Value of CONFIG_INITRAMFS_SOURCE is redefined by fragment /tmp/tmp.3ImcjxrQfO:
Previous value: CONFIG_INITRAMFS_SOURCE=""
New value: CONFIG_INITRAMFS_SOURCE="/home/dourai01/Data/Git/lisa/integration-lisa-next/src/buildroot/output/images/rootfs.cpio"

/bin/sh: foobargcc: command not found
/bin/sh: foobargcc: command not found
scripts/kconfig/conf  --alldefconfig Kconfig
./scripts/gcc-version.sh: line 26: foobargcc: command not found
./scripts/gcc-version.sh: line 27: foobargcc: command not found
./scripts/gcc-version.sh: line 29: foobargcc: command not found
./scripts/gcc-version.sh: line 26: foobargcc: command not found
./scripts/gcc-version.sh: line 27: foobargcc: command not found
./scripts/gcc-version.sh: line 29: foobargcc: command not found
init/Kconfig:17: syntax error
init/Kconfig:16: invalid statement
init/Kconfig:17: invalid statement
./scripts/clang-version.sh: line 15: foobargcc: command not found
./scripts/gcc-plugin.sh: line 11: foobargcc: command not found
make[1]: *** [scripts/kconfig/Makefile:69: alldefconfig] Error 1
make: *** [Makefile:538: alldefconfig] Error 2
Value requested for CONFIG_INITRAMFS_SOURCE not in final .config
Requested value:  CONFIG_INITRAMFS_SOURCE="/home/dourai01/Data/Git/lisa/integration-lisa-next/src/buildroot/output/images/rootfs.cpio"
Actual value:     CONFIG_INITRAMFS_SOURCE=""

OK that is weird; maybe a regression in kernel build system somehow..
I'm happy with the change but if you can afford rewording the commit message to mention that the missing ARCH in make olddefconfig was causing the problem as I believe it's the rootcause that would be great.


MicroK8s installation is failing when using launch configurations (1.27.2)

Summary
Hello :)
I would like to setup a small MicroK8s cluster using the new "launch configurations" feature available since version 1.27. However, this doesn't work well when I want to automate the deployment using a config file delivered by Ansible before installing the snap.
Some informations about my setup :

OS : Ubuntu 22.04 LTS
Snap version : 2.59.4
MicroK8s channel : 1.27/stable

Here is my config file :
root@mk8s01:~# cat /etc/microk8s.yaml
---
version: 0.1.0
persistentClusterToken: my-token # I use a 32 characters length token
extraKubeAPIServerArgs:
  --authorization-mode: RBAC,Node
extraKubeletArgs:
  --cluster-dns: <IP_ADDRESS>
  --cluster-domain: cluster.local
addons:
- name: dns
- name: rbac
- name: metrics-server

Here is the error message I got :
root@mk8s01:~# snap install microk8s --classic --channel=1.27/stable
error: cannot perform the following tasks:
- Run install hook of "microk8s" snap if present (run hook "install":
-----
+ source /snap/microk8s/5372/actions/common/utils.sh
++ [[ /snap/microk8s/5372/meta/hooks/install == \/\s\n\a\p\/\m\i\c\r\o\k\8\s\/\5\3\7\2\/\a\c\t\i\o\n\s\/\c\o\m\m\o\n\/\u\t\i\l\s\.\s\h ]]
+ '[' -f /var/snap/microk8s/5372/var/lock/installed.lock ']'
++ /snap/microk8s/5372/bin/uname -m
+ ARCH=x86_64
+ export LD_LIBRARY_PATH=/snap/microk8s/5372/lib:/snap/microk8s/5372/usr/lib:/snap/microk8s/5372/lib/x86_64-linux-gnu:/snap/microk8s/5372/usr/lib/x86_64-linux-gnu
+ LD_LIBRARY_PATH=/snap/microk8s/5372/lib:/snap/microk8s/5372/usr/lib:/snap/microk8s/5372/lib/x86_64-linux-gnu:/snap/microk8s/5372/usr/lib/x86_64-linux-gnu
+ export PATH=/snap/microk8s/5372/usr/sbin:/snap/microk8s/5372/usr/bin:/snap/microk8s/5372/sbin:/snap/microk8s/5372/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/bin:/usr/local/bin
+ PATH=/snap/microk8s/5372/usr/sbin:/snap/microk8s/5372/usr/bin:/snap/microk8s/5372/sbin:/snap/microk8s/5372/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/bin:/usr/local/bin
+ export OPENSSL_CONF=/snap/microk8s/5372/etc/ssl/openssl.cnf
+ OPENSSL_CONF=/snap/microk8s/5372/etc/ssl/openssl.cnf
+ is_strict
+ cat /snap/microk8s/5372/meta/snap.yaml
+ grep -q strict
+ grep confinement
+ return 1
+ cat /proc/1/environ
+ grep container=lxc
+ cp -r --preserve=mode /snap/microk8s/5372/default-args /var/snap/microk8s/5372/args
+ mv /var/snap/microk8s/5372/args/certs.d/localhost__32000 /var/snap/microk8s/5372/args/certs.d/localhost:32000
+ '[' -e /var/lib/kubelet ']'
+ ln -s /var/snap/microk8s/common/var/lib/kubelet /var/lib/kubelet
+ echo '`/var/lib/kubelet` linked to /var/snap/microk8s/common'
`/var/lib/kubelet` linked to /var/snap/microk8s/common
+ mkdir /var/snap/microk8s/5372/certs
+ cp /snap/microk8s/5372/certs/csr.conf.template /var/snap/microk8s/5372/certs/csr.conf.template
+ mkdir -p /var/snap/microk8s/common/etc/launcher
+ for config_file in "/etc/microk8s.yaml" "$SNAP_USER_COMMON/.microk8s.yaml" "$SNAP_COMMON/.microk8s.yaml" "$SNAP/microk8s.default.yaml"
+ '[' -f /etc/microk8s.yaml ']'
+ echo 'Found config file /etc/microk8s.yaml, will use to initialize cluster.'
Found config file /etc/microk8s.yaml, will use to initialize cluster.
+ cp /etc/microk8s.yaml /var/snap/microk8s/common/etc/launcher/install.yaml
+ /snap/microk8s/5372/bin/cluster-agent init --pre-init --config-file /var/snap/microk8s/common/etc/launcher/install.yaml
Error: failed to apply configuration: failed to apply config part 0: failed to configure persistent token: failed to open /var/snap/microk8s/5372/credentials/persistent-cluster-tokens.txt: open /var/snap/microk8s/5372/credentials/persistent-cluster-tokens.txt: no such file or directory
Usage:
   init [flags]

Flags:
  -c, --config-file string   configuration file to read, or '-' to read from stdin
  -h, --help                 help for init
  -p, --pre-init             apply pre-init configuration, do not restart services or manage addons
-----)

It's working fine without the persistentClusterToken directive, so I guess this is related with a missing "copy" in /var/snap/microk8s/5372/credentials/persistent-cluster-tokens.txt file during the bootstrap.
Reproduction Steps

Create config file in /etc/microk8s.yaml or /root/snap/microk8s/common/.microk8s.yaml
snap install microk8s --classic --channel=1.27/stable

Introspection Report
Can't provide it since the installation is failing
Thanks :)

Hi @f-bn
Thank you for reporting this. The issue is with the persistentClusterToken line. We try to append the provided token but the token's file is not created yet.
As a temporary workaround while we patch and release the fix for the problem you can set the persistentClusterToken after the installation of the snap:
With:
$ sudo cat /etc/microk8s.yaml
---
version: 0.1.0
extraKubeAPIServerArgs:
  --authorization-mode: RBAC,Node
extraKubeletArgs:
  --cluster-dns: <IP_ADDRESS>
  --cluster-domain: cluster.local
addons:
- name: dns
- name: rbac
- name: metrics-server

And:
$ cat ./microk8s-token.yaml
---
version: 0.1.0
persistentClusterToken:<PHONE_NUMBER>1234567890123456789012

Do:
sudo snap install microk8s --classic
sudo microk8s status --wait-ready
sudo snap set microk8s config="$(cat microk8s-token.yaml)"

Apologies for the inconvenience.

Hi @ktsakalozos
No problem, thanks for the quick workaround :)


ARTEMIS-3770 refactor MQTT handling of client ID

It would be useful for security manager implementations to be able to
alter the client ID of MQTT connections.
This commit supports this functionality by moving the code which handles
the client ID ahead of the authentication code. There it sets the
client ID on the connection and thereafter any component (e.g. security
managers) which needs to inspect or modify it can do so on the
connection.
This commit also refactors the MQTT connection class to extend the
abstract connection class. This greatly simplifies the MQTT connection
class and will make it easier to maintain in the future.

@riccardomodanese, does this change work for you?

it works for me.
I tried again with the full Kapua ServerPlugin and SecurityPlugin using the Artemis 2.23.0-SNAPSHOT(updated in the morning) + your commit.
Both the "normal stealing link" and the "multi tenant" are handled correctly (in the second case both the clients are able to stay connected).
With your fix I don't see exceptions thrown by Paho client while, for example, 10 clients are connecting at the same time with the same clientId. The client connects and soon after its status changes to disconnect "softly"
I'll do few more tests in the next days.

About the exception raised by Paho I think it's a good news (but I'm not so deep into MQTT specifications to be sure).
I mean, in one my tests there are n clients connecting more or less at the same time with the same clientId.
The test scope is to check that only one client is still connected after a while and all the clients were able to connect.
Before your fix I noticed a lot of exceptions (n-1) during the connect calls.
Now no client is throwing exception during its connect call.
I think it's right since the MQTT protocol says that the previous client with the same clientId should be disconnected. Not the current one.
Unfortunately I cannot run the Kapua ITs on our ci against Artemis snapshot but the manual test I did today confirmed me the fix is fine.
I added a test to connect n clients (with delay between one connection and the others) with the same clientId but on different accounts (so the Kapua security plugin will change the clientId with accountId:clientId)
All the n clients are able to connect and stay connected together.
From the plugin log I can see
### authorizing address: $EDC/stealing-link-7/client-stealing-multi-account/#::e2w9YPXivHY|client-stealing-multi-account.$EDC/stealing-link-7/client-stealing-multi-account/# - check type: CONSUME
### authorizing address: $EDC/stealing-link-7/client-stealing-multi-account/#::e2w9YPXivHY|client-stealing-multi-account.$EDC/stealing-link-7/client-stealing-multi-account/# - check type: CREATE_DURABLE_QUEUE

and that's right since the clientId in the durable queue address is (accountId:clientId):
e2w9YPXivHY|client-stealing-multi-account
Just one last question about the ETA.
Are you expecting to release this fix with the 2.23?
Thanks a lot!

Are you expecting to release this fix with the 2.23?

Yes.

Hello, this pr looks like closed without merging.
Did you fix the related issue with another pr?
Thanks!

@riccardomodanese, it was merged. See 446ff61542f47f50c2299d8ef1cae8fe2b98a5ad.


Templating: node with ws-replace and ws-template disappears from parent template

Invalid -- this was a misdiagnosed case of #106.


0.30.0 release roadmap

Things to do and iterate on with alphas before the actual release

[x] prototype upgrade of SCTK -- https://github.com/Smithay/client-toolkit/pull/215
[x] prototype upgrade of Smithay -- https://github.com/Smithay/smithay/pull/454
[x] Full pass on documentation (including readmes)

[x] wayland-sys
[x] wayland-backend
[x] wayland-scanner
[x] wayland-client
[x] wayland-server
[x] wayland-egl
[x] wayland-cursor
[x] wayland-protocols
[x] main readme of the repo

[x] deny unsafe_op_in_unsafe_fn
[x] split wayland-protocols into multiple crates
[x] https://github.com/Smithay/wayland-rs/issues/448
[x] server: don't require a DataInit initialization if the created object is already destroyed on callback return (for example if a protocol error was triggered) -- https://github.com/Smithay/wayland-rs/pull/458
[x] Remove generic argument from ClientData or provide state in its callbacks
[x] https://github.com/Smithay/wayland-rs/pull/497
[ ] Find a way to improve wayland-client's event_created_child!()
[x] Implement with_all_objects_for on the server/sys backend
[x] Investigate if DelegateDispatch can be fused with Dispatch : https://github.com/Smithay/wayland-rs/pull/518
[x] Fix all remaining TODOs

And non-blocking, but overall useful thing to do: improve code coverage by writing more tests, see https://app.codecov.io/gh/Smithay/wayland-rs

We should probably set deny for the unsafe_op_in_unsafe_fn lint.
Fyi this is going to become default or already is in 2021 edition.

Pending a new release of nix to fix the sigpipe signal issue since the new constants are not in nix yet: https://github.com/Smithay/wayland-rs/issues/457
I think we could use libc though for now to temporarily fix that problem>

It seems like a nix release might not be too far away? https://github.com/nix-rust/nix/milestone/9

split wayland-protocols into multiple crates

This has been done

backend::sys::client::Backend::from_foreign_display()

Once this is in, how does one get the WlDisplay?. Or alternatively, if I start with a ptr to a wl_surface how do I make use of this api and get a WlSurface.

Is there any migration guide for 0.29.* to the current version?

There is no proper guide (yet), but you can refer to this comment for an overview of what changed


Separating Ghost from Atomic computations in Steel

This PR provides a clean separation between Ghost computations in Steel (with the SteelGhost effect) and atomic computations (with the SteelAtomic effect), to help with erasure during extraction of SteelGhost computations.
The representations of the two effects are semantically identical, and there is a lift from SteelGhost to SteelAtomic.
SteelAtomicBase computations are still indexed by the observability bit. This is needed to compose lifted ghost computations with atomic computations. The actual SteelAtomic(F) effect that users should use does not have this bit exposed, a SteelAtomic computation is always observable (if not, users should use SteelGhost).
This change prevents effect polymorphism between SteelGhost and SteelAtomic; for instance, we now need two versions of with_invariant. I believe this is acceptable, in exchange for a cleaner extraction story.

Approved by @aseemr on Slack


404 Error: getaddrinfo ENOTFOUND https https: 80

Hello,
I have Cors-anywhere hosted in a docker container on a server that receives traffic directed as a rewrite from another container running apache.  The apache container runs a web app, and upon being loaded in the browser, sends requests via a proxy to cors-anywhere like:
https:///cors-anywhere/https://.../
A simple rewrite rule in the apache container directs traffic to the container running cors-anywhere:
RewriteRule "^/cors-anywhere/(.*)$" "http://${CORS_ANYWHERE_SERVER_HOST}:${CORS_ANYWHERE_SERVER_PORT}/$1" [P,NC,L]
When run locally, everything works fine.  However, when hitting the server,  I get this response:
Not found because of proxy error: Error: getaddrinfo ENOTFOUND https https: 80
I am aware that an issue was raised with an identical error, but I don't know how to address it in apache.  Furthermore, I don't necessarily think the causes are the same either.
Possible related issue #167

The issue is the same: You're using normalized URLs.
You should be looking for the raw values instead. I suppose that you can reconstruct the raw URL with %{REQUEST_URI} and %{QUERY_STRING} or even %{THE_REQUEST} (in RewriteCond) and then refer to the captured groups from the regexp with %1, %2, etc.
See the documentation at https://httpd.apache.org/docs/current/mod/mod_rewrite.html#RewriteCond

Thank you, @Rob--W !
My solution:
RewriteCond "%{REQUEST_URI}" "\/cors-anywhere\/https:\/(.*)"
RewriteRule "^/cors-anywhere/(.*)$" "http://${CORS_ANYWHERE_SERVER_HOST}:${CORS_ANYWHERE_SERVER_PORT}/https://%1" [P,NC,L]
Note above that RewriteCond still requires searching against a single slash (https:/) instead of (https://).  If you use %{THE_REQUEST} it will be a raw url (requiring you to search for https://).  The %{REQUEST_URI} I am using will also include query params for me.
Furthermore, I was not able to stack RewriteCond lines and extract multiple capture groups for each line and having a reference to them (e.g. using %1 for a capture group for the first RewriteCond, %2 for the second RewriteCond).  That approach did not work, so my solution was driven by that limitation.

Hi!
I'm working on angular project and from there I'm trying to post some logs to a server, but while hitting that server I got CORS error, and on searching I found that if I append https://cors-anywhere.herokuapp.com with my URL it'll work.
So after adding it my CORS error gone but now I'm getting proxy error like this:-  Not found because of proxy error: Error: getaddrinfo ENOTFOUND ..com.
This is my code snippet
const response: any = await axios.post(LOGNESS_LOG_EVENT_URL, event, {
headers: EVENT_HEADERS(bearer),
});
and my LOGNESS_LOG_EVENT_URL is as :- https://cors-anywhere.herokuapp.com/https://********.
Please provide soln to this as I got stuck here.

Hello, I'm getting the same problem using Apache (the help page appears every time):
<VirtualHost *:443>

    ServerName cors-anywhere.androz2091.fr

    ProxyPass / http://localhost:3700/
    ProxyPassReverse / http://localhost:3700/

    LogLevel warn
    ErrorLog ${APACHE_LOG_DIR}/cors.androz2091.fr.log
    CustomLog ${APACHE_LOG_DIR}/cors.androz2091.fr.log combined

</VirtualHost>

What should I use?

Hello, I'm getting the same problem using Apache (the help page appears every time):
<VirtualHost *:443>

    ServerName cors-anywhere.androz2091.fr

    ProxyPass / http://localhost:3700/
    ProxyPassReverse / http://localhost:3700/

    LogLevel warn
    ErrorLog ${APACHE_LOG_DIR}/cors.androz2091.fr.log
    CustomLog ${APACHE_LOG_DIR}/cors.androz2091.fr.log combined

</VirtualHost>

What should I use?


How to set the current time

Thanks for your awesome job on wavesurfer.js!
I found there's only how to get current time, but there's no way to set current time. I'm not sure if I didn't find it, or we don't have this function right now?
Any ideas?
Thanks,
Shaojin

@burningding The way it's done in the region examples is:
wavesurfer.play(region.start);
wavesurfer.pause();
You can replace region.start with the number of seconds.

@dmongrel Sorry for the ambiguous narration of question. In my case, I want to set the position of cursor (the current time) to the mid of region (the average between region.start and region.end). How can I achieve this?
Thanks!

You could also try
wavesurfer.seekTo(timeToSet / wavesurfer.getDuration())
where timeToSet is the number of seconds. This shouldn't fire pause and play events.

@burningding you can set it with seekTo() method or with play(); pause() combined. I'll add a method called setCurrentTime() this weekend.

@entonbiba @nelemnaru Thanks for your help! Looking forward the new version!

@nelemnaru  @entonbiba I tried to use
var sec = wavesurfer.getDuration();   wavesurfer.seekTo((4/sec)+(12/sec)*.5);
to set the current time, it works well.
Now I want to drag to add a region and also set the current time to the mid of the region. I tried to add the code above to the event "region-update-end", it's true that the cursor will be set to the mid when "region-update-end" is fired. However,  it seems that another mouse event is also fired, so at last, the cursor will be set to the place where I release the mouse. I also tried to use stopPropagation as well as stopImmediatePropagation in "region-update-end" event, but it doesn't work. Any idea on it?
Thanks!

@burningding so when you drag the region, you want it to set the play time in the middle or ?
The event region-update-end should work, can you post a sample on codepen?

I have a similar problem trying to play a region on double click, and stopPropagation doesn't help. It starts playing the region, but the cursor ends up moving to where I clicked. Currently, I'm using a workaround by using a setTimeout delay of 0.
`wavesurfer.on('region-dblclick', function (region, e) {
e.stopPropagation();
setTimeout(function(){
	region.play();
}, 0);

});`
You could try setting a 0 timeout on your code until the issue is solved.

@nelemnaru you can use e.stopImmediatePropagation(); instead,
wavesurfer.on('region-dblclick', function (region, e) {
    e.stopImmediatePropagation();
    region.play();
});

@entonbiba I tried your suggestion to no avail. The region still begins playing from where I double-clicked instead of region start. (Don't know if it matters, but I'm using Firefox.)

@nelemnaru updated, just remove the `region.play();' part from the code
wavesurfer.on('region-dblclick', function (region, e) {
    e.stopImmediatePropagation();
    // code here
});


Implement verify_kzg_proof function body

Codecov Report

Merging #18 (e108984) into main (ea3a858) will decrease coverage by 1.17%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
- Coverage   90.32%   89.16%   -1.17%
==========================================
  Files          41       40       -1
  Lines        5291     5360      +69
==========================================
  Hits         4779     4779
- Misses        512      581      +69

Impacted Files
Coverage Δ

src/commitments/kzg.rs
66.90% <ø> (ø)

src/lib.rs
0.70% <0.00%> (-0.79%)
:arrow_down:

src/math/errors.rs
100.00% <ø> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix README doc for SIM111.

The warning message for SIM111 is correct, but the documented example for it isn't.
Example 2 in the closed Issue #15 should be edited too, since it's also linked from the documentation.

Thank you very much!


Cardinal components API 4.0.0 jar seems to be missing modules

The jar on curseforge seems to have only two modules inside of it, whereas the 3.1.1 version has all of the modules. I don't see anything about this on the changelog, so not sure exactly what is going on. Do we need to download all of the individual modules from now on?

it in fact doesn't have any of CCA's modules, thanks for catching that.
seems like loom changed stuff and broke the CI pipeline

@UpcraftLP I fixed some 1.18 release changes in my fork (https://github.com/skerit/Cardinal-Components-API/commit/cf4e5713ac51ee4750a08f3632cbffdd1bf4f701) but when I build the project I don't get any usable jars.
Is this related?

@UpcraftLP @miyo6032 I reverted the changes in the build.gradle script to the ones from this commit: https://github.com/OnyxStudios/Cardinal-Components-API/blob/585360f93d8172ba8f69ce75580112a98f9a3baa/build.gradle, now assembling the project works again. Tests don't want to run though, so I have to use the gradle assemble tasks to get the jar.

I just want to note I also ran into this trying to install Victus in our modpack.

You say the release of 4.0.1, but the .jar is incorrect on github and it's not available on curseforge either, so there's no way to check.

Should be fine now


Made Qt5-msvc-code MSVC-only

Before CMake would fail with not finding the MSVC Qt5 Discovery file when accidentally not having Qt5 installed

Yesterday I installed a virtual Feren OS (out of curiosity), which is a Ubuntu/KDE-based Linux.
Feren OS
On this new installation eCAL build failed with this CMake error:
CMake Error at CMakeLists.txt:198 (autodetect_qt5_msvc_dir):
  Unknown CMake command "autodetect_qt5_msvc_dir".

I applied this solution, but id didn't work me:
CMake Error at CMakeLists.txt:156 (_find_package):
  By not providing "FindQt5.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Qt5", but
  CMake did not find one.

  Could not find a package configuration file provided by "Qt5" with any of
  the following names:

    Qt5Config.cmake
    qt5-config.cmake

  Add the installation prefix of "Qt5" to CMAKE_PREFIX_PATH or set "Qt5_DIR"
  to a directory containing one of the above files.  If "Qt5" provides a
  separate development package or SDK, be sure it has been installed.
Call Stack (most recent call first):
  lib/CustomQt/CMakeLists.txt:21 (find_package)

I saw an Ask Ubuntu question:
What package do I need to build a Qt 5 & CMake application?
I installed apt-file, and then with apt-file:
$ apt-file search Qt5Config.cmake
libaccounts-qt5-dev: /usr/lib/x86_64-linux-gnu/cmake/AccountsQt5/AccountsQt5Config.cmake
libphonon4qt5-dev: /usr/lib/x86_64-linux-gnu/cmake/phonon4qt5/Phonon4Qt5Config.cmake
libsignon-qt5-dev: /usr/lib/x86_64-linux-gnu/cmake/SignOnQt5/SignOnQt5Config.cmake
libtelepathy-qt5-dev: /usr/lib/x86_64-linux-gnu/cmake/TelepathyQt5/TelepathyQt5Config.cmake
qtbase5-dev: /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake
qtbase5-gles-dev: /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake

$ sudo apt install qtbase5-dev

$ ls -l /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake
-rw-r--r-- 1 root root 1606 Mär 19 02:19 /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake

After this installation, cmake gave no problems with or without this commit.

@OrhanKupusoglu: That's exactly what is supposed to happen. With this fix it at least failes with the proper "Qt was not found" message. We obviously cannot do anything about that - if Qt is not installed it cannot be found. 👍


Add font size options to Windows/Linux

Adding the font size options to Windows/Linux, tested on Windows 10.  There is just a lack of windows contributors. If an osx dev touches the windows menu he/she has no way to test it properly so.. we need your help
thx

@davibe I understand that, I was kidding in the comment. Sorry if it came off as rude, I really didn't mean anything by it.

I know you were kidding, you were not rude at all. I just like to explain :)


Don't call compose module update_on_recipient_change

I noticed another simple import cycle today; the input_pill low-level UI component module has a hardcoded call into the compose box subsystem: compose.update_on_recipient_change (Though that function is about to move a compose_recipient module).
This seems to be in order to cause the fading of conversations that don't match the current compose recipient with a non-empty compose box to update.
It was introduced in 5a4318d046e0409c4c042bc94ff606b27c99fd9b. I'm not sure what the cleanest fix is; one possibility would be to register an on-exit hook, but I think that's still a very weird model. We should instead be having the compose_fade component register a general on-change handler -- and may already have one, because this probably updates correctly when you add a new pill, and that doesn't seem to involve any code in the input_pill module, so we should probably figure that out in order to address this. I suppose one possibility is that we can just delete this line and it'll keep working.
Tagging as a priority, since we're generally trying to remove import cycles.

I checked this and it seems it stops working as intended by just removing this function call, so we will have to figure out something else.

@timabbott  Upon closer inspection, I found out this is the code in compose.js initialization method responsible for correctly updating fading when we add a new pill:-
export function initialize() {
    $("#below-compose-content .video_link").toggle(compute_show_video_chat_button());
    $(
        "#stream_message_recipient_stream,#stream_message_recipient_topic,#private_message_recipient",
    ).on("keyup", update_on_recipient_change);
    $(
        "#stream_message_recipient_stream,#stream_message_recipient_topic,#private_message_recipient",
    ).on("change", () => {
        update_on_recipient_change();
        compose_state.set_recipient_edited_manually(true);
    });

Specifically, the on-change handler.
It is due to the fact that when adding an input pill the selected elements do get changed which triggers the on-change callback, but it is not the case when we remove a pill, I have attached a video showcasing that:-
https://user-images.githubusercontent.com/84276404/230542225-9e5d2003-6898-4945-8afa-4ea5db47c003.mp4

This can be fixed by manually triggering a "change" event in removePill method in input_pills.js like so:-
store.$input.trigger("change");

Should I go ahead and open a PR with this change?

Yeah that sounds great -- please include a comment with a reference to the function in compose.js so that it's still easy to trace what this is doing.

Alright I will open the PR, also will stack the migration of input_pill.js to TypeScript in the same PR!

@zulipbot claim


Missing site navigation

The lack of navigation to move around the e-book site is considered an accessibility issue (see WCAG 2.2 Level AA: Multiple Ways).
Consider adding navigation at the top or even making the Lullabot logo link to the homepage of the ebook site rather than lullabot.com. When you're in an e-book, a link back to the table of contents for that ebook would also be really useful.

Resolved by #20.


feat: Add UUID to DynamoDB table to prevent ID conflicts

Describe the feature
currently, the dynamodb table used in the amazon chime sdk meeting summarizer app defines call_id as the partition key and scheduled_time as the sort key. to enhance data integrity and avoid potential id conflicts, there is a need to introduce a universally unique identifier (uuid) for each entry in the table.
Use Case
when changing the time format here, we will increase the chance to have conflicts.
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request.

CDK version used.
2.133.0
Node.js Version
v20.11.1
Environment details (OS name and version, etc.).
MacOS Sonoma 14.3.1

Discussed. Not necessary.


Upgrade org.postgresql:postgresql 42.2.13 -> 42.2.14

This PR contains the following updates:

Package
Update
Change

org.postgresql:postgresql (source)
patch
42.2.13 -> 42.2.14

Release Notes

pgjdbc/pgjdbc
v42.2.14
Changed

Reverted com.github.waffle:waffle-jna, org.osgi:org.osgi.core, org.osgi:org.osgi.enterprise dependencies to optional=true in Maven PR 1797.

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

Suggested commit message:
Upgrade PostgreSQL JDBC 42.2.13 -> 42.2.14

See:
- https://github.com/pgjdbc/pgjdbc/blob/master/CHANGELOG.md
- https://github.com/pgjdbc/pgjdbc/compare/REL42.2.13...REL42.2.14


add reconsume times header

Describe what this PR does / why we need it
消费者需要利用重试次数做一些自定义动作
Does this pull request fix one issue?

Describe how you did it
在转换成Spring Message消息前，添加到Rocketmq消息头中
Describe how to verify it
获取在消费者com.alibaba.cloud.stream.binder.rocketmq.RocketMQBinderConstants#ROCKETMQ_RECONSUME_TIMES消息头
Special notes for reviews

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Error while attempting to request for new icon

About this discussion
While requesting for new icon from both app and github , I am getting an error, attaching the screenshot below

Requests have been suspended since November anyway, so we'll make a new form later.

^ later? When will i ever be able to request icons
I'll wait ig


COUNTWINDOW support

Refer to Flink COUNTWINDOW

Tumbling count window
COUNTWINDOW(100), it will collect 100 events in a window and evaluate the window when the 100th element has been added.

Sliding count window
COUNTWINDOW(100, 1),  sliding count window of 100 elements size and 1 element trigger interval.

Supported & close the issue.


Fix lint job on main

Codecov Report

Merging #7079 (9a97064) into main (8e06fe9) will increase coverage by 0%.
The diff coverage is 22%.

:exclamation: Current head 9a97064 differs from pull request most recent head 903467b. Consider uploading reports for the commit 903467b to get more accurate results

@@          Coverage Diff          @@
##            main   #7079   +/-   ##
=====================================
  Coverage     64%     65%
=====================================
  Files        362     362
  Lines      22873   22873
  Branches    3420    3420
=====================================
+ Hits       14854   14885   +31
+ Misses      6726    6688   -38
- Partials    1293    1300    +7

Impacted Files
Coverage Δ

src/client/datascience/types.ts
100% <ø> (ø)

src/client/debugger/jupyter/kernelDebugAdapter.ts
4% <0%> (ø)

src/client/debugger/jupyter/debuggingManager.ts
33% <50%> (ø)

src/client/debugger/jupyter/debuggingCellMap.ts
100% <100%> (ø)

...lient/datascience/jupyter/kernels/cellExecution.ts
70% <0%> (+<1%)
:arrow_up:

src/client/datascience/jupyter/jupyterNotebook.ts
52% <0%> (+<1%)
:arrow_up:

...ient/datascience/editor-integration/codewatcher.ts
68% <0%> (+<1%)
:arrow_up:

...datascience/editor-integration/cellhashprovider.ts
70% <0%> (+<1%)
:arrow_up:

...datascience/editor-integration/codelensprovider.ts
66% <0%> (+2%)
:arrow_up:

src/client/terminals/codeExecution/helper.ts
18% <0%> (+5%)
:arrow_up:

... and 1 more


linux cmake project , IntelliSense can't find the std header

I read the "IntelliSense for remote headers (Visual Studio 2017 version 15.7 and later)" topic, do it.
But the problem is also exists.
And I can start and attach the bin via VS, I don't know why the IntelliSense  don't find the std header.

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

ID: c76faa92-c3bc-f26a-e4d6-24c037793ce3
Version Independent ID: 0f60b926-5fc4-5013-1459-deb032f84826
Content: Configure a C++ Linux project in Visual Studio
Content Source: docs/linux/configure-a-linux-project.md
Product: visual-cpp
GitHub Login: @mikeblome
Microsoft Alias: mblome

@iclodq The documention is correct here as far as I can tell. Please post your issue on https://developercommunity.visualstudio.com/spaces/8/index.html to get help from the product team or community.


Docker: Error response from daemon

Hey @urmzd,
Thanks for creating this Github Action.
I tried to use it but I'm running into an error I was hoping you can help me with.
When executing Run<EMAIL_ADDRESS>I get the following error :

/usr/bin/docker run --name c0442643e160ff2544d5f834adbbe709bd189_d0ace6 --label 6c0442 --workdir /github/workspace --rm -e "INPUT_MARKDOWN-FILES" -e "INPUT_COMMIT-MESSAGE" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/hcph-protocol/hcph-protocol":"/github/workspace" 6c0442:643e160ff2544d5f834adbbe709bd189  "synchronizing code in data-storage.md" "data-storage.md"
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./src/entrypoint.sh": stat ./src/entrypoint.sh: no such file or directory: unknown.
time="2023-04-19T13:30:21Z" level=error msg="error waiting for container: context canceled"

The yml file I wrote to run the Github action is as follows:

name: Embed code in markdown
on:
push:
branches:
- mkdocs
- fix/refine_PACs_info
jobs:
embed-code:
runs-on: ubuntu-latest
steps:
- name: "Checkout current repo"
uses: actions/checkout@v3
- name: "Run entrypoint script."
uses<EMAIL_ADDRESS>id: "embed-code"
with:
markdown-files: "data-storage.md"
commit-message: "synchronizing code in data-storage.md"

Do you have an idea what's wrong ?

First of all, thank you for creating an issue! This is a bug, the entry-point referenced in the dockerfile is incorrect. I'll be fixing this shortly. See issue #2

Going to leave this open, until you've verified that its working. Cheers, Urmzd

Hey @urmzd,
Thank you for the quick response. Unfortunately I'm still running into the same issue while calling uses<EMAIL_ADDRESS>(and not changing anything else from the ymal file above) :/

Hi @celprov sorry for the late response, I'll take a look at this on Tuesday and try resolving it. Thank you for your patience! In the meanwhile, you might be able to use the script manually (located in root) as part of your pipeline.
Something along the lines of
embed:
  embed-code:
    steps:
      - name: Run build script
        run: ./the-build-script-mentioned-above.sh
        shell: bash

@celprov I'm sorry for the wait... 😓
Though, I've finally come back to it and finished it (if you still want to try it).
# examples/example.yml

name: "Example"

on: [release]

jobs:
  embed-example:
    runs-on: ubuntu-latest
    steps:
      - name: "Checkout current repo"
        uses: actions/checkout@v3
      - name: "Run entrypoint script."
        uses<EMAIL_ADDRESS>        id: "embed-code"
        with:
          markdown-files: "README.md"
          commit-message: "chore: embed example using self"
          commit-name: Urmzd Mukhammadnaim
          commit-email<EMAIL_ADDRESS>          commit-push: "false"


Uncaught ObjectDisposedError: Object has been disposed

Press enter at a randomly time
Atom Version: 1.4.1
System: Unknown Windows Version
Thrown From: Atom Core
Stack Trace
Uncaught ObjectDisposedError: Object has been disposed
At C:\Users\user\AppData\Local\atom\app-1.4.1\resources\app.asar\node_modules\text-buffer\lib\text-buffer.js:810

undefined

Commands
     -1:02.3.0 core:move-up (atom-text-editor.editor.mini.is-focused)
     -0:57.1.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:57.1.0 core:cancel (atom-text-editor.editor.mini.is-focused)
  3x -0:54.5.0 omnisharp-atom:toggle-dock (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
  3x -0:45.1.0 omnisharp-atom:solution-status (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -0:39.5.0 omnisharp-atom:restart-server (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
  3x -0:30.9.0 omnisharp-atom:dock-toggle-errors (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -0:25.5.0 omnisharp-atom:next-solution-status (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -0:23.1.0 omnisharp-atom:previous-solution-status (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -0:20 omnisharp-atom:dock-toggle-errors (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
  2x -0:14 omnisharp-atom:toggle-dock (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -0:07.1.0 omnisharp-atom:solution-status (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -0:04.6.0 core:delete (atom-text-editor.editor.is-focused)
     -0:04.3.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:02.9.0 core:undo (atom-text-editor.editor.is-focused)
  6x -0:02.4.0 editor:newline (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "audioBeep": false,
    "autoHideMenuBar": true
  },
  "editor": {
    "invisibles": {}
  }
}

Installed Packages
# User
atom-yeoman, v0.3.15
json-schema, v0.1.15
linter, v1.11.3
omnisharp-atom, v0.26.9

# Dev
No dev packages

There seem to be a lot of uncaught exceptions with omnisharp-atom installed.

I am getting this a lot for when I just have Unity scripts opened
[Enter steps to reproduce below:]

...
...

Atom Version: 1.6.1
System: linux 4.4.5-1-ARCH
Thrown From: Atom Core
Stack Trace
Uncaught ObjectDisposedError: Object has been disposed
At /usr/share/atom/resources/app.asar/src/pane.js:896

undefined

Commands
 19x -2:20.3.0 core:backspace (atom-text-editor.editor.omnisharp-editor.is-focused)
     -2:09.1.0 autocomplete-plus:confirm (atom-text-editor.editor.omnisharp-editor.is-focused.autocomplete-active)
 14x -2:06.6.0 core:backspace (atom-text-editor.editor.omnisharp-editor.is-focused)
  3x -2:05.1.0 autocomplete-plus:confirm (atom-text-editor.editor.omnisharp-editor.is-focused)
 14x -2:02.2.0 core:backspace (atom-text-editor.editor.omnisharp-editor.is-focused)
  2x -1:56.9.0 autocomplete-plus:confirm (atom-text-editor.editor.omnisharp-editor.is-focused.autocomplete-active)
     -1:51.9.0 autocomplete-plus:cancel (atom-text-editor.editor.omnisharp-editor.is-focused.autocomplete-active)
  5x -1:51.6.0 autocomplete-plus:confirm (atom-text-editor.editor.omnisharp-editor.is-focused)
     -1:44.9.0 core:save (atom-text-editor.editor.omnisharp-editor.is-focused)
     -1:41.4.0 core:backspace (atom-text-editor.editor.omnisharp-editor.is-focused)
     -1:41.1.0 core:save (atom-text-editor.editor.omnisharp-editor.is-focused)
     -0:39.2.0 omnisharp-atom:restart-server (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
  3x -0:34.9.0 core:backspace (atom-text-editor.editor.is-focused.omnisharp-editor)
  2x -0:25.5.0 autocomplete-plus:confirm (atom-text-editor.editor.is-focused.omnisharp-editor.autocomplete-active)
     -0:22.2.0 autocomplete-plus:cancel (atom-text-editor.editor.is-focused.omnisharp-editor.autocomplete-active)
  4x -0:19.9.0 core:save (atom-text-editor.editor.is-focused.omnisharp-editor)

Config
{
  "core": {},
  "editor": {
    "fontSize": 13,
    "invisibles": {},
    "tabLength": 4
  }
}

Installed Packages
# User
atom-yeoman, v0.3.15
json-schema, v0.1.15
linter, v1.11.3
omnisharp-atom, v0.26.13

# Dev
No dev packages


node process uses 100% of CPU

it happens consistenly with node v0.12.2

I'm experiencing this as well.

I had to remove the package, it makes sublime unusable.

Same here

Same here

:+1:

:+1:

Not 100% sure why, but simply re-installing jshint via npm seems to have fixed the issue for me.
Haven't seen the 100% CPU issue in the last 3 days.
Here's the command I used:
$ sudo npm install -g jshint

@alexblunck it will be back don't worry, tired multiple times stays away for a while then kicks back in.

@kilianc You're right, it's back.

This is happening for me also with io.js 2.0.2

+1

+1 CPU usage %100

+1

It actually seems like the node process sticks around after closing sublime. So if you close sublime and reopen it, you now have 2 node processes, etc. And once you start going down that route the cpu usage grows quickly.

@kbjr if you are saying that the reason why we see high CPU usage is because the processes stack up on each sublime run, that is not correct.
Every node process spawned by sublime takes 100% CPU, I recall killing a couple of node processes manually but I am not sure if orphan node processes are just a side effect of node hanging or happens systematically.
Either way this needs to be fixed ASAP.

@kilianc When I looked at it, I had 4 separate node processes taking 25% each. Killing each one helped, no one process seems able to take 100% for me.
I do agree though. Regardless, this needs a fix.

If we are to look into this, we need to find a common factor. So far people are just adding +1's What we need is for people to at least give their versions of node, jshint and sublimelinter-jshint.
Any other related info is also welcome, like does it happen all the time, or only after it encounters some specific error, or after a specific duration etc etc.
I personally are not seeing any of this with node 0.10.25 and jshint 2.7.0 and latest version of this plugin.

@mokkabonna v0.10.25 has been released on 01/23/2014 -_- not really a good reference for debugging. Is that the last supported version?
I am on latest node v0.12.4 stable on mac.
No specific error, just crazy CPU.

This plugin really only have requirements of jshint 2.5.0 or later. Other than that it should work with any node really, meaning any node that can run 2.5.0 of jshint.
So 0.10.25 is as good as any really.

jshint v2.7.0 here

I have node v0.12.2 on mac, running jshint v2.7.0 and latest version of the plugin and I'm getting the issue.

I have io.js v2.0.2 and jshint v2.7.0. I have had no luck finding out how to consistently reproduce this. When it happens there is a iojs/node process running with 100% CPU and the highlighting stops working. Killing the process will make the highlighting work again on subsequent saves.
My best guess is that it happens when you rapidly save the file, so a background lint is running during the save, but that is just a guess.

I'm running<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

+1 :)
Hope this could help a bit :) Not sure when is crashes tho.. Randomly my mac start making helicopter sound.
node v0.12.4 and jshint v2.7.0.
ps aux | grep node
User          8055  99.7  0.2  3067572  35040   ??  R     3:42PM 547:26.62 node /usr/local/bin/jshint --verbose --filename /path/to/file/login_ctrl.js --config /path/to/file/.jshintrc

Have anyone experienced this with other node based linters or just jshint?

Exact same issue on Ubuntu 15.04.

OSX v10.9.5
jshint v2.5.11
sublimelinter-jshint: v1.2.1
io.js 2.2.1
Seems to happen after a few hours of using Sublime.

Ok, bear with me here, but I think I found out how to recreate this...
I was working on this code today for my Camo project and had Activity Monitor running to try and catch when this happens. I ended up having to retype the code from line 484 multiple times and noticed that's when iojs would take up 100% of the CPU.
(Sorry, I tried to trim down the file but then I couldn't recreate the problem.)
Just follow the directions described by comments on lines 482 and 489 to do it. It seems like it happens more often when I let Sublime's autocomplete finish the longer words for me. Also, doesn't seem to happen until I type in the last semicolon on line 485.
Hope this helps. Let me know if you have any questions.

+1
node v0.10.25
jshint v2.7.0
Ubuntu 15.04

+1
node v4.0.0 (installed via nvm)
jshint v2.8.0
os x 10.10.5
I'm also having this issue when I'm writing the class keyword.

+1
node v4.1.0 & v4.2.1 (via nvm)
jshint v2.8.0
os x 10.10.5
I'm also having this issue when I'm writing the class keyword. (2)

+1

Constant 25% CPU usage per core. +1

main reason why I switched to atom TBH

Had the same issues and just found this ticket. I just updated to<EMAIL_ADDRESS>and the problem seems to be gone, at least for the class example given above. I'll keep an eye on it with our own codebase during the next day.s

I'm using Atom on Ubuntu 14.04 and I just noticed this issue as well. node v4.2.6

About once a day, I'll notice my laptop fans speed up and, like a notification, I open Activity Monitor to find & kill a "node" process floating around 100% CPU usage. If this happens while I still have Sublime Text open, I can see that JSHint is no longer provides feedback. Also, The process will stick around after ST is closed. I find this often happens after frequently switching tabs or writing new JS files; however, it's rare to notice it immediately.
This time, I found the following error in ST's console (hopefully, not a red-herring):
SublimeLinter: error in SublimeLinter daemon:
SublimeLinter: --------------------
SublimeLinter: Traceback (most recent call last):
  File "~/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/queue.py", line 57, in loop
    item = self.q.get(block=True, timeout=self.MIN_DELAY)
  File "./queue.py", line 175, in get
queue.Empty

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "~/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/queue.py", line 65, in loop
    self.lint(view_id, timestamp)
  File "~/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/queue.py", line 111, in lint
    self.callback(view_id, timestamp)
  File "~/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/sublimelinter.py", line 119, in lint
    Linter.lint_view(view, filename, code, hit_time, callback)
  File "~/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/linter.py", line 957, in lint_view
    callback(cls.get_view(vid), linters, hit_time)
  File "~/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/sublimelinter.py", line 137, in highlight
    vid = view.id()
AttributeError: 'NoneType' object has no attribute 'id'

SublimeLinter: --------------------

I have the following relevant software versions:
OS X (10.11.3)
Sublime Text 3 (buid 3102)
SublimeLinter (3.6.1)
SublimeLinter-jshint (1.2.1)
jshint (2.9.1)
node (5.5.0 via nvm)

+1
OS X(10.10.4)
SublimeText 3
Jshint v2.7.0
node v4.2.1
any workaround by chance? thinking of switching to another IDE

Same...
OS X (10.11.6)
SublimeText 3 (build 3114)
Jshint v2.9.3
node v6.5.0

+1
OS X(10.11.5)
SublimeText 3
Jshint v2.7.0
node v4.6.0

I was doing a project Euler using:
Atom 1.11.2
maxOS Sierra - Version 10.12
node 4.4.7
After running some high range computational programs a few times, I had 3 instances of node using 100% of my CPU each. To stop the processes, I did the following:

Open Activity Monitor
Double click 'node' which is causing problem
Click 'Quit' on the pop-up window that shows up.

After about 60 seconds my computer stopped being in a state of overdrive.

Fwiw: Next or next-next release will actively send kill/terminate signals to old processes.

This "next next" release it out!

Solved: I switched to node version 12.6.0 to 10.16.0 and the problem got resolved for me.


Every image looks pixelated despite RenderOptions set to "HighQuality"

Describe the bug
I have an avalonia app that target desktop enviroment. I didn't pay attention to image at first because I was focusing on making the core
Today I add some image controls and realize that all image look pixelated even when RenderOptions.BitmapInterpolationMode="HighQuality" is enabled for each image control
I create a new project in the same solution and reference the same library as the old one, but the images look fine
The first image looks pixelated, the second one looks fine. Both image control and parrent window is the exact copy of each other

To Reproduce
Project specific, can not reproduce in a new project
Expected behavior
Image should not be pixelated when RenderOptions.BitmapInterpolationMode="HighQuality"
Avalonia version
11.1.3
OS
Windows
Additional context
The App icon in both case looks fine and smooth

Sorry! I found the problem. After removing SkiaSharp latest preview version, everything is fine


send a command "hold button"

hello :)
is there a way to send a button which is hold 4 seconds?
"command": [
    {
      "command": "tv_menu",
    }
  ]

Also updated Issue #34 with the below:
I'm not a node.js developer, and this is not the correct place to fix it, I think it should properly be fixed in the node-appletv package and not homebridge-apple-tv package.  However, I tested an update to homebridge-apple-tv/helpers/sendCommand.js
case "hold_menu":
return device.sendKeyPress(1, 0x86, true);
return setTimeout(device.sendKeyPress(1, 0x86, true), 3000);
this uses the sendKeyPress from the node-appletv project directly, and allows you to set a timeout on the value.  You can modify this for any button, but the above is for the menu button.
The proper place to fix it would be to create a new function in node-appletv to create a copy of sendKeyPressAndRelease and make a new function such as sendKeyPressHoldAndRelease that adds a delay between the press and release of the command in node-appletv.
But, just making the code change above seemed to work for my limited use.  I'd like to get a proper fix into a pull request to add to node-appletv.  But, i don't have time to do so as this is just a hobby project.  But, I wanted to add here in case it was helpful.

Actually the line should be
return setTimeout(device.sendKeyPress(1, 0x86, false), 3000);
not
return setTimeout(device.sendKeyPress(1, 0x86, true), 3000);
but it didn't seem to matter much in my testing.


WebUI Login Config

Where are the credentials for the WebUI login stored?

Hi @davidmthomsen
Default user is admin and the password is also set in the key django_super_user_password in scantron_secrets.json (https://github.com/rackerlabs/scantron/blob/master/master/scantron_secrets.json.empty#L2) with a minimum length of 12 (https://github.com/rackerlabs/scantron/blob/master/master/config/settings/base.py#L214)

For our target ranges do we have to add them all to themaster/target_files/ directory as a flat file?

Correct.  The Workflow section should help (https://github.com/rackerlabs/scantron#workflow).  So you'd create a file named something like internal_web_servers.txt and add the lines
<IP_ADDRESS>
<IP_ADDRESS>/24
<IP_ADDRESS>
<IP_ADDRESS>/25

the file is passed to nmap using the -iL switch.

Did that work for you @davidmthomsen ?  Can I close this ticket?

Going to close for now.  Just open another issue if you have any questions.

Actually I am still have issues. Would it be possible to set up a chat or something for this? Slack maybe?

Sure, just emailed you.


Clarify that the FPS displayed in the 3D editor viewport is estimated

See https://github.com/godotengine/godot/issues/69218.
It may be a good idea to implement CPU/GPU utilization queries in Godot, so we can display the CPU/GPU usage percentage in this panel as well. This way, you can see whether your CPU/GPU are being fully utilized or not.

I'm slightly concerned that the "(est.)" abbreviation might not be obvious to all users (it seems to be a valid one though: https://dictionary.cambridge.org/dictionary/english/est), but most importantly that it might be pretty difficult to translate while keeping it short (for example I can't find a good option for French).

Maybe use "~X fps" or "circa X fps" instead? Circa comes from Latin and is pretty universal, and the tilde even more so.

I like the (symbolic) tilde suggestion rather than an language suggestion too.

I'm not sure if "estimated" is really what needs to be conveyed here. "Estimated" conveys to the reader that the value is close to the correct value, but is not exact.
The confusion OP had in https://github.com/godotengine/godot/issues/69218 is not that the results were inexact, but that they didn't take vsync into account and so they were completely different from expected. For example, with a simple scene users may see a frame time of 1.5 ms even with VSync enabled (so it should be 16.66 ms). Reporting "~1.5 ms" isn't really an improvement here because the value is off by an order of magnitude.

Can we estimate how bad the estimate is?

Can't we just check if (fps > vsync && vsync_enabled) and if true just display vformat(TTR("FPS: ~%d (VSync)"), vsync) instead?

To do this accurately, we'd need to keep track of the current monitor the editor is on, so that we can accurately pick the refresh rate of the monitor the editor is currently on (for multi-monitor setups with different refresh rates).

I guess Ideally we would have two reports:

FPS (uncapped)
FPS (actual)

Then it would be more clear what is actually happening.
Alternatively, we could just get rid of the FPS report altogether

Superseded by https://github.com/godotengine/godot/pull/75512.


Just can't seem to get it to optimise

Hi All,
I have followed the steps, installed all the correct libraries and tried in both Windows and Linux. I get no errors at all, it just doesn't optimise my images. At first I thought it wasn't finding my images but when I changed the location a non-existent image it then threw an error leaving me at a loss as to why it wouldn't optimise my images.
`require_once (DIR."/vendor/autoload.php");
$factory = new \ImageOptimizer\OptimizerFactory(array('ignore_errors' => false));
$optimizer = $factory->get();
$images = glob("images///*.{jpg,png,gif}", GLOB_BRACE);
foreach ($images as $image) {
$oldFileSize = filesize($image);
$optimizer->optimize($image);
print("Optimised: " . $image . " Saved: ".number_format((1 - $oldFileSize / filesize($image)),2) ."% \n");
}`
Can anyone suggest as to where I may be going wrong (Installed via composer, latest version).
Any help appreciated, it seems like a great library and if I can work out why I'll post my solution here.
Thanks,
Dom

Can you give me steps to reproduce? Eg. Dockerfile or Vagrantifle with environment and testing code? Maybe you have already run optimizer for all files and after that when you run second time there is no effect?


[SPARK-21402][SQL][BACKPORT-2.2] Fix java array of structs deserialization

This PR is to backport #22708 to branch 2.2.
What changes were proposed in this pull request?
MapObjects expression is used to map array elements to java beans. Struct type of elements is inferred from java bean structure and ends up with mixed up field order.
I used UnresolvedMapObjects instead of MapObjects, which allows to provide element type for MapObjects during analysis based on the resolved input data, not on the java bean.
How was this patch tested?
Added a test case.
Built complete project on travis.
@dongjoon-hyun @cloud-fan

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Test build #97545 has started for PR 22768 at commit 90d3a74.

Test build #97545 has finished for PR 22768 at commit 90d3a74.

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

Merged build finished. Test PASSed.

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

Merged to branch-2.2.

Thank you, @vofque .

Could you close this PR? Auto-close is only working for master branch PR.


family_of_curves.compute_likelihood bug

Traceback (most recent call last):
  File "C:\Program Files\JetBrains\PyCharm 2020.1.3\plugins\python\helpers\pydev\pydevd.py", line 1438, in _exec
    pydev_imports.execfile(file, globals, locals)  # execute the script
  File "C:\Program Files\JetBrains\PyCharm 2020.1.3\plugins\python\helpers\pydev\_pydev_imps\_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "C:/Users/gunnj/PCITpy/pcitpy/importance_sampler.py", line 369, in <module>
    test_importance_sampler()
  File "C:/Users/gunnj/PCITpy/pcitpy/importance_sampler.py", line 262, in test_importance_sampler
    importance_sampler(python_data, python_analysis_settings)
  File "C:/Users/gunnj/PCITpy/pcitpy/importance_sampler.py", line 113, in importance_sampler
    ana_opt['distribution'], ana_opt['dist_specific_params'], ana_opt['data_matrix_columns'])
  File "C:\Users\gunnj\PCITpy\pcitpy\family_of_curves.py", line 25, in family_of_curves
    return horz_indpnt_curve(get_info, varargin)
  File "C:\Users\gunnj\PCITpy\pcitpy\family_of_curves.py", line 95, in horz_indpnt_curve
    ix3 = data[cluster_idx[j], predictor_var_column] > x2
ValueError: operands could not be broadcast together with shapes (0,) (50000,)

From executing importance_sampler.

My test code for compute_likelihood relies on a data file that doesn't exist yet. I suppose I can easily generate it, though? Just run the matlab version up to the first call in matlab's importance_sampler and then bail?

The trouble was that np.where (as well as np.nonzero, a close relative) returns a tuple instead of a vector or array; I have to pull the vector out of that tuple for my code to work.