Serilog.Sinks not working after upgrading to Elasticsearch 8.1.3

Does this issue relate to a new feature or an existing bug?

[x] Bug
[ ] New Feature

What version of Serilog.Sinks.Elasticsearch is affected?  Please list the related NuGet package.
8.4.1 and 9.0.0-beta4
What is the target framework and operating system? See target frameworks & net standard matrix.

[x] .Net Core 3.1
[x] .Net Standard 2.0
[x] .Net Framework 4.7.2
The main runtime is .Net Core 3.1 but I also have a  .Net Framework 4.7.2 project where i would like it to work.

Please describe the current behavior?
After updating to Elasticsearch 8.1.3 I am unable to write logs using serilog sinks.
The logs are written correctly to the bufferBaseFile and I can successfully Post an entry manually to a Elasticsearch 8.1.3 using Dev Console in Kibana without setting any component/index templates.
From Serilog Selflog i get the error:
Exception while emitting periodic batch from Serilog.Sinks.Elasticsearch.Durable.ElasticsearchLogClient: Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 400 from: POST /_bulk
   at Elasticsearch.Net.Transport`1.HandleElasticsearchClientException(RequestData data, Exception clientException, IElasticsearchResponse response)
   at Elasticsearch.Net.Transport`1.FinalizeResponse[TResponse](RequestData requestData, IRequestPipeline pipeline, List`1 seenExceptions, TResponse response)
   at Elasticsearch.Net.Transport`1.RequestAsync[TResponse](HttpMethod method, String path, CancellationToken cancellationToken, PostData data, IRequestParameters requestParameters)
   at Serilog.Sinks.Elasticsearch.Durable.ElasticsearchLogClient.SendPayloadAsync(List`1 payload, Boolean first)

I have tried with the 8..4.1 version, and have added the writeTo settings that should help with backwards compatability. Serilog creates a legacy index template that matches my provided IndexPattern.
I haven't been able to update to Serilog.Sinks.Elasticsearch version 9.0.0-beta4, as it requires a Serilog.Formatting.Elasticsearch which does not exist:
Serilog.Sinks.Elasticsearch 9.0.0-beta4 -> Serilog.Formatting.Elasticsearch (>= 9.0.0-beta4)
Please describe the expected behavior?
I am expecting to be able to see the logs that ar written to the BufferFile, being written to Elasticsearch to an Index matching my IndexPattern.
If the current behavior is a bug, please provide the steps to reproduce the issue and if possible a minimal demo of the problem
"WriteTo": [
      {
        "Name": "Elasticsearch",
        "Args": {
          "nodeUris": "{elastic cloud URL}",
          "indexFormat": "st-log-event-{0:yyyy.MM.dd}",
          "bufferBaseFilename": "C:\\Temp\\ElasticsearchEventBuffer_Web",
          "connectionGlobalHeaders": "Authorization=Basic xxxxx=",
          "autoRegisterTemplate": true,
          "autoRegisterTemplateVersion": "ESv7",
          "typeName": null,
          "batchAction": "Create",
          "detectElasticsearchVersion": true,
          "registerTemplateFailure": "IndexAnyway"
        }
      },
      {
        "Name": "Console"
      }
    ]

var loggerConfiguration = new LoggerConfiguration()
                .ReadFrom.Configuration(configuration, "SerilogEvent")
.Enrich.FromLogContext()
.CreateLogger();

I faced same Issue today and It works only with in-code configuration and it seems appsetting.json cannot set TypeName to null value.
it should be documented in your readme file to notice the users at least

Thank you @navid-dada!
Made it work by moving all my settings to in-code configuration and including the TypeName = null, with version 8.4.1.
Would still be nice to be able to use appsettings.json though, but this works for now :)

Yes, this fixed it for me as well, thanks! To be clear,

going against elasticsearch version 8.2.0
while using Serilog.Formatting.Elasticsearch version 9.0.0-beta7 (I upgraded to highest available, maybe not needed to even be version 9, don't know)
Serilog.Sinks.Elasticsearch version 9.0.0-beta7
For ElasticsearchSinkOptions set TypeName = null,

The last setting fixed the problem I was getting, which you could see when setting within ElasticsearchSinkOptions.ModifyConnectionSettings: config.OnRequestCompleted(d => $"es-req: {d.DebugInformation}".Print())
The above let it be seen the problem was this (from the printed out DebugInformation, there was a illegal_argument_exception being returned from elasticsearch: Action/metadata line [1] contains an unknown parameter [_type]. Full response:

[1] BadResponse: Node: https://xyz.elastic-cloud.com:1234/ Took: 00:00:00.0447236

OriginalException: Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 400 from: POST /_bulk. ServerError: Type: illegal_argument_exception Reason: "Action/metadata line [1] contains an unknown parameter [_type]"

Any update on when the fix will be added to a package so we can keep the settings in appsettings.json ?

Read this article. It helped me to get the Sink working.
Write to ElasticSearch 8 with Serilog in .NET Core - Article
Take note of the ElasticsearchOptions URI as it should contain the username and password, unlike in v7. I hope this helps.

Shouldn't that work with the property "connectionGlobalHeaders" too? Because it's not.

I can create a PR about Elasticsearch 8.x functionality. There are just a couple of lines, but let’s see how testing will go….

Any update on this?

Making the sink work with Elasticsearch 8.x is also captured here: #460


HDFS-15865 Interrupt DataStreamer thread if no ack

@karthikhw , the patch generally looks good to me, However what are the cases when the nodes is null ?

@mukul1987  Not exactly found when nodes come null but appears when client couldn't reach datenode (during middle of its write). Looks the next retry comes with null.

Thanks for the review @sodonnel , merging this.


Generate APIView code file as part of build pipeline job and publish …

Add new step in build pipeline to create APIView code file for JS package and publish it as artifact
Fixes: #22874

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-template

/azp run js - template - ci

Test created a PR review using new sandboxing framework: https://apiview.dev/Assemblies/Review/2a29f7f288f0471d9f9efbbaa9298465?diffRevisionId=552985e56628437c82ef3a935eb3b152&doc=False&diffOnly=False&revisionId=913d35dacbce41628d8fc1d9c121b3f5

@weshaggard Can you please have a look at this PR when you get a chance?

/azp run js - template - ci


[SPIKE] Investigate how OBE will behave with multiple tabs in different chains

Investigate how the system will behave when having multiple tabs opened in different chains:

Will UAL handle multiple logins?
How will work the local storage vars?
Will different tabs interfere in each other?

Some investigation results:

With the current implementation of OBE, if we open two tabs and change the network in one of them, it will interfere in the other one.
Changing the code to use sessionStorage instead of localStorage for the keys 'account', 'autoLogin' and 'selectedChainName', it was possible to open two different instances (separete tabs on the same browser) of OBE in differents chains and connect each chain using their accounts. The system kept the user logged in and it was possible to interact with each chain without one tab interfere in the other one.


lint: add whitenoise check

Signed-off-by: Loong Dai<EMAIL_ADDRESS>

Codecov Report

Merging #121 (93b0b49) into main (80b78e5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #121   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            5         5
=========================================
  Hits             5         5

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 80b78e5...93b0b49. Read the comment docs.


RN 0.73 compatibility for Android

@dominicstop
See: https://github.com/react-native-community/discussions-and-proposals/issues/671#issuecomment-1597386954

We're migrating this to expo modules so that should hopefully address this.

We're migrating this to expo modules so that should hopefully address this.

https://github.com/dominicstop/react-native-ios-context-menu/blob/master/android/build.gradle#L65
Yep, great stuff! Best of luck with the migration, looking forward to it! Closing this one until further notice.

@nandorojo is there an article or a comment anywhere in this repo that discusses the move to expo modules? (I wonder what the reasons behind adding that dependency were).
We're not using expo in our react-native project and I'm wondering if it's worth the overhead of dealing with expo modules since the only library that requires it is this one.
Thanks for all your great work. 🙏

Hey, there are a number of reasons.
TLDR, updating native libraries without expo is so annoying and hard that most libraries go entirely unmaintained.
Expo made it super easy to support the new/old architectures together and use JSI, all while writing Swift directly.
I understand that not everyone has expo installed; however, it's becoming increasingly easier for a vanilla RN app to simply install expo-modules into their app in order to use third party modules.
Ultimately, the maintenance burden of spending days working on config files and dealing with React Native's unreasonable breaking changes from one update to another just isn't worth it.
Conversely, working with expo modules makes a library actually maintainable, and updating RN versions becomes easy.

@nandorojo got it, I appreciate your quick response, that makes sense.
Thank you 🙏


Forgot to change address network bytes.

It looks like you accidentally forgot to change the network version bytes at https://github.com/ILCoinDevTeam/ilcoin-master/blob/master/src/chainparams.cpp#L112 so they are still the same as Bitcoin's.

Hi, we do not forgot we are like this same as Bitcoin because is the way we wanted to be. Regards!

You know this is going to cause endless problems for any exchange or wallet provider that lists you, right? With users sending to the wrong chain then either the funds having to be recovered or the users losing them depending on their policies.


Code dependency for field types

Whenever a type is in a return type of an RPC function, the call site must generate a dependency on the type involved, so that code path minification is correct. (RPC activator has to find the prototype.) But the activator works recursively, so every type occuring as a field of a class/record/union must be included too, not just the ones directly visible in the RPC return.

Fixed in https://github.com/intellifactory/websharper/commit/55d19df31f25cfe80961f995769e715d4b78e1f1 (records and classes) and https://github.com/intellifactory/websharper/commit/f1fbff70d6cac8380adc71e066c37ee3e816a31f (union case types)
Dependency edges are created between the type nodes themselves.

Reopening this for WS3. This also affects InlineControl arguments as it it is using the same Activate mechanism as RPC arguments.


Include date on which a credit was set manual in API response

(if it ever was)

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please


⚠ SpeakUpConference.com has degraded performance

In 2d551a0, SpeakUpConference.com (https://www.speakupconference.com) experienced degraded performance:

HTTP code: 200
Response time: 17247 ms

Resolved: SpeakUpConference.com performance has improved in 567633b after 11 minutes.


Testing pull request

This is temporary pull request just to see if Travis CI will run successfully. Please feel free to delete if it doesn't. I hope it doesn't cause anyone any problems.

Doesn't look like it worked!


URLs to trigger/retrieve the vulnerability scan are incorrect

In the PowerShell script provided on this page, the four functions to trigger/retrieve the results of a vulnerability scan during the conversion have a typo in the URLs that prevent the scans from occurring: defualt should be default.
With the typo, the script completes without error but does not actually trigger the on-demand scans.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 81c51ddb-f231-b5b9-6ca5-7d3fe4e8c19c
Version Independent ID: 724c245e-24b4-caf2-c4b4-0b77093ac95a
Content: PowerShell script sample - Enable vulnerability assessment on a SQL server
Content Source: articles/defender-for-cloud/powershell-sample-vulnerability-assessment-azure-sql.md
Service: defender-for-cloud
GitHub Login: @dcurwin
Microsoft Alias: dacurwin

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

#reassign:dcurwin

@HamsterExAstris  - Thanks for the comment. We've corrected the typos. The changes should be live soon.
#please-close


Editor redesign - WIP

Done : play/pause functionality and video time info, controls structure
To do : finish fullscreen implementation

Thanks for your work on this @tji, I've transferred the work over now ❤


Move abi declarations to the ty module.

This PR is one of several in a process to address https://github.com/FuelLabs/sway/issues/2951. This PR moves abi declarations to the ty module. Currently, things are a little awkward organizationally, as the definitions and impl blocks are in different modules, but this is done in (quick) iterations to reduce merge conflicts overall.

Closing in favor of #3024.


Fix unprintable characters

This js file failing to execute in chrome due to:
Uncaught SyntaxError: Invalid or unexpected token
This PR shows possible fix, I hope it will be helpfull, and you will be able to fix it in source files
Please note that minificator(uglify js) removes this unprintable characters, but I prefer to work with non minified files in development environment

Fixed with https://github.com/Kurento/kurento-client-js/commit/f4b878aa11b4ed1bc50e65fb0e53ce0cdf5df218


LRS Dashboard Mockups

Describe the task
Creation of LRS Dashboard mockups for external, staff and manager users.
Design Files

Figma: https://www.figma.com/file/rCVrqmQNEPSooT75LP2qqd/LRS-Dashboard?node-id=7%3A20&t=wibn9zPc8l3grPkp-1

Acceptance Criteria

[x] Mockups for External users
[ ] Mockups for LRS Staff users
[ ] Mockups for SDM users
[x] Figma file containing mockups
[ ] Mockups peer reviewed by team and approved by Haley

UX Definition of Done

[ ] User stories reflected in mockups

These designs need to include "Packaging/Bundling" before we can implement them.  Maybe we should create a separate task for that and mark it as blocking #113? Any thoughts?


⚠ SceneTime has degraded performance

In 42d7de1, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 17440 ms

Resolved: SceneTime performance has improved in 9de448d.


Issue 328

Pull Request Description
What issue does this change request address?
#328
What are the significant changes in functionality due to this change request?
This makes some Comparison Statistics Metrics.

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

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

Job Mingw Test on 598c4d5 : canceled by @joshua-cogliati-inl
More work is needed before this is accepted, so skip test.

@joshua-cogliati-inl Do you want me to review this PR?

@wangcj05 Yes, if you have time I would like you to review it.

OK, I will take a look.

I just went through this PR very quickly.  The changes in the Metric.py post processor is fine with me. But I do have a question. Based on the previous email discussion, I think the following format is preferred:
      <Features type="distribution">dist1</Features>
      <Targets type="variable">temperature</Targets>

could definitely work.  Possibly for consistency it should be class=DataObjects or class=Distributions

Based on my understanding, this is not the final PR, right?

      <Features type="distribution">dist1</Features>
      <Targets type="variable">temperature</Targets>

Well allowing anything for variables greatly simpliifes the input file.
For example, in  tests/framework/PostProcessors/Metrics/test_comparison_stats_metrics_dists.xml
I have:
      <Features type="variable">ans, dist1, dist1</Features>
      <Targets type="variable">ans2, dist2, outputDataMC|Output|ans2</Targets>

If I have to specify distribution and variables separately, this would require three postprocessors which would require three steps.  So I propose either we allow a completely different format, or allow anything with variables.  I can bring this to the devel list if you want.

Since you are listing different variables, i.e. variable, distribution. Do we still want to keep the "type" for the Feature and Target? One case is that we use this type=DataObjects to compare two data objects.

Please resolve the conflict and I'm ok with the rest of the changes.

Conflict fixed by dropping the commit that updated the .gitignore (which was also updated by a different merge)

Hm, I think to usefully keep the type we would need to do something like change the syntax to
<compare><feature type="variable">var1</feature><target type="distribution">dist1</target></compare>
<compare><feature type="variable">var2</feature><target type="distribution">dist2</target></compare>

Otherwise the "type" is pretty restrictive.

@wangcj05 and @alfoa There are several new commits to improve this request.  I found that in scipy 0.17 I could use scipy's interpolate function instead of wrapping it with a python function.  I found that for my tests the quadrature integration worked fine (all the tests matched to 4 significant figures, and ran much faster).  I also found a bug with duplicates being in the histogram bin boundaries, so I check for that.  Combined on my computer this decreases the time to run ./run_tests -j11 --re=Metrics from 75 seconds to 14 seconds.

I have reviewed the new changes, just minor comments, and this PR looks good to me.

I think that @alfoa  wanted to review them as well before the merge, so we can wait for that.

I think that as first implementation it is ok.
I still think that in terms of performance this implementation can be still quite slow in some circumstances. We can address this "issue" later on

@wangcj05  Would you like to do the checklist and if it passes merge it?  Thanks.

@joshua-cogliati-inl What happened to the old tests, such as test_calc_and_transfer.xml and test_cc_stats.xml? I did  not see that you changed this file. Should this two tests be modified? Am I misunderstanding?

I haven't removed the old Comparison Statistics, so I haven't removed those tests or rewritten them to use the new Metrics.  I can either add removing the old Comparison Statistics to this merge request or add a second merge request.  Or if you want, I can rewrite test_calc_and_transfer.xml to use the Metrics and leave test_cc_stats.xml to be removed with the old Comparison Statistics.

I see, let's open an issue and create a second merge request. When you open an issue, just remember:

We should have an issue to improve the performance for this PR
We should remove the old Comparison Statistics, and update all the tests, I think this changes will affect the stable and the requirement tests.

In addition, I will do the checklist.

All the checklists passed. @alfoa do you have any other comments for this PR? Are you ok we merge this PR?

Issues #397 and #398 created.

Thanks a lot. If @alfoa gives the thumbs up for this PR, I will merge it.

Ok, I just talked with @alfoa, and we agreed this PR is good to go.


fix(TDI-40275): fix GoogleDriveConnection DatastorePath behavior

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-40275
What is the new behavior?
Change the previous PR behavior due to unmanageable UI.
Please check if the PR fulfills these requirements

[X] The commit message follows Talend standard
[X] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[X] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:
Sonar results

Pull request test result: success :star:
Sonar results


Connect New Auth Methods to Users Table

Description

In LoginV2,  there are two new ways of logging: Google and Facebook
When a user creates an account using these two methods, create functionality to add a new row into our Users table

Information you will need:

First name and last name

Obtainable from the onAuthStateChanged observer (The user object in Playground)

Role (Will always be "volunteer")
Email

Obtainable from the onAuthStateChanged observer (The user object in Playground)

Firebase UID

Obtainable from the onAuthStateChanged observer (The user object in Playground)

It's important to note that our Firebase will link accounts with the same email even if different sign-in methods wre used

For example, if I use the email<EMAIL_ADDRESS>to create an account using both the plain email/password and Google methods, only one row will appear in our console since the email will be linked

Notice how multiple sign-in methods will have both the same email and Firebase UID

What this means is that you may not always need to add a new row into our Users table because similarly, we'll hold one row in Users per email
So, before adding a new row into Users, check if there is already an existing row in Users that has the Firebase UID of the newly created account

If there is, no need to add a new row in Users, it's already there (They already signed up using some other sign-in method)
If there isn't, add a new row in Users

Acceptance Criteria

For both Google and Facebook sign-in methods, a new row will be added to Users if there is no existing row with a matching Firebase UID of the newly created account

If there is an existing row, Users table will be left untouched

Resources

If you console.log the user object from the onAuthStateChanged observer, you can see some needed fields:

Some important ones:

displayName
email
uid

Firebase onAuthStateChanged

Apologies for another auth task @KevinWu098

Apologies for another auth task @KevinWu098

          Me when auth:

Originally posted by @KevinWu098 in https://github.com/ctc-uci/stand-up-to-trash-frontend/issues/55#issuecomment-1928529958


I test your build appimage for wine in i3wm environment is slot

in xfce or i3wm , you wine appimage not run any softw~

anylog or error?

info about your os.

my os info

which app you are trying not working?

the first run wine

when i run wine have causing the system to freeze

when i run wine, it always caused my system to freezed

does winecfg works

does winecfg is work ?

hmm, try wine-devel appimage

does winecfg is work ?

it should show winecfg dialog it that worked.

ok give me 20min, i download wine-devel

winecfg is work

so wine-staging does not work for you.

but i run wine appimage , it caused my system to freeze second.

wine-devel is not work too

its not appimage issue but app issue with wine

tho you can install these deps for qq
./wine-devel_8.0-x86_64.AppImage winetricks -q riched20 fakechinese mfc42


Proto forward to from hyperion.ng to hyperion (old gen) does not work

I made this issue after recommendation by @RickDB with a request to also tag @Paulchen-Panther .
Since I updated my Odroid C2 with CoreELEC to the latest version CoreELEC 9.2.1 my protobuffer forward does not work anymore. Right now my setup is as follows:

Odroid C2 runs Hyperion.ng on CoreELEC and plays the media (main instance)
RPI2 runs LibreELEC and Hyperion (old gen) and is connected to ambilight LED strips (secondary instance)
Odroid C2 forwards color details via protobuffer to RPI2

Since updating to latest version of CoreELEC, my hyperion setup does not work anymore. Before that, everything worked great on CoreELEC 9.2.1. After update the logfile is flooded with these messages:
[hyperiond FLATBUFCONNECTION] (ERROR) Unable to parse reply
[hyperiond FLATBUFCONNECTION] (ERROR) Unable to parse reply
[hyperiond FLATBUFCONNECTION] (ERROR) Unable to parse reply
[hyperiond FLATBUFCONNECTION] (ERROR) Unable to parse reply
[hyperiond FLATBUFCONNECTION] (ERROR) Unable to parse reply
[hyperiond FLATBUFCONNECTION] (ERROR) Unable to parse reply
[hyperiond FLATBUFCONNECTION] (ERROR) Unable to parse reply
[hyperiond FLATBUFCONNECTION] (ERROR) Unable to parse reply`

On the second instance, my log contains these errors:
JSONSERVER INFO: New connection
BLACKBORDER INFO: threshold set to 0 (0)
BLACKBORDER INFO: mode:default
JSONSERVER INFO: Connection closed
[libprotobuf ERROR /home/sascha/hyperion/dependencies/external/protobuf/src/google/protobuf/message_lite.cc:123] Can't parse message of type "proto.HyperionRequest" because it is missing required fields: command

The old version where everything worked is indicated as version 101 in the changelog:
101
- Add Platform script
100
- Initial Release @e438bc6

With this in the makefile:
PKG_NAME="hyperion.ng"
PKG_VERSION="74766fd62631a35d90872278b3bf9d88d4dfffdd"
PKG_SHA256="257d05290dc1bd86bc3f1b84e252af66a6a3876eda77fe3864a96f0ab87f1b9b"
PKG_REV="101"
PKG_LICENSE="GPL"
PKG_SITE="https://github.com/hyperion-project/hyperion.ng"
PKG_URL="https://github.com/hyperion-project/hyperion.ng/archive/$PKG_VERSION.tar.gz"
PKG_DEPENDS_TARGET="toolchain Python3 avahi libusb qt-everywhere protobuf flatbuffers:target"
PKG_SECTION="service"
PKG_SHORTDESC="Hyperion.NG: an AmbiLight controller"
PKG_LONGDESC="Hyperion.NG($PKG_VERSION) is an modern opensource AmbiLight implementation."

The new CoreELEC version 9.2.1 has the same changelog and makefile, but somehow this version doesn't work. Note that in 9.0.3 I used the hyperion.ng version included in the release without updating, and with 9.2.1 it didn't work before, or after updating to the latest version. The hyperion build that has the bug is version 2.0.0 with build date Nov 27th 2019 at 10:11:58.
I think the issue is with the dropped protobuffer support, which has not been brought back to the latest release included in CoreELEC.

Will close this, hyperion classic is discontinued...


add Go 1.20 to the build matrix

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2650

Relevant Lines:
7979

💛  - Coveralls


Some input from review.

Let's add the copy visual section here too, liked that very much
Will need images to support these
May want to add more context and 'why' to each of the sections, they felt a little terse.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c778cbf1-81b2-1a99-2328-471ee4fbd870
Version Independent ID: 92e418b5-6fb8-317d-01cd-4aeb9bbd8f6e
Content: Lead data-driven discussions in Microsoft Teams - Power BI
Content Source: powerbi-docs/consumer/business-user-teams-share-data.md
Service: powerbi
Sub-service: pbi-explore
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

added to https://github.com/MicrosoftDocs/powerbi-docs-pr/pull/6384


Support for redirection conditional on rssi and txpower

This PR changes:

The way we handle uri redirects, simplifying a lot of the code
Adds two new custom headers: X-PhysicalWeb-Rssi and X-PhysicalWeb-TxPower
Adds a sample redirection server (local_redirector.py), which redirects only if path_loss <= 50

Updated to add a redirector right to PWS for testing, making it easier for others to try out.

lgtm. You can merge it if you think it's ready.
You can probably add improvement you thought about later.

I think I'll rebase half of this and land it, specifically the changes to caching of redirects etc.
The HTTP headers I think should change to distance & confidence, instead of rssi & txpower, so I won't land that part just yet.

Alrighty, I think this is ready to land.  The latest big changes are:

"rank" is now a float based on calculated distance, not an int based on path_loss.  The iOS app appears to handle this fine, but I don't have a device to test at the moment.  Will do so Monday morning.
X-PhysicalWeb-Rssi and X-PhysicalWeb-TxPower are replaced with X-PhysicalWeb-Distance.  Currently this is calculated on the PWS, but may eventually be passed directly from the client app (which will have the most accurate calculation of distance).
experimental features are now disabled unless the application name ends in -dev.  This means we can check this in without actually launching features such as the X-PhysicalWeb-Distance to stable.

lgtm.


Shoukaku client is sending the request but no audio will be played

No error, it just doesn't play any sounds.
Here is the reference: https://github.com/lavalink-devs/Lavalink/discussions/1025

Same issue

Check latest commits and see if this fixes yoru issues

Check latest commits and see if this fixes your issues

Thanks! I'll check it out as soon as possible!

@Deivu I don't think the latest commit fixed the issue...
I'm still having the same issue.

Fixed for me

Please create a new issue if this is still a problem.


Document middlware with minimal APIs

Part of https://github.com/dotnet/aspnetcore/issues/44259
Not linked to anywhere yet since it's not clear how all the new docs will be stitched together yet.

Not linked to anywhere yet since it's not clear how all the new docs will be stitched together yet.
Once this merges, I'll do a PR to update the TOC.


Fixed self reference capture in Tab and TerminalPage

Summary of the Pull Request
Every lambda capture in Tab and TerminalPage has been changed from capturing raw this to std::weak_ptr<Tab> or winrt::weak_ref<TerminalPage>. Lambda bodies have been changed to check the weak reference before use.
Capturing raw this in Tab's title change event handler was the root cause of #3776, and is fixed in this PR among other instance of raw this capture.
The lambda fixes to TerminalPage are unrelated to the core issue addressed in the PR checklist. Because I was already editing TerminalPage, figured I'd do a weak_ref pass.

References

PR Checklist

[x] Closes #3776, potentially #2248, likely closes others
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Requires documentation to be updated
[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #3776

Detailed Description of the Pull Request / Additional comments
Tab now inherits from enable_shared_from_this, which enable accessing Tab objects as std::weak_ptr<Tab> objects. All instances of lambdas capturing this now capture std::weak_ptr<Tab> instead. TerminalPage is a WinRT type which supports winrt::weak_ref<TerminalPage>. All previous instance of TerminalPage lambdas capturing this has been replaced to capture winrt::weak_ref<TerminalPage>. These weak pointers/references can only be created after object construction necessitating for Tab a new function called after construction to bind lambdas.
Any anomalous crash related to the following functionality during closing a tab or WT may be fixed by this PR:

Tab icon updating
Tab text updating
Tab dragging
Clicking new tab button
Changing active pane
Closing an active tab
Clicking on a tab
Creating the new tab flyout menu

Sorry about all the commits. Will fix my fork after this PR! 😅

Validation Steps Performed
Attempted to repro the steps indicated in issue #3776 with the new changes and failed. When before the changes, the issue could consistently be reproed.

Azure pipeline got stuck in unit testing again. I imagine I don't have the god power /azp run

/azp run

Happy to help! Also, feel free to assign any goon work to me. I'm sure there's a lot of issues in the backlog with identified solutions that just need a goon to implement them.

feel free to assign any goon work to me. I'm sure there's a lot of issues in the backlog with identified solutions that just need a goon to implement them.

Be careful what you wish for 😜 I'll look for some things that might be up your alley


Whole validation accuracy using provided model_110.ckpt-79999 is extremely low

I try to test accuracy on the whole validation set using the provided ckpt, so I modify cifar10_train.py like below
# Initialize the Train object
train = Train()
# Start the training session
# train.train()

validation_array, validation_labels = read_in_all_images([vali_dir],
                                                         is_random_label=VALI_RANDOM_LABEL)
predictions=train.test(validation_array)
vali_accu=np.mean((np.argmax(predictions,1)==validation_labels.astype(int)).astype(float))
print 'total accu on vali is %f'%vali_accu

But the result is  extremly low

total accu on vali is 0.334300

Then I trained my owner checkpoint from scratch, and got a much better accuracy

total accu on vali is 0.9161000

Is there anything wrong during my test process?

I got the same result, and I still training my own model.


Add Support for Kogan Dehumidifier

Hello
Was wondering if it would be possible to add support for the following smart dehumidifier:
https://www.kogan.com/au/buy/kogan-smarterhome-smart-7l-desiccant-dehumidifier/?utm_source=google&utm_medium=product_listing_ads&gclid=Cj0KCQjwraqHBhDsARIsAKuGZeGvh80L-kiwAqezFm2FI3ZHfOJzyLT-BHJcDvfYW_gQYscddFcDWfUaAleBEALw_wcB
I've mapped the DPs as following:
1 - value: true/false (power)
2 - value: low/middle/high/quickdry (fan)
3 - value: numeric (humidity sensor)
8 - value: true/false (swing)
11 - value: 0/1 (tank full indicator)
12 - value: 0, 1, 2, 3 (countdown timer select)
13 - value: 0, 120, 240, 480 (countdown timer minutes)
101: value: 0 - 80 (humidity set point)
Cheers! :)

You'll need to post the log (remove the ID field) from step 1 of
https://github.com/tuya/tuya-home-assistant/wiki/How-to-Develop-a-New-Driver
and as shown in https://github.com/tuya/tuya-home-assistant/issues/476#issue-999764828
so we can see what category it is and what functions it supports

Hey sorry about that. Hope this helps:
"active_time":<PHONE_NUMBER>,
"biz_type": 0,
"category": "cs",
"create_time":<PHONE_NUMBER>,
"icon": "smart/icon/ay15253387844269Sg99/7ec0da9bc2c1cbb719a5a04977f55097.png",
"id":,
"ip": "",
"lat": "",
"local_key": "",
"lon": "",
"name": "Dehumidifier",
"online": true,
"owner_id": "32988501",
"product_id": "jhpmwtl30x7i3sts",
"product_name": "Dehumidifier",
"status": [
{
"code": "switch",
"value": true
}
],
"sub": false,
"time_zone": "+10:00",
"uid": "***",
"update_time":<PHONE_NUMBER>,
"uuid": "4073378124a1602449f0"
}
],

Hey sorry about that. Hope this helps:
"active_time":<PHONE_NUMBER>,
"biz_type": 0,
"category": "cs",
"create_time":<PHONE_NUMBER>,
"icon": "smart/icon/ay15253387844269Sg99/7ec0da9bc2c1cbb719a5a04977f55097.png",
"id": "",
"ip": "",
"lat": "",
"local_key": "",
"lon": "",
"name": "Dehumidifier",
"online": true,
"owner_id": "32988501",
"product_id": "jhpmwtl30x7i3sts",
"product_name": "Dehumidifier",
"status": [
{
"code": "switch",
"value": true
}
],
"sub": false,
"time_zone": "+10:00",
"uid": "***",
"update_time":<PHONE_NUMBER>,
"uuid": "4073378124a1602449f0"
}
],

Looks like it only supports on/off and that should already be in HA as a humidifier.  If you search for "functions" in the log and find the one that has the "cs" category above it (like the "Device Specifcations" section in the issue details of https://github.com/tuya/tuya-home-assistant/issues/476#issue-999764828 ) that will confirm it.
Do you get a humidifier entity with on/off in HA?

Sorry that I missed that out. I'm a bit of noob. Hopefully this is what you're after:
"result": {
"category": "cz",
"functions": [
{
"code": "switch_1",
"type": "Boolean",
"values": "{}"
},
{
"code": "countdown_1",
"type": "Integer",
"values": "{"unit":"s","min":0,"max":86400,"scale":0,"step":1}"
}
],
"status": [
{
"code": "switch_1",
"type": "Boolean",
"values": "{}"
},
{
"code": "countdown_1",
"type": "Integer",
"values": "{"unit":"s","min":0,"max":86400,"scale":0,"step":1}"
}
]
},
"success": true,
"t":<PHONE_NUMBER>593
}
2021-09-24 01:31:49 DEBUG (SyncWorker_5) [tuya iot] Request: method = GET, url = https://openapi.tuyaeu.com/v1.0/devices/4073378124a1602449f0/specifications, params = None, body = None, t =<PHONE_NUMBER>769
2021-09-24 01:31:50 DEBUG (Thread-5) [tuya iot] _on_log: Received SUBACK
2021-09-24 01:31:50 DEBUG (Thread-5) [tuya iot] _on_subscribe: 1
2021-09-24 01:31:50 DEBUG (SyncWorker_5) [tuya iot] Response: {
"result": {
"category": "cs",
"functions": [
{
"code": "switch",
"type": "Boolean",
"values": "{}"
}
],
"status": [
{
"code": "switch",
"type": "Boolean",
"values": "{}"
}
]
},
"success": true,
"t":<PHONE_NUMBER>959
}
So I do have a working entity with on/off in HA. I'm currently using the tuya local custom integration which allows me to control the operating modes of the dehumidifier and control the fan setttings with a seperate entity as per the data points I posted initially. Was hoping to get this working in this integration so I could migrate over.

OK looks like a switch is all you can currently get using the Tuya V2 integration.  You could try creating a ticket in the Tuya service console with that same info above (just those last ones, from 2021-09-24 01:31:50 onwards) at
https://service.console.tuya.com/8/2/create?step=3&id=01030503&source=content_feedback
asking them to standardise that device so that it exposes more functionality.  They're usually pretty fast to respond with either a yes or not possible.


Use GitHub's built-in template repo system

I love your project, but thought the process for using it as a template could be streamlined.
GitHub allows you to set a project up as a template with a single setting:

With just that, you get a "use this template" button in the top right of your repo. you can see it in my fork here: https://github.com/ebetancourt/full-stack-fastapi-template

This also allows the creation of a private repo based on the template.
I also added a GitHub action that runs once a day and checks the original template, and if there are any changes, it creates a PR against the project with the updates to the template

I know my screenshots don't quite fit your style (you don't have any call-outs and they are in dark mode, while yours are all in light mode) - if this is a feature you want to add, and you would like to merge my PR, I will happily update the images (and anything else!) to fit the needs of the project.
Oh, and of course, I would have to update the action to point to YOUR repo rather than my fork!

Hey! Is there any plan to actually enable template creation from this repo since it's actually a template? Cause it would be really nice to allow this out of the box for the new users of FastAPI and of the template.
From what I see in this PR I don't think it should be merged as is:

No need for explanative screenshots
Not sure if a dedicated github workflow should be included out of the box in the template @ebetancourt eventually with the manual trigger only. I would not advice to sync changes on a cron task as it would be pretty bad for a production level project. Especially that there is a high risk of merge conflicts that the GH action will not be able to handle.

But maybe one of the main maintainer could just update the docs to simplify/remove this section about making the repo private by simply ticking this "Template repository" option.
@alejsdev @tiangolo What do you think? 👾


Team Management panel in the Account page should list team members

We should show the usernames of all team members as a bulleted list in the Team Management panel. This way a team leader can know who has/hasn't joined the team.

Fixed by #182. (The squash killed the "revolves" line in one of the commit messages.)


css: sample of refactoring selectors for uniformity

This Draft PR, whose work I previewed on CZO, provides a look at the scope involved with refactoring CSS selectors with underscores to instead use hyphens (the frontend codebase includes both).
I opted to begin work in the user_status.css file, to see where it would take me.
Ordinarily I would have squashed all of these commits (apart from the documentation one). But as this is draft work, I wanted to provide the individual, per-selector commits as standalone records of just how far-flung individual frontend classes are across different CSS, JavaScript, and Handlebars files.
I now see with greater clarity what @andersk was describing in our chat yesterday, about the need for modularity. I still think that complexity is tamed by opting for uniform styles wherever possible.
To that end, there is one selector from user_status.css I did not successfully modify: .status_emoji, which I was unable to do without the Puppeteer user-status.test.ts breaking on waiting for the .emoji-info-popover to appear in the DOM.

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@karlstolley thanks for working on this! Am I correct to assume you did git greps to verify that you got all the references to these classes?
I think actually this commit structure is a lot easier to review (since one can think about one class at a time) than the squashed version; so please don't squash the commits -- our preference is to merge minimal atomic readable commits :).
Can you talk about what the issue was with migrating .status_emoji? It might be good to debug that.
As a nit, the commit message titles are a bit different from our style; see
Check out the Zulip commit message guidelines for more details.

Thanks, @timabbott!
Yes, git grep was my tool of choice to hunt down the different instances of the snake_case classes.
The issue with .status_emoji (which is now fixed with all tests passing, and now part of the PR) was that I'd overlooked an appearance in the emoji_popover_emoji.hbs file, thanks to some pretty significant conditional Handlebars logic inside the class :) (Also thanks to my overworked eyes at the time, which had glazed over pretty good. Finding and fixing this mistake this afternoon took only a few minutes.)
That all being said, a limitation of the Puppeteer tests as written was that neither the console output nor the image generated by the failed test (user-status-test.ts) was enough to hunt down what I'd missed. But given the scope of what I was fixing, it seemed pretty obvious that I'd just overlooked something. And indeed I had :)

That all being said, a limitation of the Puppeteer tests as written was that neither the console output nor the image generated by the failed test (user-status-test.ts) was enough to hunt down what I'd missed

Yeah, makes sense; I use the screenshots when needed, but if it's likely to be an actual bug, usually what works best for me is to just try to do the sequence of steps that the test does in the web UI, where you'll get the see it not work there and can use all one's favorite debugging techniques.
I have a super minor nit that the commit message titles should end with a ".", but otherwise this lgtm as a migration of this cluster of classes; I'm happy to merge this as useful progress (albeit small compared to the total difference).

I have a super minor nit that the commit message titles should end with a ".", but otherwise this lgtm as a migration of this cluster of classes; I'm happy to merge this as useful progress (albeit small compared to the total difference).

Whoops, nit fixed! I added selector. to the ends of all the CSS commit messages to keep the changed selectors themselves more readable.

Merged, thanks @karlstolley!


Fixed typo that leaked to the binary

I fixed a typo that leaks to the binary and might leak to users.
The typo was found by lintian when I was packaging glslang.

 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.


Where does the identity of the partcipant (legal entities, human persons) come from?

Multiple open questions here

Closed by #193


can we get qwik support please?

any chance to support the new javascript framework qwik?

@cschroeter
would love to help with this,
any pointers on how to do so?

Hey @naorpeled,
Park UI is eventually based on Zag.js
All the components (machines) are in general framework agnostic. Since I'm not so familiar with qwik I can only point you to what already has been discussed in the forum: https://github.com/chakra-ui/zag/discussions/392
I would be more than happy to add more frameworks in Ark ;)


Build Hyprland for Debian

Description
Please build Hyprland for Debian.
Very inconvenient when trying to install Hyprland the convenient and quick way via apt, but it's not available as a .deb package. Maybe I don't know or understand something, please explain why you don't build Hyprland for debian.

because nobody here uses debian, plus debian has way too outdated deps

because nobody here uses debian

Maybe because they are inconvenient to install hurlland due to inconvenient manual installation?

plus debian has way too outdated deps
What is the problem with opening a separate repo for debian or giving out a separate file on the site?

by "nobody here" I mean nobody in the org that maintains hyprland in any capacity.

@izzy8799 Egor, please ask Donya to check his Proton email. I wrote a letter for all of you.
I apologize for posting here. I'm in rehab and can't contact @izzy8799 otherwise.

@izzy8799 Egor, please ask Donya to check his Proton email. I wrote a letter for all of you.
I apologize for posting here. I'm in rehab and can't contact @izzy8799 otherwise.

God, Andrey! Glad to see you again! I haven't opened Github messages for a long time. And so, Donya has already read the letters.


[AutoPR maps/resource-manager] chore: jsonfmt maps

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6168

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/3346


"Init On Image" not working

https://www.froala.com/wysiwyg-editor/docs/examples/init-on-image
This functionality causes problems because the directive requires ng-model to insert html. This creates a another <p> element with the content from the ng-model, all this wrapped in the <img />. Even if I init the <img /> with a static src, as soon as I want to replace the image the src will be removed. What works is to add a ng-src and feed it with the new file location. This cannot be the right solution.
The basic question is: How can I use <img froala /> instead of <textarea froala ng-model="myHtml"></textarea>?

I am also trying to get this part to work as well. @Nudelsieb  were you able to get this to work?

Bump, any chance this can be looked at?  @stefanneculai
Thanks

@fireole we'll look into this over the following days.

@fireole, sorry for the late reply. I am not working for the project anymore that used Froala, so cannot tell if anyone else has solved this issue. However, the above described solution / workaround worked at that point. I hope I could help.

@fireole Please check this pull request: https://github.com/froala/angular-froala/pull/123 and see if it works.
You init the editor like this: <img froala ng-model="imgModel"/> where the ng-model is an object of attributes - eg: {src: 'path/to/img.jpg'}.
Please check README and demo for more explanations and examples :smiley: .
Thanks

Perfect, I will check tonight and let you know

That worked!  Thank you.
The only thing I could see and it is not super big, but after loading a
picture the handles on the picture is bumped down off the picture/image.
Here is screen shot.  I tried to reproduce on your inline demo on website
and could get it to do the same thing.
thanks
[image: Inline image 1]
On Thu, Aug 11, 2016 at 2:44 PM, Florin Popescu<EMAIL_ADDRESS>wrote:

@fireole https://github.com/fireole Please check this pull request: #123
https://github.com/froala/angular-froala/pull/123 and see if it works.
You init the editor like this:  where
the ng-model is an object of attributes - eg: {src: 'path/to/img.jpg'}.
Please check README and demo for more explanations and examples 😃 .
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/froala/angular-froala/issues/78#issuecomment-239302653,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA8ID4fWmx4JBJKtzMRomruy5b0bQGykks5qe5fBgaJpZM4Hgg_0
.

--
Antonio Olander

Cool :smiley: Thank you too.
I cannot see the screenshot.

i will try this:

let me know if you can see that.

Yep I saw. I will investigate that in the next days and I will let you know :smiley: .

This was fixed here https://github.com/froala/wysiwyg-editor/issues/1425
It is not released yet but you can include it manually till the next release :smiley: .

Merged the pull request.

That worked thanks much!!!  You guys are awesome!

@fireole thanks for confirming.


[util/syn_yosys] Add file lists to run LEC on full design including sudmodules

Add file lists to syn_yosys flow to run LEC using the complete design including all submodules.
This script has still a few hacks to work around current flow issues.

@zachjs FYI

Hi Nils,
For the CI failure, could you please sign off this commit using git commit --amend -s; git push -f. This means you agree with the CLA policy as outlined in https://github.com/lowRISC/opentitan/blob/master/CLA. This is a new requirement we added in this repo. After that, the CI check should be green.


vagrant: Bump Vagrant net-next box version

This new version of the VM image includes a newer kernel with a fix for the bpf_skb_set_tunnel_key helper [1].
1 - https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=b8fff748521c7178b9a7d32b5a34a81cec8396f3

/test-1.24-net-next

/test-runtime

Tested, reviewed, marking ready to merge.


Update INSTALL.md

Proposed changes for M1 MacOS

Thanks for this PR. I am sure it will help many people with M1 Macs. Could you add your name to CONTRIBUTORS.txt?


correct typo in install.sh (1 -> !)

I should've rtfm. Just found out it was intentional as stated in contribution guidelines.

Haha, thanks


[ci] #3825: Clean default runner free space

Description
Some CI jobs have a lack of space problem on the default GitHub runners.
Linked issue
#3825
Benefits
This possible fix might help to free up approximate 10G disk size.
Checklist

[x] I've read CONTRIBUTING.md
[x] I've used the standard signed-off commit format (or will squash just before merging)
[x] All applicable CI checks pass (or I promised to make them pass later)
[ ] (optional) I've written unit tests for the code changes
[ ] I replied to all comments after code review, marking all implemented changes with thumbs up

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
6111 unchanged lines in 102 files lost coverage.
Overall coverage decreased (-1.1%) to 58.327%

Files with Coverage Reduction
New Missed Lines
%

cli/src/main.rs
1
0.0%

cli/src/torii/pagination.rs
1
98.9%

config/base/src/runtime_upgrades.rs
1
51.72%

config/src/torii.rs
1
96.67%

core/src/smartcontracts/isi/block.rs
1
87.5%

crypto/src/merkle.rs
1
96.23%

data_model/derive/src/partially_tagged.rs
1
99.67%

data_model/src/domain.rs
1
47.37%

logger/src/lib.rs
1
95.15%

config/src/lib.rs
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-1.1%

Covered Lines:
21419

Relevant Lines:
36722

💛  - Coveralls


Formatter fails on string literals in {#match, "block"}

Here's a failing test case. I started to attempt to fix it, but it looks like there's some refactoring needed in Render.render_node/2. I tried to make an attempt at fixing it but its probably better for @paulstatezny to look into this

@davydog187 Thanks for reproducing this in a test! Fixed in #32. I'll post back here when a patch is published.


Loss of precision (int->float) detection

Is it possible to detect the following problem (if you think it makes sense)?
float f = Integer.MAX_VALUE - 1;
int i = (int)f;
System.out.println(Integer.MAX_VALUE - i);

[suggested by M. Yerly via email]

Yes, it definitely makes sense. I thought it was done but in fact you're right, that's missing. I just added that feature (int->float and long->double), and it will appear in the upcoming release. Note that in this precise code snippet it won't be detected because the casting is done at compile-time; but it is detected in that one:
int j = Integer.MAX_VALUE;
float f = j - 1;

Thanks a lot for proposing that improvement!


fix: expand prebake image variant system

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#628  👈
#613
#599
#598
#382
#381
#380
#300
#373
#377
#597
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MasterPtato and the rest of your teammates on  Graphite


backend/scanner: Do not allow arrays/newids to be nullable

The wire protocol lacked a way to express nullable arrays as distinct from empty non-null arrays, so this was broken in upstream Wayland. Nullable newids were possible in the wire protocol, but not the C API, and dubiously useful.
This matches the change in https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/252.

Thanks, this seems pretty good!
Could you just rebase your PR on master? This should take care of CI issues.

I see you commited a change to one of the submodules in this PR. I suppose it is a mistake? This is why the CI is failing.

Thanks!


BUG - large first_reply_time_business_minutes on tickets with no replies

Are you a current Fivetran customer?
Maria Riolo, Data Analyst, Zearn
Describe the bug
In tickets with no replies, first_reply_time_business_minutes defaults to "business minutes from ticket creation to current time + 1000 hrs."
Steps to reproduce

Run normally on data including tickets with no replies
See errors in the first_reply_time_business_minutes column of zendesk__ticket_metrics table

Expected behavior
I would expect first_reply_time_business_minutes to be null in tickets with no replies.
Project variables configuration

# Name your package! Package names should contain only lowercase characters
# and underscores. A good package name should reflect your organization's
# name or the intended use of these models
name: 'zearn_redshift'
version: 1.0.0
config-version: 2

# This setting configures which "profile" dbt uses for this project. Profiles contain
# database connection information, and should be configured in the  ~/.dbt/profiles.yml file
profile: 'zearn-redshift'

# These configurations specify where dbt should look for different types of files.
# The `source-paths` config, for example, states that source models can be found
# in the "models/" directory. You probably won't need to change these!
source-paths: ["models"]
analysis-paths: ["analysis"]
test-paths: ["tests"]
data-paths: ["data"]
macro-paths: ["macros"]

target-path: "target"  # directory which will store compiled SQL files
clean-targets:         # directories to be removed by `dbt clean`
  - "target"
  - "dbt_modules"

on-run-start:
  # create schemas so we don't run into errors with the on-run-end hooks
  # if only doing a partial build or e.g. just running dbt seed
  - "CREATE SCHEMA IF NOT EXISTS \"{{ target.schema }}_marts\""
  - "CREATE SCHEMA IF NOT EXISTS \"{{ target.schema }}_staging\""
  - "CREATE SCHEMA IF NOT EXISTS \"{{ target.schema }}_exports\""
  - "CREATE SCHEMA IF NOT EXISTS \"{{ target.schema }}_zendesk_staging\""

on-run-end:
  - "GRANT USAGE ON SCHEMA \"{{ target.schema }}_marts\" to group looker, group zearn_analytics, group zearn_product"
  - "GRANT USAGE ON SCHEMA \"{{ target.schema }}_exports\" to jitterbit_sfdc_export, group looker, group zearn_analytics, group zearn_product"
  - "GRANT USAGE ON SCHEMA \"{{ target.schema }}_staging\" to group looker, group zearn_analytics, group zearn_product"
  - "GRANT USAGE ON SCHEMA \"{{ target.schema }}_zendesk_staging\" to group looker, group zearn_analytics, group zearn_product"
  - "GRANT SELECT ON ALL TABLES IN SCHEMA \"{{ target.schema }}_marts\" TO group looker, group zearn_analytics, group zearn_product"
  - "GRANT SELECT ON ALL TABLES IN SCHEMA \"{{ target.schema }}_exports\" TO jitterbit_sfdc_export, group zearn_analytics"
  - "GRANT SELECT ON ALL TABLES IN SCHEMA \"{{ target.schema }}_staging\" TO group zearn_analytics, group looker"
  - "GRANT SELECT ON ALL TABLES IN SCHEMA \"{{ target.schema }}_zendesk_staging\" TO group zearn_analytics, group looker"

# You can define configurations for models in the `source-paths` directory here.
# Using these configurations, you can enable or disable models, change how they
# are materialized, and more!

# In this example config, we tell dbt to build all models in the example/ directory
# as views (the default). These settings can be overridden in the individual model files
# using the `{{ config(...) }}` macro.
models:
  +bind: false

  zearn_redshift:
    +materialized: view
    staging:
      +materialized: view
      +schema: staging
      classification:
        +materialized: table
        support_tables:
          +materialized: table
      rostering:
        +materialized: table
      usage:
        +materialized: table
        +dist: user_id
        +sort: event_type, event_type_clean, created_at
    marts:
      +materialized: view
      +schema: marts
      summaries:
        +materialized: table
        +dist: user_id
        +sort: daydate
      exports:
        +materialized: table
        +schema: exports
  zendesk:
    +schema: staging
    intermediate:
      +schema: staging
    sla_policy:
      +schema: staging
    ticket_history:
      +schema: staging
vars:
  school_years: ['2012-2013', '2013-2014', '2014-2015', '2015-2016', '2016-2017', '2017-2018', '2018-2019', '2019-2020', '2020-2021']
  rostering_school_years: ['2016-2017', '2017-2018', '2018-2019', '2019-2020', '2020-2021']
  random_seed:<PHONE_NUMBER>989899184
  burbio_table_date: "2020-01-01" #default value needed to generate docs
  burbio_file_name: fake_file.csv #default value needed to generate docs
  district_student_info_district_id: 0 #default value needed to generate docs
  zendesk_source:
    zendesk_database: production
    zendesk_schema: ft_zendesk

Package Version

packages:
  - package: fishtown-analytics/dbt_utils
    version: [">=0.3.0"]
  - package: fivetran/zendesk
    version: 0.4.1

Warehouse

[ ] BigQuery
[x] Redshift
[ ] Snowflake
[x] Postgres
[ ] Databricks
[ ] Other (provide details below)

Additional context
I suspect I know where this is coming from.
In int_zendesk__ticket_first_reply_time_business.sql:
 greatest(0,
      (
        {{ fivetran_utils.timestamp_diff(
          'ticket_schedules.schedule_created_at',
          'least(ticket_schedules.schedule_invalidated_at, min(first_reply_time.agent_responded_at))',
          'second') }}/60
        )) as raw_delta_in_minutes

and in int_zendesk__ticket_schedules.sql:
coalesce(lead(schedule_created_at) over (partition by ticket_id order by schedule_created_at)            , {{ fivetran_utils.timestamp_add("hour", 1000, "" ~ dbt_utils.current_timestamp() ~ "") }} ) as schedule_invalidated_at
So it looks to me like if there's no reply and lead(schedule_created_at) over (partition by ticket_id order by schedule_created_at) is null, then we'd end up with current time + 1000 hrs treated as first response time.
Screenshots

Please indicate the level of urgency
We're just now working on getting our Zendesk data into Looker, and we ended up looking into this because we were seeing anomalously large average resolution and reply times - especially reply times - and normal looking medians.
This is something we can probably work around if needed, by filtering on reply counts (for reply times) and ticket status (for resolution times), but it would be really nice not to have to.
Are you interested in contributing to this package?

[ ] Yes, I can do this and open a PR for your review.
[ ] Possibly, but I'm not quite sure how to do this. I'd be happy to do a live coding session with someone to get this fixed.
[x] No, I'd prefer if someone else fixed this.  I don't have the time and/or don't know what the root cause of the problem is.

Hi @annichia thanks for opening this ticket!
After looking over your Issue it clearly seems like this is unintended behavior of the package. The additional context you provided is fantastic and will definitely help us resolve this issue in a timely manner! We are currently coming to the end of this sprint and will plan for this Issue to be addressed in the next sprint (starting mid next week). As such, I will respond back here when we assign this Issue next week.
Thanks!

Thanks, great to hear!

Hi @annichia I was working on this request and think the issue you are seeing may actually have stemmed from Issue #32. Essentially the logic for tracking agent comments was capturing ALL agent comments and not just public ones. Therefore, some tickets that had no public response were still being logged as a response time because there were internal comments.
I have confirmed this bug on my end using the v0.4.1 release of the package. I will continue to investigate, but it may be helpful if you were able to install the latest v0.5.1 release of the package and see if your issue persists.
packages:
  - package: fivetran/zendesk
    version: 0.5.1

FYI - A breaking change from v0.4 -> v0.5 exists in the form of custom schemas. You can easily override this if you do not want multiple schemas to be made for the various zendesk models.

Hi @fivetran-joemarkiewicz Oh, interesting, that could make sense! I'll give v0.5.1 a try and let you know if I still see the bug.

Hi @annichia just wanted to check in if the v0.5.1 release of the package resolved the original issue you were seeing?

Hi @fivetran-joemarkiewicz - sorry, I've been out of email contact. I'm still seeing the issue with v0.5.1, both in first reply time and first resolution.

@annichia I have been trying to dig into this issue but can't seem to replicate the issue on my end 🤔
I think it would be most helpful if we were able to set some time up this week during out dbt office hours to dive into this issue live. You can schedule some time using this link. I look forward to chatting with you then!
Additionally, when digging into this issue I did find that a few of the reply time conversions were not matching up when using a date difference by minutes. As such, I changed the calendar reply times to convert from seconds to minutes for more accurate reporting. While this most likely will not solve the issue you are seeing, you can still try this branch with the below packages.yml config:
packages:
  - git: https://github.com/fivetran/dbt_zendesk.git
    revision: bug/reply-times-fix
    warn-unpinned: false

Great, thanks - I scheduled a slot for this coming Monday and I'll give that fix a try, just in case.

@annichia I was able to make the changes we discussed and also some additional updates. Would you be able to try the working branch and let me know if everything looks good before merging to master?
packages:
  - git: https://github.com/fivetran/dbt_zendesk.git
    revision: bug/reply-times-fix
    warn-unpinned: false

Thanks!

Cool, trying this now.
On Fri, Jul 16, 2021 at 7:27 PM Joe Markiewicz @.***>
wrote:

@annichia https://github.com/annichia I was able to make the changes we
discussed and also some additional updates. Would you be able to try the
working branch and let me know if everything looks good before merging to
master?
packages:

git: https://github.com/fivetran/dbt_zendesk.git
revision: bug/reply-times-fix
warn-unpinned: false

Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fivetran/dbt_zendesk/issues/35#issuecomment-881769843,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2OPNZX5GZ5QBVVLDEJXV3TYC56TANCNFSM46RDQY4A
.

Unfortunately, still seeing unrealistically large numbers in first_resolution_business_minutes and first_reply_time_business_minutes using that new package.

🤔 I would have thought that the below would have fixed the reply time large numbers...
https://github.com/fivetran/dbt_zendesk/blob/5df4d4e304b0ffec082d82681dd50b04f308e2b6/models/zendesk__ticket_metrics.sql#L178
I believe my updates to the calendar resolution times when applied to business should resolve the error. However, for reply times would you be able to confirm for one of the large reply times that the conditional mentioned above is true? Or does it seem like there could be something I am missing?

It looks like everything with status solved is fixed - the ones that are still showing large numbers are mostly deleted or closed, with a handful pending.

Okay I see. After thinking about it I understand that the status should not be a dependency in the above calculation. I have removed that dependency and also adjusted the first and full resolution times for business metrics.
Would you be able to run dbt deps on the same branch I shared and run your models again to see if these changes fixed the discrepancies?

That fixed all the first_resolution_business_minutes entries!
Still getting some unfeasibly high first_reply_time_business_minutes, but not in the same circumstances - these I'm seeing in cases where first_reply_time_calendar_minutes is null and count_public_comments > 0.

Nice, we are getting closer! 🎉
Do you see that the count_public_agent_comments is > 0 for those unfeasibly high ones? I wonder if these are in fact null? I added a coalesce to my case when statement to assume a null value as 0 public agent comments. I did just push that change if you want to see if that worked.

Yeah, count_public_agent_comments > 0 for most of the one's I'm seeing

Interesting, If you take a look at the staging table stg_zendesk__ticket_comment for one of those tickets does the first public agent reply date closely correlate to the first reply time from the final table?
I want to confirm with these ones where there are in fact comments that they are not just extremely late reply times.

@annichia were you able to look into my above comment by chance? I am hoping to merge this and other changes for Zendesk by the end of the week.

Sorry, I'm having some unrelated technical issues and haven't been able to
check this yet. I'll ask my colleague @mjirv if he can take a look.
On Tue, Jul 20, 2021 at 5:30 PM Joe Markiewicz @.***>
wrote:

@annichia https://github.com/annichia were you able to look into my
above comment by chance? I am hoping to merge this and other changes for
Zendesk by the end of the week.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fivetran/dbt_zendesk/issues/35#issuecomment-883721273,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2OPN6I3H3WO6NHNRV52BDTYXTFVANCNFSM46RDQY4A
.

Hi @fivetran-joemarkiewicz. I spot checked some of them, and am seeing tickets with very high first_reply_time_business_minutes (up to a 499200 minutes) and count_public_agent_comments > 0 where the first actual public agent reply time (from stg_zendesk__ticket_comment) was within the same day or week.

Thanks for confirming this @mjirv. The updated case statement must be incorrect on my end. I will look into this some more and get back to you with an update.

After chatting with @mjirv over in dbt slack the fixes applied to the working branch have resolved the issue. I have since merged and cut a new release for v0.5.2 of the dbt_zendesk package. This should be live on the dbt hub later today.
Please feel free to open a new issue if you have any other questions or considerations for the package. Thanks again!


Add list variables to config_helper

Looks good! I think it would be helpful to include example of what an env file should look like.

Done!


Implement an OS Scan

Changes this pull request makes :
Implement an OS Scan using python-nmap package
Checklist :

[X] I have added the relevant documentation.
[X] My branch is up-to-date with the upstream master branch.
[X] I have fully tested the changes locally.

Development environment
OS: Linux
Python Version: 3.4.6

Fixes #53

This PR made my day :smile: , merged :)


[MetricsAdvisor] Bug: service requires condition operator

If we try to update a MetricWholeSeriesDetectionCondition.CrossConditionsOperator with a single condition during a patch operation, we get a back a 400 ("Invalid parameter. conditionOperator is required."). Likely to be a service bug.

Service issue. Closing this since it's not related to the SDK.


[PREVIEW] Replace hardcoded agent values with properties

I'm replacing hardcoded values in the agent with Properties classes.
Eventually the values will come from the server and get bound.

Coverage increased (+0.01%) to 92.458% when pulling d175fb51b217ca79dc88efbaf2436a28c62637d8 on mprimi:GENIE-265-agent-runtime-config into 0d51fac3bc72adf536a17027b2aed83d2c332132 on Netflix:master.


Generate Absolute Path, not Relative

I don't see anything in the documentation about generating an absolute path rather than a relative one, does such capability exist?

@ChristianTheMinery , CAssetManager.publish() is used to generate paths in yii-sass.
http://www.yiiframework.com/doc/api/1.1/CAssetManager#publish-detail
So if you want to have absolute paths then you should configure assetManager in your app accordingly.


FP: 930120 PL1

Description
Message: Warning. Matched phrase ".nsr" at ARGS:oaparams. [file "/etc/httpd/modsecurity.d/owasp-crs-modsecurity/rules/REQUEST-930-APPLICATION-ATTACK-LFI.conf"] [line "97"] [id "930120"] [msg "OS File Access Attempt"] [data "Matched Data: .nsr found within ARGS:oaparams: 2__bannerid=111__zoneid=2__cb=c43d331188__oadest=https:/www.nsrafoo.com/bar/baz"] [severity "CRITICAL"] [ver "OWASP_CRS/3.3.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-lfi"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/255/153/126"] [tag "PCI/6.5.4"]

Your Environment

CRS version (e.g., v3.2.0): 3.3.0
Paranoia level setting: PL2
ModSecurity version (e.g., 2.9.3): 2.9.2
Web Server and version (e.g., apache 2.4.41): 2.4.6
Operating System and version: EL7

Confirmation
[X] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.

What kind of software are you using? I mean one which was blocked.

What kind of software are you using? I mean one which was blocked.

Revive Adserver, but essentially it looks like any query string parameter which contains the string ".nsr" - which in this case was the start of a www.nsrxxxxx domain name.

Revive Adserver, but essentially it looks like any query string parameter which contains the string ".nsr" - which in this case was the start of a www.nsrxxxxx domain name.


Added regionCode to location response

Thanks but there is no region code specified in Google API geocoding docs.
We use administrative area level 1 as the region which itself might not fit for every location.


Backup Jenkins Home at 04-08-17-1144

This is a test.

Jenkins job istio-testing/presubmit passed


Unable to edit service alias

Hi.
I defined a service alias for a service. After that I need to remove the service to re-create it.
Now if I try to edit the service alias, all the page become white (I suppose it's the modal), but no way to change its settings, because no form appears

Useful
Info

Versions
Rancher v1.5.8 Cattle: v0.178.11 UI: v1.5.9

Access
localauth admin

Orchestration
Cattle

Route
stacks.index

@njordr do you have any browser plugins? Curious what browser this is... I wasnt able to reproduce this with 1.5.9 (local auth as well).

It's Firefox, but I tried also with brave and Chrome

I have the same Issue on Chrome and Safari

Have same issue on version 1.5.9 and 1.6 in browsers Safari 10.1 (126<IP_ADDRESS>.34) and Chrome 58.0.3029.110 (64-bit).

I have narrowed it down, the issue appears only for alias where the destination doesn't exists anymore

@tfiduccia I think we fixed this a while ago in 1.6.x

Version - 1.6.10 & 2.0 master 10/10
Verified fixed


Map custom type problem

Hi again!
I tried to implement a new Type in Astronomy, for JS Maps:
Type.create({
	name: 'Map',
	class: Map,
	validate(args) {
		return true;
	}
});

If I use the cast function to display the field value in my document, it display "Map {}". No problem here. But when on clientside I call findOne on a document, and then display the type of the field, it displays "Object{}". That's a real problem, because of that, I can't iterate correctly on it, nor call get, set, delete.
I can't seem to find what's going on, or what I missed. Any idea or valid custom type implementation for Maps?

If you take a look at this line: https://github.com/jagi/meteor-astronomy/blob/v2/lib/core/class.js#L157 you will see what's happening when we create a new class.
Type.create({
  name: className,
  class: Class,
  validate(args) {
    // Add current class as a param of validator.
    args.param = Class;
    Validators.class(args);
  }
});

We register a new type an provide as the class property the Class constructor. And what is Class? Class is an Astronomy class that is EJSONable. And Map is not EJSON able. You have to create wrapper around Map. Let's call it MeteorMap. Here is my example from docs how to define custom type in EJSON https://docs.meteor.com/api/ejson.html#EJSON-addType
class Distance {
  constructor(value, unit) {
    this.value = value;
    this.unit = unit;
  }
  // Convert our type to JSON.
  toJSONValue() {
    return {
      value: this.value,
      unit: this.unit
    };
  }
  // Unique type name.
  typeName() {
    return 'Distance';
  }
}
EJSON.addType('Distance', function fromJSONValue(json) {
  return new Distance(json.value, json.unit);
});
EJSON.stringify(new Distance(10, 'm'));
// Returns '{"$type":"Distance","$value":{"value":10,"unit":"m"}}'

Thanks for the quick reply. Maybe Astronomy could provide wrappers or custom types for the now standard Javascript types like Map, Set, ... ? I could try to do a PR if you want. :) or maybe it has been designed this way?

Hmm maybe I could implement it. I don't know if there is a high demand for
that. Maybe there is a way you could implement solution to your problem in
a different way? Could you tell me more about your use case?
On Jun 20, 2017 7:44 PM, "Genroa"<EMAIL_ADDRESS>wrote:

Thanks for the quick reply. Maybe Astronomy could provide wrappers or
custom types for the now standard Javascript types like Map, Set, ... ? I
could try to do a PR if you want. :) or maybe it has been designed this way?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jagi/meteor-astronomy/issues/621#issuecomment-309834839,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAKXW7Ns5G75O0aNzWaT5vkjuUPiDoeks5sGAUSgaJpZM4N_fcW
.

I'm currently a miniature's wargame army list builder, and obviouly, the Army object representing an army list contains Units. Theses units can't be in an Array field like [Unit], because if you are browsing to a url of this kind /edit/[unit_position] and the array changes (positions are changed or you add/remove a Unit from it), the whole interface would refresh. But unless you delete the unit, it shouldn't matter.
But because Unit is a nested field, it has no unique _id to get it. So, I tried to change the [Unit] field and use a Map, mapping a UUID to a unit when you add it. Maps have really clean and smooth to use methods, like get, set, delete. They are powerful, you don't need to hack it using an Object and its properties. My work is mainly software programing, so, you know, if something can be more appropriate for what I want to do, even if I could do it in a messy way, I wanted to try.
Sets and Maps could easily be parsed and be added to the custom types known by Astronomy, I think. Like any other type defined with the Type API. 😄

Give some example, I don't understand description of your problem.

Example:
`Army = Class.create({
name: 'Army',
collection: new Mongo.Collection('army'),
fields: {
...,
units: {
type: Map,
default: function(){return new Map();}
}
},
helpers: {
...,
	getUnits() {
		return this.units.values();
	},

	getUnitsUIDs() {
		return this.units.keys();
	},

	getUnit(uid) {
		return this.units.get(uid);
	},

	addUnit(unit) {
		let uid = uuidv4();

		unit._uid = uid;
		this.units.set(uid, unit);
	},

	removeUnit(uid) {
		this.units.delete(uid);
	}
}

});`

It would have to serialize and deserialize data on saves and reads which is not the best idea. MongoDB is supposed to store plain data not serialized Maps. EJSON which could serialize (stringify) Maps if properly extended is not intended to be used to store data in MongoDB. Astronomy could have a feature for converting maps to plain objects and later back to Maps but it would have to be one more step which would make code really slow. Your solution is quite good.
Taking all pros and cons, sorry but I'm not gonna implement this feature.


Multi-root: Allow disabling tests (discovery/prompts/...) for a root

Multi-root workspaces are motivated like this:

For example, you might have a repository with a product's documentation which you like to keep current when you update the product source code.

Exactly my use case. However, in such a multi-root workspace, I am now often confronted with the choice of one of the two folders for various operations. This is mostly fine, but really useless when it comes to testing: my documentation repo does not offer any testing whatsoever. So it's unnecessary work for me to select the product repo each time I discover tests, or run all tests, etc.
Maybe I have missed it, but a setting to disable all test functionality would be highly appreciated. I would then put this setting into the .vscode/settings.json in the documentation repo and be very happy. (If this already exists, I'd be even happier, but I haven't found it yet.)

@bersbersbers VS Code does not ship any test functionality by default, so I believe you wish to ask for this "ignore" support from an extension that you are using. What extensions do you use? (I could try to find out their repository information and point you to it)

Oh, you mean the "Test Explorer" is exclusive to the Python extension then? Interesting - I will refile with them. Thanks!


[MAID-2926, MAID-2922, MAID-2925] Miscellaneous chores

r? @ustulation
(maidsafe_highfive has picked a reviewer for you, use r? to override)


Some Tutorial on CSI products using some results from analysis for design for an idea workflow

This is a tutorial on how to use the connectors (mostly with GH) to use the results of the structural programs to do something cool with the viewers.

Closing for now as stale.


Fix ft.show_info() doesn't work in Jupyter(#650)

Pull Request Description
Fix the issue that ft.show_info() doesn't work in Jupyter.

After creating the pull request: in order to pass the changelog_updated check you will need to update the "Future Release" section of docs/source/changelog.rst to include this pull request.

 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.FreshLeaf8865 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@FreshLeaf8865 can you sign CLA/make sure it validates?

@FreshLeaf8865 can you sign CLA/make sure it validates?

Done!

These changes were handled by #863


gen2 rest+ Clock toggle not working

does the clock work for other users? I can't get mine to turn on or off even with the official hatch app, not sure if it's just me, but I suspect it is

seems like the clock toggle matches the in app toggle, it's just that my device has a long delay in reflecting the changes


filter by Technology on Projects Timeline & Map in report-v2

TODO: filter by Technology

apps (reports-v2 branch in apps_dev): report-v2

https://github.com/marineenergy/apps/blob/48a40ed0f1a9dffbd15b69d3b7efac3e3764b78f/report-v2/global.R#L226
which calls:
https://github.com/marineenergy/apps/blob/48a40ed0f1a9dffbd15b69d3b7efac3e3764b78f/scripts/shiny_report.R#L50-L118
and eventually based on ui.R, these get called in the server.R:
https://github.com/marineenergy/apps/blob/48a40ed0f1a9dffbd15b69d3b7efac3e3764b78f/report-v2/server.R#L130-L139
and finally, these are the functions that do the mapping and plotting of the initial outputs:
https://github.com/marineenergy/apps/blob/48a40ed0f1a9dffbd15b69d3b7efac3e3764b78f/scripts/shiny_report.R#L120-L288
To subsequently filter based on Technology Tags of Interactions, I think we want to use a Proxy for both leaflet map and plotly timeline, similar to here:
https://github.com/marineenergy/apps/blob/48a40ed0f1a9dffbd15b69d3b7efac3e3764b78f/report-v2/server.R#L146-L159

Now with @cdobbelaere...
Setup
Copied /share/github/apps_dev to /share/github/apps_cdob and created a branch projects-cdob. Then turned on Shiny app for public viewing (although launching in RStudio is better for debugging):
# change directory
cd /srv/shiny-server

# switch user and do (sudo) symbolically link (ln -s) the github folder to the shiny app URL
sudo ln -s /share/github/apps_cdob/report-v2 report-v2-cdob

Then app served at https://shiny.marineenergy.app/report-v2-cdob/.
Proxy for leaflet Map
leafletProxy("prj_map", data = filteredData()) %>%
      clearShapes() %>%
      addCircles(radius = ~10^mag/10, weight = 1, color = "#777777",
        fillColor = ~pal(mag), fillOpacity = 0.7, popup = ~paste(mag)

Proxy for plotly Timeline
References:

17 Server-side linking with shiny | Interactive web-based data visualization with R, plotly, and shiny
plotly 4.7.1 now on CRAN - Carson's blog on R, RStudio, plotly, shiny, data visualization, statistics, etc

Next step is to similarly proxy leaflet Timeline plot around here:
https://github.com/marineenergy/apps/blob/5715cda496a0144a02b7703dc9fbe0525e82f02e/report-v2/server.R#L165-L168
load_projects()
https://github.com/marineenergy/apps/blob/5715cda496a0144a02b7703dc9fbe0525e82f02e/scripts/shiny_report.R#L74-L142
plot_projects()
https://github.com/marineenergy/apps/blob/5715cda496a0144a02b7703dc9fbe0525e82f02e/scripts/shiny_report.R#L74-L142
Tips:

Note the use of the number of projects per Technology in the y axis given by n_riv, n_tid and n_wav
Maybe create helper functions to generate annotations (horizontal black line) and text (Riverine, Wave, Tidal)

Plotly projects timeline now updates according to selected technology.
Ex. 1 Initial plot:

Ex. 2 Filtering by tidal & wave energy:

Ex. 3 Filtering by riverine & tidal energy:


Sample Application

Objective
Develop a sample Flutter application that demonstrates the integration and usage of the plugin. The sample application should showcase the plugin's functionality, including screenshot capture, crash log recording, and network log capture. Provide clear instructions on how to run the sample application and observe the plugin's behavior.
Requirements

Develop a sample Flutter application.
Integrate the flutter_log_capture plugin.
Demonstrate screenshot capture functionality.
Demonstrate crash log recording functionality.
Demonstrate network log capture functionality.
Provide clear instructions on how to run the sample application.
Steps to Implement

Create a new Flutter application.

Add the flutter_log_capture plugin as a dependency.
Implement the UI to demonstrate screenshot capture.
Implement the UI to demonstrate crash log recording.
Implement the UI to demonstrate network log capture.
Write instructions on how to run the sample application.

Hey please assign this issue to me.

Go Ahead @Manikasethi

can you please share the link for this library

This is the library only @Manikasethi..

Ik but I'm Unable to find it on pub dev
I guess this is discontinued or something
If you have the link please share

This hasn't been uploaded, as it is still in development.

Okay, Thankyou


combobox ui bugs

Describe the bug
These are the bugs Erika found when doing a UI review of the auroized fly website page.  June and I have a branch with a fix to #34 but these are the remaining ones that are showing in combobox...

[x] Blue border thickness in active state doesn't match spec/auro-input https://github.com/AlaskaAirlines/auro-dropdown/issues/127
[x] #34
[ ] Click into field, click X, then the From/To label is no longer aligned properly
[x] Erroring prior to submission - noverify needs to be passed down to input from combobox #37

The one below is weird because it works perfect for me but not on Erika or June's screen.

[ ] The bolding of the letters in the menu that match the entered string - try light weight for menu items with book for the typed letters

For this let's implement flight search's city API so we can validate with real data.

[x] How is the sorting within the menu happening? Should function like the homepage widget today, but when you start typing "SE" the first few items in the menu don't have an 'S' and 'Seattle ...' is far down the list

Let's refine this list next week and break up any into separate issues if necessary.

https://www.figma.com/file/3TQhiKjQqQOKYqaqcO1zj2/Dropdown?node-id=906%3A753
Here is the blueprint!

This issue is difficult to follow. Some of this is done and others are not? I don't see a branch associated to this issue... nothing is really specifically assigned to anyone?
@jason-capsule42 and I are listed as assignees, but it's stated that @braven112 and @jason-capsule42 are working on things?
Please help to define what work needs to be done and who is expected to do it.


High msg rate cause memory corruption when enabling QUIC bridging

Describe the bug
High msg rate cause memory corruption when enabling QUIC bridging
Expected behavior
no crash no mem leak no corruption
Actual Behavior
==50890==ERROR: AddressSanitizer: heap-use-after-free on address 0x61f0000126a0 at pc 0x7f343029c397 bp 0x7f34189d7950 sp 0x7f34189d70f8
READ of size 3010 at 0x61f0000126a0 thread T40
#0 0x7f343029c396 in __interceptor_memcpy ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827
#1 0x7f342ff0c5a5 in memcpy /usr/include/x86_64-linux-gnu/bits/string_fortified.h:29
#2 0x7f342ff0c5a5 in QuicStreamSendBufferRequest ../nng/extern/msquic/src/core/stream_send.c:449
#3 0x7f342ff95ae7 in QuicSendBufferFill ../nng/extern/msquic/src/core/send_buffer.c:181
#4 0x7f342ff0e4e1 in QuicStreamSendFlush ../nng/extern/msquic/src/core/stream_send.c:594
#5 0x7f342ff522a5 in QuicConnProcessApiOperation ../nng/extern/msquic/src/core/connection.c:7194
#6 0x7f342ff527cb in QuicConnDrainOperations ../nng/extern/msquic/src/core/connection.c:7329
#7 0x7f342ff18dd5 in QuicWorkerProcessConnection ../nng/extern/msquic/src/core/worker.c:510
#8 0x7f342ff19e80 in QuicWorkerLoop ../nng/extern/msquic/src/core/worker.c:668
#9 0x7f342ff1a603 in QuicWorkerThread ../nng/extern/msquic/src/core/worker.c:733
#10 0x7f342fbec946 in start_thread nptl/pthread_create.c:435
#11 0x7f342fc7ca43 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x124a43)
0x61f0000126a0 is located 32 bytes inside of 3042-byte region [0x61f000012680,0x61f000013262)
freed by thread T3 here:
#0 0x7f3430316517 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:127
#1 0x55e69a7fd724 in nni_free ../nng/src/platform/posix/posix_alloc.c:33
#2 0x55e69a7e9727 in nni_chunk_grow ../nng/src/core/message.c:147
#3 0x55e69a7e9ef8 in nni_chunk_append ../nng/src/core/message.c:244
#4 0x55e69a7eb20d in nni_msg_append ../nng/src/core/message.c:524
#5 0x55e69a84d693 in nni_mqttv5_msg_encode_publish ../nng/src/supplemental/mqtt/mqtt_codec.c:1204
#6 0x55e69a848297 in nni_mqttv5_msg_encode ../nng/src/supplemental/mqtt/mqtt_codec.c:194
#7 0x55e69a8466e1 in nng_mqttv5_msg_encode ../nng/src/supplemental/mqtt/mqtt_public.c:37
#8 0x55e69a7c6657 in bridge_handler ../nanomq/apps/broker.c:219
#9 0x55e69a7c974b in server_cb ../nanomq/apps/broker.c:504
#10 0x55e69a7f7b61 in nni_taskq_thread ../nng/src/core/taskq.c:50
#11 0x55e69a7f8ef8 in nni_thr_wrap ../nng/src/core/thread.c:94
#12 0x55e69a801e00 in nni_plat_thr_main ../nng/src/platform/posix/posix_thread.c:266
#13 0x7f342fbec946 in start_thread nptl/pthread_create.c:435
To Reproduce
just sending massive msg to quick bridging topics
** Environment Details **

NanoMQ version 0.11

Client SDK
not related
Additional context
Add any other context about the problem here.

fixed in #813


Update the README.md examples

For example .plural has been replaced with .s - etc.

This example also seems broken. (haven't cracked this one yet :)
[rhyme:perfect] The <noun(1)::&a> <verb.ed(1)-transitive::&a> the <adj::&a> <noun(1)::&a>.
Sometimes gives 1 [?] (for 3rd word) - sometimes  2 [?] (for 3rd and 5th word) and sometimes  3 [?] (for 3rd 5th and 6th word):
for ex:
The goat [?] the stout throat.
The skirt [?] the [?] shirt.
The soup [?] the [?] [?].

That's because we don't have enough pronunciation metadata in Rantionary. Not a bug with Rant itself :)

Ahh. :) on my things to look into then..


docs: add spike essential filesystem

There is a lot of changes because I changed the folder name of the spike prime to differentiate it from spike essential

Thanks for your contribution!
I'm not sure about renaming all the spike - directories just in case that would break other links on the web.
Maybe the new filesystems could go in an spike essential -  set of directories?

Ok. Sorry for that. I think it'd done. Let me know if there is any change to be made.

Sorry, I hope this time it's ok 😅

Thanks for your contribution! :)


feat: initial version

Description

Initial version.
Todo:

[x] make workflow re-usable (tokens to be inputs)
[x] make script for copr download bulk of script, so it updates automatically
[x] make action create/update "package" on copr automatically
[x] add setup and create release to CI (in order to trigger beta/stable copr builds)
[x] fix branch for file download

Screenshot

Issues Fixed or Closed

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Dependency update (updates to dependencies)
[x] Documentation update (changes to documentation)
[x] Repository update (changes to repository files, e.g. .github/...)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

CI failed because .sh script doesn't exist on master branch yet.


[BEAM-9547] Initial implementation for where, mask

Adds an implementation for where and mask on DataFrame and Series.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @pabloem
Would you be able to review this?

ping @pabloem do you have time to review this?

ah yes I'll look. Sorry Brian!


Generate a Flask blueprint from an OpenAPI spec

Is there a way to only generate a Flask blueprint from an OpenAPI spec file ? And not pull all routing / viewing unrelated stuffs as promoted by the doc ?
While digging a bit into the source code I've found this simple workaround:
import connexion

...

app.register_blueprint(
    connexion.Api(os.path.dirname(__file__) + "/../api-v1.yaml", ...).blueprint
)

Do you validate it ?
What about covering this use case in the documentation ?

We don't document this, because this is not an interface we want to support.


Add a way to set a list item as activated

As per the appendix to the CSS Classes list of the MDC List documentation, list items can be either in selected or activated state. Currently, list items of angular-mdc-web are missing a way to be set to an activated state via an input. Instead, the class must be set through other means.

@draoncc Hey, revisiting issue after completing recent improvements upstream for MDC List. From what I gathered, mdc-list-item--selected and mdc-list-item--activated share the same styling properties.
// "Selected" is ephemeral and likely to change soon. E.g., selecting one or more photos to share in Google Photos.
// "Activated" is more permanent. E.g., the currently highlighted navigation destination in a drawer.
.mdc-list-item--selected,
.mdc-list-item--activated {
  @include mdc-list-item-primary-text-ink-color(primary);
  @include mdc-list-item-graphic-ink-color(primary);
}

Would you by chance have an example I could compare to our current implementation for v0.38.0 ?

Closing. Fixed upstream in upcoming build.
https://github.com/material-components/material-components-web/pull/3388


Assignment 1

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
I created a dask to hold price_data we retrieved from yahoo finance stock information and performed rolling 10 average on different stocks.
What did you learn from the changes you have made?
I have learned concepts of data engineering, tickers, dask, loggers and how to do modelling in production systems with millions of rows of data.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
This is good
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Nope
How were these changes tested?
Yes, ran in my local machine and outputs are attached
A reference to a related issue in your repository (if applicable)
NA
Checklist

[x] I can confirm that my changes are working as intended

A1 complete


[REQUEST] Add options to proxy 'Export' button

Hi,
please ability to export only Socks4 or Http or another proxy type, checked and alive proxies or only checked dead proxies on non checked proxies, or all of them, or socks4 and http ones together
ty

a window with some checkboxes


Make CORS headers configurable

I could do it by entering line
  http.response.setHeader 'Access-Control-Allow-Origin', '*'
next to the lines, but I guess it would better be configurable when constructing new files instance
http.response.setHeader 'Content-Type', vRef.type
http.response.setHeader 'Content-Disposition', dispositionType + dispositionName + dispositionEncoding
http.response.setHeader 'Accept-Ranges', 'bytes'
http.response.setHeader 'Last-Modified', fileRef?.updatedAt?.toUTCString() if fileRef?.updatedAt?.toUTCString()
http.response.setHeader 'Connection', 'keep-alive'

Hi @martunta ,
This feature is implemented in v1.6.3, as config.responseHeaders passed into Constructor.
See docs here and here
Please, test it on your end.

@martunta have you tested it on your end?

yes, it works


Add new JavaScript questions

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Also, please make sure to update the format for your questions so the key value pairs are in the same line.
Please follow this example:
  {
    Question: "What is a maximum length for a filename under Linux?",
    Answer: "255 Bytes",
    Distractor1: "225 Bytes",
    Distractor2: "235 Bytes",
    Distractor3: "295 Bytes",
    Explanation: "The maximum length for a file name is 255 bytes. The maximum combined length of both the file name and path name is 4096 bytes.",
    Link: "https://www.ibm.com/docs/en/spectrum-protect/8.1.9?topic=parameters-file-specification-syntax",
  },

Hi @amehi0index !
I am not seeing your recent changes committed in this PR.
You might need to double check and make sure your changes you made locally are showing up in your remote repo on GitHub.
Let me know if you have any questions! 😃

Thank you!