Is Pynetbox compatible with latest version of Netbox docker (3.2.1) ?

Hello,
I would like to know if pynetbox is working with the last update of Netbox-docker 3.2.1. Because I updated my Netbox ans reinstalled pynetbox on it. But it doesn't found the module anymore.
File "/tmp/ansible_netbox_tenant_payload_tue5b_ed/ansible_netbox_tenant_payload.zip/ansible_collections/netbox/netbox/plugins/module_utils/netbox_utils.py", line 25, in <module>
    import pynetbox
ModuleNotFoundError: No module named 'pynetbox'

If someone has an idea.
Best regards.

@aconte31 I'm seeing a similar error. What was your fix?


From private repo

@huypub : Thanks for your contribution! The author, @mahesh-unnikrishnan, has been notified to review your proposed change.


Entsoe transparency API provider support

Many people (in the Nordpool spot areas in particular) have spot price contracts that follow the spot price per hour for their area - similar to what's fetched in the Tibber integration ( #12 ). Usually these contracts have some kind of fixed addition (can be negative, 0 or positive - included already in Tibber data) to the spot price, so this addition could be configurable.
There is a more generic pricing API delivered by entsoe called the "transparency API" where interested parties can download future (day-head) and historical spot prices for each price area (e.g. I'd personally fetch prices for the NO3 price area (link is to price data for jan 8th 2020).
They have an API user guide, and API access is requested after registering an account by sending an email with the subject "Restful API access" to<EMAIL_ADDRESS>with your registered email address in the message body. Token for access is created manually after logging in and having API access granted.
I think the ability of fetching price data from this API based on a selectable (or even dynamic based on positution) price area would be a very valuable addition to TMA. I'll be experimenting a bit with fetching data from entsoe in a small python project and might try my luck at C# if I manage to finish that project.

Hey this sounds great, have you seen the work being done in #27? I wonder if this largely covers the use cases you're interested in here

Ah! No I had not - that would at least cover my specific use case I believe, though AFAIK Nordpool have terms that prohibit scraping / "automated extraction", and a somewhat expensive API license if one decides to play by their rules, whereas Entsoe does not, while also providing price data for areas outside the Nordpool area.

Closing this since https://github.com/MattJeanes/TeslaMateAgile/pull/27 is more than sufficient in my Nordpool case, at least until they break their APIs.


Convert Linkchecker messages from WARN to ERROR

Step1: Create an issue for all the broken links/anchors

Blocked by #4727

Fixed in new link checker set up.


"AttributeError: 'NoneType' object has no attribute 'access_key'" instance profile

Sometimes I get the message "AttributeError: 'NoneType' object has no attribute 'access_key'"
I'm using instance profile to authenticate to AWS and I create the index and can send alerts and all looks fine but once in a while I get

"AttributeError: 'NoneType' object has no attribute 'access_key'"

Elasticsearch version = 6.2
pip==19.0.3
elastalert==0.1.39
awscli==1.16.136
pyOpenSSL==19.0.0
elasticsearch==5.5.3

config.yaml
es_host: endpoint
aws_region: us-east-1
es_port: 443
use_ssl: True
rules_folder: /rules
run_every:
  seconds: 30
buffer_time:
  minutes: 2
writeback_index: elastalert_status
alert_time_limit:
  hours: 3

error
"Traceback (most recent call last):",
"  File \"/usr/local/lib/python2.7/dist-packages/elastalert/elastalert.py\", line 1173, in run_all_rules",
"    num_matches = self.run_rule(rule, endtime, self.starttime)",
"  File \"/usr/local/lib/python2.7/dist-packages/elastalert/elastalert.py\", line 874, in run_rule",
"    if not self.run_query(rule, rule['starttime'], endtime):",
"  File \"/usr/local/lib/python2.7/dist-packages/elastalert/elastalert.py\", line 612, in run_query",
"    data = self.get_hits(rule, start, end, index, scroll)",
"  File \"/usr/local/lib/python2.7/dist-packages/elastalert/elastalert.py\", line 376, in get_hits",
"    **extra_args",
"  File \"/usr/local/lib/python2.7/dist-packages/elasticsearch/client/utils.py\", line 73, in _wrapped",
"    return func(*args, params=params, **kwargs)",
"  File \"/usr/local/lib/python2.7/dist-packages/elasticsearch/client/__init__.py\", line 632, in search",
"    doc_type, '_search'), params=params, body=body)",
"  File \"/usr/local/lib/python2.7/dist-packages/elasticsearch/transport.py\", line 312, in perform_request",
"    status, headers, data = connection.perform_request(method, url, params, body, ignore=ignore, timeout=timeout)",
"  File \"/usr/local/lib/python2.7/dist-packages/elasticsearch/connection/http_requests.py\", line 71, in perform_request",
"    prepared_request = self.session.prepare_request(request)",
"  File \"/usr/local/lib/python2.7/dist-packages/requests/sessions.py\", line 462, in prepare_request",
"    hooks=merge_hooks(request.hooks, self.hooks),",
"  File \"/usr/local/lib/python2.7/dist-packages/requests/models.py\", line 317, in prepare",
"    self.prepare_auth(auth, url)",
"  File \"/usr/local/lib/python2.7/dist-packages/requests/models.py\", line 548, in prepare_auth",
"    r = auth(self)",
"  File \"/usr/local/lib/python2.7/dist-packages/aws_requests_auth/aws_auth.py\", line 76, in __call__",
"    aws_headers = self.get_aws_request_headers_handler(r)",
"  File \"/usr/local/lib/python2.7/dist-packages/aws_requests_auth/aws_auth.py\", line 89, in get_aws_request_headers_handler",
"    aws_access_key=self.aws_access_key,",
"  File \"/usr/local/lib/python2.7/dist-packages/elastalert/auth.py\", line 28, in aws_access_key",
"    return self.refreshable_credential.access_key",
"AttributeError: 'NoneType' object has no attribute 'access_key'"

I'd guess this is the symptom of an error earlier in the process of authenticating via AWS plus bad error handling.
session = boto3.session.Session(profile_name=profile_name, region_name=aws_region)
...
session.get_credentials()

I'd bet get_credentials just returns None if the profile doesn't exist or there's another error, resulting in this error. I'd double check all of your settings. We should definitely make the error more explicit though.


fix k8s files with dot in their name are ignored

Related to #7008

Could you add a test to ensure we don't regress in the future?
If you're not sure how let me know and I can find an example when I'm at my computer (on my phone right now)

Yes, it depends on the type of test you want. An example would be great!

I suspect it's as simple as adding some additional test cases this array?
https://github.com/dependabot/dependabot-core/blob/a4556cf9956dc765930a75b707d8d877d9e5e215/docker/spec/dependabot/docker/file_fetcher_spec.rb#L272-L286

@negrel @mctofu should this be closed now that https://github.com/dependabot/dependabot-core/pull/8862 is merged?
Looking at the diff, it looks like that PR has a superset of what's tested here.

@negrel @mctofu should this be closed now that #8862 is merged?
Looking at the diff, it looks like that PR has a superset of what's tested here.

Looks like it. Thanks for the heads up!

LGTM


Can't install pypi package by version, but success if by path

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

Issue description
pixi fail to resolve pypi dependencies by version, but it will succeed when by path
Additionally, I successfully installed this package by<EMAIL_ADDRESS>
Expected behavior
Can successfully resolve pypi dependencies through version

I think this again has to do with the system-requirements. Could you try with:
[system-requirements]
linux = "2.31"

I personally can not recreate this issue as I can't seem to find the package at all.

Still doesn't work.

Is there a way to get alpha-flow2 for me?

Sorry, this is a private package, but I will continue to investigate. At present, I found that the UV only detects the wheel of py311, and does not detect the wheel of py37, resulting in the inability to install py37.

I've found the reason. The default value for default_glibc_version is 2.17, which causes the largest manylinux not to be less than it. However, the package I installed requires 2.31.
https://github.com/prefix-dev/pixi/blob/66ce6cf69e9b8ff9bc7b427cce00c8b555165171/src/project/virtual_packages.rs#L17-L19
https://github.com/prefix-dev/pixi/blob/66ce6cf69e9b8ff9bc7b427cce00c8b555165171/src/pypi_tags.rs#L19-L53

So I just need to specify system-requirements glibc = "2.31"

I'm sorry for my typo, I did indeed mean libc with my system-requirements example. Thanks for the full answer!


How to remove the path line at the first line of NERDTree?

Since I can see the path via statusline of NERDTree buffer, showing in there too is kind of pointless. How can I remove that first line?

There is no way built into NERDTree to remove the root line, but you can customize the statusline. See :h NERDTreeStatusline.
I've never played around with Vim's conceal feature. Is it able to hide an entire line? That may be an option for you to dig into.

Thanks @PhilRunninger. I think conceal may work, I'll come back if I find proper solution.

It's possible to hide that with this.
augroup nerdtreehidecwd
	autocmd!
	autocmd FileType nerdtree syntax match NERDTreeHideCWD #^[</].*$# conceal
augroup end

Also screenshot:

Awesome! For those who come across this in the future, note that you also need to turn concealment on; it's off by default. An easy way to do that is to add setlocal conceallevel=3 to the autocmd, like so:
augroup nerdtreehidecwd
	autocmd!
	autocmd FileType nerdtree setlocal conceallevel=3 | syntax match NERDTreeHideCWD #^[</].*$# conceal
augroup end

Right, I forgot about that because vim-devicons plugin sets that to 3 automatically but better to yourself.

for those who has cursorline enabled, you also need to set concealcursor to prevent text from displaying  when cursorline and concealed text were on the same line.
augroup nerdtreehidecwd
  autocmd!
  autocmd FileType nerdtree setlocal conceallevel=1
  \ | syntax match NERDTreeHideCWD #^[</].*$# conceal
  \ | setlocal concealcursor=n
augroup end

According to my configuration file It has 2 lines of margin (after It has removed the current path)
Here is the part that is about NERDTree:
let NERDTreeShowHidden=1
let NERDTreeMinimalUI=1
let NERDTreeShowBookmarks=1
" let NERDTreeShowLineNumbers=1
let NERDTreeWinPos="right"
let NERDTreeWinSize=30
let g:NERDTreeDirArrowExpandable = ' '
let g:NERDTreeDirArrowCollapsible = ' '

" Hide the current working directory in NERDTree
augroup nerdtreehidecwd
  autocmd!
  autocmd FileType nerdtree setlocal conceallevel=3
          \ | syntax match NERDTreeHideCWD #^[</].*$# conceal
          \ | setlocal concealcursor=n
augroup end

map <C-a> :NERDTreeToggle<CR>
nnoremap <leader>n :NERDTreeFocus<CR>
nnoremap <C-n> :NERDTree<CR>
nnoremap <C-t> :NERDTreeToggle<CR>
nnoremap <C-f> :NERDTreeFind<CR>

" Exit Vim if NERDTree is the only window remaining in the only tab.
autocmd BufEnter * if tabpagenr('$') == 1 && winnr('$') == 1 && exists('b:NERDTree') && b:NERDTree.isTabTree() | quit | endif


Vite with Quasar

Vite is the way to bundle modern web applications. As https://github.com/cashubtc/cashu.me/pull/33 showed, it is also insanely faster.
However, we should stick with quasar for now as I don't find that there is a compelling reason to rip it out.  This PR implements quasar with vite.
I believe I have tested all flows, and also confirmed that PWA is still working. @callebtc I'm curious, what is your process for deploying? Do you build the quasar app with pwa mode like quasar build -m pwa?

Do you build the quasar app with pwa mode like quasar build -m pwa?

Yes, that's how I do it! We should have a test instance with a BRR mint. I can set that up a mint.
Is there a tool to auto-deploy GitHub branches somewhere so we can test things continuously?

If passed, either this one or #33, will help look in to CI/CD for automated testing.
+1 vitest is always a good choice. Was in the roadmap if #33 passed.


UI: npm test fails with an error

npm test
fails with an error:
`
...BaGet.UI\node_modules\office-ui-fabric-react\lib\Icon.js:1
({"Object.":function(module,exports,require,__dirname,__filename,global,jest){export * from './components/Icon/index';
^^^^^^
SyntaxError: Unexpected token export
1 | import { HtmlRenderer, Parser } from 'commonmark';

2 | import { Icon } from 'office-ui-fabric-react/lib/Icon';
| ^
3 | import * as React from 'react';
4 | import timeago from 'timeago.js';
5 | import LicenseInfo from './LicenseInfo';

at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:403:17)
at Object. (src/DisplayPackage.tsx:2:1)
`
similar to this https://github.com/facebook/jest/issues/2550
I have updated npms to the latest but it does not resolve the issue.

I'd like to work on this if is available.

Go for it! I'm not familiar with testing frontend applications, so I look forward to learning more about it :)

By the way, in case you're interested @sipmann I have lots of wacky ideas for BaGet's frontend that I haven't captured in issues:

Create a npm module to interact with the NuGet protocol, similar to BaGet's BaGet.Protocol library (see these docs).
Create a VS Code extension that provides a UI to interact with a .NET project's NuGet packages, similar to Visual Studio's Package Manager UI. This would leverage BaGet's frontend as much as possible.

Please let me know if you're interested in those ideas! Also happy to hear any ideas you may have too :)

awesome, I'll make a branch and start working on this new features and fill an issue next week to keep track.
I'll fix the tests and code a few ones. React testing isn't my strongest front-end test but I'm sure we can improve what we have here ;)

Question: We'll follow what we have today with the "app.test" and keep the test files side bi side with the testing component?
Or move to a separated folder to keep things clean?

Good question! Do you have a preference between the two approaches? I'm fine with both, but I'd prefer whatever is standard in the React community.

I'll keep the patter that Create React Script use. But I'm stuck with mocking the fetch request. I saw that you have a __BAGET_PLACEHOLDER_API_URL__ on the config.tsx. What's the purpose of this? I'm asking because I have an issue while runing tests. The test require a full URL to mock, not just /v3/search?....

I'll keep the patter that Create React Script use.

Sounds good to me

But I'm stuck with mocking the fetch request. I saw that you have a __BAGET_PLACEHOLDER_API_URL__ on the config.tsx. What's the purpose of this?

Good question! This can be used by two things:

Normally, the BaGet backend serves the BaGet react app, and the react app uses relative URLs. These URLs is broken if you add a prefix to BaGet's URLs (example: /upload would become /my-prefix/upload). We're working on a fix to this problem here, it works by replacing that __BAGET_PLACEHOLDER_API_URL__ value as we serve the BaGet react app.
This lets you run the BaGet react app separately from the BaGet backend. Say you run the backend at URL https://my-baget-api, you can create a deployment step where you replace __BAGET_PLACEHOLDER_API_URL__ with https://my-get-api. This is a hidden feature that I should document :)

I'm asking because I have an issue while runing tests. The test require a full URL to mock, not just /v3/search?....

Hm. Could you use custom environment variables (see this) to override the API URL?


Add School SMK BOEDI LUHUR

@dewabulbul yapenhasbekasi.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


fixed fullalbum being converted to savedalbum

when querying full albums, it wasn't deserizaling it correctly. it was
trying to force it into a saved album, not a full album

Thanks, will release a hotfix when I'm at home! :+1:

Released in 2.7.0


It shows depricated APIs after updating flutter

I have upgrade flutter 3-4days back. After that "Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details." is showing whenever i try to build APK.
I am requesting to kindly solve the problem. Advance thank you.

It could be because Croppie uses the deprecated mousewheel and DOMMouseScroll events rather than standard wheel events. It doesn't really seem like Croppie is still maintained, but I fixed this issue in my simplified fork: https://github.com/theodorejb/cropt


Clustering map

There are clustering support?

There's an open PR which adds marker clustering on iOS here: https://github.com/lelandrichardson/react-native-maps/pull/137

This feature is a must.

Any idea when will this be available? 👍

+1, important feature!

+1

+1

+1

+1

+1

We use https://github.com/mapbox/supercluster in combination with https://github.com/mapbox/geo-viewport to cluster 2000 locations. It works like a charm on iOS and Android.

@klaste Could you please make a simple example?

I want to add clustering feature in my app I am using "react-native-maps" but I don’t have “clusterMarkers” prop in my library which I have installed using "npm install react-native-maps --save” how can I use "react-native-maps" library to add clustering feature to my markers ?

I want to add clustering feature in my app I am using "react-native-maps" but I don’t have “clusterMarkers” prop in my library which I have installed using "npm install react-native-maps” how can I use this library to add clustering feature to my markers.

+1

+1

If you want this feature, I'd suggest try taking over the PR
https://github.com/airbnb/react-native-maps/pull/137

+1

+1

+1

did you find any solution for clustering in Android :  @thiagoterleski  @raphaelsaunier

@klaste how can we it in react native ?

@sahir @Clcll I managed to add clusters to android & ios with supercluster and @i-tu 's gist. Here it is : https://gist.github.com/i-tu/05e79737adfe36935ec869125a686f82
It is easy to do if you wrap your mind around it. The major issue is performance, if you need to display hundreds or thousands of markers you're gonna have to optimize the hell out of it, and this is where it gets really hard.
This is a decent solution, but I think we still need a native implementation.

:+1:

If someone come here and want something working right now, i made an example :
https://github.com/warka0/react-native-cluster-example

+1 native feature

+1 for clustering feature

+1 for clustering feature

+1 for clustering. it is a really must-have!

looks like PR about that just came in #1344

@Jazz747 - it looks promising! I hope we can manage to implement both PR for complete clustering solution!

Any news ?

+1 on this

+1

+1

Please!!!

Pretty please!!

+1 please!!

+1

+1

You can try this. It works for me :) https://github.com/venits/react-native-map-clustering
It is the simplest solution right now.

+1

+1

We are working on a supercluster-based version as well, it is performing (and behaving) correctly. It'll be mounted on a production application in late Dec 2017. Try it out: https://github.com/novalabio/react-native-maps-super-cluster

👾 Much love from team Plural if this would be added 👏

Seeing many issues in implementing clustering natively. https://github.com/novalabio/react-native-maps-super-cluster is the best alternative actually.

+1 for clustering feature

+1

+1

+1

+1

+1

+1

+1

+1

+1

Going to close and lock the issue because there is a "good enough" solution mentioned in the comments and the discussion only goes "+1" which doesn't bring value.
If anybody has a better solution please open a PR.


fix(build.rs): don't fail on error

I'm unable to build this plugin when fail_on_error() is set in the build script, due to vergen claiming that I am not in a valid git worktree:
$ cargo build --release
...
error: failed to run custom build command for `cloud-plugin v0.1.2 (/Users/vdice/go/src/github.com/fermyon/cloud-plugin)`

Caused by:
  process didn't exit successfully: `/Users/vdice/go/src/github.com/fermyon/cloud-plugin/target/release/build/cloud-plugin-56e76e8961f4ea6a/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at 'failed to extract build information: not within a suitable 'git' worktree!', build.rs:7:10
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

I noticed we've also removed the fail_on_error() toggle in Spin (https://github.com/fermyon/spin/pull/1590), so I propose we do the same here.

(I've since fixed my machine such that the error no longer occurs; closing.)


Add the progress flag to support print the sync progress

Codecov Report

Merging #41 (92a4eaa) into main (bf70369) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #41   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           40        40
  Lines         1284      1284
=========================================
  Hits          1284      1284

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[$1000]  Dev: Web - Console log on clicking IOU preview component

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open a tab where account A is signed in
Request a money from account B
Open a tab where account B is signed in
Open chat between account B & A
Click on the IOU preview component

Expected Result:
There should be no console log error
Actual Result:
Console log error displayed [Failed prop type: Invalid prop personalDetails.accountID of type number supplied to IOUPreview, expected object.]
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: Dev 1.3.45-8
Reproducible in staging?: no
Reproducible in production?: no
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/e2fea8c2-9a7e-4108-a9a7-6d42cfc5cf8b
Expensify/Expensify Issue URL:
Issue reported by: @Natnael-guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690377355421559
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01f09e3655eab4d213
Upwork Job ID:<PHONE_NUMBER>325656064
Last Price Increase: 2023-08-08

heya @deetergp - since this is happening on Dev, we will need an engineer to help with the reproduction steps. thank you!

I walked through the reproduction steps and can confirm that I am seeing that same console error. It does look as though it is something an external contributor can work on.

Proposal from upwork
One possible source of the error is in the proptypes declaration in IOUPreview.js, specifically the personal details key found in lines 83-88. Only one key is declared as belonging to the object, displayName. The first thing I would do is add accountID to this declaration and test to see if this solves the problem. Whether it does or doesn't, the next move would be to find the full JSON object that is being passed and create an interface for it to ensure safety. If this theory does not pan out, my next move would be to add logs throughout function ReportActionItemSingle in ReportActionItemSingle.js, lines 73-183, and function MoneyRequestAction in MoneyRequestAction.js, lines 87-157, to determine the values that are available and set throughout, and compare these with the values expected by IOUPreview. Generally, the solution will be to identify whether the issue lies in inheritance (something goes wrong with the data en route to IOUPreview) or declaration (IOUPreview's expected props are inaccurate), and from there implementing the most efficient type safeguards.

Contributor details
Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01ee97b9ff5ee5d693

Proposal
Please re-state the problem that we are trying to solve in this issue.
Console log error displayed [Failed prop type: Invalid prop parentReportID of type number supplied to ParentNavigationSubtitle, expected string.]
What is the root cause of that problem?
This issue is caused by backend returning parentReportID of type Number instead of string
What changes do you think we should make in order to solve the problem?

we could just use toString() to convert parentReportID to string as we already do here
https://github.com/Expensify/App/blob/f3ece51bd5b9c2f8dc5e3be94da134a8af318cbe/src/pages/home/HeaderView.js#L193-L197
What alternative solutions did you explore? (Optional)
First of all various values of reportID and parentReportID should be consistent in backend replies - number or string. Then we could apply changes all over the codebase to change ReportIDs to type number.

@alexxxwork Can you trace back which API calls are returning reportID as numbers instead of strings?

1.OpenReport (same for ReconnectToReport or ReconnectApp):
1.1 "parentReportID" as Number when you have an element of report with parentReportID (IOU) or create a thread
1.2. "childReportID" when you have a thread for a message in your report
1.3. "IOUReportID" when you have an IOU in report
2.RequestMoney return "reportID", "chatReportID", "childReportID" and "IOUReportID" as numbers
3. CreateTask returns "taskReportID", "childReportID"  as numbers
4. SplitBillAndOpenReport returns "IOUReportID" in "originalMessage" as number and in other json object as string.

@deetergp @Nodebrute The problem with ReportIDs type exists for a while, I think that parentReportID isn't included in reportPropTypes intentionally to bypass propTypes problem

hiya @conorpendergrast - i am OOO until ~Aug 20. it looks like we are still deciding between two proposals:

https://github.com/Expensify/App/issues/23645#issuecomment-1663388322
https://github.com/Expensify/App/issues/23645#issuecomment-1664599887

We're awaiting @situchan to review those and hire a contributor to the job 👍

@situchan Bump on the proposal review please

@Natnael-Guchima I am not able to reproduce original console error but instead seeing this:

Can you please confirm?

@situchan Yes, I am seeing a different console log error as well.

Console log error displayed [Failed prop type: Invalid prop personalDetails.accountID of type number supplied to IOUPreview, expected object.]

So this error is gone, right?

Yes, it seems like it.

@situchan I think first error is fixed. ParentReportID is not stored as a number anymore.

still reproducible to me

@situchan yes, it's reproducible. Link to related thread https://expensify.slack.com/archives/C01GTK53T8Q/p1691167905181059. I think they have created a new issue to fix it from backend.

Great discussion! As they're trying to fix the root cause in backend, I think we can leave that console error as is now.
Or if it's still annoying for devs meanwhile, we can apply workaround of String(parentReportID) as it's already in our codebase.
Btw the main fix here is to fix all hidden bugs where propType is wrongly defined.
@Nodebrute's proposal looks good to me.
cc: @deetergp
🎀 👀 🎀 C+ reviewed

@situchan I am able to reproduce the issue when User A & User B request money from each other & when there are a total of two standing IOUs.

https://github.com/Expensify/App/assets/57330233/3de49385-2bdf-4671-bc1f-5009888b81e4

@Nodebrute nice catch! Indeed, wrong data is stored in Onyx. Can you please update your proposal to cover this?

I think we can safely remove this optimistic data because "I am going to pay" - this means I already have this payee in my contacts list. But let's make sure it doesn't cause any issue while testing offline.
@deetergp now we found the exact root cause of this issue.
Proposal that I approved is to fix propTypes errors.
Original issue is wrong optimistic personalDetails data when pay money.
So they have different root causes.
Do you agree fixing both issues together here?

@situchan In the event that the same user makes multiple payments, we store their information in Onyx each time. This could lead to the creation of duplicate entries.

It's needed to support offline payment. But if they are already in ONYXKEYS.PERSONAL_DETAILS_LIST, no need to create another optimistic data.
Especially when request money to new user I don't know.

I think we can safely remove this optimistic data because "I am going to pay" - this means I already have this payee in my contacts list. But let's make sure it doesn't cause any issue while testing offline.

That's what I suggested

Do you agree fixing both issues together here?

Yes, please! Let's do both.

@deetergp ok, let's assign @Nodebrute as recommended here

@Nodebrute @situchan I think regression from this as still seeing the console warnings
https://github.com/Expensify/App/assets/14358475/6cead4a8-db5d-451e-af16-2577f5e641e2

@Pujan92 All good after logout and login?

@maddylewis Ah, you're back! I'll unassign myself, assign me again if you need any more help!

@Pujan92 All good after logout and login?

Yes @conorpendergrast, not seeing the warnings now.

Fantastic, thanks for confirming!

moving to daily since payment is coming up this week

Payments

[ ] Reporting bonus: @Natnael-Guchima ($250 paid via Upwork)
[ ] Contributor: @Nodebrute ($1000 paid via Upwork)
[ ] C+: @situchan  ($1000 paid via Upwork)

Contributor hired on August 10
PR merged on August 14 - https://github.com/Expensify/App/pull/24386

@situchan - will you lmk if any of this checklist needs to be reviewed? thanks! https://github.com/Expensify/App/issues/23645#issuecomment-1681486486

@maddylewis this is eligible for bonus. You didn't calculate weekend

The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/20679
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/20679/files#r1304805631
Console error is already in checklist. No need regression test

everyone is paid


Increase dialogue text size on mobile devices

As discussed in #5, the text in the "display" box (the lake), is too small for viewing on mobile devices.
Adjust the font size, or modify the word-wrapping in speak.js to incorporate for larger text sizes.

Resolved via #7.


add panels for peer pending time and apply wait time.

Add 2 panels: peer pending time and apply wait time.

@siddontang @BusyJay @overvenus PTAL thanks.


is there a way to change watches dynamically?

Type of question
Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?
Question
What did you do?
developed an ansible operator using the sdk.
What did you expect to see?
all is working
What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).
Environment

operator-sdk version:
0.16.0
insert release or Git SHA here

operator-sdk version: "v0.16.0", commit: "55f1446c5f472e7d8e308dcdf36d0d7fc44fc4fd", go version: "go1.13.8 linux/amd64"

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.6+a8d983c", GitCommit:"a8d983c", GitTreeState:"clean", BuildDate:"2019-12-23T12:16:26Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
Regular

Additional context
I'm trying to develop an operator that reacts to different types dynamically. f
or that, it could help if watches can be changed dynamically. e.g. having the configuration in a configmap instead of in watches.yaml file.
any other way to modify it dynamically could be helpful.

/cc @fabianvf

@fabianvf hi Fabian,
still waiting for your answer per this one..

@nirrozenbaum
Have you found a solution for that?
I would also be interested whether there is a good solution to do that for a Golang operator

@nirrozenbaum
Have you found a solution for that?
I would also be interested whether there is a good solution to do that for a Golang operator

nope, unfortunately no.

nope, unfortunately no.

Terribly sorry, missed those pings. I do not think there is a way to dynamically update the watches for a running ansible operator currently. Some users in the past have used a watches.yaml stored in a configmap and mounted that into the operator deployment, so when the content of the watches change the operator is redeployed

Terribly sorry, missed those pings. I do not think there is a way to dynamically update the watches for a running ansible operator currently. Some users in the past have used a watches.yaml stored in a configmap and mounted that into the operator deployment, so when the content of the watches change the operator is redeployed

@fabianvf thanks for your comments.
do you know if this option is possible in go operator?

@fabianvf thanks for your comments.
do you know if this option is possible in go operator?


Persistent indices across updates

Rebuilding Indices is one of the performance bottleneck of relational e-matching. Right now, the indices are built from scratch in each iteration. A more efficient approach may be to keep the indices across iterations and keep them updated as the database changes.

By the same token, could canonicalization also be incremental? If we stored "all-eid" relations in a trie that listed each column (with the eclass id at the leaf), then the same incremental merging operation performed on indices could also be used to merge eclasses, with new collisions at the leaves triggering an additional merge.

Closing for now, as we've decided to table this.


Refactor Soldity types in view call library to be defined in .sol files instead of using the sol! macro

One rough edge in the view call library is that the BlockCommitment type is defined only in the Rust source code through a sol! macro. As a result, it is difficult to use in Solidity smart contracts to build upon it. Moving BlockCommitment and any other Solidity types into contracts that can be imported into smart contract projects would improve the developer experience.

To give some context, this is the use case we want to address:
It's about the BlockCommitment structure (defined here)
The guest is committing to a block commitment (obviously) as well as other journal data. So they have defined their own (solidity) struct that contains a block commitment + his other data.
The trouble, of course, is that BlockCommitment is defined within a sol! { ... } block. So when they went to define their own output struct (again in a sol! { ... }) macro, with a field of type BlockCommitment, the (sol) macro complained that it couldn't find the (solidity) definition of BlockCommitment.

Problem description
The function block_commitment() returns the following Solidity struct:
struct BlockCommitment {
    bytes32 blockHash;
    uint blockNumber;
}

Calling .abi_encode() returns the bytes that can then be used to verify the commitment on-chain.
However, when more data is committed to the journal, it gets more complicated. When the output is defined in the following way:
sol! {
  struct BlockCommitment {
      bytes32 blockHash;
      uint256 blockNumber;
  }

  struct Journal {
      BlockCommitment commitment;
      bytes data;
  }
}

The BlockCommitment is a different rust-type and cannot be assigned.
⚠ Even putting BlockCommitment inside a .sol file does not fix this issue.
Solution
Instead of redefining the BlockCommitment, the existing type should be reused.
use risc0_steel::BlockCommitment;

sol! {
    struct Journal {
        BlockCommitment commitment;
        bytes data;
    }
}

Open questions:

How are we going to showcase this design?
We could still put the BlockCommitment into an interface sol file. Would that simplify the usage in Solidity?


BLAKE2s wrapper ignoring the second (important) 'key' parameter

The original blake2s library accepts two params, a digest length and a key which allows for keyed hashes.
https://github.com/dchest/blake2s-js
new BLAKE2s(digestLength, key)

Creates a new instance of BLAKE2s hash with the given length of digest (default and maximum 32) and an optional secret key (a Uint8Array or Array of bytes).

The miniLockLib wrapper around blake2s only passes along the length and ignores any 'key' passed into the constructor so the hash that gets output is always the same when there should be two different outputs (with key and without).
Changing this line:
https://github.com/45678/miniLockLib/blob/master/library/BLAKE2s.coffee#L6
to:
OriginalBLAKE2s.call(this, params.length, params.key)

seems to fix the issue for me.  There don't seem to be any tests for the blake2s wrapper but the rest of the miniLockLib test suite seems to pass with this change.
Here is an example after the change:
# no key
(new miniLockLib.BLAKE2s({length: 10})).update([1,2,3]).hexDigest();
"183e4664afbe4377d3b5"

# key
(new miniLockLib.BLAKE2s({length: 10, key: [4,5,6]})).update([1,2,3]).hexDigest();
"617ac02bf3f998531c61"

Also, as far as I can tell the blake2s wrapper params are undocumented in miniLockLib. It would be helpful if your excellent homepage contained a usage example for each of the exported modules when there is an API change from the native lib.
cc:  @dchest

Thank you for investigating this issue @grempe. i have applied your suggested change to the master branch:
https://github.com/45678/miniLockLib/commit/f12ae075900c91f562681ce67d6cc4d8c2d7d40d
i will leave this issue open to remind myself to document the BLAKE2s wrapper on the website soon.

Documentation for the BLAKE2s wrapper has been updated:
https://45678.github.io/miniLockLib/#BLAKE2s
Mucho thanks for the suggestion @grempe.


Add a -z flag to suppress datasets with no activity

Fixes #12
This feels best combined with -s name, as the multi-line naming gets a bit too dynamic.

Thoughts on making -s name default in this mode?

Hmmm, there appears to have been a bug in this PR, if you tested after I merged all the others today:
me@banshee:/usr/local/bin$ sudo ioztat
  File "/usr/local/bin/ioztat", line 68
    header, _fieldnames, *fields = [line.split() for line in f]
                         ^
SyntaxError: invalid syntax

well, it doesn't appear to have been this one--I'm seeing the breakage after reverting this as well.

@Freaky I don't think I have much of an opinion about using -s name by default when -z is on. That seems fine to me. I suppose the question is whether people who want to opt out can specify a -s argument that brings back the default sorting?
Assuming the answer to the latter is "yes" I'd say you can go ahead and change the default sort when -z is on.


Clear thumbnails after uploaded

Hi,
i try using reset() method to clear thumbnail list after all uploaded in onAllComplete event but has not cleared.
My code:
this.uploader.on('onAllComplete', () => {             this.uploader.methods.reset()           });

i fixed this problem witt set submitedfields = []


Remote API: /container/{bad id}/start returns 502

Output of docker version:
Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:04:48 2016
 OS/Arch:      darwin/amd64
 Experimental: true

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:04:48 2016
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 81
Server Version: 1.12.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 95
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay host bridge null
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.16-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.954 GiB
Name: moby
ID: TDFT:QMHZ:QWMG:ZKNS:3BVF:GV75:F7HR:RL6D:GUE6:I3JC:SENA:CH6Y
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 18
 Goroutines: 28
 System Time: 2016-08-11T15:00:55.060722386Z
 EventsListeners: 1
No Proxy: *.local, 169.254/16
Username: xnat
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

Steps to reproduce the issue:

Make up a container ID that doesn't exist. For example, 1.
Using the remote API, POST to /containers/{some id}/start

Describe the results you received:
HTTP/1.1 502 Bad Gateway
Describe the results you expected:
HTTP/1.1 404 Not Found

This looks specifically like an issue with docker4mac.
404 is correctly returned by the docker daemon.
ping @justincormack

Thanks, have filed an internal issue https://github.com/docker/pinata/issues/4825 looks like our minimal proxy not behaving correctly. Hoping we can remove it soon, but will fix anyway.

Just got around to checking on this (months late). It was fixed sometime between 1.12.0 and 17.03.0-ce.

thanks @johnflavin


[BUG] GetAccessTokenAsync is very slow when running locally

Describe the bug
I used GetAccessTokenAsync code to test MSI locally. The code was running for more than 1 minute before it returned a valid token. I tested it multiple times, the behavior was consistent.
Exception or Stack Trace
Add the exception log and stack trace if available
To Reproduce
Try running the code locally.
Code Snippet
namespace test
{
    class Program
    {
        static async Task Main(string[] args)
        {
            var stopwatch = new Stopwatch();
            stopwatch.Start();

            var azureServiceTokenProvider = new AzureServiceTokenProvider();
            var token = await azureServiceTokenProvider.GetAccessTokenAsync("https://management.azure.com/");

            stopwatch.Stop();
            Console.WriteLine(stopwatch.Elapsed);
        }
    }
}

Expected behavior
The method returns code in a reasonable time (e.g. a few seconds).
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):

OS: [e.g. iOS] Mac OS 10.13.6
IDE : [e.g. IntelliJ] VS code, tested locally using dotnet run.
Version of the Library used: Microsoft.Azure.Services.AppAuthentication, 1.0.3
Dotnet version: 2.2.103
Azure CLI version: 2.0.58

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[X] Bug Description Added
[X] Repro Steps Added
[X] Setup information Added

Thank you for opening this issue! We are routing it to the appropriate team for follow up.
cc: @shahabhijeet

@omerlh Can you elaborate more on your repro steps/scenario? You said you are running locally, but MSI is only possible when deployed to an Azure VM or App Service with MSI enabled.
Can you confirm you are seeing this issue on a local machine? If that's the case, the cause of the delay is not the MSI token retrieval logic, but possibly another of AppAuth's authentication methods (Azure CLI, Visual Studio, or Windows integrated auth).

Yes, this is when running locally. I guess it's trying to use Azure CLI credentials.

Have you tried providing a connectionString to AzureServiceTokenProvider?
new AzureServiceTokenProvider("RunAs=Developer; DeveloperTool=VisualStudio")

We experienced long delays as well when running locally.
If I remember correct AzureServiceTokenProvider will first try authenticating using AzureCLI and MSI before trying VisualStudio.

I don't think this will work on Mac:
Unhandled Exception: Microsoft.Azure.Services.AppAuthentication.AzureServiceTokenProviderException: Parameters: Connection String: RunAs=Developer; DeveloperTool=VisualStudio, Resource: https://management.azure.com/, Authority: . Exception Message: Tried to get token using Visual Studio. Access token could not be acquired. Environment variable LOCALAPPDATA not set.
   at Microsoft.Azure.Services.AppAuthentication.AzureServiceTokenProvider.GetAccessTokenAsyncImpl(String authority, String resource, String scope)
   at Microsoft.Azure.Services.AppAuthentication.AzureServiceTokenProvider.GetAccessTokenAsync(String resource, String tenantId)
   at test.Program.Main(String[] args) in /Users/omerl/dev/test/Program.cs:line 40
   at test.Program.<Main>(String[] args)

Do you know what is the connection string for Azure CLI?

Do you know what is the connection string for Azure CLI?

"RunAs=Developer; DeveloperTool=AzureCli"
https://docs.microsoft.com/en-us/azure/key-vault/service-to-service-authentication#connection-string-support

Thank you, this indeed solved the issue - may be worth documenting it?

@omerlh , is the issue resolved? If yes I'll close it, thanks.

Yes please.


BUG: Crash when "existing appcast url" has an empty file

probably also crashes if the url doesn't exist.
In either scenario, it should just start from scratch.

fixed in cf27d7fa06d436479a948258294745b1d63da4f3


Hi， is that support Chinese drama background music seperate?

Hi， is that support Chinese drama background music seperate?

Not just Chinese dramas

Hi, sorry not sure what this question means?
You can separate whatever you want - you provide the input audio, the code doesn't care what the content of your audio is, it's just running it through inference with various machine learning models.


docs(policies) fix logging format

@jakubdyszkiewicz any specific reason for the new formatting?

@subnetmarco yes, take a look at this https://github.com/Kong/kuma/pull/566


Merge Development->Master (led funcs, nanopb)

Add the led functions and nanopb to master branch

Review again? Should be more in line with coding style now

Changed

Great!


Update go.yml

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f191a91). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   36.58%
=========================================
  Files             ?        3
  Lines             ?       41
  Branches          ?        0
=========================================
  Hits              ?       15
  Misses            ?       26
  Partials          ?        0

Continue to review full report at Codecov.

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


Incoporate OpenAPI type mapping changes

According to the constraint support, https://github.com/ballerina-platform/ballerina-standard-library/issues/2850 need to provide support for the below type validation

[ ] Primitive type: Integer : (ballerina mapping) int

format
keywords
Ballerina Mapping

int32

int

int64

int

minimum
@constraint:Int {   minValue: <value>}

maximum
@constraint:Int {   maxValue: <value>}

exclusiveMinimum
@constraint:Int {   minValueExclusive: <value>}

exclusiveMaximum
@constraint:Int {   maxValueExclusive: <value>}

multipleOf

[ ] Primitive type: float (ballerina mapping) : float

format
keywords
Ballerina Mapping

minimum
@constraint:Float {   minValue: <value>}

maximum
@constraint:Float {   maxValue: <value>}

exclusiveMinimum
@constraint:Float {   minValueExclusive: <value>}

exclusiveMaximum
@constraint:Float {   maxValueExclusive: <value>}

multipleOf

[ ] Primitive type: Double (ballerina mapping) : decimal

format
keywords
Ballerina Mapping

minimum
@constraint:Number {   minValue: <value>}

maximum
@constraint:Number {   maxValue: <value>}

exclusiveMinimum
@constraint:Number {   minValueExclusive: <value>}

exclusiveMaximum
@constraint:Number {   maxValueExclusive: <value>}

multipleOf

[x] Primitive type: String (ballerina mapping) : string

format
keywords
Ballerina Mapping

minLength
@constraint:String {   minLength: <value>}

maxLength
@constraint:Stringl {   maxLength: <value>}

(not support from OpenAPI)
length
@constraint:Stringl {   length: <value>}

pattern

[ ] Array type: String (ballerina mapping) : array

format
keywords
Ballerina Mapping

minItems
@constraint:Array {   minLength: <value>}

maxItems
@constraint:Array {   maxLength: <value>}

uniqueItems

[ ] Object type: object schema (ballerina mapping) : record type

format
keywords
Ballerina Mapping

minProperties

maxProperties

[ ] Apply this for object schema to record type mapping
[ ] Apply these constraints for functions parameters both remote, resource in service and client generation (ex: query parameters)

@shafreenAnfar, @ldclakmal Could you please verify this constraint mapping in OpenAPI to Ballerina? 🙂

@lnash94 As explained in the comment [1] of the Constraint package proposal, during the 1st phase we support a subset of the proposed constraints.
As a summary, only following annotations will be there:

Annotation
Compatibility type

@constraint:Int
int

@constraint:float
float

@constraint:Number
int|float|decimal

@constraint:String
string

@constraint:Array
any[]

The @constraint:Int, @constraint:Float and @constraint:Number annotations will have the minValue, maxValue, minValueExclusive and maxValueExclusive constraints.
The @constraint:String and @constraint:Array annotation will have the length, minLength and maxLength constraints.
[1] https://github.com/ballerina-platform/ballerina-standard-library/issues/2850#issuecomment-1109512766

Please find the below usage details of the validation attribute for multipleOf , uniqueItems

Validation Attributes
Percentage out of OpenAPI files (out of 349)

multipleOf (Integer)
1 -> 0.3%

uniqueItems (Arrays)
14 -> 4.01%

Since these are not often used, we are pleased to add these attributes to OpenAPI tool once it, if are available in the constraint module?
@ldclakmal could you please provide some input for this?

The main purpose of adding the constraint validation to the OpenAPI tool is to validate the Return/Response and Request Payload in the generated ballerina resources APIs.

Here in the Client generation by default, we suppose not to enable constraint validation by assuming API providers have validated their APIs on their side. We will provide an option (--enable-client-validation) to enable constraint validation for the user if they are willing to validate the request and respond before sending an API call.

But in the Service skeleton generation for default behaviours, we are supposed to add the ballerina constraint to validate the request and response payload by calling the method validate in the module constraint. Because adding constraint support to generate ballerina types will add value to service generation rather than the client. Then we make it a default behaviour to validate.

We would like to have an idea about the stability of adding the ballerina constraint validation before marking this validation as the default in-service generation side. ex: what are the limitations we will encounter using constrain validation.
After adding constraint for the service skeleton.
import ballerina/http;
import ballerina/constraint;

listener http:Listener ep0 = new (9090, config = {host: "localhost"});
service / on ep0 {
    resource function get games(@http:Payload Team body) returns error? {
          body = check constraint:validate(body);
          // business logic
    }
}

@ldclakmal  @shafreenAnfar appreciate your thought for the further implementation of OpenAPI tool 🙂

We had a meeting on this and finalized the way forward. @lnash94 shall we add the meeting notes here.

Attendees: @hevayo , @shafreenAnfar , @ldclakmal , @keizer619 , @lnash94
Meeting Notes:

Regarding the Request and Response constraint validation:  Request and Response payload validation are handled through the http module. Then it won't be explicitly handled by code generation.
Array item constrains validation with array constraint validation:  Array item validation is handled via defining another item type through the OpenAPI tool.
Please find the attached doc for the list of issue and the meeting notes : https://docs.google.com/document/d/1RwNrZpgU9A7t9gpR_JRTzrmlNWsesC66Od2t_-hhZ3I/edit#


[enhancement] Compatibility With Scholar

I don't know if it's possible, but scholar is a great mod for letting you edit books and has the ability to show two pages at a time. This would add to the immersion of creating a dictionary in game using writable books. I've noticed that the scholar UI opens every time you cast a spell from a written book as well.

I am currently working on features which should bridge this gap, though due to availability this will likely not manifest as Scholar compat. As such, I'll be closing this issue.
That being said, thank you for the suggestion!


Control over overwriting values in the identity object

Adds new property overwrite: bool (default: false) to the extended properties.
The default set to false is a breaking change, since overwriting is right now the only option.
Verification steps
make local-setup
kubectl port-forward deployment/envoy 8000:8000 2>&1 >/dev/null &

Create the AuthConfig:
kubectl apply -f -<<EOF
apiVersion: authorino.kuadrant.io/v1beta1
kind: AuthConfig
metadata:
  name: talker-api-protection
spec:
  hosts:
  - talker-api-authorino.<IP_ADDRESS>.nip.io
  identity:
  - name: plain
    plain:
      authJSON: context.request.http.headers.x-user|@fromstr
    extendedProperties:
    - name: name
      value: bar
      overwrite: false
    - name: age
      value: 35
      overwrite: true
    - name: groups
      value: ["admin"]
  response:
  - name: x-auth-data
    json:
      properties:
      - name: identity
        valueFrom:
          authJSON: auth.identity
EOF

Send a request:
curl -H 'x-user: {"name":"foo","age":30}' http://talker-api-authorino.<IP_ADDRESS>.nip.io:8000 -i
# …
#     "X-Auth-Data": "{\"identity\":{\"age\":35,\"groups\":[\"admin\"],\"name\":\"foo\"}}",

Closes #395.

Verification steps working as expected


Trying to remove a volume from a different node multiple times leaves volume in un-usable state

I ran into this issue when trying to test the retry logic for volumes.
Node 1
docker volume create --driver=vmdk --name=storage -o size=100MB
docker run --rm -it -v storage:/vol busybox

Node 2
docker volume rm storage
docker volume rm storage

The first time I get the following logs
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] lib.vmci_reply: VMCI replied with errcode 0
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] Released lock: storage
07/13/16 23:11:02 2710275 [MainThread] [DEBUG  ] lib.vmci_get_one_op returns 7, buffer '{"cmd":"remove","details":{"Name":"storage"}}'
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] LockManager.get_lock: new lock: storage, <thread.lock object at 0xffe9e7c0>
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] LockManager existing locks in store: [u'storage']
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] Trying to aquire lock: storage
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] Aquired lock: storage
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] get_datastores: [('datastore1', '57302fae-961b9cf9-2e49-000c29acb565', '/vmfs/volumes/57302fae-961b9cf9-2e49-000c29acb565/dockvols'), ('vsanDatastore', 'vsan:5201dd577fe793bd-112186a6c2b42e0c', '/vmfs/volumes/vsan:5201dd577fe793bd-112186a6c2b42e0c/dockvols')]
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] get_datastore_name: path=vsan:5201dd577fe793bd-112186a6c2b42e0c name=['vsanDatastore']
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] Authorize: vm_uuid=564d6f23-eabb-1b63-c79d-2086cca704d5
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] Authorize: datastore=vsanDatastore
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] Authorize: cmd=remove
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] Authorize: opt={}
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] get tenant vm_uuid=564d6f23-eabb-1b63-c79d-2086cca704d5 tenant_id=4acd19ee-1ed6-4716-bcda-c8637c9658f2
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] get_privileges tenant_uuid=4acd19ee-1ed6-4716-bcda-c8637c9658f2 datastore=vsanDatastore
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] delete_volume=1
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [INFO   ] cmd remove with opts {} on tenant_uuid 4acd19ee-1ed6-4716-bcda-c8637c9658f2 datastore vsanDatastore is allowed to execute
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] Found /vmfs/volumes/vsanDatastore/dockvols/tenant1, returning
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] executeRequest tenant1 /vmfs/volumes/vsanDatastore/dockvols/tenant1
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [INFO   ] *** removeVMDK: /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk
07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [DEBUG  ] Running cmd /sbin/vmkfstools -U  /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk

07/13/16 23:11:02 2710275 [photon.vsan.2-storage] [INFO   ] *** removeVMDK: /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk, coudn't lock volume for removal. Retrying...
07/13/16 23:11:03 2710275 [photon.vsan.2-storage] [DEBUG  ] Running cmd /sbin/vmkfstools -U  /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk
07/13/16 23:11:04 2710275 [photon.vsan.2-storage] [INFO   ] *** removeVMDK: /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk, coudn't lock volume for removal. Retrying...
07/13/16 23:11:05 2710275 [photon.vsan.2-storage] [DEBUG  ] Running cmd /sbin/vmkfstools -U  /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk
07/13/16 23:11:05 2710275 [photon.vsan.2-storage] [INFO   ] *** removeVMDK: /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk, coudn't lock volume for removal. Retrying...
07/13/16 23:11:06 2710275 [photon.vsan.2-storage] [DEBUG  ] Running cmd /sbin/vmkfstools -U  /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk
07/13/16 23:11:06 2710275 [photon.vsan.2-storage] [INFO   ] *** removeVMDK: /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk, coudn't lock volume for removal. Retrying...
07/13/16 23:11:07 2710275 [photon.vsan.2-storage] [DEBUG  ] Running cmd /sbin/vmkfstools -U  /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk
07/13/16 23:11:07 2710275 [photon.vsan.2-storage] [INFO   ] *** removeVMDK: /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk, coudn't lock volume for removal. Retrying...
07/13/16 23:11:08 2710275 [photon.vsan.2-storage] [DEBUG  ] Running cmd /sbin/vmkfstools -U  /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk
07/13/16 23:11:08 2710275 [photon.vsan.2-storage] [INFO   ] executeRequest 'remove' completed with ret={u'Error': u'Failed to remove /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk. Failed to delete virtual disk: Failed to lock the file (16392).\n'}
07/13/16 23:11:08 2710275 [photon.vsan.2-storage] [DEBUG  ] lib.vmci_reply: VMCI replied with errcode 0
07/13/16 23:11:08 2710275 [photon.vsan.2-storage] [DEBUG  ] Released lock: storage

After that each retry gives the following result
07/13/16 23:11:22 2710275 [MainThread] [DEBUG  ] lib.vmci_get_one_op returns 4, buffer '{"cmd":"get","details":{"Name":"storage"}}'
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] LockManager.get_lock: new lock: storage, <thread.lock object at 0xffe9e810>
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] LockManager existing locks in store: [u'storage']
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Trying to aquire lock: storage
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Aquired lock: storage
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] get_datastores: [('datastore1', '57302fae-961b9cf9-2e49-000c29acb565', '/vmfs/volumes/57302fae-961b9cf9-2e49-000c29acb565/dockvols'), ('vsanDatastore', 'vsan:5201dd577fe793bd-112186a6c2b42e0c', '/vmfs/volumes/vsan:5201dd577fe793bd-112186a6c2b42e0c/dockvols')]
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] get_datastore_name: path=vsan:5201dd577fe793bd-112186a6c2b42e0c name=['vsanDatastore']
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Authorize: vm_uuid=564d6f23-eabb-1b63-c79d-2086cca704d5
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Authorize: datastore=vsanDatastore
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Authorize: cmd=get
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Authorize: opt={}
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] get tenant vm_uuid=564d6f23-eabb-1b63-c79d-2086cca704d5 tenant_id=4acd19ee-1ed6-4716-bcda-c8637c9658f2
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] get_privileges tenant_uuid=4acd19ee-1ed6-4716-bcda-c8637c9658f2 datastore=vsanDatastore
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] mount_volume=1
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [INFO   ] cmd get with opts {} on tenant_uuid 4acd19ee-1ed6-4716-bcda-c8637c9658f2 datastore vsanDatastore is allowed to execute
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Found /vmfs/volumes/vsanDatastore/dockvols/tenant1, returning
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] executeRequest tenant1 /vmfs/volumes/vsanDatastore/dockvols/tenant1
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Trying to acquire lock: <_RLock owner=None count=0> @ 0x3433acec, caller: load, args: (u'/vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk',) {}
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Aquired lock: <_RLock owner='photon.vsan.2-storage' count=1> @ 0x3433acec, caller: load, args: (u'/vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk',) {}
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [ERROR  ] Failed to access /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage-579734cb32c89965.vmfd
Traceback (most recent call last):
  File "/usr/lib/vmware/vmdkops/Python/kvESX.py", line 266, in load
    with open(meta_file, "r") as fh:
IOError: [Errno 2] No such file or directory: '/vmfs/volumes/vsanDatastore/dockvols/tenant1/storage-579734cb32c89965.vmfd'
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Trying to acquire lock: <_RLock owner=None count=0> @ 0x3433acec, caller: get_info, args: (u'/vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk',) {}
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Aquired lock: <_RLock owner='photon.vsan.2-storage' count=1> @ 0x3433acec, caller: get_info, args: (u'/vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk',) {}
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Trying to acquire lock: <_RLock owner='photon.vsan.2-storage' count=1> @ 0x3433acec, caller: vol_open_path, args: (u'/vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk', 524289) {}
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Aquired lock: <_RLock owner='photon.vsan.2-storage' count=2> @ 0x3433acec, caller: vol_open_path, args: (u'/vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk', 524289) {}
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [ERROR  ] Failed to get disk details for /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk ('NoneType' object has no attribute '__getitem__')
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [INFO   ] executeRequest 'get' completed with ret={u'Error': u"Failed to get disk details for /vmfs/volumes/vsanDatastore/dockvols/tenant1/storage.vmdk ('NoneType' object has no attribute '__getitem__')"}
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] lib.vmci_reply: VMCI replied with errcode 0
07/13/16 23:11:22 2710275 [photon.vsan.2-storage] [DEBUG  ] Released lock: storage

@kerneltime
Shouldn't this fail earlier since the volume is attached?

I have to investigate the behavior with the vim.virtualdiskmanager, but I think vmkfstool -U is too destructive to allow execution without checking attached status.

vmkfstools removes the sidecar (KV files) ahead of unlinking the vmdk itself. So, its possible that the command errors but has removed the side car file. Seems like a bug in disk removal as its leaving the disk with meta-data removed. Again, the error seems to be a busy error at the lowest level.

Yes, the removeVMDK needs to check that the disk isn't in use - there is no check in vmdk_ops.py:removeVMDK() - which is a bug in itself. Issue #719 will fix this.

@govint
The volume was attached to another node. If the removal cmd was issued from the same node the docker daemon would check and error out

@brunotm, absolutely, but removeVMDK must handle that check as its got no idea who's asking it to remove a VMDK. And with the multi-tenant support coming up, we can have multiple VMs in the same tenant having access to the same VMDKs and this scenario can be common.

@govint
That was my first comment :)

FWIW I think adding overhead to every remove operation (check before remove) is less appealing that adding overhead to very few operations (recover on failure). Besides, I suspect checking for usage is not going to be trivial.

Fixed with Bruno's PR #719


feat: Add array literals

Closes #396.

New arrays can be created using the constructor array(x, y, z).
Uses a CustomCallChecker to support varargs
This broke some code that relied on the static signature of functions. Added special cases for CustomFunctions without known signature (such as the array constructor) that infers a concrete signature based on the context.

Codecov Report
Attention: Patch coverage is 95.58824% with 3 lines in your changes missing coverage. Please review.

Project coverage is 92.57%. Comparing base (e23b666) to head (086d3e1).

Files with missing lines
Patch %
Lines

guppylang/prelude/_internal/checker.py
96.55%
1 Missing :warning:

guppylang/prelude/_internal/compiler.py
91.66%
1 Missing :warning:

guppylang/prelude/builtins.py
75.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #446      +/-   ##
==========================================
+ Coverage   92.53%   92.57%   +0.04%
==========================================
  Files          48       48
  Lines        5249     5308      +59
==========================================
+ Hits         4857     4914      +57
- Misses        392      394       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Certificate issues

Hello Trendschau,
since ive been running the last update to 1.4.4 i got some trouble with the Certificate handelings. Sometimes is my certificate accepted as secure sometimes not. It almost happend when ive been logged in. Can it come from the new user management?
I dont use letsencrypt. My Certificate issuer is Sectigo.
Your Setup Typemill Movies at youtube are awesome. Many thanks for it
Best regards
Thomas

Hi Thomas,
thank you for the feedback!
Regarding the certificate: I don't think that this is a Typemill issue, at least I am not aware of any code that might affect it. I suppose it is an issue with the certificate itself, with the hoster or with the browser. You could check the certificate for errors here https://www.sslshopper.com/ssl-checker.html or here https://www.digicert.com/help/ , you can also search for browser issues with certificates and if that not helps, maybe contact the hoster?
Best regards
Sebastian

Hi Thomas,
I will close this issue because probably not a typemill issue. Thank you, Sebastian

Yeah thank you Trendschau,
sorry for my late answering. It was my failure with these Problems. Was a Setup Problem in my Config-Folder on my Web Server


Game crashes at the alley in the first sections of the game

Version
3.0.1 (412b94e)
Seed
R730-0000-ZJMG8MQZBFB00NRGY1Z0ZZZZZZZZZZZZH9Z
Scenario
RE 3 (Jill)
What happened?
The game crashed after going through the room with the snakes that come down from the ladder....the room that is connected to it through the ladder crashes the game (it's an alley in the city which exists in the first sections of the game...sorry for the bad description but I don't know its code name).

Closing due to lack of information. A saved game and a room number is needed.


No longer supported packages

Need to update packages, especially inflight because of this warning:
This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

NPM install logs:
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.

I think that all thoses dependencies are up to date now.

npm outdated pass.


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In 840c944, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 19986 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in d263db3 after 10 minutes.


Jerky scroll when used in ListView

I am using version 1.4.5 and I integrated adapter to my ListView as defined in the beginning of the cookbook. The scrolling gets terrible and jerky on my Nexus 6P with Android 8.1 Oreo. Why is this happening?
I haven't see any ViewHolder pattern for ListView, so, is this because of it?

Yeah I guess we should investigate and refactor the code for Advanced ads... I haven't worked on it while Advanced ads were in a beta. Sorry for a late answer


Handle multiple (per table) Mysql dump files

In MySql it is possible to export a database into multiple sql dump files, one for each table. It happens very rarely that we get such dumps from the customers, but perhaps we could enhance CloudDB to be able to handle such use cases as well.

I googled a bit and it seems like such exports can be made with a mysqldump command like this:
mysqldump --user=dbuser --password --tab=~/output/dir dbname
However, "After running the above, you will have one tablename.sql file containing each table's schema (create table statement) and tablename.txt file containing the data." (https://stackoverflow.com/questions/3669121/dump-all-mysql-tables-into-separate-files-automagically)
This is confirmed by the official documentation of mysqldump: https://dev.mysql.com/doc/refman/5.5/en/mysqldump.html#option_mysqldump_tab

We could implement this, basically the same as #163 but for MySQL.
The same is true here as there: we need to alter the import process to allow multiple files to be in an archive and then we'd need to make sure that they are all imported.
Alternatively, since MySQL dumps aren't binary, we could simply cat them together into one file and then pass that along to the importer.

Migrated to https://github.com/djavorszky/liferay-support-ee/issues/15


[FEATURE] Container-Optimized OS support

Is your feature request related to a problem? Please describe (👍 if you like this request)
https://cloud.google.com/container-optimized-os/docs This is an evaluation task instead to see how Longhorn can integrate with it.
Describe the solution you'd like
A clear and concise description of what you want to happen
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Limitations https://cloud.google.com/container-optimized-os/docs/concepts/features-and-benefits

According to the document statement:

Container-Optimized OS is the default node OS Image in Kubernetes Engine and other Kubernetes deployments on Google Cloud Platform.

Given that Longhorn is compatible with GKE, we can assume that it should also work on COS.
TODO: manually create a COS cluster with Kubernetes and verify Longhorn.

Seems like we've only tested GKE with UBUNTU_CONTAINERD. We've never done any testings with  COS_CONTAINERD.

TODO: figure out how if it is possible to get Longhorn dependencies onto COS.

COS_CONTAINERD doesn't ship with the package manager, and the majority of directories are set to read-only. GKE works around this by cloud-config in user-data and /home/kubernetes/containerized_mounter/rootfs that contains the dependencies and mounts within the chroot environment. Testing with other orchestrators like K3s is challenging due to the absence of a support method for the environment pre-configuration.
The easiest approach is to use GKE which comes with the COS_CONTAINER + Kubernetes. We could potentially use the same rootfs for installing Longhorn dependencies and mounting for the data path. However, since the user-data is predefined in GKE, we can't directly utilize the cloud-config. Instead, a possible workaround is to use a daemonset that runs chroot and nsenter for Longhorn dependencies setup/installation.
ref: https://github.com/kubernetes/kubernetes/tree/v1.29.2/cluster/gce

As evidence supporting the assumption mentioned above, I have successfully installed the open-iscsi via a daemonset and confirmed its running on the host system:
> ps aux | grep iscsid
root       58264  0.0  0.0  25384   292 ?        Ss   06:21   0:00 /sbin/iscsid
root       58265  0.0  0.0  25888  5324 ?        S<Ls 06:21   0:00 /sbin/iscsid

Given that we've done the majority of the work on the Talos support feature, it seems that this feature that only a small effort is needed for this feature. Primarily, providing users with the necessary dependency installation.
Additionally, in GKE, periodic updates are made to topology.kubernetes.io/zone to reflect the actual zone, causing failures of the replica_auto_balance_zone tests when such updates occur. To tackle this, we can modify the tests to refresh the zone labels to maintain the expected zone label simulation throughout each test run.
Below is the full test result from my PoC.
= 355 passed, 19 skipped, 348 warnings in 53969.99s (14:59:29) =

Hi @c3y1huang , test case test_replica_auto_balance_node_duplicates_in_multiple_zones failed on master pipeline after https://github.com/longhorn/longhorn-tests/pull/1819, could you take a look on that? thank you.

Hi @c3y1huang , test case test_replica_auto_balance_node_duplicates_in_multiple_zones failed on master pipeline after longhorn/longhorn-tests#1819, could you take a look on that? thank you.

Thank you @chriscchien . Will be fixed in https://github.com/longhorn/longhorn-tests/pull/1849.

After applied kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/master/deploy/prerequisite/longhorn-gke-cos-node-agent.yaml on cos_containerd, there are some error messages in the log:
$ kubectl get pods
NAME                                  READY   STATUS    RESTARTS        AGE
longhorn-gke-cos-node-agent-5n9xx     1/1     Running   1 (7h43m ago)   7h44m
longhorn-gke-cos-node-agent-8r7tx     1/1     Running   1 (7h43m ago)   7h44m
longhorn-gke-cos-node-agent-f28vz     1/1     Running   1 (7h43m ago)   7h44m

$ kubectl logs longhorn-gke-cos-node-agent-5n9xx
...
(23/24) Installing: systemd-249.17-1504<IP_ADDRESS>.x86_64 [.......
Creating group systemd-journal with gid 485.
Creating group systemd-network with gid 484.
Creating user systemd-network (systemd Network Management) with uid 484 and gid 484.
Creating group systemd-timesync with gid 483.
Creating user systemd-timesync (systemd Time Synchronization) with uid 483 and gid 483.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
/usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to resolve specifier: uninitialized /etc detected, skipping
All rules containing unresolvable specifiers will be skipped.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
done]
(24/24) Installing: open-iscsi-2.1.9-1505<IP_ADDRESS>.x86_64 [..
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

Not sure if there's any issue here, but longhorn can be installed without problem. cc @c3y1huang

After applied kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/master/deploy/prerequisite/longhorn-gke-cos-node-agent.yaml on cos_containerd, there are some error messages in the log:
$ kubectl get pods
NAME                                  READY   STATUS    RESTARTS        AGE
longhorn-gke-cos-node-agent-5n9xx     1/1     Running   1 (7h43m ago)   7h44m
longhorn-gke-cos-node-agent-8r7tx     1/1     Running   1 (7h43m ago)   7h44m
longhorn-gke-cos-node-agent-f28vz     1/1     Running   1 (7h43m ago)   7h44m

$ kubectl logs longhorn-gke-cos-node-agent-5n9xx
...
(23/24) Installing: systemd-249.17-1504<IP_ADDRESS>.x86_64 [.......
Creating group systemd-journal with gid 485.
Creating group systemd-network with gid 484.
Creating user systemd-network (systemd Network Management) with uid 484 and gid 484.
Creating group systemd-timesync with gid 483.
Creating user systemd-timesync (systemd Time Synchronization) with uid 483 and gid 483.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
/usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to resolve specifier: uninitialized /etc detected, skipping
All rules containing unresolvable specifiers will be skipped.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
done]
(24/24) Installing: open-iscsi-2.1.9-1505<IP_ADDRESS>.x86_64 [..
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

Not sure if there's any issue here, but longhorn can be installed without problem.

When dependencies are installed via package managers within a container, the package manager will try to initiate the ISCSi services managed by systemd, which causes problems because the container environment doesn't fully support systemd. Hence, the script manually starts the daemon instead of relying on systemd. Therefore, this kind of error should be safe to ignored in this context.

Verified passed on master-head (longhorn-manager f63611c) following the document to setup Longhorn on cos_containerd. Longhorn can be installed without problem, and run core test on it, test cases all passed.

Not sure if there's any issue here, but longhorn can be installed without problem.

When iSCSId is installed via package managers within a container, the package manager will try to initiate the ISCSi services managed by systemd, which causes problems because the container environment doesn't fully support systemd. Hence, the script manually starts the daemon instead of relying on systemd. Therefore, this kind of error should be safe to ignore in this context.

@c3y1huang can we mention this is an expected warning in the doc? to prevent any confusion or later explanation?

@c3y1huang can we mention this error as an expected warning in the doc? to prevent any confusion or later explanation?

Sure! Doc updated (https://github.com/longhorn/website/pull/884/files#diff-2eb85726fa84ef4b9aa85bb05e1a39d292fccefd1880bb5565441452273b3df3R51-R52).


Eliminate reloading of a whole blending point

For https://github.com/StarcounterPrefabs/Website/issues/50.
(based on bugfix/double-replace-op branch)

Fixed. Please check.

This looks excellent now!


Feat/initial SummaryPage setup

Context

Setting up the Summary page for when user finishes their interviews. Will display basic information.
What Changed?

Created a new file called SummaryPage.js that contains the summary of interview, and redirects to either home page or back to the interview
Changed InterviewPractice.js file to link to the SummaryPage by adding a "Next" button
Changed how InterviewPractice.js stores the time remaining for each interview video, by setting it as a const, and subsequently sending that state over to the SummaryPage once you route to it

How To Review

Check the SummaryPage.js file to ensure all the core functionalities are there - not all of them have been fully implemented due to limitations of the other pages at this stage
Ensure that InterviewPractice.js hasn't been broken, and the features from previous builds still work.

Testing

Tested using console.log() whether the state was being sent over from the InterviewPractice.js page to the SummaryPage.js - works as intended.

Risks

Make sure that InterviewPractice.jsn page hasn't been broken, and the core logic that was intended still remains.

Notes
Closes #19

I've just added a feature to change the color from grey to a shade of light blue - would be nice if you double check if the change fixes the issue @RusiruD

Great work on this page, my suggestions from before the change still apply but they can be implmented later. Great work fixing the Go Home button it looks much better.


ARROW-11926: [R] Add ucrt64 binaries and fix CI

The R project is experimenting with a new ucrt toolchain. This prepares us by adding ucrt64 binaries to the windows bundle.

Thanks @jeroen. Do you have a pointer to how to test the UCRT build?

You can use the ucrt build of R: https://github.com/r-windows/docs/blob/master/ucrt.md#readme
But this is pretty experimental perhaps you don't need to automate that part yet.


Create EDS_API_Test.feature

This PR adds a Gherkin feature file with tests for Simple Edge Discovery, as required by the Commonalities API Readiness Checklist

@gunjald on second thoughts, to align with Device Identifers and Quality on Demand APIs: I've made the 'EDSInvalidUEIdentity' a 404 as suggested above. It's technically not ideal for the reasons given, but at least it wil be consistent across CAMARA so probably the best option. I've update the .feature file accordingly (same Pull Request)

Superseded by #201


Broken node version requiremetns after dependencies update

After i've updated repo with #36, there is now a several issues that broke the whole install and build process.
Cannot use yarn
Using yarn for installing dependencies is now impossible. Getting error
<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">= 8"

even though my node is the correct version:
[mmarosi@unused-4-159 react-ui-components]$ node -v
v8.11.3

This can be avoided using npm or yarn with --ignore-engines flag.
Changing the node environment will also require rebuild of node-sass module. You can do that by running command npm rebuild node-sass --force.
We should fix the yarn issue.

cc @karelhala


Accent color got back to default value after deleting a key

Accent color got back to default value after deleting a key.
Steps to reproduce the behavior

start gpg-tui
select a pub key
press d and y

[general]
splash = false
tick_rate = 250
color = "blue"
style = "plain"
file_explorer = "xplr"
detail_level = "minimum"
key_bindings = [
  { keys = [
    "?",
    "h",
    "f1",
  ], command = ":help" },
  { keys = [
    "C-d",
    "C-c",
    "q",
  ], command = ":quit" },
]

[gpg]
armor = false
homedir = "~/.gnupg"
outdir = "~/.gnupg/out"
outfile = "{type}_{query}.{ext}"
default_key = ""

System Information

OS: Arch Linux 6.0.17-hardened1-1-hardened
Rust Version: rustc 1.64.0-nightly (6dbae3ad1 2022-07-25)
gpg (GnuPG) 2.2.40
gpg-tui 0.9.2 (paru -S pgp-tui-git)

Hey!
This should be fixed in 6ecc253c5c54c2779b991170eed4ff03ee539106
Thanks for reporting! 🐻

Hey you, can confirm that :) thx, for your work and have a nice day!


[BUG] Unaligned About Us heading

Description
In About Us Page , The "About Us" Heading is not aligned properly , Half of it got cut or overlapped by the navbar for screen Dimensions above 820 x 1180 ( Ipad) , 912 x 1368 ( Surface Pro) and for normal laptop and PC screens.
Screenshots
In Normal laptop and PC screens

In Surafce Pro screen

Any additional information?
No response
What browser are you seeing the problem on?
Chrome
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

kindly please assign me this Issue

@ReejoJoseph1244 go ahead

@rohansx Thank you for assigning me this issue. I'm done with fixing the issue looking forward to do a Pull request , I'm planning to keep the issue fixed branch name as : Updated_AboutUS_Page
is it Ok? or is there any specific Branch naming standard to follow

done


Flash Builder4.7(64 bit) Show error during Building project

For android project Flash Builder show me error if i add even swc of facebook plugin
Errors occurred during the build Project
Clean project shows the same error
Errors running builder 'Compiler' on project 'testapp'.
java.lang.NullPointerException
after removing it, and restarting Flash Builder  all compiled ok
reinstall Flash Builder doesnt help me
if i create at Flash Builder ios project all worked ok

Uncheking "Build Automatically" from Project Menu helps me


KAFKA-10102: update ProcessorTopology instead of rebuilding it

Rather than recreate the entire topology when we find new regex matched input partitions, we can just update the relevant pieces.
Only the SourceNodes and ProcessorTopology seem to care about the input topics, and we can actually extract this information out of the SourceNode altogether by pulling it into the ProcessorTopology.

Ready for review @abbccdda @guozhangwang

Retest this please.

Retest this please.

Retest this please.

Retest this please.

Java 8 and Java 11 failed with env issue. Java 14 passed.

Retest this please.

All tests passed, can we merge @mjsax ?

Merged to trunk and cherry-picked to 2.6 branch.


kind 0.9.0

Updating package kind to release v0.9.0.
Release info
v0.9.0 Focuses on stability enhancements following v0.8.0 / v0.8.1, a new wave of features will ship in v0.10.0.
Breaking changes have been kept to a minimum, primarily that Kubernetes v1.12.X is no longer supported to make way for some fixes requiring beta-grade kubeadm.
Breaking Changes

The default node image is a Kubernetes v1.19.1 image: kindest/node:v1.19.1@sha256:98cf5288864662e37115e362b23e4369c8c4a408f99cbc06e58ac30ddc721600
Node images built with kind v0.9.0 require using kind v0.9.0+.

These images should mostly work with older releases but may not work offline.
Images from kind v0.8.0+ should still work but lack some internal improvements

Support has been dropped for Kubernetes older than v1.13.0.

A detailed support policy is in the works. The Kubernetes project only supports v1.16+ currently.

Building Kubernetes with bazel will only work with Kubernetes v1.15+

Building without bazel still works back to v1.13.0

v1alpha3 kind config is no longer supported. Please upgrade to v1alpha4 (which was already the current version in previous releases)
Capital letters in cluster names are explicitly rejected by kind, in order to prevent encountering upstream issues with name validation

New Features

NFS volumes should now work
Kubernetes RuntimeConfig is now first class in kind config
Upgraded dependencies across the board
Nodes now have a tenative providerID value set. We commit to the kind:// prefix but the rest of the contents may change.
The base image is tentatively multi-arch by default. The node image is still not as of yet.
More values are automatically included in no_proxy when proxies are detected
The default CNI shoult automatically match MTU to the underlying bridge
Binaries are now stripped of debugger (not stacktrace) info for smaller binaries

New Node images have been built for kind v0.9.0, please use these exact images (IE like v1.19.1:@sha256:98cf5288864662e37115e362b23e4369c8c4a408f99cbc06e58ac30ddc721600 including the digest) or build your own as we may need to change the image format again in the future :sweat_smile:
Images built for this release:

1.19: kindest/node:v1.19.1@sha256:98cf5288864662e37115e362b23e4369c8c4a408f99cbc06e58ac30ddc721600
1.18: kindest/node:v1.18.8@sha256:f4bcc97a0ad6e7abaf3f643d890add7efe6ee4ab90baeb374b4f41a4c95567eb
1.17: kindest/node:v1.17.11@sha256:5240a7a2c34bf241afb54ac05669f8a46661912eab05705d660971eeb12f6555
1.16: kindest/node:v1.16.15@sha256:a89c771f7de234e6547d43695c7ab047809ffc71a0c3b65aa54eda051c45ed20
1.15: kindest/node:v1.15.12@sha256:53ca8a3f446b0751019d522066ce844f6281ffb5b15e9605cd8940176abf4c76
1.14: kindest/node:v1.14.10@sha256:ce4355398a704fca68006f8a29f37aafb49f8fc2f64ede3ccd0d9198da910146
1.13: kindest/node:v1.13.12@sha256:1c1a48c2bfcbae4d5f4fa4310b5ed10756facad0b7a2ca93c7a4b5bae5db29f5

Fixes

Limited fixes related to HA mode and restart support
Fixed issues with ipv6 network overlap
Fixed bugs with NO_PROXY generation
Mitigated issues with concurrent cluster creation on clean hosts
KUBECONFIG writing has retries to mitigate concurrency / locking issues
Docker data root on ZFS should be fixed
Fixed building with bazel in kubernetes 1.20 development
Implemented assorted workarounds for breaking bugs in podman v2.X
Upstream CNI fixes identified by the project have been upstreamed and picked up to mitigate excessive iptables calls in testing
Replaced broken component IP auto-detection with explicit addresses to work around upstream Kubernetes limitations (pending an agreement on how to move forward upstream)
Fixed some issues with userns-remap support
Fixed port forwarding in some cases

Contributors
Thanks again to everyone who contributed to this release! ❤
Users whose commits are in this release (alphabetically by user name)

@afbjorklund
@aledbf
@amwat
@aojea
@babilen5
@BenTheElder
@damdo
@dims
@ericsyh
@faiq
@giuseppe
@HadesArchitect
@Hellcatlk
@inercia
@izzyleung
@jayunit100
@k8s-ci-robot
@liggitt
@MaXinjian
@MaxRenaud
@mikedanese
@oomichi
@peteroneilljr
@prasadkatti
@rcarrillocruz
@rikatz
@SataQiu
@sozercan
@steigr
@tao12345666333
@vdice
@yashbhutwala
@zhijianli88

nice :+1:


Automated Package Upgrade

:tada: This PR is included in version 5.0.466 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


upgrade google-musicmanager to beta_<IP_ADDRESS>33-r0

Pretty simple upgrade to google-musicmanager.  It runs on my amd64, but I haven't tested the i686 version.

Thank you.


Update IVADOMED version

Checklist

[x] I've given this PR a concise, self-descriptive, and meaningful title
[x] I've linked relevant issues in the PR body
[x] I've applied the relevant labels to this PR
[ ] I've added relevant tests for my contribution
[ ] I've updated the documentation and/or added correct docstrings
[x] I've assigned a reviewer
[x] I've consulted ADS's internal developer documentation to ensure my contribution is in line with any relevant design decisions

Description

Update IVADOMED to the latest release, which should suppress some warnings.
Linked issues

#666

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.425%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1150

Relevant Lines:
1286

💛  - Coveralls


Missing get_nth_statement python method

Describe the bug
Python helper method get_nth_statement is mentioned in the documentation -  https://opensource.freecodecamp.org/curriculum-helpers/python.html#get-the-nth-statement, but I'm unable to find it in the https://github.com/freeCodeCamp/curriculum-helpers/blob/main/python/py_helpers.py

I don't quite understand how nth statement is intended to work and the example is confusing me.


Date.advance() does not work with parts-of-an-hour

Date.[advance,create]("2.25 hours") doesn't work.
Sure, I could Date.create().advance("2 hours").advance("15 minutes") - but that makes it REALLY difficult for a manually edited JSON configuration.
[Date.advance, Date.create]("2 hours from now") works just fine.  So I suspect any translation from relative that includes partials doesn't work correctly.

OK you got it buddy.
This is going to be some kind of record... I'm literally deploying everything as we speak. Just managed to squeeze this through.

Awesome!  Thanks!

What version are you using?

(hijacking this thread to say congrats :-).)

Thanks man! It's going to be..................big....

I think I'm on 1.4.1

Ok well in that case I may have to take everything back. It will go into 2.0.0 but I actually already deployed 1.5.0 just a few hours ago. 2.0.0 has a lot of breaking changes and on the assumption that it's non-trivial for you to upgrade, then this will have to be back-ported into 1.5.1.
It won't take long, but probably no records :)

OK...I appreciate it!
I look forward to using 2.0 - but I'm scared to jump into it right now and miss updating something.

Yeah, that's fair. Maybe you'd like to test out the new upgrade script. Kinda need someone to beta test it. The link is here:
https://sugarjs.com/upgrading
It'll be live..........soon....

I'll give it a go.  Doing backups now :)

Aaaaaaand it's live!

Cool...
Looks like the change for "advance()" didn't make it into the docs, tho...testing it on the docs page shows current time instead of advanced time.
But the upgrade to 2.0 wasn't that painful at all...so far..I hope I haven't missed anything!
And .advance() is working for me there.

\o/ 2013 me believed in it all along :-). Amazing!

@Earl-Brown Forgot to push the build!  Advance should work on the docs page now, but might have to clear some caches.

@vendethiel My god 2013.... unbelievable... :D

Oh, yeah, I have all sorts of way of making me feel old.
I was in high school back then.

@vendethiel ... how cute.  My kids were in high school back then :)

@Earl-Brown THANK YOU :D

Oh, no - thank YOU!!!
I love this library.  One of the most useful I've come across.

How can I give more immediate feedback on issues as they come up?  I'd rather not clutter the "issues" list with something just rolled out...

Closing this for now. Feel free to raise new issues!


New api sunpower

Here new api for sunpower one:
https://api.sunpower.maxeon.com/docs/
It's possible to create new integration?
Many thanks
Best regards

This is for a completely separate system from the PVS5/6 series sold in the US.

SunPower products are manufactured by Maxeon Solar Technologies and sold by its subsidiary SunPower Corporation Australia Pty Ltd., independent from the US-based SunPower Corporation.

To add to what @koleson said, this is very different and likely would be best in its own integration.  It doesn't appear anything is stopping someone from doing so but it also doesn't look like its shares anything in common with the API we use for this integration (meaning it should live in its own new integration)


Resume On Deck Items?

As far as I can tell, when selecting an on deck item to play, the option to "Resume" or "Start From The Beginning" is not given when beginning the item.

Will add this for next release. Playing new content from an offset actually isn't implemented anywhere throughout the app (eg. autoplay). I'll fix that up as well.

Fixed with latest commit - you can now select a specific version of the content (note: not quality) and if you want to resume from where you are up to.


[Feature request] Remove the spacing between the Mods button and the Options.../Quit Game buttons.

To look like this


ci: fix icu4c on macos and CIFuzz test

Fix an issue with icu4c on  macos that was caused by a recent change to the formula's name and alias: https://github.com/Homebrew/homebrew-core/pull/169239#issuecomment-2448643079 and update the CIFuzz test to use V4 of the upload-artifact GH action.

@mattn or @rittneje could either of you review this PR since it fixes the CI tests for outstanding PRs?

@charlievieth I'm not familiar with the GitHub workflow. How exactly is icu4c getting installed today? Is it just there by default somehow?

@rittneje This appears to have been a transient error due brew's transition to icu4@76 so I'll close this PR now that other PR's are pasing without this fix.