kube-runtime pulls in two versions of pin-project

Current and expected behavior
kube-runtime pulls in two distinct versions of pin-project & pin-project-lite:
:; cargo tree -d -i kube-runtime
pin-project v0.4.28
└── snafu v0.6.10
    └── kube-runtime v0.63.2

pin-project v1.0.8
├── kube-client v0.63.2
│   └── kube-runtime v0.63.2
├── kube-runtime v0.63.2
├── tower v0.4.10
│   └── kube-client v0.63.2 (*)
└── tower-http v0.1.2
    └── kube-client v0.63.2 (*)

pin-project-internal v0.4.28 (proc-macro)
└── pin-project v0.4.28 (*)

pin-project-internal v1.0.8 (proc-macro)
└── pin-project v1.0.8 (*)

When using tools like cargo-deny to audit dependencies, this requires an exemption like:
[bans]
multiple-versions = "deny"
# Wildcard dependencies are used for all workspace-local crates.
wildcards = "allow"
highlight = "all"
deny = []
skip-tree = []
skip = [
    # kube-runtime pulls in snafu v0.6, which pulls in an older version of pin-project
    { name = "pin-project", version = "0.4.28" },
    { name = "pin-project-internal", version = "0.4.28" },
]

I imagine this bloats compile times for packages that use kube-runtime, though I don't have hard numbers to back up this assumption.
Possible solution
I'd love it if we could drop the snafu dependency entirely, just to avoid the dependency. I know it offers some conveniences, but these seem surmountable, especially if we use thiserror for error definitions. thiserror is already pulled in by kube-client and kube-core.
Otherwise, it looks like there's a snafu v0.7 release in the works that hopefully resolves this?
Additionally, it may be valuable to use something like cargo-deny-action to audit duplicate/mismatched dependencies, license compliance, etc.
Additional context
No response
Environment
n/a
Configuration and features
:; cargo tree -p kube --depth=1
kube v0.63.2
├── k8s-openapi v0.13.1
├── kube-client v0.63.2
├── kube-core v0.63.2
├── kube-derive v0.63.2 (proc-macro)
└── kube-runtime v0.63.2

Affected crates
kube-runtime
Would you like to work on fixing this bug?
maybe

snafu was replaced by thiserror, so this should be fixed in the next release.

Additionally, it may be valuable to use something like cargo-deny-action to audit duplicate/mismatched dependencies, license compliance, etc.

We already have cargo-deny-action.
https://github.com/kube-rs/kube-rs/blob/519cc7b6332b059cf0c487d81f6d32e5579272a7/.github/workflows/ci.yml#L126
So we can configure to deny duplicate dependencies. PR to do that is welcomed.

snafu was replaced by thiserror (#686), so this should be fixed in the next release.

Do you think we are at a reasonable point to cut a new release at this time? We have a quite sizable CHANGELOG, but there are a couple of outstanding things that are possibly very close (hyper-rustls), and possibly something we might want to not split too much across releases (like error refinement).

duplicate dependencies check

I can play around with that.

I'd say the error stuff is relatively fine to split up. Especially if we ensure that any specific error types that we end up exposing to the public API are Into<kube::Error> (so that users don't need to opt into the more specific types if they don't want them).

Yeah, I've been trying to refine errors gradually per module (starting from lower level ones), so splitting across releases shouldn't be an issue. Any future refinements shouldn't be related to them.
All the higher level modules users use still returns kube::Error. Many variants were removed, and some were renamed/added. Because of how kube::Error has been, I think most users have catchall for the errors that have been changed.
The changelog is overwhelming, so we can add an overview to make the change easier to understand.

I think hyper-rustls will be released soon. They merged the PR we were waiting for, and opened a PR to release (https://github.com/rustls/hyper-rustls/pull/159).

Summary of changes to kube::Error:

Removed impl From<T> for Error
Removed Error::Connection (unused)
Removed Error::RequestBuild (unused)
Removed Error::RequestSend (unused)
Removed Error::RequestParse (unused)
Removed Error::InvalidUri (replaced by variants of errors in kube::config)
Removed Error::RequestValidation (replaced by variant of Error::BuildRequest)
Removed Error::Kubeconfig (replaced by Error::InferConfig, and Error::Auth)
Removed Error::ProtocolSwitch (ws only, replaced by Error::UpgradeConnection)
Removed Error::MissingUpgradeWebSocketHeader (ws only, replaced by Error::UpgradeConnection)
Removed Error::MissingConnectionUpgradeHeader (ws only, replaced by Error::UpgradeConnection)
Removed Error::SecWebSocketAcceptKeyMismatch (ws only, replaced by Error::UpgradeConnection)
Removed Error::SecWebSocketProtocolMismatch (ws only, replaced by Error::UpgradeConnection)
Added Error::Auth (errors related to client auth, some of them were previously under Error::Kubeconfig, confusingly)
Added Error::BuildRequest (errors building request from kube::core)
Added Error::InferConfig (for Client::try_default)
Added Error::OpensslTls (new openssl-tls feature)
Added Error::RustlsTls (rustls-tls feature)
Added Error::UpgradeConnection (ws feature, upgrade errors)

Fixed in 0.64.0.

@clux @kazk thanks!


Missing argument check

Hi,
The argument check isn't executed on the following line:
https://github.com/stackgl/gl-shader/blob/master/lib/create-attributes.js#L133
I would fix it, but I don't know where the result variable comes from a few lines below:
https://github.com/stackgl/gl-shader/blob/master/lib/create-attributes.js#L139
Best regards,
Agost

Yeah, that is a bug.  I can fix it tonight.

Thanks!
Mikola Lysenko<EMAIL_ADDRESS>schrieb am Di., 10. Nov. 2015
18:46:

Yeah, that is a bug. I can fix it tonight.
—
Reply to this email directly or view it on GitHub
https://github.com/stackgl/gl-shader/issues/8#issuecomment-155510482.


Modifies GraphSender to use Upload Session

I was receiving a Microsoft Graph API error when trying to use FluentEmail.Graph to send emails with attachments over 3MB. So, I created a fork of NatchEurope/FluentEmail.Graph that modifies the GraphSender to use an upload session for sending emails with attachments that are 3MB or larger.
Unfortunately, the Microsoft Graph API Send method does not have a SaveSentItems argument like the SendMail method does, so I had to remove the option to disable saving sent items. See Link 1, Link 2, and Link 3.
You probably won't want to merge this into your project since you will lose the SaveSentItems argument. But you can use/reference my code if you do decide to modify the project to use upload sessions. Or at the very least others can use my fork if they need to send emails with larger attachments.
I have opened issue #84

Hi, May I know, when will this PR get approved and a new package be available ?

Hi @Edwin2020 ,
Merging this would remove an existing feature "SaveSentItems"). So not an option for me.
Refactoring would allow both the original and the new 'upload session' without breaking existing implementations.
We need to implementations of the GraphSender.cs class. Is this something you want to take on?


Uncaught TypeError: plugin.projectButtons is not a function

[Enter steps to reproduce:]

right-clicking in the tree view,
don't know if i did anything out the ordinary

Atom: 1.14.2 ia32
Electron: 1.3.13
OS: Microsoft Windows 10 Pro
Thrown From: imdone-atom package 2.1.18
Stack Trace
Uncaught TypeError: plugin.projectButtons is not a function
At C:\Users\TildeMoose\.atom\packages\imdone-atom\lib\views\menu-view.coffee:103

TypeError: plugin.projectButtons is not a function
    at MenuView.module.exports.MenuView.addPluginProjectButtons (/packages/imdone-atom/lib/views/menu-view.coffee:103:85)
    at ImdoneAtomView.module.exports.ImdoneAtomView.addPluginProjectButtons (/packages/imdone-atom/lib/views/imdone-atom-view.coffee:317:41)
    at ImdoneAtomView.module.exports.ImdoneAtomView.addPluginButtons (/packages/imdone-atom/lib/views/imdone-atom-view.coffee:298:6)
    at /packages/imdone-atom/lib/views/imdone-atom-view.coffee:333:10
    at /packages/imdone-atom/lib/services/connector-manager.coffee:45:7
    at /packages/imdone-atom/lib/services/connector-manager.coffee:41:7
    at /packages/imdone-atom/lib/services/imdoneio-client.coffee:198:7
    at Request.callback (/packages/imdone-atom/node_modules/superagent/lib/node/index.js:619:12)
    at /packages/imdone-atom/node_modules/superagent/lib/node/index.js:795:18
    at /packages/imdone-atom/node_modules/superagent/lib/node/parsers/json.js:16:7)
    at emitNone (events.js:86:13)
    at Stream.emit (events.js:185:7)
    at /packages/imdone-atom/node_modules/superagent/lib/node/utils.js:112:12)
    at emitNone (events.js:91:20)
    at Unzip.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Commands
     -2:08.5.0 core:move-down (input.hidden-input)
     -2:07.8.0 core:confirm (input.hidden-input)
     -2:07.8.0 bookmarks:clear-bookmarks (input.hidden-input)
     -1:48.2.0 command-palette:toggle (input.hidden-input)
     -1:24.4.0 autocomplete-plus:activate (input.hidden-input)
     -1:21.6.0 command-palette:toggle (input.hidden-input)
     -1:16.7.0 autocomplete-plus:activate (input.hidden-input)
     -1:15.1.0 command-palette:toggle (input.hidden-input)
     -0:58.5.0 status-bar:toggle (input.hidden-input)
     -0:55.7.0 command-palette:toggle (input.hidden-input)
  2x -0:49.5.0 core:backspace (input.hidden-input)
     -0:46.1.0 status-bar:toggle (input.hidden-input)
     -0:39.5.0 linter:next-error (atom-workspace.workspace.scrollbars-visible-always.seti-icons.seti-roboto.seti-animate.theme-seti-syntax.theme-seti-ui)
  2x -0:37 go-to-line:toggle (atom-text-editor.editor)
     -0:29.1.0 tree-view:toggle-focus (ul.list-inline.tab-bar.inset-panel)
     -0:15.8.0 imdone-atom:tasks (span.name.icon.icon-repo)

Non-Core Packages
atom-beautify 0.29.17
atom-monokai 0.10.8
autoclose-html 0.23.0
color-picker 2.2.5
colorblind-wombat-dark-syntax 0.6.0
file-icons 2.0.15
git-plus 7.3.0
highlight-selected 0.12.0
imdone-atom 2.1.18
imdone-atom-github 0.1.11
linter 1.11.23
linter-csslint 1.3.3
linter-htmlhint 1.3.1
linter-jshint 3.0.2
linter-markdown 3.1.0
linter-shellcheck 1.4.3
minimap 4.26.8
minimap-bookmarks 0.4.2
minimap-cursorline 0.2.0
minimap-highlight-selected 4.5.0
monokai 0.22.0
pigments 0.39.0
ramda-syntax 0.12.0
Remote-FTP 0.10.5
seti-syntax 1.1.2
seti-ui 1.6.1
todo-show 1.10.0

[Enter steps to reproduce:]

Add List in Imdone
...

Atom: 1.14.4 x64
Electron: 1.3.13
OS: Mac OS X 10.12.3
Thrown From: imdone-atom package 2.1.21
Stack Trace
Uncaught TypeError: plugin.projectButtons is not a function
At /Users/rayk/.atom/packages/imdone-atom/lib/views/menu-view.coffee:103

TypeError: plugin.projectButtons is not a function
    at MenuView.module.exports.MenuView.addPluginProjectButtons (/packages/imdone-atom/lib/views/menu-view.coffee:103:85)
    at ImdoneAtomView.module.exports.ImdoneAtomView.addPluginProjectButtons (/packages/imdone-atom/lib/views/imdone-atom-view.coffee:317:41)
    at ImdoneAtomView.module.exports.ImdoneAtomView.addPluginButtons (/packages/imdone-atom/lib/views/imdone-atom-view.coffee:298:6)
    at ImdoneAtomView.module.exports.ImdoneAtomView.updateBoard (/packages/imdone-atom/lib/views/imdone-atom-view.coffee:610:6)
    at ImdoneAtomView.module.exports.ImdoneAtomView.onRepoUpdate (/packages/imdone-atom/lib/views/imdone-atom-view.coffee:411:6)
    at /packages/imdone-atom/lib/views/imdone-atom-view.coffee:168:8
    at Function.module.exports.Emitter.simpleDispatch (/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at PluginViewInterface.module.exports.Emitter.emit (/app.asar/node_modules/event-kit/lib/emitter.js:129:28)
    at /packages/imdone-atom/lib/views/imdone-atom-view.coffee:126:25)
    at emitOne (events.js:96:13)
    at Repository.emit (events.js:188:7)
    at fn (/packages/imdone-atom/node_modules/imdone-core/lib/repository.js:270:20)
    at _cb (/packages/imdone-atom/node_modules/imdone-core/lib/mixins/repo-fs-store.js:126:7)
    at /packages/imdone-atom/node_modules/graceful-fs/graceful-fs.js:43:10
    at /packages/linter-swagger/node_modules/graceful-fs/graceful-fs.js:43:10
    at FSReqWrap.oncomplete (fs.js:123:15)

Commands
     -1:25.4.0 tree-view:show (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-nord-atom-syntax.theme-nord-atom-ui)
     -1:16.2.0 imdone-atom:tasks (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)

Non-Core Packages
aligner-css 1.2.0
auto-update-packages 1.0.1
clock 1.9.0
cssfmt 1.4.0
date 1.2.2
file-icons 2.0.17
git-hide 1.0.0
git-log 0.4.1
git-plus 7.3.3
highlight-selected 0.12.0
imdone-atom 2.1.21
imdone-atom-github 0.1.11
ink 0.6.4
linter 1.11.23
linter-clojure 1.1.2
linter-swagger 0.3.9
linter-write-good 0.8.0
lisp-paredit 0.5.5
markdown-writer 2.6.4
minimap 4.26.8
minimap-highlight-selected 4.5.0
nord-atom-syntax 0.6.0
nord-atom-ui 0.10.2
Parinfer 1.17.0
pretty-json 1.6.1
proto-repl 1.4.16
proto-repl-charts 0.4.0
set-syntax 0.3.2
swackets 0.26.0
sync-settings 0.8.1
tablr 1.8.1
tool-bar 1.0.1
tree-view-git-status 1.3.1

READY: Fix gh:213 and gh:219 by checking for undefined id:142
CHANGELOG.md:2
@imdone commenter. The developer's task board. imdone.io

DONE: Fix gh:213 and gh:219 by checking for undefined id:142
CHANGELOG.md:2
@imdone Issue Closer. The developer's task board. imdone.io


Feat: Allow schema override in configuration for dbt projects

It felt to me like a load only value, so I'd prefer not to make the context
even more complicated. Fine with whatever you decide.
On Thu, Aug 3, 2023, 2:47 PM Iaroslav Zeigerman @.***>
wrote:

@.**** commented on this pull request.
In sqlmesh/dbt/loader.py
https://github.com/TobikoData/sqlmesh/pull/1259#discussion_r1283590774:

@@ -119,7 +122,11 @@ def _load_project(self) -> Project:
return self._project

     self._project = Project.load(

       DbtContext(project_root=self._context.path, target_name=self._context.gateway)

       DbtContext(

           project_root=self._context.path,

           target_name=self._context.gateway,

           schema_override=self._schema_override,

       )

Following the pattern of just passing the context everywhere. Can easily
change this to what you're suggesting
—
Reply to this email directly, view it on GitHub
https://github.com/TobikoData/sqlmesh/pull/1259#discussion_r1283590774,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQB5GWKHH3EHYMWALW6ZDCDXTPW4JANCNFSM6AAAAAA3DDZPI4
.
You are receiving this because your review was requested.Message ID:
@.***>

@crericha @tobymao I've realized that my initial approach is wrong. dbt has complex rules around resolving schemas for model and just simply overriding it for all models is wrong. What I actually want is to override the target schema only and let dbt figure out the rest.
Also to make sure that the manifest cache resets I now require users to override schema in the dbt_project.yaml instead of config.py.
Please revisit this PR.


[BUG]

[x] I've read the docs of nestjs-pino
[x] I've read the docs of pino and pino-http
[x] I couldn't find the same open issue of nestjs-pino
[x] This bug is related only to current library or I've tested the same behaviour with the built-in logger and this is not a bug of NestJS.

What is the current behavior?
In docker for each reload I see an error:

in dev env
What is the expected behavior?
no error
Please provide minimal example repo, not code snippet. Without example repo this issue will be closed.
https://github.com/serhbs/nestemplate
Please mention other relevant information such as Node.js version and Operating System.
Linux, Docker nodejs 18

https://stackoverflow.com/questions/4075287/node-express-eaddrinuse-address-already-in-use-kill-server

https://stackoverflow.com/questions/4075287/node-express-eaddrinuse-address-already-in-use-kill-server

and how it could help with the problem?


persistentVolumeClaim Disk supports qcow2 format

Is this a BUG REPORT or FEATURE REQUEST?:

/kind enhancement

What you expected to happen:
Currently the disk is also required to be in raw format, I want to reduce the disk image size,What should i do, ask for help.
Thanks in advance.

If it is a Windows vm, the win.img disk file is too large, Can someone give me some advice?

@awels @mhenriks maybe you have some ideas? I find it in general more and more appealing to also support qcow2. We have the security checks already in place for other volume types which support qcow2.

AFAIK the main reason we picked just raw is simplicity. Using one raw disk per PVC allows us to use k8s build in storage mechanisms like snapshotting instead of having to invent our own.
There is no reason you cannot have a sparse raw disk, so I am a little confused about the benefits of qcow2 with regards to disk space. We currently default to non sparse disks because most storage providers will give you a PVC of exactly the requested size and filling it completely when creating the disk makes sense. The notable exception is if you are using local storage (hostpath, local volume) type storage where everything is shared. It should be feasible to specify that you want sparse disks though.
@aglitke any other reasons for not supporting qcow2 disks?

@awels
I think when using thin-provisioning-block-device or cephfs pvc, the storage provider does not give all the requested size at once. But the backend storage will fill more and more until the requeseted size as using vm.
Thus qcow2 image may save more backend storage resources.


Dangerous environment variables being set

I noticed my node related commands showing unexpected output when run from terminals opened with this. Finally I found the reason. When you open a terminal from atom-terminal, you get these environment variables set:
ATOM_HOME=/home/user/.atom
GOOGLE_API_KEY=3h4kjhb4go9h4ntgwk
NODE_PATH=/usr/share/atom/resources/app.asar/exports
CHROME_DESKTOP=Atom.desktop
NODE_ENV=production

I don't know why this is done, but I understand that for a general use of a terminal at least GOOGLE_API_KEY ,NODE_PATH and NODE_ENV shouldn't be there. They can (and do) corrupt the terminal environment.

These come from the fact that atom sets them (some of them are needed for the apm modules I believe).
When we fork to start a terminal process these are just inherited. We could propably unset them explicitly, but I'm not sure thats the right approach.
Something similar came up in issue #13.

@tkw1536 Thanks! I got it working with (/bin/terminator is my weapon of choice):
    app: "/bin/bash"
    args: "-c 'unset NODE_ENV && unset NODE_PATH && /bin/terminator'"

@rubencaro Which file is that that you edited in your comment above?

@stevehanson none! That were just on the settings view inside atom.

@rubencaro thanks for the quick reply. I'm still not seeing those options. Are they in the global Atom settings, or the Terminal Status settings, or elsewhere? Thanks for the help :)

It's on atom-terminal own settings. app and args are the options.

OK. All I see is Window Height:

I'm brand new to Atom. Probably need to just spend a bit more time in it before asking these newb questions.

ok, I just found where I can edit the raw config.cson.


fix: Error Could not resolve "@nanostores/vue"

thanks for the PR! This should be fixed in the latest version. It should have been imported from the local store resolver instead.

I am still facing this issue in a Nuxt 3 application with Prisma
Could not resolve "@nanostores/vue"

I am still facing this issue in a Nuxt 3 application with Prisma Could not resolve "@nanostores/vue"

make sure you're on 0.8.1-beta.5


Syncing doesn't finish when there are build errors

Description of the bug:
We have a situation where the IntelliJ sync process "never finishes" when there are build errors in the Java code of our project. Well, the sync maybe finishes, but it just takes way too long due to excessive resource utilization. The way this manifests is in a stuck JetBrains Gateway or in a super-high IntelliJ memory consumption.
We have tracked this down to the BEP generated by Bazel being huge when there are build errors. In a normal sync for our project, the BEP that Bazel writes is a few hundred MBs big, but when the build fails, the BEP is several GBs in size. IntelliJ then chokes trying to process this output.
I compared the JSON BEP written with a good and a bad build and found that the bad build contains lots more progress and namedSet entries. For comparison, here is what a good build shows:
...
      3     "structuredCommandLine": {
  47424     "targetCompleted": {
  47424     "targetConfigured": {
 143851     "namedSet": {
 191278     "progress": {

and here is what a bad build shows:
...
      3     "structuredCommandLine": {
  47424     "targetCompleted": {
  47424     "targetConfigured": {
1255596     "namedSet": {
1303024     "progress": {

I wonder if #1167 is related to what we are seeing.
The theory in my head for the above is this: if we have two chains of actions A->B->C and A->B->D, and B fails to build, then the aspect will still try to generate data for C and D, but now the build failures of B are “accounted” towards the outputs of C and D. This results in extra progress messages and extra “outputs” via namedSet. Propagate this throughout our large tree and we end up with this issue blowing up the size of the BEP.
The problem only shows up when --keep_going and the plugin aspect are combined. It doesn't show up otherwise.
Which category does this issue belong to?
Intellij
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Introduce a Java compilation error in a project, probably in one of the base libraries of the build graph.
Which Intellij IDE are you using? Please provide the specific version.
JetBrains Gateway 2023.3.4
What programming languages and tools are you using? Please provide specific versions.
Java
What Bazel plugin version are you using?
2024.04.23-stable
Have you found anything relevant by searching the web?
See the description.
Any other information, logs, or outputs that you want to share?
No response

So unfortunately I can't reproduce it. Could you please try to catch a stacktrace next time it happens?

btw we recently found this https://github.com/bazelbuild/intellij/issues/6577


request issue

When use ner function, others work.
File "", line 1, in
File "/usr/local/lib/python3.5/dist-packages/stanfordcorenlp/corenlp.py", line 195, in ner
r_dict = self._request('ner', sentence)
File "/usr/local/lib/python3.5/dist-packages/stanfordcorenlp/corenlp.py", line 239, in _request
r_dict = json.loads(r.text)
File "/usr/lib/python3.5/json/init.py", line 319, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.5/json/decoder.py", line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Hello，
r_dict = self._request('ner', sentence)
====changed to ====>
r_dict = self._request(self.url,'ner', sentence)
may helps

@fangtanchen still getting this error

I am getting the same error.
/usr/local/python/3.7.0/Frameworks/Python.framework/Versions/3.7/lib/python3.7/json/decoder.py in raw_decode(self, s, idx)
    353             obj, end = self.scan_once(s, idx)
    354         except StopIteration as err:
--> 355             raise JSONDecodeError("Expecting value", s, err.value) from None
    356         return obj, end

JSONDecodeError: Expecting value: line 1 column 1 (char 0)

anybody solved it?

I got the same error when I use "word_tokenize()", and I finally find that it goes wrong when a "%" is in the sentence.
Then I find the same problem in https://github.com/stanfordnlp/CoreNLP/issues/1113


langchain-box: Add DocumentLoader

Thank you for contributing to LangChain!

[x] PR title: "package: description"

Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..."  for template changes, "infra: ..." for CI changes.
Example: "community: add foobar LLM"

Description:  Initial commit of the langchain-box package. This package includes:

langchain_box.document_loaders.BoxLoader —  a DocumentLoader for loading by files or folders
langchain_box.utilities.BoxAPIWrapper — a utilities file to encapsulate Box-specific code
langchain_box_utilities.BoxAuth —  an Authentication helper class to make authentication with Box as easy as possible
langchain_box_utilities.BoxAuthType —  an Enum to streamline using BoxAuth.

Twitter handle: @BoxPlatform

[x] Add tests and docs: If you're adding a new integration, please include

a test for the integration, preferably unit tests that do not rely on network access,
an example notebook showing its use. It lives in docs/docs/integrations directory.

[x] Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

Additional guidelines:

Make sure optional dependencies are imported within a function.
Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
Most PRs should not touch more than one package.
Changes should be backwards compatible.
If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.

Closing pull request and issuing a fresh one with suggested changes.


PHPUnit's clover format

Supporting clover format
Hello! PHPUnit has millions of users.
https://docs.phpunit.de/en/10.0/configuration.html#the-report-element
Can coverage-reporter read clover XML files?

Hey @szepeviktor! Right now coverage-reporter doesn't support clover XML reports but we are planning to add the support for it. If you want to speed it up, could you please share a repo I can use for testing (to create clover coverage report and parse it)? I'd appreciate it a lot.

@szepeviktor thanks for reaching out about this.
I believe Clover XML was next on our list of formats to add support for.
On that topic, though, I want to take the opportunity to point out that if anyone, including yourself, is willing to contribute a new format parser—per this message in the project README, which links to our Developer Guide for adding a new format parser—Coveralls is offering compensation in the form of one or more months of free service at Coveralls.io.
The same goes for supporting new CI services, which is pretty straighforward if you look at the currently supported CI modules here, and our docs on CI env vars.
Thanks 🙏


About the "model" module

from model.resnext import ReXNetV1
Hello, could you please clarify whether "model" is a folder or a package that needs to be installed? I am having trouble locating it. Thank you !

这是来自QQ邮箱的假期自动回复邮件。

您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。


remove script tags from drip code snippet on save

The script needs to be injected without the script tags - either remove on save or render if they have been included with the snippet

only inner content of script tag now injected


Add Connection#finished_request?

When using persistent connections there is no easy way to check if the entire body of the previous request has been consumed before sending a new request, e.g. if an exception was raised while reading the body.
Add Connection#finished? which does the same check as the guards in Connection#send_request.
https://github.com/httprb/http/blob/32a2ae68a1650d267f0687381d58880cf1b60315/lib/http/connection.rb#L69-L76

Thanks!


cmake linking error against pthread

This linking error happens on some platforms (e.g., Ubuntu 14.04 LTS, and RHEL Server 6.7), but both Mac OS X 10.11.1 and CentOS 7 works.
The main reason for such linking error is that CMakeLists.txt missed the link statement target_link_libraries(some_unittest ${CMAKE_THREAD_LIBS_INIT}), and I'll submit a pull request for this later.
But I don't know why some platforms fails; see the error logs below. I have checked $LD_LIBRARY_PATH, though.
On Ubuntu 14.04 LTS, logging_unittest linking fails.
CMakeFiles/logging_unittest.dir/src/logging_unittest.cc.o: In function `google::Thread::Start()':
logging_unittest.cc:(.text._ZN6google6Thread5StartEv[_ZN6google6Thread5StartEv]+0x26): undefined reference to `pthread_create'
CMakeFiles/logging_unittest.dir/src/logging_unittest.cc.o: In function `google::Thread::Join()':
logging_unittest.cc:(.text._ZN6google6Thread4JoinEv[_ZN6google6Thread4JoinEv]+0x1d): undefined reference to `pthread_join'
collect2: error: ld returned 1 exit status
make[2]: *** [logging_unittest] Error 1
make[1]: *** [CMakeFiles/logging_unittest.dir/all] Error 2
make: *** [all] Error 2

On RHEL Server 6.7, two unit tests (signalhandler_unittest and logging_unittest) have linking issues, but the rest 5 unit tests works.
[ 72%] Linking CXX executable signalhandler_unittest
[ 77%] Linking CXX executable stacktrace_unittest
CMakeFiles/signalhandler_unittest.dir/src/signalhandler_unittest.cc.o: In function `main':
signalhandler_unittest.cc:(.text+0x262): undefined reference to `pthread_create'
signalhandler_unittest.cc:(.text+0x273): undefined reference to `pthread_join'
collect2: ld returned 1 exit status
make[2]: *** [signalhandler_unittest] Error 1
make[1]: *** [CMakeFiles/signalhandler_unittest.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 77%] Built target stacktrace_unittest
[ 81%] Linking CXX executable demangle_unittest
[ 86%] Linking CXX executable symbolize_unittest
[ 90%] Linking CXX executable utilities_unittest
[ 90%] Built target demangle_unittest
[ 90%] Built target symbolize_unittest
[ 90%] Built target utilities_unittest
[ 95%] Linking CXX executable stl_logging_unittest
[ 95%] Built target stl_logging_unittest
[100%] Linking CXX executable logging_unittest
CMakeFiles/logging_unittest.dir/src/logging_unittest.cc.o: In function `google::Thread::Start()':
logging_unittest.cc:(.text._ZN6google6Thread5StartEv[google::Thread::Start()]+0x2a): undefined reference to `pthread_create'
CMakeFiles/logging_unittest.dir/src/logging_unittest.cc.o: In function `google::Thread::Join()':
logging_unittest.cc:(.text._ZN6google6Thread4JoinEv[google::Thread::Join()]+0x1d): undefined reference to `pthread_join'
collect2: ld returned 1 exit status
make[2]: *** [logging_unittest] Error 1
make[1]: *** [CMakeFiles/logging_unittest.dir/all] Error 2
make: *** [all] Error 2

There's already PR #51.

Oh, thanks. Please close this issue once #51 gets merged.

so bad the project glog.there is so many same problem in the issues.fuck you google.

@jianhuaixie This is an open source project which you can improve by contributing. You're not making any friends by using foul language.


Notification improvements

[ ] remove redundant channel stuff
[ ] consider using :ets

Pull Request Test Coverage Report for Build facfd4a128effe2e7fc6baea15807eef501ab6b4-PR-869

0 of 4 (0.0%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 68.145%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

apps/fz_http/lib/fz_http/notifications/errors.ex
0
2
0.0%

apps/fz_http/lib/fz_http_web/channels/notification_channel.ex
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

apps/fz_http/lib/fz_http/notifications/errors.ex
1
28.57%

apps/fz_http/lib/fz_http_web/channels/notification_channel.ex
1
66.67%

Totals

Change from base Build 8a0baed6a9b56913ab05ecd03a7b9f05790a2c4f:
0.0%

Covered Lines:
999

Relevant Lines:
1466

💛  - Coveralls


Feature : support .tool-versions for (nodejs, ruby, etc)

Hi,
A feature that would help maintenance : it would be nice to support .tool-versions (asdf) files like github actions.
For github actions, if  a key versionFile equals ".tool-versions" then the version to install is read from this file.
This would avoid multiple source of truth / conflicts.

Hi 👋
Thanks for the suggestion ✨
Instead of updating all the Features to support .tool-versions, we could propose this for the spec instead. Transferring this issue over to the spec repo, let me know if you have any concerns or additional thoughts.


[Enhancement]: Added rest of the CSS grid properties

What changes does this PR introduce?
In this PR the styles.go file is updated by adding the  grid-properties (mentioned below) following the MDN.
grid-auto-columns,
grid-auto-rows,
grid-column-gap,
grid-gap,
grid-row-gap,
grid-template-areas,
grid-template-columns,
grid-template-rows,

Fixes:
Issue #14

Awesome, thank you! Looks great. I just left a couple notes on a few that were deprecated for different syntax.

@chasefleming  thank you for your prompt review, I have made the suggested changes. Feel free to send more feedback if necessary.


Implement Edit Applicant Info Screen

Dependent on #500
Requirements:

Figma interface

Users should NOT be able to edit the applicant agency AND  location code

Users should NOT be able to edit the seedlot species

Users should be able to edit: The applicant email

Users should be able to edit: A-class source

Users should be able to edit: To be registered at the Tree Seed Centre

Users should be able to edit: Collected from a location within B.C.

The call to action button will allow users to Save edits

FYI, this feature will be used in B class seedlots, veglots

duplicate of #501


Tagger api support

First of all, amazing work on this lib! Thank you for the hard work.
Are there any plans on adding support for the tagger api?
https://tagger.scryfall.com/

What exactly would support for tagger entail? The Cards.search function is just Scryfall's full-text search exactly, so it supports everything described here afaik: https://scryfall.com/docs/tagger-tags

You are absolutely right, my bad on not doing my due diligence before reaching out...


Saving multiple versions of xgb models

Hi,
the small change below allows to save more than 1 version of the model (in the main xgb.train.R it is always overwritten).

@glr72 Thanks but some people might want to only save 1 version though. It would be better if, instead, you can add a parameter max_to_keep for the maximum number of recent models to keep. The idea is that people want to save only several versions of the recent models. I am open to other ideas though.

hi terrytangyuan,
I implemented your proposal. You have parameter max_to_keep (default = 0), which works as you suggested.

@glr72 Thank you. Could you squash your commits into one and add yourself to CONTRIBUTORS?

Hi terrytangyuan,
sure. Can you please teach me how to do it? Thanks

There are many ways to do this but here's one that's on top of my mind and you can just copy and paste.
git reset --soft HEAD~5 # move head to 5 commits before and keep the changes
git add -A # add all the changes to stage
git commit -m "Added max_to_keep parameter" # commit message
git push --force origin master # do a force push to your master branch since you are changing commit history

For your reference, you should look into how to use git rebase from command line or use it in sourceTree (http://blogs.atlassian.com/2014/06/interactive-rebase-sourcetree/).  Let me know if you have any questions.

Ok I did it. There's a problem with the CONTRIBUTOR file but it looks to be not relevant.

Good job! Looks like it has conflicts with CONTRIBUTORS. Could you resolve it or do a
git reset --hard HEAD~1
git push --hard origin master

and I'll add you there myself.
Thanks!

commands executed (actually --forcec and not --hard)
Thanks again

@glr72 I don't see any changes though. Mind trying it again?

closing this PR for now and refer to https://github.com/dmlc/xgboost/issues/892 for new guidelines with respect to adding these related features


Testing Code Climate

Signed-off-by: Jamie Popkin<EMAIL_ADDRESS>Hope this works.

Running Codeclimate locally now.


Can't import images on Mac

Hi,
I would be very interested in using mantis viewer for multipled imaging projects. I've tried the two most recent versions, but on my M1 MBP I cannot get mantis to open any images. I've screenshot the issue below. It begins saying 'loading image data' but then I get just a blank screen. When the blank screen occurs, it came up with on the console "Devtools cannot connect" or something to that effect. Wondering if you could point me in the right direction?
Thanks
Paul

just to add to this the issue happens on Windows. I can load the channel.tiffs fine, but its when I load the segmented image that I get problems. segmentation.tiff is >2GB which i assume is causing the issue as when I load the segmentation, I get an error message "array buffer allocation failed"..

Sorry for the delayed reply here! I just had a new kid, and things have been chaotic over here.
Mantis doesn't support loading any images larger than 2 GB unfortunately. The image library that Mantis uses loads the full image into memory, and JavaScript doesn't support objects in memory larger than 2 GB. You should be able to load segmentation data from the txt/csv format though. You can read about that here https://candelbio.github.io/mantis-viewer/docs/importing_data/importing_segmentation_region.html.
As for the M1 Mac issue, I'm able to reproduce on some M1 Macs, but I'm not sure what's going on. I'll look into it and see if it's an easy fix.

Hello,
I can confirm the same issue on M2 Mac. The viewer seems to have the image loaded but it freezes with the prompt "Selections are importing". I tried loading only a 250MB multi-channel Tiff file.

I encountered the same problem on a M2 macbook. Images can be loaded, but the segmentation file of 240MB not:


Allow changing uid/gid after binding

The problem: non-privileged users can't bind ports <1024 and port 80 is the standard port for HTTP. Running web server as root isn't good security practice. (Rust should be unexploitable, but who's willing to bet on it? :)) The standard way to solve it is to start as root and switch user after socket is bound.
There are three simple ways to allow it in simple-server without loss of generality:

create listen_with() method, which works like listen(), but accepts a closure which is run after socket is bound
create listen_on() method which accepts externally created socket
move TcpListener::bind from listen() to Server::new()

If I had to choose, I'd probably choose listen_on approach, but I really don't care as long as it's implemented. I'm willing to make a PR, just tell me which approach do you prefer.

Yeah, I haven't run into this because I'm always running nginx in front of simple-server. It'd be good to have the option, though.

accepts a closure which is run after socket is bound

I was considering changing listen's interface to be like this anyway; that's the way that the node API we copied works

create listen_on() method which accepts externally created socket

I am merging https://github.com/steveklabnik/simple-server/pull/104 which does exactly this!
Maybe check that out and we'll see if it's what you want? I think it is though!

In my case nginx would be unnecessary complication. #104 solves the issue.


inaccurate instructions

if you do this: https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview#install-the-mobility-service-using-ui-modernized
it leads to the classic registration window that asks for a passphrase.
had to use command line instead.

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

ID: d179f813-5826-7ec3-30c5-9b6b9c0a9acc
Version Independent ID: 3141a3e5-ea3b-cba1-7e34-4df69b8e1aa3
Content: About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery - Azure Site Recovery
Content Source: articles/site-recovery/vmware-physical-mobility-service-overview.md
Service: site-recovery
GitHub Login: @ankitaduttaMSFT
Microsoft Alias: ankitadutta

@Crensh Thank you for posting your question. We will review the doc with the content owner and update as appropriate.

@Crensh - thanks for pointing this out. We will add a note that only for versions 9.55 and above, modernized architecture is default for UI based installation. For versions 9.54 and below, command prompt instructions will need to be followed.

@Crensh The doc has been updated.

Thanks once again for your valuable feedback.
Closing this issue for now as no further action required.


Distinguish Subsystem By Lambda Alias

Is your feature request related to a problem? Please describe.
We'd like to distinguish between logs from lambdas we consider "development environment" versus from "production environments". For example, we'd like to apply the subsystem "my-service-dev" for lambdas invoked with the ci alias. Conversely, we'd like to apply the subsystem "my-service-prod" for lambdas invoked via the v1 lambda. This would allow for easy separation in Coralogix of source logs for viewing, alerting and graphing.
Describe the solution you'd like
On possible solution could be a feature that allows for mapping of subsystems based on lambda aliases via an env var CORALOGIX_ALIAS_MAPPING.
For example:
{
  "v1": "my-service-prod",
  "ci": "my-service-dev"
}

If no mapping is found, the feeder could continue to set the default subsystem as defined in the env var CORALOGIX_SUBSYSTEM.

:tada: This issue has been resolved in version 1.4.0 :tada:
The release is available on:

v1.4.0
v1.4.0
GitHub release

Your semantic-release bot :package::rocket:


Changes to allow building a devkit using podman on a RHEL8 host

Both of these changes are based on equivalents in the build pipelines:

Adds UID option for podman to ensure bind mounts are writable by the jenkins user
Avoid docker pull command if the image name contains rhel

@sxa rebase required.

@sxa rebase required.

Done - that was a tricky one, but I always knew it was going to be as I'd based it off a branch for one of Andrew's PRs which has now been merged.


Save multiple checkpoints in db in preparation to support rollbacks

Issue Number

#643
Overview

[x] I have adapted put/readCheckpoint and added unit tests
[x] I have changed TxMeta to accomodate needed changes
[x] I have adapted put/readTxHistory and added unit tests
[x] I have supported and united random and sequential scheme tests

Comments

bors r+

bors r+

bors r+

bors r+
Trying again. Devops were doing maintenance on the CI cluster.
In the staging build there were 3 integration test failures under TRANS_LIST_03 and TRANS_CREATE_10, TRANS_ESTIMATE_10.

It's weird, locally, it seems that I don't get any block from Jörmungandr beyond the first. For 60s, the restoration worker is stuck with:
[iohk.cardano-wallet.serve.worker.f6d92c46:Info:ThreadId 38] [2019-09-20 08:25:14.71 UTC] Wallet restored.
[iohk.cardano-wallet.serve.worker.f3ad0987:Info:ThreadId 47] [2019-09-20 08:25:14.78 UTC] Wallet restored.

bors r+

bors retry

(previous build failed because of release.nix on hydra)

bors retry

bors r+


Opening OBS with ahk hotkey

Hey, I'm trying to setup a ahk to open OBS with a hotkey, would this websocket for it be able to help? Because on normal ahk I get the failed to find locale and locale/en-US.ini errors.

I am afraid this is an OBS issue. My script is for controlling OBS, but it seems your OBS config files are broken/missing.
I could find some solutions for you by a quick googling, and it seems the solution is to reinstall OBS, see here:
https://obsproject.com/forum/threads/missing-locale-en-us-ini.26499/

The weird thing is that it only says that when I try to open it with AHK but when I open it normally it works just fine.

One of the solutions on the forum is:
"This occurs when you run obs64.exe outside of its working directory. Use the shortcut or set the working directory manually."
You can set the working directory for AHK's Run command.
https://www.autohotkey.com/docs/v2/lib/Run.htm

That works now thanks, would it be also possible for it to open a windowed projector of a specified scene on launch?

That is something which my script can help with.
The OpenSourceProjector method is the one you need:
https://github.com/obsproject/obs-websocket/blob/master/docs/generated/protocol.md#opensourceprojector
I've found a bug in the main library, which I needed to fix, but the script below now works. Note that this does not check whether OBS is already running (I'll leave that to you), it simply establishes connection to OBS and if that is successful, opens the projector.
#Requires AutoHotkey >=2.0-
#Include lib/ObsWebSocket.ahk

class MyOBSController extends ObsWebSocket {
	AfterIdentified() {
		; opening a source (named "Video Capture Device") as a projector
		this.OpenSourceProjector("Video Capture Device")
	}

	OpenSourceProjectorResponse(data) {
		MsgBox("Projector Window is opened")
	}
}

obsc := MyOBSController("ws://<IP_ADDRESS>:4455/")
F11:: MsgBox("") ; this is here only for keeping the script running


How to pass in constraints as functions

The current way of specifying the constraint explicitly on the variables x_1, ..., x_n doesn't quite work for me because the constraint I am working with is itself another black box. Therefore I will need to pass in the constraints as functions e.g.
constraints = [{'name': 'constr_1', 'constraint': f_1},
{'name': 'constr_2', 'constraint': f_2}]
Is it possible to do this in GPyOpt?

Unfortunately no, this is not supported. A bit more discussion in #285

Thanks for the quick response. Looking forward to the addition of this feature.


fix error in coordinator documentation

There is a missing comma in the Coordinator() documentation.

Can one of the admins verify this patch?

I signed it!

Thanks!


[Docs] Updates the documentation to clarify event persistence behaviors (Issue  #13058)

Notes for Reviewers
This PR updates the documentation to clarify the behavior of provider.PersistEvent(event) in relation to local and remote providers under "Contributing to Meshery Server Events," highlighting the potential need for better event propagation mechanisms. Additionally, a new subsection under "Remote Providers" in the "Extensibility: Providers" section discusses event visibility and proposes enhancements for enabling remote providers to dynamically subscribe to and handle Meshery server events, aligning with Meshery's extensibility framework.
Please take a look at these changes @leecalcote

This PR fixes #13058

Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit fdd247cd74d766cb846be1f6131bb3e3d0d7f5db at: https://677376e29d3a5b91c5174b2c--meshery-docs-preview.netlify.app


The error "KaTeX parse error: Invalid size" occurred when using \\[

Describe the bug:
When using \\[ such as:
a+b=c\\
[f(x)]^2

The error KaTeX parse error: Invalid size: 'f(x)' at position 9: a+b=c\\ [̲f̲(̲x̲)̲]̲^2 occurred.
To Reproduce:
Can be reproduced at https://katex.org/.
Environment (please complete the following information):

KaTeX Version: 0.16.3

That is not a bug. KaTeX is acting in precisely the same way that LaTeX acts with this input. When you write \\[,KaTeX is expecting you to specify a line skip distance, e.g., \\[2em].
There are many work arounds. For instance
a+b=c\\
{}[f(x)]^2

Thank you for replying.
However, I think it's a bit strange that \\[ is considered to be a line skip distance when \\ and [ are not even in the same line.
And it can be parsed in MathJax successfully, so I still think it should be improved.
Thanks again!

@ronkok I thought the same, but then I tested the following in LaTeX:
\begin{align*}
a+b=c \\
[f(x)]^2
\end{align*}

In fact, \\ seems to detect the whitespace before the [, and not treat it as an optional argument in this case.
In fact, the following KaTeX code seems to be trying to implement exactly this:
https://github.com/KaTeX/KaTeX/blob/2c13d2631ff9e8a6df7d895d2b2194da0572981e/src/environments/array.js#L221-L223
In fact, the above example works in KaTeX!  What doesn't work is \\ outside of an align environment. Technically that shouldn't work at all in LaTeX (can't write $a \\ b$ for example), but we've accepted it as a kind of extension (inspired by MathJax).
It looks like the culprit is src/functions/cr.js, which uses numOptionalArgs to fetch the optional argument.  It does seem that \@ifnextchar consumes spaces in LaTeX, so the default processing of optional arguments is correct.  AMSMath's definition of \math@cr is just special to avoid consuming spaces, via \new@ifnextchar.

Resolved via PR #3746.


How to start the tool

Hi , I'm not familiar with those scripts and I'm a beginner.
i installed everything and I'm looking for the command to launch the script.
I'm looking for a feature that can extract the TON address by providing the key , you thing it's possible to add it ?
thanks a lot for your answer

@abensim sorry for the late reply. So you want to get a public wallet address based on a mnemonic?
It is possible and could be added as next util, probably this weekend.

@abensim utility added with ff65aa1 commit


Trading API: Assets

Implement routes defined the Trading API assets docs.

def get_assets(self, request: GetAssetsRequest) -> List[Asset]:
    pass

def get_asset_by_symbol(self, symbol: str) -> Asset:
   pass

closed by #83


Missing the job_timelapse.yml file

Hi, and thank you for sharing this project. This is definitely an exciting project to experiment with and i have gone through the installation in the readme. Unfortunately i am a newbie and i am having trouble creating a yml file. Could you share an example yml file along with the rest of the project or do a walkthrough in the readme on how to create one?

Also, a nice twist would be to be able to upload new job files trough the dropbox connection from another pc to trigger new jobs remotely!

Hey! Thanks for the feedback. I will work up an example yml file tonight after work. Also, love the job upload idea!

Great! Thank you. Looks like i got it working now. Just copypasted the text from readme into a notepad txt and renamed it .yml
Do you know how i can render the images into a video before uploading it to dropbox?


usb2dbg: Windows can't verify the publisher of this driver software (10.0.15063.0)

Installed WDK for Windows 10, version 1703
OS: 10.0.16299 Build 16299
When trying to install usb2dbg.inf in C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\usb, it prompts "Windows can't verify the publisher of this driver software.".
Driver version is 06/21/2006,10.0.15063.0.
Issue still exists with windbg driver auto install.
No issue with driver version 14393 copied from other WDK installation.

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

ID: 3f5d6d55-cb35-6b9e-f8ca-e75f70826dc3
Version Independent ID: 1d913516-b1e0-e872-c337-e30ed5dffce8
Content: Previous WDK versions and other downloads
Content Source: windows-driver-docs-pr/other-wdk-downloads.md
Product: windows-hardware
GitHub Login: @EliotSeattle
Microsoft Alias: windowsdriverdev

Hi @wangxfdu
We're looking into this. One question. Did you already have any version of the WDK installed on this machine?
Thanks.

The team found no history of any issue like you describe. Since I haven't head anything, I am assuming that this is resolved for you. Feel free to reopen this issue if that's incorrect. Thanks!


fix: get rid of harmful shadow variable

fixes #415
@webdeveric there was a patterns array that was shadowed and led to stack overflow apparently.

@floydspace We may want to enable this eslint rule: https://eslint.org/docs/latest/rules/no-shadow


indicator will block in emui 3.1

like this

I have try. It's Ok.
1.Try Github Demo to find that is there anything wrong in your moible.
2.Try lazy load for your fragment.


The function of the tool is not understood

Is there a user manual that explains how to use the tool

In the main index of this project, there is a GammaEyes_manual_1.0.1.pdf.


getModelMarker behavior inside editor.onDidChangeModelContent

Observed Behavior
Using getModelMarkers() when handling the onDidChangeModelContent event of editor does not include any ModelMarkers that were introduced by the change being handled.
It does, however, include any ModelMarkers that existed before the current change.
Expected Behavior
When called inside the editor's onDidChangeModelContent handler, getModelMarkers() should include any ModelMarkers that were introduced by the change being handled.
monaco-editor version: 0.20.0
Browser: Chrome
OS: MacOS Mojave
Playground code that reproduces the issue:
https://codesandbox.io/s/monaco-editor-1906-zh7yx
var editor = monaco.editor.create(
    document.getElementById("container"),
    {
    value: `{ "json": true }`,
    language: "json"
    }
);

editor.onDidChangeModelContent(ev => {
    const markers = monaco.editor.getModelMarkers();

    // Note that a marker is only logged when it existed in the previous model content change
    // Shouldn't markers include the ModelMarker that was just typed?
    console.log(markers);
});

Same issue here

Let's track in https://github.com/microsoft/monaco-editor/issues/2138


Create hak-stjo.txt

Secondary Business School with IT-branch: 5 years of Java Programming/WebDev with 4 to 7 hours/week required attendance
(https://hak-stjo.salzburg.at/bildungsangebot/digbiz/stundentafel/, see section A2)
thx in advance!

@seiwaldm Pull request merged. Thank you!


Changes some missing references

Hey, I just made a Pull Request!

While #10374 was being merged I greped for Sandbox and found matches that were tied to the CNCF context. Unfortunately I wasn't fast enough to add the changes to the previous PR.
I updated the references that were missed in the previous PR within this one.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Just wanted to flag one more spot in the footer where we're linking out to the wrong CNCF page

Links to Sandbox projects page (https://www.cncf.io/sandbox-projects/) and needs to link to Incubating projects page (https://www.cncf.io/projects/)


SAMZA-2276: Add Metdata store putAll API

Add a putsAll API to the metadata store API. This allows for a delayed flush() call for underlying stores that require a flush() after write such as Kafka.

A few questions to understand the motivation of PutAll

Does Put have to be synchronous? Since flush() is exposed as part of API, what do you think about callers handling it in two steps? Have we evaluated this?
What is the use of flush()? Looking at the implementation of Put and PutAll, both are synchronous. Do we intend to have different behavior for future MetadataStore implementation? If so, I suppose we should follow up this PR with another PR that details the guarantees and expectations of these APIs.

I believe the original intent of the metadata store is to have consistent behavior regardless of the underlying store. Since it's simpler to make async calls synchronous than vice-versa, the expected behavior is synchronous. The intent of the putAll API is to provide an optimization option at least for the short-term until the next-gen metadata store abstraction is designed. That being said, I think flush() should not be exposed as an external API.
All good points you have brought up that we can take into account for the next phase of the metadata store design.

@mynameborat if you don't have any more comments, please approve and merge this commit. This is required to address an internal performance regression with job startup time. Thanks!
CC: @shanthoosh @prateekm

@mynameborat thanks for the review. I addressed your comment. This is ready to be merged.


ETL Off site IDs

are we storing things like the open corporates id as an id or a url?

Although we want the id, the url is in the sheet.I should detect url and extract ID actually, right?

Yes, that would probably be best way around!
Thanks

so for now we will only really handle RC-ids on contracts even though the model supports it


initial code commit

I've created the first implementation.

Changes Unknown when pulling 32af14dfbc7c8e6bd4431985e50bebaf172c9a92 on sttk:initial_code_commit into ** on js-cli:master**.

While the testrun module looks neat, I think I prefer to keep the tests vanilla mocha and using the expect library for assertions.  It allows for easier customization on a per test level (if it is needed) and is easier for me to follow when reading through the tests.

I started converting the tests to describe/it mocha syntax but paused due to the outstanding questions.

I'm OK that you rewrite the tests. I think testrun is useful for a mount of test cases on same test level as this case, but I also agree what you said.
(I added only and skip flags to testrun for controling test cases. Use them when they would help you convert or research the tests.)

Looks like it is getting super close!  Just have an extra devDep now

@phated Oh, sorry. I forgot to remove it. I've modified now.

Amazing work @sttk!

Published as 1.0.0 - if you need to change it at all for the liftoff implementation, we can try to fit it in the 1.x semver range.

Thank you very much! I'm so grad!


My xml file has any style information associated with it.

Hi
I wanted to use your script to turn mothur results into krona files.
I used mothur tax.summary file (mothur version 1.39.5):
taxonomy	total	A_3395B	B_3395B	C_3395B	E_3395B	L_3395B	X_3395B
Root	134	89	79	40	79	57	66
Bacteria;Actinobacteria;Coriobacteriia;Coriobacteriales;Coriobacteriaceae;Collinsella;	1	0	0	0	0	0	1
Bacteria;Actinobacteria;Coriobacteriia;Coriobacteriales;Coriobacteriaceae;Coriobacteriaceae_unclassified;	1	0	0	0	0	0	1
Bacteria;Actinobacteria;Coriobacteriia;Coriobacteriales;Coriobacteriaceae;Enterorhabdus;	1	1	0	0	0	0	0
Bacteria;Actinobacteria;Coriobacteriia;Coriobacteriales;Coriobacteriaceae;Senegalimassilia;	1	0	1	0	0	0	0
Bacteria;Actinobacteria;Coriobacteriia;Coriobacteriales;Coriobacteriaceae;uncultured;	1	0	0	0	1	0	1
and continues...
and the out put is a file XXX.xml
that provides the result in a xml file as attached file txt:
Empadas.txt
What am I doing wrong?
Thank you for any help.
Best
Igor

I'm no longer maintaining this script, and I don't work in the field anymore. I suspect something has changed in Mothur since I originally wrote this.
I'm happy to accept pull requests from anyone who would like to update the script.


Implemented Login API  Using JSON Web Token (JWT)

Thank you for your Great work, I found this I'd request you to change:

Remove "dj_rest_auth" from installed app as it is not being used, we're using JWT instead.
Remove the refresh token Configuration from settings.py as it is not necessary for now.

It is done, check it out


Add support for discarding a file in a pull request.

Description
Some files have trivial changes. There is edit and merge already provided by GitHub. Discard could take the old file and put it back as the edit.
Very useful for lightweight cleanup a PR (especially for files which have whitespace changes).
Screenshot

Example URLs
https://github.com/<org>/<repo>/pull/<id>/files

The feature exists already, its called restore-file

@atishay do you have the extension installed?

The example URLs field specifies a REAL URL is required.
The feature also already exists  👍

Thank you. Sorry was looking in the wrong browser.


Agent status report

Screenshots
1. Agent status report

2. Plugin status report

Is there too much escaping happening in the error messages?

That is the response of the API call(docker inspect task-id).


Restrict notifications by type

We should only trigger notifications on comments with the default ype. Also allow this to be filterable to include new types.

✨


[ Automation] Increase SSH connection establishing session timeout

Increase SSH Open Connection timeout over flaky network
The default value is 3 seconds. This is increase now to 30 seconds. In the recent time we are seeing SSH connection timing out in spite of BMC responding little latter.
Generally in the test connection are established as part of the suite
setup, if failed the entire test suite fails.
The only downside of this is that at the suite setup it would spend MAX
30 seconds if the connection is not established as oppose to 3 seconds
by default.

The fix is pretty simple..
From documentation
timeout=3 seconds, newline=LF, prompt=None, loglevel=INFO, term_type=vt100, width=80, height=24, path_separator=/, encoding=UTF-8
From
Library           SSHLibrary
to
Library           SSHLibrary   timeout=30 seconds


[SPARK-24994][SQL] : Support filter pushdown for short and byte without explicit casting

What changes were proposed in this pull request?
If we have a shortType column in our table, filter will not be pushed down for the following query:
select * from t where id = 2;
pushed filter ->
PushedFilters: [IsNotNull(id)], ReadSchema: struct<id:smallint>
2 is within short range still filter is not pushed down.
But it pushes filter if we cast the literal to smallint:
select * from t where id = cast(2 as smallint) ;
pushed filter ->
 PushedFilters: [IsNotNull(id), EqualTo(id,2)], ReadSchema: struct<id:smallint>
After these changes, there is no need to explicitly convert literals to short/byte for filter pushdown:
Select * from t where id = 2;
pushed filter ->
PushedFilters: [IsNotNull(id), EqualTo(id,2)], ReadSchema: struct<id:smallint>

Why are the changes needed?
These changes are needed because whenever we want to pushdown filters for short/byte value we have to explicitly cast them to short/byte even if the value is well within short/byte range.

Does this PR introduce any user-facing change?
Yes, now users dont need to explicitly cast literals to short/byte for filter pushdown.

How was this patch tested?
Manually. UT will be added soon.

cc @cloud-fan @HyukjinKwon

Can one of the admins verify this patch?

Can one of the admins verify this patch?

2 is within short range still filter is not pushed down.
But it pushes filter if we cast the literal to smallint:
select * from t where id = cast(2 as smallint) ;

Is that pushdown legal? if id is short, id = 2 is parsed as cast(id as int) = 2. So, I feel that the semantics  are different between them.

Is that pushdown legal? if id is short, id = 2 is parsed as cast(id as int) = 2. So, I feel that the semantics are different between them.

Naive users might not cast literal to shortType when passing a value within short range.
Also, if there are large number of queries which deals with short and byte fields, it is cumbersome to always explicitly cast them.
In those cases users can't get push-down benefits.
In my opinion we should push the filter if literals are in short/byte range.

So the goal is to push down cast(short_col as int) = int_literal? I agree this can be a common case, but I think we should optimize this filter before data source filter push down.
If the int_literal is beyond short range, then this predicate is either null (if the column is null) or false. So we can rewrite it to If(IsNull(short_col), null, false).
If the int_literal is within short range, we can rewrite it to short_col = short_literal by casting the int literal to short first.
When we push down filters to data source, the predicates already get rid of the cast at the column side.

This is another approach as suggested by @cloud-fan.
Rather than handling cast(id as int) in translateFilter , i have optimized the filters to remove cast expressions during optimization phase.
As of now i am removing cast for byte/short columns only. Whenever int literal is within byte/short range, cast expression is removed and int literal is casted to byte/short.
@cloud-fan @HyukjinKwon @maropu

@cloud-fan @HyukjinKwon @maropu Is it worth working on this one? Or should we close this one?

yea, +1 on closing this for now.


example scene wont run

I installed the asset and ran the example scene and got this error. Looks like a cool project!

Hmm. Egs is an autoload singleton that should get loaded in the main plugin file.
Can you check your project settings/ autoload? You can manually add it there, but you shouldn't need to do that because when you activate the plugin it should do that for you.
Just want to confirm:

Are you using Godot 3.x?
did you enable the plugin?

ah! I couldn't see where it said it needed activating, thanks, I got it working now 👍


How can I change titles of Wheel with new titles after completed the spin?

If you want to change the titles on the Wheel you may trigger a redraw by calling setNeedDisplay on your wheel. So basically you will want to do something like this:
self.spinningWheel.startAnimating(fininshIndex: 5) { (finished) in
                let slices = [ CarnivalWheelSlice.init(title: "New title"),
                               CarnivalWheelSlice.init(title: "New title"),
                               CarnivalWheelSlice.init(title: "Test")]
                self.spinningWheel.slices = slices
                self.spinningWheel.setNeedsDisplay()
}


Add Actions Workflow

Pull Request Test Coverage Report for Build 806

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.061%

Totals

Change from base Build 796:
0.0%

Covered Lines:
751

Relevant Lines:
807

💛  - Coveralls


fatal runtime error: stack overflow when a cycle exists between types with custom concrete names

Expected Behavior
There shouldn't be a stack overflow.
Actual Behavior
It seems that type registration results in an infinite loop when concrete type names are specified.
Steps to Reproduce the Problem
I was able to reproduce this error with the following schema. Notably, the error doesn't occur when the concrete(...) attributes aren't used, so I'm guessing there's something funky going on with type resolution when the concrete name is specified.
#[derive(SimpleObject)]
#[graphql(complex, concrete(name = "First", params()))]
pub struct First {
    id: String
}

#[derive(SimpleObject)]
#[graphql(complex, concrete(name = "Second", params()))]
pub struct Second {
    id: String
}

#[ComplexObject]
impl First {
    pub async fn test(&self) -> Vec<Second> {
        Vec::new()
    }
}

#[ComplexObject]
impl Second {
    pub async fn test(&self) -> Vec<First> {
        Vec::new()
    }
}

pub struct QueryRoot;

#[Object]
impl QueryRoot {
    pub async fn firsts(&self) -> Vec<First> {
        Vec::new()
    }

    pub async fn seconds(&self) -> Vec<Second>{
        Vec::new()
    }
}

Specifications

Version: cargo 1.61.0 rustc 1.61.0 async graphql 4.0.5
Platform: aarch64-darwin
Subsystem:

I have the same issue, is there any workaround?

Agree. Encountering the same issue as well. Removing concrete resolves the stack overflow.


Is possible freeze or lock rows and columns?

http://office.microsoft.com/en-us/excel-help/freeze-or-lock-rows-and-columns-HP005203861.aspx

Is there an example for this?

@jan
I found it here: https://github.com/randym/axlsx/blob/1bec39cebaef6a98481f52587ecc0483b4defc08/examples/split.rb
This is what I ended up using to have a frozen header row:
    # Header
    sheet.sheet_view.pane do |pane|
      pane.top_left_cell = "A2"
      pane.state = :frozen_split
      pane.y_split = 1
      pane.x_split = 0
      pane.active_pane = :bottom_right
    end

To be honest, I just guessed on the values until it worked.

To have a frozen header this is enough:
# Header
sheet.sheet_view.pane do |pane|
  pane.top_left_cell = "A2"
  pane.state = :frozen
end

@duffyjp that makes the first row frozen, and it also disables the scrolling while using my mouse wheel to scroll, however I can still use the scroll bar to scroll  down and up the page

Can we freeze some rows whose starting row is other than the first row?
Following code will freeze first 4 rows BUT I want to freeze 4 rows starting from row 3 i.e. rows 3,4,5 & 6.
sheet.sheet_view.pane do |pane|
  pane.top_left_cell = "A2"
  pane.state = :frozen_split
  pane.y_split = 4
  pane.x_split = 0
  pane.active_pane = :bottom_right
end

@atul25khanduri Were you able to find solution for this ?

@duffyjp that makes the first row frozen, and it also disables the scrolling while using my mouse wheel to scroll, however I can still use the scroll bar to scroll down and up the page

Please use pane.active_pane = :top_left, it will work


Partially fix page width problem

fix #805
Just fixed the case with Doc.english, you can still construct a counterexample with Doc.sep(Doc.plain(), Doc.plain(), ...)

Codecov is really buggy....


Provide a good design for the platform.

Can you pls assign this task to me?

Go ahead @bhoomikhurana


Implement a test that creates a raw proxy repository and attempts to download an artifact through it

Task Description
We need a new test to be added to the strongbox-web-integration-tests project that creates a raw proxy repository and resolves an artifact through it.
Tasks
The following tasks will need to be carried out:

[ ] Create a new module called raw under the strongbox-web-integration-tests project.
[ ] Add a new test in the module that creates a Raw proxy repository to https://services.gradle.org/distributions/ and attempts to download https://services.gradle.org/distributions/gradle-5.3-bin.zip.

References

The strongbox.yaml
Our REST API.
org.carlspring.strongbox.client.RestClient : This class should provide you the means to create a repository over the REST API. It might need to be improved.
Have a look at the other modules in the strongbox-web-integration-tests project and try to follow the same approach of doing things.

Help

Our chat
Points of contact:

@carlspring
@sbespalov
@fuss86

I will start working on this issue

[ ]  Create a new module called raw under the strongbox-web-integration-tests project.

work-in-progress branch:
https://github.com/strongbox/strongbox-web-integration-tests/commit/558d45cf6f8b0b82361035545e1adb25373bbe6a
todo:

[ ] debug adding the proxy repo
[ ] download the artifact

Ran into something that gave me pause...

When I docker-compose in my new module, and run my test, the intention is:

create a new storage
create a new repository - but, it fails 😞
... I will do other stuff later

my work-in-progress branch is here, this is the part where I add a new repository
github.com/strongbox/strongbox-web-integration-tests/blob/558d45cf6f8b0b82361035545e1adb25373bbe6a/raw/src/it/proxy-repository/test-raw-proxy-repository.groovy#L71
this is the output where it fails to create a new repository (I modified the method to return the response, not just the status code)
gist.github.com/bamarch/fc2c705638a6c805aa3b1b61a473cee0#file-gistfile1-txt-L116

sergey suggested I try the following:

there also should be a message, so you can try to read it from response you have
if message is not clear you can try to check the StoragesConfigurationController.addOrUpdateRepository method and see what can cause this response
if it still not clear you can start strongbox with spring-boot:run (or directly from your IDE) and try to debug same requests there

I am unblocked and back on track, but will be M.I.A. until Monday due to holidays

back from hols, and I spent today finishing up PR #1334
I will continue on this task (#1252) later in the week

In my pom.xml, which I based off the npm one, I had to make a change that resolves a recursive expression cycle
It was only my IDE that complained, not running mvn on the command line (although my IDE shoud be using system mvn...)
My change works fine locally but it might cause issues on jenkins?

if it still not clear you can start strongbox with spring-boot:run (or directly from your IDE) and try to debug same requests there

this was a great tip
I could run strongbox using spring boot, directly in my IDE, and then run my raw s-w-i-t with
mvn -DskipJetty clean install -U
this meant I could debug the requests as they came in and were handled

ok raw proxy repo created, just left is todo:

download the artifact
cleanup

@bamarch ,
You shouldn't have to modify any of these properties. What was the reason to do so?

@carlspring
If I run  maven lifecycle goals via IDEA (clean/install...) I get errors i.e. ‘recursive expression cycles’.
This is due to apparently cyclical definitions of strongbox.host and strongbox.port...
I only get this in IDEA, not when running via the command line (even though  I configured IDEA to use the system maven, not the bundled one)
I’m wondering if there is some setting that needs tweaking in Intellij to prevent this - for now the changes I show above give me a workaround

@carlspring so I had another look at the maven settings
it detected profiles in the pom.xml, as so:

if I just removed them from the box

Then it will run in IDEA, even with the original pom.xml properties

OK @carlspring the branch is basically ready, it works when I run it via maven
But, I am having issues when running it inside a container via docker-compose
running cd raw && mvn -U clean install (works)

running cd raw && docker-compose up (exits)

it might be that the download is timing out, because this file is around 90mb and my home internet speed is very slow - any ideas?
I have tried it a few times now, via my IDE, maven, docker - the issue only happens when using docker-compose
this is my branch:
https://github.com/bamarch/strongbox-web-integration-tests/tree/issue-1252/raw

docker-compose --verbose up

strongbox-web-integration-tests-raw_1  | Attempting to download http://localhost:48080/storages/storage-raw-proxies/raw-gradle-distributions-proxy/gradle-5.3-bin.zip
compose.cli.verbose_proxy.proxy_callable: docker wait <- (u'21636672cf3eda0d0bc51a421e6b62059ed08b764059715c75b689354f7709b4')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- (u'21636672cf3eda0d0bc51a421e6b62059ed08b764059715c75b689354f7709b4')
urllib3.connectionpool._make_request: http://localhost:None "POST /v1.25/containers/21636672cf3eda0d0bc51a421e6b62059ed08b764059715c75b689354f7709b4/wait HTTP/1.1" 200 30
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.25/containers/21636672cf3eda0d0bc51a421e6b62059ed08b764059715c75b689354f7709b4/json HTTP/1.1" 200 None
compose.cli.verbose_proxy.proxy_callable: docker wait -> {u'Error': None, u'StatusCode': 0}
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {u'AppArmorProfile': u'docker-default',
 u'Args': [u'clean', u'install', u'-U'],
 u'Config': {u'AttachStderr': False,
             u'AttachStdin': False,
             u'AttachStdout': False,
             u'Cmd': [u'mvn', u'clean', u'install', u'-U'],
             u'Domainname': u'',
             u'Entrypoint': None,
             u'Env': [u'PATH=/java/jdk8u202-b08/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin',
                      u'USER_ID=1000',
...

not much extra info when also passing --debug flag to mvn command

Opening this PR https://github.com/strongbox/strongbox-web-integration-tests/pull/49
to see if the issue still happens on Jenkins

Opening this PR strongbox/strongbox-web-integration-tests#49
to see if the issue still happens on Jenkins

it's looking good on jenkins (Y)


Error : The context size (4096)is too small to fit the context shift size 4096

I've encountered an issue while attempting to deobfuscate a JavaScript file that uses function name obfuscation and JSVMP reinforcement, utilizing a large model. My setup is a Windows 11 device with 64GB of RAM and an RTX 4000 ADA GPU with 12GB of VRAM. Could you advise me on how to proceed? Thank you very much!

I think this might be because of the recent context size change at version 2.2.0.
As a workaround you could set the --contextSize argument to something less than 1000, like 750 and try again.
If you can provide an example file which results in this kind of error, it would be super good so I can fix the underlying issue

@jehna Thank you for your reply. Unfortunately, for some reason, I am unable to provide you with the JS file. humanify local --contextSize=750 file.js and  humanify local --contextSize 750 file.js, I have tried this but it didn't work

Can you try lower values too? The original was 200, at least that should work


New Patient form text boxes should have correct text input type

🐛 Bug Report
The text boxes on the new patient form should have the correct input types. Right now, on a mobile phone it does not open the correct keyboard
Expected behavior

Phone Number should have type tel
Email should have type email.

Correct keyboard should be opened on mobile.
Changes needed
TextInputWithFormLabel component needs to support more input types and then the in the NewPatientForm component needs to declare the correct types.

Fixed it Up, hopefully up to your standards
😄

Can I take this issue?

@oizuldan I've assigned this to you!


[libpng] Replace find_library() with a simple set() for linking libm on UNIX

Similar issue as with Pull Request #7989, but different and more generic fix. Linking libm will work with the default x64-linux triplet, but fail if cross compiling (with a user-specific x86-linux triplet for example), with or without emscripten. As libm is part of the standard library, it can just be linked with its name.
This issue was also present in the Conan package manager and fixed the same way.

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

This change looks good to me.  Could you also bump the version in the libpng\CONTROL file to 1.6.37-4?


refactor(ui.config): break config into separate files

🔗 Linked issue

makes progress on #877
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

While work on reducing bundle size automatically will continue, this is part of the foundation for it.
This will also provide a workaround for devs to exclude the files for components not being used as Tailwind's content configuration reads entire files.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

@ineshbose I haven't forgotten this but it's quite hard to merge this as it will break all existing PRs. Also, is this really the solution? There should be a better way to exclude unused components from the tailwind config automatically.

@ineshbose I haven't forgotten this but it's quite tricky to merge this as it will break all existing PRs. Also, is this really the solution? There should be a better way to exclude unused components from the tailwind config automatically.

This isn't going to be the proper solution, but it is a step towards reaching it. Content detection in Tailwind is not automated right now, so just like nuxt/ui adds in the files:
https://github.com/nuxt/ui/blob/ceb2ed36d447c3617a6b077a5404949d241844e3/src/module.ts#L158-L162
we're going to have to consume them all. However, we most certainly do need to break the files down on a component-level if we are to make progress on this. When this is merged, users will at least have the option to specify the component files they don't use like so:
import { resolve } from 'pathe'

export default {
  content: [
    '!' + resolve('node_modules/@nuxt/ui/dist/runtime/ui.config/data/table.mjs'),
    '!' + resolve('node_modules/@nuxt/ui/dist/runtime/ui.config/forms/radioGroup.mjs'),
  ]
}

without this, all styles are in a singular file, so we either include it, or exclude it or do this similar approach above but in a complex way by creating an extractor function (not ideal).
All said, what would be really great for the next step of this PR, would be using unimport context during build to analyse imports and then do content configuration. Not to go out of depth and over-promise here, but this can require intensive time and research, so an automated solution will need to wait while the solution (imo) depends on this PR.
(Happy to continue discussion over Discord btw 🙂)

I'm gonna make a release in the coming days, do you think it would be best to count this in?

I'm gonna make a release in the coming days, do you think it would be best to count this in?

@benjamincanac I understand your point about breaking existing PRs, though we can also argue that implementing this change sooner for contributors to build upon would be better. I see 11 open feat PRs (some are features to existing components, so not touching ui.config, but we should also split the file to avoid potential future merge conflicts too), and fixing the conflict shouldn't be too difficult (just moving to a new file). I'll have to leave it for you to decide!

OK that's done. Ready to merge. @benjamincanac 😄


semirings

How about adding laws for semirings? Or would you rather it be in another package?
Either way, I can do the work.

Just did this.
Thanks for opening up the issue

Awesome, ty


Metric Dropdown blank when using Elastisearch data source

Hello! Thanks for taking the time to make this.
When I try to use an Elastisearch data type, the metric drop down on the display tab doesn't show anything available to be selected.

Sample Dataset:
{
   "_source": {
      "locName": "FakePlace",
      "loc_Pos_x": 447.625,
      "loc_Pos_y": 526.416
      }
}

Updated to latest version of both grafana and plotly and it's now working with elastisearch data.


Fix issue 8506

What is the purpose of the change
1.fix #8506.
2.on the consumer side, deduplicate multiple copies of the same service instance from multiple registries to execute LB correctly.
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Please resolve conflicts.

No feedback for a long time, there is any update to reopen the pr.

改好了，但是根据我修改后的逻辑会有个2个测试通不过。那2个测试会把某服务，该服务只有一个实例，同时注册到zk和redis上，去重后应该会只保留一个URL，但是assert了2个。


Instant Crash in 1.17.1 Fabric

"Cannot read field "enableInitLoadingScreen" because "net.morimori.mus.MemoryUsageScreen.CONFIG" is null. "
Crash Log has been supplied, plz advise.
crash-2022-01-24_16.43.42-client.txt
l

Nothing to do with Ears. Seems to be "memoryusagescreen".


Created a scope to resolve services from

This resolves scoped services and nested scopes

There's no way this breaks anything. But I have to check if the scope is disposed properly now that I think about it.

Looks good from my tests. No memory leaks after and all service types are resolved correctly.

If the hooks work as intended, the changes should be live soon!


Fix Autocomplete's renderOption signature.

The first argument is the props passed to the option, there was a missing ownerState.

Thanks for fixing this.


No such file or directory @ rb_sysopen

Just started to use que, but Im running into the following error: 'No such file or directory @ rb_sysopen - /User/.rvm/gems/ruby-2.2.5/gems/que-0.14.3/lib/que/migrations/4/up.sql'
When trying to run the migration file, like the example:
class CreateQueSchema < ActiveRecord::Migration[5.0]
	def up
    # Whenever you use Que in a migration, always specify the version you're
    # migrating to. If you're unsure what the current version is, check the
    # changelog.
    Que.migrate!(version: 4)
  end

  def down
    # Migrate to version 0 to remove Que entirely.
    Que.migrate!(version: 0)
  end
end

What im I doing wrong?
Thanks!

You seem to be using the 0.14.3 version of Que, where 3 is the newest migration version. Migration version 4 was added in Que 1.0, hence that files does not exists in your version of Que.
So you have two options:

Change the migration to target version 3 instead of 4.
Upgrade Que to version 1.0, and don't change your migration file.

Thanks for your quick reply. I guess updating to 1.0 (which is beta) is not the preferred solution since version 3 is the stable version right?

I haven't upgraded to 1.0 myself yet, but author of this gem is using 1.0 in production for months and it should be as stable the 0.x branch. So if I was just starting out with Que, I'd got for 1.0 now and avoid the upgrade later.
I think docs are already up to date with 1.0 as well.

Yeah, I merged the 1.0 branch into master, so I suppose you're looking at the 1.0 docs but using the 0.x branch. I'll add a notice to the README today to make that more clear.
I want to release an rc version soon, maybe that'll make people feel better about making the jump.

Like you guys mentioned, when upgrading to 1.0 this fixes my issue.


fix: some servers can have an extra relative path to /rest/api request.

I love the extension and really appreciate the great work but it doesn't work on our server due to a url issue. Please consider applying this code to fix that. Thank you.

great thanks. Anyway it seems your change is really specific. It would be better to add it as a setting. I will improve it if I have time before merge.

Yes right. A new setting for url would be also a good way to solve this problem. I guess this might be good when users want it to work automatically without manual setting work. Which way would be great if it works on our server :)

Any updates on this? It's been out since 2016 and seems like a really simple fix.


Issue when provisioning an actuator

I am using the following python code to create a service group
import json
import requests

url = 'http://localhost:4041/iot/services'
headers = {'Content-Type': "application/json", 'fiware-service': "openiot", 'fiware-servicepath': "/mtp"}

data = {
 "services": [
   {
     "apikey":      "456dgffdg56465dfg",
     "cbroker":     "http://orion:1026",
     "entity_type": "Door",
     #resource attribute is left blank since HTTP communication is not being used
     "resource":    ""
   }
 ]
}
res = requests.post(url, json=data, headers=headers)
#print(res.status_code)

if res.status_code == 201:
    print("Created")

elif res.status_code == 409:
    print("A resource cannot be created because it already exists")

else:
    print (res.raise_for_status())

But when trying to provision an actuator I get a bad request 400 error with the code below:
import json
import requests

url = 'http://localhost:4041/iot/devices'
headers = {'Content-Type': "application/json", 'fiware-service': "openiot", 'fiware-servicepath': "/mtp"}

data = {
 "devices": [
    {
      "device_id": "door003",
      "entity_name": "urn:ngsi-ld:Door:door003",
      "entity_type": "Door",
      "protocol": "PDI-IoTA-UltraLight",
      "transport": "MQTT",
      "commands": [
        {"name": "unlock","type": "command"},
        {"name": "open","type": "command"},
        {"name": "close","type": "command"},
        {"name": "lock","type": "command"}
       ],
       "attributes": [
        {"object_id": "s", "name": "state", "type":"Text"}
       ]
    }
  ]
}

res = requests.post(url, json=data, headers=headers)
#print(res.status_code)

if res.status_code == 201:
    print("Created")

elif res.status_code == 409:
    print("Entity cannot be created because it already exists")

else:
    print (res.raise_for_status())

Here is the error message I get in console.
iot-agent            | time=2021-02-17T11:39:44.132Z | lvl=DEBUG | corr=16f27639-49c2-4419-a926-2433805dbdb3 | trans=16f27639-49c2-4419-a926-2433805dbdb3 | op=IoTAgentNGSI.GenericMiddlewares | from=n/a | srv=smartdoor | subsrv=/mtp | msg=Error [BAD_REQUEST] handling request: Request error connecting to the Context Broker: 501 | comp=IoTAgent
iot-agent            | time=2021-02-17T11:39:44.133Z | lvl=DEBUG | corr=390f5530-f537-4efa-980a-890a44153811 | trans=390f5530-f537-4efa-980a-890a44153811 | op=IoTAgentNGSI.DomainControl | from=n/a | srv=smartdoor | subsrv=/mtp | msg=response-time: 29 | comp=IoTAgent

What is strange is that if a remove the commands from the payload the device provisioning works fine. Is there something am I doing wrong while trying to provision an actuator (not a sensor)?
IoT Agent version:
{"libVersion":"2.14.0-next","port":"4041","baseRoot":"/","version":"1.15.0-next"}
Orion version:
{
"orion" : {
  "version" : "2.2.0",
  "uptime" : "0 d, 0 h, 59 m, 18 s",
  "git_hash" : "5a46a70de9e0b809cce1a1b7295027eea0aa757f",
  "compile_time" : "Thu Feb 21 10:28:42 UTC 2019",
  "compiled_by" : "root",
  "compiled_in" : "442fc4d225cf",
  "release_date" : "Thu Feb 21 10:28:42 UTC 2019",
  "doc" : "https://fiware-orion.rtfd.io/en/2.2.0/"
}
}

My docker-compose file looks as follows:
iot-agent:
    image: fiware/iotagent-ul:latest
    hostname: iot-agent
    container_name: iot-agent
    restart: unless-stopped
    depends_on:
        - mongo-db
    networks:
        - default
    expose:
        - "4041"
    ports:
        - "4041:4041"
    environment:
        - IOTA_CB_HOST=orion
        - IOTA_CB_PORT=1026
        - IOTA_NORTH_PORT=4041
        - IOTA_REGISTRY_TYPE=mongodb
        - IOTA_LOG_LEVEL=DEBUG
        - IOTA_TIMESTAMP=true
        - IOTA_CB_NGSI_VERSION=v2
        - IOTA_AUTOCAST=true
        - IOTA_MONGO_HOST=mongo-db
        - IOTA_MONGO_PORT=27017
        - IOTA_MONGO_DB=iotagentul
        - IOTA_PROVIDER_URL=http://iot-agent:4041
        - IOTA_MQTT_HOST=mosquitto
        - IOTA_MQTT_PORT=1883

Thanks in advance.
Regards,

As Jason Fox said in stackoverflow, I was using an old version of Orion. By using the latest version, it works fine now.


Fix loop-reloading on shutdown

This was introduced via https://github.com/prometheus/prometheus/commit/2bf7048dbb1a60e36b0e41fc3a7ad58ecb3a8c4e
A range loop terminates on a closing channel. Switching to select thus caused case <-hup to succeed every time after closing the channel.
@jimmidyson

Thanks!


Error running the bunnymark example

Hello I'm trying to run the bunnymark example from here:
https://github.com/planetis-m/raylib-examples/blob/main/textures/bunnymark.nim
However I'm getting an issue where it errors with this message:
C:\Users\winuser\.nimble\pkgs2\naylib-4.6.1-b8dba6d8ec2d85d03665077430f315612b508f4c\raylib\src/raylib.h:1237:13:
error: conflicting types for 'LoadImageA'; have 'Image(const char *)'
 1237 | RLAPI Image LoadImage(const char *fileName); // Load image from file into CPU memory (RAM)

How would I fix this?
Here is the full error message if you'd like to take a look at the full thing:
bunnymarkerror.txt

Hi I've broken it down further and created a basic repro of the issue:
import raylib, raymath

type
  Player = ref object
    name: string
    position: raylib.Vector2 = Vector2.zero # Removing the vector also removes the error

proc main =
  var players = newSeq[Player](1)

  players[0] = Player()
  players[0].position = Vector2()
  players.add(Player()) # <<<< This gives the error

  # vvvv Adding this way doesn't give the error vvvv
  players.setLen(3)
  players[2] = Player()

main()

Strange that two functions with different names (LoadImage vs LoadImageA) have conflicts. We will have to mangle these as well.


Roll Flutter Engine from 877abb9ad6ff to 0d610802982e (5 revisions)

https://github.com/flutter/engine/compare/877abb9ad6ff...0d610802982e
2024-11-12<EMAIL_ADDRESS>Roll Dart SDK from 69170fac244c to 5f42ef8f15d5 (4 revisions) (flutter/engine#56539)
2024-11-12<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from BajfrJuYeyWvnBhuM... to z-cm2nR0aJ4lXfwZ0... (flutter/engine#56538)
2024-11-12<EMAIL_ADDRESS>Roll Skia from aa099ff91e2f to 7d5c206fc873 (6 revisions) (flutter/engine#56541)
2024-11-12<EMAIL_ADDRESS>[Impeller] In canvas_unittests, only create an MSAA offscreen texture if the platform supports MSAA (flutter/engine#56542)
2024-11-12<EMAIL_ADDRESS>[iOS] Fix slider semantics node answer to accessibility activate (flutter/engine#56427)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from BajfrJuYeyWv to z-cm2nR0aJ4l
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jimgraham<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


fix(workflows): improve sleep accuracy

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1106  👈
#1105
#1104
#1102
#1101
#1100
#1099
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MasterPtato and the rest of your teammates on  Graphite

Does the opposite


Expose way to run just microtasks

For jest integration - we should consider exposing a way to run only microtasks (nextTick) - this effectively means exporting runJobs.
There are no other things currently shimmed in lolex with microtask semantics (promises - no because of async functions, MutationObservers no). Since everything defers based on nextTick semantics that should be fine for jest inside jsdom.
CC @SimenB

We also have the inverse in Jest - just running macrotasks.
Another diff in this regard is that our tick just triggers timers, it doesn't touch microtasks. Again, I'm not sure in what instances the distinction is useful, but I suppose it exists for a reason 🙂
See Jests docs (from the linked paragraph and down) for a rundown of what we do today. http://facebook.github.io/jest/docs/en/jest-object.html#jestrunallticks
Any obvious issues popping up?

I don't understand why running just macroticks and not microticks makes sense. (Since it would never be regular execution flow). Any motivation on why this is required?

@cpojer (who's on vacation, so might be a bit before we get an answer) any particular use cases for this?

I think running both in one call works fine with me, but I cannot confirm without testing this on the FB codebase. I can check usage of advanceTimersByTime at FB in early January to confirm.

Taking a look

@benjamingr I haven't noticed the PR at all: do you have all required privileges to merge now, btw?

@benjamingr You had been added to the lolex-core team ages ago, but I had forgotten to give lolex-core rights to do anything on the lolex repo. You should be good to write and approve stuff now! Sorry for delaying this, but a new family situation  :baby_bottle:  arose around the time of this PR.
Don't be a stranger to pestering my on email, btw, if I should be blocking something.

@fatso83 congratulations! Really no rush here or sense of urgency - family first and thanks :)

@benjamingr I think I've found an issue with the implementation - it doesn't guard against recursion in the same way the timers do. Jest has the following test, which never completes when using this new function:
it('throws before allowing infinite recursion', () => {
  const global = {
    Date,
    clearTimeout,
    process: {
      nextTick: () => {},
    },
    setTimeout,
  };

  const timers = new FakeTimers({
    global,
    maxLoops: 100,
    moduleMocker,
    timerConfig,
  });

  timers.useFakeTimers();

  global.process.nextTick(function infinitelyRecursingCallback() {
    global.process.nextTick(infinitelyRecursingCallback);
  });

  expect(() => {
    timers.runAllTicks();
  }).toThrow(
    new Error(
      "Ran 100 ticks, and there are still more! Assuming we've hit an " +
        'infinite recursion and bailing out...',
    ),
  );
})

I think runMicrotasks should also respect the maxLoops argument.

Going to reopen since it's being discussed

Interesting, didn't know that! A bail seems more useful than a freeze, especially in a testing situation (as it prevents tests from timing out), but matching real behavior (beyond manipulating time) is really compelling as well.
@cpojer thoughts on this?

Regardless of what's better, we cannot change behavior for existing Jest tests at this time. If we want to use lolex for Jest, the initial version must 100% match what Jest has right now. We can make incremental breaking changes later.

I'll make a PR @SimenB @cpojer

@SimenB let me know if the fix in https://github.com/sinonjs/lolex/pull/172 works for jest


Redefine ASN_DEBUG in asn_internal.h (EMIT_ASN_DEBUG != 1)

Change proposed in #124.
By evaluating the arguments passed to "static void ASN_DEBUG(...)", many unnecessary calls are made to ber_tlv_tag_string(). My experience suggests replacing the dummy function definition with an empty macro results in a significant decrease in CPU time.

Coverage remained the same at 79.816% when pulling 97d69362d376b6d0f77c24cb33581bade3170efa on mattipee:mattipee-patch-ASN_DEBUG into bc0b0c5062cdc55f8160993441f6bb84e737d333 on vlm:master.

The reason the static function definition was there is because variadic macros (ASN_DEBUG(...)) is not a C90 conformant feature. I intentionally keep skeletons and generated code C90-conformant.
However, I see a definite value in your patch, so I rewrote it as https://github.com/vlm/asn1c/commit/2b290bef16a01beebb4bbf7212f789241d973d7e
Thank you!

Thank you.