Creation of dataviewer fails if base python class names are reassigned as a variable after launching from github desktop

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Pre-amble:
Data viewer fails if you ever re-assign a default class as a variable. There is no warning to avoid doing so, either in "Black", "Pylint", or in the jupyter extension failure error.
This only happens when vs code is launched via github desktop by right clicking the repo name --> "open in VS Code".
The data viewer simply becomes empty if you do the following but open VS Code via anaconda navigator.
Any of these lines placed anywhere in a jupyter .ipynb file cause the data viewer creation error.
list = 1

dict = 3

tuple =3

Expected Result:
I expected to have a new "Data Viewer - var_name" appear as a new window.
Result:
I received the error pop-up, ""Failed to create the Data Viewer. Check the Jupyter tab of the Output window for more info.".
The entire output log of jupyter is pasted below when opening VS Code via github desktop and running on a script within that repo.
Minimally-Reproducible Example:

Launch vscode via Github Desktop / Anaconda Navigator (I don't think this matters)
Create a two-line .ipynb script

some_list = [1,2,3,4]
list = 2

Restart Jupyter kernel
Run script
Go to "JUPYTER: VARIABLES" window tab
Click the "show variable in data viewer" button
6a) If VS Code was opened via github desktop:

6b) If VS Code was opened via anaconda navigator:

VS Code Version
Version: 1.69.2 (user setup) Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a Date: 2022-07-18T16:12:52.460Z Electron: 18.3.5 Chromium: 100.0.4896.160 Node.js: 16.13.2 V8: <IP_ADDRESS>-electron.0 OS: Windows_NT x64 10.0.19043
Jupyter Extension Version
v2022.6.1201981810
Jupyter logs
info 14:28:37.558: Execute Cell 0 c:\Users\William.coulter\Documents\example_jupyter_dataviewer_fail.ipynb
info 14:28:37.623: Cell 0 executed with state Success
info 14:29:9.833: Executing silently Code (idle) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info
info 14:29:9.875: Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info with 1 output(s)
info 14:29:11.294: Loading webview. View is notset
info 14:29:11.295: Loading web view...
info 14:29:11.296: Webview panel created.
info 14:29:11.381: Process Execution: > ~\Anaconda3\python.exe -c "import pandas;print(pandas.__version__)"
> ~\Anaconda3\python.exe -c "import pandas;print(pandas.__version__)"
info 14:29:11.410: Executing silently Code (idle) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info
info 14:29:11.410: Executing silently Code (idle) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info
info 14:29:11.437: Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info with 1 output(s)
info 14:29:11.465: Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info with 1 output(s)
info 14:29:11.645: Web view react rendered
info 14:29:12.139: Executing silently Code (idle) = def _VSCODE_getDataFrame(what_to_get, is_debugging, *args):\nimport pandas as _VSCODE_pd\nimp
info 14:29:12.831: Executing silently Code (completed) = def _VSCODE_getDataFrame(what_to_get, is_debugging, *args):\nimport pandas as _VSCODE_pd\nimp with 0 output(s)
error 14:29:12.831: [Error: Failed to fetch variable info from the Jupyter server.
	at g.extractJupyterResultText (c:\Users\William.coulter\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:24:299215)
	at g.deserializeJupyterResult (c:\Users\William.coulter\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:24:299313)
	at getDataFrameInfo (c:\Users\William.coulter\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:24:296311)
	at async r.ensureInitialized (c:\Users\William.coulter\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:39:283280)
	at async r.getDataFrameInfo (c:\Users\William.coulter\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:39:282040)
	at async E.prepDataFrameInfo (c:\Users\William.coulter\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:39:267659)
	at async E.showData (c:\Users\William.coulter\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:39:265433)
	at async f.create (c:\Users\William.coulter\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:39:279718)]

Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
v2022.10.1
Anaconda Version (if applicable)
2.2.0
Running Jupyter locally or remotely?
Local

Thanks for the issue.
We might be able to detect this and put up a warning. I think this would more an error for a linter to detect though.

Thanks for the issue.
We might be able to detect this and put up a warning. I think this would more an error for a linter to detect though.

No problem! I'm migrating from Matlab to Python, so it's a struggle to get all of these pieces (linter, formatting, github repo, visual code studio, anaconda, python interpreter in vs code) all working, let alone understand them fully.
I just saw the error code appear and thought I should mention the headache I went through. I'm using Pylint (because that's most popular I guess), so should I post this issue there?

I just saw the error code appear and thought I should mention the headache I went through. I'm using Pylint (because that's most popular I guess), so should I post this issue there?

Yeah that would probably be a better place to capture this. This would mess up other things too (not just dataframe viewing) that would be more generic to all python code.

I think we should use the builtin alias _VSCODE_builtins instead of just using list, dict, etc. We ran into similar issues in the past and used an alias for referencing these builtins, i think we haven't completed that work, list and a few others are still pointing to the globally imported items, instead of the scoped alias _VSCODE_builtins.
Same applies to str, range & others.

Yeah that would probably be a better place to capture this. This would mess up other things too (not just dataframe viewing) that would be more generic to all python code.

Ok, I'll post it there. I was surprised to find there was no warning for overriding standard classes!
I don't know how it is causing a problem with vs code jupyter, but we could probably agree that "Failed to fetch variable info from the Jupyter server" is fairly misleading.". Maybe there could be some guidance on how to track down the issue. Maybe there are many paths leading to the error.
Anyway, I'll post on Pylint. I'm impressed with the fast responses!


Convert validation of heartbeats and speedtests to use a stream

This one is quite a doozy. If you have any questions be sure to ask, the mechanics of getting async working was pretty complicated so there's a lot of teachable stuff here.
One particularly proud moment was completely avoiding any use of "box".

just need unit tests and I think it is ready to go.


Fixes for Image_from_buffer_alignment_negative when alignments are 1

The Image_from_buffer_alignment_negative test creates images with incorrect pitches by adding 1 and tests whether the image creation fails.
Devices that return 1 for either of CL_IMAGE_REQUIREMENTS_ROW_PITCH_ALIGNMENT_EXT, CL_IMAGE_REQUIREMENTS_SLICE_PITCH_ALIGNMENT_EXT or CL_IMAGE_REQUIREMENTS_BASE_ADDRESS_ALIGNMENT_EXT will successfully create the image and therefore fail the test.
This change allows to skip the image creation in this case as the error condition (pitch % pitch_alignment != 0) will not be triggered for these devices.

Merging as discussed in the June 18th teleconference.


Solve test case not running issue

❯ npm run test

<EMAIL_ADDRESS>pretest /Users/fbricon/Dev/projects/vscode-commons
npm run test-compile && npm run lint

<EMAIL_ADDRESS>test-compile /Users/fbricon/Dev/projects/vscode-commons
tsc -p ./

<EMAIL_ADDRESS>lint /Users/fbricon/Dev/projects/vscode-commons
eslint src --ext ts

<EMAIL_ADDRESS>test /Users/fbricon/Dev/projects/vscode-commons
node ./out/test/runTest.js

Found .vscode-test/vscode-1.52.0. Skipping download.
Test error: Error: spawn /Users/fbricon/Dev/projects/vscode-commons/.vscode-test/vscode-1.52.0/Visual Studio Code.app/Contents/MacOS/Electron ENOENT
Exit code:   -2
Done
Failed to run tests
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test: node ./out/test/runTest.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

here's the log file:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/Users/fbricon/.nvm/versions/node/v12.19.0/bin/node',
1 verbose cli   '/Users/fbricon/.nvm/versions/node/v12.19.0/bin/npm',
1 verbose cli   'run',
1 verbose cli   'test'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'pretest', 'test', 'posttest' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
7 verbose lifecycle<EMAIL_ADDRESS>PATH: /Users/fbricon/.nvm/versions/node/v12.19.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/fbricon/Dev/projects/vscode-commons/node_modules/.bin:/usr/local/sbin:/Users/fbricon/.sdkman/candidates/mvnd/current/bin:/Users/fbricon/.sdkman/candidates/maven/current/bin:/Users/fbricon/.sdkman/candidates/jbang/current/bin:/Users/fbricon/.sdkman/candidates/java/current/bin:/Users/fbricon/.sdkman/candidates/groovy/current/bin:/Users/fbricon/.nvm/versions/node/v12.19.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/munki
8 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/fbricon/Dev/projects/vscode-commons
9 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'npm run test-compile && npm run lint' ]
10 silly lifecycle<EMAIL_ADDRESS>Returned: code: 0  signal: null
11 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>12 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
13 verbose lifecycle<EMAIL_ADDRESS>PATH: /Users/fbricon/.nvm/versions/node/v12.19.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/fbricon/Dev/projects/vscode-commons/node_modules/.bin:/usr/local/sbin:/Users/fbricon/.sdkman/candidates/mvnd/current/bin:/Users/fbricon/.sdkman/candidates/maven/current/bin:/Users/fbricon/.sdkman/candidates/jbang/current/bin:/Users/fbricon/.sdkman/candidates/java/current/bin:/Users/fbricon/.sdkman/candidates/groovy/current/bin:/Users/fbricon/.nvm/versions/node/v12.19.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/munki
14 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/fbricon/Dev/projects/vscode-commons
15 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node ./out/test/runTest.js' ]
16 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
17 info lifecycle<EMAIL_ADDRESS>Failed to exec test script
18 verbose stack Error<EMAIL_ADDRESS>test: `node ./out/test/runTest.js`
18 verbose stack Exit status 1
18 verbose stack     at EventEmitter.<anonymous> (/Users/fbricon/.nvm/versions/node/v12.19.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
18 verbose stack     at EventEmitter.emit (events.js:314:20)
18 verbose stack     at ChildProcess.<anonymous> (/Users/fbricon/.nvm/versions/node/v12.19.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
18 verbose stack     at ChildProcess.emit (events.js:314:20)
18 verbose stack     at maybeClose (internal/child_process.js:1021:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
19 verbose pkgid<EMAIL_ADDRESS>20 verbose cwd /Users/fbricon/Dev/projects/vscode-commons
21 verbose Darwin 19.6.0
22 verbose argv "/Users/fbricon/.nvm/versions/node/v12.19.0/bin/node" "/Users/fbricon/.nvm/versions/node/v12.19.0/bin/npm" "run" "test"
23 verbose node v12.19.0
24 verbose npm  v6.14.9
25 error code ELIFECYCLE
26 error errno 1
27 error<EMAIL_ADDRESS>test: `node ./out/test/runTest.js`
27 error Exit status 1
28 error Failed at the<EMAIL_ADDRESS>test script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 1, true ]


Add oEmbedUrl as changeable prop

This change makes it possible to use another service for retrieving the preview image.
I tested the code by adding this property to ReactPlayer in App.js:
oEmbedUrl='https://api.playerx.io/oembed'

Noembed doesn't seem to be maintained anymore and there is no purge cache support and the default cache is set to expire after 100 days.
I started a new oEmbed service with purge support over at https://github.com/playerxo/oembed
It's hosted on Cloudflare workers which offers a generous free tier and it's written in Javascript.
Feel free to use it or host your own with the pubic code.

Published in 2.10.0


Recontruct vs Function with array of parameters

There is a significant difference in the time it takes to perform inference using the reconstruct method below versus defining the function model i.e. the neural network using a function feedforward() as below. For a very simple and small problem like the IRIS dataset, the difference in efficiency when using the function method the inference happens in under one minute, and when using the reconstruct method then it takes 30 minutes. Any ideas why this happens and how to make the reconstruct method comparable?
@model function bayesnnMVG(x, y, μ_prior, σ_prior, reconstruct)
    θ ~ MvNormal(μ_prior, σ_prior)
    nn = reconstruct(θ)
    ŷ = nn(x)
    for i = 1:lastindex(y)
        y[i] ~ Categorical(ŷ[:, i])
    end
end

where parameters_initial, reconstruct = Flux.destructure(nn_initial)
As compared to the below
@model  function bayesnnMVG(x, y, μ_prior, σ_prior)
    θ ~ MvNormal(μ_prior, σ_prior)
    nn = feedforward(θ)

    ŷ = nn(x)
    for i = 1:lastindex(y)
        y[i] ~ Categorical(ŷ[:, i])
    end
end

where
function feedforward(θ::AbstractVector)
       W0 = reshape(θ[1:20], 5, 4)
      ...
       model = Chain(
           Dense(W0, b0, relu),
          ...
       return model
   end

More information would be helpful: Are you using Zygote as the backend?

More information would be helpful: Are you using Zygote as the backend?

Hi, Thanks for responding.
For MCMC, ReverseDiff.
for VI, ForwardDiff.
What do you think?

Can you try Zygote and see if the discrepancy is smaller? Flux tends to be optimized towards Zygote so..

Can you try Zygote and see if the discrepancy is smaller? Flux tends to be optimized towards Zygote so..

No, the Zygote has an issue with the for loop in the @model and if I try to use LazyArray then it Errors for Categorical.
MethodError: no method matching LazyArray(::Vector{Categorical{Float32, Vector{Float32}}})

I'd wager there's a type-instability introduced by Flux.destructure then, while in your manually implemented feedforward this is not the case.

When using restructure the Chain parameters are Float32 but the θ is Float64. I tried to explicitly define the Prior θ as Float32 Normal distributions, but it errored.
A snippet from @code_warntype for reconstruct is as follows, Although there are not red marked types in its output:
MethodInstance for (::Optimisers.Restructure{Chain{Tuple{Dense{typeof(relu), Matrix{Float32}, Vector{Float32}}, Dense{typeof(relu), Matrix{Float32}, Vector{Float32}}, Dense{typeof(identity), Matrix{Float32}, Vector{Float32}}, typeof(softmax)}}, NamedTuple{(:layers,), Tuple{Tuple{NamedTuple{(:weight, :bias, :σ), Tuple{Int64, Int64, Tuple{}}}, NamedTuple{(:weight, :bias, :σ), Tuple{Int64, Int64, Tuple{}}}, NamedTuple{(:weight, :bias, :σ), Tuple{Int64, Int64, Tuple{}}}, Tuple{}}}}})(::ReverseDiff.TrackedArray{Float64, Float64, 1, Vector{Float64}, Vector{Float64}})
Similarly using @code_warntype in the case of using a feedforward(θ) similarly has no red marked types but the Chain is Float64:
MethodInstance for feedforward(::ReverseDiff.TrackedArray{Float64, Float64, 1, Vector{Float64}, Vector{Float64}}) From worker 3:      from feedforward(θ::AbstractVector) in Main at /Users/456828/Projects/Bayesian-Active-Learning/DataSets/coalminequakes_dataset/Network.jl:8 From worker 3:    Arguments From worker 3:      #self#::Core.Const(feedforward) From worker 3:      θ::ReverseDiff.TrackedArray{Float64, Float64, 1, Vector{Float64}, Vector{Float64}} From worker 3:    Locals From worker 2:    │   %16 = Main.Dense(W0, b0, Main.relu)::Dense{typeof(relu), ReverseDiff.TrackedArray{Float64, Float64, 2, Matrix{Float64}, Matrix{Float64}}, Vector{ReverseDiff.TrackedReal{Float64, Float64, ReverseDiff.TrackedArray{Float64, Float64, 2, Matrix{Float64}, Matrix{Float64}}}}}

When using restructure the Chain parameters are Float32 but the θ is Float64.

The Float32 are a Flux-specific thing, they work mainly with Float32 and even started to enforce this more generally recently.


Fix iterable length warnings with inline children

RIP

Managed to do it once before, lets see if I can figure it out again lol


error : type arguments cannot be applied to non-parameterized class 'NSArray'

When I compile code that has NSArray<SomeClass *>, for example:
@property (nonatomic) NSArray<NSNumber *> *someNumbers;

I get the following error:
error : type arguments cannot be applied to non-parameterized class 'NSArray'

Are lightweight generics currently supported?

Should be available in the next release.

fixed with 390d14661261562eb34ecf11543f0b7be0757318, available in 4/29 preview.


test(ingestion): prefix class names to avoid unittest conflicts

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

What conflicts was this causing?

It was a naming conflict: pytest treats any classes of the form TestFoo or FooTest to be unittest test definitions, and was issuing warnings because these were testing utility classes and not tests. Renaming them avoids the warnings.


Support Split Display for Minutes

Split Displays
Split displays consist of two discs that rotate in unison to depict the desired value. In this case, two discs rotate to show the hour - one disc for 0-5 (tenth minutes) and a second disc 0-9 (single minutes).
See an example here.
Specs

The updates should live in the current Dials.js module

dials: {
  hands: {
    hour: [string]
  },
  split: {
    minute: {
      ones: [string],
      tenths: [string]
    }
  }
}

Functionality
The ones disc will rotate every minute while the tenths disc will rotate every ten.
Considerations

How will this affect manual time setting and how should this feature be supported
Split displays cannot be paired with any other display type

If a minute hand is passed into the split property, no other minute hand should exist in the settings

The display is currently in place and now manual time setting remains. The API has however changed from the proposed option above.
dials: [{
  hands: {
    hour: {
      ones: 'split-hours-ones',
      tenths: 'split-hours-tens'
    },
    minute: {
      ones: 'split-minutes-ones',
      tenths: 'split-minutes-tens'
    },
    second: 'split-second-hand',
  },
}],

Still need proper test cases written.


Supporting local output formats

Originally on 2010-11-04
When an updated version of Invenio is reinstalled over an already existing installation, any customization made to invenio-local.conf, any webstyle, any new websubmit function, any new bibformat element, any new format template are preserved.
Output formats, however, have their names hardcoded into Invenio codebase, and the administrator will usually customize them in place, instead of creating new files. Hence, when make install is performed, any customization is lost.
To support -local suffix ala invenio(-local).conf might be a nice feature to have, so that administrators can simply customize a default output format (say HD.bfo can be customized by the admin by creating a file called HD-local.bfo which would not be overwritten by make install)

Not applicable to 2.x branch. Re-open if needed for 1.x.


define the Type of the sdk object.

Im trying to get an inferred type of the whole imported "sdk" object
for example.
import workspaces from '@api/generated-sdk-of-some-kind'

const configureApiModule = (apiModule: any ) => {
  apiModule.server(url, { basePath: 'v1' })
  apiModule.auth(username, password)
}

modules.forEach(configureApiModule)

i want to be able to make the apiModule typed properly, but i can't seem to export or use any of the type SDKInstance = ReturnType<typeof createSDK>; or InstanceOf since the createSDK call is an IIFE.
I also dont want to edit codegen stuff ofc. Am i missing anything?

@kanadgupta Any ideas on how we can handle this? We can't export SDK from the generated index.ts files because that'd collide with the default export in CJS environments, and we can't do the same with an export type APISDK = typeof SDK in the same file for the same reason.

@erunion what if we defined the SDK class in a sdk.ts file and created an export in the package.json for that? And then the IIFE would remain in index.ts and import from sdk.ts?

@kanadgupta That'd work


Multiple endpoints executed

When we have multiple endpoints that can be matched with the request path all endpoints are executed, but I expected only first one to be executed.
I made an example to demonstrate my problem:
import * as express from "express";
import { Server, Path, GET, PathParam } from "typescript-rest";

@Path("/api")
class ApiController {
    @Path("/test")
    @GET
    f1(): string {
        console.log('path: /test');
        return 'path: /test';
    }
    @Path("/:name")
    @GET
    f2(@PathParam('name') name: string): string {
        console.log('path: /:name (' + name + ')');
        return 'path: /:name (' + name + ')';
    }
}

let app: express.Application = express();
Server.buildServices(app);

app.listen(8080, function () {
    console.log('Rest Server listening on port 8080!');
});

If I make a GET request 'http://localhost:8080/api/test' it will execute both f1 and f2 functions but will fail with following error:
Error: Can't set headers after they are sent.
because response headers are set in the first one.
Using pure javascript I don't have this problem:
const express = require('express');
const app = express();

const router = express.Router();
router.get('/test', function (req, res, next) {
    console.log('path: /test');
    res.json({ message: 'path: /test' });
});
router.get('/:name', function (req, res, next) {
    console.log('path: /:name');
    res.json({ message: 'path: /:name' });
});
app.use('/api', router);
app.listen(8080);
console.log('app started...');

because after matched endpoint next is not called.
Using typescript-rest I don't have this control and next is always called.
I traced a possible solution in server-container.ts line 328 (part of buildServiceMiddleware function) where I could replace
next();
with
if (!res.headersSent) next();
If this is intended by design could this be made optional by adding another decorator or adding options to path decorator that will indicate to only execute first matched endpoint?
I'm not satisfied with current solution to change paths so this does not happen.

Hi @darko1979 ,
Yes. it is a problem... But I am not sure what is the best solution to solve it. We need to call next to ensure that any middleware placed after the typescript-rest middlewares be called.
Take a look at #68

I think we need to add something to give more control to developer to specify if he wants that typescript-rest send a response to the client... I will think about how could be this contract...
And we are accepting suggestions

I have a suggestion: add option in Path decorator to control if next is called. Here are proposed changes:
feat: path decorator option to call next if headers are sent
In my solution this option to call next if headers are sent is enabled by default, and if somebody does not wan't this it can set this option to false, for example:
@Path("/api", false)
This can be applied to whole class or only a single method.
Or this option can be disabled by default so that default behavior is not to call next if headers are send and if somebody want's this functionality then it has to turn it on with this Path option.

Hello,
I landed here as we are experiencing this issue.
We have a few resources that has  the pattern   "ressource/:id  and "resource/someCommand" that are now broken.
The change linked to this issue looks more like a breaking change to me.
Besides, I don't see a good enough reason why you would add a middleware after builder services. I believe this makes the lib less predictable.
Adding an  option to choose the strategy (nextAfterResponse) globally would fix the issue for me.
Cheers

Just want to add that if you follow the recommended pattern of doing an app.use(...) as the last route to capture and format 404 routes you will get bitten by this as well. Every supposedly handled path will also trigger the 404 catch all.

Hi,
I've put together the different suggestions made here and I think we have a solution:
Next function
By default, we call the next function after endpoint execution (even if headers are already sent). As discussed previously, there are use cases that need this behaviour (logs, for example). If we need to disable this, we must be able to inform it explicitly.
So, the proposal is to have an annotation @IgnoreNextMiddlewares. Check here the documentation for the proposal.
@Path('test')
class TestService {
   @GET
   @IgnoreNextMiddlewares
   test() {
       //...
      return 'OK';
   }
}

Remember that we already have a way to explicitly call next if we need to do it according with a specific condition inside our service handler. We can use Context.next
Service Return
By default, we serialize the service result to the user as a response. If the method does not return nothing (void), we send an empty response with a 204 status. It is useful to simplify all the situations where we don't have nothing to send as response.
But, if you need to handle the user response by yourself, you should be able to explicitly inform this. The proposal here is to have a specific return value to inform that you don't want to return nothing.
The Return.NoResponse (check the proposal here) should be used to this:
import {Return} from "typescript-rest";

@Path("noresponse")
class TestNoResponse {
  @GET
  public test() {
    return Return.NoResponse;
  }
}
app.use("/noresponse", (req, res, next) => {
  res.send("I am handling the response here, in other middleware");
});

or
import {Return} from "typescript-rest";

@Path("noresponse")
class TestNoResponse {
  @GET
  public test(@ContextResponse res: express.Response) {
    res.send("I am handling the response here, don't do it automatically");
    return Return.NoResponse;
  }
}

I think that these proposal:

keeps compatibility with previous versions
Keeps the usage simple for the most used cases
And allow customisations to handle all those cases reported here

Re: Next Function, I still believe the logging use case has better ways of handling than altering the expected workflow for Express users (such as response event handling which is an already existing solution). Or at least switching the default so most users don't have to annotate IgnoreNextMiddlewares on every service.
W.r.t. backwards compatibility, since #68 was itself a breaking change, I see this more as a bugfix than a backwards compatibility issue.

Hi @greghart ,

I still believe the logging use case has better ways of handling than altering the expected workflow for Express users

I did not disagree about the logging use case. But the question is what is the expected workflow for Express users?
I believe that if somebody add a middleware, after the Typescript-rest handler, directly in the express router, that person expects that it will be called after a service call.
let app: express.Application = express();
Server.buildServices(app);

app.use("/mypath", (req, res, next) => {
  // If I add something here, with a middleware in express directly, I expect that it must be called.
});

That is why we handled #68  as a bug and not a change.
But we can put a configuration property in the Serverto allow switch the default, avoiding  IgnoreNextMiddlewares in more than one service, if you need to disable it more than once.
something like:
Server.IgnoreNextMiddlewares(true);

I think your example highlights the mis-communication, as I think conventional Express users (and the other people in this thread) would expect that next middleware not to happen if Server.buildServices(app) is going to end the response by calling res.send.
This is based on documentation and examples of Express, and common usage. It's not prohibited to call next after send, but it's certainly not the expected norm.

Hi,

I think your example highlights the mis-communication, as I think conventional Express users (and the other people in this thread) would expect that next middleware not to happen if Server.buildServices(app) is going to end the response by calling res.send.

Maybe... but the point is that expressjs users have the chance to choose when and how to call the methods next and response.send, so I don't think we can reduce the problem to "Don't call next after a service method".
We need to add support to give more control to users of typescript-rest. The changes proposed here allow all possible uses cases.
And with the top level switch (Server.ignoreNextMiddlewares(true);) it is possible to keep the previous behaviour.
But thanks a lot for all contributions on this topic


Images are not appearing in a slider or carousel format. I am dynamically displaying these images with axios.

I followed all the examples, I had no luck. The preview of what is displayed is shown below.

Here is my code for my slider.
<template>
    <div>
        <splide :slides="slides">
                <splide-slide v-for="slide in slides" :key="slide.urlToImage">
                    <img :src="slide.urlToImage">
                </splide-slide>
            </splide>
    </div>
</template>

<script>
import axios from 'axios'
import { Splide, SplideSlide } from '@splidejs/vue-splide'

export default {
    components: {
        Splide,
        SplideSlide
    },

    data(){
        return {
            slides: null,
        }
    },
    methods: {
        getArticles: function(){
            axios.get('https://newsapi.org/v2/top-headlines?country=us&apiKey=2b6ef6ad2d01456fa3b7389970ab9f6a')
            .then(response => {
                this.slides = response.data.articles
            })
        }
    },
    mounted() {
      this.getArticles()
    },

    updated(){

    }
}
</script>

Hi @acebelowzero
It looks like you haven't loaded the plugin styles. Try this
import<EMAIL_ADDRESS>

@k-ivan Thank you for your support.
Yes, it seems that CSS is not applied.


merge from template-arlac77-github

package.json

chore(deps): add ^22.0.1 remove ^22.0.0 (devDependencies.semantic-release)

:tada: This PR is included in version 1.0.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add toggleVisibility() method to QS interface

I'm closing this one since I just realised it's a duplicate of the earlier #4

Dang! Since this seems to be a feature everybody wants I will finally merge it :)


Adding a scroll bar in Q chat

Description
While the scrolling functionality exists in Q chat panel, can we also add a visual component aka scroll bar to indicate the position in the chat panel?

This one should be trivial
this is why there is no scroll bar
    ::-webkit-scrollbar {
        width: 2px;
        height: 2px;
        opacity: 0.25;
        &:horizontal {
            width: 0px;
            height: 0px;
        }
    }


Goliath support

I'm wondering whether you've considered adding support for the Goliath web server?

I am not really sure how the Goliath support/integration would work. If someone has a patch, we can re-open this.

Fair enough. I know far too little about either to suggest it's something that even should be done. It was simply a question of feasibility, and not knowing what's possible.


FormBuilderDateTimePicker not Detecting 6.0.0-nullsafety.1

FormBuilderDateTimePicker in full page command

Yup, same issue.
Looks like the new maintainer removed fields that require dependencies in 6.0.0-nullsafety.0 - as per https://github.com/danvick/flutter_form_builder/blob/null_safety/CHANGELOG.md
But this looks like it also includes FormBuilderDateTimePicker as it depends on:

datetime_picker_formfield
flutter_datetime_picker  - Looks abandoned and doesn't support null-safety

But wasn't mentioned in the CHANGELOG.md.
null_safety branch has the FormBuilderDateTimePicker file commented out.
I personally use the FormBuilderDateTimePicker in a few projects - so I'd be happy to do a PR to bring it up to null safety if the maintainer is still wanting FormBuilderDateTimePicker in the package

Fixed with latest release ef2892d9d70423677484d64579f195b2ccbdb28c

Thank You
On Sat, Apr 24, 2021 at 5:29 AM Jackson Lee @.***>
wrote:

Fixed with latest release ef2892d
https://github.com/danvick/flutter_form_builder/commit/ef2892d9d70423677484d64579f195b2ccbdb28c
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danvick/flutter_form_builder/issues/771#issuecomment-825997781,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHYADCASEXSSHTKUNCLP4B3TKICUNANCNFSM42WIHYLA
.

--
K.ARJUNAN
Software Engineer,
8760874037

Solved


Added sparsity functionality, with tests

@piiswrong Is there any further issue here or is this good to merge? It seems all concerns were addressed. The CI is failing for dumb file length reasons so this should be fine to merge

@piiswrong The feature has been added to the examples folder


Docker-compose up =>  [ERROR] Could not open file '/var/log/mysql/error.log' for error logging: No such file or directory

Tried to re-install Ubuntu 18.04, used most recent Docker using OnlyOffice links & documentation.
Old version of OnlyOffice (8 months old ?) was working fine.
onlyoffice-mysql-server        | 2022-08-04 22:16:10+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.39-1.el7 started. onlyoffice-mysql-server        | 2022-08-04 22:16:10+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' onlyoffice-mysql-server        | 2022-08-04 22:16:10+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.39-1.el7 started. onlyoffice-mysql-server        | 2022-08-04 22:16:10+00:00 [Note] [Entrypoint]: Initializing database files onlyoffice-mysql-server        | 2022-08-04T22:16:10.757172Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). onlyoffice-mysql-server        | 2022-08-04T22:16:10.757234Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set. onlyoffice-mysql-server        | 2022-08-04T22:16:10.759400Z 0 [ERROR] Could not open file '/var/log/mysql/error.log' for error logging: No such file or directory onlyoffice-mysql-server        | 2022-08-04T22:16:10.759436Z 0 [ERROR] Aborting

Hello @molekm this is duplicate of https://github.com/ONLYOFFICE/Docker-CommunityServer/issues/161


required_with and required_if rules cannot handle 0 value

Sample code :
method: 'numeric', description: 'required_with:method|required_if:method,0'
Validations are not triggered when method value is 0.

@regalskr2006  Please were you able to resolve this?

@smithaitufe I am reviewing issues as I prepare v4
Would you please provide some sample code which demonstrates this issue not working

Not exactly the same issue, but it goes to show that the required_with function does not work as expected. Sample code:
const valueMap = {
  "function": null,
  "first_name": null,
  "last_name": null,
  "country": null,
  "email": null,
  "telephone": "123456",
  "mobile": null
}

const validation = {
  "country": [
    "required_with:telephone,mobile"
  ]
}

const validator = new Validator(valueMap, validation);
const passesValidation = validator.passes(); // returns true

I'm expecting the validator not to pass ('country' is a required field when either of 'telephone' or 'mobile' is filled), but it passes anyway...
I'm on 3.17.1

@mikeerickson
Not exactly the same issue, but it goes to show that the required_with function does not work as expected. Sample code:
const valueMap = {
  "function": null,
  "first_name": null,
  "last_name": null,
  "country": null,
  "email": null,
  "telephone": "123456",
  "mobile": null
}

const validation = {
  "country": [
    "required_with:telephone,mobile"
  ]
}

const validator = new Validator(valueMap, validation);
const passesValidation = validator.passes(); // returns true

I'm expecting the validator not to pass ('country' is a required field when either of 'telephone' or 'mobile' is filled), but it passes anyway...
I'm on 3.17.1

Hi.
The issue comes from the fact that required_if rule takes it's parameter as string, so what it's doing is:  0 === '0'.
As a workaround, I used the registerImplicit method provided by Validator class:
const required_if_rule = function (val, req, attribute) {
        req = this.getParameters();
        let op = this.validator._objectPath(this.validator.input, req[0]);
        if ((op != undefined && op != null ? op.toString() : null) === req[1]) { // === (typeof op !== "boolean" ? req[1] : req[1] == 'true')) {
            return this.validator.getRule('required').validate(val);
        }
        return true;
    }

Validator.registerImplicit('required_if', required_if_rule, 'The :attribute field is required when :other is :value');

I can see the point here.  Let me stew on this for a bit.  My initial thinking is, if the value is required, but an empty string is supplied, theoretically that should fail validation.
Now, on the bad side, if I make this change, then I risk breaking other applications which don’t adopt this strictness


Create Event Feature: Views Testing

All testing scenarios were tested in create_event.py (form testing) - now tested via view layer.
fix: #70

When you are using pytest variables like the variables in pytest configure the variables are saved in pytest memory until the end of the tests, so in your case there is another conftest file in the reminders app that redefine date_time_start. I have change it to event_date_time start/end to distinguish between them.


docs: full documentation write up

This is for the code that is up to this point. Any new code will be built while programing.
Closing #12

:tada: This PR is included in version 1.0.0-beta.2 :tada:
The release is available on:

GitHub release
npm package (@develop dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


tf.negative

Hey @mortendahl,
This PR implements the tf.negative operation (tf.negative([-1, 0, 1]) == [1, 0, -1]). I named it neg so it doesn't get mixed with the negative operation in the securenn protocol (negative([-1, 0, 1]) == [1, 0, 0]).
This operation appeared in one of the convolution network when I turned off in the batchnorm layer the parameters scale and offset.
Thanks!

hi @yanndupis, good work! I suggest we rename the existing method in SecureNN, maybe to is_negative, in order to stick with the TF API; anything else will only cause more confusions down the line.

Hey @mortendahl ,
Thank you very much for your review.
I have realized that negative was already implemented on the backing tensor.
What do you think is better in int100.py:
def negative(self):
            # TODO[Morten] there's probably a more efficient way
            return FACTORY.zero() - self

or
def neg(self):
            backing = [tf.math.negative(xi) for xi in self.backing]
            return DenseTensor(backing)

and in native.py:
def negative(self):
            value = tf.negative(self.value)
            if EXPLICIT_MODULUS is not None:
                value %= EXPLICIT_MODULUS
            return DenseTensor(value)

or
def neg(self):
            return DenseTensor(tf.negative(self.value))

Thank you!

Hi @yanndupis, my suggestion:

For int100:

def neg(self):
    backing = [tf.negative(xi) % mi for xi, mi in zip(self.backing, MODULI)]
    return DenseTensor(backing)

For native:

def negative(self):
    value = tf.negative(self.value)
    if EXPLICIT_MODULUS is not None:
        value %= EXPLICIT_MODULUS
    return DenseTensor(value)

Hey @mortendahl , thanks for your review! Your comments should be addressed with this pr. thanks.


My little Hackpad - Reupload from #145

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.
If you're unsure about the format, make sure to check out the Orpheuspad example and follow the format there.
If this PR isn't a submission, that's okay too! If there's anything about this PR template that seems confusing, let me know in #hackpad on the slack!

@M0HID Here is my Reupload of my PR

This should be it @M0HID

@M0HID I would soder the parts by myself. What should I change?

@qcoral Is the ESP8266 allowed? Can I pls use it.

LGTM
https://forms.hackclub.com/hackpad


Slack  improve integration

Danny did all of this, I was just committing and opening this pull for him.

Sure, we can merge into master too... but ifixit-production it branch we use in production.

Lol woops, switched

CR 👍

CR :+1:


Refactor BlockImportParams to be non_exhaustive

This marks BlockImportParams as non_exhaustive. From time to time we add new field into the struct. By making sure users use initialization function we avoid too much breakage.

Not sure that is the correct way we should go. I think the problem is that the struct already takes too much parameters. I think we should come up with a better solution, instead of adding more and more parameters.

@bkchr Any suggestions?
My opinion is that because we have this block import chain, where we must have parameters passed down from the top-level verifier to bottom-level importer, this is unavoidable. Even if we split it down to multiple structs, we'd still in the end have to combine those small structs together back to a big one, because it has to be passed down.

Yeah, I'm not sure. Maybe the best to do this now with non exhaustive in regards of releasing Substrate. However, I still don't like it.

Yeah maybe let's use non-exhaustive first and think about better ways in the mean time!


Error Message in Connected Factory:  Error while connecting to the OPC UA server

I am trying to connect a OPCUA server to Azure using Connected Factory, following this guide.
However I'm facing the same issue of #58: everything works until section Enable your gateway, when I get the error Error while connecting to the OPC UA server:
.
As suggested in #58 I added entries to /etc/hosts file:
<IP_ADDRESS>	     publisher.matt14.io  # for gateway
<IP_ADDRESS>    opcuasrv.maci14.io # for opcua server
Then I start publisher and proxy with:

for publisher sudo docker run --rm -it -v /SharedFolder:/docker -v x509certstores:/root/.dotnet/corefx/cryptography/x509stores --network iot_edge --name publisher -h publisher -p 62222:62222 --add-host opcuasrv.maci14.io:<IP_ADDRESS> microsoft/iot-edge-opc-publisher:2.1.3 publisher "<iothubconnectionstring>" --lf /docker/publisher.log.txt --as true --si 1 --ms 0 --tm true --vc true --di 30
for proxy sudo docker run -it --rm -v /SharedFolder:/mapped --network iot_edge --name proxy --add-host opcuasrv.maci14.io:<IP_ADDRESS> microsoft/iot-edge-opc-proxy:1.0.2 -i -c "<iothubconnectionstring>" -D /mapped/cs.db and
sudo docker run -it --rm -v /SharedFolder:/mapped --network iot_edge --name proxy --add-host opcuasrv.maci14.io:<IP_ADDRESS> microsoft/iot-edge-opc-proxy:1.0.2 -D /mapped/cs.db

Publisher and proxy seems to work without errors, but in /SharedFolder/CertificateStores there is no rejected certificates to move, so It seems that the Client in the web dashboard is not able to communicate with the publisher on my PC.
I tried also to connect with  opc.tcp://publisher.matt14.io:62222 as suggested in the previous issue, but the error remains (same error also trying to connect to the server opcuasrv.maci14.io).
Any suggestions?
Thank you!

Did you find a way to solve this?
I am having the exact same issue...

@shacotaco How about opc.tcp://publisher.matt14.io:62222

@matteo-bon Did you check whether your service(opc.tcp://publisher.matt14.io:62222) is fine in the UaEpert tool.

A couple of things:

Please use the latest Connected Factory. I have added a few fixes in this area in August release and August patches
Use iot-edge-opc-proxy:1.0.4 (the documentation is updated meanwhile)
Watch the log output of the proxy
When you press the connect button, you should see a proxy log output which try to resolve the hostname in the URL you entered. In your case "publisher".
Then you should see more package exchanges and a context panel showing in the browser, which tells you that the certificate is not trusted. You trust it and then it continues. The sense of this action is that the WebApp puts the certificate of the publisher (which is a selfsigned one) into its trusted cert store.
After this you can try connect to your target OPC UA server. The same procedure will happen with that one.
Now you should be able to browse your target OPC UA server and also be able to publish node values via right click context menu.


Read custom JAX-RS http verbs that are annotated with HTTPMethod.

Fix for issue: #187.
Modified JaxrsReader.extractOperatoinMethod( ... ) to check for annotations, annotated with javax.ws.rs.HttpMethod.
Unfortunately, I couldn't find a utility that would simplify the search. Ended up looping through the annotations.

Thanks, @sudohippie - merging now


No public partial functions

I think they're all gone but check anyway

Yep. (I'm not counting FingerTree.)


updating branch to add in repbulk

Hello @sgosline! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file protData/getAllDatasets.py:

Line 7:80: E501 line too long (80 > 79 characters)


[runtime][NFC] Unify reportOnCrash implementations into a single function

Title says it all -- this makes it easier to add new functionality to this routine without having to duplicate the code.

@swift-ci smoke test

@swift-ci smoke test

I'm behind the times, but LGTM.


Question - command to update ?

HI, is there any command to update instead of update manually by downloading?

git pull

#2780

SRY, tnx for answers
closed


New Install - Testing failures

Fresh Enso install - following the documentation. Using Vagrant Homestead, latest Box 6.0.0
Trying to run tests and get many failures/errors.

It seems that the dataTableIndex() test from the TestDataTable trait is the biggest offender - getting:
Expected status code 200 but received 500
I've tried to duplicate many of the tests to troubleshoot - but little success. Any insight would be appreciated.

They are tagged now


Android support.

Working:

set aspect,
select camera type,
set flash/torch mode,
take picture and save it to the file system, mediaroll or as data.

Not working:

video capture,
set orientation.

Known problems:

front camera pictures are not oriented correctly.

Tested on:

Nexus 5 (Android 6.0.1, Marshmallow)
Genymotion emulator (Android 6.0.1, Marshmallow)

So exciting! I'm going to test this out tomorrow. Thanks for all the work!

:clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap: :clap:

Amazing work!

👏

Can we get some instructions on the readme? Or am I missing something
On Sat, Jan 23, 2016 at 16:40 mattiamanzati<EMAIL_ADDRESS>wrote:

👏
—
Reply to this email directly or view it on GitHub
https://github.com/lwansbrough/react-native-camera/pull/157#issuecomment-174224683
.

on it.

Thanks!
On Sat, Jan 23, 2016 at 17:20 Fabrice<EMAIL_ADDRESS>wrote:

on it.
—
Reply to this email directly or view it on GitHub
https://github.com/lwansbrough/react-native-camera/pull/157#issuecomment-174226818
.

https://github.com/lwansbrough/react-native-camera/pull/161

Just wanted to extend my gratitude again to @farmisen and everyone who has been involved with the Android development thus far. Really great work. There's still a ways to go to feature parity but we're on our way now, so thank you.
I'm going to have to set aside some time to do feature testing as it's been a while since there's been a new version on npm - but that issue is on my radar.
Cheers guys!

Would love some confirmation on which version of react-native the instructions support. It seems like they support 0.17, but not 0.18?

@dangnelson Curious what makes you say that?

MainActivity.java seems to work differently in 0.18 than 0.17
There's no reference to ReactInstanceManager.builder() in that file.
https://github.com/facebook/react-native/blob/master/local-cli/generator-android/templates/package/MainActivity.java

More specifically, I think a lot of it got moved to ReactActivity.java:
https://github.com/facebook/react-native/commit/935cbb76c02cffd378a8f391c6e7443a3da13adc

@ardowz and I have been trying to resolve the issue here https://github.com/lwansbrough/react-native-camera/issues/165


Check indexing arg types

Please describe your wishes and possible alternatives to achieve the desired result.
Working on https://github.com/scverse/anndata/issues/1224, we discovered that np.where is called internally by scipy on boolean masks, but there are places in our code where we also call it, likely unnecessarily.  It would be good to review these places to see if they are still necessary and then see if there is an effect on performance.

My main concern here is whether doing adata[adata.obs[...] == ...].X will hit the optimized path for indexing if X is backed (since we only optimized for mask indexing, and not positional)

It does not, which kind of defeats the optimization. This now needs doing.

slight aside: np.where is designed for np.where(cond, vals_if_true, vals_if_false), using it as replacement for np.flatnonzero is awkward.

@ilan-gold what’s missing here?

Closing this as it is no longer needed.  I've gone through the remaining instances and haven't found any that affect the performance optimizations.


Add Credit Card Emoji 💳 to the "Credit Card Payments" category group

This is a second pull request for this feature. The first PR was #1013. This PR was rejected because YNAB changed the credit card payment category to be stickied at the top and added a few other UI tweaks, which I didn't have at the time. It seems YNAB has rolled this UI change back, and this PR feature is possible once again!

Users are unable to edit the name of the "Credit Card Payments" category group in YNAB. I have enjoyed adding emojis to all of my category names and this was the only category group missing an emoji. I built this little feature that adds the emoji for your through the toolkit!
A couple notes:

It took me less than an hour to build the app and get my feature working. The core team has built an awesome framework, great job!
This only works on the name of the category group in the budget list, and not in the modal that pops up when you click it (as if you were going to edit it). I played with using .modal-budget-edit-category-label.user-data to also make the change in the modal, but that also affected each credit card (since those titles are not editable as a budget).
e.g.:

Recommended Release Notes:

Added toggle for showing a credit card emoji on the "Credit Card Payments" category group.

@joshmadewell - I'm a backend guy usually, so I consider under an hour as a win 🙂

I added a few doc changes as well to make things more consistent/fix links 👍
The src/README.md file and the docs/building-features.md feel a little redundant.

Yeah, there's still this weirdness in the repo where we have legacy features not built on an ES6 framework so the documentation is a bit wild.

The feature isn't rolled back for all users so you should add code to check that the user has it. Something like this
if (YNABFEATURES.get('categories-new-style') === undefined | YNABFEATURES.get('categories-new-style') === true) { Once the feature has been rolled out to all users the get()` call will be undefined.

Well, based on the latest Web Release Notes as of today, 3/1 everyone is now getting the new handling of credit cards.

@dbaldon the new credit card category just got a mention in their release notes, does that mean it's going out to everyone? https://www.youneedabudget.com/release-notes/web-release-notes-march-1-2018/
otherewise, I can look into adding that later tonight

Currently all merges are performed by @blargity.
What version of YNAB do you have? I have v1.20327 and the `YNABFEATURES.get('categories-new-style') still exists. I wish they'd give the version number in the release notes but they don't. You have to open the dev tools to see it.


Transpose of 3x3 Matrix Calculator

Description 📜
Transpose of 3X3 Matrix Calculator #111
Transpose of a matrix is found by interchanging the rows and columns of a matrix. This calculator calculates the transpose of 3X3 matrix. I have added the code of Transpose of 3X3 Matrix Calculator. It is built with- HTML,CSS and JavaScript.
I have added the README.md of Transpose of 3X3 Matrix Calculator.
Fixes #111

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] My changes generates no new warnings.
[x] I'm GSSOC'22 contributor

Screenshots / Gif (Optional) 📸

@Chayan-11 Should I add more description about the features of Calculator in Readme file?

@Chayan-11 Should I add more description about the features of Calculator in Readme file?

yes, that's what I asked for

@Chayan-11 Okay, Will do the necessary changes!

@Chayan-11 I have updated the Readme file.


Restore gltf node animation export.

Bug. Exporting node animations to gltf doesn't work.
Here's a godot master tscn where export as gltf and then reimporting loses the node animations. I have also included the resulting glb.
mocap.zip

mocap_00000.zip
Oops that was the wrong version. This is the proper 4.0 tscn.

mocap_00000.zip
Oops that was the wrong version. This is the proper 4.0 tscn.

Does the issue affect 3.2 too?

Does the issue affect 3.2 too?

Thanks!

Thanks!

Gltf2 export is not in 3.2. I have a version, but due to the policy of 4 first, I haven't spent effort on it.

Gltf2 export is not in 3.2. I have a version, but due to the policy of 4 first, I haven't spent effort on it.


Not able to disable/delete a ManagedClusterAddon

When a user install the cluster-proxy, managed-serviceaccount and cluster-gateway addons. The managed cluster addon resources are automatically created on the registered clusters. If the addons are deployed to cluster foo and bar. Is it possible to disable or delete the addons for cluster bar? Currently, when deleting those managed cluster addon on cluster bar namespace, they will come back.
$ kubectl get managedclusteraddon -n $NSC1
NAME                     AVAILABLE   DEGRADED   PROGRESSING
cluster-gateway          True
cluster-proxy            True
managed-serviceaccount   True
$ kubectl -n $NSC1 delete managedclusteraddon cluster-gateway
managedclusteraddon.addon.open-cluster-management.io "cluster-gateway" deleted

$ kubectl get managedclusteraddon -n $NSC1
NAME                     AVAILABLE   DEGRADED   PROGRESSING
cluster-gateway          True
cluster-proxy            True
managed-serviceaccount   True

Discovered by @yitiangf
CC @qiujian16

this is controlled by each addon controller separately. If it uses installAll strategy, the addon controller of the certain addon will alway enable it.

ah, another clean up issue...FYI @zhiweiyin318. We have a fix in addon-framework that if a cluster is deleting, addon should not be created again.

I think we can add an annotation filter functionality to the addon-framework to filter managedclusters when using install strategy. If a managed cluster has annotation addon.open-cluster-management.io/disable-automatic-installation: "true", the install strategy will ignore it when deploying addons.

The PR adding annotation addon.open-cluster-management.io/disable-automatic-installation: "true" to disable the addon auto installation has been merged.
BTW, The installAll strategy has been deprecated, instead, there is a new feature introduced from v0.11.0, Enable the add-on by install strategy which can enable addons based on selected clusters.

/close


Make sure SettingsManager::all is predictable

This fixes #16

I fixed the merge conflict. It was only the Readme that couldn't be merged automatically.

:+1:

Thank you for merging.


WoT -> SDF: Add first mapping of WoT to SDF

Codecov Report

Merging #18 (0469e00) into main (2b06afe) will decrease coverage by 3.50%.
The diff coverage is 89.61%.

@@             Coverage Diff             @@
##              main      #18      +/-   ##
===========================================
- Coverage   100.00%   96.49%   -3.51%
===========================================
  Files            7        7
  Lines          360      542     +182
===========================================
+ Hits           360      523     +163
- Misses           0       19      +19

Impacted Files
Coverage Δ

sdf_wot_converter/wot_to_sdf.py
89.78% <89.61%> (-10.22%)
:arrow_down:

Continue to review full report at Codecov.

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


[BUG] CPU / RAM

hi i’m having a very serious problem since last night, in practice I open the openbullet exe file and without starting the job or anything the cpu and ram go up by themselves
without having started job or anything just by opening the exe file.
i tried to download openbullet 2 again, format windows but still the same problem.
USE |CPU|91.8 %|
|—|—|
|USE Memory|31.81 GB|
|USE NETWORK|1582 Kbit UP / 166 Mbit DOWN|
|Number Build|7801.34874 (11/05/2021 19:22:28)|
some times in the console of openbullet 2 it wrote me a continuous proxy error
you know how to solve, I have 200 gigabytes of ram and a very powerful cpu I don’t understand this problem that has been happening since yesterday.
I’m hosting everything on a dedicated one
the error in the console and this
could not get the IP from the HttpAccessor . This might happen when OB2 is set up behind a reverse proxy
I discovered the error but I don’t understand, if I insert Request administrator login the CPU and RAM go up a lot, on the other hand, if not prompted Request administrator login, the cpu and ram remain low. but I don’t understand why I've been using it since openbullet 2 came out but it had never given me such a problem

@@


Sadness on latest update... 'bug' fixed

Issue Type: Bug
Formerly you could 'clear terminal' even while your terminal was busy with a process. Now it queues the control-l until the process is  done.
I don't know how often the previous behavior was useful , but it was plenty. I would often start my compile, clear the terminal, and only have to deal with the errors of that run. Or I would be debugging an interactive program with lots of output, and clear the output, so I am only looking at what the computer is doing right now.
I would like there be a way to clear the terminal even when the terminal is busy.
VS Code version: Code 1.23.0 (7c7da59c2333a1306c41e6e7b68d7f0caa7b3d45, 2018-05-03T15:23:19.356Z)
OS version: Linux x64 4.13.0-40-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz (8 x 2800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: unavailable_softwarevideo_encode: enabledvpx_decode: unavailable_softwarewebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
31.37GB (9.50GB free)

Process Argv
/usr/share/code/code --unity-launch

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

vscode-glsllint
CAD
0.0.3

spgo
Sit
1.2.2

code-gnu-global
aus
0.2.2

githistory
don
0.4.0

gitlens
eam
8.2.4

githd
hui
1.1.3

vscode-clang
mit
0.2.2

python
ms-
2018.4.0

cpptools
ms-
0.17.0

proto
pet
0.0.2

trailing-spaces
sha
0.2.11

shader
sle
1.1.3

clang-format
xav
1.6.2

(3 theme extensions excluded)

This behaviour is really really annoying and the terminal is pretty useless now, at least for me. Started using external terminal again...

I reverted this change, it'll go out in the recovery build 1.23.1. See https://github.com/Microsoft/vscode/issues/49162#issuecomment-386820864


[feat] Quest Status Tracker: Username Quest

This issue is to create a new CheckUsernameStatus function on the backend. This function will be used to return the user's progress on the Username Quest onchain.
The goal is to return 0, 1 if the user does not have a username in the Users table on postgres, and return 1, 1 if the user has a username in postgres.
Looking at other CheckXStatus functions should give good examples.
References

Quest status backend
Username table
Username quest onchain

Hey @Soeten, thank you for volunteering for the issue. Can you comment here so I can
assign you, if you are still interested?

Hey @Shoetan, thank you for volunteering for the issue. Can you comment here so I can
assign you, if you are still interested?

Hi, if this is still available I could work on this :)

Hi @b-j-roberts thank you so much. I would love to be assigned the issue.


Process suspended when stdout and stderr are redirected and the process is daemonized

Here's a shell session demonstrating the issue:
$ serve -s . >/dev/null 2>&1 &
[1] 31586
# after a couple of seconds, this message is displayed:
[1]  + 31586 suspended (tty output)  serve -s . > /dev/null 2>&1

# checking process status... output edited for readability
$ ps gv | grep serve
32623 pts/28   TNl    0:00      0 24425<PHONE_NUMBER>0  0.2 node <some_path>/serve -s .

# the "T" in "TNl" above means the process is "stopped, either by a job control signal or because it is being traced."
# for details, go to https://linux.die.net/man/1/ps and Ctrl-F "process state codes"

# at this point, opening the link in the browser produces no response (connection stalls)

# however, all of these combinations work just fine:
$ serve -s . &                     # neither stdout nor stderr redirected
$ serve -s . >/dev/null &          # stderr not redirected
$ serve -s . 2>/dev/null &         # stdout not redirected
$ serve -s . 1>/dev/null 2>&1      # not backgrounded

As you can see, the issue only occurs if all 3 of the following conditions hold:

stdout is redirected (>/dev/null or 1>/dev/null)
stderr is redirected (2>/dev/null or, more commonly, 2>&1)
the process is sent to the background (trailing &)

This should be fixed once boxen uses a new binary for getting the window size.
See issue https://github.com/sindresorhus/term-size/issues/3#issuecomment-299663503

Updating the dependencies (npm install) should fix this but now although the process is not stopped immediately, it doesn't run the server (if you go to http://localhost:5000 it never loads)

Already updated to the latest boxen!


fix: fix 'automountServiceAccountToken' flag in the projected

What type of PR is this?
/kind bug

What does this PR do?

fix: fix 'automountServiceAccountToken' flag in the projected
Which issue(s) does this PR fix?

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

/lgtm
/approve


Throws when containers are written inside of a struct without a field…

…name.
Issue #, if available:
#341
Description of changes:
Throws when a user attempts to write a container within a struct without a paired fieldname.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I feel like this could benefit from a higher level test. The original issue was doing this:
        let data = "{ x: 1 }";
        let reader = ion.makeReader(data);
        let writer = ion.makeTextWriter();
        writer.stepIn(ion.IonTypes.STRUCT);
        writer.stepIn(ion.IonTypes.STRUCT, ['a', 'b']);
        reader.next();
        reader.stepIn();
        reader.next();
        writer.writeValues(reader);
        reader.stepOut();
        writer.stepOut();
        writer.stepOut();

So maybe not something this long, but at least demonstrating the spirit of what was attempted and where it should fail.
This would help prevent regressions in case lower level semantics change.

this test is doing so?
https://github.com/amzn/ion-js/blob/master/tests/unit/IonTextWriterTest.js#L363

At a first glance that felt too minimal, but you're right it's the minimum case for this problem. All set, thank you.


display disclaimer and intro text somewhere on the chat welcome page

use content we had on the bot framework composer pilot.

Disclaimer should probably be a popup (use fluent-ui) that is closable, has a link to re-view it on the bottom of the page footer besides feedback link. And stores a cookie so its not redisplayed again after accepting and closing dialog.

Finished. Will run it by @GuillaumeTurcotte before closing.


When uploading via URL, download file in chunks to reduce memory usage

Fixes #20

Thanks!

Just modified the commit to also do the same download action for thumbnail updates.

Hi there,
My name is Derek and I'm now one of the maintainers of the Yt gem. I want to both thank you for your contribution and apologize for the lack of feedback on your pull request. Maintaining an open source project like Yt is a pretty big job, and we're taking steps to prioritize maintenance and development of the project. We're hoping to review community contributions on a regular basis, as well as provide a roadmap for our development plans.
As part of this process we're going through the open PRs and taking action on each one, and for this PR we've chosen to close it. Unfortunately due to the sheer number of PRs and amount of time that's passed, we can't address your PR individually. If you'd like our thoughts, feel free to comment on your PR, and we'll try and get back to you in a timely manner. In lieu of that, some of the reasons we've closed PRs are:

a lack of tests. We strive for comprehensive coverage; this is important to us
the passage of time: things that were relevant when the PR was opened might not be as important anymore
feature need. Since adding features requires us to maintain them, we want to add features that many people will use

Thanks again for your contribution, and please let us know if you have any questions or comments.


Rkilgour/dotnet 6 upgrade

Just a little tidy-up task, but both the Client.Gui and Client.Repl projects have ghost file inclusions for AppSetting.config files. i.e. they are included within the project but are not actually within the repo. I assume that these should just be excluded as users are supposed to create their own AppSettings.config but with these present in the project that cannot be done via Visual Studio unless you first exclude the listed ones from the project. These were probably accidentally checked in at some point and then later deleted. See below for the 2 files:

I think that the instructions within the ReadMe.md could be a little clearer. The bold line in particular appears to be ambiguous as there does not appear to be a default value.
0. Configuration:

copy AppSettings.config.example -> AppSettings.config
insert corresponding values for API_TOKEN
- if using a base url other than the default, insert this as well for BASE_URL

Just a little tidy-up task, but both the Client.Gui and Client.Repl projects have ghost file inclusions for AppSetting.config files. i.e. they are included within the project but are not actually within the repo. I assume that these should just be excluded as users are supposed to create their own AppSettings.config but with these present in the project that cannot be done via Visual Studio unless you first exclude the listed ones from the project. These were probably accidentally checked in at some point and then later deleted. See below for the 2 files:

Ah, I didn't know these files were checked in. Will remove them.

I think that the instructions within the ReadMe.md could be a little clearer. The bold line in particular (3rd bullet) appears to be ambiguous as there does not appear to be a default value.
0. Configuration:
* copy AppSettings.config.example -> AppSettings.config

* insert corresponding values for API_TOKEN
  **- if using a base url other than the default, insert this as well for BASE_URL**

Agreed, I have been holding off on updating the documentation until completion, but I think it would have made sense to do it before the PR. Will do this now.

thanks for the comments, working on them now.

This is looking good but with a couple of small things that could be improved. See my comments. for details.

thanks for the comments, working on them now.


react-scripts: not found

I have downloaded the react,react-dom and @tensorflow/tfjs, But i still get the above error please can anyone help with this?

make sure you run npm install

I am able to see npm start working and opening the web with my web cam but npm install has lot of error.  please let me know if i need be concerned.
logs.pdf

Interesting, if it’s working I wouldn’t be concerned 🤷♂

I got an error when i ran npm install

What version of node do you have?

6.4.1

v10.15.3

I'm not sure why there are errors, but can you verify that the web app is running properly?

Closing due to inactivity


Issue with Microsoft.cds.coreassemblies.internal

Hello, solution can't be built. VS raises errors and it could not find "Microsoft.cds.coreassemblies.internal", please see the screen print.  I've already installed these three nuget packages:
Microsoft.PowerPlatform.Dataverse.Client
Microsoft.PowerPlatform.Dataverse.Client.Dynamics
Microsoft.Dynamics.Sdk.Messages

It is written in the readme:

The Dataverse ServiceClient cannot be built outside of Microsoft This is due to a set of dependencies on nuget packages that are internally available only. At some point in the future, we will expose the supporting nuget packages when we have updated our server infrastructure to support plugin development on .net core.

@bluebookfairy,  as @BetimBeja points out... we do state that this is the case in the readme upfront.   We hope to be able to do this in the future.


setObject not working

Hi,
I am not able to save an object.
The log shows : PINDiskCache.m (303) ERROR: The operation couldn’t be completed. (Cocoa error 4.)

@cyril94440 that's an error reported by the system when writing the object to disk. Can you give more information? A small sample program showing the issue? What version of PINCache are you using, or even better, what is the last commit?

Hi,
I'll try to provide more information but for now, I didn't change anything in my code directly linked to PINCache. I am using the last version using cocoa pods

On 14 Jul 2015, at 16:22, Garrett Moon<EMAIL_ADDRESS>wrote:
@cyril94440 that's an error reported by the system when writing the object to disk. Can you give more information? A small sample program showing the issue? What version of PINCache are you using, or even better, what is the last commit?
―
Reply to this email directly or view it on GitHub.

I am using the Parse-NSCoding repo.
Can it be due to a bad NSCoding implementation ?

@cyril94440 The error is an error occurring when setting the file modification date. It's returned by the system.
If I were debugging this, I'd put a breakpoint at the top of setFileModificationDate in PINDiskCache and see what is getting passed into setAttributes. If it's not immediately obvious what the issue is, can you paste what date and fileURL are in the case where it errors?

Nothing strange :/
2015-07-16 16:25:21 +0000
file:///var/mobile/Containers/Data/Application/5189A230-65E2-4DDD-927F-27817C3711AA/Library/Caches/com.pinterest.PINDiskCache.PINCacheShared/alreadyMatchUsers

Hmm, are you using the cache from an extension or watch extension? Do you have multiple cache's with the same name?

I am using group for sharing files with the watch extension.
However I am not even using an apple watch. So the code is running only for the iOS app part.
I am using the sharedCache only.
Maybe there is something happening with the group files...?

On 16 Jul 2015, at 22:29, Garrett Moon<EMAIL_ADDRESS>wrote:
Hmm, are you using the cache from an extension or watch extension? Do you have multiple cache's with the same name?
―
Reply to this email directly or view it on GitHub.

@cyril94440 PINCache does not yet support running in multiple processes at once (i.e. phone app and watch app) yet see https://github.com/pinterest/PINCache/issues/2
It could indeed be the OS 'protecting' access to group files. I'm not sure :(
I'd happily accept a pull request to implement the feature requested in the above github issue.


Make Python scripts in build_defs compatible with Python 3.

Some distributions like Arch Linux no longer ship Python 2 by default
and /usr/bin/python on these systems is a Python 3.x version, which
causes Bazel to try to run them with Python 3.x as part of the build.
With these changes, I was able to successfully build the plug-in on my
Arch Linux machine. I made sure that the changes are backwards
compatible with Python 2.x.

It looks like this should resolve #453

@drichelson Yes, I can confirm that was one of the errors I also saw on my machine. :)
@brendandouglas @plumpy I've imported the change internally in our code review system for review and merging.

Closing, because this has been merged and pushed as part of https://github.com/bazelbuild/intellij/commit/f054292b07806a288eb205d13f336badbbe1464b :)


Polyline option to make loop

Because PolygonGraphics' outlineWidth doesn't work for values other than 1, it would be nice if PolylineGraphics could have the option of changing the line strip into a line loop with a nice mitered corner.  Mentioned on the forum.

First we'd need to add loop support to PolylineGeometry.  Both PoylineCollection and GroundPolylineGeometry have support so that's the one that needs to be updated

We also plan on removing the outlineWidth limitation as part of our terrain efforts (but allowing geometry outlines to use the material system).  Not sure if that changes anything.

I don't think removing the outlineWidth limitation helps because the higher level concept is a line not a polygon.  The polygon was just a potential workaround.

duplicate  #5644

Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/forum/#!msg/cesium-dev/wECK0_q6ZPA/VfYj79LkAQAJ
If this issue affects any of these threads, please post a comment like the following:

The issue at https://github.com/AnalyticalGraphicsInc/cesium/issues/7202 has just been closed and may resolve your issue. Look for the change in the next stable release of Cesium or get it now in the master branch on GitHub https://github.com/AnalyticalGraphicsInc/cesium.


Add flake8 to the Travis run

flake8 would have caught the regression in #371 and output:
pipenv/cli.py:257:19: F821 undefined name 'hashed_deps_path'
Whilst in an ideal world there would be 100% test coverage, linters help fill in the gaps, plus spot potential unused variable/imports cleanup.
I'm happy to disable more of the style/whitespace pep8 rules if needed - the priority is having the pyflakes subset run in CI.

will merge once ci finishes

@edmorley are you on irc or facebook? would be great to have a chat with you


Locale wrapper fix

Description
This fixes the LocaleWrapper by updating to the new Context API of react.
Please be aware that you should update the config provider import in your project to:
import ConfigProvider from 'antd/lib/config-provider'; as their seems to be difficulties when importing from antd root.
Compare https://github.com/geostyler/geostyler-demo/pull/221
When working with npm link and webpack you'll even need to add an alias for antd to your webpack config.
Related issues or pull requests
closes #1417
Pull request type
Please check the type of change your PR introduces:

[x] Bugfix

Do you introduce a breaking change?

[x] No

Checklist

[x] I understand and agree that the changes in this PR will be licensed under the BSD 2-Clause License
[x] I have followed the guidelines for contributing
[x] The proposed change fits to the content of the code of conduct

Very nice! Would you see the required change of ConfigContext as a breaking change?

No. The API of the localize function should not be affected.


Fixes Blackfriday issue; provides explicit v2

This PR removes all reference to gopkg.in origin for blackfriday, because it is problematic. Direct reference to blackfriday via github.com works fine.
Also this PR adds a v2 folder, in line with the Go modules specification for semver versioned code that is > v1.
When merging, please note that the first line of go.mod should stay matcornic, i.e.
module github.com/matcornic/hermes/v2

This PR should resolve issue #67 .

Perhaps the last v1 code ought to be re-instated in the top-level folder. Also, it is possible to handle v2, v3 ... etc using tags instead of folders.
See https://blog.golang.org/v2-go-modules

please accept this

I guess it won't be accepted until the codebeat gets green.
Waiting for a satisfying solution for @matcornic we have to add replace gopkg.in/russross/blackfriday.v2 => github.com/russross/blackfriday/v2 v2.0.1 into go.mod, I hope that there won't be any other side-effect

fixed in https://github.com/go-hermes/hermes


Multiple organisation names

There are two 'wikimedia Organisation' links under the frontend contribute section.

@kaiwalyakoparkar could you just add a good first issue label, so that beginners can contribute

#121 Pull request made.


How to config multiple route rules to one service?

如题. 同一个服务如何配置多个路由规则 ?
如果我对一个服务设置两个路由规则, priority的级别不一样, 那么dubbo会不会先执行优先级高的, 再继续执行优先级低的规则呢 ? 用这种方式能不能达到我一个服务设置多个路由规则的功能 ?

We recommend use english. In theory, you can set as many route rules as you can, and i don't think the execute order of route rules will make any difference?

I set two routing rules for the same service, but dubbo-admin just displays one routing rule. please see pictures

It seems to be a bug of dubbo-admin

dubbo/dubbo-ops#9

sincerely, I guess:
If we build a bridge with dubbo and camel/spring-integration, then many patterns in EIP and connections to many framework can be reuse in dubbo applications.


图片生成的Pipeline和NLP任务纠结在一起了

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched the tutorial on modelscope  doc-site
I have searched related issues but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
使用StableDiffusion XL, 结果依赖ChatGLM等llm模型的依赖。
To Reproduce
使用官网提供的例子代码
from modelscope.utils.constant import Tasks
from modelscope.pipelines import pipeline
import cv2

pipe = pipeline(task=Tasks.text_to_image_synthesis,
                model='AI-ModelScope/stable-diffusion-xl-base-1.0',
                use_safetensors=True,
                model_revision='v1.0.0')

prompt = 'a dog'
output = pipe({'text': prompt})
cv2.imwrite('result.png', output['output_imgs'][0])

2024-01-15 21:14:04,667 - modelscope - INFO - PyTorch version 2.1.2 Found.
2024-01-15 21:14:04,668 - modelscope - INFO - Loading ast index from /root/.cache/modelscope/ast_indexer
2024-01-15 21:14:04,733 - modelscope - INFO - Loading done! Current index file version is 1.11.0, with md5 ab42468469dcc2ef53ecdba98feb0b66 and a total number of 953 components indexed
2024-01-15 21:14:05,728 - modelscope - INFO - Use user-specified model revision: v1.0.0
Traceback (most recent call last):
  File "/data/c/envs/sd/lib/python3.10/site-packages/modelscope/utils/import_utils.py", line 450, in _get_module
    requires(module_name_full, requirements)
  File "/data/c/envs/sd/lib/python3.10/site-packages/modelscope/utils/import_utils.py", line 353, in requires
    raise ImportError(''.join(failed))
ImportError:
modelscope.models.nlp.chatglm2.tokenization requires the SentencePiece library but it was not found in your environment. Checkout the instructions on the
installation page of its repo: https://github.com/google/sentencepiece#installation and follow the ones
that match your environment.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/data/s/v0/m0.py", line 5, in <module>
    pipe = pipeline(task=Tasks.text_to_image_synthesis,
  File "/data/c/envs/sd/lib/python3.10/site-packages/modelscope/pipelines/builder.py", line 163, in pipeline
    clear_llm_info(kwargs)
  File "/data/c/envs/sd/lib/python3.10/site-packages/modelscope/pipelines/builder.py", line 227, in clear_llm_info
    from .nlp.llm_pipeline import ModelTypeHelper
  File "/data/c/envs/sd/lib/python3.10/site-packages/modelscope/pipelines/nlp/llm_pipeline.py", line 15, in <module>
    from modelscope.models.nlp import ChatGLM2Tokenizer, Llama2Tokenizer
  File "<frozen importlib._bootstrap>", line 1075, in _handle_fromlist
  File "/data/c/envs/sd/lib/python3.10/site-packages/modelscope/utils/import_utils.py", line 435, in __getattr__
    value = getattr(module, name)
  File "/data/c/envs/sd/lib/python3.10/site-packages/modelscope/utils/import_utils.py", line 434, in __getattr__
    module = self._get_module(self._class_to_module[name])
  File "/data/c/envs/sd/lib/python3.10/site-packages/modelscope/utils/import_utils.py", line 453, in _get_module
    raise RuntimeError(
RuntimeError: Failed to import modelscope.models.nlp.chatglm2.tokenization because of the following error (look up to see its traceback):

modelscope.models.nlp.chatglm2.tokenization requires the SentencePiece library but it was not found in your environment. Checkout the instructions on the
installation page of its repo: https://github.com/google/sentencepiece#installation and follow the ones
that match your environment.

Your Environments (required)

OS: uname -a

Linux dummy-0-nh6vf 4.19.91-26.al7.x86_64 #1 SMP Tue May 24 12:11:55 CST 2022 x86_64 x86_64 x86_64 GNU/Linux

CPU: lscpu

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         46 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  16
  On-line CPU(s) list:   0-15
Vendor ID:               GenuineIntel
  Model name:            Intel(R) Xeon(R) Platinum 8369B CPU @ 2.90GHz
    CPU family:          6
    Model:               106
    Thread(s) per core:  2
    Core(s) per socket:  8
    Socket(s):           1
    Stepping:            6
    BogoMIPS:            5799.99
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1
                         gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq monitor ssse3 fma cx16
                         pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault i
                         nvpcid_single ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid avx512f avx512dq r
                         dseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves wbnoinvd arat
                          avx512vbmi avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid fsrm arch_capabilities
Virtualization features:
  Hypervisor vendor:     KVM
  Virtualization type:   full
Caches (sum of all):
  L1d:                   384 KiB (8 instances)
  L1i:                   256 KiB (8 instances)
  L2:                    10 MiB (8 instances)
  L3:                    48 MiB (1 instance)
NUMA:
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-15
Vulnerabilities:
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl and seccomp
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Enhanced IBRS, IBPB conditional, RSB filling
  Srbds:                 Not affected
  Tsx async abort:       Not affected

Commit id (e.g. a3ffc7d8)

/data/s/v0# pip list|grep modelscope
modelscope               1.11.0

You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Pipeline related: @Firmament-cyou @wenmengzhou

安装AI-ModelScope/stable-diffusion-xl-base-1.0模型卡片上的依赖。


fix: add set up tool command

Add additional command to set up tools for SDK install

 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.jasonchen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Deployment of smart contracts to Opera testnet fails with Truffle error "unknown account"

Describe the bug
Deployment of smart contracts to Opera testnet fails with Truffle. Smart contracts deployment/migration process to testnet doesn't recognize any account on testnet and fails with error.
To Reproduce
Steps to reproduce the behavior:

Create smart contract within Truffle enabled repository
Compile it successfully with: "truffle compile"
Create migration script for smart contract
Define account which, should be used for deployment in migration script
Define host and port for Opera public testnet and from account in truffle-config.js

Deploy/migrate smart contract to Opera testnet with command: "truffle migrate"
See error

Expected behavior
Smart contract is deployed successfully to Opera testnet. Deployment is paid with testnet FTM from account defined in migration script.
Desktop

OS: Linux Ubuntu 18.04
Truffle v5.0.5
Node v10.17.0

Additional context
Link to repository used: https://github.com/matprime/meme-of-the-day-dApp

exist a solution?

Hi, so we were able to deploy to the Opera-testnet without any issue using truffle configuration. If you can have a look at this repository (https://github.com/Fantom-foundation/example-deployment) and follow the steps given below, it should help you deploy a smart contract to Opera-testnet using truffle framework. Let us know if you still get any errors!


Better fonts

By default Skype fonts are very ugly, this small fix improve fonts in much better look and Docker image only grows around 100 Kb.

I add an small update to use date command to get timezone instead make cat to /etc/timezone. This is much better cause not all distros have /etc/timezone file.

@ogarcia can you submit a separate PR for the timezone changes?

this small fix improve fonts in much better look

while you have piqued my interest with this PR, I don't the font. How about using the "Ubuntu" font family.
apt-get install -y ttf-ubuntu-font-family and font="Ubuntu,10,-1,5,50,0,0,0,0,0"

Ok. I do three new PR. One with timezone fix and two with fonts improvement. I think that looks better with Cantarell fonts, but Ubunu fonts fonts don't look bad. The size of font must be 11, set it to 10 is too small.
I close this PR.

Ah, take note that with Cantarell the image only grows 100 Kb and with ubuntu fonts around 5 Mb.


XL-sliders-inference

the XL-Sliders-inference notebook depends on annotations in the filename
            if 'full' in lora_weight:
                train_method = 'full'
            elif 'noxattn' in lora_weight:
                train_method = 'noxattn'
            else:
                train_method = 'noxattn'

            #train_method = 'full'

            network_type = "c3lier"
            if train_method == 'xattn':
                network_type = 'lierla'

            #network_type = 'lierla'

            modules = DEFAULT_TARGET_REPLACE
            if network_type == "c3lier":
                modules += UNET_TARGET_REPLACE_MODULE_CONV
            import os
            model_name = lora_weight

            name = os.path.basename(model_name)
            rank = 1
            alpha = 4
            if 'rank4' in lora_weight:
                rank = 4
            if 'rank8' in lora_weight:
                rank = 8
            if 'alpha1' in lora_weight:
                alpha = 1.0

but the pretrained models
https://sliders.baulab.info/weights/xl_sliders/
don't have these annotations

Oh, you are right! We have renamed the pretrained models!
All the models we released are alpha 1 and rank 4

Resolved this issue with default values set in the inference scripts. Thanks again for bringing it to our attention!


feat: update docs openapi

Update OpenApi

Please, add the following to the endpoints that require authentication:
security:
        - bearer: []

Done :)

There are some duplicated endpoints, Eg. POST /file/upload and POST /files.
The Bearer token should only be added to the endpoints that require authentication. For instance, the /auth/login and /account/register do not require authentication, while the /files/download does.
There are some endpoints with incorrect tags. For instance, the account/register endpoint should have the account tag.

Done, thanks for comment 💯


Scrutinizer Auto-Fixes

@robiso requested this pull request.
It consists of patches automatically generated for this project on Scrutinizer:
https://scrutinizer-ci.com/g/robiso/wondercms/

Removing some spaces.


Allow Using NativeNode

Currently, in using or usingComponents of behaviors (and components), if the target is not found, the default component in current component space is used.
This behavior should be changed. If the target is not found, then treat it as a native node.
This is helpful when working with placeholders, and maybe helpful to solve #5 .

P.S. if placeholder exists, it will not be treat as a native node.

Fixed in #15


wds: add more information for native tunnel

For a sandwiched Gateway a zTunnel inbound may:

Prepend the bytestream with PROXY protocol information
Send traffic to a specific port that handles all routing
Do neither, and simply copy bytes on the original destination port

This is on the Workload as it affects only captured waypoints. A GatewayAddress can represent un-captured Waypoints or external Waypoints.
GatewayAddress may act as a pointer Workload|Service} --> {maybe Service} --> Workload. The GatewayAddress port is what we will send to no matter what. If the Waypoint supports HBONE, it's the port bound on the Waypoint. If it's sandwiched, it's the zTunnel port. The waypoint's Service does not need to expose the GatewayAddress hbone port, but can map it.
OR
GatewayAddress is always a pointer Workload|Service} --> {maybe Service} --> Workload. For external gateways that don't have an internal workload, we use a special WorkloadType Gateway.
Related to #48362

cc @louiscryan @bleggett @howardjohn

@stevenctl: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
ecf2a275d29f4487f52eadef29a0bbb5149dbdd9
link
true
/test release-notes

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

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
ecf2a275d29f4487f52eadef29a0bbb5149dbdd9
link
true
/test release-notes

gencheck_istio
ecf2a275d29f4487f52eadef29a0bbb5149dbdd9
link
true
/test gencheck

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

@stevenctl the PR description seems like it may be tied to another implementation. Is that the case? Or am I misunderstanding it

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
ecf2a275d29f4487f52eadef29a0bbb5149dbdd9
link
true
/test gencheck

release-notes_istio
b8e5bc7c30945f6ed360de1ad7b9a07439954e6a
link
true
/test release-notes

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

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
b8e5bc7c30945f6ed360de1ad7b9a07439954e6a
link
true
/test release-notes

gencheck_istio
b8e5bc7c30945f6ed360de1ad7b9a07439954e6a
link
true
/test gencheck

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

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
b8e5bc7c30945f6ed360de1ad7b9a07439954e6a
link
true
/test gencheck

release-notes_istio
a1991c66ba5a389d97ea4abfb39b85162caffa01
link
true
/test release-notes

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

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a1991c66ba5a389d97ea4abfb39b85162caffa01
link
true
/test release-notes

gencheck_istio
a1991c66ba5a389d97ea4abfb39b85162caffa01
link
true
/test gencheck

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

@stevenctl the PR description seems like it may be tied to another implementation. Is that the case? Or am I misunderstanding it

@howardjohn updated it.. it made sense to me at the time.

IMO the Gateway object ( created by user or whatever) should set the protocol on the port, as defined by the upstream API. And that should be consumed by Istio - not sure inventing a parallel API / terminology is the simplest solution.

The upstream API doesn't map well to what we're doing here. The control plane sees Workload Foo uses Waypoint, and Waypoint is captured by zTunnel. Now it needs to tell zTunnel(s):

Outbound Traffic to Foo traffic go to Waypoint, on zTunnel's port
Inbound Traffic to Waypoint should go to Port 123
Inbound Traffic to Waypoint needs PROXY headers


Powershell integrated terminal "Execute Selection" (F8) doesn't work anymore.

Hitting F8 does nothing.
Cmdlet parameters autocompletion doesn't work in editor anymore, but it works in terminal window.

VSCode Version: Code - Insiders 1.16.0-insider (1c6f2f9a8012565adcc50616c3aa90cb444e8797, 2017-08-23T05:23:27.861Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

azuretoolsforvscode
bra
1.2.9

gitignore
cod
0.5.0

vscode-markdownlint
Dav
0.10.0

python
don
0.7.0

xml
Dot
1.9.2

git-project-manager
fel
1.3.2

gitattributes
has
0.4.1

ruby-linter
hoo
1.0.0

Ionide-Paket
Ion
1.7.3

github-pr
jas
1.0.0

azure-functions-tools
joh
0.3.0

vscode-github
Kni
0.18.1

MagicPython
mag
1.0.12

start-git-bash
McC
1.2.1

csharp
ms-
1.12.1

PowerShell
ms-
1.4.1

azurerm-vscode-tools
msa
0.3.6

vscode-docker
Pet
0.0.16

Ruby
reb
0.15.0

arm-snippets
sam
1.0.1

python
tht
0.2.3

gitflow
vec
1.1.1

(1 theme extensions excluded)

Steps to Reproduce:

Reproduces without extensions: Yes/No

Please move this to the powershell repo https://github.com/PowerShell/vscode-powershell

done! thx.


Rework Siddhi applications

Purpose

IS_ANALYTICS_LONG_SESSION siddhi spp is amended to calculate the last seven days timestamp of users. Initially, a trigger is sent at the beginning to store the average duration of users for the last seven days in an event table. Then another trigger is sent to update that event table for every 30 minutes.

TriggerStream and LastSevenDays are renamed as TriggerStreamAtDeployment and LastSevenDaysStream respectively.

@Ambujaa10, please ensure correct git commit comments when committing in the future. All your commits have merge comments