Add support for generic multicolumn tables

Resolves #1980. Prior to this story, we could only render Node Tables and Labels (renamed to Property Lists in this PR) in the node details panel. This PR introduces Generic Table as a separate UI component that enables us to render generic data in a multi-column format without associating rows to nodes.
Modeling
As @davkal reasoned, it makes sense to have Property Lists and Generic Tables as distinct components in the UI, so I made them fully independent there, but for backward compatibility reasons, I kept them under the old Table model on the backend, which I finally decided to extend like this:
// Column is the type for multi-column tables in the UI.
type Column struct {
	ID       string `json:"id"`
	Label    string `json:"label"`
	DataType string `json:"dataType"`
}

// Row is the type that holds the table data for the UI. Entries map from column ID to cell value.
type Row struct {
	ID      string            `json:"id"`
	Entries map[string]string `json:"entries"`
}

// Table is the type for a table in the UI.
type Table struct {
	ID              string   `json:"id"`
	Label           string   `json:"label"`
	Type            string   `json:"type"`
	Columns         []Column `json:"columns"`
	Rows            []Row    `json:"rows"`
	TruncationCount int      `json:"truncationCount,omitempty"`
}

// TableTemplate describes how to render a table for the UI.
type TableTemplate struct {
	ID        string            `json:"id"`
	Label     string            `json:"label"`
	Prefix    string            `json:"prefix"`
	Type      string            `json:"type"`
	Columns   []Column          `json:"columns"`
	FixedRows map[string]string `json:"fixedRows"`
}

where Columns is used only with the multicolumn-table template type and FixedRows in only supported for property-list. The main reason I decided not to support fixed rows for generic (multicolumn) tables is that it wasn't clear what the exact use-case might be and how they would be rendered in the UI.
Storing
To be consistent with how property lists are being stored on the node, I decided to use the node.Latest map with table prefixes to store generic tables as well. The only difference is that since a multi-column table is two-dimensional, the table value is determined not only by label, but by (row, column) pair. Storing whole rows in the Latest map was not an option for two reasons:

Latest is a string to string map so we can only use it to store strings.
I also thought it would be better to use latest info on the cell level instead of row.

To be able to differ between the rows, each of them has to be given an ID (instead of what used to be a label). For backward compatibility with the old reports, property lists label is indeed used as a row ID when sending a table to the UI.
Rendering in the UI
Generic table is sortable and supports different column types (sent through Column.DataType field on the backend). Column headers are the same as for Node Tables (they are now in a new component called NodeDetailsTableHeaders), and column widths can also be hard-coded on the frontend.

To see this, run fixprobe on this report
Other Observations

Right now we iterate once through the whole node.Latest map for every table (or a property list) we are extracting, instead of just running through the entries with a given prefix and extracting the fixed row information separately. I haven't looked into the implementation details of our Map structure, but maybe it wouldn't be that difficult to add an efficient ForEachFromTo kind of method there to run only on selected intervals. That would drop our time complexity of extraction roughly from O(T * N) to O(N + T * log N) (or O(N * log N), if a lot of entries correspond to fixed rows), where T is the number of tables and N is the total size of node.Latest. Not sure if it's a bottleneck or if it's worth digging into this, but I just wanted to point it out.
There might other components in node-details dir in the UI, like NodeDetailsInfo, which are both semantically and implementation-wise similar to NodeDetailsPropertyList, so consider refactoring them in some future PR.

@fbarl Really clean design and code.
Did you test with an old probe, to check there are no backward compatibility issues?

To be consistent with how property lists are being stored on the node, I decided to use the node.Latest map with table prefixes to store generic tables as well

I've always thought that using the Latest map to store the metadata of tables was a bit of a hack (particularly for data only used in tables). However now that we are married (for backwards compatibility) I guess we can't cleanly store the metadata anywhere else.

Does this PR happen to address #1735 too?

@rade Not really. All the column widths are still hardcoded on the frontend, I just moved that code to a different file :)

@fons,

Did you test with an old probe, to verify there are no backwards compatibility issues?

I tested it on a manually modified report that I linked to above, in my PR description. Out of the three nodes visible in Weave Net, one of them has everything stored in the new format, one of them in the old, and one of them both (even though that case will never happen I think). I didn't know how to test this data dynamically (without loading it from static reports), so maybe we should do that additional check somehow before pushing. What do you think?

However, now that we are married (for backwards compatibility) I guess we can't cleanly store the metadata anywhere else.

While I was working on this story, I was gradually finding out how big of a constraint backwards compatibility is. Do you have any ideas how we could come around this in the future?

so maybe we should do that additional check somehow before pushing. What do you think?

Your test sounds reasonable, but I would also run a standalone probe with an older version (e.g. Scope 1.1.0) to make sure everything renders as it should.

Do you have any ideas how we could come around this in the future?

Not really (without content negotiation or versioned APIs)

Code looks good, waiting on further backwards compatibility testing to approve.

@fbarl Would you mind (at least) squashing the commits?

Code looks good, waiting on further backwards compatibility testing to approve.

I tested it with a standalone Scope 1.1.0 as you suggested @fons and good that I did because a small change on the backend still needed to be made for backwards compatibility with old probes to work properly. I also tested it with the new probe and with mixed reports after that, but I found no problems there. So as far as I could tell, everything should be working fine after merging this PR!

Great job @fbarl . LGTM!


Add Clean

Motivation
type Clean<T> = Pick<T, keyof T>
type A = { a: string } & { b: number } & { c: boolean }
/*
type A = {
    a: string;
} & {
    b: number;
} & {
    c: boolean;
}
*/
type B = Clean<A>
/*
type B = {
    a: string;
    b: number;
    c: boolean;
}
*/

Out of curiosity why did you end up implementing w/o Pick?

oops, just cut and paste from the wrong file I guess :(

Ah, I was just curious if there was some difference in practice.

@aaronjensen: at the time I experienced issues with a few types with it, but I may need to test more on that, never figured out what they were about. As a result I myself went back from ahejlsberg's 2.5 version to the older approach.
But yeah, I'd done some Simplify type that's exactly your Clean, haha. Don't usually use & over Overwrite, but it works when you know keys won't overlap I guess.


Is there a way to sort coverage result list?

Currently, xcov lists all .m files with the right coverage, but they don't seem to be sorted in any meaningful way. Is there a way to alter the sorting?

Hi @mixtly87 👋
Thanks for reporting! This must be a bug as the report was sorted by coverage in previous versions of the tool. I will take a look 👍


ActionBar not hidden on request

Hi, i'm not sure if it's a bug or a bad usage from me, but i'm trying to hide the action bar from code :
if ( Build.VERSION.SDK_INT < Build.VERSION_CODES.HONEYCOMB )
{
getSupportActionBar().setDisplayShowTitleEnabled(false);
getSupportActionBar().setDisplayShowCustomEnabled(false);
getSupportActionBar().setDisplayHomeAsUpEnabled(false);
getSupportActionBar().setDisplayUseLogoEnabled(false);
getSupportActionBar().setDisplayShowHomeEnabled(false);
}

On my Samsung Galaxy note (android 2.3.6, 1280*720 screen res), the actionbar view is gone, which is what i except.

On my LG Optimus 2x (android 2.3.7, 800*480 screen res), while all the bar components are hidden, the actionbar view is still shown as you can see on this screenshot :  http://imageshack.us/photo/my-images/9/actionsherlockbug.png/  so it take some place on the whole view while it should be gone.

Have you tried getSupportActionBar().hide() ?

Yes, if i do that, the tabs (ActionBar.Tab: Downloads,Filer,Logs on the screenshot) are hidden too.

This is a feature of the Ice Cream Sandwich action bar and thus will work in ABS 4.0. It is not possible in v3.x.


Permission denied while trying to connect to Docker Daemon socket during ./setup.sh

SYSTEM Details:
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
REVISION=4.15.0-106-generic
Docker version:docker-ce_19.03.9~3-0~ubuntu-xenial_amd64.deb
ISSUE Details:
$ ./setup.sh
.
.
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/create: dial unix /var/run/docker.sock: connect: permission denied.

Was able to resolve this after executing the startup script with sudo privileges.


[Minor][ML]Minor correction in the powerIterationSuite

What changes were proposed in this pull request?
Currently the power iteration clustering test in  spark ml, maps the results to the labels 0 and 1 for assertion. Since the clustering outputs need not be the same as the mapped labels, it may cause failure in the test case. Even if it correctly maps, theoretically we cannot guarantee which set belongs to which cluster label. KMeans can assign label 0 to either of the set.
PowerIterationClusteringSuite in the MLLib checks the clustering results without mapping to the particular cluster label, as shown below.
 val predictions = Array.fill(2)(mutable.Set.empty[Long])     model.assignments.collect().foreach { a =>       predictions(a.cluster) += a.id     }     assert(predictions.toSet == Set((0 until n1).toSet, (n1 until n).toSet))
How was this patch tested?
Existing tests

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #4207 has started for PR 21689 at commit b02cae5.

Hi, @srowen . I have modified the code based on your suggestions.

Merged to master

Thank you @srowen for merging.


Make keys editable

It does not appear possible to edit registry key values.

Select a key and then press rename. It might be nice to have direct editing like we do for the values, but that can't work with directories (they are links so clicking on them navigates).

It works for directories just click where the value would be in the table to select it

I'm not talking about renaming keys; I want to set the value of a key and this does not work. If I click on a key's row then the row turns grey and that's it.

When I click on a row for the key f10 the console window shows
selectType key selDir null selKey f10

but nothing happens.

Click on the value of the key and it should be editable. Just start typing. Press "shift+enter" to submit and you should change your key.
It should be clear that the key is editable, the field will have focus and your cursor will apear in the value field

When I click on the key value the row turns grey and nothing else happens. Typing on the keyboard does nothing. There's no cursor.

So in my browser, before clicking anything it looks like this:

When I click on a value (in this case clicking on the string "five2r" it looks like this:

Is that now how it works for you?

@joshmutus Great! Mine does not do that.

:/  Are you using Chrome?

Did you try refreshing the page?
Are there any weird compile errors in gulp or sbt?

@joshmutus

I'm using Chrome.

I checked out the repo this afternoon and am on revision ab30f1709a06deed69fb0642514860a9f7b531e0.

I am coordinated enough to click on the target area. I have clicked on everything imaginable and nothing gives me the opportunity to edit the item.

There are no errors in the console window.

Would you mind restarting Chrome?

@joshmutus restarted Chrome. Nothing.

If you restart the scala server does it error out again? To restart, type ctrl + D and then server/run

@joshmutus What do you mean "error out"?

The scala server shouldn't have that error, if you restart it, does it have that error?
Even still an error on the scala server shouldn't change how the client is rendering. This is troubling.

I restarted the scala server. I was able to browse to the registry etc. but still cannot edit key values. However, if I Ctrl+R the page I see the error reported above.

That error is unrelated; it happens when the connection from the backend scala server to labrad is closed because you refreshed the page. We might be able to clean up the concurrency there, but it's nothing to do with the problem you're having not being able to edit the keys.

What's in your client-js/bower_components?

Could this be because of the wrong node version?

I was able to reproduce the issue with a new checkout and fresh npm/bower/jspm install. The problem seems to be that when clicking on the value, the edit field gets shown, but then immediately thereafter a focus-changed event is fired which hides it again. I haven't tracked down which package was updated that caused this change in behavior, but presumably it's again due to the fact that we haven't pinned all the versions, so new checkout are resolving a newer version of some library (see also #63).
I have a fix coming for this specific problem with the edit fields, but it seems like we need to figure out the version pinning for all the packages so that we can make sure everyone who wants to develop of build is seeing a consistent set of packages.

Here are the bower packages that are different between what I had previously, which worked, and what I get after a fresh bower install, which does not work:
package=hydrolysis, old version=1.15.4, new version=1.17.0
package=iron-menu-behavior, old version=1.0.3, new version=1.0.4
package=iron-overlay-behavior, old version=1.0.6, new version=1.0.7
package=paper-behaviors, old version=1.0.3, new version=1.0.4
package=paper-item, old version=1.0.2, new version=1.0.3
package=paper-progress, old version=1.0.5, new version=1.0.6
package=paper-tabs, old version=1.0.2, new version=1.0.3

Downgraded typescript and can now edit keys.

Fixed by #66


fix: Some RegExpRouter bugs

I am adding a few tests now. Please wait a moment 🙇

@yusukebe
Add some tests at 61b4b4a.
Please review.
I will add more later.

Oh, sorry, this is the end of the work on this PR.
If it looks good, please merge!

Thank you!
There is nothing more I plan to do before v1.2.0.


How to use Fontawesome icons in posts?

Hi, How to use Fontawesome icons in posts?

Basically you need to include FontAwesome CSS first into the head section. To use those icons in post, you can simply paste its HTML code in your post. You can check more details on FontAwesome site.


How to get the previous version using deb-s3?

deb-s3 generates Packages.gz while doing deb-s3 upload.
Suppose I am using s3 as my custom apt-repository with the package: alpha-pkg
Now, when I do sudo apt-get update, then only the latest version of alpha-pkg comes. All the previous versions are gone. Is there any way to keep the previous versions too?
This way, I can quickly switch back to any previous version of alpha-pkg

Hi, Any updates on this?

You can do this with the --preserve-versions on the deb-s3 upload command. I'd also suggest looking through the help screens with either deb-s3 upload --help for some of the different arguments.
Then the previous versions listed in the manifest will be preserved. To add the old ones back, you will have to re-upload them, but uploading the file itself will be skipped since it already exists.
To install a previous version, you have to specify the version to use with apt-get install alpha-pkg=1.2.3. I don't know if interfaces like aptitude will list all of them or not, I don't generally use them.


Fix unit tests certificates to have correct chains and private keys

In preparation for certificate integrity-checking: invalid certificate
chains and mismatching private keys will no longer be allowed anywhere
in Lemur code.
The test vector certs were generated using the Lemur "cryptography"
authority plugin.

Certificates are now more similar to real-world usage: long serial
numbers, etc.
Private key is included for all certs, so it's easy to re-generate
anything if needed.

Coverage decreased (-0.06%) to 61.902% when pulling f4ec0229f1b5e03922a9a0beb68303ab37d735a8 on intgr:unittests-use-valid-certs into 3f9d66bd51538736485fd2b84e8c23af15c97bc8 on Netflix:master.


V2 - Project Console - When there is no data getProjectEvents should return 200 with empty list

As of now below endpoint returns 400. In Project Console UI this 400 API error is shown when there is no activity log. Since there is no CLA Group there is no activity log for the project. Endpoint should return 200 with empty list when there is no activity log for the project .
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getProjectEvents

Pushed PR: https://github.com/communitybridge/easycla/pull/1928
Pushed to DEV.

Verified that the issue is resolved


fix(material/slide-toggle): use css var for disabled label color

Create a css var to allow teams to override the label text color of a disabled switch

This is an intermediary change just so I can land https://github.com/angular/components/pull/28390. Once these have landed, I will go through the correct channels for emitting & defining this css variable. I've left some todos to reflect that this is a temporary state


service workers don't handle fetch for favicons, So how to blacklist certain build files?

I am using favicon webpack plugin to generate favicons at build, and due to bug in chrome the favicons are always fetched from network.  From what i understand of service workers, the icons will be download and cached at first visit, so if there are not be used I would rather not waste network resources even at first visit caching them.

There is no way to exclude bundles without just overriding the staticFileGlobs configuration value.

plugins: [
  new SWPrecacheWebpackPlugin(
    {
      cacheId: "my-project-name",
      filename: "my-project-service-worker.js",
      staticFileGlobs: [
        // you will need to define which bundles you want to cache here
      ],
    }
  ),
]

staticFileGlobs passes your array of string patterns in to glob.
That aside, I think browsers will behave slightly differently when it comes to requesting favicons. I don't think you can prevent the request from happening but I could be wrong. If they are fetched every visit, you will not save much (if any) bandwidth on trying to cache the asset by preventing it.

I don't think browsers fetch all the icons or favicons even if there in a link tags( I have 10+ link tags) but i wasn't sure if I added these to service worker to cache them all, if they all would be downloaded regardless of if browser needs them or not.


Add Sample persons data

Add Sample persons data with the appropriate tags

Coverage increased (+0.1%) to 92.802% when pulling 319063b0153bceb0ab98f60a981c1dc0994c23bf on lincredibleJC:feature/AddSamplePersonData into cb7df175cf1d229a8d36ea846f46e4140085e1c4 on CS2103AUG2017-T16-B2:master.

Coverage increased (+0.1%) to 92.802% when pulling 319063b0153bceb0ab98f60a981c1dc0994c23bf on lincredibleJC:feature/AddSamplePersonData into cb7df175cf1d229a8d36ea846f46e4140085e1c4 on CS2103AUG2017-T16-B2:master.

Coverage increased (+0.1%) to 92.77% when pulling 98038a288faa70998aaeef5b29c39dc48f2c2a70 on lincredibleJC:feature/AddSamplePersonData into 56180e9c6e4b4433cffbf4772189ea9ce8b4cb6f on CS2103AUG2017-T16-B2:master.


add vue-product-zoomer in Nuxt js

problems integrating the component with nuxt:
import ProductZoomer from 'vue-product-zoomer' import readme from '../components/Reame' export default {   components: { readme, ProductZoomer },
Error:

I need your help please

please check this demo. https://github.com/akulubala/nuxt-product-zoomer-demo


Combine straight edges on navigation

For example, edge 8 (51 feet length) and edge 9 (18 feet length) is straightly connected but it is divided by node 9 (transition node to staircase).
When walking from QoLT Entrance to Gates Cafe, current NavCog announce as follows:

51 feet ..and keep straight..
40 feet
approaching
18 feet ..and turn left..
approaching
turn left

This is annoying.
NavCog should announce as follows:

69 feet ..and turn left..
40 feet
approaching
turn left

The following codes will be affected

initializeWithPathNodes() in NavMachine.m
checkStateStatusUsingLocationManager() in NavState.m


Prometheus exporter: remove namespace and prefix for help message.

Closes https://github.com/census-instrumentation/opencensus-java/issues/1202.
/cc @Sebruck

Codecov Report

Merging #1203 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master   #1203      +/-   ##
===========================================
- Coverage     81.91%   81.9%   -0.01%
  Complexity     1229    1229
===========================================
  Files           192     192
  Lines          5987    5984       -3
  Branches        557     557
===========================================
- Hits           4904    4901       -3
  Misses          935     935
  Partials        148     148

Impacted Files
Coverage Δ
Complexity Δ

...porter/stats/prometheus/PrometheusExportUtils.java
95.6% <100%> (-0.15%)
16 <2> (ø)

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 d61eb47...2cf2e5f. Read the comment docs.

No problem!
Note that the failed CI builds are related to a WIP PR https://github.com/census-instrumentation/opencensus-java/pull/1200. Going to merge this PR now.


Add translation for http request node

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
I added Japanese translation for the http request node. (Retry of #2335)
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 77.543% when pulling 75a5b1354c0fb97c39227850036592e0e13fa799 on kazuhitoyokoi:master-addtranslation4httprequest into 0febcf4f9e57c523415fdca1beef3a9b4449705f on node-red:master.

@knolleary Thank you!


JDBC and JNDI SB Samples

Did we test the JNDI sample as well?

Just started reviewing :) :octocat: Sent from GH.

Just started reviewing :) :octocat: Sent from GH.

Pull request submitted to https://github.com/gamerson/liferay-blade-samples/pull/395. See changes here. :octocat: Sent from GH.


updated tests for ColumnDtypeSetter (also updated name to fit convent…

…ion)
Links to Issue
Updated testing approach for ColumnDtypeSetter (also updated name to fit convention)

Updated changelog here :) https://github.com/lvgig/tubular/pull/219/commits/8092a2418634011bdd3d99583fdb3fc80e5b75b0
(also added an update for a previous PR that I forgot on..)


Overhaul typeclasses

The current way typeclasses are implemented is very bad. Essentially none of the constraints are enforced, and instance resolution doesn't actually work as advertised. Additionally, typeclasses can't have generic type parameters, so a typeclass definition with a method that has a reference parameter like &[T, R] has no way to specify that R is a region parameter. This is bad since we want to be able to use reference types and regions.

Allow type parameters in typeclass method definitions.
Enforce that the type parameter set in an instance is a superset of the type parameter set of the typeclass.
Enforce that the argument to a typeclass must be a type constructor applied to zero or more distinct type variables.
Enforce local uniqueness: you can't have multiple instances of instance T in the same module.
Enforce orphan rules: you can't define an instance of an imported typeclass and an imported type.
Fix instance resolution to work correctly.

Split into separate tasks:

#205
#207
#208
#209


preserve existing 'regressions' options when parsing command line opts

When using 'defaultMainWith', the existing command line parser would discard the existing values for 'Config.regressions' and replace it with only the new "--regress=..." entries it parses. This change preserves the old values as well.

The current behaviour is deliberate, and I'm not thrilled about this change to only allow addition of regressions to a default set – especially as if someone depends on the current behaviour, they'll be surprised.

I don't understand what you mean by this "only allowing additions to the default set".
Anyway, if that's the intended behaviour, fair enough. I think that you should at least document that defaultMainWith ignores this part of the Config structure it is passed --- that is surprising and non-intuitive behaviour, which is the crux of the issue.


failed to build the docker image on windows with a linux container.

Plugin Version or Commit ID
v0.12.0
Unity Version
2021.3.8f1
Your Host OS
Windows11Pro 22000.2057
Target Platform
Android
[Windows Only] Visual Studio C++ and Windows SDK Version
i used docker desktop, so i think no need this.
[Linux Only] GCC/G++ and GLIBC Version
No response
[Android Only] Android Build Tools and NDK Version
No response
[iOS Only] XCode Version
No response
Command Sequences
docker build -t mediapipe_unity:linux . -f docker/linux/x86_64/Dockerfile
Log
=> ERROR [builder  4/10] RUN gpg --homedir /tmp --no-default-keyring --keyring /usr/share/keyrings/mono-official  2.0s

[builder  4/10] RUN gpg --homedir /tmp --no-default-keyring --keyring /usr/share/keyrings/mono-official-archive-keyring.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF &&     echo "deb [signed-by=/usr/share/keyrings/mono-official-archive-keyring.gpg] https://download.mono-project.com/repo/ubuntu stable-focal main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list &&     apt update:
#0 0.538 gpg: keybox '/usr/share/keyrings/mono-official-archive-keyring.gpg' created
#0 1.950 gpg: CRC error; EF0B94 - E39330
#0 1.950 gpg: read_block: read error: Invalid keyring
#0 1.950 gpg: Total number processed: 0

Dockerfile:72
71 |     # Install NuGet
72 | >>> RUN gpg --homedir /tmp --no-default-keyring --keyring /usr/share/keyrings/mono-official-archive-keyring.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF &&
73 | >>>     echo "deb [signed-by=/usr/share/keyrings/mono-official-archive-keyring.gpg] https://download.mono-project.com/repo/ubuntu stable-focal main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list &&
74 | >>>     apt update

75

ERROR: failed to solve: process "/bin/sh -c gpg --homedir /tmp --no-default-keyring --keyring /usr/share/keyrings/mono-official-archive-keyring.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF &&     echo "deb [signed-by=/usr/share/keyrings/mono-official-archive-keyring.gpg] https://download.mono-project.com/repo/ubuntu stable-focal main"

Additional Context
i have no idea about gpg, and it says CRC error there.
could you give me any tip for me?
i use the lastest code tagged v0.12.0.
windows 11
linux container, docker desktop
my command for building image
docker build -t mediapipe_unity:linux . -f docker/linux/x86_64/Dockerfile

it occured when i build an image.
i tried but failed again.
docker build --no-cache -t mediapipe_unity:linux . -f docker/linux/x86_64/Dockerfile

it works on the other machine.

Do you mean it works on the other machines on the same network?


talk: unread status may be getting cached

If you go read chats in groups and then switch to talk you may still see them as unread.

Contributing to #1426, or something else?


Flat symbol list C#

In the latest version, for C# files, all symbols show up as a flat list.

I guess C# reports symbols differently to most other languages. Unfortunately previous approach broke in many more languages so I think the best solution would be to file a bug against the C# symbol provider and have it report symbol ranges containing the entire class/method definition instead of just their names/signatures.

Ok, that makes sense. Any chance of providing an option in the settings to use the old method? I know that would not be ideal, but I miss having this work. :)

I would really like to see the fallback option as well. Is there a plan to implement a fallback for C# through the settings?

No, sorry. The old method really did not work well for any languages.

https://github.com/OmniSharp/omnisharp-vscode/issues/2329

is the code outline in your image is the same with outline
I have the lastest version of VSC but it can't parse my C# files.
Imgur

@longtth I see the same behavior both in the code outline extension and the new built in outline functionality that ships with VS Code. If I am understanding your question correctly.

@mattliewer  : as you can see here Imgur, the VSC 1.24.1 can't outline my Csharp file.


Revert package access change from #23879

Fixes (?) #25538
Fixes https://codeberg.org/forgejo/forgejo/issues/972
Regression #23879
#23879 introduced a change which prevents read access to packages if a user is not a member of an organization.
That PR also contained a change which disallows package access if the team unit is configured with "no access" for packages. I don't think this change makes sense (at the moment). It may be relevant for private orgs. But for public or limited orgs that's useless because an unauthorized user would have more access rights than the team member. This PR restores the old behaviour "If a user has read access for an owner, they can read packages".

CI failure is related.

Fixed in #25734


Needs icon

Currently it's only a blank space in the systray.

Now shows current time left in minutes as the tray icon or "off" if no session is running.


failed to cherry pick PR 4379 from ty-dc, to branch release-v0.8

commits f9feb6b59a69703154bf2b7814b6f741a3c16b25 of ty-dc conflict when merging to branch release-v0.8, please manually cherry pick it by yourself.
PR https://github.com/spidernet-io/spiderpool/pull/4379 ,  action https://github.com/spidernet-io/spiderpool/actions/runs/12270989004
Auto-merging pkg/ippoolmanager/ippool_manager.go
Auto-merging test/doc/annotation.md
CONFLICT (content): Merge conflict in test/doc/annotation.md
Auto-merging test/e2e/annotation/annotation_test.go
CONFLICT (content): Merge conflict in test/e2e/annotation/annotation_test.go
error: could not apply f9feb6b5... Merge pull request #4379 from ty-dc/fix/ip-exhaustion
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"

#4384


Incompatible with jQuery 3

The plugin seems not to be compatible with jQuery 3.
This is probably due to the "this.selector" property accessed in the plugin, which is not available anymore with jQuery 3.
See https://api.jquery.com/selector/ for reference.
Here is a discussion on an alternative approach to "this.selector":
https://stackoverflow.com/questions/21238281/what-replaces-the-deprecated-property-this-selector
Do you consider on making the plugin compatible with jQuery 3.

Rammed my head against this particular brick wall for far too long before I finally gave up and checked the Issues.


DO NOT MERGE YET Refactor for new infra

DO NOT MERGE YET
What?

Adds a deployment pipeline for the new infra.
TODO: Uses an environment variable for the tile server

Why?
To leverage the new infra setup.

👍🏼


Fix build

Test fails only on stable, but the published version will only be used on the (current) beta.


Spotless

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Spotless.
Why
Spotless.
Known limitations
Spotless.

Reference Server Preview is available here:https://anchor-ref-pr802.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr802.previews.kube001.services.stellar-ops.com/

Can we leave these changes to #799 to reduce conflicts?

I wanted ot merge it to reduce conflicts on my PR for OpenAPI


Add support for parsing bigint

This adds support for parsing BigInts.
refs #4

Awesome thanks!

Just published this changes as part of version 1.0.0

Thanks @jorinvo for merging this so quickly and releasing. Very useful.


Investigate ConPTY and OpenSSH to replace qtssh on Windows

Is your feature request related to a problem?
The only way to get VisIt's password window (on Windows) is via our qtssh mods to Putty.
When we need to update putty versions, if changes were significant, it is quite a bit of work to update qtssh.
OpenSSH has been available on Windows since 2018, Windows 10 build 1809.  I verified it works to connect to LC from a terminal window.
Problem is attempting to connect the password window and have it use openssh in the same fashion as on *nix (which uses pty when available).
ConPTY might be an option.
It might involve having to verify if ConPTY  and OpenSSH are available on the machines where VisIt gets installed.
If not, we could revert to a non-modified version of putty that we build and install, with the caveat that passwords will have to be entered via a terminal, instead of the convenience of  VisIt's password window (which has the added feature of being able to change the username needed for access).
See #18437 for recent urgent need to update putty versions.

@biagas also, if you wanted to attempt to quickly survey the user communtiy, we do have that new polling feature in our discussions. We could advertise the poll to users who mostly follow us on Teams too to be sure we get some inputs from there.


How to set 'Mail' property?

How do I set the primary email address property (.Mail)?

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

ID: 46857454-f2fd-2254-5a44-0a0ca1a7f068
Version Independent ID: 35ea3b33-903c-1a1c-a8ba-146608b40ece
Content: Configure user account properties with Office 365 PowerShell
Content Source: Enterprise/powershell/configure-user-account-properties-with-office-365-powershell.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@lesterw1  - Thank you for submitting feedback.
I will get this issue over to the Enterprise writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@lesterw1 I have added notes for mapping the Mail property to the corresponding parameters in the Set-AzureADUser and Set-MsolUser commands. Thanks for your question.

I see the note but unfortunately setting the "OtherMails" property only sets the alternative email addresses. It does NOT change the primary .Mail property. I just tested this. So the annotation in the documentation is not correct. :(

@lesterw1 Please try the instructions at https://mymicrosoftexchange.wordpress.com/tag/mail-attribute/ and let me know if they work for you.

@lesterw1 - From our understanding, the issue you raised has been answered by JoeDavies-MSFT. If you feel it hasn't been answered, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!


COHD and Openpredict KPs are not returning query results

This issue to capture the results from the mini-hackathon that occurred on May 20.
COHD and openpredict KPs were not returning results when Chris B ran the following query, possibly TRAPI validation errors
Here is the ARAX link for the results: https://arax.ncats.io/?source=ARS&id=62fa9f13-a7e4-4971-9580-1fb87d5345e2
@CaseyTa, would you be able to take a look? Chris B and Anne would like to revisit these queries next week during the mini-hackathon on June 3.

qg = {
"nodes": {
"n0": {
"categories": [
"biolink:ChemicalSubstance"
],
"name": "Chemical Substance"
},
"n1": {
"name": "EGFR",
"ids": ["NCBIGene:1956"]
}
},
"edges": {
"e0": {
"subject": "n0",
"object": "n1",
"predicates": [
"biolink:decreases_abundance_of",
"biolink:decreases_activity_of",
"biolink:decreases_expression_of",
"biolink:decreases_synthesis_of",
"biolink:increases_degradation_of",
"biolink:disrupts",
"biolink:negatively_regulates_entity_to_entity"
]
}
}
}

@tursynay, I think this is a duplicate of the standup meeting issue: https://github.com/NCATSTranslator/testing/issues/66
OpenPredict is not expected to return any results for this query.
Here's a copy of my response in the other issue:

We had a similar finding as @balhoff for COHD. COHD is returning an error saying

biolink:negatively_regulates_entity_to_entity was not recognized as a biolink predicate

This is expected behavior, from my understanding of how errors should be handled.
When I changed the query to biolink:entity_negatively_regulates_entity, COHD responds:

None of the predicates in ['biolink:decreases_abundance_of', 'biolink:decreases_activity_of',
'biolink:decreases_expression_of', 'biolink:decreases_synthesis_of', 'biolink:increases_degradation_of',
'biolink:disrupts', 'biolink:entity_negatively_regulates_entity'] are supported by COHD.

Again, this is expected behavior.

@CaseyTa , thank you for getting back. I will defer to @cbizon on the next steps for this issue.


Add pod_creation_wait_interal

Description

Add pod_creation_wait_interal property to give Kubernetes cluster some time to create pods for Job.
Motivation and Context

Fix https://github.com/spotify/luigi/issues/2570, also aimed to replace abandoned https://github.com/spotify/luigi/pull/2664
Have you tested this? If so, how?

I ran my jobs with this code and it works for me.

@honnix @Tarrasch @dlstadther Could someone please review?

@honnix @dlstadther I believe your comments are resolved, could you please review again?

@honnix @dlstadther @pisymbol ping

LGTM. It would be nicer if we could separate waiting for pod to show up and container to be running.

LGTM. It would be nicer if we could separate waiting for pod to show up and container to be running.

Sorry, could you please clarify is this a change request or just a comment? Also what are the odds that this PR will be merged anytime soon?

@plizmol It's more as a comment. I'm OK with this change. What do you think @dlstadther ?

I'm ok with this. If someone doesn't like it in the future, they can submit another PR to separate the delays.


Add label noise

This pull request adds a tool for label_projection datasets that introduces label noise.
We evaluate a metric such as Accuracy on test data, but we are unsure how "true" our training labels are. By evaluating the test Accuracy when we have artificially introduce label error at different levels we can look at the metric for several levels of artificial label noise. This resulting curves show how good the method will be at generalizing in the presence of mislabeled data. If curves for multiple methods are plotted on the same graph, a method whose curve have systematically better scores is the better performer.
The introduced tool method add_label_noise randomly relabels a fraction of the labels specified by the noise_prob parameter. Only labels from the training set are randomized.
Submission type

[x] This submission adds a new dataset
[ ] This submission adds a new method
[ ] This submission adds a new metric
[ ] This submission adds a new task
[ ] This submission adds a new Docker image
[ ] This submission fixes a bug (link to related issue: )
[ ] This submission adds a new feature not listed above

Testing

[x] This submission was written on a forked copy of SingleCellOpenProblems
[ ] GitHub Actions "Run Benchmark" tests are passing on this base branch of this pull request (include link to passed test: )
[ ] If this pull request is not ready for review (including passing the "Run Benchmark" tests), I will open this PR as a draft (click on the down arrow next to the "Create Pull Request" button)

Submission guidelines

[x] This submission follows the guidelines in our Contributing document
[ ] I have checked to ensure there aren't other open Pull Requests for the same update/change

This is great. Do you mind if I edit it to point branch master instead of task-label-projection ? To get rid of other commits

This is great. Do you mind if I edit it to point branch master instead of task-label-projection ? To get rid of other commits

Nevermind, sorry, will fix it another way

I updated the base branch for this pull requests, but the other commits did not go away. Could you please edit the pull request and see if only your commits will remain?

The tests got fixed, by unfortunately they fail with your addition: https://github.com/mxposed/SingleCellOpenProblems/runs/2232474817?check_suite_focus=true#step:14:392
This is because the loader decorator from here silently adds a custom attribute (two) to anndata object, and you copy your anndata object here
I think probably the correct way is to change the loader decorator so that it would add that field into adata.uns dictionary.
What are your thoughts? @vals


BrowserOnly component API has a counterintuitive usage of props.children

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
This is not exactly a bug, more like an API design flaw:  The <BrowserOnly> component expects its props.children to be a lambda function instead of ordinary JSX elements.  This is counterintuitive and seems unnecessary.
Steps to reproduce

Try to write some code using the <BrowserOnly> component:
// Try 1: "Uncaught TypeError: children is not a function"
const MyComponent = (props) => {
  return (
    <BrowserOnly>
      {props.children}
    </BrowserOnly>
  );
};

// Try 2: Okay let's try the example from the website docs.
// But still: "Uncaught TypeError: children is not a function"
const MyComponent = () => {
  return (
    <BrowserOnly>
      {() => page url = {window.location.href}}
      {props.children}
    </BrowserOnly>
  );
};

// Try 3: Let's simplify it down to the bare minimum
// "Uncaught TypeError: children is not a function"
const MyComponent = () => {
  return (
    <BrowserOnly>
      Okay seriously what is going on here??
    </BrowserOnly>
  );
};

// Try 4: An accidental space character 🥴
// "Uncaught TypeError: children is not a function"
const MyComponent = () => {
  return (
    <BrowserOnly> </BrowserOnly>
  );
};

After about 20 minutes of debugging and scrutinizing the docs and banging my head against the wall, what I realized is that this API expects the JSX child content to evaluate to a lambda function that returns elements, not a regular JSX element.  Any stray space character will cause props.children() to fail when BrowserOnly  tries to invoke the object as a function.
This API design does work if used correctly, but it goes against all intuition for how JSX notation is supposed to function.

Suggested redesign
Instead of this:
Current API design
const MyComponent = (props) => {
  return (
    <BrowserOnly fallback={
Loading...
}>
      {() => {
        const LibComponent = require('some-lib').LibComponent;
        return <LibComponent {...props} />;
      }}
    </BrowserOnly>
  );
};

...what if the API was like this:
Proposed API design
const MyComponent = (props) => {
  const renderForBrowser = () => {
     const LibComponent = require('some-lib').LibComponent;
     return <LibComponent {...props} />;
  };
  return (
    <BrowserOnly renderForBrowser={renderForBrowser}>

Loading...

    </BrowserOnly>
  );
};

Self-service

[X] I'd be willing to fix this bug myself.

Let me try to explain the current design.
Firstly, the children of a component is usually the center of this component. The component is called BrowserOnly, not SSRFallback, so the center of it is what's rendered in a browser. It's like a cardboard box to wrap a fragile vase. Therefore, we would never declare the fallback as children. You can even omit the fallback and just let it return nothing, which usually makes sense as well.
Secondly, I guess you understand why it's a function rather than a JSX component. The children must be lazy-evaluated because you may need to import a lib that calls browser APIs directly.
I think the only bad thing here is the error message "Uncaught TypeError: children is not a function". If we have a custom error message like "children must be a lazy-evaluable function so you can require() a browser-only library", would that be better?

Suspense will become more widely adopted, and I think there's value in having a similar API: the children is not the placeholder
https://reactjs.org/docs/concurrent-mode-suspense.html
<Suspense fallback={<Spinner />}>
  <ProfilePage />
</Suspense>

Now, we designed this component that way also to avoid a potential pitfall that is quite easy to make for less experienced users (many don't understand well what lazy execution, SSR and hydration is, so we should nudge them to use good patterns).
Consider the following:
const MyComponent = props => {
  return (
    <BrowserOnly>

{/* Huge JSX Tree here */}

URL of the page is {window.location.href}

    </BrowserOnly>
  );
};

Less experienced users will think this is fine, but it will still throw on the server due to using window. Even if the JSX is not outputted, it still has to be constructed, and eager evaluation leads to a failure such as window is not defined. We already recommend users to use BrowserOnly in the error log, but this would be confusing because the user is already using BrowserOnly
(also, we are constructing the JSX tree, and it will actually never be useful so it's a waste of computing resources, but it's a micro-optimization, not very important)
Now, for sure a solution could be:
const Content = props => (
  <>

{/* Huge JSX Tree here */}

URL of the page is {window.location.href}

  </>
);

const MyComponent = props => {
  return (
    <BrowserOnly>
      <Content />
    </BrowserOnly>
  );
};

This would work but it's harder to teach why it's needed to users that are not so familiar with React.

I think the only bad thing here is the error message "Uncaught TypeError: children is not a function". If we have a custom error message like "children must be a lazy-evaluable function so you can require() a browser-only library. Current type: string" (which will be helpful in case of the "accidental space"), would that be better?

Agree, IMHO we should just have a better error message in case children is not a function.

the children of a component is usually the center of this component. The component is called BrowserOnly, not SSRFallback, so the center of it is what's rendered in a browser.

For what it's worth, as a new adopter of Docusaurus, I initially had trouble understanding what the name BrowserOnly was referring to:  My docs don't have other output targets like PDF or DocFX.  Nor are they hosted by a Node.js service -- they are purely static CDN pages.  It seemed like my entire site was already "client-side" and "browser only," so what does this tag do? It took a bit of thinking to remember that Docusaurus has a SSR prerendering feature (that is only used during final deployment).
So if we were to change the API design, maybe the component could be renamed at the same time. Something like <PrerenderPlaceholder> or <NoPrerender>.  Just an idea.

Therefore, we would never declare the fallback as children but put the browser-only component in props. You can even omit the fallback and just let it render nothing for SSR, which usually makes sense as well.

This could be solved by representing both as props:
Proposed design #2
const MyComponent = (props) => {
  const renderForBrowser = () => {
     const LibComponent = require('some-lib').LibComponent;
     return <LibComponent {...props} />;
  };
  return (
    // The "fallback" prop is entirely optional.
    <BrowserOnly renderForBrowser={renderForBrowser} fallback={
Loading...
} />
  );
};

Eliminating the child props entirely avoids the issues @slorber mentioned of accidentally referencing window or performing expensive rendering that gets discarded.

the error message "Uncaught TypeError: children is not a function". If we have a custom error message like "children must be a lazy-evaluable function so you can require() a browser-only library. Current type: string" (which will be helpful in case of the "accidental space"), would that be better?

This would certainly be an improvement independent of the API design questions. 👍

Sorry, not really willing to change the API. If you look at suspense, Nuxt's client-only, or other SSR solutions, the escape hatch would all have the browser-only stuff as the children rather than as props. This is just more intuitive for most people: it's more a "wrapper" than a "higher-order component".
We can definitely improve on the docs and the error message about what SSR is, but it's good to keep a consistent API with other solutions out there.

Makes sense -- thanks for the explanation and for improving the error message!

Yes, let's just keep the current API, and improve the error message.
It's in sync with the ecosystem, Suspense and what React developers are used to already. This popular blog post also mention a similar comp: https://www.joshwcomeau.com/react/the-perils-of-rehydration/#abstractions
Now if you have a concrete suggestion to make it clearer why Docusaurus needs this comp, PRs are welcome


Live-preview package causes client side error in traverseFields

Link to reproduction
No response
Describe the Bug
I am sure this is still wip but this is causing a client side error on my project which is blocking me rn. I first noticed this error after clearing my pnpm cache and reinstalling all modules. The error is thrown when I open my NextJS frontend (live-preview and draft preview is not affected). The error is thrown in the traverseFields file from the live-preview package
traverseFields.js:15 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'forEach')     at traverseFields (traverseFields.js:15:1)     at mergeData (mergeData.js:17:1)     at handleMessage (handleMessage.js:29:1)     at onMessage (subscribe.js:17:1)
After some digging in the source code I have noticed that this happens because fieldSchema is undefined and forEach is called anyway. I was able to fix this locally by catching the undefined case fieldSchema?.forEach(...) in line 24 but I also thought that this code should not be called in the first place so there might be a bug in the conditions in the handleMessage file which is calling the traverseFields eventually. This is only my assumption I hope it helps in fixing this issue.
EDIT:
I also found out that a similar problem occurs if you got for example the MetaMask browser extension activated on Chromium. There is a runtime error happening in handleMessage file of the same package because it also makes use of a MessageEvent. The error occurs when trying to JSON.parse the data field of the MessageEvent.

To Reproduce
Really not sure how to reproduce this behaviour. Because it only happened after reinstalling my node_modules. I tried to use a fresh mongoDB table to make sure it wasn't my data causing this. I am using webpack, lexical, mongodb, NextJS custom server, drafts and live-preview. Sorry for the lack of information on the reproduction I hope pointing out the files from the source code helped.
Payload Version
2.0.11 and 1.0.5 for live-preview-react
Adapters and Plugins
No response

I'm getting the same.

Strangely, if I click to open the live preview in a separate window, it works fine!

Same here! I though that it has something to do with next-payload.
For me, it is triggering the error only when I open the page directly (in dev mode).
Live preview is working fine, docked or separate window.
Payload Version
2.0.13
Adapters and Plugins
@payloadcms/live-preview-react 0.1.5
@payloadcms/next-payload 0.1.8

I had a project with payload hosted separately. I created a project with the website template and copy pasted my nextjs code in.
What worked completely fine in my old project resulted in this same error now. I wasn't even using the live preview function. Why does it even do anything when live-preview is not even being used? Why does it behave differently inside monorepo?

Hey @Cuzart and everyone, I just opened up PR #4074 which will prevent this error from throwing, but this doesn't necessarily solve for why the field schema is missing in the first place for some of you. Before traversing fields and merging data, we dispatch a post message event to deliver the schema to your front-end one time. It could be that this delivery failed, and then subsequent events are missing the field schema, as you're seeing.
@thompsonsj the fact that it's works again when opening in a new window, is probably because we are re-delivering the field schema again.
@arieltonglet the fact that you are only seeing this error when accessing the page directly feels odd. Can you confirm that this is true? Because on direct access of your site, there is no parent window at all to even send message events from in the first place.
@HarleySalas I'm not sure I'm following. Can you be explain your scenario a bit more?

Hi @jacobsfletch, thanks a lot for the fix!
In the past days I was working in other parts of this project and had to reinstall node_modules, among a lot of changes in collections and other stuff – I'm saying this because of @Cuzart original post, where he said this only happened after reinstalling node_modules.
I've tested now again, and the live preview is working fine (at some point I was getting this error in the preview as well), but accessing the page directly is still triggering this error. I'll try to reproduce this in a fresh project tomorrow to see if I can find out what's happening. Thanks again!

Hey @jacobsfletch
I was able to reproduce the error in this repo:
https://github.com/arieltonglet/payload-test-traverse
https://github.com/payloadcms/payload/assets/13951624/e477dbf2-ab28-4a4a-9281-edb669e7b530

@HarleySalas I'm not sure I'm following. Can you be explain your scenario a bit more?

What I'm saying is that I did not experience the issue when payload was deployed separately from my nextjs frontend. I only encountered this issue after switching to a monorepo and hosting them together.
I was just expressing how odd it was to me that the error occurs, even when the payload admin is not open. I understand if live-preview has a bug, but if I'm not even using the live-preview feature, it's quite odd that it is still trying to work, or do something.
I can also confirm as well, in my instance, the error occurs both when the website is open by itself *and when you use the live-preview feature, with an iframe.

Thanks for the fix @jacobsfletch. Although as you already said this does not prevent the why. As you said the cause is a missing schema but why is the schema even requested when I only request my frontend this has nothing to do with live-preview at all and it should not evoke code within the live-preview package. I got the supposition that hosting my frontend and payload on the same server and same port (next-custom server) may cause this but I have no idea how to avoid this and I feel like this code should not be run at all in this context.


Regularly see E0164 - timeout or abort while handling: method GET URI /apis/projectcalico.org/v3

Hi
We regularly see these errors below on our kube-apiservers, that suggest something is not right with the aggregated v3 api's.
However, we don't see any negative impact, calico is working fine, the apiserver in calico-apiserver namespace all seems fine.
We removed the custom resource for default APIServer and put it back on, no difference..
Should we be concerned?
Expected Behavior
No errors in logs - errors in kube-apiserver logs attract our attention quickly ;-)
Current Behavior
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/profiles?allowWatchBookmarks=true&resourceVersion=73417144%2F73417144&watch=true" audit-ID="c17b2ff6-c3a8-4698-a9b5-58b9dc6bf56a"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/globalnetworksets?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="e853832c-3508-48a7-b5a8-f3e787df9c94
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/hostendpoints?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="31ef1042-a457-4510-997a-26cd306e0551"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/bgppeers?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="a4bd1b53-156b-4f62-b8d7-8413283d9a2b"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/kubecontrollersconfigurations?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="540af559-1cf8-47ed-9a03-6165a016901b"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/ipamconfigurations?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="d0ce56d5-209b-4241-8442-787ce6903d50"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/clusterinformations?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="f67a7af1-d9cf-4110-9c56-80ee4a87c545"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/felixconfigurations?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="bf03ef4f-73f4-4ae0-aeb4-30f8c1dacad4"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/networksets?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="5a855bef-247b-4214-8909-4eedf83d5ec1"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/globalnetworkpolicies?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="fd9c9329-8a19-4bce-a1b3-5863aefeb72e"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/ippools?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="f1972004-bc13-43c0-8f97-701fae5f1f91"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/caliconodestatuses?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="aa809b3f-23bd-41f9-9713-43a90270c736"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/blockaffinities?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="34ef13d1-658b-4141-bea3-4c0c5ab09a69"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/networkpolicies?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="ce6fe12c-039c-4005-a0f3-f6e0d46d7369"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/bgpconfigurations?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="9857ed1e-e75f-4c4b-87a1-c06210a0eea1"
wrap.go:53] timeout or abort while handling: method=GET URI="/apis/projectcalico.org/v3/ipreservations?allowWatchBookmarks=true&resourceVersion=73417144&watch=true" audit-ID="43db0f4e-0d78-42fe-b2ef-4442fed68325"

Steps to Reproduce (for bugs)

Fresh K8s 1.25 Cluster
Install tigera-operator
Add default Installation
Add default APIService

apiVersion: operator.tigera.io/v1
kind: APIServer
metadata:
  name: default
spec: {}

Your Environment

Calico version 3.25.1, but have seen on earlier versions on other clusters..
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes 1.25

This might not necessarily be a problem - I believe watch=true requests have an inherent timeout after which they are terminated due to inactivity.
Does this happen roughly once per minute for each of those URIs? I believe that's the default timeout.

Hi @caseydavenport - every 10 minutes without fail.

It would be good to make those logs go away - I will see what can be done about that... but I think it's safe to say these are benign logs and essentially working as expected, since long-lived "watch" requests against the API server that receive no traffic will eventually be terminated and restarted by design.

Thanks Casey - that was our assumption as well and glad to have it confirmed. So not an actual error really 😉

We are seeing these as well in our kube-api-server logs.
Is there a way to disable these? Cause they cause a massive amount of spam over time, and if they are benign why are they being logged as WARN or even ERROR sometimes?

Is there any good solution?

Hello there,
I'm actually having this issue, did any roundabout or roadmap exist for this ?

anything changed on this?

I believe @ti-afra is working on better logging and log level configuration for the API server, which may solve this.


Potential break in sequence from"Configuring idenity provider", to "Test connection string"

So after configuring the idenitity provider with your bot, the next step mentioned is to test connection string; but right after the one hits 'save', the whole configuration tab collapeses, hence the user won't see the test connection tab anymore.
Would instead suggest to have a step to re open the Oath configuration tab, so the user has access to "test the connection" tab :)

Are you referring to these documents.
After configuring the identity provider, you need to get into the newly created OAuth Connection and Test the Connection.


Add a random seed function to seed with various data including timestamp(s)

Besides timestamps, can also use system information and casts of pointers to integral values.


feature: support SQLServer XA mode

Ⅰ. Describe what this PR did
SQL Server 2019 version above supported
创建xa事务的账户必须拥有对应库的SqlJDBCXAUser权限 sa账号无法添加该权限,所以需要新建其它账号
开启对应数据库的xa开关 (master库必须要执行)
use xxx库
EXEC sp_sqljdbc_xa_install
Ⅱ. Does this pull request fix one issue?

fixes #3204
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #3203 into develop will decrease coverage by 0.09%.
The diff coverage is 66.66%.

@@              Coverage Diff              @@
##             develop    #3203      +/-   ##
=============================================
- Coverage      50.50%   50.40%   -0.10%
- Complexity      3135     3136       +1
=============================================
  Files            596      596
  Lines          19761    19756       -5
  Branches        2465     2425      -40
=============================================
- Hits            9980     9958      -22
+ Misses          8777     8768       -9
- Partials        1004     1030      +26

Impacted Files
Coverage Δ
Complexity Δ

...a/io/seata/rm/datasource/xa/DataSourceProxyXA.java
74.46% <66.66%> (-9.54%)
9.00 <0.00> (+1.00)
:arrow_down:

...obuf/convertor/BranchRegisterRequestConvertor.java
90.47% <0.00%> (-9.53%)
3.00% <0.00%> (ø%)

...otobuf/convertor/BranchReportRequestConvertor.java
90.90% <0.00%> (-9.10%)
3.00% <0.00%> (ø%)

...obuf/convertor/BranchRollbackRequestConvertor.java
92.00% <0.00%> (-8.00%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalBeginResponseConvertor.java
92.59% <0.00%> (-7.41%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalCommitRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalStatusRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...obuf/convertor/GlobalRollbackRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterTMRequestConvertor.java
94.73% <0.00%> (-5.27%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterRMRequestConvertor.java
90.47% <0.00%> (-4.77%)
3.00% <0.00%> (ø%)

... and 27 more

Codecov Report

Merging #3203 (7f84875) into develop (aa17303) will decrease coverage by 0.13%.
The diff coverage is 58.06%.

@@              Coverage Diff              @@
##             develop    #3203      +/-   ##
=============================================
- Coverage      52.09%   51.95%   -0.14%
+ Complexity      3511     3510       -1
=============================================
  Files            638      638
  Lines          21147    21172      +25
  Branches        2629     2602      -27
=============================================
- Hits           11016    11000      -16
- Misses          9044     9056      +12
- Partials        1087     1116      +29

Impacted Files
Coverage Δ
Complexity Δ

...a/io/seata/rm/datasource/xa/ResourceManagerXA.java
14.28% <0.00%> (-0.87%)
4.00 <0.00> (ø)

...a/io/seata/rm/datasource/xa/DataSourceProxyXA.java
72.00% <64.28%> (-12.62%)
9.00 <1.00> (+1.00)
:arrow_down:

...obuf/convertor/BranchRegisterRequestConvertor.java
90.47% <0.00%> (-9.53%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalBeginResponseConvertor.java
92.59% <0.00%> (-7.41%)
3.00% <0.00%> (ø%)

...n/src/main/java/io/seata/common/util/IdWorker.java
77.08% <0.00%> (-6.25%)
11.00% <0.00%> (-1.00%)

...otobuf/convertor/GlobalCommitRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalStatusRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...obuf/convertor/GlobalRollbackRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterTMRequestConvertor.java
94.73% <0.00%> (-5.27%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterRMRequestConvertor.java
90.47% <0.00%> (-4.77%)
3.00% <0.00%> (ø%)

... and 17 more

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: jsbxyyx:x: a364176773You have signed the CLA already but the status is still pending? Let us recheck it.


Make release package file names more uname friendly on Linux

When operating on Linux there are different variants of swiftly for either x86_64 or aarch64 architectures. It is likely that people will need to make platform-independent samples, such as on swift.org to download the correct binary package for their system. By making the filename reflect what uname -m on the system scripts can use this to make sure that they download the correct release package and also they can download both without collisions. Fix the release package filename for linux x86_64 to include the architecture in the file name so that the filename matches the following:
swiftly--$(uname -m).tar.gz

@swift-ci test macOS


i6 = 1 instead if i6 = 2

Hi hyper, thanks for the solution. For the value of i6, I think that it should be 1 (index offset) like i2.

No, this makes it give the wrong answer. Remember that [[6]] is larger than [[2]], so the index of [[6]] starts one higher because of that.

Oh. That's because of the + [[[2]], [[6]]]. You're not supposed to have that there; if you include that then you should start i2 and i6 at 1 but you're not supposed to have that. I accidentally left it in since I was demonstrating something during the video but I removed that a long time ago.

Oh Yeah, I didn't pay attention. there is no + [[[2]], [[6]]] in your Code. My bad.
Thanks a lot :)


Update dependcies and fixed lint err

Codecov Report

Merging #5 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #5   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines          75     75
=====================================
  Hits           75     75

Impacted Files
Coverage Δ

src/template/index.js
100% <100%> (ø)
:arrow_up:

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 89dd2c3...aeb2118. Read the comment docs.


Synced folder owner/group either admin / 1000 / solr but not vagrant

Issue Type

Bug Report

Your Environment
Vagrant 1.9.1
VirtualBox 5.1.10r112026
ansible <IP_ADDRESS>

Your OS

Linux (Fedora 25)

Full console output
Example:
vagrant@beta:/var/www/drupalvm$ ls -la
total 660
drwxrwxr-x 20 solr solr   4096 Feb 15 13:56 .
drwxr-xr-x  5 root root   4096 Feb 15 13:34 ..
-rw-rw-r--  1 solr solr   8280 Jan  4 09:18 build-pre-commit.xml
-rw-rw-r--  1 solr solr   8877 Feb  6 09:29 build.xml
drwxrwxr-x  4 solr solr   4096 Jan  4 09:18 ci
-rw-rw-r--  1 solr solr   7850 Feb 15 12:36 composer.json
-rw-rw-r--  1 solr solr 410655 Feb 15 12:36 composer.lock
drwxrwxr-x  2 solr solr   4096 Feb 15 13:47 config
drwxrwxr-x  3 solr solr   4096 Jan 25 13:47 console
drwxrwxr-x  3 solr solr   4096 Jan 24 09:18 designs
drwxrwxr-x  3 solr solr   4096 Jan  4 09:18 doc
drwxrwxr-x  4 solr solr   4096 Jan  4 09:18 docker
-rw-rw-r--  1 solr solr   1667 Jan  4 09:18 docker-compose-ci.yml
-rw-rw-r--  1 solr solr   2404 Jan  4 09:18 docker-compose-dev.yml
-rw-rw-r--  1 solr solr   1211 Jan 20 15:17 docker-compose.yml
drwxr-xr-x  8 solr solr   4096 Feb 15 12:36 docroot
drwxrwxr-x  3 solr solr  73728 Feb 15 12:29 drupal-cm
drwxrwxr-x  8 solr solr   4096 Feb 15 13:56 .git
-rw-rw-r--  1 solr solr    322 Feb  9 12:44 .gitignore
drwxrwxr-x  3 solr solr   4096 Feb 15 13:57 .idea
-rw-rw-r--  1 solr solr   5716 Jan  4 09:09 .jshintrc
-rw-rw-r--  1 solr solr   1331 Jan  4 09:18 Makefile
drwxrwxr-x  6 solr solr   4096 Feb  7 08:35 modules
drwxrwxr-x  2 solr solr   4096 Feb  7 08:35 patches
drwxrwxr-x  2 solr solr   4096 Feb 13 09:56 provision
drwxrwxr-x  5 solr solr   4096 Jan 20 11:18 qa
-rw-rw-r--  1 solr solr   1182 Jan  4 09:09 qa-tools.json
-rw-rw-r--  1 solr solr   6575 Feb  8 14:41 README.MD
drwxrwxr-x  3 solr solr   4096 Jan  4 09:09 scripts
-rw-rw-r--  1 solr solr    193 Feb 15 13:56 test-scripts
drwxrwxr-x  6 solr solr   4096 Jan  4 09:18 themes
-rw-rw-r--  1 solr solr   4638 Feb  7 08:35 .travis.yml
-rw-rw-r--  1 solr solr  15788 Jan 17 14:18 user-export.sql.gz
drwxrwxr-x  4 solr solr   4096 Feb 15 13:27 .vagrant
-rw-rw-r--  1 solr solr    544 Feb 13 09:55 Vagrantfile
drwxrwxr-x 70 solr solr   4096 Feb 15 12:36 vendor

Summary
It seems the shared drupal-vm folder owner and group doesn't get changed to vagrant, when you don't select one of the build options. We use an ant database import script to provision our Drupal installation. Depending on if I either turn on the solr installed_extra or not the shared folder user/owner is either solr or admin/1000 when not.
config.yml

I'm thinking this is related to https://github.com/geerlingguy/drupal-vm/issues/1016
See, specifically https://github.com/geerlingguy/drupal-vm/issues/1016#issuecomment-266808076

Yeah, it seems he had the same problem. Could you test it without specifying a build option? I guess that's the culprit of the problem.

This is most likely because the user on your host computer has UID 1000, which just so happens to become the UID of the solr user within the VM. With NFS the UID/GID is synced as is, and on osx that resolves to 501:dialout for most. On linux I guess it's 1000:1000.
You can fix it by using the vagrant-bindfs plugin.

I'm pretty sure the issue is identical UIDs as both reported instances was using Linux. @geerlingguy  can we close this? or should we add something to the docs?

I'd say close it... it seems to be somewhat of an edge case, and Google searches should hopefully lead people back to these issues, where there's a solution mentioned in the comments. Thanks!

I tried to use the bindfs plugin with a Vagrant.local file following the guide, but this didn't work for me 😞. Could I try something else or did I do something wrong trying to get it to work? I don't really understand why some people don't have this problem (neither did I in de past) and I do.


Correct buffer length checking

The buffer length checking does not perform correctly if a buffer is
passed in that is exactly the correct length.
The test that was present generated an incorrect error if a buffer length was passed in which was the same length as the output to be generated.
if ((0 < 0) || (0 + 1 >= 1)) is true.

My problem with this is that the code doesn't seem to handle overflows right even after the change.
Also, I think offset is best not expressed as an ssize_t -- we don't need negative offsets, just a way to indicate "broken".

I would be more than willing to get rid of the ssize_t.  A return value of 0 should be usable for a failure condition.  I do not think one can successfully encode a CBOR structure which has a final length of zero.
I need more idea of what you think is the problem with overflows in order to try and look at those problems.  These might be better dealt with by creating new issues for those problems.


Authorization error

A few weeks later this error began to appear to make the athletes' authorization.
I can not figure out why.
`
stdClass Object
(
[message] => Bad Request
[errors] => Array
(
[0] => stdClass Object
(
[resource] => RequestToken
[field] => code
[code] => invalid
)
    )

)
`

The problem is the new update.
May 25, 2018
GET https://www.strava.com/oauth/authorize returns the scope of the eventual token in the response.
The Code is coming with scope together now
EX:<PHONE_NUMBER>389014f72f8bc5c&scope=view_private
And the &scope=view_private cause erro on $api->tokenExchange($code[1]);

I am not having any problems with the following code. This seems to be more of an error in the implementation and not so much an issue with this repo. Correct?
$token = $api->tokenExchange($code)->access_token;
$api->setAccessToken($token);


Schedule of LE audio in zephyr

Hi，
For LE Audio， Zephyr now supports ISO and MICP&VCP related profiles.  Is there a plan to support BAP&MCP&CCP and LC3？Is there a schedule for LE audio development in Zephyr?
Looking forward to your reply!

Hi @xin10pan. Some of the work implementing those services is ongoing in a private repository because some of the the services you mention (BAP in particular) are not public yet. If you'd like to get access to that repo you would need to join the Zephyr Project as a company. Otherwise you can wait until all of that work trickles down to the public repo.
Regarding LC3, we have a preliminary codec here: https://github.com/zephyrproject-rtos/liblc3codec but more work is expected in the future.

When will these profiles be pushed to public repo? Is there a schedule?


Add interview command

What
Add interview command, update JsonAdaptedPerson, enhance UI to show interview date
Why
Interview command enables hiring managers to filter out shortlisted applicants and sort them based on interview date.
JsonAdaptedPerson must be updated as interviewDate field is added to Person class.
Hiring managers need to see the interview dates of applicants.
How
Add personComparator field to ModelManager. Interview command will use this comparator to sort applicants based on interview date. List command will revert to the default comparator and thus the original applicant ordering as well.
Fix #2

Seems like there is a merge conflict due to the refactoring of our Tag to the Note class. Do take a look at the conflicts and resolve them!


VSCode: CodeLens references numbers did not load and the output window contain error "Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object." when doing the Razor refactoring

Azure DevOps work item: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1284417
Testcases Affected

[6.0] SimpleWebAppRazorEditingWithVSCode
[6.0] SimpleBlazorRazorEditingWithVSCode
Platform

[x] Windows
[x] macOS
[ ] Linux

Repro Steps

Create an MVC project and open via VS Code:

md MVC
cd MVC
dotnet new mvc
code .

Go to https://github.com/OmniSharp/omnisharp-vscode/releasesinstall the latest csharp-1.23.10-lsp-beta.vsix.
Open Pages/Shared/_Layout.cshtml
Type "@add" and verify the intellisense list. Select "addTagHelper", then type "*, Microsoft.AspNetCore.Mvc.TagsHelpers" following it. Save the change.
In VS Code, using CTRL + ~ to open up TERMINAL window, type the following code.

'namespace MVC // Or Razor
{
    public class CustomTagHelper
    {
    }
}' | Out-File CustomTagHelper.cs

In CustomTagHelper.cs, type ": TagHelper" following the class. And then select "using Microsoft.AspNetCore.Razor.TagHelpers" through the Quick Actions
In _Layout.cshtml, type "@addTagHelper *, MVC
Open Program.cs, then enter the code: public interface ICheese {} above public class Program and save
Edit Index.cshtml to include the following at the bottom:

@{ var x = typeof(Program); }
@functions {
 public class Cheddar : ICheese {}
}

Save and close Index.cshtml
Close all instances of VSCode and re-open this project.
go to the program.cs file

Note:

It works well on 5.0 Project
It works well on 6.0 Preview 1

Actual Result

CodeLens references numbers did not load and the output window contain error "Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object."

Error Log

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at OmniSharp.Helpers.LocationExtensions.<>c__DisplayClass0_0.b__3(Document d) in D:\a\1\s\src\OmniSharp.Roslyn.CSharp\Helpers\LocationExtensions.cs:line 45
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable1 source, Func2 predicate)
at OmniSharp.Helpers.LocationExtensions.g__GetSourceText|0_0(Location location, IEnumerable`1 documents, Boolean hasMappedPath) in D:\a\1\s\src\OmniSharp.Roslyn.CSharp\Helpers\LocationExtensions.cs:line 45
at OmniSharp.Helpers.LocationExtensions.GetQuickFix(Location location, OmniSharpWorkspace workspace) in D:\a\1\s\src\OmniSharp.Roslyn.CSharp\Helpers\LocationExtensions.cs:line 19
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.d__64`1.MoveNext()
at System.Linq.Buffer1..ctor(IEnumerable1 source)
at System.Linq.OrderedEnumerable`1.d__1.MoveNext()
at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeList(JsonWriter writer, IEnumerable values, JsonArrayContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.Serialize(JsonWriter jsonWriter, Object value, Type objectType)
at Newtonsoft.Json.JsonSerializer.SerializeInternal(JsonWriter jsonWriter, Object value, Type objectType)
at Newtonsoft.Json.JsonConvert.SerializeObjectInternal(Object value, Type type, JsonSerializer jsonSerializer)
at OmniSharp.Protocol.Packet.ToString() in D:\a\1\s\src\OmniSharp.Host\Protocol\Packet.cs:line 22
at System.IO.TextWriter.WriteLine(Object value)
at System.IO.TextWriter.SyncTextWriter.WriteLine(Object value)
at OmniSharp.Services.SharedTextWriter.ProcessWriteQueue() in D:\a\1\s\src\OmniSharp.Host\Services\SharedTextWriter.cs:line 48
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

@NTaylorMullen This issue does not reproduce after installing the pre-release C# (here). Should we close it ？

@NTaylorMullen This issue does not reproduce after installing the pre-release C# (here). Should we close it ？

Oh definitely! Thanks for double checking @v-Lily!


Extract expression profiles from matrix.

Extract expression profiles from matrix. Fixed #82, #84, #112.

LGTM


Readme Improvement for face morphing

https://github.com/akshitagupta15june/Face-X/tree/master/Awesome-face-operations/Face-Morphing

Please assign this issue to me I would like to work on the readme file...

@akshitagupta15june please assign !!!

yup

Hey, @Jainish-shah  any update on this? Are you working on this?

Yeah! I will be completing it today as there was a small tension of Internal exams.....

Yeah! I will be completing it today as there was a small tension of Internal exams.....

that's great! , go-ahead @Jainish-shah


For PR #381: Run also from feature branch as well as main

Checking if the changes in PR #381 were successful is hard because the resource gallery submission action is running against the main branch.
This PR is only for temporary purposes to get this action to run on the "fix-resource_gallery-workflow" branch that is the base of PR #381 instead of the main branch. Once we get that PR pass and merged, we can revert this PR's only change in the workflow file.
I couldn't think of an alternative solution in this case but am open to if there is any.

Closing this PR as I noticed issues-based workflows could not be run of feature branches (ref)


Facebook failed with error 0

Error message: Call to a member function children() on null
Query string: action=display&bridge=Facebook&u=%E8%94%A1%E4%BE%9D%E6%9E%97+Jolin+Tsai&media_type=all&format=Json

After trying 蔡依林 Jolin Tsai on my side the exact PHP error seems to be:
Notice: Undefined offset: 0 in /[...]/bridges/FacebookBridge.php on line 413

Actually, the bridge is not broken, but does not handle that error very well. It could throw a better error message such as "User not found". You specified the display name of the user when the bridge expects the username shown in URL, hoo.jcai. Works fine on my side using that.


🍒 Cherry pick PR #6684 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/6684 to staging 🍒

🚀 Cherry-picked to staging by @roryabraham in version: 1.1.19-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @Julesssss in version: 1.1.21-1 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


add the function of agreeing to all requests

What's the Problem?
When I copy multiple files, many of which are the same as the folders I copy, I have to choose to deal with each one that bothers me. So hopefully the developer will add consent functionality to all requests soon.
Solution/Idea
add option button Yes All or No All
Alternatives

Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22000.466
Windows Version
Windows 11 21H2 22000.466
Comments
No response

Sames as #5030

@thientrile This issue should be resolved in the preview version. https://files.community/download/preview


[Bug]: order of similarity matters, WHY?

Current Behavior
Using the default onnx model,
Score function
def get_score(a, b):
    return evaluation.evaluation(
        {
            'question': a
        },
        {
            'question': b
        }
    )

Case 1:
a = 'What is neural network?'
b = 'Explain neural network and its components.'
c = 'What are the key components of neural network?'
print (get_score(a, b))
print (get_score(a, c))
print (get_score(b, c))

0.7585506439208984
0.02885962650179863
0.0909486636519432

Case 2:
a = 'What is neural network?'
b = 'Explain neural network and its components.'
c = 'What are the key components of neural network?'
print (get_score(b, a))
print (get_score(c, a))
print (get_score(c, b))

0.17746654152870178
0.013074617832899094
0.8378676772117615

Just changed x,y to y,x while passing argument to get_score, why drastic changes in scores?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response

It seems that you did not experiment with changing x,y to y,x. It seems that you should use
print (get_score(a, b)), print (get_score(b, a)) for comparison.

It's amazing that there is such a phenomenon!

Is it because the LLM replies differently if ranking/ordering of content is different in a rag application?

I don't know much about this part. Theoretically, the distance between the two vectors should be calculated to get the score. Swapping the positions should not affect the score.

We trained a cross-encoder model to evaluate similarity, where conceptually the pairs should ignore their positions. However, since it uses BERT, there could be some unusual behavior, as it's a lightweight transformer without any constraints to enforce this.


Fix python 2.7 and 3.4 syntax errors

Fixes #4.
Certain syntax was causing errors when installed on python 2.7 and 3.4. I'm not sure h5pickle can fully support python 2.7 given its use of __getnewargs_ex__ which was added in Python 3.4 (https://www.python.org/dev/peps/pep-3154/#calling-new-with-keyword-arguments).

Thanks David!


Define DateTime using struct embedding rather than type renaming.

This results in us inheriting all the methods of DateTime automatically.

jenkins: test this

Regarding your comment: it's just more convenient to not have to cast to time.Time to get access to these methods.

jenkins: test this


Quotes should be escaped when exporting to CSV

Variables containing quotes does not seem to get escaped when I export to CSV
The results of the following query:
SELECT ?var1 ?var2 ?var3
WHERE {
  BIND ("the quotes in var2 and var3 should be escaped" AS ?var1)
  BIND ("\"surrounded by quotes\"" AS ?var2)
  BIND (",,\"\",\",\"chaos\"\"\"" AS ?var3)
}

Is exported to the following, unmanageable CSV, when I press the "Download as CSV"-button:
 "var1" , "var2" , "var3" ,
 "the quotes in var2 and var3 should be escaped" , ""surrounded by quotes"" , ",,"",","chaos"""" ,

Tested with yasr/2.9.0 + 2.11.4 AND yasr/2.10.1 + yasqe/2.11.5 and both in Chrome and Firefox
It seems to me that there is code to handle this src/jquery/tableToCsv.js, but I have not tested if this code is ever triggered.
Thank you for an excellent tool set!
Best regards,
Jens Kilde Mjelva

Ah, thanks for that Jens, this should be fixed in the newest release. I'll include it in yasgui as well, after I made some other small bug fixes.

Thank you for the quick response!
I still get the same output CSV (no escaped quotes) when exporting after bumping up to YASR v.2.10 locally. Same thing when testing on http://yasr.yasgui.org/.
Am I missing something?

ah, was too hasty with my fix. I made some small improvements, and it should work better now

Looks good!


Docs for type aliases

Currently if we look at (for example) the Str module, it doesn't show docs for the Str type alias itself.
It should though!
Ordinarily we should render the contents of the type alias, but there's one situation where we shouldn't show anything: where the type alias includes one or more private tag union literals. For example:
## This is a string
Str : [ @Str ]

...should render as :
## This is a string
Str

Another example:
## This is a Foo
Foo :
    {
        stuff : I64,
        thing : [ @Str ],
    }

...should render as :
## This is a thing
Foo

...because it contains a private tag union literal somewhere in it. (Note that we shouldn't follow aliases when considering this; if the above example had Str instead of [ @Str ] then we would have instead rendered the entire type! It's only when there's a private tag union literal that we hide everything.)
This should render the entire type alias, because it contains no private tag union literals:
## This is a Foo
Foo :
    {
        stuff : I64,
        thing : [ Str ],
    }

Aliases show in docs now. Here's a random type example:

Source: https://github.com/roc-lang/roc/blob/b7c2cb084e15a56320e652ad3c77fdb8262bc1a4/crates/compiler/builtins/roc/Decode.roc#L53
Opaque types are shown but without their definitions.
Interestingly, the Str type still isn't in the Str docs, because it's not actually defined in https://github.com/roc-lang/roc/blob/b7c2cb084e15a56320e652ad3c77fdb8262bc1a4/crates/compiler/builtins/roc/Str.roc
I'm not sure if every case listed above is done as described, but this issue is 3 years old, so if there are cases that should be improved, they should be written up in a new issue.


An extra Powershell window pops when the Shell clicked.

Describe the bug
I can't get in container. Powershell pops when the Shell clicked. The command like 'kubectl --kubeconfig config exec' doesn't execute.
To Reproduce
Steps to reproduce the behavior:

Go to 'Pods'
Choose any pod
Click on 'Shell'
Powershell pops

Expected behavior
Powershell doesn't pop and I get in container.
Screenshots

Environment (please complete the following information):

Lens Version: 3.5.1
OS: Windows 10.0.18363.959 pro
Installation method (e.g. snap or AppImage in Linux):  install by exe files

Logs:

Kubeconfig:
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: certificate-authority-data
    server: https://server
  name: kubernetes-admin-name
contexts:
- context:
    cluster: kubernetes-admin-name
    namespace: namespace
    user: user
  name: name
current-context: admin-context
kind: Config
preferences: {}
users:
- name: name
  user:
    token: token

I had tried to close the Powershell and rename the Powershell directroy, but still can't get in the container.

When you open a pod shell, Lens will open Powershell in embedded terminal and execute kubectl exec command in the shell. So it's expected to see Powershell, but do you see kubectl exec ... command appearing in the shell?

Oh...now I got it, you actually see extra powershell window?

When you open a pod shell, Lens will open Powershell in embedded terminal and execute kubectl exec command in the shell. So it's expected to see Powershell, but do you see kubectl exec ... command appearing in the shell?

I can't see any kubectl exec ... command.
The extra powershell window display nothing about kubectl exec ....
The embedded terminal display 'Connecting ...'.

Oh...now I got it, you actually see extra powershell window?

Yes, an extra powershell window was poped when I click on the shell.

I am facing the same issue in Lens 5.2.7 ion Windows 10 Pro with an external  powershell window popping up and no kubectl exec ... command.
And if I try to type manually the kubectl exec command:
kubectl exec -i -t -n skyasd-922-staging skyasd-dd65bc849-7vwbr -c skyasd "--" sh -c "clear; (bash || ash || sh)"
I get the following error:
panic: Invalid standard handle identifier:<PHONE_NUMBER>

goroutine 1 [running]:
k8s.io/kubernetes/vendor/github.com/Azure/go-ansiterm/winterm.GetStdFile(0xfffffff6, 0x58, 0xf)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/Azure/go-ansiterm/winterm/ansi.go:173 +0x1f6
k8s.io/kubernetes/vendor/github.com/moby/term/windows.NewAnsiReader(0xfffffff6, 0xc00000000f, 0x2591240)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/moby/term/windows/ansi_reader.go:34 +0x36
k8s.io/kubernetes/vendor/github.com/moby/term.StdStreams(0x258f5c0, 0xc000006010, 0x258f5e0, 0xc000006018, 0x0, 0x0)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/moby/term/term_windows.go:75 +0x1f8
k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/exec.(*StreamOptions).SetupTTY(0xc00070a640, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/exec/exec.go:273 +0x13d
k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/exec.(*ExecOptions).Run(0xc00070a640, 0x0, 0x2410938)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/exec/exec.go:331 +0x23f
k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/exec.NewCmdExec.func1(0xc000694dc0, 0xc000822840, 0x4, 0xb)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/exec/exec.go:95 +0x11a
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute(0xc000694dc0, 0xc0008226e0, 0xb, 0xb, 0xc000694dc0, 0xc0008226e0)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:854 +0x2c2
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc00045adc0, 0xc00004c0c0, 0xc000142000, 0xd)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:958 +0x375
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute(...)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:895
main.main()
        _output/dockerized/go/src/k8s.io/kubernetes/cmd/kubectl/kubectl.go:49 +0x234

After days seraching for a solution to this issue I finally found that this is linked to an option of the Windows Console host.
In order to solve the problem, open the menu of the external console window which has opened and select Properties.
In the properties dialog, at the bottom of the Options tab uncheck the last option Use the inherited console (Utiliser la console héritée in French in the screenshot below).

Then close the console and open a new tab in Lens, it should open inside Lens.


Let holobarriers be climbable with alt. action

Fix a typo, too.
:cl:

fix: Holobarriers can be climbed like tables with the alternate activate entity in world action.

Why? They are barriers that's why they aren't climbable.

They are already climbable. This commit makes them climbable with the action instead of the context menu only.

Why? They are barriers that's why they aren't climbable.

They are already climbable. This commit makes them climbable with the action instead of the context menu only.

Oh sorry. I thought they weren't. lol