chcon: can't apply partial context to unlabeled file '/usr/local/bin/k3s'

Version:
k3s version v1.17.3+k3s1 (5b17a175)
K3s arguments:
curl -sfL https://get.k3s.io | sh -
Describe the bug
When installing on Raspbian lite (2020-02-03) on both master and agent nodes this error occurs
chcon: can't apply partial context to unlabeled file '/usr/local/bin/k3s'
To Reproduce
Setup a Raspbian lite Raspberry Pi 4 4GB and run the script.
Expected behavior
No error to occur.
Actual behavior
The error occurs!
Additional context / logs
[INFO]  Finding latest release
[INFO]  Using v1.17.3+k3s1 as release
[INFO]  Downloading hash https://github.com/rancher/k3s/releases/download/v1.17.3+k3s1/sha256sum-arm.txt
[INFO]  Downloading binary https://github.com/rancher/k3s/releases/download/v1.17.3+k3s1/k3s-armhf
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
chcon: can't apply partial context to unlabeled file '/usr/local/bin/k3s'
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
[INFO]  systemd: Starting k3s

me too
$ cat /etc/redhat-release
CentOS Linux release 7.7.1908 (Core)

$ docker --version
Docker version 19.03.8, build afacb8b

$ k3s --version
k3s version v1.17.3+k3s1 (5b17a175)

Does this result in an actual failure, or are you just not expecting to see the message? It looks like the intent is to hide both stdout and stderr from the chcon command, but the shell output redirection is bad - it first sends stderr to /dev/null, then to stdout.
https://github.com/rancher/k3s/blob/master/install.sh#L393

I get the same thing on Ubuntu 18.03, and it never seems to start properly

Same as @jfmatth

Weird, VERY Weird, tried everything again, and even though i get the chcon error, K3s comes up fine.
I'm wondering if it's a debian / library issue that got resolved today?

Sadly, same behavior from previous version too, if the firewalld is running, no route to host on a lot of the pod startup.  turn it off, and pods come up fine.
For reference, I merely install firewallD on my ubuntu VM's, and it's automatically opens port 22 for SSH, and I manually open 80 and 443 after install.

Good news (and sorry for all the posts) - Using UFW on Ubuntu seems to work!
Not sure the differences here, but it solves what i need today :)
Hope this helps everyone

This issue was for the chcon error, I'm not sure why everyone is talking about iptables and firewalld in here.

Does this result in an actual failure, or are you just not expecting to see the message? It looks like the intent is to hide both stdout and stderr from the chcon command, but the shell output redirection is bad - it first sends stderr to /dev/null, then to stdout.
https://github.com/rancher/k3s/blob/master/install.sh#L393

Just to confirm everything else works fine it's just scary when installing.

Does this result in an actual failure, or are you just not expecting to see the message? It looks like the intent is to hide both stdout and stderr from the chcon command, but the shell output redirection is bad - it first sends stderr to /dev/null, then to stdout.
https://github.com/rancher/k3s/blob/master/install.sh#L393

Just to confirm everything else works fine it's just scary when installing.

sorry for the confusion, yes, the message doesn't seem related to the FW comments.


{Core} aaz: optimize error display in argument validation

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Core


Unexpected behaviour with $elemMatch, $size, and exact object match

Hi Craig,
I encountered some unexpected behaviour when querying arrays of embedded objects with sift 13.3.1 (I'm working on node 12.16.3). Say, I have four objects, each with an array of embedded objects. In all my examples, I want to filter depending on what embedded objects there are inside the array.
const sift = require('sift')

const values = [
  {
    name: 'zeroElements',
    myArray: []
  },

  {
    name: 'oneElement',
    myArray: [
      { firstKey: 'a', secondKey: 'b' }
    ]
  },

  {
    name: 'twoElements',
    myArray: [
      { firstKey: 'a', secondKey: 'b' },
      { firstKey: 'c', secondKey: 'd' }
    ]
  },

  {
    name: 'otherElement',
    myArray: [
      { firstKey: 'e', secondKey: 'f' }
    ]
  }
]

If I run sift(query), the return value is a filter function that returns true or false, depending on whether the object matches the query, right? But this function appears to change when I use the same function again:
const query1 = {
  myArray: {
    $elemMatch: { firstKey: 'a', secondKey: 'b' }
  }
}

console.log('query1 (one sift):', values.filter(sift(query1)))
console.log('query1 (many sifts):', values.filter(x => sift(query1)(x)))

Expected behaviour: In both cases query1 should return oneElement, twoElements.
Actual behaviour: query1 (one sift) returns oneElement, twoElements, otherElement; query1 (many sifts) returns oneElement, twoElements, as expected.
The only difference between the two is that in the first version, sift(query1) is called only once, whereas in the second version, sift(query1) is called on every element of values.
In the following examples, the behaviour is the same, regardless of one sift or many sifts. Here, I want to get the value where myArray has only { firstKey: 'a', secondKey: 'b' }, and nothing else.
const query2 = {
  myArray: {
    $elemMatch: { firstKey: 'a', secondKey: 'b' },
    $size: 1
  }
}

console.log('query2:', values.filter(sift(query2)))

Expected behaviour: query2 should return oneElement.
Actual behaviour: query2 returns an empty array.
Alternatively, I can make myArray exactly match the array [ { firstKey: 'a', secondKey: 'b' } ], but in this case the order of firstKey and secondKey is important.
query3 = {
  myArray: [ { firstKey: 'a', secondKey: 'b' } ]
}

console.log('query3:', values.filter(sift(query3)))

Expected behaviour: query3 returns oneElement.
Actual behaviour: query3 returns oneElement. Yay!
Since in MongoDB the field order matters when matching the exact document, and not with $elemMatch, the following query should not work:
query4 = {
  myArray: [ { secondKey: 'b', firstKey: 'a' } ]
}

console.log('query4:', values.filter(sift(query4)))

Expected behaviour: query4 returns an empty array.
Actual behaviour: query4 returns oneElement.
Best wishes and thank you for your work!
Christopher

Very likely #212 is the same issue

Looks like @stalniy  was right - this should be fixed in 13.3.4.


Fixed tests for nm/libx264

Unified ChunkWriters interfaces: quality setting from 0..100 range for both writers
Motivation and context
Fix unit tests for https://github.com/openvinotoolkit/cvat/pull/2875
Checklist

[ ] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

@azhavoro , it looks like a wrong fix. Let's discuss tomorrow.

@azhavoro , I was wrong. The solution looks OK. At least I cannot provide a better one. I don't like that we specify externally 67, but from our side it doesn't look wrong.


[Communication] - Administration - Clean up Administration Package

Remove Administration package and all references

Remove reference from eng/jacoco-test-coverage/pom.xml

Remove reference from eng/versioning/version_client.txt

Remove reference from eng/.docsettings.yml if this file is managed by GitHub

/azp run java - core - ci

/azp run java - core - ci

/azp run java - core - ci


Migrate binary field from struct to enum.

Refactors BinaryField from being a usize container to a sum type of Zero and One.
Also adjusts tests and binary field extensions.

Curious if this is the best way for representation here. Would you create an enum for ternary field too with three elements inside?
Generally, goes for any F_p if p is known btw.
I guess for consistency's sake this is not the best possible thing.? But I may be wrong.

it's tricky
enshrined numeric data types tend to emerge from the underlying processor, $2^8, 2^{16}, 2^{32}, 2^{64}, ...$, the usize wrapper makes sense from a hardware perspective, and would likely be more performant since it's corresponding to XOR and AND cpu instructions rather than pattern matching branches.
but from a type theoretic perspective, a sum type is the cleanest well-constrained representation of a binary field element. it uses the type checker to signal to the compiler the valid states of the type. the existing implementation enforces two states in its construction, but not its implementation. that is to say while you can't construct an invalid field element via BinaryField::new, it is possible to construct or mutate one through other functions as, by definition, its cardinality depends on usize.
a ternary field and, by extension, all prime fields, would ideally be defined in this way. using product types wouldn't work for prime fields bc the cardinality of a product type is definitionally not prime. however, obviously this doesn't scale in rust. recursive types are poorly handled and a prime field sum type with literally<PHONE_NUMBER>37316195423570985008687907853269984665640564039457584007908834671663 elements is ofc impossible.
so there's a balance to be struck. personally, i'd write a ternary field in the same way (sum type), but anything beyond single or low double digit primes is off the table imo. however, i do think the prime field type should be generalized in a way that accepts arbitrary internal field element types to generalize. ie PrimeField<BinaryField>, PrimeField<U256>, etcetc. ofc there's no way to really constrain the huge primes the same way, but i think where it's feasible we should constrain it to a sum type.
(or we could just do BinaryField(bool) lol)


chore(main): release 1.22.2

:robot: I have created a release beep boop
1.22.2 (2024-12-30)
Bug Fixes

deps: replace all (#1118) (b712981)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.22.2
:sunflower:


Change main CFN template efs-file-manager.yaml

As per the implementation guide.
before
efs-file-manager.yaml
after
simple-file-manager-for-amazon-efs.yaml


Residual light exists after switching profile in AlienFX Control

Describe the bug
After changing profiles the residual light from the previous profile is not cleared unless the stuck keys are pressed.
To Reproduce

Set a profile with starfield effect
Set another profile with fill effect
Start with starfield profile and switch to fill profile

Expected behavior
I expect all keys to be refreshed and darkened (in fill profile) or lightened (in fade profile) but the residue of starfield effect is there until I press on those stuck keys, this happens with other effects as well. Refresh key does not work.
Screenshots

The bright orange light and completely darkened keys are from the previous profile. Yellow keys are newly pressed keys.
System (please complete the following information):

Model: M16R1
Model details: Per key RGB
OS: Win11

It's correct.
For some reason, there is no cleanup at grid effect start/restart, so it continues from the current situation.
In case you don't like it, just set same zone to solid color at "Colors" tab, so profile switch will update this zone.


arm/toolchain: update toolchain comment to avoid confusion

Summary
arm/toolchain: update toolchain comment to avoid confusion
1. add 'ARM' prefix to choice menu
2. rename 'Generic Clang toolchain' to 'LLVM Clang toolchain' to avoid confuse with CONFIG_ARM_TOOLCHAIN_ARMCLANG

Signed-off-by: chao an<EMAIL_ADDRESS>Impact
N/A
Testing
menuconfig

ci break is fixed here:
https://github.com/apache/incubator-nuttx/pull/7422
let's merge this simple change to save the server loading.


Slow to Recognize Barcode Mostly in iOS

We're using the plugin found in Xamarin.
https://www.nuget.org/packages/ZXing.Net.Mobile
Many of our users are discovering that the camera is slow to pick up barcodes in comparison to the apps on iOS devices. Is this a known issue? What can I do to fix it?
Some users complain on Android as well but not enough for me to think the problem exists in both places. Just wondering if there is a way to optimize the code or implementation.

+1

The slower in field scan performance of zxing in general is due to the inability to read blurry codes. All codes must be in camera focus in order to get a decode result. Zxing is also not rotation aware. It will not decode a 45° rotated barcode. There is no way to optimize it, other than providing a working object detection.
To get those detection going, deep mathematical knowledge and know-how is required. Here is an example of what it takes:
https://www.ma.utexas.edu/users/rward/barcode

Thanks for reporting this issue!  Unforunately it took me way too long to respond 😭.  Sorry, I apologize!  Recently the source code for this project was completely refactored to modernize it.  Many PR's were included in this effort, and many bugs were hopefully fixed.  Please try out the latest 3.x series of NuGet packages (currently in prerelease).  To try and make the project more maintainable in my spare time going forward, I've decided to close all existing issues to start with a clean slate.  If you're still experiencing this issue on the newest version, please open a new issue with as much detail as possible.  Thank you for your patience and understanding!  Happy scanning!


Look at using go:embed to embed templates into binaries

Since our templates are pretty small, and we have to distribute them through RPM currently, it might be better to simply embed them into the binaries themselves.
For example, in this line, we read in the admin template for admin notifications:
https://github.com/shreyb/managed-tokens/blob/568988e96a679f5678d4c46ce73b86ea942dfdfd/internal/notifications/admin.go#LL120C30-L120C30
Since all templates are read in the internal/notifications package, we could move all the templates in to the internal/notifications directory to clean up the namespace.
This would also allow us to clean up the fields of the notifications.email type and remove the templatePath and templateStruct fields.  For the first, if we use embed and read the template file somewhere in prepareServiceEmail in emailManager.go, and declare and define the struct as we already do there, *email.prepareEmailWithTemplate can become a function (rather than method on *email), and the signature of it would be something like
func prepareEmailMessageFromTemplate(tmplPath string, tmplStruct any) (string, error)

This would not only be cleaner for the service EmailManager, but it would also allow us to reuse the proposed prepareEmailMessageFromTemplate for the admin messages as well.

Can also use go:embed to bake version string in from text file, rather than injecting a build variable.

Finished first part - using go:embed for templates.
Now need to:

[ ] Unit test any added funcs (like in notifications package)
[ ] Use go:embed for version string


HACK: Disable old abi generation and see what breaks.

Need to get to where disabling these bits causes us to generate functions on buffer_views. Currently, kind of doesn't.
Simple repro through the new path: https://gist.github.com/stellaraccident/698146598ec460fd97e7bc42c1b295ab (sigs.mlir)
./iree/tools/iree-translate --iree-mlir-to-vm-bytecode-module --iree-vm-bytecode-module-output-format=annotated-mlir-text ~/tmp/sigs.mlir

I think this is out of date now?


[4.2] SR-5829: Fix NSString.commonPrefix(with:options:)

Also implement .caseInsensitive option.

(cherry picked from commit 944c1093e2473c4d9134adb638f9e8b93bbf3f2c)
(cherry picked from commit 908ffcb94ca517b86d438899129443e9e4fdea1b)

@swift-ci test 4.2

@swift-ci test and merge


Update heading to match other headings

Coverage remained the same at 29.46% when pulling cd1fe0a79dd024e1a0365507bae6578b34decdf3 on frewsxcv:patch-1 into 03f5de7dae6894a3f3993f779c1ebb37646de73b on django-extensions:master.

Already done. Thank you.


v1.1 release?

I see that there's a 1.0 tag, but it's pretty far off master.
Are you interested in maintaining regular releases? If so, would you mind tagging a new one soon?
Thanks for all your hard work!

+1
Just discovered an issue I was having (#952) was fixed but not in a tagged release yet. I can use master for now but would prefer not to in production.

+1

+1
beside this I think it helps if we have a reliable versioning system and release time to time

+1. I use golang/dep and it'll pull the latest tag by default, so it would be nice to keep doing them from time to time.

@jinzhu btw, I could help if you want :)

Hello @mehdy
Thank you, I would like to have regular releases after gorm v2.0, but don't have much time for this yet, hopefully, this could be done soon.

@jinzhu :+1: . great, so if you needed a hand just notify me.

At this point the the docs are (somewhat significantly) different than whats in the 1.0 release tag. Since this is a pretty popular project, seems like properly versioned releases would make life a lot easier for a lot of people. I'm saying that selfishly, but seems like other people ^^ agree. At the very least, can tags be created for stable minor releases until v2 comes out? Thanks for the great work @jinzhu

Hi, I'd love to have some minor versions tags for gorm too. Since dep is quickly gaining interest and usage, it would be a good thing.

Will start this after v2 release.
Thank you for your report.


Make compression algorithm configurable for parquet format

Motivation
In the parquet format the compression is always gzip. The compressor mechanism passes through the hadoop library that has a memory leak for the gzip codec, see https://issues.apache.org/jira/browse/HADOOP-12007
There's no fix available yet. The only way to avoid the leak it would be to use another algorithm.
Modifications

Added new config option parquetCodec (similar to ´AvroCodec´) that accepts a String. The string must be a available compression algorithm. The default value is still gzip for compatibiliy.
Added docs

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs)

After more testing I realized that we don't really hit the mentioned bug because usually there's no native hadoop library in the Pulsar container. In that case a simple GZIPOutputStream is used.
I think we can still merge this pull but there's no need to update the docs

Oh well :) Could you still add the new configs also to /docs/cloud-storage-sink? Thanks

Oh well :) Could you still add the new configs also to /docs/cloud-storage-sink? Thanks

done!


Bullets

Hello guys!
I saw a nice example of Swipeable with dots in here in 'Demo 7'. I searched in the docs/files and didn't find the implementation of these dots.
Do we have plans to implement it? I think is something default in the web, it's would be very nice!
I've studied some react swipe libs to implement in my project, and i prefer react-swipeable-views, congratulations! :)

The source code is right here https://github.com/oliviertassinari/react-swipeable-views/blob/master/docs/src/demo/DemoAutoPlay.js#L59-L63. Feel free to copy the component for your own needs 😄 .


Support type applications with<EMAIL_ADDRESS>

Fixes #204

Seems that type application syntax was added in purescript-language-cst-parser v0.13.0

This will also probably require to upgrade the vscode-ide-purescript dependencies in packages.dhall as well as in the package.json

Thanks, missed this, it seems amazing the change is so simple to bring in :)

it seems amazing the change is so simple to bring in :)

Yes! So satisfying ☺ Solid shoulders we stand on 💪


Fix obj name in ok-to-test PR report

Fix obj name in ok-to-test PR report
fixes #426

/approve

/merge


feat: add vCluster CLI

Signed-off-by: Batuhan Apaydın<EMAIL_ADDRESS>
Description
add vCluster CLI
Motivation and Context

[x] I have raised an issue to propose this change, which has been given a label of design/approved by a maintainer (required)
Fixes #526

How Has This Been Tested?

Are you a GitHub Sponsor (Yes/No?)

[ ] Yes
[x] No

Types of changes

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

Documentation

[x] I have updated the list of tools in README.md if (required) with ./arkade get -o markdown
[x] I have updated the list of apps in README.md if (required) with ./arkade install --help

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

[ ] I have tested this on arm, or have added code to prevent deployment

Hi @developer-guy CI is failing for this PR, please can you take a look?

seems ok @alexellis

kindly ping @alexellis

LGTM, thank you.

We have a bunch of other PRs and issues that need someone to check them over and reply. Could you take a few minutes to review?

Of course ✌


Add quickstart.rst to test scripts

Description
Currently, the docs file docs/getting_started/quickstart.rst never gets run during the testing routine. This can lead to build breaks after merging in PRs and calling invoke docs. This file should get run as part of the invoke test-readme task.

Closing because of the migration to gitbooks, testing gitbooks scripts is tracked in #199


[Question] Ignore if key is pressed

Is there a way I can modify the program so that it doesn't abort the macro if a key (except for F9, of course) is pressed?

I assume you mean in the reply mode. Again, this project was just a quick hack and I have no intention of maintaining this, so be aware of potential problems. But I think you need to do something like this. (didn't try to compile, but you can probably figure out the rest)
You need to modify this part:
			printf("Aborted by keyboard action\n");
			break;

Replace it with something like this   :
input_event ev;

			if( read(pfds[0].fd, &ev, sizeof(struct input_event)) != sizeof(struct input_event))
				{
					printf("Error: \n");
					break;
				}

				if( ev.code == KEY_F9))
				{
                                        printf("Aborted by keyboard F9\n");
					break;
				}

Thank you, made a fork adapting the change!


Add option to view available color schemes

Right now there is no way to view the available color schemes that the user can use. This commit adds an option to do so.

@hugo-vrijswijk,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@hugo-vrijswijk, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

The next week is too looooong.

Looking at this now. I've merged it and added an option to suppress the chattering errors when parsers fail to parse so when the INI parser misses against the Iterm files (since it goes first by alphabetical order in the reflective loading of the parsers), it doesn't spew output that disrupts the format of the table.

OK, manually merged.


Not able to read from vault via spring cloud using profiles

Hi Team,
I have one microservice which get the config from vault via spring cloud.
It works fine without any profile. I need to fetch the details from vault on based of profile.
So I created folder structure in vault like /secret/application/dev and also /secret/microservicename/dev inside this I have all configurations.
So problem is I am unable to find it on profile basis from vault.
Can you please help?
Basic configuration for spring cloud server is as below-
spring.profiles.active=vault,git spring.cloud.config.server.vault.host=localhost spring.cloud.config.server.vault.port=8900 spring.cloud.config.server.vault.order=1 spring.cloud.config.server.git.order=2 spring.cloud.config.server.git.uri=https://giturl spring.cloud.config.server.git.username=username spring.cloud.config.server.git.password=password spring.cloud.config.server.git.searchPaths=configuration,iam server.port=6565
I have started the microservice in dev profile.
Thanks

Please do not cross-post. Duplicate of https://github.com/spring-cloud/spring-cloud-vault/issues/373.


Enable embargoed/unembargoed plashets

@vfreex to support https://issues.redhat.com/browse/ART-2049

New version pushed


Release on PyPI

I'm using this package as a dependency, so it would be useful to be able to install with pip install bg-atlasgen.

What are you using it in?

What are you using it for?

A pipeline (private for now) to create an atlas from scratch, i.e. from raw data to packaged atlas, not just from existing atlas files. It would be useful to move atlas_scripts to another top level dir, and release the utilities as a stand-alone package on PyPI.

Going to close this as it has now been resolved with the release of brainglobe-atlasapi :partying_face: https://github.com/brainglobe/brainglobe-atlasapi


ListenerId is mandatory for this action

Apply requestTimeout to an exists albconfig caused "Message: ListenerId is mandatory for this action" error.
Thanks.

requestTimeout is a listening attribute, so it should be configured in the spec.listeners field of albconfig and specify the port and protocol of listener. Here is a simple configuration example:
apiVersion: alibabacloud.com/v1
kind: AlbConfig
metadata:
  annotations:
  ......
spec:
  config:
    ......
  listeners:
  - port: 8080
    protocol: HTTP
    requestTimeout: 60

Additionally, this error often occurs when the listener ID cannot be obtained after the update of the listener fails. If the above answer does not solve your problem, you can provide more log information to assist in troubleshooting.


I want to learn from you about model lightweight

Your work is so great. Thank you for your work. Will your model conversion code be open source? I just came into contact with lightweight and want to learn from you.

Hi, thank you for showing interest in this project. The model conversion can be done by just some Linux commands. No need to write code. Please take a look at the examples in this link: Deployment with TensorRT.

Thank you for your reply！！！
Is the onnx model input tensor you provided dynamic? If I want to change the input size to 480 x 752, do I only need to modify the minshapes parameter

I don't quite remember. You can download the onnx models, and use netron to visualize them and check.

Thank you for your reply！！
i use the netron to visualize them. the input tensor should be dynamic.

Would it be convenient for you to send me a copy of your model and convert it into onnx code?
I want to learn about your work. Thank you very much

Sorry, I don't have that code at hand, but the pipeline should be standard. You train a model in pytorch or tensorflow, and those libraries provide onnx exporting functions. For example, you can take a look at https://docs.microsoft.com/en-us/windows/ai/windows-ml/tutorials/pytorch-convert-model.

Thank you for your reply!
I have successfully converted my model into onnx.


VIC overwrites veg_lib values of LAI, albedo, and vegcover with those of the current cell

The function read_vegparam() overwrites the values of LAI, albedo, and vegcover in the veg_lib structure with those from the veg_param file for the current cell, if they are listed there and if LAI_SRC, ALB_SRC, or VEGCOVER_SRC are set to FROM_VEGPARAM.
In olden times this was not a problem - the veg_lib structure's function was re-purposed to contain climatological values of LAI and albedo for the current cell.  However, the new veg_hist feature in release 4.2 allows for the values of LAI, albedo, and vegcover in the veg_param or veg_hist files to be -1 (the "nodata" flag for these quantities), which was intended to indicate to VIC that it should take the value from the veg_param file if "nodata" in the veg_hist file, or from the veg_lib file if "nodata" in the veg_param file.  The reason for this is that some global datasets of these quantities (e.g. MODIS products) have nodata values in some cells on some dates due to cloud cover or other poor retrievals.
Unfortunately, for this to work properly, we can't have VIC overwriting the veg_lib structure with the current cell's veg_param values.  If we encounter a cell for which some of these values are "nodata", VIC will use what's in veg_lib, which will be the veg_param value from the last cell that had a valid value.
To fix this, I propose we add some 12-element arrays to the veg_con structure, to store the values of LAI, albedo, vegcover, and Wdmax (which depends on LAI) of the current cell without overwriting the veg_lib values.  So, the veg_lib structure will essentially be a read-only copy of the veg_library file in memory.
I propose that this be included in the upcoming hotfix 4.2.c.

Am I correct in assuming you'd prefer that I create my branch off of the official master, and that I should not include the contents of my other 2 (pending) pull requests?
Also, are my 2 pending pull requests waiting on me for anything?  Are they essentially approved or is there some chance you will want me to change something?

branch off master and issue against 4.2.c.
@bartnijssen and I will take another pass through your other prs asap.

@tbohn - responding to this issue.  I think we want to ovoid any time information inside vic_run.  In my opinion, the solution here needs to fill a single set of scalar veg params that go into vic_run.  However the driver decides to do that is up to the individual driver.

This is just a fix to 4.2... I can find a different fix for 5.0...
On Dec 5, 2015 8:01 AM, "Joe Hamman"<EMAIL_ADDRESS>wrote:

@tbohn https://github.com/tbohn - responding to this issue. I think we
want to ovoid any time information inside vic_run. In my opinion, the
solution here needs to fill a single set of scalar veg params that go into
vic_run. However the driver decides to do that is up to the individual
driver.
—
Reply to this email directly or view it on GitHub
https://github.com/UW-Hydro/VIC/issues/319#issuecomment-162215928.

@jhamman - did you see my response to your comment?  Are we on the same page, that this is 4.2 and thus pre- veg_hist overhaul?  The overhaul I will do of veg_hist in 5.0 will obliterate any of the changes I make to 4.2.  I'm just trying to get 4.2 to work correctly.

Okay @tbohn - I'm tracking with you.  I'll review #321 now.


Add review process documentation

LGTM, do we want to add the review_process.rst file to the index, so that it shows up in ReadtheDocs?

Indeed! Let me add the reference.


Days on schedules rolling past midnight are not intuitive

Problem

When viewing a venue, it is possible that the opening time in the viewer's timezone is past midnight. This is currently marked with a 'moon' icon over the time and a tooltip upon that icon. However this is not intuitive or accessible, and the explanation is only available on the tooltip, which is not available to users with motor impairment that may only use a keyboard, or those using other assistive technologies, additionality it is not available to touch-screen-only technologies like smart phone, tablet, or Walmart self pay kiosks that we are very popular on.
To Reproduce

Create to a venue that has an opening time of 11pm PST

Then look at it from a EST+ timezone

Expected behavior

User's would expect when the start time shifts past midnight, the day stated before would be the following day.
In the example above, it should say Saturday 2am - 6am (moon)
Environment:

OS: All OS's
Browser: All Browsers
Version: Al supported versions

Suggested solution

Isolate the day into it's own component that takes the fully qualified time. This can handle take the UTC time and shift it forward according to timezone, similar to the time component.
The risk in this is more processing for every venue rendered; a solution to this could be extrapolating the timeZone shift into a separate component/type/function and then pass this into both the day and time components to prevent double processing.
Testing Considerations
Happy path

[x] PST timezone venue in EST
[x] EST timezone venue in UTC
[x] UTC timezone venue in CEST
[x] Times that do not pass midnight

Sad path

[x] Venues that do not have a schedule/day
[x] Daylight savings

For more information and someone to inform when fixed, message redm#0001
Ticket number: 1283, closed late 27th May.

Resolved


Long Sequence in SQuAD

Case: SQuAD task, sequence length > 512
Does your script utilizes cached memory/extended context in a segment, such that the predictions are inferred from sequence longer than 512 tokens?
If yes, where is the code that achieves this?
If not, what do you suggest to utilize cached memory to perform QA task?
Thank you for such a great work!

We are not using cached memory for finetuning yet. Cached memory was used during pretraining to improve modeling long sequences. Once training is done, the model is better for long sequence modeling even with memory removed.
Including cached memory for finetuning is also an option, but not included for now. I would suggest using the same mechanism as in pretraining but backpropagating the gradients across segments.

I am trying to understand how previous segments are aligned to feed into the model.
Input Sentence Length: 1024
max_seq_length: 512
mem_len: 256
Am I correct to understand it to have 3 segments?  [0:512], [256:768], [512:1024] ?
And the data need to be passed into the model 3 times like sliding windows?
But this would make it unable to infer answer from context that is after the window.
Can you advice on how it long sequences can be processed to infer?
Sorry for asking this which might be a foundation knowledge because I am relatively new to the architecture. Btw do you plan on releasing code on using cached memory for finetuning?

@ecchochan The memory cache is actually origins from the Transformer-XL paper. I think you could dig into details from the paper. If I get it right, there are only two segments [0:512], [513:1024]. And the cached memory is [256:512] for the second segment though. As for the question

But this would make it unable to infer answer from context that is after the window.
The cached memory aims to catch long-dependency. The problem will be stuck whether there is cached memory (just like the BERT arch, which has a fixed length 512), right?


Is there exported SwiperOptions for type declarations ?

like this:
import type { SwiperOptions } from 'swiper'

you can export the types from the swiper/vue package. It should include the types if you want to manually import them.

You can also check out the export within the main package.json here: https://www.npmjs.com/package/swiper?activeTab=code
Thanks,
CP


Add Names under logos on Alliance Page

Expected Behavior
Shows names, italicized in smaller font than the average paragraph size.
Current Behavior
What is the current behavior?

@tjlahey can you add that mockup you made?


unable to create rate-limit-advanced plugins at route level with deck for distributed management

I am from API team and my API gets deployed to EKS via pipeline.
In the same pipeline I have deck jobs to create services, routes with tags for distributed management.
All works fine until there is no dependency on any global entities like consumers, ca_cert etc.
Now the problem statement is
When I try to create a rate limit advanced plugin on route level in same pipeline its throws error
$ deck gateway diff --kong-addr $KONG_ADMIN_URL --headers Kong-Admin-Token:$KONG_ADMIN_TOKEN --tls-skip-verify  plugin.yaml --parallelism=1
Error: building state: consumer xyz.abc.com for plugin rate-limiting-advanced: entity not found
below is plugin.yaml

_format_version: "3.0"
_workspace: PBG
_info:
select_tags:

app1
plugins:
config:
limit: [50]
namespace: WQ9PoXJUmtVl3fA0utK7ElXa7hpsAyXZL
path: null
redis:
cluster_addresses:
- pb-kong-redis-0001-001.xyz.cache.amazonaws.com:6379
- pb-kong-redis-0002-001.xyz.cache.amazonaws.com:6379
password: 1234QWERR
timeout: 2000
sync_rate: -1
window_size: [1]
consumer: xyz.abc.com
enabled: true
name: rate-limiting-advanced
protocols:

http
https
route: app1DeckPoc

Note: consumer 'xyz.abc.com' is created manually by logging into kmanager with no tags,
since these are global entities it can be used by n number of applications and routes and cannot be part of any particular application state yaml file.
please advise a way to address such scenarios.
Thanks in advance

This should be the same case as https://github.com/Kong/deck/pull/1124 right? @AntoineJac

@Tieske  confirm it is indeed the same case than #1124

Thanks for the information.
can you please tell when "  default_lookup_tags:" feature will be release for customers to fully leverage advantage of deck

cc @teb510 for visibility

default_lookup_tags has shipped


Cannot join session with microphone disabled

I believe this could be a similar to the issue at https://github.com/networked-aframe/networked-aframe/pull/201.
If the microphone is blocked, the user isn't detected in the logs, and can't connect to the room. However, if joining with microphone on, and then blocking, the user stays in room.
Any help with this would be greatly appreciated.

The adapter moved again in the networked-aframe repository. I'm closing all issues from this repository.
See this issue too https://github.com/networked-aframe/networked-aframe/issues/55


Paging through terminal scrollback

I'm hoping to use micro as a lightweight C IDE of sorts but there is one seemingly missing feature that is preventing this for me and that is the apparent lack of the ability to page through the full output of commands run with the term command. For example, in my ~/.config/micro/bindings.json I have the line:
"Alt-x": "command:hsplit,command:term sh -c 'cd /home/dan/src/IKD/default;make'"

but when I execute that command I can only see the bottom part of the output of make, I am unable to use the Page Up and Page Down keys to scroll through the rest of the output in the terminal window.
Am I missing something or is this a feature request?

Yes this is an annoying limitation of the internal terminal. I'll notify you via this issue if that gets implemented. In the meantime, you could run tmux or another terminal multiplexer in, and use the multiplexer's keybindings to scroll.

It looks like micro is very close to working how I'd want. I was hoping to avoid having to use tmux or screen as you might guess.
Good to hear this is a planned feature and thanks for keeping me updated!


Do you need to reslice HCP MGH data?

From a person involved in the HCP preprocessing (although not for the MGH data):
Generally you could say you can almost always ignore the transform in the nifti header. Typically it has been written automatically by the dicom conversion software, which in turn have taken it from the dicom header. In the software I've written I've just ignored it, although I usually pass it along just in case someone in the future would like to use it.
I'd say with 99% certainty that you can just ignore it in this case.


Addition of Bitcoin Jobs Section

Addition of Jobs section for Bitcoin Only companies.  Would be a nice reference point for Developers and more looking for Jobs in the Space.

I like the idea but it may require significant maintenance and would rely on companies contacting bitcoin-only to have jobs taken down once filled which may not regularly happen.
I remember that Justin Moon made a twitter thread not long ago where companies commented if they were looking for applicants. We could use that list as a starting point if we decide maintenance won't be an issue.

Hmmm, yea i tend to agree with the maintenance part of this. I was scrolling through Twitter and saw his feed, that is what made me think about it.

Hard to maintain. Closing.


tf.train.Checkpoint complain that tf.train.ExponentialMovingAverage instance is not a trackable object

My tensorflow versiong is 2.1.0, I built a model in the standard way of keras subclassing and saved it with tf.train.Checkpoint. It works fine in the following code:
model = ... # a subclassing model instance
ckpt = tf.train.Checkpoint(model=model)
for epoch in range(total_epochs):
    ...
    ckpt.save(path)

When add the code of moving average as following:
model = ... # a subclassing model instance
ema = tf.train.ExponentialMovingAverage(decay=0.999, zero_debias=True)
ckpt = tf.train.Checkpoint(model=model, ema=ema)
for epoch in range(total_epochs):
    ...
    ckpt.save(path)

cause this error:
ValueError: `Checkpoint` was expecting a trackable object (an object derived from `TrackableBase`),
got <tensorflow.python.training.moving_averages.ExponentialMovingAverage object at 0x7f63c8070a58>.
If you believe this object should be trackable (i.e. it is part of the TensorFlow Python API and manages state), please open an issue.

Is that tf.train.ExponentialMovingAverage incompatible with tf2? What's the best practice to do moving average in tf2?

@naturomics
Can you please share colab  link or minimal standalone code to reproduce the issue in our environment.It helps us in localizing the issue faster. Thanks!

@ravikyram
Please see this gist.

I have tried on colab with TF version 2.1.0 , 2.2-rc2 and was able to reproduce the issue.Please, find the gist here. Thanks!

Any update?

I'm also interested in saving the EMA variables in a checkpoint.

Was able to reproduce your issue in Tf Nightly 2.6.0-dev20210525, please find the gist here. Thanks!

Hi @naturomics ! As this document suggests although EMA objects are not directly trackable ,you can use average() to return the moving average variables for your model weights, which you can then checkpoint. Attaching Modified Gist for reference. Thanks!

Is there a reason they can't be trackable, or just no one has implemented it yet?
It seems natural to make them trackable, given that the documentation shows you how to do so. Trackability will also serialize the decay parameter, which would be nice.


What does the port firewall coming from GCM server?

I have a problem with port firewall for receiving notification from GCM server.
My private network use allowed policy firewall, so I try to config follow this link
(http://esupport.trendmicro.com/solution/en-US/1060693.aspx) .
I hope it works, but it's not.
I search in many way to solve, but I couldn’t make head or tail of it.

The GCM needs the following connections:

port: 5228, host: mtalk.google.com
port: 443, host: android.googleapis.com

Great thank, Finally I got it. > <

UPDATE: GCM is also using:

port: 443, host: android.client.google.com

this is about devices receiving push notifications.. My server is blocking attempt to initiate push request to GCM server...What ip/port I should open to send push notification request to GCM?


incorrect result

ipxe-efi.zip

see .text:000000000001D0D4  - error

use for indirect call not only comment but  IDA command: (example)
op_stroff	(0X1D130,	0,	GetStrucIdByName("EFI_BOOT_SERVICES"),	0);

.text:0001D127           mov     r8, [r13+10h]
.text:0001D12B           xor     edx, edx
.text:0001D12D           mov     rcx, r13
.text:0001D130            call    qword ptr [rbp+140h] ; EFI_BOOT_SERVICES->LocateProtocol
changed to
.text:0001D127            mov     r8, [r13+10h]   ; Interface
.text:0001D12B            xor     edx, edx        ; Registration
.text:0001D12D           mov     rcx, r13        ; Protocol
.text:0001D130            call    [rbp+EFI_BOOT_SERVICES.LocateProtocol] ; EFI_BOOT_SERVICES->LocateProtocol
in this case Ida automatically comment parameters.
But previously you need load struct description from Tlib.

Now I am handling cases where the call to "EFI_BOOT_SERVICES" occurs at an offset relative to "EFI_SYSTEM_TABLE", but sometimes it will be necessary to set the types manually. I hope that in time I will fix it.
I added this to the code, very useful, thanks.


CIA-284: Dedicated class & tests for ansible-playbook

Created a dedicated AnsiblePlaybook class that captures all previous functionality in a cleaner, more concise manner.

Updated commands to use new class rather than shell out to ansible-playbook directly.

Removed unused creation of MOLECULE_TAGS environment variable.

Moved _create_playbook_args out of core, all logic now contained within AnsiblePlaybook class.

Added tests for all the new/moved things.

Great job! :+1:

:+1: Nice work.  Glad to see you got the tests added.


Check error on messaging for #65

It was easier just to make this change manually! It's in there , though


cluster create can't access script on S3

Went to generate a new cluster v3.8.0 and the setup script that I used to generate a cluster v3.5 is no longer working:
WaitCondition received failed message: 'fetch_and_run - Failed to download OnNodeConfigured script 1 using aws s3. Please check /var/log/cfn-init.log in the head node, or check the cfn-init.log in CloudWatch logs. Please refer to https://docs.aws.amazon.com/parallelcluster/latest/ug/troubleshooting-v3.html#troubleshooting-v3-get-logs for more details on ParallelCluster logs.' for uniqueId: i-0c83383427d71dbf9
I have checked the file in S3, and nothing has changed from when I used it successfully to create my cluster in 3.5. I came across a couple of issue reports with respect to scripts that suggested removing additional comments (#) from the script and converting from windows to linux formatting (ran dos2unix on it to make sure) but no joy. Attached is my cfn-init.log file as well as my redacted yaml below:
Imds:
  ImdsSupport: v2.0
HeadNode:
  InstanceType: c5.2xlarge
  Imds:
    Secured: true
  Ssh:
    KeyName: mertz_key
  LocalStorage:
    RootVolume:
      VolumeType: gp3
  Networking:
    SubnetId: subnet-659e6f4a
    ElasticIp: true
    AdditionalSecurityGroups:
      - sg-e2f0df90
  Iam:
    AdditionalIamPolicies:
      - Policy: >-
          arn:aws:iam::2710136xxxxx:policy/DomainCertificateSecretReadPolicy-modulus-AD
  CustomActions:
    OnNodeConfigured:
      Script: s3://parallelcluster-10552b48cfa2e9aa-v1-do-not-delete/active-directory.head.post.sh
      Args:
        - arn:aws:secretsmanager:us-east-1:2710136xxxxx:secret:DomainCertificateSecret-modulus-AD-bzzAOd
        - /opt/parallelcluster/shared/directory_service/domain-certificate.crt
Scheduling:
  Scheduler: slurm
  SlurmQueues:
    - Name: modbind
      AllocationStrategy: lowest-price
      ComputeResources:
        - Name: modbind-cr-0
          Instances:
            - InstanceType: g4dn.xlarge
          MinCount: 0
          MaxCount: 100
          DisableSimultaneousMultithreading: true
      ComputeSettings:
        LocalStorage:
          RootVolume:
            VolumeType: gp3
      Networking:
        SubnetIds:
          - subnet-659xxxxx
        AssignPublicIp: true
        PlacementGroup: {}
        AdditionalSecurityGroups:
          - sg-e2fxxxxx
      CustomActions: {}
    - Name: parameters
      AllocationStrategy: lowest-price
      ComputeResources:
        - Name: parameters-cr-0
          Instances:
            - InstanceType: c6a.24xlarge
          MinCount: 0
          MaxCount: 5
          DisableSimultaneousMultithreading: true
      ComputeSettings:
        LocalStorage:
          RootVolume:
            VolumeType: gp3
      Networking:
        SubnetIds:
          - subnet-659xxxxx
        AssignPublicIp: true
        PlacementGroup: {}
        AdditionalSecurityGroups:
          - sg-e2fxxxxx
    - Name: modbind-spot
      AllocationStrategy: lowest-price
      ComputeResources:
        - Name: modbind-spot-cr-0
          Instances:
            - InstanceType: g4dn.xlarge
          MinCount: 0
          MaxCount: 100
          DisableSimultaneousMultithreading: true
      ComputeSettings:
        LocalStorage:
          RootVolume:
            VolumeType: gp3
      Networking:
        SubnetIds:
          - subnet-659xxxxx
        AssignPublicIp: true
        PlacementGroup: {}
        AdditionalSecurityGroups:
          - sg-e2fxxxxx
      CapacityType: SPOT
  SlurmSettings: {}
Region: us-east-1
Image:
  Os: centos7
DirectoryService:
  GenerateSshKeysForUsers: true
  DomainName: modulus.ad.com
  DomainAddr: ldaps://modulus.ad.com
  PasswordSecretArn: >-
    arn:aws:secretsmanager:us-east-1:2710136xxxxx:secret:PasswordSecret-modulus-AD-MM2LIh
  DomainReadOnlyUser: cn=ReadOnlyUser,ou=Users,ou=MODULUS,dc=modulus,dc=ad,dc=com
  LdapTlsCaCert: /opt/parallelcluster/shared/directory_service/domain-certificate.crt
  LdapTlsReqCert: hard
SharedStorage:
  - Name: Efs0
    StorageType: Efs
    MountDir: /shared
    EfsSettings:
      FileSystemId: fs-c3exxxxx

and here is the script that I am failing to download/run:
#!/bin/bash
set -e

CERTIFICATE_SECRET_ARN="$1"
CERTIFICATE_PATH="$2"

[[ -z $CERTIFICATE_SECRET_ARN ]] && echo "[ERROR] Missing CERTIFICATE_SECRET_ARN" && exit 1
[[ -z $CERTIFICATE_PATH ]] && echo "[ERROR] Missing CERTIFICATE_PATH" && exit 1

source /etc/parallelcluster/cfnconfig
REGION="${cfn_region:?}"

mkdir -p $(dirname $CERTIFICATE_PATH)
aws secretsmanager get-secret-value --region $REGION --secret-id $CERTIFICATE_SECRET_ARN --query SecretString --output text > $CERTIFICATE_PATH

cfn-init.log

@chenwany thanks so much for catching that missing parameter -- you saved my bacon. Once I put in the call to the S3Access the cluster compiled for me.


Deployment status

Describe the bug
No matter how many prompts i use or times i press the deploy button, i cannot deploy my app. I had it deployed earlier, but the link suddenly stopped working. I now am unable to deploy anything and get no response from the chat. It simply says "checking deployment status" does that for about 20 seconds, and provides no further response.
I have tried refreshing the page completely. it loads the project, but refuses to deploy it.
Link to the Bolt URL that caused the error
https://bolt.new/~/bolt-nextjs-shadcn-ds9z6m
Steps to reproduce
go to https://bolt.new/~/bolt-nextjs-shadcn-ds9z6m
try to deploy
Expected behavior
the app successfully would deploy to netlify
Screen Recording / Screenshot

No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 108387377,
  "usedJSHeapSize": 103116869,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = JessePimenta
Chat ID = 522d11aa3399

Additional context
No response

Hi @JessePimenta,
Appreciate the feedback. The team is aware of this issue and tracking it here: #1022. In the interim, you could try accessing your Bolt project by going to stackblitz.com and navigating to the Collections tab on the left-hand side and then opening the Bolt Collection. From there, you can open the project of interest in StackBlitz, click the download icon in the file explorer, and then upload the project files to Netlify using their service here.


ARM compiler generates wrong calling convention dispatch for uniform VFP aggregate return across COM interface type.

Issue placeholder. Reproduction case will follow.

Briefly (more on Monday):
Calling a virtual member function of a COM interface type (here ID2D1DeviceContext) that returns a struct of 2 floats is generating incorrect code.
MSVC generates (impl)
As per AAPCS, the floating point aggregate is returned in the VFP registers.
__stdcall DeviceContext::GetSize(/*implicit this*/) {
    s0 = width;
    s1 = height;
}

Clang generates (call)
struct two_floats ret, temporary;
DeviceContext::GetSize(/*implicit this*/, &temporary);
memcpy(&ret, &temporary, sizeof(return));

The call is generated with a hidden struct return parameter, and the floating point registers are ignored. A warning is usually emitted that __stdcall is ignored for ARM.
Attempts to reproduce in the same module fail, possibly due to devirtualization.


chore(tests): fix issues in test setup

Due to (https://github.com/node-fetch/node-fetch/issues/1624) pinning the versions of node the tests run on to avoid false negatives on tests.

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

Project coverage is 80.14%. Comparing base (0914019) to head (5c967f8).
Report is 1 commits behind head on alpha.

Additional details and impacted files
@@           Coverage Diff           @@
##            alpha      #97   +/-   ##
=======================================
  Coverage   80.14%   80.14%
=======================================
  Files          20       20
  Lines         534      534
  Branches       97       97
=======================================
  Hits          428      428
  Misses        102      102
  Partials        4        4

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


[docs] Add more interoperability examples

I'm tired of people think JSS can't interop with their stack.
#YOLO
It should be a quick escape hatch for a lot of people (tests, wrong settings, prototyping, etc.).
Also, it should unlock external people building themes on top of Material-UI, like they do with Bootstrap.
Add a CSS interoperability example
Add a CSS modules interoperability example
Add a global CSS interoperability example

Closes #9433

There is a big problem with that: you are making class names part of the public api with this, now every change in a class name  is a breaking change!

Wouldn't examples with passing classes hash be enough? It is actually already usable with any css solution.

There is a big problem with that: you are making class names part of the public api with this, now every change in a class name is a breaking change!

@kof They already are.

Wouldn't examples with passing classes object be enough? It is actually already usable with any css solution.

It doesn't solve the test, wrong settings, prototyping, external theming issue with undeterministic classes.

They already are.

AFAIK only property names which map to an actual class name are, no?

AFAIK only property names which map to an actual class name are, no?

OK, you are right. We make the className a public API when dangerouslyUseGlobalCSS is true. This is the point of the pull request. However, I might not have anticipated all the drawbacks with this. There are many issues for people relying on this API (dangerous). But it can be a "quick-win" for non important use cases. The new API is the name of the stylesheet concanated with the name of the style rule. Each element taken individually are in the public API. Hence, the reunion is already public.

I think we can go with that, it isn't making API much worse, if it will make life of users with simplistic setup much better.
Ultimately, in a better world, there should be no classes based overrides at all, everything should be done over theming. Classes overrides is just fragile by design.

I mean even theme.overrides is fragile, because too flexible. User can break anything.

I can't agree more. I think that we need to warn people about it. Like be aware of the downsides.

I can't agree more. I think that we need to warn people about it. Like be aware of the downsides.

Yes, and work on theming, making it more flexible in a predictable way!

I have been looking into using https://github.com/cssinjs/jss/blob/master/src/utils/createGenerateClassName.js.
One issue I can find is the env indirection const env = process.env.NODE_ENV that seems to prevent dead code element with uglify. I'm not sure what's the best strategy going forward.
The createGenerateClassName implementations can be simple but at the same time is critical. It's something we can discuss for a future PR.

Here are the alternatives to the current solution:

We keep our createGenerateClassName and use JSS version internally
We only keep one createGenerateClassName for the global CSS option and use the public JSS version as default
We have two createGenerateClassName internally one for the default and one for the global CSS option

const env = process.env.NODE_ENV that seems to prevent dead code element with uglify.

True, consider it a bug, will fix it.

just checked, not true - see this is uglified version of class names generator
  var i = n(1),
    u = r(i),
    o = n(10),
    s = (r(o), n(31)),
    a = r(s);
  t.default = function() {
    var e = 0;
    return function(t, n) {
      (e += 1) > 1e10 && (0, u.default)(!1, "[JSS] You might have a memory leak. Rule counter is at %s.", e);
      var r = "c",
        i = "";
      return n && (r = n.options.classNamePrefix || "c", null != n.options.jss.id && (i += n.options.jss.id)), "" + r + a.default+i + e
    }
  }
},

I would go with this:

We only keep one createGenerateClassName for the global CSS option and use the public JSS version as default

@kof I was trying with the repl version of Babel and the repl version of uglifyjs. I could have done a mistake. Using an intermediary variable is, as far as I know, uncommon.
@mui-org/core-contributors What do you want to do on this matter?

Using an intermediary variable is, as far as I know, uncommon.

Its done for a reason, https://github.com/cssinjs/jss/blob/master/tests/unit/createGenerateClassName.js#L36
Rewire needs this.

@kof An alternative
https://github.com/mui-org/material-ui/blob/6f5037b34b46700570603a6400a0e37e71d7a828/src/styles/createGenerateClassName.spec.js#L107-L119


Cargo dist init taking 4.25 minutes

Cargo dist init took 4 minutes 15 seconds to complete
$ cargo dist --version
cargo-dist 0.0.4

Reproduce
I would like to say that you can reproduce it, but it seems to have been a one time thing, any subsecuent tests have yielded times of around ~0.4 seconds.
$ git clone https://github.com/jalil-salame/nsudoku-solve
$ cd nsudoku-solve
$ git checkout 69fbb08
$ rm .github/workflows/release.yml  # Delete previous ci
$ head -n18 Cargo.toml > Cargo.toml.bak # Remove cargo-dist 0.0.2 configuration
$ mv Cargo.toml.bak Cargo.toml
$ time cargo dist init --ci=github

perhaps cargo got stuck doing something else 🤔, but I tried running cargo build on some big repo and launching cargo dist init and that didn't seem to slow down cargo dist too much. There is a chance that rust-analyzer got in the way and was trying to reindex your project or whatever, but that wouldn't explain whole 4 minutes (there are too few dependencies in your project to justify 4min-worth of cargo-related work)
I tried reproducing with
echo 'git clone https://github.com/jalil-salame/nsudoku-solve
 cd nsudoku-solve
 git checkout 69fbb08
 rm .github/workflows/release.yml  # Delete previous ci
 head -n18 Cargo.toml > Cargo.toml.bak # Remove cargo-dist 0.0.2 configuration
 mv Cargo.toml.bak Cargo.toml
 time cargo dist init --ci=github && cd .. && rm -rf nsudoku-solve' >> bench.sh
watch -n1 "source bench.sh"

and let it run for around two minutes, but it always was between 0.4 and 0.6 sec (that includes the time it takes to git clone)

This is almost certainly cargo updating the registry for 4 minutes and us failing to forward the message (as alluded to in #173).

i agree with @Gankra that it was probably cargo updating- i wonder if it'd be useful to have some reporting to the terminal on what's happening to help make issues like this more obvious- or at least a verbose option that sends the stdout from the wrapped commands through

I agree with it being the cargo index, it matches up with me not using cargo build for a while in this PC.
It should forward the cargo stdout, or at least have a tasks indicator: [1/4] Running cargo, so you can debug what is happening.
If nothing else is interesting abot this issue them I am ready for it to be closed.

closing in favor of #173

actually, reading more closely #173 is really a diff feature. i'm gonna keep this open as an issue to implement fwding some of the cargo msging

(I couldn't find the reason why stderr wasn't getting forwarded, I feel like I might be missing a flag in guppy or something...)

Ostensibly fixed in 0.0.6 by #207


BZ-1319546 - test refactoring and extension

Removed testCommandScript() test method as it is already included in KieServerDroolsIntegrationTest.

looks good to me, +1 once jenkins build succeed.


Excavated Chests highlight

Hi, thank you for your great work NeverSink. Excavated Chests blend with the rest of the white items a bit much, some highlight to them would be nice. No rush on this of course. Thank you!

Nothing can be done about this, item filters can't affect chests.
I recommend contacting GGG about it or making a forum thread.


Improving the styling of contributors page

What's the style idea?
We need to improve the fonts and the styling of each contributor's icon. Also a background change can be done so that it looks more appealing to the users. I would also like to work on the footer of that page as well
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

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

Can you assign it to me with gssoc label

Could you please assign me to participate in this project?

@ananya-sh30 "Given my extensive experience as a graphic designer specializing in clubs and committees within our college, particularly adept at color and responsiveness, I believe I'm the ideal candidate to tackle this issue. My track record includes successful projects where I've meticulously handled footer fonts and colors. Assigning this task to me ensures not only a swift resolution but also a high-quality outcome that aligns perfectly with our objectives."

Which background you want to put and what changes you want to do for the contributor icon @ananya-sh30


GUVNOR-2431: Redesign Copy, Save, Rename, Restore and Delete Popups

Fix use of PathProvider.
(Plus change to lamda's)
@karreiro Would you mind reviewing please?

Jenkins please retest this.

1 to merge. Thanks @manstis

thanks @manstis @karreiro


Engine Error

I bought the subscription to extract topics from Portuguese text but your pt model is not working for long text.

I opened the 2 tickets sand its been 4 days but no one is replying there.


Add -prefix-serialized-debugging-options

This commit adds a new frontend flag that applies debug path prefixing to the
paths serialized in swiftmodule files. This makes it possible to use swiftmodule
files that have been built on different machines by applying the inverse map
when debugging, in a similar fashion to source path prefixing.
The inverse mapping in LLDB will be handled in a follow up PR.

See https://github.com/apple/swift/pull/17665 for a related earlier change.

Thanks, I can definitelty see how this can be useful. Is my understanding correct that this effectively implements LLDB's target.source-map setting for binary Swift modules, with the end-goal being that SwiftASTContext will initialize the Swift CompilerInstance with the contents of target.source-map and/or the path remapping dictionary in dSYMs? It looks like the current patch reuses the debug prefix map for this. However, I wonder if this shouldn't be a separate dictionary (are -fdebug-prefix-map options being serialized at the moment?). Finally I wonder how this will work in an expression context in LLDB if there are two dylibs with dSYMs that have different remapping dictionaries. Do we expect to need to support this use-case?

Is my understanding correct that this effectively implements LLDB's target.source-map setting for binary Swift modules, with the end-goal being that SwiftASTContext will initialize the Swift CompilerInstance with the contents of target.source-map and/or the path remapping dictionary in dSYMs?

Yes, that is the idea. I haven't thought about using the dSYM remapping dictionary yet, but I think that could be handled.

It looks like the current patch reuses the debug prefix map for this. However, I wonder if this shouldn't be a separate dictionary

I considered it, but couldn't think of a case where you would want to use a different map for the swiftmodule debugging options than for the regular debugging info. Do you think this is worthwhile?

(are -fdebug-prefix-map options being serialized at the moment?)

They are, this change will skip over the flags during serialization. It may make sense to pull this into a separate commit / PR.

Finally I wonder how this will work in an expression context in LLDB if there are two dylibs with dSYMs that have different remapping dictionaries. Do we expect to need to support this use-case?

That is a case I had not considered. The complexity of handling that would be part of the upcoming PR that modifies LLDB to provide the targets source-map to the SearchPathOptions.SearchPathRemapper, so I think should not require further changes to this PR at least. For the common case of remapping the working directory to . this PR will already take care of relativizing the swiftmodule debugging info correctly and debugging should work when run from the correct working directory.

It looks like the current patch reuses the debug prefix map for this. However, I wonder if this shouldn't be a separate dictionary

I considered it, but couldn't think of a case where you would want to use a different map for the swiftmodule debugging options than for the regular debugging info. Do you think this is worthwhile?

(are -fdebug-prefix-map options being serialized at the moment?)

They are, this change will skip over the flags during serialization. It may make sense to pull this into a separate commit / PR.

I don't think there is a good reason to serialize -fdebug-prefix-map in a .swiftmodule, because the option is for debug info, which is irelevant when importing a serialized Swift AST. (Related side question: Is the debug prefix map applied to source locations inside the serialized AST in .swiftmodule that was compiled with -fdebug-prefix-map?)
But I'm not convinced that repurposing -fdebug-prefix-map is the right design, since our new option is supposed to affect file lookup and search paths as well as source paths in debug info. It feels wrong to have an -fdebug option affecting file lookup.

Finally I wonder how this will work in an expression context in LLDB if there are two dylibs with dSYMs that have different remapping dictionaries. Do we expect to need to support this use-case?

That is a case I had not considered. The complexity of handling that would be part of the upcoming PR that modifies LLDB to provide the targets source-map to the SearchPathOptions.SearchPathRemapper, so I think should not require further changes to this PR at least. For the common case of remapping the working directory to . this PR will already take care of relativizing the swiftmodule debugging info correctly and debugging should work when run from the correct working directory.

LLDB has two mechanisms for remapping paths that operate at different layers:

The target.source-map setting can be set per target (~ executable)
The dsym path remapping dictionary is a property of the symbol file (~ dylib) affects every query to that symbol file, =and the same symbol file could be loaded by different targets.

Supporting (2) is tricky because in the expression context, we don't have a ready mapping between symbol file and imported Swift modules, so it can be tricky to discern which remapping dictionary to apply. However, I think that if you are trying to build a distributed build system, then properly supporting (2) is the way to go, because a properly implemented system where dsyms are automatically fitted with that e correct remapping dictionary can be completely transparent to the end-user.

It feels wrong to have an -fdebug option affecting file lookup.

clang has -ffile-prefix-map now that implies a few of these, do you think we should add something similar to swift? Today it would imply -debug-prefix-map and -coverage-prefix-map. Happy to add that if there's interest

Related side question: Is the debug prefix map applied to source locations inside the serialized AST in .swiftmodule that was compiled with -fdebug-prefix-map?

I'm not 100% I follow, but the debug prefixes we are using are the ones passed via -debug-prefix-map, which get propagated to the Clang importer as -fdebug-prefix-map, which we then avoid serializing.

But I'm not convinced that repurposing -fdebug-prefix-map is the right design, since our new option is supposed to affect file lookup and search paths as well as source paths in debug info. It feels wrong to have an -fdebug option affecting file lookup.

Yes, I see your point. It seems a little messy to add yet another mapping flag for this (this would make 3 now I think) but how about -serialized-debugging-options-prefix-map or similar? We could consider adding a master flag later as @keith suggests to set them all at once.

However, I think that if you are trying to build a distributed build system, then properly supporting (2) is the way to go, because a properly implemented system where dsyms are automatically fitted with that e correct remapping dictionary can be completely transparent to the end-user.

As far as our use case goes we do not need to support dSYMs or even apply inverse mappings, all paths except Xcode
for a Swift compilation are kept inside a single folder, so prefixing the working directory is sufficient. We only use dSYMs for shipped applications, not for local builds, so they are generally only used for stack trace population. I am happy to have a go at getting this working though. My current patch is just applying the target's SourcePathMap.

I would like to avoid duplicating functionality that already exists in LLDB in the Swift compiler, because it can lead to hard-to-debug issues. I think we could do the following: This patch is about remapping Clang options. Those options need to get passed to the Clang compiler instance that is owned by ClangImporter. ClangImporter is created in LLDB by SwiftASTContext. If we modified ClangImporter to take a callback for remapping compiler flags, we could set that to a function similar to SwiftASTContext::RemapClangImporterOptions(). LLDB would no longer manually call RemapClangImporterOptions(), it would get called through the callback. Then we only have a single implementation of path remapping, which is owned by LLDB, and it will tie in nicely with logging and make it much more transparent what's going on.

I would like to avoid duplicating functionality that already exists in LLDB in the Swift compiler, because it can lead to hard-to-debug issues.

Agreed.

If we modified ClangImporter to take a callback for remapping compiler flags, we could set that to a function similar to SwiftASTContext::RemapClangImporterOptions(). LLDB would no longer manually call RemapClangImporterOptions(), it would get called through the callback. Then we only have a single implementation of path remapping, which is owned by LLDB, and it will tie in nicely with logging and make it much more transparent what's going on.

It seems in both the Swift serialization path and LLDB we are getting ClangImporterOptions via CompilerInvocation::getClangImporterOptions(). Would it make sense to add a method to ClangImporterOptions to handle the flag splitting and joining, with a callback for the path remapping? Something like:
std::vector<std::string> remapExtraArgs(std::function< std::string(std::string) > remapCallback) {
	// do the splitting logic for the joined args
	// and call `remapCallback` for each path
	// and return a vector of the results
}

Then we could call this function in both the Swift serialization path and LLDB to handle
their respective remapping dictionaries or whatever custom logic is required.

I updated this to use a separate -debugging-options-prefix-map flag, and to extract the flag splitting logic into a separate function that can be used from LLDB. @adrian-prantl lmk what you think of this approach.

It seems in both the Swift serialization path and LLDB we are getting ClangImporterOptions via CompilerInvocation::getClangImporterOptions(). Would it make sense to add a method to ClangImporterOptions to handle the flag splitting and joining, with a callback for the path remapping? Something like:
std::vector<std::string> remapExtraArgs(std::function< std::string(std::string) > remapCallback) {
	// do the splitting logic for the joined args
	// and call `remapCallback` for each path
	// and return a vector of the results
}

Then we could call this function in both the Swift serialization path and LLDB to handle
their respective remapping dictionaries or whatever custom logic is required.

https://github.com/apple/swift/blob/7c653e4fec06069c47ce70438a0e1be4bce68b67/include/swift/Frontend/Frontend.h#L85
I think CompilerInvocation is supposed to store the result of having built a full compiler invocation so the callback might fit better into either a class that builds a CompilerInvocation, or into ClangImporter, who receives the extra args. I thought ClangImporter's constructor would be a natural place to put the callback because it's LLDB who is creating ClangImporter:
https://github.com/apple/llvm-project/blob/c304b0469181552dfbdf745264c7277b0d23f6a7/lldb/source/Plugins/TypeSystem/Swift/SwiftASTContext.cpp#L3331

I think CompilerInvocation is supposed to store the result of having built a full compiler invocation so the callback might fit better into either a class that builds a CompilerInvocation, or into ClangImporter, who receives the extra args. I thought ClangImporter's constructor would be a natural place to put the callback because it's LLDB who is creating ClangImporter

IIUC I think what you are suggesting is that we would add a callback param as part of the constructor to the ClangImporter and then we feed the ClangImporter the unmapped args and when they are actually used internally by the ClangImporter it would call the callback function to do path fixup, is that the idea? I can see how that would work for the LLDB case, but for Swift we want the ClangImporter to keep using the existing unmodified paths, its only during serialization that we would want to remap the paths to have prefixes.
Maybe I am not following 100% though.

To summarize an offline conversation. I was conflating two things here.

we need an option to apply the debug prefix map to search paths that are serialized in .swiftmodule files
we need a way to let LLDB handle the "inverse" transformation to map the remapped paths back to something meaningful on the machine where the debugger runs

To summarize an offline conversation. I was conflating two things here.

we need an option to apply the debug prefix map to search paths that are serialized in .swiftmodule files
we need a way to let LLDB handle the "inverse" transformation to map the remapped paths back to something meaningful on the machine where the debugger runs.
This PR deals with (1). My initial concern was that having an -fdebug option affect .swiftmodule files would be unexpected. However, there serialized paths are there primarily for the debugger, so I think I've come around to being okay with just unconditionally applying the prefix map to .swiftmodule serialized search paths, too.

@artemcm @adrian-prantl just checking where we stand with this one, are further changes required or is this good for testing and merging?

@swift-ci please test

@swift-ci please test

Hi @adrian-prantl,

we need a way to let LLDB handle the "inverse" transformation to map the remapped paths back to something meaningful on the machine where the debugger runs.

Is this already supported by LLDB? I am testing debugger with -prefix-serialized-debug-info and it seems like remapping via target.source-map in .lldbinit does not affect the prefixed paths stored in .swiftmodule files.

The inverse mapping in LLDB will be handled in a follow up PR.

was there a follow-up on this?

Apologies, that one slipped off the radar, our use case requires no remapping as  we prefix all the paths to be relative to the repo root.
I can take a pass at adding remapping via the target.source-map later this week.


Where is training.ipynb

Hi,I only find llama2.ipynb in this repo and there is no steps to fine-fune LLaMa2.

That's because this is a scam for the views.

That's because this is a scam for the views.

Why do you say this, is it because the training code is not open source?

llama2.ipynb already contains the fine-tuning steps.  The readme file may mention the wrong filename.

hhhh,my mistake.I did't nitice that fine-tune demo has included in llama2.ipynb.I think I should start a PR to fix it.


Sass support

Hi)
Can you provide sass folder for compiling sass styles?
I cant setup my styles now, because using no stylus =(

Ok, have to overwrite css... :(


app: Move http server and flags parsing to their own functions

In an effort to reduce the size and cognitive load of the main Run
function for the app, this moves the flag parsing and the http server to
their own functions.
Signed-off-by: Juan Antonio Osorio<EMAIL_ADDRESS>

lgtm


Collecting infrastructure access log records

Hi,
We would like to be able to collect the access log records of the infrastructure components into our ELK stack. Currently this is not possible. As can be seen in https://github.com/cloudfoundry/gorouter/blob/68aff9a593eb565cef23906cb8c678189de6b9d1/access_log/create_running_access_logger.go and https://github.com/cloudfoundry/gorouter/blob/68aff9a593eb565cef23906cb8c678189de6b9d1/access_log/file_and_loggregator_access_logger.go:

the access log records are written to a file, if a file is specified in config/gorouter.yml ("access_log").
the access log records are also sent via dropsonde, but only if the app_id is non-empty

Therefore, infrastructure access log records (with empty app_id) are not sent anywhere besides the file.
One idea how to achieve this would be to add a new (optional) entry in config/gorouter.yml for these log records, e.g. infra_access_log: <%= p("router.infra_access_log") %>. If this entry is present, log records with empty app_id are sent in addition to a different file (if specified) or to stdout (if a file is not specified). From stdout, they are sent to syslog via the log capture mechanism in common/utils.sh, and can be collected from there.
Does this make sense? Would you accept a pull request with such a change?

I submitted a new pull request for this issue, PR #108. Instead of the proposal above, we thought it would be better to introduce general support for sending access log records with empty app_id to the syslog. For details, see the description in the pull request itself.

Closing in favor of #108


User-friendly WPS using selected watershed (4)

Description
Create a WPS with minimal user inputs:

Name of observation product (Livneh, NRCan, DEH data)
Click on basin outlet to identify watershed (largest possible)
If params are given, fine, if not, automatic calibration
Assume Canopex or USGS for streamflow obs
Fetch watershed properties from other WPS_watershed_meta
Set initial conditions (explicitly or defaults)
Set start and end date explicitly

@huard not sure this should be a WPS, I Think a notebook would be more appropriate, and we basically have that now? Should we close this?


Feedback

Hey all -- wasn't sure where the best place to put this was, so figured I'd just open up an issue!
I spent 30 minutes playing around with Augur today and wanted to share some high level feedback from a first time user. First thing I want to say is: wow! This has come a long way. The UI is beautiful, the sections make sense, the interface feels snappy and exciting. Amazing work!
Some smaller nits:

They distinction between Buy/Sell is confusing. On this trade page, I am very confused about how to bet "No", I do not think they will win the championship. I executed a "Sell" (though I don't think I owned anything?) and it seems to have executed. Does this mean I bet against it? I also issue a "Buy" and the order is still pending? I'm pretty confused by what's going on here. It would be amazing if in the UI there was some Augur 101 stuff that walked me through the basics of how I invest on either side of a prediction.
I am confused by this market. How do I actually pick a degree that I think it will be? I can place a "Buy" or a "Sell", but I can't figure out what this actually means. This is similar feedback to above, but since it's not a binary prediction, I think I require even more UI / UX help.
When I place an order, there's not status or indicator that my transaction is pending. It would be amazing if the little prompt that shows up bottom right also included a link to something like Etherscan where I could track status. Also, it would be great if pending transactions could show up in the My Positions section with a pending status.
On the Porfolio page, I'm not sure what this chart is. It was there before I had an positions, is it the entire market? Fake data?

Anyways, just wanted to dump out thoughts in case they were useful. Really excited to see this continuing to mature 👏 🎉 💛
cc @joeykrug

Thanks! This is [one of] the right place[s]!

Yep it means you short sold / bet against it. It is kinda confusing, there'll be a tutorial walkthough explaining it all in the UI eventually. Essentially it's a trading platform first, then there'll be a simpler UI skin that makes it easier / simpler to use for betting, which should also help with this issue. Did your buy order ever finish pending? Or does it instead say "open order" [this is like an open unfilled order on gdax if that's what it says]
Ah yeah, so you don't actually pick an exact degree it'll be, what you do is buy / sell or go long / short the market at a given price. So for instance, say the current prediction is 0.27 degrees and you think it'll get up to 20 degrees, just how if in a binary market you would buy up to say 60% odds or a price of 0.60 and you'd enter in 0.60 for your price in the buy box, here you'd enter in 20 and the amount you want to buy as well.
I agree, good call x2
Yeah, that's a bug I've reported as well, it's fake data haha

🙏


Feature request: control over the color if I want to change it

Problem:
users (developer using window colors) may not like to change the root_directory_name but is forced to see a theme that they hate.
Proposing an idea:
Since it seems that you use the hash to come up with window colors, means:
createColorHex(hash(root_directory_name))

If you add a global setting to your project to map root_directory_name to some user chosen value, you can give some sort of control to users, who really doesn't like the color of the window but don't want to rename their project root directory name.
// Lets say `global_settings_map` is the mapping between `root_directory_name` to `user_choice_value`

user_choice_value = global_settings_map.get(root_directory_name)
createColorHex(hash(root_directory_name + user_choice_value))

Let me know if it's not clear what I mean, but I believe this can be a great useful feature.

It would be great if the user could set the "user_choice_value" not only globally but per project. That way multiple projects with similar names would no longer end up with the same color but could be differentiated properly.


Create Login Page

Create a page for login with some kind of authentication. Passport.js seems to be a decent solution.

I plan to use two factor authentication, and there is a raw idea:

user signing to the webpage require username/password.
then they need to passing the facial recognition.


Stub form api

What problem does the pull request solve?
Checklist

[x] I've used the pull request template
[x] I've linked this PR to the relevant issue (if mission work)
[x] I've written unit tests for these changes (if code change)
[x] I've updated the documentation in (If any documentation requires updating)

[ ] README.md
[ ] Elsewhere (please link)

@danielburnley Just checking I've understood the layout we have Services, which are controllers, and Repositories, which are Models, and the Server routes act as Views?

@0atman Sorta yea - though this isn't really MVC as such, more split by responsibilities

server.rb for now contains the actual routes, which is where the logic for kinda processing the HTML requests will go (see: turning request bodies into ruby hashes)
services will handle the actual business logic, these shouldn't know anything about HTML stuff and will operate on just ruby hashes - Unit tests for this can therefore not need to do anything db related for setup and can stub repositories via dependency inversion stuff
repositories will be where anything database related can go, similarly to the server.rb anything related to databases should stay here and services shouldn't see any

At least, eventually that'll be the case. In the short term we arguably don't need the service layer if all we're doing is parsing a request and throwing it straght into the DB, kinda becomes a bit like a pointless layer in that case.
For stubbing the API however, we can probs ignore all of that and just return the json in the server.rb straight away without the need for any other layers

Swagger inspector looks good (run the server locally and try it here https://inspector.swagger.io/builder?url=http%3A%2F%2Flocalhost%3A9292%2Fapi%2Fv1%2Fswagger_doc)

So far

Tweaked schema based on our chat earlier

Format now
{
    "id": 12,
    "name": "form name",
    "submission_email"<EMAIL_ADDRESS>}

Listing forms OK:


01.04.01

As a claimant, I want to edit an expense claim while changes are allowed.

Basic Flow:

Claimant long clicks on an existing claim 2. Claimant selects "edit" on the UI Dialog options 3. Claimant edits the claim 4. Claimant presses "edit claim" button.

Exceptions:

Claim name is removed (empty) 2. Claimant enters invalid date (end before start)

Finished this test

Code has been added.
Test has been added


Intermediate training checkpoint filesizes too large?

Thanks for your amazing work! ML-beginner here - but I have doubts that I've not configured the Accelerator correctly for my training.
I'm training on musdb18hq (bass, vocals, other, drums) and I get checkpoint save-sizes almost 10-times the filesize vs. the sample checkpoint file you have provided. Is there anything to check in the Accelerator init/config to mitigate this issue?

For inference you just need "state_dict" object form the model. So you can extract this object and save to a file.

Ok I see there's a lot of intermediate data in that file container - I may close this ticket.


Add apiID to Configuration

The API interface ID is needed for the "External Koppelprofiel" base URI.
This URI is https://hostname/public/<api_id>/<object_type>
For our API v1 the header Api-Interface-Id is needed to talk to our API. On
environments where there is one API v1 this header is not needed. When
there are multiple v1 API's configured this header becomes mandatory.

And thanks again ;-) I actually left the api id out of the configuration object as I thought it was only used for the Object api. Reading your comment I understand it's used in both API's though, so that's cool ;-)
I'll update this PR soonish so it also uses the api ID in the Object api base uri and will just always send the header in case of the V1 api. Would that be the correct behaviour in your opinion?

On 16 March 2016 10:30:23 CET, Rens Admiraal<EMAIL_ADDRESS>wrote:

And thanks again ;-)

You are welcome.

I'll update this PR soonish so it also uses the api ID in the Object
api base uri and will just always send the header in case of the V1
api. Would that be the correct behaviour in your opinion?

That would be correct, if you would not include the header any application using this code would break as soon as multiple API's are configured on our side.
Cheers,
Wesley
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Just added the handling (with some minor changes to your commit) in ef23c1fab14d5a747034cbe19ef3934db5688d7f
Now the base url for the object api will have to be set without the api id suffix, and the Object api client will always append the api id to the base url.
The V1 client now always adds the 'Api-Interface-Id' header to the request.


Enable RTL rendering.

Coverage decreased (-0.08%) to 99.923% when pulling 8cc96f11e9eaa6118e891947b4c9f7e7c6a9c234 on rtl_display into adccbcc551597e17595fb5c833cc581e28b39cea on master.

Coverage remained the same at 100.0% when pulling b345adbfde9cdf43eb3a83d3522febb1d6fa25f8 on rtl_display into 3d7befaeebd02856192a3d4f3c4a37f53d30b985 on master.


Add Chrome timeline support in Tensorflow

Enables generating profiling data when using the Tensorflow backend, as requested by #6606
Passes all of the tests using the Tensorflow backend on my machine (I haven't changed anything in the Theano backend, so haven't run those tests).
It's a bit hacky how kwargs to model.compile are passed into tf.Session.run so understand if you don't want to merge this. If you're fine with this, I can update this with an example of how to generate trace files if you'd like?

Thanks for the comments; I've updated the pull request.

LGTM

It would be great to have some documentation on how to use this, for example, in order to use the timeline in Tensorflow.


sink(ticdc): support TTL table for cdc sink

What problem does this PR solve?

Issue Number: close #7997
What is changed and how it works?
The DDL statements with TTL options will be changed when syncing to donwstream

CREATE TABLE ... TTL=t + INTERVAL 1 DAY => CREATE TABLE ... TTL=t + INTERVAL 1 DAY TTL_ENABLE='OFF'
ALTER TABLE t TTL=t +  INTERVAL 1 DAY => ALTER TABLE t TTL=t +  INTERVAL 1 DAY TTL_ENABLE='OFF'
ALTER TABLE t TTL_ENABLE='ON' => ALTER TABLE t

TTL is a new experimental feature since v6.5.0, see: https://docs.pingcap.com/tidb/stable/time-to-live
We can add TTL option to a table to identify the rows in the table will be deleted when they are expired.
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
When syncing DDL with TTL options to downstream, the `TTL_ENABLE` will force be set to `OFF`

/run-verify

/run-verify

/merge

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-integration-test

/merge

/merge

/test kafka-integration-test

/test kafka-integration-test

/run-all-tests

/test engine-integration-test

/retest

/run-engine-integration-test


PythonCall not playing nicely with pyinstaller

First of all I'd like to express my appreciation for all the great work being done here. I think this package is a great facilitator for moving Julia out of it's initial niche towards integration into real, practical applications.
In that line, I've been trying to call Julia from a Python application that is then made into a (Windows) executable using pyinstaller. This did not work "out of the box". After a lot of digging, I discovered the bug was in the init_consts function, in particular in the evaluation of
:(pycopy!(pybuiltins.help, pybuiltinsmodule.help)),

Commenting the :help in src/constants/consts.jl:66 gave a working application, much to my joy and that of my colleagues, but I don't know exactly why this helped, and if there's any downside to doing this. Even if my immediate problem has been resolved/avoided, I thought I should share what I found for the benefit of the community.

Thanks for the report. It seems very odd indeed that that line would be the problematic one, but ok!
The downside of commenting out that line is that trying to use pybuiltins.help will likely crash your program horribly. Provided you don't use it you're good!
Do you have a MWE for this issue please? I have never used pyinstaller.

Sorry for not responding yet. It was a bit of a rush to get something delivered at the time, now I have some more time, I will see what I can share to illustrate the issue.

Looking at the help docs it looks like builtins.help is only available if site is imported, which pyinstaller presumably skips because it needs to control its own import path.
I can easily make that problematic line work by setting help=None if it's not available.

Just going to post a link to the commit for reference.
https://github.com/cjdoris/PythonCall.jl/commit/d223561209ccdb14b9c34119aec24ac649a29792

@KeithWM would you mind sharing how you managed to include juliacall in a PyInstaller app?
I am trying to do this on Linux, and I can't manage to get it to work.
Having an example (albeit on Windows) could still help! :slightly_smiling_face:

I think the only thing I did was to comment the line src/constants/consts.jl:66 as mentioned in the original post. But I have the impression it has been solved now anyway. Sorry if that isn't enough help.

Thanks @KeithWM for answering :slightly_smiling_face:
I actually meant how you handled the PyInstaller part.
In my minial build (on Linux) I have from juliacall import Main as jl, and when running the code it works, but trying to run the bundled app I get an error
ERROR: ArgumentError: Package PythonCall not found in current path.
- Run `import Pkg; Pkg.add("PythonCall")` to install the PythonCall package.

Do you do anything special in your PyInstaller command / .spec file? Including the julia binaries maybe?


Update README.rst

Added another option for installing on MacOS.

Cool, thanks for the heads up. I imagine that after running that pip command, you still need to run the following ones?
make qt5py3
python labelImg.py


How to run the Elastic Agent with access to ECS Task Metadata endpoint

This time I'll link to solution from the problem statement.
I want to keep a thread issue as an index.
https://github.com/zmoog/til/blob/main/aws/how-to-run-the-elastic-agent-with-access-to-ecs-task-metadata-endpoint.md

Done!


Fix training of custom models

The training API accepts "null" to mean all devices, or a
non-empty array to mean a specific set of devices.
When training a custom model, we don't refer to a specific device.
Fixes #474

No, forDevices is the list of devices that requested training. It affects showing the status bar on the device details page. You did not request training from a device page, so forDevices should be null.

Pull Request Test Coverage Report for Build 1556

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 65.24%

Files with Coverage Reduction
New Missed Lines
%

routes/my_conversation.js
1
62.83%

Totals

Change from base Build 1548:
-0.02%

Covered Lines:
5903

Relevant Lines:
8505

💛  - Coveralls


Fix the what the IgnorePixelScaling property works

Description of Change
Previously the IgnorePixelScaling allowed the drawing code to work in density-independent UI units, however it did so in a poor manner. Instead of scaling the canvas in such a way that it preserved the high density, it stretched and reduced the quality of the image.
This PR makes sure to always draw in high resolution, and then pre-scale the canvas before invoking the paint events.
Bugs Fixed

Fixes #1177
Avoids the need for https://github.com/dotnet/Microsoft.Maui.Graphics/pull/155

API Changes
None.
Behavioral Changes
A demo of the change.

Before
After

PR Checklist

[ ] Has tests (if omitted, state reason in description)
[ ] Rebased on top of main at time of PR
[ ] Changes adhere to coding standard
[ ] Updated documentation

Hi, this PR meet the our requirements except one thing
We hope to able to update ScalingFactor
https://github.com/mono/SkiaSharp/blob/2ad29861d5a40d3bf78c28ab0a9cb02a8f0fe437/source/SkiaSharp.Views/SkiaSharp.Views.Tizen/ScalingInfo.cs#L30
Because, in several reasons, we need to support a virtual scaling factor.
Could you make a setter on ScalingInfo.ScalingFactor?

Because, in several reasons, we need to support a virtual scaling factor.

@myroot I can do that. Do we need to have different scaling factors on different canvases? Or can it all be in one place?
For now I will add a setter to the ScalingInfo type. But we can easily move it to the canvas before we merge this.

@mattleibow I just stumbled over this and how the IgnorePixelScaling works.
From what I understand the new behavior is different from the document behavior, which was the old one.
The docs still say When true, the canvas is resized to device independent pixels, and then stretched to fill the view.
This isn't the case any more with v2.88.0, is it?


Update cardano-api to <IP_ADDRESS>

Update cardano-api to <IP_ADDRESS>, which matches the node's version right now. For this update the dependency of quickcheck-contractmodel to the tip of its Conway branch.
Fixes https://github.com/IntersectMBO/cardano-node-emulator/issues/22
Fixes https://github.com/IntersectMBO/cardano-node-emulator/issues/23

@mmontin> do you think you would be able to fix the compilation error?
https://github.com/IntersectMBO/cardano-node-emulator/actions/runs/9544911287/job/26304592318?pr=28

Let me check.