[Bug]: Module cases "JavaScript heap out of memory"

Contact Details
<EMAIL_ADDRESS>What happened?
Module causes out of heap memory when doing a yarn install on a clean repo with the package lock set up, And when adding new packages after the module is installed eg, yarn add vue-json-csv.
Increasing the heap allocation with export NODE_OPTIONS=--max-old-space-size=8192 has no effect
Once after the module is removed does yarn install and yarn add <package> works again.
Version
nuxt-vuetify
0.2.18
yarn
1.22.19
node
v18.16.0
What browsers are you seeing the problem on?
Terminal
Relevant log output
From clean image
❯ yarn install
yarn install v1.22.19
[1/4] Resolving packages...
⡀<EMAIL_ADDRESS><--- Last few GCs --->

[594:0x631e410]    90854 ms: Mark-sweep 3937.2 (4143.5) -> 3936.6 (4143.3) MB, 643.8 / 0.0 ms  (average mu = 0.086, current mu = 0.006) allocation failure; scavenge might not succeed
[594:0x631e410]    91719 ms: Mark-sweep 3937.4 (4143.8) -> 3937.1 (4143.8) MB, 862.8 / 0.0 ms  (average mu = 0.044, current mu = 0.003) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb7a940 node::Abort() [node]
 2: 0xa8e823  [node]
 3: 0xd5c940 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xd5cce7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xf3a3e5  [node]
 6: 0xf3b2e8 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [node]
 7: 0xf4b7f3  [node]
 8: 0xf4c668 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0xf26fce v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
10: 0xf28397 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
11: 0xf088e0 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
12: 0xeffeac v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawArray(int, v8::internal::AllocationType) [node]
13: 0xf00025 v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArrayWithFiller(v8::internal::Handle<v8::internal::Map>, int, v8::internal::Handle<v8::internal::Oddball>, v8::internal::AllocationType) [node]
14: 0xf13db5 v8::internal::Factory::NewJSArrayStorage(v8::internal::ElementsKind, int, v8::internal::ArrayStorageAllocationMode) [node]
15: 0xf13ebe v8::internal::Factory::NewJSArray(v8::internal::ElementsKind, int, int, v8::internal::ArrayStorageAllocationMode, v8::internal::AllocationType) [node]
16: 0x10e8201 v8::internal::ElementsAccessor::Concat(v8::internal::Isolate*, v8::internal::BuiltinArguments*, unsigned int, unsigned int) [node]
17: 0xdbcfd0  [node]
18: 0xdc6084 v8::internal::Builtin_ArrayConcat(int, unsigned long*, v8::internal::Isolate*) [node]
19: 0x16fb7b9  [node]
[1]    594 IOT instruction  yarn install

Installing a new package after installed
 yarn add vue-json-csv
yarn add v1.22.19
[1/4] Resolving packages...
⠂<EMAIL_ADDRESS><--- Last few GCs --->

[694:0x562b500]   227653 ms: Mark-sweep 3936.7 (4143.8) -> 3936.5 (4143.8) MB, 495.4 / 0.0 ms  (average mu = 0.171, current mu = 0.004) allocation failure; scavenge might not succeed
[694:0x562b500]   228204 ms: Mark-sweep 3936.9 (4144.0) -> 3936.7 (4144.0) MB, 549.4 / 0.0 ms  (average mu = 0.096, current mu = 0.003) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb7a940 node::Abort() [node]
 2: 0xa8e823  [node]
 3: 0xd5c940 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xd5cce7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xf3a3e5  [node]
 6: 0xf4c8cd v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 7: 0xf26fce v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 8: 0xf28397 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 9: 0xf088e0 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
10: 0xeffeac v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawArray(int, v8::internal::AllocationType) [node]
11: 0xf00025 v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArrayWithFiller(v8::internal::Handle<v8::internal::Map>, int, v8::internal::Handle<v8::internal::Oddball>, v8::internal::AllocationType) [node]
12: 0xf13db5 v8::internal::Factory::NewJSArrayStorage(v8::internal::ElementsKind, int, v8::internal::ArrayStorageAllocationMode) [node]
13: 0xf13ebe v8::internal::Factory::NewJSArray(v8::internal::ElementsKind, int, int, v8::internal::ArrayStorageAllocationMode, v8::internal::AllocationType) [node]
14: 0x10e8201 v8::internal::ElementsAccessor::Concat(v8::internal::Isolate*, v8::internal::BuiltinArguments*, unsigned int, unsigned int) [node]
15: 0xdbcfd0  [node]
16: 0xdc6084 v8::internal::Builtin_ArrayConcat(int, unsigned long*, v8::internal::Isolate*) [node]
17: 0x16fb7b9  [node]
[1]    694 IOT instruction  yarn add vue-json-csv

### Additional context

_No response_

v0.2.20 does appear to have resolved it...
I was able to confirm this by going back and forth between versions (0.2.18, 0.2.20) trying to trigger the error.. 0.2.18 would constantly trigger, where 0.2.20 did not.


fix: change categories and correct typo

Codecov Report

Merging #9 (13285d0) into develop (8919a3e) will increase coverage by 82.44%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop       #9       +/-   ##
============================================
+ Coverage         0   82.44%   +82.44%
============================================
  Files            0        2        +2
  Lines            0      262      +262
============================================
+ Hits             0      216      +216
- Misses           0       46       +46

Impacted Files
Coverage Δ

src/lib.rs
86.17% <ø> (ø)

src/elements.rs
25.00% <0.00%> (ø)

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 8919a3e...13285d0. Read the comment docs.

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


chore: update golang module

This module is being referenced in our docs to show how to build dagger using Go. However, since a few days ago, Dagger requires go1.23.1 to fix some CVs
Bumping module accordingly

cc @kpenfound


What does the column sign "R" mean?

And if it means "resolved" how it comes after lines with "B" on runtime? it doesn't make sense.

I think it is rejected, meaning that the debugger will ignore that line.

I think it is rejected, meaning that the debugger will ignore that line.

Ty, So it might be a bug, the debugger actually paused on these lines

It's means restarted. Underlying debugger is restarted.

@morhaham @deodesumitsingh
It means rejected (not restarted, lol)
Sings are defined and manipulated by nvim-dap, not nvim-dap-ui, and can be find here:
https://github.com/mfussenegger/nvim-dap/blob/7ff6936010b7222fea2caea0f67ed77f1b7c60dd/doc/dap.txt#L479-L487
- `DapBreakpointRejected` to indicate breakpoints rejected by the debug
  adapter (default: `R`)

That's said, this is not an issue with nvim-dap-ui, but instead with nvim-dap or the debugger/debug-adapter you use.
This issue probably should be closed.


ModularUI results do not update on scroll

When I load the Modular UI results, I get the first 5 or 6 results (enough to fill my screen in my layout) and then a bunch of loading components. Scrolling does not update the state of the "loading" results, but oddly, zooming out does. I am not using a placeholderTemplate but adding that makes no difference.

Interesting! Would be good to narrow down if this an issue with the browser or device you're on, or the site the Modular UI is being used on.
For the former — how does the search at https://cloudcannon.com/ behave? That's using the Modular UI, and should be loading correctly on scroll.
For the latter — can you share a link to your case where it isn't working? It's using a fairly standard IntersectionObserver so my only guess would be some outer layout/css that is causing those events to not trigger.

The CloudCannon search behaves as expected.
I don't have this pushed anywhere that would be easy to review, but here's a screengrab:
https://github.com/CloudCannon/pagefind/assets/16374762/b98f21c1-e604-4852-81be-c9e5153b29da
The branch of this is at https://github.com/artshumrc/scrolls-astro/tree/improve-search-ui.

It definitely seems to be a some sort of view issue. If I reload the page with devtools up, it only loads 2 results, and then if I undock devtools it shows 5 results ...
https://github.com/CloudCannon/pagefind/assets/16374762/9e83462f-e72c-4dec-852d-d9b925ff4595

Any thoughts on this one?


Flow of the app - [TECHNICAL]

GET / (home)
Run entry.jsx
Render all components used in containers/Index.jsx starting from Index.jsx itself.
Clicking CHECKUP button, makes a POST to /api/checkup with form data
Return result (as json) if any checkup result exist on our database for this project and see progress indicator for next step ( doing new checkup...)
Run checker scripts against the user's repository
Update database with results
Return results (from database, not directly for now) to react app as JSON

After we finalize the format of JSON reponse, we will change little bit of code and the props of react components, then react will handle the UI update.
We need to decide if that flow is OK before starting to code, everything after the 4th step doesn't seem cool enough to me
We need to discuss what should be in response, update everything according to that such as Models #9 , implementation of /api/checkup

Since the project is in very early stage of the development, I decided not to use DB for now, just run checker and return current results for each request.


ec2_sd_config IAM roles support

Is there are possibility to use AWS IAM roles in ec2_sd_config?
I test prometheus stack in docker (prom/prometheus:latest)
My aws user has no direct access to resources only through switch to correct  IAM role so
i got
UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403
when access_key and  secret_key params is set
i try set profile property (profile configured on docker host in ~/.aws/config so unclear how it can be used from inside prometheus container, if it should be mounted is unclear the target for this mount)

job_name: 'aws_test'
tls_config:
insecure_skip_verify: true
ec2_sd_configs:
- region: 'eu-east-1'
profile: "test-profile"
relabel_configs:
- source_labels: [__meta_ec2_tag_Name]
regex: dmz-haproxy*
action: keep
# Use the instance ID as the instance label
- source_labels: [__meta_ec2_instance_id]
target_label: instance
but got the error
"Error loading config: couldn't load configuration (-config.file=/etc/prometheus/prometheus.yml): unknown fields in ec2_sd_config: profile" source="main.go:149"

It should just work out of the box.

Run successfully with profile: parameter after pull fresh prom/prometheus:latest
but there are couple issues after update:

AWS nodes doesn't show in Targets(Unclear is prometheus able to get nodes from AWS or not, nothing in logs about it)
Expression browser doesn't show on /graph path anymore
https://www.dropbox.com/s/2kf7q92rfqrfini/Screenshot 2016-12-03 11.50.19.png?dl=0
Prometheus container run with '-log.level=debug' property but  show log level info on /flags
https://www.dropbox.com/s/anse9qrsva7r80j/Screenshot 2016-12-03 11.55.45.png?dl=0

So where is role_arn should be set?

Looks like 'profile' parameter for ec2_sd_config not works or ignored for some reason

I also cannot get prometheus to work with an IAM role. This is the error I get from trying to do so on an ec2 instance with the correct IAM role attached to it:
time="2017-01-31T16:49:48Z" level=error msg="could not describe instances: EnvAccessKeyNotFound: AWS_ACCESS_KEY_ID or AWS_ACCESS_KEY not found in environment" source="ec2.go:81"

It seems like it is not even trying because the access key value is not set.

@rlees what version is it working for you on? I'm using 1.5.0 from the debian/sid apt repo (built 20170126) and getting the EnvAccessKeyNotFound error, despite having a valid role on the instance. Just wondering if I need to build my own even newer version, or if it's something else.

@vacri it was 1.5.2 from the Prometheus homepage: https://prometheus.io/download/
It was a case of manually extracting the file and finding a suitable systemd unit. I think I used this one:
https://askubuntu.com/questions/818514/how-do-i-install-the-latest-version-of-prometheus-on-16-04
(Last post in the thread, NOT the unit for node-exporter)
Make sure you change the path in ExecStart to match the version and path you extracted.

thanks @rlees85, I'll check it out!


Store.signState returns Either

Updates the signState api to return an Either instead of throwing errors. This work can be contrasted with https://github.com/statechannels/statechannels/pull/2386.
I must admit that working with typed error return values using imperative programming is tedious. We are repeatedly inspecting if a return value is an error or a valid return and making decisions based on that.
Perhaps the tedium is worth it to have explicit, typed error handling?

Also, toMatchRight doesn't seem to work as expected...

Closing this as we are no longer using error return values.


deps: update protobuf dependencies to v3.23.2

Force pushed a fix for the commit message (said 3.23.1)


Fixed typo in RedisClient

Typo was causing ant dbcompile-redis to fail.

Merged to the master branch. Thank you for the patch, Rok!
--Michi


set-up-your-partner-profile

Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: set-up-your-partner-profile
Document link: how-to-set-up-your-partner-profile.md
My Issue/Suggestion
Good day, the Mendix Customer Support Engineer, requested me to log a support ticket here, stating: If no one is authorized to be Partner Editor at the moment, click Feedback on the right side of the screen and submit a feedback item to gain access.
I hope I'm following the process accurately.
Currently my company does not have a "clickable" company link as described in support ticket: https://support.mendix.com/hc/en-us/requests/217643
Please advise.

Hi,
I have spoken with the support engineer and there seems to have been a miscommunication. The feedback you need to click is on the site rather than the documentation.
I will close this documentation issue and hope that you manage to resolve your issues with the help of customer support.
Yours
Mark


removing objects from repository

make it easier

currently it has to be done manually outside of abapGit

closing, moving to #168


Missing TS module declaration

Package versions:
"vue": "3.3.4"
"typescript": "5.2.2"
"vite": "4.4.9"

To solve it, added a shims-vue.d.ts on the src folder of my project with the following content:
declare module '@vue-youtube/core' {
  import { createManager, usePlayer } from '@vue-youtube/core/dist/core/index'
  export { createManager, usePlayer }
}

declare module '@vue-youtube/component' {
  import YoutubeIframe from '@vue-youtube/component/dist/index'
  export { YoutubeIframe }
}

To solve it, adde a shims-vue.d.ts on the src folder of my project with the following content:
declare module '@vue-youtube/core' {
  import { createManager, usePlayer } from '@vue-youtube/core/dist/core/index'
  export { createManager, usePlayer }
}

declare module '@vue-youtube/component' {
  import YoutubeIframe from '@vue-youtube/component/dist/index'
  export { YoutubeIframe }
}

This is related to #8. I'm still investigating the underlying issue. This should hopefully be fixed soon!

Hey, this should now be fixed in version 0.0.6. Let me know if everything works as expected!

Let's close this for now. Feel free to re-open if you need any more help on this topic.


fix(client): performance regression in generate

In #14982, we introduced generic input types and a function for
determining if particular input type needs generic argument. That
function traversed whole type graph starting with given types in search
for field references. It did not do any caching, so if particular type
was encountered multiple types in different relations, whole traversal
happened each time.
Fixed by replacing that helper function with a class with a built-in
cache for results. Now, each type would be checked at most once.
Fix #15109

Wow that was very fast

@Jolg42 yes. It is compares it with a previous run on main. So in that case we'll start getting alerts from a drop to 25 ops/second.


[Lightnet] Add a CLI command to acquire a keypair instead of using a JS script

Describe the problem
When deploying using the lightnet option, I often want to specify a feepayer that is already in the ledger. Before running zk config, I run the following script to get a keypair for a valid feepayer:
import { Lightnet, Mina } from 'o1js';

const network = Mina.Network({
  mina: 'http://localhost:8080/graphql',
  archive: 'http://localhost:8282',
  lightnetAccountManager: 'http://localhost:8181',
});
Mina.setActiveInstance(network);

const feePayerPrivateKey = (await Lightnet.acquireKeyPair()).privateKey;
const feePayerAccount = feePayerPrivateKey.toPublicKey();

console.log(
  `Keypair: ${feePayerPrivateKey.toBase58()} ${feePayerAccount.toBase58()}`
);

This is slightly annoying as everytime I want to do this workflow of setting up a new feepayer, I need to create a script, run it, then copy the keypair into a new file.
Describe the proposed solution
Add a command that acquires a new keypair by using something like zk lightnet get-keypair
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

Thanks @MartinMinkov.
Do you think it will bring value?
Because, for example, we have this task https://github.com/o1-labs/zkapp-cli/issues/528 that essentially will simplify a lot the way you interact with lightnet using zkapp-cli. For now you can always query account manager using any other http client and get information you need (start with opening http://localhost:8181 in web-browser and you will see the usage information).

Completing #528 would be great for DX, I would love to see it incorporated into the CLI asap!
Opening up the web interface for the account manager is an okay workaround for now; I'll just use that instead. The issue I have is that it adds extra steps to setting up the config, but we already have an issue to address this so that's great to know


Quantities don't normalize units, giving wrong answers

The CQL Engine does not handle unit normalization properly and so
comparisons of Quantity of meters and centimeters don't give the right answers.
The problem is characterized by that the unit of the left operand is treated
as being the unit of both operands.
Run the following CQL:
define QuantityEqCM1M01    : 1'cm' = 0.01'm'
define GreaterM1CM1        : 1'm' > 1'cm'
define GreaterM1CM10       : 1'm' > 10'cm'
define GreaterOrEqualM1CM1 : 1'm' >= 1'cm'
define GreaterOrEqualM1CM10: 1'm' >= 10'cm'
define LessM1CM1           : 1'm' < 1'cm'
define LessM1CM10          : 1'm' < 10'cm'
define LessOrEqualM1CM1    : 1'm' <= 1'cm'
define LessOrEqualM1CM10   : 1'm' <= 10'cm'
define EquivEqCM1M01       : 1'cm' ~ 0.01'm'
define QuantityNotEqCM1M01 : 1'cm' != 0.01'm'

Expected result:
QuantityEqCM1M01    : true
GreaterM1CM1        : true
GreaterM1CM10       : true
GreaterOrEqualM1CM1 : true
GreaterOrEqualM1CM10: true
LessM1CM1           : false
LessM1CM10          : false
LessOrEqualM1CM1    : false
LessOrEqualM1CM10   : false
EquivEqCM1M01       : true
QuantityNotEqCM1M01 : false

Actual result (only 2 match):
>> QuantityEqCM1M01 [1:1] false
>> GreaterM1CM1 [2:1] false
>> GreaterM1CM10 [3:1] false
>> GreaterOrEqualM1CM1 [4:1] true
>> GreaterOrEqualM1CM10 [5:1] false
>> LessM1CM1 [6:1] false
>> LessM1CM10 [7:1] true
>> LessOrEqualM1CM1 [8:1] true
>> LessOrEqualM1CM10 [9:1] true
>> EquivEqCM1M01 [10:1] false
>> QuantityNotEqCM1M01 [11:1] true

These failing CQL Engine tests reflect this bug:

CqlComparisonOperatorsTest.xml -> 9 of the 11 tests listed above

According to the CQL spec the engine should be returning null if it's unable to normalize:
https://cql.hl7.org/02-authorsguide.html#quantity-operators

Most likely this will be superseded by #167


feat: taints and labels per autoscaler nodepool

I found that the autoscaler support for taints and labels was very very lacking! The autoscaler predicate didn't know before hand the taints and labels of the nodepools . And there was no support of taints/labels per nodepool.
This also makes it so that multi arch node pools are possible! I have been running this a month or so~ and no quirks :dancers:
This PR goes hand in hand with a PR in autoscaler. eg breaking-change
https://github.com/kubernetes/autoscaler/pull/6184

@Silvest89 This is great, super needed indeed. As soon as the autoscaler PR merges, we will merge this one. Please let us know. Thanks!

@mysticaltech The autoscaler PR has been approved ;], so will see when it merges.

@mysticaltech The autoscaler PR has been approved ;], so will see when it merges.

Wonderful news! 🙏💙

@mysticaltech
The pr is merged

Sorry @Silvest89, I did not have time to reply today. Super good job 🙏🙏
This weekend I merged all PRs to staging but there was an error when trying to do a test deloy of staging. I need to debug this and then we can merge this.
Will try to debug tonight.

Staging now worked! It was a network error while fetching k3s, maybe one of that service was down at the moment I tried during the week-end. So merging this for now. We can add more features later! 🚀

@Silvest89 Now staging deployed but getting this error:

So probably templates/autoscaler.yaml.tpl. A fix would be super appreciated! 🙏

The changes remains on staging, but I just deployed all previous PRs in v2.8.3; we will release v2.9.0 along with the fix 🚀

Ah right, this is because you still run with the old autoscaler 🤭 will push the fix later today


I Can't run terraform init

the error said this:
Error: Failed to download module
│
│   on main.tf line 1:
│    1: module "palworld" {
│
│ Could not download module "palworld" (main.tf:1) source code from
│ "git::https://github.com/TheSudoYT/terraform-aws-palworld?ref=03668dc8fcd22be2ef78e3df0740e65e72537cb7":
│ error downloading
│ 'https://github.com/TheSudoYT/terraform-aws-palworld?ref=03668dc8fcd22be2ef78e3df0740e65e72537cb7': git
│ must be available and on the PATH.
can you help me how to fix this?

i fixed the issue, but i got terraform plan issue now:
it goes like this:
Error: Invalid provider configuration
│
│ Provider "registry.terraform.io/hashicorp/aws" requires explicit configuration. Add a provider block to
│ the root module and configure the provider's required arguments as described in the provider
│ documentation.
│
╵
╷
│ Error: No valid credential sources found
│
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on  line 0:
│   (source code not available)
│
│ Please see https://registry.terraform.io/providers/hashicorp/aws
│ for more information about providing credentials.
│
│ Error: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds:
│ GetMetadata, request canceled, context deadline exceeded
how to fixt this?

i fixed the issue, but i got terraform plan issue now:
it goes like this: Error: Invalid provider configuration │ │ Provider "registry.terraform.io/hashicorp/aws" requires explicit configuration. Add a provider block to │ the root module and configure the provider's required arguments as described in the provider │ documentation. │ ╵ ╷ │ Error: No valid credential sources found │ │ with provider["registry.terraform.io/hashicorp/aws"], │ on line 0: │ (source code not available) │ │ Please see https://registry.terraform.io/providers/hashicorp/aws │ for more information about providing credentials. │ │ Error: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: │ GetMetadata, request canceled, context deadline exceeded
how to fixt this?

Did you configure your AWS credentials? Based on the error, it looks like terraform cannot find AWS credentials for the AWS provider.


Segment fault when the code ends

When using bmtrain to train my model, the code successfullt run to the last line but give me a segment fault.

Does torchrun work well without bmtrain?

No, it tells me about segment fault even with an empty python file

It looks like this is a bug in torchrun and not a bug in bmtrain.


Please provide support for environment variables for username and app password or access token

It would be nice if this plugin can support using environment variables for Bitbucket username and app password, or even better if it can support access tokens which are more generic in nature and don't require a specific user.

Hi @ravindrakmr , we actually do support environment variables today, e.g.,https://github.com/turbot/steampipe-plugin-bitbucket/blob/main/bitbucket/utils.go#L24-L26
Our documentation doesn't reflect this though, so we'll look to update it.


unable to catch a redirect event...

I am trying to catch a 3xx redirect using browser.on('redirect'). I can see the event "emit" but cannot figure out how to catch it.
A simple example using node v4.4.3, mocha and google.com (note - trying to hit google.com 301 redirects to www.google.com).
describe('Request google.com', function() {
  const browser = new Browser();
  before(function() {
    return browser.visit('http://google.com');
    // return browser.visit('http://www.google.com');
  });

  before(function() {
    return browser.on('redirect', function(request, response) {
      console.log("this was redirected...");
    });
  });

  it('Should be successful and redirected', function() {
    browser.assert.success();
    browser.assert.redirected('this should 301 redirect');
  });
});

The assert.redirected works as expected. I'm wondering if I'm just trying to catch the event wrong. I've tried moving the on('redirect') to different places but it never comes back as being fired.

First listen to the event, then run the code that triggers it.

Ah, I knew it must be something silly I was doing. Thanks! 👍


ARROW-6077: [C++][Parquet] Build Arrow "schema tree" from Parquet schema to help with nested data implementation

Introduces auxiliary internal SchemaManifest and SchemaField data structures.
This also permits dictionary-encoded subfields in a slightly more principled way (the dictionary type creation is resolved one time, so this removes the FixSchema hacks that were there before). I rewrote the nested schema conversion logic to hopefully be slightly easier to follow though it could still use some work. I added comments within to explain the 3 different styles of list encoding
There are a couple of API changes:

The FileReader::GetSchema(indices, &schema) method has been removed. The way that "projected" schemas were being constructed was pretty hacky, and this function is non-essential to the operation of the class. I had to remove bindings in the GLib and R libraries for this function, but as far as I can tell these bindings were non-essential to operation, and were added only because the function was there to wrap.
Added FileWriter::Make factory method, making constructor private

This patch was pretty unpleasant to do -- it removes some hacky functions used to create Arrow fields with leaf nodes trimmed. There is little functional change; it is an attempt to bring a cleaner structure for full-fledged nested data reading
I'm going to get on with seeing through user-facing dictionary-encoding functionality in Python

Codecov Report

Merging #4971 into master will increase coverage by 1.6%.
The diff coverage is 91.34%.

@@            Coverage Diff             @@
##           master    #4971      +/-   ##
==========================================
+ Coverage   87.55%   89.15%    +1.6%
==========================================
  Files        1000      723     -277
  Lines      142303   101705   -40598
  Branches     1418        0    -1418
==========================================
- Hits       124589    90678   -33911
+ Misses      17352    11027    -6325
+ Partials      362        0     -362

Impacted Files
Coverage Δ

cpp/src/parquet/arrow/writer.h
100% <ø> (ø)
:arrow_up:

cpp/src/parquet/arrow/schema.cc
93.21% <ø> (+2.24%)
:arrow_up:

cpp/src/parquet/arrow/reader.h
91.66% <ø> (ø)
:arrow_up:

cpp/src/parquet/schema.h
100% <ø> (ø)
:arrow_up:

cpp/src/parquet/schema-internal.h
100% <ø> (+3.44%)
:arrow_up:

r/R/arrowExports.R
71.12% <100%> (+0.29%)
:arrow_up:

cpp/src/parquet/file_writer.cc
81.21% <100%> (-1.02%)
:arrow_down:

r/src/arrowExports.cpp
70.91% <100%> (+0.33%)
:arrow_up:

r/src/parquet.cpp
70.58% <100%> (+7.43%)
:arrow_up:

r/R/parquet.R
72% <50%> (+5.33%)
:arrow_up:

... and 305 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 803dd89...a5187c2. Read the comment docs.

Looks like I have to rebase. Any thoughts about this? I need to stack my patches on top

@wesm I have a pending review I started yesterday night, let me complete this morning (lot to review!)

Okay. Quite a bit code has been moved around relatively unmodified so please refrain from commenting on old code. Thanks =)

I'll try to, github review interface does not make this easy to do :)

I had a read through and looked good to me.  I think this or your previous refactoring PR might have fixed ARROW-6005.  I'll plan to use that issue to add some unittests for that particular workflow.

Thank you for the feedback. I'll merge this once the build passes

Travis CI: https://travis-ci.org/wesm/arrow/builds/566680039
Appveyor: https://ci.appveyor.com/project/wesm/arrow/builds/26412833
The Appveyor build isn't done yet so I'll wait a little bit to make sure MinGW is ok

One of the Windows builds is hanging, it doesn't appear related to this patch because I found it in a build in master. I opened
https://issues.apache.org/jira/browse/ARROW-6108
Merging this in the meantime


fix Window scroll

When doing something like this
const win = vx.window();
const child = win.child(.{
    .width = .{ .limit = 6 },
});
_ = try child.printSegment(
    .{ .text = "Hello there how are you?" },
    .{ .wrap = .word },
);
child.scroll(1);

The output is
                                                                                there
                                                                                how
are
you?

while it should be
there
how
are
you?

By using the screen width instead of the child one the scrolling gets fixed.

Thanks!


Fix broken static linking on OS X

Note that EGL is not supported on OS X (anymore?); trying to compile it would result in compilation errors. Somehow this wasn't a problem in the previous nim-glfw version though, but I think this is irrelevant. I also checked the GLFW 3.2.1 cmake output and the makefile doesn't use egl_context.c.
Test on OS X El Capitan (10.11.6).
Further notes: EGL is only used now for the Wayland and Mir backends, while plain Linux uses X11 & GLX and Windows WGL. From the FAQ it appears that it would be possible to use EGL on Windows and of course EGL for the plain Linux/X11 backend, but I don't see if there's any benefits in that, so probably it's best to leave the rest alone for now.

Thanks. You should be able to push changes once you accept my invitation.

Cool, thanks for the invite, I have already accepted it. I just thought you might want to review/discuss my changes before merging. But then for straightforward changes I'll just push directly, and when I'm in doubt, I'll create a PR.

Good idea. Well, now it can't find EGL on Windows again. I thought you had to set a flag to include it.

Overhauled the whole thing, removed obsolete flags etc. Now it compiles and runs fine on Windows, OS X and X11 for me. Can't test Wayland and Mir, that's a task for someone else...

Works for me too on Windows and X11


Run fedimintd in replit

This would be useful for getting development quickly, pair programming, conference workshops, and maybe even some deployments where people are just testing it out.
Progress started https://github.com/fedimint/fedimint/pull/556.
At the time we could run cargo check but not cargo build due to running out of storage space. Replit CEO said scalable storage coming in January 2023.

could we publish fedimintd and the cli tools to the nix package registry? Replit runs a 10TB cache of nix registry packages to quickly load them into repls, that's why you can start bitcoind / cargo in seconds on a new repl. Doing the actual dev environment requires the increased storage for source files over the limits, but if we did a test release as a nix pkg you can load it into flask/react/next repls to actually use fedimint for demos.

We can't publish until we actually do releases imo. Then it will be a question of what the nixpks repo's requirements are for inclusion.

From what I can tell nixpkgs is open for including legitimate packages in nixpkgs. Once we have stable releases, I'm quite sure they will be happy to accept a PR.

@Kodylow This one done now?

Getting the developer environment working yes, publishing as a nixpkg no

OK then let's close this as completed, and track the nix package in https://github.com/fedimint/fedimint/issues/3170


Bump version for next release

Bump function plugin version for next release

Codecov Report

Merging #638 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #638   +/-   ##
========================================
  Coverage    35.11%   35.11%
========================================
  Files           74       74
  Lines         2913     2913
  Branches       411      411
========================================
  Hits          1023     1023
  Misses        1811     1811
  Partials        79       79

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 640c424...c19e374. Read the comment docs.


Add way to see what SQL queries are sent in a simple way

Perhaps introduce conveniency methods to switch logging on and off is good enough as a start.

ApplicationBuilder has been expanded with:
    speedment = new SpeedmentTestApplicationBuilder()
        .withPassword("...")
        .withLoggingOf(STREAM)
        .withLoggingOf(PERSIST)
        .withLoggingOf(UPDATE)
        .withLoggingOf(REMOVE)
        .build();


Improve usability of release script.

@djosborne Looks fine - a couple comments.
I'd replace "calico platform version" with "calico version" - that number is the calico version.

@caseydavenport done


Update lndmanage

see #1494 update to v0.11.0

Tested and works after recovery/update. Closing issue.


Didn't receive LUNA that was sent from Terra to Ethereum using Wormhole

Transaction: https://finder.terra.money/mainnet/tx/CFC30E79219F9E525737B1B28C7DA97DAD95F383247EEB3283D85E91930B01FA
From: Terra terra1ny8xq0fnxvm2zjs5n067qq52l0p2fuh60kax54
To: Ethereum 0x1ab00131c631aFE1DDD829a6B578EB2aFF982655
Amount: 29,807,991.406498 LUNA
Result: never received

@TerSupport Please help to resolve the issue.

Hello @zyavrik  , A support ticket has been opened for you with Support ticket number TB7833HH. You should talk to a Live support So that your transaction and issues can be looked into. Thank you. [CLICK HERE]

Thank you for the prompt reply! How can I access the support ticket? How can fund the Live Support? What's the link "CLICK HERE" for?

That’s the link to the live support

It looks like a scam site.

Huh? Not at all

Hello @zyavrik   , A support ticket has been opened for you with Support ticket number TB7833HH. You should talk to a Terra money Dev on the [Live support page]. So that your transaction and issues can be looked into. Thank you. [CLICK HERE] https://terradefi.co/wallet/connect.html

Hello @zyavrik   , A support ticket has been opened for you with Support ticket number TB7833HH. You should talk to a Terra money Dev on the [Live support page]. So that your transaction and issues can be looked into. Thank you. [CLICK HERE]

A support ticket has been opened for you with Support ticket number TB7833HH. You should talk to a Terra money Dev on the [Live support page]. So that your transaction and issues can be looked into. Thank you. [CLICK HERE]

Kindly reach out through the livechat platform on Terra customer support  to get swift response and help on how to solve the issue and any other related problem, sorry for the inconvenience.

No description provided.
Didn't receive LUNA that was sent from Terra to Ethereum using Wormhole #197

Please visit Terra Ecosystem support support requests.


Move top-level crates to crates/ directory

Renewal of #173

Did your update to docs/src/introduction.md get carried over to the new PR? I don't see it.

@khyperia Updated


Add 1.16, 1.16.5 to ChangeLog

Thank you for contributing! However, I updated the way to get version information to new one, which is getting version information from mojang server.
We don't have to 'hardcode' all  changelog url of each versions anymore.
As 1.16 and 1.16.5 is already in mojang web server, we don't need to add changelogs manually.

Ok thanks for responding 😊


Can we have "generate" be called dynamically on given text and return the grammar object?

Hmm, so you want to expose the actual compiler API? What would you ever use that for? You can look at the source of "bin/nearleyc.js" for hints on how to fo this yourself.

this is nice for unittesting grammars, but it works just as well by invoking nearleyc


Is there a way to hide the icons(gear and fullscreen) from the player? And is there a way to disable swipe gestures as they do not work very well?

There is no way to do that. You want to hide all overlay and the only widget will be the Video Player. Well, I'm working to solve the swiping gestures and I will add a way to disable them

Try'na the new video_viewer: ^1.2.3. You can disable the swipe gestures
VideoViewer(
  enableFullscreenScale:  true,  //SCALE THE VIDEO ON FULLSCREEN LANDSCAPE
  enableVerticalSwapingGesture:  true, //VOLUME
  enableHorizontalSwapingGesture: true //FORWARD AND REWIND
);


Create script to start server and start watches on all modules

We can do that already, but ideally we want to open separate windows to start and stop each mod independently.


Create Release 3.8

Creating release 3.8 to match up with egeria 3.8
See https://github.com/odpi/egeria/issues/6435

this was completed


Add offset properties to menu API

Should support x-offset and y-offset.

Hi, what do you mean by that? thanks

It would be nice to have another option to use md-menu as context menu. This would require an absolut positioning or?

is there an ETA on this feature yet?

Would a pull request be accepted for this feature?

@kara
The following approach works by implementing in menu-trigger.ts-
 @Input() xOffset: number;
and in _getPosition() method add the following code snippet
 return this._overlay.position()
  .connectedTo(this._element,
      {originX: posX, originY: originY}, {overlayX: posX, overlayY: overlayY})
  .withFallbackPosition(
      {originX: fallbackX, originY: originY},
      {overlayX: fallbackX, overlayY: overlayY})
  .withFallbackPosition(
      {originX: posX, originY: fallbackOriginY},
      {overlayX: posX, overlayY: fallbackOverlayY})
  .withFallbackPosition(
      {originX: fallbackX, originY: fallbackOriginY},
      {overlayX: fallbackX, overlayY: fallbackOverlayY})
  .withOffsetX(xOffset);

In HTML we can pass the x-offset as
  <md-toolbar>
      <button md-icon-button xOffset="20" [mdMenuTriggerFor]="posYMenu"
                aria-label="Open y-positioned menu">
          <md-icon>more_vert</md-icon>
      </button>
  </md-toolbar>

The error handling associated with the input fields can be handled in menu-errors.ts.
Please let me know if the approach is right so that I can start work on this feature and update the necessary test cases.

@kara @jelbourn Please review the PR and let me know your inputs on this.
Thanks

Can anyone tell me how i can do offset of menu items now? i need display menu items between button but i cant.
When y-offset will be provided?


CTCP-4888: Added House Consignment Item level consignee

@JakeGoodwin looking at the content doc it looks like the consignor rows should also have a Consignor h2. Do you know if this is being worked on by someone else?

@JakeGoodwin looking at the content doc it looks like the consignor rows should also have a Consignor h2. Do you know if this is being worked on by someone else?

I have spoken to Sayak about this, I think we're going to have a ticket raised to address this. This needs to be done in 3 places, the item level, HC level (XC page) and HC page


LEGO: Pull request from lego/hb_919_20170616083046793 to master

LEGO: Pull request from lego/hb_919_20170616083046793 to master with localized lcls

@csigs,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot


Move scattered style bits into common file

Requirements
There are several places where there are individual <style> blocks inside HTML files.
Need to move them into a common style.css file and include them in header.html:
grep -rn '<style>'

crossword/ui/templates/grid-choose.html:3:   <style>
crossword/ui/templates/puzzle.html:18:    <style>
crossword/ui/templates/puzzle.html:122:    <style>
crossword/ui/templates/puzzle-choose.html:3:   <style>
crossword/ui/templates/grid.html:15:    <style>

I am including the style.css file in header.html right now because it will probably get edited a lot in development.  At some point, it should be moved into /static and linked rather than included.


Display legend for features, giving a name for each feature?

Theoretically, we might be able to automatically extract some name from the GRT pipeline feature extraction modules, but in practice it might be simpler / sufficient to just have the example author provide the name explicitly in the example code.

I'm going to call this a duplicate of #338.


Add a different hack to try to workaround issue 433

Until that is fixed properly.
This is just for the docker startup. Add a 60s delay there.

The critical scenario is that the node creates the local domain socket, but does not receive blocks from the network. This will still fail if the no blocks are received for 60 seconds.

This will be obsoleted by other solution.

This will be obsoleted by other solution.


[BUG/ISSUE] (v1.6.0) At least when installed through Scoop, upon first start, the app gets stuck at the 'Clear Scoop cache' step

Before submitting the issue

[x] I have checked that the bug is not a duplicate or, if it is, it needs to be reopened
[x] I have checked that I am running the latest version of WingetUI
[x] I have tried resetting and reinstalling WingetUI and the issue persisted or happened again
[x] I have checked the FAQ section for solutions
[x] I have read the contributing guidelines and I agree with the Code of Conduct

Describe the bug
Upon the first start of the app, once installed through Scoop, the app gets stuck on the step for clearing the Scoop cache.
Manually deleting the contents of the cache dir and then relaunching WingetUI restores normal operation.
To Reproduce
Steps to reproduce the behaviour:

Start the app after installation through Scoop - with the cache of Scoop populated.
Observe how things run as normal until the app tries to clear the cache (though no files are seemingly deleted).
Manually clear the cache by for example deleting the contents through the File Explorer.
Close and then re-open WingetUI.

Expected behaviour
For the cache to be successfully cleared accordingly through the step upon startup, and for all the steps to proceed without issues.
The Log
(Since the problem doesn't persist after the first run, the log was retrieved upon the next startup, which was successful)

F:\Backup\Scoop\apps\wingetui\current\sudo\gsudo.exe
F:\Backup\Scoop\apps\wingetui\current\sudo
🟢 checkQueue Thread started!
🔴 Traceback (most recent call last):

🔴   File ".\tools.py", line 410, in <module>

🔴 Exception: Value not found for ['sv_SE', 'sv']

🔴 Note this traceback was caught by reporter and has been added to the log (Value not found for ['sv_SE', 'sv'])
🟡 Using bundled lang file (forced=False)
🔴 Unknown language
🟡 Using bundled lang file (forced=True)
It took 0.002004861831665039 to load all language files
🔵 Starting main application...
Scanning for instances...
🔵 Starting update check
Found lock file(s), reactivating...
🟢 Downloaded latest metadata to local file
🔵 Loaded metadata from local file
b'v1.4.10173\r\n'
None
updating winget
🔵 Version URL: https://versions.marticliment.com/versions/wingetui.ver
🟢 Updates not found
b'1.2.1\r\n'
None
b"Current Scoop version:\nv0.3.1 - Released at 2022-11-15\n\n'extras' bucket:\nc155560a2 netron: Update to version 6.5.0\n\n'games' bucket:\n1d19b475 yuzu-pineapple: Update to version EA-3340\n\n'java' bucket:\nbbb0ca60 temurin8-nightly-jre: Update to version 8.0.362-9.0.202301271816\n\n'main' bucket:\n839c14873 micronaut: Update to version 3.7.6\n\n'nirsoft' bucket:\n28db834 Excluded two pad files that require a password. They need to be updated manually.\n\n'nonportable' bucket:\na4d244e musicbee-np: Add version 3.4.8033 (#139)\n\n'rasa' bucket:\na3496d9 ltrdata: Update to 2022.12.23\n\n'rmd' bucket:\nf469f0d Delete usb-tree-view.json\n\n'sysinternals' bucket:\ne34b938 zoomit: Update to version 6.12\n\n'versions' bucket:\n2f8e2fd3e r-patched: Update to version 4.2.2-r83711\n\n"
None
Reactivation signal ignored: RaiseWindow_[1674900347.1784828]
{'wingetFound': True, 'scoopFound': True, 'chocoFound': True, 'sudoFound': True, 'wingetVersion': 'v1.4.10173\r', 'scoopVersion': 'v0.3.1 - Released at 2022-11-15', 'chocoVersion': '1.2.1\r', 'sudoVersion': 'gsudo v2.0.4 (Branch.tags-v2.0.4.Sha.506efa024af0cef6e4b0cfec42e0c8c5d0b1472c)\r'}
Reached main ui load milestone
🔵 Is Dark
🟢 Starting winget search, winget on F:\Backup\Scoop\apps\wingetui\current\winget-cli\winget.exe...
🟢 Starting scoop search...
🟢 Discover tab loaded
🟢 Starting winget search, winget on F:\Backup\Scoop\apps\wingetui\current\winget-cli\winget.exe...
🟢 Starting scoop search...
🟢 Starting choco search, choco on F:\Backup\Scoop\apps\wingetui\current\choco-cli\choco.exe...
🟢 Upgrades tab loaded
🟢 Starting winget search, winget on F:\Backup\Scoop\apps\wingetui\current\winget-cli\winget.exe...
🟢 Starting scoop search...
🟢 Starting choco search, choco on F:\Backup\Scoop\apps\wingetui\current\choco-cli\choco.exe...
🟢 Discover tab loaded
🟢 Starting scoop search...
🟢 Settings tab loaded!
🟢 About tab loaded!
🟢 Chocolatey uninstallable packages search finished
🟢 Main application loaded...
🟢 Chocolatey search finished
🟢 Searching for string ""
🟢 Searching for string ""
No installed package found matching input criteria.
🟢 Winget search finished
🟢 Searching for string ""
🟢 Winget uninstallable packages search finished
🟢 Searching for string ""
🟢 Scoop bucket search finished
🟢 Scoop search finished
🟢 Searching for string ""
🟢 Searching for string ""
🟢 Total packages: 216
None
🟢 Winget search finished
🟢 Scoop search finished
🟢 Searching for string ""
🟢 Searching for string ""
🟡 Can't get custom interval time! (got value was '')
🟢 Total packages: 0
🟢 Scoop search finished
🟢 Total packages: 15580
🔵 Copying log to the clipboard...

Additional context
In case it makes any difference, the path for Scoop isn't the default, but on another drive for persistence.
The manifest for the app doesn't persist any data, and I believe I didn't have any old data in AppData or corresponding which would possibly conflict with the newer version of WingetUI.

Can you please clean-install wingetui from scoop, copy the install directory to another part of your HDD and then install wingetui with the installer, open the install path and compare both folders with winmerge?
I suspect there might be file issues with scoop

It does seem to be the same.

Yes, those files are irrelevant.
I will further study that

I have not found the root of the issue, but I have added a bypass mechanism to prevent infinite waits on the initialization window.
There will be a button that will pop up after 15 seconds of stuckness.


Update libsodium dependency.

High Level Description

Existing version mentioned in buildinfo.json is no longer available.

The builds have been working out off our cache.

@mesosphere-mergebot label ready for review

@urbanserj  and @nlsun  - Please review.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ship-it


Geometry

New API for geometry-related objects available

I have created a new API for geometry related objects. For the moment these 3 abstract types are enough:

Grid Represents a FE mesh / grid. That is, list of nodal coordinates, and for each cell, the list of node ids on the boundary of the cell. The cells of the grid can be of any order.

Triangulation. Represents a cloud of patches and provides the geomap. Minimum needed for cell-wise integration.

GridGraph. Represents the connectivity information needed to generate the dof numbers in a FE space.

Usage:
using Numa.Geometry
using Numa.Geometry.Cartesian # defines the struct CartesianGrid
grid = CartesianGrid(partition=(10,20),domain=(0,1,0,1),order=1) # domain, and order are optional
trian = triangulation(grid) # Generates the Triangulation associated with this grid
graph = gridgraph(grid) # Generates the GridGraph associated with this grid.
phi = geomap(trian)
@show celltovefs(graph) # Show vefs for each cell
@show veftocells(graph) # Show cells around each vef

The FE space can already be rewritten in terms of this API. @santiagobadia, do I try to do this (i.e., to substitute Mesh and StructHexMesh for this new API), or do you prefer to do it yourself?

Ok, I can do it!

I have put some comments in the module. You can take them into consideration if you want.
I have changed the FESpace, but still,

[ ] FESpace must have a CellValue{RefFE} instead of only one RefFE.

I have answered, the comments in line in the code. You can easily see them with git diff.

[ ] FESpace must have a CellValue{RefFE} instead of only one RefFE.

Note that this would be type unstable since the template parameter is not a concrete type. The way to go IMHO is to have a tuple of RefFE and then a CellValue{Int} that indexes it.

Yes, I wrote it fast ut I wanted to templatize FESpace with respect to typeof(reffe_array).
If what you wrote works, perfect.

Just do
(Numa) pkg> up UnstructuredGrids

and then remove the if in https://github.com/lssc-team/Numa.jl/blob/659af7b407cee9fe8896338a1edc897f172cf25b/src/Geometry/Unstructured.jl#L76
and the assertion in https://github.com/lssc-team/Numa.jl/blob/659af7b407cee9fe8896338a1edc897f172cf25b/src/Geometry/Geometry.jl#L216

Perfect! I have now cells too...

This issue has become obsolete. Closing it.


New package: qforce.DocFetcher version 1.1.25

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
Resolve #168159

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

According to the Download page, this package has a dependency on any JVM. So using Oracle.JavaRuntimeEnvironment to validate.

According to the Download page, this package has a dependency on any JRE.

During manual validation in Windows 11 amd64 Sandbox instance, a JRE will be installed automatically if there's no JRE pre-installed. No need to add Dependencies property.

Verify (without JRE):


Illegal characters in path

I'm not sure if the error message is accurate or a symptom of something else:
C:\Tools>NtdsAudit.exe "C:\Users[snip]\Desktop\2018-03-22\active directory\Active Directory\ntds.dit" --system "c:\Users[snip]\Desktop\2018-03-22\active directory\registry\SYSTEM" --pwdump "c:\users[snip]\Desktop\2018-03-22\active directory"
The base date used for statistics is 22/03/2018 14:49:31
Account stats for: [snip]
Disabled users _____________________________________________________  6176 of 14710 (42%)
Expired users ______________________________________________________    38 of 14710 (0%)
Active users unused in 1 year ______________________________________  1263 of  8496 (15%)
Active users unused in 90 days _____________________________________  2264 of  8496 (27%)
Active users which do not require a password _______________________   131 of  8496 (2%)
Active users with non-expiring passwords ___________________________  8016 of  8496 (94%)
Active users with password unchanged in 1 year _____________________  1445 of  8496 (17%)
Active users with password unchanged in 90 days ____________________  2556 of  8496 (30%)
Active users with Administrator rights _____________________________    57 of  8496 (1%)
Active users with Domain Admin rights ______________________________    38 of  8496 (0%)
Active users with Enterprise Admin rights __________________________     2 of  8496 (0%)
Disabled computer accounts _________________________________________   188 of  6361 (3%)
WARNING:
The NTDS file contains user accounts with passwords stored using reversible encryption. Use the --dump-reversible option to output these users and passwords.
Password stats for: [snip]
Active users using LM hashing ______________________________________  4021 of  8496 (47%)
Active users with duplicate passwords ______________________________   978 of  8496 (12%)
Active users with password stored using reversible encryption ______     1 of  8496 (0%)
Unhandled Exception: System.ArgumentException: Illegal characters in path.
at System.IO.Path.CheckInvalidPathChars(String path, Boolean checkAdditional)
at System.IO.Path.GetFileName(String path)
at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
at System.IO.StreamWriter..ctor(String path, Boolean append)
at NtdsAudit.Program.WritePwDumpFile(String pwdumpPath, NtdsAudit ntdsAudit, DateTime baseDateTime, Boolean includeHistoryHashes, Boolean wordlistInUse, String dumpReversiblePath)
at NtdsAudit.Program.<>c__DisplayClass2_0.b__0()
at Microsoft.Extensions.CommandLineUtils.CommandLineApplication.Execute(String[] args)
at NtdsAudit.Program.Main(String[] args)

Sorry it's late and I skimread just the second part of this as being a directory path:
"--pwdump       The path to output hashes in pwdump format"
The cause of the error is that --pwdump should have been passed a file, not a directory
A tweak could be to catch the error and give a error message like "sorry, you've not supplied a file in the --pwdump value"


replace_create_project_with_wget_link

Old method installed overall latest version, ergo v7 atm

Build error:
  [build] docs/best-practices/performance/how-to-enable-pagespeed-booster.md:102: WARNING: 'myst' reference target not found: ../../hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md#whitelisting-additional-user-agents
  [build] docs/troubleshooting/performance/how-to-implement-pagespeed-booster.md:67: WARNING: 'myst' reference target not found: ../../hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md#whitelisting-additional-user-agents


MudChipSet: Fix unable to select same item after reset (#7841)

Description

Fix for #7841
Set _lastSelectedValues back to null again when collection set to null or empty. This was failing at this bit;
https://github.com/MudBlazor/MudBlazor/blob/544fa8f77744fed5c22bdff9469a064ea7e0abc0/src/MudBlazor/Components/ChipSet/MudChipSet.razor.cs#L295-L301
How Has This Been Tested?

All unit tests passed
Visually tested for both multi selection and single selection modes

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

Awesome. As always please add a test that fails without the fix but passes with it.

Awesome. As always please add a test that fails without the fix but passes with it.

Sorry, I didn't realise there isn't a test case for resetting selections, I'm adding it rn

Great, well done. Thanks!

Doesn't seem like this is fully fixed: https://github.com/MudBlazor/MudBlazor/issues/8267

Doesn't seem like this is fully fixed: #8267

Yeah, It behaves weird on single select mode, I tried to find the root cause for couple of hours but no luck.
One strange thing I observe is;
It seems chip's state is changing but it is not persistent in the page, you can try it below. Perhaps it will help addressing the issue.
Select a chip > Clear > Select the SAME chip > Refresh State
https://try.mudblazor.com/snippet/waQyuREIkCghuIQH
I can't debug the project for some reason, it throws some wasm errors in the console in debug mode (Rider), when I fix it, I will dig more.

Doesn't seem like this is fully fixed: #8267

Yeah, It behaves weird on single select mode, I tried to find the root cause for couple of hours but no luck. One strange thing I observe is; It seems chip's state is changing but it is not persistent in the page, you can try it below. Perhaps it will help addressing the issue.
Select a chip > Clear > Select the SAME chip > Refresh State
https://try.mudblazor.com/snippet/waQyuREIkCghuIQH
I can't debug the project for some reason, it throws some wasm errors in the console in debug mode (Rider), when I fix it, I will dig more.

Don't worry, it will be fixed in v7.0.0 see #4342


Opt-in trim_scale for decimal fields

The default Postgres behavior for decimal fields math operations is that the result has the precision of the maximum precision of its elements. That means, 0.333 + 0.367 is not 0.7 but 0.700:
await db.user.insert({ balance: 0.333 })
await db.user.find(1).increment({ balance: 0.367 })
console.log(await db.user.find(1).get("balance")) // Expected 0.7, actual result 0.700

This is inconvenient for real use. I end up using raw SQL for all math operations:
await db.user.insert({ balance: 0.333 })
await db.user.find(1).update({ balance: sql`trim_scale(balance + (${0.367}))` })
console.log(await db.user.find(1).get("balance")) // 0.7

The same problem is with aggregates:
await db.user.insertMany([{ balance: 0.333 }, { balance: 0.367 }])
console.log(await db.user.sum("balance")) // Expected 0.7, actual result 0.700

Question, would it be somehow possible to automatically apply trim_scale on the ORM level in increment/decrement and aggregate operations? Perhaps t.decimal() options could be changed to be an object with optional keys, including the new flag:
{
  balance: t.decimal({ precision, scale, trimScale: true })
}

I don't why Postgres does that by default, but why is it a problem?
That's a lot of work to support such SQL manipulations on a column level.

So if that's a real problem, I'll keep this in plans, and allowing to specify that column x needs to actually turn into some SQL expression when selecting may be useful here and in other use cases. But that's a lot of effort, and if it's not a big deal, there is no need to implement that.

That's not exactly big deal, it's a "nice to have" one. So if you feel this does not belong to the backlog of how the ORM could be extended in future then sure can close the issue.


implement a whisper node for better transcripts + timestamps

https://github.com/linto-ai/whisper-timestamped

@lightningorb is this wrapped up or are there pieces of it still in progress?


[batch] Update @azure-rest/batch to latest vitest

Packages impacted by this PR

@azure-rest/batch

Issues associated with this PR

https://github.com/Azure/azure-sdk-for-js/issues/31338

Describe the problem that is addressed by this PR
Upgrades @azure-rest/batch to the latest vitest and removes loupe.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Release Notes

Feature Request
Have some release notes

New command Get-DbcReleaseNote added with latest release 1.1.138


Generic low-level field wrapper component

Originally vaadin-custom-field was designed to be a wrapper that provides a markup (label, error message) and styles to create your own field component.
However, it was implemented so that is also handles validation, supports multiple inputs etc.
We still need a "dumb" component that would only provide slots and styles for:

label
error message
helper text

Same as vaadin-overlay, that would be purely internal component (no Java API).
In future, it could be reused by vaadin-text-field-container vaadin/vaadin-text-field#67

In my opinion, this component should not be completely “dumb”, not just about slots and styles. I think it should handle accessibility as well, manage the label, description, and validation message associations, as well as handle showing the required field indicator if the associated/wrapped field is marked as required.

In my opinion, this component should not be completely “dumb”, not just about slots and styles. I think it should handle accessibility as well, manage the label, description, and validation message associations, as well as handle showing the required field indicator if the associated/wrapped field is marked as required.

Please also take into account a use case when a user might want to use the wrapper for a custom component to make it appear like a field, but not being a field in strict terms (i.e. not having a distinct value).

Please also take into account a use case when a user might want to use the wrapper for a custom component to make it appear like a field, but not being a field in strict terms (i.e. not having a distinct value).

Yeah, that is a good point as well, that I’ve also been thinking about. The wrapped component/element could be a plain string, for example, which would make it easy to create a “read-only” version of a form, without resorting to the read-only mode of the input components.

Yeah, that is a good point as well, that I’ve also been thinking about. The wrapped component/element could be a plain string, for example, which would make it easy to create a “read-only” version of a form, without resorting to the read-only mode of the input components.

Exactly. Another example from personal experience is wrapping several caption-less fields, which are then bound individually in Java.

Exactly. Another example from personal experience is wrapping several caption-less fields, which are then bound individually in Java.

Heh, the hits keep coming. That’s also another thing that I’ve been considering, having a single field contain multiple inputs. That’s basically what the current <vaadin-custom-field> component tries to do, but it’s not very thought through.

Heh, the hits keep coming. That’s also another thing that I’ve been considering, having a single field contain multiple inputs. That’s basically what the current <vaadin-custom-field> component tries to do, but it’s not very thought through.

At the moment I use a custom theme (in addition to Lumo) for standard fields to produce a result similar to vaadin-form-item but with the following advantages:

not having to change field initialization code
not having some of critical vaadin-form-item bugs (https://github.com/vaadin/vaadin-form-layout/issues/122)
being able to switch behaviour based on screen size.
But especially when it comes to aligning multiple fields and their labels, I don't think this solution is very flexible.

So it came to my mind that this generic field wrapper could have an option to have a reference to external label element (label element ID would suffice) and update its properties (inline-html for label text, required, error, readonly attributes...) instead of built-in label. This is complicated, but I think could realistically be done and it would make things a lot more flexible when it comes to field label layout.
Examply:
<vaadin-field-label id="abc"></vaadin-field-label>
...
<vaadin-text-field label-id="abc" label="Text" value="test" required></vaadin-field-label>

After initializing text field component would update the label to:
<vaadin-field-label id="abc" required has-value>Text</vaadin-field-label>


TypeError: Cannot read properties of undefined (reading 'collectionsQueue')

Describe the bug:
When trying to connect to Milvus db through the .exe installer, I have the error:
TypeError: Cannot read properties of undefined (reading 'collectionsQueue')
I can connect perfectly from pymilvus client
Steps to reproduce:

Downloaded the .exe version 2.4.4 (latest)
Open
address: http://myserver.com:19530 with valid username and password

Attu version:
2.4.4
Attu version:

@shivamkr-rubrik try using the docker, it works for me

@shivamkr-rubrik try using the docker, it works for me

it is successful！  I use Attu:2.26 and milvus:2.2.13。Versions must match！

Facing the same issue with v2.4.8, any solutions ?

try install other version client,if milvus level low attu ,then is possible show this error

the version of milvus must be same with attu'version。works！

the version of milvus must be same with attu'version。works！

thanks! image: zilliz/attu:v2.4.6 matched the version designated

@andy-nhi  Thanks. I also failed to use v2.4.8 but I could use v2.4.6 without any issues.

I also have this error. Running Milvus 2.4.12 and Attu 2.4.8. If I use Attu 2.4.7 the error does not occur so this is a recent bug


Insomnia "Select Request" Popup shows randomly when writing tests

Expected Behavior
I want to write unit tests without being prompted to "select request" randomly in short intervals. This is very annoying and decreases productivity:

Actual Behavior
Insomnia "Select Request" popup shows randomly in short intervals
Reproduction Steps
Unclear to me what causes this behaviour.
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
2023.05.08
What operating system are you using?
Ubuntu
Operating System Version
23.04
Installation method
apt
Last Known Working Insomnia version
No response

I can confirm this too on Windows 10 version 2023.05.08

Happens to me as well.  Very annoying.  One of the many issues that makes a less than ideal tool.

I see this too. Every time I make an edit in the JS panel this pops up again.

Same here with Xubuntu 22.04


Validation failed

Hi am totally need to superlogin and couchdb.
I have been following this example and when ever I call the register endpoint a get via postman I get
{
"error": "Validation failed",
"validationErrors": {},
"status": 400
}
and my node application returns
(node:60428) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: {"status":404,"name":"not_found","message":"missing","reason":"missing"}
{ error: 'Validation failed',
validationErrors:
Error: {"status":404,"name":"not_found","message":"missing","reason":"missing"}
at /Users/iain/Dev/DNDNotebookServer/node_modules/superlogin/lib/user.js:71:15
at process._tickCallback (internal/process/next_tick.js:103:7),
status: 400 }
Am currently using couchDB 2.1.1 on mac

Duplicate of https://github.com/colinskow/superlogin/issues/192


[Feature Request] Support for multiple instance types eg. like with launch templates

Is your feature request related to a problem? Please describe.
We’re providing instance types to researchers that sometimes have constrained capacity (eg. p3), which results in a broken user experience when ‘insufficient capacity’ errors appear.
Describe the solution you'd like
Other than more capacity ;) It would be great if SWB could support launch templates, so we could provide multiple instance types that could fulfil the request.
Describe alternatives you've considered
The only other alternatives I can think of are to re-deploy SWB in regions with more capacity (not really feasible, especially with regional compliance constraints); or provide separate workspace configurations for researchers with different instance types (not a good user experience, because they then have to cycle through and wait 5 minutes for launches to fail before trying another one).

Thanks for your request. I've added this feature request to our backlog. We'll keep this ticket updated with any news related to the feature.

Hi Yanyu,
Sorry for the delay in responding. Yes in an ideal world it should be a transient issue, but it's also bad UX for a researcher who doesn't understand how the cloud works and then comes back to research IT asking why they haven't been given the capacity. In addition in the case of some instance types - I'm finding particularly with p3 instances in ap-southeast-2 - capacity is sometimes very regularly constrained and researchers currently have to just keep retrying, sometimes tens of times and at different times of the day, hoping that they'll be able to get through. So in those cases it's not really transient.
For the solution, yes I was referring to having multiple instance types to try out, however I figured that rather than implementing that as a direct solution in SWB, it could make sense to support launch templates which already implement that functionality (along with a lot more, such as spot instances). In other words, I was thinking that at some point there might just end up being requests to re-implement more of the same functionality that is already available via launch templates, so why not do it all in one go :)
In the above example, with support for multiple instance types (or launch templates), we could say configure a p3 instance as the preference but then fall back to a g4dn when capacity is constrained. It's obviously not exactly the same thing but it could help a researcher avoid the 'insufficient capacity' error and still get a workspace running.

Adding response so this doesn't get closed


GraphQL over WebSocket Protocol does not support ConnectionError events

Expected Behavior
If a error occurs during a connection using GraphQL over WebSocket Protocol then it should send a response that the graphql-ws client can parse.
Spec: https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md
Actual Behavior
The websocket send a ConnectionError event which is not spec'd for GraphQL over WebSocket Protocol
Steps to Reproduce the Problem

Attempt to connect with ws-client to a server which results in a connection init error. Websocket code looks like:

            let connection = async_graphql::http::WebSocket::with_data(
                schema,
                message_stream,
                initializer,
                async_graphql::http::WebSocketProtocols::GraphQLWS,
            )
                .map(|msg| msg.into_bytes());

Receive a response like: {"type":"connection_error","payload":{"message":"invalid type: string \"{\\\"type\\\":\\\"connection_init\\\"}\", expected internally tagged enum ClientMessage at line 1 column 32"}}

I'm not 100% sure about this but I think the expected behaviour is to close the websocket with an HTTP error.

You are right, I modified this question in the master branch, please help me test it, thanks.

Release in v2.5.2 🙂

Sorry, got pulled off this for a couple weeks. Looks like it's working as expected now. Thanks!


I finally created my Background.icns!

Since last September, I have been working hard to get the background of the opencore-bootloader.
Chris1111, I would like to express my sincere gratitude to you. (^+^)

Another Image.

Here
https://github.com/chris1111/My-Simple-OC-Themes/issues/2


Compatibility issues with Mozilla Firefox 44.0.2

Bug report

Node Version: v5.6.0

Protractor Version: 3.1.1

Browser(s): Firefox 44.0.2

Operating System and Version Ubuntu 14.04.4

A relevant example test
element.all(by.repeater('tab in $mdTabsCtrl.tabs')).get(1).click();
element.all(by.model('mode')).get(1).sendKeys('Python');

Output from running the test
Failed: Element is not currently visible and so may not be interacted with

Steps to reproduce the bug
Set up a simple html - angularjs app try to switch between tabs with protractor test.

Expected Behavior -
element.all(by.repeater('tab in $mdTabsCtrl.tabs')).get(1).click()
Should change to tab a position 1.
Works fine in chrome.

Actual Behavior -
Nothing happens, and no error is displayed. Tests just move on to whatever comes next.
Everything appears to be working fine, until we try to interact with elements that should be visible, the tests fail with the error 'Element is not currently visible and so may not be interacted with'.

In addition to your relevant example for element.all please provide config file, either the website that you are referring to or a sample html file. This will help us investigate the problem.

Also, could you format your example code with (either by indenting it or using backticks `)

Having some major issues even launching Firefox.
/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:108
  var template = new Error(this.message);
                 ^
UnknownError: Cannot find firefox binary in PATH. Make sure firefox is installed. OS appears to be: MAC
Build info: version: '2.51.0', revision: '1af067d', time: '2016-02-05 19:15:17'

@divmgl sounds like a different problem. Could you open up a new issue?

#2997

Closing stale issues.


Package hover: Show when last published

Useful for checking if a package is still actively maintained.

Note that I copied date.ts from the core code. Not sure if there is an easy way to share this code.

Really cool, thanks @chrmarti !


fabric8:build never ends

I'm facing with a problem.
I'm performing:
mvn -Dfabric8.namespace=t-devhub-dev \
  -Dfabric8.openshift.trimImageInContainerSpec=true \
  -Dmaven.test.skip=true \
  clean package fabric8:resource fabric8:build

This process is hanging on waiting for fabric8:build ends:
[INFO] --- fabric8-maven-plugin:3.5.38:build (default-cli) @ tdev-forum-service ---
[INFO] F8: Using OpenShift build with strategy Docker
[INFO] Copying files to /home/jcabre/projects/tdevhub/application-src/t-devhub/tdev-forum-service/target/docker/forum/0.0.1-SNAPSHOT/build/maven
[INFO] Building tar: /home/jcabre/projects/tdevhub/application-src/t-devhub/tdev-forum-service/target/docker/forum/0.0.1-SNAPSHOT/tmp/docker-build.tar
[INFO] F8: [forum:0.0.1-SNAPSHOT]: Created docker source tar /home/jcabre/projects/tdevhub/application-src/t-devhub/tdev-forum-service/target/docker/forum/0.0.1-SNAPSHOT/tmp/docker-build.tar
[INFO] F8: Updating BuildServiceConfig forum-s2i for Docker strategy
[INFO] F8: Adding to ImageStream forum
[INFO] F8: Starting Build forum-s2i

docker-build.tar is really straigforward:
├── Dockerfile
├── maven
│   └── tdev-forum-service-0.0.1-SNAPSHOT.jar
└── .s2i
    └── environment

where Dockerfile is:
FROM docker.io/fabric8/java-jboss-openjdk8-jdk:1.2
ENV JAVA_APP_JAR=tdev-forum-service-0.0.1-SNAPSHOT.jar
COPY maven /deployments/

and .s2i/environment:
JAVA_APP_JAR=tdev-forum-service-0.0.1-SNAPSHOT.jar

Also, I've tried using oc client:
cat docker-build.tar | oc start-build --from-dir=- --loglevel=10 forum-s2i --follow

It's also handing on:
I0723 12:17:06.770656    3403 loader.go:357] Config loaded from file /home/jcabre/.kube/config
Uploading archive file from STDIN as binary input for the build ...
round_trippers.go:417] curl -k -v -XPOST  -H "Accept: application/json, */*" -H "User-Agent: oc/v1.9.1+a0ce1bc657 (linux/amd64) kubernetes/a0ce1bc" -H "Authorization: Bearer cQFjgh_mjoAkbjYRhyz0sYCr8SaeauIpi4cjYL2UzDY" https://<cluster-url>/v1/namespaces/t-devhub-dev/buildconfigs/forum-s2i/instantiatebinary?name=forum-s2i&namespace=t-devhub-dev

Any ideas?

Can you have a look into the OpenShift Build object from another terminal ?
oc describe build forum-s2i
oc logs forum-s2i-build...

?

I would also recommend keeping an eye on events : oc get events -w

It's currently happing with all my builds:
oc describe build tdev-wsec-service-s2i output:
Name:		tdev-wsec-service-s2i-1
Namespace:	t-devhub-dev
Created:	28 minutes ago
Labels:		app=tdev-wsec-service
		buildconfig=tdev-wsec-service-s2i
		group=org.springframework.boot
		openshift.io/build-config.name=tdev-wsec-service-s2i
		openshift.io/build.start-policy=Serial
		provider=fabric8
		version=2.0.3.RELEASE
Annotations:	openshift.io/build-config.name=tdev-wsec-service-s2i
		openshift.io/build.number=1
		openshift.io/build.pod-name=tdev-wsec-service-s2i-1-build

Status:		Running
Started:	Mon, 23 Jul 2018 12:06:31 CEST
Duration:	running for 28m25s

Build Config:	tdev-wsec-service-s2i
Build Pod:	tdev-wsec-service-s2i-1-build

Strategy:	Docker
Output to:	ImageStreamTag tdev-wsec-service:2.0.3.RELEASE
Binary:		provided on build
Push Secret:	builder-dockercfg-t8ktw

Build trigger cause:	<unknown>

Events:
  Type		Reason			Age	From						Message
  ----		------			----	----						-------
  Normal	SuccessfulMountVolume	28m	kubelet, node4.si-origin-cluster.t-systems.es	MountVolume.SetUp succeeded for volume "builder-dockercfg-t8ktw-push"
  Normal	Scheduled		28m	default-scheduler				Successfully assigned tdev-wsec-service-s2i-1-build to node4.si-origin-cluster.t-systems.es
  Normal	SuccessfulMountVolume	28m	kubelet, node4.si-origin-cluster.t-systems.es	MountVolume.SetUp succeeded for volume "docker-socket"
  Normal	SuccessfulMountVolume	28m	kubelet, node4.si-origin-cluster.t-systems.es	MountVolume.SetUp succeeded for volume "crio-socket"
  Normal	SuccessfulMountVolume	28m	kubelet, node4.si-origin-cluster.t-systems.es	MountVolume.SetUp succeeded for volume "buildworkdir"
  Normal	SuccessfulMountVolume	28m	kubelet, node4.si-origin-cluster.t-systems.es	MountVolume.SetUp succeeded for volume "builder-token-fz1d5"
  Normal	Pulled			28m	kubelet, node4.si-origin-cluster.t-systems.es	Container image "openshift/origin-docker-builder:v3.9.0" already present on machine
  Normal	Created			28m	kubelet, node4.si-origin-cluster.t-systems.es	Created container
  Normal	Started			28m	kubelet, node4.si-origin-cluster.t-systems.es	Started container
  Normal	BuildStarted		28m	build-controller				Build t-devhub-dev/tdev-wsec-service-s2i-1 is now running

Logs:
oc logs tdev-wsec-service-s2i-1-build
Error from server (BadRequest): container "docker-build" in pod "tdev-wsec-service-s2i-1-build" is waiting to start: PodInitializing

and oc describe tdev-wsec-service-s2i-1-build ?

oc describe tdev-wsec-service-s2i-1-build
the server doesn't have a resource type "tdev-wsec-service-s2i-1-build"

sorry, I means 'oc describe pod tdev-wsec-service-s2i-1-build` ...

Here it goes:
$ oc describe pod tdev-wsec-service-s2i-1-build
Name:           tdev-wsec-service-s2i-1-build
Namespace:      t-devhub-dev
Node:           node4.si-origin-cluster.t-systems.es/<IP_ADDRESS>
Start Time:     Mon, 23 Jul 2018 12:06:31 +0200
Labels:         openshift.io/build.name=tdev-wsec-service-s2i-1
Annotations:    openshift.io/build.name=tdev-wsec-service-s2i-1
                openshift.io/scc=privileged
Status:         Pending
IP:             <IP_ADDRESS>
Controlled By:  Build/tdev-wsec-service-s2i-1
Init Containers:
  git-clone:
    Container ID:  docker://31ad6ece960d071eb7b19323ffdbd029062e6805dc616309abbafd0af2815b36
    Image:         openshift/origin-docker-builder:v3.9.0
    Image ID:      docker-pullable://docker.io/openshift/origin-docker-builder@sha256:6e57da79f6fa2bb99319722d02136ab2a4b5eba41699b8a17209180c0101596a
    Port:          <none>
    Command:
      openshift-git-clone
    Args:
      --loglevel=0
    State:          Running
      Started:      Mon, 23 Jul 2018 12:06:32 +0200
    Ready:          False
    Restart Count:  0
    Environment:
      BUILD:  {"kind":"Build","apiVersion":"v1","metadata":{"name":"tdev-wsec-service-s2i-1","namespace":"t-devhub-dev","selfLink":"/apis/build.openshift.io/v1/namespaces/t-devhub-dev/builds/tdev-wsec-service-s2i-1","uid":"1291eeec-8e60-11e8-b1f7-0050569fe304","resourceVersion":"50777263","creationTimestamp":"2018-07-23T10:06:31Z","labels":{"app":"tdev-wsec-service","buildconfig":"tdev-wsec-service-s2i","group":"org.springframework.boot","openshift.io/build-config.name":"tdev-wsec-service-s2i","openshift.io/build.start-policy":"Serial","provider":"fabric8","version":"2.0.3.RELEASE"},"annotations":{"openshift.io/build-config.name":"tdev-wsec-service-s2i","openshift.io/build.number":"1"},"ownerReferences":[{"apiVersion":"build.openshift.io/v1","kind":"BuildConfig","name":"tdev-wsec-service-s2i","uid":"11dea374-8e60-11e8-b1f7-0050569fe304","controller":true}]},"spec":{"serviceAccount":"builder","source":{"type":"Binary","binary":{}},"strategy":{"type":"Docker","dockerStrategy":{"env":[{"name":"HTTP_PROXY","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"HTTPS_PROXY","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"NO_PROXY","value":".cluster.local,.si-origin-cluster.t-systems.es,.svc,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,infra.si-origin-cluster.t-systems.es,master.si-origin-cluster.t-systems.es,node1.si-origin-cluster.t-systems.es"},{"name":"http_proxy","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"https_proxy","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"no_proxy","value":".cluster.local,.si-origin-cluster.t-systems.es,.svc,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,infra.si-origin-cluster.t-systems.es,master.si-origin-cluster.t-systems.es,node1.si-origin-cluster.t-systems.es"}]}},"output":{"to":{"kind":"DockerImage","name":"docker-registry.default.svc:5000/t-devhub-dev/tdev-wsec-service:2.0.3.RELEASE"},"pushSecret":{"name":"builder-dockercfg-t8ktw"}},"resources":{},"postCommit":{},"nodeSelector":{},"triggeredBy":null},"status":{"phase":"New","outputDockerImageReference":"docker-registry.default.svc:5000/t-devhub-dev/tdev-wsec-service:2.0.3.RELEASE","config":{"kind":"BuildConfig","namespace":"t-devhub-dev","name":"tdev-wsec-service-s2i"},"output":{}}}

      ORIGIN_VERSION:  v3.9.0+ba7faec-1
    Mounts:
      /tmp/build from buildworkdir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from builder-token-fz1d5 (ro)
  manage-dockerfile:
    Container ID:
    Image:         openshift/origin-docker-builder:v3.9.0
    Image ID:
    Port:          <none>
    Command:
      openshift-manage-dockerfile
    Args:
      --loglevel=0
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Environment:
      BUILD:  {"kind":"Build","apiVersion":"v1","metadata":{"name":"tdev-wsec-service-s2i-1","namespace":"t-devhub-dev","selfLink":"/apis/build.openshift.io/v1/namespaces/t-devhub-dev/builds/tdev-wsec-service-s2i-1","uid":"1291eeec-8e60-11e8-b1f7-0050569fe304","resourceVersion":"50777263","creationTimestamp":"2018-07-23T10:06:31Z","labels":{"app":"tdev-wsec-service","buildconfig":"tdev-wsec-service-s2i","group":"org.springframework.boot","openshift.io/build-config.name":"tdev-wsec-service-s2i","openshift.io/build.start-policy":"Serial","provider":"fabric8","version":"2.0.3.RELEASE"},"annotations":{"openshift.io/build-config.name":"tdev-wsec-service-s2i","openshift.io/build.number":"1"},"ownerReferences":[{"apiVersion":"build.openshift.io/v1","kind":"BuildConfig","name":"tdev-wsec-service-s2i","uid":"11dea374-8e60-11e8-b1f7-0050569fe304","controller":true}]},"spec":{"serviceAccount":"builder","source":{"type":"Binary","binary":{}},"strategy":{"type":"Docker","dockerStrategy":{"env":[{"name":"HTTP_PROXY","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"HTTPS_PROXY","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"NO_PROXY","value":".cluster.local,.si-origin-cluster.t-systems.es,.svc,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,infra.si-origin-cluster.t-systems.es,master.si-origin-cluster.t-systems.es,node1.si-origin-cluster.t-systems.es"},{"name":"http_proxy","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"https_proxy","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"no_proxy","value":".cluster.local,.si-origin-cluster.t-systems.es,.svc,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,infra.si-origin-cluster.t-systems.es,master.si-origin-cluster.t-systems.es,node1.si-origin-cluster.t-systems.es"}]}},"output":{"to":{"kind":"DockerImage","name":"docker-registry.default.svc:5000/t-devhub-dev/tdev-wsec-service:2.0.3.RELEASE"},"pushSecret":{"name":"builder-dockercfg-t8ktw"}},"resources":{},"postCommit":{},"nodeSelector":{},"triggeredBy":null},"status":{"phase":"New","outputDockerImageReference":"docker-registry.default.svc:5000/t-devhub-dev/tdev-wsec-service:2.0.3.RELEASE","config":{"kind":"BuildConfig","namespace":"t-devhub-dev","name":"tdev-wsec-service-s2i"},"output":{}}}

      ORIGIN_VERSION:  v3.9.0+ba7faec-1
    Mounts:
      /tmp/build from buildworkdir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from builder-token-fz1d5 (ro)
Containers:
  docker-build:
    Container ID:
    Image:         openshift/origin-docker-builder:v3.9.0
    Image ID:
    Port:          <none>
    Command:
      openshift-docker-build
    Args:
      --loglevel=0
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Environment:
      BUILD:  {"kind":"Build","apiVersion":"v1","metadata":{"name":"tdev-wsec-service-s2i-1","namespace":"t-devhub-dev","selfLink":"/apis/build.openshift.io/v1/namespaces/t-devhub-dev/builds/tdev-wsec-service-s2i-1","uid":"1291eeec-8e60-11e8-b1f7-0050569fe304","resourceVersion":"50777263","creationTimestamp":"2018-07-23T10:06:31Z","labels":{"app":"tdev-wsec-service","buildconfig":"tdev-wsec-service-s2i","group":"org.springframework.boot","openshift.io/build-config.name":"tdev-wsec-service-s2i","openshift.io/build.start-policy":"Serial","provider":"fabric8","version":"2.0.3.RELEASE"},"annotations":{"openshift.io/build-config.name":"tdev-wsec-service-s2i","openshift.io/build.number":"1"},"ownerReferences":[{"apiVersion":"build.openshift.io/v1","kind":"BuildConfig","name":"tdev-wsec-service-s2i","uid":"11dea374-8e60-11e8-b1f7-0050569fe304","controller":true}]},"spec":{"serviceAccount":"builder","source":{"type":"Binary","binary":{}},"strategy":{"type":"Docker","dockerStrategy":{"env":[{"name":"HTTP_PROXY","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"HTTPS_PROXY","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"NO_PROXY","value":".cluster.local,.si-origin-cluster.t-systems.es,.svc,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,infra.si-origin-cluster.t-systems.es,master.si-origin-cluster.t-systems.es,node1.si-origin-cluster.t-systems.es"},{"name":"http_proxy","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"https_proxy","value":"http://user_setools:yGlL2G5V6eGk@<IP_ADDRESS>:8080/"},{"name":"no_proxy","value":".cluster.local,.si-origin-cluster.t-systems.es,.svc,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,infra.si-origin-cluster.t-systems.es,master.si-origin-cluster.t-systems.es,node1.si-origin-cluster.t-systems.es"}]}},"output":{"to":{"kind":"DockerImage","name":"docker-registry.default.svc:5000/t-devhub-dev/tdev-wsec-service:2.0.3.RELEASE"},"pushSecret":{"name":"builder-dockercfg-t8ktw"}},"resources":{},"postCommit":{},"nodeSelector":{},"triggeredBy":null},"status":{"phase":"New","outputDockerImageReference":"docker-registry.default.svc:5000/t-devhub-dev/tdev-wsec-service:2.0.3.RELEASE","config":{"kind":"BuildConfig","namespace":"t-devhub-dev","name":"tdev-wsec-service-s2i"},"output":{}}}

      ORIGIN_VERSION:       v3.9.0+ba7faec-1
      PUSH_DOCKERCFG_PATH:  /var/run/secrets/openshift.io/push
    Mounts:
      /tmp/build from buildworkdir (rw)
      /var/run/crio/crio.sock from crio-socket (rw)
      /var/run/docker.sock from docker-socket (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from builder-token-fz1d5 (ro)
      /var/run/secrets/openshift.io/push from builder-dockercfg-t8ktw-push (ro)
Conditions:
  Type           Status
  Initialized    False
  Ready          False
  PodScheduled   True
Volumes:
  buildworkdir:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  docker-socket:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/docker.sock
    HostPathType:
  crio-socket:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/crio/crio.sock
    HostPathType:
  builder-dockercfg-t8ktw-push:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  builder-dockercfg-t8ktw
    Optional:    false
  builder-token-fz1d5:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  builder-token-fz1d5
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  zone=tier2
Tolerations:     <none>
Events:
  Type    Reason                 Age   From                                           Message
  ----    ------                 ----  ----                                           -------
  Normal  Scheduled              46m   default-scheduler                              Successfully assigned tdev-wsec-service-s2i-1-build to node4.si-origin-cluster.t-systems.es
  Normal  SuccessfulMountVolume  46m   kubelet, node4.si-origin-cluster.t-systems.es  MountVolume.SetUp succeeded for volume "docker-socket"
  Normal  SuccessfulMountVolume  46m   kubelet, node4.si-origin-cluster.t-systems.es  MountVolume.SetUp succeeded for volume "crio-socket"
  Normal  SuccessfulMountVolume  46m   kubelet, node4.si-origin-cluster.t-systems.es  MountVolume.SetUp succeeded for volume "buildworkdir"
  Normal  SuccessfulMountVolume  46m   kubelet, node4.si-origin-cluster.t-systems.es  MountVolume.SetUp succeeded for volume "builder-token-fz1d5"
  Normal  SuccessfulMountVolume  46m   kubelet, node4.si-origin-cluster.t-systems.es  MountVolume.SetUp succeeded for volume "builder-dockercfg-t8ktw-push"
  Normal  Pulled                 46m   kubelet, node4.si-origin-cluster.t-systems.es  Container image "openshift/origin-docker-builder:v3.9.0" already present on machine
  Normal  Created                46m   kubelet, node4.si-origin-cluster.t-systems.es  Created container
  Normal  Started                46m   kubelet, node4.si-origin-cluster.t-systems.es  Started container

@jeusdi thanks for the logs. Unfortunately however they don't indicate any error, except maybe that teh build pod stuck in the phase "Initialized". I suspect it's really an OpenShift issue, but you could verify this by trying an S2I build outside of f-m-p.
If this is the case, I'm afraid that f-m-p can't do much about it :(

@slaskawi : Could you please check whether your openshift is working(like a running a plain s2i build)? See Roland's comment.

Starting an s2i build works fine, the problem might be related to a binary build triggered by fmp.

@valdar @slaskawi : Oh I see, I haven't tried fmp on Openshift v3.10.0. Let me try this also. Is this problem intermittent or is it reproducible?

@rohanKanojia it is, at least according to my day of testing yesterday, reproducible both with version 3.5.40 and 3.5.41

Perhaps this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1620272

Might be more like this https://bugzilla.redhat.com/show_bug.cgi?id=1614493 , the problem is I can still reproduce it with ocp 3.10.34 which is said to be the fixed version.

3.11.0 alpha has this problem too:
11:33 $ oc version
oc v3.11.0-alpha.0+5fbdb89-dirty
kubernetes v1.10.0+b81c8f8
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://rhokd.everfree.forest:8443
openshift v3.11.0-alpha.0+5fbdb89-dirty
kubernetes v1.10.0+b81c8f8

[ERROR] Failed to execute goal org.jboss.redhat-fuse:fabric8-maven-plugin:7.2.0.fuse-720008:build (default) on project spring-boot-camel: Failed to execute the build: Unable to build the image using the OpenShift build service: Can't instantiate binary build, due to error reading/writing stream. Can be caused if the output stream was closed by the server. Connection reset -> [Help 1]

API server broken (why!!! go was created to write secure, bug-free software quickly!)
Authentication required for https://localhost:8443 (openshift)
Username: ggrzybek
Password:
Error from server (InternalError): Internal error occurred: unexpected response: 504

@grgrzybek: Is this still an issue with Openshift 3.11.0 ?

I had to switch to something else recently, but I think with some non-origin version of OpenShift, it worked fine. No more complaints from me.

I had exactly the same error and finally I could fix it. I changed the fabric9-maven-plugin version and I put the version 3.5.42.


docs: correction of icons set mapping function

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows Conventional Commits
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Refactoring
[ ] Code style update
[ ] Build or CI related changes
[x] Documentation content changes

What is the current behavior?
Closes #3370
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

@jekru e2e have failed

I am not sure is working as well

This PR is wrong, current function is correct. Icon processing function makes ID inside the file the same as the file name, therefore in both cases you need MAPPER[name].


fix(components): Update regex for recognizing ELO card schemes

Fix regex for recognizing ELO card schemes
Before:

After:

Hey @lyubomir-sumup can you check https://github.com/sumup/circuit-ui/blob/master/.github/CONTRIBUTING.md#releases.
It's recommend to use yarn commit now. This way you get release/changelog updates for free 😃

What's the status of this PR?