1.6.9 breaks older version of Node

@Atinux When upgrading dependencies from 1.6.8 to 1.6.9 (Async), this module breaks for older versions of Node.
While I understand the changes, to indicate a lack of support for Node versions, you need to update a major version to not mess with semver and default installation to take latest minor version.
Ultimately 1.6.9 should have been published as 2.0.0 dropping support for < v8

@Atinux Here is a snippet of the error. For this project, I just had to lock it at 1.6.8. Unfortunately, we are working on Node 4, but we are upgrading to 10 (and hopefully 12). It is just a slow process...
    function apply(fn, ...args) {
                       ^^^
SyntaxError: Unexpected token ...
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at /home/mudrekh/dev/scratch/node_modules/schema-inspector/lib/schema-inspector.js:9:49
    at Object.<anonymous> (/home/mudrekh/dev/scratch/node_modules/schema-inspector/lib/schema-inspector.js:1577:3)
    at Module._compile (module.js:409:26)

Basically, that version of async uses spread operators which aren't available in Node 4.

Also it stoped working for IE11, can be find here: https://caolan.github.io/async/v3/
"If you want to use Async in an older environment, (e.g. Node 4, IE11) you will have to transpile."

Oh dammit, sadly I don't have time anymore to maintain this module. If you guys want to tackle this and become a maintainer, I am open to it 😄

@Atinux From what i see there is no transpiling process, can I downgrade the async version to 2.6.2?

Yes you can!

We actually noticed this requirement to transpile and just changed our build process to transpile using Webpack and Babel. We set the Babel config to include files in node_modules. I see nothing wrong with that requirement, to be honest. It makes sense that you'd ship modern code and let people transpile down to old code if their use case requires it.

This is on hold. I wasn't happy with my build since I was only able to get it to work with the "useBuiltIns": "entry" setting, which brings in the entire polyfill. The best way to do it would be with the "useBuiltIns": "usage" setting, but I wasn't able to get the build to work that way. It doesn't seem to bring in the polyfills correctly.

@mattwelke I totally agree with the fact that we should change the build process to transpile using Webpack and Babel.
But the patch upgrade from 1.6.8 to 1.6.9 introduced a breaking change that should no happen, that is why I was suggesting to downgrade the async to 2.6.2.
The change in the build process should happen on the major, or at least on the minor version.

It's funny you mention the breaking change idea. We had the same discussion at our work and we concluded that it wasn't necessary to bump the major version even if one of our dependencies included ES6 code, therefore breaking some build processes. We considered the semver version to relate to the API of schema-inspector, not its build process.
We were going to communicate to our consumers that if they weren't already testing their builds in browsers like IE, they should now because we're now aware of one of our dependencies shipping ES6+ code.
However, this is the open source world so we'll have to figure out our own way to move forward.
Is it appropriate for schema-inspector's maintainers to commit to testing builds of it in all browsers so that they can be made aware when one of its dependencies starts including ES6+? The library description describes it as meant to be used in the browser and on the server. So, to me, this seems reasonable.
Let's consider some consequences of going this route though. If we did, there would be a few ways to implement this:

Increment the major version of schema-inspector and keep it on the latest version of async (and then, do we drop support for 2.x.x or maintain support for both major versions, doing multiple releases as necessary forever)
Roll back async to when it used only ES5 code and keep it there, accepting the risk of not being able to update a dependency
Replace usages of async code with our own ES5 code

We considered the semver version to relate to the API of schema-inspector, not its build process.

I see 🤔But you agree that a minor version should not break the out-of-box support of the  Node 4 version or older browsers, so it can be identified as breaking change. I think that we just need to align on the goal.
Just consider the following, if we don't transpile and release ES5 code, Schema Inspector needs to reference that will drop the support for older browsers and node versions. I don't think that we want that.
My suggestion would be the following:

Release 1.6.10 - Rollback async to when it used only ES5 code with Async 2.6.3 (For now is fixed)
Moving forward release 2.0.0, introduce a build process and transpile the Async Code that bundles the code (drop previous version support)
Or stick with Async version 2 while we see that is still being supported.

But you agree that a minor version should not break the out-of-box support of the Node 4 version or older browsers

Agreed. What makes sense to do right now is fix the semver violation. The steps you outlined make sense for that.

My suggestion would be the following:

Release 1.6.10 - Rollback async to when it used only ES5 code with Async 2.6.3 (For now is fixed)
Moving forward release 2.0.0, introduce a build process and transpile the Async Code that bundles the code (drop previous version support)
Or stick with Async version 2 while we see that is still being supported.

Agree with doing 1 and 2. 3 seems unwise. May as well fix it now.
Note that, like I said above, transpiling the code from the async dependency will not fix the problem for<EMAIL_ADDRESS>consumers who get it via NPM. It will only fix the issue for those who get the complete bundle build from the CDN. Let me know if you have any questions about how I'm coming to this conclusion. I can share example repos demonstrating how depending on schema-inspector 1.6.9 via NPM, even though it has no ES6+ code, still causes my own bundle to fail in EI (because of the transitive depenendencies with ES6+ code, async in this case).

@jcdesousa Looks like<EMAIL_ADDRESS>will be supported long term with IE support: https://github.com/caolan/async/issues/1661
That might be the quickest solution here. Sounds like we can just change to using the 2.x.x branch of async, do a patch release, and not even worry about ES6+ code until further notice.
(side note, I got my Babel working to transpile it for IE without including the whole core-js polyfill 🎉 but I'm glad others won't have to go through that pain if we just use<EMAIL_ADDRESS>)

Fixed in #80 and released in https://github.com/Atinux/schema-inspector/releases/tag/v1.6.10
Thank you @mattwelke


Final changes for glvis-4.2

This will be the last PR to be merged before the glvis-4.2 release.
Release date
~April 21st, 2022 (Thursday)~
May 20th, 2022 (Friday)
TODO

[x] Merge https://github.com/mfem/github-actions/pull/6
[x] Merge needs https://github.com/mfem/mfem/pull/2973
[x] Merge #230
[x] Merge #229
[ ] Update glvis-js and glvis.org/live

Postponed

Merge https://github.com/GLVis/glvis/pull/205
Addresshttps://github.com/GLVis/glvis-js/issues/15

I added the Markdown version of the README in this branch, see https://github.com/GLVis/glvis/blob/glvis-4.2-dev/README.md. Let me know if you have any suggestions for improvements.
ping: @v-dobrev and @pazner

This is now a release candidate for glvis-4.2, please review and speak up if you'd like to see any changes.

Can I get some reviews/approvals for this please?


Issue #1231: ROB3RTA integration.

Description
This PR implements the following changes:

refactor current BOB3 into NIBO:

add NIBOCommonCppVisitor for BOB3 and ROB3RTA.
rename IBob3Visitor to INIBOVisitor.
rename IBob3CollectorVisitor to INIBOCollectorVisitor.
update imports for Bob3CppVisitor, Bob3UsedHardwareCollectorVisitor, Bob3UsedMethodCollectorVisitor.

add rob3rta to robot.whitelist.

add blockly changes for rob3rta.

update compiled blockly resources.

add compilation case for rob3rta in ArduinoCompilerWorker.

add rob3rta specific files:

rob3rta.properties
rob3rta/program.toolbox*.xml
Rob3rtaCppVisitor, Rob3rtaCxxGeneratorWorker

update test for BOB3 (math.cpp).

add tests for rob3rta:

update testSpec.yml.
add astGenerated, collectorResults and targetLanguage files.
add test xml files.

update mmcu to atmega328pb for rob3rta.

add new tests for rob3rta:

pintouch-all-leds-if
pintouch-all-leds-wait-until
random-leds

add support for rob3rta in openroberta-connector app.

Fixes #1231
Related branches: blockly, arduino-resources and openroberta-connector
Type of change
Please delete options that are not relevant.

[X] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Run integration tests successfully.
New tests for rob3rta integrated and tested successfully.
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules

Rebased and merged with https://github.com/OpenRoberta/openroberta-lab/commit/896d4ff8ca1a7110d7aa9903e798c48c67fb0c9d


Card extensions should manage their own data

Remove from DataCard anything that belong to card extensions.
Each extension should manage its own tables , with no impact on core data.
Move extensions to their own packages .

All done, except card member extension.


Cityscapes to COCO inefficiency

I was looking into tools/cityscapes/convert_cityscapes_to_coco.py implementation, and found out that in L167 it is loading a json of already computed polygons to read the metadata and find the binary mask of the corresponding entry to convert them to polygons AGAIN, in tools/cityscapes/instances2dict_with_polygons.py.
Why is it necessary to recompute the polygons?

To be frank, I don't know.
That file was taken as is from Detectron in https://github.com/facebookresearch/maskrcnn-benchmark/pull/232 by @henrywang1 , and I didn't actually reviewed that part of the PR, given that it was taken from Detectron.
If you see optimization opportunities there, feel free to send a PR!

Hello @botcs as I understood from the code it is used to read the height and width of the image. You can replace that step by cv2.imread or lycon.load to get the height and width of the desired image.
Hope this helps :slightly_smiling_face:

I am currently refactoring the structures/segmentation_mask.py and once it is done, it should be a choice whether the user wants to use the binary masks or the polygons from CityScapes.

If you see optimization opportunities there, feel free to send a PR!
Let me clarify: we download the masks and polygons both with the original dataset - and then we take the masks to generate polygons again. One possibility for this could be that this was some legacy code, maybe the polygon annotation feature was just added later. But that would contradict that the author of this piece of code already knew about the polygon annotation since it reads in the whole file just to check the width and height of the image. Thankfully this stuff goes offline but still its existence is intimidating


Public methods are not accessible; not a function

I cannot call the public methods in version 1.5.0
"Uncaught TypeError: slider.slickPause is not a function"
"Uncaught TypeError: slider.slickPlay is not a function"
Version 1.5.0
http://jsfiddle.net/bu94scu3/2/
It works in 1.3.2
http://jsfiddle.net/bu94scu3/3/

Commenting here as this is the first search result for slickPlay is not a function. and it's easy to get lost in such a simple issue
Since version 1.4.0, the way to call all methods is:
$("#something").slick('slickPlay');
and no longer
$("#something").slickPlay();


Provide a runtime per service/application

 Issue by erandidesilva
Sunday Feb 19, 2017 at 21:58 GMT
Originally opened as https://github.com/ballerina-lang/composer/issues/1002

Currently the run functionality is global to the composer and there is no capability to individually run a service and application at the same time. The reason is the running mechanism is global to the composer (composer is bind with single runtime)
By using separate run times for the services and applications that is developed through composer will provide better usability for the user.

 Comment by hevayo
Thursday Mar 23, 2017 at 05:32 GMT

+1 This will help to debug integration scenarios involving multiple bal services.

Closing the issue since this is no longer valid


Normalized public_bookcase Editor with Wiki Page.

Normalized public_bookcase Editor with Wiki Page and add some useful fields from my own experience in mapping public bookcases.

@ToastHawaii Thanks! For your localization change to be permanent you'll have to change the string on Transifex.


Question: what is the difference between the “tolerance” parameter for velocity models and the “pick_match_tolerance” parameter for the OctoAssociator class?

Based on the descriptions in the document and the example, it seems that both tolerance and pick_match_tolerance refer to the maximum allowed difference between the observed and predicted arrival time. Are they the same?
Thank you for providing this amazing package!

Hi @zhong-yy,
indeed, this is a little confusing, but the parameters are different. The 'tolerance' of the velocity model is the allowed deviation from the predicted travel time when checking if a pick could originate from a volume. The pick_match_tolerance is for the step of matching picks to the origin, i.e., when PyOcto checks which picks are consistent with an origin. In most cases, you'll want to use the same parameters for both values, but it sometime might make sense to choose different tolerances for the search and for the matching step.


Bleeding Italics

I see these italic bleeds quite often, can we find them all with a pattern match on the latex?
also some typos

yes indeed we can let the robots turn \em{foo} into {\em foo} for us! thanks!

or better yet, we can turn \em{foo} into \emph{foo}!


Set correct phase when re-importing modules

The phase number from the modules spreadsheet was getting overwritten with a
hardcoded value when importing a module that already existed in the database.

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

#2170
#2169
#2168  👈
#2167
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite

Merge activity

Jul 17, 4:55 PM EDT: @sgrimm merged this pull request with Graphite.


Release on GitHub

Would it be possible to release tags on github as well as pypi? It would help some with the conda packaging.

Seconded, would help with any type of packaging!

Seconded as well!


User not visible in list even after voting up or voting down

Describe the bug
If a user votes up or votes down a story the voter count updates but not the follower list.
To Reproduce
Steps to reproduce the behavior:
1.Login into userstory
2.Visit a story
3. See the list of followers
4. Vote up or Vote down that story
5. Again see the list of followers
Expected behavior
The follower list should be able to update after voting up or voting down.
Environment (please complete the following information):

OS: Windows
Browser: Google Chrome

Additional context

Hi @codetheorem, There is an empty white modal showing at the top of the modal of the 'Voters for this story in the issue's image. while it is not shown on my side. I am just curious about it.

Hi @codetheorem, There is an empty white modal showing at the top of the modal of the 'Voters for this story in the issue's image. while it is not shown on my side. I am just curious about it.

It is not present there, it is just because of the extension that took the screenshot.

oh okay, Thank you.


feat: replace broadcaster's account retriever to use chain's bech32 prefix when converting AccAddress to string

Closes #1008
This PR adds a custom implementation of the AccountRetriever (copied from auth module) which is modified to convert an AccAddress to string using the target chain's bech32 prefix.

@madrezaz The latest main needs to be merged in then this is good to go :)


Comments created under account of PAT token

Describe the problem
I have cloned the repository and am on the master branch. So I have the latest version as of today.
I did export a single issue from Jira and imported it into Azure DevOps, to test the functionality.
The configuration is defined as follows:
config-agile.json.txt
I checked open/closed issues and found this one to be very similar to my case: #547
When checking the work item's History tab, I see the following:

This result is the same as what was shown by @Alexander-Hjelm where the History tab shows it all properly.
To me this seems to be fine.
Now, when looking at the work item's Details, there is where I see the issue with the comments:

The history shows that the "MB" user has added a comment, but the comment was actually added by my account.
When checking the exported/imported JSON issue, we see this in the revision:

I blurred out the user, but it is the MB user.
While debugging I see it is added to the API as one of the patch documents:

I have not seen in the issue mentioned above whether it is expected behaviour that the comments itself (so not the history) are created by the account behind the PAT, and not as mentioned in the history tab.
Tool version

Commit 4da119b91ce8b34388521c549700e8e6dbc62eed

@VincentVerweij, try the solution here: https://github.com/solidify/jira-azuredevops-migrator/issues/443

Hi @VincentVerweij ,
I am using the latest version from master.
I think the fix has been merged to master branch but not yet released with an official version.
If you download the latest code on your device, build and run; you should be able to have it working ;)

OK! Good catch :)
It will be worth looking into. I'll create a separate issue for compatibility with the New Boards Hub update. Once the feature goes public, it's likely that this issue will resurface again.


[1|CBH - New Article Post] Breadboard

 🍰 Appetite 🍰

Property
Value

Points
3 points

Difficulty rating
★★☆☆☆

Maximum Assignees
2 person

🤔 Problem Statement
Make a breadboard for each screen in the fat-marker sketch. Every place and affordance should be accounted for, but don't focus on making it look pretty. This should be essentially a bare HTML file, with no JS, and only CSS if required for basic layouts. Implement fake navigation and interactions using normal <a> tags. This purely for getting an interactive "skeleton" up, and seeing in real life whether this design would work, or has any major problems.
Please see this page for more info on what your breadboard should be like (and, if you want understand the fat-marker sketch and places affordances drawing better, please see this page).
🧪 Required Tests
None (but the Code Wizard will review whether or not your code warrants some tests! Review the Code & Testing Guidelines for more info)
⚠ Careful about:
🤖 Technologies focused on in this feature

React
Tailwind
Shadcn

@Builder-s-League/puma  assign me to this task please and Tyson

Hey, I would like to work on this one @Builder-s-League/puma

@khnatiuk
Closing this issue for housekeeping purposes.


[core] Remove outdated babel proposal plugins

Close https://github.com/mui/material-ui/issues/36794

[x] I have followed (at least) the PR section of the contributing guide.

https://deploy-preview-36795--material-ui.netlify.app/

Why the CircleCI failed by you may have revoked the CircleCI OAuth app...

Hi there?

This seems to break Safari compatibility: https://mui.com/material-ui/getting-started/supported-platforms/#browser, or at minimum the CI is always red now

https://app.circleci.com/pipelines/github/mui/material-ui/97978/workflows/05b23843-04a8-4c78-950c-e64963c5473d/jobs/521556

These test run on Safari 13.1.2, which we do not support.
I'll update the pipeline to use the browsers we claim to target.

We run the browser tests in master branch on Safari 13.1.2, while in the documentation we mention to support Safari (macOS) >=14. Also in .browserslistrc it is 14. There is a discrepancy. Also, to catch such issues, should we run tests in the Safari browser on other branches apart from the master branch as well?

Also, to catch such issues, should we run tests in the Safari browser on other branches apart from the master branch as well

Agree. They should be run on PRs to be visible. @oliviertassinari, would it significantly impact us financially if we enabled BrowserStack tests on each PR?

One thing that could work is to run it based on a modulo of the PR number. Like for 1/3 of the PR and see how it goes. But then, we need a way to run it on a case by case for PRs, e.g. for PRs like this one.

How about we enable BrowserStack on all PRs (and perhaps disable them on master) and see what is the impact, then we can adjust if necessary?

How about we enable BrowserStack on all PRs (and perhaps disable them on master) and see what is the impact, then we can adjust if necessary?

@michaldudak This is how we used to do it in the past. No objections. I'm not aware of fundamental changes that would make it work this time, so I think it's great to fully experience the problem, as a first step toward a clean solution.

It does not seem that the object-rest-spread polyfill is functional after this merge. Here is a diff from the npm package between 5.12.3 and 5.13.1. This affects @mui/utils and @mui/private-theming which I now have pinned in my project.

@gmferise Note that this PR was released in v5.13.1. Then it was reverted with #37331 but only partially released with v5.13.2, as you pointed out, not all the packages were released. Are you facing a specific problem?

@oliviertassinari It did cause me some issues, but I was able to work around them. My understanding was that this PR removed the plugins because the resulting polyfills were already included / could be enabled without them. I thought the extra info that object-rest-spread is not functional would help to fix the Safari compatibility.


body, button, input, select, textarea

The lines that go body, button, input, select, textarea should be html, button, input, select, textarea.
This way styles on html will overwrite normalize.css.

Should you add select option there as well? Safari doesn't change the font of closed a select box but using select option you can normalize the font in the open dropdown.

Thanks Jon, good call!


add ui for changing riding detection settings

What You mean by 'riding detection' settings? Enabling multiple sensors for example GPS, accelerometer? Or You thought of kind of algorithm mixing it up?

riding detection settings means parameters of algorithm which decides if user is riding on motorcycle or not.
this milestone means adding ui for changing those parameters for example speed on which we are sure that user is riding or acceleration value where we assume that user is riding. or settings like "assume unlocked phone as not riding etc"

done


Add private LRO methods for grow-up story

@AlexanderSher, what issue is this responding to?

https://github.com/azure/autorest.csharp/issues/2050
https://github.com/azure/azure-sdk-for-net/issues/28125

Discussed offline. It is possible that private methods won't be needed when next version of Azure.Core is released and suppress nested scope functionality becomes available.


Error messages for get and set index

This PR adds error checks for calls to ITensor getindex and setindex! with the wrong number of index values.

Fix erroring tests
Dimension checks for ITensor get and set index
Extra check and formatting changes
Add tests and checklist entry on formatting

Maybe better to use dispatch here to ensure there isn't any runtime overhead, for example:
@propagate_inbounds @inline function _getindex(T::Tensor{<:Any,N}, ivs::Vararg{<:Any,N}) where {N}
  # Implementation
end

and then define a fallback version:
function _getindex(T::Tensor, ivs::Vararg{<:Any,N}) where {N}
  throw(
    DimensionMismatch("$N index values passed to ITensor getindex, expected $(ndims(T))")
  )
end

Ok good idea - I can definitely do it that way instead.
So the failing tests include some involving something like T = emptyITensor() followed by T[i=>1,i'=>1] = 1.0 or similar. Are we planning to continue to support this behavior post 0.2? I guess we are at least going to allow empty ITensors to be a "universal zero for addition" but that does leave the separate question of setting elements.

Actually it looks like the test was supposed to give an error, but now the error is different so just needs to be updated to DimensionMismatch from MethodError: https://github.com/ITensor/ITensors.jl/blob/f55d05fa4075521e88eacb648d6012a49ef3aa80/test/empty.jl#L49.

Not sure what the status of T = emptyITensor(); T[i=>1,i'=>1] = 1.0 will be, I would be in support of adding that.


Add support for Typescript's nodenext module resolution

See: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-7.html#packagejson-exports-imports-and-self-referencing
For packages that define exports, the new typescript module resolution mode checks there for type definitions. This change will allow the existing type definitions to be discovered by packages using this mode.

Thanks for the PR. Sorry that I didn't merge this earlier, I've just completely missed it. It will be published after updating some of the dependencies and other minor modifications.


Implement retrieve file content endpoint

Closes #15

I've changed all occurrences of ...Endpoint to ...Uri but still have some doubts if we really need to explicitly include that in a variable/method name. Shouldn't type speak for itself? All of them are URIs and we refer to them by calling OpenAIUris.cancelFineTune(id) so how about something like that:
private object OpenAIUris {
  private val ImageBase: Uri = uri"https://api.openai.com/v1/images"
  private val AudioBase: Uri = uri"https://api.openai.com/v1/audio/"
  // ...
  val ChatCompletions: Uri = uri"https://api.openai.com/v1/chat/completions"
  val Completions: Uri = uri"https://api.openai.com/v1/completions"
  // ...
  def cancelFineTune(fineTuneId: String): Uri = FineTunes.addPath(fineTuneId, "cancel")
  def deleteFile(fileId: String): Uri = Files.addPath(fileId)
  def retrieveFileContent(fileId: String): Uri = Files.addPath(fileId, "content")
  // ...

@adamw @kciesielski @flsh86 wdyt?

@benzwreck yeah that's true, it's in the object's name

I meant something else. For example, you called a method deleteFile in
  def deleteFile(fileId: String): Uri = Files.addPath(fileId)

The fact that it's used for delete is not in the Uri, but in a DELETE call to this Uri. This is just a Uri which can have more purposes that deleting, when you call it with GET or POST or other HTTP method. That's why I suggest to name methods like this just fileEndpoint, or rather file if we agreed that endpoint is something else.
Note that there may be exceptions to this, like cancelFineTune, which indeed is a Uri meant only for canceling, because it has /cancel in the path.


Add aead and example

reviewed in tongsuo-java-sdk, can be safely merged

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Cannot change more than one colour using the viewer's legend

v1.22
Steps to reproduce:

Open a table
Add a viewer with legend that allows to change colour through legend (scatter plot or box plot with colouring, bar chart with stack, pie chart etc.)
Change one colour through legend
Change another colour through legend

Expected results: both colours are changed.
Actual results: the first changed colour is reset to default when the second one is changed:

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-16975

already fixed in 1.22.1


pure zero output of softmax

I got "Inf" cost in my training phase.
Finally found that there have many pure 0 as the output of softmax.
This has no impact on scoring, but when in training phase this could be an issue with std::log(0).
Is this normal? Or should I add EPS myself manually?
I thought this could be done in MKL-DNN, enhancing the robustness.
Thanks~

Hi!
Softmax is using exp function and if your input values > 710 or < -710 exp will return INF.
Softmax primitive first trying to rescale inputs by looking for max value and next subtracting max value from inputs. But this might not work if input range is too large, let say from -15000 to 5000.
To fix this input could be normalized with mean value or by rescaling values to range from 0 to 1 (like for LeNet).
Dmitry

However my input value would not out range, which has already been normalized.
Here my point is trying to say that the output of softmax do not have EPS, since I just got pure zero.
And this could cause Inf in next cost layer with log(0).

Yes, Softmax primitive do not have EPS

Thanks @DmitryRizshkovg
So would it be added to avoid Inf?

There seem to be no plans to do that now. Closing. Please reopen if this is a high priority.

@rsdubtso @DmitryRizshkovg
Do you have a plan to avoid the output of softmax to be 0?
If adding EPS manually, I'm afraid that the training speed will be slow down.


WebApp - Bugs related Manage NFT feature

Describe the bug
Bugs related Manage NFT feature

[x] Still, enable button Remove Collectible on the Pre-defined NFT

Expect:

If NFT is a pre-defined NFT -> Disable button Remove Collectible
If NFT is a custom NFT -> Enable button Remove collectible

[x] Error page when send NFT

[x] Update UI for the Import NFT screens follow by design

[x] Do not close the Import NFT screen after imported NFT successfully

Actual: after imported NFT successfully, do not close the Import NFT screen

Expect: Close the Import NFT screen

[x] Still show entered data when re-open the Import NFT screen

Steps:

Go to the Import NFT screen
Input data
Click on X button to close Import NFT screen
Click button Import collectible to re-open the Import NFT screen
Observe the screen displayed

Actual: Still show entered data when re-open the Import NFT screen

Expect: Reset previously entered data

[x] Do not show Properties of the NFT

Check with address 0x0a7826A5ba9E119F6D2406d1d7c284F1b2fe8969

[x] Do not show EVM custom NFT

Check with address 0x40a207109cf531024B55010A1e760199Df0d3a13
NFT address contract: 0x5ca22CcE3aEf2caCBb4054503c503a1106050C8C

Validation passed.


Automated cherry pick of #5238: fix host init set reserve memory

Cherry pick of #5238 on release/3.1.
#5238: fix host init set reserve memory

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/3.1@1b5756f). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             release/3.1   #5239   +/-   ##
=============================================
  Coverage               ?   6.73%
=============================================
  Files                  ?     547
  Lines                  ?   95767
  Branches               ?       0
=============================================
  Hits                   ?    6451
  Misses                 ?   88778
  Partials               ?     538

Flag
Coverage Δ

#aFlag
6.73% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/guestnetworks.go
0.2% <0%> (ø)

pkg/hostman/hostinfo/hostinfo.go
0% <0%> (ø)

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 1b5756f...d7a8519. Read the comment docs.

/lgtm

/lgtm

/lgtm

/approve

/approve


Use multiline when args exceeds max_width in fn_call_style = "block"

Closes #1521 (with refactoring, sorry for noise).

Thank you!


A collaboration idea ( Sparrow project )

Issue Label:

[ ] bug
[ ] feature
enhancement

Description of bug or feature enhancement:
Hi! I like your project. Actually I have somewhat similar project - https://sparrowhub.org , the idea is you can upload all your snippets into sparrowhub and manage them as the packages of software, don't hesitate to ask me why and how. Or we can think of other ways of bashsnippets / sparrow integration.
Regards.
Alexey
OS and OS version:

Mac
Linux 32 Bit
Linux 64 Bit
[ ] Windows 32 Bit
[ ] Windows 64 Bit

OS Version:

Hey
I don't fully understand your proposal, are you asking to add these scripts to sparrowhub?

hi ! Yes, I see that you have a collection of useful shell scripts. Right now the distribution is a git clone and install.sh , right ? You might upload your stuff to SparrowHub as well, the benefits you get:

expand you community ( Sparrowhub users )
script are easy to install on the most any Linux boxes by means of sparrow client
scripts are versioned, say the end user may install any version of script they want as they would do with any packages of software like Debian or Rpm packages
scripts have an ownership
scripts are searchable items by either console client or by web
end user has an access to the scripts' documentation either by web ( markdown to HTML ) or by console
sctipts might be run with  some binded parameters ( tasks ) defined in various formats - command line, json, yaml which easy the automation

These are some but no means are all features.
So, what do you think ? I can create an example taking one of your script and uploading it to SparrowHub to see how it works.

Where do things that are installed from sparrowhub get installed on the client machine? My current setup goes to /usr/local/bin is this the same? If so I wouldn't mind if you uploaded the entire repository of scripts there, the more places it is out there the better! However if the files arent installed there that will break my current update system in a confusing way that wouldn't error out at all but wouldn't update anything.

The idea behind sparrow is it provides  its own mechanism of script updates, so there is no need in install.sh / update command delivered by Bash snippets repo. All  this  is pretty described  in sparrow docs - see https://github.com/melezhik/sparrow#plugins-api
Say you have a script weather, following sparrow methodology you do this:

Upload script to SparrowHub with some version:
sparrow plg upload

Install script to the target machine:
sparrow index update
sparrow plg install weather

Later on, the script developer release the new version of the script (plugin) to SparrowHub:
sparrow plg upload

If users want to upgrade existed script (plugin) they do the same commands as above:
sparrow index update
sparrow plg install weather

You can even stick with a certain version of the script (plugin) if you want:
sparrow plg install weather --version 0.2.1

Moreover all the version of the script (plugin) are seen by SparrowHub web site.
All this is very similar to well known package distribution systems like Ruby gems, CPAN or pip. But with elemenary unit of script not library.
I have already seen your code, it seems to me that migration bash  snippets to SparrowHub won't be a big deal, as in most cases it's just a standalone bash scripts. BTW sparrow support dependencies like one can use pip, Ruby gems or CPAN Perl modules inside scripts, batteries included.

I am cool with adding it but i have to add a check in my updater that will throw an error if nothing has been updated and will recommend updating through the respective installed package manger. As i said for now if you installed through some other means then install.sh then calling tool -u or tool update would not return an error but actually would just update nothing and say successful. Also installing at the current moment doesn't prevent the user from doing this, so as much as I understand my update pipeline wouldn't be needed it would still exist in all of the tools and it would bring about broken functionality and even worse it doesn't aware the user it is broken. This might prove to be confusing for an end user.

Sure, I don't want to break existed Bash snippets installations )))
I have analyzed your repository, issues and history, looks like people want to add more and more useful scripts here. I found that sparrowhub and your project shares the same goal - let people to create and share useful scripts. Imho "in scale"  it'd be hard to manage a huge number of scripts by install.sh/update as you have there.
Say if I pick some scripts from your repo and convert them into sparrow plugins to see how one can manage and use the same scripts by means of sparrow? And if you like this examples we can think of about more deeper integration ... what do you think ?

Have created https://github.com/alexanderepstein/Bash-Snippets/pull/35 as an example

Moving conversation over to #35


Merge issue/23

Rebased PR for https://github.com/FRosner/drunken-data-quality/issues/23

Current coverage is 100.00%

Merging #63 into master will not affect coverage as of 67edca6

@@            master     #63   diff @@
======================================
  Files            4       4
  Stmts          198     200     +2
  Branches        40      40
  Methods          0       0
======================================
+ Hit            198     200     +2
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 67edca6

Powered by Codecov. Updated on successful CI builds.


Is 'vendor' still necessary?

Since we now require Go version 1.21, do we still need to include the 'vendor' directory in the repository? If users need the 'vendor' directory, they can generate it themselves using 'go mod vendor'.

Previously when we discussed this the consensus was that packaging the vendor directory ensures the code will always work even if the dependancies are unavailable for whatever reason (i.e. an environment with no internet). Interested to know how others feel about this and if it's still applicable.

My experience with vendoring has always been as a necessary evil when working with internal dependencies that are unable to be pulled in other environments while building. I have seen it become an issue when code bases get large and the vendor folder becomes unwieldy to commit. I have no strong opinion either way especially when it is as small as this folder is.
I would love to hear if others have a stronger opinion, but I find no harm in continuing with the status quo as I do not have an example that un-commiting the vendor folder would have any strong benefit outside of cleaning up our git.

I think deploying in an environment without internet access shouldn't be a problem. Users should first be able to fetch this repo from GitHub, and if they can do that, they should certainly be able to fetch others. 'The dependencies are unavailable' might be a good reason for this.

@dgduncan @mochi-co I think that deploying in an environment without internet access shouldn't pose a problem. Users should first be able to fetch this repository from GitHub, and if they can do that, they should certainly be able to fetch others. 'The dependencies are unavailable' might be a valid reason for this.
Perhaps we can weigh the pros and cons:
Pros:

Dependencies are unavailable, but we can still compile and run without any issues.

Cons:

It may result in additional code.
There might be a need for frequent updates to the Vendor library, which we may not actually be concerned about.

Additionally, we should assess how likely it is to encounter the 'dependencies are unavailable' scenario. From my experience, most of the repositories I've come across on GitHub do not include the vendor directory in their repository.

As for me, I am quite happy to remove the vendor folder, but I would be interested to hear from others like @thedevop and @torntrousers as they often have interesting use cases.

I don't have strong preference, leaning slightly for removing.

It seems to me that there is more interest in removing vendor, or at least giving it a go!

Merged into master :)


RetroArch / Libretro Bios loading does not seem to work.

Describe the bug
I'm trying to emulate PS1 games. I have the correct bios (scph5501.bin) loaded to my .config/retroarch/system directory.
When I use any PS1 core, (tried with Beetle PSX, PCSX ReARMed, SwanStation) they all fail to load the bios on running a rom.
Some games can still be played, but they may encounter issues with saving or any other features that rely on the bios.
Each playstation core in the core settings correctly reports the presence of the appropriate firmware.
I'm suspecting that there is some issue with the cores in the nix store.
Perhaps the bios change needs to edit something in the actual core files?
Anyone with more knowledge on how Retroarch works in Nixos have any ideas?
Notify maintainers
@thiagokokada
nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.39, NixOS, 23.05 (Stoat), 23.05.2162.6da4bc6cb07`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

The bios definitely works, just tested. Please try to use unstable instead of stable and check if the issue still persists.


The trait std::marker::Send is not implemented for syn::parse::Error

I try to convert from syn::parse::Error to failure::Error and receive this error message: "the trait std::marker::Send is not implemented". Is there a way to convert from syn::parse::Error to failure::Error?

Within a procedural macro you should never do this because it loses the ability to emit the error to the compiler in a way that points to the correct range of input tokens like a native compiler error.
Outside of a procedural macro you don't have that ability to begin with so I would write failure::err_msg(err.to_string()).

Thanks.


sql package handling fix

sqlserver is not mandatory if using sqlite now.

@Rick-Anderson - added some new error messages.


Add provenance trails for all actions that modify something

To each record, add a field modified, that contains a sequence of user-datetime pairs.
The user should be looked up in the user table, and the nickname should be filled in as name (denormalization).
Weed out entries: for each day before today, retain only the last entries for each person that has an entry on that day.

The first stage of the project has ended.


Tunnel: Incorrect termination of the session when disconnecting the ssh tunnel.

Open ssh tunnel.  Click on the connection on the tunnel tab
Click on the connection again to disconnect it
Go to the ssh tab and see that the connection to the this server is not available (the gray circle is lit, not blue).  If you try to connect via ssh to this server but from another device, then the connection will not occur.  The server freezes for a while and does not accept connections

@avalonix Yet I Iabel this issue "wontfix" because I dont'k understand why this can be a client (WebSSH) side issue.
Have you more logs on server side that should indicate the client is in fault?
Thanks.

client does not close the session when clicking on the connection in the tunnel tab

client does not close the session when clicking on the connection in the tunnel tab

Issue #27 is already opened for this bug behavior. So I will fix both issue into #27 in the next hours.
Thanks again for your feedback @avalonix 👍

Ok thx! I’m wait next beta


render bounding box question

is there any way we can get the bbox and scale of what is to be rendered by the map? the zoomToBox zooms the image to fit the bounds of map, but if say you produce a 800X600 image based on a zoomToBox that's 16:9 then the rendered bounding box will be significantly different to the original 16:9. I'm trying to manipulate the data layer to exclude any label on the edge of the map but without knowing what the true bounding box is and without knowing the scale will be makes this difficult. any ideas here?

Mapnik has functionality to get a map's extent and scale, but it is not implemented in the extension yet. I also suspect that being able to change the aspect fix mode (https://github.com/mapnik/mapnik/wiki/Aspect-Fix-Mode) would be helpful.
Relevant Mapnik methods:

get_current_extent (https://github.com/mapnik/mapnik/blob/master/include/mapnik/map.hpp#L413)
get_buffered_extent (https://github.com/mapnik/mapnik/blob/master/include/mapnik/map.hpp#L418)
scale (https://github.com/mapnik/mapnik/blob/master/include/mapnik/map.hpp#L423)
scale_denominator (https://github.com/mapnik/mapnik/blob/master/include/mapnik/map.hpp#L425)
set_aspect_fix_mode (https://github.com/mapnik/mapnik/blob/master/include/mapnik/map.hpp#L457)

Let me know if you want to tackle implementation. Otherwise I'll work up something over the next week or two.

I wish I could. not very handy with c. I am at "hello world" level. I think those mapnik methods would be very handy. am trying to implement it via the !bbox! intersect thing but its not very flexible nor particularly useful.  perusing the map.hpp, remove_style might also be very useful in the long run. I suspect this project will mostly be used to generate static maps, at least that's how i'm using it and managing layers and styles is big one for that. the way i am doing it is loading the xml file and altering the style and layer then send it via loadXmlString().
great project, very useful to have this available native in php7+ thank you very much for the effort so far!

The discussed methods are now available in the develop branch. There is some house keeping and documentation work I want to get in, so a tagged release is still a couple weeks out. Until then, the map class tests offers the best look into what's available.

great enhancements , good to see you pulled though a lot more than i thought you were. I've tried to compile it but it to be failing on

make test
@ FAIL \Mapnik\Image [tests/image.phpt]

i didn't get any compile errors. could it be a libgd version thing? the master branch still compiles and passes the tests.

Paths for test images were missing a directory separator. 🤦♂
I got Travis (Ubuntu Trusty) back to building successfully so you might pull and try again. Thanks!

ok , all is working , new functions are sweet! :)
$class_methods = get_class_methods($map);
echo print_r($class_methods,true);
gives ->
Array
(
[0] => __construct
[1] => loadXmlFile
[2] => loadXmlString
[3] => zoom
[4] => zoomAll
[5] => pan
[6] => panAndZoom
[7] => zoomToBox
[8] => registerFonts
[9] => getBasePath
[10] => setBasePath
[11] => getWidth
[12] => setWidth
[13] => getHeight
[14] => setHeight
[15] => resize
[16] => getSrs
[17] => setSrs
[18] => getBackgroundImage
[19] => setBackgroundImage
[20] => getBackgroundImageOpacity
[21] => setBackgroundImageOpacity
[22] => getMaximumExtent
[23] => setMaximumExtent
[24] => resetMaximumExtent
[25] => getCurrentExtent
[26] => getBufferSize
[27] => setBufferSize
[28] => getBufferedExtent
[29] => getScale
[30] => getScaleDenominator
[31] => countLayers
[32] => removeStyle
[33] => removeAll
[34] => getAspectFixMode
[35] => setAspectFixMode
)

New functionality has been merged into master and released with 1.2.0. Make sure and checkout the new API docs too. Thank you for creating the issue!


On-Screen volume controls in WSA apps

Is your feature request related to a problem? Please describe
Using WSA on a foldable or tablet device makes it cumbersome, or even hard to adjust the volume without unfolding the device or leaving the app.
Describe the solution you'd like
Show on-screen volume controls in each WSA application, maybe something similar to the accessibility option on iOS (AssistiveTouch) or comparable feature in Android.
Describe alternatives you've considered
No response
Please specify the version of Windows Subsystem for Android
2303.40000.5.0

Please file this request in feedback hub (Win+F) related to the Windows 11 audio mixer functionality.


Commodities and statuses

Also did some internal refactoring.

I'm not quite done yet, but I'd like to attempt to release the pod.


Is there a way to draw on the gaming canvas

I tried to draw on the noa.container.canvas but it doesnt work ??? I cant get the context("2D") , any ideas???

HTML canvas objects only do one mode - noa's is using webgl, so that's why trying to get a 2D context returns null. If you want to draw 2D stuff on top of the 3D scene, that's probably something to ask in the babylonJS forums about?


Making winrt::impl::lock more standard and probably open

The lock class currently doesn't implement the lockable concept and is located in the winrt::impl namespace. Probably it would be better if the lock implements the lockable concepts.
struct lock
{
    lock(lock const&) = delete;
    lock& operator=(lock const&) = delete;
    lock() noexcept = default;

    // Lockable concept
    void lock() noexcept;
    bool try_lock() noexcept;
    void unlock() noexcept;

    // Shared mutex concept
    void lock_shared() noexcept;
    bool try_lock_shared() noexcept;
    void unlock_shared() noexcept;
};

As an addition, the lock class could be moved outside of the winrt::impl namespace to be a slim version of std::mutex and std::shared_mutex (requires the shared mutex concept). So, it would be possible to use it not only in C++/WinRT implementation.
For now it isn't a good idea to use it, and the standard mutexes are too expensive.

The Visual C++ team continues to improve the performance of the standard synchronization primitives. While we love the SRW lock and use it internally, none of the types and functions in the winrt::impl namespace are considered part of the public surface of the C++/WinRT library and you should thus not use them directly. The SRW lock is however beautifully simple and you can easily write such a wrapper yourself, even using our implementation as a starting point. I would just be careful not to take a dependency on anything in the winrt::impl namespace because it is subject to change or removal at any time.

Yes, it's written in the change log.

We have steadily cleaned up the base library to avoid leaking any unnecessary implementation details. The winrt namespace is now a lot leaner, exposing only those functions and types that you could conceivably need to use in order to make the most of C++/WinRT. Anything that begins with impl_ or is within the winrt::impl namespace should be considered an implementation detail subject to change at any time.

The are few ways to implement a slim lock (using SRWLOCK or std::atomic<T>), but reimplementing something isn't a good idea. Since you are investigating similar things for COM, why not to make such things public, write an extension library, or do something else? The things like lock and handle<T> are really useful and could be used in our projects, not only internally in yours.

Yes, we may surface these in a separate library since they are not specific to WinRT. Thanks for the suggestion!

I'm making changes to base_lock (and dependencies) to make the existing winrt::impl::lock and winrt::impl::condition_variable conform to standard library concepts in order for them to work with other std types like std::lock_guard.


Carousel Current Items Providing Wrong Index

I have created a carousel slide and i need to animate different styles based on current slide number.
$("#carouselSliderWithIndicator").on('slide.bs.carousel', function(evt) {  slideNumber  = $(this).find('.active').index(); })
This code works well when slide change autometically.
But if I click on the previous Indicators $("#carouselSliderWithIndicator").on('slide.bs.carousel', function(evt) {}) this function always output the next number only on slide changes not the real current index number.
Though I solved it with onclick indicators. Doing the animation first checking if the slide changes with indicator click or just auto. If it's indicator click then i do animation with counting that number of indicator.

Please ask on StackOverflow or similar. This isn't the place for "how to" type questions. See https://github.com/twbs/bootstrap/blob/master/.github/CONTRIBUTING.md


Installation failing in python alpine image

Pip installation  is failing in python alpine docker image.
Error message
#5 3.671 ERROR: Could not find a version that satisfies the requirement minify-html (from versions: none)
#5 3.672 ERROR: No matching distribution found for minify-html

Example Dockerfile
FROM python:3.9.0-alpine

RUN pip3 install --upgrade pip && \
    pip3 install --no-cache-dir minify-html

Is there any fix or workaround for this issue?

I believe this is due to missing glibc, which is required by the library and the default target when compiling the Rust library. You can try installing that, or compiling from source targeting another libc like musl.


DateTime and TimeStamps NULL should remain NULL

Fixes #1276

@wubzz Any reason why this was closed without merging?

Or was it only relevant for maria and mysql never had this issue in the first place?

See original issue for reasons.


Have question in image_demo.py

Thank the author for his contribution. After training my own data set, I used test.py tested the model AP(iou=0.5) can reach 95%, but I use image_ demo.py for actual test,, the segmentation effect shows only one category. There are four categories in my dataset.

what code did you use? more details are needed.

what code did you use? more details are needed.

I use point_rend_r50_caffe_fpn_mstrain_3x_coco.py

what code did you change? I think this may be because the image does not have other categories, or your model did not detect other categories?

I replaced the FPN in the mask_rcnn_r50_fpn with my own improved network. I trained the improved network and the AP(IOU=0.5) can reach 95%. Then I used pictures of different categories to test and found that there was only one category in the final display

The model also misclassifies other categories into one category

what code did you change?

pafpn.py

please use the issue template to ask the issue. More details are needed. Right now, I cannot help you fix your error

okay, thank you

Also, is your evaluation and training seem normal?

Yes, everything is normal and the indicators have reached a high level, but the effect of image detection with the generated model is very poor

The data has been loaded successfully，i will check my code

It is suggested to check your code, for example, did you load your data successfully?

Hello, I have solved the above problem. When I train with my own dataset, the category order is not consistent in the label file and code. After modification, multiple categories can be displayed normally, but I encounter a new problem. Due to hardware constraints, I uniformly adjust my dataset to 604 * 604 size. During the training process, AP (medium and large) has always been - 1. Is this normal

我用自己改进的网络替换了 mask_rcnn_r50_fpn 中的 FPN。我训练了改进后的网络，AP(IOU=0.5)可以达到95%。然后我用不同类别的图片进行测试，发现最终显示的只有一个类别

可以留下联系方式一起互相交流吗？

@15032390092 @xuhao-anhe https://github.com/open-mmlab/mmdetection/blob/master/README_zh-CN.md#欢迎加入-openmmlab-社区


Exception came correction in comments

There is missing @throw statement in some methods & many methods mentions wrong exception name in the @throw, like PinterestExceptions whent he exception name is PinterestException. & also mentioned it's with wrong namespace.
I want to correct this to get better IDE support

There are no changes in this PR, except for merging dev into master. Please create a proper PR with your changes, or create an issue if you can't do it yourself.
Thanks.


Updates scripts to process HEVC content

Updates run-all.py and encode_dash.pyscripts:

now it takes the the mezzanine file list as an argument, the list is provided as a csv.
provide more flexibility in adding new columns to mezzanine csv and stream vector csv
signal cenc encryption through the csv files
fixes hardcoded cmf2 brand
fixes GOP size for hevc content
removes draft hevc splicing bash script as it can now be performed with the run-all script and specific csv configuration
fixes support for non square sar
adds --d/-dry-run option

replaces profiles/hevc.csv with profiles/chh1.csv & profiles/chd1.csv

What's missing at this point:

run the updated scripts for AVC and re-run validation
remove upload/zip from run-all.py and document the new script that supports these functionnalities
update the documentation


chore: replace broken hope-ui link with kobalte in readme

Summary
Currently component libraries links out to https://hope-ui.com/ which no longer works. Looking at the hope-ui repo, we find a working link (https://hope-ui.netlify.app/).
However, this library is deprecated and points to https://pigment.kobalte.dev as a successor. I've opted to instead link to https://kobalte.dev as it has more documented components than the pigment site.
Could also link to https://www.solidjs.com/ecosystem#ui if that is preferred.
How did you test this change?
I clicked some links.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.56%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4186

Relevant Lines:
4408

💛  - Coveralls


Open related test file

Right now the package seems to be opinionated towards using rspec. the default in rails is still minitest with _test.rb files. do you think you can add support for jumping to a unit test from a model and controller test from a controller?

Yes I'll support to jump _test.rb files.

@Soleone  I published this feature into the atom package registry right now https://atom.io/packages/rails-transporter.
But I don't get familer with minitest. If I mistake about implementation, please reopen this issue.

hi @hmatsuda, thanks a lot! it seems the basic functionality is there.
that being said in my particular rails project it is not working as expected. the reason is that before rails 4 i think the folder structure was different, and a lot of old rails project will still have the following folder structure:

test/unit instead of test/models
test/functional instead of test/controllers

here is a source with comparison between rails 3 docs and rails 4 docs
it would be great if the package could be adjusted to accommodate for both use cases, i.e.:

look in test/models first and if that doesn't exist try to find the file in test/unit
when suggesting to create a new file make sure to try to create it in the existing folder, so if only test/unit exists, suggest creating it there, otherwise suggest creating it in test/models


Confirmed doesnt work correctly

Versions

vee-validate: 2.1.0-beta.6
vue: 2.5.16

Describe the bug
I'm just simply trying to reproduce this fiddle: https://jsfiddle.net/k0L3nq55/

The password confirmation does not match.

The error will always pop-up after the required validation is passed.
Expected behavior
I'm expecting no error when the passwords do match.

I just happened to have this Situation today.
https://jsfiddle.net/pf6Lte1d/
2.0.0-rc.14 -> 2.1.0-beta.6
Is this a similar situation?
#1466

In 2.1.x beta releases the targeting was changed to use Vue refs instead for various reasons.
You have to add ref="pass" on your confirmation field:
https://jsfiddle.net/k0L3nq55/29/
The docs was just updated to better communicate this change.


v1.6 updated the code build image to standard 3.0 as per jira Her-425

The latest tag version is 1.7 now. Git base off master branch and then tag this version with 1.8.


1 test failed. locale:zh-cn:calendar next week (1848.1)

Client info
Date String   : Tue Mar 08 2016 10:40:04 GMT-0600 (CST)
Locale String : 3/8/2016, 10:40:04 AM
Offset        : 360
User Agent    : Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

====
locale:zh-cn:calendar next week (1848.1)
Today + 7 days beginning of day
// Expected 下周一凌晨12点整
// Actual   本周一凌晨12点整
"本周一凌晨12点整" === "下周一凌晨12点整"

Macintosh OSX (El Capitan)
Chrome Version 49.0.2623.75 (64-bit)

I can reproduce this on 2.12.0 in Chrome latest on Windows 10.  I think all browsers are affected.  Not sure why it didn't get caught in tests.

Looks like the nextWeek and lastWeek implementations in zh-cn.js use moment() in their calculations, so the time that the test runs could affect the output.
Not sure why this is showing up just now, as it's been there for awhile.  Something else must have surfaced it.

Ok, so I know why it's failing now.  It's DST related.  Run it in a time zone without DST (or a non-US time zone) and it will work.  It's failing now because it's testing a week out and we're approaching the start of DST in the US this coming Sunday.
Fix pending...

We'll track this in #3028.  Thanks.


Deploy to rancher action

To load docker/rancher-compose files from a URL.
https://forums.rancher.com/t/deploy-to-rancher-button/1358/9?u=vincent

version - master ui 1/22
Verified fixed


Add Pending Approvals Special Page

For #23
Current state:

Page titles are links.

Currently there seems to be a problem with the categories retrieved via DatabasePendingApprovalRetriever. All 3 of the pages in the screenshot have multiple categories.

I've started wondering is showing the last edit time and user makes sense. Perhaps it makes more sense to show when the page was unapproved and by who (or automatic). Or maybe both sets of info. Let's just start with what we already have implemented.


WIP: Add Time field to Event

Add Time field to Event
it has been there in event JSON already, just been dropped as there was no corresponding field

Actually, don't merge yet: I'll make the Time field to be of time.Time type (vs int64)

Time is Unix time in milliseconds

LGTM


Negative test report for Random library

Description:
$Subject

Closing since negative test case is already added in [1].
[1] https://github.com/ballerina-platform/module-ballerina-random/blob/e53b2b89ee9d034df8cbb9befdede65d2fd8ca40/ballerina/tests/random.bal#L36


Upgrade infrastructure

Among the many things, this PR

[x] Uses pyproject.toml for project management
[x] Upgrades docker image version
[x] Upgrades versions of other services (eg. Azurite, etc.)
[x] Uses our current setup for GitHub workflows
[x] Updates code to use modern dependencies way of doing things (eg. bootstrap)
[x] Replaces isort, flake8 and black with ruff
[x] Update pre-commit to use our current list of hooks

Close https://github.com/ImperialCollegeLondon/rse_maintenance_tasks/issues/10

The vast majority of what appear as changed is the linters and formatters.

When I tried running this I got this:
Attaching to faraday-liionsden-azurite-1, faraday-liionsden-db-1, faraday-liionsden-web-1
faraday-liionsden-db-1       |
faraday-liionsden-db-1       | PostgreSQL Database directory appears to contain a database; Skipping initialization
faraday-liionsden-db-1       |
faraday-liionsden-azurite-1  | Azurite Blob service is starting at http://<IP_ADDRESS>:10000
faraday-liionsden-azurite-1  | Azurite Blob service is successfully listening at http://<IP_ADDRESS>:10000
faraday-liionsden-azurite-1  | Azurite Queue service is starting at http://<IP_ADDRESS>:10001
faraday-liionsden-azurite-1  | Azurite Queue service is successfully listening at http://<IP_ADDRESS>:10001
faraday-liionsden-azurite-1  | Azurite Table service is starting at http://<IP_ADDRESS>:10002
faraday-liionsden-azurite-1  | Azurite Table service is successfully listening at http://<IP_ADDRESS>:10002
faraday-liionsden-db-1       | 2024-09-06 16:10:48.223 UTC [1] FATAL:  database files are incompatible with server
faraday-liionsden-db-1       | 2024-09-06 16:10:48.223 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 15.8 (Debian 15.8-1.pgdg120+1).
faraday-liionsden-db-1 exited with code 1
dependency failed to start: container for service "db" exited (1)

It appears like this means this will not work with any existing databases. If there are no databases, then this isn't a problem.


 Learn more about stacking.

Join @pepyakin and the rest of your teammates on  Graphite


Change a follower site to the new leader site

Hi,
It is possible to be provided an example of changing a follower site to become the leader site, I tried to use the below gslb task and it doesn't work. The only option / doc found it is https://avinetworks.com/docs/20.1/how-to-select-a-leader-site-manually/
We are using avi 20.1.6 with ansible 2.8
For the moment we have the old avi that is configured to be gslb site leader and the new avi as gslb site follower and we want to switch by making the avi as leader and old avi to be follower. We tried the below task but is not doing anything and we do not received any error.
    - name: Switch gslb site leaeder
      avi_gslb:
        controller: "new controler ip"
        username: "{{ avi_username }}"
        password: "{{ avi_password }}"
        api_version: "20.1.6"
        avi_api_update_method: patch
        avi_api_patch_op: replace
        state: present
        name: "AVI-gslb-{{ availability_zone }}"
        leader_cluster_uuid: "{{ cls_rtn_obj_new.obj.uuid }}"
        sites:
          - name: "{{ dc }}-gslb-{{ availability_zone }}-site_new"
            username: "{{ avi_username }}"
            password: "{{ avi_password }}"
            ip_addresses:
              - type: "V4"
                addr: "<IP_ADDRESS>"
              - type: "V4"
                addr: "<IP_ADDRESS>"
              - type: "V4"
                addr: "<IP_ADDRESS>"
            dns_vses:
              - dns_vs_uuid: "{{ vs_rtn_obj_new.obj.results.0.uuid }}"
            enabled: True
            member_type: "GSLB_ACTIVE_MEMBER"
            port: 443
            cluster_uuid: "{{ cls_rtn_obj_new.obj.uuid }}"
          - name: "{{ dc }}-gslb-{{ availability_zone }}-site_old"
            username: "{{ avi_username }}"
            password: "{{ avi_password }}"
            ip_addresses:
              - type: "V4"
                addr: "<IP_ADDRESS>"
              - type: "V4"
                addr: "<IP_ADDRESS>"
              - type: "V4"
                addr: "<IP_ADDRESS>"
            dns_vses:
              - dns_vs_uuid: "{{ vs_rtn_obj_old.obj.results.0.uuid }}"
            enabled: True
            member_type: "GSLB_ACTIVE_MEMBER"
            port: 443
            cluster_uuid: "{{ cls_rtn_obj_old.obj.uuid }}"

Please let us know if you need more details
Thank you,
Vlad

Problem resolved
REST API Request
Method: POST
API: /api/gslbsiteops/changeleader
Data: {‘new_leader’: ‘cluster-be03a807-5c88-4511-a5b3-dde1c3e8bcb0’, ‘view_id’: 1}


Neural Network approch to predict stock is added

neural network approach is added stock prediction approch is further improved

Well done @Ank-Romeo


DB Connection string not available

Hi, I need the connection string to be able to connect to the postgres db in Nhost v2.

Yes, it's on our near-term roadmap. 👌

Amazing, I already knew you guys were working on this 👍  I just made this issue so that I could be updated when you guys make it available.
Is there perhaps a public roadmap where I could check instead of making these issues?

Thanks. We don't have a public road map available but we'll try to be more transparent and explicit about new releases in the future.

This would help a lot, especially for users who want to migrate from HasuraCloud/Open Source to Nhost. Looking forward for that feature as well.

It's one of our top 5 most prioritized features so it will be available soon. 👍

what are the other 4 top features?
Honestly, v2 looks so... "alfa" right this moment, I was expecting a more robust platform for beta release
(no connection string, errors with hasura auth and camelCase, can't control Hasura version, no online viewer/editor for cloud functions, no online viewer/editor for files, "503 Service Temporarily Unavailable" from time to time, small quirks with nhostjs)

Hey @yureckey keep let's be patient, I bet it's not easy to migrate such a service

@yureckey Totally. Running a startup is like playing StarCraft 2 against three people at the same time and there are 5 marine drops in your bases with zerglings everywhere and you just realized you forgot to start armor upgrades 2 minutes ago.
Also, your kitchen just caught on fire.
But we'll get there 💪

We plan to have it available in the next 2-4 weeks. It's being actively worked on as we speak.

Hi @elitan
Will this connection string be available for everyone or just paid plans?

Everyone 🙌

Fantastic! Can't wait as I need to migrate a db.
On Thu, 17 Feb 2022, 13:55 Johan Eliasson, @.***> wrote:

Everyone 🙌
—
Reply to this email directly, view it on GitHub
https://github.com/nhost/nhost/issues/113#issuecomment-1042920645, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDT6MSM3E2LS46Z3JVVCHDU3TV3FANCNFSM5LWS5NRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

How come can i migrate my existing data to the production DB provided by nhost without connecting to the DB directly?!!

How come can i migrate my existing data to the production DB provided by nhost without connecting to the DB directly?!!

You can not but as soon as we have the DB connection string available you will be able to 👍

You can run sql on this API endpoint:
https://hasura.io/docs/latest/graphql/core/api-reference/schema-api/run-sql.html

Yes Dominik, you're absolutely right.
It is also possible to run a pg_dump with this endpoint: https://[project-id].nhost.run/v1alpha1/pg_dump
The endpoint is explained in the official Hasura documentation.
As @elitan explained, we are working hard on allowing a direct Postgres connection when required. Thanks for your patience

Hi! Is there an updated ETA on this?

We're still working on this and we're making progress. ETA right now is 1-2 weeks.

Any timeline update?

Also needed here :+1:

update from our side: we have worked on making the connection string available but last week, before releasing it, we found a security issue that is having us re-evaluate our approach. Unfortunately, we are not able to guarantee access anytime soon. There is still one thing we want to try to see if it can be fixed with the actual solution but if not, we will not be releasing this anytime soon. I am really sorry for any inconvenience this might bring but this specific issue was really hard to predict. On a better note, backups will be out very very soon.

Yes Dominik, you're absolutely right. It is also possible to run a pg_dump with this endpoint: https://[project-id].nhost.run/v1alpha1/pg_dump The endpoint is explained in the official Hasura documentation. As @elitan explained, we are working hard on allowing a direct Postgres connection when required. Thanks for your patience

@plmercereau I've tried run this call with Postman, but I only got this error response
{
"path": "$",
"error": "resource does not exist",
"code": "not-found"
}

Hello Yuriy,
The above mentioned endpoint works.
You may need to check:

you are sending a http POST request
you are adding the following headers:

{
  "x-hasura-admin-secret": "the hasura admin secret of your app"
}

you are sending a payload as per the documentation, for instance

{
  "opts": ["-O", "-x", "--schema-only", "--schema", "public"],
  "clean_output": true,
  "source": "default"
}

Well, I thought this is exactly how I tried it:

update from our side: we have worked on making the connection string available but last week, before releasing it, we found a security issue that is having us re-evaluate our approach. Unfortunately, we are not able to guarantee access anytime soon. There is still one thing we want to try to see if it can be fixed with the current solution but if not, we will not be releasing this anytime soon. I am really sorry for any inconvenience this might bring but this specific issue was really hard to predict. On a better note, backups will be out very very soon.

Any update on the "one thing" that you wanted to try? 😄 Did it work?

@mortenhillbom It didn't. Because of that, and a couple of other reasons, we are changing the way we host databases. We currently host on RDS instances (multi-tenant architecture) and are now testing moving to dedicated Postgres instances for all apps. This will make it possible to connect directly to Postgres and install any extensions needed. We are still evaluating and working on a POC so I can't give a timeline atm. I will update the issue when we have a more definite timeline.

@nunopato Ok, thank you for the update!
On that note however, how long will v1 be supported? And will it be supported until this is in place (+ a grace period for transition) or is there chance it will not?

Hello , any update on this?

Hello , any update on this?

Very soon. It's top priority internally.

hey there! I am really excited about this 🎊 we are mostly done with the work necessary to provide direct access to your project's databases. For this to work, we had to fundamentally change how we operate Postgres. We moved away from shared RDS instances to isolated Postgres instances running alongside (and closer to) your services. Other reasons to move to dedicated Postgres instances are stability, performance, and isolation - you own the entire instance (Postgres root-level access)
If any of you is starting or about to start a fresh project and want to build it on the new offering,  feel free to send me a DM on discord and I will hook that up in a new project. Existing projects will have to wait a bit for us to finish implementing moving data around between RDS and K8s

Hi @nunopato,
Any update on this? One specific use case for this would be for custom resolvers with an orm that has direct access to the database.
https://hasura.io/learn/graphql/hasura/custom-business-logic/2-remote-schemas/

I think we can happily close this? @elitan @nunopato

Yes! 🙌

So... I'm trying to connect to postgres from DBeaver and Beekeper studios and none of these ara able to connect directly to the database.
Both says that the authentication failed


Feature/immediate password error

Let the user see immediately, when the password not fulfills our requirements.

Seems to work as intented, but I get 400 response (Bad Request) on every keystroke in password field.

New proposed solution:
https://yetu-dev.atlassian.net/wiki/display/APPHOME/Password+validation+and+strength
Feedback is welcomed.

Updated PR, please review

Thanks :+1: I will review

Strength does not work anymore for me :(

When I´m in a field, it should be white, although, when it is already valid.

Feedback/Info box should be aligned with questionmark.

Better layouting for space between lines... no consistent. But this we can do in a new pull request.

After password is changed, the link should not say Ok.

In general it looks good. Small minor issues left to fix ;)

Thank you very much for your review Elisa. We should avoid commit code with problems, because I believe that the PRs revision must be just on code-styling, or general review of the code standards. I mean, there is no obligation for testing if the code committed actually work when revising, so we sorry for that.
Specially for the screen "after password is changed", seems that we forgot to replicate our modifications to that screen. We will work a little more on this. Thanks :+1:


Proposing archival of Symphony Rest Tools as project not maintained

Proposing to archive this project as:

project is not currently maintained

Note that archival means downstream projects can keep using existing releases of this project but shouldn't expect new ones and should take a hard look as to whether it's time to migrate to a potential superseding project.

Following raising this PR on 4th October 2020, the FINOS team will merge this PR on Friday 9th October 2020, so the project status is correctly represented in the README.md
Please feel free to merge the PR direct or allow the FINOS team to merge on your behalf.
James.


A couple of questions

You didn't mark your styles as scoped does it mean that they are global?
You change the tags property directly while in documentation is said "you should not attempt to mutate a prop inside a child component." and use custom events instead.
I've just started to learn Vue.js, so could you please clarify these two things?

I think scoped property is optional.
You change the tags property directly,  I think the author of Vue.js want you to mutate the prop data in child component through Vuex,  if the prop is an Object, after you change the value of the data, then its parent data also will change, if the prop is a string, after you change the value of the data, then its parent data won't change, so the author of Vue.js told you if you change the value of the prop string, it won' change the corresponding value in its parent.

@tolerious
2. I understand that, but in the given case the author of the module change the object (array) received from the parent, directly in the child module.

@osenvosem  sure, in my project if I don't use Vuex, I will use the $emit(eventName) and $on(eventName) to deliver the data.

@tolerious and this seems to be the right way, according the documentation. That is why I ask the author. 🙂

@osenvosem:

They are not global because all the styles are encapsulated under .vue-input-tag-wrapper.

In the docs it says: This means you should not attempt to mutate a prop inside a child component. If you do, Vue will warn you in the console. but I'm not seeing any warns.
But I think you're right, maybe it's better to avoid doing that. I'll change that soon.

@tolerious: thanks for helping me answer :)

@matiastucci thank you for the answer.


async UDFs

Is your feature request related to a problem?
No
Describe the solution you'd like
I would like async function support for UDFs
Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
No

Hi @mplemay, what is your use case for an async UDF?

Hi @mplemay, what is your use case for an async UDF?

@kevinzwang I was specifically interested in calling an web api, but it would generally be useful for any blocking IO operations

Hi @mplemay, I don't believe async UDFs would offer any performance advantages. Each UDF already runs on an individual thread or process, and the Python async runtime does not easily integrate with Daft's work scheduling, we would essentially run it as a blocking function anyway.
For IO operations, I would recommend either using a synchronous library such as requests, or calling asyncio.run() if you need to run async code.
Closing this issue for now

Makes sense @kevinzwang and thank you for the detailed response.


Team 11 Review (VnV Plan): Missing Requirement IDs

@samm82
Summary
There is no traceability between the tests and the new requirements listed in the Hazard Analysis (PR, AVR, RFT). Either add tests if the requirements are missing, or update the ids if they are misaligned.
Deadline
05/02/2024
Estimated Work Hours
0.5 hours

Added look-up table in SRS since the requirements are renamed


Fix ext3/4 blkid test comparisons

These two tests failed for me. Looks like a simple typo (and passes with the change).

Do I resend this to the ML or would you consider merging commit from here?

Resending to the mailing list would be easiest. (I'm traveling right now
and have access to the web archive, but not my email archive.)
Thanks,
Rob
On Thu, Dec 10, 2015 at 2:05 PM, Johan Bergström<EMAIL_ADDRESS>wrote:

Do I resend this to the ML or would you consider merging commit from here?
—
Reply to this email directly or view it on GitHub
https://github.com/landley/toybox/pull/8#issuecomment-163735337.

Fixed in https://github.com/landley/toybox/commit/2a3ac1459f857f17e1c273c49a8df000b14fc8db.


MonoDevelop doesn't open the solution when sln path contains spaces

Godot version:
3.1.2 stable mono version
OS/device including version:
KDE neon 5.17 amd64
Issue description:
MonoDevelop when launched from Godot doesn't open the game solution and just displays the startup page when the file path of the sln contains spaces.
Since in the first place, MonoDevelop doesn't allow to create solutions with spaces in them

it would feel natural that if MonoDevelop is officially supported as an external editor, Godot should comply with its official limitations
An other approach could be to add a warning when creating a project with spaces that some editors could have difficulties working properly with it.
Steps to reproduce:
Create a Godot Project with spaces in the path
Set MonoDevelop as the Mono editor
Minimal reproduction project:
here is a small test project containing spaces
trying to open Node.cs will try to open monodevelop but monodevelop will just display its home page
test project.tar.gz

MonoDevelop is able to open solutions with spaces from the GUI and when I drag and drop the solution file from the file system, so this seems to be a bug with its cli.
Regarding whether Godot should allow solutions with spaces (ideally by replacing them with either dots or underscores) I'm not really against such a rule but if this could be fixed in MonoDevelop instead that would be better.

SInce this issue is present in MonoDevelop since a long time, I am not sure the devs are willing to fix it.
They maybe want to enforce their choice of not having spaces in solutions.
I will post an issue about it on their repo as well, but I don't really know how it will go.

https://github.com/mono/monodevelop/issues/9406 I've opened an issue on their repo

This doesn't look like Godot bug and it even has an issue on another repo, so closing.


AtlasEngine: Fix uneven baselines when scaling glyphs

This commit changes the glyph scale algorithm to prefer aligning glyphs to
their baseline. This improves the visual appearance of simulated italic glyphs.
Closes #13987
Validation Steps Performed

Use FiraCode which has no italic variant and instead uses simulated italics
Write italic text
Baseline is consistent ✅

in "new" the vertical stems of letters (primarily r) become more blurry.

Ah woops... The old one is using ClearType and the new one had it disabled and that makes "Old" to appear more crisp. If you open the image in a new tab and zoom in, you can see that the stems are practically identical.

Well, it looks less weird... !

Yep, agreed. I'll try to make it work properly and as expected without downsizing in a follow-up PR.


Update Galley Server Utilization message

Fixes #14406

You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test?
Courtesy of your friendly test nag.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: therealmitchconnors
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ozevren
If they are not already assigned, you can assign the PR to them by writing /assign @ozevren in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

:thinking: :bug: You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test?
Courtesy of your friendly test nag.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ozevren, therealmitchconnors
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS [ozevren]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@therealmitchconnors: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
899460cd3347c03340920d3841e0e2cb82bf6c1e
link
/test integ-security-k8s-presubmit-tests-master

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


testing logo from SPIFFS

Here is an updated version of the State Monitor which uses the logo from SPIFFS together with an updated version of the LCD lib (available as new branch).
This is just for testing to give you an idea how the flash process would look like and how the logos look like.
The data folder of this repro contains 5 .bmp files. 4 for the 4 known logos and 1 that is just called logo.tmp. The logo.tmp ist the one that is pulled by the LCD lib and it is not tied to any maker name. To see the different logos just copy the one of interest to logo.bmp, use the ESP32 sketch data download  tool and that's it.

In the data directory of production release repro of the FW there will be only one logo.bmp which has the maker specific content.
I just put the other ones there for you to give you a chance to view them all and to see how they look in full color resotion rather than just 2-color.
I think the only way to get this loaded into SPIFFS without additional tools is the ESP32 sketch data download included in the Arduino IDE. It could be done of course by the config UI or via MQTT. May be you have something in mind?

The logos look awesome!


Relax validation of args/returns on cells

This change removes validation of a cell's args and returns on notebook startup. The validation made spot-editing a notebook onerous, and it wasn't needed because marimo auto-fixes errors on save.
This change also makes it somewhat easier to write a notebook from scratch in your text editor, because you can just omit the refs and defs. Eg, you could open the following file with marimo edit:
import marimo
app = marimo.App()

@app.cell
def imports():
  import marimo as mo

@app.cell
def greetings():
  mo.md("# Hello, world!")

and marimo would autofix it for you on save.
This change was motivated by feedback from users, who wanted to be able to easily make edits to their notebooks in their editor of choice.

Probably worth having a test case for this. Also, I assume it still fails for multiple defs? Or unknown refs?
Maybe a test case for that as well?

Yea, app.run() still fails for multiple defs, unknown refs. Added tests, thanks.
marimo forms the dag by just reading the cell code, ignoring args/rets. The args and rets are inserted by marimo on save so the cells can be executed as functions, but they aren't needed to resolve refs/defs.


Make JAX an optional dependency

JAX can be difficult to build on certain systems, so it would be good to make it optional since it's only simsopt.geo that depends on it.

Somehow JAX ends up at the top level import of simsopt. One has to check carefully the imports and restructure them.


Don.t crash JobUpdater if http fails with connection refused

It mainly happens on agents with an unstable couch server. Here is an example traceback [1]
I've applied this patch to vocms0116, since this component is going down once/twice a day.
@ticoann please review but don't merge yet please
[1]
2016-11-22 22:29:49,738:139871564584704:ERROR:JobUpdaterPoller:Caught unexpected exception in JobUpdater
[Errno 111] Connection refusedTraceback (most recent call last):
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMComponent/JobUpdater/JobUpdaterPoller.py", line 82, in algorithm
    self.synchronizeJobPriority()
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMComponent/JobUpdater/JobUpdaterPoller.py", line 114, in synchronizeJobPriority
    workflowsToCheck = [x for x in self.workqueue.getAvailableWorkflows()]
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Services/WorkQueue/WorkQueue.py", line 117, in getAvailableWorkflows
    {'reduce' : False, 'stale': 'update_after'})
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Database/CMSCouch.py", line 488, in loadView
    (self.name, design, view), encodedOptions)
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 104, in get
    encode, decode, contentType)
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Database/CMSCouch.py", line 120, in makeRequest
    encode, decode, contentType)
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 140, in makeRequest
    encoder, decoder, contentType)
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 251, in makeRequest_httplib
    body=encoded_data, headers=headers)
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-packages/httplib2/__init__.py", line 1436, in request
    (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-packages/httplib2/__init__.py", line 1188, in _request
    (response, content) = self._conn_request(conn, request_uri, method, body, headers)
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-packages/httplib2/__init__.py", line 1123, in _conn_request
    conn.connect()
  File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-packages/httplib2/__init__.py", line 796, in connect
    raise socket.error, msg
error: [Errno 111] Connection refused

This is failing for the local couch access, right?

That's right, I x-checked the code and config used and it's in the local couch access.
Eventually I'll rework this component (I think I kind of did it in 2015, but seemed to have been a bad work :P)

@ticoann code updated. Please review and merge after jenkins complete


Smoke tests are timing out after all tests have succeeded on pr-e2e

Smoke tests are occasionally timing out on pr-e2e, here is one occurrence: https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-main/builds/1001
I managed to hijack the container as the test was timing out and here are my observations:

All the 5 tests have succeeded (there are 5 green dots)
There are no CFOrg/CFSpaces that are created by the smoke test (spaces/orgs created by the test are prefixed with cf-on-k8s-smoke - there were none of these)
The process tree on the container looks like that:

root@8fdd2bf5-86ea-42e5-641d-4f8434de039b:/tmp/build/b815761c# ps auxf
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root        7075  1.0  0.0   4192  3388 pts/1    Ss   09:57   0:00 bash
root        7090  0.0  0.0   8092  3932 pts/1    R+   09:57   0:00  \_ ps auxf
root           7  0.0  0.0   3928  2776 pts/0    Ss+  09:29   0:00 /bin/bash korifi-ci/pipelines/scripts/run-smoke-tests.sh
root         234  0.0  0.0   2844  1992 pts/0    S+   09:29   0:00  \_ make -C korifi test-smoke
root         388  0.0  0.0   4576  3428 pts/0    S+   09:29   0:00      \_ bash ./scripts/run-tests.sh tests/smoke
root         420  0.0  0.1 2497528 18036 pts/0   Sl+  09:29   0:00          \_ go run github.com/onsi/ginkgo/v2/ginkgo --randomize-all --randomize-suites --coverprofile=cover.out --coverpkg=
root         577  0.0  0.0 1311196 9832 pts/0    Sl+  09:30   0:00              \_ /tmp/go-build3129190753/b001/exe/ginkgo --randomize-all --randomize-suites --coverprofile=cover.out --cover
root         818  0.2  0.7 2429636 119008 pts/0  Sl+  09:30   0:04                  \_ /tmp/build/b815761c/korifi/tests/smoke/smoke.test --test.timeout=0 --ginkgo.seed=1700040600 --ginkgo.ra
root           1  0.0  0.0   1056     8 ?        Ss   09:29   0:00 /tmp/gdn-init

The korifi-api logs showed that there are constant requests to /v3/spaces?names=cf-on-k8s-smoke-1-space-327e4684756265db&organization_guids=cf-org-5f6fd550-3de9-4ae4-918d-e4283fb5f625. That is quite weird, as the process tree shows that there is no cf processes running, and the smoke test itself is not talking to the API directly. Who is performing those calls?
Anyway, I saw that cf curl "/v3/spaces?names=cf-on-k8s-smoke-1-space-327e4684756265db&organization_guids=cf-org-5f6fd550-3de9-4ae4-918d-e4283fb5f625" returns an empty list

❯ cf curl "/v3/spaces?names=cf-on-k8s-smoke-1-space-327e4684756265db&organization_guids=cf-org-5f6fd550-3de9-4ae4-918d-e4283fb5f625" | jq .
{
  "pagination": {
    "total_results": 0,
    "total_pages": 1,
    "first": {
      "href": "https://cf.pr-e2e.korifi.cf-app.com/v3/spaces?names=cf-on-k8s-smoke-1-space-327e4684756265db&organization_guids=cf-org-5f6fd550-3de9-4ae4-918d-e4283fb5f625"
    },
    "last": {
      "href": "https://cf.pr-e2e.korifi.cf-app.com/v3/spaces?names=cf-on-k8s-smoke-1-space-327e4684756265db&organization_guids=cf-org-5f6fd550-3de9-4ae4-918d-e4283fb5f625"
    },
    "next": null,
    "previous": null
  },
  "resources": []
}

Should be fixed by: https://github.com/cloudfoundry/korifi-ci/commit/c37f46da7bebe1a8bd1b50ebc3fe57d9f2091488


Display banners and make them configurable

Is there an ETA on this issue? The CNCF marketing team are wanting to get a Kubecon EU banner up on landscape.

Yes, we are aiming at Monday. Actually we prepared a mockup yesterday 🙂

Could you feature just the following banner?

Please link it to
https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/?utm_source=landscape&utm_medium=all&utm_campaign=kubeconeu24&utm_content=slim-banner
You don't need to show Kubecon NA yet as it is a long way off.

@cjyabraham do you have a stable url for that banner that we can use on the CNCF landscape? i.e. if you've pushed it to a GH repo, like the artwork one, we can use the raw url. This will be configurable from the landscape settings file, similarly to the GTM setup.

You can use this one:
https://www.cncf.io/wp-content/uploads/2024/01/kceu24_promo_2400x300.png


changed: disabled Sciter v<IP_ADDRESS> and up incompatible code

Sorry for the late reaction, but I looks it was fixed by Andrew as I can't reproduce the issue in sciter sdk <IP_ADDRESS>. #2


unreachable code after return statement

After firefox update

https://hastebin.com/buqohahare.js

Seems like problem near this modules.


AWS-specific usage documentation for Ambassador

One of the challenges with AWS is wrangling the large number of load balancer options and reconciling that with Kubernetes usage.
To recap... on AWS there are three major load balancing products:

Product
Feature Set
Status

ELBv1 (a.k.a "Classic ELB")
L4 and limited (HTTP/1.1 only) L4, TLS offload
Active

ELBv2 (a.k.a "ALB" or "Application LB"
L7 only, TLS offload
Active

NLB
L4 only; No TLS offload
Active

The history of these products is that "Classic" ELB came first and then ALB and NLB were added much more recently (2016 and 2017).
The ELB is the most generic and feature-rich of the three but it is also hinted at to be deprecated in the future by Amazon. As it is, the ELB system has not received any updates in a long time. Using an ELB as the fronting load balancer also means that:

Healthchecks are global and unconfigurable per the current AWS Kubernetes annotation system.
Stuff like AWS WAF cannot be used to prevent DDOS attacks

Original comment that spurred this issue for more context...
We can't just use ALB's though because Kubernetes does not support those as a type = LoadBalancer service.
ELB now known as "Classic LoadBalancer" ... support for limited-L7 HTTP 1.1, HTTPS 1.1, full-L4 TCP, TCP+TLS and can do TLS offload for you while managing all the certificate work. Doesn't support websocket tho unless you change the configuration to work in TCP or TCP+TLS mode.

ALB is purely for L7 HTTP/HTTPS traffic but it supports HTTP 1.1 and HTTP 2 and WebSockets natively out of the box. However, because it's not a L4 load balancer the Kubernetes folks seem inclined to never make it work as `type = LoadBalancer` on a `v1.Service` so it will only ever work as an Ingress controller (https://github.com/kubernetes/kubernetes/issues/30518). AWS refers to ALB's internally as ELBv2 and the "classic" ELB as "ELBv1" they've also stopped adding features to ELBv1.

NLB is the third LB product from Amazon and is for the pure L4 TCP case. It doesn't suppport TLS off load though so it's kinda annoying.

So in effect what AWS has done is take the old ELB product and split it into two products... ALB and NLB.```

An early goal from us should be to at least document an optimal ELBv1 + Ambassador setup.

We've added a bunch of AWS docs with Ambassador. Closing.