incorrectly disallows in expressions in function-bodied arrows in for statement initialisers

Steps to reproduce
esprima.parse('for(()=>{a in b};;);')

Expected output
Script {
  type: 'Program',
  body:
   [ ForStatement {
       type: 'ForStatement',
       init:
        ArrowFunctionExpression {
          type: 'ArrowFunctionExpression',
          id: null,
          params: [],
          body:
           BlockStatement {
             type: 'BlockStatement',
             body:
              [ ExpressionStatement {
                  type: 'ExpressionStatement',
                  expression:
                   BinaryExpression {
                     type: 'BinaryExpression',
                     operator: 'in',
                     left: Identifier { type: 'Identifier', name: 'a' },
                     right: Identifier { type: 'Identifier', name: 'b' } } } ] },
          generator: false,
          expression: false,
          async: false },
       test: null,
       update: null,
       body: EmptyStatement { type: 'EmptyStatement' } } ],
  sourceType: 'script' }

Actual output
Error: Line 1: Unexpected token in
    at ErrorHandler.constructError (/home/lydell/forks/esprima/dist/esprima.js:5045:22)
    at ErrorHandler.createError (/home/lydell/forks/esprima/dist/esprima.js:5061:27)
    at Parser.unexpectedTokenError (/home/lydell/forks/esprima/dist/esprima.js:1990:39)
    at Parser.throwUnexpectedToken (/home/lydell/forks/esprima/dist/esprima.js:2000:21)
    at Parser.consumeSemicolon (/home/lydell/forks/esprima/dist/esprima.js:2295:23)
    at Parser.parseLabelledStatement (/home/lydell/forks/esprima/dist/esprima.js:4058:19)
    at Parser.parseStatement (/home/lydell/forks/esprima/dist/esprima.js:4151:97)
    at Parser.parseStatementListItem (/home/lydell/forks/esprima/dist/esprima.js:3412:31)
    at Parser.parseFunctionSourceElements (/home/lydell/forks/esprima/dist/esprima.js:4224:29)
    at Parser.parseAssignmentExpression (/home/lydell/forks/esprima/dist/esprima.js:3304:56)

Relevant references
shapesecurity/shift-parser-js#348

@lydell If this is urgent and if you can't wait until @ariya have solved this bug, you can solve it yourself if you replace this line with this code.
let body;
if ( this.match('{')) {
    const previousAllowIn = this.context.allowIn;
    this.context.allowIn = true;
    body = this.parseFunctionSourceElements();
    this.context.allowIn = previousAllowIn;
} else {
    body = this.isolateCoverGrammar(this.parseAssignmentExpression);
}

@nowindowsowrking, any chance you can submit a PR with the fix and some new tests? It seems like you have a good grasp of the codebase, we'd appreciate some more solid contributions to the codebase.

@mikesherov I will open a new thread in the mailing list. We can discuss there. Because I discovered a lot of things that I need to understand before I can move on to PR etc.

I don't get it? Didn't you just post a fix for this issue in a comment above? I'm not asking you to rewrite the entire codebase, I'm just wondering if you'd like to submit a patch to fix bug being reported.

@mikesherov I posted a fix yes, but at ATM I can't post a PR from my computer used in my office work. No plans to rewrite the code base, but fixing that led me to other issues. So I decided to go for an solution that solve all open issue tickets if possible. In that case I got questions.

So I decided to go for an solution that solve all open issue tickets if possible.

Your PR is not likely to be accepted if it is too large and attempts to fix too many things at once. As I mentioned before, if you'd really like to help out, filing specific bugs and submitting PRs for those gives us a chance to review the code in isolation and establishs trust and helps us all set a path forward together.
In the case that you feel you can speed up the scanner class, please do so! File a bug, explain how you intend on addressing it, post benchmarks, and fix.
Large scale all at once rewrites are not likely to be accepted.

That was one of the point why I asked something on the mailing list. Getting an overview and take things step by step. Offering a giant PR gains nothing. Unseen bugs will allways occur even you want or not if you do that. So my idea was just to get a understanding and hear the thoughts from the people and take it from there.  I also noticed @ariya like to have a issue ticket first before any PR.

@mikesherov @ariya I managed to make a PR, but discovered that this build system is not compat with Windows. So when I tried to create a test, I couldn't. Or I could, but had too do it manually. And also location tracker data differs from a Unix / Mac based computer vs a Windows computer. This related to mostly all Expression tests. At least on my laptop with windows 10.
So I then ignored that, but still couldn't create an test. Further. Paths issues as well on Windows and some other crazy things.
Too much hassle for me this one. So I'm back to only reporting issues. Good luck with Esprima!

It's not true that Windows can't be used for Esprima development (I'm myself using a ThinkPad). We even have a CI run for Windows, see such an output at e.g. https://ci.appveyor.com/project/ariya/esprima/build/557, including running test suite with IE 11.

@ariya Ok. I believe you!  After cloning the repo and installed the depenencies, I tried this first:
npm run test and ended up with

><EMAIL_ADDRESS>check-version C:\xampp4\htdocs\esprima
> node test/check-version.js

Getting the canonical library version...
Library version is 4.0.0-dev
Checking package.json ...

><EMAIL_ADDRESS>tslint C:\xampp4\htdocs\esprima
> tslint src/*.ts

><EMAIL_ADDRESS>code-style C:\xampp4\htdocs\esprima
> tsfmt --verify src/*.ts && tsfmt --verify test/*.js

src/*.ts does not exist. process abort.

No .ts file found. But at least 94 tests was running from the api test. No fixtures. Other errors is that the fixture.js in dist folder is not found. Not sure if there should be any fixture.js in the dist folder, or if the path is wrong.  Anyway. I gave it up.

From the grammar:
ConciseBody[In]:
    [ lookahead ≠ { ]  AssignmentExpression[?In, ~Yield, ~Await]
    {  FunctionBody[~Yield, ~Await]  }

Apparently, [In] for the first production is conditional, while it's not the case for the second one.
The root cause of the problem is because currently Esprima parser does not handle the second production correctly.


configuration supports node.js best-practices

[ ] Remove non-configuration functions from static/js/config.js into separate component(s)
[ ] Evaluate use of npm configuration libraries rc, nconf and config

For background, see config guide
This is a new incarnation of LD4P/bfe#3, which is itself a new incarnation of sul-dlss/bfe#3

No longer necessary.


TRIVIAL: add the option to remove search

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-docs-theme-oss-check/55/ : SUCCESS in 3s


Pamtbaau/feature translations

Features:

All text returned by server to front-end is being translated.
Admin menu is being translated.
All text (labels, messages, alerts) is being translated.
Table of changed items is replaced with Grid
Add log when issue at server
Move creating of header of list from Twig to TS/JS

Fix:

Prevent clearing input fields and ability to submit items when error was returned.
Fix npm dependency with vulnerability

Thanks!
I think ae71de0 may have broken the list display:

It's a really good change as I have also thought that the empty list with headings looked wrong. However I can no longer see any items that have changed.
A couple of related points:

it would be good to also hide the change summary field when there are no changed items and maybe show a message (translated of course!) similar to: "There are no changes to display. Make some edits to see changes listed here."
when I make a rename (as per the screenshot), it shows up as two changes in the menu "badge" but only one is displayed. It would be ideal (but probably difficult) to count renames here as a single change to be consistent. Otherwise I think it's potentially confusing for users. This is a minor UI bug.

It's a really good change as I have also thought that the empty list with headings looked wrong.

Lost of header when list is empty was unintentionally... Yes, both the absence of the header and empty list looks off.

However I can no longer see any items that have changed.

Don't you seen any changed items while there have been Git changes????

it would be good to also hide the change summary field when there are no changed items and maybe show a message (translated of course!) similar to: "There are no changes to display. Make some edits to see changes listed here."

I agree

when I make a rename (as per the screenshot), it shows up as two changes in the menu "badge" but only one is displayed. It would be ideal (but probably difficult) to count renames here as a single change to be consistent. Otherwise I think it's potentially confusing for users. This is a minor UI bug.

It's the server that sees the rename as 2 while TS does not and sets the correct count. However, when user is not on Pushy page, TS does not run and will not update the incorrect value set by server.
Will look into that.


[FLINK-12539][Connectors / FileSystem] StreamingFileSink: Make the class customizable

What is the purpose of the change
Provide mechanisms to extend the StreamingFileSink class and make it customizable
Brief change log

Provide mechanisms to extend the StreamingFileSink class and make it customizable

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @tweise @tillrohrmann Looks like I don't have permission to add you as reviewers on the PR itself.

I am not sure what "Join list" means.


Fix broken link

You could put a link like https://www.binance.com/en/crypto/buy/EUR/XMR, but I don't like this approach, because the URL might break again in the future, it forces the English language in the URL, and you have to pick a currency.

would like this closed in favor of #2223
@jorgesumle please see #2223

I agree!


Proposal - Add "tags" ability to migrator

The migrations feature of laravel is one of my favorite features, however its tightly coupled to a none extensible application.
Consider an "app" built with the idea of "plugins" (seperate to packages, these could be user installed, not developer), the app wont know anything about these plugins at any point, currently meaning any plugins seperate from the core need to setup there own migrations for db interaction.
what would be great is if we could "tag" migration locations.
this way we "tag" migration locations for anything, not just plugins.
we could turn php artisan migrate into php artisan migrate --tag=1,2,etc, or all
all we need to do is add a column to the migrations table called "tag", then have a function on the migrator to register a tag location:
Migrator::tag('myplugin', __DIR__ . '/migrations');

if we run php artisan migrate it would just run migrations from the current migrations location
but if we run php artisan migrate --tag=myplugin it would just run migrations from the registered location and add the tag name to db for that migration, or php artisan migrate --tags to migrate every location.
this way we could have divergent migration history, so if we wanted to delete "myplugin" we could rollback just the plugins migrations without effecting the core apps migrations.
it would also be imo better for current packages, they wouldnt need to "publish" migrations poluting the apps migrations, they could just register a "tagname" and location.
Then when a package is updated instead of:

the command to update the package would just be ```php artisan migrate --tag=tagname```, or more simply: ```php artisan migrate --tags``` to update everything.

happy to work on this if its useful to the core.

If not can i request a contract for ```Illuminate\Database\Migrations\Migrator``` so we can at least overwrite the core implementation?

Sorry to put a damper on this, but we don't process proposals on GitHub, as per our contribution guidelines.
I also think this has already been proposed and rejected about a year ago, or something.

understand the proposal thing, noted for future.
however doesnt the current migrator have effectivley a bug when using the --path option?
say you run php artisan migrate --path=.....
then you run php artisan migrate:rollback
this will fail because it cant find the last migration as it was from a custom path and the rollback command doesnt have a path option, plus even if it did you would have to remmeber the order in which you migrated, nullifying the benefit of migrations?
its a tricky situation i know because to just remove it would cause BC but its current implementation fails with the feature set it has?

It really just depends on what the implementation looks like and if it will be a pain to maintain or not. You can give it a shot if you want.

@GrahamCampbell since proposals aren't done on github, where can one go on slack to find all discussion about proposals and their resolutions.

@GrahamCampbell since proposals aren't done on github

Taylor has changed this policy now, starting from the day after I closed this. :0

It's fine to discuss this here, at least for now.

@GrahamCampbell thanks for the info :)

Sorry, we don't process requests/proposals here. Please see https://github.com/laravel/internals/issues.

Just a quick note, that our policy has now changed again.


updated test cases to support db upgrade in #2476

Description (required)
Fixes  #2476
What changes did you make and why?
Updated test cases to support db upgrade.
Tests performed (required)
Tested {ProdDebug} on {Google Pixel} with API level {API 27}.

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.10-release@cd145ef). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             2.10-release   #2497   +/-   ##
==============================================
  Coverage                ?    5.8%
==============================================
  Files                   ?     256
  Lines                   ?   12223
  Branches                ?    1095
==============================================
  Hits                    ?     710
  Misses                  ?   11456
  Partials                ?      57

Continue to review full report at Codecov.

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


How to disable request logging

[info] [73, 110, 118, 97, 108, 105, 100, 32, 111, 112, 116, 105, 111, 110, 32, [123, ['proxy', 44, [123, ['"<IP_ADDRESS>"', 44, '13150'], 125]], 125], 32, 105, 103, 110, 111, 114, 101, 100, 32, 10]

I am using proxy with httpc and for every reuqest I see this. I tried implementing custom Tesla.Middleware.RequestLogger but it doesn't go away. I also tried setting plug Tesla.Middleware.Logger, log_level: &my_log_level/1 to only errors but it doesn't work.
How can I disable request logging? Or set it to :error only?

Are you sure this comes from Tesla?
On 5 Mar 2019, 23:16 +0100, jan0991<EMAIL_ADDRESS>wrote:

[info] [73, 110, 118, 97, 108, 105, 100, 32, 111, 112, 116, 105, 111, 110, 32, [123, ['proxy', 44, [123, ['"<IP_ADDRESS>"', 44, '13150'], 125]], 125], 32, 105, 103, 110, 111, 114, 101, 100, 32, 10]
I am using proxy with httpc and for every reuqest I see this. I tried implementing customTesla.Middleware.RequestLoggerbut it doesn't go away. I also tried settingplug Tesla.Middleware.Logger, log_level: &my_log_level/1` to only errors but it doesn't work.
How can I disable request logging? Or set it to :error only?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for getting back to me so fast. Yep it very likely wasn't tesla but httpc. It also didn't use the proxy properly. Replacing it with hackney fixed both issues.


Removing options property from loaderAPI

In webpack 4, loaderAPI.options is null resulting in the following error...
TypeError: Cannot read property 'context' of undefined
    at Object.module.exports (/node_modules/twig-loader/lib/loader.js:25:63)

Although this wouldn't be supported on webpack < 4.

I don't think this change is correct. See #50 and #51.


Failing to create oneview_enclosure_group resources with interconnectBayMappings in v2.10.0

Scenario/Intent
Trying to create a oneview_enclosure_group with interconnectBayMappings.
Environment Details

Puppet module for HPE OneView Version: v2.10.0
OneView SDK Version: 5.17.0
OneView Appliance Version:  5.50.00-0426657
OneView Client API Version: 1200
Puppet Version: 5.5.17
Ruby Version: 2.4.5
Platform: Oracle Linux Server 7.7

Steps to Reproduce
Create a oneview_enclosure_group resource like in the examples.
oneviewconf::oneview::logical_interconnect_groups:
  LIG_01:
    ensure: present
    data:
      name: LIG_01
      enclosureType: SY12000
      consistencyCheckingForInternalNetworks: ExactMatch
      interconnectBaySet: 3
      enclosureIndexes:
      - 1
      redundancyType: Redundant
      interconnects:
      - bay: 6
        type: Virtual Connect SE 40Gb F8 Module for Synergy
        enclosure_index: 1
      - bay: 3
        type: Virtual Connect SE 40Gb F8 Module for Synergy
        enclosure_index: 1

oneviewconf::oneview::enclosure_groups:
  Enclosure_Group_Example:
    require: Oneview_logical_interconnect_group[LIG_01]
    ensure: present
    data:
      name: Enclosure_Group_Example
      stackingMode: Enclosure
      interconnectBayMappingCount: 2
      enclosureCount: 1
      interconnectBayMappings:
      - interconnectBay: 3
        logicalInterconnectGroupUri: LIG_01
      - interconnectBay: 6
        logicalInterconnectGroupUri: LIG_01

Expected Result
Creation of a oneview_enclosure_group resource.
Actual Result
See Error Message:
Notice: /Stage[main]/Oneviewconf::Oneview/Oneview_logical_interconnect_group[LIG_01]/ensure: created
Error: /Stage[main]/Oneviewconf::Oneview/Oneview_enclosure_group[Enclosure_Group_Example]: Could not evaluate: undefined method `[]' for nil:NilClass

Quick fix
The example worked for me in version v2.9.0. So the error must have come from new changes in v2.10.0.
In the oneview_enclosure_group provider  were some changes. See the following.
      lig_name = mapping_attr['logicalInterconnectGroupUri'] if mapping_attr['logicalInterconnectGroupUri']
      lig = OneviewSDK.resource_named(:LogicalInterconnectGroup, api_version, resource_variant).find_by(@client, name: lig_name)
      mapping_attr['logicalInterconnectGroupUri'] = lig.first['uri']

This code tries to to parse the logicalInterconnectGroupUri parameter but this is already done in the parent provider.
https://github.com/HewlettPackard/oneview-puppet/blob/9adeeacb0d333864b75946fb88c76a732251090c/lib/puppet/provider/oneview_resource.rb#L68
I printed out what the @data variable looks like at the beginning of the data_parse function in the oneview_enclosure_group provider. See the following.
{"name"=>"Enclosure_Group_Example",
 "stackingMode"=>"Enclosure",
 "interconnectBayMappingCount"=>2,
 "enclosureCount"=>1,
 "interconnectBayMappings"=>
  [{"interconnectBay"=>3,
    "logicalInterconnectGroupUri"=>
     "/rest/logical-interconnect-groups/7b24e8c5-e4f8-429d-88f1-641dac2c5503"},
   {"interconnectBay"=>6,
    "logicalInterconnectGroupUri"=>
     "/rest/logical-interconnect-groups/7b24e8c5-e4f8-429d-88f1-641dac2c5503"}]}
Error: /Stage[main]/Oneviewconf::Oneview/Oneview_enclosure_group[Enclosure_Group_Example]: Could not evaluate: undefined method `[]' for nil:NilClass

As you can see the parsing is already done and the data_parse function in the oneview_enclosure_group provider is not necessary. So I deleted that function completly and it worked. See the output.
Info: Performing create of EnclosureGroup Enclosure_Group_Example using the following data:
{
  "name": "Enclosure_Group_Example",
  "stackingMode": "Enclosure",
  "interconnectBayMappingCount": 2,
  "enclosureCount": 1,
  "interconnectBayMappings": [
    {
      "interconnectBay": 3,
      "logicalInterconnectGroupUri": "/rest/logical-interconnect-groups/7b24e8c5-e4f8-429d-88f1-641dac2c5503"
    },
    {
      "interconnectBay": 6,
      "logicalInterconnectGroupUri": "/rest/logical-interconnect-groups/7b24e8c5-e4f8-429d-88f1-641dac2c5503"
    }
  ]
}.
Notice: /Stage[main]/Oneviewconf::Oneview/Oneview_enclosure_group[Enclosure_Group_Example]/ensure: created

This SDK has limited support and will not be actively developed for the foreseeable future.


Extensions not working after upgrade to 1.47.1

Hi,
I'm running vscode version 1.47.1. It looks that after upgrade all my extensions not working anymore. All extensions are failing with the similar error:
Activating extension 'vscode-icons-team.vscode-icons' failed: The "path" argument must be of type string. Received type undefined.
Any suggestions?

Looks like #102180

Seems so, yes

I have the same problem too. Rollback to 1.46.1 everything works fine.

Probably a duplicate of #102082
Please follow this comment https://github.com/microsoft/vscode/issues/102082#issuecomment-657804049.
We made a fix and released new stable 1.47.1. Can you please update and try ?

Just updated to the new version 1.47.2, but still getting the same, Also it seems that problem exists only when i run vs-code as admin user. Checked the %appdata%\code\user  extensions.json file is not exist there.

/duplicate
#102686


Left and Right Swiping

Is there any option for left and right swiping at same time like this example? If there is how can I achieve that?

I am currently modify this feature in this branch. You can try this branch if you want.
https://github.com/hydrated/SwipeRevealLayout/tree/feature/multiple_dragedges

Hi I want LEFT and RIGHT swiping, I have used your link but it did not found, will you please add it again

Hi TeodorKolev, do you have solution then please send me, I am so much thankful to you


Small Training Dataset

Since the tokenization on all the dataset takes a lot of time, I have decided to create a small dataset with only 10-20 of the json.gz files. Once training starts, it gives the following error. Is it because the tokenization/BPE have not seen this character?
File "/CodeGen/codegen_sources/model/train.py", line 701, in <module> main(params) File "/CodeGen/codegen_sources/model/train.py", line 609, in main trainer.mlm_step( File
"/CodeGen/codegen_sources/model/src/trainer.py", line 1005, in mlm_step show_batch( File
"/CodeGen/codegen_sources/model/src/utils.py", line 74, in show_batch f"{label} sent:
{restore_segmentation_sentence(source_sentence, roberta_mode)}" File "/CodeGen/codegen_sources/model/src/utils.py",
line 563, in restore_segmentation_sentence return restore_roberta_segmentation_sentence(sentence) File
"/CodeGen/codegen_sources/model/src/utils.py", line 601, in restore_roberta_segmentation_sentence res =
bytearray([byte_decoder[c] for c in text]).decode("utf-8", errors="replace") File
"/CodeGen/codegen_sources/model/src/utils.py", line 601, in <listcomp> res = bytearray([byte_decoder[c] for c in
text]).decode("utf-8", errors="replace") KeyError: '郞'

It seems like some tokens can make RoBERTa's detokenizer crash. I pushed a fix that will make it output a null token instead of this character when this happens.
note: RoBERTa's tokenizer was created for natural languages. The advantage versus our tokenizer is that you can feed it code in any programming languages easily. The disadvantage is that you won't remove some tokens that don't change the semantics of the code (e.g. newlines in java and C++) and that your BPE and vocab won't be tailored to programming languages. If you are training only on languages we support or which are supported by tree-sitter, you might want to use a tokenizer made for source code.

Thanks for the reply and suggestion.
If I understand correctly, I used the tokenizer that you folks developed (fast instead of roberta ) as follows. You are suggesting to use a different detokenizer during training?
python3 -m codegen_sources.preprocessing.preprocess /gcs/transcoder_data/train_data_small \
--langs java cpp python \
--mode monolingual_functions \
--bpe_mode fast \
--local true \
--train_splits 8

For training we use the following script:
python3 -m torch.distributed.launch --nproc_per_node=$NGPU codegen_sources/model/train.py \
--exp_name mlm \
--dump_path '/gcs/transcoder_data/train_data_small_dump' \
--data_path '/gcs/transcoder_data/train_data_small/XLM-syml' \
--mlm_steps 'java_monolingual,python_monolingual' \
--add_eof_to_stream true \
--word_mask_keep_rand '0.8,0.1,0.1' \
--word_pred '0.15' \
--encoder_only true \
--n_layers 12  \
--emb_dim 768  \
--n_heads 12  \
--lgs 'java_monolingual-python_monolingual' \
--max_vocab 64000 \
--gelu_activation true \
--roberta_mode true \
--amp 2  \
--fp16 true  \
--batch_size 32 \
--bptt 512 \
--epoch_size 100000 \
--max_epoch 100000 \
--split_data_accross_gpu local \
--optimizer 'adam_inverse_sqrt,warmup_updates=10000,lr=0.0001,weight_decay=0.01' \
--save_periodic 0 \
--validation_metrics _valid_mlm_ppl \
--stopping_criterion '_valid_mlm_ppl,10'

Set roberta_mode = false got CUDA memory error
Tried to allocate 96.00 MiB (GPU 6; 15.78 GiB total capacity; 12.64 GiB already allocated; 36.25 MiB free; 14.02 GiB reserved in total by PyTorch

You made me realize that the example parameters we were showing in transcoder.md are those we used to finetune DOBF with a model that uses the same tokenizer and architecture as RoBERTa to compare it with CodeBERT and GraphCodeBERT. It didn't really make sense and we updated the parameters so that they correspond to TransCoder's architecture. Here are the differences:
--n_layers 6  \ (was 12)
--emb_dim 1024  \  (was 768)
--n_heads 8  \ (was 12)
--gelu_activation false \ (was true)
--roberta_mode false \ (was true)

We also updated it to train on python, java and C++ instead of only python and java like in the original TransCoder paper.
About your memory issues, we train our models on V100 GPUs with 32GB. If you only have 16GB you will need to either decrease the batch size (decrease the batch_size parameter for MLM or the tokens_per_batch parameter for DOBF, DAE and BT) or decrease the size of the model, for instance emb_dim (but in that case you won't be able to reload our pre-trained models). The Gradient overflow thing sometimes happens at the beginning of training and it's generally not a problem.

Thanks Baptiste for all the detailed answer. I can confirm the training is now working on our end.


Problem with Loader

Hello, when assembling any of your example, where external resources loading, can't get loader working
the project is going, but the resources just are not loaded, there is no such event as the end / error etc
added
imageloader.contentLoaderInfo.addEventListener(HTTPStatusEvent.HTTP_STATUS, httpStatusHandler);
imageloader.contentLoaderInfo.addEventListener(Event.INIT, initHandler);
imageloader.contentLoaderInfo.addEventListener(IOErrorEvent.IO_ERROR, ioErrorHandler);
imageloader.contentLoaderInfo.addEventListener(Event.OPEN, openHandler);
imageloader.contentLoaderInfo.addEventListener("progress", progressHandler);
imageloader.contentLoaderInfo.addEventListener(Event.UNLOAD, unLoadHandler);
in bat pointed to last flexjs
set FLEX_HOME=D:/apache-flex-flexjs-0.6.0-bin
maybe u know what the problem? thank you
for example TestBitmapDataSand working well
and i notices that i dont have class Image which u r using in Loader(ide didnt see it at least)

thanks open issues.but it is this example work?this example base on loader.
and it now just support the complete event.
https://github.com/matrix3d/spriteflexjs/blob/master/src/flash/display/Loader.as#L38
i have not add all the event now

and what ide u useing?i use the fd.and the image in the js.swc.
https://github.com/matrix3d/spriteflexjs/blob/master/test/build.bat#L11

intellij idea, but i just editing code there. building with ur bat file. could u pls post ur js.swc? thats strange

and ur flex_home is flexjs7, is it 0.7 version? I got 0.6

https://github.com/matrix3d/spriteflexjs/issues/1
get the 0.7

well  I tried to install 0.7 but the installation was stopped on unit tests flex-flexunit\FlexUnit4AntTasks\build.xml : 55  Error running javax.exe compiler. and so after building sdk i got error too flex-asjs\frameworks\projects\Core\src\test\flex\build.xml 117   mxmlc task failed
and now i dont see Image in flex-asjs\js\libs\js.swc (

pls try this
https://www.dropbox.com/s/13mrzk4asw1qcq2/flexjs7.zip?dl=0

here is my bat
set FLEX_HOME=D:/flexjs7
::set main=TestBitmapDraw
::set main=TestHungryHero
::set main=TestByteArrayVSArray
::set main=Main
set main=TestHungryHero
set ARGS=-remove-circulars
::set ARGS=-debug=true -remove-circulars
::set ARGS=-remove-circulars -js-compiler-option="--compilation_level WHITESPACE_ONLY"
start %FLEX_HOME%/js/bin/mxmlc %ARGS% -external-library-path="%FLEX_HOME%\js\libs\js.swc" -compiler.source-path=../src src/%main%.as -define=CONFIG::as_only,false -define=CONFIG::js_only,true
when i launch index.html i got stucked on this http://c2n.me/3zb2wQI , Do I need to do anything other than run bat file? here is end of console http://c2n.me/3zb3hGQ

you need a webserver.iis etc

when I try to download a remote resource http://c2n.me/3zbO9rP it didnt load too

the index must in webserver

that doesnt help http://c2n.me/3ze1fep

is it working good?
http://matrix3d.github.io/assets/html5/flexjsstage3d/bin/js-release/#test_hugryhero
pls paste the output console.log

yes. it working well. Browser console is empty

it working well,but your js,not work.
so pls get your loader test js,and as code.
i will debug it.

test.zip

BitmapData.js:122 Uncaught SecurityError: Failed to execute 'getImageData' on 'CanvasRenderingContext2D': The canvas has been tainted by cross-origin data.
you can not load http://cs416419.vk.me/v416419800/81a5/QxO0EJO_ORk.jpg
try QxO0EJO_ORk.jpg(it is work)

you can debug it yourself

great. When i placed both index and resources in webserver it sratrs working) hungryhero
Thank you very much!
and one more question. why there is no method loadbytes in Loader?

the loadbytes will coming soon.but i have not time now.

I forgot to ask, did u try to load swf into asjs?

swf hard to load,it is need big lib as3swf,and lzma lib.zip lib.
so not easy load it.
but maybe have a tool swf2something.exe.
and load the something(custom format of swf)


Add ARM and ARM64 to Visual Studio's ignore file.

Reasons for making this change:
Recent editions of Visual Studio now permit building Windows drivers and Windows desktop apps for the ARM and ARM64 architectures. Visual Studio uses the architecture name for some of its build directories,
Links to documentation supporting these rule changes:
This change follows existing precedent used for the x64 and x86 platforms.

@cwize1 I'm a bit nervous about ignoring every folder named some variation of arm/arm64, but given the precedence with x86/x64 and no complaints about that I guess I'm fine with it.

I renamed my folder storing ARM templates from arm to arm-temlpate for this.


Chart : series name with special characters not escaped

Hi,
When wrote a series with the name 'Score<5', I had got the following error trace:
Traceback (most recent call last):
  File "test_simple.py", line 22, in <module>
    XL_CHART_TYPE.COLUMN_CLUSTERED, x, y, cx, cy, chart_data
  File "C:\Anaconda\lib\site-packages\python_pptx-0.5.2-py2.7.egg\pptx\parts\slide.py", line 203, in add_chart

    rId = self.part.add_chart_part(chart_type, chart_data)
  File "C:\Anaconda\lib\site-packages\python_pptx-0.5.2-py2.7.egg\pptx\parts\slide.py", line 67, in add_chart_
part
    chart_part = ChartPart.new(chart_type, chart_data, self.package)
  File "C:\Anaconda\lib\site-packages\python_pptx-0.5.2-py2.7.egg\pptx\parts\chart.py", line 32, in new
    chart_part = cls.load(partname, content_type, chart_blob, package)
  File "C:\Anaconda\lib\site-packages\python_pptx-0.5.2-py2.7.egg\pptx\opc\package.py", line 328, in load
    element = parse_xml(blob)
  File "C:\Anaconda\lib\site-packages\python_pptx-0.5.2-py2.7.egg\pptx\oxml\__init__.py", line 26, in parse_xm
l
    root_element = etree.fromstring(xml, oxml_parser)
  File "lxml.etree.pyx", line 2993, in lxml.etree.fromstring (src\lxml\lxml.etree.c:62980)
  File "parser.pxi", line 1617, in lxml.etree._parseMemoryDocument (src\lxml\lxml.etree.c:92828)
  File "parser.pxi", line 1495, in lxml.etree._parseDoc (src\lxml\lxml.etree.c:91637)
  File "parser.pxi", line 1011, in lxml.etree._BaseParser._parseDoc (src\lxml\lxml.etree.c:88294)
  File "parser.pxi", line 577, in lxml.etree._ParserContext._handleParseResultDoc (src\lxml\lxml.etree.c:84019
)
  File "parser.pxi", line 676, in lxml.etree._handleParseResult (src\lxml\lxml.etree.c:85122)
  File "parser.pxi", line 616, in lxml.etree._raiseParseError (src\lxml\lxml.etree.c:84445)
lxml.etree.XMLSyntaxError: StartTag: invalid element name, line 17, column 30

I have found that series name were not escaped (https://github.com/scanny/python-pptx/blob/master/pptx/chart/data.py#L140-L161) and fix it temporally in https://github.com/huandzh/python-pptx/tree/escape_series_name .
But I am not sure whether there are other values not escaped. Maybe a overall escape solution is better.  -0 0
How about you opinion?

Fixed in 0.5.8.


Invalid metric value

Hi,
We are using the fieldpack on RHEL7.1 with Docker 1.8.2-el7 on epagent 10.1
It appears to be producing an invalid metric value error:
Response:
{
    "errorCode": 1010,
    "validCount": 387,
    "invalidCount": 1,
    "errorMessage": "One or more metric specifications were invalid",
    "metricErrors": [
        {
            "metricErrorCode": 1013,
            "metricErrorMsg": "Invalid metric value",
            "metricErrorIndex": 1,
            "metricName": "Docker|<<OUR HOSTNAME>>:Total Memory"
        }
    ]
}

If i enable the the debug line in writeMetrics :
print('type of {} is {}, name = {}, value = {}'.format(key, type(values[key]), name, values[key]))
It prints out what you would expect:
type of MemTotal is <type 'int'>, name = :Total Memory, value =<PHONE_NUMBER>
However, it continues to print the above error.
The metric is greyed out in the webview investigator.
Any thoughts?

I changed the metric type to long for memory metrics. Can you give it a try now?

Perfect!!
Just tested and its working great now - no issues.
thanks.

Great!


[RFC] N-variables polynomials

... And how should we handle them ?
Should it based on seq of tuples ? On Tensor ?

For N > 1 I think the only reasonable option is to go with Tensors. Otherwise we have to create separate overloads for each N if we go with tuples.


host searchtools.js on our theme

this relies on:

https://github.com/rtfd/readthedocs.org/pull/1808
https://github.com/rtfd/readthedocs-sphinx-ext/pull/16

ack


Investigate screen reader interpreting cells as groupings

          5. Table contents when navigating horizontally

When using CNTRL+Option+L/R or Up/Down arrows to navigate horizontally through the table with the screen reader, it reads the the contents of a cell as a group, saying the same content three times.  To minimize the amount of times you need to arrow L and R, the content inside the cell shouldn't be inside a group

Current:
Originally posted by @kristastarr in https://github.com/carbon-design-system/ibm-products/issues/3118#issuecomment-1616746078

@kristastarr when you get a chance can you talk another look at this? i made some adjustments in #3957 that should alleviate some accessibility issues

I tested "Basic usage" and "Selectable rows" since it looks like these changes are to the header so apply to all tables - are there specific ones you wanted me to test?
Observations:

When using CNRTL+OPT+ arrow key to navigate, if you press arrows consecutively without releasing CNTRL+OPT, I see the same behavior as before; when you release CNTRL+OPT with each press of arrow keys, the text content is still announced as a "group" but is only read out once, so that is an improvement

The fields with dates are not showing this issue.  Fields with numbers are.

It's confusing that column names are announced as "Last Name and Resize Column", I think because of the aria-label for the splitter.  I don't think that was happening before.

I have some other observations about the splitter as well - keyboard navigation works great but the screenreader descriptions could be improved - is there an open issue where I should document those?


FreeOTP warns that build is too old

I'm on a Galaxy S10e with Android 10 installed. When I installed FreeOTP for the first time, it warned me that the build for FreeOTP is built for too old of a version of Android and that the app may not function properly. Should I be concerned? Is there any way around this? For the sake of transparency it does seem to be working properly so far.

This project is abandoned.  Please contribute to https://github.com/freeotp/freeotp-android/issues/207

On the iOS side there has been some progress. The Android project is in need of someone to take over active development.
I am currently looking after the Android PRs, but don't have time to take on the big feature work in the Renaissance project.


Error:XHR failed:  plugin not install

Extension Name: configuration-editing
Extension Version: 0.0.1
OS Version: Linux x64 4.13.0-32-generic
VSCode version: 1.19.3

We have written the needed data into your clipboard. Please paste:

We have written the needed data into your clipboard. Please paste:

Can you try it again and paste the relevant data to GitHub?


Fix BUG "No FileSystem for scheme: hdfs" for hdfs-srorage-extension

Problem
While starting realtime node with hdfs as deep storage (i.e. hdfs-storage-extenstion), log as following shows that it should already loaded hadoop-hdfs correctly
INFO [main] io.druid.initialization.Initialization - Added URL[file:/home/druid/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.3.0/hadoop-hdfs-2.3.0.jar]

But we got IOException about "No FileSystem for scheme: hdfs"  while it tried to persist segments  onto hdfs which means hadoop-hdfs ( class org.apache.hadoop.hdfs.DistributedFileSystem in fact) should not been loaded correctly.
No FileSystem for scheme: hdfs","exceptionStackTrace":"java.io.IOException: No FileSystem for scheme: hdfs
     at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:2304)
     at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2311)
     at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:90)
     at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2350)
     at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2332)
     at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:369)
     at org.apache.hadoop.fs.Path.getFileSystem(Path.java:296)
     at io.druid.storage.hdfs.HdfsDataSegmentPusher.push(HdfsDataSegmentPusher.java:75)
     at io.druid.segment.realtime.plumber.RealtimePlumber$4.doRun(RealtimePlumber.java:356)
     at io.druid.common.guava.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:42)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
     at java.lang.Thread.run(Thread.java:745)\n","interval":"2015-01-08T08:00:00.000Z/2015-01-08T09:00:00.000Z"}}

In fact, lots of other Druid users rather than us are also being confused by the same bug

https://groups.google.com/forum/#!topic/druid-development/QpYq0eGDHa8
https://groups.google.com/forum/#!topic/druid-development/U-X8A5vsmog

Root Cause
In fact, this is a typical case of the maven-assembly plugin breaking things in hadoop hdfs.
The root cause is because differents JARs (hadoop-commons for LocalFileSystem, hadoop-hdfs for DistributedFileSystem) each contain a different file called org.apache.hadoop.fs.FileSystem in their META-INFO/services directory. This file lists the canonical classnames of the filesystem implementations they want to declare (This is called a Service Provider Interface, see org.apache.hadoop.FileSystem line L2591). Druid module management system seems to rely on customized ServiceProviderInterface too, right ? When we use maven-assembly, all META-INFO/services/org.apache.hadoop.fs.FileSystem overwrite each-other. Only one of these files remains (the last one that was added). In this case, the Filesystem list from hadoop-commons overwrites the list from hadoop-hdfs, so DistributedFileSystem was no longer declared.
Solution

As a quick solution, the druid users caught with the same problems may start druid nodes with hadoop classpath or copy all hadoop-hdfs related jars' path to the end of classpath  like:
 java -Ddruid.realtime.specFile=config/realtime/metrics.spec -classpath lib/*:config/realtime:`hadoop classpath` io.druid.cli.Main server realtime

To completely fixed the bug, we can explicitly refer to DistributedFileSystem in hdfs-storage-extension code

Having two impls in the service discovery path shouldn't be the root cause, that should simply let the service loader know there are two impls. If having two service impls is preventing HDFS from parsing the URIs correctly that sounds like a HDFS bug.

Druid purposefully tries to disconnect itself from any particular Hadoop version. With 0.x/1.x still in wide use, and 2.x very popular, and 3.x actively moving along, we need to do everything we can to make sure that the solution is easily used in whatever version the users decide to have on the backend.
As such, I think the hadoop classpath solution is preferred unless there is a particular reason that solution confounds other behaviors

To continue with my comments replied in line, druid users are really appreciating for the convenient extension loader mechanism in druid, but the bug just makes them confused.  I'm not sure but I think it may be caused by the customized class loader in Druid rather than about HDFS itself, because the hadoop classpath solution proves that it should be OK in traditional class path loader for hadoop-hdfs but how should it not work for Druid? Especially when druid's log prints:
INFO [main] io.druid.initialization.Initialization - Added URL[file:/home/druid/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.3.0/hadoop-hdfs-2.3.0.jar]

Surely, I also agree with the opinion about disconnecting Druid with any particular Hadoop version. So i think we have two options here:

If druid is still willing to help users to load all jar dependencies like what hdfs-storage-extension does for us, it should fix the bug as in this PR.

If druid really prefers users to add hadoop related dependencies by hands, the POM scope of hadoop-client  dependency here extensions/hdfs-storage/pom.xml#L58 should be changed from compile to provided, right? And it should also make sure Druid module loader not to load additional dependent hadoop-hdfs jars into local MAVEN repository, otherwise the JVM will always at least two different versions of hadoop-hdfs jars which may cause some other unknown problems:
  $ lsof -p 17094 | grep hadoop-hdfs
  java    17094 druid  mem    REG              252,0  5783912   774885 /home/druid/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.3.0/hadoop-hdfs-2.3.0.jar
  java    17094 druid  mem    REG              252,0  7822243   774161 /usr/hdp/<IP_ADDRESS>-2041/hadoop-hdfs/hadoop-hdfs-<IP_ADDRESS>.2.0.0-2041.jar
  java    17094 druid  229r   REG              252,0  7822243   774161 /usr/hdp/<IP_ADDRESS>-2041/hadoop-hdfs/hadoop-hdfs-<IP_ADDRESS>.2.0.0-2041.jar
  java    17094 druid  472r   REG              252,0  5783912   774885 /home/druid/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.3.0/hadoop-hdfs-2.3.0.jar

@haoch : Just FYI, there is a discussion about how how to handle dependencies going forward, which is part of why this PR isn't getting traction yet.

Thanks @drcrallen

@haoch, are you having this problem when you try to make a single self contained jar? I'm asking because in that case, I think it makes more sense to concatenate the services files rather than hard-coding fs impls in Druid code. Hard-coding the impls in Druid wouldn't help for other FS types (like S3) unless we add them all, and the strategy of adding these things in the code would tie us more closely to a particular version of hadoop.
Fwiw, what I've seen work for self contained jars in the past is using the maven shade plugin with a configuration like:
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-shade-plugin</artifactId>
  <executions>
    <execution>
      <phase>package</phase>
      <goals>
        <goal>shade</goal>
      </goals>
      <configuration>
        <shadedArtifactAttached>true</shadedArtifactAttached>
        <shadedClassifierName>selfcontained</shadedClassifierName>
        <transformers>
          <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
            <resource>META-INF/services/org.apache.hadoop.fs.FileSystem</resource>
          </transformer>
        </transformers>
      </configuration>
    </execution>
  </executions>
</plugin>

This will concatenate the listed services files together so different files from different jars don't clobber each other. There may be something equivalent for the assembly plugin.

looks like a genuine problem. however, it is more of an extension mechanism problem than the code being fixed here which is prone to failure in various situations requiring other FileSystem schemes than hdfs and local.
I think the problem is that when FIleSystem.get(..) is called, hadoo-hdfs.jar is not in the classpath for classloader(which is Thread.currentThread().getContextClassLoader()) used because it wasn't in the original classpath of the druid process but was a transitive dependency of druid-hdfs-storage extension. Actually, I could argue that this is a hadoop bug as well because it did not honor config.getClassLoader() and used Thread context classloader.  (otherwise https://github.com/druid-io/druid/pull/1454 would have fixed this problem)
There is some work happening to remove dynamic loading of extensions and that should fix this issue eventually. In the meantime, I would recommend just putting "hadoop classpath" manually on the classpath and that is what we [and most people] do.

actually, I created a bug for hdfs as well for using correct classloader https://issues.apache.org/jira/browse/HDFS-8750

I think these threads are also related:

http://stackoverflow.com/questions/17265002/hadoop-no-filesystem-for-scheme-file
http://grokbase.com/t/cloudera/scm-users/1288xszz7r/no-filesystem-for-scheme-hdfs

This issue also exists when using the Druid Tranquility library (https://github.com/druid-io/tranquility).

Tranquility works with the Druid indexing service (http://druid.io/docs/latest/Indexing-Service.html). To get started, you'll need an Overlord, enough Middle Managers for your realtime workload, and enough Historical nodes to receive handoffs. You don't need any Realtime nodes, since Tranquility uses the indexing service for all of its ingestion needs.

My successful workaround to Druid 0.8.0 patch the druid-hdfs-storage extension:

Git Clone Druid  from https://github.com/druid-io/druid.git and check out tag "druid-0.8.0".

Update the pom.xml dependency scopes of artifacts "hadoop-hdfs", "hadoop-common" and "hadoop-hdfs" from "test" to "provided".

         <dependency>
           <groupId>org.apache.hadoop</groupId>
           <artifactId>hadoop-hdfs</artifactId>
           <version>2.3.0</version>
           <classifier>tests</classifier>
-          <scope>test</scope>
+          <scope>provided</scope>
         </dependency>
         <dependency>
           <groupId>org.apache.hadoop</groupId>
           <artifactId>hadoop-common</artifactId>
           <version>2.3.0</version>
           <classifier>tests</classifier>
-          <scope>test</scope>
+          <scope>provided</scope>
         </dependency>
         <dependency>
           <groupId>org.apache.hadoop</groupId>
           <artifactId>hadoop-hdfs</artifactId>
           <version>2.3.0</version>
-          <scope>test</scope>
+          <scope>provided</scope>
         </dependency>

Update HdfsStorageDruidModule.java with patch mentioned in this thread.

 public class HdfsStorageDruidModule implements DruidModule
@@ -82,6 +86,10 @@ public class HdfsStorageDruidModule implements DruidModule

     final Configuration conf = new Configuration();

+    // Walk around a typical case that "maven-assembly" causes bug about "No FileSystem for scheme: hdfs" while loading hadoop-hdfs dependency
+    conf.set("fs.hdfs.impl", DistributedFileSystem.class.getName());
+    conf.set("fs.file.impl", LocalFileSystem.class.getName());
+
     // Set explicit CL. Otherwise it'll try to use thread context CL, which may not have all of our dependencies.
     conf.setClassLoader(getClass().getClassLoader());

Do a maven clean and install ("mvn clean install").
Zip the patched Druid extension (.m2\repository\io\druid\extensions\druid-hdfs-storage -> druid-hdfs-storage.zip).
Copy the patched Druid extension on the Druid host.

ls -al ~/.m2/repository/io/druid/extensions/druid-hdfs-storage/
cp druid-hdfs-storage.zip ~/.m2/repository/io/druid/extensions/
rm -rf ~/.m2/repository/io/druid/extensions/druid-hdfs-storage/
cd ~/.m2/repository/io/druid/extensions/
unzip druid-hdfs-storage.zip

Launch Druid

Full patch contents: patch.diff
diff --git a/extensions/hdfs-storage/pom.xml b/extensions/hdfs-storage/pom.xml
index 9518404..7ad60dc 100644
--- a/extensions/hdfs-storage/pom.xml
+++ b/extensions/hdfs-storage/pom.xml
@@ -81,20 +81,20 @@
           <artifactId>hadoop-hdfs</artifactId>
           <version>2.3.0</version>
           <classifier>tests</classifier>
-          <scope>test</scope>
+          <scope>provided</scope>
         </dependency>
         <dependency>
           <groupId>org.apache.hadoop</groupId>
           <artifactId>hadoop-common</artifactId>
           <version>2.3.0</version>
           <classifier>tests</classifier>
-          <scope>test</scope>
+          <scope>provided</scope>
         </dependency>
         <dependency>
           <groupId>org.apache.hadoop</groupId>
           <artifactId>hadoop-hdfs</artifactId>
           <version>2.3.0</version>
-          <scope>test</scope>
+          <scope>provided</scope>
         </dependency>
       </dependencies>

diff --git a/extensions/hdfs-storage/src/main/java/io/druid/storage/hdfs/HdfsStorageDruidModule.java b/extensions/hdfs-storage/src/main/java/io/druid/storage/hdfs/HdfsStorageDruidModule.java
index 52eadd3..94b63fe 100644
--- a/extensions/hdfs-storage/src/main/java/io/druid/storage/hdfs/HdfsStorageDruidModule.java
+++ b/extensions/hdfs-storage/src/main/java/io/druid/storage/hdfs/HdfsStorageDruidModule.java
@@ -29,6 +29,8 @@ import io.druid.initialization.DruidModule;
 import io.druid.storage.hdfs.tasklog.HdfsTaskLogs;
 import io.druid.storage.hdfs.tasklog.HdfsTaskLogsConfig;
 import org.apache.hadoop.conf.Configuration;
+import org.apache.hadoop.fs.LocalFileSystem;
+import org.apache.hadoop.hdfs.DistributedFileSystem;

 import java.util.List;
 import java.util.Properties;
@@ -82,6 +84,10 @@ public class HdfsStorageDruidModule implements DruidModule

     final Configuration conf = new Configuration();

+    // Walk around a typical case that "maven-assembly" causes bug about "No FileSystem for scheme: hdfs" while loading hadoop-hdfs dependency
+    conf.set("fs.hdfs.impl", DistributedFileSystem.class.getName());
+    conf.set("fs.file.impl", LocalFileSystem.class.getName());
+
     // Set explicit CL. Otherwise it'll try to use thread context CL, which may not have all of our dependencies.
     conf.setClassLoader(getClass().getClassLoader());

@mark1900 @haoch can you pls try the fix in https://github.com/druid-io/druid/pull/1721 and see if that fixes the issue?

@himanshug I merged the changes in #1721 (https://github.com/druid-io/druid/pull/1721/files) into the druid release tagged "druid-0.8.0" and it seemed to also address this issue.

@mark1900 thanks for testing the patch.

@himanshug can we fix merge conflicts?
:+1:

https://github.com/druid-io/druid/issues/1714 is fixed by #1721
this PR is redundant, so closing.
@mark1900 @haoch thanks for all the details you provided to find the fix for this issue.

@himanshug @haoch I merged the changes in #1721 (https://github.com/druid-io/druid/pull/1721/files) into the druid release tagged "druid-0.8.1" and it seems that this issue still occurs.

Issue seems to be resolved in the latest Druid 0.8.2 release: http://static.druid.io/artifacts/releases/druid-0.8.2-bin.tar.gz


[planner] Golang planner return error when main.go is not found

Summary
Golang planner return error when main is not found. It looks for main() and if not found, print the following error as warnings:
Error: Cannot find main() file in the directory. If you wish to specify a different import path, add `build_stage` in your devbox.json

Warnings will only get printed out if the stage is not overridden by devbox.json.
related to https://github.com/jetpack-io/devbox/issues/137
How was it tested?
devbox build

I haven't read the code yet: but I wanted to confirm that the error does not affect the ability for devbox shell to start even if the builder fails. Correct?

I haven't read the code yet: but I wanted to confirm that the error does not affect the ability for devbox shell to start even if the builder fails. Correct?

This does not affect devbox shell


k6 backend

Add https://k6.io/ as load generator.

Codecov Report

Merging #178 (0b0d391) into master (a2c6d0c) will increase coverage by 0.06%.
The diff coverage is 61.21%.

@@            Coverage Diff             @@
##           master     #178      +/-   ##
==========================================
+ Coverage   60.45%   60.51%   +0.06%
==========================================
  Files          34       36       +2
  Lines        2463     2677     +214
==========================================
+ Hits         1489     1620     +131
- Misses        871      943      +72
- Partials      103      114      +11

Impacted Files
Coverage Δ

pkg/kubernetes/apis/loadtest/v1/types.go
0.00% <ø> (ø)

pkg/proxy/request.go
78.53% <ø> (ø)

pkg/backends/k6/backend.go
38.83% <38.83%> (ø)

pkg/backends/k6/resources.go
81.98% <81.98%> (ø)

Continue to review full report at Codecov.

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

I'd also would like to attract your attention to the following behaviour:
How to reproduce: Create a loadtest with several distributed pods and provide a duration.
curl --location --request POST 'http://<IP_ADDRESS>:8080/load-test' \
--header 'Content-Type: application/json' \
--form<EMAIL_ADDRESS>\
--form 'distributedPods="4"' \
--form 'type="K6"' \
--form 'duration="240s"'

script.js is an example file from k6 documentation
Expected result: all pods are running during the same duration.
Actual result: all pods started but only one pod is running according to the desired duration. Other pods immediately change status to Completed.
If this is an expected behaviour I think this should be added to the documentation saying that it doesn't make sense to use more than one pod.

I'd also would like to attract your attention to the following behaviour: How to reproduce: Create a loadtest with several distributed pods and provide a duration.
curl --location --request POST 'http://<IP_ADDRESS>:8080/load-test' \
--header 'Content-Type: application/json' \
--form<EMAIL_ADDRESS>\
--form 'distributedPods="4"' \
--form 'type="K6"' \
--form 'duration="240s"'

script.js is an example file from k6 documentation
Expected result: all pods are running during the same duration. Actual result: all pods started but only one pod is running according to the desired duration. Other pods immediately change status to Completed.
If this is an expected behaviour I think this should be added to the documentation saying that it doesn't make sense to use more than one pod.

Hello @s-radyuk
Thanks for the review.
You need to configure VUs >= DistributedPods to put all pods to work. You can define VUs by exporting options object inside javascript code or by setting the K6_VUS environment variable.
I've added some documentation about this in the latest commit.

hey @walterwanderley :wave:
Thank you for this awesome contribution!
Could you please include the new backend docs in the mkdocs.yaml file?

hey @walterwanderley 👋 Thank you for this awesome contribution!
Could you please include the new backend docs in the mkdocs.yaml file?

Hi @lucasmdrs, awesome project!
Ok! I've added k6 to mkdocs.

Ok! I've added k6 to mkdocs.

Thanks! LGMT :heavy_check_mark:
@s-radyuk do you have any other concerns ?


Use Vertical Layout not working

Expected Behavior
trying enable the checkbox "use vertical layout"  so Response section to the right of Request section
Actual Behavior
Request section is horizontal  above the the response section (this is the default view after download)
Reproduction Steps

download insomnia 2023.1.0
open a collection
notice the image like so:

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
Mar 10, 2023 i downgraded to v2022.7.5 and this checkbox toggle works instantly
Insomnia Version
2023.1.0
What operating system are you using?
macOS
Operating System Version
Ventura 13.1
Installation method
insomnia.rest
Last Known Working Insomnia version
2022.7.5

I have the exact same issue. Seems like it is a regression in version 2023.1.0.

The same here. I need to downgrade for now.

A few days ago I was stuck with horizontal layout.
Testing again today, it seems that the checkbox is the opposite of the label.
When 'use vertical layout' is checked it's horizontal, when unchecked it's vertical.

I also thought that was it. But with a checkbox checked or not, the result doesn't change. I needed to go back to an old version, 2022.7.5.

@robwent That was my experience at first as well. I just tried updating my laptop and I'm seeing the same there.

@524c  That was my experience at first as well. I just tried updating my laptop and I'm seeing the same there.

The issue only happens on small window sizes. Try reducing the width of your window and you will see it is stuck on vertical layout.

@merc1er That's true. Reducing the width forces the horizontal layout.
The checkbox option is still the opposite of the expected behaviour though.

Just updated to the latest version and noticed the same behavior.
The option "user vertical layout" doesn't work as expected.
Version: Insomnia 2023.1.0
Build date: 3/9/2023
OS: Darwin arm64 22.3.0
Electron: 22.0.0
Node: 16.17.1
V8: <IP_ADDRESS>-electron.0
Architecture: arm64

Just updated to the latest version and noticed the same behavior.
The option "user vertical layout" doesn't work as expected.
Version: Insomnia 2023.1.0
Build date: 3/9/2023
OS: Darwin arm64 22.3.0
Electron: 22.0.0
Node: 16.17.1
V8: <IP_ADDRESS>-electron.0
Architecture: arm64

Just updated to the latest version and noticed the same behavior.
The option "user vertical layout" doesn't work as expected.
Version: Insomnia 2023.1.0
Build date: 3/9/2023
OS: Darwin arm64 22.3.0
Electron: 22.0.0
Node: 16.17.1
V8: <IP_ADDRESS>-electron.0
Architecture: arm64

Also experiencing the layout not changing when the vertical layout checkbox is checked or unchecked.
Version: Insomnia 2023.1.0
Build date: 3/9/2023
OS: Darwin arm64 21.6.0
Electron: 22.0.0
Node: 16.17.1
V8: <IP_ADDRESS>-electron.0
Architecture: arm64

Same form me :
Version: Insomnia 2023.1.0
Build date: 3/9/2023
OS: Darwin x64 22.2.0
Electron: 22.0.0
Node: 16.17.1
V8: <IP_ADDRESS>-electron.0
Architecture: x64

It still doesn't work in the latest version.
Impossible to use on notebooks with small screens (13").
Version: Insomnia 2023.2.0
Build date: 4/26/2023
OS: Darwin x64 22.1.0
Electron: 22.0.0
Node: 16.17.1
V8: <IP_ADDRESS>-electron.0
Architecture: x64

The problem seems to come from the beakpoint for layout switching. They must have changed the value.
Start by checking that "Use vertical layout" is not checked in your preferences.
Then you can correct the problem by simply zooming out a bit your UI.

Windows/Linux: Ctrl + - (not sure about the shortcut)
Mac: Cmd + -

Foohx you're my hero! That did work for me.

Then you can correct the problem by simply zooming out a bit your UI.

The issue with that is that the text becomes too small and barely legible. But I guess that's a workaround on some screen types.

Then you can correct the problem by simply zooming out a bit your UI.

The issue with that is that the text becomes too small and barely legible. But I guess that's a valid workaround on some screen types.

@merc1er, I don't know why it always worked before, but a zooming out "fix" the problem and the vertical layout came back 🙏 Thanks!
Hey @filfreire, how are ayou?
Would it be possible to try to understand what happened in the last versions? Using an older version, 2022.7.5, this issue does not occur. I'm using it on a 13" Macbook air. I can do whatever tests you need.

I have tried zooming in/out and changing the Use vertical layout checkbox to checked/unchecked and still cannot make response section come to the right.
I am on macOS (with Larger Text in display settings), and this is the first time I am using Insomnia and I am having trouble seeing the Graphql variables properly in vertical layout. hence I would like to see response in the right section with divider.
In postman graphql variables are on right and response is at bottom which is still okay. Will stick with postman for now I guess until this issue is fixed...
Here is Insomnia version info:
Version: Insomnia 2023.2.2
Build date: 5/17/2023
OS: Darwin x64 21.6.0
Electron: 22.0.0
Node: 16.17.1
V8: <IP_ADDRESS>-electron.0
Architecture: x64

I don't know if this has been updated but apparently there's a misunderstanding about this feature.
Version: Insomnia 2023.2.2
Build date: 5/17/2023
OS: Linux x64 5.19.0-42-generic
Electron: 22.0.0
Node: 16.17.1
V8: <IP_ADDRESS>-electron.0
Architecture: x64

As we can see:

While checked (Vertical), the option is supposed to stack Request and Response panels. Request to the top and Response to the bottom.
While unchecked (Horizontal), the option (was supposed to) put both panels side-to-side. Request to the left and Response to the right.

Vertical or Horizontal terms are not related to the layout of one panel individually, but to the arrangement of both of them.
That said, I was also struggling with this problem, Checking or Unchecking this option didn't change nothing.
It seems that the problem is related to auto adjust based on window width/zoom. Smaller width and/or bigger zoom will automatically adjust to vertical layout.
And while there is an option to force vertical layout (which is already the standard one), there's no option to force the horizontal. The unchecked box do not force horizontal, opposite to what is possible to deduce.
Maybe having options to choose what layout to force would solve this issue?

Is there a solution for this? It's quite annoying

@sindelio my solution for now is downloading the last release that did not have the issue from here https://github.com/Kong/insomnia/releases/tag/core%402022.7.5 and disable software updates. In the meantime I'm keeping an eye on this ticket.

@mastazi That works for now, thx

I would very much like to see this fixed, Insomnia keeps updating and the bug comes back

It seems this issue is caused by unclear language in the checkbox description. Horizontal/Vertical vs column/row
Layout rules:
Use vertical layout: Checked
This will show request and response in a single column.
Use vertical layout: Unchecked
This will show request and response in a single row above 1200px, below this width, layout will be in a single column.
This approach allows us to use more horizontal screen space for tabs and such.
I've made a PR to update the tooltip to clarify this behaviour #6739

@jackkav regardless of language the problem is that on smaller screens (e.g. MacBook Pro 14") changing the setting doesn't do anything (unless you play around with zoom level but then the text becomes too small). At least this was true until recently. Like many others in this thread I disabled updates on my Mac, but I could re-enable and test if a fix is out, please advise.

@jackkav specifically this part of your comment is not true for me and the other people in this thread

Use vertical layout: Unchecked
This will show request and response in a single row above 1200px, below this width, layout will be in a single column.

We still see request and response in a single column with the setting unchecked

Hello everyone - I am trying to understand better what's happening here.
This is the standard layout with "Use vertical layout" unchecked:

And this is the layout with "Use vertical layout" checked:

It seems that the layout is changing accordingly to the "Vertical" setting, with the response section on the right when unchecked, and the response section below (in a vertical stacked position) when checked.
When the screen size is too small, the application defaults to a vertical stacked layout by default (even when the "Use vertical layout" setting is unchecked) because there wouldn't be enough space to show all the columns otherwise. I seem to understand that this is the objection?

@subnetmarco

[...]  the layout is changing accordingly to the "Vertical" setting, with the response section on the right when unchecked, and the response section below (in a vertical stacked position) when checked.

Correct

When the screen size is too small, the application defaults to a vertical stacked layout by default (even when the "Use vertical layout" setting is unchecked) because there wouldn't be enough space to show all the columns otherwise.

Not true, there is plenty of space, download https://github.com/Kong/insomnia/releases/tag/core%402022.7.5 on a 13" Mac and see for yourself

I seem to understand that this is the objection?

The objection is that before this checkmark existed we could have the side-by-side layout all the time, regardless of screen size and now this is impossible unless reverting to the old version of Insomnia.

This is really weird..
People just want the same behaviour as it was before.
It seems that someone changed something because they thought it would be better for small screens, but those changes defied the options.

@robwent If enough folks are interested we could fork Insomnia, we would keep merging all the other updates from upstream, except the Postman-like layout. It would be better than being stuck on an 18-month-old version I guess?

@mastazi What does this have to do with the current issue?

@subnetmarco insomnia is open source, yes?  So what's wrong with forking?
Your previous comment from Nov 2nd read like "this is working as designed by our team" so in that case forking would be the logical solution, I don't see what's wrong with that.

If you want to contribute a fix on the layout problem we are discussing, you are welcome.

It seemed you did not want the fix to happen as I explained above.

If you want us to attempt to fix it, you need to have patience as we go through the issue.

I don't want you to do anything, I don't pay you and I have no say in how you use your time.

If you want to fork the project and fix this issue there, let us know when you do that so we can also merge the fix here.

This is obvious, it's just how open source works.

Still seeing the same behavior, no matter what setting is employed. My scren is quite big, however the request and response panels are always stackd on top of each other. Rolling back to version 2022.7.5 works. @subnetmarco are there any plans to fix this?

@jackkav Is there any reason why we cannot reduce the 880px threshold to better accommodate smaller screen sizes? I suggest we change it to 760px to better work with the common 768px resolution typically found in smaller screens.

@subnetmarco I think thre is really a bug in the UI, even in the latest releases my request/response panels are always stacked vertically. I rolled back to 2022.7.5 for now and I can properly set it to horizontally stacked, however this made me look into other alternatives such as Bruno and Thunder. None really satisfied my needs, so I'm keeping Insomnia for now, but note a simple UI bug might be leading users elsewhere.


Create a per podcast atom/rss feed

I was updating my podcasts rss feeds and just realize crimethinc as only one feed for every podccasts. I think it could be nice to generate a feed for each podcast.

That's a good idea. 👍🏻
The current unified feed is provided by the podcast hosting service. But we could provide our own for show specific feeds too.

That's a good idea. 👍🏻
The current unified feed is provided by the podcast hosting service. But we could provide our own for show specific feeds too.

I didn't know there was a podcast hosting service, but I'll try to give a look at that when I have some free time.

I didn't know there was a podcast hosting service, but I'll try to give a look at that when I have some free time.


request for UI tweak on checkboxes that toggle adjacent form controls

If one isn't familiar with the equivalent cli tools, it's not immediately obvious that a given checkbox will activate/disable an additional option or set of options- a couple of examples:

"Separate chroma quality" opening toggling the chroma quality slider
"pointless spec compliance" slides up an already-enabled "Optimize Huffman table" over "Progressive rendering" rather than visually indicating the latter option has been disabled.

Closing this for now since UI have changed in V2


Update quanteda cheatsheet

Change reference from quanteda.data package to quanteda.corpora (new name)
tokens_compress() occurred twice; change this to only one mention
Update date of last update
Update PDF
Upload .pptx file

Thanks @stefan-mueller!


[Feature Request] Refactor CONTRIBUTING guide

Is your feature request related to a problem? Please describe.
There is no contributing guide. Need to make one of it.
Describe the solution you'd like
I will write it
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

close at #625


fix download links for testsuites (FHI & pspnc)

Can one of the admins verify this patch?

test this please

test this please


Allow aspire dashboard run behind proxy with SSL terminate

Description
When aspire run behind a proxy / load balancer with ssl terminate, aspire oidc authn will redirect user to IdP with parameter redirect_uri=http://aspire.host.
This PR allows aspire redirect with https redirect_uri.
Fixes #5134
Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[x] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[x] No

You can just set configuration and it’ll enable this middleware

You can just set configuration and it’ll enable this middleware

Thanks. I found the solution:
ForwardedHeader can be enabled by set environment ASPNETCORE_FORWARDEDHEADERS_ENABLED to true, more info see https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-8.0#forward-the-scheme-for-linux-and-non-iis-reverse-proxies


Clean Up

Just makes actions easier to read, can eventually get rid of IDs.cs

Also preps setting up other mooch MakeShift Bait and some other stuff that could be automated

IDs.cs is used across multiple files that need to know some specific IDs, like HookType.cs that needs the IDs of the hooksets. It's better to keep them as a separate file containing all types of IDs and make things more organized and easier for future uses, there's no need to keep them on HookManager.cs like before.

Also preps setting up other mooch MakeShift Bait and some other stuff that could be automated

I didn't even know MakeShift Bait was a thing tbh, I'll check it out. I might also add some new features like Auto Patience or use Thaliak's Favor to generate GP.

I didn't even know MakeShift Bait was a thing tbh, I'll check it out. I might also add some new features like Auto Patience or use Thaliak's Favor to generate GP.

Both of these features would be most welcome! Amazing development on the plugin :)


vision-camera-ocr not working on XCode 15 Beta 8

I am trying to compile IOS app with vision-camera-ocr V1.0.0 on XCode 15 Beta 8.
Application crash with below error on startup
objc[3093]: Swift class extensions and categories on Swift classes are not allowed to have +load methods
Crash report is attached:
Report.docx
App is working well on

Xcode 14.3.1 with vision-camera-ocr
Xcode 15 Beta 8 without vision-camera-ocr

Looks like there is something in vision-camera-ocr that is not compatible with XCode 15
React Native V0.71.12
Output of npx react-native info
System:
OS: macOS 13.4.1
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 30.71 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 14.16.0 - ~/.nvm/versions/node/v14.16.0/bin/node
Yarn: Not Found
npm: 6.14.11 - ~/.nvm/versions/node/v14.16.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.0, iOS 17.0, macOS 14.0, tvOS 17.0, visionOS 1.0, watchOS 10.0
Android SDK: Not Found
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9477386
Xcode: 15.0/15A5229m - /usr/bin/xcodebuild
Languages:
Java: 11.0.2 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

I was having a similar issue with this library, which also uses MLKit. Not sure if that's where the issue lies.

I was having a similar issue with this library, which also uses MLKit. Not sure if that's where the issue lies.

Are you still getting the issue. If no, how did you fix it.

Still having an issue.

@OGreeni The issue is related to #1802


Support Iceberg positional deletes

This PR is the first cut to support reading Iceberg tables with positional delete files.
Design doc: https://github.com/facebookincubator/velox/issues/5977
TODO:

Delete file deserialization in HiveIcebergSplit. This will be done after the Prestissimo changes are in shape
File path matching when reading the positional delete files
Performance optimization to avoid extra conversion from row numbers to bitmap then to row numbers

Catches:

The velox_hive_iceberg_datasource would be better to be included in velox_hive_connector. But so far it's unclear to me how to do it properly. Suggestions are welcome.

because the split is not guaranteed to be the same type during the life cycle of the data source

@Yuhta Thanks for brainstorming. Could you give me an example when this is going to happen?

@yingsu00 For now this is not switch between two different frameworks, but could happen that the first split is a normal split without deltas but the subsequent one is a split with deltas.  So process it at per split level looks the right thing to me.

@yingsu00 For now this is not switch between two different frameworks, but could happen that the first split is a normal split without deltas but the subsequent one is a split with deltas. So process it at per split level looks the right thing to me.

This is fine. But the splits for reading an Iceberg table will always come in with extraFileInfo["table_format"]="iceberg"

This is fine. But the splits for reading an Iceberg table will always come in with extraFileInfo["table_format"]="iceberg"

This is not guaranteed for future table formats

This is fine. But the splits for reading an Iceberg table will always come in with extraFileInfo["table_format"]="iceberg"

This is not guaranteed for future table formats

But Iceberg splits will always come in with this, similar to Hudi. We can guarantee that and their datasource can be constructed accordingly.

This is fine. But the splits for reading an Iceberg table will always come in with extraFileInfo["table_format"]="iceberg"

This is not guaranteed for future table formats

But Iceberg splits will always come in with this, similar to Hudi. We can guarantee that and their datasource can be constructed accordingly.

@yingsu00 We are design the framework for all these table formats, so dispatch at split level is the right thing here

This is fine. But the splits for reading an Iceberg table will always come in with extraFileInfo["table_format"]="iceberg"

This is not guaranteed for future table formats

But Iceberg splits will always come in with this, similar to Hudi. We can guarantee that and their datasource can be constructed accordingly.

@yingsu00 We are design the framework for all these table formats, so dispatch at split level is the right thing here

But you can't mix everything together. These table formats spec are very different to each other and they are quite complex. THere has to be some abstractions, layers and separation of concerns. And how was the decision made?

Superseded by #7362


Tensor zero_padding2d_1_input:0, specified in either feed_devices or fetch_devices was not found in the Graph

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
custom
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
none
TensorFlow installed from (source or binary):
binary
TensorFlow version (use command below):
v1.14.0-rc1-22-gaf24dc9 1.14.0
Python version:
Python 3.7.4
Bazel version (if compiling from source):
none
GCC/Compiler version (if compiling from source):
none
CUDA/cuDNN version:
none
GPU model and memory:
CPU model

Describe the current behavior
This issue happens when running the Tensorflow model inference in a Tornado server started as a Thread.
class WebServer(threading.Thread):
    def run(self):
        application.listen(8888)
        #asyncio.set_event_loop(asyncio.new_event_loop())
        asyncio.set_event_loop(AnyThreadEventLoopPolicy())
        tornado.ioloop.IOLoop.instance().start()
WebServer.start()

Describe the expected behavior
Code to reproduce the issue
Inference running without any issue. The issue does not occur when it starts running on the main thread instead:
application.listen(8888)
application.listen(8888)
tornado.ioloop.IOLoop.instance().start()

Other info / logs
This error happens on both Tensorflow models I run, so I assume it's a threading problem when running the Graph in a thread that it is not the main thread.
The only error logging I get is
 Tensor zero_padding2d_1_input:0, specified in either feed_devices or fetch_devices was not found in the Graph

[NOTE]
According to here, I have tried to run model.predict in my session so I did
    with session.as_default():
        with session.graph.as_default():
            labels = np.round(model.predict(X)[0])

            prediction = []

            for i in range(0, len(labels)):
                if labels[i] == 1:
                    prediction.append(labels_group[i])

            return prediction

but now getting a
Error while reading resource variable block4_conv2/kernel from Container: localhost. This could mean that the variable was uninitialized. Not found: Container localhost does not exist. (Could not find resource: localhost/block4_conv2/kernel)
	 [[{{node sequential_1_3/block4_conv2/convolution/ReadVariableOp}}]]

[NOTE]
I was able to solve this issue creating a new global session and then setting it to keras before loading the model as stated in https://github.com/tensorflow/tensorflow/issues/28287#issuecomment-495005162:
   def load_tensorflow_shared_session(self):
        """ Load a Tensorflow/Keras shared session """
        # LP: create a config by gpu cpu backend
        if os.getenv('HAS_GPU', '0') == '1':
            config = tf.ConfigProto(
                device_count={'GPU': 1},
                intra_op_parallelism_threads=1,
                allow_soft_placement=True
            )
            config.gpu_options.allow_growth = True
            config.gpu_options.per_process_gpu_memory_fraction = 0.6
        else:
            config = tf.ConfigProto(
                intra_op_parallelism_threads=1,
                allow_soft_placement=True
            )
        # LP: create session by config
        self.tf_session = tf.Session(config=config)

        return self.tf_session

and then passing this shared session to all TF /Keras models:
def load__model(MODEL_PATH, session):
    '''
        Load the model
    '''

    # IMPORTANT: models have to be loaded AFTER SETTING THE SESSION for keras!
    # Otherwise, their weights will be unavailable in the threads after the session there has been set
    set_session(session)
    model = keras.models.load_model(MODEL_PATH)
    model._make_predict_function()

Instead of using global session object I'm using a singleton object that retains this.tf_session, by the way it works in both ways.

@loretoparisi Can you please check with the latest versions in TF1.15.3 and let us know whether the issue persists? Thanks!
Please feel free to close the issue if the issue was resolved for you. Thanks!

@jvishnuvardhan ok I will confirm.

@loretoparisi Are you confirming that this is an issue with TF1.15.3 or your are confirming that this is already resolved for you? Thanks!

@jvishnuvardhan I confirm that this has been resolved. I have investigated the solution. The problem was related to a wrong handling of the TF session through different models loaded on the same server (multi-processing application server so with the same shared session). The solution was a common shared session, passed through all loaded models.


edgeql: Verify that operators and implicit casts work.

Add exhaustive tests for all valid scalar types and all defined
operators except ?? and IF...ELSE (these 2 operators have a
different implementation from the others). The tests validate that
the operators are legal between specific scalar types and that the
return type is also inferred correctly.

I've added tests for ?? and IF/ELSE.


Abuse Checkpoint.redo field to distinguish shutdown checkpoints

This is for PR #6560. It implements the scheme I envisioned at https://github.com/neondatabase/neon/pull/6560#issuecomment-2517233039

@knizhnik if this looks good to you, can you absorb it to your PR please?


Error getting data from the stash server

When clicking play in external player I get "Error getting data from the stash server. Returned code:422". It happens regardless of which player is selected. Weirdly if I add the scene to a playlist then click send playlist to external player the playlist loads in the player fine.
Only seems to happen when running from a remote setup, when running local it works fine.

Thank you for creating this issue !  The new update will surely fix it.


Fix pre-release tests

@ilan-gold this should unblock you
See https://github.com/scverse/anndata/issues/1434 (doesn‘t fix that one though)

Scipy is unlikely to change their implementation to not use copy=True, so it’s on us to make this work.
Since it’s not a temporary bug in scipy but a change that broke us, I introduced a temporary upper bound (as opposed to a !=1.13.0.rc1 constraint) until we have a fix.

In an ideal world, all past anndata versions would have the same bound, but that’s impossible to do.

I believe conda-forge actually allows this

Yeah, I was thinking about PyPI. There it would also kinda maybe be possible by yanking everything and releasing .post1 releases but I don't think that's a reasonable standard to hold ourselves to and it would force people to change their lock files


Add '--no-reminders' option and use in the README.md build

Work for this issue will begin begin on branch work-liquid-labs/cloudsite/126.


Countdown timer in minutes suggestion

It would be great to add an option to switch countdown timer in minutes or seconds.

Hi otejiri, I have added the option to switch the countdown between minutes or seconds.
Use the following option in setting
timerType: 0(seconds)/1(minutes)
For more information on the document, please refer below
github: https://github.com/parteek111269/angular-otp-package
npm: https://www.npmjs.com/package/angular-otp-box
Regards


Way to jump to the running chunk

Maybe a link in the running tag in the navbar...

 Way to jump to the running chunk


[guide/examples] Switch from --target no-modules to --target web now

All major browsers have supported ES modules in web workers for at least a year now. Firefox was the last one to catch up, it seems, and it added support in version 114 (2023-06). See MDN.
As a newcomer wanting to play around with Wasm in web workers, I want to know the most modern/standardized way to do things with wasm-bindgen.
Therefore, I request that the following examples and pages in the wasm-bindgen guide be updated to use the newer --target web instead of --target no-modules.
https://github.com/rustwasm/wasm-bindgen/blob/e4f8c4540aee2f3c0798fdae51ac7dace28e102b/guide/src/examples/wasm-in-web-worker.md?plain=1#L13-L16
https://github.com/rustwasm/wasm-bindgen/blob/e4f8c4540aee2f3c0798fdae51ac7dace28e102b/guide/src/examples/raytrace.md#L60-L61

This should be quite straightforward to do, I'm happy to review a PR!


Improve visualization page in backoffice

Just opening an issue to track what should be done on visualizations to allow displaying up to data information to decision makers following discussion with @dulacarnold @tgy .
Short term
Currently we have the ability to render any plots in some folder into the /bo/operational-dashboard page.
We would need to,

[x] merge https://github.com/icubam/icubam/pull/222 to re-generate predicu plots periodically in the backoffice server  and check that it doesn't explode memory on the server due to unclosed objects in matplotlib
[x] at least add descriptions to predicu plots and decide which ones we should show
[x] check results consistency and apply some filtering on the raw data if needed (as done for off-line reports)
[x] add token based authentication for this page, that should only give access to this page and nothing else

Mid term
Mid term we might want to move the plot generation to separate webservice to make it a bit more interactive and not need to generate plots for a cartesian product of all possible options (regions, cities, time durations, etc). If we go this road, we can certainly get rid of the bokeh figure and close https://github.com/icubam/icubam/issues/154

A status update on this is that after https://github.com/icubam/icubam/pull/350 is merged, we can display all plots without any formatting at http://localhost:8890/bo/operational-dashboard the callback to generate plots will also work (put at least 4 hours periodicity to avoid memory issues on the server).
Now we focus only on latest @fplandes 's plots "flux_dept_lits_dept_visu_4panels" that are done by region and department.
Next steps are,

[ ] add token based authentication (still)
[ ] improve layout in particular we want to be able to select a region or department and see the plot for it. This means we need a way to generate the correct path to the corresponding image (e.g. /bo/static/extra-plots/flux-lits-dept-Ardennes.png) for a given Region / departments. Issues there are non ascii characters in names, related to https://github.com/icubam/icubam/issues/312.
[ ] we may want to split each plot in two: for covid+ and covid- information and display them on several tabs.
[ ] double check information on the plots. Plot generation currently produces a lot of verbose information (e.g. about departments missing) which might need investigation.

Closing as resolved.


Add Global CIDR to Cluster CRD

There is a growing need to be able to support multi cluster networking
across brownfield deployments that have limited abilities to create non
overlapping CIDRs for their Pod(s) and Service(s) networks. As discussed
during some meetings this can be addressed by having a Global multi
cluster network that is non-overlapping and can do NATting while still
be able to leverage the advantages that Submariner brings.
This patch adds the ability to define a Global CIDR segment associated
with a specific cluster and store the information as part of the
cluster's Cluster CRD. The autogenerated part was added by executing
./scripts/codegen

This change is

Should you also add it to GetLocalCluster in util package?

That was coming in another bigger patch. One thing is adding the attribute, another thing is using it. I thought segregating the both.

Seems artificial but however you want, that usage though is general to
adding a field IMHO and not specific to the field itself (which you should
do anyway but that is better off in a different patch, hence I didn't say
anything about that here).
On Thu, Nov 21, 2019 at 2:41 PM Michel Peterson<EMAIL_ADDRESS>wrote:

Should you also add it to GetLocalCluster in util package?
That was coming in another bigger patch. One thing is adding the
attribute, another thing is using it. I thought segregating the both.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/submariner-io/submariner/pull/213?email_source=notifications&email_token=AMFWHC3JPEB5ALN2OAI5UMTQUZ6YTA5CNFSM4JNKNJD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE2C3PI#issuecomment-557067709,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMFWHCY6VYD442FEKVZDRQLQUZ6YTANCNFSM4JNKNJDQ
.

--
Regards,
Mike

@Oats87 can you have an eye on @mpeterson proposition, that's being worked out on a separate branch from master for now.

Guys I can merge anytime you want not sure about the ordering so just tell me


and rule

The Session is now drawing to a close, and if these things are done before Parliament is prorogued, who can tell to what extent injustice and tyranny may go on in Ireland during the Recess?
session-drawing-now
session-drawing-to-close
injustice-go-during-Recess (also get these)
injustice-go-in-Ireland (also get these)
tyranny-go-during-recess
tyranny-go-in-Ireland
who-tell-injustice

But, as this low rate of exchange made it difficult for the Indian Government to pay its gold debt in England, the Indian Government made a volte face, became reckless, and closed the mints.
Government-became-reckless
Government-closed-mints

It seemed to him that no course could be so dangerous as, in a case where the natives were so numerous, intelligent, and warlike as in New Zealand, to give power to any portion of the Colonists to establish an internal superiority over the natives.
also get:
natives were warlike
natives were intelligent

The Session is now drawing to a close, and if these things are done before Parliament is prorogued, who can tell to what extent injustice and tyranny may go on in Ireland during the Recess?
injustice and tyranny


Use argument name

The method's argument is named "identifier" so indicating that in the error message is helpful.

Coverage remained the same at 97.525% when pulling 30ed53efc528b25cbb062afb69f2e0b7bebad905 on tt:use-argument-name into 30757b3efe4e5412a06f985c0b8c7c896a16b96e on localmed:master.

Coverage remained the same at 97.525% when pulling 30ed53efc528b25cbb062afb69f2e0b7bebad905 on tt:use-argument-name into 30757b3efe4e5412a06f985c0b8c7c896a16b96e on localmed:master.


Commit type "perf" increments a PATCH version

I noticed that, when merging a PR with only a perf commit, the conventional changelog action bumped a PATCH version. Is that the expected behaviour? Shouldn't a PATCH version only be bumped when there's a fix commit?
Run TriPSs/conventional-changelog-action@v3
  with:
    github-token: ***
    release-count: 0
    skip-version-file: true
    skip-commit: false
    git-message: chore(release): {version}
    git-user-name: Conventional Changelog Action
    git-user-email<EMAIL_ADDRESS>    git-pull-method: --ff-only
    git-push: true
    git-branch: refs/heads/main
    preset: angular
    tag-prefix: v
    output-file: CHANGELOG.md
    version-file: ./package.json
    version-path: version
    skip-git-pull: false
    skip-on-empty: true
    fallback-version: 0.1.0
    git-url: github.com
    skip-ci: true
    create-summary: false
Using "angular" preset
Using "chore(release): {version} [skip ci]" as commit message
Using "Conventional Changelog Action" as git user.name
Using<EMAIL_ADDRESS>as git user.email
Using "0" release count
Using "./package.json" as version file
Using "version" as version path
Using "v" as tag prefix
Using "CHANGELOG.md" as output file
Using "" as config file
Using "github.com" as gitUrl
Using "main" as gitBranch
Skipping empty releases is "enabled"
Skipping the update of the version file is "enabled"
Pull to make sure we have the full git history
/usr/bin/git config user.name Conventional Changelog Action
/usr/bin/git config user.email<EMAIL_ADDRESS>/usr/bin/git remote set-url origin ***github.com/luizpcarvalho/semantic-versioning-test-[2](https://github.com/luizpcarvalho/semantic-versioning-test-2/runs/7348242357?check_suite_focus=true#step:3:2).git
/usr/bin/git rev-parse --is-shallow-repository
true
/usr/bin/git pull --unshallow --tags --ff-only
From https://github.com/luizpcarvalho/semantic-versioning-test-2
 * [new branch]      dev        -> origin/dev
 * [new branch]      fix/update-release-count -> origin/fix/update-release-count
 * [new tag]         v0.1.0     -> v0.1.0
 * [new tag]         v1.0.0     -> v1.0.0
 * [new tag]         v1.1.0     -> v1.1.0
 * [new tag]         v2.0.0     -> v2.0.0
 * [new tag]         v[3](https://github.com/luizpcarvalho/semantic-versioning-test-2/runs/7348242357?check_suite_focus=true#step:3:3).0.0     -> v3.0.0
 * [new tag]         v3.1.0     -> v3.1.0
 * [new tag]         v3.1.1     -> v3.1.1
 * [new tag]         v3.1.2     -> v3.1.2
 * [new tag]         v3.1.3     -> v3.1.3
 * [new tag]         v3.2.0     -> v3.2.0
 * [new tag]         v3.2.1     -> v3.2.1
Already up to date.
Recommended release type: patch
Because: There are 0 BREAKING CHANGES and 0 features
Using GIT to determine the new version
Changelog generated
## [3.2.2](https://github.com/luizpcarvalho/semantic-versioning-test-2/compare/v3.2.1...v3.2.2) (2022-07-1[4](https://github.com/luizpcarvalho/semantic-versioning-test-2/runs/7348242357?check_suite_focus=true#step:3:4))
### Performance Improvements
* test if perf bumps version ([9bc732d](https://github.com/luizpcarvalho/semantic-versioning-test-2/commit/9bc732d329a[5](https://github.com/luizpcarvalho/semantic-versioning-test-2/runs/7348242357?check_suite_focus=true#step:3:5)487720add83d2b3e8875c[6](https://github.com/luizpcarvalho/semantic-versioning-test-2/runs/7348242357?check_suite_focus=true#step:3:6)ad1af5))
New version: 3.2.2
/usr/bin/git add .
/usr/bin/git commit -m chore(release): v3.2.2 [skip ci]
[main 6185e5[7](https://github.com/luizpcarvalho/semantic-versioning-test-2/runs/7348242357?check_suite_focus=true#step:3:7)] chore(release): v3.2.2 [skip ci]
 1 file changed, 9 insertions(+)
/usr/bin/git tag -a v3.2.2 -m v3.2.2
Push all changes
/usr/bin/git push origin main --follow-tags
To https://github.com/luizpcarvalho/semantic-versioning-test-2.git
   bc49662..61[8](https://github.com/luizpcarvalho/semantic-versioning-test-2/runs/7348242357?check_suite_focus=true#step:3:8)5e[57](https://github.com/luizpcarvalho/semantic-versioning-test-2/runs/7348242357?check_suite_focus=true#step:3:58)  main -> main
 * [new tag]         v3.2.2 -> v3.2.2

Do you happen to have a link for angular's definition on what version is incremented based on commit types? I couldn't find that information in any of the documentation I read.

The specification can be found here

Semantic versioning is about public API. So anything a user can notice (be it their code no longer compiling due to a breaking change, new feature, bugs, or a slower/faster performance) should increment the version number.
So I agree with @TriPSs that a perf commit should increment the PATCH version since performance is clearly a part of the public API while not being a new feature.


Toggle help window doesn't work

_unhandled_input() in HelpWindow.gd doesn't fire when mouse is captured (mouse is hidden) from capture_mouse in SmoothWorld.gd:
capture_mouse(value):
#...
Input.set_mouse_mode(Input.MOUSE_MODE_CAPTURED)
ui_root.process_mode = Node.PROCESS_MODE_DISABLED
set_ui_element_mouse_filter(ui_root, false)

This makes H to toggle help window not work when mouse is captured.

Fixed.


Instruction to Add to Laravel 5.2

I have looked at the Admin-LTE and it definately looks inviting.
I have already setup a website and would like to started using the Admin LTE. How would one go about setting it up on a site that has already been created? What would need to be changed? Would we change the compose.json file?

Hi @dkpinn , The package laravel-admin-generator is just another generator for Laravel, which dose two things

Generate a start up backbone with Admin-LTE or SB-Admin
Generate entities base on your business

Admin-LTE indeed looks inviting, while laravel-admin-generator just copy its js,css files to the right destinations automaticlly
There an instruction about how to use the package: https://github.com/lokielse/laravel-admin-generator/tree/master/docs
P.S. I used to create many admin sites, and I found that I always do the same things which waste much time. That is the reason I create this generator.