How to handle multiple pathogens/serotypes?

I think we need an example that handles multiple serotypes, variants, pathogens, etc. Particularly, I am thinking of person properties. For instance, if I want to write a model for the four serotypes of dengue (DENV1, DENV2, DENV3, DENV4), should I set the person property for infection status, heatlh status, and even maybe last time infected as:
define_person_property!(InfectionStatus, [InfectionStatusType, 4])
define_person_property!(LastTimeInfected, [f64, 4])
define_person_property!(HealthStatus, [HealthStatusType, 4])

Another complication is if we don't know the number of circulating pathogens or variants in the population. For instance, if we specify the number of variants from an input file that is unknown at compile-time, I would like to define the person properties in a similar mamner.
define_person_property!(InfectionStatus, [InfectionStatusType, parameters.number_variants])

define_person_property!(InfectionStatus, [InfectionStatusType, parameters.number_variants])
I don't believe that this is possible with a Rust macro, because the macro is evaluated at compile time, and parameters.number_variants is known at runtime. If you truly don't know until runtime, then I think you need to have a fixed upper bound that is known at compile time and a runtime error if you try to exceed that.
With that said, I tend to think that it's inadvisable to have each of these be different person properties, in part because it doesn't enforce correctness. For instance, you can have InfectionStatus=Never but LastTimeInfected=<something>. Similarly, I don't know what HealthStatus is, but I imagine it's not independent of InfectionStatus.  Restricting ourselves to InfectionStatus and LastInfected, I would instead use the type system to enforce only valid configurations, e.g.,
struct InfectionStatus {
   Susceptible,
   Infected {
      time: f64   // infected time
   },
   Recovered {
     infected: f64,  // infected time
     recovered: f64  // recovered time
   }
}

impl Default for InfectionStatus {
    fn default() -> Self {
       InfectionStatus::Susceptible
    }
}

This guarantees that if someone is Infected you have an infection time but not a recovery time, but if you are Recovered, you have both, etc.
And then you would do:
#[derive(Default)]
struct InfectionStatusAllType{
   variants: [InfectionStatus; 4]
}

Followed by:
define_person_property_with_default!(InfectionStatusAll, InfectionStatusAllType, InfectionStatusAllType::default())

For future consideration, one challenge with this approach is that event notifications for these kinds of vector person properties are not as useful as one might want. For example people may want to subscribe to people becoming newly infected and they will have to compare across the arrays to see if this kind of status change has occurred. I think we could at some point consider the concept of a vectorized/array person property - one where there is a vec/array of values for each person and where updates occur at specific index entries and updating the ith entry in that array releases an event than the ith entry has been changed with the old and new values at that index.


Can't login with Firefox

Home Assistant release with the issue:
0.80.1

Last working Home Assistant release (if known):
Don't know
Operating environment (Hass.io/Docker/Windows/etc.):

Manual installation on a Raspberry Pi 3, running as a daemon
Component/platform:
Auth/Login

Description of problem:
I just switched from Chrome to Firefox for several reasons. I opened my local home assistant instance and tried to login using the new auth system (with username and pwd). As soon as I click "next" the following message appears:
Error: Message format incorrect: required key not provided @ data['client_id']
It looks like this:

I have 2FA enabled if thats relevant. On my PC I'm running Windows 10. I also have legacy api password enabled and tried to login with my api password -> same error. So I tried it again in Chrome and there it still works. I also tried Microsoft Edge and there it is working as well, so I asume it's a Firefox related issue. I tried to restart my PC, Home Assistant and even my Pi, nothing helped. I also tried to login on a second Windows device with Firefox and even there I get the same error.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
That's my http config:
http:
  api_password: !secret hass_pw
  server_port: !secret hass_port
  base_url: !secret hass_ext_url
  use_x_forwarded_for: True
  trusted_proxies:
    - <IP_ADDRESS>
  ip_ban_enabled: true
  login_attempts_threshold: 5

Traceback (if applicable):
That's what I get in the log file as soon as I try to login:
2018-10-16 18:07:51 ERROR (MainThread) [homeassistant.components.http.data_validator] Data does not match schema: required key not provided @ data['client_id']

Additional information:
I'm using nginx to forward my hass instance to port 80, that's the corresponding config snippet:
location / {
                proxy_pass http://localhost:8123;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header Host $host;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $connection_upgrade;
 }

Can you check the URL in the browser? Looks like client_id is missing in the URL

/frontend_latest/authorize.html
that's all. Yes, the client_id is missing but why?

Anyone? The issue persists. Even after upgrading to 0.82.3

Hi, Am also getting this on 0.84.6 with Firefox, it seem to work with Chrome. It works ok with the TOTP disabled, but as soon as its enabled, it causes the same problem:

The first POST to login_flow succeeds, this is the password + username request, however the second one fails.
The POST request to login_flow fails with an error 400 Bad Request, the params is shown blow:

Looking at the code: https://github.com/home-assistant/home-assistant/blob/ead38f60054162cd73e19ecf453e8b7933e82f14/homeassistant/components/auth/login_flow.py#L28 it shows that there should be more in the POST request.

Also the Firefox console reports:

The only error at the server end is:
hass[30240]: 2019-01-04 08:48:53 ERROR (MainThread) [homeassistant.components.http.data_validator] Data does not match schema: required key not provided @ data['client_id']

My problem started with release 0.88 and on the EDGE browser.
Is there a work around?

Seeing the same with release 0.88 and Firefox. The Web Developer Console shows that the client_id is getting passed up with the POST data.

This seems to be specific to Firefox. In my case, I'm running it from a virtual env over HTTP. When I look at the web console I see:
TypeError: NetworkError when attempting to fetch resource.' in the web console. The resource in question is onboarding-ed29f25b.js:2189:1138 which is an attempt to POST to /api/onboarding/users and failing. I'm not seeing an attempt to connect to that URL on the Pi running Home Assistant.
With Chromium, this just works.

What version of Firefox are you using?
Please see my comment in https://github.com/home-assistant/home-assistant-polymer/issues/2828#issuecomment-467589688. To archive better user experience, you have to use the latest version of FireFox (and manual turn on two preference), FireFox 63 is the first version officially support ShadowDOM (although you still need turn on the support by yourself). FireFox 61 maybe the lowest version you can try. Please change to use Chrome if your FireFox version is lower than 61 (include FireFox ESR 60).
dom.webcomponents.customelements.enabled
dom.webcomponents.shadowdom.enabled

Confirmed using Firefox 60 ESR. Just to be clear, there's no user experience with 0.88 where it worked with 0.87 without issue, and from @tottka's comment above there's similar issues in Edge. I upgraded to 0.88 a few days ago without issue, and it's only when I had to log back in again that this issue appeared.
This looks very much like a nasty bug likely to unexpected affect users after they upgrade, and which will only be seen during a fresh login attempt. Is there anyway to turn off the ShadowDOM requirement causing this?

Also have the same issue. Home Assistant 0.88.1 on a RPI 3 with virtualenv, trying to access it over the Tor network from Linux

Same problem here. Can not login with:
Chrome on iOS
Safari on iOS
Edge on Windows 10
Don't dare to log out from Chrome on Windows 10 to try to login again!!!

The resource in question is onboarding-ed29f25b.js:2189:1138 which is an attempt to POST to /api/onboarding/users

@ndonegan please open a new issue to address this, it is different than the OP's issue. Mixed different issue together just let us hard to analysis.

@Strixx76
I don't have chance to test on iOS, but I tried Edge on Windows 10 and there is no issue for me.
Please open a new issue (fill in all fields in issue template we are asking) if you have met problem on the browsers you listed. I want to limit this thread to FireFox only.

@awarecan You sure it's a different issue? Exactly the same errors appearing the logs, exactly the same error appearing in the client. I just happened to dig deeper into the web console log to see what was happening.

I am sure yours are different. @mretallack 's research back to Jan 4 pointed to the root source, and it is different than yours. And it is not new issue at all.

@awarecan Got it working in Edge. I guessed it was the same problem since it was messing on different computers and devices with the same error message. But the Edge problem was solved by deleting all browser data.
But the problem persists on iOS. Created a new issue for that.

/move to home-assistant/home-assistant-polymer

Same problem for me, but on IceCat.
Also the browser crashes when i enable the two settings you recommend and then try to enter my username.

Running Firefox 60.5.2esr and having the same issue. When flipped back to 87.0 login works normally. I did the dom setting in Firefox suggested by @awarecan, which enabled login. However, lovelace fail to display correctly. See screenshot below:

Further testing...
Enabling ShadowDOM in Firefox 60.5.2esr permitted the login with the browser, but lovelace is messed up. Once logged in, disabling ShadowDOM restores lovelace. It is annoying having to disable/enable setting to get 0.88 working, but at least there is a work-around.

@Enzo-Matrix, please retest it on 0.89 beta with FireFox default settings.
If you still have problems please report it back to home-assistant/home-assistant-polymer#2859
I am going to lock this thread.


Gitea crash on windows

Gitea version (or commit ref): 1.8.3
Git version:
Operating system: Windows
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:

Description
Gitea has crashed, there is nothing in log files about crash.
In windows event viewer is error event with message: "The gitea service terminated unexpectedly.  It has done this 2 time(s)."
It is possible to get some additional logs except those in log folder?

you could increase log level in app.ini

under section [log]
set LEVEL     = info to some other value  [Trace, Debug, Info, Warn, Error, Critical, Fatal, None]

may run git in console
path\to\gitea.exe web

Is it crashing during startup or just normal running?
If it's during startup - likely your configuration is incorrect. 1.9 will give better logging.

It crashed during normal running.


cadvisor issue

Get "http://cadvisor:8080/metrics": dial tcp: lookup cadvisor on <IP_ADDRESS>:53: server misbehaving
Can anyone tell me whats going on in here. I am using same stack for grafana, prometheus , cadvisor and node export.

Can you share more details about your set-up and config files please?


Color themes apear blocky in empty regions of the editor window.

Issue Type: Bug
When you have a file open which contains text that leaves large parts of the open editor blank, the background color of the theme does not get applied to the empty space and the the editor tab looks blocky, a bit like color banding.
the issue exists in both light and dark themes: pictured Dracula color theme and
Issue as it appears in light themes (Pictured Gruvbox Concoctis Medium Light):

Issue as it appears in dark themes (Pictured Dracula color theme):

The relevant areas have been outlined using red blocks, the original images are attached below as reference:

VS Code version: Code 1.43.2 (0ba0ca52957102ca3527cf479571617f0de6ed50, 2020-03-24T07:52:11.516Z)
OS version: Linux x64 5.3.0-42-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 2505)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
15.54GB (2.76GB free)

Process Argv
--no-sandbox --unity-launch

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

solargraph
cas
0.21.1

githistory
don
0.6.3

gitlens
eam
10.2.1

docker-explorer
for
0.1.7

beautify
Hoo
1.5.0

output-colorizer
IBM
0.1.2

ruby-rubocop
mis
0.8.3

vscode-docker
ms-
1.0.0

python
ms-
2020.3.69010

vsliveshare
ms-
1.0.1847

ruby
reb
0.27.0

gruvbox-concoctis
whe
10.30.20

vscode-ruby
win
0.27.0

(2 theme extensions excluded)

Can confirm that, same bug happening to me. Will help with any tracking info if needed.

@L0stLink @igormartimiano Do you observe any changes after the following
* Command Palette search for "Configure Runtime Arguments"
* Set "disable-color-correct-rendering":  false
* Restart

@deepak1556  Just saw the discussion at #84690 before your reply, I previously have set "disable-hardware-acceleration": true and it was apparently fixed.
The following:
"disable-hardware-acceleration": false
"disable-color-correct-rendering": false
Also seems to work.

Thanks for confirming!

I have the same issue, is there a way to fix it and use hardware acceleration?


Add an option for NGrams to not return overlapping timestamps

This was requested by a couple people on perception. Basically helps return less correlated sequences by not overlapping timestamps.

Codecov Report

Merging #86 into master will decrease coverage by 0.07%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##           master      #86      +/-   ##
==========================================
- Coverage   87.15%   87.08%   -0.08%
==========================================
  Files          44       44
  Lines        2405     2415      +10
  Branches      364      368       +4
==========================================
+ Hits         2096     2103       +7
- Misses        246      247       +1
- Partials       63       65       +2

Impacted Files
Coverage Δ

petastorm/ngram.py
93.65% <81.81%> (-2.58%)
:arrow_down:

petastorm/workers_pool/process_pool.py
95.55% <0%> (-0.75%)
:arrow_down:

Continue to review full report at Codecov.

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


[10.x] Fix issue with @json incorrectly compiling when argument has one or more commas

I ran into the issue as described in #46908 myself recently and fixed it by parsing the arguments using preg_split instead of a simple explode.
The regex is a slightly modified version of the one from the SO answer below. It now also ensures that commas within parentheses and brackets are ignored.
https://stackoverflow.com/questions/18893390/splitting-on-comma-outside-quotes/18893443#18893443
We should probably add more cases to the jsonArgumentsProvider data provider before even considering merging this.

Appreciate you sending in the PR. I just want to stress being careful with this because we've had numerous occasions in the past where we tried to adjust the compiler only to break other use cases for people.

Your tests do not include the @json('a', JSON_PRETTY_PRINT) case (you can provide up to 3 arguments to @json) and there are more language structs than the ones that you define (like [...['a']] and a->?b->?c()).
Although your regex looks good and I cant find any obvious issues with some extra structs that i tested, it seems like the best way forward is to just use simple expressions whenever you are using @json (you probably want to delegate most of the logic to a controller/view-component anyway).

Your tests do not include the @json('a', JSON_PRETTY_PRINT) case (you can provide up to 3 arguments to @json) and there are more language structs than the ones that you define (like [...['a']] and a->?b->?c()).

I didn't include them since they are already tested in the test above, this test only makes sure the arguments are rendered correctly. But I totally agree with your second point, it needs a lot more cases. Also just realised that heredoc and nowdoc probably don't even work.
I guess to get this working for all possible cases we'd have to use nikic/php-parser but that definitely seems like overkill.

It indeed fails on heredoc and nowdoc strings as expected when parsing using regex.
To get it working using the php parser was actually a lot easier than expected. The php parser is currently only available when the dev dependencies are installed. This means we would need to add it as a dependency which is probably not something we would like to do for something like this

Honestly it wouldnt be a bad idea to just bite the bullet and discard/deprecate this blade directive, in favor of something like:
{{ json($params) }}

// helpers.php
function json($value, $flags, $depth) {
    return new \Illuminate\Support\HtmlString(json_encode(...func_get_args()));
}

(HtmlString allows you to call it using {{ }} instead of {!! !!})
It makes no sense to apply all this difficult parsing of arguments.
The sole reason we can't do <?php echo json_encode($expression); ?> in the blade compiler is because we have defaults for the json arguments; this make parsing the string as php code a pain.

You can already do that with the Js helper class:
<script>
    var app = {{ Js::from($array) }};
</script>

I'd suggest adding more methods into that if there are use cases it doesn't support.
https://laravel.com/docs/10.x/blade#rendering-json

Thx I've added a PR that exposes one of the functions in that class for this reason. The @json directive has already been removed from the docs, instead the docs only showcase Js::from() but that one explicitly echoes javascript code JSON.parse(...).


No Evil

Good day.
I'm not a Vim converted. So is it possible to make Evil as an option, because commenting out Evil in init.el will not do. So project text search :ag and so on can work without Evil.
Thank you.

Commenting evil out in init.el should be enough. If that isn't working for you, a common cause is that you are running byte-compiled Doom. Did you run make compile or make core before removing evil from init.el? If so, use make clean to remove byte-compiled files, then try again.
I'm not sure I understand about :ag. Without evil you don't have access to ex commands (like :ag), but you still have access to M-x counsel-ag (which is what :ag uses under the hood). Same for counsel-rg. Is that what you mean?

About the :ag. Yes the counsel-ag does the job. Thank you. All works.
Maybe we can get a noob friendly documentation on how-to features.
And yes i did all the make processes :D


Add Windows support in PlatformOperationSystemVersion

Background
In smithy-swift, PlatformOperationSystemVersion gets OS versions for Linux and macOS. This OS version information gets included in OSMetadata segment of the user agent header.
To Do
Add support for Windows as well.
Other Info
Related issue: https://github.com/awslabs/aws-sdk-swift/issues/1206

Turns out Apple recently implemented getting OS versions for Linux & Windows for us using compiler directives in their Foundation.ProcessInfo. Closing https://github.com/awslabs/aws-sdk-swift/issues/1526.


Add unit tests for create_motive_variation()

Parts of create_motive_variation() have pretty nice unit tests, but I'd like to put in some unit tests for the method as a whole. I really like how it sounds, so this may be more in the realm of regression tests to protect the algorithm.

This is mostly in place now thanks to the legacy unit tests.


tiny cosmetic improvements to BEM code

Just some tiny improvements to the BEM and forward code as I was reading it. The changes are self-explanatory for the most part. @larsoner let me know if this looks good to you.

Thanks @jasmainak


input matrix contatins NaN

Thank you for your work. When using the soap optimizer, I found that there is a certain probability of triggering this error.
How to avoid this situation

could you try printing the state['GG'] matrix?


Call out when someone @'s another viewer who is lurking / AFK (maybe a new AFK command too)!

As the bot is getting more stateful, how about if a viewer goes into lurk mode (or maybe a new AFK command), but if they get mentioned before unlurking / RTK (return to keyboard?), then the chatbot replies and informs the person who is trying to reach the lurkee that they are currently not around?
Bonus feature:
When the lurkee returns to chat and does an !unlurk, then replay the message from the original viewer in the format of @person was trying to get your attention! They said: {whatever the message was}

I like this idea a lot. Let's stick to the first example first rather than trying to keep up with logs of missed messages.
How's this for requirements:

[ ] Create an IUserInfo[] lurkingUsers property in the Twitch chat client class to maintain a list of lurking users
[ ] !lurk command that adds the user to lurkingUsers if they aren't already there
[ ] !unlurk chat command that removes the user from lurkingUsers if they are there
[ ] Chat message processor that reviews each message content for the username of any user in the lurkingUsers array and responds to the chatter with @{chatter username}, just an FYI, @{lurking username} is currently lurking and may not see your message.
[ ] In the Twitch chat client class, subscribe to the onStreamStart and onStreamEnd socket.io events and, in both cases, clear the lurkingUsers array.

Thoughts?

Maybe also, instead of keeping up with a log of missed messages, when the chat client detects a message sent to a lurking user, copy and whisper that message to the user.


[03:29:40 ERROR]: Could not pass event PlayerJoinEvent to BadlionClientModAPI v1.0

https://hatebin.com/qklmjekvig
I need help, a player is having trouble joining, keeps timing out

Hello,
Can you show your plugin config ? It shouldn't error on that line.

Might be invalid config. Closing this since no answer from the author.


add token expiration note.

Signed-off-by: andxu<EMAIL_ADDRESS>

Docs Build status updates of commit 4bf7ac3:
:clock10: Full build: the average full build time is 71 min(s) 6 sec(s), this is based on the last 261 build(s) for this repository.

Docs Build status updates of commit 4bf7ac3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-on-kubernetes.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


AddressTools return only integers

Checks failed because I forgot to update some mixins... the PR should be fine


Retro theme bad performance and high GPU usage

Environment
Windows build number: [10.0.18363.1256]
Windows Terminal version (if applicable): 1.4.3243.0
GPU: Intel UHD Graphics 630, Terminal is not using my Nvidia GPU GTX 1050TI but the integrated graphics should be plenty to handle a simple terminal theme.

Steps to reproduce
Enable Retro theme found in the official docs: https://docs.microsoft.com/en-us/windows/terminal/custom-terminal-gallery/retro-command-prompt
Expected behavior
A simple theme like this simply shouldn't be consuming the resources like it currently does
Actual behavior
Extremely high GPU usage: Not only does GPU usage reach +80%, but the performance is very bad, there's obvious delay when displaying key strokes.

It's a pixel shader marked "experimental" with known performance issues. This is by design.


chore: release main

:robot: I have created a release beep boop
0.5.2
0.5.2 (2024-12-17)
Features

Support for Statistic Files (1e4fa38)
tables: load table credentials (#675) (9fd272e)

Bug Fixes

Make BASE_URI trailing slash insensitive (#681) (4799ea7)
Snapshots without schema (1e4fa38)

Miscellaneous Chores

release 0.5.2 (c5774b2)

0.5.2
0.5.2 (2024-12-17)
Features

Update UI to 0.3.0 (#684) (2f9da51)

Miscellaneous Chores

release 0.5.2 (c5774b2)

0.5.2
0.5.2 (2024-12-17)
Features

Support for Statistic Files (1e4fa38)
tables: load table credentials (#675) (9fd272e)
Update UI to 0.3.0 (#684) (2f9da51)

Bug Fixes

Make BASE_URI trailing slash insensitive (#681) (4799ea7)
Snapshots without schema (1e4fa38)

Miscellaneous Chores

release 0.5.2 (c5774b2)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.5.2
:sunflower:


missing init-db script

/vue-crud-x/example-spa

cd ../backend&&npm run-script init-db

npm ERR! missing script: init-db

ok let me check

Hi change "init-db" to just "db" for now. I will fix this and push it in next release...

fixed,
https://github.com/ais-one/vue-crud-x/pull/73


Error while compiling protocol buffers following edits to the schema

Encountered the following error while trying to compile the protocol buffers following edits to schema enums. Windows 11 system running python in a Conda environment with libprotoc 3.12.4.
(ord-dev) bdeadman@BJDFrameworkWin:~/ord-schema$ ./compile_proto_wrappers.sh

protoc --proto_path=.. --python_out=. --pyi_out=. --js_out=import_style=commonjs,binary:js ../ord-schema/proto/dataset.proto ../ord-schema/proto/reaction.proto ../ord-schema/proto/test.proto
ord-schema/proto/reaction.proto: This file contains proto3 optional fields, but --experimental_allow_proto3_optional was not set.

@bdeadman I think you might be running an old version of protoc; that flag was deprecated a while ago. You should be on libprotoc 22.3: https://github.com/open-reaction-database/ord-schema/blob/main/.github/workflows/run_tests.yml#L87

https://github.com/protocolbuffers/protobuf/releases/tag/v22.3

Thanks @skearnes. I can confirm that libprotoc 22.3 works after some tweaks. The pre-built binaries seem to have lost protoc-gen-js in v21. If you compiled from source then it may be different, but not something I want to tackle at the moment.
The npm package allowed me to get protoc-gen-js going in WSL. I'll close this issue now, but keeping this note here for future reference.

Note that you have to install the JS side separately: https://github.com/open-reaction-database/ord-schema/blob/main/.github/workflows/run_tests.yml#L89


Bugfix on validating nullpointer exceptions

Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

Hi @jumba2010 could you please resubmit this PR to https://github.com/fiterafrica/fineract-template repo instead. Skype/Slack me or @Napho if you don't have access to that


auth() with import causes linking-error

Description and expected behavior
auth() function fields aren't resolved when User model is imported.
Screenshots

Environment (please complete the following information):

ZenStack version: next
Prisma version: 5.5.2
Database type: Postgresql

Additional context
user.zmodel:
import "./base"
import "./image"

model User extends Base {
    email String @unique

    @@auth
}

image.zmodel:
import "./user"
import "./base"

model Image extends Base {
    width Int @default(0)
    height Int @default(0)

    @@allow('read', true)
    @@allow('all', auth().role == Admin)
}

Thanks for reporting it @platon-ivanov ! Will make a fix and include in the upcoming new beta.

Fixed in 2.0.0-beta.13


Make prototypical iframes for testing purposes

So here's a check list of iframes that may need to be temporarily implemented to test the reaction time of certain activities.

[x] Make the player sprite blink red, briefly, when they are hit and lose a health.
[x] Have yellow outlines around a weapon, when the player sprite walks over it, to indicate that the weapon is pickable.
[ ] Have enemy sprite blink red constantly, on intervals, when it is in vulnerable threshold.

Some reference material in case this needs extra detail:
https://github.com/Team-Awkward-Smile/Epilogue/wiki/Mechanical-Workings-Of-Individual-Enemies
https://github.com/Team-Awkward-Smile/Epilogue/wiki/Gameplay-&-Mechanics#enemy-hit-indication

whats the vulerable threshold?
what are the condition for it i guess

@Hhk187 from discord:

Yeah, so the vulnerable threshold is when the enemy goes into glory kill mode. Basically HP goes to zero, and enemy enters the state of having gun extractable (or if failed) doing kamikaze attack.

@vitormaduro can you @Hhk187 towards the code of the glory kill/kamikaze attack.

From discord:

In case vitor doesn't reply, as he could be busy with house moving, then know that as soon as an enemy hits 0 HP (and if you read the state machine you'd know enemy doesn't directly upon hitting 0 HP as they go into a separate state), then they start blinking the iframes.

Even pointing me to the correct file wow, thanks boss

@Pseudo-64 ready to test


Documentation: Messaging API for Mathematics Functions does not document Register1/Register2

To clarify: it does not say which Params they are stored in, or what format they are.

They are really BASIC helpers, which is the primary reason they aren't documented. It's a slightly odd format, because it's designed to be used in the internal BASIC stack and possibly accessible by others. What do you want to use it for ?

It stuck out to me while I was going through the API documentation; there is no specific reason for me seeking out the math functions, but I was evaluating which functions could be exposed in what ways as part of the LLVM-MOS target.

They're really BASIC helpers.
I don't know enough about it. It does mathematics for 32 bit integers and C format floats (the standard 4 byte format). Does LLVM MOS mostly use 16 bit integers (in practice) ? 32 would likely be very slow.
If this is the case my initial inclination would be to provide specific functions for 16 bit multiply and possibly divide.  Could do 32 bit if they are used. This would be cleaner and could also be used for other languages
As for the other functions, add and subtract integers are actually quicker in 65C02 code (the call takes longer) and floats probably have fairly minimal use ?

Does LLVM MOS mostly use 16 bit integers (in practice) ? 32 would likely be very slow.

Yes, but in theory nothing stops us from sign-extending 16-bit integers into 32-bit integers. I suppose there could be a value somewhere to control operand size/type.
In general, LLVM-MOS provides everything that the C standard does, including large integers and software floats (albeit slow). It is possible, somewhat easily, to overwrite the library functions LLVM's compiler runtime provides (for multiply, divide, floating-point operations, other math functions...) with ones that accelerate these operations using the messaging API.
They have minimal use, sure (unless a program decides to use them!), but what's the fun if not trying to support all of a given hardware stack's functionality?


Fix/ci

Remove need for git repo secret as polytope is now opensource
update actions and python version

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Topic/add pkg

As this is a new pkg we could be a good citizen and add the docstrings?
We could also document the package. So we start doing it for all new code and eventually do it to old code.

What would the idea of documentation be, or would there be an example of which model to follow?

@leonardojoao take a look at https://golang.org/src/go/doc/example.go

@eduardoveiga @leonardojoao I sent a lint to avoid those packages to ever to be used.
Some errors:
pkg/models/device.go:4:2: time is in the blacklist: time access must be done using 'github.com/shellhub-io/shellhub/pkg/clock' (depguard)
"time"
^
pkg/models/license.go:3:8: time is in the blacklist: time access must be done using 'github.com/shellhub-io/shellhub/pkg/clock' (depguard)
import "time"
^
pkg/models/privatekey.go:3:8: time is in the blacklist: time access must be done using 'github.com/shellhub-io/shellhub/pkg/clock' (depguard)
import "time"


Remove Rails UJS since we don't use it

Context
We don't need/want to use Rails UJS, and its magic has bitten me once already during development.
Changes proposed in this pull request

Remove Rails UJS.
Change the sign out link to use GET instead of DELETE.

I suspect this might break the logout link, I think method only works with UJS: https://github.com/DFE-Digital/get-help-with-tech/blob/3ab357fdbac8be652f00751d5c9210c070cbaaae/app/views/layouts/_nav.html.erb#L16

I suspect this might break the logout link, I think method only works with UJS:
https://github.com/DFE-Digital/get-help-with-tech/blob/3ab357fdbac8be652f00751d5c9210c070cbaaae/app/views/layouts/_nav.html.erb#L16

Ah good catch - thanks.

Can confirm that with JS disabled our current "Sign out" link doesn't work.

Can confirm that with JS disabled our current "Sign out" link doesn't work.

I've added a2e05ff which should fix the issue – @fofr you mind giving it another go using this branch?

@benilovj Sign out works with JS disabled on this branch.

I'm in favour of not relying on Javascript, but I'm not sure about the sign out link becoming a regular GET - it will work, but it breaks the RESTfulness model and introduces some potential issues (for instance, it's then possible for the users' browser to follow the link pre-emptively and sign the user out without them knowing).
I'm going to try an alternative, will add it as a suggested change if it works - please hold off merging this for the moment

I'm going to try an alternative, will add it as a suggested change if it works - please hold off merging this for the moment

Sure. FWIW, I looked to Apply for Teacher Training for inspiration...

I've put my alternative up as a separate PR - #137 . It solves the problems of signout-as-GET, at the expense of a few lines of CSS.

Closing since #137 has been merged instead.


Update tutorial to add NativeLCEL example

No issue logged

This won't be merged until the corresponding changes are deployed to dev...


Wrong data getting when use browser.storage.local.get

HI @clarkbw firstly, thanks for this awesome repo, it help me a lots 👍
However, I encounter a bug maybe, following is my source code:
browser.storage.local.get({ apiErrReport: [] }, (result) => {
   console.log(result);
   const { apiErrReport } = result;
   // ...
});

I pass an object to get function, this is work well as usual, but when I started to use jest-webextension-mock and wrote the test, I found the callback argument reuslt become as:
There's a hardcode id always in the root object
{ id: { apiErrReport: [] } }

But I think it is suppose to be a plain object without id
{ apiErrReport: [] } }

Any idea? BTW, I saw the source code and it always call the callback with { id }, but I think:
if object given, the argument should be
const args = { ...id }
cb(args);

if string given, the argument should be
const args = {};
args[id] = ...;
cb(args);

I'm not sure, please let me know your idea. thanks
Regards,
Allen

Hi @AllenFang thanks for such an awesome write up of your issue!  I'll try to take a look today.

It's likely we need a shared solution for both get, getBytesInUse, and remove

@clarkbw sure, I can give a PR in this couple day, thanks your quick response 👍


[Request] Hide collection when scrolling through Library

Collection should be hidden when user scroll up to browse the library sections. So more items can be seen.

completely agree. I will look into seeing how to implement that

I have created the screen and will soon release a new update to the app that'll allow you to just download it or install through TestFlight


Support for Kibana 5.5.0

Changes from default exports to named exports to support Kibana 5.5.0 (https://github.com/elastic/kibana/issues/12707).
Tested and it works.

Problems found: https://github.com/ommsolutions/kibana_ext_metrics_vis/issues/13#issuecomment-319445820


Rename recipes directory to scm-info

The name no longer makes sense now that there are different directory structures.

tekton never came up
/test jvm-build-service-in-repo-e2e


Subscribe to registry events

@asim should it be registry events or runtime events being recorded?

It should be platform events because this is entirely scoped to the platform itself. Registry has its own events and runtime has its own events.


Use deviceId instead of serial (Fixes SDK28 permission error)

The included .aar is the result of https://github.com/raphaelm/UVCCamera/pull/1

No, deviceIDd is a bad choice:

Returns a unique integer ID for the device. This is a convenience for clients that want to use an integer to represent the device, rather than the device name. IDs are not persistent across USB disconnects.

We want something stable across reconnects and reboots so the user does not need to select their camera every day. We could do it like pretixPRINT now does when the serial number is not available, but that would no longer allow having the same camera model twice, but I think that's an okayish limitation:
https://github.com/pretix/pretixprint-android/commit/0b4b30299aeb8c2e2f4f1b2477dbddf16e7c5cb1

replaced by #16


Scale is messed up if yazi is resized when it is in another workspace.

What system are you running Yazi on?
Linux Wayland
What terminal are you running Yazi in?
kitty 0.35.1
Did you try the latest code to see if this problem got fixed?

Broken/Messed up GUI. (I had to take a photo using my phone since pressing prtscrn fixes the issue.

Expected Behavior
No distortion or wrong scale/zoom.
To Reproduce
In Hyprland WM using Kitty terminal:

Open yazi and another app side by side.
Switch to another workspace
Kill the app that was next to yazi
Return back to the workspace which yazi was open
Observe the messed up scale/zoom

Configuration
No response
Anything else?
This bug does not effect me. I also don't care if it is fixed or not. I just wanted to document a weird behavior I have encountered. This does not happen in lf file manager. So, I thought it is a yazi bug. Feel free to close as won't fix if this is too minor to be called a bug or can't reproduce.

I'm not quite sure what you mean - could you record a GIF and show me what's happening please?

Kooha-2024-06-16-13-39-30.webm

Problem does not exist on Alacritty and Termite.
Problem only happens on Kitty.
No difference between latest release and main branch.

Yea, It is a kitty specific issue.


Cannot create Input report of larger than 32 bytes

Due to limitations of serde and serialize it seems that only arrays up to 32 are considered.
#[gen_hid_descriptor(
    (collection = APPLICATION, usage_page = 0xFF1C, usage = 0x1100) = {
        rx=output;
        tx=input;
    }
)]
struct HidioReport {
    rx: [u8; 64],
    tx: [u8; 64],
}

error[E0277]: the trait bound `[u8; 64]: Serialize` is not satisfied
   --> usbd-hid-io/src/lib.rs:32:1
    |
32  | / #[gen_hid_descriptor(
33  | |     (collection = APPLICATION, usage_page = 0xFF1C, usage = 0x1100) = {
34  | |         rx=output;
35  | |         tx=input;
36  | |     }
37  | | )]
    | |  ^
    | |  |
    | |__the trait `Serialize` is not implemented for `[u8; 64]`
    |    in this macro invocation
    |
   ::: /home/hyatt/.cargo/registry/src/github.com-1ecc6299db9ec823/usbd-hid-macros-0.5.0/src/lib.rs:202:1
    |
202 |   pub fn gen_hid_descriptor(args: TokenStream, input: TokenStream) -> TokenStream {
    |   ------------------------------------------------------------------------------- in this expansion of `#[gen_hid_descriptor]`
    |
    = help: the following implementations were found:
              <[T; 0] as Serialize>
              <[T; 10] as Serialize>
              <[T; 11] as Serialize>
              <[T; 12] as Serialize>
            and 30 others

error: aborting due to previous error; 2 warnings emitted

For more information about this error, try `rustc --explain E0277`.
error: could not compile `usbd-hid-io`

I believe https://github.com/est31/serde-big-array can help, but I haven't figured out how to use it in this case.

I took another stab at this and to integrate serde-big-array would take a bunch of work and refactoring.
However, there is a simpler solution in my case. Just ignore serialization for arrays larger than 32 bytes. In my case there is no value to serialization anyways as I'm just using hidraw as a packet transfer mechanism.
             8 => { // u8 / i8
                 if field.descriptor_item.report_count == 1 {
                     elems.push(make_unary_serialize_invocation(8, field.ident.clone(), signed));
-                } else {
+                } else if field.descriptor_item.report_count <= 32 {
                     let ident = field.ident.clone();
                     elems.push(quote!({ s.serialize_element(&self.#ident)?; }));
+                } else {
+                    // XXX - don't attempt to serialize arrays larger than 32
+                    //       (not supported by serde, yet)
                 }
                 Ok(())

Once I've verified this works well I'll submit a PR.

Thanks for merging!


Improve ConvND error message

Personally, I prefer to simplify it in one line rather than 'full if else syntax'.
Thank you for the efforts of DeepMind and the contributors to this wonderful project.

An error was found in the a3c7b47 commit and the error was resolved in the 44cc50c commit.

@trevorcai
Thank you! I thought about your two opinions. I think you are right in both opinions. So I changed the two changed codes to the original code. Thanks to you, I learned a lot!

@trevorcai
I clicked detail to see why feedback/copybara failed, but there was no response. How do I fix this?

resolved internally, the pr will land when tom approves it internally.


Bug in error messages in sandbox UI

The error message does not fit into the message box in BitBox sandbox UI, it exceeds the screen borders. Therefore they can not be fully read. Attaching a screenshot for this below:

If the error is of type bitbox.Error, it would be nice to render the code and message separately instead of the JSON.


"Cannot find step" when using Optional (|) syntax in step definition with more than one variable {}

I am experiencing an issue where I cannot add more than one variable in a step if I have an optional part in the step definition.  example below
feature
 Scenario Outline: AC01 User should be able to select one or more <item> content types from the drop down, with each item being added to the filter labels list
        When I search for "sandwich"
        Then I can filter "<type>" by "<item>"
        Examples:
            | type    | item      |
            | Content | Article   |
            | Content | Event     |
            | Content | Video     |
            ...

step file
defineStep("I (can |)filter {string} by {string}", function(s, t) {
 ...
}

The cucumber(Gherkin) full support extension in VSCode it shows that it can find the step definition in the feature file and a step elsewhere in the feature and step files using a single variable works perfectly
defineStep("I (can |)sort by {string}", function () {

This project has literally nothing to do with vscode or syntax hightlightling. You're in the wrong place.

I think he gets "cannot find step" error from our preprocessor. But I'm not sure I understand this sentence:
The cucumber(Gherkin) full support extension in VSCode it shows that it can find the step definition in the feature file and a step elsewhere in the feature and step files using a single variable works perfectly

@DaveClissold Could you please rephrase it, maybe split it into 2/3 sentences, and then read it out loud to make sure it makes sense? For example I'm 100% sure the "Cucumber full support extension in VSCode it shows" is not correct. It brakes the flow of the sentence and makes it hard to understand what's going on. For example I'm not sure what all the "it"s and "in"s mean.
Does one of those defineSteps get highlighted by the VScode, but not the other? Or do both seem to work according to VScode but only one of them works with our preprocessor?

@lgandecki Sorry for the confusion with that sentence, even I had a problem reading it back and the mention of the extension is confusing the matter, just ignore that, I was trying to indicate that the steps were not missing. The only bit to note from that is
A step in the same step file and feature file, works
defineStep("I (can |)sort by {string}", function () {
So to answer your last question, it is the preprocessor that is not working.

I'm not able to reproduce the issue, IE. two variables with optional text seems to work fine. Granted, I removed the vertical bar from the step defintion.

@badeball I tried removing the vertical 'OR' bar and it does work, but when I try the following, which is something I need in another test that I'm writing
defineStep("I (can change|have changed) {string} with {string}", function (s, t)
the error persists

First of all, alternative text happens with slash, not vertical bar. Furthermore, I don't believe it's allowed within an optional group. This can be seen here.

@badeball I've just realised the mistake I'm making and I do apologise, I'm using regular expressions and didn't realise.  That said when I try to define the step using regex, either
defineStep(/I (can change|have changed) {string} with {string}/, function() ...
or
defineStep("^I (can change|have changed) {string} with {string}$", function() ...
I get the cannot find step implementation error, do you support using regular expressions in step definitions, I noticed at the bottom of the docs you say to not use legacy methods.

Regular expressions are supported, but the {string} syntax is part of cucumber-expressions, which is a language that translates into regular expressions. When you use regular expressions yourself, you do not get the benefit of EG. {string}.  Thanks for the support and apologies again for my stupidity on this.


Schema changes: string for sc and dr

Schema for Test are using string (with format date-time) for sc and dr.
To test use number 3 NAA and 4 RA at https://github.com/eu-digital-green-certificates/dgc-testdata/tree/main/AT, they will work after implementing the fix.
To represent the schema better PastInfections are renamed to Recovery.
See PR #9

Thank you for the PR, the changes were already in the working branch, which is now merged to main.


Frame rate around 20fps

I used the OAK-D-W with the driver with default config parameters. Buth the frame rate of all three cameras are around 20fps. I tried to changed the Parameters in camera.yaml than launch the camera.launch but the frame rate remain the same. Any suggestions?

Hi, framerate can be influenced by number of things such as resolution and bandwidth used. You can try using different USB cable (and different port) to see if things improve. It would be also nice to have some information of the system as described in bug report template

Closing due to inactivity, please reopen if you have further questions/remarks.


SearChain package reproduced using Llama_index library

Description
This is an incremental contribution. We reproduce the SearChain framework using Llama_index. This helps more people use it.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
We provide an example notebook. And we have tested our code and the relevant data can be found in the  SearChain code base.

[x] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

Could you please provide me with some guidance on how to successfully navigate through this test?

Could you please provide me with some guidance on how to successfully navigate through this test?

Hey you need a couple more BUILD files. You can create them manually, or you could add me to your fork and I can make the push from my end.
llama_index/packs/searchain/BUILD
python_sources()

tests/BUILD
python_tests()

Once those are added, that should pass checks.

Could you please provide me with some guidance on how to successfully navigate through this test?

Hey you need a couple more BUILD files. You can create them manually, or you could add me to your fork and I can make the push from my end.
llama_index/packs/searchain/BUILD
python_sources()

tests/BUILD
python_tests()

Once those are added, that should pass checks.

Thank you very much, I'll try it by myself first.

Thanks @DJC-GO-SOLO -- merging now!


While trying to connect drillbit nodes using zk style from local its throws no known host.

Describe the bug
While connecting from drillbit style I m able to connect and do all such query, but if I use zk style it doesn't work. instead it throws error as : below image

So the only way which I can connect with zk style from my local is to edit my etc/hosts file and add host IP and address like below
<IP_ADDRESS> drill-data-poc-m.us-central1-b.c.stoked-jigsaw-327806.internal
plus I ssh into the one of the nodes and try to login via those nodes I m able to use the zk style and I m able to login using external IP
as below :

but using the same external IP I m not able to login from my local its not working.
For testing its fine to add in etc/hosts file and connect but in production we would have N number of nodes we can't just add the IP and address of the nodes in etc/hosts every time.
To Reproduce
Steps to reproduce the behavior:
1.Install drillbit with zk quorum in 3 nodes with prerequisites showed in this link :  https://drill.apache.org/docs/distributed-mode-prerequisites/
2.use the zk style to connect from your local :  jdbc:drill:zk=:2181/drill/drill-data-poc
3. once you get a error : No such host is known
4. add the ip and node address in etc/hosts
5. now try to run the same command you will be able to connect.
Expected behavior
The Expected behavior is I should just connect to dill bit nodes when I enter my connection details but its not happening until I add the IP and node address details in etc/hosts file.
Desktop (please complete the following information):

OS: windows 10 , ubuntu 20.04
Version Drill 1.19

@cgivre @luocooong  @jnturton

hostnames ending with xxx.internal does not look like normal hostname configuration. Is the /etc/hostname of all nodes that run the drillbits configured with a hostname you can find on a public DNS, so that your local machine could find it? Drill should use this config to store it within zookeeper.

Hi @Z0ltrix
The hostname is been automatically assign by drillbit at the time of drillbit startup script which uses drill-env.sh so this time I added the hostname in drill-env.sh.
default setup address given by drillbit  drill-env.sh

after custom name given in  drill-env.sh  with hostname of the vm in drill-env.sh

So now zookeeper/conf/zoo.cfg , drill/conf/drill-override.conf, and  drill/conf/drill-env.sh have a same hostname
After that change when I try to connect with zk style I get a error : No active Drillbit endpoint found from ZooKeeper. Check connection parameters?

Any idea why isn't it connecting with zk style but even now it connects with drillbit style ?

Hi @mohamedkashifuddin,
you need to configure fqdn for your drillbits within your cloud provider UI and within /etc/hosts so that all systems can find each other and your local laptop can find the drillbits with the address you can see in the web UI of Drill.
For ZK connection Drill stores just its own address within zookeeper. Your client reads this entry and tries to reach it from client Side, so its important to configure real fqdn.
The drillbits do the same between them for internal communication.

Hi @Z0ltrix Thanks for the information, But it would be great if you could give example what should be within /etc/hosts.
This is my testing environment so the vms contain external IP, In our actual environment non of the vms would have a external IP so we wouldn't need to config DNS with our cloud provider.
It would be great if you give a eg to refer:
My current hosts file looks like this below
cat /etc/hosts
<IP_ADDRESS> localhost

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
<IP_ADDRESS> metadata.google.internal metadata```

Hi @Z0ltrix Thanks for the information, But it would be great if you could give example what should be within /etc/hosts. This is my testing environment so the vms contain external IP, In our actual environment non of the vms would have a external IP so we wouldn't need to config DNS with our cloud provider.
It would be great if you give a eg to refer: My current hosts file looks like this below
cat /etc/hosts
<IP_ADDRESS> localhost

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
<IP_ADDRESS> metadata.google.internal metadata

This means in your production environment you do not want to connect the drillbits from outside?
An adequate example with a minimal drill/zookeeper production environment should have the following nodes:

zookeeper1
zookeeper2
zookeeper3
drillbit1
drillbit2
drillbit3

let's assume that we have only internal communication, so we are not in need of any DNS provider.
zookeeper1
/etc/hostname:
zookeeper1.my.great.cluster.com

/etc/hosts:
<IP_ADDRESS> localhost

<IP_ADDRESS> zookeeper1 zookeeper1.my.great.cluster.com
<IP_ADDRESS> zookeeper2 zookeeper2.my.great.cluster.com
<IP_ADDRESS> zookeeper3 zookeeper3.my.great.cluster.com
<IP_ADDRESS> drillbit1 drillbit1.my.great.cluster.com
<IP_ADDRESS> drillbit2 drillbit2.my.great.cluster.com
<IP_ADDRESS> drillbit3 drillbit3.my.great.cluster.com

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
<IP_ADDRESS> metadata.google.internal metadata

zookeeper2
/etc/hostname:
zookeeper2.my.great.cluster.com

/etc/hosts:
<IP_ADDRESS> localhost

<IP_ADDRESS> zookeeper1 zookeeper1.my.great.cluster.com
<IP_ADDRESS> zookeeper2 zookeeper2.my.great.cluster.com
<IP_ADDRESS> zookeeper3 zookeeper3.my.great.cluster.com
<IP_ADDRESS> drillbit1 drillbit1.my.great.cluster.com
<IP_ADDRESS> drillbit2 drillbit2.my.great.cluster.com
<IP_ADDRESS> drillbit3 drillbit3.my.great.cluster.com

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
<IP_ADDRESS> metadata.google.internal metadata

zookeeper3
/etc/hostname:
zookeeper3.my.great.cluster.com

/etc/hosts:
<IP_ADDRESS> localhost

<IP_ADDRESS> zookeeper1 zookeeper1.my.great.cluster.com
<IP_ADDRESS> zookeeper2 zookeeper2.my.great.cluster.com
<IP_ADDRESS> zookeeper3 zookeeper3.my.great.cluster.com
<IP_ADDRESS> drillbit1 drillbit1.my.great.cluster.com
<IP_ADDRESS> drillbit2 drillbit2.my.great.cluster.com
<IP_ADDRESS> drillbit3 drillbit3.my.great.cluster.com

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
<IP_ADDRESS> metadata.google.internal metadata

drillbit1
/etc/hostname:
drillbit1.my.great.cluster.com

/etc/hosts:
<IP_ADDRESS> localhost

<IP_ADDRESS> zookeeper1 zookeeper1.my.great.cluster.com
<IP_ADDRESS> zookeeper2 zookeeper2.my.great.cluster.com
<IP_ADDRESS> zookeeper3 zookeeper3.my.great.cluster.com
<IP_ADDRESS> drillbit1 drillbit1.my.great.cluster.com
<IP_ADDRESS> drillbit2 drillbit2.my.great.cluster.com
<IP_ADDRESS> drillbit3 drillbit3.my.great.cluster.com

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
<IP_ADDRESS> metadata.google.internal metadata

drillbit2
/etc/hostname:
drillbit2.my.great.cluster.com

/etc/hosts:
<IP_ADDRESS> localhost

<IP_ADDRESS> zookeeper1 zookeeper1.my.great.cluster.com
<IP_ADDRESS> zookeeper2 zookeeper2.my.great.cluster.com
<IP_ADDRESS> zookeeper3 zookeeper3.my.great.cluster.com
<IP_ADDRESS> drillbit1 drillbit1.my.great.cluster.com
<IP_ADDRESS> drillbit2 drillbit2.my.great.cluster.com
<IP_ADDRESS> drillbit3 drillbit3.my.great.cluster.com

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
<IP_ADDRESS> metadata.google.internal metadata

drillbit3
/etc/hostname:
drillbit3.my.great.cluster.com

/etc/hosts:
<IP_ADDRESS> localhost

<IP_ADDRESS> zookeeper1 zookeeper1.my.great.cluster.com
<IP_ADDRESS> zookeeper2 zookeeper2.my.great.cluster.com
<IP_ADDRESS> zookeeper3 zookeeper3.my.great.cluster.com
<IP_ADDRESS> drillbit1 drillbit1.my.great.cluster.com
<IP_ADDRESS> drillbit2 drillbit2.my.great.cluster.com
<IP_ADDRESS> drillbit3 drillbit3.my.great.cluster.com

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
<IP_ADDRESS> metadata.google.internal metadata

As you can see, /etc/hosts is equal on every machine, so that all can find each other without DNS.
The internal ip's has to be changed to the real interla ip's of your cloud provider.
Now Drill should register itself with drillbit1-3.my.great.cluster.com within zookeeper and each node can find the other ones.

@mohamedkashifuddin Did this get sorted out?  Can we close this?

@cgivre Yes we can close it


Documentation - Read The Docs

Create a Read The Docs project and documentation for fwfr.

I'll assign this to me once I get the contributor permissions.


import/no-cycle does not work for typescript files

I used the first sample from here:
https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-cycle.md
but changed extension for files from .js to .ts.
My eslint configuration:
.eslintrc.js
module.exports = {
  plugins: ["import"],
  parser: "@typescript-eslint/parser",
  parserOptions: {
    ecmaVersion: 2017,
    project: "tsconfig.json",
    sourceType: "module"
  },
  rules: {
    "import/no-cycle": "error",
  },
};

For .ts files the rule does not work.
But when I change extension back to .js it works again.
NOTE:
I made sure that .ts files are actually checked by eslint by adding code that triggers core eslint rule.
So, I am sure that the issue is not because .ts files are not checked.

close in favor of https://github.com/import-js/eslint-import-resolver-typescript


Reference counts not managed correctly when Reference types are returned from a GDNative node?

Godot version:
3.2
OS/device including version:
Windows 10
Issue description:
In certain situations References don't seem to be dereferenced as I would expect them to, leading to memory leaks. Perhaps I am doing something wrong or have some misunderstanding.
For clarity's sake here are two examples where References work as expected, and a third example where they do not.
Thing is a class derived from Reference
class Thing : public Reference {
    GODOT_CLASS(Thing, Reference);
public:
    Thing() {
        std::cout << "Thing created" << std::endl;
    }
    ~Thing() {
        std::cout << "Thing deleted" << std::endl;
    }
    void _init() {}
};

Example 1 - Instantiating in gdscript (works as expected)
var Thing:Resource = preload("res://bin/Thing.gdns")
...
func _ready():
    var thing = Thing.new()

    # var goes out of scope, thing is deleted because there are no references left.

Output:
Thing created
Thing deleted

Example 2 - Instantiating in gdscript and passing the reference to a GDNative object to store (also works as expected)
class ThingHolder : public Node {
    GODOT_CLASS(ThingHolder, Node);
    Ref<Thing> thing_to_hold;
public:
    static void _register_methods() {
        register_method("hold_thing", &ThingHolder::hold_thing);
    }
    void _init() {}
    void hold_thing(Ref<Thing> thing) {
        thing_to_hold = thing
    }
};

func _ready():
    var thing = Thing.new()

    # ThingHolder loaded as Autoload node
    ThingHolder.hold_thing(thing)

    # var goes out of scope, ThingHolder still holds a reference to the
    # thing, so the object is not deleted yet.

As expected, "Thing deleted" is not printed until game shutdown when the ThingHolder is destructed.
Example 3 - Instantiating in GDNative and returning a Ref (does not work as expected)
class ThingCreator : public Node {
    GODOT_CLASS(ThingCreator, Node);
public:
    static void _register_methods() {
        register_method("make_thing", &ThingCreator::make_thing);
    }
    void _init() {}
    Ref<Thing> make_thing() {
        return Ref<Thing>(Thing::_new()); // (Correct?? Can't find any documentation on this.)
    }
};

func _ready():
    # ThingCreator loaded as Autoload node
    var thing = ThingCreator.make_thing()

    # At this point, there is only one logical reference to the thing, so it
    # should be deleted when var goes out of scope.

"Thing created" is printed but "Thing deleted" is never printed. When the game exits we get the familiar message:
WARNING: cleanup: ObjectDB Instances still exist!
     At: core/object.cpp:2071
ERROR: clear: Resources Still in use at Exit!
   At: core/resource.cpp:476

This may be an issue in https://github.com/GodotNativeTools/godot-cpp
How does godot-cpp pass/receive Reference to/from ptrcall? Reference is returned from ptrcall as Ref<Reference> instead of Reference *.

This? https://github.com/GodotNativeTools/godot-cpp/issues/215

Yes Seems related. The __internal_constructor() workaround mentioned there does work.


"Error processing 'configurationDone' request. Unknown Error: 0x89720010" on dotnet core debugging.

I originally posted this issue to vs code repository(https://github.com/Microsoft/vscode/issues/57840), but the team said it related with this extension. So i write my issue here again.
OS : Windows 10 64bit.
I cloned the vs code repository today, and installed all the prerequisites(yarn, python2.7, node, vs2017 community, etc...).
Atfer that, i ran the command 'yarn' and launched vs code by command 'code.bat'
vs code runs fine, so i do some debugging test on dotnet core console project.
with C# for Visual Studio Code extension(installed with vsix, because extension market doesn't works), intellisense works well... but,
when i start debugging with f5 it stop with error "Error processing 'configurationDone' request. Unknown Error: 0x89720010" and chrome debug console displays error log like below,
Error processing 'threads' request. Unknown Error: 0x9233000b: Error: Error processing 'threads' request. Unknown Error: 0x9233000b
at file:///C:/Users/mentoreet/vscode2/out/vs/workbench/parts/debug/electron-browser/rawDebugSession.js:190:119
at Object.notifyError [as _notify] (file:///C:/Users/mentoreet/vscode2/out/vs/base/common/winjs.base.js:1230:50)
at Object.enter (file:///C:/Users/mentoreet/vscode2/out/vs/base/common/winjs.base.js:916:30)
at Promise_ctor._run (file:///C:/Users/mentoreet/vscode2/out/vs/base/common/winjs.base.js:1089:29)
at Promise_ctor._error (file:///C:/Users/mentoreet/vscode2/out/vs/base/common/winjs.base.js:1062:18)
at file:///C:/Users/mentoreet/vscode2/out/vs/workbench/parts/debug/electron-browser/rawDebugSession.js:207:25
at DebugAdapter.AbstractDebugAdapter.acceptMessage (file:///C:/Users/mentoreet/vscode2/out/vs/workbench/parts/debug/node/debugAdapter.js:95:25)
at DebugAdapter.StreamDebugAdapter.handleData (file:///C:/Users/mentoreet/vscode2/out/vs/workbench/parts/debug/node/debugAdapter.js:148:38)
at Socket. (file:///C:/Users/mentoreet/vscode2/out/vs/workbench/parts/debug/node/debugAdapter.js:121:64)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:594:20)

and launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": ".NET Core Launch (console)",
"type": "coreclr",
"request": "launch",
"preLaunchTask": "build",
"program": "${workspaceFolder}/bin/Debug/netcoreapp2.1/test5.dll",
"args": [],
"cwd": "${workspaceFolder}",
"console": "internalConsole",
"stopAtEntry": false,
"internalConsoleOptions": "openOnSessionStart"
}
]
}

I totally have no idea why i got this error.
Could somebody shed some light on this issue please?
Thank you for reading.

@mentoreet The issue is that the C# extension debugger only supports running in official releases of VS Code. So you will need to use the official install if you want C# debugging.

@mentoreet there is no way to do what you are trying to do and still have C# debugging - the C# debugger is licensed to only run in the official version of VS Code.


IVS events not going to HA

After the recent update of HA core and also my Dahua NVR, i lost IVS events being processed by HA.
Tripwire and Intrusion (crossline detection, cross region detection) are now not being recognized by HA.
im not sure if the NVR update did it, or if the HA update did it.
does any one have any similar problems?
the video stream works, i can see all the entities but things like motion detection alarm, or the cross region or crossline detection is showing as "cleared"  or "idle"  but there is nothing in the logs to show any activity of these events.
can anyone help me with this issue?
also strangely my gdmss app (official dahua app) is not receiving push notifications.  Live video and playback is working fine, but i wonder if the NVR update somehow changed something.
any ideas guys?
thank you
JD

Hi Rroler,
any info on whether HA can now receive the cross line or cross region notifications from Dahua?
im still not getting any events when i look at the log for any of the cameras.
i completely deleted all cameras and reintegrated them with the Dahua integration.
is there any special way how to update the Dahua plug in?
thank you for your help. really really appreciate it in advance.
JD

Hi RRoler,
is there any special way to activate the various events from the camera to be sent to HA ?
i was using motion detection or cross region or cross line events to activate certain automations. but right now im not getting any activity from these entities of the camera.
is this feature still supported with the latest update or its not possible?
i can see the video stream ok, but i get no events from these entities.
none of them are disabled so they should be working.
any ideas???
please help  :(


Add support for ModelName (io:SomfySensorName)

[ ] I have read the README, including the advanced section regarding debugging.

Device information
A clear and concise description of the device, together with specific usecases that you would like to see supported.
wulde lie to be able to turn on off and sett temp and fan speed,  shift modes
Device details  spx-wfg01

Hub: [e.g. Cozytouch, eedoums, Hi Kumo, Rexel, Somfy Connexoon, Somfy TaHoma]
HI kumo

Device commands

Can you please provide edit your issue, there is almost nothing to help us to implement what you want.

@chali272 looking at spx-wfg01, I assume you use Hi Kumo, however as @tetienne we need way more information. Please have a look at the README (https://github.com/iMicknl/ha-tahoma/blob/master/README.md#device-not-supported).
In the mean-time, you could give https://github.com/iMicknl/ha-tahoma/archive/refs/heads/feature/support_HitachiAirToAirHeatPump.zip
a try. Extract this file and place custom_components/tahoma in your custom_components folder.

Can you please provide edit your issue, there is almost nothing to help us to implement what you want.

sorry im not shore how/were to put the different info, is it betting the ** it should be placed?
i have updated it is this better or do i need to ad something more?

@chali272 apologies for the late reply. Did you already sort this out / are you still looking for help?

i never got it working

Can you please provide edit your issue, there is almost nothing to help us to implement what you want.

sorry im not shore how/were to put the different info, is it betting the ** it should be placed?
i have updated it is this better or do i need to ad something more?

What was unclear about my instructions? If you download the zip file I referenced above. You can extract it and it has a custom_components folder with the tahoma folder inside. Copy this tahoma folder and place it in your custom_components folder.


Long running operation failed with status 'Failed'. Additional Info:'The 'location' property must be specified for 'amba-id-amba-prod-001'

Hello
when I try to deploy AMBA using Azure CLI or Azure PowerShell and I use default parameter:
"bringYourOwnUserAssignedManagedIdentity": {
"value": "No"
},
then I receive following error when I try what-if deployment
New-AzManagementGroupDeployment :
InvalidDeployment - Long running operation failed with status 'Failed'. Additional Info:'The 'location' property must be specified for 'amba-id-amba-prod-001'. Please see https://aka.ms/arm-deployment-subscription for usage details.'
when I look into the template, there is a template error only affecting me when bringYourOwnUserAssignedManagedIdentity equals 'No'
Template validation failed: The template resource 'Microsoft.WindowsAzure.ResourceStack.Frontdoor.Common.Entities.TemplateGenericProperty`1[System.String]' at line '29' and column '9' is invalid. 'ResourceGroup' property is not allowed for for the current template deployment. Please see https://aka.ms/arm-template/#resources for usage details.arm-template (validation)
userAssignedManagedIdentity.json(29, 9): The error occurred in a linked template near here
all works when I use bringYourOwnUserAssignedManagedIdentity equals 'Yes' and I add resource ID of my UAMI using bringYourOwnUserAssignedManagedIdentityResourceId parameter

Hello @Pawel1985  ,
thanks for your feedback. This issue has been already reported in #GH ISSUE 230. A User Assigned Managed Identity is now required and you have the option to either use your existing one or to create a new one during the deployment. Should you use your own, make sure it has the Monitoring Reader role assigned at the pseudoRoot management group. Documentation is in the process of being updated.
If you set the parameter to No, make sure check if you put the subscription id of the management subscription in the parameter file.

Thanks,
Bruno.

thanks a lot @Brunoga-MS


[Bug][TIR] Invalid loop vectorization and buffer compaction

When using an alloc_buffer that is not initialized or written out, CompactBufferAllocation and LoopVectorize passes perform invalid rewrites. Technically these could be considered correct because the changes have no effect on output, but they are very confusing when inspecting the lowered code.
Example script:
import tvm
from tvm.script import tir as T

@T.prim_func
def blis_gemm_microkernel_template(c: T.handle):
    A_pack = T.alloc_buffer((8,), "float32", scope="local")
    B_pack = T.alloc_buffer((8,), "float32", scope="local")
    C = T.match_buffer(c, (8,8))

    for loop in range(1000):
        for rii in T.unroll(8):
            for rjj in T.vectorized(8):
                C[rii, rjj] += A_pack[rii] * B_pack[rjj]

if __name__ == "__main__":
    with tvm.transform.PassContext(opt_level=3):
        print(tvm.lower(blis_gemm_microkernel_template, "llvm -mcpu=znver3"))

    with tvm.transform.PassContext(opt_level=3, disabled_pass=["tir.CompactBufferAllocation"]):
        print(tvm.lower(blis_gemm_microkernel_template, "llvm -mcpu=znver3"))

Output:
@main = primfn(c: handle) -> ()
  attr = {"global_symbol": "main", "tir.noalias": True}
  buffers = {C: Buffer(C_1: Pointer(global float32), float32, [64], [])}
  buffer_map = {c: C} {
  allocate(A_pack: Pointer(local float32x8), float32x8, [1]), storage_scope = local;
  allocate(B_pack: Pointer(local float32x8), float32x8, [1]), storage_scope = local;
  for (loop: int32, 0, 1000) {
    C[ramp(0, 1, 8)] = (C[ramp(0, 1, 8)] + (A_pack_1: Buffer(A_pack, float32x8, [1], [], scope="local")[0]*B_pack_1: Buffer(B_pack, float32x8, [1], [], scope="local")[0]))
    C[ramp(8, 1, 8)] = (C[ramp(8, 1, 8)] + (A_pack_1[0]*B_pack_1[0]))
    C[ramp(16, 1, 8)] = (C[ramp(16, 1, 8)] + (A_pack_1[0]*B_pack_1[0]))
    C[ramp(24, 1, 8)] = (C[ramp(24, 1, 8)] + (A_pack_1[0]*B_pack_1[0]))
    C[ramp(32, 1, 8)] = (C[ramp(32, 1, 8)] + (A_pack_1[0]*B_pack_1[0]))
    C[ramp(40, 1, 8)] = (C[ramp(40, 1, 8)] + (A_pack_1[0]*B_pack_1[0]))
    C[ramp(48, 1, 8)] = (C[ramp(48, 1, 8)] + (A_pack_1[0]*B_pack_1[0]))
    C[ramp(56, 1, 8)] = (C[ramp(56, 1, 8)] + (A_pack_1[0]*B_pack_1[0]))
  }
}

@main = primfn(c: handle) -> ()
  attr = {"global_symbol": "main", "tir.noalias": True}
  buffers = {C: Buffer(C_1: Pointer(global float32), float32, [64], [])}
  buffer_map = {c: C} {
  allocate(A_pack: Pointer(local float32x8), float32x8, [8]), storage_scope = local;
  allocate(B_pack: Pointer(local float32), float32, [64]), storage_scope = local;
  for (loop: int32, 0, 1000) {
    C[ramp(0, 1, 8)] = (C[ramp(0, 1, 8)] + (A_pack_1: Buffer(A_pack, float32x8, [8], [], scope="local")[0]*B_pack_1: Buffer(B_pack, float32, [64], [], scope="local")[ramp(0, 9, 8)]))
    C[ramp(8, 1, 8)] = (C[ramp(8, 1, 8)] + (A_pack_1[1]*B_pack_1[ramp(0, 9, 8)]))
    C[ramp(16, 1, 8)] = (C[ramp(16, 1, 8)] + (A_pack_1[2]*B_pack_1[ramp(0, 9, 8)]))
    C[ramp(24, 1, 8)] = (C[ramp(24, 1, 8)] + (A_pack_1[3]*B_pack_1[ramp(0, 9, 8)]))
    C[ramp(32, 1, 8)] = (C[ramp(32, 1, 8)] + (A_pack_1[4]*B_pack_1[ramp(0, 9, 8)]))
    C[ramp(40, 1, 8)] = (C[ramp(40, 1, 8)] + (A_pack_1[5]*B_pack_1[ramp(0, 9, 8)]))
    C[ramp(48, 1, 8)] = (C[ramp(48, 1, 8)] + (A_pack_1[6]*B_pack_1[ramp(0, 9, 8)]))
    C[ramp(56, 1, 8)] = (C[ramp(56, 1, 8)] + (A_pack_1[7]*B_pack_1[ramp(0, 9, 8)]))
  }
}

The first output incorrectly has A_pack_1 accesses as all being 0 when they should be 0-7. The second output has an incorrect ramp with a stride of 9.
@vinx13 @junrushao1994

CompactBufferAllocation requires intermediate buffer inside kernels to have both writers and readers in order to calculate the actual shape needed for allocation. If you have already specified the compacted shape, you can disable both tir.CompactBufferAllocation and tir.PlanAndUpdateBufferAllocationLocation, to keep buffer allocation and its shape as specified in the original TIR script.


Bump versions used in smoke tests

@bot-gradle help

Currently I support the following commands:

@bot-gradle test {BuildStage} to trigger a build

e.g. @bot-gradle test SanityCheck plz
SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/ReadyForMerge/ReadyForNightly/ReadyForRelease are supported
test this means test ReadyForMerge
test and merge to trigger a pre-tested commit build
cancel to cancel a running pre-tested commit build or remove it from queue
SanityCheck can be abbreviated as SC, ReadyForMerge as RFM, etc.
Specific builds:

AST: AllSmokeTestsReadyForMerge
AFT: AllFunctionalTestsReadyForMerge
ASB: AllSpecificBuildsReadyForMerge
ACC: AllConfigCacheTestsReadyForMerge
ACT: AllCrossVersionTestsReadyForNightly
APTN: AllPerformanceTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle help to display this message
@bot-gradle clean to clear the conversation history

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test qf

OK, I've already triggered QuickFeedback build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Can't open db file when creating Magnitude Object

I tried following the instructions, downloaded a db file and tried out the code
vectors = Magnitude(MAG_PATH)

The file is definitly there but i got an error
sqlite3.OperationalError: unable to open database file
When looking at the code this seems to get executed starting at line 346
    if self.fd:
         conn = sqlite3.connect('/dev/fd/%d' % self.fd,
          check_same_thread=False)
    else:
        conn = sqlite3.connect(self.path, check_same_thread=False)
        self._create_empty_db(conn.cursor())

right at the start of the _db() method.
self.fd seems to get set whenever path is not none in the init method
it is the return code of os.open(path)
So the path that is tried to open is "/dev/fd/3/" instead of the actual database path
Seems to work when i change the line
conn = sqlite3.connect('/dev/fd/%d' % self.fd,
          check_same_thread=False)

to
conn = sqlite3.connect(self.path,
          check_same_thread=False)

What operating system are you using? macOS and Linux support '/dev/fd/' paths but Windows does not. I wasn't originally targeting support for Windows, but if this is an issue for you I'm happy to fix it to make it compatible.

Yes i'm using windows.

This got fixed in the update. Thanks Ajay.


A patch release for AzureCommunicationCommon 1.1.1

Fixed the logic of PhoneNumberIdentifier to always maintain the original phone number string whether it included the leading + sign or not.

Why is this considered a bug? What benefit is there to not standardize the phone number?

Why is this considered a bug? What benefit is there to not standardize the phone number?

@tjprescott  While using the createIdentifierFromRawId by passing an e164 formatted number such as '+123456789` the response is a PhoneNumberIdentifier, but the phoneNumber property of the PhoneNumberIdentifier has two ++ at the beginning, like '++123456789' and it caused issue for our customers, so we decided to do not add plus sign internally and fixed it in this PR https://github.com/Azure/azure-sdk-for-ios/pull/1391

@tjprescott the problem mentioned by @AikoBB is just the tip of the iceberg.
The main motivation behind #1391 was that the MRI format without a + sign wasn't canonical to ACS and IC3 services. Moreover, we found out that some of the IC3 infra works with 4: MRIs such as 4:{guid}, 4:{E.164}_{guid}, 4:{guid}_{guid}. So, if we ever wanted to support other than E.164-based MRIs we shouldn't assume the PhoneNumber MRI format and keep whatever is after the leading 4:.
CC'ing @williamzhao87 (who originally called out the issue) and @DominikMe (who we've agreed on the approach with) to add any more context.


Self-service publishing to Pulumi Registry

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
With the launch of Pulumi Registry, we now have a single place to collect all of the Pulumi Packages–both Providers & Components–that are available. As a follow up, we should make it possible for members of the Pulumi community to publish their own Pulumi Packages without having to contact Pulumi.

As a first step, we should look at how we want to accept PRs into this repos now that the 3rd party plugin publishing and acquisition are unblocked.

12/21 Triage:  Dropping this into next iteration to discuss at planning - we think Praneet has the most context here, and he's out for the holidays.


DSAdmin crashes when changing namespace from default

Hi! Thanks for making this killer application.
We're trying to use it with the datastore emulator at my company, but we're running into a problem when switching namespaces. The entire application simply crashes.
Let me know what information you need to debug this and I'll happily provide:)

@FredrikAugust I tried it against my test setup with namespaces, but I can't reproduce it yet.
Do you do anything else before switching namespaces?
Can you start a development server (see the README for instructions; you'll want to run it against your own datastore server) and make it crash; this should give more useful backtraces.

If I'm not mistaken, the crash is happening in encodeKey, called from the EntitiesTable. This seems to mean that the key doesn't have a partitionId, which is strange (as far as I understand, partitionId is required; i would especially expect it to be there if you have a namespace).
What could help is that you add extra logging in encodeKey to see what the key actually contains (to double check that it actually is a key, but somehow incomplete, or something else).

Hi, thanks for the quick response! I'll try it right away and report back.

Do you do anything else before switching namespaces?

Nope! If it's of any interest, we're running the datastore emulator through a docker image:
  datastore:
    image: google/cloud-sdk:latest
    ports:
      - 8432:8432
    command: |
      gcloud beta emulators datastore start --host-port=<IP_ADDRESS>:8432 --use-firestore-in-datastore-mode --project=***

I've started the dev server, and reproduced the crash. The errors I get in the console are the following (I stripped away stack traces from React core):
Uncaught Error: Duplicate columns were found with ids: "key" in the columns array above
    at useTable3 (useTable.js:262:13)
    at Table (Table.tsx:60:7)

The above error occurred in the <Table> component:
    at Table (http://localhost:64645/dist/index.js:40562:5)
    at EntitiesTable (http://localhost:64645/dist/index.js:40758:5)
    at KindTable (http://localhost:64645/dist/index.js:45780:5)
    at div
    at KindPage (http://localhost:64645/dist/index.js:45843:5)
    at Route (http://localhost:64645/dist/index.js:39912:18)
    at Switch (http://localhost:64645/dist/index.js:39943:19)
    at div
    at DatastoreAdminView (http://localhost:64645/dist/index.js:46466:33)
    at Router (http://localhost:64645/dist/index.js:39905:42)
    at APIProvider (http://localhost:64645/dist/index.js:39518:5)
    at QueryClientProvider3 (http://localhost:64645/dist/index.js:23220:27)
    at DatastoreAdmin (http://localhost:64645/dist/index.js:46584:29)

Uncaught Error: Duplicate columns were found with ids: "key" in the columns array above
    at useTable3 (useTable.js:262:13)
    at Table (Table.tsx:60:7)

When browsing the "main page" the key values are:
{
    "partitionId": {
        "projectId": "xxx"
    },
    "path": [
        {
            "kind": "xxx:namespace",
            "name": "xxx"
        }
    ]
}

and the "encoded key" value is:
[
    "xxx",
    "",
    [
        [
            "xxx:namespace",
            "xxx"
        ]
    ]
]

Am I right that you have an entity that has key as a property name?
I was able to reproduce a crash in that situation. I'll fix that.

@FredrikAugust Can you try again with the latest commit?

Am I right that you have an entity that has key as a property name?
I was able to reproduce a crash in that situation. I'll fix that.

@emmahorn could you confirm or deny this?

@remko Works like a charm with latest commit (ccd3ebc5d18028c66aa5d8c86fb388d2299a0bb8)!

Great!
I published a new version with the fix (v0.18.2)


Merge packages into a single voodoo package

Extracted from #62
Depends on #73

Hi, merging voodoo packages in a single package means that:

voodoo-prep won't be installable for OCaml >= 4.03 & < 4.08
any change in voodoo will require the CI to rebuild everything. This is very costly. When the packages are separated, we can easily figure out whether changes are impacting the prep step.

I'd like to remove support for <4.08 at some point in the near future, but not yet. In fact, we may want voodoo support for older OCamls to outlast odoc's (we'll just use an older odoc for older ocamls, potentially).

Sorry, I didn't give enough context on https://github.com/ocaml-doc/voodoo/pull/62. This is one of the changes of that PR that aren't feasible because the individual caching of build artifacts for the prep, do, and gen steps is valuable. :slightly_smiling_face:

Thanks for the explanation, let's close this PR then!


build(datasets): Release kedro-datasets 1.7.0

Description
Release kedro-datasets 1.7.0
Development notes

Checklist

[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added a description of this change in the relevant RELEASE.md file
[ ] Added tests to cover my changes

I'm glad to see the RTD build is catching the indentation error for the polars dataset, but kind of strange it didn't flag when that was merged? 🤔 @astrojuanlu

I'm glad to see the RTD build is catching the indentation error for the polars dataset, but kind of strange it didn't flag when that was merged? 🤔 @astrojuanlu

It wasn't added to the .rst file before.

It wasn't added to the .rst file before.

Ugh, exactly, sorry about that. Should we try to make it automatic? Or at least add a checklist item in the pull request template.

Finally fixed the docstring! Please review, @merelcht @astrojuanlu @SajidAlamQB!


add shorthand CLI flag for --version

Fixes #366

@bengry I have merged previous PR. However I'm going to close this one as we have another person with fixes for both. Thank you so much for contribution


Reimplement util::MakeString(NSString*)

It turns out that -[NSString UTF8String] is almost assuredly copying the data into an autoreleased NSData and then returning a pointer into that buffer rather than exposing any internal state.
This change reimplements MakeString by bridging to CFString and then using CFString functions to copy directly into a std::string, saving a copy. Also, added a benchmark to show that this really works. Indeed, before:
Running Release/Firestore/Example/Benchmarks/firebase_firestore_util_string_apple_benchmark
Run on (8 X 2900 MHz CPU s)
CPU Caches:
  L1 Data 32K (x4)
  L1 Instruction 32K (x4)
  L2 Unified 262K (x4)
  L3 Unified 8388K (x1)
-----------------------------------------------------
Benchmark              Time           CPU Iterations
-----------------------------------------------------
BM_MakeString         63 ns         63 ns   86984076

After:
BM_MakeString         30 ns         30 ns  187703856

Note that this change is diffbased on the union of #1670, #1671, and #1672. Once those land, I'll retarget this to master.

Also note that under the same setup, MakeStringView clocks in this way:
BM_MakeStringView         59 ns         59 ns   96293558

This essentially means that it would be cheaper to just create our std::string than use MakeStringView at all. I'll tackle this in a follow-up.


MiCaller

Hello,
When i test MiCaller with CMS100MI Api.
I have an error result => '{errorCause=mvx.app.ds.sCMS100MIRLst_MSHAPP002, errorMessage=Unable to load class mvx.app.ds.sCMS100MIRLst_MSHAPP002, error=true}'
Do you have a solution ? Thx.

Hi,
CMS100MI transactions are not supported through MiCaller. This should be done instead through ION API.


Linear Search with C#

I can write the code for linear search in C#, please assign it to me :)

Hello @BasakDemirok , this issue has been assigned to you. No more contributors required at the moment.
Important:
Before you start your work on this issue, make sure you go through the README.md and Contribution Guidelines.md
File structure:

In the searching directory, navigate to `Linear Search1
Create the C# directory
Create the file LinearSearch.cs.

Here's how the final structure should look like:

Searching

Linear Search

Algorithm.md
C#

LinearSearch.cs

Please follow the same naming conventions as mentioned in this comment.
Before you create a pull request, if you observe that the folder Heap Sort has already been created, then please refrain from creating a new one, make some changes in your forked repository so that it matches with the current one and there are no conflicts.
Note that all PRs are being checked for plagiarism, please refrain from indulging in any crooked means, we trust you!
We thank you for your contribution and time and we hope that you enjoy contributing to open source.


ledger patch

This replaces the 99designs keyring with the cosmos keyring fork of the
same lib

You need to rebase this on top of the rc-1 branch if you want to use rc-1, because a bunch of stuff has changed :)

no need to fix that which isn't broken.

no need to fix that which isn't broken.


nsc-events-nextjs_7_379_nvmrc

this is a partial resolve for #379 with a purpose to test Github Actions Auto Delployment.
Testing GH Action

This PR changes nothing but allows me to run the Github Actions of the Fork I mentioned above. Please approve if you can.


Installation and Removal of FanControl

In an attempt in using your utility to install FanControl I am presented with it supposedly being installed but no files are present on the computer to run the program afterwards. When attempting to then uninstall the program with your utility it is presented with an error. This is the print in powershell for both of those.
====Chris Titus Tech=====
=====Windows Toolbox=====
---        Winget is installed          ---
Version: v1.7.11261
- Winget is a release version.
- Winget is Up to Date
Winget is already installed.
@{winget=Rem0o.FanControl; choco=na}
Queueing Rem0o.FanControl for Winget install
---        Winget is installed          ---
Version: v1.7.11261
- Winget is a release version.
- Winget is Up to Date
Winget is already installed.
--    Configuring winget packages       ---
Starting install of Rem0o.FanControl with winget.
Found an existing package already installed. Trying to upgrade the installed package...
No available upgrade found.
No newer package versions are available from the configured sources.
Rem0o.FanControl No applicable update found
--      Installs have finished          ---
Queueing Rem0o.FanControl for Winget Uninstall
--    Configuring winget packages       ---
Found FanControl [Rem0o.FanControl]
Starting package uninstall...
An unexpected error occurred while executing the command:
0x800401f5 : Application not found
Failed to uninstall Rem0o.FanControl.
--       Uninstalls have finished       ---

Wrong repo. File an issue at https://github.com/ChrisTitusTech/winutil


Unable to XM-Parse the following data:

Error Message Unable to xml-parse the following data: %s
I am running Splunk <IP_ADDRESS>, and the app version is 4.1.0
Really not sure where to look to see what the cause  is.
Thanks for any help.

@BassXVII were you able to fix this issue? we are facing the same error


Autoupvoted comment

When user write comment inside a post, his comment upvoted automatically and upvoters counter add +1.
How I can fix this behavior? Thanks

Fix it how the comment is not upvoted? I'm afraid that's just the way it works, sorry… Why do you need to change it?

I think it's a little strange when a user writes a comment and automatically receives Like for own comment. Now it returns status upvoted, when writing any comments, and I want to prevent this action.

OK, I just pushed a commit to devel to make it easier to disable that behavior: https://github.com/TelescopeJS/Telescope/commit/31f3384e855b0f7f61787fdd5248b95455018d09
So once those changes are merged and published in the next version of Telescope, you should be able to just remove that callback with:
Telescope.callbacks.remove("commentSubmitAsync", "upvoteOwnComment");

Thanks for your help!


Managed token / readonly vault token changes

turn off renaming if vault token is readonly (managed token)
copy plain vault-token to vault-token-group_role before submitting if avaliable.

All regular-user tests have passed:

multiple job submissions across multiple schedds
All jobs run successfully (sleep 300 just to confirm that condor can get the credential to the job)

All managed token tests have passed (used dunepro):

Above + switching back/forth between DUNE Global pool and GPGrid

Unit tests pass
Approved.


Harami

Implemented harami candle and added bullish/bearish harami. Also added an optional bool if shadows needs to be contained or not.

@richardsjoberg Thanks for the PR 👍  I've merged it to v3.1 branch together with other developing features, you may also switch to v3.1 branch for your new PRs 😄

Great, thanks, ok sure i will switch to v3.1!


Training Data SIZE of NLLB-200

Hello! Sorry for the basic question.
I've been looking for the breakdown for size of NLLB-200 training data and couldn't found it.
The paper states that NLLB-200 was trained using 3.6B sentences from low resource languages and 40.1B sentences form high resource languages. But, I wasn't able to find the breakdown of this for each language.
Can someone tell me where to find this breakdown? Many thanks in advance!

https://data.statmt.org/cc-matrix/


Show more info

Hi,
It works perfect to me. thanks a lot.
But, when create a procedure: ie: CREATE OR REPLACE PROCEDURE
It does not show resutls. 3 windows are opened on blank.
Can we work together on this?
Regards

In the meantime, I'll note what I've confirmed.

It throws an error when I run it.
Three blank tabs are created.
As far as the web UI is concerned, there may not be much information to display.

@cedenoaugusto
I made it possible to display the result of create procedure.
Try v0.0.53.

hi @minodisk
great news!
regards


[zh-cn] resync optional-kubectl-configs-bash-linux.md

Capitalized the words shell and bash in the localized desc text. Need to confirm my changes are correct or not.
content/zh-cn/docs/tasks/tools/included/optional-kubectl-configs-bash-linux.md

do we need to capitalized these words, bash, shel ? @tengqm

do we need to capitalized these words, bash, shell ? @tengqm

I'd vote for capitalize the first character.

/approve

/lgtm


feat: improve blog style

Docs updates should not be submitted in this repository
Our doc site content is being automatically updated from Wing repository docs folder.
Please submit any changes to the docs as a PR here

approved!


Introduce Trivy Workflow

Proposed Trivy Workflow:

Scan for all vulnerabilities, list as table
Scan for CRITICAL and HIGH risk vulnerabilities. Will break on a vulnerability not in .trivyignore

Current workflow:

Build image
Scan image (2x)
Push image to ECR (if appropriate)

The minor issue is that we don't get to make use of a nice and tidy github action (i.e. Build and Push) to push to ECR. We're instead manually pushing under a "run" action. We have to manually tag the image and manually add the labels instead of having Docker Meta do the work for us.
It might be worthwhile just to rebuild the image if we push to ECR. We only rebuild the image if it's a push to main, so it's not a lot of extra work in the grand scheme.