correct relative folders

starting in tutorial0 directory:
"This will produce an __init__.class in the python/example namespace.
This classfile can run on any Java 6 (or higher) VM. To run the project, type:
  .. code-block:: bash

      $ java -classpath ../voc/dist/python-java.jar:. python.example.__init__
      Hello, World

Congratulations! You've just run your first Python program under Java using
VOC! Now you're ready to get a little more adventurous."
the /voc doesn't work.  The command line should read:
$ java -classpath ../dist/python-java.jar:. python.example.__init__

I know you had this problem; however, I think the issue is that you've made the tutorial0 directory in the wrong location. You should have a directory structure that looks like:

tutorial

voc
tutorial0

But it looks like you've got

tutorial

voc

tutorial0

The key piece of documentation is the line:
Let’s start by creating a tutorial0 directory alongside the voc directory you just cloned into:

However, it's easy to see how you made this mistake, and you're not the first person to make it. The text clearly needs to be clarified. I'm open to suggestions on how to improve it - perhaps including a "your directory tree should now look like..." example?

Ah, that makes sense. I will look at the wording and see if I can suggest
something.
On Jun 2, 2016 3:55 PM, "Russell Keith-Magee"<EMAIL_ADDRESS>wrote:

I know you had this problem; however, I think the issue is that you've
made the tutorial0 directory in the wrong location. You should have a
directory structure that looks like:

tutorial

voc
tutorial0

But it looks like you've got

tutorial

voc

tutorial0

The key piece of documentation is the line:
Let’s start by creating a tutorial0 directory alongside the voc directory you just cloned into:
However, it's easy to see how you made this mistake, and you're not the
first person to make it. The text clearly needs to be clarified. I'm open
to suggestions on how to improve it - perhaps including a "your directory
tree should now look like..." example?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pybee/voc/pull/137#issuecomment-223446816, or mute
the thread
https://github.com/notifications/unsubscribe/ASprVouGl3U3ZJKlQ3p65T4WAAEfwX2Lks5qH196gaJpZM4Is4y_
.

Closing on the basis that #142 cleared up this problem.


About unsupervised set-ups

Hi,
Very impressive work on trying unsupervised set-up for semantic segmentation.
Some questions about the codes:

Does the unsupervised training still need ImageNet-pretrained weights as an initialisation?
Are the results in Table. 3 also obtained with ImageNet-pretrained weights?
In Fig.7, in the third "prediction" column. are the black "background" regions obtained by masking directly from Ground Truth or by indirectly voting from background patches?

Thanks.

Hi Harry,
Thanks for your thoughtful questions.

Yes, we do use pre-trained weights for initialization as VOC is too small as a dataset to train on from scratch.  (Even with supervision, the training iterations are too many to achieve satisfactory results.)
Yes.  In our opinion, it is a fair comparison as the supervised setting in Table 3 is also initialized the same way.
It is by voting from the background patches.
Please let me know if you have further questions.

Jyh-Jing

Thank you Jyh-Jing a lot for your prompt reply!

 :)


add yahp deprecation warnings

This PR adds deprecation warnings whenever a user invokes:

run_composer_trainer.py entrypoint
TrainerHparams creation

There are many places in our codebase where we have hparams objects, but this should be sufficient to cover most use cases.

I don't think so? All roads lead to the TrainerHparams anyway.

Yep you're right. Lgtm!


Add support for servers on operation level for 3.1

Describe the PR
Adding the @servers param to the operation level.
Relation issue
None
Additional context
Based on this: https://swagger.io/docs/specification/v3_0/api-host-and-base-path#overriding-servers

Hi @Nerzal, thanks for approving. Do you have an estimation of when this can be merged?

Hi @ubogdan can you take a look at this maybe? Thanks!

@pmorelli92 Thanks for your contribution


📝 Add census dataloader example

The dependencies are pretty heavy so i added the example as a code snippet in markdown.

Can you please make 2 subsections under "Train ML models" so that it both approaches are visually more balanced?

It'd also be really great to actually add the code snippet for MappedCollection so that people don't absolutely have to jump to the other guide.

(Otherwise, great! Thank you! 🙏)

Sorry, which subsections should be added?

There should be a subsection (1) that trains on the collection of h5ad

And a subsection (2) that trains on the tiledbsoma array store.

Whereever you do:
collection = ln.Collection.filter(name="cellxgene-census", version=census_version).one()

you can meanwhile do
collection = ln.Collection.get(name="cellxgene-census", version=census_version)

That's easier to read because a few users found the .one() confusing.

@falexwolf can i merge?

Something seems to be messed up with the sections all of a sudden? This wasn't the case earlier 🤔
Did somebody update lndocs? Or did you change something?

This is how it looks on prod:

lndocs doesn't have a change for more than a week so it gotta be something in this PR or build env. 🤔

Hm, checking.

Building docs locally on main looks fine:

Great, it was the backticks. This fixed it.
So now it's just nitpicking about the exact wording. I'll make another commit here to make the subsections read exactly the same

I'll finalize & merge this, @Koncopd! Thank you!

I'm discovering a tiny few more things that can be polished.

Ok!

Do we want to show this without hiding

Should it not be called "array store" properly

I went back and forth on this choice. I think the "array store" is the official precise language that we're using here at Lamin. But to ease users into building intuition that language sounded too complicated, so I simplified it to "concatenated array" in this overview doc.
So, it was a conscious choice playing through the experience of perceiving the whole doc.


Doc: Adding documentation for multi-arch operators

Description of the change:
This change aims to enhance the documentation by providing guidance on how to build multi-arch operators under advanced topics.
Motivation for the change:
More and more operator authors are looking at getting their operators to support multiple architectures. This intends to provide some help for it.

Is there anything missing to get this PR merged?

hold

@joelanford anything further required from me to get this doc improvement merged?

I don't think these docs apply only to golang-based operators. If the ansible/helm base images support multi-arch, we should move these docs into a more generic location.

I don't think these docs apply only to golang-based operators. If the ansible/helm base images support multi-arch, we should move these docs into a more generic location.

@asmacdo what's your proposal?

@joelanford @asmacdo is there something additional you wish or can you please merge this PR?

/hold cancel
My primary concerns have been addressed. Thanks @fgiloux!
Seems like @asmacdo may still have an open question on the best location for this doc. Most of this doc is generic, but the one piece that's specific to Go is the caveat about setting GOARCH in the Dockerfile.
I also added another comment about that line that I think needs to be addressed before I'm ready to lgtm.

@joelanford
I have fixed GOARCH
@asmacdo I have checked that both:
quay.io/operator-framework/helm-operator:v1.12.0
quay.io/operator-framework/ansible-operator:v1.12.0
are manifest lists. I haven't tested deploying these operators on non amd64 archs. If you think there is a better location for this documentation I am happy to move it. Please let me know.

See that not necessary users will do that to integrate with OLM. So, IMHO we need to clarify more it as well. And it seems related to kubernetes-sigs/kubebuilder#2206
I am not sure what you are referring to here. In regards to kubebuilder issue 2206 there is a way of building multi-arch images from common sources and it is what I am documented here. Surely the scaffolded Makefile could allow for that. Therefore buildx and/or buildah targets would need to be added.

@camilamacedo86 I hope the changes meet your expectations. Please let me know.

Hi @fgiloux,
I am ok with the changes it shows fine. IHMO is only missing to be added outside of the Golang language since it is not specific and only applied to Go projects.
Otherwise, /lgtm

@asmacdo @joelanford if you agree with @camilamacedo86 's proposal I will move it to a separate section, an option would be: Building Operators > Multi-arch (at the same level as Ansible, Go, Helm).
I am open to other suggestions.

@fgiloux,

@asmacdo @joelanford if you agree with @camilamacedo86 's proposal I will move it to a separate section, an option would be: Building Operators > Multi-arch (at the same level as Ansible, Go, Helm).
I am open to other suggestions.

Inside of Building Operators we have only the languages.
See the Scorecard and OLM integration sections which are common for all languages.
IMHO that could fit at the same place/level.
Note that @asmacdo also suggested the same already :
https://github.com/operator-framework/operator-sdk/pull/5178#issuecomment-923160813

@fgiloux,

@asmacdo @joelanford if you agree with @camilamacedo86 's proposal I will move it to a separate section, an option would be: Building Operators > Multi-arch (at the same level as Ansible, Go, Helm).
I am open to other suggestions.

Inside of Building Operators we have only the languages. See the Scorecard and OLM integration sections which are common for all languages. IMHO that could fit at the same place/level.

That would then be a top level section. IMHO it is little content for it. Another option would be to have: "Testing Operators", "OLM Integration" and this new section together under a more generic section. I am fine either way.

Note that @asmacdo also suggested the same already : #5178 (comment)

I know that. I am just asking for an agreement on the new location.

@fgiloux,
WDYT? Add a new section here such as Advanced Topics and add inside the doc Multiple architectures?

@camilamacedo86 as per your proposal I have created a new section "Advanced Topics" and added the Multiple architectures content there. I let a couple of introductory lines with a link to the new section in the go specific page.
Hopefully this can now get merged


Security issues

Hi,
I would like to report various security issues in ME, on what channel can we talk ?

We don't have set up any channels but I can share my email address to discuss that. Let me know so I can share it and remove it

ok I'm ready!

<EMAIL_ADDRESS>


Project failed to load properly on iOS

iOS only has the Import from URL button. How do we get a URL that imports into "Imported Projects"

Testing in both Android and iOS with the Import from URL option showed that the QField project needs to be zipped into a single .zip file containing the QGS project file and all associated data.
This can be put onto a website e.g. JNCC Resource Hub or file share such as DropBox or Google Drive.
The URL must be a direct download link where the file downloads immediately on clicking the link with no login/view screens in between.

JNCC testing has confirmed that supplied URLs for a file on the Exegesis website and in Dropbox (with dl=1) work in both iOS and Android so this is the preferred method to be documented in the guidance.

Tested - Pass - Happy to close ticket


Unable to install due to dependency

My project is configured to use React 16.13.1.
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
npm ERR! node_modules/react-native-windows
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@react-native-community/checkbox
npm ERR<EMAIL_ADDRESS>from the root project

Is there any work around for this?

Same issue here! Please assist!

Same issue here! Please assist!

I worked around this issue by installing 4.0.2. maybe you can go higher than that as well, but this was sufficient for me to to at least get the thing compiling.

My project is configured to use React 16.13.1.
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
npm ERR! node_modules/react-native-windows
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@react-native-community/checkbox
npm ERR<EMAIL_ADDRESS>from the root project

Is there any work around for this?

Did you get rid of this issue

Mine was the same problem when tying to upgrade the lib. The version that works for that version of react without upgrading the react is the version 0.4.2.
But my eslint accuses a error:
Unable to resolve path to module '@react-native-community/checkbox'.

Anyone found some solution for this problem?

@Akiles94 it seems to be fixed and will be rolled out with the next release: #149


How to get good results on PTB dataset?

similar results like #108 when running with
PROBLEM=lmptb_10k
MODEL=attention_lm
HPARAMS=attention_lm_base

Still got similar results, so I tried to turn down the hidden_size and num_hidden_layers, also increased the attention_dropout and residual_dropout, but still no satisfactory results with log_perplexity around 5.00.

What I got is either overfitting or log_perplexity about 5.1 (training loss is jitter around 4.3), which makes me really confused. I noticed there are some specific configurations in Table 3 of the paper "Attention is all you need", so can you list the proper configurations to achieve better results on PTB？Which parameters need to be tuned other than dropout or hidden_size?
Please help.

You definitely need to lower filter_size and hidden_size and set all dropouts higher. Also, as far as I can tell, log-ppx of 4.4 is quite good and 4.1 would be state-of-the-art, so 5.0 isn't that bad for a model that's totally untuned for the task. Note that we never ran our models on PTB as it's a very small data-set and it was only added recently in a github PR. I'm just giving it a shot with these params:
--problems=lmptb_10k --model=attention_lm --hparams_set=attention_lm_base --train_steps=20000 --eval_steps=7 --hparams='hidden_size=512,filter_size=1024,dropout=0.5,attention_dropout=0.5,label_smoothing=0.1,relu_dropout=0.5,residual_dropout=0.5,learning_rate_warmup_steps=2000,learning_rate_decay_scheme=exp10k'
I'm getting 4.8 after 8k steps, so not too horrible, but still way to go!
If you get a better hparams set for ptb, please make a PR adding it to attention_lm as attention_lm_ptb :). It's also sth to collaborate on with others! Please let me know what results you see.

@lukaszkaiser
Thanks! I'll try to find a better hparams set for PTB.
I'm also trying to reproduce good results for the 1B words benchmark, and here are 2 questions I have.

What's the best result you've got on the 1B words benchmark and what's the specific params for this best result?

What's the vocabulary size used in your experiment? If it's 800k, have you applied some methods to speedup the softmax computation for large vocabulary size like Hierarchical Softmax or some other sampling methods? Since as far as I know, it would take a long time to train this model without such acceleration.

Hi @rivaldinho : it'll be great if you find some good params for PTB, let us know.
As for LM1B: Noam just added in 1.0.13 a generator for the lm1b dataset with 32k subword vocabulary. I think that's the setting he got the best results with, I think attention_lm_moe goes below 30 ppx. I can ask him for a detailed number, but of course these close-to-SOTA LMs take a while to train even on 8 gpus.

Hello @lukaszkaiser
Can you explain the purpose of that 32k subword vocabulary? How is it used?

@fminkin: Subword units (either BPE or word-pieces, which is almost the same) are a compromise between character-based models (which has small "vocabulary", but long sequences) and word-based models (English may have more than 200k wordforms, which would result in big models and slow training).

@martinpop, thanks for clearing that out.
So it's beneficial to use subwords in combination with words as word level language model? How exactly does it work?

Subword vocabulary contains the most common words anyway, so there is no need to merge. In general, subwords are probably the best option for text problems. But PTB is an old dataset and it comes pre-tokenized to a fixed vocabulary anyway, so it's not a good example for that.

my google colab is showing runtime died  for large vocab size


Simpleshot nontrainable layer goes backwarding

Check logic inside simpleshot if nontrainable is treated nontrainable (or in network_graph.cpp)

:octocat: cibot: Thank you for posting issue #1135. The person in charge will reply soon.


Rollbar and New Relic integration

Added Rollbar and New Relic on the sixpack server to be able to monitor the application performance and get error notifications.

What happened here?

@zackkitzmiller I made a mistake and opened this based on the wrong branch. I'll reopen based the correct one soon.

Ha. I figured it was accidental api keys or something.
On Wed, Nov 28, 2018 at 08:40 Adriano Luz<EMAIL_ADDRESS>wrote:

@zackkitzmiller https://github.com/zackkitzmiller I made a mistake and
opened this based on the wrong branch. I'll reopen based the correct one
soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sixpack/sixpack/pull/295#issuecomment-442450003, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGzsPnZUKcRlxG9B1te3QWsFuMNd_Cvks5uzpJFgaJpZM4Y3lcx
.


Added mutex to avoid concurrent map writing

…RM sidecar

Summary

As stated in the issue #179, it is possible to have concurrent map writing, since maps are not meant for concurrent write access. Added a Mutex to avoid it

Related issue :
#179

@Surax98 ammend with sign your commits please


SGX Hardware mode build error: get_signature_revocation_lists HTTP Error code : 401

I am trying to execute a Docker-based build and execution.

SGX driver(/dev/isgx) is installed and can work. Did i miss something?
Do i need to add environment variables TCF_ENCLAVE_CODE_SIGN_PEM and TCF_HOME on the host machine? (because it is a docker-based build, i think it is not a must)

Any advice would be appreciated. Thanks in advance.
sudo docker-compose -f docker-compose.yaml -f docker-compose-sgx.yaml up --build
avalon-enclave-manager        | [17:19:26 INFO    avalon_enclave_manager.enclave_manager] Received empty list of work orders from wo-scheduled table
avalon-enclave-manager        | [17:19:26 INFO    avalon_enclave_manager.enclave_manager] Enclave manager sleeping for 10 secs
avalon-sgx-enclave-manager    | [17:19:33 INFO    avalon_enclave_manager.avalon_enclave_bridge] EPID: 00000B42
avalon-sgx-enclave-manager    | [17:19:34 WARNING STDERR] /usr/lib/python3/dist-packages/urllib3/connectionpool.py:860: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
avalon-sgx-enclave-manager    | [17:19:34 WARNING STDERR]   InsecureRequestWarning)
avalon-sgx-enclave-manager    | [17:19:34 ERROR   avalon_enclave_manager.ias_client] get_signature_revocation_lists HTTP Error code : 401
avalon-sgx-enclave-manager    | [17:19:34 WARNING avalon_enclave_manager.avalon_enclave_bridge] Failed to retrieve initial sig rl from IAS: 401 Client Error: Access Denied for url: https://api.trustedservices.intel.com/sgx/dev/attestation/v3/sigrl/00000B42
avalon-sgx-enclave-manager    | [17:19:34 WARNING avalon_enclave_manager.avalon_enclave_bridge] Retrying in 60 sec

@justalittlenoob Can you check the following:

aesm service is up and running on host machine
You obtained Intel IAS subscription key and SPID (as descirbed in here) and follow step 5. This is applicable in docker mode also.
You no need to set TCF_ENCLAVE_CODE_SIGN_PEM and TCF_HOME in docker build mode.

Let me know if you still get the issues.

@pankajgoyal2
Hi, thank you very much for your advice, it's very helpful. The root cause is I didn't configure subscription and SPID. Now it works.


[BUG] After upgrade complete, we can still see the hvst-upgrade image display on the vm and volume creation page

Describe the bug

After we successfully upgrade from v1.1.1 to v1.1.2-rc1, and try to create a VM and volume
We can still see the hvst-upgrade image display on the image list of virtual machine page

We can also see the hvst-upgrade image display on the image list of volume page

To Reproduce
Steps to reproduce the behavior:

Prepare a 2 nodes Harvester cluster of v1.1.1 release
Provision a RKE2 guest cluster
Upgrade to v1.1.2-rc1
Wait until the upgrade complete
Create a virtual machine, check the images list
Create a volume, check the images list

Expected behavior

The hvst-upgrade image should not exist on the image list of vm and volume page
Support bundle

supportbundle_2df5f22c-bf4c-41ad-a11f-e72b673a480a_2023-03-07T07-55-07Z.zip
Environment

Harvester ISO version: v1.1.1 to v1.1.2-rc1
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 2 nodes bare machines

Additional context
Add any other context about the problem here.

@TachunLin Please help monitor if this still happens after 1.1.2-rc3.

@TachunLin Please help monitor if this still happens after 1.1.2-rc3.

@bk201  I think it still exists and the UI will be fixed in v1.2.0.   (Unless the backend deletes the updated image immediately after the successful upgrade)

@WuJun2016 Yes, the backend delete the image. We think it should be fixed after https://github.com/harvester/harvester/pull/3508 as well.

ref to #1855

For same version upgrade (v1.1.2 -> v1.1.2), the volume for upgrade still exists, but VM and image deleted.

@starbops Could you check Lanfon's comment, is the volume to be kept intentionally?

Yes, the log-archive volume and downloader pod are kept intentionally for users to download the upgradelog archive even after the upgrade ends. The volume and pod will be cleaned up after the user click the "dismiss it" button on the upgrade dialog.
@lanfon72 do you remember if you clicked the "dismiss it" button on the upgrade dialog? If you clicked it or remove the upgrade CR, and the volume was still there, there might be some problem.

I can double confirm whether it will be deleted after user dismiss upgrade info, but I thought UI will still need to fix the amount as user can't access the volume.

Confirmed the volume will be deleted after dissmiss upgrade info.

Feel free to open it if it happens again. The logging volume is only deleted when clicking dismiss.


update live output node to not update state on tick

switch to passing the setter to the DropdownListControl instead of having it figure it out automatically
the live output now:

updates its hubSelect value when the user changes the liveOutputType
uses the deviceFamily and sharedVariable when updating the hubSelect
updates the hub select options when the liveOutputType is changed
the requiresSerial check now takes into account the hubSelect value
the "Physical Gripper" value of the hubSelect has both a device and noDevice view. This way the hubSelect value doesn't have to be changed when an arduino is connected or disconnected, instead just the view changes.

The simulation test that is failing is fixed in a follow on PR.


Update plugins.md

Remove linebreaks that broke markdown

I'm looking at https://leafletjs.com/plugins.html and it's not broken. I'm not clear about what you're trying to fix here.

HTML displays fine, it's the markdown that is broken. Not a big deal, but a bit confusing when trying to update the .md file using any kind of markdown editor/viewer. You can see the borken markdown here: https://github.com/Leaflet/Leaflet/blob/master/docs/plugins.md. First formatting error is right at the top after "Tile & image layers" heading. Github renders the markdown language, but random linebreaks breaks the formatting, hence broken tables.
I was about to add a plugin to the plugins.md, but thought might as well format it correctly before the actual plugin PR.

Superseded by #6813 / https://github.com/Leaflet/Leaflet/commit/3ce6e3040b80e7d37b62b74e0b7f531680ebd769


RFP - filen.io-sync-desktop

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://filen.io/
Direct download URL for the software / installer : https://cdn.filen.io/sync/updates/filen-setup.exe
Software summary / short description:
Virus total result : VirusTotal
This is one of the only actual opensource E2E encrypted sync provider (like Mega) but unlike Mega, they do not impose bandwidth limitation.
Package Expectations
I actually expect (unlike other package) to update it from chocolatey i don't have seen in the app an auto updater so it must be the best to update it though chocolatey.
Thanks for the one who will do it since they aren't many totally opensource sync provider out there.

Package created: https://community.chocolatey.org/packages/filen-sync

Package created: https://community.chocolatey.org/packages/filen-sync

Thanks ;)

try this https://github.com/FilenCloudDienste/filen-desktop/releases/download/1.6.2/filen-setup.exe

try this https://github.com/FilenCloudDienste/filen-desktop/releases/download/1.6.2/filen-setup.exe

Yeah, I use this link in the install script https://github.com/jakublevy/chocopkgs/blob/80ccfd6c5063b3e49c426ece7a37af9180b46591/filen-sync/tools/chocolateyinstall.ps1#L8

Package approved.


Docker-Compose not working

hi
Had a bit of a problem getting the docker compose-script to work out of the box, since version 3 seemst to not support secrets in the way they are used, changing it to version 3.1 worked just fine for me though.

Interesting, can you submit a PR with the fix, please?

@masaruhoshi maybe you can help out here a bit? :)


Address CSP in DatagridVirtualBody and DraggableElement

Replace the inline styles in DatagridVirtualBody.tsx and DraggableElement.tsx
Both of these files are using third party library.

[ ] Include the respective component name in the forbid configuration inside package.json
[ ]  Run yarn lint and fix the errors
[ ] Replace style={{}} usage with classNames where appropriate
[ ] Set dynamic styles using useIsomorphicEffect()

We've been investigating TanStack Table, a third-party, open-source offering, which provides extensive data table capabilities surpassing what our Carbon Datagrid offers. It provides much more flexibility and customization. TanStack Table is headless which means it can easily be added alongside Datagrid component in your product or application. The benefits of more flexibility for product teams and less maintenance for Carbon makes it a win win. Lastly, it is available in multiple frameworks including React and Web Component so it provides an option to non-React product teams.
For these reasons, we have decided to transition from building our own custom table component to using an example-based approach with TanStack Table. Datagrid will still exist in our library for existing teams but we are announcing the deprecation* of the Datagrid component in v2.54.0 release so teams can begin to work through the transition. Details about how to use both Datagrid and TanStack together can be found here.
*Deprecation means that no new features will be added however sev 1 and sev 2 bugs will be supported.


[UIbug] There is no correct display code area

When I switch from the default window to the maximization window, the code display area does not follow the maximization.

Append :  After this bug occurs, it will cause the APP to crash

@Dcr-chen you are right, there is no window resize listener to adjust the code area size. We will change the code display in the next release so it should be fixed. As for the crash, it is very unlikely that resizing the app can cause the crash. Can you provide more details about this?

Crashes don't happen every time, they're accidental, and there's another bug that might have something to do with the listener, and there's a video that shows this problem, when I maximize and then restore the default window size, I can't switch files in Explorer
https://github.com/BloopAI/bloop/assets/121916328/08bcf558-b51c-4d60-ae7d-27bbe7c8a0c2

@Dcr-chen are you sure it only happens after maximizing the window?

Yes, since I updated to 0.4. 4 yesterday, there has been a crash

did you have the ability to submit the crash report? There should be a popup on the Frontend asking you to write a comment and submit a crash report. Or was it completely broken so the app exited and had to be restarted?

It just crashed and disappeared, and then a system window popped up asking me: Is bloop working properly? My system is win11, but Bloop didn't catch an error message


Publish on Edge Store

It's a perfect extension for Socks5 proxy for edge.
But the only way to download is via Chrome Store which is not reachable at the very beginning for users in China.
Is it possible to publish the great extension into Edge Store as well?
Thanks in advance.

https://microsoftedge.microsoft.com/addons/detail/makcfnkaapoandbeldfnmamikefoafao


Add Metadata Support For Metrics

Summary
These changes are the second part of addressing #430 (first-part can be found in the diagnostics repo). This allows dotnet-monitor to show metadata in metrics and in live metrics.
Closes #430

Release Notes Entry
Add Metadata Support For Metrics

/backport to release/7.x

/backport to release/7.x

/backport to release/7.x

/backport to release/7.x


Don't warn on exit in development

Don't warn on exit in development because It is a bit annoying (especially when you use auto-reload).
+isDevelopment variable narrow down to development only (we have production/test/development?).

I agree with this DX improvement, it's a pain sometimes haha. But the inconsistency created between environments concerns me a bit too, once the UX step created when the user needs to leave the page with any pending stuff is important, which with this change, we will not validate always. WDYT @merapi ?

I think it's okay in dev mode (we know how it works and it's more for the end-user).
Alternatively, we can base it on env var that you can set in the terminal before you run webpack.


Drop table enhancement

Proposed changes
while using Drop table if there is more than one servicepath it will return message ("entity has more than one servicepath",244)
In case no service path is given it will drop whole table with code "204"
Types of changes
What types of changes does your code introduce to the project: Put
an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing
functionality to not work as expected)

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
ask. We're here to help! This is simply a reminder of what we are going
to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[ ] I have added tests that prove my fix is effective or that my
feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in
downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion
by explaining why you chose the solution you did and what alternatives
you considered, etc...
I have signed the CLA

@daminichopra thanks for this!! there's only one snag, I think we should call fiware_sp() to get the content of the service path header, not fiware_s()---see my comments in the review. Also should we add some tests? It looks like the ones we have at the moment aren't enough since they didn't catch we used the fiware service in place of the service path...

note to self. we should be able to close #455 after merging this pr.

@daminichopra any chance you can rebase on top of the master? this way the build should work out, thx

Hi @chicco785 , Please can u merge this PR if it looks good. Is it necessary to sign CLA to merge this PR?

hi @daminichopra it looks like something is broken. I think is a git merge gone sideways, have a look at this
https://github.com/orchestracities/ngsi-timeseries-api/pull/455/files#diff-ac79bcf11021293203657217c0ceed8a7ed24016c4c313322eb4059ddc43d1dfR67
if you can fix it up, rebase on master, then I'll review. thanks sooooo much!!

@daminichopra there's some still issues w/ this PR, I think it's b/c of a rebase gone wrong, if you could please double-check, see my comments in the review. Also, if you could please:

rebase again---there's some new changes in master, but this rebase should be an easy one
sign the CLA. you can try checking the box above in the PR description ("I  have signed the CLA") or if that doesn't work, add a new comment with this text: "recheckcla - I have read the CLA Document and I hereby sign the CLA"

thanks alot!!!

@daminichopra thx for the new commits, I've approved the PR. If you could pls do one last thing for me: sing the CLA. To do that

try checking the box above in the PR description ("I have signed the CLA") or if that doesn't work
add a new comment to this PR with this text: "recheckcla - I have read the CLA Document and I hereby sign the CLA"

thanks alot!!!

@daminichopra thx for the new commits, I've approved the PR. If you could pls do one last thing for me: sing the CLA. To do that

try checking the box above in the PR description ("I have signed the CLA") or if that doesn't work
add a new comment to this PR with this text: "recheckcla - I have read the CLA Document and I hereby sign the CLA"

thanks alot!!!

Hi @c0c0n3 , Now confirming the signing process inside the company, so please wait for a while.

Hi @c0c0n3 @chicco785 ,  I have signed the CLA for this PR.

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

@daminichopra let's see what @c0c0n3 think about my comment, if i got it wrong, we are ready to merge!

@chicco785 @daminichopra yes good points. Looking back at #406 what you say makes sense, so ideally the implementation should be

if request has no service path ==> drop table
if request has multiple service paths ==> 422 error
if request has one service path p and p is the only service path in the table ==> drop table
else ==> 422 error

At the moment we can't do (3) unless we extend the translator w/ an operation to check if condition (3) is true. @daminichopra do you have enough dev cycles for this additional piece of work? If not, we could just return an error if the  request has any service path in it, just to be on the safe side. So in this case the implementation could be:

if request has no service path ==> drop table
if request has one or many service paths ==> 422 error

In this scenario we see dropTable just as a maintenance convenience knob you can turn if you don't want to write yourself the SQL to drop the table and (2) would be some kind of safety net whereby if there's service paths, we assume the caller didn't mean to specify the dropTable param but rather call the bare delete entities method which already deletes all the records in the table having the specified service paths. Not optimal though.
Thoughts?

@chicco785 @daminichopra yes good points. Looking back at #406 what you say makes sense, so ideally the implementation should be

if request has no service path ==> drop table
if request has multiple service paths ==> 422 error
if request has one service path p and p is the only service path in the table ==> drop table
else ==> 422 error

At the moment we can't do (3) unless we extend the translator w/ an operation to check if condition (3) is true. @daminichopra do you have enough dev cycles for this additional piece of work? If not, we could just return an error if the request has any service path in it, just to be on the safe side. So in this case the implementation could be:

if request has no service path ==> drop table
if request has one or many service paths ==> 422 error

In this scenario we see dropTable just as a maintenance convenience knob you can turn if you don't want to write yourself the SQL to drop the table and (2) would be some kind of safety net whereby if there's service paths, we assume the caller didn't mean to specify the dropTable param but rather call the bare delete entities method which already deletes all the records in the table having the specified service paths. Not optimal though.
Thoughts?

At present the suggested code fix incorporated below  two comments:

if request has no service path ==> drop table
if request has one or many service paths ==> 422 error

For point (3) "if request has one service path p and p is the only service path in the table ==> drop table".
I would suggest to raise a separate issue for  point (3) which can be fixed separately as an enhancement. Thank you :)

At present the suggested code fix incorporated below two comments:

if request has no service path ==> drop table
if request has one or many service paths ==> 422 error

For point (3) "if request has one service path p and p is the only service path in the table ==> drop table".
I would suggest to raise a separate issue for point (3) which can be fixed separately as an enhancement. Thank you :)

agree with the path proposed

Hi @c0c0n3 , Please close this PR if it looks good.

it seems you have overwritten docs/manuals/user/index.md with the main docs/manuals/index.md, any reason for doing so?
@chicco785 , I have updated fix for this Issue

it seems you have overwritten docs/manuals/user/index.md with the main docs/manuals/index.md, any reason for doing so?
@chicco785 , I have updated fix for this Issue

i see, but the issue was not the content per se, but how readthedocs generates the nav bar, i fixed this in a separate pr #503 , can you remove changes to this file, so we can proceed?
thx

it seems you have overwritten docs/manuals/user/index.md with the main docs/manuals/index.md, any reason for doing so?
@chicco785 , I have updated fix for this Issue

i see, but the issue was not the content per se, but how readthedocs generates the nav bar, i fixed this in a separate pr #503 , can you remove changes to this file, so we can proceed?
thx

Removed Changes and updated commit.

@c0c0n3 @chicco785 , Gentle Reminder!! :)

@c0c0n3 @chicco785 , Gentle Reminder!! :)

build is failing, can't be merged.
I believe it does not implement what @c0c0n3 suggested:

At present the suggested code fix incorporated below two comments:
if request has no service path ==> drop table
if request has one or many service paths ==> 422 error

I feel the logic is more:
if request has many service paths ==> 422 error
if request has one service path => drop table
if this is the case, it's not what we want.

@daminichopra i cleaned the pr, and fixed the logic.
as by previous comment, it's better to proceed as follow:

define test cases
develop code supporting test cases

@daminichopra i cleaned the pr, and fixed the logic.
as by previous comment, it's better to proceed as follow:

define test cases
develop code supporting test cases

@chicco785 , Thanks for this i got it. Please let me know if further something needs to be done in this PR.

@daminichopra i cleaned the pr, and fixed the logic.
as by previous comment, it's better to proceed as follow:

define test cases
develop code supporting test cases

@chicco785 , Thanks for this i got it. Please let me know if further modification required for the closure of this PR.

Soft Reminder!!


Flattening types in generated .d.ts files for libraries

🔍 Search Terms
"delcaration readable" "declaration pretty"
✅ Viability Checklist

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
Allow library authors to add the inline modifier on a type declaration which makes the compiler flatten the type in generated code.
An inline modifier for type declarations
// Strawman syntax

// Instead of this
type Foo = Bar & Baz | Omit<Bat, "x" | "y">

// The library author can write this
inline type Foo = Bar & Baz | Omit<Bat, "x" | "y">

type Bar = { foo: "b" };
type Baz = { bar: "c" };
type Bat = { x: "x"; y: "y"; z: "z"; a: "a" };

The compiler would mostly ignore the inline directive (it would behave similarly to the Prettify helper type, however, when building the declaration files, the compiler will generate the flattened version like this
type Foo = {
    foo: "b";
    bar: "c";
} | {
    z: "z";
    a: "a";
}

Alternatively, instead of a modifier on a declaration, it can be a modifier we can add on types
type Foo = Inline<Bar> & Inline<Baz> | Inline<Omit<Bat, "x" | "y">>

Honestly, I'm not sure of the full semantics of inline. My mental intuition is based on the Prettify type helper.
type Prettify<T> = {
  [K in keyof T]: T[K];
} & unknown;

Alternatively, a tsconfig.json setting might also work. Although I'm sure to have the best experience, the compiler might need some feedback from the library author too.
Sorry if this isn't fully fleshed out, but I'm willing to work on a full proposal in case the team is open to the idea.
📃 Motivating Example
We have a lot of computed types in our design system library. Most (React) components can receive Theme defined props.
Here's a verbatim example which is our Box component, which is a design system aware div.
export type BoxProps = AsChild & ThemeProps & styles.SprinklesProps & React.HTMLAttributes<HTMLDivElement>;

This describes the type perfectly, but it leads to very poor DX for the callers. When someone Cmd-Clicks Box, they see a type which isn't really helpful when trying to figure out the API of Box.
What I'd like to see in the generated declarations would be something like the following

💻 Use Cases

What do you want to use this for?
Improving the UX of our library consumers when there are computed types in the public API.
What shortcomings exist with current approaches?
It's hard to understand the API of our library because cmputed types obscure the actual properties that are accepted by the types
What workarounds are you using in the meantime?
We wrap certain public API types with the Prettify helper type so that the users can hover over certain types to received a flattened version of the type

I'm not really sure how to formalize this

@RyanCavanaugh me neither to be honest. Maybe it's better to implement it as a third party compiler plugin/CLI tool to generate dts file.


Automation?

Would it be possible to get support for automation such as configure a announcement channel to scan for and then have it auto announce all messages in that channel or all messages with a keyword such as @everyone

I'm not sure if it's possible and I don't really have that much experience with making plugins. If someone else is able to do it then he/she can PR it here.


chore(ci): trace target directory content for cache troubleshooting

#153 reported a suspicious cache usage increase.
This PR introduces a new step in the build process to output the content of the target directory after the build. This will help investigate if something is wrong builds after builds.
I ran multiple builds with this change and couldn't observe any file change or file increase from the same commits.
Here is an example of the new step in action: https://github.com/daniellavoie/Ambient/actions/runs/4257943674/jobs/7408628309

@daniellavoie Yup good idea, merging.


Drop the feather-format test dependency

It is just a wrapper for pyarrow.feather, which we can use directly.

LGTM, thanks!


prevent installation of jekyll 3.9 on CI for now

Sets JEKYLL_VERSION='~> 3.8.0' to ensure that jekyll 3.9 does not cause CI breakage.
This is a temporary workaround until we can figure what to do about kramdown-parser-gfm.

Instead of preventing, you can workaround like I did for another project.

Sounds good. Superseded by #224


[objc] Reduce code duplication to generate methods...

before starting to generate more special cases :)

Build and tests passed.


smpp eliminate get_deploy_int for determining redis db

use redis_config['db'] instead

Done as part of #167. Just need to check it doesn't creep back in when the various SMPP branches land.

will merge into SMPP first anyway
On 1 March 2012 11:45, Simon Cross <
<EMAIL_ADDRESS>
wrote:

Done as part of #167. Just need to check it doesn't creep back in when the
various SMPP branches land.

Reply to this email directly or view it on GitHub:
https://github.com/praekelt/vumi/issues/109#issuecomment-4255171

--
David
He had read much of things as they are, and talked with too many people.
Well-meaning philosophers had taught him to look into the logical relations
of things, and analyse the processes which shaped his thoughts and fancies.
Wonder had gone away, and he had forgotten that all life is only a set of
pictures in the brain, among which there is no difference betwixt those
born of real things and those born of inward dreamings, and no cause to
value the one above the other. Custom had dinned into his ears a
superstitious reverence for that which tangibly and physically exists, and
had made him secretly ashamed to dwell in visions.

- H. P. Lovecraft (The Silver Key)


Issue, Tests & possible bugfix for EasyDb::is1DArray()

Currently using easydb at work, noticed a couple of issues when passing arguments in: if passing an empty array, EasyDB::is1DArray() returned false.
Not 100% sure, but I've tinkered with the method & added  phpunit tests for checking this method (this in no way satisfies issue #1, it's just to demonstrate the bug & fix).
For a point of reference, here's the output of php --version:

PHP 7.0.9 (cli) (built: Jul 20 2016 11:08:23) ( ZTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies

Excellent. Thank you for contributing this fix. :)
(Pay no mind to the Travis CI failure.)

You're welcome :)
I'm making a point to follow as many of the recommendations from the paragonie blog :D


Fixes issue #77 Function is now displayed as title

@djmgit Why is it showing previous commits also ? I have created new PR by creating new branch mybug1 from master and then pushed all changes to mybug1  branch.


Prerelease install command not working when same version is already installed

Describe the annoyance
The command to install the prerelease from here https://github.com/rerun-io/rerun/releases will not work if the same version is already installed.
Possible solution
Add --force-reinstall to the command?

To clarify: This should only affect pre-releases where the version number is the same, so this is low priority.

Adding that the command also does not work when there is a newer version (like a release candidate) on pypi already. It will install the release candidate then.

Maybe something like this would work more reliably:
pip install --no-cache-dir --force-reinstall -f https://build.rerun.io/commit/fccd095/wheels --upgrade rerun-sdk==0.13.0a3


[kwokctl] Supports disabling all QPS limits

What would you like to be added?
Disable QPS limits if it can be disabled
If not, set to maximum
Why is this needed?
Quickly mock the desired cluster

/assign


Fix account info

Description
This is a fix for the account info not working as expected. It now returns a Stellar::AccountInfo object.
Issue
account_info fetch does not work

Hi @nullstyle, I made the changes you requested :)

Beautiful!  thanks very much @iamarmanjon


Widget constructors expect children in inconsistent ways

 Issue by ianloic
Thursday Oct 29, 2015 at 20:28 GMT
Originally opened as https://github.com/flutter/engine/issues/1872

Some widgets (eg: Container) require a name child: argument to specify their children. Others (eg: Flex) take their children as the first argument. This inconsistency is confusing - especially as I switch between different container widgets.

 Comment by abarth
Thursday Oct 29, 2015 at 20:48 GMT

Yeah, the pattern we've been using is that if you take one widget as a child, you use the name child.  If you take a list, then you use a positional argument.  Are you suggesting that we make the list widgets use the name child too?  Maybe children?

 Comment by ianloic
Monday Nov 02, 2015 at 18:21 GMT

I don't have a concrete suggestion other than it's a little confusing. Perhaps make the list widgets use children so that I'm forced to be explicit everywhere.

I think we should just always use named arguments for children, since the children argument often takes up many lines of code and usually reads best when it's the last argument passed to a constructor.

Will do.


Open GL issue

When i launch the windows app scihub eva, i get the error that open GL 2.0 or higher driver is required or the ANGLE libraries are missing.
I put missing ANGEL libraries, libegl.dll, libglesv2.dll and d3dcompiler_43.dll in exe folder. exe did not work. Same error.
I tried to updated the intel HD 3000 driver. Its already latest <IP_ADDRESS>59.
Also, i checked my intel HD 3000 is supporting openGL 3.1
I also checked on another laptop, still same issue as that laptop also had the same graphics card intel hd 3000.
For 1st time, when i installed exe in my second laptop, exe ran and hanged up in fetching captcha. Then, closed it and re-ran it OPEN GL error.
I re-installed on both laptops, same error.
switched down to v3.20 still same issue.
Kindly help.

It was running fine till day before yesterday

Maybe I should add OpenGL libraries on Windows like before, see bbae550, will fix it in next release.

looking forward to it. BTW, exe hangs sometimes during captcha fetching. is it because of the connection termination from server?

Captcha is downloaded with same setting of pdf, which means it also supports proxy server. In most case, it's network problem to not display it.


scheduler/conf.c: Print to stderr if we don't open cups-files.conf

In case cupsd can't open the cups-files.conf, the error message is lost if journal and syslog don't exist or work on system (usually in containers).
Log the error into stderr at this place to get the error message if needed.

Updated.


[BUG] can not run demo Deploying AMQ Broker on MicroShift

What happened?

when I try the demo, I can not access the amqp service  in order to execute demo for providing producer and consumer.
The pod named amq-broker is not  running status. It's status is ImagePullBackOff.
The more detail log

  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  59m                    default-scheduler  Successfully assigned amq-broker/amq-broker-9c78cb94-2p4sh to fedora
  Normal   Pulling    58m (x4 over 59m)      kubelet            Pulling image "registry.redhat.io/amq7/amq-broker:7.8"
  Warning  Failed     58m (x4 over 59m)      kubelet            Failed to pull image "registry.redhat.io/amq7/amq-broker:7.8": rpc error: code = Unknown desc = unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
  Warning  Failed     58m (x4 over 59m)      kubelet            Error: ErrImagePull
  Warning  Failed     58m (x6 over 59m)      kubelet            Error: ImagePullBackOff
  Normal   BackOff    4m45s (x233 over 59m)  kubelet            Back-off pulling image "registry.redhat.io/amq7/amq-broker:7.8"

But I pull manually image podman pull registry.redhat.io/amq7/amq-broker:7.8 after login is right.

[user@fedora ~]$ podman images
REPOSITORY                          TAG         IMAGE ID      CREATED      SIZE
registry.redhat.io/amq7/amq-broker  7.8         69cd146bb6a8  2 weeks ago  680 MB

I follow the doc  step by step , anyone  would give me some guide ?
Thanks for your time.

Environment

MicroShift version (use microshift version):
MicroShift Version: 4.8.0-0.microshift-2022-04-20-141053
Base OKD Version: 4.8.0-0.okd-2021-10-10-030117

Hardware configuration:

OS (e.g: cat /etc/os-release):
fedora 36 vmware x86

Kernel (e.g. uname -a):
Linux fedora 5.19.4-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Aug 25 17:42:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Relevant logs

@TUT-jiayou, do you have CRI-O pull secret configured as described in the Runtime Prerequisites?

@ggiguash

I also can got container image.

oc describe pod  amq-broker-9c78cb94-jmxrk -n amq-broker

Name:         amq-broker-9c78cb94-jmxrk
Namespace:    amq-broker
Priority:     0
Node:         fedora/<IP_ADDRESS>
Start Time:   Tue, 13 Sep 2022 10:13:18 +0800
Labels:       app=amq-broker
              pod-template-hash=9c78cb94
Annotations:  <none>
Status:       Pending
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/amq-broker-9c78cb94
Containers:
  amq-broker:
    Container ID:
    Image:          registry.redhat.io/amq7/amq-broker:7.8
    Image ID:
    Ports:          61616/TCP, 8161/TCP, 5672/TCP, 1883/TCP
    Host Ports:     0/TCP, 0/TCP, 0/TCP, 0/TCP
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Environment:
      AMQ_USER:      admin
      AMQ_PASSWORD:  admin
      AMQ_PROTOCOL:  amqp,mqtt
      AMQ_DATA_DIR:  /data
    Mounts:
      /data from amq-broker-datavol (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rsdtj (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  amq-broker-datavol:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  amq-broker-pvc
    ReadOnly:   false
  kube-api-access-rsdtj:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
    ConfigMapName:           openshift-service-ca.crt
    ConfigMapOptional:       <nil>
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  15m                  default-scheduler  Successfully assigned amq-broker/amq-broker-9c78cb94-jmxrk to fedora
  Normal   Pulling    13m (x4 over 15m)    kubelet            Pulling image "registry.redhat.io/amq7/amq-broker:7.8"
  Warning  Failed     13m (x4 over 15m)    kubelet            Failed to pull image "registry.redhat.io/amq7/amq-broker:7.8": rpc error: code = Unknown desc = unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
  Warning  Failed     13m (x4 over 15m)    kubelet            Error: ErrImagePull
  Warning  Failed     13m (x6 over 15m)    kubelet            Error: ImagePullBackOff
  Normal   BackOff    13m (x7 over 15m)    kubelet            Back-off pulling image "registry.redhat.io/amq7/amq-broker:7.8"
  Normal   Pulling    10m (x4 over 11m)    kubelet            Pulling image "registry.redhat.io/amq7/amq-broker:7.8"
  Warning  Failed     10m (x4 over 11m)    kubelet            Failed to pull image "registry.redhat.io/amq7/amq-broker:7.8": rpc error: code = Unknown desc = unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
  Warning  Failed     10m (x4 over 11m)    kubelet            Error: ErrImagePull
  Warning  Failed     9m29s (x6 over 11m)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    90s (x41 over 11m)   kubelet            Back-off pulling image "registry.redhat.io/amq7/amq-broker:7.8"

I download the pull secret txt file and move to /etc/crio/openshift-pull-secret

change mode sudo chmod 600 /etc/crio/openshift-pull-secret
Add global_auth_file="/etc/crio/openshift-pull-secret" to file /etc/crio/crio.conf.d/microshift.conf .
restart systemd service sudo systemctl restart crio sudo systemctl restart microshift.
About the service crio and microshift log

[user@fedora ~]$ journalctl -u microshift -f
9月 13 10:29:54 fedora microshift[24643]: W0913 10:29:54.705286   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:29:54 fedora microshift[24643]: W0913 10:29:54.705342   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:29:54 fedora microshift[24643]: W0913 10:29:54.705483   24643 patch_genericapiserver.go:123] Request to "/apis/project.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:29:56 fedora microshift[24643]: W0913 10:29:56.705606   24643 patch_genericapiserver.go:123] Request to "/openapi/v2" (source IP <IP_ADDRESS>:53960, user agent "") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:29:57 fedora microshift[24643]: W0913 10:29:57.597303   24643 patch_genericapiserver.go:123] Request to "/openapi/v2" (source IP <IP_ADDRESS>:53968, user agent "") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:29:58 fedora microshift[24643]: W0913 10:29:58.495262   24643 patch_genericapiserver.go:123] Request to "/openapi/v2" (source IP <IP_ADDRESS>:53974, user agent "") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:29:59 fedora microshift[24643]: W0913 10:29:59.410691   24643 patch_genericapiserver.go:123] Request to "/openapi/v2" (source IP <IP_ADDRESS>:53988, user agent "") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:00 fedora microshift[24643]: W0913 10:30:00.291747   24643 patch_genericapiserver.go:123] Request to "/openapi/v2" (source IP <IP_ADDRESS>:53998, user agent "") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:01 fedora microshift[24643]: W0913 10:30:01.194540   24643 patch_genericapiserver.go:123] Request to "/openapi/v2" (source IP <IP_ADDRESS>:54006, user agent "") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:01 fedora microshift[24643]: E0913 10:30:01.912486   24643 pod_workers.go:190] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"amq-broker\" with ImagePullBackOff: \"Back-off pulling image \\\"registry.redhat.io/amq7/amq-broker:7.8\\\"\"" pod="amq-broker/amq-broker-9c78cb94-jmxrk" podUID=a0d624df-a317-4686-a686-f8c4d39e0324
9月 13 10:30:15 fedora microshift[24643]: W0913 10:30:15.832786   24643 patch_genericapiserver.go:123] Request to "/apis/user.openshift.io/v1" (source IP <IP_ADDRESS>:53844, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:resourcequota-controller") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:15 fedora microshift[24643]: W0913 10:30:15.833615   24643 patch_genericapiserver.go:123] Request to "/apis/image.openshift.io/v1" (source IP <IP_ADDRESS>:53968, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:resourcequota-controller") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:15 fedora microshift[24643]: W0913 10:30:15.833867   24643 patch_genericapiserver.go:123] Request to "/apis/project.openshift.io/v1" (source IP <IP_ADDRESS>:53998, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:resourcequota-controller") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:15 fedora microshift[24643]: W0913 10:30:15.834043   24643 patch_genericapiserver.go:123] Request to "/apis/route.openshift.io/v1" (source IP <IP_ADDRESS>:53960, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:resourcequota-controller") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:15 fedora microshift[24643]: W0913 10:30:15.834184   24643 patch_genericapiserver.go:123] Request to "/apis/apps.openshift.io/v1" (source IP <IP_ADDRESS>:53988, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:resourcequota-controller") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:15 fedora microshift[24643]: W0913 10:30:15.834249   24643 patch_genericapiserver.go:123] Request to "/apis/build.openshift.io/v1" (source IP <IP_ADDRESS>:53974, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:resourcequota-controller") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:15 fedora microshift[24643]: W0913 10:30:15.834807   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1" (source IP <IP_ADDRESS>:54006, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:resourcequota-controller") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:16 fedora microshift[24643]: W0913 10:30:16.134072   24643 patch_genericapiserver.go:123] Request to "/apis/apps.openshift.io/v1" (source IP <IP_ADDRESS>:53988, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:generic-garbage-collector") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:16 fedora microshift[24643]: W0913 10:30:16.134961   24643 patch_genericapiserver.go:123] Request to "/apis/project.openshift.io/v1" (source IP <IP_ADDRESS>:53998, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:generic-garbage-collector") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:16 fedora microshift[24643]: W0913 10:30:16.135142   24643 patch_genericapiserver.go:123] Request to "/apis/build.openshift.io/v1" (source IP <IP_ADDRESS>:53974, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:generic-garbage-collector") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:16 fedora microshift[24643]: W0913 10:30:16.136004   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1" (source IP <IP_ADDRESS>:54006, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:generic-garbage-collector") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:16 fedora microshift[24643]: W0913 10:30:16.136051   24643 patch_genericapiserver.go:123] Request to "/apis/route.openshift.io/v1" (source IP <IP_ADDRESS>:53960, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:generic-garbage-collector") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:16 fedora microshift[24643]: W0913 10:30:16.137364   24643 patch_genericapiserver.go:123] Request to "/apis/user.openshift.io/v1" (source IP <IP_ADDRESS>:53844, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:generic-garbage-collector") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:16 fedora microshift[24643]: W0913 10:30:16.137398   24643 patch_genericapiserver.go:123] Request to "/apis/image.openshift.io/v1" (source IP <IP_ADDRESS>:53968, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce/system:serviceaccount:kube-system:generic-garbage-collector") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:16 fedora microshift[24643]: E0913 10:30:16.912059   24643 pod_workers.go:190] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"amq-broker\" with ImagePullBackOff: \"Back-off pulling image \\\"registry.redhat.io/amq7/amq-broker:7.8\\\"\"" pod="amq-broker/amq-broker-9c78cb94-jmxrk" podUID=a0d624df-a317-4686-a686-f8c4d39e0324
9月 13 10:30:20 fedora microshift[24643]: W0913 10:30:20.111698   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1/templateinstances" (source IP <IP_ADDRESS>:54006, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:23 fedora microshift[24643]: W0913 10:30:23.719864   24643 patch_genericapiserver.go:123] Request to "/apis/route.openshift.io/v1/routes" (source IP <IP_ADDRESS>:53960, user agent "microshift/v1.21.1 (linux/amd64) kubernetes/b09a9ce") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704233   24643 patch_genericapiserver.go:123] Request to "/apis/user.openshift.io/v1" (source IP <IP_ADDRESS>:33676, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704344   24643 patch_genericapiserver.go:123] Request to "/apis/user.openshift.io/v1" (source IP <IP_ADDRESS>:33676, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704438   24643 patch_genericapiserver.go:123] Request to "/apis/user.openshift.io/v1" (source IP <IP_ADDRESS>:33676, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704467   24643 patch_genericapiserver.go:123] Request to "/apis/route.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704493   24643 patch_genericapiserver.go:123] Request to "/apis/route.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704765   24643 patch_genericapiserver.go:123] Request to "/apis/image.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704830   24643 patch_genericapiserver.go:123] Request to "/apis/image.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704906   24643 patch_genericapiserver.go:123] Request to "/apis/user.openshift.io/v1" (source IP <IP_ADDRESS>:33676, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704931   24643 patch_genericapiserver.go:123] Request to "/apis/user.openshift.io/v1" (source IP <IP_ADDRESS>:33676, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704468   24643 patch_genericapiserver.go:123] Request to "/apis/route.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704767   24643 patch_genericapiserver.go:123] Request to "/apis/build.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.705407   24643 patch_genericapiserver.go:123] Request to "/apis/image.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.705478   24643 patch_genericapiserver.go:123] Request to "/apis/image.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704783   24643 patch_genericapiserver.go:123] Request to "/apis/route.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.705535   24643 patch_genericapiserver.go:123] Request to "/apis/image.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.704443   24643 patch_genericapiserver.go:123] Request to "/apis/route.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.705707   24643 patch_genericapiserver.go:123] Request to "/apis/build.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.705791   24643 patch_genericapiserver.go:123] Request to "/apis/build.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.705831   24643 patch_genericapiserver.go:123] Request to "/apis/build.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.705881   24643 patch_genericapiserver.go:123] Request to "/apis/build.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.705968   24643 patch_genericapiserver.go:123] Request to "/apis/apps.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.705985   24643 patch_genericapiserver.go:123] Request to "/apis/apps.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706192   24643 patch_genericapiserver.go:123] Request to "/apis/apps.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706254   24643 patch_genericapiserver.go:123] Request to "/apis/apps.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706348   24643 patch_genericapiserver.go:123] Request to "/apis/project.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706413   24643 patch_genericapiserver.go:123] Request to "/apis/apps.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706428   24643 patch_genericapiserver.go:123] Request to "/apis/project.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706453   24643 patch_genericapiserver.go:123] Request to "/apis/project.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706491   24643 patch_genericapiserver.go:123] Request to "/apis/project.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706548   24643 patch_genericapiserver.go:123] Request to "/apis/project.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706646   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706683   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706706   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706729   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:24 fedora microshift[24643]: W0913 10:30:24.706755   24643 patch_genericapiserver.go:123] Request to "/apis/template.openshift.io/v1" (source IP <IP_ADDRESS>:38756, user agent "Go-http-client/2.0") before server is ready, possibly a sign for a broken load balancer setup.
9月 13 10:30:27 fedora microshift[24643]: E0913 10:30:27.911736   24643 pod_workers.go:190] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"amq-broker\" with ImagePullBackOff: \"Back-off pulling image \\\"registry.redhat.io/amq7/amq-broker:7.8\\\"\"" pod="amq-broker/amq-broker-9c78cb94-jmxrk" podUID=a0d624df-a317-4686-a686-f8c4d39e0324

Thanks for your time. Please give me more guide.

@ggiguash

I change mode sudo chmod 644 /etc/crio/openshift-pull-secret
restart service crio microshift
log info oc describe pod amq-broker-9c78cb94-m7xnb -n amq-broker

[user@fedora ~]$ oc describe pod amq-broker-9c78cb94-m7xnb -n amq-broker
Name:           amq-broker-9c78cb94-m7xnb
Namespace:      amq-broker
Priority:       0
Node:           fedora/<IP_ADDRESS>
Start Time:     Tue, 13 Sep 2022 11:49:19 +0800
Labels:         app=amq-broker
                pod-template-hash=9c78cb94
Annotations:    <none>
Status:         Pending
IP:
IPs:            <none>
Controlled By:  ReplicaSet/amq-broker-9c78cb94
Containers:
  amq-broker:
    Container ID:
    Image:          registry.redhat.io/amq7/amq-broker:7.8
    Image ID:
    Ports:          61616/TCP, 8161/TCP, 5672/TCP, 1883/TCP
    Host Ports:     0/TCP, 0/TCP, 0/TCP, 0/TCP
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      AMQ_USER:      admin
      AMQ_PASSWORD:  admin
      AMQ_PROTOCOL:  amqp,mqtt
      AMQ_DATA_DIR:  /data
    Mounts:
      /data from amq-broker-datavol (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5jg29 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  amq-broker-datavol:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  amq-broker-pvc
    ReadOnly:   false
  kube-api-access-5jg29:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
    ConfigMapName:           openshift-service-ca.crt
    ConfigMapOptional:       <nil>
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  42s   default-scheduler  Successfully assigned amq-broker/amq-broker-9c78cb94-m7xnb to fedora
  Normal  Pulling    42s   kubelet            Pulling image "registry.redhat.io/amq7/amq-broker:7.8"
[user@fedora ~]$ oc describe pod amq-broker-9c78cb94-m7xnb -n amq-broker
Name:         amq-broker-9c78cb94-m7xnb
Namespace:    amq-broker
Priority:     0
Node:         fedora/<IP_ADDRESS>
Start Time:   Tue, 13 Sep 2022 11:49:19 +0800
Labels:       app=amq-broker
              pod-template-hash=9c78cb94
Annotations:  <none>
Status:       Pending
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/amq-broker-9c78cb94
Containers:
  amq-broker:
    Container ID:
    Image:          registry.redhat.io/amq7/amq-broker:7.8
    Image ID:
    Ports:          61616/TCP, 8161/TCP, 5672/TCP, 1883/TCP
    Host Ports:     0/TCP, 0/TCP, 0/TCP, 0/TCP
    State:          Waiting
      Reason:       ErrImagePull
    Ready:          False
    Restart Count:  0
    Environment:
      AMQ_USER:      admin
      AMQ_PASSWORD:  admin
      AMQ_PROTOCOL:  amqp,mqtt
      AMQ_DATA_DIR:  /data
    Mounts:
      /data from amq-broker-datavol (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5jg29 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  amq-broker-datavol:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  amq-broker-pvc
    ReadOnly:   false
  kube-api-access-5jg29:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
    ConfigMapName:           openshift-service-ca.crt
    ConfigMapOptional:       <nil>
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age   From               Message
  ----     ------     ----  ----               -------
  Normal   Scheduled  43s   default-scheduler  Successfully assigned amq-broker/amq-broker-9c78cb94-m7xnb to fedora
  Normal   Pulling    43s   kubelet            Pulling image "registry.redhat.io/amq7/amq-broker:7.8"
  Warning  Failed     1s    kubelet            Failed to pull image "registry.redhat.io/amq7/amq-broker:7.8": rpc error: code = Unknown desc = error pinging docker registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp <IP_ADDRESS>:443: connect: connection refused
  Warning  Failed     1s    kubelet            Error: ErrImagePull
  Normal   BackOff    0s    kubelet            Back-off pulling image "registry.redhat.io/amq7/amq-broker:7.8"
  Warning  Failed     0s    kubelet            Error: ImagePullBackOff
[user@fedora ~]$ oc describe pod amq-broker-9c78cb94-m7xnb -n amq-broker.yaml [C^C
[user@fedora ~]$ oc describe pod amq-broker-9c78cb94-m7xnb -n amq-broker
Name:         amq-broker-9c78cb94-m7xnb
Namespace:    amq-broker
Priority:     0
Node:         fedora/<IP_ADDRESS>
Start Time:   Tue, 13 Sep 2022 11:49:19 +0800
Labels:       app=amq-broker
              pod-template-hash=9c78cb94
Annotations:  <none>
Status:       Pending
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/amq-broker-9c78cb94
Containers:
  amq-broker:
    Container ID:
    Image:          registry.redhat.io/amq7/amq-broker:7.8
    Image ID:
    Ports:          61616/TCP, 8161/TCP, 5672/TCP, 1883/TCP
    Host Ports:     0/TCP, 0/TCP, 0/TCP, 0/TCP
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Environment:
      AMQ_USER:      admin
      AMQ_PASSWORD:  admin
      AMQ_PROTOCOL:  amqp,mqtt
      AMQ_DATA_DIR:  /data
    Mounts:
      /data from amq-broker-datavol (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5jg29 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  amq-broker-datavol:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  amq-broker-pvc
    ReadOnly:   false
  kube-api-access-5jg29:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
    ConfigMapName:           openshift-service-ca.crt
    ConfigMapOptional:       <nil>
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  65s                default-scheduler  Successfully assigned amq-broker/amq-broker-9c78cb94-m7xnb to fedora
  Warning  Failed     23s                kubelet            Failed to pull image "registry.redhat.io/amq7/amq-broker:7.8": rpc error: code = Unknown desc = error pinging docker registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp <IP_ADDRESS>:443: connect: connection refused
  Warning  Failed     23s                kubelet            Error: ErrImagePull
  Normal   BackOff    22s                kubelet            Back-off pulling image "registry.redhat.io/amq7/amq-broker:7.8"
  Warning  Failed     22s                kubelet            Error: ImagePullBackOff
  Normal   Pulling    10s (x2 over 65s)  kubelet            Pulling image "registry.redhat.io/amq7/amq-broker:7.8"

I also try to create a secret follow link, but I can not pull image.
oc create secret generic pull-secret -n amq-broker --type=kubernetes.io/dockerconfigjson --from-file=.dockerconfigjson=/etc/crio/openshift-pull-secret

I also login by oc command line, but can not to login in web size. When I use podman login, I can login successfully.

oc login registry.redhat.io

error: couldn't get https://registry.redhat.io:443/.well-known/oauth-authorization-server: unexpected response status 404

@TUT-jiayou, can you confirm that the following sequence works for you, i.e. you're able to pull the AMQ image using crictl?
sudo crictl pull registry.redhat.io/amq7/amq-broker:7.8

If the command fails, you can look at the journal for hints on what's wrong
sudo journalctl -n 20 --no-pager -xu crio

@ggiguash  thks.

I check the crio config file/etc/crio/crio.conf.d/microshift.conf, modify the file followed by crio doc

[crio.network]
# cbr0 is the name configured by flannel in /etc/cni/net.d/ config file
# by declaring this crio will wait until that network is configured.
cni_default_network = "cbr0"
# rhel8 crio is configured to only look at /usr/libexec/cni, we override that here
plugin_dirs = [
        "/usr/libexec/cni",
        "/opt/cni/bin"
]

[crio.image]
global_auth_file = "/etc/crio/openshift-pull-secret"

Thanks for your time @ggiguash


Port to Python 3

Python 2 is end of life at the first of the year.

The script has been updated.


last row not adjust

Last row not adjust in my gallery, single item show in my last row of gallery. how to solve this problem.

@jksenthilraja have you tried both options for for the parameter lastRow like
$('.photos').gallerify({
    mode:'default',
    lastRow:'adjust',
});

and
$('.photos').gallerify({
    mode:'default',
    lastRow:'fullwidth',
});

like described in the docs? Is there an option that fits your needs?
The Gallery is working based on a maximum number of items in a row - if you don't have a fitting number of images the last row might have only one image, but will be centered.
In theory the gallery could use one image of the second last row to not have only one image in the last row, but that wouldn't solve the issue as 2 images on a 4k screen would still be too less and would be centered in the middle.
If you have a recommendation or idea for improvement let me know.

There should be this option: lastRow: 'none' which removes the last uncomplete row

That sounds like a good alternate solution for people that don't care about showing all images.
I can push a fix this afternoon.
BTW: other galleries struggle with the same issue and don't have satisfying solutions as well - at least I didn't find one.

A big downside would be that this is going to be hidden on mobile (or eventually smaller screens) and this would also hide panorama images that have a with that would fill the screen - but there could be a solution for that.

Thank you guys!

@jksenthilraja I'm working on this, but as long as I don't have a final version / have the best approach you might want to check out #22 wich has the beta code of my changes.

I did some testing and my changes seem to work fine for a first update.


Console message error

I removed the old part in the config but it always appears, so fix it as soon as you can, thanks!

Plugin work with 1.20.6?

Fixed with #88


After installing SwifterSwift my view´s corner radius changed

What did you do?

I set myView.layer.cornerRadius = 8 first, then after installing this Pod...

What did you expect to happen?

myView.layer.cornerRadius = 8 // Corner rounded 8pts

What happened instead?

I see the corners very rounded.. at leaat 20pts. And no matter what value I set.. it always look very rounder. Before installing the Pod, it worked

SwifterSwift Environment

SwifterSwift version: 4.0.1
Xcode version: 9.0
macOS version running Xcode: Sierra 10.12.6
Swift version: 3.2
Platform(s) running SwifterSwift: iOS 11

Hey @jpghelfi, I'm not sure I understood the problem clearly :)
SwifterSwift has the extension cornerRadius  to set corner radius a for a UIView, all it does is setting cornerRadius for view's layer, and nothing more.
Could you please place 2 print(yourView.layer.cornerRadius) statements before and after setting cornerRadius to see what is exactly happening.

@jpghelfi any update on this :)


Exposing http client

Motivation
Small refactor to expose OKHttp as our defactor http implementation.  I left the interfaces in for testing and backwards compatibility, but we can discuss removing them.
https://issues.jboss.org/browse/AEROGEAR-7542
Description
This makes a few small changes.
MobileCore getHttpLayer returns a OkHttpService.
OKHttpService now has a method to get the http client as well as javadocs covering how it is configured.
Progress

[x] Done Task

Additional Notes
Contact @danielpassos for additional testing information.

@secondsun  ./gradlew spotlessApply && git commit -a --amend && git push -f origin AEROGEAR-7542_expose_ok_http


[SC-211260] NextStrain Modal strings

Summary:

What: <brief description>
Ticket: sc211260
Env: none

Demos:

Notes:
I had to copy/paste the strings, so it would be helpful to have a check that I didn't copy/pasta.
Checklist:

[x] I merged latest <base branch>
[x] I manually verified the change
[x] I added labels to my PR
[x] I tested in multiple browsers
[ ] I added relevant unit tests
[ ] I have notified others of changes they need to make locally (migrations, jobs, package updates, etc)

[] fix style


Denver 2022

Should have Sessionize up as soon as they review for the free goodness.  Modify anything as you need to and then I'll get things updated as we progress.  Also will be sending an email your way 👯
Event Title	Denver 2022
Event Date	September 17, 2022
Event Time	0830 MST - 0430 MST
CFP URL
CFP End Date
Registration URL
Event Location	Cherry Creek Presbyterian Church
Event Description	Making all your SQL and Azure dreams come true
Organizer Name	Denver SQL Users Group
Contact Email<EMAIL_ADDRESS>

event complete


No Commands avaible?

Hello,
since today I cannot use any commands. When I type "Day Planner" in the quick opener, I will only see the notes with that in the name, no possible commands.
I am using v0.5.8 of Day Planner and v0.10.1 of Obsidian.

DUmbo! I used the wrong hotkey :(


No targets specified and no makefile found.  Stop.

Hey,
I am trying to install the module on Red Hat Enterprise Linux Server release 7.4 (Maipo), When I do I get the following error:
[root@896932-web3 google-authenticator-libpam-master]# ./bootstrap.sh
Makefile.am:35: error: Libtool library used but 'LIBTOOL' is undefined
Makefile.am:35:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
Makefile.am:35:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
Makefile.am:35:   If 'LT_INIT' is in 'configure.ac', make sure
Makefile.am:35:   its definition is in aclocal's search path.
autoreconf: automake failed with exit status: 1
[root@896932-web3 google-authenticator-libpam-master]# ./configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define EXTENSIONS... yes
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking whether make supports nested variables... yes
checking dependency style of gcc... gcc3
checking whether to enable maintainer-specific portions of Makefiles... yes
./configure: line 4186: LT_INIT: command not found
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking sys/fsuid.h usability... yes
checking sys/fsuid.h presence... yes
checking for sys/fsuid.h... yes
checking for setfsuid... yes
checking for security/pam_appl.h... no
checking for security/pam_modules.h... no
checking for pam_get_user in -lpam... no
configure: error: Unable to find the PAM library or the PAM header files
[root@896932-web3 google-authenticator-libpam-master]# make
make: *** No targets specified and no makefile found.  Stop.
[root@896932-web3 google-authenticator-libpam-master]# sudo make install
make: *** No rule to make target `install'.  Stop.
Please advice how to fix.
Thanks,

Your configure is erroring:
configure: error: Unable to find the PAM library or the PAM header files

You need to have the PAM libs and headers installed and in the search path for the configure call

Also you may need to install libtool, based on the first error message.
Closing for lack of follow-up by OP.


Remove Apifox.Apifox 2.4.9 to Ruihu.Apifox 2.4.9

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: http://cdn.apifox.com/download/2.4.9/Apifox-2.4.9.exe
Status Code: 200
(Automated message - build 869)


Keeping record of model version

Current NAMELIST based system does not keep track of the source code or the executable (it says "latest" or what ever happens to be in the NAMELIST). Updating NAMELISTs whenever the code changes is not practical, so are there alternatives for the hard-coded version number?

As long as you use git clone to obtain the model code and the provided runscript, the version number is automatically obtained from the version tags. However, not sure if this works well with the DEV-branch now since the tags are assigned to master. In particular, the value "latest" will occur if you're not using git to download the model.

Version is not anymore "latest", but there is an option to add hard-coded information about model versions.


typo

[Enter feedback here]
Resource logs in Key Vault should be enabled
Document Details
Resource logs in Key Vaults should be enabled
There is no s in de display name of json file
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 701faca1-7fa1-5cfd-1163-0f191b62794d
Version Independent ID: 4cac67ee-0cd6-af0f-0698-55b5e7ad2130
Content: Integrate Azure Key Vault with Azure Policy
Content Source: articles/key-vault/general/azure-policy.md
Service: key-vault
Sub-service: general
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@RamazanInceHU
Thanks for your feedback! We will investigate and update as appropriate.

@RamazanInceHU
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!

@RamazanInceHU
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!


Add migration guide 0.x to 1.0.0

Add migration guide to  /docs, as discussed in #348.

Don't worry about the tests.

@allcontributors please add @dislick for documentation