Parameters and response-body not documented while using express-oas-generator

Thanks for the library. I am using version 1.0.7
Below is my app.js code here i am using express-oas-generator
var express = require('express');
var app = express();
const expressOasGenerator = require('express-oas-generator');

var bodyParser = require('body-parser');
var port = process.env.PORT || 3606;
var db = 'mongodb://localhost/example';

expressOasGenerator.init(app, {});
var books = require('./routes/books');

app.use(bodyParser.json());
app.use(bodyParser.urlencoded({extended: true}));

app.use('/books', books);

app.listen(port, function(){
    console.log('app listening on port: '+port);
});

Below is my schema:
var BookSchema = new Schema({
	title: String,
	author: String,
	category: String,
	booknames: [ String],
	booktypes: [{
        _id : false,
        lang_code:{type : String ,required : true },
        booktype: String,
    }]
});

My api-spec looks like below:
paths: {
     /books: {
           get: {
                  summary: "/books",
                 consumes: [
                        "application/json"
                 ],
                 parameters: [ ]
           },
        post: {
                summary: "/books",
                consumes: [
                    "application/json"
                ],
               parameters: [ ]
        }
},

My post api looks like  below:
router.post('/', async(req, res, next)=>{
    res.setHeader('Content-Type', 'application/json');
    var newBook = new Book();
    newBook.set(req.body)
    await newBook.save(function(err, book){
        if(err) {
            res.status(HttpStatus.BAD_REQUEST)
            .send({
                error: HttpStatus.getStatusText(HttpStatus.BAD_REQUEST)
            });
        }
    });
    next();
});

I have seen the similar issues and implemented in the similar way. Please help where I am doing wrong.
https://github.com/mpashkovskiy/express-oas-generator/issues/9
https://github.com/mpashkovskiy/express-oas-generator/issues/4

Hi Mounika, will check it this week.

Hi mpashkovskiy,
Is this issue resolved. I am waiting to use this package in my application if the issue is fixed.

Hi Mounika, thank you for being patient. Will investigate the issue and get back to you today.

Hi Mounika, tried to reproduce the problem in the branch issue-24 (see server.js) but with no luck. May I ask you to modify the code in server.js or somewhere around index.js#177 so the problem appear?

I ran it like node server.js and then checked http://localhost:3606/api-docs/ in the browser.

@MounikaKommineni did you have time check server.js? Maybe you can give a hint how to reproduce the problem?

Hi mpashkovskiy,
I have tried with your server.js It is giving the response body. But do I need to specify all my methods manually like you are doing for POST ?
app.listen(port, function() {
  console.log('app listening on port: ' + port);
  setTimeout(() => {
    request({
      url: `http://localhost:${port}/books`,
      method: 'POST',
      headers: {'content-type' : 'application/json'},
      body: JSON.stringify({data: 'data'})
    });
  }, 2000);
});

Hi MounikaKommineni
Not sure that I understand your question, I'm not specifying anything here I'm just making a call right after server gets up and running. I did it just to show that if you make a call to your server express-oas-generator will catch it and parse parameters and update swagger specification.
Let me quote one thing from README.md:

Important! In order to get description of all parameters and JSON payloads you have to start using your REST API or run REST API tests against it so module can analyze requests/responses

So that means if you want to see all the parameters in swagger specification you have to run REST API tests (or just call your REST API with postman/insomnia/your favorite REST API client) against your service and then express-oas-generator will do the job for you - fill the specification.
Please let me know if it is clear.

Hi mpashkovskiy,
Thank you giving the clarity.  I have done the same initially only which is mentioned in the README.md
But the problem is when I post my data initially through postman in the swagger response body of post is getting displayed and request body is still empty. I have added screenshot for reference

could you please also attach postman screenshot, so I can reproduce it?

could you please also attach postman screenshot, so I can reproduce it?

i have updated my previous comment and below is the screenshot of postman

Ok, here is the problem: express-oas-generator (EOG) adds parameters handler as a very last middleware. If any middleware or path in router breaks the chain and doesn't pass execution to next middleware/router in the chain then very last EOG middleware won't be called. So call next() or next(err) as the very last line in your handler.
Some docs:

calling next() https://expressjs.com/en/guide/writing-middleware.html
handling errors with next() https://expressjs.com/en/guide/error-handling.html

To fix the problem call next() at the end of all your handlers. For example for POST handler the code will looks like:
router.post('/', async(req, res, next) => {
    var newBook = new Book();
    console.log(req.body)
    newBook.set(req.body);
    await newBook.save(function(err, book) {
        if (err) {
            res.status(HttpStatus.BAD_REQUEST)
            .send({
                error: HttpStatus.getStatusText(HttpStatus.BAD_REQUEST)
            });
            next(err);
        } else {
            res.status(HttpStatus.OK)
            .send(book)
            next();
        }
    });
  });

Thank you for pushing this issue forward. Let me know if there are still problems.

Many Thanks for solving my issue.
It's working.

I suggest adding this information to the documentation/README file.

@garretaserra, added: https://github.com/mpashkovskiy/express-oas-generator#troubleshooting

@mpashkovskiy can we somehow make it possible to add in as first middleware

@mpashkovskiy can we somehow make it possible to add in as first middleware

@duke7able We cannot because we need to analyze the response object after you send the response.
But that makes me think -- perhaps we could hook into express' res.send function and handle our logic there so that the end user does not need to call next() everywhere (at times it's not even supposed to be called - see https://github.com/mpashkovskiy/express-oas-generator/issues/36).
I think it might be possible - I'm looking at express' source code right now, and it seems that you can access req and other variables from res.send. Needs more investigation.
https://github.com/expressjs/express/blob/master/lib/response.js#L107-L111
/cc @mpashkovskiy

@duke7able We cannot because we need to analyze the response object after you send the response.
But that makes me think -- perhaps we could hook into express' res.send function and handle our logic there so that the end user does not need to call next() everywhere (at times it's not even supposed to be called - see https://github.com/mpashkovskiy/express-oas-generator/issues/36).
I think it might be possible - I'm looking at express' source code right now, and it seems that you can access req and other variables from res.send. Needs more investigation.
https://github.com/expressjs/express/blob/master/lib/response.js#L107-L111
/cc @mpashkovskiy

Just a small "wording fix": not "after you send the response." but "after your server sends the response."
In overall @kiprasmel it is an excellent idea to hook to res.send!

Just a small "wording fix": not "after you send the response." but "after your server sends the response."
In overall @kiprasmel it is an excellent idea to hook to res.send!

@kiprasmel check this out https://stackoverflow.com/questions/47518962/specify-express-middleware-that-always-runs-at-the-end

@kiprasmel check this out https://stackoverflow.com/questions/47518962/specify-express-middleware-that-always-runs-at-the-end

@matveypashkovskiy oh wow that's amazing, it seems like we can make it happen!
Sadly I'm currently hella bussy - if anyone wants to take a shot at creating a PR - let us know by commenting here, and try your luck:)

@matveypashkovskiy oh wow that's amazing, it seems like we can make it happen!
Sadly I'm currently hella bussy - if anyone wants to take a shot at creating a PR - let us know by commenting here, and try your luck:)

ok, I'll check, or maybe you, @duke7able, want to give it a try?

ok, I'll check, or maybe you, @duke7able, want to give it a try?

moved to https://github.com/mpashkovskiy/express-oas-generator/issues/81

ok, I'll check, or maybe you, @duke7able, want to give it a try?

Sorry covid hit us bad, needed to cut of time from foss . I could contribute in it later, but i dont have a specific timeline

I have similar question, I defined my route and I know I need to some parameters in body but I do not know how to define/show these parameters on doc.
This is my route;
router.post('/login', errorHandler(async (req, res) => {
    const { username, password } = req.body;
    const loginResult = await UserService.login({ username, password });
    if (loginResult) {
      return res.status(200).json({
        success: true,
        ...loginResult
      });
    }
    return res
      .status(401)
      .json({ success: false, msg: 'Incorrect username or password' });
  })
);

And I used advanced implementation of generator;
expressOasGenerator.handleResponses(app, {
  predefinedSpec: (spec) => {
    _.set(spec, 'info', options.swaggerDefinition.info);
    _.set(spec, 'mongooseModels', mongoose.modelNames());
    _.set(spec, 'components.securitySchemes.bearerAuth', {
      type: 'http',
      scheme: 'bearer',
      bearerFormat: 'JWT'
    });
    _.set(spec, "paths['/v1/some-path'].get.security", [{ bearerAuth: [] }]);
    return spec;
  },
  mongooseModels: mongoose.modelNames(),
  alwaysServeDocs: true
});

...
createRoutes(app);

...

expressOasGenerator.handleRequests();
app.listen(port, () => {
  logger.info(`App running on port ${port}`);
});

But on the localthost:3000/api-docs I can't see the body parameters, how can I define and show on doc those parameters? Can someone help me?


about the paper request

Hello, I really hope to get your paper, but I have not found the relevant information of this paper, could you please provide it

Hello, our paper is presently under review. We will be happy to keep you updated as soon as it is available for inclusion!


Fix for issue 6

https://github.com/balexand/email_validator/issues/6
Basically there are two modes now, according to http://www.remote.org/jochen/mail/info/chars.html
normal: allow all characters marked as YES and MAYBE
strict mode: allow all characters marked as YES

Hi @gucki . I made a few changes. Mainly I just cleaned up the redundancy in the specs. Can you please review my changes. If everything looks good then I'll release v1.3.0. Thanks!

Hi @balexand, looks good to me! Looking forward to 1.3.0, thanks in advance :)

Ah, one thing left: I made strict mode explicit because of backwards compatibility...but if fact I think strict mode should be the default. What do you think would be better?

After thinking about this more, I'm more concerned about backward compatibility than about strictness. I updated the regexp so that in default mode, the only difference from v1.2.4 is that the length of local-part is validated. I'm okay with this since RFC2821 (section <IP_ADDRESS>) clearly states that the max length of the local-part is 64 characters.
Strict validation can be enabled by passing the :strict_mode option to the validates method or it can be set as default. See the README.
@gucki Does this work for you? I'm open to input.


chore(deps): update common-dev-assets digest to dd53916

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
5fa5912 -> dd53916

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

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


DPS Client over MQTT

cant make it to work with Paho over web-sockets. Finally I used a dps-proxy with CORS enabled

cant make it to work with Paho over web-sockets. Finally I used a dps-proxy with CORS enabled


Verify response signature

Mandatory to verify that the message has been signed
Optionally: certificate revocation over CRL and/or OCSP

Implemented with release v1.1. Certificate chain validation against CRL/OCSP can be optionally turned off.


Update .editorconfig

Insert final newlines to prevent noisy Git diffs.

Should also run formatter on files so that people don't get noisy diffs the first time that they use this template.


Hot-swapper does not check types of new states vs. old states

On http://elm-lang.org/blog/Interactive-Programming.elm, it is said: "The hot-swapper can also check to see if the types of the old state matches the types of the new state, ruling out a whole class of hot-swapping-induced runtime errors."
However, that checking is not currently done by the hot-swapper, as can be seen here: https://github.com/elm-lang/core/blob/2.0.1/src/Native/Runtime.js#L449-L460 (which only compares structure, not types).
I suggest to add this issue here to the Swapping milestone.

@vilterp (Hi, Peter), this issue belongs on the https://github.com/elm-lang/elm-reactor/milestones/Swapping list, IMHO. Evan agreed on that here, but somehow it still did not end up added to the milestone yet.

Currently the reactor is different than what's described in the Interactive Programming post because it actually doesn't hot-swap, it only swaps. I.e. it bypasses the difficulty of verifying that the signal graph has the same structure and types by simply starting the new module from the beginning and replaying all the recorded events over it. Thus the signal graph of the new module can be completely different and we're fine (the downside is that replay time scales linearly with # events recorded).
I'm going to close this now; can come back to it if we implement real hot-swapping in reactor as opposed to replaying.

But http://elm-lang.org/try does use hot-swapping, right? So the issue described here is real and affecting current use. I'd rather not see it left unnoticed.
One could argue that since the reactor itself does not use hot-swapping right now, the reactor repo is not the right place for this as an open issue. Well, it was once an issue opened against the core repo (https://github.com/elm-lang/core/issues/81), until @evancz proposed to move it over here.
So: should I reopen that other issue instead of this one?


[Bug] Probabilistic Roadmap

Either takes WAY too much time or something is deadly wrong in this script.

It just takes WAY too much time. Resolved in last commit.


fix: use positional arg for directory name

Types of changes

[x] Bug fixes

resolves https://github.com/frouriojs/create-frourio-app/issues/308

[ ] Features

resolves #

[ ] Maintenance
[ ] Documentation

Changes
Additional context
Community note

Please upvode with reacting as :+1: to express your agreement.


Staff Dashboard Metrics: As staff I can see a tile for overdue tasks and click it to render a table of pets with overdue tasks

On the staff dashboard index page we can add value by showing a quick glance of metrics, and allowing staff to quickly access work that needs to be done.
In this issue, we want to modify one of the existing tiles to show information on Pet Tasks. Specifically, show the total number of tasks that are not complete AND not overdue, and the number of tasks that are overdue, on all pets. The staff should be able to click on each stat in the tile, and using hotwire, we render a table below of Pets for which these tasks belong. For example, if I click 'Overdue', the table is populated with Pets with overdue tasks. Let's create a table that shows the Pet image, name, and a column for the number of tasks. The staff should be able to click this pet name and be redirected to that pet's show page.
This is a rough representation of the requirements (ignore the columns to the right of the pet name, these are irrelevant).

On the index action we will want to generate the stats for overdue tasks and incomplete tasks (not overdue) to show in the tile
Make two new actions on the staff dashboard controller to handle generating the responses for click the Overdue and Not overdue links in the tile, you will need to get the appropriate data for the table, including Pet image, name, and number of tasks (incomplete and not overdue, or overdue)
Add tests to make sure the collections generated for each route contain what we expect
The table should be paginated (I'd say 5 rows per page?)

There's a lot happening here, so let me know if you have questions!

Hi @kasugaijin I can take up this issue. Can you please assign it to me?

@sarvaiyanidhi all yours!

Just a quick update that I will work on this now from this week and will try push asap. sorry for the delay.

Just a quick update that I will work on this now from this week and will try push asap. sorry for the delay.

No worries @sarvaiyanidhi !! Thank you for the update.

Absolutely no rush!


layers: GH618, Correct WSI exension flag usage

Object_tracker had no notion of individual WSI extension flags,
and unique_objects was not checking them.
Change-Id: I93c1aa0c324aa602717f36e2975120dba8bc364e

The initialization of the layer's extension dispatch table pointers could be done conditionally as Ian points out.  However, this pattern that Mark is adding here has been done repeatedly in the layers and it should function just fine.  The various wsi  enabled  flags are checked int he layer's Get*ProcAddr function instead of at CreateDevice  and CreateInstance.  This checking of the flags in GIPA/GDPA is the critical piece for the WSI extension intercept to work properly (ie only intercept if the extension is enabled).

Other than the one comment about code duplication, LGTM

Cherry-picked to Master.
commit 61d505ea40b189b7ae63f311e2f13210eef219d2
Author: Mark Lobodzinski<EMAIL_ADDRESS>Date:   Fri Jun 24 09:57:32 2016 -0600'
layers: GH618, Correct WSI exension flag usage

Object_tracker had no notion of individual WSI extension flags,
and unique_objects was not checking them.


feat: Update pasword modal

Update password modal

The missing token is the session token?
The req body show oldpassword and newpassword

The res shows only a msg

The missing token is the session token?

Token is supposed to be sent as a Bearer token in the Authorization header. Check out this file.

@PedroChaparro i need help here, i'm not sure what is the problem with the test

@PedroChaparro i need help here, i'm not sure what is the problem with the test

First of all, don't use the production URL for development or testing purposes. You are supposed to use the Python Proxy locally, which is why we created the docker-compose file.
Probably the error is caused because of that. Also, you are not using random values for the username and password fields, so your tests only work when they are run for the first time with an empty database. That could be another cause of the error.

@PedroChaparro i'm not sure what´s the problem in here now


Export not working correctly with some AE Effects 😭

Hey ,
I created a loading animation today, thinking that I could use bodymovin to export it to json and use it in our cross platform applications.
Guess it got a little too complex  🏃 💨 😅
I ran into problems converting the CC scatterize and glow effect.
While reading through the open and closed issues, I realized that the effect might just not been included to the plugin.
I still kinda hope that you have a chance to look into my problem and might give me an advice or a workaround to get this bad ass up and running ^^
Thanks!

appointer_co_loading.zip

I'm having a somewhat similar similar issue. The compositions I have in ae are not rendering correctly in the bodymovin preview mode, nor in the json files. I also had to use an older version of the bodymovin extension as the latest version would not even load in the latest after effects.
Does anyone have a similar issue to mine or cedricbals? Any fixes or guidance anyone can provide?
Thank you ~

@cedricbals neither CC scaterize nor glow is supported by bodymovin. Check the wiki for supported features and effects
https://github.com/bodymovin/bodymovin/wiki/Effects


Istio init container crash

istio init container crash
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
client version: 1.6.0
pilot version: 1.5.0
istiod version: 1.6.0
data plane version: 1.5.0 (8 proxies), 1.6.0 (3 proxies)
How was Istio installed?
version 1.5.0:
istioctl manifest apply
version 1.6.0:
istioctl install --set revision=canary -f values.yaml
Environment where bug was observed (cloud vendor, OS, etc)
CentOS Linux release 7.7.1908 (Core)
init container logs
Environment:
------------
ENVOY_PORT=
INBOUND_CAPTURE_PORT=
ISTIO_INBOUND_INTERCEPTION_MODE=
ISTIO_INBOUND_TPROXY_MARK=
ISTIO_INBOUND_TPROXY_ROUTE_TABLE=
ISTIO_INBOUND_PORTS=
ISTIO_LOCAL_EXCLUDE_PORTS=
ISTIO_SERVICE_CIDR=
ISTIO_SERVICE_EXCLUDE_CIDR=

Variables:
----------
PROXY_PORT=15001
PROXY_INBOUND_CAPTURE_PORT=15006
PROXY_UID=1337
PROXY_GID=1337
INBOUND_INTERCEPTION_MODE=REDIRECT
INBOUND_TPROXY_MARK=1337
INBOUND_TPROXY_ROUTE_TABLE=133
INBOUND_PORTS_INCLUDE=*
INBOUND_PORTS_EXCLUDE=15090,15021,15020
OUTBOUND_IP_RANGES_INCLUDE=*
OUTBOUND_IP_RANGES_EXCLUDE=
OUTBOUND_PORTS_EXCLUDE=
KUBEVIRT_INTERFACES=
ENABLE_INBOUND_IPV6=false

Writing following contents to rules file:  /tmp/iptables-rules-1590592535343591764.txt532247932
* nat
-N ISTIO_REDIRECT
-N ISTIO_IN_REDIRECT
-N ISTIO_INBOUND
-N ISTIO_OUTPUT
-A ISTIO_REDIRECT -p tcp -j REDIRECT --to-ports 15001
-A ISTIO_IN_REDIRECT -p tcp -j REDIRECT --to-ports 15006
-A PREROUTING -p tcp -j ISTIO_INBOUND
-A ISTIO_INBOUND -p tcp --dport 22 -j RETURN
-A ISTIO_INBOUND -p tcp --dport 15090 -j RETURN
-A ISTIO_INBOUND -p tcp --dport 15021 -j RETURN
-A ISTIO_INBOUND -p tcp --dport 15020 -j RETURN
-A ISTIO_INBOUND -p tcp -j ISTIO_IN_REDIRECT
-A OUTPUT -p tcp -j ISTIO_OUTPUT
-A ISTIO_OUTPUT -o lo -s <IP_ADDRESS>/32 -j RETURN
-A ISTIO_OUTPUT -o lo ! -d <IP_ADDRESS>/32 -m owner --uid-owner 1337 -j ISTIO_IN_REDIRECT
-A ISTIO_OUTPUT -o lo -m owner ! --uid-owner 1337 -j RETURN
-A ISTIO_OUTPUT -m owner --uid-owner 1337 -j RETURN
-A ISTIO_OUTPUT -o lo ! -d <IP_ADDRESS>/32 -m owner --gid-owner 1337 -j ISTIO_IN_REDIRECT
-A ISTIO_OUTPUT -o lo -m owner ! --gid-owner 1337 -j RETURN
-A ISTIO_OUTPUT -m owner --gid-owner 1337 -j RETURN
-A ISTIO_OUTPUT -d <IP_ADDRESS>/32 -j RETURN
-A ISTIO_OUTPUT -j ISTIO_REDIRECT
COMMIT

iptables-restore --noflush /tmp/iptables-rules-1590592535343591764.txt532247932
iptables-restore: line 2 failed
iptables-save
# Generated by iptables-save v1.6.1 on Wed May 27 15:15:35 2020
*mangle
:PREROUTING ACCEPT [1076136:140933167]
:INPUT ACCEPT [1076136:140933167]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [915772:172731597]
:POSTROUTING ACCEPT [915772:172731597]
COMMIT
# Completed on Wed May 27 15:15:35 2020
# Generated by iptables-save v1.6.1 on Wed May 27 15:15:35 2020
*raw
:PREROUTING ACCEPT [1076136:140933167]
:OUTPUT ACCEPT [915772:172731597]
COMMIT
# Completed on Wed May 27 15:15:35 2020
# Generated by iptables-save v1.6.1 on Wed May 27 15:15:35 2020
*nat
:PREROUTING ACCEPT [28633:1717980]
:INPUT ACCEPT [94041:5119196]
:OUTPUT ACCEPT [48620:4173884]
:POSTROUTING ACCEPT [48620:4173884]
:ISTIO_INBOUND - [0:0]
:ISTIO_IN_REDIRECT - [0:0]
:ISTIO_OUTPUT - [0:0]
:ISTIO_REDIRECT - [0:0]
-A PREROUTING -p tcp -j ISTIO_INBOUND
-A OUTPUT -p tcp -j ISTIO_OUTPUT
-A ISTIO_INBOUND -p tcp -m tcp --dport 22 -j RETURN
-A ISTIO_INBOUND -p tcp -m tcp --dport 15090 -j RETURN
-A ISTIO_INBOUND -p tcp -m tcp --dport 15021 -j RETURN
-A ISTIO_INBOUND -p tcp -m tcp --dport 15020 -j RETURN
-A ISTIO_INBOUND -p tcp -j ISTIO_IN_REDIRECT
-A ISTIO_IN_REDIRECT -p tcp -j REDIRECT --to-ports 15006
-A ISTIO_OUTPUT -s <IP_ADDRESS>/32 -o lo -j RETURN
-A ISTIO_OUTPUT ! -d <IP_ADDRESS>/32 -o lo -m owner --uid-owner 1337 -j ISTIO_IN_REDIRECT
-A ISTIO_OUTPUT -o lo -m owner ! --uid-owner 1337 -j RETURN
-A ISTIO_OUTPUT -m owner --uid-owner 1337 -j RETURN
-A ISTIO_OUTPUT ! -d <IP_ADDRESS>/32 -o lo -m owner --gid-owner 1337 -j ISTIO_IN_REDIRECT
-A ISTIO_OUTPUT -o lo -m owner ! --gid-owner 1337 -j RETURN
-A ISTIO_OUTPUT -m owner --gid-owner 1337 -j RETURN
-A ISTIO_OUTPUT -d <IP_ADDRESS>/32 -j RETURN
-A ISTIO_OUTPUT -j ISTIO_REDIRECT
-A ISTIO_REDIRECT -p tcp -j REDIRECT --to-ports 15001
COMMIT
# Completed on Wed May 27 15:15:35 2020
# Generated by iptables-save v1.6.1 on Wed May 27 15:15:35 2020
*filter
:INPUT ACCEPT [1076136:140933167]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [915772:172731597]
COMMIT
# Completed on Wed May 27 15:15:35 2020
panic: exit status 1

goroutine 1 [running]:
istio.io/istio/tools/istio-iptables/pkg/dependencies.(*RealDependencies).RunOrFail(0x38e0918, 0x21a3e72, 0x10, 0xc0003dba80, 0x2, 0x2)
	istio.io/istio/tools/istio-iptables/pkg/dependencies/implementation.go:44 +0x96
istio.io/istio/tools/istio-iptables/pkg/cmd.(*IptablesConfigurator).executeIptablesRestoreCommand(0xc000653d68, 0x2199a01, 0x0, 0x0)
	istio.io/istio/tools/istio-iptables/pkg/cmd/run.go:482 +0x387
istio.io/istio/tools/istio-iptables/pkg/cmd.(*IptablesConfigurator).executeCommands(0xc000653d68)
	istio.io/istio/tools/istio-iptables/pkg/cmd/run.go:489 +0x45
istio.io/istio/tools/istio-iptables/pkg/cmd.(*IptablesConfigurator).run(0xc000653d68)
	istio.io/istio/tools/istio-iptables/pkg/cmd/run.go:436 +0x25ef
istio.io/istio/tools/istio-iptables/pkg/cmd.glob..func1(0x388e180, 0xc000155600, 0x0, 0x10)
	istio.io/istio/tools/istio-iptables/pkg/cmd/root.go:64 +0x148
github.com/spf13/cobra.(*Command).execute(0x388e180, 0xc000155500, 0x10, 0x10, 0x388e180, 0xc000155500)
	github.com/spf13/cobra@v1.0.0/command.go:846 +0x29d
github.com/spf13/cobra.(*Command).ExecuteC(0x388e420, 0x0, 0x0, 0x0)
	github.com/spf13/cobra@v1.0.0/command.go:950 +0x349
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.0.0/command.go:887
main.main()
	istio.io/istio/pilot/cmd/pilot-agent/main.go:504 +0x2d

Seems similar to https://github.com/istio/istio/issues/24101

@erdun 这个问题我也遇到了，找了很久才发现是我清理了docker容器命令造成的istio-init重启

This is caused by the init container cleaned

@erdun 这个问题我也遇到了，找了很久才发现是我清理了docker容器命令造成的istio-init重启

Thank you for the update! I saw user reported istio-restore report failure at line 2 in the past.
This line is supposed to create the chain ISTIO_REDIRECT but I wasn't able to find why istio-init is running on a pod which has istio iptables setup prior to istio-init.

@erdun 这个问题我也遇到了，找了很久才发现是我清理了docker容器命令造成的istio-init重启

Thank you for the update! I saw user reported istio-restore report failure at line 2 in the past.
This line is supposed to create the chain ISTIO_REDIRECT but I wasn't able to find why istio-init is running on a pod which has istio iptables setup prior to istio-init.

It happens when the container istio-init is removed and restarted, the iptables rules has been set at this scenario, I can reproduce it by remove the container istio-init.
I am wondering why iptables rules restoring fails when rules are existing?

Could we remove the chains first to prevent the panic reported by istio-init container?

According to K8S devs, init containers need to be reentrant:
https://github.com/kubernetes/kubernetes/issues/90271#issuecomment-616238111

@lambdai  这个问题我也遇到了，找了很久才发现是我清理了docker容器命令造成的istio-init重启

Thank you for the update! I saw user reported istio-restore report failure at line 2 in the past.
This line is supposed to create the chain ISTIO_REDIRECT but I wasn't able to find why istio-init is running on a pod which has istio iptables setup prior to istio-init.

It happens when the container istio-init is removed and restarted when the pod is running, the iptables rules has been set when the pod is created and istio-init is initialized at firstly time.
I can reproduce it by remove the container istio-init when the status is Running and condition is Ready of pods.

Could you please help tell me how to remove the container istio-init?  I used docker kill on host, but it did not reproduce. Thanks.

I ran into the same issue . Could we remove the chain when it already exists to prevent the panic reported by istio-init container?

@zhaohuabing @willemm There is no well-guaranteed approach. But yes I think we can deduct whether the istio rules are injected already from the existing iptables rules.

@lambdai  这个问题我也遇到了，找了很久才发现是我清理了docker容器命令造成的istio-init重启

Thank you for the update! I saw user reported istio-restore report failure at line 2 in the past.
This line is supposed to create the chain ISTIO_REDIRECT but I wasn't able to find why istio-init is running on a pod which has istio iptables setup prior to istio-init.

It happens when the container istio-init is removed and restarted when the pod is running, the iptables rules has been set when the pod is created and istio-init is initialized at firstly time.
I can reproduce it by remove the container istio-init when the status is Running and condition is Ready of pods.

Could you please help tell me how to remove the container istio-init? I used docker kill on host, but it did not reproduce. Thanks.

I am not fully sure but my guess is either docker container rm or docker container prune. Manually running docker cmd on the node acts as a backdoor of kubelet. Not an expert but I believe it's undefined behavior to k8s.


Fix FSMIntegerField label and use new _meta API in Django 1.8+

Ok, so let me try again. This is the previous diff, but _meta API availability is tested at import time. Both old and new style _meta should be supported. Again, fixes #77.

Cool! Thank you! That's much better


Faq illustration

Describe the bug
Hey @wasimreja, I would like to open this issue under JWOC.

Steps to reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots
This illustration is not looking good with a white background in dark mode. I wish to improve this
Desktop

OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]

Smartphones

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
No response

@ritika728 add one more question in faq. if anyone wants to contribute and put the link of the repository.

I want to contribute this issue under JWOC


Examples broken

All of the examples point to viewconfs that were on the previous database version. They need to be recreated.
Should be pulled from github gists.

Examples are now pulled from the latest gist:
https://gist.github.com/pkerpedjiev/104f6c37fbfd0d7d41c73a06010a3b7e


error try to do an upload

I used the library a months ago and everything was fine to upload  my app, but I try to made an update this week and I have the next error, I try to find if it's a problem with my npm but I don't know :/
thanks!!!
AppData\Roaming\npm\node_modules\ios-uploader\node_modules\simple-plist\simple-plist.js:20
throw new Error(error)
^
Error: Error: maxObjectCount exceeded

Hi, this is an error given by one of the applications dependencies. I believe it's something about the Info.plist in your ipa-file it doesn't agree with. If you would be willing to send over your .ipa I might be able to troubleshoot it.

Hi, this is an error given by one of the applications dependencies. I believe it's something about the Info.plist in your ipa-file it doesn't agree with. If you would be willing to send over your .ipa I might be able to troubleshoot it.

Hi Simon, yes, you have the right, my apologies, I Don't not why I not saw that, I was thiking that it was a mistakes with some npm depencency! thanks! I will try to fix by my own! have a nice day, week, month etc

Hi Simon, yes, you have the right, my apologies, I Don't not why I not saw that, I was thiking that it was a mistakes with some npm depencency! thanks! I will try to fix by my own! have a nice day, week, month etc

Hi, this is an error given by one of the applications dependencies. I believe it's something about the Info.plist in your ipa-file it doesn't agree with. If you would be willing to send over your .ipa I might be able to troubleshoot it.

Have similar issue - can you explain what I have to do to fix this?

Hi, this is an error given by one of the applications dependencies. I believe it's something about the Info.plist in your ipa-file it doesn't agree with. If you would be willing to send over your .ipa I might be able to troubleshoot it.

Have similar issue - can you explain what I have to do to fix this?

@VirsabiMunk This error i thrown by the joeferner/node-bplist-parser module. This is if your Info.plist file contains more than the default limit of 32768 objects. This file usually only contains around 260 objects.
It might also be that there is nothing wrong with your Info.plist but that the wrong file is identified as your main Info.plist in the IPA. But without having an IPA file showing the issue it is difficult for me to troubleshoot.

@VirsabiMunk This error i thrown by the joeferner/node-bplist-parser module. This is if your Info.plist file contains more than the default limit of 32768 objects. This file usually only contains around 260 objects.
It might also be that there is nothing wrong with your Info.plist but that the wrong file is identified as your main Info.plist in the IPA. But without having an IPA file showing the issue it is difficult for me to troubleshoot.

As I don't have anything to go on in order to resolve this issue I will close it for now. If someone still encounters this issue and can give me a way to reproduce it please reopen the issue.


[stable/spinnaker] Relax PSP

Some processes need to change files from different users (deck for
instance).
If the pod is run as non root, deck does not start:

cp: cannot create regular file 'spinnaker.conf': Permission denied
sed: can't read spinnaker.conf: No such file or directory
sed: can't read spinnaker.conf: No such file or directory
sed: can't read spinnaker.conf: No such file or directory
mv: cannot stat 'spinnaker.conf': No such file or directory
ERROR: Site spinnaker does not exist!
Could not remove /etc/apache2/sites-enabled/000-default.conf: Permission denied
cp: cannot create regular file 'ports.conf': Permission denied
sed: can't read ports.conf: No such file or directory
sed: can't read ports.conf: No such file or directory
mv: cannot stat 'ports.conf': No such file or directory
cp: cannot create regular file 'passphrase': Permission denied
sed: can't read passphrase: No such file or directory
chmod: cannot access 'passphrase': No such file or directory
mv: cannot stat 'passphrase': No such file or directory
cp: cannot create regular file '/opt/deck/html/settings.js': Permission denied
chown: changing ownership of '/var/lock/apache2.ZWzj1uONRl': Operation not permitted

Relaxing the PSP to allow this.

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test
/lgtm


Refactor 'kernel_3d' section of deepseg_sc/core

Todo:

Impose isotropic resolution (0.5mm3)
Centralize all resampling operations in the same place
Expand the testing of 'kernel_3d' method

Will be replaced by sct_deepseg, which fixes these issues


Error during template rendering. no model name parse

don't know the reason but
removing boards/templatetags/gravatar.py works


Attempt concurrency with v2.3.1-Ghost-R branch (merge)

Hasn't been done for a while now so I'll try doing this later, or someone else can. This probably doesn't affect much

Nevermind I guess it will happen today

that's weird why the hell would they let me delete the branch like that... ok i'm probably not doing that again

Ok this might have some weird consequences so I might just have to make emergency changes


if user is using mobile display an alert to rotate a device

https://github.com/hardikhere/piggame.github.io/pull/5

#5

thanks


How to allow HTML in ORG chart

Version
Tell us which versions you are using:
react-google-charts 1.5.3
react v0 15.14.1
Expected behaviour
Allow HTML in Chart
Actual behaviour
Html is not being rendered
Steps to reproduce

Link to a git repo that reproduces bug :

Could you please provide some example code that explains what you're trying to achieve ?

I was planning to implement something like this using react variant of
google chart:
https://jsfiddle.net/api/post/library/pure/
The issue here is html is not being encoded and html is appearing in chart.
Thanks,
Venu
On Wed, Mar 22, 2017 at 11:59 AM, Rakan Nimer<EMAIL_ADDRESS>wrote:

Could you please provide some example code that explains what you're
trying to achieve ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RakanNimer/react-google-charts/issues/120#issuecomment-288310389,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGQxuI3HUdOTzcQmcN8oPysARCrswArQks5roL_FgaJpZM4MkxFj
.

This fiddle appears to be empty (did you forget to save ?)
I'd see if it's possible using the google charts api if it is
then, odds are this library support it.
Closing the issue, please feel free to re-open it if the issue persists

Below are the two fiddle samples one from google chart and other on react google chart:
https://jsfiddle.net/mq2216d3/1/
https://jsfiddle.net/f8zpr8uc/48/
Here there are two issues
1.The root node is not display the text in F field as compared to non react  Google Chart
2. The html's are not getting encoded.
Thansk,
Venu


Checking the audiobook conformance of a RWPM + getting the durations

According to the Readium Audiobook Profile, a RWPM must contain the duration property in the Link objects to conform.
However, the mobile toolkits Publication.conformsTo() API is only checking the media type in the reading order, not the availability of duration, so it's not checking full conformance. The reason for this is that we don't have the info for Zipped Audiobooks.
As a workaround, we could add an Audio/MediaPublicationService which will compute the duration from:

the duration Link object properties for streamed manifests
the resource metadata for Readium Packages and ZAB

Then, the conformsTo() API could use this info to check that the duration is available for all the resources of the reading order.

In hindsight, I feel like the conformsTo method might have been a mistake. To really check conformance to a profile, we have Publication.metadata.conformsTo. The method (vs the property) has been designed to determine which navigator should be used to render the publication. I don't think that's the responsibility of the shared module. Each navigator should be able to claim which publication it supports, whatever profile it conforms to, if any.

Each navigator should be able to claim which publication it supports, whatever profile it conforms to, if any.

I like this idea, testing a queue of navigator implementations until one handles the publication. In which case, that's fine if we're stricter with the conformsTo() API.

Makes sense to me.


New package: XBRL v0.1.0

Registering package: XBRL
Repository: https://github.com/robfs/XBRL.jl
Created by: @robfs
Version: v0.1.0
Commit: 62b60d04545a4e1c85be2d98b3ce681b90043034
Git reference: HEAD
Description: Package for parsing XBRL

Presumably superseded by #55168


Linking does not work in develop branch

Bug Report
Linking to an external account is broken on develop branch.
This was introduced by the implementation for #2386 -- in links.model.ts, the properties are compiled with the values of dockstore.model.ts before it has been updated by calling /metadata/config.json.
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.7
┆Issue Number: DOCK-747

quay, github seem to link properly on staging.dockstore.org


Update user guide

Codecov Report
Base: 77.11% // Head: 77.11% // No change to project coverage :thumbsup:

Coverage data is based on head (f7ae3ff) compared to base (95e5a78).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #134   +/-   ##
=========================================
  Coverage     77.11%   77.11%
  Complexity      759      759
=========================================
  Files           117      117
  Lines          2272     2272
  Branches        287      287
=========================================
  Hits           1752     1752
  Misses          444      444
  Partials         76       76

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


add celu kernel

kernel:celu
tu:celu

 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.

merge pr[320] with elu


Add Display impls for connection strings

So we can serialize them back out after parsing.

Done in 0.1.9


Minor fixes to README's examples

First off, great job!
Hope you guys don't mind, this just fixes two minors in README's examples.

Current coverage is 84.00% (diff: 100%)

Merging #73 into master will not change coverage

@@             master        #73   diff @@
==========================================
  Files            13         13
  Lines           400        400
  Methods           0          0
  Messages          0          0
  Branches         57         57
==========================================
  Hits            336        336
  Misses           51         51
  Partials         13         13

Powered by Codecov. Last update 217af05...868de76

Thanks for the PR, merged an older one that made the same change


Feature request: macros

Have you considered defining macros for main commands (i.e. @run)?

[x] Complete macros
[x] Include into documentation
[x] Include into testing
[x] update examples
[ ] release 0.3.1
[ ] announce on discourse

yes, I did consider macros and I think they could be a great addition, mainly @fun, @Prc, @process!, @event! and friends. I would like if somebody joined me with some help.

Sounds good. I'll see if I can make some time in the next couple of weeks to take a look at that implementation.￼￼

@process, @event, @run! added: https://github.com/pbayer/DiscreteEvents.jl/pull/30#issue-485896653

@hdavid16 thank you very much for your PR! This is a great addition.
Could you please complete the macros as suggested in the PR?
Then I merge, do the integration into documentation and testing
and release 0.3.1.

I reopen now for steps 2..4

With the above commits I

updated the 2-argument @event macro to accept a 1) function call, 2) an anonymous function and 3) a time argument,
added a @periodic macro,
updated docs and examples

Release DiscreteEvents 0.3.1
Introduces a macro API with contributions of @hdavid16
@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/21484
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.1 -m "<description of version>" 5feccdb697cd938402e02e52013ea22560bff8d8
git push origin v0.3.1

everything done. Hopefully this time more interest and feedback on discourse!
Thank you very much @hdavid16 .


added emojify

Emoji on the command line ... [via @mahemoff 's twitter] :scream:

Each section is ordered alphabetically; could you place emojify in the right spot? Thanks.

:+1: :zap: :rocket:


refactor: autogenerate metrics docs

Motivation
As mentioned at some point during the opentelemetry metrics changes, it would be nice if documentation could be autogenerated.
This PR does this so that there is a single source of truth for metrics and attributes.
This makes attribute documentation consistent, and the docs match the implementation in more places.
It will help when we do something about server metrics, and also with tracing (as tracing will want managed attributes and auto-generated docs).
Modifications
Create a new yaml file util/telemetry/builder/values.yaml which contains the attributes and metrics.
util/telemetry/builder/builder.go converts this into go structs and documentation which is inserted into the metrics.md docs. The go structs implement a new interface for builtin metrics.
This code change has the downside of making the shared utils directory aware of every metric again.
This fixes a few things:

The HELP for prometheus metrics will now exactly match the first line in the documentation.
The documentation for metrics are guaranteed to be in alphabetical order.
workers_busy_count has the correct attribute name (this is a legacy metric - the implementation matched 3.5 which is correct, but the docs did not match the implementation of having a different attribute name from the other queue metrics).

This can be further improved by enforcing the attributes which may mismatch at the moment, and removing all of the calls to Name() by instead allowing the operators to operate on the builtin metrics. This is left for a separate PR. This will also optimise the calls to the operators by pre-creating the attributes.
Verification
Unit and integration tests.
Some inspection of prometheus metrics from before and after.

I'm slightly surprised that the new markdown tables are passing CI. I thought there was a table linter? They aren't nice and pretty like they were before.

They aren't. The linter doesn't mind it, and some have been modified to look like this elsewhere by hand.
To make them pretty would need a prettifier, and this way is also easier for hand editing a bit like one sentence per line is.
Not remedying.

This is fine, I think I'd personally prefer if we used a markdown AST like https://github.com/yuin/goldmark.
This makes it possible to render the markdown nicely, it also makes parsing and doing inline modifications much easier.

Goldmark doesn't do nice rendering, it has an emphasis on reading markdown. I've implemented nao1215/markdown which brings in more dependencies, but does also make the tables prettier so that @tico24 can pretend he's happy too.


Spinner getSelectorName and setSelectorName use different fields

In the Spinner class:

setSelectorName sets the text in the attached label
getSelectorName returns the Actor name field

In the interests of consistency I think that the getSelectorName should return the text in the attached label.
Great library btw!

Fixed, thanks for reporting.


Updates CR concept docs with UserInfo fields and fields being immutable

Signed-off-by: joshvanl<EMAIL_ADDRESS>Adds description for the new UserInfo fields, and a note that all spec fields and cert-manager annotations are immutable.
We should merge this when we do the release.

/hold

Nit: would it be possible to add a link to the cert-manager PR where this feature was added in this PR? That helps a lot when trying to navigate 👍

/approve
/lgtm

/hold cancel


TextEditingController value is different than what is shown in TextField in RTL Text Direction

Steps to reproduce

Create A TextField widget with rtl text direction:
Type hi🤣 and see onChanged value.
The TextField shows 🤣hi which is correct.
The onChanged value shows hi🤣 which is incorrect.

Expected results
There should be consistency between what is shown in TextField and the onChanged value.
Actual results
Inconsistency between what is shown in TextField Box and what the actual value is.
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key});

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
      ),
      body: Center(
        child: TextField(
          maxLines: null,
          onChanged: (value) {
            print(value);
          },
          autofocus: false,
          textDirection: TextDirection.rtl,
          textAlignVertical: TextAlignVertical.center,
          style: const TextStyle(
            color: Color(0xffffffff),
          ),
          decoration: const InputDecoration(
            hintText: "Type a message",
            hintTextDirection: TextDirection.rtl,
            prefixIcon: Padding(
              padding: EdgeInsets.only(right: 2, top: 0, bottom: 0, left: 2),
            ),
          ),
        ),
      ),
    );
  }
}

Screenshots or Video
No response
Logs
No response
Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.5, on Ubuntu 22.04.4 LTS 6.5.0-35-generic, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Chrome - develop for the web
[✗] Linux toolchain - develop for Linux desktop
    ✗ clang++ is required for Linux development.
      It is likely available from your distribution (e.g.: apt install clang), or can be downloaded from https://releases.llvm.org/
    ✗ CMake is required for Linux development.
      It is likely available from your distribution (e.g.: apt install cmake), or can be downloaded from https://cmake.org/download/
    ✗ ninja is required for Linux development.
      It is likely available from your distribution (e.g.: apt install ninja-build), or can be downloaded from https://github.com/ninja-build/ninja/releases
    ✗ GTK 3.0 development libraries are required for Linux development.
      They are likely available from your distribution (e.g.: apt install libgtk-3-dev)
[✓] Android Studio (version 2023.3)
[✓] VS Code (version 1.90.0)
[✓] Connected device (3 available)
[✓] Network resources

! Doctor found issues in 1 category.

can you share snapshots & console log of your textfield controller.

you just neet to change
textDirection: TextDirection.rtl to textDirection: TextDirection.ltr

Reproducible using the code sample provided above.
This might be working as intended, it doesn't seem like onChanged takes the directionality into account when the value is being set.
Labeling for further insight.

flutter doctor -v
[!] Flutter (Channel stable, 3.22.2, on macOS 14.4.1 23E224 darwin-arm64, locale en-GB)
    • Flutter version 3.22.2 on channel stable at /Users/nexus/dev/sdks/flutter
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutters/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutter. Consider adding /Users/nexus/dev/sdks/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutters/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutter. Consider adding /Users/nexus/dev/sdks/flutter/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 761747bfc5 (12 days ago), 2024-06-05 22:15:13 +0200
    • Engine revision edd8546116
    • Dart version 3.4.3
    • DevTools version 2.34.3
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode-15.3.0.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Users/nexus/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.5)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 77.2.2
    • Dart plugin version 232.10286

[✓] VS Code (version 1.89.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.90.0

[✓] Connected device (5 available)
    • Nexus (mobile)                  • 00008020-001875E83A38002E • ios            • iOS 17.5.1 21F90
    • Dean’s iPad (mobile)            • 00008103-000825C811E3401E • ios            • iOS 17.5.1 21F90
    • macOS (desktop)                 • macos                     • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad     • darwin         • macOS 14.4.1 23E224 darwin-arm64
    • Chrome (web)                    • chrome                    • web-javascript • Google Chrome 126.0.6478.62

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 3.23.0-13.0.pre.242, on macOS 14.4.1 23E224 darwin-arm64, locale en-GB)
    • Flutter version 3.23.0-13.0.pre.242 on channel master at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5187cab7bd (2 days ago), 2024-06-14 23:35:34 -0400
    • Engine revision 9779c273aa
    • Dart version 3.5.0 (build 3.5.0-266.0.dev)
    • DevTools version 2.36.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode-15.3.0.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Users/nexus/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.5)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 77.2.2
    • Dart plugin version 232.10286

[✓] VS Code (version 1.89.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.90.0

[✓] Connected device (5 available)
    • Nexus (mobile)                  • 00008020-001875E83A38002E • ios            • iOS 17.5.1 21F90
    • Dean’s iPad (mobile)            • 00008103-000825C811E3401E • ios            • iOS 17.5.1 21F90
    • macOS (desktop)                 • macos                     • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad     • darwin         • macOS 14.4.1 23E224 darwin-arm64
    • Chrome (web)                    • chrome                    • web-javascript • Google Chrome 126.0.6478.62

[✓] Network resources
    • All expected network resources are available.

• No issues found!

          onChanged: (value) {
            print(value);
          }

print prints the in-memory representation of the text to the screen, it doesn't do the same type of rendering TextField does.


Computed columns shold be reported as IS_GENERATEDCOLUMN in DatabaseMetaData.getColumns(...)

Driver version or jar name
Please tell us what the JDBC driver version or jar name is.
6.3.6.jre8-preview
SQL Server version
Please tell us what the SQL Server version is.
SQL Server 2017 14.00.1000.169.v1
Client operating system
Please tell us what oprating system the client program is running on.
Windows 10 Professional
Java/JVM version
Example: java version "1.8.0", IBM J9 VM
1.8.0_121-b13
Table schema
Please tell us the table schema
CREATE TABLE X_EMPLOYEES
(
  EMPLOYEEID INTEGER NOT NULL,
  EMPLOYEE_NAME VARCHAR(30),
  START_DATE DATE,
  END_DATE DATE,
  ANNUAL_SALARY INTEGER,
  HOURLY_RATE AS (ANNUAL_SALARY/2080),
  ACTIVE AS (CASE WHEN END_DATE IS NULL THEN 'Y' ELSE 'N' END)
);

Problem description
Please share more details with us.
DatabaseMetaData.getColumns(...) should return a value of YES in IS_GENERATEDCOLUMN for columns HOURLY_RATE and ACTIVE in the table X_EMPLOYEES above.
Expected behavior and actual behavior
Please tell us what should happen and what happened instead
Please see the problem description above.
Repro code
Please share repro code with us, or tell us how to reproduce the issue.
Create the table using the SQL above, and run DatabaseMetaData.getColumns(...), and check the value of IS_GENERATEDCOLUMN for columns HOURLY_RATE and ACTIVE in the table X_EMPLOYEES above.

Hi @schemacrawler ,
Thank you for reporting the issue. The fix will be included in one of the upcoming preview releases.

Fix in #695.


Release workflow has been failing silently since 5th July

Is there supposed to be a release on every merge to main? If so, the release process appears to be broken.
The most recent release was v2.5.30 on 2023-07-05. There have been number of merges to main since then that have not been released.

Also, I am unable to get this to work in a Python AWS CDK Stack. Any tips/guidance would be appreciated.

Publish to NPM fails:
npm ERR! code E403
npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/cdk-ecr-deployment - You cannot publish over the previously published versions: 2.5.30.
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.

https://github.com/cdklabs/cdk-ecr-deployment/actions/runs/6758054038/job/18369299023#step:9:95

Publish to Maven Central fails:
Error:  Nexus Staging Rules Failure Report
Error:  ==================================
Error:
Error:  Repository "iogithubcdklabs-68364" failures
Error:    Rule "RepositoryWritePolicy" failures
Error:      * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/io/github/cdklabs/cdk-ecr-deployment/2.5.30/cdk-ecr-deployment-2.5.30-sources.jar'
Error:      * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/io/github/cdklabs/cdk-ecr-deployment/2.5.30/cdk-ecr-deployment-2.5.30-javadoc.jar'
Error:      * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/io/github/cdklabs/cdk-ecr-deployment/2.5.30/cdk-ecr-deployment-2.5.30.pom'
Error:      * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/io/github/cdklabs/cdk-ecr-deployment/2.5.30/cdk-ecr-deployment-2.5.30.jar'
Error:
Error:

https://github.com/cdklabs/cdk-ecr-deployment/actions/runs/6758054038/job/18369298568#step:10:8595

Publish to PyPi fails:
Uploading distributions to https://upload.pypi.org/legacy/
INFO     cdk_ecr_deployment-2.5.30-py3-none-any.whl (1.8 MB)
INFO     cdk-ecr-deployment-2.5.30.tar.gz (1.8 MB)
INFO     username set by command options
INFO     password set by command options
INFO     username: ***
INFO     password: <hidden>
WARNING  Skipping cdk_ecr_deployment-2.5.30-py3-none-any.whl because it appears
         to already exist
WARNING  Skipping cdk-ecr-deployment-2.5.30.tar.gz because it appears to already
         exist

https://github.com/cdklabs/cdk-ecr-deployment/actions/runs/6758054038/job/18369298796#step:10:112

Publish to NuGet fails:
Publishing NuGet packages...
📦  Publishing ./CdklabsCdkEcrDeployment.2.5.30.nupkg to NuGet
Pushing CdklabsCdkEcrDeployment.2.5.30.nupkg to 'https://www.nuget.org/api/v2/package'...
  PUT https://www.nuget.org/api/v2/package/
  Conflict https://www.nuget.org/api/v2/package/ [9](https://github.com/cdklabs/cdk-ecr-deployment/actions/runs/6758054038/job/18369299308#step:10:10)76ms
To skip already published packages, use the option --skip-duplicate
error: Response status code does not indicate success: 409 (A package with ID 'CdklabsCdkEcrDeployment' and version '2.5.30' already exists and cannot be modified.).

https://github.com/cdklabs/cdk-ecr-deployment/actions/runs/6758054038/job/18369299308#step:10:15

Publish to GitHub Go Module fails:
[main d40298a] chore(release): v2.5.30
 3 files changed, 23 insertions(+), 5 deletions(-)
All tags already exist. Skipping release

https://github.com/cdklabs/cdk-ecr-deployment/actions/runs/6758054038/job/18369299113#step:10:21

Publish Lambda to GitHub appears to work, however it is clobbering previous releases:
Run gh release upload --clobber -R $GITHUB_REPOSITORY v$(cat .repo/dist/version.txt) lambda/main lambda/main.sha[2](https://github.com/cdklabs/cdk-ecr-deployment/actions/runs/6758054038/job/18369299218#step:5:2)56
  gh release upload --clobber -R $GITHUB_REPOSITORY v$(cat .repo/dist/version.txt) lambda/main lambda/main.sha256
  shell: /usr/bin/bash -e {0}
  env:
    GITHUB_TOKEN: ***
    GITHUB_REPOSITORY: cdklabs/cdk-ecr-deployment

https://github.com/cdklabs/cdk-ecr-deployment/actions/runs/6758054038/job/18369299218
This change added the "--clobber" flag in an attempt to fix failing releases:
https://github.com/cdklabs/cdk-ecr-deployment/commit/0af6354cd741552e53db8f5538508c2875f073a2

The latest release on GitHub is showing assets from yesterday, but source code snapshots from 5th July:

This is the first commit after the last successful release:
https://github.com/cdklabs/cdk-ecr-deployment/commit/69575d444b7ca2116613046b94df1da026b160d1
I suspect this release filter broke the release process:
        "RELEASABLE_COMMITS": "git log --no-merges --oneline $LATEST_TAG..HEAD -E --grep '^(feat|fix){1}(\\([^()[:space:]]+\\))?(!)?:[[:blank:]]+.+'"

It seems this issue has been quietly/accidently fixed as part of this PR?
https://github.com/cdklabs/cdk-ecr-deployment/pull/411
Release 2.5.30 includes all the patches/changes from 2023-07-05:
https://github.com/cdklabs/cdk-ecr-deployment/compare/v2.5.30...v2.5.31

Seems like this can be closed?


[bug] Incompatible version error in Kaggle

!pip install -q pygwalker

Error
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
ibis-framework 6.2.0 requires sqlglot<18,>=10.4.3, but you have sqlglot 18.16.0 which is incompatible.

Use new version of kaggle notebook to fix it.


feat: add S3Fifo eviction for memory

What's changed and what's your intention?

This PR adds S3Fifo eviction policy based on https://blog.jasony.me/system/cache/2023/08/01/s3fifo and https://github.com/matrixorigin/matrixone/blob/c582b7d3ce8f7c177f2bd268a37375ae1a5b18bd/pkg/fileservice/fifocache/fifo.go#L24. It use a small queue and a main queue. The small queue is also served as the ghost queue.

Checklist

[ ] I have written the necessary rustdoc comments
[ ] I have added the necessary unit tests and integration tests
[ ] I have passed make all (or make fast instead if the old tests are not modified) in my local environment.

Related issues or PRs (optional)

@MrCroxx Thank for you maintaining foyer. I found this library is very well designed and are currently evaluating if it could be used in https://github.com/chroma-core/chroma for various caching scenarios. Chroma is one of the most popular embedding stores for RAG.
Chroma will use both memory and SSD for caches for different scenarios. We will also need different eviction policies for different scenarios. S3Fifo is a very promising policy and that's why I would like to collaborate with you on this.  The current PR is till a draft and are subject to change and improvements.
I would love to discuss with you more on how we can collaborate and discuss a bit more on how to use foyer as a hybrid cache.
Looking forward to speaking with you!
BTW, I used to work at PingCAP before joining Chroma.

Hi @Ishiihara . Thank you for your attention and contribution to foyer. I apologize for just seeing your PR now as I was on call these days. It will be an honor to have foyer as a component of Chroma.
To be honest, I'm not very familiar with what the workload of Chroma is like. And foyer still lacks the ability to handle small KVs as efficiently as it could be. I'm willing to hear from you about where you will use foyer and how can we make foyer better. 🥰
I'm glad to review this PR carefully after my shift. And I glanced at it briefly, it is implemented very well. And just a reminder, you can run make fast in your local environment first as a quick test.
And I'm glad to meet my former colleague here. I'm looking forward to discussing more via IM or offline. But I'm really careful to leave my personal IM on Github. I'll send you an email with my contact.

Hi @Ishiihara , thanks again for your contribution. I've modified the related codes to make them more compatible with foyer.
This PR still needs some unit tests with s3fifo (e.g. https://github.com/MrCroxx/foyer/blob/main/foyer-memory/src/eviction/lfu.rs#L425-L576). Could you please add some? 🙏 Then the PR is ready to be merged.

Hi @xiaguan , maybe you are also interested in this PR. 🥰

hit ratio bench result:
zif_exp, cache_size             fifo            lru             lfu             s3fifo          moka
0.90, 0.005                     16.24%          19.22%          32.37%          32.39%          33.50%
0.90, 0.01                      22.55%          26.20%          38.54%          39.20%          37.92%
0.90, 0.05                      41.05%          45.56%          55.37%          56.63%          55.25%
0.90,  0.1                      51.06%          55.68%          63.82%          65.06%          64.20%
0.90, 0.25                      66.81%          71.17%          76.21%          77.26%          77.12%
1.00, 0.005                     26.62%          31.10%          44.16%          44.15%          45.62%
1.00, 0.01                      34.38%          39.17%          50.63%          51.29%          50.72%
1.00, 0.05                      54.04%          58.76%          66.79%          67.85%          66.89%
1.00,  0.1                      63.15%          67.60%          73.93%          74.92%          74.38%
1.00, 0.25                      76.18%          79.95%          83.63%          84.39%          84.38%
1.05, 0.005                     32.67%          37.71%          50.26%          50.21%          51.85%
1.05, 0.01                      40.97%          46.10%          56.74%          57.40%          57.09%
1.05, 0.05                      60.44%          65.03%          72.04%          73.02%          72.28%
1.05,  0.1                      68.93%          73.12%          78.49%          79.37%          79.00%
1.05, 0.25                      80.38%          83.73%          86.78%          87.42%          87.41%
1.10, 0.005                     39.02%          44.50%          56.26%          56.20%          57.90%
1.10, 0.01                      47.60%          52.93%          62.61%          63.24%          63.05%
1.10, 0.05                      66.59%          70.95%          76.92%          77.76%          77.27%
1.10,  0.1                      74.24%          78.07%          82.54%          83.28%          83.00%
1.10, 0.25                      84.18%          87.10%          89.57%          90.06%          90.08%
1.50, 0.005                     81.17%          85.27%          88.90%          89.10%          89.89%
1.50, 0.01                      86.91%          89.87%          92.25%          92.56%          92.79%
1.50, 0.05                      94.77%          96.04%          96.96%          97.10%          97.07%
1.50,  0.1                      96.65%          97.50%          98.06%          98.14%          98.15%
1.50, 0.25                      98.36%          98.81%          99.04%          99.06%          99.09%

Thanks so much for your contribution. I've actually tried to code up an S3FIFO before and ended up failing miserably 😭 .
It's pretty awesome to see a RAG user around here 😄 .
I don't seem to catch the implementation of the ghost queue from the paper, or maybe the cache admission strategy? But I'm really surprised at how well it performed in the tests.
I think tinyufo from pingora could be a great reference for an admission strategy?

Regarding a more long-term integration with foyer. Could you briefly describe your workload, cache size, expected goals, etc?
I'm wondering if we'd be better off using a Btree for our disk storage since LSM trees have the write amplification issue?

Regarding a more long-term integration with foyer. Could you briefly describe your workload, cache size, expected goals, etc? I'm wondering if we'd be better off using a Btree for our disk storage since LSM trees have the write amplification issue?

Hi @xiaguan . Are you talking about disk cache? If it is, foyer doesn't use LSM trees as the disk cache. We can discuss on it in another issue. (Or maybe I should transfer this kind of issues into github discussions. foyer repo has already enabled it but is not used properly.)

I tryied to impl ghost queue based on your code.
But it seems not wokr well 🤔 .
LGTM

I tryied to impl ghost queue based on your code. But it seems not wokr well 🤔 . LGTM

Thanks @xiaguan . Can you send another PR with your changes? I'm interested in it. Let's find out why.

I tryied to impl ghost queue based on your code. But it seems not wokr well 🤔 . LGTM

Thanks @xiaguan . Can you send another PR with your changes? I'm interested in it. Let's find out why.

#306


LET THERE BE LIGHT!!!

Add light sources to the ceiling of the space station.


scrcpy 2.23 lag in video when phone screen is turned off

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment
feodra 38
scrcpy 2.23

installed from git hub through terminal
Pixel 6
Android version: 14

Describe the bug
simple scrcpy works as it always has for me watching a video 26-30 fps as long as my phone screen is on. when I turn the phone screen off fps drops to 15-17 . vidoe joggs badly. turn the screen back on perfect video again. have no clue why. if there is something you need from me please  post here. thanks for trying to get this android 14 mess fixed so quickly.
On errors, please provide the output of the console (and adb logcat if relevant).
Please paste terminal output in a code block.

Please do not post screenshots of your terminal, just post the content as text instead.

ok uninstalled scrcpy deleted the folder and sever and reinstalled works fine. sorry for the bother.


sudo labs:enable fails for user features when done in an app directory

If a sudo user runs labs:enable for a user:
heroku sudo labs:enable limited-features -u<EMAIL_ADDRESS>
But they happen to be running it from one of their apps, they get a cryptic error message:
Enabling limited-features for ... failed
!    You do not have access to the app foo.

This is actually caused by an API bug, but it's on a v2 endpoint which we're in the process of deprecating. I figure I'd make a note of it here.
https://github.com/heroku/api/issues/3619

:+1: for switching to the v3 endpoint

that's already been done


[JetNews] Add gif of JetNews working on large screens

Also fix some links on README

@riggaroo the recording was 2560px wide, but I felt that was too much for a gif.  I updated with a larger gif but still not full size.

This will increase the size of download of the whole repository though - I see its increased from 8mb to 41mb, I think it should be resized or referenced in a different way to not bloat the download of the whole repository.

If Github displays videos, that would be the best. Gifs are too large for the quality. The video is only 6MB.

I agree the gif is too large for this repository. Would a screenshot showing Jetnews on different sized devices work instead?

Also fix some links on README

Good point

Also fix some links on README

https://github.com/android/compose-samples/pull/789##discussion_r1326983955


Tapiosinn's tv-logos Github repository down

Describe the bug
Xteve is not able to find station logos from Tapiosinn's tv-logos Github repository.
Tapiosinn's tv-logos Github repository seems to be gone.
Server (please complete the following information):

OS Ubuntu Server 22.04
Arch amd64
xTeVe Version 2.5.3 (3)

Additional context
Maybe swap to Fourqui's fork of Tapiosinn's tv-logos.
Thx for your work so far!

Grab the latest release. It was fixed the day it broke.


Compatibility check and testing for Responsive Design (jsonConfig)

Notification from ioBroker Check and Service Bot
Dear Adapter developer,
ioBroker should be fully usable and operable on mobile devices
So please check your adapter jsonConfig for Responsive Design.
You can perform these tests in the developer console of your browser (F12)

For jsonConfig, all resolutions should be taken into account in the respective inputs.
The following resolutions are provided:

xl - width in 1/12 of screen on extra large screens (1536px < width)
lg - width in 1/12 of screen on large screens (1200px <= width < 1536px)
md - width in 1/12 of screen on middle screens (900px <= width < 1200px)
sm - width in 1/12 of screen on small screen (600px <= width < 900px)
xs - width in 1/12 of screen on tiny screens (width < 600px)

We recommend the following values for the standard layout
"xs": 12,
"sm": 12,
"md": 6,
"lg": 4,
"xl": 4

The following entry should be made below  "type": "tabs" in order to display a clearly legible table bar:
"tabsStyle": {
  width: "calc(100% - 100px)"
},

Please close the issue after you checked it.
Feel free to contact me (@iobroker-bot) if you have any questions.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@simatec for evidence
Note: If you added Responsive Design tests already, simply close this issue.

Fixed via https://github.com/copystring/ioBroker.roborock/commit/2934c4c29ff839830c68412fa699e39db0acd9ee

sorry your fix is not correct. please read the issue with the specific resolutions.

Ok. I misunderstood and will come back to this tomorrow.
One question: If this is the recommended way, why not make these the default values?
It doesn't seem to make much sense to me to "enforce" this change to every adapter when this can be made a default if nothing is set.

These are only target values. Each adapter config has different requirements for the layout of the menu items.
You do not necessarily have to adopt these values and are free to organise them as you wish.
In the end, it is important that good readability and usability is possible with any screen resolution.
It should also be possible to use all adapters on a smartphone (xs).

I have reverted my changes and went back to how it was before and recorded this video.

Isn't this responsive enough? I'm trying to understand why this change is needed.
I also tested the settings of this adapter on my phone and tablet. All look good to me.

It looks good... Thanks for the responsive review of your adapter.

Thank you. So no changes of my config are needed. If so, should I close this, since it worked fine from the beginning?

Not stale - only not yet processed

Unstale


Error configuring sqldelight-jps-plugin when trying to run gradlew

Just cloned the project, figured out I would run ./gradlew first. It fails with a weird error I've never seen before:
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':sqldelight-jps-plugin'.
> Failed to notify project evaluation listener.
   > Bad <init> method call from inside of a branch
     Exception Details:
       Location:
         org/jetbrains/intellij/dependency/PluginDependencyManager.<init>(Lorg/gradle/api/Project;Lorg/jetbrains/intellij/dependency/IdeaDependency;)V @105: invokespecial
       Reason:
         Error exists in the bytecode
       Bytecode:
         0000000: b800 204e 05bd 0004 5903 2d12 6232 2d12
         0000010: 6332 2d12 6432 2bb9 0067 0200 b900 6702
         0000020: 00b9 0067 0200 5359 042c 5359 10ff 1202
         0000030: b800 6b2a 5fab 0000 0000 005b 0000 0002
         0000040: adbc f91c 0000 001b f257 891a 0000 003a
         0000050: 5f5a 5903 32b8 002e c000 305f 5904 3212
         0000060: 34b8 003a c000 345f 57b7 006d a700 2e5f
         0000070: 5a59 0332 126f b800 3ac0 006f 5f59 0432
         0000080: 1234 b800 3ac0 0034 5f57 b700 71a7 000d
         0000090: bb00 7359 1275 b700 78bf 57b1
       Stackmap Table:
         full_frame(@80,{UninitializedThis,Object[#111],Object[#52],Object[#124]},{Object[#126],UninitializedThis})
         full_frame(@111,{UninitializedThis,Object[#111],Object[#52],Object[#124]},{Object[#126],UninitializedThis})
         full_frame(@144,{UninitializedThis,Object[#111],Object[#52],Object[#124]},{Object[#126],UninitializedThis})
         full_frame(@154,{Object[#2],Object[#111],Object[#52],Object[#124]},{Object[#126]})

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 0.92 secs

Google didn't turn out anything. I'm running OSX 10.11.6. Maybe the HD is broken or corrupted?

Uhhhhhhhhhhh @JakeWharton ever seen anything like this?

What version of Java are you running this with?

$ java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)

Can you try a newer version? The latest is 102 which is at least a 12 to 16
months newer than 11. I just want to rule out it being a problem with an
old JVM version.
On Sun, Aug 21, 2016, 4:14 PM Grzegorz Adam Hankiewicz <
<EMAIL_ADDRESS>wrote:

$ java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/square/sqldelight/issues/440#issuecomment-241279031,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEULgjbuPZIgFpERXCrovU5ITATcAks5qiLGKgaJpZM4Jo6A8
.

Will do next month when I'm near a fat internet pipe.

Yes, updating javac makes it work. Thanks.


Missing Reply URL

Missing Reply URL which is a required field
https://companyname.logicmonitor.com/santaba/saml/SSO/

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

ID: ccfaa610-6133-8bc0-54b9-bc8b9a756963
Version Independent ID: 3ed4027b-ce9a-e1c1-ae74-0bda37a1f9bc
Content: Tutorial: Azure Active Directory integration with LogicMonitor
Content Source: articles/active-directory/saas-apps/logicmonitor-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

Hello @bobert13581 ,
Thanks for bringing this to our notice, we will investigate and update the thread.

@chetansriv  and @v-hagamp can you please update this article for the Reply URL change?

Hello @bobert13581 ,
The reply URL section has been updated in Doc. Once again thanks for bringing this to our notice. Thanks.


Why are changes to iframe.html not coming through into the browser?

I am updating storybook/iframe.html to contain
:

but when I run Storybook start-storybook -s ./storybook/static/ -p 6006 and then view the source of the iframe, the
 is not there.
Please specify which version of Storybook and optionally any affected addons that you're running

@storybook/react 3.2.3
@storybook/addon-something 3.2.4

related to #3268
You shouldn't be modifying the iframe.html. If you require a modification to the code that renders inside the iframe, you should use the preview-head.html to inject it. Or have your story inject it.

Example script in preview-head.html to add your element to the root:


cloning repo means you can only ever use the button once

The way the button clones the repo implies that you can only ever use the button once. After the first use, it will fail.

This could be due to something related to CS.

It looks like when using a custom image the home dir is fresh each time.  At least it should be.  When using the default image the home dir is persistent.  I tried two deploys in quick succession and didn't have a git checkout issue.

That's been my experience as well. But it might be very well a Cloud Shell bug that occurs under certain circumstances and timing. If you can reliably repro, we should report it.


refactor session mediation; persist player location

Serious refactoring of the session mediation: it wasn't working, and it was nigh impossible to understand why due to a pile of spaghetti I am ashamed to take credit for.
I pulled more pieces out as injectable bits which should make them easier to test (writing tests will be the next activity):

ConnectionUtils is no longer static, which should make mocking connection activities much easier.
ConciergeClient and a new PlayerClient only encapsulate requests to the remote services. There are no knock-on effects to the callers.

Fixes #25


error: context deadline exceeded, make sure rpc service "add.rpc" is alread started

运行 go run bookstore.go -f etc/bookstore-api.yaml 错误
2021/03/24 12:00:59 rpc dial: discov://localhost:2379/add.rpc, error: context deadline exceeded, make sure rpc service "add.rpc" is alread started
exit status 1

rpc和etcd起了吗？


Linode power updates

Add delete to Linode action dropdown, closes #582
Linode power actions should have confirm, closes #1940, closes #1606

All but power on, which shouldn't need a confirm.

Allow you to launch lish no matter the power state, closes #1939
Rebuild triggers statusdropdown polling, closes #1986
Polls on mass events, closes #1740

Linter Error

src/linodes/components/StatusDropdown.js
50:5  warning  Unexpected console statement  no-console

Coverage decreased (-0.3%) to 79.917% when pulling da64dadc1ccda3af45fe380711757468ec84fbcf on eatonphil:linode-power-updates into ea48f7be6283d2edcdda88b5e7580d3feeaa4fe2 on linode:master.

Coverage decreased (-0.3%) to 79.9% when pulling 5cb6d35b20476b1c90ecce08c50965470cd09f66 on eatonphil:linode-power-updates into a5c98819e2ffabce4159fd81c59ec69557ca0c69 on linode:master.

reboot confirm doesn't trigger status animation?

Coverage decreased (-0.3%) to 79.9% when pulling 5babc289e51ca7795013c7730804d79d8455a065 on eatonphil:linode-power-updates into a5c98819e2ffabce4159fd81c59ec69557ca0c69 on linode:master.

I moved the progress logic out of the API coded and implemented a separate progress bar so you can still see what the Linode is doing while it's transitioning.

Coverage decreased (-0.7%) to 79.495% when pulling e70354f631955d91a1f0ee96acdc800c69f2a002 on eatonphil:linode-power-updates into a5c98819e2ffabce4159fd81c59ec69557ca0c69 on linode:master.

Fixes selected Linode background color too. We probably want a different color though...

Coverage decreased (-0.7%) to 79.495% when pulling 5a631ccf9841b00b4d4736e7227ac0f7ede5dc51 on eatonphil:linode-power-updates into a5c98819e2ffabce4159fd81c59ec69557ca0c69 on linode:master.

Coverage decreased (-0.7%) to 79.495% when pulling 12be204d22cbc9f5bdb563b77873a02147230a86 on eatonphil:linode-power-updates into a5c98819e2ffabce4159fd81c59ec69557ca0c69 on linode:master.

Coverage decreased (-0.7%) to 79.55% when pulling 12be204d22cbc9f5bdb563b77873a02147230a86 on eatonphil:linode-power-updates into a5c98819e2ffabce4159fd81c59ec69557ca0c69 on linode:master.

Coverage decreased (-0.8%) to 79.399% when pulling 8e904b49de8ccc20e1cb62ea8eefc340e6d592b2 on eatonphil:linode-power-updates into a5c98819e2ffabce4159fd81c59ec69557ca0c69 on linode:master.

Coverage decreased (-0.8%) to 79.399% when pulling 51926ed150aa2d7f3f153f9b09152e06e5af4f6b on eatonphil:linode-power-updates into 96b8bd32b07321b5e5c73724c9f9f32ecb306962 on linode:master.

Coverage decreased (-0.7%) to 79.52% when pulling 66c8dbaa36d5b4d6ef6395f7e1e1408a0454aad4 on eatonphil:linode-power-updates into fd81b0c1cd26eda480e2a42993693db5ec43830c on linode:master.

Coverage decreased (-0.7%) to 79.52% when pulling 52b14095c0bfb55ff1c96a7c05332ce2e94d0353 on eatonphil:linode-power-updates into 024c9ddf081fb14cfb88f57f19e445935565201e on linode:master.

Coverage decreased (-0.7%) to 79.581% when pulling c8e18ae0f93da32bcde9fd98319417b0942734e7 on eatonphil:linode-power-updates into 474c9f3c0147767791284dd5210245138da39807 on linode:master.

Changes Unknown when pulling e7e746be258e4a61eba817c864a4ae111b899735 on eatonphil:linode-power-updates into ** on linode:master**.

For later: one thing we may want to try and improve further is the rebuild status change, it goes from powering down > offline ( which is cool ), but then nothing else until the events notification comes up that it was rebuilt.

Coverage decreased (-0.7%) to 79.525% when pulling db115b1de0f022e351551855152749c93ea8d818 on eatonphil:linode-power-updates into 34e167cc8118143ff836a8117b7a8119b4a8b222 on linode:master.

Coverage decreased (-0.7%) to 79.581% when pulling 931cd84e75390110ceefdff39125725f4e67cf3f on eatonphil:linode-power-updates into 7143b761aa64099d738ad9248fa14e5864c6a8ab on linode:master.


Connot move to the last character of the line with $, even with softWrap disabled

I have disabled softWrap, but still cannot use $ or 0 to move to the first/last character of a line.

What versions of Atom and vim-mode are you using?

I'm using Atom 1.0.0 and vim-mode 0.54.0
In safe mode, vim-mode seems to be enabled in the Settings, but it doesn't work at all

My apologies, totally forgot that this was on vim-mode (so safe mode would disable vim-mode).
Can you then paste the output of apm list --installed?  Thanks.

Thank you for your help, here is the output :
/home/mahfoud/.atom/packages (3)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>On Thu, Jul 9, 2015 at 12:44 AM, Wliu<EMAIL_ADDRESS>wrote:

My apologies, totally forgot that this was on vim-mode (so safe mode would
disable vim-mode).
Can you then paste the output of apm list --installed? Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/atom/vim-mode/issues/746#issuecomment-119760553.

--
Mahfoud Sidi Ali Mebarek
+213 555 88 39 61

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


Policy: Spike

Feature #3
Description
As a dataspace participant I want to have my policies enforced to ensure that my assets are only used for the intended purpose.
This story is for spiking on the components needed to implement only a simple, static rule, that the caller identity has a claim "region=eu"
Acceptance Criteria

[x] Follow up issues are created to allow implementing the scenario (see story #64 )
[x] The follow up issues, when implemented, would have a scenario automatically tested such as: one provider, one consumer with region=eu and one consumer with region=us. An asset negotiation with one consumer fails, with the other it succeeds

Tasks

[x] Evaluate code provided by Ben: CatalogDataseedingExtension.java ,AbsSpatialPositionConstraintFunction.java https://github.com/bscholtes1A/edc-showcase/tree/edc-sandbox-1a/extensions/dataseeding/controlplane/src/main/java/org/eclipse/dataspaceconnector/dataseeding/connector
edc-showcase/extensions/dataseeding/controlplane/src/main/java/org/eclipse/dataspaceconnector/dataseeding/connector at edc-sandbox-1a
[x] Create follow-up stories to cover policies for #64

Created follow-up story #100


Captures.get(x) returns Option while Captures[x] returns &str

In core and std data structures, Index is generally used as a shorthand for .get().unwrap(). This decision in regex may have been done intentionally, but it seems to me that having .get() return a different type than Index violates the principle of least astonishment (I would expect Index to return a Match here).

It was done intentionally. The reason why is because caps[index] is very useful as a shorthand to reference the matched text. The indices themselves are rarely needed in my experience, in which case, it seems fine to expect to fall back to the get/name methods.


fix: Vertical tabs overflow without showing the users that more tabs are visible

🐛 Bug Report
An application with vertical tabs inside horizontal tabs has an overflow issue. This might appen if the vertical tabs are placed outside the horizontal tabs too, I have not tested that.
The problem is visible when the window size is made smaller, and the text for the given tab "overflows".
💻 Repro or Code Sample
When the page has enough width, all 4 tabs are visible

Window is smaller, two tabs are gone:

Code for these tabs:
<div style="min-height:600px">
<FluentTabs Orientation="Orientation.Vertical" >
        <FluentTab LabelClass="spaceRight10" Id="students-tab-1">
        <Header>
            Elever
        </Header>
        <Content>
            <EnterStudentsTab SaveReportEvent="@SaveReportEvent" ReportChangedEvent="@ReportChangedEvent" School="@School" LevelsAtSchool="@LevelsAtSchool"></EnterStudentsTab>
        </Content>
    </FluentTab>
        <FluentTab LabelClass="spaceRight10" Id="students-tab-2">
        <Header>
            Alenevedtak
        </Header>
        <Content>
            <StudentResolutionsTab SaveReportEvent="@SaveReportEvent" ReportChangedEvent="@ReportChangedEvent" School="@School" LevelsAtSchool="@LevelsAtSchool"></StudentResolutionsTab>
          </Content>
    </FluentTab>
        <FluentTab LabelClass="spaceRight10" Id="students-tab-3">
        <Header>
            Gruppevedtak
        </Header>
        <Content>
            <ResolutionGroupTab SaveReportEvent="@SaveReportEvent" ReportChangedEvent="@ReportChangedEvent" ReportingSchool="@School"></ResolutionGroupTab>
        </Content>
    </FluentTab>
        <FluentTab LabelClass="spaceRight10" Id="students-tab-4">
        <Header>
            Eksterne elever
        </Header>
        <Content>
            <FromOtherMuncipalitiesTab SaveReportEvent="@SaveReportEvent" ReportChangedEvent="@ReportChangedEvent" ReportingSchool="@School"></FromOtherMuncipalitiesTab>
        </Content>
    </FluentTab>
 </FluentTabs>

</div>

🤔 Expected Behavior
I believe there should be a notification showing the user that two tabs are missing. Equal the horizontal tab when the window becomes to narrow:

😯 Current Behavior
The vertical tabs just disappears without any notification or info to the user.
💁 Possible Solution
Im not sure what would be the best solution, but for vertical tabs like this, maybe just let the content overflow the table?
Or show the "more tabs button" (the little square with a number and +)
If non of these are possible, it's kind of hard to make sure users wouldn't miss content.
🌍 Your Environment
.Net 8
Fluent Blazor 4.9.3

Hi,
When trying a similar setup (vertical tabs inside of horizontal tabs) in one of the demo site examples, I get this:

We can't run the code you posted and from the screenshot I see, I'd say there is plenty of room to display the missing two tabs. I assume there is something in you CSS that is causing this. Don't think there is a lot we can do here.


feat(rewrite): support host rewrite

RT
Signed-off-by: storyicon<EMAIL_ADDRESS>

Codecov Report

Merging #159 (bed8a49) into main (432d73e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #159   +/-   ##
=======================================
  Coverage   36.33%   36.33%
=======================================
  Files          13       13
  Lines         944      944
=======================================
  Hits          343      343
  Misses        554      554
  Partials       47       47

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


Make new workspace button visible only in electron

Fixes #929
Changes proposed in this pull request:

new workspace button should now be visible only in electron

 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.

@lekterable Thanks for PR! It will be in next release. 🚀


Update to current Drake master.

We're about 5 months behind on Drake master. This PR fixes deprecation issues that have arisen since then. While it compiles, it's probably a good idea to regression test any current projects to ensure no changes. This essentially updates Drake from v0.24.0 to v0.29.0 (though we are tracking master, not these releases).
I recommend reviewing these release notes to preview any relevant changes--there are some items in there that may be useful (OSQP, trajectory optimization, and dynamics updates in particular).
https://drake.mit.edu/release_notes/release_notes.html

This change is

Through basic testing, I don't see any immediate issues in my branches. Will wait for Yu Ming to make sure it doesn't break his work. Unless some issue pops up, LGTM.

Please. Feel free to push here and merge once checks pass.


Resizing window breaks the terminal appearance

Environment
Windows build number: Microsoft Windows [Version 10.0.19042.746]
Windows Terminal version (if applicable): 1.5.10271.0 and 1.6.10272.0

Steps to reproduce

Start terminal
Run some commands
Resize terminal

Expected behavior
Terminal resizes appropriately
Actual behavior
Initial terminal window:

Make it bigger:

Make it smaller:

Might be related to #7405, but none of the mentioned workarounds fix this

I'm pretty sure this more closely matches the symptoms of #3088 than anything else.
/dup #3088


Problem with g2o

Describe the bug
I'm trying to compile ORB_SLAM2, which need the g2o package. I successfully installed g2o by using vcpkg without any problem. However when I tried to compile ORB_SLAM2 there is something wrong in linking:

Well, as linking should be automatically done, this is quite strange.
Is there any thing wrong with the package? or the link function of vcpkg? It will be great help if this can be solved.
Environment

OS: Windows
Compiler: VS2017

Hi @RollingIsland
Thanks for posting this issue.
I noticed that orb-slam2 used the internal g2o to build.
https://github.com/raulmur/ORB_SLAM2/blob/master/CMakeLists.txt#L73-L78
The source code for g2o is listed here.
https://github.com/raulmur/ORB_SLAM2/tree/master/Thirdparty/g2o
So if you want to use g2o  provided in vcpkg, you should add the usage to CMakeLists.txt and remove the g2o in thirdparty.
    find_package(g2o CONFIG REQUIRED)
    target_link_libraries(main PRIVATE g2o::core g2o::stuff g2o::types_icp g2o::types_sba)

Could you please update it and then try it again?

@NancyLi1013 , Thanks for your quick apply.
Actually I create a new empty VS project to compile orb_slam2. I installed all the required thirdparty packages by vcpkg, and the source files & the header files were added manually.
In case that the CMakeLists.txt cause any problem, I just delete it and try again, but seems no help.

Thanks for your reply. I will try to use g2o on my local machine and confirm if it can work well.

Hi @RollingIsland
Sorry for the late reply.
I create a simple CMake project and try to use g2o and it can build successfully on my local.
This is my CMakeLists.txt:
cmake_minimum_required (VERSION 3.8)
find_package(g2o CONFIG REQUIRED)
# Add source to this project's executable.
add_executable (CMakeG2o "CMakeG2o.cpp" "CMakeG2o.h")
target_link_libraries(CMakeG2o PRIVATE g2o::core g2o::stuff g2o::types_icp g2o::types_sba)

So it might be something wrong to g2o  in ORB_SLAM2.  It should be a problem in ORB_SLAM2 instead of g2o.

I'm closing this issue for now since it seems to be solved on my side.
Please try to do some changes for ORB_SLAM2  to rebuild it.