Importing renewed certificate makes certificate duplicate

Current implementation
Importing a renewed certificate makes the certificate duplicate in the list

Steps to reproduce

Import a certificate on 2 devices
Renew a certificate on one device
Import the renewed cert on second device

Suggested enhancement
The renewed certificate should replace the old certificate & certificate should also get renewed on the second device

Thanks for your enhancement request @gleichda. We have created an internal ticket for it and will raise this topic internally.
Internal Tracking ID: EXPOSUREAPP-13457
Issue was moved to cwa-wishlist repository and opening comment has been adjusted accordingly. Feel free to update it if you think that anything is missing.

Corona-Warn-App Open Source Team

I overlooked the scenario where a user may have the same certificates stored in both Corona-Warn-App and CovPass. If a user has two devices, and certificates are stored in each app on each device, that would be a total of 4 times storage of the same certificate.  That would exceed the allowance of 3 reissues per certificate, so therefore some manual exchange between the apps would be necessary.

@dsarkar

Manual exchange can be done with the "export all" functionality.

That is correct, however normally there would only be one certificate to export / import at a time from and into CWA. The point of this item is to delete the older certificate automatically. The way it is at the moment, if you import an renewed certificate you have to delete the older certificate by hand if you want to clean up. You could just leave the older certificate where it is though. It will ultimately be displayed with "Certificate Expired" status. It just means that you would have two certificates with identical details except the UCI and the technical expiration date (and therefore status) would be different.
The question is whether the clean-up to remove the older certificate should be automated or not.

@MikeMcC399 yes, I agree with your comment, and indeed, the central question is if deletion of the older certificate should be automated. I guess this is problematic, because it will be "replaced" by a different mechanism than the currently defined one. Anyway, the idea per se is interesting.


Complete French translation file

Hi,
The translation in French for Authentic Theme is over !
You can insert it to your next version.
Glad to improve your GREAT JOB !
fr.UTF-8.zip

Merci beaucoup! :sweat_smile:  I have added it locally and will push to the repo a bit later.


Bad spanish translation

Hi! Please change the spanish translation of "please, support me" or " please, support us" since the one that you are using now "por favor, me apoyen!" sounds like you are desperately asking for someone to be behind you (if you know what I mean) and it is ungrammatical.

Thanks for post.
What should I say? If you have any ideas , pls give me them!

Hi! You should say something like "¡Por favor, colabora con nosotros!" if
you are a team since "nosotros" means "us" but if you are on your own or
you do not want to use "us" you can just say "¡Por favor, colabora!". Good
Luck!
2015-01-15 11:51 GMT-02:00 Tetsuwo OISHI<EMAIL_ADDRESS>
Thanks for post.
What should I say? If you have any ideas , pls give me them!
—
Reply to this email directly or view it on GitHub
https://github.com/tetsuwo/website-blocker-chrome.ext/issues/61#issuecomment-70087769
.


Inconsistent example code and compiled result images in Table Function documentation

Description
There is an inconsistency between the example code and the compiled result images for Table Cell in the Table Function documentation.
Current situation
The compiled result of the example code is as follows:
#table(
  columns: 3,
  table.header(
    [Substance],
    [Subcritical °C],
    [Supercritical °C],
  ),
  [Hydrochloric Acid],
  [12.0], [92.1],
  [Sodium Myreth Sulfate],
  [16.6], [104],
  [Potassium Hydroxide],
  table.cell(colspan: 2)[24.7],
)

However, the image provided in the documentation is as follows:

Desired situation
It is believed that not omitting the code related to table styling can prevent confusion.
https://github.com/typst/typst/blob/5011510270c2c23f0ab019af486b26db0d62261b/crates/typst/src/model/table.rs#L694-L719
#set page(width: auto)
#show table.cell.where(y: 0): strong
#set table(
  stroke: (x, y) => if y == 0 {
    (bottom: 0.7pt + black)
  },
  align: (x, y) =>
    if x > 0 { center }
    else { left }
)
#table(
  columns: 3,
  table.header(
    [Substance],
    [Subcritical °C],
    [Supercritical °C],
  ),
  [Hydrochloric Acid],
  [12.0], [92.1],
  [Sodium Myreth Sulfate],
  [16.6], [104],
  [Potassium Hydroxide],
  table.cell(colspan: 2)[24.7],
)

Reproduction URL
No response
Operating system
Web app
Typst version

[X] I am using the latest version of Typst

I remember that I saw somewhere suggestion to add a button for expanding hidden parts, but I couldn't find it


Import the Hackage package ecosystem

Manually adding each and every one of the many packages that Hackage hosts is a gargantuan task.
With the hackage-db library, we can read out the index files:
Prelude Distribution.Hackage.DB> db <-readHackage' "D:\\Users\\blauwers\\Downloads\\00-index.tar"

You can get the index files here: http://hackage.haskell.org/api
I could not find how the JSON API works for Hackage, which is a shame, because that might be a little easier to work with / extend.

Woops, made a typo on the issue number :|


UI changes to match mockup

This issue ideally resolves #105, except for one part: what is written in #109.
What's New:

Colour adjustments
Emails are now hyperlinked so clicking on the image will redirect to the email application, the current thumbnail is a placeholder image
Tags with extra long characters are now wrapped as above.
Formatting on DeadlineList is slightly different and can handle many deadlines so that it doesn't overrun.
ProjectStatus is now a "traffic-light-colored" indicator.
UI class diagrams are updated, resolves #115.

Codecov Report
Base: 65.32% // Head: 64.49% // Decreases project coverage by -0.82% :warning:

Coverage data is based on head (3a4222f) compared to base (23f65f2).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #121      +/-   ##
============================================
- Coverage     65.32%   64.49%   -0.83%
  Complexity      484      484
============================================
  Files            91       91
  Lines          1638     1659      +21
  Branches        181      183       +2
============================================
  Hits           1070     1070
- Misses          516      537      +21
  Partials         52       52

Impacted Files
Coverage Δ

src/main/java/jeryl/fyp/ui/MainWindow.java
0.00% <ø> (ø)

src/main/java/jeryl/fyp/ui/StudentCard.java
0.00% <0.00%> (ø)

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

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


MCM binding PMID:12604790

1 normal MCM complex binding
2 abolished MCM complex binding
have just TG'd GO:1904931

normal protein complex binding FYPO:0005232
normal MCM complex binding FYPO:0005233
abolished MCM complex binding FYPO:0005234

edit file: 245cc5e9bac91981cfa01a2e702333db2eae4f12
release: fac9f9f87d3b8884f99eb5614ae1338d20e8f50b


Swift 3

Hi,
I have just updated my project to swift 3. I have the following Podfile config for Locksmith:
pod "Locksmith", :git => 'https://github.com/matthewpalmer/Locksmith.git', :branch => 'swift-3.0'
When I tried to open my project, Xcode (8) asked me to convert the project syntax to Swift 3. I did. Now I'm getting the following error on Locksmith:
public extension CreateableSecureStorable where Self : GenericPasswordSecureStorable {
   func createInSecureStore() throws {
        try performSecureStorageAction(performCreateRequestClosure, secureStoragePropertyDictionary: asCreateableSecureStoragePropertyDictionary)
    }
    func updateInSecureStore() throws {
        try self.updateInSecureStore(query: self.asCreateableSecureStoragePropertyDictionary)
    }
}

(line 547 of Locksmith.swift if that helps)
Xcode complains about self.updateInSecureStore(), saying 'Argument passed to call that takes no arguments'. The same error also occurred on
public extension CreateableSecureStorable where Self : InternetPasswordSecureStorable {
    func createInSecureStore() throws {
        try performSecureStorageAction(performCreateRequestClosure, secureStoragePropertyDictionary: asCreateableSecureStoragePropertyDictionary)
    }
    func updateInSecureStore() throws {
        try self.updateInSecureStore(query: self.asCreateableSecureStoragePropertyDictionary)
    }
}

(line 572 of Locksmith.swift if that helps)
Have I done something wrong on my Podfile branch config?
Thanks in advance for the help & the awesome library!

There's a release version of Locksmith (3.0.0)—try it out and reopen if the issue persists 👍

Hi,
THanks for the prompt response! I have tried master (Locksmith 3.0.0), but the issue still persists. I would have tried to fix it myself, but I'm not familiar with Swift 3 syntax. I can see the following definition - so I dont know why xcode is complaining about it:

extension CreateableSecureStorable {
    func updateInSecureStore(_ query: [String: Any]) throws {
        var attributesToUpdate = query
        attributesToUpdate[String(kSecClass)] = nil

        let status = SecItemUpdate(query as CFDictionary, attributesToUpdate as CFDictionary)

        if let error = LocksmithError(fromStatusCode: Int(status)) {
            if error == .notFound || error == .notAvailable {
                try self.createInSecureStore()
            } else {
                throw error
            }
        } else {
            if status != errSecSuccess {
                throw LocksmithError.undefined
            }
        }
    }
}

Would you be able to create a sample project replicating this issue? Thanks!

Actually. I played around with the compile error, and figured out what was wrong. Then I went to GitHub to look at the latest code, and it seems that your code was doing the same thing that I did ! So... it seems that Xcode 8 has broken the code while trying to fix my project into swift 3 syntax.
Basically it puts underscore as external parameter on that function. Your original code did not specify external parameter name. Don't know why Xcode thinks that it should be fixed that way !
Best regards
Alex
Get Outlook for iOS
On Sat, Sep 17, 2016 at 6:17 PM +1000, "Matthew Palmer"<EMAIL_ADDRESS>wrote:
Would you be able to create a sample project replicating this issue? Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Same issue for me - do we know of a fix?

Hi Nick,
For me it is broken because Xcode is trying to be smart by fixing the function parameter.Just remove the external parameter name, and you should be ready to rock and roll again. I know it is a little hassle - as you probably would need to update the file every time you do pod install, but it is a short term fix :). Hope that helps !
Best regards
Alex
Get Outlook for iOS
On Tue, Sep 20, 2016 at 2:43 AM +1000, "Nick Wood"<EMAIL_ADDRESS>wrote:
Same issue for me - do we know of a fix?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, i was just wondering if there's a fix for this?
I am using the latest 3.0.0 Master pod release and XCode 8 is still determined that it needs to be converted to Swift 3 (or 2.3). On allowing this to happen i get 50 build errors.
I tried forcing to use the Swift 3 older branch, which worked, until build time where the Linker failed saying it was build with Swift 2.0!

I fixed mine by setting 'Use Legacy Swift Language Version' to No on the Pods project and doing a clean of the build folder and the project. Not sure if all those steps were necessary. But until it breaks again...why poke the bear?

Thanks GhostBob, that worked a treat.

If you ever converted codes of Locksmith to Swift 3, change back to original codes.
In Locksmith.swift, change
extension CreateableSecureStorable {
    func updateInSecureStore(_ query: [String: Any]) throws {

to
extension CreateableSecureStorable {
    func updateInSecureStore(query: [String: Any]) throws {


release helix_runtime as a gem to rubygems?

I know this is still an early project, but for testing things out, it would be super helpful, if we didn't need to muck around with installing helix_runtime from source in our own gems.
/cc @chancancode

@NullVoxPopuli see the examples in the duration_wip_windows branch. You should be able to set up a Gemfile and Cargo.toml to point at this repo on Github and it should all work. (On Windows there may be a couple of additional steps.)

See also https://github.com/hone/helix-console


[MINOR][DOCS] Fix site.SPARK_VERSION pattern in RDD Programming Guide

What changes were proposed in this pull request?
Fix site.SPARK_VERSION pattern in RDD Programming Guide. I found this when I was developing #47968
Why are the changes needed?
doc fix
Does this PR introduce any user-facing change?

no
How was this patch tested?

doc build
Was this patch authored or co-authored using generative AI tooling?

no

Merged to master, branch-3.5 and branch-3.4.


Virtualmin save_bkey.cgi script is called with wrong encoding type

This was detected in https://www.virtualmin.com/node/54740
Basically, it looks like when the form on edit_bkey.cgi uses the form-data encoding type, save_bkey.cgi is called with no input. The actual URL that's requested is :
<IP_ADDRESS> - root [21/Dec/2017:17:03:06 -0800] "GET /virtual-server/pro/save_bkey.cgi/key.txt?[object%20FormData] HTTP/1.1" 200 2683

Hi, Jamie, thanks for reporting!
It happens because of unconventional form's action link, which links to something about save_bkey.cgi/key.txt.
I have made a patch to capture this kind of links for all calls.
I have noticed that it takes literately forever to create a key and fails in most cases for me with an error:
Failed to create backup key : Key generation failed : Key generation timed out, possibly due to lack of entropy.

It happens in Gray Theme as well.
Not sure why it's happening. I think it should be checked. I ran it on my VM (CentOS 7).

Surely we need to return the progressive output to the user on this page, telling what's going on.
Jamie, make sure to let me know, in case you decide to make this part of the module progressive. For the future, I need always to know, when you add progressive output for certain pages. It has to be reflected on the theme as well to work correctly.

Yeah, key generation can be slow (perhaps infinitely) on VMs due to lack of entropy. This is unfortunately un-avoidable :-(

Sure, no problem.


can we expose BaM nvme driver without HBM cache capability to python world directly?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
No.
Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like save tensor myself with BaM on nvme directly. no need cache logic from BaM
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

No. HBM cache is not a cache. It is mainly an IO buffer. What you can do is reduce the cache size to a tiny amount, perhaps 128MB. The BaM will work. However, remember you might end up getting a lot of cache thrashing with a tiny cache.


Create examples and add them as a test harness

One idea for an example is here: https://github.com/pulumi/pulumi/issues/1538

Closed via #5


Read ELF SONAMEs directly from process memory when possible.

When this fails, it falls back to the previous behavior of trying to open the mapped file name directly.
Closes #79.

I'll update the ELF fixture to add an SONAME to test this.

Sorry my review is taking a bit but I'm doing some testing directly in Firefox and this seems to work only for external libraries, not our own ones, so I'm trying to figure out what's wrong (or if it's something specific to my box).

Not all binaries have the section header table present when loaded in memory. However the program headers will be there, so I added another path which is preferred and uses only the program headers and the dynamic section information. This seems to work with all shared objects loaded by firefox at runtime when I tested it. We might still want a fallback of trying to load directly from the file (if present) if reading from memory fails for some reason.

I'm not sure why the android test is failing...

This is probably ready to merge.


IpcCreateServer and multiple user sessions

It looks like the default behavior according to the help is that 1 server is created and "authenticated users will be allowed to access the server" is this correct? I'm running on a windows server OS and will have multiple users. I noticed that each time the IpcCreateServer is called a unique channel name is returned so I'm not sure. I need to have 1 server per user session

@michaelgorman you can provide your own channel/channel name instead.

Closing issue, they are indeed separate processes. My problem was a threading issue and race conditions


[C++] Support setting priority for the consumer

Motivation
#165 added support for dispatching message based on consumer priority. However, for C++ client, there is no way to set such priority on ConsumerConfiguration. This PR is to support setting priority for the consumer in C++ client.
Modifications

Add getPriorityLevel and setPriorityLevel methods in  ConsumerConfiguration
Modify the function signature of Commands::newSubscribe to add additional parameter priority_level with default value 0

Verifying this change

[ ] Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:

Add unit test for ConsumerConfiguration::getPriorityLevel and ConsumerConfiguration::setPriorityLevel in ConsumerConfigurationTest

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

There's something wrong with vcpkg build on Windows currently so that the  I'll push a fix soon.

Please rebase to master to fix the broken CI.

Please rebase to master to fix the broken CI.

PTAL @BewareMyPower, running the workflows require approval.

It seems that KeySharedConsumerTest  will produce non-deterministic results due to using rand() to generate the key. And for some seeds used by srand(), the test will fail.

And for some seeds used by srand(), the test will fail.

Yeah, it's a flaky test but now it doesn't fail frequently. You can comment /pulsarbot run-failure-checks  to rerun the tests.

And for some seeds used by srand(), the test will fail.

Yeah, it's a flaky test but now it doesn't fail frequently. You can comment /pulsarbot run-failure-checks to rerun the tests.

OK, got it. Thanks.

Add release/2.8.3 label to fix conflict when cherry-picking https://github.com/apache/pulsar/pull/13883 to branch-2.8.


update postBuild for verson 0.2.3

this part of binder got left out of the update

Thanks @ianhi :)
You’re awesome

oooh one other thing. It looks like binder current points to the stable branch. So none of the recent changes to examples are actually available on binder yet.

Huh
I always forget about this stable stuff, not used to use it yet.
Thanks for the reminder @ianhi. Fixed! :)


Release 0.2.1

Bump version to 0.2.0 manually in order to use cargo release patch for a semi-automatic release.
@lucab do you usually edit the commit message generated by cargo release?
Depends on #52.

Cool, thanks! Let me rebase this on top of #52 so I get a hang of the process.

I've created https://github.com/lucab/dkregistry-rs/pull/1 which modifies #52. After that's merged I'll rebase this on master and attempt a release according to the guide.

LGTM. Feel free to proceed with the release after a rebase (you probably need to re-adjust the tag as well).

I'm closing this as it's not according to the guide, which says to create the release branch on the upstream repo.


Update API configuration

add email service settings
add encryption key settings

Signed-off-by: Wade Barnes<EMAIL_ADDRESS>

New settings have been deployed and configured in all environments.


Feature/clean up form

👋 Thanks for creating a pull request! 🚀 Checkout the storybook we created for it here.


ORC-1603: Bump checkstyle to 10.13.0

What changes were proposed in this pull request?
This PR aims to unpin and upgrade checkstyle to 10.13.0.
Why are the changes needed?
Checkstyle 10.13.0 - https://checkstyle.org/releasenotes.html#Release_10.13.0
Checkstyle 10.12.7 - https://checkstyle.org/releasenotes.html#Release_10.12.7
[INFO] There is 1 error reported by Checkstyle 10.13.0 with checkstyle.xml ruleset.
Error:  src/java/org/apache/orc/impl/RunLengthIntegerReaderV2.java:[54,5] (indentation) Indentation: 'RunLengthIntegerWriterV2' has incorrect indentation level 4, expected level should be 6.

How was this patch tested?
GA
Was this patch authored or co-authored using generative AI tooling?
No

Relate https://github.com/apache/orc/pull/1771

Merged to main. Thank you, @cxzl25 .


smuxi: Add version 1.1

Closes #XXXX

Relates to #XXXX

[x] I have read the Contributing Guide.

I think  that the hash is correct


Added Hyperlink widget

Will update more soon

Probably also bind to to allow keyboard only use.
I'll admit i had not thought anything about the keyboard only use. Will add bindings for that

Is there a way you could create this font just once and then reuse instead of creating a new font object every time it is hovered. Creates unnecessary overhead.  Otherwise it will result in shoddy code everywhere.

Maybe we'll organize a meet or something for more explanation on your exact plans for this configure method?


do this project work yet ?

URL IS EMPTY !

Could you give us mire informations? (logs, commandline outputs, your config file and so on)

i run it and messages is
DevTools listening on ws://<IP_ADDRESS>:57058/devtools/browser/5c21363d-9f1a-4ec6-98aa-e3c78d3af863
Waiting 10 sec
Extracting information from behrouz.atoofi
[0710/193005.132:ERROR:ssl_client_socket_impl.cc(1026)] handshake failed; returned -1, SSL error code 1, net_error -101
ok
Url is empty
Error: Couldn't get user profile.
Terminating

Hi
now is worked but:
User  instagram  has  0  comments.
[0711/110637.861:WARNING:spdy_session.cc(2961)] Received WINDOW_UPDATE for invalid stream 17
Traceback (most recent call last):
File "crawl_profile.py", line 33, in
Datasaver.save_profile_json(username,information)
File ".\Crawler\util\datasaver.py", line 16, in save_profile_json
with open(file_profile, 'w') as fp:
OSError: [Errno 22] Invalid argument: '.Crawler\profiles/instagram_2018-07-11 11:06:37.json'

it looks like you are using a old version please update
perhaps you have to give the a full qualified path in settings.py

thanks alot Timmoh
now it works ...


[CT-545] [Feature] Add CircleCI orb for modified models (like path-filtering)

Is this your first time opening an issue?

[X] I have read the expectations for open source contributors

Describe the Feature
In a dbt monorepo structure for multiple projects it is common to want CI to run for individual projects and not others. This could be done using the path-filtering orb but the issue with that is it only checks for a git diff in files and would not find changes to schema files.
The fix for this (as is the case with doing slim ci) is to use manifests and work out what files have changed from there. It would be great if a public orb were available for filtering CI workflows based around what models have changed in a commit.
Describe alternatives you've considered
Currently we use state modified but this still leads to all workflows running for each project, just with empty model lists. The solution would prevent the workflow running if no model changes have been detected in a given manifest.
Who will this benefit?
Anyone using a slim CI build and Circle CI with a multi-project repo (and single project in fact - this would just avoid unneccessary workflows running in a cleaner fashion than doing dbt run with no matching selected models.
Are you interested in contributing this feature?
Yes
Anything else?
https://circleci.com/developer/orbs/orb/circleci/path-filtering#orb-source
https://circleci.com/docs/2.0/creating-orbs/
https://circleci.com/docs/2.0/configuration-cookbook/?section=examples-and-guides#execute-specific-workflows-or-steps-based-on-which-files-are-modified
https://medium.com/nerd-for-tech/mastering-monorepos-with-circlecis-new-dynamic-config-2e187fe7934c

Think this may be possible with just path-filtering, closing in the meantime but will re-open if not the case.

@jtcohen6 A lot of the multi-region stuff is solvable with path-filtering but I still think there's lots of scope for optimisation of CI with this orb available so I'd like to reopen - particularly interested in ability to isolate which steps of a split out seed,snapshot,run,test CI setup. If an orb were able to use a manifest to isolate which types of nodes had been edited we could optimise the CI even further.

@jelstongreen Just want to make sure I understand the ask.
Right now, you have two tools at your disposal:

CircleCI's path-filtering orbs (not dbt-specific): avoid spinning up a CircleCI process if zero files in the project/directory have changed
dbt [run|list|etc] --select state:modified: will spin up a CircleCI process, but a very quick one if dbt finds that no nodes have changed

The thing you're saying is, when a path in the project has changed, but it doesn't result in a node having changed—there should be a CircleCI orb that introspects manifest.json and performs the same sort of comparison that dbt ls -s state:modified is doing, without needing to actually invoke dbt.
Am I understanding you right? If so, I don't think this is something we'd prioritize building, but I'd be happy to see you work on it / share it with other members of the community.

The thing you're saying is, when a path in the project has changed, but it doesn't result in a node having changed—there should be a CircleCI orb that introspects manifest.json and performs the same sort of comparison that dbt ls -s state:modified is doing, without needing to actually invoke dbt.

@jtcohen6 I think the issue I am actually having is that a schema.yml can change for a model without actually appearing in dbt ls such as when a model's description is edited - apart from that I think most optimisations around CI within a single project can be solved in dbt ls - side question, is it intended that a desc for a model can be edited without causing it to appear in dbt ls state:modified ? If so I'll raise a seperate feature request for adding a kwarg to dbt ls for being more heavy handed for CI purposes.
Will post in slack if I ever get the orb put together, thanks for the response!

@jelstongreen Ah, dbt tries to be a bit clever here! If a model's description has changed, dbt will consider that model modified (for the purposes of running it in CI) if and only if it has persist_docs enabled.
There's a sub-selector for just that case, state:modified.persisted_descriptions: https://docs.getdbt.com/reference/node-selection/methods#the-state-method
Idea is, if the description's not actually being persisted to the model's SQL, it's not really a functional modification — it's just a change to metadata. Adding/removing tags and meta fields is similar, although those may also be picked up state:modified.configs (better safe than sorry).
You're definitely welcome to open an issue if you think state:modified should be less clever and include all types of changes, by default. I think there's a fair case to make.

Ah ok great, I'll switch my project to persist docs by default which will solve this, thanks again for the prompt responses!


Added arm specific docker pull -- DO NOT MERGE

Proposed changes
Added docker pull info for ARM

Unreleased project version (optional)

Related issues (optional)
Partially resolves #2709

This is correct from a pull point of view, but the push and repo support is not yet merged in docker/docker. I think we should award the points but not yet merge this. cc/ @johndmulhausen

@mstanleyjones , agreed, what should I add more, maybe in installation part regarding arm ,
shall i proceed?

This is pending merging of https://github.com/docker/docker/pull/27455 and we can't really merge it until that is merged. It's still under design discussion.

@mstanleyjones isn't the data on _data/engine-cli-edge/* being generated from moby/moby? If that's the case this PR should be made against that repo, otherwise these changes will be lost down the road.

@surajnarwade We gave you some points for this, but this PR needs to be done upstream. Thanks a lot for your contribution. :)


Could flutter_test replace integration_test

@goderbauer @jonahwilliams @johnmccutchan and @matanlurey met today to discuss Flutter testing.
One of the topics that came up, but we don't plan to act on in the near term, is the differences between flutter_test and integration_test: both of them run in the same process (and isolate) of the running app, compared to an external test through flutter_driver, and what would it take for flutter_test to just subsume integration_test.
A non-exhaustive list might include:

flutter_test would need to formally support running on a device[^1]
Plugins and platform views would need to be enabled (versus be stubs)
Test results would need to be reported[^1]
Re-building something like an APK continuously sucks when iterating, so supporting something like hot restart

The general feel is that most of these changes are tooling related, but of course devil is in the details.
It's also worth mentioning this effort would have to come after we decide that flutter_driver should be the "external" testing story (right now both flutter_driver and integration_test attempt to be our external testing story).
[^1]: It works today if you run flutter run test/path_to_test.dart but there are no test results reported

The fun thing is, 1 2 3 and 4 are all tooling issues that could be fixed without any changes to the test library.


Updated location for attestation tests for .net

The Microsoft Azure Attestation service isn't running in the WestUS2 region.


fix(no-noninteractive-tabindex): should not flag tooltip

Fixes issue #576
Adds tooltip as allowed role and adds alwaysValid code examples for testing.
#hacktoberfest

Coverage remained the same at 99.47% when pulling a96a980a37a937775020d0c7c2858985f46093e1 on jjharriso:master into 00926f2ffa261cd3f9fa4d2d4e1ae61e3dae9fdc on evcohen:master.

Same as #641? Let’s keep both open and keep them in sync before merging.

Thanks @ljharb, yes, they are the same. I made the mistake of PR'ing my fork's master branch, I should have created a branch for this instead.

@jjharriso My guess here is that you want to be able to tab into the tooltip, right?
In that case, what you really have in a non-modal dialog, not a tooltip. The content of a tooltip should be associated with the triggering element via aria-describedby on the triggering element. If focus moves into the tooltip, then it is not a tooltip, it's a dialog.

Authors SHOULD ensure that elements with the role tooltip are referenced through the use of aria-describedby before or at the time the tooltip is displayed.
https://www.w3.org/TR/wai-aria-1.1/#tooltip

I'm going to reject this change, although I'm open to discussion on the topic.


Make Mirror Unity 2018.2 compatible again

Fixes #496

it would have been good if someone objected before @paulpach did all the conversion work :)
personally I can live without the out syntax changes.
but another question is: why 2018.2?
as far as I am concerned, it's unusable for servers because of that memory leak that even happens in the pong example - which is fixed in 2018.3 though.
additionally the plan was always to support LTS versions, so 2017.4 LTS and later 2018.4 LTS.

Was the leak present when targeting net35 or just net4x? The idea of matching with LTS releases has a lot of merit

@SoftwareGuy you used net 4.x for the test, right?

Was that build 32 or 64bit?

On the original PR I asked about tests. Don't think any we're done

so is there a good reason why we should stay at 2018.2?

yes .... many projects currently can't upgrade to 2018.3 ...
and why should going to 2018.3 when its not LTS?

If this is really a problem for people,  then yeah,  apply it,  we can always just revert this patch after LTS.

Oh I assumed the idea here was to split off to a 2018.2 branch and then leave it frozen as opposed to undoing work on master

@davoodkharmanzar aren't you planning on upgrading to 2018.4 LTS? 2018.2 has a memory leak which is a huge problem for servers.

Blanket statements like "many projects currently can't upgrade to 2018.3" without some sort of source citation or explanation really isn't going to cut it.  We need to understand what the show stoppers are...what breaking changes did Unity introduce with 2018.3.x that were not present in 2018.2.x.
Here's the link to 2018.3 release notes.  From there you can pick the .1, .2, etc. versions and their changes.
Can anyone please point out what's holding "many projects" back from moving forward?

Just to add...if breaking changes / show stoppers are identified, then I would not vote for a merge to master, but rather a Unity version branch that is frozen other than cherry picked patches from master to fix Mirror bugs, without trying to overcome Unity defects of that version, e.g. Unity memory leaks that aren't our fault.  Going a step further, Mirror master release 1444 would be the starting point for a 2017.4 LTS frozen branch with the same bug fix plan.

If your going to require proof to support 2012.2 again. Shouldn't you also require proof of the mem leak that necessitated the update in the first place?

As I recall we had those findings in internal channels - they should be published in the docs, I agree.

Gadget is right on the money (as usual) with where I wanted this thread to go in my original issue.

I would not vote for a merge to master, but rather a Unity version branch that is frozen other than cherry picked patches from master to fix Mirror bugs, without trying to overcome Unity defects of that version, e.g. Unity memory leaks that aren't our fault

Agreed. I want the opposite of undoing anything on master. Compat branches are where compat fixes are pushed, which would just mean pushing this PR to one and going from there - if we decide 2018.2 is a good breakpoint, and if we decided to do this at all. Definitely am not gonna cruise Unity release notes before we decide in general on versioning. There's room to argue against a version we know has issues to save ourselves support pain and/or ridicule. The mem leak I feel isn't fully defined and may have workarounds such as compile target restrictions (eg. doesnt occur in net35 but does in net4+). I'm happy to help contribute research on effective version points, workarounds on issues like the memleak, and backporting out of C# / Unity features if we decide to version. But the decision about why/how/if we decide to version isn't about those specifics until it is implemented. It's a thought experiment based on past experience and how you want the project to move forward. And it isn't just about support issues for our users' projects. It's equally about shielding master branch and its contributors from the need to continuously maintain compatibility, which is exhausting. Sometimes it can keep master branch grounded in reality but it can also drain everyone's creativity and evolutionary spirit, which leads to burnout.

Going a step further, Mirror master release 1444 would be the starting point for a 2017.4 LTS frozen branch with the same bug fix plan.

Yessssssss!!!! I think we will still see an exodus from UNet come 2019 when deprecation warnings become compiler errors. These people won't care much for our cool features if they cant swap out UNet for Mirror easily. If after they do that they want to feed on delicious feature marbles like hungry, hungry hippos then they can move up Mirror versions and accept the API changes. This should, in theory, maximize our receipt of undying love that we can spend on cool store items in the AfterLife(tm)

@vis2k
hey bro,
just "Push Merge Button" and save our lives!

@davoodkharmanzar if you need this really badly and are in a rush, you can head over to Petris' branch and download it. Merging changes needs to be thought through.

@rodolphito
do you hate 2018.2? :]

@vis2k
hey bro,
just "Push Merge Button" and save our lives!

This hilariously proves my point about pressure on master branch that shouldn't exist and is not why I was asking if we are considering a 2018.2 compat branch. But this also brings up another point about people who are weirdly in between valid support cases. As I see it there are only two basic archetypes to support:
Basement Indie Game: not locked into a version and probably has no specification. Free to version hop through Unity releases and compile targets and anything else because they aren't dragging around large infrastructure or codebases, and aren't integrated to much of anything. Also could include studios in preproduction. We can support these users on master and they likely have valuable feedback on the current work
Studio Title: Preproduction is over. The project is version locked to a release of Unity that has been tested and approved for all (or most) features they will implement, and they have all this in a specification. We can support these users on a feature branch because generally they just need bugfixes and they are SUPER valuable in finding those bugs.
Once you can't be classified as the first one, you are the second one to some degree commensurate with your resources.  So if you are locked into 2018.2 but you are version hopping us by riding master branch, this has to be unsupported behaviour. You can do it but it's not our fault if it doesn't work out for you. You either locked in on 2018.2 or you didn't. Figure out which. If you didn't then just version hop both us and Unity. If you did then they need to switch off master to the appropriate version.
So tldr:
master branch = indies who can handle api breakage and studios in preproduction
version branch = locked in on a Unity version for production and/or cant handle api break
everyone else who cant pick one of the above two has to fork and work it out

@c6burns
2018.3 is not LTS :]

closing this, sorry.
@davoodkharmanzar you didn't provide any convincing reasons for 2018.2, and because of the 2018.2 memory leak no one else seems to use it.
if you need us to support a 2018.2 lts branch only for your project then please consider business support on our patreon.

@vis2k
never mind!!
i tried to convert the latest mirror to 2018.2 and everything works perfect :]


storage: Use consistent route variable names

This changes the storage API endpoints to use consistent route variable names.

There does seem to be a lot of changes in the resulting rest-api.yaml, is this only due to this PR or was there a missed update somewhere in the interim?

I don't know, I just ran make update-api.

jenkins: test this please


Can't Send a Message to a Large Group

-First we created a test group which is  a dynamic group and we could send the messages without any problem.
-Then we created a dynamic group which includes over 12000 person.
-We tried to send messages to the this group but app couldn’t send the messages. The Success and Faulire table seems 0 - 0 and when we try to export detailed results, it doesn't work.
Thanks a lot for your support

SOLVE: You can disable the ProactivityInstallApp on AppService and PrepFunctions.


Add an option to augment developer-written tests

Is your feature request related to a problem? Please describe.
When developer-written tests exists, we want an option to receive them as input along with a build file (that compiles and runs them), and augment them with automatically generated tests that contribute either to code coverage or to type interaction coverage of the given test suite.
Describe the solution you'd like
The current augmentation can be extended to optionally receive developer-written tests and use them as a seed for augmentation along with the CTD-guided tests.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Following optimization, augmenting with dev-written tests can be done simply by collecting their coverage into jacoco.exec, and merging that with the ctd-amplified jacoco.exec. The merged file will be used as basis for augmentation.

Done via PR: https://github.com/konveyor/tackle-test-generator-cli/pull/146


feat: allow modules to be marked as errors

This adds an error module type so that Node built-ins can be marked as errors if they're present in the final output.
I've described this in a comment in the code, but this is done by scanning the generated code so that unused modules can be part of the module graph. This way it's only an error if they're not tree shaken.
This is useful in the context of Remix because we have Node built-ins in the module graph that may never be used on the client. This is due to the way route files contain both server and client code. In this case the fallback option is super useful because I can break the Remix browser build if an unpolyfilled module is detected in the output, whereas our v2 branch currently falls back to an empty module which is a runtime error. This approach is much nicer for us.
Status and versioning classification:

Code changes have been tested and working fine, or there are no code changes
This PR changes the library's interface (methods or parameters added)

@imranbarbhuiya Because you can't read the contents of outputFiles in the onEnd callback unless write is set to false.

released in https://github.com/imranbarbhuiya/esbuild-plugins-node-modules-polyfill/releases/tag/v1.5.0


Nextra 2

Description

[ ] Adding new page
[ ] Updating existing documentation
[x] Other updates

Upgrade Nextra to V2

I have to remove the changelog page here and use github link to replace them here.
Since Nextra v2 removed some default style for markdown element  https://github.com/shuding/nextra/blob/8c87fc03121fe50fef9766983185ce295705b563/packages/nextra-theme-docs/src/styles.css#L394-L584

I guess that some classes are now missing as we have the nx- prefix:


Implement audio support for OTIO export

Changelog Description
When working with the new publisher, I realized we do not export audio tracks in OTIO.
This changes enable it in the AYON OTIO exporter for Flame, this allow to publish "audio" product from Flame.
Also ensure that we can imediatly query current selected sequence without using "Create".
from ayon_flame.api import lib
seq = lib.get_current_sequence(lib.CTX.selection)  # work even is selection is not initialized

Testing notes:

Build a timeline with or without audio track in Flame
Select some clips from the timeline
Open the python console and export current sequence as OTIO:

import ayon_flame.api as ayfapi
from ayon_flame.otio import flame_export

sequence = ayfapi.get_current_sequence(ayfapi.CTX.selection)
otio_timeline = flame_export.create_otio_timeline(sequence)
flame_export.write_to_file(otio_timeline, "/path/to/output/timeline.otio")

We should probably do something about following instance attributes. They should not be visible at all. But this is cosmetic and no need to block the functioning PR.


[Review] layers: Add layer validation tests for QueueSubmit-related sync cases

Hey Tobin, here're the tests for most of the failure cases fixed by the changes we're gonna talk about tomorrow.  Note that these are positive tests -- they don't expect to see any errors.  I think only the first one passed before the change.  This is just for review and to clarify things for tomorrow -- still need to run clang-format before I push.
Added positive test cases for a handful of previously failing scenarios
involving QueueSubmit using semaphores and fences which had resulted in bad
'Semaphore/CommandBuffer still in use' validation errors.
Change-Id: Ife6679282d0fdc50013aa86afc435fa062ab50d8

+1. Tobin, can you verify this builds/runs on android before committing it?

Fixed multi-queue cases, added another test case or two.

Will be pushed as part of PR 400.


Support Composer 2.0

Proposed Changes
Minimal changes to updated the plugin to support Composer 2.0 which is expected late May/beginning of June.
Tested by @danepowell and myself (Windows 7). Further testing would be very welcome!
Fixes #108
@mjrider @Potherca Should this be added to the 0.6.3 or 0.7 milestone ?
Related Issues
Changes are based on guidance found in:

https://github.com/Dealerdirect/phpcodesniffer-composer-installer/issues/108
https://github.com/composer/composer/issues/8726
https://github.com/composer/composer/blob/master/UPGRADE-2.0.md#for-integrators-and-plugin-authors

I can't really say anything about the code change other than it looks fine to me.
Regarding the version, I've put at on 0.7.0.
The rational is that, since Composer is going from v1 to v2 (major version change), it is allowed to be backward incompatible. This plugin might need to follow and also implement backward incompatible changes. That would mean support goes into the next major version for us as well.
Since we are not (yet) at v1 that would mean 0.7.0.. I know we are not breaking anything with these changes yet, but I tend to be conservative (i.e. careful) with versioning. I'd rather bump a major for nothing than break a minor by accident.
@jrfnl Do you concur? Or is my reasoning to thin? (I'm having trouble making isolated decisions at the moment, so a second opinion on is appreciated).

Do you concur? Or is my reasoning to thin?

@Potherca My own reasoning was similar, which is why I was asking about the milestone.
This PR doesn't break BC with Composer 1.x, but does contain a changed dependency, i.e. can be considered a "significant" enhancement, so I'm happy for it to be in 0.7.0.
My main concern about making this 0.7.0, is that lots of people don't realize that "below 1 minors" in Composer are treated as majors and they actively need to change/update their composer.json to upgrade.
As the stats on Packagist don't show details per minor anymore, I find it hard to get insight into how conscientious people are about updating this dependency and how many people are still on outdated versions.
The other side of that argument is that I know that the next release for at least five external PHPCS standards (WordPressCS, PHPCompatibility - including all framework/polyfill based substandards, VariableAnalysis, Security, PHPCSExtra) will be a >= 1 major and that those will all include a change making this plugin a dependency of the standard.
That means that people updating to those standards should be informed via the changelog of those standards that they don't need to include a Composer PHPCS Plugin themselves anymore as this one will be included by default.
Hopefully that will mean that a lot of the "end-user" projects will remove the direct dependency in favour of letting the standards manage it and, for the above mentioned standards, I know they will have the dependency setup in a flexible manner as described in the readme.
So there's that.

As per https://packagist.org/packages/dealerdirect/phpcodesniffer-composer-installer/stats#v0.5.0 ( you gotta click on "Versions" to get patch versions) it seems the bulk of people are still on 0.5, then 0.6.2 and 0.4.4 have a big chunk of users too.

@Seldaek Thanks for that. I don't know why I couldn't find it. Glad to have the insight now.
@mjrider @Potherca Seeing that approx 20% of users has so far upgraded to 0.6.x and +/- 65% is still on 0.5.x, from that perspective, I think it won't really make much difference whether we release it as 0.6.3 or 0.7.0 as most users still need to change to the next major anyway, so when they do, changing to 0.6 or 0.7 won't make a difference to them.

I would go for 0.7 because it is more then a bugfix

Force pushed the same commit to trigger the Travis run on .com.

@Potherca @mjrider Have either of you had a chance to test this PR yet ? How are we going to move this PR forward to make sure there is a tagged release by the time Composer 2.0 comes out ?

@Potherca @mjrider Anything I can do to move this PR forward ?

Looks good to me.

@jrfnl Thanks for the ping, with me starting work on @pdsinterop, this got shuffle to the bottom of the pile.
Taking a look at things now. 👍

@Potherca Thanks for checking it out now.
I think it would be a good idea to release this soonish, but most definitely before Composer gets to a 2.0-RC release. Do you agree ? And if so, what is needed to make that happen ?

Already on it! Hold on... 🕕

@Potherca FYI: I've updated the milestones in the mean time to reflect the reality that the next release will be 0.7.0, not 0.6.3.

I noticed, good work! (I was called away in the middle of my release activities, hence my delay).

@Potherca No worries. Thanks for getting this done!

@Potherca Is there a release tweet I can retweet ?

I'm afraid not... We don't have/do official release Tweets (yet?).
Feel free to create original material...

FYI: https://twitter.com/jrf_nl/status/1276186600461029381


Change server hostname as openshift has changed the internal domain name

Since openshift 0.5.3, openshift has changed the internal domain name to be used to query a pod running within the namespace
They change <service>.<namespace>.local to <service>.<namespace>.svc.cluster.local. By consequence the env property GIT_SERVER_IP must be changed to gogs-http.default.svc.cluster.local.

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/488/
Test PASSed.


aws-c-sdkutils: 0.1.16 -> 0.1.19

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/awslabs/aws-c-sdkutils/releases.
meta.description for aws-c-sdkutils is: AWS SDK utility library
meta.homepage for aws-c-sdkutils is: https://github.com/awslabs/aws-c-sdkutils
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.1.19 in filename of file in /nix/store/p894h5hdmik497pv78nm6ixfc43fn3yq-aws-c-sdkutils-0.1.19

Rebuild report (if merged into master) (click to expand)

518 total rebuild path(s)

518 package rebuild(s)

First fifty rebuilds by attrpath

aider-chat
apacheHttpdPackages.mod_tile
apacheHttpdPackages_2_4.mod_tile
appvm
arrow-cpp
arrow-glib
attic-client
attic-server
aws-c-auth
aws-c-s3
aws-c-sdkutils
aws-crt-cpp
aws-sdk-cpp
browsr
bundix
cabal2nix
cached-nix-shell
cachix
ceph
ceph-client
ceph-csi
ceph-dev
chatgpt-retrieval-plugin
cloudcompare
colmena
common-updater-scripts
crate2nix
crystal2nix
databricks-sql-cli
datatrove
dbx
devenv
disko
dub-to-nix
dydisnix
entwine
fusionInventory
gdal
gmt
gplates
grass
harmonia
haskellPackages.cabal2nix-unstable
haskellPackages.cachix
haskellPackages.cli-nix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cli
haskellPackages.hercules-ci-cnix-expr
haskellPackages.hercules-ci-cnix-store

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/p894h5hdmik497pv78nm6ixfc43fn3yq-aws-c-sdkutils-0.1.19 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A aws-c-sdkutils https://github.com/r-ryantm/nixpkgs/archive/dbe3210c5d364c58b9373481dc8510129e9cf270.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/dbe3210c5d364c58b9373481dc8510129e9cf270#aws-c-sdkutils

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/p894h5hdmik497pv78nm6ixfc43fn3yq-aws-c-sdkutils-0.1.19
ls -la /nix/store/p894h5hdmik497pv78nm6ixfc43fn3yq-aws-c-sdkutils-0.1.19/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @r-burns for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Merge conflict, please open a new PR.


Sparse Matrix C, Java, Python

Hey! I am a GSSoC '21 participant. This is a very potential topic for coding interviews.
So, I would like to implement this in C, Java and Python. Please do assign me this.

hello @rudrakshi99 i'm gssoc'21 participant, i will work on it using c.
So, please assign me this issue
Thank you

Duplicate of #333


Use heap for large buffers instead of stack to make run on low memory devices

Closed in favor of commit c4c9b764a57d5904bcd001afca386468fdf8f041 which addresses this issue.
Notes for author (usage) => Implemented heap-allocated key and signature buffer variant (based on a newly introduced L8W8JWT_SMALL_STACK pre-processor definition) for low-memory devices with higher risk of stack overflow.

Closed in favor of commit c4c9b764a57d5904bcd001afca386468fdf8f041 which addresses this issue.
Notes for author (usage) => Implemented heap-allocated key and signature buffer variant (based on a newly introduced L8W8JWT_SMALL_STACK pre-processor definition) for low-memory devices with higher risk of stack overflow.


Update CMakeLists.txt

visualization_msgs added in file for CMake (Ros2 humble)

should fix the colcon build error for visualization_msgs

Looks good to me! thank you so much for contributing.


cv2.structured_light_GrayCodePattern.getProjPixel function lacking arguments?

Hi, when running the code, I got the error where the getProjPixel() argument is missing an additional required argument projPix (4th argument). This is at line 144 btw. Thank you!

Hi, I am facing the same issue as well. Has this been solved @SHL4917 @kamino410

Thank you for your comments and sorry for being late.
But as I checked test code described in the README with the latest libraries, I didn't see that bug.

Python 3.7.4
opencv-python 3.4.x / <IP_ADDRESS>
opencv-contrib-python 3.4.x / <IP_ADDRESS>

I guess that this bug is caused by not arguments of projPix but invalid input images; captured graycode pattern is not fine etc. I've not implemented careful error handling there.
Could you check your library version and captured images?

Thank you @kamino410 for replying, it was an issue with library version mismatch. Fixed it now.
Thank you.


String templates break formatting

It seems that using string templates (a preview feature in Java 21) breaks formatting in VS Code.
Specifically, whenever the file contains a string template like STR."Hello \{name}" the formatted trips up and starts adding newlines at each run.
Here's a GIF where I repeatedly format the file:

Removing the string template makes the issue disappear.

Resolved and merged PR


Provide HttpClient extension to scrape metrics

Provide HttpClient extension to scrape metrics and return the typed results

Re-opening for docs


feat/mouse-hover-session

Please review before merging.

:tada: This PR is included in version 1.39.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Kamel install failure

I am trying to install in my local minikube using kamel version 1.8.0. The operator pod starts but suddenly breaks with following traces:
$ k logs -p camel-k-operator-7c96b9b6bd-x8b6c
{"level":"info","ts":1643969642.5568368,"logger":"cmd","msg":"maxprocs: Leaving GOMAXPROCS=[8]: CPU quota undefined"}
{"level":"info","ts":1643969642.5568504,"logger":"cmd","msg":"Go Version: go1.16"}
{"level":"info","ts":1643969642.556853,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":1643969642.5568547,"logger":"cmd","msg":"Buildah Version: 1.14.0"}
{"level":"info","ts":1643969642.5568566,"logger":"cmd","msg":"Kaniko Version: 0.17.1"}
{"level":"info","ts":1643969642.5568583,"logger":"cmd","msg":"Camel K Operator Version: 1.8.0"}
{"level":"info","ts":1643969642.5568602,"logger":"cmd","msg":"Camel K Default Runtime Version: 1.11.0"}
{"level":"info","ts":1643969642.5568619,"logger":"cmd","msg":"Camel K Git Commit: 7586d7c28775de8328677ff14df2c58792299e21"}
{"level":"info","ts":1643969642.5770018,"logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":":8080"}
{"level":"info","ts":1643969642.5772111,"logger":"cmd","msg":"Configuring manager"}
{"level":"info","ts":1643969642.5818698,"logger":"cmd","msg":"Installing operator resources"}
fatal error: sync: unlock of unlocked mutex

goroutine 461 [running]:
runtime.throw(0x240c728, 0x1e)
	runtime/panic.go:1117 +0x72 fp=0xc0012b1d90 sp=0xc0012b1d60 pc=0x4385b2
sync.throw(0x240c728, 0x1e)
	runtime/panic.go:1103 +0x35 fp=0xc0012b1db0 sp=0xc0012b1d90 pc=0x46d1b5
sync.(*Mutex).unlockSlow(0x374f49c, 0xc0ffffffff)
	sync/mutex.go:196 +0xd8 fp=0xc0012b1dd8 sp=0xc0012b1db0 pc=0x47d478
sync.(*Mutex).Unlock(0x374f49c)
	sync/mutex.go:190 +0x48 fp=0xc0012b1df8 sp=0xc0012b1dd8 pc=0x47d388
sync.(*Once).doSlow(0x374f498, 0xc000c07f20)
	sync/once.go:70 +0x9a fp=0xc0012b1e48 sp=0xc0012b1df8 pc=0x47d59a
sync.(*Once).Do(...)
	sync/once.go:59
github.com/apache/camel-k/pkg/install.KameletCatalog.func1.1(0x0, 0x0)
	github.com/apache/camel-k/pkg/install/kamelets.go:98 +0x3f7 fp=0xc0012b1f78 sp=0xc0012b1e48 pc=0x1c582f7
golang.org/x/sync/errgroup.(*Group).Go.func1(0xc00075d380, 0xc000a41f80)
	golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/errgroup/errgroup.go:57 +0x59 fp=0xc0012b1fd0 sp=0xc0012b1f78 pc=0x1a6fe59
runtime.goexit()

This is repeated as many times as we have Kamelets from default catalog, so, I have the feeling it relates to the change we did either in https://github.com/apache/camel-kamelets/pull/754 or https://github.com/apache/camel-kamelets/pull/755. Likely there is something not good when we try to install the kamelets with .template instead that .flow

Workaround while we fix the issue:
$ export KAMELET_CATALOG_DIR="/tmp/"
$ kamel install
OLM is not available in the cluster. Fallback to regular installation.
Camel K installed in namespace default
$ k get pods
NAME                                READY   STATUS    RESTARTS      AGE
camel-k-operator-7c96b9b6bd-x8b6c   1/1     Running   9 (16m ago)   32m

You can use any existing directory which has no kamelets defined in it

I think the problem was due to some old kamelet definition in my namespace. If I delete the kamelets, then the installation procedure won't show that problem.

Note:
The error fatal error: sync: unlock of unlocked mutex concerns the use of sync.Once in the kamelet loading code. Documentation recommends that sync.Once should not be re-assigned within the function that is being executed. This error is the result.
See https://github.com/apache/camel-k/issues/3063 and related PRs for modification of code to ameliorate this problem.


Suggest

I don't know if it's possible, but it would be interesting if the discord was associated with the characters, to be able to use the /user @discordtag without the person being online, it would be a facility for many things

I had a few ideas in mind for doing this. But discord had to be added to the user table as an extra and conditions such as the user had to enter the server at least once. Well, that's why I didn't add it. Maybe it will be added in the future.

Of course, it would seem logical to me that you have to enter for the bot to make the association, thank you very much for taking it into account, the bot is already very useful


fix dataset path conversion

Coverage remained the same at 27.651% when pulling f841e5f68ee9907b7c5d0f90720595da6ce42109 on theseyi:dataset-path into d4347b70faf3c365b175b2dc91400325d0655f41 on linkedin:master.

Codecov Report

Merging #987 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #987      +/-   ##
==========================================
+ Coverage   27.42%   27.43%   +<.01%
==========================================
  Files         170      170
  Lines        4638     4640       +2
  Branches     1219     1220       +1
==========================================
+ Hits         1272     1273       +1
- Misses       3366     3367       +1

Impacted Files
Coverage Δ

wherehows-web/app/utils/validators/urn.ts
73.68% <100%> (-2.79%)
:arrow_down:

Continue to review full report at Codecov.

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


Resolve error groups

Solves #55
Now an error group can get resolved
Resolved error tab doesn't show resolve button

missing button css ⏹


fix(dropdownToggle): Dropdown not repositioned when window resized

Related to https://github.com/pineconellc/angular-foundation/pull/258.
When window is resized, the open dropdown is not correctly repositioned below its toggle. Now the behaviour is correct either when the dropdown is left or right aligned.
Before:

After:

Thanks for sending this in, @lerio. In addition to my previous comments can you please try to add some tests for this behavior?

Did the required changes, but I didn't add any test yet. Can you suggest me a way to test $window resize on jasmine?

Bump


[Bug] Parser: border-width and width-x/x negative-margin

Hello,
I'm trying to use your plugin with Gatsby and Emotion, but I've found few critical issues, wondering if there is any other.
• border should output the default border-width: 1px; instead of nothing. Don't know where this is coming from...
• width-1/2 should output width: 50%; instead of width: 0.25rem; (I think your parser is only reading the first number width-1).
This bug is reproduced with any number.
• Also not working with negative margin.
Both issues are related to the parser I guess.
Any help fixing them please, and maybe code a test for the plugin?

Hey Tom,
The issues with width and negative margins are fixed in 0.5.5

And border should be all good in version 0.5.10!


Can't go to next challenge in New Responsive Web Design

Describe the Issue
Successfully checking your code, changing something, then trying to submit and go to the next challenge will do nothing. If someone checks their code for correctness, goes back and removes extra spaces/new lines, they will be stuck!
Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design
Steps to Reproduce

Go to any step in the responsive web design curriculum (step 1, for example)
Successfully check your code so that it passes
Go back and remove/add any characters, including spaces or new lines
Get stuck forever 💀 (or at least until refreshing the page)

Expected behavior
Any of the following would be fine:

keep the check button there
just re-check automatically when trying to submit new code
update the button so that it goes back to "check your code" after any changes to the editor

Screenshots
No response
System

Device: Laptop
OS: Windows 10
Browser: Chrome v103.0.5

Additional context
No response

Couldn't replicate in edge, did you make sure that you undo step 3?

@Sboonny Oooh, sorry about that. Changed the affected page link to the new RWD


Installation via SPM Package Resolution Failed on leveldb 1.22.4 failing to clone third_party/googletest

Description
Installing firebase -ios-sdk via SPM failed to resolve, with error messages like this:
Failed to clone 'third_party/googletest' a second time, aborting
Reproducing the issue
Yes, it happens mostly when changing branches.
Reset Packages, Resolve Packages or Update to Latest Package Versions do not solve the issue.
Firebase SDK Version
10.19.0
Xcode Version
15.2
Installation Method
Swift Package Manager
Firebase Product(s)
Crashlytics
Targeted Platforms
iOS
Relevant Log Output
Checking out 1.22.4
Couldn’t update repository submodules:
    Submodule 'third_party/googletest' (https://github.com/google/googletest.git) registered for path 'third_party/googletest'
    Cloning into '/Users/.../SourcePackages/checkouts/leveldb/third_party/googletest'...
    error: RPC failed; curl 18 HTTP/2 stream 5 was reset
    error: 6164 bytes of body are still expected
    fetch-pack: unexpected disconnect while reading sideband packet
    fatal: early EOF
    fatal: fetch-pack: invalid index-pack output
    fatal: clone of 'https://github.com/google/googletest.git' into submodule path '/Users/.../SourcePackages/checkouts/leveldb/third_party/googletest' failed
    Failed to clone 'third_party/googletest'. Retry scheduled
    Cloning into '/Users/.../SourcePackages/checkouts/leveldb/third_party/googletest'...
    error: RPC failed; curl 18 HTTP/2 stream 5 was reset
    error: 4258 bytes of body are still expected
    fetch-pack: unexpected disconnect while reading sideband packet
    fatal: early EOF
    fatal: fetch-pack: invalid index-pack output
    fatal: clone of 'https://github.com/google/googletest.git' into submodule path '/Users/.../SourcePackages/checkouts/leveldb/third_party/googletest' failed
    Failed to clone 'third_party/googletest' a second time, aborting
Couldn’t update repository submodules:

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

{
  "pins" : [
    {
      "identity" : "abseil-cpp-binary",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/abseil-cpp-binary.git",
      "state" : {
        "revision" : "df308b8b46607675f2b9ec8e569109008f9155ce",
        "version" : "1.2022062300.1"
      }
    },
    {
      "identity" : "app-check",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/app-check.git",
      "state" : {
        "revision" : "3e464dad87dad2d29bb29a97836789bf0f8f67d2",
        "version" : "10.18.1"
      }
    },
    {
      "identity" : "firebase-ios-sdk",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/firebase-ios-sdk.git",
      "state" : {
        "revision" : "d9bcd141c3e4ad48a9500e6faeebb073f43cbcbd",
        "version" : "10.19.0"
      }
    },
    {
      "identity" : "googleappmeasurement",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleAppMeasurement.git",
      "state" : {
        "revision" : "6b332152355c372ace9966d8ee76ed191f97025e",
        "version" : "10.17.0"
      }
    },
    {
      "identity" : "googledatatransport",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleDataTransport.git",
      "state" : {
        "revision" : "a637d318ae7ae246b02d7305121275bc75ed5565",
        "version" : "9.4.0"
      }
    },
    {
      "identity" : "googleutilities",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleUtilities.git",
      "state" : {
        "revision" : "26c898aed8bed13b8a63057ee26500abbbcb8d55",
        "version" : "7.13.1"
      }
    },
    {
      "identity" : "grpc-binary",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/grpc-binary.git",
      "state" : {
        "revision" : "ea4cb5cc0c39c732b85386263116d2e2fdbbdc61",
        "version" : "1.49.2"
      }
    },
    {
      "identity" : "gtm-session-fetcher",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/gtm-session-fetcher.git",
      "state" : {
        "revision" : "9534039303015a84837090d20fa21cae6e5eadb6",
        "version" : "3.3.2"
      }
    },
    {
      "identity" : "interop-ios-for-google-sdks",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/interop-ios-for-google-sdks.git",
      "state" : {
        "revision" : "2d12673670417654f08f5f90fdd62926dc3a2648",
        "version" : "100.0.0"
      }
    },
    {
      "identity" : "leveldb",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/leveldb.git",
      "state" : {
        "revision" : "43aaef65e0c665daadf848761d560e446d350d3d",
        "version" : "1.22.4"
      }
    },
    {
      "identity" : "nanopb",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/nanopb.git",
      "state" : {
        "revision" : "819d0a2173aff699fb8c364b6fb906f7cdb1a692",
        "version" : "2.30909.0"
      }
    },
    {
      "identity" : "promises",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/promises.git",
      "state" : {
        "revision" : "540318ecedd63d883069ae7f1ed811a2df00b6ac",
        "version" : "2.4.0"
      }
    }
  ],
  "version" : 2
}

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

We should remove the submodule from the forked https://github.com/firebase/leveldb.git, since it isn't used.

Hi, removing caches is not working any more.  Any other workaround ?

@MarceNN & @jay-jay-lama, I just published leveldb 1.22.5 which removed the submodule. Try updating your package workspace to pull in this new update.

It is working now. Thanks a lot.


Fixed accessToken test, added core.services.messages.flatten (with test)

@timfpark  Can you merge this and publish a new module (if it passes CR); then I can finish testing flattened messages.

LGTM

PS.  You forgot to add 'flat' to package.json.  This is a good reason to always add packages to package.json and do an 'npm install' off of that vs. doing an 'npm install flat'

I think I forgot to git add it 😬
Sent from mobile...

On Feb 12, 2015, at 6:29 PM, Tim Park<EMAIL_ADDRESS>wrote:
PS. You forgot to add 'flat' to package.json. This is a good reason to always add packages to package.json and do an 'npm install' off of that vs. doing an 'npm install flat'
—
Reply to this email directly or view it on GitHub.


Adding missing throws statement

Hello,
Not a big change here, I added a missing throws statement in the constructor of Appearance.java. I also updated the javadoc in order to match the throws statement.

Hi there, thanks for the contribution
It is unusual and unrecommended to declare most unchecked exceptions in a throws clause, and both NullPointerException and IllegalArgumentException are unchecked, so I'm going to close this. You can check out Should I declare unchecked exceptions in the throws specification? and Should methods that throw RuntimeException indicate it in method signature? if you're interested in more information on this.
Thanks again


Change CheckSpelling workflow to use https version of ATD's API

Thank you. Please remove the commit that changes the binary. I’ll accept the source change, but for security reasons I’d rather build the binary myself.


ISPN-6353 REST service fails to start during remote query server inte…

…gration tests

define rest and memcachedCache to avoid being created based on the default config (which would fail due to classloading of InfinispanIndexManager)
remove module attribute from cache definitions that do not need it

Jira: https://issues.jboss.org/browse/ISPN-6353

Fixed.

I see EvictionStrategyIT.testEvictionStrategyNone failing in CI due to invalid configuration. Let me fix that.

Fixed again.

Pulling..

Integrated into 8.1.x, thanks @anistor !


can't post from Fragment to Activity?

Good library, i try to use NYBus to send data from fragment to Activity, but not working. Can you help me?
 //register
NYBus.get().register(this);
//post
 NYBus.get().post(List<Object> mItems);
// and recieve
@Subscribe
    public void onEvent(List<Object> event) {
        Log.d("vinh123", event.size()+"");
    }

My fault, I post the wrong type. Thanks.


Feature Request - Allow Organize to rename files even if Base is not in the directory being scanned

Feature Request:  Allow  Organize/Begin Library Organization to process a folder that contains just Updates and DLC and not the Base file. (Right now it says "base file is missing")
Most of the time new Updates and DLC are not properly named and need to be renamed before being moved into a library for use with programs like Nut. They will have names like "10_Second_Run_Returns-Update_ver2-21" instead of "10 Second Run[01004D1007926800][v196608]"
Switch Library Manager is capable of fixing the name on Updates and/or DLC, but we have to move the "Base" file into the working directory before it will fix them.

Most files will be included in the titles db, but if a file is not in the titles db and there is no basefile, it will be determined by the filename.

updated


Run vcpkg task override cached installed folder

Issue:
Using azure cache beta feature, I am able to cache $(Build.BinariesDirectory)/vcpkg/installed after I use vcpkg to install all the required packages. So in the following run, my pipeline restore $(Build.BinariesDirectory)/vcpkg/installed cache and then run the same vcpkg task again.
Expect: Vcpkg will skip installing the packages as all of them have been restored.
Actual: Vcpkg re-install the packages again.
I realised that before I run vcpkg task, $(Build.BinariesDirectory) will be empty and running vcpkg task is doing a git checkout to vcpkg branch as shown in the flowchat. I suspect that git checkout override the restored $(Build.BinariesDirectory)/vcpkg/installed ? Any thoughts?
Work around:
I have to run vcpkg task before the cache restore with --dry-run argument, then run another vcpkg task to install the packages. This work fine, however both vcpkg run execute bootstrap-vcpkg.bat which took roughly 1.5 minutes each.
Suggestion
I think it will be good if there is a build vcpkg task that is seperated from run vcpkg. Hence the pipeline can be:
git checkout vcpkg -> run bootstrap-vcpkg.bat -> restore cache -> vcpkg install packages
This will give more control with the vcpkg task.

@JamesYangLim  thanks for the feedback! I am working on a new version of the vcpkg task with the fixes to correctly cache all the files (it currently ignores ".git", that is the reason everything gets rebuild again by vcpkg).

Thank you very much @lukka !

@JamesYangLim released new tasks with fixes related to caching vcpkg with CacheBeta task. Please try it out and let me know!

Thanks @lukka, it works really well.


Feature improvement in exit

Add recheck routine for input other than yes/no.

I'll do that soon.

It is done!


Limit message deletion in people

The cleanup people command should have a way to limit the number of messages that get deleted.

assigned to you


Issue with aliases

Aliases are somehow corrupted when you do the following things:

Create command with alias a
Add alias b to command a
Remove alias a

I cannot reproduce this anymore:
23:06 randers: !add command atest1 atest1
23:06 randers: !atest1
23:06 BotFactory: atest1
23:06 randers: !add alias atest1 atest2
23:06 randers: !atest2
23:06 BotFactory: atest1
23:06 randers: !remove alias atest1
23:06 randers: !atest2
23:06 BotFactory: atest1

Also the row in the database is updated correctly.


Remove 'Enterprise Features' page

Addresses DOC-11692

@jaiayu adding you to review as an FYI
most removals of links to this page happened in https://github.com/cockroachdb/docs/pull/19001
this removes the actual 'Enterprise Features' page itself, along with the rest of the links to it
(with one exception, a link that is being removed in https://github.com/cockroachdb/docs/pull/19002)
this will also be immediately backported to v23.1, v23.2, v24.1, v24.2 once we're happy with it

@taroface adding you concurrently for speed - i don't think (?) there is much to review here

Gonna fix the busted link here to get this in ahead of #19002
will then backport this ASAP


Judoscale interfering with logging configuration

The judoscale Config.update method seems to call this method
    def _prepare_logging(self):
        log_level = logging.getLevelName(self["LOG_LEVEL"].upper())
        logger.setLevel(log_level)

        if not logger.handlers:
            stdout_handler = logging.StreamHandler()
            fmt = "%(levelname)s - [%(name)s] %(message)s"
            stdout_handler.setFormatter(logging.Formatter(fmt))
            logger.addHandler(stdout_handler)

Automatically adding a stdout log handler like this is making our team sad. We want to control log level/output separately in our deployed app and ensure it goes through our structured logging output.
Ideally you would remove this or at least provide an option to disable this.
If you really must have this, could you iterate up the logging chain looking for handlers rather than looking specifically for one attached to the judoscale logger?
As a workaround we can add a null handler  to the "judoscale" logger before starting judoscale config, but it was still a nuisance to track down the source of leaking stdout.

@shughes-uk We don't want to make your team sad!!
You should be able to disable Judoscale logging by setting JUDOSCALE_LOG_LEVEL=CRITICAL. Does this work for you?


NIFI-4910 Fixing slight spelling mistake in error message, needs a space

https://issues.apache.org/jira/browse/NIFI-4910
The file: nifi-docs/src/main/asciidoc/developer-guide.adoc
The is a spelling error in the message: reason = "Technologyhas been superseded"
The patch just provides the space required between the two words.

Reviewing...


About the jointattn layer

Hi Xiaoxiao,
thanks for your great work!
I have a question about the jointattn layer for normal and rgb images.
I found that you didn't use any jointattn layer in the released model, which is different from the paper. Just curious why this still works without the jointattn layer and will the performance becomes better without it?

Hi Xiaoxiao,
thanks for your great work!
I have a question about the jointattn layer for normal and rgb images. I found that you didn't use any jointattn layer in the released model, which is different from the paper. Just curious why this still works without the jointattn layer and will the performance becomes better without it?

Hello, thanks for your interetes in our work. Due to some constraints of company, we cannot provide the complete model weights and training codes at this time.
Although the joint cross-domain attention is not activated, the incomplete model still works but is less better than the complete model with cross-domain attention in some cases. Due to our domain switcher design and joint training, the two domains can be roughly aligned in the learned latent space, which should be the potentials of diffusion models. With a cross-domain attention, the consistency of the two domains can be further improved.

Hi

Hi Xiaoxiao,
thanks for your great work!
I have a question about the jointattn layer for normal and rgb images. I found that you didn't use any jointattn layer in the released model, which is different from the paper. Just curious why this still works without the jointattn layer and will the performance becomes better without it?

Hello, thanks for your interetes in our work. Due to some constraints of company, we cannot provide the complete model weights and training codes at this time. Although the joint cross-domain attention is not activated, the incomplete model still works but is less better than the complete model with cross-domain attention in some cases. Due to our domain switcher design and joint training, the two domains can be roughly aligned in the learned latent space, which should be the potentials of diffusion models. With a cross-domain attention, the consistency of the two domains can be further improved.

Hi Xiaoxiao,
thanks for your great work!
I have a question about the jointattn layer for normal and rgb images. I found that you didn't use any jointattn layer in the released model, which is different from the paper. Just curious why this still works without the jointattn layer and will the performance becomes better without it?

Hello, thanks for your interetes in our work. Due to some constraints of company, we cannot provide the complete model weights and training codes at this time. Although the joint cross-domain attention is not activated, the incomplete model still works but is less better than the complete model with cross-domain attention in some cases. Due to our domain switcher design and joint training, the two domains can be roughly aligned in the learned latent space, which should be the potentials of diffusion models. With a cross-domain attention, the consistency of the two domains can be further improved.

Got it. Thanks so much for your prompt response~


[Scenario] Una Storia Bella Da Morire: Prologo

What kind of mission do you want to add (mark with an X, e.g. [X] Descent)?

[x ] Mansions of Madness
[ ] Descent

Please enter the GitHub Url to your scenario here
https://github.com/blueadamantine/unastoriabelladamorireprologue

I have added this


Fix tab bug by adding functions to set and get active tab from localStorage

@maria-badanina @emma-martin @minamrp hi girls! There was a bug in the tab system and I just fixed it.
The problem was that if the user was on the CV page, and then reloaded the page, the tab changed to Form because it was the default one, but the page was still in CV. Now we only allow the tab to be a link if it's not the active tab, so the user couldn't change to Form because it was the active tab in Main.js state, and therefore couldn't be a link. I fixed this issue by saving the active tab in localStorage in the same function that controls the tab click. Moreover, there's a new function that picks up the active tab from LS and is called in Main.js state to save this value in activeTab. This way, when the user reloads the page, the tab will correspond to the page where it was before reloading!
There's still a minor bug: if localStorage is deleted, form will be the default activeTab, so if the user reloads the page there will be the same problem as before. I think it's not very likely that the user will delete the LS during the same session, so this wouldn't be urgent to solve, but if you have any ideas to fix it let me know!!

WOW! 😲 Awesome job @lauraferrandof! 🤩


User Prefrences for Keyword, intellisense, and datatypecasing ignored

SQL Operations Studio Version: sqlops 0.23.6 (8a3011756318a2ded1e6e84332230a2b2bf9c544, 2017-11-06T21:51:43.232Z)
OS Version: Windows_NT x64 10.0.16299

User preferences for font case are ignored.
Steps to Reproduce:

Edit the following user preferences to be "lowercase"
"mssql.format.keywordCasing": "lowercase",
"workbench.colorTheme": "Abyss",
"mssql.format.datatypeCasing": "lowercase",
"sql.intelliSense.lowerCaseSuggestions": true
Save preferences
Restart SQL Ops

@sebcruz there is a bug where the sql.intelliSense.lowerCaseSuggestions is only recognized as mssql.intelliSense.lowerCaseSuggestions,  This will be fixed in an upcoming release to use sql namespace, but current workaround is to use mssql.  Are the other mssql.format options also not work as expected?

Thanks kburtram.  I added "mssql.format.placeCommasBeforeNextStatement": true to my preferences and the editor respected the setting and will format sql appropriately so perhaps the bug impacts just some of the mssql namespace preferences.


added error raise

I added a check in the substitutions file so any nomial using a substitution method will go through the check. I added the check to the sublinplace function in the costed constraint file so that the substitutions a model tries to use is checked when using subinplace. There are also other changes to the file that I didn't do, I may have pulled an out of date version of the files on accident so they are showing up in the commit as well.

I'm closing this without merging; feel free to reopen if there is a path planned to making it pass unit tests.


GitLab: Support Group-level CI/CD Variables

Describe the solution you'd like
GitLab Provider support for GitLab Group-level CI/CD Variables. Currently, only GitLab Project-level CI/CD Variables are supported.
What is the added value?
The ESO GitLab Provider currently supports Project-level CI/CD Variables only. GitLab supports management of Group-level CI/CD Variables in addition to Project-level Variables. The GitLab REST API manages Group Variables and Project Variables independently. However, GitLab itself and GitLab CI allow Projects to "inherit" Group-level CI/CD Variables to enable variable reuse across Projects. Many existing GitLab CI deployments use Group-level Ci/CD Variables for this purpose.
An optimal GitLab Provider enhancement would behave like the GitLab UI and GitLab CI and expose both a project's Project Variables and its "inherited" Group Variables in a single Secret Store. A less ambitious GitLab Provider enhancement would simply introduce support for Group-level CI/CD Variables. In this case, a separate Group Variables Secret Store and a separate Project Variables Secret Store would be required to use both Project Variables and "inherited" Group Variables.

Very useful feature

I have addressed with https://github.com/external-secrets/external-secrets/pull/1692


Update: Change cask to --cask and formatting md with prettier (fix #208)

Summary

Use --cask instead in Installation
Format markdown with prettier

Reference

Issue #208
Prettier 1.8: Markdown Support

@channprj Thank you for the PR.
I see that you have formatted the README.md file using keystrokes. Can you add the prettier changes to package.json file and update the pr? This way we could automate the md files formatting as well.

@channprj Thank you for the PR.
I see that you have formatted the README.md file using keystrokes. Can you add the prettier changes to package.json file and update the pr? This way we could automate the md files formatting as well.


Deleting a failed environment

I have an environment that I attempted to create, but is in a failed state.  How do I remove the failed environment?
(https://docs.microsoft.com/en-us/azure/machine-learning/desktop-workbench/deployment-setup-configuration)

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

ID: 5904637d-335b-ed1e-2f81-646a3a83a80c
Version Independent ID: 91bd13ab-e31f-9bd9-f869-fa1e9e03000a
Content: Azure Machine Learning Model Management Setup and Configuration
Content Source: articles/machine-learning/desktop-workbench/deployment-setup-configuration.md
Service: machine-learning
GitHub Login: @aashishb
Microsoft Alias: aashishb

@jdobrzen
Thanks for the feedback! We are currently investigating and will update you shortly.

I actually found this shortly after submitting the issue.
https://docs.microsoft.com/en-us/azure/machine-learning/desktop-workbench/model-management-cli-reference


Allow additional interacting taxon ID

This is only used when a curator is annotating an inter-species interaction
This will essentially act as an extra level of partonomy:
CC -po-> cell type -po-> gross anatomical structure -po-> taxon

in practice this will frequently be short-circuited, direct CC to taxon

@thomaspd Can you explain this one

This would be another level of nesting of the CC context.  Right now in the form, it is
MF
part of CC
part of CC
part of cell type
part of anatomy
We would add the ability to include one more level of nesting at the end of that chain:
part of organism
It could be implemented in Noctua form under the ... button at the end of any of the fields above (for example "part of CC").  The text could be "Specify interacting organism".  When the user selects this option, another field is added right under the "part of anatomy" line.  The autocomplete of the new field uses the same closure as the "organism" filter in Amigo.  When making this into a model, you would use the same rule as for the other fields in this part of the form: if there are fields above it that are left blank, you connect it (with part of) to the last one that was filled in (and if none are filled in, it gets connected directly to MF using occurs in).

This is accounted for in the current specs:
https://github.com/geneontology/GO_Shapes/blob/master/shapes/go-cam-shapes.shex

@cmungall @vanaukenk @kltm any idea of how to autocomplete taxon id and short of long taxon names on neo?

I suggest we just do this in a generic fashion. Do not implement any
specific code. Currently the curator must know the 4 letter code but when
we have so many organisms this is unwieldy we will just add synonymy info
to neo
On Tue, Jul 30, 2019 at 3:53 PM Tremayne<EMAIL_ADDRESS>wrote:

@cmungall https://github.com/cmungall @vanaukenk
https://github.com/vanaukenk @kltm https://github.com/kltm any idea
of how to autocomplete taxon id and short of long taxon names on neo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/geneontology/simple-annoton-editor/issues/89?email_source=notifications&email_token=AAAMMOIBMDVJSJPFZ6SWYILQCDA7LA5CNFSM4GP7CMXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3FRMOY#issuecomment-516625979,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAMMOKABGL3Z7HRDUVJJA3QCDA7LANCNFSM4GP7CMXA
.

@kltm - has confirmed that the NCBI slim taxon is loaded in neo.  What is the source of the NCBI slim taxon?
An alternative source of species information is the BioLink API.  The source of data here would be the species list in AmiGO (annotated species OR ontology taxon slim).
Ideally, curators would be able to autocomplete on taxon id or name or substring of a name.
For now, curators will just copy and past the numerical NCBI taxon ID but, in the future, we will implement autocomplete that will show the label.

(Apologies my previous comment didn't make sense as I thought we were
talking about filtering genes by taxon)
taxslim is the subset used by various ontologies for taxon constraints plus
the set used for manual curation in GO. If we want to be sure any taxon can
be used we can just include the full ncbitaxon in the import chain
On Tue, Aug 6, 2019 at 10:45 AM vanaukenk<EMAIL_ADDRESS>wrote:

@kltm https://github.com/kltm - has confirmed that the NCBI slim taxon
is loaded in neo. What is the source of the NCBI slim taxon?
An alternative source of species information is the BioLink API. The
source of data here would be the species list in AmiGO (annotated species
OR ontology taxon slim).
Ideally, curators would be able to autocomplete on taxon id or name or
substring of a name.
For now, curators will just copy and past the numerical NCBI taxon ID but,
in the future, we will implement autocomplete that will show the label.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/geneontology/simple-annoton-editor/issues/89?email_source=notifications&email_token=AAAMMOPNBHKVOEJDULAQS6TQDG2CDA5CNFSM4GP7CMXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3V5QSY#issuecomment-518772811,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAMMOOEX7OHLPZPZQRCFHDQDG2CDANCNFSM4GP7CMXA
.

@tmushayahama - can we close this now that we have organism in the CC annotation extensions on the Noctua 2.0 form?


whether i need to change pdf.js and pdf.worker.js code to support word-searching?

Configuration:

Chrome 75.0.3770.142
Windows 10:
PDF.js 2.0.943:

Steps to reproduce the problem:

Navigate to https://mozilla.github.io/pdf.js/web/viewer.html
2 Type "CTRL+F" to open the find dialog
3 Type "like eat apple".

What is the expected behavior? (add screenshot)
The search result will only contains "like eat apple" can be searched .
but in the pdf.js 1.7.225, The search result will list all contains "like" or "eat" or "apple" or "like eat apple"
What went wrong?
whether i need to change pdf.js and pdf.worker.js code to support word search like pdf.js 1.7.225 version's effect, or i only change to call PDFFindController.executeCommand with phraseSearch: false set in the state object like below:
dispatchEvent(type, findPrev) {
this.eventBus.dispatch('find', {
source: this,
type,
query: this.findField.value,
phraseSearch: true,
caseSensitive: this.caseSensitive.checked,
entireWord: this.entireWord.checked,
highlightAll: this.highlightAll.checked,
findPrevious: findPrev,
});
}

Duplicate of #11002; please refrain from knowingly open duplicate issues!

Indeed, and the solution is outlined over there.


ENH: Custom PDF analytical integral though CDF rather than PPF

Is your feature request related to a problem? Please describe.
When implementing a custom PDF in order to draw random samples like in:
class pos_tanh(st.rv_continuous):
    def __init__(self, m=0, s=1, *args, **kwargs):
        self.m = m
        self.s = s
        super().__init__(*args, **kwargs)

        upper = self.__integral(self.b)
        lower = self.__integral(self.a)
        normalization = upper - lower

        if normalization <= 0:
            log.error('Found normalization {} = {:.3e} - {:.3e}, in range ({:.3e},{:.3e})'.format(normalization, upper, lower, self.a, self.b))
            raise
        else:
            self.normalization = normalization
    #--------------------------
    def __integral(self, x):
        u = self.s * (x - self.m)

        return x + numpy.log(numpy.cosh(u)) / self.s
    #--------------------------
    def _cdf(self, x):
        area = self.__integral(x) - self.__integral(self.a)

        cdf = area / self.normalization

        return cdf

I can calculate myself the integral and implement _cdf. However the generation of samples is extremely slow. Apparently I need _ppf also implemented, which I cannot do easily given that the integral is not invertible:
        u = self.s * (x - self.m)

        return x + numpy.log(numpy.cosh(u)) / self.s

Describe the solution you'd like.
The integral should be all that is needed in the form of a CDF. Why do I have to invert the CDF myself? At the end the only thing you need is the normalization.
Describe alternatives you've considered.
The alternative seems to either invert in an approximate way, which brings numerical precision problems or do the integral numerically, which will be terribly inneficient and slow.
Additional context (e.g. screenshots, GIFs)
No response

Hi @acampove,
If you are using SciPy >= 1.7.0, you can use the new fast numerical inversion method NumericalInverseHermite to draw samples from your custom distribution.
It approximates the PPF using cubic Hermite splines and provides a very fast sampling method. All you need to do is implement the CDF and the PDF method.
import numpy as np
from scipy.stats import NumericalInverseHermite, rv_continuous
from scipy import stats

class MyDistribution(rv_continuous):
    def _pdf(self, x, shape_parameters):
        # implement the pdf here
        return pdf
    def _cdf(self, x, shape_parameters):
        # implement the cdf here
        return cdf

distribution = MyDistribution(name="distribution")
dist = distribution(shape_parameters)  # freeze the distribution

# calculate the PPF
fni = NumericalInverseHermite(dist)

# sample from the distribution
rvs = fni.rvs(100000)

# we can also calculate the approximated PPF
ppf = fni.ppf(np.linspace(0.01, 0.99, num=100000))

# you can also sample quasi monte carlo samples from the given distribution
qrvs = fni.qrvs(100_000, qmc_engine=stats.qmc.Halton(2))

I'm looking forward to using NumericalInverseHermite.
To elaborate on your original post:
To generate random numbers from an rv_continuous you should at least be defining _pdf and _cdf, you didn't define _pdf above.
In order to generate random variables from any rv_continuous distribution a random number is generated in the interval [0, 1). This is then given to rv_continuous.ppf (inverse of _cdf) to obtain the random variate. You don't need to override the _ppf method yourself. However, if you don't override it then the inverse CDF has to be calculated in rv_continuous using a numerical root finding algorithm, which can take a long time. This is just the way of the world, there's no way around it. Or you can use @tirthasheshpatel approach.


bluetooth: fix unchecked return from lll_clk_off in ll_test_end

Inside ll_test_end(), result of lll_clk_off() is not checked
which might result in releasing resources acquired for radio.
Coverity-CID: 190954
Fixes: #13861
Signed-off-by: Maksim Masalski<EMAIL_ADDRESS>

Codecov Report

Merging #14020 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #14020      +/-   ##
==========================================
- Coverage   52.27%   52.24%   -0.04%
==========================================
  Files         307      307
  Lines       45467    45467
  Branches    10525    10525
==========================================
- Hits        23768    23752      -16
- Misses      16901    16913      +12
- Partials     4798     4802       +4

Impacted Files
Coverage Δ

subsys/testsuite/ztest/include/ztest_assert.h
38.88% <0%> (-38.89%)
:arrow_down:

subsys/testsuite/ztest/src/ztest.c
65.28% <0%> (-7.44%)
:arrow_down:

Continue to review full report at Codecov.

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

Hey @maxxlife , thanks for your patch. I think you committed the changes in separate commits by mistake. To correct this you can squash your commits doing:
git rebase -i upstream/master
and then following the instructions given by Git.
Once you have rebased you can force-push to your branch with:
git push -f origin

Should it be an assert though, or propagate the error upwards by returning error?