Continous loop, webinterface unresponsive

I flashed my wemos d1 mini with the nodemcu software. Now I have one effect in a loop and can't chose a color in the webinterface (loading forever). Should I reflash it with the wemos mini boardsettings?

SDK:2.2.1(cfd48f3)/Core:2.4.1/lwIP:2.0.3(STABLE-2_0_3_RELEASE/glue:arduino-2.4.1)`
readEEPROM(): 1
readEEPROM():
readEEPROM():
readEEPROM():
readEEPROM():
MQTT host:
MQTT port:
MQTT user:
MQTT pass:
*WM: Adding parameter
*WM: host
*WM: Adding parameter
*WM: port
*WM: Adding parameter
*WM: user
*WM: Adding parameter
*WM: pass
*WM:
*WM: AutoConnect
*WM: Connecting as wifi client...
*WM: Using last saved values, should be faster
scandone
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 2
cnt
connected with XXXXX, channel 1
dhcp client start...
ip:<IP_ADDRESS>,mask:<IP_ADDRESS>,gw:<IP_ADDRESS>
*WM: Connection result:
*WM: 3
*WM: IP Address:
*WM: <IP_ADDRESS>
connected...yeey :)
Arduino OTA activated.
Open http://<IP_ADDRESS>/ to open McLighting.
Use http://McLighting01.local/ when you have Bonjour installed.
New users: Open http://<IP_ADDRESS>/upload to upload the webpages first.
[WS-Server] Server Started.
FS File: /, size: 0B
FS File: /index.htm, size: 13.90KB
FS Usage: 14809/957314 bytes
readEEPROM(): STA| 1|  7|155| 45|255| 43|  0
Found saved state: STA| 1|  7|155| 45|255| 43|  0
ws2812fx_mode: 7
ws2812fx_speed: 155
brightness: 45
main_color.red: 255
main_color.green: 43
main_color.blue: 0
*WM: freeing allocated params!
pm open,type:2 0

Hi @MrSnuggles,
I would definitely give it a try. The wemos baords are always a bit different.
Regards
Tobias

@MrSnuggles Any news on this?


Support setting target-features and target-cpu

It would be great to have a way to be able to forward enabled Rust target features down to the C and C++ compilers, mapping the Rust names to the C / C++ compiler names depending on the compiler being used (for clang and gcc these names should be identical to the Rust ones most of the time).
The same applies to the target CPU where different compilers use -mcpu/-march/... to set it.

Seems reasonable to me!

I'm actually going to close this in favor of https://github.com/alexcrichton/cc-rs/issues/268


Update dependencies on cardano-ledger-specs and ouroboros-network

Would be really good if the  cardano-shell udpate in https://github.com/input-output-hk/cardano-shell/pull/365 could be included in that.

Would be really good if the cardano-shell udpate in input-output-hk/cardano-shell#365 could be included in that. I am just waiting for a CODEOWNERS approval.

Feel free to push an extra commit to this PR doing that. If that PR is only approved after your working hours, I'll try to remember to do it myself. You are not expecting breaking changes because of that PR, right?

There should not be any breaking changes.

https://github.com/input-output-hk/cardano-shell/pull/365 has been merged.

bors merge


chore(contracts): Stop counting expired/revoked/replaced Attestation via the balanceOf function

What does this PR do?
Stops counting revoked/replaced/expired Attestations via the balanceOf function
Related ticket
Fixes #806
Type of change

[X] Chore
[ ] Bug fix
[ ] New feature
[ ] Documentation update

Check list

[X] Unit tests for any smart contract change
[X] Contracts and functions are documented

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 48.84%. Comparing base (ba69bac) to head (f8a422c).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #835   +/-   ##
=======================================
  Coverage   48.84%   48.84%
=======================================
  Files          18       18
  Lines         389      389
  Branches       63       63
=======================================
  Hits          190      190
  Misses        196      196
  Partials        3        3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


chore(lint, formatting): introduce biomejs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

266 of 273 (97.44%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 96.667%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/mismatched-format/mismatched-format.mjs
23
25
92.0%

packages/alias/alias.mjs
35
40
87.5%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.09%

Covered Lines:
488

Relevant Lines:
496

💛  - Coveralls

Can we disable the formatting? I don't like the whitespace mangling it does; it makes it much more difficult to read (both grok and accessibility).

Maybe keep it for JSON

Can we disable the formatting? I don't like the whitespace mangling it does; it makes it much more difficult to read (both grok and accessibility).

Found good solution it's to use editorconfig as formater

bump @JakobJingleheimer

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

262 of 269 (97.4%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.08%) to 96.5%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/mismatched-format/mismatched-format.mjs
22
24
91.67%

packages/alias/alias.mjs
34
39
87.18%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.08%

Covered Lines:
485

Relevant Lines:
493

💛  - Coveralls

maybe we figure out how to get it to stop doing that last thing later?

I've tested a lot of things (using only editorconfig) and I've mostly played with the maximum line length. And what I've set seems to be the best I've found.

Yeah, I think so :) Good work 🙌


Weird behavior after loading & freeing font multiple times

I'm trying to figure out what is wrong with my game engine,
I'm not sure if I'm doing something wrong or this is a bug.
I created a simple example based on the library's sample that reproduces the problem.
After running 9 times load_font_file and then freed the font, my game crashes.
The font that I load and free multiple times is the same font file.
This is the code: https://gist.github.com/geocool/57bb71e6a8c4a4250d63
And this is the result :

I guess I'm leaking memory somewhere, I'll check the load_font_file function.

Fixed with bdee6f33eca7e85c2eaf5018c52e2852facfae86.


Add a static method of destroy all instances

This is a (multiple allowed):

[ ] bug

[x] enhancement

[ ] feature-discussion (RFC)

Swiper Version: EXACT RELEASE VERSION OR COMMIT HASH, HERE.

What you did
Add a static method Swiper.destroyAll to destroy all instances.
I push an instance to __swipers after created in closure. And support a destroyAll method to clear.
A destroyAll is like
Swiper.detroyAll = function() {
    __swipers.forEach(i => {
       i && i.destroy(true, true);
    });
});

Expected Behavior
Just like the name destroyAll, we can use Swiper to clear all instances when we need this.

btw,
When we init, we can push instance to __swipers, just like  __swipers.push(s)
when we destroy, clear instance in __swipers, just like __swipers.splice(__swipers.indexOf(s), 1)

I can't even destroy a single swiper :D
Wondering why I can't use destroy() in my swiper instance like:
mySwiper.destroy()

@xdemocle what do you mean ? You can't destroy one ? or you don't need destroy instance?

@bq-hentai in the end I gave up, because in my swiper instance I was receiving errors that destroy() method was not a function.

@xdemocle maybe sth. wrong in ur codes.

Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity.
If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


How to disable pseudolocalization from the File Explorer?

Tested versions
Reproducible in Godot
4.1.1
4.1.2
4.2.1
System information
OS: Windows 10 (x64), Godot version: 4.1.2
Issue description
After enabling "Pseudolocalization" from Editor > Editor Settings, the Projects Manager looks like this.

When attempting to open a project from the list, the engine crashes. Creating a new project didn't help getting into the engine either.
Downloading the latest version of Godot (4.2.1) didn't resolve this.
Is there a way to revert this change from the Project Manager or Windows File Explorer since I can't get into a project at all to turn off the pseudolocalization from the Editor?
Steps to reproduce

Enable Pseudolocalization. The engine will restart.
Once the Project Manager is open, click on any project from the list.
A Godot splash screen will open. However, the contents of the project will not load.
The splash screen will be automatically closed after a while.
Opening the Godot console would display the below.

Minimal reproduction project (MRP)
N/A

Update:
Found the Editor settings filepath and disabled it from there.
Editor settings path:
C:\Users<user>\AppData\Roaming\Godot
Steps:

Open the editor settings file (.TRES) from Notepad.
Locate "interface/editor/debug/enable_pseudolocalization = true" under "[resource]"
Set it to false. Save the file.
Reopen Godot.


docs: update RealtimeClient param key from token to apikey

What kind of change does this PR introduce?
docs update
What is the current behavior?
Specifies RealtimeClient param key is token
What is the new behavior?
Specifies RealtimeClient param key is apikey
Additional context
Related issue: Phoenix tokens for channel auth #95

Related comment: https://github.com/supabase/realtime/issues/95#issuecomment-777868713
NOTE:
Should be merged when feat: change socket param from token to apikey #122 has been merged to master.

@soedirgo: @kiwicopple recommended we leave in "token" for a few weeks and remove it from docs.

:tada: This PR is included in version 1.0.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Error: requested resource not found

the cortex package https://github.com/grafana/cortex-tools/pkg/client seems to be using  API v1 by default. The cortex deployment in my case uses only legacy API  "/api/prom/rules". Cortex client has a parameter : UseLegacyRoutes  . The same can be included in the provider definition.

https://github.com/grafana/cortex-tools/blob/master/pkg/client/client.go#L35

but this may require some other changes as well

but this may require some other changes as well

Can you please explain?

the format of the request body in the case of legacy routes is different. So it won't work just by changing the routes.


feat: improve before process epoch

Motivation

Improve beforeProcessEpoch by not allocating big arrays unnecessarily (that could cause spikes due to gc)
a continuation of #6945

Description

remove eligibleValidatorIndices: we can just base on flags
reuse nextEpochShufflingActiveValidatorIndices by allocating validatorCount items, use totalNextEpochShufflingActiveIndices to control its length
do not allocate proposerIndices and inclusionDelays if it's not phase0

Testing
on holesky beforeProcessEpoch could be less than 200ms. Note that it could still spike due to allocating validators array

Update test result after 3 days of testing

this branch, 1k, 10m rate interval

unstable, 1k, 10m rate interval

this branch, 1k, 6h rate interval

unstable, 1k, 6h rate interval

:tada: This PR is included in v1.21.0 :tada:


cd -

Calling cd - does not throw an error.
I think we don't have the cd - functionality implemented. I would expect an error about - directory not found. Instead, it silently does nothing.
I think it would be nice to have this functionality -- we could have PWD and OLD_PWD env vars. Calling cd <path> would move PWD into OLD_PWD and <path> into PWD. Calling cd - would swap PWD and OLD_PWD. We might as well go fancy and have PWD as a list or a record to implement this logic but that's probably stretching it too far.

I haven't looked but cd - is in nushell. I wonder how it works there.

I think in Nushell we store the previous pwd in the shell manager or something like that.

fixed by #787


Automated cherry pick of #8499: lockman: test: add prefix setting

Cherry pick of #8499 on release/3.5.
#8499: lockman: test: add prefix setting

/lgtm
/approve


orca or kaleido not available in my embedded system

Describe the bug
orca or kaleido not available in my embedded system
(headless so no chromium)
Additional context
Switch to matplotlib ?

Thank you for your comment.
The web application using this package (URL: https://shimeri-web.vercel.app) depends on plotly, so I am not considering switching the backend for drawing to matplotlib.
Could you provide more detailed information about the environment where this issue is occurring?


Order cannot be added to shipment.

Create new shipment
Try to add order.
Observed: it doesn't seem to get added and do not show Im the order area.

This has been fixed


'List' is deprecated and shouldn't be used.

Warning message:
'List' is deprecated and shouldn't be used. Try replacing the use of the deprecated member with the replacement.
Generated code:
  LocationCoordinate.fromJson(Map<String, dynamic> json) {
    states = json['states'].cast<String>();
    if (json['results'] != null) {
      results = new List<Results>();
      json['results'].forEach((v) {
        results.add(new Results.fromJson(v));
      });
    }
  }

Hey, thanks for reporting.
I believe the best replacement would be:
// results = new List<Results>();
results = new List<Results>.empty(growable: true);

Hey, thanks for reporting.
I believe the best replacement would be:
// results = new List<Results>();
results = new List<Results>.empty(growable: true);

Thank you. Your solution works

Hey, thanks for reporting.
I believe the best replacement would be:
// results = new List<Results>();
results = new List<Results>.empty(growable: true);

How about to use a literal list notation?
// results = new List<Results>();
results = [];

Also from the efective dart guide:
DON’T use new.
Linter rule: unnecessary_new
Dart 2 makes the new keyword optional. Even in Dart 1, its meaning was never clear because factory constructors mean a new invocation may still not actually return a new object.
The language still permits new in order to make migration less painful, but consider it deprecated and remove it from your code.

This project is all about honoring Dart's recommendations, and it seems that @RaulUrtecho is right.
I'll replace this with a non NEW solution shortly

It's done....sorry for taking soo long...It was a good nap though


Update Solo Machine Content under Nav Bar

Added solo machine content at https://github.com/crypto-org-chain/chain-docs/pull/282, also to add it to the navigation bar under "Resources."
Signed-off-by: Anthea<EMAIL_ADDRESS>

/staging


Logo contribution

Hello!
I designed a logo for runtime. Please tell me what you think. I waiting feedback.

Maybe a naive question (sry I am not familiar with marketing), but I would wonder why we are not using the kata containers logo here. It's a bit confusing to have different logos for the same project.

Thanks community!
I designed a logo to better reflect the property of this repository. A single logo is a good idea.
In that case,
If you need a logo for other projects,feel free to say me.
Best regards.

Thanks for the creative contribution, @reallinfo, but I agree with the others above--we'll stick with the one Kata logo. If you're interested in working on the marketing side of Kata, join the Working Committee meetings to get involved! Otherwise we can close this issue out.

Thanks @reallinfo and @annabellebertooch


Updates Node releases from both release and rc download directories

Builds on the work by Michał Gołębiowski to make two requests to both https://nodejs.org/download/release/ and https://nodejs.org/download/rc/ to add release candidates to the list of the Node versions and subsequently (as of 7th Sep 2015) show 4.0.0-rc.2 at /node/unstable - was previously incorrectly showing 0.12.7
I'm more than happy for any feedback on this and any changes that need to be made.

My comment disappeared due to an outdated diff so I'll repost here:
There's a lot of duplicated code in this PR. Why not download from both URLs, concatenate bodies (maybe separating them with a new line) and have parseResponse check both responses?
Also, note that /download/rc/ is a location of RCs but in the future there will also be betas/alphas, it should be decided what to do with them. For example, supporting nightlies would most likely be too much as they will arrive extremely frequently.
(NOTE: I'm not a maintainer of this module so my comments may be overruled :))

I agree about the duplication but I wanted to keep this PR as simple as possible and not introduce any async/promise libraries. I'm more than happy to refactor this if need be.
It's not entirely clear, to me, what the future release process will look like regarding alpha/beta/rc. I tried to decipher something from the following threads but they are fairly lengthy:
https://github.com/nodejs/dev-policy#release-process-and-branching-model
https://github.com/nodejs/node/issues/2522
https://github.com/nodejs/LTS
My main driver for this PR is that semver.io dictates which version of Node are avilable on Heroku and I believe there might be a significant desire to test out 4.0 especially as it will form the first LTS release with support until April 2017.

there might be a significant desire to test out 4.0 especially as it will form the first LTS release with support until April 2017.

One nit: 4.0 will not be an LTS, some future 4.x release will. The 4.x line will be normal Node stable line, it will turn into an LTS only when Node 5 is released. For more, see https://github.com/nodejs/LTS.

I'm going to close this as the final release of 4.0.0 came out pretty much straight away after the release candidates and some of the recent commits to this repo handle the changes to Node distribution.
It's likely we'll have to wait till October and Node 5.0.0 to get a clearer picture of how LTS and unstable releases of Node are going to handles going forward.

I'm happy to have the discussion up... now that 'stable/unstable' isn't such a clear cut thing in node versioning, we'll need to figure out what makes sense in terms of responses from semver.

now that 'stable/unstable' isn't such a clear cut thing in node versioning

It's more that now there are more flavors of "unstable": nightlies, alphas, betas, rcs. All x.y.z numbers are stable from 1.0.0 up.

I've created an issue that can track discussion of this issue more broadly than this specific pull request.
https://github.com/heroku/semver.io/issues/49


Issue #79 Read app configuration file once in app.py, and pass parame…

…ters to worker for it to use what it needs. Issue #80 Change Globus groups file override indication to be indicated by a file name.
Sorry to put two cards in one PR, but the work was kind of muddle together.

In the original writeup of issue #80, I put removing the file from Git based on @shirey  comments during a meeting.  But he later revised the issue to say, "L_ocating the GROUPS info file in the src/instance/ directory alongside app.cfg seems like the appropriate place for it, but ignored by git as app.cfg is_.", as archived in this comment.
Based on that, I revised the description to say keep it in GitHub.  But if his first instinct was to get it out of there, and that is yours also, maybe it should go.

I can push a file name change and app.py change.  @shirey is there someone else who should align the content with the SenNet group info, rather than HuBMAP?  It is unclear to me if description, name, displayname, etc. content referencing HM is important, or only the identfiers.

@kburke Sorry, based on our recent conversation leave this file as is- my confusion abounds.   @yuanzhou No further changes coming for this PR (yet :))


Date fields in dashboard won't trigger Datepicker on click or keyup

Hello!
I forked Saleor exactly one week age and cannot get datepicker to work on datefields. Triggering $('.datepicker').pickadate({}) throws a .datepicker is not definted error.
Behavoir -
Date fields cannot be focused on click.
Datepicker widget will only be shown if field is focused via tab key and then the enter key pressed; no other keyup works and cannot trigger keyup or click events on input element; using .trigger('click') throws trigger is not defined error.
I feel like I'm missing something, but am baffled after using Materialize outside of Saleor many times in the past. Any tips?
As one example, here's the product.available_on field rendered in the dashboard.
<input type="text" id="id_available_on" class="datepicker picker__input" name="" value="" readonly="" tabindex="-1" aria-haspopup="true" aria-expanded="false" aria-readonly="false" aria-owns="id_available_on_root">
Thanks!
Ian

I'm having this exact same problem as well

This seems to be working fine now. Please let us know if the problem returns.


ISPN-14803 Make sure block hound works in a server

https://issues.redhat.com/browse/ISPN-14803

I need to rework some more of the Blockhound integrations to get a server running.

I was able to run a server on main and was able to complete a RESP benchmark, we can tweak more as needed after this PR.

Should be good now.

Note that the blockhound jar has to be added to the lib directory and cannot be installed in the server/lib directory due to how our class loading works.


Typescript example causes error

I'm trying to use Ohm with Typescript, following the example, but I keep getting an error:
 TypeError: Cannot read properties of undefined (reading 'createSemantics')

      3 | import grammar, {LangSemantics} from './lang.ohm-bundle'
      4 |
    > 5 | const semantics = grammar.createSemantics()

Using the generate command created the lang.ohm-bundle.js and lang.ohm-bundle.d.ts files correctly, as far as I can tell, but it's just not working.
I'm trying to add this to a fairly large project, and I'll admit that I'm not the most JS/TS proficient person, so I'm just wondering if there are settings in various config files that need to be set a certain way for this to all work. (And if that info could be added to the documentation.)

See if this helps you: https://github.com/ohmjs/ohm/pull/462
My PR has been open forever so I don't think they particularly care about this project or the fact that users are experiencing frustration


Feature/update project status

Update Project Step dialog.  It's just a long scroll down for now.  The new schema is from SeedCompany/cord-api-v3#1038, hence the failing CI but the code is ready for review

@frankyma The dialog was really long due to all the step options. I changed it to an autocomplete. What do you think?

@frankyma The dialog was really long due to all the step options. I changed it to an autocomplete. What do you think?

Seems like a good idea.  I was thinking we'd divide into columns but autocomplete is easier


Possibility to have the same border style in all stickers

I recently noticed that some stickers have colored borders, while others do not.
I was wondering if it would be possible to have all sticker with the same border style, either all of them with borders or no borders at all. If this can be made configurable, even better.
Not my choice, but I prefer a light border :3

Ah, yeah, some of the themes I didn't feel like the border added anything to it. It might be something I consider, but I have been pretty strapped for time recently. Thanks for bringing it up though :)


Tensorboard log

Hi.
Can you also upload the tensorboard log of your training?

✅ See this link https://huggingface.co/richardbaihe/a3t-vctk/tensorboard


Fix cognitoUserPools trait documentation formatting

Fixes formatting for aws.auth#cognitoUserPools trait to match other authentication traits.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This needs to update the API Gateway docs that reference this heading now since they say "aws.auth#cognitoUserPools trait trait"


add natural sort library function

Originally reported by @bcmdarroch
Overview
This was implemented individually on each of the setting pages: https://github.com/chef/a2/pull/4434
it’d be a great refactor opportunity to pull the sorting logic out of those components into some shared library function that all of automate-ui could use.
as part of this work, we could also investigate where we want library functions to live. another good library candidate would be copy (see slack discussion starting here). we might consider these functions like an extension of the ui-library

@msorens - Advice on where to place this function would be greatly appreciated.  I see a helpers folder in app/components but I don't see anywhere yet that would be a good placement for it there.

My suggestion would be components/automate-ui/src/app/helpers/auth/sorter.ts since this particularly sorting mechanism is used solely by auth components.


[Do Not Merge] Placeholer PR to run all CI unit tests

creating this PR to run all unit tests, and see if we get any improvement with the switch to the version of hcc that contains the fix for issue-812.

closing out this PR as its purpose is served


Add new XR knob for requesting OpenXR extensions.

This is designed to allow projects and benchmarks to request additional OpenXR extensions on top of the handful that the ppx::XrComponent class requests.

Sorry for the review delay!


Display more info on default props

Default props on the prop table are displayed using the same 'PropVal' component used in source code section.
They will be shown like this.

Love it!

Great. Go for this.


Linux Support !

Hi..
This is my pull for Linux support.
Tested on Gnome 3.8 & 3.10.
Yakir.

Good job!


Hande Dialyzer warnings

Run dialyzer on the test profile during make dialyzer, and in CI runs.
This PR fixes all dialyzer warnings found in the rebar3 test profile.

A multibulk can contain a null value, like '$-1\r\n'
which is an 'undefined' in the return_value().

What about integers and other types? INCR returns an integer IIRC.

What about integers and other types? INCR returns an integer IIRC. In CLUSTER SLOTS we have integers inside array (multibulk).

I believe integers should be covered by the second binary() in:
-type return_value() :: undefined | binary() | [binary() | nonempty_list() | undefined].
as in the test
multibulk_multitype_test() ->
    %% [1, 2, 3, 4, "foobar"]
    B = <<"*5\r\n:1\r\n:2\r\n:3\r\n:4\r\n$6\r\nfoobar\r\n">>,
    ?assertEqual({ok, [<<"1">>, <<"2">>, <<"3">>, <<"4">>, <<"foobar">>], #pstate{}}, parse(init(), B)).

So integers are returned as binary. Sad but true.


feat: migrated assignment form from partial to view component

Fixes #4170
Describe the changes you have made in this PR -

Migrated assignment form from partial to view component
Wrote Test cases for the assignment form in spec folder

Screenshots of the changes (If any) -
https://github.com/CircuitVerse/CircuitVerse/assets/91966855/2b510883-a97b-40e2-b664-b1ebf1fd5908

cc @tanmoysrt


Validation Binding Error with v. ^0.12.3

I'm submitting a bug report

Library Version:
0.12.4

Please tell us about your environment:

Operating System:
Linux KUbuntu

Node Version:
4.4.7

NPM Version:
3.10.6

JSPM OR Webpack AND Version
webpack 1.13.2

Browser:
Chromium

Language:
TypeScript 2.0.2

Current behavior:
Since version 0.12.3 I get the following error in my validation binding:

Which previously worked well. I went back to version 0.12.2 to test and it worked flawlessly. This error occurs with the versions 0.12.3 and 0.12.4 of aurelia-validation.
Expected/desired behavior:
Binding a value with the validate binding behaviour which is coupled with a validationController should not throw an error.

this almost seems like you have multiple versions of aurelia-binding.  I would say execute jspm inspect --forks but it you're using webpack.
try executing npm install aurelia-binding@latest aurelia-templating@latest aurelia-validation@latest --save

@jdanyow didn't expect that. Seems to work now, thank you :smile: I doubt that i had multiple versions of it, i run npm prune right after installing the new dependencies, but maybe i had an old version of aurelia-binding or templating around.
Can be closed :-)


Update dependecies

Updated dependencies to fix vulnerabilities and support monaco-editor ^0.52.0.

I think this still need more updates for the angular19 dependencies

We will move to v19 on Monday


as "¶" is non-ascii character, we need to define encoding.

django/python takes output as ASCII by default, we need to define another (iso-8859) encoding for this piece of code as ¶ is a non-ascii character.

one more thing, now while executing the script this error shows up--
File "/home/trololol/my_proj/src/profiles/admin.py", line 25
SyntaxError: Non-ASCII character '\xc2' in file /home/trololol/edge2/my_proj/src/profiles/admin.py on line 25, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
now it is perfectly working/patched up after i've defined encoding.

Thanks Parv! This issue never cropped up in my testing. I have added a commit f90249b to fix this without changing the encoding. Hopefully everything else is working fine as well.

great!

there is a bit of the problem. with your commit (f90249b), though!

when i changed it to the commit i've created, it worked flawlessly.

Looks like I could have written this a lot better. Firstly using old style % interpolation and not importing unicode literals from future. Please check this commit/branch c46dd40fcd

Thank you for bringing this to my attention. I guess I need to do a thorough check of the code for places where I need to insert from __future__ import unicode_literals and remove old style interpolation. I have created an issue https://github.com/arocks/edge/issues/13

now that's working perfectly!


[WIP] Update Notification Improvements

closes #5071
We just merged notification improvements into LTS, see. The PR ports these changes over to 1.0.

[ ] go over changes once (quality check)
[ ] migration script for the removed settings keys? or add to things we want to remove in the next major
[x] discuss with @kevinansfield how to mark release notification as seen tomorrow - admin fetches latest release
[ ] do a big test for 1.0 messages
[x] add UI - @kevinansfield
[ ] pull https://github.com/TryGhost/Ghost/pull/9138
[ ] private configuration endpoint to expose if a blog is pro
[ ] private configuration endpoint to expose the update check url

@kevinansfield
Example notification format:
{"notifications":[{"dismissible":true,"location":"bottom","status":"alert","id":"d5a28f10-7d22-11e7-85a2-19d8e9ec82k9","type":"info","custom":true,"top": true, "message":"CUSTOM_MESSAGE"}]}

Won't continue with this PR before Wednesday.

I'll continue with the PR today and tomorrow 👩🏽💻

Will continue with this tomorrow, i want to discuss 1-2 little things internally later.


OpenSSL accepts a cert which has no subjectAltName and an empty subject and duplicate exts

Description of problem:
OpenSSL accepts a cert which has no subjectAltName and an empty subject and duplicate exts. GnuTLS and wolfSSL reject it.
Version of OpenSSL used:
1.1.1, 1.1.1f
OS
Ubuntu x64
Steps to Reproduce:

openssl verify -CAfile ca.pem seed-4s18-12s35-155s28-584c21-990c22.pem

Actual results:
openssl verify -x509_strict -CAfile ./certs_related/ca.pem ./certs/seed-4s18-12s35-155s28-584c21-990c22.pem
./certs/seed-4s18-12s35-155s28-584c21-990c22.pem: OK

Expected results:
Consistent verification results among the TLS implementations above.
Attachment:
ca.zip
seed-4s18-12s35-155s28-584c21-990c22.zip

Similarly to my remark on #13970 it's not clear why you expect openssl verify to be looking at the subject information and extensions of the end-entity certificate.

Marking as inactive, to be closed at the end of 3.4 dev barring further input


Resolve proto directory dynamically for dotnet cartservice

Changes
This allows the solution to be opened in any .NET editor and compile straight away.
Removes the requirement to manually copy the proto files.
This also now copies the protobuf files into the docker container using the original folder name.
Merge Requirements
For new features contributions please make sure you have completed the following
essential items:
* [ ] CHANGELOG.md updated to document new feature additions
* [ ] Appropriate documentation updates in the [docs][]
* [ ] Appropriate Helm chart updates in the [helm-charts][]

@open-telemetry/demo-approvers pardon the ping but this PR is not stale 😸


Refactor get user settings

Description
The main purpose of this pull request is to enhance the process of getting the current user's settings.
Test Plan
N/A
Motivation and Context
The general functionality of the app needs to be improved to be leaner and more performant overall. By refactoring not only the GetUserSettings async thunk, but as well as the containers where the thunk is used, the process of getting the current user's settings can be improved upon.
How Has This Been Tested?
I've manually tested the performance of the app by going through the containers in question and seeing how the new implementation is performing.
Types of Changes

Documentation
Bug fix
[x] New feature
Breaking change

Checklist

[x] My code follows the code style of this project

 Get user settings thunk


Set the block's m_water_level in Arena:free even if the block is not the last block

Link to issue #5155

[approve ci]

[approve ci autest]

Looks good to me.
It may reduce the use of memory.

I think this is wrong. The design in Arena is such that only memory in the last block can be freed. This change will have no effect on memory usage, as allocation in Arena only happens from that same last block. The current logic is correct - if the released memory isn't the most recently allocated memory, it's a noop.

I'm ok with that. But I prefer to adding tail pointer which point to the last block to speed up the traversing.
IIUC, the arena's lifecycle is always bond with a transaction or in a stack. That means we don't need to strictly free the memory. And all blocks are freed by destructor just like a heap.  And it is mainly designed for string because the strings is not fixed size.
And We always use free where is very close to alloc. Otherwise you have no idea where the m_water_level is. And if you free the memory into the start - water_level. The block's water_level will never be shrank. But it is ok since because we have the gc in destructor.

There's no point in a tail pointer with this fix, since the list needs to be scanned for free memory. Without the fix, a tail pointer is a clear performance gain. In the larger picture, however, I think this is a dead end. As noted, I have been working on the MemArena class as a replacement for this class. If we think there are additional features, we should put the in that class, rather than patching old code. You can see the documentation here. In this regard, MemArena only supports memory freeing at the end. To improve memory usage, it searches back from the tail, but stops when it reaches a block with less than a threshold amount of free space, to limit search time. Blocks that drop below that threshold after an allocation are moved to the front so they don't get searched again.

I'm ok with that. But I prefer to adding tail pointer which point to the last block to speed up the traversing.
IIUC, the arena's lifecycle is always bond with a transaction or in a stack. That means we don't need to strictly free the memory. And all blocks are freed by destructor just like a heap. And it is mainly designed for string because the strings is not fixed size.
And We always use free where is very close to alloc. Otherwise you have no idea where the m_water_level is. And if you free the memory into the start - water_level. The block's water_level will never be shrank. So even include this change, it is still a problem. But it is ok since because we have the gc in destructor.

It's good idea to add a tail pointer due to free is very close to alloc

I'm ok with that. But I prefer to adding tail pointer which point to the last block to speed up the traversing.
IIUC, the arena's lifecycle is always bond with a transaction or in a stack. That means we don't need to strictly free the memory. And all blocks are freed by destructor just like a heap. And it is mainly designed for string because the strings is not fixed size.
And We always use free where is very close to alloc. Otherwise you have no idea where the m_water_level is. And if you free the memory into the start - water_level. The block's water_level will never be shrank. So even include this change, it is still a problem. But it is ok since because we have the gc in destructor.

The new arena block  is in the head of the list，tail pointer actually point to the block fisrt allocate.
according to “And We always use free where is very close to alloc.” ,Scanning from header may be better.


Updates from all patch merges for Patch 1

pysam differ failing as expected until pysam_hybrids branches are merged.


Check if image is ready before chatting about it

This should help avoid the UnicodeDecodeError: 'utf-8' codec can't decode byte 0xeb in position 0: unexpected end of data error, which happens when calling the chat function before uploading the image. Instead, in the terminal, a message will inform that the image still needs to be uploaded.

Thanks for finding an issue with the webui and fixing it!


Fix/issue 3321

References
Add references/links to any related issues or PRs. These may include:

Fixes #3321

Description
Based on the noUiSlider Event Callback docs, I changed the slider to submit the year range query when the user releases the mouse button, as opposed to while the user was dragging the slider. dsDebounce was removed and the (change) was changed to onSubmit() from onSliderChange() (which I couldn't find in the component script).
Instructions for Reviewers
Please add a more detailed description of the changes made by your PR. At a minimum, providing a bulleted list of changes in your PR is helpful to reviewers.
List of changes in this PR:

The dsDebounce parameter was removed, originally set to 250ms.
The (change) argument was changed to onSubmit() from onSliderChange()

Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[ ] My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
[ ] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[ ] My PR passes ESLint validation using npm run lint
[ ] My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
[ ] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[ ] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[ ] My PR aligns with Accessibility guidelines if it makes changes to the user interface.
[ ] My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
[ ] My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
[ ] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[ ] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
[ ] If my PR fixes an issue ticket, I've linked them together.

I have a strong feeling that I did this wrong, so I would be happy to try again if needed.

Issue already resolved https://github.com/DSpace/dspace-angular/pull/3236; I explain here https://github.com/DSpace/dspace-angular/issues/3321#issuecomment-2344879676


backport cluster evaluation permissions #1885 to 1.x

Description
Backport of #1885 to 1.x
Issues Resolved
Backport PR #1885
Check List

[x] New functionality includes testing
[x] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Note; I am merging as the build was successful, we no longer maintain the test infrastructure for these older branches


Update guides for Keras V3 Saving Compatibility

This PR updates existing keras-io guides ensuring that the models created are saveable via the new Keras V3 saving format (.keras).
Most changes involve the addition of the @keras.utils.register_keras_serializable() decorator, which should be standard practice for custom objects. Additionally, these guides were updated to use the new standard import keras instead of from tensorflow import keras.

Regenerated all the md/ipynb files corresponding with the changes, thanks!

Reverted all image changes, thanks!


new module syntrax

new module syntrax created; new syntrax generator added that uses jsyntrax API

Already merged to upstream, now closing this & syncing the atp-mipt fork


remove config volume mount

@initcron Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


How to bind event to validator?

eventually i did not get it right but i would like to use validator.js like so: https://jsfiddle.net/rydfz6tk/
seems like the lib does not bind to its data sources so i will have to init Validator on every keyup again to make it work this way?

Correct, the data isn't bound so you will have to new up Validator on each key stroke. Let us know if you face any performance issues with this. We've talked about doing something where the rules are parsed only once when the Validator instance is created and being able to set data on the same instance after the fact.


Prathamesh Borse

Due we close new issues on PR merge and voting is still possible on closed issues I will close this one. Nice Profile btw 🚀


line number of log file instead of timestamp

I need to print where from log was written in output file.
This is the winston log output on console:
2015-11-10T18:19:49.603Z - error:  TypeError: Cannot read property 'Id' of null
	at global.f_create_urlQuery (C:\_Projeler\AdminLTE\trunk\node\globals.js:922:53)
	at Layer.handle [as handle_request] (C:\_Projeler\AdminLTE\trunk\node_modules\express\lib\router\layer.js:95:5)
	at trim_prefix

In the file it looks like this:

But I want to have something like this:
debug.log(3) - error:  TypeError: Cannot read property 'Id' of null

Is there any way to make output like this FileName(lineNumber) ?

winston is not going to help you here because your Error stack trace is captured independently to where logging happens.


React.PropTypes no longer exists in React 16

https://github.com/cssivision/qrcode-react/blob/master/lib/index.js#L31
This breaks the build in React 16. Need to use:
import PropTypes from 'prop-types';

See my PR #10

Also fixed in my PR #11


Management of Font Awesome assets

Currently the FA icons we're using are from the default set, stripped down to the icons specified to be used in PF4. I talked to @mindreeper2420 and he shared some assets used for the original implementation.

PatternFly 4 icon list
PatternFly 3 vs 4 comparison list
Adam's sketch file

How do we want to manage these going forward? Do we want to use a tool like Iconmoon or Fontello to make management easier? Should we add global vars for the content strings to use when defining an icon directly into a pseudo element (ie, not using .fas.fa-icon-name) as mentioned in the breadcrumb component?
Also check to see what we should do about thes PF3 icons

https://github.com/patternfly/patternfly-next/issues/375
are these included here? https://github.com/patternfly/patternfly-next/pull/766

And maybe open a separate issue for a demo page

https://github.com/patternfly/patternfly-next/issues/370

cc @matthewcarleton @LHinson

related - https://github.com/patternfly/patternfly-next/issues/771


abortEarly option not respected

It appears that when an error is thrown because of an invalid semver, errors from elements on the same level are not appearing alongside that error when the abortEarly option is set to false.
Aside from that, this extension is awesome! Thanks for making this available.

actually, this is most likely an error on my part. I'm still seeing this even when using string type

just to follow up, I did confirm this was my own stupidity. Had my joi.validate options out of the method for that and as a parameter of the method surrounding it


React Native support possible? RN web or RN android/ios

Feature Description
Is it possible for node-llama-cpp to support React Native projects?
I know that this project depends on many node standard libraries, but is it possible to make changes and run in RN runtime? Especially now that it supports arm64 Mac and Windows machines, is it possible to run in arm64 non-node environments?
Even just importing node-llama-cpp necessary functions produces error.
On Android it gives error: The package at "node_modules/node-llama-cpp/dist/evaluator/LlamaModel/LlamaModel.js" attempted to import the Node standard library module "process". It failed because the native React runtime does not include the Node standard library.
On React Native web (using expo) it gives the following error
The resource from “http://localhost:8081/node_modules/expo/AppEntry.bundle?platform=web&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.routerRoot=app” was blocked due to MIME type (“application/json”) mismatch
which comes from a

The focus of this library is mainly on running on node and node-based environments (like Electron, Bun, etc.), but I don't rule out supporting React-native if it doesn't require significant changes and is not a great maintenance burden.
I haven't used React native for a long time now, so I'm not proficient with its latest features, but from what I've seen, it doesn't use a node runtime and instead has its own kind of runtime that's implemented differently.
node-llama-cpp uses node-addon-api for the native side that uses llama.cpp, and from what I've gathered it's not supported in React native.
If you can find a solution to use a native code that's written using node-addon-api in React native, then it'd be very helpful for adapting node-llama-cpp for React native.
If the process module is the only remaining obstacle, I can refactor the code to use a custom implementation that uses a different abstraction layer when running in React native, but I think the usage of node-addon-api is the main issue.

We probably have to wait for this PR https://github.com/facebook/hermes/pull/1377 which is available in RN 0.75.0-rc.5 or newer. But even after that I don't know if android, ios is supported out of the box or not. However RN windows seems to have this implemented already https://github.com/microsoft/hermes-windows/pull/61 . But I have not experimented with any one of them yet. I will continue to research on it and share my findings here. Here is two other discussions to follow for this topic 1) https://github.com/nodejs/abi-stable-node/issues/459 and 2) https://github.com/facebook/hermes/discussions/1074

@raymon-io That looks promising!
Let me know if you need my help to get a POC working when you get to it.
It would be great if you can, as part of your research, find some way to create a basic testsuite for the compatibility of a future support for React Native for Android/iOS/Windows/etc.
This will be important to make sure that changes made to node-llama-cpp for node-based platforms won't break React Native support.


Incorrect path on page?

On the note it says to go to:
com.microsoft.Office365ServiceV2/Data/Caches/com.microsoft.Office365ServiceV2/
However, we don't see that, we see:
com.microsoft.Office365ServiceV2/Data/Library/Caches/com.microsoft.Office365ServiceV2/
Not sure if the path has changed or if it's different.

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

ID: 4e273e29-10ac-440e-634e-588b5208e484
Version Independent ID: a5a6dc8a-b504-686e-80ce-45aabd6f832b
Content: Clear the Office cache - Office Add-ins
Content Source: docs/testing/clear-cache.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@jreed5 Thanks for asking about this. We'll investigate and update the docs as needed.
Thanks.

@jreed5 For now, I'm adding the location you reported instead of replacing the previous location. I'll continue investigating and remove the previous location if it's no longer valid.
Thanks.

@jreed5 Was your cache location under ~/Library/Containers? Thanks.


NSM CI on Azure

Cross Cloud-CI runs on Azure.  As an extension of #316 it would be good to get NSM CI working on Azure as well.

@edwarnicke I'll take a look.

#887 merged. Closing.


Fix broken lambda in defaultdict

This was causing some Splunk metrics to not be reported.
R? @cory-stripe

👍


Get at debugger running on our git-phlow project

See #211 - we need to able to debug our code.
There is a MAC problem - @kryptag will you add error message here and solution?
When you can run the debugger on our git-phlow executeable, we can close this issue with a section in our developer info file about how to get it running on MAC and solve your problem as we expect other will see that.

@kryptag wanted to close this - closing comment is https://github.com/Praqma/git-phlow/issues/215#issuecomment-325967474


Added linspace

Proposed changes
Adds mx.linspace support based on the numpy.linspace interface. Open to changing the interface if you'd rather imitate torch.linspace.
Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING document
[x] I have run pre-commit run --all-files to format my code / installed pre-commit prior to committing changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have updated the necessary documentation (if needed)

@dc-dc-dc Let me know when you are ready for re-review. I think you need to rebase on main as well to resolve conflicts.

@awni Getting this finished up now!

PS @dc-dc-dc thanks for the reviews :)


fix(source-tracking): clean up mpd to prevent source tracking lib to gather status of all files

Description
Possibly source tracking lib use statusMatrix to gain information about all files when the
repository is initiated. This is gathered from the projects path at the point when the library is
intiatlized. As sfpowerscripts fixes source tracking one after the another, this is not necessary
and is resulting in some errors (statusMatrix unable to find files.. though no functional impact)
and also unnecessary computation. This fix is to clean up the sfdx-project.json to only carry the
package that is currently being fixed up for source tracking
Checklist
All items have to be completed before a PR is merged

[x] Adhere to Contribution Guidelines
[x] Updates to Decision Records considered?
[x] Updates to documentation at DX@Scale Guide considered?
[x] Tested changes?
[x] Unit Tests new and existing passing locally?

Codecov Report

Merging #930 (c71aef8) into develop (4b15d09) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #930   +/-   ##
========================================
  Coverage    80.16%   80.16%
========================================
  Files           36       36
  Lines         1104     1104
  Branches       238      238
========================================
  Hits           885      885
  Misses         209      209
  Partials        10       10

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 4b15d09...c71aef8. Read the comment docs.


build(ci): fix E2E Docker failed to write PEM to file

Motivation
Try to fix Docker E2E build dfx error:

#22 70.26 Error: Failed to save pem: Failed to write PEM to file: Failed to encrypt PEM file: /home/apprunner/.config/dfx/identity/___temp___minter/identity.pem.encrypted

Changes

Tests

We do not need this. It does not work anyway.


[3.x] Scroll to selected item when filtering VisualScript nodes

Also moves the construction of type icon array out of for loop.

Thanks!


April 2024 jdk22 dryrun triage

Release Summary Report for release-openjdk22-pipeline
Report generated at: Wed, 10 Apr 2024 16:23:21 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk22-pipeline/12/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk22u" build number 11 at 4/9/2024, 12:41:20 PM

✔ results in these Tables means the activity has successfully completed.
⏳ results means that we are actively working on closing off the runs needed for this version, platform, binaryType.
⛔ means there is no build planned for that version/platform combination.
⏸ means activity not yet started.

Platform
Status
Results

x86-64_mac
✅
comment

x86-64_linux
✅
comment

x86-64_windows
⏸
comment

aarch64_linux
✅
comment

aarch64_mac
✅
comment

x86-64_alpine-linux
⏳
comment

ppc64le_linux
⏳
comment

s390x_linux
⏳
comment

ppc64_aix
⏳
comment

aarch64_alpine-Linux
⏳
comment

riscv64_linux
⏳
comment

Test_openjdk22_hs_extended.openjdk_aarch64_alpine-linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_aarch64_alpine-linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_aarch64_alpine-linux_testList_0 ⚠ UNSTABLE ⚠
jdk_nio_0 => deep history 4/7 passed | possible issues
Test_openjdk22_hs_extended.openjdk_aarch64_alpine-linux_testList_2 ⚠ UNSTABLE ⚠
jdk_build_0 => deep history 0/7 passed | possible issues
jdk_build_1 => deep history 0/12 passed | possible issues
Test_openjdk22_hs_extended.openjdk_aarch64_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_aarch64_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_aarch64_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_net_0 => deep history 3/6 passed | possible issues
jdk_tools_1 => deep history 0/4 passed | possible issues
jdk_build_0 => deep history 29/31 passed | possible issues
Test_openjdk22_hs_extended.openjdk_aarch64_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_jdi_0 => deep history 1/5 passed | possible issues
jdk_jdi_1 => deep history 25/30 passed | possible issues
jdk_build_1 => deep history 3/5 passed | possible issues
Test_openjdk22_hs_extended.openjdk_aarch64_mac ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_aarch64_mac_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode)

Test_openjdk22_hs_extended.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_ppc64_aix_rerun ✅ SUCCESS ✅
Rerun all
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode)

Test_openjdk22_hs_extended.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_ppc64le_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_s390x_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_s390x_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_x86-64_alpine-linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_x86-64_alpine-linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_x86-64_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_x86-64_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_x86-64_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_tools_1 => deep history 0/3 passed | possible issues
jdk_build_0 => deep history 13/15 passed | possible issues
Test_openjdk22_hs_extended.openjdk_x86-64_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_build_1 => deep history 3/5 passed | possible issues
Test_openjdk22_hs_extended.openjdk_x86-64_mac ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_x86-64_mac_rerun ✅ SUCCESS ✅
Rerun all
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode)

Test_openjdk22_hs_extended.openjdk_x86-64_mac_testList_1 ⚠ UNSTABLE ⚠
jdk_security3_1 => deep history 0/1 passed | possible issues
jdk_jfr_1 => deep history 0/1 passed | possible issues
Test_openjdk22_hs_extended.openjdk_x86-64_mac_testList_2 ⚠ UNSTABLE ⚠
jdk_net_1 => deep history 7/8 passed | possible issues
jdk_nio_1 => deep history 5/8 passed | possible issues
Test_openjdk22_hs_extended.openjdk_x86-64_windows ❌ ABORTED ❌
Test_openjdk22_hs_extended.openjdk_x86-64_windows_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_x86-64_windows_testList_0 ⚠ UNSTABLE ⚠
jdk_beans_1 => deep history 16/17 passed | possible issues
jdk_net_0 => deep history 0/5 passed | possible issues
jdk_tools_0 => deep history 0/5 passed | possible issues
jdk_tools_1 => deep history 0/5 passed | possible issues
jdk_imageio_1 => deep history 4/5 passed | possible issues
Test_openjdk22_hs_extended.openjdk_x86-64_windows_testList_1 ❌ ABORTED ❌
jdk_beans_0 => deep history 2/5 passed | possible issues
jdk_security3_1 => deep history 2/5 passed | possible issues
Test_openjdk22_hs_extended.openjdk_x86-64_windows_testList_2 ❌ ABORTED ❌
jdk_io_1 => deep history 3/5 passed | possible issues
jdk_other_1 => deep history 3/5 passed | possible issues
jdk_net_1 => deep history 5/18 passed | possible issues
jdk_jfr_0 => deep history 8/15 passed | possible issues
jdk_jdi_0 => deep history 4/5 passed | possible issues
Test_openjdk22_hs_sanity.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode)

jdk_foreign_0 => deep history 4/24 passed | possible issues
jdk_foreign_1 => deep history 4/23 passed | possible issues
Test_openjdk22_hs_sanity.openjdk_ppc64_aix_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode)

Test_openjdk22_hs_special.functional_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode)

MBCS_Tests_formatter_Zh_TW_aix_0 => deep history 9/23 passed | possible issues
MBCS_Tests_formatter_zh_TW_aix_0 => deep history 9/23 passed | possible issues
MBCS_Tests_formatter_ZH_TW_aix_0 => deep history 9/23 passed | possible issues
MBCS_Tests_i18n_ko_KR_aix_0 => deep history 12/23 passed | possible issues
MBCS_Tests_i18n_KO_KR_aix_0 => deep history 12/23 passed | possible issues
Test_openjdk22_hs_special.functional_ppc64_aix_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode)

Test_openjdk22_hs_special.functional_s390x_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

MBCS_Tests_formatter_zh_TW_linux_0 => deep history 9/19 passed | possible issues
MBCS_Tests_i18n_ko_KR_linux_0 => deep history 10/19 passed | possible issues
Test_openjdk22_hs_special.functional_s390x_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

Test_openjdk22_hs_special.functional_x86-64_windows ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

MBCS_Tests_formatter_tw_windows_0 => deep history 4/21 passed | possible issues
Test_openjdk22_hs_special.functional_x86-64_windows_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

x86-64_mac
Test_openjdk22_hs_extended.openjdk_x86-64_mac ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_x86-64_mac_rerun ✅ SUCCESS ✅
Rerun all
java -version
Test_openjdk22_hs_extended.openjdk_x86-64_mac_testList_1 ⚠ UNSTABLE ⚠
jdk_jfr_1 => deep history 0/1 passed | possible issues
jdk_security3_1 => deep history 0/1 passed | possible issues
Test_openjdk22_hs_extended.openjdk_x86-64_mac_testList_2 ⚠ UNSTABLE ⚠
jdk_net_1 => deep history 7/8 passed | possible issues
jdk_nio_1 => deep history 5/8 passed | possible issues

x86-64_linux
Test_openjdk22_hs_extended.openjdk_x86-64_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_x86-64_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
Test_openjdk22_hs_extended.openjdk_x86-64_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_tools_1 => deep history 0/3 passed | possible issues
jdk_build_0 => deep history 13/15 passed | possible issues
Test_openjdk22_hs_extended.openjdk_x86-64_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_build_1 => deep history 3/5 passed | possible issues

aarch64_linux
Test_openjdk22_hs_extended.openjdk_aarch64_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_aarch64_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
Test_openjdk22_hs_extended.openjdk_aarch64_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_net_0 => deep history 3/6 passed | possible issues
jdk_tools_1 => deep history 0/4 passed | possible issues
jdk_build_0 => deep history 29/31 passed | possible issues
Test_openjdk22_hs_extended.openjdk_aarch64_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_jdi_0 => deep history 1/5 passed | possible issues
jdk_jdi_1 => deep history 25/30 passed | possible issues
jdk_build_1 => deep history 3/5 passed | possible issues

aarch64_mac
Test_openjdk22_hs_extended.openjdk_aarch64_mac ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_aarch64_mac_rerun ⚠ UNSTABLE ⚠
Rerun failed
1 testcase https://ci.adoptium.net/job/Grinder/9462/parameters/

x86-64_windows
Aborted or failed
https://ci.adoptium.net/job/Test_openjdk22_hs_extended.openjdk_x86-64_windows_testList_1/3/
https://ci.adoptium.net/job/Test_openjdk22_hs_extended.openjdk_x86-64_windows_testList_2/3/
https://ci.adoptium.net/job/Test_openjdk22_hs_extended.openjdk_x86-64_windows_rerun/6/

ppc64le_linux
Test_openjdk22_hs_extended.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_ppc64le_linux_rerun ⚠ UNSTABLE ⚠

s390x_linux
Test_openjdk22_hs_extended.openjdk_s390x_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_s390x_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

Test_openjdk22_hs_special.functional_s390x_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

MBCS_Tests_formatter_zh_TW_linux_0 => deep history 9/19 passed | possible issues
MBCS_Tests_i18n_ko_KR_linux_0 => deep history 10/19 passed | possible issues
Test_openjdk22_hs_special.functional_s390x_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.0+0 (build 22.0.1)
OpenJDK 64-Bit Server VM Temurin-22.0.0+0 (build 22.0.1, mixed mode, sharing)

@sophia-guo the windows x64 tests now pass on the 2019 & 2016 machines.. ( https://ci.adoptium.net/job/Grinder/9610/ & https://ci.adoptium.net/job/Grinder/9594/parameters/ )

Regarding HeapDumpTestWithActiveProcess and JShellHeapDumpTest on win64:
The test will try to use windbg debugger tool to attach to another process. It may need admin permissions (or something similar) as it is currently failing to do that. Someone reported the exact same issue to the JetBrains runtime:
https://youtrack.jetbrains.com/issue/JBR-6288/sun-tools-jhsdb-test-fail-on-jre-w11-azr-agents-The-pipe-is-being-closed
The stacktrace to explore and understand would be:
Error attaching to process: Windbg Error: WaitForEvent failed! (hr: 0x80004002)
sun.jvm.hotspot.debugger.DebuggerException: Windbg Error: WaitForEvent failed! (hr: 0x80004002)
	at jdk.hotspot.agent/sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.attach0(Native Method)
	at jdk.hotspot.agent/sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.attach(WindbgDebuggerLocal.java:129)
	at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.attachDebugger(HotSpotAgent.java:636)
	at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.setupDebuggerWin32(HotSpotAgent.java:534)
	at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.setupDebugger(HotSpotAgent.java:366)
	at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.go(HotSpotAgent.java:337)
	at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.attach(HotSpotAgent.java:142)
	at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.start(Tool.java:203)
	at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.execute(Tool.java:134)
	at jdk.hotspot.agent/sun.jvm.hotspot.tools.JMap.main(JMap.java:202)
	at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runJMAP(SALauncher.java:340)
	at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:500)

I'd want to know what windbg hr: 0x80004002 means. I think the failure is in the windbg tool, and system configuration around that needs to be investigated.

Whilst digging around.. https://bugs.openjdk.org/browse/JDK-8204994

Whilst digging around.. https://bugs.openjdk.org/browse/JDK-8204994

Ah nice. This was a related fix for an intermittent failure (they now retry the attach 3 times), but it doesn't look like there was a clear understanding of the problem with Windbg. I think we're seeing it consistently on a specific machine while others are passing consistently too, right?

Whilst digging around.. https://bugs.openjdk.org/browse/JDK-8204994

Ah nice. This was a related fix for an intermittent failure (they now retry the attach 3 times), but it doesn't look like there was a clear understanding of the problem with Windbg. I think we're seeing it consistently on a specific machine while others are passing consistently too, right?

Yes, its working fine on the 2016, 2019 and ONE of the 2022 machines... but not on the other 2 2022 machines.


Manually updating channel handle/URL when renaming a channel

You may also change the channel URL (also known as the channel handle) when renaming a channel. The URL is not automatically updated to prevent unintentionally breaking existing links and integrations.

Seems a little expert mode, it might be more important to be clear that changing a channel URL it will break existing links (will it break webhooks and permalinks too?)
I don't think anyone expects the channel URL to change when the UI name changes. It would be like updating the site name and expecting the entire server URL to change.

Thanks, updated

+1

+1


[experimental] Attempt to unblock the ceph build process

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "ceph-build-fix" git@github.com:docker/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@RichardScothern Sign your commits.
LGTM once signed.

Current coverage is 57.04%

Merging #1432 into master will decrease coverage by -0.06% as of bf1398e

@@            master   #1432   diff @@
======================================
  Files          123     123
  Stmts        11362   11355     -7
  Branches       797     799     +2
  Methods          0       0
======================================
- Hit           6488    6478    -10
- Partial        797     799     +2
- Missed        4077    4078     +1

Review entire Coverage Diff as of bf1398e

Uncovered Suggestions

+0.29% via ...ge/driver/gcs/gcs.go#182...213
+0.24% via ...ge/driver/gcs/gcs.go#85...111
+0.22% via ...ge/driver/gcs/gcs.go#471...494
See 7 more...

Powered by Codecov. Updated on successful CI builds.

They are signed :joy_cat:


No issue, just another non-savvy question

Hi,
Sorry guys for posting a simple question with certainly an obvious answer for savvy users, but I'd appreciate a simple definition of the only option I don't understand included in dnscrypt-proxy.conf

Run the proxy as a background process
Unless you are using systemd, you probably want to change this to "yes"
after having verified that the rest of the configuration works as expected.
Daemonize no

So, daemonize is off by default. But what is daemonize to start with?
Point is, I'm running Windows 7, I don't even know what systemd is (is that a Linux setting?)
Logically, since I'm not running systemd (as I understand it) I'd "probably want to change this [Daemonize] to "yes" ...
I've left Daemonize to "no" and all is running smooth, yet I dislike ignoring things!
Thanks (again) for helping a newbie!

Hi!
No worries. Setting this to yes makes the server run as a background process on Unix.
It's ignored on Windows, so you can set it to anything you want :)
systemd is a long-lasting subject of trolling in the Linux world. You can safely ignore this as well :)

Thanks, @jedisct1 -- Now I get it (so to say!).
All is running smooth here with dnscrypt-proxy-win64-full-1.9.1 (just updated to 1.9.1, no major change for non-techies) and the dnscrypt-proxy.conf initiated with ver. 1.9.0 is a true user's friend.
All the best for 2017 (now that I "understand" daemonize and sysyemd!) :)


[stable/hlf-ord] Configure metrics

What this PR does / why we need it:
This PR enable the setup of a metrics server to get more insight of what is happening from an operational point of view.
Which issue this PR fixes
N/A
Special notes for your reviewer:
For the values names I replicated the structure and default values from the orderer.yaml file.
In the readme.md it was required to resize the columns generating a big diff, the relevant added lines are from L104 to L109.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @inzamam-iqbal

/lgtm


worker tries to create /pach directory; fails without root access

Usage of /pach directory was added to the user container within pipline RCs/pods (for caching hashtrees during the shuffle step). creation of this directory fails if the container isn't run with root permissions (eg on openshift). This directory should be created as a volume in the generated RC manifest, instead of being created in the worker code.
The same change was already made for the storage container. Details here:  https://github.com/pachyderm/pachyderm/issues/3404
This problem can be worked around by ensuring that any docker image used as a pipeline has an empty /pach dir added to it as part of the docker image authoring process

@pappasilenus Is this fixed already or something that users need to manually change in the manifest currently, but we should be fixing in pachyderm automatically?

@JoeyZwicker this is still an issue (was introduced some time around 1.8.4), and should be fixed in Pach. AFAIK this is the last issue that blocks us from claiming full OpenShift support

hi @gabrielgrant what's the status of OpenShift support now ? I followed the wiki to install pachyderm on OKD on-prime environment, but now failed to start pod/pipeline-edges-v1- with
    message: 'pods "pipeline-edges-v1-" is forbidden: unable to validate against any
      security context constraint: [spec.volumes[4]: Invalid value: "hostPath": hostPath
      volumes are not allowed to be used]'

is it related to the issue of here ?


Update sbt-microsites to 1.0.0

Updates com.47deg:sbt-microsites from 0.9.7 to 1.0.0.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.47deg", artifactId = "sbt-microsites" } ]

labels: semver-major

Codecov Report

Merging #1325 into master will decrease coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1325      +/-   ##
==========================================
- Coverage   85.84%   85.73%   -0.12%
==========================================
  Files          74       74
  Lines        2537     2537
  Branches      108      108
==========================================
- Hits         2178     2175       -3
- Misses        359      362       +3

Impacted Files
Coverage Δ

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
94.59% <0%> (-2.71%)
:arrow_down:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
92.77% <0%> (-1.21%)
:arrow_down:

...les/core/shared/src/main/scala/io/circe/Json.scala
78.18% <0%> (-0.61%)
:arrow_down:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
85.38% <0%> (-0.59%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
85.52% <0%> (+0.26%)
:arrow_up:

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 0426a0c...ef5b6c1. Read the comment docs.


Matching any argument in a mock using withArgs()

Please advise if there is a way to match anything in the list of arguments supplied to the Contract::withArgs method.

Do you mean sth like:
await expect(token.transfer(walletTo.address, 7))
  .to.emit(token, 'Transfer')
  .withArgs(/.*/, walletTo.address, 7);

There is currently no way to match any argument and we don't plan to add such a feature at this point.
It feels with smart contacts being deterministic and simple by design such a use case is not very common.
Closing for now, feel free to reopen if you would like to add more to the discussion.

@marekkirejczyk I also have a use for this. I am testing a contract that deploys another contract and then emits its address along with other data. I cannot test the event with the current .withArgs matcher.

@marekkirejczyk I also have a use for this. I am testing a contract that deploys another contract and then emits its address along with other data. I cannot test the event with the current .withArgs matcher.

I have now written a function in my code which extracts the event arguments in the same way as the withArgs matcher. I then all of the arguments except the one i don't know ahead of time.
I don't know if this fits within the chai philosophy, but a useful matcher would be something that extracted the arguments in the event and allowed the user to check them in more detail, possibly within a closure or something.

I have now written a function in my code which extracts the event arguments in the same way as the withArgs matcher. I then all of the arguments except the one i don't know ahead of time.
I don't know if this fits within the chai philosophy, but a useful matcher would be something that extracted the arguments in the event and allowed the user to check them in more detail, possibly within a closure or something.

I also do have a use case for such feature;
for example -- to mock uniswap router swap method -- deadline arg has to be set. Which will be equal to block timestamp at the moment of test execution, so is not deterministic.
Wildcard arg match in mock setup, would be sufficient to cover the issue.

The above examples should be enough to reopen this.


OneProvision GUI should only offer valid Providers

Description
Currently, it offers metal providers if user wants a "virtual" provision, and the other way round
Use case
User should be presented with options that ensures a correct provision deployment

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

PRs to merge:

one: https://github.com/OpenNebula/one-ee/pull/1565
doc: https://github.com/OpenNebula/docs/pull/2032


v2 convert range image to point cloud seems not right

I try to convert the range image to point cloud but it seems not right. The pipeline is as follows:

download the v2 dataset

specify the context

dataset_dir = '/media/alv-2/Rambo/Data/waymo/v2'
context_name = '15832924468527961_1564_160_1584_160'

load the frames

def read(tag: str) -> dd.DataFrame:
  paths = tf.io.gfile.glob(f'{dataset_dir}/{tag}/{context_name}.parquet')
  return dd.read_parquet(paths)

lidar_df = read('lidar')
lidar_pose_df = read('lidar_pose')
lidar_calibration_df = read('lidar_calibration')
lidar_segmentation_df = read('lidar_segmentation')
stats_df = read('stats')
vehicle_pose_df = read('vehicle_pose')

_, lidar_row = next(iter(lidar_df.iterrows()))
_, lidar_pose_row = next(iter(lidar_pose_df.iterrows()))
_, lidar_calibration_row = next(iter(lidar_calibration_df.iterrows()))
_, lidar_segmentation_row = next(iter(lidar_segmentation_df.iterrows()))
_, vehicle_pose_row = next(iter(vehicle_pose_df.iterrows()))

lidar = v2.LiDARComponent.from_dict(lidar_row)
lidar_pose = v2.LiDARPoseComponent.from_dict(lidar_pose_row)
lidar_calibration = v2.LiDARCalibrationComponent.from_dict(lidar_calibration_row)
lidar_segmentation = v2.LiDARSegmentationLabelComponent.from_dict(lidar_segmentation_row)
vehicle_pose = v2.VehiclePoseComponent.from_dict(vehicle_pose_row)

call the converting function to convert range image to points

from waymo_open_dataset.v2.perception.utils import lidar_utils
points = lidar_utils.convert_range_image_to_point_cloud(lidar.range_image_return1,
                                                        lidar_calibration,
                                                        lidar_pose.range_image_return1,
                                                        vehicle_pose,
                                                        False)

then the points seems to be in spherical coordinate

i wonder whether the data got wrong or the convert_range_image_to_point_cloud function is still under developing?
can somebody help me?

Hi @Rambo8248 ,
Thank you for using WOD v2. The cause of this issue is that rows in lidar, lidar_pose, lidar_calibration parquet files do not necessarily have keys following the same order. In this case, the first row in lidar_df has key with laser_name == 1, while the first row in lidar_calibration_df has laser_name == 2. Instead, the last row in lidar_calibration_df has laser_name == 1. I tried loading the last row in lidar_calibration_df and ran conversion and visualization, the result looks correct.
While investigating this issue, I realized that a fix is needed in this line. A hot fix is to change it into:
  if calibration.beam_inclination.values is not None:
We'll fix this line in the next commit coming soon.


VideoTile error in iOS Safari <=13.3

Describe the bug; what happened?
On iOS Safari <=13.3 the VideoTile component raises an error when rendered. This occurs with or without an active video stream. A similar error occurs when VideoGallery is rendered.
With newer version of iOS ( >= 13.4) this error does not occur.
What are the steps to reproduce the issue?
Simply place a VideoTile or a VideoGallery component in the render tree.
You can also notice an error navigating to the Local Preview sample page in the UI Library: https://azure.github.io/communication-ui-library/?path=/story/examples-localpreview--local-preview
What behavior did you expect?
VideoTile and Videogallery should render correctly.
If applicable, provide screenshots:

In what environment did you see the issue?

OS & Device: iPhone XS
Browser: Apple Safari
Version: <=13.3

Is there any additional information?

@m-muratori we are looking into the issue, will keep you posted.

@m-muratori could you please provide call id or browser/console logs for the occurring issue?

Thanks a lot for helping with the logs.
The exact problem encountered was:
[Error] ReferenceError: Can't find variable: ResizeObserver
	VideoTile (bundle.js:144838:85)
	renderWithHooks (bundle.js:355661)
	mountIndeterminateComponent (bundle.js:358423)
	callCallback (bundle.js:344611)
	dispatchEvent
	invokeGuardedCallbackDev (bundle.js:344660)
	invokeGuardedCallback (bundle.js:344720)
	beginWork$1 (bundle.js:364462)
	performUnitOfWork (bundle.js:363298)
	workLoopSync (bundle.js:363235)
	renderRootSync (bundle.js:363201)
	performSyncWorkOnRoot (bundle.js:362818)
	performSyncWorkOnRoot
	(funzione anonima) (bundle.js:352071)
	unstable_runWithPriority (bundle.js:375691)
	flushSyncCallbackQueueImpl (bundle.js:352066)
	flushSyncCallbackQueue (bundle.js:352054)
	scheduleUpdateOnFiber (bundle.js:362418)
	dispatchAction (bundle.js:356787)
	dispatchAction
	(funzione anonima) (bundle.js:3030)
	asyncFunctionResume
	(funzione anonima)
	promiseReactionJob

The problem is that we depend on ResizeObserver, which supposedly works iOS 13.1+:  https://developer.mozilla.org/en-US/docs/Web/API/ResizeObserver#browser_compatibility
But MDN is sometimes off about exact browser versions that implement an API. Your experiments show that this isn't working for 13.3-.
But turns out that Azure Communication Services Calling SDK only supports iOS 15+, so you'd still not be able to use iOS 13.1 (even if we were to find a workaround for ResizeObserver.

I'll close once we've updated our documentation to correctly reflect supported versions (drop stale reference iOS 13, link to actual modality documentation).


[Fix] Switch - lagging animation

Investigate why the switch animation is sometimes very laggy (seems it is not on every instance)
https://github.com/adevinta/spark/assets/2033710/5280cfa2-0e04-4ce5-8972-88107593b650

Close as not reproductible.


Wrong blocks tags/id with other mods (v1.10.4)

Hello,
I play with a decently large modpack and noticed at some point after updating mods that my friends were experiencing issues. It seemed like blocks had ID mismatches or something, causing them to appear as waterlogged or as entirely different blocks for them, but normal for me (since I play singleplayer and open the world using Essential when they have time to play).
The issue is reproducible for me with only Fabric API, SIHYWTCAMD, and Wilder Wild. If you join a random server (I used Hypixel), you will notice some crazy stuff happening. I have not tried reproducing on a fresh install, so it's probably a lost cause if you cannot because I had over 100 mods at some point lol.
I will also be reporting this issue to the Wilder Wild repository.
Thank you!
PS: Love the mod, and appreciate the work you put in!

latest.log

Hi, thanks for the report! This looks like the same issue than #56. The player just updated other mods and it seemed to fix its issue. I will try to reproduce with wilderwild though to know if there is something more

Hi, I've done a little bit of testing. I didn't reproduce on singleplayer but I did on server. However, I encountered the issue only when I had Wilder Wild installed. Difficulty only did not seem to create block mismatches (maybe it did but as I add only one block, maybe only one is mismatched). Anyway, I think the issue you're having with your friends is that you're not playing with the mods setup in terms of mods adding new blocks, either missing mods or different versions. Can you confirm?

No, we all play with the same mods using my GitHub repository found here: https://github.com/Toimis/MC1.21
And this batch script I made with AI lol
update2.txt

If you join a random server (I used Hypixel), you will notice some crazy stuff happening

Content mods change the registered blocks and renderers. If you join a non-fabric server that does not sync that data (like hypixel), then your game will render blocks incorrectly. This is why mismatched mod versions can cause the issue as well. This is not an issue with this mod nor wilder wilds, its a problem with trying to use mods on servers with different or missing mods

This is not an issue with this mod nor wilder wilds, its a problem with trying to use mods on servers with different or missing mods

I was having this issue even with my friends, who sync their mods completely the same though? Is it because of something with Essential hosting? I'm going to start using Aternos or port-forwarding so I'll see what I can find out, but everyone else stopped playing

Having client-side mods is not the issue. As we both mentioned, the issue should come from different (server) mods registering new blocks and/or different configs. If you all have the exact same configs for the exact same (server) mods, then the issue might come from Essential that doesn't sync properly the data when opening the multiplayer.

Okay, so I was able to get my own server running that I port-forwarded, hosted on my laptop, and joined on my desktop. I tried with and without Essential mod, and it made no difference.
I still have the issue, even without Wilder Wild installed. However, WW was the only one that exhibited the issue on random servers, like Hypixel. Even with Biomes O' Plenty installed, I didn't see anything odd on the Hypixel server.
I'm guessing WW changes the registry/ID for an early entry, but SIHYTCAD will probably be incompatible with any mod that adds (a lot of) blocks.
Most importantly, this issue only occurs with SIHYWTCAMD 1.10.4. I reverted to 1.10.3, and didn't notice any problems. If I had to guess, it probably has something to do with porting to 1.21.1, but I haven't tested anything on that version of Minecraft.
I have attached the logs (hopefully they're the right ones), but it may be more helpful to just reproduce it, or even to just mark 1.10.14 as incompatible with 1.21.
Thanks for your help.

I don't know how you setup your server, but you're either doing it wrong or not installing only Difficulty and Biomes o Plenty. I did the test again and it works perfectly fine when joining a Fabric server that has the same mods and config than the client.
The 1.10.4 version is absolutely not incompatible with 1.21 as it was made for this version. Minecraft 1.21.1 has nothing to do with it, it's just a minor version that only added a hotfix for an important bug.
Feel free to share your server setup here, so I can eventually tell you what's wrong and/or understand the issue, as I can't reproduce it for now

Keep me in touch :)

Sorry for the lack of progress, but my friends stopped playing Minecraft, so I did too. If I come back to it sometime, I will probably be using your mod again and I'll let you know if I have any issues then since many mods will be updated then.
Not sure if anyone else is having this particular issue with 1.10.4 in 1.21, so you can keep it open to see if anyone else replies or you can close it. Thanks for your help anyways!


fixing like button animation

I decreasse keyframe, and add more duration for animating like button, I try to make it simple.. how do you think ?

Issue:

You're right this looks much better. Thank you!


Create Jenkins Runs Queued Time Report on Roslyn Dashboard.

Copied from work item #234600.
•       Jenkins Runs Queued Time Repot
•           Design and add a report to illustrate queued time of Jenkins jobs/runs.
•           This report can be either standalone, or integrated with the elapsed time report.

Completed.


Design

https://www.figma.com/file/mAikJIh2S6iSzYCn0dgGl9/Untitled?node-id=0%3A1

https://www.figma.com/file/mAikJIh2S6iSzYCn0dgGl9/Untitled?node-id=0%3A1

Pretty epic


updated meta desc to match new feature

we no longer are able to select how many lines
#byefreedom

📝Changed routes:

/

(view full size)

Commit 96b2a29998b6bd1a965b2d37549a2351ff115069 (https://randomcodegenerator-lol-hsc976oss-whitep4nth3r.vercel.app).


chore: make OAuth URL more explict

This shall clearly indicate the user must specify the token URL, not the auth URL or something else:

Related to #3808, proposed via this comment.

I like the change!
How'd you get the error message over the OAuth Token URL  part though? whenever I put in invalid oauth urls, it just tells me the zeebe-gateway url is the problem.  Has a recent PR helped with that validation?

Has a recent PR helped with that validation?

No. We'd want to revisit this and also mark the OAuth token URL as (potentially) invalid.


[T2A2][C01-A1]Lim Shun Xian

Extract method processUserCommand()

Ready for review

@Crsytral Some comments added. Please close the PR after reading comments.


Pretty print webaction JSON response.

Fixes #2635.

cc @dubeejw

@dubeejw we can combine this with your pr if e want to restore full pretty printing of json responses. I would actually do something slightly different in that case.


Sprite composition

Similar to #105, the idea is to remove optional pieces of the code that not every sprite needs, such as rotation, anchor, velocity, acceleration, etc.. Then create a composition system that would let you add these pieces back into an individual sprite (or the entire Sprite class) when you need them.

So the composition system doesn't really save bytes in the end since it requires a bit of boilerplate to setup. Instead, I think we should just create a build script that you pass the optional things you want from the Sprite class and it then generates the output. This should ensure there's no boilerplate and you only get exactly what you want.

Alright, a PR for this is up https://github.com/straker/kontra/pull/131. The sprite now has preprocess comments around all the extra functionality. Using a new rollup plugin https://github.com/straker/rollup-plugin-kontra, you can pass it the configuration you want to enable in the Sprite class and it will remove everything that isn't enabled.
This should let you fine tune the output to exactly what you need.

Closed vi #131


Is batch processing possible during inference?

Hi, thank you for providing a pre-trained model. I am wondering if it is possible to perform a batched prediction with the model at https://huggingface.co/RUCAIBox/mtl-data-to-text ? Something like below?:
inputs = tokenizer(
    ["Describe the following data: Iron Man | instance of | Superhero [SEP] Stan Lee | creator | Iron Man",
     "Describe the following data: Batman | instance of | Superhero",
    ]
    return_tensors="pt",
)

generated_ids = model.generate(**inputs)

tokenizer.batch_decode(generated_ids, skip_special_tokens=True)
['Iron Man is a fictional superhero appearing in American comic books published by Marvel Comics.',
"Batman is a superhero"]

Sorry, I am a little confused about your requirements. Does this code have an issue and does not solve the batch prediction?

Ah, sorry for the confusion. I was wondering how I can use the pre-trained model to process a set of input at the same time. As an example, let's say I have these two texts as input:
t1='Describe the following data: Love Is Mighty Close | INSTANCE_OF | album [SEP]'
t2='Describe the following data: Iron Man | instance of | Superhero [SEP] Stan Lee | creator | Iron Man'

And I'd like to make MTL-data-to-text model describe both t1 and t2 at the same time instead of doing the following:

tokenizer = MvpTokenizer.from_pretrained("RUCAIBox/mvp")
model = MvpForConditionalGeneration.from_pretrained("RUCAIBox/mtl-data-to-text")
# T1
inputs = tokenizer(t1, return_tensors="pt")
generated_ids = model.generate(**inputs)
tokenizer.batch_decode(generated_ids, skip_special_tokens=True)
# T2
inputs = tokenizer(t2, return_tensors="pt")
generated_ids = model.generate(**inputs)
tokenizer.batch_decode(generated_ids, skip_special_tokens=True)

Does the current codebase support this?

inputs = tokenizer([t1, t2], return_tensors="pt")
generated_ids = model.generate(**inputs)
tokenizer.batch_decode(generated_ids, skip_special_tokens=True)

Does this satisfy your requirements?

Thanks for reply. I've tried what you shared above. It throws this error:
>>> inputs = tokenizer([t1, t2], return_tensors="pt")
Traceback (most recent call last):
  File "/opt/conda/envs/py38/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 717, in convert_to_tensors
    tensor = as_tensor(value)
ValueError: expected sequence of length 20 at dim 1 (got 24)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/conda/envs/py38/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 2520, in __call__
    encodings = self._call_one(text=text, text_pair=text_pair, **all_kwargs)
  File "/opt/conda/envs/py38/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 2606, in _call_one
    return self.batch_encode_plus(
  File "/opt/conda/envs/py38/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 2797, in batch_encode_plus
    return self._batch_encode_plus(
  File "/opt/conda/envs/py38_/lib/python3.8/site-packages/transformers/tokenization_utils.py", line 737, in _batch_encode_plus
    batch_outputs = self._batch_prepare_for_model(
  File "/opt/conda/envs/py38_/lib/python3.8/site-packages/transformers/tokenization_utils.py", line 817, in _batch_prepare_for_model
    batch_outputs = BatchEncoding(batch_outputs, tensor_type=return_tensors)
  File "/opt/conda/envs/py38_/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 210, in __init__
    self.convert_to_tensors(tensor_type=tensor_type, prepend_batch_axis=prepend_batch_axis)
  File "/opt/conda/envs/py38_/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 733, in convert_to_tensors
    raise ValueError(
ValueError: Unable to create tensor, you should probably activate truncation and/or padding with 'padding=True' 'truncation=True' to have batched tensors with the same length. Perhaps your features (`input_ids` in this case) have excessive nesting (inputs type `list` where type `int` is expected).

Yes, it works. Oddly enough, I tried this before I created the problem, but it didn't work then. Anyway, thank you. I'm closing the issue.


Simple example app using Webpack

adds a simple example... It appears that Git is adding it as a subproject or something, so I may be doing something weird here with my pull request...
If so, I put the example here as well:
https://dl.dropboxusercontent.com/u/274922/photon_kit_example.zip
And you can just download it from there ;-)

Thanks for your example. It would be helpful. However, direct link out from the project is not properly as I think. we will make a new way to share some of tips or codes like recipes


Investigate OAS/Swagger generation of client

On the V4's documentation page, there are links to OAS / RAML specs for the API. We could generate a lot of code from these specifications, and then code the few differentiations there are for an actual client (overloads and whatnot) -- I imagine we'll also encounter cases where two responses/requests use the same object, but where the spec specifies different objects.
However, currently (was also the case last I tried swagger on this) the spec is incomplete or invalid: https://www.themoviedb.org/talk/58691a749251414e7500c442

The current OAS specs seem incomplete. For Movie f.ex., there are non of the "append_to_response" methods available as properties, so if we generated it from that, we would be missing those.
I suppose we could post-add those specifically, using partials.


feature request: find and replace

Hi,
I would like to suggest a feature.
Find and replace by string or hexadecimal.

There is a replace field for the Ascii search type, but it's missing for others.
I agree it should be available for more search types.


Can the script work with relative paths?

Here is my issue, in my JSP file where I need to add the cache busting - the JS includes are pointing to the relative path:

But the script will only work if I put in the full absolute path:

Is there any way around this?

This should have been fixed in #108


Add handle of Http Status Code

Hello,
I've added the handle of http status code. If the code is greater than 300, the request is processed as an error.
Please review my code. I' not sure about the argument to pass to the 'callback' function in that case.
Regards,

Thx @macjl for code 300 managment. Code is now on npm<EMAIL_ADDRESS>