MELCOR

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
Closes #544
#611
What are the significant changes in functionality due to this change request?
RAVEN-MELCOR interface should be able to parse Control Function Edit data now. This indirectly allows parsing of radionuclide data, solving the problem. For large scale parsing of many forms of radionuclide data parsing, additional code is needed to directly parse radionuclide data, but is suitable for many applications that necessitate radionuclide data parsing, as well as an overwhelming variety of other applications within MELCOR, as nearly any value within MELCOR can be passed into a Control Function.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

Hi @MagresTR, thank you for updating the documentation.
Can we get the example so we can finalize the PR?

I'm working on the example RAVEN input, I've just been using a small slice of code to run MELCORData.py pointed at a test MELCOR output and then dumping the results to a csv file for testing the new code. Will upload as soon as I've got it set up and can verify the results

At this point, I have the interface working, but the tester is still failing it for unknown reasons - it says it needs headers "ZERO" and "Test CF" with those being the two control functions in the test MELCOR input, but both headers are present in the generated output file. I've been poking around the code and am currently at a loss as to why the tester is not recognizing the headers appropriately, if you folks have any ideas I'd greatly appreciate any help you can provide. Thank you so much!
Replication steps:
-Clone https://github.com/MagresTR/raven.git
-Other installation steps as normal
./run_tests --re=framework/CodeInterfaceTests.melcorInterfaceForwardSamplingNoEx
Failure message is "FAILED (In MelcorInterface/dumpMelcorPointSet.csv: Header 'ZERO' is missing
In MelcorInterface/dumpMelcorPointSet.csv: Header 'Test CF' is missing)"
Attached is the dumpMelcorPointSet.csv file for convenience, though I had to change the file extension to a .txt, as RAVEN does not support .csv files.
dumpMelcorPointSet.txt

@MagresTR I know it was like that before, but can I ask you if you can shorten the case? the output files are 54k lines each? Is it possible?

I will download your fork and let you know why the failure is happening.

Done and done, I believe the spacing is fixed and the output files are down to around 2k lines.

@MagresTR  your problem was that you did not regold the gold files. You are adding new data in the RAVEN csv files but the gold file was still the old one.

Just to check, given that this failed the Test mac test, is there any thing I need to change or do? Thank you!

Job Test mac on 60d4bc4 : invalidated by @alfoa

@MagresTR Yes, the PR is fine...I am waiting for the MAC regression test machine to be up and running again to be sure that the tests are green there as well.
Thank you

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code. done
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts). n/a
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details. ok
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass. they pass
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True. n/a
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync. n/a
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done. #544 and #611
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added? n/a

Checklist passed...
Merging...


skTrade

Updating or New:
new
Name of your plugin:
skTrade
Creator:
Sorbon
Version of my plugin:
1.0
Raw link:
https://pastebin.com/Jf7C9fYx
Addons Required:
TuSke
Description:
This Skript allows you to send a trade request to another user on the Server.
You can trade items by placing it in the 3x3 grid inside the trade GUI.
There will be a cooldown, so both players can cancel the trade whenever they want, along the cooldown didn't run out.
/trade to start trading with your friends

Contributing has been moved back to our discord.


request with api key element

При попытке сделать запрос api key выдает ошибку
=IMPORTJSONAPI("https://www.mexc.com/open/api/v2/asset/address/list&api_key='key'";"$..";"@")
ERROR: Request failed for https://www.mexc.com returned code 404. Truncated server response: {"timestamp":"2022-11-22T13:25:36.559+00:00","status":404,"error":"Not Found","message":"","path":"/open/api/v2/asset/address/list&api_key='key'"} (use muteHttpExceptions option to examine full response)
how should I write correctly to get an answer?

You need to actually insert your API key into the URL.


dbeaver/dbeaver#22540 fix altibase constraints creation; move check c…

fix altibase constraints creation (now you can also add UK and check constraints)
move check constraints logic to generic (please check check constraints creation in H2 and Vertica)
fix columns renaming https://github.com/dbeaver/dbeaver/issues/22538

verified


Fix lingering history changes after unmount

Changes

update FEC webpack config: fixes singleton issue with redux
remove history push after app unmounts

the return function from the useApp hooks is called after the app unmounts and it adds a listener on the chrome nav changes
the history change mutates the URL of other apps after you navigate to the from policies

Codecov Report

Merging #237 (a84c778) into master (02cc1b0) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #237      +/-   ##
==========================================
- Coverage   90.69%   90.68%   -0.02%
==========================================
  Files         119      119
  Lines        2516     2513       -3
  Branches      471      471
==========================================
- Hits         2282     2279       -3
  Misses        232      232
  Partials        2        2

Impacted Files
Coverage Δ

src/app/useApp.ts
100.00% <100.00%> (ø)


Look at ways to improve app efficiency

Modern macOS offers a lot of ways for this. When we're comfortable with the state of the application, should profile it.
Xcode screenshot:

Most of this was #12 so closing unless someone can find something spicy.


chore(TS): update typescript definitons

Update to add thru() and subscribe()
Add source to Stream interface as it is needed to write 3rd party libraries in TypeScript
Add Source interface
Add Sink and Scheduler, and Disposable interfaces to complete Source interface
Add Task, ScheduledTask to complete Scheduler interface
Add Subscriber and Subscrition interfaces as needed by subscribe()

cc @AlexGalays

Nice!
Only one remark:  thru is already there at the bottom of Stream in master?

Nice catch! I didn't even notice, more worried that vsc didn't yell at me for declaring it twice

Fixed :+1:

Awesome.
So you need to create new Streams with specific sources of yours?

Yeah, I want to write most-subject in TypeScript :)
So far this is all I have, and these are the types of things I needed to get started. I'll update this PR if there are anymore interfaces I run into, but I think this covers everything
import {Stream, Source} from 'most';

export interface SubjectSource<T> extends Source<T> {
  next: (value: T) => void;
  error: (err: Error) => void;
  complete: (value: T) => void;
}

class Subject<T> extends Stream<T> {
  constructor(source: SubjectSource<T>) {
    super(source);
  }

  next (value: T) {
    (<SubjectSource<T>> this.source).next(value);
  }

  error(err: Error) {
    (<SubjectSource<T>> this.source).error(err);
  }

  complete(value: T) {
    (<SubjectSource<T>> this.source).complete(value);
  }
}

Looks good @TylorS.  See question about end/complete value type.  After we figure that out, I think we can merge this.

Updated with the fixes :)

@TylorS awesome, thanks!  @AlexGalays thanks for the assist!

Thank you, it'd be great to get a patch release for this so I can start making use of this right away :)


Update to new open api

VSCode was updated to include a new API for opening URLs. I should switch to using this.

// open default browser
await vscode.env.openExternal(vscode.Uri.parse("https://github.com/Microsoft/vscode/issues/66741"));

Fixed in 1.1


Remove PR Markdown body from Initial Slack Message with optional verbose feature flag

The markdown of the PR body adds a lot of noise to our slack channels. Removing the rendered markdown should simplify the stream of alerts while still preserving the alerting, updates and other functionality.
Release

I'm not sure how this would be released and whether we need to publish a new action version / update our code to use this feature.

might be nice to try to follow the pr naming/commit messaging format that is used in the repo (some of which drives out the semantic release works - check out the commit history and the config for semantic release, etc)
https://github.com/mlg87/pr-reviewer-slack-notify-action/blob/main/release.config.js
otherwise, LGTM

probably feat in this case: https://github.com/mlg87/pr-reviewer-slack-notify-action/blob/main/release.config.js#L19


Add option to make howdy inactive during night (dark)

I added option which will make howdy inactive during night (on specified hours in pam module and on detection in compare.py). This will allow users to not have to wait for howdy timeout when there is no way howdy would work.

I have only normal camera, which is not working properly at night. This won't affect people with IR emitters, but could help people with day-only webcams.

Thank you for putting in the effort to open a PR for this!
Howdy is primarily made for IR cameras, and i think this is a pretty big patch for pretty niche functionality. In addition, where i live the time it gets dark varies a lot during the year, so i would have to manually update the time values every month or so for it to stay accurate
Maybe this would be better as two cron jobs, one that runs sudo howdy disable 1 at sundown and one that re-enables it at dawn?

I don't know what you mean by "a lot", but I don't think it would be an issue with 'camera' option and hours set with margin. 'on' options would not work anyway, because of light which can be turned on at any time.
I also have one question: when 3.0.0 version?

Sunset somewhere between +/- 16:00 in winter and +/- 22:00 in summer
To be honest i think almost everything is ready for 3.0.0, i don't have a great overview of what still needs to be done

Sunset somewhere between +/- 16:00 in winter and +/- 22:00 in summer

Very sililar to me.

To be honest i think almost everything is ready for 3.0.0, i don't have a great overview of what still needs to be done

I am waiting for it.
Thank You!


[dev-3.x] MainContinuation freezing error

Summary
Querying for data with a frozen ApolloClient crashes the iOS app with a freezing exception.
Version
The issue is present in 3.0.0-alpha03. Last known working version is 3.0.0-dev14.
Description
When the ApolloClient is frozen so is the CancellableContinuation which according to the following line should never happen.
https://github.com/apollographql/apollo-android/blob/ecaad15d88d8af9b8e3dac809f4bc1fb1e9d2e5c/apollo-mpp-utils/src/appleMain/kotlin/com/apollographql/apollo3/mpp/dispatchOnMain.kt#L39
Possible related to #3127.
Also see https://github.com/rickclephas/KMP-NativeCoroutines/issues/10 for some more context and reproduction code by @ychescale9.

Thanks for the thorough investigation! Looks like removing the ensureNeverFrozen does the job, I relaxed the restriction and added more tests in https://github.com/apollographql/apollo-android/pull/3350.
I was under the impression that a continuation should never be frozen but looks like I was wrong there. I'll try to dig a bit more to get a better understanding of where the failing freeze() happens

Thanks @martinbonnin . I also tried to comment out ensureNeverFrozen locally and it's working as expected 👍


Merge Cache_redis.php from develop to release

Hi, it should be merged I think there is a fix for database option. If you use multiple databases on the server this is a need.

If everything was to be merged, there would be no branches.


still working ?

I imported te project in studio ,
can someone provide me latest dependencies out here

Sure, just update gradle plugin


CETopic and BERTopic training fails.

Python version: 3.7.13
Operating System: Ubuntu 16.04.7 LTS

Description
Hi, I am trying to train CETopic and BERTopic on a custom dataset consisting around 400K English tweets. The models train successfully on a very small subset of the same dataset, but training fails on the full dataset.
What I Did
dataset = Dataset()
dataset.load_custom_dataset_from_folder(dataset_path)
tm = CETopicTM(dataset=dataset, topic_model='cetopic', num_topics=200,
               embedding='sentence-transformers/bert-base-nli-mean-tokens',
               word_select_method='tfidf_idfi', dim_size=1, seed=42)
print("Begin model training...")
tm.train()
topic_words = tm.get_topics()

The following error message was displayed for both models.
Begin model training...
Traceback (most recent call last):
  File "cetopic_train.py", line 32, in <module>
    tm.train()
  File "/home/devanshjain/mlda/topicx/baselines/cetopictm.py", line 32, in train
    self.topics = self.model.fit_transform(self.sentences)
  File "/home/devanshjain/mlda/topicx/baselines/cetopic/cetopic.py", line 55, in fit_transform
    embeddings = self._extract_embeddings(documents.Document)
  File "/home/devanshjain/mlda/topicx/baselines/cetopic/cetopic.py", line 84, in _extract_embeddings
    embeddings = self.embedding_model.embed_documents(documents)
  File "/home/devanshjain/mlda/topicx/baselines/cetopic/backend/_base.py", line 69, in embed_documents
    return self.embed(document, verbose)
  File "/home/devanshjain/mlda/topicx/baselines/cetopic/backend/_flair.py", line 71, in embed
    self.embedding_model.embed(sentence)
  File "/home/devanshjain/miniconda3/envs/cetopic/lib/python3.7/site-packages/flair/embeddings/base.py", line 62, in embed
    self._add_embeddings_internal(data_points)
  File "/home/devanshjain/miniconda3/envs/cetopic/lib/python3.7/site-packages/flair/embeddings/base.py", line 766, in _add_embeddings_internal
    self._add_embeddings_to_sentences(expanded_sentences)
  File "/home/devanshjain/miniconda3/envs/cetopic/lib/python3.7/site-packages/flair/embeddings/base.py", line 684, in _add_embeddings_to_sentences
    return_tensors="pt",
  File "/home/devanshjain/miniconda3/envs/cetopic/lib/python3.7/site-packages/transformers/tokenization_utils_base.py", line 2512, in __call__
    **kwargs,
  File "/home/devanshjain/miniconda3/envs/cetopic/lib/python3.7/site-packages/transformers/tokenization_utils_base.py", line 2703, in batch_encode_plus
    **kwargs,
  File "/home/devanshjain/miniconda3/envs/cetopic/lib/python3.7/site-packages/transformers/tokenization_utils_fast.py", line 459, in _batch_encode_plus
    for key in tokens_and_encodings[0][0].keys():
IndexError: list index out of range

Thanks for the nice work by the way!

Hi,
There could be a lot of reasons for this issue. One possible reason might be in your dataset.
In the paper, we use OCTIS to load the preprocessed dataset. When you experiment on your custom dataset, have you followed their preprocessing format?
After preprocessing your data, is it possible that some of the sentences become empty strings, which might cause this issue, like this one?
Lastly, 400k data is very huge, which may take a long time for training, and we didn't test our methods on such big data. As suggested by BERTopic, you could also try methods here and here.
Thanks,

Thanks for the prompt response. It was an issue with empty strings after tokenisation.
I added a try...except block to skip the empty strings and the model worked fine! Thanks for the help.


test: set up cluster with additional insecure registries

This is useful when there are additional local registries that don't
have an SSL certificate that Clear Linux trusts out-of-the-box.

makes sense and looks good, I plan to test it in action as well.
This reduces the patching I use to do for my local deployments.

tried clear-kvm driver deployment with added local registry (where images are), works.

@okartau please merge


#96511482 Change key bindings for Squire

We're only going to be supporting bold and italics through strong & em for the near future, so we're removing the key bindings for italics, strikethrough, subscript, superscript etc. We're also replacing the b tag with strong and the i tag with em.

Would you be nice enough to submodule update the web-client once this is merged?

Updated WC submodule.


Please follow semantic versioning

OpenSSL is a central piece of infrastructure on virtually every Linux system. As such, applications linking to it should have the assurance that new OpenSSL versions don't break applications compiled against older OpenSSL versions.
According to https://semver.org/,

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.

So OpenSSL should have added "functionality in a backwards-compatible manner" going from 1.0 to 1.1. However, applications compiled against OpenSSL 1.0 seem to break when OpenSSL is updated to 1.1.
There are two ways to address this:

Ensure that all applications compiled against OpenSSL 1.0 continue to run when OpenSSL is updated to 1.1; or
Rename OpenSSL 1.1 to 2.0 in order to make clear that you made incompatible API changes; advise users to install 1.x in addition to 2.x if they want to continue to run applications compiled against 1.x

If application developers (such as Firefox and Chrome) cannot rely on backward compatibility in OpenSSL, they are effectively forced to ship privately bundled versions, leading to duplication and locking them out from system-wide security patches.
References:

https://github.com/probonopd/AppImages/commit/6c7473d8cdaaa2572248dcc53d7f617a577ade6b
http://stackoverflow.com/questions/32644157/forcing-a-binary-to-use-a-specific-newer-version-of-a-shared-library-so
https://abi-laboratory.pro/tracker/timeline/openssl/

OpenSSL will follow semantic versioning. Thanks!
https://www.openssl.org/blog/blog/2018/11/28/version/

That blog post says explicitly that we are NOT doing that:
"We are not at this stage directly adopting semantic versioning because it would mean changing our current LTS policies and practices."
I'm closing this issue because we considered it in some depth and at length, but decided not to.

changing our current LTS policies and practices

Yes, I guess this is what I was asking for.
Oh well.

You should read https://semver.org/
Semantic versioning is more than a version number layout, it's also a strict set of rules for when each number changes. Some of these rules differ ever so slightly from our practice, so we may be close to semantic versioning, but that's also all.
If it only looks like a duck but doesn't quite swim like a duck, it's not a duck...

But then, why not make it a real duck? (I mean, instead of "we are not doing it because our policy is to not do it" - real reasons?)

I'm assuming that I don't need to read about semver, but rather about OpenSSL practices. Maybe the article should have contained two sentences or a few bullets points explaining the differences as I'm pretty sure that I'm not the only one mislead by it.
The only statement indicating a difference is

We are not at this stage directly adopting semantic versioning because it would mean changing our current LTS policies and practices.

which is directly followed by

The current 1.1.1 and 1.0.2 versioning scheme will remain unchanged.

which can be easily interpreted that We are not at this stage directly adopting semantic versioning simply means that for current release strings it won't be changed.

The only statement indicating a difference is

We are not at this stage directly adopting semantic versioning because it would mean changing our current LTS policies and practices.

which is directly followed by

The current 1.1.1 and 1.0.2 versioning scheme will remain unchanged.

which can be easily interpreted that We are not at this stage directly adopting semantic versioning simply means that for current release strings it won't be changed.

The 1.1.1 series will continue to be 1.1.1 followed by a letter for patch updates.
The 1.0.2 series will continue to be 1.0.2 followed by a letter for patch updates.
However, the next major release will be 3.0.0 and will have a MAJOR.MINOR.PATCH version, where the PATCH level number will be used in place of the patch letters.
Our major deviation from semantic versioning is that we allow the addition of new public functions in a PATCH update.  Remember the setter and getter functions that were missing in 1.1.0?  They got added in patch updates.  This is something that semantic versioning does not allow.  I justify it by making a difference between adding functions that were omitted where they shouldn't (the omission is a bug) have and adding functions that are actually new features.  The former is acceptable for a patch update according to our policy, the latter is not.  So in summary, semantic versioning is problematic for us because semantic versioning views all added functions as new features, we do not necessarely do so.

As soon as #7724 goes through, the master branch will have shifted to the new version scheme.

@mattcaswell

I'm closing this issue because we considered it in some depth and at length, but decided not to.

Can you give rationale behind this decision?
Users are running into practical issues every day due to this. Example:
https://github.com/antony-jr/QTalarm-AppImage/issues/1

The major reason we can not adopt semantic versioning is because
we support more than 1 version of the software, and we might need
to add new features to older versions of the software. Adding such
a feature to older software under semantic versioning will require
that the minor number gets changed, but that minor number might
already exist. So we will change the patch number instead in that
case.
In the past we have needed to add new functions to old versions
many times. If you look at the util/libcrypto.num and
util/libssl.num files in the OpenSSL_1_1_0-stable branch, and look
at all the lines that don't have 1_1_0, but things like 1_1_0d,
you'll see that we had to add many functions.

Note also that the new versioning scheme we are adopting for our next version (3.0) is very similar in a lot of ways to semantic versioning, but doesn't quite meet the official definition due to the issue @kroeckx described above. See:
https://www.openssl.org/blog/blog/2018/11/28/version/

However, the next major release will be 3.0.0 and will have a MAJOR.MINOR.PATCH version, where the PATCH level number will be used in place of the patch letters.

Nice!

Our major deviation from semantic versioning is that we allow the addition of new public functions in a PATCH update. Remember the setter and getter functions that were missing in 1.1.0? They got added in patch updates. This is something that semantic versioning does not allow. I justify it by making a difference between adding functions that were omitted where they shouldn't (the omission is a bug) have and adding functions that are actually new features. The former is acceptable for a patch update according to our policy, the latter is not. So in summary, semantic versioning is problematic for us because semantic versioning views all added functions as new features, we do not necessarely do so.

Can you elaborate why it is important for you to make this destinction between new features and "bug fix features"? I mean, you could stick with your policy to not add new features in what you call "patches" while using semantic versioning to indicate that new functions got introduced with your bug fix. Does that make sense?
Also, if it does not, you are probably not the only project having this problem with semantic versioning. So you might want to open an issue there so that they are aware of this problem. Maybe they can find a standardized solution for it. Because I think the biggest issue here is to not comply with the standard which causes confusion. And if the standard does not fit you, maybe it needs to be changed.

I mean, you could stick with your policy to not add new features in what you call "patches" while using semantic versioning to indicate that new functions got introduced with your bug fix. Does that make sense?

There are times when we have needed to add new public functions as part of a patch, but that's not enough to make it a minor release (i.e. new feature release).  When we released 1.1.0, we had forgotten to add a number of accessor functions for the types that are now opaque, and we added them in so called "letter updates" (which corresponds in spirit to "patch" releases).  If you follow strict semantic versioning, this is forbidden.
I see no point bothering the semver folks.  They have made a set of rules that are consistent within their realm of thinking, and they do note among their tutorials and stuff that there are many projects that are close to semver, but not quite...  and in the end, that's quite all right, really.
The main thing is that:

for PATCH releases, there should be no new public features and no changed public functions.  Semver says that new public functions are new features, we say that it depends...  I think we've concluded that whole new APIs (i.e. set of functions) constitute new features.  This is still upwardly compatible, both API and ABI wise, so in spirit, semver agrees with us (even if not strictly).
for MINOR releases, there can be new public features.  There, semver agrees with us, even when read strictly.
for MAJOR releases, anything goes (even though doesn't have to be breaking).  Again, semver agrees with us there.

So in essence, we are close enough to semver to be happy.

I prefer to have things rather standardized, maybe semver can be changed if they agree with you in spirit.
Also after reading https://github.com/openssl/openssl/issues/5042#issuecomment-494534534 which I now notice to be probably a bit different from the problem you describe, I created an issue at semver about this: https://github.com/semver/semver/issues/532

There are times when we have needed to add new public functions as part of a patch, but that's not enough to make it a minor release (i.e. new feature release). When we released 1.1.0, we had forgotten to add a number of accessor functions for the types that are now opaque, and we added them in so called "letter updates" (which corresponds in spirit to "patch" releases). If you follow strict semantic versioning, this is forbidden.

Is it forbidden, though? It's a bug fix, where the bug happened to be "failure to export certain functions". Them not having been written is irrelevant to the reality: they should've been there, and weren't. This is a bug fix, and therefore should use the patch number. Yes, it's technically changing the symbol table, but SemVer doesn't mention symbol tables. Bug fixes nearly always change behaviour, but if the previous behaviour was useless, flawed or violated interfaces, that's fine.
You defined (a category of) interfaces that opaque types should possess, then fixed the bug that "not all opaque types had this interface". That's a patch number increment, because it's a bug fix that didn't introduce new features (the functions were meant to be there all along to implement the feature (you thought) you were including), doesn't break existing, correctly-working code and would, in fact, cause correct code that didn't work before to begin working.
That's not against SemVer.

Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API.

Ref: https://semver.org/#spec-item-7
But seriously, I don't understand the need to quibble over details. We have chosen something that's close enough, even though not exactly "right" according to a strict reading of the rules. But frankly, I find the difference too small to spend a lot of time and energy on. If you think we do follow semver, that's absolutely fine, but it's not like we're seeking some kind of branding...
This issue is closed.

Just to add i caution note to your version scheme.
You mention that you guarantee API/ABI compatibility between the same MAJOR versions, yet you allow the additions of new functions in a PATCH release of a older version.
I don't know if you have thought that through, but if not ill hit on it here...
Say you release have an interface that has the following functions in the releases as outlined here:
v1.0.0

FuncA
FuncB

v1.1.0

FuncA
FuncB
FuncC

v1.2.0

FuncA
FuncB
FuncC
FuncD

In order to maintain your promise, the only thing you can add to v1.0.1 is FuncC, if you add FuncD or another even a FuncE, you are breaking backwards compatibility of you v1.1.0 as that does not have that function.
I just wanted raise that, if your only ever backporting features from one version ahead, you should be fine on the promises.

We would most likely add a FuncE either to all, and release
v1.0.1, v1.1.1 and v1.2.1. Or maybe only add it to v1.1 and v1.2
because it doesn't affect v1.0.
We also use symbol versioning (on platforms that support it).
The symbol version would be v1.0.1 in all v1.* releases.
This actually works properly if you upgrade from v1.0.1 to v1.1.1
or v1.2.1. If you try to upgrade to v1.2.0, it would clearly
break, but why would you want to do that?

@kroeckx I dont think you ar understandung what I am pointing out, I don’c care what you do an how you manage versions. I only pointed out that if you do what you do, you are violating your own version scheme.
At least from how it is put forth in this thread, so you probably want to correct the scheme then.

In order to maintain your promise, the only thing you can add to v1.0.1 is FuncC, if you add FuncD or another even a FuncE, you are breaking backwards compatibility of your v1.1.0 as that does not have that function.

If we add a new function that we deem a bug fix (i.e one of those missing accessory functions I mentioned), and therefore a patch level change, we do apply that same patch to all version series (within the same major version) we support. In other words, to go from your example, if we would release FuncBbis in 1.0.1, we would have to release 1.1.1 and 1.2.1 with that same function added (and with the same transfer vector location on platforms where that's still applicable).
Does that make more sense to you?

@levitte I understand what it is your doing, and to the extend your doing it you are breaking your promise with our version scheme.
If i where to be really harsh on the way it's formulated in https://www.openssl.org/blog/blog/2018/11/28/version/

API/ABI` compatibility will only be guaranteed for the same MAJOR version number.

It could even be read as you guarantee compatibility going from 1.3.0 to 1.0.0 as you don't touch order of versions at all. I obviously ignored that and just figured you mean "Backwards API/ABI` compatibility will only be guaranteed for the same MAJOR version number." (which makes a lot more sense)...
But your still breaking the promise as your not staying backwards compatibly within the Major version when you consider is the natural order of version numbers.
As i stated to @kroeckx , I don't care what you do and why, I only wanted to point out that what you promise people in your version scheme, is not what you deliver. As such you should go over the scheme again and clarify it. - And I was fairly certain that it was a angle you overlooked as you wrote the scheme, as such you "backwards" compatibility is based on a combination of the natural order of the version number, e.g. 1.2.1 is greater than 1.1.1 and 1.2.0, but ALSO the date that it was released.

Does it make sense for me that you do that?...
Not at all, as a Software Architect, Developer and Package Consumer, I can't see any reason at all to ever not upgrade to the latest minor version if backwards compatibility is promised, and ESPECIALLY within something as the OpenSSL package as that is security related (I would even put great effort in staying with the latest major for such packages). Anything else would be ludicrous to me. BUT I am not here to discuss that

@kroeckx

If you try to upgrade to v1.2.0, it would clearly
break, but why would you want to do that?

I guess that incompatibility is what @jeme was pointing out. I am not sure why one would upgrade to v1.2.0. At least you claim that it should be compatible in your blog.

@jeme, understood. Thank you for the thorough input.

This is still causing trouble 4 years later.
Running 20.04.4 LTS (Focal Fossa) and wanting to use this software that requires libssl1.0, but apparently all that Ubuntu nowadays provides in main is libssl1.1.
There should really be a policy that wherever essential system packages like this get updated in binary breaking ways, then t least the 3 versions before it should still be shipped in distributions so as not to break existing software. Unfortunately all Linux distributions seem to care for is the software inside the distribution, not the software users want to run on top of the distribution ("sideloading").
Stuff like this is really a pain!
sudo apt-get install libssl1.1
Reading package lists... Done
Building dependency tree
Reading state information... Done
libssl1.1 is already the newest version (1.1.1f-1ubuntu2.12).
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

sudo apt-get install libssl1.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libssl1.0-dev' for regex 'libssl1.0'
Note, selecting 'libssl1.0.0' for regex 'libssl1.0'
Note, selecting 'libssl1.0.2' for regex 'libssl1.0'
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

$ sudo apt install libssl1.0.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libssl1.0.0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libssl1.0.0' has no installation candidate

Let's hope that 1.2.x.will either

Be compatible in such ways that software compiled for 1.1.x can still run with 1.2.x, or
Be called 2.0.x (because it breaks existing software again)

@probonopd lease see: https://www.openssl.org/blog/blog/2018/11/28/version/
There won't be a 1.2 nor 2.0.
2.0 was used by the FIPS Object Module (and LibreSSL)
OpenSSL's current release is 3.0; and is now based on semantic versioning as of that version. 3.0 is the current LTS release, the prior LTS release (1.0.2) will be out of support in ~17 months.

My mistake... 1.1.1 is the prior LTS release, and will be out of support in ~17 months.

OpenSSL's current release is 3.0; and is now based on semantic versioning as of that version.

:+1: :+1: :+1:
Now, will distributions (read: Ubuntu main) still carry 1.0 and 1.1 once 3.0 is released? I strongly hope so!

@probonopd OpenSSL 3.0 was released last year, and 3.0.3 will be released next week. Have a read of https://www.openssl.org/source/

and is now based on semantic versioning as of that version

"based on" is an important caveat. As per the blog post that @tmshort links to:

This more closely aligns with the expectations of users who are familiar with semantic versioning. We are not at this stage directly adopting semantic versioning because it would mean changing our current LTS policies and practices.

Now, will distributions (read: Ubuntu main) still carry 1.0 and 1.1 once 3.0 is released? I strongly hope so!

So, I installed Ubuntu 22.04 over 21.10... and... it installs OpenSSL 3.0, but removes OpenSSL 1.1... However, grub still depends on 1.1. Which ends up breaking apt because grub can't complete its updates. You can still install the 21.10 or earlier (e.g. focal) version of OpenSSL 1.1 onto 22.04.
It is "ok" for a (Unix-like) system to have multiple versions of OpenSSL installed, the shared objects are versioned, as are their names. The only complications come when building applications. You really can only have one set of header files, and one set of non-versioned symlinks to versioned shared objects (e.g. libcryto.so -> libcrypto.so.3 and libssl.so -> libssl.so.3 symlinks).


How doctor or Admin add time Slot for Appointment

Your Project are very good
How doctor or Admin add time Slot for Appointment

Can you guide me Please

Did u find a solution of ur question? #Aliya09


[QUESTION] InvalidOperationException: You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings.

I'm using Unity 2021.3.0f1 (LTS) on Linux and created a new project. I added all packages to the manifest.json file. The file now looks like
{
  "scopedRegistries": [
    {
      "name": "NPM Registry",
      "url": "https://registry.npmjs.org",
      "scopes": [
        "com.unity-atoms.unity-atoms-core",
        "com.unity-atoms.unity-atoms-base-atoms",
        "com.unity-atoms.unity-atoms-fsm",
        "com.unity-atoms.unity-atoms-mobile",
        "com.unity-atoms.unity-atoms-mono-hooks",
        "com.unity-atoms.unity-atoms-tags",
        "com.unity-atoms.unity-atoms-scene-mgmt",
        "com.unity-atoms.unity-atoms-ui",
        "com.unity-atoms.unity-atoms-input-system"
      ]
    }
  ],
  "dependencies": {
    "com.unity-atoms.unity-atoms-base-atoms": "4.4.4",
    "com.unity-atoms.unity-atoms-core": "4.4.4",
    "com.unity-atoms.unity-atoms-fsm": "4.4.4",
    "com.unity-atoms.unity-atoms-input-system": "4.4.4",
    "com.unity-atoms.unity-atoms-mobile": "4.4.4",
    "com.unity-atoms.unity-atoms-mono-hooks": "4.4.4",
    "com.unity-atoms.unity-atoms-scene-mgmt": "4.4.4",
    "com.unity-atoms.unity-atoms-tags": "4.4.4",
    "com.unity-atoms.unity-atoms-ui": "4.4.4",
    "com.unity.collab-proxy": "1.15.15",
    "com.unity.feature.2d": "1.0.0",
    "com.unity.ide.rider": "3.0.13",
    "com.unity.ide.visualstudio": "2.0.14",
    "com.unity.ide.vscode": "1.2.5",
    "com.unity.test-framework": "1.1.31",
    "com.unity.textmeshpro": "3.0.6",
    "com.unity.timeline": "1.6.4",
    "com.unity.toolchain.linux-x86_64": "2.0.0",
    "com.unity.ugui": "1.0.0",
    "com.unity.visualscripting": "1.7.6",
    "com.unity.modules.ai": "1.0.0",
    "com.unity.modules.androidjni": "1.0.0",
    "com.unity.modules.animation": "1.0.0",
    "com.unity.modules.assetbundle": "1.0.0",
    "com.unity.modules.audio": "1.0.0",
    "com.unity.modules.cloth": "1.0.0",
    "com.unity.modules.director": "1.0.0",
    "com.unity.modules.imageconversion": "1.0.0",
    "com.unity.modules.imgui": "1.0.0",
    "com.unity.modules.jsonserialize": "1.0.0",
    "com.unity.modules.particlesystem": "1.0.0",
    "com.unity.modules.physics": "1.0.0",
    "com.unity.modules.physics2d": "1.0.0",
    "com.unity.modules.screencapture": "1.0.0",
    "com.unity.modules.terrain": "1.0.0",
    "com.unity.modules.terrainphysics": "1.0.0",
    "com.unity.modules.tilemap": "1.0.0",
    "com.unity.modules.ui": "1.0.0",
    "com.unity.modules.uielements": "1.0.0",
    "com.unity.modules.umbra": "1.0.0",
    "com.unity.modules.unityanalytics": "1.0.0",
    "com.unity.modules.unitywebrequest": "1.0.0",
    "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
    "com.unity.modules.unitywebrequestaudio": "1.0.0",
    "com.unity.modules.unitywebrequesttexture": "1.0.0",
    "com.unity.modules.unitywebrequestwww": "1.0.0",
    "com.unity.modules.vehicles": "1.0.0",
    "com.unity.modules.video": "1.0.0",
    "com.unity.modules.vr": "1.0.0",
    "com.unity.modules.wind": "1.0.0",
    "com.unity.modules.xr": "1.0.0"
  }
}

After that I restarted the engine and enabled the new input system. Launching the game throws the following error

InvalidOperationException: You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings.

Should I stick to the old input system? What is the suggested way to fix this error?

The Unity Atoms Inputsystem package is made for Unity's new InputSystem. If you go to Edit -> Project Settings -> Player -> Other Settings -> Under Configuration "Active Input Handling*". When you select "Both" here the errors should disappear and you can use both InputSystems. Another option is to remove the Unity Atoms inputsystem subpackage until you need it.

Thanks @ThimoDEV
I think it might be good to notice that information in the docs, no?
Maybe here? https://unity-atoms.github.io/unity-atoms/subpackages/input-system

I think it might be good to notice that information in the docs, no?

Maybe a note that it uses the old Input System, but the error message tells you that the error is in the "Project Settings -> "Active Input Handling". and since there are only 3 options ( old, new, both ) you can't do anything wrong actually


fix: readme

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


22.1.2 hanging after upgrade

System information:

Operating system (distribution) and version - Windows Server 2012R2
DBeaver version - Latest on website as of 7/21/2022 10:00 AM DST
Additional extensions

Connection specification:

Database name and version IBM V7R3
Driver name IBM DB2 odbc
Do you use tunnels or proxies (SSH, SOCKS, etc)?  no

Describe the problem you're observing:
immediate previous version was working no problem.  With this upgrade, data sets returned with previously working query (no changes) of 144,000 rows - dbbeaver hangs.
NOTE:  the query appears to return all of the requested rows in a timely manner, and immediately afterwards pops up a small message about 'Copying', and then hangs

#17136

Probably fixed in #17068
Fix will be available in the next release - 22.1.3

I am also finding that since upgrading to 22.1.2 , dbt is now hanging on all queries. It seems to get stuck on the "Load composite cache: Load composite objects".

Hello @nathmate
What database do you use?

Closed as duplicate of #17068
Fix is already available in version 22.1.3
https://dbeaver.io/download/


pass query to external search tab bugfix

References

Fixes #3295

Description
Fixes the linked issue where the value for lookup would not be filled in is query in the external source tab
Instructions for Reviewers
Verify the issue now is fixed and the "Expected behaviour" section is how it works.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[x] My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes ESLint validation using yarn lint
[x] My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] My PR aligns with Accessibility guidelines if it makes changes to the user interface.
[x] My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
[x] My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
[x] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[x] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
[x] If my PR fixes an issue ticket, I've linked them together.

Putting PR on hold as found out for one of our own projects that this might still have issues, will re-open soon after having tested new solution


bug: tooltip doesn't work as expected

Description
Tooltip doesn't work as expected.
Expected behaviour
The tooltip should not overlay the text
Screenshot

PS: There isn't any template for issue or PR should I make one?
What's your opinion @pranshuchittora

Feel free to open a PR for the fix.
PS: There's already a PR for templates in progress.

I'm working on it.

There was a typo error in the popover props (popOver was incorrect), and hence the popover text wasn't visible. It seems to be fixed in PR #44. Furthermore, the tooltip's wrong positioning appears to be caused by react-native-elements itself (there is already an issue based on this).

This issue should be fixed after the tooltip2 PR is merged: https://github.com/react-native-elements/react-native-elements/pull/2842

please assign me this issue


survey-type.ttl - vocpres-uat is out of sync from prod

It appears that survey-type in master was pushed to vocprez prod but it not to vocprez uat. It remains as a previous version in vocprez uat. Is it GSQ's responsibility to keep the two sites in lockstep?

probably solved. DC confirmed this is not GSQ work and that SRA (through John Hudson) need to run the script to pull the latest vocabs from github into both the uat and prod VOCPREZ. This apparently has not been done consistently. Lisa Woodhead actioning.


[occm] Build Release for 1.1.1 for Helm Chart

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Seems like occm 1.1.1 is merged into master but not yet released on the Helm chart.
What you expected to happen:
Expecting 1.1.1 to be available for consumption to resolve RBAC issues.
How to reproduce it:
❯ helm repo add cpo https://kubernetes.github.io/cloud-provider-openstack
❯ helm repo update
❯ helm search repo cpo
NAME                                    CHART VERSION   APP VERSION     DESCRIPTION
cpo/openstack-cinder-csi                1.3.8           v1.21.0         Cinder CSI Chart for OpenStack
cpo/openstack-cloud-controller-manager  1.0.1           v1.21.0         Openstack Cloud Controller Manager Helm Chart
cpo/openstack-manila-csi                1.1.2           v1.21.0         Manila CSI Chart for OpenStack

Anything else we need to know?:
I may be under the incorrect assumption that 1.1.1 is available for consumption.

@atsai1220 Currently, they are only released once the new branch is cut or on new release. You can expect it to be available by Aug first week once 1.22 is targeted to release.

@atsai1220 New version of helm charts are released. https://github.com/kubernetes/cloud-provider-openstack/releases/tag/openstack-cloud-controller-manager-1.1.2 . please check.

/close


Create a way to work with EV3

This could be done with David Tseng, who is working on and EV3 component.  And/or has simpel examples of controlling EV3 from Bluetooth.  And/or see what Liz can do.

I will start by talking with David.


feat: strict inflation schedule

Description
Part of https://github.com/celestiaorg/celestia-app/issues/1570
Implement the strict inflation schedule specified in https://github.com/celestiaorg/celestia-app/pull/1584
Remaining tasks

[x] implement inflation rate change based on block timestamp rather than block height
[x] set genesis time in x/mint state
[x] move MintDenom from param to x/mint state
[x] remove TestRandomizedGenState
[x] investigate why TestQueryGRPC / other integration tests are never run
[x] write a test that 1. starts a new chain, 2. verifies state of x/mint module for first few blocks, 3. skips ahead to a block one year later, 4. verifies inflation rate went down a bit

FLUPs

https://github.com/celestiaorg/celestia-app/issues/1730

please have a look at the table above. If we do not round the inflation rates, it will look like that.

table looks fine IMO.

Codecov Report

Merging #1578 (139c84f) into main (e223493) will decrease coverage by 0.77%.
The diff coverage is 34.61%.

@@            Coverage Diff             @@
##             main    #1578      +/-   ##
==========================================
- Coverage   52.58%   51.81%   -0.77%
==========================================
  Files          97      108      +11
  Lines        6278     6562     +284
==========================================
+ Hits         3301     3400      +99
- Misses       2644     2826     +182
- Partials      333      336       +3

Impacted Files
Coverage Δ

app/app.go
4.52% <0.00%> (ø)

app/module.go
29.50% <0.00%> (ø)

x/mint/abci.go
0.00% <0.00%> (ø)

x/mint/module.go
0.00% <0.00%> (ø)

x/mint/types/genesis.go
0.00% <0.00%> (ø)

x/mint/types/params.go
0.00% <0.00%> (ø)

x/mint/keeper/querier.go
2.22% <2.22%> (ø)

x/mint/keeper/genesis.go
50.00% <50.00%> (ø)

x/mint/types/minter.go
72.22% <72.22%> (ø)

x/mint/keeper/keeper.go
83.33% <83.33%> (ø)

... and 3 more

but the actual minting of coins depends on block height and a hardcoded estimation at the amount of blocks per year.

Clarification: the actual minting of coins depends on a hardcoded estimation for the amount of blocks per year but it doesn't depend on block height. @cmwaters

what happens if the blocks per year is not accurate here?

nvm just saw #1730

CI fails on a test that wasn't modified https://github.com/celestiaorg/celestia-app/actions/runs/4962401229/jobs/8880507945#step:6:19

change the way we are calculating inflation per block to not round down nearly as much (see comment below, also this is my preferred option)

After doing this, the test passes for a proposal to spend 1utia 🎊


Add Azure disk integration test

Test that we can actually create a disk in an Azure VM. This is very
similar to the GCP and AWS disk integration tests.

@skschneider @yuyantingzero Please take a look.

One typo. Please fix, then LGTM.

Fixed typo, now merging. Thanks for the review.


Deserialization fails when directly inherit Step class

What is the bug?
When serializing/deserializing CatBoost model using joblib, the deserialization fails with the following error object has no attribute '_name'
How to reproduce it?
import pandas as pd
from sklearn.model_selection import train_test_split
from sklearn.metrics import accuracy_score
from baikal import Input, Model, make_step, Step
from baikal.steps import Stack
from catboost import CatBoostClassifier
from sklearn.linear_model import LinearRegression

# load data
df = pd.read_csv('prime.csv',
#     'https://raw.githubusercontent.com/jbrownlee/Datasets/master/pima-indians-diabetes.data.csv',
    header=None)
dataset = df.values

class CatBoostClassifierStep(Step, CatBoostClassifier):
    def __init__(self, *args, name=None, n_outputs=1, **kwargs):
        super().__init__(*args, name=name, n_outputs=n_outputs, **kwargs)

    def __hash__(self):
        return hash(super().name)

x = Input()
y = Input()

xgbStep = LinearRegressionStep()(x, y)
model = Model(x, xgbStep, y)
model.fit(dataset[:,0:8], dataset[:,8])

import joblib
s = joblib.dump(model, 't.pkl')

model2 = joblib.load('t.pkl')
model2.predict(dataset[:,0:8])

What versions are you using?
baikal==0.4.1
scikit-learn==0.23.1
python==3.6
Any additional information?
AttributeError          Traceback (most recent call last)
<ipython-input-5-139f76755734> in <module>
     31
     32 model2 = joblib.load('t.pkl')
---> 33 model2.predict(dataset[:,0:8])

/opt/anaconda3/envs/plaid/lib/python3.7/site-packages/baikal/_core/model.py in predict(self, X, output_names)
    468         # without having to change the inputs accordingly.
    469         nodes = self._get_required_nodes(
--> 470             X_norm, [], outputs, allow_unused_inputs=True, follow_targets=False
    471         )
    472

/opt/anaconda3/envs/plaid/lib/python3.7/site-packages/baikal/_core/model.py in _get_required_nodes(self, given_inputs, given_targets, desired_outputs, allow_unused_inputs, allow_unused_targets, follow_targets, ignore_trainable_false)
    189
    190         for output in desired_outputs:
--> 191             required_nodes |= backtrack(output)
    192
    193         # Check for missing inputs/targets

/opt/anaconda3/envs/plaid/lib/python3.7/site-packages/baikal/_core/model.py in backtrack(output)
    174                 return nodes_required_by_output
    175
--> 176             parent_node = output.node
    177             if parent_node in required_nodes:
    178                 return nodes_required_by_output

/opt/anaconda3/envs/plaid/lib/python3.7/site-packages/baikal/_core/data_placeholder.py in node(self)
     42     @property
     43     def node(self):
---> 44         return self.step._nodes[self.port]
     45
     46     def __repr__(self):

AttributeError: 'CatBoostClassifierStep' object has no attribute '_nodes'

Thank you for opening this issue.
It seems that catboost does not play well with subclasses in general. Even if you don't use baikal at all, pickling an instance of a subclass will fail to recover the attributes of the subclass.
import dill
from catboost import CatBoostClassifier

class CatBoostClassifierSub(CatBoostClassifier):
    def __init__(self):
        super().__init__()
        self._nodes = []

a = CatBoostClassifierSub()
b = dill.loads(dill.dumps(a))

assert hasattr(a, "_nodes")  # passes
assert hasattr(b, "_nodes")  # fails

I think this is because CatBoostClassifier implements its own __getstate__ method (here) that persists specific attributes. So it seems when you subclass from it and want it to be pickle-able you have to override the __getstate__ and __setstate__ methods to call the method of the parent class and add the attributes of the child class. Something along these lines:
class CatBoostClassifierStep(Step, CatBoostClassifier):
    def __init__(self, *args, name=None, **kwargs):
        super().__init__(*args, name=name, **kwargs)

    def __getstate__(self):
        state = super().__getstate__()
        state["_name"] = self._name
        state["_nodes"] = self._nodes
        state["_n_outputs"] = self._n_outputs

    def __setstate__(self, state):
        super().__setstate__(state)
        self._name = state["_name"]
        self._nodes = state["_nodes"]
        self._n_outputs = state["_n_outputs"]

Can you try the above and see if it works (might need some adjustments, I haven't tried this myself)? (I don't think you need to implement __setstate__ and __getstate__ for any other classes)

Answering your question from the PR thread:

do you have an example of serialization ?

There is an example in the tests here.

I tried explicitly implementing getstate and setstate but that didn't help. Still getting _nodes not defined.
]

hmm..interesting my cdeddddddddddddddddd

For anyone else, the solution suggested by Alegonz actually works. There was just one problem. getstate didn't include return statement. For reference this is how to create CatbootClassifier Step
class CatBoostClassifierStep(Step, CatBoostClassifier):
    def __init__(self, *args, name=None, n_outputs=1, **kwargs):
        super().__init__(*args, name=name, n_outputs=n_outputs, **kwargs)
        self._nodes = []

    def __getstate__(self):
        state = super().__getstate__()
        state["_name"] = self._name
        state["_nodes"] = self._nodes
        state["_n_outputs"] = self._n_outputs
        return state. // make sure to return the state

    def __setstate__(self, state):
        self._name = state["_name"]
        self._nodes = state["_nodes"]
        self._n_outputs = state["_n_outputs"]
        super().__setstate__(state)

    def __hash__(self):  // include this otherwise you will get hashing error
        return hash(super().name)

@ragrawal
Thank you for confirming! I'll add an entry in the documentation about this special case of catboost estimators.
I'm planning to patch baikal to address the case of un-hashable steps reported in Issue #37 and avoid the __hash__ workaround.


Storybook build fails in plone/documentation

See error log from build job in plone/documentation
https://github.com/plone/documentation/actions/runs/3141183181/jobs/5103412176
A proposed solution is in the docs for storybook:
https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#deprecated-default-postcss-plugins
Logs
info => Using implicit CSS loaders
(node:2584) DeprecationWarning: Default PostCSS plugins are deprecated. When switching to '@storybook/addon-postcss',
you will need to add your own plugins, such as 'postcss-flexbugs-fixes' and 'autoprefixer'.

See https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#deprecated-default-postcss-plugins for details.
(Use `node --trace-deprecation ...` to show where the warning was created)
/home/runner/work/documentation/documentation/submodules/volto/node_modules/razzle/config/env.js:78
    if (!options.forceRuntimeEnvVars.includes(key) || is_dev) {
                                     ^

TypeError: Cannot read properties of undefined (reading 'includes')
    at /home/runner/work/documentation/documentation/submodules/volto/node_modules/razzle/config/env.js:78:38
    at Array.reduce (<anonymous>)
    at getClientEnvironment (/home/runner/work/documentation/documentation/submodules/volto/node_modules/razzle/config/env.js:77:40)
    at /home/runner/work/documentation/documentation/submodules/volto/node_modules/razzle/config/createConfigAsync.js:122:20
    at new Promise (<anonymous>)
    at module.exports (/home/runner/work/documentation/documentation/submodules/volto/node_modules/razzle/config/createConfigAsync.js:78:10)
    at Object.webpackFinal (/home/runner/work/documentation/documentation/submodules/volto/.storybook/main.js:44:24)
    at /home/runner/work/documentation/documentation/submodules/volto/node_modules/@storybook/core-common/dist/cjs/presets.js:274:28
    at async Object.webpack (/home/runner/work/documentation/documentation/submodules/volto/node_modules/@storybook/builder-webpack4/dist/cjs/presets/custom-webpack-preset.js:36:28)
    at async Object.build (/home/runner/work/documentation/documentation/submodules/volto/node_modules/@storybook/builder-webpack4/dist/cjs/index.js:178:16)
    at async Promise.all (index 1)
    at async buildStaticStandalone (/home/runner/work/documentation/documentation/submodules/volto/node_modules/@storybook/core-server/dist/cjs/build-static.js:141:28)
    at async buildStatic (/home/runner/work/documentation/documentation/submodules/volto/node_modules/@storybook/core-server/dist/cjs/build-static.js:161:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/***/cli/run for documentation about this command.
Error: Process completed with exit code 1.

Fixed by https://github.com/plone/volto/pull/3689. We have plone/documentation building successfully again. Thank you!


Remove all use of model.NewConfig in test in favor of the mock

What does this PR do?
Remove all use of model.NewConfig in test in favor of the mock. This prevent tests creating multiple conflicting configurations.
This commit also add a linter to prevent more usage to be added.
Describe how to test/QA your changes
Running the CI is enough since we're only changing the tests.

/merge


Add Read me on Atmosphere

Very interesting that package. You can update the information in the Atmosphere?
It would be nice if you can add more examples of using on description, perhaps to show the difference between this package and use regular session, etc.
Thank you!

Hi Jadson, I had not realized that the readme did not appear in atmosphere, thanks for telling me

Jadson, you know why my readme is not in atmosphere?, I already try uploading a new version of the package and using the following command
meteor admin change-homepage cottz:iron-query 'https://github.com/Goluis/cottz-iron-query.git'

No, unfortunately I don't have packages on Atmosphere, only collaborate with an another but there was already published, and see the same "read me" of repository. Sorry.
I'm still learning Meteor advanced mode, but soon I will launch some packages to help others.

@Goluis new release of Meteor has new options to packages: https://www.meteor.com/blog/2015/01/20/meteor-show

My readme magically appeared with the new version of meteor


Check hash in ShopTransactionStatusServerRequest

The transaction status notification message includes a hash that can be used to check if the received data is genuine or has been altered en-route. This hash is not checked at this time.
Details of how the has works can be found here:
https://github.com/fjbender/simple-php-integration#waiting-for-payment-confirmation

Where the check needs to be, I'm not sure. A hunch says it should be in the server request message, with a method to confirm (isValid()). Raising exceptions like some gateways do can make responding and logging the received details (valid or not) a lot more difficult.

Hash check implemented and documented.
You can only sent the TSOK response to the transaction status request if the hash verifies. This makes the portalKey mandatory when accepting a notification (see docs).

Having said that, on the test instance we get the same hash sent to us every time, regardless of the contents of the status message. That does not actually make the status message tamper-proof at all - it is more like including a password.


Fixed #503 to use most modern version of bridge api and cached pages

Awesome I can ask myself to do a review! :rofl:
Regarding the empty lines: PHP is indeed not sensitive to that. The rules however are to improve code readability rather than code validity.
Merged, thanks for the fix!

:man_facepalming: Turns out I should have checked more thoroughly. Sorry, I'll push a small fix in a minute.
const DOMAIN is not valid. It must be const URI, see here.

I'll change the DOMAIN back to URI, now I know the correct way to have const built from other const instances ...
It will be a small change with no impact on code.


Update jwt-decoder extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for your contribution @zhhanging 🔥 Do you mind adding a CHANGELOG entry too?
@gdsmith can you approve this?

I have Added a CHANGELOG.md file as suggested.

@gdsmith are you around?


Not fetching correct package

I tried the following (using version 0.4.27):
PS C:\WINDOWS\system32> pwr sh jdk:7
pwr: fetching jdk:17.0.4
pwr: fetched 1 package (jdk:17.0.4)
pwr: using jdk:17.0.4

Notice it fetched version 17 when I requested 7. Is this correct? I would expect that if a JDK 7 package doesn't exist then I would get an error (maybe with a suggestion or question about using JDK 17). Maybe it's just finding the latest version that contains a 7?

Confirmed this is a bug.
PS > pwr which jdk:7
jdk:17.0.4


Aggregate PR

Aggregate of the following PRs:
https://github.com/wildfly/wildfly-core/pull/5090
https://github.com/wildfly/wildfly-core/pull/5160
https://github.com/wildfly/wildfly-core/pull/5048

Core -> Full Integration Build 11586 outcome was UNKNOWN using a merge of 19b61febfc7791e5784301592cd1d567a4302b60
Summary: Canceled Build time: 00:01:02

Core -> WildFly Preview Integration Build 11754 outcome was UNKNOWN using a merge of 19b61febfc7791e5784301592cd1d567a4302b60
Summary: Canceled Build time: 00:01:04

Core -> Full Integration Build 11755 outcome was UNKNOWN using a merge of 19b61febfc7791e5784301592cd1d567a4302b60
Summary: Canceled Build time: 00:01:04

Core -> Full Integration Build 11587 outcome was UNKNOWN using a merge of 19b61febfc7791e5784301592cd1d567a4302b60
Summary: Canceled Build time: 00:01:02

Closing this aggregate PR since each of the individual PRs have been now been merged.


Replace icon to hangout logo

There may be some trademark issues associated with this.

I'm also pretty convinced we can't just use Google's logo without their consent.
But what we can do is make a logo that looks more like the logo of a chat app, . There's already some work going on but it seems it has stalled.


Add (single) verbosity flag

Add verbose flag and hide error messages behind it. Add additional output warning, if there were I/O errors while walking the tree.
Closes #29

Very cool, thank you very much.
I think we should print a small message in non-verbose mode in case there were any errors. Something like
There were errors during the file system traversal which could lead to wrong results. Re-run with -v/--verbose to print all errors.

Oh, I just now saw the let tainted = … part. Why do you think it should only be tainted if there is a NoMetadataForPath error? CouldNotReadDir would also lead to wrong results, right?

Thank you!

Released in v0.6.0.

Thanks for pushing this through.

Oh, I just now saw the let tainted = … part. Why do you think it should only be tainted if there is a NoMetadataForPath error? CouldNotReadDir would also lead to wrong results, right?

That's how I interpreted your comment at https://github.com/sharkdp/diskus/issues/29#issuecomment-497611980, but you're right – CouldNotReadDir is also an I/O error.

Ah, I see how that could be interpreted in the wrong way. What I meant was: "But I would only show the "may be inaccurate" warning if there were any errors". It was a very trivial statement, sorry :smile:


How to mock bun?

Hi, is there any way to mock the Bun other than sqlmock, I don't want to write raw SQL queries for testing. I know I can print executed queries to stdout then copy&paste them to the Sqlmock but it's a bit painful.

I don't write mocks and thus don't have relevant experience, but you could try to create an additional layer that works with database and mock that layer instead of Bun database. That is all I know on the topic :)

I'm not experienced in testing. So what is your testing strategy? We're going to develop a relatively big project(web API). Before that, I'm experimenting with different frameworks and technics.

Usually I write tests against real database without mocking it. Something like https://github.com/go-bun/bun-realworld-app/blob/master/blog/blog_test.go, but it is not the cleanest example.

@hhuseyinpay it seems like you have more design issue.
I suggest you to create additional layer like Storage.
For each DB entity you will have separate storage service: e.g. UserStorage (for user table).
UserStorage and other storage services will provide public (exported) interface for communication with other packages. And ofc each interface will have private implementation inside storage package.
So now just use interface everywhere in you app outside storage package. In tests for the code which use your UserStorage interface, you just pass mock implementation. (Try moq package for generating mocks from interfaces).
For testing storage layer, I would suggest to use go-containers package which allows you to setup a real DB docker container before tests started. Check testify/suite package which provides before and after tests hooks logic.
So the flow is:

Setup and run DB docker container
Migrate you DB schema
Run test, which test some storage method
Truncate DB before next test to avoid side effects.

The benefit of using containers for DB layer tests is that you can setup the type and version of the DB which is used in your production.


update package describe --cli to look at command + resource json

With universe updates to change where the cli is defined, we now first
look for the cli definition in resource.cli, and if not found, look for
command.json in the package definition.

#603

LGTM.


Lint again

prepublish hook allows to build and test code before publishing in npm. There is no need to hold dist in git

I added build to prepublish earlier because it was missing.
On Jul 11, 2016 1:20 PM, "Bogdan Chadkin"<EMAIL_ADDRESS>wrote:

prepublish hook allows to build and test code before publishing in npm.
There is no need to hold dist in git
You can view, comment on, or merge this pull request online at:
https://github.com/Kflash/karma-rollup-plugin/pull/12
Commit Summary

Lint again

File Changes

M .eslintrc
https://github.com/Kflash/karma-rollup-plugin/pull/12/files#diff-0
(1)
M .gitignore
https://github.com/Kflash/karma-rollup-plugin/pull/12/files#diff-1
(1)
D dist/rollup-plugin-karma.js
https://github.com/Kflash/karma-rollup-plugin/pull/12/files#diff-2
(83)
M package.json
https://github.com/Kflash/karma-rollup-plugin/pull/12/files#diff-3
(2)
M src/index.js
https://github.com/Kflash/karma-rollup-plugin/pull/12/files#diff-4
(106)

Patch Links:

https://github.com/Kflash/karma-rollup-plugin/pull/12.patch
https://github.com/Kflash/karma-rollup-plugin/pull/12.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Kflash/karma-rollup-plugin/pull/12, or mute the
thread
https://github.com/notifications/unsubscribe/AEU1AhRN5Tl1FPiNGgepfyEwuj8-Cz9Nks5qUdK4gaJpZM4JJChj
.


App crashing when try edit Special actions in profile

Hello,
I have problem in DS4Windows (Windows 7 x64bit) when I try edit Special actions in profile. At the first time no problem, I can edit it. But on the second or third time is shows me error table (as on screenshot) .
When I click on Continue button, not happen and app not crash, but I still not can edit Special action.
And when I click click on End button, all DS4 app crashed.
Thank you in advance.

Here is the all the error code
DS4errorcode.txt

Here is the all the error code
DS4errorcode.txt
Ok maybe progress, this error code I have only when I try set Special action to check battery.


[BUG] Error copy jpg files inside .storage during processing image

Describe the bug
Error copying jpg files inside .storage during doubletake processing image.
ENOENT: no such file or directory, copyfile './.storage/matches/397fa834-e9b7-4941-9eb2-2ef5ee541b56.jpg' -> './.storage/latest/unknown.jpg'
Version of Double Take
<IP_ADDRESS>-SHA7
Expected behavior
success copy latest.jpg to unknown.jpg? i don't know.
** docker-compose.yml
`version: '3.7'
volumes:
double-take:
services:
double-take:
container_name: double-take
image: skrashevich/double-take:latest
restart: unless-stopped
volumes:
- /opt/doubletake/storage:/.storage
ports:
- 3000:3000
`
Hardware

amd64
Ubuntu
Browser (if applicable) [e.g. Chrome, Safari]
Docker image: e.g. skrashevich/double-take:latest

Additional context
Add any other context about the problem here.

doubletake_log.txt
log attached.

What i see is that the random_file_name.jpg doesn't even exist in /opt/doubletake/storage/matches,  in docker view /.storage, so nothing to be copied across directory.

https://github.com/skrashevich/double-take/issues/159#issuecomment-1826925872

i have taken a very close look on the logs for every process image.  The copy jpg issue only happens occasionally and so some images show up on Match UI and some were totally ignored.
I have .storage/latest, .storage/matches and .storage/train directory and mode is 755 (both inside/outside docker).  I have now changed to 777 and see how it goes.


[BUG] Unable to list public blobs (with no credentials)

https://azuremlexamples.blob.core.windows.net/datasets/iris.csv is public so I want to list blobs without passing in credential.
I tried the below
          BlobServiceClient blobServiceClient = new BlobServiceClientBuilder().endpoint("https://azuremlexamples.blob.core.windows.net").credential(new DefaultAzureCredentialBuilder().build()).buildClient();
          String containerName = "datasets";
          BlobContainerClient containerClient = blobServiceClient.getBlobContainerClient(containerName);
          for (BlobItem blobItem : containerClient.listBlobs()) {
              System.out.println("\t" + blobItem.getName());
          }

with
      <dependency>
  <groupId>com.azure</groupId>
  <artifactId>azure-core</artifactId>
  <version>1.0.0</version>
</dependency>
        <dependency>
            <groupId>com.azure</groupId>
            <artifactId>azure-storage-blob</artifactId>
            <version>12.0.0</version>
            <!--https://github.com/Azure/azure-sdk-for-java/issues/15215#issuecomment-735940668 need to upgrade -->
            <!--https://stackoverflow.com/questions/60589689/the-exception-java-lang-nosuchmethoderror-thrown-when-invoking-azure-storage-rel/60589738#60589738 mentions could be netty conflict -->
        </dependency>
        <dependency>
          <groupId>com.azure</groupId>
          <artifactId>azure-identity</artifactId>
          <version>1.0.3</version>
        </dependency>
        <dependency>
    <groupId>com.azure</groupId>
    <artifactId>azure-security-keyvault-secrets</artifactId>
    <version>4.1.0</version>
  </dependency>

I get
	at com.azure.identity.implementation.IdentityClient.<clinit>(IdentityClient.java:59)
	at com.azure.identity.implementation.IdentityClientBuilder.build(IdentityClientBuilder.java:50)
	at com.azure.identity.ManagedIdentityCredential.<init>(ManagedIdentityCredential.java:33)
	at com.azure.identity.DefaultAzureCredential.<init>(DefaultAzureCredential.java:37)
	at com.azure.identity.DefaultAzureCredentialBuilder.build(DefaultAzureCredentialBuilder.java:18)

If I try with different versions of dependencies in pom (including latest versions) I get:
java.lang.NoSuchMethodError: com.azure.core.http.policy.HttpLogOptions.getApplicationId()Ljava/lang/String;
	at com.azure.storage.blob.implementation.util.BuilderHelper.getUserAgentPolicy(BuilderHelper.java:165)
	at com.azure.storage.blob.implementation.util.BuilderHelper.buildPipeline(BuilderHelper.java:73)
	at com.azure.storage.blob.BlobServiceClientBuilder.buildAsyncClient(BlobServiceClientBuilder.java:107)
	at com.azure.storage.blob.BlobServiceClientBuilder.buildClient(BlobServiceClientBuilder.java:84)

OR
Caused by: java.lang.NoClassDefFoundError: com/azure/core/implementation/serializer/jackson/JacksonAdapter
	at com.azure.identity.implementation.IdentityClient.<clinit>(IdentityClient.java:60)
	at com.azure.identity.implementation.IdentityClientBuilder.build(IdentityClientBuilder.java:50)
	at com.azure.identity.ManagedIdentityCredential.<init>(ManagedIdentityCredential.java:33)
	at com.azure.identity.DefaultAzureCredential.<init>(DefaultAzureCredential.java:37)
	at com.azure.identity.DefaultAzureCredentialBuilder.build(DefaultAzureCredentialBuilder.java:18)

Is there any plan to provide a single 'working' bundle jar?
I also tried but hit issue in https://github.com/Azure/azure-sdk-for-java/issues/17970 / https://stackoverflow.com/questions/65135299/azure-java-sdk-for-blob-a-request-was-made-to-load-the-default-httpclient-prov/65138749#65138749:
          BlobServiceClient blobServiceClient = new BlobServiceClientBuilder().endpoint("https://azuremlexamples.blob.core.windows.net").buildClient();
          String containerName = "datasets";
          BlobContainerClient containerClient = blobServiceClient.getBlobContainerClient(containerName);
          for (BlobItem blobItem : containerClient.listBlobs()) {
              System.out.println("\t" + blobItem.getName());
          }

Hi, @tooptoop4. Thank you for your question. Correct me if I'm wrong, but it seems like your underlying issue is not with listing public blobs so much as dependency management. NoSuchMethodError and NoClassDefFoundError are both indications of dependency mismatches.
As to your question about a single working bundle jar, we have shipped this bom, which I think should answer your question. I'm not sure why it hasn't released since the summer, but I'm looking into that now. In any case, that bom should still work.
The other alternative I would recommend trying if the bom does not suit you is to upgrade your identity, core, keyvault, and blob dependencies to latest as I am quite confident there will be no conflicts if everything is on the most recent version. If there's a particular reason why you feel you can't upgrade to those versions yet, I'd still like to at least run some tests with those versions to see if it resolves the exceptions you're seeing and then we can figure out how to successfully target versions that work for you

Also, the first stack trace you shared seems to be cut off if you could please share the entire thing?

when using the bom:
Caused by: java.lang.IllegalStateException: Cannot find any HttpClient provider on the classpath - unable to create a default HttpClient instance
	at com.azure.core.implementation.http.HttpClientProviders.createInstance(HttpClientProviders.java:35)
	at com.azure.core.http.HttpClient.createDefault(HttpClient.java:27)
	at com.azure.core.http.HttpPipelineBuilder.build(HttpPipelineBuilder.java:60)
	at com.azure.storage.blob.implementation.util.BuilderHelper.buildPipeline(BuilderHelper.java:108)
	at com.azure.storage.blob.BlobServiceClientBuilder.buildAsyncClient(BlobServiceClientBuilder.java:105)
	at com.azure.storage.blob.BlobServiceClientBuilder.buildClient(BlobServiceClientBuilder.java:82)

using either of these code gets same error:
          BlobServiceClient blobServiceClient = new BlobServiceClientBuilder().endpoint("https://azuremlexamples.blob.core.windows.net").buildClient();
          String containerName = "datasets";
          BlobContainerClient containerClient = blobServiceClient.getBlobContainerClient(containerName);
          for (BlobItem blobItem : containerClient.listBlobs()) {
              System.out.println("\t" + blobItem.getName());
          }

          BlobServiceClient blobServiceClient = new BlobServiceClientBuilder().endpoint("https://azuremlexamples.blob.core.windows.net").credential(new DefaultAzureCredentialBuilder().build()).buildClient();
          String containerName = "datasets";
          BlobContainerClient containerClient = blobServiceClient.getBlobContainerClient(containerName);
          for (BlobItem blobItem : containerClient.listBlobs()) {
              System.out.println("\t" + blobItem.getName());
          }

imports are:
import com.azure.storage.blob.*;
import com.azure.storage.blob.models.*;
import com.azure.core.http.HttpClient;
import com.azure.core.http.HttpClientProvider;
import com.azure.identity.DefaultAzureCredentialBuilder;
import java.io.*;
import java.net.*;

note that I am running this from personal PC, not on an azure vm.

Thanks, @tooptoop4 for the information. Can you also try specifying the latest versions of the each of the libraries?
blob: 12.9.0
core: 1.11.0
security-keyvault-secrets: 4.3.0-beta.2
identity: 1.2.0
And can you please share the rest of this stack trace from your original post?
at com.azure.identity.implementation.IdentityClient.<clinit>(IdentityClient.java:59)
	at com.azure.identity.implementation.IdentityClientBuilder.build(IdentityClientBuilder.java:50)
	at com.azure.identity.ManagedIdentityCredential.<init>(ManagedIdentityCredential.java:33)
	at com.azure.identity.DefaultAzureCredential.<init>(DefaultAzureCredential.java:37)
	at com.azure.identity.DefaultAzureCredentialBuilder.build(DefaultAzureCredentialBuilder.java:18)

@rickle-msft
original post:
java.lang.NoClassDefFoundError: com/azure/core/util/serializer/JacksonAdapter
	at com.azure.identity.implementation.IdentityClient.<clinit>(IdentityClient.java:59)
	at com.azure.identity.implementation.IdentityClientBuilder.build(IdentityClientBuilder.java:50)
	at com.azure.identity.ManagedIdentityCredential.<init>(ManagedIdentityCredential.java:33)
	at com.azure.identity.DefaultAzureCredential.<init>(DefaultAzureCredential.java:37)
	at com.azure.identity.DefaultAzureCredentialBuilder.build(DefaultAzureCredentialBuilder.java:18)
	at org.ebyhr.presto.flex.FlexRecordCursor.<init>(FlexRecordCursor.java:528)
	at org.ebyhr.presto.flex.FlexRecordSet.cursor(FlexRecordSet.java:55)
	at io.prestosql.spi.connector.RecordPageSource.<init>(RecordPageSource.java:37)
	at io.prestosql.split.RecordPageSourceProvider.createPageSource(RecordPageSourceProvider.java:50)
	at io.prestosql.spi.connector.ConnectorPageSourceProvider.createPageSource(ConnectorPageSourceProvider.java:68)
	at io.prestosql.split.PageSourceManager.createPageSource(PageSourceManager.java:64)
	at io.prestosql.operator.TableScanOperator.getOutput(TableScanOperator.java:298)
	at io.prestosql.operator.Driver.processInternal(Driver.java:379)
	at io.prestosql.operator.Driver.lambda$processFor$8(Driver.java:283)
	at io.prestosql.operator.Driver.tryWithLock(Driver.java:675)
	at io.prestosql.operator.Driver.processFor(Driver.java:276)
	at io.prestosql.execution.SqlTaskExecution$DriverSplitRunner.processFor(SqlTaskExecution.java:1076)
	at io.prestosql.execution.executor.PrioritizedSplitRunner.process(PrioritizedSplitRunner.java:163)
	at io.prestosql.execution.executor.TaskExecutor$TaskRunner.run(TaskExecutor.java:484)
	at io.prestosql.$gen.Presto_344_41_g3758d9f_dirty____20201204_101810_2.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

Stack trace using
blob: 12.9.0
core: 1.11.0
security-keyvault-secrets: 4.3.0-beta.2
identity: 1.2.0
java.lang.IllegalStateException: A request was made to load the default HttpClient provider but one could not be found on the classpath. If you are using a dependency manager, consider including a dependency on azure-core-http-netty or azure-core-http-okhttp. Depending on your existing dependencies, you have the choice of Netty or OkHttp implementations. Additionally, refer to https://aka.ms/azsdk/java/docs/custom-httpclient to learn about writing your own implementation.
	at com.azure.core.implementation.http.HttpClientProviders.createInstance(HttpClientProviders.java:37)
	at com.azure.core.http.HttpClient.createDefault(HttpClient.java:39)
	at com.azure.core.http.HttpPipelineBuilder.build(HttpPipelineBuilder.java:60)
	at com.azure.storage.blob.implementation.util.BuilderHelper.buildPipeline(BuilderHelper.java:110)
	at com.azure.storage.blob.BlobServiceClientBuilder.buildAsyncClient(BlobServiceClientBuilder.java:107)
	at com.azure.storage.blob.BlobServiceClientBuilder.buildClient(BlobServiceClientBuilder.java:84)
	at org.ebyhr.presto.flex.FlexRecordCursor.<init>(FlexRecordCursor.java:529)
	at org.ebyhr.presto.flex.FlexRecordSet.cursor(FlexRecordSet.java:55)
	at io.prestosql.spi.connector.RecordPageSource.<init>(RecordPageSource.java:37)
	at io.prestosql.split.RecordPageSourceProvider.createPageSource(RecordPageSourceProvider.java:50)
	at io.prestosql.spi.connector.ConnectorPageSourceProvider.createPageSource(ConnectorPageSourceProvider.java:68)
	at io.prestosql.split.PageSourceManager.createPageSource(PageSourceManager.java:64)
	at io.prestosql.operator.TableScanOperator.getOutput(TableScanOperator.java:298)
	at io.prestosql.operator.Driver.processInternal(Driver.java:379)
	at io.prestosql.operator.Driver.lambda$processFor$8(Driver.java:283)
	at io.prestosql.operator.Driver.tryWithLock(Driver.java:675)
	at io.prestosql.operator.Driver.processFor(Driver.java:276)
	at io.prestosql.execution.SqlTaskExecution$DriverSplitRunner.processFor(SqlTaskExecution.java:1076)
	at io.prestosql.execution.executor.PrioritizedSplitRunner.process(PrioritizedSplitRunner.java:163)
	at io.prestosql.execution.executor.TaskExecutor$TaskRunner.run(TaskExecutor.java:484)
	at io.prestosql.$gen.Presto_344_41_g3758d9f_dirty____20201204_211715_2.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

https://stackoverflow.com/a/65179461/8874837 works so must be an issue in my app's classloader/conflict versions

@tooptoop4 Sorry for the delay and glad to hear it's working! If your question has been resolved, then please close the issue. Otherwise please let me know if there are other areas in which you need support

so adding Reflection.initialize(HttpClientProviders.class); gets past this but then I hit infinite loop when listing blobs (seems https://github.com/Azure/azure-sdk-for-java/issues/9465 is known but closed)
the infinite loop errors at:
java.lang.StackOverflowError
	at reactor.core.publisher.MonoFlatMapMany$FlatMapManyInner.onNext(MonoFlatMapMany.java:242)
	at reactor.core.publisher.FluxConcatArray$ConcatArraySubscriber.onNext(FluxConcatArray.java:176)
	at reactor.core.publisher.MonoFlatMapMany$FlatMapManyInner.onNext(MonoFlatMapMany.java:242)
	at reactor.core.publisher.FluxConcatArray$ConcatArraySubscriber.onNext(FluxConcatArray.java:176)
	at reactor.core.publisher.MonoFlatMapMany$FlatMapManyInner.onNext(MonoFlatMapMany.java:242)
	at reactor.core.publisher.FluxConcatArray$ConcatArraySubscriber.onNext(FluxConcatArray.java:176)

Just acknowledging I've seen this. Another user suggested a starting point on the thread you referenced, so I'll wait for that exploration to play out before following up here.

@tooptoop4 Sorry for the delay. does the solution in the issue you referenced work for you? Or do you need further support?

works


[meta] require approvals for PRs

https://github.com/containers/bootc/pull/263 is now green, and I can actually merge it even without an approval. Can we enable require approvals for this repository?

@ondrejbudai I've just enabled it


Just too slow...

It takes about 150 seconds to finish an image. I know this isn't really an issue, though. I think that it should try to detect the most important part of an image first. Like, the part that has the most colors, or is in the center, or is brighter than everything else.

Try searching for pixel art versions of your word, or pick images with less complexity/color variety.

Hello, @Wyatt-Stanke.
The number of line draw commands the skribbl.io servers can process is a limiting factor that's out of our control. We can make efficiency improvements that reduce the number of line draw commands needed for a given image. #12 discusses more specifics.
The easiest way to ensure an image draws fast is by deliberately selecting a simple image. You can find this type of image by including the term "clipart" in your Google Images search expression. The worst type of image is a photograph.


Rename LightGraphs to Graphs

Due to the "LightGraphs.jl -> Graphs.jl" rename, SankeyPlots stopped working with graphs built on top of new Graphs.jl-based types. For the detail of this rename, please check out following:
LightGraphs.jl Transition

https://discourse.julialang.org/t/lightgraphs-jl-transition/69526/11

With this rename, old "Graphs.jl" has retired as "OldGraphs.jl" and newer version of "LightGraphs.jl" is now "Graphs.jl". This caused modules using LightGraphs to fail with Graphs-based types, as method dispatch now fails.
Simply changing "using LightGraphs" to "using Graphs" should do the migration.

In my fork I solved the recent problems (https://github.com/davide-f/SankeyPlots.jl/).
I added pull requests here as well, yet my fork is working now.
I look forward for merging the pull requests; co-ownership possible?

#15 solves this issue


¿Create links nofollow?

I can create nofollow links from github pages. Are there any options configured within the template for this?
I found this: https://github.com/d-ogarkov/jekyll-extlinks  but I don't know if there is something similar in the mmistakes template
...
Others
I want to insert several things to the template and I have multiple doubts; but little by little.
I don't know if this is the best place to ask other questions, greetings; And thank you very much for everything. Or if there is a forum or something, where to ask.

For Jekyll questions ask in their forum. https://talk.jekyllrb.com/
I've never used that plugin, but that's likely the sort of solution you'll need. There is nothing in the template to alter links to add rel="nofollow".

As it isn't a whitelisted plugin by GitHub Pages I'm not interested in adding it as a dependency of the theme as it would break compatibility.
But there is nothing stopping you from installing it on your site. Looks fairly straight forward to do so.


Git Extension's onDidChange does not report branch changes

Does this issue occur when all (other) extensions are disabled?: Yes

VS Code Version: 1.81.0-insiders
OS Version: Linux 6.1.41-1-MANJARO

Steps to Reproduce:

Write an extension that uses git api:
extensions.getExtension('vscode.git').exports.getAPI(1).repositories[0].state.onDidChange(() => console.log('repo change!'))
works great for most changes to the current repo such as stashing or committing. The event contains no data as discussed in #142313 but this is as designed
Now add a branch via command line as git branch new-branch
onDidChange does not fire!

It kind of makes sense as VSCode's Git extension does not include proper branch management by itself, but for depending extensions, this is quite annoying. Here's the bug report for my extension: https://github.com/phil294/git-log--graph/issues/27 (forget about the "stashing"-part, this is unrelated and actually works)

@phil294, thank you very much for reporting this issue. The onDidChange event is meant to fire every time after a git command is being executed using the VS Code git UX. VS Code will also execute git status in response to file system change events which VS Code is focused so that would also result in the onDidChange event being fired.
If you create a sample extension with the code above and see the console message if:

you use the "Git: Create Branch..." command to create a new branch
run git checkout -b <BRANCHNAME> in the integrated terminal

I can confirm that running git branch <BRANCHNAME> in the integrated terminal will not result in the event being fired so I am suspecting that the file system event occurs in a folder/file that we are not currently watching. I will investigate further and will update the issue with my findings.

I have looked into this and I can confirm that running git branch <NAME> is creating a new file in the refs/heads folder which we are not currently watching. Watching the refs/heads folder is an option but that could have performance implications due to the large number of files that may exist in that folder so I would rather wait for this proposed API to land. This will enable the vscode.git extension to refresh the "Source Control" view when a git command is executed in the integrated terminal.


Router not working!

I have this in /lib/router.js
Router.configure({
  layoutTemplate: 'layout',
});

Router.route('/', function () {
    this.layout('layoutHome');
    this.render('home');
});

And I have this in /client/views/layout.html
<template name="layout">
    {{> header }}

      {{> yield }}

</template>

<template name="layoutHome">

        {{> header }}
        {{> search }}

        {{> yield }}

</template>

And this in /client/views/home.html
<template name="home">
    hello world come on!
</template>

When I go to the home page /, it throws this error on the client console:
Exception from Tracker recompute function: Error: Couldn't find a template named "/" or "". Are you sure you defined it?

Why is it looking for a template called '/' when I clearly specified the template to render?
Is it possible for a package to cause it to not work properly? Here's my meteor list
accounts-password                  1.0.2  Password support for accounts
autopublish                        1.0.0  Publish the entire database to all ...
insecure                           1.0.0  Allow all database writes by default
iron:router                        0.9.4  Routing specifically designed for M...
less                               1.0.9  The dynamic stylesheet language
meteor-platform                    1.1.1  Include a standard set of Meteor pa...
mizzao:bootstrap-3                 3.2.0_1  HTML, CSS, and JS framework for d...
yasinuslu:accounts-ui-bootstrap-3  0.3.10  Bootstrap styled version of login ...

In order to make it work, I have to write the routing using the legacy code:
Router.configure({
  layoutTemplate: 'layout',
});

Router.map(function () {
    this.route('home', {
        path: '/',
        layoutTemplate: 'layoutHome'
    });
});

I have the same issue and I am on iron router version 1.0.7. I have 4 templates going into layoutTemplate. On some routes Meteor renders the correct layout but on some it just renders a layout witch is not defined for this route nor as default per Router.configure. I am using yogiben/meteor-starter.
Thank you.

Having the same issue with version 1.0.7 in mobile Chrome. It loads "/" page but white blank pages for the rest of my routes. I tried mobile Firefox and it works just fine.
I think iron:router have incompatibility issues with other dependencies. i don't know..


Simple Markdown fails with Unexpected view type nested under text node

Hello, I like the styling of this library as opposed to the alternatives however I've tried all of them and they seem to all have an error parsing basic markdown due to how react native Android renders components. The error seems to occur when you try nesting components in your markdown, for example something like this (view it raw since github parses it)

[Leetcode Problem] (https://github.com/CyC2018/InnterviewNotes/blob/master/notes/Leetcode Solutions.md)
A general classification of the topics, and a summary of the problem-solving ideas for each type of question.

or

[I. Basic Concepts] (#1 - Basic Concept)

URL

I get the following error
Unexpected view type nested under text node: class com.facebook.react.uimanager.LayoutShadowNode
a simple list with a nested list of links fails... Would anyone have a simple and elegant solution to this problem?


tools/cross.sh missing?

When I run configure, I encounter the following error.
$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking for /home/wnowak1/Downloads/qnixx_src/src/cross... no
configure: error: "Please run 'bash tools/cross.sh'"

Where can I obtain the tools from?
Thanks.

Hi, you can run bash tools/cross.sh

Sorry for the late response.

https://github.com/Qnixx/src/blob/main/tools/cross.sh

It looks like at the time this issue was opened, there was no tools/cross.sh. It does exist now, so if anyone has this issue git pull and ./configure again.


CNL stability and efficiency

With extended testing it's been discovered that the CNL can send very late responses at a maximum of 20000ms.
Currently there is a general read timeout at 10 seconds and this can miss these occasional late responses. With a rework of pump read/write to cover this, it makes a number of the message clearing safeguards redundant and will decrease the average polling time from around 12 sec to around 8 sec.
For situations where the uploader is constantly in-out of range with the pump and comms are being broken while in progress the risk of producing a E86/E81 CNL error needing a replug increases. Catching these late messages and lost connections stops this happening.
During history reading where there can be 100's of packets being transferred the timeout period needs dynamic adjustment so as to not timeout too early or late. With the in-out range situation the first few packets may be read and the next 60 or 70 etc missed where we would usually have timed out but actually the pump still keeps sending. We may even miss the first 100 packets and get the last 5. We need to allow for this or we may end up with a NAK response due to the pump being in the wrong state for further request commands. If we try to close in this state the CNL will E86.

Closed - completed and available in 0.7.0 release


Ionic 4- Use Cordova-plugin-mqtt

I'm trying to make an app to allow my phone  to subscribe to MQTT topics. So I found your plugin and when I try to use it with Ionic 4 looks like something goes wrong.
I've installed your plugin with this command :  ionic cordova plugin add cordova-plugin-mqtt
When I try to use it :
import {CordovaMqTTPlugin} from 'cordova-plugin-mqtt';
I've got this issue : "Cannot find module 'cordova-plugin-mqtt' "
Any suggestions ?
Thank you

+1 ,i have same issue, need a solutiion urgent!! :) :)