Environment variables and added .env

Added .env file support.
Also added Stacktrace to better find errors.

@Ali1Ammar @skillLan What do you think of this new feature?

https://www.prisma.io/docs/guides/development-environment/environment-variables#using-env-files

https://www.prisma.io/docs/guides/development-environment/environment-variables#using-env-files

I don't think this is well supported by simply parsing .env. The current implementation of dotenv on pub.dev is fine. Maybe we need to create a dotenv ourselves (the reason is that I tried to contact the dotenv author and got no response.)

@jacobaraujo7 I have rethought this problem, we may need to redesign the configuration, and solve the problem by the way:

Simpler and more direct format than dotenv
All configuration names in the program inherit from Prisma JS/TS client
Easier custom configuration file names and paths
Runtime configuration is easier to move and read
Runtime configuration allows sharing configuration from downstream

For this, I created a new requirement issue to document this feature 👉 #15

Hello.
I'm taking into account how Prisma works in Node. Currently I don't know how it works in Go or Python.
My projects with Prisma use .env in key/value format, which I supported in this PR.
The objective of this feature is to bring the Dart prism closer and closer to the prism used in NodeJS, making it easier to understand that it already comes from this stack.
Personally, I prefer to add the environment variable directly to the system, but as many use it, I decided to make this effort.

If Dart allows environment variables to be overwritten at runtime, it may be good to configure with .env. However, the environment variable of Dart VM is read-only and cannot be overwritten or appended. The experience of using dotenv in Dart is really bad.

Maybe we can give the option downstream, use the dot priama runtime configuration, or dotenv, depending on how it is configured in pubspce.yaml and the .env file is loaded by default.

@medz I agree with this point. It really is much better to add the environment variables directly into the system or with --define.
My point is about the marketing of the tool, since some Prisma users already have the habit of using .env in their projects and this practice is referenced in the official Prisma documentation.
However, if we are going to disregard the .env, we will keep this commit preventing null errors and this commit.
I see that this commit has already been added, so I believe it is ready. I will close this pullrequest.

I made a new PR with only this 2 commits.
https://github.com/odroe/prisma-dart/pull/16

@jacobaraujo7 Released version 2.1.0 👉 https://github.com/odroe/prisma-dart/releases/tag/2.1.0
Environment variable configuration using .env files is covered.


Extremely Verilog generation

I'm seeing very slow Verilog generation (at least 10s of minutes) for the following relatively straightforward module. It simulates successfully in Amaranth, but something in the Verilog generation process is going awry.
No claim is made that this is good code, but it probably shouldn't take forever to convert to Verilog.
from amaranth import *
from amaranth.hdl import *
from amaranth.back import verilog

class VectorPerm(Elaboratable):
    def __init__(self, register_width: int):
        self._register_width = register_width
        self.in_lhs = Signal(unsigned(register_width))
        self.in_rhs = Signal(unsigned(register_width))
        self.in_control = Signal(unsigned(register_width))
        self.out_res = Signal(unsigned(register_width))

    def elaborate(self, platform):
        m = Module()

        lhs_list = [self.in_lhs[i*8:(i+1)*8] for i in range(self._register_width // 8)]
        rhs_list = [self.in_rhs[i*8:(i+1)*8] for i in range(self._register_width // 8)]
        lists = lhs_list + rhs_list
        parts_array = Array(lists)

        control_list = [self.in_control[i*8:(i+1)*8] for i in range(self._register_width // 8)]

        selects = [parts_array[control_list[i]] for i in range(self._register_width // 8)]
        m.d.comb += self.out_res.eq(Cat(*selects))

        return m

if __name__ == '__main__':
    vec_perm = VectorPerm(register_width=128)
    with open('vec_perm.v', 'w') as f:
        f.write(verilog.convert(vec_perm,
                                ports = [
                                            vec_perm.in_lhs,
                                            vec_perm.in_rhs,
                                            vec_perm.in_control,
                                            vec_perm.out_res,
                                        ]))

Which version of Amaranth is this?

Which version of Amaranth is this?

0.4.5

Try HEAD. We have completely re-engineered the backend to avoid issues like this.

Confirmed that it completes almost instantly on HEAD

Closing as this won't matter after the next release.


[TVMC] A simplified TVMC API for python scripting.

As noted in many of @CircleSpin's recent PRs, TVMC has an excellent set of utilities to make python scripting in TVM a more approachable and intuitive experience for new users. This PR introduces an object oriented approach that we believe will be a much smoother introduction to working in TVM from Python. Before jumping into the design discussion, I want to note that we were careful to make sure that the command line TVMC workflow was minimally effected by this change.
In short, the goal this PR is to reduce a full TVM workflow into a small set of intuitive function calls, one example of which can be seen in test_model.py, which I'll include here for discussion.
tvmc_model = tvmc.load(onnx_resnet50)
tvmc.tune(tvmc_model, target="llvm")
tvmc_package = tvmc.compile(tvmc_model, "llvm")
result = tvmc.run(tvmc_package, device="cpu")
print(result) # Will print a pretty time estimator breakdown

The above code uses three new classes defined in tvmc/model.py: TVMCModel, TVMCPackage, and TVMCResult.
A TVMCModel is a wrapper around a precompiled model in TVMC. It can be generated either by calling tvmc.load or by pointing it to a previously saved TVMCModel. The class itself is very straightforward and most of its functionality is for saving and loading itself from disk and producing TVMCPackages. Being able to save and load TVMCModel's directly is convenient when users dont want to have to run a relay importer everytime they start up a new python instance.
Calling tvmc.compile on a TVMCModel now will produce a package using export_model_library_format which was introduced in PR #7533. This format is actually very similar to what TVMC was previously using and will likely become the standard way for saving compiled artifacts going forward. The produced package is then used to create a TVMCPackage object which contains all the information needed to run the model.
The TVMCPackage is passed to tvmc.run which now returns a TVMCResult, a very simple wrapper around the runtime measurements and produced results.
I'd love to hear what you guys think of this flow and design and am happy to discuss any decisions in more detail. Assuming that this work is well received, we're planning on writing a tutorial for new users based on it.
Also included in this PR are a change to auto_scheduler.HardwareParams such that all arguments are optional. When an argument is provided as None, it will now extract the default value for the current target. I've also changed the default values for hardware parameters in TVMC to be None to reflect this change. This should make the default behavior of tvmc more consistent with other workflows.

@leandron, @areusch, @tkonolige, @CircleSpin can you guys take a look at this PR and let me know what you think?

Thanks for the proposal. I like the OOP approach in general since it clearly represents the available APIs and relationship between objects. I'll spend sometime on reviewing this PR in this week. Meanwhile, for the example, it seems to me that the following design is more OOP style:
tvmc_model = tvmc.load(onnx_resnet50)
tvmc_model.tune(target="llvm")
tvmc_package = tvmc_model.compile(target="llvm")
result = tvmc_package.run(device="cpu")

In this way, we can clearly see tvmc_model is the basic and the most instance in TVMC, and most features can be easily found out by looking at its methods. In addition, we can also learn from the method compile and run that tvmc_package is the compiled result of tvmc_model; tvmc_result is the execution result of tvmc_package.

@comaniac, the OOP approach was something we discussed and are on the fence about implementing. The reason we went with this functional API is because we want this API to be catered to new users trying to understand TVM. These users will often not be familiar with ML deployment and breaking the process down into 4 concrete steps (load, tune, compile, and run) can help crystallize exactly what TVM is doing. I feel that making it object oriented instead somewhat obscures the steps. That said, I do agree that there are benefits to OOP such as discoverability and would be fine adding class methods if you feel strongly that its better.

@comaniac, the OOP approach was something we discussed and are on the fence about implementing. The reason we went with this functional API is because we want this API to be catered to new users trying to understand TVM. These users will often not be familiar with ML deployment and breaking the process down into 4 concrete steps (load, tune, compile, and run) can help crystallize exactly what TVM is doing. I feel that making it object oriented instead somewhat obscures the steps. That said, I do agree that there are benefits to OOP such as discoverability and would be fine adding class methods if you feel strongly that its better.

@jwfromm I got your point, which is also fair enough. Although I personally prefer the class method approach still, I don't feel it is strongly better than the proposed one, so I'm fine with it if others agree.

@areusch I've addressed or asked questions about all your feedback. Could you take another look and let me know what you think? With regards to the custom packaging format, I don't think there's a big need for detailed documentation. The main motivation for introducing TVMCModel and TVMCPackage is to make it so users don't have to acknowledge the packing format or even the packaged files if they dont want to. Only advanced users, who should be comfortable reading the code, would ever have any need to dig into the packaging.

@leandron I'd really love for you or someone else who uses TVMC to take a look at this and let me know what you think. Also @areusch, I split off result utilities as we discussed, are there any other changes you'd like to see with this PR?

@leandron I'd really love for you or someone else who uses TVMC to take a look at this and let me know what you think. Also @areusch, I split off result utilities as we discussed, are there any other changes you'd like to see with this PR?

I will have a look first thing tomorrow.

@leandron  please take a look when you have a minute

Thanks @jwfromm @tkonolige @leandron @areusch


cannot create a pipeline between MongoDB and NEO4j

after typing " mongo-connector -m localhost:27017 -t http://localhost:7474/db/data -d neo4j_doc_manager " I get following error,
Exception in thread Thread-2:
Traceback (most recent call last):
File "/Users/gauravvashisth/anaconda/lib/python3.5/threading.py", line 914, in _bootstrap_inner
self.run()
File "/Users/gauravvashisth/anaconda/lib/python3.5/site-packages/mongo_connector/util.py", line 104, in wrapped
func(*args, **kwargs)
File "/Users/gauravvashisth/anaconda/lib/python3.5/site-packages/mongo_connector/oplog_manager.py", line 267, in run
docman.upsert(doc, ns, timestamp)
File "/Users/gauravvashisth/anaconda/lib/python3.5/site-packages/mongo_connector/doc_managers/neo4j_doc_manager.py", line 66, in upsert
tx.commit()
File "/Users/gauravvashisth/anaconda/lib/python3.5/site-packages/py2neo/cypher/core.py", line 306, in commit
return self.post(self.__commit or self.__begin_commit)
File "/Users/gauravvashisth/anaconda/lib/python3.5/site-packages/py2neo/cypher/core.py", line 261, in post
raise self.error_class.hydrate(error)
File "/Users/gauravvashisth/anaconda/lib/python3.5/site-packages/py2neo/cypher/error/core.py", line 54, in hydrate
error_cls = getattr(error_module, title)
AttributeError: module 'py2neo.cypher.error.schema' has no attribute 'ConstraintValidationFailed'
I have installed py2neo 2.0.7

i faced the same problem, you are violating some constraint for me it was uniqueness constraint.

i faced the same problem, too...
how did you solve the problem?


Template version EWMAT

The argument of non-using float is false.
When you look at the code, there're at least 3 divisions, which are very slow !

Divisions are indeed slow on AVR because they do not have hardware division instructions. However, the existence of a division operation does not promote the variables in that operation to float. Int division just nets a result and remainder, the latter of which is ignored returning a result that is truncated.
As an example, the operation 3 / 2 does not internally utilize a float at any point; it instead internally has a result of 1 and a remainder of 1, and so would return 1 rather than 1.5.


Quick start example not working react-native 0.7

Target device: (Note: simulators are not supported for running the UIKit)

Device: Galaxy J7 Prime
OS:

[ ] IOS
[X] Android

OS Version: Android 8

App Info

Type:

[X] React Native CLI & NX
[ ] Expo CLI (using custom development clients)

react-native: 0.70

Describe the issue
const App = () => {
  const [videoCall, setVideoCall] = useState(false);
  const connectionData = {
    appId: 'APP_ID',
    channel: 'CHANNEL_NAME',
    token: 'TOKEN'
  };
  const callbacks = {
    EndCall: () => setVideoCall(false),
  };
  return videoCall ? (
    <AgoraUIKit connectionData={connectionData} rtcCallbacks={callbacks} />
  ) : (
    <Text onPress={() => setVideoCall(true)}>Start Call</Text>
  );
};

I'm not able to use the quickstart example in my app, when running the app I'm getting the following error:
TypeError: Cannot read property 'prefix' of null, js engine: hermes
 ERROR  Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). Module has not been registered as callable. Registered callable JavaScript modules (n = 10): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., js engine: hermes

The error is cause by the  component removing it my app is working as expected.
To Reproduce
Steps to reproduce the behavior:

Run the quick start example : https://www.npmjs.com/package/agora-rn-uikit

Did you install the native dependency? npm i react-native-agora, if you're on iOS you'll also have install pods npx pod-install.

Can you share your package.json?

@EkaanshArora I found another SDK that worked for me. I will  close this issue. Thank you for help


porter bundle publish command

We need a new command porter bundle publish, alias porter publish that uses https://github.com/deislabs/duffle/pull/681 to push a bundle to a docker registry.
porter  publish [--file myapp/porter.yaml] [--tag altreg/myapp:tag] [--cnab-file bundle.json]

--file defaults to the bundle in the current directory
--tag defaults to a tag specified in the porter.yaml. This would be a new manifest field, Tag.
--cnab-file is an optional flag (cannot be specified when --file is present), that points to a bundle.json and is used for non-porter bundles only.

We aren't using the push verb because it's a composite command doing multiple bits of work under the hood:

This should follow the behavior outlined in #320, namely ensuring that cnab/bundle.json is up-to-date with porter.yaml before pushing, and potentially rebuilding.
Push the invocation image.
Push the bundle manifest.
TODO: I forgot the rest, sorry. Will fill in later.

Do we need a separate issue to track removing the invocation image push step from porter build (assuming consensus on this change is met)?  Or add to AC to this one?

If we remove it, without making any other change, will stuff still work? Or do we need do it as part of publish at the same time to not break porter?

If we remove it without making any other change, local bundle installation will continue to work (assuming using same docker daemon as image was built with) but the bundle may not be installable by another user on a different machine (unless porter build is run on their machine from same bundle source).
I would think adding it as part of publish in this/same set of commits would make the most sense, to cover the latter case mentioned above.  It feels 'right' that the invocation image would/should only be pushed to a remote repo when the bundle is published.

Ok, sounds good to me to do it all in a single PR then.

CLOSED BY OTHER PRS


Use tilized operators for Mistral AI speedup on inference

use tilized operators for Mistral AI migrate from row-major
tilized tensors are faster on GS/WH TT Tensix cores
use the tt_lib.tensor.tilize_with_val_padding when necessary

Reference: https://github.com/tenstorrent-metal/tt-metal/tree/a3740def58c3b8672b7e3279261506ae70b97810/models/demos/resnet/tt
/metalResnetBlock50.py

The commit is reverted to preserve the sensible output.
Corresponding PR: https://github.com/tenstorrent-metal/tt-metal/pull/4029


'bower install' fail on Windows

Hi, I'm trying to setup development environment for AngularJS and so I'm following the procedure described here. I keep getting an error with the command bower install relative to installation of a package called ng-closure-runner#*. Here is the full console log for the command:
C:\Users\gimmi\Sources\angular.js>bower install
bower bootstrap#*           not-cached https://raw.github.com/twbs/bootstrap/v2.0.2/docs/assets/bootstrap.zip#*
bower bootstrap#*              resolve https://raw.github.com/twbs/bootstrap/v2.0.2/docs/assets/bootstrap.zip#*
bower closure-compiler#*    not-cached https://closure-compiler.googlecode.com/files/compiler-20130603.zip#*
bower closure-compiler#*       resolve https://closure-compiler.googlecode.com/files/compiler-20130603.zip#*
bower ng-closure-runner#*   not-cached https://raw.github.com/angular/ng-closure-runner/v0.2.2/assets/ng-closure-runner.zip#*
bower ng-closure-runner#*      resolve https://raw.github.com/angular/ng-closure-runner/v0.2.2/assets/ng-closure-runner.zip#*
bower bootstrap#*             download https://raw.github.com/twbs/bootstrap/v2.0.2/docs/assets/bootstrap.zip
bower ng-closure-runner#*     download https://raw.github.com/angular/ng-closure-runner/v0.2.2/assets/ng-closure-runner.zip
bower closure-compiler#*      download https://closure-compiler.googlecode.com/files/compiler-20130603.zip
bower lunr.js#0.4.0             cached git://github.com/olivernn/lunr.js.git#0.4.0
bower lunr.js#0.4.0           validate 0.4.0 against git://github.com/olivernn/lunr.js.git#0.4.0
bower jquery#1.10.2             cached git://github.com/components/jquery.git#1.10.2
bower jquery#1.10.2           validate 1.10.2 against git://github.com/components/jquery.git#1.10.2
bower google-code-prettify#1.0.0           cached git://github.com/tcollard/google-code-prettify.git#1.0.0
bower google-code-prettify#1.0.0         validate 1.0.0 against git://github.com/tcollard/google-code-prettify.git#1.0.0
bower components-font-awesome#3.1.0        cached git://github.com/components/font-awesome.git#3.1.0
bower components-font-awesome#3.1.0      validate 3.1.0 against git://github.com/components/font-awesome.git#3.1.0
bower ng-closure-runner#*                 extract ng-closure-runner.zip
bower bootstrap#*                         extract bootstrap.zip
bower closure-compiler#*                  extract compiler-20130603.zip
bower ng-closure-runner#*                   EPERM EPERM, rename 'C:\Users\gimmi\AppData\Roaming\bower\cache\packages\b49378d5565266ad51701fa65c017d3e\_wildcard'

Stack trace:
Error: EPERM, rename 'C:\Users\gimmi\AppData\Roaming\bower\cache\packages\b49378d5565266ad51701fa65c017d3e\_wildcard'

Console trace:
Trace
    at StandardRenderer.error (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
    at Logger.updateNotifier.packageName (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
    at Logger.EventEmitter.emit (events.js:95:17)
    at Logger.emit (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
    at C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
    at _rejected (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
    at C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:30
    at Promise.when (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:1079:31)
    at Promise.promise.promiseDispatch (C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
    at C:\Users\gimmi\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44

System info:
Bower version: 1.2.8
Node version: 0.10.24
OS: Windows_NT 6.2.9200 x64

@danilodeveloper Unfortunately your solution doesn't work for me. Can you please tell me the name of your node version and bower? I would like to run "bower install livereload --save-dev".

@PunkSage We have now Windows CI. Feel free to add failing test if you want us to fix it.

when I run "npm install -g bower"
it shows like below
C:\Users\Prashant.shukla\AppData\Roaming\npm\bower -> C:\Users\Prashant.shukla\AppData\Roaming\npm\node_modules\bower\bin\bower
<EMAIL_ADDRESS>C:\Users\Prashant.shukla\AppData\Roaming\npm\node_modules\bower
After this when I check
"bower -v"
found
bash: bower: command not found
How to fix it?


RFE: Better extensibility

We are building some features on top of Valita and with the .4 release a lot of the public APIs that we depend on are now marked as private. I'm going to outline the things we are using to see if we can figure out how to expose these in a clean way.
Command Line Parser
We have a library that takes a Valita schema and generates a command line parser.
The code is ~500 LOC and it will be open sourced this year. I can give access to it early if you are curious.
API Used
toTerminals: This is used for the visitor pattern. We use it to gather the literals and the types.
ArrayType.prefix, ArrayType.rest, ArrayType.suffix: toTerminals was not called on these so we had to do that manually. This is used with the above. I believe we can mostly create our own visitor except for these which are not exposed.
func: We used this to get the default value out of an optional. I think I can test for name === 'optiopnal' and in that case there is no default value. Otherwise I can call schema.parse(undefined) and see what I get out of it.
Customized Error Messages
No breaking changes here but it does reproduce some of the functionality (~100 LOC). Not a big deal at the moment.
Better Union Error Reporting
When a union fails to parse we find the longest partial match and show the error for that. This allows errors like
API Used

UnionType.options: This is used to get the different types of the union and we try all of them to see which one gives use the longest path.

Sample Implementation
type FailedType = {type: v.Type; err: v.Err};

function getDeepestUnionParseError(
  value: unknown,
  schema: v.UnionType,
  mode: ParseOptionsMode,
): string {
  const failures: FailedType[] = [];
  for (const type of schema.options) {
    const r = type.try(value, {mode});
    if (!r.ok) {
      failures.push({type, err: r});
    }
  }
  if (failures.length) {
    // compare the first and second longest-path errors
    failures.sort(pathCmp);
    if (failures.length === 1 || pathCmp(failures[0], failures[1]) < 0) {
      return getMessage(failures[0].err, value, failures[0].type, mode);
    }
  }
  // paths are equivalent
  try {
    const str = JSON.stringify(value);
    return `Invalid union value: ${str}`;
  } catch (e) {
    // fallback if the value could not be stringified
    return `Invalid union value`;
  }
}

// Descending-order comparison of Issue paths.
// * [1, 'a'] sorts before [1]
// * [1] sorts before [0]  (i.e. errors later in the tuple sort before earlier errors)
function pathCmp(a: FailedType, b: FailedType) {
  const aPath = a.err.issues[0].path;
  const bPath = b.err.issues[0].path;
  if (aPath.length !== bPath.length) {
    return bPath.length - aPath.length;
  }
  for (let i = 0; i < aPath.length; i++) {
    if (bPath[i] > aPath[i]) {
      return -1;
    }
    if (bPath[i] < aPath[i]) {
      return 1;
    }
  }
  return 0;
}

That is useful. I will see if I can find time to a PR that exposes enough for us to transition to .4

One more issue popped up this week. We are creating a deepPartial that recursively applies partial. However _restType is private on ObjectType.

deepPartial implementation
/**
 * Similar to `ObjectType.partial()` except it recurses into nested objects.
 * Rest types are not supported.
 */
export function deepPartial<Shape extends ObjectShape>(
  s: v.ObjectType<Shape, undefined>,
) {
  const shape = {} as Record<string, unknown>;
  for (const [key, type] of Object.entries(s.shape)) {
    if (type.name === 'object') {
      shape[key] = deepPartial(type as v.ObjectType).optional();
    } else {
      shape[key] = type.optional();
    }
  }
  return v.object(shape as {[K in keyof Shape]: v.Optional<v.Infer<Shape[K]>>});
}


Add Freeter

NOTE: A similar PR may already be submitted! Please search among the Pull request before creating one.
Types of Changes
What types of changes does your PR introduce? Put an x in all boxes that apply

[x] New addition to list
[ ] Fixing bug in existing item in list
[ ] Removing item from list
[ ] Changing structure (organization) of list

Proposed Changes
Describe each of your changes here to communicate to the maintainers why we should accept this pull request.
Added Freeter - the free and open-source organizer for a smarter work on your computer.
PR Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING guide
[x] I have explained why this PR is important
[ ] I have added necessary documentation (if appropriate)

Further Comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...


Added a code for traversing in linked list using c.

**THANKS FOR LOOKING AT MY PULL REQUEST I HAVE WRITTEN A CODE ON TRAVERSING IN LINKED LIST USING C PROGRAMMING APPRICIATE IF U WOULF MERGE IT THANKS **

Great could you give this repo a star🐱🏍

Already gave ur repo a star ⭐
On Sat, Oct 8, 2022, 8:34 PM Tanu soni @.***> wrote:

Great could you give this repo a star🐱🏍
—
Reply to this email directly, view it on GitHub
https://github.com/tanus786/CP-Codes-HackOctober-Fest-2022/pull/18#issuecomment-1272338590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHUMHWUYUFK4DV7WFDCMED3WCGEQ5ANCNFSM6AAAAAARAI762U
.
You are receiving this because you authored the thread.Message ID:
@.***>

okay thank you😊


Add links to source code for examples

Would it be possible to have links to the source code for the examples?
I can view all of the code in the inspector but it would be nice to see how it is structured.  I tried looking up the moon.js version of TodoMVC but it doesn't appear to be available in their list of choices.
Thanks!

Moon hasn't been submitted to TodoMVC yet (#86), and the source code for all of the examples are available in the gh-pages branch of this repo.


Implement xor function

I had a use case where I needed to get the elements from two streams that weren't contained in both. This is what I came up with:
Stream.prototype.xor = function (ys) {
    return this.uniq().collect()
        .flatMap(function (array) {
            return _(ys).uniq().reduce(array, function (memo, value) {
                var i = array.indexOf(value);
                if (i > -1) {
                    memo.splice(i, 1);
                }
                else {
                    memo.push(value);
                }
                return memo;
            }).sequence();
        });
};

_.xor([1, 5, 3, 2, 7])([1, 2, 3, 9, 1]).toArray(console.log);
//=> [ 9, 5, 7 ]

That was fine for what I was doing but there are a few problems, for example the use of uniq, which could cause problems with large streams (mine were never more than 50 items in length), the call to splice from inside reduce and the hardcoding of strict equality due to indexOf. I can already think of ways to make this more performant and flexible but before I do any more work on it I just want to know if anyone would find this new functionality useful?

I'm -1 on a kitchen sink API but maybe that horse has already bolted. I think there's a place for a separate library of stream combinators that can work with flatMap/fold, so this would be called as something like xs.flatMap(xor(ys)).

@quarterto by 'kitchen sink api' you mean that there are already too many primitives that do too many things already (english is not my native language) or does it mean something else ?
I agree we need to solve the 'components' issue so that a library ecosystem could emerge.
so @svozza that would mean that given the rare use of xor (and at least until other people request it) xor should probably be written as an external module.
Now on what is the best practice for such external modules I don't think I have seen a definitive agreement on this in the related issues. This should probably be the next big subject after 3.x is out.

@jeromew pretty much, yeah.

I like the idea of a separate library of stream combinators but yeah, there'd have to be some thought into best practices etc for extension libraries like that.

I'm going to close this, discussion about external modules etc makes more sense in a 3.0 thread.

There's already discussion happening in #3, #70 and #148.


ss_cat_enc_hex not working properly

Case:

ss_cat_enc_hex(&tgt, src)
src string size: 1  (checked both with heap and stack, same behaviour)

To do:

Fix the bug
Update the tests in order to catch that case

Fixed with: f957c75ffac88eb8ef683e5362d826e4840fac35


NerfStudio Google Colab Failing to download data

Attempting to download the dozer scene to train on the NerfStudio google colab demo, but I believe the data is missing.

Hi thanks for submitting the issue! I believe that error does not mean the dataset no longer exists (if you copy paste the google drive link it seems to still exist), there might be some issues with ns-download I'll look into it.
Just curious if you've tried with any other dataset?

Seems like the dozer dataset definitely exists (here). Have you used colab before? Seems like a colab error and I'm wondering if it's a new problem.


Cannot drag a view into an unopened viewpanecontainer

Move time line view to panel as a separate panel
Try to move time line view in panel into another panel (Problems?)  - Cannot

To Verify:

Move timeline into the panel (by itself)
Move outline into the panel (by itsefl)
Try to drag timeline into outline by hovering the outline title for a second and then dropping it inside the panel.


Added getStreamPos

This is equivalent to C's ftell function.

Even though its in the part that says DO NOT MODIFY in all caps?

Oops, didn't see that. You were right then, sorry.

Code looks great here, just a few minor problems.

Fixed

Thanks :)


Update dependencies to ensure a more recent version of tokio is used

This is required to address RUSTSEC-2021-0124.
Note well: the unit tests are currently broken, regardless of this patch.

Which unit tests are not working for you?

I get these failures also on the main branch:
running 1 test
test manifest::test::test ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 4.01s

     Running tests/ui.rs (target/debug/deps/ui-c5c54af9f3a3259b)

running 1 test

running 4 tests
test [ui] ui/state/require_transition_to.rs ... FAILED
test [ui] ui/state/require_same_object_state.rs ... FAILED
test [ui] ui/state/next_must_be_state.rs ... FAILED
test [ui] ui/state/cannot_construct_transition_next.rs ... FAILED

failures:

failures:
    [ui] ui/state/cannot_construct_transition_next.rs
    [ui] ui/state/next_must_be_state.rs
    [ui] ui/state/require_same_object_state.rs
    [ui] ui/state/require_transition_to.rs

test result: FAILED. 0 passed; 4 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.18s

test compile_test ... FAILED

failures:

---- compile_test stdout ----
diff of stderr:

diff of stderr:

-error[E0277]: the trait bound `TestState: TransitionTo<_>` is not satisfied
-  --> $DIR/require_transition_to.rs:38:9
+error[E0464]: multiple matching crates for `async_trait`
+  --> $DIR/require_transition_to.rs:3:1
    |
-LL |         Transition::next(self, TestState)
-   |         ^^^^^^^^^^^^^^^^ the trait `TransitionTo<_>` is not implemented for `TestState`
+LL | extern crate async_trait;
+   | ^^^^^^^^^^^^^^^^^^^^^^^^^
    |
-note: required by `Transition::<S>::next`
-  --> $SRC_DIR/src/state.rs:43:5
-   |
-LL | /     pub fn next<I: State<S>, O: State<S>>(_i: Box<I>, o: O) -> Transition<S>
-LL | |     where
-LL | |         I: TransitionTo<O>,
-   | |___________________________^
+   = note: candidates:
+           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so
+           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so

 error: aborting due to previous error

-For more information about this error, try `rustc --explain E0277`.
+For more information about this error, try `rustc --explain E0464`.

-error[E0277]: the trait bound `OtherState: krator::State<PodState>` is not satisfied
-  --> $DIR/require_same_object_state.rs:50:32
+error[E0464]: multiple matching crates for `async_trait`
+  --> $DIR/require_same_object_state.rs:3:1
    |
-LL |         Transition::next(self, OtherState)
-   |         ----------------       ^^^^^^^^^^ the trait `krator::State<PodState>` is not implemented for `OtherState`
-   |         |
-   |         required by a bound introduced by this call
+LL | extern crate async_trait;
+   | ^^^^^^^^^^^^^^^^^^^^^^^^^
    |
-   = help: the following implementations were found:
-             <OtherState as krator::State<OtherPodState>>
-note: required by `Transition::<S>::next`
-  --> $SRC_DIR/src/state.rs:43:5
-   |
-LL | /     pub fn next<I: State<S>, O: State<S>>(_i: Box<I>, o: O) -> Transition<S>
-LL | |     where
-LL | |         I: TransitionTo<O>,
-   | |___________________________^
+   = note: candidates:
+           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so
+           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so

 error: aborting due to previous error

-For more information about this error, try `rustc --explain E0277`.
+For more information about this error, try `rustc --explain E0464`.

The actual stderr differed from the expected stderr.
Actual stderr saved to /tmp/state/require_transition_to.stage-id.stderr
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args state/require_transition_to.rs`

error: 1 errors occurred comparing output.
status: exit status: 1
command: "rustc" "tests/ui/state/require_transition_to.rs" "-L" "/tmp" "--target=x86_64-unknown-linux-gnu" "--error-format" "json" "-C" "prefer-dynamic" "-o" "/tmp/state/require_transition_to.stage-id" "-A" "unused" "-Z" "ui-testing" "-L" "/home/flavio/hacking/kubernetes/krator/target/debug/deps" "-L" "/home/flavio/hacking/kubernetes/krator/target/debug" "-L" "/home/flavio/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-L" "/home/flavio/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib" "--edition=2018" "-L" "/tmp/state/require_transition_to.stage-id.aux"
stdout:
------------------------------------------

------------------------------------------
stderr:
------------------------------------------
{"message":"multiple matching crates for `async_trait`","code":{"code":"E0464","explanation":"The compiler found multiple library files with the requested crate name.\n\nThis error can occur in several different cases -- for example, when using\n`extern crate` or passing `--extern` options without crate paths. It can also be\ncaused by caching issues with the build directory, in which case `cargo clean`\nmay help.\n"},"level":"error","spans":[{"file_name":"tests/ui/state/require_transition_to.rs","byte_start":84,"byte_end":109,"line_start":3,"line_end":3,"column_start":1,"column_end":26,"is_primary":true,"text":[{"text":"extern crate async_trait;","highlight_start":1,"highlight_end":26}],"label":null,"suggested_replacement":null,"suggestion_applicability":null,"expansion":null}],"children":[{"message":"candidates:\ncrate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so\ncrate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so","code":null,"level":"note","spans":[],"children":[],"rendered":null}],"rendered":"error[E0464]: multiple matching crates for `async_trait`\n  --> tests/ui/state/require_transition_to.rs:3:1\n   |\nLL | extern crate async_trait;\n   | ^^^^^^^^^^^^^^^^^^^^^^^^^\n   |\n   = note: candidates:\n           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so\n           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so\n\n"}
{"message":"aborting due to previous error","code":null,"level":"error","spans":[],"children":[],"rendered":"error: aborting due to previous error\n\n"}
{"message":"For more information about this error, try `rustc --explain E0464`.","code":null,"level":"failure-note","spans":[],"children":[],"rendered":"For more information about this error, try `rustc --explain E0464`.\n"}

------------------------------------------

The actual stderr differed from the expected stderr.
Actual stderr saved to /tmp/state/require_same_object_state.stage-id.stderr
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args state/require_same_object_state.rs`

error: 1 errors occurred comparing output.
status: exit status: 1
command: "rustc" "tests/ui/state/require_same_object_state.rs" "-L" "/tmp" "--target=x86_64-unknown-linux-gnu" "--error-format" "json" "-C" "prefer-dynamic" "-o" "/tmp/state/require_same_object_state.stage-id" "-A" "unused" "-Z" "ui-testing" "-L" "/home/flavio/hacking/kubernetes/krator/target/debug/deps" "-L" "/home/flavio/hacking/kubernetes/krator/target/debug" "-L" "/home/flavio/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-L" "/home/flavio/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib" "--edition=2018" "-L" "/tmp/state/require_same_object_state.stage-id.aux"
stdout:
------------------------------------------

------------------------------------------
stderr:
------------------------------------------
{"message":"multiple matching crates for `async_trait`","code":{"code":"E0464","explanation":"The compiler found multiple library files with the requested crate name.\n\nThis error can occur in several different cases -- for example, when using\n`extern crate` or passing `--extern` options without crate paths. It can also be\ncaused by caching issues with the build directory, in which case `cargo clean`\nmay help.\n"},"level":"error","spans":[{"file_name":"tests/ui/state/require_same_object_state.rs","byte_start":74,"byte_end":99,"line_start":3,"line_end":3,"column_start":1,"column_end":26,"is_primary":true,"text":[{"text":"extern crate async_trait;","highlight_start":1,"highlight_end":26}],"label":null,"suggested_replacement":null,"suggestion_applicability":null,"expansion":null}],"children":[{"message":"candidates:\ncrate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so\ncrate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so","code":null,"level":"note","spans":[],"children":[],"rendered":null}],"rendered":"error[E0464]: multiple matching crates for `async_trait`\n  --> tests/ui/state/require_same_object_state.rs:3:1\n   |\nLL | extern crate async_trait;\n   | ^^^^^^^^^^^^^^^^^^^^^^^^^\n   |\n   = note: candidates:\n           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so\n           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so\n\n"}
{"message":"aborting due to previous error","code":null,"level":"error","spans":[],"children":[],"rendered":"error: aborting due to previous error\n\n"}
{"message":"For more information about this error, try `rustc --explain E0464`.","code":null,"level":"failure-note","spans":[],"children":[],"rendered":"For more information about this error, try `rustc --explain E0464`.\n"}

------------------------------------------

diff of stderr:

-error[E0277]: the trait bound `NotState: krator::State<PodState>` is not satisfied
-  --> $DIR/next_must_be_state.rs:39:32
+error[E0464]: multiple matching crates for `async_trait`
+  --> $DIR/next_must_be_state.rs:3:1
    |
-LL |         Transition::next(self, NotState)
-   |         ----------------       ^^^^^^^^ the trait `krator::State<PodState>` is not implemented for `NotState`
-   |         |
-   |         required by a bound introduced by this call
+LL | extern crate async_trait;
+   | ^^^^^^^^^^^^^^^^^^^^^^^^^
    |
-note: required by `Transition::<S>::next`
-  --> $SRC_DIR/src/state.rs:43:5
-   |
-LL | /     pub fn next<I: State<S>, O: State<S>>(_i: Box<I>, o: O) -> Transition<S>
-LL | |     where
-LL | |         I: TransitionTo<O>,
-   | |___________________________^
+   = note: candidates:
+           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so
+           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so

 error: aborting due to previous error

-For more information about this error, try `rustc --explain E0277`.
+For more information about this error, try `rustc --explain E0464`.

The actual stderr differed from the expected stderr.
Actual stderr saved to /tmp/state/next_must_be_state.stage-id.stderr
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args state/next_must_be_state.rs`

error: 1 errors occurred comparing output.
status: exit status: 1
command: "rustc" "tests/ui/state/next_must_be_state.rs" "-L" "/tmp" "--target=x86_64-unknown-linux-gnu" "--error-format" "json" "-C" "prefer-dynamic" "-o" "/tmp/state/next_must_be_state.stage-id" "-A" "unused" "-Z" "ui-testing" "-L" "/home/flavio/hacking/kubernetes/krator/target/debug/deps" "-L" "/home/flavio/hacking/kubernetes/krator/target/debug" "-L" "/home/flavio/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-L" "/home/flavio/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib" "--edition=2018" "-L" "/tmp/state/next_must_be_state.stage-id.aux"
stdout:
------------------------------------------

------------------------------------------
stderr:
------------------------------------------
{"message":"multiple matching crates for `async_trait`","code":{"code":"E0464","explanation":"The compiler found multiple library files with the requested crate name.\n\nThis error can occur in several different cases -- for example, when using\n`extern crate` or passing `--extern` options without crate paths. It can also be\ncaused by caching issues with the build directory, in which case `cargo clean`\nmay help.\n"},"level":"error","spans":[{"file_name":"tests/ui/state/next_must_be_state.rs","byte_start":70,"byte_end":95,"line_start":3,"line_end":3,"column_start":1,"column_end":26,"is_primary":true,"text":[{"text":"extern crate async_trait;","highlight_start":1,"highlight_end":26}],"label":null,"suggested_replacement":null,"suggestion_applicability":null,"expansion":null}],"children":[{"message":"candidates:\ncrate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so\ncrate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so","code":null,"level":"note","spans":[],"children":[],"rendered":null}],"rendered":"error[E0464]: multiple matching crates for `async_trait`\n  --> tests/ui/state/next_must_be_state.rs:3:1\n   |\nLL | extern crate async_trait;\n   | ^^^^^^^^^^^^^^^^^^^^^^^^^\n   |\n   = note: candidates:\n           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so\n           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so\n\n"}
{"message":"aborting due to previous error","code":null,"level":"error","spans":[],"children":[],"rendered":"error: aborting due to previous error\n\n"}
{"message":"For more information about this error, try `rustc --explain E0464`.","code":null,"level":"failure-note","spans":[],"children":[],"rendered":"For more information about this error, try `rustc --explain E0464`.\n"}

------------------------------------------

diff of stderr:

-error[E0451]: field `state` of struct `StateHolder` is private
-  --> $DIR/cannot_construct_transition_next.rs:26:9
+error[E0464]: multiple matching crates for `async_trait`
+  --> $DIR/cannot_construct_transition_next.rs:3:1
    |
-LL |         state: Box::new(Stub),
-   |         ^^^^^^^^^^^^^^^^^^^^^ private field
+LL | extern crate async_trait;
+   | ^^^^^^^^^^^^^^^^^^^^^^^^^
+   |
+   = note: candidates:
+           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so
+           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so

 error: aborting due to previous error

-For more information about this error, try `rustc --explain E0451`.
+For more information about this error, try `rustc --explain E0464`.

The actual stderr differed from the expected stderr.
Actual stderr saved to /tmp/state/cannot_construct_transition_next.stage-id.stderr
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args state/cannot_construct_transition_next.rs`

error: 1 errors occurred comparing output.
status: exit status: 1
command: "rustc" "tests/ui/state/cannot_construct_transition_next.rs" "-L" "/tmp" "--target=x86_64-unknown-linux-gnu" "--error-format" "json" "-C" "prefer-dynamic" "-o" "/tmp/state/cannot_construct_transition_next.stage-id" "-A" "unused" "-Z" "ui-testing" "-L" "/home/flavio/hacking/kubernetes/krator/target/debug/deps" "-L" "/home/flavio/hacking/kubernetes/krator/target/debug" "-L" "/home/flavio/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-L" "/home/flavio/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib" "--edition=2018" "-L" "/tmp/state/cannot_construct_transition_next.stage-id.aux"
stdout:
------------------------------------------

------------------------------------------
stderr:
------------------------------------------
{"message":"multiple matching crates for `async_trait`","code":{"code":"E0464","explanation":"The compiler found multiple library files with the requested crate name.\n\nThis error can occur in several different cases -- for example, when using\n`extern crate` or passing `--extern` options without crate paths. It can also be\ncaused by caching issues with the build directory, in which case `cargo clean`\nmay help.\n"},"level":"error","spans":[{"file_name":"tests/ui/state/cannot_construct_transition_next.rs","byte_start":70,"byte_end":95,"line_start":3,"line_end":3,"column_start":1,"column_end":26,"is_primary":true,"text":[{"text":"extern crate async_trait;","highlight_start":1,"highlight_end":26}],"label":null,"suggested_replacement":null,"suggestion_applicability":null,"expansion":null}],"children":[{"message":"candidates:\ncrate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so\ncrate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so","code":null,"level":"note","spans":[],"children":[],"rendered":null}],"rendered":"error[E0464]: multiple matching crates for `async_trait`\n  --> tests/ui/state/cannot_construct_transition_next.rs:3:1\n   |\nLL | extern crate async_trait;\n   | ^^^^^^^^^^^^^^^^^^^^^^^^^\n   |\n   = note: candidates:\n           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-bb76eb0106e5175e.so\n           crate `async_trait`: /home/flavio/hacking/kubernetes/krator/target/debug/deps/libasync_trait-d7fb65c29a022f39.so\n\n"}
{"message":"aborting due to previous error","code":null,"level":"error","spans":[],"children":[],"rendered":"error: aborting due to previous error\n\n"}
{"message":"For more information about this error, try `rustc --explain E0464`.","code":null,"level":"failure-note","spans":[],"children":[],"rendered":"For more information about this error, try `rustc --explain E0464`.\n"}

------------------------------------------

thread 'compile_test' panicked at 'Some tests failed', /home/flavio/.cargo/git/checkouts/compiletest-rs-346efcee5beef3c0/1fed013/src/lib.rs:105:22
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    compile_test

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.25s

I'm using rust nightly on linux, I just installed it via rustup

We can ignore the UI tests. rustc keeps changing the output, I will fix that in a separate PR

BTW, once you're fine with the changes I'll squash everything into a single commit


Fix Parsing Issue for ISONE LMP

Fixes a parsing issue for ISONE introduced in https://github.com/kmax12/gridstatus/pull/409

None of the get_lmp tests currently fail on main, which is how this error got through. I will write a test that fails on main but passes with these changes once I figure out the circumstances under which the error occurs.


Video+array utils

Adds array_utils and video_utils that are used within the registration capsule but are generally useful

Those functions are taken from the ophys_etl_pipelines, thus have already been vetted. How do I "open a ticket to remove the test_example.py", and why not just remove it myself?

Those functions are taken from the ophys_etl_pipelines, thus have already been vetted. How do I "open a ticket to remove the test_example.py", and why not just remove it myself?

To open a ticket, you can click on the Issues tab and click the green New Issue button on the upper right.
It's up to you if you want to remove it here. My usual workflow is to have a one-to-one correspondence between a PR and a ticket in the Issues column. If I see something that's outside the scope of the original issue, I'll try to open a new ticket. For larger software projects with a dedicated QA team, it helps them know which Issues are being resolved with the latest changes and what to look out for when they test things. Also, sometimes seemingly simple things can spiral into a rabbit hole and block the fix for the original issue.


qiita webserver start should error nicely when the cluster hasn't been started

When running qiita webserver start and the IPython cluster hasn't been started a traceback is shown on screen. The desired behavior is to have a message indicating what's wrong.

Should this be here or in moi?
cc @wasade

Likely moi

I think it should be in both places so qiita has nice errors not based on imports.

I still think just moi for the sake of separation of concerns. qiita can catch an exception by moi, but I do not see a need for qiita to have direct interaction with compute subsystem.

Currently, if the ipcluster is down, it will fail like:
$ qiita pet webserver --no-build-docs start --port 5558
Unable to connect to ipcluster(s): qiita-test-local
Traceback (most recent call last):
  File "/home/qiita_test/qiita_main/scripts/qiita", line 31, in <module>
    from qiita_ware.context import system_call, ComputeError
  File "/home/qiita_test/qiita_main/qiita_ware/context.py", line 274, in <module>
    context = Dispatch()
  File "/home/qiita_test/qiita_main/qiita_ware/context.py", line 62, in __init__
    self.demo = Client(profile=ctx_default)
  File "/home/qiita_test/.virtualenvs/qiita_t/lib/python2.7/site-packages/IPython/parallel/client/client.py", line 411, in __init__
    with open(url_file) as f:
IOError: [Errno 2] No such file or directory: u'/home/qiita_test/.ipython/profile_qiita-test-local/security/ipcontroller-client.json'

which I think has all the info required to know what's going on.
BTW, if the cluster doesn't have more than 2 workers we get:
Traceback (most recent call last):
  File "/home/qiita_test/qiita_main/scripts/qiita", line 31, in <module>
    from qiita_ware.context import system_call, ComputeError
  File "/home/qiita_test/qiita_main/qiita_ware/context.py", line 274, in <module>
    context = Dispatch()
  File "/home/qiita_test/qiita_main/qiita_ware/context.py", line 69, in __init__
    'but you have %d' % workers)
ValueError: You need to have at least 2 IPython workers but you have 0

Thus, closing. If you want to improve this behavior please reopen and add what else will be needed. Thanks.


[Rust][Doc] Re-enable the building and copying of Rust documentation.

Closes #9217, #7743, #7744. This turns back on the documentation for the Rust bindings.

ping @jroesch

Hey any updates?

closing due to inactivity.


HTTP trace logs aren't working as expected

Description:
Entity body is missing. See below.

Ballerina code,
// A system module containing protocol access constructs
// Module objects referenced with 'http:' in code
import ballerina/http;
import ballerina/io;

# A service is a network-accessible API
# Advertised on '/hello', port comes from listener endpoint

http:Client client1 = new("http://localhost:8601/endpoint1");
http:Client client2 = new("http://localhost:8602/endloint2");

service clone on new http:Listener(9090) {

    // http:Client client1 = new("http://localhost:8601/endpoint1");
    // http:Client client2 = new("http://localhost:8602/endloint2");

    # A resource is an invokable API method
    @http:ResourceConfig {
        body: "payload"
    }
    resource function aggregate(http:Caller caller, http:Request request, json payload) {

        json[] aggregatedResponse = cloneAndAggregate(<map<json>>payload, client1, client2);
        var res3 = caller->respond(<@untainted> aggregatedResponse);

        if (res3 is error) {
            io:println("Error in responding", res3);
        }
    }
}

function cloneAndAggregate(map<json> payload, http:Client clientEP1, http:Client clientEP2) returns @untainted json[] {
    map<json> callerPayload = payload.clone();

    fork {
        worker w1 returns json {
            payload["endpoint1"] = "endpoint1Value";
            return invokeEndpoint(clientEP1, payload);
        } worker w2 returns json {
            callerPayload["endpoint2"] = "endpoint2Value";
            return invokeEndpoint(clientEP2, callerPayload);
        }
    }
    record{json w1; json w2;} results = wait {w1, w2};

    json[] aggregatedResponse = [results.w1, results.w2];
    return aggregatedResponse;
}

function invokeEndpoint(http:Client clientEP, json outboundPayload) returns @tainted json {
    var inboundResponse = clientEP->post("/", outboundPayload);
    if (inboundResponse is http:Response) {
        var inboundPayload = inboundResponse.getJsonPayload();
        if (inboundPayload is json) {
            return inboundPayload;
        }
    }
    return {message: "error couldn't get the payload"};
}

Request
curl -v localhost:9090/clone/aggregate -H "Content-Type: application/json" -d "{\"key1\": \"value1\"}"

Backend
docker pull shafreen/netty_echo_server:latest

docker run -d -p 8601:8688 netty_echo_server
docker run -d -p 8602:8688 netty_echo_server

fixed with https://github.com/ballerina-platform/ballerina-lang/pull/18610


HOW

how create workflow for running trunk serve on github.io?

you don't - github actions are not persistent so running a web server in them would be pointless
here's a workflow that will use trunk build and then deploy to github pages.
https://github.com/dbalsom/fluxfox/blob/main/.github/workflows/deploy_ff_egui_app.yml


Consideration about the refactor of the code generation of sql model

There's always a need to modify the model code generated by goctl model during the dev process. But it's always slightly comfortable when modified the generated code.
Currently, I use this approach to alleviate this discomfort:
type FooModelEx interface {
	FooModel
	Bar(ctx context.Context,  whatever interface{}) (int64, error)
}

So far so good, and wouldn't it be better if we separated the interface from this file? This way we can extend the FooModel interface as we wish, and goctl can override the implementation of the interface at will without affecting the user experience.

This is a good proposal!

Sounds great! We'll discuss more on this.

Would you please describe what kind of scenarios that we need to re-generate the model?

We sometimes need to adjust the structure of the table, such as adding fields, modifying indexes, etc.
Such requirements are literally inevitable, especially when using a development model similar to prototype-driven.

I see, thanks!

Currently, the foomodel.go looks like:
type FooModel interface {
	Insert(ctx context.Context, data *Foo) (sql.Result, error)
	FindOne(ctx context.Context, foo string) (*Foo, error)
	...
}

type defaultFooModel {
}

Do you mean by moving FooModel interface to a separated file?
Thanks!

Could we change all the declarations in foomodel.go to private and generate a new model in a new file, as shown in the following code?
type FooModel interface {
	fooModel //private model interface
	Bar(ctx context.Context,  whatever interface{}) (int64, error)
}

@kevwan

This makes fewer changes and does not break the existing model.tpl structure.


B 18800 county with address response main

Agility ticket
Integration PR

Looks like the only difference is some example syntax. Ain't gonna worry about that. LGTM!

That was bugging me. Should be fixed now!


(#638) Revert server facts removal

@smortex I think this might help us with the discovery stuff, I dont find the meaning of \d now but I seem to recall it being some undocumented array match thing

This though will only work with the latest mcorpc support gem, so we need to be sure to update at the same time the modules data that installs that to grab the latest

I just did a few tests with puppet query… .match("\d+") on an array seems to do what we want here.  My understanding is that we do not know the index of the value of interest so we can't do facts.mcollective.server.collectives.0 = "%s" and this syntax with in is not valid: "%s" in facts.mcollective.server.collectives.


Speed up inverses of detector variances in shape fitting

Apparently, we can achieve a notable performance improvement by changing the current code:
const float sigma_squared_2D_inv = 1.0f / std::sqrt(sigma_squared_2D);
Mat Sigma = Mat::zeros(num_landmarks3, num_landmarks3, CV_32FC1);
for (int i = 0; i < num_landmarks3; ++i) {
    Sigma.at<float>(i, i) = sigma_squared_2D_inv; // the higher the sigma_squared_2D, the smaller the diagonal entries of Sigma will be
}
Mat Omega = Sigma.t() * Sigma; // just squares the diagonal

to
const float sigma_squared_2D_inv = 1.0f / sigma_squared_2D;
Mat Omega = Mat::zeros(num_landmarks3, num_landmarks3, CV_32FC1);
for (int i = 0; i < num_landmarks3; ++i) {
    Omega.at<float>(i, i) = sigma_squared_2D_inv; // the higher the sigma_squared_2D, the smaller the diagonal entries of Sigma will be
}

I haven't had a look at the code yet, but definitely need to. It's probably trivial.

I finally implemented this in e2809f13d163c3fd4b4e325a09cfd96a3a9d1153, the change is indeed trivial.
I believe a lot of further speed-up can probably be gained by switching to Eigen for these computations - the matrix multiplications and cv::solve are still somewhat slow in OpenCV.


do not return zero with minus-sign within range value, fixes #3221

looks good, I would add a simple comment of why this line exists like
"//avoid returning -0
On Fri, Jan 8, 2016 at 9:08 AM, Richard Nespithal<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/3277
Commit Summary

do not return zero with minus-sign within range value, fixes #3221

File Changes

M scene/gui/range.cpp
https://github.com/godotengine/godot/pull/3277/files#diff-0 (5)

Patch Links:

https://github.com/godotengine/godot/pull/3277.patch
https://github.com/godotengine/godot/pull/3277.diff

—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/3277.

looks good, I would add a simple comment of why this line exists like
"//avoid returning -0

+1

Looks good. Could you try merging the two commits into one? Using the git command-line, it would be:

git rebase -i HEAD~2
in the editor that shows up, replace the word "pick" before commit 3b11dc8 by "fixup", save and close the editor
it should then merge commit 3b11dc8 into its parent commit, git log should show only one commit
if the log is fine, git push -f origin 3221_range-minus-zero-fix to update this PR.

Thank you for the nice tutorial @akien-mga :wink: :yellow_heart:
Updated.

Perfect :)

This is still a problem in 2.14 stable when using float( )


Add placeholder support to

What it does?

if select.form-control has a placeholder attribute
adds a new first option with value="" and content from palceholder attribute
if there are no any option with "selected" attribute then also make first option selected
now select has a "placeholder" same color as .form-control::placeholder
Enjoy, welcome to 2016 and say good bye to "stackoverflow: how to add placeholder for select"

sass:
select.form-control[placeholder] option:first-child {
  color: $input-color-placeholder;
}

select.form-control[placeholder] option:not(first-child) {
  color: $input-color;
}

.placeholder {
  color: $input-color-placeholder;
}

and JS for side effects:

document.addEventListener('DOMContentLoaded', () => {
    document.getElementsByTagName('select').forEach((select) => {
        let placeholder = select.getAttribute('placeholder');
        if (placeholder !== null) {

            let selected = false;
            for (let k = 0; k < select.options.length; k++) {
                if (select.options[k].hasAttribute('selected')) {
                    selected = true;
                    break;
                }
            }

            let option = document.createElement('option');
            option.setAttribute('value', '');
            option.textContent = placeholder;
            select.insertBefore(option, select.firstChild);

            if (!selected) {
                select.selectedIndex = 0;
            }

            if (select.selectedIndex === 0) {
                select.classList.add('placeholder');
            } else {
                select.classList.remove('placeholder');
            }
            select.addEventListener('change', () => {
                if (select.selectedIndex === 0) {
                    select.classList.add('placeholder');
                } else {
                    select.classList.remove('placeholder');
                }
            });
        }
    });
});

If you will upvote this I'll make an ES5 version without my .forEach() added to many oldschool prototypes.

This JS is too brittle; it doesn't handle <select>s added to the DOM after the initial page load.

Well, in that case all the code block inside forEach can be an object and called via:
select = document.createElement('select');
...
BsSelect.init(select);

I admit that I'm not a fan of silently extending native elements this way. Particularly thinking about developers looking at code like <select placeholder="..." ...> in a bootstrapped site and assuming that this is standard behavior of <select>, copy-pasting it into their own (non-bootstrapped) projects, and then getting very confused about why it doesn't work. So, in the first instance, I'd rather see data-placeholder being used, as that more clearly signals that it's a non-standard attribute.
More generally, this still feels like something that would perhaps best be left to a 3rd party plugin, rather than as part of BS core, though my feelings aren't all that strong about that.

Further to brittleness of JS, does the code also handle situations where a <select> would be dynamically updated (for instance as a result of another control being changed/activated in the form)? e.g. a whole new set of <option>s being injected, and the data-placeholder attribute being modified dynamically?

Sounds like HTML already provides for a placeholder <option> for <select>s: https://html.spec.whatwg.org/multipage/#placeholder-label-option
Albeit, good luck styling it at present. However, once CSS Selectors Level 4 becomes a thing, seems like you could do:
.placeholder:checked /* are there really any browsers that allow styling <option>s? */
select:has(.placeholder:checked) {
  color: $input-color-placeholder;
}

@cvrebert my reading of that (slightly inpenetrable) wording is: if there <select> has a required attribute, and the first <option> in the list of options is empty <option></option>, then treat it as the placeholder and fail constraint validation (i.e. the user is required to select something other than that first empty <option></option>). this does not, to my understanding, say anything about specifying a non-empty <option> as being the placeholder, nor does it define any other way of giving the <select> a placeholder

oh, actually, strike that. reading further, it's the value that needs to be empty.
<select name="unittype" required>
 <option value=""> This would be the placeholder due to empty value </option>
 <option value="1"> ... </option>
 ...
</select>

So, it may be a case of using this instead then...

.placeholder:checked
This is only for options, not ; .placehodler class is needed only for  itself. When you set color on option, only dropdown item color is changed, not  selected item (dropdown closed).

You need to add .palceholder on  when 1st item is selected. CSS4 parent selectors is still far away from being a standard.
And yes, basic styles, like color, are allowed in any browser.
HTML, does not provide placeholder for option or select. It allows native required attribute to work with option with empty value.

@patrickhlauke

Further to brittleness of JS, does the code also handle situations where a  would be dynamically updated (for instance as a result of another control being changed/activated in the form)? e.g. a whole new set of s being injected, and the data-placeholder attribute being modified dynamically?

Any code is not a magic and will not cover all cases. If it is required to modify select with JS and as a result it will break placeholder, then you have to update it with provided BsSelect.init() or smth. The init() method can be extended to cover more cases.
Software engineers have to know and understand what they are doing not copy-pasting.

Not going to be adding custom JS to encourage/imply browser support for the placeholder attribute on <select>s, nor anything else that augments the first <option>.


update run length/issue frequency

closes #66

Tests are in fact passing although github has not updated. @wholmgren could you give this a quick?

Let's wait on this. I don't know if it's actually a change for the better.


Question about BAN

If we use this api login, the lat and lang all 0. Do you think that will make Niantic think we are Use of any other third-party software or app and make our account get soft ban or terminated?

It's detectable, and whether they ban you or not it at their discretion. I would think they have other ban targets in mind, as long as you don't really bot using this, but you can never be sure, and they would be in the right if they did so.

hmm.. i see


Fix bugs with slippage settings and improve user experience

After talking with @esteblock I saw he wants to emulate more closely the slippage config on Uniswap. This change accomplishes that and goes a little further making it easier for the user.
FYI: It depends on my previous PR which I accidentally left in the main branch.
Before
Previously when it opened the first time it was expanded and the wrong text.

Compare with Uniswap
https://github.com/soroswap/frontend/assets/165131835/e4c928e0-8d1b-4f0b-9b39-8f194bcaee13
After
https://github.com/soroswap/frontend/assets/165131835/ec22d858-9937-400f-98d8-cf1f67e00980

Specific details

By default when it opens it's in the auto state not showing the textbox yet
Fix toggling auto or custom
Make clicking and typing the slippage toggle to custom
Allow up down arrows with 0.1 increment and decrement
When opening the dialog and custom slippage focus and select allowing the user to quickly change it again.
Fix number formatting & connect better with state module

As an aside I couldn't figure out how to get the placeholder to dim like on other text boxes. Maybe someone can show me?


Fix code scanning alert - Shell command built from environment values

Tracking issue for:

[ ] https://github.com/agensdev/junit-summary-action/security/code-scanning/1

Fixed in https://github.com/agensdev/junit-summary-action/commit/7c29466d4e9b176532329745cf45858bef4f8d42


now saving the bib to cite.bib -- as required since Academic 4.4

the current version saves the bib with the name of the publication folder
since Academic 4.4, a cite button is only created for a cite.bib
see here:
https://sourcethemes.com/academic/updates/v4.4.0/#breaking-changes

Thanks for your contribution!


Update Storybook addon metadata

Hey ccpu! We've created a catalog of Storybook addons and yours is included: https://storybook.js.org/addons/storybook-addon-toolbar-actions
To make your addon more discoverable in the catalog, we've curated some of its metadata, and I've included those edits in this PR.
To learn more about the catalog metadata, check out our documentation: https://storybook.js.org/docs/react/addons/addon-catalog

Thanks!


CASMHMS-5894: Language linting of API spec

Summary and Scope
Linting of minor language issues in API spec file (spelling, punctuation, capitalization). No functional impact.
REMINDER: HAVE YOU INCREMENTED VERSION NUMBERS?
Yes
REMINDER 2: HAVE YOU UPDATED THE COPYRIGHT PER hpe GUIDELINES: (C) Copyright 2014-2021 Hewlett Packard Enterprise Development LP    ?
Yes
Issues and Related PRs

Resolves CASMHMS-5894
After this merges, will make a PR to the craycli repository to propagate the changes there

Testing
None -- all changes were to contents of text fields.
Risks and Mitigations
Very low risk.
HAS A SECURITY AUDIT BEEN RUN? (./runSnyk.sh)
No -- only contents of text fields have changed.
ARE THERE KNOWN ISSUES WITH THESE CHANGES?
No
ANY OTHER SPECIAL CONSIDERATIONS?
No

I'm assuming those checks are failing because I made the PR from a fork. I did that since I don't have write access to the repo. I don't mind remaking the PR without the fork if you give me write access. No big deal either way.


Mysql2::Error: Table 'development.spree_taxonomy_translations' doesn't exist: SHOW FULL FIELDS FROM spree_taxonomy_translations

after run "bundle exec rails g spree_static_content:install" command i have Mysql2::Error: Table 'development.spree_taxonomy_translations' doesn't exist: SHOW FULL FIELDS FROM spree_taxonomy_translations

Same problem here..

same issue here......

/home/tim/.rvm/gems/ruby-2.6.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:131:in _query': Table 'fairshopping_development.spree_taxon_translations' doesn't exist (Mysql2::Error)`
somehow embarassing. it's a year... gg


Running checkhealth returns error about CLI version

distant: require("distant.health").check()

distant.nvim ~
- OK distant installed
- ERROR unable to retrieve distant CLI version

This is my output from :checkhealth distant
Help!

Running distant help outputs the following:
./distant: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./distant)
./distant: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./distant)
./distant: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./distant)

Yeah, the newer version of the Rust compiler used seems to also require a more recent version of glibc. An alternative you can pursue is to instead install the musl version on linux.
See discussion here: https://github.com/chipsenkbeil/distant.nvim/issues/118


[BUG] fatal: unable to access 'https://git.rancher.io/charts/': Could not resolve host: git.rancher.io

Rancher Server Setup

Rancher version: rancher version v2.7.3 (bbba80e2a)
Installation option (Docker install/Helm Chart): Docker Install

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details: no-certs

Information about the Cluster

Kubernetes version:
Cluster Type (Local/Downstream): Local

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Admin

If custom, define the set of permissions:

Describe the bug

Error in rancher server container logs while booting up single node cluster with docker on ubuntu
To Reproduce

Spin an EC2 instance in private VPC and run below command
docker run -d --restart=unless-stopped  -p 80:80 -p 443:443   --privileged   rancher/rancher:latest
Result
Able to access UI but when trying to get kubectl shell, Not able to get shell access.
2023/05/23 02:13:03 [ERROR] error syncing 'helm3-library': handler catalog: Clone failed: Cloning into 'management-state/catalog-cache/f341cfdfa521a9aa2b993cb34b26bb91b2d173ef1a7df8d41b8921b0e4f82788'...
fatal: unable to access 'https://git.rancher.io/helm3-charts/': Could not resolve host: git.rancher.io
Expected Result

I should be able to access kubectl shell from rancher UI. Docker logs should no show error for git.rancher.io dns
Screenshots

Additional context

Below command fails when run in the container
d8b03c0544d4:/var/lib/rancher # git clone https://git.rancher.io/charts && cd charts && git ls-remote
Cloning into 'charts'...
fatal: unable to access 'https://git.rancher.io/charts/': Could not resolve host: git.rancher.io

content of /etc/resolve.conf
d8b03c0544d4:/var/lib/rancher # cat /etc/resolv.conf
nameserver <IP_ADDRESS>
search ec2.internal

docker info
Client: Docker Engine - Community
 Version:    24.0.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.10.4
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.18.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 2
  Running: 1
  Paused: 0
  Stopped: 1
 Images: 3
 Server Version: 24.0.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
 runc version: v1.1.7-0-g860f061
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.19.0-1025-aws
 Operating System: Ubuntu 22.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 7.664GiB
 Name: ip-10-42-2-53
 ID: 545e9370-0de6-4d34-ae26-c529ab1d4bf5
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

I had to add <IP_ADDRESS> manually in /etc/resolve.conf to be able to get out of the error. but the default installation worked earlier on a different ec2 instance in different aws account


Update to 3.0.2 breaks working installation

Upgrading to v3.0.2 breaks my working webrtc installation.
ERROR: NotSupportedIssue: Failed to execute 'addSourceBuffer' on 'MediaSource': The type provided ('video/mp4; codecs="undefined") is unsupported.
Reverting back to v3.0.1 fixes the issue.
Log file:
2023-02-02 22:36:24.201 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 145, in handle
result = await result
File "/config/custom_components/webrtc/init.py", line 204, in get
await ws_server.prepare(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_ws.py", line 138, in prepare
payload_writer = await super().prepare(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py", line 421, in prepare
return await self._start(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py", line 429, in _start
await self._write_headers()
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py", line 502, in _write_headers
await writer.write_headers(status_line, self._headers)
File "/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py", line 131, in write_headers
self._write(buf)
File "/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py", line 76, in _write
raise ConnectionResetError("Cannot write to closing transport")
ConnectionResetError: Cannot write to closing transport

Show screen with NotSupportedIssue


Node 8 and async/await?

Any plans to upgrade for that?

@demiters this is my setup in package.json
"engines": {
    "node": "8.1.4",
    "npm": "5.2.0"
  }

You can start to use async and await and you should have no issues.

Closed with https://github.com/bertho-zero/react-redux-universal-hot-example/pull/330


Implement "Share" Sharing

Share relationship created. Additional functionality needs to be built out in the future (Ex: After the relationship is created, refactor the gets to retrieve and display shared entities.


Fix code example in the guide

Closes #1187

r? @wycats
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+ 04404d1

:hourglass: Testing commit 04404d1 with merge 3fe1a10...

:broken_heart: Test failed - cargo-win-32

@bors: retry
On Mon, Jan 19, 2015 at 6:12 PM, bors<EMAIL_ADDRESS>wrote:

[image: :broken_heart:] Test failed - cargo-win-32
http://buildbot.rust-lang.org/builders/cargo-win-32/builds/761
—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/cargo/pull/1196#issuecomment-70583505.

:hourglass: Testing commit 04404d1 with merge 9fcc370...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64


enhancements for the terminal code

add more comments
include CI/CD through travis.
remove getpass for travis.

no needed


Update reading-time.mdx

Description (required)

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

en/recipes/reading-time.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳.

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.


Black screen below tab bar on left or right scroll

I am seeing a black screen below the tab bar when I scroll  to the left or right beyond the visible portion of screen.
In other words, (because it's hard to explain this) I keep on scrolling left and I see this black screen below tabBar.
Any idea what's happening?

Same case here. To work properly I manually set background color in master ViewController wich extends ButtonBarPagerTabStripViewController.

Hi @kishykumar
The problem is that when the buttonBarView is scrolled to its limits, the background is shown. This means that the black color you are seeing is the backgroundColor of the view in the container viewController (the class that implements ButtonBarPagerTabStripViewController).
Setting the background color of the view in the viewController to the same background color of the tabs should do the trick.
Hope it helps! Regards,


fix stats calculator lost column statistics on limit node

Proposed changes
select avg(id) from (select id from t1 limit 1);
above sql encounters NPE, because stats for limit node lost column statistics
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.98 seconds
load time: 488 seconds
storage size:<PHONE_NUMBER>3 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221202085533_clickbench_pr_56744.html


data source on web admin throws and error

Hi,
When i installed it, everything went fine but going to the data source section between server and web throws an error, I can still get the data source in the server section but web errors out.
One other question I did have is, would it be possible to expand a little on the deployment side? When i try and deploy out it overwrites the settings each time, like its deploying a new instance of Lucee each time.
Thanks!

 This is known behavior no matter what type of app you are deploying there.
It is recommended to run your app locally with foreman, make any necessary changes there, and then deploy so that these changes will be there each time you app spins up.
Regarding the datasource issue, that is more of a Lucee issue than an issue with this project. I suspect (although haven't confirmed) that working on your project locally and setting up datasources there may also remedy this. If you continue to have issues, you may also want to look into the "official" Lucee deployment pack for Heroku found here: https://github.com/lucee/lucee-heroku/
Hope that helps.


Change directory for StyleTransfer example

Codecov Report

Merging #1182 (4ea4d9d) into master (7f545ab) will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1182      +/-   ##
============================================
+ Coverage     70.18%   70.19%   +0.01%
- Complexity     4963     4965       +2
============================================
  Files           476      476
  Lines         21952    21952
  Branches       2318     2318
============================================
+ Hits          15406    15409       +3
+ Misses         5336     5335       -1
+ Partials       1210     1208       -2

Impacted Files
Coverage Δ

...mark/src/main/java/ai/djl/benchmark/Arguments.java
87.82% <0.00%> (+0.64%)
:arrow_up:

.../main/java/ai/djl/benchmark/AbstractBenchmark.java
91.01% <0.00%> (+1.19%)
:arrow_up:

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 7f545ab...4ea4d9d. Read the comment docs.


refactor: integrating off-dart 1.30.1

Impacted files:

background_task_details.dart: minor refactoring
background_task_image.dart: minor refactoring
background_task_refresh_later.dart: minor refactoring
country_selector.dart: minor refactoring
new_product_page.dart: minor refactoring
ocr_packaging_helper.dart: minor refactoring
offline_data_page.dart: now using an explicit api version
ordered_nutrients_cache.dart: minor refactoring
paged_search_product_query.dart: now using an explicit api version
paged_to_be_completed_product_query.dart: now using an explicit api version
Podfile.lock: wtf
product_image_data.dart: minor refactoring
product_list.dart: minor refactoring
product_list_import_export.dart: now using an explicit api version
product_list_page.dart: now using an explicit api version
product_query.dart: explicit api version
product_query_page.dart: minor refactoring
product_refresher.dart: now using an explicit api version
products_preload_helper.dart: now using an explicit api version
app/pubspec.lock: wtf
smooth_app/pubspec.lock: wtf
pubspec.yaml: upgraded off-dart version to 1.30.1
up_to_date_changes.dart: minor refactoring

What

Upgraded to off-dart 1.30.1
Mainly it was about

field "packaging" that got deprecated
field "offTag" that replaced custom tags
setting a specific api version (v2)

We cannot set v3 yet because of a pending bug (cf. https://github.com/openfoodfacts/openfoodfacts-dart/issues/617#issuecomment-1365356459). Meanwhile, we'll have to tap dance if we want to use the new packagings instead of the old packaging.
Perhaps we should make api_version mandatory in off-dart 2.0.0, for more clarity.

Codecov Report

Merging #3471 (5e487ee) into develop (9c9b93b) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##           develop    #3471   +/-   ##
========================================
  Coverage    11.18%   11.18%
========================================
  Files          261      261
  Lines        12668    12668
========================================
  Hits          1417     1417
  Misses       11251    11251

Impacted Files
Coverage Δ

...th_app/lib/background/background_task_details.dart
0.00% <0.00%> (ø)

...ooth_app/lib/background/background_task_image.dart
0.00% <0.00%> (ø)

.../lib/background/background_task_refresh_later.dart
0.00% <0.00%> (ø)

...smooth_app/lib/data_models/product_image_data.dart
0.00% <0.00%> (ø)

...kages/smooth_app/lib/data_models/product_list.dart
1.26% <0.00%> (ø)

...smooth_app/lib/data_models/up_to_date_changes.dart
0.00% <ø> (ø)

...pers/data_importer/product_list_import_export.dart
0.00% <ø> (ø)

...ckages/smooth_app/lib/pages/offline_data_page.dart
0.91% <ø> (ø)

...oth_app/lib/pages/onboarding/country_selector.dart
0.00% <0.00%> (ø)

...pp/lib/pages/product/common/product_list_page.dart
0.00% <ø> (ø)

... and 9 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


VS 201x and VS Code are not able to find real source with declarationMaps

TypeScript Version:  Version 3.0.0-dev
Search Terms:
goto definition F12
Code structure
BaseControl/source.ts
BaseControl/tsconfig.json
ButtonControl/source.ts
ButtonControl/tsconfig.json with "include": [ "../BaseClass/Source.d.ts"]
When I use in ButtonControl stuff from the BaseControl the code compiles and all Intellisense works.
But using "Goto Definition" F12 shows a small popup window: "No definition found for..."
Without using declarationMap:true F12 jumps to the Source.d.ts file.
Attached is a minimal example for VS Code
ts_navigation.zip
Related Issues:
Related to #25322 but this is typescript only (no gulp-sourcemaps involved)
@weswigham

@weswigham can you take a look.


Plugin broken

When I save my program containing:
		rows, err = tx.Query(ctx, /* sql */ `
			UPDATE clientips AS ips
			SET test_start = CASE -- keep test date, when the previous failed

the linter converts it to
		rows, err = tx.Query(ctx /* sql */, `
			UPDATE clientips AS ips
			SET test_start = CASE -- keep test date, when the previous failed

and so the highlighting is gone.

This should fix it:
https://github.com/antonnyman/vscode-go-sql-highlight/blob/92f829bf4c8d14b44e6a27249e907e905eb60cd9/syntaxes/go-sql-highlight.json#L7
"begin": "\\s*+(/\\* [sS][qQ][lL] \\*/)\\s*,?\\s*(`)",

P.S. Changing my code to
		rows, err = tx.Query(ctx,
			/* sql */ `
			UPDATE clientips AS ips
			SET test_start = CASE -- keep test date, when the previous failed

Also worked… I think it's a matter of personal taste.

Hi @Skeeve!
Thank you for submitting an issue, sorry I haven't responded.
I don't use this plugin daily anymore but I'm glad someone uses it!
Do you mind making a pull request with your changes?


Can't write to error/debug log

Operating System: 10.13.6
Vagrant Version: 2.2.1
Virtual Box Version: 5.2.30
trying to use error_log('here is something'); doesn't print anything where I would expect it. I can't find it any where. I have DEBUG_LOG set to true and I get nothing in debug.log. I have ssh'ed into the vagrant box and checked /var/log/apache2/gorton-test-access.log and /var/log/apache2/gorton-test-error.log neither have my updates in them.

never mind


Updating while the table is sorted corrupts data

System information:

Operating system (distribution) and version: Ubuntu 20.04
DBeaver version 22.1.3 CE
Additional extensions N/A

Connection specification:

Database name and version H2DB
Driver name JDBC
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
While the table is sorted, updating cells can corrupt the table:
I ordered by the first column and corrected the shop references(no keys) after the previous corruption and this is what I got:
https://ibb.co/KqsVB4D
But if I use a select from the console then I get this:
https://ibb.co/chP4kQt
Note that when I got all the rows with "shop2" the data in the first view has been saved and no error got thrown!
It just simply inserted "shop2" in every row. When I first loaded the data from a csv, sorted by the middle column and updated the last columns then it renamed all references of "shop2" to "shop1".
Steps to reproduce, if exist:
Have a simple table with 3 columns. Sort it and updating multiple cells at a time will corrupt the table sooner or later.

thanks for the report


Incorrect values after feeding power to the grid/total sum is negative.

Something is wrong here, as soon as the power sum is negative (pv feeds into the grid) some values like volts glitches. Can anyone reproduce this?

After a reboot its fine again, this need some debugging

And again:

Setting my Waveshare RS485 TO ETH No-Data-Reset like this, fixed it for me


Deployment - sign jars with gpg

Since the first release is in the near future we should also sign all deployed jars with maven-gpg-plugin to sign all of the project's attached artifacts with GnuPG.

small tutorial

reopened because the secure variables have not yet been provided and it is a must have for deploying a release version to maven central so I think testing this on a snapshot version might be a good choice.

added some description as a proposal in this comment


Libnd4j/Nd4j: ELU doesn't support alpha

The DL4J ActivationELU supports an alpha parameter, while the C++ and Java ops don't.  Ideally the op would support this and we wouldn't have to do the extra mul and replaceWhere ops.
https://github.com/SkymindIO/deeplearning4j/blob/00fd50cee21636113f5a4b5c56fbb39762185bb2/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/linalg/activations/impl/ActivationELU.java#L56-L92

Added recently
https://github.com/eclipse/deeplearning4j/blob/master/libnd4j/include/ops/declarable/generic/activations/elu.cpp


a missing '' in line 11

add ' ' to the end of line 11

This fix the syntax error but did not fix 'make distprep' option,  we might enable distprep option in the future. So this fix is okay.
The only issue is the commit message, we should follow the format. Please update the commit message before we merge it in. Thanks.
For example:
"HAWQ-224. Fix syntax error of make distprep."

Sorry, I mean the commit message title, it should include the JIRA number.


Fix corrupt patch

Applying: base: Don't use updatable apexes
Applying: bootscript: Disable uart logging
Applying: Disable AVB
Applying: bootscript: Use ab_test command
Applying: common: Add OTA-related packages
Applying: Fixes for OTA updates
Applying: u-boot: Expand userdata partition. Fixes unallocated space issue when single image install method is used
error: corrupt patch at line 74
Patch failed at 0009 u-boot: Expand userdata partition. Fixes unallocated space issue when single image install method is used
The line offset was wrong after I removed the echo...

Would you mind if I disable branch protection rules and squash it with 2 patches in the main? Not many people rely on this repo now, so nobody will be hurt.

Yes, I would have done the same thing

Done. Branch protection rules restored


Self-preservation mode logged and announced by JMX

A new schedule is generated to announce if the instance is in self-preservation using servo

NetflixOSS » eureka » eureka-pull-requests #577 SUCCESS
This pull request looks good

Servo can do probing automatically. Please, check how it is implemented in DiscoveryClient:
    @com.netflix.servo.annotations.Monitor(name = METRIC_REGISTRATION_PREFIX + "lastSuccessfulHeartbeatTimePeriod",
            description = "How much time has passed from last successful heartbeat", type = DataSourceType.GAUGE)
    private long getLastSuccessfulHeartbeatTimePeriodInternal() {
        long delay = getLastSuccessfulHeartbeatTimePeriod();
        heartbeatStalenessMonitor.update(computeStalenessMonitorDelay(delay));
        return delay;
    }

Can you reimplement it using this approach?

Hi!
I will assess this in the next days! The dedicated scheduler (plus polling) just for monitoring purposes looked a bit overkilling, but I thought may be the cleanest one until you presented this servo feature to me ;) . I will keep you posted,
 Daniel

NetflixOSS » eureka » eureka-pull-requests #582 FAILURE
Looks like there's a problem with this pull request

Hi,
I've been taking a look, and I guess we have two options:

discard this PR. I've been browsing the current metrics you are exporing, and bearing in mind the method "isBelowRenewThreshold" is also there, the additional metric this PR incorporates adds small value.

keep the suggested approach. Thanks to the additional schedule/thread, eureka will be logging if the instance is in self-preservation mode, or not. This could be interesting staff for admins. If we let servo to prove this, I understand the schedule (and the log generation) will be driven by external JMX polls, that does not look ideal. One point that can be interesting, though, is to log only transitions, instead of every renewalSelfPreservationStatusUpdateIntervalMs.
Thanks!

NetflixOSS » eureka » eureka-pull-requests #583 SUCCESS
This pull request looks good

@dcaba I propose to close this PR. As you have stated we have roughly equivalent metric already, and if we would like to implement this anyway, we should use servo annotations.


Add related examples to docs and website

Problem
There have been a few questions recently about layout related things in discord. Many of the questions can be answered easily by looking at one of the examples. We don't yet have VHS tapes / gifs of these linked in the README, and they're not linked in the docs / website.
Solution

[ ] Create any missing VHS tapes for each example - https://github.com/ratatui-org/ratatui/tree/main/examples/vhs
[ ] Create / update any out of date gifs and upload to the images branch
[ ] Add the example to the examples README
[ ] Link to the example from each relevant main widget / layout doc comment
[ ] Link to the examples from each relevant concept page in the website

In addition, I think layouts that are very common could use copy paste friendly docs on the website.

Related: https://github.com/ratatui-org/ratatui/issues/845, https://github.com/ratatui-org/ratatui/issues/1014

Related: #845, #1014

Ha, thanks past Joshka. :D