Fix TxnExecutionResult.data field

Fixes the TxnExecutionResult.data to be consistent. Before this
change, some components assumed this field was a list of
(data type,bytes) pairs, others assumed it was just a list of bytes.
Signed-off-by: Logan Seeley<EMAIL_ADDRESS>

The "updates .gitignore" also removes the python block info transaction family. If intentional, that deserves it's own commit and explanation.

These are the generated protobuf files that should have be ignored by the .gitignore and not checked in. Would adding details to the message of the existing commit be sufficient

The "updates .gitignore" also removes the python block info transaction family. If intentional, that deserves it's own commit and explanation.

These are the generated protobuf files that should have be ignored by the .gitignore and not checked in. Would adding details to the message of the existing commit be sufficient

Yes, it would.

The "updates .gitignore" also removes the python block info transaction family. If intentional, that deserves it's own commit and explanation.

These are the generated protobuf files that should have be ignored by the .gitignore and not checked in. Would adding details to the message of the existing commit be sufficient

Yes, it would.

Fixed

MarLu96 1:54 AM
Hi all, I'm trying to create a node that can deploy solidity contract with seth, but using PoET (and not devMode). Here is how I modify the docker-compose file from the seth github. It seems that when I create an account seth account create --nonce=0 --wait myalias , nothing happens like if the connection is not properly done. I have the returned message Error: Problem submitting account creation transaction: Transaction was submitted, but client timed out before it was committed.
danintel 8:47 AM
@MarLu96 The problem is you are using the latest version of Seth, which is broken--it does not work. The workaround is to roll back Seth to changeset 52a0512 (Disable clippy warning about not returning Self). This forces Seth to run docker-compose with Ubuntu 16 (Xenial) and Sawtooth 1.0.
The issue I filed is https://jira.hyperledger.org/browse/STL-1509
ltseeley 9:37 AM
@danintel @MarLu96 @rajatwasan @lin2xing the issue with seth account creation has been resolved on the master branch of sawtooth-core: https://github.com/hyperledger/sawtooth-core/pull/2064

MarLu96 1:54 AM
Hi all, I'm trying to create a node that can deploy solidity contract with seth, but using PoET (and not devMode). Here is how I modify the docker-compose file from the seth github. It seems that when I create an account seth account create --nonce=0 --wait myalias , nothing happens like if the connection is not properly done. I have the returned message Error: Problem submitting account creation transaction: Transaction was submitted, but client timed out before it was committed.
danintel 8:47 AM
@MarLu96 The problem is you are using the latest version of Seth, which is broken--it does not work. The workaround is to roll back Seth to changeset 52a0512 (Disable clippy warning about not returning Self). This forces Seth to run docker-compose with Ubuntu 16 (Xenial) and Sawtooth 1.0.
The issue I filed is https://jira.hyperledger.org/browse/STL-1509
ltseeley 9:37 AM
@danintel @MarLu96 @rajatwasan @lin2xing the issue with seth account creation has been resolved on the master branch of sawtooth-core: https://github.com/hyperledger/sawtooth-core/pull/2064


Fix latest build number

[x] All tests passed. If this feature is not already covered by the tests, I added new tests.
[x] This pull request is on the dev branch.
[x] I used gofmt for formatting the code before submitting the pull request.

Fix fetching latest version using --build flag
[jfrog/jfrog-cli/issues/1110]
(When trying to download the artifacts from Arifactory using Jfrog CLI and specifying the --build option and it is expected to fetch the latest version but it is not fetching the latest  #version.)

I have read the CLA Document and I hereby sign the CLA

This PR was closed because https://github.com/jfrog/jfrog-client-go/pull/396 replaces it.


overlapping-text-issue-resolved

Fixes #67
Now text is not overlapping
Iphone se 2022:
After:

Before:

hi @Shayan12456 , please re do this using css, you are adding complexity to the component that impacts performance and it's not really necessary. You can use media queries like you did but in the css easily. Thanks!


Repo name
my-new-service1
Repo visibility
private
Team Write Permissions
dev-team
Team Admin Permissions
admin-team
Enable issues
yes
Enable projects

[x] yes

Extra features
new repo, new pr, new issue

/create-service


Update URL py5.ixora.io -> py5coding.org

Thank you for noticing this!

sorry for this, I think I messed up with the branches :-S

@villares , github is being uncooperative right now. It looks like you pushed a lot of example code to the previous PR that made that URL change. Is that correct? I haven't quite mastered reviewing PRs, or even have a half understanding of them.

Yeah, that's it.
I could close this and restart on a clean branch I suppose...

This PR is fine, but next time, it is probably better to start a new PR for each separate thing.
Can you tell me about this? This contains all the ported example code, right?

I usually make distinct branches, I even teach this to my students!
But this time I messed up twice... first I made the URL correction in main. And made the PR.
Then I have this branch with the Processing Python mode examples I'm working on converting and for some reason I wanted to merge them to main and start over, I don't even remember why. So that was it.

OK, I don't understand what happened. There isn't more example code or anything different. @villares, can you create a new PR with the new example code you worked on? It isn't your fault, Github doesn't seem to like that you reopened a previous PR.

Sure, I was thinking of some way of "testing", running many examples before sending the examples, but I'll do it.

If it helps, there is code that is used to run all of the example code you see in the reference docs.
https://github.com/py5coding/py5generator/blob/main/py5_docs/scripts/run_example_code.py
Most of that is specific to the reference docs and the Documetation files though. The part that might be useful is here:
https://github.com/py5coding/py5generator/blob/main/py5_resources/py5_module/py5_tools/testing.py
That assumes module mode. Is your example code in imported mode? If so, you might benefit from making calls to run_code() in imported.py:
https://github.com/py5coding/py5generator/blob/main/py5_resources/py5_module/py5_tools/imported.py

The examples are imported mode, as they are the Processing Python mode direct coversion... I'll have to tinker with that! thanks!


model: impl KethMaybeRelocatable and KethOption

Related https://github.com/kkrt-labs/keth/issues/37

left a comment to be more generic but ok as is

Just fixed the comment, this is nicer


Unable to OR'd the variables using the symple '||=' in<EMAIL_ADDRESS>

I have a TypeScript code that contains the following lines:

var modifyFlag = false;
for (var phase of phases) {
modifyFlag ||= UpdateVerticalPhaseTitleWidth(phase, args.propertyName);
}

When I compile this cold using TS_Build task in Visual Studio 2022 Task Runner Explorer, I get the following error message:

file: dev\typescript-diagram\Shapes\DiagramShapeFactory.ts:
[909]         diagram.updateNode(sourceShape.name,
[11:51:56] 'TS_Build' errored after 3.74 s
[11:51:56] GulpUglifyError: unable to minify JavaScript
Caused by: SyntaxError: Unexpected token: punc (;)
File: C:\Projects1\Repos\NavviaProjects\Navvia\dist\js\NavviaDiagram.js
Line: 982
Process terminated with code 1.

The error generated at Line 982 which is

'modifyFlag ||= UpdateVerticalPhaseTitleWidth(phase, args.propertyName);'.

In regular JavaScript, the '||=' this is valid (and I tested to make sure in JS Fiddle)  but<EMAIL_ADDRESS>sees it as an error.
I do have a work around for this but it is not a good solution<EMAIL_ADDRESS>is able to compile this my work around successfully).

Closing this issue.


Istio helm chart should support inject container with debug mode

With auto-injection, I cannot enable debug mode for side-car injection, we should add the option to enable debug.
https://github.com/istio/istio/blob/master/install/kubernetes/helm/istio/charts/sidecar-injector/templates/configmap.yaml

/cc @sdake @linsun @morvencao

Can you change the annotation sidecar.istio.io/proxyImage to specify the proxy debug image that you want to use for specific pod?

@yusuoh sorry, I mean coreDump mode https://github.com/istio/istio/blob/master/pilot/pkg/kube/inject/mesh.go#L66-L78 here, we should support this in auto injection as well.

#5044


Fix docker-default profile handing signals

Replaces #16944

ping @diogomonica this fixes what you showed in your demo correctly

ping @ewindisch I didnt remove docker-default for the binary because then people who download completely static binaries couldnt use apparmor

LGTM

ping @estesp :innocent:

LGTM with minor nit mentioned in file diff

updated

great! LGTM

yayyyy green


Fix js bundling

Streamlined bundling
changed npm library name stencila-mini-core -> stencila-libcore :

less dashes
removed 'mini' from name, as it is now a pure library, which can be used outside mini as well

@nokome are you ok with these decisions?

stencila-libcore is not yet published on npm. @oliver---- can I?

I'm about to review this PR and will then publish. Give me 30mins. I'll ping you :)

Oh looks like stencila-libcore is not yet referenced in Stencila. So better wait?

@oliver---- : thanks for this :+1:
Yes, the renaming is the right thing to do! I've completed that process, will rename this repo, publish to  npm, and deprecate mini-core.
Also made some fixes to bundling for tests.


Create sticky order

Could you add the option of creating limit orders at the spread line and move with the price until its all bought/sold?

Also, where do I set the margin? I go 50x but dont see an option on here to set it

Set it on on your account.
On Mon 6. Aug 2018 at 21:13, smokenmirrors2<EMAIL_ADDRESS>wrote:

Also, where do I set the margin? I go 50x but dont see an option on here
to set it
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nice-table/bitmex-scaled-orders/issues/3#issuecomment-410821270,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjWb4QvW2jZEMRQm2rTm_XxSrBDSUBnTks5uOJVtgaJpZM4Vw7V5
.

Hey
You have to use the official Bitmex UI in order to see and change leverage for now.
Regarding spread orders: maybe. I'm currently in the middle of improving support for others instruments like ETHUSD and friends.
Bitmex Assistant may have the feature you're looking for: https://github.com/BigBitsYouTube/BitMEXAssistant
I'll keep the issue open since it's a good suggestion.


Fixed mistake in sound types category

Changed range from 20 Hz - 20 Hz to 20 Hz - 20.000 Hz

Thanks, first pull request 👍 🥇  But it says 20 Hz - 20 kHz (audio), kHz short for kilo Hertz, meaning 20000 Hz

Thanks, first pull request +1 1st_place_medal But it says 20 Hz - 20 kHz (audio), kHz short for kilo Hertz, meaning 20000 Hz

inattentional blindness after reading too much 😂


refactor: notice classes names and codes

closes #784
Summary:
This PR refactors notice class names and codes so that they are all the same. It implements getCode() in the base Notice class.
Expected behavior:
Notice code should be derived from the notice class name.
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[x] Linked all relevant issues
~[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)~

@lionel-nj I would be glad to discuss your ideas before you start writing code. Just drop me an email next time.

I would suggest to implement getCode() in the base Notice class and just derive it from the class name.

I would suggest to implement getCode() in the base Notice class and just derive it from the class name.

👍  I was thinking along these lines too - plus, if the code is always derived from the class name, we don't even need to list the code in the table in RULES.md for https://github.com/MobilityData/gtfs-validator/pull/781

I would suggest to implement getCode() in the base Notice class and just derive it from the class name.

👍 I was thinking along these lines too - plus, if the code is always derived from the class name, we don't even need to list the code in the table in RULES.md for #781

Good point! Will update both PRs.

I would suggest to implement getCode() in the base Notice class and just derive it from the class name.

👍 I was thinking along these lines too - plus, if the code is always derived from the class name, we don't even need to list the code in the table in RULES.md for #781

Good point! Will update both PRs to meet these thoughts.

@aababilov @barbeau before going further, I'd love to have your feedback on https://github.com/MobilityData/gtfs-validator/pull/783/commits/6eb3b5c5308ce9aa21e4e32995d0d2e2e708f346 please :)
Here is a screenshot of a test execution in debug mode: the notice's code has effectively been changed. It now the name_of_the_class_with_underscores. In order to avoid introducing a new dependency a re-used the code defined in FieldNameConverter (from the processor module).

@barbeau also https://github.com/MobilityData/gtfs-validator/pull/783/commits/7dd23a3469b9e54baf5ee286702c9aaeb97febbd and https://github.com/MobilityData/gtfs-validator/pull/783/commits/3df44f232d69e0f3b46ee39eed8aa9ca759d2d77 refactor some notice class names to account for https://github.com/MobilityData/gtfs-validator/pull/781#discussion_r585866237

In order to avoid introducing a new dependency in the core module on processor) I re-used the code defined in FieldNameConverter (from the processor module). I am not sure this is best practice or the most effective way to get around this, I am all hears for any suggestions 😃

Since processor depends on core already we could move any relevant utility methods into core and then call them in processor. I could go either way in this case because it's a single line of code, but as a best practice maybe it would be good to start this now.

Should we remove the terms "notice" or "error" (as done for most validation rule related notices)?

You mean for the notice code, right (not class name)? For the notice code, I'd suggest we keep the same pattern that we currently have - it's less verbose when looking at the error output.

You mean for the notice code, right (not class name)? For the notice code, I'd suggest we keep the same pattern that we currently have - it's less verbose when looking at the error output.

The notice code. Alright!

I suggest to make changes step by step in separate PRs to facilitate review.
Step 1. Implement Notice.getCode() method. It should strip the "notice" substring but not strip "error" since we will carefully remove that suffix in the further steps.
Step 2. Change Notice.equals() and Notice.hashCode() to use the class instead of getCode().
Step 3. Remove implementations of getCode() in child classes. Some classes will be renamed in accordance to their "code".
Here we can establish a convention: all children of SystemError end with Error, all children of ValidationNotice end with Notice.

Step 1. Implement Notice.getCode() method. It should strip the "notice" substring but not strip "error" since we will carefully remove that suffix in the further steps.

Implemented in https://github.com/MobilityData/gtfs-validator/pull/788

Step 2. Change Notice.equals() and Notice.hashCode() to use the class instead of getCode().

Implemented in https://github.com/MobilityData/gtfs-validator/pull/789

Step 3. Remove implementations of getCode() in child classes.

https://github.com/MobilityData/gtfs-validator/pull/790

Some classes will be renamed in accordance to their "code".

This will be done in a separate PR in order to avoid confusion
Thanks for your feedback @barbeau @aababilov!

Since processor depends on core already we could move any relevant utility methods into core and then call them in processor. I could go either way in this case because it's a single line of code, but as a best practice maybe it would be good to start this now.

Opening an issue for discussions.

Closing this PR since it has been split in three others: #788, #789, #790.
https://github.com/MobilityData/gtfs-validator/pull/783#issuecomment-790994961


Loss function give negative values... bad news ?

Hi,
When training the MDN model, after some times, the custom  "loss=mdn.get_mixture_loss_func(OUTPUT_DIMS,N_MIXES)" give negative values.
Note: Happens with Standard Scaling on Y. every thing else is quite simple:

What that means ? Is it a bug ? Is it still converging ?
thanks!

It's ok for the loss to be negative because of the way that continuous probability density functions work (more discussion in #15 ). 🙃
Seems weird to me too! But it's generally ok.


Define Swift development experience

At the current moment, the possibilities for Swift development experience on OpenWhisk are wide open. Let's use this issue to discuss the right approach to make developing OpenWhisk artifacts in Swift a good experience for our users.
Whatever specific decisions are made, I think we should keep in mind the following ideals:

Allow for use of standard development tools, including Xcode and the Swift CLI.
User code should compile cleanly on their development machine (not just in the OW Swift runtime).
Some amount of unit testing should be possible on the user's development machine.
User should be able to develop multiple OW artifacts (say, all artifacts within a OW package) in the same Swift package/Xcode target.
The development experience should be comparable regardless of the platform the developer is using to write their code.

It may not be possible to achieve all of these ideals in the final experience, and so compromise should be carefully considered.

Proposal: Actions must declare a global main function
The obvious advantage of this approach is simplicity. The action developer gets to see exactly what is expected of them, and the OW runtime knows exactly what code to invoke to run the action:
func main(args: [String:Any]) -> [String:Any] {
    // action implementation goes here
}

This advantage extends even to having the types of the args object and the expected return type plainly visible to the action developer.
The disadvantage to this approach is that it violates our goals of using standard tools and developing multiple OW artifacts in the same Swift package or Xcode target. If you have multiple files declaring this global main function, the swift compiler will complain that you are trying to redefine a global function.

@csantanapr @paulcastro @jberstler should we move this to the new swift repo?


add StubSyncManager

add StubSyncManager

Codecov Report

Merging #140 into dev will increase coverage by 0.35%.
The diff coverage is n/a.

Codecov Report

Merging #140 into dev will increase coverage by 0.35%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##                dev     #140      +/-   ##
============================================
+ Coverage     39.48%   39.84%   +0.35%
- Complexity      601      617      +16
============================================
  Files           142      145       +3
  Lines          4467     4533      +66
  Branches        331      338       +7
============================================
+ Hits           1764     1806      +42
- Misses         2564     2592      +28
+ Partials        139      135       -4

Impacted Files
Coverage Δ
Complexity Δ

.../com/webank/wecross/restserver/RestfulService.java
65.78% <ø> (+1.13%)
10 <0> (ø)
:arrow_down:

src/main/java/com/webank/wecross/stub/Stub.java
88% <ø> (ø)
12 <0> (ø)
:arrow_down:

...ava/com/webank/wecross/stub/remote/RemoteStub.java
50% <0%> (-16.67%)
4 <0> (ø)

...a/com/webank/wecross/stub/jdchain/JDChainStub.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...in/java/com/webank/wecross/stub/bcos/BCOSStub.java
66.66% <0%> (+6.66%)
7 <0> (ø)
:arrow_down:

.../java/com/webank/wecross/peer/StubSyncManager.java
0% <0%> (ø)
0 <0> (?)

...ava/com/webank/wecross/stub/fabric/FabricStub.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...rc/main/java/com/webank/wecross/resource/Path.java
65.51% <0%> (-3.45%)
11% <0%> (-1%)

...ain/java/com/webank/wecross/proposal/Proposal.java
69.23% <0%> (ø)
6% <0%> (?)

...java/com/webank/wecross/proposal/ProposalPool.java
78.26% <0%> (ø)
12% <0%> (?)

... and 2 more

Continue to review full report at Codecov.

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


Set timestamp from payload

The decoder should set the timestamp of the measurements to the time the gateway or ttn server received the message if not encoded in the message

a9f860c56e2892926aef4e6a309707dcb9d92014
if available, gateway time is used, else TTN API time, else local time


Enable build scan upload for pull requests

Motivation:
Explain why you're making this change and what problem you're trying to solve.
Modifications:

List the modifications you've made in detail.

Result:

Closes #. (If this resolves the issue.)
Describe the consequences that a user will face after this PR is merged.

And you added it as a non-secret environment variable, right? Sounds good to me. :bow:


metadata fixes

Docs Build status updates of commit 864167e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Publishing of document 'IIS-Administration/api/iis.administration.swagger.json' failed at SafeOpenReadStream with relative path: IIS-Administration/api/iis.administration.swagger.json. Error: Could not find a part of the path 'E:\approot\build\%_op_cacheFolder%\IIS-Administration\hnxebanq.gso\432o0lw1.m45'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Good to merge?

Docs Build status updates of commit 864167e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

IIS-Administration/api/files.md
:bulb:Suggestion
View
Details

IIS-Administration/api/installing-features.md
:bulb:Suggestion
View
Details

IIS-Administration/api/request-tracing.md
:bulb:Suggestion
View
Details

IIS-Administration/api/scope.md
:bulb:Suggestion
View
Details

IIS-Administration/api/sites.md
:bulb:Suggestion
View
Details

IIS-Administration/configuration/appsettings.json.md
:bulb:Suggestion
View
Details

IIS-Administration/index.md
:bulb:Suggestion
View
Details

IIS-Administration/security/access-tokens.md
:bulb:Suggestion
View
Details

IIS-Administration/security/integrated/authorization.md
:bulb:Suggestion
View
Details

IIS-Administration/docfx.json
:white_check_mark:Succeeded

IIS-Administration/api/files.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

IIS-Administration/api/installing-features.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

IIS-Administration/api/request-tracing.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

IIS-Administration/api/scope.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

IIS-Administration/api/sites.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

IIS-Administration/configuration/appsettings.json.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

IIS-Administration/index.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

IIS-Administration/security/access-tokens.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

IIS-Administration/security/integrated/authorization.md

[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

The bug was fixed and now my PR passed. It seems that there are some other metadata issues that we need to fix here.


add instantiation process in the origin UFO

add instantiation process in the origin UFO, which been debugged and partially tested.

@microsoft-github-policy-service agree company="Microsoft"


Syncing with upstream react-boostrap-web3-android. Updating minimal-slp-wallet to v5.10.0

:tada: This PR is included in version 2.0.2 :tada:
Your semantic-release bot :package::rocket:


Gather Teensy design specifications

Time estimate:
Deadline:
Description of task: As it was decided to have ADCs on the Acoustic PCB, we should think of a possible design how to interact with the PCB.
Main goal is to figure out which configuration is needed for the Teensy to communicate with the ADCs over SPI. Following aspects should be considered:

Do we have enough Bandwidth? Which is depending on:

Max. serial clock (SCK)
Daisy Chain or multiple single SPI connections over digital pins
How ADC are triggered / data is read from them

If Teensys can fulfill the needs, how will we interact with Xavier, e.g. I2C or Ethernet

Decided to use parallel data read from the ADC instead of serial.
Will create a separate task for implementing the ADC driver.
Mostly covered on the Vortex Wiki
Ethernet will be used to interact with Xavier and is working https://github.com/vortexntnu/Teensy/pull/2


Socket hangup on multiple async requests

Hi, I'm having a socket hangup issue whenever I try to do many simultaneous requests (over 100 for example). I've researched the issue and apparently setting http.globalAgent.maxSockets to 'Infinity' should fix this. I think the optimal way to handle this is to add the maxSockets option to needle, even though it's quite specific. I am aware that node.js version 0.12 comes with 'Infinity' sockets by default, but still it would be a nice addition in my opinion.

Hi @monitz87,
You're right. In the meantime I guess nothing prevents you from doing http.globalAgent.maxSockets = Infinity in your code. I don't think it's a good idea to include that on Needle and force everyone to a specific number of maxSockets.


Get rid of #[serde(with = "ruma_serde::json_string")]

Since we are now using our own fork of serde_urlencoded that does this automatically, we no longer need the attribute.

I've tried removing the attributes but it doesn't actually work yet. This is probably a bug in ruma-serde.

With the new monorepo, there's no longer any reason to track removal of the module and removal of its usage separately. Closing in favor of ruma/ruma#2.


Missing jars in deployed PowerShell module

Describe the bug
Within the binary folder the jars are missed
Expected behavior
The folders net6.0 and net462 shall contains the needed jars like nuget packages have
Screenshots
No screenshoot, see list of FileList on https://www.powershellgallery.com/packages/MASES.JNetPS/1.4.11
Desktop (please complete the following information):

OS: All
Version 1.4.11

Additional context
N/A

Linked to #64


Next.js TypeError: Cannot read properties of undefined (reading 'files')

Hi, trying to build a Next.js project, using React 18, Next.js v13 and the pages folder, after applying all the changes by the guide () setting the Edge API Routes and the Edge Runtime also for the pages, I get the following error:
14:05:40.491 | ▲ info  - Collecting page data...
-- | --
14:05:40.492 | ▲
14:05:41.533 | ▲ TypeError: Cannot read properties of undefined (reading 'files')
14:05:41.534 | ▲     at /opt/buildhome/repo/node_modules/next/dist/build/utils.js:817:33
14:05:41.534 | ▲     at Span.traceAsyncFn (/opt/buildhome/repo/node_modules/next/dist/trace/trace.js:79:26)
14:05:41.534 | ▲     at Object.isPageStatic (/opt/buildhome/repo/node_modules/next/dist/build/utils.js:802:29)
14:05:41.534 | ▲     at execFunction (/opt/buildhome/repo/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2828)
14:05:41.534 | ▲     at execHelper (/opt/buildhome/repo/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2486)
14:05:41.535 | ▲     at execMethod (/opt/buildhome/repo/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2574)
14:05:41.535 | ▲     at process.messageListener (/opt/buildhome/repo/node_modules/next/dist/compiled/jest-worker/processChild.js:1:1284)
14:05:41.535 | ▲     at process.emit (node:events:390:28)
14:05:41.535 | ▲     at emit (node:internal/child_process:917:12)
14:05:41.535 | ▲     at processTicksAndRejections (node:internal/process/task_queues:84:21)
14:05:41.536 | ▲
14:05:41.539 | ▲
14:05:41.539 | ▲ > Build error occurred
14:05:41.539 | ▲
14:05:41.541 | ▲ Error: Failed to collect page data for /500
14:05:41.541 | ▲     at /opt/buildhome/repo/node_modules/next/dist/build/utils.js:963:15
14:05:41.541 | ▲     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
14:05:41.541 | ▲   type: 'Error'
14:05:41.542 | ▲ }
14:05:41.542 | ▲
14:05:41.623 | ▲ Error: Command "npm run build" exited with 1

My next.config.js:
const path = require('path');
const withBundleAnalyzer = require('@next/bundle-analyzer')({
  enabled: process.env.ANALYZE === 'true'
});

module.exports = withBundleAnalyzer({
  experimental: {
    legacyBrowsers: false,
    newNextLinkBehavior: true,
    fallbackNodePolyfills: false,
    nextScriptWorkers: true
  },
  swcMinify: true,
  reactStrictMode: false, // disabled to allow gsap to properly run in dev mode
  trailingSlash: true,
  i18n: {
    locales: ['en'],
    defaultLocale: 'en',
    localeDetection: true
  },
  sassOptions: {
    includePaths: [path.join(__dirname, 'styles')]
  }
});

Any ideas please ?

Someone else have this issue with next.js ?

I'm getting the same issue.  Same versions as you as well

yes, I'm getting the same

This is a Next.js issue, not a next-on-pages one. https://github.com/vercel/next.js/issues/40379
Although not ideal, the workaround of removing 404 and 500 pages may resolve it for you.

Closing this issue since it doesn't look next-on-pages related as @james-elicx mentioned.


[FIX #79] Attach the open file menu to the topBarView

Fixes #79
By default, AppKit tries to match the position of the selected item of a menu with the frame specified in [s_cell performClickWithFrame:frame inView:controlView] However, if there is insufficient screen space, the menu will displayed below the controlView which is in case of the previously used O_editorView outside of the visible screen frame. To overcome this issue, the topBar is now being used as controlView placing the menu in case of insufficient space below the top bar

After looking into it more it seems to be more intricate. However, couldn't root cause it better and the approach with the status bar works hidden or not, so I'll take this slightly adjusted. Thanks for the preparation work here!

done almost this way in 3654b4942b4fc3297728f0dfacf49ad5bec13fa2


Reference page screenshots mismatch

Hi.
On https://hypertext.artofthesmart.com/reference
#7 and #5 seem switched. Didn`t check them all, but one should make sure the screens show the actual style.

It seems to be fine for me. Can you screeenshot where the problem is?
https://hypertext.artofthesmart.com/reference?theme=5
https://hypertext.artofthesmart.com/reference?theme=7

I was under the impression a style called dark solar, would be similar to a dark solar theme, and not black text on white-ish background.
name #7 is dark solar but neither actually dark nor solar.

I see it now. Yeah the names are totally out of whack with what the actual CSS files are. I'm going to get this fixed on the next major revision. Stay tuned.


Necessary thing in the update

Add editor .js  for gametest API
Add editor ui/gui
Add editor entity, block and etc. creater

Yes, perhaps the requests are difficult to execute, but in my opinion this is the most important thing that should be in the utility for convenient creation and edition of addons

Thanks @colemad! I'll do my best to add those features. Your feedback means a lot! 😊

In any case, it is extremely convenient now. Looking forward to improving what is already good

Thank you for your excitement about the features you've mentioned! I'm not always focused on blocks, entities, and JSON UI, but I'm definitely planning to work on them for the plugin. I want to ensure they are done right, which might take some time. Your understanding and patience mean a lot to me! Thanks for your support! :blush:

In fact, they are a little similar to each other, so this is a great functionality that can be done

Hi there! I was imagining how it'll look after implementation. Wondering where to place the button for creating new items, blocks, UI, animations, recipes, and more, hehe. What do you think? Would it be okay to have a new button that opens a dropdown with all these options? I'd really appreciate your input before I start implementing. Thanks a bunch!

The easiest thing in my opinion is to make a bind, for example Ctrl+M, which will open a menu with a choice of what you need, but I was talking about a simple syntax for creating, for example, a tooltip or highlighting, you made it complicated but it also sounds good

Hi @colemad! Quick check – when you mentioned 'simple syntax for tooltips and highlighting', were you thinking of something like auto-suggestions for Minecraft json? I might've got a bit mixed up, thinking about the model editor with graphics, like .bridge. My bad if it's a bit confusing! Your thoughts mean a lot, thanks a bunch!

Yes, that’s what I meant, but if you can do something more functional, that’s also good, but I was thinking about the minimum

Sorry for the earlier confusion. I haven't started on it because I haven't explored Minecraft blocks yet, and I took a break from coding last week to rest. It might take me a while, maybe weeks or months. School also demands my time. I'll do my best to tackle it soon. Thanks for understanding!


Update Selenium version

IMPORTANT
Your issue might be labeled as invalid and eventually closed if:

You have deleted completely the issue template for no reason
You can not reproduce the issue
Your question is not an issue nor a feature request but it's only a support/consulting request (use stack overflow for it)
Your post violates our code of conduct

Help us to manage our issues by answering the following:

Describe your issue:

The version of Selenium being used is now over 6 months old, we should update Selenium so we can target the latest version of every respective browser and leverage new web driver functionality.

Can you reproduce the issue?

On which python and selenium version does the issue appear?

Which version of py-component-controller does it affect?

How would you tag this issue?

[ ] Question
[ ] Bug
[ ] Discussion
[ ] Feature request
[ ] Tip
[x] Enhancement
[x] Performance

https://github.com/neetjn/py-component-controller/pull/108


Group entries based on author name

Noticed following issue - all summaries / graphs usually show output like:

Author
Tests

Author B
2

Author A
12

Author B
5

Author A
7

Author C
12

Author C
5

Author C
3

Suppose reason is that author email changed at certain moment.
Wonder if it's possible to add option to group results by name?

Git Hammer relies on Git itself for this functionality. Git has a feature called mailmap file that can be used to define which names and/or emails should be treated as the same person. I found a nice explanation of how to create a mailmap file on the Atlassian blog: https://blog.developer.atlassian.com/aliasing-authors-in-git/
If you need further help, I'm happy to try, but I'm not an expert in this, and my mailmap file creation often ends up experimenting and running git shortlog -se until I'm happy with the results.

@asharov thank you! .mailmap aliases work just fine :-)


Validate Stored Procedure names

We currently don't validate the name entered.

Marking as P2
The Stored Procedure creation happens in <5 seconds, and it's a single step wizard. I currently don't see big UI value.

There is the isResourceValid method that enables this in the node-document-db package. See here. Even though the function is 'hidden', a fix for this bug will have to necessarily mirror that logic, solely to maintain parity.
With the migration in #760, it looks like this function would be public, and we will have a lesser to worry about maintaining it.


add pr e2etest

What this PR does / why we need it:
add pr e2etest
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Codecov Report

Merging #107 (01fc39e) into main (27dbff4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #107   +/-   ##
=======================================
  Coverage   17.16%   17.16%
=======================================
  Files          72       72
  Lines        7106     7106
=======================================
  Hits         1220     1220
  Misses       5765     5765
  Partials      121      121

Help us with your feedback. Take ten seconds to tell us how you rate us.


Drop gconf2 and/or python-2.7 dependencies

Hi
Many distros are phasing or have already phased out python-2.7.
It's possible that Mattermost desktop client might be the only package on a Linux system still pulling these outdated packages in.
Do we know what it would take to drop them?

i think python v2.7 is the minimum required version. it might be needed for node-gyp and problably electron-builder, but I don't think it is restricted to v2.7

Could someone skilled enough here run an experiment setting the minimum to Python 3.6?

Closing as inactive. Feel free to re-open if this is still an issue.

Closing as inactive. Feel free to re-open if this is still an issue.

Gentoo managed to take care of it on its own, so it might not have been an upstream problem after all.


Overwriting of auth creds in case of several git projects

System information:

Windows 10 2004
DBeaver version 23.0.3
Git for DBeaver

Describe the problem you're observing:
Current version of program rewrites auth. details when using https protocol in case of several projects.
Steps to reproduce, if exist:

Create repository 1 from git with auth details 1

Create repository 2 from git with auth details 2

Check remote url of repository 1 (right click -> Team -> Remote -> Configure Push To Upstream ->change
Authentication creds are rewriteen by ones from auth details 2

Thank you for the report. Looks like a third party issue.


PRFC: Lightweight Analytics API for Plugin Devs and App Integrators

Need
Setting up, maintaining, and iterating on Backstage can be a large investment.  While organizations can measure the return on this investment by qualitative means (surveys, user interviews, etc), it would be ideal if they could have hard data to do so as well.  This would validate deployments in early stages, as well as inform ongoing investments in specific areas of the app.
App Integrators (those in need of this data) are unable to instrument most things Backstage because of its unique plugin/extension architecture.  Meanwhile, Plugin Developers (the ones who could instrument the plugin code) have no standard means to do the instrumentation.
We need an API that's simple enough for Plugin Developers to be able to just fire an event in their plugins on one end...  And flexible enough for App Integrators to be able to capture and forward those events to the analytics system of their preference.
Proposal
A Plugin Developer should be able to instrument her plugin with a simple function call and two arguments.
import { useAnalytics } from '@backstage/core-plugin-api'

export const MyThing = ({ myValue }) => {
  const analytics = useAnalytics();
  const handleClick = () => analytics.captureEvent('click', myValue);
  return <Thing value={myValue} onClick={handleClick} />
};

This proposal includes three examples of instrumentation for illustrative purposes:

Within a typical plugin
Within a core component
Within the core app itself

Meanwhile, an App Integrator should get the event, decorated with other important metadata about where the event was fired.  Here's an example, using Google Analytics as a target system.
import { analyticsApiRef, useApi } from '@backstage/core-plugin-api';
const analyticsApi = useApi(analyticsApiRef);

analyticsApi.event$().subscribe(event => {
  // Capture the root:navigate event as a pageview.
  if (event.domain.pluginId === 'root' && event.verb === 'navigate') {
    return ga('send', {
      hitType: 'pageview',
      page: event.noun,
    });
  }

  // Capture all other events as a custom event.
  ga('send', {
    hitType: 'event',
    eventCategory: event.domain.pluginId,
    eventAction: event.verb,
    eventLabel: event.noun,
    value: event.value,
  });
});

The extra metadata would come from a proposed <AnalyticsDomain />, wrapping all extensions by default.  Events fired outside the context of an extension would get hard-coded values for the pluginId and componentName of root and App respectively.  A routeRef value is also provided underneath routable extensions.
There is also a proposed withAnalyticsDomain HOC provider for static analytics domain attributes, a proposed application of which is included in this PR in the core <Link /> component.
App Integrators would still be responsible for wiring up the service of their choice, but it's easy to imagine sane defaults being handled by analytics system-specific plugins.  I chose to illustrate using GA because it's one of the more constrained / opinionated web-based analytics frameworks.  Many others could be as simple as, for example...
analyticsApi.event$().subscribe(event => amplitude.getInstance().logEvent(event));

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Closing this out for the PR!  #6677


Add support for camel-activemq and camel-jms

These are heavily used in integrations.

We already support sjms and sjms2. Could somebody please remove camel-jms from the title?


git tag 0.18 mismatch code version on PyPI

I just wanted to try out the introduced patching of an existing cmd class. The signature of get_cmdclass now takes an optional argument to pass in a command class, but the release on PyPI does not have this code.
I upgraded from version 0.16:
$ versioneer install
replacing old versioneer.py (0.16)
versioneer.py (0.18) installed into local tree
Now running 'versioneer.py setup' to install the generated files..
 creating pyemma/_version.py
 appending to pyemma/__init__.py
 'versioneer.py' already in MANIFEST.in
 versionfile_source already in MANIFEST.in

So I doubt that the base64 encode of the implementation is really at the state of tag 0.18. I've verified this locally by downloading the wheel and writing a fresh install. The signature is not matching.

Yes, versions in versioneer are handled manually. I've updated the source to be 0.19.dev0 until the next release.


Added loader

PR Description 📜
I have successfully added a loading animation on the game. Currently, It can be seen when the page is loaded or the when we click the start button. Further, it can be used anywhere when needed by just calling the loading() function.
Fixes #83

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for review.

## Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

@Durgesh4993 Please have a look on PR, there are no merge conflicts. Please merge it.

@hars-21 this loader is creating a lot of issues after merging, please review it once and add proper working video, I had initially merged this PR but reverted it for this reason


WASM example fix

This fix a caching issue, since HF models are not correctly cache, here using Cache API to store the models appropriately
update UI to change seq_len depending on model size

Thanks!


Fix helm bug caused by old evil-collection

Issue #503 is caused by a bug in evil-collection regarding 3rd party macros (described here: https://github.com/emacs-evil/evil-collection/issues/101). It is fixed in upstream but not on elpa (yet?). This pull request gets evil-collection from github and reverts the change to the helm module which was unnecessary. I suggest this change is reverted as soon as the bug fix in evil-collection makes it's way to elpa. It would also probably be advantageous to only pull from github if helm is enabled and otherwise from elpa but I do not know how to accomplish that.

Considering how volatile the evil-collection package is turning out to be, I'm not too keen on tracking its HEAD. I'm even considering forking it, for Doom's sake.
In any case, it has been two weeks since the fix was pushed upstream, so it must be reflected in MELPA by now. If so, is this PR still necessary?


payULogger.CRITICAL: PosId is empty

Given:

When magento is configured with multiple websites/stores
PayU is only enabled for 1 of those websites

Issue:
Critical error gets logged when cart is loaded in all websites/stores where PayU is not enabled
Expected result:
No error is logged, as PayU is disabled
Affected code line:
https://github.com/PayU-EMEA/plugin_magento_24/blob/master/lib/OpenPayU/AuthType/Basic.php#L14
Call stack

Versions:

Magento 2.4.4-p2
PHP 8.1

Who also faces this issue, here is a patch:
diff --git a/vendor/payu/magento24-payment-gateway/Model/GetPayMethods.php b/vendor/payu/magento24-payment-gateway/Model/GetPayMethods.php
--- a/vendor/payu/magento24-payment-gateway/Model/GetPayMethods.php
+++ b/vendor/payu/magento24-payment-gateway/Model/GetPayMethods.php	(date<PHONE_NUMBER>195)
@@ -84,6 +84,10 @@
     public function execute()
     {
         try {
+            if (!$this->gatewayConfig->getValue('main_parameters/active', $this->storeId)) {
+                return [];
+            }
+
             $this->payUConfig->setDefaultConfig(ConfigProvider::CODE);
             $payURetrive = $this->openPayURetrieve;
             $response = $payURetrive::payMethods($this->availableLocale->execute())->getResponse();


add on amazon filter onto the isotope (perhaps even aws datacenters)

to make the filters usefull finally..................

that's actually a quite a good idea
speaking of which - it's time to improve those dashboard buttons, mayber?

nah


Projected-Based GPS Camera: example and updating Docs

Follows https://github.com/AR-js-org/AR.js/pull/75

[ ] Add at least one example using new projected gps camera component
[ ] Update AR.js official Docs

@nickw1 I will give you access so you can work directly on this branch on AR.js repo, also I will give you access to AR.js-Docs repository: https://github.com/AR-js-org/AR.js-Docs
You can open a branch + related PR also on there when you want :)

@nicolocarpignoli OK thanks! Will put together an example and work on some docs.

@nicolocarpignoli Basic example now up, hard-coded location and three projected entity-places. Will work on docs and try to put together a more complex example using openstreetmap data. Will keep you updated!

@nicolocarpignoli OK now have two examples, a basic one (as I mentioned the other day) and one which downloads OpenStreetMap data from an API and renders it as AR content. I've also added some docs to a 'projecred-based-example' branch in the docs repo.

@nickw1 basic example is ok, the other one I fixed something (see my commit) and changed some indentation, cosmetic stuff. But: it's stuck on 'Loading OSM data...'. Can you check please?

@nicolocarpignoli  ok thanks for the cleanup.
The bundle.js was actually intentional; to run the example you have to build it with browserify (the provided makefile does this) and then include the resulting bundle.js. Maybe I need to add a README to clarify this :-)

@kalwalt are you able to give a look at this and try it? I have very poor time these period unfortunately

Or someone else, any help is welcome

@nicolocarpignoli i would do, i tried the example in the issue time ago.i will let you know.

looks good to me. Great great job @nickw1 thank you again! merging and going to release this


Default colour for Grid Lines

Expected behavior
Hi, I am not able to change the default gridlines color with Chart.defaults.scale.gridLines.color  = 'rgba(200, 0, 0, 0.09)';
This should change the color or the grid lines for the charts, but it is not working.
Actually, I want to change the grid colors with dark mode toggle.
Current behavior
It is not changing the grid color.
Reproducible sample
Codepen
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
No response
chart.js version
v2.9.3
Browser name and version
Chrome
Link to your project
No response

As stated in the issue template:

Chart.js versions lower then 3.x are NOT supported anymore, new issues will be disregarded.

Also without a reproducable example we wont be able to help since it seems to work fine.


brew upgrade appsody does not work

Summary
[Debug] Creating log dir .appsody/logs
[Debug] Logging to file /.appsody/logs/appsody2019-11-07T11-20-02.809248.log
[Debug] Writing config file /.appsody/.appsody.yaml
[Debug] Getting latest version https://github.com/appsody/appsody/releases/latest
[Debug] Got version 0.4.10
[Info]
*
*
*

A new CLI update is available.
Please run `brew upgrade appsody` to upgrade from 0.4.7 --> 0.4.10.

Scenario

When I run appsody -v , above log returned.

I follow the instruction to run brew upgrade appsody , but got error Error: appsody 0.4.7 already installed

Actual output
Error: appsody 0.4.7 already installed
Expected output

Successful upgrade to 0.4.10

Current situation
I had to brew uninstall appsody and brew install appsody/appsody/appsody to make upgrade version.

Hi @DanielChuDC,  I just did this exact upgrade 0.4.7 -> 0.4.10 and had no issues.  I'm on macOS Catalina 10.15.1.   What OS and version are you on?  As I just did this upgrade I don't think the issue lies with the command not working at all, it could be not functional on an older OS version etc.

Hi @CameronMcWilliam , Thank you for your reply! I'm on macOS Catalina 10.15.1 too. Not sure why the error trigger.
As I cannot reproduce or inspect the error. I will close the issue.


How this tool differs to nikic/PHP-Parser

Just wondering, the PHP world now uses https://github.com/nikic/PHP-Parser for parsing.
What was the motivation to create new tool for parsing instead of extending the nikic's one?
What are the use cases I should use this one?
Thank you

I think this

Error tolerant design - in IDE scenarios, code is, by definition, incomplete. In the case that invalid code is entered, the parser should still be able to recover and produce a valid + complete tree, as well as relevant diagnostics.

and the level of performance is the answer

Thanks for sharing that. Do you have some specific example that fails in Nikic/PHP-Parser and works here?

Not really, just quoting from the readme :D
This project, however, seems to be written with Visual Studio Code in mind (I hope so, at least!) and their went crazy with its optimization (in terms of an app written in JS/Electron). I just want to say that they seem to know what they're doing.
Some benchmarks would be nice, indeed and I think that all we need is to wait a bit.

Hey all! Good question. I'll start from the beginning :smiley:.
Why another parser?
As @Sobak mentioned, this arose out of a need for Visual Studio Code. In particular, we're focused on ensuring PHP devs have an awesome tooling experience.
We recently looked into what ongoing PHP efforts we might want to contribute to, and was especially excited by some of the language service efforts from VS Code extensions like PHP IntelliSense and Crane. Eventually we zeroed into the parsers underlying these language services, and began investigating what it might look like have a PHP parser optimized for IDE scenarios (error tolerance, performance, tree representation, etc.).
Initially, the plan was simply to contribute some fixes upstream to Nikic's PHP-Parser, but the more we dug into it, the more we realized just how difficult it would be to retrofit an existing parser (let alone an auto-generated one) to satisfy these constraints.
And so, we started working on this handspun parser, key benefits being:

ingrained error tolerance - in editor scenarios, code is (by definition) incomplete. In the case that invalid code is entered, the parser should still be able to recover and produce a valid + complete tree, as well as relevant diagnostics. This translates to a more consistent overall experience, with less time spent tracking down esoteric bugs, and more time spent implementing features.
performance and memory usage - ultimately leaving more room for analysis of the trees, while still providing a snappy user experience. (To give a bit of context on our ambitions here., we generally aim for <100ms response time in the editor, which means language server operations should be <50ms to leave room for all the other stuff going on in parallel).
fully-representative tree and round-trippable back to the text it was parsed from - all whitespace and comment "trivia" are included in the parse tree, even when there are errors. This means that it’ll be suitable for applications such as linting, or tree-transformations like formatting and refactoring.

These features tend to be exceedingly difficult to retrofit an existing parser with if they are not architected for from the start (over time, you end up with a long tail of esoteric bugs). There are also some other aspects to this approach (like the API), and I recommend checking out the Design Goals, Syntax Overview, and How It Works sections for a more comprehensive overview.
When to use this parser?
Just like any parser, this parser produces a syntax tree from a source code string. This syntax tree represents the lexical and syntactic structure of source code.
So ultimately, you can use this parser in same scenarios you would otherwise use a parser, with the added benefit that it is optimized for cases where you might care about graceful error handling, memory + performance, and/or having a full-fidelity representation of the source code.
That said, I'd like to stress that the parser is still in its early stages - we know there are gaps, and we have a validation strategy for detecting and closing those gaps. At any point, you can take a look at our current status or just file an issue to ask, so you can decide whether it makes sense for your use case.
Hope that helps, and happy to share more if you're interested. The big question at this point is "where should we focus our efforts", and that really comes down to community feedback. So please please please, try it out, and let us know what you think! We'd love to hear your feedback, especially if it happens to come in the form of a pull request :wink:

Also, regarding performance metrics, stay tuned!
Right now we're hesitant to give precise numbers because we haven't set up an environment where we've sufficiently reduced variance between runs and sufficiently tested different platforms and architectures. You can follow #8 for more details on that, and the meantime, we have instructions on how to run the perf tests on your machine. And if you do that, I just realized one thing we forgot to mention there is that you should also have xdebug, profiling, etc. disabled.
The How It Works section also details some of not-yet-implemented ways we plan to improve memory/performance.

I see. Thank for your answers :)

Love what you're doing here, can't wait for great PHP support in VSCode and other IDEs. Thank you so much @mousetraps and everyone involved. ❤


Adds unlink functionality

Closes Closes GDT-48

Merge activity

Dec 24, 12:12 AM: @@NathanFlurry started a stack merge that includes this pull request via Graphite.


With defer_to_prod option, it raises

Expected behavior
With dbt 1.8 and defer_to_prod option set true, it shows no error in PROBLEMS tab.
Actual behavior
PROBLEMS Tab at the bottom shows an error described below.
Copy Message Result

There is a problem in your dbt project. Compilation failed: Manifest.merge_from_artifact() got multiple values for argument 'other'

Copy Result
[{
	"resource": "/workspaces/<reducted>/dbt/dbt_project.yml",
	"owner": "dbt10",
	"severity": 8,
	"message": "There is a problem in your dbt project. Compilation failed: Manifest.merge_from_artifact() got multiple values for argument 'other'",
	"startLineNumber": 1,
	"startColumn": 1,
	"endLineNumber": 1000,
	"endColumn": 1000
}]

Steps To Reproduce

Clone https://github.com/potsbo/vscode-dbt-power-user-defer-issue-reproduce
run poetry install in the repository
open the repository in Visual Studio Code
Update python interpreter to the venv created by poetry

Notes to reproduce
Visual Studio Code version
ersion: 1.89.1
Commit: dc96b837cf6bb4af9cd736aa3af08cf8279f7685
Date: 2024-05-07T05:14:32.757Z (1 wk ago)
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0

poetry version
poetry --version
Poetry (version 1.8.2)

others

It also happens on Codespaces
I suspect https://github.com/dbt-labs/dbt-core/pull/9199, which I believe was released in dbt-core v1.8.0, caused this issue

Log output/Screenshots

Operating System
macOS Sonoma 14.4.1 (23E224)
dbt version
1.8.0
dbt Adapter
dbt-bigquery 1.8.1
dbt Power User version
v0.39.9
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Fixed in 0.39.12. Please reopen if not the case.


Newest particle core failed to launch

This is my latest.log: https://mclo.gs/oxbeaAk , idk what is going on

same issue particle core and fzzy config lib crash game on startup the old particle core used to work just fine

Fixed in 0.2.1


A bug that leads to Arbitrary file download

Describe the bug
cod in vendor/s-cart/core/src/Admin/Controllers/AdminBackupController.php
    $download = request('download') ?? '';
    if ($download) {
        $file = storage_path() . "/backups/" . $download;
        if (file_exists($file)) {
            $headers = array(
                'Content-Type' => 'application/octet-stream',
            );
            return response()->download($file, '', $headers);
        }
    }

without any filter,can Splicing the path.
poc:
sc_admin/backup/?download=../../../../../../../../../../../../etc/passwd

To Reproduce
Steps to reproduce the behavior:

login in as admin
visit the path:sc_admin/backup/?download=../../../../../../../../../../../../etc/passwd
the file will be downloaded

Screenshots

version
newest
6.7

@a756379684 Thanks for report.
bug fixed https://github.com/s-cart/core/commit/328dd312866b86144b43941dee2ad942708f70da


use latest htmlhint

Thanks Steve!  I'll need to publish an updated htmlhint extension to the vs code marketplace for this to roll out.


Add hints for activation of MeshServices

Description
In case meshService is set to "Disabled" (which is default), we should display hints on how to get them activated (including docs link). Indicator to that is when there are no services listed in the mesh service type tabs.

lets do it


Errors running sample...

It shows login screen, i get to the AAD login page and I can login, it redirect back.. then booom this error...
I tried both an ORG id and a MS ID...
{"name":"AzureAD: OIDC Passport Strategy","hostname":"xxx-redacted-xxxx","pid":9050,"level":30,"msg":"v2 has no userinfo endpoint, using the content in id_token as the profile","time":"2017-04-06T01:42:43.949Z","v":0}
Error: No oid found
at Strategy._verify (/Users/xxxx/app.js:121:19)
at onProfileLoaded (/Users/xxxx/node_modules/passport-azure-ad/lib/oidcstrategy.js:124:27)
at self._idTokenHandler.urlParseException (/Users/xxxx/node_modules/passport-azure-ad/lib/oidcstrategy.js:1186:16)
at jwt.verify (/Users/xxxx/node_modules/passport-azure-ad/lib/oidcstrategy.js:966:12)
at /Users/xxxx/node_modules/passport-azure-ad/lib/jsonWebToken.js:79:16
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickCallback (internal/process/next_tick.js:104:9)

@kdupreez The problem can be fixed by adding 'profile' in the scope. I updated the code in the master branch. Thanks.


Changed Hoover thermostat to Gaussian

Hoover thermostat name can lead to confusion. Changed to its more general name "Gaussian" which better describes how the thermostat algorithm operates.

Thanks!
Conflicting PDF; can you resolve?

Ah. That was fast.

yeah I realized I had not handled that yet.
I dont think I recompiled the whole document, however.

That's OK.


[19967] Define a super client by environment variable

The feature allows the user to define a super client setting a new environment variable ROS_SUPER_CLIENT to true. This environment variable is used in combination with ROS_DISCOVERY_SERVER.
Merge after:

https://github.com/eProsima/Fast-DDS/pull/4047

@mergifyio rebase

https://github.com/Mergifyio backport 2.12.x 2.11.x 2.10.x 2.6.x


Expose DistributedSampler RNG seed argument

Relies on https://github.com/mosaicml/composer/pull/3724.
Closes #1676.

Note that tests will fail until Composer bump CC: @dakinggg  to track

I guess we need to update the requirement in setup.py accordingly? Forgot about that.

Yeah unfortunately it won't work until we have the necessary code in a Composer release and then update Foundry. You can of course install from branches to unblock yourself as needed.

Composer v0.28.0 has been released and dependency updated. Rerunning CI/CD


Determine Galaxy Side Commands to support galaxy plugins for data sources

Determine all of the Galaxy Side commands to support galaxy plugins as a source of game data.
Sample when there is no client response back:
{"id":"0","jsonrpc":"2.0","method":"get_capabilities","params":{}} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"} {"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"}
From a fresh reboot (already imported data) from the generic plugin.
plugin-test-97543122-7785-4444-2254-711233556699.log

The current implementation has cause the need for #3 .

Also see. https://github.com/AndrewDWhite/GalaxyGenericImporterPlugin/issues/105

Some plugins also appear to require the commands to be awaited for their response.
https://github.com/UncleGoogle/galaxy-integration-humblebundle/blob/master/galaxy_emulator.py#L76


CASSANDRA-16851: upgrade Jackson 2.9->2.12

As per title, patch to upgrade Jackson version from the latest 2.9 patch to the latest 2.10 patch.
One change required wrt access of JsonStringEncoder.
Assuming that trunk is for Cassandra 4.1: while this should be safe change seems better than for 4.0.x.
I am running the test suite locally which seems to take a while. Not sure if there's Cassandra CI of some kind for other tests; will update if and when test suite passes (or if there are failures). Leaving as [WIP] until then.

Whops. Used wrong issue id in commit, fixed in title.

As per @ekaterinadimitrova2 's suggestion, try targeting the latest stable Jackson release, 2.12(.4).

@michaelsembwever As per above comment, decided to go with minimal diff here. A full CI run would make sense now, I think?

Merged outside of this PR (into 3.11, 4.0, trunk), closing PR.


Sane defaults for OSM field widths

This is something I think ESRI may have a closer look at. Currently, the OSM Attribute Selector seems to apply a default width of 100 characters to each and every key extracted from the key/value storage.
I am not actually sure how file geodatabases, or different enterprise geodatabases, handle the storage of the actual data technically and what strains this put on the storage, but purely from a user perspective, it would be desirable to have some sane default widths for most keys. Many keys only have valid values that are much shorter than 100 characters. By using the 100 character default for all keys, attribute tables in ArcMap become unwieldy wide and difficult to browse or get an overview from.
I think there must be a better way to handle this, based on statistics for different keys and the values therein. OSM seems to have quite a landscape of tools and APIs accessing and extracting information from the main OSM key/value database. E.g. TagInfo (http://wiki.openstreetmap.org/wiki/Taginfo/API) seems to offer an API that may offer oppertunities, or maybe Overpass Turbo could help giving answers (http://wiki.openstreetmap.org/wiki/Overpass_API/Language_Guide).
What I envision:

Somehow extract sane default widths from some OSM API for all current keys in the database, e.g. by getting the 95%-98% smallest values for each key.
Store these widths as XML or so, to be automatically used and applied by the OSM Attribute Selector each time a new field mapping needs to be made for the storage of a key
If the key is not present in the XML file (e.g. newly introduced key), only then, default to 100 characters (updating of the file could help setting a better default later).

what is the width of those fields in OSM itself? that's what should drive the design of the data structure in the geodatabase. after the import you could shrink field sizes based on the data actually imported.

what is the width of those fields in OSM itself? that's what should drive the design of the data structure in the geodatabase. after the import you could shrink field sizes based on the data actually imported.

That is maybe the point, there is no real width in OSM... At the real backend of OSM, it is a key/value storage in PostgreSQL. I don't know the current restrictions, but values were once restricted at 255 characters, at least I saw some mailing list posts from 2009 relating to that figure. This means the only real way to "device" useful defaults for field widths is to base these on real statistics about value length per key.
If you want to dive a little bit deeper into the OSM database stuff, here are links to Wikipedia pages about the Rails application driving the website, and the database. The "Database"
http://wiki.openstreetmap.org/wiki/The_Rails_Port
http://wiki.openstreetmap.org/wiki/Rails_port/Database_schema
http://wiki.openstreetmap.org/wiki/Database
However, I don't think this will give you more clues as to a solution, as it only illustrates the fact of the key/value storage backend, and thus no available "defaults" that could be copied for this project. That is why I think getting statistics from one of the OSM APIs may be the best way to go, and use those for more realistic defaults.

Looking at the DB Schema the node_tag:k (key) and value are using Character Varying. However the node_tag in the Rails Model has a validation of length: 255.
So seems like the geodatabase should default to 255 instead of 100.

Hi Andrew,
Yes, the current implementation of the OSM Attribute Selector actually truncates any values bigger than 100 characters. The code is in OSMGPAttributeSelector.cs
E.g. see these two excerpts:
// generate a new attribute field
                                        IFieldEdit fieldEdit = new FieldClass();
                                        fieldEdit.Name_2 = tagKey;
                                        fieldEdit.AliasName_2 = nameOfTag + resourceManager.GetString("GPTools_OSMGPAttributeSelector_aliasaddition");
                                        fieldEdit.Type_2 = esriFieldType.esriFieldTypeString;
                                        fieldEdit.Length_2 = 100;

//...then stored the value in the attribute field
                                    // ensure that the content of the tag actually does fit into the field length...otherwise do truncate it
                                    string tagValue = tagItem.v;

                                    int fieldLength = attributeFieldLength[fieldIndex];

                                    if (tagValue.Length > fieldLength)
                                        tagValue = tagValue.Substring(0, fieldLength);

                                    osmRow.set_Value(fieldIndex, tagValue);
           rowChanged = true;

However, my main point was that, since many important keys have only a limited range of valid (I can better write "most used") values, it might be a better option to derive defaults for common keys based on statistics.
OpenStreetMap has an open data model, anyone can enter anything they like as tag values. That

Currently, according to OpenStreetMap TagInfo (https://taginfo.openstreetmap.org/keys), there are 53382 unique keys in the OSM database. I am not saying we need to derive default for all of these, but even having defaults for the thousand most used keys, would be of value.
And storing default field width values for even 50k keys in XML or so to be used by the OSM Attribute Selector, should technically be 0 challenge (of course, deriving the default values themselves is not... I am aware of that)

Deriving analyzed defaults is intriguing - but is it necessary? Is there a problem with changing it to 255 so it works all the time?

Deriving analyzed defaults is intriguing - but is it necessary? Is there a problem with changing it to 255 so it works all the time?

That is actually a question the ESRI geodatabase experts need to answer. Is it a problem to have an Oracle or SQL Server enterprise geodatabase with let's say 100 text fields all 255 characters, with many of them only partially filled with text, because the actual values in many keys are shorter?? What is the performance penalty if I need to export data from such tables if these tables contain data of entire continents, or possibly the globe, as I need to for my renderer?
Of course, working on my ArcGIS Renderer for OpenStreetMap (ask Christine), I am all in favour of not truncating values. But the above is a realistic scenario, as my renderer needs to extract OSM keys first to fields, before it can generate the thematic feature classes using SQL definition queries.
I currently have over 300 thematic feature layers to generate something like the images below (all straight rendered from OpenStreetMap data, and requiring the ArcGIS Editor for OpenStreetMap's OSM Attribute Selector to support my ModelBuilder / Python based renderer), but it requires a quite large set of attribute fields. I have not seen major issues with several up to 10-20 GB extracts of OSM using File Geodatabases, but what about bigger?

By the way, I realized my suggestion is partially flawed, especially the 95-98% cut off of most used values per key. Let's assume we have a key with a rather well defined Wiki documented domain, like
surface = x.
E.g.:
Valid values and present in the OSM database (example):
paved
asphalt
cobblestone
concrete
paving_stones
Of course, if we just count the 95-98% most used values to set the default width of the field, any of the above values may actually not make it, and not be regarded when determining the default width. This might lead to the situation where a value like "paving_stones", can not be stored, since it was not considered one of the most used values in statistics.
Therefore, maybe another approach is needed:

Test if there at least 1000 occurences of key in the OSM database (as otherwise default field widths will probably not be reliably determined, 1000 occurences is also the arbitrary cut-off the OpenStreetMap carto developers use for considering to render a particular tag, e.g. surface = paved).
Test if a key has less than let's than say 50-100 unique values, as that probably indicates some documented domain for the values
If less than 50 unique values, get the longest value of the key, use this as the default
If more than 50 unique values, get the 95-98% most used keys, and determine the longest value, set this as default.

On the other hand, maybe I am making this all way to complex..., and we should try to use existing sources, like this JOSM Preset XML file, that has many of the most used domains defined:
https://josm.openstreetmap.de/browser/trunk/data/defaultpresets.xml
Anything not in the preset, could default to 100 or 255 char field width...

I now found an article that seems interesting in terms of the possible caveats when declaring a size for variable width columns:
http://aboutsqlserver.com/2010/08/18/what-is-the-optimal-size-for-variable-width-columns/


[AppContext] Add AppContext

This patch add basic app context with setting current working directory
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>Implemented without std::experimental::filesystem
~Current implementation (as of f0d969f) uses std::experimental::filesystem.~
~ndk does not support std::filesystem until r22~
~So either 1. we have to support from r22 or 2. reimplement related method in this patch.~
~IMO, I think we should stick to r21 since other people might not be using r22. and reimplement app_context.cpp~

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #728. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/728-202011120948460.27518892288208-aead9da1c37ccd1db50374013a5bc25c3b219c63/.

Could you check the ci?

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/728-202011121120150.89197611808777-5fad23cc27cbc3a6bf92664787073abcbc5e2cd0/.


Question: if/how does this relate to the Java Client produced by the Symphony open source community?

Keen to better understand if/how this project relates to the Java Client recently produced by the Symphony open source community.

There is no relation. The symphony-api-client-java repository refers to the Symphony supported and produced Java API client.

@opoupeney functionally they appear to overlap quite substantially, which is rather confusing.
How should a developer choose between them?

@opoupeney any updates on this?


Postmaster Templates :: Secondary toggle (Old 278)

In gitlab by @A-Lawrence on Aug 31, 2015, 01:07
Implement a toggle for secondary email enable/disable on the template list.

In gitlab by @A-Lawrence on Aug 31, 2015, 01:18
mentioned in issue #287

In gitlab by @A-Lawrence on Aug 31, 2015, 01:18
mentioned in issue #287

In gitlab by @A-Lawrence on Aug 31, 2015, 01:18
mentioned in issue #287

In gitlab by @A-Lawrence on Aug 31, 2015, 01:18
mentioned in issue #288

In gitlab by @A-Lawrence on Aug 31, 2015, 01:18
mentioned in issue #288

In gitlab by @A-Lawrence on Aug 31, 2015, 01:18
mentioned in issue #288

In gitlab by @A-Lawrence on Aug 31, 2015, 01:53
No longer required as in 5.1 we've retired postmaster pat.


Add content collection custom IDs section

Description (required)
As discussed on Discord, this PR adds back an equivalent of the “Defining custom slugs” section in the current version of the docs for the content collections page in the v5 docs.
The content is based on the current version but updated to match the new changes related to the Content Layer API.
A few notes:

It works with JSON files too.
The sentence about slug being a special, reserved property name not allowed in schema is removed, as it is not true anymore.
Not sure about the capitalization of IDs in the title.

Related issues & labels (optional)

Closes #
Suggested label: 5.0.0-beta

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

en/guides/content-collections.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


[AutoPR datafactory/resource-manager] [Datafactory] Add folders to Pipeline and Dataset

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3636

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/2136


NOISSUE - Update approach on Things policies

What does this do?
Which issue(s) does this PR fix/relate to?
Noissue
List any changes that modify/break current functionality
None
Have you included tests for your changes?
No
Did you document any new/modified functionality?
No
Notes

Codecov Report

Merging #1808 (fb7180d) into clients (b4eb4a5) will increase coverage by 0.64%.
The diff coverage is 91.04%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           clients    #1808      +/-   ##
===========================================
+ Coverage    62.54%   63.19%   +0.64%
===========================================
  Files          122      115       -7
  Lines         8968     9112     +144
===========================================
+ Hits          5609     5758     +149
+ Misses        2792     2762      -30
- Partials       567      592      +25

Impacted Files
Coverage Δ

certs/postgres/certs.go
0.00% <ø> (ø)

consumers/notifiers/api/transport.go
91.01% <ø> (ø)

consumers/notifiers/postgres/database.go
74.19% <ø> (ø)

consumers/notifiers/service.go
60.00% <ø> (-28.00%)
:arrow_down:

consumers/writers/cassandra/consumer.go
77.55% <ø> (ø)

consumers/writers/influxdb/consumer.go
89.87% <ø> (-5.48%)
:arrow_down:

consumers/writers/mongodb/consumer.go
79.31% <ø> (ø)

consumers/writers/postgres/consumer.go
65.76% <ø> (ø)

consumers/writers/timescale/consumer.go
66.99% <ø> (ø)

http/api/transport.go
69.30% <ø> (-2.13%)
:arrow_down:

... and 27 more

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


Add nova group in product summary

Description

Display the Nova group in the product view.
Minor changes in strings.xml

Screen-shots, if any

Checklist
Make sure you've done all the following (You can delete the checklist before submitting)

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.
[x] Code is well documented
[x] Include unit tests for new functionality
[x] All user-visible strings are made translatable
[x] Code passes Travis builds in your branch
[x] If you have multiple commits please combine them into one commit by squashing them.
[x] Read and understood the contribution guidelines.

Look good to me, tested it. Works.


LXD: Document the preseed file format for lxc init

Documentation: https://documentation.ubuntu.com/lxd/en/latest/
GitHub repo: https://github.com/canonical/lxd
Contribution guide: https://documentation.ubuntu.com/lxd/en/latest/contributing/

You can initialize LXD through a preseed file - see Non-interactive configuration.
This section also contains an example for a preseed file. However, this is only an example and does not contain all available fields. For example, it is missing the fields for clusters (some of these are included in How to form a cluster).
The top-level struct is:
config: {}
	networks: []
	storage_pools: []
	profiles: []
	projects: []
	cluster:
	  server_name: ""
	  enabled: false
	  member_config: []
	  cluster_address: ""
	  cluster_certificate: ""
	  server_address: ""
	  cluster_password: ""
	  cluster_certificate_path: ""
	  cluster_token: ""

We should add a reference page that contains the full file format, and link to it from the initialization and clustering how-tos.
This requires some research/checking the code and testing.

Hi @ru-fu! I would like to work on this issue.

Thanks @activus-d ! I've assigned the issue to you now.
Let me know if anything is unclear!

Thanks a lot @activus-d ! This has now been merged. :)
https://documentation.ubuntu.com/lxd/en/latest/reference/preseed_yaml_fields/


VLAZ: Watch +27791653574

VLAZ requests the watch of the watch_number +27791653574. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Jeff Schaller in Charcoal HQ


feat: run shellcheck & add github action

This PR cleans up the bash scripts by fixing all issues except SC2001 reported by shellcheck. The SC2001 issue is an info level message which I think would be nice to clean up, but left that in for now.
Also added a github action to run shellcheck to ensure there are no issues in future prs

Hi @pimlie,
Thanks for PR, sorry I seem to have missed it in the noise. This seems well worth doing and appreciate the time you put in to check the scripts for safety with shellcheck.
I'll try to pull the branch in locally and test it out from start to finish.
The main thing I was concerned about look at the PR was double-double quotes the with the variable assignment with default value fallback after the read prompt; testing this manually in bash seems to work. I've heard of shellcheck before, and I guess we should trust the recommendations from the experts :)

Thanks for the review, have fixed the indentation. And yeah, some of the shellcheck recommendations might look 'off' at first. Had the exact same concerns when I first ran shellcheck :)
Thanks for sharing these scripts btw, as fyi I'm referring to your repository/scripts here: https://github.com/pimlie/ubuntu-mainline-kernel.sh#secureboot

This all LGTM. Thanks for fixing the linting.
I'm new to the GitHub workflows, in GitLab we need to enable CI on the repository for the functionality to work. Do I need to do the same here or will just including the file enable it?


manifests: bump loglevel of operator to normal

https://github.com/openshift/cluster-kube-controller-manager-operator/pull/241

/retest

/retest

/retest

/retest
memory shortage
this PR must be cursed.


pull request for e2e test at 01/18/2017 14:56:16

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update version of trio on pypi

Hey,
The current version of trio on pypi is 0.2 but the version in tree has had 2 more versions since. could we get a new release?

I didn't understand this-- what package is version 0.2?

appears I got confused 🤦🏼♀
sorry for the noise!


Add border radius

Adding borderRadius as an optional style.

@jte0711 sorry i forgot to push my last version the conflicts are just in package json i believe

@jte0711 updated the PR

can we update also README so ppl may know about this new 1 ?

@natysoz yes, done. let me know if there's anything else


added --version flag to print tool version

but we already have --version and had since my first release, so this only adds it to docs

You are right! Completely missed it. I'll remove unneeded code then and will leave only docs update.

          1 Error

:no_entry_sign:
Any changes to library code need a summary in the Changelog.

  Generated by :no_entry_sign: danger


Refactor/complete project refactoring

This PR reflects all nuances described in #46.
This is a completely new terraform provider with breaking changes.
Features:

MERGE and OVERWRITE mode as discussed on #46.
parallel resources processing (got rid of mutexes) that is the fix of #31
better input data validation that is the fix of #32
ability to change email_mode (refer to https://www.namecheap.com/support/api/methods/domains-dns/set-hosts/ EmailType request parameter) that is the fix of #37
stability improvements

Remaining work:

on create, if default parking records are set, then remove them before applying the resource ✅
tests (next PR)
documentation & examples (next PR)

This is looking great!


Error in events

Recently all containers in microk8s cluster were restarted. In events I found
(combined from similar events): Readiness probe errored: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "b5b7ad431e1d9c795f6922bd688d8593b9ad81b8ebb765f5707f94616502f253": OCI runtime exec failed: fork/exec /snap/microk8s/1073/bin/runc: too many open files: unknown

What does it mean?

My guess is that some pods are opening sockets, files etc that are not propert closed.  Check the code behind what the livenessProbe or readinessProbe is doing.
You can always increase the linux ulimit to alleviate this.

You can always increase the linux ulimit to alleviate this.

How to do it for the container?
Thanks for helping

The number you gave is already high.  Where is this set?
Last time i did this was when im installing elasticsearch on k8s.
The yaml came with an init container.
      initContainers:
      - name: set-vm-max-map-count
        image: busybox
        imagePullPolicy: IfNotPresent
        command: ['sysctl', '-w', 'vm.max_map_count=262144']
        securityContext:
          privileged: true


Implement gateway alias for routes

Add annotation "gateway.istio.io/alias-for". If this annotation
is present in a gateway, any routes that bind to the gateway
in the annotation will bind to the gateway with the annotation.
This allows us to build other gateway controller on top of
Istio gateway controller.
Please provide a description of this PR:

/cherrypick release-1.13

@howardjohn: new pull request created: #36927

In response to this:

/cherrypick release-1.13

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


Menus not working after upgrading to 1.0.0

Hello all.
I have noticed after upgrading to<EMAIL_ADDRESS>my application menus stopped working. They are being created within the MuiModal-root but the MuiModal-hidden class aren't being removed.

[x] This is a v1.x issue (v0.x is no longer maintained).
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

MuiModal-hidden class getting removed from the modal root.

Current Behavior

MuiModal-hidden class is still applied to modal root.

GIF reference

Context
It is not working when I try to show the drawer, menu within the AppBar nor within the rows per page menu on TablePagination.
Your Environment

Tech
Version

Material-UI
v1.0.0

React
v16.2.0

browser
Google Chrome

Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!

The fix for this is to also ensure react-dom is updated to at least 16.3.0

@carlgunderson Yes indeed.

Thanks for this. I was fighting with all of my menus after upgrading to 1.0. Upgrading to React and react-dom 16.3 from 16.2 fixed it.


Reduce I/O with typeserver during typechecking

The idea would be to memoize valid Java constructs (class names, method call / field access signatures).


[CP][beta channel] Verify consistent null safety modes of JavaScript modules

commit(s) to merge: d0ee5dbe4088f5b1cd0ccda04e9f7d87fe9a9be6
merge instructions: patch CL/176504 (merge had conflicts, CL resolves them).
What is the issue: If the build/test infra is misconfigured JavaScript modules compiled with different null safety modes could be loaded in the browser as part of a single app.
What is the fix: Verify the null safety mode each module was compiled with matches the mode of the dart sdk module loaded in the browser.
Why cherrypick: To catch any infrastructure errors before the stable release. The priority of this cherry pick should be considered low and we only hope to include this with other cherry picks if they happen.
Risk: Low, we have not seen any signs of errors.
Link to original  issue(s): NA
/cc @kevmoo @mit-mit @whesse @athomas @vsmenon @franklinyow @sigmundch

@pcsosinski

@pcsosinski

Merged in 01bc1f5083950751261af2219b65df445ad8f83f (2.12.0-133.6.beta).

Merged in 01bc1f5083950751261af2219b65df445ad8f83f (2.12.0-133.6.beta).


Refactor crate

Extract mod session containing Session from lib.rs
Refactor Error: Use thiserror::Error to simplify its implementation.

This change is


Update README.md

Update of the README.md with the problems solved

resolution of the lack of the tracking of the issues modification of the project


for NIO 2.0.0 and Swift 5: warnings to errors

for NIO 2, we should swift build --build-tests -Xswiftc -warnings-as-errors -Xcc -Werror. We can't in NIO 1 because of the tests for deprecated stuff.

that's done


Support assumptions and caveats in docstrings

Support assumptions and caveats written within function/class documentation:

Python docstrings, with custom heading defined in napoleon config. Should configure this in the hook from #8
R roxygen sections

Support for R roxygen @section added.
Python docstrings implementation would require users to configure a sphinx extension. Also, the format of an assumption wouldn't fit well into a docstring currently.


'View profile' ACL actions isn't properly working.

https://una.io/page/view-album-media?id=97&context=album
https://una.io/cmts.php?sys=bx_forum&id=505&cmt_id=1571

I cannot reproduce the issue. Looks like it was fixed in Ticket #906.


tpmmgr should not use deprecated /persist/config

/persist/config is deprecated, and will not exist after fresh USB installs
in those cases, creation of the certs will fail
/persist/certs already exists on device, re-using that instead of /persist/config

Signed-off-by: Hariharasubramanian C S<EMAIL_ADDRESS>

LGTM.
But are we currently failing after a USB install? Fatal or just missing the certs?
Do you also want move from /persist/config to /persist/certs, or you just recreate them in /persist/certs?

Hi @eriknordmark
There is no fatal. It does not create the certs, and fails saying that /persist/config directory is not found. In the interest of keeping it simple, I am just recreating it in /persist/certs.


WinGet strings need to be updated

Microsoft PowerToys version
0.47
Running as admin

[ ] Yes

Area(s) with issue?
Installer
Steps to reproduce
WinGet now accepts the store and there is naming conflict now between them.
Since the store currently isn't on Win10 (but will), our current guidance will be the following string
winget install PowerToys -s winget

Docs.msft
I bet multiple spots in PowerToys docs will needs to be updated

✔ Expected Behavior
No response
❌ Actual Behavior
WinGet throws error as there are two stores
Other Software
No response

I cannot find any more winget strings that need to be updated.
Can we close this?

Think bug one was on docs.Microsoft and we did that


Unsupported export map resolution

Currently, the package' export map looks like this:
{
  "types": "./utils.d.ts",
  "module": "./esm/utils.js",
  "default": "./utils.js"
}

However, most bundlers that uses the export map (e.g. Vite, ESBuild, Skypack) uses the import/require resolution (see here) and NodeJS supports this natively. Currently, the behavior is that the CJS bundle gets picked up even if the bundle target is ESM.
Suggested solution would be to use import/require over module. (We can still retain "default")

Specifying import seems to cause Dual package hazard.
This isn't very nice. Suggestions are welcome. Past discussions are scattered around unfortunately.
We would like to keep all zustand/jotai/valtio consistent.
zustand does probably not have the dual package issue.
jotai and valtio do have the dual package issue because they rely on symbols.
It would be nice if we can reproduce the dual package problem and try to find a working config.

#110 is also an issue, we'd like to solve.

Thanks for linking that issue.

It seems that the esm module is attempting to re-import the CJS bundle, which seems to be the issue for Skypack (as Skypack uses the import/require resolution). As we know, Node, by default, resolves to the default/require resolution if the package is not defined with "type": "module" and this could be the cause of what seems to be ESM and CJS mixing up. We could probably solve this by opting into using relative imports instead of node_modules resolution. Less roundtrips, too.
On a side note, the index export is resolvable by resolve.exports, but this is not true for the rest of the exports (vanilla, utils, etc.). The legacy resolution would still attempt to resolve the relative path from the index export.

I tested the package.json against import / require resolution and this is how all of the bundlers and resolvers resolve valtio. As you can see, if the resolvers uses the export map, it picks up the CJS bundle.

Above is the resolution output if we use the import / require. Do take note that since the resolution is correct, mixture of CJS and ESM modules will never happen as the modules are correctly resolved (the currrent behavior was, if the we import valtio, it resolves to either the CJS or ESM, however if valtio imports valtio/vanilla, it can only resolve to valtio/vanilla's CJS bundle.

some previous discussion: https://github.com/pmndrs/jotai/issues/354
I think dual package hazard is rare, but it can be intentionally produced, no?

but it can be intentionally produced, no?

Could be with Node versions that do not support the new resolution spec: https://nodejs.org/api/esm.html#esm_resolution_algorithm
which is the current resolution most bundlers follow (e.g. @rollup/plugin-node-resolve, ESBuild, etc.)

package valtio: cjs and esm
a 3rd-party package valtio-foo: cjs only
app using both packages: webpack?
does this work?

I'm not that familiar with Webpack's resolution algorithm, although I'll try with ESBuild and see how the bundle output looks like.

I managed to make a reproduction of dual package hazard. Here's the output log of the modules:

module D:
console.log('imported module-d');

export default function moduleD() {
  console.log('D');
}

module A:
import D from 'module-d';

console.log('imported module-a');

export default function A() {
  D();
}

module B:
import D from 'module-d';

console.log('imported module-b');

export default function B() {
  D();
}

module C:
import A from 'module-a';
import B from 'module-b';

console.log(A, B);

Behavior:

Module D produces both ESM and CJS builds
Module A produces a CJS build, module D marked external
Module B produces a CJS build, module D marked external
Module C produces an ESM build, bundling all modules.

So the answer to this

but it can be intentionally produced, no?

Was yes, although it can only be intentionally produced by a third-party author.

IMO, 1P should not be the one reliable for providing a bridge between CJS and ESM (for preventing state isolation).

@LXSMNSYC Thanks for the repro! Yeah, feels like a rare case.
https://github.com/pmndrs/jotai/pull/289#discussion_r574271494
Would you check this conversation? It originally suggested "module".
Can you follow, why webpack introduced it?

I think we'd like this?
{
  "types": "./utils.d.ts",
  "module": "./esm/utils.js",
  "import": "./esm/utils.js",
  "default": "./utils.js"
}

It originally suggested "module".

It seems that this condition was introduced by Webpack (much like the "module" field in package.json)
According to here: https://webpack.js.org/guides/package-exports/#providing-commonjs-and-esm-version-stateful
If the package was stateful (in valtio's case, the symbols), the package would still need to provide an import/require resolution along side module, however this time, import provides a wrapper file for the require export file.
Compatibility-wise, this would be good, however I'm not sure if tree-shaking would work here.

I found another solution: https://nodejs.org/api/packages.html#packages_approach_2_isolate_state
We can move valtio's state and side-effects to another module. This way, valtio can provide both CJS and ESM bundles while sharing the same state and side-effect

Okay, if symbols are only blocking, we should prefer using Symbol.for. Let me draft a PR.