[Bug]:  causal=True in speechbrain.lobes.models.conv_tasnet.MaskNet results in an error

Description
Hi everyone,
I am running into a seemingly simple bug when trying to run the causal version of speechbrain.lobes.models.conv_tasnet.MaskNet. Simply setting the 'causal' flag to True triggers this error: TypeError: bad operand type for unary -: 'str'.
Expected behaviour
I expect that simply changing the flag allows switching between the causal and acausal implementations.
To Reproduce
Here is a minimal example:
from speechbrain.lobes.models.conv_tasnet import MaskNet

hprams = {'N': 64, 'B': 32, 'H': 64, 'P': 3, 'X': 6, 'R': 3, 'C': 1}

acausal_net = MaskNet(**hparams, causal=False)
# -> defines network

causal_net = MaskNet(**hparams, causal=True)

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/lobes/models/conv_tasnet.py", line 238, in __init__
    self.temporal_conv_net = TemporalBlocksSequential(
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/lobes/models/conv_tasnet.py", line 160, in __init__
    self.append(
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/nnet/containers.py", line 112, in append
    layer = layer(*args, input_shape=input_shape, **kwargs)
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/lobes/models/conv_tasnet.py", line 346, in __init__
    self.layers.append(
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/nnet/containers.py", line 112, in append
    layer = layer(*args, input_shape=input_shape, **kwargs)
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/lobes/models/conv_tasnet.py", line 443, in __init__
    self.append(
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/nnet/containers.py", line 111, in append
    input_shape = self.get_output_shape()
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/nnet/containers.py", line 132, in get_output_shape
    dummy_output = self(dummy_input)
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/nnet/containers.py", line 144, in forward
    x = layer(x)
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/ALABSAD/aloradad/anaconda3/envs/se/lib/python3.8/site-packages/speechbrain/lobes/models/conv_tasnet.py", line 487, in forward
    return x[:, : -self.chomp_size, :].contiguous()
TypeError: bad operand type for unary -: 'str'

The error simply says that it can not negate a string. This string is self.chomp_size, which turns out have the value 'same' when causal=True
Versions
I am using speechbrain version 0.5.12.

Hello @ahmad-aloradi,
Thanks for spotting the bug.
@cemildemir19 could you please have a look? I was able to reproduce the issue and found that https://github.com/speechbrain/speechbrain/blob/develop/speechbrain/lobes/models/conv_tasnet.py#L437 was the problem. We are giving in input padding which is a string while we were expecting a chomp_size int... thanks :)

Sorry for my terribly late reply. The error was caused by the fact that way padding is handled changed with pytorch versions. I aim to provide a fix in this PR: https://github.com/speechbrain/speechbrain/pull/1851. I am closing this issue for now. If there are other problems feel free to re-open.

Thank you! @ycemsubakan @Adel-Moumen 🙏


Feature/#26 tournaments tab

The return of the tournaments tab. Featuring our api-challonge-proxy.

I have just retestet it and wondered why it is broken. Adding the @Async annotation breaks it without any exception in the log. Any ideas? @axel1200  @micheljung

@Brutus5000 Any more details about the "breaks it" part?

It was a white page without exception, but thanks to axel I was able to solve it.


Option to start with OS

Add an option to the tray menu to start clipshift with the OS.

[x] Windows startup start menu shortcut
[x] MacOS
[ ] Linux (needs research, maybe systemd)

Going to move Linux to its own ticket


A passing Cucumber dry run with --strict option returns a bash exit code of 1

Hello,
As of cucumber 2.0.0.rc.4, a passed cucumber dry run with the --strict option enabled will return a bash exit code of 1. Previously, (i.e. in cucumber version 1.3.9), this would return 0.
For example:
cucumber -r features --dry --strict features/faildry.feature
Feature: faildry.feature
  Scenario: faildry.feature # features/faildry.feature:2
    Given I have "3" cukes  # features/step_definitions/cukes.rb:1
1 scenario (1 skipped)
1 step (1 skipped)
0m0.001s

echo $?
1

In cucumber 1.3.9, this would return 0. Also, running without the --strict option in 2.0.0.rc.4 will return 0.
My setup is:
Fedora 21, 3.18.3-201.fc21.x86_64
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]
cucumber 2.0.0.rc.4
Thanks!

@brasmusson looks great, thanks so much!


When should we use tests ?

It is my understanding that we currently run our tests twice, at precommit with the ci option, and at prepush, which I added some time ago.
(I might be wrong though).
I find it more convenient to test at prepush. Maybe we should only keep this one ?

With jest-styled-component, all tests are still run at lint-staged, but at least many less tests fail because of changed classnames in snapshots.

Great, I didn't know that module thanks.


Saving

Add option to save whole feature engineering dataset with all labels as one csv.

Resolved in #31


Get Signing Working Using GitHub Actions, openssl, and developer.apple.com

Following the instructions in the README I get:
No profiles for '***' were found: Xcode couldn't find any iOS App Development provisioning profiles matching '***'

Change the instructions or Actions so that signing works.

There is a $100 bounty on this: https://gitpay.me/#/task/667/get-signing-working-using-git-hub-actions-openssl-and-developer-apple-com


[jnigen] Generate ResourceIdentifiers

To address https://github.com/dart-lang/native/issues/681, we should to generate ResourceIdentifiers on all JNIgen generated methods.
class PDDocument extends jni.JObject {

  @ResourceIdentifier('jnigen')
  jni.JObject getDocumentCatalog();

  @ResourceIdentifier('jnigen')
  static PDDocument load(
    jni.JObject file,
  );

}

The consuming of the annotations can be tested with pkg/vm/tool/gen_kernel. pkg/vm/tool/gen_kernel --help shows the API. --resources-file=... --aot --tfa are the arguments to use.
Some questions to answer:

What do we need from the resources.json format

Currently the class surrounding the method is missing (workaround: ResourceIdentifier('PDDocument') to get the class this way)
Instance methods are not supported. What would we need for instance methods? The identical metadata in the annotation on every override? Some serialization of the class hierarchy?

Do we possibly need to change the structure of the generated JNI API?

Some assumptions:

We cannot generate proguard rules for any dynamic invocations.
We cannot generate proguard rules for uses of package:jni invokeMethod and friends.

@HosseinYousefi This would be very useful to know in the design of hook/link.dart and the resources.json format. Can you give the existing implementation a spin and try to answer the above questions? (And maybe ask some more good questions! 😄)
Related issues:

https://github.com/dart-lang/native/issues/1085
https://github.com/dart-lang/native/issues/1099

@liamappelbe mentioned that we'd need to deal with renames and super classes, so probably we should generate something along the lines of:
@ResourceIdentifier({
  'jnigen': true,
  'java_class' : 'SomeClass',
  'java_method' : 'someMethod',
  'java_method_static' : true,
  'java_super_class' : 'SomeOtherClass',
})

Instance methods are not supported.

We have static const method IDs for all methods, and static const class object as well. So we could generate the resource identifiers for those instead.

Do we possibly need to change the structure of the generated JNI API?

I don't think so, I will try it!

Some assumptions:

We cannot generate proguard rules for any dynamic invocations.

Of course, this seems to be fine. If you want any level of dynamicism, you'll have to deal with keeping the classes and methods yourself.

We cannot generate proguard rules for uses of package:jni invokeMethod and friends.

We could consider supporting this use case iff all the names and signatures are known at compile time. And maybe issue a helpful warning when the names and signatures are not const.
final jclass = JClass.forName('Ljava/nio/ByteBuffer;'); // using a string literal, so we could keep it
const name = 'allocate';
final allocate = jclass.staticMethodId(name, '(I)Ljava/nio/ByteBuffer;'); // ditto

Will we be able to "link" the method name with the class name though? Or does the JClass need to be const as well?
I can construct another use case, imagine we have a bunch of icon fonts in a Flutter application and we want to access a certain one:
final font = Font('assets/fonts/1.ttf');
final icon = font.icon(5);
// We would ideally like to keep the icon number 5 from 1.ttf and tree-shake everything else that's unused.

we'd need to deal with renames and super classes

We only need the class' binary name, member name, its signature, and its modifiers to keep the class or member in proguard: https://www.guardsquare.com/manual/configuration/usage

We could consider supporting this use case iff all the names and signatures are known at compile time.

For example using @mustBeConst.
cc/ @mosuem


Will pony port another platform in the future?

Hi.
Maybe android and ios?
And have a question, Can I call function when I know function pointer?
like c example:
  /* int sum(int a, int b) */
  int n = ((void*)0x12345678)(1,2)

Yes, Pony will eventually be ported to many platforms. For Android and iOS, we first need a 32-bit x86 port (to work out 64 vs 32 bit issues) and then an ARM port (to work out x86 vs ARM issues). The OS parts of the port should be straight-forward, since Android is Linux and iOS is Darwin.
Community help on porting would be fantastic :)
C function pointer types will be available soon, but aren't currently. You can write a C FFI to call function pointers right now, if you need to.

Ok, Thank you.


Migration failure - Calling unknown method: craft\console\Request::getSegment()

Describe the bug
After preparing everything to update to Craft 4, CP Nav fails the migration. Error:
*** applying m220409_000000_craft_4
    > rename column order in table {{%cpnav_navigation}} to sortOrder ... done (time: 0.012s)
    > add column prevLevel smallint AFTER `sortOrder` to table {{%cpnav_navigation}} ... done (time: 0.011s)
    > add column level smallint DEFAULT 1 AFTER `prevLevel` to table {{%cpnav_navigation}} ... done (time: 0.038s)
    > add column prevParentId integer AFTER `level` to table {{%cpnav_navigation}} ... done (time: 0.018s)
    > add column parentId integer AFTER `prevParentId` to table {{%cpnav_navigation}} ... done (time: 0.016s)
    > add column subnavBehaviour string AFTER `newWindow` to table {{%cpnav_navigation}} ... done (time: 0.052s)
    > update in {{%cpnav_navigation}} ... done (time: 0.004s)
    > dropping {{%cpnav_pending_navigations}} if it exists ... done (time: 0.004s)
Exception: Calling unknown method: craft\console\Request::getSegment() (/Users/darylknight/Sites/sitename/vendor/yiisoft/yii2/base/Component.php:300)
#0 /Users/darylknight/Sites/sitename/vendor/nystudio107/craft-seomatic/src/Seomatic.php(388): yii\base\Component->__call('getSegment', Array)
#1 /Users/darylknight/Sites/sitename/vendor/verbb/cp-nav/src/helpers/Permissions.php(73): nystudio107\seomatic\Seomatic->getCpNavItem()
#2 /Users/darylknight/Sites/sitename/vendor/verbb/cp-nav/src/migrations/m220409_000000_craft_4.php(99): verbb\cpnav\helpers\Permissions::getBaseNavItems()
#3 /Users/darylknight/Sites/sitename/vendor/craftcms/cms/src/db/Migration.php(49): verbb\cpnav\migrations\m220409_000000_craft_4->safeUp()
#4 /Users/darylknight/Sites/sitename/vendor/yiisoft/yii2/console/controllers/BaseMigrateController.php(758): craft\db\Migration->up()
#5 /Users/darylknight/Sites/sitename/vendor/craftcms/cms/src/console/controllers/MigrateController.php(360): yii\console\controllers\BaseMigrateController->migrateUp('m220409_000000_...')
#6 [internal function]: craft\console\controllers\MigrateController->actionAll()
#7 /Users/darylknight/Sites/sitename/vendor/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array(Array, Array)
#8 /Users/darylknight/Sites/sitename/vendor/yiisoft/yii2/base/Controller.php(178): yii\base\InlineAction->runWithParams(Array)
#9 /Users/darylknight/Sites/sitename/vendor/yiisoft/yii2/console/Controller.php(182): yii\base\Controller->runAction('all', Array)
#10 /Users/darylknight/Sites/sitename/vendor/yiisoft/yii2/base/Module.php(552): yii\console\Controller->runAction('all', Array)
#11 /Users/darylknight/Sites/sitename/vendor/yiisoft/yii2/console/Application.php(180): yii\base\Module->runAction('migrate/all', Array)
#12 /Users/darylknight/Sites/sitename/vendor/craftcms/cms/src/console/Application.php(90): yii\console\Application->runAction('migrate/all', Array)
#13 /Users/darylknight/Sites/sitename/vendor/yiisoft/yii2/console/Application.php(147): craft\console\Application->runAction('migrate/all', Array)
#14 /Users/darylknight/Sites/sitename/vendor/craftcms/cms/src/console/Application.php(121): yii\console\Application->handleRequest(Object(craft\console\Request))
#15 /Users/darylknight/Sites/sitename/vendor/yiisoft/yii2/base/Application.php(384): craft\console\Application->handleRequest(Object(craft\console\Request))
#16 /Users/darylknight/Sites/sitename/craft(27): yii\base\Application->run()
#17 {main}
*** failed to apply m220409_000000_craft_4 (time: 0.346s)

Steps to reproduce

Upgrade everything to latest Craft 3
Run composer update
This migration fails

Craft CMS version
Craft CMS 3.7.51
Plugin version
3.0.17
Multi-site?
Yes
Additional context
No response

Hmmm, this issue cropped up some time ago and fixed via https://github.com/verbb/cp-nav/commit/97323fe407d715a107e3c3fea507d4e8aa86579e in 4.0.2. This comes down to when trying to re-generate navigations on the command line, and some plugin's getCpNavItem() functions don't work so well in that scenario.

I'm sorry I don't understand what that means. Is it fixable? I'm currently uninstalling CP Nav before upgrading to Craft 4 and re-installing it again afterwards. It's happened on 3 sites so far.

What I mean is that it _shouldn't be happening anymore, and the site's I've tested from Craft 3 to 4 don't seem to throw this error (with SEOmatic installed), but I'll keep digging. I can't imagine you're not updating to the latest CP Nav version (4.0.5) which is why I mentioned that, just in case for some reason you're only updating to 4.0.0 or 4.0.1 (unlikely, but you never know!)

Got it - thanks. Yeah, this is after going through everything on the update tab and adding that version with the ^ symbol, so "verbb/cp-nav": "^4.0.5",

This is indeed still an issue, you're right. Fixed for the next release. To get this fix early, change your verbb/cp-nav requirement in composer.json to:
"require": {
  "verbb/cp-nav": "dev-craft-4 as 4.0.5",
  "...": "..."
}

Then run composer update.

Yep, this worked - thank you!

Fixed in 4.0.6


Grouping multiple items / blocks into one section

Description of new idea or improvement on existing one
Specifying a section for many different blocks that have the same options is inconvenient and makes the configuration very large. Right now, if you wanted to add all the varieties of granite to a job, one would agree that the following is very cumbersome.
granite:
    income: 0
    points: 0
    experience: 0
granite_slab:
    income: 0
    points: 0
    experience: 0
granite_stair:
    income: 0
    points: 0
    experience: 0
polished_granite:
    income: 0
    points: 0
    experience: 0
polished_granite_slab:
    income: 0
    points: 0
    experience: 0
polished_granite_stair:
    income: 0
    points: 0
    experience: 0

Instead, what would be better, is grouping them together. Take these couple of examples:
"cobblestone_[slab,stairs,wall]":
    income: 0
    points: 0
    experience: 0
"[polished_]granite[_slab,stair]":
    income: 0
    points: 0
    experience: 0

We can also group sections together by using placeholders that function similar to wildcards. Take this example:
"%color%_wool":
    income: 0
    points: 0
    experience: 0
"%wood%_planks":
    income: 0
    points: 0
    experience: 0

It could also be possible for these placeholders to be defined in the configuration itself such as:
placeholders:
    wood: [oak,dark_oak,birch,acacia,mangrove,crimson,warped]

However, I would consider this to be less of importance unless there was a real use case where this would be useful.
Detailed information what should do
If we take the key shown in the above example [polished_]granite[_slab,stair], we can trust that the section would apply for granite, granite_slab, granite_stair, polished_granite, polished_granite_slab, and polished_granite_stair, drastically cutting down on the size of the configuration and making it more convenient to all the different variations of items.
As for the %color%_wool key, that would correspond to white_wool, red_wool, green_wool and so on and so forth. %wood% would correspond to your different types of wood.

Interesting suggestion. Tho we do have option to define materials in one single line if you are after smaller files, like for example
  Place:
    # You can use list of materials to simplify adding each materials one by one
    # Remember that you should separate the income, points and exp with ';'
    materials:
    - sapling;1.0;1.0;1.0
    - wood;2.0;1.0
    - stone;0.1


Feature/vaccinecer 840 lt otp revocation

OtpRevocationService#getOtpRevocations has Cachable annotation which is great. But from what I've seen, it's only called from OtpRevocationService#isRevoked method which is another method from the same class. In that case, Cachable annotationwon't kick in. If you want OTP Revocations to be cached, you need to callOtpRevocationService#getOtpRevocationsfrom a different class/service or moveOtpRevocationService#getOtpRevocations` to another class.
For further information:
https://stackoverflow.com/questions/12115996/spring-cache-cacheable-method-ignored-when-called-from-within-the-same-class


W1 with anisotropic weights

Use correct harmonic averaging in consistent manner. Apply to anisotropic weights. Only cell based averaging.

Ignore the failing W1 tests for now as these are all based on face based weight reconstruction - which is outdated.


Merge to live!

Update Excel.Range.Formula2.md

Update Excel.Range.Formula2Local.md

Update Excel.Range.Formula2R1C1.md

Update Excel.Range.Formula2R1C1Local.md

Update Excel.Range.SavedAsArray.md

Update Excel.Range.SpillParent.md

Update range-formula-vs-formula2.md

Update datepart-function.md

Docs Build status updates of commit 278aa1f:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 278aa1f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/datepart-function.md
:white_check_mark:Succeeded
View

api/Excel.Range.Formula2.md
:white_check_mark:Succeeded
View

api/Excel.Range.Formula2Local.md
:white_check_mark:Succeeded
View

api/Excel.Range.Formula2R1C1.md
:white_check_mark:Succeeded
View

api/Excel.Range.Formula2R1C1Local.md
:white_check_mark:Succeeded
View

api/Excel.Range.SavedAsArray.md
:white_check_mark:Succeeded
View

api/Excel.Range.SpillParent.md
:white_check_mark:Succeeded
View

excel/Concepts/Cells-and-Ranges/range-formula-vs-formula2.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Design Notes

Design notes and discussion for a tool to manage runs of the Salish Sea Atlantis model.
The general idea is to create a new tool based on SalishSeaCast/NEMO-Cmd for running Atlantis. NEMO-Cmd is already the basis for tools for running various NEMO configurations (SalishSeaCast, GoMSS), WaveWatchIII, and FVCOM.
The goal is a command like:
atlantis run run_description.yaml results_directory_path/
e.g.
atlantis run 25yr.yaml /ocean/rlovindeer/MOAD/analysis-raisha/SSmodel_outputs/output-25yr/
That command will:

Use the run description YAML file to construct a temporary run directory for an Atlantis run
Launch the run as a background job
Gather the run inputs, metadata about the run, and the run outputs into the specified results directory

Other ideas:

Some sort of "run diary" mechanism inspired by Javier's Atlantis calibration workflow tool
Extension to launch collections of runs as GLOST jobs on HPC for large scale batch work like sensitivity studies

@raishalovindeer I decided that I should write down what I have been thinking about on this in a way/place where we can discuss and reflect on it. It it turns out that you don't think this will add value to your workflow, it doesn't have to go any farther than discussion.
I have more notes to add here, but I have to go out for a while. Will continue later today.

Here's a first cut at a run description YAML file layout with some design questions/alternatives noted in comments:
run id: 25yr

paths:
  Atlantis code: /ocean/rlovindeer/Atlantis/atlantis-trunk/
  runs directory: /ocean/rlovindeer/Atlantis/runs/

forcing:
  # keys are the file/directory names that are used for the
  # symlinks created to the values of the `link to:` items
  SS_init.nc:
    link to: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/SS_init.nc

  # important design questions here!!!

  # This approach links an entire directory of forcing files into tmp run dir
  # and leaves the specification of which files from there are used to lines in forcing.prm
  inputs:
    link to: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/inputs

  # This approach identifies the forcing files explicitly here
  # and potentially lets forcing.prm be generic;
  # i.e. no inputs/... just file names that match keys here.
  # This also keeps tmp run dir flat.
  SS_hydro.nc:
    link to: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/inputs/SS_hydro.nc
  SS_temp.nc:
    link to: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/inputs/SS_temp.nc
  SS_salt.nc:
    link to: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/inputs/SS_salt.nc

parameters:
  groups: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/SS_grps.csv
  run: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/SS_run.prm
  forcing: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/SS_forcing.prm
  physics: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/SS_physics.prm
  biology: /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/SS_biology.prm

  # Another design question!!

  # Alternative is to make these lists of files that are concatenated
  # to create the filename that is the key.
  # This is a little cumbersome because we still need to know what kind of
  # parameter file each is
  groups:
    # example of single file list
    SS_grps.csv:
      - /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/SS_grps.csv

output filename base: outputSalishSea

vcs revisions:
  svn:
    # can probably make this automatic because we have it already in `paths: Atlantis code:`
    - /ocean/rlovindeer/Atlantis/atlantis-trunk/
  git:
    - /ocean/rlovindeer/Atlantis/salish-sea-atlantis-model/

Thanks for this Doug. I'm really liking this approach and think it will add value because it makes the run transparent—easier for us to have a memory of what we did for each run. Your suggestions seem excellent but I'll look over this some more in detail tomorrow and see if I have any additional suggestions or strong opinions on the content of the run description YAML.

Great! I will try to add more notes tomorrow about structure and contents of tmp run dir that I am thinking about. Happy to do video call on Slack if/when you want to talk more synchronously about this.

I think I have a demo of the whole flow of a minimal atlantis run command set up now on tyee. It starts from this run description YAML file:
run id: 25yr

paths:
  Atlantis code: /ocean/dlatorne/Atlantis/atlantis-trunk/
  runs directory: /ocean/dlatorne/Atlantis/runs/

polygons: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/SS_xy.bgm

initial conditions: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/SS_init.nc

forcing:
  SS_hydro.nc:
    link to: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/inputs/SS_hydro.nc
  SS_temp.nc:
    link to: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/inputs/SS_temp.nc
  SS_salt.nc:
    link to: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/inputs/SS_salt.nc

parameters:
  groups: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/SS_grps.csv
  run: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/SS_run.prm
  forcing: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/SS_forcing.prm
  physics: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/SS_physics.prm
  biology: /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/SS_biology.prm

output filename base: outputSalishSea

vcs revisions:
  git:
    - /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/

Assuming that file is called 25yr.yaml, the command atlantis run 25yr.yaml /ocean/dlatorne/Atlantis/runs/25yr/ would create a temporary run directory like /ocean/dlatorne/Atlantis/runs/25yr_2021-06-30T111454.630340-0700/. That directory presently exists on tyee. Its contents are:
lrwxrwxrwx 1 dlatorne sallen       76 Jun 25 14:44 atlantisMerged -> /ocean/dlatorne/Atlantis/atlantis-trunk/atlantis/atlantismain/atlantisMerged*
-rw-rw-r-- 1 dlatorne sallen   384229 Jun 25 14:52 SS_xy.bgm
-rw-rw-r-- 1 dlatorne sallen 13295166 Jun 25 14:53 SS_init.nc
lrwxrwxrwx 1 dlatorne sallen       69 Jun 25 15:01 SS_hydro.nc -> /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/inputs/SS_hydro.nc
lrwxrwxrwx 1 dlatorne sallen       68 Jun 25 15:01 SS_salt.nc -> /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/inputs/SS_salt.nc
lrwxrwxrwx 1 dlatorne sallen       68 Jun 25 15:01 SS_temp.nc -> /ocean/dlatorne/Atlantis/salish-sea-atlantis-model/inputs/SS_temp.nc
-rw-rw-r-- 1 dlatorne sallen     5343 Jun 25 15:05 SS_grps.csv
-rw-rw-r-- 1 dlatorne sallen    13529 Jun 25 15:06 SS_physics.prm
-rw-rw-r-- 1 dlatorne sallen   766070 Jun 25 15:07 02SS_biology.prm
-rw-rw-r-- 1 dlatorne sallen     2099 Jun 25 15:09 SS_forcing.prm
-rw-rw-r-- 1 dlatorne sallen      190 Jun 25 15:23 salish-sea-atlantis-model_rev.txt
-rw-rw-r-- 1 dlatorne sallen     7370 Jun 30 16:11 SS_run.prm
-rwxrwxr-- 1 dlatorne sallen     1270 Jul  6 15:44 Atlantis.sh*
-rw-r--r-- 1 dlatorne sallen     1098 Jul  6 15:48 25yr.yml

The Atlantis.sh script gets generated by atlantis run and executed as the final step of atlantis run to launch atlantisMerged with the appropriate command-line options. The results of the run initially accumulate in the temporary run directory, so you can monitor progress there, and by looking at the stdout and stderr files in the results directory (/ocean/dlatorne/Atlantis/runs/25yr/). When the run finishes, all of the files (but not the symlinks) in the tmp run dir are moved to the results directory, and the tmp run dir is deleted.
The contents of the results directory, /ocean/dlatorne/Atlantis/runs/25yr/ at the end of the process are:
-rw-rw-r-- 1 dlatorne sallen   384229 Jun 25 14:52 SS_xy.bgm
-rw-rw-r-- 1 dlatorne sallen 13295166 Jun 25 14:53 SS_init.nc
-rw-rw-r-- 1 dlatorne sallen     5343 Jun 25 15:05 SS_grps.csv
-rw-rw-r-- 1 dlatorne sallen    13529 Jun 25 15:06 SS_physics.prm
-rw-rw-r-- 1 dlatorne sallen   766070 Jun 25 15:07 02SS_biology.prm
-rw-rw-r-- 1 dlatorne sallen     2099 Jun 25 15:09 SS_forcing.prm
-rw-rw-r-- 1 dlatorne sallen      190 Jun 25 15:23 salish-sea-atlantis-model_rev.txt
-rw-rw-r-- 1 dlatorne sallen     7370 Jun 30 16:11 SS_run.prm
-rwxrwxr-- 1 dlatorne sallen     1270 Jul  6 15:44 Atlantis.sh*
-rw-rw-r-- 1 dlatorne sallen     1098 Jul  6 15:48 25yr.yml
-rw-rw-r-- 1 dlatorne sallen        0 Jul  6 15:49 delete_to_halt_run
-rw-rw-r-- 1 dlatorne sallen    17396 Jul  6 15:49 SS_run.xml
-rw-rw-r-- 1 dlatorne sallen   111844 Jul  6 15:49 SS_grps.xml
-rw-rw-r-- 1 dlatorne sallen  1093304 Jul  6 15:49 02SS_biology.xml
-rw-rw-r-- 1 dlatorne sallen 13715452 Jul  6 15:49 outputSalishSea.nc
-rw-rw-r-- 1 dlatorne sallen   213780 Jul  6 15:49 outputSalishSeaTOT.nc
-rw-rw-r-- 1 dlatorne sallen  1504900 Jul  6 15:49 outputSalishSeaPROD.nc
-rw-rw-r-- 1 dlatorne sallen  8212818 Jul  6 15:49 log.txt
-rw-rw-r-- 1 dlatorne sallen      850 Jul  6 15:49 outputSalishSeaYOY.txt
-rw-rw-r-- 1 dlatorne sallen      871 Jul  6 15:49 outputSalishSeaSSB.txt
-rw-rw-r-- 1 dlatorne sallen     3322 Jul  6 15:49 outputSalishSeaBiomIndx.txt
-rw-rw-r-- 1 dlatorne sallen    22181 Jul  6 15:49 outputSalishSeaSpecificMort.txt
-rw-rw-r-- 1 dlatorne sallen     2184 Jul  6 15:49 outputSalishSeaMort.txt
-rw-rw-r-- 1 dlatorne sallen    48880 Jul  6 15:49 outputSalishSeaMortPerPred.txt
-rw-rw-r-- 1 dlatorne sallen   233475 Jul  6 15:49 outputSalishSeaSpecificPredMort.txt
-rw-rw-r-- 1 dlatorne sallen   227104 Jul  6 15:49 outputSalishSeaDietCheck.txt
-rw-rw-r-- 1 dlatorne sallen   234084 Jul  6 15:49 outputSalishSeaPredPropCheck.txt
-rw-rw-r-- 1 dlatorne sallen     2065 Jul  6 15:49 outputSalishSeaMigration.txt
-rw-rw-r-- 1 dlatorne sallen      859 Jul  6 15:49 outputSalishSeaVertSize.txt
-rw-rw-r-- 1 dlatorne sallen   200462 Jul  6 15:49 outputSalishSeaBoxBiomass.txt
-rw-rw-r-- 1 dlatorne sallen    41063 Jul  6 15:49 outputSalishSeaAnnualAgeBiomIndx.txt
-rw-rw-r-- 1 dlatorne sallen     9626 Jul  6 15:49 outputSalishSeaAgeBiomIndx.txt
-rw-rw-r-- 1 dlatorne sallen     2819 Jul  6 15:49 outputSalishSeaBoxLight.txt
-rw-rw-r-- 1 dlatorne sallen   159933 Jul  6 15:49 inputs.ts
-rw-rw-r-- 1 dlatorne sallen   162048 Jul  6 15:49 export.ts
-rw-rw-r-- 1 dlatorne sallen    55273 Jul  6 15:49 stderr
-rw-rw-r-- 1 dlatorne sallen    16802 Jul  6 15:49 outputSalishSeaMigrationArray.txt
-rw-rw-r-- 1 dlatorne sallen    22401 Jul  6 15:49 stdout

I shortened my testing run to 10 day, so despite its name, this isn't really a 25 year run :smile:

Some more notes on design issues that arose from the exercise above:

svn is very different to git. You can't do svn log -l 1 to get information about the working copy rev without accessing the svn server. That requires authentication for atlantis-trunk which would greatly complicate things. I need to think more about how to get a VCS record for atlantis-trunk similar to what is in salish-sea-atlantis-model_rev.txt for the salish-sea-atlantis-model Git repo clone.

The console output from atlantisMerged is a mixture of output to the stdout and stderr streams. I've captured them separately in my example above. They could alternatively be captured as an interleaved stream in stdout if that makes more sense. Note that stdout also gets messages from the Atlantis.sh script for things that happen before and after the actual run of atlantisMerged.

Thanks for this detailed trial run and description Doug.
First thing I notice—from your list of files that get saved in the results directory at the end, it appears we're also saving some of the original .prm files, which is excellent. Especially these:

-rw-rw-r-- 1 dlatorne sallen    13529 Jun 25 15:06 SS_physics.prm
-rw-rw-r-- 1 dlatorne sallen   766070 Jun 25 15:07 02SS_biology.prm
-rw-rw-r-- 1 dlatorne sallen     2099 Jun 25 15:09 SS_forcing.prm
-rw-rw-r-- 1 dlatorne sallen     7370 Jun 30 16:11 SS_run.prm

Most (if not all) of the differences between runs during an investigation will be reflected inside those files and not in the run code itself, and I was wondering how we were going to capture the small changes in the .prm files for each run. Saving the .prm files with the results, just as they were used for the run, is a great feature.

What do stdout and stderr stand for? My brain reads standard output and standard error, but in the context of Atlantis, I don't know what those streams represent.

re: the .prm files: The idea is to capture all of the run configuration details with the run output. The hope is to enable relatively easy reproducibility, and relatively easy diff-ing of configuration between runs after the fact.

re:  stdout and stderr:
They are exactly what you read. They are one of the base features that Linux copied from Unix. Well written code sends informational messages to stdout and errors, warnings, etc. to stderr. Things get a little murky when it comes to debugging output. Some devs and tools send it to stderr, others to stdout. So much for "standard" :smirk: The other murky thing is that the 2 streams are merged when a program's output goes to the terminal (as you see when you run Atlantis now). It is possible to capture them separately though when things are wrapped in a shell script like Atlantis.sh that AtlantisCmd will generate. The idea with AtlantisCmd is that the run can be detached from terminal output and all of the stuff that would appear on the terminal is captured in file(s) in the results directory.
The question is whether to separate them in the results directory, or dump everything into stdout so that it reads the same as what you would see if you were reading it as it streams by on the terminal now.

I did a little more research on the VCS recording with svn issue and found that, without having to authenticate to the server, svn info provides a bunch of useful stuff including:

repo URL
last changed rev
last changed authored
last changed date
What's missing compared to what we can get from git are the list of files that were touched in the most recent commit, and the commit message. I'm fuzzy on whether svn has the git concept of commit and push to server, or if svn commit communicates directly with the server. So, I'm not sure if there is a case where svn info would show something different for changes that have been committed but not pushed (if that's even a thing).

svn diff also works without authentication, so we can capture uncommitted changes.

Closing this because we now have an initial implementation. It's close to what is written above, though the structure of the YAML run description file did evolve some; see docs.


Update README.md

Add a little documentation about the new capability of being able to visualize custom objects and being able to customize the text and/or icons displayed in the graph

Looks good, thanks @khdesai!


Fix various region visibility edge cases

Fixes part of #291
Depends on #326
Depends on #311
Depends on #286
Depends on #293

Odd.. Looks like there's an issue with Linux that doesn't repro on mac:
21:40:10 Expected: 0
21:40:10 Actual:   1
21:40:10 lt-testregion: testregion.c:904: test_isVisibleRegionRectI: Assertion `(int)isVisible == (int)(0)' failed.
21:40:10


Add kids theme

Add kids theme

please label this with hacktoberfest tag
thanks :)

Done. Don't forget to star the repo. Thanks


Tab view padding

I add padding parameter to MacosTabView to allow setting custom.
I am using macos_ui package in one of my apps and the default padding impact the ui.
here is a screenshot of the app with the MacosTabView with the default padding and a DataTable as one of children

And here is the same app with custom padding

Pre-launch Checklist

[x] I have run dartfmt on all changed files
[x] I have incremented the package version as appropriate and updated CHANGELOG.md with my changes
[x] I have added/updated relevant documentation
[x] I have run "optimize/organize imports" on all changed files
[x] I have addressed all analyzer warnings as best I could

Have made all changes.

Very pleased to do such a little thing. Realy love your work.


fix: onclick components cant be removed

Mind to add tests to prevent accidental deletion?

Mind to add tests to prevent accidental deletion?

done


Re-build time issue with webpack v3.0.0

I migrated to v3.0.0 from version 1.x and followed the official migration guide to do so. But the re-build time of webpack-dev-server and webpack watch had increased significantly (from 3 seconds to 15 seconds). I downgraded to v2.6.1, and the re-build time got back to what it was on version 1, using the same config file. Here is the config file that I am using:
const path = require('path');
require('es6-promise').polyfill();
const ExtractTextPlugin = require('extract-text-webpack-plugin');

const devBuild = process.env.NODE_ENV !== 'production';
const nodeEnv = devBuild ? 'development' : 'production';

const config = {
  entry: [
    'es5-shim/es5-shim',
    'es5-shim/es5-sham',
    'babel-polyfill',
    './app/common/startup/CommonApp'
  ],
  output: {
    filename: 'webpack-bundle.js',
    path: path.resolve(__dirname, '../app/assets/webpack'),
  },

  resolve: {
    extensions: ['.json', '.jsx', '.js'],
    alias: {
      libs: path.join(process.cwd(), 'app', 'libs'),
      common: path.join(process.cwd(), 'app', 'common'),
      react: path.resolve('./node_modules/react'),
      'react-dom': path.resolve('./node_modules/react-dom'),
    },
  },
  plugins: [
    new webpack.DefinePlugin({
      'process.env': {
        NODE_ENV: JSON.stringify(nodeEnv),
      },
    }),
    new ExtractTextPlugin({ filename: 'app.css', allChunks: true }),
    new webpack.LoaderOptionsPlugin({
      debug: true
    })
  ],
  module: {
    rules: [
      {
        test: /plugin\.css$/,
        use: [
          'style-loader', 'css-loader',
        ],
      },
      { test: require.resolve('react'), use: 'imports-loader?shim=es5-shim/es5-shim&sham=es5-shim/es5-sham' },
      {
        test: /\.css$/, exclude: /plugin\.css$/,
        loader: ExtractTextPlugin.extract({
          fallback: 'style-loader',
          use: 'css-loader?modules&importLoaders=1&localIdentName=[name]__[local]___[hash:base64:5]'
        })
      },
      { test: /\.jsx?$/, loader: 'babel-loader', exclude: /node_modules/ }
    ],
  },
};

module.exports = config;

if (devBuild) {
  console.log('Webpack dev build for Rails'); // eslint-disable-line no-console
  module.exports.devtool = 'eval-source-map';
} else {
  config.plugins.push(
    new webpack.optimize.DedupePlugin()
  );
}

The only difference I see in the logs is:
DeprecationWarning: Chunk.modules is deprecated. Use Chunk.getNumberOfModules/mapModules/forEachModule/containsModule instead.     at /node_modules/extract-text-webpack-plugin/index.js:271:24
which pops up when using v3.0.0 but doesn't show any such warning with v2.6.1.
Which means it must be related to extract-text-webpack-plugin?

@raiprabh - This issue will be resolved with #553
That PR is waiting on a fix in Webpack ( it's listed in the PR ).

@raiprabh can your update to 3.0.0-rc.0 and check?

@evilebottnawi - I evidently missed a chunk.module in there somewhere. There will be another rc build today at some point.

@d3viant0ne seems yep, now i migrate own repos to webpack 3 and get warning:
DeprecationWarning: Chunk.modules is deprecated. Use Chunk.getNumberOfModules/mapModules/forEachModule/containsModule instead.

I'm activly working on this & trying to figure out what it's still rendering css in the wrong order

@raiprabh - Please pick up<EMAIL_ADDRESS>( requires<EMAIL_ADDRESS>) and let me know if you are still seeing a performance issue.

@d3viant0ne - sure, i'll try it out and post my observations today.

@d3viant0ne I still have the warning
"DeprecationWarning: Chunk.modules is deprecated. Use Chunk.getNumberOfModules/mapModules/forEachModule/containsModule instead."
My package.json: https://github.com/ova2/angular-development-with-primeng/blob/master/angular-primeng-seed-for-authors/package.json
Simple try to execute npm run start:prod What is wrong in my webpack config?

We missed one - https://github.com/webpack-contrib/extract-text-webpack-plugin/blob/master/src/lib/ExtractTextPluginCompilation.js#L38
I'll get it sorted shortly and out this evening

@ova2 - I'm still seeing the deprecation warning as well, i'll get it sorted.

@d3viant0ne I hope you can fix it ;-) Many thanks for your effort!

So after seriously considering I was losing my mind & questioning if I am any good at JavaScript, this particular deprecation warning isn't coming from etwp.

But if it's not coming from etwp, how do you want to kill it? -:)
Am 13.07.2017 21:24 schrieb "Joshua Wiens"<EMAIL_ADDRESS>So after seriously considering I was losing my mind & questioning if I am
any good at JavaScript, this particular deprecation warning isn't coming
from etwp.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/561#issuecomment-315177279,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAu1ZhVOSel08HTSmbi4AqFv69d3Wb9fks5sNm7hgaJpZM4OPRmA
.

@d3viant0ne FYI: The warning came from webpack-md5-hash. I've removed this plugin and the warning is gone. No issues with extract-text-webpack-plugin.

@ova2 - Yeah, just keeping this open just until I have the PR open to md5

@raiprabh problem still exists?


logic for SSD in TS client

limit size of SSD which can be requested
there are quite some servers where SSD capacity is not large enough in line of CPU/MEM capacity.
We should not allow anyone to provision more than 2x total CU relation to SSD
e.g. if total CU is 10 and SSD 500 GB. this means one CU can max reserve 100 GB (500/10x2)
This should be checked when filling in the field, so not at deploy time alone, fill in max size.
Put this now in TS client for now as well (this is check at deploy time), we can later do it in ZOS. Do good error reporting at deploy time, to explain what issue is, and what max size is which can be done.
over-provisioning is possible !!!

lets allow overprovision of 2x for now
if e.g. 500GB SSD, 1000 GB can be requested, because people will avg out not use the full capacity.

Moved from: https://circles.threefold.me/project/test-tfgrid3/issue/6


update dockerfile and devcontainer

The defaults are there to provide a nice dev experience out of the box.


BZ-1066962  Add support for git hooks

Some code style refactoring. Merge of duplicate code etc.

http://github.com/uberfire/uberfire/commit/a0dbc0a3b


React Native, cannot connect native focus to Norigin focus

Describe the bug
I tried connecting the native focus provided via RN (tvOS and AndroidTV) based on the example provided in the documentation but cannot make it work.
To Reproduce
  const {ref, focused, focusSelf} = useFocusable({
    onEnterPress: () => {
      onClickFkt();
    },
  });

return (
    <Pressable
      ref={ref}
      onFocus={focusSelf}>
      <Icon
        name={'play'}
        style={focused ? localStyles.button_focused : localStyles.button}
      />
    </Pressable>
  );

I checked that the onFocus callback of Pressable is executed when I move around in my app. Based on the Norigin-Spatial-Navigation documentation:
In order to "sync" the focus events coming from the native focus engine to the hook the onFocus callback needs to be linked with the focusSelf method. This way the hook will know that the component became focused and will set the focused flag accordingly.
I would have expected that focused would change when focusSelf is called. This does not happen.
Norigin Navigation is setup using nativeMode: true
Expected behavior
I would have expected that focused would change when focusSelf is called.

I tested a bit further. I noticed that using Pressable was probably not suitable and I switched to TouchableOpacity.
I created an example here: https://github.com/MalteSchm/TestcaseFocusNoriginNav I use this app as tvOS and AndroidTV application.
I can see that focus is set to the TouchableOpacity on keyboard presses when running the app in the simulator. The focus / style of the elements seems to be a result of TouchableOpacity and not a result of the styles that are provided.
I expected that focused would become true when focusSelf is called and the style is selected acoordingly. This does not seem to be the case.
A screenshot of the result is shown below (both AndroidTV and tvOS applicaiton). The stylesheet specifies the focused button to be "red" which obviously does not happen

In fact, focusSelf does not work in native mode.
  setFocus(focusKey: string, focusDetails: FocusDetails = {}) {
    // Cancel any pending auto-restore focus calls if we are setting focus manually
    this.setFocusDebounced.cancel();

    if (!this.enabled || this.nativeMode) {
      return;
    }


haven't deregister master when stop && have't add health check consul  health check for master

Describe the bug
A clear and concise description of what the bug is.
Environment
Describe your server system version, kernel version
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
cInfo := &ConsulRegisterInfo{
	Name:    app,
	ID:      id,
	Address: host,
	Port:    port,
	Tags: []string{
		"app=" + app,
		"role=" + role,
		"cluster=" + cluster,
	},
}

Describe the bug
A clear and concise description of what the bug is.
Environment
Describe your server system version, kernel version
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
cInfo := &ConsulRegisterInfo{
	Name:    app,
	ID:      id,
	Address: host,
	Port:    port,
	Tags: []string{
		"app=" + app,
		"role=" + role,
		"cluster=" + cluster,
	},
}

Hi @wwq1988 ,
The description of this issue is very unclear.
Please describe in detail.

@wwq1988
I now answer the information in your title.

Why do you think the component needs to be unregistered with the master when it is stopped. In actual use, there will be many artificial and temporary stops of nodes due to various reasons, such as server maintenance and restart. These nodes will be restarted and serviced shortly after maintenance. If a component is removed from the cluster after it is stopped, the system will rebuild the data copy on the stopped node on other online nodes in the cluster in order to ensure sufficient data copy redundancy. This will cause a lot of unnecessary performance loss.

consul is used to serve Prometheus. It is only a third-party and optional component. It is not a part of ChubaoFS. From the semantics of the entire project and components, he does not need the master to manage it. The master is our resource manager who is only responsible for managing the resources of the ChubaoFS cluster.

@mervinkid ok


Arrange the components of the page to make it more user friendly

The different components for shape, style, and text are not positioned correctly, causing the user to scroll down repeatedly to make even small changes. Design the layout so that all the tools are more accessible.

I would like to work on this issue pls assign me this @vishanurag

I am already working on it


3890 not working, missing DNS records?

I follow all steps of the guide and I still can connect my conga to HA, maybe is missing some dns records but not sure.
at the moment my DNS on the robot
<IP_ADDRESS> cecotec.das.3irobotix.net cecotec.download.3irobotix.net cecotec.log.3irobotix.net cecotec.ota.3irobotix.net eu.das.3irobotics.net eu.log.3irobotics.net eu.ota.3irobotics.net
If I ping any of the cecotec DNS, <IP_ADDRESS> is my HA ip.
PING cecotec.das.3irobotix.net (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=64 time=8.056 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=64 time=4.203 ms
64 bytes from <IP_ADDRESS>: seq=2 ttl=64 time=2.076 ms
64 bytes from <IP_ADDRESS>: seq=3 ttl=64 time=2.072 ms
64 bytes from <IP_ADDRESS>: seq=4 ttl=64 time=2.166 ms
64 bytes from <IP_ADDRESS>: seq=5 ttl=64 time=2.090 ms
64 bytes from <IP_ADDRESS>: seq=6 ttl=64 time=2.063 ms

The robot is still online on the conga 3890 APP so not sure what I'm missing...

The 3890 model is not yet supported.
You are free to koin to the already open discussion trying to get into this model protocol
https://github.com/adrigzr/agnoc/issues/40


Feature request: Bandpower function to output specified ratios (e.g., theta/beta etc)

Would be nice to be able to do this easily in YASA :)

Hi @apavlo89,
Thanks for opening the issue! How would you specify the ratios? It's pretty straightforward to calculate from the output of the yasa.bandpower function already (e.g. data['delta_beta'] = data['delta'] / data['beta']), and therefore, I'm not sure it is worth burdening the API of the bandpower function.
Thanks,
Raphael


feat: add ChatGPT support

move finder code to share with all content
rename indicator.js -> create-element.js
move element creation to create-element
inject contentElementSelector
include the self element in findRanges
add the content.chatgpt to build

Part of #86
Need help with the style:

it seems like we have two options to solve this:

diverge the CSS when we are on chatgpt's URL to manipulate the color
add a more comprehended solution traversing up to the first background colour and determining the colour based on it.

@baruchiro @jossef WDYT?

On Hold: Waiting for @jossef to finish the Figma styles and support dark mode.


Neumorphic button idea

Adding this button idea that I'd like to implement

Issue: #96

Great thanks for the help!
@all-contributors please add @vitoriapena for idea


Drop VC features

Would be good to drop the VC features in the recipe as these are out-dated.

Already done.

Already done.


Cloud reader on Microsoft Edge, failed HTTP CORS header when fetching from browser cache

This looks like an Edge-specific bug, as Internet Explorer, Chrome and Firefox work fine.
SEC7120: Origin XYZ not found in Access-Control-Allow-Origin header. SCRIPT7002: XMLHttpRequest: Network Error 0x80700013, Could not complete the operation due to error 80700013.
The error goes away when the browser cache is cleared, or bypassed via the developer tools F12 (network tab). I am closing this issue immediately as I don't think we can do anything about it. We use regular Ajax / jQuery-wrapped XMLHttpRequest.
http://readium.surge.sh/?epub=https://dl.dropboxusercontent.com/u/38631221/CircularFLO_Published_EPUBs/JigsawPlaced
http://readium.surge.sh/?epub=https://dl.dropboxusercontent.com/u/38631221/CircularFLO_Published_EPUBs/CircularFLO_v5_1_promo
http://readium.surge.sh/?epub=https://dl.dropboxusercontent.com/u/38631221/CircularFLO_Published_EPUBs/InterativeEbooks
http://readium.surge.sh/?epub=https://dl.dropboxusercontent.com/u/38631221/CircularFLO_Published_EPUBs/baby_jigsaw

Hi
I am experiencing same issue you explained in this post, has there been any fix for that?
Thanks

Do you compile the Readium cloud/web reader yourself, or do you use an off-the-shelf ready-to-use build?
Which GitHub revision are you using? Latest code from the develop branch? ( https://readium.firebaseapp.com or https://readium.surge.sh )

I am not using Readium. I have an issue with a 3rd party component when I use it from my web app I keep getting the same error that you get and the only fix is to force the browser to get resources from the browser on the dev tools which is obviously is not a fix I can tell my users to do. The error happens with IE but with Chrome things are fine


update_pr pipeline is triggering and failing unexpectedly

Error message: Could not get latest source version from github using commit reference.
Additional info from trouble shooting:
This reference is pointing to correct code base when used against public repo azure-sdk-for-python. So issue seems to be in replicating(cloning) tool which is supposed to move commits in public repo to private repo.

This doesn't look like an issue anymore. Issue was due to wrong trigger even when PR was submitted on main repo. Pipeline is triggered now only if a PR is submitted to cloned branch.

This issue is still occurring.

This problem is not occurring anymore.


Another set of features

This time I updated the Readme.md to specify the new features. Of particular importance are the following for me:

I extensively tested the useInShaderTextures option and don't think it should be considered experimental at this point, though some user input would be nice. I don't know how many users the extension has right now though,
I added the ability to load other shaders as textures, which required a significant refactor to be at all readable and usable. These can be specified inside shaders or settings, though in my opinion the latter version should just as well be deprecated because it is not nearly as user-friendly at this point. Shaders feeding back into themselves is not supported yet,
paths can now be specified relative to the working directory, this is handled by the extension itself and doesn't rely on third-party behavior (hopefully),
last but not least improved the interface for compilation errors, which now highlights the line an error happens on, when the user clicks said line. This works as expected with multiple passes, in that it displays all errors on one page and highlights lines in the appropriate file.

One particular problem that I would like to address, but have not been able to, is the problematic sampling of textures. If you investigate the uv-warp.glsl -> multipass.glsl demo and output only uv in uv-warp.glsl then you can see that using the resulting texture will have significant artifacts compared to computing uv yourself inside multipass.glsl. I tried eliminating it by using different filtering methods but to no avail. Maybe someone else has an idea?

I also now just updated three.js and passed a webgl2 context to WebGlRenderer. If not available this will automatically fall back to webgl1, but when available it will allow more modern shaders.

Thanks @Malacath-92. This looks great. Really powerful features.

Added three more commits

Great, thank you. I will merge/release tonight.

Any idea though what the sampling issue is related to?

No clue. Haven't looked into it yet. Would you mind opening up a new issue with a screenshot of the problem?

I was gonna do that on the main repo as soon as this gets merged. Otherwise I'll keep investigating before you merge if you would prefer that.

I was going to go ahead and merge it with the understanding this would be an outstanding issue with the new features. The new features are important enough I don't want to block the release. What do you think?

Released 0.7.1. Thanks @Malacath-92

Yes, I approve that the issue isn't so severe that it should block the release. I'll open the Issue later when I get to a PC.


Importing renewed certificate makes certificate duplicate

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[x] Bug is not already reported in another issue

Technical details

Device name:
Android version:
App version:

Describe the bug

Importing a renewed certificate makes the certificate duplicate in the list
Steps to reproduce the issue

Import a certificate on 2 devices
Renew a certificate on one device
Import the renewed cert on second device

Expected behaviour

Certificate gets also renewed on second device
Possible Fix

Expected behavior new cert replaces old cert
Additional context

@gleichda
I don't think this can be considered a bug, although it could be a wishlist item.
The old and new certificates are only connected by hash information on an RKI server, so to automate a clean up after importing a renewed certificate would involve contacting the RKI server. That is probably not desirable. Certificate scanning should be possible locally without having to share any data with a central server instance.
The privacy notice explains in the section "Update feature for COVID certificates"
In order to be able to prevent users from using the update feature several times, which is not permitted, the electronic signatures of the updated and new digital COVID certificates are temporarily stored on the app’s server system by means of special one-way encryption (what’s known as a hash value). This means that the app performs a certain mathematical procedure in order to convert the electronic signature in such a way that it can no longer be identified. The hash value cannot be used to infer the data in the relevant digital COVID certificate or other information about you. However, it is still possible to clearly assign the hash value to the updated digital COVID certificate. The hash values will be deleted again 365 days after the update.

When importing a certificate the app checks if there is already a certificate in the app with the same UCID (Unique Certificate Identifier). Only if this is the case, the app shows an info message to the user that the certificate is already in the app.
As the renewed and the old certificate have different UCIDs, the app does not detect that they are the same (from users perspective).

@Ein-Tim @MikeMcC399 by using the information from the certificate this should be possible: Comparing name,  date of event and type of certificate (Vaccination, recovery) with existing certificates this should be easy doable I would say

@gleichda
Up to a maximum of three devices the expected use case is for the reissue to be requested on each device individually. A user would only need to scan a reissued certificate starting with the fourth device and there the old certificate would need to be deleted by hand. On the first three devices the older certificate would be automatically removed (see https://www.coronawarn.app/en/faq/results/#dcc_replacement_howto).
You are right that it would be possible to compare other fields on the certificate. It will be up to the developers to consider whether this is something they would want to implement.
This issue should probably be moved to cwa-wishlist/issues and I expect that the moderators will look at this.


Didn't know that result:ok is required in JSON response for sending location.

Can we document that {"result": "ok"} is required in the response to make it a valid response?
https://github.com/aaronpk/Overland-iOS/blob/5f2a5be9bdea8a26677a37f15f477360613c5500/GPSLogger/GLManager.m#L236C43-L236C58
Happy to start on the code; I'd like to add it to the UI or README, somewhere obvious.
Amazing app. Thanks <3

It's mentioned in the readme but it could be in a better spot. Feel free to suggest something in a PR.

Taking another look, your docs are already great, I just missed it earlier.


Header transfer-encoding make Splash API return 504 Gateway Timeout

I was developing a crawler using Splash when suddenly i started to receive a lot of gateway timeouts. Trying to troubleshooting the problem, i discover the cause of this is header transfer-encoding: chunked, i made a PoC  (the url httpbin.org/headers returns the same headers i sent on request):
import requests
import json

ENDPOINT_SPLASH = 'http://localhost:8050/execute'

def test_with_custom_headers():
    lua_script = """
    function main(splash, args)
     splash:set_custom_headers({
       ["x-custom-header"] = "splash"
     })
     assert(splash:go(args.url))
     assert(splash:wait(0.5))
     return {
       html = splash:html()
     }
    end
    """

    payload = {
        'lua_source': lua_script,
        'url': 'https://httpbin.org/headers',
        'timeout': 15,
    }

    r = requests.post(url=ENDPOINT_SPLASH,
                      json=payload)

    result = json.loads(r.text)

    return result.get('html', result)

def test_with_content_encoding():
    lua_script = """
    function main(splash, args)
     splash:set_custom_headers({
       ["transfer-encoding"] = "chunked"
     })
     assert(splash:go(args.url))
     assert(splash:wait(0.5))
     return {
       html = splash:html()
     }
    end
    """

    payload = {
        'lua_source': lua_script,
        'url': 'https://httpbin.org/headers',
        'timeout': 15,
    }

    r = requests.post(url=ENDPOINT_SPLASH,
                      json=payload)

    result = json.loads(r.text)

    return result.get('html', result)

print("test_with_custom_headers: \n{}\n".format(test_with_custom_headers()))
print("test_with_content_encoding: \n{}".format(test_with_content_encoding()))

Results:
test_with_custom_headers:

{
  "headers": {
    "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8",
    "Accept-Encoding": "gzip, deflate",
    "Accept-Language": "en,*",
    "Host": "httpbin.org",
    "User-Agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/602.1 (KHTML, like Gecko) splash Version/9.0 Safari/602.1",
    "X-Custom-Header": "splash"
  }
}

test_with_content_encoding:
{'info': {'timeout': 15.0}, 'type': 'GlobalTimeoutError', 'error': 504, 'description': 'Timeout exceeded rendering page'}

@kmike @Gallaecio Can you guys take a look at this?

@kmike @Gallaecio I only need to know if this is a qt issue or splash issue, please give me some feedback, thanks!

@lucywang000 Can you at least take a look on this? Is this problem of Qt?

I'm having the same issue but weirdly enough only when using proxies via splash:on_request.
My splash is patched with decompression patch described in this issue: https://github.com/scrapinghub/splash/issues/324 if you aren't using proxies this might solve the issue for you.

Is this fixed?

This, or something similar, appears to be occurring to me using an HTTP proxy as well.

I'm having the same issue.  Is there a solution for this problem yet?  Thank you.

I'm having the same issue.  Is there a solution for this problem yet?  Thank you.


Include JsonTemplateLayout for log4j2

Purpose

Include JsonTemplateLayout for log4j2 [1]

related https://github.com/wso2-enterprise/choreo/issues/9223
[1] https://logging.apache.org/log4j/2.x/manual/json-template-layout.html

 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.


(BKR-1509) Hypervisor usage instructions for Beaker 4..0

Needs pin FaceFS for old ruby: Gem::InstallError: fakefs requires Ruby version >= 2.3.0.


Additional fields and resource-level description

This PR translates more of the eve fields to their corresponding swagger fields.
PR #15 is extended by adding resource-level description.
I renamed _type_and_format, because now more fields are set in this function.

thanks!


tests: disabling the aws dynamodb integration test

We are out of an AWS account to run integration tests on. Until we get a new account, we will disable AWS specific integration test.
Signed-off-by: Jiaxiao Zhou<EMAIL_ADDRESS>

/AzurePipelines run


Fix for CachePoolDeferTrait::save() return values

Seem to remember a long discussion about this, but the spec says this (and saveDeferred()) return bool.

Ping @Crell - just making sure you've seen this

Indeed, thanks for the ping.  (GitHub isn't notifying me unless I'm mentioned, because GitHub's notifications suck.)  Can you include a test for this?

Heya @Crell, here's the test. Any timescale for when cache-util will be available in packagist?


Cleaned up some cached variables after including benchmark

It's ugly but I tested this in the starling repo and it appears to solve our problem.


nodePackages.concurrently: init at 6.3.0

Motivation for this change
This PR adds the concurrently CLI tool to the nodePackages set!
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[X] x86_64-darwin
[ ] aarch64-darwin

[X] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

closed in favor of #144339


Bug fixes for users with partial privileges on apps:info

Waiting on @balansubr's okay before it's ready to merge.
@dickeyxxx are there any tests I should add?

nope, travis will take care of that

Looks good to me for now. If we get more customer feedback that some of these should not be displayed for users with view privilege, we will adjust then.

@dickeyxxx ready to merge


How do i change the payouts?

How do i change the payouts? Thank you in advance its a wonderful script!

https://github.com/TheIndra55/fivem-burglary/blob/master/burglary/houses.lua#L21


T480 Fixed with N24ET56W (1.31 ) BIOS ?

Hi,
I've recently updated BIOS on my T480 and i don't see any throttling-messages in "/var/log/messages" any more (and i was getting a lot of them). Also the throttling messages during system start are gone.
BIOS Information
Vendor: LENOVO
Version: N24ET56W (1.31 )
Release Date: 02/19/2020
BIOS Revision: 1.31
Firmware Revision: 1.20
I am on Fedora 31 and I've used fwupd for update.
Maybe someone could confirm this?

Maybe you can try to disable throttle fix (see README), reboot, and measure performance.

T480 on Ubuntu - not fixed with 1.31


style_transfer: explore stylize result image save to linux disk function

I need .style_transfer.create and see result and save stylize result image to disk. (not xcode,only linux)
I read python code and c code. I think this function want edit c.  "explore" function
I need this : stylized_images.save_stylized_image('/home/a/testResult/', format='jpg')
my try code .
model = tc.style_transfer.create(styles, content, max_iterations=maxInt)
test_images = tc.load_images('/home/a/test/')
stylized_images = model.stylize(test_images)
stylized_images.save('/home/a/test/1.csv',format='csv')
/*    stylized_images.show()
/*    stylized_images.explore()
stylized_images.save('/home/a/test/1.jpg', format='jpg')

The Turi Create image type does have a save method.
It looks like stylized_images is an SFrame. So you'll need to reference the entry you want and then call save on it. Something like the following should work:
stylized_images[0]['stylized_images'].save('/home/a/test/1.jpg')
I'm going to close this issue, but let me know if you have any more questions.

yes.CLOSE DIALOG please


Direct link to pre-selected items

Thank you for develop this nice streamlit component. Would it be possible to add support for getting direct link to pre-selected menu?
Relevant issues:
https://discuss.streamlit.io/t/direct-link-to-pre-selected-items/4817
https://github.com/streamlit/streamlit/pull/1169

Hi @giswqs, if I understood what you mean, letting users pre-select an option through a URL parameter is feasible in Streamlit, but in my opinion should be implemented at the app level, not the component level.
I would imagine doing something like the following:
Given a URL like http://localhost?selected_index=1
params = st.experimental_get_query_params()
selected = option_menu("Menu Title", ["option1", "option2"], default_index=int(params['selected_index'][0]))
if selected == "option1":
    # show the page for option1

Hi @giswqs, if I understood what you mean, letting users pre-select an option through a URL parameter is feasible in Streamlit, but in my opinion should be implemented at the app level, not the component level.
I would imagine doing something like the following:
Given a URL like http://localhost?selected_index=1
params = st.experimental_get_query_params()
selected = option_menu("Menu Title", ["option1", "option2"], default_index=int(params['selected_index'][0]))
if selected == "option1":
    # show the page for option1

Thanks for the suggestion. I was able to implement it.
https://share.streamlit.io/giswqs/streamlit-template


Create helpful database integration guide

Per #476, let's revise/replace http://expressjs.com/guide/database-integration.html to be more helpful, without delving into specifics of various ORMs.
From that issue:

what we need is documentation to show how to glue things together with Express. For example, perhaps someone has a Winston logger or a MySQL connection and they don't know what the best practices are for having these managed with a request/response life cycle and exposed to their routes.

@crandmck where is the source for that document? And can I contribute to it?

@vitaly-t It's just https://github.com/strongloop/expressjs.com/blob/gh-pages/en/guide/database-integration.md.

@crandmck thank you!
If I submit a PR to change the PostgreSQL integration via pg-promise, any chance it will be accepted?
The example would be simplified, and much more modern-looking.

We would certainly consider it.  Ultimately, it would be up to @dougwilson, but it sounds reasonable to me.

Thank you, I have just submitted it.

To clarify, based on comments from #476:

we need to show how to glue things together with Express. For example, perhaps someone has a Winston logger or a MySQL connection and they don't know what the best practices are for having these managed with a request/response life cycle and exposed to their routes. I think that's probably more useful from an Express point of view compared to the existing page.

Reading through the database guide, it's really just repeating how to use the various modules at a basic level without any express (or web application in general) specifics. I think a good addition would be around best practices when using a DB. A few things immediately come to mind:

don't create a new db connection for every request
closing the DB connection when your application shuts down

#522 was merged, and at this point the rest is out of scope.


NETOBSERV-666: K8s decoration not adding namespace if empty

This caused that empty-string and nil namespaces were treated differently in some metrics aggregations:

Codecov Report

Merging #335 (5b72965) into main (1d6ef70) will increase coverage by 0.15%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #335      +/-   ##
==========================================
+ Coverage   69.12%   69.28%   +0.15%
==========================================
  Files          86       86
  Lines        4907     4909       +2
==========================================
+ Hits         3392     3401       +9
+ Misses       1303     1293      -10
- Partials      212      215       +3

Flag
Coverage Δ

unittests
69.28% <0.00%> (+0.15%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/pipeline/transform/transform_network.go
69.01% <0.00%> (+5.44%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[SPARK-39295][PYTHON][DOCS] Improve documentation of pandas API suppo…

What changes were proposed in this pull request?

The description provided in the supported pandas API list document or the code comment needs improvement.
Also, there are cases where the link of the function property provided in the document is not connected, so it needs to be corrected.
Why are the changes needed?

To improve document readability for users and to link to the correct API document.
Does this PR introduce any user-facing change?

Yes, the "Supported pandas APIs" page has changed as below.

How was this patch tested?

Manually check the links in the documents & the existing doc build should be passed.

@HyukjinKwon The current 'supported API generation' function dynamically compares the modules of PySpark.pandas and pandas to find the difference. At this time, the inherited class is also aggregated, and the link is not generated correctly (such as CategoricalIndex.all()) because it does not match the pattern of each API document.
ex>

.../reference/pyspark.pandas/api/pyspark.pandas.CategoricalIndex.add_categories.html
    >> exists
.../reference/pyspark.pandas/api/pyspark.pandas.CategoricalIndex.all.html
    >> not exists

So, I thought about the options below:

Creates by excluding methods that exist in the parent class.

For example, in the list of CategoricalIndex class, the list of functions available by inheriting the Index function (methods of base class) is removed.

Includes all methods, and creates a document link to the parent class by identifying whether a document corresponding to the path of the parent class exists.

In my opinion, the part of "determining whether the corresponding document exists" seems to be difficult, and option 1 seems appropriate because the existing pandas documentation does not document all methods of the parent class. (ex> https://pandas.pydata.org/docs/reference/api/pandas.CategoricalIndex.categories.html?highlight=category)

Can one of the admins verify this patch?

@beobest2 I am fine with separating PRs. I can merge this one, and you can go ahead for a separate fix for the link problem.
I remember there are some options in Sphinx about inherited docs, e.g.) https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html#directive-option-automodule-members
From a cursory look, we can let the autosummary generate the inherited documentations and link it here (?). Maybe we can take a closer look at how they handled it.

@HyukjinKwon @itholic With a separate PR, I'd like to look into some options in Sphinx about inherited documents.
The title of the truncated PR has been corrected.

Merged to master.
@beobest2 would you mind creating a backport PR to fix https://github.com/apache/spark/blob/branch-3.3/python/docs/source/user_guide/pandas_on_spark/supported_pandas_api.rst too please?

@HyukjinKwon  I just have created a backport PR to branch-3.3 (https://github.com/apache/spark/pull/36748). Please check whether I did it right.

@beobest2, is there any progress on https://github.com/apache/spark/pull/36729#issuecomment-1141632078?

@HyukjinKwon I've been missing out because there have been some other workloads lately. I will be able to register for PR this week. I have created an issue here. (https://issues.apache.org/jira/browse/SPARK-39456)

Sure, thanks for tracking this.


Automatic workspace creation

The workspaces readme states:
A workspace is automatically created (and switched to) when you:

Create a new frame (with make-frame; bound to M-N by default).
Switch to a project using projectile-switch-project.

While these are the cases for the master branch, on the develop branch I only get an automatic workspace created upon a new frame -- switching to a project does not create and switch to a new workspace like it does on the master branch.

This is still the case on develop except if your current workspace is empty (e.g. only the scratch/dashboard buffer is left). Then it'll just change the project without creating a new workspace.

Oh, I should mention, you can also create workspaces with M-t, :tabnew [NAME] and SPC TAB n, by default.

If I try loading a project with projectile-switch-project in a workspace that is not empty I just get an error. Here's the backtrace:
Debugger entered--Lisp error: (wrong-type-argument perspective (((min-height . 4) (min-width . 109) (min-height-ignore . 3) (min-width-ignore . 109) (min-height-safe . 1) (min-width-safe . 2) (min-pixel-height . 124) (min-pixel-width . 1417) (min-pixel-height-ignore . 72) (min-pixel-width-ignore . 1417) (min-pixel-height-safe . 31) (min-pixel-width-safe . 26)) leaf (pixel-width . 3816) (pixel-height . 2085) (total-width . 294) (total-height . 67) (normal-height . 1.0) (normal-width . 1.0) (buffer "*doom*" (selected . t) (hscroll . 0) (fringes 0 0 nil) (margins 107) (scroll-bars nil 0 t nil 0 t) (vscroll . 0) (dedicated) (point . 1) (start . 1))))
  signal(wrong-type-argument (perspective (((min-height . 4) (min-width . 109) (min-height-ignore . 3) (min-width-ignore . 109) (min-height-safe . 1) (min-width-safe . 2) (min-pixel-height . 124) (min-pixel-width . 1417) (min-pixel-height-ignore . 72) (min-pixel-width-ignore . 1417) (min-pixel-height-safe . 31) (min-pixel-width-safe . 26)) leaf (pixel-width . 3816) (pixel-height . 2085) (total-width . 294) (total-height . 67) (normal-height . 1.0) (normal-width . 1.0) (buffer "*doom*" (selected . t) (hscroll . 0) (fringes 0 0 nil) (margins 107) (scroll-bars nil 0 t nil 0 t) (vscroll . 0) (dedicated) (point . 1) (start . 1)))))
  (or (and (memq (type-of persp) cl-struct-perspective-tags) t) (signal 'wrong-type-argument (list 'perspective persp)))
  (progn (or (and (memq (type-of persp) cl-struct-perspective-tags) t) (signal 'wrong-type-argument (list 'perspective persp))) (aref persp 1))
  (let* (persp-p (persp (let* ((default-directory +workspaces--project-dir) (project-name (doom-project-name 'nocache))) (or (setq persp-p (+workspace-get project-name t)) (+workspace-new project-name)))) (new-name (progn (or (and (memq (type-of persp) cl-struct-perspective-tags) t) (signal 'wrong-type-argument (list 'perspective persp))) (aref persp 1)))) (+workspace-switch new-name) (if persp-p nil (switch-to-buffer (doom-fallback-buffer))) (save-current-buffer (set-buffer (doom-fallback-buffer)) (setq default-directory +workspaces--project-dir)) (if current-prefix-arg nil (funcall +workspaces-switch-project-function +workspaces--project-dir)) (+workspace-message (format "Switched to '%s' in new workspace" new-name) 'success))
  (if (+workspace-buffer-list) (let* (persp-p (persp (let* ((default-directory +workspaces--project-dir) (project-name (doom-project-name 'nocache))) (or (setq persp-p (+workspace-get project-name t)) (+workspace-new project-name)))) (new-name (progn (or (and (memq (type-of persp) cl-struct-perspective-tags) t) (signal 'wrong-type-argument (list 'perspective persp))) (aref persp 1)))) (+workspace-switch new-name) (if persp-p nil (switch-to-buffer (doom-fallback-buffer))) (save-current-buffer (set-buffer (doom-fallback-buffer)) (setq default-directory +workspaces--project-dir)) (if current-prefix-arg nil (funcall +workspaces-switch-project-function +workspaces--project-dir)) (+workspace-message (format "Switched to '%s' in new workspace" new-name) 'success)) (save-current-buffer (set-buffer (switch-to-buffer (doom-fallback-buffer))) (setq default-directory +workspaces--project-dir) (message "Switched to '%s'" (doom-project-name 'nocache))) (if current-prefix-arg nil (funcall +workspaces-switch-project-function +workspaces--project-dir)))
  (unwind-protect (if (+workspace-buffer-list) (let* (persp-p (persp (let* ((default-directory +workspaces--project-dir) (project-name (doom-project-name 'nocache))) (or (setq persp-p (+workspace-get project-name t)) (+workspace-new project-name)))) (new-name (progn (or (and (memq (type-of persp) cl-struct-perspective-tags) t) (signal 'wrong-type-argument (list 'perspective persp))) (aref persp 1)))) (+workspace-switch new-name) (if persp-p nil (switch-to-buffer (doom-fallback-buffer))) (save-current-buffer (set-buffer (doom-fallback-buffer)) (setq default-directory +workspaces--project-dir)) (if current-prefix-arg nil (funcall +workspaces-switch-project-function +workspaces--project-dir)) (+workspace-message (format "Switched to '%s' in new workspace" new-name) 'success)) (save-current-buffer (set-buffer (switch-to-buffer (doom-fallback-buffer))) (setq default-directory +workspaces--project-dir) (message "Switched to '%s'" (doom-project-name 'nocache))) (if current-prefix-arg nil (funcall +workspaces-switch-project-function +workspaces--project-dir))) (setq +workspaces--project-dir nil))
  (progn (unwind-protect (if (+workspace-buffer-list) (let* (persp-p (persp (let* ((default-directory +workspaces--project-dir) (project-name (doom-project-name 'nocache))) (or (setq persp-p (+workspace-get project-name t)) (+workspace-new project-name)))) (new-name (progn (or (and (memq (type-of persp) cl-struct-perspective-tags) t) (signal 'wrong-type-argument (list 'perspective persp))) (aref persp 1)))) (+workspace-switch new-name) (if persp-p nil (switch-to-buffer (doom-fallback-buffer))) (save-current-buffer (set-buffer (doom-fallback-buffer)) (setq default-directory +workspaces--project-dir)) (if current-prefix-arg nil (funcall +workspaces-switch-project-function +workspaces--project-dir)) (+workspace-message (format "Switched to '%s' in new workspace" new-name) 'success)) (save-current-buffer (set-buffer (switch-to-buffer (doom-fallback-buffer))) (setq default-directory +workspaces--project-dir) (message "Switched to '%s'" (doom-project-name 'nocache))) (if current-prefix-arg nil (funcall +workspaces-switch-project-function +workspaces--project-dir))) (setq +workspaces--project-dir nil)))
  (if (and persp-mode +workspaces--project-dir) (progn (unwind-protect (if (+workspace-buffer-list) (let* (persp-p (persp (let* ((default-directory +workspaces--project-dir) (project-name (doom-project-name 'nocache))) (or (setq persp-p (+workspace-get project-name t)) (+workspace-new project-name)))) (new-name (progn (or (and (memq (type-of persp) cl-struct-perspective-tags) t) (signal 'wrong-type-argument (list 'perspective persp))) (aref persp 1)))) (+workspace-switch new-name) (if persp-p nil (switch-to-buffer (doom-fallback-buffer))) (save-current-buffer (set-buffer (doom-fallback-buffer)) (setq default-directory +workspaces--project-dir)) (if current-prefix-arg nil (funcall +workspaces-switch-project-function +workspaces--project-dir)) (+workspace-message (format "Switched to '%s' in new workspace" new-name) 'success)) (save-current-buffer (set-buffer (switch-to-buffer (doom-fallback-buffer))) (setq default-directory +workspaces--project-dir) (message "Switched to '%s'" (doom-project-name 'nocache))) (if current-prefix-arg nil (funcall +workspaces-switch-project-function +workspaces--project-dir))) (setq +workspaces--project-dir nil))))
  +workspaces|switch-to-project()
  run-hooks(projectile-after-switch-project-hook)
  projectile-switch-project-by-name("~/.config/" nil)
  #f(compiled-function (project) #<bytecode 0x20bc24d>)("~/.config/")
  ivy-call()
  ivy-read("[bloom] Switch to project: " ("~/.config/doom/" "~/.emacs.d/" "~/.config/") :initial-input nil :action #f(compiled-function (project) #<bytecode 0x20bc24d>) :caller projectile-completing-read)
  projectile-completing-read("Switch to project: " ("~/.config/doom/" "~/.emacs.d/" "~/.config/") :action #f(compiled-function (project) #<bytecode 0x20bc24d>))
  projectile-switch-project(nil)
  funcall-interactively(projectile-switch-project nil)
  call-interactively(projectile-switch-project nil nil)
  command-execute(projectile-switch-project)

Found and fixed in bd7f1f6. Let me know if that fixes the error!

This does fix the error it seems. Thanks for that. Back to the original topic, would it at all be possible to make the functionality present in the master branch as an option, or has the code diverged too much to support that? I find it really cumbersome that I can't open a new Emacs session, open a project, and have a fresh perspective to work in, as I like to keep the default workspace for temporary non-project stuff.

@hlissner Mostly because then I have to rename it and suddenly I have a few operations to remember that I got for free with master. Oh well, worth a try :)

Ah, fair enough! I’ll look into adding such an option in the morning.
On Aug 29, 2018, 2:30 AM +0200, Michael Fiano<EMAIL_ADDRESS>wrote:

@hlissner Mostly because then I have to rename it and suddenly I have a few operations to remember that I got for free with master. Oh well, worth a try :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

6515efa adds the +workspaces-on-switch-project-behavior option. Set it to t to have it always create a new workspace when switching projects. Let me know if you have trouble with it and I'll reopen this.


Replace asset-url with url in Sass files

Both Sprockets and Propshaft will replace url with a digested version [1]. This change allows to use these Sass files with other Sass implementations like, Dartsass [2].
This also helps with: https://github.com/railsadminteam/rails_admin/issues/3697.
[1] https://github.com/rails/dartsass-rails/issues/18#issuecomment-1113972661
[2] https://github.com/rails/dartsass-rails

This failing test seems to be unrelated: https://github.com/railsadminteam/rails_admin/actions/runs/10770743198/job/29864748939.
This is probably also unrelated but it seems to be flaky: https://github.com/railsadminteam/rails_admin/actions/runs/10770743198/job/29864751251. It passed in my fork: https://github.com/jacob-carlborg-apoex/rails_admin/actions/runs/10770737339/job/29864729789.

Note: support for url was added from sprockets-rails 3.3.0.
https://github.com/rails/sprockets-rails/pull/476


Refactor wallet to create encrypted wallet with wif

change wallet format to include wif and single public key
wallet to create encrypted wallet with password

done now - this was split into 2 parts
the wallet format was changed in #70
and the wallet encryption was done in #73


New Parser and Analyzer support BACKUP and RESTORE related statements【Easy】

Requirement Description
The new Parser and the new Analyzer support BACKUP、RESTORE related statements
Mentor
@HangyuanLiu
Registration procedure
Step 1. Add a comment when you sign up. The comment can be a brief self-introduction and reason for signing up, including what you do, what you're good at, what you're interested in and your technology stack, and how familiar you are with StarRocks. Example:

I pick! My name is Johnny. I am from StarRocks and I have been working on database kernel development for 1 year. I am interested in OLAP, good at C++ programming, and have been using StarRocks for 6 months. I chose to solve this issue because I am familiar with execution engine.

Step 2. On your WeChat, add the StarRocks community assistant "StarRocks-1" as a WeChat friend and leave your GitHub ID. The assistant will invite you to a WeChat group based on the issue you picked.
Step 3. The mentor will communicate with all the participants who picked this issue and assign the task to the best match.
Before you start

Read the StarRocks GitHub workflow carefully, which provides the configurations of BE and FE and describes how to submit a pull request.
To learn more about StarRocks, read StarRocks documentation.

Pull request requirements

After you complete code development, upload the code to the StarRocks code repo as a pull request (PR).

PR title format: [SR GeekCamp] + PR title
Labels ：[Geek Camp 2022/feature]

After you submit your PR, comment on the status of your PR submission as requested under the Pinned Issue [StarRocks geek Camp 2022] page.

Comment format: "I have finished Issue #" + PR link id

I pick! My name is Xuqing Chai. I am a postgraduate student from BUPT. I have been learning on database kernel development for 1 year.  I have studied CMU 15-445 and MIT6.824, and I have read part of the source code of LevelDB. I'm currently studying CMU15-712, the main content of this course is reading VLDB papers. I am interested in OLAP, good at C++ programming, but have been using StarRocks. I chose to solve this issue because I want to contribute for StarRocks.


Having Difficulties running the program in windows

I have installed both FFmpeg and MinGW.
I have tried running the program on windows but it is still not working.
I have gotten an error in the src folder (main.cpp) under time(NULL).
If you don't mind, would you please make a screen record of how you can run the program in windows and genenerate the GIFS.
Even if its just recording without any sound (screen recording).
You may upload to youtube then please share the link here.
I'll really appreaciate your help and make a donation.

U need to add this line on top of main.cpp and metadatafunction.cpp: " include " or u can redownload the repository i fixed this

Redownload the repository i fixed this

And write me on discord, there i'm faster in responding ti u


Maximum call stack exceeded. This error occured when using rowsgroup plugin.

First time when the data is generated with Data parameter the DataTable & rowsGroup loads perfectly. When I make a ajax call to get new Data for the DataTable, I do ".clear()" & ".destroy()" and repopulate the DataTable. But my page Hangs and I face this error "Maximum call stack size exceeded". After 5-10 secs the DataTable loads with the new data and rows group modifications. I have tried with all possbile solutions but getting the same Error.
Hoping for a reply.

I have the exact same issue. Are you by any chance using the SmartAdmin template?

I've experienced the same issue here. At last, I found a way to bypass it. Simply avoid destroying the table if you can. Rather you clear the table and use the rows.add().draw() to update the content. In a word, keep the table instance unchanged but refresh its data.

Yes. This is known defect in plugin. I discovered it before the first release but used the plugin only for one table without any reinit. This should be fixed soon (I expect so)

When will futpib's commits be merged into master? His fix for this works for me.
https://github.com/ashl1/datatables-rowsgroup/pull/11

#11 Works for me too. In particular, I'm using the destroy:true option, and now it's working fine.

@ashl1 Hello, I really liked the plugin, to destroy the table you can include this code, for those who work with ajax.
$(document).on( 'destroy.dt', function ( e, settings ) {
var api = new $.fn.dataTable.Api( settings );
api.off('order.dt');
api.off('preDraw.dt');
api.off('column-visibility.dt');
api.off('search.dt');
api.off('page.dt');
api.off('length.dt');
api.off('xhr.dt');
});

@ashl1 Hello, I really liked the plugin, to destroy the table you can include this code, for those who work with ajax.
$(document).on( 'destroy.dt', function ( e, settings ) {
var api = new $.fn.dataTable.Api( settings );
api.off('order.dt');
api.off('preDraw.dt');
api.off('column-visibility.dt');
api.off('search.dt');
api.off('page.dt');
api.off('length.dt');
api.off('xhr.dt');
});

it works

Thanks mutaqin07.
On Wednesday, February 19, 2020, 01:32:30 PM GMT+5:30, mutaqin07<EMAIL_ADDRESS>wrote:
@ashl1 Hello, I really liked the plugin, to destroy the table you can include this code, for those who work with ajax.
$(document).on( 'destroy.dt', function ( e, settings ) {
var api = new $.fn.dataTable.Api( settings );
api.off('order.dt');
api.off('preDraw.dt');
api.off('column-visibility.dt');
api.off('search.dt');
api.off('page.dt');
api.off('length.dt');
api.off('xhr.dt');
});
it works
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

futpib's fix is work, why still not merge it into master ??


images: accumulate image data across multiple lines

What were you trying to do?
ImageData can contain valid newlines (\xA0) which we need to preserve. They're raw bytes but when we read as ASCII/EBCDIC those characters are interpreted as separate lines.
This sometimes causes errors like: invalid record type: m which is pretty confusing at first.
What did you expect to see?
Valid files parse correctly for all usecases. Images can be extracted from valid files.

A couple solutions after talking with Matt C in slack.

Accumulate strings when we're parsing ImageViewData records across newlines. This would probably need access to the original bufio.Scanner.
Read the entire file byte by byte and buffer strings where the buffer knows ImageViewData's specific case of multi-line buffering.


Could not read serialized diagnostics file: error("Invalid diagnostics signature")

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[x ] I have read the wiki page and cheat sheet, but there is no information I need.
[ x] I have searched in existing issues, but did not find a same one.
[x ] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
What
Swift UI Projects no longer building with Kingfisher
[Tell us about the issue]
Unable to build SWift UI projects with KIngfisher Could not read serialized diagnostics file: error("Invalid diagnostics signature") (in target 'Quiz' from project 'Quiz')
Command CompileSwift failed with a nonzero exit code
Reproduce
[The steps to reproduce this issue. What is the url you were trying to load, where did you put your code, etc.]
Install King Fisher using Package manager or cocapods
Try to build - get this error: Could not read serialized diagnostics file: error("Invalid diagnostics signature") (in target 'Quiz' from project 'Quiz')
Command CompileSwift failed with a nonzero exit code

It is likely an issue in Kingfisher or can be solved here. Maybe try to

Perform a clean
Close all unnecessary tabs
Reboot Xcode or macOS
Update to use the latest Xcode/CocoaPods
and other things might be related.

I am closing it since there won't be more we can help...


fix: route all unknown web content requests to index.html

Untested.
Fixes: #2103

 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.

@sarabala1979 @alexec seems like you would know more about this part of the code

By way of explanation:
Anything that has a "." in it, and that is not an actual asset with staticfiles, is treated as a file not found. This routes them all through to index.html. I've tested this and it fixes things for me.

LGTM


Data source type Variable support

Variable Plugin is very usefull in many different dashboards, i have case there users should select needed datasource before reading data and would be very usefull if they could do with this plugin, as then you can put selection in any place you want instead of sticking on top .

@Nesweikas Thank you for the feature request. We will add in the next version.

@vitPinchuk Please open an issue in the grafana/grafana repository with description of the Grafana Scenes values issue.

https://github.com/grafana/grafana/issues/98032


[DO NOT MERGE] WIP: Moving client from kubernetes to client-go

Partially fixes #318
Signed-off-by: André Martins<EMAIL_ADDRESS>

This change is

Waiting on https://github.com/kubernetes/client-go/issues/28


lidar sensor time of flight

Hi,
could you please tell me how to calculate the time of flight of lidar sensor signals?
It is also possible to compute time of flight of signal by calculating the distance between the hit point and the sensor? How to calculate the distance then?

Hi @NurbekHalikulov I can see that you asked your question on Discord as well, is everything clear for you now?


Adopt VS Code's 'asWebviewUri' API

Hi, I maintain VS Code's Webview API
Issue
Our telemetry suggests that your extension uses webviews and may be loading resources in these webviews using hardcoded vscode-resource: URIs. These URIs have some important limitations and don't work properly when VS Code is run in a browser. We are also making changes in the desktop version of VS Code that may cause these URIs to not work properly in future versions of VS Code.
While we are making our best effort to continue support existing webview extensions that use vscode-resource: URIs on desktop versions of VS Code, we will not able to fully support all uses cases.
Fix
To ensure that your extension continues to work in as many environments as possible—including on web and remotely—please:

Switch to use the Webview.asWebviewUri function for loading resources.

Switch to use the Webview.cspSource property in content security policies.

These APIs shipped around 2 years ago so they should be available in all modern versions of VS Code. You can find additional information about the issue here: https://github.com/microsoft/vscode/issues/97962
Let me know if you have any questions about this change

Hi @mjbvz,
I am developing with vscode ^1.1.33 where this API was not available. Can you tell me from which version this api is available?


fix: add retry to firecracker connect

In some cases, we fail the initial connect to Firecracker, seemingly due to a race during VM startup. This adds retries to the connect method where we bail out attempting to read bytes if we get nothing back within 10 milliseconds (by default). We then create a new stream and try again. We'll do this up to 30 times before bailing out completely.