cannot use CSS variables

What version of @tailwindcss/jit are you using?
0.1.3
What version of Node.js are you using?
12.20.1
What browser are you using?
Chrome
What operating system are you using?
macOS
Reproduction repository
https://www.youtube.com/watch?v=4e7iksx-Zig
I'd expect that:
<div className="p-[var(--app-padding)]" />

would generate something like
.p-[var(--app-padding)] {
  padding: var(--app-padding);
}

but seems like it just does nothing

I don't expect to see this be supported.

@aweary I ran into a similar issue, but with the clamp() function.
In your case however, is there a reason you aren't using your variable directly in your tailwind config instead? The bracket syntax is supposed to be for one-off things, but your variable name suggests otherwise.
I'm not the cops though 😉

In your case however, is there a reason you aren't using your variable directly in your tailwind config instead? The bracket syntax is supposed to be for one-off things, but your variable name suggests otherwise.

@Daronspence a CSS variable can still be useful for one-off use cases, a better example might be something like bg-[var(--animated-background)] where the animated-background variable is controlled by JavaScript.
The brackets syntax says it's for "arbitrary values" so  arbitrary would imply any value at all. It should really just make sure it parses according to the CSS grammar and pipe it through.

@aweary Thanks for raising this! Right now the arbitrary value support is pretty curated, so each utility may or may not support it and may only support certain formats. I started really conservative with it because it's easy to loosen the restrictions.
For padding I see no reason to not just allow any value at all, so we can definitely update this. In other cases we have to be more careful about supporting any value or we might "hit" the wrong utility plugin, like bg-[var(--some-var)] — is that a background image, a background color, a background position, etc. Tough one because our API is sort of deliberately ambiguous in order to be terse, but it means we have to be careful now when adding features like this.
Again for padding though this is totally doable, there are no naming collisions or anything there so I'll update this one!

Should be good now in v0.1.4 👍🏻


Missing TemplatePart causes window freeze instead of exception

Describe the bug
When creating a ControlTemplate and forgetting some required TemplateParts, the window will freeze if the broken control is loaded sometime after startup. Behind a TabItem that needs to be clicked after startup in this case. Seemed to freeze the Previewer in Rider, too, but I didn't investigate in-depth.
When the broken control is loaded while starting, a KeyNotFoundException immediately closes the program.
To Reproduce
Clone this repo
Run. Click the "Crash" tab. Window should be unresponsive until you try to resize it. Then it will crash.
Expected behavior
I expect a crash/exception immediately after clicking the tab instead of a window freeze.
Environment

OS: Windows 10
Avalonia-Version: 11.0.4
IDE: Rider 2023.2.1, VS 17.7.0

Most likely is going to be fixed by this PR https://github.com/AvaloniaUI/Avalonia/pull/13189

Can confirm fixed by that PR. Can close this issue when it gets merged.

added to the fixes list


Limit of short, long, possible answer to #395

#395
One easy idea this morning was to add an optional parameter to this.advice('short'/'long');
Can be in percent like : this.advice('short', 10) (10 for 10% of amount)

usefull and working  with #448 #449 #450

I think this has been implemented or has open PRs for it

No but it will be very soon. Active discussion now in #1834.


fix: [Main] Set EXTRA_PROXY_ROUTE_LIST for all add on services except Device Virtual

fixes #405

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-compose/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?) *N/A

Testing Instructions
From compose builder run make run ds-onvif-camera ds-usb-camera ds-bacnet-ip ds-modbus ds-mqtt ds-rest ds-snmp ds-virtual ds-llrp ds-coap ds-gpio asc-http asc-mqtt asc-sample asc-metrics as-llrp asc-ex-mqtt mqtt-broker
For each of the above services (expect mqtt-broker) verify https://localhost:8443/<service-key>/api/v3/ping results in 200 response.

@cherrycl , are the 2 failing tests on this PR known failures? THX!

do we apply this ADD Extra route logic into taf-secty ?

TAF team already added it where they needed it.

recheck


Job names of build-and-test.yaml and build-and-test-pr.yaml conflict

After #24 is merged, the job names conflict and the Required condition doesn't work correctly.
https://github.com/autowarefoundation/autoware_common/issues/21#issuecomment-1032127058

I feel changing the job name in build-and-test-pr.yaml to "build-and-test-pr", "build-and-test-modified-packages", "build-and-test-differential" is good.
But in that case, we might have to change other job names such as clang-tidy or spell-check as well for consistency.
@KeisukeShima @h-ohta Do you have any ideas?

Or, changing the condition from "push" to "pull_request is merged" can work? :thinking:

@kenji-miyake I agree with you.
We may also need to change the name of the arm job from "build-and-test-arm".

Which one do you think is the best?

I think, since sometimes we will want to run the full tests on PRs, I'd like to avoid -pr.
Also, modified-packages is a bit long, so I prefer differential.

For example in the future, we can add prevent-no-label-execution of the full-build label to build-and-test.yaml workflow and make it run when the label is added on PRs.

Since we are using get-modified-packages in our workflow, we also need to consider its name.
To avoid confusion, I want to change the name of the action if we make it differential.

Do you mean changing get-modified-packages to get-differential-packages? :thinking:
If so, I feel it's not a big problem.

Do you mean changing get-modified-packages to get-differential-packages? thinking If so, I feel it's not a big problem.

Yes. It's not a big problem.

I'll create a PR.
@KeisukeShima By the way, do you think we should add -amd64 as well? For example, build-and-test.yaml will be build-and-test-amd64.yaml.

Or instead, should we change the suffix -arm to -self-hosted?

Considering the reason why I split the ARM workflows, it's because of self-hosted, not because of ARM, so I think -self-hosted might be better.
If ARM machines are supported by GitHub-hosted runners in the future, we can configure matrix jobs in build-and-test.yaml.

Also, if we use -self-hosted, the users of sync-files workflow can understand whether it's necessary for them or not.
With -arm, they sometimes try to sync them mistakenly.
https://github.com/autowarefoundation/autoware.universe/blob/2268517328f217dee7f3b6f3dc634af728552b30/.github/sync-files.yaml#L24

Agreed. -self-hosted suffix is appropriate.

I sent two PRs!


Implementation of class for Gear Meshing model that represents dynamic system (issue #142 related)

System is to implement or improve in module gear.py. It should be inherited from similar class being implemented within scope of the module if possible.

Class was checked by the following call:
from dynpy.models.mechanics.gears import DDOFGearMechanism
DDOFGearMechanism(None);


How did you select learner

I've followed both tutorials, also https://www.microsoft.com/net/learn/apps/machine-learning-and-ai/ml-dotnet/get-started/windows. I just wanted to know, how did you select learner, as Both Iris and sentiment-analysis are types of binary  classifier, so if possible please explain why you have selected FastTreeBinaryClassifier for sentiment-analysis and StochasticDualCoordinateAscentClassifier for Iris-data tutorial.
Thanks

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

ID: c8e22825-c4ee-5a36-f911-8ad456970ecc
Version Independent ID: ad0bf640-7dfc-1184-077c-358bb14277a7
Content: Use ML.NET in a sentiment analysis classification scenario
Content Source: docs/machine-learning/tutorials/sentiment-analysis.md
Service: unspecified
Product: dotnet-ml
GitHub Login: @JRAlexander
Microsoft Alias: johalex

Adding @aditidugar and @asthana86 to help with this question.

Hey @Amit1150, thanks for your question! Actually, the Iris tutorial is a multi-class classification task, not a binary classification task since there are 3 different types of flowers that can be predicted. Hence, you must use a different learner.
Hope this helps!

With that, I think we can close this issue. Thanks @aditidugar!


[SE-0298: Async/Await: Sequences] Enable by default.

One still needs to import the _Concurrency library to use it.

@swift-ci please smoke test

@swift-ci please test source compatibility

@swift-ci please smoke test

@swift-ci please test source compatibility


Cassandra Channel || No Exception is thrown when ssl.provider is "OpenSSL" (Certificates are created using key-tool)

Version Information

Software
Version(s)

BusinessEvents
6.3.0

OS Type?

OS Version?

What is the expected behavior?
Exception should be thrown since ssl.provider sets to OpenSSL but certificates are created using JDK-keytool.
###Steps to reproduce
Set the configuration in Cassandra.yaml for one-way ssl.
Start Cassandra and Pulsar
Create a required keyspace and table
Set the SSL configuration for CDC Cassandra Nar File as below:
ssl.provider="OpenSSL"
ssl.truststore.path=
ssl.truststore.password=
ssl.hostnameValidation="false"
Note: I have created certificates using keytool. For 2way SSL, if ssl.provider=OpenSSL it throws an exception if the certificates are created using keytool.

This exception is beaviour from pulsar/cdc-apache-cassandra lib side.

Logged issue on cassandra-datastax side: https://github.com/datastax/cdc-apache-cassandra/issues/154


Number of neighboring vehicles in "parking-v0" environment?

Hey @eleurent first of all thanks a lot for all this gym environments, which made my life a bit easy, since I was working with CARLA for validating my SAC agent for autonomous parking. Two things:

One is there a way I can spawn more vehicles at the other parking spots (other than the goal position)?
Secondly I have my own SAC agent with PER implemented, but I find it difficult to make the vehicle learn to park, I can see from the log that the vehicle(agent), falls into a local optima.

Hi,

For 1., you can configure the environment as follows:

env.configure({"vehicles_count": 5})

Be careful and ensure that the positions of these vehicles are present in the observation (they are not if you use the default parking observation), e.g. you could use an image observation, or lidar + goal, etc.

For 2., its generally non-trivial to debug an RL algorithm as there is a number of things that could go wrong, so I'm afraid I don't have any silver bullet solution for you. If you believe your algorithm is converging too early to a suboptimal local minimum, you may want to increase the amount of exploration (e.g. random noise injection, use temporally correlated noise, etc)

Yeah eleurent,
https://user-images.githubusercontent.com/94734022/201953648-aa529cce-9e5b-48ac-9e56-f4837bea49b9.mp4
Thanks for your response! I did a similar implementation in the virtual space of CARLA. SAC+HER is working fine, just some wobbling is still there in the maneuvering of the vehicle when it starts getting more closer to the parking spot. Can you throw some light on the reward setting you designed when you have nearby parked cars in the parking lot?
Also in the parking-v0 environment, as part of the environment, you have assigned the acceleration as one of the action values predicted by the agent. unfortunately in CARLA it's not possible to predict the acceleration instead I have to predict the throttle, brake, and steering commands.
So these are the 2 things right now I am struggling with, when the vehicle is far away from the parking spot it brakes more often and thus it rarely moves in the initial episodes.
And secondly, the wobbling issue, when the vehicle starts to learn to reach the parking spot. Could you please share your opinions on these?
And also in CARLA, I don't have the flexibility to reverse the vehicle just by putting a negative acceleration(deceleration) value, since in CARLA, to switch to reverse we have to literally toggle the gear.

And also I believe the input argument going into "self.road.step(1 / self.config["simulation_frequency"])" is the rate at which the action is being predicted by the agent, right? since I believe I need to get the exact same time_step value between two actions in CARLA, since the rate at which the action is being applied by the agent also matters a lot.

So what time step between 2 actions should I set-up?
And secondly the steering action being predicted by the agent, does it have any sort of relation to the previous steering action predicted by the agent?
Like: current_action = current_action(predicted) + last_action ?

just some wobbling is still there in the maneuvering of the vehicle when it starts getting more closer to the parking spot. Can you throw some light on the reward setting you designed when you have nearby parked cars in the parking lot?

My reward only has a distance-to-goal term and a collision term, nothing for comfort/jerk. The amount of wobbling that you get will depend on lot on your choice of action space and your dynamics (e.g. you could have a low pass filter, e.g. preventing the steering wheel angle to jump instantly from -180deg to +180deg). If you don't want to change the dynamics, you will have to go through the reward function which is probably a bit more difficult because the agent will need to figure it out. You can e.g. add a reward term penalising angular velocity or angular acceleration, but for your agent to be able to measure it you will also need to provide these as measurements (or several frams if you are using images).

Also in the parking-v0 environment, as part of the environment, you have assigned the acceleration as one of the action values predicted by the agent. unfortunately in CARLA it's not possible to predict the acceleration instead I have to predict the throttle, brake, and steering commands.

In theory the agent can also find a good policy in this alternative action space, but as you noticed it probably makes exploration difficule as random actions are not as useful. So either you find some way of how your agent explores (e.g. by using temporally-correlated noise, prevent using the brake action if it was used recently, etc.), either you change the action space so exploration is easier: e.g. you could write a low-level acceleration controller which translates desired acceleration (output by the agent) into throttle and brake commands, depending on the vehicle state.

And also I believe the input argument going into "self.road.step(1 / self.config["simulation_frequency"])" is the rate at which the action is being predicted by the agent, right?

Correct!

So what time step between 2 actions should I set-up?

A smaller timestep means:

better accuracy when simulating the dynamics
slower simulation time (more steps for the same simulated duration)
harder exploration for the agent, as a single action has a very limited impact

And secondly the steering action being predicted by the agent, does it have any sort of relation to the previous steering action predicted by the agent? Like: current_action = current_action(predicted) + last_action ?

As of now, this project uses the Kinematics Bicycle Model. The steering action is used to set the front wheel angle delta_f, which is unrelated to the previous one (unlike what you suggested). However, there is an integration step in the dynamics: the front wheel angle delta_f is converted to a slip angle beta, which is then integrated to give the variations of heading. This integration step has a low-pass filtering effect, and contributes to smoothing the jitter in steering actions a bit, kind of like what you wrote.

First of all, I really appreciate you for taking some time to go through these questionnaires!!!
I tried including the angular velocity and even the angular acceleration into the reward functionality, but it is getting just worse in terms of the performance of the vehicle in parking at such a tight space.
So, let's see I am still playing with the reward functionality.

Just thinking about your last point about the timesteps between 2 consecutive actions by the agent.
Having smaller timesteps will have a better dynamics understanding from a simulation perspective, does this mean that smaller time step will study the dynamics of the vehicle much more in detail, like-in we are able to closely observe the dynamics of the vehicle more often? but thinking from a simulation perspective, if we have such smaller time steps it also means that there is a high possibility that your agent will hardly learn anything, since the actions are being outputted at such high frequency?
Also could you please elaborate on the harder exploration strategy for the agent(your third point on the list?)

Thanks for all the comment and help really appreciate it.
I hereby close the issue here.


not able to save hdf5

I am getting this error while running pre-process, can you please check?
2018-08-02 18:50:57,367 - [preprocess_data.py:375-run()] - INFO - padding id vectors...
2018-08-02 18:51:21,268 - [preprocess_data.py:392-run()] - INFO - export to hdf5 file...
Traceback (most recent call last):
File "./run.py", line 35, in
preprocess(args.config_path)
File "./run.py", line 24, in preprocess
pdata.run()
File "/data/dchaudhu/Match-LSTM/dataset/preprocess_data.py", line 393, in run
self._export_squad_hdf5()
File "/data/dchaudhu/Match-LSTM/dataset/preprocess_data.py", line 344, in _export_squad_hdf5
**self._compress_option)
File "/data/dchaudhu/anaconda3/envs/py36/lib/python3.6/site-packages/h5py/_hl/group.py", line 116, in create_dataset
dsid = dataset.make_new_dset(self, shape, dtype, data, **kwds)
File "/data/dchaudhu/anaconda3/envs/py36/lib/python3.6/site-packages/h5py/_hl/dataset.py", line 100, in make_new_dset
tid = h5t.py_create(dtype, logical=1)
File "h5py/h5t.pyx", line 1611, in h5py.h5t.py_create
File "h5py/h5t.pyx", line 1633, in h5py.h5t.py_create
File "h5py/h5t.pyx", line 1688, in h5py.h5t.py_create
TypeError: Object dtype dtype('O') has no native HDF5 equivalent
Regards,
Debanjan

Sorry, I have not encountered such a problem.
You can check the value of sub_value.dtype in /data/dchaudhu/Match-LSTM/dataset/preprocess_data.py, line 342.
Did you set some options False in global_config.yaml? like use_char , use_pos .


Added note to SipSignalingPort

Docs Build status updates of commit 878d4f1:
:clock10: Full build: the average full build time is 12 min(s) 2 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 878d4f1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsOnlinePSTNGateway.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Custom field mappings do not work with react production mode

When deploying my application in production mode react mangles the component names.
This causes the custom field mapping to not work because the component doesn't have the same name.
usage example:
const BootstrapTextField = createFieldClass({
  FormControl: controls.text
});

const MyComponent = () => (

      <BootstrapTextField model="forms.test">
          <FormControl type="text" />
      </BootstrapTextField>

);

What comes out in production mode when looking at the react dev tools is something similar to:

    <o model="forms.test">
      <t type="text" />
    </o>

How does the library currently checks the child components? is it using displayName or something else?
I don't have time right now to prepare a full reproduction test case but will try to do it later today.

Yep, it's using displayName, which is minified in production mode, unfortunately.
V1 will solve this issue, but until then, an easy workaround is this:
import CustomTextInput from '../path/to/custom-text-input';

CustomTextInput.displayName = 'CustomTextInput';

// ... do everything else like normal

For more info, see:

https://davidkpiano.gitbooks.io/react-redux-form/content/react_native_&_custom_components.html#custom-components
https://github.com/davidkpiano/react-redux-form/issues/224
https://github.com/davidkpiano/react-redux-form/issues/176
https://github.com/davidkpiano/react-redux-form/issues/161
https://github.com/davidkpiano/react-redux-form/issues/65

I've actually just introduced a more idiomatic way to do this:
const BootstrapTextField = createFieldClass({
  FormControl: controls.text
}, {
  componentMap: {
    FormControl: FormControl
  }
});

This allows RRF to recognize the component by its constructor, instead of by its .displayName. Will be available in 0.13.6+

The syntax seems a bit verbose, maybe instead of providing a separate map you could supply the actual component as the key?

Oh, smart idea. I'll update that now.


Fragment Shader Exception

On OS X I get an exception immediately after dragging an image into the window:
GPUImage`runSynchronouslyOnVideoProcessingQueue
Failed to compile fragment shader
Program link log: (null)
Fragment shader compile log: ERROR: 0:25: 'vec2' : syntax error: syntax error
Vertex shader compile log: (null)
*** Assertion failure in -[GPUImageSingleComponentGaussianBlurFilter switchToVertexShader:fragmentShader:], /SwiftOCR/framework/SwiftOCR/GPUImage-master/framework/Source/GPUImageGaussianBlurFilter.m:401
An uncaught exception was raised
Filter shader link failed

I didn't manage to track down which vec2 it was (1503 results in 128 files)

It was caused by the GPUImageSingleComponentGaussianBlurFilter. Setting the blur radius to a number bigger than 7 (i think) caused it to crash.


Add a test case for importing a module from a test file of another module in the same project

Description:
$subject
Related PR :
https://github.com/ballerina-platform/ballerina-lang/pull/12625

Test cases were added with https://github.com/ballerina-platform/ballerina-lang/pull/12655, hence closing this issue.


Feature request: Provide localisation method for custom text

Really happy to see the built-in localisation for all of the standard text.
Wondering if you'd consider adding a method for localising any custom text throughout the app.
Many thanks!

i'm in for this too. Would be nice if we can use something like:

en
something
de
etwas
fr
quelque chose


DCOS-5935 Added storemixin to vanilla objects to avoid duplicating constants

Reviewer: @rcorral

Aside from @kennyt's comment I think this looks good! 🚢

Rebase and then 🚢


Check TorrentFile is complete download issue

I wrote this method extension to check if TorrentFile is download complete, but it return false result (invalid) when torrent just complete in current session
    public static bool IsFileDownloadCompleted(this TorrentFile file)
    {
        return file.BytesDownloaded >= file.Length;
    }

But when I restart the app and run this again, it return true result. May be BytesDownloaded not update yet?

BytesDownloaded is implemented as:

If this property is returning an incorrect value then it means the BitField is being updated incorrectly. It sounds like this only happens while the torrent is actively downloading so I'll look into this to start with. If you can come up with a concrete testcase that would help.
I'll update this issue if I find anything which explains this further.

By the sounds of it the issue is that the torrent reports 100% complete, but individual files aren't marked as 100% complete. I'm not sure how that could happen as the file and torrent are updated in the same method, and there are tests covering this to make sure they are updated correctly.
If you can come up with a way to reproduce the issue that would be very helpful!

I will try to reproduce the issue later, and for more info, the method I use to determine torrent is downloaded is
if (TorrentManager.Progress >= 100)
{
// torrent loaded
}

I can't reproduce issue, it just happen one time. I will open this again when it bother me again. Thanks


Support Python 3.7

Raspbian is still using Python 3.7. It would be good to support it.
I've already updated .travis.yml do a build for Python 3.7. However, one can't specify multiple Python versions on the Pipfile, so on the virtual environment we end up using Python 3.8 anyway.
There may be other things that need to be updated to support Python 3.7.

Probably just need to replace typing.get_args with .__args__ for it to support Python 3.7. Also need to make pyre run successfully against 3.7 from Travis CI.


Add installation notice for nix

As requested, here are the install instructions (more or less) for nix based installations.

thank you @matthiasbeyer and sorry for the delay

Don't worry about it! :tada:


Error: options/query provided without loader

Hi,
I've just installed vue-cli to try it out and after the following steps
npm install vue-cli -g
vue init webpack-simple i-vue
cd i-vue
npm install
npm run dev

I got this issue
Error: options/query provided without loader (use loader + options) in {
  "test": {},
  "use": "vue-loader",
  "options": {
    "loaders": {}
  }
}

Just don't know what to do.
Would be really happy if someone could help.
Thank you in advance.
--
npm: 5.5.1
node: 6.11.3
vue: 2.9.1

Seems like leaving out "webpack-simple" works. I'll go with that.

For the record: I messed up the webpack-simple template yesterday with a bad commit. I fixed it soon after and it's working as expected again.
Sorry for the inconvenience.


Invalid escaping of {staged_files}

:wrench: Summary
If file names contains some utf8 (I guess) characters, lefthook fails because of invalid escaping.
error replacing {staged_files}: CreateFile C:\code\repro\lefthook-wrong-escape\"files\KO \303\251.json": La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.

(part of the message is in French, probably the system error lefthook trapped).
Lefthook version
1.7.7
Running on Windows 10. Both reproed using PowerShell 7 and legacy cmd console.
Steps to reproduce
Clone this repo: https://github.com/stevebeauge/repro-lefthook-wrong-escape
git clone https://github.com/stevebeauge/repro-lefthook-wrong-escape
cd repro-lefthook-wrong-escape
pnpm i

Edit the file files/KO é.json. Set whatever you want in the file. If you are using a powershell console you can run
Get-Date | ConvertTo-Json | Set-Content -LiteralPath '.\files\KO é.json' -Encoding utf8

Then try to commit the changes:
git add .
git commit -m "Something"

Expected results
It should work whatever the file name is (assuming it's a valid filename for the system).
Actual results
It fails because utf8 character is escaped, but the escape character is itself not properly escaped:

error replacing {staged_files}: CreateFile C:\code\repro\lefthook-wrong-escape"files\KO \303\251.json": La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.

Possible Solution

Logs / Screenshots
Running pnpm lefthook run pre-commit -v in a powershell console generates this logs:
│ [lefthook] cmd: [git rev-parse --show-toplevel]
│ [lefthook] err: <nil>
│ [lefthook] out: C:/code/repro/lefthook-wrong-escape

│ [lefthook] cmd: [git rev-parse --git-path hooks]
│ [lefthook] err: <nil>
│ [lefthook] out: .git/hooks

│ [lefthook] cmd: [git rev-parse --git-path info]
│ [lefthook] err: <nil>
│ [lefthook] out: .git/info

│ [lefthook] cmd: [git rev-parse --git-dir]
│ [lefthook] err: <nil>
│ [lefthook] out: .git

│ [lefthook] cmd: [git hash-object -t tree /dev/null]
│ [lefthook] err: <nil>
│ [lefthook] out: 4b825dc642cb6eb9a060e54bf8d69288fbee4904

╭──────────────────────────────────────╮
│ 🥊 lefthook v1.7.7  hook: pre-commit │
╰──────────────────────────────────────╯
│ [lefthook] cmd: [git status --short --porcelain]
│ [lefthook] dir: C:/code/repro/lefthook-wrong-escape
│ [lefthook] err: <nil>
│ [lefthook] out: M  "files/KO \303\251.json"

│ [lefthook] cmd: [git diff --name-only --cached --diff-filter=ACMR]
│ [lefthook] dir: C:/code/repro/lefthook-wrong-escape
│ [lefthook] err: <nil>
│ [lefthook] out: "files/KO \303\251.json"

│  prettier (skip) error replacing {staged_files}: CreateFile C:\code\repro\lefthook-wrong-escape\"files\KO \303\251.json": La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.
│ [lefthook] cmd: [git stash list]
│ [lefthook] dir: C:/code/repro/lefthook-wrong-escape
│ [lefthook] err: <nil>
│ [lefthook] out:

  ────────────────────────────────────
summary: (done in 0.28 seconds)
🥊  prettier: error replacing {staged_files}: CreateFile C:\code\repro\lefthook-wrong-escape\"files\KO \303\251.json": La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.
╭

As a comparison, modifying files/ok.json is working. It's verbose output is:
│ [lefthook] cmd: [git rev-parse --show-toplevel]
│ [lefthook] err: <nil>
│ [lefthook] out: C:/code/repro/lefthook-wrong-escape

│ [lefthook] cmd: [git rev-parse --git-path hooks]
│ [lefthook] err: <nil>
│ [lefthook] out: .git/hooks

│ [lefthook] cmd: [git rev-parse --git-path info]
│ [lefthook] err: <nil>
│ [lefthook] out: .git/info

│ [lefthook] cmd: [git rev-parse --git-dir]
│ [lefthook] err: <nil>
│ [lefthook] out: .git

│ [lefthook] cmd: [git hash-object -t tree /dev/null]
│ [lefthook] err: <nil>
│ [lefthook] out: 4b825dc642cb6eb9a060e54bf8d69288fbee4904

╭──────────────────────────────────────╮
│ 🥊 lefthook v1.7.7  hook: pre-commit │
╰──────────────────────────────────────╯
│ [lefthook] cmd: [git status --short --porcelain]
│ [lefthook] dir: C:/code/repro/lefthook-wrong-escape
│ [lefthook] err: <nil>
│ [lefthook] out: M  files/ok.json

│ [lefthook] cmd: [git diff --name-only --cached --diff-filter=ACMR]
│ [lefthook] dir: C:/code/repro/lefthook-wrong-escape
│ [lefthook] err: <nil>
│ [lefthook] out: files/ok.json

│ [lefthook] files before filters:
[files/ok.json]
│ [lefthook] files after filters:
[files/ok.json]
│ [lefthook] files after escaping:
[files/ok.json]
│ [lefthook] executing: pnpm prettier files/ok.json
┃  prettier ❯

"2024-07-25T18:29:38.9212089+02:00"

│ [lefthook] cmd: [git stash list]
│ [lefthook] dir: C:/code/repro/lefthook-wrong-escape
│ [lefthook] err: <nil>
│ [lefthook] out:

  ────────────────────────────────────
summary: (done in 1.38 seconds)
✔  prettier

Hey! Thank you for submitting this issue. I couldn't reproduce the issue on my macOS, so I assume this is something OS-related. I will try to figure it out.

From my perspective it looks like git command returns the file list in different encoding.
Could you try setting the default encoding for Powershell to UTF-8 (if not set yet)?
I found some useful options here: https://stackoverflow.com/questions/57131654/using-utf-8-encoding-chcp-65001-in-command-prompt-windows-powershell-window/57134096#57134096

It is already on utf8 code page (65001).
Which git command lefthook runs?  Can I "test" the single comment to see how it behaves?

Yes, it's git diff --name-only --cached --diff-filter=ACMR. So, it returns the same corrupted result when executed explicitly, right?

Maybe this can help: https://stackoverflow.com/questions/10651975/unicode-utf-8-with-git-bash

Ok, found a workaround.
git config core.quotepath false
git status

Returns:
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        modified:   files/KO é.json

Restoring the config
git config core.quotepath true
git status

Returns:
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        modified:   "files/KO \303\251.json"

I close the issue. It's not related to lefthook, but to git actually. Thanks for the help

I don't know if it can solve the issue, but git diff has a -z flag that does not encode the file name:
git diff --name-only --cached --diff-filter=ACMR
"files/KO \303\251.json"

git diff --name-only --cached --diff-filter=ACMR -z
files/KO é.json^@

The final char is a NUL char. So what about adding the flag to lefthook, take the output minus the last NUL char and adding surrounding quotes?

If I both wrap the {staged_files} with quotes and set git config core.quotepath false, it works as expected.
However, I don't feel comfortable with this solution. Git options are not committed as part of the source code. It requires every developer to set the option, and will eventually lead to issues or conflict with other tools that may rely on git commands (I'd bet turborepo or NX are using same technics to detect affected projects).
I never works with go and I have no idea of the impact/complexity, but I'd wish lefthook take the normalization into account.
From the git doc

Path names are encoded in UTF-8 normalization form C.

Maybe there's some lib in go that can revert the normalization back to plain utf8 encoding ?
(🤫 https://chatgpt.com/share/448c4b2f-c19d-4532-a57c-c7c0d9573a44)
This would create a bullet proof and cross platform way to read the file names.

For the last issue the problem is that Windows doesn't work well with single quotes (as far as I know), and considers 'files/KO é.json' as two files: 'files/KO and é.json'. So, this is not the encoding issue here.
But I like your idea for normalization of the output. It makes sense. I'll put it on my radar :+1:

I've also bumped into an issue with wrong escaping of {staged_files}, but it was of another kind.
If file name contains square brackets ([ or ]), it will be additionally wrapped with single quotes, making file name invalid for eslint, for example.

@nicky1038 , in this case use "{staged_files}" in your configuration, so every file is wrapped in double quotes when calling with eslint

@nicky1038 , in this case use "{staged_files}" in your configuration, so every file is wrapped in double quotes when calling with eslint

@mrexox Thank you for the quick response, the suggested solution works like a charm! And sorry for not reading docs before asking questions 😶

A


[Feature Request] Allow for Prisma enums in validation rules

Is your feature request related to a problem? Please describe.
While Zenstack is already offering great validation capabilities, it would be nice if it were possible to use Prisma enums
inside a validate block, for example with an in operation. This would allow for an always-in-sync validation instead of relying on manual updates in both codebase and validation rules.
One might ask why not set the field as the enum? The answer to that being that working with primitives is easier to migrate and also better supported across third party vendors, like Hasura GraphQL.
Describe the solution you'd like
Allow for Prisma enums to be referenced in validations rules, especially with the in operator.
Describe alternatives you've considered
Additional context

Hey @nwidynski , thanks for filing this. Do you mind providing a ZModel snippet showing how you want to use it? Thanks!

@ymc9 This woukd be a short example with some options for the validate API.
enum PostType {
  DRAFT
  ACTIVE
  CANCELLED
}

model Post {
  id String @id
  status String

  @@validate(status in PostType)
  @@validate(has(PostType, status))
}

Got it. Yes, string and enum can be compatible for comparison.

We‘re especially looking for the in operator which would probably translate to:
Object.values(PostStatus).includes(value)

I actually don't get why this is necessary. Making status of type PostStatus instead of String would already validate the type. No need for in operator in this case.

@Eliav2 It's mentioned at the bottom of the PR description.


Visual touch up improvements

Sections updated:

hero section - text style and positioning only
dune data section
live use cases section
get involved section

Just one remaining issue on Vercel with the image resolution @Tanya-atatakai


Error running the simple_box example via trunk for WASM

$ git log -n 1 --pretty=format:"%h" --no-show-signature
09ab02f6
$ trunk serve
2024-08-28T13:21:50.131755Z  INFO 🚀 Starting trunk 0.20.3
2024-08-28T13:21:50.134149Z  INFO 📦 starting build
   Compiling bevy_picking_raycast v0.20.0
   Compiling bevy_egui v0.28.0
warning: unused import: `LOCAL_SOCKET`
  --> lightyear/src/client/io/config.rs:21:50
   |
21 | use crate::transport::{BoxedReceiver, Transport, LOCAL_SOCKET};
   |                                                  ^^^^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

warning: `lightyear` (lib) generated 1 warning (run `cargo fix --lib -p lightyear` to apply 1 suggestion)
   Compiling bevy_mod_picking v0.20.1
error[E0308]: mismatched types
   --> /home/qtfkwk/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_egui-0.28.0/src/web_clipboard.rs:233:13
    |
233 |         let Some(clipboard) = nav.clipboard() else {
    |             ^^^^^^^^^^^^^^^   --------------- this expression has type `Clipboard`
    |             |
    |             expected `Clipboard`, found `Option<_>`
    |
    = note: expected struct `Clipboard`
                 found enum `std::option::Option<_>`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `bevy_egui` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
2024-08-28T13:21:53.585820Z ERROR ❌ error
error from build pipeline

Caused by:
    0: HTML build pipeline failed (1 errors), showing first
    1: error from asset pipeline
    2: running cargo build
    3: error during cargo build execution
    4: cargo call to executable 'cargo' with args: '["build", "--target=wasm32-unknown-unknown", "--manifest-path", "/home/qtfkwk/github.com/cBournhonesque/lightyear/examples/simple_box/Cargo.toml"]' returned a bad status: exit status: 101
...

Seems to be known already in this upstream issue and resolved in 0.29.
Unsure if/how lightyear and/or the simple_box example should be updated?

Thanks, I think it can be fixed by specifying bevy-inspector-egui="=0.25.1" in the Cargo.toml
(the 0.25.2 version seems to be importing egui 0.28 which has the bug you mentioned above)


Some pictures won't load after running script.

Any idea why this is the case.

https://i.gyazo.com/2d191216a794f85d1ccf1cee7aabde87.png


License

It seems because no license is listed, that documentation is not available:
https://pkg.go.dev/github.com/komkom/toml

Thanks will fix this.

Thanks will fix this.

Thanks, here is the temporary link:
https://pkg.go.dev/github.com/komkom/toml@master

Thanks, here is the temporary link:
https://pkg.go.dev/github.com/komkom/toml@master


Port rules in Component .hpp file are incorrect

In the .hpp file generated by the acfproject template , there are comments that describe the rules for defining GDS ports. At least some of these rules are incorrect.
For example, the comments state:
Create one (and only one) instance of this struct.
Apart from this single struct instance, there must be no other Component variables declared with the #port comment.

... but I have successfully broken this rule in firmware version 2021.0.3 on an AXC F 2152.
Perhaps these comments were correct for an earlier firmware version, but they need to be revised.
This might be the same for GDS ports in PLM components (I haven't checked).

It is not really a rule. It is more of a suggestion which works. The problem when you use multiple structure is, that it is easy to have the same port name twice. Both in different structures. Do you mean we should change the comment, so that is does not sound like a rule?

These comments are written like rules, and that is good - users of this template need to know what the rules are for defining Component ports, in the same way that users need to know the rules for defining Program ports. After the rules are clear, then examples can be provided. But the first priority is to clearly list the complete set of rules.
So, either the comments should be changed to list the rules for defining Component ports, or else a reference to the complete set of rules should be provided in the comments. Otherwise, I don't understand how users of this template are supposed to know the rules for defining Component ports?

Will be fixed with the next version

Was fixed in the 21.6 Release.


List of things to include in next astropy-helpers/package template updates

This issue is just a reminder of things we could include in the next batch updates for astropy-helpers and package-template files. Feel free to add more in comments (or edit this):

[x] Update astropy-helpers
[x] Remove ez_setup.py
[x] Update _astropy_init.py
[ ] Update setup.py

Notify/open issues:

[x] MPLBACKEND is now set to Agg, packages expecting interactive plotting should override it in .travis.yml
[x] update travis matrix, at least jobs with NUMPY_VERSION<1.13 and ASTROPY_VERSION=stable
[x] sphinx-astropy as dependency: https://github.com/astropy/astropy-procedures/issues/108#issuecomment-447880971
[x] six not to be imported from astropy but directly

Next round of issues:

[ ] usage of _ASTROPY_SETUP_ and that whether that tries to import astropy at setup time or not https://github.com/astropy/astropy/pull/8402#discussion_r258379669

With helpers 3.2 update:

[ ] make a note that sphinx-astropy should be listed as a dependency for building the docs.

The first 2 can and will be dealt with the usual helpers update procedure.
For the rest, it would be useful to list the stuff that we need to update specifically (a link to the relevant PR in the template would do)

@bsipocz - for _astropy_init.py I was thinking of just copying over the whole file from the template to make sure it's up to date, whatever people have in their package (rather than checking for specific changes)

oh. So you think it's safe to assume no one did any customization there? Probably that's a fair assumption though (or maybe there is an easy way to compare it to each and every version of that file from the package template, and if it's from any point in the past we can assume it's safe to update).

We can check for customizations of the file by comparing to hashes of past versions of that file. This is actually true for all files of the template in fact. I'll try writing a script soon that can do these kinds of checks.

I found that I also had to update RTD requirements file to include sphinx-astropy after update to astropy-helpers 3.1. Not sure how easy it is to hunt down some random RTD requirements file and update it properly; maybe just add a note in this same PR to remind maintainer to check it, is applicable.

This can be closed now without further action.


DRY

@boostrack have you signed the contributors agreement?

@spencergibb have the following one.
SpringSource Community Contributor number is<PHONE_NUMBER>1072209.


Karpenter not deprovisioning and deleting customized gpu node

Version

Karpenter Version: v0.20.0

Kubernetes Version: v1.23
Expected Behavior
When i scaled down the deployment to 0 the node should be deprovisioned and deleted, but that's not happening.
Actual Behavior
During scaling the deployment does not bring down the node
kubectl -napp scale deploymentapp1-service --replicas=0

Steps to Reproduce the Problem
Create a provisioner using this config
I deployed this configuration:
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
    name: default
    namespace: "app"
spec:
    requirements:
    - key: karpenter.sh/capacity-type
        operator: In
        values: ["spot"]
    - key: node.kubernetes.io/instance-type
        operator: In
        values: ["r5.large"]
    - key: kubernetes.io/os
        operator: In
        values: ["linux"]
    providerRef:
        name: default
    consolidation:
        enabled: true
    labels:
        node: default
---
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
    name: default
    namespace: "app"
spec:
    instanceProfile: "IAMProveApp1"
    subnetSelector:
        Role: "private"
    securityGroupSelector:
        aws:eks:cluster-name: dev-cluster
    tags:
        karpenter.sh/discovery/node: default
        karpenter.sh/discovery: dev-cluster
---
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
    name: gpu
    namespace: "app"
spec:
    requirements:
    - key: karpenter.sh/capacity-type
        operator: In
        values: ["on-demand"]
    - key: node.kubernetes.io/instance-type
        operator: In
        values: ["g4dn.4xlarge"]
    kubeletConfiguration:
        containerRuntime: dockerd
    providerRef:
        name: gpu
    consolidation:
        enabled: true
    taints:
    - key: app
        value: app1-service
        effect: NoSchedule
    labels:
        app: app1-service
---
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
    name: gpu
    namespace: "app"
spec:
    labels:
    app: app1-service
    amiSelector:
        karpenter.sh/discovery: dev-cluster //<-- We tagged the ami to select with this key name, the ami is GPU base ami with prebuilt images in it
    blockDeviceMappings:
    - deviceName: /dev/xvda
        ebs:
        volumeSize: 150Gi
    subnetSelector:
       Role: "private"
    securityGroupSelector:
       aws:eks:cluster-name: dev-cluster
    tags:
       app: app1-service
       karpenter.sh/discovery/node: GPU
       karpenter.sh/discovery/app: app1-service
       karpenter.sh/discovery: dev-cluster

and use this to deploy it app1-service.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: inflate
  namespace: app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: app1-service
  template:
    metadata:
      labels:
        app: app1-service
    spec:
      terminationGracePeriodSeconds: 0
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: app
                    operator: In
                    values:
                      - app1-service
      tolerations:
        - effect: NoSchedule
          key: app
          operator: Equal
          value: app1-service
      containers:
        - name: inflate
           image: public.ecr.aws/eks-distro/kubernetes/pause:3.2

Deploy it via kubectly apply -napp -f app1-service.yaml
Scale-up should provision the ami from the customAMISelector
Sclae down should deprovision and delete the node
Resource Specs and Logs
Below is the current config spec that got deployed to the cluster
$ kubectl get provisioner
NAME      AGE
default   9d
gpu       3d5h

$ kubectl get AWSNodeTemplate
NAME      AGE
default   3d5h
gpu       3d5h

$ kubectl get provisioner default gpu -o yaml
apiVersion: v1
items:
- apiVersion: karpenter.sh/v1alpha5
  kind: Provisioner
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"karpenter.sh/v1alpha5","kind":"Provisioner","metadata":{"annotations":{},"name":"default"},"spec":{"consolidation":{"enabled":true},"labels":{"node":"default"},"providerRef":{"name":"default"},"requirements":[{"key":"karpenter.sh/capacity-type","operator":"In","values":["spot"]},{"key":"node.kubernetes.io/instance-type","operator":"In","values":["r5.large"]},{"key":"kubernetes.io/os","operator":"In","values":["linux"]}]}}
    creationTimestamp: "2023-04-26T21:15:13Z"
    generation: 2
    managedFields:
    - apiVersion: karpenter.sh/v1alpha5
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:spec:
          .: {}
          f:consolidation:
            .: {}
            f:enabled: {}
          f:labels:
            .: {}
            f:node: {}
          f:providerRef:
            .: {}
            f:name: {}
          f:requirements: {}
      manager: HashiCorp
      operation: Update
      time: "2023-04-26T21:15:13Z"
    - apiVersion: karpenter.sh/v1alpha5
      fieldsType: FieldsV1
      fieldsV1:
        f:status:
          .: {}
          f:resources:
            .: {}
            f:attachable-volumes-aws-ebs: {}
            f:cpu: {}
            f:ephemeral-storage: {}
            f:memory: {}
            f:pods: {}
      manager: karpenter
      operation: Update
      subresource: status
      time: "2023-04-26T21:29:16Z"
    name: default
    resourceVersion: "39970268"
    uid: 3082a50c-7dcc-4e85-adfc-3c4dd78ea3b7
  spec:
    consolidation:
      enabled: true
    labels:
      node: default
    providerRef:
      name: default
    requirements:
    - key: karpenter.sh/capacity-type
      operator: In
      values:
      - spot
    - key: node.kubernetes.io/instance-type
      operator: In
      values:
      - r5.large
    - key: kubernetes.io/os
      operator: In
      values:
      - linux
    - key: kubernetes.io/arch
      operator: In
      values:
      - amd64
  status:
    resources:
      attachable-volumes-aws-ebs: "25"
      cpu: "2"
      ephemeral-storage: 20959212Ki
      memory: 16078488Ki
      pods: "29"

- apiVersion: karpenter.sh/v1alpha5
  kind: Provisioner
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"karpenter.sh/v1alpha5","kind":"Provisioner","metadata":{"annotations":{},"name":"gpu"},"spec":{"consolidation":{"enabled":true},"kubeletConfiguration":{"containerRuntime":"dockerd"},"labels":{"app":"app1-service"},"providerRef":{"name":"gpu"},"requirements":[{"key":"karpenter.sh/capacity-type","operator":"In","values":["on-demand"]},{"key":"node.kubernetes.io/instance-type","operator":"In","values":["g4dn.4xlarge"]}],"taints":[{"effect":"NoSchedule","key":"app","value":"app1-service"}]}}
    creationTimestamp: "2023-05-03T12:15:51Z"
    generation: 4
    managedFields:
    - apiVersion: karpenter.sh/v1alpha5
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:spec:
          .: {}
          f:consolidation:
            .: {}
            f:enabled: {}
          f:kubeletConfiguration:
            .: {}
            f:containerRuntime: {}
          f:labels:
            .: {}
            f:app: {}
          f:providerRef:
            .: {}
            f:name: {}
          f:requirements: {}
          f:taints: {}
      manager: HashiCorp
      operation: Update
      time: "2023-05-06T16:39:12Z"
    - apiVersion: karpenter.sh/v1alpha5
      fieldsType: FieldsV1
      fieldsV1:
        f:status:
          .: {}
          f:resources:
            .: {}
            f:attachable-volumes-aws-ebs: {}
            f:cpu: {}
            f:ephemeral-storage: {}
            f:memory: {}
            f:nvidia.com/gpu: {}
            f:pods: {}
      manager: karpenter
      operation: Update
      subresource: status
      time: "2023-05-06T16:41:37Z"
    name: gpu
    resourceVersion: "44220337"
    uid: 2d1ab463-06b0-46ae-b13e-9a665ba25a9b
  spec:
    consolidation:
      enabled: true
    kubeletConfiguration:
      containerRuntime: dockerd
    labels:
      app: app1-service
    providerRef:
      name: gpu
    requirements:
    - key: karpenter.sh/capacity-type
      operator: In
      values:
      - on-demand
    - key: node.kubernetes.io/instance-type
      operator: In
      values:
      - g4dn.4xlarge
    - key: kubernetes.io/os
      operator: In
      values:
      - linux
    - key: kubernetes.io/arch
      operator: In
      values:
      - amd64
    taints:
    - effect: NoSchedule
      key: app
      value: app1-service
  status:
    resources:
      attachable-volumes-aws-ebs: "39"
      cpu: "16"
      ephemeral-storage: 157274092Ki
      memory: 65042920Ki
      nvidia.com/gpu: "1"
      pods: "29"
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

  apiVersion: v1
items:
- apiVersion: karpenter.k8s.aws/v1alpha1
  kind: AWSNodeTemplate
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"karpenter.k8s.aws/v1alpha1","kind":"AWSNodeTemplate","metadata":{"annotations":{},"name":"default"},"spec":{"instanceProfile":"eks-1cc37185-87f0-0c88-44b4-4db5a32ae91a","securityGroupSelector":{"aws:eks:cluster-name":"dev-cluster"},"subnetSelector":{"Role":"private"},"tags":{"karpenter.sh/discovery":"dev-cluster","karpenter.sh/discovery/node":"default"}}}
    creationTimestamp: "2023-05-03T12:15:51Z"
    generation: 1
    managedFields:
    - apiVersion: karpenter.k8s.aws/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:spec:
          .: {}
          f:instanceProfile: {}
          f:securityGroupSelector:
            .: {}
            f:aws:eks:cluster-name: {}
          f:subnetSelector:
            .: {}
            f:Role: {}
          f:tags:
            .: {}
            f:karpenter.sh/discovery: {}
            f:karpenter.sh/discovery/node: {}
      manager: HashiCorp
      operation: Update
      time: "2023-05-03T12:15:51Z"
    name: default
    resourceVersion: "42727203"
    uid: fae27ccb-b308-404c-b622-b61233d71975
  spec:
    instanceProfile: eks-1cc37185-87f0-0c88-44b4-4db5a32ae91a
    securityGroupSelector:
      aws:eks:cluster-name: dev-cluster
    subnetSelector:
      Role: private
    tags:
      karpenter.sh/discovery: dev-cluster
      karpenter.sh/discovery/node: default
- apiVersion: karpenter.k8s.aws/v1alpha1
  kind: AWSNodeTemplate
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"karpenter.k8s.aws/v1alpha1","kind":"AWSNodeTemplate","metadata":{"annotations":{},"name":"gpu"},"spec":{"amiSelector":{"karpenter.sh/discovery":"dev-cluster"},"blockDeviceMappings":[{"deviceName":"/dev/xvda","ebs":{"volumeSize":"150Gi"}}],"labels":{"app":"app1-service"},"securityGroupSelector":{"aws:eks:cluster-name":"dev-cluster"},"subnetSelector":{"Role":"private"},"tags":{"app":"app1-service","karpenter.sh/discovery":"dev-cluster","karpenter.sh/discovery/app":"app1-service","karpenter.sh/discovery/node":"gpu"}}}
    creationTimestamp: "2023-05-03T12:15:51Z"
    generation: 10
    managedFields:
    - apiVersion: karpenter.k8s.aws/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:spec:
          .: {}
          f:amiSelector:
            .: {}
            f:karpenter.sh/discovery: {}
          f:blockDeviceMappings: {}
          f:securityGroupSelector:
            .: {}
            f:aws:eks:cluster-name: {}
          f:subnetSelector:
            .: {}
            f:Role: {}
          f:tags:
            .: {}
            f:app: {}
            f:karpenter.sh/discovery: {}
            f:karpenter.sh/discovery/app: {}
            f:karpenter.sh/discovery/node: {}
          f:userData: {}
      manager: HashiCorp
      operation: Update
      time: "2023-05-06T15:33:52Z"
    name: gpu
    resourceVersion: "44207417"
    uid: 838a5d29-b348-4476-adf2-e9f9712222c2
  spec:
    amiSelector:
      karpenter.sh/discovery: dev-cluster
    blockDeviceMappings:
    - deviceName: /dev/xvda
      ebs:
        volumeSize: 150Gi
    securityGroupSelector:
      aws:eks:cluster-name: dev-cluster
    subnetSelector:
      Role: private
    tags:
      app: app1-service
      karpenter.sh/discovery: dev-cluster
      karpenter.sh/discovery/app: app1-service
      karpenter.sh/discovery/node: gpu
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Logs:
2023-05-06T15:45:53.971Z	ERROR	controller.provisioner	Could not schedule pod, incompatible with provisioner "default", incompatible requirements, key karpenter.sh/provisioner-name, karpenter.sh/provisioner-name DoesNotExist not in karpenter.sh/provisioner-name In [default]; incompatible with provisioner "gpu", did not tolerate app=app1-service:NoSchedule	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:47:57.971Z	DEBUG	controller.provisioner	relaxing soft constraints for pod since it previously failed to schedule, removing: spec.topologySpreadConstraints = {"maxSkew":1,"topologyKey":"topology.kubernetes.io/zone","whenUnsatisfiable":"ScheduleAnyway","labelSelector":{"matchLabels":{"app.kubernetes.io/instance":"karpenter","app.kubernetes.io/name":"karpenter"}}}	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:47:57.982Z	ERROR	controller.provisioner	Could not schedule pod, incompatible with provisioner "gpu", did not tolerate app=app1-service:NoSchedule; incompatible with provisioner "default", incompatible requirements, key karpenter.sh/provisioner-name, karpenter.sh/provisioner-name DoesNotExist not in karpenter.sh/provisioner-name In [default]	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:47:57.982Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "f60dacd", "pods": 2}
2023-05-06T15:47:57.982Z	INFO	controller.provisioner	serviced new node(s) to fit pod(s)	{"commit": "f60dacd", "nodes": 1, "pods": 1}
2023-05-06T15:47:57.989Z	INFO	controller.provisioner	launching node with 1 pods requesting {"cpu":"125m","pods":"3"} from types g4dn.4xlarge	{"commit": "f60dacd", "provisioner": "gpu"}
2023-05-06T15:47:59.662Z	DEBUG	controller.provisioner.cloudprovider	created launch template	{"commit": "f60dacd", "provisioner": "gpu", "launch-template-name": "Karpenter-dev-cluster-123456", "launch-template-id": "lt-0f3aef76435882c8d"}
2023-05-06T15:48:02.821Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "f60dacd", "provisioner": "gpu", "launched-instance": "i-02c2ad45690ea2d4c", "hostname": "ip-10-111-22-33.ec2.internal", "type": "g4dn.4xlarge", "zone": "us-east-1a", "capacity-type": "on-demand"}
2023-05-06T15:48:17.886Z	DEBUG	controller.provisioner	relaxing soft constraints for pod since it previously failed to schedule, removing: spec.topologySpreadConstraints = {"maxSkew":1,"topologyKey":"topology.kubernetes.io/zone","whenUnsatisfiable":"ScheduleAnyway","labelSelector":{"matchLabels":{"app.kubernetes.io/instance":"karpenter","app.kubernetes.io/name":"karpenter"}}}	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:48:17.886Z	ERROR	controller.provisioner	Could not schedule pod, incompatible with provisioner "default", incompatible requirements, key karpenter.sh/provisioner-name, karpenter.sh/provisioner-name DoesNotExist not in karpenter.sh/provisioner-name In [default]; incompatible with provisioner "gpu", did not tolerate app=app1-service:NoSchedule	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:48:20.000Z	DEBUG	controller.deprovisioning	relaxing soft constraints for pod since it previously failed to schedule, removing: spec.topologySpreadConstraints = {"maxSkew":1,"topologyKey":"topology.kubernetes.io/zone","whenUnsatisfiable":"ScheduleAnyway","labelSelector":{"matchLabels":{"app.kubernetes.io/instance":"karpenter","app.kubernetes.io/name":"karpenter"}}}	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:48:40.837Z	DEBUG	controller.deprovisioning	relaxing soft constraints for pod since it previously failed to schedule, removing: spec.topologySpreadConstraints = {"maxSkew":1,"topologyKey":"topology.kubernetes.io/zone","whenUnsatisfiable":"ScheduleAnyway","labelSelector":{"matchLabels":{"app.kubernetes.io/instance":"karpenter","app.kubernetes.io/name":"karpenter"}}}	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:49:01.586Z	DEBUG	controller.provisioner	relaxing soft constraints for pod since it previously failed to schedule, removing: spec.topologySpreadConstraints = {"maxSkew":1,"topologyKey":"topology.kubernetes.io/zone","whenUnsatisfiable":"ScheduleAnyway","labelSelector":{"matchLabels":{"app.kubernetes.io/instance":"karpenter","app.kubernetes.io/name":"karpenter"}}}	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:49:01.587Z	ERROR	controller.provisioner	Could not schedule pod, incompatible with provisioner "default", incompatible requirements, key karpenter.sh/provisioner-name, karpenter.sh/provisioner-name DoesNotExist not in karpenter.sh/provisioner-name In [default]; incompatible with provisioner "gpu", did not tolerate app=app1-service:NoSchedule	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:49:52.987Z	DEBUG	controller.deprovisioning	relaxing soft constraints for pod since it previously failed to schedule, removing: spec.topologySpreadConstraints = {"maxSkew":1,"topologyKey":"topology.kubernetes.io/zone","whenUnsatisfiable":"ScheduleAnyway","labelSelector":{"matchLabels":{"app.kubernetes.io/instance":"karpenter","app.kubernetes.io/name":"karpenter"}}}	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:50:28.991Z	DEBUG	controller.aws	deleted launch template	{"commit": "f60dacd"}
2023-05-06T15:50:29.096Z	DEBUG	controller.aws	deleted launch template	{"commit": "f60dacd"}
2023-05-06T15:50:30.099Z	INFO	controller.inflightchecks	Inflight check failed for node, Expected resource "nvidia.com/gpu" didn't register on the node	{"commit": "f60dacd", "node": "ip-10-111-22-33.ec2.internal"}
2023-05-06T15:50:31.541Z	DEBUG	controller.provisioner	relaxing soft constraints for pod since it previously failed to schedule, removing: spec.topologySpreadConstraints = {"maxSkew":1,"topologyKey":"topology.kubernetes.io/zone","whenUnsatisfiable":"ScheduleAnyway","labelSelector":{"matchLabels":{"app.kubernetes.io/instance":"karpenter","app.kubernetes.io/name":"karpenter"}}}	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:50:31.541Z	ERROR	controller.provisioner	Could not schedule pod, incompatible with provisioner "default", incompatible requirements, key karpenter.sh/provisioner-name, karpenter.sh/provisioner-name DoesNotExist not in karpenter.sh/provisioner-name In [default]; incompatible with provisioner "gpu", did not tolerate app=app1-service:NoSchedule	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}
2023-05-06T15:50:44.504Z	DEBUG	controller.deprovisioning	relaxing soft constraints for pod since it previously failed to schedule, removing: spec.topologySpreadConstraints = {"maxSkew":1,"topologyKey":"topology.kubernetes.io/zone","whenUnsatisfiable":"ScheduleAnyway","labelSelector":{"matchLabels":{"app.kubernetes.io/instance":"karpenter","app.kubernetes.io/name":"karpenter"}}}	{"commit": "f60dacd", "pod": "karpenter/karpenter-57c5f67dd6-7g9fd"}

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Do you see the karpenter.sh/initialized label on the deployed node? If not, you may be hitting this troubleshooting item.

Thanks @jonathan-innis  the karpenter.sh/initialized label is not showing up in the node. Also I added the below to the deployment and the pod didn't get added to the node and the node doesn't have the label.
...
...
  resources:
    limits:
    nvidia.com/gpu: 1
....
....

@iamtito You'll need to install the https://github.com/NVIDIA/k8s-device-plugin as a daemonset on the cluster in order for the resource to get registered on GPU nodes so that pods can schedule to it. This will also help the karpenter.sh/initialized issue since Karpenter isn't considering the node as initialized because of the lack of that resource.
Alternatively, if you use the Bottlerocket AMIFamily, the image has built-in support for the plugin so that you don't need to install the DS separately.


HTML view of Dropdown documentation missing  tag

In the HTML tab of the examples for the Dropdown and Dropdown - Disabled the <i> tag before the <select> is missing that is needed in order for the down caret icon to appear.
Everything shows up correctly in the Example tabs because the tag is in the source for those.

OK - we actually think we know what's happening here. It looks like the CMS might be ripping that line of code out. Ouch!
Good find - we'll put it on the backlog and scan the rest of the components as well to see if it did something similar. Thanks!


pivpn install ends after configuration of static ip

PiVPN Issue Template

Console output of curl install.pivpn.io | bash
pi@raspberrypi:~ $  curl -L https://install.pivpn.io | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   178  100   178    0     0    266      0 --:--:-- --:--:-- --:--:--   266
100 53505  100 53505    0     0  60604      0 --:--:-- --:--:-- --:--:-- 60604
:::
::: sudo will be used for the install.
::: Verifying free disk space...
:::
::: Checking apt-get for upgraded packages.... done!
:::
::: Your system is up to date! Continuing with PiVPN installation...
::: Static IP already configured.

Console output of pivpn
pi@raspberrypi:~ $ pivpn
-bash: pivpn: command not found.

Issue
I hope I can clarify my problem. You have to know that I'm almost a linux noob, sorry for that.
I tried to install pivpn several times on a raspberry pi 3 running raspbian jessie. I origninally tried the latest image "2017-07-05-raspbian-jessie" but as well "2017-06-21-raspbian-jessie".
With both installations I'm not able to install pivpn.
I start the installation and the IP configuration comes up. After I set a static IP the installer just exits with no error or something else as you can see above. I tried to configure a static IP before starting the setup but the same problem occurs.
I installed pivpn on a raspberry pi 2 with the latest raspbian jessie image of 2017-07-05 with no errors and the system is running fine but with the raspi 3 I'm not able to get it running.
If some information is missing please tell me what I have to do.
Thanks in advance and regards
Yeza
Console output of cat /etc/os-release
pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Console output of uname -a
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux

Same here, I'm also on a RB3 with Raspbian 8. The installation ended with the ip config and the pivpn command can not be found. Whats wrong here?

@Yezariael @levinus
Just a curiosity question ... if you are using raspbian fresh installs why are you using Jessie instead of stretch?
Will look into this and try to check if the problem is somewhere in the script ... but seems that might be something broken on your side ...

Same issue here with pi zero running raspbian stretch.
pi@pizerovpn:~ $ curl -L https://install.pivpn.io | bash
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100   178  100   178    0     0    174      0  0:00:01  0:00:01 --:--:--   174
100 53505  100 53505    0     0  29237      0  0:00:01  0:00:01 --:--:--  496k
:::
::: sudo will be used for the install.
::: Verifying free disk space...
:::
::: apt-get update has not been run today. Running now... done!
:::
::: Checking apt-get for upgraded packages.... done!
:::
::: Your system is up to date! Continuing with PiVPN installation...
pi@pizerovpn:~ $
pi@pizerovpn:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

@cfcolaco as a linux noob I just did what the PiVPN page says.

Strongly recommend using the latest Jessie Lite image but the normal Jessie image will work as well.

I tried Stretch as well but with it I get an error during generating the keys, I think a path changed.
If it would work with Stretch that would be fine for me as well :)
I did a couple of tries always with a completely fresh install of Jessie (and Stretch). No idea what should be the problem on my side.
Today i braught my Pi2 running Jessie, PiVPN and Pihole to work and I will try to copy an image to the problem-pi-3.

I actually used a fresh Stretch installation and everything worked fine, seems there was something wrong on my side before.

@Yezariael Hmm Thank you for bringing that to my attention!!! we recently added the support for stretch .. so a few things need to be updated!!
@levinus Good to know!! However, I would like to be able to replicate this ... since I have seen this happening before but I don't remember why!! =/ and would be good to understand if there is something we can do on our side to help out!

@cfcolaco Today I did a clean install of Jessie and PiVPN on a completely other Raspi 3 and I have the same issue. After setting the IP to static mode the setup ends.
As a second I installed PiVPN on the same Raspi 3 with a clean install of Stretch. I get an error while trying to read the file in /etc/openvpn/easy-rsa/pki/index.txt.attr and have problems to access the VPN with Android.
I'll create a new issue for that.

@Yezariael about the android there is already an issue regarding that ... the problem relies on the mobile apps! check here: #364
I think is what you might be looking for!
About the rest. .. need to do more testing! eventually, tomorrow might go to hardware store and buy and extra RPI to have with me and do some testings ...

Trying to install from DietPi, same issue. Installer just quits.  Is there a log file anywhere?

@cfcolaco thanks for your great support!
Yes, I've already seen the thread #364 and tried the other app with success.

@Yezariael so .. I still do not understand ...
Can you exaplain me please exactly ... What have you done to fix??

Closing this as per issue #388 .
Any questions read the mentioned please, if any issues persist please help us out and do things in a more organized way.
Kind regards to you all.


Updating VS Code should check for updates first.

If I have an update pending and a new update comes, in order to get the latest version I need to update (and reload window), then check for updates and update again (reloading the window again).
Steps to Reproduce:

Open VS Code Insiders
Check for updates --> a little 1 appears.
Wait 24 hours
Click the gear
Find out there is no way to check for new updates until the previous update is installed.

Does this issue occur when all extensions are disabled?: Yes

In my case new insider builds come out super early in the morning and are promptly detected. Sometimes a second insiders build will then be released an hour or two later though, so when I finally get back to the editor I have to update multiple times. This would be a great quality-of-life improvement.


Add PBR tutorial - updated for CLA check

This replaces #53

@Khronoswebmaster Opened a new PR for that, as of https://github.com/KhronosGroup/glTF-Tutorials/pull/53#issuecomment-844223848 , but it seems still to do the check. Let's see what the CLA people say.

cla-assistant support has pointed out that the link to cla-assistant on this PR points to PR46 (https://cla-assistant.io/KhronosGroup/glTF-Tutorials?pullRequest=46). This suggets this new PR wasn't entirely new and is somehow a copy of PR46? Creating an entirely new PR should resolve the issue we are seeing.

GitHub apparently determines when two PRs are created from the same state (i.e. from the same hash or so). E.g. it did not allow me to create "the same" PR again, before closing the old one. Maybe this CLA thingy also identifies the PR by the hash (and not by its # number)? Whatever, I'll try to work around that.


[WIP] Fix add worker

closes partly #99

I'm fixing the last issue. It's with the register node task. I think the certs are missing somehow...
May 29 16:11:21 production-worker-04 kubelet[12336]: F0529 16:11:21.515541   12336 server.go:218] unable to load client CA file /etc/kubernetes/pki/ca.crt: open /etc/kubernetes/pki/ca.crt: no such file or directory
May 29 16:11:21 production-worker-04 systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
May 29 16:11:21 production-worker-04 systemd[1]: kubelet.service: Unit entered failed state.
May 29 16:11:21 production-worker-04 systemd[1]: kubelet.service: Failed with result 'exit-code'.

i think if the progress bar is the only issue I can merge this, so the very basic stuff gets working
LGTM

Adding an external node results in:
panic: runtime error: slice bounds out of range
goroutine 1 [running]:
github.com/xetys/hetzner-kube/pkg/clustermanager.PrivateIPPrefix(0x0, 0x0, 0xc420206610, 0xa)
/root/go/src/github.com/xetys/hetzner-kube/pkg/clustermanager/wireguard.go:61 +0xad
github.com/xetys/hetzner-kube/cmd.glob..func3(0xb974a0, 0xc42001d140, 0x0, 0x4)
/root/go/src/github.com/xetys/hetzner-kube/cmd/cluster_add_external_worker.go:133 +0x4b7
github.com/xetys/hetzner-kube/vendor/github.com/spf13/cobra.(*Command).execute(0xb974a0, 0xc42001d100, 0x4, 0x4, 0xb974a0, 0xc42001d100)
/root/go/src/github.com/xetys/hetzner-kube/vendor/github.com/spf13/cobra/command.go:702 +0x2bd
github.com/xetys/hetzner-kube/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xb998c0, 0xc42014a9c5, 0x0, 0x0)
/root/go/src/github.com/xetys/hetzner-kube/vendor/github.com/spf13/cobra/command.go:783 +0x349
github.com/xetys/hetzner-kube/vendor/github.com/spf13/cobra.(*Command).Execute(0xb998c0, 0x91c952, 0x5)
/root/go/src/github.com/xetys/hetzner-kube/vendor/github.com/spf13/cobra/command.go:736 +0x2b
github.com/xetys/hetzner-kube/cmd.Execute()
/root/go/src/github.com/xetys/hetzner-kube/cmd/root.go:51 +0x82
main.main()
/root/go/src/github.com/xetys/hetzner-kube/main.go:20 +0x20

Ok so external workers is still broken (missed the comment) do we have any pointers as to why yet?


Add support for hosting Blazor Web components directly in Windows Forms (.NET Core)

Did you think we forgot about Windows Forms (WinForms)? After doing WPF in #313, let's get Blazor Web working in Windows Forms too!

@Eilon  你太棒了，看到MoileBlazorBindings天天在进步，真高兴

WinForms sample app is here: https://github.com/xamarin/MobileBlazorBindings/tree/master/samples/WinFormsBlazorSample
And it uses this standard Razor Class Library (RCL) as its web content: https://github.com/xamarin/MobileBlazorBindings/tree/master/samples/SharedProjects/RazorClassLibrarySample


[Question] Envoy binary size increase

We had forked envoy around the v1.11 release and at that time the stripped binary size was around 27M. I recently merged the v1.14 release and noticed that the binary size had doubled to 55M for the same build config. Are there any high level new filter/features that were added in the last couple of releases that would cause such a jump?
@sumukhs

Nothing specific comes to mind, but that's a huge increase. Not sure what filters, etc. you are bringing in. I would definitely only compile the filters you are actually using. @junr03 has done size analysis for Envoy Mobile and can possibly provide some scripts if you are looking to better understand where size is being spent.

That would be very helpful. Thanks!

I know from testing that the Kafka filter alone adds about 11MB. This is another reason why I advocate for custom builds where only the extensions you need are compiled into the binary (vs. the kitchen sink images / approach).

@appario since v1.11 the v3 APIs were introduced. That by no means account for such a big increase, but it does account for a non-trivial amount (for example, it accounts for ~10% of Envoy Mobile's size under some measures).
You could follow the instructions here to do some analysis on your Envoy binary. I have used a tool called Bloaty, per the instructions. Bloaty even allows you to compare binaries and see where the increases happened.


Reactivating terminals...

In my vscode-copilot workspace, I have this status bar spinner that never goes away

I see this in the Terminal log when the window starts
2024-10-11 15:06:11.602 [error] Exception occurred during xterm disposal [{}]
2024-10-11 15:06:11.608 [error] Exception occurred during xterm disposal [{}]
2024-10-11 15:06:11.609 [error] Exception occurred during xterm disposal [{}]

@meganrogge do you know what causes this status bar item to appear? I can't find it searching the main repo for that string.

@roblourens any ideas what could be adding this? Some extension?

this is coming from python, I see it pretty often too.


Not sure what do I miss on Fedora

First of all thanks for the project and all the work you put in. It looks very interesting and useful but somehow I can't make it work.
Fedora 36 here with OpenJDK 11, vpn.sh status looks ok-ish (v1.80, CShell running, SNX installed, CHSell self-signed CA cert visible, but in status report there is a line "VPN off", "VPN signatures" are empty).
Opening FF v102 on https://vpn.address.com renders "Secure connection failed".
Going to https://localhost:14186/id shows JSON response like {"id":"some-uuid-here"}. Curling verbose same link, shows certificate(O=check Point), with same JSON response.
starting vpn.sh in new terminal or vpn.sh restart doesn't bring me any further.
Thanks :)

Hi Vladi,
That seems a problem either with mobile portal setup on VPN side and/or the
certificate installed on the Checkpoint side or expired, if any installed.
Most probably certificate expired.
You can check the certificate with:
openssl s_client -showcerts -servername vpn.address.com -connect
vpn.address.com:443
I think you can bypass the error temporarily doing in Firefox:
about:config
and setting security.ssl.enable_ocsp_stapling to false until the underlying
issue is fixed.
In holidays, can't add code to the script for a week to status to check for
that.
Regards
On Tue, 26 Jul 2022, 18:29 Vladi, @.***> wrote:

First of all thanks for the project and all the work you put in. It looks
very interesting and useful but I can't make it work somehow.
Fedora 36, vpn.sh status looks ok-ish (v1.80, CShell running, SNX
installed, CHSell self-signed CA cert visible, but in status report there
is a line "VPN off", "VPN signatures" are empty).
Opening FF v102 on https://vpn.address.com renders "Secure connection
failed".
Going to https://localhost:14186/id shows JSON response like
{"id":"some-uuid-here"}.
starting vpn.sh in new terminal or vpn.sh restart doesn't bring me any
further.
—
Reply to this email directly, view it on GitHub
https://github.com/ruyrybeyro/chrootvpn/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPDBPYGHDL7HQRBMREZ4C3VWAOARANCNFSM54WXXVLA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

hmm.. openssl response looks fine, all certificates in chain have valid dates.
Ok, time for you to enjoy holidays, maybe we can analyse more when you are back.
Cheers

The mobile portal site has to open without any software/agent installed.
e.g the issue is not the software installed.
If vpn.sh is ending the setup, is because it ignores certificates being
valid intentionality when download scripts from your VPN. So at least we
know the web service is answering.
Please send the openssl output to my @.*** email.
On Wed, 27 Jul 2022, 07:55 Vladi, @.***> wrote:

hmm.. openssl response looks fine, all certificates in chain have valid
dates.
Ok, time for you to enjoy holidays, maybe we can analyse more when you are
back.
Cheers
—
Reply to this email directly, view it on GitHub
https://github.com/ruyrybeyro/chrootvpn/issues/1#issuecomment-1196335275,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPDBPY6SVBOUK6L27TU453VWDMPRANCNFSM54WXXVLA
.
You are receiving this because you commented.Message ID:
@.***>

you are right, something is wrong with that vpn web service.
wget request gives output as:
HTTP request sent, awaiting response... Read error (The TLS connection was non-properly terminated.) in headers.
Retrying.

Interestingly enough from other Linux machine, output is slightly different:
HTTP request sent, awaiting response... Read error (Success.) in headers.
Retrying.

Nevertheless wget is retrying on both systems.

Ok, thanks. How about Chrome, is it able to open it?
If you send me by a side channel the real DNS address, I might be able to
have a look by Monday.
Regards
On Wed, 27 Jul 2022, 19:42 Vladi, @.***> wrote:

you are right, something is wrong with that vpn web service.
wget request gives output as:
HTTP request sent, awaiting response... Read error (The TLS connection was non-properly terminated.) in headers.
Retrying.
Interestingly enough from other Linux machine, output is slightly
different:
HTTP request sent, awaiting response... Read error (Success.) in headers.
Retrying.
Nevertheless wget is retrying on both systems.
—
Reply to this email directly, view it on GitHub
https://github.com/ruyrybeyro/chrootvpn/issues/1#issuecomment-1197222347,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPDBP6ZQ7UKTWWDQPY4NWLVWF7ILANCNFSM54WXXVLA
.
You are receiving this because you commented.Message ID:
@.***>

Same issue with Chrome This page isn’t working ERR_EMPTY_RESPONSE

Btw, just added in vpn.sh to status printing the VPN X.509 certificate.


What's the difference between omni_send and omni_createpayload_simplesend?

”https://github.com/OmniLayer/omnicore/wiki/Use-the-raw-transaction-API-to-create-a-Simple-Send-transaction“, I have seen。step 3 return null。

Hi there,

omni_send is a command to create, sign and broadcast a send transaction in one step
omni_createpayload_simplesend is a command to create only the payload for a send transaction

You can probably use omni_send directly, which is less hassle.


Sudoko using backtracking

This is sudoku solver made using c++. Program is having a grid and using backtracking we are solving the sudoko given

update project_doc.md file with the description of your project or add another readme file in your project folder and raise another PR.


[MINOR][DOCS] add link for Debugging your Application in running-on-yarn.html#launching-spark-on-yarn

What changes were proposed in this pull request?
add link for Debugging your Application in running-on-yarn.html#launching-spark-on-yar
Why are the changes needed?
Currrently on running-on-yarn.html page launching-spark-on-yarn section, it mentions to refer for Debugging your Application. It is better to add a direct link for it to save reader time to find the section

Does this PR introduce any user-facing change?
Yes.
Docs changes.  add link for Debugging your Application in running-on-yarn.html#launching-spark-on-yarn section
Updated behavior:

How was this patch tested?
manual test has been performed to test the updated

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Jenkins test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30745/
Test PASSed.

Test build #126133 has started for PR 29154 at commit f0f5793.

Test build #126133 has finished for PR 29154 at commit f0f5793.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126133/
Test PASSed.

Jenkins test this please

Jenkins test this please

Test build #126217 has started for PR 29154 at commit 96fa931.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30831/
Test PASSed.

Test build #126217 has finished for PR 29154 at commit 96fa931.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126217/
Test PASSed.

Merged to master, branch-3.0 and branch-2.4.


feat: update partial templates to match naming conventions and prefix with fullstack namespace

Description
This pull request changes the following:

update partial templates to match naming conventions (camelCase)
prefix partial template names with fullstack namespace fullstack.*

Related Issues

Closes #210

:tada: This PR is included in version 0.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Feature Request: Undefined step, leading to suggested alternative(s) from current glue

Summary
Wouldn't it be nice if Cucumber could suggest step definitions from the current project's glue that are similar to the undefined step that is currently being matched.
Possible Solution
There are fuzzy regex matching libraries available e.g. http://laurikari.net/tre/
Context & Motivation
When a step fails to match an undefined error is thrown and a snippet emitted. Often the failure is due to simple mistyping by the user. It would be nice if Cucumber could suggest step definitions that almost matched.
This could make it much simpler to pick up many categories of error, such as missing spaces and/or misspelt words

That's a lovely idea!

Excellent...!

++


Math improvements

This repo looks fantastic:
https://github.com/benrbray/prosemirror-math
Related: schema needs to parse begin{ statements.

We have made a lot of improvements here, and took some inspiration from prosemirror-math for the styling/interaction - decided in the end to not go with @benrbray's library for now. We still have a lot of custom pieces related to our reactive math/history/collaboration that need some custom work.
Example

Adding Dynamic Math Rendering
See https://curvenote.dev/article/equation for where we are going with the editor

I would be curious to see if there are some pieces in the prosemirror-math repo that we could use - some of the paste pieces from wikipedia look like the could be very generalized!
If you have some comments or would like to meet @benrbray let me know!!


Add beans adds 2nd Integration CRD

Describe the Bug
Similar behavior to #2043, but Integration CRD was supposed to work just like Camel Route where the beans are placed in top level FlowsWrapper.metadata. Something wrong is going on.
https://github.com/KaotoIO/kaoto-ui/assets/265462/fac8652c-b2ee-4ee9-b951-8c40ca34dbac
Steps to Reproduce the Bug or Issue

Choose Integration
Open Beans UI
Click Add beans
Open code editor

Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 0.30.0]

This would be caused by https://github.com/KaotoIO/kaoto-backend/issues/717

Verified it's addressed by KaotoIO/kaoto-backend#741

Duplicate of KaotoIO/kaoto-backend#717


IOC Extract doesn't extract Ambiguous IP Addresses

The ipaddress module does not accept IP addresses with ambiguous decimal/octal values.
In this example, the IP address is rejected because of the ambiguous final octet.
>>> from ipaddress import ip_address
>>> ip_address("<IP_ADDRESS>")
ValueError: '<IP_ADDRESS>' does not appear to be an IPv4 or IPv6 address

Because iocextract uses ip_address to validate IP candidates, this causes iocextract to fail to extract similar ambiguous IP addresses.
Although the IP address is technically ambiguous, I recommend logging the ambiguity and then trying again with an address with the leading zeroes removed (to prefer decimal).
>>> re.sub(r"0+([0-9])", r"\1", "<IP_ADDRESS>")
'<IP_ADDRESS>'

Thanks, @malvidin . Do you mind opening this issue in the stoq-plugins-public repo, so it can be tracked there instead? This isn't a core framework issue.

As mentioned above, this applies to the public plugins, not the framework.


Analyzer fixes after upgrading to VS 15.3

Fixed #1370

I think it should be ok: for the analyzer it may just change the order in which the diagnostics are reported and for the code fix, the specified args only help us determine if a bool is true or false so order won't matter, and for the default args, order might change (not sure) but their evaluation order won't matter since they can only be constants.

Hmm, for some reason on travis the Microsoft.CodeAnalysis package being restored is 2.3.1, but it fails looking for 2.3.0 when building. Going to try adding an explicit package reference.

Nope, that didn't work. Upon close inspection it appears the problem occurs when building a project that uses the analyzers. Maybe 2.3.0 is the latest available for use during analysis. Bumping versions down to see if that fixes it.

Still not working. This seems to be the same issue: https://github.com/dotnet/roslyn-analyzers/issues/1215. Looks like we need to use a newer version of CSC. Is that something you specify to travis?

Perhaps setting the dotnet version in the .travis.yml to 1.1.0? What do you think?

Superseded by #1376


bug: Birthday Custom Command not sending birthday messages.

Expected behaviour
Bot was supposed to send a birthday message on the set date of a member.
Actual behaviour
No birthday announcement message was sent.
Steps to reproduce.
Bot was set up as per main cc and the update. New birthdays were added and -startbday was initiated with a minimum of 2 minutes delay from current time.
Additional context
No response
Terms

[x] I agree to follow this project's Code of Conduct.
[X] I have searched existing issues for similar reports.

found the problem on why it isn't sending. timezones suck. 🤦


Move create user profiles to monitoring process

CreateProfile Win32 API requires the admin user SID to be present in the calling process token.

Profile creation is handled by a dedicated service instead of the monitoring process.


Altitude of Slider indicator is top, instead of middle

The indicator should be centered over the desired value, not directly under it.

Closed by 16679dafffb8d4f6486af87fe9490148df2c02e4.


Combining imports from the same file

Have there been any plans to combine all (side-effect-free) imports from the same file into a single import statement?
We're using import-sort in combination with Prettier and would benefit a lot from this feature.

I would like this as well.
Currently I'm using VS Code's Organize Imports feature, but it has a huge downside as of Feb 2021 - it removes the unused imports as well 😵 https://github.com/microsoft/TypeScript/issues/36085

Looks like import-sorter from @SoominHan does this, among other features (also with a lot of configuration options for this)! 💯
Using it via the JS/TS Import/Export Sorter VS Code Extension by @daidodo


Minor grammatical fixes

Like the project a lot but not quite well-versed enough in rust yet to help with the low-level stuff; figured I'd try and help with something though :)

Thanks for your contribution!


Add slides

Topics: Validation sets and semantic image segmentation

It looks like your file still lacks the ".pdf" file extension. Can you rename it?

Ping


Consider deleting AllSquareSizes

##Context
After implementing square size independent commitments, it seems like celestia-app no longer needs:
https://github.com/celestiaorg/celestia-app/blob/24626ff8d00854d7e0027abcfdf50de1a2aee6a3/x/blob/types/square_sizes.go#L25-L27
Proposal
Investigate if AllSquareSizes is still used. If not, remove it and related tests.

:axe:


Authentication

Authenticate users view list of companies update company details Add contacts to a company

 Authentication | Extend the User API as appropriate to relate the User information from the HTTP request header to a user record in the TFRS database |3|

implemented


Impossible to download generated reports

Branch name: master
I'm submitting a bug report
Current behavior:
Generated reports (like PV) are not proposed for downloading. But they are well generated.
Expected behavior:
Once the form is filled and the Generate button pressed, the resulting document should come out allowing me to download it.
Steps to reproduce:

Open the platform
Navigate to PV report page
Fill the form
Click on "Generer" button.

Platform info :

Ubuntu OS
Payara server
Mozilla firefox browser

I don't really know why we are facing this issue. The behaviour seems to be correct with Google Chrome only this is why I advertise people to use this browser instead.
It definitely needs to be investigated.


feat: Making saving more secure

What does this PR do?
Making saving more secure
Motivation
#772
Additional Notes

@WaterLemons2k 抽空看下有什么问题否


Create a more detailed documentation

I am new to AngularJs development, and it really helps when there's a more detailed documentation (e.g.: explaining how to use the service to extract information).

Please provide a more detailed description, it's hard to understand what exactly should I improve.....

Angular-embedly has been great for embedding videos/photos, but let's say I am just trying to get a 'title', or the 'thumbnail_url' from a given URL, or the 'html' (to post it somewhere). I believe I should use 'embedlyService' to do that, right? The documentation doesn't show how to do it, I've been trying to figure it out but couldn't make it yet.

@brasileirorodrigo have you looked at the embedly documentation?  I don't want to create duplicates..

@Urigo, I did (and also I have checked oEmbed's docs). The thing is not really about their documentation . It is quite actually about how to obtain the different parts of the .json file through Angular-Embedly.
I have gotten to embed the title on the directive (by making some changes in the switch statement and some other places):
...
scope.embedTitle = data.data.title;
...

But it is not an embedding issue, it is more of an extracting issue. I believe the part of the code that may solve my issue is this (embedlyService):
            this.extract = function(inputUrl) {
                var escapedUrl = encodeURI(inputUrl);
                var embedlyRequest = getProtocol + '://api.embed.ly/1/extract?key=' + key + '&url=' +  escapedUrl;
                return $http({method: 'GET', url: embedlyRequest});
            };

I have been trying to access it from the controller.js, in many different ways, for example:
embedlyModule.controller('embedCtrl', ['$scope','$http','embedlyService', function($scope, $http, embedlyService) {
    $scope.urlToSearch = 'https://www.youtube.com/watch?v=U9PlYbmEWOk';
    console.log(embedlyService.extract('$scope.urlToSearch'));
}]);

But it never works. I do really believe that solving such problem is super-easy, but it is quite difficult for a beginner, as the module.provider is a sort of a function:
(function (module) {
    module.provider('embedlyService', function () {

And working with these kinds of providers started with a function is not covered on any tutorial I found on the web that teaches how to deal with services from the controller.
I hope I haven't been too redundant or confusing.. Thanks!


chore: update to bee 1.11.0

Updated Bee version 1.11.0-rc1-d0b144a3

🗒 Bee 1.11.0-rc1 Release notes
Changelog

d0b144a3 fix: mutable batches do not stop uploads that reach max utilization (#3685)
4de93a97 fix: cancel bee node construction while waiting on nat manager (#3688)
4aa6ee45 feat: residual migration (#3686)
a6ae2ee4 chore: go mod tidy (#3687)
45547e92 chore(api): stamper putter cleanups (#3678)
c32275ab chore: remove overlay mining (#3684)
b433c130 fix: depthmonitor to track active syncing counter instead of rate (#3680)
8baf9338 fix: reduce depthmonitor target size to 40 percent (#3682)
8ac5e27a feat: stake withdraw role (#3667)
84b76047 fix: gracefully suspend bee node on interrupt signal (#3671)
ab68b284 fix: add deferred header to allowed cors headers (#3669)

Closing in favor #813