Farming Policy attached to farm should migrate existing node policies

When a farming policy is attached to a farm, only new nodes receive this policy. We also want to migrate all existing nodes to this new policy.

needs https://github.com/threefoldtech/tfchain/issues/405

Firstly, i created a farming policy Test_Farming_policy_1

then i voted on the proposal from the dashboard and waited until it expired.

the i got the proposal index to close it

and the policy was created successfully.

Then i repeated the whole process to attach the policy to farm 5 on devnet.

The policy was successfully attached to the farm

but the farming policy of the only node that belongs to this farm (node 38) was not updated.

Looks like your node is not in NodesByFarmID storage map, this is why this Node didn't get the proper farming policy.
@mohamedamer453  When did you boot this node into this farm?

Unfortunately i don't have access to this node so i don't really know when it was booted to the farm, but from the dashboard  i can see that the node was first booted on Jul 03 2022

i'll check if i can get access to another node that's booted recently or one that appears in NodesByFarmID

I have no clue why it wasn't inserted into this NodesByFarmID storage map. Was this node linked to another farm previously?

i'm not sure but i think it might have been booted before on testnet not sure if it was linked to another farm or not.

I think there is an issue with this NodesByFarmID storage map migration that happened on devnet, investigating now.

Other thing that might be considered
When a farming policy is attached to a farm, existing nodes don t necessarily migrate to new policy in those cases:

when existing node has a custom/non-default (default = false) farming policy
when new farming policy limits is reach in terms of (cu, su, end or nodeCount) it gets a default policy

Verified on devnet.
i created a new farming policy 5

and attached it to farm 5 successfully

and this time the nodes' farmingPolicyId was also updated to 5 instead of the default policy.

tfgridModule.nodes: Option<TfchainSupportNode>
{
  version: 5
  id: 38
  farmId: 5
  twinId: 149
  resources: {
    hru: 1,073,741,824,000
    sru: 1,610,612,736,000
    cru: 4
    mru: 4,127,178,752
  }
  location: {
    longitude: 31.3844
    latitude: 31.0371
  }
  country: Egypt
  city: Al Mansurah
  publicConfig: {
    ip4: {
      ip: <IP_ADDRESS>/24
      gw: <IP_ADDRESS>
    }
    ip6: {
      ip: 2001:db8:3333:4444:5555:6666:7777:8888/64
      gw: 2001:db8:3333:4444:5555:6666:7777:8888
    }
    domain: null
  }
  created: 1,656,849,612
  farmingPolicyId: 5
  interfaces: [
    {
      name: zos
      mac: 54:87:b8:17:9c:f1
      ips: [
        <IP_ADDRESS>
      ]
    }
  ]
  certification: Diy
  secureBoot: false
  virtualized: true
  serialNumber: Not Specified
  connectionPrice: 80
}

However the farmingPolicyId is still 1 when i query the node from graphql or grid_proxy

Will transfer this issue to graphql


BUG:: RyzenAdj can crash the app

Applying TDP too quickly to Ryzen APU's has a chance to crash the whole application. Log does leave an error. This is a known issue, but previous mitigations aren't effect enough.
I should also mention that it seems to crash even when only applying a single TDP profile, but this crash is a lot more rare. Edit: this seems to be related to applying profiles while the system is under high CPU/GPU usage.

I think we sorted this one out on discord? Closing


error in documentation - Dockerfile

Dockerfile line 3 should be "bin\Release" .
without the double quotes, it gives the following error
GetFileAttributesEx binRelease: The system cannot find the file specified

Thank you for catching this @nambisan! This could definitely trip up users. Fix will soon be on Docker Hub.


Implement Name Resolution as of TR13§3.7

the binding generated using "nameResolution.skill" can not be compiled using the current implementation strategy
proper treatment of shadowing is rather tricky (in the API)

wont fix, as the new TR will rule this illegal anyway


Has anyone figured how to get labels on the outside of a doughnut?

So I am trying to figure out how to get labels on the outside of a doughnut.
I stumbled across another project from emn178 (https://github.com/emn178/Chart.PieceLabel.js) that seems to do it, but I do not know how to get it to work with angular2-chartjs.
Any ideas?

here is an example.
https://github.com/emn178/angular2-chartjs-sample/blob/master/src/app/app.module.ts#L4
change to
import 'chart.piecelabel.js';

this should also answer your the other question #39
just change to your custom register plugin

Thanks, that worked! For the outer labels at least. Do you have a project for putting labels in the middle of a doughnut?

@DanaEpp @vvsraju04
https://github.com/ciprianciurea/chartjs-plugin-doughnutlabel


mean coverage

include in the status report the mean coverage in addition to the coverage at 80% of targets?
check '/home/deya/Desktop/coverage/mean_coverage/Untitled.ipynb' for more details

/home/deya/Desktop/coverage/mean_coverage_Nextseq'


Clarify suggested usage pattern for package

Currently when using package as noted in the README there are a couple odd behaviors that make it unclear how package is supposed to actually be used.

Package removes package itself from node_modules, requiring a new npm install before each build
npx also defaults to the instance of node that is now placed into node_modules/.bin, causing package to throw an error on subsequent builds. Deleting node_modules/bin solves this

It feels like the way that package wants to be used is to copy the entire project (including node_modules and package.json) into a new directory and build from there, but that's not made clear in the readme--and is also quite laborious to do manually. An example package.json entry that does this copying and removing would go a long way without adding any complexity to package.

Hi @aaronsantiago,
Thanks for reaching out.
I added the following note to the documentation. I hope that addresses your concern.

Note: Running this command has some side-effects, for example, removing development dependencies and copying the Node.js executable into node_modules/.bin/. This tool has been designed to run in a build server, for example, GitHub Actions. If you run it locally, then you may want to copy the project directory to a different location and run npx package on the copy.


Get Networking setup working with Raspbian Jessie Lite

Some things have changed: see https://wiki.archlinux.org/index.php/dhcpcd#Static_profile

See related blog post: http://www.jeffgeerling.com/blog/2016/setting-static-ip-address-raspbian-jessie-lite-on-raspberry-pi


pre-deploy pull, new login mechanism and pkg cli updates

Changes to support pre-deploy pull, authenticate with the browser and fixes / optimizations to the packaged CLI
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

We need the Amplify App ID across the project rather than repeatedly extracting it from the meta, we can make it a function to do that.


0.6 compatibility

Can someone run tests on it?

@mmalecki  - Thanks for opening this.
We'll get you an account on rackspace soon so you can run tests like this yourself.

@indexzero I'm using v0.5.9 as my "main" node - it's installed in /usr/bin.
For switching to previous versions I use nvm or nave, they're both really nice (haven't used n yet). Only difference is that nave opens up a subshell (so when you're done with some node version you can just ^D) and nvm modifies environment variables (to clear things up you need to nvm deactivate).
nave is easier to start with. You just sudo npm install -g nave, nave install <version> and nave use 0.4.12.
To start with nvm you have to source it somewhere, for example in your .bashrc.
Remember to export JOBS=<number-of-cores> before you do anything - compilation using one core takes ages.
Also, please note that when running things using sudo, your main node installation will be used. For example, this is the case when running haibu-carapace tests.

This is ready for merge. Can someone review or should I just merge it?
Also, it would be awesome to have this npm published.

Nudge on this as I need it as well.
Thanks

@mmalecki This looks fine. It's just require.paths and assert.lengthOf. Merge at will.

@mmalecki actually I'll do this quickly and publish it to npm. It's backwards compatible with 0.4.

Done. Published to npm as<EMAIL_ADDRESS>


Add membership flow to first run

Ask before reward approval, after channel selection. If they sign up, they'll get reward approved, so re-check user/me. Would be nice to smooth out the flow with the whole CC adding situation.


translate errno=-4094 errors to "no-such-device" on Windows

When an application attempts to open a non-existent path such as //foo/bar/baz on Windows, Node generates an error of the form:
{
  errno: -4094,
  syscall: 'open',
  code: 'UNKNOWN',
  path: '//foo/bar/baz'
}

Prior to this commit, that error would be re-thrown, causing Wasm execution to trap.  Now we convert it to a "no-such-device" error instead.

Thanks for merging this, @guybedford.  Is there a chance we could publish a new release of the shim with this fix soonish?  That would help unblock https://github.com/dotnet/runtimelab/pull/2614, which is where I encountered this issue.

Sure, I've pushed a 0.16.3.


Request: Enhance "transforms" plugins

@enhance/ssr allows for script and css transformations, would it be possible to plug in custom transforms alongside the standard ones provided by arc-plugin-enhance here https://github.com/enhance-dev/arc-plugin-enhance/blob/f6dcdd406b60c7b9c8310bb93c6bfb1fff00f20f/src/http/any-catchall/router.mjs#L132-L141

No idea how this would look for a plugin author...
So far Enhance has intentionally (wisely!) avoided an explicit configuration file. Maybe transforms could be added via a file-based API?
plugins/transforms/css/index.mjs
I'm not sold, but it's a thought.
I don't think Enhance needs these sort of plugins, but it would open up some powerful possibilities. On the other hand it could have a negative performance impact and lead to some plugin author/consumer anti-patterns and footguns. On the other other hand, can't save everyone from themselves 😬

This is a great idea and has been requested previously.
The technical hurdle we ran into was knowing when to run the transform since some transforms would be undone by others.
I had planned to loop back around on this at a later date in order to gather some specifications for concrete use cased people wanted this feature for so I could write better tests.


Async Rust in libindy

Hi @jovfer I know this is fairly old PR but this looks pretty cool, wondering whether this would pass on rerun, now that CI/CD stuff has been sorted out.

@Patrik-Stas Evernym has more changes atop it in the internal fork. And we are planning to publish our changes. Hopefully, it would be the same licence and in the nearest future, so it would be possible to merge libindy async from there instead of fixing this PR.
FYI @esplinr

@jovfer wow that would be really amazing! Honestly I think if you manage to pull off this contribution, it can substantially change the future of libindy - not only because by itself it's a great contribution, but especially because it can drive further community engagement. Imo async libindy is the main factor whether Aries frameworks stay with libindy or migrate to indy-shared-rs and whether community contributions in general continue here or move over to indy-shared-rs).

I did not realize just how much awesome this PR is before.
This is not only gonna improve performance by a magnitude, but also creates an opportunity to expose async, Rust native API from libindy crate itself. If the individual methods of executors (PoolCommandExecutor, WalletCommandExecutor) are changed to pub, eg. method open in PoolCommandExecutor,  you could then look at the commands layer as native Rust API, and libindy could be published and consumed via crates.io.
This would in particular greatly benefit aries-vcx library, as we could call libindy directly instead of via C ABI - which would give us lot more flexibility and make maintenance a lot more easy. Definitely incentivizing us to stay with libindy.
It also gives potential for other Rust project to build on top of libindy and therefore find / incentivize new Rust developers.
For proof of concept, I have:

took this PR and made a few modifications (exposed more commands module from the crate, made some methods pub) https://github.com/Patrik-Stas/indy-sdk/pull/2
Created small project trying to consume that version of libindy as crate dependency. And it works! https://github.com/Patrik-Stas/consume-indy-crate/blob/master/src/libindy_async.rs

Soo now I am really excited and want to get this merged! :-) Happy to help with this.

Any status on when this PR would get merged? Excited for this PR to solve the blocking nature of the wallet APIs.

There is no plan at Evernym to update this PR. But our own version of IndySDK is available at https://gitlab.com/evernym/verity/vdr-tools under Apache 2.0 Licenses and main branch there is actually the evolved version of this PR/branch. So if Hyperledger community is interesting in such changes there are no license concerns to bring some commits from Evernym repo


VFITex dataset is not available.

Hi,
First of all, thank you so much for your well-developed research of VFI.
I'm raising an issue because I can't access your VFITex dataset.
When I try to download it, the message pops up and says "the link has expired".
Can I access your VFITex?
Thank you!

Hi,
Thank you very much for your kind words, and apologies for the inconvenience. I have updated the link and you should now be able to access it.
Many thanks.

Hi,
Thank you very much for your kind words, and apologies for the inconvenience. I have updated the link and you should now be able to access it.
Many thanks.

Thanks for your quick answer and fix!


Bug: @html-eslint/indent

"indent" rule shows that there should be indentation when it's the first line in HTML file:

After letting ESLint fix the problem, it goes this weird way:

Maybe this thing happens because the rule expects an "html" tag in the beginning for the file, but it's an Angular template and this file should be considered as correct one. For index.html, which does have "html" tag in the beginning, the rule works fine.

@alexei-vedder Thanks for the reporting. I can reproduce it (demo) I'll fix it as soon.

Thanks a lot for the fix and for the plugin in general!


Katerina site

Hi Katerina,
These changes are for your own personal site (which should stay in your repository, not in mine), so I'm not going to merge these.


oom caused after use #234's statistics record code

https://github.com/moka-rs/moka/pull/234

Hi. Thank you for reporting the issue. Can you please provide more information to help us investigate further?

What is the moka version?
What is the cache implementation? sync::Cache, sync::SegmentedCache, or future::Cache?
Is your eviction listener code exactly same to the one in #234?
What is the max_capacity of the cache?
If you make the max_capacity smaller, does the issue still happen?
What is the average size of the value stored in the cache? (Rough estimate is fine)
What is the write rate to the cache? (Number of writes per second. Rough number is fine)

Are you doing heavy writes? (e.g. millions writes per second, like benchmarking)

Hi. Thank you for reporting the issue. Can you please provide more information to help us investigate further?

What is the moka version?

What is the cache implementation? sync::Cache, sync::SegmentedCache, or future::Cache?

Is your eviction listener code exactly same to the one in Statistics for metrics #234?

What is the max_capacity of the cache?

If you make the max_capacity smaller, does the issue still happen?

What is the average size of the value stored in the cache? (Rough estimate is fine)

What is the write rate to the cache? (Number of writes per second. Rough number is fine)

Are you doing heavy writes? (e.g. millions writes per second, like benchmarking)

0.11.2
sync::SegmentedCache / I tried sync::Cache, same oom
exactly same as #234
still happen, I tried to set max_capacity just 128
20B
1000 QPS

@itherunder — Thank you for the info. It was very helpful! I believe I found the root cause of the bug, and the following PR will fix it:

#295

src/sync_base/key_lock.rs#L33-R33

When you have chance, please try it to see if the OOM is fixed:
Cargo.toml
[dependencies]
moka = { git = "https://github.com/moka-rs/moka.git", branch = "fix-eviction-listener-key-lock-v011" }

I will apply the fix to Moka v0.11.x, v0.10.x and v0.9.x, and hopefully we can release them in this weekend.

I will apply the fix to Moka v0.11.x, v0.10.x and v0.9.x, and hopefully we can release them in this weekend.

I just published v0.11.3, v0.10.4 and v0.9.9 to crates.io.
Please reopen this issue if the OOM still happens with v0.11.3.


Implement non-admin cluster status

Status checks for a non-admin that need to be conveyed:

Cluster has at least one associated MigToken available that is "Ready"
The MigCluster itself is "Ready"


Unhandled rejection StatusCodeError: 405 on using WCT Structured data testing

Unhandled rejection StatusCodeError: 405 - "\n\n  \n  <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">\n  Error 405 (Method Not Allowed)!!1\n  \n  \n  405. That’s an error.\n  The request method POST is inappropriate for the URL /structured-data/testing-tool/u/0/validate.  That’s all we know.\n"
at new StatusCodeError (/home/ttn/WebstormProjects/website/node_modules/request-promise-core/lib/errors.js:32:15)
at Request.plumbing.callback (/home/ttn/WebstormProjects/website/node_modules/request-promise-core/lib/plumbing.js:104:33)
at Request.RP$callback [as _callback] (/home/ttn/WebstormProjects/website/node_modules/request-promise-core/lib/plumbing.js:46:31)
at Request.self.callback (/home/ttn/WebstormProjects/website/node_modules/request/request.js:186:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:191:7)
at Request. (/home/ttn/WebstormProjects/website/node_modules/request/request.js:1163:10)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at IncomingMessage. (/home/ttn/WebstormProjects/website/node_modules/request/request.js:1085:12)
at IncomingMessage.g (events.js:292:16)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)

hey... I've not looked into this in a while as it was a bit of a hacked concept. @kkashyap1707
Did you have a look into it?


Incorrectly transforming the case in properties keys in event and custom-property logs

What App Center service does this affect?
App Center Analytics
Describe the bug
Currently App Center incorrectly transforms the properties keys in event and custom-property logs.
This can be seen in the pipeline:  LogFlow, Export.
This mainly affects when customers are using Export.
Few examples:
•	Test -> test
•	TEST -> tEST
Expected behavior
The case should not be changed and should be left as is.

For customers affected by this issue, The casing issue has been fixed. We are providing 90 days to ensure that you have enough time to validate your queries.
Please test and adjust your existing queries accordingly. If you run into issue, please contact us through our support team (blue chat bubble on the bottom right).

I'm seeing a similar issue where custom properties I've set are changed to pageName -> PageName, loadTime -> LoadTime in the logs.v1.data files between Aug 13 and Aug 14 and returned to normal after.


Webp format support

For webp support in php-imagemagick:
https://gauntface.com/blog/2014/09/02/webp-support-with-imagemagick-and-php
Build test:
https://travis-ci.org/1271/image/builds/221240037

Bump, this looks like a cool addition - is there anything blocking its merge?

Included in baeeac5125b7015f3fad0f9333b5e33585430f38 and 961c58a9951acd688b9a2d17ff24ac9bcb199f84.

great


Add User session utility functions

User session data will be stored in local storage. Instead of us always calling localStorage class to get a value, its better to have a utility class that abstracts this work.

@valasaladinesh once this is done, I think you can implement the redirect to login feature.


[Feat]: I want  add some extention to search feature

What feature?
I have an idea to improve the search feature even more.
Present in skills criteria we can search only one skill at a time. so we can search for users with multiple skills at a time with a single input box
I can do this feature. I have already implemented it in my e-commerce website so users can filter products in different categories simultaneously.
please assign this issue to me under gssoc-ext for
Add screenshots

so below we cannot see users when I search for multiple skills

Please assign it to me so that I can contribute to DevDisplay.
I will follow the Rules and code of Conduct.
Add the labels Gssoc-ext and Hacktoberfest.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Before raising any issue, please add you profile here and be sure to star the DevDisplay GitHub Repository. 🌟
💌 This is a mandatory step for all contributors. & It's is the first priority of contribution in DevDisplay 💌
🚀 We look forward to your contribution once these steps are completed. 🚀
Thanks 👍🏻

I have completed the feature, I have tested it and it is working well, I have also created the pull request #414.
could please review the code give me feedback and also add the badges of gssoc-ext, hacktoberfest2024, level2


Updating engines requirement

Relates to https://github.com/cibernox/ember-native-dom-helpers/issues/52
Fancy features are used in this repo, so requires node 6+

We should leave this as >= 4.  The warning about block scoping is instructing you to add 'use strict'; to the top of the index.js, that should resolve it...

Since I use newer nodes I wasn't aware that let required strict mode.

Thanks!


Relative paths are not handled properly in the kubeconfig (at least for certificate-authority).

Description
Relative paths are not handled properly in the kubeconfig (at least for certificate-authority).

File and path references in a kubeconfig file are relative to the location of the kubeconfig file. File references on the command line are relative to the current working directory. In $HOME/.kube/config, relative paths are stored relatively, and absolute paths are stored absolutely. -- https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/#file-references

@marians identified an issue at https://github.com/kinvolk/headlamp/issues/112#issuecomment-762953053

I identified another reason that caused headlamp to exit. In my kubeconfig I had cluster entries with relative path in certificate-authority. The path was relative from my ~/.kube directory. For kubectl that seems to work, but the headlamp backend exits with this error:

*** Headlamp Server ***
API Routers:
2021/01/19 17:15:57 Failed to add certificate:open certs/gs-gollum/k8s-ca.crt: no such file or directory
After I change this to an absolute path, the backend seems to come up.

Impact
Configuration is broken where people rely on the documented relative path behaviour.
Environment and steps to reproduce
echo "no" > ~/.kube/ca.crt
Add the line to ~/.kube/ca.crt
    certificate-authority: ca.crt

The error is:
2021/01/22 19:18:15 Failed to add certificate:open ca.crt: no such file or directory

Expected behavior
It should read the ca.crt file in the config folder.

The issue seems to be here: headlamp/backend/cmd/cluster.go
func (c *Cluster) getCAData() []byte {
	if c.config.CertificateAuthority != "" {
		pemBytes, err := ioutil.ReadFile(c.config.CertificateAuthority)
		if err == nil {
			return pemBytes
		}

		log.Fatal("Failed to add certificate:", err)
	}

	if caData := c.config.CertificateAuthorityData; len(caData) > 0 {
		return caData
	}

	return nil
}

The issue seems to be here: headlamp/backend/cmd/cluster.go
func (c *Cluster) getCAData() []byte {
	if c.config.CertificateAuthority != "" {
		pemBytes, err := ioutil.ReadFile(c.config.CertificateAuthority)
		if err == nil {
			return pemBytes
		}

		log.Fatal("Failed to add certificate:", err)
	}

	if caData := c.config.CertificateAuthorityData; len(caData) > 0 {
		return caData
	}

	return nil
}


Cloning into bare git repo fails

It is currently not possible to add a repo that is bare and dont have any refs on the remote side. It fails out with the error fatal: Remote branch master not found in upstream origin
Investigate if it is possible to determine if the repo is bare or not. Otherwise a new solution has to be thought up on how to deal with this case as it must be supported.

DEBUG: Repo update - all
Are you sure you want to update the following repos "myrepo"
(y/n) << y
Traceback (most recent call last):
  File "/home/nn/code/foobar/sgit/sgit/core.py", line 260, in update
    branch=revision['branch'],
  File "/home/nn/code/foobar/sgit/.venv/lib/python3.6/site-packages/git/repo/base.py", line 1017, in clone_from
    return cls._clone(git, url, to_path, GitCmdObjectDB, progress, multi_options, **kwargs)
  File "/home/nn/code/foobar/sgit/.venv/lib/python3.6/site-packages/git/repo/base.py", line 958, in _clone
    finalize_process(proc, stderr=stderr)
  File "/home/nn/code/foobar/sgit/.venv/lib/python3.6/site-packages/git/util.py", line 328, in finalize_process
    proc.wait(**kwargs)
  File "/home/nn/code/foobar/sgit/.venv/lib/python3.6/site-packages/git/cmd.py", line 408, in wait
    raise GitCommandError(self.args, status, errstr)
git.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --branch=master -v git@gitlab.com:foobar/myrepo.git /home/nn/code/foobar/sysrepo/myrepo
  stderr: 'Cloning into '/home/nn/code/foobar/sysrepo/myrepo'...
fatal: Remote branch master not found in upstream origin
fatal: the remote end hung up unexpectedly
'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/nn/code/foobar/sgit/sgit/cli.py", line 185, in cli_entrypoint
    exit_code = run(cli_args, sub_args)
  File "/home/nn/code/foobar/sgit/sgit/cli.py", line 171, in run
    retcode = core.update(repo)
  File "/home/nn/code/foobar/sgit/sgit/core.py", line 264, in update
    raise SgitException(f'Clone "{name}" failed, exception: {e}')
sgit.exceptions.SgitException: Clone "myrepo" failed, exception: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --branch=master -v git@gitlab.com:foobar/myrepo.git /home/nn/code/foobar/sysrepo/myrepo
  stderr: 'Cloning into '/home/nn/code/foobar/sysrepo/myrepo'...
fatal: Remote branch master not found in upstream origin
fatal: the remote end hung up unexpectedly
'
> /home/nn/code/foobar/sgit/sgit/core.py(264)update()
-> raise SgitException(f'Clone "{name}" failed, exception: {e}')

With the following .sgit.yml file
repos:
  bare:
    clone-url: git@gitlab.com:dynamist/sgit-bare-repo.git
    revision:
      branch: master

you will get the following output from the initial update and future updates
(sgit) ➜  sgit git:(master) ✗ DEBUG=1 PDB=1 sgit -y update
DEBUG: Repo update - None
Are you sure you want to update the following repos "bare"
INFO: Automatically answer yes to question
Successfully cloned into bare git repo "bare" from remote server

(sgit) ➜  sgit git:(master) ✗ sgit update
DEBUG: Repo update - None
Are you sure you want to update the following repos "bare"
(y/n) << y
TODO: Parse for any changes...
DEBUG: Handling branch update case
Exception type : BadName
EXCEPTION MESSAGE: Ref 'origin/master' did not resolve to an object
To get more detailed exception set environment variable 'DEBUG=1'
To PDB debug set environment variable 'PDB=1'


Add chromium base port

Please add port for Chromium Base, thank goodness.
URL at:
https://chromium.googlesource.com/chromium/src/base/

It doesn't supported for cmake, i try to write a CMakeLists.txt for it, but always failed, SOS!
各位大大请支持一下Chrome Base库，我试过自己写cmake文件，可总是失败，那个gyp文件不好读，总是翻译失败，想把chromium base作为基础库，用cmake链接

@iHuahua Any chrome library needs tool depot-tools, we need to add it first.

这段时间会尝试添加这个工具。

@JackBoosY
why not add? almost all capacious google projects are tied to GYP or newer GN

Related: #6184.

maybe for starters add depot-tools
and then everything else

@JackBoosY @Voskrese thank for reply. I'm waiting for u. If something i can do, please call me.

@iHuahua In fact, I really need your help, please see here.

@iHuahua In fact, I really need your help, please see here.

抱歉，手误关了，最近比较忙，没时间上来看消息，我找个时间尝试看看能不能解决这个问题

@JackBoosY
Sorry for delayed participation to this discussion. Now I'm manually building Chromium for Windows by myself (since 3 days ago, clang + ninja), to learn how to do that, and my slow machine is still running.
If the escaping of the argument (--args='cc=... cxx=...') to "gn" is broken by CMake, my idea is "how about using a Python script to invoke gn?". I'm afraid that some experts might have tried such already, and if it's already tried and known to be "does not work", please let me know.

I have another question, how to retrieve the source code? If I'm understanding current situation correctly, Google no longer release the source code tarball, they instruct their special tools to download the source of Chromium and related libraries. In my case, it takes so long time (20 hours or so). Also, it's hard to keep the availability of the past sources.
In the case of Ubuntu and other GNU/Linux distributions, they keep the source tarball in their package distribution system to stabilize this issue. Should we do like that?

@mpsuzuki In #8963, first we will download depot-tools, and download the basic source code, call the sync command to download the latest code, and use gn to build the port. However, I found that the entire chromium is built no matter which port is built, and it is not clear to me what went wrong, using cmake to pass in compilation options is also a challenge.

@iHuahua In fact, I really need your help, please see here.

亲，我自己改gn脚本把chromium base部分提取出来了，但是我不知道怎么接到cmake里

@JackBoosY sorry，这么久才来回复。我自己改脚本和依赖通过python把chromium base部分提取出来了，但是我不知道怎么接到vcpkg里，需要的话我可以我改的脚本共享给你。目前是通过删除deps/.gn等方式减少下载内容数据，已经调通了windows/MacOS/linux/android/iOS，脚本支持3个桌面平台，安卓和iOS是另外单写的两个脚本，只是发现里面还指定libcxx，这个需要重写cmake的时候注意，不知道是否是由于内存优化模块导致的强制依赖

@iHuahua 你可以先提一个空的CONTROL和portfile.cmake，顺带把脚本传上去，我帮你修改。

@iHuahua 你可以先提一个空的CONTROL和portfile.cmake，顺带把脚本传上去，我帮你修改。

好的，我试试

@JackBoosY https://github.com/microsoft/vcpkg/pull/12280
亲，有空看看怎么弄


Ecosystem issues and a corresponding dev

There are three tickets related to the ecosystem that are currently labeled with fallback (a label for tickets that don't fall into any other existing category):

https://github.com/perl6/problem-solving/issues/19
https://github.com/perl6/problem-solving/issues/26
https://github.com/perl6/problem-solving/issues/39

As I mentioned before, I think we need a new label ecosystem as well as a dev who will be looking after the tickets and driving the progress in that area (current list).
Personally I think @ugexe is the best candidate, and I highly recommend them to apply. Meanwhile others can also do so if they feel strongly about it.

I will do it. But I'm also busy and lazy and thus don't know when I'll feel like writing up an application. If someone wants to do that for me it will leave me more time for digesting and responding to the issues.

@ugexe Good! Can you file a PR adding yourself to the list? (example). It doesn't mean that you should do all the work, rather that there's a defined person who is knowledgeable enough to help and guide others when needed. If there are any specific things (e.g. projects) you want to get done but can't due to your time restrictions, please file separate tickets here. Either someone will pick it up, or we'd at least have a nice list of things to work on for the next GSoC.
After the PR is merged we'd be able to label a few tickets appropriately (I prefer not to have orphaned labels).


You can toggle other peoples gun stocks

I think this is intended so you can like, take armbraces off people

I think this is intended so you can like, take armbraces off people

Correct.


Theming v2 message reactions react

🎯 Goal
Add stream-chat-react specific styles for theming V2 related to message reactions.

:tada: This PR is included in version 3.0.0-theming2.1 :tada:
The release is available on:

npm package (@theming2 dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[BugFix][Cherry-pick] fix invalid partition predicate bug for 3.0 (#19373)

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #19352
Problem Summary(Required) ：

fix invalid partition predicate bug
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

run all

@Mergify rebase


Compiler complains when pagecustomization reuses the ID of a pageextension object

If you declare a pageextension object with id 70000001 and then a pagecustomization object with id 70000001, the compiler will complain.
These should not be intermixed, and the IDs should be reusable between different object types.
There used to be a bug that you couldn't declare a pageextension with the ID of a page declared in the same extension, or a tableextension with the ID of a table declared in the same extension, but this was fixed in (I think) June release.
This is the same kind of issue, and it should also be allowed to use the same ID for customizations and extensions.
This is especially important because profiles are expected to deliver a lot of page customizations, there will always be more page customizations than there are page extensions, and we should not be forced to use larger object ranges to support large volume of customization objects.

Page Customizations won't have IDs in the next update


Add support for traffic analysis

Would be nice if we could add some analysis/intelligence/interpretation/guidance on flagged records on top of scanning. There can occasionally be an innocuous record that is flagged (correctly due to IP origin), but isn't indicative of any user actions.
For example we recently had a single record flagged, that was due to a SignalR ping getting through in the brief window before the VPN connection was made. It should have been (and was) flagged, but in scenarios like this it would be awesome if additional info could be provided, i.e. user jane had illegal access from <IP_ADDRESS> at foo o'clock, but it was only single isolated record driven by SignalR, not a direct user action.
@marjorienorm @beverts312  thoughts?

After some thought, discussion, and using the scan extension for while.. I am going to close this.
Ultimately, we wanted this extension to flag records when they came from an unknown IP address so those records could be investigated by a human. The extension shouldn't be in the business of attempting to interpret those records based on fields (like the useragent) that can be spoofed.
Adding additional configuration features, for example like #12 to filter on authentication mechanisms, will be a much better approach of reducing "false positives"


Using the "tpl" function in a template disallows any template functions with quotes

I've written a couple of different issues that show the key element of what our Helm process is doing.
This is a short excerpt from our "configmap.yaml":
apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ .Values.msname_wr }}-configs
  namespace: {{ .Values.kube_namespace }}
data:
{{ tpl (.Files.Glob "configs/*").AsConfig . | indent 2 }}

In this "configs" directory, we have several Java properties files, and those files also have "{{}}"" references, like this:
redis.cluster.config={{.Values.redisconfigspath}}/redis.properties

This works fine.  However, if we instead change this reference to use particular template filter functions, like "default", then we get errors from Helm, like (not sure of the exact wording right now):
Unexpected character: "\\\"
I narrowed this down to the fact that the result of that "tpl" function is a structure like this:
data:
    system.properties: "........

As opposed to, perhaps:
data:
    system.properties: |
        ...

It appears that when a template function that uses quotes is referenced inside a quoted value, something gets confused about escape characters, resulting in an unparseable string.
So, it's not clear to me whether it's possible to change that "tpl" invocation phrase so that it uses the multi-line format, but it seems like that would at least give us the ability to use template functions that use quotes. I also don't know if doing that would have any unexpected consequences.

Do you have an example that could reproduce the problem? I'm unsure of how something like default would cause a situation like this and a test situation would help figure that out.

I am now attempting to recreate this, but I'm having trouble getting it to go into "quote mode".  I tried with an almost empty directory of config files, with just two files with a few simple properties, and it consistently uses the multiline character ("|") instead of generating a single quoted line. It seems like some characteristic of the sample data makes it decide to render them as quoted strings.  Any idea what might be doing that?

I've managed to reduce this to a much smaller test case.  I think there still are some unnecessary files, but the zip file is only 16kb, so I think that's small enough, and you should be able to demonstrate curious behavior just by editing one file in the zip file and rerunning the test script.
This sample has a "cmdline" script. You run it to run the test case. When you run it without change, it should produce "output/idpchart/templates/k8s/configmap.yaml".  Right now, that looks like this:
---
# Source: idpchart/templates/k8s/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: checkoutms-blue-configs
  namespace: com-att-idp
data:
  application.properties: "# needs to exactly match with configmap name for applicationcontext refresh upon configmap edit.\nserver.tomcat.max-connections=10000 \n"

Notice that it rendered the "application.properties" file as a quoted string. That doesn't demonstrate the error I was seeing, but it would lead to it if I referenced a "default" template function in the file.
You'll want to find the "application.properties" file and copy the current contents outside of this tree, or simply be prepared to undo changes to the file.
The current contents of that file is this:
# needs to exactly match with configmap name for applicationcontext refresh upon configmap edit.
server.tomcat.max-connections=10000

If you remove the second line and then rerun the "cmdline", it will produce the "application.properties" entry in multiline mode, not quoted string. If you add the line back in and run it again, it will go back to a quoted string.
From this so far, you might think the issue has something to do with the size of the file.  It does not.  The way I got to this sample file was starting with the original "application.properties" file, which was a few hundred lines, and simply chopping off a block of lines at the end.  If it produced a multiline, I added the lines back and then removed a smaller set at the end.  I finally determined that it was that actual line, the setting of the "server.tomcat.max-connections" property, that puts it in quoted string mode.  I know that doesn't make any sense, I just know what I saw.  If I had that line in the file, no matter how large it was, it would produce a quoted string.  If I removed it, it would produce a multiline.
quotesTestCase.zip

The issue being highlighted here originally is with regards to the use of other helm functions inside a file being rendered using tpl.
I have added a very simple helm project to replicate this issue (see attachment)
The template configmap.yaml is using Files.Glob to read files in a config directory, to generate a configmap "data" element using AsConfig.
This is then passed into tpl so that we can replace helm variables in those config-files.
So in application.properties for example:
someKey={{ .Values.someKey }}

would get converted to :
someKey=someValue

However if we try to use the "default" function in the application.properties such as this:
someKey={{ .Values.someKey2 | default "someDefaultValue" }}

Then we get this error:
$ helm template tpl-with-default --debug
install.go:173: [debug] Original chart version: ""
install.go:190: [debug] CHART PATH: C:\opt\vscode-ws\helm-experiment\tpl-with-default

Error: template: tpl-with-default/templates/configmap.yaml:7:3: executing "tpl-with-default/templates/configmap.yaml" at <tpl (.Files.Glob "configs/*").AsConfig .>: error calling tpl: error during tpl function execution for "application.properties: \"# some comment about some key\\r\\nsomeKey={{ .Values.someKey2 | default \\\"someDefaultValue\\\" }}\"": parse error at (tpl-with-default/templates/configmap.yaml:1): unexpected "\\" in operand
helm.go:81: [debug] template: tpl-with-default/templates/configmap.yaml:7:3: executing "tpl-with-default/templates/configmap.yaml" at <tpl (.Files.Glob "configs/*").AsConfig .>: error calling tpl: error during tpl function execution for "application.properties: \"# some comment about some key\\r\\nsomeKey={{ .Values.someKey2 | default \\\"someDefaultValue\\\" }}\"": parse error at (tpl-with-default/templates/configmap.yaml:1): unexpected "\\" in operand

So the question is:
Does the tpl function only support variable replacement? OR does it also support all the other functions integrated into helm?
tpl-with-default-1.zip

Do to the following docs help provide any answers for you two?
https://helm.sh/docs/howto/charts_tips_and_tricks/#using-the-tpl-function
https://helm.sh/docs/chart_template_guide/named_templates/#declaring-and-using-templates-with-define-and-template
If all else fails, you can review the original PR to help determine its behaviour. It was introduced in https://github.com/helm/helm/pull/2350 - Helm 2.5.0, released in 2017.

And here's where it lives in pkg/engine today: https://github.com/helm/helm/blob/db4d20f3ad3ebbd8d17926e7a3cc7da7c177b52b/pkg/engine/engine.go#L127-L152

Thanks, we will review those.  I think we'll probably be heading towards a solution not using AsConfig, after we verify there are no unintended consequences.

AsConfig does a YAML conversion. YAML needs to deal with (escape) " in the string.

Just found this issue and wanted to ask for clarity here; rather than opening a net new issue (although I'm happy to if desired).
It appears that tpl does not support calling other helm functions such as default & required. Is this assumption correct?

It appears that tpl does not support calling other helm functions such as default & required. Is this assumption correct?

No, that’s incorrect—tpl supports all Helm functions. The issue described was not caused by tpl, but rather by File.AsConfig and the escaping of quotes (see details in the thread).


[docs] Fix links to dockerfiles

The master/ directory in these paths have been renamed to main/ in https://github.com/swiftlang/swift-docker/commit/f9be7230b6bb84f00abb680d494b1bffa39c5a72.

CC @shahmishal


Missing mp3-decoder / any kind of audio decoders in pure no-std rust

Currently, I'm unable to find any pure no-std audio decoders that I can use for the asnd part of ogc-rs library. Are there any good ones I'm not finding? In the case that there simply aren't any decoders yet, it would be a good idea to see if we can use the minimp3 library, or anything like it.

Hi)
For pure rust there https://github.com/Herschel/puremp3, not sure if it can be used for no-std.
For no-std minimp3 bindings there https://github.com/viriuwu/rmp3 .

Some very useful information on what kind of audio format asnd supports: https://wiibrew.org/wiki/Asndlib#Audio_Format. It seems like
we can either use the cross platform sox tool to convert various audio formats. "The primary audio format accepted by asndlib is 16-bit, 2-channel (stereo), big-endian RAW PCM.", and to convert we can use sox like so:
sox input.wav -t raw -b 16 --endian big -c 2 output.raw

Alternatively we can do this at runtime by for instance wrapping sox to be callable from Rust or decoding ourselves.


bug: Message Placement no working expected

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Messages always show on top-center only Placement.Top and Placement.Bottom working
Expected Behavior
Message position should to obey Placement property, I want it show on right-bottom, tryied Placement.BottomEnd and Placement.RightEnd it not working
Steps To Reproduce
Repo to reproduce
https://github.com/coddoge/bb-bug-reproduce/blob/main/MessageBugs1/Pages/Index.razor
<PackageReference Include="BootstrapBlazor" Version="7.9.1-beta04" />

@inject MessageService MessageService

Package version: @typeof(Message).Assembly.FullName

Message Position Check

<Message @ref="_message" Placement="Placement.RightEnd"></Message>

<Button OnClick="ShowMessage">Try</Button>

@code
{
    private Message? _message;

    private void ShowMessage()
    {
        MessageService.Show(new MessageOption()
        {
            Content = "Position?"
        },_message);
    }
}

Exceptions (if any)
No response
.NET Version
7.0.400-preview.23330.10
Anything else?
Mybe I should use Toast?

@coddoge Hi bro. the Message component only support Placement.Top or Placement.Bottom

@ArgoZhang Oh this is my mistake, document is well.
I will use Toast.


Removed TenantID from Subscriptions

Related https://github.com/Azure/azure-rest-api-specs/issues/1146
@tfitzmac @vivsriaus
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

I agree with what @mcardosos is doing here, removing a field that doesn't appear to be set, so a 👍 from me. But, I'd like it if the service team also signs off on the change.

I am not the right person to sign off on this PR. @ravbhatnagar - do you know who should review this?

@vivsriaus @tianoMs  - Can one you please review?

Looks good to me. We don't return tenantId in subscription responses.

LGTM

Thanks! :D

 https://github.com/Azure/azure-sdk-for-ruby/pull/764

 https://github.com/Azure/azure-sdk-for-python/pull/1109


initial commit

Got it. I'll add it and also add my 5th day TL as collaborator. Does that mean I need to create a new pull request?

Done.

Looks good!


created a new file

issue: #5

commands used
root@LAPTOP-EMH0HQHF:~/m3/FreshHat-Learning-Repository/submissions/adityaagg/week1# mkdir task4
root@LAPTOP-EMH0HQHF:~/m3/FreshHat-Learning-Repository/submissions/adityaagg/week1# cd task4/
root@LAPTOP-EMH0HQHF:~/m3/FreshHat-Learning-Repository/submissions/adityaagg/week1/task4# touch task4.txt

Hey @adityaagg4689
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @adityaagg4689
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


Implemented Session Encryption

Implemented Session Encryption for Unseal.

adding Chris to double check we used the direct API properly.


request: please open the wiki editing permission

as title

Hi, @ssfdust . Thanks for asking. However, foyer is not using github wiki. It is using a dedicated repo to manage documents with Docusaurus in https://github.com/foyer-rs/website . PR is acceptable there. 🙌
Thank you very much for your contribution. 🥰

Got it.


RuntimeError: result type Long can't be cast to the desired output type Bool

Hello,
I am trying your example and i have the following error :
PhySG-master\code\model\ray_tracing.py", line 265, in rootfind
while work_mask.any() & i < self.n_rootfind_steps:
RuntimeError: result type Long can't be cast to the desired output type Bool
Can you help?
Best regards

Change the work_mask.any() to work_mask.any().item() should do the trick I guess.


[MM-38325] Polished up some of the UI elements

Summary
Fixed up some of the UI elements as a few things were misaligned or needed some colours changed.
Ticket Link
https://mattermost.atlassian.net/browse/MM-38325
NONE

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/desktop/12945
https://circleci.com/gh/mattermost/desktop/12944
https://circleci.com/gh/mattermost/desktop/12942

@matthewbirtch Tried to cover everything listed in the tickets, these are my notes:

The dropdown icons that I fixed were the little drag handles and the plus button, the other ones all looked fine.
I did the alignment changes on the mention badges you requested, but it feels like they're sitting too low now.
I still can't really do anything about the number inside of the badge for the reasons you mentioned, I'm open to ideas about how to fix that if you or anyone else has an idea.
I'm pretty sure I updated the styles for the badges to be mostly the same now so they should be virtually identical.

Artifact links:
https://12945-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-setup-5.0.0-develop-win.exe
https://12944-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-mac-arm64.dmg
https://12944-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-mac-x64.dmg
https://12942-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-linux-ia32.tar.gz
https://12942-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-linux-x64.tar.gz

Nice work @devinbinnie. It's looking good

The dropdown icons that I fixed were the little drag handles and the plus button, the other ones all looked fine.

Hmm, this still looks a little off to me. If I measure it, the server icon and the drag icon are sitting 1px too low. The other elements in the row seem fine. The plus icon in the Add server row also seems to be 1px too low.

I did the alignment changes on the mention badges you requested, but it feels like they're sitting too low now.

I just played with this a bit in the inspector and the only way I could get the number to sit vertically centered is the change font-size: 9px instead of 10px. This actually seems to look better and because it's bolder now, it shouldn't be too small. Can we try that on both the tab and dropdown button badges?
A couple new items I hadn't noticed:

What is dictating the width of the servers dropdown? Is that a fixed width or is it based on the content. The main reason I ask is that it's quite a bit wider than it needs to be.
2/ In dark mode, the unread badges don't have the same color. It looks like the badge color in the tabs and the dropdown button need to be updated to the color that is used in the menu row

For the unread badge on the dropdown button, it needs to be nudged down by 1px and to the left by 1px. The mention badge position is fine as-is though

Building app in separate branch.

Nice work @devinbinnie. It's looking better - a few more things

The dropdown icons that I fixed were the little drag handles and the plus button, the other ones all looked fine.

Hmm, this still looks a little off to me. If I measure it, the server icon and the drag icon are sitting 1px too low. The other elements in the row seem fine. The plus icon in the Add server row also seems to be 1px too low.

Fixed!

I just played with this a bit in the inspector and the only way I could get the number to sit vertically centered is the change font-size: 9px instead of 10px. This actually seems to look better and because it's bolder now, it shouldn't be too small. Can we try that on both the tab and dropdown button badges?

Done!

What is dictating the width of the servers dropdown? Is that a fixed width or is it based on the content. The main reason I ask is that it's quite a bit wider than it needs to be.

I had a min-width of 354px set on the dropdown. I've removed that and forced a margin between the buttons and the server name on each dropdown menu item of 36px, which should reduce the width while still making sure we have good spacing. Let me know if this works for you.

2/ In dark mode, the unread badges don't have the same color. It looks like the badge color in the tabs and the dropdown button need to be updated to the color that is used in the menu row

Done!

For the unread badge on the dropdown button, it needs to be nudged down by 1px and to the left by 1px. The mention badge position is fine as-is though

Done!

Successfully building:
https://circleci.com/gh/mattermost/desktop/12998
https://circleci.com/gh/mattermost/desktop/12997
https://circleci.com/gh/mattermost/desktop/12996

Artifact links:
https://12998-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-setup-5.0.0-develop-win.exe
https://12997-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-mac-arm64.dmg
https://12997-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-mac-x64.dmg
https://12996-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-linux-ia32.tar.gz
https://12996-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-linux-x64.tar.gz

Thanks for resolving most of the issues @devinbinnie!

Hmm, this still looks a little off to me. If I measure it, the server icon and the drag icon are sitting 1px too low. The other elements in the row seem fine. The plus icon in the Add server row also seems to be 1px too low.

It looks like the checkmark icon might need an adjustment too - it still feels like it's sitting low to me.

Also, it looks like the styling of the server dropdown button mention badge and the tab mention bade aren't quite matching. Can we update the server dropdown badge to use -webkit-font-smoothing: auto; and adjust so it vertically sits centered like it does on the tab badge? I'm not sure what the cause is but there is something inconsistent between the two.

@matthewbirtch Okay I fixed the checkmark thing, as for the badges I made changes to make sure that the CSS is identical, but I still see some positioning issues between the two. I looked at the CSS generated and nothing that I changed made any difference. This is the CSS for each of the badge classes, which are now identical except for positioning requirements.

@matthewbirtch Okay I fixed the checkmark thing, as for the badges I made changes to make sure that the CSS is identical, but I still see some positioning issues between the two. I looked at the CSS generated and nothing that I changed made any difference. This is the CSS for each of the badge classes, which are now identical except for positioning requirements.

I have a feeling it's related to line-heights set on parent elements. There are no line-heights being set on the badge span tag itself so there may be something inconsistent inheriting here.

@matthewbirtch Okay I fixed the checkmark thing, as for the badges I made changes to make sure that the CSS is identical, but I still see some positioning issues between the two. I looked at the CSS generated and nothing that I changed made any difference. This is the CSS for each of the badge classes, which are now identical except for positioning requirements.

I have a feeling it's related to line-heights set on parent elements. There are no line-heights being set on the badge span tag itself so there may be something inconsistent inheriting here.

@matthewbirtch There is a difference, one is using 13.5px and one is using 18px, but I changed them both to 18px and nothing changed. Don't know if it changes for you, I'm working on Windows with no zoom level set.

@also @devinbinnie the span itself has pretty different styles applied based on what's in the inspector.
Dropdown badge span
.TeamDropdownButton__badge-count > span {
    color: white;
    font-size: 9px;
    padding: 0px 5px;
    display: flex;
    justify-content: center;
    align-items: center;
    font-family: "Open Sans", sans-serif;
    font-weight: bold;
    letter-spacing: normal;
    -webkit-font-smoothing: antialiased;
}

Tab badge span
.TabBar .teamTabItem span {
    flex: 0 1 auto;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
    text-align: center;
    -webkit-font-smoothing: auto;
}

@matthewbirtch There is a difference, one is using 13.5px and one is using 18px, but I changed them both to 18px and nothing changed. Don't know if it changes for you, I'm working on Windows with no zoom level set.

The line-height should be 12px, but it sounds like it's not making a difference for you

@devinbinnie I just removed all styling on the span tag and applied the following and it seems to resolve:
.TeamDropdownButton__badge-count {
    background: #F74343;
    border-radius: 8px;
    display: flex;
    align-items: center;
    flex: 0 0 auto;
    padding: 0px 5px;
    color: white;
    font-size: 9px;
    position: absolute;
    top: -4px;
    right: -2px;
    border: 2px solid #efefef;
    height: 12px;
    font-family: 'Open Sans', sans-serif;
    font-weight: bold;
    -webkit-font-smoothing: auto;
    line-height: 12px;
    box-sizing: unset;
}

I think the problem was box-sizing was getting set by something

@devinbinnie I just removed all styling on the span tag and applied the following and it seems to resolve:
.TeamDropdownButton__badge-count {
    background: #F74343;
    border-radius: 8px;
    display: flex;
    align-items: center;
    flex: 0 0 auto;
    padding: 0px 5px;
    color: white;
    font-size: 9px;
    position: absolute;
    top: -4px;
    right: -2px;
    border: 2px solid #efefef;
    height: 12px;
    font-family: 'Open Sans', sans-serif;
    font-weight: bold;
    -webkit-font-smoothing: auto;
    line-height: 12px;
    box-sizing: unset;
}

I think the problem was box-sizing was getting set by something

Thanks @matthewbirtch, should be all good now.

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/desktop/13052
https://circleci.com/gh/mattermost/desktop/13051
https://circleci.com/gh/mattermost/desktop/13050

Artifact links:
https://13052-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-setup-5.0.0-develop-win.exe
https://13051-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-linux-ia32.tar.gz
https://13051-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-linux-x64.tar.gz
https://13050-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-mac-arm64.dmg
https://13050-43964563-gh.circle-artifacts.com/0/tmp/artifacts/mattermost-desktop-5.0.0-develop-mac-x64.dmg


Set Default Value for 'startDate' to January 1, 2013.

Re: https://github.com/wise-old-man/wise-old-man/issues/1373
Changes:

Refactored the date selection logic to address user input issues and improve browser compatibility.
Introduced a fixed Min Date (OSRS Launch Date: February 22, 2012) to prevent users from selecting dates before this point.
Set a Max Date dynamically to the current date to prevent users from selecting future dates.

Outcome:

Resolves issues related to unconventional user input, such as entering a Year of '1', by ensuring that the start date defaults to '01-01-2013'.
Enhances browser compatibility and mitigates unexpected behaviours triggered by non-sanitized dates.
Improves the user experience by providing a stable and predictable date selection process.
Enhances data integrity and prevents users from selecting illogical date ranges, ensuring that the end date is not set before the start date and vice versa. This measure contributes to the overall robustness and accuracy of the date selection process.

Ran QA on new code, and checked usages. I did not encounter any issues with changes. Ran lint - OK.

One last thing, could you also do that for endDateTime? It could also be incorrectly set to 1

One last thing, could you also do that for endDateTime? It could also be incorrectly set to 1

Done! See Commit 8129c59.
Tested and works as intended on my dev

Closing in favour of https://github.com/wise-old-man/wise-old-man/pull/1507


from models.loss import *  #NTXentLoss, NTXentLoss_poly

hello
i want to knwo what models is ?

HI Changru Guo,
In from models.loss import * is a typo, it should be from model import * and from loss import *. We just updated the TFC to fix this typo and more bugs. The new version is in folder TFC-pretraining/code/TFC/.
Please check more details in the Updates on Jan 2023 section of the repo readme. Thank you.


Add gRPC reverse proxy server example

Motivation:
Add gRPC reverse proxy server example
Modifications:
Add gRPC reverse proxy server example with testcontainers.
Result:

Closes #2353 .

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yukeun seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Could you check the build failures and make sure the tests are not flaky?

It does not appear to be a problem caused by overlapping ports.
Let me find the cause again.

build-self-hosted-unsafe-jdk-21-snapshot-blockhound
I don't think there's a docker on the ci server
java.util.concurrent.CompletionException: java.lang.IllegalStateException: Could not find a valid Docker environment. Please see logs and check configuration

Pushed some small commits 🙇  Let me know if any changes don't make sense

Looks great, thanks! Could you also run this script to see if everything works correctly? https://github.com/line/armeria-examples/blob/main/update-examples.sh You might run this command: (I supposed armeria and armeria-examples are in the same parent directory) ./update-examples.sh 1.29.0 ../armeria

This script is not working properly.
The following error occurs
Is there a dependency I need to add?

This script is not working properly.

Let me see what happened. 😉

Let me see what happened. 😉

It works correctly. The problem was just that we needed to convert the libs.testcontainers.junit.jupiter to the actual names in the script like:
-pe "s/libs.testcontainers.junit.jupiter/'org.testcontainers:junit-jupiter:$TESTCONTAINER_VERSION'/g;" \
It will be handled when we release the next version so you don't have to worry about it. 😉

Rather, I think learned a lot. Thank you. 😄


Add a fromString() constructor.

While the current API provides a toString() method for serialization, it would also be handy to have a Measure.fromString() method for de-serialization.
Even though parsing such a string is trivial, it should still be handled internally by the API, with the possibility of throwing an Error on invalid or non-sensical inputs (think of temperatures below 0 Kelvin).

Also, the precision should be (optionally?) serialized along the value and unit.


run.sh is killed

Dears,
When I run the .sh by cmd "./run.sh" as following, it always shows ***** killed. Do you know how to get rid of the problem, please?
Thank you in advance!
Yi Huo
(base) yihuo@yihuo:~/Documents/deephar-master$ ./run.sh
~/Documents/deephar-master ~/Documents/deephar-master
fatal: not a git repository (or any of the parent directories): .git
Initializing deephar v0.5.0
CUDA_VISIBLE_DEVICES: 2
2023-04-30 20:27:21.740019: I tensorflow/core/util/port.cc:110] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2023-04-30 20:27:21.797162: I tensorflow/tsl/cuda/cudart_stub.cc:28] Could not find cuda drivers on your machine, GPU will not be used.
2023-04-30 20:27:22.088804: I tensorflow/tsl/cuda/cudart_stub.cc:28] Could not find cuda drivers on your machine, GPU will not be used.
2023-04-30 20:27:22.089272: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-04-30 20:27:22.808816: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
Using keras version "2.12.0"
/home/yihuo/Documents/deephar-master/exp/mpii/train_mpii_singleperson.py:94: UserWarning: Model.fit_generator is deprecated and will be removed in a future version. Please use Model.fit, which supports generators.
model.fit_generator(data_tr,
2023-04-30 20:28:17.264850: I tensorflow/core/common_runtime/executor.cc:1197] [/device:CPU:0] (DEBUG INFO) Executor start aborting (this does not indicate an error and you can ignore this message): INVALID_ARGUMENT: You must feed a value for placeholder tensor 'Placeholder/_0' with dtype int32
[[{{node Placeholder/0}}]]
./run.sh: line 52: 104766 Killed                  python3 exp/mpii/train_mpii_singleperson.py output/mpii_singleperson_trial-00

Hi @YeeHoran ,
Please check the file requirements.txt and double check your environment.  It seems you are using a different version of Keras and that your tensorflow is not able to use the gpu.

Dear @dluvizon
Thank you so much for your quick reply! And really the tensorflow is not enabled to use the gpu. In fact the version of the tools listed in  requirement.txt  are posted in the below:
numpy: 1.23.5
keras: 2.12.0
tensorflow-gpu: 2.12.0
pillow: 9.4.0
scipy: 1.10.0
h5py:3.7.0
It could be observed that they are all newer than the versions listed in the requirement.txt file. In my opinion, newer versions are backward compatible, so they could be used as well. Do you think this is correct, please?
Thank you for your kind support!

Hi, I'm pretty sure that it will not work. This code uses TF 1.x, which is quite often not compatible with TF 2.

Thank you so much again for your kind support @dluvizon,
Now I run it, but it stopped again, and present the following information:
File "/home/yihuo/Documents/deephar-master/exp/mpii/train_mpii_singleperson.py", line 94, in
model.fit_generator(data_tr,
File "/home/yihuo/anaconda3/lib/python3.10/site-packages/keras/src/engine/training.py", line 2810, in fit_generator
return self.fit(
File "/home/yihuo/anaconda3/lib/python3.10/sinceite-packages/keras/src/utils/traceback_utils.py", line 70, in error_handler
raise e.with_traceback(filtered_tb) from None
File "/home/yihuo/Documents/deephar-master/exp/common/mpii_tools.py", line 156, in on_epoch_end
scores = eval_singleperson_pckh(model, self.fval, self.pval,
File "/home/yihuo/Documents/deephar-master/exp/common/mpii_tools.py", line 67, in eval_singleperson_pckh
input_shape = model.get_input_shape_at(0)
RuntimeError: The layer model_1 has never been called and thus has no defined input shape.
./run.sh: line 52:  2374 Killed                  python3 exp/mpii/train_mpii_singleperson.py output/mpii_singleperson_trial-00_
Additionally, the log.txt is in Epoch 1/120, and since the end of the file shows 1073/1073, so may be now the problem is it runs out of ram, do you think this is right, please? Thank you!


When preempting in a flavor, retry all flavors in the next iteration

What type of PR is this?
/kind bug
What this PR does / why we need it:
Wipe the last assignment information when issuing preemptions, as the scheduler should retry all flavors in the next admission attempt.
Also ensure that the integration test checks for the admission flavor, not just that a workload was preempted.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Fixed fungiblity policy `whenCanPreempt: Preempt`. The admission should happen in the flavor for which preemptions were issued.

cc @KunWuLuan

/cherry-pick release-0.5


Integration of Xtion into Hera's vision system

[x] Install all necessary packages in order to run Xtion2 bridge.
[x] Change all vision system topics and frame size to Xtion2.
[x] Test detector_2d and hera_objects with Xtion2.

If everything works, next step will be to add a Logitech C920 RGB camera on top of Xtion2 and try to synchronize them.

Worked. Proceeding to the next step.


Colab example not working

Hi, I tried your notebook at https://colab.research.google.com/github/neuml/txtai/blob/master/examples/10_Extract_text_from_documents.ipynb
but the second cell ("Create a Textractor instance") returns an error:
RuntimeError: Failed to import transformers.pipelines because of the following error (look up to see its traceback): module 'PIL.Image' has no attribute 'Resampling'
Do you have any idea how to fix this?
Great project though!

Thank you for giving txtai a try!
This is similar to these issues: https://github.com/neuml/txtai/issues/255 and https://github.com/neuml/txtai/issues/257
In certain cases, Colab requires a restart when updating libraries. Unfortunately, I haven't found a clean automated way to do this outside the runtime restart and re-run pattern.

Great, I had no idea a restart could help :)


Cannot configure Phpstan with the DDEV container.

Hi, I keep getting the following error;
com.intellij.execution.process.ProcessNotCreatedException: Cannot run program "docker-compose" (in directory "/home/huzaifa/code/shopware/.ddev"): error=2, No such file or directory

Can you provide a guide or a setting configuration how I can run this? @rfay

This isn't the right place for this issue, but what you would want to do is configure the location of docker-compose in Build, Execution, Deployment -> Docker -> Tools - and it should be set to ~/.ddev/bin/docker-compose (or expand the ~, for example /Users/rfay/.ddev/bin/docker-compose or /home/rfay/.ddev/bin/docker-compose


🎁 ✉ 📆 [Sticky] UI Kitten Release Notes & News

📰 This is a read-only UI Kitten newsletter.
📫 Only latest news and release notes.
🚀 Subscribe (on the right) to stay tuned!

🎉 v4.1.0 (2019-07-11)
Release Notes:
Highlights 🚀
✅ 🌐 React Native Web support
✅ 📱New modal component with developer-friendly API
✅ Input icon press handler
const onIconPress = () => {
  // Handle Icon Press
};

<Input onIconPress={this.onIconPress}/>

Lots of other bug fixes and improvements!

🎉 v4.2.0-beta.2 (2019-08-30)
Release Notes:
Highlights 🚀
✅ Select component
✅ Drawer component
✅ Spinner component
✅ OverflowMenu component is based on Menu now
✅ Icon component
✅ Meet the brand-new Eva-Icons Module with the pre-setup icons packs!
Lots of other bug fixes and improvements!

🎉 v4.2.0 (2019-09-27)
Release Notes:
Highlights 🚀
📝 Global Font Family: Now it is possible to set fontFamily globally as mapping variable
import React from 'react';
import { mapping, light as theme } from '@eva-design/eva';
import { ApplicationProvider } from 'react-native-ui-kitten';

const strictTheme = { ['text-font-family']: 'YOUR-FONT-FAMILY' };
const customMapping = { strict: scrictTheme };

// ...

<ApplicationProvider mapping={mapping} theme={theme} customMapping={customMapping} />

📆 Calendar and Datepicker components.
Supports ranges, locales, and differend date objects like moment
🔥 New component stylings provided by updated Eva Design System
✅ Toggle now can accept text property
🐛 Fixed react-native template modules
# Simply run the command below to initialize application based on UI Kitten
npx react-native init AwesomeApp --template react-native-template-ui-kitten

📚 Documentation examples were refactored to JavaScript
✅ All components from beta release were updated with bug fixes. Thanks for your feedback!
Lots of other bug fixes and improvements!

🎉 Documentation for v4.2.0 (2019-10-11)
📚 Documentation was updated with tons of clickable examples
👇 https://akveo.github.io/react-native-ui-kitten/docs/components/components-overview
Notes:
Live examples are running with React Native Web and can contain some bugs with web states like hover and focus. This means it works perfect on mobile, but not on the web. This will be fixed soon with #663

🎉 v4.3.0-beta.1 (2019-10-17)
Release Notes:
Highlights 🚀
🌐 React Native Web states: Now components support hover and focus states when using in the web! Just open documentation to see how it feels 😍
📆 Calendar now supports setting a first day of week. Notice, that this feature is also available for  RangeCalendar, Datepicker and  RangeDatepicker components. See it in action
🐛 Fixed Calendar navigation when passing min property
🐛 Fixed ButtonGroup render issues
Mobile backend Bundles 📱
We also glad to present the new products of Akveo team! See ready-to-go solution with Mobile Backend Bundles
Lots of other bug fixes and improvements!

🎉 v4.3.0 (2019-12-04)
Release Notes:
Highlights 🚀
📚 Simplified Getting Started Guide: We have completely reworked our Getting Started Guide. Now it includes step-by-step articles to build React Native app including Branding, Navigation and more.
💅 Unified Eva 1.3 Design: Eva 1.3 is about unification component stylings
✅ Card component: New UI Kitten component
Lots of other bug fixes and improvements

⚠ react-native-ui-kitten package deprecated
We deprecate react-native-ui-kitten package in order to use @ui-kitten/components.
In fact, the new package contains same source code as an old. In order to migrate, consider following the steps below:
npm un react-native-ui-kitten && npm i @ui-kitten/components

- import { ApplicationProvider, Layout, Button } from 'react-native-ui-kitten';
+ import { ApplicationProvider, Layout, Button } from '@ui-kitten/components';

In case you have no react-native-svg package installed:
npm i react-native-svg && cd ios && pod install

🎉 v4.3.2 (2019-12-13)
Release Notes:
Highlights 🚀
🐛Resolve web builds. You don't need custom webpack config to run UI Kitten modules anymore. Furthermore, now it works properly in Safari!
(#763, #729, #692)
🐛Fix performance of Modals, Pickers, and Calendar. Check them out!
(#641)

Upgrade:
npm i @ui-kitten/components@latest @ui-kitten/eva-icons@latest @eva-design/eva@latest

And restart your app with clearing cache.

🎉 v4.4.0-beta.1 (2020-01-03)
Highlights 🚀
✅ Autocomplete: new UI Kitten component. Docs
(#696, #750)
💅 Styling & Theming: add useTheme and useStyleSheet hooks. Use useTheme to accept a current theme, and useStyleSheet to create styles in a way similar toStyleSheet.create.
See docs for more details
import { useStyleSheet } from '@ui-kitten/components';

const MyComponent = () => {
  const styles = StyleSheet.create();

  return (
    <View style={styles.container} />
  );
};

const StyleSheet = useStyleSheet({
  container: { backgroundColor: 'color-primary-default' },
});

(#676, #752)

Upgrade:
npm i @ui-kitten/components@beta @ui-kitten/eva-icons@beta

And restart your app with clearing cache.

🎉 v4.4.0 (2020-02-10)
Highlights 🚀
With this release, we bring new Eva Design System package which will make your app look like material. Try it out by switching @eva-design/eva imports to @eva-design/material with no more changes 🤯
We also introduce a bare-minimal application that already runs Eva Material. Check it out! or try running Kitten Tricks to see how it looks!

🙀Demo App Kitten Tricks is now runnable in both Expo and React Native environments and supports expo eject with no need to refactor expo-specific modules.
🐛 Modal: state update during render (#847)
🐛 Input: extra vertical padding on Android (#609)
Complete changelog
Upgrade:
npm i @ui-kitten/components@latest @ui-kitten/eva-icons@latest @eva-design/eva@latest

And restart your app with clearing cache.

🎉 v4.4.1 (2020-02-24)
Highlights 🚀
With this release, we introduce a package to help you improve performance of application loading by processing Eva during the build time.
Integration (Guide)

yarn add @ui-kitten/components@latest && yarn add -D @ui-kitten/metro-config
Add or modify metro.config.js with following configuration

+ const MetroConfig = require('@ui-kitten/metro-config');

+ const evaConfig = {
+   evaPackage: '@eva-design/eva', // Required (Can be `@eva-design/material`)
+   customMappingPath: './custom-mapping.json', // Optional
+ };

+ module.exports = MetroConfig.create(evaConfig, {
+   // Whatever was in previous metro.config.js
+ });

Modify props of ApplicationProvider

- import { mapping, light } from '@eva-design/eva';
+ import * as eva from '@eva-design/eva';
- import { customMapping } from './custom-mapping.js'

export default = () => (
- <ApplicationProvider mapping={mapping} theme={light} />
+ <ApplicationProvider {...eva} theme={eva.light} />
);

Restart your app with clearing cache.

🎉 v5.0.0-alpha.1 (2020-04-08)
Highlights 🚀
With this release, we introduce a completely rethought component APIs, improving developer experience by structuring components in a declarative way. These changes also open more capabilities in component styling, providing you a flexible APIs.
Migration

🎉 v5.0.0-alpha.1 (2020-05-12)
Highlights 🚀
UPCOMING


Do you utilize original gaussian render engine

When you decompose motion into gaussians, do you have modification on original gaussian render engine. I assume the backward part should have some modifications..

What do you mean about ‘decompose motion into gaussians’？ I didn't modify the original gaussian render engine.


Fix amplitudeencoding

Fix for #365.
Exchanges np.linalg.norm with hand-coded normalization. Improves and adds tests.

I addressed all comments and the fix is working with all interfaces and argument passing strategies. Ready for re-review.

closes #365


Axios patch request is not working.

var config = {
headers: {
'Content-Type': 'application/x-www-form-urlencoded'
},
withCredentials: true,
}
var payload = axios.patch(url, {} , config);
It throws an error -  XMLHttpRequest cannot load "request_url". Response for preflight has invalid HTTP status code 405

Your code makes a CORS request, but the server cannot handle preflight (OPTIONS) requests. You can learn about CORS here:

http://www.html5rocks.com/en/tutorials/cors/
https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS

@nickuraltsev When Im hitting as POST request it is working fine. And i checked it too that PATCH request is allowed at server.


introspectNavigationController

In our project all the following are failing on an iPhone 6S device running iOS 15.1. Using Introspect v0.1.4.
introspectNavigationController
introspectTabBarController
introspectScrollView
They never trigger the callback. It works on other more recent devices, however. Is this a known issue?

This is no longer an issue when using the new SwiftUIIntrospect module. Closing.


Switch from ReactiveCocoa to ReactiveObjC

Since ReactiveCocoa has been split into separate repos for Obj-C and Swift, this switches from using ReactiveCocoa (which only includes ReactiveSwift) to ReactiveObjC instead.
There are also some minor changes to Overcoat.xcodeproj/project.pbxproj and Podfile.lock caused by the latest version of CocoaPods.

Thanks!!


Reduce the size of the prelude by promoting Session! to a more prominent position in the library

@sdleffler When you get the chance, I'd appreciate your thoughts on the documentation in this branch as it stands, in particular focusing on tutorial.rs and the quick reference table section of the main lib.rs docs, but also including item documentation that makes use of Session!. The tutorial as of right now has been converted to exclusively using the Session! macro, and only mentions in passing the existence of the underlying dialectic::types module whose types to which Session! compiles. Is this too little discussion of dialectic::types? How to integrate with the main text without being overwhelming? How to provide users with the tools they need to understand error messages?

After merging in this most recent main branch, this change seems to break the micro benchmarks. While dialectic::unary::constants remains in the prelude, dialectic::unary::types was removed, which causes bench/micro to break. It seems that if we want Choice in the prelude, it makes sense to also include the types which are necessary to write a valid Choice<N> type. Requesting review once again to take a look at this, after that I think I'm okay w/ merging?


Potentially use Kani

Including tests using Kani could potentially help avoid bugs. https://github.com/model-checking/kani

I rarely write a test here.


Notification shows up right away instead of waiting for scheduled time

Code:
                await CrossNotifications.Current.Send(new Notification
                {
                    Id = 1,
                    Title = "Test title here",
                    Message = "Test message here",
                    When = TimeSpan.FromSeconds(10),
                });

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[] iOS
[v] Android
[] UWP
[] .NET Standard

Version of OS(s) listed above with issue
Min. 4.0.3
Target 8.0
Version of Library
4.0
Expected Behaviour
Notification waits for 10 seconds and show.
Actual Behavior
Notification shows up right away.
Code of Conduct

No Library Update Requests
No Timeline Requests
Please read through the documentation and FAQs
Please be respectful of my time. I put a lot of effort into my libraries.  I try to support the issue requests within a day.  I'm not psychic, so please take the time to fill out the above form as complete as possible

When will be gone in the next release.  Just use 'Date'.  Couldn't reproduce anyhow


Request for Open Source License

Hi there,
I am a Machine Learning Developer in Mila's AI for Humanity department working on the Biasly project. In our work, we came across your paper "An expert annotated dataset for the detection of online misogyny" and found it very useful for our project!
We are hoping to use the dataset published on this Github repository for some of our experiments, but are unable to as, as far as we could see, the Github repository does not contain an open source license.
We were therefore wondering if you would be willing to add an open source license to the repository so that we can use this dataset for our project?
Please let us know if you'd like to learn more about our project or need additional information regarding licensing the dataset.
Best,
Brooklyn and the Biasly team

Added an MIT license. Best of luck with the project and let me know if you have any questions!


fix: upgrade tekton and fix eks secret schema

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/override Kind / kind (pull_request)

@jstrachan: /override requires a failed status context to operate on.
The following unknown contexts were given:

Kind / kind (pull_request)

Only the following contexts were expected:

Lighthouse Merge Status
gke

In response to this:

/override Kind / kind (pull_request)

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.


Add a note for use with Parity [ci skip]

Per https://github.com/thoughtbot/parity/issues/51#issuecomment-144960222 :blush:
/cc @geoffharcourt

I'm not sure what parity has to do with this. Those remotes are from the old version of this plugin, I don't think that's where they came from. (But please correct me if I'm wrong)

I'm not sure what parity has to do with this. Those remotes are from the old version of this plugin, I don't think that's where they came from. (But please correct me if I'm wrong)

You're right! :bow:


Upgrade chaos-operator in chaoscenter/graphql

Proposed changes
Summarize your changes here to communicate with the maintainers and make sure to put the link of that issue
Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING doc
[ ] I have signed the commit for DCO to be passed.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Dependency

Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

This PR have to wait for the PR#475 to be merged.

Hi @Nageshbansal , Can you check the build-pipeline / docker-build-graphql-server (pull_request) ?

The build is failing because of local path reference in the go.mod ( which I will refactor after the operator PR gets merged)

I will approve it after the operator PR gets merged


Test fix dns case

Type of change:

[ ] Bugfix
[ ] New feature provided
[ ] Improve performance
[ ] Backport patches
[ ] Documentation
[ ] Refactor
[ ] Chore
[x] CI/CD or Tests

What this PR does / why we need it:

Pre-submission checklist:

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[ ] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

Codecov Report
Patch and project coverage have no change.

Comparison is base (c3dff87) 40.42% compared to head (3e6bba9) 40.42%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #132   +/-   ##
=======================================
  Coverage   40.42%   40.42%
=======================================
  Files          92       92
  Lines        7090     7090
=======================================
  Hits         2866     2866
  Misses       3841     3841
  Partials      383      383

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


Fix #418, Windows Redis yields ValueError

This defensive programming fix gets around a fatal ValueError when connecting to Windows Redis instances, see https://github.com/MeetMe/newrelic-plugin-agent/issues/418

It would be lovely if this pull request got some attention. This bug will affect anyone who uses Redis on Windows, please accept the patch.

@gmr Do you think you could take a look at this itty-bitty pull request that will help this software from failing to work vs. Redis 2.x on Windows?
It's a simple defensive programming measure so that the key/value splitting happens only on the first ':' in the line.
Thanks!


Playback speed

I would love the ability to change the playback speed on mobile. Surprised after all this time it was never added to the default app.

Duplicate of #539


Date validation in non-US cultures

Hi everyone,
I'm new to the project; I've enjoyed investigating the source so far, and I hope I'll be able to contribute something useful.
I recently came across an issue with the date pickers on the website: the server side validation occurs according to the culture that the web server runs in.
However, the jQuery UI date picker used across the site is currently hard coded to use US date format (in Views/Shared/_Layout).
This means that when server is run in cultures with different date format, like the UK (where I am), the server side validation fails (the default date format here being DD/MM/YYYY).
Perhaps the most straightforward way to address this, at least for the time being, is to force the server to run with culture set to en-US.  That would make the site operational for those of us not in the US with just a few lines of code in Startup.cs.
Does that sound like a sensible way forward?
Thanks
Simon

In general, we need to review how we handle dates in the app.
Date formatting is part of it although I think we are likely limited to the US for this first version.
I don't think we are using the jQuery UI date picker. I think we are using a bootstrap date picker.
Timezones is a bigger issue I think. I recommend some variation of the approach outlined here: https://weblog.west-wind.com/posts/2015/Feb/10/Back-to-Basics-UTC-and-TimeZones-in-NET-Web-Apps

Thanks for the Strahl reference, that was a useful read.  And yep, my mistake on which datepicker is being used.
The issue isn't so much date formatting, though, or even date storage.  At least as far as I can gather, the problem is that if the server is run in a non-US context then it's not possible to submit dates to the site which have a day-in-the-month value greater than 12.  E.g. if I use the date selector to pick October 29, it's formatted and sent to server as 10/29/2015, which is then rejected as an invalid date server side because ASP.NET running on my machine with a culture of en-GB thinks that date is invalid.
I think that issue is independent of how the dates are stored or subsequently re-displayed to the user.

Ah so this is getting into the globalization side of things. That's a tough one, especially since those features of MVC 6 are not well documented yet.
@tonysurma @BillWagner Are we targeting non-US cultures for this November MVP?

Yes, partly at least.
But note that as it stands the application has inconsistent behaviour: parts of the app derive the culture from the execution environment, run in that culture and so then behave (e.g. with respect to the handling of dates) accordingly.  Other parts have US date format hard-coded.
If the decision is made to be US-only, this inconsistency should be ironed out so that at least the app can be run successfully in US-only mode on non-US machines.

Target is us only

Okay.  Is it alright to go ahead and push the change needed to ensure US culture server side?

from my perspective yes, but I would defer to @dpaquette for the call

Yeah that sounds safe. I assume you will just force the Culture to US for now?

Yes


(PUP-5382) Allow undefined nodes key on app declarations

Per the app spec, providing node mappings on app declarations is
optional. Prior to this commit, an error would be raised if the nodes
key on an app declaration was undefined. This commit prevents .value
from being called on an undefined value during application evaluation.

Thanks for the PR, looks good - I wonder if we need to be concerned about a non hash value or not.

Henrik, apt observation. Does the approach in 1b2076a work for you?

Yes, that adds sufficient protection. (There may be checks elsewhere, but since other aspects of what may be found inside a :node hash was being checked I think this added check is worth having).


Enable billing measure of GCP Jenkins workers

What feature do you want to see added?
As a GCP customer, I'd like to set labels on the Jenkins workers created (the VMs), so that I can measure the cost of my Jenkins workers in my GCP billing reporting screen.
AC :

If a list of googleLabels ("key":  "value") are set (in the Casc code or from configuration screen in Jenkins), then those labels are set to the created GCP VMs

Notes :

I understand that googleLabels doesn't have the DataBoundSetter annotatation and thus cannot be set from Jenkins : https://github.com/jenkinsci/google-compute-engine-plugin/blob/develop/src/main/java/com/google/jenkins/plugins/computeengine/InstanceConfiguration.java#L288
There are 2 existing labels (cf https://github.com/jenkinsci/google-compute-engine-plugin/blob/develop/src/main/java/com/google/jenkins/plugins/computeengine/ComputeEngineCloud.java#L81), but it is not enought for me to differentiate the costs origine

Upstream changes
No response

hey @gfroid79 , I know I'm 1.5 yrs late but I've run into the same issue and would really appreciate if you could tell me how you got around this .

I could not... Sorry !


update black-screen to 0.1.23

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Thank you.

Sorry for the late reply, thanks for merging this quickly


broken link in readme

just noticed the link to the catalyst idea in the readme is broken, https://cardano.ideascale.com/c/idea/402572

Hey @fangio10 thanks for reporting this, I don't know how I missed it sorry about the delay!
I tried the link in the README https://cardano.ideascale.com/c/idea/402572 and it seems like it works and it just redirects to the new link https://cardano.ideascale.com/c/idea/62613.
Seems like that's ok, so I'll go ahead and close this. Thanks again!


Readme 0.33

0.33 readme prep

Do we ship an updated experimental build? The last one was 0.28.0 from December.

By the way: 10000 issues/prs 🥳 🎉
Originally posted by @Aaron-Junker in https://github.com/microsoft/PowerToys/pull/10000#issuecomment-789473483
@crutkas We should celebrate and mention this in our readme.  😀🎉🥳


Content Security Policy Error

Versions
Angular CLI: 1.7.3
Node: 6.10.0
OS: win32 x64
Angular: 5.2.9
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.7.3
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.5.3
webpack: 3.11.0

Repro steps

Create a new project with ng new myproject
Run ng serve
Open http://localhost:4200 in Chrome

Observed behavior
The page comes up with an error saying Cannot get /
Errors in Chrome's Dev Tools, there's 22 of them but these are just the top few:
Refused to load the font '<URL>' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'font-src' was not explicitly set, so 'default-src' is used as a fallback.
localhost/:1 Refused to load the font 'data:font/woff;base64,d09GRgABAAAAAGVUABEAAAAAxuQAAQABAAAAAAAAAAAAAAAAAAAAA…eLo4GBkcWhIzkkAqQkEggceHw5HFkM2VRZJFlYebR2MP5v3cDSu5GJwWUDW9xG1hQXAFAmKZU=' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'font-src' was not explicitly set, so 'default-src' is used as a fallback.
localhost/:1 Refused to load the font 'data:font/woff;base64,d09GRgABAAAAAGz8ABEAAAAA09gAAQABAAAAAAAAAAAAAAAAAAAAA…i3i6OBgZHFoSM5JAKkJBIIHHh8ORxZDNlUWSRZWHm0djD+b93A0ruRicFlA1vcRtYUFwBQJimV' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'font-src' was not explicitly set, so 'default-src' is used as a fallback.
localhost/:1 Refused to load the font 'data:font/woff;base64,d09GRgABAAAAAGvEABEAAAAA0agAAQABAAAAAAAAAAAAAAAAAAAAA…i3i6OBgZHFoSM5JAKkJBIIHHh8ORxZDNlUWSRZWHm0djD+b93A0ruRicFlA1vcRtYUFwBQJimV' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'font-src' was not explicitly set, so 'default-src' is used as a fallback.
localhost/:1 Refused to load the font 'data:font/woff;base64,d09GRgABAAAAAG1gABEAAAAA1pAAAQABAAAAAAAAAAAAAAAAAAAAA…ujgYGRxaEjOSQCpCQSCBx4fDkcWQzZVFkkWVh5tHYw/m/dwNK7kYnBZQNb3EbWFBcAUCYplQ==' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'font-src' was not explicitly set, so 'default-src' is used as a fallback.

Desired behavior
Seeing the page as you normally would.
Mention any other details that might be useful (optional)
I deleted the global version of @angular/cli and I deleted it from the cache, then reinstalled it with no changes.

So I've actually already solved it while typing problem out but I wanted to make it available for others. The problem is that I had a space in the name of my Git repo. This appears as a %20 in Windows. I renamed that folder and this started working. #


DO_NOT_MERGE update vite to 2.5.0-beta.0 to check ci

lets see if something breaks

2.5 has been released


threadpool:use channel to reduce lock in push new task && adjust test

Hi,all,
This PR use channel to reduce lock when a tasks comes. Also it adjust the test to fix https://github.com/pingcap/tikv/issues/1796.
@zhangjinpeng1987 @hhkbp2 PTAL.

@zhangjinpeng1987 @hhkbp2 PTAL

LGTM please fix ci

@hhkbp2 PTAL

Rest LGTM

@hhkbp2 @zhangjinpeng1987 PTAL again.

LGTM

Rest LGTM

LGTM