feature request - rolling version update for apps

at some point you need to test your app with real traffic
you got v5 deployed and its stable now works ok and now you need to create the next killer feature ..
feature ready .. testing done .. (but nothing tests as good as real traffic .. !)
.. v6 .. but to see if anything behaves correctly you need to have live traffic ..
100% direct traffic could cost you a lot in a given scenario ..
of course you can rollback but you still affect 100% of your user-base
so a rolling update function
for balancing would be nice ..
lets say for the next N hours  (timescale should be "adjustable" i am going to use %)  gradually update traffic towards v6
why ? simple ..  risks management ( cost of fail )
V5       V6
10%|        90        10     - ( get some peaks with a few customers .. - easy to spot errors ..)
20%|        80        20     -
30%|        70        30     -
40%|        60        40     -
50%|        50        50     - ( decent amount of traffic get realistic insight )
60%|        40        60     -
70%|        30        70     -
80%|        20        80     - ( nearly there .. if anything goes wrong we should have spotted it by now )
90%|        10        90     -
100 full deploy of v6 kill - v5 .. ( we are able to restore it anyway )
if something errors in that timescale .. you could simply rollback to 100% v5 .. fix your problem and deploy v5 to v7 with the same mechanics ..
HOW ?
we use nginx as routing mechanics anyway ( as of now )..
weight=number
sets the weight of the server, by default, 1.
upstream XXX {
server v5.example.com weight=9;
server v6.example.com weight=1;
}
basically what we need is a way to tell to not kill the older versions and keep it around .. to verify
deis config:set GRADUAL_DEPLOY=Xm/h
any ideas / insights would be appreciated

:+ plus one billion. Seriously... this should be expected for a production scale application.

Closing in favor of #3685.


SEARCH-1646 - Include dictionary file and Update libraries for compressing the renderingBlob filed

Description
Include dictionary file and Update libraries for compressing the renderingBlob filed.
SEARCH-1646
Solution Approach
Due to the bot messages which users are subscribed, which contains the entire markup content used for rendering causes the index to grow very big. And to reduce the size of the index we compress the renderingBlob are using zstd lib.
Update the new libraries which compress the renderingBlob of the message object to reduce the index size.
Passing a path to the index-validator and to the library's init function so that the library can access the stored dictionary file.
Related PRs
List related PRs against other branches / repositories:

branch
PR

SymphonyElectron
#759

SymphonyElectron master
#760

QA Checklist

[x] Unit-Tests

Attach unit in PDF format against the above task lists for this branch

Published<EMAIL_ADDRESS>


check_docs has no guarantee of providing useful information if either src or dest are added to doing reindex.

@victorluft Can you provide more detail on the issue? Is this resolveable?

Currently, as in original script, it checks using document count in src/destination and ensuring that those are the same. This is unlikely to be useful to us in our application as we are fairly likely to have new documents added to destination during the reindex process. In the general case, not sure about resolving it as of yet - in our case, we can resolve it with custom checking code based on our read/write aliases and the date filtered one in the target index, but that's not broadly applicable as there's not necessarily going to be a date on documents in an ES index.


Session object has no attribute Started

sorry i know that there is an etiquette to this, i dont know what it is so sorry just gonna go for it.
Describe the bug
Session attribute has no object Started
Traceback (most recent call last):
File "/home/mprocter/Downloads/bot1/quickstart.py", line 10, in
session = Session()
File "/home/mprocter/Downloads/bot1/tinderbotz/session.py", line 111, in init
uc.Chrome(version_main=101, options=options)  that part i did change per a post prior to this one suggested.
#ChromeDriverManager().install(),
File "/home/mprocter/.local/lib/python3.9/site-packages/undetected_chromedriver/init.py", line 208, in init
patcher.auto()
File "/home/mprocter/.local/lib/python3.9/site-packages/undetected_chromedriver/patcher.py", line 118, in auto
release = self.fetch_release_number()
File "/home/mprocter/.local/lib/python3.9/site-packages/undetected_chromedriver/patcher.py", line 140, in fetch_release_number
return LooseVersion(urlopen(self.url_repo + path).read().decode())
File "/usr/lib/python3.9/urllib/request.py", line 214, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.9/urllib/request.py", line 517, in open
response = self._open(req, data)
File "/usr/lib/python3.9/urllib/request.py", line 534, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/usr/lib/python3.9/urllib/request.py", line 1389, in https_open
return self.do_open(http.client.HTTPSConnection, req,
File "/usr/lib/python3.9/urllib/request.py", line 1349, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [Errno -2] Name or service not known>
/==============\

Tinderbotz

duration: 20

like: 0

dislike: 0

superlike: 0

==============/

Error in atexit._run_exitfuncs:

Traceback (most recent call last):

File "/home/mprocter/Downloads/bot1/tinderbotz/session.py", line 68, in cleanup

print("Started session: {}".format(self.started))

AttributeError: 'Session' object has no attribute 'started'
To Reproduce
Steps to reproduce the behavior:
python3 quickstart.py
Desktop (please complete the following information):

OS: ubuntu
Browser chrome
Version 101

Smartphone (please complete the following information):
Additional context
was working fine.

If it was working fine, then I would suggest deleting the folder "chrome_profile", it worked for me.

Same problem. How to solve it

If it was working fine, then I would suggest deleting the folder "chrome_profile", it worked for me.

same problem even I deleted the folder chrome_profile

hello, how do i find this folder ?


Default highlight.js off, dockerfile > conf highlighting, pygments

Changes

highlight.js is disabled unless highlightjs: true is enabled in front-matter
import of all pygments CSS files, which work with Rouge lexer
change of dockerfile to conf, which works fine, syntax-highlighting-wise
Removal of excess inactive scrollbars, e.g. https://docs.docker.com/engine/examples/running_redis_service/
Using slightly modified perldoc.css file from pygments, nice mild color scheme (https://github.com/richleland/pygments-css)

Why?

Fixes terrible JS lag, especially on pages such as this: https://docs.docker.com/compose/aspnet-mssql-compose/ which is killing browser tabs due to syntax collision between C# and highlight.js's regex
Better highlighting in general

Fix for SQL compose example (page loads with no lag): https://deploy-preview-2757--docker-docs.netlify.com/compose/aspnet-mssql-compose/
Code blocks from test page:
https://deploy-preview-2757--docker-docs.netlify.com/test/#code-blocks

LGTM, merging


added slide on carousel, started style mods

-added slide to each carousel
-changed sports to misc (info seemed more pertinent)
-changed background color
-started spacing out elements
-added placeholders and style to header

Sorry about the confusion, I thought we were going for a little bit of a cleaner, more modern look.  I'm not totally finished yet so it can wait til morning and everyone can have a look then.  If people like it, cool.  If they like the colors the other way then we can just disregard the pull request.

I'm not talking about your new changes.... just some of the stuff we did today.  Namely this:

Huh, I didn't change anything myself in that area.  It's possible my main is out of sync.  I tried git merging into the branch I'm pushing but it said I was up to date.  Lemme see if I can square up why the two aren't lining up.

We can square it up tomorrow too. No worries
On Mon, Jul 11, 2022, 9:30 PM littletonjeffrey @.***>
wrote:

Huh, I didn't change anything myself in that area. It's possible my main
is out of sync. I tried git merging into the branch I'm pushing but it said
I was up to date. Lemme see if I can square up why the two aren't lining up.
—
Reply to this email directly, view it on GitHub
https://github.com/codewizard-dt/city-cost-comparison/pull/30#issuecomment-1181243725,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWRQ2JL7RBR5EEZQML3GCO3VTTKFFANCNFSM53JCSLYA
.
You are receiving this because you commented.Message ID:
@.***>

Hopefully better now, sorry for all the headache.  Good lesson in not getting distracted from git pulling


Documentation

I know this is quite a recurrent issue, but I think it's still an important one. I'm sure everyone is busy with adding all the new features/backends/etc but it has come to the point where a lot of keras's functionality is undocumented and changing from one commit to the other.
Digging through the (largely also uncommented) code and trying to infer what every new thing does and how every old thing changed is becoming cumbersome and utterly intractable. Half the merge mode are missing explanation even on the shape of the output. I do recommend not accepting any more pull requests that lack some form of explanation and maybe also updating the docs a bit from behind.
The API is awesome, but I'm starting to not know what the features are any more or what's the right way to access them >.>

You're right. What are some specific features that are currently undocumented? We could start there.

Not sure if this is the right issue, but I had a hard time figuring out what training data should look like, specifically for the simple examples (which except for this are great). Numpy arrays? Python lists? What shape is expected?
For example, in the multilayer perceptron example it would be useful to use way less input nodes, leaving room to define X_train and y_train. That would be a nice bottom-up starting point for further coding.

rmse and poisson losses are missing as objectives
all merge modes but sum, mul and concat are missing (only sum and concat are present in graph modes)
concat_axis, dot_axes, create_output are missing from the add_node graph model documentation
layers such as LRN2D, Lambda, MaskedLambda are missing.
input_length and go_backwards are undocumented for recurrent layers

There are more but I'll dig through them tomorrow

There is not the go_backwards  documentation @lemuriandezapada? I added it there https://github.com/fchollet/keras/blob/master/docs/sources/layers/recurrent.md some days after the addition of the flag to the library.
Some newer layers have not documentation yet i know but we should focus together to add it, most of this library is currently evolving through pull request from people, from one side not fast enough and from the other too fast we are in a transitioning phase that will decide if this is going to be a real widely used deep learning library.
A thing is that we should have a development branch of the library that can be partially documented but we should have some checkpoints that must be up to date. The pip version of Keras should be correctly documented the other may be partially since is under development from my point of view.
I don't know if the administrator @fchollet  plans to add some more strict versioning system in the future. Or rules regarding unitest and documentation for all the pull request to be accepted.
There are many things that must be addressed in particular for user demanding more from the library but the people actively developing it are really few. @fchollet @EderSantana and @farizrahman4u  are really committing a lot to the library and i'm trying to do my best too (at the best of my knowledge and capabilities). If there are problems with something just point out, if you can solve the problem by yourself just pull request, for the rest maybe someone can take care of the issue. There are a lot of things to make this library better.

Maybe I'm doing it wrong(?) but I keep referring to this page, and go backwards doesn't appear to be there:
http://keras.io/layers/recurrent/
Although after some looks in the .md files some stuff is still missing even there.
I'd love to help out but my coding skills and understanding of theano are too low to patch it up myself. ^^
Pointing things out is what I'm doing now. To be fair, I'd personally be ok with slower development but easier to understand features. I would personally suggest some more hardcore requirements for documentation from pull requests.

@lemuriandezapada You  have to check the docs folder in the repository. www.keras.io is not up to date

Yes, I see now some of them are there, but not all.
Merge modes and everything related to them and the graph models are missing.

I updated the online documentation yesterday, which fixes some but not all of the issues mentioned.

Random thought: we could probably rig up travis to push the docs to wherever you are hosting them, if master is updated and all tests pass.

@phreeza I agree with you. If there's a structure that people can take part in I'm willing to help!

I've also noticed that the LRN2D layer is missing documentation - it may be pretty straightforward, but its existence is not even mentioned.

The neural turing machine is also undocumented

'trainable' option is also undocumented

@lemuriandezapada I'll work on better documentation for NTM, right now, we have some notes here: https://github.com/fchollet/keras/wiki/Tutorials-and-lessons

Cool ^^
siamese layer is also undocumented

In addition to documenting the API itself it would be beneficial to have a change log, especially since there are often breaking changes.
I also think it would be good to separate the API documentation from a more use case centered tutorial. Use cases would be something like data pre-processing, model training, evaluation, model selection, performance optimization, visualization, model debugging or extensibility. This would also be a good place to explain the main concepts in terms of composability/modularity.

You might be interested in

NumpyDoc
How Lasagne did their documentation, e.g.

docs/objectives.rst and the rendered result

We have had autogenerated documentation for a few weeks now. Closing this issue.


Write efficiency: direct I/O?

I'm currently adding a zarr writer to our project, which can be roughly described as data acquisition and live processing framework for electron microscopy. I'm trying to make the writing operation as low-overhead as possible, to make room for actual data processing in the same data pipeline. (I'm also interested in offering compressed writing, which of course has a different CPU vs I/O profile, for users with a beefier system, but that's a different topic).
One approach I've used in the past was to use direct I/O bypass the page cache, resulting in much better performance (much closer to what the hardware can actually deliver).
I've built a demo repository that compares zarrs uncompressed write speed with a small prototype that writes the chunks "manually" using direct I/O: https://github.com/LiberTEM/zarr-dio-proto/
On the system I have available (AMD EPYC 7F72, 2x KCM61VUL3T20 NVMe SSD in a RAID0), the direct I/O approach is about 5x faster than the buffered I/O approach. There's also a branch that directly puts the data into a page-size-aligned buffer, which is a bit less realistic but still interesting (it writes the 32GiB in ~4s, which is about the limit of the SSDs). This is all on a single core.
Is there interest in integrating a FilesystemStore with direct I/O capabilities into zarrs? Getting this working as fast as the prototype would require some structural changes, too, which probably have to be done incrementally.
I'm also interested in trying an io_uring implementation, which would be the modern way for high-performance I/O on Linux systems.

Is there interest in integrating a FilesystemStore with direct I/O capabilities into zarrs

Yes! This looks great and I would probably use it myself. Thanks for putting together such a nice little demo.

I'm also interested in trying an io_uring implementation, which would be the modern way for high-performance I/O on Linux systems.

I am also interested in this, but I have been lazily waiting for support from object_store or opendal https://github.com/apache/opendal/issues/4520, but that could be a long time.

Yes! This looks great and I would probably use it myself. Thanks for putting together such a nice little demo.

Great to hear! I'll work on a minimal PR as a basis for discussion.

I am also interested in this, but I have been lazily waiting for support from object_store or opendal apache/opendal#4520, but that could be a long time.

Yeah, integrating this different style of I/O generically into such libraries is no small task, I imagine.

Thanks for your work on this @sk1p!
xref direct IO PRs and comments related to compressed writing/potential further improvements:

#58

requesting a buffer from storage
partial encoder-like encoding chain?

#64

Thank you for the discussion and reviews! To pull the discussion back here, from the closed PR(s): (#58):

Yep, that could probably work. The standard encode/decode methods of codecs do not provide any access to storage. But what you are after is not so different from the partial decoders and partial encoders (#45). They pass input/output handles through the codec chain and the last codec ends up calling storage methods via StoragePartialDecoder / StoragePartialEncoder. The same ideas could be applied to non-partial encoding.

Interesting. I'll need to have a closer look.
Next on my TODO list is a full integration into our software, then I can see how well the approach works in practice - I'll write an update in this issue if I don't forget :)
If there is a need, I could also work on adding O_DIRECT read support, which I personally don't need yet, but might also be nice to have for symmetry reasons.


set context

This PR fixes #10384
This PR fixes #10386
this seems to be caused by recent vscode merge, but i didn't find out how it broke this scenario, it turns out notebook is also using this action, and it is working properly because it has the context set.
https://github.com/microsoft/azuredatastudio/blob/master/src/sql/workbench/contrib/notebook/browser/cellToggleMoreActions.ts#L59
so i am just doing the same here.

most likely this issue is also in the RC build, i will bring this to Release manager's attention.

Coverage increased (+0.1%) to 33.842% when pulling e2f564477f0755ed899bfacc294abc5b948a51ca on alanren/widget-context-menu into 18128d700d21fcc89a9ecfa6b35eae53dc54019c on master.


preserve state on HMR when multiple components exists in a single file

Related plugins

[ ] plugin-vue

[X] plugin-vue-jsx

Describe the bug
import { defineComponent } from "vue";

export const Test = defineComponent({
  render() {
    return Then change me...;
  },
});

export default defineComponent({
  render() {
    return (

          <input type="text" placeholder="Type fist..." />

        <Test></Test>

    );
  },
});

Reproduction
https://stackblitz.com/edit/vitejs-vite-uda5gz?file=src/main.ts
Steps to reproduce
No response
System Info
System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1
    Memory: 125.39 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.18.0 - /opt/homebrew/bin/npm
  Browsers:
    Safari: 16.2
  npmPackages:
    @vitejs/plugin-vue: ^4.0.0 => 4.0.0
    @vitejs/plugin-vue-jsx: ^3.0.0 => 3.0.0
    vite: ^4.0.0 => 4.1.1

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I wasn't able to reproduce. Would you write a more detailed steps?

I wasn't able to reproduce. Would you write a more detailed steps?

The problem is when I change the jsx template of Test component and save the App.tsx, the msg in the default component has been reseted.
I've made some changes in App.tsx:
https://stackblitz.com/edit/vitejs-vite-uda5gz?file=src%2FApp.tsx,src%2Fstyle.css,src%2Fmain.ts

I see.
To achieve that, we somehow need to skip calling __VUE_HMR_RUNTIME__.reload for the default component. I'm not sure how we can do that though.

it should call __VUE_HMR_RUNTIME__.rerender instead of reload.


Implement array update operator $rename

Another general-purpose array operator to implement is $rename. Its semantics are similar to $unset followed by $set (if that was allowed), so that:

If target path exists, the value is overwritten
If source path does not exist, operation does nothing (but does not fail)

Format is simple:
{ "$rename" : { "field1" : "newName1", .... , "fieldN", "newNamen" } }

Following error modes exist:

_id either as source or target: cannot modify immutable property "_id"
Same source and target (must differ)
Attempt to move source to incompatible path

The last case occurs, for example when an attempt is madeto set a property on Array value: that is, target path points to something that is not possible to add: for example with
{ "x" : 3, "array" : [ 1 ] }

attempt to apply operation
{ "$rename" : { "x" : "array.x" }  }

would fail. Same is true for paths "through" atomic fields; only (sub)documents have properties.

$rename isn't necessarily an array operator. I'd also put $rename as low priority, it is rarely used in my experience.

Thank you @vkarpov15 that was a copy-paste mistake (I know it's not array-specific).
I am creating issues based on @amorton's list; this is lower priority than my current work on dotted paths for sure.


Postgres block insert issue for block 46631

When running a fresh postgres sync with backend:latest the backend hangs and keeps restarting at block 46631.
Probably related to some recent changes. It´s the block with the first NFTs created it seems.
`I0226 09:05:44.548962       1 server.go:1147] Server._handleBlock: Received block ( 46631 / 107387 ) from Peer [ Remote Address               : <IP_ADDRESS>:17000 PeerID=1 ]
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x49 pc=0xb1b525]
goroutine 56 [running]:
github.com/go-pg/pg/v10.(*Tx).RunInTransaction.func1()
/root/go/pkg/mod/github.com/go-pg/pg/v10@v10.10.0/tx.go:91 +0x86
panic({0x10a56c0, 0x1e8a660})
/usr/lib/go/src/runtime/panic.go:1038 +0x215
github.com/deso-protocol/core/lib.(*Postgres).InsertTransactionsTx(0xc0016054b8, 0xc0016054c8, {0xc016be2000, 0xae4, 0xc0037c7c               c0}, 0xc004e97780)
/deso/src/core/lib/postgres.go:1092 +0x1b65
github.com/deso-protocol/core/lib.(*Postgres).UpsertBlockAndTransactions.func1(0x0)
/deso/src/core/lib/postgres.go:1336 +0x98
github.com/go-pg/pg/v10.(*Tx).RunInTransaction(0xc0016eb280, {0x1730468, 0xc00003a280}, 0xc016cb4230)
/root/go/pkg/mod/github.com/go-pg/pg/v10@v10.10.0/tx.go:95 +0xa5
github.com/go-pg/pg/v10.(*baseDB).RunInTransaction(0xc017fda798, {0x1730468, 0xc00003a280}, 0xc010586ea0)
/root/go/pkg/mod/github.com/go-pg/pg/v10@v10.10.0/tx.go:74 +0x51
github.com/deso-protocol/core/lib.(*Postgres).UpsertBlockAndTransactions(0xc000168e10, 0xc010586ea0, 0xc017c22000)
/deso/src/core/lib/postgres.go:1324 +0x5c
github.com/deso-protocol/core/lib.(*Blockchain).ProcessBlock(0xc00082ebb0, 0xc010586ea0, 0xe5)
/deso/src/core/lib/blockchain.go:1935 +0x191c
github.com/deso-protocol/core/lib.(*Server)._handleBlock(0xc000fd80c0, 0xc001bb6d80, 0xc010586ea0)
/deso/src/core/lib/server.go:1193 +0x3e5
github.com/deso-protocol/core/lib.(*Server)._handlePeerMessages(0xc000fd80c0, 0xc001bb6d80)
/deso/src/core/lib/server.go:1494 +0x18d
github.com/deso-protocol/core/lib.(*Server).messageHandler(0xc000fd80c0)
/deso/src/core/lib/server.go:1534 +0x19c
created by github.com/deso-protocol/core/lib.(*Server).Start
/deso/src/core/lib/server.go:1710 +0xb1
`
Will check what is causing it.

Just seeing this now. Any update on this? I don't think anything's changed since the most recent release.

Just seeing this now. Any update on this? I don't think anything's changed since the most recent release.

Did not find out the exact cause yet. Some new fields linking to block height have been introduced. The error is very generic, but that block had the first NFT transactions.

Just tried the updated backend and pulled that version and started the sync. Same error invalid memory address. It tried to continue where it crashed. On block 46631 @diamondhands0 @lazynina can it be related to the new block height column added for certain transactions and in Postgres?

@mvanhalen - I'm looking now, apologies for not seeing this issue earlier.

@mvanhalen - I'm looking now, apologies for not seeing this issue earlier.

Thanks let me know how I can help.

@mvanhalen - this PR will resolve the current issue and should allow you to pick up syncing where you left off.
https://github.com/deso-protocol/core/pull/232

Can you try pulling the latest image and let me know if you encounter any other issues please?

Wow superfast. Just deleted that DB.  But will sync one which has just started. And put this version there

Wow superfast. Just deleted that DB. But will sync one which has just started. And put this version there

awesome - sounds good. Keep me posted. I was able to reproduce it locally by submitting a bid on serial number 0 - which is a standing offer on any serial number, but there's no NFT entry (as there is no real serial number 0)

Wow superfast. Just deleted that DB. But will sync one which has just started. And put this version there

awesome - sounds good. Keep me posted. I was able to reproduce it locally by submitting a bid on serial number 0 - which is a standing offer on any serial number, but there's no NFT entry (as there is no real serial number 0)

Ok sync is running. Needed to start fresh. Anyway how can I setup the local stuff? I tried in the past but it did not work out. That way I can be of more assistance. Do you have a repo somewhere or the run.sh file? Thanks.

Wow superfast. Just deleted that DB. But will sync one which has just started. And put this version there

awesome - sounds good. Keep me posted. I was able to reproduce it locally by submitting a bid on serial number 0 - which is a standing offer on any serial number, but there's no NFT entry (as there is no real serial number 0)

Ok sync is running. Needed to start fresh. Anyway how can I setup the local stuff? I tried in the past but it did not work out. That way I can be of more assistance. Do you have a repo somewhere or the run.sh file? Thanks.

@mvanhalen - I'll share how I run things locally tomorrow. Can you let me know what didn't work for you? And assuming you want a local Postgres setup, correct?

@lazynina @mvanhalen i created this a while ago for dharmesh to run postgres + backend locally
github.com/desodev/prodeso

@lazynina sync has past the previous crash point now at blockheight 57000+ waiting for it to complete. But looking good. For the testing stuff would like to setup a local chain with postgres(external) indeed last time we tried testnet it crashed on some transaction in the around 30K block range.  I guess you test custom local chain? Thanks @tijno

For info @mvanhalen - My PG node crashed yesterday - but after restarting its stuck at 108743. May just be because of the crash as this sometimes happens with postgres.

For info @mvanhalen @lazynina - My PG node crashed yesterday - but after restarting just now its stuck at 108741. Looks like time of crash yesterday is same as time this block 108731 was mined.
I restarted with new stable image 2dc0ed73a08f - but still stuck with this error.

E0303 09:35:18.204038       1 blockchain.go:1214] MarkBlockInvalid: Block height: 108741, Block hash:<PHONE_NUMBER>0014b98e050080d584625a69236b78775bb3792827f9351b9d0eb7, Error: ConnectBlock: : ConnectTransaction: : RuleErrorCreateProfileTxnOutputExceedsInput

As this seems to be a new issue ill raise it as a separate one.

Ok thanks for the heads-up. Which version of core was that? there have been a couple of versions the last view days. I´m running one from yesterday with the bids fix

current stable - so that is 2.0.7 i think @mvanhalen

Wow superfast. Just deleted that DB. But will sync one which has just started. And put this version there

awesome - sounds good. Keep me posted. I was able to reproduce it locally by submitting a bid on serial number 0 - which is a standing offer on any serial number, but there's no NFT entry (as there is no real serial number 0)

Ok sync is running. Needed to start fresh. Anyway how can I setup the local stuff? I tried in the past but it did not work out. That way I can be of more assistance. Do you have a repo somewhere or the run.sh file? Thanks.

@mvanhalen - I replace the data-dir flag in the n0_test script in backend/scripts/nodes/no_test with the postgres-uri below to run a regtest node locally.
--postgres-uri=postgresql://postgres:postgres@localhost:5432/postgres?sslmode=disable \

Regtest allows you to start your own chain locally (not testnet nor mainnet).
I start postgres by using the following command to run a docker container:
sudo docker run --rm --name postgresql -p 5432:5432 -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres -d postgres:latest

You can use this scheme to sync to testnet by removing the --regtest flag. To sync mainnet, also remove --testnet=true
Let me know if you have further questions.

Wow superfast. Just deleted that DB. But will sync one which has just started. And put this version there

awesome - sounds good. Keep me posted. I was able to reproduce it locally by submitting a bid on serial number 0 - which is a standing offer on any serial number, but there's no NFT entry (as there is no real serial number 0)

Ok sync is running. Needed to start fresh. Anyway how can I setup the local stuff? I tried in the past but it did not work out. That way I can be of more assistance. Do you have a repo somewhere or the run.sh file? Thanks.

@mvanhalen - I replace the data-dir flag in the n0_test script in backend/scripts/nodes/no_test with the postgres-uri below to run a regtest node locally.
--postgres-uri=postgresql://postgres:postgres@localhost:5432/postgres?sslmode=disable \

Regtest allows you to start your own chain locally (not testnet nor mainnet).
I start postgres by using the following command to run a docker container:
sudo docker run --rm --name postgresql -p 5432:5432 -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres -d postgres:latest

You can use this scheme to sync to testnet by removing the --regtest flag. To sync mainnet, also remove --testnet=true
Let me know if you have further questions.

Thanks will test tomorrow. Appreciate it. Shameless plug: nftz.zone v2 is out. More here all possible because of Postgres sweetness! @lazynina @diamondhands0

Latest build go beyond this point


chore: Move files from /usr/etc/ to /etc/ in build-time

Take a look at this issue for more details:
https://github.com/blue-build/modules/issues/314
Idk if anything else needs to be done, please tell
Should be tested for regressions too

Don't see anything else that needs to be done, so easy-peasy I guess


Buttons of showcase are appearing outside of display

I tried making a sequence of showcase appearances on a view i was making but after the first showcase no button shows up.  When I try removing the first showcase the button shows up but part of it is off screen.
Here is an image of a showcase which is done on the top left rectangle after a showcase was done on the bottom left button.

What my calls look like
        builder.context(activityRule.getActivity())
                .key("KEY")
                .developerMode(true)
                .view(activityRule.getActivity().findViewById(R.id.button_dashboard_view_init))
                .descriptionImageRes(R.mipmap.ic_launcher)
                .descriptionTitle("First button")
                .descriptionText("Click here to do stuff.")
                .buttonText("Done")
                .buttonVisibility(true)
                .cancelButtonVisibility(true)
                .cancelButtonColor(Color.WHITE)
                .add()                                              //add first showcase
                .view(activityRule.getActivity().findViewById(R.id.linearlayout_dashboard_info))
                .descriptionTitle("Your Progress")
                .descriptionText("Here is your progress so far")
                .buttonText("Done")
                .buttonVisibility(true)
                .cancelButtonVisibility(true)
                .cancelButtonColor(Color.WHITE)
                .add()                                             //add showcase shown in image
                .build()
                .show();

Note that I'm doing this with Expresso and am just passing an activity rule as the activity

It seems like setting negative margins helps this issue a bit although I wouldn't consider it fixed.

I forked the project and added two function, useGravity and setGravity to enable gravity and using a gravity argument to position the description relative to the showcase target (ex Gravity.START would place the description box and button to the left of the item being targeted). https://github.com/travis575757/ShowcaseView


explorer.autoReveal bad interaction with preview files

Testing #15647

VSCode Version: insiders 1.8.0 a8d5b9
OS Version: MacOS

Steps to Reproduce:

open a folder
close all editors
single click on a file to open it in preview mode
open settings.json (CMD+,), now the editor should be replaced
go into zen mode (CMD+K, Z)
exit zen mode (CMD+K, Z)

Result: the last file you had open, before opening the settings file, is now in view. In other words, the settings file is no longer visible.  Only seems to happen with settings.json

As designed. On explorer open we always open the revealed file - there is a setting for this 'explorer.autoReveal'.
So you can get the same behavior if instead of going in and out of zen mode you would show / hide the viewlet.
Though I do agree that your scenario is not nice. But the key problem here is that explorer.autoReveal does not make much sense when an editor is open in preview. Though this is up to ben to decide how to tackle this.

This is a consequence of the explorer restoring the last active file when you open it. Another example where we do this is when you jump from Git viewlet back to the explorer we close the diff editor that you likely have open and bring back the file you last worked on. In that scenario I like the flow, however in the described scenario it is not very nice.
Btw the same happens when you open a markdown as preview, close all other editors and hide and show the explorer. The last file you had open restores.
One way to probably fix this is by only restoring the file if it is still open in the editor group.

The explorer is now treating the settings and keybindings in the same way as a normal file, so this bug as reported is fixed.

LGTM

@chrisdias feel free to add a verified label :)

@isidorn sorry, added.


Please allow using gzipped log files

Under many Linux distributions, logfiles are compresses after a few days.  It would be convenient if goacess could transparently decompress such compressed log files.

Possible ways to fix this:

Actually manage your server so it does not do things you don't want it to do.
Pipe the output of zcat instead of the actual log files to goaccess.

Yes, I know about the workaround.  I'm just saying that it would be convenient if goaccess could decompress on the fly.

Hi @jech
Perhaps you can a fuse filesystem that have to support that.
I find fuse-bgzip here.

@jech Thanks for suggesting this. I can look into this. I'm guessing it will require to build --with-zlib, it shouldn't be too bad. @0bi-w6n-K3nobi Thanks for sharing those workarounds, certainly did not know the fuse-bgzip :)


Removal of el8 Support

Hello,
Any reason support for el8 was removed for the last two releases? It wasn't indicated in the changelog so it came as a surprise while I was bumping the version in my project. Thanks in advance!

The old packages were built with CentOS Stream 8, which went EOL at the same time as CentOS Linux 7:
https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and-centos-linux-7/
The new packages are instead built with AlmaLinux 8 and AlmaLinux 9, so that means that they are EL:

https://github.com/Mirantis/cri-dockerd/issues/383

Ah got it. Thank you!


tabu_search wrong commas in line 255&256 within branch optimization_runner

these commas at the end in line 255 & 256 in the file tabu_search should not be there, as they turn the dicts into lists which results in multiple errors. @MLuuwak
If I remove the commas it works, so I think this is a very quick fix. Could you also merge the one change made in main into the optimization_runner branch, that would be very helpful!
Thanks and thanks also for all the changes made!

There is an additional bug in simulated_annealing in line 251 - the optimizer should not be given as a parameter here. If I remove it, it works again.
Moreover, just as a minor note, could you rename the newly added optimisation examples to .py files? Otherwise, these are not rendered correctly for me in GitHub.
Thanks!


limited config params count?

Hi,
i have a problem with my config fields count. Is there a limit to a count or memory limit? I have the following fields set. but the last 2 are missing:
Device-Address
Hostname (String)
Update-Interval (int)
10x 1W-Address (String 16)
10x GA
Only the GAs 1-8 are there, 9 and 10 are missing. Is this there a known limit?
kindly regards

Take a look at https://github.com/envy/esp-knx-ip/blob/eff93654078f299825aa644cf9a2d4e816591c5f/esp-knx-ip.h#L17L22 and adjust those values accordingly.


Error w/ config.el (void-function doom-themes-treemacs-config) ?

Observed behavior
Am trying to use treemacs instead of neotree now and just pulled the latest from develop branch.
I run ~/.emacs.d/make and get the following:
Deleted old autoloads.pkg.el
✓ Cached package state
✓ Package autoloads included
✓ Removed load-path/auto-mode-alist entries

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

There was an unexpected error:
  Error in private config (doom-private-error)
  config.el
  (void-function doom-themes-treemacs-config)

Expected behavior
make successfully rebuilds 😄
Steps to reproduce
My configuration sits in ~/.config/doom directory and I just copy over init.example.el to init.el in this directory. I have a config.el in this directory too which has my private custom configurations.
The contents of my private config.el:
;;; config.el -*- lexical-binding: t; -*-
;;; skalfyfan custom doom! config changes

(require 'doom-themes)

;; Global setting (defaults)
(setq doom-themes-enable-bold t    ; if nil, bold universally disabled
      doom-themes-enable-italic t) ; if nil, italics universally disabled

(load-theme 'doom-dracula t)

(doom-themes-visual-bell-config)
(doom-themes-treemacs-config)
(doom-themes-org-config)

(after! projectile
        (setq projectile-require-project-root t))

If I remove this custom config.el then make works successfully. Wondering what is causing the conflict w/ treemacs though and causing this error?

@hlissner That worked! Had not updated packages in awhile.
Also, thanks for the config.el tip!


pull request for e2e test at 11/24/2016 21:56:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


taliwind css module stops working

i tried to add this module on a project that had the tailwind css module on it, then all the tailwind classes stopped working. any idea? sorry if its not clear

Hi, do you think you could provide a reproduction ? I don't think it's related to this module but le'ts figure out !

@IanEvers Any updates on your issue ? :)


Update the dev to be compatible with Intel

Update the dev branch to reflect the latest development on main.

Just doing the last changes to the Runners to make them operational again and I'll merge the PR

After this I'll merge this PR and open a new to fix the issues with ADIOS


Add allowlist setting for ingest-common processors

Add a new static setting that lets an operator choose specific ingest processors to enable by name. The behavior is as follows:

If the allowlist setting is not defined, all installed processors are enabled. This is the status quo.
If the allowlist setting is defined as the empty set, then all processors are disabled.
If the allowlist setting contains the names of valid processors, only those processors are enabled.
If the allowlist setting contains a name of a processor that does not exist, then the server will fail to start with an IllegalStateException listing which processors were defined in the allowlist but are not installed.
If the allowlist setting is changed between server restarts then any ingest pipeline using a now-disabled processor will fail. This is the same experience if a pipeline used a processor defined by a plugin but then that plugin were to be uninstalled across restarts.

Related to #14439
Check List

[x] Functionality includes testing.
[ ] ~API changes companion pull request created, if applicable.~
[x] Public documentation issue/PR created, if applicable: https://github.com/opensearch-project/documentation-website/pull/7414

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Should we prevent users from not allowing the processors which are used by existing ingest pipelines? Indexing failures will happen if users change the setting but some in-use processors are not in the allowlist.

Should we prevent users from not allowing the processors which are used by existing ingest pipelines? Indexing failures will happen if users change the setting but some in-use processors are not in the allowlist.

I think this is one of the goals - if the processor could be disabled at any time (for whatever reasons). The same would happen if plugin with custom processors is uninstalled.


Kubeflow installation fails if ksonnet is not installed

Before installing kubeflow, the script needs to check if ksonnet is installed, if not, it should install ksonnet otherwise kubeflow app deployment will fail.

Indeed. However I prefer NOT to mess with the system EKStender is running on. It does require a bunch of stuff to work (AWS CLI, jq, ksonnet etc). I am actually adding the requirements to eksutils which is the tool I am suggesting to use to run EKStender.


Incomplete release

Hello,
I just pulled your last release and discovered the following issues if i try to compile:
I'm on branch master respectively tag v2019.11.21
Component compile order
Compiling bitvis_vip_avalon_mm source
(vcom-1598) Library "bitvis_vip_scoreboard" not found.
Missing files
Error: (vcom-7) Failed to open design unit file "./../bitvis_vip_uart/script/../src/monitor_cmd_pkg.vhd" in read mode.
Missing components
bitvis_vip_gmii
bitvis_vip_hvvc_to_vvc_bridge
bitvis_vip_ethernet
best regards
Michael

Hi Michael!
Thank you for the information! The bug somehow slipped through the release process. A new release is on its way.
Br
Marius

Hi,
A new release has been published. I see you mention that you get a component compile order error for the Bitvis VIP Avalon MM. In the latest release of UVVM every VIP require Bitvis VIP Scoreboard to be compiled in addition to UVVM Util and UVVM VVC Framework.
Best regards,
Marius

Thanks for the quick fix. The compilation works fine now.
best regards
Michael


Clone a table but leave offline

When cloning a table via the shell, we should have the option to keep the table offline.

In #575 the ability to create tables in the offline state was added.  Would be worth looking at the API changes made for that in order to try and achieve consistency if possible.


Make hwloc compulsory instead of optional

As suggested in #2923 - we should make hwloc a requirement rather than an optional dependency.
Things to do

Remove abstract topology class and virtual interface to hwloc_topology
upgrade to hwloc 2.0 API (Due for release end Nov 2017)
Improve CMake integration to allow hwloc 2.0 to be downloaded and built as part of the hpx compilation step if it is not found on the system. This may not be possible on all platforms, but should be done where supported/possible.

Thanks John, this is the right step. I would however advise against integrating downloading/building of hwloc into our build system. Our build system is sufficiently complex as it is without that. If we followed that route we would need to do the same with Boost.
Let's rather create proper documentation on how to install hwloc if it's not available (or provide a separate (python) script for this).


1.17????

Is this mod also for 1.17????
I hope so 😇😇😇

GitHub is not for messages like that

Oké but is it for 1.17 or not or is it comming??


Support for not full plates in importer, and cellHTS2 nodes

For some experiments the plates are not filled at every place. It would be
convenient if the read and analysis would not require to have full plates.

Original issue reported on code.google.com by aborgabor on 16 Sep 2009 at 10:23

Most of this work would be on CellHTS2, which is no longer supported.


Store n_cycles and time_bandwidth params in *TFR objects

Describe the new feature or enhancement
Discussed partly with @larsoner.
MNE-Connectivity is being updated to allow connectivity computations using complex coefficients stored in EpochsTFR objects (https://github.com/mne-tools/mne-connectivity/pull/232). For the multitaper method, TFR coefficients have a tapers dimension that need to be aggregated over when computing the CSD. These weights are not stored in the *TFR objects, and computing these weights requires knowledge of the time_bandwidth and n_cycles used to estimate the TFR. However, currently these parameters are not stored in *TFR objects.
If we want to accurately compute these weights in MNE-Connectivity, we would currently require the user to pass these parameters in addition to the EpochsTFR object. It would be more convenient if this information could also be read from the EpochsTFR object.
Describe your proposed implementation
There were two ideas:

Either store this information directly as attributes, e.g., tfr.n_cycles and tfr.time_bandwidth
Or store these params as a dict to minimise clutter in the *TFR namespace, e.g., tfr.estimation_parameters = {'mt_bandwidth': 4, 'n_cycles': 5}

Describe possible alternatives
An alternative would be to just store the taper weights in the *TFR objects, which is similar to how this is now handled for *Spectrum objects. However, the weights are not returned by tfr_array_multitaper, so they would still need to be recomputed.
It's perhaps simpler if we just handle this in MNE-Connectivity using the stored estimation params.
What do people think is the best choice?

An alternative would be to just store the taper weights in the *TFR objects, which is similar to how this is now handled for *Spectrum objects. However, the weights are not returned by tfr_array_multitaper, so they would still need to be recomputed.

Since we already store weights for spectrum objects, I'm inclined to store weights (not estimation params) for TFRs too. That saves having to recompute them when users pass MNE objects (not arrays) to the connectivity functions, and is more internally consistent. (this assumes that we don't anticipate needing n_cycles or mt_bandwidth for other purposes... I suppose to be maximally future-proof we could store the weights and the estimation params)
When users pass NumPy arrays to the conn functions, they can/should expect that they'll need to provide some extra information, so IMO it's fine to ask them to pass in estimation params (n_cycles and mt_bandwidth) and we calc the weights for them at that time... even though it's a bit error-prone to trust that the user passes the same values to both the TFR function and the connectivity function.
Another option would be adding return_weights=False to tfr_array_multitaper, so that folks can use the array-based connectivity API as long as they're willing to re-compute the TFR with return_weights=True first. That feels slightly worse to me than just asking them to pass in the estimation params.

Since we already store weights for spectrum objects, I'm inclined to store weights (not estimation params) for TFRs too. That saves having to recompute them when users pass MNE objects (not arrays) to the connectivity functions, and is more internally consistent.

Sure, I see your reasoning, especially to keep it consistent with *Spectrum objects. I'll open a PR for this.

When users pass NumPy arrays to the conn functions, they can/should expect that they'll need to provide some extra information, so IMO it's fine to ask them to pass in estimation params (n_cycles and mt_bandwidth) and we calc the weights for them at that time... even though it's a bit error-prone to trust that the user passes the same values to both the TFR function and the connectivity function.

Just to clarify, for the proposed connectivity function changes, users would still only be able to pass in arrays of epoched timeseries data, not epoched coefficients. If we change to store weights in *TFR objects, then n_cycles and mt_bandwidth params could be completely ignored for *TFR data, but for Epochs and arrays of epoched timeseries data they would still function in the same way (to determine the TFR estimation).

Just to clarify, for the proposed connectivity function changes, users would still only be able to pass in arrays of epoched timeseries data, not epoched coefficients. If we change to store weights in *TFR objects, then n_cycles and mt_bandwidth params could be completely ignored for *TFR data, but for Epochs and arrays of epoched timeseries data they would still function in the same way (to determine the TFR estimation).

Ah OK, so it's for any non-spectral/spectrotemporal data (whether in Epochs object form or array form) where they need to pass the estimation params. That makes sense.

Since we already store weights for spectrum objects, I'm inclined to store weights (not estimation params) for TFRs too. That saves having to recompute them when users pass MNE objects (not arrays) to the connectivity functions, and is more internally consistent.

Had a look into this and have a couple questions about the implementation:
When Raw/Epochs.compute_tfr(method="multitaper") is called, what happens internally is essentially tfr_array_multitaper() -> _compute_tfr() -> _make_dpss(). The taper weights are computed in _make_dpss(), which already has a toggle to return the weights.
However, _compute_tfr() currently does not return weights, and more importantly neither does tfr_array_multitaper(). So if we wanted to return the weights computed in _make_dpss() to the *TFR object, a new param would be needed in tfr_array_multitaper(). This was mentioned earlier in a slightly different context:

Another option would be adding return_weights=False to tfr_array_multitaper

Is a public API change like this acceptable?
If not, then the weights would need to be recomputed in the *TFR object. It's not the most efficient approach, but the compute cost isn't huge.

So if we wanted to return the weights computed in _make_dpss() to the *TFR object, a new param would be needed in tfr_array_multitaper().

I find this acceptable. The tfr_array_*() functions are sort of like "expert mode" now that there are .compute_tfr() methods on objects. I don't see much harm/danger in adding a return_weights param to it. @larsoner WDYT? The alternatives are

recompute weights later (feels icky, but as @tsbinns says, the compute cost isn't huge)
do some kind of larger refactor so that the .compute_tfr() methods don't call the public tfr_array_* APIs, but instead call directly to _compute_tfr().

Sorry for not opening a PR on this yet, things ended up being a little more complicated. Making the changes so that weights are available to be stored in TFR objects was fine, but when looking into the code I also realised that the TFR plotting methods (plot, plot_topo, and plot_topomap) cannot handle cases where a tapers dimension is present (raises an error related to data shape), and also that to_data_frame does not account for the possibility of a tapers dimension.
Fixing to_data_frame is easy, and for the plotting functions the equivalent issue was addressed for Spectrum objects in #12747 (aggregate over tapers and convert to power before plotting; currently the conversion to power happens, but there is no aggregation).
However, since this is a distinct thing to adding a weights attr, I wasn't sure if people would prefer these in separate PRs, or should I handle all of this at once?

since this is a distinct thing to adding a weights attr, I wasn't sure if people would prefer these in separate PRs, or should I handle all of this at once?

ideally separate, but I doubt anyone will complain too much if you roll them all into one. They're separable sure, but they're still related, so if it's easier to do it all at once, then I will happily sign up to review one bigger PR instead of 2 smaller ones.

Okay super, then I'll also add these fixes to #12910!


[BUG] Weird TypeError when calling init_beanie using dict instead of Dict in module

Using Python 3.10, one is expected to essentially not use Dict anymore, and simply utilise dict. This is also true with many other types such as tuple, etc.
This, tho, makes beanie raise a TypeError if such dict usage is done at the module level of one of the documents input to init_beanie.
To Reproduce
import asyncio
from typing import Any

from beanie import Document, init_beanie
from motor.motor_asyncio import AsyncIOMotorClient

DictStrAny = dict[str, Any]

class Thing(Document):
    thing: DictStrAny

    class Settings:
        name = "things"

async def main():
    client = AsyncIOMotorClient("mongodb://localhost:27017")

    await init_beanie(database=client["test_db"], document_models=[Thing])

if __name__ == "__main__":
    asyncio.run(main())

Expected behaviour
Technically, nothing wrong has been done here, but the program crashes with the following:
Traceback (most recent call last):
  [...]
  File "[...]/beanie_crash_pydantic_v2.py", line 20, in main
    await init_beanie(database=client["test_db"], document_models=[Thing])
  File "[...]/.cache/pypoetry/virtualenvs/algo-db-manager-C0jUbCoT-py3.10/lib/python3.10/site-packages/beanie/odm/utils/init.py", line 754, in init_beanie
    await Initializer(
  File "[...]/.cache/pypoetry/virtualenvs/algo-db-manager-C0jUbCoT-py3.10/lib/python3.10/site-packages/beanie/odm/utils/init.py", line 121, in __init__
    self.fill_docs_registry()
  File "[...]/.cache/pypoetry/virtualenvs/algo-db-manager-C0jUbCoT-py3.10/lib/python3.10/site-packages/beanie/odm/utils/init.py", line 137, in fill_docs_registry
    if inspect.isclass(obj) and issubclass(obj, BaseModel):
  File "[...]/.conda/envs/python310/lib/python3.10/abc.py", line 123, in __subclasscheck__
    return _abc_subclasscheck(cls, subclass)
TypeError: issubclass() arg 1 must be a class

Additional context
Using:

pydantic v2.5.3
beanie v1.24.0
python v3.10.

Current workaround
Current workaround is to either come back to use capital Dict (or equivalents) in those kinds of definitions... which goes technically against current style guides, or avoid using this kind of auxiliary definitions at all.

Hi @ivan-gj ,
Thank you for the catch!

Confirmed reproduced under Python 3.10 only. Would upgrading to a newer Python version work for you?
$ python py310_repro.py
Traceback (most recent call last):
  File "C:\Users\...\Projects\beanie-test-migrations\py310_repro.py", line 24, in <module>
    asyncio.run(main())
  File "C:\Users\...\.pyenv\pyenv-win\versions\3.10.5\lib\asyncio\runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "C:\Users\...\.pyenv\pyenv-win\versions\3.10.5\lib\asyncio\base_events.py", line 646, in run_until_complete
    return future.result()
  File "C:\Users\...\Projects\beanie-test-migrations\py310_repro.py", line 20, in main
    await init_beanie(database=client["test_db"], document_models=[Thing])
  File "C:\Users\...\Projects\beanie-test-migrations\.venv\lib\site-packages\beanie\odm\utils\init.py", line 782, in init_beanie
    await Initializer(
  File "C:\Users\...\Projects\beanie-test-migrations\.venv\lib\site-packages\beanie\odm\utils\init.py", line 126, in __init__
    self.fill_docs_registry()
  File "C:\Users\...\Projects\beanie-test-migrations\.venv\lib\site-packages\beanie\odm\utils\init.py", line 142, in fill_docs_registry
    if inspect.isclass(obj) and issubclass(obj, BaseModel):
  File "C:\Users\...\.pyenv\pyenv-win\versions\3.10.5\lib\abc.py", line 123, in __subclasscheck__
    return _abc_subclasscheck(cls, subclass)
TypeError: issubclass() arg 1 must be a class

Interestingly, the same is not reproduced if the document model is typed as:
class Thing(Document):
    thing: dict[str, Any]

    class Settings:
        name = "things"

By not using the type alias.
The issue is caused since DictStrAny is not a subclass of a pydantic.BaseModel which Beanie is expecting but rather a typing.GenericAlias type and so it fails.
For the fix, maybe we could try wrapping the critical section in a try-except, or by doing some different check. Example:
    def fill_docs_registry(self):
        for model in self.document_models:
            module = inspect.getmodule(model)
            members = inspect.getmembers(module)
            for name, obj in members:
                try:
                    if inspect.isclass(obj) and issubclass(obj, BaseModel):
                        DocsRegistry.register(name, obj)
                except TypeError:
                    pass

Or we could replace the issubclass call with the lenient_issubclass() method from Pydantic: https://github.com/pydantic/pydantic/pull/2392
To fix this under Python 3.10.


Added localization for Infinity Nuke entity

This is for The One Probe/HWYLA/Jade compatibility
This PR fixes the localization issue seen at the top:

Stopid entities smh


Conflicted with Pod

I used Pod to import Mediapipe
Then I use your method to deploy opencv, it has the following errors:
487 duplicate symbols
Linker command failed with exit code 1 (use -v to see invocation)
Could you pls check it for me? Thanks

Could you pls check it for me? Thanks


map, collect for collection

need add to Collection next methods:
map, collect, collectFirst

https://github.com/fntzr/sirius/commit/ff9c3799796fc5f9afb8b2c0f8effdf3c60d37a3


Api Error: body contains invalid json

Thanks for sharing such a great project! It seems to be very well written and well documented.
However I'm having a bit of trouble running some basic functions such as registerUser() and setLightState(). It constantly throws a Api Error: body contains invalid json error. I have however been successful in running functions like connect() and deleteUser().
I'm running on a Windows 8.1 environment, with node version 0.10.35 and bridge swversion 01018228.

I have also been running into this issue. My code is as follows:
var hue = require('node-hue-api'),
	HueApi = hue.HueApi,
	lightState = hue.lightState,
	elasticsearch = require('elasticsearch'),
	client = new elasticsearch.Client({ host: 'elastic1.df.vimeows.com:9200' }),
	hostname = '[ip address here]',
	username = 'zenahirsch',
	api = new HueApi(hostname, username),
	state = lightState.create();

var displayResult = function(result) {
    console.log(JSON.stringify(result, null, 2));
};

api.setLightState(1, state.off(), function(err, lights) {
    if (err) {
    	console.log(err);
    }

    displayResult(lights);
});

I get the following result:
{ [Api Error: body contains invalid json]
  message: 'body contains invalid json',
  type: 2,
  address: '/lights/1/state' }

Can you check the version of request that is inside the request-util dependency of the hue-api?
I released an updated version of this support library to support the upcoming version 1.0.0 of the hue-api, and may have broken this. The new version of request changed the way the json property is interpreted and I suspect this may be your issue.
If confirmed, I can fix that quickly with a new patch release.

package.json within request shows "version": "2.51.0"

Ok, I should be able to fix that quickly...

I have just released version 0.0.3 of request-util that should resolve this issue.
Run npm update on your project and it should pull this new version down with corrects the JSON issues.
Let me know if it works, and I can close out this issue.

Yes, it worked! Thank you so much!

I am very sorry for that, I should have properly followed my semver version numbers and incremented it as a patch...


Update AzureRM->Az include

OPS Build status updates of commit 9d1d96c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azurermps-4.4.1/overview.md
:white_check_mark:Succeeded
View (azurermps-4.4.1)

docs-conceptual/azurermps-5.7.0/install-azurerm-ps.md
:white_check_mark:Succeeded
View (azurermps-5.7.0)

docs-conceptual/azurermps-5.7.0/overview.md
:white_check_mark:Succeeded
View (azurermps-5.7.0)

docs-conceptual/azurermps-6.13.0/install-azurerm-ps.md
:white_check_mark:Succeeded
View (azurermps-6.13.0)

docs-conceptual/azurermps-6.13.0/overview.md
:white_check_mark:Succeeded
View (azurermps-6.13.0)

docs-conceptual/includes/az-replacing-azurerm.md
:white_check_mark:Succeeded
View (azurermps-4.4.1) View (azurermps-5.7.0) View (azurermps-6.13.0)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


feat(assets): Update text to mention we support images in MDX and Markdoc too

What kind of changes does this PR include?

New or updated content

Description
We added support for relative and optimized images in MDX and Markdoc as well! Core PR for MDX: https://github.com/withastro/astro/pull/6824 (Markdoc is already in, but figure we can do both at once.)

@Princesseuh It looks like this feature was already merged? So merge this one whenever you're ready!  :partying_face:


added primitive .travis.yml

First step to Travis integration

Part of #12
Leaving 5.3 failing on purpose


crawlab 重启之后，重启前 pending 的任务无法继续执行

Bug 描述
当我重启crawlab之后，在重启之前处于pending的任务无法成功调度，一直处于pending状态。
复现步骤
该 Bug 复现步骤如下

保证当前tasks列表中有pending的任务，且node为空
重启master和worker节点
重启成功后pending的任务会一直pending

期望结果
重启crawlab之后，之前处于pending的任务可以继续调度执行。

@ma-pony hey!
I would appreciate if you provide relevant translation for your issue in ENG.
I'm not sure if Google Translator handle it properly.
Thanks)

@ma-pony hey! I would appreciate if you provide relevant translation for your issue in ENG. I'm not sure if Google Translator handle it properly. Thanks)

Thanks for the suggestion！

@ma-pony thanks for your translation.
Have the same issues. In my case I have > 400 scheduled tasks and lot of them staying in pending state and never executed.
Seems like Redis queues don't clear in proper way.

@ma-pony thanks for your translation. Have the same issues. In my case I have > 400 scheduled tasks and lot of them staying in pending state and never executed. Seems like Redis queues don't clear in proper way.

I have 6k+ scheduled tasks...

@ma-pony 6k+ scheduled tasks it is impressive.
What kind of Crawlab installation you using Docker based or Kubernetes and what kind of infrastructure you using.
Could you please share some details?

@ma-pony 6k+ scheduled tasks it is impressive. What kind of Crawlab installation you using Docker based or Kubernetes and what kind of infrastructure you using. Could you please share some details?

https://docs.crawlab.cn/en/guide/installation/kubernetes.html
four 8C16G  machines, deployed using k8s, one master node and six worker node， with worker configured with 4C16G and master configured with 6C12G


Remaining mention of "Oracle" on Azure Bare Metal Infrastructure doc page

There is a sole fragmentary mention of "Oracle" on the Azure Bare Metal Infrastructure page (HERE), apparently left over from prior to the cancellation of the offering of Oracle on BMI in March 2022.
The fragment occurs at this link HERE and is listed in the first bulleted list in this section, where both SAP and Oracle are mentioned.
All mentions of Oracle in relation to BMI should be erased to prevent confusion for customers.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 64a00f8f-aa3d-18ef-88ff-2ef4bc3ce8a2
Version Independent ID: 83e4b536-e0ec-4041-ca9c-0255fd64722b
Content: What is BareMetal Infrastructure on Azure? - Azure Baremetal Infrastructure
Content Source: articles/baremetal-infrastructure/concepts-baremetal-infrastructure-overview.md
Service: baremetal-infrastructure
GitHub Login: @dineshga
Microsoft Alias: kalyank

@tigormanmsft
I've delegated this to @dineshga, a content author, to review and share their valuable insights.

Ramanathan,
Please be aware that @dineshgahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdineshga&data=05|01|Timothy.Gorman%40microsoft.com|45a98a1f668948366a8a08dafe8cd7ac|72f988bf86f141af91ab2d7cd011db47|1|0|638102178116074031|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=X6DYAPOGDhuUMEwGmTtZANGq5wJHO6Q2b2G96wqUmHs%3D&reserved=0 no longer works at Microsoft?
Thank you!
Tim Gorman   |   +1<PHONE_NUMBER>   |<EMAIL_ADDRESS>Principal Cloud Solution Architect - Azure Infrastructure - Oracle SME
Customer Success Architecture & Engineering
Learn why customers modernize and migrate with Azure - YouTubehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DRPfR3GJvztA&data=05|01|Timothy.Gorman%40microsoft.com|756e7b0ea6dc4c35dbc008da3cd82cbb|72f988bf86f141af91ab2d7cd011db47|1|0|637889196410882674|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=n6ui7M0sjpj2N54jZle8FQZwE5UAZvWEhvGup27rTLk%3D&reserved=0
[http://mysignature/Templates/Logos/L_Microsoft.png]
From: RamanathanChinnappan @.>
Sent: Tuesday, January 24, 2023 8:30 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Tim Gorman @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Remaining mention of "Oracle" on Azure Bare Metal Infrastructure doc page (Issue #104241)
@tigormanmsfthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftigormanmsft&data=05|01|Timothy.Gorman%40microsoft.com|45a98a1f668948366a8a08dafe8cd7ac|72f988bf86f141af91ab2d7cd011db47|1|0|638102178115917518|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=RLM0NDdDNfpxkXoV8%2FYco8sBes%2FvE9ixmJ%2Bgwvoza9g%3D&reserved=0
I've delegated this to @dineshgahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdineshga&data=05|01|Timothy.Gorman%40microsoft.com|45a98a1f668948366a8a08dafe8cd7ac|72f988bf86f141af91ab2d7cd011db47|1|0|638102178116074031|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=X6DYAPOGDhuUMEwGmTtZANGq5wJHO6Q2b2G96wqUmHs%3D&reserved=0, a content author, to review and share their valuable insights.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F104241%23issuecomment-1403084259&data=05|01|Timothy.Gorman%40microsoft.com|45a98a1f668948366a8a08dafe8cd7ac|72f988bf86f141af91ab2d7cd011db47|1|0|638102178116074031|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=C%2BWZZQ4e5tKGwFCAyF%2FN8fN8dVrWPpAbjYir4txcLaY%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOEEG3KC2DCL7PM4YKP4L73WUCT5BANCNFSM6AAAAAAUF2NCXA&data=05|01|Timothy.Gorman%40microsoft.com|45a98a1f668948366a8a08dafe8cd7ac|72f988bf86f141af91ab2d7cd011db47|1|0|638102178116074031|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=m9QFGDsilas6hAT3rJfd8HjHXGwo%2B5zZE9b3RkzvTf0%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

#please-close

@akashdubey-ms pls comment as above (I'm not allowed to)


Build Failed with Crosswalk and PushPlugin

Hi,
sadly my build failed with com.phonegap.plugins.PushPlugin and Crosswalk
BUILD FAILED

Total time: 47.356 secs

/Users/mayer/apps/platforms/android/cordova/node_modules/q/q.js:126
                    throw e;
                          ^
Error code 1 for command: /Users/mayer/apps/platforms/android/gradlew with args: cdvBuildDebug,-b,/Users/mayer/apps/platforms/android/build.gradle,-PcdvBuildArch=arm,-Dorg.gradle.daemon=true

Your system information:

OS: Mac OS X Yosemite
Node Version: v0.10.33
Cordova CLI: 4.3.0
Ionic CLI Version: 1.3.16
Xcode version: Xcode 6.2 Build version 6C131e
ios-sim version: 3.0.0

This might be related to some of the flags being passed to gradle.
It looks like the cdvBuildDebug flag is causing some issues. I'll look into this.

Some other guys have the same problem. See here:
http://forum.ionicframework.com/t/reporting-bug-crosswalk-issue-with-other-plugins/18028

@neeg Thanks for reporting this.
At a quick glance, it looks like the plugin authors haven't updated the plugin to work with other webviews than the default one. In this case, the XWalkWebView.
This is more an issue to be handled from the plugin authors. Closing for now.

Any update on this ?

For the ones interested, I managed to solve this issue by changing my build.gradle file.
Change this :
dependencies {
compile fileTree(dir: 'libs', include: '*.jar') ...}
To
dependencies {
compile fileTree(dir: 'libs', include: 'gcm.jar') ...}
The * was making gradle to take all the libs in the folder which was including android-support-v13.jar as well.
As Pushplugin uses support-v4 there was an incompatibility.
So now only support-v4 is included and it's ok.

@kcedric this solution is not working for me. How can I use push notifications with ionic if Ionic relies on a not up-to-date dependencies ? I don't understand why this issue is closed.


Expand remaining AlexandriaNetworkAPI long running tasks

What was wrong?
The alexandria network needs to maintain the routing table in the same manner as the base protocol.  Not all of that functionality has been ported over.
How was it fixed?
Largely just a copy/pasta from NetworkAPI implementation with only superficial updates.
I explicitely didn't copy over any tests that are currently being applied to the equivalent functionality under the NetworkAPI because those tests are largely flakey/fragile and I don't want to expand that problem.
Cute Animal Picture

All of the code here is just copy/pasta from existing implementations in the NetworkAPI so review as you see fit.


default redis cluster protocol

Defaults the Redis Cluster protocol for outbound clusters to MAGLEV as discussed in https://github.com/istio/istio/pull/14582#pullrequestreview-246343642

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ramaraochavali
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ostromart
If they are not already assigned, you can assign the PR to them by writing /assign @ostromart in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @ramaraochavali. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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

@rshriram as discussed here. PTAL.

/ok-to-test

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ramaraochavali, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@howardjohn @fpesce We want Redis protocol support in 1.2 branch. Could you please add the label so that mergify bot can cherry pick this PR?

@howardjohn @fpesce @rshriram Looks like 1.2 is out - can we consider this for 1.2.1 patch? Can you please add the label for auto merge to 1.2.1?

@hzxuzhonghu Can you please also add label to this PR?

Hi @ramaraochavali , mergify failed to create the PR to cherrypick this change without conflict, please submit a manually cherrypicked PR to 1.2!
Thanks!


feat: add env update error

Changes

#814  👈
main

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

Join @MasterPtato and the rest of your teammates on  Graphite


About dockerfile

Can you provide the latest dockerfile, I found that the dockerfile on github is not the latest, which is inconsistent with the generation of docker exadel/compreface:1.0.1-arcface-r100. I want to develop new Dockerfile on arm machine.Thanks.

Could you check it again?
I just didn't merge the 1.1.x branch to master branch before

I want to develop new Dockerfile on arm machine.
That is very interesting. Could you share the results afterward?


SOUL SACRIFICE DELTA™ [PCSD00079]

App summary

App name: SOUL SACRIFICE DELTA™
App serial: PCSD00079
App version: 1.30

Vita3K summary

Version: v0.1.6
Build number: 3017
Commit hash: https://github.com/vita3k/vita3k/commit/762ee3bc4a261d779bbf34179a7c6a5316f36c69
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: @Nathaniel-Wu
OS: Windows 10
CPU: Intel i7-8700K
GPU: NVIDIA GeForce RTX 3070
RAM: 16 GB

Issues
The game is playable and runs fine in the main menu scene, there are minor glitches with particle effects such as fire.
The first time I started a quest the scene for some reason was too bright. Restarting the quest fixes that but it still runs very slowly, and the issue isn't resolution related, it runs around 10~15fps at both 1x and 4x resolutions.
Screenshots
Visual glitches with fire, framerate is stable 30 fps at 4x resolution:

Oversaturated scene the first time starting a quest:

Framerate drops massively from the main menu scene to the quest at 1x resolution:

Recommended labels

Ingame +
shader bug

I will remove the labels until you try with 2x resolution as soul sacrifice works best with this resolution

It's still about the same framerate in 2x resolution.

Japanese version also has a graphics bug at all resolutions.

some scenes are too bright

Hey guys, I didn't go deep into playing it, but I think it's more playable


The download in progress is terminated. And there is no stop & pause functionality right now. So you may have to reinitiate the download if the download is not successfully finished.


mark AppiumServer as component

Coverage increased (+0.2%) to 31.475% when pulling<PHONE_NUMBER>c915383c86138378f03a28654619cd on fix_appium_server into 4e18a5c1faeb71b7f1072991471fa59e9af37105 on master.


Make examples more secure

Some Predis users clone the repository and use it as it is. This leads to a situation where a malicious user can access the sensitive Redis storage data by accessing example files with a direct URL. This pull request tries to add some protection against that.

I guess this makes sense, but at this point woulnd't it be just better to limit examples to be exacutable only when using the CLI? They were actually meant to be used like that after all, the output of these scripts is not really formatted to be displayed as a web page.


[AIRFLOW-3302] Small CSS fixes

Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title.

https://issues.apache.org/jira/browse/AIRFLOW-3302

Description

[x] 2 small CSS fixes

Don't highlight logout button when viewing Log tab of a task run
Align Airflow logo to the center of the login page

Before:

After:

Before:

After:

Tests

[x] Tested manually

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes flake8

Probably okay, but could you include a before and after screenshot?

@ashb done.

Thanks @msumit


Add support for BOM schema validation

cyclonedx-cli should support validation of BOMs using the official schemas for both XML and JSON formats. Validation should be possible for all versions of the spec, with the default always being the latest available version.
I'm thinking of a usage similar to this:
$ cyclonedx-cli validate --input-file bom.xml --input-format autodetect --spec-version 1.1

Addressed with https://github.com/CycloneDX/cyclonedx-cli/pull/83. Thanks for implementing this! 🎉


Code Cimate github integration

Although we do have an account on Code Climate we're not seeing its status on the pull requests. It is something important to have.

Moved to https://github.com/departurerb/departure/issues/5


[PlutusTx] [Test] 'Eq' for 'Value'

This adds some budget tests for (==) @Value.
Needs docs, don't look here yet.

This is ready for review, but

CI throws random nix errors that I don't understand
there are some true errors related to name duplication etc, but it's hard to dig them out because of 1
I need to create golden files per GHC version, which I just realized

I'll handle 2 and 3 and they shouldn't really affect reviews, so please review. I'll need help with 1, I've no idea what's going on there.

It's a bit hidden, but you can eventually find that it's a failure to solve for the dependencies on 8.10: https://ci.iog.io/build/1252601/nixlog/1
This is because the plugin is not buildable on < 9.2, so we now can't build the plutus-ledger-api tests on 8.10, which we were previously able to do. I'm unsure about that - thus far we've kept plutus-ledger-api entirely free of the plugin. But annoyingly Value is defined there, so not sure what else to do. We could either just accept that the tests don't work on 8.10, or make another test component that has stuff that depends on the plugin and doesn't build on 8.10.

To be clear, to get stuff to be ignored for 8.10 you just have to do what we do elsewhere and add an GHC version conditional guarding buildable: False.

@michaelpj I've separated the new tests into a separate stanza, but CI still seems to complain. Any suggestions what I should do next?

I pushed a couple of commits:

Annoying Nix stuff since we need to turn off anything using the plugin when cross-compiling.
Some unnecessary dependencies that were causing a -Werror failure


Revit encountered a System.Exception: The component 'RevitAddinManager.View.FrmAddInManager' does not have a resource identified by the URI

Describe the bug
Revit encountered a System.Exception: The component 'RevitAddinManager.View.FrmAddInManager' does not have a resource identified by the URI '/RevitAddinManager;component/view/frmaddinmanager.xaml'.
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
at RevitAddinManager.View.FrmAddInManager..ctor(AddInManagerViewModel vm)
at RevitAddinManager.Command.AddinManagerBase.ExecuteCommand(ExternalCommandData data, String& message, ElementSet elements, Boolean faceless)
at RevitAddinManager.Command.AddInManagerManual.Execute(ExternalCommandData commandData, String& message, ElementSet elements)
at apiManagedExecuteCommand(AString* assemblyName, AString* className, AString* vendorDescription, MFCApp* pMFCApp, DBView* pDBView, AString* message, Set<ElementId,std::less,tnallc >* ids, Map<AString,AString,std::less,tnallc<std::pair<AString const ,AString> > >* data, AString* exceptionName, AString* exceptionMessage)
To Reproduce
Steps to reproduce the behavior:

Go to Addin Open Add-in Manager
Click Load dll Add-in manager to Add-in Manager
Run AddinManager loaded
Open again Add-in Manager from ribbon
See Error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser [e.g. chrome, safari]
Version Revit 2023

Use small trick to trim assembly version in project configuration
<PropertyGroup>
 <PublishSingleFile>true</PublishSingleFile>
      <PublishTrimmed>true</PublishTrimmed>
    </PropertyGroup>

This problem occurs when Assembly.LoadFile method is used to load assemblies at runtime. But when Assembly.LoadFrom method is used, it does not occur.

https://chowdera.com/2022/03/202203091902109000.html

System.InvalidCastException: [A]RevitAddinManager.View.Control.ExtendedTreeView cannot be cast to [B]RevitAddinManager.View.Control.ExtendedTreeView. Type A originates from 'RevitAddinManager, Version=2<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' in the context 'LoadNeither' at location 'C:\Users\Chuong.Ho\AppData\Local\Temp\RevitAddins\RevitAddinManager-Executing-20220529_151417_2606\RevitAddinManager.dll'. Type B originates from 'RevitAddinManager, Version=2<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' in the context 'LoadFrom' at location 'C:\Users\Chuong.Ho\AppData\Roaming\Autodesk\Revit\Addins\2023\RevitAddinManager\RevitAddinManager.dll'.
at RevitAddinManager.View.FrmAddInManager.System.Windows.Markup.IComponentConnector.Connect(Int32 connectionId, Object target) in D:\API\Revit\RevitAddInManager\AddInManager\View\FrmAddInManager.xaml:line 0
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetConnectionId(Object root, Int32 connectionId, Object instance)

https://github.com/dotnet/wpf/issues/1700

https://github.com/dotnet/wpf/issues/4494

@lishuangquan1987 still not yet, it problem from core of wpf, error same when change to in net 4.7.2, you can read some acticle a has report in main github wpf open source in https://github.com/dotnet/wpf/issues/1700


[Feature Request] User-Managed Access support

I'm using Keycloak for user management, and with traefik-forward-auth, access control is basically all or nothing. (There are some workarounds involving modifying the login flow, but its pretty hack-y). Keycloak has an API that implements UMA which can be used to check if the specific user has access to that specific resource (which is usually specified by url).
@thomseddon  would you take a PR implementing this?
Some info:
https://en.wikipedia.org/wiki/User-Managed_Access
https://docs.kantarainitiative.org/uma/wg/rec-oauth-uma-grant-2.0.html
https://wso2.com/library/article/2018/12/a-quick-guide-to-user-managed-access-2-0/

This sounds great, would definitely be interested to see how it could be implemented. Happy to discuss implementation ideas!


MAVSDK SERVO_OUTPUT_RAW(36) DATA Receive

Hello,
I have a question. I am using the Pixhawk Orange Cube Plus and MAVSDK to communicate between the Pixhawk and a Raspberry Pi. While I have successfully received GPS data, roll, pitch, yaw angles, and various other data, I have not been able to receive servo data. The following code is causing an error:
const Telemetry::Result set_rate_actuator_output_result = telemetry.set_rate_actuator_output_status(1.0);
if (set_rate_actuator_output_result != Telemetry::Result::Success)
{
    std::cerr << "Setting rate failed: " << set_rate_actuator_output_result << '\n';
    return 1;
}
The error code is MAVLink: info: No ap_message for mavlink id (375) (system_impl.cpp:243), and when I connect the Pixhawk to Mission Planner and inspect the MAVLink messages, the list shows:

Vehicle 1
 L Comp 1 MAV_COMP_ID_AUTOPILOT1
  L SERVO_OUTPUT_RAW (2.0 Hz, #36) 48Bps
    L port 0 system.Byte
    L servo1_raw 0 system.UInt16
    ...
    L time_usec x system.UInt32

According to the official documentation, the SERVO_OUTPUT_RAW ID has been replaced by ACTUATOR_OUTPUT_STATUS. Is it possible to modify the MAVSDK code to receive SERVO_OUTPUT_RAW? If not, are there any other solutions?
Thank you very much.

PX4 or ArduPilot? And which version?
The message you're trying to set the rate is: ACTUATOR_OUTPUT_STATUS.
Presumably ArduPilot doesn't implement that one?
Could you just use MavlinkPassthrough instead for this one?

I solved it with MavlinkPassthrough. Thank you for your reply.


[HUDI-400]check upgrade from old plan to new plan for compaction

What is the purpose of the pull request
Add more test for compaction plan upgrade
Brief change log
check upgrade from old plan to new plan for compaction
Verify this pull request
This pull request is a trivial rework / code cleanup without any test coverage.
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #1422 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1422      +/-   ##
============================================
+ Coverage     67.51%   67.56%   +0.04%
  Complexity      255      255
============================================
  Files           340      340
  Lines         16499    16499
  Branches       1686     1687       +1
============================================
+ Hits          11139    11147       +8
+ Misses         4622     4615       -7
+ Partials        738      737       -1

Impacted Files
Coverage Δ
Complexity Δ

...oning/compaction/CompactionV2MigrationHandler.java
84.21% <100%> (+21.05%)
0 <0> (ø)
:arrow_down:

...src/main/java/org/apache/hudi/metrics/Metrics.java
56.75% <0%> (-13.52%)
0% <0%> (ø)

...pache/hudi/common/versioning/MetadataMigrator.java
83.33% <0%> (+25%)
0% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Gpu resource required ?

What is the exact gpu memory required to run the evaluation experiment of internvideostage2 ?

Just one gpu below 10 gpu memory.

in my case, it is taking more than 48GB and it stops with out of memory error.


Automated cherry pick of #2983: - instance snapshot

Cherry pick of #2983 on release/2.12.
#2983: - instance snapshot

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@6148eed). Click here to learn what that means.
The diff coverage is 3.24%.

@@              Coverage Diff               @@
##             release/2.12   #3199   +/-   ##
==============================================
  Coverage                ?   7.14%
==============================================
  Files                   ?     480
  Lines                   ?   77475
  Branches                ?       0
==============================================
  Hits                    ?    5536
  Misses                  ?   71476
  Partials                ?     463

Flag
Coverage Δ

#aFlag
7.14% <3.24%> (?)

Impacted Files
Coverage Δ

pkg/compute/guestdrivers/kvm.go
3.58% <ø> (ø)

pkg/cloudcommon/db/opslog.go
1.94% <ø> (ø)

pkg/mcclient/options/servers.go
0% <ø> (ø)

pkg/hostman/monitor/qmp.go
5.86% <0%> (ø)

pkg/compute/models/snapshots.go
1.73% <0%> (ø)

pkg/compute/models/disks.go
0.68% <0%> (ø)

pkg/compute/models/guest_actions.go
0% <0%> (ø)

pkg/util/qemuimg/qemuimg.go
0% <0%> (ø)

pkg/compute/models/guests.go
0.64% <0%> (ø)

pkg/compute/models/instance_snapshot_joint.go
4.16% <4.16%> (ø)

... and 1 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 6148eed...066d627. Read the comment docs.


Add CPP error if trying to use recording on a non-Windows platform

Thanks for this contribution. I think this error message is a good idea.
The message after #error doesn't need to be in quotes.

Thanks!


YARN-11055. Add missing newline in cgroups-operations.c

Description of PR
Adding missing newline characters in the end of fprintf format strings in cgroups-operations.c
How was this patch tested?
pseudo-distributed deploy https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/UsingGpus.md#distributed-shell--gpu-with-docker
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m  0s

Docker mode activated.

-1 :x:
docker
20m 57s

Docker failed to build yetus/hadoop:13467f45240.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/3851

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3851/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
22m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
36m 13s

trunk passed

+1 :green_heart:
compile
1m 18s

trunk passed

+1 :green_heart:
mvnsite
0m 46s

trunk passed

+1 :green_heart:
shadedclient
60m 37s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 37s

the patch passed

+1 :green_heart:
compile
1m 14s

the patch passed

+1 :green_heart:
cc
1m 14s

the patch passed

+1 :green_heart:
golang
1m 14s

the patch passed

+1 :green_heart:
javac
1m 14s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
shadedclient
22m 17s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
22m 40s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

132m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3851/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3851

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux c58be576f4eb 4.15.0-162-generic #170-Ubuntu SMP Mon Oct 18 11:38:05 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 57a90c2035e9509631c45c7f6df4a0942184b641

Default Java
Red Hat, Inc.-1.8.0_312-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3851/2/testReport/

Max. process+thread count
604 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3851/2/console

versions
git=2.9.5 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

I think the patch is too trivial to add a test but open to a review feedback otherwise

the changes look fine to me but would be good for someone else active in Hadoop code to take a look.

Thank you @tgravescs and @aajisaka for reviews!


Move some tests from Travis CI to Github Actions

Thanks @martinpitt! :+1:  All update!

@henrywang : Your call of course, but I found the make test_rpmbuild better. I didn't realize at first that this calls sudo docker run ... by itself, which is fine -- it makes it much easier to run that test locally. Of course at some point the Makefile should be changed to work with podman, and unprivileged :) (But that's for another time).


ConceptClass Filter is wrong when a relation matches data source restriction but not CC restriction.

Reported by @KeywanHP and just fixed, I'm adding the issue to keep track of it. This is about the operations of the CC-based filter, which removes/keeps concepts and incident relations, based on specified concept class and, optionally, a given data source.
From comments in the code:
// Suppose gene1(DS=FOO) -> (r1) -> protein1(DS=TAIR), CC = Gene
// Neither gene1 nor protein are filtered (gene1 not in DS, protein1 not in CC)
// Yet getRelationsOfDataSource(TAIR) WILL pick r1, due to prot1.DS

That's because of selectedR.retainAll(graph.getRelationsOfDataSource(dataSource)); (see the filter source) is too broad for the selection that's actually needed. We basically need to retain only the selectedC concepts that were selected by both filtering by CC and then by DS.
There's a test file showing the case (GENE-FOO and its relation should be filtered there, but not the other gene and its relation, despite the fact the latter lands on a concept from TAIR which is not a gene).

Tested with real data, closing.


App doesn't click on supports

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA
FGA build number
1575
Describe the bug
The other day the app was working fine with clicking on support servants for 3T farming. This morning there was a Android update and afterwards it wouldn't work. I have uninstalled and reinstalled thinking it would work but it didn't.
Video
Uploading record (1).mp4…
Device model
Samsung S21 Ultra
Android version
12
Screen size
2400x1080
RAM
No response

https://user-images.githubusercontent.com/90011008/146668645-74d0358c-d3d1-4745-83e9-86fcf79474a1.mp4

Play button should be in the bottom right.


date.getTime is not a function

previously we never face this issue.
our stack trace
`Uncaught (in promise): TypeError: date.getTime is not a function
TypeError: date.getTime is not a function
at NativeDateTimeAdapter.push../node_modules/ng-pick-datetime/date-time/adapter/native-date-time-adapter.class.js.NativeDateTimeAdapter.isValid (native-date-time-adapter.class.js:169)
at NativeDateTimeAdapter.push../node_modules/ng-pick-datetime/date-time/adapter/date-time-adapter.class.js.DateTimeAdapter.compare (date-time-adapter.class.js:25)

at NativeDateTimeAdapter.push../node_modules/ng-pick-datetime/date-time/adapter/date-time-adapter.class.js.DateTimeAdapter.clampDate (date-time-adapter.class.js:69)
at OwlDateTimeContainerComponent.set [as pickerMoment] (date-time-picker-container.component.js:59)

at OwlDateTimeInlineComponent.push../node_modules/ng-pick-datetime/date-time/date-time-inline.component.js.OwlDateTimeInlineComponent.writeValue (date-time-inline.component.js:251)

at forms.js:2118

at forms.js:3273

at Array.forEach (<anonymous>)

at<EMAIL_ADDRESS>(forms.js:3273)

at forms.js:4872

at resolvePromise (zone.js:831)

at zone.js:896

at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:423)

at Object.onInvokeTask (core.js:17290)

at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:422)

at Zone.push../node_modules/zone.js/dist/zone.js.Zone.runTask (zone.js:195)

at drainMicroTaskQueue (zone.js:601)

at ZoneTask.push../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask [as invoke] (zone.js:502)

at invokeTask (zone.js:1744)

at HTMLElement.globalZoneAwareCallback (zone.js:1770)`

our html code
<mdc-dialog-content>
        <owl-date-time-inline [(ngModel)]="selecteddate" [pickerType]="'calendar'" [min]="min"></owl-date-time-inline>
      </mdc-dialog-content>

when ever we open date picker we setting min as current date  and selecteddate  default value null or any previous value if it exist.

resolved this by using new Date(selecteddate)