Celo dApp Council Exploration

Closing this epic because the dApp council idea is now part of the monthly Celo "Wallet and (d)App Council"

Closing this epic because the dApp council idea is now part of the monthly Celo "Wallet and (d)App Council"


[TASK] Use proper gas limit for each network

Is your feature request related to a problem? Please describe.
Different networks have different gas limits. We should avoid hardcoding it always to the same value.
Describe the solution you'd like
We should have a map from chains to their hardcoded gas limits.
Describe alternatives you've considered
Really just need hardcoded value for each chain rather than 1 hardcoded value for all chains.

Move this issue to https://github.com/webb-tools/protocol-solidity/issues/241


Provide size of downloadable models

Please show file size of models available to download.

Where possible, I think the models should have their hardware requirements, author, description, purpose, and so forth described.

In the last release I added the size of the models available to download: https://github.com/juliooa/secondbrain/releases/tag/v0.2.1
In a next release I will make it easier to add model info before download them.


Why not publish sources ?

I perhaps miss something, but I can't see any sources but only the dist folder.
Is it normal ?

The source is both public on NPM and github.
https://github.com/FranzSkuffka/vue-medium-editor/blob/master/index.js

There's even published too much - actually only index, readme, package.json and dist should be on npm.

I agree, but I was speaking about github, not NPM...
To be more clear :

How to have a look at the source of your code?
How to propose you some code correction?

About NPM, we also have some repos on Github. We prepare then separately for NPM.

Holly s... I didn't have a look at index.js...was expecting the '"src" folder.
My apologies...


Update gettingstarted.rst

You want "bootstrap.sh" not "build.sh" - or if you're going to go with build.sh just remove the configure line from the documentation. ;)

(Fixed)


Rename invalid Loggers to be consistent with the project standard (LOG)

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[X] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @tgroh since some of those come from of he Harness work.

Coverage decreased (-0.007%) to 69.166% when pulling a75aee81287a230bac2e45262c56a363e720951e on iemejia:fix-logger-name into 038ebd3bf523b916734cebed5b6e9c8790ba4f04 on apache:master.

LGTM


Turn off image preloading for Autopilot

What type of PR is this?
/kind bug

What this PR does / why we need it:
Autopilot does not support image preloading.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/assign @jprzychodzen

Could you add a follow up GitHub issue to fix this?

/lgtm


ACL Policies: lack of AND logic when assigning groups

Currently when i add multiple groups it means devices only need to match one of the group. I can't create a policy where devices need to match both groups. It is a weird behavior because you can simply add multiple policies when you need to use an OR logic in those group selections and achieving AND logic is much more difficult.
Port ranges seems not supported yet, i saw related issues.

Indeed port range would be useful especially for UDP.

Why not create one more group and add devices that fits condition?


The Alexis Clue - 1st Episode

1Password with Frances Coronel

✅ By submitting this issue, I have verified the following

[x] Checked to see if the issue has already been discussed before 🤔
[x] If proposing new content to be added, enough details were provided 🔍

Potential Panelists

Ruth Wu
Mina Markham

Rebrand to one person - me! :-) and make room for guest speakers instead :P


Support Dropdown

Need a dropdown created to include the following:

Ask a Question - Opens a form with a Question field and Send button. @joseegm @saadmhybris @xak Can this form be integrated back to Github where it could auto create an issue in a project created specifically for this?
Submit an Issue - this link will open a Github issue - @joseegm - can you provide details on how you would like to manage this? Should this be a form link Ask a question above?

The Github API does not allow issue creation without authentication. We can provide a link to https://github.com/SAP/techne/issues/new and an email address.

We'll got with the link to the issues page for now.

this will be developed under #1255


Room&Contact.find() should throw exception when it get more than one value

When I have two contacts with the same name, using function find()  will return one of the contacts randomly, which is not easy to debug.
We should throw an exception when function find() return more than one value.

Agree. PR is welcome.

Instead of throw, I'm now considering to use a log.warn() instead.
Because sometimes be able to just using the first find result will be very convienence.

It's a good idea, I will change then.

We can set the level to warn or info. which one do you think is better?

I think warn is better, because it can cause more attention.


Add patches for 2.3.7-p3 & 2.3.7-p4

Thank you for your contribution! I'm currently also working on backporting fixes in magento/module-customer


Training time?

Hi, I see from section D.3 in the appendix that your provide details on the hardware and setup for training. Could you comment on how long in real time training took with this setup?
Thanks!

Hi @yunfanjiang -- any comment on this? Rough estimates are completely fine. Thanks!

Hey @thesofakillers, for almost all experiments we ran for 2M to 4M environment steps, which took roughly 1 day and 2 days on our machines.

Thanks!


Better component desc and naming

Inspired by discussion #1393
I'd like to make component descriptions and naming more customizable

coverage: 100.0%. remained the same
when pulling 1aca907a99e203ad745593c35c3ba66d193061e7 on better-component-desc-and-naming
into 01f737359c27310baad6aec99cee37b7da2cf0ee on prepare-v16.


Support for 8bit PIC MCUs

Port picoRTOS to 8bit PIC to see if it fits.
It's more of a challenge than anything else, but who knows ?

Ok for tinyAVRs, impossible on PICs (no decent stack management)

Ok for tinyAVRs, impossible on PICs (no decent stack management)


[Suggestion] Fail immediately if no hooks file found and hotreload is false

Current  behavior in verbose mode:
λ webhook.exe -verbose
[webhook] 2015/07/22 22:01:25 version 2.3.4 starting
[webhook] 2015/07/22 22:01:25 attempting to load hooks from hooks.json
[webhook] 2015/07/22 22:01:25 couldn't load hooks from file! open hooks.json: The system cannot find the file specified.
[webhook] 2015/07/22 22:01:25 starting insecure (http) webhook on :9000

Without the -verbose flag the program silently fails to find the hooks.json file (expectedly), but doesn't tell the user that. I think it would be helpful to fail immediately if no hooks file is found (and assuming -hotreload is false). What are your thoughts?

I was thinking of having verbose output set to on by default, and have a separate switch for silent mode for those that do not want the output.

:+1:

Decided to use your approach. The webhook 2.3.5 will now fail under those conditions, unless you provide a -nopanic flag to it.


[ui bug] header not visible when player active

Looks like some recent CSS changes have made the header invisible when the player is active. Also means user is stuck in player mode and has to quit to get back to index.

PR incoming.

FYI, hitting ESC also works :)


Google Login claims invalid password in Linux Mint

💻 Environment
Platform: Linux
OS Version: Linux Mint Tessa (19.1)
Toggl Version: toggldesktop_7.4.459_amd64.deb
🐞 Actual behavior
When logging in with a Google account, the app claims the email or password is wrong.
📦 Additional info
There's probably a window with more information for a split second.
https://app.intercom.io/a/apps/ayixs927/conversations/22667832385

linking again so intercom will track this

Unable to reproduce the login issue. Maybe user has to re-enable the Google login from webapp.

This seems like a problem that is resolved by clearing the cache and cookies in the embedded browser we have inside our Linux app. I had an issue with the dialog showing for a split second too and it has disappeared after that fix. I'm adding this issue to the Google Login PR that contains the commit in question.

I'm convinced this issue is now fixed. I have tested the app on Linux Mint Tessa with Cinnamon and it works as expected.


Only last custom template renders without props in cell

Issue Type (delete the irrelevant ones)

[x] Bug

Specs
2.20.0
What browser?
Chrome 84.0.4147.105 (Official Build) (64-bit)
Expected Behavior
All custom templates should prevent rendering of field cell values unless explicitly interpolated
Actual Behavior
Only the last v-if before the v-else in a custom template renders without field props in the relevant cell, while if you have two custom templates in a row, the first one will display prop text values even when you only want to show a button.
Since we can explicitly interpolate values on our own, I think any custom template v-ifs should prevent rendering of values, regardless of the number used. In my case, I need multiple buttons in a single row, but currently can't find a way to have multiple custom templates without the field prop values also being injected.
Here's a fiddle that shows CANCEL ORDER renders just a button, while VIEW MESSAGE shows the value 16 next to it.
Is there a way to manually hide a prop value in a cell?
jsfiddle
https://jsfiddle.net/synapse709/wc3uzf8d/

hey @titusdecali I think you misunderstand how row templates work. Each template is a row and your condition evaluates for every cell. This means your conditional logic will need to be part of the same if + else-if + else flow.
In other words, if matches cell 1, else if matches cell 2, else normal. Your corrected fiddle would be:
취소 불가

  <button
    size="small"
    variant="danger"
    variant-type="normal"
    @click="
      showModal({
        title: '인쇄소 메시지',
        message: props.row.comment
      })
    "
    >VIEW MESSAGE</button>

  <button>
    CANCEL ORDER
  </button>

  {{ props.formattedRow[props.column.field] }}

Notice how within the template, each span is part of the same logic flow. starting with an if, followed by else-if, followed by else. In your fiddle, you are telling vue to render "View Message" button, but then also render the formatted value if the cell does not match the last condition which is not what you want.
closing.

Thanks for the concise explanation and quick reply ^^


Consider "name" argument to create_index for index name

Current version does not allow giving a human readable index name.

Thanks for the PR, I also need this!  However, it looks like create_indexes probably needs name added as well.

Yes indeed, please add name in create_indexes before I merge.

Thank you for the review. I've implemented this change as proposed.


Hand Game Controller using OpenCV

Hand Game Controller using OpenCV
Solving Issue #58
I am a GSSOC'24 Extended and Hacktoberfest Contributor

@aviralgarg05 can you share the screenshots of results or screen recording

Should I upload them in the folder or just present them here?

@aviralgarg05 first show here

For different hand positions different key bindings are present, they can be printed in the terminal as well as work in games too

@aviralgarg05 Please modify the project to capture hand gestures via the webcam instead of using raw input, so I can clearly see how the hand gestures are detected

I guess now it is clear. If yes then I will commit the changes.

@aviralgarg05 yes go ahead!

@aviralgarg05 can you please add these results attachments in readme file then will merge it

@aviralgarg05 good,and please star the repo if you find it helpful


Incorrect screenshot in the document for ResourceUsageperApplication API Statistics.

As per the document [1] , the analytics data in WSO2AM 2.6.0 will be displayed in 5 columns i.e. Application Name, API Name, API Version, Resource Usage, Resource Hit Count.
But as per my investigation, the column support for Resource Hit Count was released in wso/carbon-apimgt version 6.4.60 [2] and support for API Version was released in wso2/carbon-apimgt version 6.4.230 [3] . WSO2AM 2.6.0 uses carbon-apimgt version 6.4.50. Hence the column support of API Version and Resource Hit Count should not be in WSO2AM 2.6.0.
If my understanding is correct, then document [1] needs an update for correct screenshot.
[1] https://docs.wso2.com/display/AM260/Viewing+API+Statistics#ViewingAPIStatistics-ResourceUsageperApplication
[2] https://github.com/wso2/carbon-apimgt/blob/v6.4.60/features/apimgt/org.wso2.carbon.apimgt.store.feature/src/main/resources/store/site/themes/wso2/templates/stats/apiCallType/js/stats.js
[3] https://github.com/wso2/carbon-apimgt/blob/v6.4.230/features/apimgt/org.wso2.carbon.apimgt.store.feature/src/main/resources/store/site/themes/wso2/templates/stats/apiCallType/js/stats.js

Closing Since the issue has been stale for a long time.


OSX handle CMD+key up combinations in Avalonia

What does the pull request do?
On macOS, when you press CMD + some key you don't get key up event notification as we do on Windows.
What is the current behavior?
The order of events is

KeyDown CMD
KeyDown A (modifiers CMD)
KeyUp CMD

What is the updated/expected behavior with this PR?

KeyDown CMD
KeyDown A (modifiers CMD)
KeyUp A (modifiers CMD)
KeyUp CMD

(this is aligned to Shift and Control behavior)
How was the solution implemented (if it's not obvious)?
I am a newbie with objective C (please check the code or rework completely). I was inspired by this SO thread https://stackoverflow.com/questions/4001565/missing-keyup-events-on-meaningful-key-combinations-e-g-select-till-beginning?rq=1
I think it is common behavior on mac but is not in line with other frameworks.
Breaking changes
We should get more events, not less. So it should be safe.
Note that there are other unrelated keyboard problems

Alt key does not forward key down/up keys.
Shift + key sends Shift + shift key on key down
Meta and LWin modifiers are kind of randomly used for the same CMD mac key. To align this would probably create some breaking changes though.

I based it on the master branch but the master branch is not buildable ATM. Try it on the RC branch to test.

You can test this PR using the following package version. 0.10.999-cibuild0018519-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Closing due to inactivity, please ping me if this is going to be worked on again.

@jmacato I saw you closed both this and https://github.com/AvaloniaUI/Avalonia/pull/6991 OSX PRs. What is the process to have this accepted? We use this code in our code successfully (from a custom build). If some additional samples/tests are necessary I can provide these.

@ltetak yeah i closed because i didnt see any activity over the last month. I'll reopen this and see if anyone in core can review it.

You can test this PR using the following package version. 0.10.999-cibuild0019328-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

@jmacato I'm just going to comment this here since it's the last one I saw. I noticed this happens a lot though. You are closing PRs that are clearly waiting for review of the Avalonia maintainers. I don't think you should just close PRs. First, ask if there is anything that needs to be done or if it is ready for review. Only if there is no response and clearly pending issues close it.
Closing good PRs just because the maintainers haven't reviewed it is a bad look for the project.

You can test this PR using the following package version. 0.10.999-cibuild0019914-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0019959-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Which Llama-7b model was used?

Which LLaMA 7b model was used?
Is it available on Hugging face?
Thank you. I am trying to reproduce your success

This project needs a bit of an update. Fine tuning in a large text file is not going to have the results you are looking for. You can now use Superoobago however use the extension https://github.com/oobabooga/text-generation-webui/tree/main/extensions%2Fsuperbooga
In text generation webui. The Vicunia model you can use that is pretty good is Vicuna 1.3 7B .

@hypersniper05 Thank you for introducing Superbooga! I will try it out.
For the case where the LLM 2K context window is too small to fit in the context when using superbooga, is it finetuning still the way to go?

Can you run the 13B quantized ? It's 11GB vram. Here is the link:
https://huggingface.co/TheBloke/Vicuna-13B-1-3-SuperHOT-8K-GPTQ
The superhot funetuned gives you more tokens.
I have been able to get 6k out of it with a 3080ti.
Update oobabooga, download the model via url link in models tab, set model to exllama, use 6k sequence length, 2 context, set chat instruct template to vicuna 1.1 . Select instruct on chat and setup superbooga.
If you use context 4 with 8k on my machine at least, numbers are off. The model will have a missing 0 if it quotes 00 .

I just wanted to let you know that chatgpt can help you with your prompt to get it to work better for you. Usually, I don't have to be so specific with chatgpt 3.5, but with 13B and 7B, you do. I just finished creating synthetic data for a training I want to do on a smaller 3B model (planning on running it on mobile)  using the Vicuna 13B 1.3 model, and looking at my spreadsheet and comparing the same query and outputs its scary similar to turbo3.5. Turbo is slightly and I mean very slightly better, but you won't be able to tell. It's all about the prompt for these little guys.


ERROR in ./node_modules/xpath-helper/dist/mjs/xpath-helper.js [SOLVED]

some interesting error appears when importing in a commonjs based project:
Module parse failed: Unexpected token (9:6)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|  */
| export class XPathHelper {
>     sb;
|     /**
|      * Creates an instance of XPathHelper.
 @ ./src/modules/module/index.ts 9:0-42 50:17-19 50:41-47
 @ ./src lazy ^\.\/.*$ namespace object
 @ ./src/content_scripts/content.tsx

I tried all possible combinations of options in tsconfig and webpack but nothing worked. It seems as if mjs has precedence over cjs or that mjs is set as default somewhere so at the end I resorted to deleting ./node_modules/xpath-helper/dist/mjs/. That caused ./node_modules/xpath-helper/dist/cjs/ to be loaded.

Thanks, @nopmop for raising the issue :)
Would you have a project where I can reproduce the issue?
I wonder if adding "default": "./dist/cjs/xpath-helper.js", property inside exports object of package.json solve the issue.

I prepared a project skeleton for you (jrebecchi.zip).
To test, unzip, cd jrebecchi, then do npm i; npm run watch - you will see the error.
Then do: rm -rf ./node_modules/xpath-helper/dist/mjs/ and run npm run watch again, you'll see the error is gone.
It's good to see you're providing support actively for your library :)
Cheers!
jrebecchi.zip

@nopmop fix published in version v0.1.3 :)


SyncUp tutorial fixes

Here's a PR fixing a variety of issues I found while going through the tutorial. Overall it was quite good though!

Hi @dafurman, thank you very much for taking the time to make these fixes to our tutorial! It is incredibly kind of you and we are very appreciative.
It is going to be a bit tough for us to make the time to review this PR, as is. Many of the changes are no-brainers, and we would happily pull them in, but others require us to actually go through the tutorial and make sure that it works as intended.
If you have a bit more time, you could separate out the simple changes from the complex ones in a separate PR, and that would allow us to merge the simple changes quickly, and make it easier for us to vet the complex ones later.
I think the simple ones include:

Simple typos
Poorly formatted code like the {@MainActor stuff in tests
Obviously missing code like durationPerAttendee
And you can delete the commented out code

And if there is anything else you think is "simple" then please do include that.
If you were to PR those things we could happily merge, and then that might help make this PR a little smaller for us to grok.

If you have a bit more time, you could separate out the simple changes from the complex ones in a separate PR, and that would allow us to merge the simple changes quickly, and make it easier for us to vet the complex ones later.
If you were to PR those things we could happily merge, and then that might help make this PR a little smaller for us to grok.

Sure that's completely understandable, I was a bit worried about the PR size myself.
I'll break this out into sensible chunks of complexity sometime this week!

Hi @dafurman, we merged a bunch of tutorial fixes today and so you should be able to merge main into your branch to see what is left. Hopefully it isn't too much of a pain.

@mbrandonw Alright, this should be ready for review now and be easier to look at this time around!


Write manual test cases for "CaliforniaPage".

Please write a manual test case for the following pages, which involves breaking down the functionality of the webpage into specific steps that can be tested.
CaliforniaPage: https://prayersconnect.com/mosques/search/Anaheim%252C%2520California%252C%2520United%2520States/33.8365932%2C-117.9143012/33.8365932%2C-117.9143012
Please use this Google sheet for your test cases.
https://docs.google.com/spreadsheets/d/1PIzULJpRSBqpsujibqaAh4GZrrIZb48yqy2q3yJpSBI/edit?usp=sharing

ticket #39 Done. https://docs.google.com/spreadsheets/d/1PIzULJpRSBqpsujibqaAh4GZrrIZb48yqy2q3yJpSBI/edit#gid=836302319

Thank you.


Moonscript: dynamic code preview does not display the names of methods

added moon function to the code outline
displays only moon functions, not class methods

closing on .19


WIP: Create a web server example

This is a quick update to @bhansconnect's initial implementation:

Brought it up to date with (then) current trunk.
Added a flag to allow it to run as part of the CLI tests

Note that none of the commits are signed (didn't notice this until late in the game) and the branch is super old so this PR needs some help before it's a candidate for merge, but unfortunately I've been pulled in several different directions lately and don't know when I'll be able to get back to this.

@bparks would you still like to work on this?
We have roc-lang/basic-webserver now.
What do you think?

Would I like to work on it? Yes. Do I have the time to work on this? Sadly (or maybe happily..) no. I did see the new simple webserver project a few weeks ago and I'm excited to see that it's gotten some momentum.
My hope would be for a more declarative style for handling routing -- though there's certainly a question to be asked as to where "webserver" ends and "app framework" begins.
I need to log back into the group chat one of these days... perhaps I can at least be a resource for ideas, design, architecture guidance until I can free up some time to contribute actual code?
However, I do think this PR can safely be considered "superseded" by the simple-webserver project.

Thanks for the update. Your ideas will be very much appreciated in the discussion 😃
I'll close this PR for now. I look forward to exploring more declarative ideas for the API.


Numpy testing version 1.24

Pull Request Description
What issue does this change request address?
What are the significant changes in functionality due to this change request?
This is some library changes.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Test qsubs sawtooth on d899220 : canceled by @joshua-cogliati-inl
will certainly fail

Job Test qsubs sawtooth on dd8e960 : canceled by @joshua-cogliati-inl
not needed

Job Mingw Test on dd8e960 : canceled by @joshua-cogliati-inl
not needed

Job Test mac on dd8e960 : canceled by @joshua-cogliati-inl
not needed

Job Test qsubs sawtooth on c13bc3b : canceled by @joshua-cogliati-inl
not needed

Job Test qsubs sawtooth on c13bc3b : invalidated by @joshua-cogliati-inl
civet problems

Job Test qsubs sawtooth on c13bc3b : canceled by @joshua-cogliati-inl
failed already

Code combined with other code and moved to #2365


HTTR RELAP-7 model

HTTR documentation added to vtb.bib

Let's use a single issue for the entire model, and keep it more detailed.
However please do not populate this with any model information until this has cleared the lab review process


The release date is showing ahead of one month.

System information:

Operating system: Ubuntu 20.04
DBeaver version: <IP_ADDRESS>204021640

Describe the problem you're observing:
Today is April 4, 2022. The release date is showing ahead of one month.
Steps to reproduce, if exist:
Help -> About

Thanks you for the bug report.
It is a bug in release description. We will fix it in the next version.


Show zoom scale indicator in status bar

VSCode Version:
OS Version:

Steps to Reproduce:
1.
2.

@qasims please do not combine multiple requests in one issue. I've removed the second request.

Duplicate of #12318


Milligram css pointing to node_modules

Fix path that pointing to node_modules

Is we really need Milligram @ri7nz ?
Can we remove that?

Mungkin ada kaitannya dengan ini #13

@mazipan  maybe, we can wait for the response from @tyohan for milligram css.

@mazipan @ri7nz any suggestion for typography only CSS framework? Baseline grid typography make text content looks better.


remote_file drops default HTTP port from GET request

Description
I'm using remote_file to download a file from a HTTP source. The source contains the default port in the URL. Example: http://<IP_ADDRESS>:80/file. The server at the other end (in which I have no control over) requires the GET to come with the port included. If it's not there it responds with a 403 Forbidden error.
It seems that the as_uri(source) method used by Chef::Provider::RemoteFile::Content drops the port.
as_uri() is just URI.parse().
Chef Version
$ chef-client --version
Chef: 12.5.0.current.0

Platform Version
CentOS 7
Replication Case
irb(main):001:0> require 'uri'
=> true
irb(main):002:0> source = 'http://<IP_ADDRESS>:80/file'
=> "http://<IP_ADDRESS>:80/file"
irb(main):003:0> URI.parse(source)
=> #<URI::HTTP:0x00000001670358 URL:http://<IP_ADDRESS>/file>

Then have a server that doesn't like requests without the port.
Client Output
The file itself is not relevant here.
[2016-05-10T10:23:39+00:00] DEBUG: Initiating GET to http://<IP_ADDRESS>/file.rpm
...
    remote_file("/var/chef/cache/file.rpm") do
      provider Chef::Provider::RemoteFile
      action [:create]
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      path "/var/chef/cache/file.rpm"
      backup 5
      atomic_update true
      source ["http://<IP_ADDRESS>:80/file.rpm"]
      use_etag true
      use_last_modified true
      declared_type :remote_file
      cookbook_name "test"
      recipe_name "download"
      owner "root"
      group "root"
      mode "0644"
      not_if { #code block }
    end
[2016-05-10T10:23:39+00:00] INFO: Running queued delayed notifications before re-raising exception
[2016-05-10T10:23:39+00:00] DEBUG: Re-raising exception: Net::HTTPServerException - remote_file[/var/chef/cache/file.rpm] (test::download line 31) had an error: Net::HTTPServerException: 403 "Forbidden"

Testing with curl from the command line results in the same error. If I add the port, everything is fine. Without it the server responds with 403. It's picky.
I found this: CHEF-5355, but the Host header itself should be fine without the port. And it is just the IP with both remote_file and a curl test from the command line.

The quick answer is that the target server is broken. That said, can you do curl -v http://... for both the url with the port and the one with out it?

I don't understand how this doesn't conflict with CHEF-5355, and if curl doesn't work against this IP address I'm fairly hesistant to change remote_file.  If remote_file's header property can be used to set the Host header to work around this issue(?) the I really wouldn't see any need for code changes (and I'd be more inclined to take code changes that allowed overriding the Host header).

I'll try and remember to run the curl -v tomorrow. But I guess it won't reveal anything special.
I don't think it's an issue with the headers, it's with the URL in the GET itself. Curl sends the Host header similarly, with just the IP. So modifying the Host header won't work.
I assumed, and would like that whenever I use remote_file the URL used is the source specified and not something modified (the :80 dropped). Even if this case is due to a silly server.

I think that is just coming from Net::HTTP which also makes me somewhat disinclined to fix it...

$ curl -v http://<IP_ADDRESS>:80/file.rpm
> GET http://<IP_ADDRESS>:80/file.rpm HTTP/1.1
> User-Agent: curl/7.29.0
> Host: <IP_ADDRESS>
> Accept: */*
> Proxy-Connection: Keep-Alive

< HTTP/1.1 200 OK
< Date: Mon, 16 May 2016 06:27:56 GMT
< Server: Apache/2.4.7 (Ubuntu)
< Content-Length: 30646421
< Accept-Ranges: bytes
< Last-Modified: Mon, 02 May 2016 08:49:25 GMT
< Content-Type: binary/octet-stream
< Via: 1.1 http-proxy-in-between
<

$ curl -v http://<IP_ADDRESS>/file.rpm
> GET http://<IP_ADDRESS>/file.rpm HTTP/1.1
> User-Agent: curl/7.29.0
> Host: <IP_ADDRESS>
> Accept: */*
> Proxy-Connection: Keep-Alive

< HTTP/1.1 403 Forbidden
< Date: Mon, 16 May 2016 06:27:59 GMT
< Server: Apache/2.4.7 (Ubuntu)
< Content-Length: 358
< Content-Type: text/html; charset=iso-8859-1
<

There's a proxy in between too, but I don't think it matters here. And the 403 response seems to come from the real destination.
Any way, I get your hesitance to change things. Indeed, it seems to be a problem / feature of the Net::HTTP library. As you can see in the initial report, it's the URI.parse() that drops the port.
I already created a workaround using an execute block. I'd rather use remote_file though.
If this were going to be changed in Chef, I think the as_uri() would have to be change to be something more than just the URI.parse(). And that probably is used in multiple places. :)

I think we're going to say that this is a won't fix - we're pretty sure that Net::HTTP is behaving to spec, and this is the first time anyone's reported this, so the cost/benefit is not good.
Sorry we can't give you an answer you'd like more.


Missing baoab_vs_aboba_analysis.py file

This line in the master branch refers to a baoab_vs_aboba_analysis.py file that doesn't seem to be in the repository.
I'm a bit confused as to which branch is also the current one here...

Addressed -- now the required function is benchmark.plotting.plot_scheme_comparison


Issues parsing a previously encoded binary (non-UTF8) string.

This is a bit of an edge case, but it seems to be handled in other platforms (to varying degrees).
The simplest explanation I can give you is just to show you this code:
#include <string>
#include "json.hpp"
using json = nlohmann::json;

int main(int argc, const char **argv) {
    std::string encoded("\u0006\u00e4\u00b4\u00d8\u008d\"");
    auto j3 = json::parse(encoded);
}

Which produced this exception:
JSON Exception: [json.exception.parse_error.101] parse error at 1: syntax error - invalid literal; last read: '<U+0006>'test complete.

Note: the same error occurs when nlohmann has done the previous encoding of the string (as shown below).
Whilst I fully understand the reason for the error, I don't believe that it is valid to assume all strings will be valid UTF-8, merely because the JSON spec includes \u0000 unicode escape sequences.  I might be wrong, I haven't read the RFC lately.
Ignore everything below this line, as it's just more details. :)
Expanded tests
int main(int argc, const char **argv) {
    // binary string, not valid utf-8
    std::string ugly("\x06\xe4\xb4\xd8\x8d\x22");

    // will encode okay
    json j = {{ "text", ugly.c_str() }};
    printf("encoding complete.\n");                fflush(stdout);

    // 2.1.1 can dump okay
    // dumping: {"text":"\u0006▒؍\""}

    // 3.2.0 will trigger exception when dumping
    printf("dumping: %s\n", j.dump().c_str());     fflush(stdout);

    // both will trigger exception when parsing
    auto j2 = json::parse(j.dump());

    printf("test complete.\n");                    fflush(stdout);

Some tests with other platforms showed that php will not encode a raw non-UTF8 binary string, JavaScript (v8) had no issues, and python actually produced the "every character escaped" version I used in the initial example.
    // JavaScript tests (performed in Chrome console window)
    // helper functions from: https://nt4.com/js/hexdump.js

    /*
     * > j = JSON.stringify(sprintf("\x06\xe4\xb4\xd8\x8d\x22"))
     * < ""\u0006ä´Ø\"""
     *
     * > hexdump(j)
     * < 0000000: 22 5c 75 30 30 30 36 e4 b4 d8 8d 5c 22 22          "\u0006....\""
     *
     * > JSON.parse(j)
     * < "ä´Ø""
     *
     * > hexdump(JSON.parse(j))
     * < 0000000: 06 e4 b4 d8 8d 22                                  ....."
     */

PHP test:
    // PHP test (performed from bash shell, with the aid of a private helper)
    // (encode fails, but decode succeeds)

    /*
     * root@ec js $ echo -ne "\x06\xe4\xb4\xd8\x8d\x22" | phpparse - json_encode
     * false
     *
     * root@ec js $ echo -n '"\u0006ä´Ø\""' | phpparse - json_decode
     * ä´Ø"
     */
}

The JSON text in your initial program needs to be properly escaped. Here is a version with a raw string literal that works:
#include <string>
#include "json.hpp"

using json = nlohmann::json;

int main(int argc, const char **argv) {
    std::string encoded(R"("\u0006\u00e4\u00b4\u00d8\u008d")");
    auto j3 = json::parse(encoded);
}

I did not know that.  Unfortunately, there still remain an issue with your library - though fortunately, the solution is clearer now.
#include <string>
#include "json.hpp"

using json = nlohmann::json;

int main(int argc, const char **argv) {
    // binary string, not valid utf-8
    std::string ugly("\x06\xe4\xb4\xd8\x8d\x22");

    // will encode okay
    json j = {{ "text", ugly.c_str() }};
    printf("encoding complete.\n");                fflush(stdout);

    // 2.1.1 can dump okay
    // dumping: {"text":"\u0006▒؍\""}

    // 3.2.0 will trigger exception when dumping
    printf("dumping: %s\n", j.dump().c_str());     fflush(stdout);

    // both will trigger exception when parsing
    auto j2 = json::parse(j.dump());

    printf("test complete.\n");                    fflush(stdout);

More details in original post about how other languages handle this.
I have a proposed solution, not sure if I will be able to whip up a PR for it - I haven't checked what you use for unicode translation.  But essentially, there seem two open paths.
JavaScript (well, V8 anyway) passes through the invalid UTF-8 binary sequences as-is, or python escapes at a byte level when the UTF-8 encoding is not valid.
Your library will decode the python version, but not the JavaScript version, which can be tested thusly:
int main(int argc, const char **argv) {
    std::string encoded1(  "\\u0006\u00e4\u00b4\u00d8\u008d\"");
    auto j3 = json::parse(encoded);

This time the \u and \\u are used as intended to convey:
> j = JSON.stringify(sprintf("\x06\xe4\xb4\xd8\x8d\x22"))
< ""\u0006ä´Ø<8d>\"""

Related: #1198

Quite.  As someone who has always treated JSON as alternative to uuencode or base64_encode or similar utilities that can serialize and deserialize any binary string, I do feel strongly that any encoded input should be identical after encoding and decoding, even if only within the same library.
I'll take a look at the code now.

@nlohmann This is quite interesting.  A small alternation to my original test code, to properly encapsulate the string inside a key/value object in JSON format, and the library seems to be able to decode, re-encode, and dump, without apparent issue.
Is this all just a storm in a tea-cup?
encoded string: {"test":"\u0006\u00e4\u00b4\u00d8\u008d\""}
decoding complete.
dumping: {"test":"\u0006ä´Ø\""}
encoding complete.
dumping: {"test":"\u0006ä´Ø\""}
re-encoded complete.
dumping: {"test":"\u0006ä´Ø\""}

#include <string>
#include "json320.hpp"

#define JSON_TRY(...)                                                       \
    try {                                                                   \
        __VA_ARGS__;                                                        \
    }                                                                       \
    catch (json::exception e)                                               \
    {                                                                       \
        fprintf(stderr, "%s: JSON Exception: %s", __FUNCTION__, e.what());  \
        return 1;                                                           \
    }

using json = nlohmann::json;

int main(int argc, const char **argv) {
    json j;
    std::string encoded1(R"({"test":"\u0006\u00e4\u00b4\u00d8\u008d\""})");
    printf("encoded string: %s\n", encoded1.c_str());  fflush(stdout);
    JSON_TRY(
        j = json::parse(encoded1);
        printf("decoding complete.\n");                fflush(stdout);
    )

    JSON_TRY(
        printf("dumping: %s\n", j.dump().c_str());     fflush(stdout);
    )

    std::string encoded;

    JSON_TRY(
        encoded = j.dump();
        printf("encoding complete.\n");                fflush(stdout);
    )

    JSON_TRY(
        printf("dumping: %s\n", j.dump().c_str());     fflush(stdout);
    )

    json j2;
    JSON_TRY(
        j2 = json::parse(encoded);
        printf("re-encoded complete.\n");              fflush(stdout);
    )

    JSON_TRY(
        printf("dumping: %s\n", j2.dump().c_str());    fflush(stdout);
    )
}


Add Perplexity provider

Description
Add Perplexity provider ask in #711
It can be hard to setup this provider.
Especially to get the cookies:
You need to follow almost what is written here.
But instead of taking their curlconverter link, you need to use this (replace python by json and save the json the same way the hugging cookie is saved.

Motivation and Context

How has this been tested?
Tested by the main function only

Screenshots (if appropriate)
Types of changes

Changes visible to users:

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

Internal changes:

[ ] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[ ] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)
[ ] Infrastructure (prefix: chore - examples include GitHub Actions, issue templates)

Checklist

[ ] My code follows the code style of this project and passes yarn run lint.
[x] My change requires a change to the documentation.
[x] My change works!

Thanks!


css doesn't apply

Hi,
I've been trying to render the test I edited using Froala, but I got a few problems. I'm using rails-sass, so I imported the css files for froala using
@import "froala_editor.min.css";
@import "froala_style.min.css";
@import "plugins/video.min.css";
@import "plugins/video.min.css";
@import "plugins/file.min.css";
@import "plugins/image.min.css";
@import "plugins/fullscreen.min.css";
@import "plugins/quick_insert.min.css";

The thing is, it seems like it doesn't work. Unlike all other vendors, these lines are rendered directly in my compiled css file, same format:
@charset "UTF-8";
/* -------------------------------------
 * Fonts
 * ------------------------------------- */
@import url("https://fonts.googleapis.com/css?family=Open+Sans:400,300,700|Montserrat:400,700|Raleway:300,400");
@import url(froala_editor.min.css);
@import url(froala_style.min.css);
@import url(plugins/video.min.css);
@import url(plugins/video.min.css);
@import url(plugins/file.min.css);
@import url(plugins/image.min.css);
@import url(plugins/fullscreen.min.css);
@import url(plugins/quick_insert.min.css);

...

Is that related to sass ? or did I miss something ?
Second problem is, I assume the fr-view class is the one in charge of formatting the way my text is rendered, but since I do not have the css file, I had to find an alternative, so I used the rails sanitize method. It seems to be working, however, the videos are not displayed, and the text-align is not maintained. Without sanitize, I get this :

With sanitize, it turns into this

How comes so ? Is it all related to the missing css files ?

Hi Sashkan, I imagine you have overcome your issue but I would like to know how, since I have the same problem. Could you help me?

Hi @jbprat  , actually my issue came from AWS, I restricted the access to froala css and js files, and therefore had no design nor animations at all

FYI, for anyone else having the same problem, make sure you include the correct @import statements:
i.e. use: @import "froala_editor.min";
do not use: @import "froala_editor.min.css";


Add ARM64 images

Closes #26

will this build in github actions?

will this build in github actions?

It should


support multiple primers in primer columns

LinkerPrimerSequence and ReversePrimer can have multiple primers separated by commas.

Woops, this was already supported. Added a comment to the code explaining this.


PlatformIO GCC error in Linter

For some reason, GCC error is giving an error in Linter.

I2CSoilMoistureSensor.h: No such file or directory

However the program is still compiling and working fine, but the error is of annoyance.
Info:
I2CSoilMoistureSensor has been added in the project PlatformIO Library Manager as per instructions: http://platformio.org/lib/show/294/I2CSoilMoistureSensor/examples
platform.ini
[env:nodemcuv2]
platform = espressif8266_stage
board = nodemcuv2
framework = arduino
lib_deps = PubSubClient, ArduinoJson, I2CSoilMoistureSensor

Any ideas how I can debug this?

Hi,
sorry, but because I personally do not use PlatformIO I have no idea how to help here ...


S3 - Unable to sync: Error: connect ECONNREFUSED

When attempting to upload static assets to S3, I receive the ECONNREFUSED error.
Here's what it looks like:
→ ember deploy:assets --environment staging
version: 0.1.11
Uploading assets...
Unable to sync: Error: connect ECONNREFUSED
    at errnoException (net.js:905:11)
    at Object.afterConnect [as oncomplete] (net.js:896:19)

My deploy.json looks about like this:
{
  "staging": {
    "buildEnv": "staging",
    "store": {
      "host": "redacted.test",
      "port": 49155,
      "password": "XXX"
    },
    "assets": {
      "type": "s3",
      "gzip": true,
      "accessKeyId": "AAAAAAAAAAAAAAAAAAAA",
      "secretAccessKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
      "endpoint": "redacted.text.s3-website-us-west-1.amazonaws.com",
      "bucket": "redacted.test"
    }
  }
}

I tried multiple IAM accounts, and double-checked my S3 user policy:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["s3:ListBucket"],
      "Resource": ["arn:aws:s3:::redacted.test"]
    },
    {
      "Effect": "Allow",
      "Action": [
        "s3:PutObject",
        "s3:GetObject",
        "s3:DeleteObject"
      ],
      "Resource": ["arn:aws:s3:::redacted.test/*"]
    }
  ]
}

And bucket policy:
{
	"Version": "2012-10-17",
	"Statement": [
		{
			"Sid": "Allow Public Access to All Objects",
			"Effect": "Allow",
			"Principal": "*",
			"Action": "s3:GetObject",
			"Resource": "arn:aws:s3:::redacted.test/*"
		}
	]
}

I solved it by adding "region" to my deploy.json:
{
    "assets": {
      "type": "s3",
      "gzip": true,
      "accessKeyId": "AAAAAAAAAAAAAAAAAAAA",
      "secretAccessKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
      "region": "us-west-1",
      "bucket": "redacted.test"
    }
}


system artifacts: add system-buildinfo to return buildinfo

This adds support for an experimental (and controversial?) special type of artifact that we might call "system artifacts".
System artifacts are defined at the project level and their ids begin with system-. They cannot be created, listed, deleted, or replaced, but they can be read with get-artifact and get-artifact-contents.
One system artifact is defined, system-buildinfo, which returns a YAML-formatted description of the build and its dependencies. It is for use in environments that don't have access to Admin.GetStatus.
We could access the artifact with the following:
$ registry get artifacts/system-buildinfo -o yaml
apiVersion: apigeeregistry/v1
kind: BuildInfo
metadata:
  name: system-buildinfo
data:
  goVersion: go1.18.1
  path: github.com/apigee/registry/cmd/registry-server
  main:
    path: github.com/apigee/registry
    version: (devel)
    sum: ""
    replacement: null
  dependencies:
    - path: cloud.google.com/go
      version: v0.104.0
      sum: h1:gSmWO7DY1vOm0MVU6DNXM11BWHHsTUmsC5cv1fuW5X8=
      replacement: null
  ...
  settings:
    -compiler: gc
    CGO_CFLAGS: ""
    CGO_CPPFLAGS: ""
    CGO_CXXFLAGS: ""
    CGO_ENABLED: "1"
    CGO_LDFLAGS: ""
    GOAMD64: v1
    GOARCH: amd64
    GOOS: linux
    vcs: git
    vcs_modified: "true"
    vcs_revision: cfa42e6a3d6ddbbc1724543556c68d17e01b6933
    vcs_time: "2023-01-17T23:56:10Z"

And with tools like jq and yq, we could pick out specific values as needed:
$ registry rpc get-artifact-contents --name "projects/foo/locations/global/artifacts/system-buildinfo" -j | jq .data -r | base64 -d | yq .settings.vcs_revision
https://github.com/timburks/registry/commit/ea5d4c317c3aa93ef48d117820db8904a0ff6f8a

$ registry get artifacts/system-buildinfo -o yaml | yq .data.settings.vcs_revision
https://github.com/timburks/registry/commit/ea5d4c317c3aa93ef48d117820db8904a0ff6f8a

Some possible questions:

Why system- and not some other prefix? It's arbitrary, but I think we want to use valid artifact ids, which means no special prefixes like underscores or exclamation points.
Why not return these from List operations? At first it's laziness - including them in list operations would complicate listings - but also these might confuse users and as "system" features, they might be better hidden anyway.
What else might we want to have in system artifacts? Maybe some database-related info or registry configuration, but I don't think these are for application-specific data, meaning I wouldn't change any existing prefixes if we added these.
Would system- artifacts always be read-only? Maybe...
Does this break any proxying layers that expect to cache artifact metadata? Worth investigating... @Krpate?
Why return YAML and not serialized proto? User-friendliness
Why not JSON? Consistency with our current usage of YAML in the registry tool and the possible changes in #946.

(If we like this, I'll add tests)

It would be fairly easy to argue that this should be an explicit API. Is this a truly completely separate class of thing than operational health (eg. kubernetes) or runtime metrics (eg. prometheus) endpoints? That said, I do like the dynamic aspect of being able to expose new classes of system metadata without having to add new APIs... so I'm ambivalent at this point and easily swayed.

Is this a truly completely separate class of thing than operational health (eg. kubernetes) or runtime metrics (eg. prometheus) endpoints?

That's a very broad question! Yes? No? Failing to answer that, I think this is a practical compromise that accounts for the high cost of adding new API methods and the relatively low value of this information (it is high to a few developers but low to most users). If someone wanted to push through an API method that provided build info, I'd be happy to use the new method but I wouldn't be able to confidently say they'd spent their time productively considering all the other things they might have done. But we do have situations where we would like to verify the build version that we're working with, and there's nothing better than providing that directly (IMO).

Yes and opportunity cost is likely the strongest point here: Since this solution extends and existing pattern in an easily understandable way and reasonably clean way with minimal effort, that's a huge benefit. And, since I can't think of any truly painful side-effects, I feel this is a reasonable compromise.

Does this break any proxying layers that expect to cache artifact metadata?

We don't cache artifact metadata today but to consider plans down the line for making artifacts CCFE managed - If we are saying that system artifacts are always created by server during runtime and are read only then it shouldn't break anything.

but also these might confuse users and as "system" features, they might be better hidden anyway.

I realize how system-buildinfo can be useful for us as Apigee Registry API producers to provide support and debug issues. I am not seeing how this would be useful to API hub customers? If it's only for our use then maybe the internal producer API can be used for exposing this info?

I realize how system-buildinfo can be useful for us as Apigee Registry API producers to provide support and debug issues. I am not seeing how this would be useful to API hub customers? If it's only for our use then maybe the internal producer API can be used for exposing this info?

@Krpate thanks for this suggestion - I think there's value in keeping this solution open so that application-builders can also independently confirm the version of the API that they are using (or access whatever other metadata that we decide to share here). That certainly comes with caveats: this is not an official API feature and can be changed or removed at any time.

One possibility that we haven't discussed here involves no change to the API at all and follows an existing pattern: That is, simply use the controller to create / populate an regular artifact.


Several StaffBot improvements

Coverage decreased (-0.6%) to 90.761% when pulling d4bd3f43bb20b6f31dc78ab8a2118d15e64e9ee5 on staffing-priority into d8d3229fb0050ce529473e5760e33cefb933c102 on master.


Specify test path

When running pytest, it is best to specify the path to the tests (in our case, tests/), so that files that happen to be of the name test* but are not really tests are ignored. We can do this either by being explicit in the CI, or (the preferred way), by specifying the test path in pyproject.toml, so that the invocation of pytest on the command line picks up the correct test path from pyproject.toml.

Removed test path from dev.yml and integrated it in pyproject.toml.


feat: * Swap banner if Logic is on.

Closes #4092
This swaps the banner if Logic is on!~
To test: Have feature flag off. Then have it on.

QA Testing - LGTM! Just needs a PR Review :)


About the training time

Excellent work!
But I am confused about the training time that you spend. The only information related to the training duration that I see in the text is "The training of stable-diffusion-2-base costs hundreds of hours with 128× A100 GPUs." However, this seems to have no relation to GlyphControl.

Thanks for your questions. Yes, we only training the Glyph ControlNet part. The training time depends on the training dataset and available GPUs. For the case of training on LaionGlyph 1M, we used 8 cluster nodes, each of which has 8 32G V100s. On each GPU, the batch size is 16. Each epoch took around 3 hours and in the end it took around 64 hours to train the model for 20 epochs.
I hope that this information could be a useful reference for you.


Release a new version

Hi!
First of all, thanks for the work on this project!
I've noticed it's been a while since the release of version 1.8.7, and master has some features that would be really useful for me, like #1292.
Could we have a new release with all these fixes?
Thanks!

Oh , sorry! I'll subscribe to that other issue then 😄


Quantizated models availability in the default library

I've being using text-generation-webui to load 3 bit quantized models to fit my GPU memory (a GTX 1650, 4GB dedicated memory). I usually go to the user TheBloke hugging Face page and check if there is a compatible model. It is a straightforward process, very easy to acomplish requiring just the path and the models name (mostly GGUF format). Most the times they provide the template for instruction tasks, and I practically don't have to touch a single line in any configuration file to work. I'm satisfied with the inference process, and I get stable results that range from 10 to 15 tokens / s.
About your project, the ollama, when I saw the available library, I couldn't load practically any model because anything >= 4 bit precision is too much for my GPU memory.
I'm here to ask, if it's not a difficult task, and if you trust users like TheBloke, to make these quantized models available to use by a simple "one click" install in your UI. These models are already available and free to use. I'm asking a practial UI to use them with few steps without the need to write configuration files for them to work.
Thanks!

I'm very sorry, I'm writing this without testing the new updates (I tested long time ago). I see that there are some quantized models now.
Maybe I'm asking just a better integration with Hugging Face.
Anyway, thank you so much. Now I can test some models with your app!

Thanks @guinanet, I really appreciate you creating an issue. Keep an eye on https://github.com/jmorganca/ollama/issues/1267!


Disallow use insecure_example auth provider in configuration.yml

Description:
Disallow use insecure_example auth provider in configuration.yml
The insecure_example auth provider is for testing only.
Related issue (if applicable): fixes #15199
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Great! I think at a later point we can move the insecure example to the test dir and just patch it in place with a fixture when we want to do testing.

I think it is okay keep insecure_example in place, so that other developer can have an example to follow. No one will look at tests folder I believe.


Intake State Machine

Components

Intake

States

Intaking
Retracted

Thoughts
This state machine is pretty straightforward. It will just orchestrate the transitions between the two states of the intake mechanism. The bit still open to discussion is how we should trigger transitions between these states. It could be timed, but I think it will be better if we have at least one sensor involved to automate the sequence. To do this we will need to run some tests and think about what will work best here ;)

I have this idea of, when the driver presses the button, the intaking state will be active until the intake succeeds (e.g. an object pass through a break-beam sensor); when the driver press and holds the button, the intake will keep intaking untili the driver lets go of the button.
Would that be suitable for this case?

We are going to have this logic in the intake controller now


Add tasks for German Embedding Evaluation

We added a few tasks to evaluate German embedding models:
PawsX (https://huggingface.co/datasets/paws-x): This dataset contains pairs of an original text and a paraphrased version of it. The labels determine whether it is a real paraphrase or the content has a different semantic. We add this as a pair classification task to MTEB
MIRACL (https://huggingface.co/datasets/miracl/miracl): This is originally retrieval dataset. It contains a corpus of passages from Wikipedia articles and human-annotated relevance judgements for some of them.  We only took passages where relevance judgements are available since those are suitable for an MTEB re-ranking task.
GerDaLIR (https://github.com/lavis-nlp/GerDaLIR): GerDaLIR is a legal information retrieval dataset created from the Open Legal Data platform with the same name.
GermanDPR (https://www.deepset.ai/germanquad): GermanDPR is a passage retrieval tasks for question answering, i.e. it contains questions associated to passages which contain the relevant answer.
XMarket (https://xmrec.github.io/): This is originally a ecommerce product dataset which contains titles and descriptions of products which are associated to very fine-granular categories. We created a category to product description retrieval task out of it.
GermanSTSBenchmarkSTS (https://github.com/t-systems-on-site-services-gmbh/german-STSbenchmark): This dataset is an STS dataset created by T-Systems. It contains translations of English STS datasets.

I also updated the script in scripts/run_mteb_german.py to include those additional tasks, as well as the exiting German tasks for clustering and STS

Seems also be related to #183

Do you already have some results on what embedding model works best for german atm?

Do you already have some results on what embedding model works best for german atm?

I have shared some results here:
https://twitter.com/michael_g_u/status/1747293709849227618

@Muennighoff is it possible to assign someone to review this PR?

guenthermi

Taking a look! Also invited you to the org so you can request reviews in the future 👍
Amazing work on this!

Let's merge?

Let's merge?

It did't work out with just adding more languages for PawsX so I had to adjust the code in AbsTaskPairClassification to support multilingual datasets. If it looks ok to you, we can merge it
I evaluated some multilingual e5 models on the PawsX task:

de
en
es
fr
ja
ko
zh

e5-multilingual-small
0.538849
0.548835
0.537453
0.556763
0.493585
0.512998
0.54783

e5-multilingual-base
0.544398
0.540388
0.550975
0.569298
0.497352
0.511751
0.556259

e5-multilingual-large
0.575009
0.595169
0.563678
0.585035
0.49574
0.516579
0.57002


[Bug report]: missing padding in Table header in compact mode

Requirements before reporting

[X] No duplicated issue reported.
[X] I have checked the latest version if the bug exist there. See all available packages at npmJS.com
[X] I have followed the installation guide.

Package versions
@scania/tegel: ^1.6.0
Browser
Chrome
Framework
Angular
Version
Angular 16
Reproduction steps

Create a Tegel Table with a header
Set it to use compact mode
Write a long text in one of the columns
Shrink the window until the line breaks into multiple rows
Observe how there is no padding over or under the text

Code example
   <tds-table
        [responsive]="true"
        [compactDesign]="true"
        [noMinWidth]="true"
    >
                <tds-table-header>
                        <tds-header-cell
                            [cellValue]="A very very long text that keeps going and going and never ends and just keeeps going until the bitter end and never stops because it just keeps going and going and just continues through time and space into eternity and just continues after that too..."
                            sortable="true"
                       >
                </tds-table-header>

                <tds-table-body>
                     <tds-table-body-row></tds-table-body-row>
                 </tds-table-body>
</tds-table>

Screenshots

Expected behaviour
There should be padding at the top and bottom even when the text breaks into multiple rows and when it is in compact mode
Console errors
Add warning/error message
Contact information
<EMAIL_ADDRESS>

Hi @jolalab! Thank you for reporting this, a fix for the issue has now been merged and will be available in the next release! :)


Add compat mode option to AzureClient and TinyliciousClient

AB#7966
Based on @vladsud 's #20283 , this is a draft of API surface to toggle 1.x vs. 2.x compat mode.
Note that this feature's goal is to ensure compatible upgrade from 1.x to 2.x because the default settings don't allow for that currently.  It is not a generic feature flagging API; feature owners must develop a go-to-market plan for their individual features.  This API is intended to be for 1->2 only, and not for future version upgrades.
Putting up as a draft PR as a preview of the surface while I experiment with the usage.  Re: defaults and optionality, I optimized for (in order):

Folks upgrading from 1.x get a compatible experience by default
Default values prefer 2.x except where required to satisfy bullet 1
Easing eventual removal of the option by preferring optional over required so customers can omit the argument as much as possible except where required to satisfy bullet 1.

EDIT: From feedback, changing to mandatory params.

Marking this ready for review - I had a chance to experiment with this and it worked as expected in a variety of scenarios.
Main downside is that when attempting to load a "2"-mode document in a true 1.x client, the errors are a little obtuse (e.g. I hit 0x122 and "Summary metadata mismatch", Vlad's tests imply 0x162 and 0x121 would also be expected).  I think this is probably best served by ensuring the documentation covers the situation well.


Tracking issue: 🤝 mock consensus engine for integration tests

💭 background and motivation
currently, writing complete end-to-end integration tests for Penumbra is
difficult.
currently, the smoke-test.sh script performs the steps needed
to run integration tests of the system, including:

generate testnet configuration
start a cometbft process
start a pd process
run pclientd integration tests against the local test network
run pcli integration tests against the local test network
confirm the test network is still running

because these integration tests assume a test network including pd and
cometbft is running locally, these tests must run serially, and must spend
time waiting for new blocks to be generated.
additionally, this means we must under-handedly make use of the #[ignore]
attribute to prevent these tests from running (and failing) alongside unit
tests when commands like cargo test --workspace are run.
see CometMock for a mock implementation of CometBFT implemented
in Go. see #2771 for previous work in this space integrating with CometMock.
📐 overview
this state of affairs would be improved if we had a mock implementation of the
consensus engine (CometBFT) that would allow #[test] functions to
generate ABCI messages. this mock implementation should function as a drop-in
replacement for CometBFT from the perspective of the pd daemon.
this mocking library should additionally expose some "meta" interfaces. to allow us
to write integration tests including things like:

manipulating the timer used for generating blocks, so that edge-cases
involving e.g. expiry may be exercised.
commit double-signing violations
[...] (this list is non-exhaustive at the time of writing)

this will allow us to run integration tests faster, write them more easily,
and generally improve our ability to make assurances about the correctness
of our software.
:link: related work

#3597
#3695

#3672

#3740
#3741
#3753
#3754
#3755
#3756
#3757
#3758
#3759
#3760 (NOT MVP!)

:eyeglasses: further reading

#1664
#1675

update 2024-01-09: in #3592 and in some direct conversations, we discussed the desire to address #3588 using two crates: (1) a core library that provides the ability to generate block headers, and (2) an in-memory consensus engine with facilities to manipulate time.
after some further reading, i believe it makes sense to keep #3597 focused on (1), rather than attempting to completely address #3588 in one PR. this core library should be able to generate valid block headers that can be successfully parsed by a real light client library. (tendermint-light-client-verifier seems promising for this)
today i spent time reading through the broad strokes of how the protobuf types and .proto files are used to generate Rust types that can be (de)serialized and used by core application logic. i also spent some time today learning more about how the cnidarium crate's StateRead and StateWrite traits are extended by the penumbra-chain and penumbra-ibc libraries in crates/core/component. the latter part led me to some the message handling code, which interacts with cometbft/tendermint headers.
at this point i'm still getting a lay of the land, but i feel like i am gaining a much clearer picture of what work is to come. tomorrow i'll meet up with @avahowell to answer questions i've accrued concerning IBC, and spend some time working on stubs to generate a valid tendermint block header.

:bread: :link: helpful links for future reference

https://github.com/penumbra-zone/ibc-types
https://rustdoc.penumbra.zone/main/ibc_types/lightclients/tendermint/client_state/struct.ClientState.html
https://crates.io/crates/tendermint-light-client-verifier
https://crates.io/crates/tendermint-light-client
Header structure: https://github.com/penumbra-zone/penumbra/blob/29b7cb2afde3a664bcbcbbe33e544b43a802ee83/crates/proto/src/gen/tendermint.types.rs#L104

update 2024-01-22:

today i continued to push pr #3597 along. i am at the point where i can almost feed output into the tendermint-light-client-verifier.
as of now, i have a lightweight validator system defined, defaulting to a single validator. i have my consensus state defined, modeled after (some of) comet's own internal consensus state.
there is still much more to do, but it's tremendously exciting to see this library progressing past the embryonic stages. h/t to conor for showing me some relevant plumbing in the pd daemon today as well.
that's all from me for this week, i will see you all on monday 💐

me, #status channel in discord

with my draft pr (#3597) further along, i am going to pivot focus to work on #3627 this week. i'll resume work on this issue afterwards.

update 2024-02-06: my focus this week has been scoping and specifying the work to be done, and filing tickets. see :point_up: #3740, #3741, #3753, #3754, #3755, #3756, #3757, #3758, #3759, #3760.
i'll be meeting with Henry tomorrow to talk more about this, and hopefully pair program a bit.

I think it would be good to focus this effort on the concrete goal of writing App-wide tests, which is the purpose of building the mock engine. We already have two of these, which were added in the original testing push in #1664 / #1675:

app/src/tests/spend.rs
app/src/tests/swap_and_swap_claim.rs

We should start by writing a second version of each of those tests, but instead of driving each component's code manually in the #[test] function, we'd just instruct the mock engine to do high-level steps. This will ensure we're not overbuilding the test infrastructure relative to what we need.
Let's look at the first, simpler test, in spend.rs. In what follows I'll make up some stub API along the way, but this is just to convey a general shape, I'm not opinionated about the specifics. I'll also take the liberty of slightly rearranging the blocks of code in the existing test to fit a narrative order.
#[tokio::test]
async fn spend_happy_path() -> anyhow::Result<()> {
    let mut rng = rand_chacha::ChaChaRng::seed_from_u64(1312);

    let storage = TempStorage::new().await?.apply_default_genesis().await?;
    let mut state = Arc::new(StateDelta::new(storage.latest_snapshot()));

    let height = 1;

This is initializing a new TempStorage with a default genesis data. Instead, this should look something like this:
#[tokio::test]
async fn spend_happy_path_2() -> anyhow::Result<()> {
    let mut rng = rand_chacha::ChaChaRng::seed_from_u64(1312);

    let storage = TempStorage::new().await?;
    let app = App::new(storage.latest_snapshot());
    let engine = MockComet::builder()
        .single_validator() // builder-style methods for configuring validators
        .app_state(genesis::AppState::default()) // N.B. will later need an ext trait
        .init_chain(app) // "finish" method of builder, saves app and calls InitChain
        .await?;

As before, we create a TempStorage for an RAII-guarded temporary storage that only lives as long as the test. However, instead of manually writing in the genesis state, we first construct a complete App instance. Then, we instantiate a MockComet and use a builder API to configure it, before passing in the app to call init_chain.
The note about the extension trait is that we'll later want to have an extension trait for the builder API that does Penumbra-specific behavior, because the Penumbra application needs to know about its validators at genesis, so we'll eventually want to have a method that can "reconcile" a default genesis state with whatever validators the MockComet was configured with. But I think this is not particularly important to start off with, until we seek to exercise the staking component.
Let's keep going.
    // ORIGINAL spend_happy_path()

    // Precondition: This test uses the default genesis which has existing notes for the test keys.
    let mut client = MockClient::new(test_keys::FULL_VIEWING_KEY.clone());
    let sk = test_keys::SPEND_KEY.clone();
    client.sync_to(0, state.deref()).await?;
    let note = client.notes.values().next().unwrap().clone();
    let note_commitment = note.commit();
    let proof = client.sct.witness(note_commitment).unwrap();
    let root = client.sct.root();
    let tct_position = proof.position();

This section uses the existing MockClient to mock a Penumbra client syncing the chain. Remember that Penumbra distinguishes between public data, kept on-chain, and user data, kept off-chain on the user device. So to perform actions, we not only need a way to mock the consensus engine, but also a way to mock a client.
The MockClient is a minimal reference implementation of the Penumbra client logic (as compared to the entire Rust view server, which has a ton of incidental complexity), accessing the state directly rather than making network calls and only keeping data in memory.
This code would remain unchanged. If the complexity of the actions we wanted to perform in tests grew, we could either hook up the complete view server implementation, or add adapters to the MockClient. In any case, it's not the problem we need to address right now.
    // ORIGINAL spend_happy_path()
    // 1. Simulate BeginBlock
    let mut state_tx = state.try_begin_transaction().unwrap();
    state_tx.put_block_height(height);
    state_tx.put_epoch_by_height(
        height,
        Epoch {
            index: 0,
            start_height: 0,
        },
    );
    state_tx.apply();

    // 2.  Simulate execution of the Spend action
    spend.check_stateless(transaction_context).await?;
    spend.check_stateful(state.clone()).await?;
    let mut state_tx = state.try_begin_transaction().unwrap();
    state_tx.put_mock_source(1u8);
    spend.execute(&mut state_tx).await?;
    state_tx.apply();

    // 4. Execute EndBlock
    let height = 1;
    let end_block = abci::request::EndBlock {
        height: height.try_into().unwrap(),
    };
    ShieldedPool::end_block(&mut state, &end_block).await;

    let mut state_tx = state.try_begin_transaction().unwrap();
    // ... and for the App, call `finish_block` to correctly write out the SCT with the data we'll use next.
    state_tx.finish_block(false).await.unwrap();

    state_tx.apply();

    Ok(())

In the rest of the test, the current code:

manually does some ad-hoc BeginBlock simulation (not exercising the real codepaths, just manually poking at the state)
creates a "detached" Spend action isolated from any transaction (this will never occur in reality) and does ad-hoc mocking to patch up the fact that there is no containing transaction
executes only that Spend action, isolated from any containing transaction
manually simulates EndBlock (but only for the ShieldedPool component, leaving the app in an invalid state).

Instead, this should use MockComet to execute the entire app logic, so we are testing the code paths we care about and creating complete state transitions:
    // NEW spend_happy_path_2()

    // 1. Create a `TransactionPlan` with a 1-spend, 1-output transaction
    let plan = TransactionPlan {
        // self-contained struct literal with a 1-spend, 1-output transaction
        // using the data obtained from the MockClient as in the snippet above
    };
    let auth_data = AuthorizationData {
        // we can either create a struct literal with the signatures we need,
        // or we can initialize a SoftKms instance with the test keys and pass the plan
    };
    let witness_data = WitnessData {
        // self-contained struct literal using the inclusion proof from the MockClient
    };

    // 2. Use the `TransactionPlan`, `AuthorizationData`, and `WitnessData` to build the transaction
    let tx = plan.build_concurrent(...).await?;

    // 3. Now use the `MockComet` to create a new block with that transaction
    engine.block_builder()
        //.timestamp(...) // methods for controlling simulated execution
        .add_tx(tx.encode_to_vec()) // adds to list in block builder
        .execute() // triggers app execution
        .await?;

This is much simpler and less error-prone. We need to change from simulating a single Spend action in isolation to simulating it in a complete transaction. But this is fine, because that's the actual code path we are going to be executing.
We manually plan the transaction using the data from the MockClient, then build it. Later, if the complexity of transaction planning grows, we may want to consider adapting the Rust view server into the test framework, but this is not important to worry about now.
Then, we use a block_builder() builder API on the MockComet instance to create a new block and execute it against the app. I'm imagining that in general, invocations of the builder API should look like:

zero or more calls to various methods for controlling simulated block production, like setting a timestamp, setting certain validators as not signing, and so on. The important thing here is that these all must be optional, with reasonable defaults, so that it's low-friction to write tests; for instance, if there was no call to .timestamp, there should be default of 5s relative offset, etc.
zero or more calls to add_tx, appending transactions into the block;
.execute(), which builds the block as-configured and then drives execution of the application.

Now, in this example, we can go even further with spend_happy_path_2():
    // NEW spend_happy_path_2()

    // 4. Use the MockClient to check that we detect our output note
    client.sync_to(...)
    // .... check that the note we expect is now seen in the MockClient

    // ... or we could make a second transaction, checking we can spend notes that weren't created at genesis
    // ... or we could check that a double-spend fails, or, ....

By contrast, what would happen if we tried to add this to the existing test? The entire test would explode, because the current test leaves the application in an invalid state, it doesn't write out the compact block, it doesn't close the SCT, etc., because it doesn't execute the full application logic.
Note also what's not required: anything other than actually driving the application and feeding it a header as part of BeginBlock. At this point, the header doesn't even need to be valid -- that would only come into play once we try to write an IBC test (#3758).

I think it would be good to focus this effort on the concrete goal of writing App-wide tests, which is the purpose of building the mock engine.

first: i've renamed this issue, to be clearer about the fact that this is not intended for intgegration tests, and is intended for App tests.

This is initializing a new TempStorage with a default genesis data. Instead, this should look something like this:

#[tokio::test]
async fn spend_happy_path_2() -> anyhow::Result<()> {
    // ...
    let engine = MockComet::builder()
        .single_validator() // builder-style methods for configuring validators
        .app_state(genesis::AppState::default()) // N.B. will later need an ext trait
        .init_chain(app) // "finish" method of builder, saves app and calls InitChain
        .await?;

this part, where we "finish" the builder, and call InitChain was what i was intending to describe and track with #3754.

[T]he Penumbra application needs to know about its validators at genesis, so we'll eventually want to have a method that can "reconcile" a default genesis state with whatever validators the MockComet was configured with. But I think this is not particularly important to start off with, until we seek to exercise the staking component.

i am curious to talk to you more about this. i filed #3760 to track what i think this is implying: we will want to be able to supports multiple validators to exercise certain components, like the staking component you mention.
i agree that running a single node is all that is needed for an MVP, and we don't want to introduce networking complexity into tests.
i suspect i am misunderstanding something.

[ ] - TODO file an issue for the block builder API

crossreferencing https://github.com/penumbra-zone/tower-abci/pull/41#issuecomment-1936860930 for visibility

x-ref https://github.com/penumbra-zone/penumbra/pull/3902#issuecomment-1972239643


Flutter Build Web Cache issue when we changing local.env

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

You have a working flutter app with .env file with some base url or encryption key etc.
Change any variable in .env file
Upload the build on web
you will see the cache is not cleared and new .env variable is not upload.
Because flutter only reload cache data when we change something in pages in mainfest.js
But when we directly change some asset or.env file it will not reload the cache data and you wont get the new updates

Expected results
when i change in .env it should update it when web application when it goes live and start working with new client id i should not have to clear the cache first
Actual results
I have change the google client id in .env file
upload it but when i open live website it is working with old client id
then i had to clear cache then it start working
it was suppose to take care if that
Code sample
Code sample
class GoogleSignInService {

  static final _googleSignIn = GoogleSignIn(
    clientId: dotenv.env[Environment.clientId],
  );

  static Future<GoogleSignInAccount?> login() => _googleSignIn.signIn();

  static Future logout() => _googleSignIn.disconnect();

}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.7, on macOS 14.0 23A344 darwin-arm64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[!] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    ✗ Unable to get list of installed Simulator runtimes.
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.83.0)
[✓] Connected device (2 available)
[✓] Network resources

! Doctor found issues in 1 category.

Hi @syed-growexxer
Could you share a complete sample code for this issue? (a simple app only reads env variable for eg)


feat: add OpenCensus metrics recorder

Using OpenCensus to record when a request is being sent to CalculateMatrix. This should make it easier to keep track of the number of requests being made.
Also bumped to go 1.17
@odsod Would like your feedback on the implementation!

Yeah makes sense. I'll add something in our repository instead! 👍


Need help with Camera and xMOS chip

Hi-
We need drivers to get the xmos audio processor up under Linux.  We also need the camera drivers.  Would it be possible to post these? We are happy to make a cash donation or exchange some Kuri parts & boards to help.
Thanks!
<EMAIL_ADDRESS>

@MartinBodo do you still have issues with the audio and/or camera firmware? If not, I'll close this.

Hi Paul-
Thanks for the follow-up. Missed your earlier email.
I'll pass this on to the team and get back to you early next week.
Thanks again for your help.
-Martin
On Fri, Feb 1, 2019 at 1:41 PM Paul Mathieu<EMAIL_ADDRESS>wrote:

@MartinBodo https://github.com/MartinBodo do you still have issues with
the audio and/or camera firmware? If not, I'll close this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KuriRobot/Kuri-Documentation/issues/23#issuecomment-459877218,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArfvpabnWwyDX24u3r3JXp6HIAhwATtcks5vJLRrgaJpZM4Zo7Z4
.

--
Thanks,
Martin Bodo
Digital Loggers, Inc.
2695 Walsh
Santa Clara, CA 95051
(408) 330-5599
<EMAIL_ADDRESS>

Hi Paul-
We were able to figure out the xmos part with some help from the factory.
It works will with the Mayfield drivers.
Unfortunately we don't have a Kuri running.There are lots of parts, boards,
etc, but no image files for either the eMMC flash or SD card.
Is there flash image file for Kuri (containing /opt/geocam) somewhere on
the web?
Could you post one possibly? We would be willing to pay for it.
Thanks
-Martin
On Sat, Jan 12, 2019 at 3:03 PM Paul Mathieu<EMAIL_ADDRESS>wrote:

If you have a running Kuri, you should be able to get these from the robot
itself.
You'll find the camera firmware in /opt/geocam.
As for the driver, you'll have to use madmux, for which you'll only find
a binary version on the robot. See the doc here:
https://github.com/KuriRobot/Kuri-Documentation/blob/master/reference/ros-packages/madmux.md
For the audio, the Kuri software is able to flash its xmos audio chip.
Look for the /opt/gizmo/lib/xmos_linux_tools/xmos_updater executable. The
firmware binary should be under
/opt/gizmo/share/xmos_linux_tools/mayfield.bin
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/KuriRobot/Kuri-Documentation/issues/23#issuecomment-453787693,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArfvpYTVnUn5VkyvPdkVJ5OFDr9uc3PGks5vCmmpgaJpZM4Zo7Z4
.

--
Thanks,
Martin Bodo
Digital Loggers, Inc.
2695 Walsh
Santa Clara, CA 95051
(408) 330-5599
<EMAIL_ADDRESS>

Is there flash image file for Kuri (containing /opt/geocam) somewhere on the web?

Unfortunately I don't think any of us former employees retained any Mayfield files and/or IP. One thing that could be done is finding somebody with a running robot and ask them to make an image of the filesystem and upload it somewhere.
Something like the following should work:
tar --one-file-system -c / | gzip > kuri.tar.gz

IMPORTANT: the resulting file may contain sensitive data (wifi passwords, robot UUID, user account info...)

Hey sorry for the delay our Kuri was wondering around campus and I did not have a chance until now to grab the /opt/geocam folder.
https://www.dropbox.com/s/9uvgy6rannd43bz/geocam.zip?dl=0

Hi-
I would like to offer some free spare parts for Kuri.
If anyone needs a spare High Speed Board or some spare drive motors, we
have them in Santa Clara.
All in the spirit of keeping Kuri alive!
-Martin
On Fri, Feb 1, 2019 at 1:41 PM Paul Mathieu<EMAIL_ADDRESS>wrote:

@MartinBodo https://github.com/MartinBodo do you still have issues with
the audio and/or camera firmware? If not, I'll close this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KuriRobot/Kuri-Documentation/issues/23#issuecomment-459877218,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArfvpabnWwyDX24u3r3JXp6HIAhwATtcks5vJLRrgaJpZM4Zo7Z4
.

--
Thanks,
Martin Bodo
Digital Loggers, Inc.
2695 Walsh
Santa Clara, CA 95051
(408) 330-5599
<EMAIL_ADDRESS>

Hi Martin,
I know this is an old thread, but I would really like to purchase some spare Kuri parts or a dead robot if possible.
Please let me know if you still have some laying around.


Pressing the back button when no soft keyboard is displayed cause a NullPointerException

Reproduction:
Pressing the back button (hardware keyboard or soft button) when no soft keyboard is diplayed cause the app to crash (hide the soft keyboard otherwise).
Expected :
The Application send an ESC key to the terminal.
Crash location
Term.java:backkeyInterceptor@308
Error:
NullPointerException
Version :
1.0.68
Platform :
Android 4.4.4 KatKiss variant, Asus TF101
Possibly relate to missing action bar since material design switch.

Clearing the Data seem to fix the issue, so I would point at a bad upgrade

On a phone ( japan variant of the htc m7), the line number throwing the exception is different ( 950 )

The fix #411 is imperfect as mActionBar ( set on line 377 )is not suppose to be null when mActionBarMode  is TermSettings.ACTION_BAR_MODE_HIDES,  the reason why ActivityCompat.getActionBar is returning null should be checked


nixos/gnupg: (fix) use runtimeShell to call updatestartuptty

Description of changes
Fixes  #208791.
This wraps the ssh_config hook to simulate changing TTYs in a shell script, to make sure it is called by the correct interpreter.
In Nushell 0.73.0, the hook causes the following complaint:
use 'out+err>' instead of '2>&1' in Nushell

This ought to fix it.

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

I tested this with a couple of shells and it seems to be working as expected. Can you just fix the newline at the end?

Done. Thanks for the review and tests!


nixStatic broken on aarch64-linux

Steps To Reproduce
Steps to reproduce the behavior on aarch64-linux:

nix build nixpkgs#nixStatic -L

btw nix build github:nixos/nix#nix-static works fine.
Build log
[...]
nix-static-aarch64-unknown-linux-musl> running install tests
nix-static-aarch64-unknown-linux-musl> installcheck flags: -j4 SHELL=/nix/store/99bgmihz5ybclg11h00nm9lgqmsfhp4p-bash-5.1-p16/bin/bash profiledir=\$\(out\)/etc/profile.d PRECOMPILE_HEADERS=0 installcheck
nix-static-aarch64-unknown-linux-musl>   GEN    tests/common.sh
nix-static-aarch64-unknown-linux-musl>   GEN    tests/config.nix
nix-static-aarch64-unknown-linux-musl>   GEN    tests/ca/config.nix
nix-static-aarch64-unknown-linux-musl> ran test tests/flakes/mercurial.sh... [SKIP]
nix-static-aarch64-unknown-linux-musl> ran test tests/flakes/flakes.sh... [SKIP]
nix-static-aarch64-unknown-linux-musl> ran test tests/flakes/circular.sh... [SKIP]
nix-static-aarch64-unknown-linux-musl> ran test tests/flakes/run.sh... [FAIL]
nix-static-aarch64-unknown-linux-musl>     ++ [[ -n '' ]]
nix-static-aarch64-unknown-linux-musl>     ++ trap onError ERR
nix-static-aarch64-unknown-linux-musl>     + clearStore
nix-static-aarch64-unknown-linux-musl>     + echo 'clearing store...'
nix-static-aarch64-unknown-linux-musl>     clearing store...
nix-static-aarch64-unknown-linux-musl>     + chmod -R +w /build/nix-test/tests/flakes/run/store
nix-static-aarch64-unknown-linux-musl>     + rm -rf /build/nix-test/tests/flakes/run/store
nix-static-aarch64-unknown-linux-musl>     + mkdir /build/nix-test/tests/flakes/run/store
nix-static-aarch64-unknown-linux-musl>     + rm -rf /build/nix-test/tests/flakes/run/var/nix
nix-static-aarch64-unknown-linux-musl>     + mkdir /build/nix-test/tests/flakes/run/var/nix
nix-static-aarch64-unknown-linux-musl>     + clearProfiles
nix-static-aarch64-unknown-linux-musl>     + profiles=/build/nix-test/tests/flakes/run/var/nix/profiles
nix-static-aarch64-unknown-linux-musl>     + rm -rf /build/nix-test/tests/flakes/run/var/nix/profiles
nix-static-aarch64-unknown-linux-musl>     + rm -rf /build/nix-test/tests/flakes/run/test-home/.cache /build/nix-test/tests/flakes/run/test-home/.config /build/nix-test/tests/flakes/run/test-home/.local
nix-static-aarch64-unknown-linux-musl>     + cp ../shell-hello.nix ../config.nix /build/nix-test/tests/flakes/run/test-home
nix-static-aarch64-unknown-linux-musl>     + cd /build/nix-test/tests/flakes/run/test-home
nix-static-aarch64-unknown-linux-musl>     + cat
nix-static-aarch64-unknown-linux-musl>     + nix run --no-write-lock-file .#appAsApp
nix-static-aarch64-unknown-linux-musl>     run.sh: line 22:  6216 Segmentation fault      (core dumped) nix run --no-write-lock-file .#appAsApp
nix-static-aarch64-unknown-linux-musl>     ++ onError
nix-static-aarch64-unknown-linux-musl>     ++ set +x
nix-static-aarch64-unknown-linux-musl>     run.sh: test failed at:
nix-static-aarch64-unknown-linux-musl>       main in run.sh:22
nix-static-aarch64-unknown-linux-musl> make: *** [mk/lib.mk:123: tests/flakes/run.sh.test] Error 139
nix-static-aarch64-unknown-linux-musl> make: *** Waiting for unfinished jobs....
nix-static-aarch64-unknown-linux-musl> ran test tests/flakes/follow-paths.sh... [SKIP]
nix-static-aarch64-unknown-linux-musl> ran test tests/flakes/init.sh... [SKIP]
nix-static-aarch64-unknown-linux-musl> ran test tests/flakes/bundle.sh... [FAIL]
nix-static-aarch64-unknown-linux-musl>     +++ [[ -n '' ]]
nix-static-aarch64-unknown-linux-musl>     +++ trap onError ERR
nix-static-aarch64-unknown-linux-musl>     ++ registry=/build/nix-test/tests/flakes/bundle/registry.json
nix-static-aarch64-unknown-linux-musl>     + cp ../simple.nix ../simple.builder.sh ../config.nix /build/nix-test/tests/flakes/bundle/test-home
nix-static-aarch64-unknown-linux-musl>     + cd /build/nix-test/tests/flakes/bundle/test-home
nix-static-aarch64-unknown-linux-musl>     + cat
nix-static-aarch64-unknown-linux-musl>     + nix build .#
nix-static-aarch64-unknown-linux-musl>     bundle.sh: line 26:  6268 Segmentation fault      (core dumped) nix build .#
nix-static-aarch64-unknown-linux-musl>     ++ onError
nix-static-aarch64-unknown-linux-musl>     ++ set +x
nix-static-aarch64-unknown-linux-musl>     bundle.sh: test failed at:
nix-static-aarch64-unknown-linux-musl>       main in bundle.sh:26
nix-static-aarch64-unknown-linux-musl> make: *** [mk/lib.mk:123: tests/flakes/bundle.sh.test] Error 139
error: builder for '/nix/store/hsr6qxdswfqhjk0n7bg27zzb4q6h7kzl-nix-static-aarch64-unknown-linux-musl-2.11.0.drv' failed with exit code 2

Additional context
[root@rpi:~]# file /nix/store/bwnjbzw2apbszik5spvpazaxfrv655id-nix-static-aarch64-unknown-linux-musl-2.11.0/bin/nix
/nix/store/bwnjbzw2apbszik5spvpazaxfrv655id-nix-static-aarch64-unknown-linux-musl-2.11.0/bin/nix: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /nix/store/bk46s7844fxdhhisjdgy73jm0392myrl-musl-static-aarch64-unknown-linux-musl-1.2.3/lib/ld-musl-aarch64.so.1, not stripped

^ don't know why there is dynamic linked binary
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

https://hydra.nixos.org/build/202403781
Last success: https://hydra.nixos.org/build/183031905
First failure: https://hydra.nixos.org/build/183928906

cc: @eelco @lovesegfault @artturin

builds with latest master
nix build github:nixos/nixpkgs?rev=4c042866938cfef3dfb2b58e21319874cdeb8f4d#nixStatic

Broken again: https://hydra.nixos.org/build/242869526
Somehow the June builds aren't marked as "last success" on Hydra, even though I clearly recall having been able to fetch them from cache back then

Any update here? Seems very important.

Fails with a new error now
env: '/nix/store/k5q8vn5qlf1qppw00p7vzk751crq70vg-nix-static-aarch64-unknown-linux-musl-2.18.7/bin/nix': No such file or directory
https://hydra.nixos.org/build/273110502/nixlog/2
> file /nix/store/k5q8vn5qlf1qppw00p7vzk751crq70vg-nix-static-aarch64-unknown-linux-musl-2.18.7/bin/nix
/nix/store/k5q8vn5qlf1qppw00p7vzk751crq70vg-nix-static-aarch64-unknown-linux-musl-2.18.7/bin/nix: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, with debug_info, not stripped

ldd /nix/store/k5q8vn5qlf1qppw00p7vzk751crq70vg-nix-static-aarch64-unknown-linux-musl-2.18.7/bin/nix
	statically linked

pkgsStatic.hello
file ./result/bin/hello
./result/bin/hello: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, not stripped

ldd ./result/bin/hello
    not a dynamic executable

Same results on cross

Works on Raspberry Pi 4.


Problem with tado component in 0.46.1

Just upgraded to Docker 0.46.1
Getting errors at startup from tado:
2017-06-12 16:08:53 INFO (MainThread) [homeassistant.setup] Setup of domain tado took 0.3 seconds.
2017-06-12 16:08:53 ERROR (MainThread) [homeassistant.setup] Setup failed for tado: Component failed to initialize.

Config:
tado:
  username<EMAIL_ADDRESS>  password: xxxxxxxxxxxxxxxx

Configuration was working fine before upgrade.

it seems to be a tado problem, they must have changed something with their API. even if i use PyTado directly, i get 400 unauthorized errors.

Something to do with oauth:
curl -s "https://my.tado.com/oauth/token" -d client_id=tado-webapp -d grant_type=password -d password=yourPasssword -d scope=home.user -d<EMAIL_ADDRESS>{"error":"invalid_grant","error_description":"A client must have at least one authorized grant type."}

i changed the client_id and added a client_secret (picked up from the webapp) in PyTado, which seemed to have helped for now.
https://github.com/wmalgadey/PyTado/issues/1

I hit the same issue. Thanks for the workaround! I hope it will be merged soon.

I am on it!

https://github.com/wmalgadey/PyTado/issues/1 fixes this. The hass tado component will follow!

👍  Waiting for this - let me know if we can help!


Cleaned up all wx depreciated warnings

Check is failing because it's building against wxWidgets 3.0 instead of 3.1, think we need to bump that requirement up on the build test

maybe we should do some checks for wx version #if wxCHECK_VERSION(3, 1, 1)  StartStyling(0) else ...
similar to
https://github.com/eranif/codelite/issues/2292
https://github.com/eranif/codelite/commit/92ed90e07774dfc8556bee02c66120eed4938a40

In debian/ubuntu we are stuck with wxwidgets 3.0 https://packages.debian.org/source/sid/wxwidgets3.0 so we need to backward compatible patches

Yeah, I'm think we should roll back the problem 'StartStyling' call changes for now. It doesn't hurt anything on wx3.1, just build noise.

just ifdef and maybe later we can build for both 3.1 and 3.0  something similar to https://wiki.codelite.org/pmwiki.php/Main/WxWidgets31Binaries

Seems like wxWidgets is aiming for a new stable 3.2 release by the end of the year, at which point the linux distros should pick it up. Might be better to leave the old 3.0 'StartStyling' calls in place until then, rather than leaving ifdefs to be forgotten about.


Fluid Framework throws a local storage access exception when third party cookies are blocked

There is a usage of local storage in containerRuntime https://github.com/microsoft/FluidFramework/blob/4c5738cd28e243d482069bd5f1e26ec74f1b71a7/packages/runtime/container-runtime/src/containerRuntime.ts#L711
Chromium based browsers will throw an exception when attempting to access local storage when third party cookies are disabled. Full repro steps in Chromium Edge:

Open the settings pane
Search for " lock third-party cookies" in the settings and set it to true
Open a fluid document on office.com

Expected: page should load
Actual: Error dialog, with the following error in the console: Error: Failed to read the 'localStorage' property from 'Window': Access is denied for this document.
We have worked around this issue in other repos by having a utility called safeLocalStorage that puts all local storage access behind a try/catch and ensuring all usages of local storage can function in this case where we are not able to read or write values from local storage.

@arinwt - This is likely a hot bug that we will need in the 0.26 and 0.25 branches. Starting a livesite conversation on Teams