map uid/guid to different ids

My understanding is that when postfix starts it uses a couple of user/group that are mapping to uid 101/102.
My problem is that I need this group to read the config folder from the host.
On the host the uid 101 maps to is something like system-journal, this means that on the host I have to give the postfix config file are rather confusing looking permission.
Is there some what to force the postfix container to use alternate uid/gids so that I can map them to unused  uid/gids on the host.
I can then create a postfix user on the host with the same uid as the containers postfix user and my host permissions now look sensible.

I note that your documentation states:

While I cannot guarantee IDs (they are auto-generated by package manages), they tend to be fairly consistent across specific distribution. Please be aware of this if you are switching images from Alpine to Debian to Ubuntu or back.

I don't believe this is correct because if you create the users/groups before running the package manager they should use the existing uid/guid.
I play a similar game for the maria db container:
# add our user and group first to make sure their IDs get assigned consistently

RUN groupadd -g 2002 -r mysql && useradd -u 2002 -r -g mysql mysql --home-dir /var/lib/mysql

So if the container where to take a couple of env vars with the desired uid/gid then I think that would provide a solution.

HI Brett,
Thank you for your comment. Unfortunately, (system) users are assigned to apps when the container is built, not when it's run.
So implementing ENV vars would do nothing more than fail to start the container if you were to change them.
If you do have any good ideas, I'm open to pull requests.
B

So plan b:
assign the users to a higher UID that have a lower chance of causing a
collision.
e.g. 20001
On Thu, Aug 15, 2024 at 2:38 PM Boky @.***> wrote:

HI Brett,
Thank you for your comment. Unfortunately, (system) users are assigned to
apps when the container is built, not when it's run.
So implementing ENV vars would do nothing more than fail to start the
container if you were to change them.
If you do have any good ideas, I'm open to pull requests.
B
—
Reply to this email directly, view it on GitHub
https://github.com/bokysan/docker-postfix/issues/210#issuecomment-2290580056,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG32OAYDE3NS7YRIVPM2DLZRQWEDAVCNFSM6AAAAABMRKKCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJQGU4DAMBVGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

@bsutton While assigning higher IDs most likely will cause less collision, we still do not eliminate it.
Another issue is changing the IDs now would cause a lot of headache to existing users, as their images would suddenly stop working.
I certainly do not have a good way out of this. Any other ideas?

Perhaps a half way mark.
Change the docker file so the build phase takes the ID's from an env var -
in this way people like me could easily grab the build script and create a
custom image.
Add some doco on how to pass the ID's to the build phase.
No breakage for existing users but a nice solution for everyone else.
On Sun, Sep 15, 2024 at 5:43 PM Boky @.***> wrote:

@bsutton https://github.com/bsutton While assigning higher IDs most
likely will cause less collision, we still do not eliminate it.
Another issue is changing the IDs now would cause a lot of headache to
existing users, as their images would suddenly stop working.
I certainly do not have a good way out of this. Any other ideas?
—
Reply to this email directly, view it on GitHub
https://github.com/bokysan/docker-postfix/issues/210#issuecomment-2351440045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG32OG7FQVRR3T3L7ZVEDTZWU3AVAVCNFSM6AAAAABMRKKCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJRGQ2DAMBUGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

I can live with that. Passing IDs at a build time is done in Dockerfile via ARG instruction and then via --build-arg when running docker build.
What would need to be done here:

Add ARG instruction to Dockerfile
Change the build script to take it into account if set
Ensure that it works on all flavours (Debian / Ubuntu / Alpine)
Ensure that if not set, the defaults persist.
Update documentation to explain how to build this yourself with different IDs.

Frankly, I don't see this as a high-priority feature, but if you would like to take a crack at it, I'd be more than happy to accept a PR.


find out if leg.Messages has any purpose and if, expose it

See src/Client.js:208.
Find out, if the LegList.Leg[…].Message field is being used. If it is, expose it in a concise format.

Right now, they don't seem to be used seriously: :stuck_out_tongue_winking_eye:
{
	value: '',
	id: '187',
	type: 'GLOB',
	act: true,
	pub: '',
	head: 'Test Globalmeldung',
	lead: '',
	text: 'Meldung gilt erst im Februar!<br />Bitte noch nicht anzeigen lieber Server.',  // WAT.
	tckr: '',
	priority: 100
}

The message above is available only on the HAFAS test server. On the production server, real and diverse Messages will be available.
However, we still need to find out in which way all the production Messages differ and parse them.


Single-multiple.md update

Description
Edited single-multiple.md file to improve and clarify content, voice, tense, and grammar.
Issues Resolved
Makes the content more usable.
Check List

[x ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

I've updated the file and checked in the updates... thanks!


Add view dashboard

HEAD: dd390a6d57c6b3d282682c7c2316b530a7440ce1
Feature request
Add a separate dashboard for view in addition to graphs that we have today.
This dashboard will have a lot more view specific graphs including view HH manager metrics.

@vladzcloudius can you please elaborate on which metrics will be useful?

All hints related metrics are useful: type "hint" in the Prometheus console to see their names.
There are two classes of these metrics: for MV and for regular queries. Naturally they need to be clearly separated on dashboard(s).

@vladzcloudius please provide the name of the metrics you think are useful
We do not want to include all metric in the dashboards.

@tzach All metrics with a "view" in their name (there isn't very many) plus coordinator and replica side write/read requests metrics. This would be a good start.


negative to positive transition doesn't turn out well

Hi! I have followed your instructions to the last step: Finaly training with high-quality pairs and then generation.
For the YELP dataset, positive to negative conversion can yield good results, but the negative to positive training is not ideal, with a bleurt score of -0.035 and a style score of only 0.620. (It was observed that in my Step 3 Further Pre-training, the effect from negative to positive was also not ideal)
Do you have a different setup for transitioning from negative to positive during supervised training?

Hi! To maximise the quality of synthetic pairs, we choose sentences that contain one polarity word only, and swap that one with its antonym. But I saw in the log (in the last issue) that you used all synthetic pairs. Maybe you can check with this.

Hi! To maximise the quality of synthetic pairs, we choose sentences that contain one polarity word only, and swap that one with its antonym. But I saw in the log (in the last issue) that you used all synthetic pairs. Maybe you can check with this.

In the final stage of high-quality parallel data screening, I use the style classifier and bleurt index together to select the sentences. In this way, the style of the sentence pair and the text quality will be high. Is it because the existence of multiple style words in the sentence will affect the quality of the training during the transfer from negative to positive direction?
In addition, I am curious that using the same data for training, positive to negative conversion effect is very good. Is this the case for you?

As a final step, we select high-quality pairs using BLEURT and the style classifier. Then, the outputs of one direction and their corresponding source sentences are used to train the model of the opposite direction, so the training data is different for the two directions.


Python 2.7

Hi,
Python 2.7 is no more maintained. You should convert your project in Python 3.
Best,

Yes, will do.

It might be possible to convert the backend machine learning stuff to python 3, then run that bit with rpyc, to allow it to work on 2.10 but with the current versions of libraries and modern python.
It would a) potentially simplify install (you could just bundle the backend server as a py2exe.) b) mean windows support would be possible as torch is python 3 only, and c) mean that example code from recent research could be used without the effort of back porting to 2.7.
I might give this a go to see how hard it would be, as I would like the plugin on Windows.

Scratch that, rpyc is broken between 2.7 and 3 right now, easier solution is to just pipe the image data into a python 3 process, and pipe progress and results back. Is pretty trivial stuff, just reading from stdin in the backend and writing to a subprocess pipe in frontend. This would mean development on the gimp 3 plugin frontend could be completely separate to the plugins themselves, so that work wouldn't break 2.10 compatibility before 3 final comes out.
It would also give the potential for the plugins to be used in other apps too, kind of like ffmpeg is used in many things.

Hello! Thank you for providing these plugins. I'm using Gimp 2.10.18 on Ubuntu 20.04 (installed with apt). I'm eager to try them out however can't get the plugins to work. From gimp --verbose --console-messages
_Querying plug-in: '/home/user/Gimp/GIMP-ML/gimp-plugins/super_resolution.py'
GIMP-Error: Unable to run plug-in "super_resolution.py"
(/home/user/Gimp/GIMP-ML/gimp-plugins/super_resolution.py)
Failed to execute child process “/home/user/Gimp/GIMP-ML/gimp-plugins/super_resolution.py” (Exec format error)_
Is this a clash between python2 and python3 as they are both on my system? Any pointers on how to fix this?
BR

Even with python2.7 I get the same error,
Parsing '/home/prudhvirampey/.config/GIMP/2.10/pluginrc'
Querying plug-in: '/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/super_resolution.py'
GIMP-Error: Unable to run plug-in "super_resolution.py"
(/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/super_resolution.py)

Failed to execute child process “/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/super_resolution.py” (Exec format error)

Querying plug-in: '/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/monodepth.py'
gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): error
Terminating plug-in: '/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/monodepth.py'
Querying plug-in: '/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/invert.py'
gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): error
Terminating plug-in: '/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/invert.py'
Querying plug-in: '/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/faceparse.py'
GIMP-Error: Unable to run plug-in "faceparse.py"
(/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/faceparse.py)

Failed to execute child process “/home/prudhvirampey/Documents/GIMP-ML/gimp-plugins/faceparse.py” (Exec format error)

I think this might not be python version related.

I have described the same problem here.
Might it be a platform-specific bug? Does the plugin make use of any Darwin binaries which naturally won’t work on Linux systems?

We have started development using python 3.
https://github.com/kritiksoman/GIMP-ML/tree/GIMP3-ML


PodDisruptionBudget are not named according to overrides

What happened?
When using datacenterName overrides, the dc name label is set to the overridden one, and the pdb object is created with this name as well.
If two cassdc are created with a dc1 overridden name in the same namespace, they will end up competing for the ownership of the same dc1-pdb PodDisruptionBudget object, and reconcile in a loop.
What did you expect to happen?
The pdb objects should be created with the cassdc meta.name as prefix for their name, which will then avoid creating conflicts as two cassdc objects cannot have the same name in the same namespace.
How can we reproduce it (as minimally and precisely as possible)?
Create a first cassdc using dc1 as datacenterName:
apiVersion: cassandra.datastax.com/v1beta1
kind: CassandraDatacenter
metadata:
  name: cluster1-dc1
  namespace: test
spec:
  clusterName: cluster1
  datacenterName: dc1
  ...

and another one with the same datacenterName value:
apiVersion: cassandra.datastax.com/v1beta1
kind: CassandraDatacenter
metadata:
  name: cluster2-dc1
  namespace: test
spec:
  clusterName: cluster2
  datacenterName: dc1
  ...

They'll both end up creating a dc1-pdb object.
cass-operator version
v1.22.4
Kubernetes version
v1.30
Method of installation
Helm
Anything else we need to know?
No response
┆Issue is synchronized with this Jira Story by Unito
┆Fix Versions: 2024-11
┆Issue Number: CASS-75

Actually, what it is missing is the clusterName prefix which is present in every other object. Otherwise the naming uses the same methods as other resources.

Now, while fixing when creating a new one is easy, this will require us to also delete the old one. Will have to use the new field metadataVersion.


Acorn no longer works in web worker

After working around https://github.com/marijnh/acorn/issues/238 issue by replacing relevant lines with lines from older version of acorn, the next problem I run into while trying to use the new version is this:
file: acorn_loose.js

However, it only occurs when using in a web worker. I have copied the full source of acorn.js, acorn_loose.js, and walk.js and put them inside of the same file in the web worker (in the order specified) and acorn_loose.js thinks its missing acorn.js. I'm clueless as to how this new module loader shim works (it looks like you're using es6 and compiling to es5) , but I think it is causing to the problem.

I just ran a quick test to make sure my code is not the issue.
I cloned Tern, set useWorker=true; in demo.js and fired it up:

I did further testing and I'm even more confused than when I started....
I beautified acorn.js and it fixes the Cannot find module error (not sure why, but I tested undoing and redoing this multiple times, each time with the same result). Only the loader shim needs to be beautified, which results in:
(function(f) {
    if (typeof exports === "object" && typeof module !== "undefined") {
        module.exports = f()
    }
    else if (typeof define === "function" && define.amd) {
        define([], f)
    }
    else {
        var g;
        if (typeof window !== "undefined") {
            g = window
        }
        else if (typeof global !== "undefined") {
            g = global
        }
        else if (typeof self !== "undefined") {
            g = self
        }
        else {
            g = this
        }
        g.acorn = f()
    }
})(function() {
    var define, module, exports;
    return (function e(t, n, r) {
        function s(o, u) {
            if (!n[o]) {
                if (!t[o]) {
                    var a = typeof require == "function" && require;
                    if (!u && a) return a(o, !0);
                    if (i) return i(o, !0);
                    var f = new Error("Cannot find module '" + o + "'");
                    throw f.code = "MODULE_NOT_FOUND", f
                }
                var l = n[o] = {
                    exports: {}
                };
                t[o][0].call(l.exports, function(e) {
                    var n = t[o][1][e];
                    return s(n ? n : e)
                }, l, l.exports, e, t, n, r)
            }
            return n[o].exports
        }
        var i = typeof require == "function" && require;
        for (var o = 0; o < r.length; o++) s(r[o]);
        return s
    })({
        1: [function(require, module, exports) {

Now the strange part... after beautifying the file and using in a web worker I get the https://github.com/marijnh/acorn/issues/238 issue which I thought I had ruled as a Chrome App problem, but I am now confirming it in Chrome (not ChromeApp), FireFox, and IE. I made sure that the modified acorn.js (which I beautified the loader shim) is saved in UTF-8.

It was detecting a browser env (in order for the loose parser to find the main parser module) by looking for window, which workers don't have. I've changed it to simply look for a global called acorn.


MINOR: Close MockitoStatic in try-with-resource

Minor code cleanup to use try-with-resource so that there is no leak in case an exception is thrown before closing mocks.

Failed tests are unrelated.


doc: Update metrics

This renames the instance metrics page, and includes the internal
metrics.
Signed-off-by: Thomas Hipp<EMAIL_ADDRESS>

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.11028/


Endpoint example &

Is there an example of how we should format the endpoint?
http://<IP_ADDRESS>:5000, http://<IP_ADDRESS>:5000\, http://<IP_ADDRESS>:5000\v1,  and http://<IP_ADDRESS>:5000/v1/chat/completions for example.
Also, I am getting this error and I am not sure if it is related to the endpoints.
Traceback (most recent call last):
  File "/home/usr/GOAT-Storytelling-Agent/goat_storytelling_agent/storytelling_agent.py", line 59, in _query_chat_hf
    generated_text = result_prefix + json.loads(
                                     ^^^^^^^^^^^
KeyError: 'generated_text'
Timeout error, retrying...

Using llama.cpp server with http://localhost:8080 as the backend_url still  returns the same error as above and I am getting ```404`` codes.

Extracting the _query_chat_llamacpp function and running
_query_chat_llamacpp('http://localhost:8080', [{"role":"user","content":'hello'}], retries=3, request_timeout=120,
                         max_tokens=4096, extra_options={})

Works
========== Submitting prompt: >>
### USER: hello
### ASSISTANT:<<| Hello! How can I assist you today?
Done reading response.
'Hello! How can I assist you today?'

Oh, I see. You have the default parameter as backend="hf". I recommend just adding that parameter in the first example of the readme.


improved outro notebook

Made sume suggested changes, @benHeid

streamlining bullet point presentation
shortening the double pipeline
sharpening the points of what the graph pipeline adds - not e2e but simplicity (less nested/convoluted)
roadmap sharpened
summary section
up-to-date "join us"

important, @benHeid - the data is not in the repo. The notebook does not run in binder. Please fix that asap!

Thank you for the changes, and sorry for not pinging on the data PR...


Refactor MovieCard Component: Improved Code Readability and Performance

Related Issue

Closes: #478
Description of Changes
Description:
This pull request introduces several code enhancements and refactorings to the MovieCard component, resulting in improved code readability and better performance. The changes made are as follows:

Optimized URL Encoding: In the original code, the shareUrl and shareTvUrl were created using string manipulation to replace spaces with %20. Instead, we have used the encodeURIComponent() function to properly encode the movie title and name for URL usage. This ensures that special characters are handled correctly in the URLs.

Consolidated Similar Code Blocks: The code blocks for rendering the link and title have been consolidated, removing the need for redundant conditionals. We now determine the route based on the props.type and generate the link dynamically.

Simplified Like/Save Handling: The handleSave function has been simplified to handle both saving and removing movies from the user's saved list. We removed the unnecessary conditional for handling different actions based on the like state.

Corrected React Hook Usage: We have added an empty dependency array ([]) to the useEffect hook, ensuring that the effect only runs once when the component mounts. This prevents unnecessary multiple updates in the handleSave function.

Refactored CSS Imports: We changed the import of the CSS module to be specific to the component, using the styles object instead of the global styles module. This helps prevent potential naming conflicts with other components.

Added Missing Key Attribute: The outer div in the MovieCard component has been given a unique key attribute to address React's warning about missing keys in lists.

Removed Unnecessary Async Keyword: The saveShow function did not contain any asynchronous operations, so we removed the unnecessary async keyword.

Updated Dialog Properties: The properties data-modal-hide and onClick were adjusted to use React's data- attribute syntax (data-modal-hide="staticModal") for better compliance with HTML5 standards.
Certainly! Let's go through the changes made in the code for the MovieCard component step-by-step and explain each change.

Optimized URL Encoding:
const shareUrl = encodeURIComponent(props.movie.title);
const shareTvUrl = encodeURIComponent(props.movie.name);

In the original code, the shareUrl and shareTvUrl were created using string manipulation to replace spaces with %20. However, this approach might not handle other special characters properly. Instead, we have used the encodeURIComponent() function to properly encode the movie title and name for URL usage. This ensures that any special characters in the title or name are encoded correctly, making the URLs valid and safe to use.

Consolidated Similar Code Blocks:
{props.type === 'movie' ? (
  <Link to={`/movie/${props.movie.title}/${props.movie.id}`}>
    {/* ... */}
  </Link>
) : (
  <Link to={`/tv/${props.movie.name}/${props.movie.id}`}>
    {/* ... */}
  </Link>
)}

The code blocks for rendering the link and title have been consolidated to avoid redundant conditionals. We now determine the route based on the props.type prop, and we generate the link dynamically using template literals (${}) in the to attribute of the Link component. This makes the code more concise and eliminates the need for duplicated code blocks.

Simplified Like/Save Handling:
const saveShow = () => {
  if (user?.email) {
    setLike(!like);
    setSaved(true);
  } else {
    alert('Please log in to save a movie');
  }
};

The handleSave function has been simplified to handle both saving and removing movies from the user's saved list. We removed the unnecessary conditional for handling different actions based on the like state. Now, when the user clicks the save button, it toggles the like state and sets the saved state to true.

Corrected React Hook Usage:
useEffect(() => {
  handleSave();
}, [like]);

We added an empty dependency array ([]) to the useEffect hook to ensure that the effect only runs once when the component mounts. This prevents unnecessary multiple updates in the handleSave function, which was previously causing extra calls to handleSave on each render.

Refactored CSS Imports:
import styles from '../../style.module.css';

We changed the import of the CSS module to be specific to the component, using the styles object instead of the global styles module. This helps prevent potential naming conflicts with other components and makes it easier to identify the specific CSS module used for this component.

Added Missing Key Attribute:
<div className={`shadow flex my-4 p-3 group`} key={props.movie.id}>
  {/* ... */}
</div>

We added a unique key attribute to the outer div in the MovieCard component to address React's warning about missing keys in lists. Providing a unique key allows React to efficiently update and re-render the component when necessary.

Removed Unnecessary Async Keyword:
const saveShow = () => {
  // ...
};

The saveShow function did not contain any asynchronous operations, so we removed the unnecessary async keyword, making the function more concise.

Updated Dialog Properties:
<button
  type='button'
  className='text-gray-900 bg-transparent hover:bg-gray-200 rounded-lg text-sm p-1.5 ml-auto inline-flex items-center'
  data-modal-hide='staticModal'
  onClick={() => setOpenFilter(false)}
>
  {/* ... */}
</button>

The properties data-modal-hide and onClick were adjusted to use React's data- attribute syntax (data-modal-hide="staticModal") for better compliance with HTML5 standards.

By making these changes, we have improved the overall code quality and maintainability of the MovieCard component, making it more efficient and easier to work with.
Checklist:

[ ] My code adheres to the established style guidelines of this project.
[ ] I have conducted a self-review of my code.
[ ] I have included comments in areas that may be difficult to understand.
[ ] I have made corresponding updates to the project documentation.
[ ] My changes have not introduced any new warnings.

Hey @sourabhsikarwar PLease Review the Pr and then Merge it :) Happy hacking

Hey @sourabhsikarwar PLease Review the Pr and then Merge it :) Happy hacking

Hey, Can you provide the images or video demo of the changes? @Nishitbaria

Hey, Can you provide the images or video demo of the changes? @Nishitbaria

I have Mention Changes in PR  see 🤷♂

@sourabhsikarwar i have resolved conflicts now you can review and merge my pull request

Deployment build getting failed @Nishitbaria

@sourabhsikarwar ,I have made changes please review and merge my pull request


Can't close a notification, have to visit metamask site first.

I 've received a notification that Ethereum wallet not found. Can't close a notification, have to visit metamask site first.
Reproducible on: Chrome browser ver 131.0.6778.140
MacOS
https://github.com/user-attachments/assets/774181d6-39b8-40b3-b4c5-636a69696ec9

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WB240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

Hello,
Use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WT240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WB240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

@Liubov-crypto I am working on delivering a fix. This was originally the intended behavior, but double-displaying seems like a bug.
Also, we don't have any ticketing system or live support. Please be careful about those malicious actors posting phishing links here. Thanks.


Fix crash when at-function-named-arguments encounters trailing commas in function calls

When at-function-named-arguments is enabled, stylelint crashes when the rule attempts to parse function calls that have a trailing comma (has been part of Sass since ± 2016). For example:
.b {
  border: reset(
    $value: 40px,
  );
}

This will cause the following error:
    TypeError: Cannot read property 'key' of undefined

       98 |             case "always": {
    >  99 |               if (arg.key && isScssVarRegExp.test(arg.key)) {
          |                                                    ^
      100 |                 return;
      101 |               }

      at src/rules/at-function-named-arguments/index.js:99:52
      [...]

The error is caused by groupByKeyValue of  parseFunctionArguments, which creates an empty group when seeing the comma. It seems like a simple fix would be to ignore the comma if it is trailing, this seems to work based on the tests I added.

Coverage increased (+0.02%) to 92.287% when pulling 7be866f5dbd8f1e630513230c628277786b4ff3c on thibaudcolas:bug/at-function-named-arguments-trailing-comma into 993f32ee13da4db14906bc06a490607312f3a898 on kristerkari:master.

Thanks! The fix looks good.

the fix is available in version 3.3.1 👍

Thank you 👌 I can confirm it works on my project!


How to create a typings manually (for a package typings doesn't supply) ?

I am trying yo use three-stl-loader package in Angular2 project and i installed it with npm. Also i need its typings but when i typed typings search three there is no typings available for three-stl-loader package. So i think i have to create a typings file for three-stl-loader manually. For every package typings doesn't supply, do i need to create manually a typings file or is there any other way? If there is no way what are the steps of generating typings files?

Yes and no. If you want to get the most out of TypeScript, you do need to create typings for the modules that does not yet have typings available.
You can consider using generator-typings to help scaffold the typings projects you want to create.
You can also use the new syntax in TypeScript 2.0 to tell it to ignore the types of that module. Something like declare module 'xyz'; or declare module 'xyz/*';. Can't remember it correctly as I have not use it myself.
Does anyone know?

Thanks for your comment, i think generator-typings is for yeoman and i don't want to use yeoman. I tried to use your second suggest, it didn't work and i want to share with you the way i used. I used the below link for declare command:
http://definitelytyped.org/guides/best-practices.html
First of all i have a typings folder and it has a global folder which has typings, an index.d.ts file which has reference paths of all typings and the a declaration.d.ts file which i created for the STLLoader typings.
declaration.d.ts includes these lines:
import { STLLoader } from '../node_modules/three/examples/js/loaders/STLLoader.js';

declare module 'STLLoader' {
    var STLLoader: THREE.STLLoader;
    export = STLLoader;
}

and i gave the reference path of declaration.d.ts file to the  index.d.ts:
/// <reference path="globals/angular-protractor/index.d.ts" />
/// <reference path="globals/core-js/index.d.ts" />
/// <reference path="globals/jasmine/index.d.ts" />
/// <reference path="globals/node/index.d.ts" />
/// <reference path="globals/selenium-webdriver/index.d.ts" />
/// <reference path="globals/three-orbitcontrols/index.d.ts" />
/// <reference path="globals/three/index.d.ts" />
/// <reference path="globals/threejs/detector/index.d.ts" />
/// <reference path="declarations.d.ts" />

then i wrote the   private loader: THREE.STLLoader; line in my component that i want to use in. Now it says:
Module 'THREE' has no exported member 'STLLoader'
Property 'STLLoader' does not exist on type 'typeof THREE'

Is there anything wrong with using "declare module"?

Did you ever get this to work?  I'm also using STLLoader within an Angular 2 project, and I would love to see what you came up with.  Thanks!

Yes, we created a typings file manully for stl-loader:
declare namespace THREE {
  export class STLLoader {
    options: any;
    load(
      name: string,
      readyCallback: (result: any) => void): any;
  }
}

and we gave its reference path where we want to use.

@unional
the creating dummy module  syntax is declare module 'rc-time-picker*';

Thanks!


Chattooga County, Georgia

emailed 7:40 am EST
Joy Cooper Hampton, Tax Commissioner
Chattooga County, Georgia
Email<EMAIL_ADDRESS>Office Hours:
Monday through Friday, 8:30 a.m. – 5:00 p.m. CLOSED MOST MAJOR HOLIDAYS.
Phone:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>
Mailing Address:
P.O. Box 517
Summerville, GA 30747-0517
Physical Address:
Courthouse Annex, 120 Cox Street
Summerville, GA 30747
site:https://www.chattoogacountygatax.com/#/contact

Almost too far from Atlanta to be considered an exurb, pretty small place.

sent follow-up email

no data


Retrieving incorrect value for uint or any integer format in smart contract.

Hi,
When I submit/save an integer value as 11, it retrieves 17 in smart contract.
Is it a bug? It started appearing after upgrading eris version to 0.12.0
Regards,
Nikhil

@npc0405 please see the issue template and provide the appropriate information, especially the step to reproduction (including your solidity code and epm.yaml)


Google Analytics UA

See comments in #135 and #228. Both PRs. Both merged. The first, more complete solution to jb-development branch, the second to master.
Reconcile. Resolve. Should be a low-risk, low-effort change.

Fixed in local repo. Pushing this weekend.


Fix face-mask-detection.ipynb error in visualize_images function

Fix no integer division in visualize_images function, which can causes a bad indexing of the matplotlib figure

I have met the same problem, the integer bug should be fixed.

I have met the same problem, the integer bug should be fixed.


i18n: fix german translation for OAUTH_PROVIDER_NAME

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for validating the changes?
[ ] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description
The text "Continue with {{provider}}" currently translates to "Mit {{Anbieter}} fortfahren". The template variable was translated too which obviously is not correct.
Fixed

Rename template var in german translation

Thanks!


Add proxy config

This made two changes.
  - Communication via proxy has been enabled.
  - Temporary directory can be changed.

Thank you for your PR.
Could you change version number to 1.4.0 instead of 1.3.2?
It's semantic version.

MINOR version when you add functionality in a backwards-compatible manner, and
後方互換性があり機能性を追加した場合はマイナーバージョンを

thanks. I fixed.

Merged! Thx!


?TableName is not changed to table name using .DB().Exec()

I'm using the below code:
type Team struct {
	ID uint64
	CreatedAt time.Time `bun:",nullzero,notnull,default:current_timestamp"`
	UpdatedAt time.Time `bun:",nullzero"`
	Name string
}

var _ bun.AfterCreateTableHook = (*Team)(nil)

func (*Team) AfterCreateTable(_ context.Context, query *bun.CreateTableQuery) error {
	_, err := query.DB().Exec(`CREATE TRIGGER custom_trigger BEFORE UPDATE ON ?TableName FOR EACH ROW EXECUTE PROCEDURE custom_trigger()`)
	if err != nil {
		return fmt.Errorf("create trigger: %w", err)
	}

	return nil
}

but the script fails with error:
CREATE                1.209ms  CREATE TRIGGER custom_trigger BEFORE UPDATE ON ?TableName FOR EACH ROW EXECUTE PROCEDURE custom_trigger()
 pgdriver.Error: ERROR: syntax error at or near "?" (SQLSTATE=42601)

?TableName is not changed to teams table name.
Is this a bug?

Is this a bug?

No, your query does not reference Team model in any way. I believe this is not supported at the moment.

Oh, isn't it enough that the hook is tied to that struct to understand that I am referring to it? But perhaps this assertion of mine is wrong.
Anyway something like that would be really useful for speed up writing code instead of manually writing "table_names" each time.


a7rii firmware 4.0 compatible ?

Hello,
Sony has released the Firmware 4.0 on 07.06.17 and is the hack compatible with the new Firmware ?

Yes it works, have loaded it to 3 x A7RII's and it works exactly as before.
Only issue I've found is that .mov files stop once they've hit the 4Gb limit at around 35-36min, never tested this on earlier version.
XAVC s and AVCHD will keep running though.

Ok, thank you for the answer.

@cws127 do you happen to know if this tweak affects the camera in anyway if it goes through a firmware update with the tweak installed?


chore: add CODEOWNERS file

Description

This PR adds a CODEOWNERS file and I suggest that after we merge and change settings to make it required for minimum 1 codeowners to approve any PR but of course we should always try to have 2 👀 on a PR if possible. The reason why these people are on the list:

@arjungarg07 is added of course because the whole project and its setup is done by him.
@magicmatatjahu and me because we know the project well through review/approval process already and can easily be involved in maintenance
bot - because bot is doing lots of work that humans do not want to do, and bot is coolio

Please read what it means to be a committer aka CODEOWNER of the project https://github.com/asyncapi/.github/blob/master/CHARTER.md#3-committers-and-contributors
Please read that as a committer you become also a TSC member but you can also reject and clearly say that your focus is only this specific project -> https://github.com/asyncapi/.github/blob/master/CHARTER.md#2-technical-steering-committee (Committers are the voting members of the TSC and must be listed in the VOTERS file within the Project’s code repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the Project’s GOVERNANCE file). We do not have this set yet, lots of automation is needed in place to setup TSC, but technically you are becoming a member of it

@arjungarg07 @magicmatatjahu you need to approve to get this merged or reject and leave a comment why you do not agree. You do not have to become a codeowner, it is completely fine if you say you are no longer interested in maintaining the project, and also becoming a TSC member

@derberg How to approve this PR, I can't see any option to do it.


在方法configServerPipeline内，建议移除原有pipeline的SimpleChannelInboundHandler的逻辑，移除后并不会影响正常运行，而且triple-demo也能正常运行

What is the purpose of the change
在方法configServerPipeline内，建议移除原有pipeline的SimpleChannelInboundHandler的逻辑，移除后并不会影响正常运行，而且triple-demo也能正常运行。
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8893 (1750ba6) into 3.0 (754404a) will decrease coverage by 0.18%.
The diff coverage is 100.00%.

:exclamation: Current head 1750ba6 differs from pull request most recent head 48a0ce9. Consider uploading reports for the commit 48a0ce9 to get more accurate results

@@             Coverage Diff              @@
##                3.0    #8893      +/-   ##
============================================
- Coverage     63.29%   63.10%   -0.19%
+ Complexity      314      311       -3
============================================
  Files          1178     1178
  Lines         49759    49721      -38
  Branches       7445     7418      -27
============================================
- Hits          31494    31377     -117
- Misses        14827    14892      +65
- Partials       3438     3452      +14

Impacted Files
Coverage Δ

...he/dubbo/rpc/protocol/tri/TripleHttp2Protocol.java
97.14% <100.00%> (-0.16%)
:arrow_down:

...ava/org/apache/dubbo/config/DubboShutdownHook.java
59.25% <0.00%> (-22.23%)
:arrow_down:

...ian2/dubbo/AbstractHessian2FactoryInitializer.java
81.81% <0.00%> (-18.19%)
:arrow_down:

...bo/rpc/cluster/support/FailbackClusterInvoker.java
59.37% <0.00%> (-17.19%)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
75.00% <0.00%> (-12.50%)
:arrow_down:

...ubbo/registry/client/AbstractServiceDiscovery.java
87.50% <0.00%> (-12.50%)
:arrow_down:

...e/dubbo/remoting/transport/netty/NettyChannel.java
51.13% <0.00%> (-9.10%)
:arrow_down:

...moting/transport/netty4/NettyEventLoopFactory.java
22.22% <0.00%> (-7.78%)
:arrow_down:

...va/org/apache/dubbo/registry/RegistryNotifier.java
79.48% <0.00%> (-7.70%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

... and 42 more

Continue to review full report at Codecov.

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


Build fixed

Docker image name fix.

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


Replace Validation class with one that allows for nested validation

Replace Validation class with one that allows for nested validation of deep Pojos.
Using the current Validation class for anything other than flat classes leads to unreadable code.
For example, I wish to parse and validate a Person object, which contains a name String and an Address object. Trying to combine these validations leads to very unreadable code.
The chief problem is that validation of a single field has a single error, and a combined validation has a sequence of errors. These cannot be combined in a fluent way.  By ensuring that every validation returns a sequence of errors, I can combine any validations I want fluently. This allows for complex validation rules with nested validation.
I have deprecated the current Validation class and created a new one in another package. As some of the deprecation warnings for the generated code were appearing despite @SuppressWarnings("deprecation") being switched on (a known issue), I have had to disable deprecation warnings.
The library is still backward compatible, and it's pretty simple to upgrade your deprecated classes and methods with the new ones.
Any feedback is appreciated.

Codecov Report

Merging #2073 into master will decrease coverage by 0.09%.
The diff coverage is 96.21%.

@@             Coverage Diff             @@
##             master    #2073     +/-   ##
===========================================
- Coverage     97.55%   97.45%   -0.1%
- Complexity     5204     5262     +58
===========================================
  Files            92       93      +1
  Lines         11930    12165    +235
  Branches       1572     1598     +26
===========================================
+ Hits          11638    11856    +218
- Misses          144      158     +14
- Partials        148      151      +3

Impacted Files
Coverage Δ
Complexity Δ

vavr/src/main/java/io/vavr/control/Validation.java
99.05% <ø> (ø)
55 <0> (ø)
:arrow_down:

vavr/src/main/java/io/vavr/control/Either.java
100% <100%> (ø)
47 <2> (+2)
:arrow_up:

vavr/src/main/java/io/vavr/Value.java
88.26% <68.75%> (-5.29%)
144 <13> (ø)

...c/main/java/io/vavr/control/fluent/Validation.java
98.19% <98.19%> (ø)
56 <56> (?)

Continue to review full report at Codecov.

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

Hi Amy, many thanks for your PR!
You are fast with providing a solution. We already planned to give Validation some love (see #1565 and #1938).
We are in the lucky case of working on a major release that will contain changes that affect backward compatibility. We wrote about it here. It would be better to re-think the existing Validation rather than deprecating it and adding a new one.
Currently I'm preparing the 0.9.1 patch release (targeted for this weekend). After that I will come back to this PR!
Thx,
Daniel

Great to hear, Daniel! I was worried that backward compatibility would be an issue, so good to see you're biting the bullet. I hadn't even realised that there was an open issue about what I changed.

Hi @danieldietrich , have you had a chance to look at this yet?

Hi @amygithub, I took a look now. The differences to the 'original' Validation class are hard to spot. As I said, we are able to change the original one. Could you please move your particular changes to control.Validation and remove the control.fluent package? Then it is easier for me to see the difference and to review the PR.
Sorry for being so slow in the past - but now there is room to get this right!
Thx!

Hi @danieldietrich. I've moved the classes now, so should be ready for review.

@amygithub Thank you for your contribution and sorry that a took a while. I think you brought validation forward and significantly increased its usability! :)


TOC: Support HTML H* elements

Currently the TOC completely falls over if the markdown document has HTML H* elements, such as
Header 1

Header 2
.
For my particular use case, I have one markdown file that is generated HTML code from API documentation, that we want rendered into the rest of the documentation - it renders fine - but no TOC.

While I understand the desire for this feature, it would be extremely difficult to implement given how the raw HTML is handled. Personally, I have no interest in doing the work. Therefore, I am closing this as something which can be implemented as a third party extension.


Run Prisma's formatSchema before AND after the case formatting to automatically add missing relations

The Prisma formatter does not only format the schema file, but also does maintenance work on it, such as adding missing relations maps to models that specifies relations.
Currently, if there is a missing relation, this packages formats the fields, tables, etc. as per the configuration, and then formats the file using prisma's formatSchema util, which adds the relations that are not necessarily formatted as per this package's configuration, leading the user to need to run this tool again.

Hey @V-ed . Maybe I don't follow -- why can't you solve your problem by running prisma format before prisma-case-format?

Oh don't get me wrong, this is definitely a way to get around this "issue"!
I love this tool and I'd love for it to completely replace the prisma formatter, and it feels weird to run two things when your formatter already runs prisma format (well, the programmatic function anyway) as part of its execution.
I did make this issue right after #57, you could say they are related in a small way!


cmd/compile: crashes in slicing array converted from slice

What version of Go are you using (go version)?

$ go version
go version go1.17beta1 linux/amd64

What did you do?

package main

func SumPointer(b []byte) []byte {
	return (*[32]byte)(b[:32])[:]
}

func main() {
}

What did you expect to see?
Compiles okay.
What did you see instead?
Compiler crashes.
# command-line-arguments
./main.go:4:28: internal compiler error: 'SumPointer': bad type in slice int

Please file a bug report including a short program that triggers the error.
https://golang.org/issue/new

CC @josharian @randall77 @mdempsky

This looks like a serious issue. In 1.16, this would report: cannot convert b[:32] (type []byte) to type *[32]byte.

I'm AFK for a while, but on my phone, looks like the type for the return value in ssagen/ssa.go:3177 is wrong. It is TINT, but should be n.Type(). Anyone else should feel free to send this as a CL, if this diagnosis seems right.

Sorry for the assignment churn. I was trying to assign it to @cuonglm, because he jumped on it with CL 330672 (thanks @cuonglm!). But GitHub won't allow me to for some reason.

Sorry for the assignment churn. I was trying to assign it to @cuonglm, because he jumped on it with CL 330672 (thanks @cuonglm!). But GitHub won't allow me to for some reason.

Yay, I actually have the CL ready one hour ago, but still trying to figure it out why the wrong type is not problem in normal case. Also, sounds like we are not consistent in the type argument passing with OpSlicePtr. But I think n.Type() is best here.

still trying to figure it out why the wrong type is not problem in normal case.

Probably because SSA doesn't do any type checking to make sure types are consistent, and int and *[N]T are interchangeable in most cases.
Also, the feature is new, so we probably don't have any code to exercise that *[N]T is handled correctly by the garbage collector if it needs to get spilled out of the register set for some reason.

@mdempsky Only people in the go-assignees group can be assigned issues: https://github.com/orgs/golang/teams, but Cuong is not part of that group.

@ALTree Thanks. Do you know how we fix that? I clicked around briefly, and either I couldn't figure out how to add members or I don't have authority to.
Cuong has been a Gerrit approver for a while now.

He's a gerrit approver but Github Access and Gerrit Access are two separated things.
He needs to be part of the Golang Github organization first, he's currently not (he's not in https://github.com/orgs/golang/people and his label says "collaborator", not "member").
He should open an issue as described here: https://github.com/golang/go/wiki/GithubAccess asking for Assignees and Editors roles (if he wishes to).

@ALTree Thanks, I filed https://github.com/golang/go/issues/46920


pegasus cache should be identifiable as platform dependent

Generating projects from different platforms in the same shared folder yields to problems due to the baked in paths.
A filecache generated from linux which subsequently runs on the mac will look for /home/
Instead, this should be a platform-specific file cache.
pegasus.macosx.filecache

If we make it platform dependent, then it should also be architecture dependent.


Homogenize collections

I have some collections of GeometryCollection objects and I'd like to simplify them to homogenous geometry types (where possible). For example:

GEOMETRYCOLLECTION (POINT (40 10)) --> POINT (40 10)
GEOMETRYCOLLECTION (POLYGON ((40 40, 20 45, 45 30, 40 40))) --> POLYGON ((40 40, 20 45, 45 30, 40 40))
GEOMETRYCOLLECTION (POINT (10 40),POINT (40 30)) --> MULTIPOINT ((10 40), (40 30))
MULTIPOINT ((10 40)) --> POINT (10 40)
etc

What's the easiest way to do this in Python? In PostGIS, there is a ST_CollectionHomogenize function: https://postgis.net/docs/ST_CollectionHomogenize.html.
Furthermore, it would also be good to be able to do this to the whole collection of geometries, e.g.:

[GEOMETRYCOLLECTION (POINT (40 10)), GEOMETRYCOLLECTION (POINT (10 40),POINT (40 30))] -->[MULTIPOINT ((40 10)), MULTIPOINT ((10 40), (40 30))]

What do you think?

@jamesmyatt I'm sorry, but this issue tracker is for development of the shapely package and not for usage questions. Higher level functionality like this might be useful to the Geopandas project, which is to Shapely what PostGIS is to GEOS (sort of).

@jamesmyatt I'm sorry, but this issue tracker is for development of the shapely package and not for usage questions. Higher level functionality like this might be useful to the Geopandas project, which is to Shapely what PostGIS is to GEOS (sort of).

So, are you saying that I should post this as a feature request to GEOS first, and then I can ask for Shapely to expose that functionality?
For the vector functionality, maybe it's better to raise this in PyGEOS or GeoPandas.

So, are you saying that I should post this as a feature request to GEOS first, and then I can ask for Shapely to expose that functionality?
For the vector functionality, maybe it's better to raise this in PyGEOS or GeoPandas.


Fails if using pnpm

We are using pnpm (https://pnpm.js.org/) with our project. As such, we do not have a package-lock.json file. Even setting install to false fails with the cypress github action (see below).
Pnpm uses a pnpm-lock.yaml file that serves the same purpose, and generally (though not always) has the same syntax as npm. However, the lockfile formats are not compatible.

This action installs local dependencies using lock files. If yarn.lock file is found, the install uses yarn --frozen-lockfile command. Otherwise it expects to find package-lock.json and install using npm ci command.

internal/fs/utils.js:220
    throw err;
    ^

Error: ENOENT: no such file or directory, open 'package-lock.json'
    at Object.openSync (fs.js:440:3)
    at Object.readFileSync (fs.js:342:35)
    at Function.module.exports.309.hasha.fromFileSync (/home/runner/work/_actions/cypress-io/github-action/v1.16.1/dist/index.js:4439:54)
    at Object.104 (/home/runner/work/_actions/cypress-io/github-action/v1.16.1/dist/index.js:2440:24)
    at __webpack_require__ (/home/runner/work/_actions/cypress-io/github-action/v1.16.1/dist/index.js:22:30)
    at startup (/home/runner/work/_actions/cypress-io/github-action/v1.16.1/dist/index.js:37:19)
    at /home/runner/work/_actions/cypress-io/github-action/v1.16.1/dist/index.js:41:18
    at Object.<anonymous> (/home/runner/work/_actions/cypress-io/github-action/v1.16.1/dist/index.js:44:10)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: 'package-lock.json'
}

If relevant, there is a github action for pnpm: https://github.com/marketplace/actions/setup-pnpm
They also have these docs that might be relevant: https://pnpm.js.org/en/continuous-integration

We would be open to PR to fix this. This would be pretty low priority for us to address ourselves since we have very few pnpm users.

I'll see if I can find some time to do that. I imagine it'll be a relatively simple PR.

Sorry for the delay. I've done most of the work for this PR, but I'm getting errors related to the cache dependency. I also see this locally - there's no cache/lib/index.
Is the DEVELOPMENT.md missing a step?

If needed, you can peek at my WIP implementation of PNPM support for Cypress's github action here: https://github.com/FFdhorkin/github-action/tree/feature/pnpm-support
As an additional note, the actions unrelated to pnpm are failing at the same place. However, example-recording / basic fails and yet gets marked as success: https://github.com/FFdhorkin/github-action/runs/1033660717?check_suite_focus=true

@bahmutov any idea why I'm getting that import error?

Could you rebase from the latest code - we have started using the official actions/cache NPM dependency, so this error should be gone.

@FFdhorkin seems close! Would be much appreciated if you could fix this :)

I've rebased off master and opened a draft PR https://github.com/cypress-io/github-action/pull/381

I've also opened a draft PR #381 to solve a similar issue using npm workspaces #377 that allows the lock file path to be specified, but it currently errors with this:
The `npm ci` command can only install with an existing package-lock.json

Just installed pnpm and got blocked by this ;(
I was using yarn before, and it was working, even though the image specifies that the github action is expecting npm's package-lock.json file.

@penx is there a way of using your draft branch for now, changing - uses: cypress-io/github-action@v2 for - uses: penx/github-action@4c488bcaa610e82cc1b45c3b0ac935e415fc6e59 or something like that?

I got stuck on this but running the pnpm install and cypress separately seemed to resolve it. It's possible this isn't the best way but it got things working!
- name: Set up pnpm
  uses<EMAIL_ADDRESS>  with:
    version: 6
    # Only install what we need to run the client in-action and tests against it
    # format:    `--filter <packagename>...`
    run_install: |
      - args: [--filter myclient... --filter cypress-tests...]

- name: Run Cypress tests
  uses: cypress-io/github-action@v2
  with:
    # we have already installed all dependencies above
    install: false
    command: pnpm --dir cypress/ cypress:ci
    start: pnpm --dir myclient/ dev
    wait-on: 'https://localhost:3000'

I also just ran into this. We are using pnpm for faster installs.
Whats odd is /home/runner/work/clients/clients/src/app/package-lock.json seems like the wrong path (notice the double client in that path). It seems like it should be looking for /home/runner/work/clients/src/app/package-lock.json (correct path single clients). But yeah no package-lock.json would exist there either.
internal/fs/utils.js:220
    throw err;
    ^

Error: ENOENT: no such file or directory, open '/home/runner/work/clients/clients/src/app/package-lock.json'
    at Object.openSync (fs.js:440:3)
    at Object.readFileSync (fs.js:342:35)
    at Function.module.exports.hasha.fromFileSync (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:18048:54)
    at lockHash (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:6729:26)
    at getNpmCache (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:6739:16)
    at restoreCachedNpm (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:6784:21)
    at installMaybe (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:7365:5)
    at Object.<anonymous> (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:7388:1)
    at __webpack_require__ (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:24:31)
    at startup (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:43:19) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/home/runner/work/clients/clients/src/app/package-lock.json'
}

Setting install: false to false fixes this for us

A PR has been opened #586


UX Review of graph side-panel

This is a topic that has been mentioned before in various places but did not have a devoted design issue.  This is asking for a review of the graph side panel for consistency, clarity and usability.  The side-panel presents summary information for the selected graph element.  Or, for the entire graph is nothing is explicitly selected.  The side panel is currently fixed to the right, using 100% of the available vertical space, and is collapsible.  Although changes are not required, there is a general feeling that the information could be presented in a cleaner way.
The current goal of the side panel is to provide the user with more information about an element of interest, and to work as a gateway to related detail pages via links.  Some of those links may also be found in the context menu (right-click) of the element.
Current Guides:

Minimal width.  As width increases the graph must shrink.
Collapsible.
Find balance between providing additional information and deferring to detail pages.
Avoid the need to query for non-metric information. (i.e. use what the graph has locally)
Minimize vertical scrolling

There are currently four different summaries: Graph, Node, Edge, App Box.  Each is roughly organized like this:
Header (Info, links)
For each protocol (http, grpc, tcp)
  Traffic Summary Table and bar Chart
For each protocol (http, grpc, tcp)
  Mini-chart

In places we use tabbing to present differing information without adding horizontal
Here is an example of each summary:
Full Graph (default):

Node:

Edge:

App Box:

We will work on this in Sprint 174 (when ends November 6th)

Will be tracked by : https://jira.coreos.com/browse/DTUX-126

Include a title on the side panel.  The first row should include the resource badge followed by the resource name which is a link.  The second row should show a left-aligned status badge, and a right aligned action dropdown menu.

Thanks @serenamarie125 .   We've already replaced some header text with resource badging as part of the work to add Istio config validation notification to the namespaces graph side panel.  I can show you what we have at the next UX meeting, and we can discuss this design and next steps.  I'll add a screen shot here when I get an env running again...

Graph

note new config validation icon next to namespace name
note icon links

Node:

Edge:

Here is a mockup from one of my first Kiali redesigns:

Graph

note new config validation icon next to namespace name

@jshaughn I know the validations visualization is planned to be discussed separately, but just in case I will leave the comment here - it is important to make sure it is clear to user that the icons are referring to validations and not to health, as we have similar icons indicating health in several screens.


ScanStruct implementation

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: #1076
What is the new behavior?

Other information

Codecov Report
Attention: Patch coverage is 48.28897% with 136 lines in your changes are missing coverage. Please review.

Project coverage is 38.02%. Comparing base (d1f6e5b) to head (d654e42).

Files
Patch %
Lines

internal/value/value.go
0.00%
128 Missing :warning:

query/result.go
0.00%
6 Missing :warning:

query/named.go
0.00%
2 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #1091       +/-   ##
===========================================
- Coverage   66.93%   38.02%   -28.92%
===========================================
  Files         283      284        +1
  Lines       27697    27704        +7
===========================================
- Hits        18540    10534     -8006
- Misses       8296    16770     +8474
+ Partials      861      400      -461

Flag
Coverage Δ

?

go-1.21.x
39.21% <48.28%> (-29.56%)
:arrow_down:

go-1.22.x
38.02% <48.28%> (-28.90%)
:arrow_down:

integration
?

macOS
37.93% <48.28%> (+<0.01%)
:arrow_up:

ubuntu
38.01% <48.28%> (+<0.01%)
:arrow_up:

unit
38.02% <48.28%> (-0.02%)
:arrow_down:

windows
?

ydb-22.5
?

ydb-23.1
?

ydb-23.2
?

ydb-23.3
?

ydb-24.1
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Install in browser option not shown when installing extension that prefers ['ui', 'web'] on remote

VS Code Version: stable and from sources

Steps to Reproduce:

Run server ./scripts/code-server.sh --without-connection-token --install-extension=ms-vscode.anycode --install-extension=ollyhayes.colmak-vim --start-server
Open code in browser and got to extensions view
Observe ms-vscode.anycode has option to Install in browser
:bug: Observe ollyhayes.colmak-vim doesn't have option to Install in browser

Created PR #143328 fixing this cc @sandy081

/duplicate
https://github.com/microsoft/vscode/issues/142007

@sandy081 I think you linked the wrong issue, https://github.com/microsoft/vscode/issues/142007 is for showing a installed section in the extensions view.
Could you link the correct issue please :pray:

Sorry for wrong link. Here is the actual issue - https://github.com/microsoft/vscode/issues/141322


number_type_finder

Issue Id you have worked upon -
#49
Briefly explain your program logic -
I have created inputs for number and number type.
Created functions to check the number's compatibility with the selected number types.
And show the results with "Yes" or "No" for the selected types.
Screenshots(Attach 2 screenshots of your own input and output) -
Attach here
screenshot_01
screenshot_02

By raising this PR I affirm that -

[x] My code follows the guidelines of this project.

[x] I have performed a self-review of my own code.

[x] I have commented my code.

[x] My code gives the correct output.

[x] I affirm that I strictly follow contributing guidelines and code of conduct.

Hey @ashishnallana,
Code looks perfect. Kindly add screenshots as simple snips rather than link, then I will merge it.

Hey @SarthakKeshari
As you asked I have added the images as simple snips.

Hey 👋, may you also encourage us by clicking the star icon on the repository main page. ⭐


jdk11-ssl issue

reproduced with:
linux - jdk 11
after 2 mins run of demo App
got hight cpu (200%) + stop recieving messages from websocket
profiler shows native jdk network stack takes cpu
fixed after updating to jdk 13
seems that related to
https://stackoverflow.com/questions/54485755/java-11-httpclient-leads-to-endless-ssl-loop

seems similar to https://github.com/TinkoffCreditSystems/invest-openapi-java-sdk/issues/46

Closing due duplicating #46


Update Content

Fill out the requested content:

What content do you want to update on the site?

The listed current and past syllabi

What is the URL of where you want to update content?

https://academics.cs.luc.edu/syllabi/syllabi.html
https://academics.cs.luc.edu/syllabi/legacy-syllabi.html

Why should content be updated?

The content listed here is out of date and does not reflect the Fall 2021 semester.
If need be, only keep the Spring 2021 syllabi and nothing else on https://academics.cs.luc.edu/syllabi/syllabi.html

Issue has been partially resolved.
This issue needs to be communicated to whoever is responsible for putting together the syllabi so that an updated syllabi can be uploaded to this project.


Merge 1.8.6 to develop

Merge conflicts were a bit rougher than normal, so I did it this way to have tests run

(think something is wrong with this merge, will investigate)


Select range feature

### Summary of the changes
Users can now extract a selected range that spans multiple sibling elements, along with their parent (or not), depending on the case. Unit tests still being set up.
Fixes:

Is it possible to merge the other PR, to make this one easier? Or is that still blocked on something?

FWIW, the build failures can be avoided by building at the command-line with build.cmd before creating your PR or pushing changes.


importing sdk on my React app breaks the bundle

Describe the bug
I import the sdk on my React application and the webpage does not display anymore
To Reproduce

Use CRA Create React Application and import the sdk 0.0.3
Do an import somewhere

import { createMessagePayload } from "@siwt/sdk";

refresh the page

you got Uncaught TypeError: axios_1.default is undefined  on the web page console
Expected behavior
Do not break the react bundle
Screenshots

Desktop (please complete the following information):

OS: WSL2 ubuntu
Browser : all

Additional context
When I do npm run start there is no error, it is when the page refresh to fetch the React bundle
package.json.lock
 "node_modules/@ionic/react": {
      "version": "7.0.0",
      "resolved"<EMAIL_ADDRESS>      "integrity": "sha512-t9NlHZTiH/NvT3GLcO4yS5Whe9stpsZ9AtNOYS+aPcKM5vhxJSFGXDUvKtABOLi2CniW2kFE8krHwjz9V0GQYA==",
      "dependencies": {
        "@ionic/core": "7.0.0",
        "ionicons": "^7.0.0",
        "tslib": "*"
      },
      "peerDependencies": {
        "react": ">=16.8.6",
        "react-dom": ">=16.8.6"
      }
    },
  ...
 "node_modules/react": {
      "version": "18.2.0",
...
"node_modules/@siwt/sdk": {
      "version": "0.0.3",
      "resolved"<EMAIL_ADDRESS>      "integrity": "sha512-cZDzozAJEYbMdvgRqqbULcXw2o10h34EpKn7WsH2MCArgRGIaQ0gOgPBk5JhOL3bYkgKbYi+Od86JhljcseEng==",
      "peerDependencies": {
        "@taquito/utils": "15.1.0",
        "axios": "1.3.3",
        "ramda": "0.28.0",
        "tslib": "2.5.0"
      }
    },
    ...
   "node_modules/axios": {
      "version": "1.3.3",

npm i<EMAIL_ADDRESS>--force seem to fix it
Just axios is not compatible with Typescript anymore after axios v1 ...
I recommend you to set the axios version like mine to allow Typescript to be used


chore: fix typo in IAP example related to oauth2 config

what

Fixed a typo in the IAP section related to oauth2 config.

references

Closes #121

@kvanzuijlen, @kpocius, @cblkwell, @drieske, @mmourick could any of you kindly review this please?


Missing link

Hi, there's a missing "click here" link for the new authentication methods experience at](https://docs.microsoft.com/en-us/azure/active-directory-b2c/multi-factor-[authentication?pivots=b2c-user-flow#delete-totp-authenticator-app-enrollment-using-the-azure-portal).

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

ID: a2df1f73-52bb-3ec8-7371-61b75c77e084
Version Independent ID: fcd3269a-0e70-6019-cc95-540d991822de
Content: Multifactor authentication in Azure Active Directory B2C
Content Source: articles/active-directory-b2c/multi-factor-authentication.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@simonziegler
Thanks for your feedback! We will investigate and update as appropriate.

@simonziegler
Thank you for your post!
Step 7 under the Delete TOTP section isn't linked to anything. The "Click here" mention is referring to the option within the Azure Portal.

If you don't see this interface, select Switch to the new user authentication methods experience! Click here to use it now to switch to the new authentication methods experience.

I've created a PR to hopefully make this more clear, and it's currently waiting for the author to review and sign off.
I will now close out this issue. Please allow some time for the author to review and the changes to reflect.
Thank you for your time and patience!


DBZ-1184 Support long purged GTID set

LGTM; will merge once CI has passed.

There's still a test failure, @jpechane.

@gunnarmorling I know, the problem is that flushing binlog can cause failing of unelated tests and this unfortunately depends on test class order execution we have no way to influence. So I am now investigating two options

somehow force specifing ordernign od the tests
introducing a specific test group that would run after the other tests were executed

This looks like a solution - http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#runOrder


Parent-Child-Relation of Entities: Remove Parent

I created a parent child relation of Entity instances by providing parent child behaviour in Component classed.
When the parent entity is deleted I want to remove all child entities, too.
I'm using a EntityWorldListener to remove all children once the parent has been removed:
FXGL.getGameWorld().addWorldListener(new EntityWorldListener() {
            @Override
            public void onEntityAdded(final Entity entity) {}

            @Override
            public void onEntityRemoved(final Entity entity) {
                if (Objects.equals(entity, parent)) {
                    // FXGL.getGameWorld().removeEntity(child); //TODO FXGL -> Bug
                    FXGL.getGameWorld().removeWorldListener(this);
                }
            }
        });

When I uncomment the comment line in the code snippet I will receive the following exception:
java.lang.IllegalArgumentException: #iterator() cannot be used nested.
	at com.almasb.fxgl.core.collection.Array$ArrayIterator.hasNext(Array.java:719)
	at com.almasb.fxgl.entity.GameWorld.notifyEntityRemoved(GameWorld.kt:573)
	at com.almasb.fxgl.entity.GameWorld.removeEntity(GameWorld.kt:113)

Adding / removing entities during addition / removal of an entity is a design limitation to avoid concurrency issues. I think it's undocumented, so an action from this issue is on me to document this behaviour.
Workarounds depend on the use case, a common one:
Suppose you have a parent child component similar to this:
class ChildComponent extends Component {
     Entity parent;
}

Somewhere in your code parent gets removed from the world:
parent.removeFromWorld() or world.removeEntity(parent);

Before calling above code, how about:
world.getEntitiesByComponent(ChildComponent.class)
         .stream()
         .filter(e -> e.getComponent(ChildComponent.class).parent == parent)
         .forEach(e -> e.removeFromWorld());

// then
parent.removeFromWorld()

Adding / removing entities during addition / removal of an entity is a design limitation to avoid concurrency issues. I think it's undocumented, so an action from this issue is on me to document this behaviour.
Workarounds depend on the use case, a common one:
Suppose you have a parent child component similar to this:
class ChildComponent extends Component {
     Entity parent;
}

Somewhere in your code parent gets removed from the world:
parent.removeFromWorld() or world.removeEntity(parent);

Before calling above code, how about:
world.getEntitiesByComponent(ChildComponent.class)
         .stream()
         .filter(e -> e.getComponent(ChildComponent.class).parent == parent)
         .forEach(e -> e.removeFromWorld());

// then
parent.removeFromWorld()

Sadly this won't work since the 'parent' can be removed based on several actions. A common fix for such use case would be the usage of a CopyOnWriteArrayList instead of using a ArrayList.

Sadly this won't work since the 'parent' can be removed based on several actions. A common fix for such use case would be the usage of a CopyOnWriteArrayList instead of using a ArrayList.

CopyOnWriteArrayList may introduce performance issues, though this would have to be tested.
How about:
class ChildComponent extends Component {
Entity parent;
onUpdate() {
     if (!parent.isActive()) {
          entity.removeFromWorld();
     }
}

}

CopyOnWriteArrayList may introduce performance issues, though this would have to be tested.
How about:
class ChildComponent extends Component {
Entity parent;
onUpdate() {
     if (!parent.isActive()) {
          entity.removeFromWorld();
     }
}

}

That Works :) THX

That Works :) THX


experimental flag to transpile styled-components to next-yak

Maybe we could add an experimental flag in the withYak config to automatically transpile styled-components code to next-yak. This feature would allow users to easily test existing styled-components-based projects with next-yak, potentially identifying performance improvements and compatibility issues.
Benefits:

Easier migration path for existing styled-components projects
Quick performance comparison between styled-components and next-yak
Identify areas where next-yak might need additional features to fully support styled-components syntax

Proposed Implementation:

Add a new experimental flag in withYak config, e.g., library: "styled-components"
When enabled, the loader would detect and transform styled-components imports to the next-yak equivalent

At the moment we don't support 100% of all features that styled-components has. Is the idea to somehow bail out if we find something that we don't support or just generate a warning?

Hi ! That's what I'm looking for. Transforming all these lines is a bit of work, before being convinced of the interest of this lib.
import styled from 'styled-components'
import {styled} from 'next-yak'

The other task I see for my codebase is to transform the css={text-transform: uppercase} to css={csstext-transform: uppercase}, which contrary to styled-components's version, needs an import of {css}

I guess there are tools that help build scripts that transform js/ts files to handle these migrations, but I don't know this field.

The migration is quite heavier than I thought. Multiple days of work for my map application. https://github.com/cartesapp/cartes/pull/704
I'm converting components one by one in dev mode.
Running the build fails with an error that is not easy to understand.
$ next build
   ▲ Next.js 15.0.3
   - Environments: .env.local, .env
   - Experiments (use with caution):
     · turbo
     · swcPlugins
     · reactCompiler

   Creating an optimized production build ...
Generated 11 documents in .contentlayer
Failed to compile.

HookWebpackError: /home/laem/cartes/static/css/aaefa09d05cdbf9f.css:21:3: Unclosed block
    at makeWebpackError (/home/laem/cartes/node_modules/next/dist/compiled/webpack/bundle5.js:28:314597)
    at /home/laem/cartes/node_modules/next/dist/compiled/webpack/bundle5.js:28:106393
    at eval (eval at create (/home/laem/cartes/node_modules/next/dist/compiled/webpack/bundle5.js:13:9218), <anonymous>:44:1)
-- inner error --
CssSyntaxError: /home/laem/cartes/static/css/aaefa09d05cdbf9f.css:21:3: Unclosed block
    at Input.error (/home/laem/cartes/node_modules/postcss/lib/input.js:106:16)
    at ScssParser.unclosedBlock (/home/laem/cartes/node_modules/postcss/lib/parser.js:574:22)
    at ScssParser.endFile (/home/laem/cartes/node_modules/postcss/lib/parser.js:336:35)
    at ScssParser.parse (/home/laem/cartes/node_modules/postcss/lib/parser.js:475:10)
    at scssParse (/home/laem/cartes/node_modules/next/dist/compiled/postcss-scss/scss-syntax.js:1:322)
    at new LazyResult (/home/laem/cartes/node_modules/postcss/lib/lazy-result.js:133:16)
    at Processor.process (/home/laem/cartes/node_modules/postcss/lib/processor.js:53:14)
    at CssMinimizerPlugin.optimizeAsset (/home/laem/cartes/node_modules/next/src/build/webpack/plugins/css-minimizer-plugin.ts:48:8)
    at /home/laem/cartes/node_modules/next/src/build/webpack/plugins/css-minimizer-plugin.ts:97:47
    at Span.traceAsyncFn (/home/laem/cartes/node_modules/next/src/trace/trace.ts:143:14)
caused by plugins in Compilation.hooks.processAssets
CssSyntaxError: /home/laem/cartes/static/css/aaefa09d05cdbf9f.css:21:3: Unclosed block
    at Input.error (/home/laem/cartes/node_modules/postcss/lib/input.js:106:16)
    at ScssParser.unclosedBlock (/home/laem/cartes/node_modules/postcss/lib/parser.js:574:22)
    at ScssParser.endFile (/home/laem/cartes/node_modules/postcss/lib/parser.js:336:35)
    at ScssParser.parse (/home/laem/cartes/node_modules/postcss/lib/parser.js:475:10)
    at scssParse (/home/laem/cartes/node_modules/next/dist/compiled/postcss-scss/scss-syntax.js:1:322)
    at new LazyResult (/home/laem/cartes/node_modules/postcss/lib/lazy-result.js:133:16)
    at Processor.process (/home/laem/cartes/node_modules/postcss/lib/processor.js:53:14)
    at CssMinimizerPlugin.optimizeAsset (/home/laem/cartes/node_modules/next/src/build/webpack/plugins/css-minimizer-plugin.ts:48:8)
    at /home/laem/cartes/node_modules/next/src/build/webpack/plugins/css-minimizer-plugin.ts:97:47
    at Span.traceAsyncFn (/home/laem/cartes/node_modules/next/src/trace/trace.ts:143:14)

> Build failed because of webpack errors
error: script "build" exited with code 1

I have never seen this error but i'll take a look - thanks for sharing

could you please share which file is causing this?
we noticed doing migration that styled component silently ignored errors but now that postcss processes them they break the build

could you please share which file is causing this?
we noticed doing migration that styled component silently ignored errors but now that postcss processes them they break the build

Cloning cartesapp/cartes, switching to the "yak" branch and doing bun install && bun run build should trigger the error.
The static/css/xxx files are not present anymore after the error is triggered, making it hard to find where it comes from in a large code base.

@laem thank you so much - this is (probably) a bug in our parsing logic 🤯
in app/boussole/UI.tsx you are using background: url(...) but our parser can only handle urls inside quotes e.g. background: url("...")

Thanks ! That was quite a peripheral unused page. How did you find out which one of the files was causing the build fail ?

I modified the node_modules module which showed the "Unclosed Block" error message to get the full css code which caused the problem
btw we have a fix in #227

cartes.app has switched fully to next-yak yesterday :)
Was quite a large set of changes. I've tried Aider to assist me, with Mistral, it's impressive but too difficult to know if the set of changes doesn't include an error. So, manually.
Prod works great. I have the impression that the app is faster in use. But it's very difficult to say. At least, the rehydratation errors have disappeared :)

Really nice to hear. Thank you for pushing through the migration. We're currently also busy to migrate a part of a huge application to get some real world performance comparisons between styled-components and next-yak.


Add documentation for Bitcoin to ISK endpoint

Describe this code change as best you can here. Is it a new endpoint, bugfix or
changes to the documentation?
Checklist

[x] Write tests
[x] Write documentation

This LGTM. @MiniGod can you take a look and merge it it looks good to you?


Support for filetypes with underscores?!

I used to use this piece code for verilog.
" verilog
let g:neomake_verilog_enabled_makers = ['iverilog']
let g:neomake_verilog_iverilog_maker = {
    \ 'args': ['-v', '-Wall'],
    \ }

Recently, I install a plugin, vhda/verilog_systemverilog.vim.
It change the filetype to "verilog_systemverilog".
And neomake doesn't work because different filetype name.
but I don't know how to write for this one.
I tried this,
let g:neomake_verilog_systemverilog_enabled_makers = ['iverilog']
let g:neomake_verilog_systemverilog_iverilog_maker = {
    \ 'args': ['-v', '-Wall'],
    \ }

but it doesn't work.
Whether can neomake handle when filetype contain underline?
If it can, how to write it correctly?
(Or filetype shouldn't contain underline at all...)

I think it is not supported currently, sorry.
Typically you would use a dot to combine filetypes, but there are also issues regarding this.
In this case I wonder why the plugin is not called / does not use systemverilog, since it does not get any benefit from using verilog_ (instead of verilog).
But we should look into how this could be supported after all.

Not sure after which update, but now it works fine.
:)

Makes me curious, and should get covered by some test.
Are you using still the same setup as outlined above?

sry, didn't notice that.
Yes, I still use the same config, and it works fine.


change the feature extraction setting of vctk config

Hi, first of all, thank you so much for providing pre-trained models through many experiments. But what I want to ask is, I want to fine-tune the pre-trained VCTK model with my multi-speaker dataset. In the VCTK config file, fft_size = 2048, hop_length = 300, win_length = 1024, but the config of the TTS model I trained is 1024, 256, 1024. When fine-tuning, will it work if I change the config file to 1024, 256, 1024 to match my TTS model? The sampling rate is 24000. Thank you!

Sorry for the late reply.
I think you should train from scratch for the following reasons:

The difference of fft size or window size might be OK if you finetune the model
The difference of hop length is critical since the hop length determines the upsampling layer structure.
If you want to change hop length, you need to change the upsample layers as well.

Example:
hop length = 300 ->  5 * 5 * 4 * 3
https://github.com/kan-bayashi/ParallelWaveGAN/blob/86740373ec609cb9fb192d472d2aea125041491a/egs/vctk/voc1/conf/hifigan.v1.yaml#L40

thank you so much for answering me
i will try your recommend. thank you!


Can't install node-sass on heroku

Before opening an issue:

Read the common workarounds in the TROUBLESHOOTING.md
Search for duplicate or closed issues
Validate that it runs with both Ruby Sass and LibSass
Prepare a reduced test case for any bugs
Read the contributing guidelines

When reporting an bug, you must provide this information:
It's on heroku. The information of versioning are listed below:
Heroku stack
Auto Cert Mgmt: false
Dynos:          web: 1
Region:         us
Repo Size:      22 MB
Slug Size:      70 MB
Stack:          heroku-16
Heroku push log
Counting objects: 20, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (20/20), done.
Writing objects: 100% (20/20), 11.33 KiB | 0 bytes/s, done.
Total 20 (delta 16), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Node.js app detected
remote:
remote: -----> Creating runtime environment
remote:
remote:        NPM_CONFIG_LOGLEVEL=error
remote:        NPM_CONFIG_PRODUCTION=true
remote:        NODE_VERBOSE=false
remote:        NODE_ENV=production
remote:        NODE_MODULES_CACHE=false
remote:
remote: -----> Installing binaries
remote:        engines.node (package.json):  ~6.11.x
remote:        engines.npm (package.json):   unspecified (use default)
remote:        engines.yarn (package.json):  unspecified (use default)
remote:
remote:        Resolving node version ~6.11.x...
remote:        Downloading and installing node 6.11.3...
remote:        Using default npm version: 3.10.10
remote:        Resolving yarn version (latest)...
remote:        Downloading and installing yarn (1.0.0)...
remote:        Installed yarn 1.0.0
remote:
remote: -----> Restoring cache
remote:        Skipping cache restore (disabled)
remote:
remote: -----> Building dependencies
remote:        Installing node modules (yarn.lock)
remote:        yarn install v1.0.0
remote:        [1/4] Resolving packages...
remote:        [2/4] Fetching packages...
remote:        info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
remote:        info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
remote:        [3/4] Linking dependencies...
remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency "babel-core@6 || 7 || ^7.0.0-alpha || ^7.0.0-beta || ^7.0.0-rc".
remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency "webpack@2".
remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency "webpack@1 || ^2.1.0-beta || ^2.2.0-rc.0".
remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| >= 3.0.0-rc.0 || ^3.0.0".
remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency "webpack@^1 || ^2 || ^2.1.0-beta || ^2.2.0-beta".
remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency "glamor@>=2".
remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency "file-loader@*".
remote:        warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>remote:        [4/4] Building fresh packages...
remote:        error An unexpected error occurred: "/tmp/build_3ca45f1523c41f3b3d69f74657245a36/node_modules/node-sass: EROFS: read-only file system, access '/usr/local/bin'".
remote:        info If you think this is a bug, please open a bug report with the information provided in "/tmp/build_3ca45f1523c41f3b3d69f74657245a36/yarn-error.log".
remote:        info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
remote:
remote: -----> Build failed
remote:
remote:        We're sorry this build is failing! You can troubleshoot common issues here:
remote:        https://devcenter.heroku.com/articles/troubleshooting-node-deploys
remote:
remote:        Some possible problems:
remote:
remote:        - This project was built with yarn, which is new and under development. Some projects can still be built more reliably with npm
remote:        https://devcenter.heroku.com/articles/nodejs-support#build-behavior
remote:
remote:        Love,
remote:        Heroku
remote:
remote:  !     Push rejected, failed to compile Node.js app.
remote:
remote:  !     Push failed
remote: Verifying deploy....
remote:
remote: !       Push rejected .
remote:
To
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to ''

NPM version (npm -v):
Node version (node -v):
Node Process (node -p process.versions):
Node Platform (node -p process.platform):
Node architecture (node -p process.arch):
node-sass version (node -p "require('node-sass').info"):

Was trying to install
<EMAIL_ADDRESS>
npm node-sass versions (npm ls node-sass):

When encountering a syntax, or compilation issue:

Open an issue on LibSass. You
may link it back here, but any change will be required there, not here

If you delete this text without following it, your issue will be closed.

Same error here.

Would like this to be resolved asap as this never happened before, one of my applications somehow is blocked because of this issue. And unfortunately node-sass is a requirement atm, one of the dependencies of the software we developed.

Nothing has changed with node-sass. This sounds like an heroku issue. I
suggest you start your debugging by googling the error in the logs
EROFS: read-only file system, access
On 7 Sep. 2017 12:54 pm, "Penn Su"<EMAIL_ADDRESS>wrote:

Would like this to be resolved asap as this never happened before, one of
my applications somehow is blocked because of this issue. And unfortunately
node-sass is a requirement atm, one of the dependencies of the software we
developed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2089#issuecomment-327668939,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWDUT02RQ9OnbcsltX9L1QJvVPi-0ks5sf1rPgaJpZM4PN5NV
.

Same error here.

@pencilcheck @xzyfer @King-Ran this is actually yarn issue. Don't have link to the issue right now but
forcing older yarn engine in packages.json resolved my issue
 "engines": {    "yarn": "0.28.4"   }

@marekstabla
npm install -g cnpm --registry=https://registry.npm.taobao.org
cnpm install --save-dev node-sass
resolved my issue

I had been having this issue for the last couple of days too, but I just managed to do a successful deployment with no changes on my end. Can anyone confirm that this issue has been resolved?

@ordinathorreur I still have this issue (node >= 7.*)

Same issue. (node >= 7.*)

Still happening

Closing since this seems related to Heroku file system permissions rather than something related/fixable in node-sass


Minor improvements

This PR changes a few things to use the latest conventions and best practises on the web and adds another project that uses handlebars (muffin).

Instead of ignoring files with .npmignore, only the required ones will now be included using the "files" property within package.json
The license was converted into markdown, to make it easier readable
"release-notes.md" was renamed to "RELEASE-NOTES.md" to match those other info files
The project description of "Cory" has been adjusted

I'd also like to volunteer for being a collaborator on this repo! :blush: (Since it looks like there's someone needed who manages PRs and issues.)

This project is dead ¯_(ツ)_/¯


Ctppsdb4 rp pos

declarations of RP positions class for CTPPS database

@clemencia Many thanks Clemencia! Would you have a test config that could be used to validate the functionality?

Hi Jan,
There is no test config in this example, as the usage  (DB filling) is done in the next pull request (In the past when I've developed new classes for the conditions they ask us to decouple the declaration from the usage). This declaration should be tested that it doesn't  break other functionalities of the conditions system. What is present here is a serialization test in the CondFormats/CTPPSObjects package.

@clemencia Ok, thanks! Thus let's postpone testing to the next PR.


Add hover effects to the navItems

We need something like this: https://www.meisternote.com/?ref=landingfolio

Do you want me to do it ? :)

Sure. Thanks for your interest @JulienMaurice. Go for it! 🚀


leochan.ex linkedin

Template update due to out dated API doc

these are rather strong changes, should it at least write to different tables? it looks like it will cause a lot of pain on existing configurations

I have switched all the updated templates from campaign_statistics to campaign_analytics which in fact is reflecting more accurately what we are extracting from the API. There is actually another endpoint in LinkedIn called AdStatistics, essentially extracting the same info but more parameters option.. will this be sufficed ?

Much better, I'm thinking - how long will the old API points work? i.e. - if it's months it might be worth just adding new templates and remove the old ones only when they cease to work anyway

The old templates are no longer working =/
TBH, I have no idea when they change the parameters and it has been a while since we have customers using this component. Now we have a customer requires it and I have tested the updated templates!

ic, in that case, lets get on with this :)

the changes are listed here https://docs.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes
i think that if you subsrcibe to linked developers, you'll get notifications


Javadoc fails to generate resourcedoc.xml for Jersey 1.19

I'm using following configuration of Javadoc to generate resourcedoc.xml for Jersey 1.19 (the pattern taken from https://docs.gradle.org/current/dsl/org.gradle.api.tasks.javadoc.Javadoc.html).
The task fails with "javadoc: error - invalid flag: -d":
-d flag value is generated from destinationDir property, which can't be omitted.
Is there a way to workaround this?
Java version: 1.8.0_144
def jerseyVersion = "1.19"
configurations {
    wadlDoclet
}
dependencies {
    wadlDoclet "com.sun.jersey.contribs:wadl-resourcedoc-doclet:${jerseyVersion}"
}
task generateWadl(type: Javadoc) {
    source = sourceSets.main.allJava
    destinationDir = file('./')
    options.docletpath = configurations.wadlDoclet.files.asType(List)
    options.doclet = "com.sun.jersey.wadl.resourcedoc.ResourceDoclet"
    options.addStringOption("output", "resourcedoc.xml")
}
war {
    dependsOn generateWadl
}

Please see here: https://bugs.openjdk.java.net/browse/JDK-4935349
This is not a Gradle issue.

Disagree: the problem is not in javadoc, but in a javadoc gradle plugin, which supplies incorrect set of parameters to javadoc.

You're right. Sorry.

A workaround is to use ant.javadoc plugin - destdir is not required, if custom doclet is used.
See https://ant.apache.org/manual/Tasks/javadoc.html


Weird edge at top of bump wave travelling 45°

I made a bump wave using Add from texture shader with this texture:

I attached that bump to a moving GameObject travelling 45 degrees across the ocean plane but the ocean mesh vertices are so regular that you can notice the gap on diagonal creating "dent" shape at top of wave as in this picture:

It is quite visible in in wireframe:

Just copy-paste my red bump texture above to use as add bump texture then rotate the gameobject 45° and move it along teh forward axis, you should be able to see in some positions the dent edge appearing.
Note: Tested on Windows 10 x64 under Unity 2019.4.0f1 URP in Editor but that also happens with other versions too (first noticed since 2019).

The shape in that texture is too 'sharp' for the mesh at that resolution. Smoothing it out a bit would help. Or increasing lod data resolution on the ocean component would add more verts/resolution which would help, but add cost.
Our surface mesh uses an edge layout which minimises this kind of artifacts, but they can still happen if there is a lot of curvature in the shape like the above example..


Rename icatypes.PortPrefix to icatypes.ControllerPortPrefix

Summary
I think it'd be useful to make the naming a bit more explicit. I often need to double check what the actual value is here. "Prefix" does imply it is the controller since the host doesn't really have a prefix, but I think it'd still be useful to update the naming to "ControllerPortPrefix"
Rename icatypes.PortPrefix to icatypes.ControllerPortPrefix

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Should we also rename PortID to HostPortID?

Yea that sounds good to me

Is the issue open? Would like to work on it

Is the issue open? Would like to work on it

It is! Thanks so much to being so active on the repo!

My pleasure 😄


Chore: Upgrade to the latest version of stellar-wallet-kit

What problem does your feature solve?
Stellar wallet kit has a first stable release 1.2.0: https://github.com/Creit-Tech/Stellar-Wallets-Kit/releases

Closing this ticket, as dependabot has opened a PR to update dependencies https://github.com/stellar/laboratory/pull/994