Show job chain on Dashboard

I think it would be great if we could be able to see the chain ot the jobs we win on the My Nodes Dashboard
Something like this:

Great idea! Thank you :)
I'm gonna see if I can plan out my next update for othub and will try get this in with it


Fix parameter passing in deprecated client

Parameters are not nullable on API side

@volkerstampa I think this will be a breaking change unless we have a default on the API, no?


plugin(authz-keycloak): Chinese doc

Now we only have English doc and need to translate Chinese doc.
https://github.com/apache/incubator-apisix/pull/1701/files#diff-142655bb13c688162035732e434efc7e

I think I could help with this. PR on the way.


Add docker-compose file, update README

I'm adding a docker-compose file that can be used to run all three of the go services, with request routing handled by linkerd and namerd.  I've update the README with usage instructions.

⭐ 👍
$ curl -s $DOCKER_IP:4140/gob?limit=1
bees


refactor remove gulp-util dependency

Hi,
Since gulp-util has been deprecated, this PR replaces gulp-util with alternative individual modules. https://github.com/gulpjs/gulp-util

Thanks


Request Adding vtk 9.3.1

Is your feature request related to a problem? Please describe.
I'm trying to use vtkHDFWriter to output adaptive mesh data in my code. HDF5 is a good way to visualize adaptive mesh data for its capability of large and complex data structures.
Describe the solution you'd like
Support latest vtk version 9.3.1 in https://github.com/xmake-io/xmake-repo/blob/dev/packages/v/vtk/xmake.lua
Describe alternatives you've considered
No response
Additional context
No response

you can open a pr to update it.

Done https://github.com/xmake-io/xmake-repo/pull/5041


Adds newline to the end of files and fixes a typo in the readme

also stop using MongoDB

I regret making this public.


Update asp-all-route-data

When using asp-all-route-data, if it is specified after other  asp-route-myvar attributes they will not be used to generate the route.
@{
    var queryString = new Dictionary<string, string>()
    {
        {"returnUrl", @Context.Request.GetEncodedUrl()}
    };
}

The following works:
asp-all-route-data="@queryString" asp-action="Edit"<EMAIL_ADDRESS>The following does NOT work:
asp-action="Edit"<EMAIL_ADDRESS>asp-all-route-data="@queryString"

Needs edit after approval.

I'm not convinced this is a mainline enough scenario to warrant adding it to the docs.

@NTaylorMullen  thanks. It's very discoverable  on this page from the issue. We  work on the title.


removed quote section@Home

⚠⚠⚠⚠⚠⚠⚠
Do not merge this PR now
this PR depends on changes added in another PR #782
I will update this PR when #782 gets merged
closes #778

- I have participated in GSSOC and CrossWoC

Update the PR with a squash commit please @ashuvssut  😅

Remove this too please!

@smaranjitghose  done


Provide a programmatic way to close the modal window

My modal does submit some action and I want it to close itself after the action's Promise is resolved. There are 2 ways to open a modal: by directly passing the open prop or by trigger element. Inside you can use the Modal.Close component to close the modal in its native way. But there is no other way. Also, there is no forwardRef on Modal.Close, so I can't trigger a click event on the element. So I ended up with the following code:
const MyCustomModal: FC<Props> = ({ onSubmit, onOpenChange, ...props }) => {
    const [ isLoading, setIsLoading ] = useState<boolean>(false);

    const onClick = useCallback(async () => {
        setIsLoading(true);
        try {
            await onSubmit?.();
        } finally {
            setIsLoading(false);
        }

        // There is no way to close a modal natively, honoring all events, from within, other than using Modal.Close.
        // I wanted to use a programmatic click on the ref of the element, but unfortunately this solution isn't
        // possible because the component doesn't have a forwardRef.
        //
        // So the current implementation just fires the native event and relies on the fact that the modal window
        // being displayed via `open`/`onOpenChange` rather than a `trigger`.
        onOpenChange?.(false);
    }, [onOpenChange]);

    return (
        <Modal onOpenChange={onOpenChange} {...props}>
            <ButtonCell mode="destructive" disabled={isLoading} onClick={onClick}>
                Delete
            </ButtonCell>
        </Modal>
    );
};

So it would be nice to provide some imperative property on the Modal component, that will let the developer close the modal in its native way regardless of the way it was opened.

Hey, there is example in the docs how to do it, please refer to it. It works as expected
https://tgui.xelene.me/?path=/docs/overlays-modal--documentation#controlled
export const Controlled: Story = {
  args: {
    ...Playground.args,
  },
  render: (args) => {
    const [isOpen, setIsOpen] = useState(args.open);
    const [isFetching, setIsFetching] = useState(false);

    const fetchAndClose = () => {
      setIsFetching(true);
      setTimeout(() => {
        setIsFetching(false);
        setIsOpen(false);
      }, 1000);
    };

    return (
      <Placeholder
        header="This modal will be closed after 1000ms, click fetch"
        description="Click fetch"
        action={<Button size="m" onClick={() => setIsOpen(true)}>Open again</Button>}
      >
        <Modal
          {...args}
          trigger={undefined}
          open={isOpen}
          onOpenChange={setIsOpen}
        >
          <Placeholder action={(
            <Button
              size="m"
              loading={isFetching}
              onClick={fetchAndClose}
            >
              Fetch data and close
            </Button>
          )} />
        </Modal>
      </Placeholder>
    );
  },
  decorators: [DecoratorFullScreen],
};

This example shows how to close the modal by the parent component, while I'm asking how to close it by itself. You might say that this is not "react-way", but why is there a Modal.Close component that directly allows closing the modal from within?

If you want to close the modal in any custom way, you need to use the open prop and manage the state as you want. States can be updated from any child component/you can use the store. Otherwise, I don't understand your use case


Incorrect minRunLength() computing minRun to be too small

The following line seems incorrect.
Since MIN_MERGE is 32, the loop would end with n containing the 5 most significant bits instead of 6 most significant bits.
Therefore, the function would return [0, 32], which is less than what Python is doing here
The Python detailed description of Timsort in the readme here also corresponds to returning a size of [32, 64] when possible.

Indeed, CPython seems to have MIN_MERGE = 64 and it's not a late addition or fix since it was already the case when this project was started in 2011. If there is a reason for the difference I don't know what it is: the value in this C++ project has been 32 since the initial commit so there isn't any specific commit explaining it. Only @gfx might know why.
I'm going to change it and run all the tests I have to check whether everything still works. If there isn't any obvious issue I will change it to 64. Thanks for the catch.

Oh, I don't remember the why. Please fix it.

Indeed, CPython seems to have MIN_MERGE = 64 ...
MIN_MERGE seems to mean "the minimum size at which I will start doing merging". Also, it is also used here.

So, I wouldn't change MIN_MERGE to 64. On the contrary, I would change this line to while (n >= 2*MIN_MERGE) {.
This would ensure that the name MIN_MERGE is accurate, and we do merging at sizes of range [32, 64] when there are enough elements left to "top-up" our runs to said sizes. What do you think?
Btw, thanks for maintaining this repo (and many others).

You're right once again, I applied your proposed resolution, thanks :)
Thank you Goro too for the heads up!


Repo manager leaves files on fail

When attempting to add the apparently corrupted file HG00101.mapped.ILLUMINA.bwa.GBR.low_coverage.20130415.bam I found the repo manager left behind the linked file, even though the process apparently failed.
(server-1)➜  server-1 git:(master) ✗ python repo_dev.py add-readgroupset ga4gh-example-data 1kg-p3-subset ../1000genomes/HG00101.mapped.ILLUMINA.bwa.GBR.low_coverage.20130415.bam
[W::bam_hdr_read] EOF marker is absent. The input is probably truncated.
Traceback (most recent call last):
  File "repo_dev.py", line 7, in <module>
    ga4gh.cli.repo_main()
  File "/Users/david/server-1/ga4gh/cli.py", line 1672, in repo_main
    runner.run()
  File "/Users/david/server-1/ga4gh/cli.py", line 1468, in run
    self.datasetName, self.filePath, self.moveMode)
  File "/Users/david/server-1/ga4gh/repo_manager.py", line 427, in addReadGroupSet
    pysam.index(destPath.encode('utf-8'))
  File "/Users/david/server-1/server-1/lib/python2.7/site-packages/pysam/utils.py", line 65, in __call__
    "\n".join(stderr)))
pysam.utils.SamtoolsError: 'samtools returned with error 1: stdout=, stderr=samtools index: "ga4gh-example-data/datasets/1kg-p3-subset/reads/HG00101.mapped.ILLUMINA.bwa.GBR.low_coverage.20130415.bam" is corrupted or unsorted\n'

(server-1)➜  server-1 git:(master) ✗ ls ga4gh-example-data/datasets/1kg-p3-subset/reads/HG00101.mapped.ILLUMINA.bwa.GBR.low_coverage.20130415.bam
ga4gh-example-data/datasets/1kg-p3-subset/reads/HG00101.mapped.ILLUMINA.bwa.GBR.low_coverage.20130415.bam

So in the case (like here) where we are doing a processing step that may fail, what do you propose the recovery process should be?  I think:

delete all index files that pysam may leave lying around, in any case
1a) if the moveMode is link, delete the link
1b) if the moveMode is copy, delete the file
1c) if the moveMode is move, move the file back to where it came from

Sound good?

I believe if you were to perform the move after all other processing you would simplify the approach. If the index step's exceptions are handled properly you shouldn't have to do anything else.

Perhaps, but I want to avoid modifying files in areas that we don't control (e.g. outside a repo) and aren't explicitly asked to do

How about #1064? We should limit the features of the repo manager as much as possible and add features if their requested.

I'm with @david4096 here. Let's pull back on the auto-generating index feature of repo manager for a while, and flesh out the features we need for the upcoming milestones. (We'll figure out exactly what those features are over the next few days.)

Closed by #1166.


done

Implemented #193

Codecov Report

Merging #194 (f5f7c26) into develop (435a772) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #194      +/-   ##
===========================================
+ Coverage    97.53%   97.56%   +0.02%
===========================================
  Files           63       66       +3
  Lines         2639     2669      +30
===========================================
+ Hits          2574     2604      +30
  Misses          65       65

Impacted Files
Coverage Δ

glasses/models/segmentation/fpn/__init__.py
91.66% <ø> (-0.09%)
:arrow_down:

glasses/nn/__init__.py
100.00% <100.00%> (ø)

glasses/nn/pool/SpatialPyramidPool.py
100.00% <100.00%> (ø)

glasses/nn/pool/__init__.py
100.00% <100.00%> (ø)

test/test_pool.py
100.00% <100.00%> (ø)

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 435a772...f5f7c26. Read the comment docs.

Codecov Report

Merging #194 (f5f7c26) into develop (435a772) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #194      +/-   ##
===========================================
+ Coverage    97.53%   97.56%   +0.02%
===========================================
  Files           63       66       +3
  Lines         2639     2669      +30
===========================================
+ Hits          2574     2604      +30
  Misses          65       65

Impacted Files
Coverage Δ

glasses/models/segmentation/fpn/__init__.py
91.66% <ø> (-0.09%)
:arrow_down:

glasses/nn/__init__.py
100.00% <100.00%> (ø)

glasses/nn/pool/SpatialPyramidPool.py
100.00% <100.00%> (ø)

glasses/nn/pool/__init__.py
100.00% <100.00%> (ø)

test/test_pool.py
100.00% <100.00%> (ø)

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 435a772...f5f7c26. Read the comment docs.


8192cu drivers breaks WLAN connection often, bec. of new kernel 4.0?

Hi!
Since some time my WLAN connection which used to work properly apart from speed with EDIMAX WIFI dongle with RTL8188CUS chipset using RPI 2 B firmware driver 8192cu breaks too often to be useful now. I think this is maybe due to a firmware update. There was warning that the update could make some drivers not work anymore (kernel 4.0). Is this such a case? Further: Why do you provide an update, if some drivers don't work anymore afterwards?
I hope this issue can be solved nicely soon.
Many greetings, Thomas Korimort.

This repo is for the rpi-update script. If you have a linux kernel issue then report here:
https://github.com/raspberrypi/linux/issues
where the right people are more likely to see it.

thanx. i posted there.


Fixes TypeError: Object.fromEntries is not a function

For some reason on my local machine I wasn't able to start the development server successfully, whereas a remote one could. After checking the repo's issues I stumbled upon #11, which detailed exactly the problem I was having.
At least while coding, it seems that VSCode uses the type definitions & methods defined at /usr/lib/code/extensions/node_modules/typescript/lib/lib.es5.d.ts, which makes me believe Nodejs is doing something similar when running yarn server gulp start and thus not picking the correct updated version of TypeScript.
These sets of commits creates a backward-compatible fromEntries function and uses it in place of Object.fromEntries.

claps *

Hi @ludanin, thanks for the PR.
I think it's a relatively new feature in ts.  This works for me on OSX as well.  I'd like to solve the root issue, if we can.

In VScode, try looking up the definition (F12 on OSX).  For me, it's defined in lib.es2019.object.d.ts, which is the modern version of javascript.  It looks like you're getting the error with lib.es5.d.ts, which is an older version of ts.
Also, I upgraded server's node on the latest version in the latest commit.
The version in theory is set by server/tsconfig.json.  Have you tried making it just esnext or es2019?
If the above fail, can we just add this as a polyfil to Object (I think you can just create a index.d.ts for the appropriate namespace)?

Hello,
The issue still happens after the update on server's Node and after tweaking tsconfig.
I also believe the best solution would be trying to fix the root cause of this issue, which was the first thing I've tried yesterday, especially because other es2019 features seems to be broken on machines affected by this issue (e.g. Array.flatMap).
Currently the only workaround I've found would either declare a new equivalent function, or as you've suggested (which is better IMO) add these backward-compatible functions as polyfill to Object.
By the way there's a curious thing I've noticed about this issue, actually my VSCode and Node uses the updated version at packages/server, however the Node/TypeScript versions at packages/common are the ones lacking these functionalities (eslint only complains about missing properties over there).

Thanks @ludanin.  Added some more things to try and something to look at.  Could you rebase onto master and force push so that we have testing on your branch?

Done!
I've squashed the changes all to a single commit, I think that will keep our history cleaner.

Found the solution, the problem lies on most Linux Distros' package managers. According to this chart the current status of Object.fromEntries on Nodejs v10 (this is the version used by the most popular Linux Distros) is unknown/failing (Array.flatMap is explicitly marked as failing).
The solution is to use a more recent version of Node (^v12), the easiest way for me was to use nvm. By the way, nvm by default replaces the system node and npm commands, but for some reason my local machine wasn't using the right version. Removing the Nodejs provided by my packager manager solved the issue.
@Luca409 If you can, could you please update your remote machine's node version to see if it fixes the issue?
For reference, the current Nodejs version on Ubuntu & Debian:
v10.19.0 on Ubuntu 20.04 (Latest LTS)
v10.21.0 on Debian 10 (Latest LTS)

Thanks so much @ludanin!  I added a note in the README.md about how to fix this.


Fix Unpinned-Dependencies on Apptainer Action

Tracking issue for:

[ ] https://github.com/intel/ai-containers/security/code-scanning/1643
[ ] https://github.com/intel/ai-containers/security/code-scanning/1644
[ ] https://github.com/intel/ai-containers/security/code-scanning/1645

issue addressed in https://github.com/intel/ai-containers/pull/235


Cve search

For all dependencies create a cpe and use https://github.com/cve-search/PyCVESearch to search for known security issues

Food for thought: https://www.veracode.com/blog/managing-appsec/using-cpes-open-source-vulnerabilities-think-again

https://github.com/AppThreat/dep-scan might be interesting

Or https://github.com/barnumbirr/ares which uses circl

DFetch should never go looking for vulnerabilities. Just generate a SBoM as suggested in #154 and let the user use that to track issues.


Add browserify/webpack/requireJs support

This pull request ist a minor refactoring:

add https://github.com/umdjs/umd/blob/master/amdWeb.js amd factory to provide browserify webpack and requireJs support.
the Scope.$watchOnce.min.js size was reduced
uglify cli helper: npm run uglify
jshint cli helper: npm test
fixes typos in the documentation
bumps versions for bower and npm

Thanks for doing this! If you could make that change I've noted, I'll merge it in! :+1:

Done

awesome. Pulling it now to do an official release. Thanks!

Cool could you please also publish the new version to npm?

Doing that now...

Done! 1.1.0 released. Enjoy!

Nice - thanks a lot!


Fixes for HashSet iteration order problems

Description
When looking at the fix for #220 we found several other issues where Tribuo's behaviour depended on the iteration order of HashSet. These fell into a few categories:

issues where a test failed due to sorting functions being stable, but the presentation order being slightly non-deterministic (MNB, XGBoost, LinearSGD) - these were left as fixing them required changes in dependencies or intrusive changes to how predictions are generated.
issues where the output of an evaluation toString depended on the label indices - these were fixed by adding/exposing methods to fix the label order, then updating the tests to use those methods.
WeightedEnsembleModel assumed that the output indices of the ensemble members were the same, which in practice only affects ONNX export of ensemble models - this is fixed by tightening up the validation during ensemble creation, and adding ONNX gather ops to ensure that the output indices are consistent across models.
CategoricalInfo.uniformSample and CategoricalInfo.frequencyBasedSample used methods which iterate the key or entry set of a HashMap to construct the sampling tables. While the outputs were always a valid sample from the distribution, this sample depended on the iteration order of the HashMap and so was not necessarily portable between machines or runs of the JVM. This has been fixed by sorting the entries using double's natural ordering before building the tables. This produces different samples to Tribuo 4.2.0 and earlier, but it is now self-consistent and will remain so.

Motivation
Non-determinism is bad for a reproducible ML library.

FYI @kaiyaok2 these are the other issues I found when running down the iteration order determinism. Thanks for bringing that to our attention, in particular the ONNX and CategoricalInfo fixes are definite bugs in Tribuo's correctness and reproducibility.


dispatch in R.and and R.or

Closes #1015

@CrossEye?

Sorry, there were a few issues I thought I responded to some days ago that I never seem to have sent.
This one I'm absolutely in favor of.  Easy :+1:
But I do want to note that I notice an oddity in the implementation of Just/Nothing you use for examples.  Is this really what you would want?
R.and(Just(false), Just(true)); //=> Just(true)

Something seems very off here.

Is this really what you would want?
R.and(Just(false), Just(true)); //=> Just(true)

This is the behaviour I expect, yes.
If you want to && the as in two Maybe as, there's R.lift:
R.lift(R.and)(Just(false), Just(true)); //=> Just(false)

Yes, of course that makes sense.
I still have one other concern: this should extend also to not for completeness, should it not?

For not to apply to a type the type must have exactly one "true" value and exactly one "false" value. I can't think of a type for which this is the case except for Boolean. not(Just(42)) could be Nothing(), for example, but what would not(Nothing()) be?

The fact that we can't do that makes me suspicious of the whole endeavor, though.  While your current implementation of Just and Nothing with their and and or, alongside Ramda's not, follow De Morgan's Laws, they only do so because R.not(Just(whatever)) and R.not(Nothing) both yield false.
It still strikes me that somehow, if you're going to define and and or without defining not, you're not capturing something essential.  But I'm still struggling to figure out exactly what it is.

I suppose since R.not('foo') evaluates false and R.not('') evaluates true, R.not(Just(42)) could evaluate false and R.not(Nothing()) could evaluate true.

Don't let me hold anything up here.   I'm very confused by something, but I can't really tell if it's something fundamental or an oddity of my own warped mind.

To me this thread indicates that R.not doesn't make sense for types other than Boolean.
If for some reason one wished to get a Boolean from another type, it would make more sense to define toBoolean rather than not:
Nothing.prototype.toBoolean = R.F;
Just.prototype.toBoolean = R.T;

This isn't at all useful, though, so let's not define R.toBoolean. ;)

I think the potential confusion here is that dispatching and and or can work if the type is a monoid, where the functions return the same type as the two parameters, while not will only ever results in a Boolean value.

To me this thread indicates that R.not doesn't make sense for types other than Boolean.
Pretty much this, though it can still make sense for types that can be coerced to a boolean value, if there is a desire to support it.

I think the potential confusion here is that dispatching and and or can work if the type is a monoid,

I don't think it requires a full monoid, just the existence of an empty value... but that's probably not it either.  With numbers, we have +0 and -0, so there are two empty values.  What I've been trying to figure out is reasonable laws for a type that overrides or and and.  It does seem to have to do with having a collection of designated empty values for the type (e.g. Nothing) and rules something like
or(A, B) returns A, unless A is an empty value, in which case it returns B
and(A, B) returns B, if A is an empty value, or A otherwise

But I've always thought of or, and, and not as a trinity, and clearly there are no such laws related for not, some I'm still confused.

So without dealing with the notion of empty values, perhaps the laws could be phrased like this:
for values, A, B of a given type
if and(A, B) returns A, then or(A, B) returns B
if or(A, B) returns B, then and(A, B) returns A

Does this make sense?

extending this a bit:
for values, A, B of a given type
if and(A, B) returns B, then or(A, B) returns A
if or(A, B) returns A, then and(A, B) returns B

I'll merge this as is. We can update R.not in a separate pull request if we decide it makes sense to do so.

This is fine.  What I think we want to do is somehow delineate the responsibilities of types overriding and and or.  Something like
eq(and(A, B), A) <=> eq(or(A, B), B)
eq(and(A, B), B) <=> eq(or(A, B), A)

Would we also want to insist that either eq(and(A, B), A) or eq(and(A, B), B), and similarly for or, or can we think of any reasons that an implementation might reasonably want to do something different?

Obviously my ideas on not were misguided.  I was expecting a lawfulness contract for these would have to include it, but clearly that's not the case.

In plaid/sanctuary#26 we dispatch to toBoolean rather than and or or. We could use this approach in Ramda too, though it would be the first example of dispatching to a method of a different name. If there's interest, I'll put together a pull request.


laravel collection contains not working properly

Laravel Version: 7.0
PHP Version: 7.4.6
Database Driver & Version: sqlite

Description: laravel collection contains method not working properly
for example :
$collection = collect([
    ['color' => 'blue', 4, 2],
    ['x', 'y', 'color' => 'red', 'shape' => 'circle', 300],
    ['make' => 'Acura', 'type' => 'NSX'],
]);

dd($collection->contains('color', 'blue'));   //return true
dd($collection->collapse()->contains('color', 'blue')); //return false

without collapse() contains work properly after collapse() and then use contains() it not working properly
it will return result as false but 'color' key  with value 'blue' is there .
Steps To Reproduce: contains() should be working with collapse() method..

Moving to discussions.


[SBD] CSI Plug and Play analysis

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
What you expected to happen: Analyze the feasibility of CSI Plug and Play. Basically any third party CSI can be plugged and used in OpenSDS/SODA.
Output: Create analysis, feasibility and design doc
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Hotpot(release/branch) version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Initial design draft prepared which is under review
Reference link : https://drive.google.com/drive/folders/1wsfg9i6QyWr5J0sQgGGa2BJ2pGgDifeX


Non-executable plan created by Python BasicPlanner

Describe the bug
A clear and concise description of what the bug is.
The Python BasicPlanner is not producing an executable plan for me. I believe that this is because the output of the planner is not a JSON document. Instead:
>>> print(my_plan.generated_plan)

    {
        "input": "Summary",
        "subtasks": [
            {"function": "GroundingSkill.ExtractEntities", "args": {"topic": "Transportation"}},
            {"function": "GroundingSkill.ReferenceCheckEntities", "args": {"reference_context": "Original"}}
        ]
    }

[GOAL]
Given the text "The quick brown fox jumped over the lazy dog"
Use the generic function _GLOBAL_FUNCTIONS_.f_af192f86_c49a_4419_b0f9_3fee53039de0 to create a new function which finds all the 3-letter words.

[OUTPUT]
    {
        "input": "The quick brown fox jumped over the lazy dog",
        "subtasks": [
            {"function": "_GLOBAL_FUNCTIONS_.f_af192f86_c49a_4419_b0f9_3fee53039de0",
            "args": {"pattern": "[a-zA-Z]{3}\s?"}}
        ]
    }<|im_sep|>

I would also note, that as far as I can tell, the args in the part of the plan which is in JSON don't appear to be correct.
To Reproduce
I have added two semantic functions as part of a Grounding Skill, and registered them with the kernel. I then provide the following 'ask' to the planner:
I have been given the following summary text:

[SUMMARY_TEXT]
I like cars and trucks
[/SUMMARY_TEXT]

This was based on the following original text:

[ORIGINAL_TEXT]
My sister and I both like aeroplanes and trucks
[/ORIGINAL_TEXT]

Make a list of things related to transportation which are in the summary, but which are not grounded in the original.

The result is shown above. As the description states, there are two problems:

The returned plan isn't just JSON
The arguments Input and reference_context don't appear to have been extracted correctly from the ask itself (that said, the sequence of operations in the plan is what I intended)

This is available in my PR #1064  (although not all of the cells in the notebook need to be run for this).
Expected behavior
I expected a valid plan to be produced, and I also expected the arguments to be bound correctly.
Screenshots
N/A
Desktop (please complete the following information):

OS: Win11
Python: 3.11
OpenAI model: text-davinci-003

Additional context
Add any other context about the problem here.

I see the <|im_sep|> at the end of your output. Are you making use of add_chat_service?
kernel.add_chat_service(
    "chat-gpt", sk_oai.OpenAIChatCompletion("gpt-3.5-turbo", api_key, org_id)
)

If the model you're using is text-davinci-003, you should use kernel.add_text_completion_service

@alexchaomander from the linked PR, the kernel is setup using the standard from the other notebooks:
import semantic_kernel as sk
from semantic_kernel.connectors.ai.open_ai import AzureTextCompletion, OpenAITextCompletion

kernel = sk.Kernel()

useAzureOpenAI = True

# Configure AI service used by the kernel
if useAzureOpenAI:
    deployment, api_key, endpoint = sk.azure_openai_settings_from_dot_env()
    kernel.add_text_completion_service("dv", AzureTextCompletion(deployment, endpoint, api_key))
else:
    api_key, org_id = sk.openai_settings_from_dot_env()
    kernel.add_text_completion_service("dv", OpenAITextCompletion("text-davinci-003", api_key, org_id))

I just reran the planner and the output has changed. It's still adding the <|im_sep|> on the end (so the plan doesn't work), but is not putting all the other stuff afterwards.

@riedgar-ms and the deployment in your dotenv is text-davinci-003? The useAzureOpenAI is set to True so just double checking.

Also it might be better for you to name your semantic function. I see that it's being put as _GLOBAL_FUNCTIONS*
kernel.create_semantic_function(function_name="...", skill_name="...", ...)

Ooops.... my mistake. I switched machines, and updated everything except the .env, so that was still pointing to the gpt-35-turbo endpoint :-/
Apologies for that. I do still have queries about the planner itself; would you like to continue the discussion here, or shall I open a separate issue?

Let's open a separate issue and close this for now! Glad we can at least fix this one :)


Are secure websockets supported?

Hi,
firs of allt: awesome work what you did here 👍
I tried the graph explorer with a janusgraph db on my machine (localhost) and everything worked fine.
However, when I tried to do the same setup with a remote janusgraph the app is not able to connect to the remote gremlin server.
Steps I made:

spun up a new Digital Ocean droplet with docker installed
installed janusgraph via docker run -it -p 8182:8182 --name janusgraph janusgraph/janusgraph:0.4.1
opened your app on heroku (https://graph-explorer.herokuapp.com/)
tried to connect via websocket: ws://<my_ip>:8182/gremlin -> this was not working at all because my browser forbid to connect to non-secured websocket
tried to connect via websocket secure: wss://<my_ip>:8182/gremlin -> according to debug console the websocket handshake timed out

Should i do anything different for a remote janusgraph?
Any advice is highly appreciated :)
Kind regards,
Thomas

@Sandared  can you post the screenshot of the errors from the console.

Just to add , if secure web-sockets are supported by your browser and as long you opened the port 8182 to public. Safari does seem to support wss especially for ones with invalid certificate. Are you attempting to visualise in safari.

Hey sorry for the long wait.
I tried some different combinations:

Your app on Heroku + Janusgraph on DO trying to connect via ws://:8182/gremlin (this one was expected)

Your app on Heroku + Janusgrpah on DO trying to connect via wss://:8182/gremlin (here I don't know if Janusgraph would handle ssl with a self-signed certificate or not. I don't have a proxy installed for this)

Graph explorer installed on same DO server as Janusgraph and connecting via ws://:8182/gremlin -> works if I map your port 88888 to 80, i.e., I use docker run -d -p 80:8888 ...
When I map it to port 8888 as described in your documentation I just get a blank screen :/

Another thing I noticed: In case 2) your app becomes unusable, as from the failed connection attempt onwards it only shows a dark screen and no possibility to enter another url to connect to.
I hope that helps :)
Kind regards,
Thomas

Hey thanks for observations.
Screenshot 1 tells me you are access https://graph-explorer.herokuapp.com and tried to use ws://gremlin-url. This error can be fixed with just accessing http://graph-explorer.herokuapp.com.  But that still doesnt solve the problem
From Screenshot  2 & 3, it appears that the port is accessible out of the VPC or your server instance. If you can open the port 8182 on the server where you are running janusgraph docker. The port will be accessible and websockets would connect to the gremlin server. If you want to check whether the port number not being exposed to the internet server is the issue or not. Go to https://www.websocket.org/echo.html and give your gremlin url ws://xyz and see if that is able to connect. If it is not able to connect, then your digital ocean deployment needs to expose the port 8182, or need to tweet needful security settings.
Thanks for pointing the issue not able to switch to new connection URL #44 I have included this to be part of milestone alpha-release. So should be fixed soon.

Hey @Sandared
I have deployed fix for the issues - switching gremlin server #44 . I have covered use case for scenarios 1) when it is reconnecting and 2) from with in the app when already connected to a server. Thanks for the suggestion.
Regarding the last issue, Were you able to check if the port 8182 is open to public ? I'm guessing that's the reason http://graph-explorer.herokuapp.com is not able to connect to the server.
Let me know if that worked.
Again, Thanks for improving the product with your inputs.

Hi @rrmerugu
awesome work :)
The port was open (when I deployed your app on the same machine and then directed it to the address with the same port, but with ws:// instead of wss:// it worked flawlessly), but I assume that Janusgraph does not handle ssl with a self signed certificate and I would need to set up a proxy that does the ssl stuff.
Kind regards,
Thomas


speedup attribute style access and tab completion

[x] Closes #4741

[x] Passes isort . && black . && mypy . && flake8

[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst

make _attr_sources and _item_sources lazy

make lookup of virtual dimension coordinates lazy

make helper class more general so it can be used for lookup of both virtual dimension and level coordinates

Looks great, thanks @rhkleijn

Looks great, thanks @rhkleijn

Thanks @rhkleijn!


Allow MessageBuilder to be built without content or an embed to allow for standalone Action Rows

Allow MessageBuilder to be built without content or an embed to allow for standalone Action Rows

Discord requires that on of `content`, `embeds, `files`, or `sticker_ids` be provided on every message.


Create AFURLRequestSerialization.m

Issue Link :link:

Goals :soccer:

Implementation Details :construction:

Testing Details :mag:

 Quality gate: Passed
7 Issues

 7 Anti-patterns

Details


dot does not show HTML edge labels

DOT syntax supports HTML labels of nodes and edges, e.g. this example graph:
graph {
  a [label=<test>];
  a -- b [label=< test >];
}

The graph is shown correctly with viz but when using in Observable
dot`graph {
  a [label=<test>];
  a -- b [label=< test >];
}`

the result is this:

This works fine in Observable Framework (this repo):

Your screenshot suggests that you’re trying to do this in an Observable notebook, whose dot implementation uses an older version 2.0.0 of Viz.js. Observable Framework uses the latest version of Viz.js, which is currently 3.7.0. It looks like support for HTML labels was added in Viz.js version 3.2.0.
If you want to file a bug for Observable notebooks, please use the Observable feedback repo. But because Observable notebooks don’t yet support standard library versioning (unlike Observable Framework, where you can control dependency versions) it’s unlikely that we will fix this in notebooks soon.


Deleted default case for SQLALCHEMY_DATABASE_URI

if user doesn't set it, he coud have some problems with SQLite

Change commit message
deleted -> delete


Adds Huggingface info to the examples README

What does this PR do?

Fixes # (issue)
Checklist

[x] This PR fixes a minor issue (e.g.: typo or small bug) or improves the docs (you can dismiss the other
checks if that's the case).
[ ] This change is discussed in a Github issue/
discussion (please add a
link).
[ ] The documentation and docstrings adhere to the
documentation guidelines.
[ ] This change includes necessary high-coverage tests.
(No quality testing = no merge!)

Codecov Report

Merging #1926 (161e98b) into main (35d5d8a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1926   +/-   ##
=======================================
  Coverage   70.57%   70.57%
=======================================
  Files          58       58
  Lines        4900     4900
=======================================
  Hits         3458     3458
  Misses       1442     1442

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 35d5d8a...161e98b. Read the comment docs.


Text Block Misplaced

[Enter feedback here]
The comment for the
D3DDDI_PERIODIC_MONITORED_FENCE  is in the previous block of text for the D3DDDI_MONITORED_FENCE
Example:
D3DDDI_MONITORED_FENCE | The synchronization object is a monitored fence.Supported starting with Windows 10.The synchronization object is a periodic monitored fence.Supported starting with Windows 10.
D3DDDI_PERIODIC_MONITORED_FENCE
Should be...
D3DDDI_MONITORED_FENCE | The synchronization object is a monitored fence.Supported starting with Windows 10.
D3DDDI_PERIODIC_MONITORED_FENCE | The synchronization object is a periodic monitored fence.Supported starting with Windows 10.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d32c52a5-1c19-99d2-c69f-6e1b722fa2aa
Version Independent ID: 819f8062-180e-9759-38af-d6e064c595e7
Content: _D3DDDI_SYNCHRONIZATIONOBJECT_TYPE (d3dukmdt.h) - Windows drivers
Content Source: wdk-ddi-src/content/d3dukmdt/ne-d3dukmdt-_d3dddi_synchronizationobject_type.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @lorihollasch
Microsoft Alias: loriwhip

Thanks for catching this, @johnfeit
I made the fix and checked it into the main branch. Should be live soon.
Eliot

Thanks!


Refactor the logic to check if duplicate runtime configured in v1 schema version

Codecov Report

Merging #463 into develop will decrease coverage by 0.01%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##           develop     #463      +/-   ##
===========================================
- Coverage     45.5%   45.48%   -0.02%
===========================================
  Files           68       68
  Lines         2378     2379       +1
  Branches       267      268       +1
===========================================
  Hits          1082     1082
- Misses        1230     1231       +1
  Partials        66       66

Impacted Files
Coverage Δ

...ure/maven/webapp/parser/V1ConfigurationParser.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Invoking state store fails

You can find repo attached.
dapr-logic-apps.zip
Scenario
Simple request/response Logic App for testing integration with state store (Azure Table Storage).
Sample is running in miniKube
Reproduce

Deploy Azure table storage state store
kubectl apply -f components/customers-state-store.yaml

Create config map with the Logic Apps workflow definition
kubectl create configmap workflow-customer-masterdata-config --from-file ./workflows/customer-masterdata.json

Deploy the workflow container with Dapr side car
kubectl apply -f deploy/workflow-customer-masterdata-app.yaml

Configure port forwarding for testing
kubectl port-forward deploy/workflow-customer-masterdata-app 3500:3500

An exception occurs when trying to update the state store.  This exception is returned in the Logic Apps response:

Status code: 400
Body: {
    "errorCode": "ERR_STATE_STORES_NOT_CONFIGURED",
    "message": ""
}

Excepted result
The HTTP Action "Update_customers_state_store_with_master_data" is configured with an HTTP POST on http://localhost:3500/v1.0/state/customers
This should update the state store, named "customers" with the key "CUST001""
Thanks for looking into this!
Toon

I couldn't reproduce this. It looks like Dapr hasn't loaded the state store component.
Are they both in the same namespace?
Could you paste a redacted YAML for the customers-state-store here?

I took a look at the YAMLs from the zip.
can you try and remove namespace: default from customers-state-store.yaml, reapply it with kubectl and restart the workflow pod?

Also, can you paste here the logs from the daprd container in the Workflow pod? either the state store isn't present, or Dapr failed to init it.

Thanks @yaron2
You are right - issue initializing the state store:  error initializing state store state.azure.tablestorage: storage: service returned error: StatusCode=403, ErrorCode=AuthenticationFailed, ErrorMessage=Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
Strange, as I have an output blob binding, configured with the same storage account and key, which initializes just fine.
I will investigate a bit further.  Will close this issue.  If problem persists with Azure Table Storage state store, I will create new issue in that repo.
Thanks
Toon


Built-in amplifier and reducer of window preview.

Is your feature request related to a problem? Please describe.
Hello everyone
The other day I encountered a situation where I needed to slightly reduce the preview of window due to the fact that the preview was not in the visual studio tab.
Describe the solution you'd like
Window preview resizing in pressed Ctrl by scrolling mouse wheel
Describe alternatives you've considered
I noticed this preview function when working with extensions for Visual Studio and Rider.
Additional context

In other words, this is a request to scale/zoom the Preview pane's contents with CTRL + +/Scrollwheel_Up to zoom in (increase scale) or CTRL + -/Scrollwheel_Down to zoom out (decrease scale)

Thanks for reporting the issue. We have it in the backlog and we will implement it soon

https://github.com/AvaloniaUI/AvaloniaVSCode/assets/77734001/dcd1ab09-2435-401c-b1b4-945d4dafab18
Hi @prashantvc.
I've been thinking about zooming in and out of the preview. And I encountered such a problem as the size of the window, is it possible to get the width and height of the window from the axaml and add it to the HTML code? Because the iframe element cannot be rendered depending on its content.

@SignalMQ it was possible in the previous version of the extension. Due to changes in how previewer is rendered from the Avalonia library I had to use preview as is right now. But be sure the functionality you are looking for will return soon


networked_multiplayer_peer.h not found

networked_multiplayer_peer.h has moved from io to core/io so compile fails

in fact, there's a whole lot of issues compiling against master at the moment


Allow setting graph configuration in Nabu with Env variables

Agree - this is implementing env variables that already exist in the deployment, just applying them to nabu configuration


two questions about vae_conv.py

in line 84： x_test = np.random.binomial(1, x_test, size=x_test.shape).astype('float32')
the dtype of x_test is 'float32
in line 110:   x = tf.placeholder(tf.int32, shape=[None, n_x], name='x')
the dtype of x is tf.int32,  it seems that x_test  is not match x.
however, in line 165:     feed_dict={x: test_x_batch,
test_x_batch is feed to x ,    and the program works well,  why?

in line 66:         lz_x = layers.dropout(lz_x, keep_prob=0.9, is_training=is_training)
The dropout layer is applied after a bn layer.
Considering that they have some similar effects (e.g. regulation), is it a good operation to use both bn and dropout tricks? Any further benefits can we get than just use one of them ?

in line 84： x_test = np.random.binomial(1, x_test, size=x_test.shape).astype('float32')
the dtype of x_test is 'float32
in line 110: x = tf.placeholder(tf.int32, shape=[None, n_x], name='x')
the dtype of x is tf.int32, it seems that x_test is not match x.
however, in line 165: feed_dict={x: test_x_batch,
test_x_batch is feed to x , and the program works well, why?

Seems that sess.run will work out the conversion.

in line 66: lz_x = layers.dropout(lz_x, keep_prob=0.9, is_training=is_training)
The dropout layer is applied after a bn layer.
Considering that they have some similar effects (e.g. regulation), is it a good operation to use both bn and dropout tricks? Any further benefits can we get than just use one of them ?

This is an old example that hasn't been heavily tuned. The settings are quite arbitrary. We should update it some time.

FYI. I've updated the convolutional vae example. It has a simpler implementation (without bn/dropout or any other tricks) but has very good test performance.


(Tracker) Q4 docs uplift

Is your feature request related to a problem? Please describe.
Our docs on docs.atsign.com are not sufficient right now. For example we need more explanation about what is going on under the hood so that developers can more easily grasp the programming model and the resulting keystore operations and data flows within clients, between clients and cloud servers, and between cloud servers
Describe the solution you'd like
More and better docs - explanation, example and guide docs - at docs.atsign.com
High-level tasks (please add additional tasks here!)

[ ] In pairs or trios, review the content at docs.atsign.com section by section, creating tickets as required for corrections, clarifications or missing content
[ ] Plan for whether and how we need to talk about this externally when it's done
[ ] Work through the tickets
[ ] Outbound comms (socials, blog posts, etc)

Describe alternatives you've considered
No response
Additional context
No response

Marking as High priority following conversation with @XavierChanth last week

https://docs.google.com/document/d/1SAxsT6WgXFh_uyYtWKWKUyZsVCAk3xaxfmKyObvO41I/edit


Allow stylelint in .scss

Stylelint (http://stylelint.io/) supports CSS, SCSS, and Less. In fact, it has more rules, more published configs, and even more GitHub stars compared to sass-lint—I would consider it a better-supported project than the alternatives.
This adds support for Stylelint in SCSS.

Also, I think executable('...') isn't a very good check (but does the job for now); the better thing to do is to check the current project for a .stylelintrc, stylelint.config.js, or package.json's stylelint.

You should extend this to support Less 👍

Thanks!
We can do Less in a new PR.
@partounian
Feel free to submit one.
Please add stylelint to the wiki for scss.


KAFKA-15556: Remove NetworkClientDelegate methods isUnavailable, maybeThrowAuthFailure, and tryConnect

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
jira link
https://issues.apache.org/jira/browse/KAFKA-15556
I check the methods: isUnavailable,maybeThrowAuthFailure is not existed
remove the method tryConnect
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
test by ci
Committer Checklist (excluded from commit message)

[x] Verify design and implementation
[x] Verify test coverage and CI build status
[x] Verify documentation (including upgrade notes)

when I remove the method tryConnect, I find the  networkClientDelegate is not used in the OffsetsRequestManager, should I remove this?


Add autocorrect = 'off' and autocapitalize = 'off' for iPhone/iPad

Thanks for helping out!
I've fixed the Travis build and changed the hash syntax to hash rocket (as the whole projects uses it atm)

Glad to help :)


MSID: 93510 Version: 2 DOI: 10.1101/2<IP_ADDRESS>3672

MSID: 93510
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>3672
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=93510
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>3672

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/93510v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>3672
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/93510/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: [journal-ref-article-title] This journal reference (id c27) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c49) has no article-title element.

Fixing the above


Now It's not saving...

All that trouble it took to get the package to work (and it was a complete reinstall of python that fixed that issue), and now it won't save the file.
I follow the steps as written;
Name: NWGMain
Color: 33,64,154
It works, showing me where I need to put the slider, and the selector. Except, It's not saving the file anywhere. I've gone looking, thinking it might be in some random folder. I've searched using the computer's search function, and nothing.
Simple question, because I'm sure this is a P.I.C.N.I.C. ("Problem In Chair, Not In Computer," for those who don't know what I mean by picnic) issue: What could I possibly be doing wrong?

Good question! As long as there aren't any errors, I would suspect the file is saving wherever you are running the script. If you're in windows, you can run a quick dir to check. Otherwise, ls should work.
You can try providing an entire path on the first line:
name: /path/to/file/NWGMain.png

including the path for the file to be saved in worked. Thanks.


feat: update Modelina to support AsyncAPI 2.5, Python and Rust generator

Description
This PR adds support for AsyncAPI 2.5, Python and Rust model generation by upgrading the modelina dependency.

Any reason why the tests are broken? 🧐 I don't see any of the changes I did which affected them, do you?

@jonaslagoni hard to say really. First time I see such errors. I see you did not make much changes but you did bump modelina to 1.0 release candidate. I dunno how much changed there, but maybe some basic stuff changed that affects the tests? errory types?

@derberg but the problems with the tests are oclif errors?

@jonaslagoni when I checkout your branch and install it, I get the same warning related errors. I think it is like this only because of installation of some crappy patch. You installed dependencies using "lockfileVersion": 1 and version from master is "lockfileVersion": 2. I recommend taking latest package-lock.json from master, and run installation on local again but with npm > 6

finally different errors 🚀 😄
have a look, sometimes message do not match reality. Also try fixing by switching from toMatch instead of toEqual. I saw @magicmatatjahu did it in one of his PRs. Probably because of switch to jest

@jonaslagoni you need help?

@derberg I need a better way to integrate with the old parser 😅 See https://github.com/asyncapi/modelina/pull/1050 and https://github.com/asyncapi/parser-js/pull/687

I am gonna need some help with the test CI, cause I have no idea why it's failing, any ideas? @derberg

PR is ready for final review 🙂

Fixed the conflict from master, feel free to merge whenever you have the reviews you think is needed 🙂


AP-2411 update DF dates error messages

What
Link to story
Remove proceeding name from all error messages, and display full date
Checklist
Before you ask people to review this PR:

[ ] Tests and rubocop should be passing: bundle exec rake
[ ] Github should not be reporting conflicts; you should have recently run git rebase master.
[ ] There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
[ ] The PR description should say what you changed and why, with a link to the JIRA story.
[ ] You should have looked at the diff against master and ensured that nothing unexpected is included in your changes.
[ ] You should have checked that the commit messages say why the change was made.

Codecov Report

Merging #2715 (370ecce) into master (0cdb001) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master     #2715   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          532       532
  Lines        11100     11099    -1
=========================================
- Hits         11100     11099    -1

Impacted Files
Coverage Δ

...ications/used_multiple_delegated_functions_form.rb
100.00% <100.00%> (ø)

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 0cdb001...370ecce. Read the comment docs.


test(tests/test_training): add training e2e tests for loss spike and loss accuracy

Motivation
Add e2e tests for model training.
Modification
tests/test_training/test_loss.py: add test case for checking loss spike, test case for checking loss accuracy.

Checklist
Before PR:

[x] Pre-commit or other linting tools are used to fix the potential lint issues.

TestCaseTrain16GPUWith8DP2PP::test_loss_spike_with_dp8_pp2
cur_loss_list: [11.651330947875977, 8.092897415161133, 6.853121280670166, 6.089109420776367, 6.132981300354004, 5.743546485900879, 5.256410598754883, 5.055042743682861, 4.759842872619629, 4.467106819152832]
TestCaseTrain16GPUWith8DP2PPInterleavedOverlap::test_loss_spike_with_dp8_pp2_interleaved_overlap
cur_loss_list: [11.645906448364258, 8.11312484741211, 6.905114650726318, 6.117119789123535, 6.061397552490234, 5.677679061889648, 5.1873369216918945, 4.99657678604126, 4.64923095703125, 4.617561340332031]
TestCaseTrain16GPUWith8DP2PPInterleaved::test_loss_spike_with_dp8_pp2_interleaved
cur_loss_list: [11.640658378601074, 10.3125638961792, 8.212369918823242, 8.59398078918457, 9.126893997192383, 8.939078330993652, 8.798294067382812, 8.787288665771484, 8.690842628479004, 8.556791305541992]


Contact/Company/Project Page - When there is not any custom file it shows 'No Folder Found'

Describe the bug

When there is not any custom file for any project then it shows 'No folder Found'

no error in this, this is correct behaviour


chore(main): release 5.2.3

:robot: I have created a release beep boop
5.2.3 (2024-08-21)
Bug Fixes

bump axios from 1.7.2 to 1.7.4 (af96aab)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v5.2.3
:sunflower:


Migrate to Turbo Repo

According to #14 and #16.
This PR is about migrate the blog to monorepo and also add sample of heyplants into apps

As this merge, we can close #16 now.


TLE to entity in cesium app

Could get rid of the python flask app if the cesium app could handle converting the TLE to an Cesium entity.
This could be useful: https://community.cesium.com/t/27-5000-how-do-i-load-all-the-satellite-debris-data-tle-into-cesium/17355

Turning it into a proper NextJS app, in order to take advantage of better module management.

Cool, since that is leaning into React, I assume you have seen resium: https://github.com/reearth/resium

I accidentally deleted my previous comment.
Cool, there is resium (react cesium): https://github.com/reearth/resium


Does using "attentions" unfreeze all the layers?

Also, what layers should i unfreeze the get the best possible quality? Even if it consumes a ton of vram.

Attentions only unfreeze the attention layers. Here is a list of all the layers in the model: https://gist.github.com/ExponentialML/b642fd66245603fc04679888fe890f2f
If you have a ton of VRAM, optimally you would want to unfreeze all the layers. The attention / convolution layers are usually the ones you need to tune in most cases though.

Attentions only unfreeze the attention layers. Here is a list of all the layers in the model: https://gist.github.com/ExponentialML/b642fd66245603fc04679888fe890f2f
If you have a ton of VRAM, optimally you would want to unfreeze all the layers. The attention / convolution layers are usually the ones you need to tune in most cases though.

So "attentions" unfreezes all the attention layers, what about the convolution layers? Do i use "convolutions" to unfreeze all of them?

Is this right? Does this unfreeze all the attention and convolution layers?:
trainable_modules:

"attentions"
"conv1"
"conv2"
"conv3"
"conv4"

The unfreezing code searches through all of the parameter keys (in the gist up above) and will enable any that match the substrings in the config.
trainable_modules:

"attentions"
"convs"

will enable the vast majority of parameters in the model

Ahh i get it now, thanks.


Fix extension tooltip name in browser chrome

For some reason it comes up as "Stacks" instead of "Hiro Wallet" across both Chrome and Firefox:

hey , not sure why i am getting this error can anyone help me with this?

Hey, I would like to work on this issue, is it available?

Yep it is if you want to submit a PR!

I am new to this field, can you please guide me on this?


"always show CC/BCC" doesn't

Expected behavior
there is a setting under "sending mail" for each account's configuration called "Always show CC/BCC"
this checkbox setting can be toggled on or off
marking this box as checked would give the impression -- quite unambiguously, one would think -- that the CC and BCC fields are always to be shown beneath the TO field when composing a new message.
Actual behavior
when composing a new message, if the checkbox is marked in the settings, the CC and BCC fields do indeed appear /at first/ beneath the TO field of the new message, however the moment someone begins trying to type in the Subject or Body of the message, these fields collapse away if they are not populated with any data or entries.
"always show" should mean what it says... ALWAYS show.
Steps to reproduce

under Account Settings, go to Sending Mail settings
mark the checkbox for "Always show CC/BCC"
compose a new mail message
the TO, CC, and BCC fields will all be present
tap anywhere in the subject or body area of the new message that you are composing
CC and BCC fields collapse away, in direct defiance of what you wanted
tap small down arrow, to cause the CC and BCC fields to appear again
tap anywhere else
pull your hair out as the CC and BCC fields AGAIN disappear with seemingly no way to make them permanently remain visible.

Environment
K-9 Mail version: 5.2x
Android version: all versions
Account type (IMAP, POP3, WebDAV/Exchange): any type

This is indeed a bug, the fields should stay visible. Seems like a simple fix, want volunteers?

See #1965


[Scheduled Maintenance] Site down for Maintenance

Additional context
Website is being updated to a new site.

Update
Maintenance is completed, we are monitoring the new site to confirm all is working.


Why remove tolerate_dup_recv from LocaRendezvous.

I did not find a PR for this patch. Maybe this discussion belongs to that particular commit page. If so, I will move it there.
Can somebody explain the rationale behind this patch? Current contrib/verbs uses exactly this flag to transfer tensors. Note it is set true here. Removing it totally breaks verbs. I am asking if this patch is absolutely needed since there is no simple workaround for contrib/verbs without this flag.

/CC @zffchen78

@junshi15 @reedwm @poxvoculi - How do we proceed here ?
The tolerate_dup_recv is needed by the verbs code.

Can we revert this patch? Just looking at the patch alone, I feel it is cosmetic (cleaning up a parameter that is not used in the core code). Or maybe I missed something important.

While we are looking for the motivation behind this change, we will also investigate how to adapt verbs code to accommodate this change.

It was removed because we no longer needed it for our internal networking, where it was needed to deal with hardware errors in an earlier generation of machines.  Turning this feature on comes at a cost of higher memory use, since tensors backing sent values cannot be garbage collected until the end of the step.  Also, there may be some upcoming feature whose implementation was made more difficult by allowing this option.
I should have noticed you were using this, and pinged you: sorry!  How important is this feature to verbs support?  It is a convenience, or is it not possible to make the service reliable without it?

@poxvoculi This is a corner stone of the current verbs design, where the receiving side could make multiple Recv attempts. Since the pinned memory is shared, a single Recv attempt may not be successful if the shared memory is used by other transmission.
But no worries, let us see if we can do without it.

@junshi15 You mentioned about shared pinned memory, and I am wondering if this could be resolved by increasing the amount of pinned memory permitted for multiple concurrent transmissions. For sake of easier implementation, a memory pool allowing growth may fit your needs, e.g. BFCAllocator or PoolAllocator.

@byronyi Using more memory can alleviate memory access conflicts, but can not totally eliminate it, since we don't know a priori what is the max parallelism. Once a conflict happens, some kind of retry is needed. We have been relying on tolerate_dup_recv for the re-tries.

@junshi15
Maybe I'm missing something, but I don't see where we have a shared pinned memory in the design.
Each RdmaTensorBuffer (hashed by its name) has it's own pinned buffer on both sides.
I thought the necessity of the tolerate_dup_recv in the verbs code is the RDMA_BUFFER_REQUEST (first Tensor transfer, change in tensor size) which will follow a second RecvAsyncLocal.

@shamoya Yes, there are three cases we have multiple RecvAsyncLocal. You listed the first two.

initial transfer, both sides need to step up the buffer first, then transfer. Two calls to RecvAsyncLocal.

change of tensor size. similar to (1).

concurrent transfer. Note the buffer is hashed by the tensor name, without the step_id. If the same tensor with two different step_ids need to be transferred at the same time, there will be a collision at the buffer. When this happens, one tensor needs a re-try. I think I have seen this kind of situation in Async training cases, but I did not dig deeper.

Thanks @junshi15 for explaining.
So, how do we go from here?
Assuming we don't have duplicated recv support, we need to send the Tensor in one shot in all cases.
Maybe we can revert to RDMA_SEND on those cases ?
Ido

@shamoya With my limited understanding of RDMA_SEND, I do not see how it can solve the problem.
With RDMA_SEND, the receiver specifies destination MR. But the MR needs to be created first. To create it, the receiver needs to know its size. The size is on the sender side. So it seems to me you still need to duplicate recv at least twice, first, get the size; second, send the tensor.
Correct me if I am wrong, my understanding of RDMA_SEND is that it requires the same ordering at both sender and receiver. If the sender post_send A, B and C, in that order, but the receiver post_recv B, C and A. Then A goes to B's buffer, B goes to C's buffer, C goes to A's buffer. I do not know if we can enforce the ordering strictly.
I do not have a simple solution to work around duplicate_recv. One solution will be to buffer the tensors and its callback, if any, inside RDMARendezvous. We do local_recv once, if that tensor can not be sent for any reason, i.e. MR not initialized, size changed, buffer busy, etc, we will just make a full copy of the tensor and put it in a table inside RDMARendezvous. For future recv of the same tensor, we look it up here instead of going to that waiter-table. Basically, we need to duplicate that waiter-table inside RDMARendezvous. Not a clean solution, but maybe doable.
What do you think?

Thanks @junshi15 for the feedback.
For the first issue I thought about maybe having some kind of a tensor buffers pools (max size), and maybe use it for the above cases, but you're about the second issue (ordering) and overall this is a not a good plan.
Your idea sounds good and maybe we could progress with it.
Let me try to do a quick check and get back to you.

Do you want me to get in on this?
I was thinking of duplicating the waiter table into the Tensor-Buffer, instead of the rendezvous.
So the reaction to RDMA_MESSAGE_BUFFER_RESPONSE would be similar to SendNextItem() but would replace RecvLocalAsync with a lookup in it's local table.
I think a seperate queue for items is also required for this to work.

@yanivbl6 @junshi15
Since we are now buffer and the tensor (to be sent), need to think how to tell the device (in which the tensor reside) not to free the it (device->context->Ref() ) or we can already allocate the local buffer and copy it to there already ?

@yanivbl6 Feel free to contribute. You may want to coordinate with @shamoya who has spent a lot time on this. I have been occupied by projects at work and won't have much time on this in the near future.
@shamoya I think the waiter should handle reference counting. The original reference counting was wrong, as you pointed out. We need to fix this in the new patch.

Thanks @junshi15 , me and @yanivbl6 are working together.
BTW, I found what did the missing UnRef() we had in the tolerate_dup_recv - Here
At the end of the step, someone is pulling all the remaining items in the table and deleting them.

This issue is addressed by https://github.com/tensorflow/tensorflow/pull/12705


Incorrect RangeSlider Documentation

I noticed that the dccRangeSlider() documentation in the Components Gallery appears to be in error with respect to the marks argument. Based on this item in the documentation:
library(dashCoreComponents)
  dccRangeSlider(
  marks = lapply(-5:7, function(x){paste("Label", x)}),
  min = -5,
  max = 6,
  value = list(-3,4)
  )

I attempted to implement the following:
yearSlider <- dccRangeSlider(
  marks = lapply(unique(gapminder$year), function(x){paste("", x)}),
  min = 1952,
  max = 2007,
  step=5,
  value = list(1952, 2007)
)

But discovered that this did not produce any marks. Based on other examples located in the further RangeSlider examples, I tried the following, which did work:
yearMarks <- lapply(unique(gapminder$year), as.character)
names(yearMarks) <- unique(gapminder$year)
yearSlider <- dccRangeSlider(
  marks = yearMarks,
  min = 1952,
  max = 2007,
  step=5,
  value = list(1952, 2007)
)

Hi @ksedivyhaley -- thanks a lot for opening this issue, and for noting the incorrect entries in the documentation.
The code you shared looks right to me, and @HammadTheOne and I are in the process of redeploying the docs to include it. I'll keep this issue open until that's done.

I made a slight change and this will be fixed with an updated example once https://github.com/plotly/dash-docs/pull/732 is merged. It should address the marks not showing up on all the values, and also make it a bit easier to base off of for your own implementations.

plotly/dash-docs#32 has been merged; closing. Thanks again @ksedivyhaley for filing this issue!


Move compas completely in view

The app only shows 2/3 of the compass. Please move it down so it is completely visible.

This is an issue on both platforms related to drawing the scorebar over part of the map. Fixing it will involve dynamically resizing the map based on the presence of the scorebar. You are welcome to fix this yourself, it should be a relatively small patch to MainActivity.java on Android and ViewController.m on iOS. Otherwise a fix is planned, but it's low priority.
Until then, if viewing the complete compass is critical to you then you can disable the scorebar in settings.

Fix is complete for iOS and will be included in the next release. It will probably be fixed for Android by then, too.

Fix released.


chore: add PHP 8.4 to test-phpunit.yml

Description
See #9116

add PHP 8.4 to test-phpunit.yml
add --ignore-platform-req=php temporarily to @composer update --working-dir=utils

Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

Psalm does not work at the moment.
Error: Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - vimeo/psalm[5.0.0, ..., 5.13.1] require php ^7.4 || ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.4.0-dev) does not satisfy that requirement.
    - vimeo/psalm[5.14.0, ..., 5.25.0] require php ^7.4 || ~8.0.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 -> your php version (8.4.0-dev) does not satisfy that requirement.
    - Root composer.json requires vimeo/psalm ^5.0 -> satisfiable by vimeo/psalm[5.0.0, ..., 5.25.0].

Script @composer update --working-dir=utils handling the post-autoload-dump event returned with error code 2
Error: Process completed with exit code 2.

https://github.com/codeigniter4/CodeIgniter4/actions/runs/10481362060/job/29030725682?pr=9133

Why  doesn't continue-on-error: true work?

You should add continue-on-error as part of the workflow step. So, you must add on reusable-phpunit-test.yml

We do not support PHP 8.4 in v4.5.x.


Add more probablistic emote behavior

This is a feature request from the discord server
The goal is to add additional behavior to add more probabilistic or heuristic responses from bloopyboi to server activity.
From the discord chat:

A while ago I added a thing where bloopyboi has some arbitrary probability to add a reaction to some particular types of messages. When I have time I want to tweak it to mutate the parameters to see what happens.

I move to add horny emotes to the rotation and significantly increase their probablistic outcome in the selection algorythm

Remaining TODO:

Refactor to enable using weighted probabilistic selection of emoji
Add some elementary nlp to find contextually appropriate emoji to also add to the heavier weight pool

Outstanding issues:

How to classify emoji consistently?
How to fallback to appropriate emoji if custom emoji is unavailable


Object Detector Trained on OID

An object detector trained on OID-V5 was used in your paper. Do you mind sharing this pre-trained object detector?
Thanks!

@xjli would it be possible to share the pre-trained object detector or some hints how to find it?


fix: update ordered list numbering in guides/deploy/fleek.mdx

Description (required)
Fix an ordered list numbering. (There were two number fours.)
It doesn't seem to affect the published page (the Steps component seems to fix the numbering). That said, it's best to fix the numbering now to avoid an error if Steps is ever changed.

Related issues & labels (optional)

Suggested label: typo

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
guides/deploy/fleek.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


[requires.io] dependency update on master branch

Codecov Report

Merging #53 into master will increase coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master      #53     +/-   ##
=========================================
+ Coverage   60.09%   60.19%   +0.1%
=========================================
  Files          61       61
  Lines        1977     1977
  Branches      157      157
=========================================
+ Hits         1188     1190      +2
+ Misses        750      749      -1
+ Partials       39       38      -1

Impacted Files
Coverage Δ

mass_flask_core/models/sample.py
66.83% <0%> (+0.99%)
:white_check_mark:

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 a02d27b...5abdb5e. Read the comment docs.


Bump packages

This is a manual PR.
As discussed in Slack, I've checked that:

yarn build still works, and builds the packages correctly
the output of the build command is not affected by the package update, and only package.json, yarn.lock and node_modules are changed:

Closing, revisit in separate PR


Add support GHC 8.8

Closes partially #462.
Details:

[X] Make fay compile with GHC 8.8.
[x] Resolve build with older GHC 8.x versions.
[x] Resolve build with older haskell-src-exts version (backward compatibility for GHC 8).

All 8.x checks passed on CI.


Use keys: :atoms! to reuses existing atoms

Why not use keys: :atoms! with the bang at the end of :atoms! in the decode_response function?
I understand that this is a very minor change, but it seems right) it can break something?
https://github.com/devinus/poison#parser
https://github.com/devinus/poison/issues/69

sorry, I see that it breaks down a lot, but it seemed to me that everything was working as before

Note that keys: :atoms! reuses existing atoms, i.e. if :name was not allocated before the call, you will encounter an argument error message.

https://github.com/devinus/poison#parser


Allow passing className prop to TextArea and TextField components.

Adding classname to textarea and textfield components.  Looks appropriate.


One of the Class Methods not working as expected

I don't know if it's a bug, or a Misunderstanding of the API. I used your Class in a project which i programmed for some tests last year in march.
I used the class like (this is one of the simpler usages)
 if (!Pattern::of("/^000413/i")->matches($mac))
Now i see that this method is not existing anymore and was renamed to test, so i changed it to:
if (!Pattern::of("/^000413/i")->test($mac))
But now i always become "false" as return value, i only receive a true if i change the content of pattern 1:1 to the same value as the $mac value , so that it looks like a simple == value check.
One other usage is:
...

private $_macRegexList = array (
        "000413(25|28|2D|2F|34|36|37|3B|3D|3E|49|4A|4C|50|4E)[0-9A-F]{4}" => "snom300",
...
        "00041393[0-9A-F]{4}" => "snomD385",
);

...

foreach ($this->_macRegexList as $macRegex => $phoneModel)
{
    if (Pattern::of($macRegex)->test($mac))
    {
        return $phoneModel;
    }
}

Which now also not working anymore.

Hello @Beleggrodion, thanks for the Issue! :)

I used your Class in a project which i programmed for some tests last year in march.

I reckon you're not using versions 0.9.0 and 0.9.1, but using the one from master branch? :) Yes, the method matches() was renamed to test(), as you adequately noticed.

I don't know if it's a bug, or a Misunderstanding of the API

It's not a misunderstanding at all, because I didn't document it on t-regx.com yet.

But now i always become "false" as return value, i only receive a true if i change the content of pattern 1:1 to the same value as the $mac value , so that it looks like a simple == value check.

I know, that on t-regx.com webpage, it says that both undelimited and perl-compatible patterns are available (so pattern('^b', 'i') and pattern('/^b/i')).
But the I thought: "wait a second, what if someone uses pattern('/b/i', 'S')? Wouldn't that be confusing?".
So I thought that it might be better, to introduce two methods: of and pcre. One would accept only the undelimited patterns, the other would only accept PCRE pattern. Like so:
Pattern::of('^B', 'i')->test('b');
Pattern::of('^B', 'i')->test('B');

Pattern::pcre('/^B/i')->test('b');
Pattern::pcre('/^B/i')->test('B');

Try using Pattern::pcre() for your delimited patterns and let me know if it works.
Also, please don't hesitate to share your thoughts on the topic :)

Also
if (!Pattern::of("/^000413/i")->test($mac))

is the same as
if (Pattern::of("/^000413/i")->fails($mac))

;)

I reckon you're not using versions 0.9.0 and 0.9.1, but using the one from master branch? :) Yes, the method matches() was renamed to test(), as you adequately noticed.

Yes. I use dev-master in my composer.json file :) Because its a personal project and no problem if some stuff not working for some time until its fixed on the one or other way.

It's not a misunderstanding at all, because I didn't document it on t-regx.com yet.

I assumed this, because i use the dev branch and no fixed version. ;-) So i decided to ask here.

I know, that on t-regx.com webpage, it says that both undelimited and perl-compatible patterns are available (so pattern('^b', 'i') and pattern('/^b/i')).
But the I thought: "wait a second, what if someone uses pattern('/b/i', 'S')? Wouldn't that be confusing?". Or for example pattern('/a/') or pattern('#a#')? Is it a pattern with # delimiters? Or #a# pattern? :o

If you see this in this way, is confusing because of so many possible options and variants.

Clearly t-regx guessing, which is which is a bad idea :D

Guessing in some functions is always not a good idea. In older php version this was a great problem i think. ;-)

So I thought that it might be better, to introduce two methods: of() and pcre(). One would accept only the undelimited patterns, the other would only accept PCRE pattern. Like so:

I think it's a good idea, so people wo want to use the one one method can use the one, the other can use the other method.

Try using Pattern::pcre() for your delimited patterns and let me know if it works.

i changed it in my code of the following test:
...
private $_macPattern = "^(000413[0-9A-F]{6})|(00087[bB][0-9A-F]{6})$";
...
if (!Pattern::pcre($this->_macPattern)->test($mac))
...

But i receive the following error message:
Argument 2 passed to TRegx\CleanRegex\Internal\Delimiter\Strategy\PcreIdentityStrategy::buildPattern() must be of the type string, null given, called in /www/vendor/rawr/t-regx/src/TRegx/CleanRegex/Internal/Delimiter/Delimiterer.php on line 26
I thin the pattern should be ok, because i copied it from a python script, which use the same pattern:
macPattern = re.compile("^(000413[0-9A-F]{6})|(00087[bB][0-9A-F]{6})$")
I know that fails exist, but i like the way with the ! more ;-) Perhaps i'm to old school for this.

For pattern "^(000413[0-9A-F]{6})|(00087[bB][0-9A-F]{6})$", you should go Pattern::of(), because it doesn't have delimiters.
Your earlier example, "/^000413/i" does have delimiters, so it should use Pattern::pcre().
Try:
private $_macPattern = "^(000413[0-9A-F]{6})|(00087[bB][0-9A-F]{6})$";
...
if (!Pattern::of($this->_macPattern)->test($mac))

and
if (!Pattern::pcre("/^000413/i")->test($mac))

Hope I helped :)

But you do bring an interesting point, a more proper exception should be raised for such usecase.

This is related to: https://github.com/T-Regx/T-Regx/issues/55

Thanks. It works now :) After i changed some parts to of and some to pcre.

Nice, good to know!
I'm closing this issue now, but please feel free to ask/contact me with anything! :D


metabase: 0.48.4 -> 0.48.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/metabase/versions.
meta.description for metabase is: The easy, open source way for everyone in your company to ask questions and learn from data
meta.homepage for metabase is: https://metabase.com
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.48.5 in filename of file in /nix/store/1pkhii6dqb3m0x0br8s09jgd3clmcbha-metabase-0.48.5

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
metabase

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1pkhii6dqb3m0x0br8s09jgd3clmcbha-metabase-0.48.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A metabase https://github.com/r-ryantm/nixpkgs/archive/abea1cbd9da62eab2d136137097b794ad9b0e2e9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/abea1cbd9da62eab2d136137097b794ad9b0e2e9#metabase

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1pkhii6dqb3m0x0br8s09jgd3clmcbha-metabase-0.48.5
ls -la /nix/store/1pkhii6dqb3m0x0br8s09jgd3clmcbha-metabase-0.48.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

metabase

Maintainer pings
cc @schneefux @thoughtpolice @mmahut for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/metabase/versions.
meta.description for metabase is: The easy, open source way for everyone in your company to ask questions and learn from data
meta.homepage for metabase is: https://metabase.com
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.48.6 in filename of file in /nix/store/zb79jw1axsd57xxgbrzm460g5w58800b-metabase-0.48.6

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
metabase

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zb79jw1axsd57xxgbrzm460g5w58800b-metabase-0.48.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A metabase https://github.com/r-ryantm/nixpkgs/archive/0e4d42d094045ba04531b00e80fbb43f8f990d77.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0e4d42d094045ba04531b00e80fbb43f8f990d77#metabase

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zb79jw1axsd57xxgbrzm460g5w58800b-metabase-0.48.6
ls -la /nix/store/zb79jw1axsd57xxgbrzm460g5w58800b-metabase-0.48.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

metabase

Maintainer pings
cc @schneefux @thoughtpolice @mmahut for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/metabase/versions.
meta.description for metabase is: The easy, open source way for everyone in your company to ask questions and learn from data
meta.homepage for metabase is: https://metabase.com
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.48.7 in filename of file in /nix/store/gzhhjsmqpg8hphf56qbxizbvar3lnyaz-metabase-0.48.7

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
metabase

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gzhhjsmqpg8hphf56qbxizbvar3lnyaz-metabase-0.48.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A metabase https://github.com/r-ryantm/nixpkgs/archive/609fa7d249cbeb6082747807a31a69e85e8dd983.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/609fa7d249cbeb6082747807a31a69e85e8dd983#metabase

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gzhhjsmqpg8hphf56qbxizbvar3lnyaz-metabase-0.48.7
ls -la /nix/store/gzhhjsmqpg8hphf56qbxizbvar3lnyaz-metabase-0.48.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

metabase

Maintainer pings
cc @schneefux @thoughtpolice @mmahut for testing.


Limit-Rater: Waiting because the rate limit was exceeded

Bug Report
Hello guys!
Im getting this error since a 2 days ago: twurple:api:rate-limiter WARNING Waiting for 59512 ms because the rate limit was  exceeded.
I was testing a function that looped over the users from a team (about 40 users), and then would check if they were online. At one moment, it went into a loop and i started receiving status 429 - Too Many Requests. I dropped the site and fixed the code, but since then i wasn't able anymore to do any requests.
I'm using the API on a NextJS website hosted on Vercel.
How can i solve that?
Code
async function getTeam() {
    try {
	const team = await apiClient.teams.getTeamByName(teamName);

	const users = await team?.getUserRelations();
	if (!users) return null;

	const allStreams = await Promise.all(
		users.map(async (user) => {
			return await (await user.getUser()).getStream();
		}),
	);
	const online = allStreams?.filter((stream) => !!stream);

	const rawTeam = team ? getRawData(team) : null;
	const rawOnline = online.map((stream) => {
		if (!stream) return null;

		const rawStream = getRawData(stream);
		rawStream.thumbnail_url = stream.getThumbnailUrl(384, 216);

		return rawStream;
	});

	return { team: rawTeam, online: rawOnline };
    } catch (err) {
	console.log({ err });
	return null;
    }
}

Expected behavior
To be able to request API again.
Actual Behavior
I get the error above as soon as I load the site, and am not able to do any requests.
Environment

Version: 5.0.18
Node version: 16.14.0
Operating system: Mac, Win

You're doing 81 requests every time this function is called. If you're running it more than 9 times a minute, that's the rate limit. It will apply across all people that visit the site. The client will wait until the rate limit resets for you to be able to make requests again.
Also, why did you move your question away from Discord? This issue tracker is not the place for usage questions.


adafruit_io and cleaning up the dependencies (no longer depending on circuitpython)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.444%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
96

Relevant Lines:
180

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.444%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
96

Relevant Lines:
180

💛  - Coveralls


add app.context.root variable for maven projects

@rdebusscher this is the fix for the build break.

@rdebusscher can you merge into your branch and kick off the build again?

moved commit to PR https://github.com/eclipse/microprofile-starter/pull/385/commits/2d84607f5ae4aea5536008a885a6e0e6623f6874


From now on, Flutter using a third-party library is a great pain to me

When I want to use some third party SDK into my flutter project，I met a problem that I can't across！
such as Tencent IMSDK, they provides both Android and IOS version。

as you know , I am not familiar with IOS development，so ,if I want to use the SDK, I count only able to encapsulate the android part, SO I HAVE TO  look for a person who skill at IOS and Willing to help me encapsulate the IOS part, But also he has time, etc。

Tencent IMSDK offer us lots of functions ,most of the function is useful to me ,so if I  encapsulate all the funciton into method_channel ,it is really a boring wok,so I think method channel is not a friendly way to use third party,

Would you provide use some more friendly way to use third-party libraries in future features？

Platform Channel feature is the very elegant way to deal with the matter of integrating third-party platform-specific library. Flutter is just a 'client' dedicating for UI render and living on the 'host' Android or iOS system.

https://github.com/flutter/flutter/issues/7053 might make it easier in some cases if it will be implemented.

I'm sure the Flutter team is aware that this should be made easier.
I think this issue is to broad though and not actionable and I am going to close it.
If you have more concrete issues that you think need to be fixed or improved, please create new issues.
Thank your for your contribution.


An Improve of the demo.html page

Description
I'm so excited to contribute to this project
Fixes #243
I added basic styling to the demo.html page. I also changed home.html to Index.html, and added the logo as the favicon
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code

Reviewer: Vinit Shahdeo

@vinitshahdeo

@enyichiaagu We are not accepting any changes to the master branch. Please make contributions as per the instructions in the readme:

If you're interested in contributing for documentation, please check out feature/documentation branch.

If you're interested in contributing for backend, please check out the following branch according to the tech stack:

Django: feature/backend-django

Node.js: feature/backend-node

If you're interested in contributing for frontend, please check out feature/frontend branch.


Student ID Card: Implement Barcode Generator

Use codabar barcode type

Barcode generator demo available on branch demo/barcode-builder

Ready for testing on branch student-id-card

This work has been completed, closing.


Spanish translations for Build an App without Using any Code with Microsoft Power Platform

This issue is for the short workshop on Build an App without Using any Code with Microsoft Power Platform
 being translated into Spanish
The structure of the translation should follow other translations like https://github.com/microsoft/workshop-library/tree/main/full/intro-nlp-tensorflow/translations

thanks to @aleepsy for taking this one :D

Hello @abrilurena can you review please the Pull Request?
Greetings! :D


Sketch necessary changes to support Arbitrary

Obviously this needs to move upstream to xdrgen (I will post a version of the minimal change needed there too) but this is a sketch of what support for Arbitrary looks like. Very straightforward -- the only question I think I have is whether @leighmcculloch you'd like it to be cfg'ed behind another feature or not. Argument for feature-cfg'ing is that obviously "it's more code" people might not want to compile; argument against is that "every feature makes a larger powerset".

I commented on https://github.com/stellar/xdrgen/pull/127, let's discuss there.

LGTM!


fix: escape import.meta.url passed to esbuild

Closes #473
When path had a single quote it was breaking the path passed to esbuild.
Added passing tests.
Locally using node from nvmrc there were 3 tests not passing.
But passing in node v18.15.0

:tada: This issue has been resolved in v4.7.1
If you appreciate this project, please consider supporting this project by sponsoring :heart: :pray:


Fix SelectedItemsChanged event arguments in SelectingItemsControl

What does the pull request do?
Corrects the event arguments for replacing a selected item in SelectingItemsControl.
What is the current behavior?
The arguments for the SelectedItemsChanged event are inverted.
What is the updated/expected behavior with this PR?
Sets the arguments as expected.

Checklist:

[x] Added unit tests

Idk if this should be added to the breaking changes.

I haven't found any issues referencing this bug, so it's unlikely anyone quietly assumed this will remain broken forever. I'd say it's more likely no one used this feature until now.

Wow thats a good spot! @jmacato should we get this into 0.7?

@danwalmsley I do think this is a critical bug fix that needs to be included with the release
@WojciechKrysiak hmm better be safe and let's add it there

@jmacato done: https://github.com/AvaloniaUI/Avalonia/wiki/Breaking-Changes


ControlsHelper.IsUnderlined Position

@flagbug is it possible to adjust where the underline on the TabControl is based on where the TabControl is located (i.e. top of the window vs. left side vs. right side).  I think for this to be a completely functional property, the "Underline" should transition with the control:
Examples:
If the TabControl is docked to the left of the screen, the underline should be on the right
If the TabControl is docked to the right of the screen, the underline should be on the left

I'll working on it