text:
Error: llama runner process has terminated: signal: aborted (core dumped)

What is the issue?
ollama run gemma2:27b-instruct-q8_0
,....
Error: llama runner process has terminated: signal: aborted (core dumped)

nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Wed_Jun__8_16:49:14_PDT_2022
Cuda compilation tools, release 11.7, V11.7.99
Build cuda_11.7.r11.7/compiler.31442593_0
OS
Linux
GPU
Nvidia
CPU
Intel
Ollama version
0.1.45

gemma2 needs ollama  0.1.47.  But there's also an issue with inaccurate calculation of required VRAM, see https://github.com/ollama/ollama/issues/5350#issuecomment-2196929454

I got the same with the 9b model
➜  media ollama list
NAME                               	ID          	SIZE  	MODIFIED
gemma2:latest                      	c19987e1e6e2	5.4 GB	21 minutes ago
yi:9b                              	3af70141e8eb	5.0 GB	6 days ago
phi3:14b                           	1e67dff39209	7.9 GB	6 days ago
deepseek-coder-v2:latest           	6d3369b54a0e	8.9 GB	10 days ago
➜  media ollama run gemma2
Error: llama runner process has terminated: signal: aborted (core dumped)

upgraded to the latest ollama fixed my problem

Thanks @felixgao @mikestut - this should be fixed now in 0.1.48

authors: felixgao jmorganca mikestut rick-github

repo: ollama/ollama


text:
Is it possible to configure ollama deployed in docker?

I pull docker image from dockerhub and launched a few models and then found the num of user requests was limited.
In the documentation it shows that this could be solved by set up OLLAMA_NUM_PARALLEL by systemctl commands.
How can I do this since systemctl is not included in the docker container?

Plain docker:
docker run -d -v ollama:/root/.ollama -p 11434:11434 -e OLLAMA_NUM_PARALLEL=2 --name ollama ollama/ollama

Docker compose:
services:
  ollama:
    image: ollama/ollama
    ports:
      - 11434:11434
    environment:
      - OLLAMA_NUM_PARALLEL=2

source: gharchive/issue

authors: rick-github wizounovziki

license: MIT

license_type: permissive

license_source: github-api


text:
Do not reinstall the CLI tools if they are already installed on macOS

Check installed() inside of the install function before running the cli setup commands. Fix #5305.

Hi @seanchristians, thanks for the PR. I believe installed() is already checked before triggering the first time installer screen. Do you know what /usr/local/bin/ollama is pointing to in your case? This might help debug why https://github.com/ollama/ollama/issues/5305 is happening.

Hi @jmorganca, my installer script runs this command: /bin/ln -F -s /Applications/Ollama.app/Contents/Resources/ollama /usr/local/bin/ollama. It is targetting the correct ollama executable within the installed application.
I submitted this PR because installed() is not checked before triggering the first time installer screen.
Please consider re-opening this PR.

source: gharchive/pull-request

authors: jmorganca seanchristians


text:
Time format change possibility for entities displaying remaining or countdown time.

Pease add possibility to choose what kind of time format to display on "Remaining Time" or "Countdown Time" type entities.
Would like to see option to switch in between hh.mm.ss to hh.mm or HH.mm format as some entities does not display seconds at all.
It's could be some trigger in  integration setting window or anything. this would be more easier for users and cleaner for system to not create additional converters

I'd definitely be interested it in this.
I discovered the timer bar card in hacs from the doc here. It's great but it doesn't work in a grid style card.
Would love the format change.

To be more useful in automations, I'd argue this should just come across as number of minutes. Consumers of the stat can always come up with their own display, but being able to do triggers like "time remaining < 5 minutes, then send notification to get ready" would be great, hard to do when the time remaining is a string.

authors: Datortarp5 Kapncanada sfumarolo


text:
Почему решили перейти на node-fetch?

Есть какие-то плюсы в сравнении с request?

request слишком перегружен и тянет за собой кучу зависимостей, в которых нет необходимости конкретно в node-vkapi.
Также, как я вижу, request не особо поддерживается: висит более 500 issues, многие из которых без ответа, либо не исправлены.
Тем более, автор request уже давненько выпустил "вторую" версию, которая полностью опирается на node-fetch и которую я бы тоже не советовал использовать, как минимум из-за этого.

authors: lostcodder olnaz

repo: olnaz/node-vkapi

license: isc

license_source: bigquery


text:
Improved message/event timestamping

The current control API implementation just wraps A2_event structs up as messages and passes those via sfifos, with timestamps and all. Since, even after #204, there will only be one API-to-engine sfifo per A2 state (as the API is still not fully threadsafe anyway), we need to timestamp all messages at all times, using a2_TimestampReset() for contexts with timestamping "disabled."
One approach would be to remove the timestamps from the existing messages, and instead use separate timestamping messages. Interfaces may keep track of the last timestamp message sent to their target engine state, in order to send timestamp messages only when necessary. There would be a special message to disable timestamping altogether, causing subsequent messages to be scheduled ASAP when they arrive, meaning no delays, and no risk of "late event" warnings when timestamping is not actually used.

Or, we can just do this: 0ee5030fa548d9d3df23cf733043328e989effed. Serves the same purpose, but seems simpler and more efficient. I think this will do.

license: Zlib


text:
Fixed advisory lcok getter. No need in Scan, because OID 2278 reterns…

… here(Void). It causes error
I encountered a scan error in &x when using the tool because OID 2278 is unfamiliar to the scanner. I found out that scanning is applicable only when receiving the result of the pg_try_advisory_lock function, which returns the status as a boolean value. In this case, a void is returned that cannot be scanned and this causes an error.

It only happens with using a template. With empty SchemaFile field all gonna be ok.

repo: olomix/go-test-pg


text:
dropdown/split button is little lower than info-button in the same row

<div class="row flex-justify-around bg-red p-1">

if remove p-1 from the row, it will be more clear:

https://codepen.io/taurenshaman/pen/ExxwvwJ
Thank you very much!

Thx, fixed in 4.3.3

authors: olton taurenshaman

repo: olton/Metro-UI-CSS

license: mit


text:
Uncaught ReferenceError: metroDialog is not defined

How to get the reference of metroDialog? I have already imported the metro.js file in the html, but when specifying the method metroDialog.toggle("#dailog"), where "#dialog" is the id of the div. I am getting the error.
Also, how do i use Metro UI in angular to gain access to the metroDialog or $.Dialog?
Appreciate any guidance on the same.

use metroDialog.open(angular.element("#dialog")[0]).


text:
pydantic stops video_understanding task

my pydantic version is 2.2, and when run the video_understanding task, it shows the warning and terminates the run.
UserWarning: Field "model_id" has conflict with protected namespace "model_".

You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
  warnings.warn(
[1]    63213 illegal hardware instruction  python run.py

I can see solutions such as from pydantic import ConfigDict is added in omagent_core/llm/gpt.py and
class Config:

        protected_namespaces = ()
        extra = "allow"

is added in omagent_core/llm/openai_gpt.py.
But it doesn't resolve the issue.

It is caused by the OVD tool in 'engine/tools/ovd_tool.py'. I fixed it in the most recent commit.

repo: om-ai-lab/OmAgent


text:
Flutter 3.27 incompatible: replace all hashValues with Object.hash

Current (1.0.1) version in pub.dev in incompatible with Flutter 3.27 due to deprecated API usage. All usages of hashValues() must be replaced with Object.hash()

Current (1.0.1) version in pub.dev in incompatible with Flutter 3.27 due to deprecated API usage. All usages of hashValues() must be replaced with Object.hash()

There's a open pull request here: https://github.com/omarhurani/flutter_painter/pull/84

authors: g-starr koldoon


text:
Scheduled Molecule tests fail with an SSLHandshakeException

See https://github.com/ome/ansible-role-omero-server/runs/2439809443?check_suite_focus=true
The import test in particular failed with
javax.net.ssl.SSLHandshakeException: The server selected protocol version TLS10 is not accepted by client preferences [TLS12]

The scheduled build for the omero-server-docker also failed (https://github.com/ome/omero-server-docker/runs/2430310101?check_suite_focus=true), possibly for the same reasons as the Dropbox test import did not create any image
/cc @jburel @joshmoore

After comparing the packages, I think I found the root cause. From the release notes for OpenJDK 8u292
  - JDK-8202343: Disable TLS 1.0 and 1.1

Also https://aws.amazon.com/blogs/opensource/tls-1-0-1-1-changes-in-openjdk-and-amazon-corretto/

repo: ome/ansible-role-omero-server


text:
Address small issue with sysadmin links.

Aiming to turn OMERO-docs green and tidy up a little along the way.

Yesterday evening's build (90) was nicely green. Merging.

authors: joshmoore mtbc

repo: ome/ome-documentation


text:
Multi well validation

Currently, when validating a Plate, we only validate the First image in each Well and there's no way to validate other Images except to open each Well in turn.
This PR allows you to choose a Well Index to validate and also allows you to validate ALL Wells in a Plate.
However, this can result in loading a lot of data, so it's not the default behaviour.
To test, use e.g. plate SQ00014814__2016-05-23T17_24_56-Measurement1.ome.zarr/ PR deployment:
https://deploy-preview-14--ome-ngff-validator.netlify.app/?source=https://cellpainting-gallery.s3.amazonaws.com/cpg0004-lincs/broad/images/2016_04_01_a549_48hr_batch1/images_zarr/SQ00014814__2016-05-23T17_24_56-Measurement1.ome.zarr/
Use the all link to check all Wells (or add &well=all to the URL). This highlights 1 Well that is invalid:

Clicking on that Well shows which Images are invalid:

@sbesson Thanks - Hopefully this is better:

I :heart: the "all images" visualization. :)

authors: joshmoore will-moore

repo: ome/ome-ngff-validator


text:
🛑 UoD SLS OMERO (4064) is down

In b5c6cfc, UoD SLS OMERO (4064) (nightshade.openmicroscopy.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UoD SLS OMERO (4064) is back up in c998685 after 12 minutes.

repo: ome/upptime


text:
remove entry

Update demo list


text:
Add One Signal

Add one signal plugin

One signal added


text:
add deposit.all method to child chain

#303

@jarindr the CI/integration-test failed after rebased master, not sure why... still good to merge ?

Ohh, i think this test fails sometimes, re-running the test should work.

authors: Pongch souradeep-das

repo: omgnetwork/omg-js


text:
Failed to bridge ERC20

So, I am trying to brige my OMG token.
The first tx was for approving the spend, that was succesfull. Afterwards I got to metamask popup to send the tokens to the boba l2.
I did decline that tx (high gas fees)
Now a bit later I wanted to bridge the tokens but now I just keep getting the popup Failed to brige erc20.
When I open up the browser debug it shows me this:

same issue here, I was able to bridge eth to l2 on the wallet with the error for omg. I was also able to bridge both eth and omg from another wallet,   Gas is nuts.......  over$140 per wallet, ate up a fair portion of my small stack.

Yea, I was thinking about sending my omg to another wallet to do it from there if it is not resolved. still something to look into for them :)

my plan was to send and stake out of a couple wallets and see what happens with the air drop they announced, so I would like to know how to get past the failure.  I also canceled when i saw the gas fees for OMG.  It was around 120 and I only had 60 total OMG  Almost half of the value lost to gas.  Guess that is why we are all hunting layer 2.

Investigating now. The best option for cost effective on ramping is probably the Fast Bridge. There will be fixes / action on this with 24 hours. Yup gas is insane.

I have the same problem. When I accepted fee for bridge so metamask notification sent me that transaction is not accepted but etherscan is ok, so I don´t know what next. When I try same again so bobanetwork write me "Failed to brige erc20"

Investigating now. The best option for cost effective on ramping is probably the Fast Bridge. There will be fixes / action on this within 24 hours. Yup gas is insane.
Anecdotal observation: some people are able to bridge OMG L1->L2 - this issue only seems to affect a subset of users/wallets.

From what I've seen, if you cancel the transaction (cause users saw the high gas costs) or the transaction fails the first time, the wallet won't work anymore.

I don't really understand why it creates something somewhere and it doesn't work 100%. Only the transfers cost me 30 USD and in the end it doesn't work again. Is there any competent person to whom I will send the link from etherscan and will be able to explain and put this into operation?

We have a partial fix. The problem is that some users were using an outdated firmware for their Ledger hardware wallets.
https://github.com/omgnetwork/optimism/pull/496/commits/1c792e3c2c5cb4b34c3c4ad5f120d68393209562

I'm using the metamask I downloaded today, so it's hard to be an outdated version

The above fix is specific for people using the Ledger hardware wallet with hardware firmware < 2.0.0

I wonder how much I get in the airdrop. Normally it is enough to send the address of the wallet to the date and nothing has to be transferred anywhere. I pay the transfer fees here and it still doesn't work. What's the point of inventing something new when it doesn't work and it's not tested?

It doesn't work for $ 20, so here you advise me to transfer it for several times higher fee and hope that it will be transferred and if not, someone will deal with it preferentially? What is this nonsensical advice?

So what should I do now?

send it fast for nonsense, which I certainly won't do when I see it here ...
Wait for someone to fix it?
When will someone fix it?

As noted above, we are working on this right now.
1/ Bridge issues for users of Ledger hardware wallet below 2.0.0 = resolved - please update firmware
2/ Bridge issues for some users of MetaMask version below  10.1.0 = resolved - please update MetaMask
3/ Bridge issues for some users of MetaMask version ===  10.1.0 = open - investigating

@CAPtheorem I just arrived home from work, I just tried it with a different pc. I imported the account where I have my omg tokens on into metamask 10.1.0.
I do still get the error Failed to bridge erc20 token.
Also to clarify the steps I did:
1: Approve the spend tx
2: decline the tx that popped up to send my omg tokens to the boba layer  (high tx fees)
I am able to transfer eth to the boba layer it only happens with the omg tokens (did not try any other erc20 token tho)
Please let me know if I can help you further

As noted above, we are working on this right now.
1/ Bridge issues for users of Ledger hardware wallet below 2.0.0 = resolved - please update firmware
2/ Bridge issues for some users of MetaMask version below 10.1.0 = resolved - please update MetaMask
3/ Bridge issues for some users of MetaMask version === 10.1.0 = open - investigating

I have version 10.1.0 I will wait

How to unconnected metamask wallet from bobanetwork?

I tried uninstall metamask from chrome a install again but nothing - still the same "Failed to brige erc20" I have 3 transactions 2 ok with etherscan a one fail. It is interesting that I sent the conversion only once, because it did not work several times, but in etherscan I have 3 outgoing transactions, where I was always deducted a fee. It really doesn't work very well.

I have read the above comments and have the same issue, able to approve but not bridge.
I have Ledger 2.0.0 and MM 10.1.0
I have used my Ledger successfully yesterday, so obviously less than 1 yr since last use.
I have enabled contract data.
My approval happened successfully, although I did set my gas price to 76 gwei, so it took a bit of wait before it cleared mempool.  And while Etherscan showed that it cleared, my MM kept showing that the txn was pending.  I had to close the browser and launch again in order for MM showing the approve under activity.
When I tried to bridge, it failed immediately.  I tried several times

The root cause has been found, and a fix in in the works. Briefly, it relates to the OMG token's nonstandard configuration relative to most other tokens, based on contract architecture choices made in June of 2017.

Thx.  So if I have already successfully approved once for a bridge amt, do I have to go back and do all 3 steps or just steps 1 and 3?

It depends. For example, if you approved 10, but want to bridge 7, you are all set. But if you approved 3, and want to bridge 7, then three steps will be needed. 3->0, 0->7, bridge. This is out of our control, and a basic feature of the OMG token contract.

What do you mean by all set?  Just now I tried to bridge an amount less than what was successfully approved earlier today.  It gave me the same erc 20 error.
Do I need to approve 0, and then approve all, and then bridge?
The above instructions and your responses are a bit confusing.
Thx

we are about 3 hours away from actual production

Oh, got it.  Sorry for jumping the gun

Saw the screen shot and the sentence "fix moving to production" and thought it is a done deal

sorry - that means we have everything working locally, and are in the process of moving it to production

My metamask wallet is pretty new.  This year.  I also bridged some eth off the same wallet and that went through with no issues.  I have a secrod metamask wallet that both eth and omg went through with no problems.  Same metamask acct so it can't be an issue with the firmware.  It is a bummer that I burned a shit ton of expensive eth trying to get bridged with the approvals. I know you folks are testing and bugs come out.    Thanks for the help.  I'm going to try to bridge omg again tomorrow night.  Between the eth and omg and approvals I'm at about 140 USD per wallet. So between the two I'm looking at nearly 300usd That is to bridge 60 omg and ..07 eth between the two.    Makes it tough for the small fish to be part of defi
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: CAPtheorem @.>
Sent: Tuesday, September 21, 2021 6:42:24 PM
To: omgnetwork/optimism @.>
Cc: lowballer356 @.>; Comment @.>
Subject: Re: [omgnetwork/optimism] BUG + Partial Fix: Failed to bridge OMG L1->L2 for some users/wallets (#501)
sorry - that means we have everything working locally, and are in the process of moving it to production
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/omgnetwork/optimism/issues/501#issuecomment-924513294, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVXGXZ52GI56ZBHBJQ3OATDUDEYABANCNFSM5EN2SNUQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

It depends. For example, if you approved 10, but want to bridge 7, you are all set. But if you approved 3, and want to bridge 7, then three steps will be needed. 3->0, 0->7, bridge. This is out of our control, and a basic feature of the OMG token contract.

Hi: A request: Once the fix IS in production, more clear, specific, and exact instructions on how we can proceed to accomplish the Bridge would be very much appreciated. I, like several others, have "Approved Spends" [2 in my case at a cost of ~$25]... but--so far--it is not at all clear IF we can use those approvals to complete our L2 Bridge and exactly HOW [step by step process...] we can use to actually, successfully DO it ...OR--on the other hand--IF we need to initiate a whole new Bridging process from the start.  If the latter, but really in either case, as an owner of many thousand OMG, I expect I can speak for us all in stating the obvious: we'd all appreciate some compensation for our lost fees as well as our time in helping Boba Network to BetaTest the highly frustrating and largely non-functional bridging UX that you've subjected us to...Thanks for hearing this!

I hear you and it's been a long day for us all. Step one is to get the OMG-bridges sorted and tested. Separately, please retain your TX hashes for the unnecessary approvals. Speaking for everyone here, thank you for all the information and patience, and please keep bug reports and suggestions coming.

@RogerThat002 @lowballer356 @nocturnien @Hellprdel @Septboba @jwboba - please retain your TX hashes - standby for more specific instructions. We have your back.

Jet86 on TG or Discord is waiting for you

@RogerThat002 @lowballer356 @nocturnien @Hellprdel @Septboba @jwboba - please log a support ticket in our Discord by heading to the #support-boba channel and clicking "Create ticket" then entering the details, including the transaction hashes.
If you have any issues, you can reach out to me either in Discord or in Telegram.

Can you guys give us a quick walk through of how to get the stuff we sent to L2 to show up. I tried finding said #support-boba channel to create a ticket and had zero luck, even sent a screen shot of what I was seeing on discord.

I wanted to bridge yesterday. Gas charges left in etherscan's transactions are ok, but nothing happened. Subsequently, I tried and wrote to me that Failed. I tried it in the morning and the transaction went through again, but nothing moved. It already cost me about $ 70 and still nothing. Developers must be great masters if they can't do this either.
So a question for developers:
Who will refund my gas charges if it doesn't work?
Is there a well-founded person who is able to answer me, why etherscan tells me that the transaction is ok, but nothing has been transferred to L2?

Well, to be honest it seems like you are just resetting the approval, but after the txs it worked. bit of a shame as it cost money
I found a similar issue with staking the omg tokens on the l2 I will create a new ticket for it

@CAPtheorem, @jet86 I am facing the same issue. Were there more specific instructions given somewhere to walk through potential fixes? I have tried following the steps above 5+times this evening to bridge OMG, after also updating all software and firmware on ledger and metamask and still all transaction attempts are failing. Any help appreciated. Thanks

@RogerThat002 @lowballer356 @nocturnien @Hellprdel @Septboba @jwboba - please log a support ticket in our Discord by heading to the #support-boba channel and clicking "Create ticket" then entering the details, including the transaction hashes.
If you have any issues, you can reach out to me either in Discord or in Telegram.

G'morning! Thanks to the team for all your efforts to address this bug. I hear that a fix is now in production and we have a UX that delivers successful bridging...I will retest it again myself tonight and report my experience. Also, I hope the team is taking seriously the need to have a communication specialist developing detailed instructions on exactly how to Bridge--especially with noobs in mind--as I've suggested above.  We've seen how even experienced crypto investors such as myself have had a very frustrating and time-consuming experience in bridging to Boba.  I'm concerned that too many who're new to Boba and crypto will be left behind unnecessarily. That outcome would be quite unfortunate for all of us.

Can you guys give us a quick walk through of how to get the stuff we sent to L2 to show up. I tried finding said #support-boba channel to create a ticket and had zero luck, even sent a screen shot of what I was seeing on discord.

I found the #support-boba channel on Boba's Discord, which you'll want to Join, if you haven't already. https://discord.com/invite/m7NysJjKhm It's easy to create a ticket once you're there.

They fixed the channel after I messaged Jet. I still have not gotten an answer back but Jet is not online so it will probably take time.

@CAPtheorem Glad to see that the fix has been pushed to production.  However, when I tried to fast bridge, I am told that the liquidity bridge only has 6.6 OMG.  When will it increase?  What would cause it to increase?  I prefer to use fastbridge since I already have spent eth on an approval (or does it not matter whether regular or fastbridge) and it is less costly?
Also, as echoed by other users here, we understand that we are early and things will break some times.  But it is very important for the team to provide solid communication and support coverage.  Your early users can help spread the word and evangelize the project if you take care of them.  On the flip side, if they get frustrated and leave, you wont get the positive network effect and possibly distractors.  Please make support/communication a strategic high priority item even though its tempting to chase after other fires that are more visible. thx

I think questions should be directed onto TG and Discord for support. Github is for bug fixing. @nocturnien fast bridge liquidity is provided by the community so you just have to wait for liquidity (other users providing it).

Looks like the liquidity is back up now.  But it seems that I have to approve again even though I am trying to bridge an amount equal to what I was approved yesterday.  @CAPtheorem I thought I dont need to approve again per what you wrote yesterday as long as I am bridging an amt less than what I previously approved?

Just wanted to let you know that I was able to successfully bridge my OMG over tonight and got both my eth and OMG staked.
It did charge me the approval fee twice tonight though.
I am a total newb on etherscan so I will need to figure out how to read it and how many extra charges were incurred through unnecessary additional approvals and try to get those logged somewhere for you.  Learning opportunity for me.
I understand you are still in beta, so things happen.  I am not expecting anything to be refunded, but if that is something you can do, or if you can sweeten the airdrop (if my pittance qualifies) , I would greatly appreciate it.
With that being said, I want to personally thank you for actually looking into this, being helpful and genuinely seeming to care about helping us get our assets through the bridge.  I have worked with several other help desks for other projects and their help desk sucked balls.
If you have a supervisor, please forward this to them, you are what I am looking for as a manager and I have been very satisfied with the updates, response time, insights, and resolution.
THANK YOU!
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: @.>
Sent: Wednesday, September 22, 2021 11:52 AM
To: @.>
Cc: @.>; @.>
Subject: Re: [omgnetwork/optimism] FIX: Failed to bridge OMG L1->L2 for some users/wallets (#501)
Looks like the liquidity is back up now. But it seems that I have to approve again even though I am trying to bridge an amount equal to what I was approved yesterday. @CAPtheoremhttps://github.com/CAPtheorem I thought I dont need to approve again per what you wrote yesterday as long as I am bridging an amt less than what I previously approved?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/omgnetwork/optimism/issues/501#issuecomment-925207581, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVXGXZ3QTTMWW5IK2NPSND3UDIQVXANCNFSM5EN2SNUQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

So, I tried to get my OMG staked last night and had the same issue with request to spend eth multiple times.  Unfortunately I wasn’t watching my balance and now my eth  balance is too low to unstake some eth, or to try to stake my OMG.  Bummer, I guess ill have to bridge some more at some point.  This is getting spendy.
Might want to look into why it is requesting that we authorize spending after spending has already been approved for a token multiple times.
Thank you.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: @.>
Sent: Tuesday, September 21, 2021 10:48 AM
To: @.>
Cc: @.>; @.>
Subject: Re: [omgnetwork/optimism] BUG: Failed to bridge OMG L1->L2 for some users/wallets (#501)
We have a partial fix. The problem is that some users were using an outdated firmware for their Ledger hardware wallets.
1c792e3https://github.com/omgnetwork/optimism/commit/1c792e3c2c5cb4b34c3c4ad5f120d68393209562
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/omgnetwork/optimism/issues/501#issuecomment-924217920, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVXGXZ4HPSSRWD32JI6L7KTUDDANXANCNFSM5EN2SNUQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@CAPtheorem @jet86 or anyone from the team, I have the same experience as @lowballer356.  I needed to do multiple approvals, a total of 3 before I was able to bridge.  This included once before the new fix and twice after the fix.  The 2 approvals after the fix happened immediately one after another.  Very strange and costly.  Not a happy camper right now.  And certainly not happy with the lack of responses to user comments in this thread.  This is not how your interact with the early adopters in the community.  My confidence in Boba, the protocol, and the team's responsiveness is pretty low.  I am seriously considering bridging my OMG back to L1 and dump them.

Good morning.  I was asked to save my hashes for this issue.  I believe I have that list although I am a newb and might not have them correctly logged.
Where should I send that list.
Thank you
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: CAPtheorem @.>
Sent: Tuesday, September 21, 2021 8:41:23 PM
To: omgnetwork/optimism @.>
Cc: lowballer356 @.>; Mention @.>
Subject: Re: [omgnetwork/optimism] FIX: Failed to bridge OMG L1->L2 for some users/wallets (#501)
@RogerThat002https://github.com/RogerThat002 @lowballer356https://github.com/lowballer356 @nocturnienhttps://github.com/nocturnien @Hellprdelhttps://github.com/Hellprdel @Septbobahttps://github.com/Septboba @jwbobahttps://github.com/jwboba - please retain your TX hashes - standby for more specific instructions. We have your back.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/omgnetwork/optimism/issues/501#issuecomment-924556368, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVXGXZ7EZ7DOIHZ34GGGT63UDFF6HANCNFSM5EN2SNUQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

repo: omgnetwork/optimism


text:
This pull request fixes per-column searches.

Though this fixes column searches for me, it's still to be reviewed by the maintainer if it affects any other adapter as well.

@shades684 yours to check   😉

@vaibhavpandeyvpz can you look at the open conversations?
@shades684 can you review it?

I'm fine with the solution as is.
In the long run we should have a different and more generic solution. I'd rather have some sort of callback per column if it's searchable so we can have the user extend the query.
What I'm missing in the current solution is: What happens if we have a datefield and we search for the string 20. Is 1-1-2000 valid or maybe 1-1-1920.
The solution that's defined here isn't generic (it's opinionated), but it solves/fixes a problem.

Ok   :)

I agree with @shades684 - possibility to have column filter with callback option would solve advanced requirements such as date range search and so on.

repo: omines/datatables-bundle


text:
fix: make odd length string errors go away

It seems the errors happened when omg_performance "simple perftest" tests ran.
After changes from cd094b589a6881cc38696dc7006c792a6b1415c5 we started ramping up the whole :omg_child_chain, including the Ethereum-machinery.
This machinery complained about the ethereum configs being malformed.
This proposes to revert to the selective start approach prior to the mentioned change, including some readability and doc improvements.
NOTE: to reproduce the odd length string error, tag happy_path_test and performance_test with tag: :this and do:
mix test --only this --seed 294090

Coverage increased (+0.007%) to 81.633% when pulling f3cb763adf9a9562d8493a74aa503a77c58dc916 on fix_odd_length_string_errors into c7bef096c875306eba4c98624674c0c153b7728a on master.

interestingly, if you do this: ExUnit.start(capture_log: true) it captures the error logs as well
https://github.com/omisego/elixir-omg/pull/657/files
runs:
https://circleci.com/gh/omisego/elixir-omg/5733
https://circleci.com/gh/omisego/elixir-omg/5743
now which approach is better. hard to say. if I play the devils advocate:

in this specific case, the idea was to run the simple perf tests without all EthereumListeners. But they get shutdown because there's no blockchain client running and the alarm captures them and then prevents them from restarting. So that's covered.
it might make the test maintenance difficult

it captures the error logs as well

aye, but it is a global setting, which I think we should use only when testing things we specifically want to print some logs out. Those error/warn logs which pop up in test runs sometimes lead to interesting findings, I'd very much like to keep them pestering us (and us fixing the issues :) )

in this specific case, the idea was to run the simple perf tests without all EthereumListeners

We're after not only terminating those services, but never starting them. Note also, that this affected how the perf test actually run, not only perf test's smoke test. We want to run a minimal artificial subset of the production services and reason about that specifically.

it might make the test maintenance difficult

What I see as a more proper alternative here is that we parametrize the production supervisor children with an option like :start_eth_services, and set it to false when running things like that. But I'm not sure whether we want to invest in that ATM.
I am guessing we're pretty safe - if we miss some service to start during perftesting, we'll know that rather immediately and explicitly.

authors: InoMurko coveralls pdobacz

repo: omisego/elixir-omg


text:
Admin Login throws "no function clause matching in Base.url_decode64/2"

Issue:
After running mix seed --sample in the ewallet Docker container (docker exec -it omisego_ewallet_1 mix seed --sample) and trying to follow the instructions to login as admin@example.com, the login is denied and the following text is output by the ewallet Docker container:
ewallet_1  | 17:38:27.435 request_id=2kmqfgt2as9jim219g0002n1 [info] GET /admin
ewallet_1  | 17:38:27.514 request_id=2kmqfgt2as9jim219g0002n1 [info] Sent 200 in 78ms
ewallet_1  | 17:38:40.124 request_id=2kmqfhkmpvce4nsp2o0002q1 [info] POST /admin/api/login
ewallet_1  | 17:38:40.237 request_id=2kmqfhkmpvce4nsp2o0002q1 [info] Sent 500 in 113ms
ewallet_1  | 17:38:40.239 [error] #PID<0.1125.0> running UrlDispatcher.Plug terminated
ewallet_1  | Server: localhost:4000 (http)
ewallet_1  | Request: POST /admin/api/login
ewallet_1  | ** (exit) an exception was raised:
ewallet_1  |     ** (FunctionClauseError) no function clause matching in Base.url_decode64/2
ewallet_1  |         (elixir) lib/base.ex:482: Base.url_decode64(nil, [padding: false])
ewallet_1  |         (salty) lib/salty/utils.ex:18: Salty.Utils.decode_key/2
ewallet_1  |         (salty) lib/salty/secret_box.ex:53: Salty.SecretBox.decrypt/1
ewallet_1  |         (cloak) lib/cloak.ex:170: anonymous fn/3 in Cloak.decrypt/1
ewallet_1  |         (elixir) lib/enum.ex:1899: Enum."-reduce/3-lists^foldl/2-0-"/3
ewallet_1  |         (cloak) lib/cloak.ex:164: Cloak.decrypt/1
ewallet_1  |         (cloak) lib/cloak/types/encrypted_map_field.ex:26: Cloak.EncryptedMapField.load/1
ewallet_1  |         (ecto) lib/ecto/type.ex:647: Ecto.Type.process_loaders/3

Compose File:
version: '2.1'
services:
  ewallet:
    image: omisego/ewallet:latest
    depends_on:
      db:
        condition: service_healthy
    environment:
    - DATABASE_URL=postgresql://postgres:password@db:5432/ewallet
    - LOCAL_LEDGER_DATABASE_URL=postgresql://postgres:password@db:5432/local_ledger
    ports:
    - 4000:4000

  db:
    image: postgres
    restart: always
    environment:
      POSTGRES_PASSWORD: password
    ports:
    - 5432:5432
    volumes:
    - ./postgres-data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 30s
      timeout: 30s
      retries: 3

Commands:
$ docker-compose up
$ docker exec omisego_ewallet_1 mix do local.rebar --force, local.hex --force, ecto.create, ecto.migrate
$ docker exec -it omisego_ewallet_1 mix seed --sample

Hi @suprtux1 if you have some time could you format your docker compose file? The indentation will affect its behavior.

A quick & dirty fix for me is to add the following env vars to the docker compose file (the keys are taken from dev config):
environment:
  - SECRET_KEY_BASE=p+A/M31eF7pNXK7q6pWKfBZbubUTF5x2NSX3pGwIOywHiOIN6PCgoZjTcAS81Vlz
  - EWALLET_SECRET_KEY=j6fy7rZP9ASvf1bmywWGRjrmh8gKANrg40yWZ-rSKpI
  - LOCAL_LEDGER_SECRET_KEY=j6fy7rZP9ASvf1bmywWGRjrmh8gKANrg40yWZ-rSKpI

Yes adding ENVs should fix it. I don't think these keys should have a default value (since they're used for encryption and for signing session cookie, etc.) so I think having a better error message (e.g. EWALLET_SECRET_KEY is missing, please generate it using foo/bar) might be a better way to fix this issue?

Yes adding ENVs should fix it. I don't think these keys should have a default value (since they're used for encryption and for signing session cookie, etc.)
Can we add this to DockerHub's readme? Currently it only mentions DATABASE_URL and LOCAL_LEDGER_DATABASE_URL.

so I think having a better error message (e.g. EWALLET_SECRET_KEY is missing, please generate it using foo/bar) might be a better way to fix this issue?

Ok! I'm adding this to my queue.

Thanks, this fixed it!
Another suggestion, do these secrets have to be environment variables?
That's insecure, being exposed in the compose file, Dockerfile, processes in the container etc...
A much better option might be to have these secrets in a volume-mounted config file that is read in at runtime and appropriate for each environment (dev vs test vs qa vs prod), and maybe a utility that makes the file for you with appropriate values the first time.

@suprtux1 Thank you for your feedback. I agree that putting secrets in ENV var as a plain text is quite insecure, and even dangerous, given that we’re dealing with something with monetary value. We’ll look into adding support for using volume-mounted configuration file for the eWallet app. :-)

Since the original issue is solved by adding more environment variables, and we have #194 for the suggestion, I'm closing this issue. Thanks both!

authors: sirn suprtux1 unnawut

repo: omisego/ewallet


text:
android can't process uint32 asset_id

our testnet with uint32  assetId: 2147485160 .
and android receive and process as  as negative int  which value "-2147482136" ;
android code or log

this because java  have no unit32 .
java convert  uint32 2147485160 to int32, and the convert overflow, and got a negative value -2147482136.
int signedIntAssetid=-2147482136

//unsignedAssetid will be  2147485160
long unsignedAssetid = signedIntAssetid & 0xffffffffL;

repo: omnilaboratory/OBAndroid


text:
GitHub

Bootstrap Example

My First Bootstrap Page
Resize this responsive page to see the effect!

Column 1
Lorem ipsum dolor sit amet, consectetur adipisicing elit...
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris...

Column 2
Lorem ipsum dolor sit amet, consectetur adipisicing elit...
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris...

Column 3
Lorem ipsum dolor sit amet, consectetur adipisicing elit...
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris...

A script on this page starts this clock:

Un script sur cette page démarré cette horloge:
15:45:54


text:
ModuleNotFoundError: No module named 'omegaconf'

after importing with !pip install omegaconf
Testing this notebook
https://colab.research.google.com/github/nicolas-chaulet/torch-points3d/blob/master/notebooks/PartSegmentationKPConv.ipynb#scrollTo=PBRS6vxSvjRo
also locally
and it gives me this error.
---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
<ipython-input-7-3a91811b7225> in <module>
----> 1 from omegaconf import OmegaConf
      2 conf = OmegaConf.create()
      3 print(OmegaConf.to_yaml(conf))
      4 {}

ModuleNotFoundError: No module named 'omegaconf'

Problem solved

repo: omry/omegaconf


text:
FI-563: Omit invalid client ID token refresh test for public clients

This branch omits the invalid client ID token refresh test for public clients because that test is only valid for confidential clients. There is no client ID based authentication for public client during a token refresh.
Submitter:

[x] This pull request describes why these changes were made
[x] Internal ticket for this PR: https://oncprojectracking.healthit.gov/support/browse/FI-563
[x] Internal ticket links to this PR
[x] Internal ticket is properly labeled (Community/Program)
[x] Internal ticket has a justification for its Community/Program label
[x] Code diff has been reviewed for extraneous/missing code
[x] Tests are included and test edge cases
[x] Tests/code quality metrics have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure
where appropriate, and accomplishes the task's purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure
where appropriate, and accomplishes the task's purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Why are we passing client_id in the refresh token grant type for non-confidential clients?  This doesn't seem right.
https://github.com/onc-healthit/inferno/blob/426e8af6aa9f3d8acd528e84638f973cfc02e400/lib/modules/smart/token_refresh_sequence.rb#L152-L156

I agree, that doesn't seem right.

authors: Jammjammjamm arscan

repo: onc-healthit/inferno


text:
Link to jq missing

Is this the good one?

It is indeed :-)

authors: nhoizey oncletom

repo: oncletom/letsencrypt-alwaysdata


text:
Markdown lint

Existing Sample Changes
Description
I cleaned up this file with MarkdownLint in my development environment:

Maximize probability that features (e.g. code highlighting) work in the target MD-reader.
Resolve some format issues (e.g. sensitivity to unintended indentation).
Automatic consistency between different README.md files.

This serves as a proposal to encourage others to clean all README.md files they touch, moving forward.
Fixes Issue#
External Dependencies
List any external dependencies created as a result of this change.
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Implement fixes for ONSAM Jiras

How Has This Been Tested?
View in VS Code viewer.
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[x] VSCode
[ ] When compiling the compliler flag "-Wall -Wformat-security -Werror=format-security" was used

Delete this line and everything below if this is not a PR for a new code sample
Delete this line and all above it if this PR is for a new code sample
Adding a New Sample(s)
Description
Please include a description of the sample
Checklist
Administrative

[x] Review sample design with the appropriate Domain Expert: @mdbtucker
[ ] If you have any new dependencies/binaries, inform the oneAPI Code Samples Project Manager: @JoeOster

Code Development

[ ] Implement coding guidelines and ensure code quality. see wiki for details
[ ] Adhere to readme template
[ ] Enforce format via clang-format config file
[ ] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[ ] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[ ] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com

Security and Legal

[ ] OSPDT Approval (see @JoeOster for assistance)
[ ] Compile using the following compiler flags and fix any warnings, the falgs are: "/Wall -Wformat-security -Werror=format-security"
[ ] Bandit Scans (Python only)
[ ] Virus scan

Review

[ ] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[ ] Review readme with Tom Lenth(@tomlenth) and/or Joe Oster(@JoeOster)
[ ] Tested using Dev Cloud when applicable

PR made to wrong upstream...

repo: oneapi-src/oneAPI-samples


text:
Drop support for k0s

I am pretty frustrated by the inconsistencies of k0sctl and do not want to be the first line of support for the issues I've encountered using it.
Today I wanted to switch over my NAS to using k0s and ran into issue after issue after issue after issue after issue using it. I ended up reverting back to k3s.
Overall k0s seems decent enough, but development is very slow and it's not in the CNCF. It seems very much like a pet project between a few Mirantis employees that are trying to give it their best effort.

This will be the last commit with k0s for now. https://github.com/onedr0p/cluster-template/commit/3e0fb233b69b78dda98867467629824e7f2d1c18


text:
Questions related to requestedAttributes

I have two questions related to the requestedAttributes (in the sp-settings)

I'm trying to figure you how the requestedAttributes (configuration on the sp-settings) works. I've included it in the sp-configuration, but they only seem to be present in the metadata and not in the generated SAMLRequest. What am I missing?

I would expect that if the requestedAttributes (the ones marked required) on the sp are validated somehow in the processing of the SAMLResponse. Meaning if an attribute that is marked required:true is missing in the attribute statement of the SAMLResponse some sort of error is going to be added to the errorlist. Is this something that is supported and I just can't figured out? If it is not supported would it be a nice improvement?

That is how SAML works, the SP defines in its metadata what attributes it requires so any IdP trusting on this SP can record it and provide such attributes on the SAMLResponse. That why the requestedAttributes attributes appear on the SP XML metadata and not in the AuthNRequest.

See AuthNRequest schema:  http://www.datypic.com/sc/saml2/e-samlp_AuthnRequest.html
Anoher Reference: StackOverflow thread: https://stackoverflow.com/questions/35873526/saml-request-attributes-in-authnrequest

That depends on how the IdP was implemented. IdP could try to satisfy your requirements and in case of not be able to provide them:
a) Cancel the authentication and return a non Status=Success SAMLResponse
b) Return the attributes available and leave the SP to validate them and raise the errors.

I believe b) is the most implemented scenario.
The SAML toolkit has no idea about the Attribute Mapping (the relation between how the IdP names the user attributes and how the SP expects such attribute names), Sometime the Mapping is done on the IdP side, others on the SP sides, so isn't
ideal to implement such validation at the toolkit level and I consider that is something that needs to be handled at the app level, where there is the info about app user accounts
At the end gonna be a matter of extract the attributes with auth.get_attributes() and then apply the Attribute Mapping changes to the array if need to be applied and later validate that the required attributes are in the array returned and contains data.

@pitbulk Thank you for your quick and informative reply.

I had been reading this technical specification from OASIS which is an extension to the standard SAML protocol I now see. This however would then probably not be widely supported and thus not worth including in the SAML toolkit.

I did not take into consideration that the mapping could happen a the idp-side, which in the case of requested attributes which specify the attribute name, would not make much sense to me. I'm relatively new to the SAML protocol and it's implementations so I'm not yet very familiar with it's implementation conventions.

Again thank you for your explanation. It is very much appreciated.

authors: MatthijsvW pitbulk


text:
Allow requirement of single files

This is to reflect the advertised behaviour in the README.
You can manually test requirements of each file in irb (exiting irb between each) with:

require_relative 'lib/onelogin/ruby-saml/authrequest'
require_relative 'lib/onelogin/ruby-saml/logoutrequest'
require_relative 'lib/onelogin/ruby-saml/logoutresponse'
require_relative 'lib/onelogin/ruby-saml/settings'
require_relative 'lib/onelogin/ruby-saml/slo_logoutrequest'
require_relative 'lib/onelogin/ruby-saml/slo_logoutresponse'

:+1:

@luisvm , @Lordnibbler what do you think?

:+1:

:+1:

:+1:

thank you @rafaelgonzalez !

Cheers everyone

The file onelogin.rb is unnecessary since we don't use any
require 'onelogin' anywhere.
I noticed that in ruby-saml-example we never used
require 'onelogin/ruby-saml'

with the gem installed, it imports the lib/ruby-saml.rb  so the library is available.
After read the REQUIRING CODE section of rubygem I saw that is common to set in the lib path a file with the name of the library, so I will replace lib/onelogin.rb by lib/ruby-saml.rb .That will maintain ruby-saml-example compatibility.
@Lordnibbler, are you agree?

authors: Lordnibbler cgthornt luisvm pitbulk rafaelgonzalez

repo: onelogin/ruby-saml


text:
Enable 3rd party release custom checks

Add logic that collects custom datadog checks from 3rd party releases.
Scripts placed in
${JOB_PATH}/config/datadog-integrations/${checkname}.py
will be copied to checks.d directory of the datadog agent. Configuration for these checks can be done using already built in 3rd party configuration merging functionality. Simply - put the config in the same directory and ensure it has .yaml suffix.
This functionality will break datadog-agent job startup if it finds two custom checks with the same name. This is so that it doesn't overwrite checks and doesn't fail silently when it's not clear which check should be used.
Example of use case: https://github.com/alphagov/paas-datadog-for-cloudfoundry-boshrelease/tree/master/jobs/datadog-bbs

spec file links to check that is in the submodule. This will include it in the bosh release and it will then be picked by the collect script

Pretty interesting, I didn't even realize this was there! Thanks for the contribution, this makes a lot of sense.
Sorry for the late reply!

authors: adamstegman mtekel

repo: onemedical/datadog-agent-boshrelease


text:
fix bug: intercept requests when current session is null ( APP_INITIA…

…LIZE )

Comment ça 🤔 !?

authors: YoussefDahi usfalami

repo: oneteme/inspect-ng-collector


text:
🛑 Identity Plus (EU) is down

In fad939f, Identity Plus (EU) (https://eu.onetimesecret.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Identity Plus (EU) is back up in 118e738 after 28 minutes.

repo: onetimesecret/status


text:
langauge server will not start on flow-cli later then  0.39.1

When starting my editor (nvim) with flow-cli versions later then 0.39.1 my editor just hangs and will not start lsp.

flow-cli version 0.39.1 and 0.39.2 does not work on vscode either.
The flow-cli dependency cannot be found on vscode.
Also inline comment and auto-complete seems to be gone as well for these flow-cli versions.

@bjartek there were a bunch of changes we introduced in the latest version of LS. So can you make sure the changes are reflected in the LS client.
@Bamthelearner Which version of vscode extension do you have? please make sure it's the latest.

@bjartek there were a bunch of changes we introduced in the latest version of LS. So can you make sure the changes are reflected in the LS client.
@Bamthelearner Which version of vscode extension do you have? please make sure it's the latest.

Thank you!
I am on v1.0.4, I think that's the latest version?

@Bamthelearner it is. Let me move this to the vscode repo as it might be related to that. @DylanTinianov might have some more questions.

authors: Bamthelearner bjartek sideninja

repo: onflow/flow-cli


text:
Added errors to accessors methods in config

Closes #349
Description

For contributor use:

[ ] Targeted PR against master branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[ ] Code follows the standards mentioned here
[ ] Updated relevant documentation
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Added appropriate labels

../../go/pkg/mod/github.com/onflow/cadence/languageserver@v0.18.2/integration/initialization.go:47:33: multiple-value state.Networks().ByName() in single-value context
I think we might need to change something in languageserver as well?

../../go/pkg/mod/github.com/onflow/cadence/languageserver@v0.18.2/integration/initialization.go:47:33: multiple-value state.Networks().ByName() in single-value context
I think we might need to change something in languageserver as well?

Yep, this line should be updated: https://github.com/onflow/cadence/blob/master/languageserver/integration/initialization.go#L47
But probably also others, so the way you can test that is to pull language server locally, link version of the CLI/flowkit to the latest commit from this PR and then update all the changes, after that push the changes as part of PR and then link the latest commit in LS PR from the CLI so it passes tests.

I already made a PR in LS, it is referecend above. https://github.com/onflow/cadence/pull/1102

authors: bjartek sideninja


text:
Cadence Tutorials - Update FT and NFT

Update the basic tutorials to include new things:

latest cadence features
explain capabilities a bit better
potentially use standard-compatible code
maybe re-order FT and NFT tutorials to start with the simplest version and build from there?

@joshuahannan Is this in-progress/completed ?

This is still in progress. Moving slowly because other things keep pulling my attention away

repo: onflow/flow


text:
Dogfooding Notes

Capturing some initial notes on the current UX:

Landing page lets you mint without logging in

After minting is finished, the button below indicates purchase, which then prompts for a login. This can be confusing because its not clear why a password was required to access the minting page (The button on the password prompt says "Log In", but doesn't actually log you into your wallet).
Suggestion: users should be prompted to log into the wallet first?

Unclear how to add funds to wallet

There is no way to access the "funding" page in the dev-wallet from the UI. User has to log out and log back in again. The funding page is also hidden behind "manage". Ultimately this is confusing.

Insufficent finds error is too small. It's not clear there is a problem. The dev-wallet closes and you're left wondering. This should be a modal, with instructions about how to add funds to the wallet?

After purchasing you're immediately prompted to list your items. This feels awkward. Should redirect user to their profile after purchase, with the purchased item highlighted in some way.

On testnet, after a user logs in using their wallet, the top banner reads "Log in to the Service Account and initialize it to get started." but this is impossible. More confusing messaging around the mock-login to the admin/minting page.

The title of the "Store" page says "Marketplace". This is confusing.

Clicking "purchase" if you're not logged in, bring up the login dialog, you log in, but have to click purchase again to complete the purchase.

adding some more notes from observations:

If minting fails, there is no error message. it seems like a glitch in the UI and could be handled better

repo: onflow/kitty-items


text:
Expose colors

Needed for the Markdown preview, Oni side is in the Markdown-preview PR.

Awesome, thanks for adding this! It's going to look awesome with the background / foreground in sync... can't wait.

authors: TalAmuyal bryphe

repo: onivim/oni-api


text:
Handle NBD partitions

[ ] Get it working
[ ] Write documentation
[ ] Be sure that ocs-scripts are compatible

Reading :

http://lwn.net/Articles/276044/

cc @aimxhaisse @edouardb

Added nbd.max_parts=8 to bootcmd
root@test:~# cat /proc/cmdline
earlyprintk=ttyS0 nousb console=ttyS0,9600n8 noplymouth ip=dhcp boot=local root=/dev/nbd0 USE_XNBD=1 nbd.max_parts=8

I think this is OK from the kernel's POV, I'm able to mount a device with several partitions with userland tools (kpartx) in it this way:
dd if=my_image_with_partitions.img of=/dev/nbd1 bs=1M
kpartx -a /dev/nbd1
mount /dev/mapper/nbd1p1 /mnt/p1
mount /dev/mapper/nbd1p2 /mnt/p2
# and so one

I haven't tested to create partitions on a /dev/nbd device yet, I guess it's fine.

Ok good news, so I check the first need "Get it working"

@aimxhaisse @edouardb, does anyone of you continued the testing ? We know the support is here, but there are some specificities that need to be documented

authors: aimxhaisse moul

repo: online-labs/kernel-config


text:
Nginx

Update nginx to 1.10.1

👍

authors: chosenken franvarney

repo: onmodulus/docker-run-python


text:
[BUG] Cannot find symbol class TileArchives

Describe the bug
The planetiler-examples do not build on latest main.
To Reproduce
Steps to reproduce the behavior:
git clone git@github.com:onthegomap/planetiler.git
cd planetiler/planetiler-examples
../mvnw clean package --file pom.xml

Expected behavior
Examples build.
Screenshots
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/wipfli/maps/test/planetiler/planetiler-examples/src/main/java/com/onthegomap/planetiler/examples/ToiletsOverlayLowLevelApi.java:[7,41] cannot find symbol
  symbol:   class TileArchives
  location: package com.onthegomap.planetiler.archive
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.029 s
[INFO] Finished at: 2023-03-18T20:14:26+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project planetiler-examples: Compilation failure
[ERROR] /home/wipfli/maps/test/planetiler/planetiler-examples/src/main/java/com/onthegomap/planetiler/examples/ToiletsOverlayLowLevelApi.java:[7,41] cannot find symbol
[ERROR]   symbol:   class TileArchives
[ERROR]   location: package com.onthegomap.planetiler.archive
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Environment (please complete the following information):

Hardware: xps dell
OS: ubuntu
Java version and distribution: 17
Maven version: 3.8.2

Additional context

@wipfli when you build directly from planetiler-examples you need to run ../mvnw clean package -f standalone.pom.xml

Ah my bad, thanks for the pointer @msbarry. With standalonge.pom.xml it compiles...

authors: msbarry wipfli

repo: onthegomap/planetiler


text:
Mapping generation fails on MySQL due to "unknown table"

Description
Mapping bootstrapping fails on different MySQL DBs
Steps to Reproduce
Run the following command: ./ontop bootstrap -p $ONTOP_JDBC_PROPERTIES -m $ONTOP_MAPPING -t $ONTOP_ONTOLOGY -b $ONTOP_BASE_IRI
Expected behavior: Mapping is generated successfully
Actual behavior: Mapping generation fails
Reproduces how often: All the time with the same specific MySQL DBs
Attached material
        at it.unibz.inf.ontop.spec.mapping.bootstrap.impl.DirectMappingEngine.bootstrapMappingAndOntology(DirectMappingEngine.java:136)
        at it.unibz.inf.ontop.spec.mapping.bootstrap.impl.DirectMappingEngine.bootstrap(DirectMappingEngine.java:97)
        at it.unibz.inf.ontop.spec.mapping.bootstrap.impl.DefaultDirectMappingBootstrapper.bootstrap(DefaultDirectMappingBootstrapper.java:16)
        at it.unibz.inf.ontop.cli.OntopBootstrap.run(OntopBootstrap.java:40)
        at it.unibz.inf.ontop.cli.Ontop.main(Ontop.java:18)
Caused by: java.sql.SQLSyntaxErrorException: Unknown table '*******' in information_schema
        at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
        at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
        at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
        at com.mysql.cj.jdbc.StatementImpl.executeQuery(StatementImpl.java:1218)
        at com.mysql.cj.jdbc.DatabaseMetaData$7.forEach(DatabaseMetaData.java:2965)
        at com.mysql.cj.jdbc.DatabaseMetaData$7.forEach(DatabaseMetaData.java:2953)
        at com.mysql.cj.jdbc.IterateBlock.doForAll(IterateBlock.java:56)
        at com.mysql.cj.jdbc.DatabaseMetaData.getPrimaryKeys(DatabaseMetaData.java:3006)
        at it.unibz.inf.ontop.dbschema.RDBMetadataExtractionTools.getPrimaryKey(RDBMetadataExtractionTools.java:557)
        at it.unibz.inf.ontop.dbschema.RDBMetadataExtractionTools.loadMetadata(RDBMetadataExtractionTools.java:274)
        at it.unibz.inf.ontop.spec.mapping.bootstrap.impl.DirectMappingEngine.bootstrapMappings(DirectMappingEngine.java:212)
        at it.unibz.inf.ontop.spec.mapping.bootstrap.impl.DirectMappingEngine.extractPPMapping(DirectMappingEngine.java:194)
        at it.unibz.inf.ontop.spec.mapping.bootstrap.impl.DirectMappingEngine.bootstrapMappingAndOntology(DirectMappingEngine.java:120)
        ... 4 more

Versions
Version 3 beta as Docker image: https://github.com/AtomGraph/ontop/tree/version3-docker/docker
Additional Information
Happens with 2 different MySQL databases, both on MySQL 5.7.23 and MySQL 5.7.19.

Hi @namedgraph ,
I quickly tested the latest v3-beta-3-SNAPSHOT, but I could not reproduces the problem on the MySQL database (5.7.23-0ubuntu0.16.04.1) that we are using for testing.
Reading your logs, it appears the problem happens when retrieving the primary keys from the databases. The error message "Unknown table '' in information_schema" suggests that it seems that the JDBC driver is not able to find the metadata of the table ''.
In order to solve your issue, we need a way to reproduce the problem. Without any data, we are not able to analyze and debug the issue. Maybe you can share a minimal dump of your schemas?

@ghxiao did it help?

It appears to be a problem of versions of JDBC drivers.
In your docker, mysql-connector-java-8.0.12.jar is used and I can reproduce the problem.
With an older version of mysql-connector-java-5.1.46.jar, I don't have such issue.
I will investigate further.

Any solution in sight? :)

We have confirmed that the problem is that MySQL-connector drivers v5.x and v8.x have different behaviors when retrieving metadata. We are working on a hotfix now.
In the meanwhile, you can just use MySQL-connector driver v5.

Hi, we have worked out a hotfix of supporting MySQL connector v8 in https://github.com/ontop/ontop/commit/f5eebb225b3a3da50745fb07c55c274a41e8cd68. Now ontop should work with both v5 and v8.
The fix has been merged to the version3 branch. Please give it a try.

authors: ghxiao namedgraph

repo: ontop/ontop


text:
🛑 Fedora Koji is down

In dd97192, Fedora Koji (https://koji.fedoraproject.org/koji/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fedora Koji is back up in 91a81e0 after 5 minutes.

repo: onuralpszr/uptime


text:
reformat, remove notice and add hook

Auto-reformat code
remove unnecessary line with PHP notice
hook_google_oauth_create_user_alter() added

/approved 🎉

Guess Im not allowed to approve it :/ sorry about that

This looks great, thanks for your cleanup @nevergone! This was my very first D8 module and I wrote it during a session "Building your first Drupal 8 module" – I'm happy to see it getting a little traction!
I will add unit tests in the future, too, but this PR really gives it a little polish. Thanks again!

authors: bendoh brettsaguid nevergone


text:
Reach feature completeness for OONI Run service

What's still missing:

[x] Pattern for runnning db migrations
[x] Monitoring via prometheus exporter
[x] Health check API

Having landed both #820 and #819, this is done.

repo: ooni/backend


text:
Update the confirmed and anomaly columns as part of centrifugation

As discussed in: https://github.com/ooni/api/issues/59#issuecomment-475587287
It seems like the confirmed and anomaly tables are not currently being updated.
I think that for the sake of coming up with an MVP that implements the heuristics present in the current explorer we define:
confirmed we saw a blockpage of the country of the measurement for web_connectivity measurements (we don't mark as confirmed any other measurement types for the moment)
anomaly in the case of web_connectivity the value of blocking != 'false' AND blocking != NULL OR it's confirmed
@darkk how would you suggest we handle updating the values of these columns as part of the centrifugation stage?
My proposal is to do the following:

[ ] Re-run as a one-off a query similar to that we do for the ooexpl_website_msmts MAT VIEW (see: https://github.com/ooni/pipeline/pull/144/files#diff-15300963e74e04b5836ccfc9f0b1f6abR52)
[ ] Add to the centrifugation stage logic to update this columns once a certain bucket is being ingested, reingested or reprocessed

Does this seem reasonable to you?

I believe that's done by 5fac5cf96b4c7416f5ab2c4b41f709d3bca0a9b6 at #144, so I'm closing the ticket.

authors: darkk hellais

repo: ooni/pipeline


text:
Package "atlantis/router/backend" fails

Package atlantis/router/backend fails with message following messages:
vagrant@atlantis-aquarium-vm:~/repos/atlantis-router$ export TEST_PACKAGE=atlantis/router/backend && export VERBOSE=-v && make test
Testing atlantis/router/backend...
=== RUN TestNewServerStatus
--- PASS: TestNewServerStatus (0.00 seconds)
=== RUN TestSet
--- PASS: TestSet (0.00 seconds)
=== RUN TestStatusWeight
--- PASS: TestStatusWeight (0.00 seconds)
=== RUN TestIsValidStatus
--- PASS: TestIsValidStatus (0.00 seconds)
=== RUN TestParseAndSet
--- PASS: TestParseAndSet (0.02 seconds)
=== RUN TestCostMasking
--- PASS: TestCostMasking (0.00 seconds)
=== RUN TestSlowStartFactor
--- PASS: TestSlowStartFactor (1.00 seconds)
=== RUN TestSlowStartShape
--- FAIL: TestSlowStartShape (60.17 seconds)
	status_test.go:160: Tdelta, SlowStartFactor
	status_test.go:165:  0, 4027
	status_test.go:165:  1, 1979
	status_test.go:165:  2, 1297
	status_test.go:165:  3, 955
	status_test.go:165:  4, 750
	status_test.go:165:  5, 614
	status_test.go:165:  6, 516
	status_test.go:165:  7, 443
	status_test.go:165:  8, 386
	status_test.go:165:  9, 341
	status_test.go:165: 10, 304
	status_test.go:165: 11, 273
	status_test.go:165: 12, 246
	status_test.go:165: 13, 224
	status_test.go:165: 14, 204
	status_test.go:165: 15, 187
	status_test.go:165: 16, 172
	status_test.go:165: 17, 159
	status_test.go:165: 18, 147
	status_test.go:165: 19, 136
	status_test.go:165: 20, 126
	status_test.go:165: 21, 117
	status_test.go:165: 22, 109
	status_test.go:165: 23, 102
	status_test.go:165: 24, 95
	status_test.go:165: 25, 89
	status_test.go:165: 26, 83
	status_test.go:165: 27, 78
	status_test.go:165: 28, 72
	status_test.go:165: 29, 68
	status_test.go:165: 30, 63
	status_test.go:165: 31, 59
	status_test.go:165: 32, 55
	status_test.go:165: 33, 52
	status_test.go:165: 34, 48
	status_test.go:165: 35, 45
	status_test.go:165: 36, 42
	status_test.go:165: 37, 39
	status_test.go:165: 38, 36
	status_test.go:165: 39, 34
	status_test.go:165: 40, 31
	status_test.go:165: 41, 29
	status_test.go:165: 42, 26
	status_test.go:165: 43, 24
	status_test.go:165: 44, 22
	status_test.go:165: 45, 20
	status_test.go:165: 46, 18
	status_test.go:165: 47, 17
	status_test.go:165: 48, 15
	status_test.go:165: 49, 13
	status_test.go:165: 50, 12
	status_test.go:165: 51, 10
	status_test.go:165: 52, 9
	status_test.go:165: 53, 7
	status_test.go:165: 54, 6
	status_test.go:165: 55, 4
	status_test.go:165: 56, 3
	status_test.go:165: 57, 2
	status_test.go:165: 58, 1
	status_test.go:165: 59, 0
	status_test.go:167: should decrease monotonically to 0
FAIL
exit status 1
FAIL	atlantis/router/backend	61.208s
make: *** [test] Error 1

It appears to be an artifact of floating point arithmetic.
If i understand correctly slow start factor must be equal to 4028 at 1'st second. At the end of 60 seconds  it should become 1. At 61'st second it should become 0.
But its starting at 4027 and becoming 0 at 60'th second. Hence the error.
We can either modify  the SlowStartFactor method to index the difference of time to exact value instead of calculating at each step. Or we can refactor the unit test. I prefer the later.

Fixed and PR here https://github.com/ooyala/atlantis-router/pull/25

authors: blackgold budhrg

repo: ooyala/atlantis-router


text:
Adjust MCDA functions to be more generic

Currently adjustments to the MCDA (and related) functions require manual adjustments where criteria and their weights are added/removed.
Manually adjusting number of arguments and their index positions can lead to hard-to-debug issues due to the risk of human error, and a more than necessary time-sink as changes are required across a number of files (and those changes to be validated/tested).
We should instead move towards a more generic implementation of the MCDA functions.
One way would be to use ~NamedArrays~ NamedDims+AxisKeys to avoid the need for numeric indices, auto-generate the mapping between the column positions and the criteria they represent, and/or making the functions accept an arbitrary number of criteria/weights.
If it is necessary to continually add criteria as explicit arguments, the function could be made to accept an arbitrary number of arguments:
Notes:

https://docs.julialang.org/en/v1/manual/functions/#Varargs-Functions
https://github.com/mcabbott/AxisKeys.jl

Is this a separate issue from #252 ?

Wow, yes, it does seem like #252 is a duplicate. I did do a quick search before I opened it but obviously I'm blind (or used the wrong keywords).
Let's close this one in favour of that #252 then.

authors: ConnectedSystems Rosejoycrocker


text:
Add status column & ability to "remove" a claim from the my claimed facilities table

Overview
#573 adds a table listing all of a user's approved claimed facilities. For this card, add two features that were shown in the wireframes:

(small) add a column showing the OAR ID
(larger) add the ability to "remove" a claim from my claimed facilities

For the latter, check the wireframes for how it should look & work. I think the simplest thing might be to just have that feature delete the facility claim altogether, as there are no other columns that depend on it. Note that the FacilityClaim is checked into using django-simple-history, and the historical model may now may include some PII.
Describe the solution you'd like
add two features that were shown in the wireframes:

(small) add a column showing the OAR ID
(larger) add the ability to "remove" a claim from my claimed facilities

For the latter, check the wireframes for how it should look & work. I think the simplest thing might be to just have that feature delete the facility claim altogether, as there are no other columns that depend on it. Note that the FacilityClaim is checked into using django-simple-history, and the historical model may now may include some PII which we'll need to figure out how to handle.

#573 Already includes an OAR ID column so we should be able to drop that from the requirements for this issue.

authors: jwalgran kellyi


text:
Add version to help.

Since a user may need to know the version, we should have it readily available in the help message. I didn't think to add this as part of #33
(dev) [bnelson@dlw05 open-ce-builder]$ open-ce -h
usage: open-ce [-h] {build,test,validate,get} ...

Open-CE Builder 3.0.0

optional arguments:
  -h, --help            show this help message and exit

Open-CE Commands:
  Choose from the following commands to perform.

  {build,test,validate,get}
    build               Build a feedstock, an image, or an environment.
    test                Run tests within a feedstock.
    validate            Validate an env file or a conda_build_config file.
    get                 Get information about Open-CE builds.

Codecov Report

Merging #34 (46693ff) into main (a3a3ed3) will decrease coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
- Coverage   95.45%   95.40%   -0.05%
==========================================
  Files          21       21
  Lines        1825     1826       +1
==========================================
  Hits         1742     1742
- Misses         83       84       +1

Flag
Coverage Δ

unittests
95.40% <100.00%> (-0.05%)
:arrow_down:

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

Impacted Files
Coverage Δ

open_ce/open-ce
87.69% <100.00%> (+0.19%)
:arrow_up:

open_ce/validate_config.py
96.88% <0.00%> (-3.12%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #34 (46693ff) into main (a3a3ed3) will decrease coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
- Coverage   95.45%   95.40%   -0.05%
==========================================
  Files          21       21
  Lines        1825     1826       +1
==========================================
  Hits         1742     1742
- Misses         83       84       +1

Flag
Coverage Δ

unittests
95.40% <100.00%> (-0.05%)
:arrow_down:

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

Impacted Files
Coverage Δ

open_ce/open-ce
87.69% <100.00%> (+0.19%)
:arrow_up:

open_ce/validate_config.py
96.88% <0.00%> (-3.12%)
:arrow_down:

Continue to review full report at Codecov.

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

It probably makes sense to add a --version argument as well that will print out the version number.

Looks good, but I agree that a --version option would also be good.

authors: bethune-bryant bnemanich codecov-commenter jayfurmanek

repo: open-ce/open-ce-builder


text:
do not set ownerref if resource is deployed into different namespace

Signed-off-by: Roke Jung roke@redhat.com
When resources are deployed into different namespaces by subscription-admin, do not set owner reference to the subscription. k8s garbage collection will delete the resources because it cannot find the owner in the same namespace.

/lgtm

authors: rokej xiangjingli


text:
set common env and reduce the kube context switch.

This PR tries to enhance the document:

set some common environment variables at the beginning of the whole guideline.
try to reduce the kube context switch, for example, clusteradm support --context flag, so we can use that to quickly refer to the expected kube context.
reduce duplicated environment variable definition, for example, MANAGED_CLUSTER_NAME can be exported after the cluster is created by the kind command and then it will be reused throughout the guideline.
fix typo.

Signed-off-by: morvencao lcao@redhat.com

Thank you for the PR. I will need to at least run it once myself to verify the steps.

@mikeshng Another look? I rebased code changes.

@morvencao sorry for the delay. I will get to this today.

/approve
will lgtm in today if I don't hear some feedback from Dominique or Qiu Jian

I am ok with all the changes but have some concerns for the quick-start ones.
@qiujian16 @itdove could you please share your thoughts? Should we update clusteradm outputs with the --context flag before making the suggested change here?

--context could be a global flag similar as kubectl so you could have clusteradm options to know all the global flags.

/lgtm
After verifying that clusteradm join --context ${CTX_MANAGED_CLUSTER} --hub-token ... works fine.

authors: mikeshng morvencao qiujian16


text:
backend bearer token support

Signed-off-by: James Talton jtalton@redhat.com

/lgtm

authors: KevinFCormier jamestalton

repo: open-cluster-management/console


text:
add owners

Signed-off-by: Zhiwei Yin zyin@redhat.com

/assign @itdove

/lgtm


text:
[release-2.4] Fix health-probe-bind-address arg

Signed-off-by: Yu Cao ycao@redhat.com

/assign @hanqiuzh

/approve
/lgtm


text:
reduce the hub controller permissions

Signed-off-by: liuwei liuweixa@redhat.com

/assign @qiujian16


text:
Barebones /sources curator UI page

Breaking this story up to keep PR length sane. For now, just adding a minimal /sources page and SourceTable component; largely analogous to a simplified LinelistTable. The existing Source model isn't exactly what Tim and I landed on, but I'll address that after the bulk of the interface boilerplate is taken care of. Still adding the types to the component file to be "correct," though we could technically get away with just defining _id/name.

 Create barebones source config UI backed by sources API/MongoDB

repo: open-covid-data/healthmap-gdo-temp


text:
Setup Github Actions for CI

Create a CI/CD pipeline for the repo

Build
Test
Code Coverage
Setup styling compliance via dotnet-format
Publishing package to nuget

For the time being, we can use openfeature-core@groups.io for publishing packages.

@benjiro, I'll take care of it. Unfortunately, the group email isn't working how I expected so I can't confirm the org. It may take a bit to figure out. FYI, @toddbaert.

@benjiro, I've contacted the NuGet support team because I'm not receiving the verification email. Hopefully we can get this addressed ASAP.

The NuGet support team still hasn't responded. I've contacted the CNCF to see if they offer an email service. If I don't hear something soon, I can setup a gmail account with an alias.

Got it working! @benjiro, do you have a NuGet account? I can add you as a collaborator.

@beeme1mr yea my nuget id is benjiro

Thanks for your work with the nuget red-tape @beeme1mr

Still nothing from the NuGet team. I'll send them another email.

The prefix OpenFeature.* has been reserved.

authors: beeme1mr benjiro toddbaert

repo: open-feature/dotnet-sdk


text:
Organize - Open-Insurance Day - 03

Current proposal
location: Vienna
date: 25.05.2020  26.05.2020
host:

TelKo on 21.02.2020
with @MarRothm, Udo Urbantschitsch and @MarkusTiede
Talk proposal by Baloise: "Open-Source (Software) in der Versicherung(swelt), Markus Tiede

Udos proposal RedHat would promote the event within all customer interaction events until then.
Idea: one could also use RedHat Forum Austria for this (e.g. during 2020)
@MarRothm : on 25. - 26.05 ABS Summit is happening. APOSIN would like to join on neutral ground.
1/2 day - for the 3rd Open-Insurance Day in Austria: after lunch until early evening
Open lightweight "Call for Paper" for OID 3.

Follow-up call sent for March 9, 2020 at 15:30
Mentioning Aposin and Allianz as supporter on social media appreciated
my presentation alt1: Contributing A Core Insurance Solution - Insights In Allianz' Open Source Initiative
my presentation alt 2: From OSS Usage To Contribution -  Insights In Allianz' Open Source Initiative

First draft of information available so far published under
https://open-insurance.org/events/2020/open-insurance-day-02.html

authors: MarRothm MarkusTiede

repo: open-insurance/events


text:
Fixed 'CONTRIBUTING.md'

Twitter* -> Open*

Coverage remained the same at 97.292% when pulling 40d842181dc99a15a7857f21d607e330c04c7055 on improve_coverage_mechanickim into f87b280bcd2a399c6baab1e8044d822e4997bcbb on master.

authors: MechanicKim coveralls

repo: open-korean-text/open-korean-text


text:
Kafka Error

Error while testing connection with Kafka
Error example:
test-connection-Kafka-my798FgW Failed to trigger workflow due to airflow API returned Internal Server Error and response {"error": "Error running automation workflow due to [KafkaError{code=_INVALID_ARG,val=-186,str="Failed to create admin client: No provider for SASL mechanism GSSAPI: recompile librdkafka with libsasl2 or openssl support. Current build options: PLAIN SASL_SCRAM OAUTHBEARER"}]] "}
Configuration example:

Scrin error:

Version:

OpenMetadata version: 1.3.3

related to https://github.com/confluentinc/confluent-kafka-dotnet/issues/567

repo: open-metadata/OpenMetadata


text:
Enhance Dashboard Entity

Context
We have been getting different inputs from the community about adding more properties and enhancing the Service hierarchy. A few examples are:

https://github.com/open-metadata/OpenMetadata/issues/5406
https://github.com/open-metadata/OpenMetadata/issues/3416
https://github.com/open-metadata/OpenMetadata/issues/3412

The goal of this EPIC is to scope and track what additions can be done that are consistent among the different services
Tasks
TBD

@pmbrull closing this

authors: harshach pmbrull


text:
Allow consumers of Openmetadata-ingestion to define custom connectors in their own package with same namespace

Is your feature request related to a problem? Please describe.
As a consumer of Openmetadata-ingestion package,  I want to add my custom connectors within the same namespace but in a different package repository.
Consider a situation below:
├─my_code_repository_package
  ├── src
      ├── my_other_relevant_code_package
      ├── metadata
      │   └── ingestion
      │       └── source
      │        └── database
      │         └── my_awesome_connector.py
      └── setup.py
├── openmetadata_ingestion
  ├── src
      ├── metadata
      │   └── ingestion
      │       └── source
      │        └── database
      │         └── existingSource1
      |         └── existingSource2
      |         └── ....
      └── setup.py

I want my_awesome_connector.py to build as a source and run as a part of workflows defined in openmetadata_ingestion
Describe the solution you'd like
Clear set of steps to achieve this and also how to index the same on IDE
Describe alternatives you've considered
NA
Additional context
NA

Thanks for the details @abcabhishek.
This will be a growing need for the community, so we'll test it out and land it in the docs

authors: abcabhishek pmbrull


text:
Remove boilerplate code for listAfter and listBefore methods in DashboardRepository

See change in pull request fcf71a1d810b3b32dfcfb10fed6bbc28069456da for details

I can take this up. Can someone please assign it to me?

authors: sureshms vivekratnavel


text:
[Enhance] Add get_cat_ids and get_gt_labels to KFoldDataset

Motivation
KFoldDataset isn't implemented get_cat_ids and get_gt_labels.
Not implemented get_cat_ids, KFoldDataset can't use with ClassBalancedDataset for example.
Not implemented get_gt_labels, can't calculate confusion matrix like #598.
Modification
Simply implemented these methods to KFoldDataset.
Checklist
Before PR:

[x] Pre-commit or other linting tools are used to fix the potential lint issues.
[x] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[x] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[x] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects, like MMDet or MMSeg.
[ ] CLA has been signed and all committers have signed the CLA in this PR.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Yuichi Ito seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Sorry, I made a mistake in the email address when doing git commit.
Once this pull request is closed.

repo: open-mmlab/mmclassification


text:
config file for HTC HRNetV2p-W48 28e

Please provide the config file for HTC hrnet W48 28e

Created by me. Thanks

repo: open-mmlab/mmdetection


text:
Tried to train HTC model in 1 GPU, ERROR arise

Dear community I have tried train HTC model by 1 GPU 16 gb.
/mmdetection/mmdet/ops/roi_align/roi_align.py", line 30, in forward aligned)
RuntimeError: CUDA error: invalid device function
Segmentation fault (core dumped)
What is the changes in config file I should do for it work?

Please follow the Error report issue template.

authors: Korolyow hellock


text:
Invalid link in readme of cityscape

Hi, Thank you very much for the amazing project!
I would like to report that the model in the readme in the cityscape is invalid.
Meanwhile, may I ask whether there are more pre-trained models on Cityscape? I would like to evaluate the models elaborately.
Thank you!

Hi @luzai, thanks for your comments, and we will fix it soon.

authors: luzai v-qjqs


text:
use mobilenet backbones ,train 60 epoch ,get 3% accuracy

When i attempt to change the resnet backbone to mobilenet .However,the accuracy is pretty low.What might be the reason to get this 3% low accuracy,since the resnet backbone is over 90%.

You may provide the config file and command you used.

config:faster_rcnn_r50_fpn_1x.py
model = dict(
3     type='FasterRCNN',
4    # pretrained='modelzoo://resnet18',
5     pretrained=None,
6   #  backbone=dict(
7      #   type='ResNet',
8         #block=BasicBlock,
9         #layers=[2,2,2,2],
10         #sample_size=64),
11         #sample_duration=2),
12     #    depth=18,
13    #     num_stages=4,
14   #      out_indices=(0, 1, 2, 3),
15        # frozen_stages=1,
16       #  norm_eval=False,
17      #   style='pytorch'),
18     backbone=dict(
19         type='MobileNet',
20         width_multiplier=1,
21         class_num=1),
22     neck=dict(
23         type='FPN',
24         in_channels=[128, 256, 512,1024],
25         out_channels=64,
26         num_outs=5),
Nothing else changed .
Backbone: mobileNet
1          import torch
2 import torch.nn as nn
3 import logging
4 import torch.utils.checkpoint as cp
5
6 from mmcv.cnn import constant_init, kaiming_init
7 from mmcv.runner import load_checkpoint
8 from ..registry import BACKBONES
9
10 class DepthSeperabelConv2d(nn.Module):
11
12     def init(self, input_channels, output_channels, kernel_size, **kwargs):
13         super().init()
14         self.depthwise = nn.Sequential(
15             nn.Conv2d(
16                 input_channels,
17                 input_channels,
18                 kernel_size,
19                 groups=input_channels,
20                 **kwargs),
21             nn.BatchNorm2d(input_channels),
22             nn.ReLU(inplace=True)
23         )
24
25         self.pointwise = nn.Sequential(
26             nn.Conv2d(input_channels, output_channels, 1),
27             nn.BatchNorm2d(output_channels),
28             nn.ReLU(inplace=True)
29         )
30
31     def forward(self, x):
32         x = self.depthwise(x)
33         x = self.pointwise(x)
34
35         return x
36
37
38 class BasicConv2d(nn.Module):
39
40     def init(self, input_channels, output_channels, kernel_size, **kwargs):
41
42         super().init()
43         self.conv = nn.Conv2d(
44             input_channels, output_channels, kernel_size, **kwargs)
45         self.bn = nn.BatchNorm2d(output_channels)
46         self.relu = nn.ReLU(inplace=True)
47
48     def forward(self, x):
49         x = self.conv(x)
50         x = self.bn(x)
51         x = self.relu(x)
52
53         return x
54
55 @BACKBONES.register_module
56 class MobileNet(nn.Module):
57
58     """
59     Args:
60         width multipler: The role of the width multiplier α is to thin
61                          a network uniformly at each layer. For a given
62                          layer and width multiplier α, the number of
63                          input channels M becomes αM and the number of
64                          output channels N becomes αN.
65     """
66
67     def init(self, width_multiplier=1, class_num=1):
68        super().init()
69
70        alpha = width_multiplier
71        self.stem = nn.Sequential(
72            BasicConv2d(3, int(32 * alpha), 3, padding=1, bias=False),
73            DepthSeperabelConv2d(
74                int(32 * alpha),
75                int(64 * alpha),
76                3,
77                padding=1,
78                bias=False
79            )
80        )
81
82        #downsample
83        self.conv1 = nn.Sequential(
84            DepthSeperabelConv2d(
85                int(64 * alpha),
86                int(128 * alpha),
87                3,
88                stride=2,
89                padding=1,
90                bias=False
91            ),
92            DepthSeperabelConv2d(
93                int(128 * alpha),
94                int(128 * alpha),
95                3,
96                padding=1,
97                bias=False
98            )
99        )
100
101        #downsample
102        self.conv2 = nn.Sequential(
103            DepthSeperabelConv2d(
104                int(128 * alpha),
105                int(256 * alpha),
106                3,
107                stride=2,
108                padding=1,
109                bias=False
110            ),
111            DepthSeperabelConv2d(
112                int(256 * alpha),
113                int(256 * alpha),
114                3,
115                padding=1,
116                bias=False
117            )
118        )
119
120        #downsample
121        self.conv3 = nn.Sequential(
122            DepthSeperabelConv2d(
123                int(256 * alpha),
124                int(512 * alpha),
125                3,
126                stride=2,
127                padding=1,
128                bias=False
129            ),
130
131            DepthSeperabelConv2d(
132                int(512 * alpha),
133                int(512 * alpha),
134                3,
135                padding=1,
136                bias=False
137            ),
138            DepthSeperabelConv2d(
139                int(512 * alpha),
140                int(512 * alpha),
141                3,
142                padding=1,
143                bias=False
144            ),
145            DepthSeperabelConv2d(
146                int(512 * alpha),
147                int(512 * alpha),
148                3,
149                padding=1,
150                bias=False
151            ),
152            DepthSeperabelConv2d(
153                int(512 * alpha),
154                int(512 * alpha),
155                3,
156                padding=1,
157                bias=False
158            ),
159            DepthSeperabelConv2d(
160                int(512 * alpha),
161                int(512 * alpha),
162                3,
163                padding=1,
164                bias=False
165            )
166        )
167
168        #downsample
169        self.conv4 = nn.Sequential(
170            DepthSeperabelConv2d(
171                int(512 * alpha),
172                int(1024 * alpha),
173                3,
174                stride=2,
175                padding=1,
176                bias=False
177            ),
178            DepthSeperabelConv2d(
179                int(1024 * alpha),
180                int(1024 * alpha),
181                3,
182                padding=1,
183                bias=False
184            )
185        )
186
187       # self.fc = nn.Linear(int(1024 * alpha), class_num)
188       # self.avg = nn.AdaptiveAvgPool2d(7)
189
190     def init_weights(self, pretrained=None):
191         if isinstance(pretrained, str):
192             logger = logging.getLogger()
193             load_checkpoint(self, pretrained, strict=False, logger=logger)
194         elif pretrained is None:
195             for m in self.modules():
196                 if isinstance(m, nn.Conv2d):
197                     kaiming_init(m)
198                 elif isinstance(m, (nn.BatchNorm2d, nn.GroupNorm)):
199                     constant_init(m, 1)
200
201     def forward(self, x):
202         outs=[]
203         x = self.stem(x)
204         x=self.conv1(x)
205         outs.append(x)
206         x = self.conv2(x)
207         outs.append(x)
208         x = self.conv3(x)
209         outs.append(x)
210         x = self.conv4(x)
211
212        # x = self.avg(x)
213         outs.append(x)
214        # x = x.view(x.size(0), -1)
215         #x = self.fc(x)
216         return tuple(outs)
217     def train(self, mode=True):
218         super(MobileNet, self).train(mode)
219         if mode:
220             for m in self.modules():
221                 # trick: eval have effect on BatchNorm only
222                 if isinstance(m, nn.BatchNorm2d):
223                     m.train()
command :                  CUDA_VISIBLE_DEVICES=0,1,2,3,4,5 python tools/train.py configs/faster_rcnn_r50_fpn_1x.py --gpus 5 --validate
task:        Recognise and locate the  license plate number
Thanks

The result is expected since pretrained=None.

loading annotations into memory...
Done (t=0.03s)
creating index...
index created!
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] 2000/2000, 152.4 task/s, elapsed: 13s, ETA:     0s
writing results to result.pkl
Starting evaluate bbox
Loading and preparing results...
DONE (t=0.16s)
creating index...
index created!
Running per image evaluation...
Evaluate annotation type bbox
DONE (t=1.40s).
Accumulating evaluation results...
DONE (t=0.35s).
Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.011
Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.038
Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.001
Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = -1.000
Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.015
Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.002
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.021
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.090
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.096
Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = -1.000
Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.106
Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.056
Thanks

I mean your result is as expected, since you randomly initialized backbone weights.

how to improve the accuracy

However,things turn out to be different on resnet backbone.when i use the resnet backbone,and turn off the BN,set the pretrained=None, the accuracy is still over 90% on the same dataset.A slightly down compares to set pretrained=True.

@jerrynije
Hi, When i attempt to change the resnet backbone to mobilenet as you said , I got the error :
" TypeError: init() got an unexpected keyword argument 'width_multiplier' " , in "mmdet/utils/registry.py"
could you tell me how to fix it , please ?

Hi, @jerrynije !
Your MobileNet version is v1/v2, please?

authors: catchy666 hellock jerrynije xscjun


text:
Error: 'eval_res' is empty

The training proceed normally but fail to evaluate.
I think the eval path is correct but I don't what the problem is.
Here is the screenshot. Thank you !

This should have been fixed, please tell me your mmcv and mmdet versions.

We may got the same problem

Resolved by https://github.com/open-mmlab/mmdetection/pull/7101

authors: LuooChen hhaAndroid terrancraft


text:
Custom dataset wrapper

Hi, I'm making a custom dataset wrapper that works similar to MultiImageMixDataset but mixing across datasets. After some digging, it seems like the few default dataset wrappers are all "hard-coded" in mmdet.datasets.builder.build_dataset. Is the recommended way to include my custom dataset wrapper to write my own build_dataset? Thank you!

Maybe you can rewrite build_dataset, at least the basic dataset api as same as  CocoDataset

alright, thank you