Add offer_deferred status

Context
Providers need to be able to defer offers to the next recruitment cycle.
Changes proposed in this pull request

Add a new offer_deferred status to the Application Choice
Add rules to the state machine

Only applications that are in 'Offer accepted' (pending_conditions) and 'Conditions met' (recruited) can change to offer_deferred
From offer_deferred we can go back to recruited and pending_conditions states and withdrawn as candidates should be able to withdraw

Update status tag components
Update support documentation
Update performance statistics
Hide deferred applications from the API

Guidance to review

Check preview for each interface eg: http://localhost:3000/rails/view_components/provider_interface/application_status_tag_component/offer_deferred

Check provider and candidate application flows: http://localhost:3000/support/provider-flow

Not sure about the way of hiding deferred offers from the API.

Link to Trello card
https://trello.com/c/UeS5yjDh/2689-add-offerdeferred-status
Things to check

[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] API release notes have been updated if necessary
[ ] New environment variables have been added to the Azure config

It's possible to crash the app by putting an application in offer_deferred state and trying to visit it. Fixing.


tracking issue for full unleash of DefaultConfig for FRAME

https://github.com/paritytech/substrate/pull/13454 will bring in the basic functionality needed to start using this feature. See this example to learn more.
This will mark the first version of this work complete, but a lot has to be done in order for it to be fully complete.
Improve Error Handling, Bugs

[ ] Improve error handling. There seems to be an error in the parse/config.rs file that allows #[pallet::whatever] to be parsed and ignored in #[pallet::config]. This has to be fixed.
[x] Properly hide __export_tokens_tt_test_default_config and similar from docs.
[ ] Handle pallet instancing.

Full usage in Substrate Pallets

[ ] migrate the docs for derive_impl to use real code. As all of this functionality can work on normal traits, and as per #14115, we should strive to make the docs of derive_impl be real rust code. We might even want to remove ./frame/example/default-config in favor this.

Provide testing defaults for common pallets

[x] System: already provided
[x] Balances https://github.com/paritytech/substrate/pull/14453
[ ] Timestamp
[ ] ...?

Then, we should start migrating existing pallets and their test setup to use the unified testing prelude of system, balances and so on. Here's a tracking list:

[ ] alliance
[ ] asset-conversion
[ ] asset-rate
[ ] assets
[ ] atomic-swap
[ ] aura
[ ] authority-discovery
[ ] authorship
[ ] babe
[ ] bags-list
[ ] balances
[ ] beefy
[ ] beefy-mmr
[ ] bounties
[ ] child-bounties
[ ] collective
[ ] contracts
[ ] conviction-voting
[ ] core-fellowship
[ ] democracy
[ ] election-provider-multi-phase
[ ] elections-phragmen
[ ] executive
[ ] fast-unstake
[ ] glutton
[ ] grandpa
[ ] identity
[ ] im-online
[ ] indices
[ ] insecure-randomness-collective-flip
[ ] lottery
[ ] membership
[ ] merkle-mountain-range
[ ] message-queue
[x] multisig https://github.com/paritytech/substrate/pull/14453
[ ] nft-fractionalization
[ ] nfts
[ ] nicks
[ ] nis
[ ] node-authorization
[ ] nomination-pools
[ ] offences
[ ] preimage
[x] proxy https://github.com/paritytech/substrate/pull/14453
[ ] ranked-collective
[ ] recovery
[ ] referenda
[ ] remark
[ ] root-offences
[ ] root-testing
[ ] salary
[ ] scheduler
[ ] scored-pool
[ ] session
[ ] society
[ ] staking
[ ] staking-bags-benchmarks
[ ] state-trie-migration
[ ] statement
[ ] sudo
[ ] system
[ ] timestamp
[ ] tips
[ ] transaction-payment
[ ] transaction-storage
[ ] treasury
[ ] try-runtime
[ ] uniques
[ ] utility
[ ] vesting
[ ] whitelist

Full Usage in node-template-runtime and parachain-template-runtime
We should provide runtime templates that utilize this, evangelising its usage. This requires us to carefully consider what is a reasonable default for a node template in order to use. We should provide possibly two new preludes:
Full usage in westend -> kusama -> polkadot runtimes.
Once we have are more and more confident in both the core functionality, and our skills to define sensible defaults, we can slowly start migrating perhaps some of the configs define in Polkadot to use this feature.
For security reasons we should be super caution here. Adding #[derive_impl] will open the door for upstream changes manipulating the configurations used in the Polkadot runtime. Perhaps we should only ever do this once we have more tooling that could notify us of unexpected upstream changes to config_preludes.
I would personally find it reasonable to never use this feature in production runtimes for this reason.
V2
At the moment, the system that is introduced is has some limitations. Most notably:

[x] it cannot provide default for types that are reliant on types that are themselves reliant on frame_system::Config. For example, a type Admin: Get<Self::AccountId> cannot have a default. Is is mainly because trait DefaultConfig is not in itself trait DefaultConfig: frame_system::DefaultConfig. Moreover, sadly, because the definition of BalanceOf<T> (somewhat needlessly) also relies on frame_system::Config::AccountId, anything akin to Get<BalanceOf<Self>> can also not have a sensible default.  https://github.com/paritytech/substrate/pull/14453

I believe this is father easy to fix, by standardizing frame_system::DefaultConfig and making trait DefaultConfig: frame_system::DefaultConfig.

[ ] If the above is done, we are only left with types that cannot really have a default in any pallet. Such types are: PalletInfo, RuntimeEvent, RuntimeCall and such. Such types can also be mocked but they require more coordination with construct_runtime!. A new attribute can mark these types simply as #[derive_from_runtime] or similar, which would mean they are expected to be found in the existing scope with the same name.

Other approaches could be explored for the last step, as I am not quite sure what is the best way forward.

it cannot provide default for types that are reliant on types that are themselves reliant on frame_system::Config. For example, a type Admin: Get<Self::AccountId> cannot have a default. Is is mainly because trait DefaultConfig is not in itself trait DefaultConfig: frame_system::DefaultConfig. Moreover, sadly, because the definition of BalanceOf<T> (somewhat needlessly) also relies on frame_system::Config::AccountId, anything akin to Get<BalanceOf<Self>> can also not have a sensible default.

Personally I would say that we do this before we do all the other things, otherwise you will start changing all this code twice. I already left a comment here on how it could work: https://github.com/paritytech/substrate/pull/13454#issuecomment-1495855632
In general to this feature, I had some idea recently which could improve the versioning around our crates. Currently when we are adding a new type to a Config trait it requires that we bump the major version of the crate. If we have the system outlined here working and it is being used everywhere. (I would even go that far and say it is fine to use it in production runtimes, at least having the attribute above each Config implementation) Then we could introduce some kind of "versioning" of these Config traits. Then every time you would add a new config type, you would bump this version in your pallet. We would then only require to bump the minor version. Downstream users would then at some point bump the pallet minor version. It would still compile, because the attribute above the impl Config would put there some safe/secure default value. But it would also generate a warning that tells the user that it put there some new type. It could even show some more context to the new type added. The user can accept the new safe default value by bumping the "trait version to use" or they just add the type on their own and bump the trait version in use.
Not sure if this idea is something we should really do, but I wanted to leave it here :P

is the parse issue still present with #[pallet::whatever]?

potential vast improvement: https://github.com/paritytech/substrate/pull/14437#discussion_r1251861668


Investigate values on frontend server stdout stream.

There are some crash reports with message being null here:
https://github.com/flutter/flutter/blob/v1.7.8-hotfixes/packages/flutter_tools/lib/src/compile.dart#L99
This needs investigation. Is null a value on the stream that should just be ignored, or is there a deeper problem.
So far this is 17.2% of tool crashes in 1.7.8+hotfix.3. This crash was not present in the last stable release.

Currently investigating, not certain of the cause yet.

I investigated a bit from the tool side of things - I don't see any obvious places where we would be inserting a null ourselves, as this should come more or less directly from stdout/utf8.decoder/linesplitter.
@aam could you advise on the best approach here? Should we be ignoring these values or treating them as an exception from the frontend_server

Not sure what a null from LineSplitter from process stdout might mean besides something being wrong with the process and its stdout. I don't think they should be ignored.
Are we able to reproduce this?
Running in verbose mode should print all frontend server communication, hopefully provide clues to what precedes those crashes.

It looks like the null is occurring in/around when the frontend_server is reporting a compilation error

After further investigation we found that this error is not caused by a null value returned from the frontend_server. Instead I suspect this happens when a compilation or evaluation request receives partial output from a previous message. This places the stdout state machine in an invalid position, where we don't know what boundary key to look for.
The frontend_server requires that we serialize the requests and maintain the ordering on our own in the tool. For the most part it looks like we're doing this correctly, but there might be a case where we're missing an await or otherwise starting a new request before a previous value completed.

#37743 fixes a bug which is consistent with the errors returned here, involving the tools's frontend_server state machine going into a bad state. To confirm this hypothesis, we'll be monitoring the next dev release which should contain the fix

Still awaiting dev release.

We've seen this error occur after the fix in master, so it is back to square 1.

Update: At this point we're going to need to wait for more information in order to identify a fix. I'm also investigating alternative structural changes to how we interact with the frontend server should no fix become apparent.
Based on this information, I'm updating the milestone to nearer to the end of Q4, since I don't expect to take any further action for the time being.

Hello,
What else can I do to help you get more information about this issue other than the following?
Compiler message:
lib/main.dart: Error: Can't access platform private library.
The Dart compiler encountered an internal problem. The Flutter team would greatly appreciate if you could leave a comment on the issue https://github.com/flutter/flutter/issues/35924 describing what you were doing when the crash happened.

I was wrapping an Expanded around a custom widget that is essentially a heavily styled scrolling ListView when this occurred.

It's not consistent, no. If there is any other information I can get you when it happens again, let me know though.

@afabbro It would be worth know what you were doing when this showed up - like, did you hot reload invalid code or added a new import et cetera, or if you were doing nothing out of the ordinary.

Hi, just got this crash when trying to hot reload this bad code:
Compiler message: lib/homerearrange.dart:179:6: Error: Expected ';' after this.     })

The errors might be related to the fact that output from compiler when processing 'reject' request is not properly enclosed into result boundaryKey...boundaryKey: https://github.com/dart-lang/sdk/blob/master/pkg/frontend_server/lib/frontend_server.dart#L928

Potentially fixed by https://dart.googlesource.com/sdk/+/efbfda2e6dcf47df302891109ddde0d1f8bf9577

We think the above fixed the issue, so until we hear more I'm going to close the issue. For now, we should leave the bad state handling code in the tool in case we regress elsewhere

This issue has been closed for a while, but I encountered an error today that asked me to leave a comment here:
Launching lib/web_benchmarks.dart on Web Server in debug mode...
The Dart compiler encountered an internal problem. The Flutter team would greatly appreciate if you could
leave a comment on the issue https://github.com/flutter/flutter/issues/35924 describing what you were
doing when the crash happened.

Additional debugging information:
  StdoutState: StdoutState.CollectDiagnostic
  compilerMessageReceived: false
  _expectSources: true
  sources: []

Syncing files to device Web Server...

I was running the web benchmarks locally using:
flutter run -d web-server --web-port=8888 --local-engine=host_debug_unopt lib/web_benchmarks.dart

FWIW, the error disappears if I add the --profile flag which goes through dart2js instead of DDC.

I recently added a new argument to the frontend-server, --libraries-spec, to fix the config specific import issue I re-introduced when switching the compilers. If you were on a version of flutter that had this flag, but a version of the engine that didn't, it could cause this crash at startup

I pulled flutter master and engine master, and things seem to work now. Thanks @jonahwilliams!


Inés Feedback - Website Structure

Structure

Although obviously it is just launched and there is less content to find, but as you build up a library of it I think it will be helpful to have an obvious place to easily search and access particular entries.  {I am thinking very Wordpress-like here, but I realise this is built in GitHub, so I admit I don't know how adaptable it is and if this is just because I'm used to traditional blog/Wordpress powered-looking sites)
You could achieve this by having a top or side bar, where you could have different themes such as "MumsRockTech", "OnesToWatch", "WeRockTech" - maybe have them display snippets and the teaser video in the short version they display, and when clicking Read More, to display the full episode. If each entry has a category and/or tag, it can help with search too. An archive page is a good idea too. :)
At first I found the Future Episodes a bit confusing, as I was expecting the sidebar to have quick links. I think it is nice to have an area to show what's to come, but it's a slight overload of information. I could recommend either having a tab that goes to "coming up next...", or a snippet in side bar saying "Up next week: Kimberley Cook", or each of the names displayed and when they're clicked on the full bio is displayed underneath.

Started addressing point 3 in #12

Started addressing point 2 in #15

Series filter mentioned in point 2 addressed in #18


Create a panel for subtitles for spoken text

While units will be speaking, subtitles need to be shown to make it easier to understand.
Need to create a panel that will be in the bottom portion of the screen, slightly above the abilities UI. The panel will include:

The portrait of the unit's speaking.
The name of the unit's speaking.
The sentence it is currently saying.

The panel should be not visible by default, and will show up and be hidden by using events.
This needs to be done by two portions:

Design: Need to design the panel and its portions. We can use design from similar games, such as WC3, while still using Dota themed panels.
Functionality: Need to hook the panel into events that the server calls, such as showing the text, the portrait, the name of the unit, and whether the panel should be visible or not.

Implemented in https://github.com/ModDota/dota-tutorial/pull/74


Grails 3.x version

The plugin has been very useful with grails 2.
Is there a grails 3 version on the roadmap?

IS there plan to upgrade the plugin to grails 3 officially ? -- or i can branch it, put efforts to upgrade and release a grails 3 version myself ?

Hi, we're currently not putting more efforts into the plugin but I would love to help if someone is committed to migrate it to version 3.x
I think there are several challenges because a lot has changed.

I would be happy to migrate the plugin to grails 3... i will keep u updated of progress.

@Alotor i got the basic functionality working with grails 3 -- here's my branch -- https://github.com/snimavat/grails-admin-interface/tree/grails3
I will be working on it to get it working properly with grails 3, and i have plan to refactor few things, make it lil more customizable and add few new features

@Alotor there's one javascript file missing grails-admin/js/widgets/relationpopup.js and browser complains about that, does this file even expected to exist ? i think it needs to be removed from widget js ?

Thansk a lot! I'll try to check this today. The script missing was replaced when we separated the relationship in several widgets. The first version there was only "one to many" relationships (if memory serves) and then we created one for each type.

@snimavat can you open a Pull Request so I can comment and push my own changes?
Looks very prominsing bug I've found some issues with the static resources. Moving them to src/main/resources/public instead of src/main/webapp seems to do the trick but then is necessary to change more things in the resolution.

@Alotor do you have plan to maintain and ehance the plugin ? Otherwise i can publish the new version from my repo and i have plan to support and maintain it for a long time.

@snimavat @Alotor Hi guys, I would like to try Sudhir's grails3 plugin. What is the best way to do that?

@edwardotis i have one package published here, the source is in my fork.
No, i have not made changed to static resources...
Note: even though the plugin would work with grails 3 (i tried it, works almost, but could be some bugs).. i dont plan to maintain it forever.... but if u want to start working on it, start with my fork and u should have a working grails 3 version

Thanks, I'll see how it works with my domains and use cases

@snimavat  The dependency is not resolving with my usual repos .
What do I need to add for it to pickup https://bintray.com/snimavat/grails-plugins/grails-admin-interface ?
repositories {
    mavenLocal()
    maven { url "https://repo.grails.org/grails/core" }
    mavenCentral()
    jcenter()
}

And:
   compile 'grails.plugin.admin-interface:grails-admin-interface:3.0.1.RC1'
Error
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'grails_server3'.
> Could not resolve all dependencies for configuration ':runtime'.
   > Could not find grails.plugin.admin-interface:grails-admin-interface:3.0.1.RC1.
     Searched in the following locations:
...
         file:/home/me/.m2/repository/grails/plugin/admin-interface/grails-admin-interface/3.0.1.RC1/grails-admin-interface-3.0.1.RC1.pom
         file:/home/me/.m2/repository/grails/plugin/admin-interface/grails-admin-interface/3.0.1.RC1/grails-admin-interface-3.0.1.RC1.jar
         https://repo.grails.org/grails/core/grails/plugin/admin-interface/grails-admin-interface/3.0.1.RC1/grails-admin-interface-3.0.1.RC1.pom
         https://repo.grails.org/grails/core/grails/plugin/admin-interface/grails-admin-interface/3.0.1.RC1/grails-admin-interface-3.0.1.RC1.jar
         https://repo1.maven.org/maven2/grails/plugin/admin-interface/grails-admin-interface/3.0.1.RC1/grails-admin-interface-3.0.1.RC1.pom
         https://repo1.maven.org/maven2/grails/plugin/admin-interface/grails-admin-interface/3.0.1.RC1/grails-admin-interface-3.0.1.RC1.jar
         https://jcenter.bintray.com/grails/plugin/admin-interface/grails-admin-interface/3.0.1.RC1/grails-admin-interface-3.0.1.RC1.pom
         https://jcenter.bintray.com/grails/plugin/admin-interface/grails-admin-interface/3.0.1.RC1/grails-admin-interface-3.0.1.RC1.jar

@snimavat And regardless, could you submit a pull request to the kaleidos project so that @Alotor can comment and merge his 3.x fixes?

You need to add maven repo
 maven { url "https://dl.bintray.com/snimavat/grails-plugins " }

compile 'grails.plugin.admin-interface:grails-admin-interface:3.0.1.RC1'

PR done

Thanks, that fixed the dependency issue for me. That additional repo requirement might be good to add to the README

@snimavat Hi, I'm getting 500 errors when I navigate to the /admin, /admin/list/<some-domain., and /admin/add/. Can you enable Issues on your fork so I can post you the stacktraces?

ok


Using with Nullable{Function}

How can I create a Nullable{Function} anon-ized anonymous function?
julia> VERSION
v"0.3.6"

julia> using Compat

julia> using FastAnonymous

julia> f = @anon x -> 2*x;

julia> Nullable{Function}(f)
ERROR: `Nullable{Function}` has no method matching Nullable{Function}(::Type{##23149})

f isn't a function. Use Nullable{typeof(f)}(f).

Thanks. That's a bit annoying. My use case is to pass an anonymous function to a type constructor that expects a Nullable{Function}. What's the best resolution? Change it to Nullable{Union(Function,DataType)}?

Yes, you have to broaden the type signature of the code that uses this. There's no way (yet) to make it a function and get good performance; this uses a trick of building a special-purpose type.
I did something like this in https://github.com/JuliaLang/julia/pull/10314, perhaps it will help you see how to do it.

Many thanks. My initial interest in FastAnonymous was for something like this:
using FastAnonymous
n = 5000;
M = sprand(n, n, .8);
prod = @anon v -> M * v;
# prod = v -> M * v;

v = rand(n);
u = prod(v);
@time u = prod(v);

But I'm not seeing any time difference. Is that expected?

Yes. All the time spent in your computation is in the matrix multiply. FastAnonymous helps only when the overhead of the function call represents an appreciable fraction of the time. Think about it this way: there's a bit of overhead to "launch" an anonymous function call, but once it gets launched, it's running at full speed.
The other thing to note is that the main point of the package is when you pass a function as an argument to some other function. You'll never notice the overhead of a single call at the REPL.

You're right. My test is too simplistic. My application is to pass the anonymous function to another function. I'll have to implement the whole thing to find out. Thanks again.

I don't think there's anything actionable here, so I'm closing.


allow OpenStruct to be validated as an object

Fairly self explanatory.
Sorry there aren't any tests, I tried to write some but the metaprogramming in test/support/type_validation.rb got in my way, don't have time to mess around with it atm, sorry :(

just spotted my hideous error, fixing it now...

I'm not really in favor of supporting another type as object. We recently decided that we want to keep the library clean and slim (which is why e.g. symbol support will be dropped in the next major release) and this would be a step in the opposite direction.

Yes, I agree with @RST-J - I'd recommend ensuring that your hash is valid JSON (by using #to_json) before validating

Fair enough, that works for me.


Worldinfo hex compatibility

world info added to bots
hexagon grid

GitHub is confused? This PR has been merged, but GitHub doesn't seem to be aware... Closing.


Fix issue #87 & #88

This PR fixes issue #87 and #88 and also provides an alternate UI for the leader-board page. The profile page also has been modified a little.
The page can also be converted to figma design if wanted.

@just-ary27 can you please take a look at https://github.com/Bugheist/Flutter/issues/91 the build is not running all the way through because of this

@fredfalcon I've addressed the issue in #92


ConscryptPlatform platform should not globally configure Conscrypt.setUseEngineSocketByDefault

What kind of issue is this?

[x] Bug report.

ConscryptPlatform.buildIfSupported() globally sets Conscrypt.setUseEngineSocketByDefault(true), which causes HttpUrlConnections used across the jvm to behave differently (connections external to okhttp, okhttp itself works fine). In my case I'm seeing socket timeouts causing tests to fail where there aren't problems with setUseEngineSocketByDefault disabled.
Proposed Fix:
We can invoke Conscrypt.setUseEngineSocket(SSLSocketFactory, true) on the SSLSocketFactory instance rather than setting global configuration.

Just saw this issue. It might be also worth reporting to the conscrypt project.

cc @flooey
@yschimke the FD and engine-based sockets do differ WRT detection of the underlying socket closure. when wrapping another socket.  The FD socket cheats by obtaining the underlying FD for the wrapped socket and detecting when it is closed.  The engine-based socket relies on operations of the wrapped Java socket to fail, which can take a while depending on the configuration.


responsive for different screen sizes

I saw that it's working fine for mobile device, but still for some sizes of screen, it's not quite responsive, here I attached a screenshot:

when screen width >900 px, it becomes not responsive.

I see the issue, could you make the css for 'for-toolbar > for-pc > ul' that has this attribute:
{flex-wrap: wrap} so that it will be more responsive? thanks

Update to the latest version, it has been solved

If you find again, please leave the version

hi, for 2.3.2 version, I see the issue is still there like

For screen width >900 width, it becomes like this.

add a {flex-wrap: wrap} to the .ul class will solve this issue I think.

ok, I will fix this soon.

Please update to the latest version, and check if it is ok

yes it's not overflowing out of the box now, it's now looking like this, it may be optimized later when you have plenty of time to do so


Fix default user role

Default role is set to ANONYMOUS where as it should be user

Fixed the Default user role to USER
Please find below pull request for the same
https://github.com/njit-dl92/event_manager/pull/5


STAC 1.0.0 support

Add new extensions (raster, community extensions, ...), see #9
Basic Support for JSON Schema in summaries, see #7

Issues above are already tackled by other issues.


Would be nice to choose or automatically detect which entity or entitites have changed

The issue
JHipster-UML has helped me a lot since its first release. But keep the data model over the time with this tool bring some extra work and then you start to spend all time saved during the data model start.
What really bothers me is once you change something on your entity (add a new field for example) it passes over all the other entities (that has no change at all) and makes you answer 'no' for everything because you have a lot of customizations.
Am I doing something wrong or it can become an issue and perhaps become a new feature for a new version?

I noticed some problems with the checks, but I have to test your problem.

I don't have this issue... what version of JHipster UML are you using?

v1.6.1, the latest.
Does it just try to change the entities you changed? Because what I tried to explain is that it will try to change any other entity if the files are not the same as generated, if you have customizations it will ask if you want to change or not. What I told that can be nice to have is to select what are the entities you have changed and you want to update (if it could be automatically chosen would be great).
When you have too many entities and customizations it is very difficult to keep the JDL file updated. What I do is too change directly in the json file and run the jhipster:entity again for the entities I have changed.
My goal here is to keep the maintenance of my data model on the JDL. This is a great tool and can make easy documentation lifecycle.

Oh! I didn't understand that! It's a good idea =)
I'll see about adding it in v1.6.2 or v1.6.3.

I was wondering... one thing you can do is, first check if there is a change on the entity.json, if there is not, don't try continue the jhipster:entity sub-generator.

I've finished implementing the new system, I'll add the option to select which entity to update later this week. And then I'll release after moving Visual-Paradigm away from this project.

Finished, and improved (992dd30).


MetaRewriter is no longer correctly replacing title and description

Meta tags are currently receiving default values from Notion, e.g.:
<meta name="twitter:site" content="@NotionHQ">
<meta name="twitter:title" content="Notion – The all-in-one workspace for your notes, tasks, wikis, and databases.">
<meta name="twitter:description"
  content="A new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team">
<!--- ...  -->
<meta property="og:title" content="Notion – The all-in-one workspace for your notes, tasks, wikis, and databases.">
<meta property="og:description"
  content="A new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team">

Which leads to SEO issues:

The problem is  likely happening at: https://github.com/velsa/notehost/blob/d227b8c2fbef34644cc337af9f327a40f41da289/src/rewriters/meta-rewriter.ts#L23-L24
Which gets used at:
https://github.com/velsa/notehost/blob/d227b8c2fbef34644cc337af9f327a40f41da289/src/rewriters/meta-rewriter.ts#L29-L35
And:
https://github.com/velsa/notehost/blob/d227b8c2fbef34644cc337af9f327a40f41da289/src/rewriters/meta-rewriter.ts#L41-L50
A quick and dirty workaround is to use siteName and siteDescription instead of content for all pages. A more flexible solution would be to parameterise slugs with optional custom titles + descriptions, falling back to siteNameand description:
  siteName: 'My Notion Website',
  siteDescription: 'Build your own website with Notion. This is a demo site.',
  // Should replace twitter:site
  siteTwitter: '@MyHandle'

  slugToPage: {
    '': 'NOTION_PAGE_ID',
    about: 'NOTION_PAGE_ID',
    // Both pages above will fallback to siteName + description
    contact: {
      id: 'NOTION_PAGE_ID',
      title: 'Contact form',
      description: 'Bla bla bla',
    },
  },

Bonus, we should probably prepend https:// to the domain at:
https://github.com/velsa/notehost/blob/d227b8c2fbef34644cc337af9f327a40f41da289/src/rewriters/meta-rewriter.ts#L52-L54

Since the 2024-06-25 update (https://www.notion.so/releases/2024-06-25), when a page is configured to be "Discoverable on the web", Notion now sets:

Titles ending in "| Notion"
Clean descriptions taken from the first text block on the page
A "good" default image (e.g., page cover)
No longer sets twitter:site to @NotionHQ

So, most of the problems mentioned above should be fixed now. Nevertheless, customising meta tags is a premium feature, so I think we can still make good use of this PR. I'll update it to fallback to the old behaviour of extracting content from Notion when pageMetadata is not specified.

Thanks for the pull request!
Merged it with a small refactoring.
Now version 1.0.31 is the latest one containing your PR.

Hi @velsa,
Many thanks for merging and refactoring the PR, as well as for the amazing software.
I've updated my site to use the latest version  and can confirm that custom metadata is still reported correctly when visiting the site with Googlebot and Bingbot user agents (i.e., Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) [Chrome/W.X.Y.Z](https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers#user_agent_version) Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) and Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) Chrome/).
Apparently, https://velsa.net/ is reporting a 404 when using one of the agents. Have you toggled the "Discoverable on the web" option off by any chance?
Finally, a non-important detail, but given Notion's update mentioned in https://github.com/velsa/notehost/issues/36#issuecomment-2195560337, I don't think that lines 98 and 100 bellow are necessary anymore: https://github.com/velsa/notehost/blob/811088548ab07daf71e78e507fcfc02c03fa0d9b/src/rewriters/meta-rewriter.ts#L96-L101
Line 99 is still required for the title, and if you ever decide to change the code to not replace og:site_name unconditionally, you may also want to replace ' on Notion'.


Add logging to cli

This PR adds logging capability to cli commands for split and join, as well as a minimum set of logging info from the underlying packages.
Perhaps the single most annoying thing in the world is when it is impossible as an advanced user to get contextual information about what a tool does, at a minimum if it has understood the input parameters passed to it. Let's not be annoying.

why on hold?

@acud because this first: https://github.com/ethersphere/bee/pull/251

@acud because this first: #251

what's the connection between the two? is this pr going to redo the logging on all of those binaries too then?

Yeah I'd rather just do it on top.

obsoleted by https://github.com/ethersphere/bee/pull/251


Configuration files???

soo what is your plan for configuration files, .cfg or .lua files???

Sorry for the late response. What do you mean exactly by configuration files? For building, theming or something else?

for now I think .ini files are ideal for this

is there gonna be some kind of documentation for configuring the editor?

for color themes probably. for general settings there will just be an easy to use gui window in the editor that writes to the file

pretty nice, this is using imgui so probably imgui colors right?

pretty cool 😎

pretty cool 😎


Improve formatting

This was annoying me. I didn't look into it much, but this should work.

You need to update the expected test outputs.

removing some fernflower charm here, that'd be the end of an era :3

Oops! This was just a quick fix with no understanding of how the code actually works.
Tests are passing now.

I hope this can make it soon this looks wonderful

Thanks for this! I'll integrate it and resolve the issues.

I'm sorry for not getting it to work :P. It worked fine locally which is weird!

Nah, it's all good! Updating all of the tests is fairly tedious, but I have a system to fix that automatically so I wanted to go ahead and apply that 😄

Yayy!


LINK-1754 | Modal before reservation time is expiring

Description

Display accessibility notification after loading reservation timer. Text tells to user how much time there is to register.
Display modal if registration time is expiring soon

Closes
LINK-1754
Screenshot

LINKEDCOMPONENTS-UI branch is deployed to platta: https://linkedcomponents-pr368-ui.dev.hel.ninja :rocket::rocket::rocket:

e2e tests result is success for https://linkedcomponents-pr368-ui.dev.hel.ninja :laughing::tada::tada::tada:


Notification that Configure Failed, Debug with CMake Debugger shows up when you override a Configure with a Build

Brief Issue Summary
When a CMake Configure action is running, and you override with a Build action, I get an error that Configure Failed, Debug with CMake Debugger. Ideally, this would not surface to the user, since nothing "failed".
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response

There should also be a way to disable the pop-up for legitimate cases.

@cjdb Thanks for the suggestion. Could you elaborate some on what you mean by "legitimate cases"? It'd be great to understand any and all cases where we should allow this.

That would be whatever the reason the popup was designed for.

There should also be a way to disable the pop-up for legitimate cases.

Agreed 💯, that pop-up is extremely annoying. There should be an option to disable it.

The same error pops when I cancel configuring (#3472).

The "Do not show again" button doesn't appear to have any effect. I still get the pop-up even after pressing that button (I've run CMake twice in a row after pressing the button to see if a change in my environment is the culprit, and it is not).

@cjdb Also, what operating system are you on?

If you search for cmake.showConfigureWithDebuggerNotification in your settings, could you tell me what you see? I've just tested on the most recent pre-release whether this takes affect, and I've confirmed (for my repro) that it does take affect. I'm wondering if there is some settings issue that is happening?

That setting isn't present in my settings.json.

@cjdb Also, what operating system are you on?

Arch Linux. I've also run the following, which may be relevant too?
$ code --version
1.86.1
31c37ee8f63491495ac49e43b8544550fbae4533
x64

Update: I see "cmake.showConfigureWithDebuggerNotification": false on my work machine, which runs macOS. Perhaps my Arch VS Code build is out-of-date.

@cjdb It might not be in your settings.json yet, but if you search for it in the global settings UI, you should be able to find it.
Could you check there?

Yep, it's there. Looks like the global settings UI is having difficulty writing to my settings.json, but I've been able to write to that manually, which seems to have solved my problem :)
My guess is that I've got a permissions issue or something, but that's out of scope for the bug!


Use the current branch or master as the global donejs binary

That way we will catch problems with the global DoneJS before it is published to npm.

Coverage remained the same at 96.226% when pulling 2b828adadb34fb989ed8433c7040d8e4bf5a86c0 on guide-test-branch into de0bc2edb6b662a0452f59d8bd0cba37bce2082b on master.

Coverage remained the same at 96.226% when pulling 2dd6935ddddbb4b582a860fd4a0a285ea9baf373 on guide-test-branch into de0bc2edb6b662a0452f59d8bd0cba37bce2082b on master.

Coverage remained the same at 96.226% when pulling 175deeb0a195669fdaf0713bf21a3960851c887d on guide-test-branch into a7b82658f82f27ebc289e31a6589596cd5eae982 on master.

Coverage increased (+0.04%) to 96.262% when pulling 11d84c68fe982a1d68b328a1e760fe8656dd15d8 on guide-test-branch into a7b82658f82f27ebc289e31a6589596cd5eae982 on master.

Coverage increased (+0.04%) to 96.262% when pulling 2af824292526c23e277a29030657cc1e2762e198 on guide-test-branch into a7b82658f82f27ebc289e31a6589596cd5eae982 on master.

@daffl Only the appveyor PR is failing now, it's because it is using a7b82658f82f27ebc289e31a6589596cd5eae982 instead of this branch (I guess the PR always does this?)  I think if we merged this everything would then be passing in master.


Bulk upload: suggest names, generate usernames

This (hopefully) fixes #623 (see https://github.com/swcarpentry/amy/issues/623#issuecomment-166152983). And this fixes #526.
For details, see commit messages.

Usernames are sometimes also used as filenames (e.g., for the _include file in the main website with the person's biography, and as the stem of the PDF certificate name for instructors). Since some Unix command-line tools still have trouble with non-7-bit characters, we want usernames to be 7-bit, e.g., lacera.ana instead of laçera.aña. Since the mapping from accented or non-Latin characters to Latin characters is tricky, it seems simpler to allow editing of the computer-generated username during upload.

@gvwilson:

Usernames are sometimes also used as filenames (e.g., for the _include file in the main website with the person's biography, and as the stem of the PDF certificate name for instructors). Since some Unix command-line tools still have trouble with non-7-bit characters, we want usernames to be 7-bit, e.g., lacera.ana instead of laçera.aña. Since the mapping from accented or non-Latin characters to Latin characters is tricky, it seems simpler to allow editing of the computer-generated username during upload.

This is convincing. I could add a regex check for non-ASCII characters.
I'll also introduce this change to the way username field works:

if there's no matching person (== we'll add a new person and a new task to the database), the field will be editable
if there is a matching person (== we'll only add a new task to that person), the field will not be editable

Sounds good?

@gvwilson updated!

OK, if I understand the logic correctly now, :+1: to merge - but man, this is becoming complicated...

@gvwilson:

OK, if I understand the logic correctly now, :+1: to merge - but man, this is becoming complicated...

Yep, every removed bit counts, even something as small as ditch of middle field.


[release-4.11] Bug 2119607: Env save button fix

📝 Description
Cause
Save button enabled and disabled at the wrong moment. Don't use index to compare new and old envs array. The update can change the order

/bugzilla refresh

/bugzilla refresh

/lgtm


Add code to simulate actual microscopes

The code as it currently is only simulates the wavefront a the camera in a widefield/epi scope, but with a few modifications multiple different microscope PSFs (and OTFs) can be modeled. The following should be doable

[x] Epi
[x] Confocal
[x] Apotome (approximation of non-linear function, i.e. no real OTF for this reconstruction method)
[x] SIM (of all varieties)

[x] OS-SIM
[x] 2D-SIM
[x] 3D-SIM & (Zeiss Lattice SIM)

Will update README.md to reflect this

Just saw these recently added notebooks.
These are a great resource, thank you !


eclipse-logan

Hello! In my artwork I have created a depiction of the upcoming North American Eclipse on April 8th! I have some coding experience as I am in high school and have taken an introductory course. The blot API was easy to understand and develop your own intuition in building features. I built a program for the Sprig project before and I can say the improvements to the website are great, the IDE is simple to use and the cloud saving is a wonderful feature. I hope you enjoy my artwork!

Thanks for the submission! I think you could add one more artistic element before we merge. How about trying to capture the light that emanates from the edges of the eclipse. How could that be done?

Thank you for the suggestion! I have committed the changes(I believe), and now there should be sun rays that display based on the percentage of eclipse variable. Let me know if theres anything else I need to do before submission.

Hi there! This looks pretty cool.
A couple points of feedback for the rays. For the full coverage ecplise, it would be cool if it looks something like this:

Also for the partial coverages, I think it would be cool if as theres less and less coverage, more and more rays appear, instead of having just 3 rays that get larger.

Also, can you complete the header with
/*
@title:
@author:
@snapshot:
*/
That would be greatly appreciated

Thank you for all your suggestions! I've added them to the best of my ability, the rays now disappear and reappear depending on the coverage, along with a special display for the totality, I made the time change based on the percentage, and finally fixed the header like you asked. Thanks for all the tips.

Also, can you complete the header with /* @title: @author: @snapshot: */ That would be greatly appreciated

Sorry if I'm double messaging(I'm not sure how GitHub comments work), but I'm just making sure that I replied to your helpful suggestions correctly and that there's nothing else required of me to complete, thank you!


Return reference to object providing Endpoint

Summary
This adds a new field Target to the ingress.Endpoint type, which references the object providing that Endpoint.
Use case
I am writing a controller for Apache 2 and want to provide the ability to enable stickiness in front of Tomcat backends. The standard way to achieve this is to set the route= parameter for every BalancerMember (equivalent of upstream.server in nginx). This parameter must match the value of jvmRoute= on the backend.
Without a reference to the Pod providing the endpoint I can't reliably set a route Apache 2 and Tomcat can agree on, like the Pod's name.
ref: https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass

This change is

Coverage decreased (-0.01%) to 44.105% when pulling 6035e55ec342902d98e98ed3c1d2095d4a87b5dc on antoineco:ep-targetref into 65e8cecbac3fc5b46fae69147ded9cd000b27672 on kubernetes:master.

/lgtm

@antoineco thanks!


Add API requirements and design document

As discussed in our call today, this patch adds the document we crafted.
@didier-wenzek and @makr11st I put your "Signed-off-by" into the commit message as well, as we all collaborated here. I hope that's okay with you.
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[x] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Superseded by https://github.com/thin-edge/thin-edge.io/pull/1549


[system]  throws unasignable type

What it says on the tin - using typescript

[√] This is not a v0.x issue.
[√] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔

Shouldn't complain when passing attributes component should accept
Current Behavior 😯

Does complain:
Type '{ children: Element; component: ComponentType<PaperProps>; square: true; className: string; }' is not assignable to type 'IntrinsicAttributes & BoxProps & { children?: ReactNode; }'.
  Property 'square' does not exist on type 'IntrinsicAttributes & BoxProps & { children?: ReactNode; }

Steps to Reproduce 🕹
https://codesandbox.io/s/kind-haslett-38ykt
Context 🔦
I want to leverage the awesome attributes Box gives me whilst using other components, for example;
<Box
  component={Paper}
  minHeight={320} // <Box /> prop
  square // <Paper /> prop
/>

From the typescript guide:

Not every component fully supports any component type you pass in. If you encounter a component that rejects its component props in TypeScript please open an issue. There is an ongoing effort to fix this by making component props generic.

Your Environment 🌎

Tech
Version

Material-UI
v5.0.0.alpha.13

React
1.6.8

Browser
Chrome 75

TypeScript
3.5.3

I am having the same error, I cannot use any of the properties on the Box, dismisses almost the whole point of Material-UI, please fix

I confirm this issue sill exist.

For tracking, the issue exists with primitive component values as well. For example:
<Box
  component="img"
  src="https://tailwindcss.com/_next/static/media/erin-lindford.4804b52007ca82ebe9999d19c717b44d.jpg"
/>`

First reported in https://github.com/mui-org/material-ui/pull/23053#issuecomment-713186467

Temporary workaround (here with a <form> component)
import { FunctionComponent, FormHTMLAttributes } from 'react'
import { Box, BoxProps } from '@material-ui/core'

type FormBoxProps = BoxProps & FormHTMLAttributes<HTMLFormElement>

export const FormBox: FunctionComponent<FormBoxProps> = (props) => (
  <Box {...props} component='img' />
)


"Starting client failed" error when installing Sql Migration extension

Azure Data Studio / OS Version:
Version: 1.47.0 (system setup)
Commit: c7c2b2f21505562d21972d4c135119d00806db4f
Date: 2023-11-07T17:17:45.669Z
VS Code: 1.82.0
Electron: 25.8.4
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.17763

Steps to Reproduce:

Install SQL Migration Extension
View the output

Downloading https://github.com/Microsoft/sqltoolsservice/releases/download/<IP_ADDRESS>/microsoft.sqltools.migration-win-x64-net7.0.zip
(54,448 KB)....................Done downloading Sql Migration Service
Installing Sql Migration Service to c:\Users\sgfx\.azuredatastudio\extensions\microsoft.sql-migration-1.4.11\migrationService\Windows\<IP_ADDRESS>
Installed Sql Migration Service
[Error - 6:12:14 PM] Starting client failed
Error: spawn UNKNOWN
at ChildProcess.spawn (node:internal/child_process:413:11)
at Object.spawn (node:child_process:783:9)
at c:\Users\sgfx\.azuredatastudio\extensions\microsoft.sql-migration-1.4.11\dist\main.js:2:741075
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

@sgft001 does this happen consistently? Did this only start happening with the latest release?
I just tried installing the Azure SQL Migration extension on the ADS 1.47.0 release today and did not run into this error.

@kisantia, this is the first time I am using the product so I just installed the latest version since I need to run SQL Migration assessment against SQL Server database - please advise on troubleshooting approach.

@cpichuka @stuti149 can you please help with this sql migration issue?
@sgft001 can you try uninstalling and reinstalling the extension and see if this is an intermittent issue?

@kisantia , I uninstalled/reinstalled/reloaded ADS a few times - same outcome

@sgft001 @kisantia.
I am able to install Azure SQL migration extension on ADS version 1.47.0 successfully as well.

@sgft001, Can you check if you are able to install the same on other versions of ADS?

Thanks - will do during the day Thu and update this post

@stuti149 @kisantia  - I installed ADS 1.45.1 instead and migration extension got installed correctly and assessment started to work - not sure what's the issue with the latest version


Integrating with vue-router

Hi there, Segment folks!
I think the developer experience could be greatly increased by having a user
pass in their Vue router's instance. That way you can create an afterEach router hook
so the user themselves wouldn't have to create a mounted() hook in each component.
A nice example is how vue-gtm solves this:
https://github.com/mib200/vue-gtm/blob/aacc3b521e3d17827d77aab8ca88cbb15162b583/src/index.js#L43
Would this be something you're willing to consider (and would you be open for a PR)?
Best,
andreas

@andreasvirkus Thanks for checking out our repo :) Absolutely, this is a great idea! We were aiming for the community to find some suggested tips & tricks to help this guide get even better.
I think it is still worth having the content for demonstrating the option of using mounted() for developers who want page calls to be independent in their page components, but I could see this being very useful for people who would like to instrument their app this way.
Would you mind adding a description and an example snippet to the content in Step 2: Track Page Views in an SPA?
Cheers!

Closing for inactivity.

Sorry for not staying on top of this. We're now starting to integrate with Segment and I'll try to put together a PR for this feature over the next few weeks.

PR https://github.com/segmentio/analytics-vue/pull/12 contains an example of how you can implement this yourselves quite easily. Might be of interest to people finding this issue through Google, like me.


Added link to Wikidata's list of all properties

In order to help others find the list of properties easier, I have added the link to Wikidata's list of properties.

Thanks for adding this!


No way to detect if viewer is in hand tool grab-pan mode

Manually setting it to presentation mode, i call HandTool.enterPresentationMode();
i looked at the viewer.js and i cannot find any way to detect if the viewer is in presentation mode or not.
is there such function currently?

There is isInPresentationMode in PDFViewer, see https://github.com/mozilla/pdf.js/blob/1c253e6e1d44237e12ed165d03c50576f732dcf4/web/pdf_viewer.js#L660, which could be accessed (in the default viewer) using PDFViewerApplication.pdfViewer.isInPresentationMode.
Closing as answered.

hi . snuffleupagus. apologies. it's not the presentation mode but when i click the hand tool mode and activate grab to pan. is there such variable to identify that it is in this mode?
currently im checking if the viewerContainer element has the class grab-pan-... but having a variable to detect that would be better.

In that case, try using HandTool.handTool.active.
Closing as answered.

Now that #7207 landed there is PDFViewerApplication.handTool.isActive for this.


new release

This is to aims to make and distribute a new release. @mrakitin if you could check this that would be great.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@mpmdean, I don't see the version at https://pypi.org/project/edrixs/#history. Can you please push the source distribution there?

Hi @mrakitin
When I try to upload via the instructions here
https://nsls-ii.github.io/scientific-python-cookiecutter/publishing-releases.html
I get the error message
Binary wheel 'edrixs-0.0.8-cp36-cp36m-linux_x86_64.whl' has an unsupported platform tag 'linux_x86_64'.

I think uploading sdist (.tar.gz) will be sufficient for now. I don't think we updated the setup.py to build the wheels correctly.

@mrakitin I just uploaded the .tar.gz only and verified it appears on pypi.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender.


[help] Accommodate new breaking change.

This pull request changes user.timeout to user.communication_disabled_until, breaking change in the nextcord lib.
Remove an unused import as well because why not

oh something happened.


Add docs page warning about generators

Step 1 of https://pydantic.slack.com/archives/C05AF4A4WRM/p1715430326710039

for what it's worth, I think it's more likely that someone would discover they need to read this starting from the error message. Not sure if there's a good way for us to make it easier to go from error message -> answer as opposed to answer -> error message (other than google, which maybe is enough).


broken types for parse

by adding |number to the value side of ParsedQuery, you've changed the return type in a really breaking the type signature for users who don't use parseNumbers - now every use of this generates errors like this:
[devserver] TS2345: Argument of type 'string | number | ReactText[]' is not assignable to parameter of type 'string | string[]'.
[devserver]   Type 'number' is not assignable to type 'string | string[]'.

This is only going to get worse when #183 is fixed.
I'd like to suggest either a complex typescript signature such that only passing parseNumbers results in the new string |number| (number|string)[], or introduce a new  function parseValues which does the number/boolean/etc

The first option seems better:
Have a complex type signature that changes output type depending on config.
This could also be applied to arrays, maybe only if you pass parseArray option, it could return an Array

I'd like to suggest either a complex typescript signature such that only passing parseNumbers results in the new string |number| (number|string)[]

👍 PR welcome :)

Is someone with Typescript knowledge working on this? I'd like to fix it but I've kinda so knowledge of Typescript.


sync2: implement database-backed sync based on FPTree

Motivation
The new set reconciliation mechanism requires an efficient data structure for handling range fingerprint queries.
Description
fptree.FPTree provides a sufficiently efficient data structure for
performing range fingerprinting on data residing in database tables,
speeding up the queries at expense of some memory use.
dbset.DBSet builds on fptree.FPTree and provides a database-backed
implementation of the multipeer.OrderedSet interface.
#6405 needs to be merged before this one.

bors merge

Unrelated TestSmeshing systest failure:
    smeshing_test.go:114:
        	Error Trace:	/src/systest/tests/smeshing_test.go:170
        	            				/src/systest/tests/smeshing_test.go:114
        	            				/src/systest/tests/smeshing_test.go:51
        	Error:      	Not equal:
        	            	expected: 26
        	            	actual  : 51
        	Test:       	TestSmeshing
        	Messages:   	0xfc9d997f8b3870be67e24ab7506f62b7c52c8ed41b90d577926fdb3dbbee9419

bors merge

That's not the test that failed, this is the workflow that failed: https://github.com/spacemeshos/go-spacemesh/actions/runs/11748167959
And the reason it failed is because a node generated a malfeasance proof that couldn't be validated by another node: https://grafana.spacemesh.dev/goto/sKk1avMNg?orgId=1
I have never seen this before, the post that we generate in that test is guaranteed to be invalid so a malfeasance proof generated for it should be valid...
cc @poszu

SyncV2 is not used in systests yet (and not integrated with ATXs yet in this PR).
So this needs to be checked, but I think it's not related to the changes here


Add SVG version

@luishdez Maybe add a wontfix label to the issues you've closed without resolution? I mean this one, #1 and #5 (and possibly others I might not be aware of).

@waldyrious Sure, I'm updating the readme because there are other libraries more suitable for nowadays. Thanks for the recommendation 👍

Won't fix this, since I can't give time to this project PRs/Colabs are always welcome


Can't update to newer version

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
I followed the upgrade instructions and I see that the server is retrieving files but nothing is being updated to a new version
Exact BookStack Version
BookStack v22.11
Log Content
No response
Hosting Environment
Ubuntu 22.10 php:8.2.6

Hi @ryanvoorspoels,
Please could you explain the detail/output/errors you're seeing when attempting to run the update commands?

Hi @ssddanbrown, It is solved. There were extra files in the public folder and git pull origin release gave an error.

Hi @ssddanbrown, after the update the header is too big

@ryanvoorspoels

What is the current output of running git status from your bookstack directory?
What is the current output of running git log -n 1 from your bookstack directory?
Have you attempted (now or previously) any customizations to the header via custom HTML or our theme systems?

git status
On branch release
Your branch is up to date with 'origin/release'.
Untracked files:
(use "git add ..." to include in what will be committed)
bookstack-files-backup.tar.gz
public/bookstack-files-backup.tar.gz
public/dist/print-styles.css
public/libs/tinymce/custom-changes.md
nothing added to commit but untracked files present (use "git add" to track)
git log -n 1
commit c61af9c22b319f3fa00e1b089000aecefe36ad09 (HEAD -> release, origin/release)
Author: Dan Brown<EMAIL_ADDRESS>Date:   Thu Nov 2 14:44:53 2023 +0000
Updated version and assets for release v23.10.1

Before the update we added somthing to  Custom HTML Head Content. I have removed it but no change.

Thanks for the info @ryanvoorspoels.
Just a note, you may want to move/remove the public/bookstack-files-backup.tar.gz file you have, since that file would be accessible to anyone with any kind of web access to your instance.
Can't see anything which would affect the header though.

Do you have anything with the themes/ folder of your BookStack install?
Does this remain the same if you open in a different browser and/or private window?
What browser are you using?
Does our demo instance look okay in the same browser (https://demo.bookstackapp.com)?

@ssddanbrown  thanks for the info. I removed the public/bookstack-files-backup.tar.gz file. I tried it on a differed pc and it looks normal. I only have the problem on firefox on windows but after the deleting history and cookies and the buffer the problem is gone.


Cask whatsyoursign fails to uninstall

Pretty self-explanatory here - Cask whatsyoursign fails to uninstall.
==> Uninstalling Cask whatsyoursign
==> Uninstalling Cask whatsyoursign
==> Un-installing artifacts
==> 3 artifact/s defined
#<SortedSet:0x007fe154238ad8>
==> Un-installing artifact of class Hbc::Artifact::PreflightBlock
==> Executing: ["/usr/bin/pluginkit", "-r", "/Applications/WhatsYourSign.app/Contents/PlugIns/WhatsYourSign.appex"]
==> remove: no plugin at /Applications/WhatsYourSign.app/Contents/PlugIns/WhatsY
Error: Command failed to execute!

==> Failed command:
/usr/bin/pluginkit -r /Applications/WhatsYourSign.app/Contents/PlugIns/WhatsYourSign.appex

==> Standard Output of failed command:

==> Standard Error of failed command:
remove: no plugin at /Applications/WhatsYourSign.app/Contents/PlugIns/WhatsYourSign.appex

==> Exit status of failed command:
#<Process::Status: pid 29073 exit 1>

/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/system_command.rb:71:in `assert_success'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/system_command.rb:36:in `run!'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/system_command.rb:14:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/system_command.rb:18:in `run!'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/dsl/base.rb:14:in `system_command'
/usr/local/Caskroom/whatsyoursign/.metadata/1.4.1/20180228044433.477/Casks/whatsyoursign.rb:17:in `block (2 levels) in load'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_flight_block.rb:38:in `instance_eval'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_flight_block.rb:38:in `abstract_phase'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_flight_block.rb:26:in `uninstall_phase'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:403:in `block in uninstall_artifacts'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:674:in `each'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:674:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:400:in `uninstall_artifacts'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:353:in `uninstall'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/uninstall.rb:22:in `block in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/uninstall.rb:12:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/uninstall.rb:12:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/abstract_command.rb:35:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:98:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:168:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:132:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:101:in `<main>'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:173:in `exit'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:173:in `rescue in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:156:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:132:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:101:in `<main>'````

Does /Applications/WhatsYourSign.app/Contents/PlugIns/WhatsYourSign.appex exist?
Also, please always fill out the template.

There wasn't a template for me, sorry. I didn't realize that I uninstalled WhatsYourSign before.

https://github.com/caskroom/homebrew-cask/pull/46988

Is that needed?

Yes, it's installer manual.
brew cask install whatsyoursign && brew cask uninstall whatsyoursign
errors because the app does't exist in /Applications

There wasn't a template for me

Our template have changed recently, did you use "Open a regular issue" when you opened a new issue?


Setup The Warm Start Factory

          I am wondering if the information necessary for the setup and generate of the WarmStart class should be contained in the OCP class or in class specific parameters.

For the moment we have 3 warm start implementation in mind:

"from_gravity_compensation" -> setup needs the robot model, generate the current q
"from_previous_solution" -> setup maybe gets the OCP discretization dt and the MPC frequency, generate needs the previous solution
"from_diffusion_model" -> setup might need the generative model, generate might need a description of the environment/obstacles

Originally posted by @MedericFourmy in https://github.com/agimus-project/agimus_controller/pull/97#discussion_r1869039586

For agimus_controller at the first solve we use inverse dynamics as warm start, same as the references used in the costs, so the generate function of the WarmStart class would need the control plan made by the ocp

Sorry, I'm not sure to understand your point. You mean that in the current implementation you use tau = pin.rnea(q,dq,ddq) for each point of the trajectory as a warm start right?

control plan made by the ocp
You mean made by the planner?

Sorry, I'm not sure to understand your point. You mean that in the current implementation you use tau = pin.rnea(q,dq,ddq) for each point of the trajectory as a warm start right?

well the point is we were talking about the warm start we would use and we were missing one, yes in the current implementation I'm using the formula you are mentioning

control plan made by the ocp

You mean made by the planner?

well the computation of the control is made in the ocp (maybe it will be done elsewhere after the refactor) but it's based on informations from the planner


Cannot load module on PowerShell Core 6.2.3 on Ubuntu

This should speak for itself:
> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.2.3
PSEdition                      Core
GitCommitId                    6.2.3
OS                             Linux 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

> import-module -Verbose PSColor
VERBOSE: Skipping the Version folder <IP_ADDRESS> under Module /home/sto/.local/share/powershell/Modules/PSColor as it does not have a valid module manifest file.
import-module : The specified module 'PSColor' was not loaded because no valid module file was found in any module directory.
At line:1 char:1
+ import-module -Verbose PSColor
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ResourceUnavailable: (PSColor:String) [Import-Module], FileNotFoundException
+ FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

> ls -l /home/sto/.local/share/powershell/Modules/PSColor/<IP_ADDRESS>/
total 48
-rw-rw-r-- 1 sto sto  2879 Mar  2  2016 FileInfo.ps1
-rw-rw-r-- 1 sto sto   560 Mar  2  2016 MatchInfo.ps1
-rw-rw-r-- 1 sto sto  1065 Mar  2  2016 ProcessInfo.ps1
-rw-rw-r-- 1 sto sto 11259 Mar  2  2016 PSColorHelper.ps1
-rw-rw-r-- 1 sto sto  5306 Mar  2  2016 PsColor.psd1
-rw-rw-r-- 1 sto sto  1702 Mar  2  2016 PSColor.psm1
-rw-rw-r-- 1 sto sto  6174 Dec 24 09:53 PSGetModuleInfo.xml
-rw-rw-r-- 1 sto sto   960 Mar  2  2016 ServiceController.ps1

Just in case it doesnt speak for itself; the file PsColor.psd1 has a lowercase s and renaming the file to PSColor.psd1 fixes it.

Indeed!
At least, the fix to be included in the next release is an easy one. I might even try to find some bandwidth to create the corresponding PR...

I run into the same problem


deprecation in qsvm implementation file

hello good sir,
i believe "from dataset import breast_cancer" has been deprecated Quantum Support Vector Machines.ipynb file, i was wondering if you could update or modify the file. Thank you.

Hello,
did you figure out how to implement it?


⚠ Roblox site has degraded performance

In 7177751, Roblox site (https://www.roblox.com/) experienced degraded performance:

HTTP code: 200
Response time: 29129 ms

Resolved: Roblox site performance has improved in 0585855.


[RESOLVED] Unavailable by ICMP ping

Problem started at 12:33:16 on 2023.01.25
Problem name: Unavailable by ICMP ping
Host: ST-FG
Severity: High
Operational data: Down (0)
Original problem ID: 4773
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23133&eventid=4773

Problem has been resolved in 1m 0s at 12:34:16 on 2023.01.25
Problem name: Unavailable by ICMP ping
Host: ST-FG
Severity: High
Original problem ID: 4773


update version bump instructions

can't push directly to master per old instructions, since it's a protected branch.  results in error like:
$ git push
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 8 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 423 bytes | 211.00 KiB/s, done.
Total 4 (delta 3), reused 0 (delta 0)
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: At least 1 approving review is required by reviewers with write access.
To github.com:LD4P/sinopia_editor.git
 ! [remote rejected]   master -> master (protected branch hook declined)
error: failed to push some refs to 'git@github.com:LD4P/sinopia_editor.git'

i also fixed up the indentation in that section so that everything related to the version bump would be nested under the right bullet point.
alternatively, we could close this PR, and unprotect master.  no preference either way from me -- pushing version bumps to master is nice, but protecting from accidental merges and force pushes is probably worth the inconvenience?  🤷♂

discovered while working on #2069


minio: 2021-12-10T23-03-39Z -> 2021-12-27T07-23-18Z

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/minio/versions.
meta.description for minio is: "An S3-compatible object storage server"
meta.homepage for minio is: "https://www.minio.io/"
meta.changelog for minio is: "https://github.com/minio/minio/releases/tag/RELEASE.2021-12-27T07-23-18Z"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/rhkjj3jkmp39mxw2ml85pz1k801rmass-minio-2021-12-27T07-23-18Z/bin/minio passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 2021-12-27T07-23-18Z with grep in /nix/store/rhkjj3jkmp39mxw2ml85pz1k801rmass-minio-2021-12-27T07-23-18Z
found 2021-12-27T07-23-18Z in filename of file in /nix/store/rhkjj3jkmp39mxw2ml85pz1k801rmass-minio-2021-12-27T07-23-18Z

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

50 total rebuild path(s)

25 package rebuild(s)

25 x86_64-linux rebuild(s)
25 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
arrow-cpp
docbookrx
minio
parquet-tools
python38Packages.datasets
python38Packages.google-cloud-bigquery
python38Packages.intake
python38Packages.intake-parquet
python38Packages.pyarrow
python38Packages.snowflake-connector-python
python38Packages.snowflake-sqlalchemy
python38Packages.spacy-transformers
python38Packages.tokenizers
python38Packages.transformers
python39Packages.datasets
python39Packages.google-cloud-bigquery
python39Packages.intake
python39Packages.intake-parquet
python39Packages.pyarrow
python39Packages.snowflake-connector-python
python39Packages.snowflake-sqlalchemy
python39Packages.spacy-transformers
python39Packages.tokenizers
python39Packages.transformers
streamlit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rhkjj3jkmp39mxw2ml85pz1k801rmass-minio-2021-12-27T07-23-18Z \
  --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 minio https://github.com/r-ryantm/nixpkgs/archive/f687526593148b136100f297f316348ce2a583b7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rhkjj3jkmp39mxw2ml85pz1k801rmass-minio-2021-12-27T07-23-18Z
ls -la /nix/store/rhkjj3jkmp39mxw2ml85pz1k801rmass-minio-2021-12-27T07-23-18Z/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

python38Packages.spacy-transformers
python39Packages.spacy-transformers

22 packages built:

arrow-cpp
minio
parquet-tools
python38Packages.datasets
python38Packages.google-cloud-bigquery
python38Packages.intake
python38Packages.intake-parquet
python38Packages.pyarrow
python38Packages.snowflake-connector-python
python38Packages.snowflake-sqlalchemy
python38Packages.tokenizers
python38Packages.transformers
python39Packages.datasets
python39Packages.google-cloud-bigquery
python39Packages.intake
python39Packages.intake-parquet
python39Packages.pyarrow
python39Packages.snowflake-connector-python
python39Packages.snowflake-sqlalchemy
python39Packages.tokenizers
python39Packages.transformers
streamlit

Maintainer pings
cc @edolstra @bachp @kalbasit for testing.

Result of nixpkgs-review pr 153183 run on x86_64-linux 1

11 packages failed to build:

python38Packages.datasets
python38Packages.google-cloud-bigquery
python38Packages.intake
python38Packages.intake-parquet
python38Packages.pyarrow
python38Packages.snowflake-connector-python
python38Packages.snowflake-sqlalchemy
python38Packages.spacy-transformers
python38Packages.tokenizers
python38Packages.transformers
python39Packages.spacy-transformers

13 packages built:

arrow-cpp
minio
parquet-tools
python39Packages.datasets
python39Packages.google-cloud-bigquery
python39Packages.intake
python39Packages.intake-parquet
python39Packages.pyarrow
python39Packages.snowflake-connector-python
python39Packages.snowflake-sqlalchemy
python39Packages.tokenizers
python39Packages.transformers
streamlit


Support 1.21 based on Atomic Junky's work

This almost definitely shouldn't be merged. Just putting this out here to show what I needed to change to get Gamemode 4 working.

See also https://github.com/mcbeet/mecha/pull/300

Superceded by 1.21 support (https://github.com/mcbeet/beet/pull/422)


KIC returns self-signed certificate during pod restart

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When I call the URL exposed with Ingress during KIC pod rollouts I receive errors regarding self-signed certificates for a moment and then it starts returning a proper one (LetsEncrypt):
*   Trying redacted:443...
* Connected to redacted (redacted) port 443 (#0)
* ALPN: offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
} [326 bytes data]
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [19 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [979 bytes data]
* SSL certificate problem: self signed certificate
* Closing connection 0

In the logs we observed:
2023/07/04 15:39:19 [info] 1109#0: *306 SSL_do_handshake() failed (SSL: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:SSL alert number 46) while SSL handshaking, client: <IP_ADDRESS>, server: <IP_ADDRESS>:8443

We're running KIC integrated with AWS NLB on EKS. Runs as Daemonset on all nodes (number of running pods depends on how many nodes are added by autoscaler[karpenter]).
Certificate is not changing during the KIC deployment/rollouts.
Expected Behavior
When I call the any URL exposed with KIC in our cluster I should receive "no route to host" "service unavailable" or preferably traffic should not be directed to the pods that hasn't started properly yet.
Steps To Reproduce
1. Trigger KIC restart (kill one or more pods)
2. Call any of URLs exposed with KIC. For my testing purposes I was running a loop calling some endpoint
3. In case all pods are terminating it returns `Connection refused`. Pretty much understandable
4. But after new ones are created in some of the receive `SSL certificate problem: self signed certificate`

Kong Ingress Controller version
3.0

Kubernetes version
Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.17-eks-c12679a", GitCommit:"d5ce2cee85d99653d6f8c278043213db21b1cd72", GitTreeState:"clean", BuildDate:"2023-05-22T20:32:28Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}

Anything else?

KIC was installed using the official Helm Chart
values.yaml file

kong:
  priorityClassName: "system-cluster-critical"
  replicaCount: 1

  deployment:
    kong:
      enabled: true
    daemonset: true
    namespace: "infra-system"

    # Applying workaround from https://github.com/Kong/kong/issues/9836#issuecomment-1444966054
    # to prevent 'address already in use' error when container is restarted
    userDefinedVolumes:
      - name: "kong-kong-prefix-dir-tempfs"
        emptyDir:
          medium: "Memory"
          sizeLimit: 256Mi
    userDefinedVolumeMounts:
      - name: "kong-kong-prefix-dir-tempfs"
        mountPath: "/kong_prefix_tempfs/"

  env:
    # "prefix" value must be set to match mountPath configured above
    prefix: "/kong_prefix_tempfs/"
    router_flavor: traditional
    headers: "off"
    log_level: "info"
    ssl_cipher_suite: "intermediate"
    ssl_protocols: "TLSv1.2 TLSv1.3"
    nginx_proxy_proxy_ignore_client_abort: "on"

  status:
    enabled: true
    http:
      enabled: true

    tls:
      enabled: true

  admin:
    enabled: true
    type: ClusterIP

    http:
      enabled: true

    tls:
      enabled: true

  proxy:
    enabled: true
    type: LoadBalancer
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-scheme: "internet-facing"
      service.beta.kubernetes.io/aws-load-balancer-type: "nlb"
    labels:
      enable-metrics: "true"

    http:
      enabled: true

    tls:
      enabled: true

  migrations:
    preUpgrade: false
    postUpgrade: false

  ingressController:
    enabled: true
    ingressClass: external-lb

  waitImage:
    enabled: false

  serviceMonitor:
    enabled: true
    interval: 30s
    labels:
      release: kube-prometheus-stack

  tolerations:
    - key: "allocation"
      operator: "Equal"
      value: "infra"
      effect: "NoSchedule"
  plugins:
    configMaps:
      - name: kong-plugin-moesif
        pluginName: moesif

Moesif plugin has been installed
example Ingress object (redacted)

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress-name
  annotations:
    konghq.com/https-redirect-status-code: '301'
    konghq.com/protocols: https
spec:
  tls:
    - hosts:
        - name.example.com
      secretName: certificate-wildcard
  rules:
    - host: name.example.com
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-name
                port:
                  number: 8000

This predates the change to use the new config available readiness endpoint and was presumably using the old /status endpoint, which would mark Kong containers ready regardless of whether or not they had configuration available. Newer versions of the ingress controller should have prevented Pods from becoming ready in sidecar mode, but it's not clear which version of the controller was used here.
AFAIK this will not happen on current versions (controller 3.0, Kong 3.5, chart 2.33). My test plan was:

Deploy a 15-replica set of Kong instances with a sidecar controller (the Kong readiness endpoint behaves the same way whether the controller is deployed as a sidecar or not, so that shouldn't affect behavior--although separate Deployments for Kong and the controller are now more common, I opted for the topology used for the original report).
Create a basic HTTPS Ingress+Service: tls_ingress.yaml.txt
Confirm I see the expected certificate from the Secret for kong.example and the default self-signed certificate for wrong.example (the latter does not match any configured route/SNI and should serve the fallback certificate).
Start repeatedly sending requests for kong.example to the proxy Service LB IP using curl while logging the presented certificate subject to a file.
Run kubectl rollout restart on the Kong Deployment.
Wait for the new replicas to replace the old.
 All observed hostnames across the restart period were the expected kong.example certificate.

Results did not indicate that any of the requests saw the fallback certificate:
pod_restart_status.txt
curl_test.txt
Based on my knowledge of the old and new readiness behaviors, the original report was likely caused by the old behavior bringing Pods into Service before they were truly ready. Testing indicates that the new readiness behavior is behaving as expected and that kube-proxy will not dispatch requests to instances before they've received configuration. I'm closing this as outdated; if you continue to see incorrect certificates served with current versions, please respond back with updated replication steps.

Faced similar issue, After configuring all the ClusterIssuer and obtaining Certificate, adding the protocol annotation helped me with using right certificate.
https://docs.konghq.com/kubernetes-ingress-controller/3.0.x/reference/annotations/#konghqcomprotocols
apiVersion: v1
kind: Service
metadata:
  name: service-basic-nuxt-app
#  annotations:
#    konghq.com/protocol: https
#    konghq.com/plugins: rate-limit-5-min
spec:
  selector:
    app: basic-nuxt-app
  ports:
    - protocol: TCP
      port: 3000
      targetPort: 3000
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ing-basic-nuxt-app
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
    konghq.com/preserve-host: "true"
    konghq.com/strip-path: "true"
    konghq.com/protocols: "https"
    # redirects to HTTPS
    konghq.com/https-redirect-status-code: "301"
spec:
  ingressClassName: kong
  tls:
    - secretName: k8-prod-certs
      hosts:
        - example.com
  rules:
    - host: example.com
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-basic-nuxt-app
                port:
                  number: 3000


AMBARI-23913 New UI Makes it hard to see that a host is in a "Decommissioning" state

How was this patch tested?
21535 passing (30s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2389/
Test PASSed.


Modified the utils and the demo.ts file to showcase the functionality of updating the stream

Please note. Any changes inside of SDK should be called out, because it needs a release to get reflected for those who want to run this.

Noted. Thank you

Please note. Any changes inside of SDK should be called out, because it needs a release to get reflected for those who want to run this.

@amarts  you mean call out internally?

@amarts you mean call out internally?

Call out in description of the PR itself, so when we review, and later when we check git log we have context of when all a release was required etc.

@adi-a11y  pls review the comments and close this PR

@adi-a11y pls review the comments and close this PR

working on it


[BUG] Doesnt Save Suffixes/Prefixs

Details
Spigot Version: paper 1.16.5 on java 11
please run /ep debug and attach a screenshot https://ibb.co/93gPBWt
Describe the bug
A clear and concise description of what you expected to happen.
When I add prefixes/suffixes the plugin will not save them. It always reverts to the default config and groups.yml
Expected behavior
A clear and concise description of what you expected to happen.
Save prefixes and suffixes
Screenshots
If applicable, add screenshots to help explain your problem.
https://ibb.co/hyGy7j0

https://pastebin.com/4pjBiWu7 Here is the groups.yml

I Found the solution. Just delete the entire plugin and reinstall it or just use a different plugin


add types

Not sure if it covers all the types, but it's a copy from the typings project that exist for this project

Thanks whats the reason for putting the types into the source project instead of DefinitelyTyped? Does it make Versioning easier?

Yes! Also no need to install multiple packages, and it's easier to keep the types up to dae

Can we resolve the conflicts and I will merge this!
Pretty sure we should add enableLabel as well to the type def

Done!


A11y_AzureDataStudio_Deploymenttemplateconfiguration_ScreenReader:NVDA is not announcing disabled button as disabled.

5. "Select the deployment option" screen gets open and click on I accept check box and click on select button.
6. Start NVDA and navigate with the help of up and down arrow and observe the announcement.
Actual:
NVDA is announcing disabled button as normal enabled button.
Expected:
NVDA should announce disabled button as disabled button.
User Impact:
Screen reader User will misunderstood content and they will think there is some interactive button which can be used for some purpose.
Attachment for Reference:
7677_A11y_AzureDataStudio_Selectthedeploymentoption_ScreenReader4.pptx
Does this issue occur when all extensions are disabled?: Yes

we have removed the checkbox(emoji) in the latest design, see below, closing the issue.

GitHubTags:#SQLADS-Win32-May2019;


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 852

Questions ?
Please refer to the Backport tool documentation


Using Timezone Calendar and Timezone events to calculate DTSTART, DTEND

For now, the DTSART and DTEND values returned don't take in consideration the calendar timezone and the events timezone.
I propose to modify the class so that it returns timezone adapted values into new fields (ex : DTSTART_tz, DTEND_tz).

See https://github.com/johngrogg/ics-parser/pull/66/commits/529f48122db9b51acc16419e0a2beeb06d24652b

Fixed by PR #70


chore: upgrade zod to 3.22.3

Closes #548
✅ Checklist

[x] I have followed every step in the contributing guide
[x] The PR title follows the convention.
[x] I ran and tested the code works

Testing
Ran E2E tests to verify they succeeded.

Changelog
Upgrade zod library to 3.22.3 across all packages.

Screenshots

💯

This looks great! Could you resolve the conflicts and then this PR can be merged 👍

Thanks! I've rebased the PR.

@hmacr unfortunately the pnpm-lock.yaml file in this PR is broken, probably because of a bad merge or conflict resolution. Might be easiest to close this PR and redo the changes on top of the newest main broken lockfile. Doing a pnpm install with a broken lockfile completely recreates the lockfile which is definitely not what we want.

@ericallam ah ok. Let me close this and create a new PR.

@ericallam Raised a new PR - #570. Please check.
Unfortunately, I was using pnpm v8 (instead of the recommended v7). v8 introduced a change in the lockfile format, hence it resulted in too many changes.


Encoder cannot accept input from stdin

The encoder requires two passes over the input, stdin does not support seeking, so I can only receive input from something I can (a file). Decoding does not have this issue as it requires only one pass over the input.

Potential solutions are:

caching input while counting and then reading over that cache for encoding
using an adaptive tree: by beginning with a basic tree and dynamically updating it while reading encoding (and decoding) would eliminate the need for two passes and no longer require the tree to be encoded, however the actual compression ratio may suffer


What format should be used for start/end dates?

Sorry @danielfowler missed this from a year ago!! Unix timestamps should be used


Google Voice Dark Mode update

Pre-flight Checklist
Please ensure you've completed all of the following.

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I updated the version package Updating

Description of Change

Dark mode change required for a recent Google Voice update. Text message input field had an additional style added on the service's end, and this PR compensates for it in dark mode

@all-contributors please add @oc013 for code


No longer set DEVICE_PERIPHERALS in steal()

We've discussed this a bit in the weekly meetings, I propose removing setting DEVICE_PERIPHERALS from steal() and leave it only in take(). This shouldn't meaningfully change the safety conditions or the use of either API, but does make stealing zero-cost. It was always possible to unsafely transmute() to obtain Peripherals without setting DEVICE_PERIPHERALS, so I'm interested if anyone can remember why this existed in the first place or if it is indeed still needed.

Closing this. We discovered why this is present: frameworks like RTIC want to take() the peripherals but know it cannot fail as they are running before any other code, so can use steal() to avoid the overhead associated with unwrap() while still setting the DEVICE_PERIPHERALS flag to ensure subsequent user code cannot safely end up with duplicate peripherals.
We should add this to the documentation ideally, but it doesn't seem worth changing this behaviour. Instead we can add the new per-peripheral steal() in #723 which needn't set DEVICE_PERIPHERALS, and that can be the zero-overhead way of unsafely creating a peripheral for new code.


Add support for pending block data

Is your feature request related to a problem? Please describe.
Currently, when Katana is asked for get_events, the pending block is not taken in account.
The function that is ignoring the pending block is this one:
https://github.com/dojoengine/dojo/blob/54a891ee45d0f593c7d0cea28c5b72f56008412e/crates/katana/storage/provider/src/traits/block.rs#L18
Describe the solution you'd like
The underlying provider must be updated to support the pending block. For now we could assume pending block will ends up having the block number = latest + 1. But this may not always be true on the public network. However, on Katana, it should be fair to make this assumption.

@glihm can I work on this?

@EjembiEmmanuel closed in favor of #2328 and @kariy will work on it, let me check which one could be tackled on your end @EjembiEmmanuel. Will try to have more good first issues.

Alright @glihm no worries!


How do I add packages?

How do I add packages? I can't find instructions anywhere.

Packages are stored in the Community Repo.

Pleas add the ability to add packages directly using this tool.

This is all I could find:

https://docs.microsoft.com/en-us/windows/package-manager/package/
https://github.com/microsoft/winget-cli/blob/master/doc/ManifestSpecv0.1.md

Please put this info in the readme in this repo, it wasn't easy to figure out and stumbled upon it accidentally here.


refactor(pipelines/pingcap): simplfy git repo cache keys

Ref:  #2113
Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve

/approve


[ASK] MSO365 => MSO2016 Proplus

How and why does my MS365 installed changed to MS2016 ProPlus?

If you are following the tutorial, this is correct.
If it changed after you login MS account, please log out your MS account.


refresh from 1.2.1-proposed

Backport formatting fixes (#210)
fix typo in ResourceRequirement.coresMin description (#214)
fix workflow scatter typos (#215)
Two tests were accidently still specifying v1.0 (#217)
Add missing label field
backport labels for some conditional tests
Increase the timeout in the time limit test
Create dependabot.yml
Added conformance tests for File and Directory glob
add hyperlinks to intent definition
Bump rojopolis/spellcheck-github-actions from 0.23.0 to 0.29.0
Bump actions/setup-python from 2 to 4
Bump actions/checkout from 2 to 3
ci: use cwltest pytest plugin for better speed
Bump rojopolis/spellcheck-github-actions from 0.29.0 to 0.30.0
Fixed MacOS X compatibility for wc-tool
Document that ExpressionTool outputs are always valid
add render script
install cwltool when rendering
also lockfile
render: skip docker
render: re-use git checkout
official IANA media types for CWL documents
spelling: check YAML docs
Fixes #193
Substitute URI with IRI in docs
Add tests for decimal representation of very big and very small numbers
ci: add codespell check
sync metaschema
typos
Fix typo {} vs ()
Bump rojopolis/spellcheck-github-actions from 0.30.0 to 0.32.0
Bump codespell-project/actions-codespell from 1.0 to 2.0
Update requirements.txt
Update requirements.txt
All loadContents tests are required
default_with_falsey_value (#48)
Bump rojopolis/spellcheck-github-actions from 0.32.0 to 0.33.0 (#257)

Failed test is due to the cwl-1.3 branch of cwltool not being up to date with recent fixes, especially https://github.com/common-workflow-language/cwltool/pull/1853


Why dont support dispatch_once?

Hi,
You said "I've found no need for dispatch_once in Swift" in #2 .
Could you please explain why no need to use dispatch_one in Swift?
Thanks.

Global variable (and constants) plus static members of classes/structs/enums with inital values basically initialised with the same dispatch once guarantees. And you can be the inital value be the result of a closure if you need any complex set up.

@huynhphan89 What @josephlord said. If you have a specific use of dispatch_once in Swift, feel free to share :)


You can not interact with Windows Taskbar when VS Code is fully mazimixed.

Issue Type: Bug
Hi, there is a problem that is kinda annoying, for me mostly.
My WIndows 10 Taskbar is placed not in the bottom, but in the upper part of the screen, and it is also hidden (only shows up when I hover the mouse, why do you have it configure like that you may ask?!, you know, to give my Windows 10 a sick look). But this is where the problem comes.
When VS Code is fully maximized, for some reason, when I try to search for something in the hidden taskbar, the taskbar do not show up. I have to minimize the VS Code window, in order for being able to change windows or change a setting in the system.
This is kinda annoying, since this program is the only one with this type of behavior. I have the latest Slow Ring Update for Windows 10 (19041.153).
So the steps are:

Have a passion to transform WIndows 10 and place the Windows 10 Taskbar in the upper part of the screen.
Have a sick passion for design, and change the settings of the Taskbar to "In Desktop Mode, automatically hide the taskbar" (I made a rough translation from Spanish, sorry).
Install the lastest insider version (mine is 1.44.0-insider) of VS Code, and fully maximize it (in my case, any version of VS Code will do the trick).
Now try to go and reach the taskbar, you will notice that out of the blue the little extrovert, now has become a little shy. Maybe Windows 10 feel kinda overpowered by one of it is tools, a awesome tool I may add.

I do not accept as answer to fix my problem, hey press the Windows key, that will fix the problem, or, use Alt + Tab (to change applications, and in this step you can learn to be more productive) nor, just minimize VS Code, and you won't have this problem anymore.
Thank you for your time.
VS Code version: Code - Insiders 1.44.0-insider (798481c7978af034b054e14ace4e471e7a83f665, 2020-03-16T07:59:35.730Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (4 x 3293)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.70GB (1.54GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

python
ms-
2020.2.64397

remote-wsl
ms-
0.44.0

vscode-css-peek
pra
3.0.2

open-in-browser
tec
2.0.0

vscode-icons
vsc
10.0.0

vscode-todo-highlight
way
1.0.4

(1 theme extensions excluded)

/duplicate of #86260


Add touch support?

Hello,
I was wondering if there was a way to add touch / drag support into the gauge views to select the desired value?

Hi,
This library doesn't support progress bar or any response to actions, for now at least.
Please follow this issue #72 for more details.


Merge changes to add @manez to committers.

Purpose / why
Updates the main branch with commits that were only on master.
@jordandukart many thanks for the quick work on #1612!
But... I forgot to git commit after fixing the merge conflict, so this re-adds @manez .
One of you want to merge?

Thanks for that catch @manez !