'osgi.bundle;  org.eclipse.ui.editors 3.14.300' but it could not be found

Cannot complete the install because one or more required items could not be found.
Software currently installed: Mice OpenAi Feature <IP_ADDRESS>301251847 (it.micegroup.openai.feature.feature. group <IP_ADDRESS>301251847)
Missing requirement: it.micegroup.openai.plugin <IP_ADDRESS>301251847 (it.micegroup.openai. plugin <IP_ADDRESS>301251847) requires 'osgi.bundle;  org.eclipse.ui.editors 3.14.300' but it could not be found
Cannot satisfy dependency:
From: Mice OpenAi Feature <IP_ADDRESS>301251847 (it.micegroup.openai.feature.feature. group <IP_ADDRESS>301251847)
To: org.eclipse.equinox.p2.iu;  it.micegroup.openai.plugin [<IP_ADDRESS>301251847,<IP_ADDRESS>301251847]

It seems that the version is too old., I am using version 2021-03 (4.19), error.
Downloaded new version 2022-03 (4.23) and can install this plugin normally.

I modify it for eclipse luna sr2 and openjdk-8 by [openai-java] 0.12.0 if you want check issue #2

welcome sir~


Update for node iron lts

Upgrade node modules

Upgrade some packages + audit fix (reduce some security warnings) to prepare for the transition to node 20
(see #37041 )
fix style (due to bootstrap-touchspin upgrade )

Questions
Answers

Description?
upgrade node modules

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
related #34058

Sponsor company
Your company or customer's name goes here (if applicable).

How to test?
Indicate how to verify that this change works as expected.

Hello @mattgoud!
This is your first pull request on classic-theme repository of the PrestaShop project.
Thank you, and welcome to this Open Source community!

No need functional testing :) ok to be merged

PR merged, well done!
Message to @PrestaShop/committers: do not forget to milestone it before the merge.

Thanks @mattgoud


Add ability to turn of "git clone --depth=1", it's sometimes quite expensive

This was changed in 2e9ceb9 by @kellegous. See this comment to a CocoaPods issue for why using shallow clones for things like this is a bad idea.
IMO this commit should just be reverted, it makes much more sense to do a full clone and then fetch that with the way the fetch protocol works and how shallow clones can trigger bad edgecases in it, but if not please add some config option to turn this off.
Edit: FWIW this isn't some theoretical thing, I have a very large repo that's running into this edge-case, a "pull" should take 2-3s, but sometimes takes up to 6 minutes from hound (a fresh clone is ~3m) because of the edge cases triggered by the shallow clone.

Maybe use --single-branch instead?

Boosting this— using a shallow clone also complicates things when you have branches that may change non-linearly (force push), or when hound is pointed at a SHA or switched between different branches. I dealt with this some years ago on a fork, but it wasn't a very clean solution so I never tried to push it upstream:
https://github.com/hound-search/hound/commit/6b0b44db489f9aeff390ad8a95cc57d6543b002e
I think probably just doing a single-branch clone upfront would be a better way.


Can‘t open UI

I follow the install step 'add https://puni.sh/api/repository/veyn' and install bossmod. but i cant open config UI and cant use in some quests.
here is the error:
| ERR | Exception during raise of "Void OpenConfigUI()"
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'start')
at BossMod.ModuleViewer.Classify(Info module) in /home/runner/work/ffxiv_bossmod/ffxiv_bossmod/BossMod/Config/ModuleViewer.cs:line 251
at BossMod.ModuleViewer..ctor() in /home/runner/work/ffxiv_bossmod/ffxiv_bossmod/BossMod/Config/ModuleViewer.cs:line 77
at BossMod.ConfigUI..ctor(ConfigRoot config, WorldState ws) in /home/runner/work/ffxiv_bossmod/ffxiv_bossmod/BossMod/Config/ConfigUI.cs:line 20
at BossMod.Plugin.OpenConfigUI() in /home/runner/work/ffxiv_bossmod/ffxiv_bossmod/BossMod/Framework/Plugin.cs:line 136
at Dalamud.Utility.EventHandlerExtensions.HandleInvoke(Action act)

but the bossmod works in some sepcific quest like 'A Finale Most Formidable' and boss in ‘the Praetorium’

I don't know this issue happened because I'm a CN platform player or i install bossmod in a wrong way.
I wish some good guys could help me to fix this issue, Thx.

you need to use the chinese fork https://github.com/44451516/ffxiv_bossmod

you need to use the chinese fork https://github.com/44451516/ffxiv_bossmod

thank you, you help me a lot

No problem. This problem comes up a lot, I am not sure why the UI does not work on the chinese version. Not sure if it can be fixed directly or is a problem resulting from the chinese dalamud version.

No problem. This problem comes up a lot, I am not sure why the UI does not work on the chinese version. Not sure if it can be fixed directly or is a problem resulting from the chinese dalamud version.

Chinese users may encounter this issue. Could we include the solution in the readme.md to prevent more Chinese users from being unable to use the product or submitting unnecessary issues?Thank you very much for your understanding and assistance.

Outdated.

This fork has been deleted, the user also been deactivated.


Does it support alpine arm?

As the title ,does it support alpine arm 64/32 or any other arm?  thanks

I haven't used NPOI on alpine arm. But it should work as long as .NET core can run on it and libgdi is available on Alpine.
For details about how to make it work on Linux, you can read this post


Add missing closing ``` for a code block

Fixes formatting bug from #6555
Signed-off-by: Gera Shegalov<EMAIL_ADDRESS>

Screenshot showing how Bash and bash render in gh-pages

build


community: Fix validation error in SettingsConfigDict across multiple Langchain modules

Description: This pull request addresses the validation error in SettingsConfigDict due to extra fields in the .env file. The issue is prevalent across multiple Langchain modules. This fix ensures that extra fields in the .env file are ignored, preventing validation errors.
Changes include:

Applied fixes to modules using SettingsConfigDict.

Issue: NA, similar https://github.com/langchain-ai/langchain/issues/26850

Dependencies: NA

@Raj725 this looks good. Let me know whenever PR is ready for review

@Raj725 this looks good. Let me know whenever PR is ready for review

@eyurtsev I kept this in draft because I haven't tested it. However, I did test similar changes I made for SharePointLoader/_O365Settings in this PR: https://github.com/langchain-ai/langchain/pull/26851.

It looks reasonable to me


CI improvements and cleanups to flake.nix

The PR reduces the number of Rust toolchains we test against on CI. This was a holdover from my habits during pre-1.0 Rust where we were encouraged to test all the versions. Hopefully Github’s error de-duplication will improve in the future (see https://github.com/actions/runner/issues/504).
I also took the time to clean up the flake.nix file. It skips the packaging for now and just loads a Rust development environment. This is used on CI to load Rust instead of actions-rs which appears to be dormant. This might be controversial, but it seemed decently clean and decreases the amount of setup stuck in CI land. We can always switch to another approach in the future though, as Fathom’s use case is pretty simple.
I also added the minimum supported rust version to fathom/Cargo.toml. This is used to drive the MSRV used on CI.

@wezm Yeah, remembering to keep that in sync was always a pain! And it’s a bit finicky to pass to the build matrix.
Just pushed an update to do cargo check, cargo build, and cargo test all in one job to further pare things back.
Also happy to do a MSRV bump if you are finding the current version too restrictive?


Trust-List vs Trust Anchor vs TLS Trust List

I am having trouble understanding what the usage of application-jks-signing.yml and if/why I should configure it.
In the EU DCC solution, we have the TLS Trust List, and the DGC Gateway which acts as the Trust Anchor.
Why do we have the addition of the Trust-List in the above mentioned file?
The specific feature: https://github.com/eu-digital-green-certificates/dgca-businessrule-service/pull/22
mentions issue https://github.com/eu-digital-green-certificates/dgca-businessrule-service/issues/10 which again describe a technical requirement, and not really a business requirement, and why it should be included... "The responses of the following routes should include a header with a ECDSA signature"
Should the signature included not be that of the Trust-List, which is all ready defined in  application.yml
      trust-anchor:
        alias: ta
        password: dgcg-p4ssw0rd
        path: classpath:trust_anchor.jks

Please help me understand this better as for us to configure it correctly for Cyprus.
Please note that the dockerfile has also not been updated to reflect the change introduced:
\https://github.com/eu-digital-green-certificates/dgca-businessrule-service/blob/main/docker-compose.yml

@daniel-eder  Anyways we can get a response for this?

@SchulzeStTSI can you chime in?

@psavva the mentioned feature is a signing of the business rule list provided by the national backend, means NB<-->Wallet/Verifier App. The other trust components are from gateway to national backend(Gateway<--->NB). So far I see it's currently not enabled in the apps, so the configuration of it is optional for the moment.


fail to import swiper

page error

Module not found: Error :can't resolve 'swiper/dist/css/swiper.css'

console warn

This dependency was not found:
* swiper/dist/css/swiper.css in ./src/main.js
To install it, you can run: npm install --save swiper/dist/css/swiper.css

npm install --save swiper/dist/css/swiper.css

npm ERR! code ENOLOCAL
npm ERR! Could not install from "swiper\dist\css\swiper.css" as it does not contain a package.json file.

source

import Vue from 'vue';
import VueAwesomeSwiper from 'vue-awesome-swiper';
import 'swiper/dist/css/swiper.css';
import App from './App.vue';
import router from './router';
import store from './store';
import './assets/css/reset.css';
import './assets/fonts/iconfont.css';
import 'lib-flexible';
Vue.config.productionTip = false;

Vue.use(VueAwesomeSwiper);
new Vue({
  router,
  store,
  render: h => h(App),
}).$mount('#app');

swiper.css in your node_modules directory, if you have "can't resolve 'swiper/dist/css/swiper.css", you should check the this file path is right?

I meet this problem two times,the first time, I rewrite the project and it works.the second time is now,I don't want to rewrite it but I don't know what to do

v4.0.0 was released!
May be you need reread the document. (Swiper was move to peerDependencies)

If you don't want to change anything in your code,  just downgrage package. The code is below:
npm i<EMAIL_ADDRESS>--save

For those scratching their head at this error. It's because it's not enough to just install vue-awesome-swiper, you have to explicitly also install the package swiper which wasn't required in V3. Just do a npm i swiper --save and it will work

npm i swiper --save
or
yarn add swiper --save
and then:
import { Swiper, SwiperSlide } from 'vue-awesome-swiper'
import 'swiper/swiper-bundle.css'

I have the same question ,and I use import  'swiper/css/swiper.css' to fix it

I have the same question ,and I use import 'swiper/css/swiper.css' to fix it

where??

fixed by changing path to file    'swiper/swiper.scss'

@vbarrientos97 Add these two lines inside your component's script tag:
import { Swiper, SwiperSlide, directive } from "vue-awesome-swiper";
import "swiper/css/swiper.css";

This is not working

I agree, all the above solutions don't work!

@programmeranamul, @Christo-Deyzel, try this and it should work:
npm i swiper --save
or
yarn add swiper --save
and then:
import { Swiper, SwiperSlide } from "vue-awesome-swiper"
import "swiper/swiper-bundle.css"
import "swiper/css/swiper.css"

If this doesn't work, so please, give us more details about the error that you are facing.

This is a known issue when using Swiper v7.
I temporarily fixed the problem in my project by downgrading swiper
yarn add swiper@6 --save
We should update this package to be compatible with the new Swiper version.

None of the solutions mentioned above seem to work for me i am using swiper version "^7.0.4"
Trying to add css does not work with all solutions above

@MandelaMan I opted to remove swiper for now.. might delay the feature I am working on

its resolve on my case. ive upgraded
swiper@6
then on import is
import "swiper/swiper.scss";

Hey,
I have faced the same problem, where my images module isn't found during gatsby build time, I cloned the repo of swiper js in a separate directory and copied the missing files and then added them to my git repo to prevent it from installing during cloud build time. this works for the time being until the fix is shipped.

someone please fixed this issue I am facing swiper/css module not found
I have uninstalled and install v6 still issue same. changed import directory still issue is there. error is only with swiper/css

@mustafa174, please try these steps below:
npm cache clean -f
npm uninstall swiper
npm uninstall vue-awesome-swiper

npm cache clean -f
npm install --save swiper@5
npm install vue-awesome-swiper@4 --save --legacy-peer-deps

Please let me know if you have resolved the issue

Downgrade to version 6 is resolved the issue with import components Swiper and SwiperSlider, but im stil doesnt know how to import styles

Idk lol.. Everything you tried to import, can't resolve

"swiper": "^6.8.4",
"vue-awesome-swiper": "^4.1.1",
with
import Vue from "vue"
import { directive } from "vue-awesome-swiper"
import "swiper/swiper.min.css"

Vue.directive("swiper", directive)

working fine, FINALLY!

Same problem here using Swiper 7.0.6. I was using version 6.8.4 and everything was working fine. After upgrade to version 7.0.6 I am getting Can't resolve '~swiper/swiper-bundle.min.css' when the file exists in ./node_modules/swiper/.
No matter what version of (S)CSS I use, I am getting always the same error, looks like import stylesheets from Swiper doesn't work anymore.

I have same problem installing 7.0.8
Fixed by using absolute path to node_modules, e.g. @import '../../../../../../node_modules/swiper/swiper.scss';
An odd problem since imports from other packages work fine with alias like @import '~sass-rem/rem';.

i think it has to do with the way exports are configured on swiper package.json:
// this was always giving an error of file not found
@import "~swiper/swiper";
// this fixed the issue since is what is configured on the exports of swiper package.json ("./scss": "./swiper.scss",)
@import "~swiper/scss";

npm i -g sass
or
npm i sass --save-dev

i had the same problem
fixed it by giving a absolute path import "../../../../node_modules/swiper/swiper-bundle.min.css";
I don't know why the nextJs or reactJs wont take the imports like the other packages lol

Solution for Swiper 7.4.1 on Vue 3 + Vite and compile with Webpack
https://stackoverflow.com/questions/69179230/unable-to-use-swiper-vue-dependencies-not-found/70755021#70755021

Working for me ^7
import 'swiper/css/bundle'

use it as plugin, that's work.

downgrade it to the 3.1.3 version in Nuxt.

删除node_modules
删除package-lock.json
重新npm install
如果还不能运行并提示让安装某个插件，请检查插件是否有升级，package.json中版本是否有修改
比如e-icon-picker从1.0.14升级到1.1.7之后
e-icon-picker/dist/index.css要改为
e-icon-picker/lib/index.css


Fix resource history endpoint when the version numbers aren't continuous (#3305)

Pull request opened by the merge tool on behalf of #3305

Merged into branches iso4 in c61b5fb4f63368f8ab83c14c6811d12d1700c5f1


try a new code coverage tool

the current codecov tool in GitHub we use doesn't seem to be super accurate for measuring code coverage -- experiment with other rust code coverage tools

@de-husk any ideas?

So looking at what we have now, we are actually using cargo tarpaulin to generate the actual report:
https://github.com/DA0-DA0/dao-contracts/blob/main/.github/workflows/codecov.yml#L16
So we might as well keep using codecov to view the reports in github.
We should try this code coverage tool to see if it is more accurate for us: https://github.com/mozilla/grcov

Closing until there is a more concrete plan. Feel free to re-open with one.


Create metadata health check endpoint

Description
This PR creates a metadata/health endpoint that runs health checks. This endpoint is basically a wrapper for the Dropwizard GET /healthchecks endpoint, except you can specify a query parameter to indicate if you want to run a specific health check. The /metadata/health endpoint is also more vague than the Dropwizard one, returning only the health check name and whether or not it's healthy, because I made it an unauthenticated endpoint. The error messages for failed health checks are logged.
Background: the webservice container in our Fargate deployment uses the Dropwizard GET /healthchecks endpoint as its health check. The Dropwizard endpoint runs all registered health checks, which include are our TemplateHealthCheck and ConnectionPoolHealthCheck, as well as two default Dropwizard health checks: SessionFactoryHealthCheck and a deadlocks health check. During an RDS DB upgrade, the SessionFactoryHealthCheck fails if the DB restarts, which was the case when our RDS instance automatically applied a minor version upgrade.
This metadata endpoint is used in https://github.com/dockstore/dockstore-deploy/pull/632 by the webservice container health check. It uses the query parameter so it only runs the connection pool health check to avoid running the SessionFactoryHealthCheck which fails during a DB upgrade. We have the option in the future to include other health checks if we want, but for now, it just runs the connection pool health check. I also removed the TemplateHealthCheck because I don't think we need it.
This PR also updates the postgres version in docker-compose to match the engine version in the database CloudFormation template in this PR https://github.com/dockstore/dockstore-deploy/pull/632.
Issue
SEAB-4900
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

Catching up, but if I understand correctly, the reason for the new endpoint is to create a healthcheck that doesn't fail during a database upgrade since a failed healthcheck during a database upgrade will cause the webservice container to be replaced (once? potentially more than once depending on how long the upgrade takes?)
Is that correct?

Yes that's correct. I also chose to create a new endpoint instead of getting rid of the default Dropwizard SessionFactoryHealthCheck in Dropwizard's endpoint because it might still be useful information.


Detect when pinned columns overflow the grid width

When one or more columns is pinned but its/their combined size exceeds the width of the grid, you can no longer scroll horizontally. The current work around is to reset the pinned columns, but detecting and handling this edge case would be better.

@Sleeckx can this be closed?


Please update npm package :-)

Hi,
thanks again for merging my request!
I'm using the npm package in node red for collecting metrics from my Vallox unit.
Could you please update on npm?
cheers, Thorsten

Done, see https://github.com/danielbayerlein/vallox-api/releases/tag/v1.0.0 🙂

Thank you!  :+1:


Bug: TableActionMenuPlugin in Playground has unexpected behavior

playground version: https://lexical-playground-3ezi6rvaa-fbopensource.vercel.app/

It would be nice to report the package version in the playground.

Steps To Reproduce

Merge Any header cell.
Unmerge merged cell.
Select cell that doesn't has background, and click "Remove Row Header"

https://github.com/facebook/lexical/assets/47362439/6a398ff3-61cd-40b0-a414-24095ce39024
The current behavior
It toggles TableCellHeaderStates.Row.
The expected behavior
All cell in Selected Row should add or delete TableCellHeaderStates.Row.
The solution I think

$unmergeCell should create cell with TableCellHeaderStates.Row / TableCellHeaderStates.Column according to the near row / column.
(related to 1) $insertTableRow__EXPERIMENTAL / $insertTableColumn__EXPERIMENTAL should create cell with TableCellHeaderStates.Row / TableCellHeaderStates.Column according to the near row / column.
toggleTableRowIsHeader / toggleTableColumnIsHeader should use TableCellNode.setHeaderStyles not TableCellNode.toggleHeaderStyles.

This was fixed some time ago. Closing.

Was there a modification to the merge logic that I'm not aware of?
Same behavior on https://lexical-playground-2p9vpui47-fbopensource.vercel.app/ .
And also no change on below.
https://github.com/facebook/lexical/blob/5319bf68fe1771d48b6a2cb5872bc246acd44fdf/packages/lexical-playground/src/plugins/TableActionMenuPlugin/index.tsx#L411
https://github.com/facebook/lexical/blob/5319bf68fe1771d48b6a2cb5872bc246acd44fdf/packages/lexical-playground/src/plugins/TableActionMenuPlugin/index.tsx#L454


Fix: solana stakes  clean handling

Problem

Returns no message if invalid pubkey(s) are provided.
Does not search for identity pubkeys.

Summary of Changes

Retrieval of matching vote account from identity/vote pubkey. If invalid pubkey(s) are provided, it will throw an error without continuing with valid ones.
Added separate progress bars for fetching vote accounts and for fetching stake accounts
returns a message if no stake accounts are found for the vote account.

I decided not to continue with pubkeys if some of them are invalid, because the message might go unnoticed by the user when a lot of stake accounts are displayed.
@mvines  @CriesofCarrots  Waiting for your reviews and your thoughts about my suggestion below.
(fyi, I've tested CLI with my changes - everything works as expected)
Suggestion
Should I change an argument name of <VOTE_ACCOUNT_PUBKEYS> to <VALIDATOR_ACCOUNT_PUBKEY> in the help description if $ solana stakes <> now supports both identity and vote pubkeys?
Also, I think if $ solana stakes is run without any pubkey, it shouldn't return all stake accounts. What about putting some limit (like a max of 50/100 displayed stake accounts) on?
Closes https://github.com/solana-labs/solana/issues/8441

Codecov Report
Attention: Patch coverage is 0% with 34 lines in your changes are missing coverage. Please review.

Project coverage is 82.1%. Comparing base (f291ca4) to head (1c13592).
Report is 21 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master     #797     +/-   ##
=========================================
- Coverage    82.1%    82.1%   -0.1%
=========================================
  Files         886      886
  Lines      236392   236412     +20
=========================================
- Hits       194274   194240     -34
- Misses      42118    42172     +54

@CriesofCarrots thanks a lot for your patience!


chore(main): release 1.0.2

:robot: I have created a release beep boop
1.0.2 (2024-02-09)
Bug Fixes

loosen trigger for production release (#315) (3746ade)
ops: loosen trigger for production release (3746ade)
release action trigger (#316) (18ff427)
Store analytics key in variables manager (#313) (eb7632f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/nader-eloshaiker/screen-geometry-app/releases/tag/v1.0.2 :sunflower:


config.json should be written to a sensible place

When you create a configuration using the config command, it "works" but it just drops a config.json file randomly where ever you ran the command from. It should save it in a sensible standard place and allow the user to override it with a command line option.

Closing and reopening here: https://github.com/InfluxCommunity/influxdb3-python-cli/issues/2


Issue when passing path_model_init argument to train_model in train_network.py

When we pass the path to an existing model to train_model function in network.py, we get an error because the function global_variables_initializer in line 328 doesn't take any argument.

@alzaia @jcohenadad I detected this, should I work on it?

@oumayb Yes it would be a good practice for you to start using the pull request pipeline. You can find the full guidelines in this wiki page: https://github.com/neuropoly/axondeepseg/wiki/Guidelines-for-contribution.

This was merged into dev_issue73 branch of PR #96, which got approved and already merged into master, so we can close this issue.


The library 'package:parallax_bg/parallax_bg.dart' is legacy, and should not be imported into a null safe library.

SETUP:
sdk: ">=2.12.0 <3.0.0"
parallax_bg: ^1.0.4
ISSUES: I receive errors -
"The library 'package:parallax_bg/parallax_bg.dart' is legacy, and should not be imported into a null safe library."
"Error: Cannot run with sound null safety, because the following dependencies don't support null safety:"
Can you make this for null safety?

Hi Kumar. Any luck making this null safe?

@jonnyplow
Thanks for reminding me. I totally forgot to update the library.
I have already made the changes & it will be up in few hours.

@jonnyplow
Null safety version is updated on pub. It will take few hours to officially verifying the package so it will be available soon.
Please test it & raise an issue if you face any problem.
Thanks

Thanks Kumar!! working now!


Insert block in sidekiq and handle system timeout and not ready error

Codecov Report

Merging #64 into develop will increase coverage by 0.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop      #64      +/-   ##
===========================================
+ Coverage    97.85%   97.87%   +0.01%
===========================================
  Files           60       61       +1
  Lines         1588     1601      +13
===========================================
+ Hits          1554     1567      +13
  Misses          34       34

Impacted Files
Coverage Δ

app/models/cita_sync/persist.rb
97.8% <100%> (+0.18%)
:arrow_up:

app/workers/save_block_worker.rb
100% <100%> (ø)

spec/models/cita_sync/persist_spec.rb
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Crash!!

Describe your bug here.
For some reason, the song crashes when I do it in storymode. Please help!!
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
I made an extension in the script, but it doesn't matter to the song

I pressed the wrong button


Using hamlet as storage is real and free

Hamlet can wear the captains jetpack, a 4 tile item.
Hamlet is a one tile item.
Free 3 tiles :godo:

just whitelist emergency oxygen and nothing else

Hamlet with jetpack is hilarious tbh. Considering Hamlet is a ghost role, whichever captain wants to use them as free inventory is feeling very confident.

You can also put it in a tablet jar.

don't forget that you can also put hamlet (and all animals with the 'tiny' tag) can fit into pill bottles + cigarette boxes. 1 storage slot for pill bottle  -->  10 rodents.


Tracking Issue: transfer essential repositories to haskellPackages infra to the NixOS organisation

There are a few haskell packages released on hackage and being managed in GitHub repositories in @peti's account which are tightly coupled with cabal2nix and/or the haskell infrastructure in nixpkgs. Future development for our haskell infrastructure in nixpkgs will require touching those repositories and releasing new versions to hackage. Such changes would be implementing changes to the package set generation (https://github.com/NixOS/cabal2nix/issues/499, https://github.com/NixOS/cabal2nix/issues/497) or adding a new platform (like aarch64-darwin in the near future).
The repos in question are (feel free to add any I've missed):

[x] https://github.com/peti/distribution-nixpkgs (hackage: https://hackage.haskell.org/package/distribution-nixpkgs)
[x] https://github.com/peti/jailbreak-cabal which is used for all doJailbreak overrides (hackage: https://hackage.haskell.org/package/jailbreak-cabal)
[x] https://github.com/peti/language-nix (hackage: https://hackage.haskell.org/package/language-nix)
[x] https://github.com/peti/hackage-db (hackage: https://hackage.haskell.org/package/hackage-db)
[x] https://github.com/peti/package-list

I don't think we currently would need access to all of the repositories, but I think it'd be a good idea to give @NixOS/haskell access to them, so we won't have to bother @peti whenever we have to change something for day-to-day nixpkgs operation.
As for what should be done I think it is a case of:

Adding the members of the haskell team as maintainers for the respective packages on hackage. Unfortunately we can't create an equivalent of the team there, so these lists will have to be updated manually. For that purpose we'll need to collect the hackage usernames of everyone involved.
Enable the haskell team to commit to the respective repositories either by

forking them into the NixOS organisation and using them as a new upstream or
transferring the repositories to the NixOS organisation.

Any comments and concerns are welcome!
cc @NixOS/haskell

Hey @peti, I hope you are happy about what we did in the last weeks and that we didn‘t step too much on your toes. Would be great if you could transfer those packages so that we don‘t need to bother you in the future. Of course any input you have will always be greatly appreciated.

I emailed Peter today to ask if he could take a look at this issue.

I have moved all of those repositories to the NixOS organization and transferred maintainer rights to the cabal2nix-owners and haskell teams. I've also added @cdepillabout as a maintainer for those packages an Hackage where applicable. I believe this gives Dennis the ability to add more maintainers as required. I would have added @maralorn and @sternenseemann, too, but I could not figure out your Hackage user names quickly. I hope this allows you guys to move forward without me blocking progress.

Thanks a lot @peti!

@maralorn @sternenseemann and @expipiplus1, if you guys let me know your Hackage usernames, I can add you as maintainers to all the relevant packages on Hackage.

I've added maralorn, sternenseemann, and expipiplus1 as maintainers on Hackage for:

https://hackage.haskell.org/package/hackage-db
https://hackage.haskell.org/package/language-nix
https://hackage.haskell.org/package/jailbreak-cabal
https://hackage.haskell.org/package/distribution-nixpkgs

However, @sternenseemann noticed that I am not a maintainer for cabal2nix on Hackage, so I will reach out to peti for that.

I've added maralorn, sternenseemann, and expipiplus1 as maintainers on Hackage for https://hackage.haskell.org/package/cabal2nix as well.
That should be all the libraries needed, so I will go ahead and close this issue.


react-native run-android error

react-native run-android error
stacktrace
for Android Gradle Plugin 3.0.0.
Android SDK Build Tools 26.0.2 will be used.
To suppress this warning, remove "buildToolsVersion '25.0.1'" from your build.gradle file, as each version of the Android Gradle Plugin now has a default version of the build tools.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Get more help at https://help.gradle.org

BUILD FAILED in 3s
65 actionable tasks: 1 executed, 64 up-to-date
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

在android/app/build.gradle添加
dependencies {
..
compile project(':rn-splash-screen')
}
问题解决


Linters and Checkers

This change adds several linters and checkers to our gradle

checkstyle
findbugs
pmd

Wow, quite the spring, er summer, cleaning. LGTM


search component

https://github.com/opencollective/opencollective/issues/828

Closing in favor of #352


add documentation for ContentMetaData

🗄 Docs report
Description
 A clear and concise description of the problem...
🔬 Minimal Reproduction
What's the affected URL?**

Reproduction Steps**

Expected vs Actual Behavior**

📷Screenshot

🔥 Exception or Error

🌍 Your Environment
Browser info

Anything else relevant?

@SanderElias I think this is a duplicate issue, see #1087


Add Bobaopera Testnet docs

Why we need this?
We deployed on Bobaopera, so need to add docs for it.
Overview
Add Bobaopera Testnet docs and a file that contains all registered contract addresses
Changes

Add Bobaopera Testnet URLs and links
Add a file that contains all registered contract addresses

Codecov Report

:exclamation: No coverage uploaded for pull request base (docs-in-monrepo@ee4b15b). Click here to learn what that means.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##             docs-in-monrepo     #229   +/-   ##
==================================================
  Coverage                   ?   47.14%
==================================================
  Files                      ?       99
  Lines                      ?     3875
  Branches                   ?      761
==================================================
  Hits                       ?     1827
  Misses                     ?     2048
  Partials                   ?        0

Flag
Coverage Δ

boba-contracts
20.39% <0.00%> (?)

contracts
77.71% <0.00%> (?)

core-utils
86.77% <0.00%> (?)

data-transport-layer
30.85% <0.00%> (?)

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

Continue to review full report at Codecov.

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

Do you still have the artifacts of the deployment? Please upload them too in the repo. Ignore if you have :)

I created another PR for the deployment files - https://github.com/bobanetwork/boba/pull/234

@java-spaces should give a thumbs up in terms of language I think!

@Boyuan-Chen This commentary is great -- but I would make one adjustment. This does a great job describing what was solved, but it would be even better if it described why the change was needed in the first place. And then how that problem was solved with the changes made in the PR.

@Boyuan-Chen This commentary is great -- but I would make one adjustment. This does a great job describing what was solved, but it would be even better if it described why the change was needed in the first place. And then how that problem was solved with the changes made in the PR.

Added


Added configurable style for Media Image

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #[issue number]
Description
Currently Media Image style is not defined so it's not configurable like alignment , size etc. So need to add configurable style attribute for Image.
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: Bug fix
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct.
[x] I have read the Contributing page.
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
[x] I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

@khyativyasargus I haven't check your PR yet, but since you're working on this, can you also add configurable styling based on the issue below?
https://github.com/google/android-fhir/issues/1874


Welcome screen - Button labels should be: "Continue with..." and not "Login with..."

Verified as done.
Checked on the Dev env. v0.18.1-2
Devices:
Desktop - Google Chrome 81.0
Redmi Go // Android 8.1.0


Y152 - Grouping components by feature

As the example application structure (Y152) there is a folder called components/ containing a calendar and a user-profile.
I'm also noticing a feature area for people (people/ folder). Wouldn't it make more sense to put the user-profile component inside the people feature area?
I know these rules aren't written in stone, but is there any advantage of using one strategy over another?

I think the components/  directory is supposed to hold stuff that is re-usable across all feature areas.
For example, the people feature could be a CRUD for people, but you're likely to show the author of a post (another feature of your app) using the userProfile directive.

Ok, makes sense. So, but if you write a component that's related only to a specific feature (for example people), it would be a good idea to add it to the same folder, right?

I was confused on this and found the explanation that @gustavohenke gave to be helpful. I think this should be clearly explained in the guide along with examples to show the important of "cross cutting" concerns.

Ok, makes sense. So, but if you write a component that's related only to a specific feature (for example people), it would be a good idea to add it to the same folder, right?

If you are only going to use it within that feature, then I think that's fine.

if (component.isRelatedTo(feature)) {
    component.livesIn(feature);
} else {
    component.liveIn(appLevelComponentFolder);
}


Fix search bug with Sphinx>=7.2

Fixes #274
See relevant change in sphinx: https://github.com/sphinx-doc/sphinx/commit/8e730ae303ae686705ea12f44ef11da926a87cf5

I can confirm that this works with Sphinx v8.1.3 as per the deployed preview:
https://github.com/user-attachments/assets/1073506b-179c-4dda-8111-7037695be175
and it also works with an older version of Sphinx e.g. 7.1.2
https://github.com/user-attachments/assets/aaae44cc-66b1-4acb-9e0b-4a2d5b548fc1

Thank you all!
Should we try to document any of this somewhere? Either in the docs or the readme?


runtime: go1.5beta1 on Windows 64 with CGO: signal arrived during external code execution

Go version: go1.5beta1 windows/amd64
OS: Windows 7 SP1 64 bits
When trying to connect to Oracle using https://github.com/mattn/go-oci8 or https://github.com/go-goracle/goracle I get the following errors:
go-oci8:
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0
signal arrived during external code execution

github.com/mattn/go-oci8._Cfunc_WrapOCIEnvCreate(0x1, 0x0, 0x0, 0x0, 0x0)
        ??:0 +0x5a
github.com/mattn/go-oci8.(*OCI8Driver).Open(0x6dc678, 0x5f9560, 0x1d, 0x0, 0x0, 0x0, 0x0)
        C:/Projetos/Go/src/github.com/mattn/go-oci8/oci8.go:531 +0x4a8
database/sql.(*DB).conn(0xc082070140, 0x44c801, 0xc082065ea0, 0x0, 0x0)
        c:/go/src/database/sql/sql.go:710 +0x458
database/sql.(*DB).Ping(0xc082070140, 0x0, 0x0)
        c:/go/src/database/sql/sql.go:491 +0x3d
main.main()
        C:/projetos/go/exemplos-Go/oracle-connect.go:16 +0x16a

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
        c:/go/src/runtime/asm_amd64.s:1696 +0x1

goroutine 5 [chan receive]:
database/sql.(*DB).connectionOpener(0xc082070140)
        c:/go/src/database/sql/sql.go:634 +0x4c
created by database/sql.Open
        c:/go/src/database/sql/sql.go:481 +0x33d
rax     0x22fd30
rbx     0xc082065a20
rcx     0x22fd30
rdi     0xc082065a20
rsi     0x6b91e0
rbp     0x22fd50
rsp     0x22fce8
r8      0x0
r9      0x0
r10     0xc082008d80
r11     0x55555555555555
r12     0x3
r13     0x6185a2
r14     0x38
r15     0x0
rip     0x0
rflags  0x10246
cs      0x33
fs      0x53
gs      0x2b
exit status 2

goracle:
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0
signal arrived during external code execution

gopkg.in/goracle.v1/oracle._Cfunc_OCIEnvNlsCreate(0xc082054bd0, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xffffff00000000, 0x0)
        ??:0 +0x43
gopkg.in/goracle.v1/oracle.NewEnvironment(0x6620c0, 0x0, 0x0)
        C:/Projetos/Go/src/gopkg.in/goracle.v1/oracle/environment.go:99 +0x266
gopkg.in/goracle.v1/oracle.NewConnection(0x6b5fa0, 0x6, 0x6b5fa7, 0x7, 0x6b5faf, 0xe, 0x6b5f00, 0xc08200e400, 0x0, 0x0)
        C:/Projetos/Go/src/gopkg.in/goracle.v1/oracle/connection.go:132 +0xd1
gopkg.in/goracle%2ev1.(*Driver).Open(0x7b10a0, 0x6b5fa0, 0x1d, 0x0, 0x0, 0x0, 0x0)
        C:/Projetos/Go/src/gopkg.in/goracle.v1/driver.go:255 +0x166
database/sql.(*DB).conn(0xc08206c140, 0x44f601, 0xc082061ea0, 0x0, 0x0)
        c:/go/src/database/sql/sql.go:710 +0x458
database/sql.(*DB).Ping(0xc08206c140, 0x0, 0x0)
        c:/go/src/database/sql/sql.go:491 +0x3d
main.main()
        C:/projetos/go/exemplos-Go/oracle-connect.go:17 +0x16a

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
        c:/go/src/runtime/asm_amd64.s:1696 +0x1

goroutine 5 [chan receive]:
database/sql.(*DB).connectionOpener(0xc08206c140)
        c:/go/src/database/sql/sql.go:634 +0x4c
created by database/sql.Open
        c:/go/src/database/sql/sql.go:481 +0x33d
rax     0xc082054bd0
rbx     0x0
rcx     0xc082054bd0
rdi     0x0
rsi     0x0
rbp     0x22fda0
rsp     0x22fd18
r8      0x0
r9      0x0
r10     0x0
r11     0x0
r12     0x10
r13     0x6e15bc
r14     0x8
r15     0x2
rip     0x0
rflags  0x10202
cs      0x33
fs      0x53
gs      0x2b
exit status 2

Test code is below. Drivers need to be installed first.
package main

import (
	"database/sql"
	"fmt"
	_ "github.com/mattn/go-oci8"
	_ "gopkg.in/goracle.v1"
)

func main() {
	// Change to "goracle" to test Goracle
	db, err := sql.Open("oci8"<EMAIL_ADDRESS>	if err != nil {
		fmt.Println(err)
		return
	}
	defer db.Close()
	err = db.Ping()
	if err != nil {
		fmt.Println(err)
		return
	}
}

This works using Go 1.4.2. It also works if I use the 32 bit version of Go 1.5beta1 on Windows, or if I use the 64 bit version on Linux.

Oh, and there is no need for an Oracle database, the error happens before trying to connect.

The error message suggests that the C code is calling a NULL pointer.

As far as I can tell this is what is expected to happen when an exception occurs with PC == 0.  I don't know if PC == 0 is correct, and I don't know what has changed here since Go 1.4.
CC @alexbrainman

Your program raised EXCEPTION_ACCESS_VIOLATION exception somewhere inside your C WrapOCIEnvCreate function. EXCEPTION_ACCESS_VIOLATION means memory access error - most common would be dereferencing 0 pointer. You can try and debug this yourself - just insert extra printf statements inside of WrapOCIEnvCreate to try and understand what is happening. Is error happening in WrapOCIEnvCreate? Or is it happening inside external OCIEnvCreate function? If it happens inside of OCIEnvCreate, print its parameters and make sure they are correct.
Alex

I did some investigating, but first a small disclamier: I have very little knowledge of C and CGO, so I might be missing something obvious.
Ok, I'm using go-oci8 to debug, and the function that is causing the error is this: https://github.com/mattn/go-oci8/blob/master/oci8.go#L142-161
I modified it to print values that are passed to OCIEnvCreate:
static ret2ptr
WrapOCIEnvCreate(ub4 mode, size_t extra) {
  ret2ptr vvv = {NULL, NULL, 0};

  void *ptr;
  if (extra == 0)  {
    ptr = NULL;
  } else {
    ptr = &vvv.extra;
  }
  printf("OciEnv: %p\n", (OCIEnv**)(&vvv.ptr));
  printf("Mode: %d\n", mode);
  printf("Extra: %d\n", extra);
  printf("Extra Ptr: %p\n", ptr);
  vvv.rv = OCIEnvCreate(
    (OCIEnv**)(&vvv.ptr),
    mode,
    NULL,
    NULL,
    NULL,
    NULL,
    extra,
    ptr);
  printf("worked\n");
  return vvv;
}

And this is the output:
Go 1.5:
OciEnv:<PHONE_NUMBER>22FD60
Mode: 1
Extra: 0
Extra Ptr:<PHONE_NUMBER>000000
Exception 0xc0000005 0x0 0xd7d526 0x69c018
PC=0x69c018
signal arrived during external code execution

github.com/mattn/go-oci8._Cfunc_WrapOCIEnvCreate(0x1, 0x0, 0x0, 0x0, 0x0)
        ??:0 +0x5a
github.com/mattn/go-oci8.(*OCI8Driver).Open(0x6db678, 0x5f8ba0, 0x1c, 0x0, 0x0,
0x0, 0x0)
        c:/projetos/go/src/github.com/mattn/go-oci8/oci8.go:538 +0x4a8
database/sql.(*DB).conn(0xc08206a140, 0x44be01, 0xc08205bea0, 0x0, 0x0)
        c:/go/src/database/sql/sql.go:710 +0x458
database/sql.(*DB).Ping(0xc08206a140, 0x0, 0x0)
        c:/go/src/database/sql/sql.go:491 +0x3d
main.main()
        C:/Projetos/Go/oracle-connect.go:17 +0x16a

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
        c:/go/src/runtime/asm_amd64.s:1696 +0x1

goroutine 5 [chan receive]:
database/sql.(*DB).connectionOpener(0xc08206a140)
        c:/go/src/database/sql/sql.go:634 +0x4c
created by database/sql.Open
        c:/go/src/database/sql/sql.go:481 +0x33d
rax     0x1c
rbx     0xc08205ba20
rcx     0x22fd60
rdi     0x22fd60
rsi     0x0
rbp     0x1
rsp     0x22fd18
r8      0x0
r9      0x0
r10     0x0
r11     0x246
r12     0x0
r13     0xc08205bfa0
r14     0x38
r15     0x0
rip     0x69c018
rflags  0x10246
cs      0x33
fs      0x53
gs      0x2b

Go 1.4:
OciEnv:<PHONE_NUMBER>22FE60
Mode: 1
Extra: 0
Extra Ptr:<PHONE_NUMBER>000000
worked

Apparently the parameters are passed correctly.
The problem is on the line that calls OCIEnvCreate, however I monitored calls to API using a program called API Monitor V2, and while the 1.4 version shows the DLL being called, the 1.5 version shows nothing. So the problem is most likely inside the C code in oci8.go.

I also tried forcing an error passing an invalid parameter in 1.4, but I got a treated message from this code block:
if rv := C.WrapOCIEnvCreate(
		C.OCI_DEFAULT|C.OCI_THREADED,
		0); rv.rv != C.OCI_SUCCESS && rv.rv != C.OCI_SUCCESS_WITH_INFO {
		// TODO: error handle not yet allocated, we can't get string error from oracle
		return nil, errors.New("can't OCIEnvCreate")

And the call is also shown in API Monitor.
Is there anything else I can do to help identify the problem? In the meantime I'll see if I can simulate it with a simpler DLL call.

Unfortunately I don't know how to help you. In go1.5 cgo changed considerably. Go used to always link final executable, but now it calls gcc if you use cgo. I don't know much about gcc. You can revert to old way of linking by asking go command to use "internal" linker. I think you need to say:
go build -gcflags "-linkmode internal" ...

Another alternative might be to use my github.com/alexbrainman/odbc driver. I haven't used it for Oracle. But I don't see why it wouldn't work.
Another option would be for you to call into Oracle DLL directly with syscall.Syscall. Probably too much work if you start from scratch. But you never know.
I also wouldn't give up on what you have. There might be bugs in the library you use. Make your example as small as possible. Check that things work every step of the way (you have call monitor, check all values are passed and returned correctly and so on). And add things slowly.
Alex

@alexbrainman I tried your first suggestion linking using the -linkmode flag and it worked:
go build -ldflags "-linkmode internal" oracle-connect.go

The strange thing is that in one of my machines it started working all of a sudden, even if I don't pass the -linkmode flag. I tried forcing external and internal and both work. I created a simpler package that only calls this first method of the OCI.dll, but I am still trying to get consistent results.
As for ODBC, my application needs to query and format up to 5 million database rows as fast as possible. Right now the speed is around 35k rows per second, and from my previous experience I don't think ODBC will come even close to that. But I will try your driver, it might surprise me.

I created a very simple application that reproduces the problem with no external dependencies.
To test it:
go get github.com/ricsmania/ocitest
cd %GOPATH%\src\ricsmania\ocitest
go run oci.go

Sure I will try it. Thank you.
Alex

@ricsmania Thanks for that very small program. It is possible that what has changed is whether the cgo call executes in the main (program startup) thread. Perhaps the OCI DLL requires that the call be started from the main thread. If you put
func init() {
runtime.LockOSThread()
}
in your program, then func main will be forced to run in the main OS thread. It would be interesting to see if that changes the behavior reliably.

@rsc Thanks for your suggestion. Unfortunately nothing changed, I still get the error.

That does not build on my pc:
C:\dev\src\github.com\ricsmania\ocitest>go build
# github.com/ricsmania/ocitest
C:\DOCUME~1\brainman\LOCALS~1\Temp\go-build303634482\github.com\ricsmania\ocitest\_obj\oci.cgo2.o: In function `CreateEnv':
c:/dev/src/github.com/ricsmania/ocitest/oci.go:14: undefined reference to `OCIEnvCreate'
collect2.exe: error: ld returned 1 exit status

Alex

you may need to put oci8.pc in your $PKG_CONFIG_PATH.

@alexbrainman could you please try setting CGO_CFLAGS and CGO_LDFLAGS to an absolute path before building?
set CGO_CFLAGS=-I%GOPATH%\github.com\ricsmania\ocitest
set CGO_LDFLAGS=-L%GOPATH%\github.com\ricsmania\ocitest
Thanks

Still get the same error message:
C:\dev\src\github.com\ricsmania\ocitest>set CGO_CFLAGS=-I%GOPATH%\github.com\ricsmania\ocitest

C:\dev\src\github.com\ricsmania\ocitest>set CGO_LDFLAGS=-L%GOPATH%\github.com\ricsmania\ocitest

C:\dev\src\github.com\ricsmania\ocitest>set | find "CGO_"
CGO_CFLAGS=-Ic:\dev\github.com\ricsmania\ocitest
CGO_LDFLAGS=-Lc:\dev\github.com\ricsmania\ocitest

C:\dev\src\github.com\ricsmania\ocitest>go build
# github.com/ricsmania/ocitest
C:\DOCUME~1\brainman\LOCALS~1\Temp\go-build110287182\github.com\ricsmania\ocitest\_obj\oci.cgo2.o:oci.cgo2.c:(.text+0x4c): undefined reference to `OCIEnvCreate'

collect2.exe: error: ld returned 1 exit status

C:\dev\src\github.com\ricsmania\ocitest>

Alex

@alexbrainman I'm sorry, I forgot a part, the path should be
set CGO_CFLAGS=-IC:\dev\src\github.com\ricsmania\ocitest\oracle
set CGO_LDFLAGS=-LC:\dev\src\github.com\ricsmania\ocitest\oracle
They should point to the folder that has oci.dll and several .h files.

Also, after building you will probably have to add this same path to your %PATH% before executing.

Still broken:
C:\dev\src\github.com\ricsmania\ocitest>set CGO_CFLAGS=-IC:\dev\src\github.com\ricsmania\ocitest\oracle

C:\dev\src\github.com\ricsmania\ocitest>set CGO_LDFLAGS=-LC:\dev\src\github.com\ricsmania\ocitest\oracle

C:\dev\src\github.com\ricsmania\ocitest>go build
# github.com/ricsmania/ocitest
C:\DOCUME~1\brainman\LOCALS~1\Temp\go-build119391970\github.com\ricsmania\ocitest\_obj\oci.cgo2.o:oci.cgo2.c:(.text+0x4c): undefined reference to `OCIEnvCreate'

collect2.exe: error: ld returned 1 exit status

C:\dev\src\github.com\ricsmania\ocitest>

Alex

@ricsmania I was able to build your program by running 'go build' in the github.com/ricsmania/ocitest directory, and then after downloading some DLLs from Oracle and then downloading msvcr100.dll from some random site on the internet, I was able to run the program, and it prints "worked".
This is with Windows 7 (ver prints "Microsoft Windows [Version 6.1.7601]", which the internet says is Windows 7).
I did notice that the file github.com/ricsmania/ocitest/oracle/oci.dll is a 32-bit DLL, so that's not going to work. But I assume you copied the wrong one off your system and that on your system you are still using a 64-bit DLL, just not that one. When I tried to run with the 32-bit DLL I got exit code 0xc000007b. (Missing DLL is 0xc0000135.)
My guess is that something is wrong with your Windows 7 system, possibly with the version of oci.dll that you have installed. The one that worked for me was the "Instant Client Package - Basic", from http://www.oracle.com/technetwork/topics/winx64soft-089540.html. Please try extracting that and put the instantclient_12_1 directory first in your %PATH%. Thanks.

@rsc I still have this problem on some machines. I recently installed Windows 10 from scratch and the problem is happening on Go 1.5 with 3 different drivers:
https://github.com/mattn/go-oci8
https://github.com/go-goracle/goracle
https://github.com/rana/ora
If I use "-linkmode internal" or create the environment variable GO_EXTLINK_ENABLED=0 the problem goes away, so I'm pretty sure it has to do with the linking mode.
The problem is that I can't reliably reproduce it, it happens on some machines but not on others. I got to reproduce it on a VM, however I don't think I can legally distribute a Windows VM. If I reproduce it on an EC2 or Azure instance, would you be able to help us investigate it?


'PlatformAppBar' can't be assigned to the parameter type 'PreferredSizeWidget'

I am getting this error trying to use PlatformAppBar, what am I doing wrong?

Solved: I was not using the PlatformScaffold


Add json schema for CW Alarm period when in the AWS namespace

Issue #, if available:
Description of changes:

Add json schema for CW Alarm period when in the AWS namespace

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This will fix #1059 when v1 is fully released.


nuclei: 3.1.3 -> 3.1.4

Diff: https://github.com/projectdiscovery/nuclei/compare/v3.1.3...v3.1.4
Changelog: https://github.com/projectdiscovery/nuclei/releases/tag/v3.1.4
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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


python3Packages.apache-airflow: 2.2.4 -> 2.3.3

Description of changes
Apache Airflow v2.3.3 included update to flask-appbuilder to version 4.x.x, which gets rid of old flask version 1.x.x - source of the old dependencies.
Changed source of src (by adding fetchSubmodules = true;) to include tests, since packaged sources don't include them.
The large amount of disabled tests is due to actually including the tests in the first place.
Included small amount of pinned dependencies to an older version, but reduced the number of "jailbreaks".
Removed the broken flag 🎉
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This is upgrading jupytext too, but I cannot find any place where it is used by airflow, unless I am missing something.

This is upgrading jupytext too, but I cannot find any place where it is used by airflow, unless I am missing something.

Airflow upgrade required update markdown-it-py version 2.0.1 -> 2.1.0 which is a dependency of jupytext and broke some tests.
All necessary changes were made in the first commit, the second one was resolving an issue from nixpkgs-review

nixpkgs-review fails to eval:
$ nixpkgs-review pr 181234
$ git -c fetch.prune=false fetch --no-tags --force https://github.com/NixOS/nixpkgs master:refs/nixpkgs-review/0 pull/181234/head:refs/nixpkgs-review/1
$ git worktree add /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs dbe1337750f324137ca2ba78f20a3be00e16481a
Preparing worktree (detached HEAD dbe1337750f)
Updating files: 100% (31017/31017), done.
HEAD is now at dbe1337750f gh: 2.14.0 -> 2.14.1
$ nix-env --option system x86_64-darwin -f /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs -qaP --xml --out-path --show-trace
$ git merge --no-commit --no-ff 6138c9bdd52329f2afac4d3d197d0b582fcd3ea7
Automatic merge went well; stopped before committing as requested
$ nix-env --option system x86_64-darwin -f /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs -qaP --xml --out-path --show-trace --meta
error: path '/nix/store/l7c3dbl497wwz9aw5y0l4ks988bsl31c-source.drv' is not valid

       … while realising the context of path '/nix/store/6y39vrglz811h05k7ycr34nx11wjpip9-source/airflow/www/package.json'

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/development/python-modules/apache-airflow/frontend.nix:9:36:

            8|   };
            9|   packageJSON = builtins.fromJSON (builtins.readFile "${src}/package.json");
             |                                    ^
           10|   patchedPackageJSON = builtins.toFile "package.json" (builtins.toJSON (packageJSON // additionalFields));

       … while evaluating the attribute 'meta.license'

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/development/tools/yarn2nix-moretea/yarn2nix/default.nix:382:9:

          381|         version = packageJSON.version or "";
          382|         license = if packageJSON ? license then getLicenseFromSpdxId packageJSON.license else "";
             |         ^
          383|       } // (attrs.meta or {});

       … while evaluating 'toList'

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/lib/lists.nix:284:12:

          283|   */
          284|   toList = x: if isList x then x else [x];
             |            ^
          285|

       … from call site

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:54:15:

           53|     hasLicense attrs &&
           54|     isUnfree (lib.lists.toList attrs.meta.license);
             |               ^
           55|

       … while evaluating 'isUnfree'

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:50:14:

           49|
           50|   isUnfree = licenses: lib.lists.any (l: !l.free or true) licenses;
             |              ^
           51|

       … from call site

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:54:5:

           53|     hasLicense attrs &&
           54|     isUnfree (lib.lists.toList attrs.meta.license);
             |     ^
           55|

       … while evaluating 'hasUnfreeLicense'

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:52:22:

           51|
           52|   hasUnfreeLicense = attrs:
             |                      ^
           53|     hasLicense attrs &&

       … from call site

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:80:5:

           79|   hasDeniedUnfreeLicense = attrs:
           80|     hasUnfreeLicense attrs &&
             |     ^
           81|     !allowUnfree &&

       … while evaluating 'hasDeniedUnfreeLicense'

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:79:28:

           78|   # `allowUnfreePredicate` function.
           79|   hasDeniedUnfreeLicense = attrs:
             |                            ^
           80|     hasUnfreeLicense attrs &&

       … from call site

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:329:12:

          328|     }
          329|     // (if hasDeniedUnfreeLicense attrs && !(hasAllowlistedLicense attrs) then
             |            ^
          330|       { valid = "no"; reason = "unfree"; errormsg = "has an unfree license (‘${showLicense attrs.meta.license}’)"; }

       … while evaluating 'checkValidity'

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:321:19:

          320|   # Along with a boolean flag for each reason
          321|   checkValidity = attrs:
             |                   ^
          322|     {

       … from call site

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:353:18:

          352|   assertValidity = { meta, attrs }: let
          353|       validity = checkValidity attrs;
             |                  ^
          354|     in validity // {

       … while evaluating 'assertValidity'

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/check-meta.nix:352:20:

          351|
          352|   assertValidity = { meta, attrs }: let
             |                    ^
          353|       validity = checkValidity attrs;

       … from call site

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:403:14:

          402|
          403|   validity = checkMeta { inherit meta attrs; };
             |              ^
          404|

       … while evaluating the attribute 'postInstall' of the derivation 'python3.10-apache-airflow-2.3.3'

       at /Users/smancill/.cache/nixpkgs-review/pr-181234-1/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:270:7:

          269|     // (lib.optionalAttrs (attrs ? name || (attrs ? pname && attrs ? version)) {
          270|       name =
             |       ^
          271|         let

       … while querying the derivation named 'apache-airflow-2.3.3'
https://github.com/NixOS/nixpkgs/pull/181234 failed to build
$ git worktree prune


ALTER: identifier resolution

For the ALTER statement, if the new target paragraph (so after the TO) is an identifier, is the value of that identifier evaluated at ALTER, or when the altered paragraph is performed?
In the following example:
...
DATA DIVISION.
    01 TARGET PICTURE IS X.
PROCEDURE DIVISION.
    MOVE "B" TO TARGET.
    ALTER A TO PROCEED TO TARGET.
    MOVE "C" TO TARGET.

    STOP.
C.
    DISPLAY "C" WITH NO ADVANCING.

Would this display "B" or "C"?

According to the definition of ALTER, both of its arguments are "procedure" (paragraph) names, so the easy answer is that your code should lead to a compiler error at the second line of PROCEDURE DIVISION. There is a version of GO TO where a developer can use a field name instead, but there is no such version for ALTER.
PS: can I haz access to https://github.com/Michael-Janssen-dev/baby-cobol-compiler-v3?

Thank you. My understanding was that "ProcedureName" in the grammar meant that it was an identifier containing a procedure name, or an actual procedure name, because the same symbol is used in the grammar for GO TO.
Access has been granted 👍🏻


Rewrite all code in C++/GDNative

This will allow using this addon not only in mono builds.
It should also increase performance.
But at the moment I have other goals. Most likely, I will update this addon when I start actively using the 3D capabilities of Godot.

Done in https://github.com/DmitriySalnikov/godot_debug_draw_3d
This repository is now obsolete.


Cannot create a new 4.7.0-0.okd-2021-08-22-163618 cluster with oVirt backend

Describe the bug
Cannot create a cluster with oVirt backend with release. Deployment fails during the bootstrap process.
Version
4.7.0-0.okd-2021-08-22-163618
oVirt Backend
Client OS: RHEL 8.4
How reproducible
100%
Log bundle
I can't get a decent log bundle, so I'm dumping what I have on the output and some basic commands that I've tried:
INFO Obtaining RHCOS image file from 'https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/34.20210711.3.0/x86_64/fedora-coreos-34.20210711.3.0-openstack.x86_64.qcow2.xz?sha256=0c7034702363cc04f34c6ef7a7019fabe611c92f34ecb3175fff509b339a05cb'
INFO The file was found in cache: /home/ferrao/.cache/openshift-installer/image_cache/dca49b280428f9090cb39cda82f6e4d8. Reusing...
INFO Creating infrastructure resources...
INFO Waiting up to 20m0s for the Kubernetes API at https://api.okd.versatushpc.com.br:6443...
INFO API v1.20.0-1093+4593a24e8fd58d-dirty up
INFO Waiting up to 30m0s for bootstrapping to complete...
ERROR Cluster operator authentication Degraded is True with IngressStateEndpoints_MissingSubsets::OAuthRouteCheckEndpointAccessibleController_SyncError::OAuthServerDeploymeyment_DeploymentAvailableReplicasCheckFailed::OAuthServerRoute_InvalidCanonicalHost::OAuthServiceCheckEndpointAccessibleController_SyncError::OAuthServiceEndpointsCheckEdonndpointAccessibleController_SyncError::OAuthVersionDeployment_GetFailed::Route_InvalidCanonicalHost::WellKnownReadyController_SyncError: OAuthServiceCheckEndpointAccessienobleControllerDegraded: Get "https://<IP_ADDRESS>:443/healthz": dial tcp <IP_ADDRESS>:443: connect: connection refused
ERROR OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready
ERROR IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server
ERROR WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap "oauth-openshift" not found (checkak authentication operator, it is supposed to create this)
ERROR OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address
ERROR RouteDegraded: no ingress for host oauth-openshift.apps.okd.versatushpc.com.br in route oauth-openshift in namespace openshift-authentication
ERROR OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps "oauth-openshift" not found
ERROR OAuthServerDeploymentDegraded: deployments.apps "oauth-openshift" not found
ERROR OAuthServerRouteDegraded: no ingress for host oauth-openshift.apps.okd.versatushpc.com.br in route oauth-openshift in namespace openshift-authentication
INFO Cluster operator authentication Available is False with OAuthServiceCheckEndpointAccessibleController_EndpointUnavailable::OAuthServiceEndpointsCheckEndpointAccessiblebleController_EndpointUnavailable::OAuthVersionDeployment_MissingDeployment::ReadyIngressNodes_NoReadyIngressNodes::WellKnown_NotReady: OAuthServiceEndpointsCheckEndpoinAcstAccessibleControllerAvailable: Failed to get oauth-openshift enpoints
INFO ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).
INFO OAuthServiceCheckEndpointAccessibleControllerAvailable: Get "https://<IP_ADDRESS>:443/healthz": dial tcp <IP_ADDRESS>:443: connect: connection refused
INFO WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap "oautauth-openshift" not found (check authentication operator, it is supposed to create this)
INFO Cluster operator baremetal Disabled is True with UnsupportedPlatform: Nothing to do on this Platform
INFO Cluster operator console Progressing is True with DefaultRouteSync_FailedAdmitDefaultRoute::OAuthClientSync_FailedHost: DefaultRouteSyncProgressing: route "console"is is not available at canonical host []
INFO OAuthClientSyncProgressing: route "console" is not available at canonical host []
INFO Cluster operator console Available is Unknown with NoData:
INFO Cluster operator image-registry Available is False with NoReplicasAvailable: Available: The deployment does not have available replicas
INFO ImagePrunerAvailable: Pruner CronJob has been created
INFO Cluster operator image-registry Progressing is True with DeploymentNotCompleted: Progressing: The deployment has not completed
ERROR Cluster operator image-registry Degraded is True with Unavailable: Degraded: The deployment does not have available replicas
INFO Cluster operator ingress Available is False with IngressUnavailable: Not all ingress controllers are available.
INFO Cluster operator ingress Progressing is True with Reconciling: Not all ingress controllers are available.
ERROR Cluster operator ingress Degraded is True with IngressControllersDegraded: Some ingresscontrollers are degraded: ingresscontroller "default" is degraded: DegradedCondhonditions: One or more other status conditions indicate a degraded state: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status conditionstt set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.), DeploymentReplicasMinAvailable=False (DeploymentMinimumpcNReplicasNotMet: 0/2 of replicas are available, max unavailable is 1)
INFO Cluster operator insights Disabled is False with AsExpected:
INFO Cluster operator kube-apiserver Progressing is True with NodeInstaller: NodeInstallerProgressing: 2 nodes are at revision 0; 1 nodes are at revision 3; 0 nodes haveaca achieved new revision 6
INFO Cluster operator kube-storage-version-migrator Available is False with _NoMigratorPod: Available: deployment/migrator.openshift-kube-storage-version-migrator: no repliplicas are available
ERROR Cluster operator monitoring Degraded is True with UpdatingconfigurationsharingFailed: Failed to rollout the stack. Error: running task Updating configuration sharingng failed: failed to retrieve Prometheus host: getting Route object failed: routes.route.openshift.io "prometheus-k8s" not found
INFO Cluster operator monitoring Available is False with :
INFO Cluster operator monitoring Progressing is True with RollOutInProgress: Rolling out the stack.
INFO Cluster operator network ManagementStateDegraded is False with :
INFO Cluster operator network Progressing is True with Deploying: Deployment "openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
INFO Pulling debug logs from the bootstrap machine
INFO Bootstrap gather logs captured here "/home/ferrao/okd/log-bundle-20210825022725.tar.gz"
FATAL Bootstrap failed to complete: failed to wait for bootstrapping to complete: timed out waiting for the condition

# export KUBECONFIG=auth/kubeconfig
# oc get clusterversion
The connection to the server api.okd.versatushpc.com.br:6443 was refused - did you specify the right host or port?
# oc login -u kubeadmin -p RNhih-aIbob-fCd7R-pbckW // Fetched the password from ./auth/kubeadmin-password
error: dial tcp <IP_ADDRESS>:6443: connect: connection refused - verify you have provided the correct host and port and that the server is currently running.

For oc adm must-gather all the errors are available on this paste:
https://pastebin.com/nttN8hk9
Thanks.

Hi @vrutkovs I'm trying to understand/debug why it is failing. I'm doing my best to add the correct and required information to see if this a duplicate or not.

after the change

SDN change? The duped bug could not be specific to OVN.

Yes, I destroyed the cluster, created a new install-config.yaml, changed from OVNKubernetes to OpenShiftSDN and tried to create the cluster again.

In any case, #483 has log bundle attached and this report doesn't, so its not useful

I'm trying to understand how #483 relates to this but I really can't. I don't know if the lack of open-vm-tools would do any difference since the provisioner is oVirt.
Finally back on track, I tried to generate what I think it is the log bundle but it's not generating:
# okd ./openshift-install gather bootstrap --dir=./installokd --log-level=info
FATAL failed to get bootstrap and control plane host addresses from "installokd/terraform.tfstate": failed to lookup bootstrap: resource not found

I'm following the documentation available on this link to generate the logs.
I also tried passing the master IP addresses (that DHCP gave) but was a no go either:
./openshift-install gather bootstrap --dir=installokd --master <IP_ADDRESS> --master <IP_ADDRESS> --master <IP_ADDRESS>

What I could fetch was oc adm must-gather, and it's available here:
http://www.if.ufrj.br/~ferrao/okd
If there's anything else that I can do please let me know, and sorry for any inconvenience.
Thank you.

Sorry, mistyped - not #483 but #783. Check recent 4.7 nigthlies, it should have a fix for this

Hi @vrutkovs thank you! With the latest nightlies I could install the cluster. It worked on first try:
# okd ./openshift-install create cluster --dir=installokd --log-level=info
INFO Consuming Install Config from target directory
INFO Obtaining RHCOS image file from 'https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/34.20210626.3.1/x86_64/fedora-coreos-34.20210626.3.1-openstack.x86_64.qcow2.xz?sha256=c2364a4ddb747d23263dec398d956799d2362983fb8fc257a5ab1d87b604683d'
INFO Creating infrastructure resources...
INFO Waiting up to 20m0s for the Kubernetes API at https://api.okd.versatushpc.com.br:6443...
INFO API v1.20.0-1095+9689d22dc3121e-dirty up
INFO Waiting up to 30m0s for bootstrapping to complete...
INFO Destroying the bootstrap resources...
INFO Waiting up to 40m0s for the cluster at https://api.okd.versatushpc.com.br:6443 to initialize...
INFO Waiting up to 10m0s for the openshift-console route to be created...
INFO Install complete!
INFO To access the cluster as the system:admin user when using 'oc', run 'export KUBECONFIG=/home/ferrao/okd/installokd/auth/kubeconfig'
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.okd.versatushpc.com.br
INFO Login to the console with user: "kubeadmin", and password: "xxxxxxxxxxx"
INFO Time elapsed: 1h26m28s

On the web interface it's complaining about errors on checking for upgrades but I think this is due to the fact its a nightly build.
What was the issue at the end?
Thank you again.

What was the issue at the end?

That was https://github.com/coreos/fedora-coreos-tracker/issues/943. Current fix is to start with older FCOS in installer. We'll release a new stable 4.7 with this workaround on the weekend.

On the web interface it's complaining about errors on checking for upgrades but I think this is due to the fact its a nightly build.

Is it https://github.com/openshift/okd/blob/master/KNOWN_ISSUES.md#cannotretrieveupdates-alert with "unreachable origin-release.svc.ci.openshift.org" or "version ... not found in channel ..." (the latter is expected for any nightly)?

What was the issue at the end?

That was coreos/fedora-coreos-tracker#943. Current fix is to start with older FCOS in installer. We'll release a new stable 4.7 with this workaround on the weekend.

Nice.

On the web interface it's complaining about errors on checking for upgrades but I think this is due to the fact its a nightly build.

Is it https://github.com/openshift/okd/blob/master/KNOWN_ISSUES.md#cannotretrieveupdates-alert with "unreachable origin-release.svc.ci.openshift.org" or "version ... not found in channel ..." (the latter is expected for any nightly)?

On the warning it says: Cluster version operator has not retrieved updates in 1d 22h 53m 8s. Failure reason RemoteFailed . For more information refer to https://console-openshift-console.apps.okd.versatushpc.com.br/settings/cluster/.
So it's exactly what the workaround solves. Thank you again @vrutkovs. It's perfectly working now.
Everything seems to be fine now.


flyway-core 7.7.3 (was 7.5.4)

Updates org.flywaydb:flyway-core from 7.5.4 to 7.7.3.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.flywaydb", artifactId = "flyway-core" } ]

labels: test-library-update, semver-minor

Superseded by #162.


Incorrect tray icon sometimes

Steps to reproduce
On Linux Mint 22 Cinnamon Framework 13.

Where are you starting? What can you see?
What do you click?
More steps…

Outcome
What did you expect?
What happened instead?
Operating system
No response
Application version
No response
How did you install the app?
No response
Homeserver
No response
Will you send logs?
Yes


Governance API changes in v1.10.2

Proposed changes

Reflect changes https://github.com/klaytn/klaytn/pull/1783
It is preferable to merge #514 first to avoid conflict.

Types of changes
Please put an x in the boxes related to your change.

[ ] Minor Issues and Typos
[ ] Major Content Contribution
[ ] Others

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to reach out. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING GUIDELINES
[ ] I have signed the CLA
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Related issues
Further comments

I have read the CLA Document and I hereby sign the CLA

@kjeom I think we need to follow up this change for caver or open SDK.

@blukat29 Why don't you merge this?