Add new project

Under admin controller create a function to add new project. See the issue of project schema for the fields required in the projects

i would like to work on this!

@nanda-mik I can't find you in the whatsApp group . Please join the whatsapp group asap. After that I will assign.

Where is the link to join?

In the Slack channel

I am unaware about these things! Where i will get link to join slack?

I can work on this

@nanda-mik Aren't you a part of GSSoC extended? If so you would have received the slack invitation .

@pratikbaid3 I am assigning you

@gauravdas014 No i am not a part of Gssoc. So, am i not eligible to contribute to any project under gssoc?

@nanda-mik This project is only for those who are part of GSSoC extended.

@gauravdas014 Since the project schema is not done yet but the issue for it has been assigned, should I make the schema myself??

Yes create a simple schema for now.


testing sockets

I cant find any resource about testing app connected to backend via sockets. Specifically, I'm trying to test angular/angularfire app with firebase and didn't find any batter solution except protractor.promise.delayed(xxx). Is it regular way to do that? Angularfire team also use this style testing in their specs, but just want to check here does it recommended solution for web sockets testing in general?

It really depends on what you're trying to test or wait for. If there's some indication in your application that an event has happened (e.g. a spinner), then you can wait on the presence or absence of that element using browser.wait. If what you want to test is really that something happens after a specific timeout, then promise.delayed seems like a good solution.
Since this is not an bug or feature request for Protractor I'm going to close the issue. Please open up a question on Stack Overflow if you'd like to get more opinions.


Generation failing when discriminator is only declared on the base object schema

Hi @yonaskolb, I'm back with a new discriminator issue. In this sample spec, the discriminator is only declared on the base Pet object and does not generate correctly. GetPets.Response is empty.
info:
  version: 1.0.0
  title: Example API
  description: >
    This is an example API excercising the discriminator syntax.
servers:
  - url: http://petstore.swagger.io/v1
paths:
  /pets:
    get:
      responses:
        '200':
          description: fetch a list of pets
          content:
            application/json:
              schema:
                type: object
                required:
                  - data
                properties:
                  data:
                    type: array
                    items:
                      '#/components/schemas/Pet'

components:
  schemas:
    Pet:
      type: object
      required:
        - pet_type
      properties:
        pet_type:
          type: string
      discriminator:
        propertyName: pet_type
    Dog:     # "Dog" is a value for the pet_type property (the discriminator value)
      allOf: # Combines the main `Pet` schema with `Dog`-specific properties
        - $ref: '#/components/schemas/Pet'
        - type: object
          # all other properties specific to a `Dog`
          properties:
            bark:
              type: boolean
            breed:
              type: string
              enum: [Dingo, Husky, Retriever, Shepherd]
    Cat:     # "Cat" is a value for the pet_type property (the discriminator value)
      allOf: # Combines the main `Pet` schema with `Cat`-specific properties
        - $ref: '#/components/schemas/Pet'
        - type: object
          # all other properties specific to a `Cat`
          properties:
            hunts:
              type: boolean
            age:
              type: integer```

Hey @yonaskolb, have you had a chance to look at this?

Hi @chaseacton
Firstly your response is misconfigured: the array items would need to be a $ref
items:
  $ref: '#/components/schemas/Pet'

Then it would generate as Pet and not [String: Any]
Secondly at this time SwagGen does not support using discriminators in allOf class hierarchies, only in oneOf cases.
To get this to work you must declare it like this
paths:
  /pets:
    get:
      responses:
        '200':
          description: fetch a list of pets
          content:
            application/json:
              schema:
                type: object
                required:
                  - data
                properties:
                  data:
                    type: array
                    items:
                      oneOf:
                        - $ref: '#/components/schemas/Cat'
                        - $ref: '#/components/schemas/Dog'
                      discriminator:
                        propertyName: pet_type
                        mapping: # only required if pet_type is not Cat and Dog
                          cat: '#/components/schemas/Cat'
                          dog: '#/components/schemas/Dog'

I hope that helps!


Add model export for a few layers, missed in ModelSaver.kt

Each layer should be exported in JSON, Keras compatible format
The following layers are missed in ModelSaver.kt

Concatenate
ZeroPadding2D
DepthwiseConv2D
SeparableConv2D

NOTE: some another layers' export, like Activation or merge layers like Subtract and so on are parts of other PRs now

I'll take this one.


No key updates for key: EF6E286DDA85EA2A4BA7DE684E2C6E8793298290

http://storage5.static.itmages.com/i/17/1028/h_1509198394_5620215_6da637e29e.png
Hi, just tried to update tor and i'm getting the above error 'Signature Verification Failed'. I updated my Tor keys using:
gpg --homedir "$HOME/.local/share/torbrowser/gnupg_homedir/" --refresh-keys --keyserver pgp.mit.edu
I'm using DNSCrypt so either something is wrong with that or you've made a mistake of some sort?

For Gentoo, it just stucks at "Verifying Signature".
When starting it in foreground, I get get following:
ramon@lenovo ~ % torbrowser-launcher
Gtk-Message: Failed to load module "canberra-gtk-module"
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.8
https://github.com/micahflee/torbrowser-launcher
Refreshing local keyring...
Keyring refreshed successfully...
  No key updates for key: EF6E286DDA85EA2A4BA7DE684E2C6E8793298290
Downloading and installing Tor Browser for the first time.
Downloading https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
Latest version: 7.0.8
Downloading https://www.torproject.org/dist/torbrowser/7.0.8/tor-browser-linux64-7.0.8_en-US.tar.xz.asc
Downloading https://www.torproject.org/dist/torbrowser/7.0.8/tor-browser-linux64-7.0.8_en-US.tar.xz
Verifying Signature

I get the same problem on ubuntu:
Running it from the command line:
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.4
https://github.com/micahflee/torbrowser-launcher
Downloading and installing Tor Browser for the first time.
Downloading https://dist.torproject.org/torbrowser/update_2/release/Linux_x86_64-gcc3/x/en-US
Latest version: 7.0.10
Downloading https://www.unicorncloud.org/public/torproject.org/disttorbrowser/7.0.10/tor-browser-linux64-7.0.10_en-US.tar.xz.asc
Downloading https://www.unicorncloud.org/public/torproject.org/disttorbrowser/7.0.10/tor-browser-linux64-7.0.10_en-US.tar.xz
Verifying signature

Updating my keys with:
gpg --homedir "$HOME/.local/share/torbrowser/gnupg_homedir/" --refresh-keys --keyserver pgp.mit.edu
gpg: refreshing 1 key from hkp://pgp.mit.edu
gpg: requesting key 93298290 from hkp server pgp.mit.edu
gpg: key 93298290: "Tor Browser Developers (signing key<EMAIL_ADDRESS>not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

@Danielgb23 the version you use is too old.
if you use debian, you can try latest version [0], even on backports [0].
[0] https://wiki.debian.org/TorBrowser

@rogers0 I updated it to 0.2.8 but I still get the same error. Only that two  lines were added to the command line output's end.
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.8
https://github.com/micahflee/torbrowser-launcher
Refreshing local keyring...
gpgkeys: HTTP fetch error 1: unsupported protocol
Downloading and installing Tor Browser for the first time.
Downloading https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
Latest version: 7.0.10
Downloading https://www.unicorncloud.org/public/torproject.org/disttorbrowser/7.0.10/tor-browser-linux64-7.0.10_en-US.tar.xz.asc
Downloading https://www.unicorncloud.org/public/torproject.org/disttorbrowser/7.0.10/tor-browser-linux64-7.0.10_en-US.tar.xz
Verifying Signature
Refreshing local keyring...
gpgkeys: HTTP fetch error 1: unsupported protocol


recipe/CEN-6951_video_to_image

Completed recipe.

@gordonwade I have updated with the necessary changes. Please review.


[Header]  Menu navigation tab 'Про нас' is not highlighted while you are on this page

Environment: Windows 7, Service Pack 1, Google Chrome, 90.0.4430.212 (Розробка) (64-розрядна версія).
Reproducible: always.
Build found: the last commit
Preconditions
Open https://speak-ukrainian.org.ua/dev
Steps to reproduce

Go to 'Про нас' page
Look at the navigation menu bar

Actual result
Menu navigation tab 'Про нас' is not highlighted while you are on this page.

Expected result
Menu navigation tab 'Про нас' should be highlighted while you are on this page

User story and test case link
E.g.: "User story #371
Test case"

It is fixed in build 27.05.2021https://speak-ukrainian.org.ua/dev/


Datepicker autoClose doesnt work

Current Behavior
When select a date picker doesnt close automatically.
Steps to Reproduce (for bugs)
https://codepen.io/anon/pen/qYrLBE
var elem = document.querySelector('.datepicker');
var options = {autoClose: true, format: "dd-mm-yyyy"};
var instance = M.Datepicker.init(elem,options);

It will be working in the release coming out today, it was added after the last beta release.

This is still happening on 1.0.0

Still happening on 1.0.0... bump! 👍

Auto Close is still not working!!

I love this framework but properly applying datepicker logic is extremly frustrating as its not registering events properly at all.
autoclose, datechange do notworks as documented

Do any of the events work? I don't think options are being applied at all to DatePicker.

This issues should be reopened.
'this' in _handleClick: https://github.com/Dogfalo/materialize/blob/1122efadad8f1433d404696f7613e3cc13fb83a4/js/datepicker.js#L818
Doesn't seem to be the same instance that is initialized here: https://github.com/Dogfalo/materialize/blob/v1-dev/js/datepicker.js#L120
At least the options are completely different in the handler. this.options in the handler seem to be the default options even tho the options passed in seemed to be applied correctly in the constructor.

Alright, I decided I would create a PR to fix this and figured out I didn't need to. I think the issue is that npm has a broken build. It needs to be updated. If you change your package.json to reference the 1.0.0 tag, it will work: "materialize-css": "github:dogfalo/materialize#1.0.0",


TypeError: compiler.plugin is not a function

Bug report

What is the current behavior?
"build": "webpack --mode production",
"dev": "webpack serve --mode development --open --watch"
Unsuccessful builds with error: TypeError: compiler.plugin is not a function
It happened after install webpack-md5-hash.
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Successful build

Other relevant information:
webpack version:  5.3.0
Node.js version: 12.18.3
Operating System: Win10
Additional tools:
Files with configs: https://github.com/dubovik02/config

Please open an issue in webpack-md5-hash (no compatibility with webpack@5), anyway you don't need this plugin for v5, webpack do it for mode: 'production'


tsconfig: exclude not working as expected

I would like to exclude node_modules from my compilation but still be able to reference d.ts files within. Imagine the following scenario: I want to depend on one node module that comes with a d.ts file. If I exclude node_modules, this d.ts file will never be found. If I do not exclude node_modules, I might drag in other d.ts files that I dont want.
The best solution imho would be:

allow me to exclude node_modules
if there is a import for a module, still use node.js module resolution logic to find the d.ts file

In other words, never let the exclude property in tsconfig.json prevent the tsc look up logic to look into node_modules as needed.

What you are explaining is the expected behavior. if you seeing something different it is a bug. can you please provide more information and preferably a repro project?

@mhegazy ok I might have spoken too soon, I can get tsc to compile the following project: https://github.com/bpasero/attachments/blob/master/test.zip?raw=true
What worries me is that I can rename the folder "issue" inside node_modules to "issue2" and everything still compiles. I can also rename issue.d.ts to issue2.d.ts and it will still work.
I would probably expect that if I do a import * as issue from 'issue'; that you would only ever look for a issue.d.ts in a folder called issue anywhere in the node_modules hierarchy?

@mhegazy ok and now I have a case where the exclude seems to fail: https://github.com/bpasero/attachments/blob/master/test_2_fail.zip?raw=true
The typescript module is within node_modules and even though I exclude node_modules in the tsconfig.json I get errors when I compile:
node_modules/typescript/lib/lib.core.d.ts(1168,28): error TS1005: ';' expected.
node_modules/typescript/lib/lib.core.d.ts(1168,31): error TS1005: ';' expected.
node_modules/typescript/lib/lib.core.d.ts(1168,41): error TS1005: '(' expected.
node_modules/typescript/lib/lib.core.d.ts(1169,26): error TS1005: '(' expected.
node_modules/typescript/lib/lib.core.d.ts(1170,1): error TS1128: Declaration or statement expected.
node_modules/typescript/lib/lib.core.es6.d.ts(1168,28): error TS1005: ';' expected.
node_modules/typescript/lib/lib.core.es6.d.ts(1168,31): error TS1005: ';' expected.
node_modules/typescript/lib/lib.core.es6.d.ts(1168,41): error TS1005: '(' expected.
node_modules/typescript/lib/lib.core.es6.d.ts(1169,26): error TS1005: '(' expected.
node_modules/typescript/lib/lib.core.es6.d.ts(1170,1): error TS1128: Declaration or statement expected.
node_modules/typescript/lib/lib.d.ts(1168,28): error TS1005: ';' expected.
node_modules/typescript/lib/lib.d.ts(1168,31): error TS1005: ';' expected.
node_modules/typescript/lib/lib.d.ts(1168,41): error TS1005: '(' expected.
node_modules/typescript/lib/lib.d.ts(1169,26): error TS1005: '(' expected.
node_modules/typescript/lib/lib.d.ts(1170,1): error TS1128: Declaration or statement expected.
node_modules/typescript/lib/lib.es6.d.ts(1168,28): error TS1005: ';' expected.
node_modules/typescript/lib/lib.es6.d.ts(1168,31): error TS1005: ';' expected.
node_modules/typescript/lib/lib.es6.d.ts(1168,41): error TS1005: '(' expected.
node_modules/typescript/lib/lib.es6.d.ts(1169,26): error TS1005: '(' expected.
node_modules/typescript/lib/lib.es6.d.ts(1170,1): error TS1128: Declaration or statement expected.

Sorry, I was running with a globally installed 1.5.x and this caused all these issues. It works fine now, especially since I discovered https://github.com/Microsoft/TypeScript/wiki/Typings-for-npm-packages
I really like how this was pushed for 1.6, makings typings a lot more understandable!

glad that was resolved.


Unable to find widget in scope when declared within an item block

The desired element could be found by as follows:
widget(:list).last.root.find('item root selector)

@murtys Please feel free to clarify and we can reopen this.


requirements: Update pygments to 2.11.1

Updating from pygments 2.10.x to 2.11.x brings new lexers,
including the new Savi lexer which is needed by the Savi community
in our Zulip chat at https://savi.zulipchat.com/
Testing plan: I haven't done any testing locally. I'm hoping the CI test suite is adequate for testing a requirement version update like this.

Notes: To make this change, I temporarily added a specific version for pygments to requirements/common.in, then ran tools/update-locked-requirements, but did not commit the temporary change in requirements/common.in.

Merged after updating PROVISION_VERSION so that development environments will update. I'm not even sure if that was necessary, since we don't have any tests affected by this.  In any case, thanks for the PR @jemc!
This should make it to Zulip Cloud by early next week.

Exciting!
Thanks for the merge, and for the great product.


Concurrent Bulk API Query Limit

Are there concurrent request limits for the Salesforce Bulk API? If so, what are they? If I use JSForce, are they handled / are additional requests queued up? Is it common to see ECONNRESET errors on an open connection when the limit is reached.

ECONNRESET is the error thrown in Node.js socket lib and it shows TCP session is closed by the peer. I'm not sure when they (Salesforce) will do it because no manuals says about it AFAIK, but some protection might be working in the provider's side.


ValueError: Gas estimation failed

Hi, I am a new user of brownie. I keep getting this error when I'm running chainlink_api_scripts/02_request_api.py. I wonder what could go wrong. Thank you for your explanation.
ValueError: Gas estimation failed: 'execution reverted'. This transaction will likely revert. If you wish to broadcast, you must set the gas limit manually.

hi @dennislblog , does the wallet linked to your account used to deploy/interact with contracts have at least 1 LINK in it, and also some ETH?

Thank you for your explanation. It works indeed after I add some coins to my account.


Fixes : https://github.com/huggingface/nanotron/issues/114

Implementation of 1.58bit LLM with Llama following the paper & handbook released by Microsoft :
https://github.com/microsoft/unilm/blob/master/bitnet/The-Era-of-1-bit-LLMs__Training_Tips_Code_FAQ.pdf
Here are The training results on 25B tokens :

cc @NouamaneTazi @xrsrke @thomwolf

I think it has to do with the batch size. During our latest experiment, we trained the 1.58 model on 100B tokens, and we managed to get a 2.8 loss after 25B tokens with a batch size of 1024

Hi, I fetched this pr, and fintune the llama 70B using tp=8 or pp=8, before training, I have convert the llama 70B into nanotron format using this method: https://github.com/huggingface/nanotron/pull/174, but got this error:

so, how to finetune the 70B model into 1.58bit from scratch? could you give me some suggestion please? thank you!

Hey @hjc3613 thanks for the report ! you don't have to be consitent with the convert config, it should work I will investigate that! Can you tell me from your side what is the content of models/qwen2.5-72b-instruct-nanotron/model/model/decoder/0/pp_block/MLPBitNet

Hey @hjc3613 thanks for the report ! you don't have to be consitent with the convert config, it should work I will investigate that! Can you tell me from your side what is the content of models/qwen2.5-72b-instruct-nanotron/model/model/decoder/0/pp_block/MLPBitNet

thank you very much!
My requirement is to successfully fine-tune a 70B model to a 1.58bit model, using either Qwen2.5 70B or LLama 70B - both have almost identical model architectures. According to the training code, I need to provide a dataset and a base model in nanotron format, which will then be fine-tuned to 1.58bit for inference. However, I only have a HF version of the base model, so following PR174, I'm first converting it to nanotron format. Before conversion, I need to set dp=1, pp=1, tp=1. After conversion, I'm using the code from PR180 for training. This is what I'm currently doing - if there are any unreasonable or unnecessary steps, please advise. Thank you sincerely. To my understanding, a 70B model must have pp>1 or tp>1, as a single GPU card cannot hold the complete model.

Hi @MekkCyber !
Similar to what @hjc3613 wanted to try, I am trying to fine-tune the Llama3-8B-1.58-100B-tokens model on a downstream task. (I have been detailing my progress in this Hugging Face discussion thread)
So far I think I managed to correctly unpack the weights of the model using the functions provided by you, but the convert_hf_to_nanotron script from this PR seems to not copy the weight_scale layers into the nanotron-format model (even after messing around with the quantization_config), resulting in a model that is outputting garbage when using the run_generate script with it (as a sanity check).
I am unsure if this is expected and if I should continue with fine-tuning, having the model in this state. I would appreciate any help or guidance you could provide on this matter.


Base Component without StateMachine

Hi,
We have a lot of components which don't use any of the State methods from StateMachine. A lot of little UI widgets are simple and ideally should be built off an lng.Component without StateMachine. I suspect this will reduce memory footprint quite a bit.

Hey, yeah we're aware of this fact. Also we're rewriting that specific part (component creation) and hope to share more information soon

Any updates on this? cc @erikhaandrikman


LiveDirectory for static assets in Hyper-Express sometimes does leaves connection hanging

Hello, I am trying to use LiveDirectory to serve static assets with Hyper-Express like this:
const LiveAssets = new LiveDirectory({ path: './public' });
app.get('/*',(req, res) => {
  const found = LiveAssets.get(req.path);
  if (!found) return res.status(404).send();
  res.type(found.extension).send(found.buffer);
});

I am working on integrating passportjs with hyper-express based on the passportjs example I forked here:
https://github.com/MichaelJCole/hyper-express-sessions-passport-local
When I start the server and reload in chrome, almost always the server connections hang on some of the static assets.  If I reload 20ish times, the assets server just fine.
To reproduce, try the master branch.  I'm using node 14.18.1.  Firefox 95.0.2.

Am I using this wrong?  Thank you!

The snippet you posted above looks fine so there is likely some problem in one of your middlewares which are not continuing their execution. I would say look through all of your middlewares and check to see that you are calling the next() parameter callback or resolving any await promises inside of async middlewares. To narrow down to which middleware is causing the problem, try commenting out the use() calls to each middleware until the problem is resolved.

Hi Kartik, I just moved this to: https://github.com/kartikk221/hyper-express/issues/42.  Ok, I'll try that out and comment there.


Multiple ids for /abort_query

Tried to do a call with multiple ids:
curl -X 'GET'   'http://<IP_ADDRESS>:9000/abortquery/mygraph?requestid=65632.RESTPP_1_1.1640614087990.N&requestid=93.RESTPP_1_1.1640614057969.N'   -H 'accept: application/json'

{"version":{"edition":"enterprise","api":"v2","schema":0},"error":true,"message":"At most 1 values can be provided for parameter requestid, but 2 value(s) are given.","code":"REST-30000"}

got this error: At most 1 values can be provided for parameter requestid, but 2 value(s) are given
The docs suggest that it is doable:
curl -X GET "localhost:9000/abortquery/poc_graph?requestid=16842763.RESTPP_1_1.1561401340785.N&requestid=16973833.RESTPP_1_1.1561401288421.N"

{
  "version": {
    "edition": "enterprise",
    "api": "v2",
    "schema": 0
  },
  "error": false,
  "message": "",
  "results": [
    {
      "aborted_queries": [
        {
          "requestid": "16842763.RESTPP_1_1.1561401340785.N",
          "url": "/sleepgpe?milliseconds=110000"
        },
        {
          "requestid": "16973833.RESTPP_1_1.1561401288421.N",
          "url": "/sleepgpe?milliseconds=100000"
        }
      ]
    }
  ],
  "code": "REST-0000"
}

Check in the newest version of tigergraph (you use 3.3).
BTW: the docs for 3.3 are the same in this matter.

Checked this out in 3.4. The same.
Asked question: https://community.tigergraph.com/t/restpp-abortquery-description/1766

Saw this post. I'll look into it @karol-brejna-i


approved-for-ci-run: carry labels to ci-run/pr-*

We don't carry run-* labels from external contributors PRs to ci-run/pr-* PRs. This is not really convenient.
Need to sync labels in approved-for-ci-run workflow.
          Merging main and doing a CI run to get benchmarks run in https://github.com/neondatabase/neon/pull/7717 (I've added a label to that PR)

Originally posted by @bayandin in https://github.com/neondatabase/neon/issues/7242#issuecomment-2107115847

Last week:

initial implementation
the workflow is flaky

This week:

finish the implementation with the proper GitHub token


Question on setting a new RAMP up [and doc update suggestion]

Hi,
I'm currently writing a starting-kit but one thing remains unclear from the doc: where to put the private data used for the private leaderboard? In can't be distributed along with the starting-kit since it's... private. So it is currently under ramp_deployment/ramp-data/data but ramp-board doesn't have access to that, if I'm not mistaken.
Another question is, is there a workflow for time-series that are grouped into different independent experiments?
Many thanks,

we put the private date in this org https://github.com/ramp-data using
private repos.
We then clone them in the server and run prepare data there.
clear?

So it is currently under ramp_deployment/ramp-data/data but ramp-board doesn't have access to that, if I'm not mistaken.

Basically ramp-board will go pick up the data there. You are giving this path for the events/xxx/config.yml.
As @agramfort mentioned, usually we tend to have a separate repository for these data that we are cloning when deploying.
Finally the public data will always be part of the ramp-kit.

Another question is, is there a workflow for time-series that are grouped into different independent experiments?

I am not sure about that. I think that we have some forecasting at some point but I think this is usually a single experiment.

Alright, thanks for the clarifications.
Is there a naming convention for the private test data filename then?
Inside problem.py, get_train_data() and get_test_data() both refer to the public data, so I guess it's somewhere hard-coded?

So to be complete
ramp-test --submission is taking --ramp-data-dir as an argument. By default (and usually locally), it will search in pwd/data/. On the server side, we set --ramp-data-dir to the ramp-data folder of the kit. Thus it will point on ramp-data/name_kit/data/ where the data will be.
So we require the train/test data to be named the same for both public and private datasets.

All clear, thanks @glemaitre!

Addendum: just saw it is mentioned inside https://paris-saclay-cds.github.io/ramp-docs/ramp-workflow/stable/data.html. Since it is also relevant to ramp-board, may be it should be linked to https://paris-saclay-cds.github.io/ramp-docs/ramp-board/stable/create_new_challenge.html.


Add support for custom domain name resolvers

We needed this feature for a commercial product, maybe it can be of use to someone else too
Cheers
-- Simone

Thanks for sending the contribution!
Would you be able to provide an example how you are creating the client after these changes? I ran the tests, but most of them fail on missing type annotation for the client. When the type is annotated like this
let client: restson::blocking::RestClient<dns::GaiResolver> = RestClient::new_blocking("https://httpbin.org").unwrap();

There is still an error the trait Default is not implemented for GaiResolver.
I will look at this more closely later when I have more time, and also try to see if the explicit type annotation could be avoided altogether. This would keep the interface clean in the basic case where custom resolver is not needed.
If you can provide some further feedback it is much appreciated.

Ok, the Default trait issue should now be resolved (through use of a zero-cost abstraction in the form of a newtype around GaiResolver to provide for the Default trait, we have no idea why it isn't already implemented by hyper, as constructing a GaiResolver is basically a no-op).
About the explicit type annotations, we made the error of assuming that rust would use the default type provided in the structs' definitions when none is specified by the user, but apparently it does not... for reasons that now escape me.
The latest commits contain a proposed solution: the new and new_blocking methods now only exist for RestClient<GaiResolver>. This way old and common-usecase users can keep building the most common type of client exactly like they did before:
let rest_client = RestClient::new_blocking("https://example.org").unwrap();

Users who need a special resolver can use the builder, either setting an appropriate hyper client instance explicitely
let mut http_connector = hyper::client::connect::HttpConnector::new_with_resolver(MyResolver::new());
http_connector.enforce_http(false);
let mut https_connector = hyper_tls::HttpsConnector::from((http_connector, tls_connector.into()));
https_connector.https_only(true);
let https_client = hyper::client::Client::builder()
    .build(https_connector);
let mut rest_client = RestClient::builder()
    .with_client(https_client)
    .build("https://example.org")
    .unwrap();

or by specifying the resolver type without setting an instance, in which case it will be default-constructed:
let rest_client: RestClient<MyResolver> = RestClient::builder()
    .build("https://example.org")
    .unwrap();

This should be 99% backwards compatible, bar cases in which people have over-annotated variable types, because RestClient now has a type parameter. Still I think it is easy and obvious enough to fix in client code that it should not be too big of an issue.
Let me know what you think of it
Cheers 👋

I do like the approach taken here, and it works almost perfectly. As you mentioned, new and new_blocking now work as expected without additional type annotations. However, when using the Builder with defaults the type is still needed.
Previously this was possible
let client = RestClient::builder()
    .timeout(Duration::from_secs(10))
    .build("https://httpbin.org")
    .unwrap();

which would have to be changed either to annotate the type
let client = RestClient::<GaiResolver>::builder()

or use this hacky syntax to make the compiler actually infer the default type
let client = <RestClient>::builder()

The first approach forces the user to over-annotate, and the second one is quite unintuitive. Sidenote about why the default type does not work here: RestClient::builder() is basically same as RestClient::<_>::builder() and the compiler does not infer the default type for _ here. More discussion about this here .
How about also moving builder() inside impl RestClient<GaiResolver> with new? Then if the type needs to be changed the Builder can be created explicitly:
let builder = Builder::<MyResolver>::default();
let client = builder
    .timeout(Duration::from_secs(10))
    .build("https://httpbin.org")
    .unwrap();

I actually just noticed a regression. For some reason HTTPS requests with blocking clients do not work (cargo test get):
thread 'basic_get_https' panicked at 'called `Result::unwrap()` on an `Err` value: HyperError(hyper::Error(Connect, "invalid URL, scheme is not http"))', tests/get.rs:65:53

Seems to be same behaviour whether the blocking client was created with new_blocking or with Builder. HTTP requests seem to work, and also the async client works with both HTTP and HTTPS.
The same tests pass on master, but I cannot immediately spot what is causing the issue with these changes.

How about also moving builder() inside impl RestClient<GaiResolver> with new? Then if the type needs to be changed the Builder can be created explicitly:

Yeah, of course... use is starting to get a bit obscure in the non-default case, but if backwards-compatibility is the main goal, I'd say it's still usable. Maybe the API can be cleaned up in a possible future (breaking) release, if the project ever ends up having one eventually.

Sidenote about why the default type does not work here: RestClient::builder() is basically same as RestClient::<_>::builder() and the compiler does not infer the default type for _ here. More discussion about this here .

Thank you for the link, it's been quite enlightening! (Although a bit disappointing for all the inconsistencies). The different behaviors the compiler has between type position and expression position always trip me up. Also:

let client = <RestClient>::builder()

that's a nice, obscure piece of syntax you got there... I think I have never seen it explicitly documented anywhere... although I guess it arises from normal path parsing rules? So no need to discuss it explicitly as its own thing in the docs, though it is quite surprising if you have never seen it before... basically it solves the issue by pushing RestClient in type position (nested inside of the expression) where the default parameter is correctly considered?
Anyways...

I actually just noticed a regression. For some reason HTTPS requests with blocking clients do not work (cargo test get):

That's weird, i was quite sure we had tested it. We should check again. I'll let you know when we have something new, although we are closed for summer holidays until just about the end of the month, I'll see if I can maybe take a look in my free time before then.

I, of course, try to minimize breaking changes and keep backward compatibility when it is feasible, but I'd say it is not the main "concern" here. While quite unlikely, the new type parameter can be breaking for some already, so I will likely bump the major number anyway.
My thinking is more about the fact that custom resolvers will probably be minority use case, so I would really like to keep the let client = RestClient::builder() //... working as is for the majority.
Unfortunately, the way the compiler handles type defaults is not very helpful here, and we need to jump through hoops to keep the syntax.
Alternative approach still could be to implelement two sets of new() and builder() with one set fixing the type to default resolver. This kind of approach is used e.g. in Vec with allocator type:

Vec::new fixes the allocator type always to Global. This way Vec::new() works for most people without annotating the allocator type.
Vec::new_in allows to change the allocator type

About the obscure syntax. I think this link probably explains it better than I can!
Again, thanks for the time and effort you have put in to iterating the code! And no sweat about not working on this for a while!


redfish next boot support in new interfaces

With the new interfaces design, adding support for new functionality can be handle in nice small increments. This issue is to implement redfish next boot support. I should be able to tackle this here, shortly.

implemented in https://github.com/bmc-toolbox/bmclib/pull/303


feat: Scroll to active Cairo code segment

Cairo editor should automatically scroll to a first highlighted (active) Cairo code segment when moving through the execution trace. It should not scroll if any highlighted code segment is already in a viewport.

Hi @barabanovro, can I hop on this?

Hi, I am a frontend software engineer that recently discovered starknet ecosystem! I really want and I am motivated to start doing my first contributions to the ecosystem, I would be honored to tackle this issue  !

@BlackStarkGoku, the issue is yours!
@princeibs, according to our contributing guidelines, you should present yourself briefly if you are a first-time contributor.


Create SPA development proposal for Q2

Overview of the Feature Request
Just like we did with the beta proposal for the community day, we need to write a new proposal for the next months (Q2). This document will highlight the new features the SPA will include in the upcoming months. This document will be shared with the community at the community day.
What kind of user is the feature intended for?
All of them
What inspired the request?

Discussion with the team

What existing behavior do you want changed?
N/A
Any brand new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this feature request?
N/A

Waiting for some initial feedback from the team.

Waiting for feedback from the team.

I just read through the doc and it looks good. I left a comment about what's included under "write operations".
Also, I didn't want to junk up the doc with "I agree" but I'm glad we're considering NOT having file upload as part of dataset creation. I never use it. I like the idea of the dataset having a database id before I upload files. 😄 Plus, apart from creating datasets with BagIT (I think), we don't easily offer this "create and upload" functionality via the API. (If we do offer it in the SPA, perhaps the API gets a new, testable feature.)
I'll leave this is in Ready for Review to give others a chance.

Wow, thanks @pdurbin for mentioning that the removal of file upload from the dataset creation is being considered as part of this. I had assumed that this proposal would be similar to the beta proposal and changes like this wouldn't be proposed here, so I wasn't planning on following it very closely or contributing much.
I wonder if others on the team haven't chimed in because they assume the same.

I also like the idea of making the file upload a separate step, but maybe we need to consider more the user experience? @jggautier, do you think this would be missed by users?

I've been long in favor of dropping file upload from create, yes.
Whether it would be missed by users - there's one very efficient way to find out for sure.
It would 100% simplify the workflow and reduce the number of places where things can go wrong.

Hi @ekraffmiller. Yeah I think different types of users will notice it. Not sure if they'll wish it was there 🤔
Sorry, my comment was more about the nature of this proposal compared to the beta one and whether others on the team were aware of how it's different and how it affects what kind of work would be involved and who should be involved. The great conversation in the dv-tech Slack channel yesterday is more along the lines of what I was getting at.

Closed, as the proposal has been reviewed and refined based on team feedback.


Thundernetes and Virtual Kubelet

We should test thundernetes with Virtual Kubelet on AKS and work on guidance/documentation/best practices.

thundernetes uses initcontainers (GSDK) and DaemonSets (NodeAgent) so Virtual Kubelet cannot be used at this time (source)

Moreover, Virtual Kubelet Node does not get a Public IP so we would need to do extra work to open the game server Pods to the internet (e.g. with #104)

Closing, we should reopen if it's technically feasible.


HTML

HTML
User Story
AS a bootcamp student
I WANT the prework notes to be structured on a webpage
SO THAT I can easily find and read information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed

CSS
User Story
AS a boot camp student
I WANT the prework notes to be structured on a webpage
SO THAT I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I see a dark blue header and footer, and four boxes with a shadow

JavaScript
User Story
AS a boot camp student
I WANT the prework notes to be structured on a webpage
SO THAT I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first


Developer experience improvements

What?
Makes it easier to get up and running with melty.
How?

Added instructions for local setup and development.
Replace react-scripts with vite for faster builds in the webview-ui.
Consolidated the installation and development scripts in package.json.

Tested and looks nice :) easier than before to run melty local in that way

Thanks @abhi12299, looks good. I'll take a more thorough look soon.

This looks great Abhi. For some reason, a bunch of @cbh123 's commits are showing up in this PR... could you try rebasing from the main branch of meltylabs/melty and see if that fixes it?

@jacksondc check now - I reverted the branch up until my last commit


[REQUEST] More Known things

Is your feature request related to a problem? Please describe.
This is just reminder ticked not request.

Add Socks support to CF.
Add Use "HTTP Only" amongst other options https://gyazo.com/aa793678f15ca2de118bda9382de93a9 ( I might do PR if find time to do it)

I know
SSL only is basically already HTTP only, I don't really check for SSL support, it's just very poorly written

i did open ticked as a reminder not for being request and being closed because you know lol

There's mein and demi reminding me everyday, I will do it eventually

Also next time if you want your issues to be left open, do not make 1 big issue with a lot of stuff inside, make 1 for each problem with a good title so I can see what needs to be done at a glance when looking at the issues page.


Over-Receipt/Approval Functionality

A few issues occur when trying to turn on Approvals for Over-Receipt:

In the online documentation it states their is a standard workflow when there is not, but the applicable information is there to build your own. Highlighted below is the online documentation:
"You can set up an approval workflow to require that over-receipts must be approved before they can be handled. In that case, you must select the Approval Required check box on the Over-Receipt Codes page. A dedicated workflow response, Approve Over-Receipt exists in the standard workflow data for this purpose. For more information, see Create Workflows."

After a workflow is created and an approval does get sent properly using the correct workflow code. Issue is when you try to Approve you get an error saying "The requested operation is not supported". I debugged the issue and will provide where the error is occurring.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 27756a8b-eafb-abaa-c57a-737aa025f670
Version Independent ID: 936c08fc-81e2-ceee-d714-26e295e434a9
Content: How to Receive Items - Business Central
Content Source: business-central/warehouse-how-receive-items.md
Service: dynamics365-business-central
GitHub Login: @SorenGP
Microsoft Alias: sgroespe

Hello,
Thank you for your feedback! You're right that there is no sample workflow for approving over-receipts in the demonstration company for Dynamics 365 Business Central trials. We'll get that clarified in the next doc refresh.
If you think you have identified a bug in code, please contact technical support.


Add various statistical mean rules

This commit includes new rules regarding various statistical means, including harmonic, geometric, contraharmonic, root mean square, trimean, interquartile, and cubic means. These new rules have been added to the corresponding schemas (full.json, full.php and full_clean.yml) and their relevant checks have been outlined in the README with the corresponding explanations. The 'cubic_mean' rule implementation has also been removed from tests/schemas/todo.yml indicating its successful implementation.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

82 of 82 (100.0%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 96.649%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
1875

Relevant Lines:
1940

💛  - Coveralls


fix(ci): GitHub API 403 error fixed

What was changed

Why?

Checklist

Closes

How was this tested:

Any docs updates needed?

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

fork was removed


Multiple nodes, high availability

Hi there,
are you guys using poxa on production? if so how do you guys handle high availability? How do you guys run poxa on 2 or 3 instances? I've got a tight deadline for a chat application and the way we planned our design is to have a cluster of pubsub servers exchanging messages and hooking up our chat microservice for each message for storaging.

Hey! The distributed part of Poxa is still part of the TODO: https://github.com/edgurgel/poxa#todo
Happy to accept PRs :)


Extend options

Add additional options to specify

job name
build number
cause
We want to be able to specify meaningful values here so they can be used in some plugins.

Thanks! Job Name and Build Number sound about right, but I am not sure about cause. Introducing a new instance type in the Jenkinsfile Runner would do the job for some edge cases, but I would rather expect common causes to be set, e.g. SCM cause. Having a custom cause type limits options for it to be consumed by plugins. Would be great to have more justification for that before merging

I had a look to the existing causes but from my point of view they don't really match.
For the SCMTriggerCause we would need to have a polling log file.
If we take UserIdCause we would need to create a user for each execution of the Jenkinsfile Runner to avoid problems.
The RemoteCause comes close but I would only define the note but no host.
We could rename the Cause to NoteCause with 'Started with note %s' as description.
We could also name the Cause FileRunnerCause.
What do you think?

I cannot reproduce the failing check locally. Looks like an infrastructure error to me.

yes, infra and Jenkinsfile Runner CI are quite unstable.
I agree with having an explicit JFR-specific cause as long as it is not
injected by default
On Fri, Oct 18, 2019 at 3:57 PM Matthias Rinck<EMAIL_ADDRESS>wrote:

I cannot reproduce the failing check locally. Looks like an infrastructure
error to me.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/jenkinsci/jenkinsfile-runner/pull/203?email_source=notifications&email_token=AAW4RIHZFCVM3MWSHJA54GLQPG6ETA5CNFSM4JBZU5C2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBURY2Y#issuecomment-543759467,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW4RIAERHQPJ7ZK3SFOW6LQPG6ETANCNFSM4JBZU5CQ
.

This change if fully backward compatible. If no --cause cli option is set the code works as before.

Pipeline:
node {
stage('Build') {
echo currentBuild.getBuildCauses().toString()
}
}
--cause 'foo'
-> [{"_class":"io.jenkins.jenkinsfile.runner.FileRunnerCause","shortDescription":"Started by foo"}]
-- cause ''
-> []
No cause cli option set
-> []

Just added 7f4ab782f7ae6a9ab82b5853d29aab23933fcb6a. Is this OK too?

Only fixed the commit message from  7f4ab78 to ced2c76.
I'm ready now.

Thanks @rinckm! I hope to cut a new release within few days


Export representation classes to allow for extension

I'm creating a custom StructureRepresentation for my embedded NGL viewer, where I want to extend the StructureRepresentation class. I've also exported all representations and their parameters as well, as if someone wants to make a representation based on an existing representation, those are also exposed.

Thanks @luxaritas. This looks fine, I guess the only slight concern is that the public NGL namespace is getting big, but I'm not sure a big reorganization of that would help anyone right now. @ppillot and @garyo any comments?


Can not invite participant/participants to an active call

I initiated a call from PSTN number to the Incident Bot. In the IncomingCallHandler.cs, I added the following code snippet to invite a team's user participant of the same tenant. Transfer to the same user works but invitation API doesn't.
Code Snippet
var identity = new IdentitySet
{
User = new Identity
{
Id = "user id of the participant from the same tenant",
},
};
this.Call.Participants.InviteAsync(identity).ConfigureAwait(false);
Expected behavior
It should invite the participant of the same tenant. And the participants should be:
a) PSTN number
b) Incident Bot
c) Invited participant of the same tenant
Graph SDK (please complete the following information):

Version [1.1.0-prerelease]

Call ID
Call Id: 451f0400-441f-4a82-8711-1ed759fc5cb6
Time:  11/22/2019 11:37 AM
Logs
CommunicationsClient[1313972621]
2019-11-22T11:36:17.4101Z 98484501-15a0-415c-bc69-d9bb0dbd624c pid:11588 tid:14 (CommunicationsClientExtensions.cs:217 LogRequestAndCreateResponse):
{
<EMAIL_ADDRESS>"#microsoft.graph.commsNotifications",
"value": [
{
<EMAIL_ADDRESS>"#microsoft.graph.commsNotification",
"changeType": "deleted",
"resourceUrl": "/communications/calls/451f0400-441f-4a82-8711-1ed759fc5cb6/operations/1f215e0d-faac-45e3-b296-f97ddc803669",
"resource": "(Generic: VxYVhw/w)",
"resourceData": {
<EMAIL_ADDRESS>"#microsoft.graph.inviteParticipantsOperation",
"participants": [
{
<EMAIL_ADDRESS>"#microsoft.graph.invitationParticipantInfo",
"identity": {
<EMAIL_ADDRESS>"#microsoft.graph.identitySet",
"user": {
<EMAIL_ADDRESS>"#microsoft.graph.identity",
"id": "user id the participant from the same tenant",
"tenantId": "(Generic: PLeWwKeL)"
}
}
}
],
"status": "failed",
"clientContext": "f1b115f9-d1b1-4ae4-b25c-e7d4b8e63847",
"resultInfo": {
<EMAIL_ADDRESS>"#microsoft.graph.resultInfo",
"code": 500,
"subcode": 9999,
"message": "addParticipantsfailed for participants: 8:orgid:7f8430e3-f688-41e7-b385-2731b68c4e9f reason: Audio-video modality controller could not invite participant to this conversation., code=580 subcode=5201",
"subcode": "(Generic: MWZZkZLK)"
},
"id": "1f215e0d-faac-45e3-b296-f97ddc803669"
}
}
]
}
{
"AadApplicationIdentity": {
"AppId": "xxxxxxxxxxx",
"AppName": "IncidentBot"
},
"HttpLogData": {
"TransactionDirection": "Incoming",
"TraceType": "HttpRequest",
"Url": "http://localhost:9442/callback/calling?webInstanceId=local",
"Method": "POST",
"Headers": [
"Accept: application/json",
"Authorization: (redacted)",
"Host: localhost:9442",
"User-Agent: Microsoft-Skype/3.0,(Calling/1.0)",
"Scenario-Id: 98484501-15a0-415c-bc69-d9bb0dbd624c",
"X-Forwarded-For: (redacted)",
"X-Forwarded-Proto: (redacted)",
"X-Microsoft-Skype-Chain-Id: 98484501-15a0-415c-bc69-d9bb0dbd624c",
"X-Microsoft-Skype-Message-Id: 00fa12dc-0346-4568-a3c1-af91f7f40ada",
"X-Original-Host: (redacted)",
"Content-Type: application/json; charset=utf-8",
"Content-Length: (redacted)"
]
}
}
Additional context

Thanks for the thorough post.
I see that the original call was a P2P call.  Escalation of P2P to group call has been disabled as it was not fully supported.  @VinodRavichandran for timeline when this will be added.
Regards,
Kamil

Do we have any future plans to add this feature and support it fully? If yes, what would be the approximate time period?

I can anticipate this to be available in CY20Q2.

We tested user in the same tenant and it works.
However, if we invite a PSTN destination from the group call/bot, does not work.
If the caller of the original call which is converted to a group call is PSTN number, we receive this error:
"403 forbidden Call does not contain the metadata required for making this PSTN dial out".
If the caller of the original call which is converted to a group call is a teams user within the tenant, we receive this error:
"412 conditional failure Could not find the PSTN content for the sponsor of this PSTN leg".
Is there any configuration required for PSTN INVITE or is this feature not available for PSTN destination yet?
Any feedback is appreciated.


Theme Editor missing control

Describe the bug
There is no place in the app to adjust the color of the DatePicker IconBackground
Component (please tell us which flow or app you are experiencing issues with):
Theme Builder
To Reproduce
Steps to reproduce the behavior:

Select DatePicker from list
No IconBackground in the list
See error

Expected behavior
As a result the date picker is created with a Black IconBackground even though it shows correctly in the app
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

It also appears that the ComboBox input is not represented

I was able to add several properties to the JSON for the DatePicker and the Toggle control (FalseFill and TrueFill were not available) however The ComboBox control is not listed at all so I was unsure of the syntax to add those items to the theme

Hi Brian. I'm afraid I don't follow your issue here. I do see support for the date picker, combo box, and toggle.
Can you share more specifically what is missing for you?

I did a search in the JSON for Combo and looked in the list of controls but I did not see anything listed. I also did not see the TrueFill and FalseFill properties for the Toggle control, many other items are listed, but not those properties.


Date value not visible on iOs5

Environment :  Safari + iOs 5 + JQM 1.0 + Mobipick.
The date value is not visible in the input field .
When selecting a date, the change event fired , but the field has no value.
Works well on Android, Chrome , Safari / MacOsx, and ... iOS 4.3.2 and previous.
issue occured also on iOS 5 simulator.
I add a log on updateDateInput
_updateDateInput: function() {
	this.element.val( this.dateString() );
	console.log('update value to ' + this.dateString() + ' => ' + this.element.val());
}

output :
updateValue to 30-12-2011 =>

I realized that JQM use a native date selector for date field (that I don't want)
fixed by removing the type=date attribute on the input field.
Still does not understand why I should do that only for iOs5

Since iOS5, Safari uses a native date picker, see
http://smithsrus.com/ios-5-safari-now-has-native-html5-date-and-time-pickers/
Is there a reason why you don't want to use it? I would like to understand your problem better.
Yes, the workaround is to use an input field with
type="text"

Hi christoph,
With JQM standard date field, I can't change min/max/value  on the fly.
I work on a unique page (it's a phonegap app)
the JQM Date appears when you select an option (otherwise it's
hidden), and I would like to set the min/max/value when I show the date
field.
regards
Le 21/12/11 18:25, Christoph Baudson a écrit :

Since iOS5, Safari uses a native date picker, see
http://smithsrus.com/ios-5-safari-now-has-native-html5-date-and-time-pickers/
Is there a reason why you don't want to use it? I would like to understand your problem better.
Yes, the workaround is to use an input field with
type="text"

Reply to this email directly or view it on GitHub:
https://github.com/sustainablepace/mobipick/issues/2#issuecomment-3236647

Bonjour!
By JQM date, do you mean the iOS5 native datepicker? It's possible it doesn't support min/max.
So far I have only tried native datepickers on Opera, as I don't have access to an Apple device. In Opera, native min/max settings work.
But if you don't want native datepickers, setting the input type to "text" is the best option. Are you satisfied with this solution, or did you have something else in mind?

No its ok for me.
Thanks
Le 21 dc. 2011 18:53, "Christoph Baudson" <
<EMAIL_ADDRESS>a crit :

Bonjour!
By JQM date, do you mean the iOS5 native datepicker? It's possible it
doesn't support min/max.
So far I have only tried native datepickers on Opera, as I don't have
access to an Apple device. In Opera, native min/max settings work.
But if you don't want native datepickers, setting the input type to "text"
is the best option. Are you satisfied with this solution, or did you have
something else in mind?

Reply to this email directly or view it on GitHub:
https://github.com/sustainablepace/mobipick/issues/2#issuecomment-3237077


Add Portuguese (PT) Language Support

Please add support for Portuguese (PT) language. Currently, the supported languages do not include Portuguese, and it would be useful to have this option.
Thank you.

Please add support for Portuguese (PT) language. Currently, the supported languages do not include Portuguese, and it would be useful to have this option.

Hi! Added pt parameter:
multranslate --language pt

or
npm start -- --language pt

Example:


the efficiency of using ping too slow

Hello, is the efficiency of using ping too slow, can use the form of broadcast to use ARP protocol to achieve it？

Unfortunately, on iOS we don't have access to lower networking layers, so we cannot send an ARP request.


I'd like to join community

Hello.
My name: Phanatagama
My Github Username: @phanatagama
I really would love to jump into this community.
Thank you.

Hello there, welcome to openAOD, I have sent an invite to join the org. Happy to have you here : )


FR: Ability to define additional custom dhcp server section

So we could run scripts on dhcp leases and so on...

on commit {
set clip = binary-to-ascii(10, 8, ".", leased-address);
set clhw = binary-to-ascii(16, 8, ":", substring(hardware, 1, 6));
execute("/usr/local/sbin/dhcpevent", "commit", clip, clhw, host-decl-name);
}

timeout (https://github.com/opnsense/core/commit/7338549ba5f295f5420e45ba74112af10d20c713)


Session Pool

Use a pool to manage sessions. Session creation is expensive and the number of sessions that can be created is limited. Sessions and the pool will be hidden from end users, but the pool behavior can be configured by the following settings:

min: Minimum number of sessions that the pool will maintain at any point in time.
max: Maximum number of active sessions that the pool will have at any point in time.
keepalive: The frequency that the session pool checks for idle sessions and keep them alive. If the number of idle sessions is more than min then they can be closed and culled from the pool.

Creating transactions with BeginTransaction is an expensive call, so some fraction of the pool may preallocate transactions. If this is done, end users should be able to control what percentage of the pool will do this. However, we should investigate if using TransactionSelector.begin adds the same amount of overhead that BeginTransaction does.
The pool should follow the behavior of other ruby connection pools and raise if there are no sessions available, so end users can handle the error and adjust the pool size if needed/wanted.

As for calling BeginTransaction it is useful since because it allows one to make concurrent read/query calls. Otherwise you would have to wait for the first read/query to yield the first chunk before you can make any subsequent calls. Also if the first read failed for whatever reason you will not get back the transaction id.


Functions in anonymous namespaces have blank names in disassembly

The following program compiled for Linux with symbols does not show a name at all for the call to test_func.
#include <stdio.h>

namespace
{
    void test_func()
    {
        printf("test\n");
    }

    class A
    {
    public:
        A()
        {
            test_func();
        }
    };

    A a;
}

int main()
{
    return 0;
}

test.zip

Fixed in 1.0.278 beta


inkcut: init at 2.1.1

Motivation for this change
Great application for driving vinyl cutter machines
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

(converting to draft since I want to look into cleaning up the qt-reactor packaging)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/what-are-your-goals-for-20-09/8035/7

(split into commit-per-package and fixed up the qreactor package)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/197

Thanks for all the reviewing and pointers, I'm learning a lot ;)


Memory leak in Keras: Functions Clone_model() and Set_Weights() become slower and slower when used in loop

Configuration

Library
Version

pyhton
3.6.8

GCC
7.3.0

tensorflow-base/tensorflow-gpu
1.13.1

keras-gpu/keras-base
2.2.4

theano
1.0.4

cudnn
7.6.0

cudatoolkit
10.0.130

Machine Configuration：
Ubuntu 18.04.2 LTS
Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz 128GB RAM
CUDA Version: 10.2
Double GeForce GTX 1080ti

Description
I use keras.models.clone_model() to clone the resnet50 model and use set_weights()  to set the weights for each layer. But I find that the time consumption for each iteration becomes much larger as time goes by. At the first iteration, the clone stage takes about 4 seconds and the setting-weights stage takes about 3 seconds but those turn to be 34 seconds and 4 minutes at the 50th iteration.
Is there a problem with my usage? Or would there be a memory leak in keras?
I hope to hear from you soon. Thanks in advance.
The code is shown as bellow:
import keras
import sys
import datetime

def get_HH_mm_ss(td):
    days,seconds = td.days,td.seconds
    hours = days * 24 + seconds // 3600
    minutes = (seconds % 3600)//60
    secs = seconds % 60
    return hours,minutes,secs

loop_iter = int(sys.argv[1])
origin_resnet = keras.applications.resnet50.ResNet50(include_top=True, weights='imagenet', input_tensor=None, input_shape=None, pooling=None, classes=1000)

for i in range(loop_iter):
    print("Iteration {}".format(i))
    s = datetime.datetime.now()
    copy_model = keras.models.clone_model(origin_resnet)
    e1 = datetime.datetime.now()
    copy_model.set_weights(origin_resnet.get_weights())
    e2 = datetime.datetime.now()
    td_copy = e1 - s
    td_set_weights = e2 - e1
    h1, m1, s1 = get_HH_mm_ss(td_copy)
    print("Copy model: Time used: {} hour,{} min,{} sec".format(h1, m1, s1))
    h2, m2, s2 = get_HH_mm_ss(td_set_weights)
    print("Set weights: Time used: {} hour,{} min,{} sec".format(h2, m2, s2))

Here is partial result:

Keras may leak memory。 load_model,memory continues to grow


Smarter flow-typing with ||

Search Terms

mutually exclusive

flow typing

Suggestion
The following code doesn't type-check today. I think it would be nice if it did:
function getThing(): null | object {
  return {};
}
function example() {
  const thing1: null | object = getThing();
  const thing2: null | object = getThing();

  if (!thing1 && !thing2) {
    return;
  }

  // error: Type 'object | null' is not assignable to type 'object'.
  const either: object = thing1 || thing2;
}

playground link (enable strict null checks)
We know that it's impossible for both thing1 and thing2 to be falsey because of the earlier check, so it would be nice if the inferred type were object instead of object | null.
Use Cases
The above is basically the use-case I had in mind. In my case, they were regexp match objects, but the general idea still applies no matter what they area.
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code [more-accurate types might cause some conditionals to be marked as redundant, but that should just help clean up code]
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Design Limitation Concerns
This doesn't exactly fit in with TypeScript's existing flow-typing implementation, since it requires typing thing1 and thing2 together. Doing this everywhere (for all pairs or triplets of objects) would be prohibitively costly.
The kind of reasoning I'd prefer, which is more scalable, goes roughly like the following:

when evaluating thing2 in the expression thing1 | thing2, we know that thing1 is falsy [since otherwise we wouldn't have gotten here]
there's a recent "still-valid" flow-typing check that requires !truthiness(thing1) && !truthiness(thing2) to be false
we can now "learn" a more-precise flow-type on thing2 since the thing1 and thing2 both appear in a relevant flow-type condition

My hope is that this is merely a limitation of the existing implementation, rather than the overall design. I would hope this kind of feature could be added to the existing implementation in a nice and elegant way without impacting type-checking preciseness or performance elsewhere.

It's easy enough to counterfactually reason through the 2-variable case, but generalizing this is really quite difficult and doesn't come up often enough for us to want to start trying to writing heuristic algorithms for NP-complete problems.

@RyanCavanaugh
Indicate with a specific warning, all type evaluations within a if scope with an OR logic?
That is, the design limitation is clear, but if not indicated it is questionable


POC Astro

...Just a place to keep notes pertaining to Astro

Platform wishes

#356

UI wishes

#368

Content wishes

#667
#668

Features

Search - with AI?
Top menu
Left-side toc with filter on article and tutorial pages
Language selector
In this article
Related content
Breadcrumbs
Edit page, Feedback, and Site feedback
Content info with version, time-to-read, audience, onsite/online, pilot
(Sub)Category pages
Homepage
Footer with copyright and links
Redirects
"Stable" links for the dispatcher
Sitemap exported to In-App

Markdown

[ ] Frontmatter metadata
[ ] Admonitions (tip, note, caution, warning)
[ ] Tables with left/center/right aligned cols (rows automatic alternating colors)
[ ] Tabbed content
[ ] Inline code with single backticks
[ ] Fenced code blocks with triple backticks
[ ] Includes (for reuse)
[ ] Includes (code-snippets with DocFX Flavoured Markdown)
[ ] Paths relative to current md/yml file
[ ] Reference-style links and images
[ ] xref-style links (uid)
[ ] Optional explicit anchor on headings
[ ] Bookmark links (anchors)
[ ] Expandable content (used only 5x)
[ ] <script> tag to embed forms from SuperOffice
[ ] Markdownlint

Content and data formats

Markdown

Articles
Release notes
Contribution guide
NetServer config
RESTful (Agents, REST)
SOAP (Services88 osv)
Archive providers
MDO providers

Yaml (custom)

Homepage
Category page
SubCategory page

YAML ManagedReference

CRMScript
NetServer Core and Services
SuperOffice.WebApi
SuperOffice.DCF.Web

JSON

Map src files to output folders (DocFX build file)

Things we can measure and compare

Page load performance
Build time (both prod and localhost)
Publication time

Integrations

@astrojs/tailwind
@astrojs/sitemap
@astrojs/mdx
@astrojs/react
astro-compress
astro-navbar
astro-pagefind
astro-i18next
astro-breadcrumbs
accessible-astro-components
astro-page-insight
astro-social-share
astro-robots
cookieconsent
astro-toolkit
astro-custom-toc
astro-redirect-from


[build-script-impl] Process substitution avoiding "/bin/sh: Argument list too long" - 5.0 branch

Purpose
This is a duplicate PR of #14367 for the 5.0 branch.
This PR adds a fix to build-script-impl that should avoid the /bin/sh: Argument list too long error that's been seen on the ASAN CI bot.
rdar://33714951

@swift-ci please smoke test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 1b39bc5f208256d452bc3ef6da70be987cee2a3d

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 1b39bc5f208256d452bc3ef6da70be987cee2a3d


feat: Support to choose openstack backend plugins

Is this a bug report or feature request? (choose one): feature request

Kubernetes Version (output of kubectl version):
Helm Client and Tiller Versions (output of helm version):
Development or Deployment Environment?:
Release Tag or Master:
Expected Behavior:
What Actually Happened:
How to Reproduce the Issue (as minimally as possible):
Any Additional Comments:
openstack's modules are implemented to select plugin backend system or agents. for example, nova can select hypervisors like kvm, vmware, xen and so on, neutron can select agents like linuxbridge-agent, opencswitch-agent and so on.
So it needs to design to choose plugins in helm charts. in neutron-helm package case, it needs to configure to disable openvswitch-agent to do not deploy openvswitch-agent daemonset, and enable another agent like linuxbridge-agent daemonset and config map.
almost all openstack's modules have same concept to use plugins, so we need to design all charts can use.

@v1k0d3n thanks. but it looks there's some difference between cinder multi backend function (#300) and neutron agent plugin function on openstack-helm. because in cinder case, there's no change of k8s resources. the cinder configuration acts in cinder-volume deployment so it's enough to fix cinder.conf. but in neutron case,  ovs-agent, ovs-db, ovs-vswitchd daemonsets should be not deployed when we set up to use linuxbridge-agent. it means neutron-helm chart should control what *-agent daemonsets will be deployed or not. do we need new issue for neutron?


download/Cargo.toml: Update env_proxy to 0.3.0

env_proxy 0.3.0 supports more of cURL's specifix environment variable
behaviour, we should use that.
Signed-off-by: Daniel Silverstone<EMAIL_ADDRESS>

NOTE: this updates Cargo.lock, please check carefully.


Add check to flag when a PMID is associated with anything other than dbxref

Fixes #1354

Do I also fix the problem with this PR? How could I proceed? Delete all the wrong entries?

@anitacaron looks like only 5 violations, happy to go take a look at them manually :) I think it's probably just tagged wrongly on something, but I'll check

yeah its also my mistake :p i did a stupid >.< sorry

Should all be fixed, 3/5 were mine >.< hahahhahaa! im really glad we have this check now


remove unused attributes from Connection

Please provide a description of this PR:
clean up Connection unused fields

@hzxuzhonghu: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Ft/es snapshots

This PR implements taking Elasticsearch snapshots to S3. Implementation uses ES's Snapshot Lifecycle Management (SLM) API  to automate snapshot creation every 91 days (Rollover should be every 90 days)

... API to automate snapshot creation every 91 days (Rollover should be every 90 days)

My immediate thoughts/questions (may not be accurate):

Are we 100% sure that the two policies we be schedule at the exact same time? Otherwise we can't guarantee that 91st day (for snapshot) will be a day after the 90th day (for rollover).
The two schedules even if they start at the same time, will drift over time:

Rollover: 90th day, 180th day, ... 900, 990, ...

I think you want them to happen every 90 days but one should start a day earlier/later

Are the snapshots incremental?

Yes the snapshots are incremental
Yes, the scheduling is a little bit tricky. Since the count starts on the day of deployment to prod. These would actually overlap since initial rollover would have happened by then. Looking at this!

Seeing this comment:

Are we 100% sure that the two policies will be schedule at the exact same time? Otherwise we can't guarantee that 91st day (for snapshot) will be a day after the 90th day (for rollover).

I had thought there was some way to trigger actions (like snapshotting) as part of ILM, and that scheduling wouldn't be an issue...

Seeing this comment:

Are we 100% sure that the two policies will be schedule at the exact same time? Otherwise we can't guarantee that 91st day (for snapshot) will be a day after the 90th day (for rollover).

I had thought there was some way to trigger actions (like snapshotting) as part of ILM, and that scheduling wouldn't be an issue...

Yes Ideally, had we gone with the full ILM phase rollovers from hot->warm->cold/frozen snapshotting would automatically be done once we rollover int the cold/frozen phase.
So right now with all our indices in the hot phase, we're trying to achieve this using Snapshot Lifecycle Management (SLM) APIs

@thepsalmist Can you add a small description (in this PR or docs) what this change mean vs what we were aiming for with the 90-day rollover?

@thepsalmist Can you add a small description (in this PR or docs) what this change mean vs what we were aiming for with the 90-day rollover?

Resolved


[VS Code] [Audio] Request startOrJoinCall failed unexpectedly without providing any details.

Error:
Request startOrJoinCall failed unexpectedly without providing any details.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS-Audio

extensionVersion
0.1.91

applicationName
VSCode

applicationVersion
1.71.2

platformName
Windows

platformVersion
10.0.22000

We're unable to prioritize fixes to this area as we re-evaluate our priorities and product direction. We understand that this maybe disappointing. We appreciate your input and comments on this issue till now. We will soon be sunsetting this feature and will work towards a better use experience for communication needs for Live Share users from the editor.


Uncomment - -bugprone-unused-local-non-trivial-variable

Disabled tidy check in #3340

[ ] Uncomment and investigate
[ ] Fix code if able
[ ] reneable check

After turning off -bugprone-unused-local-non-trivial-variable, two unused local variable errors was reported:

src/module.cpp:1136:

program.cpp:1019

Pull those out, rebuild, run a make -j$(nproc) check and then ensure that doesn't break anything. I don't think it would break anything if you removed this. Open PR after and I can approve


Can i upload my own files  locally?

i want to upload my own csv files locally like this link,https://pair-code.github.io/facets/
bazel run facets:facets can work
but facets.html is empty
do any demo owns the function of uploading local files?

Hi anna-mo,
What browser are you using?

i use chrome to do this, and i can make the simple ones work, like http：// localhost：6006 / facets-dive / components / facets-dive / runner.html works well on my browser, but i want to use some my own csv files ,   then try to run facet.html ,found that it's empty, i just wonder that the fuction of uploading files like the website https://pair-code.github.io/facets/ can build locally ?


Fix 2019-06-01-preview/FailoverManagedInstance.json

Fix 2019-06-01-preview/FailoverManagedInstance.json. It just renames the parameters and unblocks 2020-06-01-preview PR #11840
The original author @MilanBrkicFON will help us to verify there is no real break change for the FailoverManagedInstance.
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@MilanBrkicFON
Can you help us to verify this API actually works without any true compatibility problem?
In theory, this re-naming change would introduce a breaking change in the paperwork.

I believe the failure of SDK azure-sdk-for-go is not from us.
the same error also happens in https://github.com/Azure/azure-rest-api-specs/pull/11883

/azp run

@akning-ms
can you help to review this PR and merge it? Thanks!
I have explained the breaking change issue in the description and comments.
@jamestao  and the API endpoint owner @MilanBrkicFON have approved this PR.


fabric 1.18.2 plz

https://cdn.discordapp.com/attachments/317970591191924736/1118196553778221086/showmemydps-1.0.0.jar
it built on June, 2023 so have the same function as 1.5-SNAPSHOT but it haven't tested so if you use it, it may causes crash.
I apologize for the inconvenience.

ty so much


Recreate PR#317

See closed PR#317

I hope I managed to redo what I did earlier, after several hours at the pub with friends.


ReleaseRecordedEventsMiddleware return the value for the next middlew…

Return the value for the next middleware configured in the bus.

Thank you @pablonunez for the contribution.
According to Tactician's interfaces, this is a good addition. But just out of curiosity - what is your use case? I think using return values with commands is more like anti-pattern, isn't it?

Hi @borNfreee,
We are using league/tactician-bundle in our protect, and some use-cases are synchronous, and others are asynchronous.
For example to create a user, it's very useful to get the user uuid, and run asynchronous other events. For symfony I think this bundle is good solution. It's less complex that manage all commands asynchronous...
In any case, I think users can choose if use the result or not... :-)

Could you please tag a minor version with this addition? It's so much better than manage a fork...

Upps!, It's done. Thanks very much.

No problem if it helps you :)
But if you are speaking about UUID, then return value is not what you need. Consider the following example:
// Inside UserController.php
...
public function createUserAction(Request $request)
{
    $uuid = $request->get('uuid'); // for simplicity. In real app it would be Symfony Forms
    $name = '...';
    $password = '...';

    $this->get('command_bus')->handle(new CreateUser($uuid, $name, $password);

    return $this->redirect('some_route', $uuid); // here you already know UUID of the user. No need to use return value
}
...

We create the uuid in the handler (Application level)...because I think it's better than give this responsability to the Web/Rest/Console Controller (UI level).
But I have read differents opinions...

Yes, there are multiple opinions.
But at this time, when we have rich client side applications, it's ok when JS generates (and immediately uses) UUID and sends it to the server. JS side don't need to wait a response in order to retrieve the entity ID. It's already here. Just one of the many solutions.

Yes. If you need the uuid in the client side it's a better solution to create via JS. But if you have a REST Api and/or some console commands to create users, it very good if you create the uuid in the handle too.
(We have lot chats about this in the office, hehehe)


Multidimensional RNN

Hi all,
This is a feature request for Multidimensional LSTM. Is there any plan to support this in tensorflow?
I might be able to help with implementation if there is such a plan.
Cheers,

@ebrevdo: Want to comment on this?  Fancier variants of LSTMs would be great to have, the only question is whether they should go in core tensorflow, the contrib directory, or the models repo.  If you can make the interface similar to Eugene's existing RNN cell setup contrib might be the best place at first.

Right now it's possible to implement various types of multidimensional RNNs by feeding in your data as time being one direction (say, x), taking the output of the RNN, transposing it, and feeding it into a second RNN.  etc.  Alternatively feed your data & its transpose into separate RNNs (possibly with tied weights) and depth-concatenate the results.  And maybe feed the result into another RNN.
This allows one to implement both separable and non-separable multidimensional RNNs.  Not sure we need the sugar until people show it's superior to convolutional networks for something, and there's lots of use cases.
That said, it would be really nice to implement GridLSTM (also by Alex Graves, and according to their paper showing a lot of promise with fewer parameters).  GridLSTM uses standard LSTM cells, so it would be a function that uses RNNCell objects.  It connects them in interesting, convolutional, ways.
GridLSTM would probably go well in contrib, until enough people use it and it shows to be a very successful technique.

Thanks, GridLSTM looks interesting. I will give it a shot. This seems to be a good starting point.
I do have a use-case for this, but it is still in a pilot study. Will be nice to make it into contrib until there are more use-cases.

Right now it's possible to implement various types of multidimensional RNNs by feeding in your data as time being one direction (say, x), taking the output of the RNN, transposing it, and feeding it into a second RNN. etc.

How exactly do I transpose the output? Say I have this code:
input = tf.placeholder(tf.float32, [batch_size, time_steps, num_features]
cell = rnn.BasicLSTMCell(num_units=1)
lstm1 = tf.nn.dynamic_rnn(cell, input, dtype=tf.float32)
tranposed_lstm_output = some_transpose_function(lstm1) # how does this work?
lstm2 = tf.nn.dynamic_rnn(cell, transposed_lstm_output, dtype=tf.float32)

As for the other one:

Alternatively feed your data & its transpose into separate RNNs (possibly with tied weights) and depth-concatenate the results.

How do I "depth-concatenate" the results?
input = tf.placeholder(tf.float32, [batch_size, time_steps, num_features])
transposed_input = tf.placeholder(tf.float32, [batch_size, num_features, time_steps])
cell = rnn.BasicLSTMCell(num_units=1)
lstm1 = tf.nn.dynamic_rnn(cell, input, dtype=tf.float32)
lstm2 = tf.nn.dynamic_rnn(cell, transposed_input, dtype=tf.float32)
mdlstm1 = some_depth_concatenation_function([lstm1, lstm2]) # how does this work?


adding args to check-ram.rb to allow changing its behavior

first pass at rewriting check-ram.rb
The following changes are notable:

Switched "free -m" for vmstat gem to make it more OS agnostic (tested linux & OSX).
Added flags to use either --free, --used respectively. This affects whether you are checking resources available or resources in use. The default is to use free to not change the way its working (wouldnt want to make a bunch of people have to change their check defintions).

Here are some typical examples

default behavior: checks % of RAM free:

$ bin/check-ram.rb
CheckRAM OK: 53.46% RAM free

checks % of RAM in use:

$ bin/check-ram.rb --used
CheckRAM OK: 48.22% RAM used

checks how many MB of RAM in use:

$ bin/check-ram.rb --megabytes --used -w 200 -c 100
CheckRAM CRITICAL: 888 megabytes of RAM used

https://github.com/sensu-plugins/sensu-plugins-memory-checks/issues/5#issuecomment-116047418

@mattyjones @tas50 @maticmeznar had a chance to look at this yet?

I took a really quick look at this and I think there is an error in your calculation of MB.  The values returned by vmstat are not in KB but rather in number of pages.  The page size may vary from OS to OS, so you need to use the page size data also returned by the vmstat gem to calculate the actual usage.

@andyshoe maybe I am misreading something but it returns the number of bytes: https://github.com/threez/ruby-vmstat/blob/master/lib/vmstat/memory.rb

From the link you sent:
@attr [Fixnum] wired
The number of wired pages in the system.
@attr [Fixnum] active
The number of active pages in the system.
@attr [Fixnum] inactive
The number of inactive pages in the system.
Its the number of pages, like I suggested in my last comment.  Looks like there are also wired_bytes and active_bytes if you wanted to use those instead.  Just as a reminder I'm a Ruby noob so take what I'm saying with a grain of salt, but I'm pretty certain your code is not properly accounting for page size.

@andyshoe what I mean is that on each of his functions he times it by page size. Here is an example: https://github.com/threez/ruby-vmstat/blob/master/lib/vmstat/memory.rb#L22
I am also not as strong with the ruby foo as I would like. I am investigating further since it still seems off to me

@andyshoe I need to use it like this though I am still showing it a bit off count as far as total ram:
    mem = Vmstat.snapshot.memory
    free_ram = mem.inactive_bytes + mem.free_bytes
    used_ram = mem.wired_bytes + mem.active_bytes
    total_ram = mem.total_bytes

It looks good to me (regarding the unit sizes) a little off but thats nothing new due to the lack of consensus to use SI prefix or IEC prefix... @mattyjones @tas50 is there a preference in which sensu plugins should use?

@sge-babrams  I will look at this this week.  I would really like to find a way to do this in pure Ruby that also allows for Windows as well.  Absent that I would go with vmstat.

@mattyjones I have yet to see a pure ruby implementation that is cross platform, I have been searching for a way and unable to find anything thus settling on vmstat. I hope I am just not searching for the right terms because I agree this is silly that there is no way to do this...From what I have found I think our best bet is OS detection and use vmstat for *nix and some other method for windows maybe a c extension like vmstat is.

@mattyjones any word? if we are ready I will rebase and fix merge conflicts

@sge-babrams  If you update the changelog and fix the dep issue I noted then we are good to merge.
Thanks!

@mattyjones updated as requested let me know if there is anything else

@sge-babrams  will do and I will take care of it but in the futire, you don't need to add a dep to both the gemspec and the gemfile.  The gemfile does nothing but call the gemspec so it is just extra cruft ;p


Consider adding seichi-portal-backend to SeaORM showcase!

Hey @rito528, Thanks for adopting SeaORM!
It's our pleasure to see more inspirational projects were built on top of SeaORM :)
Let us know if you have any feature recommendation or feedback.
Some learning resources for you: Documentation, Tutorial, Cookbook, Q&A, Blog
Join our Discord server to chat with others in the SeaQL community!
Feel free to submit a PR to showcase your project, https://github.com/SeaQL/sea-orm/issues/403.

I've created a PR to add this to SeaORM ShowCase.
https://github.com/SeaQL/sea-orm/pull/1553


ngx_pagespeed and nginx 1.9.14

It seems that nginx 1.9.14 has some issues with ngx_pagespeed.
I compiled this version using the following versions:
ngx_pagespeed: release-<IP_ADDRESS>-beta
psol: <IP_ADDRESS>
pagespeed: <IP_ADDRESS>
The compilation finishes correctly but when I try to run the nginx sever, I get this error about the configuration:
nginx: [emerg] unknown directive "gzip" in /home/user/nginx/conf/nginx.conf:31
Also, I tried with nginx 1.9.12 and upgrade the ngx_pagespeed, psol and pagespeed versions but it is still not working. Did you notice about this before?

can you paste the nginx.conf that you have, and the output of nginx -V

Hi, here is the output:
→ sudo /opt/nginxstack/nginx/sbin/nginx -Vv
nginx version: nginx/1.9.14
built with OpenSSL 1.0.2g  1 Mar 2016
TLS SNI support enabled
configure arguments: --prefix=/opt/nginxstack/nginx --with-http_ssl_module --with-http_stub_status_module --with-cc-opt=-I/opt/nginxstack/common --with-ld-opt=-L/opt/nginxstack/common/lib --with-http_gzip_static_module --with-mail --with-mail_ssl_module --with-http_realip_module --with-http_stub_status_module --with-http_v2_module --add-module=/opt/nginxstack/src/gnosek-nginx-upstream-fair-5f6a3b7 --add-module=/opt/nginxstack/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/ext/nginx --add-module=/opt/nginxstack/src/ngx_pagespeed-release-<IP_ADDRESS>-beta

and here is the nginx.conf:
user  daemon daemon;
worker_processes  auto;

error_log  "/opt/nginxstack/nginx/logs/error.log";
pid        "/opt/nginxstack/nginx/logs/nginx.pid";

events {
      worker_connections  1024;
}

http {
      include       mime.types;
      default_type  application/octet-stream;

      client_body_temp_path  "/opt/nginxstack/nginx/tmp/client_body" 1 2;
      proxy_temp_path "/opt/nginxstack/nginx/tmp/proxy" 1 2;
      fastcgi_temp_path "/opt/nginxstack/nginx/tmp/fastcgi" 1 2;
      scgi_temp_path "/opt/nginxstack/nginx/tmp/scgi" 1 2;
      uwsgi_temp_path "/opt/nginxstack/nginx/tmp/uwsgi" 1 2;

      access_log  "/opt/nginxstack/nginx/logs/access.log";

      sendfile        on;

      keepalive_timeout  65;

      gzip on;
      gzip_http_version 1.1;
      gzip_comp_level 2;
      gzip_proxied any;
      gzip_vary on;
      gzip_types text/plain
          text/xml
          text/css
          text/javascript
          application/json
          application/javascript
          application/x-javascript
          application/ecmascript
          application/xml
          application/rss+xml
          application/atom+xml
          application/rdf+xml
          application/xml+rss
          application/xhtml+xml
          application/x-font-ttf
          application/x-font-opentype
          application/vnd.ms-fontobject
          image/svg+xml
          image/x-icon
          application/atom_xml;

      gzip_buffers 16 8k;
      add_header X-Frame-Options SAMEORIGIN;
      ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

      # HTTP server
      server {
          listen       80;
          server_name  localhost;

          location / {
              root   html;
              index  index.html index.htm;
          }

          location ~ \.php$ {
              root           html;
              fastcgi_read_timeout 300;
              fastcgi_pass   unix:/opt/nginxstack/php/var/run/www.sock;
              fastcgi_index  index.php;
              fastcgi_param  SCRIPT_FILENAME $request_filename;
              include        fastcgi_params;
          }
      }
}

so, the error is:
nginx: [emerg] unknown directive "gzip" in /opt/nginxstack/nginx/conf/nginx.conf:31

I tried to just comment the gzip directives but the error persists.
Note: I recompiled it so I changed the path.

looks like you're using a very old version of psol.
--add-module=/opt/nginxstack/src/ngx_pagespeed-release-<IP_ADDRESS>-beta

is in your configure options.

By the way, Nginx v1.9.15 got released.

You are right, I compiled that version with an old version of ngx_pagespeed in order to check if it would work with it. I forgot to mention it.
I will compile this new Nginx with the <IP_ADDRESS> version of psol, pagespeed and ngx_pagespeed and I will write back.

I tried this new version:
→ sudo /opt/nginxstack/nginx/sbin/nginx -Vv
nginx version: nginx/1.9.15
built with OpenSSL 1.0.2g  1 Mar 2016
TLS SNI support enabled
configure arguments: --prefix=/opt/nginxstack/nginx --with-http_ssl_module --with-http_stub_status_module --with-cc-opt=-I/opt/nginxstack/common --with-ld-opt=-L/opt/nginxstack/common/lib --with-http_gzip_static_module --with-mail --with-mail_ssl_module --with-http_realip_module --with-http_stub_status_module --with-http_v2_module --add-module=/opt/nginxstack/src/gnosek-nginx-upstream-fair-5f6a3b7 --add-module=/opt/nginxstack/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/ext/nginx --add-module=/opt/nginxstack/src/ngx_pagespeed-release-<IP_ADDRESS>-beta

and the errors is still being:
nginx: [emerg] unknown directive "gzip" in /opt/nginxstack/nginx/conf/nginx.conf:31

I used the same nginx.conf. Is there anything I could be missing? Nginx is working properly without the pagespeed module and I'm compiling ngx as I did with previous versions.
However, I'm getting this error since the 1.9.11 (1.9.10 works properly with this module).
I tried to disable --with-http_gzip_static_module in order to discard conflicts with pagespeed and any internal compression process that nginx could be performing. I didn't get any advance.
Did you find any similar issues before?

Never seen this before. Let me try to reproduce this  locally.

Confirmed. Also when I disable ngx_pagespeed's gzip_setter code the error persists.

Confirmed: <IP_ADDRESS> will run without problems.
I will check this weekend if there is something we can backport to get this working in <IP_ADDRESS>.

This patch fix problem:
diff -urN ngx_pagespeed-<IP_ADDRESS>-beta-orig/config ngx_pagespeed-<IP_ADDRESS>-beta/config
--- ngx_pagespeed-<IP_ADDRESS>-beta-orig/config	2016-04-27 12:24:06.986198238 -0400
+++ ngx_pagespeed-<IP_ADDRESS>-beta/config	2016-04-27 12:24:38.000000000 -0400
@@ -195,10 +195,10 @@

   # Make pagespeed run immediately before gzip.
   HTTP_FILTER_MODULES=$(echo $HTTP_FILTER_MODULES |\
-    sed "s/$HTTP_GZIP_FILTER_MODULE/$HTTP_GZIP_FILTER_MODULE $ngx_addon_name/")
+    sed "s/ngx_http_gzip_filter_module/ngx_http_gzip_filter_module $ngx_addon_name/")
   # Make the etag header filter run immediately after gzip.
   HTTP_FILTER_MODULES=$(echo $HTTP_FILTER_MODULES |\
-    sed "s/$HTTP_GZIP_FILTER_MODULE/ngx_pagespeed_etag_filter $HTTP_GZIP_FILTER_MODULE/")
+    sed "s/ngx_http_gzip_filter_module/ngx_pagespeed_etag_filter ngx_http_gzip_filter_module/")
   CORE_LIBS="$CORE_LIBS $pagespeed_libs"
   CORE_INCS="$CORE_INCS $pagespeed_include"
   echo "List of modules (in reverse order of applicability): "$HTTP_FILTER_MODULES

$HTTP_GZIP_FILTER_MODULE is empty. Sed can't apply pattern for given data and after that we have empty HTTP_FILTER_MODULES variable.
checking for psol ... found
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression
List of modules (in reverse order of applicability):
 + ngx_pagespeed was configured

I will try that patch and I will write you back.
Thank you so much.

I'm having the same issues as well.  Any updates on when this bug will be fixed?

@kossamums is there a reason why you can't use the latest version of ngx_pagespeed?
there have been some security patches since then, so it's recommended to upgrade.

ngx_pagespeed 1.9.x is no longer supported, and has unpatched security vulnerabilities.  Please use the latest version (1.11).
If you need to keep using 1.9.x, you need to be backporting the security patches anyway, in which case applying the patch above (https://github.com/pagespeed/ngx_pagespeed/issues/1180#issuecomment-215142121) shouldn't be much more work.

@jeffkaufman 1.11 can be built on CentOS 6 with GCC 4.4.7?

1.11 can be built on CentOS 6, but via a secondary install of gcc-4.8 instead of the default compiler.  On build_ngx_pagespeed_from_source we have the steps for installing the gcc-4.8 compiler into /opt/ in a way that won't mess with the rest of your CentOS setup.