Assign multiple permission sets with force:user:permset:assign

Is your feature request related to a problem? Please describe.
Whenever we are assigning permission sets we typically want to do more than one.
Can we extend the -n | --permsetname parameter to handle a list of perm set names?
What are you trying to do
Assign multiple perm sets with a single command.
Describe the solution you'd like
sfdx force:user:permset:assign -u myorg -n "permset1, permset2"
Describe alternatives you've considered
Calling multiple times but this introduces a small delay between calls and is just not as nice or convenient as the proposal.

You could create a sfdx plugin to do it using the standard command.
I created one that installs multiple packages.
sfdx hpe:package:install -p 04t1V000000olrcQAA,04t1V000000TYMqQAO,04t1V000000XUr1QAG,04t1P00000027PlQAI,04t1V000000XUVUQA4,04t1V000000XUeWQAW,04t1V000000olt4QAA -u ${this.flags.targetusername} --json

If you don't want to make it a plugin, you can just write a node script that will call the sfdx command for you multiple times given a list of permission sets. If you need help send me an e-mail and we can talk. My contact<EMAIL_ADDRESS>

closed because this has been merged and is available to use 👍🏻


can we use s3 path here instead of hdfs?

from petastorm.spark import SparkDatasetConverter, make_spark_converter
specify a cache dir first.
the dir is used to save materialized spark dataframe files
spark.conf.set(SparkDatasetConverter.PARENT_CACHE_DIR_URL_CONF, 'hdfs:/...')
### can we use s3 path here instead of hdfs?
df_train, df_test = ... # df_train and df_test are spark dataframes
model = Net()
create a converter_train from df_train
it will materialize df_train to cache dir. (the same for df_test)
converter_train = make_spark_converter(df_train)
converter_test = make_spark_converter(df_test)
make a pytorch dataloader from converter_train
with converter_train.make_torch_dataloader() as dataloader_train:
# the dataloader_train is torch.utils.data.DataLoader object
# we can train model using the dataloader_train
train(model, dataloader_train, ...)
# when exiting the context, the reader of the dataset will be closed
the same for converter_test
with converter_test.make_torch_dataloader() as dataloader_test:
test(model, dataloader_test, ...)
delete the cached files of the dataframes.
converter_train.delete()
converter_test.delete()

Did you try doing that? What did you observe?

yes. i tried following codes:
from petastorm.spark import SparkDatasetConverter, make_spark_converter
specify a cache dir first.
the dir is used to save materialized spark dataframe files
spark.conf.set(SparkDatasetConverter.PARENT_CACHE_DIR_URL_CONF, 's3a://****/*****/')
df_train, df_test = train_df, test_df # df_train and df_test are spark dataframes
model = Net()
create a converter_train from df_train
it will materialize df_train to cache dir. (the same for df_test)
converter_train = make_spark_converter(df_train)
converter_test = make_spark_converter(df_test)
make a pytorch dataloader from converter_train
with converter_train.make_torch_dataloader() as dataloader_train:
# the dataloader_train is torch.utils.data.DataLoader object
# we can train model using the dataloader_train
train(model, dataloader_train, ...)
# when exiting the context, the reader of the dataset will be closed
the same for converter_test
with converter_test.make_torch_dataloader() as dataloader_test:
test(model, dataloader_test, ...)
delete the cached files of the dataframes.
converter_train.delete()
converter_test.delete()
and got following error:

I see that you are using s3a:// protocol. We currently do not support it. Can you use s3:// in your case?

Hi @selitvin ,
Thanks for the response. In my org we use s3a protocol as this more secure. I can try using s3 protocol. Is there a plan to incorporate s3a protocol?

error while using s3 buckets:

I added s3n and s3a to the list of supported protocols and checked that I could both write and read from  my s3 bucket.
Would you like to try it and see if it helps?
pip3 install git+https://github.com/selitvin/petastorm.git@support-s3-s3a-s3n

sure Thanks!

@p9anand those distinctions are only meaningful on Hadoop-based systems (see Technically what is the difference between s3n, s3a, and s3?). Because petastorm delegates to s3fs, which in turn uses boto3 (indirectly), everything will be treated with an object-native interface, regardless of the protocol. Since it makes no difference on this side, could you just substitute the protocols to something already accepted? That would be closer to a conceptually clear solution, because there isn't a meaningful way for petastorm to "support" the other protocols, in the way you mean (i.e.: other than to ignore the distinction and treat them all uniformly).
Saying that, your understanding of what s3a does in Hadoop already maps to how s3fs (and, by extension, petastorm) treats the s3 protocol; i.e.: an object-native interface using AWS's own SDK (boto3 for Python, in this case), and with no arbitrary limit on the file size, beyond S3's own limits. Moreover, you needn't worry about specifying the s3 protocol not being interoperable (because it's a Block FileSystem), because this Hadoop-specific view of the world is pretty dated. In the non-Hadoop world, s3 simply means the same thing as s3a (except on EMR, where it means emrfs, but that's out-of-scope).

working perfectly...!! Thanks.


Lightning Node Connect fails

Just installed LND LIT from the Raspiblitz menu.
Trying to pair via https://terminal.lightning.engineering/#/connect/pair gives me an error:
Failed to connect
Connected. rpc error: code = Unknown desc = lnd macaroon validation failed: rpc error: code = Unknown desc = permission denied. Try reloading the page or obtaining a new pairing phrase.
Tried reloading, rebooting, generating new phrase both from webinterface and lncli. Any suggestions?

You need to re-generate your lnd macaroons. You can do that by removing the admin.macaroon, readonly.macaroon and invoice.macaroon (singular, not invoices.macaroon) in the lnd data directory (I think somewhere in /mnt/hdd/lnd/data/chain/bitcion/mainnet/on RaspiBlitz). Then restartlnd` and Lightning Terminal.

i'm using tor btw, maybe that's the issue?

The re-try was with a totally new pairing phrase, correct? They expire after 10 minutes is why I ask.

i hit the 'copy pairing phrase' button, not sure if that generated a new phrase.
now i get the rpc error again after generating a new phrase.
nvm, i'll keep playing around. just wanted to try terminal, nothing important. thx!

Happy to help you debug if you want to keep trying! If there's an issue, we definitely want to get to the bottom of it. Could you try running debug logs in your browser console while connecting? That could give us more information about the problem.

like this?
2023-03-04 14:11:54.283 [DBG] WASM: WASM client ready for connecting index.js:2:928
2023-03-04 14:11:54.871 [DBG] GRPC: [core] parsed scheme: "" index.js:2:928
2023-03-04 14:11:54.877 [DBG] GRPC: [core] scheme "" not registered, fallback to default scheme index.js:2:928
2023-03-04 14:11:54.877 [DBG] GRPC: [core] ccResolverWrapper: sending update to cc: {[{mailbox.terminal.lightning.today:443   0 }]  } index.js:2:928
2023-03-04 14:11:54.878 [DBG] GRPC: [core] ClientConn switching balancer to "pick_first" index.js:2:928
2023-03-04 14:11:54.878 [DBG] GRPC: [core] Channel switches to new LB policy "pick_first" index.js:2:928
2023-03-04 14:11:54.879 [DBG] GRPC: [core] Subchannel Connectivity change to CONNECTING index.js:2:928
2023-03-04 14:11:54.879 [DBG] GRPC: [core] Subchannel picks a new address "mailbox.terminal.lightning.today:443" to connect index.js:2:928
2023-03-04 14:11:54.879 [DBG] MBOX: Client: Dialing... index.js:2:928
2023-03-04 14:11:54.879 [DBG] MBOX: New client conn, read_stream=2fa125183e957489692ab288d3097512b5626e08003657c1e07ef49cfc8eb85c6d3ccd7d05fe920f1ddd227faaf66cd9f45f77c2fe3056cfc230cbca9af830e0, write_stream=2fa125183e957489692ab288d3097512b5626e08003657c1e07ef49cfc8eb85c6d3ccd7d05fe920f1ddd227faaf66cd9f45f77c2fe3056cfc230cbca9af830e1 index.js:2:928
2023-03-04 14:11:54.880 [DBG] MBOX: Client: Attempting to create send socket/stream index.js:2:928
2023-03-04 14:11:54.879 [DBG] GRPC: [core] pickfirstBalancer: UpdateSubConnState: 0x1feeeb0, {CONNECTING } index.js:2:928
2023-03-04 14:11:54.882 [DBG] GRPC: [core] Channel Connectivity change to CONNECTING index.js:2:928
2023-03-04 14:11:55.761 [DBG] MBOX: Client: Connected to send socket/stream index.js:2:928
2023-03-04 14:11:56.349 [DBG] MBOX: Client: receive mailbox initialized index.js:2:928
2023-03-04 14:11:56.541 [DBG] MBOX: Starting client handshake index.js:2:928
2023-03-04 14:11:57.920 [DBG] MBOX: Kicking off client handshake with client_key=0338b0e3c08851f8bea23e107233bde0248277a670b72c9b798ccc6bb1689f54dd index.js:2:928
2023-03-04 14:11:58.319 [DBG] MBOX: Completed client handshake with with server_key=023d4dea88223d399125d2cc14cacaf9507aa788f66b429d0f0255ca434a0beea3 index.js:2:928
2023-03-04 14:11:58.320 [TRC] MBOX: Client handshake completed index.js:2:928
2023-03-04 14:11:58.743 [DBG] GRPC: [core] Subchannel Connectivity change to READY index.js:2:928
2023-03-04 14:11:58.744 [DBG] GRPC: [core] pickfirstBalancer: UpdateSubConnState: 0x1feeeb0, {READY } index.js:2:928
2023-03-04 14:11:58.745 [DBG] GRPC: [core] Channel Connectivity change to READY index.js:2:928
2023-03-04 14:11:58.746 [DBG] WASM: WASM client connected to RPC index.js:2:928
2023-03-04 14:11:58.926 [INF] WASM: Calling 'lnrpc.Lightning.GetInfo' on RPC with request {} index.js:2:928


Break on  application-code only

Hi,
Byebug is great and it seems to be a lot less buggy than debugger so thumbs up!   However, the issue I'm running into is that whenever I step in, byebug (and also debugger) would step in too deep, or into a chunk of code that's somewhere deep in the gem.  Obviously I don't want to step thru any gem code or external library but focus only on my current application's code.
My question/suggestion is that if there's a way to filter or skip over external library, or a setting to step into the next line that belongs to a script within the current application.  For example, step into a method call will skip over any Rails's internal script or any currently-used gem and stop at the next line of the file that's inside the application.  This will greatly reduce the tediousness of stepping into the app and help pin-pointing the issue.  Currently it's quite time consuming to setup the correct breakpoint, and usually it's a hit-or-miss and having to run the test suite multiple times just to figure out the correct breakpoint placement.
Something like a configuration to list the path or locations to resume the debugger when stepping in automatically would be a great start.

Changed my mind again after rereading this issue and this stackoverflow question.

:+1:  I'd like to be able to do this.

As a tip to anyone wanting to contribute here, debase just added file filtering: https://github.com/denofevil/debase/commit/722157903d50a165371fc988a96c0f96424a17b0

It would be great to have file filter where one can specific the list of files or the directories in the path where it should step through.

🏏 🏏 🏏

I think this could solve your issue: https://rubyjard.org/. It's a wrapper around byebug, with a nice Terminal UI, and plenty of features. One of the key feature is frame filtering that allow you to debug application code only, or include/exclude any gems/ruby libs you want.

I would really love this too. Rubyjard looks excellent but when not in a terminal (i.e. running a debugger within an editor), it's no longer suitable.
From what I can tell, Rubyjard handles this by wrapping the command processor and stepping through until the current file matches a set that it should stop on, or some execution time or depth expires. Is that a suitable solution here, or does it need to be implemented somewhere in the C bindings, like debaser has done?

@lazyatom Yes, it will be re-implemented in C. However, recently, I'm focusing on feature set instead. Btw, in the roadmap, I will implement DAP protocol to support debugging in VS Code, Vim, or Emacs.


build: remove VERSION file as git-semver now manages version

TBD...Need to discuss in TSC meeting.
Signed-off-by: Ernesto Ojeda<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit subject follows the Conventional Commits spec
[x] The commit message follows the EdgeX Contributor Guide
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[x] make test has completed successfully

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number:
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Are there any new imports or modules? If so, what are they used for and why?
Are there any specific instructions or things that should be known prior to reviewing?
Other information

What is the plan to make snap builds work without the VERSION file?
12:19:23 Pulling version
12:19:23 cat: VERSION: No such file or directory
12:19:24 Failed to run 'override-pull': Exit code was 1.
12:19:34 Build step 'Execute shell' marked build as failure

What is the plan to make snap builds work without the VERSION file?
12:19:23 Pulling version
12:19:23 cat: VERSION: No such file or directory
12:19:24 Failed to run 'override-pull': Exit code was 1.
12:19:34 Build step 'Execute shell' marked build as failure

Couple things...

We should be able to safely remove the edgex-go-snap-master-verify and edgex-go-snap-master-verify-arm JJB managed jobs. We have an inline Snap stage that can be added to the pipeline job (currently commented out). It's a couple of lines of code and because git-semver is used in the pipeline the VERSION file is automatically written to the workspace. In all honesty I thought we had removed the verify snap jobs.
The nightly snap job is being updated to use the VERSION file created by git-semver

@ernestojeda great thanks for specifying, one more question what is the plan for local builds of the snap? Since the builds will be local there will be no VERSION file and thus it will fail to build unless the developer creates a VERSION file.

@ernestojeda great thanks for specifying, one more question what is the plan for local builds of the snap? Since the builds will be local there will be no VERSION file and thus it will fail to build unless the developer creates a VERSION file.

I wrote a note about this in the snapcraft.yaml file here. I added the VERSION file to the .gitignore so if one cares about local snap development they could write a local VERSION file to allow the snap to build. There is a similar concept in the make version target will look for the version in the VERSION file and if it cannot find a file it returns 0.0.0. So another option might be to update snapcraft.yaml to use make version rather than cat VERSION. Not sure if that is possible.

So another option might be to update snapcraft.yaml to use make version rather than cat VERSION. Not sure if that is possible.

This would be my preference, I think that this PR should not be merged until that is done. Probably this can be something as simple as:
    override-pull: |
      cd $SNAPCRAFT_PROJECT_DIR
      if [ -f VERSION ]; then
        PROJECT_VERSION=$(cat VERSION)
      else
        PROJECT_VERSION=local-dev
      fi
      GIT_REVISION=$(git rev-parse --short HEAD)
      snapcraftctl set-version ${PROJECT_VERSION}-$(date +%Y%m%d)+${GIT_REVISION}

since the version number for a local build is not super important.

I will apply this to my PR

LGTM


Add missing SWIG mapping for int 64 and void pointer types

The CSharp Image methods GetBufferAsVoid, GetBufferAsUInt64 and
GetBufferAsInt64 return type was SWIGTYPE_p_void, etc. This
appropriate type map is not added to return these pointers as IntPtr
types.

The PR addresses issues reporting in ITK Discourse: https://discourse.itk.org/t/how-can-i-use-getbufferasint64-in-c/3623/4


CardHeader should have same typography/props controls like ListItemText

CardHeader should have same typography/props controls like ListItemText:
<ListItemText primaryTypographyProps={...} secondaryTypographyProps={...}/>

@kirill-konshin Feel free to go ahead.

@oliviertassinari,
What about disableTypography, should it be implemented in CardHeader as well?

What about disableTypography

@chenop I think that supporting disableTypography would be another great addition.

should the new props should be named

It's a good point. It would be better to use the  titleTypographyProps and subheaderTypographyProps wording.

#12166


build: pin black to 24.x.x

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


The polling thread does not seem to be used when GCM is disabled

https://github.com/vector-im/vector-android/commit/446a4b7eec25ed04cd4167936121df9ae252b7c4


This Plugin Breaks the Neovim Start Screen

When opening Neovim without arguments and without this plugin, I can see the start screen. With this plugin, I see it only for a millisecond and then it disappears. I can conclude that this plugin is causing the Neovim start screen to not show. I do not know why though.

Same here

Feel free to submit a PR. I don't use the Neovim start screen, so won't spend the time to look into this. Todo-comments doesn't do anything weird, no idea what's causing this

I looked into this and concluded that it's caused by config.colors() function being called from a deferred function (setup()), more precisely these 3 lines:
vim.cmd("hi def TodoBg" .. kw .. " guibg=" .. hex .. " guifg=" .. fg .. " gui=" .. bg_gui)
vim.cmd("hi def TodoFg" .. kw .. " guibg=NONE guifg=" .. hex .. " gui=" .. fg_gui)
vim.cmd("hi def TodoSign" .. kw .. " guibg=" .. sign_bg .. " guifg=" .. hex .. " gui=NONE")

:highlight command triggers redrawing, which causes the start screen to disappear. I managed to fix this behaviour by adding event='VimEnter' to my packer setup. It looks like this:
use {
	'folke/todo-comments.nvim',
	requires = 'nvim-lua/plenary.nvim',
	event = 'VimEnter',
	config = function()
		require('todo-comments').setup()
	end
}

Remember to run :PackerCompile if you change your configuration.

@MPWrobel's solution works for me


request for removeAppender() function

I'm submitting a feature request

Library Version:
1.1.0

Please tell us about your environment:

Operating System:
Linux (mint)

Node Version:
6.9.1

Browser:
all

Language:
TypeScript 2.0.9

Expected/desired behavior:
Would like to have a removeAppender companion to the addAppender

What is the motivation / use case for changing the behavior?

I have a use case where I have a default appender assigned, and I'd like to remove the default  and replace it with a different appender.

How would you like to identify the existing appender(s)?
Since the place your add the default appender and the place you want to swap the appender can be quite remote from each other, you may not be able to (or want to) access the existing appender(s).
Do you think removeAppender(existingAppender) would be sufficient?


check_jumps needs to be rewritten for IPTA use

Currently check_jumps doesn't know what to do with JUMPs that aren't NANOGrav-style -fe jumps. We should fix that.

requires someone with knowledge of how the jumps work

This could still be a useful enhancement, but it seems like it might be more trouble than it's worth in the IPTA context. For DR3, the approach so far has been to avoid the check_jumps() function altogether, which puts the burden of checking that jumps make sense on the person doing the combination. This is hard to avoid because different PTAs' systems of jumps are so different, and no one seems to have the complete picture.


Expose GET WorkflowTask and split API files

closes #760
closes #761

This raise is not tested but it's impossible to trigger: workflow_task_update is already a WorkflowTaskUpdate at that point and only has args and meta.
https://github.com/fractal-analytics-platform/fractal-server/blob/4ee54fa33b6272754a1b5c0c3fd672d5a19443f1/fractal_server/app/api/v1/workflowtask.py#L132


Use dynamic loading for charts

Is your feature request related to a problem? Please describe.
If there is some form of delay in render of a component, it is better to load a spinner instead and show the component only after it has been loaded. Code splitting is done when codebases get really large and help us not load entire components at a time.
Describe the solution you'd like
We can use dynamic imports to load components in our application.
Resources
Code Splitting.
Usage in tsx.

@aquibbaig, this is good from UX point. But I was thinking since we already support real-time streaming of data (and hence sockets), we can make graphs being refreshed in regular intervals which happens from a push in service (Note: only from service). This derives the true sense of dynamic graphs.

I am Interested with the issue.

@vipuldcoder sure, you can go ahead with this.

@vipuldcoder I think this issue needs to wait for now, because we are on our way to make a new version of our dashboard in #167, you might want to contribute to that instead. Thanks for your interest in bench-routes.

Unrelated now.


Incorrect matching of +/- in rule labels

should recognize empty-w as a variable.function? as per scope naming page

I misunderstood the usage; it should be entity.name.function for the definition and variable.function when invoked

fixed per 44765ba


downloading files in headless mode with selenium is broken

I had some tests that downloaded files, and they broke suddenly on the 29th of August. The file is not downloaded anymore in headless mode, it is working in headed mode tho.
I tried with downloading the chrome installer from google.com/chrome with a ChatGPT generated generic script from scratch and it's not working there either.
RFW version: 7.0.1
chrome version: 1128.0.6613.138
chromedriver version: 128.0.6613.137
OS: win server 2009 1809

No idea what's causing this, but the problem certainly isn't in Robot Framework itself. You don't tell what web testing library you use, but unless you have noticed updated it, it's unlikely the problem is in it either. Probably there's some change to the browser and the underlying web testing tool hasn't yet been updated. I recommend you to search have others had this issue and if that doesn't provide any info, to ask about it on our Slack or Forum.
This tracker is only for Robot Framework itself and this issue is rhus


[DPTOOLS-93] Remove Canary whitelist

We originally had this check so that the Canary scheduler running 1.8
wouldn't delete TI's that the 1.7 scheduler in Prod marked as QUEUED.
Now that 1.8 is the only scheduler, this logic is no longer needed.
Still trying to wrap my head around the implications, but I think this
could be why some of the metric_dryrun tasks last night got stuck in
state QUEUED after the etl deployment. Let's get rid of it and see if
that behavior goes away with the next deployment.
cc @lyft/data-platform

+1


[Bug] Python 3 output not working

Summary
I can not run in Python 3.
Expected behavior
For example, I have file test.py. Content of file:
print("Sasha Goddess!")

If I run file use command prompt:
E:\Киролайна>python test.py
Sasha Goddess!

If in test.py I press Ctrl+Shift+P → Terminality: Browse Commands... → Run test.py as Python 2.7 document → new tab was opened for me, I see in new tab:
Sasha Goddess!

Actual behavior
I see mojibake if I run any Python script.
"python3" �� ���� ����७��� ��� ���譥�
��������, �ᯮ��塞�� �ணࠬ��� ��� ������ 䠩���.

Steps to reproduce
The problem is reproduced for me in a version of Sublime Text without plugins and user settings.
If in test.py I press Ctrl+Shift+P → Terminality: Browse Commands... → Run test.py as Python 3 document → new tab was opened for me, I see mojibake in new tab.
Environment
Operating system and version:
Windows 32-bit 10.0.14393
Sublime Text:
Build 3126
Python version in operating system:
3.5.2
Thanks.

Python 3 command will use python3 executable to run your file. If you already set your executable to be python you can simply use Python 2 command to run it.
In another word,

Python 3 command use python3 executable to run
Python 2 command use python executable to run


⚠ Jenkins Plugins Artifactory has degraded performance

In aa5c1a5, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1233 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 7949ff5 after 27 minutes.


now it scrolls down to events section

Closes
Closes #1571

Description
The id given was not updated after the section being updated

Screenshots
Now it scroll down to the section

Note to reviewers

Checklist:

[x] I have linked the PR to the correct issue.
[x] I have read the Contribution Guidelines
[x] I have built and tested the changes, and they do not break or show any errors.

@Divesh2003 can you please assign me #1570


Document current server-client implementation and scope migration to FastAPI

As a stop-gap to having a fully typed server #605, we would like to evaluate, document the current server implementation, and provide details of how hard it would be to convert the endpoints to fastAPI endpoints.
We'll use this documentation to design and build our professional server-client implementation as per #605.

Assigning to @rec for visibility.

The final two points ('Investigate ...' and 'Sync ...') are currently being discussed in a GitHub Discussion here.


Improve support for 'action' & 'component'

It seems like Sharpbrake v2 had better support for context/action & context/component for ASP.NET apps.
@aholovko could we make an audit and improve support of these fields. They are used in our dashboard to show the WHERE field.

Updated in the version 3.0.3 (https://github.com/airbrake/sharpbrake/pull/52).


Whisk: Move non-preset values to config

Preset values should be those that affect types or other build time data structures.
Both WHISK_EPOCHS_PER_SHUFFLING_PHASE and WHISK_PROPOSER_SELECTION_GAP do not affect any data structure and are useful to tweak in tests to speed up their runtime. Setting WHISK_PROPOSER_SELECTION_GAP to a value >= WHISK_EPOCHS_PER_SHUFFLING_PHASE - 1 disables tracker shuffling

Thanks!

@dapplion
Also need to update the presets/<minimal,mainnet>/whisk.yaml files and config files


Dependency Graph - Clean up

Clean up Dependency graph
Verify the name matches with the catalog modules

Seems like this module looks which has only 2 dependency GItops and namespaces
@triceam - FYI

Completed the db2 clean up

As part of clean up build, it requires to update the notification module which throws error


If args is undefined for Executable then options are ignored

It seems that typings for child_process.spawn is bogus it should be:
export function spawn(command: string, options?: SpawnOptions): ChildProcess;
export function spawn(command: string, args: string[], options?: SpawnOptions): ChildProcess;

at least when I debug an implementation it tests the second argument whether it is an array or an object and treats them differently.

Publish 3.3.0-alpha.6


events: past events cannot be edited - therefore the save/publish buttons shouldnt be presented at the bottom of the page

In which case, if we can make the fields on past events readonly then that makes sense too - will add to backlog.


Redirect docs to current version

PROBLEM:
See #350 for context. There's a GitHub issue open for this on the
facebook docusaurus repo:
https://github.com/facebook/docusaurus/issues/9049
SOLUTION:
Use the redirect workaround for the time being.
OUTCOME:
https://holos.run/docs will link to the most recent version of our docs
site.

Just so I understand this correctly, the _redirect file is service-side redirect config supported by CloudFlare, and we will have to update the redirect any time a new API version is pushed (e.g. v1alpha6)?

the _redirect file is service-side redirect config supported by CloudFlare, and we will have to update the redirect any time a new API version is pushed (e.g. v1alpha6)?

@natemccurdy Yes that's correct.
curl https://gl-350-docs-redirect.holos.pages.dev/docs

Redirecting to /docs/v1alpha5

FYI, @glarizza @natemccurdy Cloudflare tacks a / on the end of all the URL's, so I changed the redirects to match and handle both /docs and /docs/


Create test2

Codecov Report

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

@@          Coverage Diff          @@
##           master    #26   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          78     78
  Lines        1625   1625
  Branches      289    289
=====================================
  Hits         1625   1625

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 30ae323...6063834. Read the comment docs.

ccc


[6.0] Re-add app property to Manager

Otherwise this would be a too big change for packages. I've added a deprecation note. We'll keep this around for a few major versions and then remove it in a future version.

@crynobone what do you think of this solution?

Better than before.


Removing Default Spring

In the atEnter, AtLeave, and atActive parameters, the spring method is applied to the animations by default.  In react-motion, however, if you don't add the spring method to your interpolated value, the "unspringed" value just gets passed in without being interpolated over the duration of the spring. Would a better alternative be to either

remove the default spring and make a dev apply spring methods for each interpolated value on atEnter, atLeave, and atActive

OR

have a mapStyles for atEnter, atLeave, and atActive.

I see this as beneficial by giving more granular control over what values get "springed" and what doesn't.  Just a thought.

@jwdinker feel free to PR. i would prefer the first option you listed, whereby we just remove the ensureSpring usage.