React does not recognize the showTodayButton prop on a DOM element

Environment

Tech
Version

@material-ui/pickers
3.2.6

material-ui
4..41

React
16.8.6

Browser
Google and Firefox

Peer library
moment and date-fns

Steps to reproduce

Use the KeyboardDatePicker with the variant property inline
Try to use the property showTodayButton

Expected behavior
The calendar displays the today button
Actual behavior
An error is thrown

Live example
https://codesandbox.io/s/material-ui-showtodaybutton-f67by

Fixed a long time ago :)


Add option to hide copied username, password, and one time password from clipboard history.

Version 1.2.0


Format output properly

when we have more columns to be retrieved , the output data is not formatted properly . Finding it difficult to view the data

Please try the latest version, the output shows as an HTML table.


Problems with WCR and tests with only one covariates

... as in classical AB test setups without covariates. The same problem exists for fwildclusterboot.

Is this soemthing that should have an error message for now?

Yes, until I fix it :)


doc: fix tmpdir documentation for windows

What does this PR change? What problem does it solve?
The environment variable to change the temp directory is called TMP or TEMP on Windows.

Was the change previously discussed in an issue or on the forum?
Fix https://github.com/restic/restic/issues/4813

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[x] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

LGTM.


Update index.rst

The name='btnG' does not exist on "http://www.google.com" and a run of the sample code results in an IndexError exception.  I propose that the button be accessed by value='Google Search' as this will make the sample code work and will be more resilient to change than continuing to use the often-changing Google element names.

@schurma Your change wouldn't really make the code more resilient, not unless you know Google will never change the text in their submit button. It also introduces a breaking changes for anyone who uses google in a non-English language.
Finding elements by their text content should only be done when the text content is something that needs to be retrieved and evaluated. It's poor practice to use it for finding a button element and not the sort of thing I'd want displayed front and center in the documentation.
The code examples in the documentation should be more abstract. There's no way to control external websites and a google search example should be part of a longer tutorial, not part of the standard docs.
eg:
# Go to a website with a search input and submit button
# Then get the results of the search
with Browser('firefox') as b:
    b.visit('http://my.web.site/')
    b.find_by_css('#searchInput').fill('My Search Query')
    b.find_by_css('#searchSubmit').click()

    results = b.find_by_css('.results')
    if results[0].value == 'My Expected Result':
        print('Success!')
    else:
        print('Failure!')

That’s incorrect.  This change will make the code more resilient.  This will fix the broken script and prevent the breakage from recurring.
It isn’t true that this causes breakage for non-English users of Google.  http://www.google.com defaults to English and the zope.testbrowser,  geckodriver, and chromedriver engines used by Splinter all default to English.  If someone knows how to change the language settings for those drivers then it’s incredibly unlikely that they’d be learning web automation for the first time using this sample script and then be perplexed why the “Google Search” text doesn’t match “Google [ & something clearly different]” text.  That isn’t an instance of breaking changes.  A breaking change is what happened to the Splinter example code after an ephemeral selector was used for a popular website.
It's correct that name selectors are often recommended over text selectors for a number of reasons, except that none of those reasons makes sense for the example.  Google and other large companies know those recommendations and they craft those fields in order to break tools that crawl their websites.  Popular websites have switched best practices with antipatterns for web automation.
The example doesn’t need to be abstract.  It needs to work.  It's embarrassing to recommend Splinter as the best web automation tool while the first example is broken.  Most people won’t read any more docs if the first example is broken, especially if the broken example is used to explain the tool.  If it’s important to maintain the remaining docs, then maybe the docs following the resilient example can begin it by asking the reader to get the name field of the button by viewing source.  Then say, “For example, the name may equal btnk…”, then proceed from there.  A sentence about the name selector being faster and better for dynamic text could be used without building a longer tutorial.
This change is the most resilient solution for the example.  The language of the speaker doesn’t break the script and text value is the best selector.  The text for that button hasn’t changed since 1998 and it’s reasonable to assume it won’t change in the future.

This will be fixed in a different way with acceptance of PR #1255.

It's been 2.5 years since I submitted that and I don't care.  I tried to
help but the response I got was so rude that I abandoned any idea of
helping.  Soon after that my company and I abandoned even using the
project.
It's more important to get rid of rude jerks than it is to get rid of
software bugs.  Especially when those jerks scare away new volunteers for
your buggy crappy wreck of a project.
On Fri, Mar 1, 2024 at 6:04 AM nameloCmaS @.***> wrote:

This will be fixed in a different way with acceptance of PR #1255
https://github.com/cobrateam/splinter/pull/1255.
—
Reply to this email directly, view it on GitHub
https://github.com/cobrateam/splinter/pull/942#issuecomment-1973161604,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPBNKRMW7IFFQK6IBAO7VTYWB4EZAVCNFSM5HWPQLWKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJXGMYTMMJWGA2A
.
You are receiving this because you were mentioned.Message ID:
@.***>


Unable to remove quotes from my own nadeko bot?

iv been looking into the files and the commands to remove quotes but i cant seem to figure it out both ..qdel, ..quotedelete dont seem to be working on my server so i stopped looking and turned to you guys please help!
Thanks!

Your ownerID in credentials.json is probably wrong.

that cant possibly be the problem since i can use all the other server owner only commands just fine

Did you update to the latest version? i.e. -h ..qdel should respond with the description

also Kwoth im hosting from my own computer and all my other owner only commands work fine and i did my ownerID right im pretty sure that the quote deleting is the only thing that isnt working

Do what applemac told you. You are probably just not on the latest version.


Password protection

Hi there,
Thanks for the hard work !
I only miss a password protection feature. Something as simple as one shared password for everyone.
Have you thought of this for your roadmap ?
Thanks

I have forked and tried my way to implement a simple password protection, but it is untested (as I cannot find how to start properly the app without having  an error
Traceback (most recent call last):   File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main     "__main__", mod_spec)   File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code     exec(code, run_globals)   File "browsepy/__main__.py", line 13, in <module>     from . import app, compat ImportError: attempted relative import with no known parent package
So I will issue a pull request so you can do the last mile ?

I use a simple HTTP authentication (configured on a proxy server like NGINX) over HTTPS (to make it safe).
A note about extra functionality: browsepy's feature scope is closed, but any extra functionality could be added as plugin (as long as it complies a few rules http://ergoithz.github.io/browsepy/builtin_plugins.html#contributing-builtin-plugins). Indeed a proper authentication plugin is on our roadmap.


WasmExtension queries without height

With the WasmExtension for QueryClient is not possible to make a query with a specific height as it can be done with ABCIquery.
And I think it's a very useful feature.
I myself very often query smart contracts but get outdated data without knowing.

agreed that feature would be awesome. posted a similar issue here https://github.com/osmosis-labs/telescope/issues/356

I myself very often query smart contracts but get outdated data without knowing.

I've also run into this problem, though for my use case I'd prefer just knowing the height a query was actually made at, instead of specifying what it should be made at. That way I can do something like "if query height is less than or equal to the last height I got, sleep and try again"
Will open a PR to address this and take it from there... I think it's across a couple different packages


增加对项目chenkui164/FastASR的致谢

PR types

PR changes

Describe

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

Please sign for CLA, THX

@chenkui164  如果可以，欢迎将源码合入paddlespeech中。


Page Weight for gist parser - need it be reduced?

When using just-dashboard, you've kindly provided the option to submit ready-written dashboard and data files. With this, however, the bundle.js (as used for one of your simple pie chart examples for instance) is 907kb ([http://bottoml.in/e/kantord/2973bdd4ad689642562018bb4091ffbd]). Doesn't that make the idea a bit restricted in the width of uses? I had hoped to use it in a sort of 'i-frame' manner (without the iframe of course) as I think you intend.
However, in a text and graphics-heavy page, adding 1Kb to that page weight for a graph makes it noticeably slow to load when I try it - will people for the graphs to load whilst browsing the page, especially on mobile? Obviously caching will alleviate massively but for me, it'll only be one page per website so that doesn't help.
A news article might well have a page weight of 1Mb. If it were to include an auto-generated graphic (or set of graphics), generated by just-dashboard (as in http://bottoml.in/e/kantord/2973bdd4ad689642562018bb4091ffbd),  there would be a further delay, after the 'main' page has loaded.
Maybe if the just-dashboard bundle.js could somehow be able to use async defer from the calling (1Mb) page, then the delay wouldn't be noticeable? Destroy some simplicity of use, so maybe as an option?

It is definitely a goal to reduce bundle sizes, as they are without doubt oversized. There are many opportunities, but it might not be easy to make it very small. The ideal would be to separate each chart component into separate chunks that only depend on the relevant parts of d3. I'm not sure whether it's possible to do that with billboardjs though.


FAO Global Record of Stocks and Fisheries: UUID

not urgent, just warming you up 😄 response to FAO below on global unique ID's for stocks
Dear Aureliano and the FAO team,
We heard from Ruth that there are some follow-up questions related to the below and to the GRSF GUID. Here are some answers, happy to have a chat if we have confused rather than clarified 😊
DOI

So far, we have only used DOI’s for the specific instance of a stock assessment (usually Year + Stock), so it is related in a 1:1 way with the Assessment Key in the Stock Assessment Database (SAG)
We wanted the DOI solution for a globally recognised URI that would accompany the DOI of the published stock advice and allow us to have a more transparent and citable system;
For the clients of advice, the linking backwards and forwards between the current and past stock instances was an important feature
We are using suffix namespaces (advice, data, pub) to denote the type of object resource the DOI is pointing to
We have not implemented this against the more ‘fixed part’ – the stock key which is related to the Stock Information Database (SID) and controlled in the ICES Vocab http://vocab.ices.dk/?ref=357

GRSF

We simply hadn’t thought to include the GRSF against the stock key, but we all agree that this is a good idea and it would be easy for us to implement against our vocab and then to expose it via SAG and SID
We had a look at the API and couldn’t get it to work for us i.e. http://updater.grsf.d4science.org/grsf-api/resources/stocks?from_year=2018 doesn’t return any results;
Could you provide us with a table of all the GRSF UUID’s for ICES stocks so we can set this up in our vocab – is there any issue with publishing this subset of ICES related GRSF UUID’s in vocab.ices.dk for you?

Best, and hope you are all seeing signs Spring and the home haircuts aren’t as disastrous as here in the ICES Secretariat.
Neil

Waiting for list with links between ICES stocks and GRSF

see SAG board issue for follow-up:
globalID's

@cmspinto is this something Laure can help with?

@cmspinto is this something Laure can help with?

@Milldaz

@cmspinto and @Milldaz can you answer us, please?

@cmspinto and @Milldaz - Provided the list we can accommodate references in the stock vocabulary (most likely as an attribute)

@cekv @cmspinto @Osanna123  can someone show me where this is implemented, i can't see it?

Hi @neil-ices-dk I think this is still open in #400 , at the moment I sent some feedback on FAO list of codes and I am waiting for them to get back with the final list of uniqur identifiers

thanks @odontaster - i suspected it might be, just lost track of issues on this one; will comment on #400


Formating fixes for create variable section

Closes #4059
These are text and formatting updates for the Create Variable Section for both Cloud and OSS

I found that the "Create Variable" section was missing some steps so I have added steps and used the same formatting as the "Import a Variable" section.
The original issue was for OSS but I found the same formatting errors in Cloud. These formatting updates are for both.


(maint) Add with_puppet_running_on to device test

Not all tests restart the server as part of state cleanup in their
teardown blocks. Recommended practice instead is to do master
interaction inside a with_puppet_running_on block, which resets state
before and after the block. This commit adds such a block to the puppet device test.

jenkins please test this servertests

I cleaned up some stuff that should be taken care of better by with_puppet_running_on.

CLA signed by all contributors.

Cleaned up the comments and reran with other corrupting test, still passing.

I think we also want to target 5.5.x as that's when the device test was added


Adding allows_null on select_multiple keeping standard

Adding option to remove default empty value

Hi @PinguimN ,
Thanks for the PR, you're totally right - let's keep consistency. Just merged it into the dev branch, it will be available to everyone next week.
Cheers!


AlphaPeel fails due to missing tinypeel.tinyhouse module

I installed AlphaPeel following the build_pipeline.sh file. After the wheel was generated I used pip install AlphaPeel-1.1.0-py3-none-any.whl to install AlphaPeel  from Dash (since my System runs on MINT 21). But when I try to call AlphaPeel the executable stops with the following error code :
AlphaPeel  Traceback (most recent call last):   File "/home/oem/anaconda3/bin/AlphaPeel", line 5, in <module>     from tinypeel.tinypeel import main   File "/home/oem/anaconda3/lib/python3.9/site-packages/tinypeel/tinypeel.py", line 8, in <module>     from .tinyhouse import Pedigree ModuleNotFoundError: No module named 'tinypeel.tinyhouse'
I checked the tinypeel python modules and found some unknown module .tinyhouse which I could not locate in the tinypeel package.
Then I checked your commits and I found that this commit might indeed break something, despite commit message indicates otherwise.
To me the problem looks like the following. You merged the functions from tinyhouse with tinypeel. But tinypeel and Pedigree still tries to call .tinyhouse. Since the tinyhouse reference inside the tinypeel package was deleted due to merging this reference is not available so that the python interpreter has to fail. I may have overlooked something here, please let me know if this problems occurs due to some mishandling on my side.
If not I would suggest to reverse the merging between tinyhouse and tinypeel if this does not lead to some other error I'm unaware at the moment. From my point of view the better coding practice is often to outsource as many functions as possible and import them when needed. There might be some possibility where one could define the functions inside tinypeel and Pedigree instead of loading them from .tinyhouse but I would not recommend this because this might lead to redundancies in the package which could be avoided using the outsourcing strategy.
I will post here again when I reversed your merge between tinyhouse and tinypeel and will report if this solves the error!

@Npaffen I had the same issue as you.
I have now done some updates to AlphaPeel and tinyhouse - see the latest commits - and got it to work out of the box.
Let me know if things don't work out for you and I will reopen the issue.


why doesn't keep item sequence of js files

in xxx.html
<!-- build:js scripts/site.js -->
<script src="foo.js"></script>
<script src="bar.js"></script>
<script src="baz.js"></script>
<!-- endbuild -->

When build end, content of site.js is like this:
// content of bar.js
// content of foo.js
// content of baz.js

I'm unable to reproduce this. What version of grunt-usemin are you on? Mind trying the dev branch? We're working on many updates in there. A reduced  testcase would definitely help too.

Closing due to inactivity. Happy to reopen when you provide a reduced testcase.


feat: group bulk edit

Close #1406
Enables bulk adding and removing users to/from groups.

Hi @jorwoods! Do you have an ETA on the merging of this PR? (and a new version release)


make it possible to specify the min and max value for the x- and y-axes

New properties added to control the minimum and maximum ticks for x- and y-axis:
YAxisTicksMin, YAxisTicksMax, XAxisTicksMin, XAxisTicksMax
Default value: Null
Released in version 1.23.15

New properties added to control the minimum and maximum ticks for x- and y-axis:
YAxisTicksMin, YAxisTicksMax, XAxisTicksMin, XAxisTicksMax
Default value: Null
Released in version 1.23.15


code checking too strict in step 44 of build a music player (js beta curriculum)

Describe the Issue
The code check for step 44 of the build a music player is too strict in my view. If you don't use the ?. notation, the step doesn't pass even though the else runs only if userData.currentSong is not null. I believe using dot notation to access the userData.currentSong.id in the else block is sufficient without the use of the ?.
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-basic-string-and-array-methods-by-building-a-music-player/step-44
Your code
  if (userData?.currentSong === null) {
    playSong(userData?.songs[0].id);
  } else {
    playSong(userData.currentSong.id);
  }

Expected behavior
I would expect regular dot notation to be accepted
Screenshots
No response
System
N/A
Additional context
No response

I think because it is a strict null check on a property, userData can be undefined or null which would run the else and if you then dot onto it without optional chaining it would be a type error.
const userData = undefined;

if (userData?.currentSong === null) {
  console.log("if");
} else {
  console.log("else"); // else
  console.log(userData?.currentSong); // undefined
  console.log(userData.currentSong); // TypeError: Cannot read property 'currentSong' of undefined
}

That makes sense. The only thing left to answer then is: shoudn't the undefined value be handled in the main if block rather than the else? (like should we play the first song if the value for the currentSong is undefined?)

You can always check the object or property instead of using optional chaining. But the point of optional chaining is that you can "embed" that check into the access.
Not really sure how currentSong would be undefined. The find inside the playSong would have to return undefined which given how it is passed the id I don't really see happening. But if it was, playing the first song would be one option for handling that particular "error state". Also, not strictly checking for null would handle both cases.
if (!userData?.currentSong)

If userData is undefined or null then we should likely throw and send the user an error message. Optional chaining, used just to avoid throwing errors when in fact it is an error, isn't necessarily that useful. It can also hide bugs if you are not careful, or at least make them less obvious.

Okay I think the null scenario basically happens when we haven’t started to play anything yet so it does need handling but an undefined scenario is probably unlikely in this app? (So really using the ?. is more about handling programmer error than anything else?)

null is the default value given to currentSong and is also what it is reset to.

So really using the ?. is more about handling programmer error than anything else?

It is a way to handle expected (known possible) null/undefined. It is more a convenience, because the problem doesn't go away just because the program doesn't throw. To some extent, you just "kick the error down the road". Sure, your app doesn't blow up, but you still need to handle that error state. For example, passing undefined to playSong doesn't really do you any good.

https://github.com/tc39/proposal-optional-chaining

In a deeply nested chain like  a?.b?.c, why should I write  ?.  at each level? Should I not be able to write the operator only once for the whole chain?
By design, we want the developer to be able to mark each place that they expect to be null/undefined, and only those. Indeed, we believe that an unexpected null/undefined value, being a symptom of a probable bug, should be reported as a TypeError rather than swept under the rug.

To clarify, would undefined be an expected scenario in this app if all the code was written correctly?

Expected for what and where?
If you mean for userData I would have to say no, that isn't expected. If userData somehow doesn't exist, that would be a major error that should be caught and corrected. Pretty much anytime you see userData?.someProperty it isn't a solution to userData not existing. If userData?.someProperty evaluates to undefined we have a problem. And that can't be solved by not throwing, that doesn't fix anything.

thank you, yes I was referring to the userData?.currentSong as that was the original topic for discussion. So since it will effectively never be undefined (unless fCC project code has a bug), does it still make sense to force the camper to type playSong(userData?.currentSong.id); to pass the check for this step? (I understand that in theory, undefined is a possible outcome if there is a bug in the code)

This may actually be bigger than expected.
let userData = {
  songs: [...allSongs],
  currentSong: null,
  songCurrentTime: 0,
};

userData is declared with let, but I don't see it reassigned. So that should probably be const.
Which means userData?.<prop> is entirely unnecessary, because userData can never be undefined or null. So we'd want to remove that specific optional chaining from the entire project.

I was wondering if it (optional chaining) was just being introduced for the sake of introducing it so I was okay with it being pretty much everywhere till I felt that the checking was too strict. But t.b.h. I found the steps where it said that we didn’t need it maybe a bit more confusing than the ones that needed it because I couldn’t directly map (or intuitively map) the need for it at most points. (Unless we are protecting against coding bugs)
Where would you introduce optional chaining if not in this project though?

I'm not sure. Probably in the fetch project, where we're working with external APIs and undefined responses might be expected.

just fyi, we have one person in the forum who also had some questions about this step and others where ?. is used https://forum.freecodecamp.org/t/javascript-music-player-step-43-possible-unnecessary-use-of-optional-chaining/716045


Single-command Docker-compose deploy

It'd be great to have a way to run shynet from scratch based on a single docker-compose file.
I finished most of the (minor) adaptations that are needed in order to get that running, so I'll PR when I'm done.
For transparency, modifications include:

exposing current function Arguments as Environement variables (https://github.com/milesmcc/shynet/tree/master/shynet/core/management/commands)
Adding a check to Webserver.sh to query postgre on startup and check:

if the db is running (otherwise exit container)
if the database tables exist, otherwise run migrate
if the admin user is set, otherwise run createadmin with the env passed as parameter
if the hostname is set, otherwise run hostname with with the env passed as parameter
if the whitelabel is set, otherwise run whitelabel with the env passed as parameter

the Compose file itself is pretty much ready but I suck at postgre so it' staking me a while to write valid checks in the bash.

Got it! Thanks for the contribution. I'm looking forward to the PR when it comes!
And just a side note (you're probably doing it this way already): definitely write your DB checks using Python via the Django ORM, and not directly as SQL. That way we can keep complexity centralized.

Yup, I can't actually do the DB checks via the DB anyway because they're called from the shynet container, not the db one, so the psql command doesn't exist :)
That said I suck at Python/Django so it'll take me a bit. Getting the compose file ready was easy, that part is harder for me :(


manage Azure Pipelines permissions and/or try github actions

In migrating to the jupyterhub org, I had to set up Azure devops anew. I ran into some weirdness because DevOps appears to not have any real GitHub integration in terms of accounts and permissions. There are two results of this:

I apparently didn't (and don't) have permissions on the jupyter/repo2docker pipeline, and
I am now the only person with access to the new one

I didn't realize (or maybe I just haven't found it) that Azure had this limitation, and it seems like a pretty big downside. CircleCI, Travis, etc. all support delegating permissions to the repo itself, which means we don't need to manage yet another set of accesses.
So we need to either:

figure out the right way to manage permissions on the Azure pipelines (I can grant permission to anyone who wants it), or
switch to something like GitHub actions, which I'm pretty pleased with, especially based on what @sgibson91 has been doing across various repos

My current slight inclination is to give GitHub actions a try, since I haven't had particularly good experiences with Azure pipelines (their uniquely short log retention is a common source of frustration), and several tests had to be retried in #940 (at least) three times due to warnings like:

The remote provider has asked us to wait until 8/10/2020 9:55:13 AM before attempting to provision a resource. This will cause delays in the running of this request.

which suggests the high capacity and short queues that were once part of the reason to migrate is no longer the case.
Maybe that was because of some different configuration in the pipeline that I set up wrong, since I can't see the original. But even if that's the case, having any configuration that's not in the repo itself is a mark against Pipelines for me. I'm not opposed to sticking with Pipelines and just working out the kinks we have left, if folks are more inclined that way.
What do folks think? The main reason we moved to DevOps was the much greater concurrency available in the free tier when compared to Travis (#744) and I wonder if GitHub Actions is similar?

👍  for GitHub actions. I've switched to it on my own new repos and it's more reliable than travis, and so far I haven't seen any delays in running jobs. Also not requiring people to setup an Azure account to gain access to the pipeline is another benefit. I've used Azure Pipelines on one other project (predates GitHub Actions)- people can sign-in to Azure using their GitHub account, and it should be possible to add those people to the project, but as you found it's not automatic.

Also +1 on GitHub Actions. I basically only use Azure Pipelines if there's an Azure resource I directly want to interact with because handling permissions for that resource is all Service Principal-based. If it's not an Azure resource, I do it with GHAs :)


Add STDP support

Add reinforcements learning and STDP learning to neurons

[ ] Unsupervised  learning STDP Rule
[ ] Spiking Neural network with (10,2) shape
[ ] Spking (10,2) Neural Network for with inhibitory neuron connected to last layers


(my) patreon form wing render glitch

yeah, okay so the latest update was supposed to fix the improper rigging on the wings, and yeah it did, but uh not for my patreon form, wing rigging on that is still bugged like before
ign is FailnNoFail, same as my username here

https://github.com/LtxProgrammer/patreon-benefits/commit/fd741577ade1700c7217176136e2252028dd55e9


Generate migrations from blueprint

What would you like to see added?
This is something I've told a couple of people about but essentially, my plan at some point is to build a way to automatically generate database migrations, based on field configurations from your blueprint.
How would it work?
It would be smart enough to know which column type each builtin fieldtype should be and it would be clever to change that if max_assets is defined.
If we don't know which column type to use (eg. custom fieldtype) we could maybe just leave it as a string/json column and give the user an error?
This would be some sort of command, like: php please runway:migration order
Considerations

It would also need to know how to handle changes in a blueprint (eg. field added, field removed, field config changed, etc). I guess in that case we'd just need to do a comparison to what's there and make a new migration with the relevant changes.

Is there a workaround you can use in the meantime?
You could just do it by hand, which is a bit of a sucky option because you then have to define everything twice.
Priority wise - where's this feature for you?
This is just a nice to have. I can deal without.

I was thinking about this the other day, nearly started a PR.
It would also be good to have a php please runway:blueprint Order. Where the schema of the model could be mapped or best guessed to a fieldtype and generate a blueprint based on that.
Both are useful, because sometimes you already have an app with your migrations and models already existing, and other times on greenfield projects it would be good to use the blueprint builder to make the migration for you.

Yeah that's a good idea. Didn't think about the other side of it.

It would be a bit of guess work on what column is what fieldtype, but defaulting to text would be okay.
Especially if the Statamic PR for addons registering their own blueprints gets merged, then you can go in and make the tweaks in the CP blueprint builder.

I've created a pull request for creating migrations from blueprints, it's pretty much ready to merge, just need to check over it again.
Would you mind opening another issue for the 'migration > blueprint' flow? As this one will be closed when the PR is merged.


metadata: move models to Arsenal

The models are the module BucketInfo, ObjectMD, WebsiteConfiguration and
ReplicationConfiguration.
These models are needed for the S3SOFS feature into the cdmiclient
repository. The S3 one does not export modules and shared ones are in
Arsenal so move these model modules to it.
Pull request template
Description
Motivation and context
Why is this change required? What problem does it solve?
Related issues
Please use the following link syntaxes #600 to reference issues in the
current repository
Checklist
Add tests to cover the changes
New tests added or existing tests modified to cover all changes
Code conforms with the style guide
Sign your work
In order to contribute to the project, you must sign your work
https://github.com/scality/Guidelines/blob/master/CONTRIBUTING.md#sign-your-work
Thank you again for contributing! We will try to test and integrate the change
as soon as we can.

@ironman-machine go

Hello @jeremyds
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "dev/models-in-arsenal"}
Please follow http://ci.ironmann.io/gh/scality/Integration/14094 for CI status.

@ironman-machine go

Hello @jeremyds
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "dev/models-in-arsenal"}
Please follow http://ci.ironmann.io/gh/scality/Integration/14097 for CI status.

So, the tests failure are caused by two things:

because the models code / tests in S3 has been modified since the PR adding them to Arsenal has been merged (by me....),
a test is broken since the delimiterTools is exported in Arsenal (guilty again).

These two problems are handled in two PRs, in Arsenal and in S3. I will rebase this branch and relaunch the tests once they will be merded.

@ironman-machine

Hello @rahulreddy
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "dev/models-in-arsenal"}
Please follow http://ci.ironmann.io/gh/scality/Integration/14117 for CI status.


Add de-bloat for release mode.

Hello, just found this awesome template!
I just recommend adding the recommended debloat release settings from Tauri
see here
https://tauri.studio/en/docs/usage/guides/bundler/anti-bloat

Thank you!
I read the link and check the size of app.
Your change makes this template better!


[Bug] Pip install fails

Hi,
With a conda environment with python 3.9 and itk 5.3.0 installing through pip fails.  Specifically, this error gets thrown:
ERROR: Could not find a version that satisfies the requirement itk-ioomezarrngff (from versions: none)ERROR: No matching distribution found for itk-ioomezarrngff

When trying to install from source it gives:
× python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      running egg_info
      creating /tmp/pip-pip-egg-info-x5670qbg/itk_ioomezarrngff.egg-info
      writing /tmp/pip-pip-egg-info-x5670qbg/itk_ioomezarrngff.egg-info/PKG-INFO
      writing dependency_links to /tmp/pip-pip-egg-info-x5670qbg/itk_ioomezarrngff.egg-info/dependency_links.txt
      writing requirements to /tmp/pip-pip-egg-info-x5670qbg/itk_ioomezarrngff.egg-info/requires.txt
      writing top-level names to /tmp/pip-pip-egg-info-x5670qbg/itk_ioomezarrngff.egg-info/top_level.txt
      writing manifest file '/tmp/pip-pip-egg-info-x5670qbg/itk_ioomezarrngff.egg-info/SOURCES.txt'
      error: package directory 'itk' does not exist
      [end of output]

Hi @melonora ,
Could more details please be provided on:

Your operating system, e.g. macOS, Linux, Windows
The hardware architecture, e.g. ARM, AMD64
pip version

Thanks!


Refactor after QWERTZ

As as an optional "bonus" to the qwertz pull request, I tried to refactor the code a bit. No idea if it's idiomatic coffeescript (first time I used this), but it's much shorter and much less redundant. Also, no more qwertz-hacks (except for the 'ö' keycode).

looks very good!

Clean code ! I tested locally and the keycode 192 doesn't seem to work on chrome and ff (mac).
The keycode 186 worked for me on both. Where did you get 192 ?

When I press the 'ö' key on my QWERTZ keyboard in Chromium (Linux), "e.keyCode" and "e.which" are 192. In Firefox, the values are 0, but apparently that's a known issue.


fix: update charts endpoint params + update value source vars

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[BUG] Roblox is not launching.

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
I went to "C:\Users\User\AppData\Local\Bloxstrap\Roblox\Player" and the roblox files were gone.
Bloxstrap Log
2024-10-18T21:32:59Z [App::OnStartup] Starting Bloxstrap v2.8.0
2024-10-18T21:32:59Z [App::OnStartup] Compiled Wednesday, 16 October 2024 at 4:44:37 AM from commit 42ffec26cf2e080fe22210305a08fcb286aeb577 (tag/v2.8.0)
2024-10-18T21:32:59Z [App::OnStartup] Loaded from %UserProfile%\AppData\Local\Bloxstrap\Bloxstrap.exe
2024-10-18T21:32:59Z [App::OnStartup] Temp path is %UserProfile%\AppData\Local\Temp\Bloxstrap
2024-10-18T21:32:59Z [App::OnStartup] WindowsStartMenu path is %UserProfile%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
2024-10-18T21:32:59Z [Logger::Initialize] Initializing at %UserProfile%\AppData\Local\Bloxstrap\Logs\Bloxstrap_20241018T213259Z.log
2024-10-18T21:32:59Z [Logger::Initialize] Finished initializing!
2024-10-18T21:32:59Z [JsonManager<Settings>::Load] Loading from %UserProfile%\AppData\Local\Bloxstrap\Settings.json...
2024-10-18T21:32:59Z [JsonManager<Settings>::Load] Loaded successfully!
2024-10-18T21:32:59Z [JsonManager<State>::Load] Loading from %UserProfile%\AppData\Local\Bloxstrap\State.json...
2024-10-18T21:32:59Z [JsonManager<State>::Load] Loaded successfully!
2024-10-18T21:32:59Z [FastFlagManager::Load] Loading from %UserProfile%\AppData\Local\Bloxstrap\Modifications\ClientSettings\ClientAppSettings.json...
2024-10-18T21:32:59Z [FastFlagManager::Load] Loaded successfully!
2024-10-18T21:32:59Z [FastFlagManager::SetValue] Setting of 'FLogNetwork' to '7' is pending
2024-10-18T21:33:04Z [LaunchHandler::LaunchRoblox] Initializing bootstrapper
2024-10-18T21:33:04Z [LaunchHandler::LaunchRoblox] Initializing bootstrapper dialog
2024-10-18T21:33:04Z [Bootstrapper::Run] Running bootstrapper
2024-10-18T21:33:04Z [Bootstrapper::SetStatus] Connecting to Roblox...
2024-10-18T21:33:04Z [Deployment::TestConnection<https://setup.rbxcdn.com>] Connecting...
2024-10-18T21:33:04Z [HttpClientLoggingHandler::ProcessRequest] GET https://setup.rbxcdn.com/versionStudio
2024-10-18T21:33:05Z [Deployment::InitializeConnectivity] Testing connectivity...
2024-10-18T21:33:05Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://setup.rbxcdn.com/versionStudio
2024-10-18T21:33:05Z [Deployment::InitializeConnectivity] Got https://setup.rbxcdn.com as the optimal base URL
2024-10-18T21:33:05Z [Bootstrapper::Run] Connectivity check finished
2024-10-18T21:33:05Z [Bootstrapper::CheckForUpdates] Checking for updates...
2024-10-18T21:33:05Z [HttpClientLoggingHandler::ProcessRequest] GET https://api.github.com/repos/bloxstraplabs/bloxstrap/releases/latest
2024-10-18T21:33:06Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://api.github.com/repos/bloxstraplabs/bloxstrap/releases/latest
2024-10-18T21:33:06Z [Bootstrapper::CheckForUpdates] No updates found
2024-10-18T21:33:06Z [Bootstrapper::GetLatestVersionInfo] Got channel as production
2024-10-18T21:33:06Z [Deployment::GetInfo] Getting deploy info for channel production
2024-10-18T21:33:06Z [HttpClientLoggingHandler::ProcessRequest] GET https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer
2024-10-18T21:33:06Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer
2024-10-18T21:33:06Z [RegistryKeyEx::SetValueSafe] Writing '' to HKEY_CURRENT_USER\SOFTWARE\ROBLOX Corporation\Environments\RobloxPlayer\Channel\www.roblox.com
2024-10-18T21:33:06Z [HttpClientLoggingHandler::ProcessRequest] GET https://setup.rbxcdn.com/version-9dbf9780562444e1-rbxPkgManifest.txt
2024-10-18T21:33:06Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://setup.rbxcdn.com/version-9dbf9780562444e1-rbxPkgManifest.txt
2024-10-18T21:33:06Z [Bootstrapper::SetStatus] Upgrading {product}...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.RobloxApp.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::ExtractPackage] Extracting RobloxApp.zip...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-avatar.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-configs.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-fonts.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::ExtractPackage] Extracting content-avatar.zip...
2024-10-18T21:33:09Z [Bootstrapper::ExtractPackage] Extracting content-configs.zip...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-models.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-sky.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-sounds.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::ExtractPackage] Finished extracting content-configs.zip
2024-10-18T21:33:09Z [Bootstrapper::ExtractPackage] Extracting content-fonts.zip...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.shaders.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.ssl.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-textures2.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-textures3.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-terrain.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.content-platform-fonts.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.extracontent-places.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.extracontent-luapackages.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.extracontent-translations.zip] Package is already downloaded, skipping...
2024-10-18T21:33:09Z [Bootstrapper::DownloadPackage.extracontent-models.zip] Package is already downloaded, skipping...
2024-10-18T21:33:10Z [Bootstrapper::DownloadPackage.extracontent-textures.zip] Package is already downloaded, skipping...
2024-10-18T21:33:10Z [Bootstrapper::DownloadPackage.WebView2.zip] Package is already downloaded, skipping...
2024-10-18T21:33:10Z [Bootstrapper::DownloadPackage.WebView2RuntimeInstaller.zip] Package is already downloaded, skipping...
2024-10-18T21:33:10Z [Bootstrapper::DownloadPackage.redist.zip] Package is already downloaded, skipping...
2024-10-18T21:33:10Z [Bootstrapper::SetStatus] Configuring {product}...
2024-10-18T21:33:10Z [Bootstrapper::ExtractPackage] Finished extracting content-avatar.zip
2024-10-18T21:33:10Z [Bootstrapper::ExtractPackage] Extracting content-models.zip...
2024-10-18T21:33:10Z [Bootstrapper::ExtractPackage] Finished extracting content-models.zip
2024-10-18T21:33:10Z [Bootstrapper::ExtractPackage] Extracting content-sky.zip...
2024-10-18T21:33:10Z [Bootstrapper::ExtractPackage] Finished extracting content-sky.zip
2024-10-18T21:33:10Z [Bootstrapper::ExtractPackage] Extracting content-sounds.zip...
2024-10-18T21:33:10Z [Bootstrapper::ExtractPackage] Finished extracting content-fonts.zip
2024-10-18T21:33:10Z [Bootstrapper::ExtractPackage] Extracting shaders.zip...
2024-10-18T21:33:11Z [Bootstrapper::ExtractPackage] Finished extracting content-sounds.zip
2024-10-18T21:33:11Z [Bootstrapper::ExtractPackage] Extracting ssl.zip...
2024-10-18T21:33:11Z [Bootstrapper::ExtractPackage] Finished extracting ssl.zip
2024-10-18T21:33:11Z [Bootstrapper::ExtractPackage] Extracting content-textures2.zip...
2024-10-18T21:33:12Z [Bootstrapper::ExtractPackage] Finished extracting shaders.zip
2024-10-18T21:33:12Z [Bootstrapper::ExtractPackage] Extracting content-textures3.zip...
2024-10-18T21:33:15Z [Bootstrapper::ExtractPackage] Extracting content-terrain.zip...
2024-10-18T21:33:16Z [Bootstrapper::ExtractPackage] Finished extracting content-terrain.zip
2024-10-18T21:33:16Z [Bootstrapper::ExtractPackage] Extracting content-platform-fonts.zip...
2024-10-18T21:33:16Z [Bootstrapper::ExtractPackage] Finished extracting RobloxApp.zip
2024-10-18T21:33:16Z [Bootstrapper::ExtractPackage] Extracting extracontent-places.zip...
2024-10-18T21:33:17Z [Bootstrapper::ExtractPackage] Finished extracting content-textures3.zip
2024-10-18T21:33:17Z [Bootstrapper::ExtractPackage] Extracting extracontent-luapackages.zip...
2024-10-18T21:33:17Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-places.zip
2024-10-18T21:33:17Z [Bootstrapper::ExtractPackage] Extracting extracontent-translations.zip...
2024-10-18T21:33:17Z [Bootstrapper::ExtractPackage] Finished extracting content-platform-fonts.zip
2024-10-18T21:33:17Z [Bootstrapper::ExtractPackage] Extracting extracontent-models.zip...
2024-10-18T21:33:17Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-translations.zip
2024-10-18T21:33:17Z [Bootstrapper::ExtractPackage] Extracting extracontent-textures.zip...
2024-10-18T21:33:18Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-models.zip
2024-10-18T21:33:21Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-luapackages.zip
2024-10-18T21:33:21Z [Bootstrapper::ExtractPackage] Extracting WebView2.zip...
2024-10-18T21:33:21Z [Bootstrapper::ExtractPackage] Finished extracting WebView2.zip
2024-10-18T21:33:21Z [Bootstrapper::ExtractPackage] Extracting redist.zip...
2024-10-18T21:33:23Z [Bootstrapper::ExtractPackage] Finished extracting redist.zip
2024-10-18T21:33:39Z [Bootstrapper::ExtractPackage] Finished extracting extracontent-textures.zip
2024-10-18T21:33:57Z [Bootstrapper::ExtractPackage] Finished extracting content-textures2.zip
2024-10-18T21:33:57Z [Bootstrapper::UpgradeRoblox] Writing AppSettings.xml...
2024-10-18T21:33:57Z [Bootstrapper::UpgradeRoblox] Registering approximate program size...
2024-10-18T21:33:57Z [RegistryKeyEx::SetValueSafe] Writing '444669' to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\Bloxstrap\EstimatedSize
2024-10-18T21:33:57Z [Bootstrapper::UpgradeRoblox] Registered as 444669 KB
2024-10-18T21:33:57Z [JsonManager<State>::Save] Saving to %UserProfile%\AppData\Local\Bloxstrap\State.json...
2024-10-18T21:33:57Z [JsonManager<State>::Save] Save complete!
2024-10-18T21:33:57Z [Bootstrapper::SetStatus] Applying Roblox modifications...
2024-10-18T21:33:57Z [Bootstrapper::ApplyModifications] Checking file mods...
2024-10-18T21:33:57Z [Bootstrapper::ApplyModifications] ClientSettings\ClientAppSettings.json has been copied to the version folder
2024-10-18T21:33:57Z [JsonManager<State>::Save] Saving to %UserProfile%\AppData\Local\Bloxstrap\State.json...
2024-10-18T21:33:57Z [JsonManager<State>::Save] Save complete!
2024-10-18T21:33:57Z [Bootstrapper::ApplyModifications] Finished checking file mods
2024-10-18T21:33:57Z [Bootstrapper::SetStatus] Starting {product}...
2024-10-18T21:34:04Z [LaunchHandler::LaunchRoblox] Bootstrapper task has finished
2024-10-18T21:34:04Z [LaunchHandler::LaunchRoblox] An exception occurred when running the bootstrapper
2024-10-18T21:34:04Z [App::FinalizeExceptionHandling] System.ComponentModel.Win32Exception (740): An error occurred trying to start process '%UserProfile%\AppData\Local\Bloxstrap\Roblox\Player\RobloxPlayerBeta.exe' with working directory '%UserProfile%\AppData\Local\Bloxstrap\Roblox\Player'. The requested operation requires elevation.
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Bloxstrap.Bootstrapper.StartRoblox()
   at Bloxstrap.Bootstrapper.Run()
   at Bloxstrap.Bootstrapper.Run()

I tried reinstalling bloxstrap

Read the Wiki next time. https://github.com/bloxstraplabs/bloxstrap/wiki/"The-requested-operation-requires-elevation"-error-when-launching-Roblox


fix build error.

Attempt at fixing the build error from #186

Can we put this in the template too?


Added folding markers for: object definition, multiline comment, heregex...

..., heredoc (both ' and "), open parenthesis, switch, if, until, else, try, catch, for, while.  Inside heregex blocks, #included patterns from source.regexp.oniguruma to achieve regex coloring.
Since Coffeescript is so terse, the folding markers on if, until, and else might be overkill.  I can tone it down if that is desirable.

The revert -> commit was only to fix the whitespace so the diff would come out right.  Feel free to squash.


[WIP] 3 arg update_func

fix https://github.com/SciML/SciMLOperators.jl/issues/202
Operators should accept a single update_func with two methods A = update_func(u, p, t), and update_func(A, u, p, t) # = nothing. The DEFAULT_UPDATE_FUNC shall return nothing to indicate that no update has taken place.
TO DO

[ ] remove update_func!
[ ] add 3 arg DEFAULT_UPDATE_FUNC
[ ] bump version to 0.4

Hey, what's the status of this? It could be good to merge soon-ish to minimize the amount of code in the old style we'll have to adjust


[5.9🍒] prevent reinitialization of self after discard

• Description: Adds a missing piece of SE-390 where we want to prevent reinitialization of self after discarding it, since it doesn't make sense to permit that and can limit our ability to implement discard more generally in the future.
• Risk: Medium. Will introduce a source break in functions that are using discard self and reinitialize self at some point reachable afterwards. (see test/SILOptimizer/discard_checking.swift for examples). The set of programs using discard is probably quite small currently and we'd want to introduce this change early, though the error could be downgraded into a warning for 5.9 upon request.
• Original PR: https://github.com/apple/swift/pull/66351
• Reviewed By: @gottesmm
• Testing: regression tests included
• Resolves: rdar://106098163

I rebased this on top of https://github.com/apple/swift/pull/65449 since it depends on those changes.

@swift-ci please test

@swift-ci clean test macOS platform


chore: bdd-spring-1572795001 to 0.0.1

chore: Promote bdd-spring-1572795001 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


Option 'Download CNC exporting post processor' now redirects to the Fusion post library website

Removed the export CNC file to VS Code post from the extension since it is available on the post library website now.
The option within  the extension to download the post now redirects to the library directly.

Perfect, thanks!


Path Validation Error when caching on container jobs

When I use the cache action with a container job, the cache is not saved during the post cache step and instead I get the following error
Post job cleanup.
/usr/bin/docker exec  ecc19d4d[2](https://github.com/daoudi-mohammed/spring-boilerplate/runs/6771275062?check_suite_focus=true#step:10:2)b410eadd[3](https://github.com/daoudi-mohammed/spring-boilerplate/runs/6771275062?check_suite_focus=true#step:10:3)082d7a7d5d22cc782f29dfba69ac4a8edc83090a10843c sh -c "cat /etc/*release | grep ^ID"
Warning: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

Here is the code for my job
jobs:
  unit-tests:

    runs-on: ubuntu-latest

    container: openjdk:17-jdk-alpine

    steps:
      - name: Setup git
        working-directory: ""
        run: |
          apk add -q --no-cache --no-progress git yq tar
          git config --global --add safe.directory $GITHUB_WORKSPACE

      - name: Check out repository code
        uses: actions/checkout@v2

      - name: Cache maven packages
        uses: actions/cache@v3
        with:
          path: |
            ${{ github.workspace }}/.m2/repository
          key: test

      - name: Run liquibase update
        run: |
          mkdir -pv ${{ github.workspace }}/.m2/repository/
          echo "hello" > ${{ github.workspace }}/.m2/repository/hello.txt

I tried replacing the ${{ github.workspace }} with it's exact value (absolute path) but nothing worked.
However when I use a hardcoded path that has nothing to do with ${{ github.workspace }} it works
with:
          path: |
            /test/.m2/repository
          key: test

      - name: Run liquibase update
        run: |
          mkdir -pv test/.m2/repository/
          echo "hello" > test/.m2/repository/hello.txt

Hi @Iduoad
Few questions for you.

Are you using windows image? What all images are you facing this issue on?
What is the size of cache that's getting generated for you when you're hardcoding the path? Can you please share the logs?

Thanks for sharing the info @Iduoad
I used the workflow you shared with and without ${{ github.workspace }}
I was able to run without any issues with ${{ github.workspace}} , here's my workflow file and corresponding run with
debug logs
Then I tried replacing the ${{ github.workspace}} path with hardcoded paths as you suggested -
         path: |
           /test/.m2/repository
         key: test
     - name: Run liquibase update
       run: |
         mkdir -pv test/.m2/repository/
         echo "hello" > test/.m2/repository/hello.txt

Here's my workflow file and corresponding run with debug logs after replacing ${{ github.workspace}} with hardcoded values . However this time I got the error that you mentioned -
Warning: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

Then I realised that you are using /test in the path for Cache maven packages whereas the Run liquibase update runs in current working directory with test/... without / before the test. In other words /test is present at the root directory of your image whereas test/... is present in current working directory of your image. The current working directory is usually /home/runner/work/repo-name/repo-name so test/... would actually be /home/runner/work/repo-name/repo-name/test/... resulting into the following error -

As you can see Cache Paths is having [] an empty array here because the path mentioned doesn't exist.
To confirm that, I ran the hardcoded workflow again, but this time without the / root reference /test. Here's my workflow file and corresponding run with debug logs with test for the same.
As you can see below, this time the paths were found and cache was saved successfully.

Please check the workflows and their outputs and let me know if you see any issues in the executions I've done based on the info you've provided. If everything seems correct, please validate your actual workflow files for any typo or / root references.
The Path Validation Error warning you have received is a recent implementation done to avoid empty cache saves. And this also helps users realise that the paths they've provided might not have any content at all if provided incorrectly.
Do let me know your findings, happy to help! :)

Thank you @kotewar for the detailed description.
The only difference is that I run a container job like I mentioned before.
Sorry if that wasn't clear. I edited the issue's description to mention that.
Here is the workflow file
jobs:
  unit-tests:

    runs-on: ubuntu-latest

    container: openjdk:17-jdk-alpine

    steps:
      - name: Setup git
        working-directory: ""
        run: |
          apk add -q --no-cache --no-progress git yq tar
          git config --global --add safe.directory $GITHUB_WORKSPACE

      - name: Check out repository code
        uses: actions/checkout@v2

      - name: Cache maven packages
        uses: actions/cache@v3
        with:
          path: |
            ${{ github.workspace }}/.m2/repository
          key: test

      - name: Run liquibase update
        run: |
          mkdir -pv ${{ github.workspace }}/.m2/repository/
          echo "hello" > ${{ github.workspace }}/.m2/repository/hello.txt

Let me check the behaviour with openjdk:17-jdk-alpine and get back to you.

Here's the difference after using openjdk container.
The search path is getting evaluated to -

Search path '/__w/learning-actions/learning-actions/.m2/repository'

whereas the given path in action is - /home/runner/work/learning-actions/learning-actions/.m2/repository

[Workflow file](https://github.com/kotewar/learning-actions/actions/runs/2460328311/workflow) [logs](https://github.com/kotewar/learning-actions/runs/6790248919?check_suite_focus=true)
I need to find out why the value of `${{ github.workspace }}` needs to be `/__w` in case of `openjdk:17-jdk-alpine` container.
Note - I've used previous version v3.0.2 of @actions/cache hence its not giving any error message, but also it would be storing and restoring empty cache as nothing exists at the path provided.

This is a mixed scenario where the workflow is running on ubuntu image sometimes, and on the container the rest of the times. That's why ${{ github.workspace }} is sometimes evaluated as /__w and /home/runner/work/repo-name/repo-name the rest of the times. To investigate the issue, we went ahead to understand the behaviour of actions when ran in a container. If interested to know, please refer the workflow and run executed to understand the same. The logs will give you a better idea of the same.
To conclude our understandings, here's what we found -

Containers will always have ${{ github.workspace }} as /__w. If anything is running with /home/runner/work/repo-name/repo-name as current working directory, its outside your container in the ubuntu-latest image (or base image for that matter).
To run actions cache inside the container for java application, the appropriate location of .m2 folder must be known. After investigation, it turns out that .m2 folder in openjdk:17-jdk-alpine is actually present at /root/.m2/repository location. So this should actually be the path that must be used to cache the /.m2/repository folder. Refer this
After the /.m2 folder is located, it should be referred in path parameter of the cache action.

Sample code to get .m2 folder location and setting it in the appropriate location.
     - id: cache-path
        run: |
          echo "::set-output name=dir::$(mvn help:evaluate -Dexpression=settings.localRepository | grep 'm2/repository')"
      - name: Cache maven packages
        id: cache
        uses: actions/cache@v3
        with:
          path: |
            ${{ steps.cache-path.outputs.dir }}
          key: test_100

Please try using this and see if you get the expected results. You can refer this workflow.
Hope this helps! 😊

It definitely helps! Thank you so much @kotewar


Create ReverseString...cpp

Thank you
I have already given a star to your repo.
On Thu, 7 Oct 2021 at 18:22, Shubham Bawankar @.***>
wrote:

Merged #177
https://github.com/Shubham56-droid/DataStruture-and-algroithms-program/pull/177
into main.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Shubham56-droid/DataStruture-and-algroithms-program/pull/177#event-5428303405,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATW6J77HZBE7GM5BKHLYWT3UFWJXTANCNFSM5FQZKDQA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


CBT Tape Annual Review- 10/13

Please share any additional details on this topic
Annual review for CBT Tape. @neopragma let me know if you need anything in preparation for the meeting.
Detail what actions or feedback you would like from the TAC
Annual review and vote for renewal for CBT Tape. @neo

CBT Tape renewed for another year per TAC vote


Generate grouping poms for easier execution per-structure

Generate grouping poms for easier execution of all projects generated for given structure.

LGTM 😛


Create pylint.yml

Description

Please include a summary of the changes and the related issue.
Fixes # (issue)

Type of change

[ ] New features (non-breaking change).
[ ] Bug fix (non-breaking change).
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected).

Checklist

[ ] I have performed a self-review of my code.
[ ] I have added thorough tests if it is a core feature.
[ ] There is a reference to the original bug report and related work.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] The feature is well documented.

I think adding pylint to .pre-commit-config.yaml would be better. This repo already has a workflow for  style-check.
cc: @taprosoft


[FIX] fixing some minor issues introduced recently

Individual commits describe fixes better.
Follow up to https://github.com/bids-standard/bids-specification/pull/1392 .

[ ] make sure that fixed references worked out as expected

The CI error is unrelated as far as I can see. Link https://nipy.org/nibabel/coordinate_systems.html does not exist any more, but that can be fixed in a separate PR.

Looks like the nipy DNS is broken.


Fix args_are_cpp to look for -x without =

Clang doesn't allow = between -x and the language name.

LGTM, thanks!
@bors-servo r+

:pushpin: Commit 1c7f8c6 has been approved by emilio

:hourglass: Testing commit 1c7f8c61e959426f2a79ef1d73c5034ae923812f with merge c77f8c7975515aaafb680198d158ce03ca605b25...

:sunny: Test successful - status-travis
Approved by: emilio
Pushing c77f8c7975515aaafb680198d158ce03ca605b25 to master...


Fix grant Content-Type to application/json

From RFC6749:

The parameters are included in the entity-body of the HTTP response
using the "application/json" media type as defined by [RFC4627].  The
parameters are serialized into a JavaScript Object Notation (JSON)
structure by adding each parameter at the highest structure level.
Parameter names and string values are included as JSON strings.
Numerical values are included as JSON numbers.  The order of
parameters does not matter and can vary.

We were returning test/plain but the RFC specifies that application/json should be returned instead.

LGTM. Any reason I might be missing on why text/plain was being returned @thomseddon?

Non at all, that's a bug - thanks :)

Released as 1.0.1


Toggling visibility of a node inside an invisible parent causes the eye icon to stop being greyed out

Godot version
4.0.alpha2
System information
Windows 10
Issue description
When nodes are visible, their icons are lighter than when they are not. As a reference, here's how things look by default:

When you make a node invisible, it greys out the visibility icon of all of its children, as below:

However, if you hide and then re-show one of those children, this effect is lost:

This behaviour happens in v4.0 alpha 2, and definitely does not in v3.4. I don't currently have v3.5 so am unable to check there.
Steps to reproduce

Create a new scene, with any root node, eg a Node2D.
Create any child node under the root node, again a Node2D is fine.
Click the eye icon of the root node to make it invisible. The eye icon of the child node should desaturate.
Click the eye icon of the child node to make it invisible. It will correctly switch to the "closed eye" icon and stay grey.
Click the eye icon of the child node again. It will switch back to the "open eye" icon, but will lose its desaturated effect.

Minimal reproduction project
No response

Just realised I've not got 4.0 alpha3 yet, so grabbed it and found things are working fine, although I can't find the original issue or any fix.
Either way, looks like it's a false alarm, sorry!

This was likely fixed by #58315


Allow for podSelectorKey

This PR allows for the Grafana Rollout Operator to customize the key used to select for pods. My org's internal infra uses a different label from name and customizing it is trickier than having the rollout operator use for a different key instead.

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

I see that https://github.com/grafana/rollout-operator/pull/18 is currently pending review. This would also solve our problem, if it is a better solution than this.


Add missing dependency to Relational tests

Still running tests locally...

:shipit:

Hmm, now I'm getting

error CS0246: The type or namespace name 'IServiceCollection' could not be found (are you missing a using directive or an assembly reference?)

@anurse Is something currently broken in dependency resolution?

Not that I know of

Merged as part of 98bcccd99eff9b85f17a8ac6782894d4b75dcc8d


FileFilter some parameters are not optional

Hi,
In the OpenMS FileFilter version 2.5 and 2.6 some parameters seem to be set to optional despite they shouldn't be.
Running the tool with default parameters gives the following error:
Invalid string parameter value 'None' for parameter 'remove_mode' given! Valid values are: 'Unknown,MassSpectrum,MS1Spectrum,MSnSpectrum,SelectedIonMonitoring,SelectedReactionMonitoring,ConsecutiveReactionMonitoring,ConstantNeutralGain,ConstantNeutralLoss,Precursor,EnhancedMultiplyCharged,TimeDelayedFragmentation,ElectromagneticRadiation,Emission,Absorption'. Updating failed!
Invalid string parameter value 'None' for parameter 'remove_activation' given! Valid values are: 'Collision-induced dissociation,Post-source decay,Plasma desorption,Surface-induced dissociation,Blackbody infrared radiative dissociation,Electron capture dissociation,Infrared multiphoton dissociation,Sustained off-resonance irradiation,High-energy collision-induced dissociation,Low-energy collision-induced dissociation,Photodissociation,Electron transfer dissociation,Pulsed q dissociation'. Updating failed!
Invalid string parameter value 'None' for parameter 'select_mode' given! Valid values are: 'Unknown,MassSpectrum,MS1Spectrum,MSnSpectrum,SelectedIonMonitoring,SelectedReactionMonitoring,ConsecutiveReactionMonitoring,ConstantNeutralGain,ConstantNeutralLoss,Precursor,EnhancedMultiplyCharged,TimeDelayedFragmentation,ElectromagneticRadiation,Emission,Absorption'. Updating failed!
Invalid string parameter value 'None' for parameter 'select_activation' given! Valid values are: 'Collision-induced dissociation,Post-source decay,Plasma desorption,Surface-induced dissociation,Blackbody infrared radiative dissociation,Electron capture dissociation,Infrared multiphoton dissociation,Sustained off-resonance irradiation,High-energy collision-induced dissociation,Low-energy collision-induced dissociation,Photodissociation,Electron transfer dissociation,Pulsed q dissociation'. Updating failed!
Invalid string parameter value 'None' for parameter 'select_polarity' given! Valid values are: 'unknown,positive,negative'. Updating failed!
Once all these parameters are set to their default values the tool runs through.
I assume this can be fixed in the wrapper by removing  'optional=True' for these parameters:
"remove_mode", "remove_activation", "select_mode", "select_activation", "select_polarity"
@bernt-matthias I would appreciate if you could have a look ;)
Cheers,
Melanie

Will do.

Do you have a history to share?

Here you go: https://usegalaxy.eu/u/melanie-foell/h/filefilter-test  Thanks for checking it!

Think I got it. Apparently a bug in Galaxy itself https://github.com/galaxyproject/galaxy/pull/11380. I'm afraid that this might take some time since it needs to be accepted, backported, and rolled out.
In addition I will check if the additional option <option value="">default (nothing chosen)</option> can be removed. But this is not critical and does not change anything.

The change in Galaxy is now available for 20.05 - 21.01. @bgruening is usegalaxy.eu updated regularly?

Not automatically, but I just did it and deployment is running. @foellmelanie please reopen when it is not fixed.


TokenErrorResult with password grant type and mfa

Please only use the issue tracker for simple questions. For general security questions, or free / commercial support options do not use the issue tracker and instead see here for more details.
For questions containing large amounts of code we recommend submitting a question on stack overflow using the Identity Server 4. Our amazing community on Stack Overflow is there to help answer all of your questions.
Finally, please keep the issue concise and to the point if your question does include code be sure it is a Minimal working example. If you paste in more code than the text for your question then it probably belongs on Stack overflow.
Question / Steps to reproduce the problem
TokenEndpoint for password grant type returns 400 or 200 with access token. How to implement mfa so in case mfa is required I would expect 403 as it is described here https://auth0.com/docs/api-auth/tutorials/multifactor-resource-owner-password . I know that according to this response https://github.com/IdentityServer/IdentityServer4/issues/2805 specs expects only 400 but is there any good possible solution to distinguish between incorrect username or password or invalid clientId etc and kind of mfa_required error.
Minimal working example
<code goes here>

Relevant parts of the log file
<log goes here>

Auth0 is not the authoritative source for the OAuth spec.
I would set a custom error or token response element to indicate the MFA requirement to the client.

Danke and thank you :)


When new Commitish, cache should require bootstrap_vcpkg to run again

I was upgrading vcpkg to the new release (https://github.com/microsoft/vcpkg/releases/tag/2022.11.14) which supports "overlay-ports" in vcpkg-configuration.json.
When running with friendly_anon/setup-vcpkg with cache: true, it fails with the following message:
-- Running vcpkg install
warning: configuration contains the following unrecognized fields:

$.overlay-portsIf these are documented fields that should be recognized try updating the v
cpkg tool.

When running with cache: false it works as expected.
I'm running on self-hosted runners and unfortunately a private repo so I cannot link to a reproducible PR.
I solved it by clearing out the  _work/repo directory (hence the cache) on the self-hosted runner, but I imagine that it could also have been solved by rerunning bootstrap_vcpkg, to ensure that the vcpkg executable is recompiled with the newest definitions.
Again my problem has been solved, but you might have interest in hearing about this :)
Keep up the good work.

The committish input is already part of the hash:
https://github.com/friendlyanon/setup-vcpkg/blob/85a802286791d6ef61b4be4b806a4fcac728a894/src/main.ts#L23
How exactly is the action used?

Oh, nevermind. The recovery key is vcpkg-<os>(-<cache-version>)? and the hash is not considered there. You can change the cache version I guess, but this could probably be handled on the action's side.


Skips the spec

Expected behavior
It is skipping the spec
Actual behavior
It should execute the spec
Steps to reproduce
Specification Heading
=====================

* step2
----
* step2
___
* step2

Give the implementation

    @Step("step2")
    public void implementation2() {
    }

Version
Gauge version: 0.4.1.nightly-2016-05-13

Plugins
-------
csharp (0.7.3.nightly-2016-05-13)
html-report (2.1.1.nightly-2016-05-13)
java (0.4.1.nightly-2016-05-13)
xml-report (0.1.2.nightly-2016-05-13)

I don't see any scenarios in the example given. Are you trying to execute a spec with no scenario and just teardown steps?

In the above example

step2

step2 - This is a step of a scenario

step2 - This is the teardown step

The definition is ambiguous, * step2 is a valid step syntax, and since it is single underlined another interpretation is that it could be a scenario.
However, Gauge parses top-down, so
* step2
--------

would mean that step2 is a step and not a scenario. This is by design.

* step2

----
* step2

___
* step2

If this is a step and not a scenario,
then it should give me a parse error that
Scenario heading should have at least one character. But it executes and says
No scenarios found in spec: /Users/sswaroop/work/gauge-test-apps/basic-java/specs/subfolder/one.spec

Successfully generated html-report to => /Users/sswaroop/work/gauge-test-apps/basic-java/reports/html-report
Specifications:	0 executed	0 passed	0 failed	1 skipped
Scenarios:	0 executed	0 passed	0 failed	0 skipped

# spec
* step2

----
* step2
___
* step2

This is considered as a spec with no scenarios. Even the markdown considers
<empty line>
---

as br tag and not as h2. So message No scenarios found should be fine.


Fix broken link and add missing link

Summary
Fix broken link and add missing PR link for a feature in CHANGELOG.md.
Test plan
N/A

Codecov Report

Merging #6374 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6374   +/-   ##
=======================================
  Coverage   63.47%   63.47%
=======================================
  Files         227      227
  Lines        8677     8677
  Branches        4        3    -1
=======================================
  Hits         5508     5508
  Misses       3168     3168
  Partials        1        1

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 aff9681...137badb. Read the comment docs.

Thanks!


Cypress remove visual comparison and viewport settings in plugins

This PR resolves issue #2926 "Cypress fails to run with Chrome in headless mode".
Viewport settings which prevented Cypress running in headless mode using the Google Chrome web browser have been removed from cypress/plugins/index.js. The contents are reset to the minimum, similar to after installing Cypress 9.
The unused folder cypress/integration/__image_snapshots__ and contents is removed, including references to this folder. Visual comparison was disabled through https://github.com/corona-warn-app/cwa-website/pull/302 two years ago.
Verification
npx cypress run --config baseUrl=https://coronawarn.app --spec cypress/integration/mime.js --browser chrome --headless

runs without error after applying this PR.

Good morning @MikeMcC399, thanks for the PR, we will review it.

@dsarkar
Good morning to you too! Thanks for picking up this PR. I wondered for a long time why headless mode didn't work properly and I finally got around to investigating it!

Changes approved.
This will be merged into our ongoing cypress branch cypress-workflow and then into master later.


Invalid pattern **

Invalid pattern '\burl=api/ResumeSearch/SearchResultList/10-635**1/1/10\b' at offset 48. Nested quantifier '*'.

Dear Jon,
You have to use issue template from the .github folder.
Please add more details and reopen the issue.
I'm going to close because of the lack of details


Add Structs and global variables to the Array and Table section of the wiki

Added a guide on how structs work in detail, as well as a short explanation on makeing a variable global

Wow, nice PR, I'll get to it later today along with a few others.


fix the bug that secret will never be modified

What this PR does
Before this PR:
Value fileChangeDetected will be false always，and value reload will never equals true. In this case, secret in VMI will never be modified
After this PR:

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

@muxuelanKK do you mind writing a unit test which replicates the bug?
Out of scope of this PR,  the watchSecret function should also be refactor as it is very complex and hard to read.

/cc @akrejcir

This change does not seems to have any effect.

The initial value of fileChangeDetected is not relevant, because the variable reload := true, so secrets will be reloaded regardless of fileChangeDetected.
Moving the assignment to fileChangeDetected to the end of the loop does also have no effect, because in every branch in the loop, before a continue statement, the variable reload is set to true, and secrets will be reloaded in the next loop.

@muxuelanKK , Can you please describe how you hit this bug? Maybe it is an edge case and we need to solve it differently.

/hold on

Not a bug

Still the code could be probably "cleaner", any takers?

hold on


feat(footer): create custom footer

This PR creates our custom footer for Docusaurus. Some elements (credits, socials, legal links) are configurable via the docusaurus.config.js. The logos are hard-coded because they're highly unlikely to change, so we are not making them dynamic for now.
Note that Tailwind's preflight is enabled with this PR, so we might need to fix some basic styles along the way.

Good catch! I have fixed this with the last commits.

Good catch! I have fixed this with the last commits.

Great thx! I noticed I still have an overflow with the links in the bottom:

Uff, thanks! Now it should work 😄


The example about happy-eyeballs has a memory leak

Currently, if we run for a long time examples/happy/main.exe, we can observe that the memory just grows indefinitely. We don't have (yet?) the tools to track down where we have the memory leak.

The happy-eyeballs has no more memory leaks as far as we can observe.


Vision improvements

More telemetry
Reliable USB enumeration on startup
Bug fixes
Heartbeat-based conn. status

Reject rotation from single-target poses
Reject off-field robot poses

Done.


Add ccamel/playground-binding.scala to repos.md

Thanks for this amazing tool! :heart_eyes:
I would be very interested in having my repo added to your list!
Thanks!

Hi @ccamel, I've seen that you starred https://github.com/scala-steward/scala-steward. Thanks for that, but could do me a favor and unstar that repo and star https://github.com/fthomas/scala-steward instead? scala-steward/scala-steward is the bot's fork of this repo which it uses to propose updates and ideally it shouldn't receive any attention. :-) Thanks!

@fthomas No problem,with pleasure. :relaxed:


Render tracks as tiles

We're having problem wiith big libraries, TracksList render time is getting longer and longer, >3000 tracks make the render update noticeable with the eye.
We should implement what Atom has done with the editor view: render tracks in group (tiles), and only show the tiles needed when scrolling.
===

[x] Tracks as tiles (absolute + translate3d transformation)
[x] Show only needed tiles
[x] Use onScroll on .tracks-list-body instead of onWheel
[x] Move chunkArray to Store to improve performance even more ? (wontdo, not really needed, it takes 0.15ms)
[x] Fix multi-select with maj.

===
helpers:
http://blog.atom.io/2015/06/24/rendering-improvements.html
http://blog.atom.io/2014/07/02/moving-atom-to-react.html

First tests
Render time with 3200 tracks:

before: 100ms (O(n) tome complexity)
after: 6ms (O(1) time complexity)

All done.


Fix default compilation options construction in arrow sql runner implemenation

The runner would create an incorrect traits descriptor (i.e. with cuda-specific settings).

Do you need a similar change for pyhdk._sql.RelAlgExecutor.execute?

Yep, good catch. I think I should redo it a bit. Maybe make the platform a required parameter for defaults(). Otherwise, it gets messy.


Added bombardment in c#

If not using Visual Studio, can be run with the dotnet-cli.
Invoke from the command-line by navigating to the 11_Bombardment/csharp directory and typing dotnet run.

nice! 💥 Thank you!


Please add the sidebar

Is your feature request related to a problem? Please describe.
Yes, we cannot use the sidebar component that is outlined in the bootstrap documentation: https://bootstrap-vue.org/docs/components/sidebar
Describe the solution you would like
The sidebar added
Describe alternatives you have considered
None at this time since I'm trying to do a hackathon!
Additional context

Pretty sure it's called offcanvas in Bootstrap

I'm going to close this as completed since there has been no additional reply, this should be added, just not well documented.


Contribute

Hey @beardymcjohnface I think this is a good effort to make a package for that.
I had some similar scripts, even with doc test as it seems. https://github.com/metagenome-atlas/atlas/blob/master/atlas/init/create_sample_table.py
my scripts also are able to parese _1/_2 .1/.2 which are common fastq pair endings.
What do you think of incorporating my scripts or let me contribute to your repo?
what do you think of creating a csv file which follows the pep data structure. https://snakemake.readthedocs.io/en/stable/snakefiles/configuration.html#configuring-scientific-experiments-via-peps

Hi Silas,
I'd love to collaborate! I'm happy for you to add your scripts or to update fastq_finder to recognize _1/2 and .1/2, whichever you think is best. The idea behind parse_directory() was so that I could dump all my paired and/or single end reads into one folder and feed that into a pipeline. You can see it in action in trimnami and koverage.
I didn't realise PEPs were a thing in Snakemake and I think it might solve a headache I'm having with trimnami, in that I want it to generate a new file of sample names and their outputs so that it can be easily read in by another workflow. I think PEPs would be perfect for this, perhaps as a new module like pepper.py?


types:hashMethod and observable:HashNameEnum seem to be unrelated

As of today's master branch (cc1ba30), I don't see a way to relate the hash name enumeration in observable.ttl to types:hashMethod.
Would it be appropriate to replace:
types:hashMethod rdfs:range xsd:string
with:
types:hashMethod rdfs:range observable:HashNameEnum
?

This also seems to be true in today's turtle-cleanup head (c494954).

@ajnelson-nist , I'll look into this today. This is an issue that I have been thinking about. It is possible to assert a statement that allows a value not in the enumeration. If a reasoner is run, it will flag a logical inconsistency if the value is not in the enumeration. Applications running description logics reasoners can check for logical consistency. However, a HUMAN authoring an assertion with a value not in the enumeration will not be warned.

Reworking how we have defined open vocabularies is one of the things I have on my list that we need to do once we get things cleaned up and have a chance.
FireEye has an approach that has proven successful that I think we should leverage.
I will enter a ticket for it when I have a chance.

The range on hasMethod is not currently set to HashNameEnum.  Until the refactor that Sean mentioned is done, the range on hasMethod should be changed the HashNameEnum in my opinion.

Addressed in PR #109

Resolved in PR #109


Get rid of the Firefox hack once onAuthRequired is supported

Once the support for onAuthRequired lands in Firefox (see https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/webRequest/onAuthRequired#Browser_compatibility ), we can get rid of the nasty hack currently in place as a workaround.
https://github.com/krtek4/MultiPass/commit/7579bd368528f1c62eef33cb66e6b310b6cc0392#diff-4147e8e9f371dbb63e98e62403a732ba

Note that onAuthRequired is supported from Firefox 54+, but they do async blocking in a weird way so you'll still need a behavioral workaround. Also, some people still have to use Firefox 47.x or earlier for automated browser testing because of missing or broken features in the W3C WebDriver API, so there may be some value in keeping the serveCredentialsAsHeader workaround for now.

Thanks for the heads up.
As we are doing feature detection, newer firefox version are already using onAuthRequired. The point about people having to use older version is valid tho, so I will wait a bit before removing the hack.


Network Load Balancer dual-stack support for AWS

Request:
We have received a request to enable dual-stack support on the AWS NLB.
The requirements are to enable the IPv6 support on NLB side only, not involving changes for internal LBs nor the cluster itself. Dual-stack NLB handles the network address translation to IPv4 out of the box.
Investigation/Initial Implementation details:
To satisfy the requirements, the setup would have to involve following steps:

Adding IPv6 CIDR to VPC which will have to be different per cluster due to the peering.
Creating IPv6 Subnet for each availability zone
Adding the route tables for the VPCs
Deploying the NLB to IPv6 subnet for the IPv6 NLB support.

This does not involve only adding and exposing the annotation on the aws-load-balancer-controller-app. The implementation will also have to consist of creating an operator and logic handling the points above. The assignments have to happen automatically per MC and WCs.
Another points to consider is that the implementation will differ between AWS Vintage and CAPA, which will also affect migration.

In Vintage we will have to implement the logic within aws-operator (and have a WC release)
Plain CAPA does not support IPv6 just yet: https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/2420. To have any IPv6 features full upstream implementation has to be provided, otherwise it will be rejected.
Migration from Vintage to CAPA with IPv6 setup (if implemented) will be very problematic as is still unclear due to no implementation on CAPA.
Alternatively Managed EKS CAPA implementation supports IPv6, however it has several limitations: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/82b93149354660c0e54988e11a87c3287d92cc29/docs/book/src/topics/eks/ipv6-enabled-cluster.md. It would involve running Cilium ENI for ipv6 (currently we are only having Cilium ENI mode for IPv4, the IPv6 details have never been reviewed nor tested) or you can't define custom POD CIDRs on EKS with IPv6. Also important note is that The use of a Nitro enabled instance is required.

All and all this topic is an uncharted territory, both in CAPA and Vintage. It has never been tested, implementation upstream might take a very long time specially for plain CAPA. We also have to take into consideration the efforts for the actual migration from Vintage to CAPA for existing clusters if implemented. The 'combined' efforts can't be easily estimated and we will have to discuss within Product which direction we want to take with all providers in general.
### Tasks
- [ ] https://github.com/giantswarm/giantswarm/issues/29159

Based on the internal spike, the dual stack support for the NLB can be achieved initially with set of terraform scripts that can be applied on CAPA clusters.


High Vulnerabilities on argoexec docker image.

@alexec
CLAIR scan on Image: argoproj/argoexec:v3.1.3
We are using Clair tool for image scanning.
Alert: 3 High Vulnerabilities Found.
Error: Voting Gate failed  due to a Vendor rated High CVE-2021-3520 which is Fixed By lz4 1.8.3-1+deb10u1
Alert: 15 Low Vulnerabilities Found.
Alert: 15 Medium Vulnerabilities Found.
Error: Voting Gate failed  due to a Vendor rated Medium CVE-2021-20305 which is Fixed By nettle 3.4.1-1+deb10u1
Error: Voting Gate failed  due to a Vendor rated Medium CVE-2021-33560 which is Fixed By libgcrypt20 1.8.4-5+deb10u1
Info: Some Unknown/Negligible vulnerabilities found, please check Clair report for detailed information.
Info: Some Unknown/Negligible vulnerabilities found, please check Clair report for detailed information.
[Pipeline] }

I don't see us fixing v3.1.3 because in v3.2 we use alpine which has fewer issues.


Surfacing errors in LangChain4j tools in dev mode in the dev UI?

If an @Tool throws an exception during execution, the stack trace turns up in the quarkus console, but it can be masked by request and response logging. In my experience, it seems like the response logging seems to mostly to hit the log second, and especially if there's a few tools defined, it can be pretty verbose. So to even notice that there was a tool problem, a lot of scrolling is needed.
Here's an example, where the details don't matter, but you can see on the right side how far back I had to scroll to get to the stack trace:

I wonder if there's some value in surfacing the exception to the browser window? The model I'm thinking of is the normal dev mode exception handling, which is helpful to developers:

We couldn't use that exact behaviour in this case, because the server doesn't return a 500, it goes down a success path and returns 200. My first thought was that we'd detect the error case and render a split screen with the string response in one half and the stack trace in the other.
That doesn't really work, I don't think, because it assumes the client is a browser. If the client is an REST client that was trying to consume API output, giving it html would be a disaster. But maybe there's something that can be done. We could set the favicon, but browsers tend to cache that. We could set headers, but I don't know what header we could choose that a browser would do something interesting with.
At the very least, I think it would be safe to surface the errors in the main Dev UI? Perhaps something like this, where that row only shows if a bad thing happened during a tool invocation?

Very interesting usability issue indeed!
I am not sure what can be done about honestly... @jmartisk @phillip-kruger any ideas?

You can stream a dedicated log in the footer for tool errors. Then you can clean up the log in there as you wish, maybe make the stack collapsible

Ah, my comment crossed with @phillip-kruger's! I was going to suggest that there's probably stuff that can be done in the in-Dev-UI log window to separate out the request/response logging (which can be super-verbose) from the rest, maybe by having two tabs.
Ideally, that would be part of the solutions along with something higher up the page.

You can stream a dedicated log in the footer for tool errors. Then you can clean up the log in there as you wish, maybe make the stack collapsible

+1 this would be cool

I'll have a shot at implementing the dedicated log if you don't mind

Ah, the footer log feature is from Quarkus 3.16, so we can't use it yet (we are based on 3.15), right @phillip-kruger?

Yes, but you can still do it in 3.15, it's just more work


Feature Importance in Logistic Regression

It can be seen from the image that features importance calculated by VerticaPy is ABS(Coefficient * (max - min)) but this implementation is not supported for columns which are of different scales i.e Column A have min=-200 max=100 with coef=0.2 and Column B have min=1 and max=8 with coef=0.9.
Coef
Column A 0.2
Column B 0.9
Importance (VerticaPy)
Column A 60
Column B 6.3
It can be seen that both columns have different coefficients and very different ranges of data but when importance is calculated then column with high range of values dominate over coefficients.
Can you please justify the approach used by VerticaPy to calculate the feature importance.

Its written just above: "Computes the model features importance by normalizing the Logit coefficients".
Example: Let's say you computed your Logit. f(x1 ... xn) = f(a0 + a1 * x1 + a2 * x2 ... + an * xn).
So f(x1 ... xn) = f(a0 + (a1 * (max(x1) - min(x1))) * (x1 / (max(x1) - min(x1))) + (a2 * (max(x2) - min(x2))) * (x2 / (max(x2) - min(x2))) + ...)
By setting Xi = (xi / (max(xi) - min(xi))) and Ai = (ai * (max(xi) - min(xi))), we now have:
f(x1 ... xn) = F(X1 ... Xn) but now the Xi live in [0, 1]. The higher is their coefficient the more they can influence the decision. Remember that there is no perfect "features_importance" value but this one is fair enough. p-value can also be used but they exist just to reject some coefficient and not to tell that one is more important than another.
Hope it helps!

Thanks for such an explanation but my point is still not cleared i.e when the scales and ranges of columns are ranges then how can we decide which column is more important than another. I know that if scales are the same then only the coefficient value indicates importance but if you go through my example provided above you can see that the coefficient has nothing to do with importance if the value ranges are different among columns.

Hi @SMoazzamR,
The coefficient is of course took into account! The new importance is a combination between the coefficient and the variable range.
Ai = (ai * (max(xi) - min(xi)))
If the variable scale in 0,1 then the importance is the coefficient itself, otherwise we have to multiply it by the range. Imagine the following use-case:
Column A have min=-20 max=10 with coef=0.2 and Column B have min=1 and max=8 with coef=0.9.
Then Imp(A) = 30 * 0.2 = 6 and Imp(B) = 0.9 * 9 = 8.1 so B is still more important. This score is ofc at the end normalized to get a sum equals to 100.
The importance in this case is how the variable can influence the prediction, how it can unbalanced the result of the Logit(X) function.
Hope it answers to your question,
Best,
Badr


twilio couldn't keep the volume to  the minimum during the call

when the phone during the call,the sound could not be turn off in the android demo and twilio apk .
what is the reason of this phenomenon？
if i want to twilio can turn off  , how should i do?

The chat application does not use any voice/audio features, are you sure you're writing to the right repo?

Closing this as there was no response.


FEEL expression fails to parse when referencing an itemComponent with a space in the name

Describe the bug
DMN models that contain itemDefinitions with itemComponents that include spaces in their name, throw a "failed to parse expression" error. An example from the included VacationDayCalculator.dmn model is: FEEL expression: failed to parse expression 'Years of Service(employee.start Date, calculation date)': Expected (!"(" | "." | parameters | StringIn("<=", ">=", "<", ">", "!=", "=") | "between" | "in" | "and" | "or" | end-of-input):1:19, found "(employee."
In this example, employee is of type Employee which is an itemDefinition containing an itemComponent "start Date". Note that 'calculation date' also contains a space, but it is a variable with a typeRef="date". We are not experiencing the same parse error with 'calculation date'.
To Reproduce
Steps to reproduce the behavior:

Create a DMN model with an ItemDefinition that has an itemComponent, whose name contains a space.
Create a valid FEEL expression that references the itemComponent that contains the space.

Expected behavior
The FEEL expression should successfully parse.
Environment

DMN engine version: 1.7.1
Integration:

Embedded as library in custom application

Note that when we create the DmnEngine object using the DmnEngine.Builder we are setting the following builder properties:

escapeNamesWithSpaces(true)
escapeNamesWithDashes(true)

Here is a sample DMN model that demonstrates the problem.
VacationDayCalculator.dmn.zip

@twilger thank you for reporting :+1:
Please note that the support for whitespace is more of an experimental feature. I recommend replacing whitespace by camelCase or snake_case.

Done by #198 :rocket:


mesa: reduce rebuild impact [plan]

Currently the rebuild impact is only due to libGL stubs pulling headers from the mesa build (I think), but upgrading the headers shouldn't be needed on every driver minor bump, as the API should be portable even to other libGL implementations, etc.
Plan: use headers from a fixed version, so that mesa(_drivers) can be changed much easier.

It might actually reduce the rebuild impact of a few other packages, too, as glvnd has much smaller closure than mesa.

I think we could avoid this sort of mass rebuild by removing the self references in mesa_noglu.stubs.  It wouldn't help with version upgrades (unless we pin it, which I'm not sure is a good idea).  Maybe we should source the headers from khronos repositories?

Well, yes, I meant whatever way to get suitable headers.  I have a feeling the khronos headers had been considered by us once, but I don't remember what's happened to that idea.

Done in #118479, currently in staging.