Authentication mode is different.

I have created my account using google login, hence I don't have password for my account.. How i am suppose to put credentials in .env file? any idea?

Visit Open AI and create an API key, and put that in the .env file.

Okay, so Org ID and API key will work in this case... i'll try :)

I tried, still getting same msg: I'm sorry, I'm not available at the moment to reply. Please try again after sometime.
and on console Failed to send message to ChatGPT API: Error: Request failed with status code 404

ok, I changed... what does the 429 status code means?

also the 401 status code. can you explain the these both status codes?

ok, I changed... what does the 429 status code means?

got it, thanks..  :)


Remove ChainedError trait

It's presently not serving much purpose.

I've looked at this. What's the plan for the functionality contained in the trait? I.e. what does the removal look like at a high level?

That would mean moving the code in the macro.

It turns out that implementing DisplayChain requires accessing the backtrace and there's no way to do that without a trait of some form. The only other solution would be moving code from src/lib.rs into the macro, which just seems like it would cause additional bloat.

I'm using ChainedError as associated type for trait. What would be my alternative if/when it's gone?


Adds response computed variable

This is useful when you just need the (possible) network response but don't care about the specific Error (see this example of usage).
It feels silly to have to write it, but it makes sense. May as well only write the silly code once :smile:

Current coverage is 91.72%

Merging #401 into master will increase coverage by +0.56% as of dfe70c7

@@            master    #401   diff @@
======================================
  Files           13      13
  Stmts          453     459     +6
  Branches         0       0
  Methods
======================================
+ Hit            413     421     +8
  Partial          0       0
+ Missed          40      38     -2

Review entire Coverage Diff as of dfe70c7

Uncovered Suggestions

+1.30% via ...ource/Response.swift#76...81
+1.09% via ...+ReactiveCocoa.swift#54...58
+1.09% via Source/Moya.swift#188...192
See 7 more...

Powered by Codecov. Updated on successful CI builds.

:+1:

Thanks!


init build system for cleaner/launcher

this is a first step in the building of the native installer, it works for cleaner and launcher and the resulting assembled contains native for windows only in the same path as in current used zip.
I'm progressing slowly and would prefer finishing the easy part to later do jnilib that looks complex to me.
I use Makefile.mingw to be inline with native-launcher and limit the cost to learn a new system for each lib. But this is an abstract view.
If anyone could also make any feedback to choose a version for the artefacts that make them less confusing with NetBeans version https://lists.apache.org/thread/vgm39xzh5lqrm33pfxk2xcv1pr769jqm

Excellent step you are taking.
For me it is all about

Repeatability.  The artifact used by the NetBeans distribution must be build by a pipeline and uploaded to its final destination (from where NetBeans distro picks it up) by a pipeline.
Traceability. It must be possible to look at a build artifact and see exactly from where and from which commit it originates. This is typically solved by Git tagging, but if you are including a BUILDINFO file in the distributed artifact then tagging is not necessary per se. You can see in build-for-native-profiler-lib how this might be done. The BUILDINFO has the advantage that it can also convey a repo URL which is increasingly important now that all the native stuff will be in lots of different repos.

As for unifying (to some extend) which tool chain is being used, I'm all for it.
Other:

Tool chain requirements should be documented in the repo's README.

Branch workflow should be documented in the repo's README, in particular what it requires to create a real release. For example, this may be triggered by a commit to main branch.

If this is a new repo, why is the branch called master  and not main ?  From what I know, the ASF is quite involved with the Inclusive Naming Initiative, I remember some email to all ASF committers about a year ago?  .. so we might as well start out on the right foot.

My comments are more in the things-to-remember category. They should not be seen as a blocker to merge this PR.

@lbruun @mbien I'm not sure to follow 100% but is it ok to merge. If we miss a 32bits/64bits target maybe we could iterate.
Would like to alter main repo to have a workflow to start integrate that.
@neilcsmith-net not against nbpacker but the nbm-harness contains thoose libraries because using unziped nbi engine and installer build is "locked to that" except if we change nbm-maven-plugin for this goal.

@ebarboni yes, I'm aware of that, and will try and look at options for that soon. But I'm not arguing against people stepping up to fix NBI. Just there's a bunch of issues with it alongside this - it really needs active development or dropping.

I'm not sure to follow 100% but is it ok to merge. If we miss a 32bits/64bits target maybe we could iterate.
Would like to alter main repo to have a workflow to start integrate that.

If I could chip in - I tried compiling as a 32-bit windows exe and AFAICS it was fine. I believe that a 32-bit parent can spawn a 64-bit child process and vice versa, so either type of stub would be able to start the JVM which runs NBI itself. However if the user were using 32-bit Windows then a 64-bit stub would not work for them. I know Windows 11 is 64-bit only but there are probably Windows 10 and earlier users with 32 bit installations.
Which is a round-about way of saying the stub should be 32-bit, unless there's another reason I've not understood!

So you mean I put architecture=32 and would be good for you ?
@lbruun sorry I did not get the issue on the main/master branch. I prefer to stay on master because our build use master as default and changing only for new repo will drive me crazy. We should do a giant leap changing in the same timeframe all to get back on our foot in a day or so but this has to be prepared.

So you mean I put architecture=32 and would be good for you ?

You'd need to change the 64-bit compiler (x86_64-w64-mingw32-gcc) which is hardcoded in the Makefile.mingw. I think you need to call the particular compiler, it's not just a command line option. I can't check just now but if memory serves the 32-bit tools start with i686-...

You'd have to change src/main/cpp/launcher/windows/Makefile.mingw also in the same way (for C compiler and resource compiler)

@pedro-w sorry thanks for pointing that. Hope this is fine now :D

I haven't had time to test but that looks good to me.

I did rebase and merge


Updated / Deleted some examples

Description
example/multivariate_time_series:

updated README to point to Gluon implementation
fixed typo

example/named_entity_recognition:

fix example and remove need for preprocessed_data  data folder

example/nce-loss:

fix README.md instructions

example/numpy-ops:

removed outdate API example (NumpyOp)

example/onnx:

deleted example, duplicate of the tutorial

example/python-howto:

deleted outdated example

example/mxnet_adversarial_vae:

renamed to example/vae-gan

@anirudh2290 I don't believe there is a need to replace the Monitor ones with Gluon equivalent, as a print() statement is enough to print values in Gluon. Also Monitor seems deprecated since it doesn't appear in the docs and I haven't seen it used in any other examples.
The grouped example is very bare and does not bring anything more than the documentation is already bringing. https://mxnet.incubator.apache.org/versions/1.3.0/api/python/symbol/symbol.html?highlight=group#mxnet.symbol.Group
The image record iter is better served through the docs as well https://mxnet.incubator.apache.org/versions/1.3.0/api/python/io/io.html?highlight=imagerecorditer#mxnet.io.ImageRecordIter

@ThomasDelteil Thanks for the contribution!
@mxnet-label-bot [pr-awaiting-merge,Example]

@anirudhacharya @anirudh2290 Could you please take a look?

LGTM

LGTM

@indhub @szha @nswamy can you please merge? Thanks

@sandeep-krishnamurthy can you please help with a review and merge? Thanks!


[WIP] Video player headers

As requested in https://github.com/flutter/flutter/issues/16466
I added headers for VideoPlayerController for android for now, ios will come eventually.
screenshot from charles proxy:

cc @mravn-google

@charafau how can i get your working solution for android only


[Bug] DocSum failed on Gaudi

Priority
P1-Stopper
OS type
Ubuntu
Hardware type
Gaudi2
Installation method

[ ] Pull docker images from hub.docker.com
[x] Build docker images from source

Deploy method

[X] Docker compose
[ ] Docker
[ ] Kubernetes
[ ] Helm

Running nodes
Single Node
What's the version?
340796bbae61d38a6aae4d244eef8d583101c04e
Description
https://github.com/opea-project/GenAIExamples/actions/runs/12142010040/job/33896729882
Reproduce steps
https://github.com/opea-project/GenAIExamples/actions/runs/12142010040/job/33896729882
Raw log

@MSCetin37

This issue is addressed in 1231

@chensuyue, @ashahba , @feng-intel,
This issue is solved, but merge https://github.com/opea-project/GenAIExamples/pull/992 is causing a DocSum Megaservice failure, which is not within the scope of this issue.


Check if Ledger works with Hex

Checked it by myself, here's the results:

Break block - doesn't log at all, does not rollback as well (Which is weird, as it worked fine before)
Place block 1/2 - logs perfectly
Conjure block/light - does not log at all as well as you can't rollback
Conjure water/lava - Does not log at all (I also found out that placing water/lava normally does not log for some reason)
Destory liquid - Nope, no log

So in results, only place block actually logs here, while other spells seems to not log at all. It might be because we're on quilt, as some things here act differently


Learn about Reactor

https://projectreactor.io/

It is not necessary at the moment. LEAN approach


Sonos loses current music stream

When I am listening to Pandora and I tell the node to play some content, my Sonos connect loses the current stream and starts to play what is in the queue.

Hi Jmorris,
yes, the Sonos API are undocumented and it's nearly impossible to resume a radio station.
Sorry for that, but i'm unable to fix it at the moment.

Hi Jmorris,
yes, the Sonos API are undocumented and it's nearly impossible to resume a radio station.
Sorry for that, but i'm unable to fix it at the moment.


wrong tokenization about eos token

Hi, teams!
Thanks so much for the great repo! I want to report a problem about add eos token in the finetune.py
https://github.com/allenai/open-instruct/blob/763206f5b8fe340c7833c438113f69ba7bca8886/open_instruct/finetune.py#L277
https://github.com/allenai/open-instruct/blob/763206f5b8fe340c7833c438113f69ba7bca8886/open_instruct/finetune.py#L311
Here is the reason why this might cause problem:
from transformers import AutoTokenizer
tokenizer = AutoTokenizer.from_pretrained("huggyllama/llama-7b")
text = "a random text"
text = text + tokenizer.eos_token
print(tokenizer.tokenize(text))

text = text + " " + tokenizer.eos_token
print(tokenizer.tokenize(text))

Hi,
thanks for the issue! Curiously, we don't see this issue with the tokenizer from the official facebook release:
>>> tokenizer = AutoTokenizer.from_pretrained("meta-llama/Llama-2-7b-hf")
>>> tokenizer("hello</s>")
{'input_ids': [1, 22172, 2], 'attention_mask': [1, 1, 1]}
>>> tokenizer("hello </s>")
{'input_ids': [1, 22172, 29871, 2], 'attention_mask': [1, 1, 1, 1]}

But I do see it with other uploaded llama tokenizers....:
>>> tokenizer = AutoTokenizer.from_pretrained("oobabooga/llama-tokenizer", legacy=False)
>>> tokenizer("hello</s>")
{'input_ids': [1, 22172, 829, 29879, 29958], 'attention_mask': [1, 1, 1, 1, 1]}
>>> tokenizer("hello </s>")
{'input_ids': [1, 22172, 2], 'attention_mask': [1, 1, 1]}

Looking at the configs, they are not identical.... Our code behaves correctly when we use the official tokenizer, and adding a space actually changes the tokenization with the official tokenization:
>>> tokenizer("hello </s>")
{'input_ids': [1, 22172, 29871, 2], 'attention_mask': [1, 1, 1, 1]}

As such, I don't really want to change this, but this is a useful find. Perhaps you can edit the script locally to match your use case, if you need to use this tokenizer?

Hi,
Thanks so much for the response and detailed investigation! I would update the script locally.

Hi, @hamishivi
I found a compatible way by using add_eos_token=True when initialize a Tokenizer.

Hi, @hamishivi
Sorry for bother you again.
But could you please check this issue? https://github.com/huggingface/transformers/issues/29375
Can you replicate this behaviour on your side?

Unrelated since tulu did not use fast tokenizer


Fix import failing when using "python -OO"

[x] Tests added / passed
[x] Passes black dask / flake8 dask
[x] Fixes #6296

cc @dask/maintenance
To test: try python -OO -c 'import dask.array'  on this branch vs master.

?? optimised functions don't have names ?? :)
So you think it's worth doing a test run for OO, or at least an import check?

We used to do this, but stopped since not many people wanted it and it took up a test matrix slot. The code logic is still in our travis setup, it's just not enabled.

I think it's more like optimized partial functions don't have names. I think this PR is an improvement as I don't think the name is as intended on master anyways:
>>> import dask.array
>>> print(dask.array.full.__name__)
blocked_full

don't really care one way or the other about CI.

OK :)


Created a synchronous ZooKeeper.sync() method for use in ZooKeeperTestingServer tests

Related to #2474

Closing in favor of #2550


Do not work with ts-patch

{
  "compilerOptions": {
    "module": "NodeNext",
    "declaration": true,
    "removeComments": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "allowSyntheticDefaultImports": true,
    "target": "ESNext",
    "sourceMap": true,
    "outDir": "./dist",
    "baseUrl": "./",
    "incremental": true,
    "skipLibCheck": true,
    "strictNullChecks": false,
    "noImplicitAny": false,
    "strictBindCallApply": false,
    "forceConsistentCasingInFileNames": false,
    "noFallthroughCasesInSwitch": false,
    "plugins": [
      {
        "transform": "tsc-progress",
        "title": "TSC"
      }
    ]
  }
}

><EMAIL_ADDRESS>build:tsc /home/keinsell/xxx/apps/server
> tspc -p tsconfig.build.json

Nevermind, was caused by incremental compilation (I had dist already and progress was not showing up)


Adjust / reduce the rate that text is output to the screen for visual effect.

-->
Slow the output of text to each line, replicating the slow modems of old, teletypes and sci-fi movie computer text.
Cathode, a now dead/obsolete fancy terminal for MacOS (similar to CoolRetroTerm) had a similar feature.

Proposed technical implementation details (optional)
Artificially reduce the speed new characters are output to a line in any given terminal session.

While this does seem like a fun gimmick, couldn't this be accomplished with some sort of shim executable like slow-output-down.exe that just starts some other commandline and buffers the output itself? I'm not totally sure that this is something that needs to be built in to the Terminal...

While this does seem like a fun gimmick, couldn't this be accomplished with some sort of shim executable like slow-output-down.exe that just starts some other commandline and buffers the output itself?

Yeah, I have a little python script I use for viewing old VT animations. That said, I did also think it might be neat to have it built into the terminal as a hidden feature which could possibly be triggered with a DECSCS sequence. I don't feel that strongly about it, though, because it's honestly not the sort of thing I'd use very often.

I agree this is 95% for show, but I really did find it made working with big lists in the command line much easier.  Thought I'd float it just in case.
I've found some python scripts that replicate the effect and while not remotely sane to pipe every terminal command to it just for eye candy, since what I'm mostly dealing with is from my own scripts I can just tack on some code to them instead.


When will the batch html import feature be available?

I don't mean to be pushy, I just don't need to study pandoc if it's going to be available soon

It's planned, but not currently in progress, see #13


Feature Request: Push debugger activation to first breakpoint hit instead of require "debug"

Proposal

require "debug" won't activate the debugger. Debugger will only be activated when the first breakpoint is triggered.

require "debug" will be the same as require "debug/session"

require "debug/open" and require "debug/open_nonstop"'s behaviour will remain the same.

Why
Side-effects
In apps that have Bundler.require, like most Rails apps, having gem "debug" in Gemfile means the debug gem is always activated when the app is booted.
However, with the debugger's activation, many things will happen in the background:

Additional TracePoints would be enabled (example)
A new thread will be spawned
Additional computation and object allocation that come with the above

To most apps, having them in the background doesn't make a huge difference. But to some, having the debugger activated causes tests to fail.
For example, I tested 5 mid-to-large Rails apps in Shopify, and 3 of them have test failures that only happen when debug is activated:

Some tests mock File.readlines and could break when this line is triggered in the background.
There's also weird NoMethodError exceptions that only happens with the debugger activated.

Therefore, we always have require: false after gem "debug".
Problem Solved?
However, having require: false means users need to manually type require "debug" before start debugging with console. But in the meantime, byebug can be required by default without the same side-effects. So byebug doesn't need that manual require.
This extra require step is quite inconvenient for people considering switching from byebug to debug.
Other Smaller Issues

The activation and forking messages are noisy and disabling them project-by-project is not trivial.
require "debug" locks the UI to console, so if users want to use the remote UI by requiring debug/open after the app is booted, require: false is also needed.

Possible Change
diff --git a/lib/debug.rb b/lib/debug.rb
index 15ebccb..3489268 100644
--- a/lib/debug.rb
+++ b/lib/debug.rb
@@ -1,5 +1,3 @@
 # frozen_string_literal: true

 require_relative 'debug/session'
-return unless defined?(DEBUGGER__)
-DEBUGGER__::start no_sigint_hook: true, nonstop: true
diff --git a/lib/debug/session.rb b/lib/debug/session.rb
index a900f89..ffb2604 100644
--- a/lib/debug/session.rb
+++ b/lib/debug/session.rb
@@ -2486,7 +2486,9 @@ end

 module Kernel
   def debugger pre: nil, do: nil, up_level: 0
-    return if !defined?(::DEBUGGER__::SESSION) || !::DEBUGGER__::SESSION.active?
+    if !defined?(::DEBUGGER__::SESSION) || !::DEBUGGER__::SESSION.active?
+      DEBUGGER__::start no_sigint_hook: true, nonstop: true
+    end

     if pre || (do_expr = binding.local_variable_get(:do))
       cmds = ['binding.break', pre, do_expr]

Let me think some more time about it.

require "debug" won't activate the debugger. Debugger will only be activated when the first breakpoint is triggered.

Your proposal is based on that: user only specify the breakpoint with debugger method.
I agree many people do that but I don't want to remove other possibilities.

To most apps, having them in the background doesn't make a huge difference. But to some, having the debugger activated causes tests to fail.

In general, I want to solve these failures by fixing the debugger, not by lazy session starting. So the bug reports are welcome.

For example, using from IDE it is same issue.

Additional overhead can be an issue and I want to know how it impact on the real usecases. Please file if you find an impact.

I want to provide a way to connect to the app via debug port as an backdoor, so I'll provide a way more lightweight version (disable collecting the source code, and so on).

If we don't start the session, we couldn't support the following and I'm not sure it should be disabled by default.

opening debug port with RUBY_DEBUG_OPEN.

loading rdbgrc file(s).

multiple forked code entering to the debug console, the input/output will be mixed.

it can be avoid with a trick, anyway.

recording evaled code.

not so high priority.

BTW requiring debug/prelude doesn't start session, but define debugger (and others) so you may want to use it (but it needs to change Gemfile a bit).
Another idea is to make gem only requires debug/prelude.

I introduced RUBY_DEBUG_LAZY experimentally (so I don't write it on doc), it's require debug/prelude instead of calling start, so please try it and make it official on next version.

The activation and forking messages are noisy and disabling them project-by-project is not trivial.

fixed on https://github.com/ruby/debug/pull/823

require "debug" locks the UI to console, so if users want to use the remote UI by requiring debug/open after the app is booted, require: false is also needed.

I'd supported it (override by requiring debug/open after requiring debug) but it was broken.
fixed on https://github.com/ruby/debug/pull/825

Your proposal is based on that: user only specify the breakpoint with debugger method.

If users want to set breakpoints with other ways, say with break command, shouldn't rdbg  work the same? 🤔
I'm not sure why lazily loading debugger will reduce the possibilities to set breakpoints. Can you elaborate more?

In general, I want to solve these failures by fixing the debugger, not by lazy session starting.

Yes I also believe that's the way to go. But I'm not sure how much the effort it'd take and how it'd be prioritised.
I think lazy-activation to reduce friction is a good first step toward that goal though. And once we made activation lightweight, we can turn it back on and users wouldn't notice a thing.

I'll provide a way more lightweight version (disable collecting the source code, and so on).

I can test if disabling the TracePoint reduce test failures in our apps.

If we don't start the session, we couldn't support the following and I'm not sure it should be disabled by default.

I think the features you listed are useful, but also seem quite specialised. In my experience using and helping my colleagues use the debugger in apps and gems, we rarely need them. I'm not saying that we represent most users, but it may be a shared experience.
So how about we do it in another way:

By default we lazily activate the debugger (until it became lightweight enough).
In the readme we tell users, if they need the listed features, they need to eagerly load the debugger by setting an environment variable like RUBY_DEBUG_ACTIVATE_AT_START=true.

The idea is, to make the debugger easily accessible to average users, we make it as lightweight as possible by default (lazy-activation is one way). And if some users want more powerful features, we also give them options to change the default behaviour.

Another idea is to make gem only requires debug/prelude.

I think that's a good idea too 👍

fixed on https://github.com/ruby/debug/pull/823
fixed on https://github.com/ruby/debug/pull/825

Thank you so much for these fixes 🙏

I'm not sure why lazily loading debugger will reduce the possibilities to set breakpoints. Can you elaborate more?

For example, rdbgrc can set breakpoints and editors (vi and so on) can set them.

The idea is, to make the debugger easily accessible to average users, we make it as lightweight as possible by default (lazy-activation is one way). And if some users want more powerful features, we also give them options to change the default behaviour. WDYT?

I believe reducing functionality is for high-level users who can understand what they are doing.

for example: "if you want to use Regexp on Ruby, please use --regexp option" is not convenient.

I believe reducing functionality is for high-level users who can understand what they are doing.

I think it really depends on what functionalities we are reducing and what most of the users's usage of them.
For example, I haven't needed to use rdbgrc to set breakpoints because it means the breakpoint would be set to all Ruby projects I have, which varies a lot and it simply won't work. I'm not saying nobody uses this feature, but it's likely be a rare case.
In the contrary, at Shopify we several applications, as well as gems like Tapioca, that can benefit from having lazy-activation by default. (Also the app of my prev company, which's tests fail whenever debug is required).
I also want to add an update on the RUBY_DEBUG_LAZY experiment:
I experimented RUBY_DEBUG_LAZY=1 and removed require: false on a big monolith we have. I applied it to

The project's local development default envs
The project's cloud development default envs

And the initial CI seemed to run fine, so we merged the PR.
But it turned out it randomly hanged some of the CI suites from time to time. And it took us a few days to pin down to my change. We don't exactly know what code was causing that, but it's loading the debugger that caused it. So we now added require: false back.
It's possible that we can add RUBY_DEBUG_LAZY=1 to the project's CI setup too. But that project has a dozen of CI suites. If I missed anyone of them, we'll have a flaky CI again.
What I want to say is, we're not requesting any advanced features of the debugger. We simply want to add gem "debug" to the Gemfile and let users explore it. But the current activation behaviour is causing a lot of issues just to do that.
The RUBY_DEBUG_LAZY experiment is helping, which we appreciate. But it'd still be a lot better if we can make it the default. And if the cost is some advanced and potentially rarely used features would require a flag to work, I think it's a reasonable tradeoff.

So RUBY_DEBUG_LAZY also have an issue you couldn't figure out, right?

Sorry I wasn't clear: the problem was caused by some CI tests not having RUBY_DEBUG_LAZY:

Some test suites ran with RUBY_DEBUG_LAZY and they passed.
Some test suites ran without RUBY_DEBUG_LAZY and failed randomly, therefore we didn't discover at the beginning.

So my point is, needing to manually apply RUBY_DEBUG_LAZY in all the places that could use it could be a huge burden to users.

BTW why do you use debug.gem on CI?

In Rails applications, debug gems usually will be put under the development and test group in Gemfile. This is the Gemfile current Rails generates:
group :development, :test do
  # See https://guides.rubyonrails.org/debugging_rails_applications.html#debugging-with-the-debug-gem
  gem "debug", platforms: %i[ mri mingw x64_mingw ]
end

So when running tests, the debug gem could be automatically required and be used to debug tests.
And because CI runs tests with test environment, the debug gem would be required there too.

So you mean that

most of programmers don't want to debug by debug.gem, especially on test group
but it is required because Rails inserts it to Gemfile by default
most of programmers don't want to use any debug.gem features until it calls debugger method

So the gem "debug.gem" is not assumed that "require it when debug it" but introduce debugger command by many people, you say.

Sorry for the delay.

So the gem "debug.gem" is not assumed that "require it when debug with it" but introduce debugger command by many people, you say.

Yes that's the feedback I got from many devs, also my personal expectation.
I understand that the goal is debug will become a completely built-in tool, which users won't need to add debug in their Gemfile at all. And when that happens, require "debug" could just mean "start debugging" and calling debugger would be redundant (like the most early design of debug did, which would start the console when required).
But at the moment and in near future, debug is still better to be treated as a gem because

It's easier to receive bug fix/enhancement through gem releases than upgrading Ruby
Old Ruby version always need to receive updated debug as a gem

Therefore, making its activation behaviour similar to other gems (e.g. pry, byebug) can make users adopting it quicker and benefit from its power.

I understand that the goal is debug will become a completely built-in tool, which users won't need to add debug in their Gemfile at all.

At least I don't think such goal.

Given that Bundler.require exists and is used e.g. by Rails, I think it's a fairly well-known expectation that all gems don't do heavy processing or e.g. add TracePoints while they are being loaded, as that could cause significant overhead or incompatibilities.
So +1 for this.
I guess the main use case for require "debug" to start the debugger is for ruby -rdebug some_script.rb.
Maybe that case can be detected and and so the session would be started eagerly only for that case?
When people add gem "debug" in their Gemfile, I would think none of them want that to immediately start the debugging session when they load their app.

ruby -rdebug some_script.rb

OTOH using rdbg ... for that use case seems good enough, so probably no need to treat ruby -rdebug any differently.


Add section to CSS Reference on forcing state on multiple elements

Elements Panel > DOM Tree > Right-Click > Force State
https://twitter.com/ChromeDevTools/status/986992837127319552
https://groups.google.com/d/msg/google-chrome-developer-tools/7vuOpsVQaGs/mI1M2aGJCgAJ
https://developers.google.com/web/tools/chrome-devtools/css/reference#pseudo-class

Digital Marketing! | Work From Home!
Make money online without any expenses!
Our Journey Since 24.12.2012
http://www.mizansurovi1.blogspot.com


Invoking undefined behaviour when using an rvalue in the constructor of stdex::cvector

This is my first pull request :fireworks:, so yeah..., but here you're invoking an undefined behaviour(for count larger then 1) by moving an rvalue into the emplace_back function count times. It'd be fine if you were to move only once, but because you're moving it more than once you can't really expect any other element after the first to be in the valid state inside the the_data member field.
https://github.com/peter-winter/ctpg/blob/99af8d2f712a3bfdfbe37d858fac391da2c78240/ctpg.hpp#L114-L119

Thanks. It is not used anywhere, this constructor literally doesn't ake sense.

Fixed


Have to run source ~/antigen.zsh every time I open the terminal?

I have to source it every time I open the terminal window. And the plugins I added will disappear. How to fix this?

The READ me explains it a bit. In your .zshrc (or wherever you put your configs) after you source antigen you have to use antigen bundle or antigen bundles to load your bundles.
A basic config would look like:
source ~/antigen.zsh
antigen use oh-my-zsh

antigen bundles <<EOBUNDLES
    jimhester/per-directory-history
    zsh-users/zsh-syntax-highlighting
EOBUNDLES

antigen theme robbyrussell

antigen apply

See examples here.

Thanks. It could work.


Potentially Another false Positive for CA2000

See this Stackoverflow question https://stackoverflow.com/q/52520390/6915929
Essentially it is using 'using statements' within a try catch with a filter

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

ID: c370a407-b61d-0de6-6ac4-9b0ab49216b9
Version Independent ID: a96e421e-65d3-07ba-097e-3feff2b3c677
Content: CA2000: Dispose objects before losing scope - Visual Studio
Content Source: docs/code-quality/ca2000-dispose-objects-before-losing-scope.md
Product: visual-studio-dev15
GitHub Login: @gewarren
Microsoft Alias: gewarren

Related to #898

@insulind From your SO post it sounds like you encountered this in VS 2015, which means you are using static code analysis. Do you get this same false positive in the FxCop analyzer version of this rule? If so, please log an issue at roslyn-analyzer issues.

Closing the issue due to inactivity.
If there are any concerns, please comment below.


Some DXF splines converted incorrectly to SVG bezier curves

Sorry to keep blasting you with issues, I wouldn't be asking if your library wasn't extremely useful to me!
I've ran into a somewhat weird problem with splines while converting DXFs to SVGs. I realize that SVG only supports a small subset of the possible splines that DXF supports, and that the dxf library falls back to polylines whenever a DXF spline cannot be represented as an SVG bezier curve. In the DXF below, it seems like one or more splines are being converted to SVG format incorrectly. Converting to polylines instead of SVG does give correct output, so perhaps this is simply a case of a DXF spline that cannot be represented in SVG. I'm sorry that I don't understand enough about splines to be of much help here... what I do know is that the file size is much smaller with native SVG splines, and they're so smooooth....
Here's the weird spline:
https://raw.githubusercontent.com/ericman314/test-arc-bbox/master/dxfs/weird-splines.dxf
Expected output:

Actual output:

Note some parts on the 5 and the 6 that are supposed to be curved, which are flat. Also of note is that the dxf library renders the left side of the 6 as polylines, not bezier curves, and those are correct.
Thank you!

I don't work with DXFs any longer so unfortunately I have limited time to look at issues, but will have a quick look...

I don't work with DXFs any longer

I don't blame you....
I'll keep investigating. I've tried a couple different DXF softwares and this particular drawing is rendered differently in each one. I'll let you know if I find a cause. I'm not even sure what the drawing is supposed to look like.

Fixed
Before:

After:

Released in 4.2.4 - let me know if it fixed your issue

Yes, it's fixed! Thanks


LanguageClient adds an extra --stdio argument when using TransportKind.stdio

Hey,
I'm developing an extension that uses LanguageClient to create an LSP session over stdio, and it looks like the library is passing an extra --stdio argument to the the command. Since the executable that runs the LSP server does not support the --stdio argument, the server crashes.
Here's an example:
new LanguageClient(
	"my_client",
	{
		command: "/path/to/executable",
		transport: TransportKind.stdio,
		args: ["lsp"],
	},
	{
		outputChannel: logger,
		documentSelector: this.generateDocumentSelector(),
		traceOutputChannel: window.createOutputChannel("My LSP"),
	},
);

The binary that runs the LSP server expects the command to be /path/to/executable lsp
But the library appends an additional --stdio argument: /path/to/executable lsp --stdio, and since it's not supported by the command, it fails.
This can be an issue when the developer that creates the LSP client does not also maintain the LSP server, because he might be unable to adapt it to match the currently required behaviour.
Could this be removed? If not, would it be possible to explain why this argument is necessary?
Happy to contribute the change.

It is there because it is an implementation recommendation of the spec (https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#implementationConsiderations).
However you can always pass a function as the server options which gives you full control on how the server is launch, including all command line arguments.
See
(() => Promise<ChildProcess | StreamInfo | MessageTransports | ChildProcessInfo>)

here: https://insiders.vscode.dev/github/microsoft/vscode-languageserver-node/blob/dbaeumer/personal-pinniped-aqua/client/src/node/main.ts#L126


[Plugin] Response Transformer

Response transformer plugin, to add/remove headers and JSON parameters from a response before sending it to the client.

Changes Unknown when pulling 14bb709c78c0fe592e5087c7f53d0494955b606d on feature/response-transformer into ** on master**.

Changes Unknown when pulling 14bb709c78c0fe592e5087c7f53d0494955b606d on feature/response-transformer into ** on master**.

Changes Unknown when pulling 14bb709c78c0fe592e5087c7f53d0494955b606d on feature/response-transformer into ** on master**.


chore: add more utils to docker images

Closes https://github.com/fedimint/fedimint/issues/5954
Busybox is very complete. curl and rsync may be also be util.

What does busybox add?

What does busybox add?

@m1sterc001guy It adds a bunch of UNIX utilities (check below), but @douglaz do we need all of that ?

I know from experience that we only find out we need it when most need it in debugging, so I might be biased. 😅

What does busybox add?

@m1sterc001guy It adds a bunch of UNIX utilities (check below), but @douglaz do we need all of that ?

It provide many useful commands but it's also very lightweight:
 ls -lh /nix/store/6723i29mnr4gib2qp5vahfr7xv7h8ad8-busybox-1.36.1/bin/busybox
-r-xr-xr-x 1 root root 1.2M Jan  1  1970 /nix/store/6723i29mnr4gib2qp5vahfr7xv7h8ad8-busybox-1.36.1/bin/busybox

So there is no reason to not add it.

It provide many useful commands but it's also very lightweight:
 ls -lh /nix/store/6723i29mnr4gib2qp5vahfr7xv7h8ad8-busybox-1.36.1/bin/busybox
-r-xr-xr-x 1 root root 1.2M Jan  1  1970 /nix/store/6723i29mnr4gib2qp5vahfr7xv7h8ad8-busybox-1.36.1/bin/busybox

So there is no reason to not add it.

Oh, got it. Thanks!


org.openrewrite.recommendations.CodeStyle Changes a class's visibility when it shouldn't.

Design partner provided a case where org.openrewrite.recommendations.CodeStyle removed public from a class. This caused compiler errors in the project, as the class was referenced elsewhere in the project.

Not an exact copy of the code that was changed, but similar:

import org.springframework.context.annotation.DependsOn;

public class ExampleImpl extends extends AnotherClassImpl {
  public ExampleImpl() {
    super();
  }
}

This ended up being a parsing issue when a comment immediately followed an annotation without a whitespace character.


Service client

Same as before, but now the client can be updated. Every client will have a load balancer layer. I shall comment below. Obviously, this still needs tests and documentation.
@aliyakamercan @jlbelmonte @amotamed @dxuhuang @DanSimon

Codecov Report

Merging #637 into develop will decrease coverage by 0.2%.
The diff coverage is 73.68%.

@@             Coverage Diff             @@
##           develop     #637      +/-   ##
===========================================
- Coverage    84.78%   84.57%   -0.21%
===========================================
  Files           99      101       +2
  Lines         4435     4480      +45
  Branches       354      350       -4
===========================================
+ Hits          3760     3789      +29
- Misses         675      691      +16

Impacted Files
Coverage Δ

...lossus/src/main/scala/colossus/service/Async.scala
50% <ø> (ø)
:arrow_up:

...in/scala/colossus/service/AsyncServiceClient.scala
87.17% <0%> (-7.27%)
:arrow_down:

...ain/scala/colossus/service/ServiceClientPool.scala
100% <100%> (ø)
:arrow_up:

...c/main/scala/colossus/protocols/http/package.scala
30.76% <100%> (ø)
:arrow_up:

...protocols/http/streaming/StreamingHttpClient.scala
100% <100%> (ø)
:arrow_up:

...ain/scala/colossus/protocols/http/HttpClient.scala
88.88% <100%> (-1.12%)
:arrow_down:

...s/src/main/scala/colossus/service/ServiceDSL.scala
81.13% <55.55%> (-2.55%)
:arrow_down:

...src/main/scala/colossus/service/LoadBalancer.scala
65% <65%> (ø)

...n/scala/colossus/service/LoadBalancingClient.scala
85.48% <66.66%> (-1.19%)
:arrow_down:

.../scala/colossus/service/LoadBalancerSettings.scala
66.66% <66.66%> (ø)

... and 7 more

Continue to review full report at Codecov.

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

Going to re-open as a new PR... again :)


HOTFIX: Fix invalid long format conversion in request logger message

Merging to trunk and 0.11.0.


Implement Wave Spawning

References #218
I will work on implementing the wave spawning option to the AISpawnerController. This will wait to respawn the AI until all the AI are dead and will then respawn all the AI according to maxAI in a "wave"

This definitely took some more time to implement as I spent time deciding the best way to do it. There's some new properties: waveSize and waveIncrement. AI will keep spawning until the waveSize is reached and a new wave will not spawn until all the AI are dead. waveSize is incremented by waveIncrement, so gradually scaling waves can be designed. In addition, waveSize overrides MaxAI. I think the system can be refined at a later date, (for more specified waves) but for now it'll work well as a novelty. In the future, probably want to disable AI targeting other AI in this mode.


Document is out of date

The documentation need to be updated.

The instruction of how to build and push container image is not correct with Makefile.
Missing namespace in CLIENT_POD=$(kubectl get pod  -l app=client-test -o jsonpath={.items..metadata.name})

There are too many ways(YAML files, HelmChart, GMC) to install OPEA and pipeline, which can make users feel confused. Is it possible to provide a single, unified installation method if they can be used interchangeably?
If multiple methods need to be maintained, please describe the use cases for each method separately. This way, users can choose the installation method that suits them best.

At the same time, there are too many manifests under different components (GenAIInfra, GenAIExample), which result in high maintenance costs and inconsistencies.

Can the documentation describe how to deploy OPEA and pipeline that running behind a proxy.

Can the documentation describe how to deploy OPEA and pipeline that running behind a proxy.
I did this recently, but I have so much work backlogged, and I am not an official OPEA maintainer, so I will defer this to someone else.
I dont think that there are too many different ways to setup OPEA, but it sounds like what you really think, is that there needs to be a CLI (or maybe LLM) to walk non technical users through their options.

GMC's doc is updated by #321 and #332

One readme update here
https://github.com/opea-project/GenAIExamples/pull/640

Could we close this?


Interface to Cardinal or MALDIquant

Hi:
Thank you for developing this software.
Do you have designed interfaces to software, like Cardinal and MALDIquant.
By the way, an example is really appreciated.
Thank you!
Peifeng Ji

Hi,
Thank you for your interest!
MSIWarp can be interfaced to Cardinal and MALDIQuant implicitly by loading and saving files in the .imzML format.
There is a complete example notebook of how to align a data set from MetaboLights in the example folder (warp_orbitrap_desi_imzml.ipynb).
The readme file also summarizes how to use MSIWarp together with pyimzML (although with the code to setup alignment parameters is omitted)
I hope those examples can help you!
Jonatan


boards: weact: usb2canfdv1: fix broken link

Fix broken link to the usb2canfdv1 default board configuration file.
Fixes: 25d9fc118f61c049a58858703ea354a1b833ca6d

I've been wanting to instrument the Sphinx role to allow checking for dead links so maybe it's time I finally do it :)

That would be awesome.

I've been wanting to instrument the Sphinx role to allow checking for dead links so maybe it's time I finally do it :)

That would be awesome.

#80530


Added a section to create a new history.

And fixed formatting issue in data upload section.

Ok, made the change and pushed.

Thank you both!


Fix NOTIFICATION_SORT_CHILDREN is called twice on startup

Fixes: https://github.com/godotengine/godot/issues/92644

Is it better to rearrange them based on their call order?

Thanks!


Can't completely style button in snackbar without !important

Hi React Toolbox,
I am trying to style the button in the snackbar - specifically, to make the text color white and remove the fixed height. I am able to pass styles through the theme property (I changed the background to pink to be sure), but the font color and height of the button get overwritten unless I flag them as important. Please help?
Thanks,
Laura
.button {
    margin: 0;
    padding: 0;
    color: #fff !important;
    font-family: 'Open Sans';
    line-height: 20px !important;
    height: auto !important;
    font-weight: 600;
    font-size: 14pt;
    background-color: pink;
}

        <MaterialSnackbar
          label={message}
          action={actionLabel}
          onClick={handleClick}
          active={true}
          type='accept'
          timeout={1000}
          theme={{ snackbar: styles.snackbar, label: styles.label, button: styles.button }}
        />

It's probably a specificity issue (i.e. your styles are getting overwritten by a rule with higher specificity). It's not the prettiest solution, but try giving your rule higher specificity, e.g. by including the button tag name in the rule.

This is an issue with the Button component as well, because of the :not([disabled]) selector.

This is affecting pretty much any component that has alternate states. I've not been able to find a good workaround for this yet.

@rubenmoya Please comment
How to override your styles? I'm also using !important everywhere, but it's an awful solution.
I don't want to use react-themr or something else.
Maybe throw away CSS modules ?)


Add support for implicit bootstrapping of modules

As of cake-build/cake#2849, modules are automatically bootstrapped before running the script. While it's still possible to do it explicitly with the --bootstrap option, it's no longer necessary. Instead, a new option has been introduced to opt out of the bootstrapping process called --skip-bootstrap.
The Cake action should reflect these changes both in the code and in the documentation.

@ecampidoglio what if I chose to set cake-version to 0.38.5? I would need the "old" --bootstrap option. Would it be possible to change the cake-bootstrap setting to accept

bootstrap (equivalent to true for compatibility) to pass --bootstrap and
skip to pass --skip-bootstrap.

The documentation for this, then, should state that setting cake-bootstrap: bootstrap is only valid for Cake versions < 1.0.0 and, in turn, setting cake-bootstrap: skip is only valid for Cake versions >= 1.0.0.

0.* going out of support in a week or so, perhaps that concern can be skipped?

Sure, that sounds reasonable.

Resolved by 3dc8398.


AutoDLL not working in NextJS

I have tried implementing autodll in nextjs environment but its not excluding the vendor pages from chunks such as main.js, common.js, app.js, index.js.
config.plugins.push(
new AutoDllPlugin({
inject: true, // will inject the DLL bundles to index.html
filename: '[name].js',
entry: {
vendor: [
'react',
'react-dom',
'styled-components',
]
}
})
);

That's because we already use this plugin internally in Next.js


feat: add possibility to set external_location for incremental model on iceberg table

Description
Add possibility to set external_location for incremental model on iceberg table.
So in this way we can avoid to use uuid on table path and use a naming convention on Data Lake , apply Data Governance rules, better organize the Data Lake.
#559
Checklist

[x] You followed contributing section
[x] You kept your Pull Request small and focused on a single feature or bug fix.
[ ] You added unit testing when necessary
[ ] You added functional testing when necessary

@rokity now the code looks good, but we have some functional tests that check for location uniqueness - specifically check this section of the code
@Jrmyy what @rokity proposed here seems fine for me. In case of incremental loads, we are safely use a not unique location.
The only part that I'm concern about, are case of when we do --full-refresh, but based on this issue: https://github.com/dbt-athena/dbt-athena/issues/286 we should be fine.

@Jrmyy have a look please - for consistency we might want to consider to support ha=false for iceberg, that doesn't use a rename feature and allows "specific" locations if they are required.

if we remove the default ha behaviour for Iceberg
we don't have necessary to remove the default ha behaviour for iceberg, but allow ha=false with possibility to use external location and also not unique location. Doing so the user pick what it's the best for the setup that she/he might have.


Attacks on medical images

Hello, I am new on adversarial attacks, I checked nearly all the examples. Especially Mnist examples look super easy to apply. However, I want to attack some segmentation models for medical images. I just cannot figure out where to start, how can I apply ART for more complex models? If a model is written in pytorch should I have to use ART's pytorch wrappers? Thanks.

Hi @furkandurmus
Thank you for exploring ART! I think this should be possible, although currently you would have to adapt or implement an new estimator for the segmentation model by following the estimators for classification or object detection. Estimators for object segmentation is on our list of features we would like to support in future releases.


Undefined property: Illuminate\Database\Eloquent\Relations\HasMany::$orWhere

Laravel Version
10.45.0
PHP Version
8.3.3
Database Driver & Version
mysql
Description
Hi,
I upgrade each week to the latest Laravel. When I upgraded today from 10.44.0 to 10.45.0 and I am now getting this stack trace.
2024-02-20 21:29:08] web.ERROR: Undefined property: Illuminate\Database\Eloquent\Relations\HasMany::$orWhere {"exception":"[object] (ErrorException(code: 0): Undefined property: Illuminate\Database\Eloquent\Relations\HasMany::$orWhere at
The Line in my code looks like this:
->when(!$series, function ($query) {
$query->notSeries()->orWhere->book()->orWhere->speaker();
})
This has worked for a long time (years) and stopped today.
I looked through the fixes that went into 10.45.0 and can't seem to determine what might have caused it.
I just reverted back to 10.44.0 and it's working again so I am sure it's in 10.45.0.
Thanks!
Steps To Reproduce
n/a (not sure how to reproduce short of the code I wrote above)

This is caused by #50124 we already pinned v10.44 due to massive failures.

added a PR with a currently failing test that passes with v10.44 and below #50176

The same issue also

Not sure if exactly related, but I'm also having an issue caused by https://github.com/laravel/framework/pull/50124 in a Laravel Nova project.
Being more specific, the trait Illuminate\Support\Traits\Tappable that was added to the Relation class seems to cause a type hint problem with our custom Nova filters and a few other Nova methods. For example:
App\Nova\Resource::indexQuery(): Return value must be of type Illuminate\Database\Eloquent\Builder, Staudenmeir\EloquentHasManyDeep\HasManyDeep returned {"userId":2,"exception":"[object] (TypeError(code: 0): App\\Nova\\Resource::indexQuery(): Return value must be of type Illuminate\\Database\\Eloquent\\Builder, Staudenmeir\\EloquentHasManyDeep\\HasManyDeep returned at /srv/app/Nova/Resource.php:31)
The indexQuery method came directly from Nova docs and wasn't even modified by us.
App\Nova\Filters\Subscriptions\Type::apply(): Return value must be of type Illuminate\Database\Eloquent\Builder, Illuminate\Database\Eloquent\Relations\HasManyThrough returned {"userId":2,"exception":"[object] (TypeError(code: 0): App\\Nova\\Filters\\Subscriptions\\Type::apply(): Return value must be of type Illuminate\\Database\\Eloquent\\Builder, Illuminate\\Database\\Eloquent\\Relations\\HasManyThrough returned at /srv/app/Nova/Filters/Subscriptions/Type.php:32)
This one is a custom filter we have. It is defined using Nova 3 way of creating filters, and although our project is currently using Nova 4, it worked just fine until Laravel 10.45.
Again, removing the trait ´TappablefromRelation` seems to solve the issue.
I'm probably opening a new issue for this if it doesn't get fixed in 10.46, but until that, I'll at least add these details.


Add support for a GUI, virtio-input and virtio-gpu devices

I added command line support for the user to add virtio-gpu and virtio-input devices which also ties into having a good experience with the newly added gui compatability.
I added command line support for the user to start a graphical application window when their virtual machine starts through the --gui flag (assuming the user added a virtio-gpu device as well).
I also added some mutual exclusion during creation of the virtual machine configuration. Without calling runtime.LockOSThread(), starting the virtual machine subsequently starting a graphic application window would result in a SIGILL error. Alongside calling runtime.LockOSThread(), I parallelized the running of the graphic application window and checking the status of the virtual machine. Otherwise, the two wouldn't be able to run simultaneously.
These new features can be testing using a command similar to this:
$ ./out/vfkit --cpus 2 --memory 2048 \
--bootloader efi,variable-store=/Users/jakecorrenti/efi-variable-store,create \
--device virtio-serial,stdio \
--device virtio-fs,sharedDir=/Users/jakecorrenti,mountTag=dir0 \
--device virtio-blk,path=/Users/jakecorrenti/Downloads/Fedora-Server-dvd-x86_64-38-1.6.iso \
--device virtio-net,nat,mac=72:20:43:d4:38:62 --device virtio-input,keyboard --device virtio-input,pointing --device virtio-gpu,display --gui

ok-to-test

/ok-to-test

LGTM

please be aware that the git title is too long and gets broken up. best to just write 'gui' instead of the full 'graphical user interface' as I care more about the addition of the last words: virtio-gpu devices

please be aware that the git title is too long and gets broken up. best to just write 'gui' instead of the full 'graphical user interface' as I care more about the addition of the last words: virtio-gpu devices

Since you bring this up, I would have preferred (at least) 3 separate commits, each doing one specific thing, "add virtio-input support", "add virtio-gpu support", "add gui support". This also helps with the shortlog length ;)

I would have preferred (at least) 3 separate commits,

Didn't want to be so picky at first, but the description talks about the "I added", "I also added", which refers to these, right. Prefer not to see 'I' in a description either. More like 'This adds'

I would have preferred (at least) 3 separate commits,

Didn't want to be so picky at first, but the description talks about the "I added", "I also added", which refers to these, right. Prefer not to see 'I' in a description either. More like 'This adds'
Let's say, for future commits to separate them?

Fixed. I fixed the PR info but forgot to actually change the commit. Also, feel free to be picky. I want this to be a quality contribution

please be aware that the git title is too long and gets broken up. best to just write 'gui' instead of the full 'graphical user interface' as I care more about the addition of the last words: virtio-gpu devices

Since you bring this up, I would have preferred (at least) 3 separate commits, each doing one specific thing, "add virtio-input support", "add virtio-gpu support", "add gui support". This also helps with the shortlog length ;)

I can definitely see this being better, I had the habit of squashing everything. I think it would be beneficial to have some sort of CONTRIBUTING.md file to have a location for contributors to see what you want for a PR so you don't have to make the same change requests.

we prefer small(er) commits as we have been in situations where bisect was required.


⚠ SkipTheTrailers has degraded performance

In 1d1a1e3, SkipTheTrailers ($STT) experienced degraded performance:

HTTP code: 200
Response time: 17045 ms

Resolved: SkipTheTrailers performance has improved in 2ea417d.


feat(api) Messages Include Annotation Data

User Story
As an end user using LeapfrogAI to "chat with my docs"
I want to see annotations with my RAG responses
So that I can attribute the source of the generated response
Acceptance Criteria
Given an Assistant exists with one or more files for RAG
When one or more of those files is used to generate a response
Then the returned Message should include file_citation and file_path annotation information
Additional context

API Documentation for messages
Description of Message annotations

The annotations are implemented, however they are always present instead of only including them when the source was actually used in the response:

Handled by https://github.com/defenseunicorns/leapfrogai/issues/669


qintelqsentry: New App - Initial Commit of the Qintel QSentry App

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[X] Testing of all the changes has been performed (for bug fixes / features)
[X] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[X] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[X] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[X] Verify all checks are passing.
[X] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[X] Do NOT submit updates to dependencies unless it fixes an issue.
[X] Limit your pull request to one application and submit multiple pull requests if necessary.

Pull Request Type
Please check the type of change your PR introduces:

[X] New App
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Release Notes (REQUIRED)

initial release, providing the ip reputation action

What is the current behavior? (OPTIONAL)

NA

What is the new behavior? (OPTIONAL)

New App

Other information (OPTIONAL)
Pay close attention to (OPTIONAL)
Screenshots (if relevant)

Thanks for contributing!

Hi @calvin-qintel, could you please provide me the access rights to this repo(qintel:feat/qsentry_app)?

The changes of this PR are incorporated into this- #2


Preparing for 1.0 release

It's time to start publicly planning for the upcoming 1.0 release. We've had to push back our initial timeline due to a couple outstanding issues: one for a cluster performance regression, another for feature parity.

Webapp cluster performance issue https://github.com/graphite-project/graphite-web/issues/1690
Timeseries merge (no issue exists but I believe @DanCech is planning for this)

Raintank has devoted many engineer hours to the aforementioned "architectural regression" and is making great progress. To hasten things along, and with a personal desire to decrease the project's dependency on my own availability, I've elevated @deniszh, @iksaif, and @DanCech to core team members.
If we intend to move forward with the 1.0 version, various docs will need to be updated accordingly. I haven't identified these yet but it shouldn't be hard to track them down.
Based on my notes, here are the steps I used for the 0.9.14 release. These should be adapted as needed for a release from the master branch for each of the Graphite projects (graphite-web, carbon, whisper, ceres, and carbonate). I'll leave it up to the other maintainers as to whether it makes sense to "version align" Carbonate alongside the major components.

bump the version in setup.py
git tag the new version
push both to origin
launched a new Synthesize vagrant (this clones and checks out the 0.9.14 release)
inside the checkout for each, sudo python setup.py sdist
extract the PKG_INFO file from each tarball
login to https://pypi.python.org/pypi
for each project, submit PKG_INFO to https://pypi.python.org/pypi?%3Aaction=submit_form
upload source distribution tarball for each release ("files")

Currently we have myself, @mleinart, @iksaif, and @jssjr as PyPI package maintainers. I'd like to add @deniszh and @DanCech as well but I'll need your PyPI usernames.
I know there's plenty of other stuff to discuss so just consider this a bootstrapping for further conversation.

/cc @graphite-project/committers

I'm fine with the current trunk of graphite-web/carbon/whisper, it's what
has been running in production for almost a year. The external projects
(carbonate, biggraphite, etc..) will quickly adapt after the release.
While doing the release, could you create a wiki page describing the steps
? That would help for the next one :).
I'd just like to upstream
https://github.com/criteo-forks/carbon/commit/0bed7c78c35e7b9777cb2a2f7c18a11e225e828b
for carbon first, which I'll do next week.
Also, do we have a list of breaking changes and upgrade instructions ? That
would be nice to advertise them somewhere.
On Sun, Feb 12, 2017 at 12:07 AM, Jason Dixon<EMAIL_ADDRESS>wrote:

/cc @graphite-project/committers
https://github.com/orgs/graphite-project/teams/committers
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/1823#issuecomment-279182463,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_DAzXWyLcOAAuGgk4_5PflDEQVpsswks5rbj8VgaJpZM4L-VCD
.

--
Corentin Chary
http://xf.iksaif.net

Apologies, REMOTE_STORE_MERGE_RESULTS already exists in master. I think I meant to refer to parallel fetch but I suspect the proposed cluster changes will incorporate this functionality. Does this sound right to you @DanCech?

@iksaif http://graphite.readthedocs.io/en/latest/releases/0_10_0.html#upgrading
Yes, a wiki page should be created, but I'd like to see it put together by whoever manages this release. The notes I added above are a couple years old and iirc there were some problems with the pip packages in 0.9.15 so they should be taken with a grain of salt.

@obfuscurity yes, the optimizations discussed in #1063 are included in #1818

By the way, since the changes are massive for this release, would it make
sense to tag a RC for each projects, advertise it, and accept only fixes
for the next few weeks on these branches ?
On Sun, Feb 12, 2017 at 7:46 PM, Dan Cech<EMAIL_ADDRESS>wrote:

@obfuscurity https://github.com/obfuscurity yes, the optimizations
discussed in #1063
https://github.com/graphite-project/graphite-web/issues/1063 are
included in #1818
https://github.com/graphite-project/graphite-web/pull/1818
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/1823#issuecomment-279238852,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_DA-joFpuqCdubdusYLvp3Gw6oJvM1ks5rb1OOgaJpZM4L-VCD
.

--
Corentin Chary
http://xf.iksaif.net

I think we should do that after merging that massive changes, indeed.

To go forward, I propose:

create the 1.0.x branch on monday for each sub-project and tag a rc1
publish a pre-release (at least a github) and advertise it on the mailing
list / irc for people to test
wait two weeks until we decide if we need a rc2 or if we can go forward
with a full release

On Fri, Feb 17, 2017 at 10:54 AM, Denis Zhdanov<EMAIL_ADDRESS>wrote:

I think we should do that after merging that massive changes, indeed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/1823#issuecomment-280606523,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_DA7tpvDXegPZsoUoGrXtlYEU9xzylks5rdW5PgaJpZM4L-VCD
.

--
Corentin Chary
http://xf.iksaif.net

Going forward with RC w/o merging #1818 ?

I'd be very hesitant to call it an rc without #1818 or similar.  I'm on vacation this week but will be back in action Monday and can push through any remaining issues with #1818.

Good point, let's move this plan by one week then :).
On Thu, Feb 23, 2017 at 2:34 PM, Dan Cech<EMAIL_ADDRESS>wrote:

I'd be very hesitant to call it an rc without #1818
https://github.com/graphite-project/graphite-web/pull/1818 or similar.
I'm on vacation this week but will be back in action Monday and can push
through any remaining issues with #1818
https://github.com/graphite-project/graphite-web/pull/1818.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/1823#issuecomment-281992443,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_DAy4shpd47KCeR29WLbNFzVfj2fqdks5rfYrigaJpZM4L-VCD
.

--
Corentin Chary
http://xf.iksaif.net

Any news, here?
Looking forward to 1.0 :-)
regards
christian

Any latest news around Graphite 1.0 release date? Cannot wait to get my hands on it.

According to milestone major blocker is #1690 - but we have good news - fix is in #1818  and under review now.
@kkdk5535 - you can try to test master branch with #1818 applied and share your results  - it will make 1.0 release much faster. 😸

Let's tag whisper and carbon to 1.0-rc1 on monday, and tag graphite-web as
soon as https://github.com/graphite-project/graphite-web/pull/1818 is
merged.
Does that work for you ?
On Thu, Mar 16, 2017 at 9:36 PM, Denis Zhdanov<EMAIL_ADDRESS>wrote:

According to milestone
https://github.com/graphite-project/graphite-web/milestone/2 major
blocker is #1690
https://github.com/graphite-project/graphite-web/issues/1690 - but we
have good news - fix is in #1818
https://github.com/graphite-project/graphite-web/pull/1818 and under
review now.
@kkdk5535 https://github.com/kkdk5535 - you can try to test master
branch with #1818
https://github.com/graphite-project/graphite-web/pull/1818 applied and
share your results - it will make 1.0 release much faster. 😸
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/1823#issuecomment-287183353,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_DA7_O-SjTjPKQ24KamrRlF7RV0PoHks5rmZ1OgaJpZM4L-VCD
.

--
Corentin Chary
http://xf.iksaif.net

If nobody disagrees today I'll branch 1.0.0 for carbon/whisper/graphite-web tomorrow and create a rc1 tag

Doing that now.

https://github.com/graphite-project/whisper/releases/tag/1.0.0-pre1
https://github.com/graphite-project/carbon/releases/tag/1.0.0-pre1

Looking forward to it. Will give it a spin

@iksaif : Indeed, 0.9.13-pre1 created many confusions in the past.

Can influencial twitter people encourage users to test 1.0.0-pre1 ? :)
It would be great to do a release next week if there isn't any blocker.

Not sure if I influential, but will try to ask my 600 followers to do that.
@obfuscurity, is it possible for you to ask your 5K followers to do so too, please? :)

@deniszh Is there an authoritative page I can point users to or is it assumed they'll figure out how to install the RC?

@obfuscurity,
Good question, indeed. Should we create a separate page or install current master is enough? @iksaif @DanCech
Then we need to point users to https://graphite.readthedocs.io/en/latest/install-source.html#installing-from-source, and I just found out that download link there is broken - we should point it to Github instead of launchpad - #1880 👿

Looks like we have no proper download page. Maybe we should fix that before release too. :(
Or even asap, and put RC there.

Or maybe just point user on https://graphite.readthedocs.io/en/latest/install-pip.html#installing-in-the-default-location to test the last master - that's the fastest way. Thoughts?

https://twitter.com/obfuscurity/status/846417810804948992

Thanks, @obfuscurity! I retweet with citation: https://twitter.com/deniszh/status/846437032582877184
And congrats on a finishing line of the book, Jason!

@deniszh there is https://github.com/graphite-project/graphite-web/releases I guess: pip install https://github.com/graphite-project/graphite-web/archive/1.0.0-pre1.zip

@iksaif: Yes, for Graphite web - but we have whisper and carbon too.

https://github.com/graphite-project/carbon/releases works too .. But it's true that there isn't one single page to do that.
Another thing: there are a few commits on master that we may want on 1.0.x (https://github.com/graphite-project/graphite-web/compare/1.0.x...master). I'll let you choose which ones.

Related to https://github.com/graphite-project/graphite-web/compare/1.0.x...master, what is our current merge path ?
Merge PR to 1.0.x if they qualify, then merge back to master ?
Merge everything to master, and cherry-pick to 1.0.x ?

I think second one, master is a bleeding edge, and we're cherry-picking
commits to release branch and tag releases there
On Wed, 29 Mar 2017 at 07:22, Corentin Chary<EMAIL_ADDRESS>wrote:

Related to 1.0.x...master
https://github.com/graphite-project/graphite-web/compare/1.0.x...master,
what is our current merge path ?
Merge PR to 1.0.x if they qualify, then merge back to master ?
Merge everything to master, and cherry-pick to 1.0.x ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/1823#issuecomment-289985649,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABK51prn-Ri-UEBOT1l-DO5Wet8tO3tXks5rqep-gaJpZM4L-VCD
.

Do you think it's realistic to target wednesday ?

I wanted to propose Thursday, but Wednesday is even better. Let me sync latest changes and put date first.

I set April 12 as the release date for 1.0.0 and 0.9.16 and push changes to 0.9.x, 1.0.x and master branches.

OK, I tagged releases already, prepared PKG_INFO and going to upload packages to PyPI. A little bit out of schedule, but...
It's the last chance to fix something, though.
Any objections, corrections, etc? @obfuscurity @iksaif @DanCech

LGTM
Le 11 avr. 2017 22:13, "Denis Zhdanov"<EMAIL_ADDRESS>a écrit :
OK, I tagged releases already, prepared PKG_INFO and going to upload
packages to PyPI. A little bit out of schedule, but...
It's the last chance to fix something, though.
Any objections, corrections, etc? @obfuscurity
https://github.com/obfuscurity @iksaif https://github.com/iksaif
@DanCech https://github.com/DanCech
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/1823#issuecomment-293386358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_DA0g-5Eyf__ACbd5NgvenGdTu6yVAks5ru97LgaJpZM4L-VCD
.

OK, everything is finished now. It's almost midnight in CET, so, we're almost on time.
Let's promote release tomorrow, in twitter and chats.
And let's celebrate, of course!

Oh yeah
On Tue, Apr 11, 2017 at 2:58 PM, Denis Zhdanov<EMAIL_ADDRESS>wrote:

Closed #1823
https://github.com/graphite-project/graphite-web/issues/1823.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/1823#event-1039183081,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALCw-HsigfJnZdm8YnnyyBhTpTPVxtNgks5ru_d0gaJpZM4L-VCD
.

Woohoo ! thanks for the hard word this finish to wrap up evertyhing

Thanks, @iksaif ! We're all made this possible.
Jason, could you please make announce in your twitter? Or should I do? /cc @obfuscurity

I posted https://news.ycombinator.com/item?id=14095347 (but it isn't exactly neutral :P)

That's fine IMO. :) Thanks!

I hope that @obfuscurity and @mjulian will mention release in Monitoring weekly too ;)

It's already in the queue. 😄

Nice work everyone!


Is this project really active?

Many links do not work, pages do not load, get access denied like messages etc... Perhaps the project is abandoned

inactive, not abandoned...
On Sun, Mar 19, 2017 at 1:51 PM, Ashok Chilakapati<EMAIL_ADDRESS>
wrote:

Many links do not work, pages do not load, get access denied like messages
etc... Perhaps the project is abandoned
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zorba-processor/zorba/issues/5, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP3W0vBJ67Su3mw88EzcOPQ_t0f1jkOks5rnWsSgaJpZM4Mhz3b
.

--
Rod.O

I had the same thought.  Seems like an interesting concept that might be useful to my project. Perhaps someone could put an update on the blog - is there a plan and schedule for 4.0?

Still a very interesting project. It is a pity that it is not under active development. Even though it is usable in a productive environment as long as you can maintain it yourself.

The project is currently based on volunteers, any participation is appreciated.


Don't allow zero reward durations.

Resolves #327.
Previously a rewards duration of zero was allowed. This is suboptimal because should the admin set a zero rewards duration there are a few places where we'd run into divide by zero errors. This adds the needed checks to be sure a zero reward duration is not set.

Codecov Report

Merging #349 (f09c9ef) into main (b5f2b08) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #349      +/-   ##
==========================================
+ Coverage   96.92%   96.93%   +0.01%
==========================================
  Files          37       37
  Lines        8284     8323      +39
==========================================
+ Hits         8029     8068      +39
  Misses        255      255

Impacted Files
Coverage Δ

...tracts/stake-cw20-external-rewards/src/contract.rs
98.92% <100.00%> (+0.03%)
:arrow_up:

Continue to review full report at Codecov.

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


Adaptive deadline parser

Fixes the yaml parser to accept a multitude of deadline formats, and simply converts to the expected format.

Coverage increased (+0.4%) to 36.275% when pulling 94ce170891255dac96b54fdd94974b3879f0f402 on adaptive-deadline-parser into e89c5e2043ac5167a663b8448eee3e83428174bf on master.


fix: drag to re-arrange custom columns not working

resolves: #1282
Broken by #1013. Can't use prop spreading with our Button component.
Revert to previous button. Needs silverheels cherry-pick.

Any reason to not allow prop spreading any unknown props to our button? There's probably just some specific event handler we don't explicitly add to our button that react beautiful dnd uses

This is one of the exceptions to the rule I think. The button component has a bunch of extra HTML props that it can/should be able to accept (it should be a superset of the base button). So it would be silly to explicitly add every prop instead of spreading those we don't handle in some specific way


Adding custom exception when cache insert fails because of too many columns

Adding custom exception to fix scenarios like https://github.com/huggingface/datasets-server/issues/731

Codecov Report
Base: 90.14% // Head: 92.00% // Increases project coverage by +1.86% :tada:

Coverage data is based on head (fa6166d) compared to base (7cc7367).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #749      +/-   ##
==========================================
+ Coverage   90.14%   92.00%   +1.86%
==========================================
  Files          99       33      -66
  Lines        5051     2214    -2837
==========================================
- Hits         4553     2037    -2516
+ Misses        498      177     -321

Flag
Coverage Δ

jobs_mongodb_migration
?

libs_libcommon
?

services_admin
?

services_api
?

workers_datasets_based
92.00% <100.00%> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ets_based/src/datasets_based/workers/first_rows.py
82.17% <100.00%> (-0.05%)
:arrow_down:

...rs/datasets_based/tests/workers/test_first_rows.py
97.50% <100.00%> (+0.13%)
:arrow_up:

.../migrations/_20221116133500_queue_job_add_force.py

...grations/_20221117223000_cache_generic_response.py

...grations/_20230126164900_queue_job_add_priority.py

libs/libcommon/src/libcommon/queue.py

libs/libcommon/src/libcommon/dataset.py

services/api/src/api/prometheus.py

services/api/src/api/routes/webhook.py

... and 59 more

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

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

Thanks! That's not really what I had in mind. I thought we could instead add a new env var to set the maximum number of columns (features) supported in /first-rows, and check this early in the function (as soon as we have the features), and then raise if the number of features is above the limit.
Then, once deployed in prod, we refresh the /first-rows endpoint for the affected datasets -> they should now have this error, which is more explicit.

Got it, it will first validate if the amount of columns exceeded the limit but what if even having a less number of columns but the content without rows is also too long that exceeds the rows_max_bytes?  I think another kind of error could be thrown for now or just leave it as it is as unexpectederror

Yes, two cases are missing:

too many columns, compared to the new configuration parameter that we need to create -> TooManyColumnsError
truncated content is still too big compared to the max number of bytes of the response -> it's an internal error because it should be the result of an incoherent set of configuration parameters, ie: we could fix it by reducing the max number of column, or by increasing the min size of the response, or else. But you're right, it should be a new error, something like: TooBigTruncatedContent, something like that


Disable/Enable OpenXR Device during runtime

Describe the bug
Hi, I need to switch between mulitple devices during runtime (Desktop, HP Reverb G2 and Hololens 2). Currently, I'm working on the device switch between Desktop and VR. When I disable XR with StopXR() and try to enable it afterwards with StartXR(), then I'm not able to provide Inputs to the motion controllers anymore. The headset is working fine, I'm able to see the controllers but an input is not possible anymore. If there is any ohter way to do this, I would be happy about any advice.
For this I'm using the following code:
    `public void StartXR()
    {
        Debug.Log("Initializing XR...");

        XRGeneralSettings.Instance.Manager.InitializeLoaderSync();
        XRGeneralSettings.Instance.Manager.StartSubsystems();

    }

    public void StopXR()
    {
        Debug.Log("Stopping XR...");

        XRGeneralSettings.Instance.Manager.StopSubsystems();
        XRGeneralSettings.Instance.Manager.DeinitializeLoader();
        Debug.Log("XR stopped completely.");
    }`

Error message
After calling StartXR() (before that StopXR() was executed once) , then I stopped unity and after running unity again the follwing error occurs and inputs to the controller,which are implemented by the new input system, are not possible anymore:
Could not recreate input device 'HP HP Reverb G2 Controller OpenXR (XRInputV1)' with layout 'XRInputV1::HP::HPReverbG2ControllerOpenXR' and variants 'Default' after domain reload
UnityEngine.InputSystem.LowLevel.NativeInputRuntime/<>c__DisplayClass7_0:<set_onUpdate>b__0 (UnityEngineInternal.Input.NativeInputUpdateType,UnityEngineInternal.Input.NativeInputEventBuffer*)
UnityEngineInternal.Input.NativeInputSystem:NotifyUpdate (UnityEngineInternal.Input.NativeInputUpdateType,intptr)
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes (System.Type[])
InvalidOperationException: Cannot find parent 'devicepose' of control 'devicepose/istracked' in layout 'XRInputV1::HP::HPReverbG2ControllerOpenXR'
UnityEngine.InputSystem.Layouts.InputDeviceBuilder.InsertChildControl (UnityEngine.InputSystem.Layouts.InputControlLayout layout, UnityEngine.InputSystem.Utilities.InternedString variant, UnityEngine.InputSystem.InputControl parent, System.Boolean& haveChildrenUsingStateFromOtherControls, UnityEngine.InputSystem.Layouts.InputControlLayout+ControlItem& controlItem) (at Library/PackageCache/com.unity.inputsystem@1.0.2/InputSystem/Devices/InputDeviceBuilder.cs:557)
UnityEngine.InputSystem.Layouts.InputDeviceBuilder.AddChildControlIfMissing (UnityEngine.InputSystem.Layouts.InputControlLayout layout, UnityEngine.InputSystem.Utilities.InternedString variants, UnityEngine.InputSystem.InputControl parent, System.Boolean& haveChildrenUsingStateFromOtherControls, UnityEngine.InputSystem.Layouts.InputControlLayout+ControlItem& controlItem) (at Library/PackageCache/com.unity.inputsystem@1.0.2/InputSystem/Devices/InputDeviceBuilder.cs:508)
UnityEngine.InputSystem.Layouts.InputDeviceBuilder.AddChildControls (UnityEngine.InputSystem.Layouts.InputControlLayout layout, UnityEngine.InputSystem.Utilities.InternedString variants, UnityEngine.InputSystem.InputControl parent, System.Boolean& haveChildrenUsingStateFromOtherControls) (at Library/PackageCache/com.unity.inputsystem@1.0.2/InputSystem/Devices/InputDeviceBuilder.cs:337)
UnityEngine.InputSystem.Layouts.InputDeviceBuilder.InstantiateLayout (UnityEngine.InputSystem.Layouts.InputControlLayout layout, UnityEngine.InputSystem.Utilities.InternedString variants, UnityEngine.InputSystem.Utilities.InternedString name, UnityEngine.InputSystem.InputControl parent) (at Library/PackageCache/com.unity.inputsystem@1.0.2/InputSystem/Devices/InputDeviceBuilder.cs:193)
UnityEngine.InputSystem.Layouts.InputDeviceBuilder.InstantiateLayout (UnityEngine.InputSystem.Utilities.InternedString layout, UnityEngine.InputSystem.Utilities.InternedString variants, UnityEngine.InputSystem.Utilities.InternedString name, UnityEngine.InputSystem.InputControl parent) (at Library/PackageCache/com.unity.inputsystem@1.0.2/InputSystem/Devices/InputDeviceBuilder.cs:102)
UnityEngine.InputSystem.Layouts.InputDeviceBuilder.Setup (UnityEngine.InputSystem.Utilities.InternedString layout, UnityEngine.InputSystem.Utilities.InternedString variants, UnityEngine.InputSystem.Layouts.InputDeviceDescription deviceDescription) (at Library/PackageCache/com.unity.inputsystem@1.0.2/InputSystem/Devices/InputDeviceBuilder.cs:51)
UnityEngine.InputSystem.InputDevice.Build[TDevice] (System.String layoutName, System.String layoutVariants, UnityEngine.InputSystem.Layouts.InputDeviceDescription deviceDescription) (at Library/PackageCache/com.unity.inputsystem@1.0.2/InputSystem/Devices/InputDevice.cs:678)
UnityEngine.InputSystem.InputManager.AddDevice (UnityEngine.InputSystem.Utilities.InternedString layout, System.Int32 deviceId, System.String deviceName, UnityEngine.InputSystem.Layouts.InputDeviceDescription deviceDescription, UnityEngine.InputSystem.InputDevice+DeviceFlags deviceFlags, UnityEngine.InputSystem.Utilities.InternedString variants) (at Library/PackageCache/com.unity.inputsystem@1.0.2/InputSystem/InputManager.cs:1033)
UnityEngine.InputSystem.InputManager.RestoreDeviceFromSavedState (UnityEngine.InputSystem.InputManager+DeviceState& deviceState, UnityEngine.InputSystem.Utilities.InternedString layout) (at Library/PackageCache/com.unity.inputsystem@1.0.2/InputSystem/InputManager.cs:3420)
UnityEngine.InputSystem.LowLevel.<>c__DisplayClass7_0:<set_onUpdate>b__0(NativeInputUpdateType, NativeInputEventBuffer*)
UnityEngineInternal.Input.NativeInputSystem:NotifyUpdate(NativeInputUpdateType, IntPtr)
UnityEngineInternal.Input.NativeInputSystem:Update(NativeInputUpdateType)
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes(Type[])
Furthermore, when I enable/disable XR multiple times I got multiple Instances of those devices as depicted in the image below. When I stop Unity and run Unity again those device duplicates stay. I need to restart unity or remove those device duplicates manually to get it work again:

Expected Behavior
run Unity:

stop Unity:

To reproduce
Steps to reproduce the behavior:

Setup a Scene with Motion Controllers and HP Reverb enabled
Set up a Second camera
Script - Switch between the VR camera and the Second camera and using the above mentioned code snippet to enable/disable the VR Device
Stop Unity and run Unity again

Your setup (please complete the following information)

Unity Version [2020.3.17f1]
MRTK Version [v2.7]
Mixed Reality OpenXR Plugin [Version 1.1.2]
OpenXR [Version 1.2.8]

Target platform (please complete the following information)

HP Reverb G2
WMR immersive
OpenXR

Thanks.

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


Null Reference Exception after disposing the last Iterator

We got an NullReferenceException during writing to the Log, because disposing the only Iterator from our reading task disposes the fasterLog object.
See Line 556 in FasterLogScanIterator.Dispose()
if (Interlocked.Decrement(ref fasterLog.logRefCount) == 0)
fasterLog.TrueDispose();
Please remove this lines from the dispose, if possible.

The refcount starts at 1, and every Scan call increments the refcount by 1 here: FasterLog.cs:1405
So the stated issue should not occur if you pair the Scan with exactly one dispose call of the scan iterator.

Sure, I see this seems not to be the problem.
I created a test in FasterLogTests.cs.
I got a NullReferenceException in this test, because into.Iterators is null:
if (_lastPersistedIterators.Count != info.Iterators.Count)
return true;
Here is the Code:
`
    [Test]
    [Category("FasterLog")]
    public async ValueTask FasterLogAsyncConsumerTestAfterDisposeIterator([Values] LogChecksumType logChecksum)
    {
        device = Devices.CreateLogDevice(path + "fasterlog.log", deleteOnClose: true);
        var logSettings = new FasterLogSettings { LogDevice = device, LogChecksum = logChecksum, LogCommitManager = manager, TryRecoverLatest = false };
        log = await FasterLog.CreateAsync(logSettings);

        byte[] entry = new byte[entryLength];
        for (int i = 0; i < entryLength; i++)
            entry[i] = (byte)i;

        for (int i = 0; i < numEntries; i++)
        {
            log.Enqueue(entry);
        }
        log.Commit(true);

        // Test is working if I add this Iterator
        //using var iter2 = log.Scan(0, long.MaxValue, "TEST2");

        var nextAddress = 0L;
        using (var iter = log.Scan(0, long.MaxValue, "TEST"))
        {
            var count = 0;
            while (iter.GetNext(out _,out _, out _, out nextAddress)) count++;
            log.Commit(true);
            Assert.AreEqual(numEntries, count);
        }

        entry = new byte[entryLength];
        for (int i = 0; i < entryLength; i++)
            entry[i] = (byte)i;

        for (int i = 0; i < numEntries; i++)
        {
            log.Enqueue(entry);
        }

`

`
log.Commit(true);
log.CompleteLog(true);
        using (var iter = log.Scan(nextAddress, long.MaxValue, "TEST"))
        {
            var counter = new Counter(log);
            var consumer = new TestConsumer(counter, entry);
            await iter.ConsumeAllAsync(consumer);
            Assert.AreEqual(numEntries, counter.count);
        }

    }

}`

Thanks for the report. Feel free to submit a fix as pull request, it will take a bit of time for us to review this.


Update DESM Landing Page

**DESM is designed to make mapping easy and support the currency of mappings over time.  It supports pairwise, semantic mapping of schema terms and their definitions using a synthetic spine agnostic to data models and formats.
Resultant mappings are intended to help data standards organizations, developers, decision makers, and others have a clear understanding of how schemas map and provide useful visual and data outputs of completed mappings. **
Link instructions for mappers.
Provide instructions for seeing mappings.

(First draft)
About the DESM tool
The Data Ecosystem Mapping Tool (DESM) is a specialized tool for creating, editing, maintaining and viewing crosswalks between data standards from two or more Data Standard Organizations (DSOs). These crosswalks are based on the degree of semantic alignment between terms in the different standards or schemas, and may be useful for:

supporting translation of data from one standard to another,
supporting the development of data models that align to several standards
showing which standards cover what terms,

among other uses. These uses recognize the reality that any data ecosystem will encompass actors who use different data standards, different models and different schemas, because they have different interests, systems and requirements for the data. Data translation allows a degree of interoperability despite the use of data standards; however our ultimate hope is that semantic mapping will show that data harmonization is possible, that is that different data standards can share semantics and models for common elements.
The crosswalks are based on pairwise mapping of terms from the different standards to a "synthetic spine", a schema-neutral synthesis terms that is created during the mapping. Mappings from terms in one standard to terms in another can then be inferred where their respective mappings to the spine are transitive.
The DESM tool is available as Open Source Software under an Apache 2.0 license.
Instructions for setting up an instance of the DESM tool are available from the repository.
Instructions for carrying out a mapping are available on the DESM repository wiki.
Acknowledgements
[TBD]

OK that's my starter for text to show on the home page of a DESM instance. This text makes sense as a shared, generic description of DESM, however it strikes me that there will be information that needs to be added on an instance by instance basis, e.g what is being mapped in a specific instance, who is responsible for it, how do people get access to that instance; and also that some of the generic information might not be wanted, but there might be some text (aknowledgements etc) that we want kept.

@jbaird123 in addition to Phil's write up above.  Include the following:
DESM is sponsored by the U.S. Chamber of Commerce Foundations' T3 Innovation Network program.  The T3 Open Competency Network, in partnership with the T3 Data and Technology Standards Network is responsible for the requirements and project plans that are used for development and enhancement of the DESM too.
If you are interested in participating with a T3 mapping project, please contact Taylor Hanson<EMAIL_ADDRESS>

On the left side of the landing page the following text should also be updated or removed:
Map your specification to a base schema

Upload Your Specification
Coarse Grain Mapping
Fine Grain Mapping and Tuning
Download Mapping

Either remove it altogether or change it to something like this.
Map your schema:

Upload your schema
Map the schema's properties and concepts
Review and download the completed mappings

@jeannekitchens @philbarker @dmsaunders: Please review the changes that we made based on your notes above.  If there are additional changes needed, please provide exact text and detailed descriptions needed (to eliminate any guess work).

@jeannekitchens @DMSaunders do we need the image? I'm not sure it explains much.

No.  Not at this time.  The pilot may help us create an image.  The only
one I can think of that might be useful is in our deck as a backup showing
the synthetic spine but I think it has to be updated.
Jeanne Kitchens
Chief Technology Services Officer
Credential Engine
217.494.6558
@.***
www.credentialengine.org
www.credreg.net
Credential Engine is a non-profit whose mission is to map the credential
landscape with clear and consistent information, fueling the creation of
resources that empower people to find the pathways that are best for them.
On Tue, Nov 15, 2022 at 3:12 AM Phil Barker @.***>
wrote:

@jeannekitchens https://github.com/jeannekitchens @DMSaunders
https://github.com/DMSaunders do we need the image? I'm not sure it
explains much.
—
Reply to this email directly, view it on GitHub
https://github.com/t3-innovation-network/desm/issues/311#issuecomment-1315159879,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE7SXVSFHFMPCDVK5NVVX63WINV2PANCNFSM6AAAAAARDJDOEU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Resolved.


Email issues

I am getting email errors with fetching GPG keys and when trying to email items. It states that the email was sent but not delivered. How do I fix this? Also what if my organization does not use GPG?

I did change the address of both sql and misp server in both dockerfile and build.sh to my server address, but when i go to the web interface I get "Internal Server Error". Can you please help me with this issue?

@aniss05 Can you try with today's update - it should fix that.
@robertnixon2003 - did you setup a mail server? Otherwise email is all local. A default GPG key is needed for MISP to "function" correctly, but you don't really have to use it past that point.

I tried like you suggested with the latest update and I am still getting this error, and when I open the error.log in my docker container, I get the following error:
2017-09-26 14:51:01 Error: [MissingConnectionException] Database connection "Mysql" is missing, or could not be created.
Exception Attributes: array (
'class' => 'Mysql',
'message' => 'SQLSTATE[HY000] [1045] Access denied for user 'misp'@'localhost' (using password: YES)',
'enabled' => true,
)
Request URL: /
Stack Trace:
#0 /var/www/MISP/app/Lib/cakephp/lib/Cake/Model/Datasource/DboSource.php(269): Mysql->connect()
#1 /var/www/MISP/app/Lib/cakephp/lib/Cake/Model/ConnectionManager.php(105): DboSource->__construct(Array)
#2 /var/www/MISP/app/Controller/AppController.php(99): ConnectionManager::getDataSource('default')
#3 /var/www/MISP/app/Controller/EventsController.php(33): AppController->beforeFilter()
#4 /var/www/MISP/app/Lib/cakephp/lib/Cake/Event/CakeEventManager.php(243): EventsController->beforeFilter(Object(CakeEvent))
#5 /var/www/MISP/app/Lib/cakephp/lib/Cake/Controller/Controller.php(677): CakeEventManager->dispatch(Object(CakeEvent))
#6 /var/www/MISP/app/Lib/cakephp/lib/Cake/Routing/Dispatcher.php(189): Controller->startupProcess()
#7 /var/www/MISP/app/Lib/cakephp/lib/Cake/Routing/Dispatcher.php(167): Dispatcher->_invoke(Object(EventsController), Object(CakeRequest))
#8 /var/www/MISP/app/webroot/index.php(92): Dispatcher->dispatch(Object(CakeRequest), Object(CakeResponse))
#9 {main}
2017-09-26 14:51:02 Error: [MissingConnectionException] Database connection "Mysql" is missing, or could not be created.
Exception Attributes: array (
'class' => 'Mysql',
'message' => 'SQLSTATE[HY000] [1045] Access denied for user 'misp'@'localhost' (using password: YES)',
'enabled' => true,
)
Request URL: /
Stack Trace:
#0 /var/www/MISP/app/Lib/cakephp/lib/Cake/Model/Datasource/DboSource.php(269): Mysql->connect()
#1 /var/www/MISP/app/Lib/cakephp/lib/Cake/Model/ConnectionManager.php(105): DboSource->__construct(Array)
#2 /var/www/MISP/app/Controller/AppController.php(99): ConnectionManager::getDataSource('default')
#3 /var/www/MISP/app/Controller/EventsController.php(33): AppController->beforeFilter()
#4 /var/www/MISP/app/Lib/cakephp/lib/Cake/Event/CakeEventManager.php(243): EventsController->beforeFilter(Object(CakeEvent))
#5 /var/www/MISP/app/Lib/cakephp/lib/Cake/Controller/Controller.php(677): CakeEventManager->dispatch(Object(CakeEvent))
#6 /var/www/MISP/app/Lib/cakephp/lib/Cake/Routing/Dispatcher.php(189): Controller->startupProcess()
#7 /var/www/MISP/app/Lib/cakephp/lib/Cake/Routing/Dispatcher.php(167): Dispatcher->_invoke(Object(EventsController), Object(CakeRequest))
#8 /var/www/MISP/app/webroot/index.php(92): Dispatcher->dispatch(Object(CakeRequest), Object(CakeResponse))
#9 {main}

@aniss05 I decided to go to a brand new environment and test this out -- it seems to work, so I think there might be something old/cached on your side.
Here's what I did:
0.) docker rmi harvarditsecurity/misp  # just to confirm there is nothing
1.) cd /tmp
2.) git clone https://github.com/harvard-itsecurity/docker-misp
3.) cd docker-misp
4.) Edit build.sh -> I changed the two MySQL lines:
 --build-arg MYSQL_ROOT_PASSWORD=TestDifferentPassword \
 --build-arg MYSQL_MISP_PASSWORD=YetAnotherPassword \
5.) ./build.sh #wait until done
6.) Now, setup your "DATA" dir. NOTE: On the mac, by default only "/Users", "/Volumes", "/private", and "/tmp" are directories that Docker will see. I added "/docker" and created it.
7.) mkdir -p /docker/DATA/misp-db/
8.)  Now run the "run-init.sh" and wait. Once it's complete, run the "run.sh". Once that starts, verify that the docker process is running with "docker ps"
10.) In the browser, go to https://localhost and try to login:
Login<EMAIL_ADDRESS>Password: admin

^ For me, that works perfectly. Please verify that these exact steps work for you.
Thanks.

Thanks for your quick reply @ventz , I will try your suggestion and let you know. Hope it will work, thanks again.

Thanks a lot @ventz, it finally worked ! I followed the same steps that you sent except for the steps where you have to set up the external volume path. First I tried the same like yours and it was not working, but then I noticed that the volume "/docker/DATA/misp-db" owner's was not the same as my user, I do not know why this was causing me issues but when I changed the path of the volume in my home path "~/docker/DATA/misp-db", it finally worked.

@aniss05 Great! I am glad it's working.
Closing the issue - if something else comes up, please feel free to ping me here.


[Fix]fix http query_info api return wrong column

What problem does this PR solve?
Fix /rest/v2/manager/query/query_info return data not match its column title.
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[x] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[x] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall