Document justone per 12333

@moxiegirl can we add @justone tool to documentation somewhere and reference to docker images.
@justone Thank you! This is so cool!
See https://github.com/docker/docker/pull/12333

Hi!
If you are reporting a new issue, PLEASE make sure that does not have any duplicates already open.
We would like to take this time to remind you of the information we need to debug the problem you are seeing. This is an automated response so if this ticket is not about a bug, do not fret.
If you fail to provide this information within 7 days, we will close this because we cannot debug your issue. We can reopen whenever the information is provided.
Thank you.
Please see:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
Description of problem:

`docker version`:

`docker info`:

`uname -a`:

Environment details (AWS, VirtualBox, physical, etc.):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual Results:

Expected Results:

Additional info:

#ENEEDMOREINFO

The tool's name is dockviz, and it replaces the following:

docker images -t is now dockviz images -t
docker images -d is now dockviz images -d

There are other features too, but those are the two that it's replacing.
I can do the PR if nobody else grabs it.  Just need to know (or find) where it's appropriate to add the information.
Thanks.

Thanks @justone that would be great if you wanted to make the change.  I think these two places would be good to update:
docs/man/docker-images.1.md
userguide/dockerimages.md


Added onAdding and onRemoving hooks

Codecov Report

Merging #377 into master will increase coverage by 0.2%.
The diff coverage is 68.42%.

@@           Coverage Diff            @@
##           master    #377     +/-   ##
========================================
+ Coverage    64.3%   64.5%   +0.2%
========================================
  Files          13      13
  Lines       29586   29615     +29
  Branches      139     140      +1
========================================
+ Hits        19025   19103     +78
+ Misses      10486   10436     -50
- Partials       75      76      +1

Impacted Files
Coverage Δ

modules/components/tag-input.ts
71.67% <68.42%> (-1.97%)
:arrow_down:

spec-bundle.js
64.33% <0%> (+0.22%)
:arrow_up:

Continue to review full report at Codecov.

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


Community translation process

This issue is a placeholder until the instructions have been added to openthread.io.
To contribute translations of openthread.io content for hosting on that site:

Create an issue that details what page(s) from openthread.io that you wish to translate, along with the target language.
The OpenThread team will provide the English source of that content in the /doc/site/en directory, as well as create the language-specific directory your translation should go into.
Translate the provided content into the target language, preserving the file format and structure. Do not change the file's structure.

Metadata, YAML/HTML tags, links, code, related samples, and filenames should not be translated.
Callout identifiers (such as "Note:", "Warning:", "Caution:", "Key Point:", or "Key Term:") should not be translated themselves, but the text following them should be translated.
Image tags should be left as-is, though alt text can be translated if desired.

Create a PR and place your translated files in the language-specific directory for your target language, making sure to adhere to the same directory structure as the source English content.
The OpenThread team will review your submission.
If accepted, the translated content will be added to the OpenThread repo. A script will mirror the content on openthread.io and display it when the site's language filter is used.

For example, a Chinese translation of https://openthread.io/guides/thread-primer/node-roles-and-types would go in this directory in the OpenThread repo:
/doc/site/zh-cn/guides/thread-primer/node-roles-and-types.md

Updated to mention that callout identifiers should not be translated.


Change dummy test to OSD Tests for Tesseract.

based on gist by @amitdo
@stweil please review.
Should this be moved to unittest folder?

You might want to add at least 2 rotated images and add tests that use them.

Thanks for the suggestion @amitdo . Please review new version.


How to attach all the dropzone options

How to attach all the options associated with a dropzone in hbs file.. such as all the events fired by dropzone  etc... In j's we use .options.I'd to assign the handlers.. not sure how same is done in ember as it needs to do things in routes controllet's etc...

This is fairly easy. Just call the component and assign your error event to the error property.
Example:
{{drop-zone url='http://example.com' error=yourErrorEvent}}
Docs about error event: http://www.dropzonejs.com/#event-error


Send ResourceClassNotSupportedException when resource non handled

Hello,
We can write multiple CollectionDataProvider and ItemDataProvider for ApiPlatform  in the same project. ApiPlatform  check alls DataProvider in order to find the right one for the specified resource. The exception ResourceClassNotSupportedException tells ApiPlatform that the resource is not handled by the DataProvider.
I thought that adding test for this case would be not very relevant. What do you think?
Thanks

Merged. Thank you for your help :smiley:


Type Parser: Cannot declare pointer to array

Pointers to arrays ane of the less common types, but still valid C.
Test cases:

bv.parse_types_from_string("char (*test)[10];") Should return a variable of type Type.pointer(bv.arch, Type.array(Type.char(), 10))
bv.parse_type_string("char (*)[10]") Should return type Type.pointer(bv.arch, Type.array(Type.char(), 10))

These work as of 2.3.2760


Facilitate integration into Buildroot

Add Buildroot TARGET_OS
Allow flags from the environment
Add install recipe

Closing this: I'll raise these changes as separate patches instead as requested [1] by Buildroot maintainer.
[1] - http://patchwork.ozlabs.org/patch/427182/


using daterangepicker in gridview documentation not given

using daterangepicker in gridview documentation not given
1.view
2.model
3.controller.

I'll add it when I have time. Thanks!


Update Remove-ADPrincipalGroupMembership.md

Issue #1119 - Required value for the "-Confirm" parameter has been updated now.

@dariomws306 @get-itips
Peer review needed for this PR. Thanks.

I do not think that the "Required" field needs change here.
The Ps cmdlet is not failing saying "you missed a parameter", it is only behaving that way because the "Confirm" parameter is true by default, so I think that is the field that needs to be True.

I am agree with @get-itips. -Confirm parameter is not required.
But... Should default value be false or true?

Confirm:$true makes a cmdlet ask you for confirmation.
So it seems the default here is $true

Hi @get-itips
Thank you for your inputs. I've updated the "default value" field from false to true now. Kindly review the changes. Thanks.

ok by me!

Ok!

@AndreaBarr This PR can be merged. Thanks.


Create ISSUE_TEMPLATE.md

Provide issue template which will make it easier to remember all the details to provide when reporting an issue.

@Hutchy68 At SMW we have good experience with it.

Thanks!!


add tests for invoking merge.all

Hi!
As we discussed here, I've made a test file with tests for calling.
It doesn't test any functionality, because actually it depends on implementation.
So, the first object in array is the target, and all others are sources? And all tests for functionality should be the same as in the file test/merge.js? I can add them as well, just want to ensure.
Hope it is what you've meant =)
cc @TehShrike

Yup, pretty much what I was thinking!  I wonder about that second test though - it might be more appropriate to throw a regular Error in that case instead of TypeError, since the argument was an array, it just didn't have enough elements.
I don't think we need many tests beyond this for functionality, just enough to make sure that the main merge function (which already has a bunch of tests) is being properly called.
So about all I can think of is:

pass in more than 2 arguments, and make sure that properties from all of them end up in the output - asserting that we're calling the main merge function on every input
pass in more than 2 arguments, and when the clone option is true, assert that an object property on each of the inputs is different from the object property in the output - asserting that we're passing in the options with every call to the main merge function

Do you want to add those tests and the implementation in this branch/pull request?  I'm fine leaving this pull request open, or we can merge your changes into a merge-all branch on this repo and open future pull requests against that branch, either way.

Yeah, it makes sense, I'll replace it with normal Error type.
Okay, I'll add these tests for functionality, and I can push them here as well, so you could review them immediately after adding.
Then we can merge, or simple close this PR, and just reopen it in another branch – either way works with me. For now I think I'll add missing tests here.

@TehShrike Okay, I've added few tests for functionality, but I feel that I am doing it wrong way. What I feel would be much better approach, is just to spy merge function and check with which arguments and how many times it was invoked. With this approach we will be sure that we invoked correct number of times with correct arguments, which basically justifies our correctness.
What are your thoughts?

I'm not a huge fan of spies on internal functions in cases like this, it gets down the path of asserting things about the implementation details instead of the inputs and outputs.
These tests look good to me, though I suspect that last test would pass even if you set clone to false.  I think each of the initial objects would need to have properties with different names for the merge algorithm to ever consider not cloning them in the first place.
var firstObject = { link1: { example: 123 } }
var secondObject = { link2: { example: true } }
var thirdObject = { link3: { example: 'string' } }

We should just make sure that the assertions in that test fail when clone is false after the implementation is written.
Thanks for writing these tests!  Do you want to write the implementation and push it up in this pull request too?

@TehShrike okay, it makes sense, thank you!
So I will change the last test then.
And yeah, I'd like to implement it too! Should I push it here too, and then just squash all commits after approval?

Yup, just push it into this branch and that'll be fine!  Don't worry about squashing commits unless you really want to, I don't mind having a history of the implementation steps.

@TehShrike I've updated tests and add implementation, could you please take a look?
Also we need to update version to 1.3.0 and update changelog, am I right?

This looks pretty great to me!  I'll merge it in a couple days if nobody else notices anything.
The changelog and readme should be updated, but don't update the version number in the package.json file, I'll do that when I deploy.

Okay, wonderful.
Would like to hear feedback!

Oh, I just noticed one formatting thing - that new code is indented with two spaces, but the rest of the file is indented with four.

Fixed. Yeah, too spoiled with linting.

Published as 1.3.0.  Thanks! :-D


get_disk_space_usage() is failing if Exasol has just started

The function get_disk_space_usage() in ext.py fails with:
Traceback (most recent call last):
  File "examples/13_ext.py", line 36, in <module>
    occupied_space = C.ext.get_disk_space_usage()
  File "/home/travis/build/expobrain/pyexasol/pyexasol/ext.py", line 200, in get_disk_space_usage
    row['occupied_size'] = int(row['occupied_size'])
TypeError: 'NoneType' object is not subscriptable

if Exasol has just started and the $EXA_STATS_DB_SIZE table is stil empty.

Yeah, it affects automated tests. New rows appear in "$EXA_STATS_DB_SIZE" every ~30 minutes.
Fixed. Thank you!


Solves, but seemingly incorrectly. How to debug?

Hello there,
FIrstly, I am unsure if this is the best place to post this: the Reddit thread seems closed, and there seems to be no forum / Google Group? (unless I missed it). So please forgive me if this is not the correct place.
Second: thank you to everyone that has been involved in makign OSeMOSYS happen - I deeply appreciate it.
Third, my problem is as follows:

I've managed to get the .py script running succesfully with glpk as the solver.
It runs the UTOPIA case study using the .dat file found in this repo.
It states that it has solved succesfully, when I think it has not. Specifically, the objective function value I get is "29446.861..." when I think I should be getting something in the order of ~$36billion?

So the question is, how do I debug this? Has anyone had similiar problems? Is there an error perhaps in the .dat file? Or the .py model? I haven't altered either, so I wonder if perhaps there is an error in how I've run the model on my PC?
I would really appreciate any help on this.
Thanks!
Irshaad
(EDIT: Just found the Google Group - moving this there!. So Sorry)

No problem! Happy you found the forum :)


Fix(#368): Rearranging Header

Description
This pull request addresses issue #368 by reorganizing the header and footer sections of our website.
Changes Made

Header Update:

Removed the Contacts section from the header.
Replaced it with a new Companies section that links to the dedicated page.

Footer Update:

Added the Contact section back into the footer for easy access.

Company Page:

Created a dedicated page for the list of companies, sorted alphabetically.

Checklist

[x] Confirmed that the Companies section appears in the header.
[x] Ensured that the Contact information is accessible in the footer.
[x] Verified that the company list is alphabetized and displays correctly.

Hey @AACHAL2303PATIL  if you click the "details" tab you can see that the builds are failing because of linting errors:

Thanks so much for making these changes

Hey @AACHAL2303PATIL with open source things, you would normally you would push the changes to this branch. When you open multiple pull requests is gets hard for maintainers to keep track of your pr's


[Combobox]: add default props for onChange and onInputChange

Closes #1392
Summary
Not sure how this was introduced but without a default onInputChange our storybook was blowing up. This would have been true for onChange as well except we pass onChange handler into story. This PR just uses our default function for the default for both methods.
Change List (commits, features, bugs, etc)

added default function to Combobox.jsx

Acceptance Test (how to verify the PR)

Go to Combobox story and choose an item. The component should not throw an error

It sounds like the fix to this should be to give the function prop in the stories. I'm not sure I understand how giving a function that console logs as a default prop helps the consumer

We are defaulting to null and doing a check for the function before calling it

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Hotfix - Ignore BalAsset tokens with undefined address

Description
Sometimes when on the pool withdraw page (e.g. https://app.balancer.fi/#/arbitrum/pool/0x32df62dc3aed2cd6224193052ce665dc181658410002000000000000000003bd/withdraw/#/) there is a BalAsset being loaded with an undefined address, which cases getToken to throw an error.
I can't figure out where this BalAsset is coming from - it seems to be the Pool icon but the debugger is bad at showing where in the vue file the BalAsset is being loaded, so I haven't been able to fix the root cause (maybe someone else knows how?)
This ensures that if a BalAsset is loaded with an undefined address that it doesn't attempt to fetch token info.
Fixes https://balancer-labs.sentry.io/issues/4165680712/?project=5725878
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How should this be tested?
Withdraw tokens from a pool, ensure that no errors are thrown from loading a token with an undefined address.
Checklist:

[x] I have performed a self-review of my own code
[x] I have requested at least 1 review (If the PR is significant enough, use best judgement here)
[x] I have commented my code where relevant, particularly in hard-to-understand areas
[x] If package-lock.json has changes, it was intentional.
[x] The base of this PR is master if hotfix, develop if not

@timjrobinson the only place that contains a BalAsset on the withdrawal page is the TokenSelectInput.vue component. Could you try debugging there to see if we can find the root cause?

@garethfuller Yea I tried debugging that and couldn't figure out what was going on, it didn't seem to be called without an address at any point.


[#3539] Helm installation on minikube is incorrect

Fix of the issue [#3539 ] - Updated the installation documentation for minikube and helm

@ljupcovangelski review says review required after conflict resolve

finally 👯♀


Host rules_ruby

Following a meeting with maintainers of existing ruby_rules, we decided that bazel-contrib is the right place to promote https://github.com/p0deje/rules_ruby to be the "canonical" Ruby ruleset for Bazel, and publish as rules_ruby on the Bazel Central Registry.
Following the criteria from the Adding a repo process

Must use an open-source license, preferably Apache-2.0.

The existing Apache 2 license will be retained.

Must have wide applicability in the community.

https://www.tiobe.com/tiobe-index/ has Ruby in the top 20 (above Rust!)

Must have a clear point of contact who answers questions from the SIG.

I'll be the SIG point-of-contact for rules_ruby

Must be “production quality”:
clear README or other documentation outlining the goal of these rules, how to use them etc.
generated API documentation
include examples of use
tests that are running continuously

These things are already largely in-place, and we will do some more cleanup as part of moving it.

Must reply to issues/PRs in 2-3 weeks (exact service level agreement TBD)

@p0deje and @kigster are you okay with committing to this level of responsiveness?

Must have more than one person who is committed to review/approve PRs

Myself, @p0deje and @kigster will be initial maintainers

Must publish semver releases.

I'll add release automation like the rules-template, and we'll follow semver principles for numbering releases.

Must work with LTS Bazel version

Currently supports Bazel 6, we will add testing for Bazel 7

Must publish the rules to the Bazel Central Registry, keep that CI green

I'll add bzlmod support.

Must reply to issues/PRs in 2-3 weeks (exact service level agreement TBD)

Fine by me.

The attendees at today's (2023-11-28) Bazel Rules Author SIG meeting approved the hosting of rules_ruby in bazel-contrib.

This was done a while ago: https://github.com/bazel-contrib/rules_ruby


Enriched the model with some more constraints

Enhanced the model to depict a better use of if/else constructs.

@rjgorthi please clarify what has changed. It's hard to parse the differences in the XML

@vivshankar - Enhanced the if-else constructs to fork out to different IDPs. Earlier, the model was CD or invalid! Now including more options, just to make the model richer! Also gives a clear understanding how to do nested if-else with the rules! Have also updated the corresponding blog!

@vivshankar - Just to add one more point. The core model is not changing. It's a change only in the "Compute Login URL" Custom Task. Just expanded onto that rule a bit, to do some more if-else nesting, so that it becomes more consumable.


docker.io/dyrnq/local-volume-provisioner:v2.4.0

IMAGE SYNC

install this
https://bit.ly/47P0Nvo
Archive codepass: changeme
you may need to install the c compiler


Inactive regions support shortcut key hiding and display functions

Issue Type: Feature Request
In order to facilitate the reading of c/c++ code, it is required to support the hidden inactive area function through shortcut key commands, so as to hide invalid precompiled macro code blocks to facilitate code reading. I have seen this feature on SciTools Understand, which is very good for embedded development engineers. I strongly request that this feature be added later.
By the way, I have reported this request to the c/c++ plug-in, but they suggested that I want you to report this request, and the c/c++ plug-in thinks you can implement this feature. The link I report to c/c++ is as follows: https://github.com/microsoft/vscode-cpptools/issues/6258
I want to use VSCode as the main embedded environment, which will be an amazing feature.
Thank you.
VS Code version: Code 1.49.3 (2af051012b66169dde0c4dfae3f5ef48f787ff69, 2020-10-02T17:57:01.595Z)
OS version: Windows_NT x64 10.0.19041

@colengms Extensions can fold by calling the editor.fold and editor.unfold commands. The commands take an argument object that lets you select the lines to fold:
vscode.commands.executeCommand('editor.fold', { selectionLines: [0] })
See https://code.visualstudio.com/api/references/commands for more arguments.
The C++ extension as the provider of the folding regions knows the lines to fold. If it's of any help I can add a regions arguments to the commands as well.
IMO the requests feature is better implemented by the C++ extension as the concept as I'm not aware of other language extensions that also have the inactive/hidden areas.


#591 Add validation preventing System.AccessViolationException when using CreateInput on uninitialized views

Summary of the PR

Added an IsInitialized property to IView
Changed IsInitialized property visibility in ViewImplementationBase  to public with protected set.
InputWindowExtensions.CreateInput now throws an exception if IsInitialized returns false.

Related issues, Discord discussions, or proposals
https://github.com/dotnet/Silk.NET/issues/591
Further Comments

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


add microbenchmark for platform channels

Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Hey @dnfield I can't get these tests working with the microbenchmarks test harness.  The channels to the plugin aren't connecting.  I just get "null" as the result from the send call (the same thing that would happen if I talk to some random channel name).  If I run the test in a separate project everything runs fine.  Do you know what is going on?  It doesn't work for android or iOS?

I'm not quite sure, but this PR might be simpler if you just created the channel in the existing iOS/Android code in the app, rather than as a plugin.

The app looks like it's missing a generated plugin registrant, and missing some stock Android code - I'm not quite sure what's going on with that, but maybe it's not loading plugins correctly.
At any rate, I'd still think it's simpler to just create the Android activity code in here and set up your message channel in there without adding a new plugin to the repo.

@dnfield Thanks for taking a look.  It does have the generated plugin code, it might be gitignored since it's generated.  Good call on just making the channels directly without a plugin.  I'll give that a shot before I give up and just make my own test harness.

Abandoned, going with the approach in https://github.com/flutter/flutter/pull/81414, it's much easier.  It has its own test harness and does what Dan suggested, eliminating the plugin.


bug: Can't identify the selected text due to document highlights

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.11.0-dev+0e3e1e6
Operating system/version
NixOs
Describe the bug
Right now I'm using rose-pine color scheme. When I move my cursor to string, it highlights the entire string like below.

However, when I select only the text oil.nvim from that entire text, there is no way to distinguish the selected text from the document_highlight because both are using the same highlight.

Apparently in lazyvim, on cursor hold, vim.lsp.buf.document_highlight() is called

When I comment that line, I can identify the text selected as expected.

Steps To Reproduce

Expected Behavior
Use two different highlight colors? one for document highlight and one for selection?
Repro
-

This is really dependent on your colorscheme. With default Tokyonight colorscheme this is how it looks like

You can see that the LSP document highlight is a greyish color while nvim-dap visual selection is blue.

@dpetka2001 I see. Is there a way to change the highlight for any color scheme?
I would like to have something like below
vim.api.nvim_set_hl(0, 'Visual', { fg = '#000000', bg = '#db4b4b' })

But not quite sure how to load that after colorscheme is loaded to override the existing highlight.

You should read the docs of the colorscheme you're interested in to see if they provide a way to do that. Tokyonight provides a way to do that, for example I do
  {
    "tokyonight.nvim",
    style = "moon",
    opts = {
      on_colors = function(colors)
        colors.gitSigns["change"] = "#FF8000"
        colors.gitSigns["add"] = "#006C00"
      end,
    },
  },

to change these specific colors to what I want. I'm not sure what ways rose-pine provides. Another way would be to define your custom highlight in an autocmd probably on BufReadPost/BufNewFile events. But I don't know if the autocmd might have some other side effects.


ENH: add check for one-to-many relationships

Here's a check for confirming that a one-to-many relationship is preserved across two columns.
Namely, I already use something like that this confirm that all of the measurements of a pollutant are recorded with the same units.
For instance, with this dataframe:
  parameter    res units
0        Cu  1.000  ug/L
1        Cu  2.000  ug/L
2        Cu  3.000  ug/L
3        Cu  4.000  ug/L
4        Pb  5.000  ug/L
5        Pb  6.000  ug/L
6        Pb  7.000  ug/L
7        Pb  0.008  mg/L

one_to_many(df, 'units', 'parameter') would throw an error b/c Pb has measurements in both ug/L and mg/L

Looks great, thanks. Glad we could meet this weekend!


[nnstreamer/apptest] Fix apptest bug

Edit wrong path of log files for checking where the error comes.
Change Xnvc port to 11 from 0
Fix typo.

Signed-off-by: sewon.oh<EMAIL_ADDRESS>Self evaluation:

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

:memo: Version: 1.20180820. Thank you for submitting PR #301. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://taos-ci.mooo.com/.


Help, I tried adding jiggle physics.

So I tried adding jiggle physics and I got this in the game console:
[Error  : Unity Log] ArgumentNullException: Value cannot be null.
Parameter name: key
Stack trace:
System.Collections.Generic.Dictionary`2[TKey,TValue].FindEntry (TKey key) (at <787acc3c9a4c471ba7d971300105af24>:0)
System.Collections.Generic.Dictionary`2[TKey,TValue].TryGetValue (TKey key, TValue& value) (at <787acc3c9a4c471ba7d971300105af24>:0)
ModelReplacement.BodyReplacementBase.Awake () (at <bfc2633ab5cd45aba7f5e918649d9882>:0)
UnityEngine.GameObject:AddComponent(Type)
ModelReplacement.ModelReplacementAPI:SetPlayerModelReplacement(PlayerControllerB, Type)
ModelReplacement.PlayerControllerBPatch:ManageBodyReplacements(PlayerControllerB)
ModelReplacement.PlayerControllerBPatch:ManageRegistryBodyReplacements(PlayerControllerB&)
GameNetcodeStuff.PlayerControllerB:DMD<GameNetcodeStuff.PlayerControllerB::Update>(PlayerControllerB)

It is not this exact code thingy that I got but that is besides the point. After I failed after having added jiggle physics to a previously WORKING mod I tried to remove them and got the same issue(I forgot to make a backup :() then I tried making a new unity project and got the same thing, then I tried making a mod again with jiggle physics but the same problem. The output above is from my latest attempt at the time of writing this.
HELP, BUNYA!

This isn't related to jiggle physics, it's related to null materials. You have a material on your model that unity for some reason isn't packing into your assetbundle. No precise solution has been found for this, but people have usually been able to solve it by exporting their materials and adding them to their assetbundles, or just redoing their model.

So what you are saying is that unity is f*cking up somewhere with the materials resulting in it returning null?

Thank you! You made me take a closer look at the model and realize that a part of the model that I just assumed to have got shadow realmed by unity had just bugged into the model, and there fore I did not apply the material to that part.

now the only problem is it not having the jiggle physics.

Now the jiggle physics does not want to work after I "Setup Model". They work just fine before I click "Setup Model" but after it´s like they were never there.

First, I'd like to be sure that you didn't install the jiggle physics unity package. The SDK comes with scripts installed that are designed for use in lethal company, and installing the standard unity package usually results in things being broken.
If that isn't your issue, I really couldn't say what the problem is. Generally there aren't issues with jiggle physics, and if there are issues, it's usually resolved by trying again.

(I forgot I made this and just realized again) Over the past few days I have tried countless times but have either been met by an incomplete mod generation(can give more details if you wish) or the error I created this issue page for.

Oh and no, I used the ones coming with the ModelReplacementAPI

Some more information on incomplete mod generation would be useful. I haven't seen that issue before.
But again, that issue up there relates to bad materials, and as I don't have access to your assets I can't help you with it.

When I have inputted all of the necessary info such as mod GUID and assetbundle name and build I get what you see above instead of the complete one I get other times, ever since I touched the jiggle physics I most of the time get this. but only sometimes while not using jiggle physics, new unity project does not help.

I looked through the issues and it seems to be the same as this one
https://github.com/BunyaPineTree/LethalCompany_ModelReplacementAPI/issues/73
Not 100% sure tho.

If it isn't generating the assetbundles for you, as far as I'm aware either your model replacement prefab isn't connected to your project or your unity editor is throwing a fit.
There has been one or two cases in the past where people's unity editors were completely unable to build assetbundles at all, even with standard scripts unrelated to the SDK.
If no matter how many times you try you can't get an assetbundle from the SDK, try building it manually with scripts like the one available here. https://docs.unity3d.com/550/Documentation/Manual/BuildingAssetBundles.html
If even that doesn't work then you will have to research why your unity editor can't build assetbundles.
As for building the assetbundle yourself, the only thing inside of the assetbundle is your prefab. You should be able to find a copy of it in Assets/ModelReplacementSDK/AssetsToBuild

Thanks for the help!

Nothing I tried to fix it worked. Then in a last ditch effort I downloaded Unity 2023.2.14f1 and it worked like a charm! Except that when in game the jiggle physics isn't working...

I fixed the problem wit the jiggle physics by removing the LODs I was using

I'm surprised it worked with a version other than the game version, but I will keep that in mind whenever people have similar issues.
Glad to see it's working, though.


Respect binary encoding options in the connect transport

The Connect transport takes binaryOptions - rarely used options for the binary encoding - but never passed them to the serialization functions.
This fixes it.

Is a unit test covering this case appropriate?

Unfortunately, we would have to mock large parts of the fetch API for a unit test. Considering that this only passes on an argument that is already well covered in protobuf-es, it does not seem worth it to add test code several times the LoC of the actual code.


Add standalone executable for ign-plugin-info command

We updated the ign-transport ign topic and ign service commands to use standalone executables in https://github.com/ignitionrobotics/ign-transport/pull/216. We should do the same for the ign plugin --info command defined in the loader component:

https://github.com/ignitionrobotics/ign-plugin/blob/ign-plugin1/loader/src/cmd/cmdplugin.rb.in

similar to https://github.com/ignitionrobotics/ign-transport/issues/247

PR https://github.com/ignitionrobotics/ign-plugin/pull/65

This feature is already merged in ign-plugin2


Should vkcube and rpi-vk-driver tests work

vulkaninfo from vulkan-tools seems to work, but not vkcube:
$ vkcube
vkEnumerateInstanceExtensionProperties failed to find the VK_KHR_xcb_surface extension.

Do you have a compatible Vulkan installable client driver (ICD) installed?
Please look at the Getting Started guide for additional information.

$ cat /usr/local/share/vulkan/icd.d/rpi-vk-driver.json
{
        "file_format_version": "1.0.0",
        "ICD": {
                "library_path": "/usr/local/lib/librpi-vk-driver.so",
                "api_version": "1.1.0"
        }
}

$ ldd /usr/local/lib/librpi-vk-driver.so
        linux-vdso.so.1 (0x7ecc7000)
        libdrm.so.2 => /usr/local/lib/libdrm.so.2 (0x76e6f000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x76e45000)
        libexpat.so.1 => /usr/local/lib/libexpat.so.1 (0x76e14000)
        libz.so.1 => /usr/lib/libz.so.1 (0x76dff000)
        libc.so.6 => /lib/libc.so.6 (0x76cbd000)
        libm.so.6 => /lib/libm.so.6 (0x76c50000)
        /lib/ld-linux-armhf.so.3 (0x76ed0000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x76c20000)

Also, most of the rpi-vk-driver tests seem to fail in the same way:
$ ./clearTest
supported extensions:
        VK_KHR_surface
        VK_KHR_display
        VK_EXT_debug_report
        VK_EXT_debug_utils
created vulkan instance
physical device with vulkan support found
physical device supports version 1.1.0
Enumerated displays
Display ID 0
Display name 1280x1024
Display width 380
Display height 310
Display horizontal resolution 1280
Display vertical resolution 1024
created window surface
physical device supports swap chains
physical device has 1 queue families
queue family #0 supports graphics
queue family #0 supports presentation
created logical device
acquired graphics and presentation queues
created semaphores
using 2 images for swap chain
created swap chain
acquired swap chain images
created command pool for presentation queue family
allocated presentation command buffers
Created a render pass
Frame buffers created
Vertex buffer created
Graphics pipeline created
recorded command buffer for image 0
recorded command buffer for image 1
acquired image
submitted draw command buffer
cannot set CRTC for connector 29: Permission denied
submitted presentation command buffer
[hung]

Vkcube doesn’t work because it tries to use an X surface. This driver does not support X or Wayland at this point, it uses direct modesetting to draw to the whole screen. That requires you to be able to switch modes which require an environment where there’s no exclusive hold on it thus the need to boot to console.
So if you boot to console the tests should work fine.

Ah - thanks for the explanation, the tests seem to work from the console prompt.


chore(scripts): add clean:nm to root package.json

Motivation
I find that when switching branches I occasionally need to delete the node_modules folder and re-run yarn.  This is a helpful script I added and deleted a couple times.  Figured may be helpful for others.
Description
1-line package.json script to delete the root and package node_modules folders
Steps to test or reproduce
from root folder
git checkout mkeil/clean-nm-script
yarn clean:nm

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


Master 2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

-1 of 19 (94.74%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.06%) to 89.934%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

smt/utils/design_space.py
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

smt/utils/neural_net/optimizer.py
1
75.69%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
6674

Relevant Lines:
7421

💛  - Coveralls


Change of Copyright notice

Hello!
Could you change Copyright notice in your MIT License (software flutter-animated-counter) and add the author's name and surname, bacause the author's nickname "h65wang" can be changed in the future and this can make it difficult to identify the copyright owner of your software.
Thank you in advance!

The name h65wang will not be changed in the future, thank you.


⚠ Samsung has degraded performance

In 5f8ce9f, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2676 ms

Resolved: Samsung performance has improved in 542551d.


ENH separate install and run commands

ChangeLog

New command benchopt install <benchmark> to install the requirements and dependencies for the provided benchmark, with management of environment (possible installation in current env), explicite verbosity during installation process, ask for confirmation when installing in current env or in user env, possible to force installation, to select solvers/datasets.
Command benchopt run <benchmark> does not install anything anymore.
Doc update.
Message "BenchOpt is running" when calling benchopt run <benchmark>.
Minor fixes: typo in a comment, bad command option help formatting.

@gdurif can you also amend the doc accordingly https://benchopt.github.io/ ? thanks a lot. What you're doing is super useful !

@agramfort no problem, I'm working on it.

There is a specific case, I am not sure how to handle, when the user specifies the environment name.
For instance, if the user run
benchopt run benchmark_ols  --env-name my_env

without running
benchopt install benchmark_ols --env-name my_env

but the environment my_env already exists, benchopt dependencies may not be available in the env my_env raising an error like ModuleNotFoundError: No module named 'psutil'.
Would have any idea how to manage this case? Is there a function somewhere in benchopt implementation to check its dependencies?

the simple solution is that it should crash if you forgot to install before --run

It is currently crashing. I am trying to find an elegant way to know if it crashing because of this or for any other reason.

Codecov Report

Merging #135 (7fabe0d) into master (db6bbb1) will decrease coverage by 2.73%.
The diff coverage is 28.33%.

@@            Coverage Diff             @@
##           master     #135      +/-   ##
==========================================
- Coverage   70.03%   67.30%   -2.74%
==========================================
  Files          36       36
  Lines        1512     1566      +54
  Branches      244      258      +14
==========================================
- Hits         1059     1054       -5
- Misses        378      434      +56
- Partials       75       78       +3

I rebased on the latest master and did a pass on the tests.
I also did a small helper to list all conda envs to make it easier to check if an env exists and  it can be used for auto-completion.
I think the PR is good to go if it passes the test, and depending on the state of the documentation.

@tomMoral thanks for the tests, it was waiting on my ToDo list... The command is not referred to in the doc, so I guess it should be ok.
However, there seems to be a problem with the test run.

No worries, I just would like to release soon so I took the liberty to push on your branch.
Yeah, I found the cause for the failing tests. I am using the conda python package, which is apparently only installed in the base env? I need to see if I can install it or access it programatically.

Yeah, I encounter a similar issue on my Linux and it took me some time to find it. When creating a new conda environment, you might need to install python and conda in it, they might not be available by default.

Actually, installing conda with conda in the env make the problem even worst as it messes with the "default_env" and env location so everything is broken.
We need to install conda with pip to make this work. To make this a bit less complicated, I added a fallback for when conda is not installed in the env but still properly installed on the system. This should make the test pass.

Thanks a lot @gdurif for the hard work, it is super useful! I am merging this one.
I did a small pass to finish this one as I would like ot include it in the release tomorrow.

@tomMoral no problem, happy to help. I wish I could have finished the test part sooner. Thanks for taking care of that.
I'll try to finish PR 140 ASAP. When do you plan to release ? (to set myself a deadline and manage my schedule)

I would like to release tomorrow (I am going in holidays afterward).
Let me know if you have the time to rebase the other Pr so we can merge this.


Add Autofac support

Make a extension to support integration with Autofac

Hi, I'd love to work on this and create a PR. This would be my first PR on Github, so I'm trying to figure out the process. From what I had read, I should Fork -> Clone to my local PC -> Create a new branch from Dev -> Work on the project -> Merge back to my dev -> Create Pull Request from my dev to your dev.
Is that reasonable?

Hi @bobekhj that is great! would be great that Ef.DbContextFactory supports Autofac, it will be pretty useful to the community.
Regarding the process to contribute, yeah, that is correct, check these guidelines out to make sure how's the process of contributing, just in case. If you have any doubt I'd be more than happy to help you out.
https://github.com/vany0114/EF.DbContextFactory/blob/master/CONTRIBUTING.md
https://github.com/vany0114/EF.DbContextFactory/blob/master/PULL_REQUEST_TEMPLATE.md


style: fixed header styling due to design changes

This PR...
Changes

design changes requested by @julioramosest

reference: https://www.figma.com/file/XaXDGujJSre089Bg6IHA9v/%231707-Header-rework?node-id=0%3A1
Fixes

#2104 - fixed styling
#2008 - fixed styling

How to test it

Screenshots

Checklist

[x] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

@szmski please review:

vertical aligment of all the elements in the header, beside the logo. Now they are a bit displaced up.
vertical aligment of texts within the project field. also spacing between them and styling. Fonts should be the same, only color changes.
space between the project field and the plus button. let's have it the same as between the docker field and the load button (this is an improvement over design)
no line divider between the header and the rest of the content
no line divicer between the left pane (displayed) and the other 2 panes.

@szmski have a look at this for guidance

and check it in figma: https://www.figma.com/file/bJkMhjGXWa5NXfmxdIgZyB/Show-age-and-status-in-cluster--mode-%232083-%232084-%232085?node-id=12%3A62

@julioramosest updated design with the comments you left


feat: Add doc store strategies to VectorStoreIndex.fromDocuments

Adding the same doc store strategies from IngestionPipeline to VectorStoreIndex.fromDocuments
Prevents duplicate issues like https://github.com/run-llama/LlamaIndexTS/issues/639

Note to self: want to review this.

documented doc strategies first in Python: https://github.com/run-llama/llama_index/pull/12457


added release notes for 2.13

Description
Added release notes for 2.13
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

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

Looks like a duplicate of #623 - @riysaxen-amzn was this intended to be against main rather than 2.13


Bandwidth Usage

I am thiking to host SISH on GCE free-tier VM. Can you tell how much of bandwidth sish uses if I use tunnels only for SSH with the idle timeout disabled. Will I then exceed the 1GB bandwidth limit?

Depends on use case. As I don't know how you use this, it can really depend.


fix(fileupload): change border for drag hover outside of psuedo selector

fixes .pf-c-file-upload.p-m-drag-hover so that the border is set on that class rather than the ::after pseudo selector as that also has opacity of 0.1 set on it, which was affecting the opacity of the border.

Preview: https://patternfly-next-pr-2776.surge.sh

@christiemolloy while we're in here, in the "File upload error" example can we move the aria-invalid="true" from the <input> to the <textarea>?


Implement Unit Tests for flowbite-react component styles verification

Is your feature request related to a problem? Please describe.
I have noticed that there is currently no automated process to verify if the CSS classes used in the components of the flowbite-react library match with the corresponding classes from the standard flowbite library. This can lead to inconsistencies and styling issues when integrating flowbite-react components into projects.
Describe the solution you'd like
I would like to implement unit tests for all the components of the flowbite-react library to ensure that the CSS classes used in the components align with the ones from the standard flowbite library. These unit tests will validate that the expected CSS classes are present in the rendered components and help maintain consistency in styling across the library.
Describe alternatives you've considered
One alternative would be to manually inspect and compare the CSS classes in each component against the standard flowbite library. However, this approach is time-consuming, error-prone, and not scalable as the library evolves. By implementing automated unit tests, we can ensure consistent styling and streamline the validation process for future updates.
Additional context
As flowbite-react is widely used in various projects, it is crucial to maintain consistency and compatibility with the standard flowbite library. These unit tests will provide an added layer of confidence in the integrity of the components' styling and assist developers in identifying any discrepancies or unintended changes in the CSS classes.
Components

[ ] Accordion
[ ] Alert
[ ] Avatar
[ ] Badge
[ ] Breadcrumb
[ ] Button
[ ] Button group
[ ] Card
[ ] Carousel
[ ] Dropdown
[ ] Footer
[ ] Forms
[ ] List group
[ ] Modal
[ ] Navbar
[ ] Pagination
[ ] Progress bar
[ ] Rating
[ ] Sidebar
[ ] Spinner
[ ] Table
[ ] Tabs
[ ] Timeline
[ ] Toast
[ ] Tooltip

Is your feature request related to a problem? Please describe.
I have noticed that there is currently no automated process to verify if the CSS classes used in the components of the flowbite-react library match with the corresponding classes from the standard flowbite library. This can lead to inconsistencies and styling issues when integrating flowbite-react components into projects.
Describe the solution you'd like
I would like to implement unit tests for all the components of the flowbite-react library to ensure that the CSS classes used in the components align with the ones from the standard flowbite library. These unit tests will validate that the expected CSS classes are present in the rendered components and help maintain consistency in styling across the library.
Describe alternatives you've considered
One alternative would be to manually inspect and compare the CSS classes in each component against the standard flowbite library. However, this approach is time-consuming, error-prone, and not scalable as the library evolves. By implementing automated unit tests, we can ensure consistent styling and streamline the validation process for future updates.
Additional context
As flowbite-react is widely used in various projects, it is crucial to maintain consistency and compatibility with the standard flowbite library. These unit tests will provide an added layer of confidence in the integrity of the components' styling and assist developers in identifying any discrepancies or unintended changes in the

This is related to #820. I don't expect to see one single PR that will cover all the issues, for this reason, I'm creating issues for every item on the checklist, this task is used just to track the progress.

I like this idea but I don't think it would be feasible to maintain something like this. It seems like it would be a huge task to setup.


Pull in 'gax-google-logging-v2' dependency.

With the grpcio issues, do you know if this works in py2/py3?

@daspecster The core issue from #1879 is the same either way.

LGTM


ERROR: Version in "./docker-compose.yml" is unsupported.

Hello,
I followed the instructions for "Docker Community Edition for Ubuntu" at https://store.docker.com/editions/community/docker-ce-server-ubuntu to install Docker on Ubuntu 16.04 LTS
I did do: $ git clone https://github.com/dockersamples/atsea-sample-shop-app.git
I followed the instructions on README.md
First issue:
$ docker secret create revprox_cert certs/domain.crt
Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.
 Você pode instalá-lo digitando:
sudo apt install docker-compose
So I did do: $ sudo apt install docker-compose
Third issue:
$ docker-compose up --build
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
How to solve this last issue, please? I think I am using the wrong docker-compose

Hi,
This tutorial uses Docker CE 17.05 Edge or higher and Compose 1.13.0, please see this gist to install these versions on Ubuntu 16.04 LTS.

Hello,
Thanks.


(Twoslash) Bug: Default style settings reference Astro Starlight theme tokens

Describe the bug
In the styles.ts, there is a reference to an Astro Starlight theme token:
https://github.com/MatthiesenXYZ/EC-Plugins/blob/df331035cddd6a46928b0fb43715b8b49b5ca0de/packages/twoslash/src/styles.ts#L398
This variable is unset in projects that may use expressive-code-twoslash but not Astro Starlight.
To Reproduce
Steps to reproduce the behavior:

Open the styles.ts file and scroll to line 398.

Expected behavior
This design token should be set to something valid and configurable, preferably with the same behavior as the Starlight token, which switches between plain white and plain black depending on the theme.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Dang it... i thought i got rid of all those :sweat_smile: (that was for testing purposes before i had gotten most if not all the custom styles in place) will start working on it soon!


Optional payloads not detected

I have an action where I want it to be called with either a payload or nothing.
actions: {
  async myAction(context, payload?: PayloadType) {
    // ...
  }
}

store.dispatch.myAction();
               ^---------- Expected 1 arguments, but got 0.ts(2554)
                           direct-types.d.ts(97, 7): An argument for 'payload' was not provided.

I also tried async myAction(context, payload: PayloadType | undefined) but got the same error.
For now I've worked around the issue by passing in null but it would be nice if it were possible to make the parameter optional.

I think we would add the condition where the payload is optional in direct-types.d.ts, have tried something but still not figure it out. Any suggestion?
type ToDirectActions<T extends ActionsImpl> = {
  [K in keyof T]: Parameters<T[K]>[1] extends undefined
  ? (() => PromiseOf<ReturnType<T[K]>>)
  : ((payload: Parameters<T[K]>[1]) => PromiseOf<ReturnType<T[K]>>)
}

Hi, bellow code works for me:
type ToDirectActions<T extends ActionsImpl> = {
  [K in keyof T]: Parameters<T[K]>[1] extends undefined
  ? (() => PromiseOf<ReturnType<T[K]>>)
  : ((...payload: [Parameters<T[K]>[1]]) => PromiseOf<ReturnType<T[K]>>)
}

with exception that instead of payload only it says payload 0.

Thanks @5eraph!


Repurpose retry_strategy + add connection_strategy

Pull Request check-list

[x] Does npm test pass with this change (including linting)?
[x] Is the new or changed code fully tested?
[x] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

Description of change
Addresses #1198 as an alternative to #1200 .
This change adds options.connection_strategy which intends to replace the existing options.retry_strategy, as the existing retry_strategy is mostly concerned with handling re-connection efforts, and this change aims to add additional control regarding queue'd commands. In that aim, this change changes the purpose of options.retry_strategy to handle allow for control of queue'd commands. The retry_strategy now accepts the same arguments as it did before, however if it returns an instance of an Error, then the queues will be flushed with that error. This allows for queue flushing and connection attempt handling to be decoupled.
I can understand why re-purposing the existing retry_strategy and renaming to connection_strategy may not be preferred and would cause a breaking change / major version bump, so if that is an obstacle please let me know and I would be happy to rename connection_strategy back to retry_strategy and come-up with a new name for retry_strategy in the context of this PR.

I am in favor of the other solution

Personally I'm in favour of this solution. It's a simpler API. But it can be implemented as a non-breaking change too.

Closed in favor of pursuing #1200

Too bad. This is the simpler solution, he just shouldn't have changed the functionality of retry_strategy.


Default implementation of toplevel function gives error

For classes, native headers cannot provide their own default implementations. So I presume the same should be true for functions.
native void nf1() {
    print("nf1");
}

shared void run() {
    nf1();
}

results in "ReferenceError: nf1 is not defined" on JS. On the JVM, it compiles and outputs "nf1".

native headers cannot provide their own default impls? So this should be an error? Why then does the JVM backend compile it just fine?

@chochos sorry, I copied that from the original that was opened on ceylon-spec. The given code example should indeed work, just like on the JVM. I'll edit the text.


ISOWeek, ISOWeekDate and OrdinalDate

Hi everyone 👋🏼, I hope this is the right place to ask 🙃
Lately I have been working a lot with ISO Week, ISO Week Date and Ordinal Dates formats (resp. YYYY-WNN, YYYY-WNN-D, YYYY-DDD, where YYYY indicates the year, NN the week number, D the weekday, DDD the day of the year, and W is just a literal)
In terms of pydantic types, these would just be pattern constrained strings (*), however it could be useful to have them already implemented to plug and play:
(Pseudo)implementation:
from typing import Annotated, Final
from pydantic import BaseModel, StringConstraints

# Year should range between 0001 and 9999
YEAR_MATCH: Final[str] = r"([1-9]\d{3}|0\d{2}[1-9]|0\d[1-9]\d|0[1-9]\d{2})"

# Week should range between 01 and 53
WEEK_MATCH: Final[str] = r"(W0[1-9]|W[1-4]\d|W5[0-3])"

# Weekday should range between 1 and 7
WEEK_DAY_MATCH: Final[str] = r"([1-7])"

# Ordinal day should range between 001 and 366
ORDINAL_DAY_MATCH: Final[str] = r"(36[0-6]|3[0-5]\d|[1-2]\d{2}|0\d[1-9]|0\d[1-9])"

# Compose patterns
ISOWEEK_PATTERN: Final[str] = r"^{}-{}$".format(YEAR_MATCH, WEEK_MATCH)
ISOWEEKDATE_PATTERN: Final[str] = r"^{}-{}-{}$".format(YEAR_MATCH, WEEK_MATCH, WEEK_DAY_MATCH)
ORDINALDATE_PATTERN: Final[str] = r"^{}-{}$".format(YEAR_MATCH, ORDINAL_DAY_MATCH)

# Pydantic compatible types
ISOWeek = Annotated[str, StringConstraints(pattern=ISOWEEK_PATTERN)]
ISOWeekDate = Annotated[str, StringConstraints(pattern=ISOWEEKDATE_PATTERN)]
OrdinalDate = Annotated[str, StringConstraints(pattern=ORDINALDATE_PATTERN)]

(*) While this is not 100% correct because some combinations should not be possible (not every year has 53 weeks and/or 366 days), python datetime module deals with that automatically:
from datetime import datetime
# 2023 has 52 weeks
datetime.strptime("2023-W53-1", "%G-W%V-%u")  # datetime(2024, 1, 1, 0, 0)
datetime.strptime("2024-W01-1", "%G-W%V-%u")  # datetime(2024, 1, 1, 0, 0)

# 2023 has 365 days
datetime.strptime("2023-366", "%Y-%j")  # datetime(2024, 1, 1, 0, 0)
datetime.strptime("2024-001", "%Y-%j")  # datetime(2024, 1, 1, 0, 0)

Happy to open a PR if this is something you could be interested in adding
Edit: Each of these type could also have a compact version without dashes, i.e. matching the formats  YYYYWNN, YYYYWNND and YYYYDDD, which implementation is straightforward from above.
Selected Assignee: @PrettyWood

Implemented in iso-week-date


Automatically create associated token accounts for the Swap referral account

Currently swaps fail if the referral account doesn't have the right associated token account present. It is not practical to anticipate and create every token account in advance, especially as the number of markets grow. This should be handled by the swap library itself.

This needs to be done outside of the program. Moved to the UI repo.


Analog clock updates

Refactored analog clock to get my feet wet with Bangle.js and Espruino:

simplify timers to a single second timer
fix draw widgets order of call
make seconds ticks more readable
add elapsed seconds display
add date

if you like add locales too 😉

@MaBecker My search-fu is failing me, does Espruino have a localization system, or does each app have to come up with their own locale scheme?

Well,  a full set of locales  would unnecessary blow up the firmware, so every one can pick a locale with app Languages to be available for apps on his Bangle.js
Sneak into Mixed Clock app to figure out how this work and look at this forum conversion

Done!

Thanks! Please could you add/update the ChangeLog so users know what has changed? https://github.com/espruino/BangleApps/blob/master/apps/aclock/ChangeLog

ah, yes, i did but didn't bring it to this branch.

Thanks!


Update grafana infrastructure

Loki and or grafana (or both) need an update. The query editor is borderline unusable. We haven't updated it since we originally installed it 2 years ago.

related to this: https://github.com/grafana/grafana/issues/54535

update done via apt testing now

Looks good


stake BYX + initial distribution

Basic Staking of BYX (no rewards)
Basic functions in all contracts (receive, fallback, withdraw)
Initial token distribution system
I have not tested this code yet. I will do a test suite this afternoon and bring corrections if needed.

Fixed
I also added a getter for the user staked amount (that will be needed by frontend
I switched the functions between an external that call the internal for gas optimisation (like openzeppellin always do)


Suggestion: Only Active if on Arceuus Spellbook

Love the plugin, helpful for dummies like myself to remember. Would be awesome if it was only active in making the infobox happen based on the spellbook you're on. I'm pretty much only on Arceuus book when doing activities with thralls, so would be nice to be able to leave the plugin perma on, instead of toggling the plugin off whenever not doing an activity with thralls.

I've updated the plugin with a better system so after summoning a thrall if you don't summon another for a configurable amount of time, it will remove the prompt. Thanks for the suggestion!

Liking the plugin but I do think it would still be better if it only activated when you're on the Arceuus spellbook and have the book/runes with you.

I ended up deciding to include this feature and it will be available once the plugin is updated.


docs: modify to detailed links + add details to running-locally

Fixes #TODO
Motivation
When I first tried to install Argo Workflows using Dev Containers in my local environment, I was confused because the link to the The Visual Studio Code Remote - Containers and Dev-container CLI in the documentation didn't go to the link to extension or Dev-Container CLI itself, even though the context indicates that this is a link for that.
Also, as someone new to Dev Containers, I didn't know that I needed to use the make clean & make start to boilerplate, so I had to infer from the #Developing Locally section in the middle of the documentation how to get Argo Workflows running in my local environment.
The changes I've made to the documentation are located earlier in the documentation and would make getting up and running with Argo Workflows faster and easier for someone like me who is new to Argo Workflows or Dev Containers.
Modifications

Modified the link of Dev Container extension in Visual Studio Code
Modified the link of Dev Container CLI
Added command for start the argo workflow inside Dev Container

Verification

Dev-container CLI in the documentation didn't go to the link to extension or Dev-Container CLI itself

Good change! I think I stumbled upon this myself and just forgot about it as I don't use the CLI

so I had to infer from the #Developing Locally section in the middle of the documentation how to get Argo Workflows running in my local environment.

Hmm so it might make sense to just link downward to "Developing Locally" using its anchor #developing-locally.
(I also see that the /etc/hosts part is no longer needed for the dev container since #11104 automated that)

I was confused because all the spelling errors in the checks from the original running locally.md...

Not sure why these just started showing up now 🤔 Seems to be erroring on code backticks.
Wonder if there was a change in mdspell recently...


Fix minor typos in adoc

What's this PR do/fix?
Fixes several minor typos in the docs.
Are there unit tests? If not how should this be manually tested?
No code changes, so no tests.
Any background context you want to provide?
None.
What are the relevant issues?
None.

I believe this issue is still relevant 🤷

I'm guessing https://github.com/springfox/springfox isn't maintained anymore.


ENH: sparse: special-case DIA * scalar

Reference issue
Fixes gh-20434.
What does this implement/fix?
This adds an override for sparse * scalar multiplication, to avoid a potentially costly conversion to CSR format.
Performance
In [1]: import scipy.sparse as ss
In [2]: import numpy as np
In [3]: a = ss.diags_array(np.random.random((5, 10000)), offsets=[-4, -2, 0, 1, 6], shape=(10000, 10000))
In [4]: %timeit a * 5
38.4 µs ± 246 ns per loop (mean ± std. dev. of 7 runs, 10,000 loops each)
In [5]: %timeit a.tocsr() * 5
643 µs ± 3.63 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)

And a perfplot:

generated via:
import perfplot
perfplot.show(
   setup=lambda n: ss.diags_array(np.random.random((5, n)), offsets=[-4, -2, 0, 1, 6], shape=(n, n)),
   kernels=[lambda x: x * 5, lambda x: x.tocsr() * 5],
   labels=['new', 'old'],
   n_range=[1e2, 1e3, 1e4, 1e5, 1e6],
   xlabel='NxN shape',
   equality_check=None,
)

@dschult When trying to do some performance testing here, I discovered that _mul_scalar() is no longer called from sparse arrays via __mul__, because we now call multiply() which doesn't include any special-casing. This performance regression appears to have been introduced by me, in gh-18440.

Can we add a test here to check it stays as dia_array?

Added a simple test.

This makes A * 3 different from A.multiply(3). The first special cases to _mul_scalar before conversion to CSR format. The latter converts to CSR format and then calls _mul_scalar. If we want them to be the same we could put the check for a scalar inside _spbase.multiply before the conversion to CSR format.

Good point, done.


waffle.io Badge

Merge this to receive a badge indicating the number of issues in the ready column on your waffle.io board at https://waffle.io/mirskytech/ui-timepicker
This was requested by a real person (user ajmirsky) on waffle.io, we're not trying to spam you.

Manually added directly to updated readme and github.io pages.


Search tree error

Trying to use the "search tree..." results in php error:
Warning: preg_match_all(): Compilation failed: invalid range in character class at offset 4 in gitlist/src/Git/Repository.php on line 342

Can you provide further information about the error like the generated regular expression?

I'm just typing in a simple text input, e.g. "searchtext" in the "search tree..." form input.
How do I get repository.php to output the generated regular expression? I've looked at the source and I'm not familiar enough with regular expression patterns to understand what line 342 of repository.php is doing:
preg_match_all('/([\w-._]+):([^:]+):([0-9]+):(.+)/', $result, $matches, PREG_SET_ORDER);
I can complete a text search using grep at the command prompt and yield a result.
grep -rnw '/path/' -e 'searchtext'

If you don't want to wait till my pull-request is merged you can change the "-" in the first part of the expression to "-". For more details see my pull request.


auro-flightline: z-index overlaps header

Describe the bug

To Reproduce
Steps to reproduce the behavior:
The new schedules view (alaskaair.com/status/628/2021-05-14) and scroll up on a mobile viewport
Expected behavior
auro-flight-segment doesn't overlap the headerfooter
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Here is what I know. The z-index for the dot is 2. The z-index for the header is 499.
Is there a better production URL I can see to repro this?

Minimal repro: https://codepen.io/geoff-rich/pen/LYWRLVY

@gusnaughton the URL you have to demo the issue no longer has a stopover to illustrate the actual bug you are reporting.

@gusnaughton Do you have an updated example where we can repro this issue?

Added BLOCKED label. Unable to repro. @gusnaughton is you have an example we can use to repro, we can see if there is a solution or I will have to close the issue.

@blackfalcon we ran into similar z-index issues in disruptions. We had to work around it by setting z-index on the flightline and our overlay and it was a bit of a pain.
As an example, the "canceled" flightline was appearing over our flight details overlay (note the dashed red line under the heading):

You can repro similar behavior in the flightline demo repo by adding a fixed heading to the top of the demo page:

    I'm a heading

Here's a gif of the result:

It is not difficult to get into this situation and is a significant pain point for those using the component. By using z-index in this way, we break the isolation that a component model promises.
I think this issue should be reopened. I've been messing around in the repo and I think we can resolve this by removing some of the z-indexes and using isolation: isolate.

:tada: This issue has been resolved in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Make provenance executable

Is this a bug fix or adding new feature?
What is this PR about? / Why do we need it?
What testing is done?

/approve
/lgtm


Get older version 0.9.42

DO NOT MERGE INTO MASTER!!
According to https://github.com/conda-forge/gap-feedstock/issues/1#issuecomment-279237244, an 0.9.42 branch needs to be created and then we can merge this PR into that branch.
Resolves https://github.com/conda-forge/slacker-feedstock/issues/8

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The build section contained an unexpected subsection name. nopython is not a valid subsection name.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@synapticarbors as a core member you should have all that is needed to create the branch, if you are having trouble with that please let me know and I can do that for you.

Just bumped your rights. @synapticarbors can you try again?

@ocefpaf - Works now.

@ocefpaf - Works now.

You should also have access for the Dbox paper and be on the meeting google calendar list. Let me know if those are OK on your side.
(We have a meeting tomorrow BTW.)

Can you point me to where I can find those items?

Can you point me to where I can find those items?

I guess the former you can try to log on Dropbox paper and see if you have conda-forge docs folder there. Same thing with the Google calendar.
If you don't have those send me your proffered e-mail and I'll add you.


Stakeholders unable to reorder cards vertically on Kanban boards

We have recently begun adding stakeholders to collaborate via the Kanban boards. But for some reason they can't change the order of the cards vertically. They are able to change the cards horizontally, to move it to different columns.
After searching I saw that the option to drag and drop on the boards for stakeholders was added last year. But I see no one mentioning this issue. Is there an option or setting I'm missing? Or is this done deliberately?

@ntvbsrene
Thanks for your feedback; we appreciate it. To make sure we have all the information needed to address your issue, please let us know which article you’re referencing.
@KathrynEE @mijacobs for awareness -

https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/boards/sprint-173-update
This one explains that dragging between columns had been added last year.
Our stakeholders would very much like the ability to also reorder the cards vertically within the same column.

@ntvbsrene - Thank you for your inquiry. The ability to reorder items within columns is directly connected to placing work items by priority order. This isn't a supported feature for those with Stakeholder access. If you want to request a feature change, please log it on our Developer Community page.


VANotify monitors and is alerted of complaints and bounces

Value Statement
As a VANotify team member
I want to to be able to view and alerted of email complaints and bounces
So that our reputation can be safeguarded
Acceptance Criteria
GIVEN
WHEN
THEN
Checklist

[ ] Checklist item here

Assumptions

Additional Info/Resources

Out of Scope

Open Questions

@miabecker


WCMMODE=disabled no longer works

It redirects to chrome-extension://hgjhcngmldfpgpakbnffnbnmcmohfmfc/NaN?wcmmode=disabledundefined

Verified the issue. All URL manipulation features were affected such as toggling WCM mode, content finder, classic/touch, debug clientlibs and debug layout. The issue surfaced just as Chrome released their latest version, 43. The issue has been resolved and pushed out to the Google web store.
Chrome will automatically update the plugin or to force it, navigate to chrome://extensions, check "Developer mode" and click "Update extensions now".

Thank you for the notice Peter.

You're welcome :-)


Seaport 1.3 ABI-gen not implementing traits

Version
└── ethers v1.0.2
    ├── ethers-addressbook v1.0.2
    │   ├── ethers-core v1.0.2
    ├── ethers-contract v1.0.2
    │   ├── ethers-contract-abigen v1.0.2
    │   │   ├── ethers-core v1.0.2 (*)
    │   ├── ethers-contract-derive v1.0.2 (proc-macro)
    │   │   ├── ethers-contract-abigen v1.0.2
    │   │   │   ├── ethers-core v1.0.2
    │   │   ├── ethers-core v1.0.2 (*)
    │   ├── ethers-core v1.0.2 (*)
    │   ├── ethers-providers v1.0.2
    │   │   ├── ethers-core v1.0.2 (*)
    ├── ethers-core v1.0.2 (*)
    ├── ethers-etherscan v1.0.2
    │   ├── ethers-core v1.0.2 (*)
    ├── ethers-middleware v1.0.2
    │   ├── ethers-contract v1.0.2 (*)
    │   ├── ethers-core v1.0.2 (*)
    │   ├── ethers-etherscan v1.0.2 (*)
    │   ├── ethers-providers v1.0.2 (*)
    │   ├── ethers-signers v1.0.2
    │   │   ├── ethers-core v1.0.2 (*)
    ├── ethers-providers v1.0.2 (*)
    └── ethers-signers v1.0.2 (*)

Platform
Linux DESKTOP-GR484G2 <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Wed Nov 23 01:01:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Description
https://github.com/the-emerald/ethers-seaport-demo
The ABI used is Seaport 1.3, taken from here. It seems like some basic trait impls aren't happening for the complex structs that Seaport uses. e.g.
error[E0277]: the trait bound `(ethers::types::H160, ethers::types::U256, ethers::types::U256, ethers::types::H160, ethers::types::H160, ethers::types::H160, ethers::types::U256, ethers::types::U256, u8, ethers::types::U256, ethers::types::U256, [u8; 32], ethers::types::U256, [u8; 32], [u8; 32], ethers::types::U256, std::vec::Vec<(ethers::types::U256, ethers::types::H160)>, ethers::types::Bytes): std::default::Default` is not satisfied
 --> src/lib.rs:3:1
  |
3 | abigen!(Seaport, "src/abi.json");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `std::default::Default` is not implemented for `(ethers::types::H160, ethers::types::U256, ethers::types::U256, ethers::types::H160, ethers::types::H160, ethers::types::H160, ethers::types::U256, ethers::types::U256, u8, ethers::types::U256, ethers::types::U256, [u8; 32], ethers::types::U256, [u8; 32], [u8; 32], ethers::types::U256, std::vec::Vec<(ethers::types::U256, ethers::types::H160)>, ethers::types::Bytes)`
  |
  = help: the following other types implement trait `std::default::Default`:
            ()
            (A, Z, Y, X, W, V, U, T)
            (B, A, Z, Y, X, W, V, U, T)
            (C, B, A, Z, Y, X, W, V, U, T)
            (D, C, B, A, Z, Y, X, W, V, U, T)
            (E, D, C, B, A, Z, Y, X, W, V, U, T)
            (T,)
            (U, T)
          and 5 others
  = note: this error originates in the derive macro `Default` (in Nightly builds, run with -Z macro-backtrace for more info)

libstd Reference:

Due to a temporary restriction in Rust’s type system, the following traits are only implemented on tuples of arity 12 or less. In the future, this may change:

PartialEq
Eq
PartialOrd
Ord
Debug
Default
Hash

We'll need to rewrite can_derive_default to append all these derives only if the tuple fields length <=12

Can't wait for some const generic love for this..


Respect --mlir-print-op-generic in attribute prettyprinters

Attributes like ConvDimensionNumbers always prettyprint at the moment, regardless of --mlir-print-op-generic.

Two possible options:

Don't have custom attribute printers, and handle this at the op pretty-print level. I.e. for ConvDimensionNumbers, don't specify custom mnemonic, or custom assembly for the attr, and instead on ops that use it, add custom assembly with custom<ConvolutionDimensions>
Have an attr verifier. Attrs that use custom assembly that fail verification can get printed with a raw_ prefix.


add WHO and CDC resource links

Let's do our part to keep the official resource links front-and-center. They can be swapped out easily the next time this page is revived for something else (which, let's be honest, we hope we never have to).

@macmanx2 Thanks for the pull request! The index.html file is generated but I've put your links into the .org file now and pushed the changes. Thanks again!


Fluid simulation - First fully functional version

This is the first fully functional version of the fluid simulator I started writing several months ago.
Many thanks to @chaoticbob and @Keenuts for their guidance during this implementation. I've learned quite a bit!
This PR is quite big, so I split it in 7 commits.  Basically:

Initial version of the simulation loop: This completed the code conversion from the original WebGL implementation. This is followed by 4 commits that fixed various bugs.
Introduce repeat samplers: This added a clamp and a repeat sampler. The repeat sampler is using when computing the final image to present. Clamp sampler is used by all the compute passes.
Simplify dispatch record generation - Fix DirectX12 failure and Add debugging code to draw all computed textures are various fixes and debug code that I added when trying to figure out the bug that was producing odd output.
Fix texture formats to use floating point instead of ints fixes the odd output. @Keenuts observed that several of the compute textures in the code were using the display color format (uint8), instead of floating point values.  With that fix, the simulation produced a single splash that looked more accurate.
Add command line flags and simplify some logic: This moves the configuration data into a structure that can be filled-in via command-line arguments. I hope to hook this to the knobs framework once @angela28chen makes it available.
Add documentation on the simulation parameters: Documents all the parameters that can be altered to produce different simulation output.

The default execution of the simulator should produce an output similar to this.

LGTM for a first iteration, not let's make is 4k@60fps 😊

Ha!  Yeah, it's actually pretty easy to peg the GPU by changing some of the resolution parameters.


Add Levitate as an example for read/write integrations option

Signed-off-by: प्रथमेश Sonpatki<EMAIL_ADDRESS>

The build is now passing. Can someone take a look?

@RichiH Can you review this?
Thanks!


Consider creating a read-only mailing list for announcements

Description
Currently announcements are distributed via issues in the announcements repository. This has the downside that anyone can open issues there, not just the .NET team. On a regular basis someone will create an unrelated issue (e.g. https://github.com/dotnet/announcements/issues/238), which then gets sent to everyone subscribed to the repository, for no benefit.
Consider distributing announcements via a better, read-only, channel instead. Options include a mailing list or a RSS feed.
For backwards compatibility, a bot can sync announcements from there to the announcements repository.

Configuration

Regression?

Other information

@terrajobst @richlander @jamshedd

@danmoseley, @terrajobst and I had an email thread ~2022/4/24 about how to improve this--there are another few alternatives that would maybe let .NET still use dotnet/announcements.
One is adding a .github/ISSUE_TEMPLATE/config.yml that doesn't actually include a way to file an issue, just redirects to other repos. Users could still file issues, but they would need to find the issue-filing URL manually because GitHub wouldn't show a button they could click to take them there. So far, the repo hasn't had a problem with malicious issues/comments, just unknowing issues/comments, so I think this would end up ok.
Another is using the "temporary interaction limits" to make sure nobody files issues or comments. We actually enabled it at the time, but as the name says, they're only temporary, and they've expired. Making it someone team's job to refresh the limits (or find a way to configure it using a bot?) could make this work out.
Of course, GitHub isn't designed to be used for this purpose, so going for something else entirely makes a lot of sense. 😄

What about the Wiki feature of the Announcements repository?  That can be locked down to just contributors having edit access and we can get a little more search indexing capabilities from our friends at Bing and Google.

It appears that GitHub repositories are not designed for making announcements, yet the potential solutions seem restricted to using one for that purpose. Is that the case? If so, why is that?

Speaking for myself, I don't mean to restrict the potential solutions. The original post already suggests mailing lists and RSS feeds and I don't personally see a problem with either one. I'm just mentioning a few ideas from a while back that address this line of the original post (the motivation for switching):

This has the downside that anyone can open issues there, not just the .NET team.

@terrajobst @richlander @jamshedd any action needed or planned for this issue?

Playing the data controller or data processor role with PII such as email addresses involves more policy and process overhead than one might imagine. I would not favor that approach, instead I'd explorer cheaper ways to lock down the creation of issues in announcements if there's a way to do that. The 2 workarounds @dagood suggested above might work.

We discussed the use of email lists at the beginning of the .NET Core project. After a few back and forths we decided against that. I don't think we'll ever want to start using them again. Markdown on GitHub gives us a lot more flexibility than email. You can easily link to it, you can edit it to improve clarity, and there is an obvious place to point people for a public conversation. I'm very much opposed to going that path.
The announcement pattern has worked reasonably well for us, modulo the issue that sometimes people open new issues. I say sometimes, because we basically have continuous restriction that disallows non-contributors from opening issues (it's a GitHub feature, but we need to renew it every 6 months). We have given the feedback to GitHub. There are several ways this could be achieved here (allowing permanently disabling issues or pure announcement issues + notifications). If something better is available, I'm all for it. But it's for sure not a mailing list.


which function is the first start when

hello,
The lio sam system is made up with 4 node ,the 4 node is a loop ,every node start must subscribe another publisher of another node ,so how do this system start?which function  start's first?


User Information Overlay Issue on Small/Vertical Screens

Steps to Reproduce

Open https://www.bmsamay.com/community on a small screen or resize the browser window to a vertical layout.
Hover over the username on any card
Observe that the black div containing the user information is being overlapped by the card elements.

ill do this


Add Support for iPad on iOS 13

Nice. Tests pass locally but not in CI. Something's up with puppeteer I'm guessing

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Client-side validation options

https://github.com/joecorcoran/judge
https://github.com/amatsuda/html5_validators
https://github.com/posabsolute/jQuery-Validation-Engine
Creating a wizard to save intermediate state
https://github.com/schneems/wicked
My specific suggestion is to create validations but have then all run on: :certify, not on :create or :update. Then, you create controller logic for create where if the object is valid, it runs certify, and otherwise it just saves (which keeps it in an intermediate state). This isn't fully thought through, though, because you would not want an :update to be able to move you to an invalid state.

I think we're going a different direction than described here.


Is this project still being maintained?

Doesn't seem to be compatible with the latest Arduino IDE (and toolchain).
I'm on Mac 10.7.
So far the alternative has been to use Arduino's own very clunky and difficult to use CLI. Please someone update Ino !!

Yes, it seems to be outdated and not compatible with the latest Arduino IDE and also Mac OS X El Captain...pls maintain it!

@amperka Would you mind finding a new maintainer? There's 35 open pull requests ATM and no commits for 2 years.

FYI, the ano project is a ino fork for just that purpose.

You can also use Platform.io (https://github.com/platformio/platformio) which is really awesome.

@nailxx @12qu @chrisspen and any interested parties,
Ino is such a cool toolkit. Great work. The community is begging to use and contribute to it.
The inotools name has a lot of recognition. I'm worried that we are fragmenting the community by renaming the project (ano). This results wasting valuable contributions.
This project belongs under a dedicated organization where the community can continue to move it forward.

Appoint some project maintainers.
Create a dedicated inotool organization.
Migrate this project to the organization. (Ideally using Github's transfer function to keep issues and setup the proper redirects)

There are many issues that have been fixed multiple times. Tons of work out on branches that just needs tested and merged.
Lets open this project up to some active stewards so that the community can move it forward!

That would require the project creator's permission, and he's AWOL, so
that's not going to happen. I'd recommend helping out with Ano. That Dev
responds to issue submissions and is actively looking for help to port the
code to the most recent Arduino release.
On Feb 24, 2016 2:06 PM, "Casey Watson"<EMAIL_ADDRESS>wrote:

@nailxx https://github.com/nailxx @12qu https://github.com/12qu
@chrisspen https://github.com/chrisspen and any interested parties,
Ino is such a cool toolkit. Great work. The community is begging to use
and contribute to it.
The inotools name has a lot of recognition. I'm worried that we are
fragmenting the community by renaming the project (ano). This results
wasting valuable contributions.
This project belongs under a dedicated organization where the community
can continue to move it forward.

Appoint some project maintainers.
Create a dedicated inotool organization.
Migrate this project to the organization. (Ideally using Github's
transfer function to keep issues and setup the proper redirects)

There are many issues that have been fixed multiple times. Tons of work
out on branches that just needs tested and merged.
Lets open this project up to some active stewards so that the community
can move it forward!
—
Reply to this email directly or view it on GitHub
https://github.com/amperka/ino/issues/255#issuecomment-188408301.

id second looking at plaformio.org its awesome


Replace deprecated 'compile' gradle configuration with 'implementation'

According to<EMAIL_ADDRESS>default gradle version is now 4.4.

I think it is better to upgrade the gradle in travis to 4.4.


Move Routing to Individual Blueprints

It is important that we compartmentalize the routing code as more features are added to the code base. I have added blueprints for all of the different api interfaces and went through a few general tests to ensure all the components are working as expected.

This looks good to me. I'm passing this off to @jburket will handle testing and merging the pull request.

I have tested the changes on my instance. Everything appears in order.

We could really use some regression tests.

I'll be working on regression tests soon. The current set of tests are hopelessly broken.

Where are the current tests?

Found them. Yeah I'll create an issue.


⚠ Processors has degraded performance

In 7b10d6f, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 59 ms

Resolved: Processors performance has improved in 9af32dc.


Memgpt

How to use with memgpt as one of agents ?

+1 for MemGpt integration, or something like "teachable agent"
I started to build my online project with CrewAi, but I have to switch to autogen because of that

@MindsightsAI see this active langchain issue

Independently of LangChain, I would love to add MemGPT! Def something that has been on my radar!Adding as feature accepted

That would be awesome!

Any news on this part?

What is the current progress？


This is an awesome workflow!

Just wanted to say this is a very handy and fantastic workflow. Thanks!

Hey Saeed, thanks for the feedback. I'm glad it's been useful for others as it has been for me :)


⚠ Samsung has degraded performance

In ace49a5, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 1991 ms

Resolved: Samsung performance has improved in ea577e6.


[CARBONDATA-3374] Optimize documentation and fix some spell errors.

Optimize documentation and fix some spell errors.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?
NA
[x] Any backward compatibility impacted?
No
[x] Document update required?
Yes
[x] Testing done
add test case
[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

No

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3117/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11382/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3318/

LGTM

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3133/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11398/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3332/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3141/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11406/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3340/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3144/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3343/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11409/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3177/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11442/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3374/

LGTM

LGTM


find-moj-data - all form controls should have labels

For accessibility, all form controls should have an associated <label>
Search box - it's OK to do something like this to create a visually hidden label:
<label for="searchForm-search" class="govuk-label govuk-visually-hidden-focusable">Search MOJ Data</label>

The checkbox labels just need a for attribute added:

https://github.com/ministryofjustice/find-moj-data/pull/73


Assertion error on ObjectSubclass::get_instance() with zero sized type

If a zero-sized type implements ObjectSubclass, calling get_instance() errors:
thread 'main' panicked at 'assertion failed: `(left != right)`
  left: `0`,
 right: `0`', /home/ian/src/glib-rs/src/subclass/types.rs:300:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This assert is failing:
https://github.com/gtk-rs/glib/blob/0cc0a46c6da1cd7c853cef8f6851d80d4a0de202/src/subclass/types.rs#L300
Removing the assertion fixes it. I don't know if there's a good reason to have the assertion. If it's to verify the offset has been set, perhaps it should use a sentinel value other than 0.
I came across this just testing the API, and the struct I actually was going to use wasn't zero-sized. But there are probably some sane uses for a GObject with no data members (except those in a parent type).

Yes that assertion shouldn't be there at all :) Previously (before https://github.com/gtk-rs/glib/commit/bbe787c1aaf6f450b33bd4102acbfd7cbd525bb3) it was not possible to have a ZST for it. It would always be an Option<_> instead, but when doing that change I apparently forgot this assertion.
Do you want to submit a PR for this?

And if so, please also extend the test here with a call to get_instance():
https://github.com/gtk-rs/glib/blob/0cc0a46c6da1cd7c853cef8f6851d80d4a0de202/src/subclass/object.rs#L332

This is also fixed on crates.io in 0.10.3 now. Thanks!


Working direct sdk interaction

This is a separate branch. Still WIP. But need this to be merged so we can experiment few things. Will merge to get the SDK going.


Update index library names

Description
We haven't aligned on naming proposal A yet and the library names aren't in conflict with proposal A, but they should be updated to be more consistent.

 For example Carbon React also includes React hooks (functions), Carbon Angular also includes some coded patterns, etc.
It prevents confusion between vanilla and React libraries.
The naming is aligned with how we now name code packages in the Carbon scope, like @carbon/react.

There's a related design issue to specify library descriptions: https://github.com/carbon-design-system/carbon-platform/issues/559
Steps to reproduce
How do we reproduce the error? Please be as specific as you can.

View the libraries list https://next.carbondesignsystem.com/assets/libraries

@kingtraceyj @aubrey-oneal can you review the table above and justification?

@carbon-design-system/carbon-platform-designers can you review the table and justification above?

Hey team! Please add your planning poker estimate with ZenHub @alisonjoseph @andreancardona @francinelucca @jdharvey-ibm

@aubrey-oneal

Before
After

~Carbon React~
~Carbon React~

Carbon Components
Carbon Vanilla - Carbon no longer supports Vanilla @aubrey-oneal  thoughts on this?

Carbon Components Angular
Carbon Angular PR: https://github.com/IBM/carbon-components-angular/pull/2202

Carbon Components Svelte
Carbon Svelte

Carbon Components Vue
Carbon Vue

Carbon Web Components
Carbon Web Components

@andreancardona Carbon Vanilla isn't deprecated or sunset; it's just community maintained. It still needs indexed (for now at least.)

@andreancardona Carbon Vanilla isn't deprecated or sunset; it's just community maintained. It still needs indexed (for now at least.)

Here is the original PR - I cannot seem to find the carbon.yml to save my life 👀 do you see it?
https://github.com/carbon-design-system/carbon/pull/11265/files

@andreancardona https://github.com/carbon-design-system/carbon/blob/v10/packages/components/carbon.yml you have to do it in v10 branch


Flipview to have styleable attributes like other controls

Hi,
At the moment the Flipview controls banner and arrow colours are connected to the app theme and are only changed by setting either light or dark for the entire app itself. I propose it to be style-able via tags similar to other controls e.g.
    <mah:MetroWindow.Resources>
        <ResourceDictionary>
            <Style x:Key="{x:Type Flip}"
       TargetType="{x:Type ToolTip}">
                <Setter Property="Background" Value="#d9e1e9" />
                <Setter Property="Foreground" Value="#000000" />
            </Style>
        </ResourceDictionary>
    </mah:MetroWindow.Resources>

This would allow the control to use accent colours etc, maybe even variable sizes and make it a little more flexible overall.

I would like to jump in this Hacktoberfest
My idea is:

[ ] Add a Style for the Buttons
[ ] Add a DataTemplate for the Buttons Contents
[ ] Add a DataTemplate for the Banner

Anything missing?


Do not use period for autostart timer

Instead of using 24h period, just reschedule the next autostart timer
Period seems inaccurate, can be skewed from requested period
We use absolute scheduled time to get around this

Fixed.


Python Version

Hello i am looking to use the penrose pattern as a moving noise generator.
Your code seems to be the only one using vertex information to tile indefinatly.
When i try to run it i get the error.
And i was wondering if my python version has anything to do with it.
    p4 =
         ^
SyntaxError: invalid syntax```

Hey, sorry about that.
Looks like a syntax error on my part (that didn't need to be there).
Just fixed it.
Sorry that I didn't respond sooner, but yeah just deleting that line is fine.

Dont apologise for making a mistake to a complete stranger. Ill have a look when I have time i`m currently working for my exams.

Dont apologise for making a mistake to a complete stranger. Ill have a look when I have time i`m currently working for my exams.