I met this error:

Hi, @jtoy @hunkim @Kongsea @DingKe @JayParks
I met this error:
sgiO2:image_captioning sgi$ python build_vocab.py
loading annotations into memory...
Traceback (most recent call last):
File "build_vocab.py", line 77, in
main(args)
File "build_vocab.py", line 59, in main
threshold=args.threshold)
File "build_vocab.py", line 31, in build_vocab
coco = COCO(json)
File "/Library/Python/2.7/site-packages/pycocotools/coco.py", line 84, in init
dataset = json.load(open(annotation_file, 'r'))
IOError: [Errno 2] No such file or directory: '/usr/share/mscoco/annotations/captions_train2014.json'
What's wrong with me?

Sorry for the late reply. This has been fixed in the current version.


Property 'createRequireFromPath' does not exist on type 'typeof Module'.

🐛 Bug Report
Prerequisites

[x] I'm using the latest version of Docusaurus.
[x] I have tried the npm run clear or yarn clear command.
[x] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[x] I have tried creating a repro with https://new.docusaurus.io
[x] I have read the console error message carefully (if applicable)

Description
When I run tsc, I get the following error:
node_modules/@docusaurus/theme-classic/src/index.ts:17:54 - error TS2339: Property 'createRequireFromPath' does not exist on type 'typeof Module'.

Have you read the [Contributing Guidelines on issues]
Yes
Steps to reproduce
$ git clone https://github.com/issueset/docusaurus-ts-theme-classic.git
$ cd docusaurus-ts-theme-classic
$ yarn install
$ yarn typecheck

Expected behavior
No error
Actual behavior
$ yarn typecheck
yarn run v1.22.5
$ tsc
node_modules/@docusaurus/theme-classic/src/index.ts:17:54 - error TS2339: Property 'createRequireFromPath' does not exist on type 'typeof Module'.

17 const createRequire = Module.createRequire || Module.createRequireFromPath;
                                                        ~~~~~~~~~~~~~~~~~~~~~

Found 1 error.

Your environment

Public source code: https://github.com/issueset/docusaurus-ts-theme-classic
Public site URL: N/A
Docusaurus version used: 2.0.0-beta.6
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0):  node v14.17.1
Operating system and version (e.g. Ubuntu 20.04.2 LTS): ubuntu 18.04

Reproducible demo
https://github.com/issueset/docusaurus-ts-theme-classic

Can reproduce here (node v16). It's related to your node version I believe—it's already deprecated in v12, and probably removed in v14. Since we have dropped support for v10, I guess we can just remove this fallback

Will be fixed in #5496.


Release tagging support

Feature request / Notes for potential PR
I'm thinking about automating the process of tagging a release and update git mirrors with something like hatch tag
to basically run the following.
$ git tag -s 0.1.1
$ git push gitlab 0.1.1
$ git push mirror 0.1.1

Hatch has been rewritten from scratch and now supports custom scripts, see https://ofek.dev/hatch/latest/config/environment/#scripts


Fix _isPointInArea for undefined point

Resolves #8676

Filename
Size
Change

dist/chart.js
85.1 kB
+3 B (0%)

dist/chart.min.js
60.6 kB
+1 B (0%)

dist/chunks/helpers.segment.js
18.9 kB
+2 B (0%)


ValueError when running on discovery

As reported by Austin we ran into another error on discovery (stderr, stdout).
The crux of it seems to be that the ANOVA is failing:
----  Messages for py:session9:default  ----
  Traceback (most recent call last):
* PythonTeX stderr - error on line 17 in "results.tex":
    File "<outputdir>/py_session9_default.py", line 429, in <module>
      print(pytex.formatter(boilerplate.anova(factor='C(Q("PA rel. Bregma [mm]"))')))
    File "/opt/src/opfvta/lib/boilerplate.py", line 143, in anova
      summary = sm.stats.anova_lm(ols, typ=typ, robust='hc3')
    File "/usr/lib/python3.10/site-packages/statsmodels/stats/anova.py", line 349, in anova_lm
      return anova_single(model, **kwargs)
    File "/usr/lib/python3.10/site-packages/statsmodels/stats/anova.py", line 83, in anova_single
      return anova3_lm_single(model, design_info, n_rows, test, pr_test,
    File "/usr/lib/python3.10/site-packages/statsmodels/stats/anova.py", line 252, in anova3_lm_single
      f = model.f_test(L12, cov_p=cov)
    File "/usr/lib/python3.10/site-packages/statsmodels/base/model.py", line 1765, in f_test
      res = self.wald_test(r_matrix, cov_p=cov_p, invcov=invcov, use_f=True, scalar=True)
    File "/usr/lib/python3.10/site-packages/statsmodels/base/model.py", line 1841, in wald_test
      LC = DesignInfo(names).linear_constraint(r_matrix)
    File "/usr/lib/python3.10/site-packages/patsy/design_info.py", line 536, in linear_constraint
      return linear_constraint(constraint_likes, self.column_names)
    File "/usr/lib/python3.10/site-packages/patsy/constraint.py", line 419, in linear_constraint
      return LinearConstraint(variable_names, coefs)
    File "/usr/lib/python3.10/site-packages/patsy/constraint.py", line 62, in __init__
      raise ValueError("must have at least one row in constraint matrix")
  ValueError: must have at least one row in constraint matrix

It's reported via TeX, but this is in the end a Python error, caused by either:

Missing data on account of quiet preprocessing errors
Updates in the statsmodels/patsy packages.

Since we pin the versions, I'm pretty sure it's (1), but I'll need to meet with @asmacdo again and check.

@asmacdo if you could check the lengths of our stats summary files on discovery:
[dark]~/docsrc/opfvta ❱ for i in data/*csv; do wc -l ${i}; done
18 data/features_structural.csv
79 data/functional_significance.csv
79 data/functional_t.csv
34 data/groups.csv
10 data/implant_coordinates_block.csv
10 data/implant_coordinates.csv
10 data/implant_coordinates_phasic.csv

That would give us a good indicator whether data was dropped on discovery. If your numbers are larger, that just means my last local run dropped some data.

This was fixed way back


Question on input queries and contigs.

Hi Linxing,
Thank you for this excellent paper and tool! I have some questions about the input of COBRA:

Now I'm using spades to assembly with parameter --meta resulting in contigs.fasta and scaffolds.fasta. May I use the scaffolds.fasta file as --fasta FASTA input, or only contigs.fasta` could be used?
Shall I use virues identification softwares (e.g. VirSorter, VirFinder, VIBRANT), to identify viral contigs before running cobra to gain -q query ? If so, how should I set the parameter min-length in virus identification softwares? If not, how should I gain query input?

Best regards,
Alena

Hi Alena,
Thank you for your questions.

for input, both contigs and scaffolds are fine, the queries should be from the corresponding set, though.
there are two ways, 1) you can use contigs/scaffolds >= 5000 kbp (for example) as queries for analyses, then perform viral prediction, or 2) predict viral contigs/scaffold first and then use viral contigs/scaffolds as queries.

I hope this helps. Please don't hesitate to ask more if my answers are unclear.
Best,
LINXING


Add Tech Updates plugin to market place

Hey Please look into this plugin :

A tech updates plugin will deliver most recent technology and other news from across the world.
Based on the user configurations news feed will be displayed.

@awanlin changes done please review

Getting much closer, thanks!
The README content on NPM doesn't match the latest version from your repo: https://www.npmjs.com/package/@techupdate/plugin-tech-updates. Can you also make sure that you have a link to the source repo in your NPM package? This allows Adopters to validate the lineage of the package for security reasons.

@awanlin Updated both repo and npm please review
npm : https://www.npmjs.com/package/@newsupdates/plugin-tech-updates
repo: https://github.com/AmbrishRamachandiran/tech-updates
added repo link at the bottom of readme

closing this as ran into issue with the packaging & build

@awanlin reopened it for your review

@awanlin take a look please , commenting for prevent stale

Approving for content, but I have a question. This is saying that infosys is the author of the plugin, but it's in a @newsupdates namespace which seems to be a one-off, and you have the source in your personal repo instead of under https://github.com/Infosys where their other OSS efforts are. Care to explain what's going on there?

Yes make sense ! iam trying to find out the process to publish under Infosys namespace and github will revert once the process is completed for now closing it.


Add connecting title to spinner for Connection dialog

Fixes #9410
I considered adding a default "Loading" title if none was specified but I think I prefer that this be an opt-in thing since loading might not make sense in all scenarios.
I also considered doing the suggestion of having a timeout for the announce so we only announce if some amount of time has passed but that seemed like overkill - and I'd actually rather it be consistent in whether it announces something or not.

I'm going to merge this in since I think that's separate enough to warrant a separate issue/PR.
So my opinion on that is that we shouldn't necessarily announce "connected". The point of voiceover is to provide the user a speech explanation of what's happening on screen - and in the "connected" case it's not like we pop up a dialog saying "Connected!" or anything.
What does happen though is the server tree node is expanded and changed to the connected status. So what I think would be better is if we make sure that when the dialog is closed that the user is informed that the focus has switched to the server tree view and that the node status was changed and expanded.
Does that seem reasonable to you?
I tested that and it currently looks like all we're doing is announcing that the focus switched to the tree view so we might need to do some extra work there.


Fix markdown links in CHANGELOG.md

(text)[link] -> [text](link)
Links are formatted with incorrect markup in all releases.

It's been corrected in https://github.com/obervinov/_templates/pull/57


Add new feature clear-python-folder

autorest has clear-output-folder to avoid zombie code. But it is not flexible for python codegen. Since README.md is in root package folder but if set clear-output-folder, it will be deleted every time. To avoid the inconvenience, we have to set output-folder like:
...
root-folder: ...
output-folder: $(root-folder)/azure/dpg/module
namespace: azure.dpg.module
no-namespace-folders: true
clear-output-folder: true

The up configuration will bring troublesome for --package-mode since we can't generate README.md directly in output-folder.
In conclusion, we need new feature clear-python-folder to tell autorest.python to clear specific folder without deleting README.md. Customers can input folder relative to output folder like:
...
root-folder: ...
output-folder: $(root-folder)
namespace: azure.dpg.module
clear-python-folder: azure/dpg/module

nit: we need to avoid deleting _patch.py in subfolder
There are two main advantages:
(1) avoid clear-output-folder delete those _patch.py in subfolder
(2) make the configuration cleaner and united (we don't need no-namespace-folder anymore)

@msyyc talked with @lmazuel and we like this direction, but we want to make the design more generic (so other languages can use as well), and move the clearing to have autorest core handle it. This is because we're not supposed to mess with disk in the inidivial language generators, autorest core has to handle that. We're thinking of adding a flag that's like clean-output-folders or somethign like that that takes in a list of output folder directories, then cleans out those directories. This way it's not python specific, and autorest handles everything. Thanks!

Hi @iscai-msft That makes sense because JS also needs the similar flag. For python, the generic flag needs to keep _patch.py to avoid deleting the customized code of customers.

Sounds good! We will continue using the same code we do for keeping version files and patch files in the python generator to make sure those files stay if we want them to, so not something that autorest needs to do with their implementation. I'm going to transfer this issue to the main autorest repo


Jesse: Watch howly.com

Jesse requests the watch of the watch_keyword howly\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

howly\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


No Popup for install in Mobile

I am unable to get a popup to install app in mobile browser.
can you fix or share the code of implementation of PWA for mobile app.

do you want to work on this issue? @rapidtrader

I am unable to get a popup to install app in mobile browser.
can you fix or share the code of implementation of PWA for mobile app.

Can you explain or provide screenshots ?

Since there haven't been any updates, we can move forward with closing this issue.


Allow Option::deserialize to fail.

This allows the changes to work with older versions of agones.

This doesn't seem to actually fix it, so closing.


Strange characters when typing a after a single quotes

VS Code Version: 1.66.2
OS Version: Win 10

Steps to Reproduce:
When I type char a (or c, y, i) immediately after a quotation mark , the quotation marks are not automatically completed. but there will be strange characters áä ç  áä ç ýíá . How to disable such characters ？

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!


Validate the content of API state parameter

This adds a whitelist check to state values ingested by the API.
It also adds a states fixture for standalone and testing use.
Review
@chosak @willbarton

Coverage decreased (-0.001%) to 99.419% when pulling e83506cd6043b6e738064ba2f288832e93a1c959 on higs4281:master into acc18ffe41f8d66828ae02e7ffbcd8dca305ff23 on cfpb:master.

Coverage decreased (-0.001%) to 99.419% when pulling ec1e99cd69df57ab56241a422827f8b38bfdfdb3 on higs4281:master into acc18ffe41f8d66828ae02e7ffbcd8dca305ff23 on cfpb:master.

@chosak @willbarton @lfatty
Finally made travis happy.

Coverage decreased (-0.001%) to 99.419% when pulling f406bca30009357e321487b2c0942f27cc96d50e on higs4281:master into acc18ffe41f8d66828ae02e7ffbcd8dca305ff23 on cfpb:master.

Coverage decreased (-0.001%) to 99.419% when pulling a70dc9220748d138ee913cb0b79843bbdbe7bb90 on higs4281:master into acc18ffe41f8d66828ae02e7ffbcd8dca305ff23 on cfpb:master.


Make runtime dependencies handling more consistent

Previously runtime dependencies were stored in the tab but these values were only used by brew uninstall. Confusingly this would result in various commands (e.g. brew leaves, brew missing, brew doctor, brew uses --installed) contradicting brew uninstall in what the dependencies are for a formula.
This refactoring means that Formula#runtime_dependencies will now look at the formula's tab if possible (and if not specifically requested not to). After this, Formula#runtime_dependencies has been able to be used in more places so all the above commands can be consistent.
While I was here a few other tweaks have been made:

diagnostic and leaves didn't need changes but, while looking there, I was able to clean them up a bit for more readable and simple code
Tab now defaults runtime_dependencies to nil rather than an empty array. This is useful in differentiating between runtime_dependencies being not present in a Tab vs. there being no runtime dependencies. The nil case already needed handled because of returning nil for old, invalid runtime_dependencies anyway.

It seems off to me that asking a formula for its runtime dependencies would cause it to check its tab, because that isn't information about the formula, but about a specific installation of the formula (ie a keg). This ends up with us having to introduce options to specify whether we actually mean a formula itself, or its installed keg, which continues to reduce the separation of concerns and complicate the code with conditionals and options.

I agree with this in principle but not in practice, I think. That said: yes, this could potentially be refactored so that every time you want Formula#runtime_dependencies to return the value from the Tab you actually want to query the relevant Keg but this ends up meaning that all the callers that are currently already asking a formula what the dependencies are now need to deal with a Keg instead.

Something worth thinking about anyway, I think. I'm not against this change – in fact I think it would be good for usability. I vaguely remember bringing up this inconsistency a while ago, and the consensus at the time seemed to be that we didn't want to change the behaviour of leaves, uses etc, but if that's changed that's more than fine by me.

Cool thanks 👍

this ends up meaning that all the callers that are currently already asking a formula what the dependencies are now need to deal with a Keg instead.

I don't think that would be a bad thing, although the effort to get there isn't necessarily worth it.


Autopilot notebook Direct Marketing with Amazon SageMaker Autopilot fails to run in the console

When run in the console:
https://github.com/awslabs/amazon-sagemaker-examples/blob/master/autopilot/sagemaker_autopilot_direct_marketing.ipynb
fails to run as it cannot upload the data from the location provided.
Error message:
Failed to upload data: "S3UploadFailedError: Failed to upload data/train.csv to qqnl-autopilot/reuse-autopilot-blog/training_data/train.csv: An error occurred (AccessDenied) when calling the PutObject operation: Access Denied"

The upload issue is now fixed. This now runs in both Studio and Console.


Add support for series upgrade

We can't actually pause the service because the series upgrade hooks run on the subordinates before the principal so doing so could interfere with the pod drain process. So instead, we just set a status to let the Juju admin know that it's ok to proceed.
Part of https://bugs.launchpad.net/charm-canal/+bug/1869944

Can you also replace the calls to status_set in calico.py and flannel.py? (this charm is a mess, sorry)

LGTM


Deploy to Heroku

Deployment on Heroku was throwing many errors.
The beta branch got deployed on the server successfully but it did not run, so there was only a blank app on the server.
Then, observing the deadline, I deployed the beta branch on NCSU VCL and the app is up and running.
Link to deployment: http://<IP_ADDRESS>:8080/


differentiate detween device and device_index, platform and platform_index

in cuda.py and in opencl.py.

I'm not sure what you mean, could you explain a bit?

Sure. What I propose is to rename the argument device here to device_index to avoid confusion with the variable dev that your get back when you do for example, this.
And similar for platform / platform_index.

Ah now I see. I know these variables are just indices, but I chose to stick with the naming that is common in CUDA and OpenCL.
CUDA Runtime:
http://docs.nvidia.com/cuda/cuda-runtime-api/group__CUDART__DEVICE.html#group__CUDART__DEVICE_1g159587909ffa0791bbe4b40187a4c6bb
OpenCL specification (see clCreateContext):
https://www.khronos.org/registry/OpenCL/sdk/1.2/docs/man/xhtml/
CUDA calls this a 'device' and OpenCL calls it a 'device_id'. In PyCuda it's called 'CUDA_DEVICE' and the PyOpenCL documentations just calls it 'device' as well. I just went for 'device' and 'platform' for the user interface, because this way it will be clear to CUDA and OpenCL programmers what we mean by that. We could of course use a different name for these things internally, but I'm not sure that that is a good idea.
I'm also not sure that there will be much confusion of the two. 'device' and 'platform' are only used for a very brief moment to instantiate the device function interface. From that moment onward, only the device function interface is used.

I think CUDA is doing it wrong when they refer to a device when really, they're talking about a device_index. Blasphemy, I know, but OpenCL's use of a device_id indicates I'm right.
Your argument that both device and platform are used only briefly is true but besides the point IMHO.
So, how to resolve this... it seems that you (and me) have given the issue ample thought. We do not share the same opinion. However, you are in charge of governing the project. So, keep device and platform and  close the issue?

I have thought about this some more, but since we are doing GPU programming in Python and both PyCuda and PyOpenCL are using just 'device' and 'platform' I feel it would be wrong to diverge from what seems to be the common practice.


remove deprecated and unused import

strange. Travis does not pull in bytes 0.4.7 which introduces the deprecation warning??

Likely due to the fact that travis caches crates. Try changing bytes in cargo.toml to 0.4.7 and recompiling

Great. Tried just bumping the version number, but now it conflicts w/ other crates...

we may need to wait for a day or so to let the caches invalide?

No, it just needed to have cargo update run against it. Ignore what I said about bumping the version number, wasn't thinking clearly. It should build now.

yes, all green now

thanks, merged.


Deleting branches

I strongly suggest deleting the branches: Baobab, Coconut, dewberries

Reasons:

main reason: one of the OpenSSF Best Practices "gold" badge requirements: "The project MUST have FLOSS automated test suite(s) that provide at least 80% branch coverage". Writing tests for old branches at the moment makes no sense and resources
OpenSSF Score Card requirement for branch protection (needs to be additionally configured) #480
We still haven't maintained branches (bug fixes, haven't received external requests for any branches)
Now we use a linear development strategy
Branches proposed for deletion are associated with tags

I hope we will increase the test coverage of the current code to 90%, and in the future, if necessary, we will be able to use branches for version support (considering that the maturity of our product is growing)
I hope for a positive result. I can delete myself.

+1

I second this proposal since developers can find tags related to release.

@tdrozdovsky What about the docker image distributed from DockerHub? Removing it as well? Hope that helps me cast my vote here. 🙏

@tdrozdovsky What about the docker image distributed from DockerHub? Removing it as well? Hope that helps me cast my vote here. 🙏

Deleting branches does not affect DockerHub

@tdrozdovsky What about the docker image distributed from DockerHub? Removing it as well? Hope that helps me cast my vote here. 🙏

Deleting branches does not affect DockerHub

@tdrozdovsky My question is - do we need to also delete the docker images of the previous releases from DockerHub? Thank you in advance. 😁

Since the Docker images are associated with tags (semantic versions), nothing needs to be deleted. Therefore, I wrote that there will be no impact on the Dockerhub

+1


How to display warning dialog when - in an edit dialog - a checkbox is being checked by the user

Good evening JaiQ,
John Ranger here with another question :-)
I have a Dialog with a Checkbox, which - when checked  and then the update button on the Dialog is clicked - will as a consequence overwrite some values on a possibly large number of records in another table (reseting These values to Default values) and then syncing These Changes to System Center Service Manager.
As this is a potentially dangerous action, I want to warn and clearly inform the user with a Special Dialog about the consequences of what happpens when he/she checks this Checkbox.

How would I add an Event (jquery Checked if I understand correctly) to the particular Checkbox field?
How would I create a similar Dialog like serenity has when an underlying SQL error is displayed?
How would I "attach" the displaying of this Dialog to the above Event?

Thank you for your Support
and with Kind regards,
John

form.TheCheck.Element.Click = e => { ... }

Q.Confirm is probably what you are looking for.

Or Q.Alert if you just want to show message.

Hi JaiQ,
Many thanks for guiding me into the right direction. Please keep up your excellent work!
With Kind regards,
John

For the benefit of other Readers - here the code that worked for me (replace Value1, Value2, Value3 and xxx with real values from your project):
do this in the xyzDialog.cs:
public xyzDialog()
       {
            form = new xyzForm(this.IdPrefix);
            //...

            form.UpdateInitialValuesOnAllAssociatedClients.Change(e =>
                {
                    if (form.UpdateInitialValuesOnAllAssociatedClients.Value == true)
                    {
                        var opt = new Serenity.AlertOptions();
                        Q.Warning("Warning! Checking this checkbox and click on update will reset Value1, Value2 and Value3 on xxx assets. These assets may already be in use and have these values set to their individual requirements.\n\nDo you really intend to do that?", opt);
                    }
                });
      }


New Game: Chess Chouette

Inspired by backgammon chouette, a group of players rotate in and out of a single game, betting on the outcome.
Maybe you could buy out the side that you think is going to win, and that lets you swap in. Some kind of auction mechanism, maybe with a tithe to the pot?

Beetter fit if there's an element of chance? Deck builder and war? Strengthen deck after lost battle? More deck improvement when luck is unkind.


"import type { X }" with exported value with same name gives "Individual declarations in merged declaration 'X' must be all exported or all local."

Bug Report
🔎 Search Terms

Individual declarations in merged declaration 'X' must be all exported or all local.
import type

🕗 Version & Regression Information

This is the behavior in every version I tried, the latest being 4.8.3, and I reviewed the FAQ for entries.

⏯ Playground Link
cannot import other files in playground
💻 Code
import type { x } from './foo';

export const x = 7

🙁 Actual behavior
Running tsc gives:
Individual declarations in merged declaration 'x' must be all exported or all local.

🙂 Expected behavior
No error.

The error is exactly describing the situation that's happening.
You can write
import type { x } from './foo';

const x = 7

export { x };

Thanks, that works indeed!
I suppose I don't know enough about JavaScript module syntax to see the difference :P export { x } is not a declaration?

Actually, it doesn't work. There is no type error in the exporting file, but when I save what you posted to bar.ts, and in another file:
import { x } from './bar';
console.log(bar);

I get:
'x' cannot be used as a value because it was imported using 'import type'

@mb21 See https://github.com/microsoft/TypeScript/issues/40583#issuecomment-693542271

Thanks! This works indeed:
type x = import("./foo").x;
export const x = 7;


Add per-repo config and prepare for org-wide webhook

This PR contains multiple refactors to allow other teams to easily add triagebot on their own repositories, and to reduce the maintenance overhead on our end.
Each repository now has its own configuration file, triagebot.toml, which lives at the root of the master branch that repository, and it's fetched by triagebot at runtime whenever needed (and cached for 2 minutes). If a repository doesn't have the configuration file and an user tries to execute a valid command an error will be shown in the comments instead.
Each of the handlers has its own section in the configuration file, and triagebot will call the handler only if the configuration section is present, allowing repository owners to toggle the handlers they want on their end. As with disabled repos, if an user tries to use a disabled handler an error will be shown.
The way handlers are registered in the code changed: instead of using dynamic dispatch they have to be registered in a macro in handlers.rs (which replaces the mod foo;). This way it's possible to automatically disable not configured handlers, and associated types can be used in the trait.
The trait also changed, with handle_event being split into two methods (parse_input and handle_input). This way the input is also parsed when the handler is disabled, allowing the code to show the disabled handler error message only when a valid command was actually present in the comment.
Finally I did some bits of cleanup in the code, and renamed the label handler in relabel since that's what it actually does.
r? @Mark-Simulacrum

Before deploying this PR, the following triagebot.toml must be landed in the rustc repo:
[relabel]
allow-unauthenticated = [
    "C-*", "A-*", "E-*", "NLL-*", "O-*", "S-*", "T-*", "WG-*",
    # I-* without I-nominated
    "I-compilemem", "I-compiletime", "I-crash", "I-hang", "I-ICE", "I-slow",
]

This looks good to me (let's merge the config to rust-lang rust as soon as possible and then merge this).


[BUG] SKMatrixConvolutionTileMode.Clamp not working as expected

I am trying to implement various matrix convolution filters in my mobile application, but I get some strange borders around the filtered image. Here is the code I use to generate a sharpened version of an image, for example:
private static SKImage SharpenImage(SKImage image)
{
    var kernel = new float[]
    {
        1.0f,  4.0f,   6.0f,  4.0f, 1.0f,
        4.0f, 16.0f,  24.0f, 16.0f, 4.0f,
        6.0f, 24.0f,-476.0f, 24.0f, 6.0f,
        4.0f, 16.0f,  24.0f, 16.0f, 4.0f,
        1.0f,  4.0f,   6.0f,  4.0f, 1.0f
    };
    var gain = -1.0f / 256.0f;
    var bias = 0.0f;
    var size = new SKSizeI(5, 5);
    var offset = new SKPointI(2, 2);

    using (var bitmap = new SKBitmap(image.Width, image.Height))
    using (var canvas = new SKCanvas(bitmap))
    using (var paint = new SKPaint())
    using (var filter = SKImageFilter.CreateMatrixConvolution(size, kernel,
        gain, bias, offset, SKMatrixConvolutionTileMode.Clamp, true))
    {
        paint.ImageFilter = filter;

        canvas.Clear();
        canvas.DrawImage(image, SKPoint.Empty, paint);

        return SKImage.FromBitmap(bitmap);
    }
}

The code for the blur filter is very similar. Here are some screenshots of the original image and its blurred and sharpened version:
Original image:

Blurred image:

Sharpened image:

As you can see, there are noticeable borders around the filtered images.
I am passing SKMatrixConvolutionTileMode.Clamp when creating the SKImageFilter. To my understanding, SKMatrixConvolutionTileMode.Clamp is supposed to clamp to image edge's pixels, thus eliminating any such artifacts. I have tested with the other modes as well, but I cannot see any difference between SKMatrixConvolutionTileMode.Clamp and SKMatrixConvolutionTileMode.ClampToBlack - both modes seem to produce the same result. Only the SKMatrixConvolutionTileMode.Repeat mode makes any difference, but it is not doing what I need for my filters.
I have also tested the built-in blur filter, i.e. SKImageFilter.CreateBlur(sigmaX, sigmaY), but it seems to suffer from the same problem as well, with no option to pass SKMatrixConvolutionTileMode upon creation.
I am not certain whether this is a SkiaSharp problem or a Skia problem, so I am posting it here to cover all possibilities.
Edit: I forgot to mention that I am creating a Xamarin.Forms mobile application for Android and iOS. I am using the latest SkiaSharp NuGet package: 1.68.0. The problem is reproducible on both platforms.

I have also noticed something even more strange. If I try to draw the image directly to the SKCanvasView or SKGLView and apply the filter on the fly, then nothing happens - the image appears unfiltered, as if the SKImageFilter specified to the current SKPaint is simply ignored. Here is my test paint code:
private void OnPaintSurface(object sender, SKPaintSurfaceEventArgs eventArgs)
{
    var canvas = eventArgs.Surface.Canvas;
    var width = eventArgs.Info.Width;
    var height = eventArgs.Info.Height;
    var length = Math.Min(width, height);
    var left = (width - length) / 2;
    var top = (height - length) / 2;
    var right = left + length;
    var bottom = top + length;
    var rect = new SKRectI(left, top, right, bottom);
    var kernel = new float[]
    {
        1.0f,  4.0f,   6.0f,  4.0f, 1.0f,
        4.0f, 16.0f,  24.0f, 16.0f, 4.0f,
        6.0f, 24.0f,-476.0f, 24.0f, 6.0f,
        4.0f, 16.0f,  24.0f, 16.0f, 4.0f,
        1.0f,  4.0f,   6.0f,  4.0f, 1.0f
    };
    var gain = -1.0f / 256.0f;
    var bias = 0.0f;
    var size = new SKSizeI(5, 5);
    var offset = new SKPointI(2, 2);

    using (var paint = new SKPaint())
    using (var filter = SKImageFilter.CreateMatrixConvolution(size, kernel,
        gain, bias, offset, SKMatrixConvolutionTileMode.Clamp, true))
    {
        paint.ImageFilter = filter;

        canvas.Clear();
        canvas.DrawImage(this.image, rect, paint);
    }
}

Being able to create a blur that clamps edge pixels is also something I've needed.


more fixes from dogfooding

Issues
Here are some more changes from dogfooding the faktory style runner

The linter picked something up but otherwise looks alright


[composer] Newly added if/while in design view are cannot be deleted from design

Description:
As $subject,

Open a bal file  if_else.bal or while.bal
Go to edit mode and add one more if statement from graphical view => added
Save and goto edit mode and try to delete

Affected Versions:
0.970.0
OS, DB, other environment details and versions:
Windows 10
Chrome 66.0.3

fixed with https://github.com/ballerina-platform/ballerina-lang/pull/9299


Prevent older versions of Rubocop from breaking LSP

Motivation
Closes #286
Implementation

Successfully replicated the error with rubocop versions less than 1.4.0.
When testing, I noticed that rubocop-shopify (~> 2.9) needs rubocop to be ~> 1.33 so I went ahead and updated it in the gemfile for development.
Added in logic to rubocop_runner so that the lsp would also run without rubocop if the version is less than 1.4.0

Tests

Looked into writing a regression test to catch the error, but it ended up being difficult since it would involve running a test with a rubocop version that is different than the project's which meant the test would have to be written separately from the current rubocop testing.

Rebasing on the current main should fix the CI errors related to trailing commas.


Added database firewall rule feature.

@ahmetalpbalkan: Thanks for the review. Fixed all currently outstanding issues.

LGTM. As I reviewed this on mobile, will let @paulmey take a look and merge.

LGTM

Thanks @aznashwan !


recipe for differentiable versions K.max() and K.min()

feature suggestion:
K.abs() allows you to include a differentiable version of K.max() and K.min().
This is easy because, for scalars a and b, we have:
max(a, b) = .5*( a + b + |a - b |)
similarly,
min(a, b) = .5*( a + b - |a - b| )
Also, a differentiable switch on the sign of a scalar value b can be implemented as:
(1 + b/|b|) / 2     or (1 - b/|b|) / 2

K.max and K.min are already differentiable, aren't they?

They are not.

I mean the gradient is not strong and even with your proposition the gradient will be almost 0 everywhere, but if max and min were not differentiable, most activation functions wouldn't work.

I apologize.  It seems you are correct and you can use K.max() in the loss function, so it must be differentiable.   I was getting an error message that I cannot now reproduce, but the error message listed K.max as a possible cause of having a non-differentiable loss function (even though I was not using K.max).


[TF] Introduce callables.

Introduce callables: values that can be "called" like functions.
struct Adder {
    var base: Int
    call func(_ x: Int) -> Int {
        return base + x
    }
}
let add3 = Adder(base: 3)
add3(10) // 13

This is experimental functionality and highly subject to change:
the design will be updated based on feedback for SE-0253.

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow macOS

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

For the eventual final patch (not necessary in the 0.3 release) I think it would be better to model this as a normal FuncDecl with a special name. I don't think it is necessary to have a CallDecl node.

Yes, switching to a normal FuncDecl with a "callable" bit and special name is definitely the direction.

It'd be nice to change "call member" to "call function" or "call method" in diagnostics.

I believe this is already done, please let me know if you found places I missed.


Implement mentor dashboard - my mentees view

Description
As part of this issue, we need to create the mentor dashboard - my mentees view, which should closely match the provided mockup. This will provide the mentors with a way to view their mentees. Also this view includes the functionality of setting the mentor availability status.
Tasks

Set up the basic React components as required.
Implement the layout and design of the mentor dashboard - my mentees view,, following the provided mockup.
Integrate the necessary components and assets to achieve the desired functionality and visual appearance.
Ensure responsiveness and compatibility across different devices and screen sizes.

Mockup: https://www.figma.com/file/nehm2ff8aR7NkPerg39fK9/ScholarX-V2-|-Wireframes?type=design&node-id=1974-2309&mode=design&t=4rAK5DBPmyfRYE3Q-4

Note: You may want to mock the API refer to the API doc - Get my mentees and API doc - Update mentor availabiliy to see the relevant details.
Acceptance Criteria

The user interface closely resembles the provided mockup.
All required sections, elements, and content are present and displayed correctly.
The interface is responsive and works well on various devices and screen sizes.
The implementation follows best practices and coding standards.
Unit tests are written.

@anjula-sack I think it'll be much easier to work on if we divide up this issue even further. As I see it there are few components here that we can make separately and assembled on a view page.
Components

Mentee table
Tab switcher button row (for lack of a better term, I'm talking about those My mentee/Application and All/Approved/Rejected button rows)
Switch (If that's not already included in ant design)

View

My mentee view (Which is this issue, that we can get into after we've made those three components that should be in the view)

It'll be a much organised approach if we made them into different issues and worked on them separately. (And I can send more PRs to get more green dots :D)

Tab switcher button row and switch is available on antd, my bad 😄

Hi @Gravewalker666, Here's the updated wireframe. Will you be working on this or should I assign someone else?

@anjula-sack Can you please assign this task to me? I'll work on it.

Current progress of the MyMentee view

@udeesha-kularathne Any updates on this?


existence of cache file(.tern/) effects report output

Describe the bug
Output of tern differs whether there exist cache files(.tern/) or not.

debian_buster_img#.json : created by command
tern report -f json -i debian:buster -o debian_buster_img#.json
debian_buster_img_scancode#.json : created by command
tern report -f json -x scancode -i debian:buster -o debian_buster_img_scancode#.json
To Reproduce
Steps to reproduce the behavior:

Pull debian:buster
Run command tern report -f json -i debian:buster -o debian_buster_img1.json
Run command tern report -f json -i debian:buster -o debian_buster_img2.json
Remove cache rm -rf ~/.tern/
Run command tern report -f json -x scancode -i debian:buster -o debian_buster_img_scancode1.json
Run command tern report -f json -x scancode -i debian:buster -o debian_buster_img_scancode2.json
Run command tern report -f json -i debian:buster -o debian_buster_img3.json
Run command tern report -f json -x scancode -i debian:buster -o debian_buster_img_scancode3.json
Remove cache rm -rf ~/.tern/
Run command tern report -f json -i debian:buster -o debian_buster_img4.json
Remove cache rm -rf ~/.tern/
Run command tern report -f json -x scancode -i debian:buster -o debian_buster_img_scancode4.json

Error in terminal
no error occurred
Expected behavior
Same command need to provide same output
Environment you are running Tern on
Enter all that apply
Tern at commit 273e3c8cd8969df3dacc56c5d878d65378d8e4bf
Python 3.6.13
Docker version 19.03.13, build 4484c46d9d
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.7 LTS
Release:        16.04
Codename:       xenial

I first cleared the cache and then followed the Tern commands in order according to your directions.
Regular Tern run comparison:

debian_buster_img1.json and debian_buster_img2.json had no differences between them.
As expected,debian_buster_img1.json and debian_buster_img2.json differed from debian_buster_img3.json because the cache was populated with scancode data from the previous run (step 5 and 6) that would've been included additionally in debian_buster_img3.json. Same thing for debian_buster_img4 vs debian_buster_img3.
debian_buster_img4.json and debian_buster_img[1/2].json were the same file, however, the pkg_liceneses fields were not ordered lists so the diff did not come back clean. However, if you take a further look, they are reporting the same licenses.

FYI, Tern collects debian licenses using the debian-inspector package, which parses the copyright text to report licenses. Due to the parsing, there are oftentimes multiple licenses reported for debian packages whereas with other package managers there would only be one.

As expected, debian_buster_img3.json and debian_buster_img4.json differ as img3 contains scancode output (from steps 5 and 6).

Scancode files:

Due to the size of the file, I can't find specific differences in debian_buster_img_scancode1.json and debian_buster_img_scancode2.json -- Do you have any insight on if there's missing information between the two files here? I agree it's incorrect that the two would be different but in order to debug I need specific information to look for that's missing.
debian_buster_img_scancode2 and debian_buster_img_scancode3 are the same (both load from cache).
debian_buster_img_scancode1 and debian_buster_img_scancode4 are the same (both run with clean cache).

Things are mostly what I would expect except for the following case:

Running Tern with Scancode back to back is not producing the same document. The first document created with Scancode is almost double the size of the second which makes me think there is an issue loading from the cache with scancode.

By the way, tern -c will clear the cache for you instead of having to remove the cache file directly :)
I'll keep poking at this.

It's good to know the tern -c option! I've been deleting the temp directory :P
About the difference between debian_buster_imge_scancode1.json and debian_buster_imge_scancode2.json.
As you might know, report file with Scancode extension describes information for a file twice. One with detailed info, one without detailed info(e.g. checksum_type, extattrs, licenses and etc.)
debian_buster_imge_scancode1.json has both of them, but debian_buster_imge_scancode2.json only first one.(I suppose that's because why the second report is about half size of first report)
If you search for paths, you'll see what I mean.
For example (numbers are line numbers in pretty format)

"path": "usr/bin/shred"
debian_buster_imge_scancode1.json : 131734, 249256
debian_buster_imge_scancode2.json : 131734
"path": "var/log/apt/eipp.log.xz"
debian_buster_imge_scancode1.json : 18219 , 131770
debian_buster_imge_scancode2.json : 18219

(left is debian_buster_imge_scancode1.json and right is debian_buster_imge_scancode2.json)

Thanks @JustinWonjaePark for the clarification of differences. From what I see, Scancode is reporting the file and its metadata twice on the first run which is why the files are different. Tern then captures the file metadata only once in the cache and reports on it once when it loads from the cache. This is because Tern only stores one copy of a file in the cache when the name, path and checksum properties are the same -- which they are for the shred file in debian_buster_img_scancode1.json and debian_buster_img_scancode2.json. Using the shred example, I don't see any metadata for the shred file that is present in debian_buster_img_scancode1.json that is not present in debian_buster_img_scancode2.json, it's just not reported on twice because it's only loaded from the cache once.
I agree that Tern should not double report scancode data on a file in debian_buster_img_scancode1.json but don't actually see any missing metadata (which is good). Is there metadata in particular you're seeing missing that I'm not?

I agree with you @rnjudge. I've not seen missing metadata either.

I will start to look at a fix so a fresh scancode run doesn't report the same package twice. When I run just scancode without Tern I get only one reported instance of the usr/bin/shred file so this could be a Tern issue instead of coming from scancode.

@rnjudge I am glad that it has been fixed. Thanks!!


Reference Genome

How to run chloroExtractor while providing reference genome for assembly? I tried run it with Illumina paired end data it gave fasta file with more than one contigs. The length for those contigs is quite short from supposedly chloroplast length (about 20k).

Dear nsmt89,
Unfortunately, chloroExtractor does not support a reference based assembly, due to its underlying assembly spades. In general it would be possible to use another reference during the filter step, but the final assembly is limited by spades. Nevertheless, using an individual reference while filtering would avoid to throw away important read pairs . In case you want to try that we will provide you with an how-to . Just let us


[Snyk] Upgrade swr from 2.2.4 to 2.2.5

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade swr from 2.2.4 to 2.2.5.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2024-02-15.

Release notes

Package name: swr

2.2.5 - 2024-02-15Patches

types: isLoading typed as boolean when using fallbackData (#2866) by @ yjrhgvbn in #2875
fix: allow onErrorRetry on inactive tab without focus/reconnect revalidation by @ qkdreyer in #2848
feat: pass a function to the revalidate option in mutate by @ koba04 in #2862
fix: SWRConfiguration type by @ hulla-dev in #2882

Misc

build: use new bundle convention by @ huozhi in #2865
chore: update pnpm-lock.yaml by @ koba04 in #2874
chore: remove useless comment by @ kongmoumou in #2868
test: run pnpm test on CI by @ koba04 in #2872
fix: all act warnings by @ koba04 in #2861
Update bundler by @ huozhi in #2830

New Contributors

@ kongmoumou made their first contribution in #2868
@ yjrhgvbn made their first contribution in #2875
@ qkdreyer made their first contribution in #2848
@ hulla-dev made their first contribution in #2882

Full Changelog: v2.2.4...v2.2.5

2.2.4 - 2023-09-25Patches

Revert "Remove index.js suffix of use-sync-external-store/shim to support React Native" by @ huozhi in #2802

Full Changelog: v2.2.3...v2.2.4

    from swr GitHub release notes

Commit messages

Package name: swr

79445e4 2.2.5
744f692 fix: SWRConfiguration type (#2882)
3668c90 feat: pass a function to the revalidate option in mutate (#2862)
f306893 fix: allow onErrorRetry on inactive tab without focus/reconnect revalidation (#2848)
30cfa8c types: isLoading typed as boolean when using fallbackData (#2866) (#2875)
d5d8482 chore: remove useless comment (#2868)
b18781b chore: update pnpm-lock.yaml (#2874)
bf5363e build: use new bundle convention (#2865)
387a3ab test: run pnpm test on CI (#2872)
ef63a30 fix: all act warnings (#2861)
1d81109 Update bundler (#2830)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

duplicate


follow up the documentation improvements PR

better @repl usages
move errortypes.md into jetanalysis.md since the error references are specific to JET's default error analysis

/cc @jakobnissen

Codecov Report
Base: 89.95% // Head: 88.05% // Decreases project coverage by -1.89% :warning:

Coverage data is based on head (e2f576d) compared to base (f6f781d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #423      +/-   ##
==========================================
- Coverage   89.95%   88.05%   -1.90%
==========================================
  Files          10       10
  Lines        2637     2629       -8
==========================================
- Hits         2372     2315      -57
- Misses        265      314      +49

Impacted Files
Coverage Δ

src/JET.jl
73.90% <ø> (-0.61%)
:arrow_down:

src/abstractinterpret/typeinfer.jl
89.31% <0.00%> (-5.26%)
:arrow_down:

src/analyzers/jetanalyzer.jl
89.52% <0.00%> (-4.04%)
:arrow_down:

src/ui/print.jl
91.15% <0.00%> (-0.69%)
:arrow_down:

src/abstractinterpret/inferenceerrorreport.jl
89.32% <0.00%> (-0.40%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

move errortypes.md into jetanalysis.md since the error references are specific to JET's default error analysis

Maybe this "Error kinds and how to fix them" section is so useful that it should have its own page as before, but from technical point of view this listing is more correct (as the errors described in that section won't be reported by report_opt-analysis).
I welcome any suggestion on this, but for now let me merge this as is.


Open in Terminal in folders Error is back in VScode v.1.37.1

Got this error after updating my vscode.
https://github.com/microsoft/vscode/issues/77174
https://github.com/microsoft/vscode/issues/77179

Does the CWD exist? I can't give advice if you don't show the error.

Yeah the folder exists and is exactly the same issues I mentioned. I have been working on my project for 6 months now with the same config for debugging. I solved it downgrading one version as people suggested on those issues and it's working as usual after that but I had to disable the vscode auto-updates sadly.

Please show the error, when did you downgrade? Did you try on 1.38?

I updated it last week after I started this issue. I just updated to v1.38 and got:
The terminal shell CWD "my_folder" does not exist
Here my launch.json file:
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File (Integrated Terminal)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "cwd": "my_folder",
            "env": {
                "DJANGO_SECRET_KEY":"***"
            },
            // "args": ["test_db"]
        }
    ]
}

works in v1.36

Since it's related to python debugging please report to the python extension first https://github.com/microsoft/vscode-python


kubectl version command on Docker Desktop for Mac always returns a "Unable to connect to the server: dial tcp...no such host" error

I have just started using Kubernetes on my Docker Desktop for Mac and after enabling Kubernetes from the Preferences window, I tried running kubectl version to get the client version and server version. This is what I saw instead:
$kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.7", GitCommit:"be3d344ed06bff7a4fc60656200a93c74f31f9a4", GitTreeState:"clean", BuildDate:"2020-02-11T19:34:02Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"darwin/amd64"}
Unable to connect to the server: dial tcp: lookup kubernetes.docker.internal on <IP_ADDRESS>:53: no such host
I then decided to take a look at the kubectl config file by running kubectl config view:
$kubectl config view
apiVersion: v1
clusters:

cluster:
certificate-authority-data: DATA+OMITTED
server: https://kubernetes.docker.internal:6443
name: docker-desktop
contexts:
context:
cluster: docker-desktop
user: docker-desktop
name: docker-desktop
context:
cluster: docker-desktop
user: docker-desktop
name: docker-for-desktop
current-context: docker-for-desktop
kind: Config
preferences: {}
users:
name: docker-desktop
user:
client-certificate-data: REDACTED
client-key-data: REDACTED

Prior to this, I had already changed my current context to docker-for-desktop (as you can see in the above config file) but after running kubectl version, I kept seeing the same "Unable to connect to server error". That is very interesting because the above config file shows another address for the server....
After perusing some online threads, I decided to look at the cluster by running kubectl cluster-info.  But this also gave me the same error:
$kubectl cluster-info
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
Unable to connect to the server: dial tcp: lookup kubernetes.docker.internal on <IP_ADDRESS>:53: no such host
I ran kubectl cluster-info dump and saw the same error yet again:
$kubectl cluster-info dump
Unable to connect to the server: dial tcp: lookup kubernetes.docker.internal on <IP_ADDRESS>:53: no such host
I have already restarted Docker Desktop and reset the Kubernetes cluster but the error unfortunately doesn't go away.
Please advise and let me know the best way to solve this issue so that I can use kubectl to run Kubernetes commands locally with Docker Desktop on my Mac laptop.
Here is also a screenshot showing the version of Docker Desktop for Mac that I am currently running:

Just figured it out. By default, the server address for the cluster in the kube config file is set to https://kubernetes.docker.internal:. For Docker Desktop for Mac version <IP_ADDRESS> and K8s version 1.16.5, this server address needs to be changed to https://localhost:, where the port number is usually something like 6443. Once I made this change to the server address, I was finally able to connect to the local kube server and use the kubectl command without any issues.
You can change the kube config file by finding the .kube folder in the Users folder on your Mac (it's a hidden folder) and opening the config file in an editor. Then change the server address in the config file and save it.

Glad you got it figured out.
If the server address is wrong, you might want to open an issue with Docker Desktop for Mac.  They would be the ones who set that address.

/triage support
/close

This resolved my issue. Thank you.

Just in case anyone encounters the same issue I had...  Editing the kube config file from kubernetes.docker.internal to localhost worked, but was getting overwritten each time I restarted kube.  In the end I found that there was something wrong with my /etc/hosts file - it had an entry for kubernetes.docker.internal, but I couldn't ping it.  I recreated the /etc/hosts file from scratch and I could then ping kubernetes.docker.internal.  Kubectl then started working.

mac version
macos big sur 11.6

docker version
Client:
 Cloud integration: 1.0.17
 Version:           20.10.8
 API version:       1.41
 Go version:        go1.16.6
 Git commit:        3967b7d
 Built:             Fri Jul 30 19:55:20 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.8
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.6
  Git commit:       75249d8
  Built:            Fri Jul 30 19:52:10 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.9
  GitCommit:        e25210fe30a0a703442421b0f60afac609f950a3
 runc:
  Version:          1.0.1
  GitCommit:        v1.0.1-0-g4144b63
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

kubectl version
kubectl version --v=7
I0918 17:44:37.046766   58438 loader.go:372] Config loaded from file:  /Users/xxxxx/.kube/config
I0918 17:44:37.047343   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:37.047353   58438 round_trippers.go:438] Request Headers:
I0918 17:44:37.047358   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:37.047362   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:37.048995   58438 round_trippers.go:457] Response Status:  in 1 milliseconds
I0918 17:44:37.049067   58438 request.go:959] Got a Retry-After 1s response for attempt 1 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:38.052010   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:38.052029   58438 round_trippers.go:438] Request Headers:
I0918 17:44:38.052035   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:38.052040   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:38.053258   58438 round_trippers.go:457] Response Status:  in 1 milliseconds
I0918 17:44:38.053307   58438 request.go:959] Got a Retry-After 1s response for attempt 2 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:39.057269   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:39.057295   58438 round_trippers.go:438] Request Headers:
I0918 17:44:39.057305   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:39.057312   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:39.059058   58438 round_trippers.go:457] Response Status:  in 1 milliseconds
I0918 17:44:39.059109   58438 request.go:959] Got a Retry-After 1s response for attempt 3 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:40.059337   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:40.059367   58438 round_trippers.go:438] Request Headers:
I0918 17:44:40.059375   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:40.059382   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:40.060902   58438 round_trippers.go:457] Response Status:  in 1 milliseconds
I0918 17:44:40.060952   58438 request.go:959] Got a Retry-After 1s response for attempt 4 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:41.064600   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:41.064617   58438 round_trippers.go:438] Request Headers:
I0918 17:44:41.064622   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:41.064627   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:41.065893   58438 round_trippers.go:457] Response Status:  in 1 milliseconds
I0918 17:44:41.065945   58438 request.go:959] Got a Retry-After 1s response for attempt 5 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:42.069898   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:42.069945   58438 round_trippers.go:438] Request Headers:
I0918 17:44:42.069960   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:42.069972   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:42.072609   58438 round_trippers.go:457] Response Status:  in 2 milliseconds
I0918 17:44:42.072678   58438 request.go:959] Got a Retry-After 1s response for attempt 6 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:43.073128   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:43.073153   58438 round_trippers.go:438] Request Headers:
I0918 17:44:43.073161   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:43.073167   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:43.074932   58438 round_trippers.go:457] Response Status:  in 1 milliseconds
I0918 17:44:43.074986   58438 request.go:959] Got a Retry-After 1s response for attempt 7 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:44.076268   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:44.076286   58438 round_trippers.go:438] Request Headers:
I0918 17:44:44.076292   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:44.076296   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:44.077693   58438 round_trippers.go:457] Response Status:  in 1 milliseconds
I0918 17:44:44.077737   58438 request.go:959] Got a Retry-After 1s response for attempt 8 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:45.082764   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:45.082784   58438 round_trippers.go:438] Request Headers:
I0918 17:44:45.082791   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:45.082796   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:45.084247   58438 round_trippers.go:457] Response Status:  in 1 milliseconds
I0918 17:44:45.084295   58438 request.go:959] Got a Retry-After 1s response for attempt 9 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:46.088829   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:46.088873   58438 round_trippers.go:438] Request Headers:
I0918 17:44:46.088887   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:46.088899   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:46.091262   58438 round_trippers.go:457] Response Status:  in 2 milliseconds
I0918 17:44:46.091325   58438 request.go:959] Got a Retry-After 1s response for attempt 10 to https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:47.093526   58438 round_trippers.go:432] GET https://kubernetes.docker.internal:6443/version?timeout=32s
I0918 17:44:47.093547   58438 round_trippers.go:438] Request Headers:
I0918 17:44:47.093555   58438 round_trippers.go:442]     Accept: application/json, */*
I0918 17:44:47.093561   58438 round_trippers.go:442]     User-Agent: kubectl/v1.21.4 (darwin/amd64) kubernetes/3cce4a8
I0918 17:44:47.095153   58438 round_trippers.go:457] Response Status:  in 1 milliseconds
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.4", GitCommit:"3cce4a82b44f032d0cd1a1790e6d2f5a55d20aae", GitTreeState:"clean", BuildDate:"2021-08-11T18:16:05Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"darwin/amd64"}
I0918 17:44:47.095468   58438 helpers.go:216] server response object: [{
  "metadata": {},
  "status": "Failure",
  "message": "an error on the server (\"\") has prevented the request from succeeding",
  "reason": "InternalError",
  "details": {
    "causes": [
      {
        "reason": "UnexpectedServerResponse"
      }
    ],
    "retryAfterSeconds": 1
  },
  "code": 500
}]
F0918 17:44:47.095510   58438 helpers.go:115] Error from server (InternalError): an error on the server ("") has prevented the request from succeeding
goroutine 1 [running]:
k8s.io/kubernetes/vendor/k8s.io/klog/v2.stacks(0xc00018e001, 0xc000c4a1e0, 0x97, 0xe8)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/klog/v2/klog.go:1021 +0xb9
k8s.io/kubernetes/vendor/k8s.io/klog/v2.(*loggingT).output(0x3c5a180, 0xc000000003, 0x0, 0x0, 0xc000788000, 0x31f5601, 0xa, 0x73, 0x100e100)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/klog/v2/klog.go:970 +0x191
k8s.io/kubernetes/vendor/k8s.io/klog/v2.(*loggingT).printDepth(0x3c5a180, 0xc000000003, 0x0, 0x0, 0x0, 0x0, 0x2, 0xc0005948c0, 0x1, 0x1)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/klog/v2/klog.go:733 +0x16f
k8s.io/kubernetes/vendor/k8s.io/klog/v2.FatalDepth(...)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/klog/v2/klog.go:1495
k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/util.fatal(0xc000c54000, 0x68, 0x1)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/util/helpers.go:93 +0x288
k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/util.checkErr(0x2c7bc00, 0xc000c48000, 0x2b07b00)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/util/helpers.go:188 +0x935
k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/util.CheckErr(...)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/util/helpers.go:115
k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/version.NewCmdVersion.func1(0xc000bca000, 0xc000495fd0, 0x0, 0x1)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/cmd/version/version.go:79 +0x117
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute(0xc000bca000, 0xc000495fc0, 0x1, 0x1, 0xc000bca000, 0xc000495fc0)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:854 +0x2c2
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc00046edc0, 0xc000190120, 0xc000180030, 0x3)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:958 +0x375
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute(...)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:895
main.main()
	_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubectl/kubectl.go:49 +0x21d

goroutine 18 [chan receive]:
k8s.io/kubernetes/vendor/k8s.io/klog/v2.(*loggingT).flushDaemon(0x3c5a180)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/klog/v2/klog.go:1164 +0x8b
created by k8s.io/kubernetes/vendor/k8s.io/klog/v2.init.0
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/klog/v2/klog.go:418 +0xdf

goroutine 11 [select]:
k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0x2b07a20, 0x2c7bf00, 0xc0003a8000, 0x1, 0xc00019eae0)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:167 +0x118
k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0x2b07a20, 0x12a05f200, 0x0, 0x1, 0xc00019eae0)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0x98
k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0x2b07a20, 0x12a05f200, 0xc00019eae0)
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:90 +0x4d
created by k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/util/logs.InitLogs
	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/kubectl/pkg/util/logs/logs.go:51 +0x96

Hi,
I had the same issue on my mac except instead of kubernetes.docker.internal kubectl wanted to connect to host.docker.internal.
The problem was missing record in /etc/hosts so I altered following line at the end of the file:
<IP_ADDRESS> host.docker.internal
# in your case you would add
# <IP_ADDRESS> kubernetes.docker.internal

constantly rewriting kube config (ususally ~/.kube/config) as mentioned above is a bad solution.


Research / proof of concept for GitHub deployments with approval gates

Make a copy of a repository (instead of just feature branch) in the US-EPA-CAMD organization and set up approval gates
Identify all steps & dependencies for deployment workflow

Determined not to consolidate all workflows into one
Will maintain feature branch and develop branch workflows
Modify release branch workflow for approvla gates

Proof of concept done for facilities API
https://github.com/US-EPA-CAMD/easey-facilities-api/tree/feature/Issue-902-Approval-Process-POC


ImportError: No module named 'tensorflow.models.rnn' cannot import data_utils

In 09_Recurrent_Neural_Networks\05_Creating_A_Sequence_To_Sequence_Model
05_seq2seq_translation.py
There was some import error as follows:
ImportError                               Traceback (most recent call last)
 in ()
21 from zipfile import ZipFile
22 from collections import Counter
---> 23 from tensorflow.models.rnn.translate import data_utils
24 from tensorflow.models.rnn.translate import seq2seq_model
25 from tensorflow.python.framework import ops
ImportError: No module named 'tensorflow.models.rnn'
And could you please give me some suggestion about how to find the right module in ver 1.0 after the update changed

TensorFlow's upgrade to v1.0.0 conversion script does not appear to have worked with the RNN library.  TF v 1.0 has moved the RNN library.  I will address this over the weekend.

I think I have the solution.  But it depends on a pull request that has recently been merged into the TensorFlow code base.  It will not be available until the next version release of TensorFlow.  Which should be soon.  Stay tuned.

Finally TF released a new version and I was able to get it working.  Please upgrade to TF v1.1.0 + and re try with the newer code.  Thanks!


[Question] Can we add or remove signaling servers dynamically?

Hi, I have a question regarding the use of dynamic signaling servers with the WebrtcProvider. Is there a way to add or remove signaling servers dynamically after initializing the provider?
Specifically, I’m wondering if it’s possible to switch signaling servers or handle errors with the signaling connection by adding/removing servers without reinitializing the entire WebrtcProvider or its awareness instance.
Thanks!

So that's a "NO," I suppose.

In the issue template I politely asked not to use this issue tracker as a discussion board.. Apparantly you didn't read it.
Please help me to me more efficient by following the rules. I think that's a small favor to ask for.


Error Message: connect ECONNREFUSED <IP_ADDRESS>:10000

Does this occur consistently? Yes
Repro steps:

deploy into newly created function app (make sure function is running)
make some changes, deploy new version into azure

Action: azureFunctions.deploy
Error type: ECONNREFUSED
Error Message: connect ECONNREFUSED <IP_ADDRESS>:10000
Version: 0.21.0
OS: win32
OS Release: 10.0.19587
Product: Visual Studio Code
Product Version: 1.43.1
Language: en

Call Stack
TCPConnectWrap.afterConnect [as oncomplete] net.js:1056:14

There is already same issue, #1521 which was closed with no resolution

@DenisBalan this doesn't reproduce for me with those simple steps. I'll need more information - for example what language your project is, what type of triggers it has, how you created the function app in Azure, etc.

@EricJizbaMSFT
function app linux os
language c#
http trigger
function app created in azure, deployed function from vscode

Are you by chance behind a proxy? Make sure you set that up in VS Code https://code.visualstudio.com/docs/setup/network
Also, this comment seems to suggest all that's needed is a VS Code restart


Integration PR for #6541

Allow admin users to set a repositories visibility to public, even if FORCE_PRIVATE is to true (#6541)
Signed-off-by: Matthias Beckert<EMAIL_ADDRESS>

Codecov Report

Merging #6572 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #6572      +/-   ##
==========================================
- Coverage   40.35%   40.35%   -0.01%
==========================================
  Files         405      405
  Lines       54260    54260
==========================================
- Hits        21899    21898       -1
- Misses      29346    29347       +1
  Partials     3015     3015

Impacted Files
Coverage Δ

routers/repo/setting.go
10.05% <0%> (ø)
:arrow_up:

modules/log/event.go
64.46% <0%> (-1.53%)
:arrow_down:

models/repo_list.go
67.89% <0%> (+1.05%)
: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 2664adf...f24aa88. Read the comment docs.

You are right, the user can always switch back to private. Nevertheless, the switch from private to public can only be performed by an administrator (in case of FORCE_PRIVAT).  This is also the case, if the visibility is changed multiple times.


DOCS: update introduction pages

Fix #149

add description of Bulma
swap title with logo for aesthetics
fix some typos (because why not)

in case it wasn't entirely clear @MangelMaxime from the issue itself, it is a very small change to the docs :-) so if you approve, it is ready to merge.

Yes, sorry I saw the PR and forget about it.


Add README.md with Hostnet sniff descriptions

Fixed issue #17 with @janlam7

So beautiful, thanks :heart:


Implement Contact data page on user profile edit section

Add email and telephone. Send this information to clinical site.


Feeds: arbitrary payload instead of arbitrary data structure

User story

Story

As I noticed, the payload of Feeds is an arbitrary data structure currently with only the time of the upload and the reference of a Content Addressed Chunk.
I think it is completely a waste of available chunk payload (in case of passing unencrypted reference, it uses 40 bytes from <4096 bytes).
Secondly, what if I want to add to this update more than one reference of swarm content? Or I want to attach metadata as well? This rigid data structure does not let me do that.
Seems neccessary to make a decision on a more flexible data structure first.
My suggestion is to use BSON instead of this current one, which could be ideal for our use-case (bee-js).
Acceptance criteria

On feed update it is possible to pass arbitrary data that is retrievable later.
It could make place for other specific use-cases as well, like dynamic content references in dApp environment (e.g. HTML link references, etc.) and other later.
The interface of this payload thereby has to be in generic type, but you still could protocolize for specific use-cases, like this before mentioned one.
Background

This approach proposal came up on the feed interface PR of bee-js.

What do you believe are the practical use cases of using BSON type of encoding for feeds instead of the current way of doing things?

Hey!
The point is it can open many unconsidered doors which are handled within application layer.
Let's suppose I only would like to open the referenced chunk if the metadata in the feed chunk meets with my requirements (e.g. if it describes the linked content is in format avi with length 1 hour 38 minutes, I don't want to even fetch it, because the theoritical application only supports mkv under 5 minutes).
Also there can be a use-case if I want to reference hashes of two independent content (e.g. one provides a Map DB, the other provides the client side to illustrate it visually.) where the two content connect together but not neccesary I want to download/use one side of it (e.g. I just want to download the DB part for my application that can interpret).
So I can go on, the goal of this approach is decrease the number of unneccessary requests while utilize anyhow the remaining unused data of the feed chunk.

I believe this is a good suggestion, but I see it as a nice to have. A higher priority for the dev team is hardening Bee.

@nugaon feeds in their current form enforce a strict data structure, because that's part of the definition of feeds as a construct. If you want to change the data structure it will not be a feed, but something else. I hope this answers the underlying concern. In theory you don't need to use feeds if they don't fit your purpose, but build some other type of construct that uses soc as the underlying chunk type in order to provide certain guarantees. As we all know, feeds can be entirely implemented outside of bee, so why not do things in the way that suits you best?

@acud you are right about its logic can be implemented outside of the Bee.
Nonetheless, if the Bee cannot interpret these extended payloads as a feed - when these are inteded to only extend the default feed capabilities - then one won't able to fetch feed reference on the BZZ path and it won't be supported by other tools as well that use feed endpoint to fetch feeds.
Although, the latter can be sorted out by integrating and replacing the feed endpoint usage with the application layer implementation, the application layer feed lookups cannot perform as well as if it would happen on the Bee side; e.g. the browsers have really tight limitation for concurrent requests towards one server (Bee), thereby slows down the lookup time.

Legacy feed swarm implementation had no restriction on the payload. Was there a reason to make it of Reference type? Would love to find out when this feature could be part of bee-js?

.

closed by #4677


Refactor out overlay type

Companion to https://github.com/spcl/dace-vscode/pull/268

Sadly not yet, but that is still firmly planned soon as well - only restriction is available time.. :-)


remove unnecessary build jobs from pull-request-checks workflow

Signed-off-by: Reuben Miller<EMAIL_ADDRESS>Proposed changes

Remove unnecessary build jobs from the pull-request-checks workflow. The PR checks already run cargo test which will build the binary anyway. Removing these tasks, also makes the pr check quicker.
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

It's weird. Why is GitAction expecting status of checks that are no more launched?

It's weird. Why is GitAction expecting status of checks that are no more launched?

I’ll look at the GitHub config. I probably just have to remove it from the repo settings as well

It's weird. Why is GitAction expecting status of checks that are no more launched?

I’ll look at the GitHub config. I probably just have to remove it from the repo settings as well

I have updated the branch protection rule to remove those checks.


Sagemaker Endpoint: Memory leak when switch model from SDXL and SD1.5/2.1 back and forth

Describe the bug
There are some issues describe memory leak when switch models, such as [Bug]: linux memory leak when switching models, and there are also some solution to mitigate the problem, like using tcmalloc.
Using tcmalloc seems to have solved the problem, but I recently encountered the memory leak problem again.
Expected Behavior
No memory leak and no OOM in Sagemaker endpoint.
Current Behavior
1. Init a new sagemaker endpoint

2. Check current sagemaker endpoint memory usage

3. Call /inference-api/inference to inference
Call the API_URL with follow parameters one by one (start from 1)

4. Load the first model (SDXL model)

we can see memory usage went up

and the first inference succeeded
5. Load the second model (SD1.5 model)

and the second inference also succeeded

6. Load the third model (SDXL model)

and we got OOM

7. After sagemaker restart
Because there were some requests in Sagemaker async queue, so when sagemaker went back, the endpoint kept switching models back and forth, memory kept going up, and we got another OOM.

Reproduction Steps
See Current Behavior
Possible Solution
I'm also trying to figure out a solution.
Additional Information/Context
No response
Solution Version
commit a4d0de13abb1dd61193100e0e643b8c2ca9f11aa
AWS Region. e.g., us-east-1
No response
Other information
No response

I finished another test, which only switch among SD1.5 models, no memory leak. Seems like that tcmalloc really work for some situations.

Finished last test, which only switch among SDXL models, also little memory leak.

Maybe we should not deploy SD1.5 models and SDXL models in one endpoint currently.

Thanks for the sharing. There mentioned memory leakage fix in 1.6.0 of webui, we will sync upstream in next sprint and should fix the issue.


timesync: await layer should return a read only channel

Motivation
A read only channel (<-chan) cannot be closed. Since the channel returned from AwaitLayer is shared by multiple components this adds an additional layer of safety where callers of AwaitLayer cannot close the received channel, but rather only the clock itself.
Changes
Change AwaitLayer to return a read only channel.
Test Plan
n/a
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors mere

bors merge

bors merge


Monorepo requires local @sveltejs/kit dependency

Describe the bug
In a mono repo, when using the Houdini vite build step. This bug occurs :
template:dev:
template:dev:  ><EMAIL_ADDRESS>dev
template:dev:  > vite dev
template:dev:
template:dev:  🎩 Generating runtime...
template:dev:  💡 No operation found. If that's unexpected, please check your config.
template:dev:  Forced re-optimization of dependencies
template:dev:
template:dev:    VITE v5.1.3  ready in 13480 ms
template:dev:
template:dev:    ➜  Local:   http://localhost:5173/
template:dev:    ➜  Network: use --host to expose
template:dev:  Internal server error: Failed to load url /src/routes/+layout.js (resolved id: /src/routes/+layout.js). Does the file exist?
template:dev:        at loadAndTransform (/home/projects/stackblitz-starters-vzrahe/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:53621:21)
template:dev:        at async instantiateModule (/home/projects/stackblitz-starters-vzrahe/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:54643:10)
template:dev:  Internal server error: Failed to load url /src/routes/+page.js (resolved id: /src/routes/+page.js). Does the file exist?
template:dev:        at loadAndTransform (/home/projects/stackblitz-starters-vzrahe/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:53621:21)
template:dev:        at async instantiateModule (/home/projects/stackblitz-starters-vzrahe/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:54643:10)
template:dev:  Error: Failed to load url /src/routes/+layout.js (resolved id: /src/routes/+layout.js). Does the file exist?
template:dev:      at loadAndTransform (/home/projects/stackblitz-starters-vzrahe/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:53621:21)
template:dev:      at async instantiateModule (/home/projects/stackblitz-starters-vzrahe/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:54643:10) {
template:dev:    code: 'ERR_LOAD_URL'
template:dev:  }

It can be resolved by adding a
"devDependencies": {
	"@sveltejs/kit": "^2.5.0"
}

to
.
└── apps/
    └── exp/
        └── package.json

or by manually adding the page.js/ts and layout.js/ts files to every route.
Without the houdini() build step, the issue does not occur even without the added dependency.
Reproduction
https://stackblitz.com/edit/houdini-bug-local-kit-dependency

You can pass the projectDir value in your config file to help houdini understand where things live. The docs should have an explanation. I'm going to close this but let me know if it's still bothering you and we can figure out what the best move is


results of the experiments

save experiment results (the whole result to be more generic) to the DB,
trigger next phases (e.g. offer 10 more experiments, stop experiment etc.)

analysis name should be taken from execution strategy

factorial analysis, bayesian optimization, t-tests (as in paper)

implemented here


Create a new Inventory Source -> Status must be off and save. We can see the Inventory Source Still Active.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
Master
Issue Description
Create a new Inventory Source -> Status must be off and save. We can see the Inventory Source Still Active.
Preconditions
Create a new Inventory Source -> Status must be off and save. We can see the Inventory Source Still Active.
Steps to reproduce

Go to Admin -> Settings -> Inventory Sources ->  Create a Inventory Source -> Status Off
Click on Save -> Check the  Datagrid -> Status is active.

Expected Result
If the Status is Inactive then it must be Inactive.
Actual Result
Please check the video for reference.
Video
https://github.com/user-attachments/assets/85afdadc-2505-4efd-bb2a-d33488e85caa
Screenshots
No response
Additional context
No response

Checked and found that status option UI issue has been fixed and working fine now, Please check the video for reference.
Video
https://github.com/user-attachments/assets/4be27309-b0c9-49ac-87a2-1fb558cce51c


implementation of Poroelasticity

…ic parameters

@sungho91 The build tests are failing because you have committed Makefile specified to your work environment. Please leave all the library and header paths as in the master branch.
Also, please see if you can make your changes be included in building through a command line option to make: e.g., make ndims=3 opt=2 openmp=1.

@echoi   I replaced Makefile with the original. Building was successfully done with both "make" and "make ndims=3 opt=2 openmp=1".

@sungho91 , please add brief descriptions of what are the main changes, and how they achieve the goal. Also, after building https://github.com/GeoFLAC/DynEarthSol/commit/6ca29b784a58ded65547f165088d445692a47d04, how can we @GeoFLAC/all test it? I mean, which input parameter file should we use and what are the results we should expect to get?

@echoi
I'm working on the implementation of poroelasticity, but some features are still needed to test it with a small problem. Therefore, I think I need to delete this branch before an example is ready. A description of the main changes may follow.


[release-3.1] cherry pick: Makefile: a new rule for CI test

Signed-off-by: mahjonp<EMAIL_ADDRESS>
What have you changed?
cherry-pick: #5934
What is the type of the changes?

Misc (other changes)

How is the PR tested?

No code

Does this PR affect documentation (docs) or should it be mentioned in the release notes?

No

Does this PR affect tidb-ansible?

No

Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Any examples? (optional)

/run-integration-common-test

/run-integration-common-test

/merge

/merge


Excuse me, I want to ask about database update

When I run dotnet ef database update, I run into this error: More than one DbContext was found. Specify which one to use
I notice that you have more than 1 DbContext. So how to fix this?

Ok I solved this

Hi there
You need to consider the following DbContext's, dependent what you are using:

ApplicationDbContext: cares about your application specific DB-Schema models. Might have an other name!
OpenIddictUIContext: cares about the OpenIddict dependent DB-Schema models
OpenIddictUIIdentityContext: cares about the ASP.NET Identity related DB-Schema models


Add an option to doubly-indent method parameters.

This is analogous to (and named after) the option for adding extra indent to class declarations.
I also fixed a bug in the existing DoubleIndentClassDeclaration implementation - note the added test case in TemplateFormatterTest.

This needs a rebase against https://github.com/scala-ide/scalariform

Closing in favor of PR against scala-ide/scalariform.


Add Support for Spark3.4

Add Spark3.4

Codecov Report

Merging #2050 (6b1bb0d) into spark3.4 (c6d5882) will decrease coverage by 21.85%.
The diff coverage is 50.00%.

@@              Coverage Diff              @@
##           spark3.4    #2050       +/-   ##
=============================================
- Coverage     87.07%   65.23%   -21.85%
=============================================
  Files           306      306
  Lines         16063    16221      +158
  Branches        852     1456      +604
=============================================
- Hits          13987    10581     -3406
- Misses         2076     5640     +3564

Files Changed
Coverage Δ

...a/com/microsoft/azure/synapse/ml/nn/BallTree.scala
0.00% <ø> (-82.86%)
:arrow_down:

...spark/ml/recommendation/RecommendationHelper.scala
36.70% <0.00%> (-50.14%)
:arrow_down:

...osoft/azure/synapse/ml/core/env/PackageUtils.scala
100.00% <100.00%> (ø)

...se/ml/exploratory/DistributionBalanceMeasure.scala
96.42% <100.00%> (+0.06%)
:arrow_up:

.../azure/synapse/ml/io/binary/BinaryFileFormat.scala
84.09% <100.00%> (-14.78%)
:arrow_down:

...spark/ml/source/image/PatchedImageFileFormat.scala
48.21% <100.00%> (-42.53%)
:arrow_down:

... and 140 files with indirect coverage changes


Adding more proxies

How do I add more proxies from other website so that when I select the option to use free proxy it will grab the info from there? I mean from those free proxy site where it could get the updated free proxy from those website and it will auto update with the latest working proxy. I have found a few good websites and would like to add in for the script to run as I realize that there isn't much proxy from the free ones and often they tend to fail.

You can download manually list from those websites and use it. Normally adding some websites won't work with the code it works with those 6 pre defined urls.
I believe script gather around 5k to 7k proxies. Also I suggest not to use free proxies.


fixes #22 in upstream

Coverage increased (+0.1%) to 87.417% when pulling ffdd65e4d65ac352c770052b4fb1fb2ba56c2c17 on kapeels:master into 789ff05562e8810d4979ad06928f1edf970b97a3 on hyojin:master.

Thanks! :)
Btw, I will change the prop and variable names to make it more clear.


Creat or Upodate a Global Policy does not set the baseurl, errors out always

errors out with:
##[error]Invalid URI: The hostname could not be parsed.
apimglobalpolicy.ps1 line 88 references baseurl, but never sets the variable

Hello,
Fixed, I merge @simonness's pull request!
Thanks

Thanks @stephaneey! 👍


fixed getting stuck when GroupConsumer#_joinGroup is failing.

This PR fixes a problem we have seen in no-kafka that would cause the consumer to hang forever and not attempt to rejoin. This would occur intermittently if a messagehub outage occurred.
This happens when the kafka server (in our case messagehub) is down. when you try to rejoin you will be in a reconnect loop and when the rejoins are failing you get an AggregateError. This contains errors.NoKafkaConnectionError for each of the kafka brokers in the cluster so catching that on the _joinGroup() call and then just re-throwing the first on in the Aggregate correctly puts us back into the catch(errors.NoKafkaConnectionError, { code: 'UnknownMemberId' }, { code: 'NotCoordinatorForGroup' } lower down that schedules another delayed attempt at a full rejoin.
We reproduced this problem by rolling restating a messagehub cluster and have confirmed this fixes the issue we where seeing.

I think it will be safe enough to retry full rejoin on any error. So
.catch(errors.NoKafkaConnectionError, { code: 'UnknownMemberId' }, { code: 'NotCoordinatorForGroup' }, function (err) {
can be replaced with
.catch(function (err) {

@oleksiyk See this last commit, this makes the change you proposed such that on any error in _tryFullRejoin we will retry to rejoin.

Can you please remove debug logging on line 188 and line 201 and also drop all changes to package.json and then I'll merge it. Or alternatively I can close this PR and simply make changes myself.

@oleksiyk Since its a small change i will close this if you could then do it your self that would be good. The package.json changes where meant to be on a different branch sorry about that

Published as 3.2.3


🚧 Contributing guidelines 🚧

[ ] Write contributing guidelines - WIP
[ ] Write code of conduct
[ ] Write issue template
[ ] Write pull request template

Codecov Report

Merging #42 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #42   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          14     14
  Lines          36     36
=====================================
  Hits           36     36

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 e3508bc...9e2699d. Read the comment docs.


Move DropNegligible transpiler pass to qiskit

See https://github.com/Qiskit/qiskit/pull/12384

Now that Qiskit has the RemoveIdentityEquivalent pass, we can proceed with this issue by deprecating and removing DropNegligible.


Whether batch GET and DELETE are supported?

var rowKeys = ['1', '2', '3', '4', '5'....] rowKeys.forEach(rowKey -> {client.get(rowKey)/ client.delete(rowKey)});
How can I get or delete multiple rows with row keys in addition to using the loop function above.

And can i set the 'ttl' option for the cells or rows?


Cyrillic support

Hello,
Can you please include a support for dispaying Cyrillic in .md files?
Thank you in advance.
P.S. Useful plugin!

Hello,
Thanks for contributing. Next release will have cyrillic support.

Can you provide some md file with Cyrillic text for testing?

https://github.com/PoziWorld/PoziTone/blob/develop/README_ru.md
https://github.com/poziworld/PoziTone/blob/develop/HISTORY_ru.md
It's a weird thing, yesterday when I first switched rendering engine to JavaFX WebView, in one of two open files Cyrillic showed up, so I switched it a few more times, but I wouldn't show up again in any of those two files.
Now I have JxBrowser chosen, and in the second file it shows Cyrillic, but not in the one it showed up the first time...

Hello,
Any update on this issue?
Thanks.

@PoziWorld, can you please try to disable ''Use offline generation" option inside Gfm settings.

When it's enabled, the first time I open a Cyrillic document, it works fine. But when I change something in that document, and then go back to the preview, it no longer works.
When it's disabled, it doesn't work at all. Not event the first time.
It is the same for all rendering engines.

That's odd. Can you please provide your OS version and Itellij(Webstor, phpstorm,...) version. Can you please check that you have version 0.1.8 of GFM plugin installed?

Windows 7
PhpStorm PS-143.129
GFM 0.1.8

Should be fixed in v0.1.9

It works in offline mode. Thank you!

Actually, in both modes. But when I first tried it after upgrading, the plugin wasn't in offline mode, when added some text in .md file and switched to preview, it showed some exception. Sorry, didn't take a screenshot. Can't replicate it anymore.