[NOTE] API "POST /projects/{project_id}/metadatas" not work properly

by swagger UI

by harborctl
[#677#root@ubuntu-1604 /go/src/github.com/moooofly/harborctl]$./harborctl project metadata add -h
This endpoint is aimed to add all metadatas for a project.

Usage:
  harborctl project metadata add [flags]

Flags:
  -a, --automatically_scan_images_on_push                        Whether scan images automatically when pushing.
  -t, --enable_content_trust                                     Whether content trust is enabled or not. If it is enabled, user cann't pull unsigned images from this project.
  -h, --help                                                     help for add
  -r, --prevent_vulnerable_images_from_running                   Whether prevent the vulnerable images from running.
  -s, --prevent_vulnerable_images_from_running_severity string   If the vulnerability is high than severity defined here, the images cann't be pulled.
  -j, --project_id int32                                         (REQUIRED) Project ID of project which will be get.
  -k, --public int32                                             The public status of the project, public(1) or private(0). (default 1)

Global Flags:
      --config string   config file (default is $HOME/, working dir (.), and ./conf dir)
[#678#root@ubuntu-1604 /go/src/github.com/moooofly/harborctl]$
[#678#root@ubuntu-1604 /go/src/github.com/moooofly/harborctl]$./harborctl project metadata add -j 95 -k 1 -a true -t true -r true
==>  {"public":1,"enable_content_trust":true,"prevent_vulnerable_images_from_running":true,"prevent_vulnerable_images_from_running_severity":"","automatically_scan_images_on_push":true}
==> POST https://localhost/api/projects/95/metadatas
<==
<== Rsp Status: 400 Bad Request
<== Rsp Body: Invalid json request
[#679#root@ubuntu-1604 /go/src/github.com/moooofly/harborctl]$

After some tests, new conclusions update here:

"400 Invalid json requrest" results from the value in this json object must be string (not as "Example Value" defines)

after changing the value type, you will get

Can add only one key/value pair each time calling this API, or you will get "400 invalid request: has no valid key/value pairs or has more than one valid key/value pairs" as above.

Adding only one metadata works well

Adding the same metadata again will fail with "409"


introduced consul_systemd_service_name variable

SUMMARY
introduced consul_systemd_service_name variable to allow specifying name of service (and related directories), solving the issue of running multiple instances on the same machine
ISSUE TYPE

Feature Pull Request

Can you add the new variable to the readme, please? Otherwise this looks good to me (when ansible-lint is happy).


[Codelab Issue] Testing Codelab 5.1, Task 8, Step 5 - Typo in a link

Describe the problem
There is a type in the link that sends to ApplicationProvider.getApplicationContext()
it looks like this:

ApplicationProvider.getApplicationContex t

while it should look like this:

ApplicationProvider.getApplicationContext()

In which lesson and step of the codelab can this issue be found?
-> Advanced Android in Kotlin 05.1
-> ->Task 8.(Setting up a ViewModel Test with AndroidX Test)
-> -> ->Step 5. Use AndroidX Test
codelab: advanced-android-kotlin

Thanks, fixed in next release.


Bug - 'Send' functionality broken with genesis account

Description
Broken 'Send' UX/UI with specific genesis account(s)
Additional Context

account: haytcmjrgige
not yet reproducible with other genesis accounts

Screenshots

I was able to do this on mainnet @donnyquixotic. Not able to duplicate the issue.

Closing it because is not reproducible anymore


cmd ref: metrics 1.0 update

This PR updates cmd ref according to https://github.com/iterative/dvc/pull/3963

cmd ref: metrics diff: targets desc updated per https://github.com/iterative/dvc/pull/3963

cmd ref: metrics show: targets desc updated per https://github.com/iterative/dvc/pull/3963

Part of #1414

Thanks @nik123 !


make examples and hello awesome

This enables us to pn examples panel-chemistry and pn show panel-chemistry. Similarly for panel-highcharts and other repositories.

Codecov Report
Base: 89.28% // Head: 90.07% // Increases project coverage by +0.79% :tada:

Coverage data is based on head (ba3ed70) compared to base (1fcfea8).
Patch coverage: 92.53% of modified lines in pull request are covered.

:exclamation: Current head ba3ed70 differs from pull request most recent head aa77d76. Consider uploading reports for the commit aa77d76 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #43      +/-   ##
==========================================
+ Coverage   89.28%   90.07%   +0.79%
==========================================
  Files          10       10
  Lines         364      393      +29
==========================================
+ Hits          325      354      +29
  Misses         39       39

Impacted Files
Coverage Δ

src/awesome_panel_cli/cli/main.py
92.30% <87.50%> (-7.70%)
:arrow_down:

src/awesome_panel_cli/hello.py
93.18% <93.18%> (ø)

src/awesome_panel_cli/cli/create.py
84.42% <100.00%> (-0.26%)
:arrow_down:

src/awesome_panel_cli/config.py
96.07% <100.00%> (ø)

src/awesome_panel_cli/shared.py
100.00% <100.00%> (ø)

src/awesome_panel_cli/cli/test.py
81.94% <0.00%> (-0.25%)
:arrow_down:

src/awesome_panel_cli/cli/build.py
100.00% <0.00%> (ø)

src/awesome_panel_cli/cli/autoformat.py
100.00% <0.00%> (ø)

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.


[NETBEANS-1074] Module Review libs.nashorn

Just added license to binaries-list

Folks, this will not be that easy. Nashorn binary needs to be distributed, since it is used at runtime, but uses GPLv2+CPE license, which is not compatible with Apache distribution AFAIK.
I would separate two issues: cleaning up / fixing license so that the code may reside in the repository. This is what this PR is about. Other code can compile against the nashorn classes (compile-time dependency), but that code will not actually run.
I filed issue NETBEANS-1159 to explore possible relicensing from the contributor (Oracle). In the meantime, approach similar to NB javac could be used, as the code can (IMHO, IANAL) be legally compiled AND distributed, though not using Apache mirrors. See NETBEANS-1160.

NB is working, at least the 'basic' cluster. I hope to fix the non-political issue soon ;)

Yeah - I meant working javascript support. My understand was/is, that for the incubation period it is more or less expected, that releases are not perfect and as such, we gain nothing by breaking the js support.

So do you think it's OK for the GPLed binary to appear in convenience master builds ?
@geertjanw  - what's your opinion ?

Yes - and if nashorn follows OpenJDK convention, this is GPL-CPE, which is at least discussed as Category-B: https://issues.apache.org/jira/browse/LEGAL-336

@matthiasblaesing returned nashorn back to the build. Please re-check before squash/merge.


bundler and node16 not mentioned in Module Resolution

Handbook Module Resolution page doesn't mention newly added bundler and node16/nodenext options. There are also implications that are not mentioned in the config reference, but only in the announcement blog.

This is in progress: https://github.com/microsoft/TypeScript/issues/52593


won't work with code actions that will open up a new floating window

nvim -v
NVIM v0.7.0
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by<EMAIL_ADDRESS>
Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/opt/homebrew/Cellar/neovim/0.7.0/share/nvim"

Run :checkhealth for more info

To be specific, null-ls.nvim + gitsigns.nvim wouldn't work for code action preview hunk
minimal config
 require('packer').startup(function()
    use 'nvim-telescope/telescope.nvim'
    use 'nvim-telescope/telescope-ui-select.nvim'
    use 'lewis6991/gitsigns.nvim'
    use 'jose-elias-alvarez/null-ls.nvim'
end
)

require 'telescope'.setup {}
require('telescope').load_extension 'ui-select'
vim.keymap.set('n', 'gca', vim.lsp.buf.code_action, {})

require 'null-ls'.setup {
    sources = {
        null_ls.builtins.code_actions.gitsigns,
    }
}

Then open any file that has any unstaged changes, put cursor at the place where changes make, type gca, and select preview hunk, and it will show nothing.
However, if comment out this line, using default ui of code_action(), then preview_hunk works just fine
-- require('telescope').load_extension 'ui-select'

same issue, but it's sporadic.

Similar issue but with efm-langserver when vim.lsp.buf.formatting is called.

I think i found the cause of the problem from dressing.nvim. You can take my fork or try dressing.nvim which also provides the same select(telescope).
https://github.com/stevearc/dressing.nvim/blob/c1e1d5fa44fe08811b6ef4aadac2b50e602f9504/lua/dressing/select/telescope.lua#L73C10-L73C10


Add nodev to options of bind mounts from kube

Need to do this in the runtime as k8s doesn't allow
arbitrary mount options to be passed in for bind mounts.
Fixes vulnerability issue.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1627633
Signed-off-by: Urvashi Mohnani<EMAIL_ADDRESS>

@mrunalp PTAL

/ok-to-test

/test all

/test kata-containers

/test kata-containers

/retest

/test kata-containers

@sboeuf kata broken somehow?

we would need this for 1.12/1.11 and probably cherry-pick on older release (on me, no worry :))

@runcom yeah the BZ for this is for 3.9, so we need to cherry-pick into 1.9 as well. Thanks!

@runcom let me check

@runcom only a glitch, let's rerun it.

/test kata-containers

/test kata-containers

Alright green, let's start the backports now

@runcom are you doing the backports or should I go ahead and do them?

I'm doing them no worry!


ESP32S3 support

I would also like to know if it would be compatible with ESP32S3. Thanks

The only Espressif devices I currently own are the ESP8266 and the ESP32, so I can not officially support other devices.
However since the ESP32S3 uses the same Framework as the ESP32 it would likely work with only adjustments to the platformio.ini.

Nevermind, because I have WiFi issues with the latest version of the Framework(documented here) I set this project to use an outdated version of it, which does not support the ESP32S3.
Conclusion: Sorry, but until my WiFi issues are resolved I will be unable to use a version of the Framework that supports newer ESP chips.


Should move params to one big file

Based upon: #165
It think it would be better if there is one big ::php::params class who gets inherited by the code.
With the version_switch patch, you'll have case statements floating in every single params class what is a waste of resources and a pity to maintain.
What is your thought about it?

I would rather user module data instead.


skbio.Table.write does not work as expected

This is puzzling. The .write, which subsequently opens a h5py.File for write is erroring on read. The same table can be successfully written with biom.util.biom_open, which suggests there may be an unexpected interplay in the IO registry
> table.write('qiita_study_13114-workshop.biom')
---------------------------------------------------------------------------
UnsupportedOperation                      Traceback (most recent call last)
Cell In[64], line 1
----> 1 table.write('qiita_study_13114-workshop.biom')

File ~/miniconda3/envs/sk061/lib/python3.11/site-packages/skbio/io/registry.py:670, in IORegistry._apply_write.<locals>.write(self, file, format, **kwargs)
    669 def write(self, file, format=cls.default_write_format, **kwargs):
--> 670     return registry.write(self, into=file, format=format, **kwargs)

File ~/miniconda3/envs/sk061/lib/python3.11/site-packages/skbio/io/registry.py:616, in IORegistry.write(self, obj, format, into, **kwargs)
    610 if writer is None:
    611     raise UnrecognizedFormatError(
    612         "Cannot write %r into %r, no %s writer found."
    613         % (format, into, obj.__class__.__name__)
    614     )
--> 616 writer(obj, into, **kwargs)
    617 return into

File ~/miniconda3/envs/sk061/lib/python3.11/site-packages/skbio/io/registry.py:1095, in Format.writer.<locals>.decorator.<locals>.wrapped_writer(obj, file, encoding, newline, **kwargs)
   1093 with open_files(files, mode="w", **io_kwargs) as fhs:
   1094     kwargs.update(zip(file_keys, fhs[:-1]))
-> 1095     writer_function(obj, fhs[-1], **kwargs)

File ~/miniconda3/envs/sk061/lib/python3.11/site-packages/skbio/io/format/biom.py:125, in _sktable_to_biom(obj, fh)
    123 @biom.writer(Table)
    124 def _sktable_to_biom(obj, fh):
--> 125     _table_to_biom(obj, fh)

File ~/miniconda3/envs/sk061/lib/python3.11/site-packages/skbio/io/format/biom.py:130, in _table_to_biom(obj, fh)
    128 def _table_to_biom(obj, fh):
    129     h5grp = h5py.File(fh, "w")
--> 130     obj.to_hdf5(h5grp, f"Written by scikit-bio version {skbio.__version__}")

File ~/miniconda3/envs/sk061/lib/python3.11/site-packages/biom/table.py:4694, in Table.to_hdf5(self, h5grp, generated_by, compress, format_fs, creation_date)
   4686 grp.create_dataset('matrix/indptr', shape=(len_indptr,),
   4687                    dtype=np.int32,
   4688                    data=self._data.indptr,
   4689                    compression=compression)
   4691 if len_ids > 0:
   4692     # if we store IDs in the table as numpy arrays then this store
   4693     # is cleaner, as is the parse
-> 4694     grp.create_dataset('ids', shape=(len_ids,),
   4695                        dtype=H5PY_VLEN_STR,
   4696                        data=[i.encode('utf8') for i in ids],
   4697                        compression=compression)
   4698 else:
   4699     # Empty H5PY_VLEN_STR datasets are not supported.
   4700     grp.create_dataset('ids', shape=(0, ), data=[],
   4701                        compression=compression)

File ~/miniconda3/envs/sk061/lib/python3.11/site-packages/h5py/_hl/group.py:183, in Group.create_dataset(self, name, shape, dtype, data, **kwds)
    180         parent_path, name = name.rsplit(b'/', 1)
    181         group = self.require_group(parent_path)
--> 183 dsid = dataset.make_new_dset(group, shape, dtype, data, name, **kwds)
    184 dset = dataset.Dataset(dsid)
    185 return dset

File ~/miniconda3/envs/sk061/lib/python3.11/site-packages/h5py/_hl/dataset.py:166, in make_new_dset(parent, shape, dtype, data, name, chunks, compression, shuffle, fletcher32, maxshape, compression_opts, fillvalue, scaleoffset, track_times, external, track_order, dcpl, dapl, efile_prefix, virtual_prefix, allow_unknown_filter, rdcc_nslots, rdcc_nbytes, rdcc_w0)
    163 dset_id = h5d.create(parent.id, name, tid, sid, dcpl=dcpl, dapl=dapl)
    165 if (data is not None) and (not isinstance(data, Empty)):
--> 166     dset_id.write(h5s.ALL, h5s.ALL, data)
    168 return dset_id

File h5py/_objects.pyx:54, in h5py._objects.with_phil.wrapper()

File h5py/_objects.pyx:55, in h5py._objects.with_phil.wrapper()

File h5py/h5d.pyx:282, in h5py.h5d.DatasetID.write()

File h5py/_proxy.pyx:148, in h5py._proxy.dset_rw()

File h5py/h5fd.pyx:163, in h5py.h5fd.H5FD_fileobj_read()

UnsupportedOperation: read

@RaeedA do you have some thoughts on this? Thanks!

Is this a more recent issue, or has this been ongoing?

This is a more recent issue. It is seemingly urgent too (but @wasade can comment on this). But @RaeedA let's first address the other issue you are currently working on before getting to it.

@mataton and I were just looking into another I/O issue regarding SampleMetadata. We solved it. But during the process we realized that skbio's I/O is super complicated. There are lots of interplays.

For example, there is a place where a write class inherits a read class. It is probably not related to the current issue, though.

I was able to reproduce this error on the workshop BIOMs. However, skbio.table.example_table seems to work fine.

That is quite weird. And the unit tests pass. @qiyunzhu, did that table have any sample or observation metadata? I ask as historically that's been the primary pain point with IO

@wasade Good point. Just tested. A table without metadata (the OGU table downloaded from Qiita) works fine. A table with metadata (the 16S ASV table downloaded from your GG2 repo) failed. It seems that metadata is the problem. Even after executing del_metadata the problem persists.

I don't know what the GG2 repo is... sorry. Metadata cannot be the problem if it exists after del_metadata


TimeUtility relies on DateTime

https://github.com/StansAssets/com.stansassets.foundation/blob/b3332055c35bb65162e22570b14c06d59ff4155e/Runtime/Utilities/TimeUtility.cs#L20
the TimeUtility class is based on DateTime, which means it breaks when pausing the play mode in the editor (timers should not proceed while paused).
Relying on Time.time OR Time.unscaledTime would pause if the game is paused in the editor (or even paused via timeScale in game, for Time.time)
Also the class is missing a "RuntimeInitializeOnLoad" to clear the static dictionary, which means timers would survive the playmode if the faster-playmode-options are used (https://blog.unity.com/technology/enter-play-mode-faster-in-unity-2019-3)

I think that we don't need to replace current implementation with something that pays attention to Editor.pause. But I'm sure that we have to extend current impl with version that you have requested. It sounds like a good idea for me, thank you.
[RuntimeInitializeOnLoad]. Absolutely agree, should be fixed. Otherwise it might become Editor only timer-tool.


HTTP Error 412 while using recent Turbo versions

🐛 Bug Report
I updated Turbo from 1.10.16 to 1.12.5 today and started seeing this in CI:
 WARNING  failed to contact remote cache: Error making HTTP request: HTTP status client error (412 Precondition Failed) for url (http://<IP_ADDRESS>:45045/v8/artifacts/e946449d9e73b6d1?slug=ci)

There is some discussion around this in this turbo issue, where people mention that this is likely due to using this remote cache server along with S3 specifically.
To Reproduce
I doubt that it will be possible for me to create reproduction instructions / repo for this issue considering that others have failed to reliably reproduce this in the thread above.
Expected behavior
To not get the http status errors.
Your Environment

Using this package with my GH action. I'm specifically using trappar/turborepo-remote-cache-gh-action@v2, which is a new version I've been working on in order to support the up-to-date version of this package.
Turbo version 1.12.5
Seeing the failures in CI while using GitHub Actions, where I'm using ubuntu-latest
Server is configured to connect to an S3 bucket

we've been having the same issue using Azure. Locked in at turbo v1.10 for now until we have time to fully investigate

Super weird. We're using a remote-cache server and Turbo 1.12.5 in other projects, and so far, we haven't had any problems at all

I've found what is causing this in my particular case.
I have two different workflows. I was only seeing this issue appear in one of them.
Both of them utilize my GH Action to start a cache server like this:
- uses: trappar/turborepo-remote-cache-gh-action@v2
  env:
    AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
    AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
  with:
    storage-provider: s3
    storage-path: turborepo-cache

However, the one that was failing had the following proceeding it:
- name: Configure AWS credentials
  uses: aws-actions/configure-aws-credentials@v4
  with:
    role-to-assume: arn:aws:iam::${{ secrets.ACCOUNT_ID }}:role/[REDACTED]
    aws-region: us-east-1

If I simply switch the order of these so that the remote cache server starts before configuring AWS credentials, then the error disappears.
So I'm not actually sure if this is a bug or not. Which credentials should take precedence? I'd assume env variables, but it looks like I'm wrong. I'm not actually 100% sure what the output of that aws action is, but it looks like it's taking over, and I'm fairly certain whatever credentials those are don't actually have permission to view the S3 bucket I'm telling the cache server to use.
Can someone who knows more about AWS than me help here?

I don't think wontfix is necessarily appropriate here for two reasons:

This only appears upon switching to Turbo versions above 1.10.16. Why is this same setup valid on 1.10.16? Seems like there's more to the story that's worth investigating.
The error handling needs to be improved.

just tried with turbo v1.13... 412 still persists :(

Does anybody know of alternatives to ducktors / turborepo-remote-cache that don't have this issue?

I'm seeing this as well, 1.10.16 works but newer versions do not.

last compatible turbo version is 1.12.0

@NullVoxPopuli, can you please provide a repro repo? I have enough time to investigate this properly, but I can't reproduce it myself.

Is there a discord or something, I don't want to spam everyone while I debug. I saw a request body too large error at one point -- while I was looking at the server logs, but I don't know if that's the problem -- trying figure out some filter syntax 😅

Yes, we have a nonpublic Discord that we set up a while ago, but I would love to have you join! https://discord.gg/PCnY8BEg

I don't think wontfix is necessarily appropriate here for two reasons:

This only appears upon switching to Turbo versions above 1.10.16. Why is this same setup valid on 1.10.16? Seems like there's more to the story that's worth investigating.
The error handling needs to be improved.

You are correct in saying this. As I said, we need a repro to investigate further. I also agree with the "better error handling" part you said.

Ok, I can't guarantee that the cause for me is the same as the cause for everyone else, but here's a minimal reproduction:
https://github.com/exogee-technology/turborepo-remote-cache-323-reproduction
Let me know if you need anything else!

Just wanted to confirm that as a workaround I've done the following in my deployment:
	// Create an access key and secret key for the service to access the bucket as a workaround for
	// https://github.com/ducktors/turborepo-remote-cache/issues/323
	const user = new User(this, 'Issue323WorkaroundUser');
	const accessKey = new CfnAccessKey(this, 'Issue323WorkaroundUserAccessKey', {
		userName: user.userName,
	});
	bucket.grantReadWrite(user);

	const service = new ApplicationLoadBalancedEc2Service(construct, 'TurborepoCacheService', {
		taskImageOptions: {
			env: {
				S3_ACCESS_KEY: accessKey.ref,
				S3_SECRET_KEY: accessKey.attrSecretAccessKey,
				// etc
			},
			// etc
		},
		// etc
	});

And this works fine. So it does really seem to be "When you don't pass secret key and access key, the server is unable to assume the execution role of the task as it should by default."

Awesome! How can we fix this directly in the app?

Personally I'd start by upgrading from aws-sdk v2 to v3. I'm not sure that'd fix it, but it might, and if it didn't then we'd have a better chance of working with AWS to figure out the root cause.
It'd also be good to catch this error more specifically and log out what's happening in a less cryptic way in this scenario.

I was able to replicate it using a homelab server, k3s and minio. I assume it is something related to the s3 bucket connection
"originalError":{"message":"write EPROTO 08C2C90647750000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL

I faced the 412 Precondition Failed issue with S3 as my Storage Provider recently while running the server (version 2.2.1) locally behind a proxy (http_proxy, https_proxy). In my case, the underlying error was denoted as a TimeoutError. For transparency, my monorepo project is using<EMAIL_ADDRESS>After using the AWS CLI directly (aws s3 ls s3://bucket-name) to confirm that the issue was not with my assumed temporary credentials, I started trying to isolate the issue between Turborepo Remote Cache directly and aws-sdk.
I'll spare the extra details, but essentially I set up a separate bare-bones project and only installed the exact version of aws-sdk that is used here (i.e., npm i -E aws-sdk@2.1310.0). I then created a single script where the only function was trying to "get object" from the S3 bucket, and upon running I again was greeted with a TimeoutError.
Some quick research brought me to the AWS "Configuring Proxies for Node.js" docs page which pointed out that the some third-party HTTP agent, such as proxy-agent, package would be required.
I npm installed Turborepo Remote Cache into a separate project, then proxy-agent, and finally modified remote-cache/storage/s3.ts (so s3.js in the project's node_modules) by adding the proxy configuration before the creation of the S3 client. This resolved my issue.
import { ProxyAgent } from 'proxy-agent';
// ...
export function createS3(...) {
  // Added this before creating client
  aws.config.update({
    httpOptions: {
      agent: new ProxyAgent(process.env.https_proxy),
    },
  });
  const client = new aws.S3(...);
  // ...
}

Again, this was only an issue locally where a proxy was set. Unfortunately, something simple like NO_PROXY="amazonaws.com" would not suffice in my case as the proxy is actually required for me to communicate with AWS entirely. A solution like this would only really make sense for local development and local testing, and not for an actual app being deployed to AWS.
I'm not sure if this will help in the case of the original post, but maybe this will help others searching for 412 Precondition Failed. Also, I agree that it would be nice for aws-sdk to be upgraded to v3 at some point 😃 .


Initial checkin of prometheus data capture code (KRAK-346).

Note that this depends on an unsubmitted PR to kraken-services.

Honestly it's still confusing to me that the volume / path is called 'promdash', isn't prometheus the thing storing all the data?  Aren't we anticipating we're going to remove promdash?

You are right that it's confusing. The previous emptyDir volume type stores both prometheus and promdash data, and the new hostPath will as well,but that's no reason to name it promdash. Fixing now.

OBE by k2


USB HID Keyboard on ESP32

Title!

It seems this is much more complicated than I thought. It would require patching up the esp-idf, replacing the build system, or somehow bringing in our own copy of TinyUSB. You'll note that this is something Arduino is doing: https://github.com/espressif/arduino-esp32/tree/master/tools/sdk/esp32s2/lib - see libarduino_tinyusb.a.
Otherwise, we could fork esp-idf and prep a docker image for building.

Feasible for Hackathon? Or do you think it is too much work?

Would it be reasonable to depend on the arduino version of the esp-idf?

The other thing we could do is build a one off UF2 that acts as a keyboard and mouse Jacdac->HID device for esp32. This would reduce overhead as we wouldn't have to set up all the infrastructure.


Keep the SuppressClientNestedActivities flag private for now

Addressing Review feedback
Related: https://github.com/Azure/azure-sdk/issues/4222

Do not  expose SuppressNestedClientSpans until we have some clear request, make it an explicit parameter on ClientDiagnsotics
Use Activity terminology instead of span similar to OpenTelemetry in .NET and BCL

API change check for Azure.Core
API changes have been detected in Azure.Core. You can review API changes here
API changes
-         public bool SuppressNestedClientSpans { get; set; }

API change check for Microsoft.Azure.WebJobs.Extensions.EventGrid
API changes are not detected in this pull request for Microsoft.Azure.WebJobs.Extensions.EventGrid

API change check for Azure.Storage.Common
API changes are not detected in this pull request for Azure.Storage.Common


Support for .Net 5

Are there any plans to support .Net 5?

We have a 3.1 target. Isn't that sufficient?

i would like to update my program to use .Net 5, in which i use avalonedit

My app is .Net 5 and I use AvalonEdit without any issues.

I should clarify and say I am using the NuGet package.

I've tested it and it indeed works.


About Quick Start

I have done the step git clone https://github.com/donnyyou/torchcv.git to the Cloud Server.
and then run the order: pip3 install -r requirements.txt
when I went to the next step : cd extensions
it returned me this error
(base) root@beeadf295ca5:~/code/torchcv# cd extensions
-bash: cd: extensions: 没有那个文件或目录
So I check the Code and I didn't find the file named extensions
is there something i miss to do?

Sorry, I have changed the directory to "exts".

Sorry, I have changed the directory to "exts".

Thanks for ur reply! It's my careless so that i miss the abbreviation “exts”


setHeaders should have a way to append instead of overwrite

Describe the problem
When using setHeaders for setting the Link header, it overwrites the current Link header that is generated by Sveltekit.
Describe the proposed solution
setHeaders should have a way to append to the current headers instead of overwriting them.
Alternatives considered
It could be done from within hooks, but I have different Link header depending on the page, so it would be easier to manage that in +page.server.ts or +layout.server.ts.
Importance
would make my life easier
Additional Information
No response

This would be helpful for me to quickly append Server-Timing at different parts of the app for perf monitoring when staging too. (hooks, parent loaders, etc)


How to save the rendered image

I tried to run kal.visualize.show() on the server but it seems not working.
So is there an alternative way like saving the rendered images?

@Zhangsihao-Yang I hope you answered your question -- sorry to take a long time to respond.
If not, please re-file the bug with more specific information. What rendered images do you mean? kaolin.visualize.show() is not a function in the library. To save rendered images you can use any one of standard python libraries like PIL or skimage.io.
Here is a tutorial on visualization features in Kaolin:
https://kaolin.readthedocs.io/en/latest/notes/checkpoints.html


How we Use Photo Library Picker after select images

Hi is there any sample photoLibraryPicker, whenever we selected images. How we take them.
Kind Regards.

@bmkaraduman Hi. The sample in the project.


Restore sveltekit template for Tauri 2(as new option in addition to svelte)

I know that this was closed in #340, but according to comments, this feature is really desirable.
The problem is that on web, most of the tutorials use sveltekit, and is very hard to create an app with svelte and alternative tools.
I tried to do this, but failed when trying to use routing via svelte-routing - with sveltekit everything works fine.
If needed, there can be added a warning with potential drawbacks, but I think that user should have ability to choose sveltekit

check out this guide if you want to create a sveltekit template https://beta.tauri.app/start/frontend-configuration/sveltekit/

At least for now, I've started using https://github.com/maiertech/template-tauri-sveltekit because it's the only template that has worked for me almost out of the box with Tauri 2 and sveltekit.
(Requires adding vitePreprocess to svelte.config.js and a few minor changes).
However, the problem is also that it cannot export app to mobile devices(actually I haven't tried it yet, but I'm almost sure that this not works).

We decided to replace Svelte with SvelteKit in https://github.com/tauri-apps/create-tauri-app/pull/708


Fix xds_test on MacOS by configuring ...

mesh in test setup so that listeners write access log to
/tmp/envoy-access.log instead of default /dev/stdout.
With this change make test shows the same failures on MacOS
as on linux. (Given a matching envoy executable version.)
Co-authored-by: Holger Oehm<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: holgero
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: sebastienvas
Assign the PR to them by writing /assign @sebastienvas in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @holgero. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

About the problem with the cla-check:

Is it due to our pairing set up? (@loewenstein is git-author, and I am only co-authoring, but I did the pull request).
Or is it the fact that my primary email address in my github account does not match my company email address? (But my company email address is also attached to my account.)
Or something completely different?

/ok-to-test

@holgero: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
26eace82cd9c057868a5bb4e770a091d3f32290c
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

If you are doing this, would you mind fixing that scripts to download the MacOS version of istio proxy ? We are building both versions now

@rshriram are we? Last time we checked we couldn't find it and built our own envoy to get rid of some more test failures. Any pointer?

Please rebase and wait until master gets all the other changes - wrapping up 0.8 release branch.

@holgero: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
97f65a08d8049284b23d92f8b49eb6d2d4e55f08
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Playwright requests should only override the user-agent when one is set, don't use the default, let chrome set its own.

Discussed in https://github.com/dgtlmoon/changedetection.io/discussions/1795

Originally posted by codedesperate September 13, 2023
Describe the bug
When switching from selenium to playwright, all checks get the error:
Warning, no filters were found, no change detection ran - Did the page change layout? update your Visual Filter if necessary.
Version
0.45.1
To Reproduce
Steps to reproduce the behavior:
1:
Use the following docker-compose:
version: '3.2'
services:
    changedetection:
      image: ghcr.io/dgtlmoon/changedetection.io
      container_name: changedetection
      hostname: changedetection
      network_mode: host
      environment:
        - PORT=5001
        - PLAYWRIGHT_DRIVER_URL=ws://<IP_ADDRESS>:3000/?stealth=1&--disable-web-security=true
#        - WEBDRIVER_URL=http://<IP_ADDRESS>:4444/wd/hub
      volumes:
        - changedetection-data:/datastore
      restart: unless-stopped
      depends_on:
#        browser-chrome:
#          condition: service_started
        playwright-chrome:
          condition: service_started

    playwright-chrome:
      hostname: playwright-chrome
      image: browserless/chrome
      network_mode: host
      restart: unless-stopped
      environment:
        - SCREEN_WIDTH=1920
        - SCREEN_HEIGHT=1024
        - SCREEN_DEPTH=16
        - ENABLE_DEBUGGER=false
        - PREBOOT_CHROME=true
        - CONNECTION_TIMEOUT=300000
        - MAX_CONCURRENT_SESSIONS=10
        - CHROME_REFRESH_TIME=600000
#        - DEFAULT_BLOCK_ADS=true
        - DEFAULT_STEALTH=true

#    browser-chrome:
#      hostname: browser-chrome
#      image: selenium/standalone-chrome-debug:3.141.59
#      network_mode: host
#      environment:
#        - VNC_NO_PASSWORD=1
#        - SCREEN_WIDTH=1920
#        - SCREEN_HEIGHT=1080
#        - SCREEN_DEPTH=24
#      volumes:
#          - /dev/shm:/dev/shm
#      restart: unless-stopped

volumes:
  changedetection-data:

Set up the following monitor:
https://changedetection.io/share/d0qlVgD8rgsa

In global "Fetch Method" have wait seconds set to 20.
Expected behavior
To have the monitor run, and successfully get the CSS Selector's value.
Desktop (please complete the following information):

OS: Ubuntu Server 22.04.3
Browser: Firefox

a test fix locally fixed a few of the "page request timed out" errors

https://github.com/chromedp/chromedp/issues/396
So kinda related
Now it sends  HeadlessChrome ...
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/103.0.5060.53 Safari/537.36


Fixed links in block-subscription-to-an-api.md

Purpose
Fixed links and notes in the block-subscription-to-an-api.md file.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Fetch errors not displayed correctly

I am currently developing an Angular application fetching data from an GraphQL server. When the GraphQL server throws an error and does not return data, the console in Edge would show a simple "Error on "fetch"" message whereas a browser like Firefox would show the correct error returned from the GraphQL server. As both browsers access the same Angular project connecting to the same GraphQL server through the same graphql-request module the problem seems to lie in Edge and presumably in Chakra.
The attached images show the returned error (1) from the GraphQL playground, (2) Firefox and (3) Edge.

Quick update: When the GraphQL server is responding with valid data, Edge also throws a fetch error while all other major browsers correctly receive and parse the data.

Second update: Upon further investigation, similar issues also occur when using plain Xhr requests instead of fetch. Right now, I am not able to make any http request from my Angular application whatsoever in Edge.

I'm going to close this one since it's unrelated to ChakraCore. Feel free to re-open if you have anything we can help with.


Failed to compile. Cannot read property 'compilation' of undefined

node scripts/start.js

Failed to compile.
Cannot read property 'compilation' of undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node scripts/start.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\Jaya\AppData\Roaming\npm-cache_logs\2018-10-31T17_59_05_425Z-debug.log

Please fill in the issue template and provide repro steps, thanks

I am having the same issue did you figure it out @crazyinvitation ?


Adds tests for section 9 of XEP-0045 Multi-User Chat

I'm opening this PR as a draft (for your reviewing pleasure) as I've completed a boatload of tests for sections 9.1 through 9.5. On the to-do list are sections 9.6 to 9.9.
Some of these tests are expected to fail when executing against Openfire versions before 4.8.3 (because of https://igniterealtime.atlassian.net/browse/OF-2843 and https://igniterealtime.atlassian.net/browse/OF-2844).

I've now completed sections 9.1 through 9.8. The XEP has a section 9.9, but I don't see things that are easily tested. I'll leave it at this. This PR now has 67 tests. \o/

I'm all for improving things, even if it's just marginally. I you have pedantic nits, just create a PR with them.


resetValues should not set the value to 0

When resetting states, there are better ways to reset the value

use deleteState to remove the state or
use the state.q flag to inform other adapters that this is not a "valid value"

See https://github.com/iobroker-community-adapters/ioBroker.statistics/issues/128

I have now implemented it so that when the gas station is closed, the old value from the ioBroker remains and the state quality is set to ( 0x40 ⇒ Substitute value from device ). The same happens if for some reason no price is available at the gas station.
My PR here still needs to be merged for this, of course. 😃


SurfaceExt is not exported

This seems like just an oversight, since lib.rs has
pub use surface::{
    MappedImageSurface,
    Surface,
};

Will submit a PR shortly.

Huh, I just noticed that it is exported, but from the prelude.

It should be exported from both though :) All types should be exported from lib.rs and all traits also from prelude

I always wondered what should be in a prelude.  Traits?  Anything else?

Traits only normally.

Not only normally. Only traits ;)


jsdom error on npm test

When I try to run tests I'm getting the following output. Of note, linting seems to work fine but as soon as the tests start up this error happens:
rglover @ ~/projects/themeteorchef/snippets/mantra/demo (master) $ npm test

><EMAIL_ADDRESS>test /Users/rglover/projects/themeteorchef/snippets/mantra/demo
> npm run lint && npm run testonly

><EMAIL_ADDRESS>lint /Users/rglover/projects/themeteorchef/snippets/mantra/demo
> eslint ./lib ./client ./server --ext .js

><EMAIL_ADDRESS>testonly /Users/rglover/projects/themeteorchef/snippets/mantra/demo
> mocha .scripts/mocha_boot.js client/**/tests/**/*.js --compilers js:babel-core/register

/Users/rglover/projects/themeteorchef/snippets/mantra/demo/node_modules/jsdom/lib/jsdom.js:3
() => `jsdom 7.x onward only works on Node.js 4 or newer: https://github.com/t
 ^
SyntaxError: Unexpected token )
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Module._extensions..js (module.js:478:10)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/rglover/projects/themeteorchef/snippets/mantra/demo/node_modules/babel-core/node_modules/babel-register/lib/node.js:166:7)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (mocha_boot.js:1:13)
    at Module._compile (module.js:460:26)
    at loader (/Users/rglover/projects/themeteorchef/snippets/mantra/demo/node_modules/babel-core/node_modules/babel-register/lib/node.js:158:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/rglover/projects/themeteorchef/snippets/mantra/demo/node_modules/babel-core/node_modules/babel-register/lib/node.js:168:7)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at /Users/rglover/projects/themeteorchef/snippets/mantra/demo/node_modules/mocha/lib/mocha.js:219:27
    at Array.forEach (native)
    at Mocha.loadFiles (/Users/rglover/projects/themeteorchef/snippets/mantra/demo/node_modules/mocha/lib/mocha.js:216:14)
    at Mocha.run (/Users/rglover/projects/themeteorchef/snippets/mantra/demo/node_modules/mocha/lib/mocha.js:468:10)
    at Object.<anonymous> (/Users/rglover/projects/themeteorchef/snippets/mantra/demo/node_modules/mocha/bin/_mocha:403:18)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3

npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/usr/local/bin/npm" "run" "testonly"
npm ERR! node v0.12.4
npm ERR! npm  v2.10.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>testonly: `mocha .scripts/mocha_boot.js client/**/tests/**/*.js --compilers js:babel-core/register`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>testonly script 'mocha .scripts/mocha_boot.js client/**/tests/**/*.js --compilers js:babel-core/register'.
npm ERR! This is most likely a problem with the mantra-demo package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     mocha .scripts/mocha_boot.js client/**/tests/**/*.js --compilers js:babel-core/register
npm ERR! You can get their info via:
npm ERR!     npm owner ls mantra-demo
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/rglover/projects/themeteorchef/snippets/mantra/demo/npm-debug.log
npm ERR! Test failed.  See above for more details.

Can this be easily solved by swapping a version somewhere or is it a bigger issue?

Can you tell me what's your node version?

Same issue using node v4.20.6. Haven't had a chance to try with new node yet but I'm sure that's the issue.

Got the same error ; updated to node 6.3.1 with n -> works fine.
npm test

><EMAIL_ADDRESS>test /Users/laurent/dev/meteor/mantra-sample-blog-app
> npm run lint && npm run testonly

><EMAIL_ADDRESS>lint /Users/laurent/dev/meteor/mantra-sample-blog-app
> eslint ./lib ./client ./server --ext .js

><EMAIL_ADDRESS>testonly /Users/laurent/dev/meteor/mantra-sample-blog-app
> mocha .scripts/mocha_boot.js client/**/tests/**/*.js --compilers js:babel-core/register

  comments.actions.comments
    create
      ✓ should reject if text is not there
      ✓ should reject if postId is not there
      ✓ should clear older LocalState for CREATE_COMMENT_ERROR
      ✓ should call Meteor.call to save the comment
      after Meteor.call
        if there is error
          ✓ should set CREATE_COMMENT_ERROR with the error message
    clearErrors
      ✓ should clear CREATE_COMMENT_ERROR local state

  comments.components.comment_list
    ✓ should list given number of items
    ✓ should list comment author for each item
    ✓ should list comment text for each item
    ✓ should list saving status for each item

  comments.components.create_comment
    ✓ should show the error if there are any
    ✓ should display the create comment form
    ✓ should create a new comment when click on the button

  comments.containers.comment_list
    composer
      ✓ should subscribe to posts.comments
      after subscribed
        ✓ should fetch data from all comments & pass to onData

  comments.containers.create_comment
    composer
      ✓ should get CREATE_COMMENT_ERROR from local state
      ✓ should call onData with null and {error}
      ✓ should return clearErrors
    depsMapper
      actions
        ✓ should map comments.create
        ✓ should map comments.clearErrors
      context
        ✓ should map the whole context as a function

  core.actions.posts
    create
      ✓ should reject if title is not there
      ✓ should reject if content is not there
      ✓ should clear older LocalState for SAVING_ERROR
      ✓ should call Meteor.call to save the post
      ✓ should redirect user to the post
      after Meteor.call
        if there is error
          ✓ should set SAVING_ERROR with the error message
    clearErrors
      ✓ should clear SAVING_ERROR local state

  core.components.main_layout
    ✓ should contain navigation
    ✓ should render childrens

  core.components.navigation
    ✓ should contain a link to home
    ✓ should contain a link to create a new post

  core.components.newpost
Warning: ReactComponentTreeDevtool: Missing React element for debugID 5 when building stack
Warning: ReactComponentTreeDevtool: Missing React element for debugID 5 when building stack
Warning: ReactComponentTreeDevtool: Missing React element for debugID 5 when building stack
Warning: ReactComponentTreeDevtool: Missing React element for debugID 5 when building stack
Warning: ReactComponentTreeDevtool: Missing React element for debugID 5 when building stack
Warning: ReactComponentTreeDevtool: Missing React element for debugID 5 when building stack
Warning: ReactComponentTreeDevtool: Missing React element for debugID 5 when building stack
Warning: ReactComponentTreeDevtool: Missing React element for debugID 5 when building stack
Warning: ReactComponentTreeDevtool: Missing React element for debugID 5 when building stack
    ✓ should show the error if there are any
    ✓ should display the create post form
    ✓ should create a new post when click on the button

  core.components.post
    ✓ should display the post title
    ✓ should display the post content
    ✓ should display saving indicator if saving prop is there

  core.components.postlist
    ✓ should list given number of items
    ✓ should list post title for each item
    ✓ shallow list post link for each items

  core.containers.newpost
    composer
      ✓ should get SAVING_ERROR from local state
      ✓ should call onData with null and {error}
      ✓ should return clearErrors
      - should get SAVING_NEW_POST from local state
    depsMapper
      actions
        ✓ should map posts.create
        ✓ should map posts.clearErrors
      context
        ✓ should map the whole context as a function

  core.containers.post
    composer
      ✓ should subscribe to the given postId via prop
      before subscription ready
        with latency componsation
          ✓ should call onData with data
        with no latency componsation
          ✓ should call onData without nothing
      after subscription is ready
        ✓ should call onData with data

  core.containers.postlist
    composer
      ✓ should subscribe to posts.list
      after subscribed
        ✓ should fetch data from all posts & pass to onData

  53 passing (255ms)
  1 pending

What's the pending test ?


proxy option without is ignored

1. What version of Caddy are you using (caddy -version)?
Bug in version 0.10 (0.8.3 working just fine)
2. What are you trying to do?
Use the 'without' option in the proxy module
3.   Please paste any relevant HTTP request(s) here.
No Curl, but browser: http://<IP_ADDRESS>:8000/wikipedia/wiki/Hans_Zimmer
6. What did you expect to see?
The german wikipedia site of Hans Zimmer
7. What did you see instead (give full error messages and/or log)?
Wikipedia responding with its 404 page
Page not found
/wikipedia/wiki/Hans_Zimmer

We could not find the above page on our servers.

Error being the /wikipedia not being stripped.
8. How can someone who is starting from scratch reproduce the bug as minimally as possible?
Nothing but the supplied Caddyfile and a browser

Hi @tstorch - thank you for using the issue template! And I like what you're using Caddy for. :+1:
This is a duplicate of #1604 I believe. (Definitely don't keep using 0.8.3 though! That's oollldddd.)

You're absolutely correct. It's a duplicate.
I'm just starting a new project and thought: Why not update...
I'll just resort to 0.9.5 :cry:
Thanks for the quick answer and keep up the good work! :+1:


Arrow functions inside of an object getter don't transpile to ES5 properly

TypeScript Version:  2.2.1 / nightly (2.2.0-dev.201xxxxx)
2.2.1
Code
You can see the transpiled output in the playground
// A *self-contained* demonstration of the problem follows...
const example = {
  arr: [0, 1, 2],
  bar() { },
  get foo() {
    return this.arr.map((item) => {
      // throws _this is undefined
      return this.bar(item);
    });
  }
};

Expected behavior:
To transpile to:
var example = {
    arr: [0, 1, 2],
    bar: function () { },
    get foo() {
        var _this = this;
        return this.arr.map(function (item) {
            return _this.bar(item);
        });
    }
};

Actual behavior:
Transpiles to:
var example = {
    arr: [0, 1, 2],
    bar: function () { },
    get foo() {
        return this.arr.map(function (item) {
            // throws _this is undefined
            return _this.bar(item);
        });
    }
};

Looks like we just forgot to check for captured this in accessors. Fix is up at #15357

Nice one, thanks for the quick turnaround! 🙂


When routing away from route where map is rendered, error "TypeError: Cannot read property 'bottomright' of undefined"

HOW TO REPRODUCE
(example code below)

Put the Map with Google Layer in some route (I'm using React-router v3 here with react-redux-router).
Put one Marker with a Popup inside with a link which dispatches a routing action
Click on the link > check console

MAP
<Map {...props}>
<GoogleLayer
      googlekey={key}
      maptype={mapType}
      styles={styles}
 />
</Map>

Marker
<Marker>
     <Popup>
         <a onClick={goTo} />
    </Popup>
</Marker>

goTo() {
    dispatch(push(<anything>);)
}

ERROR:
reactBoilerplateDeps.dll.js:205346 Uncaught (in promise) TypeError: Cannot read property 'bottomright' of undefined
    at NewClass.onRemove (reactBoilerplateDeps.dll.js:205346)
    at NewClass.removeLayer (reactBoilerplateDeps.dll.js:95784)
    at NewClass.removeFrom (reactBoilerplateDeps.dll.js:95669)
    at NewClass.remove (reactBoilerplateDeps.dll.js:95662)
    at NewClass.remove (reactBoilerplateDeps.dll.js:92953)
    at Map.componentWillUnmount (reactBoilerplateDeps.dll.js:210619)
    at reactBoilerplateDeps.dll.js:185672
    at measureLifeCyclePerf (reactBoilerplateDeps.dll.js:185338)
    at ReactCompositeComponentWrapper.unmountComponent (reactBoilerplateDeps.dll.js:185671)
    at Object.unmountComponent (reactBoilerplateDeps.dll.js:192107)

I just had the same issue! Sigh

Me too!

Solved it by downgrading leaflet and react-leaflet to:

supported versions

"react-leaflet": "^1.0.1"
"leaflet": "^1.0.2"

@sjchmiela fixed it for me as well +1

I ran into the same problem and looked into it a bit.
The problem seems to be that when removing the map leaflet removes the _controlCorners property of the map before it removes the layers. So when onRemove gets called it can't access map._controlCorners.bottomright.
This should be an easy fix. Since in this case the whole map gets removed anyways it doesn't really matter if the position for the bottom right control corner gets reset so we can just add a check if it is there or not.
I'll make a PR for that.

There is a similar problem in line: https://github.com/Charmatzis/react-leaflet-google/blob/00bc05fe34c5bca5253aee0f00ade356363a8361/src/leaflet.google.js#L91
The same fix should be applied:
https://github.com/Charmatzis/react-leaflet-google/blob/00bc05fe34c5bca5253aee0f00ade356363a8361/src/leaflet.google.js#L109


Circumvent hangs on update method of inky frame 7 when on battery power

Some users and myself experienced issues with the update method, which often hangs when the inky frame is powered by batteries.
Discussions:
https://github.com/pimoroni/pimoroni-pico/issues/866
https://forums.pimoroni.com/t/inky-frame-not-refreshing-screen-on-battery-power-using-inky-frame-sleep-for/23174/23
This adds a timeout for the busy_wait function, so that the code continues after a default timeout of 45 seconds. It seems it fixes the issues, as there are no more hangs. Of course, the root cause seems to be somewhere else, but this way we can at least use the update method successfully on battery power.
Relases for testing pruposes can be found here:
https://github.com/w3stbam/pimoroni-pico/releases/

Thank you! And sorry for missing this before- I'd been embroiled in Pi 5 chaos.
The public API for busy_wait should probably not change, so the default value - =45000 - for maximum_wait_ms should probably be in the function declaration (.hpp) and not the definition.
You could probably also leave is_busy() as-is, and move the timeout handling to busy_wait, since is_busy() is in the public API so it could be called without setting a timeout value and, I guess, would have unexpected results.
make_timeout_time_ms also returns a absolute_time_t  (alias of uint64_t afaik) rather than an int, I think there would be a narrowing conversion and a signedness issue here so something like:
  // hpp
  void busy_wait(uint maximum_wait_ms=45000);
  // cpp
  void Inky73::busy_wait(uint timeout_ms) {
    absolute_time_t  timeout = make_timeout_time_ms(timeout_ms);
    while(is_busy() && !time_reached(timeout)) {
      tight_loop_contents();
    }
  }

Note: time_reached() looks handy, TIL- https://www.raspberrypi.com/documentation//pico-sdk/hardware.html#ga1e41eca96d5c1b3b5e69e3b1a00cdf7d
These e-ink displays are awkward, I have a timeout-on-busy-wait pattern in most of the Python-equivalent code, so it makes a lot of sense here too. Thank you.

Thank you for this. I've been having issues with my Inkyframe hanging on updates but it has been working perfectly since applying the firmware in from your test releases!
I look forward to this being in a official release 😃

Replaced by #900 implementing my suggestions.
I was going to add a Co-authored-by but I don't think f<EMAIL_ADDRESS>is your real email address 😆  so I settled for attribution via the commit message.
Did get a chuckle out of it though.

@Gadgetoid I'm not seeing the mentions on the release page. What version is this in?
This fix appears to be needed for a 7.3" Inky Frame based on https://forums.pimoroni.com/t/inky-frame-slide-show/19996/35


Refactor image caching

I refactored image caching. For big image I have scale down the image size and store it on disk.
cc @aleffert

This needs unit tests. They can use a different path and delete it on initialization to ensure it doesn't interfere with any existing user data.

We need to handle the case where a user logs out. Also, we should probably mark these as using NSURLIsExcludedFromBackupKey.

If I scroll up and down on a slow connection is this going to result in a lot of requests and compression operations for the same image?

Added NSURLIsExcludedFromBackupKey on image path. Also added filter for checking if image request is already in queue. it will avoid duplicate image requests
cc @aleffert

Sorry for the long back and forth. Just a couple more things.

:+1:


Enable metallb in CI

Issue
Currently, metallb is enabled from within the itest itself.
Solution
Enable metallb in CI instead. (For local testing would need to have a devenv with metallb already enabled.)
Related: https://github.com/canonical/microk8s-core-addons/issues/146
Release Notes
Enable metallb in CI.

This is fine by me, though I thought the discussion last week was that we could see if there's another option for it.
For the bundle testing, where we don't enable/disable it (vs traefik), the assumption that anyone running the integration tests will probably have metallb enabled is probably a safe one, but it would be ideal to use the same pattern in both places.
If we're going to keep the enable/disable || before/after metallb tests in traefik, may as well use the same pattern here.
A preflight check in (maybe in conftests, probably as a pytest hook) would nice nice, both to flag to anyone who may have forgotten to enable metallb exactly why their tests are failing, and to give us a clear message in CI if it ever stops for some reason.

A preflight check in (maybe in conftests, probably as a pytest hook) would nice nice, both to flag to anyone who may have forgotten to enable metallb exactly why their tests are failing, and to give us a clear message in CI if it ever stops for some reason.

Agreed. I haven't done it because I wanted to avoid parsing strings:
$ microk8s status --addon metallb
enabled

Going to merge it as-is; happy to submit another PR with a good way of checking for metallb status.


Support for Pipenv

Looking to integrate a pipenv built Python project with my Artifactory instance. JFrogCLI currently only supports pip client.
It would be nice to have JFrogCLI support pipenv as well

Do we have any update on this one? It will be nice to have python native support for JFrog CLI.

+1 Currently we're using the native gradle and npm support, but python uploads have to be done with jforg rt u, as opposed to python-publish or something similar.

@DanielJRutledge -
Supporting pipenv is included in our roadmap - that is for generating build-info, similarly to what the jfrog rt pip command does.
As for uploading python packages to Artifactory, jforg rt u is probably the way to go. Let us know know however if you see any value in adding a specific publish command for python. It seems that thsi command will perform plain upload, just like jfrog rt u. The reason for habing the jfrig rt npm-publish command, is becuase this command actually packs the package prior to uploading it. If you already have the npm package built, you can upload it using jfrog rt u.

I was thinking more along the lines of handling the Artifactory properties automatically so that we don't have to supply them manually in the jfrog rt u command, as they are needed in order for Artifactory to resolve packages properly on pulls.
Our uploads currently look like this:
jfrog rt u "target/dist/(*)-([0-9]*)/dist/*-([0-9]*)(-py*|.tar.gz)" pypi/{1}/{3}/  --server-id=artifactory --recursive=true --props="pypi.name=${pkg_name};pypi.normalized_name=${pkg_name};pypi.version=${pkg_version}"
Where pkg_name and pkg_version are spliced from the folder/file name.
I assume npm-publish picks up the name and version properties from the package.json and there isn't a need to supply them separately as props.

Got it @DanielJRutledge.


Silence Sass deprecation warnings coming from GOV.UK Frontend by treating Sass files loaded from extensions as dependencies

Dart Sass allows you to silence deprecation warnings coming from dependencies (like GOV.UK Frontend, which is included via the extensions system) by using the quietDeps flag. A ‘dependency’ is defined as any file that’s loaded through loadPaths or importer. Because we are using the legacy Javascript API, we use includePaths which is equivalent to loadPaths.
In order to ensure that Sass files loaded by the extension system are treated as dependencies, we need to load them using this mechanism.
Add node_modules to the list of include paths when calling the Sass compiler, and modify the import paths generated by the sass-extension so that they are relative to node_modules rather than full file-system paths.
Update the two Sass files that manually import GOV.UK Frontend to import them relative to node_modules.
Enable the quietDeps flag and remove the silent logger as it is no longer needed.
We also have to update to Dart Sass 1.49.10 which allows us to silence the remaining warnings, which are caused when mixins and functions in GOV.UK Frontend are called from application stylesheets.
From the changelog for 1.49.10:

Quiet deps mode now silences compiler warnings in mixins and functions that are defined in dependencies even if they're invoked from application stylesheets.

I can rebase this and try and resolve the conflicts this morning.

@36degrees I definitely like these changes... I'm a little worried though about changing the Sass import paths. This feels like it could be a breaking change for some people, especially for people using other extensions. Struggling to find an example so far though, so I could be worrying for nothing 😅

I'm a little worried though about changing the Sass import paths. This feels like it could be a breaking change for some people, especially for people using other extensions. Struggling to find an example so far though, so I could be worrying for nothing 😅

As far as I can tell no import paths were previously defined, and so these changes should just be adding 'node_modules' to what was previously an 'empty set'. Therefore, I think any previously working import would have had to resolve relative to the stylesheet and not rely on import paths (because there weren't any).
So based on that and the comment here, I can't think of a scenario where the behaviour of an existing working import would be affected by this change… 🤔
Does that make sense to you, or am I missing something?

I'm a little worried though about changing the Sass import paths. This feels like it could be a breaking change for some people, especially for people using other extensions. Struggling to find an example so far though, so I could be worrying for nothing 😅

As far as I can tell no import paths were previously defined, and so these changes should just be adding 'node_modules' to what was previously an 'empty set'. Therefore, I think any previously working import would have had to resolve relative to the stylesheet and not rely on import paths (because there weren't any).
So based on that and the comment here, I can't think of a scenario where the behaviour of an existing working import would be affected by this change… 🤔
Does that make sense to you, or am I missing something?

Ah, maybe my language is a bit imprecise here sorry; what I was specifically referring to was that this PR changes the path you need to use to @import a Sass file in the node_modules tree. My thinking was that if someone has a Sass file that they're importing in the same way that we do in docs.scss
https://github.com/alphagov/govuk-prototype-kit/pull/1272/files#diff-7483aebf0f5093509cb6d0bec0bc39a40f879df4f0ec4a6e5cfa3dc8bc8e956a
- @import "node_modules/govuk-frontend/govuk/all";
+ @import "govuk-frontend/govuk/all";

then they would have to change their path in the same way.
Fortunately it looks like if you're using an extension, the way the _extensions.scss file is generated means that you don't need to add your own Sass import (I found a good example in a DEFRA prototype that uses both govuk-frontend and hmrc-frontend, although I'm not sure how their _extensions.scss file got committed 😅).

Based on my understanding, I think the existing import would continue to work, it's just that the deprecation warnings wouldn't be silenced as it wouldn't be treated as a dependency. From memory (it was a while ago now) that's the only reason I had to change those hardcoded paths.

Based on my understanding, I think the existing import would continue to work, it's just that the deprecation warnings wouldn't be silenced as it wouldn't be treated as a dependency.

Ah of course, that makes sense. Except...

From memory (it was a while ago now) that's the only reason I had to change those hardcoded paths.

... if I change the paths back (but keep the other changes) I don't get warnings 😕

Possibly I'm mis-remembering then. Perhaps I made that change expecting the remaining warnings to be silenced, before realising that Dart Sass 1.49.10 was required to 'silence compiler warnings in mixins and functions that are defined in dependencies even if they're invoked from application stylesheets'?
Maybe Sass is clever enough to realise that even though the path is relative it's still loading a path that could be loaded using loadPaths?

@36degrees thanks for spending time looking at this with me this morning! This comment summarises what I think we figured out from that:
I think we found that the change to add includePaths and import GOV.UK Frontend via a load path is not strictly necessary. I think we found that Dart Sass treats imports relative to the current working directory as different to imports relative to the file in which the @import rule appeared, quietDeps works the way we want either with that change or without it.
This can be seen by taking the changes in branch https://github.com/alphagov/govuk-prototype-kit/tree/ldeb-dart-sass-quiet-deps (which doesn't add includePaths, but has the same outcome as this PR), and change the import in app/assets/sass/unbranded.scss to be relative to the file:
- @import "node_modules/govuk-frontend/govuk/settings/all";
+ @import "../../../node_modules/govuk-frontend/govuk/settings/all";

then you get warnings about division where previously there were none.
So I think while it is correct that Dart Sass treats any file that's loaded through loadPaths as a dependency [1], the behaviour of the default importer [2] seems to also need to be taken into account (except with the caveat that 'stylesheets that are imported relative to the entrypoint are not considered dependencies').

So with all that in mind, I've raised a PR against my own branch, without the loadPaths change, and I'd like to merge that instead, on the principle that  that requires less changes and having less code is better 😅
Does that all make sense to you? Would you be happy to review PR https://github.com/alphagov/govuk-prototype-kit/pull/1301?

Closing in favour of #1301 (can reopen if we decide not to go that way)


handle null value from formbuilderTextfield

hi , i would like to know the right way how to handle null value from formbuilderTextfield , thank in advance .

What exactly do you mean by 'handle'? If you need only non-null values from FormBuilderTextField, you may consider using
a valueTransformer to transform the null to say an empty string.

@danvick what i mean
Example: i have 2 textfields (name [required] and bio [optional]) if i don't input anything to bio textfield, i want get data from Form builder like this
{name: 'jhon'}

I'd advise massaging the data by yourself otherwise in case you need changes to the returned map.
Or maybe create a PR if possible.

@danvick thank you, solved


Amending assertColumnExists to accept Closure to test configuration

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[ ] Visual changes are explained in the PR description using a screenshot/recording of before and after.

The PR changes assertColumnExists to behave like assertFormFieldExists where a closure can be passed to assert the configuration of a column. This will avoid adding numerous assertions targetting specific attributes of a column with a more open approach and, potentially, in v4, allow the removal of superfluous assertions such as assertTableColumnHasDescription.

Just added in support to add a record to accurately get the state of the column. I've left this as a draft mainly to get feedback on a particular aspect of the assertion and how you want to approach it:
...
if ($checkColumnUsing && $column->getRecord()) {
    Assert::assertTrue(
        $checkColumnUsing($column),
        "Failed asserting that a field with the name [{$name}] and provided configuration exists on the [{$livewireClass}] component."
    );
}
...

I don't see the point of using the closure if you're not supplying a record. This will work without a record in some instances where the configuration doesn't rely on it being evaluated. (e.g. hidden() vs isHidden()) but here, I've elected to not check the closure if the record is null as it may give rise to false positives. What I'm wondering about is feedback to the end user if this is the case. None of the other assertions check to see if the record is valid so no inspiration there but am thinking to change this to:
...
if ($checkColumnUsing) {
    Assert::assertNotNull(
        $column->getRecord(),
        "The record supplied is null"
    );

    Assert::assertTrue(
        $checkColumnUsing($column),
        "Failed asserting that a field with the name [{$name}] and provided configuration exists on the [{$livewireClass}] component."
    );
}
...

Feedback appreciated!

Thanks


[Resolver] Add option to pre-filter the container versions

This gives us a performance boost when we are iterating versions because we
don't need to parse the tools version of versions who will always be rejected
anyway.
-- rdar://problem/31652875 Turn PackageContainer's versions property into a method which accepts a filter closure

Added, this shows a 4x boost

@swift-ci please smoke test

@swift-ci please smoke test


The versions on GitHub different with the versions on npm

Hi @simsalabim ,
We are cdnjs team, we want to host this project in cdnjs.
I found that there are 5 releases on GitHub but only one release on npm. I'd like to confirm with you if it's correct? Or is it possible to publish all releases on npm?
Thank you.
https://github.com/cdnjs/cdnjs/issues/8069
https://github.com/cdnjs/cdnjs/pull/8353

Hi @pvnr0082t, I'm sorry it took me that long to get to this issue. I just released new version v1.1.3 here on GitHub and published it on npm registry.
package.json was introduced starting v1.1.2, thus I don't see much benefit in publishing precursory releases on npm.

Thanks for help. @simsalabim


Better Implementation in Activation Grids Notebook

Hi, thanks for your previous helps. There is a little trouble in index selecting of Better Implementation in Activation Grids.
The method to decrease computing consumption is to compute 64/196 batches by the code:
rand_inds = tf.random_uniform([batch_size], 0, N, dtype=tf.int32).
But when I change the rand_inds to rand_inds = tf.range(0, 64, 1), I found indexes I never selected are updated somewhat. I thought they should be random noise.
Reason I did this test is because running times of naive implement and better implement are not much different. Both implements took about 350s in my computer GPU 1080. (Theoretically, two running times should have several times gap I think)
Could you help me to make some analysis about this trouble? Thank you very much.
indexes: 0-63

random 64 indexes

Hello, sorry submit two things in one issue.
The thing is when I read your paper (https://distill.pub/2018/building-blocks/) about this tutorial, I found

For instance, GoogLeNet has multiple floppy ear detectors that appear to detect slightly different levels of droopiness, length, and surrounding context to the ears.
In fact, when I handle some more advanced network (ResNext, SE-ResNeXt), I also found there are many similarly functional convolutional kernels in lowest and highest layers like paper said.

Have you tried some methods to suppress appearance of these similar activation maps when training a new network? Or maybe it could improve performance.
I tried to introduce correlation coefficient (SSIM) and wasserstein-1 distance to evaluate similarity among activation maps. But there is no idea to combine these methods into loss function for training in a fast enough way. I would very appreciate it if you would like share some thoughts or related papers about it.

The method to decrease computing consumption is to compute 64/196 batches by the code:
rand_inds = tf.random_uniform([batch_size], 0, N, dtype=tf.int32).
But when I change the rand_inds to rand_inds = tf.range(0, 64, 1), I found indexes I never selected are updated somewhat. I thought they should be random noise.

That's a nice way to test your understanding! You're absolutely right that that is a surprising result. The issue is a bit subtle.
If you do an activation grid visualization naively, it will have snouts and such facing different directions in each place. This isn't because they are representing different vectors, it's that the model mostly doesn't care at that point about orientation.

In order to fix this, we use a special parameterization. This general idea is discussed in the differentiable parameterizations article, which you may enjoy reading. In particular, aligned feature interpolation is a kind of similar idea.
For this particular visualization, we use the following parametrization:
    group_imgs_raw = param.fft_image([n_groups, W, W, 3])
    unique_imgs_raw = param.fft_image([N, W, W, 3])
    opt_imgs = param.to_valid_rgb(tf.stack([
            0.7*unique_imgs_raw[i] +
            0.5*sum(groups[i, j] * group_imgs_raw[j] for j in range(n_groups))
            for i in range(N) ]),
            decorrelate=True)

Because group_imgs_raw are shared between all the images we optimize, updating some images will also cause others to change.

Have you tried some methods to suppress appearance of these similar activation maps when training a new network?

I think you are asking if we've tried to train a network while suppressing, say, it from having a floppy ear detector? I have not tried anything like that, but it sounds like an interesting experiment!

Hi, thanks to your fast and warm response.
First one:
It seems like tensorflow updating all the variables in Graph, so the related tensor that makes up opt_imgs will be updated for updating opt_imgs. That caused others to change, it sounds a bit counterintuitive but reasonable.
When I initialized group_imgs_raw in advance, wanted results were generated.

Second one:
Say, there are always multiple floppy ear detectors appeared. In other words, these detectors' outputs or activation maps will be similar (similar channel-wise matrix). There are many ways to evaluate similarity between matrix or vector.
I think suppressing appearance of multiple similar detectors is approximately equal to decreasing similarity between activation maps. Combining the way of evaluating activation maps with loss function maybe improve performance.
But I don't have further idea about this, e.g., how to solve the problem of a surge in computing, because there are 512 activation maps that need to compare similarities. I think of this problem, because matrix decomposition methods are used in your code for dimensionality reduction.

There is a paper in CVPR2019 seems have begun to solve conv-kernel functionally overlap or redundancy problem.
RePr: Improved Training of Convolutional Filters. A Prakash, J Storer, D Florencio, C Zhang. CVPR2019.
This is a good idea to solve the problem.
Further, I think better kernel overlap metric should be derived from better understanding of conv-kernel functions. Better understanding -> better metric for kernel functionally overlap -> alter the training method by fusing with the metric (like this paper's metric and training method).


meshcentral: 0.9.98 -> 0.9.98

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for meshcentral is: "Computer management web app"
meta.homepage for meshcentral is: "https://meshcentral.com/info/"
meta.changelog for meshcentral is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/yrpawjs5j9v5m2rhdg853d8hfni0cyri-meshcentral-0.9.98/bin/meshcentral had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.9.98 with grep in /nix/store/yrpawjs5j9v5m2rhdg853d8hfni0cyri-meshcentral-0.9.98
found 0.9.98 in filename of file in /nix/store/yrpawjs5j9v5m2rhdg853d8hfni0cyri-meshcentral-0.9.98

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

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
meshcentral

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

meshcentral

Maintainer pings
cc @lheckemann for testing.

Interesting case... While updating dependencies is fine and dandy, this commit message/description is awkward at best, so let's not use it as is.


changing helm log to fmt.Printf

Signed-off-by: jonahjon<EMAIL_ADDRESS>Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherrypick release-0.12


Servicebus version increment after May release

Servicebus version upgrade PR:
May GA release version 7.2.1
The next version to update to : 7.3.0-beta.3

/azp run java - servicebus - ci


Add export_csv.py script

The script can be used to export *.pkl files to an intermediate data format that can then be converted to mastodon file format using https://github.com/mastodon-sc/mastodon-deep-lineage/tree/master/src/test/java/org/mastodon/mamut/astec
Data for which this script can be applied can be found here: https://figshare.com/projects/Phallusiamammillata_embryonic_development/64301

Thanks for the contribution! If you don't mind, I'll soon incorporate that fully within the library.

Feel free. This is why I shared it via the Pull Request.

Moreover, is the format of spots.csv combined with links.csv and fates1.csv [...] a standard format for Mastodon?

Unfortunately, not. This format is highly customized to work with the ascidian data from https://figshare.com/projects/Phallusiamammillata_embryonic_development/64301
It currently can only be further used with https://github.com/mastodon-sc/mastodon-deep-lineage/tree/master/src/test/java/org/mastodon/mamut/astec/AstecReader
Of course, if other datasets fulfill the same requirements, the could be converted with this converter as well:
 * spots.csv: id; label; timePoint; x; y; z; volume
 * links.csv: source spot id; target spot id
 * fates1.csv: tagValue
 * fate_values1.csv: spot id; tagValue
 * fates2.csv: tagValue
 * fate_values2.csv: spot id; tagValue
 * fates3.csv: tagValue
 * fate_values3.csv: spot id; tagValue

The fates2 and fates3 file are only there, because they existed in the ascidian data. Spots.csv and links.csv would be sufficient already. Fates can be added, if they exist.

I was used to MaMuT xml format which was a bit heavy for me to manipulate, but is the csv format is becoming supported I'll make a more general converter.

The MaMuT file format was also the format recommended by https://github.com/tinevez to use for the conversion. But, I also found it easier to work with these CSV files, since I also found the MaMuT xml a bit heavy for the task at hand.


[DOCFIX] add s3a streaming upload docs

@calvinjia Added the s3 streaming upload docs, PTAL, thanks

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/358/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/367/
Test PASSed.


Add SelfAssignementProcessor (SonarRule 1656)

This PR adds a processor for the rule [https://rules.sonarsource.com/java/type/Bug/RSPEC-1656](Variables should not be self-assigned)
class SelfAssignement {
   int a,c = 0;
   int[] b = {0};
   int h = 0;
   int[] g = 0;
   SelfAssignementCheckB checkB = new SelfAssignementCheckB();
-  void method(int e,int h) {
-    a = a; // Noncompliant [[sc=7;ec=8]] {{Remove or correct this useless self-assignment.}}
-    this.a = this.a; // Noncompliant
-    b[0] = b[0]; // Noncompliant
-    b[fun()] = b[fun()]; // Noncompliant
-    int d = 0;
-    d = d; // Noncompliant
-    e = e; // Noncompliant
     int[] g = new int[]{ 0 };
-    g[fun()] = g[fun()]; // Noncompliant
-    h = h;
-    checkB.b = checkB.b; // Noncompliant
-    checkB.getSelf().foo = checkB.getSelf().foo; // Noncompliant
-  }
+  void method(int e,int h) {
+    int d = 0;
     int[] g = new int[]{ 0 };
+    this.g[fun()] = g[fun()];
+    this.h = h;
+  }
   int fun() {
     return 0;
   }
}

@henry-lp, everything seems great, I just left one comment for simple fixes in the documentation. Once you address it, I will merge it, without waiting for Travis since no change in source code will be made.

@fermadeiral Thanks for the review , Fernanda :). I've fixed it.

@henry-lp, thank you very much for this processor, this one was a difficult one!

@fermadeiral thanks for all the help as usual :) .


add 'beginnersBase11ty' to starter-projects

Hi,
I have had so much fun putting this together! 11ty is awesome to work with thank you so much :)

haha I love your possum!
I think for starter projects we want a link to the source code too!

Thank you!


udpdated node-express-mongo Signed-off-by: Ajeet Tiwari <ajeettiwari0…

Related Issue

[bug]: correction required in doc quickstart
Closes: keploy/keploy#1581

Describe the changes you've made
Changed the node-express-mongo guide.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Please let us know if any test cases are added
NA
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] New and existing unit tests pass locally with my changes.

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

Hey @Ajeett01 ! Build is failing due to the error

Also the docs needs to be updated in the specific struct/format! You can refere to this: - https://github.com/Keploy/docs/blob/main/versioned_docs/version-2.0.0/quickstart/python-django-sql.md

Hey @Ajeett01 ! Build is failing due to the error

Also the docs needs to be updated in the specific struct/format! You can refere to this: - https://github.com/Keploy/docs/blob/main/versioned_docs/version-2.0.0/quickstart/python-django-sql.md

It was working fine , wait I will check it again

Hey, any updates @Ajeett01 ?

Hey, any updates @Ajeett01 ?

Working on it.


Short solution needed: "How to get the repository url" (git)

Please help us write most modern and shortest code solution for this issue:
How to get the repository url (technology: git)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to get the repository url


First joining players don't get assigned automatically to default group

After new players joined my server, they didn't get assigned to default group, I've checked with listmembers and they weren't there. I had to manually add each one of them to the group. Am I missing something?
I'm using the 5.0.72 version for my Spigot 14.4.4 server.

Yes. Players added automatically to the default group that are not online don't show with listmembers.
You can use /lp user <user> info  to verify that they are in the default group.

@BrainStone "Online players" mean players that are connected with a Mojang account right?
I tried your method and it works. Thank you.

I mean players that are on the server.
There might be a chance that they then still don't show there.

I see. Then listmembers does exclude all players that are automatically assigned to default. There's a technical reason for that.

Basically everyone who doesn't have a group is in the group default.
No database entry is created to be more flexible and use less space in the database, etc.
Therefore there is no way to know who is in the group as there could be million members, but they aren't saved anywhere.

Yeah this is normal :)


How to use the quantised model for inference

I was able to quantise and save a hugging face model with my custom data how do I use the model for inference. Could anybody help on how to load and use the quantised model with something like trainer / pipeline APIs?
I have 2 files in the directory to which I save my quantised model best_configure.yaml and best_model_weights.pt how do I use these files for inference?

Could you tell me which framework your code runs on, PyTorch or TensorFlow?

Please tell me which mode your model used, eager or fx?
If it's eager mode, we have examples under directory examples/pytorch/eager/huggingface_models. You need to follow our instructions to install huggingface/transformers
Then you can use LPOT API to load the quantized model as follows:
model = AutoModelForXXX.from_pretrained(args.model_name_or_path) # fp32 model from lpot.utils.pytorch import load model = load(args.output_dir, model)  # int8 model
Please note that output_dir needs to contain best_configure.yaml and best_model_weights.pt.
If it's fx mode, we will provide an example in next release. Please wait, thank you.

I was trying this out on eager , but would like to have an example for fx as well.
Thanks for the solution this seems to work, I have a follow up question in the code model = AutoModelForXXX.from_pretrained(args.model_name_or_path) the fp32 model is loaded to model what if I dont have the fp32 model available with me can I still use int8 model.
For eg in a scenario where quantisation is done to reduce storage size it wouldnt be possible to have both FP32 and int8 model in disk.

Actually, what we want from fp32 model is the architecture. If you don't have pretrained weights, it's still OK.
Right now, we still cannot get rid of fp32 model initialization, because quantized model architecture saved in model.pt cannot be reloaded correctly.

So does that mean I should have the fp32 .pt file in the machine for initialization or would having just the config.json file alone  suffice for initialisation.?

Additionally on trying with the sample code I tried to print dtypes of weights of qunantised model, I am getting the dtypes to  be torch.float32 is this expected
ie
model = AutoModelForSequenceClassification.from_pretrained('fp32/model/path')
from lpot.utils.pytorch import load
modellpot = load("path/to/lpotmodel/", model)
for param in modellpot.parameters():
  print(param.data.dtype)

this prints.
torch.float32
torch.float32
torch.float32
torch.float32
torch.float32
torch.float32
torch.float32
..
...

How do I verify my model loaded has been quantised?

Please provide the necessary documents for us to reproduce your problem.

You can use print(modellpot) to check whether the model is quantized. For example, Linear layer will be converted to QuantizedLinear layer.
Actually, only layers that are supported in PyTorch will be converted into Quantized layer, so not all parameters are int8/uint8.

Thanks  xin3he for the tip. this helps
I am able to see layers are named dynamicQuantised layers and in the layer it shows the dtype is qint8 while printing the model.
But It is still confusing why  print(param.data.dtype) displays torch.float32 for all the parameters. Infering from your comment "so not all parameters are int8/uint8" I was hoping to see some of the params dtype to be int8

It seems that the quantitative model does not support the parameters or named_parameters attributes. If you compare the parameters of the fp32 model and the int8 model, you will find that the parameters of the int8 model are unreasonable, such as the size of the tensor.
I suggest you use print(model.state_dict()) instead, and then you can see that the dtype of the tensor is torch.qint8.


Add link to markdown syntax help

When writing  a message to abandon a change, the hint below the form says "Write your comment here. You can use a simple markdown-like syntax". It would be nice if the words "markdown-like syntax" would link to a help / web page explaining the supported syntax.

@sschuberth: Thanks for your suggestions.
Do you think the following guide would help? I have not found anything Gerrit specific, but most things should work.
https://guides.github.com/features/mastering-markdown/
This seems to be Gerrit specific, but IMHO not in a condition that could be used as reference: https://gist.github.com/dlebech/62b69ee7c9fdb53c63a6.
Probably it would also be worth adding a guide to the Gerrit documentation and link that.

Hi @uwolfer! Based on the information from the Gist I've created a change for upstream Gerrit to document the three supported markdown-like elements: https://gerrit-review.googlesource.com/74494
Once this gets merged, the correct link would be: https://gerrit-review.googlesource.com/Documentation/user-review-ui.html#summary-comment
Although the summary-comment anchor does not exist yet in the current Gerrit documentation, you could still already use that link as non-existing anchors simply get ignored, and IMO user-review-ui.html, even in its current state, is the most fitting official Gerrit documentation regarding the markdown-syntax supported in comments as it at least mentions the block quote element.

Thanks @sschuberth for your great efforts here! I will add this link once the googlesource.com Gerrit setup gets updated with this doc update.


Mirror extraction

This PR implements or fixes...
This PR is extracting Mirror from Draggable. This will allow Draggable to focus on core dragging and defer the mirror logic to its own plugin.
This will entail some breaking changes:

Drag events won't include the mirror property (can be accessed through Mirror events)
Mirror events are now triggered after drag:start
appendTo option is part of mirror config

This PR closes the following issues...
N/A
Does this PR require the Docs to be updated?
Yes
Does this PR require new tests?
Yes
This branch been tested on... (click all that apply / add new items)
Browsers:

[x] Chrome version
[x] Firefox version
[x] Safari version
[x] IE / Edge version
[x] iOS Browser version
[ ] Android Browser version

@beefchimi this should be ready for review. Added tests and made sure examples are working 👍 Still need to address documentation changes and figure out what's going on with the "Drag events" example.
Let's try and get this in sooner than later, so we can move forward with the Styleable plugin PR

@beefchimi Examples pages should now work perfectly again. Also addressed READMEs to reflect the updates.
Let me know if this is good to go


Consider server only apps

At the moment properties clientPrefix and client are required in createEnv options.
These options are unnecessary for API only apps (express).
For the env-core package it would be great to make these options optional.

if you dont have both sides this package is pure overhead for you.
you can just create a zod schema and parse it and be done with it. don't need the proxy logic that handles client/server boundary


Add feedback button

I haven't been able to confirm if match submission service is working - can you test before merge?

This version works with fixed location feedback button. Not sure why it was giving me so many bugs before

Can we get one more screencap of the modal itself?


Color rgb hex

This PR will add the support for color picker in Chaise. ERMrestJS#864 makes sure the data is properly served to Chaise.
Summary of changes:

Added the style for the new  .chaise-color-preview class that ERMretJS will use for color preview in read-only modes.
Added a new color input type and colorPicker directive that is used in recordedit and inputSwitch for showing a color input. I used this package for the color picker functionality. It was the only proper and functional color picker that I could find. The only downside of using this one is the fact that it needs jQuery (which is not an issue really, just something that I hope it didn't need.)
Modified test cases in both read-only and entry modes to test this new column type.

~P.S. I commented the test case that I added to recordedit-helper.js because it's not working properly. I'm currently trying to fix it.~
related issue: #2015

@jrchudy I fixed my color test cases and they should be working properly now.
While working on this, the broken float test case was causing issues for me (as I couldn't properly run the new tests.) So I spend some time trying to rewrite that it with proper promise-chain. But that didn't help at all. Now it's easier to figure out where exactly in the it the error is happening, but I couldn't fix it. Besides, this test originally was testing validation. I was setting an invalid value and was making sure that the error is displayed. But ever since it has been modified and wasn't event doing that (it was setting the input to some valid value and was clearing it.) So for now, I just ignored it by doing xit. I'll spend a little more time trying to figure this out.

Tests are passing for me locally.


Replaces AtomicReference

with oldfashioned synchronized because for threads contition spinning causes CPU overheating
fix #1002690

retest this please

The methods are synchronizes but wouldn't it be possible that multiple threads access different methods and therefore there could be a race condition when accessing threads?

LGTM. The error is related to EE.

Simon,
generally access to 'threads' should be atomic (so synchronious in this
time). AtomicReference was working pretty good. I think that main problem
was related to iulian's finding so :+ used instead of :: and permanent
recreation of 'prev :+ threadToAdd'. 'synchronized' just does it once but
blocks bigger range of code.
this is how I see it. I hope Iulian can correct me if I'm wrong.
2016-04-28 15:07 GMT+02:00 Simon Schäfer<EMAIL_ADDRESS>
The methods are synchronizes but wouldn't it be possible that multiple
threads access different methods and therefore there could be a race
condition when accessing threads?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/scala-ide/scala-ide/pull/1097#issuecomment-215417144