[LICENSE] Update NOTICE

:mag: Description
Issue References 🔗

This pull request fixes the NOTICE issue.
Describe Your Solution 🔧
According to https://infra.apache.org/licensing-howto.html#alv2-dep, we should analyze and bubble up the relevant portions into the top-level NOTICE file, no matter whether they're ASF projects or not.

If the dependency supplies a NOTICE file, its contents must be analyzed and the relevant portions bubbled up into the top-level NOTICE file.

Kyuubi has some code copied/derived from Apache Iceberg/Hive/Spark/Parquet MR, so we should update NOTICE to respect that.
Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Non-code change, review is required.

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Kyuubi has some code copied/derived from Apache Iceberg/Hive/Spark/Parquet MR, so we should update NOTICE to respect that.

Please also address these in the LICENSE file.

@yaooqinn listing them under LICENSE is not mandatory, just to facilitate traceability. We already use explicit words like "copied from XXXX" in class comments to achieve that.

It is best to list the files in LICENSE even if they are ALv2 licensed, as users know which files they are. As all ASFs have the same header files, it is hard to determine where a file comes from, and you may want to update it.

... as users know which files they are ...

for project-level auditing, it could be done by searching the keyword "copied from".
for the developer/user reading code, the inline comments are more convenient

In my experience, the tracking list maintained externally without an automated script to check is easily out-of-sync, and eventually corrupt.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (865a8b7) 61.27% compared to head (51b4e11) 61.21%.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5953      +/-   ##
============================================
- Coverage     61.27%   61.21%   -0.06%
  Complexity       23       23
============================================
  Files           622      622
  Lines         36882    36882
  Branches       5014     5014
============================================
- Hits          22599    22578      -21
- Misses        11852    11865      +13
- Partials       2431     2439       +8

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

cc @cfmcgrady you may have the full context of this PR

Thanks, merged to master/1.8/1.7


feat: suspense resolve immediately on available data

suspense will not force refetch if data is not stale
Based on: https://github.com/DamianOsipiuk/vue-query/pull/176

So apparently you can use await suspense() without onServerPrefetch when you set high enough staleTime, like staleTime: 5000 in nuxt 3.


attribute authorization_servers in the issuer metadata for Draft 13 is now an array and ends with an s

For draft 13 and above
If authorization server is given in the offer, take it to look for the authorize endpoint, token endpoint, PAR, etc. It means that the issuer server and the authorization server are 2 different servers.
Example of an offer for pre authorized code flow with an authorization_server attribute
 {
      "credential_offer": {
            "credential_issuer": "http://<IP_ADDRESS>:3000/issuer/npwsshblrm",
            "credential_configuration_ids": [
                  "Pid"
            ],
            "grants": {
                  "urn:ietf:params:oauth:grant-type:pre-authorized_code": {
                        "pre-authorized_code": "24b82a4d-27fd-11ef-9b72-0b0c8fc8184c",
                          "authorization_server": "http://<IP_ADDRESS>:3000/issuer/kwcdgsspng"
                  }
            }
      }
}

or
Example of an offer authorization code flow with teh authorization_server attribute
{
      "credential_offer": {
            "credential_issuer": "http://<IP_ADDRESS>:3000/issuer/kwcdgsspng",
            "credential_configuration_ids": [
                  "Pid"
            ],
            "grants": {
                  "authorization_code": {
                        "issuer_state": "test11",
                        "authorization_server": "http://<IP_ADDRESS>:3000/issuer/kwcdgsspng"
                  }
            }
      }
}

if the authorization server is not given in the offer

if the attribute authorization_servers : [ "https://....", "https://...."] exist in the issuer metadata take the first value as the authorization server endpoint (for well known/...)
if it does not exist, it means that the issuer and the authorization server are the same server

Becareful the new attribute authorization_servers (with 's' at the end) is now an array, it was previously a string
issuer metadata are in   <issuer URL>/well-known/openid-credential-issuer
authorization server metadata are in  <authorization server URL >/.well-known/openid-configuration

specs of eth authiorization_servers attribute
authorization_servers: OPTIONAL. Array of strings, where each string is an identifier of the OAuth 2.0 Authorization Server (as defined in [[RFC8414](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#RFC8414)]) the Credential Issuer relies on for authorization. If this parameter is omitted, the entity providing the Credential Issuer is also acting as the Authorization Server, i.e., the Credential Issuer's identifier is used to obtain the Authorization Server metadata. The actual OAuth 2.0 Authorization Server metadata is obtained from the oauth-authorization-server well-known location as defined in Section 3 of [[RFC8414](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#RFC8414)]. When there are multiple entries in the array, the Wallet may be able to determine which Authorization Server to use by querying the metadata; for example, by examining the grant_types_supported values, the Wallet can filter the server to use based on the grant type it plans to use. When the Wallet is using authorization_server parameter in the Credential Offer as a hint to determine which Authorization Server to use out of multiple, the Wallet MUST NOT proceed with the flow if the authorization_server Credential Offer parameter value does not match any of the entries in the authorization_servers array.

OIDC4VCI test 8, 10 , 11


fix: (IAC-632) tfvars PREFIX not applied to host nodes for k8s/Viya

Changes:
Updated the code to include the -<node_name> to show up for the node names.
Test
Verified the changes by creating cluster, instance names for the nodes were populated with prefix. See internal ticket for details.

Are these the only updates needed given the module update and prefix issues? Just checking.

The changes made in this PR match the -<node_name> format as before.

I made the changes a while ago, so had to do a rebase and found the default nodes didn't pick the prefix so made the similar changes. See internal ticket for testing details.

👍

LGTM


Add OSCORE Support to leshan-bsserver-demo

This aims to add support of OSCORE in the bootstrap configuration.
~This is work in progress.~
Some missing feature :

~making oscore/dtls exclusive~ Not needed :x:
~display  oscore is used in the bootstrap config list~ :heavy_check_mark:
~add support for bootstrap server wizard step (only dm is supported for now)~ :heavy_check_mark:
~handle object 21 deletion.~ :heavy_check_mark:

@rikard-sics, I think this is in a testable state now.

@rikard-sics, I integrated this in oscore branch, I also rebase oscore branch on master.


Sprint 1 check list

Self Grading Checklist
All self and by peer grading must be complete prior to Teacher review date(s).  Show a direct link to the tangible(s) for each line item.
Sprint1 Key Objectives
During the sprint you need to complete all of these key objectives and find and complete supporting hacks that show level of command you are declaring.
Rank to Ratio, rank is an integer
0 = .00 work, but faking understanding/accomplishment
1 = .55 incomplete assignment, big gaps
2 = .75 meeting some objectives, multiple little gaps
3 = .85 meeting most objectives, one little gap
4 = .90 meeting all objectives
4+Mastered-Y = .95 exceeding all objectives, requires links and  office hours verification

Skill
Mastered (Y/N)
Rank (1-4)
Ratio
Notes

Laptop Verification or Cloud Workspace
[ y]
4
0.0
verification by Linux commands notebook

VSCode
[n ]
4
0.0
live change code, commit, make, run localhost, test, debug

Show VSCode GitLens
[ n]
4
0.0
verify commits, show change, comments, reset to commit, run on old commit

GitHub student_2025 repo
[n ]
4
0.0
template create, push changes, verify id, review analytics

GitHub Pages Actions
[ n]
4
0.0
review runs and verify runtime, receive demo

Hacks Tools & Equipment Play
[n ]
4
0.0
Hacks

Hacks GitHub Pages Playground
[n ]
4
0.0
Hacks

Hacks SASS Basics
[ n]
0
0.0
Hacks

Hacks Frontend
[n ]
4
0.0
Hacks

Pair Programming
[ n]
0
0.0
tangibles that show coop work

Total
16

0.0

Average
?

0.0

Learning Habits Table
Review criteria in habits.  In this review, pairs should rate each other base on their experience with the person on the line item.
Rank to Ratio, rank is an integer
1 = .55
2 = .75
3 = .85
4 = .90
4+Mastered-Y = .95

Skill
Mastered (Y/N)
Rank (1-4)
Ratio
Notes

Attendance
[ y]
4
0.0

Work Habits
[ y]
4
0.0

Behavior
[ y]
4
0.0

Timeliness
[y ]
4
0.0

Tech Sense
[ y]
4
0.0

Tech Talk
[y ]
4
0.0

Tech Growth
[ y]
4
0.0

Advocacy
[y ]
4
0.0

Comm & Collab
[y ]
4
0.0

Integrity
[y ]
4
0.0

Organized
[n ]
2
0.0

Total
42

0.0

Average

0.0

Show Vscode Gitlens & VScode

Student_2025 Repo

Github Pages Actions

Hacks, Tools, and Equipmnt

Hacks Frontend


Set TargetManifestFiles in PropertyGroup (WIP)

Fixes #50
It's too late to set the TargetManifestFiles property inside a target that runs before publish. The dotnet sdk publish targets resolve the file list here. Since we don't rely on any other targets or properties to set TargetManifestFiles, the proposal in thiss PR sets the property in a property group before the donet sdk publish targets. Note that in this approach we no longer produce an error if the resolution of the manifest rid fails and will fail silently instead.
I tested on a local dotnet new console app with a package reference to M.A.All package and the publish output is trimmed.

That's why I originally asked why we didn't just set a property.


Building a .NET Standard library using Refit in Docker with .NET Core - mono not found

We have a .NET Standard library using Refit, and would like to integrate CI via GitLab. This means using Docker to build the library, and deploy it to our Nuget server.
We're using the microsoft/dotnet:1.1-sdk image, and the dotnet build line in our script fails with a mono: not found error:

error MSB3073: The command "mono "/root/.nuget/packages/refit/3.1.0/build/netstandard1.1/../../tools/InterfaceStubGenerator.exe" "obj/Release/netstandard1.5//RefitStubs.g.cs" "/...../...../....." "obj/Release/netstandard1.5/RefitParams.rsp"" exited with code 127.

Does that mean mono must always be available to build a project using Refit? It's working on .NET Core, right?
When I compile and deploy this .NET Standard library from my local machine (which has all the .NET tools, including mono), out .NET Core projects work flawlessly.

I think this may have been fixed for the next unreleased versions: https://github.com/paulcbetts/refit/commit/22e4fa46e9036d9d5398728d710e4ad59eb387fb

v 4.0 is out now


Dispenser Arrow Firing

Dispensers shooting arrows will always shoot towards the last position a player Placed/Interacted with an SU area.

w h a t
h o w

the heck

the heck


Clean up colwise

Instead of offering functions colmean, colstd, etc., I'd like to lean more heavily on colwise. Right now its behavior surprises, although I think I understand the logic.
using DataFrames
    df = DataFrame(A = 1:4, B = randn(4))
    colwise(cumsum, df) # -> Evaluates to Array{Any}

I assume we do this with the assumption that the return values for a function may differ in length across columns, which means that we can't do better than return a generic Array{Any}. That might be the right approach, but it's worth making sure that we prefer this very general strategy over something that would produce a more easily interpreted DataFrame.

Revisiting this 2 years later, colwise still returns an array of Any, where each element is a Vector, even when the result of each operation is a scalar. Example:
df =DataFrame(a = repeat([1,2,3,4], outer =[2]), b =repeat([2,3], outer =[4]), c =randn(8))
colwise(sum, df)

gives
3-element Array{Any,1}:
 [20]
 [20]
 [5.0978]

This is not really convenient for any further work on the column results.

@mkborregaard this has been addressed in DataTables by https://github.com/JuliaData/DataTables.jl/pull/28

Great, thanks for the heads up! Must be nice to be able to close a three year old issue :-)


[UI] Opening browser console docked at the bottom on trainer's page ruins the layout.

As title says. Happens both in Firefox and Chrome (didn't test other browsers).
Screenshots:

OS: Windows 7
Browsers: Firefox 74.0 , Chrome 80.0.3987.149

Fixed


CLI fails on projects that contain FSI signature files

Describe the bug
Running the CLI analyzer on a project that contains a signature file fails, with the error could not get context for file %s.
To Reproduce
Steps to reproduce the behaviour:

Create a project and add a signature file to it. FsProjWithFsi.zip
Run FSharp.Analyzers.Cli --project "FsProjWithFsi.fsproj" --verbose
Observe the error could not get context for file %s.

Expected behaviour
The analyzer CLI app shouldn't crash.
Environment (please complete the following information):

OS: Win10
Ionide version: n/a
VSCode version: n/a
dotnet SDK version: 5

Additional context
The root cause is that in createContext, FSharpCheckFileResults.ImplementationFile is None, which then short-circuits in runProject.
I'm not sure if signature files should simply be skipped for analysis by default, or if there's still potentially useful output that could be produced.

We should skip analysis of signature files entirely, this is a good catch!


Honor RESTIC_CACHE_DIR environment variable

What does this PR change? What problem does it solve?

CacheDir option doesn't honor the RESTIC_CACHE_DIR environment variable by default, this is done by default now.
This avoid checking for gopts.CacheDir and RESTIC_CACHE_DIR environment variable.
Was the change previously discussed in an issue or on the forum?
Fix #3382: restic check doesn't obey the RESTIC_CACHE_DIR environment variable

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[x] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[ ] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

@MichaelEischer Thank you for your quick feedback and guidance. I have updated the pull request.
If cache.DefaultDir return an error, should we only continue to fall back with TempDir or disable the cache with warning ?

When placing the temporary check directories inside the regular restic cache directory, then no there's no guarantee that a cleanup of these directories will occur.
The problem is that the current cache cleanup mechanism explicitly ignores all directories which don't look like a repository id. Changing that would require a change in the following location or somewhere nearby:
https://github.com/restic/restic/blob/553ea36ca62c870d71cd31d4091c86d0ec984e82/internal/cache/cache.go#L174

The temp directory restic-check-cache-* create a new subfolder cache dir with 64 character folder name and CACHEDIR.TAG file, changing the regex to accept this folder name will list the folder but not the content.
cache.OlderThan do not list recursively.
What should be the behaviour of cache --cleanup ? Always delete this folder ?
Best regards,

If cache.DefaultDir return an error, should we only continue to fall back with TempDir or disable the cache with warning ?

My reference to DefaultDir was only intended to illustrate what the other parts of restic, but wasn't meant to refer to the chagnes necessary here, sorry for the confusion. I'd like to have a new helper function next to DefaultDir which only queries the environment variable and does not fall back to os.UserCacheDir(). With the current change in the PR, the temporary cache directory would always be placed in the regular cache directory unless the environment variable was changed. But the PR should only change the behavior when the environment variable is specified and keep the old behavior in all other cases.

The temp directory restic-check-cache-* create a new subfolder cache dir with 64 character folder name and CACHEDIR.TAG file, changing the regex to accept this folder name will list the folder but not the content.
cache.OlderThan do not list recursively.
What should be the behaviour of cache --cleanup ? Always delete this folder ?

I don't think that there's a reason to not just delete the whole restic-check-cache-* folder. Each check run should use its own temporary cache folder.

Changing validCacheDirName with allow to list the restic-check-cache-*. but cleanup will remove the wrong caches and keep the last.

I'm not sure I understand. Which caches would cleanup remove which it shouldn't have?
I'd still prefer to just extend the cache name regexp and maybe filter the check caches from the output. That would also have the benefit of allowing automatic cleanups by other restic commands using --cleanup-cache.

For now, restic cache will not show restic-check-cache-* caches, but with --cleanup, it will remove regular cache dirs, and then search for restic-check-cache-* names and remove them too.

The code currently deletes every check cache it encounters even if it was created recently. That way it could actually delete a cache currently used by running check operation. Is there are reason not to use the same "x days old" logic as for normal cache directories?

Changing validCacheDirName with allow to list the restic-check-cache-*. but cleanup will remove the wrong caches and keep the last.

I'm not sure I understand. Which caches would cleanup remove which it shouldn't have?
I'd still prefer to just extend the cache name regexp and maybe filter the check caches from the output. That would also have the benefit of allowing automatic cleanups by other restic commands using --cleanup-cache.

For now, restic cache will not show restic-check-cache-* caches, but with --cleanup, it will remove regular cache dirs, and then search for restic-check-cache-* names and remove them too.

The code currently deletes every check cache it encounters even if it was created recently. That way it could actually delete a cache currently used by running check operation. Is there are reason not to use the same "x days old" logic as for normal cache directories?

I'm really sorry, I didn't fully understand the cache cleaning behavior, I just re-read the code and do some test and indeed this behavior is the correct one. I have updated the pr.
I chose to display all the caches, in order to allow the user to have the information and thus choose if he should run a cleanup.
Maybe we can filter the name to have a more explicit listing ?
Repo ID     Last Used    Old  Size
-----------------------------------------
restic-che  90 days ago  yes   95.066 KiB
d82a4e2897  0 days ago         95.023 KiB
-----------------------------------------

by
Repo ID                       Last Used    Old  Size
-----------------------------------------------------------
restic-check-cache-037381024  90 days ago  yes   95.066 KiB
d82a4e2897                    0 days ago         95.023 KiB
-----------------------------------------------------------

or
Repo ID                       Last Used    Old  Size
-----------------------------------------------------------
037381024 (check)  90 days ago  yes   95.066 KiB
d82a4e2897         0 days ago         95.023 KiB
-----------------------------------------------------------

Thanks again for your feedbacks,

Repo ID                       Last Used    Old  Size
-----------------------------------------------------------
restic-check-cache-037381024  90 days ago  yes   95.066 KiB
d82a4e2897                    0 days ago         95.023 KiB
-----------------------------------------------------------

I like that variant. The number after restic-check-cache is not a repository id, so just displaying that number would be misleading.
https://github.com/restic/restic/blob/6c84ea1412ecaec9b7bd02a08758c2aa8af46c29/cmd/restic/cmd_cache.go#L144
It should be sufficient to not shorten the repo ID when it starts with restic-check-cache-.

Change added in the last commit.
Best regards,


InflateException

Caused by: android.view.InflateException: Binary XML file line #57: Binary XML file line #57: Error inflating class com.miguelcatalan.materialsearchview.MaterialSearchView
Caused by: android.view.InflateException: Binary XML file line #57: Error inflating class com.miguelcatalan.materialsearchview.MaterialSearchView
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.miguelcatalan.materialsearchview.MaterialSearchView" on path: DexPathList[[zip file "/data/app/-----/base.apk"],nativeLibraryDirectories=[/data/app/----/lib/arm64, /system/lib64, /vendor/lib64]]

there is no same search_view.xml in my whole app but this exception occer in debug.apk ,
and release.apk  working fine , can you please explain me about that.


The GPU execution time never restart

Describe the bug
The GPU execution time never restart. My user is mregueira. I have used GPU time once but it has never restarted, I'm not able to start a GPU session anymore. I have tried to eliminate the account and create it again, but the issue remains
To Reproduce
Steps to reproduce the behavior:

Select compute type GPU
Click on Start run time
There is no runtime available right now. Please change the compute type or try again later.

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser chrome

Thanks for your support,
Miguel

I've been using sage daily for my little fun projects, for 5 days I have never been able to get a GPU machine, tried a new account, and still do the same thing, i think it is not from our side but its from sage maker side,i hope they add more datacenters i think since they only use East Us 2 as i have seen in someone thread or something ,good luck getting a notebook with GPU i guess until they fix it

Great to know, cannot complaint for a free service. If its lack of resources and not a bug that's it. It was weird for me that the first time I use it GPU worked but never again, but still it can be a coincidence.

Thanks all for the feedback. We are working on making it more accessible and fair.

When will this issue get fixed? I can only get cpu runtimes

Any update on when GPU's will be available again? I am teaching a data science class for a bootcamp, and all students are using Sagemaker Studio Lab. Without GPU's we can't train deep learning models. Greatly appreciate your making this service available free of charge - but is there a timeline on when it might be fixed? Thank you

Yeah, its literally impossible to get GPU sesions...

Dear @MiguelRegueira, we improved the GPU allocation recently. Could you please try launching the GPU instance ? (you do not need to recreate your account). If the problem solved, please let us know by closing this issue. We are very glad if we can support your working on your data science assignment.

Thanks a lot! I've been able to start an execution on GPU. Closing the issue.

I have been also facing the problem I trained my model halfway yesterday and thought the remaining GPU time would restart today as well. After yesterday's training, I had only 45 mins left for GPU usage. WIll it get renewed today?
As I need more time to train the model efficiently and then validate and predict using my model?


Script Debugger in Xplore scripts

It's not a bug, but a new feature. I have looked a bit, maybe it's there, but I did not find it... sorry if it's me missing it.
It would be great if you could check a box or dispose of a "Run in Script Debugger" button and when you run your code it would open Script Debugger and step througth your code with a break point on the first line (or allow to add break point in the script)...

Great suggestion. Not sure how I go about this right now, may need some re-engineering. Will keep this open for future thought.

If I move my script / code into a Script Include and then call that from Xplore, I can use the debugger, it's just an extra step and it bypasses the ability to catch the gs.addInfoMessage and other logs - which I also love using. I really want to help on this, @jneale do you already have a plan for debugging brewing in the back of your mind? I'll devise my own if no... (love this plugin)

btw it is possible to debug xplore script running in a non-global script. Just set your breakpoint in the first line of snd_Xplore_code

But this does not work for scripts run in the global scope because snd_Xplore_code is not used in that situation


Import actions dynamically

Resolve #2
Import actions dynamically from the name.
A prefix can be set in the config, so the name does not need to be the entire import path.

Codecov Report

Merging #4 into master will decrease coverage by 1.73%.
The diff coverage is 44%.

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
- Coverage   74.04%   72.31%   -1.74%
==========================================
  Files          12       12
  Lines         551      567      +16
==========================================
+ Hits          408      410       +2
- Misses        143      157      +14

Impacted Files
Coverage Δ

smapy/resource.py
59.34% <100%> (-0.66%)
:arrow_down:

smapy/api.py
83.13% <41.66%> (-16.87%)
:arrow_down:

Continue to review full report at Codecov.

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


Clicking notifications icon displays a dropdown, 'See All' brings you to notification page, both use infinite scroll

Currently, there's a very nice feature where if you're watching a video you will be alerted in live time of a new notification and it will increment the notification amount. Such as:

However, major sites like Facebook and YouTube have the functionality whereby clicking on this notification will simply drop down a dropdown box, at which point the user can see the notification without having to leave their content. This is especially useful if someone is in the middle of viewing content, and with the dopaminergic effect of wanting to click that notification immediately, and also with the fact that users are already used to another flow, we will probably want to just adopt the standard YouTube/Facebook have set rather than train a user to not click the notification button when they get a new notificaiton.
I'd like to suggest a dropdown with infinite scroll, that also has a 'See All' button that links to the current notification page. Currently the existing notification page doesn't have infinite scroll, pagination was suggested for notifications here ( https://github.com/lbryio/lbry-desktop/issues/6510 )  but as infinite scroll is what YouTube and Facebook does and that it feels really natural (and could also be reused in the dropdown functionality) I'd like to suggest the notifications page also uses infinite scroll.
How Facebook looks/functions:

How YouTube looks/functions:

Great write up, will close mine at https://github.com/lbryio/lbry-desktop/issues/6391

@tzarebczan please transfer

Issue moved to OdyseeTeam/odysee-frontend #1417 via ZenHub


ConnectionResetError is not being retried by the Table client

Package Name: azure-data-tables
Package Version: 12.4.0
Operating System: Linux
Python Version:  3.8.10

Describe the bug
We have been receiving a lot of TCP Connection failures for table client.
  File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.8/site-packages/enterprise_event_broker/AzureEventHubPublisher.py", line 121, in periodically_save_hwm
    self.save_high_water_mark()
  File "/usr/local/lib/python3.8/site-packages/enterprise_event_broker/BaseEventPublisher.py", line 118, in save_high_water_mark
    raise excep
  File "/usr/local/lib/python3.8/site-packages/enterprise_event_broker/BaseEventPublisher.py", line 112, in save_high_water_mark
    self.__hwm_table_client.upsert_entity(entity=hwm_record, mode=UpdateMode.MERGE)
  File "/usr/local/lib/python3.8/site-packages/azure/core/tracing/decorator.py", line 78, in wrapper_use_tracer
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/azure/data/tables/_table_client.py", line 652, in upsert_entity
    metadata, content = self._client.table.merge_entity(  # type: ignore
  File "/usr/local/lib/python3.8/site-packages/azure/data/tables/_generated/operations/_table_operations.py", line 700, in merge_entity
    pipeline_response = self._client._pipeline.run(request, stream=False, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 211, in run
    return first_node.send(pipeline_request)  # type: ignore
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 71, in send
    response = self.next.send(request)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 71, in send
    response = self.next.send(request)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 71, in send
    response = self.next.send(request)
  [Previous line repeated 1 more time]
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/policies/_authentication.py", line 118, in send
    response = self.next.send(request)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 71, in send
    response = self.next.send(request)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/policies/_redirect.py", line 158, in send
    response = self.next.send(request)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 71, in send
    response = self.next.send(request)
  File "/usr/local/lib/python3.8/site-packages/azure/data/tables/_policies.py", line 225, in send
    raise err
  File "/usr/local/lib/python3.8/site-packages/azure/data/tables/_policies.py", line 201, in send
    response = self.next.send(request)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 71, in send
    response = self.next.send(request)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 71, in send
    response = self.next.send(request)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 71, in send
    response = self.next.send(request)
  [Previous line repeated 1 more time]
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/_base.py", line 103, in send
    self._sender.send(request.http_request, **request.context.options),
  File "/usr/local/lib/python3.8/site-packages/azure/data/tables/_base_client.py", line 334, in send
    return self._transport.send(request, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/azure/core/pipeline/transport/_requests_basic.py", line 361, in send
    raise error
azure.core.exceptions.ServiceResponseError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))

In these line of code, the sdk doesn't handle the non-http related error codes.
https://github.com/Azure/azure-sdk-for-python/blob/7cfb4ee29a51c0f1b55278a099368443a0f48434/sdk/tables/azure-data-tables/azure/data/tables/_policies.py#L214-L225
azure.core.exceptions.ServiceResponseError is an AzureError but it fails to be retried as this method seems to be only handling PATCH methods if the response code is 5XX.
https://github.com/Azure/azure-sdk-for-python/blob/7cfb4ee29a51c0f1b55278a099368443a0f48434/sdk/core/azure-core/azure/core/pipeline/policies/_retry.py#L165-L186
To Reproduce
Steps to reproduce the behavior:
Hard to reproduce as these Connection Reset Error occurs at the TCP layer. But have seen many instances of this issue on this sdk.
Expected behavior
RetryPolicy should handle ConnectionResetErrors as well.

Hi @preethamrajk - Thanks for your report!
🤔This seems to be a service-related issue. We'll investigate asap!

Hi @swathipil @YalinLi0312
Is there an update on this issue?

Hi @preethamrajk , we are preparing new features release recently, will back to investigate asap. Thanks

@YalinLi0312  Hi, just wondering if there's an update for this feature?

@YalinLi0312  Yes. Is there a rough timeline as to when the fix will be released? Thank you :)

@YalinLi0312 Yes. Is there a rough timeline as to when the fix will be released? Thank you :)

We usually releasing packages at the second week of each month, but we also can ship a preview at anytime when the bug is fixed.

Hi @preethamrajk  @LucasH-Coles , the operation you want to retry on is a PATCH request, it is not retriable by default. Can you try passing keyword retry_on_methods=["PATCH"] in upser_entity()? It should reset this operation to retry.


Fix display of multiple help entries

The upper part of the list is truncated. I will look at fixing that - creating an issue just to remind myself.

Solution here is to overwrite HELP_SHOW_MATCHES to return a properly HTML formatted list of links...


NoSQL update

This commit cleans up the VOLUME support by separating the /kvroot and turning that into a volume. This means the data itself can persist an upgrade of the NoSQL binaries.

Note this requires #381 to be merged first.

@nirmay can you please review this and see if it's more aligned with what you wanted to achieve with your previous PR?

Ok, have squashed all the changes so that only the Dockerfile diff requires review.

It's fine by me.

I will wait for @nirmay to comment/review to make sure I'm meeting his expectations for VOLUME support.

Thanks @Djelibeybi for taking the time to make these changes, this is a better approach.


When splitting strings without spaces, look for punctuation

-        format!("file_name,\"{}\",file_line,{},file_col,{},extent_start,{},extent_start_bytes,{},\
-                 file_line_end,{},file_col_end,{},extent_end,{},extent_end_bytes,{}",
+        format!("file_name,\"{}\",file_line,{},file_col,{},extent_start,{},extent_start_bytes,{},f\
+                 ile_line_end,{},file_col_end,{},extent_end,{},extent_end_bytes,{}",

We should prefer splitting at , . ; : rather than the middle of a word.

http://www.unicode.org/reports/tr14/

I'm figuring out how to fix this (it seems easy and I am looking to start helping), but I can't seem to test it. When i try to format a very long string, rustfmt won't even let me format lines that are that long.

Could you give an example of input and the error message? That is unexpected and sounds like a bug.

Nevermind, sorry, it was my bad. I'm can now test my code.


Errors you may encounter when upgrading the library

An error will happen when upgrading library prometheus/client_golang:
github.com/prometheus/client_golang
-Latest Version: v1.7.1   (Latest commit fe7bd95 5 days ago)
-Where did you use it:
https://github.com/docker/swarmkit/search?q=prometheus%2Fclient_golang%2Fprometheus&unscoped_q=prometheus%2Fclient_golang%2Fprometheus
-Detail:

github.com/prometheus/client_golang/go.mod

module github.com/prometheus/client_golang
require (
	github.com/beorn7/perks v1.0.1
	github.com/cespare/xxhash/v2 v2.1.1
…
)
go 1.11

github.com/prometheus/client_golang/prometheus/desc.go

package prometheus
import (
	"github.com/cespare/xxhash/v2"
	…
)

This problem was introduced since prometheus/client_golang v1.2.0(committed 9a2ab94 on 16 Oct 2019) . Now you used version v0.8.0. If you try to upgrade  prometheus/client_golang to version v1.2.0 and above, you will get an error--- no package exists at "github.com/cespare/xxhash/v2"
I investigated the libraries (prometheus/client_golang >= v1.2.0) release information and found the root cause of this issue is that----

These dependencies all added Go modules in the recent versions.

They all comply with the specification of "Releasing Modules for v2 or higher" available in the Modules documentation. Quoting the specification:

A package that has migrated to Go Modules must include the major version in the import path to reference any v2+ modules. For example,  Repo github.com/my/module migrated to Modules on version v3.x.y.  Then this repo should declare its module path with MAJOR version suffix "/v3"  (e.g., module github.com/my/module/v3), and its downstream project should use "github.com/my/module/v3/mypkg" to import this repo’s package.

This "github.com/my/module/v3/mypkg" is not the physical path. So earlier versions of Go (including those that don't have minimal module awareness) plus all tooling (like dep, glide, govendor, etc) don't have minimal module awareness as of now and therefore don't handle import paths correctly See golang/dep#1962, golang/dep#2139.

Note: creating a new branch is not required. If instead you have been previously releasing on master and would prefer to tag v3.0.0 on master, that is a viable option. (However, be aware that introducing an incompatible API change in master can cause issues for non-modules users who issue a go get -u given the go tool is not aware of semver prior to Go 1.11 or when module mode is not enabled in Go 1.11+).
Pre-existing dependency management solutions such as dep currently can have problems consuming a v2+ module created in this way. See for example dep#1962.
https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

Suggested solutions
1. Migrate to Go Modules.
Go Modules is the general trend of ecosystem, If you want a better upgrade package experience, migrating to Go Modules is a good choice.
2. Keep using the dependency manage tool (like dep, glide, govendor, etc).
Because the import paths have different meanings between the projects adopting module mechanism and the non-module mechanism.

https://github.com/golang/go/wiki/Modules#semantic-import-versioning
https://golang.org/cmd/go/#hdr-Module_compatibility_and_semantic_versioning
https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

If you prefer to use the dependencies manage tool (like dep, glide, govendor, etc), a textbook example provided by repo github.com/moby/moby can prevent this type of issues.
https://github.com/moby/moby/blob/master/VENDORING.md
https://github.com/moby/moby/blob/master/vendor.conf
In the vendor directory, github.com/moby/moby adds the /vN subdirectory in the corresponding dependencies.
This will help more downstream modules to work well with your package, otherwise they will be stuck in github.com/cespare/xxhash v1.1.0.
By the way, have you ever encountered such errors when upgading the libraries? Do you plan to upgrade the libraries in near future?
Hope this issue report can help you ^_^
Thank you very much for your attention.
Best regards,
Kate

@dperny  @thaJeztah  Could you help me review this issue? Thx :p

Not sure I understand the problem; where are you trying to update the github.com/prometheus/client_golang dependency ?

If you try to upgrade prometheus/client_golang to version v1.2.0 and above, you will get an error--- no package exists at "github.com/cespare/xxhash/v2"

So, you're trying to update that dependency, but didn't add the new dependency to vendor.conf, and didn't run vndr to bring the new dependency in? vndr (the tool currently used in this repository for vendor management) does not automatically add new dependencies; it requires new dependencies to be manually added to vendor.conf.

By the way, have you ever encountered such errors when upgading the libraries? Do you plan to upgrade the libraries in near future?

Feel free to open a pull request to update. I generally would recommend to update the docker/docker dependency, and update other dependencies accordingly (so that they match the version that's used in the docker/docker (moby/moby) codebase.

@thaJeztah   Thanks for your reply. This report is a warm prompt for you to prevent or combat this issue. Just let you know the problem if you upgrade this dependency in near future.
Hope this can help you.
Thanks again.
Kate


Allow PRs from forks to run on CI

I had to deactivate the Build pull request updates option on Travis because secure environment variables do not get exposed on fork PRs, due to the fact that this would be a security risk. This causes builds to break because Sauce Labs fails to connect without the required environment variables.
Some ideas from this PR about how we could still run most of our CI on foreign forks:

Using conditional builds to only run tasks that don't depend on special vars; like linting, functional tests
Running integration tests against phantomjs on CI for forks (had some issues with this previously when testing locally)
Running integration tests against firefox or chrome on CI for forks (on the Travis linux box itself, I think I've seen it done)

Might be fixed by https://github.com/alphagov/accessible-autocomplete/issues/132.
Using https://github.com/alphagov/accessible-autocomplete/pull/133 as a guinea pig.

This is now fixed.


Timeout while trying to browse through Webdav-Share

We have a working setup with Onlyoffice Community and Document Server. A few days ago the functionality of browser through webdav shares and editing files stopped working.
Setup:

VM1:
8 CPU, 16 GB RAM, 100 GB SSD
Ubuntu Server 20.04 LTS
Community and Document Server installed with opensource-install.sh without mail-server
Public Domain with office.domain.com
VM2:
4 CPU, 16 GB RAM, 500 GB SSD
Ubuntu Server 18.04 LTS
Nextcloud 19.0.3
Public Domain with domain.com

I mounted a Nextcloud Webdav-Share and shared it with a group in community server. All worked fine for 5 weeks. Two days ago browsing through the folder structure in community server was slower and opening a docx or xlsx was  often really slow or ended up with an error, that the file was not able to be opened.
Then I updated the VM1 with bash opensource-install.sh -u true which updated the document server. Nothing was better. After that i removed the webdav sahre an added it again. Now, when trying to browse through the share it takes some 30seconds ("Loading ... please wait") or so ...

... and then it redirects to "My Documents".
Hint:
The Nextcloud side has no problems. No error logs there. Browser directly through the webdav share ist no problem an editing files from within the nextcloud interface with Onlyoffice is also no problem.
Does anybody has a solution for our problem?

Edit:
I tried two different webdav-services (magentacloud an another Nextcloud in version 18). Those two services work. The webdav share that doesn't work is from a Nextcloud 19.0.3.
I had a look on the last Update (19.0.2 -> 19.0.3): In the release news there is one point regarding "dav", see https://github.com/nextcloud/viewer/pull/582
--> Could this update be the problem for Onlyoffice Community Server to load the webdav directiory?

Hello @ttjaden Please check the web.files.log, web.api.log and web.log for the errors. Maybe some happens in your network or servers network?

@Carazyda : I tried to integrate the webdav share and afterwards i downloaded all the logs you've said.
within web.files.log I found
  at ASC.Web.Files.Services.DocumentService.DocumentServiceConnector.GetConvertedUri (System.String documentUri, System.String fromExtension, System.String toExtension, System.String documentRevisionId, System.String password, System.Boolean isAsync, System.String& convertedDocumentUri) [0x00038] in <c1973b05c8414a40bb633c2cd827ba68>:0
  at ASC.Web.Files.Utils.FileConverter.CheckConvertFilesStatus (System.Object _) [0x002f2] in <c1973b05c8414a40bb633c2cd827ba68>:0

Within the other log-files I didn't find somethind "strange" but on the other side, I don't know for what I have to look out!?

@ttjaden Can you show the error text from date? For this fragment of log i can't say something. And also please check console and network of browser for the errors, when you redirect to My Documents folder.

Unfortunately I don't find the time to look for the errors. We will switch back to Nextcloud as the main service and use OnlyOffice only as document server.
Thanks for you support!


US Census and Tiger maps node with links in option description

The new node dialogs have a little icon next to each dialog option. To make it easier for people to find the right MIPS etc numbers it would be great if we could add a link to a lookup page to the corresponding dialog option so that the link is shown directly in the node dialog when clicking on the question mark of the option.

Add a hyperlink of the FIPS code list onto the icon links of the census and tiger node


chore: cleanup unused and deprecated code

Making this PR to run the benchmarks for the release, no functional changes are included.

/run_benchmark interlay

/run_benchmarks interlay-dev

/run_benchmarks interlay-dev

/run_benchmarks interlay-dev

/run_benchmarks interlay-dev

/run_benchmarks interlay-dev


Add aten::record_stream

[x] record_stream

This op has no unit tests for xpu in stock pytorch at the moment, essentially due to lack of xpu counterpart of torch.cuda._sleep(). In CUDA unit tests of this op, torch.cuda._sleep() is used to delay one stream suffciently long. So, during local testing I replace it with an expensive kernel and translate two tests from test_cuda.py to effectively test this op (and it passed).
I will work on finding a good way to add unit tests for this op.

Please be aware - this OP is widely used in distributed FSDP.


Updated to be compatible with Swift 3.0 2016-08-18-a snapshot

Looks like the ordering of tests changed a bit:
/home/travis/build/vapor/json/Tests/JSONTests/JSONTests.swift:45: error: JSONTests.testComplex : XCTAssertEqual failed: ("{"bool":0,"null":null,"string":"ferret 🚀","int":42,"double":3.14159265358979,"array":[null,1,1337,"😄"],"object":{"nested":"text"}}") is not equal to ("{"bool":0,"int":42,"null":null,"string":"ferret 🚀","double":3.14159265358979,"array":[null,1,1337,"😄"],"object":{"nested":"text"}}") -

I can fix this. Thanks for the PR!


vconverter: add more element during the lexer phase

Store the value also in addition to the kind of token that we found in the stream, helps us to improve the syntax a little bit
https://github.com/vincenzopalazzo/vbook/blob/main/vconverter/markdown/scanner.v

Fixed in https://github.com/vincenzopalazzo/vbook/commit/43ad2d5ac02bf9182a71aa45de4ea44084650173


Rewrite shaders to WebGL2.0 [Fixes #65]

I had an idea of implementing VertexArrayObjects in this PR as well, but it looks like there's some deeper architectural thinking required there, so let's open #81 and move the discussion there.

While I applaud the use of the modern technology, it's worth pointing out that moving to WebGL2 affects the compatibility matrix of Cervus:

Can I Use: WebGL (91% global support)
Can I Use: WebGL2 (58% global support)

Do you plan to go all out on WebGL2 or would you like to maintain backward compatibility with Edge and Safari?

WebGL2 was a plan since the very beginning, I temporarily returned to WebGL when working on ShadowMaps and forgot to reimplement everything again after I failed.
Safari already supports it behind the flag, and Edge works on that as well.
The initial idea behind Cervus was that when new WebGL will became widely supported standard we'll already be there, ahead of all the other js game engines. For now almost 60% of global support is good enough.

This makes perfect sense, thanks!


Setting android:textViewStyle makes labels ignore fab:fab_labelStyle

When you create a custom textViewStyle in a theme, apply the theme to the Activity you use the floating action button in, the properties set in fab_labelStyle are ignored.

Thanks for reporting this issue.

I have successfully reproduced the issue, but I have no idea how to solve it. I don't understand why using style attribute from XML overrides the textViewStyle from theme, but using ContextThemeWrapper does not. Bug? Feature?

@chalup Thanks for coming back to me. :smile:
I don't know much about this problem, but it looks like there may be some options to explore.

Use TextView.setTextAppearance(Context, int).
Using a cloned LayoutInflater, which is suggested on StackOverflow.

Already tried option 2, doesn't work.
On Feb 2, 2015 9:31 PM, "Wijnand Warren"<EMAIL_ADDRESS>wrote:

@chalup https://github.com/chalup Thanks for coming back to me. [image:
:smile:]
I don't know much about this problem, but it looks like there may be some
options to explore.

Use TextView.setTextAppearance(Context, int).
Using a cloned LayoutInflater, which is suggested on StackOverflow
http://stackoverflow.com/a/15496425.

—
Reply to this email directly or view it on GitHub
https://github.com/futuresimple/android-floating-action-button/issues/123#issuecomment-72531717
.

The 1st option works, unless textViewStyle from theme contains style elements outside of appearance scope, like background.
It's still and improvement, so I'm implementing it in 0bac367. @wjwarren does that solve your use case?

@chalup Works like a charm! :)


Bio Metric - Average Time Between Draw Order and Collection

Please run descriptive statistics on the time between draw order placement time and clinical collection time in days for each KP site. Include records with a clinical collection date on or after 02/01/2023. I've included a mock-up table below.
Variables/CIDs:

Date/Time Blood Order Placed - BioClin_BldOrderPlacdDt_v1r0 (769615780)
Date/time Clinical Blood Collected - BioClin_ClinBloodTime_v1r0 (982213346)

@HopkinsDC  Please see below and let me know if you need this as just a one time metric or added to a report
Average-Time-Between-Draw-Order-and-Collection.pdf

@KELSEYDOWLING7 This looks great, Kelsey.
Please remove the number column on the far left, align the KP site names to the left, and add this to the biospecimen metrics report; make it Table 22 and make the "Clinical Blood Draw Order Status Among Verified Participants" Table 23.


Feature/event patterns

depends on https://github.com/PythonFreeCourse/calendar/pull/126

Codecov Report

Merging #127 (e6970d0) into develop (d706153) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##           develop      #127   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           16        17    +1
  Lines          544       622   +78
=========================================
+ Hits           544       622   +78

Impacted Files
Coverage Δ

app/database/models.py
100.00% <100.00%> (ø)

app/internal/event.py
100.00% <100.00%> (ø)

app/routers/event.py
100.00% <100.00%> (ø)

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 d706153...1557208. Read the comment docs.

Codecov Report

Merging #127 (e6970d0) into develop (d706153) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##           develop      #127   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           16        17    +1
  Lines          544       622   +78
=========================================
+ Hits           544       622   +78

Impacted Files
Coverage Δ

app/database/models.py
100.00% <100.00%> (ø)

app/internal/event.py
100.00% <100.00%> (ø)

app/routers/event.py
100.00% <100.00%> (ø)

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 d706153...1557208. Read the comment docs.


is it possible to change the period of time of the calendar?

Hi, i'm new to the react native.
since the currently calendar are begin in 0:00, how could i change the begin time like 8:00? or any method that i can hide the grid from 0:00 to 8:00?
thank you!

Hi, thanks for trying the library!
You can use the prop startHour to indicate the vertical position of the calendar in the first render, for example startHour={8} for 8 am. Although the user could still scroll and see the grid between 00:00 and 8:00
Hiding the start of the grid is a feature similar to #168 and #70, like providing startAt and endAt, and hiding the test of the of the grid.
I'll try to implement this soon

Update: option 2 is now implemented in the props beginAgendaAt and endAgendaAt


Update Composer dependencies (2021-10-30-00-07)

Visual regression test passed!
View the visual regression test report


Add typescript declaration file

Cloudflare Workers mostly opt for using TypeScript.
Adding a declaration file helps developers get insights as they type and helps prevent errors (and typos) early.
Exposing both the "commonjsModule" as default and named exports allows import in both ways:
import { getTokenFromGCPServiceAccount } from<EMAIL_ADDRESS>
and
import workersJWT from<EMAIL_ADDRESS>
const token = workersJWT.getTokenFromGCPServiceAccount({…});

Examples:

Resolve #19

Thanks @omrilotan. LGTM.

Publish to npm as<EMAIL_ADDRESS>

Regretfully, the file did not make it into the published package. Addressed in #28


Update size of toolbar to take new icons

Wouldn't that be involved automatically with #6?

No. Just tried it with some XParticle icons. No scaling.

The reason it doesn't change size like other toolbars is because it's actually a dialog and not a toolbar.

Yes, but we can't make it an actual palette. It would require turning each button into a CommandData plugin and be able to open a palette from code (which I believe is not possible with the SDK).

The combobox is just a placeholder, looking to add another button there to toggle 20/32 pixel size icons.

You don't want to make it into a proper toolbar so i behaves like all the other toolbars?

Too much work for now
User would need to pop out the toolbar window manually

Ok :)

Now right-click menu but items in the dialog menu bar instead. You can also choose a vertical layout and your choice is being remembered.

Hey. Thats great!

I made a tmp update to the icons to get the right size: https://github.com/nr-plugins/resedit/pull/9

Merged, and 1c9173c fixes the icon size.


need to specify --target for the icons to be placed in the correct place

When only running tauricon the icons get placed in no-mans-land.
I can investigate this further, just want to register this so I don't forget it.
Linux
fish shell
To get the correct behaviour I need to do
tauricon --target ./src-tauri/icons

Did you install tauricon globally or locally? If globally i wonder why it didn't crash, because it actively looks for a tauri.conf file

now I've verified this.
This gives no icons (have not searched for the icons, but they are not in the project folder at least)
Simple setup to reproduce
yarn add -D @tauri-apps/tauricon:github:tauri-apps/tauricon
mkdir -p src-tauri/icons
npx tauricon

But if you instead run it like this it works
npx tauricon --target src-tauri/icons


Test Framework changes for parquet filter pushdown project.

Hi Chun,
Can you review these changes?
Thanks.
--Robert

Hi Chun,
I have updated the code.  Please review them.
Thanks.
--Robert

Hi Chun,
I have updated the code. Please review them.
Thanks.
--Robert

LGTM. +1
Please make sure you run pre-commit test with the code change. Thanks for the improvement.


Siddhi Event Table "in" condition behaves as filter when passed as delete/update condition

Description:
from FooStream
select symbol
delete FooTable
on FooTable.symbol in symbol;
Here, the ( FooTable.symbol in symbol ) will be treated as filter where symbol will be the table id and FooTable.symbol will be an expression.

@niveathika Is this issue still valid ?

Yes, it is still valid, see https://github.com/niveathika/siddhi/blob/table-join-in/modules/siddhi-core/src/test/java/io/siddhi/core/query/table/DeleteFromTableTestCase.java#L338,
It is mainly validation improvement, the user should not be able to write queries with in operator.


minor rem_part bug for certain ACSet schemas

There is a bug that prevents one from using rem_part on an initial CSet schema instance due to type ambiguity of a Dict. This is a really minor fix that is needed for the following example to work.
using Catlab.CategoricalAlgebra
using Catlab.Present
using Catlab.Graphs

initG = Graph(1)
rem_part!(initG, :V, 1) # WORKS!

@present ThInitial(FreeSchema) begin
  I::Ob
end

@acset_type Initial(ThInitial)
init = Initial()
add_part!(init, :I)
rem_part!(init, :I, 1) #ERROR in calling rem_part_body

Thanks Kris! Owen, can you please review?


Tests: Setup automatic tests with github workflow for this project.

So that we are absolutely sure while merging that the code changes are not causing a regression

We need to add a github actions to trigger when saomeone create a pr for this repo right

We need to add a github actions to trigger when saomeone create a pr for this repo right

Yes. There is already a check for yarn build (ie, the build is successful) but need is to add more tests (like running demo scripts etc).


Allow Role to run when become_method is su

This allows the check for unzip to run when the become_method is set to su in a global ansible project and the su required a password.

Do you have a test case?
In this action we have become: false, ansible_become is supposed to be equivalent.


Is there any problem with collecting the intrinsic and extrinsic parameters of the camera like this?

Habitat-Sim version
vx.x.x
Habitat is under active development, and we advise users to restrict themselves to stable releases. Are you using the latest release version of Habitat-Sim? Your question may already be addressed in the latest version. We may also not be able to help with problems in earlier versions because they sometimes lack the more verbose logging needed for debugging.
Main branch contains 'bleeding edge' code and should be used at your own risk.
Docs and Tutorials
Did you read the docs? https://aihabitat.org/docs/habitat-sim/
Did you check out the tutorials? https://aihabitat.org/tutorial/2020/
Perhaps your question is answered there. If not, carry on!
❓ Questions and Help
hfov=90
Intrinsic = np.array([
[1/np.tan(math.pi/4), 0., 0., 0.],
[0., 1/np.tan(math.pi/4), 0., 0.],
[0., 0.,  1, 0],
[0., 0., 0, 1]])
Extrinsics=np.array([sim.get_agent(0).get_state().rotation.w,sim.get_agent(0).get_state().rotation.x,sim.get_agent(0).get_state().rotation.y,sim.get_agent(0).get_state().rotation.z])
Extrinsics=quaternion_to_rotation_matrix(Extrinsics)
Extrinsics[0][3]=sim.get_agent(0).get_state().position[0]
Extrinsics[1][3]=sim.get_agent(0).get_state().position[1]
Extrinsics[2][3]=sim.get_agent(0).get_state().position[2]
print(Extrinsics)
if the width = 512, height = 512
fx =512, fy = 512
cx = 512 / 2 = 256 and cy = 512 / 2 = 256
But the output Intrinsic parameters and extrinsic parameters couldn't match the picture when I warped the picture.
And i used Replica Dataset.I want to use this data to do some novel viewpoint synthesis tasks.
I think I need some help, such as how to render the Replica image while outputting its camera intrinsic and extrinsic parameters.I would be grateful if someone could provide some help.

Hey @oskar0812,
First thing I notice is that you are querying the state of the agent rather than the camera here:
sim.get_agent(0).get_state() will return the agent's state. The camera, however is offset from the agent by some configured transformation. Instead, try something like
agent_rotation = sim.get_agent(0)._sensors["color_sensor"].node.absolute_transformation(). The key is to get the camera's scene_node instead of the agent's.


HBASE-28928 Handle NPE in Split/Merge table when getMasterQuotaManager returns null

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 29s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 49s

master passed

+1 :green_heart:
compile
3m 13s

master passed

+1 :green_heart:
checkstyle
0m 45s

master passed

-1 :x:
spotbugs
1m 57s
/branch-spotbugs-hbase-server-warnings.html
hbase-server in master has 1 extant spotbugs warnings.

+1 :green_heart:
spotless
0m 53s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 28s

the patch passed

+1 :green_heart:
compile
3m 32s

the patch passed

+1 :green_heart:
javac
3m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 40s

the patch passed

+1 :green_heart:
spotbugs
1m 58s

the patch passed

+1 :green_heart:
hadoopcheck
10m 46s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 42s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s

The patch does not generate ASF License warnings.

39m  9s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6375/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6375

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 88fb3747b398 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 726b2d8e2f2ba70bedd277bb9f2cc9e2b1749eb9

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
84 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6375/1/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

Spotbugs failure is unrelated.

+1, LGTM

@NihalJain if everything is good. can you please help me in getting this committed upto branch-2.5.


Use JTravis V2

This PR will be stuck for some time: we cannot get right now the language from Travis API V3. I'll work on it later.


Fix RR4 hash links

Fixes #2180

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @odero!

  Generated by :no_entry_sign: dangerJS

Hey @odero, would you be up for taking another look at this?

Feel free to reopen this when you have some time to take a look!


Farcasterd syncer types1

Codecov Report

Merging #588 (412bafb) into main (9b8ce02) will decrease coverage by 0.0%.
The diff coverage is 0.0%.

@@           Coverage Diff           @@
##            main    #588     +/-   ##
=======================================
- Coverage    9.2%    9.2%   -0.0%
=======================================
  Files         34      34
  Lines      10738   10780     +42
=======================================
  Hits         991     991
- Misses      9747    9789     +42

Impacted Files
Coverage Δ

src/farcasterd/runtime.rs
0.0% <0.0%> (ø)

Continue to review full report at Codecov.

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

to be merged after https://github.com/farcaster-project/farcaster-node/pull/583

I found this PR much easier to review by itself seeing that there was no dead code and I could actually understand what the intention behind certain designs is. There is just one small change I suggested, then I think this can be merged.


New spring element in SubDyn: 6 by 6 stiffness matrix

I believe this pull request is ready to be merged.
Feature or improvement description
One new spring element has been included in SubDyn.
The spring is a new member type. Accordingly, SubDyn now supports as members: beams, cables, rigid elements and springs.
Previously, SubDyn could only include a stiffness matrix as a boundary condition.
The spring element has the next properties:

It provides a 6 by 6 stiffness matrix (including diagonal and cross-coupling terms). The stiffness matrix is assumed to be symmetric (Kij = Kji).

It doesn't have a mass/inertia associated. If interested, the user may include a lumped mass at a given JointID.
The spring element must be defined between nodes (i.e., JointIDs) that are coincident. The code checks if this condition is true and aborts the program if the condition is not met.
Since the spring element is defined between two coincident nodes, the user must provide the spring orientation by means of the direction cosine.
When defining a spring element, the user must provide 22 inputs (the PropSetID and 21 coefficients to define the upper half of the stiffness matrix).
The spring is not subdivided by means of NDiv.
The sensors definition for the spring element (e.g., force, moment, displacement, rotation...) are the same as for the beams.
The spring can be connected to beams, kinematic joints (e.g., revolute joint, universal joint, and spherical joint), the interface joint and rigid links. Avoid connecting one spring directly to one cable.

The new SubDyn input file includes a new section for the spring element. See below for reference:

Internally, the spring element relates 2 nodes with 6 DOFs each. Accordingly, mathematically the spring element has a 12 by 12 dimension.

Impacted areas of the software
Only SubDyn is impacted. Since this is a new element, the verification tests should pass as the legacy elements in the code have not been modified.
Additional supporting information
Having the capability to include a stiffness matrix is very helpful for modelers. This stiffness matrix can be used for example to model:

Elastic couplings.
Bearings. Some OpenFAST users include part of the wind turbine drivetrain in SubDyn. The loads could be transferred to the supporting structure through one or more spring elements. Tapered roller bearings could also be represented taking advantage of the cross-coupling terms.
Sensors with compliance for models at scale.
The spring element could also be used to approximate revolute joints, universal joints or spherical joint. For example, one revolute joint could be considered by defining the diagonal coefficients as stiff (e.g., 1E12, don't provide very high values or the system will be ill-conditioned), except the direction with the DOF of interest (e.g., K44). It's important to remember at this point that SubDyn assumes that structural motions within the body are small.
Many more!

Test results, if applicable
Several test cases have been reviewed for the new spring element in SubDyn. Below some representative test cases are included. Results compare the output from SubDyn vs reference results (computed analytically or by means of different codes like HOTINT, SAMCEF and OpenModelica).

Test Case 1: Spring and lumped mass.
One spring with a vertical stiffness of 3947.8 N/m and a lumped mass of 100 kg is considered. For the spring, one side is connected to the interface joint and the other side is attached to the lumped mass. The gravity acceleration is 9.81 m/s^2. For this condition, the system should oscillate around -0.2485 m (-9.81*100/3947.8) with a frequency of 1 Hz.

Test Case 2: Same spring and lumped mass as test case 1, but 5% damping considered.

Test Case 3: Comparison between SubDyn revolute joint and spring element.
One pendulum-type system is evaluated. See schematic representation below for reference. One revolute joint or a spring element is defined at point B. The rotational stiffness is 1E6 Nm/rad. The AB beam is 1 m long and the BC beam is 4 m long. Both beams have the same sectional properties (2 m diameter for a full circle beam) and material properties (Young Modulus = 210E9 N/m^2, Poisson ratio = 0.3 and density = 7860 kg/m^3).
The SubDyn interface joint is located at point A. Accoding to SubDyn’s methodology, it’s a floating case (there are no reaction joints). The Guyan modes correspond to rigid body modes and the gravitational loads are applied to the Guyan modes. This means that the system will only experience the elastic restoring from the revolute joint or the spring element, but not the gravitational restoring.

One force to reproduce a free-decay is applied at point C. This nonlinear force is as follows:
#Time_[s] , Fx_[N]  , Fy_[N] , Fz_[N] , Mx_[Nm] , My_[Nm] , Mz_[Nm]
0.0       ,  0.0    , 0.0    , 0.0    , 0.0     , 0.0     , 0.0
25        ,  2.5E4  , 0.0    , 0.0    , 0.0     , 0.0     , 0.0
50        ,  2.5E4  , 0.0    , 0.0    , 0.0     , 0.0     , 0.0
50.01     ,  0.0    , 0.0    , 0.0    , 0.0     , 0.0     , 0.0
100.0     ,  0.0    , 0.0    , 0.0    , 0.0     , 0.0     , 0.0
The angle rotated at the point B is computed by looking at the displacement of point C with regarding to point B.

The changes to the SubDyn input files should be updated in the r-test repository.
And also documented here:
https://openfast.readthedocs.io/en/dev/source/user/api_change.html
And likely some small documentation changes are needed.

I have updated the documentation for this new spring element. I guess the current r-test will run just modifying the SubDyn input file accordingly. This is, adding below the RIGID LINK PROPERTIES section, the new entries:
----------------------- SPRING ELEMENT PROPERTIES -------------------------------------
             0   NSpringPropSets - Number of spring properties
PropSetID   k11     k12     k13     k14     k15     k16     k22     k23     k24     k25     k26     k33     k34     k35     k36     k44      k45      k46      k55      k56      k66
  (-)      (N/m)   (N/m)   (N/m)  (N/rad) (N/rad) (N/rad)  (N/m)   (N/m)  (N/rad) (N/rad) (N/rad)  (N/m)  (N/rad) (N/rad) (N/rad) (Nm/rad) (Nm/rad) (Nm/rad) (Nm/rad) (Nm/rad) (Nm/rad)

See PR https://github.com/RBergua/openfast/pull/2 for updates (brings this PR up to dev -- only necessary to get r-test to the right point).

Will the spring elements be included in the next release of OpenFAST? And when is that coming?

The spring elements for SubDyn have been merged into OpenFAST dev branch and will be available in OpenFAST v.4.0.0. Such OpenFAST version should be released relatively soon.


Import error in routers.py

I just came across this awesome plugin and wanted to give it a try in my new v3.2-beta2 installation but ran into an error right of the gate
ImportError: cannot import name 'NetBoxRouter' from 'netbox.api.routers' (/opt/netbox/netbox/netbox/api/routers.py)

Traceback (most recent call last):
  File "/opt/netbox/netbox/./manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 425, in execute_from_command_line
    utility.execute()
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 419, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 373, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 412, in execute
    self.check()
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 438, in check
    all_issues = checks.run_checks(
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/checks/registry.py", line 77, in run_checks
    new_errors = check(app_configs=app_configs, databases=databases)
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/checks/urls.py", line 13, in check_url_config
    return check_resolver(resolver)
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/checks/urls.py", line 23, in check_resolver
    return check_method()
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/urls/resolvers.py", line 448, in check
    for pattern in self.url_patterns:
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/utils/functional.py", line 48, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/urls/resolvers.py", line 634, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/utils/functional.py", line 48, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/opt/netbox/venv/lib/python3.9/site-packages/django/urls/resolvers.py", line 627, in urlconf_module
    return import_module(self.urlconf_name)
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 855, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/opt/netbox/netbox/netbox/urls.py", line 9, in <module>
    from extras.plugins.urls import plugin_admin_patterns, plugin_patterns, plugin_api_patterns
  File "/opt/netbox/netbox/extras/plugins/urls.py", line 35, in <module>
    urlpatterns = import_object(f"{plugin_path}.api.urls.urlpatterns")
  File "/opt/netbox/netbox/extras/plugins/utils.py", line 31, in import_object
    spec.loader.exec_module(module)
  File "/opt/netbox/venv/lib/python3.9/site-packages/netbox_documents/api/urls.py", line 1, in <module>
    from netbox.api.routers import NetBoxRouter
ImportError: cannot import name 'NetBoxRouter' from 'netbox.api.routers' (/opt/netbox/netbox/netbox/api/routers.py)

This is working from the feature branch using 0.2.1 tag


ga4 internal dashboard demo blog post

@TyDunn   I've made some small content updates. Please have a look.


[🚀+🐛] The github workflows probably don't work right now

🐛 Bug Report
Don't want to deal with the hassle of maintaining the github workflows.
Will disable them for now, but hope to revisit them in the future.

Some issues that I need to resolve

Release Drafter needs to be a different branch

Update the template github workflows


Add missing ENVs to native or GitHub .env.examples

Missing required ENVs in the native example in particular.

@nerdalert some of these environment variables like "NEXT_PUBLIC_LOCAL_TAXONOMY_ROOT_DIR" are intentionally not exposed for users, because they are mainly for UI devs to tweak for their dev environment to over ride the default.


Botocore not catching internal exceptions / providing generic AWS API error exception

Botocore is not catching exceptions when the AWS API acts up and has issues.  We are having an issue with that right now, reported on the AWS status page, and are getting the following:
    user.LoginProfile().update(Password=generate_password(), PasswordResetRequired=True)
  File "/usr/local/lib/python3.5/site-packages/boto3/resources/factory.py", line 498, in do_action
    response = action(self, *args, **kwargs)
  File "/usr/local/lib/python3.5/site-packages/boto3/resources/action.py", line 83, in __call__
    response = getattr(parent.meta.client, operation_name)(**params)
  File "/usr/local/lib/python3.5/site-packages/botocore/client.py", line 228, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/usr/local/lib/python3.5/site-packages/botocore/client.py", line 481, in _make_api_call
    operation_model, request_dict)
  File "/usr/local/lib/python3.5/site-packages/botocore/endpoint.py", line 117, in make_request
    return self._send_request(request_dict, operation_model)
  File "/usr/local/lib/python3.5/site-packages/botocore/endpoint.py", line 144, in _send_request
    request, operation_model, attempts)
  File "/usr/local/lib/python3.5/site-packages/botocore/endpoint.py", line 203, in _get_response
    parser.parse(response_dict, operation_model.output_shape)),
  File "/usr/local/lib/python3.5/site-packages/botocore/parsers.py", line 209, in parse
    parsed = self._do_error_parse(response, shape)
  File "/usr/local/lib/python3.5/site-packages/botocore/parsers.py", line 433, in _do_error_parse
    root = self._parse_xml_string_to_dom(xml_contents)
  File "/usr/local/lib/python3.5/site-packages/botocore/parsers.py", line 385, in _parse_xml_string_to_dom
    "invalid XML received:\n%s" % (e, xml_string))
botocore.parsers.ResponseParserError: Unable to parse response (no element found: line 1, column 0), invalid XML received:
b''

The first line is our code, which just updates a user login profile with a random password.  Looks like AWS is (currently due to errors), not returning something that botocore can parse.  It should catch this exception and return a proper botocore.exceptions exception.  I just looked through them, and there does not appear to be a "AWSAPIError" or something that indicates a problem on the backend AWS API.  Probably need to create one for these situations, as we (end-users) can't be expected to catch every exception that might be thrown when using the botocore/boto3 services.  If you have a problem parsing a bad response from AWS, we should not get an error / exception such as botocore.parsers.ResponseParserError...

I agree, we should not be propogating a botocore.parsers.ResponseParserError in the case of an empty body like you're seeing.  We'll get this updated.

Fixed via https://github.com/boto/botocore/pull/859

I'm receiving botocore.parsers.ResponseParserError, using boto3 1.4.2 and botocore 1.4.87.  Error occurs when calling send_email on ses client.  The email is delivered as expected, but the error is returned from the call and causes an except block to execute.


Add "nowrshmsk" attribute, fix shift-and-mask bit slice write for signed offset

Fixes some of #1990.
Remaining issues:

Disable shift-and-mask when the code describes latches
[x+:N] doesn't work properly for signed x with vectors with negative indices

Signed indices and vectors that have negative start offsets should work fine now. I've also added some test cases for that.


lzma native prebuilds not accessible

Seems like the prebuilds aren't able to be fetched, and building locally is erroring out on our build machine, any thoughts?
https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v6.0.1-n-api-darwin-x64.tar.gz the respective link it is trying to fetch the prebuilt from

Likewise, I think we are seeing a similar issue that started overnight sometime between 12/28/21@ 3pm PST (last successful pull) and 12/29/21 @ 9am PST.
node-pre-gyp WARN Pre-built binaries not installable for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>node-pre-gyp WARN Hit error connect ECONNREFUSED <IP_ADDRESS>:443

I was using electron-rebuild and updated the module, if you directly depend on lzma-native just update the module, if it's a dependency of another module you're using try to update that as well; worked great for me.

That's actually the same module we are experiencing this problem with (electron-rebuild), but updating that forced us to update node to 12.x, which has trickle-led to other problems.  The hope was in the meantime to resolve this issue for now to punt on all these downstream changes.  That said, glad you're at least back up and running @jjason685 !


--handle-input not working with Expo?

Description: I'm trying to run expo start along with another command, I'm using --handle-input but nothing happens when I press r (reload) or i (open on iOS)
Expected Behavior: I would expect the commands to be forwarded to the Expo CLI
Environment: macOS, Node lts/jod
Reproduction: concurrently -k -n 'mobile-client,backend' -c 'red,green' --handle-input 'yarn expo start' 'yarn workspace backend run dev'

Sounds like it's detecting whether it's in TTY mode. I don't know how this is used, but the function name is pretty suggestive:
https://github.com/expo/expo/blob/988261c1a1405aca1f0a32f28bf068306aa03a8c/packages/%40expo/cli/src/utils/interactive.ts#L4-L5
If you pass the --raw flag to concurrently, expo might respond - but at the cost of not having output prefixed.
It'd be cool to have some env variable to force interactivity.

Thanks. Do you think the raw option could be enabled just for a specific command rather than for all of them? So that I can have the output prefixed for all the other commands I run?

Yep, this should already be possible today though through API mode.
concurrently([
	{ name: '...', command: 'foo', raw: true },
	{ name: '...', command: 'bar' } // raw: false by default
])

Docs (it's lacking raw in there, but it works)
That said, I wouldn't say no to making the CLI --raw flag accept indices/names as a way to pick which commands use it.

so would it be --raw 0 and/or --raw label-a right? Could it support multiple raws at the same time? (--raw 0 --raw 1)?

Yes, but I'd favour using comma separators like in most other flags that accept multiple inputs (e.g. --prefix-colors, --names or --success), so --raw foo,bar,1,2,3


Question:  Regard Realtime Updates

I have successfully implemented Pusher in my chat, instead of using javascript poll to retrieve updates from server.  Its working correctly as updates are realtime.  Now, my the next feature I want to add is to make the chat items on the left of the screenshot have a background of blue whenever there is an update for them.  My question is, how are the updates for these implemented?  should each of them have their own listener?

Use The event variable inside the model, like so:
/**
 * The event map for the model.
 *
 * @var array
 */
protected $dispatchesEvents = [
	'created' => \App\Events\Messages\MessageCreatedEvent::class,
];

Then you can create the eventfile which can push your event to where ever (preferably sockets)
<?php

namespace App\Events\Messages;

use Illuminate\Broadcasting\Channel;
use Illuminate\Queue\SerializesModels;
use Illuminate\Broadcasting\PrivateChannel;
use Illuminate\Broadcasting\PresenceChannel;
use Illuminate\Foundation\Events\Dispatchable;
use Illuminate\Broadcasting\InteractsWithSockets;
use Illuminate\Contracts\Broadcasting\ShouldBroadcast;

class MessageCreatedEvent implements ShouldBroadcast
{
    use Dispatchable, InteractsWithSockets, SerializesModels;

    public $message;

    /**
     * Create a new event instance.
     *
     * @return void
     */
    public function __construct(Messages $message)
    {
        $this->message = $message;
    }

    /**
     * Get the channels the event should broadcast on.
     *
     * @return \Illuminate\Broadcasting\Channel|array
     */
    public function broadcastOn()
    {
        return ['message-system'];
    }
}

Then client side you can listen to the even something like this to change the color of a new message
socket.on('message/event', function(event){
    // access your sidebar message
    $('#message-' +event.message.id).addClass('alert alert-info');
})

You need to add a identifier to that row with an id like message-123

hi @filtration,
thanks for the assist.  i have managed to implement realtime update notification based partially on your guide.  what i am not sure though is if I am doing it correctly.
basically, when some dude sends a message, all "participants" on that thread (likely only 2), will be "notified":
	foreach($thread->participants as $p) {
		if ($p->user->id != Auth::id()) {
		  $tv = view('messenger.partials.thread1', ['thread' => $thread])->render();
		  event(new MessageAddedOrUpdated($msg, $p->user, $p->user->newThreadsCount(), $tv));
		}
	}
params of MessageAddedOrUpdated are as follows:
$msg = message data sent
$p->user = the participant
$p->user->newThreadsCount() = new thread count of participant.  to update new thread count on the lower right of the screen (not seen on the screenshot)
$tv = the thread rendered view.  to update the thread info on the left of the screenshot.

You can broadcast it privately with the message ID and then listen to that specific Id if they are authorized... More information can be found here: https://laravel.com/docs/5.5/broadcasting#authorizing-channels


bug: E5108: Error executing lua ...e\pack\packer\start\flash.nvim/lua/flash/search/init.lua:58: ...ta\site\pack\packer\start\flash.nvim/lua/flash/ acks.lua:28: cannot resolve symbol 'search_match_lines': Ҳĳ

Did you check docs and existing issues?

[X] I have read all the flash.nvim docs
[X] I have searched the existing issues of flash.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.8.3
Operating system/version
windows
Describe the bug
E5108: Error executing lua ...e\pack\packer\start\flash.nvim/lua/flash/search/init.lua:58: ...ta\ ite\pack\packer\start\flash.nvim/lua/flash/hacks.lua:28: cannot resolve symbol 'search_match_lines': Ҳĳ                                                                                stack traceback:                                                                                [C]: in function 'error'                                                                          ...e\pack\packer\start\flash.nvim/lua/flash/search/init.lua:58: in function '_call'               ...e\pack\packer\start\flash.nvim/lua/flash/search/init.lua:74: in function 'get'                 ...ta\site\pack\packer\start\flash.nvim/lua/flash/cache.lua:87: in function 'get_state'           ...ta\site\pack\packer\start\flash.nvim/lua/flash/state.lua:283: in function '_update'            ...ta\site\pack\packer\start\flash.nvim/lua/flash/state.lua:248: in function 'update'             ...ta\site\pack\packer\start\flash.nvim/lua/flash/state.lua:380: in function 'step'               ...ta\site\pack\packer\start\flash.nvim/lua/flash/state.lua:413: in function 'loop'               ...site\pack\packer\start\flash.nvim/lua/flash/commands.lua:9: in function 'jump'
Steps To Reproduce
just use keymap with flash
Expected Behavior
If you are experiencing this issue when running the lua require("flash").jump() command in Neovim and it turns the whole buffer into an empty color, and then attempting to jump results in the error message.it seems like there is a problem with the Flash.nvim plugin. but the command lua require("flash").treesitter() is working fine  and
Repro
No response

Works fine for me. Make sure you have a proper Neovim version installed with LuaJit

I updated to nvim 0.9 and it's resolved ,thanks!!!


Allow the draw function to be called programmatically

This PR allows a user of eventdrops to call the draw() function programmatically, the way the zoom handler does.  We wish to alter the zoom behavior slightly and need a hook to call draw() from the requestAnimationFrame() in a similar way.

Looks good. Can you rebase with your last PR to remove changes for JSPM?
Moreover, it miss a test to ensure we won't remove the draw method in the future. And, can you also update the docs? :)

@jpetitcolas I just started looking at adding the test which would, as you say, help to keep the draw function from being removed.  I noticed recent commits have removed the .zoom() function, which we also depend on.  This was probably removed by mistake, ironically, because it is still documented in the README.

Updated my branch to latest master, and resubmitted changes to add the hook for draw() and added back the hook for zoom().  I also added a test for these.

It would need a last rebase. Yet, just wait a few ready PR to be merged, to ensure you won't have to rebase again. Will be embedded in the 0.3 version.
Sorry for the delay. :)

No problem on the rebase, but how should I proceed?  Should I recreate a
new branch?  I think if I rebase and push --force the pull request will
auto close anyway.  Please advise.
On Mon, May 29, 2017 at 12:48 PM, Jonathan Petitcolas <
<EMAIL_ADDRESS>wrote:

It would need a last rebase. Yet, just wait a few ready PR to be merged,
to ensure you won't have to rebase again. Will be embedded in the 0.3
version.
Sorry for the delay. :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marmelab/EventDrops/pull/119#issuecomment-304699541,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAq8lxTS_w6xUishE2OwqHaEYIdmZs4Hks5r-vbKgaJpZM4L6_2-
.

@kwesterfeld: yes, just rebase and push force, it should not close the PR if it still contains some changes. :)

@jpetitcolas I did a rebase and push force on this branch.  Can you review and include please?
Thanks

No news for too long, closing


Database Access Issue for Users in shared Network environments

Some users have reported issues accessing certain databases on the Relax page when many users are connected to the page from the same network (like eduroam). Users within this network can only access the test database, while attempts to connect to other databases fail.
Cause:

Database connections on Relax rely on data served via GitHub Gists.
GitHub enforces rate limiting when there are numerous requests from the same IP address, which is often the case within shared networks like the university's.
Due to this restriction, GitHub blocks additional requests from the same IP, limiting access to the databases.

Solution/Workaround:

Log into GitHub: Users can log into their GitHub account while using Relax. This may prevent rate limiting by associating requests with individual accounts rather than a shared IP.
Access Outside the University Network: Users may also avoid this issue by accessing Relax from a non-university network.

Perhaps, this information could be added as a note to the part of the documentation about gist files.


Tab Manager: Origin pixels

Task/Issue URL: https://app.asana.com/0/1174433894299346/1208763092216879/f
Description
This PR adds an origin to the pixels sent when the tab manage is open
Steps to test this PR
From SERP

[x] Open and and make any search
[x] Open Tab Manager
[x] Verify m_tab_manager_open_from_serp is fired

From any site

[x] Open and and visit any site
[x] Open Tab Manager
[x] Verify m_tab_manager_open_from_website is fired

From new tab

[x] Open New Tab
[x] Open Tab Manager
[ ] Verify m_tab_manager_open_from_newtabpage is fired

#5396  👈 (View in Graphite)
develop

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

Thanks @0nko !


Chart is broken and unusable

What a nightmare, this chart is absolutely broken and unusable. I had to drop the chart and roll my own deployment.
One's helm chart is a good indicator of quality and commitment. Suggesting people use this for handling secrets and not giving a way to do stuff as basic as pointing to an existing credentials secret is just ridiculous.
Having to install this and depend on it for something as crucial as credentials and secrets is truly worrisome.
 Paying as business, not a proverbial cup of coffee per month kind of paying.

ingress bit is particularly broken - I'll also have to either create a new chart or create some make-shift ingress resources on the side.

Hey @rauanmayemir and @Tipsmark ! 👋
I am sorry to hear that your experience with the Helm charts we provide didn't go as smooth as you've wanted.
Firstly, we wanted to share that when it comes to ingress, the charts work as expected based on #179.
We really appreciate your time and effort that you have already put into trying to use these Helm charts. If you have some additional time to spare, could you provide additional details about your use case in which you want to use the helm chart and the challenges that you're facing? This will help us better understand what's missing in the current version of it and how we can improve it.
What would be useful for you to provide:

Example snippets on how the Helm chart configuration would look like when pointing to existing credentials secrets.
Example snippets on configuring the ingress that do not work with the Helm charts we provide.
Explanation on the use case and the desired goal.
Mention any workarounds if there are any.

Thank you! 😄

Closing this as it hasn't received a reply for a while.
In the meantime, we will look into the existing bugs and issues opened and improve the Helm charts by addressing those. We will update our progress on the specific tickets. Feel free to re-open if needed and provide specific use cases challenges you're facing.


Add dogether

为确保 Token Profile 的顺利通过，务必逐一确保以下检查项并补充项目资料：
.json 及 .png 文件检查项
logo 尺寸：120*120 px
logo 背景：透明
代币有至少一笔成功的转账记录
此项对于 ERC-20 项目方：合约地址有大小写（做 checksum）
.json 和 .png 文件名一致（包括大小写）
项目资料：
项目资料：
DOGETHER—一种可扩展的区块链验证解决方案 比特币社区中最受欢迎的争论是区块链不能正确扩展。它不会扩展，因为每个完整节点都必须验证每个事 务。由于固定的块时间（两个块创建之间的时间），缩放不能很好地工作。如果有越来越多的交易（意味 着系统增长）;那么每个节点都必须在固定的时间内处理更多的事务。以太坊的交易比比特币更复杂。尽 管如此，它还没有达到它的极限，但社区正致力于解决可扩展性问题。 在简单的数据库系统中，可扩展性问题的解决方案是添加服务器，这些服务器可以接管额外的事务，甚至 可以接管系统。另一方面，区块链是一个分布式数据库，添加节点在这里没有帮助，因为每个节点都必须 处理每个事务，所以它不会缓解问题。如果我们决定仅将额外的事务分发给少数节点;然后这些节点可能 在验证期间作弊，因为事务不与其他节点一起记录。此外，这违反了区块链系统（信任） 的基本规则，即每个节点都必须处理每个事务。以太坊的可扩展性问题与比特币相同。以太网对比特币的优势在于以太网团队自从开始以来就意识到这个问题，因此如果需要的话，他们已经准备好用来解决问题。处理以太坊中的可扩展性问题有三个提案。 Casper不仅仅关注POS，还要扩展区块链。在Casper中，扩展是基于一个名为Sharding的概念完 成的，这与处理可伸缩性的分布式数据库系统的概念非常相似。在Sharding中，事务被发送到某些节点 以进行验证，但因为casper更安全。 Raiden是比特币闪电网络的以太坊类比。在Raiden，概念是通过国家渠道扩大交易规模。这意味着通 过以某种方式对事务进行分组，然后转移到另一个网络（离线链接）。最后，将多个类似的交易分组并放 回区块链网络。它只是意味着，更多的交易被包含在一个额外的交易中。 DOGETHER是处理该问题的第三个提案。在DOGETHER中，概念是通过交互式验证来扩展计算。 只有Casper需要fork，因为其他两个可以使用智能合约代码直接实现。
媒体报道：
币世界 https://www.reddit.com/r/DigiFinex/comments/c6ickp/digifinex_lists_dogethereum_and_airdrops/?utm_source=share&utm_medium=web2x
收录的交易所：数字币交易所 新加坡币多网
转账所需 Gas Limit（对 ERC-20 项目方）：60000
Please check the following to ensure a successful verification of Token Profile
.json and .png document checklists
logo dimensions: 120*120 px
logo background: Transparent
At least one transaction on the token contract
For ERC-20 project teams: Upper and lower capitalized alphabets in token address (For checksum purposes)
Same document name for both .json and .png (Including capitalization)
Project background:
Project basic information:DOGETHER, an extensible block chain validation solution, is the most popular argument in the Bitcoin community that block chains do not scale properly. It does not expand because each complete node must verify each transaction. Because of the fixed block time (the time between the creation of two blocks), scaling does not work well. If there are more and more transactions (which means system growth), then each node must handle more transactions within a fixed time. The ETF deal is more complex than Bitcoin. Nevertheless, it has not yet reached its limits, but the community is working on scalability. In a simple database system, the solution to the scalability problem is to add servers that can take over additional transactions or even systems. On the other hand, block chains are distributed databases, and adding nodes is not helpful here, because each node has to deal with every transaction, so it does not alleviate the problem. If we decide to distribute only additional transactions to a few nodes, then these nodes may cheat during validation because transactions are not recorded with other nodes. In addition, this violates the basic rule of block chain system (trust), that every node must handle every transaction. The scalability of ETF is the same as that of Bitcoin. The advantage of Ethernet over bitcoin is that the Ethernet team has been aware of this problem since its inception, so they are ready to solve it if needed. There are three proposals to address scalability in the Ethernet workshop. Casper not only focuses on POS, but also extends block chains. In Casper, extensions are based on a concept called Sharing, which is very similar to the concept of a distributed database system that handles scalability. In Harding, transactions are sent to certain nodes for authentication, but because Casper is safer. Raiden is the Ethernet analogy of the Bitcoin lightning network. In Raiden, the concept is to expand the scale of transactions through national channels. This means grouping transactions in some way and then moving to another network (offline links). Finally, several similar transactions are grouped and put back into the block chain network. It just means that more transactions are included in an additional transaction. DOGETHER is the third proposal to address this issue. In DOGETHER, the concept is to extend computing through interactive validation. Only Casper needs fork, because the other two can be implemented directly using smart contract code.
Mediapublications: https://www.reddit.com/r/DigiFinex/comments/c6ickp/digifinex_lists_dogethereum_and_airdrops/?utm_source=share&utm_medium=web2x
Tradeable exchanges: Digifinex
Recommended Gas Limit (For ERC-20 project teams) for transaction: (Default is 60,000) 60000

https://github.com/consenlabs/token-profile/blob/master/tutorial/erc20-tutorial.zh-CN.md#资料的完整和准确


Perform INSERT..SELECT via coordinator if it cannot be pushed down

Why are we implementing it? (sales eng)
What are the typical use cases?
Communication goals (e.g. detailed howto vs orientation)
Good locations for content in docs structure
How does this work? (devs)
Example sql
Corner cases, gotchas
Are there relevant blog posts or outside documentation about the concept/feature?
Link to relevant commits and regression tests if applicable
https://github.com/citusdata/citus/pull/1402

This issue is another case where we have to use a temp table on the coordinator? https://docs.citusdata.com/en/latest/reference/sql_workarounds.html#temp-tables-the-last-resort
Is it still a thing as of 7.3?